|
Internet Drafts - IDs for Nov/2007
Index - Month Index of IDs
All IDs - sorted by date)
19/11/2007
| |
|
| |
| | Representing multi-value time in MANETs |
| |
|
This document describes a general and flexible TLV (type-length-value structure) for representing time using the generalized MANET packet/ message format. It defines two message and two address block TLVs for representing validity and interval times for MANET routing protocols. |
| | Password-Authenticated Diffie-Hellman Exchange (PAK) |
| |
|
This document proposes to add mutual authentication, based on human-memorizable password, to the basic unauthenticated Diffie-Hellman key exchange. The proposed algorithm is called Password-authenticated Key exchange (PAK). PAK allows two parties to authenticate themselves while performing the Diffie-Hellman exchange. The protocol is secure against all passive and active attacks. In particular, it does not allow either type of attackers to obtain any information that would enable an off-line dictionary attack on the password. The use of Diffie-Hellman exchange ensures Forward Secrecy. |
| | Presence Information Data format (PIDF) Extension for Partial Presence |
| |
|
The Presence Information Document Format (PIDF) specifies the baseline XML based format for describing presence information. One of the characteristic of the PIDF is that the document always needs to carry all presence information available for the presentity. In some environments where low bandwidth and high latency links can exist it is often beneficial to limit the amount of transported information over the network. This document introduces a new MIME type which enables transporting of either only the changed parts or the full PIDF based presence information. |
18/11/2007
| |
|
| |
| | IANA Allocations for MANET Protocols |
| |
|
This document enumerates several common IANA allocations for use by MANET protocols. The following well-known numbers are required: a UDP port number, an IP protocol number, and a link-local multicast group address. |
| | Session Initiation Protocol (SIP) Session Mobility |
| |
|
Session mobility is the transfer of media of an ongoing communication session from one device to another. This document describes the basic approaches and shows the signaling and media flow examples for providing this service using the Session Initiation Protocol (SIP). Service discovery is essential to locate targets for session transfer and is discussed using the Service Location Protocol (SLP) as an example. This document is intended as an informational document. |
16/11/2007
| |
|
| |
| | Split Multi-link Trunking (SMLT) |
| |
|
This document describes Split Multi-link Trunking (SMLT) for bridged and routed networks. SMLT enables topologies with upstream node redundancy for increased reliability of Layer 2 link aggregation subnetworks based on [IEEE 802.3ad] and router redundancy based on VRRP [RFC3768]. SMLT is an improvement over Multi-Link Trunking (MLT), a method of link aggregation that allows multiple Ethernet links to be aggregated together, and handled as a single logical trunk. MLT can be realized via many different link aggregation mechanisms. Several methods of MLT are in use today; one example is [IEEE 802.3ad]. SMLT is MLT with links of a link-aggregation group connected to ports on two different devices (e.g. SMLT client and aggregation device). Unlike MLT, at least one end of a link-aggregated group is dual-homed to two different SMLT aggregation devices. In many cases those devices act as bridges (switches) as well as L3 routers (Routing Switches). These two redundant SMLT aggregation devices can share one or more VRRP routing instances; for that SMLT-VRRP extends the VRRP functionality to an active-active router concept, where both SMLT aggregation device route traffic for a common VRRP-ID, thus load balancing traffic not only for L2 but also for L3. |
| | IP Fast Reroute using tunnels |
| |
|
This draft describes an IP fast re-route mechanism that provides backup connectivity in the event of a link or router failure. In the absence of single points of failure and asymmetric costs, the mechanism provides complete protection against any single failure. If perfect repair is not possible, the identity of all the unprotected links and routers is known in advance. This IP Fast Reroute advanced method was invented in 2002 and draft (draft-bryant-ipfrr-tunnels-00.txt) describing it was submitted to the IETF in May 2004. It was one of the first methods of achieving full repair coverage in an IP Network, and as such the draft has been widely referenced in the academic literature. The authors DO NOT propose that this IPFRR method be implemented since better IPFRR advanced method capable of achieving full repair coverage have subsequently been invented. |
| | EAP-Based Keying for IP Mobility Protocols |
| |
|
EAP [1] is increasingly used for network access authentication in various networks. Also, key generating EAP methods are being adopted in various systems for the purposes of cryptographic protection between an EAP peer and an enforcement point in the network. Key generating EAP methods produce an MSK and an EMSK in accordance with [1]. The MSK is meant for use by the EAP lower layer at the peer and the authenticator and is used differently by various lower layers. The EMSK hierarchy is defined in [2]. The EMSK hierarchy is meant to be extensible to derive keys for various usages. This document defines the key hierarchy and key derivations for using the EMSK hierarchy for keying in IP mobility protocols. |
| | Basic Forward Error Correction (FEC) Schemes |
| |
|
This document provides FEC Scheme specifications according to the RMT FEC Building Block for the Compact No-Code FEC Scheme, the Small Block, Large Block and Expandable FEC Scheme, the Small Block Systematic FEC Scheme and the Compact FEC Scheme. |
| | An Extensible Markup Language (XML) Patch Operations Framework Utilizing XML Path Language (XPath) Selectors |
| |
|
Extensible Markup Language (XML) documents are widely used as containers for the exchange and storage of arbitrary data in today's systems. In order to send changes to an XML document, an entire copy of the new version must be sent, unless there is a means of indicating only the portions that have changed. This document describes an XML patch framework utilizing XML Path language (XPath) selectors. These selector values and updated new data content constitute the basis of patch operations described in this document. In addition to them, with basic , and directives a set of patches can then be applied to update an existing XML document. |
15/11/2007
| |
|
| |
| | Binding Extensions to Web Distributed Authoring and Versioning (WebDAV) |
| |
| | draft-ietf-webdav-bind-20.txt |
| | Date: |
15/11/2007 |
| | Authors: |
Geoffrey Clemm, Jason Crawford, Julian Reschke, Jim Whitehead |
| | Working Group: |
WWW Distributed Authoring and Versioning (webdav) |
| | Formats: |
xml txt |
|
This specification defines bindings, and the BIND method for creating multiple bindings to the same resource. Creating a new binding to a resource causes at least one new URI to be mapped to that resource. Servers are required to insure the integrity of any bindings that they allow to be created. Editorial Note (To be removed by RFC Editor before publication) Please send comments to the Distributed Authoring and Versioning (WebDAV) working group at , which may be joined by sending a message with subject "subscribe" to . Discussions of the WEBDAV working group are archived at . lists all registered issues since draft 02. |
13/11/2007
| |
|
| |
| | Subscriptions to Request-Contained Resource Lists in the Session Initiation Protocol (SIP) |
| |
|
This document specifies a way to create subscription to a list of resources in SIP. This is achieved by including the list of resources in the body of a SUBSCRIBE request. Instead of having a subscriber send a SUBSCRIBE request for each resource individually, the subscriber defines the resource list, subscribes to it, and gets notifications about changes in the resources' state using a single SUBSCRIBE dialog. |
| | Conference Establishment Using Request-Contained Lists in the Session Initiation Protocol (SIP) |
| |
|
This document describes how to create a conference using SIP URI-list services. In particular, it describes a mechanism that allows a user agent client to provide a conference server with the initial list of participants using an INVITE-contained URI-list. |
| | Framework and Security Considerations for Session Initiation Protocol (SIP) Uniform Resource Identifier (URI)-List Services |
| |
|
This document describes the need for SIP URI-list services and provides requirements for their invocation. Additionaly, it defines a framework for SIP URI-List services, which includes security considerations applicable to these services. |
12/11/2007
| |
|
| |
| | Extensible Authentication Protocol (EAP) Key Management Framework |
| |
| | draft-ietf-eap-keying-22.txt |
| | Date: |
12/11/2007 |
| | Authors: |
Bernard Aboba, Daniel Simon, Pasi Eronen |
| | Working Group: |
Extensible Authentication Protocol (eap) |
| | Formats: |
txt |
|
The Extensible Authentication Protocol (EAP), defined in RFC 3748, enables extensible network access authentication. This document specifies the EAP key hierarchy and provides a framework for the transport and usage of keying material and parameters generated by EAP authentication algorithms, known as "methods". It also provides a detailed system-level security analysis, describing the conditions under which the key management guidelines described in RFC 4962 can be satisfied. |
| | The Session Initiation Protocol (SIP) P-Refused-URI-List Private-Header (P-Header) |
| |
|
This document specifies the Session Initiation Protocol (SIP) P-Refused-URI-List Private-Header (P-Header). This P-Header is used in the Open Mobile Alliance's (OMA) Pust to talk over Cellular (PoC) system. It enables URI-list servers to refuse the handling of incoming URI-list that have embedded URI-lists. This P-Header also makes it possible for the URI-list server to inform the client about the embedded URI-list that caused the rejection and the individual URIs that form such a URI-list. |
| | A Session Initiation Protocol (SIP) Media Feature Tag for MIME Application Sub-Types |
| |
|
The caller preferences specification for the Session Initiation Protocol (SIP) allows a caller to express preferences that the call be routed to a User Agent (UA) with particular capabilities. Similarly, a specification exists to allow a UA to indicate its capabilities in a registration. Amongst those capabilities are the type of media streams the agent supports, described as top-level MIME types. The 'application' MIME type is used to describe a broad range of stream types, and provides insufficient granularity as a capability. This specification allows a UA to indicate which application sub-types the agent supports. |
| | Reed-Solomon Forward Error Correction (FEC) Schemes |
| |
|
This document describes a Fully-Specified Forward Error Correction (FEC) Scheme for the Reed-Solomon FEC codes over GF(2^^m), with m in {2..16}, and its application to the reliable delivery of data objects on the packet erasure channel (i.e., a communication path where packets are either received without any corruption or discarded during transmission). This document also describes a Fully-Specified FEC Scheme for the special case of Reed-Solomon codes over GF(2^^8) when there is no encoding symbol group. Finally, in the context of the Under-Specified Small Block Systematic FEC Scheme (FEC Encoding ID 129), this document assigns an FEC Instance ID to the special case of Reed-Solomon codes over GF(2^^8). Reed-Solomon codes belong to the class of Maximum Distance Separable (MDS) codes, i.e., they enable a receiver to recover the k source symbols from any set of k received symbols. The schemes described here are compatible with the implementation from Luigi Rizzo. |
08/11/2007
| |
|
| |
| | Identity-based Encryption Architecture |
| |
|
This document describes the security architecture required to implement identity-based encryption, a public-key encryption technology that uses a user's identity as a public key. |
07/11/2007
| |
|
| |
| | Mobile Ad hoc Network Architecture |
| |
|
This document discusses Mobile Ad hoc NETworks (MANETs). It presents the initial motivation for MANET and describes unaccustomed characteristics and challenges. It also defines a MANET, other MANET entities, and MANET architectural concepts. |
| | IS-IS Generic Cryptographic Authentication |
| |
|
This document proposes an extension to IS-IS to allow the use of any cryptographic authentication algorithm in addition to the already documented authentication schemes, described in the base specification and RFC 3567. Although this document has been written specifically for using HMAC construct along with the SHA family of cryptographic hash functions, the method described in this document is generic and can be used to extend IS-IS to support any cryptographic hash function in the future. |
01/11/2007
| |
|
| |
| | Restart Signaling for Intermediate System to Intermediate System (IS-IS) |
| |
|
This document describes a mechanism for a restarting router to signal to its neighbors that it is restarting, allowing them to reestablish their adjacencies without cycling through the down state, while still correctly initiating database synchronization. This document additionally describes a mechanism for a restarting router to determine when it has achieved LSP database synchronization with its neighbors and a mechanism to optimize LSP database synchronization, while minimizing transient routing disruption when a router starts. |
| | Policy-Enabled Path Computation Framework |
| |
|
The Path Computation Element (PCE) Architecture introduces the concept of policy in the context of path computation. This document provides additional details on policy within the PCE Architecture and also provides context for the support of PCE Policy. This document introduces the use of the Policy Core Information Model (PCIM) as a framework for supporting path computation policy. This document also provides representative scenarios for the support of PCE Policy.Contents |
|
