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

IETF · RFC

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

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

RFC70752013-11-01

Realm-Based Redirection In Diameter

Realm-Based Redirection In Diameter

The Diameter protocol includes a capability for message redirection, controlled by an application-independent "redirect agent". In some circumstances, an operator may wish to redirect messages to an alternate domain without specifying individual hosts. This document specifies an application-specific mechanism by which a Diameter server or proxy (node) can perform such a redirection when the Straig…

RFC70742013-11-01

Revised Definition of the GMPLS Switching Capability and Type Fields

Revised Definition of the GMPLS Switching Capability and Type Fields

GMPLS provides control for multiple switching technologies and for hierarchical switching within a technology. GMPLS routing and signaling use common values to indicate the type of switching technology. These values are carried in routing protocols via the Switching Capability field, and in signaling protocols via the Switching Type field. While the values used in these fields are the primary indi…

RFC70732013-11-01

A Reputation Response Set for Email Identifiers

A Reputation Response Set for Email Identifiers

This document defines a response set for describing assertions a reputation service provider can make about email identifiers, for use in generating reputons.

RFC70722013-11-01

A Reputation Query Protocol

A Reputation Query Protocol

This document defines a mechanism to conduct queries for reputation information over the HyperText Transfer Protocol (HTTP) using JavaScript Object Notation (JSON) as the payload meta-format.

RFC70712013-11-01

A Media Type for Reputation Interchange

A Media Type for Reputation Interchange

This document defines the format of reputation response data ("reputons"), the media type for packaging it, and definition of a registry for the names of reputation applications and response sets.

RFC70702013-11-01

An Architecture for Reputation Reporting

An Architecture for Reputation Reporting

This document describes a general architecture for a reputation-based service, allowing one to request reputation-related data over the Internet, where "reputation" refers to predictions or expectations about an entity or an identifier such as a domain name. The document roughly follows the recommendations of RFC 4101 for describing a protocol model.

RFC70692013-11-01

DECoupled Application Data Enroute (DECADE)

DECoupled Application Data Enroute (DECADE)

Content distribution applications, such as those employing peer-to-peer (P2P) technologies, are widely used on the Internet and make up a large portion of the traffic in many networks. Often, however, content distribution applications use network resources inefficiently. One way to improve efficiency is to introduce storage capabilities within the network and enable cooperation between end-host an…

RFC70682013-11-01

Diameter Overload Control Requirements

Diameter Overload Control Requirements

When a Diameter server or agent becomes overloaded, it needs to be able to gracefully reduce its load, typically by advising clients to reduce traffic for some period of time. Otherwise, it must continue to expend resources parsing and responding to Diameter messages, possibly resulting in a progressively severe overload condition. The existing Diameter mechanisms are not sufficient for managing o…

RFC70672013-11-01

Directory Assistance Problem and High-Level Design Proposal

Directory Assistance Problem and High-Level Design Proposal

Edge TRILL (Transparent Interconnection of Lots of Links) switches currently learn the mapping between MAC (Media Access Control) addresses and their egress TRILL switch by observing the data packets they ingress or egress or by the TRILL ESADI (End-Station Address Distribution Information) protocol. When an ingress TRILL switch receives a data frame for a destination address (MAC&Label) that the …

RFC70662013-11-01

IPv6 for Third Generation Partnership Project (3GPP) Cellular Hosts

IPv6 for Third Generation Partnership Project (3GPP) Cellular Hosts

As the deployment of third and fourth generation cellular networks progresses, a large number of cellular hosts are being connected to the Internet. Standardization organizations have made the Internet Protocol version 6 (IPv6) mandatory in their specifications. However, the concept of IPv6 covers many aspects and numerous specifications. In addition, the characteristics of cellular links in terms…

RFC70652013-11-01

Traversal Using Relays around NAT (TURN) Uniform Resource Identifiers

Traversal Using Relays around NAT (TURN) Uniform Resource Identifiers

This document specifies the syntax of Uniform Resource Identifier (URI) schemes for the Traversal Using Relays around NAT (TURN) protocol. It defines two URI schemes to provision the TURN Resolution Mechanism (RFC 5928).

RFC70642013-11-01

URI Scheme for the Session Traversal Utilities for NAT (STUN) Protocol

URI Scheme for the Session Traversal Utilities for NAT (STUN) Protocol

This document specifies the syntax and semantics of the Uniform Resource Identifier (URI) scheme for the Session Traversal Utilities for NAT (STUN) protocol.

RFC70632013-12-01

Survey Report on Protocol Independent Multicast - Sparse Mode (PIM-SM) Implementations and Deployments

Survey Report on Protocol Independent Multicast - Sparse Mode (PIM-SM) Implementations and Deployments

This document provides supporting documentation to advance the IETF stream's Protocol Independent Multicast - Sparse Mode (PIM-SM) protocol from Proposed Standard to Internet Standard.

RFC70622013-11-01

Framework for GMPLS and PCE Control of G.709 Optical Transport Networks

Framework for GMPLS and PCE Control of G.709 Optical Transport Networks

This document provides a framework to allow the development of protocol extensions to support Generalized Multi-Protocol Label Switching (GMPLS) and Path Computation Element (PCE) control of Optical Transport Networks (OTNs) as specified in ITU-T Recommendation G.709 as published in 2012.

RFC70612013-11-01

eXtensible Access Control Markup Language (XACML) XML Media Type

eXtensible Access Control Markup Language (XACML) XML Media Type

This specification registers an XML-based media type for the eXtensible Access Control Markup Language (XACML).

RFC70602013-11-01

Using LDP Multipoint Extensions on Targeted LDP Sessions

Using LDP Multipoint Extensions on Targeted LDP Sessions

Label Distribution Protocol (LDP) can be used to set up Point-to-Multipoint (P2MP) and Multipoint-to-Multipoint (MP2MP) Label Switched Paths. However, the specification for the Multipoint Extensions to LDP presupposes that the two endpoints of an LDP session are directly connected. The LDP base specification allows for the case where the two endpoints of an LDP session are not directly connected; …

RFC70592013-11-01

A Comparison of IPv6-over-IPv4 Tunnel Mechanisms

A Comparison of IPv6-over-IPv4 Tunnel Mechanisms

This document provides an overview of various ways to tunnel IPv6 packets over IPv4 networks. It covers mechanisms in current use, touches on several mechanisms that are now only of historic interest, and discusses some newer tunnel mechanisms that are not widely used at the time of publication. The goal of the document is helping people with an IPv6-in-IPv4 tunneling need to select the mechanisms…

RFC70582013-11-01

Media Control Channel Framework (CFW) Call Flow Examples

Media Control Channel Framework (CFW) Call Flow Examples

This document provides a list of typical Media Control Channel Framework call flows. It aims at being a simple guide to the use of the interface between Application Servers and MEDIACTRL-based Media Servers, as well as a base reference document for both implementors and protocol researchers.

RFC70572013-12-01

Update to the Extensible Authentication Protocol (EAP) Applicability Statement for Application Bridging for Federated Access Beyond Web (ABFAB)

Update to the Extensible Authentication Protocol (EAP) Applicability Statement for Application Bridging for Federated Access Beyond Web (ABFAB)

This document updates the Extensible Authentication Protocol (EAP) applicability statement from RFC 3748 to reflect recent usage of the EAP protocol in the Application Bridging for Federated Access Beyond web (ABFAB) architecture.

RFC70562013-12-01

Name Attributes for the GSS-API Extensible Authentication Protocol (EAP) Mechanism

Name Attributes for the GSS-API Extensible Authentication Protocol (EAP) Mechanism

The naming extensions to the Generic Security Service Application Programming Interface (GSS-API) provide a mechanism for applications to discover authorization and personalization information associated with GSS-API names. The Extensible Authentication Protocol GSS-API mechanism allows an Authentication, Authorization, and Accounting (AAA) peer to provide authorization attributes alongside an aut…

RFC70552013-12-01

A GSS-API Mechanism for the Extensible Authentication Protocol

A GSS-API Mechanism for the Extensible Authentication Protocol

This document defines protocols, procedures, and conventions to be employed by peers implementing the Generic Security Service Application Program Interface (GSS-API) when using the Extensible Authentication Protocol mechanism. Through the GS2 family of mechanisms defined in RFC 5801, these protocols also define how Simple Authentication and Security Layer (SASL) applications use the Extensible Au…

RFC70542013-11-01

Addressing Requirements and Design Considerations for Per-Interface Maintenance Entity Group Intermediate Points (MIPs)

Addressing Requirements and Design Considerations for Per-Interface Maintenance Entity Group Intermediate Points (MIPs)

The framework for Operations, Administration and Maintenance (OAM) within the MPLS Transport Profile (MPLS-TP) describes how the Maintenance Entity Group Intermediate Points (MIPs) may be situated within network nodes at incoming and outgoing interfaces. This document elaborates on important considerations for internal MIP addressing. More precisely, it describes important restrictions for any mec…

RFC70532013-11-01

SACK-IMMEDIATELY Extension for the Stream Control Transmission Protocol

SACK-IMMEDIATELY Extension for the Stream Control Transmission Protocol

This document updates RFC 4960 by defining a method for the sender of a DATA chunk to indicate that the corresponding Selective Acknowledgment (SACK) chunk should be sent back immediately and should not be delayed. It is done by specifying a bit in the DATA chunk header, called the (I)mmediate bit, which can get set by either the Stream Control Transmission Protocol (SCTP) implementation or the ap…

RFC70522013-10-01

Locator/ID Separation Protocol (LISP) MIB

Locator/ID Separation Protocol (LISP) MIB

This document defines the MIB module that contains managed objects to support the monitoring devices of the Locator/ID Separation Protocol (LISP). These objects provide information useful for monitoring LISP devices, including determining basic LISP configuration information, LISP functional status, and operational counters and other statistics.

RFC70512013-11-01

Analysis of Solution Proposals for Hosts to Learn NAT64 Prefix

Analysis of Solution Proposals for Hosts to Learn NAT64 Prefix

Hosts and applications may benefit from learning if an IPv6 address is synthesized and if NAT64 and DNS64 are present in a network. This document analyzes all proposed solutions (known at the time of writing) for communicating whether the synthesis is taking place, what address format was used, and what IPv6 prefix was used by the NAT64 and DNS64. These solutions enable both NAT64 avoidance and lo…

RFC70502013-11-01

Discovery of the IPv6 Prefix Used for IPv6 Address Synthesis

Discovery of the IPv6 Prefix Used for IPv6 Address Synthesis

This document describes a method for detecting the presence of DNS64 and for learning the IPv6 prefix used for protocol translation on an access network. The method depends on the existence of a well-known IPv4-only fully qualified domain name "ipv4only.arpa.". The information learned enables nodes to perform local IPv6 address synthesis and to potentially avoid NAT64 on dual-stack and multi-inter…

RFC70492013-10-01

Concise Binary Object Representation (CBOR)

Concise Binary Object Representation (CBOR)

The Concise Binary Object Representation (CBOR) is a data format whose design goals include the possibility of extremely small code size, fairly small message size, and extensibility without the need for version negotiation. These design goals make it different from earlier binary serializations such as ASN.1 and MessagePack.

RFC70482014-01-01

Neighbor Unreachability Detection Is Too Impatient

Neighbor Unreachability Detection Is Too Impatient

IPv6 Neighbor Discovery includes Neighbor Unreachability Detection. That function is very useful when a host has an alternative neighbor -- for instance, when there are multiple default routers -- since it allows the host to switch to the alternative neighbor in a short time. By default, this time is 3 seconds after the node starts probing. However, if there are no alternative neighbors, this time…

RFC70472013-12-01

The Open vSwitch Database Management Protocol

The Open vSwitch Database Management Protocol

Open vSwitch is an open-source software switch designed to be used as a vswitch (virtual switch) in virtualized server environments. A vswitch forwards traffic between different virtual machines (VMs) on the same physical host and also forwards traffic between VMs and the physical network. Open vSwitch is open to programmatic extension and control using OpenFlow and the OVSDB (Open vSwitch Databas…

RFC70462013-12-01

A Common API for Transparent Hybrid Multicast

A Common API for Transparent Hybrid Multicast

Group communication services exist in a large variety of flavors and technical implementations at different protocol layers. Multicast data distribution is most efficiently performed on the lowest available layer, but a heterogeneous deployment status of multicast technologies throughout the Internet requires an adaptive service binding at runtime. Today, it is difficult to write an application th…