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

IETF · RFC

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

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

RFC42372005-10-01

Voice Messaging Directory Service

Voice Messaging Directory Service

This document provides details of the Voice Profile for Internet Mail (VPIM) directory service. The service provides the email address of the recipient that is given a telephone number. It optionally provides the spoken name of the recipient and the media capabilities of the recipient. The VPIM directory Schema provides essential additional attributes to recreate the voice mail user experience usi…

RFC42362005-11-01

HTTP Adaptation with Open Pluggable Edge Services (OPES)

HTTP Adaptation with Open Pluggable Edge Services (OPES)

Open Pluggable Edge Services (OPES) framework documents several application-agnostic mechanisms such as OPES tracing, OPES bypass, and OPES callout protocol. This document extends those generic mechanisms for Hypertext Transfer Protocol (HTTP) adaptation. Together, application-agnostic OPES documents and this HTTP profile constitute a complete specification for HTTP adaptation with OPES. [STANDARD…

RFC42352005-11-01

An INVITE-Initiated Dialog Event Package for the Session Initiation Protocol (SIP)

An INVITE-Initiated Dialog Event Package for the Session Initiation Protocol (SIP)

This document defines a dialog event package for the SIP Events architecture, along with a data format used in notifications for this package. The dialog package allows users to subscribe to another user and to receive notification of the changes in state of INVITE-initiated dialog usages in which the subscribed-to user is involved. [STANDARDS-TRACK]

RFC42342005-10-01

Augmented BNF for Syntax Specifications: ABNF

Augmented BNF for Syntax Specifications: ABNF

Internet technical specifications often need to define a formal syntax. Over the years, a modified version of Backus-Naur Form (BNF), called Augmented BNF (ABNF), has been popular among many Internet specifications. The current specification documents ABNF. It balances compactness and simplicity, with reasonable representational power. The differences between standard BNF and ABNF involve naming r…

RFC42332006-01-01

Integrated Services Digital Network (ISDN) Q.921-User Adaptation Layer

Integrated Services Digital Network (ISDN) Q.921-User Adaptation Layer

This document defines a protocol for backhauling of Integrated Services Digital Network (ISDN) Q.921 User messages over IP using the Stream Control Transmission Protocol (SCTP). This protocol would be used between a Signaling Gateway (SG) and Media Gateway Controller (MGC). It is assumed that the SG receives ISDN signaling over a standard ISDN interface. This document obsoletes RFC 3057. [STANDARD…

RFC42312005-12-01

Identifiers and Test Vectors for HMAC-SHA-224, HMAC-SHA-256, HMAC-SHA-384, and HMAC-SHA-512

Identifiers and Test Vectors for HMAC-SHA-224, HMAC-SHA-256, HMAC-SHA-384, and HMAC-SHA-512

This document provides test vectors for the HMAC-SHA-224, HMAC-SHA-256, HMAC-SHA-384, and HMAC-SHA-512 message authentication schemes. It also provides ASN.1 object identifiers and Uniform Resource Identifiers (URIs) to identify use of these schemes in protocols. The test vectors provided in this document may be used for conformance testing. [STANDARDS-TRACK]

RFC42302005-12-01

RSVP Security Properties

RSVP Security Properties

This document summarizes the security properties of RSVP. The goal of this analysis is to benefit from previous work done on RSVP and to capture knowledge about past activities. This memo provides information for the Internet community.

RFC42292005-12-01

HTTP Header Field Registrations

HTTP Header Field Registrations

This document defines the initial contents of a permanent IANA registry for HTTP header fields and a provisional repository for HTTP header fields, per RFC 3864. This memo provides information for the Internet community.

RFC42282005-12-01

Requirements for an IETF Draft Submission Toolset

Requirements for an IETF Draft Submission Toolset

This document specifies requirements for an IETF toolset to facilitate Internet-Draft submission, validation, and posting. This memo provides information for the Internet community.

RFC42272006-01-01

Using the Simple Object Access Protocol (SOAP) in Blocks Extensible Exchange Protocol (BEEP)

Using the Simple Object Access Protocol (SOAP) in Blocks Extensible Exchange Protocol (BEEP)

This memo specifies a Simple Object Access Protocol (SOAP) binding to the Blocks Extensible Exchange Protocol (BEEP) core. A SOAP binding describes how SOAP messages are transmitted in the network. The SOAP is an XML-based (eXtensible Markup Language) messaging protocol used to implement a wide variety of distributed messaging models. It defines a message format and describes a variety of message …

RFC42262005-12-01

HOTP: An HMAC-Based One-Time Password Algorithm

HOTP: An HMAC-Based One-Time Password Algorithm

This document describes an algorithm to generate one-time password values, based on Hashed Message Authentication Code (HMAC). A security analysis of the algorithm is presented, and important parameters related to the secure deployment of the algorithm are discussed. The proposed algorithm can be used across a wide range of network applications ranging from remote Virtual Private Network (VPN) acc…

RFC42252005-12-01

Mobile IP Version 6 Route Optimization Security Design Background

Mobile IP Version 6 Route Optimization Security Design Background

This document is an account of the rationale behind the Mobile IPv6 (MIPv6) Route Optimization security design. The purpose of this document is to present the thinking and to preserve the reasoning behind the Mobile IPv6 security design in 2001 - 2002. The document has two target audiences: (1) helping MIPv6 implementors to better understand the design choices in MIPv6 security procedures, and (2)…

RFC42242006-01-01

RObust Header Compression (ROHC): ROHC over Channels That Can Reorder Packets

RObust Header Compression (ROHC): ROHC over Channels That Can Reorder Packets

RObust Header Compression (ROHC), RFC 3095, defines a framework for header compression, along with a number of compression protocols (profiles). One operating assumption for the profiles defined in RFC 3095 is that the channel between compressor and decompressor is required to maintain packet ordering. This document discusses aspects of using ROHC over channels that can reorder packets. It provide…

RFC42232005-10-01

Reclassification of RFC 1863 to Historic

Reclassification of RFC 1863 to Historic

This memo reclassifies RFC 1863, A BGP/IDRP Route Server alternative to a full mesh routing, to Historic status. This memo also obsoletes RFC 1863. This memo provides information for the Internet community.

RFC42222005-10-01

Приоритетная обработка отдельных пакетов OSPF версии 2 и предотвращение перегрузки

Prioritized Treatment of Specific OSPF Version 2 Packets and Congestion Avoidance

RFC 4222 описывает рекомендуемые методы повышения масштабируемости и устойчивости крупных сетей с OSPFv2 при перегрузке управляющего трафика, в частности во время «штормов» LSA. Основная рекомендация состоит в приоритетной обработке пакетов Hello и подтверждений Link State Acknowledgement по сравнению с прочими пакетами OSPF с учётом ограничений криптографической аутентификации. Документ также пре…

Читать русский перевод →
RFC42212005-11-01

Multiprotocol Label Switching (MPLS) Management Overview

Multiprotocol Label Switching (MPLS) Management Overview

A range of Management Information Base (MIB) modules has been developed to help model and manage the various aspects of Multiprotocol Label Switching (MPLS) networks. These MIB modules are defined in separate documents that focus on the specific areas of responsibility of the modules that they describe. This document describes the management architecture for MPLS and indicates the interrelationshi…

RFC42202005-11-01

Traffic Engineering Link Management Information Base

Traffic Engineering Link Management Information Base

This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects for modeling TE links as described in the Link Bundling in MPLS Traffic Engineering (TE) document. [STANDARDS-TRACK]

RFC42192005-10-01

Things Multihoming in IPv6 (MULTI6) Developers Should Think About

Things Multihoming in IPv6 (MULTI6) Developers Should Think About

This document specifies a set of questions that authors should be prepared to answer as part of a solution to multihoming with IPv6. The questions do not assume that multihoming is the only problem of interest, nor do they demand a more general solution. This memo provides information for the Internet community.

RFC42182005-10-01

Threats Relating to IPv6 Multihoming Solutions

Threats Relating to IPv6 Multihoming Solutions

This document lists security threats related to IPv6 multihoming. Multihoming can introduce new opportunities to redirect packets to different, unintended IP addresses. The intent is to look at how IPv6 multihoming solutions might make the Internet less secure; we examine threats that are inherent to all IPv6 multihoming solutions rather than study any specific proposed solution. The threats in th…

RFC42172005-10-01

Securing FTP with TLS

Securing FTP with TLS

This document describes a mechanism that can be used by FTP clients and servers to implement security and authentication using the TLS protocol defined by RFC 2246, "The TLS Protocol Version 1.0.", and the extensions to the FTP protocol defined by RFC 2228, "FTP Security Extensions". It describes the subset of the extensions that are required and the parameters to be used, discusses some of the po…

RFC42162005-11-01

MPLS Inter-Autonomous System (AS) Traffic Engineering (TE) Requirements

MPLS Inter-Autonomous System (AS) Traffic Engineering (TE) Requirements

This document discusses requirements for the support of inter-AS MPLS Traffic Engineering (MPLS TE). Its main objective is to present a set of requirements and scenarios which would result in general guidelines for the definition, selection, and specification development for any technical solution(s) meeting these requirements and supporting the scenarios. This memo provides information for the In…

RFC42152005-10-01

Analysis on IPv6 Transition in Third Generation Partnership Project (3GPP) Networks

Analysis on IPv6 Transition in Third Generation Partnership Project (3GPP) Networks

This document analyzes the transition to IPv6 in Third Generation Partnership Project (3GPP) packet networks. These networks are based on General Packet Radio Service (GPRS) technology, and the radio network architecture is based on Global System for Mobile Communications (GSM) or Universal Mobile Telecommunications System (UMTS)/Wideband Code Division Multiple Access (WCDMA) technology. The focus…

RFC42142005-10-01

Intra-Site Automatic Tunnel Addressing Protocol (ISATAP)

Intra-Site Automatic Tunnel Addressing Protocol (ISATAP)

The Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) connects IPv6 hosts/routers over IPv4 networks. ISATAP views the IPv4 network as a link layer for IPv6 and views other nodes on the network as potential IPv6 hosts/routers. ISATAP supports an automatic tunneling abstraction similar to the Non-Broadcast Multiple Access (NBMA) model. This memo defines an Experimental Protocol for the Inter…

RFC42132005-10-01

Basic Transition Mechanisms for IPv6 Hosts and Routers

Basic Transition Mechanisms for IPv6 Hosts and Routers

This document specifies IPv4 compatibility mechanisms that can be implemented by IPv6 hosts and routers. Two mechanisms are specified, dual stack and configured tunneling. Dual stack implies providing complete implementations of both versions of the Internet Protocol (IPv4 and IPv6), and configured tunneling provides a means to carry IPv6 packets over unmodified IPv4 routing infrastructures. This …

RFC42122005-10-01

Alternative Certificate Formats for the Public-Key Infrastructure Using X.509 (PKIX) Certificate Management Protocols

Alternative Certificate Formats for the Public-Key Infrastructure Using X.509 (PKIX) Certificate Management Protocols

The Public-Key Infrastructure using X.509 (PKIX) Working Group of the Internet Engineering Task Force (IETF) has defined a number of certificate management protocols. These protocols are primarily focused on X.509v3 public-key certificates. However, it is sometimes desirable to manage certificates in alternative formats as well. This document specifies how such certificates may be requested using …

RFC42112005-09-01

Internet X.509 Public Key Infrastructure Certificate Request Message Format (CRMF)

Internet X.509 Public Key Infrastructure Certificate Request Message Format (CRMF)

This document describes the Certificate Request Message Format (CRMF) syntax and semantics. This syntax is used to convey a request for a certificate to a Certification Authority (CA), possibly via a Registration Authority (RA), for the purposes of X.509 certificate production. The request will typically include a public key and the associated registration information. This document does not defin…

RFC42102005-09-01

Internet X.509 Public Key Infrastructure Certificate Management Protocol (CMP)

Internet X.509 Public Key Infrastructure Certificate Management Protocol (CMP)

This document describes the Internet X.509 Public Key Infrastructure (PKI) Certificate Management Protocol (CMP). Protocol messages are defined for X.509v3 certificate creation and management. CMP provides on-line interactions between PKI components, including an exchange between a Certification Authority (CA) and a client system. [STANDARDS-TRACK]

RFC42092005-10-01

Link Management Protocol (LMP) for Dense Wavelength Division Multiplexing (DWDM) Optical Line Systems

Link Management Protocol (LMP) for Dense Wavelength Division Multiplexing (DWDM) Optical Line Systems

The Link Management Protocol (LMP) is defined to manage traffic engineering (TE) links. In its present form, LMP focuses on peer nodes, i.e., nodes that peer in signaling and/or routing. This document proposes extensions to LMP to allow it to be used between a peer node and an adjacent optical line system (OLS). These extensions are intended to satisfy the "Optical Link Interface Requirements" des…

RFC42082005-10-01

Generalized Multiprotocol Label Switching (GMPLS) User-Network Interface (UNI): Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Support for the Overlay Model

Generalized Multiprotocol Label Switching (GMPLS) User-Network Interface (UNI): Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Support for the Overlay Model

Generalized Multiprotocol Label Switching (GMPLS) defines both routing and signaling protocols for the creation of Label Switched Paths (LSPs) in various switching technologies. These protocols can be used to support a number of deployment scenarios. This memo addresses the application of GMPLS to the overlay model. [STANDARDS-TRACK]

RFC42072005-10-01

Synchronous Optical Network (SONET)/Synchronous Digital Hierarchy (SDH) Encoding for Link Management Protocol (LMP) Test Messages

Synchronous Optical Network (SONET)/Synchronous Digital Hierarchy (SDH) Encoding for Link Management Protocol (LMP) Test Messages

This document details the Synchronous Optical Network (SONET)/Synchronous Digital Hierarchy (SDH) technology-specific information needed when sending Link Management Protocol (LMP) test messages. [STANDARDS-TRACK]