draft-ietf-mpls-tp-fault-03.txt   draft-ietf-mpls-tp-fault-04.txt 
MPLS Working Group G. Swallow, Ed. MPLS Working Group G. Swallow, Ed.
Internet-Draft Cisco Systems, Inc. Internet-Draft Cisco Systems, Inc.
Intended status: Standards Track A. Fulignoli, Ed. Intended status: Standards Track A. Fulignoli, Ed.
Expires: April 28, 2011 Ericsson Expires: October 28, 2011 Ericsson
M. Vigoureux, Ed. M. Vigoureux, Ed.
Alcatel-Lucent Alcatel-Lucent
S. Boutros S. Boutros
Cisco Systems, Inc. Cisco Systems, Inc.
D. Ward D. Ward
Juniper Networks, Inc. Juniper Networks, Inc.
October 25, 2010 April 26, 2011
MPLS Fault Management OAM MPLS Fault Management OAM
draft-ietf-mpls-tp-fault-03 draft-ietf-mpls-tp-fault-04
Abstract Abstract
This draft specifies OAM messages to indicate service disruptive This draft specifies OAM messages to indicate service disruptive
conditions for MPLS Transport Profile (MPLS-TP) Label Switched Paths conditions for MPLS Transport Profile (MPLS-TP) Label Switched Paths
(LSPs). The notification mechanism employs a generic method for a (LSPs). The notification mechanism employs a generic method for a
service disruptive condition to be communicated to a Maintenance End service disruptive condition to be communicated to a Maintenance End
Point (MEP). An MPLS Operation, Administration, and Maintenance Point (MEP). An MPLS Operation, Administration, and Maintenance
(OAM) channel is defined along with messages to communicate various (OAM) channel is defined along with messages to communicate various
types of service disruptive conditions. types of service disruptive conditions.
skipping to change at page 1, line 44 skipping to change at page 1, line 44
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 28, 2011. This Internet-Draft will expire on October 28, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 13, line 47 skipping to change at page 13, line 47
Operations, Administration, and Maintenance (OAM) in MPLS Operations, Administration, and Maintenance (OAM) in MPLS
Transport Networks", RFC 5860, May 2010. Transport Networks", RFC 5860, May 2010.
[3] Bradner, S., "Key words for use in RFCs to Indicate Requirement [3] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997. Levels", BCP 14, RFC 2119, March 1997.
[4] Bocci, M., Vigoureux, M., and S. Bryant, "MPLS Generic [4] Bocci, M., Vigoureux, M., and S. Bryant, "MPLS Generic
Associated Channel", RFC 5586, June 2009. Associated Channel", RFC 5586, June 2009.
[5] Bocci, M., Swallow, G., and E. Gray, "MPLS-TP Identifiers", [5] Bocci, M., Swallow, G., and E. Gray, "MPLS-TP Identifiers",
draft-ietf-mpls-tp-identifiers-03 (work in progress), draft-ietf-mpls-tp-identifiers-04 (work in progress),
October 2010. March 2011.
[6] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA [6] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA
Considerations Section in RFCs", BCP 26, RFC 5226, May 2008. Considerations Section in RFCs", BCP 26, RFC 5226, May 2008.
9.2. Informative References 9.2. Informative References
Authors' Addresses Authors' Addresses
George Swallow (editor) George Swallow (editor)
Cisco Systems, Inc. Cisco Systems, Inc.
 End of changes. 6 change blocks. 
7 lines changed or deleted 7 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/