draft-ietf-pce-wson-routing-wavelength-11.txt   draft-ietf-pce-wson-routing-wavelength-12.txt 
Network Working Group Y. Lee Network Working Group Y. Lee
Internet Draft Huawei Internet Draft Huawei
Intended status: Informational Intended status: Informational
Expires: September 2014 G. Bernstein Expires: October 2014 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
March 11, 2014 April 28, 2014
PCEP Requirements for WSON Routing and Wavelength Assignment PCEP Requirements for WSON Routing and Wavelength Assignment
draft-ietf-pce-wson-routing-wavelength-11.txt draft-ietf-pce-wson-routing-wavelength-12.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 September 11, 2014. This Internet-Draft will expire on September 28, 2014.
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 5 skipping to change at page 3, line 5
Table of Contents Table of Contents
1. Introduction ...................................................3 1. Introduction ...................................................3
2. WSON RWA Processes & Architecture ..............................4 2. WSON RWA Processes & Architecture ..............................4
3. Requirements ...................................................6 3. Requirements ...................................................6
3.1. Path Computation Type Option..............................6 3.1. Path Computation Type Option..............................6
3.2. RWA Processing............................................6 3.2. RWA Processing............................................6
3.3. Bulk RWA Path Request/Reply...............................7 3.3. Bulk RWA Path Request/Reply...............................7
3.4. RWA Path Re-optimization Request/Reply....................7 3.4. RWA Path Re-optimization Request/Reply....................7
3.5. Wavelength Range Constraint...............................7 3.5. Wavelength Range Constraint...............................7
3.6. Wavelength Assignment Preference..........................8 3.6. ability of a laser transmitter, any optical element, or an
policy based restriction. Wavelength Assignment Preference.....8
3.7. Signal Processing Capability Restriction..................8 3.7. Signal Processing Capability Restriction..................8
4. Manageability Considerations ...................................8 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.........................9 4.3. Liveness Detection and Monitoring.........................9
4.4. Verifying Correct Operation...............................9 4.4. Verifying Correct Operation...............................9
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 ...........................................10
7. Acknowledgments ...............................................10 7. Acknowledgments ...............................................10
8. References ....................................................10 8. References ....................................................11
8.1. Normative References.....................................10 8.1. Normative References.....................................11
8.2. Informative References...................................11 8.2. Informative References...................................11
Authors' Addresses...............................................12 Authors' Addresses...............................................12
Intellectual Property Statement..................................12 Intellectual Property Statement..................................13
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
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
skipping to change at page 7, line 45 skipping to change at page 7, line 45
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. provide the re-optimized path and wavelengths.
3. In case that the path is not found, the response MUST include why 3. In case that the path is not found, the response MUST include why
the path is not found (e.g., no route, wavelength not found, both the path is not found (e.g., no route, wavelength not found, both
route and wavelength not found, etc.) route and wavelength not found, etc.)
3.5. Wavelength Range Constraint 3.5. Wavelength Range Constraint
For any RWA computation type request, the requester (PCC) MAY For any RWA computation type request, the requester (PCC) MAY
specify a restriction on the wavelengths to be used. specify a restriction on the wavelengths to be used. The requester
MAY use this option to restrict the assigned wavelenght for Explict
Label or Label Sets.
Note that the requestor (PCC) is NOT required to furnish any range Note that the requestor (e.g., PCC) is NOT required to furnish any
restrictions. This restriction is to be interpreted by the PCE as a range restrictions. This restriction may for example come from the
constraint on the tuning ability of the origination laser tuning
transmitter.
3.6. Wavelength Assignment Preference 3.6. ability of a laser transmitter, any optical element, or an
policy based restriction.
Wavelength Assignment Preference
1. A RWA computation type request MAY include the requestor 1. A RWA computation type request MAY include the requestor
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 2 or more paths (e.g., 1+1 link disjoint paths) MUST 2. A request for 2 or more paths (e.g., 1+1 link disjoint paths) MUST
be able to specify an option constraining the path to have the be able to specify an option constraining the path to have the
same wavelength(s) assigned. same wavelength(s) assigned.
 End of changes. 11 change blocks. 
15 lines changed or deleted 19 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/