RFC 9603 on Path Computation Element Communication Protocol (PCEP) Extensions for IPv6 Segment Routing
A new Request for Comments is now available in online RFC libraries. RFC 9603 Title: Path Computation Element Communication Protocol (PCEP) Extensions for IPv6 Segment Routing Author: C. Li, Ed., P. Kaladharan, S. Sivabalan, M. Koldychev, Y. Zhu Status: Standards Track Stream: IETF Date: July 2024 Mailbox:c...@huawei.com, preje...@rtbrick.com, msiva...@gmail.com, mkold...@cisco.com, zhu...@chinatelecom.cn Pages: 23 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-pce-segment-routing-ipv6-25.txt URL:https://www.rfc-editor.org/info/rfc9603 DOI:10.17487/RFC9603 Segment Routing (SR) can be used to steer packets through a network using the IPv6 or MPLS data plane, employing the source routing paradigm. An SR Path can be derived from a variety of mechanisms, including an IGP Shortest Path Tree (SPT), explicit configuration, or a Path Computation Element (PCE). Since SR can be applied to both MPLS and IPv6 data planes, a PCE should be able to compute an SR Path for both MPLS and IPv6 data planes. The Path Computation Element Communication Protocol (PCEP) extension and mechanisms to support SR-MPLS have been defined. This document outlines the necessary extensions to support SR for the IPv6 data plane within PCEP. This document is a product of the Path Computation Element 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 To unsubscribe send an email to ietf-announce-le...@ietf.org
RFC 9619 on In the DNS, QDCOUNT Is (Usually) One
A new Request for Comments is now available in online RFC libraries. RFC 9619 Title: In the DNS, QDCOUNT Is (Usually) One Author: R. Bellis, J. Abley Status: Standards Track Stream: IETF Date: July 2024 Mailbox:r...@isc.org, jab...@cloudflare.com Pages: 7 Updates:RFC 1035 I-D Tag:draft-ietf-dnsop-qdcount-is-one-04.txt URL:https://www.rfc-editor.org/info/rfc9619 DOI:10.17487/RFC9619 This document updates RFC 1035 by constraining the allowed value of the QDCOUNT parameter in DNS messages with OPCODE = 0 (QUERY) to a maximum of one, and it specifies the required behavior when values that are not allowed are encountered. This document is a product of the Domain Name System Operations 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 To unsubscribe send an email to ietf-announce-le...@ietf.org
RFC 9607 on RTP Payload Format for the Secure Communication Interoperability Protocol (SCIP) Codec
A new Request for Comments is now available in online RFC libraries. RFC 9607 Title: RTP Payload Format for the Secure Communication Interoperability Protocol (SCIP) Codec Author: D. Hanson, M. Faller, K. Maver Status: Standards Track Stream: IETF Date: July 2024 Mailbox:dan.han...@gd-ms.com, michael.fal...@gd-ms.com, keith.ma...@gd-ms.com Pages: 15 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-avtcore-rtp-scip-09.txt URL:https://www.rfc-editor.org/info/rfc9607 DOI:10.17487/RFC9607 This document describes the RTP payload format of the Secure Communication Interoperability Protocol (SCIP). SCIP is an application-layer protocol that provides end-to-end session establishment, payload encryption, packetization and de-packetization of media, and reliable transport. This document provides a globally available reference that can be used for the development of network equipment and procurement of services that support SCIP traffic. The intended audience is network security policymakers; network administrators, architects, and original equipment manufacturers (OEMs); procurement personnel; and government agency and commercial industry representatives. This document is a product of the Audio/Video Transport Core Maintenance 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 To unsubscribe send an email to ietf-announce-le...@ietf.org
RFC 9612 on Bidirectional Forwarding Detection (BFD) Reverse Path for MPLS Label Switched Paths (LSPs)
A new Request for Comments is now available in online RFC libraries. RFC 9612 Title: Bidirectional Forwarding Detection (BFD) Reverse Path for MPLS Label Switched Paths (LSPs) Author: G. Mirsky, J. Tantsura, I. Varlashkin, M. Chen Status: Experimental Stream: IETF Date: July 2024 Mailbox:gregimir...@gmail.com, jefftant.i...@gmail.com, i...@google.com, mach.c...@huawei.com Pages: 9 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-mpls-bfd-directed-31.txt URL:https://www.rfc-editor.org/info/rfc9612 DOI:10.17487/RFC9612 Bidirectional Forwarding Detection (BFD) is expected to be able to monitor a wide variety of encapsulations of paths between systems. When a BFD session monitors an explicitly routed unidirectional path, there may be a need to direct the egress BFD peer to use a specific path for the reverse direction of the BFD session. This document describes an extension to the MPLS Label Switched Path (LSP) echo request that allows a BFD system to request that the remote BFD peer transmit BFD control packets over the specified LSP. This document is a product of the Multiprotocol Label Switching Working Group of the IETF. EXPERIMENTAL: This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. 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 To unsubscribe send an email to ietf-announce-le...@ietf.org
RFC 9593 on Announcing Supported Authentication Methods in the Internet Key Exchange Protocol Version 2 (IKEv2)
A new Request for Comments is now available in online RFC libraries. RFC 9593 Title: Announcing Supported Authentication Methods in the Internet Key Exchange Protocol Version 2 (IKEv2) Author: V. Smyslov Status: Standards Track Stream: IETF Date: July 2024 Mailbox:s...@elvis.ru Pages: 13 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-ipsecme-ikev2-auth-announce-10.txt URL:https://www.rfc-editor.org/info/rfc9593 DOI:10.17487/RFC9593 This specification defines a mechanism that allows implementations of the Internet Key Exchange Protocol Version 2 (IKEv2) to indicate the list of supported authentication methods to their peers while establishing IKEv2 Security Associations (SAs). This mechanism improves interoperability when IKEv2 partners are configured with multiple credentials of different types for authenticating each other. This document is a product of the IP Security Maintenance and Extensions 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 To unsubscribe send an email to ietf-announce-le...@ietf.org
RFC 9611 on Internet Key Exchange Protocol Version 2 (IKEv2) Support for Per-Resource Child Security Associations (SAs)
A new Request for Comments is now available in online RFC libraries. RFC 9611 Title: Internet Key Exchange Protocol Version 2 (IKEv2) Support for Per-Resource Child Security Associations (SAs) Author: A. Antony, T. Brunner, S. Klassert, P. Wouters Status: Standards Track Stream: IETF Date: July 2024 Mailbox:antony.ant...@secunet.com, tob...@codelabs.ch, steffen.klass...@secunet.com, paul.wout...@aiven.io Pages: 9 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-ipsecme-multi-sa-performance-09.txt URL:https://www.rfc-editor.org/info/rfc9611 DOI:10.17487/RFC9611 In order to increase the bandwidth of IPsec traffic between peers, this document defines one Notify Message Status Types and one Notify Message Error Types payload for the Internet Key Exchange Protocol Version 2 (IKEv2) to support the negotiation of multiple Child Security Associations (SAs) with the same Traffic Selectors used on different resources, such as CPUs. The SA_RESOURCE_INFO notification is used to convey information that the negotiated Child SA and subsequent new Child SAs with the same Traffic Selectors are a logical group of Child SAs where most or all of the Child SAs are bound to a specific resource, such as a specific CPU. The TS_MAX_QUEUE notify conveys that the peer is unwilling to create more additional Child SAs for this particular negotiated Traffic Selector combination. Using multiple Child SAs with the same Traffic Selectors has the benefit that each resource holding the Child SA has its own Sequence Number Counter, ensuring that CPUs don't have to synchronize their cryptographic state or disable their packet replay protection. This document is a product of the IP Security Maintenance and Extensions 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 To unsubscribe send an email to ietf-announce-le...@ietf.org
RFC 9615 on Automatic DNSSEC Bootstrapping Using Authenticated Signals from the Zone's Operator
A new Request for Comments is now available in online RFC libraries. RFC 9615 Title: Automatic DNSSEC Bootstrapping Using Authenticated Signals from the Zone's Operator Author: P. Thomassen, N. Wisiol Status: Standards Track Stream: IETF Date: July 2024 Mailbox:pe...@desec.io, n...@desec.io Pages: 12 Updates:RFC 7344, RFC 8078 I-D Tag:draft-ietf-dnsop-dnssec-bootstrapping-11.txt URL:https://www.rfc-editor.org/info/rfc9615 DOI:10.17487/RFC9615 This document introduces an in-band method for DNS operators to publish arbitrary information about the zones for which they are authoritative, in an authenticated fashion and on a per-zone basis. The mechanism allows managed DNS operators to securely announce DNSSEC key parameters for zones under their management, including for zones that are not currently securely delegated. Whenever DS records are absent for a zone's delegation, this signal enables the parent's registry or registrar to cryptographically validate the CDS/CDNSKEY records found at the child's apex. The parent can then provision DS records for the delegation without resorting to out-of-band validation or weaker types of cross-checks such as "Accept after Delay". This document establishes the DS enrollment method described in Section 4 of this document as the preferred method over those from Section 3 of RFC 8078. It also updates RFC 7344. This document is a product of the Domain Name System Operations 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 To unsubscribe send an email to ietf-announce-le...@ietf.org
RFC 9591 on The Flexible Round-Optimized Schnorr Threshold (FROST) Protocol for Two-Round Schnorr Signatures
A new Request for Comments is now available in online RFC libraries. RFC 9591 Title: The Flexible Round-Optimized Schnorr Threshold (FROST) Protocol for Two-Round Schnorr Signatures Author: D. Connolly, C. Komlo, I. Goldberg, C. A. Wood Status: Informational Stream: IRTF Date: June 2024 Mailbox:durumcrustu...@gmail.com, cko...@uwaterloo.ca, i...@uwaterloo.ca, c...@heapingbits.net Pages: 47 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-irtf-cfrg-frost-15.txt URL:https://www.rfc-editor.org/info/rfc9591 DOI:10.17487/RFC9591 This document specifies the Flexible Round-Optimized Schnorr Threshold (FROST) signing protocol. FROST signatures can be issued after a threshold number of entities cooperate to compute a signature, allowing for improved distribution of trust and redundancy with respect to a secret key. FROST depends only on a prime-order group and cryptographic hash function. This document specifies a number of ciphersuites to instantiate FROST using different prime-order groups and hash functions. This document is a product of the Crypto Forum Research Group (CFRG) in 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 To unsubscribe send an email to ietf-announce-le...@ietf.org
RFC 9608 on No Revocation Available for X.509 Public Key Certificates
A new Request for Comments is now available in online RFC libraries. RFC 9608 Title: No Revocation Available for X.509 Public Key Certificates Author: R. Housley, T. Okubo, J. Mandel Status: Standards Track Stream: IETF Date: June 2024 Mailbox:hous...@vigilsec.com, tomofumi.okubo+i...@gmail.com, j...@akayla.com Pages: 10 Updates:RFC 5280 I-D Tag:draft-ietf-lamps-norevavail-04.txt URL:https://www.rfc-editor.org/info/rfc9608 DOI:10.17487/RFC9608 X.509v3 public key certificates are profiled in RFC 5280. Short-lived certificates are seeing greater use in the Internet. The Certification Authority (CA) that issues these short-lived certificates do not publish revocation information because the certificate lifespan that is shorter than the time needed to detect, report, and distribute revocation information. Some long-lived X.509v3 public key certificates never expire, and they are never revoked. This specification defines the noRevAvail certificate extension so that a relying party can readily determine that the CA does not publish revocation information for the certificate, and it updates the certification path validation algorithm defined in RFC 5280 so that revocation checking is skipped when the noRevAvail certificate extension is present. 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 To unsubscribe send an email to ietf-announce-le...@ietf.org
RFC 9606 on DNS Resolver Information
A new Request for Comments is now available in online RFC libraries. RFC 9606 Title: DNS Resolver Information Author: T. Reddy.K, M. Boucadair Status: Standards Track Stream: IETF Date: June 2024 Mailbox:kond...@gmail.com, mohamed.boucad...@orange.com Pages: 10 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-add-resolver-info-13.txt URL:https://www.rfc-editor.org/info/rfc9606 DOI:10.17487/RFC9606 This document specifies a method for DNS resolvers to publish information about themselves. DNS clients can use the resolver information to identify the capabilities of DNS resolvers. How DNS clients use such information is beyond the scope of this document. This document is a product of the Adaptive DNS Discovery 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 To unsubscribe send an email to ietf-announce-le...@ietf.org
RFC 9575 on DRIP Entity Tag (DET) Authentication Formats and Protocols for Broadcast Remote Identification (RID)
A new Request for Comments is now available in online RFC libraries. RFC 9575 Title: DRIP Entity Tag (DET) Authentication Formats and Protocols for Broadcast Remote Identification (RID) Author: A. Wiethuechter, Ed., S. Card, R. Moskowitz Status: Standards Track Stream: IETF Date: June 2024 Mailbox:adam.wiethuech...@axenterprize.com, stu.c...@axenterprize.com, r...@labs.htt-consult.com Pages: 43 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-drip-auth-49.txt URL:https://www.rfc-editor.org/info/rfc9575 DOI:10.17487/RFC9575 The Drone Remote Identification Protocol (DRIP), plus trust policies and periodic access to registries, augments Unmanned Aircraft System (UAS) Remote Identification (RID), enabling local real-time assessment of trustworthiness of received RID messages and observed UAS, even by Observers lacking Internet access. This document defines DRIP message types and formats to be sent in Broadcast RID Authentication Messages to verify that attached and recently detached messages were signed by the registered owner of the DRIP Entity Tag (DET) claimed. This document is a product of the Drone Remote ID Protocol 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 To unsubscribe send an email to ietf-announce-le...@ietf.org
RFC 9597 on CBOR Web Token (CWT) Claims in COSE Headers
A new Request for Comments is now available in online RFC libraries. RFC 9597 Title: CBOR Web Token (CWT) Claims in COSE Headers Author: T. Looker, M.B. Jones Status: Standards Track Stream: IETF Date: June 2024 Mailbox:tobias.looker@mattr.global, michael_b_jo...@hotmail.com Pages: 6 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-cose-cwt-claims-in-headers-10.txt URL:https://www.rfc-editor.org/info/rfc9597 DOI:10.17487/RFC9597 This document describes how to include CBOR Web Token (CWT) claims in the header parameters of any CBOR Object Signing and Encryption (COSE) structure. This functionality helps to facilitate applications that wish to make use of CWT claims in encrypted COSE structures and/or COSE structures featuring detached signatures, while having some of those claims be available before decryption and/or without inspecting the detached payload. Another use case is using CWT claims with payloads that are not CWT Claims Sets, including payloads that are not CBOR at all. This document is a product of the CBOR Object Signing and Encryption 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 To unsubscribe send an email to ietf-announce-le...@ietf.org
RFC 9583 on Application Scenarios for the Quantum Internet
A new Request for Comments is now available in online RFC libraries. RFC 9583 Title: Application Scenarios for the Quantum Internet Author: C. Wang, A. Rahman, R. Li, M. Aelmans, K. Chakraborty Status: Informational Stream: IRTF Date: June 2024 Mailbox:chonggang.w...@interdigital.com, akbar.rah...@ericsson.com, l...@se.kanazawa-u.ac.jp, maelm...@juniper.net, kaushik.chakrabor...@gmail.com Pages: 26 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-irtf-qirg-quantum-internet-use-cases-19.txt URL:https://www.rfc-editor.org/info/rfc9583 DOI:10.17487/RFC9583 The Quantum Internet has the potential to improve application functionality by incorporating quantum information technology into the infrastructure of the overall Internet. This document provides an overview of some applications expected to be used on the Quantum Internet and categorizes them. Some general requirements for the Quantum Internet are also discussed. The intent of this document is to describe a framework for applications and to describe a few selected application scenarios for the Quantum Internet. This document is a product of the Quantum Internet Research Group (QIRG). 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 To unsubscribe send an email to ietf-announce-le...@ietf.org
RFC 9592 on Retiring the Tao of the IETF
A new Request for Comments is now available in online RFC libraries. RFC 9592 Title: Retiring the Tao of the IETF Author: N. ten Oever, G. Wood Status: Informational Stream: IETF Date: June 2024 Mailbox:m...@nielstenoever.net, ghw...@staff.ietf.org Pages: 36 Obsoletes: RFC 6722 I-D Tag:draft-tenoever-tao-retirement-04.txt URL:https://www.rfc-editor.org/info/rfc9592 DOI:10.17487/RFC9592 This document retires and obsoletes the Tao of the IETF as an IETF-maintained document. This document also obsoletes RFC 6722, which describes the publication process of the Tao. Furthermore, this document describes the rationale for the retirement of the Tao. For archival purposes, the last version of the Tao is included in the appendix. Information that new participants need to engage in the work of the IETF will continue to be provided through the IETF website in a more timely and accessible manner. This is the way. 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 To unsubscribe send an email to ietf-announce-le...@ietf.org
RFC 9578 on Privacy Pass Issuance Protocols
A new Request for Comments is now available in online RFC libraries. RFC 9578 Title: Privacy Pass Issuance Protocols Author: S. Celi, A. Davidson, S. Valdez, C. A. Wood Status: Standards Track Stream: IETF Date: June 2024 Mailbox:cheren...@riseup.net, alex.davidso...@gmail.com, sval...@chromium.org, c...@heapingbits.net Pages: 36 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-privacypass-protocol-16.txt URL:https://www.rfc-editor.org/info/rfc9578 DOI:10.17487/RFC9578 This document specifies two variants of the two-message issuance protocol for Privacy Pass tokens: one that produces tokens that are privately verifiable using the Issuer Private Key and one that produces tokens that are publicly verifiable using the Issuer Public Key. Instances of "issuance protocol" and "issuance protocols" in the text of this document are used interchangeably to refer to the two variants of the Privacy Pass issuance protocol. This document is a product of the Privacy Pass 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 To unsubscribe send an email to ietf-announce-le...@ietf.org
RFC 9577 on The Privacy Pass HTTP Authentication Scheme
A new Request for Comments is now available in online RFC libraries. RFC 9577 Title: The Privacy Pass HTTP Authentication Scheme Author: T. Pauly, S. Valdez, C. A. Wood Status: Standards Track Stream: IETF Date: June 2024 Mailbox:tpa...@apple.com, sval...@chromium.org, c...@heapingbits.net Pages: 25 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-privacypass-auth-scheme-15.txt URL:https://www.rfc-editor.org/info/rfc9577 DOI:10.17487/RFC9577 This document defines an HTTP authentication scheme for Privacy Pass, a privacy-preserving authentication mechanism used for authorization. The authentication scheme specified in this document can be used by Clients to redeem Privacy Pass tokens with an Origin. It can also be used by Origins to challenge Clients to present Privacy Pass tokens. This document is a product of the Privacy Pass 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 To unsubscribe send an email to ietf-announce-le...@ietf.org
RFC 9576 on The Privacy Pass Architecture
A new Request for Comments is now available in online RFC libraries. RFC 9576 Title: The Privacy Pass Architecture Author: A. Davidson, J. Iyengar, C. A. Wood Status: Informational Stream: IETF Date: June 2024 Mailbox:alex.davidso...@gmail.com, j...@fastly.com, c...@heapingbits.net Pages: 25 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-privacypass-architecture-16.txt URL:https://www.rfc-editor.org/info/rfc9576 DOI:10.17487/RFC9576 This document specifies the Privacy Pass architecture and requirements for its constituent protocols used for authorization based on privacy-preserving authentication mechanisms. It describes the conceptual model of Privacy Pass and its protocols, its security and privacy goals, practical deployment models, and recommendations for each deployment model, to help ensure that the desired security and privacy goals are fulfilled. This document is a product of the Privacy Pass 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 To unsubscribe send an email to ietf-announce-le...@ietf.org
RFC 9584 on RTP Payload Format for Essential Video Coding (EVC)
A new Request for Comments is now available in online RFC libraries. RFC 9584 Title: RTP Payload Format for Essential Video Coding (EVC) Author: S. Zhao, S. Wenger, Y. Lim Status: Standards Track Stream: IETF Date: June 2024 Mailbox:shuai.z...@ieee.org, st...@stewe.org, yklwh...@gmail.com Pages: 42 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-avtcore-rtp-evc-07.txt URL:https://www.rfc-editor.org/info/rfc9584 DOI:10.17487/RFC9584 This document describes an RTP payload format for the Essential Video Coding (EVC) standard, published as ISO/IEC International Standard 23094-1. EVC was developed by the MPEG. The RTP payload format allows for the packetization of one or more Network Abstraction Layer (NAL) units in each RTP packet payload and the fragmentation of a NAL unit into multiple RTP packets. The payload format has broad applicability in videoconferencing, Internet video streaming, and high-bitrate entertainment-quality video, among other applications. This document is a product of the Audio/Video Transport Core Maintenance 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 To unsubscribe send an email to ietf-announce-le...@ietf.org
RFC 9596 on CBOR Object Signing and Encryption (COSE) "typ" (type) Header Parameter
A new Request for Comments is now available in online RFC libraries. RFC 9596 Title: CBOR Object Signing and Encryption (COSE) "typ" (type) Header Parameter Author: M.B. Jones, O. Steele Status: Standards Track Stream: IETF Date: June 2024 Mailbox:michael_b_jo...@hotmail.com, orie@transmute.industries Pages: 5 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-cose-typ-header-parameter-05.txt URL:https://www.rfc-editor.org/info/rfc9596 DOI:10.17487/RFC9596 This specification adds the equivalent of the JSON Object Signing and Encryption (JOSE) "typ" (type) header parameter to CBOR Object Signing and Encryption (COSE). This enables the benefits of explicit typing (as defined in RFC 8725, "JSON Web Token Best Current Practices") to be brought to COSE objects. The syntax of the COSE type header parameter value is the same as the existing COSE content type header parameter. This document is a product of the CBOR Object Signing and Encryption 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 To unsubscribe send an email to ietf-announce-le...@ietf.org
RFC 9587 on YANG Data Model for OSPFv3 Extended Link State Advertisements (LSAs)
A new Request for Comments is now available in online RFC libraries. RFC 9587 Title: YANG Data Model for OSPFv3 Extended Link State Advertisements (LSAs) Author: A. Lindem, S. Palani, Y. Qu Status: Standards Track Stream: IETF Date: June 2024 Mailbox:acee.i...@gmail.com, sharmila.pal...@microsoft.com, yingzhen.i...@gmail.com Pages: 25 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-lsr-ospfv3-extended-lsa-yang-29.txt URL:https://www.rfc-editor.org/info/rfc9587 DOI:10.17487/RFC9587 This document defines a YANG data model augmenting the IETF OSPF YANG data model (RFC 9129) to provide support for OSPFv3 Link State Advertisement (LSA) Extensibility as defined in RFC 8362. OSPFv3 Extended LSAs provide extensible TLV-based LSAs for the base LSA types defined in RFC 5340. 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 To unsubscribe send an email to ietf-announce-le...@ietf.org
RFC 9590 on IMAP Extension for Returning Mailbox METADATA in Extended LIS
A new Request for Comments is now available in online RFC libraries. RFC 9590 Title: IMAP Extension for Returning Mailbox METADATA in Extended LIS Author: K. Murchison, B. Gondwana Status: Standards Track Stream: IETF Date: May 2024 Mailbox:mu...@fastmailteam.com, br...@fastmailteam.com Pages: 6 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-extra-imap-list-metadata-05.txt URL:https://www.rfc-editor.org/info/rfc9590 DOI:10.17487/RFC9590 This document defines an extension to the Internet Message Access Protocol (IMAP) LIST command that allows the client to request mailbox annotations (metadata), along with other information typically returned by the LIST command. This document is a product of the Email mailstore and eXtensions To Revise or Amend 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 To unsubscribe send an email to ietf-announce-le...@ietf.org
RFC 9585 on IMAP Response Code for Command Progress Notifications
A new Request for Comments is now available in online RFC libraries. RFC 9585 Title: IMAP Response Code for Command Progress Notifications Author: M. Bettini Status: Standards Track Stream: IETF Date: May 2024 Mailbox:marco.bett...@open-xchange.com Pages: 6 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-extra-imap-inprogress-06.txt URL:https://www.rfc-editor.org/info/rfc9585 DOI:10.17487/RFC9585 This document defines a new IMAP untagged response code, "INPROGRESS", that provides progress notifications regarding the status of long-running commands. This document is a product of the Email mailstore and eXtensions To Revise or Amend 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 To unsubscribe send an email to ietf-announce-le...@ietf.org
RFC 9579 on Use of Password-Based Message Authentication Code 1 (PBMAC1) in PKCS #12 Syntax
A new Request for Comments is now available in online RFC libraries. RFC 9579 Title: Use of Password-Based Message Authentication Code 1 (PBMAC1) in PKCS #12 Syntax Author: H. Kario Status: Informational Stream: IETF Date: May 2024 Mailbox:hka...@redhat.com Pages: 15 Updates:RFC 7292, RFC 8018 I-D Tag:draft-ietf-lamps-pkcs12-pbmac1-08.txt URL:https://www.rfc-editor.org/info/rfc9579 DOI:10.17487/RFC9579 This document specifies additions and amendments to RFCs 7292 and 8018. It defines a way to use the Password-Based Message Authentication Code 1 (PBMAC1), defined in RFC 8018, inside the PKCS #12 syntax. The purpose of this specification is to permit the use of more modern Password-Based Key Derivation Functions (PBKDFs) and allow for regulatory compliance. This document is a product of the Limited Additional Mechanisms for PKIX and SMIME 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 To unsubscribe send an email to ietf-announce-le...@ietf.org
RFC 9586 on IMAP Extension for Using and Returning Unique Identifiers (UIDs) Only
A new Request for Comments is now available in online RFC libraries. RFC 9586 Title: IMAP Extension for Using and Returning Unique Identifiers (UIDs) Only Author: A. Melnikov, A. P. Achuthan, V. Nagulakonda, A. Singh, L. Alves Status: Experimental Stream: IETF Date: May 2024 Mailbox:alexey.melni...@isode.com, arunprak...@myyahoo.com, nvikram_i...@yahoo.com, ashutoshvsi...@yahoo.com, luis.al...@lafaspot.com Pages: 9 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-extra-imap-uidonly-08.txt URL:https://www.rfc-editor.org/info/rfc9586 DOI:10.17487/RFC9586 The UIDONLY extension to the Internet Message Access Protocol (RFCs 3501 and 9051) allows clients to enable a mode in which information about mailbox changes is returned using only Unique Identifiers (UIDs). Message numbers are not returned in responses and cannot be used in requests once this extension is enabled. This helps both clients and servers to reduce resource usage required to maintain a map between message numbers and UIDs. This document defines an experimental IMAP extension. This document is a product of the Email mailstore and eXtensions To Revise or Amend Working Group of the IETF. EXPERIMENTAL: This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. 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 To unsubscribe send an email to ietf-announce-le...@ietf.org
RFC 9571 on Extension of RFC 6374-Based Performance Measurement Using Synonymous Flow Labels
A new Request for Comments is now available in online RFC libraries. RFC 9571 Title: Extension of RFC 6374-Based Performance Measurement Using Synonymous Flow Labels Author: S. Bryant, Ed., G. Swallow, M. Chen, G. Fioccola, G. Mirsky Status: Standards Track Stream: IETF Date: May 2024 Mailbox:s...@stewartbryant.com, swallow.i...@gmail.com, mach.c...@huawei.com, giuseppe.fiocc...@huawei.com, gregimir...@gmail.com Pages: 18 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-mpls-rfc6374-sfl-10.txt URL:https://www.rfc-editor.org/info/rfc9571 DOI:10.17487/RFC9571 RFC 6374 describes methods of making loss and delay measurements on Label Switched Paths (LSPs) primarily as they are used in MPLS Transport Profile (MPLS-TP) networks. This document describes a method of extending the performance measurements (specified in RFC 6374) from flows carried over MPLS-TP to flows carried over generic MPLS LSPs. In particular, it extends the technique to allow loss and delay measurements to be made on multipoint-to-point LSPs and introduces some additional techniques to allow more sophisticated measurements to be made in both MPLS-TP and generic MPLS networks. This document is a product of the Multiprotocol Label Switching 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 To unsubscribe send an email to ietf-announce-le...@ietf.org
RFC 9548 on Generating Transport Key Containers (PFX) Using the GOST Algorithms
A new Request for Comments is now available in online RFC libraries. RFC 9548 Title: Generating Transport Key Containers (PFX) Using the GOST Algorithms Author: E. Karelina, Ed. Status: Informational Stream: Independent Date: May 2024 Mailbox:ekaterina.karel...@infotecs.ru Pages: 24 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-pkcs12-gost-08.txt URL:https://www.rfc-editor.org/info/rfc9548 DOI:10.17487/RFC9548 This document specifies how to use "PKCS #12: Personal Information Exchange Syntax v1.1" (RFC 7292) to transport key containers (PFX) for storing keys and certificates in conjunction with the Russian national standard GOST algorithms. This specification has been developed outside the IETF. The purpose of publication is to facilitate interoperable implementations that wish to support the GOST algorithms. This document does not imply IETF endorsement of the cryptographic algorithms used here. 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 To unsubscribe send an email to ietf-announce-le...@ietf.org
RFC 9574 on Optimized Ingress Replication Solution for Ethernet VPNs (EVPNs)
A new Request for Comments is now available in online RFC libraries. RFC 9574 Title: Optimized Ingress Replication Solution for Ethernet VPNs (EVPNs) Author: J. Rabadan, Ed., S. Sathappan, W. Lin, M. Katiyar, A. Sajassi Status: Standards Track Stream: IETF Date: May 2024 Mailbox:jorge.raba...@nokia.com, senthil.sathap...@nokia.com, w...@juniper.net, mu...@versa-networks.com, saja...@cisco.com Pages: 28 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-bess-evpn-optimized-ir-12.txt URL:https://www.rfc-editor.org/info/rfc9574 DOI:10.17487/RFC9574 Network Virtualization Overlay (NVO) networks using Ethernet VPNs (EVPNs) as their control plane may use trees based on ingress replication or Protocol Independent Multicast (PIM) to convey the overlay Broadcast, Unknown Unicast, or Multicast (BUM) traffic. PIM provides an efficient solution that prevents sending multiple copies of the same packet over the same physical link; however, it may not always be deployed in the NVO network core. Ingress replication avoids the dependency on PIM in the NVO network core. While ingress replication provides a simple multicast transport, some NVO networks with demanding multicast applications require a more efficient solution without PIM in the core. This document describes a solution to optimize the efficiency of ingress replication trees. 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 To unsubscribe send an email to ietf-announce-le...@ietf.org
RFC 9573 on MVPN/EVPN Tunnel Aggregation with Common Labels
A new Request for Comments is now available in online RFC libraries. RFC 9573 Title: MVPN/EVPN Tunnel Aggregation with Common Labels Author: Z. Zhang, E. Rosen, W. Lin, Z. Li, IJ. Wijnands Status: Standards Track Stream: IETF Date: May 2024 Mailbox:zzh...@juniper.net, erose...@gmail.com, w...@juniper.net, lizhen...@huawei.com, i...@braindump.be Pages: 14 Updates:RFC 6514, RFC 7432, RFC 7582 I-D Tag:draft-ietf-bess-mvpn-evpn-aggregation-label-14.txt URL:https://www.rfc-editor.org/info/rfc9573 DOI:10.17487/RFC9573 The Multicast VPN (MVPN) specifications allow a single Point-to-Multipoint (P2MP) tunnel to carry traffic of multiple IP VPNs (referred to as VPNs in this document). The EVPN specifications allow a single P2MP tunnel to carry traffic of multiple Broadcast Domains (BDs). These features require the ingress router of the P2MP tunnel to allocate an upstream-assigned MPLS label for each VPN or for each BD. A packet sent on a P2MP tunnel then carries the label that is mapped to its VPN or BD (in some cases, a distinct upstream-assigned label is needed for each flow.) Since each ingress router allocates labels independently, with no coordination among the ingress routers, the egress routers may need to keep track of a large number of labels. The number of labels may need to be as large as, or larger than, the product of the number of ingress routers times the number of VPNs or BDs. However, the number of labels can be greatly reduced if the association between a label and a VPN or BD is made by provisioning, so that all ingress routers assign the same label to a particular VPN or BD. New procedures are needed in order to take advantage of such provisioned labels. These new procedures also apply to Multipoint-to-Multipoint (MP2MP) tunnels. This document updates RFCs 6514, 7432, and 7582 by specifying the necessary procedures. 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 To unsubscribe send an email to ietf-announce-le...@ietf.org
RFC 9572 on Updates to EVPN Broadcast, Unknown Unicast, or Multicast (BUM) Procedures
A new Request for Comments is now available in online RFC libraries. RFC 9572 Title: Updates to EVPN Broadcast, Unknown Unicast, or Multicast (BUM) Procedures Author: Z. Zhang, W. Lin, J. Rabadan, K. Patel, A. Sajassi Status: Standards Track Stream: IETF Date: May 2024 Mailbox:zzh...@juniper.net, w...@juniper.net, jorge.raba...@nokia.com, ke...@arrcus.com, saja...@cisco.com Pages: 19 Updates:RFC 7432 I-D Tag:draft-ietf-bess-evpn-bum-procedure-updates-14.txt URL:https://www.rfc-editor.org/info/rfc9572 DOI:10.17487/RFC9572 This document specifies updated procedures for handling Broadcast, Unknown Unicast, or Multicast (BUM) traffic in Ethernet VPNs (EVPNs), including selective multicast and segmentation of provider tunnels. This document updates RFC 7432. 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 To unsubscribe send an email to ietf-announce-le...@ietf.org
RFC 9589 on On the Use of the Cryptographic Message Syntax (CMS) Signing-Time Attribute in Resource Public Key Infrastructure (RPKI) Signed Objects
A new Request for Comments is now available in online RFC libraries. RFC 9589 Title: On the Use of the Cryptographic Message Syntax (CMS) Signing-Time Attribute in Resource Public Key Infrastructure (RPKI) Signed Objects Author: J. Snijders, T. Harrison Status: Standards Track Stream: IETF Date: May 2024 Mailbox:j...@fastly.com, t...@apnic.net Pages: 9 Updates:RFC 6488 I-D Tag:draft-ietf-sidrops-cms-signing-time-07.txt URL:https://www.rfc-editor.org/info/rfc9589 DOI:10.17487/RFC9589 In the Resource Public Key Infrastructure (RPKI), Signed Objects are defined as Cryptographic Message Syntax (CMS) protected content types. A Signed Object contains a signing-time attribute, representing the purported time at which the object was signed by its issuer. RPKI repositories are accessible using the rsync and RPKI Repository Delta protocols, allowing Relying Parties (RPs) to synchronize a local copy of the RPKI repository used for validation with the remote repositories. This document describes how the CMS signing-time attribute can be used to avoid needless retransfers of data when switching between different synchronization protocols. This document updates RFC 6488 by mandating the presence of the CMS signing-time attribute and disallowing the use of the binary-signing-time attribute. This document is a product of the SIDR Operations 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 To unsubscribe send an email to ietf-announce-le...@ietf.org
RFC 9598 on Internationalized Email Addresses in X.509 Certificates
A new Request for Comments is now available in online RFC libraries. RFC 9598 Title: Internationalized Email Addresses in X.509 Certificates Author: A. Melnikov, W. Chuang, C. Bonnell Status: Standards Track Stream: IETF Date: May 2024 Mailbox:alexey.melni...@isode.com, wei...@google.com, corey.bonn...@digicert.com Pages: 12 Obsoletes: RFC 8398 Updates:RFC 5280 I-D Tag:draft-ietf-lamps-rfc8398bis-05.txt URL:https://www.rfc-editor.org/info/rfc9598 DOI:10.17487/RFC9598 This document defines a new name form for inclusion in the otherName field of an X.509 Subject Alternative Name and Issuer Alternative Name extension that allows a certificate subject to be associated with an internationalized email address. This document updates RFC 5280 and obsoletes RFC 8398. 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 To unsubscribe send an email to ietf-announce-le...@ietf.org
RFC 9582 on A Profile for Route Origin Authorizations (ROAs)
A new Request for Comments is now available in online RFC libraries. RFC 9582 Title: A Profile for Route Origin Authorizations (ROAs) Author: J. Snijders, B. Maddison, M. Lepinski, D. Kong, S. Kent Status: Standards Track Stream: IETF Date: May 2024 Mailbox:j...@fastly.com, benm@workonline.africa, mlepin...@carleton.edu, derrick.k...@raytheon.com, k...@alum.mit.edu Pages: 15 Obsoletes: RFC 6482 I-D Tag:draft-ietf-sidrops-rfc6482bis-09.txt URL:https://www.rfc-editor.org/info/rfc9582 DOI:10.17487/RFC9582 This document defines a standard profile for Route Origin Authorizations (ROAs). A ROA is a digitally signed object that provides a means of verifying that an IP address block holder has authorized an Autonomous System (AS) to originate routes to one or more prefixes within the address block. This document obsoletes RFC 6482. This document is a product of the SIDR Operations 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 To unsubscribe send an email to ietf-announce-le...@ietf.org
RFC 9570 on Deprecating the Use of Router Alert in LSP Ping
A new Request for Comments is now available in online RFC libraries. RFC 9570 Title: Deprecating the Use of Router Alert in LSP Ping Author: K. Kompella, R. Bonica, G. Mirsky, Ed. Status: Standards Track Stream: IETF Date: May 2024 Mailbox:kireeti.i...@gmail.com, rbon...@juniper.net, gregimir...@gmail.com Pages: 9 Updates:RFC 8029 I-D Tag:draft-ietf-mpls-lspping-norao-08.txt URL:https://www.rfc-editor.org/info/rfc9570 DOI:10.17487/RFC9570 The MPLS echo request and MPLS echo response messages, defined in RFC 8029, "Detecting Multiprotocol Label Switched (MPLS) Data-Plane Failures" (usually referred to as LSP ping), are encapsulated in IP packets with headers that include a Router Alert Option (RAO). In actual deployments, the RAO was neither required nor used. Furthermore, RFC 6398 identifies security vulnerabilities associated with the RAO in non-controlled environments, e.g., the case of using the MPLS echo request/reply as inter-area Operations, Administration, and Maintenance (OAM), and recommends against its use outside of controlled environments. Therefore, this document retires the RAO for MPLS OAM and updates RFC 8029 to remove the RAO from LSP ping message encapsulations. Furthermore, this document explains why RFC 7506 has been reclassified as Historic. Also, this document recommends the use of an IPv6 loopback address (::1/128) as the IPv6 destination address for an MPLS echo request message. This document is a product of the Multiprotocol Label Switching 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 To unsubscribe send an email to ietf-announce-le...@ietf.org
RFC 9562 on Universally Unique IDentifiers (UUIDs)
A new Request for Comments is now available in online RFC libraries. RFC 9562 Title: Universally Unique IDentifiers (UUIDs) Author: K. Davis, B. Peabody, P. Leach Status: Standards Track Stream: IETF Date: May 2024 Mailbox:kyda...@cisco.com, b...@peabody.io, p...@uw.edu Pages: 46 Obsoletes: RFC 4122 I-D Tag:draft-ietf-uuidrev-rfc4122bis-14.txt URL:https://www.rfc-editor.org/info/rfc9562 DOI:10.17487/RFC9562 This specification defines UUIDs (Universally Unique IDentifiers) -- also known as GUIDs (Globally Unique IDentifiers) -- and a Uniform Resource Name namespace for UUIDs. A UUID is 128 bits long and is intended to guarantee uniqueness across space and time. UUIDs were originally used in the Apollo Network Computing System (NCS), later in the Open Software Foundation's (OSF's) Distributed Computing Environment (DCE), and then in Microsoft Windows platforms. This specification is derived from the OSF DCE specification with the kind permission of the OSF (now known as "The Open Group"). Information from earlier versions of the OSF DCE specification have been incorporated into this document. This document obsoletes RFC 4122. This document is a product of the Revise Universally Unique Identifier Definitions 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 To unsubscribe send an email to ietf-announce-le...@ietf.org
RFC 9554 on vCard Format Extensions for JSContact
A new Request for Comments is now available in online RFC libraries.
RFC 9554
Title: vCard Format Extensions for JSContact
Author: R. Stepanek,
M. Loffredo
Status: Standards Track
Stream: IETF
Date: May 2024
Mailbox:r...@fastmailteam.com,
mario.loffr...@iit.cnr.it
Pages: 21
Updates:RFC 6350
I-D Tag:draft-ietf-calext-vcard-jscontact-extensions-10.txt
URL:https://www.rfc-editor.org/info/rfc9554
DOI:10.17487/RFC9554
This document defines a set of new properties for vCard and extends
the use of existing ones. Their primary purpose is to align the same
set of features between the JSContact and vCard formats, but the new
definitions also aim to be useful within just the vCard format. This
document updates RFC 6350 ("vCard Format Specification").
This document is a product of the Calendaring Extensions 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
To unsubscribe send an email to ietf-announce-le...@ietf.org
RFC 9553 on JSContact: A JSON Representation of Contact Data
A new Request for Comments is now available in online RFC libraries. RFC 9553 Title: JSContact: A JSON Representation of Contact Data Author: R. Stepanek, M. Loffredo Status: Standards Track Stream: IETF Date: May 2024 Mailbox:r...@fastmailteam.com, mario.loffr...@iit.cnr.it Pages: 73 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-calext-jscontact-16.txt URL:https://www.rfc-editor.org/info/rfc9553 DOI:10.17487/RFC9553 This specification defines a data model and JavaScript Object Notation (JSON) representation of contact card information that can be used for data storage and exchange in address book or directory applications. It aims to be an alternative to the vCard data format and to be unambiguous, extendable, and simple to process. In contrast to the JSON-based jCard format, it is not a direct mapping from the vCard data model and expands semantics where appropriate. Two additional specifications define new vCard elements and how to convert between JSContact and vCard. This document is a product of the Calendaring Extensions 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 To unsubscribe send an email to ietf-announce-le...@ietf.org
RFC 9555 on JSContact: Converting from and to vCard
A new Request for Comments is now available in online RFC libraries. RFC 9555 Title: JSContact: Converting from and to vCard Author: M. Loffredo, R. Stepanek Status: Standards Track Stream: IETF Date: May 2024 Mailbox:mario.loffr...@iit.cnr.it, r...@fastmailteam.com Pages: 60 Updates:RFC 6350 I-D Tag:draft-ietf-calext-jscontact-vcard-13.txt URL:https://www.rfc-editor.org/info/rfc9555 DOI:10.17487/RFC9555 This document defines how to convert contact information between the JSContact and vCard data formats. It defines conversion rules for every JSContact and vCard element registered at IANA at the time of publication. It also defines new JSContact properties as well as vCard properties and parameters, to support converting arbitrary or unknown JSContact and vCard elements. This document is a product of the Calendaring Extensions 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 To unsubscribe send an email to ietf-announce-le...@ietf.org
RFC 9568 on Virtual Router Redundancy Protocol (VRRP) Version 3 for IPv4 and IPv6
A new Request for Comments is now available in online RFC libraries. RFC 9568 Title: Virtual Router Redundancy Protocol (VRRP) Version 3 for IPv4 and IPv6 Author: A. Lindem, A. Dogra Status: Standards Track Stream: IETF Date: April 2024 Mailbox:acee.i...@gmail.com, addo...@cisco.com Pages: 35 Obsoletes: RFC 5798 I-D Tag:draft-ietf-rtgwg-vrrp-rfc5798bis-18.txt URL:https://www.rfc-editor.org/info/rfc9568 DOI:10.17487/RFC9568 This document defines version 3 of the Virtual Router Redundancy Protocol (VRRP) for IPv4 and IPv6. It obsoletes RFC 5798, which previously specified VRRP (version 3). RFC 5798 obsoleted RFC 3768, which specified VRRP (version 2) for IPv4. VRRP specifies an election protocol that dynamically assigns responsibility for a Virtual Router to one of the VRRP Routers on a LAN. The VRRP Router controlling the IPv4 or IPv6 address(es) associated with a Virtual Router is called the Active Router, and it forwards packets routed to these IPv4 or IPv6 addresses. Active Routers are configured with virtual IPv4 or IPv6 addresses, and Backup Routers infer the address family of the virtual addresses being advertised based on the IP protocol version. Within a VRRP Router, the Virtual Routers in each of the IPv4 and IPv6 address families are independent of one another and always treated as separate Virtual Router instances. The election process provides dynamic failover in the forwarding responsibility should the Active Router become unavailable. For IPv4, the advantage gained from using VRRP is a higher-availability default path without requiring configuration of dynamic routing or router discovery protocols on every end-host. For IPv6, the advantage gained from using VRRP for IPv6 is a quicker switchover to Backup Routers than can be obtained with standard IPv6 Neighbor Discovery mechanisms. This document is a product of the Routing Area Working Group 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 9567 on DNS Error Reporting
A new Request for Comments is now available in online RFC libraries. RFC 9567 Title: DNS Error Reporting Author: R. Arends, M. Larson Status: Standards Track Stream: IETF Date: April 2024 Mailbox:roy.are...@icann.org, matt.lar...@icann.org Pages: 11 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-dnsop-dns-error-reporting-08.txt URL:https://www.rfc-editor.org/info/rfc9567 DOI:10.17487/RFC9567 DNS error reporting is a lightweight reporting mechanism that provides the operator of an authoritative server with reports on DNS resource records that fail to resolve or validate. A domain owner or DNS hosting organization can use these reports to improve domain hosting. The reports are based on extended DNS errors as described in RFC 8914. When a domain name fails to resolve or validate due to a misconfiguration or an attack, the operator of the authoritative server may be unaware of this. To mitigate this lack of feedback, this document describes a method for a validating resolver to automatically signal an error to a monitoring agent specified by the authoritative server. The error is encoded in the QNAME; thus, the very act of sending the query is to report the error. This document is a product of the Domain Name System Operations 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 9560 on Federated Authentication for the Registration Data Access Protocol (RDAP) Using OpenID Connect
A new Request for Comments is now available in online RFC libraries. RFC 9560 Title: Federated Authentication for the Registration Data Access Protocol (RDAP) Using OpenID Connect Author: S. Hollenbeck Status: Standards Track Stream: IETF Date: April 2024 Mailbox:shollenb...@verisign.com Pages: 40 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-regext-rdap-openid-27.txt URL:https://www.rfc-editor.org/info/rfc9560 DOI:10.17487/RFC9560 The Registration Data Access Protocol (RDAP) provides Representational State Transfer (RESTful) web services to retrieve registration metadata from domain name and regional internet registries. RDAP allows a server to make access control decisions based on client identity, and as such, it includes support for client identification features provided by the Hypertext Transfer Protocol (HTTP). Identification methods that require clients to obtain and manage credentials from every RDAP server operator present management challenges for both clients and servers, whereas a federated authentication system would make it easier to operate and use RDAP without the need to maintain server-specific client credentials. This document describes a federated authentication system for RDAP based on OpenID Connect. This document is a product of the Registration Protocols Extensions 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 9557 on Date and Time on the Internet: Timestamps with Additional Information
A new Request for Comments is now available in online RFC libraries. RFC 9557 Title: Date and Time on the Internet: Timestamps with Additional Information Author: U. Sharma, C. Bormann Status: Standards Track Stream: IETF Date: April 2024 Mailbox:ryzoku...@igalia.com, c...@tzi.org Pages: 17 Updates:RFC 3339 I-D Tag:draft-ietf-sedate-datetime-extended-11.txt URL:https://www.rfc-editor.org/info/rfc9557 DOI:10.17487/RFC9557 This document defines an extension to the timestamp format defined in RFC 3339 for representing additional information, including a time zone. It updates RFC 3339 in the specific interpretation of the local offset , which is no longer understood to "imply that UTC is the preferred reference point for the specified time". This document is a product of the Serialising Extended Data About Times and Events 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 9566 on Deterministic Networking (DetNet) Packet Replication, Elimination, and Ordering Functions (PREOF) via MPLS over UDP/IP
A new Request for Comments is now available in online RFC libraries. RFC 9566 Title: Deterministic Networking (DetNet) Packet Replication, Elimination, and Ordering Functions (PREOF) via MPLS over UDP/IP Author: B. Varga, J. Farkas, A. Malis Status: Informational Stream: IETF Date: April 2024 Mailbox:balazs.a.va...@ericsson.com, janos.far...@ericsson.com, agma...@gmail.com Pages: 10 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-detnet-mpls-over-ip-preof-11.txt URL:https://www.rfc-editor.org/info/rfc9566 DOI:10.17487/RFC9566 This document describes how the DetNet IP data plane can support the Packet Replication, Elimination, and Ordering Functions (PREOF) built on the existing MPLS PREOF solution defined for the DetNet MPLS data plane and the mechanisms defined by MPLS-over-UDP technology. 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
RFC 9423 on Constrained RESTful Environments (CoRE) Target Attributes Registry
A new Request for Comments is now available in online RFC libraries. RFC 9423 Title: Constrained RESTful Environments (CoRE) Target Attributes Registry Author: C. Bormann Status: Informational Stream: IETF Date: April 2024 Mailbox:c...@tzi.org Pages: 8 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-core-target-attr-06.txt URL:https://www.rfc-editor.org/info/rfc9423 DOI:10.17487/RFC9423 The Constrained RESTful Environments (CoRE) specifications apply web technologies to constrained environments. One such important technology is Web Linking (RFC 8288), which CoRE specifications use as the basis for a number of discovery protocols, such as the Link Format (RFC 6690) in the Constrained Application Protocol's (CoAP's) resource discovery process (Section 7.2 of RFC 7252) and the Resource Directory (RD) (RFC 9176). Web Links can have target attributes, the names of which are not generally coordinated by the Web Linking specification (Section 2.2 of RFC 8288). This document introduces an IANA registry for coordinating names of target attributes when used in CoRE. It updates the "RD Parameters" IANA registry created by RFC 9176 to coordinate with this registry. This document is a product of the Constrained RESTful Environments 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
BCP 141, RFC 9542 on IANA Considerations and IETF Protocol and Documentation Usage for IEEE 802 Parameters
A new Request for Comments is now available in online RFC libraries. BCP 141 RFC 9542 Title: IANA Considerations and IETF Protocol and Documentation Usage for IEEE 802 Parameters Author: D. Eastlake 3rd, J. Abley, Y. Li Status: Best Current Practice Stream: IETF Date: April 2024 Mailbox:d3e...@gmail.com, jab...@strandkip.nl, liyiz...@huawei.com Pages: 32 Obsoletes: RFC 7042 See Also: BCP 141 I-D Tag:draft-ietf-intarea-rfc7042bis-11.txt URL:https://www.rfc-editor.org/info/rfc9542 DOI:10.17487/RFC9542 Some IETF protocols make use of Ethernet frame formats and IEEE 802 parameters. This document discusses several aspects of such parameters and their use in IETF protocols, specifies IANA considerations for assignment of points under the IANA Organizationally Unique Identifier (OUI), and provides some values for use in documentation. This document obsoletes RFC 7042. This document is a product of the Internet Area Working Group 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
RFC 9429 on JavaScript Session Establishment Protocol (JSEP)
A new Request for Comments is now available in online RFC libraries. RFC 9429 Title: JavaScript Session Establishment Protocol (JSEP) Author: J. Uberti, C. Jennings, E. Rescorla, Ed. Status: Standards Track Stream: IETF Date: April 2024 Mailbox:jus...@uberti.name, flu...@iii.ca, e...@rtfm.com Pages: 86 Obsoletes: RFC 8829 I-D Tag:draft-uberti-rtcweb-rfc8829bis-05.txt URL:https://www.rfc-editor.org/info/rfc9429 DOI:10.17487/RFC9429 This document describes the mechanisms for allowing a JavaScript application to control the signaling plane of a multimedia session via the interface specified in the W3C RTCPeerConnection API and discusses how this relates to existing signaling protocols. This specification obsoletes RFC 8829. This document is a product of the Real-Time Communication in WEB-browsers 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 9556 on Internet of Things (IoT) Edge Challenges and Functions
A new Request for Comments is now available in online RFC libraries. RFC 9556 Title: Internet of Things (IoT) Edge Challenges and Functions Author: J. Hong, Y-G. Hong, X. de Foy, M. Kovatsch, E. Schooler, D. Kutscher Status: Informational Stream: IRTF Date: April 2024 Mailbox:jh...@etri.re.kr, yonggeun.h...@gmail.com, xavier.de...@interdigital.com, i...@kovatsch.net, eve.schoo...@gmail.com, i...@dkutscher.net Pages: 31 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-irtf-t2trg-iot-edge-10.txt URL:https://www.rfc-editor.org/info/rfc9556 DOI:10.17487/RFC9556 Many Internet of Things (IoT) applications have requirements that cannot be satisfied by centralized cloud-based systems (i.e., cloud computing). These include time sensitivity, data volume, connectivity cost, operation in the face of intermittent services, privacy, and security. As a result, IoT is driving the Internet toward edge computing. This document outlines the requirements of the emerging IoT edge and its challenges. It presents a general model and major components of the IoT edge to provide a common basis for future discussions in the Thing-to-Thing Research Group (T2TRG) and other IRTF and IETF groups. This document is a product of the IRTF T2TRG. This document is a product of the Thing-to-Thing 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
RFC 9558 on Use of GOST 2012 Signature Algorithms in DNSKEY and RRSIG Resource Records for DNSSEC
A new Request for Comments is now available in online RFC libraries. RFC 9558 Title: Use of GOST 2012 Signature Algorithms in DNSKEY and RRSIG Resource Records for DNSSEC Author: B. Makarenko, V. Dolmatov, Ed. Status: Informational Stream: Independent Date: April 2024 Mailbox:bmakare...@tcinet.ru, vdolma...@gmail.com Pages: 9 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-makarenko-gost2012-dnssec-05.txt URL:https://www.rfc-editor.org/info/rfc9558 DOI:10.17487/RFC9558 This document describes how to produce digital signatures and hash functions using the GOST R 34.10-2012 and GOST R 34.11-2012 algorithms for DNSKEY, RRSIG, and DS resource records, for use in the Domain Name System Security Extensions (DNSSEC). 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 9536 on Registration Data Access Protocol (RDAP) Reverse Search
A new Request for Comments is now available in online RFC libraries. RFC 9536 Title: Registration Data Access Protocol (RDAP) Reverse Search Author: M. Loffredo, M. Martinelli Status: Standards Track Stream: IETF Date: April 2024 Mailbox:mario.loffr...@iit.cnr.it, maurizio.martine...@iit.cnr.it Pages: 17 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-regext-rdap-reverse-search-25.txt URL:https://www.rfc-editor.org/info/rfc9536 DOI:10.17487/RFC9536 The Registration Data Access Protocol (RDAP) does not include query capabilities for finding the list of domains related to a set of entities matching a given search pattern. Considering that an RDAP entity can be associated with any defined object class and other relationships between RDAP object classes exist, a reverse search can be applied to other use cases besides the classic domain-entity scenario. This document describes an RDAP extension that allows servers to provide a reverse search feature based on the relationship defined in RDAP between an object class for search and any related object class. The reverse search based on the domain-entity relationship is treated as a particular case. This document is a product of the Registration Protocols Extensions 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 9561 on Using the Parallel NFS (pNFS) SCSI Layout to Access Non-Volatile Memory Express (NVMe) Storage Devices
A new Request for Comments is now available in online RFC libraries. RFC 9561 Title: Using the Parallel NFS (pNFS) SCSI Layout to Access Non-Volatile Memory Express (NVMe) Storage Devices Author: C. Hellwig, Ed., C. Lever, S. Faibish, D. Black Status: Standards Track Stream: IETF Date: April 2024 Mailbox:h...@lst.de, chuck.le...@oracle.com, s.faib...@opendrives.com, david.bl...@dell.com Pages: 9 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-nfsv4-scsi-layout-nvme-07.txt URL:https://www.rfc-editor.org/info/rfc9561 DOI:10.17487/RFC9561 This document specifies how to use the Parallel Network File System (pNFS) Small Computer System Interface (SCSI) Layout Type to access storage devices using the Non-Volatile Memory Express (NVMe) protocol family. This document is a product of the Network File System Version 4 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 9564 on Faster Than Light Speed Protocol (FLIP)
A new Request for Comments is now available in online RFC libraries. RFC 9564 Title: Faster Than Light Speed Protocol (FLIP) Author: M. Blanchet Status: Informational Stream: Independent Date: 1 April 2024 Mailbox:marc.blanc...@viagenie.ca Pages: 6 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-blanchet-flip-01.txt URL:https://www.rfc-editor.org/info/rfc9564 DOI:10.17487/RFC9564 The recent advances in artificial intelligence (AI) such as large language models enable the design of the Faster than LIght speed Protocol (FLIP) for Internet. FLIP provides a way to avoid congestion, enhance security, and deliver faster packets on the Internet by using AI to predict future packets at the receiving peer before they arrive. This document describes the protocol, its various encapsulations, and some operational considerations. 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 9537 on Redacted Fields in the Registration Data Access Protocol (RDAP) Response
A new Request for Comments is now available in online RFC libraries. RFC 9537 Title: Redacted Fields in the Registration Data Access Protocol (RDAP) Response Author: J. Gould, D. Smith, J. Kolker, R. Carney Status: Standards Track Stream: IETF Date: March 2024 Mailbox:jgo...@verisign.com, dsm...@verisign.com, jkol...@godaddy.com, rcar...@godaddy.com Pages: 31 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-regext-rdap-redacted-16.txt URL:https://www.rfc-editor.org/info/rfc9537 DOI:10.17487/RFC9537 This document describes a Registration Data Access Protocol (RDAP) extension for specifying methods of redaction of RDAP responses and explicitly identifying redacted RDAP response fields, using JSONPath as the default expression language. This document is a product of the Registration Protocols Extensions 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
BCP 219, RFC 9499 on DNS Terminology
A new Request for Comments is now available in online RFC libraries. BCP 219 RFC 9499 Title: DNS Terminology Author: P. Hoffman, K. Fujiwara Status: Best Current Practice Stream: IETF Date: March 2024 Mailbox:paul.hoff...@icann.org, fujiw...@jprs.co.jp Pages: 45 Obsoletes: RFC 8499 Updates:RFC 2308 See Also: BCP 219 I-D Tag:draft-ietf-dnsop-rfc8499bis-10.txt URL:https://www.rfc-editor.org/info/rfc9499 DOI:10.17487/RFC9499 The Domain Name System (DNS) is defined in literally dozens of different RFCs. The terminology used by implementers and developers of DNS protocols, and by operators of DNS systems, has changed in the decades since the DNS was first defined. This document gives current definitions for many of the terms used in the DNS in a single document. This document updates RFC 2308 by clarifying the definitions of "forwarder" and "QNAME". It obsoletes RFC 8499 by adding multiple terms and clarifications. Comprehensive lists of changed and new definitions can be found in Appendices A and B. This document is a product of the Domain Name System 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
RFC 9544 on Precision Availability Metrics (PAMs) for Services Governed by Service Level Objectives (SLOs)
A new Request for Comments is now available in online RFC libraries. RFC 9544 Title: Precision Availability Metrics (PAMs) for Services Governed by Service Level Objectives (SLOs) Author: G. Mirsky, J. Halpern, X. Min, A. Clemm, J. Strassner, J. François Status: Informational Stream: IETF Date: March 2024 Mailbox:gregimir...@gmail.com, joel.halp...@ericsson.com, xiao.m...@zte.com.cn, lud...@clemm.org, straz...@gmail.com, jerome.franc...@inria.fr Pages: 12 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-ippm-pam-09.txt URL:https://www.rfc-editor.org/info/rfc9544 DOI:10.17487/RFC9544 This document defines a set of metrics for networking services with performance requirements expressed as Service Level Objectives (SLOs). These metrics, referred to as "Precision Availability Metrics (PAMs)", are useful for defining and monitoring SLOs. For example, PAMs can be used by providers and/or customers of an RFC 9543 Network Slice Service to assess whether the service is provided in compliance with its defined SLOs. This document is a product of the IP Performance Measurement 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 9550 on Deterministic Networking (DetNet): Packet Ordering Function
A new Request for Comments is now available in online RFC libraries. RFC 9550 Title: Deterministic Networking (DetNet): Packet Ordering Function Author: B. Varga, Ed., J. Farkas, S. Kehrer, T. Heer Status: Informational Stream: IETF Date: March 2024 Mailbox:balazs.a.va...@ericsson.com, janos.far...@ericsson.com, stephan.keh...@belden.com, tobias.h...@belden.com Pages: 11 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-detnet-pof-11.txt URL:https://www.rfc-editor.org/info/rfc9550 DOI:10.17487/RFC9550 The replication and elimination functions of the Deterministic Networking (DetNet) architecture can result in out-of-order packets, which is not acceptable for some time-sensitive applications. The Packet Ordering Function (POF) algorithms described in this document enable restoration of the correct packet order when the replication and elimination functions are used in DetNet networks. The POF only provides ordering within the latency bound of a DetNet flow; it does not provide any additional reliability. 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
RFC 9541 on Flush Mechanism for Customer MAC Addresses Based on Service Instance Identifier (I-SID) in Provider Backbone Bridging EVPN (PBB-EVPN)
A new Request for Comments is now available in online RFC libraries. RFC 9541 Title: Flush Mechanism for Customer MAC Addresses Based on Service Instance Identifier (I-SID) in Provider Backbone Bridging EVPN (PBB-EVPN) Author: J. Rabadan, Ed., S. Sathappan, K. Nagaraj, M. Miyake, T. Matsuda Status: Standards Track Stream: IETF Date: March 2024 Mailbox:jorge.raba...@nokia.com, senthil.sathap...@nokia.com, kiran.naga...@nokia.com, masahiro.miy...@g.softbank.co.jp, taku.mats...@g.softbank.co.jp Pages: 11 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-bess-pbb-evpn-isid-cmacflush-09.txt URL:https://www.rfc-editor.org/info/rfc9541 DOI:10.17487/RFC9541 Provider Backbone Bridging (PBB) can be combined with Ethernet Virtual Private Networks (EVPNs) to deploy Ethernet Local Area Network (E-LAN) services in large Multiprotocol Label Switching (MPLS) networks. That combination is what we refer to as "PBB-EVPN." Single-Active multihoming and per Service Instance Identifier (I-SID) load-balancing can be provided to access devices and aggregation networks. In order to speed up the network convergence in case of failures on Single-Active multihomed Ethernet Segments (ESs), PBB-EVPN defines a flush mechanism for Customer MACs (C-MACs) called "C-MAC flush" that works for different Ethernet Segment Backbone MAC (B-MAC) address allocation models. This document complements those C-MAC flush procedures for cases in which no PBB-EVPN ESs are defined (i.e., the attachment circuit is associated with a zero Ethernet Segment Identifier (ESI)) and the C-MAC flush requires I-SID-level granularity. 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 9529 on Traces of Ephemeral Diffie-Hellman Over COSE (EDHOC)
A new Request for Comments is now available in online RFC libraries. RFC 9529 Title: Traces of Ephemeral Diffie-Hellman Over COSE (EDHOC) Author: G. Selander, J. Preuß Mattsson, M. Serafin, M. Tiloca, M. Vučinić Status: Informational Stream: IETF Date: March 2024 Mailbox:goran.selan...@ericsson.com, john.matts...@ericsson.com, marek.sera...@assaabloy.com, marco.til...@ri.se, malisa.vuci...@inria.fr Pages: 62 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-lake-traces-09.txt URL:https://www.rfc-editor.org/info/rfc9529 DOI:10.17487/RFC9529 This document contains example traces of Ephemeral Diffie-Hellman Over COSE (EDHOC). This document is a product of the Lightweight Authenticated Key Exchange 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 9528 on Ephemeral Diffie-Hellman Over COSE (EDHOC)
A new Request for Comments is now available in online RFC libraries. RFC 9528 Title: Ephemeral Diffie-Hellman Over COSE (EDHOC) Author: G. Selander, J. Preuß Mattsson, F. Palombini Status: Standards Track Stream: IETF Date: March 2024 Mailbox:goran.selan...@ericsson.com, john.matts...@ericsson.com, francesca.palomb...@ericsson.com Pages: 82 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-lake-edhoc-23.txt URL:https://www.rfc-editor.org/info/rfc9528 DOI:10.17487/RFC9528 This document specifies Ephemeral Diffie-Hellman Over COSE (EDHOC), a very compact and lightweight authenticated Diffie-Hellman key exchange with ephemeral keys. EDHOC provides mutual authentication, forward secrecy, and identity protection. EDHOC is intended for usage in constrained scenarios, and a main use case is to establish an Object Security for Constrained RESTful Environments (OSCORE) security context. By reusing CBOR Object Signing and Encryption (COSE) for cryptography, Concise Binary Object Representation (CBOR) for encoding, and Constrained Application Protocol (CoAP) for transport, the additional code size can be kept very low. This document is a product of the Lightweight Authenticated Key Exchange 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 9509 on X.509 Certificate Extended Key Usage (EKU) for 5G Network Functions
A new Request for Comments is now available in online RFC libraries. RFC 9509 Title: X.509 Certificate Extended Key Usage (EKU) for 5G Network Functions Author: T. Reddy.K, J. Ekman, D. Migault Status: Standards Track Stream: IETF Date: March 2024 Mailbox:kond...@gmail.com, jani.ek...@nokia.com, daniel.miga...@ericsson.com Pages: 9 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-lamps-nf-eku-05.txt URL:https://www.rfc-editor.org/info/rfc9509 DOI:10.17487/RFC9509 RFC 5280 specifies several extended key purpose identifiers (KeyPurposeIds) for X.509 certificates. This document defines encrypting JSON objects in HTTP messages, using JSON Web Tokens (JWTs), and signing the OAuth 2.0 access tokens KeyPurposeIds for inclusion in the Extended Key Usage (EKU) extension of X.509 v3 public key certificates used by Network Functions (NFs) for the 5G System. 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 9549 on Internationalization Updates to RFC 5280
A new Request for Comments is now available in online RFC libraries. RFC 9549 Title: Internationalization Updates to RFC 5280 Author: R. Housley Status: Standards Track Stream: IETF Date: March 2024 Mailbox:hous...@vigilsec.com Pages: 10 Obsoletes: RFC 8399 Updates:RFC 5280 I-D Tag:draft-ietf-lamps-rfc8399bis-05.txt URL:https://www.rfc-editor.org/info/rfc9549 DOI:10.17487/RFC9549 The updates to RFC 5280 described in this document provide alignment with the 2008 specification for Internationalized Domain Names (IDNs) and includes support for internationalized email addresses in X.509 certificates. The updates ensure that name constraints for email addresses that contain only ASCII characters and internationalized email addresses are handled in the same manner. This document obsoletes RFC 8399. 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 9565 on An Update to the tcpControlBits IP Flow Information Export (IPFIX) Information Element
A new Request for Comments is now available in online RFC libraries. RFC 9565 Title: An Update to the tcpControlBits IP Flow Information Export (IPFIX) Information Element Author: M. Boucadair Status: Standards Track Stream: IETF Date: March 2024 Mailbox:mohamed.boucad...@orange.com Pages: 7 Obsoletes: RFC 7125 I-D Tag:draft-ietf-opsawg-rfc7125-update-07.txt URL:https://www.rfc-editor.org/info/rfc9565 DOI:10.17487/RFC9565 RFC 7125 revised the tcpControlBits IP Flow Information Export (IPFIX) Information Element that was originally defined in RFC 5102 to reflect changes to the TCP header control bits since RFC 793. However, that update is still problematic for interoperability because some flag values have subsequently been deprecated. This document removes stale information from the IANA "IPFIX Information Elements" registry and avoids future conflicts with the authoritative IANA "TCP Header Flags" registry. This document obsoletes RFC 7125. This document is a product of the Operations and Management Area Working Group 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 9551 on Framework of Operations, Administration, and Maintenance (OAM) for Deterministic Networking (DetNet)
A new Request for Comments is now available in online RFC libraries. RFC 9551 Title: Framework of Operations, Administration, and Maintenance (OAM) for Deterministic Networking (DetNet) Author: G. Mirsky, F. Theoleyre, G. Papadopoulos, CJ. Bernardos, B. Varga, J. Farkas Status: Informational Stream: IETF Date: March 2024 Mailbox:gregimir...@gmail.com, fabrice.theole...@cnrs.fr, georgios.papadopou...@imt-atlantique.fr, c...@it.uc3m.es, balazs.a.va...@ericsson.com, janos.far...@ericsson.com Pages: 14 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-detnet-oam-framework-11.txt URL:https://www.rfc-editor.org/info/rfc9551 DOI:10.17487/RFC9551 Deterministic Networking (DetNet), as defined in RFC 8655, aims to provide bounded end-to-end latency on top of the network infrastructure, comprising both Layer 2 bridged and Layer 3 routed segments. This document's primary purpose is to detail the specific requirements of the Operations, Administration, and Maintenance (OAM) recommended to maintain a deterministic network. The document will be used in future work that defines the applicability of and extension of OAM protocols for a deterministic network. With the implementation of the OAM framework in DetNet, an operator will have a real-time view of the network infrastructure regarding the network's ability to respect the Service Level Objective (SLO), such as packet delay, delay variation, and packet-loss ratio, assigned to each DetNet flow. 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
RFC 9543 on A Framework for Network Slices in Networks Built from IETF Technologies
A new Request for Comments is now available in online RFC libraries. RFC 9543 Title: A Framework for Network Slices in Networks Built from IETF Technologies Author: A. Farrel, Ed., J. Drake, Ed., R. Rokui, S. Homma, K. Makhijani, L. Contreras, J. Tantsura Status: Informational Stream: IETF Date: March 2024 Mailbox:adr...@olddog.co.uk, je_dr...@yahoo.com, rro...@ciena.com, shunsuke.homma.i...@gmail.com, kiran.i...@gmail.com, luismiguel.contrerasmuri...@telefonica.com, jefftant.i...@gmail.com Pages: 44 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-teas-ietf-network-slices-25.txt URL:https://www.rfc-editor.org/info/rfc9543 DOI:10.17487/RFC9543 This document describes network slicing in the context of networks built from IETF technologies. It defines the term "IETF Network Slice" to describe this type of network slice and establishes the general principles of network slicing in the IETF context. The document discusses the general framework for requesting and operating IETF Network Slices, the characteristics of an IETF Network Slice, the necessary system components and interfaces, and the mapping of abstract requests to more specific technologies. The document also discusses related considerations with monitoring and security. This document also provides definitions of related terms to enable consistent usage in other IETF documents that describe or use aspects of IETF Network Slices. This document is a product of the Traffic Engineering Architecture and Signaling 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 9531 on Path Steering in Content-Centric Networking (CCNx) and Named Data Networking (NDN)
A new Request for Comments is now available in online RFC libraries. RFC 9531 Title: Path Steering in Content-Centric Networking (CCNx) and Named Data Networking (NDN) Author: I. Moiseenko, D. Oran Status: Experimental Stream: IRTF Date: March 2024 Mailbox:ili...@mailbox.org, daveo...@orandom.net Pages: 19 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-irtf-icnrg-pathsteering-07.txt URL:https://www.rfc-editor.org/info/rfc9531 DOI:10.17487/RFC9531 Path steering is a mechanism to discover paths to the producers of Information-Centric Networking (ICN) Content Objects and steer subsequent Interest messages along a previously discovered path. It has various uses, including the operation of state-of-the-art multi-path congestion control algorithms and for network measurement and management. This specification derives directly from the design published in "Path Switching in Content Centric and Named Data Networks" (4th ACM Conference on Information-Centric Networking) and, therefore, does not recapitulate the design motivations, implementation details, or evaluation of the scheme. However, some technical details are different, and where there are differences, the design documented here is to be considered definitive. This document is a product of the IRTF Information-Centric Networking Research Group (ICNRG). It is not an IETF product and is not an Internet Standard. EXPERIMENTAL: This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. 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
RFC 9508 on Information-Centric Networking (ICN) Ping Protocol Specification
A new Request for Comments is now available in online RFC libraries. RFC 9508 Title: Information-Centric Networking (ICN) Ping Protocol Specification Author: S. Mastorakis, D. Oran, J. Gibson, I. Moiseenko, R. Droms Status: Experimental Stream: IRTF Date: March 2024 Mailbox:smast...@nd.edu, daveo...@orandom.net, jcgibso...@gmail.com, ili...@mailbox.org, rdroms.i...@gmail.com Pages: 18 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-irtf-icnrg-icnping-12.txt URL:https://www.rfc-editor.org/info/rfc9508 DOI:10.17487/RFC9508 This document presents the design of an Information-Centric Networking (ICN) Ping protocol. It includes the operations of both the client and the forwarder. This document is a product of the Information-Centric Networking Research Group of the IRTF. EXPERIMENTAL: This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. 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
RFC 9507 on Information-Centric Networking (ICN) Traceroute Protocol Specification
A new Request for Comments is now available in online RFC libraries. RFC 9507 Title: Information-Centric Networking (ICN) Traceroute Protocol Specification Author: S. Mastorakis, D. Oran, I. Moiseenko, J. Gibson, R. Droms Status: Experimental Stream: IRTF Date: March 2024 Mailbox:smast...@nd.edu, daveo...@orandom.net, ili...@mailbox.org, jcgibso...@gmail.com, rdroms.i...@gmail.com Pages: 17 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-irtf-icnrg-icntraceroute-11.txt URL:https://www.rfc-editor.org/info/rfc9507 DOI:10.17487/RFC9507 This document presents the design of an Information-Centric Networking (ICN) Traceroute protocol. This includes the operation of both the client and the forwarder. This document is a product of the Information-Centric Networking Research Group of the IRTF. EXPERIMENTAL: This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. 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
RFC 9546 on Operations, Administration, and Maintenance (OAM) for Deterministic Networking (DetNet) with the MPLS Data Plane
A new Request for Comments is now available in online RFC libraries. RFC 9546 Title: Operations, Administration, and Maintenance (OAM) for Deterministic Networking (DetNet) with the MPLS Data Plane Author: G. Mirsky, M. Chen, B. Varga Status: Standards Track Stream: IETF Date: February 2024 Mailbox:gregimir...@gmail.com, mach.c...@huawei.com, balazs.a.va...@ericsson.com Pages: 12 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-detnet-mpls-oam-15.txt URL:https://www.rfc-editor.org/info/rfc9546 DOI:10.17487/RFC9546 This document defines format and usage principles of the Deterministic Networking (DetNet) service Associated Channel over a DetNet network with the MPLS data plane. The DetNet service Associated Channel can be used to carry test packets of active Operations, Administration, and Maintenance (OAM) protocols that are used to detect DetNet failures and measure performance metrics. This document is a product of the Deterministic Networking 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 9539 on Unilateral Opportunistic Deployment of Encrypted Recursive-to-Authoritative DNS
A new Request for Comments is now available in online RFC libraries. RFC 9539 Title: Unilateral Opportunistic Deployment of Encrypted Recursive-to-Authoritative DNS Author: D. K. Gillmor, Ed., J. Salazar, Ed., P. Hoffman, Ed. Status: Experimental Stream: IETF Date: February 2024 Mailbox:d...@fifthhorseman.net, joeyg...@gmail.com, paul.hoff...@icann.org Pages: 24 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-dprive-unilateral-probing-13.txt URL:https://www.rfc-editor.org/info/rfc9539 DOI:10.17487/RFC9539 This document sets out steps that DNS servers (recursive resolvers and authoritative servers) can take unilaterally (without any coordination with other peers) to defend DNS query privacy against a passive network monitor. The protections provided by the guidance in this document can be defeated by an active attacker, but they should be simpler and less risky to deploy than more powerful defenses. The goal of this document is to simplify and speed up deployment of opportunistic encrypted transport in the recursive-to-authoritative hop of the DNS ecosystem. Wider easy deployment of the underlying encrypted transport on an opportunistic basis may facilitate the future specification of stronger cryptographic protections against more-powerful attacks. This document is a product of the DNS PRIVate Exchange Working Group of the IETF. EXPERIMENTAL: This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. 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 9510 on Alternative Delta Time Encoding for Content-Centric Networking (CCNx) Using Compact Floating-Point Arithmetic
A new Request for Comments is now available in online RFC libraries.
RFC 9510
Title: Alternative Delta Time Encoding for
Content-Centric Networking (CCNx)
Using Compact Floating-Point Arithmetic
Author: C. Gündoğan,
T. Schmidt,
D. Oran,
M. Wählisch
Status: Experimental
Stream: IRTF
Date: February 2024
Mailbox:cenk.gundo...@huawei.com,
t.schm...@haw-hamburg.de,
daveo...@orandom.net,
m.waehli...@tu-dresden.de
Pages: 11
Updates:RFC 8609
I-D Tag:draft-irtf-icnrg-ccnx-timetlv-05.txt
URL:https://www.rfc-editor.org/info/rfc9510
DOI:10.17487/RFC9510
Content-Centric Networking (CCNx) utilizes delta time for a number of
functions. When using CCNx in environments with constrained nodes or
bandwidth constrained networks, it is valuable to have a compressed
representation of delta time. In order to do so, either accuracy or
dynamic range has to be sacrificed. Since the current uses of delta
time do not require both simultaneously, one can consider a
logarithmic encoding. This document updates RFC 8609 ("CCNx messages
in TLV Format") to specify this alternative encoding.
This document is a product of the IRTF Information-Centric Networking
Research Group (ICNRG).
EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community. It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
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
RFC 9545 on Path Segment Identifier in MPLS-Based Segment Routing Networks
A new Request for Comments is now available in online RFC libraries. RFC 9545 Title: Path Segment Identifier in MPLS-Based Segment Routing Networks Author: W. Cheng, Ed., H. Li, C. Li, Ed., R. Gandhi, R. Zigler Status: Standards Track Stream: IETF Date: February 2024 Mailbox:chengweiqi...@chinamobile.com, li...@chinamobile.com, c...@huawei.com, rgan...@cisco.com, royi.zig...@broadcom.com Pages: 11 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-spring-mpls-path-segment-22.txt URL:https://www.rfc-editor.org/info/rfc9545 DOI:10.17487/RFC9545 A Segment Routing (SR) path is identified by an SR segment list. A subset of segments from the segment list cannot be leveraged to distinguish one SR path from another as they may be partially congruent. SR path identification is a prerequisite for various use cases such as performance measurement and end-to-end 1+1 path protection. In an SR over MPLS (SR-MPLS) data plane, an egress node cannot determine on which SR path a packet traversed the network from the label stack because the segment identifiers are removed from the label stack as the packet transits the network. This document defines a Path Segment Identifier (PSID) to identify an SR path on the egress node of the path. This document is a product of the Source Packet Routing in Networking 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 9524 on Segment Routing Replication for Multipoint Service Delivery
A new Request for Comments is now available in online RFC libraries. RFC 9524 Title: Segment Routing Replication for Multipoint Service Delivery Author: D. Voyer, Ed., C. Filsfils, R. Parekh, H. Bidgoli, Z. Zhang Status: Standards Track Stream: IETF Date: February 2024 Mailbox:daniel.vo...@bell.ca, cfils...@cisco.com, ripar...@cisco.com, hooman.bidg...@nokia.com, zzh...@juniper.net Pages: 22 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-spring-sr-replication-segment-19.txt URL:https://www.rfc-editor.org/info/rfc9524 DOI:10.17487/RFC9524 This document describes the Segment Routing Replication segment for multipoint service delivery. A Replication segment allows a packet to be replicated from a replication node to downstream nodes. This document is a product of the Source Packet Routing in Networking 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 9538 on Content Delivery Network Interconnection (CDNI) Delegation Using the Automated Certificate Management Environment
A new Request for Comments is now available in online RFC libraries. RFC 9538 Title: Content Delivery Network Interconnection (CDNI) Delegation Using the Automated Certificate Management Environment Author: F. Fieau, Ed., E. Stephan, S. Mishra Status: Standards Track Stream: IETF Date: February 2024 Mailbox:frederic.fi...@orange.com, emile.step...@orange.com, sanjay.mis...@verizon.com Pages: 10 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-cdni-delegation-acme-04.txt URL:https://www.rfc-editor.org/info/rfc9538 DOI:10.17487/RFC9538 This document defines metadata to support delegating the delivery of HTTPS content between two or more interconnected Content Delivery Networks (CDNs). Specifically, this document defines a Content Delivery Network Interconnection (CDNI) Metadata interface object to enable delegation of X.509 certificates leveraging delegation schemes defined in RFC 9115. Per RFC 9115, delegating entities can remain in full control of the delegation and can revoke it at any time. This avoids the need to share private cryptographic key material between the involved entities. This document is a product of the Content Delivery Networks Interconnection 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 9535 on JSONPath: Query Expressions for JSON
A new Request for Comments is now available in online RFC libraries. RFC 9535 Title: JSONPath: Query Expressions for JSON Author: S. Gössner, Ed., G. Normington, Ed., C. Bormann, Ed. Status: Standards Track Stream: IETF Date: February 2024 Mailbox:stefan.goess...@fh-dortmund.de, glyn.norming...@gmail.com, c...@tzi.org Pages: 62 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-jsonpath-base-21.txt URL:https://www.rfc-editor.org/info/rfc9535 DOI:10.17487/RFC9535 JSONPath defines a string syntax for selecting and extracting JSON (RFC 8259) values from within a given JSON value. This document is a product of the JSON Path 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 9540 on Discovery of Oblivious Services via Service Binding Records
A new Request for Comments is now available in online RFC libraries. RFC 9540 Title: Discovery of Oblivious Services via Service Binding Records Author: T. Pauly, T. Reddy.K Status: Standards Track Stream: IETF Date: February 2024 Mailbox:tpa...@apple.com, kond...@gmail.com Pages: 10 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-ohai-svcb-config-07.txt URL:https://www.rfc-editor.org/info/rfc9540 DOI:10.17487/RFC9540 This document defines a parameter that can be included in Service Binding (SVCB) and HTTPS DNS resource records to denote that a service is accessible using Oblivious HTTP, by offering an Oblivious Gateway Resource through which to access the target. This document also defines a mechanism for learning the key configuration of the discovered Oblivious Gateway Resource. This document is a product of the Oblivious HTTP Application Intermediation 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 9523 on A Secure Selection and Filtering Mechanism for the Network Time Protocol with Khronos
A new Request for Comments is now available in online RFC libraries. RFC 9523 Title: A Secure Selection and Filtering Mechanism for the Network Time Protocol with Khronos Author: N. Rozen-Schiff, D. Dolev, T. Mizrahi, M. Schapira Status: Informational Stream: IETF Date: February 2024 Mailbox:neta.r.sch...@gmail.com, danny.do...@mail.huji.ac.il, tal.mizrahi@gmail.com, schapi...@huji.ac.il Pages: 13 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-ntp-chronos-25.txt URL:https://www.rfc-editor.org/info/rfc9523 DOI:10.17487/RFC9523 The Network Time Protocol version 4 (NTPv4), as defined in RFC 5905, is the mechanism used by NTP clients to synchronize with NTP servers across the Internet. This document describes a companion application to the NTPv4 client, named "Khronos", that is used as a "watchdog" alongside NTPv4 and that provides improved security against time-shifting attacks. Khronos involves changes to the NTP client's system process only. Since it does not affect the wire protocol, the Khronos mechanism is applicable to current and future time protocols. This document is a product of the Network Time Protocols 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 9512 on YAML Media Type
A new Request for Comments is now available in online RFC libraries. RFC 9512 Title: YAML Media Type Author: R. Polli, E. Wilde, E. Aro Status: Informational Stream: IETF Date: February 2024 Mailbox:robipo...@gmail.com, erik.wi...@dret.net, eem...@gmail.com Pages: 13 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-httpapi-yaml-mediatypes-10.txt URL:https://www.rfc-editor.org/info/rfc9512 DOI:10.17487/RFC9512 This document registers the application/yaml media type and the +yaml structured syntax suffix with IANA. Both identify document components that are serialized according to the YAML specification. This document is a product of the Building Blocks for HTTP APIs 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 9530 on Digest Fields
A new Request for Comments is now available in online RFC libraries. RFC 9530 Title: Digest Fields Author: R. Polli, L. Pardue Status: Standards Track Stream: IETF Date: February 2024 Mailbox:robipo...@gmail.com, lu...@lucaspardue.com Pages: 32 Obsoletes: RFC 3230 I-D Tag:draft-ietf-httpbis-digest-headers-13.txt URL:https://www.rfc-editor.org/info/rfc9530 DOI:10.17487/RFC9530 This document defines HTTP fields that support integrity digests. The Content-Digest field can be used for the integrity of HTTP message content. The Repr-Digest field can be used for the integrity of HTTP representations. Want-Content-Digest and Want-Repr-Digest can be used to indicate a sender's interest and preferences for receiving the respective Integrity fields. This document obsoletes RFC 3230 and the Digest and Want-Digest HTTP fields. This document is a product of the HTTP 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 9421 on HTTP Message Signatures
A new Request for Comments is now available in online RFC libraries. RFC 9421 Title: HTTP Message Signatures Author: A. Backman, Ed., J. Richer, Ed., M. Sporny Status: Standards Track Stream: IETF Date: February 2024 Mailbox:richa...@amazon.com, i...@justin.richer.org, mspo...@digitalbazaar.com Pages: 95 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-httpbis-message-signatures-19.txt URL:https://www.rfc-editor.org/info/rfc9421 DOI:10.17487/RFC9421 This document describes a mechanism for creating, encoding, and verifying digital signatures or message authentication codes over components of an HTTP message. This mechanism supports use cases where the full HTTP message may not be known to the signer and where the message may be transformed (e.g., by intermediaries) before reaching the verifier. This document also describes a means for requesting that a signature be applied to a subsequent HTTP message in an ongoing HTTP exchange. This document is a product of the HTTP 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 9547 on Report from the IAB Workshop on Environmental Impact of Internet Applications and Systems, 2022
A new Request for Comments is now available in online RFC libraries. RFC 9547 Title: Report from the IAB Workshop on Environmental Impact of Internet Applications and Systems, 2022 Author: J. Arkko, C. S. Perkins, S. Krishnan Status: Informational Stream: IAB Date: February 2024 Mailbox:jari.ar...@ericsson.com, c...@csperkins.org, suresh.krish...@gmail.com Pages: 21 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-iab-ws-environmental-impacts-report-03.txt URL:https://www.rfc-editor.org/info/rfc9547 DOI:10.17487/RFC9547 Internet communications and applications have both environmental costs and benefits. The IAB ran an online workshop in December 2022 to explore and understand these impacts. The role of the workshop was to discuss the impacts and the evolving industry needs, and to identify areas for improvements and future work. A key goal of the workshop was to call further attention to the topic and bring together a diverse stakeholder community to discuss these issues. Note that this document is a report on the proceedings of the workshop. The views and positions documented in this report are those of the workshop participants and do not necessarily reflect IAB views and positions. This document is a product of the Internet Architecture Board. 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 9422 on The LIMITS SMTP Service Extension
A new Request for Comments is now available in online RFC libraries. RFC 9422 Title: The LIMITS SMTP Service Extension Author: N. Freed, J. Klensin Status: Standards Track Stream: IETF Date: February 2024 Mailbox:john-i...@jck.com Pages: 11 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-freed-smtp-limits-07.txt URL:https://www.rfc-editor.org/info/rfc9422 DOI:10.17487/RFC9422 This document defines a LIMITS extension for the Simple Mail Transfer Protocol (SMTP), including submission, as well as the Local Mail Transfer Protocol (LMTP). It also defines an associated limit registry. The extension provides the means for an SMTP, submission, or LMTP server to inform the client of limits the server intends to apply to the protocol during the current session. The client is then able to adapt its behavior in order to conform to those limits. 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 9534 on Simple Two-Way Active Measurement Protocol Extensions for Performance Measurement on a Link Aggregation Group
A new Request for Comments is now available in online RFC libraries. RFC 9534 Title: Simple Two-Way Active Measurement Protocol Extensions for Performance Measurement on a Link Aggregation Group Author: Z. Li, T. Zhou, J. Guo, G. Mirsky, R. Gandhi Status: Standards Track Stream: IETF Date: January 2024 Mailbox:li_zhenqi...@hotmail.com, zhoutian...@huawei.com, guo.j...@zte.com.cn, gregimir...@gmail.com, rgan...@cisco.com Pages: 8 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-ippm-stamp-on-lag-06.txt URL:https://www.rfc-editor.org/info/rfc9534 DOI:10.17487/RFC9534 This document extends Simple Two-way Active Measurement Protocol (STAMP) to implement performance measurement on every member link of a Link Aggregation Group (LAG). Knowing the measured metrics of each member link of a LAG enables operators to enforce a performance-based traffic steering policy across the member links. This document is a product of the IP Performance Measurement 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 9533 on One-Way and Two-Way Active Measurement Protocol Extensions for Performance Measurement on a Link Aggregation Group
A new Request for Comments is now available in online RFC libraries. RFC 9533 Title: One-Way and Two-Way Active Measurement Protocol Extensions for Performance Measurement on a Link Aggregation Group Author: Z. Li, T. Zhou, J. Guo, G. Mirsky, R. Gandhi Status: Standards Track Stream: IETF Date: January 2024 Mailbox:li_zhenqi...@hotmail.com, zhoutian...@huawei.com, guo.j...@zte.com.cn, gregimir...@gmail.com, rgan...@cisco.com Pages: 13 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-ippm-otwamp-on-lag-08.txt URL:https://www.rfc-editor.org/info/rfc9533 DOI:10.17487/RFC9533 This document defines extensions to the One-Way Active Measurement Protocol (OWAMP) and the Two-Way Active Measurement Protocol (TWAMP) to implement performance measurement on every member link of a Link Aggregation Group (LAG). Knowing the measured metrics of each member link of a LAG enables operators to enforce the performance-based traffic steering policy across the member links. This document is a product of the IP Performance Measurement 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 9532 on HTTP Proxy-Status Parameter for Next-Hop Aliases
A new Request for Comments is now available in online RFC libraries. RFC 9532 Title: HTTP Proxy-Status Parameter for Next-Hop Aliases Author: T. Pauly Status: Standards Track Stream: IETF Date: January 2024 Mailbox:tpa...@apple.com Pages: 7 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-httpbis-alias-proxy-status-07.txt URL:https://www.rfc-editor.org/info/rfc9532 DOI:10.17487/RFC9532 This document defines the HTTP Proxy-Status Parameter. This parameter carries the list of aliases and canonical names an intermediary received during DNS resolution as part of establishing a connection to the next hop. This document is a product of the HTTP 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 9527 on DHCPv6 Options for the Homenet Naming Authority
A new Request for Comments is now available in online RFC libraries. RFC 9527 Title: DHCPv6 Options for the Homenet Naming Authority Author: D. Migault, R. Weber, T. Mrugalski Status: Standards Track Stream: IETF Date: January 2024 Mailbox:daniel.miga...@ericsson.com, ralf.we...@akamai.com, tomasz.mrugal...@gmail.com Pages: 13 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-homenet-naming-architecture-dhc-options-24.txt URL:https://www.rfc-editor.org/info/rfc9527 DOI:10.17487/RFC9527 This document defines DHCPv6 options so that a Homenet Naming Authority (HNA) can automatically set the appropriate configuration and outsource the authoritative naming service for the home network. In most cases, the outsourcing mechanism is transparent for the end user. This document is a product of the Home Networking 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 9526 on Simple Provisioning of Public Names for Residential Networks
A new Request for Comments is now available in online RFC libraries. RFC 9526 Title: Simple Provisioning of Public Names for Residential Networks Author: D. Migault, R. Weber, M. Richardson, R. Hunter Status: Experimental Stream: IETF Date: January 2024 Mailbox:daniel.miga...@ericsson.com, ralf.we...@nominum.com, mcr+i...@sandelman.ca, v6...@globis.net Pages: 35 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-homenet-front-end-naming-delegation-27.txt URL:https://www.rfc-editor.org/info/rfc9526 DOI:10.17487/RFC9526 Home network owners may have devices or services hosted on their home network that they wish to access from the Internet (i.e., from a network outside of the home network). Home networks are increasingly numbered using IPv6 addresses, which in principle makes this access simpler, but accessing home networks from the Internet requires the names and IP addresses of these devices and services to be made available in the public DNS. This document describes how a Home Naming Authority (NHA) instructs the outsourced infrastructure to publish these pieces of information in the public DNS. The names and IP addresses of the home network are set in the Public Homenet Zone by the Homenet Naming Authority (HNA), which in turn instructs an outsourced infrastructure to publish the zone on behalf of the home network owner. This document is a product of the Home Networking Working Group of the IETF. EXPERIMENTAL: This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. 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 9522 on Overview and Principles of Internet Traffic Engineering
A new Request for Comments is now available in online RFC libraries. RFC 9522 Title: Overview and Principles of Internet Traffic Engineering Author: A. Farrel, Ed. Status: Informational Stream: IETF Date: January 2024 Mailbox:adr...@olddog.co.uk Pages: 73 Obsoletes: RFC 3272 I-D Tag:draft-ietf-teas-rfc3272bis-27.txt URL:https://www.rfc-editor.org/info/rfc9522 DOI:10.17487/RFC9522 This document describes the principles of traffic engineering (TE) in the Internet. The document is intended to promote better understanding of the issues surrounding traffic engineering in IP networks and the networks that support IP networking and to provide a common basis for the development of traffic-engineering capabilities for the Internet. The principles, architectures, and methodologies for performance evaluation and performance optimization of operational networks are also discussed. This work was first published as RFC 3272 in May 2002. This document obsoletes RFC 3272 by making a complete update to bring the text in line with best current practices for Internet traffic engineering and to include references to the latest relevant work in the IETF. This document is a product of the Traffic Engineering Architecture and Signaling 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 9519 on Update to the IANA SSH Protocol Parameters Registry Requirements
A new Request for Comments is now available in online RFC libraries. RFC 9519 Title: Update to the IANA SSH Protocol Parameters Registry Requirements Author: P. Yee Status: Standards Track Stream: IETF Date: January 2024 Mailbox:pe...@akayla.com Pages: 6 Updates:RFC 4250, RFC 4716, RFC 4819, RFC 8308 I-D Tag:draft-yee-ssh-iana-requirements-03.txt URL:https://www.rfc-editor.org/info/rfc9519 DOI:10.17487/RFC9519 This specification updates the registration policies for adding new entries to registries within the IANA "Secure Shell (SSH) Protocol Parameters" group of registries. Previously, the registration policy was generally IETF Review, as defined in RFC 8126, although a few registries require Standards Action. This specification changes it from IETF Review to Expert Review. This document updates RFCs 4250, 4716, 4819, and 8308. 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 9517 on A URN Namespace for the Data Documentation Initiative (DDI)
A new Request for Comments is now available in online RFC libraries. RFC 9517 Title: A URN Namespace for the Data Documentation Initiative (DDI) Author: J. Wackerow Status: Informational Stream: Independent Date: January 2024 Mailbox:joachim.wacke...@posteo.de Pages: 18 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-urn-ddi-06.txt URL:https://www.rfc-editor.org/info/rfc9517 DOI:10.17487/RFC9517 This document describes the Namespace Identifier (NID) "ddi" for Uniform Resource Names (URNs) used to identify resources that conform to the standards published by the Data Documentation Initiative (DDI) Alliance. The DDI Alliance is not affiliated with the Internet Engineering Task Force (IETF) or Internet Society (ISOC). This Independent Submission is not a standard nor does it have IETF community consensus. 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 9490 on Report from the IAB Workshop on Management Techniques in Encrypted Networks (M-TEN)
A new Request for Comments is now available in online RFC libraries. RFC 9490 Title: Report from the IAB Workshop on Management Techniques in Encrypted Networks (M-TEN) Author: M. Knodel, W. Hardaker, T. Pauly Status: Informational Stream: IAB Date: January 2024 Mailbox:mkno...@cdt.org, i...@hardakers.net, tpa...@apple.com Pages: 15 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-iab-m-ten-workshop-02.txt URL:https://www.rfc-editor.org/info/rfc9490 DOI:10.17487/RFC9490 The "Management Techniques in Encrypted Networks (M-TEN)" workshop was convened by the Internet Architecture Board (IAB) from 17 October 2022 to 19 October 2022 as a three-day online meeting. The workshop was organized in three parts to discuss ways to improve network management techniques in support of even broader adoption of encryption on the Internet. This report summarizes the workshop's discussion and identifies topics that warrant future work and consideration. Note that this document is a report on the proceedings of the workshop. The views and positions documented in this report are those of the expressed during the workshop by participants and do not necessarily reflect IAB views and positions. This document is a product of the Internet Architecture Board. 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 9467 on Relaxed Packet Counter Verification for Babel MAC Authentication
A new Request for Comments is now available in online RFC libraries. RFC 9467 Title: Relaxed Packet Counter Verification for Babel MAC Authentication Author: J. Chroboczek, T. Høiland-Jørgensen Status: Standards Track Stream: IETF Date: January 2024 Mailbox:j...@irif.fr, t...@toke.dk Pages: 8 Updates:RFC 8967 I-D Tag:draft-ietf-babel-mac-relaxed-05.txt URL:https://www.rfc-editor.org/info/rfc9467 DOI:10.17487/RFC9467 This document relaxes the packet verification rules defined in "MAC Authentication for the Babel Routing Protocol" (RFC 8967) in order to make the protocol more robust in the presence of packet reordering. This document updates RFC 8967. This document is a product of the Babel routing protocol 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 9521 on Bidirectional Forwarding Detection (BFD) for Generic Network Virtualization Encapsulation (Geneve)
A new Request for Comments is now available in online RFC libraries. RFC 9521 Title: Bidirectional Forwarding Detection (BFD) for Generic Network Virtualization Encapsulation (Geneve) Author: X. Min, G. Mirsky, S. Pallagatti, J. Tantsura, S. Aldrin Status: Standards Track Stream: IETF Date: January 2024 Mailbox:xiao.m...@zte.com.cn, gregimir...@gmail.com, santosh.pallaga...@gmail.com, jefftant.i...@gmail.com, aldrin.i...@gmail.com Pages: 11 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-nvo3-bfd-geneve-13.txt URL:https://www.rfc-editor.org/info/rfc9521 DOI:10.17487/RFC9521 This document describes the use of the Bidirectional Forwarding Detection (BFD) protocol in point-to-point Generic Network Virtualization Encapsulation (Geneve) unicast tunnels used to make up an overlay network. This document is a product of the Network Virtualization Overlays 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 9458 on Oblivious HTTP
A new Request for Comments is now available in online RFC libraries. RFC 9458 Title: Oblivious HTTP Author: M. Thomson, C. A. Wood Status: Standards Track Stream: IETF Date: January 2024 Mailbox:m...@lowentropy.net, c...@heapingbits.net Pages: 40 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-ohai-ohttp-10.txt URL:https://www.rfc-editor.org/info/rfc9458 DOI:10.17487/RFC9458 This document describes Oblivious HTTP, a protocol for forwarding encrypted HTTP messages. Oblivious HTTP allows a client to make multiple requests to an origin server without that server being able to link those requests to the client or to identify the requests as having come from the same client, while placing only limited trust in the nodes used to forward the messages. This document is a product of the Oblivious HTTP Application Intermediation 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 9552 on Distribution of Link-State and Traffic Engineering Information Using BGP
A new Request for Comments is now available in online RFC libraries. RFC 9552 Title: Distribution of Link-State and Traffic Engineering Information Using BGP Author: K. Talaulikar, Ed. Status: Standards Track Stream: IETF Date: December 2023 Mailbox:ketant.i...@gmail.com Pages: 60 Obsoletes: RFC 7752, RFC 9029 I-D Tag:draft-ietf-idr-rfc7752bis-17.txt URL:https://www.rfc-editor.org/info/rfc9552 DOI:10.17487/RFC9552 In many environments, a component external to a network is called upon to perform computations based on the network topology and the current state of the connections within the network, including Traffic Engineering (TE) information. This is information typically distributed by IGP routing protocols within the network. This document describes a mechanism by which link-state and TE information can be collected from networks and shared with external components using the BGP routing protocol. This is achieved using a BGP Network Layer Reachability Information (NLRI) encoding format. The mechanism applies to physical and virtual (e.g., tunnel) IGP links. The mechanism described is subject to policy control. Applications of this technique include Application-Layer Traffic Optimization (ALTO) servers and Path Computation Elements (PCEs). This document obsoletes RFC 7752 by completely replacing that document. It makes some small changes and clarifications to the previous specification. This document also obsoletes RFC 9029 by incorporating the updates that it made to RFC 7752. 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 9520 on Negative Caching of DNS Resolution Failures
A new Request for Comments is now available in online RFC libraries. RFC 9520 Title: Negative Caching of DNS Resolution Failures Author: D. Wessels, W. Carroll, M. Thomas Status: Standards Track Stream: IETF Date: December 2023 Mailbox:dwess...@verisign.com, wicarr...@verisign.com, mtho...@verisign.com Pages: 14 Updates:RFC 2308, RFC 4035, RFC 4697 I-D Tag:draft-ietf-dnsop-caching-resolution-failures-08.txt URL:https://www.rfc-editor.org/info/rfc9520 DOI:10.17487/RFC9520 In the DNS, resolvers employ caching to reduce both latency for end users and load on authoritative name servers. The process of resolution may result in one of three types of responses: (1) a response containing the requested data, (2) a response indicating the requested data does not exist, or (3) a non-response due to a resolution failure in which the resolver does not receive any useful information regarding the data's existence. This document concerns itself only with the third type. RFC 2308 specifies requirements for DNS negative caching. There, caching of TYPE 2 responses is mandatory and caching of TYPE 3 responses is optional. This document updates RFC 2308 to require negative caching for DNS resolution failures. RFC 4035 allows DNSSEC validation failure caching. This document updates RFC 4035 to require caching for DNSSEC validation failures. RFC 4697 prohibits aggressive requerying for NS records at a failed zone's parent zone. This document updates RFC 4697 to expand this requirement to all query types and to all ancestor zones. This document is a product of the Domain Name System Operations 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 9497 on Oblivious Pseudorandom Functions (OPRFs) Using Prime-Order Groups
A new Request for Comments is now available in online RFC libraries. RFC 9497 Title: Oblivious Pseudorandom Functions (OPRFs) Using Prime-Order Groups Author: A. Davidson, A. Faz-Hernandez, N. Sullivan, C. A. Wood Status: Informational Stream: IRTF Date: December 2023 Mailbox:alex.davidso...@gmail.com, armf...@cloudflare.com, nicholas.sullivan+i...@gmail.com, c...@heapingbits.net Pages: 61 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-irtf-cfrg-voprf-21.txt URL:https://www.rfc-editor.org/info/rfc9497 DOI:10.17487/RFC9497 An Oblivious Pseudorandom Function (OPRF) is a two-party protocol between a client and a server for computing the output of a Pseudorandom Function (PRF). The server provides the PRF private key, and the client provides the PRF input. At the end of the protocol, the client learns the PRF output without learning anything about the PRF private key, and the server learns neither the PRF input nor output. An OPRF can also satisfy a notion of 'verifiability', called a VOPRF. A VOPRF ensures clients can verify that the server used a specific private key during the execution of the protocol. A VOPRF can also be partially oblivious, called a POPRF. A POPRF allows clients and servers to provide public input to the PRF computation. This document specifies an OPRF, VOPRF, and POPRF instantiated within standard prime-order groups, including elliptic curves. This document is a product of the Crypto Forum Research Group (CFRG) in 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
RFC 9496 on The ristretto255 and decaf448 Groups
A new Request for Comments is now available in online RFC libraries. RFC 9496 Title: The ristretto255 and decaf448 Groups Author: H. de Valence, J. Grigg, M. Hamburg, I. Lovecruft, G. Tankersley, F. Valsorda Status: Informational Stream: IRTF Date: December 2023 Mailbox:i...@hdevalence.ca, i...@jackgrigg.com, i...@shiftleft.org, i...@en.ciph.re, i...@gtank.cc, i...@filippo.io Pages: 27 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-irtf-cfrg-ristretto255-decaf448-08.txt URL:https://www.rfc-editor.org/info/rfc9496 DOI:10.17487/RFC9496 This memo specifies two prime-order groups, ristretto255 and decaf448, suitable for safely implementing higher-level and complex cryptographic protocols. The ristretto255 group can be implemented using Curve25519, allowing existing Curve25519 implementations to be reused and extended to provide a prime-order group. Likewise, the decaf448 group can be implemented using edwards448. This document is a product of the Crypto Forum Research Group (CFRG) in 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
RFC 9475 on Messaging Use Cases and Extensions for Secure Telephone Identity Revisited (STIR)
A new Request for Comments is now available in online RFC libraries. RFC 9475 Title: Messaging Use Cases and Extensions for Secure Telephone Identity Revisited (STIR) Author: J. Peterson, C. Wendt Status: Standards Track Stream: IETF Date: December 2023 Mailbox:jon.peterson@team.neustar, chris-i...@chriswendt.net Pages: 10 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-ietf-stir-messaging-08.txt URL:https://www.rfc-editor.org/info/rfc9475 DOI:10.17487/RFC9475 Secure Telephone Identity Revisited (STIR) provides a means of attesting the identity of a telephone caller via a signed token in order to prevent impersonation of a calling party number, which is a key enabler for illegal robocalling. Similar impersonation is sometimes leveraged by bad actors in the text and multimedia messaging space. This document explores the applicability of STIR's Personal Assertion Token (PASSporT) and certificate issuance framework to text and multimedia messaging use cases, including support for both messages carried as a payload in SIP requests and messages sent in sessions negotiated by SIP. This document is a product of the Secure Telephone Identity Revisited 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 9518 on Centralization, Decentralization, and Internet Standards
A new Request for Comments is now available in online RFC libraries. RFC 9518 Title: Centralization, Decentralization, and Internet Standards Author: M. Nottingham Status: Informational Stream: Independent Date: December 2023 Mailbox:m...@mnot.net Pages: 22 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-nottingham-avoiding-internet-centralization-14.txt URL:https://www.rfc-editor.org/info/rfc9518 DOI:10.17487/RFC9518 This document discusses aspects of centralization that relate to Internet standards efforts. It argues that, while standards bodies have a limited ability to prevent many forms of centralization, they can still make contributions that assist in the decentralization of the Internet. 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
BCP 239, RFC 9501 on Open Participation Principle regarding Remote Registration Fee
A new Request for Comments is now available in online RFC libraries. BCP 239 RFC 9501 Title: Open Participation Principle regarding Remote Registration Fee Author: M. Kühlewind, J. Reed, R. Salz Status: Best Current Practice Stream: IETF Date: December 2023 Mailbox:mirja.kuehlew...@ericsson.com, jr...@akamai.com, rs...@akamai.com Pages: 6 See Also: BCP 239 I-D Tag:draft-ietf-shmoo-remote-fee-09.txt URL:https://www.rfc-editor.org/info/rfc9501 DOI:10.17487/RFC9501 This document outlines a principle for open participation that extends the open process principle defined in RFC 3935 by stating that there must be a free option for online participation to IETF meetings and, if possible, related IETF-hosted events. This document is a product of the Stay Home Meet Occasionally Online 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
RFC 9515 on Revision to Registration Procedures for Multiple BMP Registries
A new Request for Comments is now available in online RFC libraries. RFC 9515 Title: Revision to Registration Procedures for Multiple BMP Registries Author: J. Scudder Status: Standards Track Stream: IETF Date: December 2023 Mailbox:j...@juniper.net Pages: 3 Updates:RFC 7854 I-D Tag:draft-ietf-grow-bmp-registries-change-04.txt URL:https://www.rfc-editor.org/info/rfc9515 DOI:10.17487/RFC9515 This document updates RFC 7854, "BGP Monitoring Protocol (BMP)", by changing the registration procedures for several registries. Specifically, any BMP registry with a range of 32768-65530 designated "Specification Required" has that range redesignated as "First Come First Served". This document is a product of the Global Routing Operations 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 9500 on Standard Public Key Cryptography (PKC) Test Keys
A new Request for Comments is now available in online RFC libraries. RFC 9500 Title: Standard Public Key Cryptography (PKC) Test Keys Author: P. Gutmann, C. Bonnell Status: Informational Stream: IETF Date: December 2023 Mailbox:pgut...@cs.auckland.ac.nz, corey.bonn...@digicert.com Pages: 28 Updates/Obsoletes/SeeAlso: None I-D Tag:draft-gutmann-testkeys-05.txt URL:https://www.rfc-editor.org/info/rfc9500 DOI:10.17487/RFC9500 This document provides a set of standard Public Key Cryptography (PKC) test keys that may be used wherever pre-generated keys and associated operations like digital signatures are required. Like the European Institute for Computer Antivirus Research (EICAR) virus test and the Generic Test for Unsolicited Bulk Email (GTUBE) spam test files, these publicly known test keys can be detected and recognised by applications consuming them as being purely for testing purposes without assigning any security properties to them. 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
