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

IETF · RFC

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

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

RFC92192022-04-01

S/MIME Signature Verification Extension to the JSON Meta Application Protocol (JMAP)

S/MIME Signature Verification Extension to the JSON Meta Application Protocol (JMAP)

This document specifies an extension to "The JSON Meta Application Protocol (JMAP) for Mail" (RFC 8621) for returning the S/MIME signature verification status.

RFC92182022-06-01

Extensible Prioritization Scheme for HTTP

Extensible Prioritization Scheme for HTTP

This document describes a scheme that allows an HTTP client to communicate its preferences for how the upstream server prioritizes responses to its requests, and also allows a server to hint to a downstream intermediary how its responses should be prioritized when they are forwarded. This document defines the Priority header field for communicating the initial priority in an HTTP version-independe…

RFC92172022-03-01

Current Open Questions in Path-Aware Networking

Current Open Questions in Path-Aware Networking

In contrast to the present Internet architecture, a path-aware internetworking architecture has two important properties: it exposes the properties of available Internet paths to endpoints, and it provides for endpoints and applications to use these properties to select paths through the Internet for their traffic. While this property of "path awareness" already exists in many Internet-connected n…

RFC92162022-04-01

S/MIME Example Keys and Certificates

S/MIME Example Keys and Certificates

The S/MIME development community benefits from sharing samples of signed or encrypted data. This document facilitates such collaboration by defining a small set of X.509v3 certificates and keys for use when generating such samples.

RFC92152022-03-01

Using GOST R 34.10-2012 and GOST R 34.11-2012 Algorithms with the Internet X.509 Public Key Infrastructure

Using GOST R 34.10-2012 and GOST R 34.11-2012 Algorithms with the Internet X.509 Public Key Infrastructure

This document describes encoding formats, identifiers, and parameter formats for the GOST R 34.10-2012 and GOST R 34.11-2012 algorithms for use in the Internet X.509 Public Key Infrastructure (PKI). This specification is developed to facilitate implementations that wish to support the GOST algorithms. This document does not imply IETF endorsement of the cryptographic algorithms used in this docume…

RFC92142022-04-01

OSPFv3 Code Point for MPLS LSP Ping

OSPFv3 Code Point for MPLS LSP Ping

IANA has created "Protocol in the Segment ID Sub-TLV" and "Protocol in Label Stack Sub-TLV of Downstream Detailed Mapping TLV" registries under the "Multiprotocol Label Switching (MPLS) Label Switched Paths (LSPs) Ping Parameters" registry. RFC 8287 defines the code points for Open Shortest Path First (OSPF) and Intermediate System to Intermediate System (IS-IS) protocols. This document specifies …

RFC92132022-06-01

Targeted HTTP Cache Control

Targeted HTTP Cache Control

This specification defines a convention for HTTP response header fields that allow cache directives to be targeted at specific caches or classes of caches. It also defines one such header field, the CDN-Cache-Control response header field, which is targeted at content delivery network (CDN) caches.

RFC92122022-03-01

Commercial National Security Algorithm (CNSA) Suite Cryptography for Secure Shell (SSH)

Commercial National Security Algorithm (CNSA) Suite Cryptography for Secure Shell (SSH)

The United States Government has published the National Security Agency (NSA) Commercial National Security Algorithm (CNSA) Suite, which defines cryptographic algorithm policy for national security applications. This document specifies the conventions for using the United States National Security Agency's CNSA Suite algorithms with the Secure Shell Transport Layer Protocol and the Secure Shell Aut…

RFC92112022-06-01

The Cache-Status HTTP Response Header Field

The Cache-Status HTTP Response Header Field

To aid debugging, HTTP caches often append header fields to a response, explaining how they handled the request in an ad hoc manner. This specification defines a standard mechanism to do so that is aligned with HTTP's caching model.

RFC92102022-03-01

DNS Transport over TCP - Operational Requirements

DNS Transport over TCP - Operational Requirements

This document updates RFCs 1123 and 1536. This document requires the operational practice of permitting DNS messages to be carried over TCP on the Internet as a Best Current Practice. This operational requirement is aligned with the implementation requirements in RFC 7766. The use of TCP includes both DNS over unencrypted TCP as well as over an encrypted TLS session. The document also considers th…

RFC92092022-06-01

The Proxy-Status HTTP Response Header Field

The Proxy-Status HTTP Response Header Field

This document defines the Proxy-Status HTTP response field to convey the details of an intermediary's response handling, including generated errors.

RFC92082022-03-01

IMAP QUOTA Extension

IMAP QUOTA Extension

This document defines a QUOTA extension of the Internet Message Access Protocol (IMAP) (see RFCs 3501 and 9051) that permits administrative limits on resource usage (quotas) to be manipulated through the IMAP protocol. This document obsoletes RFC 2087 but attempts to remain backwards compatible whenever possible.

RFC92072022-03-01

OAuth 2.0 Authorization Server Issuer Identification

OAuth 2.0 Authorization Server Issuer Identification

This document specifies a new parameter called iss. This parameter is used to explicitly include the issuer identifier of the authorization server in the authorization response of an OAuth authorization flow. The iss parameter serves as an effective countermeasure to "mix-up attacks".

RFC92062022-03-01

Commercial National Security Algorithm (CNSA) Suite Cryptography for Internet Protocol Security (IPsec)

Commercial National Security Algorithm (CNSA) Suite Cryptography for Internet Protocol Security (IPsec)

The United States Government has published the National Security Agency's Commercial National Security Algorithm (CNSA) Suite, which defines cryptographic algorithm policy for national security applications. This document specifies the conventions for using the United States National Security Agency's CNSA Suite algorithms in Internet Protocol Security (IPsec). It applies to the capabilities, conf…

RFC92052022-06-01

Building Protocols with HTTP

Building Protocols with HTTP

Applications often use HTTP as a substrate to create HTTP-based APIs. This document specifies best practices for writing specifications that use HTTP to define new application protocols. It is written primarily to guide IETF efforts to define application protocols using HTTP for deployment on the Internet but might be applicable in other situations. This document obsoletes RFC 3205.

RFC92042022-06-01

QPACK: Field Compression for HTTP/3

QPACK: Field Compression for HTTP/3

This specification defines QPACK: a compression format for efficiently representing HTTP fields that is to be used in HTTP/3. This is a variation of HPACK compression that seeks to reduce head-of-line blocking.

RFC92032022-08-01

The Object Security for Constrained RESTful Environments (OSCORE) Profile of the Authentication and Authorization for Constrained Environments (ACE) Framework

The Object Security for Constrained RESTful Environments (OSCORE) Profile of the Authentication and Authorization for Constrained Environments (ACE) Framework

This document specifies a profile for the Authentication and Authorization for Constrained Environments (ACE) framework. It utilizes Object Security for Constrained RESTful Environments (OSCORE) to provide communication security and proof-of-possession for a key owned by the client and bound to an OAuth 2.0 access token.

RFC92022022-08-01

Datagram Transport Layer Security (DTLS) Profile for Authentication and Authorization for Constrained Environments (ACE)

Datagram Transport Layer Security (DTLS) Profile for Authentication and Authorization for Constrained Environments (ACE)

This specification defines a profile of the Authentication and Authorization for Constrained Environments (ACE) framework that allows constrained servers to delegate client authentication and authorization. The protocol relies on DTLS version 1.2 or later for communication security between entities in a constrained network using either raw public keys or pre-shared keys. A resource-constrained ser…

RFC92012022-08-01

Additional OAuth Parameters for Authentication and Authorization for Constrained Environments (ACE)

Additional OAuth Parameters for Authentication and Authorization for Constrained Environments (ACE)

This specification defines new parameters and encodings for the OAuth 2.0 token and introspection endpoints when used with the framework for Authentication and Authorization for Constrained Environments (ACE). These are used to express the proof-of-possession (PoP) key the client wishes to use, the PoP key that the authorization server has selected, and the PoP key the resource server uses to auth…

RFC92002022-08-01

Authentication and Authorization for Constrained Environments Using the OAuth 2.0 Framework (ACE-OAuth)

Authentication and Authorization for Constrained Environments Using the OAuth 2.0 Framework (ACE-OAuth)

This specification defines a framework for authentication and authorization in Internet of Things (IoT) environments called ACE-OAuth. The framework is based on a set of building blocks including OAuth 2.0 and the Constrained Application Protocol (CoAP), thus transforming a well-known and widely used authorization solution into a form suitable for IoT devices. Existing specifications are used wher…

RFC91992022-03-01

Considerations for Large Authoritative DNS Server Operators

Considerations for Large Authoritative DNS Server Operators

Recent research work has explored the deployment characteristics and configuration of the Domain Name System (DNS). This document summarizes the conclusions from these research efforts and offers specific, tangible considerations or advice to authoritative DNS server operators. Authoritative server operators may wish to follow these considerations to improve their DNS services. It is possible that…

RFC91982022-05-01

Advanced Unidirectional Route Assessment (AURA)

Advanced Unidirectional Route Assessment (AURA)

This memo introduces an advanced unidirectional route assessment (AURA) metric and associated measurement methodology based on the IP Performance Metrics (IPPM) framework (RFC 2330). This memo updates RFC 2330 in the areas of path-related terminology and path description, primarily to include the possibility of parallel subpaths between a given Source and Destination pair, owing to the presence of…

RFC91972022-05-01

Data Fields for In Situ Operations, Administration, and Maintenance (IOAM)

Data Fields for In Situ Operations, Administration, and Maintenance (IOAM)

In situ Operations, Administration, and Maintenance (IOAM) collects operational and telemetry information in the packet while the packet traverses a path between two points in the network. This document discusses the data fields and associated data types for IOAM. IOAM-Data-Fields can be encapsulated into a variety of protocols, such as Network Service Header (NSH), Segment Routing, Generic Networ…

RFC91962022-02-01

YANG Modules Describing Capabilities for Systems and Datastore Update Notifications

YANG Modules Describing Capabilities for Systems and Datastore Update Notifications

This document defines two YANG modules, "ietf-system-capabilities" and "ietf-notification-capabilities". The module "ietf-system-capabilities" provides a placeholder structure that can be used to discover YANG-related system capabilities for servers. The module can be used to report capability information from the server at runtime or at implementation time by making use of the YANG instance data …

RFC91952022-02-01

A File Format for YANG Instance Data

A File Format for YANG Instance Data

There is a need to document data defined in YANG models at design time, implementation time, or when a live server is unavailable. This document specifies a standard file format for YANG instance data, which follows the syntax and semantics of existing YANG models and annotates it with metadata.

RFC91942022-10-01

A YANG Module for IS-IS Reverse Metric

A YANG Module for IS-IS Reverse Metric

This document defines a YANG module for managing the reverse metric extension to the Intermediate System to Intermediate System (IS-IS) intra-domain routing information exchange protocol.

RFC91932022-06-01

Sensor Measurement Lists (SenML) Fields for Indicating Data Value Content-Format

Sensor Measurement Lists (SenML) Fields for Indicating Data Value Content-Format

The Sensor Measurement Lists (SenML) media types support multiple types of values, from numbers to text strings and arbitrary binary Data Values. In order to facilitate processing of binary Data Values, this document specifies a pair of new SenML fields for indicating the content format of those binary Data Values, i.e., their Internet media type, including parameters as well as any content coding…

RFC91922022-02-01

Network Service Header (NSH) Fixed-Length Context Header Allocation

Network Service Header (NSH) Fixed-Length Context Header Allocation

The Network Service Header (NSH) specification defines two possible methods of including metadata (MD): MD Type 0x1 and MD Type 0x2. MD Type 0x1 uses a fixed-length Context Header. The allocation of this Context Header, i.e., its structure and semantics, has not been standardized. This memo defines the Timestamp Context Header, which is an NSH fixed-length Context Header that incorporates the pack…

RFC91912022-02-01

Handling Large Certificates and Long Certificate Chains in TLS-Based EAP Methods

Handling Large Certificates and Long Certificate Chains in TLS-Based EAP Methods

The Extensible Authentication Protocol (EAP), defined in RFC 3748, provides a standard mechanism for support of multiple authentication methods. EAP-TLS and other TLS-based EAP methods are widely deployed and used for network access authentication. Large certificates and long certificate chains combined with authenticators that drop an EAP session after only 40 - 50 round trips is a major deployme…

RFC91902022-02-01

EAP-TLS 1.3: Using the Extensible Authentication Protocol with TLS 1.3

EAP-TLS 1.3: Using the Extensible Authentication Protocol with TLS 1.3

The Extensible Authentication Protocol (EAP), defined in RFC 3748, provides a standard mechanism for support of multiple authentication methods. This document specifies the use of EAP-TLS with TLS 1.3 while remaining backwards compatible with existing implementations of EAP-TLS. TLS 1.3 provides significantly improved security and privacy, and reduced latency when compared to earlier versions of T…