New RFCs Sun, 05 Feb 2012 06:55:22 GMT
""Gateway-Initiated" 6rd" - Tina Tsou, Cathy Zhou, Tom Taylor, Ole Troan, Qi Chen ... 2012-02-01, rev -05: This document proposes an alternative 6rd deployment model to that of RFC 5969. The basic 6rd model allows IPv6 hosts to gain access to IPv6 networks across an IPv4 access network using 6-in-4 tunnels. 6rd requires support by a device (the 6rd-CE) on the customer site, which must also be assigned an IPv4 address. The alternative model described in this document initiates the 6-in-4 tunnels from an operator-owned gateway collocated with the operator's IPv4 network edge, rather than from customer equipment. The advantages of this approach are that it requires no modification to customer equipment and avoids assignment of IPv4 addresses to customer equipment. The latter point means less pressure on IPv4 addresses in a high-growth environment.
"A Convention for HTTP Access to JSON Resources" - Paul Bryan ... 2012-02-01, rev -01: This document codifies a convention for accessing JSON representations of resources via HTTP.
"A More Granular Web Origin Concept" - Yoav Nir ... 2012-02-01, rev -00: This document defines an HTTP header that allows to partition a single origin as defined in RFC 6454 into multiple origins, so that the same origin policy applies among them.
"ATM-Based xDSL Bonded Interfaces MIB" - Edward Beili ... 2012-02-01, rev -05: This document defines Management Information Base (MIB) module for use with network management protocols in TCP/IP based networks. This document proposes an extension to the GBOND-MIB module with a set of objects for managing ATM-based multi-pair bonded xDSL interfaces, defined in ITU-T recommendation G.998.1.
"Additional HTTP Status Codes" - Mark Nottingham, Roy Fielding ... 2012-02-01, rev -04: This document specifies additional HyperText Transfer Protocol (HTTP) status codes for a variety of common situations.
"BFD Management Information Base (MIB) extensions for MPLS and MPLS-TP Networks" - Sam Aldrin, Venkatesan Mahalingam, Kannan Sampath, Thomas Nadeau ... 2012-02-01, rev -01: This draft defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it extends the BFD Management Information Base BFD- STD-MIB and describes the managed objects for modeling Bidirectional Forwarding Detection (BFD) protocol for MPLS and MPLS-TP networks.
"Bidirectional Forwarding Detection (BFD) on Link Aggregation Group (LAG) Interfaces" - Manav Bhatia, Mach Chen, Sami Boutros, Marc Binderberger, Jeffrey Haas ... 2012-02-01, rev -03: This document proposes a mechanism to run BFD on Link Aggregation Group (LAG) interfaces. It does so by running an independent BFD async session on every LAG member link.
"CDNi Content De-duplication Optimization" - WeiYi Jin, Wei Wang, ZhenWu Hao, Yu Meng ... 2012-02-01, rev -00: Some CDNi deployments are likely to lead to content repetition in the same dCDN. This document gives the cases and then discusses the optimization approach to de-duplicate of the repeated content in CDNi network. To implement the optimization, the enhancement to CDNi metadata model and interface is required.
"Capability Exchange for Media Plane Security" - Peter Dawes ... 2012-02-01, rev -05: Negotiating the security mechanisms used between a Session Initiation Protocol (SIP) user agent and its next-hop SIP entity is already described in an RFC. This document extends negotiation of a security mechanism to the media plane by defining a new Session Initiation Protocol (SIP) header field parameter to label security mechanisms that apply to the media plane.
"Constructing protection paths for inter-AS, inter-sub-AS P2MP TE-LSPs" - Balaji Venkat, Gaurav Raina ... 2012-02-01, rev -00: Constructing primary and backup explicit path Point-to-Multipoint Label Switched Paths is important from the point of view of providing protection switching in case the primary fails.
"Data Center Mobility based on BGP/MPLS, IP Routing and NHRP" - Rahul Aggarwal, Yakov Rekhter, Wim Henderickx, Ravi Shekhar ... 2012-02-01, rev -02: This document describes a set of network-based solutions for seamless Virtual Machine mobility in the data center. These solutions provide a toolkit which is based on IP routing, BGP/MPLS E-VPNs, BGP/MPLS IP VPNs, and NHRP.
"Definitions of Managed Objects for 6rd" - Lei Cai, Jacni Qin, Shishio Tsuchiya ... 2012-02-01, rev -01: This document defines a portion of the Management Information Base (MIB) for use with network management protocols. In particular, it defines objects for managing 6rd devices.
"Diameter Network Access Server Application" - Glen Zorn ... 2012-02-01, rev -07: This document describes the Diameter protocol application used for Authentication, Authorization, and Accounting (AAA) services in the Network Access Server (NAS) environment; it obsoletes RFC 4005. When combined with the Diameter Base protocol, Transport Profile, and Extensible Authentication Protocol specifications, this application specification satisfies typical network access services requirements.
"Distributed Mobile IPv6" - Behcet Sarikaya ... 2012-02-01, rev -00: As networks are moving towards flat architectures, a distributed approach is needed to Mobile IPv6. This document defines a distributed mobility management protocol. Protocol is based on Mobile IPv6 and its extensions for multiple care of address registration, flow mobility and dual stack mobile IPv6 with minimum extensions. Control and data plane separation is achieved by separating Home Agent functionalities into the control and data planes.
"Distributed Mobility Anchoring" - Pierrick Seite, Philippe Bertin ... 2012-02-01, rev -00: Most existing IP mobility solutions are derived from Mobile IP principles where a given mobility anchor maintains Mobile Nodes (MNs) binding up-to-date. Data traffic is then encapsulated between the mobility anchor and the MN or its Access Router. These approaches are usually implemented on a centralised architectures where both MN context and traffic encapsulation need to be processed at a central network entity, i.e. the mobility anchor. However, one of the trend in mobile network evolution is to "flatten" mobility architecture by confining mobility support in the access network, e.g. at the access routers level, keeping the rest of the network unaware of the mobility events and their support. This document discusses the deployment of a Proxy Mobile IP approach in such a flat architecture. The solution allows to dynamically distribute mobility functions among access routers. The goal is also to dynamically adapt the mobility support of the MN's needs by applying traffic redirection only to MNs' flows when an IP handover occurs.
"Extensible XDR Discriminated Union Primitive Type" - Thomas Keiser ... 2012-02-01, rev -05: AFS-3 relies upon XDR to carry Rx RPC call payloads. XDR discriminated unions are ill-suited to cases where the protocol needs to evolve without inventing new RPCs, i.e., unknown discriminant values cause the entire XDR payload to fail the decoding step. While this can be circumvented through the use of opaque payloads (and recursive XDR invocations), such solutions are inelegant and difficult to implement. This memo defines a new XDR primitive type, "ext-union", which is derived from the XDR discriminated union primitive type, but with two key variations: 1) each leg contains a length field, and 2) no default leg is supported.
"Flow Aggregation for the IP Flow Information Export (IPFIX) Protocol" - Brian Trammell, Arno Wagner, Benoit Claise ... 2012-02-01, rev -01: This document describes the export of aggregated Flow information using IPFIX. An Aggregated Flow is essentially an IPFIX Flow representing packets from multiple Original Flows sharing some set of common properties. The document describes Aggregated Flow export within the framework of IPFIX Mediators and defines an interoperable, implementation-independent method for Aggregated Flow export.
"Framework for Telepresence Multi-Streams" - Allyn Romanow, Mark Duckworth, Andrew Pepperell, Brian Baldino ... 2012-02-01, rev -03: This memo offers a framework for a protocol that enables devices in a telepresence conference to interoperate by specifying the relationships between multiple media streams.
"Hiding Transit-only Networks in OSPF" - Yi Yang, Alvaro Retana, Abhay Roy ... 2012-02-01, rev -02: A transit-only network is defined as a network connecting routers only. In OSPF, transit-only networks are usually configured with routable IP addresses, which are advertised in Link State Advertisements (LSAs) but not needed for data traffic. In addition, remote attacks can be launched against routers by sending packets to these transit-only networks. This document presents a mechanism to hide transit-only networks to speed up network convergence and minimize remote attack vulnerability.
"IPv4 Traffic Offload Selector Option for Proxy Mobile IPv6" - Sri Gundavelli, Xingyue Zhou, Jouni Korhonen, Rajeev Koodli ... 2012-02-01, rev -03: This specification defines a mechanism and a related mobility option for carrying IPv4 Offload traffic selectors between a mobile access gateway and a local mobility anchor in a Proxy Mobile IPv6 domain. Based on the received offload flow selectors from the local mobility anchor, a mobile access gateway can enable offload traffic rule on the selected IPv4 flows.
"Implementation Advice for IPv6 Router Advertisement Guard (RA-Guard)" - Fernando Gont ... 2012-02-01, rev -01: The IPv6 Router Advertisement Guard (RA-Guard) mechanism is commonly employed to mitigate attack vectors based on forged ICMPv6 Router Advertisement messages. Many existing IPv6 deployments rely on RA- Guard as the first line of defense against the aforementioned attack vectors. However, some implementations of RA-Guard have been found to be prone to circumvention by employing IPv6 Extension Headers. This document describes the evasion techniques that affect the aforementioned implementations, and provides advice on the implementation of RA-Guard, such that the RA-Guard evasion vectors are eliminated.
"Lightweight 4over6: An Extension to DS-Lite Architecture" - Yong Cui, Qiong Sun, Yiu Lee, Tina Tsou (Ting ZOU), Mohamed Boucadair ... 2012-02-01, rev -05: This document specifies an extension to DS-Lite called lightweight 4over6. This mechanism moves the translation function from the tunnel concentrator (AFTR) to initiators (B4s), and hence reduces the mapping scale on the concentrator to per-subscriber level. To delegate the NAT function to the initiators, port-restricted IPv4 addresses are allocated to the initiators.
"Media Type Specifications and Registration Procedures" - Ned Freed, John Klensin, Tony Hansen ... 2012-02-01, rev -01: This document defines procedures for the specification and registration of media types for use in HTTP, MIME and other Internet protocols.
"Multi-Stream Media Conferencing" - Magnus Westerlund, Bo Burman ... 2012-02-01, rev -00: This memo describes a multimedia multi-party conferencing architecture based on use of multiple Real-Time Transport Protocol (RTP) streams.
"Multicast Support for 4rd" - Behcet Sarikaya ... 2012-02-01, rev -01: This memo specifies 4rd technology's multicast component so that IPv4 hosts can receive multicast data from IPv4 servers over an IPv6 network. In 4rd Translation Multicast solution, IGMP messages are translated into MLD messages at the CE router which is IGMP/MLD Proxy and sent to the network in IPv6. 4rd Border Relay does the reverse translation and joins IPv4 multicast group for 4rd hosts. Border Relay as multicast router receives IPv4 multicast data and translates the packet into IPv6 multicast data using 4rd-U and sends downstream on the multicast tree. Member CEs receive multicast data, translate it back to IPv4 and transmit to the hosts. In AMT based solution, AMT Gateway at the 4rd Customer Edge router uses AMT protocol to establish a tunnel interface with AMT Relay at the 4rd Border Relay and this tunnel is used to exchange IGMP messages to establish multicast state at AMT Relay so that AMT Relay can tunnel IPv4 multicast data to IPv4 hosts connected to AMT Gateway.
"Multicast Transition Overview" - Hitoshi Asaeda, Marshall Eubanks, Tina Tsou, Stig Venaas ... 2012-02-01, rev -01: The transition from IPv4 to IPv6 raises issues for multicast signaling and multicast content distribution. This memo describes the problem and briefly surveys the solution space.
"Multicast in VPLS" - Rahul Aggarwal, Yakov Rekhter, Yuji Kamite, Luyuan Fang ... 2012-02-01, rev -10: This document describes a solution for overcoming a subset of the limitations of existing VPLS multicast solutions. It describes procedures for VPLS multicast that utilize multicast trees in the sevice provider (SP) network. One such multicast tree can be shared between multiple VPLS instances. Procedures by which a single multicast tree in the SP network can be used to carry traffic belonging only to a specified set of one or more IP multicast streams from one or more VPLSes are also described.
"Operational Neighbor Discovery Problems" - Igor Gashinsky, Joel Jaeggli, Warren Kumari ... 2012-02-01, rev -04: In IPv4, subnets are generally small, made just large enough to cover the actual number of machines on the subnet. In contrast, the default IPv6 subnet size is a /64, a number so large it covers trillions of addresses, the overwhelming number of which will be unassigned. Consequently, simplistic implementations of Neighbor Discovery (ND) can be vulnerable to deliberate or accidental denial of service, whereby they attempt to perform address resolution for large numbers of unassigned addresses. Such denial of attacks can be launched intentionally (by an attacker), or result from legitimate operational tools or accident conditions. As a result of these vulnerabilities, new devices may not be able to "join" a network, it may be impossible to establish new IPv6 flows, and existing IPv6 transported flows may be interrupted.
"Processing of IPv6 "atomic" fragments" - Fernando Gont ... 2012-02-01, rev -00: The IPv6 specification allows packets to contain a Fragment Header without the packet being actually fragmented into multiple pieces. Such packets typically result from hosts that have received an ICMPv6 "Packet Too Big" error message that advertises a "Next-Hop MTU" smaller than 1280 bytes, and are currently processed by some implementations as "fragmented traffic". Thus, by forging ICMPv6 "Packet Too Big" error messages an attacker can cause hosts to employ "atomic fragments", and then launch any fragmentation-based attacks against such traffic. This document discusses the generation of the aforementioned "atomic fragments", the corresponding security implications, and formally updates RFC 2460 and RFC 5722 such that fragmentation-based attack vectors against traffic employing "atomic fragments" are completely eliminated.
"Protocol Independent Multicast ECMP Redirect" - Yiqun Cai, Liming Wei, Heidi Ou, Vishal Arya, Sunil Jethwani ... 2012-02-01, rev -02: A PIM router uses the RPF procedure to select an upstream interface and router to build forwarding state. When there are equal cost multiple paths (ECMP), existing implementations often use hash algorithms to select a path. Such algorithms do not allow the spread of traffic among the ECMPs according to administrative metrics. This usually leads to inefficient or ineffective use of network resources. This document introduces the ECMP Redirect, a mechanism to improve the RPF procedure over ECMPs. It allows ECMP path selection to be based on administratively selected metrics, such as data transmission delays, path preferences and routing metrics.
"RTCP XR Blocks for QoE Metric Reporting" - Geoff Hunt, Alan Clark, Wenson Wu, Roland Schott, Glen Zorn ... 2012-02-01, rev -00: This document defines an RTCP XR Report Block and associated SDP parameters that allow the reporting of QoE metrics for use in a range of RTP applications.
"RTCP XR Blocks for Synchronization Delay and Offset Metrics Reporting" - Hitoshi Asaeda, Rachel Huang, Wenson Wu ... 2012-02-01, rev -03: This document defines an RTCP XR Report Block and associated SDP parameters that allow the reporting of synchronization delay and offset metrics for use in a range of RTP applications.
"RTP Payload Format for SMPTE 336M Encoded Data" - Jeff Downs Downs, J. Arbeiter ... 2012-02-01, rev -03: This document specifies the payload format for packetization of KLV (Key-Length-Value) Encoded Data, as defined by the Society of Motion Picture and Television Engineers (SMPTE) in SMPTE 336M, into the Real-time Transport Protocol (RTP).
"Real-time Transport Control Protocol (RTCP) Extension Report (XR) for Run Length Encoding of Discarded Packets" - Joerg Ott, Varun Singh, Igor Curcio ... 2012-02-01, rev -03: The Real-time Transport Control Protocol (RTCP) is used in conjunction with the Real-time Transport Protocol (RTP) in to provide a variety of short-term and long-term reception statistics. The available reporting may include aggregate information across longer periods of time as well as individual packet reporting. This document specifies a per-packet report metric capturing individual packets discarded from the jitter buffer after successful reception.
"Requirements for Labeled NFS" - David Quigley, James Morris, Jarrett Lu, Stephen Smalley, Thomas Haynes ... 2012-02-01, rev -00: This Internet-Draft outlines high-level requirements for the integration of flexible Mandatory Access Control (MAC) functionality into NFSv4.2. It describes the level of protections that should be provided over protocol components and the basic structure of the proposed system. It also gives a brief explanation of what kinds of protections MAC systems offer.
"SPF Authentication Failure Reporting using the Abuse Report Format" - Scott Kitterman ... 2012-02-01, rev -05: This memo presents extensions to the Abuse Reporting Format (ARF), and Sender Policy Framework (SPF) specifications to allow for detailed reporting of message authentication failures in an on-demand fashion.
"The Hypertext Transfer Protocol (HTTP) Status Code 308 (Permanent Redirect)" - Julian Reschke ... 2012-02-01, rev -03: This document specifies the additional HyperText Transfer Protocol (HTTP) Status Code 308 (Permanent Redirect).
"The RPKI/Router Protocol" - Randy Bush, Rob Austein ... 2012-02-01, rev -26: In order to verifiably validate the origin ASs of BGP announcements, routers need a simple but reliable mechanism to receive RPKI [I-D.ietf-sidr-arch] prefix origin data from a trusted cache. This document describes a protocol to deliver validated prefix origin data to routers.
"The application/zlib and application/gzip media types" - John Levine ... 2012-02-01, rev -00: This document defines the 'application/gzip' and 'application/zlib' media types for compressed data using the gzip and zlib compression formats.
"Threat Model for BGP Path Security" - Stephen Kent, Andrew Chi ... 2012-02-01, rev -01: This document describes a threat model for BGP path security (BGPSEC). It assumes the context established by the SIDR WG charter, as of April 19, 2011. The charter established two goals for the SIDR work:
"Tiny Fragments in IPv6" - Vishwas Manral ... 2012-02-01, rev -00: IPv6 fragmentation allows fragments to be sent only by the source of a packet. The Fragment header is used by an IPv6 source to send a packet larger than would fit in the path MTU to its destination.
"Traversal Using Relays around NAT (TURN) Uniform Resource Identifiers" - Marc Petit-Huguenin, Suhas Nandakumar, Gonzalo Salgueiro, Paul Jones ... 2012-02-01, rev -00: This document specifies the syntax of Uniform Resource Identifier (URI) schemes for the Traversal Using Relays around NAT (TURN) protocol. It defines two URI schemes that can be used to provision the configuration values needed by the resolution mechanism defined in [RFC5928].
"Update to MIME regarding Charset Parameter Handling in Textual Media Types" - Alexey Melnikov, Julian Reschke ... 2012-02-01, rev -00: This document changes RFC 2046 rules regarding default charset parameter values for text/* media types to better align with common usage by existing clients and servers.
"User-Managed Access (UMA) Core Protocol" - Thomas Hardjono ... 2012-02-01, rev -03: This specification defines the User-Managed Access (UMA) core protocol. This protocol provides a method for users to control access to their protected resources, residing on any number of host sites, through an authorization manager that governs access decisions based on user policy.
"Using Secure DNS to Associate Certificates with Domain Names For TLS" - Paul Hoffman, Jakob Schlyter ... 2012-02-01, rev -15: TLS and DTLS use PKIX certificates for authenticating the server. Users want their applications to verify that the certificate provided by the TLS server is in fact associated with the domain name they expect. TLSA provides bindings of keys to domains that are asserted not by external entities, but by the entities that operate the DNS. This document describes how to use secure DNS to associate the TLS server's certificate with the intended domain name.
"WebSocket Per-frame DEFLATE Extension" - Takeshi Yoshino ... 2012-02-01, rev -05: This specification defines a per-frame DEFLATE compression extension for the WebSocket Protocol. This extension compresses the "Application data" part of WebSocket data frames using DEFLATE.
"Wireline Incremental IPv6" - Victor Kuarsingh, Lee Howard ... 2012-02-01, rev -01: Operators worldwide are in various stages of preparing for, or deploying IPv6 into their networks. The operators often face difficult challenges related to both IPv6 introduction along with those related to IPv4 run out. Operators will need to meet the simultaneous needs of IPv6 connectivity and continue support for IPv4 connectivity for legacy devices with a depleting supply of IPv4 addresses. The IPv6 transition will take most networks from an IPv4- only environment to an IPv6 focused environment with long period of dual stack operation varying by operator. This document helps provide a framework for Wireline providers who are faced with the challenges of introducing IPv6 along meeting the legacy needs of IPv4 connectivity utilizing well defined and commercially available IPv6 transition technologies.
"xDSL multi-pair bonding (G.Bond) MIB" - Edward Beili, Moti Morgenstern ... 2012-02-01, rev -08: This document defines Management Information Base (MIB) module for use with network management protocols in TCP/IP-based internets. This document proposes an extension to the Interfaces Group MIB with a set of common objects for managing multi-pair bonded Digital Subscriber Line (xDSL) interfaces, defined in ITU-T recommendations G.998.1, G.998.2 and G.998.3. The MIB modules specific to each bonding technology are defined in GBOND-ATM-MIB, GBOND-ETH-MIB and GBOND-TDIM-MIB respectively.
"A CoAP REST API for XMPP Publish-Subscribe" - Klaus Hartke ... 2012-01-31, rev -00: The REST API defined in this document enables Constrained Application Protocol (CoAP) clients to interact with Extensible Messaging Protocol (XMPP) Publish-Subscribe services by delegating the task of creating, retrieving, updating and deleting pubsub items and nodes to a CoAP/XMPP proxy.
"Carrying PIM-SM in ASM mode Trees over P2MP mLDP LSPs" - Yakov Rekhter, Rahul Aggarwal ... 2012-01-31, rev -00: When IP multicast trees created by PIM-SM in ASM mode need to pass through an MPLS domain, it may be desirable to map such trees to Point-to-Multipoint Label Switched Paths. This document describes how to accomplish this in the case where such Point-to-Multipoint Label Switches Paths are established using mLDP.
"CoRE Interfaces" - Zach Shelby ... 2012-01-31, rev -01: This document defines well-known REST interface descriptions for Batch, Sensor, Parameter and Actuator types for use in contrained web servers using the CoRE Link Format. A short reference is provided for each type that can be efficiently included in the interface description attribute of the CoRE Link Format. These descriptions are intended to be for general use in resource designs or for inclusion in more specific interface profiles.
"Creation and Use of Email Feedback Reports: An Applicability Statement for the Abuse Reporting Format (ARF)" - J.D. Falk, M. Kucherawy ... 2012-01-31, rev -05: RFC 5965 defines an extensible, machine-readable format intended for mail operators to report feedback about received email to other parties. This document describes common methods for utilizing this format for abuse reporting. Mailbox Providers of any size, mail sending entities, and end users can use these methods as a basis to create procedures that best suit them.
"Definition of Managed Objects for Performance Reporting" - Robert Cole, Joseph Macker, Andy Bierman ... 2012-01-31, rev -02: 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 for configuring autonomous report generation on any device that supports MIBs containing counter and gauge objects for performance monitoring. This allows a management station to instruct a device to build off-line reports to be collected asynchronously by the management station. Further, this REPORT-SAMPLED-MIB can be configured in a proxy configuration where the report generation is performed on a device in close network proximity to the device containing the referenced counter objects. Hence, this capability allows network operators to reduce the SNMP polling traffic burden on Mobile Ad-Hoc and Disruption Tolerant Networks which is typical of SNMP performance management applications.
"Definitions of Managed Objects for 4rd" - Yu Fu, Sheng Jiang, Jiang Dong, Peng Wu ... 2012-01-31, rev -00: This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines managed objects for 4rd.
"Extensions to DKIM for Failure Reporting" - Murray Kucherawy ... 2012-01-31, rev -08: This memo presents extensions to the DomainKeys Identified Mail (DKIM) specification to allow for detailed reporting of message authentication failures in an on-demand fashion.
"Extranet in BGP Multicast VPN (MVPN)" - Rahul Aggarwal, Yakov Rekhter, Thomas Morin, Wim Henderickx, Praveen Muley, Ray Qiu ... 2012-01-31, rev -07: This document describes clarifications and extensions to the procedures in [BGP-MVPN] for supporting extranets. The procedures specified in this document assume that BGP is used for transmission of MVPN customers' multicast routing information within the service provider(s) infrastructure.
"IODEF-extension to support structured cybersecurity information" - Takeshi Takahashi, Kent Landfield, Thomas Millar, Youki Kadobayashi ... 2012-01-31, rev -02: This document extends the Incident Object Description Exchange Format (IODEF) defined in RFC 5070 [RFC5070] to facilitate enriched cybersecurity information exchange among cybersecurity entities by embedding structured information formatted by specifications, including CAPEC[TM] [CAPEC], CEE[TM] [CEE], CPE[TM] [CPE], CVE(R) [CVE], CVRF [CVRF], CVSS [CVSS], CWE[TM] [CWE], CWSS[TM] [CWSS], OCIL [OCIL], OVAL(R) [OVAL], and XCCDF [XCCDF].
"JSON Responses to RESTful URL Queries for RIRs" - Andrew Newton, Kaveh Ranjbar, Arturo Servin ... 2012-01-31, rev -00: This document describes responses in the JSON format to the RESTful queries described in draft-newton-et-al-weirds-rir-query.
"Label Switched Path (LSP) Data Path Delay Metrics in Generalized MPLS/ MPLS-TE Networks" - Weiqiang Sun, Guoying Zhang ... 2012-01-31, rev -05: When setting up a label switched path (LSP) in Generalized MPLS and MPLS/TE networks, the completion of the signaling process does not necessarily mean that the cross connection along the LSP have been programmed accordingly and in a timely manner. Meanwhile, the completion of signaling process may be used by applications as indication that data path has become usable. The existence of this delay and the possible failure of cross connection programming, if not properly treated, will result in data loss or even application failure. Characterization of this performance can thus help designers to improve the application model and to build more robust applications. This document defines a series of performance metrics to evaluate the availability of data path in the signaling process.
"MANET Cryptographical Signature TLV Definition" - Ulrich Herberg, Thomas Clausen ... 2012-01-31, rev -08: This document describes general and flexible TLVs (type-length-value structure) for representing cryptographic signatures as well as timestamps, using the generalized MANET packet/message format defined in RFC 5444. It defines two Packet TLVs, two Message TLVs, and two Address Block TLVs, for affixing cryptographic signatures and timestamps to a packet, message and address, respectively.