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
Mon Jul 3 18:38:13 CEST 2017
> On 3 Jul 2017, at 14:09, Carsten Schiefner <ripe-wgs.cs at schiefner.de> wrote: > > I find the requirements "unusual" and not entirely "RIPE style" - to say > the least. <AOL Mode>Me too!</AOL Mode> 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. Mind you, the hotel demanded they photocopy my passport at check-in. Which is annoying enough. I wonder what would happen if a bunch of “tourists" turned up in Dubai and just happened to walk into the RIPE meeting? Will there be badge police at the door checking for bar-codes? This DTCM silliness is not compatible with RIPE meetings and I’m very disappointed that The Management has just accepted it.
- 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 ]