draft-ietf-ccamp-rsvp-te-eth-oam-ext-12.txt   draft-ietf-ccamp-rsvp-te-eth-oam-ext-13.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: October 31, 2014 H. Long Expires: January 23, 2015 H. Long
Huawei Huawei
April 29, 2014 July 22, 2014
GMPLS RSVP-TE Extensions for Ethernet OAM Configuration GMPLS RSVP-TE Extensions for Ethernet OAM Configuration
draft-ietf-ccamp-rsvp-te-eth-oam-ext-12 draft-ietf-ccamp-rsvp-te-eth-oam-ext-13
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 4 skipping to change at page 2, line 4
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 October 31, 2014. This Internet-Draft will expire on January 23, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 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 2, line 28 skipping to change at page 2, line 28
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Background . . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Background . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Overview of Ethernet OAM operation . . . . . . . . . . . . . 3 2. Overview of Ethernet OAM operation . . . . . . . . . . . . . 3
3. GMPLS RSVP-TE Extensions . . . . . . . . . . . . . . . . . . 5 3. GMPLS RSVP-TE Extensions . . . . . . . . . . . . . . . . . . 5
3.1. Operation overview . . . . . . . . . . . . . . . . . . . 5 3.1. Operation overview . . . . . . . . . . . . . . . . . . . 5
3.2. OAM Configuration TLV . . . . . . . . . . . . . . . . . . 7 3.2. OAM Configuration TLV . . . . . . . . . . . . . . . . . . 7
3.3. Ethernet OAM Configuration Sub-TLV . . . . . . . . . . . 7 3.3. Ethernet OAM Configuration Sub-TLV . . . . . . . . . . . 8
3.3.1. MD Name Sub-TLV . . . . . . . . . . . . . . . . . . . 8 3.3.1. MD Name Sub-TLV . . . . . . . . . . . . . . . . . . . 8
3.3.2. Short MA Name Sub-TLV . . . . . . . . . . . . . . . . 9 3.3.2. Short MA Name Sub-TLV . . . . . . . . . . . . . . . . 9
3.3.3. MEP ID Sub-TLV . . . . . . . . . . . . . . . . . . . 10 3.3.3. MEP ID Sub-TLV . . . . . . . . . . . . . . . . . . . 10
3.3.4. Continuity Check (CC) Sub-TLV . . . . . . . . . . . . 11 3.3.4. Continuity Check (CC) Sub-TLV . . . . . . . . . . . . 11
3.4. Pro-active Performance Monitoring . . . . . . . . . . . . 11 3.4. Pro-active Performance Monitoring . . . . . . . . . . . . 12
3.5. Summary of Ethernet OAM configuration errors . . . . . . 12 3.5. Summary of Ethernet OAM configuration errors . . . . . . 13
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
4.1. RSVP-TE OAM Configuration Registry . . . . . . . . . . . 13 4.1. RSVP-TE OAM Configuration Registry . . . . . . . . . . . 13
4.2. Ethernet Sub-TLVs Sub-Registry . . . . . . . . . . . . . 13 4.2. Ethernet Sub-TLVs Sub-Registry . . . . . . . . . . . . . 14
4.3. RSVP Error Code . . . . . . . . . . . . . . . . . . . . . 14 4.3. RSVP Error Code . . . . . . . . . . . . . . . . . . . . . 14
5. Security Considerations . . . . . . . . . . . . . . . . . . . 14 5. Security Considerations . . . . . . . . . . . . . . . . . . . 15
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 14 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 15
7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 15 7. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 15
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 15 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 16
8.1. Normative References . . . . . . . . . . . . . . . . . . 15 8.1. Normative References . . . . . . . . . . . . . . . . . . 16
8.2. Informative References . . . . . . . . . . . . . . . . . 15 8.2. Informative References . . . . . . . . . . . . . . . . . 16
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 16
1. Background 1. Background
Provider Backbone Bridging - Traffic Engineering (PBB-TE) Provider Backbone Bridging - Traffic Engineering (PBB-TE)
[IEEE.802.1Q-2011] decouples the Ethernet data and control planes, [IEEE.802.1Q-2011] decouples the Ethernet data and control planes,
and allows external control and management mechanisms to create and allows external control and management mechanisms to create
explicitly routed Ethernet connections. In addition, PBB-TE defines explicitly routed Ethernet connections. In addition, PBB-TE defines
mechanisms for protection switching of bidirectional Ethernet mechanisms for protection switching of bidirectional Ethernet
connections. Ethernet Connectivity Fault Management (CFM) defines an connections. Ethernet Connectivity Fault Management (CFM) defines an
adjunct connectivity monitoring OAM flow to check the liveliness of adjunct connectivity monitoring OAM flow to check the liveliness of
skipping to change at page 3, line 22 skipping to change at page 3, line 22
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.
The use of GMPLS RSVP-TE to support the establishment and The use of GMPLS RSVP-TE to support the establishment and
configuration of OAM entities with LSP signaling is defined in a configuration of OAM entities with LSP signaling is defined in a
technology agnostic way in [OAM-CONF-FWK]. The purpose of this technology agnostic way in [RFC7260]. The purpose of this document
document is to specify the additional technology specific OAM is to specify the additional technology specific OAM entities to
entities to support Ethernet connections. support Ethernet connections.
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 Ethernet OAM
aspects that are relevant for proactive connectivity monitoring of aspects that are relevant for proactive connectivity monitoring of
Ethernet LSPs. On-demand OAM functions for the purposes of this Ethernet LSPs. On-demand OAM functions for the purposes of this
document will be supported by Management Plane operations. document will be supported by Management Plane operations.
PBB-TE defines point-to-point Ethernet Switched Paths (ESPs) as a PBB-TE defines point-to-point Ethernet Switched Paths (ESPs) as a
provisioned traffic engineered unidirectional connectivity, provisioned traffic engineered unidirectional connectivity,
identified by the 3-tuple [ESP-MAC DA, ESP-MAC SA, ESP-VID], where identified by the 3-tuple [ESP-MAC DA, ESP-MAC SA, ESP-VID], where
the ESP-MAC DA is the destination address of the ESP, the ESP-MAC SA the ESP-MAC DA is the destination address of the ESP, the ESP-MAC SA
is the source address of the ESP, and the ESP-VID is a VLAN is the source address of the ESP, and the ESP-VID is a VLAN
identifier allocated for explicitly routed connections. To form a identifier allocated for explicitly routed connections. To form a
bidirectional PBB-TE connection, two co-routed point-to-point ESPs bidirectional PBB-TE connection, two co-routed point-to-point ESPs
are combined. The combined ESPs must have the same ESP-MAC addresses are combined. The combined ESPs must have the same ESP-MAC addresses
but may have different ESP-VIDs. but may have different ESP-VIDs. The formed co-routed bidirectional
path is a path where the forward and backward directions follow the
same route (links and nodes) across the network.
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 fully single unidirectional ESP, the Ethernet OAM mechanisms are only fully
functional when bidirectional connections are established with co- functional when bidirectional connections are established with co-
routed ESPs. Therefore, the scope of this document only covers routed ESPs. Therefore, the scope of this document only covers
bidirectional point-to-point PBB-TE connections. 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
skipping to change at page 5, line 14 skipping to change at page 5, line 19
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 Attribute Flags: "OAM MEP entities desired" and "OAM
MIP entities desired", as described in [OAM-CONF-FWK], are used to MIP entities desired", as described in [RFC7260], are used to signal
signal that the respective OAM entities must be established. An OAM that the respective OAM entities must be established. An OAM
Configuration TLV, as described in [OAM-CONF-FWK], is added to the Configuration TLV, as described in [RFC7260], is added to the
LSP_ATTRIBUTES or LSP_REQUIRED_ATTRIBUTES Objects specifying that LSP_ATTRIBUTES or LSP_REQUIRED_ATTRIBUTES Objects specifying that
Ethernet OAM is to be setup for the LSP. Ethernet OAM specific Ethernet OAM is to be setup for the LSP. Ethernet OAM specific
information, as described below, is carried in the new Ethernet OAM information, as described below, is carried in the new Ethernet OAM
Configuration Sub-TLV (see Section 3.3) within the OAM Configuration Configuration Sub-TLV (see Section 3.3) within the OAM Configuration
TLV. 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).
skipping to change at page 7, line 27 skipping to change at page 7, line 33
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, this end Once the Resv message successfully arrives to the initiator, this end
can extract the remote side's reachability information from the Label can extract the remote side's reachability information from the Label
Object and therefore it has all the information needed to properly Object and therefore it has all the information needed to properly
configure 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 [RFC7260] and is used to select which OAM
OAM technology/method should be used for the LSP. In this document, technology/method should be used for the LSP. In this document, a
a new OAM Type: Ethernet OAM is defined. IANA is requested to new OAM Type: Ethernet OAM is defined. IANA is requested to allocate
allocate OAM Type 1 for Ethernet OAM in the RSVP-TE OAM Configuration OAM Type 1 for Ethernet OAM in the RSVP-TE OAM Configuration
Registry. Registry.
RSVP-TE OAM Configuration Registry RSVP-TE OAM Configuration Registry
OAM Type Description OAM Type Description
------------ ------------------ ------------ ------------------
TBA1 Ethernet OAM TBA1 Ethernet OAM
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
skipping to change at page 8, line 29 skipping to change at page 8, line 37
"RSVP-TE OAM Configuration Registry". "RSVP-TE OAM Configuration Registry".
Length: indicates the total length of the TLV including padding and Length: indicates the total length of the TLV including padding and
including the Type and Length fields. including the Type and Length fields.
Version: identifies the CFM protocol version according to Version: identifies the CFM protocol version according to
[IEEE.802.1Q-2011]. If a node does not support a specific CFM [IEEE.802.1Q-2011]. If a node does not support a specific CFM
version an error MUST be generated: "OAM Problem/Unsupported OAM version an error MUST be generated: "OAM Problem/Unsupported OAM
Version" Version"
MD L. (MD Level): indicates the desired MD Level. Possible values MD L. (MD Level): indicates the desired MD Level. Possible values
are defined according to [IEEE.802.1Q-2011]. If a node does not are defined according to [IEEE.802.1Q-2011]. If a node does not
support a specific MD Level an error MUST be generated: "OAM Problem/ support a specific MD Level an error MUST be generated: "OAM Problem/
Unsupported MD Level". Unsupported MD Level".
3.3.1. MD Name Sub-TLV 3.3.1. MD Name Sub-TLV
The optional MD Name Sub-TLV is depicted below, it MAY be used for MD The optional MD Name Sub-TLV is depicted below, it MAY be used for MD
naming. naming.
0 1 2 3 0 1 2 3
skipping to change at page 12, line 20 skipping to change at page 12, line 48
activation together with Fault Management functions such as the activation together with Fault Management functions such as the
Continuity Check. Continuity Check.
[ITU-T.Y.1731-2011] defines dual-ended Loss Measurement as pro-active [ITU-T.Y.1731-2011] defines dual-ended Loss Measurement as pro-active
OAM for performance monitoring and as a PM function applicable to OAM for performance monitoring and as a PM function applicable to
fault management. For dual-ended Loss Measurement each MEP piggy- fault management. For dual-ended Loss Measurement each MEP piggy-
backs transmitted and received frame counters on CC messages; to backs transmitted and received frame counters on CC messages; to
support and synchronize bidirectional Loss Measurements at the MEPs. support and synchronize bidirectional Loss Measurements at the MEPs.
Dual-ended Loss Measurement is supported by setting the Performance Dual-ended Loss Measurement is supported by setting the Performance
Monitoring/Loss OAM Function Flag and the Continuity Check Flag in Monitoring/Loss OAM Function Flag and the Continuity Check Flag in
the OAM Function Flags Sub-TLV [OAM-CONF-FWK], and configuring the the OAM Function Flags Sub-TLV [RFC7260], and configuring the
Continuity Check functionality by including the Ethernet OAM Continuity Check functionality by including the Ethernet OAM
Configuration Sub-TLV. No additional configuration is required for Configuration Sub-TLV. No additional configuration is required for
this type of Loss Measurement. this type of Loss Measurement.
3.5. Summary of Ethernet OAM configuration errors 3.5. Summary of Ethernet OAM configuration errors
In addition to error values specified in [OAM-CONF-FWK] this document In addition to error values specified in [RFC7260] this document
defines the following values for the "OAM Problem" Error Code. defines the following values for the "OAM Problem" Error Code.
o If a node does not support a specific CFM version, an error MUST o If a node does not support a specific CFM version, an error MUST
be generated: "OAM Problem/Unsupported OAM Version". be generated: "OAM Problem/Unsupported OAM Version".
o If a node does not support a specific MD Level, an error MUST be o If a node does not support a specific MD Level, an error MUST be
generated: "OAM Problem/Unsupported MD Level". generated: "OAM Problem/Unsupported MD Level".
o If an undefined MD name format is specified, an error MUST be o If an undefined MD name format is specified, an error MUST be
generated: "OAM Problem/Unknown MD Name Format". generated: "OAM Problem/Unknown MD Name Format".
skipping to change at page 13, line 9 skipping to change at page 13, line 33
equal to 44bytes, if this is violated an error MUST be generated: equal to 44bytes, if this is violated an error MUST be generated:
"OAM Problem/Name Length Problem". "OAM Problem/Name Length Problem".
o If a node does not support the requested CCM Interval, an error o If a node does not support the requested CCM Interval, an error
MUST be generated: "OAM Problem/Unsupported CC Interval". MUST be generated: "OAM Problem/Unsupported CC Interval".
4. IANA Considerations 4. IANA Considerations
4.1. RSVP-TE OAM Configuration Registry 4.1. RSVP-TE OAM Configuration Registry
[OAM-CONF-FWK] includes a request for IANA to create the "RSVP-TE OAM IANA maintains the "RSVP-TE OAM Configuration Registry". IANA is
Configuration Registry". IANA is requested to assign an "OAM Type" requested to assign an "OAM Type" from this registry as follows.
from this registry as follows. Allocate the value TBA1 for "Ethernet Allocate the value TBA1 for "Ethernet OAM" from the "OAM Type Sub-
OAM" from the "OAM Type Sub-Registry" of the "RSVP-TE OAM Registry" of the "RSVP-TE OAM Configuration Registry". Allocate type
Configuration Registry". Allocate type TBA2 for the "Ethernet OAM TBA2 for the "Ethernet OAM Configuration Sub-TLV" from the
Configuration Sub-TLV" from the technology-specific range of the "OAM technology-specific range of the "OAM Sub-TLVs Sub-Registry" of the
Sub-TLVs Sub-Registry" of the "RSVP-TE OAM Configuration Registry". "RSVP-TE OAM Configuration Registry".
RSVP-TE OAM Configuration Registry RSVP-TE OAM Configuration Registry
OAM Types Sub-Registry OAM Types Sub-Registry
OAM Type Number | Description | Reference OAM Type Number | Description | Reference
------------------------------------------------- -------------------------------------------------
TBA1 | Ethernet OAM | [This.ID] TBA1 | Ethernet OAM | [This.ID]
OAM Sub-TLVs Sub-Registry OAM Sub-TLVs Sub-Registry
skipping to change at page 14, line 23 skipping to change at page 14, line 47
--------------------------------------------------- ---------------------------------------------------
0 | Reserved | [This.ID] 0 | Reserved | [This.ID]
1 | MD Name Sub-TLV | [This.ID] 1 | MD Name Sub-TLV | [This.ID]
2 | Short MA Name Sub-TLV | [This.ID] 2 | Short MA Name Sub-TLV | [This.ID]
3 | MEP ID Sub-TLV | [This.ID] 3 | MEP ID Sub-TLV | [This.ID]
4 | Continuity Check Sub-TLV | [This.ID] 4 | Continuity Check Sub-TLV | [This.ID]
5-65536 | Unassigned | [This.ID] 5-65536 | Unassigned | [This.ID]
4.3. RSVP Error Code 4.3. RSVP Error Code
[OAM-CONF-FWK] includes a request for IANA to allocate a new Error IANA maintains an Error Code, "OAM Problem" in the "Error Codes and
Code, "OAM Problem" in the "Error Codes and Globally-Defined Error Globally-Defined Error Value Sub-Codes" sub-registry of the "Resource
Value Sub-Codes" sub-registry of the "Resource Reservation Protocol Reservation Protocol (RSVP) Parameters" registry. [RFC7260] defines
(RSVP) Parameters" registry. [OAM-CONF-FWK] defines a set of Error a set of Error Value sub-codes for the "OAM Problem" Error Code.
Value sub-codes for the "OAM Problem" Error Code. This document
defines additional Error Values sub-codes for the "OAM Problem" Error This document defines additional Error Values sub-codes for the "OAM
Code as defined below. Problem" Error Code as summarized below.
Value | Description | Reference Value | Description | Reference
-------+---------------------------+-------------- -------+---------------------------+--------------
TBA | Unsupported OAM Version | [This.ID] TBA | Unsupported OAM Version | [This.ID]
TBA | Unsupported MD Level | [This.ID] TBA | Unsupported MD Level | [This.ID]
TBA | Unknown MD Name Format | [This.ID] TBA | Unknown MD Name Format | [This.ID]
TBA | Unknown MA Name Format | [This.ID] TBA | Unknown MA Name Format | [This.ID]
TBA | Name Length Problem | [This.ID] TBA | Name Length Problem | [This.ID]
TBA | Unsupported CC Interval | [This.ID] TBA | Unsupported CC Interval | [This.ID]
5. Security Considerations 5. Security Considerations
This document does not introduce any additional security issue to This document does not introduce any additional security issue to
those discussed in [OAM-CONF-FWK] and [RFC6060]. those discussed in [RFC7260] and [RFC6060].
The signaling of OAM-related parameters and the automatic
establishment of OAM entities based on RSVP-TE messages add a new
aspect to the security considerations discussed in [RFC3473]. In
particular, a network element could be overloaded if a remote
attacker targeted that element by sending frequent periodic messages
requesting liveliness monitoring of a high number of LSPs. Such an
attack can efficiently be prevented when mechanisms for message
integrity and node authentication are deployed. Since the OAM
configuration extensions rely on the hop-by-hop exchange of exiting
RSVP-TE messages, procedures specified for RSVP message security in
[RFC2747] can be used to mitigate possible attacks.
For a more comprehensive discussion of GMPLS security and attack
mitigation techniques, please see the Security Framework for MPLS and
GMPLS Networks [RFC5920].
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.
7. Contributors 7. Contributors
- Don Fedyk, don.fedyk@hp.com - Don Fedyk, don.fedyk@hp.com
skipping to change at page 15, line 19 skipping to change at page 16, line 14
8. References 8. References
8.1. Normative References 8.1. Normative References
[IEEE.802.1Q-2011] [IEEE.802.1Q-2011]
IEEE, "IEEE Standard for Local and metropolitan area IEEE, "IEEE Standard for Local and metropolitan area
networks -- Media Access Control (MAC) Bridges and Virtual networks -- Media Access Control (MAC) Bridges and Virtual
Bridged Local Area Networks", IEEE Std 802.1Q, 2011. Bridged Local Area Networks", IEEE Std 802.1Q, 2011.
[OAM-CONF-FWK]
Attila Takacs, Don Fedyk, and Jia He, "GMPLS RSVP-TE
extensions for OAM Configuration", Internet Draft, work in
progress, 2014.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC6060] Fedyk, D., Shah, H., Bitar, N., and A. Takacs, [RFC6060] Fedyk, D., Shah, H., Bitar, N., and A. Takacs,
"Generalized Multiprotocol Label Switching (GMPLS) Control "Generalized Multiprotocol Label Switching (GMPLS) Control
of Ethernet Provider Backbone Traffic Engineering (PBB- of Ethernet Provider Backbone Traffic Engineering (PBB-
TE)", RFC 6060, March 2011. TE)", RFC 6060, March 2011.
[RFC7260] Takacs, A., Fedyk, D., and J. He, "GMPLS RSVP-TE
Extensions for Operations, Administration, and Maintenance
(OAM) Configuration", RFC 7260, June 2014.
8.2. Informative References 8.2. Informative References
[ITU-T.Y.1731-2011] [ITU-T.Y.1731-2011]
ITU, "ITU-T Recommendation Y.1731: OAM functions and ITU, "ITU-T Recommendation Y.1731: OAM functions and
mechanisms for Ethernet based networks", ITU-T mechanisms for Ethernet based networks", ITU-T
Recommendation Y.1731, 2011. Recommendation Y.1731, 2011.
[RFC2747] Baker, F., Lindell, B., and M. Talwar, "RSVP Cryptographic
Authentication", RFC 2747, January 2000.
[RFC3473] Berger, L., "Generalized Multi-Protocol Label Switching
(GMPLS) Signaling Resource ReserVation Protocol-Traffic
Engineering (RSVP-TE) Extensions", RFC 3473, January 2003.
[RFC5828] Fedyk, D., Berger, L., and L. Andersson, "Generalized [RFC5828] Fedyk, D., Berger, L., and L. Andersson, "Generalized
Multiprotocol Label Switching (GMPLS) Ethernet Label Multiprotocol Label Switching (GMPLS) Ethernet Label
Switching Architecture and Framework", RFC 5828, March Switching Architecture and Framework", RFC 5828, March
2010. 2010.
Authors' Addresses [RFC5920] Fang, L., "Security Framework for MPLS and GMPLS
Networks", RFC 5920, July 2010.
Authors' Addresses
Attila Takacs Attila Takacs
Ericsson Ericsson
Konyves Kalman krt. 11. Konyves Kalman krt. 11.
Budapest 1097 Budapest 1097
Hungary Hungary
Email: attila.takacs@ericsson.com Email: attila.takacs@ericsson.com
Balazs Peter Gero Balazs Peter Gero
Ericsson Ericsson
Konyves Kalman krt. 11. Konyves Kalman krt. 11.
Budapest 1097 Budapest 1097
Hungary Hungary
Email: balazs.peter.gero@ericsson.com Email: balazs.peter.gero@ericsson.com
Hao Long Hao Long
Huawei Huawei
skipping to change at page 16, line 14 skipping to change at page 17, line 22
Balazs Peter Gero Balazs Peter Gero
Ericsson Ericsson
Konyves Kalman krt. 11. Konyves Kalman krt. 11.
Budapest 1097 Budapest 1097
Hungary Hungary
Email: balazs.peter.gero@ericsson.com Email: balazs.peter.gero@ericsson.com
Hao Long Hao Long
Huawei Huawei
PR China
Email: lonho@huawei.com Email: lonho@huawei.com
 End of changes. 26 change blocks. 
50 lines changed or deleted 78 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/