draft-ietf-ccamp-gmpls-ason-reqts-04.txt   draft-ietf-ccamp-gmpls-ason-reqts-05.txt 
CCAMP Working Group D. Papadimitriou (Alcatel) CCAMP Working Group D. Papadimitriou (Alcatel)
Internet Draft J. Drake (Calient) Internet Draft J. Drake (Calient)
Category: Informational J. Ash (ATT) Category: Informational J. Ash (ATT)
A. Farrel (Old Dog Consulting) A. Farrel (Old Dog Consulting)
Expiration Date: April 2004 L. Ong (Ciena) Expiration Date: May 2004 L. Ong (Ciena)
October 2003 November 2003
Requirements for Generalized MPLS (GMPLS) Signaling Usage Requirements for Generalized MPLS (GMPLS) Signaling Usage
and Extensions for Automatically Switched Optical Network (ASON) and Extensions for Automatically Switched Optical Network (ASON)
draft-ietf-ccamp-gmpls-ason-reqts-04.txt draft-ietf-ccamp-gmpls-ason-reqts-05.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC-2026. all provisions of Section 10 of RFC-2026.
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
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Internet-Drafts are draft documents valid for a maximum of Drafts. Internet-Drafts are draft documents valid for a maximum of
skipping to change at line 49 skipping to change at line 49
applications. These include support for requesting TDM connections applications. These include support for requesting TDM connections
including SONET/SDH and Optical Transport Networks (OTNs). including SONET/SDH and Optical Transport Networks (OTNs).
This document concentrates on the signaling aspects of the GMPLS This document concentrates on the signaling aspects of the GMPLS
suite of protocols. It identifies the features to be covered by the suite of protocols. It identifies the features to be covered by the
GMPLS signaling protocol to support the capabilities of an GMPLS signaling protocol to support the capabilities of an
Automatically Switched Optical Network (ASON). This document Automatically Switched Optical Network (ASON). This document
provides a problem statement and additional requirements on the provides a problem statement and additional requirements on the
GMPLS signaling protocol to support the ASON functionality. GMPLS signaling protocol to support the ASON functionality.
D.Papadimitriou et al. - Expires April 2004 1 D.Papadimitriou et al. - Expires May 2004 1
2. Conventions used in this document 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 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
this document are to be interpreted as described in RFC-2119. this document are to be interpreted as described in RFC-2119.
3. Introduction 3. Introduction
The GMPLS suite of protocol specifications provides support for The GMPLS suite of protocol specifications provides support for
skipping to change at line 104 skipping to change at line 104
This document describes the use of GMPLS signaling (in particular, This document describes the use of GMPLS signaling (in particular,
[RFC 3471] and [RFC 3473]) to provide call and connection management [RFC 3471] and [RFC 3473]) to provide call and connection management
(see [ITU-T G.7713]). The following functionality is expected to be (see [ITU-T G.7713]). The following functionality is expected to be
supported and to be backward compatible with the GMPLS protocol supported and to be backward compatible with the GMPLS protocol
suite as currently defined by the IETF: suite as currently defined by the IETF:
(a) soft permanent connection capability (a) soft permanent connection capability
(b) call and connection separation (b) call and connection separation
(c) call segments (c) call segments
(d) extended restart capabilities during control plane failures (d) extended restart capabilities during control plane failures
D.Papadimitriou et al. - Expires March 2004 2 D.Papadimitriou et al. - Expires May 2004 2
(e) extended label association (e) extended label association
(f) crankback capability (f) crankback capability
(g) additional error cases. (g) additional error cases.
4. Requirements for Extending Applicability of GMPLS to ASON 4. Requirements for Extending Applicability of GMPLS to ASON
The next sections detail the signaling protocol requirements for The next sections detail the signaling protocol requirements for
GMPLS to support the following ASON functions: GMPLS to support the following ASON functions:
- Support for soft permanent connection capability - Support for soft permanent connection capability
skipping to change at line 154 skipping to change at line 154
to be a GMPLS UNI and must be supported. to be a GMPLS UNI and must be supported.
Compatibility aspects of non-GMPLS systems (nodes) within a GMPLS Compatibility aspects of non-GMPLS systems (nodes) within a GMPLS
control domain i.e. the support of GMPLS systems and other systems control domain i.e. the support of GMPLS systems and other systems
which utilize other signaling protocols or some which may not which utilize other signaling protocols or some which may not
support any signaling protocols is described. For instance, Section support any signaling protocols is described. For instance, Section
4.5 'Support for Extended Label Association' covers the requirements 4.5 'Support for Extended Label Association' covers the requirements
when a non-GMPLS capable sub-network is introduced or when nodes do when a non-GMPLS capable sub-network is introduced or when nodes do
not support any signaling protocols. not support any signaling protocols.
D.Papadimitriou et al. - Expires March 2004 3 D.Papadimitriou et al. - Expires May 2004 3
4.1 Support for Soft Permanent Connection (SPC) Capability 4.1 Support for Soft Permanent Connection (SPC) Capability
An SPC is a combination of a permanent connection at the source An SPC is a combination of a permanent connection at the source
user-to-network side, a permanent connection at the destination user-to-network side, a permanent connection at the destination
user-to-network side, and a switched connection within the network. user-to-network side, and a switched connection within the network.
An Element Management System (EMS) or a Network Management System An Element Management System (EMS) or a Network Management System
(NMS) typically initiates the establishment of the switched (NMS) typically initiates the establishment of the switched
connection by communicating with the node that initiates the connection by communicating with the node that initiates the
switched connection (also known as the ingress node). The latter switched connection (also known as the ingress node). The latter
skipping to change at line 209 skipping to change at line 209
destination endpoints controlling the SPC request may be needed. destination endpoints controlling the SPC request may be needed.
These may be done via the source and destination signaling These may be done via the source and destination signaling
controller addresses. controller addresses.
Note that the association at the ingress node between the permanent Note that the association at the ingress node between the permanent
connection and the switched connection is an implementation matter connection and the switched connection is an implementation matter
under the control of the EMS/NMS and is not within the scope of the under the control of the EMS/NMS and is not within the scope of the
signaling protocol. It is, therefore, outside the scope of this signaling protocol. It is, therefore, outside the scope of this
document. document.
D.Papadimitriou et al. - Expires March 2004 4 D.Papadimitriou et al. - Expires May 2004 4
4.2 Support for Call and Connection Separation 4.2 Support for Call and Connection Separation
A call may be simply described as "An association between endpoints A call may be simply described as "An association between endpoints
that supports an instance of a service" [ITU-T G.8080]. Thus, it can that supports an instance of a service" [ITU-T G.8080]. Thus, it can
be considered as a service provided between two end-points, where be considered as a service provided between two end-points, where
several calls may exist between them. Multiple connections may be several calls may exist between them. Multiple connections may be
associated to each call. The call concept provides an abstract associated to each call. The call concept provides an abstract
relationship between two users, where this relationship describes relationship between two users, where this relationship describes
(or verifies) to what extent the users are willing to offer (or (or verifies) to what extent the users are willing to offer (or
skipping to change at line 261 skipping to change at line 261
For instance, a feasible structure for the call identifier (to For instance, a feasible structure for the call identifier (to
guarantee global uniqueness) may concatenate a globally unique fixed guarantee global uniqueness) may concatenate a globally unique fixed
ID (e.g., may be composed of country code, carrier code) with an ID (e.g., may be composed of country code, carrier code) with an
operator specific ID (where the operator specific ID may be composed operator specific ID (where the operator specific ID may be composed
of a unique access point code - such as source node address - and a of a unique access point code - such as source node address - and a
local identifier). Other formats shall also be possible depending on local identifier). Other formats shall also be possible depending on
the call identification conventions between parties involved in the the call identification conventions between parties involved in the
call setup process. call setup process.
D.Papadimitriou et al. - Expires March 2004 5 D.Papadimitriou et al. - Expires May 2004 5
4.3 Support for Call Segments 4.3 Support for Call Segments
As described in [ITU-T G.8080], call segmentation may be applied As described in [ITU-T G.8080], call segmentation may be applied
when a call crosses several administrative domains. As such, an end- when a call crosses several administrative domains. As such, an end-
to-end call may consist of multiple call segments, when the call to-end call may consist of multiple call segments, when the call
traverses multiple administrative domains. Each call segment can traverses multiple administrative domains. For a given end-to-end
have one or more associated connections and the number of call, each call segment can have one or more associated connections
connections associated with each call segment may not be the same and the number of connections associated with each call segment may
for a given end-to-end call. be different.
The initiating caller interacts with a called party by means of one The initiating caller interacts with the called party by means of
or more intermediate call controllers located at the network edge one or more intermediate network call controllers located at
between administrative domains (i.e., inter-domain reference point) administrative domain boundaries (i.e., inter-domain reference
and in particular at the user-to-network reference point. Their points). Call segment capabilities are defined by the policies
functions are defined by the policies associated by interactions associated at these reference points.
between the administrative domain boundaries and between users and
the network.
This capability allows for independent (policy based) choices of This capability allows for independent (policy based) choices of
signaling, concatenation, data plane protection and control plane signaling, concatenation, data plane protection and control plane
driven recovery paradigms in different administrative domains. driven recovery paradigms in different administrative domains.
4.4 Support for Extended Restart Capabilities 4.4 Support for Extended Restart Capabilities
Various types of failures may occur affecting the ASON control Various types of failures may occur affecting the ASON control
plane. Requirements placed on the control plane failure recovery by plane. Requirements placed on the control plane failure recovery by
[ITU-T G.8080] include: [ITU-T G.8080] include:
skipping to change at line 315 skipping to change at line 313
4.5 Support for Extended Label Association 4.5 Support for Extended Label Association
Labels are defined in GMPLS (see [RFC 3471]) to provide information Labels are defined in GMPLS (see [RFC 3471]) to provide information
on the resources used on link local basis for a particular on the resources used on link local basis for a particular
connection. The labels may range from specifying a particular connection. The labels may range from specifying a particular
timeslot, a particular wavelength to a particular port/fiber. timeslot, a particular wavelength to a particular port/fiber.
In the ASON context, the value of a label MAY not be consistently In the ASON context, the value of a label MAY not be consistently
the same across a link. For example, the figure below illustrates the same across a link. For example, the figure below illustrates
D.Papadimitriou et al. - Expires March 2004 6
the case where two GMPLS capable nodes (A and Z) are interconnected the case where two GMPLS capable nodes (A and Z) are interconnected
D.Papadimitriou et al. - Expires May 2004 6
across two non-GMPLS capable nodes (B and C), where these nodes are across two non-GMPLS capable nodes (B and C), where these nodes are
all SONET/SDH nodes providing, e.g., a VC-4 service. all SONET/SDH nodes providing, e.g., a VC-4 service.
----- ----- ----- -----
| | --- --- | | | | --- --- | |
| A |---| B |---| C |---| Z | | A |---| B |---| C |---| Z |
| | --- --- | | | | --- --- | |
----- ----- ----- -----
Labels have an associated implicit imposed structure based on Labels have an associated implicit imposed structure based on
skipping to change at line 370 skipping to change at line 368
Either method may be used. In case of dynamic association, this Either method may be used. In case of dynamic association, this
implies that the discovery mechanism operates at the timeslot/label implies that the discovery mechanism operates at the timeslot/label
level before the connection request is processed at the ingress level before the connection request is processed at the ingress
node. Note that in the case where two nodes are directly connected, node. Note that in the case where two nodes are directly connected,
no association is required. In particular, for directly connected no association is required. In particular, for directly connected
TDM interfaces no mapping function (at all) is required due to the TDM interfaces no mapping function (at all) is required due to the
implicit label structure (see [GMPLS-SONET] and [GMPLS-OTN]). In implicit label structure (see [GMPLS-SONET] and [GMPLS-OTN]). In
such instances, the label association function provides a one-to-one such instances, the label association function provides a one-to-one
mapping of the received to local label values. mapping of the received to local label values.
D.Papadimitriou et al. - Expires March 2004 7 D.Papadimitriou et al. - Expires May 2004 7
4.6 Support for Crankback 4.6 Support for Crankback
Crankback has been identified as an important requirement for ASON Crankback has been identified as an important requirement for ASON
networks. It allows a connection setup request to be retried on an networks. It allows a connection setup request to be retried on an
alternate path that detours around a blocked link or node upon a alternate path that detours around a blocked link or node upon a
setup failure, for instance, because a link or a node along the setup failure, for instance, because a link or a node along the
selected path has insufficient resources. selected path has insufficient resources.
Crankback mechanisms may also be applied during connection recovery Crankback mechanisms may also be applied during connection recovery
skipping to change at line 425 skipping to change at line 423
connection, per node, per area or even per administrative domain. connection, per node, per area or even per administrative domain.
- When the number of retries at a particular node or area is - When the number of retries at a particular node or area is
exceeded, the node currently handling the failure reports the exceeded, the node currently handling the failure reports the
error message upstream to the next repair node where further error message upstream to the next repair node where further
rerouting attempts may be performed. It is important that the rerouting attempts may be performed. It is important that the
crankback information provided indicates that re-routing crankback information provided indicates that re-routing
through this node will not succeed. through this node will not succeed.
- When the maximum number of retries for a specific connection - When the maximum number of retries for a specific connection
has been exceeded, the repair node handling the current has been exceeded, the repair node handling the current
D.Papadimitriou et al. - Expires March 2004 8 D.Papadimitriou et al. - Expires May 2004 8
failure should send an error message upstream indicating failure should send an error message upstream indicating
"Maximum number of re-routings exceeded". This error message "Maximum number of re-routings exceeded". This error message
will be sent back to the ingress node with no further will be sent back to the ingress node with no further
rerouting attempts. Then, the ingress node may choose to rerouting attempts. Then, the ingress node may choose to
retry the connection setup according to local policy but also retry the connection setup according to local policy but also
re-use its original path or compute a path that avoids the re-use its original path or compute a path that avoids the
blocking resources. blocking resources.
Note: after several retries, a given repair point may be unable to Note: after several retries, a given repair point may be unable to
compute a path to the destination node that avoids all of the compute a path to the destination node that avoids all of the
skipping to change at line 479 skipping to change at line 477
Additionally, when transit nodes, that do not need to participate in Additionally, when transit nodes, that do not need to participate in
the new functions described in this document, lie on the path of a the new functions described in this document, lie on the path of a
call or connection, the GMPLS signaling extensions must be such that call or connection, the GMPLS signaling extensions must be such that
those transit nodes are able to participate in the establishment of those transit nodes are able to participate in the establishment of
the call or connection by passing the setup information onwards, the call or connection by passing the setup information onwards,
unmodified. unmodified.
Lastly, when a transit or egress node is called upon to support a Lastly, when a transit or egress node is called upon to support a
function described in this document, but does not, the GMPLS function described in this document, but does not, the GMPLS
D.Papadimitriou et al. - Expires March 2004 9 D.Papadimitriou et al. - Expires May 2004 9
signaling extensions must be such that they can be rejected by pre- signaling extensions must be such that they can be rejected by pre-
existing GMPLS signaling mechanisms in a way that is not detrimental existing GMPLS signaling mechanisms in a way that is not detrimental
to the network as a whole. to the network as a whole.
6. Security Considerations 6. Security Considerations
Per [ITU-T G.8080], it is not possible to establish a connection Per [ITU-T G.8080], it is not possible to establish a connection
until the associated call has been set up. Also, policy and until the associated call has been set up. Also, policy and
authentication procedures are applied prior to the establishment of authentication procedures are applied prior to the establishment of
the call (and can then also be restricted to connection the call (and can then also be restricted to connection
skipping to change at line 530 skipping to change at line 528
[RFC 3473] L.Berger (Editor) et al., "Generalized Multi-Protocol [RFC 3473] L.Berger (Editor) et al., "Generalized Multi-Protocol
Label Switching (GMPLS) Signaling - Resource Label Switching (GMPLS) Signaling - Resource
ReserVation Protocol-Traffic Engineering (RSVP-TE) ReserVation Protocol-Traffic Engineering (RSVP-TE)
Extensions," RFC 3473, January 2003. Extensions," RFC 3473, January 2003.
[ITU-T G.8080] ITU-T Rec. G.8080/Y.1304, "Architecture for the [ITU-T G.8080] ITU-T Rec. G.8080/Y.1304, "Architecture for the
Automatically Switched Optical Network (ASON)," Automatically Switched Optical Network (ASON),"
November 2001 (and Revision, January 2003). November 2001 (and Revision, January 2003).
D.Papadimitriou et al. - Expires March 2004 10 D.Papadimitriou et al. - Expires May 2004 10
8.2 Informative References 8.2 Informative References
[GMPLS-OTN] D.Papadimitriou (Editor), "GMPLS Signaling Extensions [GMPLS-OTN] D.Papadimitriou (Editor), "GMPLS Signaling Extensions
for G.709 Optical Transport Networks Control," Work for G.709 Optical Transport Networks Control," Work
in progress, draft-ietf-ccamp-gmpls-g709-04.txt, May in progress, draft-ietf-ccamp-gmpls-g709-04.txt, May
2003. 2003.
[GMPLS-OVERLAY]G.Swallow et al., "GMPLS RSVP Support for Overlay [GMPLS-OVERLAY]G.Swallow et al., "GMPLS RSVP Support for Overlay
Model," Work in Progress, draft-ietf-ccamp-gmpls- Model," Work in Progress, draft-ietf-ccamp-gmpls-
overlay-01.txt, February 2003. overlay-02.txt, October 2003.
[GMPLS-SONET] E.Mannie and D.Papadimitriou (Editors), "GMPLS [GMPLS-SONET] E.Mannie and D.Papadimitriou (Editors), "GMPLS
Extensions for SONET and SDH Control, Work in Extensions for SONET and SDH Control, Work in
Progress," draft-ietf-ccamp-gmpls-sonet-sdh-08.txt, Progress," draft-ietf-ccamp-gmpls-sonet-sdh-08.txt,
February 2003. February 2003.
[GMPLS-VPN] H.Ould-Brahim and Y.Rekhter (Editor), "GVPN Services: [GMPLS-VPN] H.Ould-Brahim and Y.Rekhter (Editor), "GVPN Services:
Generalized VPN Services using BGP and GMPLS Generalized VPN Services using BGP and GMPLS
Toolkit," Work in Progress, draft-ouldbrahim-ppvpn- Toolkit," Work in Progress, draft-ouldbrahim-ppvpn-
gvpn-bgpgmpls-03.txt, March 2003. gvpn-bgpgmpls-04.txt, October 2003.
[ITU-T G.7713] ITU-T Rec. G.7713/Y.1304, "Distributed Call and [ITU-T G.7713] ITU-T Rec. G.7713/Y.1304, "Distributed Call and
Connection Management," November 2001. Connection Management," November 2001.
9. Author's Addresses 9. Author's Addresses
Dimitri Papadimitriou (Alcatel) Dimitri Papadimitriou (Alcatel)
Francis Wellesplein 1, Francis Wellesplein 1,
B-2018 Antwerpen, Belgium B-2018 Antwerpen, Belgium
Phone: +32 3 2408491 Phone: +32 3 2408491
skipping to change at line 585 skipping to change at line 583
AT&T Labs, Room MT D5-2A01 AT&T Labs, Room MT D5-2A01
200 Laurel Avenue 200 Laurel Avenue
Middletown, NJ 07748, USA Middletown, NJ 07748, USA
EMail: gash@att.com EMail: gash@att.com
Lyndon Ong (Ciena) Lyndon Ong (Ciena)
5965 Silver Creek Valley Road 5965 Silver Creek Valley Road
San Jose, CA 95138, USA San Jose, CA 95138, USA
EMail: lyong@ciena.com EMail: lyong@ciena.com
D.Papadimitriou et al. - Expires March 2004 11 D.Papadimitriou et al. - Expires May 2004 11
Appendix - Terminology Appendix - Terminology
This document makes use of the following terms: This document makes use of the following terms:
Administrative domain: See Recommendation G.805. Administrative domain: See Recommendation G.805.
Call: association between endpoints that supports an instance of a Call: association between endpoints that supports an instance of a
service. service.
skipping to change at line 636 skipping to change at line 634
Transport plane: provides bi-directional or unidirectional transfer Transport plane: provides bi-directional or unidirectional transfer
of user information, from one location to another. It can also of user information, from one location to another. It can also
provide transfer of some control and network management information. provide transfer of some control and network management information.
The Transport Plane is layered; it is equivalent to the Transport The Transport Plane is layered; it is equivalent to the Transport
Network defined in G.805. Network defined in G.805.
User Network Interface (UNI): interfaces are located between User Network Interface (UNI): interfaces are located between
protocol controllers between a user and a control domain. protocol controllers between a user and a control domain.
D.Papadimitriou et al. - Expires March 2004 12 D.Papadimitriou et al. - Expires May 2004 12
Full Copyright Statement Full Copyright Statement
"Copyright (C) The Internet Society (2003). All Rights Reserved. "Copyright (C) The Internet Society (2003). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph kind, provided that the above copyright notice and this paragraph
skipping to change at line 666 skipping to change at line 664
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
D.Papadimitriou et al. - Expires March 2004 13 D.Papadimitriou et al. - Expires May 2004 13
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/