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

IETF · RFC

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

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

RFC48522007-04-01

IPv6 Enterprise Network Analysis - IP Layer 3 Focus

IPv6 Enterprise Network Analysis - IP Layer 3 Focus

This document analyzes the transition to IPv6 in enterprise networks focusing on IP Layer 3. These networks are characterized as having multiple internal links and one or more router connections to one or more Providers, and as being managed by a network operations entity. The analysis focuses on a base set of transition notational networks and requirements expanded from a previous document on ent…

RFC48512007-05-01

The Flexible Authentication via Secure Tunneling Extensible Authentication Protocol Method (EAP-FAST)

The Flexible Authentication via Secure Tunneling Extensible Authentication Protocol Method (EAP-FAST)

This document defines the Extensible Authentication Protocol (EAP) based Flexible Authentication via Secure Tunneling (EAP-FAST) protocol. EAP-FAST is an EAP method that enables secure communication between a peer and a server by using the Transport Layer Security (TLS) to establish a mutually authenticated tunnel. Within the tunnel, Type-Length-Value (TLV) objects are used to convey authenticatio…

RFC48502007-04-01

Declarative Public Extension Key for Internet Small Computer Systems Interface (iSCSI) Node Architecture

Declarative Public Extension Key for Internet Small Computer Systems Interface (iSCSI) Node Architecture

The Internet Small Computer Systems Interface (iSCSI) protocol, described in RFC 3720, allows for extension items to the protocol in the form of Private or Public Extension Keys. This document describes a Public Extension Key for the purpose of enhancing iSCSI supportability. The key accomplishes this objective by allowing iSCSI nodes to communicate architecture details during the iSCSI login sequ…

RFC48492007-04-01

RADIUS Filter Rule Attribute

RADIUS Filter Rule Attribute

While RFC 2865 defines the Filter-Id attribute, it requires that the Network Access Server (NAS) be pre-populated with the desired filters. However, in situations where the server operator does not know which filters have been pre-populated, it is useful to specify filter rules explicitly. This document defines the NAS-Filter-Rule attribute within the Remote Authentication Dial In User Service (RA…

RFC48482007-04-01

Domain-Based Application Service Location Using URIs and the Dynamic Delegation Discovery Service (DDDS)

Domain-Based Application Service Location Using URIs and the Dynamic Delegation Discovery Service (DDDS)

The purpose of this document is to define a new, straightforward Dynamic Delegation Discovery Service (DDDS) application to allow mapping of domain names to URIs for particular application services and protocols. Although defined as a new DDDS application, dubbed U-NAPTR, this is effectively an extension of the Straightforward NAPTR (S-NAPTR) DDDS Application. [STANDARDS-TRACK]

RFC48472007-04-01

Framework and Requirements for Layer 1 Virtual Private Networks

Framework and Requirements for Layer 1 Virtual Private Networks

This document provides a framework and service level requirements for Layer 1 Virtual Private Networks (L1VPNs). This framework is intended to aid in developing and standardizing protocols and mechanisms to support interoperable L1VPNs. The document examines motivations for L1VPNs, high level (service level) requirements, and outlines some of the architectural models that might be used to build L1…

RFC48462007-07-01

Independent Submissions to the RFC Editor

Independent Submissions to the RFC Editor

There is a long-standing tradition in the Internet community, predating the Internet Engineering Task Force (IETF) by many years, of use of the RFC Series to publish materials that are not rooted in the IETF standards process and its review and approval mechanisms. These documents, known as "Independent Submissions", serve a number of important functions for the Internet community, both inside and…

RFC48452007-07-01

Process for Publication of IAB RFCs

Process for Publication of IAB RFCs

From time to time, the Internet Architecture Board (IAB) publishes documents as Requests for Comments (RFCs). This document defines the process by which those documents are produced, reviewed, and published in the RFC Series. This memo provides information for the Internet community.

RFC48442007-07-01

The RFC Series and RFC Editor

The RFC Series and RFC Editor

This document describes the framework for an RFC Series and an RFC Editor function that incorporate the principles of organized community involvement and accountability that has become necessary as the Internet technical community has grown, thereby enabling the RFC Series to continue to fulfill its mandate. This memo provides information for the Internet community.

RFC48432007-04-01

An IPv6 Prefix for Overlay Routable Cryptographic Hash Identifiers (ORCHID)

An IPv6 Prefix for Overlay Routable Cryptographic Hash Identifiers (ORCHID)

This document introduces Overlay Routable Cryptographic Hash Identifiers (ORCHID) as a new, experimental class of IPv6-address- like identifiers. These identifiers are intended to be used as endpoint identifiers at applications and Application Programming Interfaces (API) and not as identifiers for network location at the IP layer, i.e., locators. They are designed to appear as application layer e…

RFC48422007-04-01

Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Circuit Emulation over Packet (CEP)

Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Circuit Emulation over Packet (CEP)

This document provides encapsulation formats and semantics for emulating Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) circuits and services over MPLS. [STANDARDS-TRACK]

RFC48412007-03-01

RFC 4181 Update to Recognize the IETF Trust

RFC 4181 Update to Recognize the IETF Trust

This document updates RFC 4181, "Guidelines for Authors and Reviewers of MIB Documents", to recognize the creation of the IETF Trust. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.

RFC48402007-04-01

Multiple Encapsulation Methods Considered Harmful

Multiple Encapsulation Methods Considered Harmful

This document describes architectural and operational issues that arise from link-layer protocols supporting multiple Internet Protocol encapsulation methods. This memo provides information for the Internet community.

RFC48392007-04-01

Media Type Registrations for the Open eBook Publication Structure (OEBPS) Package File (OPF)

Media Type Registrations for the Open eBook Publication Structure (OEBPS) Package File (OPF)

This document serves to register a media type for the Open eBook Publication Structure (OEBPS) Package Files. This memo provides information for the Internet community.

RFC48382007-04-01

Delay-Tolerant Networking Architecture

Delay-Tolerant Networking Architecture

This document describes an architecture for delay-tolerant and disruption-tolerant networks, and is an evolution of the architecture originally designed for the Interplanetary Internet, a communication system envisioned to provide Internet-like services across interplanetary distances in support of deep space exploration. This document describes an architecture that addresses a variety of problems…

RFC48372007-07-01

Managed Objects of Ethernet Passive Optical Networks (EPON)

Managed Objects of Ethernet Passive Optical Networks (EPON)

This document defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based Internets. In particular, it defines objects for managing interfaces that conform to the Ethernet Passive Optical Networks (EPON) standard as defined in the IEEE Std 802.3ah-2004, which are extended capabilities to the Ethernet like interfaces. [STANDARDS-TRACK]

RFC48362007-04-01

Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs)

Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs)

This document defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for managing IEEE 802.3 Medium Attachment Units (MAUs). This document obsoletes RFC 3636. It amends that specification by moving MAU type OBJECT-IDENTITY definitions and relevant textual conventions into a separate Internet …

RFC48352007-04-01

Cryptographic Algorithm Implementation Requirements for Encapsulating Security Payload (ESP) and Authentication Header (AH)

Cryptographic Algorithm Implementation Requirements for Encapsulating Security Payload (ESP) and Authentication Header (AH)

The IPsec series of protocols makes use of various cryptographic algorithms in order to provide security services. The Encapsulating Security Payload (ESP) and the Authentication Header (AH) provide two mechanisms for protecting data being sent over an IPsec Security Association (SA). To ensure interoperability between disparate implementations, it is necessary to specify a set of mandatory-to-imp…

RFC48342007-04-01

Requirements for Multicast in Layer 3 Provider-Provisioned Virtual Private Networks (PPVPNs)

Requirements for Multicast in Layer 3 Provider-Provisioned Virtual Private Networks (PPVPNs)

This document presents a set of functional requirements for network solutions that allow the deployment of IP multicast within Layer 3 (L3) Provider-Provisioned Virtual Private Networks (PPVPNs). It specifies requirements both from the end user and service provider standpoints. It is intended that potential solutions specifying the support of IP multicast within such VPNs will use these requiremen…

RFC48332007-04-01

Timezone Options for DHCP

Timezone Options for DHCP

Two common ways to communicate timezone information are POSIX 1003.1 timezone strings and timezone database names. This memo specifies DHCP options for each of those methods. The DHCPv4 time offset option is deprecated. [STANDARDS-TRACK]

RFC48322007-04-01

Security Threats to Network-Based Localized Mobility Management (NETLMM)

Security Threats to Network-Based Localized Mobility Management (NETLMM)

This document discusses security threats to network-based localized mobility management. Threats may occur on two interfaces: the interface between a localized mobility anchor and a mobile access gateway, as well as the interface between a mobile access gateway and a mobile node. Threats to the former interface impact the localized mobility management protocol itself. This memo provides informatio…

RFC48312007-04-01

Goals for Network-Based Localized Mobility Management (NETLMM)

Goals for Network-Based Localized Mobility Management (NETLMM)

In this document, design goals for a network-based localized mobility management (NETLMM) protocol are discussed. This memo provides information for the Internet community.

RFC48302007-04-01

Problem Statement for Network-Based Localized Mobility Management (NETLMM)

Problem Statement for Network-Based Localized Mobility Management (NETLMM)

Localized mobility management is a well-understood concept in the IETF, with a number of solutions already available. This document looks at the principal shortcomings of the existing solutions, all of which involve the host in mobility management, and makes a case for network-based local mobility management. This memo provides information for the Internet community.

RFC48292007-04-01

Label Switched Path (LSP) Preemption Policies for MPLS Traffic Engineering

Label Switched Path (LSP) Preemption Policies for MPLS Traffic Engineering

When the establishment of a higher priority (Traffic Engineering Label Switched Path) TE LSP requires the preemption of a set of lower priority TE LSPs, a node has to make a local decision to select which TE LSPs will be preempted. The preempted LSPs are then rerouted by their respective \%Head-end Label Switch Router (LSR). This document presents a flexible policy that can be used to achieve diff…

RFC48282007-04-01

TCP Friendly Rate Control (TFRC): The Small-Packet (SP) Variant

TCP Friendly Rate Control (TFRC): The Small-Packet (SP) Variant

This document proposes a mechanism for further experimentation, but not for widespread deployment at this time in the global Internet. TCP-Friendly Rate Control (TFRC) is a congestion control mechanism for unicast flows operating in a best-effort Internet environment (RFC 3448). TFRC was intended for applications that use a fixed packet size, and was designed to be reasonably fair when competing f…

RFC48272007-05-01

An Extensible Markup Language (XML) Configuration Access Protocol (XCAP) Usage for Manipulating Presence Document Contents

An Extensible Markup Language (XML) Configuration Access Protocol (XCAP) Usage for Manipulating Presence Document Contents

This document describes a usage of the Extensible Markup Language (XML) Configuration Access Protocol (XCAP) for manipulating the contents of Presence Information Data Format (PIDF) based presence documents. It is intended to be used in Session Initiation Protocol (SIP) based presence systems, where the Event State Compositor can use the XCAP-manipulated presence document as one of the inputs on w…

RFC48262007-05-01

Extensible Markup Language (XML) Formats for Representing Resource Lists

Extensible Markup Language (XML) Formats for Representing Resource Lists

In multimedia communications, presence, and instant messaging systems, there is a need to define Uniform Resource Identifiers (URIs) that represent services that are associated with a group of users. One example is a resource list service. If a user sends a Session Initiation Protocol (SIP) SUBSCRIBE message to the URI representing the resource list service, the server will obtain the state of the…

RFC48252007-05-01

The Extensible Markup Language (XML) Configuration Access Protocol (XCAP)

The Extensible Markup Language (XML) Configuration Access Protocol (XCAP)

This specification defines the Extensible Markup Language (XML) Configuration Access Protocol (XCAP). XCAP allows a client to read, write, and modify application configuration data stored in XML format on a server. XCAP maps XML document sub-trees and element attributes to HTTP URIs, so that these components can be directly accessed by HTTP. [STANDARDS-TRACK]

RFC48242007-04-01

The Transmission of IP Datagrams over the Semaphore Flag Signaling System (SFSS)

The Transmission of IP Datagrams over the Semaphore Flag Signaling System (SFSS)

This document specifies a method for encapsulating and transmitting IPv4/IPv6 packets over the Semaphore Flag Signal System (SFSS). This memo provides information for the Internet community.

RFC48232007-04-01

FTP Transport for Secure Peer-to-Peer Business Data Interchange over the Internet

FTP Transport for Secure Peer-to-Peer Business Data Interchange over the Internet

This Applicability Statement (AS) describes how to exchange structured business data securely using the File Transfer Protocol (FTP) for XML, Binary, Electronic Data Interchange (EDI - ANSI X12 or UN/EDIFACT), or other data used for business-to-business data interchange for which MIME packaging can be accomplished using standard MIME content types. Authentication and data confidentiality are obtai…