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

IETF · RFC

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

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

RFC85182019-03-01

Selection of Loop-Free Alternates for Multi-Homed Prefixes

Selection of Loop-Free Alternates for Multi-Homed Prefixes

Deployment experience gained from implementing algorithms to determine Loop-Free Alternates (LFAs) for multi-homed prefixes (MHPs) has revealed some avenues for potential improvement. This document provides explicit inequalities that can be used to evaluate neighbors as potential alternates for MHPs. It also provides detailed criteria for evaluating potential alternates for external prefixes adver…

RFC85172019-02-01

An Inventory of Transport-Centric Functions Provided by Middleboxes: An Operator Perspective

An Inventory of Transport-Centric Functions Provided by Middleboxes: An Operator Perspective

This document summarizes an operator's perception of the benefits that may be provided by intermediary devices that execute functions beyond normal IP forwarding. Such intermediary devices are often called "middleboxes". RFC 3234 defines a taxonomy of middleboxes and issues in the Internet. Most of those middleboxes utilize or modify application- layer data. This document primarily focuses on devi…

RFC85162019-01-01

"Too Many Requests" Response Code for the Constrained Application Protocol

"Too Many Requests" Response Code for the Constrained Application Protocol

A Constrained Application Protocol (CoAP) server can experience temporary overload because one or more clients are sending requests to the server at a higher rate than the server is capable or willing to handle. This document defines a new CoAP response code for a server to indicate that a client should reduce the rate of requests.

RFC85152019-02-01

URN Namespace for ETSI Documents

URN Namespace for ETSI Documents

This document describes the Namespace Identifier (NID) "etsi" for Uniform Resource Names (URNs) used to identify resources published by the European Telecommunications Standards Institute (http://etsi.org). ETSI specifies and manages resources that utilize this URN identification model. Management activities for these and other resource types are handled by the manager of the ETSI Protocol Naming …

RFC85142019-01-01

Internet Message Access Protocol (IMAP) - SAVEDATE Extension

Internet Message Access Protocol (IMAP) - SAVEDATE Extension

This document adds a new capability called "SAVEDATE" to the Internet Message Access Protocol (IMAP). It defines a new IMAP message attribute called "save date" that, unlike the existing "internal date" attribute, always indicates the moment at which the message was saved in its current mailbox. The SAVEDATE capability extends the FETCH command with the means to retrieve the save date attribute an…

RFC85132019-01-01

A YANG Data Model for Dual-Stack Lite (DS-Lite)

A YANG Data Model for Dual-Stack Lite (DS-Lite)

This document defines a YANG module for the Dual-Stack Lite (DS-Lite) Address Family Transition Router (AFTR) and Basic Bridging BroadBand (B4) elements.

RFC85122019-01-01

A YANG Module for Network Address Translation (NAT) and Network Prefix Translation (NPT)

A YANG Module for Network Address Translation (NAT) and Network Prefix Translation (NPT)

This document defines a YANG module for the Network Address Translation (NAT) function. Network Address Translation from IPv4 to IPv4 (NAT44), Network Address and Protocol Translation from IPv6 Clients to IPv4 Servers (NAT64), customer-side translator (CLAT), Stateless IP/ICMP Translation (SIIT), Explicit Address Mappings (EAM) for SIIT, IPv6-to-IPv6 Network Prefix Translation (NPTv6), and Destina…

RFC85112018-12-01

TCP Alternative Backoff with ECN (ABE)

TCP Alternative Backoff with ECN (ABE)

Active Queue Management (AQM) mechanisms allow for burst tolerance while enforcing short queues to minimise the time that packets spend enqueued at a bottleneck. This can cause noticeable performance degradation for TCP connections traversing such a bottleneck, especially if there are only a few flows or their bandwidth-delay product (BDP) is large. The reception of a Congestion Experienced (CE) E…

RFC85102019-01-01

OSPF Link-Local Signaling (LLS) Extensions for Local Interface ID Advertisement

OSPF Link-Local Signaling (LLS) Extensions for Local Interface ID Advertisement

Every OSPF interface is assigned an Interface ID that uniquely identifies the interface on the router. In some cases, it is useful to know the assigned Interface ID on the remote side of the adjacency (Remote Interface ID). This document describes the extensions to OSPF link-local signaling (LLS) to advertise the Local Interface ID.

RFC85092018-12-01

A Root Key Trust Anchor Sentinel for DNSSEC

A Root Key Trust Anchor Sentinel for DNSSEC

The DNS Security Extensions (DNSSEC) were developed to provide origin authentication and integrity protection for DNS data by using digital signatures. These digital signatures can be verified by building a chain of trust starting from a trust anchor and proceeding down to a particular node in the DNS. This document specifies a mechanism that will allow an end user and third parties to determine t…

RFC85082019-01-01

IMAP REPLACE Extension

IMAP REPLACE Extension

This document defines an IMAP extension that can be used to replace an existing message in a message store with a new message. Message replacement is a common operation for clients that automatically save drafts or notes as a user composes them.

RFC85072018-12-01

Simple Internet Protocol (SIP) Specification

Simple Internet Protocol (SIP) Specification

This document is published for the historical record. The Simple Internet Protocol was the basis for one of the candidates for the IETF's Next Generation (IPng) work that became IPv6. The publication date of the original Internet-Draft was November 10, 1992. It is presented here substantially unchanged and is neither a complete document nor intended to be implementable. The paragraph that follows …

RFC85062019-03-01

Diameter Credit-Control Application

Diameter Credit-Control Application

This document specifies a Diameter application that can be used to implement real-time credit-control for a variety of end-user services such as network access, Session Initiation Protocol (SIP) services, messaging services, and download services. The Diameter Credit- Control application as defined in this document obsoletes RFC 4006, and it must be supported by all new Diameter Credit-Control app…

RFC85052018-11-01

Registration Extensions for IPv6 over Low-Power Wireless Personal Area Network (6LoWPAN) Neighbor Discovery

Registration Extensions for IPv6 over Low-Power Wireless Personal Area Network (6LoWPAN) Neighbor Discovery

This specification updates RFC 6775 -- the Low-Power Wireless Personal Area Network (6LoWPAN) Neighbor Discovery specification -- to clarify the role of the protocol as a registration technique and simplify the registration operation in 6LoWPAN routers, as well as to provide enhancements to the registration capabilities and mobility detection for different network topologies, including the Routing…

RFC85042019-01-01

IPv6 Node Requirements

IPv6 Node Requirements

This document defines requirements for IPv6 nodes. It is expected that IPv6 will be deployed in a wide range of devices and situations. Specifying the requirements for IPv6 nodes allows IPv6 to function well and interoperate in a large number of situations and deployments. This document obsoletes RFC 6434, and in turn RFC 4294.

RFC85032018-12-01

BGP/MPLS Layer 3 VPN Multicast Management Information Base

BGP/MPLS Layer 3 VPN Multicast Management Information Base

This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects to configure and/or monitor Multicast communication over IP Virtual Private Networks (VPNs) supported by the Multiprotocol Label Switching/Border Gateway Protocol (MPLS/BGP) on a Provider Edge (PE) router.

RFC85022018-12-01

L2L3 VPN Multicast MIB

L2L3 VPN Multicast MIB

This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes two MIB modules that will be used by other MIB modules for monitoring and/or configuring Layer 2 and Layer 3 Virtual Private Networks that support multicast.

RFC85012018-11-01

Reverse DNS in IPv6 for Internet Service Providers

Reverse DNS in IPv6 for Internet Service Providers

In IPv4, Internet Service Providers (ISPs) commonly provide IN-ADDR.ARPA information for their customers by prepopulating the zone with one PTR record for every available address. This practice does not scale in IPv6. This document analyzes different approaches and considerations for ISPs in managing the IP6.ARPA zone.

RFC85002019-02-01

IS-IS Routing with Reverse Metric

IS-IS Routing with Reverse Metric

This document describes a mechanism to allow IS-IS routing to quickly and accurately shift traffic away from either a point-to-point or multi-access LAN interface during network maintenance or other operational events. This is accomplished by signaling adjacent IS-IS neighbors with a higher reverse metric, i.e., the metric towards the signaling IS-IS router.

RFC84992019-01-01

DNS Terminology

DNS Terminology

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 sometimes 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 obsoletes RFC 7719 and updates RFC…

RFC84982019-02-01

A P-Served-User Header Field Parameter for an Originating Call Diversion (CDIV) Session Case in the Session Initiation Protocol (SIP)

A P-Served-User Header Field Parameter for an Originating Call Diversion (CDIV) Session Case in the Session Initiation Protocol (SIP)

The P-Served-User header field was defined based on a requirement from the 3rd Generation Partnership Project (3GPP) IMS (IP Multimedia Subsystem) in order to convey the identity of the served user, his/ her registration state, and the session case that applies to that particular communication session and application invocation. A session case is metadata that captures the status of the session of…

RFC84972018-11-01

Marking SIP Messages to Be Logged

Marking SIP Messages to Be Logged

SIP networks use signaling monitoring tools to diagnose user-reported problems and to perform regression testing if network or user agent (UA) software is upgraded. As networks grow and become interconnected, including connection via transit networks, it becomes impractical to predict the path that SIP signaling will take between user agents and therefore impractical to monitor SIP signaling end t…

RFC84962018-10-01

P-Charge-Info: A Private Header Field (P-Header) Extension to the Session Initiation Protocol (SIP)

P-Charge-Info: A Private Header Field (P-Header) Extension to the Session Initiation Protocol (SIP)

This text documents the current usage of P-Charge-Info, an existing Session Initiation Protocol (SIP) private header field (P-Header) used to convey billing information about the party to be charged. This P-Header is currently used in production by several equipment vendors and carriers and has been in use since at least 2007. This document details the registration of this header field with IANA.

RFC84952018-11-01

Allocation Token Extension for the Extensible Provisioning Protocol (EPP)

Allocation Token Extension for the Extensible Provisioning Protocol (EPP)

This document describes an Extensible Provisioning Protocol (EPP) extension for including an Allocation Token in "query" and "transform" commands. The Allocation Token is used as a credential that authorizes a client to request the allocation of a specific object from the server using one of the EPP transform commands, including "create" and "transfer".

RFC84942018-11-01

Multicast Email (MULE) over Allied Communications Publication (ACP) 142

Multicast Email (MULE) over Allied Communications Publication (ACP) 142

Allied Communications Publication (ACP) 142 defines P_MUL, which is a protocol for reliable multicast suitable for bandwidth-constrained and delayed acknowledgement (Emissions Control or "EMCON") environments running over UDP. This document defines MULE (Multicast Email), an application protocol for transferring Internet Mail messages (as described in RFC 5322) over P_MUL (as defined in ACP 142). …

RFC84932018-10-01

The BagIt File Packaging Format (V1.0)

The BagIt File Packaging Format (V1.0)

This document describes BagIt, a set of hierarchical file layout conventions for storage and transfer of arbitrary digital content. A "bag" has just enough structure to enclose descriptive metadata "tags" and a file "payload" but does not require knowledge of the payload's internal semantics. This BagIt format is suitable for reliable storage and transfer.

RFC84922019-02-01

Secure Password Ciphersuites for Transport Layer Security (TLS)

Secure Password Ciphersuites for Transport Layer Security (TLS)

This memo defines several new ciphersuites for the Transport Layer Security (TLS) protocol to support certificateless, secure authentication using only a simple, low-entropy password. The exchange is called "TLS-PWD". The ciphersuites are all based on an authentication and key exchange protocol, named "dragonfly", that is resistant to offline dictionary attacks.

RFC84912018-11-01

Signaling Maximum SID Depth (MSD) Using IS-IS

Signaling Maximum SID Depth (MSD) Using IS-IS

This document defines a way for an Intermediate System to Intermediate System (IS-IS) router to advertise multiple types of supported Maximum SID Depths (MSDs) at node and/or link granularity. Such advertisements allow entities (e.g., centralized controllers) to determine whether a particular Segment ID (SID) stack can be supported in a given network. This document only defines one type of MSD: Ba…

RFC84902019-03-01

DNS Stateful Operations

DNS Stateful Operations

This document defines a new DNS OPCODE for DNS Stateful Operations (DSO). DSO messages communicate operations within persistent stateful sessions using Type Length Value (TLV) syntax. Three TLVs are defined that manage session timeouts, termination, and encryption padding, and a framework is defined for extensions to enable new stateful operations. This document updates RFC 1035 by adding a new DN…

RFC84892020-02-01

Session Traversal Utilities for NAT (STUN)

Session Traversal Utilities for NAT (STUN)

Session Traversal Utilities for NAT (STUN) is a protocol that serves as a tool for other protocols in dealing with NAT traversal. It can be used by an endpoint to determine the IP address and port allocated to it by a NAT. It can also be used to check connectivity between two endpoints and as a keep-alive protocol to maintain NAT bindings. STUN works with many existing NATs and does not require an…