PWE3 Working Group Dinesh Mohan Internet Draft: Michael Chen draft-mohan-pwe3-vccv-eth-01.txt Dave Allan Expiration Date: July 2007 Nortel Muneyoshi Suzuki NTT Lei Zhu Simon Delord Sprint Uecomm Philippe Niger Yaakov Stein Gilles Joncour RAD France Telecom Yang Yang Kenji Kumaki Huawei Munefumi Tsurusawa KDDI January 2007 VCCV Extension for Ethernet OAM draft-mohan-pwe3-vccv-eth-01.txt Status of this Memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. 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." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. Abstract Mohan, et. al. Expiry : July 2007 [Page 1] Internet Draft draft-mohan-pwe3-vccv-eth-01.txt January 2007 This document proposes extensions to Virtual Circuit Connection Verification (VCCV) procedures to add Ethernet OAM functionality. VCCV supports connection verification applications for PWs regardless of the underlying public service network technology. This document proposes VCCV to support Ethernet OAM as an option to perform operations and maintenance functions; especially when the PSN is Ethernet. Table of Contents: Status of this Memo................................................1 Abstract...........................................................1 1. Introduction....................................................2 2. Ethernet PSN....................................................3 3. VCCV Types Extension............................................3 3.1 Ethernet OAM...................................................3 3.2 Ethernet OAM Capability Indications............................4 4. IANA Considerations.............................................4 4.1 CV Types.......................................................4 5. Ethernet OAM Applications and Scenarios.........................4 5.1 Ethernet OAM Encapsulation.....................................4 5.2 Ethernet OAM Functions.........................................5 5.3 Ethernet OAM in MSPW...........................................5 6. Security Considerations.........................................5 7. Intellectual Property Statement.................................5 8. Normative References............................................5 9. Informative References..........................................5 10. Acknowledgments................................................6 11. Authors' Addresses.............................................6 Full Copyright Statement...........................................7 1. Introduction [VCCV] describes a mechanism for PSN-agnostic fault detection and diagnostics for an emulated PW service. The VCCV control channel is associated with a PW. VCCV control channel carries encapsulated messages e.g. ICMP ping, BFD, MPLS ping etc. Ethernet OAM, as being defined in [802.1ag] and [Y.1731], offers a rich set of functionality that has been designed for proactive and on-demand OAM. Some of the desirable functionalities e.g. performance monitoring, remote maintenance, etc. are not available in MPLS ping, BFD, etc. In addition, hierarchical OAM requirements have also been identified in [MSPW-REQ], for which the solutions are not yet identified. Such functionality may be added to mechanisms currently used in [VCCV]; however, such functionality is not yet addressed and Ethernet OAM has already defined these. Similar to MPLS ping, BFD, Mohan, et. al Expiry : July 2007 [Page 2] Internet Draft draft-mohan-pwe3-vccv-eth-01.txt January 2007 etc. being used in MPLS/IP PSN, Ethernet OAM is a natural choice for Ethernet based PSN. As per the procedures described in [VCCV], the choice of Ethernet OAM based VCCV messages can be negotiated between the PEs. This document specifies the extensions required to support Ethernet OAM as an option for VCCV messages. 2. Ethernet PSN Ethernet is fast emerging as a viable PSN technology especially for metro area networks. Recent discussions in IETF have also shown considerable interest in Ethernet technology with specific work items being created to address the control plane aspects of Ethernet PSN. Examples include the TRILL WG, GELS BOF, and discussions around generic PWs which seem to have indicated that PSNs may not be limited to MPLS/IP. Even though the PW over Ethernet PSN is not completely specified yet, some solutions like [PWoPBT] have been proposed that address this particular space. Since [VCCV] is meant to be agnostic to specific PSN and provides capability to carry different message types which are most often tied to the PSN type, this document adds an option to VCCV control channel to carry Ethernet OAM messages. 3. VCCV Types Extension [VCCV] specifies different types of protocols that can be carried in the VCCV control channel simultaneously or individually. The following sections indicate the specific extensions to [VCCV] to support Ethernet OAM as an option for Ethernet PSN. 3.1 Ethernet OAM This section can be added as a new section 5.3 in [VCCV]. In order to use Ethernet OAM, both ends of the PW must have signaled the existence of a control channel and the ability to run Ethernet OAM. The use of control channel provides the context required to bind the Ethernet OAM messages to a particular PW. Ethernet OAM includes the following OpCodes for Ethernet OAM messages that can be carried in the VCCV control channel: 01 -- CCM - Continuity check messages 03 -- LBM - Loopback request message 02 -- LBR - Loopback reply message 05 -- LTM - Linktrace request message 04 -- LTR - Linktrace reply message Mohan, et. al Expiry : July 2007 [Page 3] Internet Draft draft-mohan-pwe3-vccv-eth-01.txt January 2007 33 -- AIS - Alarm indication signal message 41 -- MCC - Maintenance communication channel message 43 -- LMM - Single-ended loss measurement request message 42 -- LMR - Single-ended oss measurement reply message 45 -- 1DM - Dual-ended delay measurement message 47 -- DMM - Two-way delay measurement request message 46 -- DMR - Two-way delay measurement reply message xx -- others that may not be needed here 3.2 Ethernet OAM Capability Indications This section can be added to section 6.1 in [VCCV]. The format of the VCCV parameter field is as follows: 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 0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 0x0c | 0x04 | CC Types | CV Types | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ The CV Type Indicators field is a bit mask used to indicate the specific type or types (i.e.: none, one or more) of control channel packets that may be sent on the specified control channel. The defined values are: 0x01 ICMP Ping 0x02 LSP Ping 0x04 BFD for PW Fault Detection only 0x08 BFD for PW Fault Detection and AC/PW Fault Status Signaling 0x10 Ethernet OAM as defined in [Y.1731] and [802.1ag] 4. IANA Considerations 4.1 CV Types This section can be added to section 8.1.2 in [VCCV]. 0x01 ICMP Ping 0x02 LSP Ping 0x04 BFD 0x10 Ethernet OAM 5. Ethernet OAM Applications and Scenarios 5.1 Ethernet OAM Encapsulation TBD Mohan, et. al Expiry : July 2007 [Page 4] Internet Draft draft-mohan-pwe3-vccv-eth-01.txt January 2007 5.2 Ethernet OAM Functions TBD 5.3 Ethernet OAM in MSPW TBD 6. Security Considerations Introduction of the Ethernet OAM messages to VCCV control channel does not present any new security considerations besides those that are already listed in [VCCV]. 7. Intellectual Property Statement The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf- ipr@ietf.org. 8. Normative References [Y.1731] ITU-T Recommendation Y.1731, OAM Functions and Mechanisms for Ethernet based Networks, May 2006. 9. Informative References Mohan, et. al Expiry : July 2007 [Page 5] Internet Draft draft-mohan-pwe3-vccv-eth-01.txt January 2007 [VCCV] Nadeau et. al., Pseudo Wire Virtual Circuit Connectivity Verification, draft-ietf-pwe3-vccv-09.txt, work in progress. [MPLS-PING] Kompella et. al., Detecting MPLS Data Plane Failures, draft-ietf-mpls-lsp-ping-12.txt, work in progress. [BFD] Katz et. al., Bidirectional Forwarding Detection, draft-ietf- bfd-base-05.txt, work in progress. [PWoPBT] Allan et. al., Pseudo Wire over Provider Backbone Transport, draft-allan-pw-o-pbt-00.txt, work in progress. [802.1ag] Connectivity Fault Management, IEEE 802.1ag draft 6.1, work in progress. [MSPW-REQ] Bitar et. al., Requirements for inter domain Puedowires, draft-ietf-pwe3-ms-pw-requirements-02.txt, work in progress. 10. Acknowledgments The authors would like to thank Florin Balus and Jeffery Sugimoto for their valuable comments and suggestions. 11. Authors' Addresses Dinesh Mohan Nortel 3500 Carling Ave. Ottawa ON K2H 8E9 Canada Email: mohand@nortel.com Michael Chen Nortel 4010 East Chapel Hill-Nelson Hwy Research Triangle Park NC 27709 Email: mchen@nortel.com Dave Allan Nortel 3500 Carling Ave. Ottawa ON K2H 8E9 Canada Email: dallan@nortel.com Yang Yang Huawei Technologies Co., Ltd. Bantian Industry Base, Longgang District Shenzhen, P.R. China Email: healthinghearts@huawei.com Mohan, et. al Expiry : July 2007 [Page 6] Internet Draft draft-mohan-pwe3-vccv-eth-01.txt January 2007 Yaakov (Jonathan) Stein RAD Data Communications 24 Raoul Wallenberg St., Bldg C Tel Aviv 69719 Israel Email: yaakov_s@rad.com Muneyoshi Suzuki NTT 1-6, Nakase, Mihama-ku, Chiba-shi, Chiba 261-0023, Japan Email: suzuki.muneyoshi@lab.ntt.co.jp Lei Zhu Sprint 6220 Sprint Parkway Overland Park, Kansas 66251 Email: lei.zhu@mail.sprint.com Simon Delord Uecomm 658 Church St Richmond, VIC, 3121, Australia Email: sdelord@uecomm.com.au Philippe Niger France Telecom 2 av. Pierre Marzin 22300 Lannion, France Email: philippe.niger@orange-ft.com Gilles Joncour France Telecom 2 av. Pierre Marzin 22300 Lannion, France Email: gilles.joncour@orange-ft.com Kenji Kumaki KDDI Corporation Iidabashi, Chiyoda-ku, Tokyo 102-8460, Japan Email: ke-kumaki@kddi.com Munefumi Tsurusawa KDDI Corporation Email: tsuru@kddilabs.jp Full Copyright Statement Copyright (C) The IETF Trust (2007). Mohan, et. al Expiry : July 2007 [Page 7] Internet Draft draft-mohan-pwe3-vccv-eth-01.txt January 2007 This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.