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

IETF · RFC

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

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

RFC38962004-09-01

Definitions of Managed Objects for the DS3/E3 Interface Type

Definitions of Managed Objects for the DS3/E3 Interface Type

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 objects used for managing DS3 and E3 interfaces. This document is a companion to the documents that define Managed Objects for the DS0, DS1/E1/DS2/E2 and Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Interface …

RFC38952004-09-01

Definitions of Managed Objects for the DS1, E1, DS2, and E2 Interface Types

Definitions of Managed Objects for the DS1, E1, DS2, and E2 Interface Types

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 objects used for managing DS1, E1, DS2 and E2 interfaces. This document is a companion to the documents that define Managed Objects for the DS0, DS3/E3 and Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Interfac…

RFC38942004-10-01

Sieve Extension: Copying Without Side Effects

Sieve Extension: Copying Without Side Effects

The Sieve scripting language allows users to control handling and disposal of their incoming e-mail. By default, an e-mail message that is processed by a Sieve script is saved in the owner's "inbox". Actions such as "fileinto" and "redirect" cancel this default behavior. This document defines a new keyword parameter, ":copy", to be used with the Sieve "fileinto" and "redirect" actions. Adding ":co…

RFC38932004-09-01

Session Initiation Protocol (SIP) Authenticated Identity Body (AIB) Format

Session Initiation Protocol (SIP) Authenticated Identity Body (AIB) Format

RFC 3261 introduces the concept of adding an S/MIME body to a Session Initiation Protocol (SIP) request or response in order to provide reference integrity over its headers. This document provides a more specific mechanism to derive integrity and authentication properties from an 'authenticated identity body', a digitally-signed SIP message, or message fragment. A standard format for such bodies (…

RFC38922004-09-01

The Session Initiation Protocol (SIP) Referred-By Mechanism

The Session Initiation Protocol (SIP) Referred-By Mechanism

The Session Initiation Protocol (SIP) REFER method provides a mechanism where one party (the referrer) gives a second party (the referee) an arbitrary URI to reference. If that URI is a SIP URI, the referee will send a SIP request, often an INVITE, to that URI (the refer target). This document extends the REFER method, allowing the referrer to provide information about the REFER request to the ref…

RFC38912004-09-01

The Session Initiation Protocol (SIP) "Replaces" Header

The Session Initiation Protocol (SIP) "Replaces" Header

This document defines a new header for use with Session Initiation Protocol (SIP) multi-party applications and call control. The Replaces header is used to logically replace an existing SIP dialog with a new SIP dialog. This primitive can be used to enable a variety of features, for example: "Attended Transfer" and "Call Pickup". Note that the definition of these example features is non-normative.…

RFC38902004-09-01

A Transport Independent Bandwidth Modifier for the Session Description Protocol (SDP)

A Transport Independent Bandwidth Modifier for the Session Description Protocol (SDP)

This document defines a Session Description Protocol (SDP) Transport Independent Application Specific Maximum (TIAS) bandwidth modifier that does not include transport overhead; instead an additional packet rate attribute is defined. The transport independent bit-rate value together with the maximum packet rate can then be used to calculate the real bit-rate over the transport actually used. The e…

RFC38882004-09-01

Message Tracking Model and Requirements

Message Tracking Model and Requirements

Customers buying enterprise message systems often ask: Can I track the messages? Message tracking is the ability to find out the path that a particular message has taken through a messaging system and the current routing status of that message. This document provides a model of message tracking that can be used for understanding the Internet-wide message infrastructure and to further enhance those…

RFC38872004-09-01

Message Tracking Query Protocol

Message Tracking Query Protocol

Customers buying enterprise message systems often ask: Can I track the messages? Message tracking is the ability to find out the path that a particular message has taken through a messaging system and the current routing status of that message. This document describes the Message Tracking Query Protocol that is used in conjunction with extensions to the ESMTP protocol to provide a complete message…

RFC38862004-09-01

An Extensible Message Format for Message Tracking Responses

An Extensible Message Format for Message Tracking Responses

Message Tracking is expected to be used to determine the status of undelivered e-mail upon request. Tracking is used in conjunction with Delivery Status Notifications (DSN) and Message Disposition Notifications (MDN); generally, a message tracking request will be issued only when a DSN or MDN has not been received within a reasonable timeout period. This memo defines a MIME content-type for messag…

RFC38852004-09-01

SMTP Service Extension for Message Tracking

SMTP Service Extension for Message Tracking

This memo defines an extension to the SMTP service whereby a client may mark a message for future tracking. [STANDARDS-TRACK]

RFC38842004-09-01

Use of IPsec Transport Mode for Dynamic Routing

Use of IPsec Transport Mode for Dynamic Routing

IPsec can secure the links of a multihop network to protect communication between trusted components, e.g., for a secure virtual network (VN), overlay, or virtual private network (VPN). Virtual links established by IPsec tunnel mode can conflict with routing and forwarding inside VNs because IP routing depends on references to interfaces and next-hop IP addresses. The IPsec tunnel mode specificati…

RFC38832004-10-01

Detecting Inactive Neighbors over OSPF Demand Circuits (DC)

Detecting Inactive Neighbors over OSPF Demand Circuits (DC)

OSPF is a link-state intra-domain routing protocol used in IP networks. OSPF behavior over demand circuits (DC) is optimized in RFC 1793 to minimize the amount of overhead traffic. A part of the OSPF demand circuit extensions is the Hello suppression mechanism. This technique allows a demand circuit to go down when no interesting traffic is going through the link. However, it also introduces a pro…

RFC38822004-10-01

Configuring BGP to Block Denial-of-Service Attacks

Configuring BGP to Block Denial-of-Service Attacks

This document describes an operational technique that uses BGP communities to remotely trigger black-holing of a particular destination network to block denial-of-service attacks. Black-holing can be applied on a selection of routers rather than all BGP-speaking routers in the network. The document also describes a sinkhole tunnel technique using BGP communities and tunnels to pull traffic into a …

RFC38812004-10-01

Security Audit and Access Accountability Message XML Data Definitions for Healthcare Applications

Security Audit and Access Accountability Message XML Data Definitions for Healthcare Applications

This document defines the format of data to be collected and minimum set of attributes that need to be captured for security auditing in healthcare application systems. The format is defined as an XML schema, which is intended as a reference for healthcare standards developers and application designers. It consolidates several previous documents on security auditing of healthcare data. This memo p…

RFC38802004-11-01

Call Processing Language (CPL): A Language for User Control of Internet Telephony Services

Call Processing Language (CPL): A Language for User Control of Internet Telephony Services

This document defines the Call Processing Language (CPL), a language to describe and control Internet telephony services. It is designed to be implementable on either network servers or user agents. It is meant to be simple, extensible, easily edited by graphical clients, and independent of operating system or signalling protocol. It is suitable for running on a server where users may not be allow…

RFC38792004-09-01

Deprecating Site Local Addresses

Deprecating Site Local Addresses

This document describes the issues surrounding the use of IPv6 site-local unicast addresses in their original form, and formally deprecates them. This deprecation does not prevent their continued use until a replacement has been standardized and implemented. [STANDARDS-TRACK]

RFC38782004-09-01

Alarm Reporting Control Management Information Base (MIB)

Alarm Reporting Control Management Information Base (MIB)

This memo 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 controlling the reporting of alarm conditions. [STANDARDS-TRACK]

RFC38772004-09-01

Alarm Management Information Base (MIB)

Alarm Management Information Base (MIB)

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 management objects used for modelling and storing alarms. [STANDARDS-TRACK]

RFC38762004-09-01

Returning Matched Values with the Lightweight Directory Access Protocol version 3 (LDAPv3)

Returning Matched Values with the Lightweight Directory Access Protocol version 3 (LDAPv3)

This document describes a control for the Lightweight Directory Access Protocol version 3 that is used to return a subset of attribute values from an entry. Specifically, only those values that match a "values return" filter. Without support for this control, a client must retrieve all of an attribute's values and search for specific values locally. [STANDARDS-TRACK]

RFC38752004-10-01

The Common Gateway Interface (CGI) Version 1.1

The Common Gateway Interface (CGI) Version 1.1

The Common Gateway Interface (CGI) is a simple interface for running external programs, software or gateways under an information server in a platform-independent manner. Currently, the supported information servers are HTTP servers. The interface has been in use by the World-Wide Web (WWW) since 1993. This specification defines the 'current practice' parameters of the 'CGI/1.1' interface develope…

RFC38742004-09-01

A 224-bit One-way Hash Function: SHA-224

A 224-bit One-way Hash Function: SHA-224

This document specifies a 224-bit one-way hash function, called SHA-224. SHA-224 is based on SHA-256, but it uses a different initial value and the result is truncated to 224 bits. This memo provides information for the Internet community.

RFC38732004-09-01

Stream Control Transmission Protocol (SCTP) Management Information Base (MIB)

Stream Control Transmission Protocol (SCTP) Management Information Base (MIB)

The Stream Control Transmission Protocol (SCTP) is a reliable transport protocol operating on top of a connectionless packet network such as IP. It is designed to transport public switched telephone network (PSTN) signaling messages over the connectionless packet network, but is capable of broader applications. This memo defines the Management Information Base (MIB) module which describes the mini…

RFC38722004-09-01

Management Information Base for Telephony Routing over IP (TRIP)

Management Information Base for Telephony Routing over IP (TRIP)

This memo defines a portion of the Management Information Base (MIB) module for use with network management protocols in the Internet community. In particular, it describes a set of managed objects that are used to manage Telephony Routing over IP (TRIP) devices. [STANDARDS-TRACK]

RFC38712004-09-01

Operational Security Requirements for Large Internet Service Provider (ISP) IP Network Infrastructure

Operational Security Requirements for Large Internet Service Provider (ISP) IP Network Infrastructure

This document defines a list of operational security requirements for the infrastructure of large Internet Service Provider (ISP) IP networks (routers and switches). A framework is defined for specifying "profiles", which are collections of requirements applicable to certain network topology contexts (all, core-only, edge-only...). The goal is to provide network operators a clear, concise way of c…

RFC38702004-09-01

application/rdf+xml Media Type Registration

application/rdf+xml Media Type Registration

This document describes a media type (application/rdf+xml) for use with the Extensible Markup Language (XML) serialization of the Resource Description Framework (RDF). RDF is a language designed to support the Semantic Web, by facilitating resource description and data exchange on the Web. RDF provides common structures that can be used for interoperable data exchange and follows the World Wide We…

RFC38692004-08-01

IAB Concerns and Recommendations Regarding Internet Research and Evolution

IAB Concerns and Recommendations Regarding Internet Research and Evolution

This document discusses IAB concerns that ongoing research is needed to further the evolution of the Internet infrastructure, and that consistent, sufficient non-commercial funding is needed to enable such research. This memo provides information for the Internet community.

RFC38682004-10-01

Signalling Connection Control Part User Adaptation Layer (SUA)

Signalling Connection Control Part User Adaptation Layer (SUA)

This document defines a protocol for the transport of any Signalling Connection Control Part-User signalling over IP using the Stream Control Transmission Protocol. The protocol is designed to be modular and symmetric, to allow it to work in diverse architectures, such as a Signalling Gateway to IP Signalling Endpoint architecture as well as a peer-to-peer IP Signalling Endpoint architecture. [STA…

RFC38672004-11-01

Payment Application Programmers Interface (API) for v1.0 Internet Open Trading Protocol (IOTP)

Payment Application Programmers Interface (API) for v1.0 Internet Open Trading Protocol (IOTP)

The Internet Open Trading Protocol (IOTP) provides a data exchange format for trading purposes while integrating existing pure payment protocols seamlessly. This motivates the multiple layered system architecture which consists of at least some generic IOTP application core and multiple specific payment modules. This document addresses a common interface between the IOTP application core and the p…

RFC38662004-07-01

Language Tags and Ranges in the Lightweight Directory Access Protocol (LDAP)

Language Tags and Ranges in the Lightweight Directory Access Protocol (LDAP)

It is often desirable to be able to indicate the natural language associated with values held in a directory and to be able to query the directory for values which fulfill the user's language needs. This document details the use of Language Tags and Ranges in the Lightweight Directory Access Protocol (LDAP). [STANDARDS-TRACK]