Wildcard Pseudowire Type
RFC 4863, “Wildcard Pseudowire Type”, is a Proposed Standard document published in May 2007 by L. Martini, G. Swallow. The canonical text is published by the RFC Editor.
Abstract
Pseudowire signaling requires that the Pseudowire Type (PW Type) be identical in both directions. For certain applications the configuration of the PW Type is most easily accomplished by configuring this information at just one PW endpoint. In any form of LDP-based signaling, each PW endpoint must initiate the creation of a unidirectional LSP. In order to allow the initiation of these two LSPs to remain independent, a means is needed for allowing the PW endpoint (lacking a priori knowledge of the PW Type) to initiate the creation of an LSP. This document defines a Wildcard PW Type to satisfy this need. [STANDARDS-TRACK]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 4863 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 4864 Local Network Protection for IPv6
- RFC 4862 IPv6 Stateless Address Autoconfiguration
- RFC 4865 SMTP Submission Service Extension for Future Message Release
- RFC 4861 Neighbor Discovery for IP version 6
- RFC 4866 Enhanced Route Optimization for Mobile IPv6
- RFC 4860 Generic Aggregate Resource ReSerVation Protocol Reservations
- RFC 4867 RTP Payload Format and File Storage Format for the Adaptive Multi- Rate and Adaptive Multi-Rate Wideband Audio Codecs
- RFC 4859 Codepoint Registry for the Flags Field in the Resource Reservation Protocol-Traffic Engineering Session Attribute Object