draft-ietf-pce-wson-routing-wavelength-14.txt   draft-ietf-pce-wson-routing-wavelength-15.txt 
skipping to change at page 1, line 15 skipping to change at page 1, line 15
Expires: April 2015 Grotto Networking Expires: April 2015 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 13, 2014 October 28, 2014
PCEP Requirements for WSON Routing and Wavelength Assignment PCEP Requirements for WSON Routing and Wavelength Assignment
draft-ietf-pce-wson-routing-wavelength-14.txt draft-ietf-pce-wson-routing-wavelength-15.txt
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 and forms an additional routing constraint to optical light
skipping to change at page 2, line 10 skipping to change at page 2, line 10
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
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 reference at any 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 February 13, 2009. This Internet-Draft will expire on April 28, 2009.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 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
skipping to change at page 3, line 7 skipping to change at page 3, line 7
3.6. Wavelength Assignment Preference..........................8 3.6. Wavelength Assignment Preference..........................8
3.7. Signal Processing Capability Restriction..................8 3.7. Signal Processing Capability Restriction..................8
4. Manageability Considerations...................................9 4. Manageability Considerations...................................9
4.1. Control of Function and Policy............................9 4.1. Control of Function and Policy............................9
4.2. Information and Data Models, e.g. MIB module..............9 4.2. Information and Data Models, e.g. MIB module..............9
4.3. Liveness Detection and Monitoring........................10 4.3. Liveness Detection and Monitoring........................10
4.4. Verifying Correct Operation..............................10 4.4. Verifying Correct Operation..............................10
4.5. Requirements on Other Protocols and Functional Components10 4.5. Requirements on Other Protocols and Functional Components10
4.6. Impact on Network Operation..............................10 4.6. Impact on Network Operation..............................10
5. Security Considerations.......................................10 5. Security Considerations.......................................10
6. IANA Considerations...........................................10 6. IANA Considerations...........................................11
7. Acknowledgments...............................................11 7. Acknowledgments...............................................11
8. References....................................................11 8. References....................................................11
8.1. Normative References.....................................11 8.1. Normative References.....................................11
8.2. Informative References...................................11 8.2. Informative References...................................11
Authors' Addresses...............................................12 Authors' Addresses...............................................12
Intellectual Property Statement..................................13 Intellectual Property Statement..................................13
Disclaimer of Validity...........................................13 Disclaimer of Validity...........................................13
1. Introduction 1. Introduction
skipping to change at page 7, line 42 skipping to change at page 7, line 42
b. Re-optimize wavelength(s) keeping the same path b. Re-optimize wavelength(s) keeping the same path
c. Re-optimize allowing both the wavelength and the path to c. Re-optimize allowing both the wavelength and the path to
change change
2. The corresponding response to the re-optimized request MUST 2. The corresponding response to the re-optimized request MUST
provide the re-optimized path and wavelengths even when the provide the re-optimized path and wavelengths even when the
request asked for the path or the wavelength to remain unchanged. request asked for the path or the wavelength to remain unchanged.
3. In case that the new path (i.e., other than the current path) is 3. In case that the new path is not found, the response MUST include
not found, the response MUST include why the path is not found why the path is not found (e.g., network disconnected, wavelength
(e.g., network disconnected, wavelength not found, or both, not found, or both, etc.). Note that 'wavelength not found' may
etc.). Note that 'wavelength not found' may include several sub- include several sub-cases such as wavelength continuity not met,
cases such as wavelength continuity not met, unsupported unsupported FEC/Modulation type, etc.
FEC/Modulation type, etc.
3.5. Wavelength Range Constraint 3.5. Wavelength Range Constraint
For any RWA computation type request, the requester (PCC) MUST be For any RWA computation type request, the requester (PCC) MUST be
allowed to specify a restriction on the wavelengths to be used. The allowed to specify a restriction on the wavelengths to be used. The
requester MAY use this option to restrict the assigned wavelength requester MAY use this option to restrict the assigned wavelength
for explicit label or label set. for explicit label or label set. This restriction may for example
come from the tuning ability of a laser transmitter, any optical
element, or a policy-based restriction.
Note that the requester (e.g., PCC) is not required to furnish any Note that the requester (e.g., PCC) is not required to furnish any
range restrictions. This restriction may for example come from the range restrictions.
tuning ability of a laser transmitter, any optical element, or a
policy-based restriction.
3.6. Wavelength Assignment Preference 3.6. Wavelength Assignment Preference
1. A RWA computation type request MAY include the requester 1. A RWA computation type request MAY include the requester
preference for, e.g., random assignment, descending order, preference for, e.g., random assignment, descending order,
ascending order, etc. A response SHOULD follow the requestor ascending order, etc. A response SHOULD follow the requestor
preference unless it conflicts with operator's policy. preference unless it conflicts with operator's policy.
2. A request for two or more paths MUST allow the requester to 2. A request for two or more paths MUST allow the requester to
include an option constraining the paths to have the same include an option constraining the paths to have the same
skipping to change at page 10, line 9 skipping to change at page 10, line 7
4.2. Information and Data Models, e.g. MIB module 4.2. Information and Data Models, e.g. MIB module
As this document only concerns the requirements to support WSON RWA, As this document only concerns the requirements to support WSON RWA,
no additional MIB module is defined in this document. However, the no additional MIB module is defined in this document. However, the
corresponding solution draft will list the information that should corresponding solution draft will list the information that should
be added to the PCE MIB module defined in [PCEP-MIB]. be added to the PCE MIB module defined in [PCEP-MIB].
4.3. Liveness Detection and Monitoring 4.3. Liveness Detection and Monitoring
Mechanisms defined in this document do not imply any new liveness No new mechanism is defined in this document that implies any new
detection and monitoring requirements in addition to those already liveness detection and monitoring requirements in addition to those
listed in section 8.3 of [RFC5440]. already listed in section 8.3 of [RFC5440].
4.4. Verifying Correct Operation 4.4. Verifying Correct Operation
Mechanisms defined in this document do not imply any new No new mechanism is defined in this document that implies any new
verification requirements in addition to those already listed in verification requirements in addition to those already listed in
section 8.4 of [RFC5440] section 8.4 of [RFC5440]
4.5. Requirements on Other Protocols and Functional Components 4.5. Requirements on Other Protocols and Functional Components
If PCE discovery mechanisms ([RFC5089] and [RFC5088]) were to be If PCE discovery mechanisms ([RFC5089] and [RFC5088]) were to be
extended for technology-specific capabilities, advertising WSON RWA extended for technology-specific capabilities, advertising WSON RWA
path computation capability should be considered. path computation capability should be considered.
4.6. Impact on Network Operation 4.6. Impact on Network Operation
Mechanisms defined in this document do not imply any new network No new mechanism is defined in this document that implies any new
operation requirements in addition to those already listed in network operation requirements in addition to those already listed
section 8.6 of [RFC5440]. in section 8.6 of [RFC5440].
5. Security Considerations 5. 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.
Solutions that address the requirements in this document need to
verify that existing PCEP security mechanisms adequately protect the
additional network capabilities and must include new mechanisms as
necessary.
6. IANA Considerations 6. IANA Considerations
This informational document does not make any requests for IANA This informational document does not make any requests for IANA
action. action.
7. Acknowledgments 7. Acknowledgments
The authors would like to thank Adrian Farrel, Cycil Margaria and The authors would like to thank Adrian Farrel, Cycil Margaria and
Ramon Casellas for many helpful comments that greatly improved the Ramon Casellas for many helpful comments that greatly improved the
contents of this draft. contents of this draft.
 End of changes. 11 change blocks. 
21 lines changed or deleted 25 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/