draft-ietf-ccamp-gmpls-ether-svcs-03.txt   draft-ietf-ccamp-gmpls-ether-svcs-04.txt 
Internet Draft Lou Berger (LabN) Internet Draft Lou Berger (LabN)
Category: Standards Track Don Fedyk (Nortel) Category: Standards Track Don Fedyk (Alcatel-Lucent)
Expiration Date: August 25, 2009 Expiration Date: April 14, 2010
February 25, 2009 October 14, 2009
Generalized MPLS (GMPLS) Support For Metro Ethernet Forum Generalized MPLS (GMPLS) Support For Metro Ethernet Forum
and G.8011 Ethernet Service Switching and G.8011 Ethernet Service Switching
draft-ietf-ccamp-gmpls-ether-svcs-03.txt draft-ietf-ccamp-gmpls-ether-svcs-04.txt
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.
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware 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 have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with BCP 78 and BCP 79. aware will be disclosed, in accordance with BCP 78 and BCP 79.
skipping to change at page 1, line 39 skipping to change at page 1, line 39
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/1id-abstracts.html http://www.ietf.org/1id-abstracts.html
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 August 25, 2009. This Internet-Draft will expire on April 14, 2010.
Copyright and License Notice Copyright and License 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.
Abstract Abstract
This document describes a method for controlling two specific types This document describes a method for controlling two specific types
of Ethernet switching via Generalized Multi-Protocol Label Switching of Ethernet switching via Generalized Multi-Protocol Label Switching
(GMPLS). This document supports the types of switching implied by (GMPLS). This document supports the types of switching corresponding
the Ethernet services that have been defined in the context of the to the Ethernet services that have been defined in the context of the
Metro Ethernet Forum (MEF) and International Telecommunication Union Metro Ethernet Forum (MEF) and International Telecommunication Union
(ITU) G.8011. Specifically, switching in support of Ethernet private (ITU) G.8011. Specifically, switching in support of Ethernet private
line and Ethernet virtual private line services. Support for MEF and line and Ethernet virtual private line services are covered. Support
ITU defined parameters are also covered. for MEF and ITU defined parameters is also covered.
Table of Contents Table of Contents
1 Introduction ........................................... 3 1 Introduction ........................................... 3
1.1 Overview ............................................... 3 1.1 Overview ............................................... 3
1.2 Conventions used in this document ...................... 5 1.2 Conventions used in this document ...................... 5
2 Common Signaling Support ............................... 5 2 Common Signaling Support ............................... 5
2.1 Ethernet Endpoint Identification ....................... 5 2.1 Ethernet Endpoint Identification ....................... 5
2.1.1 Endpoint ID TLV ........................................ 6 2.1.1 Endpoint ID TLV ........................................ 6
2.2 Connection Identification .............................. 6 2.2 Connection Identification .............................. 6
skipping to change at page 3, line 33 skipping to change at page 3, line 33
document defines the GMPLS extensions needed to support such document defines the GMPLS extensions needed to support such
switching, but does not define the UNI or External NNI (E-NNI) switching, but does not define the UNI or External NNI (E-NNI)
reference points. See [GMPLS-MEF-UNI] for a description of the UNI reference points. See [GMPLS-MEF-UNI] for a description of the UNI
reference point. This document makes use of the traffic parameters reference point. This document makes use of the traffic parameters
defined in [ETH-TRAFFIC] and the generic extensions defined in defined in [ETH-TRAFFIC] and the generic extensions defined in
[GMPLS-EXT]. [GMPLS-EXT].
1.1. Overview 1.1. Overview
This document uses a common approach to supporting the switching This document uses a common approach to supporting the switching
implied by the Ethernet services defined in [MEF6], [G.8011.1] and corresponding to the Ethernet services defined in [MEF6], [G.8011.1]
[G.8011.2]. The approach builds on standard GMPLS mechanisms to and [G.8011.2]. The approach builds on standard GMPLS mechanisms to
deliver the required control capabilities. This document reuses the deliver the required control capabilities. This document reuses the
GMPLS mechanisms specified in [RFC3473] and [RFC4974]. The document GMPLS mechanisms specified in [RFC3473] and [RFC4974]. The document
uses the extensions defined in [GMPLS-EXT]. uses the extensions defined in [GMPLS-EXT].
Two types of connectivity between Ethernet endpoints are defined in Two types of connectivity between Ethernet endpoints are defined in
[MEF6] and [G.8011]: point-to-point (P2P) and multipoint-to- [MEF6] and [G.8011]: point-to-point (P2P) and multipoint-to-
multipoint (MP2MP). [MEF6] uses the term Ethernet Line (E-line) to multipoint (MP2MP). [MEF6] uses the term Ethernet Line (E-line) to
refer to point-to-point virtual connections, and Ethernet LAN (E-LAN) refer to point-to-point virtual connections, and Ethernet LAN (E-LAN)
to refer to multipoint-to-multipoint virtual connections. [G.8011] to refer to multipoint-to-multipoint virtual connections. [G.8011]
also identifies point-to-multipoint (P2MP) as an area for "further also identifies point-to-multipoint (P2MP) as an area for "further
study." Within the context of GMPLS, support is defined for point- study." Within the context of GMPLS, support is defined for point-
to-point unidirectional and bidirectional TE Label Switched Paths to-point unidirectional and bidirectional TE Label Switched Paths
(LSPs), see [RFC3473], and unidirectional point-to-multipoint TE (LSPs), see [RFC3473], and unidirectional point-to-multipoint TE
LSPs, see [RFC4875]. LSPs, see [RFC4875].
Support for P2P and MP2MP services is required by [G.8011] and Support for P2P and MP2MP services is defined by [G.8011] and
required by [MEF11]. Note that while [MEF11] and [G.8011] discuss
[MEF11]. Note that while [MEF11] requires MP2MP, [G.8011.1] and MP2MP, [G.8011.1] and [G.8011.2] only define support for P2P. There
[G.8011.2] only require P2P. There is a clear correspondence between is a clear correspondence between E-Line/P2P service and GMPLS P2P TE
E-Line/P2P service and GMPLS P2P TE LSPs, and support for such LSPs LSPs, and support for such LSPs is included in the scope of this
are included in the scope of this document. There is no such clear document. There is no such clear correspondence between E-LAN/MP2MP
correspondence between E-LAN/MP2MP service and GMPLS TE LSPs. service and GMPLS TE LSPs. Although, it is possible to emulate this
Although it is possible to emulate the service using multiple P2P or service using multiple P2P or P2MP TE LSPs, the definition of support
P2MP TE LSPs. The definition of support for MP2MP service is left for MP2MP service is left for future study and is not addressed in
for future study and is not addressed in this document. this document.
[MEF11] defines multiple types of control for UNI Ethernet services. [MEF11] defines multiple types of control for UNI Ethernet services.
In MEF UNI Type 1, services are configured manually. In MEF UNI Type In MEF UNI Type 1, services are configured manually. In MEF UNI Type
2, services may be configured manually or via a link management 2, services may be configured manually or via a link management
interface. In MEF UNI Type 3, services may be established and interface. In MEF UNI Type 3, services may be established and
managed via a signaling interface. From the MEF perspective, this managed via a signaling interface. From the MEF perspective, this
document along with [GMPLS-MEF-UNI] are aimed at the network control document along with [GMPLS-MEF-UNI] is aimed at the network control
needed to support the MEF UNI Type 3 mode of operation. needed to support the MEF UNI Type 3 mode of operation.
[G.8011.1], [G.8011.2] and [MEF11] together with [MEF10.1] define a [G.8011.1], [G.8011.2] and [MEF11] together with [MEF10.1] define a
set of service attributes that are associated with each Ethernet set of service attributes that are associated with each Ethernet
connection. Some of these attributes are based on the provisioning connection. Some of these attributes are based on the provisioning
of the local physical connection and are not modifiable or selectable of the local physical connection and are not modifiable or selectable
per connection. Other attributes are specific to a particular per connection. Other attributes are specific to a particular
connection, or must be consistent across the connection. The connection, or must be consistent across the connection. The
approach taken in this document to communicate these attributes is to approach taken in this document to communicate these attributes is to
exclude the static class of attributes from signaling. This class of exclude the static class of attributes from signaling. This class of
attributes will not be explicitly discussed in this document. The attributes will not be explicitly discussed in this document. The
other class of attributes are communicated via signaling and will be other class of attributes is communicated via signaling and will be
reviewed in the sections below. The major attributes that will be reviewed in the sections below. The major attributes that will be
supported in signaling include: supported in signaling include:
- Endpoint identifiers - Endpoint identifiers
- Connection identifiers - Connection identifiers
- Traffic parameters (see [ETH-TRAFFIC]) - Traffic parameters (see [ETH-TRAFFIC])
- Bundling / VLAN IDs map (EVPL only) - Bundling / VLAN IDs map (EVPL only)
- VLAN ID Preservation (EVPL only) - VLAN ID Preservation (EVPL only)
Common procedures used to support Ethernet LSPs are described in Common procedures used to support Ethernet LSPs are described in
Section 2 of this document. Procedures related to signaling Section 2 of this document. Procedures related to the signaling of
switching in support of EPL services are described in Section 3. switching in support of EPL services are described in Section 3.
Procedures related to signaling switching in support of EVPL services Procedures related to the signaling of switching in support of EVPL
are described in Section 4. services are described in Section 4.
1.2. Conventions used in this document 1.2. Conventions used in this document
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 [RFC2119]. document are to be interpreted as described in [RFC2119].
2. Common Signaling Support 2. Common Signaling Support
This section describes the common mechanisms for supporting GMPLS This section describes the common mechanisms for supporting GMPLS
skipping to change at page 5, line 28 skipping to change at page 5, line 28
related to the processing of RSVP objects are not modified by this related to the processing of RSVP objects are not modified by this
document. The relevant procedures in existing documents, such as document. The relevant procedures in existing documents, such as
[RFC3473], MUST be followed in all cases not explicitly described in [RFC3473], MUST be followed in all cases not explicitly described in
this document. this document.
2.1. Ethernet Endpoint Identification 2.1. Ethernet Endpoint Identification
Ethernet endpoint identifiers, as they are defined in [G.8011] and Ethernet endpoint identifiers, as they are defined in [G.8011] and
[MEF10.1], differ significantly from the identifiers used by GMPLS. [MEF10.1], differ significantly from the identifiers used by GMPLS.
Specifically, the Ethernet endpoint identifiers are character based Specifically, the Ethernet endpoint identifiers are character based
as apposed to the GMPLS norm of being IP address based. as opposed to the GMPLS norm of being IP address based.
The approach taken by this document to address this disparity The approach taken by this document to address this disparity
leverages the solution used for connection identification, see leverages the solution used for connection identification, see
Section 2.2 and [RFC4974], and a new CALL_ATTRIBUTES TLV defined in Section 2.2 and [RFC4974], and a new CALL_ATTRIBUTES TLV defined in
this document. The solution makes use of the [RFC4974] short call this document. The solution makes use of the [RFC4974] short call
ID, and supports the Ethernet endpoint identifier much like [RFC4974] ID, and supports the Ethernet endpoint identifier similar to
supports the long call ID. That is, the SENDER_TEMPLATE and SESSION [RFC4974] supports the long call ID. That is, the SENDER_TEMPLATE
objects carry IP addresses and a short call ID, and long identifiers and SESSION objects carry IP addresses and a short call ID, and long
are carried in the CALL_ATTRIBUTES object. As with the long call ID, identifiers are carried in the CALL_ATTRIBUTES object. As with the
the Ethernet endpoint identifier is typically only relevant at the long call ID, the Ethernet endpoint identifier is typically only
ingress and egress nodes. relevant at the ingress and egress nodes.
As defined below, the Ethernet endpoint identifier is carried in the As defined below, the Ethernet endpoint identifier is carried in the
CALL_ATTRIBUTES object in a new TLV. The new TLV is referred to as CALL_ATTRIBUTES object in a new TLV. The new TLV is referred to as
the Endpoint ID TLV. The processing of the Endpoint ID TLV parallels the Endpoint ID TLV. The processing of the Endpoint ID TLV parallels
the processing of the long call ID in [RFC4974]. This processing the processing of the long call ID in [RFC4974]. This processing
requires the inclusion of the CALL_ATTRIBUTES object in a Notify requires the inclusion of the CALL_ATTRIBUTES object in a Notify
message. message.
2.1.1. Endpoint ID TLV 2.1.1. Endpoint ID TLV
skipping to change at page 6, line 43 skipping to change at page 6, line 43
CALL_ATTRIBUTES object containing an Endpoint ID TLV MUST be included CALL_ATTRIBUTES object containing an Endpoint ID TLV MUST be included
in the Notify message along with the Long Call ID. in the Notify message along with the Long Call ID.
Short Call ID processing, including those procedures related to call Short Call ID processing, including those procedures related to call
and connection processing, is not modified by this document and MUST and connection processing, is not modified by this document and MUST
proceed according to [RFC4974]. proceed according to [RFC4974].
2.2. Connection Identification 2.2. Connection Identification
Signaling for Ethernet connections follows the procedures defined in Signaling for Ethernet connections follows the procedures defined in
[RFC4974]. In particular the Call related mechanisms are reused to [RFC4974]. In particular the Call related mechanisms are used to
support endpoint identification. In the context of Ethernet support endpoint identification. In the context of Ethernet
connections, a call only is only established when one or more LSPs connections, a call is only established when one or more LSPs
(connections in [RFC4974] terms) are needed. An LSP will always be (connections in [RFC4974] terms) are needed. An LSP will always be
established within the context of a call and, typically, only one LSP established within the context of a call and, typically, only one LSP
will be used per call. See Section 4.4 for the case where more than will be used per call. See Section 4.4 for the case where more than
one LSP may exist within a call. one LSP may exist within a call.
2.2.1. Procedures 2.2.1. Procedures
Any node that supports Ethernet connections MUST be able to accept Any node that supports Ethernet connections MUST be able to accept
and process call setups per [RFC4974]. Ethernet connections and process call setups per [RFC4974]. Ethernet connections
established according to this document MUST treat the Ethernet established according to this document MUST treat the Ethernet
(virtual) connection identifier as the long "Call identifier (ID)", (virtual) connection identifier as the long "Call identifier (ID)",
described in [RFC4974]. The short Call ID MUST be used as described described in [RFC4974]. The short Call ID MUST be used as described
in [RFC4974]. Use of the LINK_CAPABILITY object is OPTIONAL. Both in [RFC4974]. Use of the LINK_CAPABILITY object is OPTIONAL. Both
network-initiated and user-initiated Calls MUST be supported. network-initiated and user-initiated Calls MUST be supported.
When establishing an Ethernet connection the initiator MUST first When establishing an Ethernet connection the initiator MUST first
establish a Call per the procedures defined in [RFC4974]. LSP establish a Call per the procedures defined in [RFC4974]. LSP
management, including removal and addition, then follows [RFC4974]. management, including removal and addition, then follows [RFC4974].
As stated in [RFC4974], once a Call is established the initiator As stated in [RFC4974], once a Call is established, the initiator
SHOULD establish at least one Ethernet LSP. Also, when the last LSP SHOULD establish at least one Ethernet LSP. Also, when the last LSP
associated with a Call is removed, the Call SHOULD be torn down per associated with a Call is removed, the Call SHOULD be torn down per
the procedures in [RFC4974]. the procedures in [RFC4974].
2.3. Traffic Parameters 2.3. Traffic Parameters
Several types of service attributes are carried in the traffic Several types of service attributes are carried in the traffic
parameters defined in [ETH-TRAFFIC]. These parameters are carried in parameters defined in [ETH-TRAFFIC]. These parameters are carried in
the FLOWSPEC and TSPEC objects as discussed in [ETH-TRAFFIC]. The the FLOWSPEC and TSPEC objects as discussed in [ETH-TRAFFIC]. The
service attributes that are carried are: service attributes that are carried are:
skipping to change at page 11, line 33 skipping to change at page 11, line 33
This field is reserved. It MUST be set to zero on transmission This field is reserved. It MUST be set to zero on transmission
and MUST be ignored on receipt. This field SHOULD be passed and MUST be ignored on receipt. This field SHOULD be passed
unmodified by transit nodes. unmodified by transit nodes.
VLAN ID: 12 bits VLAN ID: 12 bits
A VLAN identifier. A VLAN identifier.
4.2. Egress VLAN ID Control and VLAN ID preservation 4.2. Egress VLAN ID Control and VLAN ID preservation
When an EVPL service does not support both bundling and VLAN ID When an EVPL service is not configured for both bundling and VLAN ID
preservation, [MEF6] allows VLAN ID mapping. In particular, the preservation, [MEF6] allows VLAN ID mapping. In particular, the
single VLAN ID used at the incoming interface of the ingress may be single VLAN ID used at the incoming interface of the ingress may be
mapped to a different VLAN ID at the outgoing interface at the egress mapped to a different VLAN ID at the outgoing interface at the egress
UNI. Such mapping MUST be requested and signaled based on the UNI. Such mapping MUST be requested and signaled based on the
explicit label control mechanism defined in [RFC3473] and clarified explicit label control mechanism defined in [RFC3473] and clarified
in [RFC4003]. in [RFC4003].
When the explicit label control mechanism is not used, VLAN IDs MUST When the explicit label control mechanism is not used, VLAN IDs MUST
be preserved, i.e., not modified, across an LSP. be preserved, i.e., not modified, across an LSP.
skipping to change at page 12, line 37 skipping to change at page 12, line 37
IDs MAY be added to the EVPL connection using either a new LSP or IDs MAY be added to the EVPL connection using either a new LSP or
make-before-break procedures, see [RFC3209]. Make-before-break make-before-break procedures, see [RFC3209]. Make-before-break
procedures on individual LSPs SHOULD be used to remove VLAN IDs. procedures on individual LSPs SHOULD be used to remove VLAN IDs.
To change other service parameters it is necessary to resignal all To change other service parameters it is necessary to resignal all
LSPs associated with the call via make-before-break procedures. LSPs associated with the call via make-before-break procedures.
5. IANA Considerations 5. IANA Considerations
IANA is requested to administer assignment of new values for IANA is requested to administer assignment of new values for
namespaces defined in this document and reviewed in this section. namespaces defined in this document and summarized in this section.
5.1. Endpoint ID Attributes TLV 5.1. Endpoint ID Attributes TLV
Upon approval of this document, the IANA will make the assignment in Upon approval of this document, IANA will make the assignment in the
the "CALL_ATTRIBUTES TLV Space" section of the "RSVP TE Parameters" "CALL_ATTRIBUTES TLV Space" section of the "RSVP TE Parameters"
registry located at http://www.iana.org/assignments/rsvp-te- registry located at http://www.iana.org/assignments/rsvp-te-
parameters: parameters:
Type Name Reference Type Name Reference
---- ----------- --------- ---- ----------- ---------
2* Endpoint ID [This document] 2* Endpoint ID [This document]
(*) Suggested value. (*) Suggested value.
5.2. Line LSP Encoding 5.2. Line LSP Encoding
Upon approval of this document, the IANA will make the assignment in Upon approval of this document, IANA will make the assignment in the
the "LSP Encoding Types" section of the "GMPLS Signaling Parameters" "LSP Encoding Types" section of the "GMPLS Signaling Parameters"
registry located at http://www.iana.org/assignments/gmpls-sig- registry located at http://www.iana.org/assignments/gmpls-sig-
parameters: parameters:
Value Type Reference Value Type Reference
----- --------------------------- --------- ----- --------------------------- ---------
14* Line (e.g., 8B/10B) [This document] 14* Line (e.g., 8B/10B) [This document]
(*) Suggested value. (*) Suggested value.
5.3. Ethernet Virtual Private Line (EVPL) Switching Type 5.3. Ethernet Virtual Private Line (EVPL) Switching Type
Upon approval of this document, the IANA will make the assignment in Upon approval of this document, IANA will make the assignment in the
the "Switching Types" section of the "GMPLS Signaling Parameters" "Switching Types" section of the "GMPLS Signaling Parameters"
registry located at http://www.iana.org/assignments/gmpls-sig- registry located at http://www.iana.org/assignments/gmpls-sig-
parameters: parameters:
Value Type Reference Value Type Reference
----- --------------------------- --------- ----- --------------------------- ---------
30* Ethernet Virtual Private Line (EVPL) [This document] 30* Ethernet Virtual Private Line (EVPL) [This document]
(*) Suggested value. (*) Suggested value.
It should be noted that the assigned value should be reflected in It should be noted that the assigned value should be reflected in
skipping to change at page 14, line 10 skipping to change at page 14, line 10
messages, nor change the relationship between LSRs that are adjacent messages, nor change the relationship between LSRs that are adjacent
in the control plane. As such, this document introduces no additional in the control plane. As such, this document introduces no additional
security considerations. See [RFC3473] for relevant security security considerations. See [RFC3473] for relevant security
considerations. considerations.
7. References 7. References
7.1. Normative References 7.1. Normative References
[ETH-TRAFFIC] Papadimitriou, D., "Ethernet Traffic Parameters," [ETH-TRAFFIC] Papadimitriou, D., "Ethernet Traffic Parameters,"
draft-ietf-ccamp-ethernet-traffic-parameters-06.txt, draft-ietf-ccamp-ethernet-traffic-parameters,
Work in progress, October 31, 2008. Work in progress.
[GMPLS-EXT] Berger, L., Papadimitriou, P., Fedyk, D., [GMPLS-EXT] Berger, L., Fedyk, D., "Generalized MPLS (GMPLS) Data
"Generalized MPLS (GMPLS) Data Channel Switching Channel Switching Capable (DCSC) and Channel Set
Capable (DCSC) and Channel Set Label Extensions", Label Extensions",
draft-ietf-ccamp-gmpls-dcsc-channel-ext-00.txt, draft-ietf-ccamp-gmpls-dcsc-channel-ext, Work in
Work in Progress, August 2008. Progres.
[GMPLS-MRN] Papadimitriou, D. et al, "Generalized Multi-Protocol [GMPLS-MRN] Papadimitriou, D. et al, "Generalized Multi-Protocol
Label Switching (GMPLS) Protocol Extensions for Label Switching (GMPLS) Protocol Extensions for
Multi-Layer and Multi-Region Networks (MLN/MRN)", Multi-Layer and Multi-Region Networks (MLN/MRN)",
draft-ietf-ccamp-gmpls-mln-extensions-03.txt, draft-ietf-ccamp-gmpls-mln-extensions,
Work in progress, October 2008. Work in progress.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels," RFC 2119. Requirement Levels," RFC 2119.
[RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T.,
Srinivasan, V. and G. Swallow, "RSVP-TE: Extensions Srinivasan, V. and G. Swallow, "RSVP-TE: Extensions
to RSVP for LSP Tunnels", RFC 3209, December 2001. to RSVP for LSP Tunnels", RFC 3209, December 2001.
[RFC3471] Berger, L., Editor, "Generalized Multi-Protocol Label [RFC3471] Berger, L., Editor, "Generalized Multi-Protocol Label
Switching (GMPLS) Signaling Functional Description", Switching (GMPLS) Signaling Functional Description",
skipping to change at page 15, line 16 skipping to change at page 15, line 16
[G.8011] ITU-T G.8011/Y.1307, "Ethernet over Transport [G.8011] ITU-T G.8011/Y.1307, "Ethernet over Transport
Ethernet services framework", August 2004. Ethernet services framework", August 2004.
[G.8011.1] ITU-T G.G.8011.1/Y.1307.1, "Ethernet private [G.8011.1] ITU-T G.G.8011.1/Y.1307.1, "Ethernet private
line service", August 2004. line service", August 2004.
[G.8011.2] ITU-T G.8011.2/Y.1307.2, "Ethernet virtual [G.8011.2] ITU-T G.8011.2/Y.1307.2, "Ethernet virtual
private line service", September 2005. private line service", September 2005.
[GMPLS-MEF-UNI] Berger, L., Papadimitriou, P., Fedyk, D., [GMPLS-MEF-UNI] Berger, L., Fedyk, D., "Generalized MPLS (GMPLS)
"Generalized MPLS (GMPLS) Support For Metro Support For Metro Ethernet Forum and G.8011
Ethernet Forum and G.8011 User-Network Interface User-Network Interface (UNI)",
(UNI)", Work in Progress, draft-ietf-ccamp-gmpls-mef-uni, Work in Progress.
draft-ietf-ccamp-gmpls-mef-uni-01.txt,
August 2008.
[MEF6] The Metro Ethernet Forum, "Ethernet Services [MEF6] The Metro Ethernet Forum, "Ethernet Services
Definitions - Phase I", MEF 6, June 2004 Definitions - Phase I", MEF 6, June 2004
[MEF10.1] The Metro Ethernet Forum, "Ethernet Services [MEF10.1] The Metro Ethernet Forum, "Ethernet Services
Attributes Phase 2", MEF 10.1, November 2006. Attributes Phase 2", MEF 10.1, November 2006.
[MEF11] The Metro Ethernet Forum , "User Network [MEF11] The Metro Ethernet Forum , "User Network
Interface (UNI) Requirements and Framework", Interface (UNI) Requirements and Framework",
MEF 11, November 2004. MEF 11, November 2004.
skipping to change at page 16, line 13 skipping to change at page 16, line 13
Cohen for their valuable comments. Cohen for their valuable comments.
9. Author's Addresses 9. Author's Addresses
Lou Berger Lou Berger
LabN Consulting, L.L.C. LabN Consulting, L.L.C.
Phone: +1-301-468-9228 Phone: +1-301-468-9228
Email: lberger@labn.net Email: lberger@labn.net
Don Fedyk Don Fedyk
Nortel Networks Alcatel-Lucent
600 Technology Park Drive Groton, MA, 01450
Billerica, MA, 01821 Phone: +1-978-467-5645
Phone: +1-978-288-3041 Email: donald.fedyk@alcatel-lucent.com
Email: dwfedyk@nortel.com
Generated on: Wed Feb 25 20:00:02 EST 2009 Generated on: Wed Oct 14 14:47:45 EDT 2009
 End of changes. 29 change blocks. 
69 lines changed or deleted 65 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/