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

IETF · RFC

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

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

RFC86122019-05-01

DDoS Open Threat Signaling (DOTS) Requirements

DDoS Open Threat Signaling (DOTS) Requirements

This document defines the requirements for the Distributed Denial-of- Service (DDoS) Open Threat Signaling (DOTS) protocols enabling coordinated response to DDoS attacks.

RFC86112019-06-01

Label Switched Path (LSP) Ping and Traceroute Multipath Support for Link Aggregation Group (LAG) Interfaces

Label Switched Path (LSP) Ping and Traceroute Multipath Support for Link Aggregation Group (LAG) Interfaces

This document defines extensions to the MPLS Label Switched Path (LSP) Ping and Traceroute mechanisms as specified in RFC 8029. The extensions allow the MPLS LSP Ping and Traceroute mechanisms to discover and exercise specific paths of Layer 2 (L2) Equal-Cost Multipath (ECMP) over Link Aggregation Group (LAG) interfaces. Additionally, a mechanism is defined to enable the determination of the capab…

RFC86102019-06-01

Concise Data Definition Language (CDDL): A Notational Convention to Express Concise Binary Object Representation (CBOR) and JSON Data Structures

Concise Data Definition Language (CDDL): A Notational Convention to Express Concise Binary Object Representation (CBOR) and JSON Data Structures

This document proposes a notational convention to express Concise Binary Object Representation (CBOR) data structures (RFC 7049). Its main goal is to provide an easy and unambiguous way to express structures for protocol messages and data formats that use CBOR or JSON.

RFC86092019-07-01

Content-Centric Networking (CCNx) Messages in TLV Format

Content-Centric Networking (CCNx) Messages in TLV Format

Content-Centric Networking (CCNx) is a network protocol that uses a hierarchical name to forward requests and to match responses to requests. This document specifies the encoding of CCNx messages in a TLV packet format, including the TLV types used by each message element and the encoding of each value. The semantics of CCNx messages follow the encoding-independent CCNx Semantics specification. Th…

RFC86082019-06-01

BGPsec Algorithms, Key Formats, and Signature Formats

BGPsec Algorithms, Key Formats, and Signature Formats

This document specifies the algorithms, algorithm parameters, asymmetric key formats, asymmetric key sizes, and signature formats used in BGPsec (Border Gateway Protocol Security). This document updates RFC 7935 ("The Profile for Algorithms and Key Sizes for Use in the Resource Public Key Infrastructure") and obsoletes RFC 8208 ("BGPsec Algorithms, Key Formats, and Signature Formats") by adding Do…

RFC86072019-06-01

Calendaring Extensions to WebDAV (CalDAV): Managed Attachments

Calendaring Extensions to WebDAV (CalDAV): Managed Attachments

This specification adds an extension to the Calendaring Extensions to WebDAV (CalDAV) to allow attachments associated with iCalendar data to be stored and managed on the server. This specification documents existing code deployed by multiple vendors. It is published as an Informational specification rather than Standards Track due to its noncompliance with multiple best current practices of HTTP.

RFC86062019-06-01

ISDN User Part (ISUP) Cause Location Parameter for the SIP Reason Header Field

ISDN User Part (ISUP) Cause Location Parameter for the SIP Reason Header Field

The SIP Reason header field is defined to carry ISUP (ISDN User Part) cause values as well as SIP response codes. Some services in SIP networks may need to know the ISUP location where the call was released in the PSTN (Public Switched Telephone Network) to correctly interpret the reason of release. This document updates RFC 3326 by adding a location parameter for this purpose.

RFC86052019-05-01

vCard Format Extensions: ICANN Extensions for the Registration Data Access Protocol (RDAP)

vCard Format Extensions: ICANN Extensions for the Registration Data Access Protocol (RDAP)

This document defines extensions to the vCard data format for representing and exchanging contact information used to implement the Internet Corporation for Assigned Names and Numbers (ICANN) operational profile for the Registration Data Access Protocol (RDAP). The property and parameter defined here are used to add values to RDAP responses that are consistent with ICANN policies.

RFC86042019-06-01

Interconnecting Millions of Endpoints with Segment Routing

Interconnecting Millions of Endpoints with Segment Routing

This document describes an application of Segment Routing to scale the network to support hundreds of thousands of network nodes, and tens of millions of physical underlay endpoints. This use case can be applied to the interconnection of massive-scale Data Centers (DCs) and/or large aggregation networks. Forwarding tables of midpoint and leaf nodes only require a few tens of thousands of entries. …

RFC86032019-05-01

Commercial National Security Algorithm (CNSA) Suite Certificate and Certificate Revocation List (CRL) Profile

Commercial National Security Algorithm (CNSA) Suite Certificate and Certificate Revocation List (CRL) Profile

This document specifies a base profile for X.509 v3 Certificates and X.509 v2 Certificate Revocation Lists (CRLs) for use with the United States National Security Agency's Commercial National Security Algorithm (CNSA) Suite. The profile applies to the capabilities, configuration, and operation of all components of US National Security Systems that employ such X.509 certificates. US National Securi…

RFC86022019-07-01

Update to the Telephony Routing over IP (TRIP) IANA Registry Rules regarding Postal Addresses

Update to the Telephony Routing over IP (TRIP) IANA Registry Rules regarding Postal Addresses

This memo updates the IANA registry rules for the Telephony Routing over IP (TRIP) protocol, by no longer requiring that postal addresses be included in contact information. This memo updates RFC 3219.

RFC86012019-05-01

Message Header Field for Indicating Message Authentication Status

Message Header Field for Indicating Message Authentication Status

This document specifies a message header field called "Authentication-Results" for use with electronic mail messages to indicate the results of message authentication efforts. Any receiver-side software, such as mail filters or Mail User Agents (MUAs), can use this header field to relay that information in a convenient and meaningful way to users or to make sorting and filtering decisions. This do…

RFC86002019-06-01

Using Extensible Messaging and Presence Protocol (XMPP) for Security Information Exchange

Using Extensible Messaging and Presence Protocol (XMPP) for Security Information Exchange

This document describes how to use the Extensible Messaging and Presence Protocol (XMPP) to collect and distribute security incident reports and other security-relevant information between network- connected devices, primarily for the purpose of communication among Computer Security Incident Response Teams and associated entities. To illustrate the principles involved, this document describes such…

RFC85992019-05-01

Push Notification with the Session Initiation Protocol (SIP)

Push Notification with the Session Initiation Protocol (SIP)

This document describes how a Push Notification Service (PNS) can be used to wake a suspended Session Initiation Protocol (SIP) User Agent (UA) with push notifications, and it also describes how the UA can send binding-refresh REGISTER requests and receive incoming SIP requests in an environment in which the UA may be suspended. The document defines new SIP URI parameters to exchange PNS informati…

RFC85982019-05-01

Split DNS Configuration for the Internet Key Exchange Protocol Version 2 (IKEv2)

Split DNS Configuration for the Internet Key Exchange Protocol Version 2 (IKEv2)

This document defines two Configuration Payload Attribute Types (INTERNAL_DNS_DOMAIN and INTERNAL_DNSSEC_TA) for the Internet Key Exchange Protocol version 2 (IKEv2). These payloads add support for private (internal-only) DNS domains. These domains are intended to be resolved using non-public DNS servers that are only reachable through the IPsec connection. DNS resolution for other domains remains…

RFC85972019-05-01

Cooperating Layered Architecture for Software-Defined Networking (CLAS)

Cooperating Layered Architecture for Software-Defined Networking (CLAS)

Software-Defined Networking (SDN) advocates for the separation of the control plane from the data plane in the network nodes and its logical centralization on one or a set of control entities. Most of the network and/or service intelligence is moved to these control entities. Typically, such an entity is seen as a compendium of interacting control functions in a vertical, tightly integrated fashio…

RFC85962019-06-01

MPLS Transport Encapsulation for the Service Function Chaining (SFC) Network Service Header (NSH)

MPLS Transport Encapsulation for the Service Function Chaining (SFC) Network Service Header (NSH)

This document describes how to use a Service Function Forwarder (SFF) Label (similar to a pseudowire label or VPN label) to indicate the presence of a Service Function Chaining (SFC) Network Service Header (NSH) between an MPLS label stack and the packet original packet/ frame. This allows SFC packets using the NSH to be forwarded between SFFs over an MPLS network, and to select one of multiple SF…

RFC85952019-06-01

An MPLS-Based Forwarding Plane for Service Function Chaining

An MPLS-Based Forwarding Plane for Service Function Chaining

This document describes how Service Function Chaining (SFC) can be achieved in an MPLS network by means of a logical representation of the Network Service Header (NSH) in an MPLS label stack. That is, the NSH is not used, but the fields of the NSH are mapped to fields in the MPLS label stack. This approach does not deprecate or replace the NSH, but it acknowledges that there may be a need for an i…

RFC85942019-05-01

The Sunset HTTP Header Field

The Sunset HTTP Header Field

This specification defines the Sunset HTTP response header field, which indicates that a URI is likely to become unresponsive at a specified point in the future. It also defines a sunset link relation type that allows linking to resources providing information about an upcoming resource or service sunset.

RFC85932019-05-01

Video Traffic Models for RTP Congestion Control Evaluations

Video Traffic Models for RTP Congestion Control Evaluations

This document describes two reference video traffic models for evaluating RTP congestion control algorithms. The first model statistically characterizes the behavior of a live video encoder in response to changing requests on the target video rate. The second model is trace-driven and emulates the output of actual encoded video frame sizes from a high-resolution test sequence. Both models are desi…

RFC85922019-05-01

Key Performance Indicator (KPI) Stamping for the Network Service Header (NSH)

Key Performance Indicator (KPI) Stamping for the Network Service Header (NSH)

This document describes methods of carrying Key Performance Indicators (KPIs) using the Network Service Header (NSH). These methods may be used, for example, to monitor latency and QoS marking to identify problems on some links or service functions.

RFC85912019-04-01

SIP-Based Messaging with S/MIME

SIP-Based Messaging with S/MIME

Mobile messaging applications used with the Session Initiation Protocol (SIP) commonly use some combination of the SIP MESSAGE method and the Message Session Relay Protocol (MSRP). While these provide mechanisms for hop-by-hop security, neither natively provides end-to-end protection. This document offers guidance on how to provide end-to-end authentication, integrity protection, and confidentiali…

RFC85902019-05-01

Change Poll Extension for the Extensible Provisioning Protocol (EPP)

Change Poll Extension for the Extensible Provisioning Protocol (EPP)

This document describes an Extensible Provisioning Protocol (EPP) extension for notifying clients of operations on client-sponsored objects that were not initiated by the client through EPP. These operations may include contractual or policy requirements including, but not limited to, regular batch processes, customer support actions, Uniform Domain-Name Dispute-Resolution Policy (UDRP) or Uniform…

RFC85892019-05-01

The 'leaptofrogans' URI Scheme

The 'leaptofrogans' URI Scheme

This document describes the 'leaptofrogans' Uniform Resource Identifier (URI) scheme, which enables applications to launch Frogans Player on a given Frogans site. Frogans is a medium for publishing content and services on the Internet, defined as a generic software layer on the Internet. Frogans Player is software that enables end users to browse Frogans sites.

RFC85882019-05-01

Personal Assertion Token (PaSSporT) Extension for Signature-based Handling of Asserted information using toKENs (SHAKEN)

Personal Assertion Token (PaSSporT) Extension for Signature-based Handling of Asserted information using toKENs (SHAKEN)

This document extends the Personal Assertion Token (PASSporT), which is a token object that conveys cryptographically signed information about the participants involved in communications. The extension is defined based on the "Signature-based Handling of Asserted information using toKENs (SHAKEN)" specification by the ATIS/SIP Forum IP-NNI Task Group. It provides both (1) a specific set of levels …

RFC85872019-05-01

NFS Version 4.0 Trunking Update

NFS Version 4.0 Trunking Update

In NFS version 4.0, the fs_locations attribute informs clients about alternate locations of file systems. An NFS version 4.0 client can use this information to handle migration and replication of server file systems. This document describes how an NFS version 4.0 client can also use this information to discover an NFS version 4.0 server's trunking capabilities. This document updates RFC 7530.

RFC85862019-04-01

Loop Detection in Content Delivery Networks (CDNs)

Loop Detection in Content Delivery Networks (CDNs)

This document defines the CDN-Loop request header field for HTTP. CDN-Loop addresses an operational need that occurs when an HTTP request is intentionally forwarded between Content Delivery Networks (CDNs), but is then accidentally or maliciously re-routed back into the original CDN causing a non-terminating loop. The new header field can be used to identify the error and terminate the loop.

RFC85852019-05-01

Requirements for IPv6 Customer Edge Routers to Support IPv4-as-a-Service

Requirements for IPv6 Customer Edge Routers to Support IPv4-as-a-Service

This document specifies the IPv4 service continuity requirements for IPv6 Customer Edge (CE) routers that are provided either by the service provider or by vendors who sell through the retail market. Specifically, this document extends the basic requirements for IPv6 CE routers as described in RFC 7084 to allow the provisioning of IPv6 transition services for the support of IPv4-as-a-Service (IPv4…

RFC85842019-04-01

Framework for Ethernet VPN Designated Forwarder Election Extensibility

Framework for Ethernet VPN Designated Forwarder Election Extensibility

An alternative to the default Designated Forwarder (DF) selection algorithm in Ethernet VPNs (EVPNs) is defined. The DF is the Provider Edge (PE) router responsible for sending Broadcast, Unknown Unicast, and Multicast (BUM) traffic to a multihomed Customer Edge (CE) device on a given VLAN on a particular Ethernet Segment (ES). In addition, the ability to influence the DF election result for a VLA…

RFC85832019-08-01

Diameter Load Information Conveyance

Diameter Load Information Conveyance

RFC 7068 describes requirements for Overload Control in Diameter. This includes a requirement to allow Diameter nodes to send "load" information, even when the node is not overloaded. The base solution defined in RFC 7683 (Diameter Overload Information Conveyance (DOIC)) describes a mechanism meeting most of the requirements but does not currently include the ability to send load information. This…