Re: [Mtgvenue] Fwd: New Version Notification for draft-daley-gendispatch-venue-requirements-02.txt

[Benson Muite <[e-mail]>]

On 29/02/2024 22.06, John Levine wrote:
> It appears that Benson Muite  <[e-mail]> said:
>> This is an improvement, thanks.  Rather than single out Europe, North
>> America and Asia, a split by timezones is more reasonable as there are
>> places in Europe, North America and Asia that would likely not get the
>> right makeup or enough attendees for a viable IETF meeting and so would
>> be considered exploratory locations.
> 
> This makes no sense. Dublin, London, Reykjavik, and Dakar are all in
> the same time zone but the first two are established Europe meeting
> cities and the other two would be exploratory. Washington DC,
> Philadelphia, Bogota and Lima are all in the same time zone, same
> thing.
Had started on a revision available at:
https://codeberg.org/bkmgit/meeting-locations/src/branch/main/draft-mtgvenue-meeting-policy-00.xml

The rotation policy helps ensure more equitable participation in IETF
activities.  As you note, Reykjavik is in Europe and should be
considered exploratory but under the current vague rotation policy of
America, Asia and Europe, would not. A more precisely defined and less
exclusionary 1-1-1 type policy under timezones, is
 - [UTC-10,UTC-2) Corresponding roughly to the Americas
 - [UTC-2,UTC+6) Corresponding roughly to Europe, the Middle East,
     the Near East and Africa
 - [UTC+6,UTC-10) Corresponding roughly to the Far East and Oceania

This would place Dakar and Reykjavik on the same footing.
> 
> Even within a single country, Iqaluit and Toronto are in the same
> time zone, but I don't think we're going to Nunavut.
> 
There may be good reasons to have a meeting served only by satellite
internet.  This would certainly be exploratory.  If a meeting were to be
held in Nunavut, then it would be considered a meeting in the Americas,
so other meetings should preferably be held in  [UTC-2,UTC+6) and
[UTC+6,UTC-10).