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 ]
Jim Reid
jim at rfc1035.com
Wed Jul 5 15:49:55 CEST 2017
> On 5 Jul 2017, at 14:02, Hans Petter Holen <hph at oslo.net> wrote: > >> On 3 July 2017 at 18:38, Jim Reid <jim at rfc1035.com> wrote: >> >> It’s even stranger because when I was in Dubai for an ITU meeting (sigh) earlier this year, nothing was said (or done) about these DTCM requirements. Attendees were not bar-coded or obliged to hand over their Personal Data in advance. > > ITU is an international treaty organisation, so special rules may apply. Special rules didn’t seem to have been put into place for that earlier meeting. The hotel that hosted it didn’t know or care if I was an attendee. The immigration people at DXB didn’t either. There probably would have been no way for either of them to find that out. Assuming they wanted to. Which they didn’t AFAICT. > The ITU and UN meetings I have been to have had rather strict registration and badge restrictions. How those organisations choose to run their meetings is an entirely different issue.
- 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 ]