Second (of three) NomCom 2021-2022 Call for Volunteers
This is the second (of three) call for volunteers for the 2021-2022 NomCom. I wanted to mention a few updates from the previous email (sent 2 weeks ago): - Unlike previous IETFs (e.g., IETF 108 a year ago) for IETF 111 the registration form does not (yet) include a checkbox that will let you volunteer (instead of emailing me). - However, the email can be a very short 3 line message (see below). - Thanks to everyone who has volunteered so far. However, we currently only have 56 volunteers. We need many more. So, please, please volunteer. The IETF NomCom appoints people to fill the open slots on the IETF LLC, IETF Trust, the IAB, and the IESG. Ten voting members for the NomCom are selected in a verifiably random way from a pool of volunteers. The more volunteers, the better chance we have of choosing a random yet representative cross section of the IETF population. The details of the operation of the NomCom can be found in BCP 10 (RFC 8713). RFC 3797 details the selection algorithm. Special for this year RFC 8989 (one-off update to RFC 8713 / BCP 10) tells us who is eligible to volunteer as anyone who satisfies any of the three following conditions: Path 1: The person has attended 3 out of the last 5 IETF meetings, including meetings held entirely online. For the 2021-2022 NomCom, the meetings concerned will be IETF 106, 107, 108, 109, and 110 Path 2: The person has been a Working Group Chair or Secretary within the 3 years prior to the day the first call for NomCom volunteers is sent to the community Path 3: The person has been a listed author or editor (on the front page) of at least two IETF Stream RFCs within the last 5 years prior to the day the call for NomCom volunteers is sent to the community. An Internet-Draft that has been approved by the IESG and is in the RFC Editor queue counts the same as a published RFC, with the relevant date being the date the draft was added to the RFC Editor queue. [Normative details are in RFC8989.] You can check your eligibility at: https://datatracker.ietf.org/accounts/profile/ (after logging in, you will see your eligibility displayed in the field "Nomcom Eligible"). If you qualify, please volunteer as explained below. However, please remember that anyone appointed to this NomCom will not be considered as a candidate for any of the positions that the 2021-2022 NomCom is responsible for filling. Details of Positions to Be Filled (some details to be finalized) An asterisk (*) next to a person's name indicates they do not intend to accept renomination. LLC Board (3-year term) • Jason Livingood IETF Trust (3-year term) • Kathleen Moriarty IAB (2-year term) • Ben Campbell • Cullen Jennings • Mirja Kühlewind • Jared Mauch • Tommy Pauly • Jiankang Yao IESG (2-year term) • Murray Kucherawy, ART AD • Erik Kline, INT AD • Robert Wilton, OPS AD • Martin Vigoureux, RTG AD • Benjamin Kaduk, SEC AD * • Martin Duke, TSV AD The primary activity for this NomCom will begin in July 2021 and should be completed by January 2022. The NomCom will have regularly scheduled conference calls to ensure progress. There will be activities to collect requirements from the community, review candidate questionnaires, review feedback from community members about candidates, and talk to candidates. While being a NomCom member does require some time commitment it is also a very rewarding experience. As a member of the NomCom it is very important that you be willing and able to attend meetings either remotely or in-person during IETF 112 (Madrid 6-12 November 2021) to conduct interviews. Remote attendance will be supported whether or not there are in-person meetings. Orientation and setting of the NomCom schedule will be done by videoconference during the week 26-30 July (exact time and date to be determined after NomCom membership is finalized on July 15), prior to IETF 111. Please volunteer by sending me an email before 23:59 UTC on Wednesday June 23, 2021, as follows: To: nomcom-chair-2...@ietf.org Subject: NomCom 2021-22 Volunteer Please include the following information in the email body: Your Full Name: // as you write it on the IETF registration form Current Primary Affiliation: // Typically what goes in the Company field // in the IETF Registration Form Emails: // Email addresses used to register for the past 5 IETF meetings // Preferred email address first You should expect an email response from me within 5 business days stating whether or not you are qualified. If you don't receive this response, please re-send your email with the tag "RESEND"" added to the subject line. If you are not yet sure if you would like to volunteer, please consider that NomCom members play a very important role in shaping the leadership of the IETF. Questions by email or voice are welcome.
RFC 9015 on BGP Control Plane for the Network Service Header in Service Function Chaining
A new Request for Comments is now available in online RFC libraries. RFC 9015 Title: BGP Control Plane for the Network Service Header in Service Function Chaining Author: A. Farrel, J. Drake, E. Rosen, J. Uttaro, L. Jalil Status: Standards Track Stream: IETF Date: June 2021 Mailbox:adr...@olddog.co.uk, jdr...@juniper.net, erose...@gmail.com, ju1...@att.com, luay.ja...@verizon.com Pages: 59 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-bess-nsh-bgp-control-plane-18.txt URL:https://www.rfc-editor.org/info/rfc9015 DOI:10.17487/RFC9015 This document describes the use of BGP as a control plane for networks that support service function chaining. The document introduces a new BGP address family called the "Service Function Chain (SFC) Address Family Identifier / Subsequent Address Family Identifier" (SFC AFI/SAFI) with two Route Types. One Route Type is originated by a node to advertise that it hosts a particular instance of a specified service function. This Route Type also provides "instructions" on how to send a packet to the hosting node in a way that indicates that the service function has to be applied to the packet. The other Route Type is used by a controller to advertise the paths of "chains" of service functions and give a unique designator to each such path so that they can be used in conjunction with the Network Service Header (NSH) defined in RFC 8300. This document adopts the service function chaining architecture described in RFC 7665. This document is a product of the BGP Enabled Services Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. 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
RFC 9045 on Algorithm Requirements Update to the Internet X.509 Public Key Infrastructure Certificate Request Message Format (CRMF)
A new Request for Comments is now available in online RFC libraries. RFC 9045 Title: Algorithm Requirements Update to the Internet X.509 Public Key Infrastructure Certificate Request Message Format (CRMF) Author: R. Housley Status: Standards Track Stream: IETF Date: June 2021 Mailbox:hous...@vigilsec.com Pages: 9 Updates:RFC 4211 I-D Tag:draft-ietf-lamps-crmf-update-algs-07.txt URL:https://www.rfc-editor.org/info/rfc9045 DOI:10.17487/RFC9045 This document updates the cryptographic algorithm requirements for the Password-Based Message Authentication Code in the Internet X.509 Public Key Infrastructure Certificate Request Message Format (CRMF) specified in RFC 4211. This document is a product of the Limited Additional Mechanisms for PKIX and SMIME Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. 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
RFC 9044 on Using the AES-GMAC Algorithm with the Cryptographic Message Syntax (CMS)
A new Request for Comments is now available in online RFC libraries. RFC 9044 Title: Using the AES-GMAC Algorithm with the Cryptographic Message Syntax (CMS) Author: R. Housley Status: Standards Track Stream: IETF Date: June 2021 Mailbox:hous...@vigilsec.com Pages: 9 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-lamps-cms-aes-gmac-alg-05.txt URL:https://www.rfc-editor.org/info/rfc9044 DOI:10.17487/RFC9044 This document specifies the conventions for using the AES-GMAC Message Authentication Code algorithm with the Cryptographic Message Syntax (CMS) as specified in RFC 5652. This document is a product of the Limited Additional Mechanisms for PKIX and SMIME Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. 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
RFC 9029 on Updates to the Allocation Policy for the Border Gateway Protocol - Link State (BGP-LS) Parameters Registries
A new Request for Comments is now available in online RFC libraries. RFC 9029 Title: Updates to the Allocation Policy for the Border Gateway Protocol - Link State (BGP-LS) Parameters Registries Author: A. Farrel Status: Standards Track Stream: IETF Date: June 2021 Mailbox:adr...@olddog.co.uk Pages: 5 Updates:RFC 7752 I-D Tag:draft-ietf-idr-bgp-ls-registry-06.txt URL:https://www.rfc-editor.org/info/rfc9029 DOI:10.17487/RFC9029 RFC 7752 defines the Border Gateway Protocol - Link State (BGP-LS). IANA created a registry consistent with that document called "Border Gateway Protocol - Link State (BGP-LS) Parameters" with a number of subregistries. The allocation policy applied by IANA for those registries is "Specification Required", as defined in RFC 8126. This document updates RFC 7752 by changing the allocation policy for all of the registries to "Expert Review" and by updating the guidance to the designated experts. This document is a product of the Inter-Domain Routing Working Group of the IETF. This is now a Proposed Standard. STANDARDS TRACK: This document specifies an Internet Standards Track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the Official Internet Protocol Standards (https://www.rfc-editor.org/standards) for the standardization state and status of this protocol. 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
RFC 9023 on Deterministic Networking (DetNet) Data Plane: IP over IEEE 802.1 Time-Sensitive Networking (TSN)
A new Request for Comments is now available in online RFC libraries. RFC 9023 Title: Deterministic Networking (DetNet) Data Plane: IP over IEEE 802.1 Time-Sensitive Networking (TSN) Author: B. Varga, Ed., J. Farkas, A. Malis, S. Bryant Status: Informational Stream: IETF Date: June 2021 Mailbox:balazs.a.va...@ericsson.com, janos.far...@ericsson.com, agma...@gmail.com, s...@stewartbryant.com Pages: 10 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-detnet-ip-over-tsn-07.txt URL:https://www.rfc-editor.org/info/rfc9023 DOI:10.17487/RFC9023 This document specifies the Deterministic Networking IP data plane when operating over a Time-Sensitive Networking (TSN) sub-network. This document does not define new procedures or processes. Whenever this document makes statements or recommendations, these are taken from normative text in the referenced RFCs. This document is a product of the Deterministic Networking Working Group of the IETF. 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 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
