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

IETF · RFC

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

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

RFC62142011-03-01

Adaptation of RFC 1149 for IPv6

Adaptation of RFC 1149 for IPv6

This document specifies a method for transmission of IPv6 datagrams over the same medium as specified for IPv4 datagrams in RFC 1149. This document is not an Internet Standards Track specification; it is published for informational purposes.

RFC62132011-04-01

IS-IS BFD-Enabled TLV

IS-IS BFD-Enabled TLV

This document describes a type-length-value (TLV) for use in the IS-IS routing protocol that allows for the proper use of the Bidirectional Forwarding Detection (BFD) protocol. There exist certain scenarios in which IS-IS will not react appropriately to a BFD-detected forwarding plane failure without use of either this TLV or some other method. [STANDARDS-TRACK]

RFC62122011-04-01

Authentication-Results Registration for Vouch by Reference Results

Authentication-Results Registration for Vouch by Reference Results

This memo updates the registry of properties in Authentication- Results: message header fields to allow relaying of the results of a Vouch By Reference query. [STANDARDS-TRACK]

RFC62112011-04-01

Cryptographic Message Syntax (CMS) Algorithm Identifier Protection Attribute

Cryptographic Message Syntax (CMS) Algorithm Identifier Protection Attribute

The Cryptographic Message Syntax (CMS), unlike X.509/PKIX certificates, is vulnerable to algorithm substitution attacks. In an algorithm substitution attack, the attacker changes either the algorithm being used or the parameters of the algorithm in order to change the result of a signature verification process. In X.509 certificates, the signature algorithm is protected because it is duplicated in…

RFC62102011-04-01

Experiment: Hash Functions with Parameters in the Cryptographic Message Syntax (CMS) and S/MIME

Experiment: Hash Functions with Parameters in the Cryptographic Message Syntax (CMS) and S/MIME

New hash algorithms are being developed that may include parameters. Cryptographic Message Syntax (CMS) has not currently defined any hash algorithms with parameters, but anecdotal evidence suggests that defining one could cause major problems. This document defines just such an algorithm and describes how to use it so that experiments can be run to find out how bad including hash parameters will …

RFC62092011-04-01

Addition of the ARIA Cipher Suites to Transport Layer Security (TLS)

Addition of the ARIA Cipher Suites to Transport Layer Security (TLS)

This document specifies a set of cipher suites for the Transport Layer Security (TLS) protocol to support the ARIA encryption algorithm as a block cipher. This document is not an Internet Standards Track specification; it is published for informational purposes.

RFC62082011-04-01

Cloud Data Management Interface (CDMI) Media Types

Cloud Data Management Interface (CDMI) Media Types

This document describes several Internet media types defined for the Cloud Data Management Interface (CDMI) by the Storage Networking Industry Association (SNIA). The media types are: o application/cdmi-object o application/cdmi-container o application/cdmi-domain o application/cdmi-capability o application/cdmi-queue This document is not an Internet Standards Track specification; it is published …

RFC62072011-04-01

The Media Types application/mods+xml, application/mads+xml, application/mets+xml, application/marcxml+xml, and application/sru+xml

The Media Types application/mods+xml, application/mads+xml, application/mets+xml, application/marcxml+xml, and application/sru+xml

This document specifies media types for the following formats: MODS (Metadata Object Description Schema), MADS (Metadata Authority Description Schema), METS (Metadata Encoding and Transmission Standard), MARCXML (MARC21 XML Schema), and the SRU (Search/Retrieve via URL Response Format) protocol response XML schema. These are all XML schemas providing representations of various forms of information…

RFC62062011-03-01

The Trickle Algorithm

The Trickle Algorithm

The Trickle algorithm allows nodes in a lossy shared medium (e.g., low-power and lossy networks) to exchange information in a highly robust, energy efficient, simple, and scalable manner. Dynamically adjusting transmission windows allows Trickle to spread new information on the scale of link-layer transmission times while sending only a few messages per hour when information does not change. A sim…

RFC62052011-03-01

Generalized Labels for Lambda-Switch-Capable (LSC) Label Switching Routers

Generalized Labels for Lambda-Switch-Capable (LSC) Label Switching Routers

Technology in the optical domain is constantly evolving, and, as a consequence, new equipment providing lambda switching capability has been developed and is currently being deployed. Generalized MPLS (GMPLS) is a family of protocols that can be used to operate networks built from a range of technologies including wavelength (or lambda) switching. For this purpose, GMPLS defined a wavelength label…

RFC62042011-04-01

Basic Requirements for IPv6 Customer Edge Routers

Basic Requirements for IPv6 Customer Edge Routers

This document specifies requirements for an IPv6 Customer Edge (CE) router. Specifically, the current version of this document focuses on the basic provisioning of an IPv6 CE router and the provisioning of IPv6 hosts attached to it. This document is not an Internet Standards Track specification; it is published for informational purposes.

RFC62032011-03-01

IMAP4 Extension for Fuzzy Search

IMAP4 Extension for Fuzzy Search

This document describes an IMAP protocol extension enabling a server to perform searches with inexact matching and assigning relevancy scores for matched messages. [STANDARDS-TRACK]

RFC62022011-04-01

Known Issues and Best Practices for the Use of Long Polling and Streaming in Bidirectional HTTP

Known Issues and Best Practices for the Use of Long Polling and Streaming in Bidirectional HTTP

On today's Internet, the Hypertext Transfer Protocol (HTTP) is often used (some would say abused) to enable asynchronous, "server- initiated" communication from a server to a client as well as communication from a client to a server. This document describes known issues and best practices related to such "bidirectional HTTP" applications, focusing on the two most common mechanisms: HTTP long polli…

RFC62012011-03-01

Device Reset Characterization

Device Reset Characterization

An operational forwarding device may need to be restarted (automatically or manually) for a variety of reasons, an event called a "reset" in this document. Since there may be an interruption in the forwarding operation during a reset, it is useful to know how long a device takes to resume the forwarding operation. This document specifies a methodology for characterizing reset (and reset time) duri…

RFC61982011-04-01

Requirements for the Graceful Shutdown of BGP Sessions

Requirements for the Graceful Shutdown of BGP Sessions

The Border Gateway Protocol (BGP) is heavily used in Service Provider networks for both Internet and BGP/MPLS VPN services. For resiliency purposes, redundant routers and BGP sessions can be deployed to reduce the consequences of an Autonomous System Border Router (ASBR) or BGP session breakdown on customers' or peers' traffic. However, simply taking down or even bringing up a BGP session for main…

RFC61972011-04-01

Location-to-Service Translation (LoST) Service List Boundary Extension

Location-to-Service Translation (LoST) Service List Boundary Extension

Location-to-Service Translation (LoST) maps service identifiers and location information to service contact URIs. If a LoST client wants to discover available services for a particular location, it will perform a <listServicesByLocation> query to the LoST server. However, the LoST server, in its response, does not provide context information; that is, it does not provide any additional information…

RFC61962011-03-01

Moving mailserver: URI Scheme to Historic

Moving mailserver: URI Scheme to Historic

This document registers the mailserver: URI scheme as historic in the IANA URI registry. [STANDARDS-TRACK]

RFC61952011-03-01

Domain Name System (DNS) IANA Considerations

Domain Name System (DNS) IANA Considerations

This document specifies Internet Assigned Number Authority (IANA) parameter assignment considerations for the allocation of Domain Name System (DNS) resource record types, CLASSes, operation codes, error codes, DNS protocol message header bits, and AFSDB resource record subtypes. This memo documents an Internet Best Current Practice.

RFC61942011-03-01

Security Considerations for the SHA-0 and SHA-1 Message-Digest Algorithms

Security Considerations for the SHA-0 and SHA-1 Message-Digest Algorithms

This document includes security considerations for the SHA-0 and SHA-1 message digest algorithm. This document is not an Internet Standards Track specification; it is published for informational purposes.

RFC61932011-04-01

Media Description for the Internet Key Exchange Protocol (IKE) in the Session Description Protocol (SDP)

Media Description for the Internet Key Exchange Protocol (IKE) in the Session Description Protocol (SDP)

This document specifies how to establish a media session that represents a virtual private network using the Session Initiation Protocol for the purpose of on-demand media/application sharing between peers. It extends the protocol identifier of the Session Description Protocol (SDP) so that it can negotiate use of the Internet Key Exchange Protocol (IKE) for media sessions in the SDP offer/answer …

RFC61922011-03-01

Protecting the Router Control Plane

Protecting the Router Control Plane

This memo provides a method for protecting a router's control plane from undesired or malicious traffic. In this approach, all legitimate router control plane traffic is identified. Once legitimate traffic has been identified, a filter is deployed in the router's forwarding plane. That filter prevents traffic not specifically identified as legitimate from reaching the router's control plane, or ra…

RFC61912011-04-01

Reducing the TIME-WAIT State Using TCP Timestamps

Reducing the TIME-WAIT State Using TCP Timestamps

This document describes an algorithm for processing incoming SYN segments that allows higher connection-establishment rates between any two TCP endpoints when a TCP Timestamps option is present in the incoming SYN segment. This document only modifies processing of SYN segments received for connections in the TIME-WAIT state; processing in all other states is unchanged. This memo documents an Inter…

RFC61902011-05-01

RTP Payload Format for Scalable Video Coding

RTP Payload Format for Scalable Video Coding

This memo describes an RTP payload format for Scalable Video Coding (SVC) as defined in Annex G of ITU-T Recommendation H.264, which is technically identical to Amendment 3 of ISO/IEC International Standard 14496-10. The RTP payload format allows for packetization of one or more Network Abstraction Layer (NAL) units in each RTP packet payload, as well as fragmentation of a NAL unit in multiple RTP…

RFC61892011-04-01

ZRTP: Media Path Key Agreement for Unicast Secure RTP

ZRTP: Media Path Key Agreement for Unicast Secure RTP

This document defines ZRTP, a protocol for media path Diffie-Hellman exchange to agree on a session key and parameters for establishing unicast Secure Real-time Transport Protocol (SRTP) sessions for Voice over IP (VoIP) applications. The ZRTP protocol is media path keying because it is multiplexed on the same port as RTP and does not require support in the signaling protocol. ZRTP does not assume…

RFC61882011-03-01

The Use of AES-192 and AES-256 in Secure RTP

The Use of AES-192 and AES-256 in Secure RTP

This memo describes the use of the Advanced Encryption Standard (AES) with 192- and 256-bit keys within the Secure RTP (SRTP) protocol. It details counter mode encryption for SRTP and Secure Realtime Transport Control Protocol (SRTCP) and a new SRTP Key Derivation Function (KDF) for AES-192 and AES-256. [STANDARDS-TRACK]

RFC61872011-03-01

X.509v3 Certificates for Secure Shell Authentication

X.509v3 Certificates for Secure Shell Authentication

X.509 public key certificates use a signature by a trusted certification authority to bind a given public key to a given digital identity. This document specifies how to use X.509 version 3 public key certificates in public key algorithms in the Secure Shell protocol. [STANDARDS-TRACK]

RFC61862011-03-01

Use of SRV Records for Locating Email Submission/Access Services

Use of SRV Records for Locating Email Submission/Access Services

This specification describes how SRV records can be used to locate email services. [STANDARDS-TRACK]

RFC61852011-05-01

RTP Payload Format for H.264 Reduced-Complexity Decoding Operation (RCDO) Video

RTP Payload Format for H.264 Reduced-Complexity Decoding Operation (RCDO) Video

This document describes an RTP payload format for the Reduced- Complexity Decoding Operation (RCDO) for H.264 Baseline profile bitstreams, as specified in ITU-T Recommendation H.241. RCDO reduces the decoding cost and resource consumption of the video processing. The RCDO RTP payload format is based on the H.264 RTP payload format. [STANDARDS-TRACK]

RFC61842011-05-01

RTP Payload Format for H.264 Video

RTP Payload Format for H.264 Video

This memo describes an RTP Payload format for the ITU-T Recommendation H.264 video codec and the technically identical ISO/IEC International Standard 14496-10 video codec, excluding the Scalable Video Coding (SVC) extension and the Multiview Video Coding extension, for which the RTP payload formats are defined elsewhere. The RTP payload format allows for packetization of one or more Network Abstra…

RFC61832011-04-01

IP Flow Information Export (IPFIX) Mediation: Framework

IP Flow Information Export (IPFIX) Mediation: Framework

This document describes a framework for IP Flow Information Export (IPFIX) Mediation. This framework extends the IPFIX reference model specified in RFC 5470 by defining the IPFIX Mediator components. This document is not an Internet Standards Track specification; it is published for informational purposes.