draft-ietf-ccamp-rsvp-te-eth-oam-ext-08.txt   draft-ietf-ccamp-rsvp-te-eth-oam-ext-09.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: January 14, 2013 H. Long Expires: August 29, 2013 H. Long
Huawei Huawei
July 13, 2012 February 25, 2013
GMPLS RSVP-TE Extensions for Ethernet OAM Configuration GMPLS RSVP-TE Extensions for Ethernet OAM Configuration
draft-ietf-ccamp-rsvp-te-eth-oam-ext-08 draft-ietf-ccamp-rsvp-te-eth-oam-ext-09
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
Monitoring, for Ethernet networks. This document specifies Monitoring, for Ethernet networks. This document specifies
extensions of GMPLS RSVP-TE to support the setup of the associated extensions of GMPLS RSVP-TE to support the setup of the associated
Ethernet OAM (CFM and Y.1731) entities defining Ethernet technology Ethernet OAM entities of Ethernet LSPs, and defines the Ethernet
specific TLV based on [OAM-CONF-FWK]. technology specific TLV based on [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
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
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 January 14, 2013. This Internet-Draft will expire on August 29, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2013 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 4, line 7 skipping to change at page 4, line 7
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15
5. Security Considerations . . . . . . . . . . . . . . . . . . . 16 5. Security Considerations . . . . . . . . . . . . . . . . . . . 16
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 17 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 17
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 19 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 19
7.1. Normative References . . . . . . . . . . . . . . . . . . . 19 7.1. Normative References . . . . . . . . . . . . . . . . . . . 19
7.2. Informative References . . . . . . . . . . . . . . . . . . 19 7.2. Informative References . . . . . . . . . . . . . . . . . . 19
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 20 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 20
1. Background 1. Background
Provider Backbone Bridging - Traffic Engineering (PBB-TE) Provider Backbone Bridging - Traffic Engineering (PBB-TE) [IEEE]
[IEEE-PBBTE] decouples the Ethernet data and control planes by decouples the Ethernet data and control planes, and allows external
explicitly supporting external control/management mechanisms to control and management mechanisms to create explicitly routed
configure static filtering entries in bridges and create explicitly Ethernet connections. In addition, PBB-TE defines mechanisms for
routed Ethernet connections. In addition PBB-TE defines mechanisms protection switching of bidirectional Ethernet connections. Ethernet
for protection switching of bidirectional Ethernet connections. Connectivity Fault Management (CFM) defines an adjunct connectivity
Ethernet Connectivity Fault Management (CFM) defines an adjunct monitoring OAM flow to check the liveliness of Ethernet networks
connectivity monitoring OAM flow to check the liveliness of Ethernet [IEEE], including the monitoring of specific explicitly routed
networks [IEEE-CFM], including the monitoring of explicitly-routed
Ethernet connections. Ethernet connections.
In IETF the GMPLS controlled Ethernet Label Switching (GELS) work In IETF the GMPLS controlled Ethernet Label Switching (GELS) work
extended the GMPLS control plane to support the establishment of extended the GMPLS control plane to support the establishment of
explicitly routed Ethernet connections [RFC5828][RFC6060]. We refer explicitly routed Ethernet connections [RFC5828][RFC6060]. We refer
to GMPLS established Ethernet connections as Ethernet LSPs. GELS to GMPLS established Ethernet connections as Ethernet LSPs. GELS
enables the application of MPLS-TE and GMPLS provisioning and enables the application of MPLS-TE and GMPLS provisioning and
recovery features in Ethernet networks. recovery features in Ethernet networks.
2. Overview of Ethernet OAM operation 2. Overview of Ethernet OAM operation
For the purposes of this document, we only discuss Ethernet OAM For the purposes of this document, we only discuss those Ethernet OAM
[IEEE-CFM] aspects that are relevant for the connectivity monitoring [IEEE] aspects that are relevant for the connectivity monitoring of
of Ethernet LSPs. Ethernet LSPs.
PBB-TE [IEEE-PBBTE] defines point-to-point Ethernet Switched Paths PBB-TE [IEEE] defines point-to-point Ethernet Switched Paths (ESPs)
(ESPs) as a provisioned traffic engineered unidirectional as a provisioned traffic engineered unidirectional connectivity,
connectivity, identified by the 3-tuple [ESP-MAC DA, ESP-MAC SA, ESP- identified by the 3-tuple [ESP-MAC DA, ESP-MAC SA, ESP-VID], where
VID] where the ESP-MAC DA is the destination address of the ESP, the the ESP-MAC DA is the destination address of the ESP, the ESP-MAC SA
ESP-MAC SA is the source address of the ESP, and the ESP-VID is a is the source address of the ESP, and the ESP-VID is a VLAN
VLAN identifier allocated for explicitly routed connections. To form identifier allocated for explicitly routed connections. To form a
a bidirectional PBB-TE connection two co-routed point-to-point ESPs bidirectional PBB-TE connection two co-routed point-to-point ESPs are
are combined. The combined ESPs must have the same ESP-MAC addresses combined. The combined ESPs must have the same ESP-MAC addresses but
but may have different ESP-VIDs. may have different ESP-VIDs.
Note that although it would be possible to use GMPLS to setup a Note that although it would be possible to use GMPLS to setup a
single unidirectional ESP, the Ethernet OAM mechanisms are only full single unidirectional ESP, the Ethernet OAM mechanisms are only full
functional when bidirectional connections are established with co- functional when bidirectional connections are established with co-
routed ESPs. Hence, we focus on bidirectional point-to-point PBB-TE routed ESPs. Therfore, the scope of this document only covers
connections only. bidirectional point-to-point PBB-TE connections.
At both ends of the bidirectional point-to-point PBB-TE connection At both ends of the bidirectional point-to-point PBB-TE connection
one Maintenance Endpoint (MEP) is configured. The MEPs monitoring a one Maintenance Endpoint (MEP) is configured. The MEPs monitoring a
PBB-TE connection must be configured with the same Maintenance Domain PBB-TE connection must be configured with the same Maintenance Domain
Level (MD Level) and Maintenance Association Identifier (MAID). Each Level (MD Level) and Maintenance Association Identifier (MAID). Each
MEP has a unique identifier, the MEP ID. Besides these identifiers a MEP has a unique identifier, the MEP ID. Besides these identifiers a
MEP monitoring a PBB-TE connection must be provisioned with the MEP monitoring a PBB-TE connection must be provisioned with the
3-tuples [ESP-MAC DA, ESP-MAC SA, ESP-VID] of the two ESPs. 3-tuples [ESP-MAC DA, ESP-MAC SA, ESP-VID] of the two ESPs.
In the case of point-to-point VLAN connections, the connection is In the case of point-to-point VLAN connections, the connection may be
identified with a single VLAN forwarding traffic in both directions identified with a single VLAN, or with two VLANs one for each
or with two VLANs each forwarding traffic in a single direction. direction. Therefore, instead of the 3-tuples of the PBB-TE ESPs,
Hence instead of the 3-tuples of the PBB-TE case MEPs must be MEPs must be provisioned with the proper VLAN identifiers.
provisioned with the proper VLAN information, otherwise the same MD
Level, MAID, MEP ID configuration is required in this case as well.
MEPs exchange Connectivity Check Messages (CCMs) periodically with MEPs exchange Connectivity Check Messages (CCMs) periodically with
fixed intervals. Eight distinct intervals are defined in [IEEE-CFM]: fixed intervals. Eight distinct intervals are defined in [IEEE]:
+---+--------------------+----------------+ +---+--------------------+----------------+
| # | CCM Interval (CCI) | 3 bit encoding | | # | CCM Interval (CCI) | 3 bit encoding |
+---+--------------------+----------------+ +---+--------------------+----------------+
| 0 | Reserved | 000 | | 0 | Reserved | 000 |
| | | | | | | |
| 1 | 3 1/3 ms | 001 | | 1 | 3 1/3 ms | 001 |
| | | | | | | |
| 2 | 10 ms | 010 | | 2 | 10 ms | 010 |
| | | | | | | |
skipping to change at page 6, line 27 skipping to change at page 6, line 27
| | | | | | | |
| 5 | 10 s | 101 | | 5 | 10 s | 101 |
| | | | | | | |
| 6 | 1 min | 110 | | 6 | 1 min | 110 |
| | | | | | | |
| 7 | 10 min | 111 | | 7 | 10 min | 111 |
+---+--------------------+----------------+ +---+--------------------+----------------+
Table 1: CCM Interval encoding Table 1: CCM Interval encoding
If 3 consecutive CCM messages are not received by one of the MEPs it If 3 consecutive CCM messages are lost; connectivity failure is
declares a connectivity failure and signals the failure in subsequent declared. The MEP detecting the failiure will signal the defect to
CCM messages, by setting the Remote Defect Indicator (RDI) bit, to the remote MEP in the subsequent CCM messages it emmits, by setting
the remote MEP. If a MEP receives a CCM message with RDI set it the Remote Defect Indicator (RDI) bit in the CCM message. If a MEP
immediately declares failure. The detection of a failure may trigger receives a CCM message with RDI bit set it immediately declares
protection switching mechanisms or may be signaled to a management failure. The detection of a failure may trigger protection switching
system. However, what happens once a failure is detected is out of mechanisms or may be signaled to a management system.
the scope of this document.
At each transit node Maintenance Intermediate Points (MIPs) can be At each transit node Maintenance Intermediate Points (MIPs) may be
established to help failure localization by supporting link trace and established to help failure localization, e.g., using link trace and
loop back functions. MIPs need to be provisioned with a subset of loop back functions. MIPs need to be provisioned with a subset of
MEP identification parameters described above. the MEP identification parameters described above.
3. GMPLS RSVP-TE Extensions 3. GMPLS RSVP-TE Extensions
3.1. Operation overview 3.1. Operation overview
To simplify the configuration of connectivity monitoring, when an To simplify the configuration of connectivity monitoring, when an
Ethernet LSP is signaled the associated MEPs should be automatically Ethernet LSP is signaled the associated MEPs should be automatically
established. To monitor an Ethernet LSP a set of parameters must be established. To monitor an Ethernet LSP a set of parameters must be
provided to setup a Maintenance Association and related MEPs. provided to setup a Maintenance Association and related MEPs.
Optionally, MIPs may be created at the transit nodes of the Ethernet Optionally, MIPs may be created at the transit nodes of the Ethernet
LSP. The LSP Attributes Flags: "OAM MEP entities desired" and "OAM LSP. The LSP Attributes Flags: "OAM MEP entities desired" and "OAM
MIP entities desired", described in [OAM-CONF-FWK] are used to signal MIP entities desired", described in [OAM-CONF-FWK] are used to signal
that the respective OAM entities must be established. Subsequently, that the respective OAM entities must be established. Subsequently,
an OAM Configuration TLV is added to the LSP_ATTRIBUTES Object an OAM Configuration TLV is added to the LSP_ATTRIBUTES Object
specifying that Ethernet OAM is to be setup for the LSP. The below specifying that Ethernet OAM is to be setup for the LSP. Ethernet
detailed Ethernet OAM specific information is carried in the new OAM specific information, as described below, is carried in the new
Ethernet OAM Configuration sub-TLV. Ethernet OAM Configuration sub-TLV.
o A unique MAID must be allocated for the PBB-TE connection and both o A unique MAID must be allocated for the PBB-TE connection and both
MEPs must be configured with the same information. The MAID MEPs must be configured with the same information. The MAID
consists of an optional Maintenance Domain Name (MD Name) and a consists of an optional Maintenance Domain Name (MD Name) and a
mandatory Short Maintenance Association Name (Short MA Name). mandatory Short Maintenance Association Name (Short MA Name).
Various formatting rules for these names have been defined by Various formatting rules for these names have been defined in
[IEEE-CFM]. Since these information is also carried in all CCM [IEEE]. Since this information is also carried in all CCM
messages, the combined length of the Names is limited to 44 bytes. messages, the combined length of the Names is limited to 44 bytes.
How these parameters are determined is out of scope of this How these parameters are determined is out of scope of this
document. document.
o Each MEP must be provisioned with a MEP ID. The MEP ID uniquely o Each MEP must be provisioned with a MEP ID. The MEP ID uniquely
identifies a given MEP within a Maintenance Association. That is, identifies a given MEP within a Maintenance Association. That is,
the combination of MAID and MEP ID must uniquely identify a MEP. the combination of MAID and MEP ID must uniquely identify a MEP.
How the value of the MEP ID is determined is out of scope of this How the value of the MEP ID is determined is out of scope of this
document. document.
o The Maintenance Domain Level (MD Level) allows hierarchical o The Maintenance Domain Level (MD Level) allows hierarchical
separation of monitoring entities. [IEEE-CFM] allows separation of monitoring entities. [IEEE] allows differentiation
differentiation of 8 levels. How the value of the MD Level is of 8 levels. How the value of the MD Level is determined is out
determined is out of scope of this document. Note that most of scope of this document. Note that most probably for all
probably for all Ethernet LSPs a single (default) MD Level will be Ethernet LSPs a single (default) MD Level will be used within a
used within a network domain. network domain.
o The desired CCM Interval must be specified by the management o The desired CCM Interval must be specified by the management
system based on service requirements or operator policy. The same system based on service requirements or operator policy. The same
CCM Interval must be set in each of the MEPs monitoring a given CCM Interval must be set in each of the MEPs monitoring a given
Ethernet LSP. How the value of the CCM Interval is determined is Ethernet LSP. How the value of the CCM Interval is determined is
out of scope of this document. out of scope of this document.
o The desired CCM priority to be set by MEPs for the CCM frames can o The desired forwarding priority to be set by MEPs for the CCM
be specified. The same CCM priority must be set in each of the frames can be specified. The same CCM priority must be set in
MEPs monitoring a given Ethernet LSP. How CCM priority is each of the MEPs monitoring a given Ethernet LSP. How CCM
determined is out of scope of this document. Note that the priority is determined is out of scope of this document. Note
highest priority is used as the default CCM priority. that the highest priority is used as the default CCM priority.
o MEPs must be aware of their own and the reachability parameters of o MEPs must be aware of their own and the reachability parameters of
the remote MEP. In the case of bidirectional point-to-point the remote MEP. In the case of bidirectional point-to-point
PBB-TE connections this requires that the 3-tuples [ESP-MAC A, PBB-TE connections this requires that the 3-tuples [ESP-MAC A,
ESP-MAC B, ESP-VID1] and [ESP-MAC B, ESP-MAC A, ESP-VID2] are ESP-MAC B, ESP-VID1] and [ESP-MAC B, ESP-MAC A, ESP-VID2] are
configured in each MEP, where the ESP-MAC A is the same as the configured in each MEP, where the ESP-MAC A is the same as the
local MEP's MAC address and ESP-MAC B is the same as remote MEP's local MEP's MAC address and ESP-MAC B is the same as remote MEP's
MAC address. The GMPLS Ethernet Label for forwarding, as defined MAC address. The GMPLS Ethernet Label format, as defined in
in [RFC6060], consists of the ESP-MAC DA and ESP-VID. Hence the [RFC6060], consists of the ESP-MAC DA and ESP-VID. Hence the
necessary reachability parameters for the MEPs can be obtained necessary reachability parameters for the MEPs can be obtained
from Ethernet Labels (i.e., carried in the "downstream" and from Ethernet Labels (i.e., carried in the "downstream" and
upstream labels). In the case of point-to-point VLAN connections, upstream labels). In the case of point-to-point VLAN connections,
MEPs need to be provisioned with the VLAN identifiers, which can MEPs need to be provisioned with the VLAN identifiers only, which
be derived similarly from the Ethernet Label. can be derived similarly from the Ethernet Label.
Assuming the procedures described in [RFC6060] for bidirectional Assuming the procedures described in [RFC6060] for bidirectional
PBB-TE Ethernet LSP establishment the MEP configuration should be as PBB-TE Ethernet LSP establishment the MEP configuration should be as
follows. When the RSVP-TE signaling is initiated for the follows. When the RSVP-TE signaling is initiated for the
bidirectional Ethernet LSP the local node generates a Path message bidirectional Ethernet LSP the local node generates a Path message
and: and:
o Allocates an Upstream Label from its MAC address (ESP-MAC A) and o Allocates an Upstream Label formed by combining its MAC address
locally selected VID (ESP-VID1), which will be used to receive (ESP-MAC A) and locally selected VID (ESP-VID1), which will be
traffic; used to receive traffic;
o Inserts the OAM Configuration TLV with OAM Type set to Ethernet o Inserts the OAM Configuration TLV with OAM Type set to Ethernet
OAM in the LSP_ATTRIBUTES object; OAM in the LSP_ATTRIBUTES object;
o Adds the OAM Function Flags sub-TLV in the OAM Configuration TLV o Adds the OAM Function Flags sub-TLV in the OAM Configuration TLV
and sets the OAM function flags as needed; and sets the OAM function flags as needed;
o Adds an Ethernet OAM Configuration sub-TLV in the OAM o Adds an Ethernet OAM Configuration sub-TLV in the OAM
Configuration TLV that specifies the CCM Interval and MD Level; Configuration TLV that specifies the CCM Interval and MD Level;
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 Label by selecting the MAC address initiator. Then it allocates a Label by selecting a local MAC
(ESP-MAC B) and VID (ESP-VID2) it would like to use to receive address (ESP-MAC B) and VID (ESP-VID2) that will be used 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, this 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 and therefore it has all the information needed to properly
to establish its local MEP. configure its local MEP.
3.2. OAM Configuration TLV 3.2. OAM Configuration TLV
This TLV is specified in [OAM-CONF-FWK] and is used to select which This TLV is specified in [OAM-CONF-FWK] and is used to select which
OAM technology/method should be used for the LSP. In this document a OAM technology/method should be used for the LSP. In this document a
new OAM Type: Ethernet OAM is defined. new OAM Type: Ethernet OAM is defined.
OAM Type Description OAM Type Description
------------ ------------------ ------------ ------------------
0 Reserved 0 Reserved
skipping to change at page 9, line 42 skipping to change at page 9, line 42
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 within the OAM Configuration TLV in the Configuration TLV is carried within the OAM Configuration TLV in the
LSP_ATTRIBUTES or LSP_REQUIRED_ATTRUIBUTES object in Path messages. LSP_ATTRIBUTES or LSP_REQUIRED_ATTRUIBUTES object in Path messages.
This new TLV accommodates generic Ethernet OAM information and This new TLV accommodates Ethernet OAM information and carries sub-
carries sub-TLVs. 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 ~
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: indicates a new type: the Ethernet OAM Configuration TLV. IANA Type: indicates a new type: the Ethernet OAM Configuration TLV. IANA
is requested to assigne a value from the "OAM Type sub-TLV" space in is requested to assigne a value from the "OAM Type sub-TLV" space in
the "RSVP-TE OAM Configuration Registry". the "RSVP-TE OAM Configuration Registry".
Length: indicates the total length including sub-TLVs. Length: indicates the total length including sub-TLVs.
Version: identifies the CFM protocol version according to [IEEE-CFM]. Version: identifies the CFM protocol version according to [IEEE]. If
If a node does not support a specific CFM version an error must be a node does not support a specific CFM version an error must be
generated: "OAM Problem/Unsupported OAM Version" generated: "OAM Problem/Unsupported OAM Version"
MD L. (MD Level): indicates the desired MD Level. The values are MD L. (MD Level): indicates the desired MD Level. Posible values are
according to [IEEE-CFM]. If a node does not support a specific MD defined according to [IEEE]. If a node does not support a specific
Level an error must be generated: "OAM Problem/Unsupported OAM MD Level an error must be generated: "OAM Problem/Unsupported OAM
Level". Level".
3.3.1. MD Name Sub-TLV 3.3.1. MD Name Sub-TLV
The optional MD Name sub-TLV is depicted below. The optional MD Name sub-TLV is depicted below.
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 (1) | Length | | Type (1) | Length |
skipping to change at page 10, line 52 skipping to change at page 10, line 52
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
~ MD Name ~ ~ MD Name ~
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 1, MD Name Sub-TLV. Type: 1, MD Name Sub-TLV.
Length: indicates the total length of the TLV including padding. Length: indicates the total length of the TLV including padding.
Format: according to [IEEE-CFM]. Format: according to [IEEE].
Name Length: the length of the MD Name field in bytes. This is Name Length: the length of the MD Name field in bytes. This is
necessary to allow non 4 byte padded MD Name lengths. necessary to allow non 4 byte padded MD Name lengths.
MD Name: variable length field, formatted according to the format MD Name: variable length field, formatted according to the format
specified in the Format field. specified in the Format field.
If an undefined Format is specified an error must be generated: "OAM If an undefined Format is specified an error must be generated: "OAM
Problem/Unknown MD Name Format". Also the combined length of MD Name Problem/Unknown MD Name Format". Also the combined length of MD Name
and Short MA Name must be less or equal to 44bytes, if this is and Short MA Name must be less or equal to 44bytes, if this is
violated an error must be generated: "OAM Problem/Name Length violated an error must be generated: "OAM Problem/Name Length
Problem". Note that it is allowed to have no MD Name, as such the MD Problem". Note it is allowed to have no MD Name, therefore the MD
Name sub-TLV is optional. In this case the MA Name must uniquely Name sub-TLV is optional. In this case the MA Name must uniquely
identify a Maintenance Association. identify a Maintenance Association.
3.3.2. Short MA Name Sub-TLV 3.3.2. Short MA Name Sub-TLV
The Short MA Name sub-TLV is depicted below. The Short MA Name sub-TLV is depicted below.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 11, line 39 skipping to change at page 11, line 39
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
~ Short MA Name ~ ~ Short MA Name ~
| | | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 2, Short MA Name Sub-TLV. Type: 2, Short MA Name Sub-TLV.
Length: indicates the total length of the TLV including padding. Length: indicates the total length of the TLV including padding.
Format: according to [IEEE-CFM]. Format: according to [IEEE].
Name Length: the length of the MA Name field in bytes. This is Name Length: the length of the MA Name field in bytes. This is
necessary to allow non 4 byte padded MA Name lengths. necessary to allow non 4 byte padded MA Name lengths.
Short MA Name: variable length field formatted according to the Short MA Name: variable length field formatted according to the
format specified in the Format field. format specified in the Format field.
If an undefined Format is specified an error must be generated: "OAM If an undefined Format is specified an error must be generated: "OAM
Problem/Unknown MA Name Format". Also the combined length of MD Name Problem/Unknown MA Name Format". Also the combined length of MD Name
and Short MA Name must be less or equal to 44bytes, if this is and Short MA Name must be less or equal to 44bytes, if this is
violated an error must be generated: "OAM Problem/Name Length violated an error must be generated: "OAM Problem/Name Length
Problem". Note that it is allowed to have no MD Name, in this case Problem". Note it is allowed to have no MD Name, in this case the MA
the MA Name must uniquely identify a Maintenance Association. Name must uniquely identify a Maintenance Association.
3.3.3. MEP ID Sub-TLV 3.3.3. MEP ID Sub-TLV
The MEP ID Sub-TLV is depicted below. The MEP ID Sub-TLV is depicted below.
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 (3) | Length (4) | | Type (3) | Length (4) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 13, line 9 skipping to change at page 13, line 9
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Prio | CCM I | Reserved (set to all 0s) | | Prio | CCM I | Reserved (set to all 0s) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 4, Continuity Check (CC) sub-TLV. Type: 4, Continuity Check (CC) sub-TLV.
Prio: Indicates the priority to be set for CCM frames. In Ethernet 3 Prio: Indicates the priority to be set for CCM frames. In Ethernet 3
bits carried in VLAN TAGs identify priority information. bits carried in VLAN TAGs identify priority information.
CCM I (CCM Interval): CCM Interval, according to the 3 bit encoding CCM I (CCM Interval): CCM Interval, according to the 3 bit encoding
[IEEE-CFM] shown in Table 1. If a node does not support the [IEEE] shown in Table 1. If a node does not support the requested
requested CCM Interval an error must be generated: "OAM Problem/ CCM Interval an error must be generated: "OAM Problem/Unsupported CC
Unsupported CC Interval". Interval".
3.4. Pro-active Performance Monitoring 3.4. Pro-active Performance Monitoring
Ethernet OAM functions for Performance Monitoring (PM) allow Ethernet OAM functions for Performance Monitoring (PM) allow
measurements of different performance parameters including Frame Loss measurements of different performance parameters including Frame Loss
Ratio, Frame Delay and Frame Delay variation as defined in the ITU-T Ratio, Frame Delay and Frame Delay variation as defined in the ITU-T
Y.1731 recommendation. Only a subset of PM functions are operated in Y.1731 recommendation. Only a subset of PM functions are operated in
a pro-active fashion to monitor the performance of the connection a pro-active fashion to monitor the performance of the connection
continuously. Pro-active PM supports Fault Management functions, by continuously. Pro-active PM supports Fault Management functions, by
providing an indication of decreased service performance and as such providing an indication of decreased service performance and as such
skipping to change at page 19, line 22 skipping to change at page 19, line 22
[RFC5828] "GMPLS Ethernet Label Switching Architecture and [RFC5828] "GMPLS Ethernet Label Switching Architecture and
Framework", RFC 5828, March 2010. Framework", RFC 5828, March 2010.
[RFC6060] "Generalized Multiprotocol Label Switching (GMPLS) Control [RFC6060] "Generalized Multiprotocol Label Switching (GMPLS) Control
of Ethernet Provider Backbone Traffic Engineering of Ethernet Provider Backbone Traffic Engineering
(PBB-TE)", RFC 6060. (PBB-TE)", RFC 6060.
7.2. Informative References 7.2. Informative References
[IEEE-CFM] [IEEE] "IEEE, "IEEE Standard for Local and metropolitan area
"IEEE 802.1ag, Draft Standard for Connectivity Fault networks -- Media Access Control (MAC) Bridges and Virtual
Management", work in progress. Bridged Local Area Networks", IEEE Std 802.1Q, 2011.".
[IEEE-PBBTE]
"IEEE 802.1Qay Draft Standard for Provider Backbone
Bridging Traffic Engineering", work in progress.
Authors' Addresses Authors' Addresses
Attila Takacs Attila Takacs
Ericsson Ericsson
Laborc u. 1. Konyves Kalman krt. 11.
Budapest, 1037 Budapest, 1097
Hungary Hungary
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
 End of changes. 35 change blocks. 
98 lines changed or deleted 90 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/