Re: Feedback: Proposed IESG Statement on Restricting Access
On 2022-10-11, at 14:58, IETF Chair wrote: > Based on the IETF LLC consultation on restricting participant access to IETF > systems [1], the IESG has reviewed the draft policy produced by the IETF LLC. > Implementation of this policy would take the form of publishing an IESG > statement. The text of this proposed IESG statement is included below. > > The IESG plans to make a decision in the next few weeks, and solicits final > comments on this statement. Please send substantive comments to the IESG at > i...@ietf.org by 2022-11-25. Thank you for the feedback on the proposed statement. We've tried to take what we've received into account and revised the proposed text (see below.) I'm also attaching a diff to make the changes easier to spot. Please send additional feedback by 2022-11-25. Lars Eggert IETF Chair, on behalf of the IESG -- Statement on Restricting Access (Draft) In discussions with IETF counsel, a number of potential circumstances have been identified under which the IESG should, after having been advised by counsel, restrict an individual from using IETF IT systems and/or from participating in IETF meetings, as not doing so would expose the IETF to serious legal risk. The IESG expects that it will follow the advice of counsel and restrict access and/or restrict participation of an individual. The IESG intends to only take such drastic actions in response to legal advice by counsel, and not for other reasons. It is expected that this advice will only be received after all other reasonable attempts to address the issue, if any are possible, have been exhausted. The IESG publishes this statement to set out in advance the principles and procedural guidelines it will follow in taking such an action. The circumstances currently identified under which such legal advice may be provided are as follows. This is not an exhaustive list and this statement will apply under any circumstance where legal advice of this nature is received: 1. When ordered to do so by a court that has jurisdiction over the IETF LLC. 2. If an individual concerned is using those systems or meetings to threaten or otherwise seriously harass someone. 3. If an individual repeatedly shares copyrighted material – through IETF IT systems or at IETF meetings – that they do not have authority to share. The principles that the IESG will aim to maintain from the outset are as follows. These principles are listed in order of priority and where a conflict between them arises, the higher priority principle will take precedence: 1. To comply with the law and mitigate any serious legal risk to the IETF. 2. To preserve, as far as is possible, the integrity and openness of the standards process. 3. To preserve the current approach to identity for IETF engagement, noting that this varies according to context from anonymous (e.g., accessing RFCs), to pseudonymous (e.g., contributing to a mailing list), to identity verified (e.g., as a board member of the IETF LLC). 4. To only act as necessary to mitigate the serious legal risk and to avoid any over-reach. 5. To be fully transparent with the IETF community about the action taken, the reasons why, and who is affected. Some examples of a conflict between the principles are: * Where a court order instructs us to keep an action secret. * Where identifying an individual being acted against is considered likely to lead to an escalation of their behavior of harassment. The following procedural guidelines will be used when action is taken, unless overridden by the principles above: 1. The IESG will consult with other parts of the IETF as needed, including the Ombudsteam, the IRTF Chair, IETF LLC or any affected participants. 2. If the identity of an individual is reasonably well established, then the restriction will be against the individual, but if it is not, the restriction will be limited to their identifiers (e.g., usernames or email addresses). 3. If the restriction can reasonably be limited to one or more IT systems and/or forms of participation, then it will be, unless there is an expectation that broader restrictions will inevitably be required. 4. An individual will be notified of the IESG action by counsel and is expected to only correspond with counsel, not the IESG or others, on this matter. 5. An action will be announced to the ietf-announce mailing list and a public record will be kept on the IETF website. In addition, in order to ensure that the IETF is protected by the Safe Harbor regime of the US DMCA, the IETF website will include a page with the following warning alongside the specific contact information required by the DMCA: The IETF reserves the right to terminate the use of IETF IT systems by IETF participants who violate the law by repeat copyright infringement. For full details, see the IESG Statement on Restricting Access. [link to be added]. Title: Diff: old.txt - DRAFT - Statement on Restricting Acce
REMINDER: IETF 115 Hotel Room Block and Standard Registration Deadlines Approaching
IETF 115 London and online November 5-11, 2022 Hosted by Cisco 1. Registration 2. Reservations 3. Fee Waivers 4. Child Care 5. IETF 115 Meeting T-Shirts 6. Hackathon 7. Social Event 1. Standard Registration Deadline: The Standard deadline for registration is Monday, October 24th, UTC 23:59. Be sure to register before the deadline passes! Register online at: https://registration.ietf.org/115/ Standard Registration Full Week Rates: Onsite Standard Registration: USD 875 + VAT, if paid in full prior to 23:59 UTC 2022-10-24 Remote Standard Registration: USD 375, if paid in full prior to 23:59 UTC 2022-10-24 NOTE: Payment is required at the time of registration. The Standard registration fee is available until Monday, October 24th at UTC 23:59. After Monday at UTC 23:59, the registration fees will increase. Registration types and fee tiers are available at https://registration.ietf.org/115/ If you require any further information or assistance with registration then please feel free to contact us at supp...@ietf.org. 2. Reservations & Hotel Room Block Ending: The IETF 115 meeting venue is the Hilton London Metropole. As explained in the FAQ, you will need to register before you can reserve a guest room at the venue. A link to reserve a guest room will be sent to you after you register. The IETF Room Rate ends Saturday, 2022-10-22. Guests booking after this date will be subject to an increased nightly rate. https://www.ietf.org/how/meetings/115/faq/ 3. Fee Waivers for Remote Participants: We understand that not everyone can afford the IETF 115 remote registration fee for a variety of reasons, including issues with income, employment status and employer support, and we do not want any of these to be a barrier to participation. If you cannot afford the remote registration fee, then please take this fee waiver option to ensure that you can participate: https://www.ietf.org/forms/115-registration-fee-waiver/. 4. Child Care: Thanks to the generous support of our Diversity & Inclusion Gold sponsors, Akamai, Cisco, and Huawei and Bronze sponsors Comcast, Identity Digital and Verisign, we will once again be offering onsite childcare at IETF 115 in London, UK. Childcare will be provided by Rose Event Nannies, a professional event childcare provider. This service is offered free of charge to registered IETF participants and initially provides space for up to ten children. We strongly encourage advance sign up to give us sufficient time to investigate adding more space if this service becomes fully booked. roseeventnannies.co.uk Please see the online FAQ for more information and a link to the form to sign up. Additional information regarding daily activities available upon request. https://www.ietf.org/how/meetings/115/childcare/ 5. IETF 115 Meeting T-Shirts: Thanks to the generosity of the IETF 115 meeting host, Cisco, registered participants, both onsite and remote, have the option to receive a free t-shirt with free delivery or collection onsite. Limited quantities are available on a first-come, first-served basis. 6. Hackathon: The IETF is holding a Hackathon to encourage developers to discuss, collaborate and develop utilities, ideas, sample code and solutions that show practical implementations of IETF standards. When: Saturday, November 5, 2022 through Sunday, November 6, 2022 Signup for the Hackathon Onsite: https://registration.ietf.org/115/new/hackathon_onsite/ Signup for the Hackathon Remote: https://registration.ietf.org/115/new/hackathon_remote/ More information can be found here: https://www.ietf.org/how/runningcode/hackathons/115-hackathon/ Keep up to date by subscribing to: https://www.ietf.org/mailman/listinfo/hackathon The Hackathon is free to attend and open to all. Extend the invitation to colleagues outside the IETF! Descriptions and information regarding the technologies for the hackathon are located on the IETF 115 Meeting Wiki: https://wiki.ietf.org/en/meeting/115/hackathon Don’t see anything that interests you? Feel free to add your preferred technology to the list, sign up as its Champion and show up to work on it. Note: you must login to the wiki to add content. If you do add a new technology, we strongly suggest that you send an email to hackat...@ietf.org to let others know. You may generate interest in your technology, and find other people who want to contribute to it. 7. Social Event: Participants will have the opportunity to attend a unique social event on Tuesday, Nov 8th, hosted by Cisco. A limited amount of tickets are available, so be sure to register before they’re gone. Additional information regarding the social event can be found via our Social Event Page: https://www.ietf.org/how/meetings/115/social/ ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
REMINDER: IETF 115 Hotel Room Block and Standard Registration Deadlines Approaching
IETF 115 London and online November 5-11, 2022 Hosted by Cisco 1. Registration 2. Reservations 3. Fee Waivers 4. Child Care 5. IETF 115 Meeting T-Shirts 6. Hackathon 7. Social Event 1. Standard Registration Deadline: The Standard deadline for registration is Monday, October 24th, UTC 23:59. Be sure to register before the deadline passes! Register online at: https://registration.ietf.org/115/ Standard Registration Full Week Rates: Onsite Standard Registration: USD 875 + VAT, if paid in full prior to 23:59 UTC 2022-10-24 Remote Standard Registration: USD 375, if paid in full prior to 23:59 UTC 2022-10-24 NOTE: Payment is required at the time of registration. The Standard registration fee is available until Monday, October 24th at UTC 23:59. After Monday at UTC 23:59, the registration fees will increase. Registration types and fee tiers are available at https://registration.ietf.org/115/ If you require any further information or assistance with registration then please feel free to contact us at supp...@ietf.org. 2. Reservations & Hotel Room Block Ending: The IETF 115 meeting venue is the Hilton London Metropole. As explained in the FAQ, you will need to register before you can reserve a guest room at the venue. A link to reserve a guest room will be sent to you after you register. The IETF Room Rate ends Saturday, 2022-10-22. Guests booking after this date will be subject to an increased nightly rate. https://www.ietf.org/how/meetings/115/faq/ 3. Fee Waivers for Remote Participants: We understand that not everyone can afford the IETF 115 remote registration fee for a variety of reasons, including issues with income, employment status and employer support, and we do not want any of these to be a barrier to participation. If you cannot afford the remote registration fee, then please take this fee waiver option to ensure that you can participate: https://www.ietf.org/forms/115-registration-fee-waiver/. 4. Child Care: Thanks to the generous support of our Diversity & Inclusion Gold sponsors, Akamai, Cisco, and Huawei and Bronze sponsors Comcast, Identity Digital and Verisign, we will once again be offering onsite childcare at IETF 115 in London, UK. Childcare will be provided by Rose Event Nannies, a professional event childcare provider. This service is offered free of charge to registered IETF participants and initially provides space for up to ten children. We strongly encourage advance sign up to give us sufficient time to investigate adding more space if this service becomes fully booked. roseeventnannies.co.uk Please see the online FAQ for more information and a link to the form to sign up. Additional information regarding daily activities available upon request. https://www.ietf.org/how/meetings/115/childcare/ 5. IETF 115 Meeting T-Shirts: Thanks to the generosity of the IETF 115 meeting host, Cisco, registered participants, both onsite and remote, have the option to receive a free t-shirt with free delivery or collection onsite. Limited quantities are available on a first-come, first-served basis. 6. Hackathon: The IETF is holding a Hackathon to encourage developers to discuss, collaborate and develop utilities, ideas, sample code and solutions that show practical implementations of IETF standards. When: Saturday, November 5, 2022 through Sunday, November 6, 2022 Signup for the Hackathon Onsite: https://registration.ietf.org/115/new/hackathon_onsite/ Signup for the Hackathon Remote: https://registration.ietf.org/115/new/hackathon_remote/ More information can be found here: https://www.ietf.org/how/runningcode/hackathons/115-hackathon/ Keep up to date by subscribing to: https://www.ietf.org/mailman/listinfo/hackathon The Hackathon is free to attend and open to all. Extend the invitation to colleagues outside the IETF! Descriptions and information regarding the technologies for the hackathon are located on the IETF 115 Meeting Wiki: https://wiki.ietf.org/en/meeting/115/hackathon Don’t see anything that interests you? Feel free to add your preferred technology to the list, sign up as its Champion and show up to work on it. Note: you must login to the wiki to add content. If you do add a new technology, we strongly suggest that you send an email to hackat...@ietf.org to let others know. You may generate interest in your technology, and find other people who want to contribute to it. 7. Social Event: Participants will have the opportunity to attend a unique social event on Tuesday, Nov 8th, hosted by Cisco. A limited amount of tickets are available, so be sure to register before they’re gone. Additional information regarding the social event can be found via our Social Event Page: https://www.ietf.org/how/meetings/115/social/ ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
Protocol Action: 'Definitions of Managed Objects for IP Traffic Flow Security' to Proposed Standard (draft-ietf-ipsecme-mib-iptfs-11.txt)
The IESG has approved the following document: - 'Definitions of Managed Objects for IP Traffic Flow Security' (draft-ietf-ipsecme-mib-iptfs-11.txt) as Proposed Standard This document is the product of the IP Security Maintenance and Extensions Working Group. The IESG contact persons are Paul Wouters and Roman Danyliw. A URL of this Internet Draft is: https://datatracker.ietf.org/doc/draft-ietf-ipsecme-mib-iptfs/ Technical Summary This document describes managed objects for the management of IP Traffic Flow Security additions to IKEv2 and IPsec. This document provides a read only version of the objects defined in the YANG module for the same purpose. Working Group Summary This document has been presented and discussed on list. No objections to this work have been raised. Document Quality This document is an SNMP MIB model definition and is derived from the YANG model defined in draft-ietf-ipsecme-yang-iptfs. Personnel * Document Shepherd: Tero Kivinen. * Responsible Area Director: Roman Danyliw ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC 9316 on Intent Classification
A new Request for Comments is now available in online RFC libraries. RFC 9316 Title: Intent Classification Author: C. Li, O. Havel, A. Olariu, P. Martinez-Julia, J. Nobre, D. Lopez Status: Informational Stream: IRTF Date: October 2022 Mailbox:lich...@chinatelecom.cn, olga.ha...@huawei.com, adriana.ola...@huawei.com, pe...@nict.go.jp, jcno...@inf.ufrgs.br, diego.r.lo...@telefonica.com Pages: 35 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-irtf-nmrg-ibn-intent-classification-08.txt URL:https://www.rfc-editor.org/info/rfc9316 DOI:10.17487/RFC9316 Intent is an abstract, high-level policy used to operate a network. An intent-based management system includes an interface for users to input requests and an engine to translate the intents into the network configuration and manage their life cycle. This document mostly discusses the concept of network intents, but other types of intents are also considered. Specifically, this document highlights stakeholder perspectives of intent, methods to classify and encode intent, and the associated intent taxonomy; it also defines relevant intent terms where necessary, provides a foundation for intent-related research, and facilitates solution development. This document is a product of the IRTF Network Management Research Group (NMRG). This document is a product of the Network Management Research Group of the IRTF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce, rfc-dist and IRTF-Announce lists.To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist https://www.irtf.org/mailman/listinfo/irtf-announce For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
BCP 185, RFC 9319 on The Use of maxLength in the Resource Public Key Infrastructure (RPKI)
A new Request for Comments is now available in online RFC libraries. BCP 185 RFC 9319 Title: The Use of maxLength in the Resource Public Key Infrastructure (RPKI) Author: Y. Gilad, S. Goldberg, K. Sriram, J. Snijders, B. Maddison Status: Best Current Practice Stream: IETF Date: October 2022 Mailbox:yoss...@cs.huji.ac.il, gol...@cs.bu.edu, kotikalapudi.sri...@nist.gov, j...@fastly.com, benm@workonline.africa Pages: 13 See Also: BCP 185 I-D Tag:draft-ietf-sidrops-rpkimaxlen-15.txt URL:https://www.rfc-editor.org/info/rfc9319 DOI:10.17487/RFC9319 This document recommends ways to reduce the forged-origin hijack attack surface by prudently limiting the set of IP prefixes that are included in a Route Origin Authorization (ROA). One recommendation is to avoid using the maxLength attribute in ROAs except in some specific cases. The recommendations complement and extend those in RFC 7115. This document also discusses the creation of ROAs for facilitating the use of Distributed Denial of Service (DDoS) mitigation services. Considerations related to ROAs and RPKI-based Route Origin Validation (RPKI-ROV) in the context of destination-based Remotely Triggered Discard Route (RTDR) (elsewhere referred to as "Remotely Triggered Black Hole") filtering are also highlighted. This document is a product of the SIDR Operations Working Group of the IETF. BCP: This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see https://www.ietf.org/mailman/listinfo/ietf-announce https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see https://www.rfc-editor.org/search For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk Requests for special distribution should be addressed to either the author of the RFC in question, or to rfc-edi...@rfc-editor.org. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. The RFC Editor Team Association Management Solutions, LLC ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
