--- 1/draft-ietf-ccamp-rwa-wson-encode-23.txt 2014-02-13 16:14:38.092871442 -0800 +++ 2/draft-ietf-ccamp-rwa-wson-encode-24.txt 2014-02-13 16:14:38.160873083 -0800 @@ -1,24 +1,24 @@ Network Working Group G. Bernstein Internet Draft Grotto Networking Intended status: Standards Track Y. Lee -Expires: May 2014 D. Li +Expires: August 2014 D. Li Huawei W. Imajuku NTT - November 13, 2013 + February 13, 2014 Routing and Wavelength Assignment Information Encoding for Wavelength Switched Optical Networks - draft-ietf-ccamp-rwa-wson-encode-23.txt + draft-ietf-ccamp-rwa-wson-encode-24.txt Status of this Memo This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. @@ -27,25 +27,25 @@ months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html - This Internet-Draft will expire on May 13, 2013. + This Internet-Draft will expire on August 13, 2014. Copyright Notice - Copyright (c) 2013 IETF Trust and the persons identified as the + Copyright (c) 2014 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without @@ -73,56 +73,53 @@ Conventions used in this document The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC-2119 [RFC2119]. Table of Contents 1. Introduction...................................................3 - 1. Terminology....................................................4 + 1.1. Terminology..................................................4 2. Resources, Resource Blocks, and the Resource Pool..............4 2.1. Resource Block Set Field..................................5 3. Resource Accessibility/Availability............................6 3.1. Resource Accessibility Field..............................6 3.2. Resource Wavelength Constraints Field.....................8 3.3. Resource Block Pool State (RBPoolState) Field............10 3.4. Resource Block Shared Access Wavelength Availability (RBSharedAccessWaveAvailability) Field........................11 - 4. Resource Signal Constraints and Processing Capabilities.......13 - 4.1. Resource Block Information (ResourceBlockInfo) Field.....13 - 4.2. Shared Input or Output Indication........................14 - 4.3. Optical Interface Class List(s) Field....................14 - 4.3.1. Optical Interface Class Format......................15 - 4.3.2. ITU-G.698.1 Application Code Mapping................16 - 4.3.3. ITU-G.698.2 Application Code Mapping................18 - 4.3.4. ITU-G.959.1 Application Code Mapping................19 - 4.3.5. ITU-G.695 Application Code Mapping..................21 - 4.4. Acceptable Client Signal List Field......................23 - 4.5. Input Bit Rate List Field................................24 - 4.6. Processing Capability List Field.........................24 - 4.6.1. Processing Capabilities Field.......................24 + 4. Resource Block Information (ResourceBlockInfo) Field..........13 + 4.1. Optical Interface Class List Subfield....................15 + 4.1.1. ITU-G.698.1 Application Code Mapping.............16 + 4.1.2. ITU-G.698.2 Application Code Mapping.............18 + 4.1.3. ITU-G.959.1 Application Code Mapping.............19 + 4.1.4. ITU-G.695 Application Code Mapping...............22 + 4.2. Acceptable Client Signal List Subfield...................24 + 4.3. Input Bit Rate List Subfield.............................24 + 4.4. Processing Capability List Subfield......................25 5. Security Considerations.......................................26 - 6. IANA Considerations...........................................26 - 7. Acknowledgments...............................................26 - APPENDIX A: Encoding Examples....................................27 - A.1. Wavelength Converter Accessibility Field.................27 - A.2. Wavelength Conversion Range Field........................28 - A.3. An OEO Switch with DWDM Optics...........................29 - 8. References....................................................32 - 8.1. Normative References.....................................32 - 8.2. Informative References...................................32 - 9. Contributors..................................................34 - Authors' Addresses...............................................35 - Intellectual Property Statement..................................36 - Disclaimer of Validity...........................................37 + 6. IANA Considerations...........................................27 + 6.1. Types for subfields of WSON Resource Block Information...27 + 7. Acknowledgments...............................................27 + APPENDIX A: Encoding Examples....................................28 + A.1. Wavelength Converter Accessibility Field.................28 + A.2. Wavelength Conversion Range Field........................29 + A.3. An OEO Switch with DWDM Optics...........................30 + 8. References....................................................33 + 8.1. Normative References.....................................33 + 8.2. Informative References...................................33 + 9. Contributors..................................................35 + Authors' Addresses...............................................36 + Intellectual Property Statement..................................37 + Disclaimer of Validity...........................................38 1. Introduction A Wavelength Switched Optical Network (WSON) is a Wavelength Division Multiplexing (WDM) optical network in which switching is performed selectively based on the center wavelength of an optical signal. [RFC6163] describes a framework for Generalized Multiprotocol Label Switching (GMPLS) and Path Computation Element (PCE) control of a @@ -134,31 +131,31 @@ This document provides efficient encodings of information needed by the routing and wavelength assignment (RWA) process in a WSON. Such encodings can be used to extend GMPLS signaling and routing protocols. In addition these encodings could be used by other mechanisms to convey this same information to a path computation element (PCE). Note that since these encodings are relatively efficient they can provide more accurate analysis of the control plane communications/processing load for WSONs looking to utilize a GMPLS control plane. -1. Terminology +1.1. Terminology Refer to [RFC6163] for CWDM, DWDM, RWA, WDM. Refer to Section 5 of [Gen-Encode] for the terminology of Resources, Resources Blocks, and Resource Pool. 2. Resources, Resource Blocks, and the Resource Pool This section provides encodings for the information elements defined - in [RWA-INFO] that have applicability to WSON. The encodings are + in [RWA-Info] that have applicability to WSON. The encodings are designed to be suitable for use in the GMPLS routing protocols OSPF [RFC4203] and IS-IS [RFC5307] and in the PCE protocol (PCEP) [RFC5440]. Note that the information distributed in [RFC4203] and [RFC5307] is arranged via the nesting of sub-TLVs within TLVs and this document defines elements to be used within such constructs. Specific constructs of sub-TLVs and the nesting of sub-TLVs of the information element defined by this document will be defined in the respective protocol enhancement documents. This document defines the following information elements pertaining @@ -253,21 +250,21 @@ pool in relation to the switching device. In particular it indicates the ability of an input port to reach sets of resources and of sets of resources to reach a particular output port. This is the PoolInputMatrix and PoolOutputMatrix of [RWA-Info]. The Resource Accessibility is defined by: 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - | Reserved |C| Reserved | + |Reserved(8bits)|C| Reserved (23 bits) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Input Link Set Field A #1 | : : +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | RB Set Field A #1 | : : +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Additional Link set and RB set pairs as needed to | : specify PoolInputMatrix : +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ @@ -471,114 +468,136 @@ Indicates the wavelengths currently available (not being used) on the input fiber to this resource block. This field is encoded via the Label Set field of [Gen-Encode]. Output Available Wavelength Set Field: Indicates the wavelengths currently available (not being used) on the output fiber from this resource block. This field is encoded via the Label Set field of [Gen-Encode]. -4. Resource Signal Constraints and Processing Capabilities +4. Resource Block Information (ResourceBlockInfo) Field - Within a WSON network element (NE) there may be resources with - signal compatibility constraints. These resources be regenerators, - wavelength converters, etc... Such resources may also constitute the - network element as a whole as in the case of an electro optical - switch. This section primarily focuses on the signal compatibility - and processing properties of such a resource block. + As defined in [RWA-INFO], the Resource Block Information + field is used to represent resource signal + constraints and processing capabilities of a node. - The fundamental properties of a resource block, such as a - regenerator or wavelength converter, are: + The fundamental properties of a resource block are: (a) Optical Interface Class List(s) (b) Acceptable Client Signal (shared input, modulation, FEC, bit rate, G-PID) (c) Input Bit Rate (d) Processing Capabilities (number of resources in a block, regeneration, performance monitoring, vendor specific) -4.1. Resource Block Information (ResourceBlockInfo) Field - - Resource Block information fields are used to convey relatively - static information about individual resource blocks including the - resource block compatibility properties, processing properties, and - the number of resources in a block. + ResourceBlockInfo fields are used to convey relatively static + information about individual resource blocks including the resource + block properties and the number of resources in a block. - There can be more than one Resource Block field as resources are - packaged together in blocks of similar devices and its - characteristics. + When more than one ResourceBlockInfo field is used, there are no + ordering requirements amongst these fields. - This field has the following format: + This ResourceBlockInfo field has the following format: 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | RB Set Field | : : +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |I|O| Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - | Optical Interface Class List(s) (opt) | - : : - +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - | Acceptable Client Signal Type (opt) | - : : + | Optional subfield 1 | + : ... : +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - | Input Bit Rate List (opt) | - : : + : : : + : : : +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - | Processing Capabilities List (opt) | + | Optional subfield N | : : +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ RB Set Field is described in Section 2.1. - 4.2. Shared Input or Output Indication - The shared input or output indication is indicated by the first bit (I) and the second bit (O): where I and O are set to 1 if the resource blocks identified in the RB set field utilized a shared fiber for input/output access and set to 0 otherwise. - 4.3. Optical Interface Class List(s) Field + Zero or more Optional subfields MAY be present. Optional subfields + have following format: - The list of Optical Interface Class Field has the following format: + 0 1 2 3 + 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | Type | Length | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | Value... | + . . + . . + . . + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + + The Length field defines the length of the value portion in bytes + (thus a subfield with no value portion would have a length of zero). + The subfield is padded to four-byte alignment; padding is not + included in the Length field (so a three byte value would have a + length of three, but the total size of the subfield would be eight + byte). Unrecognized types are not processed. If multiple subfields + of the same type are present, only the first of the type SHOULD be + processed. + + The following subfield Types are defined: + + Value Length Sub-TLV Type + + 1 variable Optical Interface Class List + 2 variable Acceptable Client Signal List + 3 variable Input Bit Rate List + 4 variable Processing Capability List + + See the IANA Considerations section for allocation of new Types. + +4.1. Optical Interface Class List Subfield + + The list of Optical Interface Class subfield has the following + format: 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - | Type | Length | Reserved |I|E| + | Reserved |I|O| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Optical Interface Classes | : : +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ The following I and E combination are defined: - I E + I O 0 0 Invalid 1 0 Optical Interface Class List acceptable in input 0 1 Optical Interface Class List available in output 1 1 Optical Interface Class List available on both input and output. The Resource Block MAY contain one or more lists according to input/output flags. - 4.3.1. Optical Interface Class Format + The Optical Interface Classes Format is defined as follows: 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |S| Reserved | OI Code Points | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Optical Interface Class | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Optical Interface Class (Cont.) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ @@ -609,21 +627,21 @@ 2: [ITU-G.698.2] application code. 3: [ITU-G.959.1] application code. 4: [ITU-G.695] application code. In case of ITU Application Code, the mapping between the string defining the application code and the 64 bits number implementing the optical interface class is given in the following sections. - 4.3.2. ITU-G.698.1 Application Code Mapping + 4.1.1. ITU-G.698.1 Application Code Mapping Recommendation ITU-G.698.1 defines the Application Codes: DScW- ytz(v) and B-DScW-ytz(v). Where: B: means Bidirectionals. D: means a DWDM application. S: take values N (narrow spectral excursion), W (wide spectral excursion). @@ -659,36 +677,36 @@ reported above): B: = 1 bidirectional, 0 otherwise D (prefix): = 0 reserved, = 1 (D) S: = 0 (N), = 1 (W) c: Channel Spacing, 4 bits mapped according to same definition in [RFC6205] (note that DWDM spacing apply here) - W: = 0 reserved, = 2 (S), = 3 (L) y: = 0 reserved, = 1 (1), = 2 (2) t: = 0 reserved, = 4 (D) z: = 0 reserved, = 2 (2), = 3 (3), = 5 (5) + v: = 0 reserved, = 1 (S), = 2 (C), = 3 (L) F (suffix): = 0 reserved, = 1 Fec Encoding Values not mentioned here are not allowed in this application code, the last 32 bits are reserved and shall be set to zero. - 4.3.3. ITU-G.698.2 Application Code Mapping + 4.1.2. ITU-G.698.2 Application Code Mapping Recommendation ITU-G.698.2 defines the Application Codes: DScW- ytz(v) and B-DScW-ytz(v). B: means Bidirectional. D: means a DWDM application. S: take values N (narrow spectral excursion), W (wide spectral excursion). @@ -740,21 +758,21 @@ z: = 0 reserved, = 2 (2), = 3 (3), = 5 (5) v: = 0 reserved, = 1 (S), = 2 (C), = 3 (L) F (suffix): = 0 reserved, = 1 Fec Encoding Values not mentioned here are not allowed in this application code, the last 32 bits are reserved and shall be set to zero. - 4.3.4. ITU-G.959.1 Application Code Mapping + 4.1.3. ITU-G.959.1 Application Code Mapping Recommendation ITU-G.959.1 defines the Application Codes: PnWx-ytz and BnWx-ytz. Where: P,B: when present indicate Plural or Bidirectional n: maximum number of channels supported by the application code (i.e. an integer number) W: take values I (intra-office), S (short-haul), L (long-haul), V @@ -820,21 +839,21 @@ suffix is an 6 bit, bit map: 0 1 2 3 4 5 +-+-+-+-+-+-+ |F|D|E|r|a|b| +-+-+-+-+-+-+ where a 1 in the appropriate slot indicates that the corresponding suffix has been added. - 4.3.5. ITU-G.695 Application Code Mapping + 4.1.4. ITU-G.695 Application Code Mapping Recommendation [ITU-G.695] defines the Application Codes: CnWx-ytz and B-CnWx-ytz and S-CnWx-ytz. Where the optional prefixed are: B: Bidirectional S: a system using a black link approach @@ -894,82 +913,91 @@ suffix is an 6 bit, bit map: 0 1 2 3 4 5 +-+-+-+-+-+-+ |F|0|0|0|0|0| +-+-+-+-+-+-+ where a 1 in the appropriate slot indicates that the corresponding suffix has been added. -4.4. Acceptable Client Signal List Field +4.2. Acceptable Client Signal List Subfield - This field contains a list of acceptable input client signal types. + This subfield contains a list of acceptable input client signal + types. The acceptable client signal list is a list of Generalized Protocol - Identifiers (G-PIDs). G-PIDs are assigned by IANA and many are - defined in [RFC3471] and [RFC4328]. + Identifiers (G-PIDs). 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - | Number of G-PIDs | G-PID #1 | + | Reserved | Number of G-PIDs | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + | G-PID #1 | G-PID #2 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ : | : +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | G-PID #N | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - Where the number of G-PIDs is an integer greater than or equal to - one. + Type (16 bits): identifies the Acceptable Client Signal List field. -4.5. Input Bit Rate List Field + Length (16 bits): The Length field defines the length of the value + portion in octets. - This field contains a list of bit rate of each input client signal - types specified in the Input Client Signal List. + The number of G-PIDs is an integer greater than or equal to one. + + G-PIDs are assigned by IANA and many are defined in [RFC3471] and + [RFC4328]. + +4.3. Input Bit Rate List Subfield + + This subfield contains a list of bit rate of each input client + signal types specified in the Input Client Signal List. The number of Input Bit Rate MUST match the number of G-PID. 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Input Bit Rate of G-PID #1 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ : : +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Input Bit Rate of G-PID #N | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ -4.6. Processing Capability List Field + Input Bit Rates are in IEEE floating point format [IEEE]. - This field contains a list of resource processing capabilities. +4.4. Processing Capability List Subfield + + This subfield contains a list of resource processing capabilities. The processing capability list field is a list of capabilities that can be achieved through the referred resources: 1. Regeneration capability 2. Fault and performance monitoring 3. Vendor Specific capability Note that the code points for Fault and performance monitoring and vendor specific capability are subject to further study. - 4.6.1. Processing Capabilities Field - - The processing capability field is then given by: + The processing capability list field is then given by: 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - | Processing Cap ID | Length | + | Reserved | Processing Cap ID | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Possible additional capability parameters depending upon | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ : the processing ID : +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ When the processing Cap ID is "regeneration capability", the following additional capability parameters are provided in the following field: @@ -993,43 +1021,67 @@ C=0: Reserved C=1: Fixed Regeneration Point C=2: Selective Regeneration Point Note that when the capability of regenerator is indicated to be Selective Regeneration Pools, regeneration pool properties such as input and output restrictions and availability need to be specified. - This encoding is to be determined in the later revision. + The code point for this is subject to further study. 5. Security Considerations This document defines protocol-independent encodings for WSON information and does not introduce any security issues. However, other documents that make use of these encodings within protocol extensions need to consider the issues and risks associated with, inspection, interception, modification, or spoofing of any of this information. It is expected that any such documents will describe the necessary security measures to provide adequate protection. A general discussion on security in GMPLS networks can be found in [RFC5920]. 6. IANA Considerations - This document provides general protocol independent information - encodings. There is no IANA allocation request for the information - elements defined in this document. IANA allocation requests will be + IANA allocation requests for protocol dependent encodings will be addressed in protocol specific documents based on the encodings defined here. + This document introduces a new registry for GMPLS routing parameters + for WSON encoding. This new IANA registry will be created to make + the assignment of a new type and new values for the new "GMPLS + Routing Parameters for WSON." + +6.1. Types for subfields of WSON Resource Block Information + + Under this new GMPLS Routing Parameters for WSON, a new IANA + registry will be created for nested subfields of the Resource Block + Information field to create a new section named "Types for subfields + of WSON Resource Block Information" and allocate new values as + follows: + + Value Length Sub-TLV Type Reference + + 0 Reserved + 1 variable Optical Interface Class List [This.I-D] + 2 variable Acceptable Client + Signal List [This.I-D] + 3 variable Input Bit Rate List [This.I-D] + 4 variable Processing Capability List [This.I-D] + 5-65535 Unassigned + + Types are to be assigned via Standards Action as defined in + [RFC5226]. + 7. Acknowledgments This document was prepared using 2-Word-v2.0.template.dot. APPENDIX A: Encoding Examples A.1. Wavelength Converter Accessibility Field Example: @@ -1238,40 +1290,34 @@ : (All output links connect to resource) : +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 8. References 8.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. - [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, - "Structure of Management Information Version 2 (SMIv2)", - STD 58, RFC 2578, April 1999. - [RFC4328] Papadimitriou, D., Ed., "Generalized Multi-Protocol Label Switching (GMPLS) Signaling Extensions for G.709 Optical Transport Networks Control", RFC 4328, January 2006. - [RWA-Info] G. Bernstein, Y. Lee, D. Li, W. Imajuku, "Routing and - Wavelength Assignment Information Model for Wavelength - Switched Optical Networks", work in progress: draft-ietf- - ccamp-rwa-info. - [Gen-Encode] G. Bernstein, Y. Lee, D. Li, W. Imajuku, "General Network Element Constraint Encoding for GMPLS Controlled Networks", work in progress: draft-ietf-ccamp-general- constraint-encode. 8.2. Informative References + [IEEE] IEEE, "IEEE Standard for Binary Floating-Point + Arithmetic", Standard 754-1985, 1985 (ISBN 1-5593-7653-8). + [G.694.1] ITU-T Recommendation G.694.1, Spectral grids for WDM applications: DWDM frequency grid, June 2002. [G.694.2] ITU-T Recommendation G.694.2, Spectral grids for WDM applications: CWDM wavelength grid, December 2003. [G.695] ITU-T Recommendation G.695, Optical interfaces for coarse wavelength division multiplexing applications, October, 2010. @@ -1298,20 +1344,25 @@ Networks", RFC 5920, July 2010. [RFC6205] T. Otani, H. Guo, K. Miyazaki, D. Caviglia, "Generalized Labels for G.694 Lambda-Switching Capable Label Switching Routers", RFC 6205, March 2011. [RFC6163] Y. Lee, G. Bernstein, W. Imajuku, "Framework for GMPLS and PCE Control of Wavelength Switched Optical Networks", RFC 6163, April 2011. + [RWA-Info] G. Bernstein, Y. Lee, D. Li, W. Imajuku, "Routing and + Wavelength Assignment Information Model for Wavelength + Switched Optical Networks", work in progress: draft-ietf- + ccamp-rwa-info. + 9. Contributors Diego Caviglia Ericsson Via A. Negrone 1/A 16153 Genoa Italy Phone: +39 010 600 3736 Email: diego.caviglia@ericsson.com