--- 1/draft-ietf-ccamp-rsvp-te-eth-oam-ext-05.txt 2011-07-11 16:16:03.000000000 +0200 +++ 2/draft-ietf-ccamp-rsvp-te-eth-oam-ext-06.txt 2011-07-11 16:16:03.000000000 +0200 @@ -1,23 +1,20 @@ Network Working Group A. Takacs Internet-Draft B. Gero Intended status: Standards Track Ericsson -Expires: September 15, 2011 D. Fedyk - Alcatel-Lucent - H. Long +Expires: January 7, 2012 H. Long Huawei - D. Mohan - March 14, 2011 + July 11, 2011 GMPLS RSVP-TE Extensions for Ethernet OAM Configuration - draft-ietf-ccamp-rsvp-te-eth-oam-ext-05 + draft-ietf-ccamp-rsvp-te-eth-oam-ext-06 Abstract The GMPLS controlled Ethernet Label Switching (GELS) work extended GMPLS RSVP-TE to support the establishment of Ethernet LSPs. IEEE Ethernet Connectivity Fault Management (CFM) specifies an adjunct OAM flow to check connectivity in Ethernet networks. CFM can be also used with Ethernet LSPs for fault detection and triggering recovery mechanisms. The ITU-T Y.1731 specification builds on CFM and specifies additional OAM mechanisms, including Performance @@ -40,21 +37,21 @@ 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 September 15, 2011. + This Internet-Draft will expire on January 7, 2012. Copyright Notice Copyright (c) 2011 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 @@ -74,24 +71,24 @@ 3.3. Ethernet OAM Configuration TLV . . . . . . . . . . . . . . 9 3.3.1. MD Name Sub-TLV . . . . . . . . . . . . . . . . . . . 10 3.3.2. Short MA Name Sub-TLV . . . . . . . . . . . . . . . . 11 3.3.3. MEP ID Sub-TLV . . . . . . . . . . . . . . . . . . . . 12 3.3.4. Continuity Check (CC) Sub-TLV . . . . . . . . . . . . 12 3.4. Pro-active Performance Monitoring . . . . . . . . . . . . 13 3.5. Ethernet OAM configuration errors . . . . . . . . . . . . 13 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 5. Security Considerations . . . . . . . . . . . . . . . . . . . 16 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 17 - 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 18 - 7.1. Normative References . . . . . . . . . . . . . . . . . . . 18 - 7.2. Informative References . . . . . . . . . . . . . . . . . . 18 - Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 19 + 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 19 + 7.1. Normative References . . . . . . . . . . . . . . . . . . . 19 + 7.2. Informative References . . . . . . . . . . . . . . . . . . 19 + Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 20 1. Background Provider Backbone Bridging - Traffic Engineering (PBB-TE) [IEEE-PBBTE] decouples the Ethernet data and control planes by explicitly supporting external control/management mechanisms to configure static filtering entries in bridges and create explicitly routed Ethernet connections. In addition PBB-TE defines mechanisms for protection switching of bidirectional Ethernet connections. Ethernet Connectivity Fault Management (CFM) defines an adjunct @@ -273,21 +270,21 @@ connection. Note that values for these parameters may be derived from the GMPLS LSP identification parameters; o Adds a MEP ID Sub-TLV to the Ethernet OAM Configuration TLV. It selects two distinct integer values to identify the local and remote MEPs within the Maintenance Association created for monitoring of the point-to-point PBB-TE connection. Once the remote node receives the Path message it can use the UPSTREAM_LABEL to extract the reachability information of the - initiator. Then it allocates a Lable by selecting the MAC address + initiator. Then it allocates a Label by selecting the MAC address (ESP-MAC B) and VID (ESP-VID2) it would like to use to receive traffic. These parameters determine the reachability information of the local MEP. That is, the 3-tuples [ESP-MAC A, ESP-MAC B, ESP- VID1] and [ESP-MAC B, ESP-MAC A, ESP-VID2] are derived from the Ethernet Labels. In addition the information received in the Ethernet OAM Configuration TLV is used to configure the local MEP. Once the Resv message successfully arrives to the initiator it can extract the remote side's reachability information from the Label Object whereby this node has also obtained all the information needed @@ -306,23 +303,24 @@ 2-256 Reserved The receiving node when the Ethernet OAM Type is requested should look for the corresponding technology specific Ethernet OAM Configuration TLV. 3.3. Ethernet OAM Configuration TLV The Ethernet OAM Configuration TLV (depicted below) is defined for Ethernet OAM specific configuration parameters. The Ethernet OAM - Configuration TLV is carried in the LSP_ATTRIBUTES or - LSP_REQUIRED_ATTRUIBUTES object in Path messages. This new TLV - accommodates generic Ethernet OAM information and carries sub-TLVs. + Configuration TLV is carried within the OAM Configuration TLV in the + LSP_ATTRIBUTES or LSP_REQUIRED_ATTRUIBUTES object in Path messages. + This new TLV accommodates generic Ethernet OAM information and + carries sub-TLVs. 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type (IANA) | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Version |MD L.| Reserved (set to all 0s) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | ~ sub TLVs ~ @@ -540,20 +538,30 @@ This document does not introduce any additional security issuse to those discussed in [OAM-CONF-FWK]. 6. Acknowledgements The authors would like to thank Francesco Fondelli, Adrian Farrel, Loa Andersson, Eric Gray and Dimitri Papadimitriou for their useful comments. +Contributors + + Don Fedyk + Alcatel-Lucent + Groton, MA 01450 + USA + Email: donald.fedyk@alcatel-lucent.com + + Dinesh Mohan + 7. References 7.1. Normative References [OAM-CONF-FWK] "OAM Configuration Framework for GMPLS RSVP-TE", Internet Draft, work in progress. [RFC5828] "GMPLS Ethernet Label Switching Architecture and Framework", RFC 5828, March 2010. @@ -583,23 +591,14 @@ Email: attila.takacs@ericsson.com Balazs Gero Ericsson Laborc u. 1. Budapest, 1037 Hungary Email: balazs.gero@ericsson.com - Don Fedyk - Alcatel-Lucent - Groton, MA 01450 - USA - - Email: donald.fedyk@alcatel-lucent.com - Hao Long Huawei Email: lonho@huawei.com - - Dinesh Mohan