NomCom 2022 Announcement of IETF Trust Selection
As Chair of the 2022-2023 NomCom, I am pleased to announce that Glenn Deen Has been selected and confirmed for the IETF Trust open position. The full list of trustees, and their term of office, can be found at https://trustee.ietf.org/about/trustees/. I wish to thank all of the other nominees and the IETF community for the feedback they provided. -Rich Salz, 2022-2023 IETF NomCom Chair ___ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce
RFC 9333 on Minimal IP Encapsulating Security Payload (ESP)
A new Request for Comments is now available in online RFC libraries. RFC 9333 Title: Minimal IP Encapsulating Security Payload (ESP) Author: D. Migault, T. Guggemos Status: Informational Stream: IETF Date: January 2023 Mailbox:daniel.miga...@ericsson.com, gugge...@mnm-team.org Pages: 13 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-lwig-minimal-esp-12.txt URL:https://www.rfc-editor.org/info/rfc9333 DOI:10.17487/RFC9333 This document describes the minimal properties that an IP Encapsulating Security Payload (ESP) implementation needs to meet to remain interoperable with the standard ESP as defined in RFC 4303. Such a minimal version of ESP is not intended to become a replacement of ESP in RFC 4303. Instead, a minimal implementation is expected to be optimized for constrained environments while remaining interoperable with implementations of ESP. In addition, this document provides some considerations for implementing minimal ESP in a constrained environment, such as limiting the number of flash writes, handling frequent wakeup and sleep states, limiting wakeup time, and reducing the use of random generation. This document does not update or modify RFC 4303. It provides a compact description of how to implement the minimal version of that protocol. RFC 4303 remains the authoritative description. This document is a product of the Light-Weight Implementation Guidance 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
Last Call: (TLS-based EAP types and TLS 1.3) to Proposed Standard
The IESG has received a request from the EAP Method Update WG (emu) to consider the following document: - 'TLS-based EAP types and TLS 1.3' as Proposed Standard 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 2023-01-27. 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 EAP-TLS (RFC 5216) has been updated for TLS 1.3 in RFC 9190. Many other EAP types also depend on TLS, such as EAP-FAST (RFC 4851), EAP- TTLS (RFC 5281), TEAP (RFC 7170), and possibly many vendor specific EAP methods. This document updates those methods in order to use the new key derivation methods available in TLS 1.3. Additional changes necessitated by TLS 1.3 are also discussed. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-emu-tls-eap-types/ 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
RFC 9334 on Remote ATtestation procedureS (RATS) Architecture
A new Request for Comments is now available in online RFC libraries. RFC 9334 Title: Remote ATtestation procedureS (RATS) Architecture Author: H. Birkholz, D. Thaler, M. Richardson, N. Smith, W. Pan Status: Informational Stream: IETF Date: January 2023 Mailbox:henk.birkh...@sit.fraunhofer.de, dtha...@microsoft.com, mcr+i...@sandelman.ca, ned.sm...@intel.com, william.pan...@huawei.com Pages: 46 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-rats-architecture-22.txt URL:https://www.rfc-editor.org/info/rfc9334 DOI:10.17487/RFC9334 In network protocol exchanges, it is often useful for one end of a communication to know whether the other end is in an intended operating state. This document provides an architectural overview of the entities involved that make such tests possible through the process of generating, conveying, and evaluating evidentiary Claims. It provides a model that is neutral toward processor architectures, the content of Claims, and protocols. This document is a product of the Remote ATtestation ProcedureS 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
RFC 9353 on IGP Extension for Path Computation Element Communication Protocol (PCEP) Security Capability Support in PCE Discovery (PCED)
A new Request for Comments is now available in online RFC libraries. RFC 9353 Title: IGP Extension for Path Computation Element Communication Protocol (PCEP) Security Capability Support in PCE Discovery (PCED) Author: D. Lopez, Q. Wu, D. Dhody, Q. Ma, D. King Status: Standards Track Stream: IETF Date: January 2023 Mailbox:diego.r.lo...@telefonica.com, bill...@huawei.com, dhruv.i...@gmail.com, maqiufa...@huawei.com, dan...@olddog.co.uk Pages: 13 Updates:RFC 5088, RFC 5089, RFC 8231, RFC 8306 I-D Tag:draft-ietf-lsr-pce-discovery-security-support-13.txt URL:https://www.rfc-editor.org/info/rfc9353 DOI:10.17487/RFC9353 When a Path Computation Element (PCE) is a Label Switching Router (LSR) or a server participating in the Interior Gateway Protocol (IGP), its presence and path computation capabilities can be advertised using IGP flooding. The IGP extensions for PCE Discovery (PCED) (RFCs 5088 and 5089) define a method to advertise path computation capabilities using IGP flooding for OSPF and IS-IS, respectively. However, these specifications lack a method to advertise Path Computation Element Communication Protocol (PCEP) security (e.g., Transport Layer Security (TLS) and TCP Authentication Option (TCP-AO)) support capability. This document defines capability flag bits for the PCE-CAP-FLAGS sub-TLV that can be announced as an attribute in the IGP advertisement to distribute PCEP security support information. In addition, this document updates RFCs 5088 and 5089 to allow advertisement of a Key ID or KEY-CHAIN-NAME sub-TLV to support TCP-AO security capability. This document also updates RFCs 8231 and 8306. This document is a product of the Link State 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 9354 on Transmission of IPv6 Packets over Power Line Communication (PLC) Networks
A new Request for Comments is now available in online RFC libraries. RFC 9354 Title: Transmission of IPv6 Packets over Power Line Communication (PLC) Networks Author: J. Hou, B. Liu, Y-G. Hong, X. Tang, C. Perkins Status: Standards Track Stream: IETF Date: January 2023 Mailbox:houjianqi...@huawei.com, remy.liub...@huawei.com, yonggeun.h...@gmail.com, i...@sgepri.sgcc.com.cn, charl...@computer.org Pages: 20 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-6lo-plc-11.txt URL:https://www.rfc-editor.org/info/rfc9354 DOI:10.17487/RFC9354 Power Line Communication (PLC), namely using electric power lines for indoor and outdoor communications, has been widely applied to support Advanced Metering Infrastructure (AMI), especially smart meters for electricity. The existing electricity infrastructure facilitates the expansion of PLC deployments due to its potential advantages in terms of cost and convenience. Moreover, a wide variety of accessible devices raises the potential demand of IPv6 for future applications. This document describes how IPv6 packets are transported over constrained PLC networks, such as those described in ITU-T G.9903, IEEE 1901.1, and IEEE 1901.2. This document is a product of the IPv6 over Networks of Resource-constrained Nodes 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
