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

IETF · RFC

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

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

RFC59962010-09-01

Internet Key Exchange Protocol Version 2 (IKEv2)

Internet Key Exchange Protocol Version 2 (IKEv2)

This document describes version 2 of the Internet Key Exchange (IKE) protocol. IKE is a component of IPsec used for performing mutual authentication and establishing and maintaining Security Associations (SAs). This document replaces and updates RFC 4306, and includes all of the clarifications from RFC 4718. [STANDARDS-TRACK]

RFC59952010-09-01

Using POST to Add Members to Web Distributed Authoring and Versioning (WebDAV) Collections

Using POST to Add Members to Web Distributed Authoring and Versioning (WebDAV) Collections

The Hypertext Transfer Protocol (HTTP) Extensions for the Web Distributed Authoring and Versioning (WebDAV) do not define the behavior for the "POST" method when applied to collections, as the base specification (HTTP) leaves implementers lots of freedom for the semantics of "POST". This has led to a situation where many WebDAV servers do not implement POST for collections at all, although it is w…

RFC59942010-10-01

Application of Ethernet Pseudowires to MPLS Transport Networks

Application of Ethernet Pseudowires to MPLS Transport Networks

Ethernet pseudowires are widely deployed to support packet transport of Ethernet services. These services in-turn provide transport for a variety of client networks, e.g., IP and MPLS. This document uses procedures defined in the existing IETF specifications of Ethernet pseudowires carried over MPLS networks. Many of the requirements for the services provided by the mechanisms explained in this do…

RFC59932010-10-01

RTP Payload Format for Global System for Mobile Communications Half Rate (GSM-HR)

RTP Payload Format for Global System for Mobile Communications Half Rate (GSM-HR)

This document specifies the payload format for packetization of Global System for Mobile Communications Half Rate (GSM-HR) speech codec data into the Real-time Transport Protocol (RTP). The payload format supports transmission of multiple frames per payload and packet loss robustness methods using redundancy. [STANDARDS-TRACK]

RFC59922010-10-01

Internationalized Domain Names Registration and Administration Guidelines for European Languages Using Cyrillic

Internationalized Domain Names Registration and Administration Guidelines for European Languages Using Cyrillic

This document is a guideline for registries and registrars on registering internationalized domain names (IDNs) based on (in alphabetical order) Bosnian, Bulgarian, Byelorussian, Kildin Sami, Macedonian, Montenegrin, Russian, Serbian, and Ukrainian languages in a DNS zone. It describes appropriate characters for registration and variant considerations for characters from Greek and Latin scripts wi…

RFC59912010-09-01

Teredo Security Updates

Teredo Security Updates

The Teredo protocol defines a set of flags that are embedded in every Teredo IPv6 address. This document specifies a set of security updates that modify the use of this flags field, but are backward compatible. [STANDARDS-TRACK]

RFC59902010-09-01

Use of the RSA-KEM Key Transport Algorithm in the Cryptographic Message Syntax (CMS)

Use of the RSA-KEM Key Transport Algorithm in the Cryptographic Message Syntax (CMS)

The RSA-KEM Key Transport Algorithm is a one-pass (store-and-forward) mechanism for transporting keying data to a recipient using the recipient's RSA public key. ("KEM" stands for "key encapsulation mechanism".) This document specifies the conventions for using the RSA-KEM Key Transport Algorithm with the Cryptographic Message Syntax (CMS). The ASN.1 syntax is aligned with an expected forthcoming …

RFC59892010-10-01

A SIP Event Package for Subscribing to Changes to an HTTP Resource

A SIP Event Package for Subscribing to Changes to an HTTP Resource

The Session Initiation Protocol (SIP) is increasingly being used in systems that are tightly coupled with Hypertext Transport Protocol (HTTP) servers for a variety of reasons. In many of these cases, applications can benefit from being able to discover, in near real- time, when a specific HTTP resource is created, changed, or deleted. This document proposes a mechanism, based on the SIP Event Fram…

RFC59882010-10-01

Web Linking

Web Linking

This document specifies relation types for Web links, and defines a registry for them. It also defines the use of such links in HTTP headers with the Link header field. [STANDARDS-TRACK]

RFC59872010-08-01

Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters

Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters

By default, message header field parameters in Hypertext Transfer Protocol (HTTP) messages cannot carry characters outside the ISO- 8859-1 character set. RFC 2231 defines an encoding mechanism for use in Multipurpose Internet Mail Extensions (MIME) headers. This document specifies an encoding suitable for use in HTTP header fields that is compatible with a profile of the encoding defined in RFC 22…

RFC59862010-09-01

Discovering the Local Location Information Server (LIS)

Discovering the Local Location Information Server (LIS)

Discovery of the correct Location Information Server (LIS) in the local access network is necessary for Devices that wish to acquire location information from the network. A method is described for the discovery of a LIS in the access network serving a Device. Dynamic Host Configuration Protocol (DHCP) options for IP versions 4 and 6 are defined that specify a domain name. This domain name is then…

RFC59852010-09-01

HTTP-Enabled Location Delivery (HELD)

HTTP-Enabled Location Delivery (HELD)

This document defines a Layer 7 Location Configuration Protocol (L7 LCP) and describes the use of HTTP and HTTP/TLS as transports for the L7 LCP. The L7 LCP is used for retrieving location information from a server within an access network. It includes options for retrieving location information in two forms: by value and by reference. The protocol is an extensible application-layer protocol that …

RFC59842011-03-01

Increasing Throughput in IP Networks with ESP-Based Forwarding: ESPBasedForwarding

Increasing Throughput in IP Networks with ESP-Based Forwarding: ESPBasedForwarding

This document proposes an experimental way of reaching infinite bandwidth in IP networks by the use of ESP-based forwarding. This document defines an Experimental Protocol for the Internet community.

RFC59832010-10-01

Mailing Lists and Internationalized Email Addresses

Mailing Lists and Internationalized Email Addresses

This document describes considerations for mailing lists with the introduction of internationalized email addresses. This document makes some specific recommendations on how mailing lists should act in various situations. This document defines an Experimental Protocol for the Internet community.

RFC59822010-08-01

IP Flow Information Export (IPFIX) Mediation: Problem Statement

IP Flow Information Export (IPFIX) Mediation: Problem Statement

Flow-based measurement is a popular method for various network monitoring usages. The sharing of flow-based information for monitoring applications having different requirements raises some open issues in terms of measurement system scalability, flow-based measurement flexibility, and export reliability that IP Flow Information Export (IPFIX) Mediation may help resolve. This document describes som…

RFC59812011-02-01

Authorization for NSIS Signaling Layer Protocols

Authorization for NSIS Signaling Layer Protocols

Signaling layer protocols specified within the Next Steps in Signaling (NSIS) framework may rely on the General Internet Signaling Transport (GIST) protocol to handle authorization. Still, the signaling layer protocol above GIST itself may require separate authorization to be performed when a node receives a request for a certain kind of service or resources. This document presents a generic model…

RFC59802011-03-01

NSIS Protocol Operation in Mobile Environments

NSIS Protocol Operation in Mobile Environments

Mobility of an IP-based node affects routing paths, and as a result, can have a significant effect on the protocol operation and state management. This document discusses the effects mobility can cause to the Next Steps in Signaling (NSIS) protocol suite, and shows how the NSIS protocols operate in different scenarios with mobility management protocols. This document is not an Internet Standards T…

RFC59792011-03-01

NSIS Operation over IP Tunnels

NSIS Operation over IP Tunnels

NSIS Quality of Service (QoS) signaling enables applications to perform QoS reservation along a data flow path. When the data flow path contains IP tunnel segments, NSIS QoS signaling has no effect within those tunnel segments. Therefore, the resulting tunnel segments could become the weakest QoS link and invalidate the QoS efforts in the rest of the end-to-end path. The problem with NSIS signalin…

RFC59782010-10-01

Using and Extending the NSIS Protocol Family

Using and Extending the NSIS Protocol Family

This document gives an overview of the Next Steps in Signaling (NSIS) framework and protocol suite created by the NSIS Working Group during the period of 2001-2010. It also includes suggestions on how the industry can make use of the new protocols and how the community can exploit the extensibility of both the framework and existing protocols to address future signaling needs. This document is not…

RFC59772010-10-01

RMD-QOSM: The NSIS Quality-of-Service Model for Resource Management in Diffserv

RMD-QOSM: The NSIS Quality-of-Service Model for Resource Management in Diffserv

This document describes a Next Steps in Signaling (NSIS) Quality-of-Service (QoS) Model for networks that use the Resource Management in Diffserv (RMD) concept. RMD is a technique for adding admission control and preemption function to Differentiated Services (Diffserv) networks. The RMD QoS Model allows devices external to the RMD network to signal reservation requests to Edge nodes in the RMD ne…

RFC59762010-10-01

Y.1541-QOSM: Model for Networks Using Y.1541 Quality-of-Service Classes

Y.1541-QOSM: Model for Networks Using Y.1541 Quality-of-Service Classes

This document describes a QoS-NSLP Quality-of-Service model (QOSM) based on ITU-T Recommendation Y.1541 Network QoS Classes and related guidance on signaling. Y.1541 specifies 8 classes of Network Performance objectives, and the Y.1541-QOSM extensions include additional QSPEC parameters and QOSM processing guidelines. This document defines an Experimental Protocol for the Internet community.

RFC59752010-10-01

QSPEC Template for the Quality-of-Service NSIS Signaling Layer Protocol (NSLP)

QSPEC Template for the Quality-of-Service NSIS Signaling Layer Protocol (NSLP)

The Quality-of-Service (QoS) NSIS signaling layer protocol (NSLP) is used to signal QoS reservations and is independent of a specific QoS model (QOSM) such as IntServ or Diffserv. Rather, all information specific to a QOSM is encapsulated in a separate object, the QSPEC. This document defines a template for the QSPEC including a number of QSPEC parameters. The QSPEC parameters provide a common lan…

RFC59742010-10-01

NSIS Signaling Layer Protocol (NSLP) for Quality-of-Service Signaling

NSIS Signaling Layer Protocol (NSLP) for Quality-of-Service Signaling

This specification describes the NSIS Signaling Layer Protocol (NSLP) for signaling Quality of Service (QoS) reservations in the Internet. It is in accordance with the framework and requirements developed in NSIS. Together with General Internet Signaling Transport (GIST), it provides functionality similar to RSVP and extends it. The QoS NSLP is independent of the underlying QoS specification or ar…

RFC59732010-10-01

NAT/Firewall NSIS Signaling Layer Protocol (NSLP)

NAT/Firewall NSIS Signaling Layer Protocol (NSLP)

This memo defines the NSIS Signaling Layer Protocol (NSLP) for Network Address Translators (NATs) and firewalls. This NSLP allows hosts to signal on the data path for NATs and firewalls to be configured according to the needs of the application data flows. For instance, it enables hosts behind NATs to obtain a publicly reachable address and hosts behind firewalls to receive data traffic. The overa…

RFC59722010-10-01

General Internet Signaling Transport (GIST) State Machine

General Internet Signaling Transport (GIST) State Machine

This document describes state machines for the General Internet Signaling Transport (GIST). The states of GIST nodes for a given flow and their transitions are presented in order to illustrate how GIST may be implemented.

RFC59712010-10-01

GIST: General Internet Signalling Transport

GIST: General Internet Signalling Transport

This document specifies protocol stacks for the routing and transport of per-flow signalling messages along the path taken by that flow through the network. The design uses existing transport and security protocols under a common messaging layer, the General Internet Signalling Transport (GIST), which provides a common service for diverse signalling applications. GIST does not handle signalling ap…

RFC59702010-09-01

DHCPv6 Options for Network Boot

DHCPv6 Options for Network Boot

The Dynamic Host Configuration Protocol for IPv6 (DHCPv6) provides a framework for passing configuration information to nodes on a network. This document describes new options for DHCPv6 that SHOULD be used for booting a node from the network. [STANDARDS-TRACK]

RFC59692010-08-01

IPv6 Rapid Deployment on IPv4 Infrastructures (6rd) -- Protocol Specification

IPv6 Rapid Deployment on IPv4 Infrastructures (6rd) -- Protocol Specification

This document specifies an automatic tunneling mechanism tailored to advance deployment of IPv6 to end users via a service provider's IPv4 network infrastructure. Key aspects include automatic IPv6 prefix delegation to sites, stateless operation, simple provisioning, and service, which is equivalent to native IPv6 at the sites that are served by the mechanism. [STANDARDS-TRACK]

RFC59682010-09-01

Guidelines for Extending the RTP Control Protocol (RTCP)

Guidelines for Extending the RTP Control Protocol (RTCP)

The RTP Control Protocol (RTCP) is used along with the Real-time Transport Protocol (RTP) to provide a control channel between media senders and receivers. This allows constructing a feedback loop to enable application adaptation and monitoring, among other uses. The basic reporting mechanisms offered by RTCP are generic, yet quite powerful and suffice to cover a range of uses. This document provi…

RFC59672010-08-01

The application/pkcs10 Media Type

The application/pkcs10 Media Type

This document specifies a media type used to carry PKCS #10 certification requests as defined in RFC 2986. It carries over the original specification from RFC 2311, which recently has been moved to Historic status, and properly links it to RFC 2986. This document is not an Internet Standards Track specification; it is published for informational purposes.