draft-ietf-pce-wson-routing-wavelength-03.txt   draft-ietf-pce-wson-routing-wavelength-04.txt 
Network Working Group Y. Lee Network Working Group Y. Lee
Internet Draft Huawei Internet Draft Huawei
Intended status: Informational Intended status: Informational
Expires: May 2011 G. Bernstein Expires: September 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
November 24, 2010 March 10, 2011
PCEP Requirements for WSON Routing and Wavelength Assignment PCEP Requirements for WSON Routing and Wavelength Assignment
draft-ietf-pce-wson-routing-wavelength-03.txt draft-ietf-pce-wson-routing-wavelength-04.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 May 24, 2009. This Internet-Draft will expire on September 10, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 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
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 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/reply.........................6 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.........................8
3.4. Verifying Correct Operation...............................9 3.4. Verifying Correct Operation...............................9
skipping to change at page 6, line 14 skipping to change at page 6, line 4
+----------------------------+ +----------------------------+
+-----+ | +-------+ +--+ | +-----+ | +-------+ +--+ |
| | | |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/reply 2.1.1. RWA Computation Type and Wavelength Assignment Option
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: be:
(i) Both Routing and Wavelength Assignment (RWA), or (i) Both Routing and Wavelength Assignment (RWA), or
(ii) Routing only. (ii) Routing only.
This requirement is needed to differentiate between the currently This requirement is needed to differentiate between the currently
supported routing with distributed wavelength assignment option and supported routing with distributed wavelength assignment option and
combined RWA. In case of distributed wavelength assignment option, combined RWA. In case of distributed wavelength assignment option,
wavelength assignment will be performed at each node of the route. wavelength assignment will be performed at each node of the route.
2. The PCRep Message MUST include the route, wavelengths assigned to 2. When the PCReq Message is RWA path computation type, the PCReq
the route (i.e., each hop of the route must be assigned a Message MUST further include the wavelength assignment options. At
wavelength). the minimum, the following option should be supported:
3. In the case where a valid path is not found, the PCRep Message (i) Explicit Label Control (ELC) [RFC4003]
(ii) Non-Explicit labels in the form of Label Sets (This will allow
Distributed WA at a node level where each node would select
the wavelength from the Label Sets)
3. The PCRep Message MUST include the route, wavelengths assigned to
the route and indication of which wavelength assignment option has
been applied (ELC or Label Sets).
4. 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 MUST include why the path is not found (e.g., no route, wavelength
not found, optical quality check failed, etc.) not found, optical quality check failed, etc.)
2.1.2. Bulk RWA path request/reply 2.1.2. Bulk RWA path request/reply
1. The PCReq Message MUST be able to specify an option for bulk RWA 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 path request. Bulk path request is an ability to request a number
of simultaneous RWA path requests. of simultaneous RWA path requests.
2. The PCRep Message MUST include the route, wavelength assigned to 2. The PCRep Message MUST include the route, wavelength assigned to
skipping to change at page 8, line 12 skipping to change at page 8, line 12
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 [RFC5440], a PCEP implementation SHOULD allow configuring the
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 RWA
skipping to change at page 9, line 26 skipping to change at page 9, line 26
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 [RFC5440]. 8.6 of [RFC5440].
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 [RFC5440]. However the additional information distributed
order to address the RWA problem represents a disclosure of network in order to address the RWA problem represents a disclosure of
capabilities that an operator may wish to keep private. Consideration network capabilities that an operator may wish to keep private.
should be given to securing this information. 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 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.
 End of changes. 12 change blocks. 
18 lines changed or deleted 27 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/