|
Internet Drafts - IDs for Aug/2008
Index - Month Index of IDs
All IDs - sorted by date)
27/08/2008
| |
|
| |
| | Compressed Data within an Internet EDI Message |
| |
|
This document explains the rules and procedures for utilizing compression (RFC 3274) within an Internet EDI (Electronic Data Interchange) 'AS' message, as defined in RFCs 3335, 4130, and 4823. |
25/08/2008
| |
|
| |
| | Using IPsec between Mobile and Correspondent IPv6 Nodes |
| |
|
Mobile IPv6 uses IPsec to protect signaling between the Mobile Node and the Home Agent. This document defines how IPsec can be used between the Mobile Node and Correspondent Nodes for Home Address Option validation and protection of mobility signaling for Route Optimization. The configuration details for IPsec and IKE are also provided. |
19/08/2008
| |
|
| |
| | Cisco Systems' Private VLANs: Scalable Security in a Multi-Client Environment |
| |
|
This document describes a mechanism to achieve device isolation through the application of special Layer 2 forwarding constraints. Such mechanism allows end devices to share the same IP subnet while being Layer 2 isolated, which in turn allows network designers to employ larger subnets and so reduce the address management overhead. Some of the numerous deployment scenarios of the aforementioned mechanism (which range from data center designs to Ethernet-to-the- home basement networks) are mentioned in the following to exemplify its possible usages; however, this document is not intended to cover all such deployment scenarios nor delve into their details. |
| | The Subnetwork Encapsulation and Adaptation Layer (SEAL) |
| |
|
For the purpose of this document, subnetworks are defined as virtual topologies that span connected network regions bounded by encapsulated border nodes. These virtual topologies may span multiple IP- and/or sub-IP layer forwarding hops, and can introduce failure modes due to packet duplication and/or links with diverse Maximum Transmission Units (MTUs). This document specifies a Subnetwork Encapsulation and Adaptation Layer (SEAL) that accommodates such virtual topologies over diverse underlying link technologies. |
06/08/2008
| |
|
| |
| | Auto Issued X.509 Certificate Mechanism (AIXCM) |
| |
|
The Transport Layer Security (TLS) protocol does not support the use of client public key pairs without X.509 security certificates. This document circumvents this limitation: an end-entity has access to the public domain private key of a dummy (or "explicitly meaningless") Certification Authority (CA), and can thus freely issue an X.509 security certificate for interoperability purposes. Given these workaround requirement and solution approach, the document limits itself to the strict minimal set of standardization provisions. This supports the orderly cohabitation of auto issued certificates and normal TLS traffic relying on the full Public Key Infrastructure (PKI) model. |
04/08/2008
| |
|
| |
| | Identification of Communications Services in the Session Initiation Protocol (SIP) |
| |
|
This document considers the problem of service identification in the Session Initiation Protocol (SIP). Service identification is the process of determining the user-level use case that is driving the signaling being utilized by the user agent. This document discusses the uses of service identification, and outlines several architectural principles behind the process. It identifies perils when service identification is not done properly - including fraud, interoperability failures and stifling of innovation. |
|
