Опубликованные RFC, связи обновления и замены, официальные статусы и русские переводы.
Реестр · 9 842 документов
The Internet Message Action Protocol (IMAP4) Child Mailbox Extension
The CHILDREN extension provides a mechanism for a client to efficiently determine if a particular mailbox has children, without issuing a LIST '' * or a LIST '' % for each mailbox name.
Small Computer Systems Interface protocol over the Internet (iSCSI) Requirements and Design Considerations
The IP Storage Working group is chartered with developing comprehensive technology to transport block storage data over IP protocols. This effort includes a protocol to transport the Small Computer Systems Interface (SCSI) protocol over the Internet (iSCSI). The initial version of the iSCSI protocol will define a mapping of SCSI transport protocol over TCP/IP so that SCSI storage controllers (prin…
Applicability Statement for Traffic Engineering with MPLS
This document describes the applicability of Multiprotocol Label Switching (MPLS) to traffic engineering in IP networks. Special considerations for deployment of MPLS for traffic engineering in operational contexts are discussed and the limitations of the MPLS approach to traffic engineering are highlighted.
Border Gateway Protocol (BGP) Persistent Route Oscillation Condition
The Border Gateway Protocol (BGP) [1] is an inter-Autonomous System routing protocol. The primary function of a BGP speaking system is to exchange network reachability information with other BGP systems.
IP Mobility Support for IPv4
The Application Exchange (APEX) Presence Service
This memo describes the APEX presence service, addressed as the well- known endpoint 'apex=presence'. The presence service is used to manage presence information for APEX endpoints.
The Application Exchange (APEX) Option Party Pack, Part Deux!
APEX, at its core, provides a best-effort application-layer datagram service. Options are used to alter the semantics of the core service. This memo defines various options to change the default behavior of APEX's 'relaying mesh'.
The Application Exchange (APEX) Access Service
This memo describes the APEX access service, addressed as the well- known endpoint 'apex=access'. The access service is used to control use of both the APEX 'relaying mesh' and other APEX services.
The Application Exchange Core
This memo describes APEX, an extensible, asynchronous message relaying service for application layer programs.
Date and Time on the Internet: Timestamps
This document defines a date and time format for use in Internet protocols that is a profile of the ISO 8601 standard for representation of dates and times using the Gregorian calendar.
Dual Stack Hosts Using "Bump-in-the-API" (BIA)
This document specifies a mechanism of dual stack hosts using a technique called 'Bump-in-the-API'(BIA) which allows for the hosts to communicate with other IPv6 hosts using existing IPv4 applications. The goal of this mechanism is the same as that of the Bump-in-the-stack mechanism [BIS], but this mechanism provides the translation method between the IPv4 APIs and IPv6 APIs. Thus, the goal is sim…
Class Extensions for PPP over Asynchronous Transfer Mode Adaptation Layer 2
PPP over ATM Adaptation Layer 2 defines the encapsulation that allows a PPP session to be transported over an ATM virtual circuit using the AAL2 adaptation layer. This document defines a set of class extensions to PPP over AAL2 that implement equivalent functionality to Multi Class Multi Link PPP over a single ATM virtual circuit. Instead of using Multi Link PPP as the basis for fragmentation func…
PPP Over Asynchronous Transfer Mode Adaptation Layer 2 (AAL2)
The Point-to-Point Protocol (PPP) [1] provides a standard method for transporting multi-protocol datagrams over point-to-point links.
MIME-based Secure Peer-to-Peer Business Data Interchange over the Internet
This document describes how to exchange structured business data securely using SMTP transport for Electronic Data Interchange, (EDI - either the American Standards Committee X12 or UN/EDIFACT, Electronic Data Interchange for Administration, Commerce and Transport), XML or other data used for business to business data interchange. The data is packaged using standard MIME content-types. Authenticat…
Policy-Based Accounting
This document describes policy-based accounting which is an approach to provide flexibility to accounting architectures. Accounting policies describe the configuration of an accounting architecture in a standardized way. They are used to instrument the accounting architecture and can be exchanged between AAA entities in order to share configuration information. This document describes building blo…
Signaling System 7 (SS7) Message Transfer Part 3 (MTP3) - User Adaptation Layer (M3UA)
This Internet Draft defines a protocol for supporting the transport of any SS7 MTP3-User signalling (e.g., ISUP and SCCP messages) over IP using the services of the Stream Control Transmission Protocol. Also, provision is made for protocol elements that enable a seamless operation of the MTP3-User peers in the SS7 and IP domains. This protocol would be used between a Signalling Gateway (SG) and a …
Signaling System 7 (SS7) Message Transfer Part 2 (MTP2) - User Adaptation Layer
This Internet Draft defines a protocol for backhauling of SS7 MTP2 User signaling 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 SS7 signaling over a standard SS7 interface using the SS7 Message Transfer Part (MTP) to provide transport. The Si…
Special-Use IPv4 Addresses
This document describes the global and other specialized IPv4 address blocks that have been assigned by the IANA. It does not address IPv4 address space assigned to operators and users through the Regional Internet Registries. It also does not address allocations or assignments of IPv6 addresses or autonomous system numbers.
Security Mechanism Agreement for the Session Initiation Protocol (SIP)
This document defines new functionality for negotiating the security mechanisms used between a Session Initiation Protocol (SIP) user agent and its next-hop SIP entity. This new functionality supplements the existing methods of choosing security mechanisms between SIP entities.
Session Initiation Protocol (SIP) Extension Header Field for Registering Non-Adjacent Contacts
The REGISTER function is used in a SIP system primarily to associate a temporary contact address with an address-of-record. This contact is generally in the form of a URI, such as Contact: <sip:alice@pc33.atlanta.com> and is generally dynamic and associated with the IP address or hostname of the SIP UA. The problem is that network topology may have one or more SIP proxies between the UA and the re…
The Reason Header Field for the Session Initiation Protocol (SIP)
The REGISTER function is used in a Session Initiation Protocol (SIP) system primarily to associate a temporary contact address with an address-of-record. This contact is generally in the form of a Uniform Resource Identifier (URI), such as Contact: <sip:alice@pc33.atlanta.com> and is generally dynamic and associated with the IP address or hostname of the SIP User Agent (UA). The problem is that ne…
Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity within Trusted Networks
This document describes private extensions to SIP that enable a network of trusted SIP servers to assert the identity of authenticated users, and the application of existing privacy mechanisms to the identity problem. The use of these extensions is only applicable inside an administrative domain with previously agreed-upon policies for generation, transport and usage of such information. This docu…
Short Term Requirements for Network Asserted Identity
There is no requirement for identities asserted by a UA in a SIP message to be anything other than the user's desired alias. A Network Asserted Identity is an identity initially derived by a SIP network intermediary as a result of an authentication process. This draft describes short term requirements for the exchange of Network Asserted Identities within networks of securely interconnected truste…
A Privacy Mechanism for the Session Initiation Protocol (SIP)
This document defines new mechanisms for the Session Initiation Protocol (SIP) in support of privacy. Specifically, guidelines are provided for the creation of messages that do not divulge personal identity information. A new 'privacy service' logical role for intermediaries is defined to answer some privacy requirements that user agents cannot satisfy themselves. Finally, means are presented by w…
Signaling Compression (SigComp) Requirements & Assumptions
In wireless environments and especially in cellular systems, e.g. GSM (Global System for Mobile communications) and UMTS (Universal Mobile Telecommunications System), there is a need to maximize the transport efficiency for data over the radio interface. With the introduction of SIP/SDP (Session Initiation Protocol/Session Description Protocol) to cellular devices, compression of the signaling mes…
Signaling Compression (SigComp) - Extended Operations
This document describes how to implement certain mechanisms in SigComp (Signaling Compression), RFC XXX, which can significantly improve the compression efficiency compared to using simple per- message compression. SigComp uses a UDVM (Universal Decompressor Virtual Machine) for decompression, and the mechanisms described in this document are possible to implement using the UDVM instructions defin…
Signaling Compression (SigComp)
This document defines SigComp, a solution for compressing messages generated by application protocols such as SIP [RFC-2543] and RTSP [RFC-2326]. The architecture and pre-requisites of SigComp are outlined, along with the format of the SigComp message. Decompression functionality for SigComp is provided by a 'Universal Decompressor Virtual Machine' optimized for the task of running decompression a…
Dynamic Host Configuration Protocol (DHCPv6) Options for Session Initiation Protocol (SIP) Servers
This document defines a DHCPv6 option that contains a list of domain names or IPv6 addresses that can be mapped to one or more SIP outbound proxy servers. This is one of the many methods that a SIP client can use to obtain the addresses of such a local SIP server.
Framework Policy Information Base
This document defines a set of PRovisioning Classes (PRCs) and textual conventions that are common to all clients that provision policy using Common Open Policy Service (COPS) protocol for Provisioning. Structure of Policy Provisioning Information (SPPI) describes a structure for specifying policy information that can then be transmitted to a network device for the purpose of configuring policy at…
Differentiated Services Quality of Service Policy Information Base
This document describes a Policy Information Base (PIB) for a device implementing the Differentiated Services Architecture. The provisioning classes defined here provide policy control of resources implementing the Differentiated Services Architecture. These provisioning classes can be used with other none Differentiated Services provisioning classes (defined in other PIBs) to provide for a compre…