draft-ietf-ccamp-gmpls-mef-uni-00.txt   draft-ietf-ccamp-gmpls-mef-uni-01.txt 
Internet Draft Lou Berger (LabN) Internet Draft Lou Berger (LabN)
Category: Standards Track Category: Standards Track Don Fedyk (Nortel)
Expiration Date: October 14, 2008 Don Fedyk (Nortel) Expiration Date: February 8, 2009
April 14, 2008 August 8, 2008
Generalized MPLS (GMPLS) Support For Metro Ethernet Forum Generalized MPLS (GMPLS) Support For Metro Ethernet Forum
and G.8011 User-Network Interface (UNI) and G.8011 User-Network Interface (UNI)
draft-ietf-ccamp-gmpls-mef-uni-00.txt draft-ietf-ccamp-gmpls-mef-uni-01.txt
Status of this Memo Status of this Memo
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 Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 36 skipping to change at page 1, line 36
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 October 14, 2008. This Internet-Draft will expire on February 8, 2009.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2008). Copyright (C) The IETF Trust (2008).
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 a Generalized Multi-Protocol Label of Ethernet switching via a Generalized Multi-Protocol Label
Switching (GMPLS) based User-Network Interface (UNI). This document Switching (GMPLS) based User-Network Interface (UNI). This document
skipping to change at page 3, line 22 skipping to change at page 3, line 22
Ethernet Private Line (EPL) service and [G.8011.2] defines the Ethernet Private Line (EPL) service and [G.8011.2] defines the
Ethernet Virtual Private Line (EVPL) service. [MEF6] covers both Ethernet Virtual Private Line (EVPL) service. [MEF6] covers both
service types. [MEF10.1] defines service parameters and [MEF11] service types. [MEF10.1] defines service parameters and [MEF11]
provides UNI requirements and framework. provides UNI requirements and framework.
This document provides a method for GMPLS based control of LSPs that This document provides a method for GMPLS based control of LSPs that
support the transport services defined in the above documents at the support the transport services defined in the above documents at the
UNI network reference points. This document does not define or limit UNI network reference points. This document does not define or limit
the underlying intra-domain or Internal NNI (I-NNI) technology used the underlying intra-domain or Internal NNI (I-NNI) technology used
to support the UNI. This document makes use of the GMPLS extensions to support the UNI. This document makes use of the GMPLS extensions
defined in [GMPLS-ESVCS]. defined in [GMPLS-ESVCS] and [GMPLS-EXT].
The scope of this document covers Ethernet UNI applications, and it The scope of this document covers Ethernet UNI applications, and it
is intended to be consistent with the GMPLS overlay model presented is intended to be consistent with the GMPLS overlay model presented
in [RFC4208] and aligned with GMPLS Core Network signaling. The in [RFC4208] and aligned with GMPLS Core Network signaling. The
scope and reference model used in this document are represented in scope and reference model used in this document are represented in
Figure 1, which is based on Figure 1 of [RFC4208]. Figure 1, which is based on Figure 1 of [RFC4208].
Figure 1 shows two core networks, each containing two core-nodes. Figure 1 shows two core networks, each containing two core-nodes.
The core-nodes are labeled 'CN'. Connected to each CN is an edge- The core-nodes are labeled 'CN'. Connected to each CN is an edge-
node. The edge-nodes are labeled 'EN'. Each EN supports Ethernet node. The edge-nodes are labeled 'EN'. Each EN supports Ethernet
skipping to change at page 4, line 36 skipping to change at page 4, line 36
Network <-----> <-----> Network Network <-----> <-----> Network
Scope of this Document Scope of this Document
Legend: EN - Edge Node Legend: EN - Edge Node
CN - Core Node CN - Core Node
Figure 1: Ethernet UNI Reference Model Figure 1: Ethernet UNI Reference Model
1.1. Overview 1.1. Overview
This document uses a largely common approach to supporting the This document uses a common approach to supporting the switching
switching implied by the Ethernet services defined in [MEF6], implied by the Ethernet services defined in [MEF6], [G.8011.1] and
[G.8011.1] and [G.8011.2]. The approach builds on standard GMPLS [G.8011.2]. The approach builds on standard GMPLS mechanisms to
mechanisms to deliver the required control capabilities. This deliver the required control capabilities. This document reuses the
document reuses the GMPLS mechanisms specified in [GMPLS-ESVCS], GMPLS mechanisms specified in [GMPLS-ESVCS], [RFC4208], and
[RFC4208], and [RFC4974]. [RFC4974].
Support for P2P and MP2MP service is required by [G.8011] and Support for P2P and MP2MP service is required by [G.8011] and
[MEF11]. P2P service delivery support is based on the GMPLS support [MEF11]. P2P service delivery support is based on the GMPLS support
for Ethernet Services covered in [GMPLS-ESVCS]. As with [GMPLS- for Ethernet Services covered in [GMPLS-ESVCS]. As with [GMPLS-
ESVCS], the definition of support for MP2MP service is left for ESVCS], the definition of support for MP2MP service is left for
future study and is not addressed in this document. future study and is not addressed in 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
skipping to change at page 5, line 31 skipping to change at page 5, line 31
2. Common Signaling Support 2. Common Signaling Support
This section describes the common mechanisms for supporting a UNI This section describes the common mechanisms for supporting a UNI
reference point for LSPs that provide the Ethernet Services described reference point for LSPs that provide the Ethernet Services described
in [GMPLS-ESVCS]. in [GMPLS-ESVCS].
Except as specifically modified in this document, the procedures Except as specifically modified in this document, the procedures
related to the processing of RSVP objects is not modified by this related to the processing of RSVP objects is not modified by this
document. The relevant procedures in existing documents, notably document. The relevant procedures in existing documents, notably
[GMPLS-ESVCS] and [RFC4208], MUST be followed in all cases not [GMPLS-ESVCS], [GMPLS-EXT] and [RFC4208], MUST be followed in all
explicitly described in this document. cases not explicitly described in this document.
2.1. UNI Addressing 2.1. UNI Addressing
LSPs providing Ethernet connections controlled via the mechanisms LSPs providing Ethernet connections controlled via the mechanisms
defined in this document MUST use the addressing and other procedures defined in this document MUST use the addressing and other procedures
defined in [RFC4208]. Of note, this includes the use of the egress defined in [RFC4208]. Of note, this includes the use of the egress
edge-node's IP address in the end-point address field in the SESSION edge-node's IP address in the end-point address field in the SESSION
object. object.
One issue that presents itself with the addressing approach taken in One issue that presents itself with the addressing approach taken in
skipping to change at page 6, line 25 skipping to change at page 6, line 25
At the UNI reference point, it is possible for the ingress edge-node At the UNI reference point, it is possible for the ingress edge-node
to not have the egress edge-node's IP address when initiating an LSP. to not have the egress edge-node's IP address when initiating an LSP.
This presents an issue as the egress edge-node's IP address is This presents an issue as the egress edge-node's IP address is
carried in the SESSION object. This case is handled leveraging the carried in the SESSION object. This case is handled leveraging the
approach described in Section 7.2 of [RFC4974] to address call ID approach described in Section 7.2 of [RFC4974] to address call ID
assignment by the first core-node. assignment by the first core-node.
When an edge-node (the UNI-C) initiates an LSP and it has the egress When an edge-node (the UNI-C) initiates an LSP and it has the egress
Ethernet endpoint identifier, but does not have its IP address, the Ethernet endpoint identifier, but does not have its IP address, the
edge-node MUST create a Notify message as described in [RFC4974]. edge-node MUST create a Notify message as described in [RFC4974].
The Notify message MUST include the LSP_ATTRIBUTES object with the The Notify message MUST include the CALL_ATTRIBUTES object with the
Endpoint ID TLV defined [GMPLS-ESVCS]. The tunnel end point address Endpoint ID TLV defined [GMPLS-ESVCS]. The tunnel end point address
field of the SESSION object in the Notify message MUST be set to zero field of the SESSION object in the Notify message MUST be set to zero
(0). The message MUST be addressed and sent to an address associated (0). The message MUST be addressed and sent to an address associated
with the first core-node. with the first core-node.
When a core-node, i.e., the node providing the network side of the When a core-node, i.e., the node providing the network side of the
UNI (the UNI-N), receives a Notify message with the tunnel end point UNI (the UNI-N), receives a Notify message with the tunnel end point
address field of the SESSION object set to zero, it MUST locate the address field of the SESSION object set to zero, it MUST locate the
Endpoint ID TLV in the LSP_ATTRIBUTES object. If the object or TLV Endpoint ID TLV in the CALL_ATTRIBUTES object. If the object or TLV
are not present, the node MUST discard the message. In this case, a are not present, the node MUST discard the message. In this case, a
Message ID Acknowledgment MUST NOT be sent for the Notify message. Message ID Acknowledgment MUST NOT be sent for the Notify message.
When the Endpoint ID TLV is located, the node MUST map the Endpoint When the Endpoint ID TLV is located, the node MUST map the Endpoint
ID into an IP address associated with the egress edge-node. If the ID into an IP address associated with the egress edge-node. If the
node is unable to obtain an egress address, it MUST issue an error node is unable to obtain an egress address, it MUST issue an error
response Notify messages according to Section 6.2.2. of [RFC4974]. response Notify messages according to Section 6.2.2. of [RFC4974].
The Error code and value SHOULD be "Routing Problem/Unknown The Error code and value SHOULD be "Routing Problem/Unknown
Endpoint." (To be assigned by IANA). Endpoint." (To be assigned by IANA).
skipping to change at page 8, line 44 skipping to change at page 8, line 44
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
[GMPLS-ESVCS] Berger, L., Papadimitriou, P., Fedyk, D., [GMPLS-ESVCS] Berger, L., Papadimitriou, P., Fedyk, D.,
"Generalized MPLS (GMPLS) Support For Metro Ethernet "Generalized MPLS (GMPLS) Support For Metro Ethernet
Forum and G.8011 Ethernet Service Switching", Work in Forum and G.8011 Ethernet Service Switching", Work in
Progress, draft-berger-ccamp-gmpls-ether-svcs-01.txt, Progress, draft-ietf-ccamp-gmpls-ether-svcs-02.txt,
February 2008. August 2008.
[GMPLS-EXT] Berger, L., Papadimitriou, P., Fedyk, D.,
"Generalized MPLS (GMPLS) Data Channel Switching
Capable (DCSC) and Channel Set Label Extensions",
draft-ietf-ccamp-gmpls-dcsc-channel-ext-00.txt,
Work in Progress, August 2008.
[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.
[RFC3473] Berger, L., Editor, "Generalized Multi-Protocol Label [RFC3473] Berger, L., Editor, "Generalized Multi-Protocol Label
Switching (GMPLS) Signaling - Resource ReserVation Switching (GMPLS) Signaling - Resource ReserVation
skipping to change at page 10, line 7 skipping to change at page 10, line 11
[MEF6] The Metro Ethernet Forum, "Ethernet Services [MEF6] The Metro Ethernet Forum, "Ethernet Services
[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.
8. Acknowledgments 8. Acknowledgments
Dimitri Papadimitriou provided substantial textual contributions to
this document and coauthored earlier versions of this document.
The authors would like to thank Evelyne Roch and Stephen Shew for The authors would like to thank Evelyne Roch and Stephen Shew for
their valuable comments. 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
Dimitri Papadimitriou
Alcatel Lucent
Francis Wellesplein 1,
B-2018 Antwerpen, Belgium
Phone: +32 3 240-8491
Email: Dimitri.Papadimitriou@alcatel-lucent.be
Don Fedyk Don Fedyk
Nortel Networks Nortel Networks
600 Technology Park Drive 600 Technology Park Drive
Billerica, MA, 01821 Billerica, MA, 01821
Phone: +1-978-288-3041 Phone: +1-978-288-3041
Email: dwfedyk@nortel.com Email: dwfedyk@nortel.com
10. Full Copyright Statement 10. Full Copyright Statement
Copyright (C) The IETF Trust (2008). Copyright (C) The IETF Trust (2008).
skipping to change at line 452 skipping to change at line 454
any copyrights, patents or patent applications, or other any copyrights, patents or patent applications, or other
proprietary rights that may cover technology that may be required proprietary rights that may cover technology that may be required
to implement this standard. Please address the information to the to implement this standard. Please address the information to the
IETF at ietf-ipr@ietf.org. IETF at ietf-ipr@ietf.org.
Acknowledgement Acknowledgement
Funding for the RFC Editor function is provided by the IETF Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA). Administrative Support Activity (IASA).
Generated on: Mon Apr 14 18:11:01 EDT 2008 Generated on: Fri Aug 8 10:17:27 EDT 2008
 End of changes. 13 change blocks. 
25 lines changed or deleted 27 lines changed or added

This html diff was produced by rfcdiff 1.35. The latest version is available from http://tools.ietf.org/tools/rfcdiff/