PWE3 Working Group G. Liu
Internet-Draft J. Yu
Intended status: Informational ZTE Corporation
Expires: June 15, 2013 December 12, 2012
p2mp pw protection for MPLS-TP network
draft-liu-pwe3-mpls-tp-p2mp-pw-protection-02
Abstract
The requirements of MPLS-TP in RFC 5654 include a requirement(R63)
that requires MPLS-TP MUST be possible to provide protection for
MPLS-TP data plane without any IP forwarding capability and control
plane.If applying 1:1 protection for the p2mp traffic in rfc6718 , it
must have a return path to coordinate the switch state to select the
same path to receive and send the traffic packet.As there exists the
above problem statement,This document describes a kind of protection
solution to recovery and protect the p2mp traffic under the failure
condition.
This document is a product of a joint Internet Task Force(IETF) /
International Telecommunications Union Telecommunications
Standardization Sector (ITU-T) effort to include an MPLS Transport
Profile within the IETF MPLS and PWE3 architectures to support the
capabilities and functionalities of a packet transport network as
defined by the ITU-T.
Status of this Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. This document may not be modified,
and derivative works of it may not be created, and it may not be
published except as an Internet-Draft.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on June 15, 2013.
Liu & Yu Expires June 15, 2013 [Page 1]
Internet-Draft p2mp pw protection for mpls-tp network December 2012
Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Problem statement . . . . . . . . . . . . . . . . . . . . . . . 3
2. Conventions used in this document . . . . . . . . . . . . . . . 3
3. protection solution . . . . . . . . . . . . . . . . . . . . . . 4
4. Security Considerations . . . . . . . . . . . . . . . . . . . . 7
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7
6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 7
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8
7.1. Normative References . . . . . . . . . . . . . . . . . . . 8
7.2. Informative References . . . . . . . . . . . . . . . . . . 8
7.3. URL References . . . . . . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 8
Liu & Yu Expires June 15, 2013 [Page 2]
Internet-Draft p2mp pw protection for mpls-tp network December 2012
1. Problem statement
According to MPLS-TP requirement(RFC 5654), It requires that MPLS-TP
data plane is independent of control plane and IP forwarding
capability. So it means that MPLS-TP data plane can still work
without control plane and any IP forwarding capability.It must be
essential for unidiretional path including p2p or p2mp path to set up
a return path between any leaf node and root node . So it costs more
configuration and maintenece . While this document describes a kind
of protection solution for p2mp traffic without return path, IP
forwarding capability and control plane.
2. Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
datatracker.ietf.org