Network Working Group                                      G. Bernstein
Internet Draft                                        Grotto Networking
Intended status: Standards Track                                 Y. Lee
Expires: April August 2010                                              D. Li
                                                                 Huawei
                                                             W. Imajuku
                                                                    NTT

                                                        October 8, 2009

                                                      February 18, 2010

        Routing and Wavelength Assignment Information Encoding for
                   Wavelength Switched Optical Networks

                  draft-ietf-ccamp-rwa-wson-encode-03.txt

                  draft-ietf-ccamp-rwa-wson-encode-04.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.

   Internet-Drafts are draft documents valid for a maximum of six 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 April 8, 2007. August 18, 2010.

Copyright Notice

   Copyright (c) 2009 2010 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 (http://trustee.ietf.org/license-info). 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 warranty as
   described in the Simplified BSD License.

Abstract

   A wavelength switched optical network (WSON) requires that certain
   key information elements are made available to facilitate path
   computation and the establishment of label switching paths (LSPs).
   The information model described in "Routing and Wavelength Assignment
   Information for Wavelength Switched Optical Networks" shows what
   information is required at specific points in the WSON.

   The Part of the
   WSON information model contains aspects that may be used in Generalized Multiprotocol Label
   Switching (GMPLS) signaling protocols, and may be distributed by
   GMPLS routing protocols. Other distribution mechanisms (for example,
   XML-based protocols) may also be used. of general
   applicability to other technologies, while other parts are fairly
   specific to WSONs.

   This document provides efficient, protocol-agnostic encodings for the
   WSON specific information elements necessary to operate a WSON. elements. It is intended that
   protocol-specific protocol-
   specific documents will reference this memo to describe how
   information is carried for specific uses. 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).

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.1. Revision History..........................................4
         1.1.1. Changes from 00 draft................................4
         1.1.2. Changes from 01 draft................................4
         1.1.3. Changes from 02 draft................................4 draft................................5
         1.1.4. Changes from 03 draft................................5
   2. Terminology....................................................5
   3. Common Field Encoding..........................................5 WSON Encoding Usage Recommendations............................6
      3.1. Link Set Field............................................5 WSON Node TLV.............................................6
      3.2. Wavelength Information Encoding...........................7
      3.3. Wavelength Set Field......................................8
         3.3.1. Inclusive/Exclusive Wavelength Lists.................9
         3.3.2. Inclusive/Exclusive Wavelength Ranges................9
         3.3.3. Bitmap Wavelength Set...............................10 WSON Dynamic Node TLV.....................................6
   4. Wavelength and Connectivity sub-TLV Encodings.................11 Resource Accessibility/Availability............................6
      4.1. Available Wavelengths Sub-TLV............................11 Resource Block Accessibility Sub-TLV......................8
      4.2. Shared Backup Wavelengths Sub-TLV........................11
      4.3. Connectivity Matrix Sub-TLV..............................11
      4.4. Port Wavelength Restriction sub-TLV......................13
         4.4.1. SIMPLE_WAVELENGTH...................................14
         4.4.2. CHANNEL_COUNT.......................................14
         4.4.3. WAVEBAND1...........................................14
         4.4.4. SIMPLE_WAVELENGTH & CHANNEL_COUNT...................15
   5. Resource Wavelength Converter Constraints Sub-TLV..................10
      4.3. Resource Block Pool Encoding............................15 State Sub-TLV........................10
   5. Resource Properties Encoding..................................12
      5.1. Wavelength Converter Set Field...........................16 Resource Block Information Sub-TLV.......................12
      5.2. Wavelength Converter Accessibility Sub-TLV...............17 Input Modulation Format List Sub-Sub-TLV.................13
         5.2.1. Modulation Format Field.............................13
      5.3. Wavelength Conversion Range Sub-TLV......................18 Input FEC Type List Sub-Sub-TLV..........................15
         5.3.1. FEC Type Field......................................16
      5.4. Wavelength Converter Usage State Sub-TLV.................19 Input Bit Range List Sub-Sub-TLV.........................18
         5.4.1. Bit Range Field.....................................18
      5.5. Input Client Signal List Sub-Sub-TLV.....................19
      5.6. Processing Capability List Sub-Sub-TLV...................20
         5.6.1. Processing Capabilities Field.......................20
      5.7. Output Modulation Format List Sub-Sub-TLV................22
      5.8. Output FEC Type List Sub-Sub-TLV.........................22
   6. WSON Encoding Usage Recommendations...........................20
      6.1. WSON Node TLV............................................20
      6.2. WSON Dynamic Node TLV....................................20
      6.3. WSON Link TLV............................................21
      6.4. WSON Dynamic Link TLV....................................21
   7. Security Considerations.......................................21
   8. Considerations.......................................22
   7. IANA Considerations...........................................21
   9. Acknowledgments...............................................21 Considerations...........................................23
   8. Acknowledgments...............................................23
   APPENDIX A: Encoding Examples....................................22 Examples....................................24
      A.1. Link Set Field...........................................22
      A.2. Wavelength Set Field.....................................22
      A.3. Connectivity Matrix Sub-TLV..............................23
      A.4. Connectivity Matrix with Bi-directional Symmetry.........26
      A.5. Wavelength Converter Accessibility Sub-TLV...............28
      A.6. Sub-TLV...............24
      A.2. Wavelength Conversion Range Sub-TLV......................30
   10. References...................................................32
      10.1. Sub-TLV......................25
      A.3. An OEO Switch with DWDM Optics...........................26
   9. References....................................................29
      9.1. Normative References....................................32
      10.2. References.....................................29
      9.2. Informative References..................................32
   11. Contributors.................................................34 References...................................29
   10. Contributors.................................................31
   Authors' Addresses...............................................34 Addresses...............................................31
   Intellectual Property Statement..................................35 Statement..................................32
   Disclaimer of Validity...........................................36 Validity...........................................33

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.

   [WSON-Frame] describes a framework for Generalized Multiprotocol
   Label Switching (GMPLS) and Path Computation Element (PCE) control of
   a WSON. Based on this framework, [WSON-Info] describes an information
   model that specifies what information is needed at various points in
   a WSON in order to compute paths and establish Label Switched Paths
   (LSPs).

   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.

   Note that encodings of information needed by the routing and label
   assignment process applicable to general networks beyond WSON are
   addressed in a separate document [Gen-Encode].

1.1. Revision History

   1.1.1. Changes from 00 draft

   Edits to make consistent with update to [Otani], i.e., removal of
   sign bit.

   Clarification of TBD on connection matrix type and possibly
   numbering.

   New sections for wavelength converter pool encoding: Wavelength
   Converter Set Sub-TLV, Wavelength Converter Accessibility Sub-TLV,
   Wavelength Conversion Range Sub-TLV, WC Usage State Sub-TLV.

   Added optional wavelength converter pool TLVs to the composite node
   TLV.

   1.1.2. Changes from 01 draft

   The encoding examples have been moved to an appendix. Classified and
   corrected information elements as either reusable fields or sub-TLVs.
   Updated Port Wavelength Restriction sub-TLV. Added available
   wavelength and shared backup wavelength sub-TLVs. Changed the title
   and scope of section 6 to recommendations since the higher level TLVs
   that this encoding will be used in is somewhat protocol specific.

   1.1.3. Changes from 02 draft

   Removed inconsistent text concerning link local identifiers and the
   link set field in section 3.1. field.

   Added E bit to the Wavelength Converter Set Field.

   Added bidirectional connectivity matrix example. Added simple link
   set example. Edited examples for consistency.

   1.1.4. Changes from 03 draft

   Removed encodings for general concepts to [Gen-Encode].

   Added in WSON signal compatibility and processing capability
   information encoding.

2. Terminology

   CWDM: Coarse Wavelength Division Multiplexing.

   DWDM: Dense Wavelength Division Multiplexing.

   FOADM: Fixed Optical Add/Drop Multiplexer.

   ROADM: Reconfigurable Optical Add/Drop Multiplexer. A reduced port
   count wavelength selective switching element featuring ingress and
   egress line side ports as well as add/drop side ports.

   RWA: Routing and Wavelength Assignment.

   Wavelength Conversion. The process of converting an information
   bearing optical signal centered at a given wavelength to one with
   "equivalent" content centered at a different wavelength. Wavelength
   conversion can be implemented via an optical-electronic-optical (OEO)
   process or via a strictly optical process.

   WDM: Wavelength Division Multiplexing.

   Wavelength Switched Optical Network (WSON): A WDM based optical
   network in which switching is performed selectively based on the
   center wavelength of an optical signal.

3. Common Field WSON Encoding Usage Recommendations

   In encoding WSON information both sets this section we give recommendations of links typical usage of the sub-
   TLVs and sets composite TLVs which are based on the high level information
   bundles of [WSON-Info].

3.1. WSON Node TLV

   The WSON Node TLV would consist of
   wavelengths frequently arise. In the following list of sub-TLVs:

   <Node_Info> ::= <Node_ID>[Other GMPLS sub-TLVs]
   [<ResourcePool>][<RBPoolState>]

   Where

   <ResourcePool> ::= <ResourceBlockInfo>...
   [<ResourceBlockAccessibility>...] [<ResourceWaveConstraints>...]

   The encoding of structure and properties of a general resource pool
   utilizes a resource block info sub-TLV (<ResourceBlockInfo> in
   section 5. ), an accessibility sub-TLV (<ResourceBlockAccessibility>
   in section 4.1. ), and a resource pool wavelength constraint sub-TLV
   (<ResourceWaveConstraints> in section 4.2. ).

3.2. WSON Dynamic Node TLV

   If the protocol supports the separation of dynamic information from
   relatively static information then the wavelength converter pool
   state can be separated from the general Node TLV into a dynamic Node
   TLV as follows.

   <NodeInfoDynamic> ::= <NodeID> [<RBPoolState>]

   Where the resource pool state sub-TLV <RBPoolState> is defined in
   section 4.3. Note that currently the only dynamic information modeled
   with a node is associated with the status of the wavelength converter
   pool.

4. Resource Accessibility/Availability

   In this section we specify define the
   encoding sub-TLVs for dealing with accessibility
   and availability of resource blocks. These in include the following
   ResourceBlockAccessibility, ResourceWaveConstraints, and RBPoolState
   sub-TLVs. All these repeatedly used fields.

3.1. Link Set Field

   We sub-TLVs are concerned with sets of resources.

   In a WSON node that includes resource blocks (RB) we will frequently need want to
   denote subsets these blocks to efficiently describe common properties
   the blocks and to describe the structure, if non-trivial, of groups of links. To
   do so efficiently we can make use of the
   resource pool. The RB Set field is defined in a link set concept similar manner to the
   label set concept of [RFC3471].

   The information carried in a Link
   Set RB set field 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
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |    Action     |Dir|  Format     |E|C| Reserved  |        Length                 |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                       Link     RB Identifier 1           |        RB Identifier 2        |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      :                               :                               :
      :                               :                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                       Link     RB Identifier n-1         |        RB Identifier N n        |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

      Action: 8 bits

         0 - Inclusive List

   Indicates that the TLV contains one or more link identifiers RB elements that are
   included in the Link
   Set. Each identifies a separate link that is part of the set.

         1 list.

         2 - Inclusive Range

   Indicates that the Link Set defines TLV contains a range of links.  It RBs.  The object/TLV
   contains two link identifiers. WC elements. The first identifiers element indicates the start of
   the range (inclusive). range. The second identifiers element indicates the end of the range (inclusive). All links with numeric values between the
   bounds are considered to be part of the set. range. A value
   of zero in
   either position indicates that there is no bound on the corresponding portion
   of the range. Note that the Action field can be set

      E (Even bit): Set to
   0x02(Inclusive Range) only when unnumbered link identifier is used.

     Dir: Directionality 0 denotes an odd number of RB identifiers in
   the Link list (last entry zero pad); Set (2 bits)

        0 -- bidirectional to 1 -- ingress

         2 -- egress

   In optical networks we think in terms of unidirectional as well as
   bidirectional links. For example, wavelength restrictions or
   connectivity may be different for denotes an ingress port, than for its
   "companion" egress port if one exists. Note that "interfaces" such as
   those discussed even number of RB
   identifiers in the Interfaces MIB [RFC2863] are assumed list (no zero padding).

      C (Connectivity bit): Set to be
   bidirectional. This also applies 0 to the links advertised denote fixed (possibly multi-
   cast) connectivity; Set to 1 to denote potential (switched)
   connectivity. Used in various
   link state routing protocols.

     Format: resource pool accessibility sub-TLV. Ignored
   elsewhere.

      Reserved: 6 bits

   This field is reserved. It MUST be set to zero on transmission and
   MUST be ignored on receipt.

      Length: 16 bits

   The format total length of the link identifier (6 bits)

   0 -- Link Local Identifier

   Indicates that the links in the Link Set are identified by link local
   identifiers. All link local identifiers are supplied this field in bytes.

      RB Identifier:

   The RB identifier represents the context ID of the advertising node.

   1 -- Local Interface IPv4 Address

  2 -- Local Interface IPv6 Address

   Indicates that resource block which is a
   16 bit integer.

4.1. Resource Block Accessibility Sub-TLV

   This sub-TLV describes the links in structure of the Link Set are identified by Local
   Interface IP Address. All Local Interface IP Address are supplied resource pool in relation
   to the context of the advertising node.

         Others TBD.

   Note that all link identifiers in the same list must be of the same
   type.

     Length: 16 bits

   This field switching device. In particular it indicates the total length in bytes ability of the Link Set field.

     Link Identifier: length is dependent on the link format

   The link identifier represents the an
   ingress port which is being described
   either for connectivity or wavelength restrictions. This can be the
   link local identifier of [RFC4202], GMPLS routing, [RFC4203] GMPLS
   OSPF routing, to reach a resource block and [RFC5307] IS-IS GMPLS routing. The use of the link
   local identifier format can result in more compact WSON encodings
   when the assignments are done in a reasonable fashion.

3.2. Wavelength Information Encoding resource block to
   reach a particular egress port. This document makes frequent use of is the lambda label format PoolIngressMatrix and
   PoolEgressMatrix of [WSON-Info].

   The resource block accessibility sub-TLV is defined
   in [Otani] shown below strictly for reference purposes: 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
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |Grid
      |  C.S. Connectivity  |                    Reserved                   |               n
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                    Ingress Link Set Field A #1                |
      :                                                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                          RB Set Field A #1                    |
      :                                                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |         Additional Link set and RB set pairs as needed to     |
      :                    specify PoolIngressMatrix                  :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                Egress Link Set Field B #1                     |
      :                                                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |             RB Set B Field #1 (for egress connectivity)       |
      :                                                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |         Additional Link Set and RB set pairs as needed to     |
      :                    specify PoolEgressMatrix                   :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Where

   Grid is used

   Connectivity indicates how the ingress/egress ports connect to indicate which ITU-T grid specification the
   resource blocks.

         0 -- the device is being
   used.

   C.S. = Channel spacing used in fixed (e.g. a DWDM system, i.e., with an ITU-T
   G.694.1 grid.

   n = Used to specify connected port must go through
         the frequency as 193.1THz +/- n*(channel spacing)
   and n resource block)

         1 -- the device is switched(e.g., a two's complement integer that takes either port can be configured to
         go through a negative,
   zero or a positive value.

3.3. Wavelength resource but isn't required )

   The Link Set Field

   Wavelength sets come up frequently is defined in WSONs to describe [Gen-Encode].

   Note that the range of
   a laser transmitter, direction parameter within the wavelength restrictions on ROADM ports, or Link Set Field is used
   to indicate whether the availability of wavelengths on a DWDM link. The general format
   for a wavelength link set is given below. This format uses the Action
   concept from [RFC3471] with an additional Action to define a "bit
   map" type of label set. Note that ingress or egress link set,
   and the second 32 bit field bidirectional value for this parameter is a lambda
   label not permitted in
   this sub-TLV.

   See Appendix A.1 for an illustration of this encoding.

4.2. Resource Wavelength Constraints Sub-TLV

   Resources, such as wavelength converters, etc., may have a limited
   input or output wavelength ranges. Additionally, due to the previously defined format. This provides important
   information on structure
   of the WDM grid type and channel spacing that will be
   used in optical system not all wavelengths can necessarily reach or
   leave all the compact encodings listed. resources. These properties are described by using one
   or more resource wavelength restrictions sub-TLVs as defined below:

       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
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      | Action|    Num Wavelengths    |          Length                     RB Set Field                              |
      :                                                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |Grid |  C.S. |    Reserved
      |  n  for lowest frequency                Input Wavelength Set Field                     |
      :                                                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |     Additional fields as necessary per action                 |                Output Wavelength Set Field                    |

   Action:

         0 - Inclusive List

         1 - Exclusive List
         2 - Inclusive Range

         3 - Exclusive Range

         4 - Bitmap
      :                                                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

      RB Set

   Length is the length in bytes Field:

   A set of resource blocks (RBs) which have the entire field.

   3.3.1. Inclusive/Exclusive same wavelength
   restrictions.

      Input Wavelength Lists

   In Set Field:

   Indicates the case wavelength input restrictions of the inclusive/exclusive lists RBs in the
   corresponding RB set.

      Output Wavelength Set Field:

   Indicates the wavelength set
   format is given by:

      0                   1                   2                   3
      0 1 2 3 output restrictions of RBs in the
   corresponding RB set.

4.3. Resource Block Pool State Sub-TLV

   The usage state of a resource is encoded as either a list of 16 bit
   integer values or a bit map indicating whether a single resource is
   available or in use. This information can be relatively dynamic,
   i.e., can change when a connection is established or torn down.

       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
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |0 or 1 | Num Wavelengths       |          Length               |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |Grid
      |  C.S. Action        |    Reserved                                   |    n  for lowest frequency    |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |    n2                         |          n3                     RB Set Field                              |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      :                                                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |    nm                         |                  RB Usage state                               |
      :                                                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Where:

   Num Wavelengths tells us the number of wavelength in this inclusive
   or exclusive

   Where Action = 0 denotes a list including the initial wavelength in the list. Hence
   if the number of wavelengths is even then zero padding of the last
   half word is required.

   n2 - nm, are used to specify the frequency as 193.1THz +/- n*(channel
   spacing) 16 bit integers and is Action = 1
   denotes a two's complement integer. Note that the channel
   spacing is given by C.S. and is the same for all frequencies on the
   list.

   3.3.2. Inclusive/Exclusive Wavelength Ranges bit map. In both cases the case elements of inclusive/exclusive ranges the wavelength set format
   is given by: RB Set field are
   in a one-to-one correspondence with the values in the usage RB usage
   state area.

       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
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |2 or 3
      | Num Wavelengths Action = 0    |             Length    Reserved                                   |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |Grid
      |  C.S.                     RB Set Field                              |    Reserved
      :                                                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |      n  for lowest frequency                  RB#1 state   |      RB#2 state               |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   In this case Num Wavelengths specifies the number of wavelengths in
   the range starting at
      :                                                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                 RB#n-1 state  |   RB#n state or Padding       |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Whether the given last 16 bits is a wavelength and incrementing converter (RB) state or
   padding is determined by the Num
   Wavelengths number of channel spacing up in frequency.

   3.3.3. Bitmap Wavelength Set

   In the case of Action = 4, the bitmap elements in the wavelength RB set format is
   given by: field.

       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
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |  4    |   Num Wavelengths Action = 1    |            Length    Reserved                                   |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |Grid |  C.S. |    Reserved
      |      n  for lowest frequency                     RB Set Field                              |
      :                                                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |    Bit Map Word #1 (Lowest frequency channels)                  RB Usage state bitmap                        |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      :                                                               :

      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |    Bit Map Word #N (Highest frequency channels)                     ......             |      Padding bits    |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Where Num Wavelengths in this case tells us the number

   RB Usage state:  Variable Length but must be a multiple of wavelengths
   represented by the bit map. 4 byes.

   Each bit in indicates the bit map represents a
   particular frequency with a value usage status of 1/0 one RB with 0 indicating whether the
   frequency
   RB is in the set or not. Bit position zero represents the
   lowest frequency, while each succeeding bit position represents the
   next frequency a channel spacing (C.S.) above available and 1 indicating the previous. RB is in used. The size sequence of
   the bit map is Num Wavelengths bits, but the bit map is
   padded out ordered according to a full multiple of 32 bits so that the TLV is RB Set field with this sub-
   TLV.

   Padding bits: Variable Length

5. Resource Properties Encoding

   Within a
   multiple of four bytes. Bits that do not represent wavelengths (i.e.,
   those in positions (Num Wavelengths) and beyond SHOULD be set to zero
   and MUST be ignored.

4. Wavelength and Connectivity sub-TLV Encodings

   A type-length-value (TLV) encoding of the high level WSON information
   model [WSON-Info] is given in the following sections. This encoding
   is designed to network element (NE) there may be suitable for use resources with signal
   compatibility constraints. Such resources typically come in the GMPLS routing protocols
   OSPF [RFC4203] and IS-IS [RFC5307] "blocks"
   which contain a group on identical and in the PCE protocol PCEP
   [PCEP]. Note that indistinguishable individual
   resources. These resource blocks may consist of regenerators,
   wavelength converters, etc... Such resource blocks may also
   constitute the information distributed network element as a whole as in [RFC4203] and
   [RFC5307] is arranged via the nesting case of sub-TLVs within TLVs and an
   electro optical switch. In this document makes use section we focus on the signal
   compatibility and processing properties of such constructs.

4.1. Available Wavelengths Sub-TLV

   To indicate a resource block,
   i.e., <ResourceBlockInfo> of section 3.1.  the wavelengths available for use on accessibility aspects
   of a link resource in a shared pool were encoded in the Available
   Wavelengths sub-TLV consists previous section.

   The fundamental properties of a single variable length wavelength
   set field resource block, such as follows: a regenerator
   or wavelength converter, are:

   (a)Input constraints (modulation, FEC, bit rate, GPID)

   (b)Processing capabilities (number of resources in a block,
        regeneration, performance monitoring, vendor specific)

   (c)Output Constraints (modulation, FEC)

5.1. Resource Block Information Sub-TLV

   Resource Block descriptor sub-TLVs are used to convey relatively
   static information about individual resource blocks including the
   resource block properties of section 3. and the number of resources
   in a block.

   This sub-TLV 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
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                           Wavelength                     RB Set Field                              |
      :                                                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

4.2. Shared Backup Wavelengths
      |           Input Modulation Type List Sub-Sub-TLV  (opt)       |
      :                                                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |           Input FEC Type List Sub-Sub-TLV    (opt)            |
      :                                                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |         Input Client Signal Type Sub-TLV

   To indicate the wavelengths available for shared backup use on a link
   the Shared Backup Wavelengths      (opt)           |
      :                                                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |         Input Bit Rate Range List  Sub-Sub-TLV (opt)          |
      :                                                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |         Processing Capabilities List Sub-Sub-TLV (opt)        |
      :                                                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |         Output Modulation Type List Sub-Sub-TLV  (opt)        |
      :                                                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |         Output FEC Type List Sub-Sub-TLV  (opt)               |
      :                                                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

5.2. Input Modulation Format List Sub-Sub-TLV

   This sub-TLV consists contains a list of acceptable input modulation formats.

   Type := Input Modulation Format List

   Value:= A list of Modulation Format Fields

   5.2.1. Modulation Format Field

   Two different types of modulation format fields are defined: a single variable
   length wavelength set
   standard modulation field as follows: and a vendor specific modulation field.
   Both start with the same 32 bit header shown below.

      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|I|      Modulation ID          |                           Wavelength Set Field        Length               |
     :                                                               :
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

4.3. Connectivity Matrix Sub-TLV

   The switch and fixed connectivity matrices of [WSON-Info] can be
   compactly represented in terms of

   Where S bit set to 1 indicates a minimal list of ingress standardized modulation format and
   egress port S
   bit set pairs that have mutual connectivity. As described in
   [Switch] such a minimal list representation leads naturally to 0 indicates a
   graph representation for path computation purposes that involves vendor specific modulation format. The
   length is the
   fewest additional nodes and links.

   A TLV encoding of this list length in bytes of link the entire modulation type field.

   Where I bit set pairs is:

       0 to 1                   2                   3
       0 indicates it is an input modulation constraint
   and I bit set to 0 indicates it is an output modulation constraint.

   Note that if an output modulation is not specified then it is implied
   that it is the same as the input modulation. In such case, no
   modulation conversion is performed.

   The format for the standardized type for the input modulation is
   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
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |1|1|       Modulation ID         | Connectivity  |   MatrixID    |             Reserved           Length            |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |                         Link Set A #1   Possible additional modulation parameters depending upon    |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     :   the modulation ID                                           :                               :
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

      Modulation ID (S bit = 1); Input modulation (I bit = 1)

   Takes on the following currently defined values:

      0        Reserved

      1        optical tributary signal class NRZ 1.25G

      2        optical tributary signal class NRZ 2.5G

      3        optical tributary signal class NRZ 10G

      4        optical tributary signal class NRZ 40G
      5        optical tributary signal class RZ 40G

   Note that future modulation types may require additional parameters
   in their characterization.

   The format for vendor specific modulation field (for input
   constraint) is 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
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |0|1|  Vendor Modulation ID     |          Length               |                         Link Set B #1                         :
      :                               :                               :
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |                       Additional Link set pairs as needed                       Enterprise Number                       |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     :                     to specify connectivity   Any vendor specific additional modulation parameters        :
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Where

   Connectivity

   Vendor Modulation ID

     This is a vendor assigned identifier for the device modulation type.

         0 -- the device is fixed

         1 -- the device is switched(e.g., ROADM/OXC)

   MatrixID represents the ID

   Enterprise Number

     A unique identifier of the connectivity matrix and is an 8 bit organization encoded as a 32-bit integer. The value of 0xFF is reserved for use with port wavelength
   constraints
     Enterprise Numbers are assigned by IANA and should not be used to identify a connectivity matrix. managed through an IANA
     registry [RFC2578].

   Vendor Specific Additional parameters

     There are two permitted combinations for can be potentially additional parameters characterizing the link set
     vendor specific modulation.

5.3. Input FEC Type List Sub-Sub-TLV

   This sub-TLV contains a list of acceptable FEC types.

   Type := Input FEC Type field parameter
   "dir" for Link Set A and B pairs:

   o  Link Set A dir=ingress, Link Set B dir=egress

     In this case any signal on the ingress links in set A can be
     potentially switched out of an egress link in set B.

   o  Link Set A dir=bidirectional, Link Set B dir=bidirectional

      In this case any ingress signal on the links in set A can
      potentially egress on a link in set B, and any ingress signal on
      the links in set B can potentially egress on a link in set A.

   See Appendix List

   Value:= A for examples of both types list of encodings.

4.4. Port Wavelength Restriction sub-TLV FEC type Fields
   5.3.1. FEC Type Field

   The port wavelength restriction of [WSON-Info] can be encoded as a
   sub-TLV as follows. More than one of these sub-TLVs FEC type Field may be needed to
   fully specify a complex port constraint. When more than one consist of these
   sub-TLVs are present the resulting restriction is the intersection two different formats of
   the restrictions expressed in each sub-TLV. To indicate that fields: a
   restriction applies to the port in general and not to
   standard FEC field or a vendor specific
   connectivity matrix use the reserved value of 0xFF for FEC field. Both start with
   the MatrixID. same 32 bit header shown below.

      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|I|      FEC ID                 |   MatrixID    |  RestrictionType |      Reserved/Parameter        Length               |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |     Additional Restriction Parameters per RestrictionType   Possible additional FEC parameters depending upon           |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     :   the FEC ID                                                  :
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Where:

   MatrixID: either

   Where S bit set to 1 indicates a standardized FEC format and S bit
   set to 0 indicates a vendor specific FEC format. The length is the value
   length in bytes of the corresponding Connectivity
   Matrix sub-TLV or takes the value OxFF entire FEC type field.

   Where I bit set to indicate the restriction
   applies 1 indicates it is an input FEC constraint and I
   bit set to 0 indicates it is an output FEC constraint.

   Note that if an output FEC is not specified then it is implied that
   it is the port regardless of any Connectivity Matrix.

   RestrictionType can take same as the following values and meanings:

         0: SIMPLE_WAVELENGTH  (Simple wavelength selective restriction)

         1: CHANNEL_COUNT (Channel count restriction)

         2: WAVEBAND1 (Waveband device with a tunable center frequency
         and passband)

         3: SIMPLE_WAVELENGTH & CHANNEL_COUNT (Combination of
         SIMPLE_WAVELENGTH and CHANNEL_COUNT restriction. The
         accompanying wavelength set and channel count indicate
         wavelength permitted on the port and the maximum number of
         channels that can be simultaneously used on the port)

   4.4.1. SIMPLE_WAVELENGTH input FEC. In such case, no FEC conversion is
   performed.

   The length is the case length in bytes of the SIMPLE_WAVELENGTH the GeneralPortRestrictions (or
   MatrixSpecificRestrictions) entire FEC type field.

   The format for input standard FEC field is 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
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |1|1|       FEC ID                | MatrixID      | RstType = 0   |             Reserved           Length            |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |                        Wavelength Set Field   Possible additional FEC parameters depending upon           |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   In this case the accompanying wavelength set indicates
     :   the
   wavelengths permitted FEC ID                                                  :
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      Takes on the port.

   4.4.2. CHANNEL_COUNT

   In the case of the CHANNEL_COUNT following currently defined values for the standard
   FEC ID:

      0        Reserved

      1        G.709 RS FEC

      2        G.709V compliant Ultra FEC

      3       G.975.1 Concatenated FEC
              (RS(255,239)/CSOC(n0/k0=7/6,J=8))

      4       G.975.1 Concatenated FEC (BCH(3860,3824)/BCH(2040,1930))

      5        G.975.1 Concatenated FEC (RS(1023,1007)/BCH(2407,1952))

      6       G.975.1 Concatenated FEC (RS(1901,1855)/Extended Hamming
              Product Code (512,502)X(510,500))

      7       G.975.1 LDPC Code

      8       G.975.1 Concatenated FEC (Two orthogonally concatenated
              BCH codes)

      9       G.975.1 RS(2720,2550)

      10      G.975.1 Concatenated FEC (Two interleaved extended BCH
              (1020,988) codes)

      Where RS stands for Reed-Solomon and BCH for Bose-Chaudhuri-
      Hocquengham.

   The format for input vendor-specific FEC field is 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
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |0|1|       Vendor FEC ID           | MatrixID         Length            | RstType = 1
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |        MaxNumChannels                       Enterprise Number                       |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   In this case the accompanying MaxNumChannels indicates
     :   Any vendor specific additional FEC parameters               :
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Vendor FEC ID

     This is a vendor assigned identifier for the maximum
   number FEC type.

   Enterprise Number

     A unique identifier of channels that an organization encoded as a 32-bit integer.
     Enterprise Numbers are assigned by IANA and managed through an IANA
     registry [RFC2578].

   Vendor Specific Additional FEC parameters

     There can be simultaneously used on the
   port/matrix.

   4.4.3. WAVEBAND1

   In potentially additional parameters characterizing the case
     vendor specific FEC.

5.4. Input Bit Range List Sub-Sub-TLV

   This sub-TLV contains a list of acceptable input bit rate ranges.

   Type := Input Bit Range List

   Value:= A list of Bit Range Fields

   5.4.1. Bit Range Field

   The bit rate range list sub-TLV makes use of the WAVEBAND1 the GeneralPortRestrictions (or
   MatrixSpecificRestrictions) format is given by: following bit rate
   range field:

      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
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     | MatrixID      | RstType = 2   |     MaxWaveBandWidth                          Starting Bit Rate                    |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |                        Wavelength Set                            Ending Bit Rate                    |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   In this case the accompanying MaxWaveBandWidth indicates the maximum
   width of the waveband in terms of the channels spacing

   The starting and ending bit rates are given as 32 bit IEEE floating
   point numbers in bits per second. Note that the
   wavelength set. The corresponding wavelength set starting bit rate is used
   less than or equal to indicate the overall tuning range. Specific center frequency tuning
   information can be obtained from dynamic channel in use information.
   It is assumed that both center frequency and bandwidth (Q) tuning can
   be done without causing faults in existing signals.

   4.4.4. SIMPLE_WAVELENGTH & CHANNEL_COUNT

   In the case of the SIMPLE_WAVELENGTH & CHANNEL_COUNT the format ending bit rate.

   The bit rate range list sub-TLV 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
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     | MatrixInfo                                                               | RstType = 3
     +-+-+-+-+-+-+-+-+-+-+-+-+ Bit Range Field #1  +-+-+-+-+-+-+-+-+-+
     |        MaxNumChannels                                                               |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     :                               :                               :
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |                     Wavelength Set                                                               |
     +-+-+-+-+-+-+-+-+-+-+-+-+ Bit Range Field #M  +-+-+-+-+-+-+-+-+-+
     |                                                               |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   In this case the accompanying wavelength set and MaxNumChannels
   indicate wavelength permitted on the port and the maximum number of
   channels that can be simultaneously used on the port.

5. Wavelength Converter Pool Encoding

   The encoding of structure and properties of a general wavelength
   converter pool utilizes a converter accessibility sub-TLV, a
   wavelength converter range sub-TLV, and

5.5. Input Client Signal List Sub-Sub-TLV

   This sub-TLV contains a wavelength converter state
   sub-TLV. All these sub-TLVs make use list of the wavelength converter set
   field.

5.1. Wavelength Converter Set Field acceptable input client signal types.

   Type := Input Client Signal List

   Value:= A WSON node may include a set list of wavelength converters (WC) and such
   information frequently is used in describing the wavelength converter
   pool and its properties. GPIDs

   The WC Set field acceptable client signal list sub-TLV is defined in a similar
   manner to the label set concept list of [RFC3471].

   The information carried in a WC set field is Generalized
   Protocol Identifiers (GPIDs). GPIDs are assigned by IANA and many are
   defined by: in [RFC3471] and [RFC4328].

      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
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |    Action     |E|   Reserved  |        Length                 |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |     WC Identifier 1       Number of GPIDs         |        WC Identifier 2          GPID #1              |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     :                               :                               |                               :
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |     WC Identifier n-1            GPID #N            |        WC Identifier n                               |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

      Action: 8 bits

         0 - Inclusive List

   Indicates that

   Where the TLV contains one number of GPIDs is an integer greater than or more WC elements that are
   included in the list.

         2 - Inclusive Range

   Indicates that the TLV equal to one.

5.6. Processing Capability List Sub-Sub-TLV

   This sub-TLV contains a range list of WCs.  The object/TLV
   contains two WC elements. The first element indicates the start resource block processing
   capabilities.

   Type := Processing Capabilities List

   Value:= A list of
   the range. Processing Capabilities Fields

   The second element indicates the end of the range. A value
   of zero indicates that there is no bound on the corresponding portion
   of the range.

      E (Even bit): Set to 0 denotes an odd number of WC identifiers in
   the list (last entry zero pad); Set to 1 denotes an even number of WC
   identifiers in the processing capability list (no zero padding).

      Reserved: 7 bits

   This field is reserved. It MUST be set to zero on transmission and
   MUST be ignored on receipt.

      Length: 16 bits

   The total length of this field in bytes.

      WC Identifier:

   The WC identifier represents the ID of the wavelength convertor which sub-TLV is a 16 bit integer.

5.2. Wavelength Converter Accessibility Sub-TLV

   This sub-TLV describes the structure list of the wavelength converter pool
   in relation to the switching device. In particular it gives the
   ability WSON network
   element (NE) that can perform signal processing functions including:

     1. Number of an ingress port to reach a wavelength converter Resources within the block

     2. Regeneration capability

     3. Fault and of a
   wavelength converter to reach a particular egress port. This is performance monitoring

     4. Vendor Specific capability

   Note that the
   PoolIngressMatrix code points for Fault and PoolEgressMatrix of [WSON-Info]. performance monitoring and
   vendor specific capability are subject to further study.

   5.6.1. Processing Capabilities Field

   The wavelength converter accessibility sub-TLV processing capability field is defined 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
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |                    Ingress Link Set Field A #1                |
      :                                                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                          WC Set Field A #1                    |
      :                                                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+          Processing Cap ID     |         Additional Link set and WC set pairs as needed to         Length               |
      :                    specify PoolIngressMatrix                  :
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |             WC Set B Field #1 (for egress connectivity)   Possible additional capability parameters depending upon    |
      :                                                               :
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                Egress link Set Field B #1                     |
     :   the processing ID                                           :
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |         Additional WC set and egress link set pairs           |
      :              as needed to specify PoolEgressMatrix            :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   Note that the direction parameter within the Link Set Field is used
   to indicate whether the link set is an ingress or egress link set,
   and

   When the bidirectional value for this parameter processing Cap ID is not permitted in
   this sub-TLV.

5.3. Wavelength Conversion Range Sub-TLV

   Wavelength converters may have a limited input or output range.
   Additionally, due to the structure "number of resources" the optical system not all
   wavelengths can necessarily reach or leave all the converters. These
   properties are described by using one or more wavelength conversion
   sub-TLVs as defined below: format is
   simply:

      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
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |                     WC Set Field                              |
      :                                                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+          Processing Cap ID     |                Input Wavelength Set Field         Length = 8           |
      :                                                               :
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |                Output Wavelength Set Field                  Number of resources per block                |
      :                                                               :
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   WC Set Field:

   A set of wavelength converters (WCs) which have the same conversion
   range.

   Input Wavelength Set Field:

   Indicates the wavelength input range of the WCs in the corresponding
   WC set.

   Output Wavelength Set Field:

   Indicates the wavelength output range of WCs in

   When the corresponding WC
   set.

5.4. Wavelength Converter Usage State Sub-TLV

   The usage state of a wavelength converter processing Cap ID is encoded as a bit map
   indicating whether "regeneration capability", the converter is available or in use. This
   information can be relatively dynamic, i.e., can change when a
   connection is established or torn down. This bit map is
   following additional capability parameters are provided in
   correspondence with a wavelength converter set as follows: the sub-
   TLV:

   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
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |                     WC Set Field                              |
      :                                                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                  WC Usage state bitmap                        |
      :                                                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+  T  |                     ...... C |      Padding bits                 Reserved                            |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   WC Usage state:  Variable Length but must be a multiple

   Where T bit indicates the type of 4 byes.

   Each regenerator:

      T=0: Reserved

      T=1: 1R Regenerator

      T=2: 2R Regenerator

      T=3: 3R Regenerator

   Where C bit indicates the usage status capability of one WC with 0 indicating regenerator:

      C=0: Reserved

      C=1: Fixed Regeneration Point

      C=2: Selective Regeneration Point

   Note that when the
   WC capability of regenerator is available indicated to be
   Selective Regeneration Pools, regeneration pool properties such as
   ingress and 1 indicating the WC is in used. The sequence of
   the bit map egress restrictions and availability need to be
   specified. This encoding is ordered according to the WC Set field with this sub-
   TLV.

   Padding bits: Variable Length

6. WSON Encoding Usage Recommendations

   In this section we give recommendations of typical usage of the
   previously defined sub-TLVs. Typically the sub-TLVs defined in the
   preceding sections would be incorporated into some kind of composite
   TLV. The example composite TLVs determined in the following sections are based
   on the four high level information bundles later revision.

5.7. Output Modulation Format List Sub-Sub-TLV

   This sub-TLV contains a list of [WSON-Info].

6.1. WSON Node TLV

   The WSON Node TLV could consist available output modulation formats.

   Type := Output Modulation Format List

   Value:= A list of the following Modulation Format Fields

5.8. Output FEC Type List Sub-Sub-TLV

   This sub-TLV contains a list of sub-TLVs:

   <Node_Info> ::= <Node_ID>[Other GMPLS sub-
   TLVs][<ConnectivityMatrix>...]
   [<WavelengthConverterPool>][<WCPoolState>]

6.2. WSON Dynamic Node TLV

   If the protocol supports the separation output FEC types.

   Type := Output FEC Type field List

   Value:= A list of dynamic information from
   relatively static FEC type Fields

6. Security Considerations

   This document defines protocol-independent encodings for WSON
   information then the wavelength converter pool
   state can be separated from the general Node TLV into a dynamic Node
   TLV as follows.

   <NodeInfoDynamic> ::= <NodeID> [<WCPoolState>]
   Note and does not introduce any security issues.

   However, other documents that currently make use of these encodings within
   protocol extensions need to consider the only dynamic information modeled with a node
   is issues and risks associated with the status of the wavelength converter pool.

6.3. WSON Link TLV

   The new link related sub-TLVs could be incorporated into a composite
   link TLV as follows:

   <LinkInfo> ::=  <LinkID> [Other GMPLS sub-TLVs]
   [<PortWavelengthRestriction>...][<AvailableWavelengths>]
   [<SharedBackupWavelengths>]

6.4. WSON Dynamic Link TLV

   If the protocol supports the separation of dynamic information from
   relatively static information then the available wavelength and
   shared backup status can be separated from the general link TLV into
   a TLV for dynamic link information.

   <DynamicLinkInfo> ::=  <LinkID> <AvailableWavelengths>
   [<SharedBackupWavelengths>]

7. 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
   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.

8.

7. IANA Considerations

   TBD. Once our approach is finalized we may need identifiers for the
   various TLVs and sub-TLVs.

9.

8. Acknowledgments

   This document was prepared using 2-Word-v2.0.template.dot.

APPENDIX A: Encoding Examples

A.1. Link Set Field

   Suppose that we wish to describe Wavelength Converter Accessibility Sub-TLV

   Example:

   Figure 1 shows a set of ingress ports that are have
   link local identifiers number 3 through 42. wavelength converter pool architecture know as
   "shared per fiber". In this case the link set field we
   set the Action = ingress and egress pool matrices
   are simply:

              +-----+       +-----+
              | 1 to denote an inclusive range; the Dir = 1 to
   denote ingress links; and, the Format = 0 to denote link local
   identifiers. In particular we have:

     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |  Action=1     |0 1|0 0 0 0       | 1 0 0|             Length = 12 |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
          WI =|     |,  WE =|     |                     Link Local Identifier = #3
              |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1 1 |                     Link Local Identifier = #42       |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

A.2. Wavelength Set Field

   Example:

   A 40 channel C-Band DWDM system with 100GHz spacing with lowest
   frequency 192.0THz (1561.4nm) and highest frequency 195.9THz
   (1530.3nm). These frequencies correspond to n = -11, and n = 28
   respectively. Now suppose the following channels are available:

   Frequency (THz)    n Value      bit map position
   --------------------------------------------------
      192.0             -11               0
      192.5              -6               5
      193.1               0              11
      193.9               8              19
      194.0               9              20
      195.2              21              32
      195.8              27              38

   With the Grid value set to indicate an ITU-T G.694.1 DWDM grid, C.S.
   set to indicate 100GHz this lambda bit map set would then be encoded
   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
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |  4    | Num Wavelengths = 40  |    Length = 16 bytes          |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |Grid |  C.S. |      Reserved   | n  for lowest frequency = -11 |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |1 0 0 0 0 1 0 0 0 0 0 1 0 0 0 0 0 0 0 1 1 0 0 0 0 0 0 0 0 0 0 0|
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |1 0 0 0 0 0 1 0|   Not used in 40 Channel system (all zeros)   |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   To encode this same set as an inclusive list we would have:

      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
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |  0    | Num Wavelengths = 40  |    Length = 20 bytes          |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |Grid |  C.S. |      Reserved   | n  for lowest frequency = -11 |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |          n2 = -6              |          n3 = 0               |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |          n4 = 8               |          n5 = 9               |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |          n6 = 21              |          n7 = 27              |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

A.3. Connectivity Matrix Sub-TLV

   Example:

   Suppose we have a typical 2-degree 40 channel ROADM. In addition to
   its two line side ports it has 80 add and 80 drop ports. The picture
   below illustrates how a typical 2-degree ROADM system that works with
   bi-directional fiber pairs is a highly asymmetrical system composed
   of two unidirectional ROADM subsystems.

                         (Tributary) Ports #3-#42
                     Ingress added to    Egress dropped from
                     West Line Egress    East Line Ingress
                           vvvvv          ^^^^^
                          | |||.|       | |||.|
                    +-----| |||.|--------| |||.|------+
                    |    +----------------------+     |
                    |    |                      |     |
        Egress      |    | Unidirectional ROADM |     |    Ingress
   -----------------+    |                      |     +--------------
   <=====================|                      |===================<
   -----------------+    +----------------------+     +--------------
                    |                                 |
        Port #1     |                                 |   Port #2
   (West Line Side) |                                 |(East Line Side)
   -----------------+    +----------------------+     +--------------
   >=====================|                      |===================>
   -----------------+    | Unidirectional ROADM |     +--------------
        Ingress     |    |                      |     |    Egress
                    |    |              _       |     |
                    |    +----------------------+     |
                    +-----| |||.|--------| |||.|------+
                          | |||.|        | |||.|
                           vvvvv          ^^^^^
                     (Tributary) Ports #43-#82
                Egress dropped from    Ingress added to
                West Line ingress      East Line egress

   Referring to the figure we see that the ingress direction of ports
   #3-#42 (add ports) can only connect to the egress on port #1. While
   the ingress side of port #2 (line side) can only connect to the
   egress on ports #3-#42 (drop) and to the egress on port #1 (pass
   through). Similarly, the ingress direction of ports #43-#82 can only
   connect to the egress on port #2 (line). While the ingress direction
   of port #1 can only connect to the egress on ports #43-#82 (drop) or
   port #2 (pass through). We can now represent this potential
   connectivity matrix as follows. This representation uses only 30 32-
   bit words.

       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
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |    Conn = 1   |    MatrixID   |      Reserved                 |1
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                          Note: adds to line
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |  Action=1     |0 1|0 0 0 0 0 0|          Length = 12          |2
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |                     Link Local Identifier = #3                |3
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |                     Link Local Identifier = #42               |4
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
              +-----+       +-----+

                    +-----------+                      +------+
                    |  Action=0     |1 0|0 0 0 0 0 0|          Length = 8           |5
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+           |--------------------->|      |                     Link Local Identifier = #1                |6
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                       Note: line to drops
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                    |  Action=0     |0 1|0 0 0 0 0 0|          Length = 8           |7
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+           |--------------------->|  C   |                     Link Local Identifier = #2                |8
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
              /|    |  Action=1     |1 0|0 0 0 0 0 0|          Length = 12          |9
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+           |--------------------->|  o   |                     Link Local Identifier = #3                |10
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
             /D+--->|           |--------------------->|  m   |                     Link Local Identifier = #42               |11
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                       Note: line to line
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
            + e+--->|           |  Action=0     |0 1|0 0 0 0 0 0|          Length = 8           |12
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+                      |                     Link Local Identifier = #2                |13
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+  b   |========>
   ========>| M|    |  Action=0     |1 0|0 0 0 0 0 0|          Length = 8           |14
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+  Optical  |                     Link Local Identifier = #1                |15
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                Note: adds to line
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+    +-----------+     |  Action=1     |0 1|0 0 0 0 0 0|          Length = 12          |16
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+  i   |                     Link Local Identifier = #43               |17
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Port E1
   Port I1  + u+--->|   Switch  |                     Link Local Identifier = #82               |18
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+    |  Action=0     |1 0|0 0 0 0 0 0|          Length = 8           |19
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+  WC Pool  |                     Link Local Identifier = #2                |20
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                       Note: line to drops
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+     |  Action=0     |0 1|0 0 0 0 0 0||          Length = 8          |21
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+  n   |                     Link Local Identifier = #1                |22
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
             \x+--->|           |  Action=1     |1 0|0 0 0 0 0 0|          Length = 12          |23
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+    |                     Link Local Identifier = #43               |24
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+  +-----+  |                     Link Local Identifier = #82               |25
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                       Note: line to line
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+     |  Action=0     |0 1|0 0 0 0 0 0|          Length = 8           |26
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+  e   |                     Link Local Identifier = #1                |27
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
              \|    |  Action=0     |1 0|0 0 0 0 0 0|          Length = 8           |28
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+           +----+->|WC #1|--+---->|  r   |                     Link Local Identifier = #2                |30
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

A.4. Connectivity Matrix with Bi-directional Symmetry

   If one has the ability to renumber the ports of the previous example
   as shown in the next figure then we can take advantage of the bi-
   directional symmetry and use bi-directional encoding of the
   connectivity matrix. Note that we set dir=bidirectional in the link
   set fields.

                                (Tributary)
                     Ports #3-42         Ports #43-82
                     West Line Egress    East Line Ingress
                           vvvvv          ^^^^^
                    | |||.|           | |||.|
                    +-----| |||.|--------| |||.|------+    |    +----------------------+  +-----+  |     +------+
                    |           |    |           |
        Egress     +------+
              /|    |           | Unidirectional ROADM    |  +-----+  |    Ingress
   -----------------+     |      |     +--------------
   <=====================|                      |===================<
   -----------------+    +----------------------+     +--------------
             /D+--->|           +----+->|WC #2|--+---->|  C   |
            + e+--->|           |
        Port #1    |  +-----+  |   Port #2
   (West Line Side) |                                 |(East Line Side)
   -----------------+    +----------------------+     +--------------
   >=====================|                      |===================>
   -----------------+     | Unidirectional ROADM  o   |     +--------------
        Ingress
   ========>| M|    |           |    +-----------+     |  m   |========>
   Port I2  + u+--->|           |    Egress                      |  b   |              _ Port E2
             \x+--->|           |--------------------->|  i   |
              \|    |           |--------------------->|  n   |    +----------------------+
                    |
                    +-----| |||.|--------| |||.|------+           |--------------------->|  e   | |||.|
                    | |||.|
                           vvvvv          ^^^^^
                     Ports #3-#42         Ports #43-82
                Egress dropped from    Ingress added to
                West Line ingress      East Line egress           |--------------------->|  r   |
                    +-----------+                      +------+
    Figure 1 An optical switch featuring a shared per fiber wavelength
                       converter pool architecture.

   This wavelength converter pool can be encoded 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
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |    Conn = 1   |    MatrixID   | Connectivity=1|                    Reserved                 |1
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                          Add/Drops #3-42                   |
                  Note: I1,I2 can connect to Line side #1 either WC1 or WC2
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |  Action=1  Action=0     |0 0|0 1|0 0 0 0 0 0|            Length = 12          |2        |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                     Link Local Identifier = #3                |3 #1                |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                     Link Local Identifier = #42               |4 #2                |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |  Action=0     |0 0|0 0 0 0 0 0|     |1|  Reserved   |            Length = 8           |5         |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                     Link Local Identifier           WC ID = #1                |6          |       WC ID = #2              |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                        Note: line #2 WC1 can only connect to add/drops #43-82 E1
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |  Action=0     |0 0|0 0 0 0 0 0|     |0|  Reserved   |            Length = 8           |7         |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                     Link Local Identifier           WC ID = #2                |8 #1          |       zero padding            |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |  Action=1     |0  Action=0     |1 0|0 0 0 0 0 0|            Length = 12          |9
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 8         |                     Link Local Identifier = #43               |10
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                     Link Local Identifier = #82               |11 #1                |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                        Note: line WC2 can only connect to line E2
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |  Action=0     |0 0|0 0 0 0 0 0|     |0|             |            Length = 8           |12         |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                     Link Local Identifier           WC ID = #1                |13 #2          |       zero padding            |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |  Action=0     |0     |1 0|0 0 0 0 0 0|            Length = 8           |14         |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                     Link Local Identifier = #2                |15                |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

A.5.

A.2. Wavelength Converter Accessibility Conversion Range Sub-TLV

   Example:

   Figure

   We give an example based on figure 1 shows a about how to represent the
   wavelength converter pool architecture know as
   "shared per fiber". In this case conversion range of wavelength converters. Suppose the ingress
   wavelength range of input and egress pool matrices output of WC1 and WC2 are simply:

              +-----+       +-----+
              | 1 1 |       | {L1, L2, L3,
   L4}:

       0                   1                   2                   3
       0 1 2 3 4 5 6 7 8 9 0 |
          WI =|     |,  WE =|     |
              | 1 2 3 4 5 6 7 8 9 0 1 |       | 2 3 4 5 6 7 8 9 0 1
                             Note: WC Set
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |
              +-----+       +-----+

                    +-----------+                      +------+
                    |           |--------------------->|      |
                    |           |--------------------->|  C   |
              /|    |           |--------------------->|  o   |
             /D+--->|           |--------------------->|  m   |
            + e+--->|           |                      |  b   |========>
   ========>| M|    |  Optical  |    +-----------+     |  i  Action=0     |1| Reserved    | Port E1
   Port I1  + u+--->|   Switch     Length = 8                |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |           WC Pool ID = #1          |       WC ID = #2              |  n
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                             Note: wavelength input range
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |
             \x+--->| 2   | Num Wavelengths = 4     |  +-----+          Length = 8           |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |Grid |  e  C.S. |
              \|     Reserved    |           +----+->|WC #1|--+---->|  r  n for lowest frequency = 1   |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                             Note: wavelength output range
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      | 2   | Num Wavelengths = 4     |  +-----+          Length = 8           |     +------+
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |Grid |  C.S. |     Reserved    |  n for lowest frequency = 1   |     +------+
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

A.3. An OEO Switch with DWDM Optics

   In Figure 2 we show an electronic switch fabric surrounded by DWDM
   optics. In this example the electronic fabric can can handle either
   G.709 or SDH signals only (2.5 or 10 Gbps). To describe this node we
   have the potential information:

   <Node_Info> ::= <Node_ID>[Other GMPLS sub-
   TLVs][<ConnectivityMatrix>...]  [<ResourcePool>][<RBPoolState>]

   In this case there is complete port to port connectivity so the
   <ConnectivityMatrix> is not required. In addition since there are
   sufficient ports to handle all wavelength signals we will not need
   the <RBPoolState> element.

   Hence our attention will be focused on the <ResourcePool> sub-TLV:

   <ResourcePool> ::=
   <ResourceBlockInfo>[<ResourceBlockAccessibility>...][<ResourceWaveCon
   straints>...]
              /|    |           |    |  +-----+  |     |      |    +-----------+    +-------------+   +------+
             /D+--->|           +----+->|WC #2|--+---->|  C           +--->|Tunable Laser|-->|      |
            + e+--->|           |    +-------------+   |  +-----+  |     |  o  C   |
   ========>| M|    |           |    +-----------+        ...           |  m  o   |========>
   Port I2 I1  + u+--->|           |    +-------------+   |  b  m   | Port E2
             \x+--->|           |--------------------->|  i   |
              \|    |           |--------------------->|  n   |
                    |           |--------------------->|  e E1
             \x+--->|           |--->|Tunable Laser|-->|  b   |
              \|    |           |--------------------->|  r  Electric |
                    +-----------+    +-------------+   +------+
    Figure 1 An optical switch featuring a shared per fiber wavelength
                       converter pool architecture.

   This wavelength converter pool can be encoded 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
                  Note: I1,I2 can connect to either WC1 or WC2
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                    |  Action=0     |0 1|0 0 0 0 0 0|            Length = 12   Switch  |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
              /|    |                     Link Local Identifier = #1           |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+    +-------------+   +------+
             /D+--->|           +--->|Tunable Laser|-->|      |                     Link Local Identifier = #2
            + e+--->|           |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+    +-------------+   |  Action=0     |1|  Reserved  C   |            Length = 8
   ========>| M|    |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+           |           WC ID = #1        ...           |       WC ID = #2  o   |========>
   Port I2  + u+--->|           |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                        Note: WC1 can only connect to E1
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+    +-------------+   |  Action=0     |0|  Reserved  m   |            Length = 8 Port E2
             \x+--->|           +--->|Tunable Laser|-->|  b   |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
              \|    |           WC ID = #1           |       zero padding    +-------------+   +------+
                    |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+           |  Action=0     |1 0|0 0 0 0 0 0|            Length = 8
              /|    |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+           |                     Link Local Identifier = #1    +-------------+   +------+
             /D+--->|           |--->|Tunable Laser|-->|      |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                        Note: WC2 can only connect to E2
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
            + e+--->|           |  Action=0     |0|    +-------------+   |            Length = 8  C   |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   ========>| M|    |           WC ID = #2           |       zero padding        ...           |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+  o   |========>
   Port I3  + u+--->|           |  Action=0     |1 0|0 0 0 0 0 0|            Length = 8    +-------------+   |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+  m   |                     Link Local Identifier = #2 Port E3
             \x+--->|           |--->|Tunable Laser|-->|  b   |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

A.6. Wavelength Conversion Range Sub-TLV

   Example:

   We give
              \|    +-----------+    +-------------+   +------+

      Figure 2 An optical switch built around an example based on figure 1 electronic switching
                                  fabric.

   The resource block information will tell us about how to represent the
   wavelength conversion range processing
   constraints of wavelength converters. Suppose the
   wavelength range of input and output of WC1 receivers, transmitters and WC2 the electronic switch.
   The resource availability information, although very simple, tells us
   that all signals must traverse the electronic fabric (fixed
   connectivity). The resource wavelength constraints are {L1, L2, L3,
   L4}: not needed
   since there are no special wavelength constraints for the resources
   that would not appear as port/wavelength constraints.

   <ResourceBlockInfo>:

       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
                             Note: WC Set
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |  Action=0     |1| Reserved                     RB Set Field                              |     Length = 8
      :  (only one resource block in this example)                    |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |           WC ID = #1           Input Modulation Type List Sub-Sub-TLV              |       WC ID = #2
      :        (The receivers can only process NRZ)                   :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |           Input FEC Type List Sub-Sub-TLV                     |
      :           (Only Standard SDH and G.709 FECs)                  :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                             Note: wavelength input range
      |         Input Client Signal Type Sub-TLV                      |
      :              (GPIDs for SDH and G.709)                        :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      | 2         Input Bit Rate Range List  Sub-Sub-TLV                | Num Wavelengths = 4
      :                          (2.5Gbps, 10Gbps)                    :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |          Length = 8         Processing Capabilities List Sub-Sub-TLV              |
      :                    Fixed (non optional) 3R regeneration       :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |Grid
      |  C.S.         Output Modulation Type List Sub-Sub-TLV               |     Reserved
      :                          NRZ                                  :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |  n for lowest frequency = 1         Output FEC Type List Sub-Sub-TLV                      |
      :                 Standard SDH, G.709 FECs                      :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                             Note: wavelength output range

   Since we have fixed connectivity to resource block (the electronic
   switch) we get <ResourceBlockAccessibility>:

       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
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      | 2 Connectivity=1|Reserved       | Num Wavelengths = 4
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |          Length = 8                    Ingress Link Set Field A #1                |
      :                    (All ingress links connect to resource)    :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |Grid
      |  C.S.                          RB Set Field A #1                    |     Reserved
      :              (trivial set only one resource block)            :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |  n for lowest frequency = 1                Egress Link Set Field B #1                     |
      :                    (All egress links connect to resource)     :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

10.

9. References

10.1.

9.1. Normative References

   [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
             Requirement Levels", BCP 14, RFC 2119, March 1997.

   [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
             MIB", RFC 2863, June 2000.

   [RFC3471] Berger, L., "Generalized Multi-Protocol Label Switching
             (GMPLS) Signaling Functional Description", RFC 3471,
             January 2003.

   [G.694.1] ITU-T Recommendation G.694.1, "Spectral grids for WDM
             applications: DWDM frequency grid", June, 2002.

   [RFC4202] Kompella, K., Ed., and Y. Rekhter, Ed., "Routing Extensions
             in Support of Generalized Multi-Protocol Label Switching
             (GMPLS)", RFC 4202, October 2005

   [RFC4203] Kompella, K., Ed., and Y. Rekhter, Ed., "OSPF Extensions in
             Support of Generalized Multi-Protocol Label Switching
             (GMPLS)", RFC 4203, October 2005.

10.2.

9.2. Informative References

   [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.

   [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-ext-
             encode-00.txt.

   [Otani]   T. Otani, H. Guo, K. Miyazaki, D. Caviglia, "Generalized
             Labels for G.694 Lambda-Switching Capable Label Switching
             Routers", work in progress: draft-ietf-ccamp-gmpls-g-694-
             lambda-labels.

   [RFC5307] Kompella, K., Ed., and Y. Rekhter, Ed., "IS-IS Extensions
             in Support of Generalized Multi-Protocol Label Switching
             (GMPLS)", RFC 5307, October 2008.

   [Switch] G. Bernstein, Y. Lee, A. Gavler, J. Martensson, " Modeling
         WDM Wavelength Switching Systems for Use in GMPLS and Automated
         Path Computation", Journal of Optical Communications and
         Networking, vol. 1, June, 2009, pp. 187-195.

   [WSON-Frame] Y. Lee, G. Bernstein, W. Imajuku, "Framework for GMPLS
             and PCE Control of Wavelength Switched Optical Networks",
             work in progress: draft-ietf-ccamp-wavelength-switched-
             framework, Marh 2009.

   [WSON-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, March 2009.

   [PCEP]    Vasseur, JP., Ed. and JL. Le Roux, Ed., "Path Computation
             Element (PCE) communication Protocol (PCEP) - Version 1",
             RFC5440.

11.

10. Contributors

   Diego Caviglia
   Ericsson
   Via A. Negrone 1/A 16153
   Genoa Italy

   Phone: +39 010 600 3736
   Email: diego.caviglia@(marconi.com, ericsson.com)

   Anders Gavler
   Acreo AB
   Electrum 236
   SE - 164 40 Kista Sweden

   Email: Anders.Gavler@acreo.se

   Jonas Martensson
   Acreo AB
   Electrum 236
   SE - 164 40 Kista, Sweden

   Email: Jonas.Martensson@acreo.se

   Itaru Nishioka
   NEC Corp.
   1753 Simonumabe, Nakahara-ku, Kawasaki, Kanagawa 211-8666
   Japan

   Phone: +81 44 396 3287
   Email: i-nishioka@cb.jp.nec.com

Authors' Addresses

   Greg M. Bernstein (ed.)
   Grotto Networking
   Fremont California, USA

   Phone: (510) 573-2237
   Email: gregb@grotto-networking.com
   Young Lee (ed.)
   Huawei Technologies
   1700 Alma Drive, Suite 100
   Plano, TX 75075
   USA

   Phone: (972) 509-5599 (x2240)
   Email: ylee@huawei.com

   Dan Li
   Huawei Technologies Co., Ltd.
   F3-5-B R&D Center, Huawei Base,
   Bantian, Longgang District
   Shenzhen 518129 P.R.China

   Phone: +86-755-28973237
   Email: danli@huawei.com

   Wataru Imajuku
   NTT Network Innovation Labs
   1-1 Hikari-no-oka, Yokosuka, Kanagawa
   Japan

   Phone: +81-(46) 859-4315
   Email: imajuku.wataru@lab.ntt.co.jp

   Jianrui Han
   Huawei Technologies Co., Ltd.
   F3-5-B R&D Center, Huawei Base,
   Bantian, Longgang District
   Shenzhen 518129 P.R.China

   Phone: +86-755-28972916
   Email: hanjianrui@huawei.com

Intellectual Property Statement

   The IETF Trust takes no position regarding the validity or scope of
   any Intellectual Property Rights or other rights that might be
   claimed to pertain to the implementation or use of the technology
   described in any IETF Document or the extent to which any license
   under such rights might or might not be available; nor does it
   represent that it has made any independent effort to identify any
   such rights.

   Copies of Intellectual Property disclosures made to the IETF
   Secretariat and any assurances of licenses to be made available, or
   the result of an attempt made to obtain a general license or
   permission for the use of such proprietary rights by implementers or
   users of this specification can be obtained from the IETF on-line IPR
   repository at http://www.ietf.org/ipr

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights that may cover technology that may be required to implement
   any standard or specification contained in an IETF Document. Please
   address the information to the IETF at ietf-ipr@ietf.org.

Disclaimer of Validity

   All IETF Documents and the information contained therein are provided
   on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
   REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE
   IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL
   WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY
   WARRANTY THAT THE USE OF THE INFORMATION THEREIN WILL NOT INFRINGE
   ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS
   FOR A PARTICULAR PURPOSE.

Acknowledgment

   Funding for the RFC Editor function is currently provided by the
   Internet Society.