draft-ietf-pce-wson-routing-wavelength-08.txt   draft-ietf-pce-wson-routing-wavelength-09.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 2013 G. Bernstein Expires: December 2013 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 18, 2012 June 27, 2013
PCEP Requirements for WSON Routing and Wavelength Assignment PCEP Requirements for WSON Routing and Wavelength Assignment
draft-ietf-pce-wson-routing-wavelength-08.txt draft-ietf-pce-wson-routing-wavelength-09.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 April 18, 2009. This Internet-Draft will expire on April 27, 2009.
Copyright Notice Copyright Notice
Copyright (c) 2012 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
skipping to change at page 6, line 25 skipping to change at page 6, line 25
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:
(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. When the PCReq Message is RWA path computation type, the PCReq 2. When the PCReq Message is RWA path computation type, the PCReq
Message MUST further include the wavelength assignment options. Message MUST further include the wavelength assignment options.
At the minimum, the following option should be supported: At the minimum, the following option should be supported:
(i) Explicit Label Control (ELC) [RFC4003] (i) Explicit Label Control (ELC) [RFC4003]
(ii) Non-Explicit labels in the form of Label Sets (This will (ii) Non-Explicit labels in the form of Label Sets (This will
allow Distributed WA at a node level where each node would allow Distributed WA at a node level where each node would
select the wavelength from the Label Sets) select the wavelength from the Label Sets)
3. The PCRep Message MUST include the route, wavelengths assigned to 3. The PCRep Message MUST include the route, wavelengths assigned to
the route and indication of which wavelength assignment option the route and indication of which wavelength assignment option
has been applied (ELC or Label Sets). has been applied (ELC or Label Sets).
4. In the case where a valid path is not found, the PCRep Message 4. In the case where a valid path is not found, the PCRep Message
skipping to change at page 9, line 36 skipping to change at page 9, line 36
3.3. Liveness Detection and Monitoring 3.3. Liveness Detection and Monitoring
Mechanisms defined in this document do not imply any new liveness Mechanisms defined in this document do not imply any new liveness
detection and monitoring requirements in addition to those already detection and monitoring requirements in addition to those already
listed in section 8.3 of [RFC5440]. listed in section 8.3 of [RFC5440].
3.4. Verifying Correct Operation 3.4. Verifying Correct Operation
Mechanisms defined in this document do not imply any new Mechanisms defined in this document do not imply 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].
3.5. Requirements on Other Protocols and Functional 3.5. Requirements on Other Protocols and Functional
Components Components
The PCE Discovery mechanisms ([RFC5089] and [RFC5088]) may be used The PCE Discovery mechanisms ([RFC5089] and [RFC5088]) may be used
to advertise WSON RWA path computation capabilities to PCCs. to advertise WSON RWA path computation capabilities to PCCs.
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
skipping to change at page 12, line 9 skipping to change at page 12, line 9
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.)
Huawei Technologies Huawei Technologies
1700 Alma Drive, Suite 100 5340 Legacy Drive, Building 3
Plano, TX 75075, USA Plano, TX 75024
Phone: (972) 509-5599 (x2240) USA
Email: ylee@huawei.com Phone: (469) 277-5838
Email: leeyoung@huawei.com
Greg Bernstein (Ed.) Greg Bernstein (Ed.)
Grotto Networking Grotto Networking
Fremont, CA, USA Fremont, CA, USA
Phone: (510) 573-2237 Phone: (510) 573-2237
Email: gregb@grotto-networking.com Email: gregb@grotto-networking.com
Jonas Martensson Jonas Martensson
Acreo Acreo
Email:Jonas.Martensson@acreo.se Email:Jonas.Martensson@acreo.se
 End of changes. 9 change blocks. 
12 lines changed or deleted 13 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/