⌕ Поиск по атласу

IETF · RFC

Опубликованные RFC, связи обновления и замены, официальные статусы и русские переводы.

Реестр · 9 842 документов

RFC99732026-07-01

TLS 1.3 Extension for Using Certificates with an External Pre-Shared Key

TLS 1.3 Extension for Using Certificates with an External Pre-Shared Key

This document specifies a TLS 1.3 extension that allows TLS clients and servers to authenticate with certificates and provide confidentiality based on encryption with a symmetric key from the usual key agreement algorithm and an external pre-shared key (PSK). This Standards Track RFC obsoletes RFC 8773, which was an Experimental RFC.

RFC99722026-05-01

Advanced BGP Monitoring Protocol (BMP) Statistics Types

Advanced BGP Monitoring Protocol (BMP) Statistics Types

The BGP Monitoring Protocol (BMP) described in RFC 7854 defines statistics message types to observe events that occur on a monitored router. This document defines new statistics types to monitor BMP Adj-RIB-In and Adj-RIB-Out Routing Information Bases (RIBs).

RFC99712026-08-01

Multiple Loss Ratio Search

Multiple Loss Ratio Search

This document describes an alternative to throughput in "Benchmarking Methodology for Network Interconnect Devices" (RFC 2544) by defining a new methodology called Multiple Loss Ratio Search (MLRsearch). MLRsearch aims to minimize Search Duration, support multiple loss ratio goals, and improve result repeatability and comparability. MLRsearch is motivated by the pressing need to address the challe…

RFC99702026-06-01

Connected Identity for Secure Telephone Identity Revisited (STIR)

Connected Identity for Secure Telephone Identity Revisited (STIR)

The Session Initiation Protocol (SIP) Identity header field conveys cryptographic identity information about the originators of SIP requests. However, the Secure Telephone Identity Revisited (STIR) framework provides no means for determining the identity of the called party in a conventional telephone-calling scenario. This document updates prior guidance on the "connected identity" problem to ref…

RFC99692026-05-01

Report from the IAB Workshop on AI-CONTROL

Report from the IAB Workshop on AI-CONTROL

The AI-CONTROL Workshop was convened by the Internet Architecture Board (IAB) in September 2024. This report summarizes its significant points of discussion and identifies topics that may warrant further consideration and work. 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 …

RFC99682026-05-01

Report from the IAB Workshop on the Next Era of Network Management Operations (NEMOPS)

Report from the IAB Workshop on the Next Era of Network Management Operations (NEMOPS)

The "Next Era of Network Management Operations (NEMOPS)" workshop was convened by the Internet Architecture Board (IAB) from December 3-5, 2024 as a three-day online meeting. It builds on a previous 2002 workshop, the outcome of which was documented in RFC 3535, identifying 14 operator requirements for consideration in future network management protocol design and related data models, along with s…

RFC99672026-05-01

System for Cross-Domain Identity Management (SCIM) Profile for Security Event Tokens (SETs)

System for Cross-Domain Identity Management (SCIM) Profile for Security Event Tokens (SETs)

This specification defines a set of System for Cross-domain Identity Management (SCIM) Security Events using the Security Event Token (SET) specification (RFC 8417) to enable the asynchronous exchange of messages between SCIM service providers and receivers. This specification updates RFC 7643 by defining additional attributes for the "urn:ietf:params:scim:schemas:core:2.0:ServiceProviderConfig" s…

RFC99662026-05-01

Bootstrapped TLS Authentication with Proof of Knowledge

Bootstrapped TLS Authentication with Proof of Knowledge

This document defines a mechanism that enables a bootstrapping device to establish trust and mutually authenticate against a TLS server. Bootstrapping devices have a public/private key pair; this mechanism enables a TLS server to prove to the device that it knows the public key and enables the device to prove to the TLS server that it knows the private key. The mechanism leverages existing Device …

RFC99652026-05-01

The eap.arpa. Domain and Extensible Authentication Protocol (EAP) Provisioning

The eap.arpa. Domain and Extensible Authentication Protocol (EAP) Provisioning

This document defines the eap.arpa. domain for use only in Network Access Identifiers (NAIs) as a way for Extensible Authentication Protocol (EAP) peers to signal to EAP servers that they wish to obtain limited, and unauthenticated, network access. EAP peers signal which kind of access is required via certain predefined identifiers that use the NAI format of RFC 7542. A table of identifiers and me…

RFC99642026-05-01

ML-DSA for JSON Object Signing and Encryption (JOSE) and CBOR Object Signing and Encryption (COSE)

ML-DSA for JSON Object Signing and Encryption (JOSE) and CBOR Object Signing and Encryption (COSE)

This document specifies JSON Object Signing and Encryption (JOSE) and CBOR Object Signing and Encryption (COSE) serializations for the Module-Lattice-Based Digital Signature Standard (ML-DSA), a Post-Quantum Cryptography (PQC) digital signature scheme defined in US NIST FIPS 204.

RFC99632026-04-01

Legacy RSASSA-PKCS1-v1_5 Code Points for TLS 1.3

Legacy RSASSA-PKCS1-v1_5 Code Points for TLS 1.3

This document allocates code points for the use of RSASSA-PKCS1-v1_5 with client certificates in TLS 1.3. This removes an obstacle for some deployments to migrate to TLS 1.3.

RFC99622026-05-01

A Decentralized Locator/ID Separation Protocol Mapping System (LISP-Decent)

A Decentralized Locator/ID Separation Protocol Mapping System (LISP-Decent)

This document describes how the Locator/ID Separation Protocol (LISP) Mapping System can be distributed for scale and decentralized for management, while maintaining trust among data plane nodes. This is an Informational RFC and should be used by LISP-Decent implementations to interoperate with each other.

RFC99612026-04-01

MPLS Segment Routing Point-to-Multipoint (P2MP) Policy Ping

MPLS Segment Routing Point-to-Multipoint (P2MP) Policy Ping

Segment Routing (SR) Point-to-Multipoint (P2MP) Policies are used to define and manage explicit P2MP paths within a network. These policies are typically calculated via a controller-based mechanism and installed via, e.g., a Path Computation Element (PCE). In other cases, these policies can be installed using the Network Configuration Protocol (NETCONF) / YANG or a Command Line Interface (CLI). Th…

RFC99602026-04-01

Segment Routing Point-to-Multipoint Policy

Segment Routing Point-to-Multipoint Policy

The Point-to-Multipoint (P2MP) Policy enables creation of P2MP trees for efficient multipoint packet delivery in a Segment Routing (SR) domain. This document specifies the architecture, signaling, and procedures for SR P2MP Policies with Segment Routing over MPLS (SR-MPLS) and Segment Routing over IPv6 (SRv6). It defines the SR P2MP Policy construct, candidate paths (CPs) of an SR P2MP Policy, and…

RFC99592026-05-01

Careful Resume: Convergence of Congestion Control from Retained State

Careful Resume: Convergence of Congestion Control from Retained State

This document specifies a cautious method for Internet transports that enables fast startup of Congestion Control (CC) for a wide range of connections, known as "Careful Resume". It reuses a set of computed CC parameters that are based on previously observed path characteristics between the same pair of transport endpoints. These parameters are saved, allowing them to be later used to modify the C…

RFC99582026-06-01

Post-Quantum Cryptography for Engineers

Post-Quantum Cryptography for Engineers

The advent of a cryptographically relevant quantum computer (CRQC) would render state-of-the-art, traditional public key algorithms deployed today obsolete, as the mathematical assumptions underpinning their security would no longer hold. To address this, protocols and infrastructure must transition to post-quantum algorithms, which are designed to resist both traditional and quantum attacks. This…

RFC99572026-05-01

The DOCSIS Queue Protection Algorithm to Preserve Low Latency

The DOCSIS Queue Protection Algorithm to Preserve Low Latency

This Informational RFC explains the specification of the queue protection algorithm introduced into Data-Over-Cable Service Interface Specification (DOCSIS) technology at version 3.1. A shared low-latency queue relies on the non-queue-building behaviour of every traffic flow using it. However, some flows might not take such care, either accidentally or maliciously. If a queue is about to exceed a …

RFC99562026-05-01

A Non-Queue-Building Per-Hop Behavior (NQB PHB) for Differentiated Services

A Non-Queue-Building Per-Hop Behavior (NQB PHB) for Differentiated Services

This document specifies characteristics of a Non-Queue-Building Per-Hop Behavior (NQB PHB). The NQB PHB provides a shallow-buffered, best-effort service as a complement to a Default deep-buffered, best-effort service for Internet services. The purpose of this NQB PHB is to provide a separate queue that enables smooth (i.e., non-bursty), low-data-rate, application-limited traffic microflows, to avo…

RFC99552026-07-01

Hybrid Signature Spectrums

Hybrid Signature Spectrums

This document describes classification of design goals and security considerations for hybrid digital signature schemes, including proof composability, non-separability of the component signatures given a hybrid signature, backwards and forwards compatibility, hybrid generality, and Simultaneous Verification (SV).

RFC99542026-07-01

Hybrid Key Exchange in TLS 1.3

Hybrid Key Exchange in TLS 1.3

Hybrid key exchange refers to using multiple key exchange algorithms simultaneously and combining the result with the goal of providing security even if a way is found to defeat the encryption for all but one of the component algorithms. It is motivated by the transition to post-quantum cryptography. This document provides a construction for hybrid key exchange in the Transport Layer Security (TLS…

RFC99532026-03-01

DNS over CoAP (DoC)

DNS over CoAP (DoC)

This document defines a protocol for exchanging DNS queries (OPCODE 0) over the Constrained Application Protocol (CoAP). These CoAP messages can be protected by (D)TLS-Secured CoAP or Object Security for Constrained RESTful Environments (OSCORE) to provide encrypted DNS message exchange for constrained devices in the Internet of Things (IoT).

RFC99522026-03-01

Application-Layer Protocol Negotiation (ALPN) ID for CoAP over DTLS

Application-Layer Protocol Negotiation (ALPN) ID for CoAP over DTLS

This document specifies an Application-Layer Protocol Negotiation (ALPN) ID for Constrained Application Protocol (CoAP) services that are secured by DTLS.

RFC99512026-04-01

Export of Delay Performance Metrics in IP Flow Information Export (IPFIX)

Export of Delay Performance Metrics in IP Flow Information Export (IPFIX)

This document specifies new IP Flow Information Export (IPFIX) Information Elements to export the On-Path delay at each Operations, Administration, and Maintenance (OAM) transit and decapsulating nodes. The On-Path delay is defined as the delay between the OAM header encapsulating node and each OAM header transit and OAM header decapsulating nodes. This delay measurement is computed by an On-Path …

RFC99502026-03-01

A YANG Data Model for Terminal Access Controller Access-Control System Plus (TACACS+)

A YANG Data Model for Terminal Access Controller Access-Control System Plus (TACACS+)

This document defines a Terminal Access Controller Access-Control System Plus (TACACS+) client YANG module that augments the System Management data model, defined in RFC 7317, to allow devices to make use of TACACS+ servers for centralized Authentication, Authorization, and Accounting (AAA). Specifically, the TACACS+ YANG module can be used to manage TACACS+ over TLS. This document obsoletes RFC 9…

RFC99492026-04-01

BUSA-TLS: Mandatory Audio Component (MAC) Pre-Shared Key (PSK) Derivation for TLS 1.3 Using 2 Live Crew's "Banned in the U.S.A."

BUSA-TLS: Mandatory Audio Component (MAC) Pre-Shared Key (PSK) Derivation for TLS 1.3 Using 2 Live Crew's "Banned in the U.S.A."

TLS 1.3 (RFC 8446) eliminates null cipher suites entirely. However, one vestigial zero remains in the key schedule: when no Pre-Shared Key (PSK) is used, the Input Keying Material (IKM) for the initial HKDF-Extract operation is a string of zero bytes. This document specifies that this zero-byte IKM MUST be replaced with the SHA-256 digest of the raw PCM audio data of "Banned in the U.S.A." by 2 Li…

RFC99482026-04-01

Internet Protocol Police (IPP) - Schedule of Punishments

Internet Protocol Police (IPP) - Schedule of Punishments

The Internet Protocol Police (IPP) is in charge of punishing willful infractions of the Collected Wisdom of the IETF community. This document sets out the schedule of punishments for such infractions.

RFC99472026-03-01

Application of the Alternate-Marking Method to the Segment Routing Header

Application of the Alternate-Marking Method to the Segment Routing Header

This document describes an alternative experimental approach for the application of the Alternate-Marking Method to Segment Routing for IPv6 (SRv6). It uses an experimental TLV in the Segment Routing Header (SRH); thus, participation in this experiment should be between coordinating parties in a controlled domain. This approach has potential scaling and simplification benefits over the technique d…

RFC99462026-04-01

The UDP Speed Test Protocol (UDPSTP) for One-Way IP Capacity Metric Measurement

The UDP Speed Test Protocol (UDPSTP) for One-Way IP Capacity Metric Measurement

This document addresses the problem of protocol support for measuring One-Way IP Capacity metrics specified by RFC 9097. The Method of Measurement discussed in that RFC requires a feedback channel from the receiver to control the sender's transmission rate in near real-time. This document defines the UDP Speed Test Protocol (UDPSTP) for conducting measurements as described in RFC 9097 and other re…

RFC99452026-02-01

IETF Community Moderation

IETF Community Moderation

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 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 se…

RFC99442026-05-01

Device Schema Extensions to the System for Cross-Domain Identity Management (SCIM) Model

Device Schema Extensions to the System for Cross-Domain Identity Management (SCIM) Model

The initial core schema for the System for Cross-domain Identity Management (SCIM) was designed for provisioning users. This memo specifies schema extensions that enable provisioning of devices using various underlying bootstrapping systems such as Wi-Fi Easy Connect, FIDO device onboarding vouchers, Bluetooth Low Energy (BLE) passcodes, and MAC Authenticated Bypass (MAB).