On 5 Jul 2017, at 11:50, JORDI PALET MARTINEZ <jordi.palet@consulintel.es> wrote: I fully agree that we should have meetings at every country covered by the RIPE constituency, however, I think the community has the right to decide, when there are such kind of special conditions, if we want to have a meeting there or not.
I’m not sure I agree with “the community has the right to decide” part. From an operational point of view (from my experience of running UKNOF meetings and DNS-OARC workshops, it is not a simple task to find a place to hold a meeting with a willing Host. Once the Host is found it is then down to venue logistics and that in itself is not simple as there are so many different parts to this that need to join up… RIPE NCC have to cover the whole region it operates in. It can not be shown to and should not favour one part of the region over another. There are going to be parts of the region where things are unusual for those from “the West”, however we also have to keep in mind that those coming from outside of the usual “West” will also have faced challenges travelling to RIPE meetings due to various Visa / entry rules. How easy is it for delegates from the Middle east to get to a RIPE meeting being held in say, Amsterdam? We all, at some point, have to accept that it will be difficult to travel to meetings due to entry requirements, or the country has policies we do not agree with - in which case, we give the appropriate message by not going to that particular meeting. ICANN too have similar considerations when it comes to their main meetings. It is this - meeting numbers and demographics - which may shape the choosing of future venues, Host and ultimately, meeting logistics.. Regards Denesh
Now is too late to change the meeting location, but we should learn from that for future locations with “special” conditions.
I’ve been in Dubai already for a previous meeting, and for other reasons, and haven’t got any issue, but I don’t recall having needed to submit my passport up-front, even if I was a speaker, so it is really surprising.
Regards, Jordi
-----Mensaje original----- De: ripe-list <ripe-list-bounces@ripe.net> en nombre de Gordon Lennox <gordon.lennox.13@gmail.com> Responder a: <gordon.lennox.13@gmail.com> Fecha: miércoles, 5 de julio de 2017, 12:27 Para: <ripe-list@ripe.net> CC: Nigel Titley <nigel@titley.com> Asunto: Re: [ripe-list] RIPE 75 - DTCM Requirements
On 5 Jul 2017, at 11:01, Nigel Titley <nigel@titley.com> wrote:
can we move on?
With respect - no.
If it is OK to chat about coffee then it ought to be OK to chat about other things related to the meeting.
It has already been pointed out that this meeting is atypical is several respects.
I am intrigued by the requirement to supply a mini-CV. I am not clear where and when the bar-codes will be scanned. Any information there?
Using the Internet in this region though has been problematic in the past, both in terms of content (mostly the usual stuff) and services/protocols (again mostly the usual stuff). So it seemed worthwhile to talk about the current situation, of which I presume NCC are quite aware.
It was good to get Brian’s reassurance that access to the meeting network would be as usual, and by implication there will be no restrictions towards the rest of the Internet.
By way of putting some of this in some kind of perspective I mentioned two other meetings.
In Stockholm I was not entirely comfortable with the use of RFIDs. Maybe I have been to too many IETF meetings?
In Beijing I was struck by the “bucket” solution - I should have guessed that Randy was involved. But it met both the requirements of the local authorities and of the IETF crowd. I wonder which one was harder to please?
So probably still some questions. But I guess no rush. I hope nobody else will feel inhibited about writing though.
And I sincerely hope Randy’s coffee needs are met!
Gordon
********************************************** IPv4 is over Are you ready for the new Internet ? http://www.consulintel.es The IPv6 Company
This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.