draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext-03.txt   draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext-04.txt 
CCAMP Working Group E. Bellagamba, Ed. CCAMP Working Group E. Bellagamba, Ed.
Internet-Draft L. Andersson, Ed. Internet-Draft L. Andersson, Ed.
Intended status: Standards Track Ericsson Intended status: Standards Track Ericsson
Expires: January 10, 2011 P. Skoldstrom, Ed. Expires: July 13, 2011 P. Skoldstrom, Ed.
Acreo AB Acreo AB
D. Ward D. Ward
Juniper Juniper
July 9, 2010 A. Takacs
Ericsson
January 9, 2011
Configuration of pro-active MPLS-TP Operations, Administration, and Configuration of pro-active MPLS-TP Operations, Administration, and
Maintenance (OAM) Functions Using RSVP-TE Maintenance (OAM) Functions Using RSVP-TE
draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext-03 draft-ietf-ccamp-rsvp-te-mpls-tp-oam-ext-04
Abstract Abstract
This specification describes the configuration of pro-active MPLS-TP This specification describes the configuration of pro-active MPLS-TP
Operations, Administration, and Maintenance (OAM) Functions for a Operations, Administration, and Maintenance (OAM) Functions for a
given LSP using a common set of TLVs that can be carried on RSVP-TE given LSP using a common set of TLVs that can be carried on RSVP-TE
protocol. protocol.
Status of this Memo Status of this Memo
skipping to change at page 1, line 38 skipping to change at page 1, line 40
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 January 10, 2011. This Internet-Draft will expire on July 13, 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 3, line 32 skipping to change at page 3, line 32
provides low- overhead, short-duration detection of failures in the provides low- overhead, short-duration detection of failures in the
path between two forwarding engines, including the interfaces, data path between two forwarding engines, including the interfaces, data
link(s), and to the extent possible the forwarding engines link(s), and to the extent possible the forwarding engines
themselves. BFD can be used to track the liveliness and detect data themselves. BFD can be used to track the liveliness and detect data
plane failures of MPLS-TP point-to-point and might also be extended plane failures of MPLS-TP point-to-point and might also be extended
to p2mp connections. to p2mp connections.
MPLS Transport Profile (MPLS-TP) describes a profile of MPLS that MPLS Transport Profile (MPLS-TP) describes a profile of MPLS that
enables operational models typical in transport networks, while enables operational models typical in transport networks, while
providing additional OAM, survivability and other maintenance providing additional OAM, survivability and other maintenance
functions not currently supported by MPLS. [MPLS-TP-OAM-REQ] defines functions not currently supported by MPLS. [RFC5860] defines the
the requirements for the OAM functionality of MPLS-TP. requirements for the OAM functionality of MPLS-TP.
BFD has been chosen to be the basis of pro-active MPLS-TP OAM BFD has been chosen to be the basis of pro-active MPLS-TP OAM
functions. MPLS-TP OAM extensions for transport applications, for functions. MPLS-TP OAM extensions for transport applications, for
which this document specifies the configuration, are specified in which this document specifies the configuration, are specified in
[BFD-CCCV], [MPLS-PM], and [MPLS-FMS]. [BFD-CCCV], [MPLS-PM], and [MPLS-FMS].
1.1. Contributing Authors 1.1. Contributing Authors
This document is the result of a large team of authors and This document is the result of a large team of authors and
contributors. The following is a list of the co-authors: contributors. The following is a list of the co-authors:
John Drake John Drake
Attila Takacs
Benoit Tremblay Benoit Tremblay
1.2. Requirements Language 1.2. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
1.3. Overview of BFD OAM operation 1.3. Overview of BFD OAM operation
skipping to change at page 4, line 46 skipping to change at page 4, line 46
The ability of each system to control the BFD packet transmission The ability of each system to control the BFD packet transmission
rate in both directions provides a mechanism for congestion control, rate in both directions provides a mechanism for congestion control,
particularly when BFD is used across multiple network hops. particularly when BFD is used across multiple network hops.
As recommended in [BFD-CCCV], the BFD tool needs to be extended for As recommended in [BFD-CCCV], the BFD tool needs to be extended for
the proactive CV functionality by the addition of an unique the proactive CV functionality by the addition of an unique
identifier in order to meet the requirements. The document in [BFD- identifier in order to meet the requirements. The document in [BFD-
CCCV] specifies the BFD extension and behavior to meet the CCCV] specifies the BFD extension and behavior to meet the
requirements for MPLS-TP proactive Continuity Check and Connectivity requirements for MPLS-TP proactive Continuity Check and Connectivity
Verification functionality and the RDI functionality as defined in Verification functionality and the RDI functionality as defined in
[MPLS-TP-OAM-REQ]. [RFC5860].
2. Overview of MPLS OAM for Transport Applications 2. Overview of MPLS OAM for Transport Applications
[MPLS-TP-OAM-FWK] describes how MPLS OAM mechanisms are operated to [MPLS-TP-OAM-FWK] describes how MPLS OAM mechanisms are operated to
meet transport requirements outlined in [MPLS-TP-OAM-REQ]. meet transport requirements outlined in [RFC5860].
[BFD-CCCV] specifies two BFD operation modes: 1) "CC mode", which [BFD-CCCV] specifies two BFD operation modes: 1) "CC mode", which
uses periodic BFD message exchanges with symmetric timer settings, uses periodic BFD message exchanges with symmetric timer settings,
supporting Continuity Check, 2) "CV/CC mode" which sends unique supporting Continuity Check, 2) "CV/CC mode" which sends unique
maintenance entity identifiers in the periodic BFD messages maintenance entity identifiers in the periodic BFD messages
supporting Connectivity Verification as well as Continuity Check. supporting Connectivity Verification as well as Continuity Check.
[MPLS-PM] specifies mechanisms for performance monitoring of LSPs, in [MPLS-PM] specifies mechanisms for performance monitoring of LSPs, in
particular it specifies loss and delay measurement OAM functions. particular it specifies loss and delay measurement OAM functions.
skipping to change at page 16, line 10 skipping to change at page 16, line 10
number of LSPs, targeting a single network element. number of LSPs, targeting a single network element.
Security aspects will be covered in more detailed in subsequent Security aspects will be covered in more detailed in subsequent
versions of this document. versions of this document.
8. References 8. References
8.1. Normative References 8.1. Normative References
[MPLS-CSF] [MPLS-CSF]
He, J. and H. Li, "Indication of Client Failure in He, J., Li, H., and E. Bellagamba, "Indication of Client
MPLS-TP", 2009, <draft-he-mpls-tp-csf>. Failure in MPLS-TP", 2010, <draft-he-mpls-tp-csf>.
[MPLS-FMS] [MPLS-FMS]
Swallow, G., Fulignoli, A., and M. Vigoureux, "MPLS Fault Swallow, G., Fulignoli, A., Vigoureux, M., Boutros, S.,
Management OAM", 2009, <draft-sfv-mpls-tp-fault>. and D. Ward, "MPLS Fault Management OAM", 2009,
<draft-ietf-mpls-tp-fault>.
[MPLS-PM] Bryant, S. and D. Frost, "Packet Loss and Delay [MPLS-PM] Bryant, S. and D. Frost, "Packet Loss and Delay
Measurement for the MPLS Transport Profile", 2009, Measurement for the MPLS Transport Profile", 2010,
<draft-frost-mpls-tp-loss-delay>. <draft-ietf-mpls-tp-loss-delay>.
[MPLS-TP-IDENTIF] [MPLS-PM-Profile]
Bocci, M. and G. Swallow, "MPLS-TP Identifiers", 2009, Bryant, S. and D. Frost, "A Packet Loss and Delay
<draft-swallow-mpls-tp-identifiers>. Measurement Profile for MPLS-based Transport Networks",
2010, <draft-ietf-mpls-tp-loss-delay-profile>.
[MPLS-TP-OAM-REQ] [MPLS-TP-IDENTIF]
Vigoureux, M., Ward, D., and M. Betts, "Requirements for Bocci, M., Swallow, G., and E. Gray, "MPLS-TP
OAM in MPLS Transport Networks", 2009, Identifiers", 2010, <draft-ietf-mpls-tp-identifiers>.
<draft-ietf-mpls-tp-oam-requirements>.
[OAM-CONF-FWK] [OAM-CONF-FWK]
Takacs, A., Fedyk, D., and J. van He, "OAM Configuration Takacs, A., Fedyk, D., and J. van He, "OAM Configuration
Framework for GMPLS RSVP-TE", 2009, Framework for GMPLS RSVP-TE", 2009,
<draft-ietf-ccamp-oam-configuration-fwk>. <draft-ietf-ccamp-oam-configuration-fwk>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V., [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V.,
skipping to change at page 17, line 9 skipping to change at page 17, line 9
(GMPLS) Signaling Resource ReserVation Protocol-Traffic (GMPLS) Signaling Resource ReserVation Protocol-Traffic
Engineering (RSVP-TE) Extensions", RFC 3473, January 2003. Engineering (RSVP-TE) Extensions", RFC 3473, January 2003.
[RFC5586] Bocci, M., Vigoureux, M., and S. Bryant, "MPLS Generic [RFC5586] Bocci, M., Vigoureux, M., and S. Bryant, "MPLS Generic
Associated Channel", RFC 5586, June 2009. Associated Channel", RFC 5586, June 2009.
[RFC5654] Niven-Jenkins, B., Brungard, D., Betts, M., Sprecher, N., [RFC5654] Niven-Jenkins, B., Brungard, D., Betts, M., Sprecher, N.,
and S. Ueno, "Requirements of an MPLS Transport Profile", and S. Ueno, "Requirements of an MPLS Transport Profile",
RFC 5654, September 2009. RFC 5654, September 2009.
[RFC5860] Vigoureux, M., Ward, D., and M. Betts, "Requirements for
Operations, Administration, and Maintenance (OAM) in MPLS
Transport Networks", RFC 5860, May 2010.
[RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection [RFC5880] Katz, D. and D. Ward, "Bidirectional Forwarding Detection
(BFD)", RFC 5880, June 2010. (BFD)", RFC 5880, June 2010.
[RFC5884] Aggarwal, R., Kompella, K., Nadeau, T., and G. Swallow, [RFC5884] Aggarwal, R., Kompella, K., Nadeau, T., and G. Swallow,
"Bidirectional Forwarding Detection (BFD) for MPLS Label "Bidirectional Forwarding Detection (BFD) for MPLS Label
Switched Paths (LSPs)", RFC 5884, June 2010. Switched Paths (LSPs)", RFC 5884, June 2010.
8.2. Informative References 8.2. Informative References
[BFD-CCCV] [BFD-CCCV]
Fulignoli, A., Boutros, S., and M. Vigoreux, "MPLS-TP BFD Allan, D., Swallow, G., and J. Drake, "Proactive
for Proactive CC-CV and RDI", 2009, Connectivity Verification, Continuity Check and Remote
<draft-asm-mpls-tp-bfd-cc-cv>. Defect indication for MPLS Transport Profile", 2010,
<draft-ietf-mpls-tp-bfd-cc-cv-rdi>.
[BFD-Ping] [BFD-Ping]
Bahadur, N., Aggarwal, R., Ward, D., Nadeau, T., Sprecher, Bahadur, N., Aggarwal, R., Ward, D., Nadeau, T., Sprecher,
N., and Y. Weingarten, "LSP-Ping and BFD encapsulation N., and Y. Weingarten, "LSP-Ping and BFD encapsulation
over ACH", 2009, over ACH", 2010,
<draft-nitinb-mpls-tp-lsp-ping-bfd-procedures-02>. <draft-ietf-mpls-tp-lsp-ping-bfd-procedures-02>.
[ETH-OAM] Takacs, A., Gero, B., Fedyk, D., Mohan, D., and D. Long, [ETH-OAM] Takacs, A., Gero, B., Fedyk, D., Mohan, D., and D. Long,
"GMPLS RSVP-TE Extensions for Ethernet OAM", 2009, "GMPLS RSVP-TE Extensions for Ethernet OAM", 2009,
<draft-ietf-ccamp-rsvp-te-eth-oam-ext>. <draft-ietf-ccamp-rsvp-te-eth-oam-ext>.
[LSP Ping] [LSP Ping]
Kompella, K. and G. Swallow, "Detecting Multi-Protocol Kompella, K. and G. Swallow, "Detecting Multi-Protocol
Label Switched (MPLS) Data Plane Failures", 2006, <RFC Label Switched (MPLS) Data Plane Failures", 2006, <RFC
3479>. 3479>.
[LSP-PING CONF] [LSP-PING CONF]
Bellagamba, E., Andersson, L., Ward, D., and P. Bellagamba, E., Andersson, L., Ward, D., and P.
Skoelstroem, "Configuration of pro-active MPLS-TP Skoelstroem, "Configuration of pro-active MPLS-TP
Operations, Administration, and Maintenance (OAM) Operations, Administration, and Maintenance (OAM)
Functions Using LSP Ping", 2010, Functions Using LSP Ping", 2010,
<draft-absw-mpls-lsp-ping-mpls-tp-oam-conf>. <draft-ietf-mpls-lsp-ping-mpls-tp-oam-conf>.
[MPLS-TP OAM Analysis] [MPLS-TP OAM Analysis]
Sprecher, N., Nadeau, T., van Helvoort, H., and Sprecher, N., Weingarten, Y., and E. Bellagamba, "MPLS-TP
Weingarten, "MPLS-TP OAM Analysis", 2006, OAM Analysis", 2011, <draft-ietf-mpls-tp-oam-analysis>.
<draft-sprecher-mpls-tp-oam-analysis>.
[MPLS-TP-FWK]
Bocci, M., Bryant, S., Frost, D., and L. Levrau, "OAM
Configuration Framework for GMPLS RSVP-TE", 2009,
<draft-ietf-mpls-tp-framework>.
[MPLS-TP-OAM-FWK] [MPLS-TP-OAM-FWK]
Busi, I. and B. Niven-Jenkins, "MPLS-TP OAM Framework and Bocci, M. and D. Allan, "Operations, Administration and
Overview", 2009, <draft-ietf-mpls-tp-oam-framework>. Maintenance Framework for MPLS-based Transport Networks",
2010, <draft-ietf-mpls-tp-oam-framework>.
[RFC4447] Martini, L., Rosen, E., El-Aawar, N., Smith, T., and G. [RFC4447] Martini, L., Rosen, E., El-Aawar, N., Smith, T., and G.
Heron, "Pseudowire Setup and Maintenance Using the Label Heron, "Pseudowire Setup and Maintenance Using the Label
Distribution Protocol (LDP)", RFC 4447, April 2006. Distribution Protocol (LDP)", RFC 4447, April 2006.
[RFC5921] Bocci, M., Bryant, S., Frost, D., Levrau, L., and L.
Berger, "A Framework for MPLS in Transport Networks",
RFC 5921, July 2010.
Appendix A. Additional Stuff Appendix A. Additional Stuff
This becomes an Appendix. This becomes an Appendix.
Authors' Addresses Authors' Addresses
Elisa Bellagamba (editor) Elisa Bellagamba (editor)
Ericsson Ericsson
Farogatan 6 Farogatan 6
Kista, 164 40 Kista, 164 40
 End of changes. 21 change blocks. 
40 lines changed or deleted 45 lines changed or added

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