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

IETF · RFC

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

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

RFC63662011-08-01

Requirements for an Internet Audio Codec

Requirements for an Internet Audio Codec

This document provides specific requirements for an Internet audio codec. These requirements address quality, sampling rate, bit-rate, and packet-loss robustness, as well as other desirable properties. This document is not an Internet Standards Track specification; it is published for informational purposes.

RFC63652011-09-01

Terminology Used in Internationalization in the IETF

Terminology Used in Internationalization in the IETF

This document provides a list of terms used in the IETF when discussing internationalization. The purpose is to help frame discussions of internationalization in the various areas of the IETF and to help introduce the main concepts to IETF participants. This memo documents an Internet Best Current Practice.

RFC63642011-10-01

Session Description Protocol Elements for the Forward Error Correction (FEC) Framework

Session Description Protocol Elements for the Forward Error Correction (FEC) Framework

This document specifies the use of the Session Description Protocol (SDP) to describe the parameters required to signal the Forward Error Correction (FEC) Framework Configuration Information between the sender(s) and receiver(s). This document also provides examples that show the semantics for grouping multiple source and repair flows together for the applications that simultaneously use multiple …

RFC63632011-10-01

Forward Error Correction (FEC) Framework

Forward Error Correction (FEC) Framework

This document describes a framework for using Forward Error Correction (FEC) codes with applications in public and private IP networks to provide protection against packet loss. The framework supports applying FEC to arbitrary packet flows over unreliable transport and is primarily intended for real-time, or streaming, media. This framework can be used to define Content Delivery Protocols that pro…

RFC63622011-08-01

Multiple Attachments for Electronic Data Interchange - Internet Integration (EDIINT)

Multiple Attachments for Electronic Data Interchange - Internet Integration (EDIINT)

The Electronic Data Interchange - Internet Integration (EDIINT) AS1, AS2, and AS3 messages were designed specifically for the transport of EDI documents. Since multiple interchanges could be placed within a single EDI document, there was not a need for sending multiple EDI documents in a single message. As adoption of EDIINT grew, other uses developed aside from single EDI document transport. Some…

RFC63612011-08-01

PPP Transparent Interconnection of Lots of Links (TRILL) Protocol Control Protocol

PPP Transparent Interconnection of Lots of Links (TRILL) Protocol Control Protocol

The Point-to-Point Protocol (PPP) defines a Link Control Protocol (LCP) and a method for negotiating the use of multiprotocol traffic over point-to-point links. This document describes PPP support for the Transparent Interconnection of Lots of Links (TRILL) Protocol, allowing direct communication between Routing Bridges (RBridges) via PPP links. [STANDARDS-TRACK]

RFC63602011-08-01

Conclusion of FYI RFC Sub-Series

Conclusion of FYI RFC Sub-Series

This document concludes the For Your Information (FYI) sub-series of RFCs, established by RFC 1150 for use by the IETF User Services Area, which no longer exists. The IESG does not intend to make any further additions to this RFC sub-series, and this document provides a record of this decision. This document also obsoletes RFC 1150 and changes the status of RFC 1150 to Historic. This document is n…

RFC63592011-09-01

Datatracker Extensions to Include IANA and RFC Editor Processing Information

Datatracker Extensions to Include IANA and RFC Editor Processing Information

This document captures the requirements for integrating IANA and RFC Editor state information into the Datatracker to provide the community with a unified tool to track the status of their document as it progresses from Internet-Draft (I-D) version -00 to RFC. Extending the Datatracker to hold document data from I-D version -00 to RFC allows for increased automation between the Datatracker, IANA, …

RFC63582012-01-01

Additional Master Secret Inputs for TLS

Additional Master Secret Inputs for TLS

This document describes a mechanism for using additional master secret inputs with Transport Layer Security (TLS) and Datagram TLS (DTLS). This document defines an Experimental Protocol for the Internet community.

RFC63572011-08-01

Design Considerations for Session Initiation Protocol (SIP) Overload Control

Design Considerations for Session Initiation Protocol (SIP) Overload Control

Overload occurs in Session Initiation Protocol (SIP) networks when SIP servers have insufficient resources to handle all SIP messages they receive. Even though the SIP protocol provides a limited overload control mechanism through its 503 (Service Unavailable) response code, SIP servers are still vulnerable to overload. This document discusses models and design considerations for a SIP overload co…

RFC63562011-10-01

Coupled Congestion Control for Multipath Transport Protocols

Coupled Congestion Control for Multipath Transport Protocols

Often endpoints are connected by multiple paths, but communications are usually restricted to a single path per connection. Resource usage within the network would be more efficient were it possible for these multiple paths to be used concurrently. Multipath TCP is a proposal to achieve multipath transport in TCP. New congestion control algorithms are needed for multipath transport protocols such …

RFC63552011-08-01

Definition of the UUID-Based DHCPv6 Unique Identifier (DUID-UUID)

Definition of the UUID-Based DHCPv6 Unique Identifier (DUID-UUID)

This document defines a new DHCPv6 Unique Identifier (DUID) type called DUID-UUID. DUID-UUIDs are derived from the already-standardized Universally Unique IDentifier (UUID) format. DUID-UUID makes it possible for devices to use UUIDs to identify themselves to DHC servers and vice versa. UUIDs are globally unique and readily available on many systems, making them convenient identifiers to leverage …

RFC63542011-08-01

Forward-Shifted RTP Redundancy Payload Support

Forward-Shifted RTP Redundancy Payload Support

This document defines a simple enhancement to support RTP sessions with forward-shifted redundant encodings, i.e., redundant data sent before the corresponding primary data. Forward-shifted redundancy can be used to conceal losses of a large number of consecutive media frames (e.g., consecutive loss of seconds or even tens of seconds of media). [STANDARDS-TRACK]

RFC63532011-07-01

Transport Layer Security (TLS) Transport Model for the Simple Network Management Protocol (SNMP)

Transport Layer Security (TLS) Transport Model for the Simple Network Management Protocol (SNMP)

This document describes a Transport Model for the Simple Network Management Protocol (SNMP), that uses either the Transport Layer Security protocol or the Datagram Transport Layer Security (DTLS) protocol. The TLS and DTLS protocols provide authentication and privacy services for SNMP applications. This document describes how the TLS Transport Model (TLSTM) implements the needed features of an SNM…

RFC63522011-08-01

CardDAV: vCard Extensions to Web Distributed Authoring and Versioning (WebDAV)

CardDAV: vCard Extensions to Web Distributed Authoring and Versioning (WebDAV)

This document defines extensions to the Web Distributed Authoring and Versioning (WebDAV) protocol to specify a standard way of accessing, managing, and sharing contact information based on the vCard format. [STANDARDS-TRACK]

RFC63512011-08-01

xCard: vCard XML Representation

xCard: vCard XML Representation

This document defines the XML schema of the vCard data format. [STANDARDS-TRACK]

RFC63502011-08-01

vCard Format Specification

vCard Format Specification

This document defines the vCard data format for representing and exchanging a variety of information about individuals and other entities (e.g., formatted and structured name and delivery addresses, email address, multiple telephone numbers, photograph, logo, audio clips, etc.). This document obsoletes RFCs 2425, 2426, and 4770, and updates RFC 2739. [STANDARDS-TRACK]

RFC63492011-08-01

Framework for TCP Throughput Testing

Framework for TCP Throughput Testing

This framework describes a practical methodology for measuring end- to-end TCP Throughput in a managed IP network. The goal is to provide a better indication in regard to user experience. In this framework, TCP and IP parameters are specified to optimize TCP Throughput. This document is not an Internet Standards Track specification; it is published for informational purposes.

RFC63482011-09-01

Requirements for Point-to-Multipoint Extensions to the Label Distribution Protocol

Requirements for Point-to-Multipoint Extensions to the Label Distribution Protocol

This document lists a set of functional requirements that served as input to the design of Label Distribution Protocol (LDP) extensions for setting up point-to-multipoint (P2MP) Label Switched Paths (LSP), in order to deliver point-to-multipoint applications over a Multiprotocol Label Switching (MPLS) infrastructure. This work was overtaken by the protocol solution developed by the MPLS working gr…

RFC63472012-01-01

Datagram Transport Layer Security Version 1.2

Datagram Transport Layer Security Version 1.2

This document specifies version 1.2 of the Datagram Transport Layer Security (DTLS) protocol. The DTLS protocol provides communications privacy for datagram protocols. The protocol allows client/server applications to communicate in a way that is designed to prevent eavesdropping, tampering, or message forgery. The DTLS protocol is based on the Transport Layer Security (TLS) protocol and provides …

RFC63462011-08-01

The Address plus Port (A+P) Approach to the IPv4 Address Shortage

The Address plus Port (A+P) Approach to the IPv4 Address Shortage

We are facing the exhaustion of the IANA IPv4 free IP address pool. Unfortunately, IPv6 is not yet deployed widely enough to fully replace IPv4, and it is unrealistic to expect that this is going to change before the depletion of IPv4 addresses. Letting hosts seamlessly communicate in an IPv4 world without assigning a unique globally routable IPv4 address to each of them is a challenging problem. …

RFC63452011-08-01

Protocol for Carrying Authentication for Network Access (PANA) Relay Element

Protocol for Carrying Authentication for Network Access (PANA) Relay Element

This document specifies Protocol for carrying Authentication for Network Access (PANA) Relay Element functionality, which enables PANA messaging between a PANA Client (PaC) and a PANA Authentication Agent (PAA) where the two nodes cannot reach each other by means of regular IP routing. [STANDARDS-TRACK]

RFC63442011-08-01

Operating Virtual Concatenation (VCAT) and the Link Capacity Adjustment Scheme (LCAS) with Generalized Multi-Protocol Label Switching (GMPLS)

Operating Virtual Concatenation (VCAT) and the Link Capacity Adjustment Scheme (LCAS) with Generalized Multi-Protocol Label Switching (GMPLS)

This document describes requirements for, and the use of, the Generalized Multi-Protocol Label Switching (GMPLS) control plane in support of the Virtual Concatenation (VCAT) layer 1 inverse multiplexing data plane mechanism and its companion Link Capacity Adjustment Scheme (LCAS). LCAS can be used for hitless dynamic resizing of the inverse multiplex group. These techniques apply to Optical Transp…

RFC63432011-08-01

Advisory Guidelines for 6to4 Deployment

Advisory Guidelines for 6to4 Deployment

This document provides advice to network operators about deployment of the 6to4 technique for automatic tunneling of IPv6 over IPv4. It is principally addressed to Internet Service Providers (ISPs), including those that do not yet support IPv6, and to Content Providers. Some advice to implementers is also included. The intention of the advice is to minimize both user dissatisfaction and help-desk …

RFC63422011-08-01

Mobile Networks Considerations for IPv6 Deployment

Mobile Networks Considerations for IPv6 Deployment

Mobile Internet access from smartphones and other mobile devices is accelerating the exhaustion of IPv4 addresses. IPv6 is widely seen as crucial for the continued operation and growth of the Internet, and in particular, it is critical in mobile networks. This document discusses the issues that arise when deploying IPv6 in mobile networks. Hence, this document can be a useful reference for service…

RFC63412011-08-01

Use Cases and Requirements for SIP-Based Media Recording (SIPREC)

Use Cases and Requirements for SIP-Based Media Recording (SIPREC)

Session recording is a critical requirement in many business communications environments, such as call centers and financial trading floors. In some of these environments, all calls must be recorded for regulatory and compliance reasons. In others, calls may be recorded for quality control or business analytics. Recording is typically performed by sending a copy of the session media to the recordi…

RFC63402011-08-01

Textual Conventions for the Representation of Floating-Point Numbers

Textual Conventions for the Representation of Floating-Point Numbers

This memo defines a Management Information Base (MIB) module containing textual conventions (TCs) to represent floating-point numbers. [STANDARDS-TRACK]

RFC63392011-08-01

Context Token Encapsulate/Decapsulate and OID Comparison Functions for the Generic Security Service Application Program Interface (GSS-API)

Context Token Encapsulate/Decapsulate and OID Comparison Functions for the Generic Security Service Application Program Interface (GSS-API)

This document describes three abstract Generic Security Service Application Program Interface (GSS-API) interfaces used to encapsulate/decapsulate context tokens and compare OIDs. This document also specifies C bindings for the abstract interfaces. [STANDARDS-TRACK]

RFC63382011-08-01

Definition of a Uniform Resource Name (URN) Namespace for the Schema for Academia (SCHAC)

Definition of a Uniform Resource Name (URN) Namespace for the Schema for Academia (SCHAC)

This document describes a Uniform Resource Name (URN) namespace for the Schema for Academia (SCHAC). The namespace described in this document is for naming persistent resources defined by the SCHAC participants internationally, their working groups, and other designated subordinates. The main use of this namespace will be for the creation of controlled vocabulary values for attributes in the SCHAC…

RFC63372011-08-01

Session Initiation Protocol (SIP) Usage of the Offer/Answer Model

Session Initiation Protocol (SIP) Usage of the Offer/Answer Model

The Session Initiation Protocol (SIP) utilizes the offer/answer model to establish and update multimedia sessions using the Session Description Protocol (SDP). The description of the offer/answer model in SIP is dispersed across multiple RFCs. This document summarizes all the current usages of the offer/answer model in SIP communication. This document is not an Internet Standards Track specificati…