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