This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-list@ripe.net/
[ripe-list] RIPE 75 - DTCM Requirements
- Previous message (by thread): [ripe-list] RIPE 75 - DTCM Requirements
- Next message (by thread): [ripe-list] RIPE 75 - DTCM Requirements
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Randy Bush
randy at psg.com
Tue Jul 4 11:55:23 CEST 2017
> Access to the IETF’s network was a local concern and so we all picked > a login pair out of a bucket at registration. So the local need to > restrict access to attendees was complemented by giving a bit of > anonymity to attendees. > > Maybe NCC can clarify a little bit more what is to be expected in Dubai? as one of the key designers of the beijing authorization system, i have no idea how to help in dubai (if anyone cared) because i have no idea what the layer>7 goals and constraints are. randy
- Previous message (by thread): [ripe-list] RIPE 75 - DTCM Requirements
- Next message (by thread): [ripe-list] RIPE 75 - DTCM Requirements
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]