draft-ietf-ccamp-rsvp-te-eth-oam-ext-01.txt | draft-ietf-ccamp-rsvp-te-eth-oam-ext-02.txt | |||
---|---|---|---|---|
Network Working Group A. Takacs | Network Working Group A. Takacs | |||
Internet-Draft B. Gero | Internet-Draft B. Gero | |||
Intended status: Standards Track Ericsson | Intended status: Standards Track Ericsson | |||
Expires: September 10, 2009 D. Fedyk | Expires: April 29, 2010 D. Fedyk | |||
Alcatel-Lucent | ||||
D. Mohan | D. Mohan | |||
Nortel | Nortel | |||
H. Long | H. Long | |||
Huawei | Huawei | |||
March 9, 2009 | October 26, 2009 | |||
GMPLS RSVP-TE Extensions for Ethernet OAM Configuration | GMPLS RSVP-TE Extensions for Ethernet OAM Configuration | |||
draft-ietf-ccamp-rsvp-te-eth-oam-ext-01 | draft-ietf-ccamp-rsvp-te-eth-oam-ext-02 | |||
Status of this Memo | Status of this Memo | |||
This Internet-Draft is submitted to IETF in full conformance with the | This Internet-Draft is submitted to IETF in full conformance with the | |||
provisions of BCP 78 and BCP 79. | provisions of BCP 78 and BCP 79. | |||
Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
Task Force (IETF), its areas, and its working groups. Note that | Task Force (IETF), its areas, and its working groups. Note that | |||
other groups may also distribute working documents as Internet- | other groups may also distribute working documents as Internet- | |||
Drafts. | Drafts. | |||
skipping to change at page 1, line 37 | skipping to change at page 1, line 38 | |||
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." | |||
The list of current Internet-Drafts can be accessed at | The list of current Internet-Drafts can be accessed at | |||
http://www.ietf.org/ietf/1id-abstracts.txt. | http://www.ietf.org/ietf/1id-abstracts.txt. | |||
The list of Internet-Draft Shadow Directories can be accessed at | The list of Internet-Draft Shadow Directories can be accessed at | |||
http://www.ietf.org/shadow.html. | http://www.ietf.org/shadow.html. | |||
This Internet-Draft will expire on September 10, 2009. | This Internet-Draft will expire on April 29, 2010. | |||
Copyright Notice | Copyright Notice | |||
Copyright (c) 2009 IETF Trust and the persons identified as the | Copyright (c) 2009 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 in effect on the date of | |||
(http://trustee.ietf.org/license-info) in effect on the date of | publication of this document (http://trustee.ietf.org/license-info). | |||
publication of this document. Please review these documents | Please review these documents carefully, as they describe your rights | |||
carefully, as they describe your rights and restrictions with respect | and restrictions with respect to this document. | |||
to this document. | ||||
This document may contain material from IETF Documents or IETF | ||||
Contributions published or made publicly available before November | ||||
10, 2008. The person(s) controlling the copyright in some of this | ||||
material may not have granted the IETF Trust the right to allow | ||||
modifications of such material outside the IETF Standards Process. | ||||
Without obtaining an adequate license from the person(s) controlling | ||||
the copyright in such materials, this document may not be modified | ||||
outside the IETF Standards Process, and derivative works of it may | ||||
not be created outside the IETF Standards Process, except to format | ||||
it for publication as an RFC or to translate it into languages other | ||||
than English. | ||||
Abstract | Abstract | |||
The GMPLS controlled Ethernet Label Switching (GELS) work is | The GMPLS controlled Ethernet Label Switching (GELS) work is | |||
extending GMPLS RSVP-TE to support the establishment of Ethernet | extending GMPLS RSVP-TE to support the establishment of Ethernet | |||
LSPs. IEEE Ethernet Connectivity Fault Management (CFM) specifies an | LSPs. IEEE Ethernet Connectivity Fault Management (CFM) specifies an | |||
adjunct OAM flow to check connectivity in Ethernet networks. CFM can | adjunct OAM flow to check connectivity in Ethernet networks. CFM can | |||
be also used with Ethernet LSPs for fault detection and triggering | be also used with Ethernet LSPs for fault detection and triggering | |||
recovery mechanisms. The ITU-T Y.1731 specification builds on CFM | recovery mechanisms. The ITU-T Y.1731 specification builds on CFM | |||
and specifies additional OAM mechanisms, including Performance | and specifies additional OAM mechanisms, including Performance | |||
skipping to change at page 4, line 13 | skipping to change at page 3, line 13 | |||
TLV to [OAM-CONF-FWK]. | TLV to [OAM-CONF-FWK]. | |||
Requirements Language | 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 | document are to be interpreted as described in | |||
Table of Contents | Table of Contents | |||
1. Background . . . . . . . . . . . . . . . . . . . . . . . . . . 5 | 1. Background . . . . . . . . . . . . . . . . . . . . . . . . . . 4 | |||
2. Overview of Ethernet OAM operation . . . . . . . . . . . . . . 6 | 2. Overview of Ethernet OAM operation . . . . . . . . . . . . . . 5 | |||
3. GMPLS RSVP-TE Extensions . . . . . . . . . . . . . . . . . . . 8 | 3. GMPLS RSVP-TE Extensions . . . . . . . . . . . . . . . . . . . 7 | |||
3.1. Operation overview . . . . . . . . . . . . . . . . . . . . 8 | 3.1. Operation overview . . . . . . . . . . . . . . . . . . . . 7 | |||
3.2. OAM Configuration TLV . . . . . . . . . . . . . . . . . . 10 | 3.2. OAM Configuration TLV . . . . . . . . . . . . . . . . . . 9 | |||
3.3. Ethernet OAM Configuration TLV . . . . . . . . . . . . . . 10 | 3.3. Ethernet OAM Configuration TLV . . . . . . . . . . . . . . 9 | |||
3.3.1. MD Name Sub-TLV . . . . . . . . . . . . . . . . . . . 11 | 3.3.1. MD Name Sub-TLV . . . . . . . . . . . . . . . . . . . 10 | |||
3.3.2. Short MA Name Sub-TLV . . . . . . . . . . . . . . . . 12 | 3.3.2. Short MA Name Sub-TLV . . . . . . . . . . . . . . . . 11 | |||
3.3.3. MEP ID Sub-TLV . . . . . . . . . . . . . . . . . . . . 13 | 3.3.3. MEP ID Sub-TLV . . . . . . . . . . . . . . . . . . . . 12 | |||
3.3.4. Continuity Check (CC) Sub-TLV . . . . . . . . . . . . 13 | 3.3.4. Continuity Check (CC) Sub-TLV . . . . . . . . . . . . 12 | |||
3.4. Pro-active Performance Monitoring . . . . . . . . . . . . 14 | 3.4. Pro-active Performance Monitoring . . . . . . . . . . . . 13 | |||
3.5. Ethernet OAM configuration errors . . . . . . . . . . . . 14 | 3.5. Ethernet OAM configuration errors . . . . . . . . . . . . 13 | |||
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 | 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 | |||
5. Security Considerations . . . . . . . . . . . . . . . . . . . 17 | 5. Security Considerations . . . . . . . . . . . . . . . . . . . 16 | |||
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 18 | 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 17 | |||
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 19 | 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 18 | |||
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 20 | Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 19 | |||
Intellectual Property and Copyright Statements . . . . . . . . . . 21 | ||||
1. Background | 1. Background | |||
Provider Backbone Bridging - Traffic Engineering (PBB-TE) | Provider Backbone Bridging - Traffic Engineering (PBB-TE) | |||
[IEEE-PBBTE] decouples the Ethernet data and control planes by | [IEEE-PBBTE] decouples the Ethernet data and control planes by | |||
explicitly supporting external control/management mechanisms to | explicitly supporting external control/management mechanisms to | |||
configure static filtering entries in bridges and create explicitly | configure static filtering entries in bridges and create explicitly | |||
routed Ethernet connections. In addition PBB-TE defines mechanisms | routed Ethernet connections. In addition PBB-TE defines mechanisms | |||
for 1:1 protection switching of bidirectional Ethernet connections. | for 1:1 protection switching of bidirectional Ethernet connections. | |||
skipping to change at page 20, line 24 | skipping to change at page 19, line 24 | |||
Balazs Gero | Balazs Gero | |||
Ericsson | Ericsson | |||
Laborc u. 1. | Laborc u. 1. | |||
Budapest, 1037 | Budapest, 1037 | |||
Hungary | Hungary | |||
Email: balazs.gero@ericsson.com | Email: balazs.gero@ericsson.com | |||
Don Fedyk | Don Fedyk | |||
Nortel | Alcatel-Lucent | |||
600 Technology Park Drive | Groton, MA 01450 | |||
Billerica, MA 01821 | ||||
USA | USA | |||
Email: dwfedyk@nortel.com | Email: donald.fedyk@alcatel-lucent.com | |||
Dinesh Mohan | Dinesh Mohan | |||
Nortel | Nortel | |||
3500 Carling Ave | 3500 Carling Ave | |||
Ottawa, ON, K2H8E9 | Ottawa, ON, K2H8E9 | |||
Canada | Canada | |||
Email: mohand@nortel.com | Email: mohand@nortel.com | |||
Hao Long | Hao Long | |||
End of changes. 8 change blocks. | ||||
43 lines changed or deleted | 29 lines changed or added | |||
This html diff was produced by rfcdiff 1.37a. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ |