draft-ietf-pce-wson-rwa-ext-16.txt   draft-ietf-pce-wson-rwa-ext-17.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: September 1, 2019 CTTC Expires: September 1, 2019 CTTC
March 1, 2019 March 1, 2019
PCEP Extension for WSON Routing and Wavelength Assignment PCEP Extension for WSON Routing and Wavelength Assignment
draft-ietf-pce-wson-rwa-ext-16 draft-ietf-pce-wson-rwa-ext-17
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).
Path provisioning in WSONs requires a routing and wavelength Path 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 36 skipping to change at page 2, line 36
1. Terminology....................................................3 1. Terminology....................................................3
2. Requirements Language..........................................3 2. Requirements Language..........................................3
3. Introduction...................................................3 3. Introduction...................................................3
4. Encoding of a RWA Path Request.................................6 4. Encoding of a RWA Path Request.................................6
4.1. Wavelength Assignment (WA) Object.........................7 4.1. Wavelength Assignment (WA) Object.........................7
4.2. Wavelength Selection TLV..................................9 4.2. Wavelength Selection TLV..................................9
4.3. Wavelength Restriction Constraint TLV.....................9 4.3. Wavelength Restriction Constraint TLV.....................9
4.3.1. Link Identifier Field...............................12 4.3.1. Link Identifier Field...............................12
4.3.2. Wavelength Restriction Field........................14 4.3.2. Wavelength Restriction Field........................14
4.4. Signal Processing Capability Restrictions................15 4.4. Signal Processing Capability Restrictions................15
4.4.1. Signal Processing Exclusion.........................17 4.4.1. Signal Processing Exclusion.........................16
4.4.2. Signal Processing Inclusion.........................18 4.4.2. Signal Processing Inclusion.........................18
5. Encoding of a RWA Path Reply..................................19 5. Encoding of a RWA Path Reply..................................19
5.1. Wavelength Allocation TLV................................19 5.1. Wavelength Allocation TLV................................19
5.2. Error Indicator..........................................21 5.2. Error Indicator..........................................20
5.3. NO-PATH Indicator........................................21 5.3. NO-PATH Indicator........................................21
6. Manageability Considerations..................................22 6. Manageability Considerations..................................22
6.1. Control of Function and Policy...........................22 6.1. Control of Function and Policy...........................22
6.2. Liveness Detection and Monitoring........................22 6.2. Liveness Detection and Monitoring........................22
6.3. Verifying Correct Operation..............................22 6.3. Verifying Correct Operation..............................22
6.4. Requirements on Other Protocols and Functional Components23 6.4. Requirements on Other Protocols and Functional Components22
6.5. Impact on Network Operation..............................23 6.5. Impact on Network Operation..............................23
7. Security Considerations.......................................23 7. Security Considerations.......................................23
8. IANA Considerations...........................................23 8. IANA Considerations...........................................23
8.1. New PCEP Object: Wavelength Assignment Object............23 8.1. New PCEP Object: Wavelength Assignment Object............23
8.2. WA Object Flag Field.....................................24 8.2. WA Object Flag Field.....................................23
8.3. New PCEP TLV: Wavelength Selection TLV...................24 8.3. New PCEP TLV: Wavelength Selection TLV...................24
8.4. New PCEP TLV: Wavelength Restriction Constraint TLV......24 8.4. New PCEP TLV: Wavelength Restriction Constraint TLV......24
8.5. Wavelength Restriction Constraint TLV Action Values......25 8.5. Wavelength Restriction Constraint TLV Action Values......25
8.6. New PCEP TLV: Wavelength Allocation TLV..................25 8.6. New PCEP TLV: Wavelength Allocation TLV..................25
8.7. Wavelength Allocation TLV Flag Field.....................26 8.7. Wavelength Allocation TLV Flag Field.....................25
8.8. New PCEP TLV: Optical Interface Class List TLV...........26 8.8. New PCEP TLV: Optical Interface Class List TLV...........26
8.9. New PCEP TLV: Client Signal TLV..........................27 8.9. New PCEP TLV: Client Signal TLV..........................26
8.10. New No-Path Reasons.....................................27 8.10. New No-Path Reasons.....................................27
8.11. New Error-Types and Error-Values........................27 8.11. New Error-Types and Error-Values........................27
8.12. New Subobjects for the Exclude Route Object.............28 8.12. New Subobjects for the Exclude Route Object.............28
8.13. New Subobjects for the Include Route Object.............28 8.13. New Subobjects for the Include Route Object.............28
8.14. Request for Updated Note for LMP TE Link Object Class Type 8.14. Request for Updated Note for LMP TE Link Object Class Type
..............................................................29 ..............................................................28
9. Acknowledgments...............................................29 9. Acknowledgments...............................................29
10. References...................................................29 10. References...................................................29
10.1. Normative References....................................29 10.1. Normative References....................................29
10.2. Informative References..................................30 10.2. Informative References..................................30
11. Contributors.................................................32 11. Contributors.................................................32
Authors' Addresses...............................................33 Authors' Addresses...............................................33
1. Terminology 1. Terminology
This document uses the terminology defined in [RFC4655], and This document uses the terminology defined in [RFC4655], and
skipping to change at page 15, line 18 skipping to change at page 15, line 18
3 - Exclusive Range 3 - Exclusive Range
4 - Bitmap Set 4 - Bitmap Set
Num Labels (12 bits): It is generally the number of labels. It has a Num Labels (12 bits): It is generally the number of labels. It has a
specific meaning depending on the action value. specific meaning depending on the action value.
Length (16 bits): It is the length in bytes of the entire Wavelength Length (16 bits): It is the length in bytes of the entire Wavelength
Restriction field. Restriction field.
The Identifier has a specific PCEP context. To clarify the Identifier (9 bits): The Identifier is always set to 0. If PCC
interpretation of the Identifier, the following additional receives the value of the identifier other than 0, it will ignore.
explanation is added.
Identifier (9 bits): The value to be included in the "Identifier"
field of the WDM label in RSVP-TE signaling, as defined in section
3.2 of [RFC6205]. The PCC MAY use the assigned value for the
Identifier field in the corresponding LSP-related messages in RSVP-
TE signaling. The Identifier is always set to 0. If PCC receives the
value of the identifier other than 0, it will ignore.
See Sections 2.6.1 - 2.6.3 of [RFC7579] for details on additional See Sections 2.6.1 - 2.6.3 of [RFC7579] for details on additional
field discussion for each action. field discussion for each action.
4.4. Signal Processing Capability Restrictions 4.4. Signal Processing Capability Restrictions
Path computation for WSON includes checking of signal processing Path computation for WSON includes checking of signal processing
capabilities at each interface against requested capability; the PCE capabilities at each interface against requested capability; the PCE
MUST have mechanisms to know the signal processing capabilities at MUST have mechanisms to know the signal processing capabilities at
each interface, e.g. by means of the Traffic Engineering Database each interface, e.g. by means of the Traffic Engineering Database
 End of changes. 9 change blocks. 
18 lines changed or deleted 10 lines changed or added

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