draft-ietf-pce-wson-rwa-ext-07.txt | draft-ietf-pce-wson-rwa-ext-08.txt | |||
---|---|---|---|---|
Network Working Group Y. Lee, Ed. | Network Working Group Y. Lee, Ed. | |||
Internet Draft Huawei Technologies | Internet Draft Huawei Technologies | |||
Intended status: Standard Track R. Casellas, Ed. | Intended status: Standard Track R. Casellas, Ed. | |||
Expires: May 20, 2018 CTTC | Expires: November 14, 2018 CTTC | |||
November 20, 2017 | May 14, 2018 | |||
PCEP Extension for WSON Routing and Wavelength Assignment | PCEP Extension for WSON Routing and Wavelength Assignment | |||
draft-ietf-pce-wson-rwa-ext-07.txt | draft-ietf-pce-wson-rwa-ext-08.txt | |||
Abstract | Abstract | |||
This document provides the Path Computation Element communication | This document provides the Path Computation Element communication | |||
Protocol (PCEP) extensions for the support of Routing and Wavelength | Protocol (PCEP) extensions for the support of Routing and Wavelength | |||
Assignment (RWA) in Wavelength Switched Optical Networks (WSON). | Assignment (RWA) in Wavelength Switched Optical Networks (WSON). | |||
Lightpath provisioning in WSONs requires a routing and wavelength | Lightpath provisioning in WSONs requires a routing and wavelength | |||
assignment (RWA) process. From a path computation perspective, | assignment (RWA) process. From a path computation perspective, | |||
wavelength assignment is the process of determining which wavelength | wavelength assignment is the process of determining which wavelength | |||
can be used on each hop of a path and forms an additional routing | can be used on each hop of a path and forms an additional routing | |||
skipping to change at page 2, line 7 ¶ | skipping to change at page 2, line 7 ¶ | |||
Internet-Drafts are draft documents valid for a maximum of six | Internet-Drafts are draft documents valid for a maximum of six | |||
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 May 20, 2018. | This Internet-Draft will expire on November 14, 2018. | |||
Copyright Notice | Copyright Notice | |||
Copyright (c) 2016 IETF Trust and the persons identified as the | Copyright (c) 2017 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 22, line 24 ¶ | skipping to change at page 22, line 24 ¶ | |||
(http://www.iana.org/assignments/pcep/pcep.xhtml#pcep-error-object). | (http://www.iana.org/assignments/pcep/pcep.xhtml#pcep-error-object). | |||
Error- Meaning Error-Value Reference | Error- Meaning Error-Value Reference | |||
Type | Type | |||
--------------------------------------------------------------- | --------------------------------------------------------------- | |||
TDB WSON RWA Error 1: Insufficient [This.I-D] | TDB WSON RWA Error 1: Insufficient [This.I-D] | |||
Memory | Memory | |||
2: RWA computation {This.I-D] | 2: RWA computation {This.I-D] | |||
Not supported | N o t u s p p o r e t d | |||
9. Acknowledgments | 9. 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. | |||
This document was prepared using 2-Word-v2.0.template.dot. | This document was prepared using 2-Word-v2.0.template.dot. | |||
10. References | 10. References | |||
10.1. Informative References | 10.1. Informative References | |||
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | |||
Requirement Levels", BCP 14, RFC 2119, March 1997. | Requirement Levels", BCP 14, RFC 2119, March 1997. | |||
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group | [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group | |||
MIB", RFC 2863, June 2000. | MIB", RFC 2863, June 2000. | |||
[RFC4003] Berger, L., "GMPLS Signaling Procedure for Egress Control", | [RFC4003] Berger, L., "GMPLS Signaling Procedure for Egress | |||
RFC 4003, February 2005. | Control", RFC 4003, February 2005. | |||
[RFC4655] Farrel, A., Vasseur, J., and J. Ash, "A Path Computation | [RFC4655] Farrel, A., Vasseur, J., and J. Ash, "A Path Computation | |||
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 | |||
End of changes. 7 change blocks. | ||||
8 lines changed or deleted | 8 lines changed or added | |||
This html diff was produced by rfcdiff 1.46. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ |