The Trust Legal Provisions and are provided without warranty asġ. Include Simplified BSD License text as described in Section 4.e of Code Components extracted from this document must Please review these documentsĬarefully, as they describe your rights and restrictions with respect This document is subject to BCP 78 and the IETF Trust's Legal George & Pignataro Informational Ĭopyright (c) 2015 IETF Trust and the persons identified as the Information about the current status of this document, any errata,Īnd how to provide feedback on it may be obtained at Not all documentsĪpproved by the IESG are a candidate for any level of Internet Internet Engineering Steering Group (IESG). Received public review and has been approved for publication by the It represents the consensus of the IETF community. This document is a product of the Internet Engineering Task Force This document is not an Internet Standards Track specification it is Most major gaps, work is in progress to upgrade the relevant However, support for IPv6 among MPLS control-plane protocols, MPLSĪpplications, MPLS Operations, Administration, and Maintenance (OAM),Īnd MIB modules is mixed, with some protocols having major gaps. In the data plane, MPLS fully supports IPv6, and MPLS labeled packetsĬan be carried over IPv6 packets in a variety of encapsulations. (or lack thereof) in the context of IPv6-only MPLS functionality. Intended to focus on gaps in the standards defining the MPLS suite,Īnd is not intended to highlight particular vendor implementations Protocol suite in the context of IPv6 and identifies gaps that mustīe addressed in order to allow MPLS-related protocols andĪpplications to be used with IPv6-only networks. This document reviews the Multiprotocol Label Switching (MPLS) Gap Analysis for Operating IPv6-Only MPLS Networks Request for Comments: 7439 Time Warner CableĬategory: Informational C. RFC 7439: Gap Analysis for Operating IPv6-Only MPLS Networks Įrrata Exist Internet Engineering Task Force (IETF) W.
0 Comments
Leave a Reply. |