draft-ietf-pce-wson-routing-wavelength-04.txt   draft-ietf-pce-wson-routing-wavelength-05.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 2011 G. Bernstein Expires: January 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
March 10, 2011 July 6, 2011
PCEP Requirements for WSON Routing and Wavelength Assignment PCEP Requirements for WSON Routing and Wavelength Assignment
draft-ietf-pce-wson-routing-wavelength-04.txt draft-ietf-pce-wson-routing-wavelength-05.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.
skipping to change at page 1, line 44 skipping to change at page 1, line 44
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 September 10, 2011. This Internet-Draft will expire on September 6, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 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
skipping to change at page 3, line 8 skipping to change at page 3, line 8
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..........................6 2.1.2. Bulk RWA path request/reply..........................6
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.........................7 2.1.5. Wavelength Policy Constraint.........................7
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..............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.........................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...............................9 3.6. Impact on Network Operation...............................9
4. Security Considerations........................................9 4. Security Considerations........................................9
5. IANA Considerations............................................9 5. IANA Considerations............................................9
6. Acknowledgments................................................9 6. Acknowledgments...............................................10
7. References....................................................10 7. References....................................................10
7.1. Normative References.....................................10 7.1. Normative References.....................................10
7.2. Informative References...................................10 7.2. Informative References...................................11
Authors' Addresses...............................................11 Authors' Addresses...............................................11
Intellectual Property Statement..................................12 Intellectual Property Statement..................................12
Disclaimer of Validity...........................................12 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
Element within a Wavelength Division Multiplexing (WDM) network. The Element within a Wavelength Division Multiplexing (WDM) network. The
skipping to change at page 8, line 4 skipping to change at page 8, line 4
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.5. 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.)
2.1.6. Signal Processing Capability Restriction
The PCReq Message MUST be able to specify restrictions for signal
compatibility either on the endpoint or any given link. The following
signal processing capability should be supported at a minimum:
o Modulation Type List
o FEC Type List
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
[RFC5440], a PCEP implementation SHOULD allow configuring the [RFC5440], a PCEP implementation SHOULD allow configuring the
following PCEP session parameters on a PCC: following 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
[RFC5440], a PCEP implementation SHOULD allow configuring the [RFC5440], a PCEP implementation SHOULD allow configuring the
following PCEP session parameters on a PCE: following PCEP session parameters on a PCE:
o The support for WSON RWA. o The support for WSON RWA.
o The maximum number of bulk path requests associated with WSON RWA o The maximum number of bulk path requests associated with WSON
per request message. RWA per request message.
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 3.2. Information and Data Models, e.g. MIB
module module
As this document only concerns the requirements to support WSON RWA, As this document only concerns the requirements to support WSON RWA,
 End of changes. 12 change blocks. 
12 lines changed or deleted 22 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/