Consultation on changes to the IETF meeting venue identification and selection process
The IETF Administration LLC is planning to make some changes to the process it uses to identify and select venues for IETF meetings. The intent is to improve the process without changing how we assess venues, which will continue to follow the guidelines in RFC 8718 [1]. The planned changes to the venue identification and selection process are: * Explain clearly all the steps * Provide clarity on who/how venues can be recommended. * Providing a clear path for venues and their agents to recommend their own venue and provide us the details we need to assess them. This already happens but in an unstructured and time consuming way. * Require IETF participants who want to recommend a venue to fill out a form explaining why they think this city is suitable and providing some basic details based on their first-hand knowledge. Assessing cities/venues is a very time consuming process. Utilising local knowledge in this way ensures that we get high quality input from the start and minimises the time we spend assessing unsuitable cities/venues. The new process is below and on the following GitHub repository: https://github.com/ietf-llc/venue-identification-and-selection-process-consultation We welcome any feedback before Sunday 15 November. -- Jay Daley IETF Executive Director exec-direc...@ietf.org # IETF MEETING VENUE IDENTIFICATION AND SELECTION PROCESS ## Step 1 - Recommendation The first step in the selection process is an initial recommendation of a city and/or a specific venue in that city ### Cities within the IETF meeting regions If the city is within one of the three IETF meeting regions (North America, Asia, Europe) you can make a recommendation in one of two ways: * If you are a participant then fill out the "Venue Recommendation (Participants)" [2] form and send that to meeting-plann...@ietf.org. * If you are a venue or an agent for a venue then fill out the "Venue Recommendation (Venues and Agents)" [3] form and send that to meeting-plann...@ietf.org. Additionally the IETF LLC solicits recommendations directly from Global Hosts and self-recommends countries and cities within the three regions that it thinks may be suitable. ### Cities outside of the IETF meeting regions For countries or cities outside of the three meeting regions the process in RFC 8719 [4] for an exploratory meeting needs to be followed: * You must write to the IETF discussion list i...@ietf.org with your proposal for the IETF to meet in a specific city or country. You will need to explain why you are making the proposal and seek support from other IETF participants. * If the IETF Chair decides there is consensus to consider the proposal then they inform the IETF LLC. * The IETF LLC will then work with you to identify cities to take to step 2. You will be asked to fill out the "Venue Recommendation (Participants)" [2] form for each of the cities that goes to step 2. ## Step 2 - Initial Assessment Once a recommendation has been accepted, the IETF LLC carries out an initial assessment by remotely researching the city and any potential venues in that city. The output of this step is a report that assesses if the city is likely to meet or not meet the requirements and a recommendation on whether or not to consider the city any further. ## Step 3 - Community Feedback We then seek community feedback on the assessment report and recommendation. This feedback is assessed and published in a public repository [5]. Depending on the feedback received, we may advance the city to the next step, or return to step 2 and conduct further remote research, or we may reject the city and update the Meeting Location Assessment table [6]. ## Step 4 - Detailed Assessment Once a city passes the community feedback step, we carry out the detailed assessment, which may take some years to complete. This includes the following steps: * Site visits to specific venues undertaken by the meetings team and NOC members to assess the facilities and the network. * Detailed cost discussions with venues. * Initial discussions with secondary hotels. * Discussions with any local tourism or convention bureau on possible support packages. We may choose not to follow up with a specific city at this stage for a number of reasons, such as all the venues are too expensive or unable to meet our network requirements or not available for our required dates. Depending on the reason for not following up we may update the Meeting Location Assessment table or it may continue to show this as a potential location. ## Step 5 - IETF LLC Board Approval The IETF LLC board is then asked to approve the venue location based on a detailed confidential information pack. ## Step 6 - Contracting Once the IETF LLC board has approved a venue, the final contracts are agreed and signed. ## Step 7 - Community Notification Once the contracts are signed and we are committed to the
Upcoming NomCom Office Hours
Hi IETFers, I've posted the upcoming NomCom office hours on our datatracker site (https://datatracker.ietf.org/nomcom/2020/). We've scheduled 4 hours over the next 3 weeks: Wednesday, November 4, 11:00-12:00 UTC: https://ietf.webex.com/ietf/j.php?MTID=m86a62d9313e37208dde9312ecad0b1ac Thursday, November 5, 21:00-22:00 UTC: https://ietf.webex.com/ietf/j.php?MTID=m30d820c911458b39cfe276093caf576f Tuesday, November 10, 16:00-17:00 UTC: https://ietf.webex.com/ietf/j.php?MTID=m9dae586c1f719cfca27baa181550cec4 Wednesday, November 11, 18:00-19:00 UTC: https://ietf.webex.com/ietf/j.php?MTID=m8a8c660c26bd9f55e625da37bab6b006 If these don't suit you and you need to chat, let me know and we can schedule something. We've been receiving some excellent and thoughtful feedback on our site at https://datatracker.ietf.org/nomcom/2020/feedback/. In addition to nominee-specific feedback, we can accept input on "Topics" at the bottom of that page. There exist Topics for general feedback on all the I* groups, if you want to provide that sort of input. We've scheduled interviews for all the nominees over the next 3 weeks (mostly the 2 weeks before IETF 109). So we're on track to meet our timeline and expecting to deliver some excellent candidate slates to confirming bodies after we complete deliberations. If you have any questions about NomCom, please feel free to contact me. If you have questions on anything else, please don't bother me. I've got no time for anything else. ;) Barbara NomCom 2020 Chair ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
Protocol Action: 'Synonymous Flow Label Framework' to Proposed Standard (draft-ietf-mpls-sfl-framework-11.txt)
The IESG has approved the following document: - 'Synonymous Flow Label Framework' (draft-ietf-mpls-sfl-framework-11.txt) as Proposed Standard This document is the product of the Multiprotocol Label Switching Working Group. The IESG contact persons are Alvaro Retana, Martin Vigoureux and Deborah Brungard. A URL of this Internet Draft is: https://datatracker.ietf.org/doc/draft-ietf-mpls-sfl-framework/ Technical Summary RFC 8372 (MPLS Flow Identification Considerations) describes the requirement for introducing flow identities within the MPLS architecture. This document describes a method of accomplishing this by using a technique called Synonymous Flow Labels in which labels which mimic the behaviour of other labels provide the identification service. These identifiers can be used to trigger per-flow operations on the packet at the receiving label switching router. Working Group Summary The Working Group has reached consensus that this document is useful and should be published This document went through multiple reviews within the working group over the course of its development. The techniques defined in this document are useful in several applications, such as the measurement of the number of received packets in a flow for performance monitoring, triggering IPFIX inspection, triggering other types of Deep Packet Inspection, or identification of the packet source. Document Quality Review was done by MPLS review-team (MPLS-RT) and from several members of the WG. All comments have been addressed, and there are currently no open issues. Personnel Who is the Document Shepherd for this document? Tarek Saad Who is the Responsible Area Director? Deborah Brungard ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
2020 IANA Annual Engagement Survey
Dear IETF community, Help IANA evolve their engagement. As a valued customer, your opinion matters. We have revamped the IANA annual engagement survey using the feedback received last year. We also want to share our findings with you. As a thank you for taking part, you will receive a complimentary summary of our findings and outcomes. WHAT NEXT? Please use this link to take part: https://surveys6.jibunu.com/EchoResearch_0002/index.aspx?l=2=uvh3 [surveys6.jibunu.com] ABOUT THE SURVEY It only takes up 5 minutes to complete Conducted by Echo Research, an independent market research company, on behalf of the IANA services provider PTI (an affiliate of ICANN). Data confidentiality assured Echo Research is committed to protecting the confidentiality of all respondents, and in doing so will follow GDPR guidelines as detailed by EFAMRO, the European Research Federation, written for market research members of ESOMAR world research, and The Market Research Society (MRS). If you have any questions about the survey, please contact Marilia Hirano at: marilia.hir...@iana.org Thank you very much for your time, Michelle Cotton on behalf of our vendor, Ruth David Senior Account Executive Echo Research ruth.da...@echoresearch.com www.echoresearch.com smime.p7s Description: S/MIME cryptographic signature ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
Last Call: (An Information Model for Firmware Updates in IoT Devices) to Informational RFC
The IESG has received a request from the Software Updates for Internet of Things WG (suit) to consider the following document: - 'An Information Model for Firmware Updates in IoT Devices' as Informational RFC The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the last-c...@ietf.org mailing lists by 2020-11-11. Exceptionally, comments may be sent to i...@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract Vulnerabilities with Internet of Things (IoT) devices have raised the need for a reliable and secure firmware update mechanism that is also suitable for constrained devices. Ensuring that devices function and remain secure over their service life requires such an update mechanism to fix vulnerabilities, to update configuration settings, as well as adding new functionality. One component of such a firmware update is a concise and machine- processable meta-data document, or manifest, that describes the firmware image(s) and offers appropriate protection. This document describes the information that must be present in the manifest. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-suit-information-model/ No IPR declarations have been submitted directly on this I-D. ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
Concise Binary Object Representation Maintenance and Extensions (cbor) WG Virtual Meeting: 2020-10-28 CHANGED
MEETING DETAILS HAVE CHANGED. SEE LATEST DETAILS BELOW. The Concise Binary Object Representation Maintenance and Extensions (cbor) WG will hold a virtual interim meeting on 2020-10-28 from 17:00 to 18:00 Europe/Paris (16:00 to 17:00 UTC). Agenda: CBOR WG Meeting - Interim 20-18 Wednesday, Oct 28, 2020, 17:00 - 18:00 CET Chairs: Francesca Palombini Webex: https://ietf.webex.com/ietf/j.php?MTID=m8abc7d12fe6aaeb2c84fe10148a4b4f9 Meeting number: 161 827 6159 Password: h7MeKJEqj68 Jabber: c...@jabber.ietf.org Minutes: https://codimd.ietf.org/notes-ietf-interim-2020-cbor-18-cbor Agenda: * WG update * WG documents status - OID tags - new proposal dictionaries * AoB Information about remote participation: https://ietf.webex.com/ietf/j.php?MTID=m8abc7d12fe6aaeb2c84fe10148a4b4f9 Meeting number: 161 827 6159 Password: h7MeKJEqj68 ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
