draft-ietf-pce-wson-routing-wavelength-02.txt   draft-ietf-pce-wson-routing-wavelength-03.txt 
Network Working Group Y. Lee Network Working Group Y. Lee
Internet Draft Huawei Internet Draft Huawei
Intended status: Standard Track Intended status: Informational
Expires: February 2011 G. Bernstein Expires: May 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
August 23, 2010 November 24, 2010
PCEP Requirements for WSON Routing and Wavelength Assignment PCEP Requirements for WSON Routing and Wavelength Assignment
draft-ietf-pce-wson-routing-wavelength-02.txt draft-ietf-pce-wson-routing-wavelength-03.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 December 23, 2010. This Internet-Draft will expire on May 24, 2009.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 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 19 skipping to change at page 3, line 19
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................................................9
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...................................10
Authors' Addresses...............................................11 Authors' Addresses...............................................11
Intellectual Property Statement..................................11 Intellectual Property Statement..................................12
Disclaimer of Validity...........................................12 Disclaimer of Validity...........................................12
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 8, line 18 skipping to change at page 8, line 18
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 [PCEP], a PCEP implementation SHOULD allow configuring the following
PCEP session parameters on a PCC: 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
[PCEP], a PCEP implementation SHOULD allow configuring the following [RFC5440], a PCEP implementation SHOULD allow configuring the
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 synchronized path requests associated with o The maximum number of bulk path requests associated with WSON RWA
WSON RWA per request message. per request message.
o A set of WSON RWA specific policies (authorized sender, request
rate limiter, etc).
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
Extensions to the PCEP MIB module defined in [PCEP-MIB] should be As this document only concerns the requirements to support WSON RWA,
defined, so as to cover the WSON RWA information introduced in this no additional MIB module is defined in this document. However, the
document. A future revision of this document will list the corresponding solution draft will list the information that should be
information that should be added to the MIB module. added to the PCE MIB module defined in [PCEP-MIB].
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 [PCEP]. 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 verification Mechanisms defined in this document do not imply any new verification
requirements in addition to those already listed in section 8.4 of requirements in addition to those already listed in section 8.4 of
[PCEP] [RFC5440]
3.5. Requirements on Other Protocols and 3.5. Requirements on Other Protocols and
Functional Components Functional Components
The PCE Discovery mechanisms ([RFC5089] and [RFC5088]) may be used to The PCE Discovery mechanisms ([RFC5089] and [RFC5088]) may be used to
advertise WSON RWA path computation capabilities to PCCs. 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
operation requirements in addition to those already listed in section operation requirements in addition to those already listed in section
8.6 of [PCEP]. 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 [PCEP]. However the additional information distributed in
order to address the RWA problem represents a disclosure of network order to address the RWA problem represents a disclosure of network
capabilities that an operator may wish to keep private. Consideration capabilities that an operator may wish to keep private. Consideration
should be given to securing this information. should be given to securing this information.
5. IANA Considerations 5. IANA Considerations
skipping to change at page 10, line 32 skipping to change at page 10, line 32
Element (PCE)-Based Architecture", RFC 4655, August 2006. Element (PCE)-Based Architecture", RFC 4655, August 2006.
[RFC4657] Ash, J. and J. Le Roux, "Path Computation Element (PCE) [RFC4657] Ash, J. and J. Le Roux, "Path Computation Element (PCE)
Communication Protocol Generic Requirements", RFC 4657, Communication Protocol Generic Requirements", RFC 4657,
September 2006. September 2006.
[RFC5440] Vasseur, JP., Ed. and JL. Le Roux, Ed., "Path Computation [RFC5440] Vasseur, JP., Ed. and JL. Le Roux, Ed., "Path Computation
Element (PCE) communication Protocol", RFC 5440, March Element (PCE) communication Protocol", RFC 5440, March
2009. 2009.
[PCEP-MIB] Koushik, K, et al., "PCE communication protocol(PCEP)
Management Information Base", draft-ietf-pce-pcep-mib, work
in progress.
7.2. Informative References 7.2. Informative References
[WSON-IMP] Lee, Y. and Bernstein, G. (Editors), D. Li and G. [WSON-IMP] Lee, Y. and Bernstein, G. (Editors), D. Li and G.
Martinelli "A Framework for the Control and Measurement of Martinelli "A Framework for the Control and Measurement of
Wavelength Switched Optical Networks (WSON) with Wavelength Switched Optical Networks (WSON) with
Impairments, draft-ietf-ccamp-wson-impairments, work in Impairments, draft-ietf-ccamp-wson-impairments, work in
progress. progress.
[WSON-Frame] Lee, Y. and Bernstein, G. (Editors), and W. Imajuku, [WSON-Frame] Lee, Y. and Bernstein, G. (Editors), and W. Imajuku,
"Framework for GMPLS and PCE Control of Wavelength Switched "Framework for GMPLS and PCE Control of Wavelength Switched
 End of changes. 12 change blocks. 
20 lines changed or deleted 21 lines changed or added

This html diff was produced by rfcdiff 1.40. The latest version is available from http://tools.ietf.org/tools/rfcdiff/