Test Account

document updates RFCs 9146 and 9147. This document is a product of the Transport Layer Security Working Group of the IETF. 3/3

the Datagram Transport Layer Security (DTLS) protocol versions 1.2 and 1.3. Implementations offering the CID functionality described in RFCs 9146 and 9147 are encouraged to also provide the RRC functionality described in this document. For this reason, this 2/3

RFC 9853: Return Routability Check for DTLS 1.2 and 1.3, H. Tschofenig, Ed., et al., https://www.rfc-editor.org/info/rfc9853 #RFC This document specifies a Return Routability Check (RRC) subprotocol for use in the context of the Connection ID (CID) construct for 1/3

validating requested schedules and reporting scheduling statuses. This document is a product of the Network Modeling Working Group of the IETF. 3/3

based on date and time. For the sake of better modularity, the YANG module includes a set of recurrence-related groupings with varying levels of representation (i.e., from basic to advanced) to accommodate a variety of requirements. It also defines groupings for 2/3

RFC 9922: A Common YANG Data Model for Scheduling, Q. Ma, Ed., et al., https://www.rfc-editor.org/info/rfc9922 #RFC This document defines common types and groupings that are meant to be used for scheduling purposes, such as events, policies, services, or resources 1/3

product of the Limited Additional Mechanisms for PKIX and SMIME Working Group of the IETF. 3/3

(ML-KEM) is a quantum-resistant Key Encapsulation Mechanism. This document specifies the conventions for using the ML-KEM in X.509 Public Key Infrastructure. The conventions for the subject public keys and private keys are also specified. This document is a 2/3

RFC 9935: Internet X.509 Public Key Infrastructure - Algorithm Identifiers for the Module-Lattice-Based Key-Encapsulation Mechanism (ML-KEM), S. Turner, et al., https://www.rfc-editor.org/info/rfc9935 #RFC The Module-Lattice-Based Key-Encapsulation Mechanism 1/3

is a product of the Limited Additional Mechanisms for PKIX and SMIME Working Group of the IETF. 4/4

document specifies the conventions for using ML-KEM with the Cryptographic Message Syntax (CMS) using the KEMRecipientInfo structure defined in "Using Key Encapsulation Mechanism (KEM) Algorithms in the Cryptographic Message Syntax (CMS)" (RFC 9629). This document 3/4

sets for the ML-KEM algorithm are specified by the US National Institute of Standards and Technology (NIST) in FIPS 203. In order of increasing security strength (and decreasing performance), these parameter sets are ML-KEM-512, ML-KEM-768, and ML-KEM-1024. This 2/4

RFC 9936: Use of ML-KEM in the Cryptographic Message Syntax (CMS), P. Julien, et al., https://www.rfc-editor.org/info/rfc9936 #RFC Module-Lattice-Based Key-Encapsulation Mechanism (ML-KEM) is a quantum-resistant Key Encapsulation Mechanism (KEM). Three parameter 1/4

product of the Limited Additional Mechanisms for PKIX and SMIME Working Group of the IETF. 3/3

(ML-KEM) is a quantum-resistant Key Encapsulation Mechanism. This document specifies the conventions for using the ML-KEM in X.509 Public Key Infrastructure. The conventions for the subject public keys and private keys are also specified. This document is a 2/3

RFC 9935: Internet X.509 Public Key Infrastructure - Algorithm Identifiers for the Module-Lattice-Based Key-Encapsulation Mechanism (ML-KEM), S. Turner, et al., https://www.rfc-editor.org/info/rfc9935 #RFC The Module-Lattice-Based Key-Encapsulation Mechanism 1/3

security considerations that apply to data sent by the client before this request is confirmed and adds new requirements to RFCs 9112 and 9298 to avoid related security issues. This document is a product of the HTTP Working Group of the IETF. 2/2

RFC 9931: Security Considerations for Optimistic Protocol Transitions in HTTP/1.1, B. Schwartz, https://www.rfc-editor.org/info/rfc9931 #RFC In HTTP/1.1, the client can request a change to a new protocol on the existing connection. This document discusses the 1/2

libraries. This document specifies a standard file format for this purpose, similar to how RFC 7468 defines other Privacy-Enhanced Mail (PEM) file formats. 2/2

RFC 9934: Privacy-Enhanced Mail (PEM) File Format for Encrypted ClientHello (ECH), S. Farrell, https://www.rfc-editor.org/info/rfc9934 #RFC Encrypted ClientHello (ECH) key pairs need to be configured into TLS servers, which can be built using different TLS 1/2

Transport Layer Security Working Group of the IETF. 2/2

RFC 9849: TLS Encrypted Client Hello, E. Rescorla, et al., https://www.rfc-editor.org/info/rfc9849 #RFC This document describes a mechanism in Transport Layer Security (TLS) for encrypting a message under a server public key. This document is a product of the 1/2

connection to the server. This specification provides a mechanism for conveying the ECH configuration information via DNS, using a SVCB or HTTPS resource record (RR). This document is a product of the Transport Layer Security Working Group of the IETF. 2/2

RFC 9848: Bootstrapping TLS Encrypted ClientHello with DNS Service Bindings, B. Schwartz, et al., https://www.rfc-editor.org/info/rfc9848 #RFC To use TLS Encrypted ClientHello (ECH), the client needs to learn the ECH configuration for a server before it attempts a 1/2

a product of the Limited Additional Mechanisms for PKIX and SMIME Working Group of the IETF. 2/2

RFC 9939: PKCS #8: Private-Key Information Content Types, J. Mandel, et al., https://www.rfc-editor.org/info/rfc9939 #RFC This document defines PKCS #8 content types for use with PrivateKeyInfo and EncryptedPrivateKeyInfo as specified in RFC 5958. This document is 1/2

procedures and facilitate their consistent implementation with chairs and administrators. This document is a product of the MODeration PrOceDures Working Group of the IETF. 3/3

9245 by establishing a policy for the moderation of disruptive participation across the IETF's various public contribution channels and discussion fora. It establishes guardrails for moderation and a moderator team. That team will develop a set of moderation 2/3

RFC 9945: IETF Community Moderation, L. Eggert, Ed., et al., https://www.rfc-editor.org/info/rfc9945 #RFC The IETF community will treat people with kindness and grace, but not endless patience. This memo obsoletes RFCs 3683 and 3934, and it updates RFCs 2418 and 1/3

server. This document obsoletes RFC 7170 and updates RFC 9427 by moving all TEAP specifications from those documents to this one. This document is a product of the EAP Method Update Working Group of the IETF. 3/3