|
Internet Drafts - IDs for Feb/2008
Index - Month Index of IDs
All IDs - sorted by date)
25/02/2008
| |
|
| |
| | RTP payload format for mU-law EMbedded Codec for Low-delay IP communication (UEMCLIP) speech codec |
| |
|
This document describes the RTP payload format of a mU-law EMbedded Coder for Low-delay IP communication (UEMCLIP), an enhanced speech codec of ITU-T G.711. The bitstream has a scalable structure with an embedded u-law bitstream, also known as PCMU, thus providing a handy transcoding operation between narrowband and wideband speech. |
| | Benchmarking Methodology for Link-State IGP Data Plane Route Convergence |
| |
|
This document describes the methodology for benchmarking Interior Gateway Protocol (IGP) Route Convergence. The methodology is to be used for benchmarking IGP convergence time through externally observable (black box) data plane measurements. The methodology can be applied to any link-state IGP, such as ISIS and OSPF. Link-State IGP Data Plane Route Convergence |
| | Terminology for Benchmarking Link-State IGP Data Plane Route Convergence |
| |
|
This document describes the terminology for benchmarking Interior Gateway Protocol (IGP) Route Convergence. The terminology is to be used for benchmarking IGP convergence time through externally observable (black box) data plane measurements. The terminology can be applied to any link-state IGP, such as ISIS and OSPF. Link-State IGP Data Plane Route Convergence |
| | Considerations for Benchmarking Link-State IGP Data Plane Route Convergence |
| |
|
This document discusses considerations for benchmarking Interior Gateway Protocol (IGP) Route Convergence for any link-state IGP, such as Intermediate System-Intermediate System (ISIS) and Open-Shorted Path first (OSPF). A companion methodology document is to be used for benchmarking IGP convergence time through externally observable (black box) data plane measurements. A companion |
| | IODEF/RID over SOAP |
| |
|
Documents intended to be shared among multiple constituencies must share a common format and transport mechanism. The Incident Object Description Exchange Format (IODEF) defines a common XML format for document exchange. This draft outlines the SOAP wrapper for all IODEF documents and extensions to facilitate an interoperable and secure communication of documents. The SOAP wrapper allows for flexibility in the selection of a transport protocol. The transport protocols will be provided through existing standards and SOAP binding, such as SOAP over HTTP/TLS and SOAP over BEEP. |
24/02/2008
| |
|
| |
| | Internet Mail Architecture |
| |
|
Over its thirty-five year history Internet Mail has undergone significant changes in scale and complexity, as it has become a global infrastructure service. The first standardized architecture for networked email specified little more than a simple split between the user world and the transmission world. Core aspects of the service, such as the styles of mailbox address and basic message format, have remained remarkably constant. However today's Internet Mail is distinguished by many independent operators, many different components for providing service to users and many others for performing message transfer. Public discussion of the service often lacks common terminology and a common frame of reference for these components and their activities. Having a common reference model and terminology facilitates discussion about problems with the service, changes in policy, or enhancement to the service's functionality. This document offers an enhanced Internet Mail architecture that targets description of the existing service, in order to facilitate clearer and more efficient technical, operations and policy discussions about email. |
| | A Hitchhiker's Guide to the Session Initiation Protocol (SIP) |
| |
|
The Session Initiation Protocol (SIP) is the subject of numerous specifications that have been produced by the IETF. It can be difficult to locate the right document, or even to determine the set of Request for Comments (RFC) about SIP. This specification serves as a guide to the SIP RFC series. It lists the specifications under the SIP umbrella, briefly summarizes each, and groups them into categories. |
23/02/2008
| |
|
| |
| | The use of the SIPS URI Scheme in the Session Initiation Protocol (SIP) |
| |
|
This document provides clarifications and guidelines concerning the use of the SIPS URI scheme in the Session Initiation Protocol (SIP). It also makes normative changes to SIP. This document also provides a discussion of possible future steps in specification. |
21/02/2008
| |
|
| |
| | NFS RDMA Problem Statement |
| |
|
This draft addresses enabling the use of Remote Direct Memory Access (RDMA) by the Network File System (NFS) protocols. NFS implementations historically incur significant overhead due to data copies on end-host systems, as well as other processing overhead. The potential benefits of RDMA to these implementations are explored, and the reasons why RDMA is especially well-suited to NFS and network file protocols in general are evaluated. |
20/02/2008
| |
|
| |
| | Media Gateway Control Protocol Fax Package |
| |
|
This document defines a Media Gateway Control Protocol (MGCP) package to support fax calls. The package allows for fax calls to be supported in two different ways. The first one utilizes ITU-T Recommendation T.38 for fax relay under the control of the Call Agent. The second one lets the gateway decide upon a method for fax transmission as well as handle the details of the fax call without Call Agent involvement. |
19/02/2008
| |
|
| |
| | Sieve Notification Mechanism: xmpp |
| |
|
This document describes a profile of the Sieve extension for notifications, to allow notifications to be sent over the Extensible Messaging and Presence Protocol (XMPP), also known as Jabber. |
16/02/2008
| |
|
| |
| | RTP Payload Format for the Speex Codec |
| |
| | draft-ietf-avt-rtp-speex-05.txt |
| | Date: |
16/02/2008 |
| | Authors: |
Greg Herlein, Jean-Marc Valin, Alfred Heggestad, Aymeric Moizard |
| | Working Group: |
Audio/Video Transport (avt) |
| | Formats: |
txt |
|
Speex is an open-source voice codec suitable for use in Voice over IP (VoIP) type applications. This document describes the payload format for Speex generated bit streams within an RTP packet. Also included here are the necessary details for the use of Speex with the Session Description Protocol (SDP).Editors Note All references to RFC XXXX are to be replaced by references to the RFC number of this memo, when published. |
14/02/2008
| |
|
| |
| | Shim6: Level 3 Multihoming Shim Protocol for IPv6 |
| |
| | draft-ietf-shim6-proto-10.txt |
| | Date: |
14/02/2008 |
| | Authors: |
Erik Nordmark, Marcelo Bagnulo |
| | Working Group: |
Site Multihoming by IPv6 Intermediation (shim6) |
| | Formats: |
txt |
|
This document defines the Shim6 protocol, a layer 3 shim for providing locator agility below the transport protocols, so that multihoming can be provided for IPv6 with failover and load sharing properties, without assuming that a multihomed site will have a provider independent IPv6 address prefix which is announced in the global IPv6 routing table. The hosts in a site which has multiple provider allocated IPv6 address prefixes, will use the Shim6 protocol specified in this document to setup state with peer hosts, so that the state can later be used to failover to a different locator pair, should the original one stop working. |
13/02/2008
| |
|
| |
| | Dual Stack Mobile IPv4 |
| |
|
This specification provides IPv6 extensions to the Mobile IPv4 protocol. The extensions allow a dual stack node to use IPv4 and IPv6 home addresses as well as to move between IPv4 and dual stack network infrastructures. |
| | A Framework for Session Initiation Protocol User Agent Profile Delivery |
| |
|
This document specifies a framework to enable configuration of Session Initiation Protocol (SIP) User Agents in SIP deployments. The framework provides a means to deliver profile data that User Agents need to be functional, automatically and with minimal or no User and Administrative intervention. The framework describes how SIP User Agents can discover sources, request profiles and receive notifications related to profile modifications. As part of this framework, a new SIP event package is defined for notification of profile changes. The framework provides minimal data retrieval options to ensure interoperability. The framework does not include specification of the profile data within its scope. |
12/02/2008
| |
|
| |
| | SPEERMINT Terminology |
| |
|
This document defines the terminology that is to be used in describing Session PEERing for Multimedia INTerconnect (SPEERMINT). |
07/02/2008
| |
|
| |
| | NSLP for Quality-of-Service Signaling |
| |
|
This specification describes the NSIS Signaling Layer Protocol (NSLP) for signaling QoS reservations in the Internet. It is in accordance with the framework and requirements developed in NSIS. Together with GIST, it provides functionality similar to RSVP and extends it. The QoS NSLP is independent of the underlying QoS specification or architecture and provides support for different reservation models. It is simplified by the elimination of support for multicast flows. This specification explains the overall protocol approach, design decisions made and provides examples. It specifies object, message formats and processing rules. |
06/02/2008
| |
|
| |
| | Internet Calendaring and Scheduling Core Object Specification (iCalendar) |
| |
|
This document defines the iCalendar data format for representing and exchanging calendaring and scheduling information such as events, to- dos, journal entries and free/busy information, independent of any particular calendar service or protocol. |
|
