Re: [Mtgvenue] Update of RFC8719

[Benson Muite <[e-mail]>]

On 12/29/23 20:53, Michael Richardson wrote:
> 
> I see Benson's point is that, going forward into an era where there are more
> and more remote attendees, and perhaps some more intentionally all-online
> meetings (vs pandemic forced meetings), that rather than document our
> 1-1-1 as Asia-Europe-NA, that we could do that via time zones instead.
> 
> What we would be doing is saying that we need to distribute the pain of who
> stays up all night to remote attend, rather than distribute the pain of
> travel for those who are in-person.
> 
> (It also means, I guess, that we can meet in Philadelphia in lieu of Bangkok,
> as long as the in-person meeting occurs in Bangkok time zone.  Not that I
> think we would do this, but we could)
Would expect the in person meeting to occur in a physical location
within that time zone.
> 
> UTC-12 for Americas means Hawaii is still in Americas, although we once
> counted it as Asia :-)
> 
Yes, though suggestions for exact time zone boundaries are welcome.
Puerto Rico and New Foundland could be considered Europe. Northern
Mariana Islands and Guam would be considered Asia/Oceania.
> What Benson's proposal also means is that if we were to return to South
> America, or we were to try Johannessburg, that we'd be within rule to do it
> during the appropriate time zone.
> 
Yes.
> Brian and John's point: we will likely continue to meet where there are
> people who are doing the work.  So in the end, changing the criteria likely
> has no actual effect for a long time.  I don't object to the patch, but I
> don't see it as helping much.
> 
It is nice to have consistency between active RFCs that describe the
aims of the IETF and how it operates.