draft-ietf-pce-wson-routing-wavelength-06.txt   draft-ietf-pce-wson-routing-wavelength-07.txt 
Network Working Group Y. Lee Network Working Group Y. Lee
Internet Draft Huawei Internet Draft Huawei
Intended status: Informational Intended status: Informational
Expires: April 2012 G. Bernstein Expires: October 2012 G. Bernstein
Grotto Networking Grotto Networking
Jonas Martensson Jonas Martensson
Acreo Acreo
T. Takeda T. Takeda
NTT NTT
T. Tsuritani T. Tsuritani
KDDI KDDI
O. G. de Dios O. G. de Dios
Telefonica Telefonica
October 30, 2011 April 23, 2012
PCEP Requirements for WSON Routing and Wavelength Assignment PCEP Requirements for WSON Routing and Wavelength Assignment
draft-ietf-pce-wson-routing-wavelength-06.txt draft-ietf-pce-wson-routing-wavelength-07.txt
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with This Internet-Draft is submitted to IETF in full conformance with
the provisions of BCP 78 and BCP 79. the 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.
skipping to change at page 1, line 47 skipping to change at page 1, line 47
months and may be updated, replaced, or obsoleted by other documents months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as at any time. It is inappropriate to use Internet-Drafts as
reference material or to cite them other than as "work in progress." reference 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 January 30, 2009. This Internet-Draft will expire on October 23, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2012 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 carefully, as they describe your rights and restrictions with
respect to this document. Code Components extracted from this respect to this document. Code Components extracted from this
document must include Simplified BSD License text as described in document must include Simplified BSD License text as described in
Section 4.e of the Trust Legal Provisions and are provided without Section 4.e of the Trust Legal Provisions and are provided without
skipping to change at page 2, line 40 skipping to change at page 2, line 40
addressed in a separate document. addressed in a separate document.
Conventions used in this document 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 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. RWA Computation Type and Wavelength Assignment Option6 2.1.1. RWA Computation Type and Wavelength Assignment Option6
2.1.2. Bulk RWA path request/reply..........................7 2.1.2. Bulk RWA path request/reply..........................7
2.1.3. An RWA path re-optimization request/reply............7 2.1.3. An RWA path re-optimization request/reply............7
2.1.4. Wavelength Range Constraint..........................7 2.1.4. Wavelength Range Constraint..........................7
2.1.5. Wavelength Policy Constraint.........................8 2.1.5. Wavelength Policy Constraint.........................8
2.1.6. Signal Processing Capability Restriction.............8 2.1.6. Signal Processing Capability Restriction.............8
3. Manageability Considerations...................................8 3. Manageability Considerations ...................................8
3.1. Control of Function and Policy............................8 3.1. Control of Function and Policy............................8
3.2. Information and Data Models, e.g. MIB module..............9 3.2. Information and Data Models, e.g. MIB module..............9
3.3. Liveness Detection and Monitoring.........................9 3.3. Liveness Detection and Monitoring.........................9
3.4. Verifying Correct Operation...............................9 3.4. Verifying Correct Operation...............................9
3.5. Requirements on Other Protocols and Functional Components.9 3.5. Requirements on Other Protocols and Functional Components.9
3.6. Impact on Network Operation..............................10 3.6. Impact on Network Operation..............................10
4. Security Considerations.......................................10 4. Security Considerations .......................................10
5. IANA Considerations...........................................10 5. IANA Considerations ...........................................10
6. Acknowledgments...............................................10 6. Acknowledgments ...............................................10
7. References....................................................10 7. References ....................................................10
7.1. Normative References.....................................10 7.1. Normative References.....................................10
7.2. Informative References...................................11 7.2. Informative References...................................11
Authors' Addresses...............................................12 Authors' Addresses...............................................12
Intellectual Property Statement..................................12 Intellectual Property Statement..................................12
Disclaimer of Validity...........................................13 Disclaimer of Validity...........................................13
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
skipping to change at page 4, line 36 skipping to change at page 4, line 36
high cost, while the number of WDM channels that can be supported in high cost, while the number of WDM channels that can be supported in
a fiber is also limited. As a WSON can be composed of network nodes a fiber is also limited. As a WSON can be composed of network nodes
that cannot perform wavelength conversion, nodes with limited that cannot perform wavelength conversion, nodes with limited
wavelength conversion, and nodes with full wavelength conversion wavelength conversion, and nodes with full wavelength conversion
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. Requirements for Optical impairments will be addressed
in a separate document.
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 [RFC6163] three alternative process architectures were given for
for performing routing and wavelength assignment. These are shown 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
| Processes | WA performed in a | Processes | WA performed in a
+-------------------+ Distributed manner +-------------------+ Distributed manner
(a) (b) (c) (a) (b) (c)
Figure 1 RWA process alternatives. Figure 1 RWA process alternatives.
These alternatives have the following properties and impact on PCEP These alternatives have the following properties and impact on PCEP
requirements in this document. requirements in this document.
1. Combined Processes (R&WA) - Here path selection and wavelength 1. Combined Processes (R&WA) - Here path selection and wavelength
assignment are performed as a single process. The requirements assignment are performed as a single process. The requirements
for PCC-PCE interaction with such a combined RWA process PCE is for PCC-PCE interaction with such a combined RWA process PCE is
addressed in this document. addressed in this document.
2. Routing separate from Wavelength Assignment (R+WA) - Here the 2. Routing separate from Wavelength Assignment (R+WA) - Here the
skipping to change at page 6, line 13 skipping to change at page 6, line 13
are specified in this document. 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. RWA Computation Type and Wavelength Assignment Option 2.1.1. RWA Computation Type and Wavelength Assignment Option
1. The PCReq Message MUST include the path computation type. This 1. The PCReq Message MUST include the path computation type. This
can be: can be:
skipping to change at page 10, line 21 skipping to change at page 10, line 21
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 [RFC5440]. However the additional information within PCEP [RFC5440]. However the additional information
distributed in order to address the RWA problem represents a distributed in order to address the RWA problem represents a
disclosure of network capabilities that an operator may wish to keep disclosure of network capabilities that an operator may wish to keep
private. Consideration should be given to securing this information. private. Consideration 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 This informational document does not make any requests for IANA
codepoint allocation. action.
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
skipping to change at page 11, line 27 skipping to change at page 11, line 27
[RFC5440] 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", RFC 5440, March Element (PCE) communication Protocol", RFC 5440, March
2009. 2009.
[PCEP-MIB] Koushik, K, et al., "PCE communication protocol(PCEP) [PCEP-MIB] Koushik, K, et al., "PCE communication protocol(PCEP)
Management Information Base", draft-ietf-pce-pcep-mib, Management Information Base", draft-ietf-pce-pcep-mib,
work in progress. work in progress.
7.2. Informative References 7.2. Informative References
[WSON-IMP] Lee, Y. and Bernstein, G. (Editors), D. Li and G. [RFC6566] Lee, Y. and Bernstein, G. (Editors), D. Li and G.
Martinelli "A Framework for the Control and Measurement of Martinelli "A Framework for the Control and Measurement of
Wavelength Switched Optical Networks (WSON) with Wavelength Switched Optical Networks (WSON) with
Impairments, draft-ietf-ccamp-wson-impairments, work in Impairments", RFC 6566, March 2012.
progress.
[WSON-Frame] Lee, Y. and Bernstein, G. (Editors), and W. Imajuku, [RFC6163] Y. Lee, G. Bernstein, W. Imajuku, "Framework for GMPLS
"Framework for GMPLS and PCE Control of Wavelength and PCE Control of Wavelength Switched Optical Networks",
Switched Optical Networks", draft-ietf-ccamp-rwa-wson- RFC 6163, April 2011.
framework, 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
Young Lee (Ed.) Young Lee (Ed.)
 End of changes. 18 change blocks. 
27 lines changed or deleted 26 lines changed or added

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