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

[Jay Daley <[e-mail]>]

Hi All

Please see the latest version of our I-D updating the meeting venue requirements.

Following feedback, we have made the following changes:

1.  Instead of replacing all of RFC 8719, it now aims just to replace the process for agreeing an exploratory meeting for the reasons given in the I-D.  The text includes a number of safeguards in the proposed new process.

2.  Removes the reference to the Tao as that is being retired.

3.  Removes the whole section about Internet filtering.  The feedback is that this is not as restrictive as the LLC has read it to be. 

There are two requests made by more than one person that we have not incorporated.

a.  Requiring the LLC to always find a secondary hotel at a lower price point.  Our reasons for not including this are: 
- this is very hard to obtain (often because we get such a large discount at the main hotel due to our block size)
- when we do do it, the block is only very lightly used and that carries a significant financial risk (that ultimately will end up back on registration fees) 
That does not mean that we will not do this, for example we are actively aiming to do so for IETF 120 Vancouver, but we do not want to be required to do so.

b.  Requiring the LLC to consider security of devices when assessing venue suitability.  Our reasons for not including this are:
- This is a huge topic that could take a very long time to resolve
- This is a concern that has been claimed about multiple countries and assessing the validity of those claims is particularly difficult.  
- If the claims above are correct and this becomes policy, that could severely restrict the number of countries we can visit.

It is our hope that this is close enough to agreement now that we do not need a session at IETF 119 to discuss.  If anyone disagrees then please let us know.

Jay


> Begin forwarded message:
> 
> From: [e-mail]
> Subject: New Version Notification for draft-daley-gendispatch-venue-requirements-02.txt
> Date: 29 February 2024 at 16:40:44 GMT
> To: "Jay Daley" <[e-mail]>, "Sean Turner" <[e-mail]>
> 
> A new version of Internet-Draft
> draft-daley-gendispatch-venue-requirements-02.txt has been successfully
> submitted by Jay Daley and posted to the
> IETF repository.
> 
> Name:     draft-daley-gendispatch-venue-requirements
> Revision: 02
> Title:    IETF Meeting Venue Requirements Review
> Date:     2024-02-29
> Group:    Individual Submission
> Pages:    11
> URL:      https://www.ietf.org/archive/id/draft-daley-gendispatch-venue-requirements-02.txt
> Status:   https://datatracker.ietf.org/doc/draft-daley-gendispatch-venue-requirements/
> HTML:     https://www.ietf.org/archive/id/draft-daley-gendispatch-venue-requirements-02.html
> HTMLized: https://datatracker.ietf.org/doc/html/draft-daley-gendispatch-venue-requirements
> Diff:     https://author-tools.ietf.org/iddiff?url2=draft-daley-gendispatch-venue-requirements-02
> 
> Abstract:
> 
>   Following a review of the IETF meeting venue requirements, this
>   document proposes updates to RFC 8718 “IETF Plenary Meeting Venue
>   Selection Process”, clarifies how the IETF Administration Support
>   Activity (IASA) should interpret some elements of RFC 8718, and
>   proposes a replacement exploratory meeting process, thereby updating
>   RFC 8719 "High-Level Guidance for the Meeting Policy of the IETF".
> 
> 
> 
> The IETF Secretariat
> 
> 

-- 
Jay Daley
IETF Executive Director
[e-mail]