draft-ietf-pce-wson-routing-wavelength-01.txt   draft-ietf-pce-wson-routing-wavelength-02.txt 
Network Working Group Y. Lee Network Working Group Y. Lee
Internet Draft Huawei Internet Draft Huawei
Intended status: Standard Track Intended status: Standard Track
Expires: September 2010 G. Bernstein Expires: February 2011 G. Bernstein
Grotto Networking Grotto Networking
Jonas Martensson Jonas Martensson
Acreo Acreo
T. Takeda T. Takeda
NTT NTT
T. Tsuritani T. Tsuritani
KDDI KDDI
March 1, 2010 August 23, 2010
PCEP Requirements for WSON Routing and Wavelength Assignment PCEP Requirements for WSON Routing and Wavelength Assignment
draft-ietf-pce-wson-routing-wavelength-01.txt draft-ietf-pce-wson-routing-wavelength-02.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.
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. Drafts.
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
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 1, 2010. This Internet-Draft will expire on December 23, 2010.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with
to this document. Code Components extracted from this document must respect to this document. Code Components extracted from this
include Simplified BSD License text as described in Section 4.e of document must include Simplified BSD License text as described in
the Trust Legal Provisions and are provided without warranty as Section 4.e of the Trust Legal Provisions and are provided without
described in the BSD License. warranty as described in the Simplified BSD License.
Abstract Abstract
This memo provides application-specific requirements for the Path This memo provides application-specific requirements for the Path
Computation Element communication Protocol (PCEP) for the support of Computation Element communication Protocol (PCEP) for the support of
Wavelength Switched Optical Networks (WSON). Lightpath provisioning Wavelength Switched Optical Networks (WSON). Lightpath provisioning
in WSONs requires a routing and wavelength assignment (RWA) process. in WSONs requires a routing and wavelength assignment (RWA) process.
From a path computation perspective, wavelength assignment is the From a path computation perspective, wavelength assignment is the
process of determining which wavelength can be used on each hop of a process of determining which wavelength can be used on each hop of a
path and forms an additional routing constraint to optical light path path and forms an additional routing constraint to optical light path
skipping to change at page 2, line 41 skipping to change at page 2, line 41
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 RFC-2119 0. document are to be interpreted as described in RFC-2119 0.
Table of Contents Table of Contents
1. Introduction...................................................3 1. Introduction...................................................3
1.1. WSON RWA Processes........................................4 1.1. WSON RWA Processes........................................4
2. WSON PCE Architectures and Requirements........................5 2. WSON PCE Architectures and Requirements........................5
2.1. RWA PCC to PCE Interface..................................6 2.1. RWA PCC to PCE Interface..................................6
2.1.1. A new RWA path request...............................6 2.1.1. A new RWA path request/reply.........................6
2.1.2. An RWA path re-optimization request..................6 2.1.2. Bulk RWA path request/reply..........................6
2.1.3. Wavelength Range Constraint..........................6 2.1.3. An RWA path re-optimization request/reply............7
3. Manageability Considerations...................................7 2.1.4. Wavelength Range Constraint..........................7
3.1. Control of Function and Policy............................7 2.1.5. Wavelength Policy Constraint.........................7
3. Manageability Considerations...................................8
3.1. Control of Function and Policy............................8
3.2. Information and Data Models, e.g. MIB module..............8 3.2. Information and Data Models, e.g. MIB module..............8
3.3. Liveness Detection and Monitoring.........................8 3.3. Liveness Detection and Monitoring.........................8
3.4. Verifying Correct Operation...............................8 3.4. Verifying Correct Operation...............................9
3.5. Requirements on Other Protocols and Functional Components.8 3.5. Requirements on Other Protocols and Functional Components.9
3.6. Impact on Network Operation...............................8 3.6. Impact on Network Operation...............................9
4. Security Considerations........................................8 4. Security Considerations........................................9
5. IANA Considerations............................................9 5. IANA Considerations............................................9
6. Acknowledgments................................................9 6. Acknowledgments................................................9
7. References.....................................................9 7. References....................................................10
7.1. Normative References......................................9 7.1. Normative References.....................................10
7.2. Informative References...................................10 7.2. Informative References...................................10
Authors' Addresses...............................................10 Authors' Addresses...............................................11
Intellectual Property Statement..................................11 Intellectual Property Statement..................................11
Disclaimer of Validity...........................................12 Disclaimer of Validity...........................................12
1. Introduction 1. Introduction
[RFC4655] defines the PCE based Architecture and explains how a Path [RFC4655] defines the PCE based Architecture and explains how a Path
Computation Element (PCE) may compute Label Switched Paths (LSP) in Computation Element (PCE) may compute Label Switched Paths (LSP) in
Multiprotocol Label Switching Traffic Engineering (MPLS-TE) and Multiprotocol Label Switching Traffic Engineering (MPLS-TE) and
Generalized MPLS (GMPLS) networks at the request of Path Computation Generalized MPLS (GMPLS) networks at the request of Path Computation
Clients (PCCs). A PCC is shown to be any network component that Clients (PCCs). A PCC is shown to be any network component that
makes such a request and may be for instance an Optical Switching makes such a request and may be for instance an Optical Switching
Element within a Wavelength Division Multiplexing (WDM) network. The Element within a Wavelength Division Multiplexing (WDM) network. The
PCE, itself, can be located anywhere within the network, and may be PCE, itself, can be located anywhere within the network, and may be
within an optical switching element, a Network Management System within an optical switching element, a Network Management System
skipping to change at page 4, line 33 skipping to change at page 4, line 37
abilities, wavelength assignment is an additional routing constraint abilities, wavelength assignment is an additional routing constraint
to be considered in all lightpath computation. to be considered in all lightpath computation.
In this document we first review the processes for routing and In this document we first review the processes for routing and
wavelength assignment (RWA) used when wavelength continuity wavelength assignment (RWA) used when wavelength continuity
constraints are present and then specify requirements for PCEP to constraints are present and then specify requirements for PCEP to
support RWA. support RWA.
The remainder of this document uses terminology from [RFC4655]. The remainder of this document uses terminology from [RFC4655].
1.1. WSON RWA Processes 1.1. WSON RWA Processes
In [WSON-Frame] three alternative process architectures were given In [WSON-Frame] three alternative process architectures were given
for performing routing and wavelength assignment. These are shown for performing routing and wavelength assignment. These are shown
schematically in Figure 1. schematically in Figure 1.
+-------------------+ +-------------------+
| +-------+ +--+ | +-------+ +--+ +-------+ +---+ | +-------+ +--+ | +-------+ +--+ +-------+ +---+
| |Routing| |WA| | |Routing|--->|WA| |Routing|--->|DWA| | |Routing| |WA| | |Routing|--->|WA| |Routing|--->|DWA|
| +-------+ +--+ | +-------+ +--+ +-------+ +---+ | +-------+ +--+ | +-------+ +--+ +-------+ +---+
| Combined | Separate Processes Separate Processes | Combined | Separate Processes Separate Processes
skipping to change at page 5, line 29 skipping to change at page 5, line 40
addressed in this document. addressed in this document.
3. Routing and distributed Wavelength Assignment (R+DWA) - Here a 3. Routing and distributed Wavelength Assignment (R+DWA) - Here a
standard path computation (unaware of detailed wavelength standard path computation (unaware of detailed wavelength
availability) takes place, then wavelength assignment is performed availability) takes place, then wavelength assignment is performed
along this path in a distributed manner via signaling (RSVP-TE). along this path in a distributed manner via signaling (RSVP-TE).
This alternative should be covered by existing or emerging GMPLS This alternative should be covered by existing or emerging GMPLS
PCEP extensions and does not present new WSON specific PCEP extensions and does not present new WSON specific
requirements. requirements.
2. WSON PCE Architectures and Requirements 2. WSON PCE Architectures and Requirements
In the previous section we reviewed various process architectures for In the previous section various process architectures for
implementing RWA. In Figure 2 we reduce these alternatives to one implementing RWA have been reviewed. Figure 2 shows one typical PCE
typical PCE based implementation, which is referred to as Combined based implementation, which is referred to as Combined Process
Process (R&WA). In Figure 2 we show the two processes of routing and (R&WA). With this architecture, the two processes of routing and
wavelength assignment accessed via a single PCE. wavelength assignment are accessed via a single PCE. This
architecture is the base architecture from which the requirements are
specified in this document.
+----------------------------+ +----------------------------+
+-----+ | +-------+ +--+ | +-----+ | +-------+ +--+ |
| | | |Routing| |WA| | | | | |Routing| |WA| |
| PCC |<----->| +-------+ +--+ | | PCC |<----->| +-------+ +--+ |
| | | | | | | |
+-----+ | PCE | +-----+ | PCE |
+----------------------------+ +----------------------------+
Figure 2 Combined Process (R&WA) architecture Figure 2 Combined Process (R&WA) architecture
2.1. RWA PCC to PCE Interface 2.1. RWA PCC to PCE Interface
The requirements for the PCC to PCE interface of Figure 2 are The requirements for the PCC to PCE interface of Figure 2 are
specified in this section. specified in this section.
2.1.1. A new RWA path request 2.1.1. A new RWA path request/reply
1. The PCReq Message MUST include the path computation type. This can 1. The PCReq Message MUST include the path computation type. This can
be: RWA, or only routing. This requirement is needed to be:
differentiate between the currently supported routing with
distribute wavelength assignment option and combined RWA. (i) Both Routing and Wavelength Assignment (RWA), or
(ii) Routing only.
This requirement is needed to differentiate between the currently
supported routing with distributed wavelength assignment option and
combined RWA. In case of distributed wavelength assignment option,
wavelength assignment will be performed at each node of the route.
2. The PCRep Message MUST include the route, wavelengths assigned to 2. The PCRep Message MUST include the route, wavelengths assigned to
the route and an indicator that says if the path has passed an the route (i.e., each hop of the route must be assigned a
optical quality check. In the case where a valid path is not wavelength).
found, the PCRep Message MUST include why the path is not found
(e.g., no route, wavelength not found, etc.)
2.1.2. An RWA path re-optimization request 3. In the case where a valid path is not found, the PCRep Message
MUST include why the path is not found (e.g., no route, wavelength
not found, optical quality check failed, etc.)
2.1.2. Bulk RWA path request/reply
1. The PCReq Message MUST be able to specify an option for bulk RWA
path request. Bulk path request is an ability to request a number
of simultaneous RWA path requests.
2. The PCRep Message MUST include the route, wavelength assigned to
the route for each RWA path request specified in the original bulk
PCReq Message.
2.1.3. An RWA path re-optimization request/reply
1. For a re-optimization request, the PCReq Message MUST provide the 1. For a re-optimization request, the PCReq Message MUST provide the
path to be re-optimized and include the following options: path to be re-optimized and include the following options:
a. Re-optimize the path keeping the same wavelength(s) a. Re-optimize the path keeping the same wavelength(s)
b. Re-optimize wavelength(s) keeping the same path b. Re-optimize wavelength(s) keeping the same path
c. Re-optimize allowing both wavelength and the path to change c. Re-optimize allowing both wavelength and the path to change
2. The corresponding PCRep Message for the re-optimized request MUST 2. The corresponding PCRep Message for the re-optimized request MUST
provide the Re-optimized path and wavelengths. In case that the provide the Re-optimized path and wavelengths.
path is not found, the PCRep Message MUST include why the path is
not found (e.g., no route, wavelength not found, both route and
wavelength not found, etc.)
2.1.3. Wavelength Range Constraint 3. In case that the path is not found, the PCRep Message MUST include
why the path is not found (e.g., no route, wavelength not found,
both route and wavelength not found, etc.)
2.1.4. Wavelength Range Constraint
For any PCReq Message that is associated with a request for For any PCReq Message that is associated with a request for
wavelength assignment the requester (PCC) MUST be able to specify a wavelength assignment the requester (PCC) MUST be able to specify a
restriction on the wavelengths to be used. restriction on the wavelengths to be used.
Note that the requestor (PCC) is NOT required to furnish any range Note that the requestor (PCC) is NOT required to furnish any range
restrictions. This restriction is to be interpreted by the PCE as a restrictions. This restriction is to be interpreted by the PCE as a
constraint on the tuning ability of the origination laser constraint on the tuning ability of the origination laser
transmitter. transmitter.
2.1.4. Wavelength Policy Constraint 2.1.5. Wavelength Policy Constraint
The PCReq Message May include specific operator's policy information The PCReq Message May include specific operator's policy information
for WA (E.g., random assignment, descending order, ascending order, for WA (E.g., random assignment, descending order, ascending order,
etc.) etc.)
3. Manageability Considerations
3. Manageability Considerations
Manageability of WSON Routing and Wavelength Assignment (RWA) with Manageability of WSON Routing and Wavelength Assignment (RWA) with
PCE must address the following considerations: PCE must address the following considerations:
3.1. Control of Function and Policy 3.1. Control of Function and Policy
In addition to the parameters already listed in Section 8.1 of In addition to the parameters already listed in Section 8.1 of
[PCEP], a PCEP implementation SHOULD allow configuring the following [PCEP], a PCEP implementation SHOULD allow configuring the following
PCEP session parameters on a PCC: PCEP session parameters on a PCC:
o The ability to send a WSON RWA request. o The ability to send a WSON RWA request.
In addition to the parameters already listed in Section 8.1 of In addition to the parameters already listed in Section 8.1 of
[PCEP], a PCEP implementation SHOULD allow configuring the following [PCEP], a PCEP implementation SHOULD allow configuring the following
PCEP session parameters on a PCE: PCEP session parameters on a PCE:
skipping to change at page 8, line 5 skipping to change at page 8, line 34
WSON RWA per request message. WSON RWA per request message.
o A set of WSON RWA specific policies (authorized sender, request o A set of WSON RWA specific policies (authorized sender, request
rate limiter, etc). rate limiter, etc).
These parameters may be configured as default parameters for any PCEP These parameters may be configured as default parameters for any PCEP
session the PCEP speaker participates in, or may apply to a specific session the PCEP speaker participates in, or may apply to a specific
session with a given PCEP peer or a specific group of sessions with a session with a given PCEP peer or a specific group of sessions with a
specific group of PCEP peers. specific group of PCEP peers.
3.2. Information and Data Models, e.g. MIB module 3.2. Information and Data Models, e.g. MIB
module
Extensions to the PCEP MIB module defined in [PCEP-MIB] should be Extensions to the PCEP MIB module defined in [PCEP-MIB] should be
defined, so as to cover the WSON RWA information introduced in this defined, so as to cover the WSON RWA information introduced in this
document. A future revision of this document will list the document. A future revision of this document will list the
information that should be added to the MIB module. information that should be added to the MIB module.
3.3. Liveness Detection and Monitoring 3.3. Liveness Detection and Monitoring
Mechanisms defined in this document do not imply any new liveness Mechanisms defined in this document do not imply any new liveness
detection and monitoring requirements in addition to those already detection and monitoring requirements in addition to those already
listed in section 8.3 of [PCEP]. listed in section 8.3 of [PCEP].
3.4. Verifying Correct Operation 3.4. Verifying Correct Operation
Mechanisms defined in this document do not imply any new verification Mechanisms defined in this document do not imply any new verification
requirements in addition to those already listed in section 8.4 of requirements in addition to those already listed in section 8.4 of
[PCEP] [PCEP]
3.5. Requirements on Other Protocols and Functional Components 3.5. Requirements on Other Protocols and
Functional Components
The PCE Discovery mechanisms ([RFC5089] and [RFC5088]) may be used to The PCE Discovery mechanisms ([RFC5089] and [RFC5088]) may be used to
advertise WSON RWA path computation capabilities to PCCs. advertise WSON RWA path computation capabilities to PCCs.
3.6. Impact on Network Operation 3.6. Impact on Network Operation
Mechanisms defined in this document do not imply any new network Mechanisms defined in this document do not imply any new network
operation requirements in addition to those already listed in section operation requirements in addition to those already listed in section
8.6 of [PCEP]. 8.6 of [PCEP].
4. Security Considerations 4. Security Considerations
This document has no requirement for a change to the security models This document has no requirement for a change to the security models
within PCEP [PCEP]. However the additional information distributed in within PCEP [PCEP]. However the additional information distributed in
order to address the RWA problem represents a disclosure of network order to address the RWA problem represents a disclosure of network
capabilities that an operator may wish to keep private. Consideration capabilities that an operator may wish to keep private. Consideration
should be given to securing this information. should be given to securing this information.
5. IANA Considerations 5. IANA Considerations
A future revision of this document will present requests to IANA for A future revision of this document will present requests to IANA for
codepoint allocation. codepoint allocation.
6. Acknowledgments 6. Acknowledgments
The authors would like to thank Adrian Farrel for many helpful The authors would like to thank Adrian Farrel for many helpful
comments that greatly improved the contents of this draft. comments that greatly improved the contents of this draft.
This document was prepared using 2-Word-v2.0.template.dot. This document was prepared using 2-Word-v2.0.template.dot.
7. References 7. References
7.1. Normative References 7.1. Normative References
[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.
[RFC3471] Berger, L., "Generalized Multi-Protocol Label Switching [RFC3471] Berger, L., "Generalized Multi-Protocol Label Switching
(GMPLS) Signaling Functional Description", RFC 3471, (GMPLS) Signaling Functional Description", RFC 3471,
January 2003. January 2003.
[RFC3473] Berger, L., Ed., "Generalized Multi-Protocol Label [RFC3473] Berger, L., Ed., "Generalized Multi-Protocol Label
Switching (GMPLS) Signaling Resource ReserVation Protocol- Switching (GMPLS) Signaling Resource ReserVation Protocol-
Traffic Engineering (RSVP-TE) Extensions", RFC 3473, Traffic Engineering (RSVP-TE) Extensions", RFC 3473,
January 2003. January 2003.
[RFC4655] Farrel, A., Vasseur, J., and J. Ash, "A Path Computation [RFC4655] Farrel, A., Vasseur, J., and J. Ash, "A Path Computation
Element (PCE)-Based Architecture", RFC 4655, August 2006. Element (PCE)-Based Architecture", RFC 4655, August 2006.
[RFC4657] Ash, J. and J. Le Roux, "Path Computation Element (PCE) [RFC4657] Ash, J. and J. Le Roux, "Path Computation Element (PCE)
Communication Protocol Generic Requirements", RFC 4657, Communication Protocol Generic Requirements", RFC 4657,
September 2006. September 2006.
[PCEP] Vasseur, JP., Ed. and JL. Le Roux, Ed., "Path Computation [RFC5440] Vasseur, JP., Ed. and JL. Le Roux, Ed., "Path Computation
Element (PCE) communication Protocol (PCEP) - Version 1", Element (PCE) communication Protocol", RFC 5440, March
draft-ietf-pce-pcep, work in progress. 2009.
7.2. Informative References 7.2. Informative References
[WSON-Frame] Bernstein, G. and Lee, Y. (Editors), and W. Imajuku, "A [WSON-IMP] Lee, Y. and Bernstein, G. (Editors), D. Li and G.
Framework for the Control and Measurement of Wavelength Martinelli "A Framework for the Control and Measurement of
Switched Optical Networks (WSON) with Impairments Wavelength Switched Optical Networks (WSON) with
draft-bernstein-ccamp-wson-impairments-02.txt, work in Impairments, draft-ietf-ccamp-wson-impairments, work in
progress. progress.
[WSON-IMP] Bernstein, G. and Lee, Y. (Editors), and D. Li, "Framework [WSON-Frame] Lee, Y. and Bernstein, G. (Editors), and W. Imajuku,
for GMPLS and PCE Control of Wavelength Switched Optical "Framework for GMPLS and PCE Control of Wavelength Switched
Networks", draft-bernstein-ccamp-wavelength-switched, work Optical Networks", draft-ietf-ccamp-rwa-wson-framework,
in progress. work in progress.
[RFC5088] Le Roux, JL., Ed., Vasseur, JP., Ed., Ikejiri, Y., and R. [RFC5088] Le Roux, JL., Ed., Vasseur, JP., Ed., Ikejiri, Y., and R.
Zhang, "OSPF Protocol Extensions for Path Computation Zhang, "OSPF Protocol Extensions for Path Computation
Element (PCE) Discovery", RFC 5088, January 2008. Element (PCE) Discovery", RFC 5088, January 2008.
[RFC5089] Le Roux, JL., Ed., Vasseur, JP., Ed., Ikejiri, Y., and R. [RFC5089] Le Roux, JL., Ed., Vasseur, JP., Ed., Ikejiri, Y., and R.
Zhang, "IS-IS Protocol Extensions for Path Computation Zhang, "IS-IS Protocol Extensions for Path Computation
Element (PCE) Discovery", RFC 5089, January 2008. Element (PCE) Discovery", RFC 5089, January 2008.
Authors' Addresses Authors' Addresses
 End of changes. 38 change blocks. 
71 lines changed or deleted 97 lines changed or added

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