--- 1/draft-ietf-ccamp-rwa-wson-encode-13.txt 2012-04-24 18:13:58.782671984 +0200 +++ 2/draft-ietf-ccamp-rwa-wson-encode-14.txt 2012-04-24 18:13:58.850671601 +0200 @@ -1,24 +1,24 @@ Network Working Group G. Bernstein Internet Draft Grotto Networking Intended status: Standards Track Y. Lee -Expires: April 2012 D. Li +Expires: October 2012 D. Li Huawei W. Imajuku NTT - October 31, 2011 + April 24, 2012 Routing and Wavelength Assignment Information Encoding for Wavelength Switched Optical Networks - draft-ietf-ccamp-rwa-wson-encode-13.txt + draft-ietf-ccamp-rwa-wson-encode-14.txt Status of this Memo This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. @@ -27,25 +27,25 @@ months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html - This Internet-Draft will expire on February 31, 2012. + This Internet-Draft will expire on September 24, 2012. Copyright Notice - Copyright (c) 2011 IETF Trust and the persons identified as the + Copyright (c) 2012 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without @@ -81,60 +81,60 @@ 1. Introduction...................................................4 1.1. Revision History..........................................4 1.1.1. Changes from 00 draft................................4 1.1.2. Changes from 01 draft................................5 1.1.3. Changes from 02 draft................................5 1.1.4. Changes from 03 draft................................5 1.1.5. Changes from 04 draft................................5 1.1.6. Changes from 05 draft................................5 1.1.7. Changes from 06 draft................................5 - 1.1.8. Changes from 07 draft................................5 + 1.1.8. Changes from 07 draft................................6 1.1.9. Changes from 08 draft................................6 1.1.10. Changes from 09 draft...............................6 1.1.11. Changes from 10 draft...............................6 1.1.12. Changes from 11 draft...............................6 - 2. Terminology....................................................6 + 1.1.13. Changes from 12 draft...............................6 + 1.1.14. Changes from 13 draft...............................6 + 2. Terminology....................................................7 3. Resources, Blocks, Sets, and the Resource Pool.................7 3.1. Resource Block Set Field..................................8 - 4. Resource Pool Accessibility/Availability.......................9 - 4.1. Resource Pool Accessibility Sub-TLV.......................9 - 4.2. Resource Block Wavelength Constraints Sub-TLV............11 - 4.3. Resource Pool State Sub-TLV..............................12 - 4.4. Block Shared Access Wavelength Availability sub-TLV......13 - 5. Resource Properties Encoding..................................15 - 5.1. Resource Block Information Sub-TLV.......................15 - 5.2. Input Modulation Format List Sub-Sub-TLV.................16 - 5.2.1. Modulation Format Field.............................17 - 5.3. Input FEC Type List Sub-Sub-TLV..........................18 - 5.3.1. FEC Type Field......................................19 - 5.4. Input Bit Range List Sub-Sub-TLV.........................21 - 5.4.1. Bit Range Field.....................................21 - 5.5. Input Client Signal List Sub-Sub-TLV.....................22 - 5.6. Processing Capability List Sub-Sub-TLV...................23 - 5.6.1. Processing Capabilities Field.......................23 - 5.7. Output Modulation Format List Sub-Sub-TLV................25 - 5.8. Output FEC Type List Sub-Sub-TLV.........................25 - 6. Security Considerations.......................................25 + 4. Resource Pool Accessibility/Availability......................10 + 4.1. Resource Pool Accessibility Sub-TLV......................10 + 4.2. Resource Block Wavelength Constraints Sub-TLV............12 + 4.3. Resource Pool State Sub-TLV..............................14 + 4.4. Block Shared Access Wavelength Availability sub-TLV......15 + 5. Resource Properties Encoding..................................16 + 5.1. Resource Block Information Sub-TLV.......................17 + 5.2. Modulation Format List Sub-Sub-TLV.......................17 + 5.2.1. Modulation Format Field.............................18 + 5.3. FEC Type List Sub-Sub-TLV................................20 + 5.3.1. FEC Type Field......................................20 + 5.4. Input Bit Range List Sub-Sub-TLV.........................22 + 5.4.1. Bit Range Field.....................................22 + 5.5. Input Client Signal List Sub-Sub-TLV.....................23 + 5.6. Processing Capability List Sub-Sub-TLV...................24 + 5.6.1. Processing Capabilities Field.......................24 + 6. Security Considerations.......................................26 7. IANA Considerations...........................................26 8. Acknowledgments...............................................26 APPENDIX A: Encoding Examples....................................27 A.1. Wavelength Converter Accessibility Sub-TLV...............27 A.2. Wavelength Conversion Range Sub-TLV......................29 A.3. An OEO Switch with DWDM Optics...........................29 - 9. References....................................................33 - 9.1. Normative References.....................................33 - 9.2. Informative References...................................33 - 10. Contributors.................................................35 + 9. References....................................................32 + 9.1. Normative References.....................................32 + 9.2. Informative References...................................32 + 10. Contributors.................................................34 Authors' Addresses...............................................35 Intellectual Property Statement..................................36 - Disclaimer of Validity...........................................37 + Disclaimer of Validity...........................................36 1. Introduction A Wavelength Switched Optical Network (WSON) is a Wavelength Division Multiplexing (WDM) optical network in which switching is performed selectively based on the center wavelength of an optical signal. [RFC6163] describes a framework for Generalized Multiprotocol Label Switching (GMPLS) and Path Computation Element (PCE) control of a @@ -148,21 +148,23 @@ 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]. + addressed in a separate document [Gen-Encode]. This document makes + use of the Label Set Field encoding of [Gen-Encode] and refers to it + as a Wavelength Set Field. 1.1. Revision History 1.1.1. Changes from 00 draft Edits to make consistent with update to [RFC6205], i.e., removal of sign bit. Clarification of TBD on connection matrix type and possibly numbering. @@ -202,26 +204,25 @@ information encoding. 1.1.5. Changes from 04 draft Added encodings to deal with access to resource blocks via shared fiber. 1.1.6. Changes from 05 draft Revised the encoding for the "shared access" indicators to only use - one bit each for ingress and egress. + one bit each for input and output. 1.1.7. Changes from 06 draft Removed section on "WSON Encoding Usage Recommendations" - 1.1.8. Changes from 07 draft Section 3: Enhanced text to clarify relationship between pools, blocks and resources. Section 3.1, 3.2: Change title to clarify Pool-Block relationship. Section 3.3: clarify block-resource state. Section 4: Deleted reference to previously removed RBNF element. Fixed TLV figures and descriptions for consistent sub-sub-TLV nomenclature. @@ -245,34 +246,49 @@ 1.1.12. Changes from 11 draft Fixed length fields in section 4 to be 16 bits, correcting errors in TLV and field figures. Added a separate section on resources, blocks, sets and the resource pool. Moved definition of the resource block set field to this new section. 1.1.13. Changes from 12 draft - RB Identifier field in Section 3.1 to be 32 bits from 16 bits. Added - Editorial changes and updated the contributor list. + Replaced all instances of "ingress" with "input" and all instances + of "egress" with "output". + + 1.1.14. Changes from 13 draft + + C bit of Resource Block Set Field is redundant and was removed, + i.e., has been returned to "Reserved" block and appendix examples + were updated to reflect the change. + + Enhanced section 4.2 encoding to allow for optionality of input or + output wavelength set fields. + + Clarified that wavelength set fields use the Label Set field + encoding from [Gen-Encode]. + + Enhanced section 5.1 encoding to simplify the Modulation and FEC + input and output cases. 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. + count wavelength selective switching element featuring input and + output 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. @@ -312,191 +328,204 @@ . Resource Block Information Sub-TLV Each of these sub-TLVs works with one or more sets of resources rather than just a single resource block. This motivates the following field definition. 3.1. Resource Block Set Field In a WSON node that includes resource blocks (RB), denoting subsets of these blocks allows one to efficiently describe common properties - the blocks and to describe the structure and characteristics, if + of the blocks and to describe the structure and characteristics, if non-trivial, of the resource pool. The RB Set field is defined in a similar manner to the label set concept of [RFC3471]. The information carried in a 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 |C| Reserved | Length | + | Action |E| Reserved | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - | RB Identifier 1 | + | RB Identifier 1 | RB Identifier 2 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ : : : +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - | RB Identifier n | + | RB Identifier n-1 | RB Identifier n | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Action: 8 bits 0 - Inclusive List - Indicates that the TLV contains zero or more RB elements that are + Indicates that the TLV contains one or more RB elements that are included in the list. - 1 - Reserved - - 2 - Inclusive Range - - Indicates that the TLV contains a range of RBs. The object/TLV - contains two WC elements. The first element indicates the start of - the range. 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. + 2 - Inclusive Range(s) - 3 - Reserved + Indicates that the TLV contains one or more ranges of RBs. Each + individual range is denoted by two 16 bit RB identifiers in a 32 bit + word. The first 16 bits is the RB identifier for the start of the + range and the next 16 bits is the RB identifier for the end of the + range. Note that the Length field is used to determine the number of + ranges. - C (Connectivity bit): Set to 0 to denote fixed (possibly multi- - cast) connectivity; Set to 1 to denote potential (switched) - connectivity. Used in resource pool accessibility sub-TLV. Ignored - elsewhere. + E (Even bit): Set to 0 denotes an odd number of RB identifiers in + the list (last entry zero pad); Set to 1 denotes an even number of + RB identifiers in the list (no zero padding). This applies only if + Action == 0. 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. RB Identifier: The RB identifier represents the ID of the resource block which is a - 32 bit integer. + 16 bit integer. Usage Note: the inclusive range "Action" can result in very compact encoding of resource sets and it can be advantages to number resource blocks in such a way so that status updates (dynamic information) can take advantage of this efficiency. 4. Resource Pool Accessibility/Availability This section defines the sub-TLVs for dealing with accessibility and availability of resource blocks within a pool of resources. These include the ResourceBlockAccessibility, ResourceWaveConstraints, and RBPoolState sub-TLVs. 4.1. Resource Pool Accessibility Sub-TLV This sub-TLV describes the structure of the resource pool in relation to the switching device. In particular it indicates the - ability of an ingress port to reach sets of resources and of a sets - of resources to reach a particular egress port. This is the - PoolIngressMatrix and PoolEgressMatrix of [WSON-Info]. + ability of an input port to reach sets of resources and of a sets of + resources to reach a particular output port. This is the + PoolInputMatrix and PoolOutputMatrix of [WSON-Info]. The resource pool accessibility sub-TLV 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Connectivity | Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - | Ingress Link Set Field A #1 | + | Input Link Set Field A #1 | : : +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | RB Set Field A #1 | : : +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Additional Link set and RB set pairs as needed to | - : specify PoolIngressMatrix : + : specify PoolInputMatrix : +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - | Egress Link Set Field B #1 | + | Output Link Set Field B #1 | : : +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - | RB Set B Field #1 (for egress connectivity) | + | RB Set B Field #1 (for output connectivity) | : : +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Additional Link Set and RB set pairs as needed to | - : specify PoolEgressMatrix : + : specify PoolOutputMatrix : +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Where - Connectivity indicates how the ingress/egress ports connect to the + Connectivity indicates how the input/output ports connect to the resource blocks. 0 -- the device is fixed (e.g., a connected port must go through the resource block) 1 -- the device is switched (e.g., a port can be configured to go through a resource but isn't required) - The Link Set Field is defined in [Gen-Encode]. + The For the Input and Output Link Set Fields, the Link Set Field + encoding defined in [Gen-Encode] is to be used. 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 the bidirectional value for this parameter is not permitted in - this sub-TLV. + to indicate whether the link set is an input or output link set, and + the bidirectional value for this parameter is not permitted in this + sub-TLV. See Appendix A.1 for an illustration of this encoding. 4.2. Resource Block Wavelength Constraints Sub-TLV Resources, such as wavelength converters, etc., may have a limited input or output wavelength ranges. Additionally, due to the structure of the optical system not all wavelengths can necessarily reach or leave all the 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + |I|O|B| Reserved | + +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | RB Set Field | : : +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Input Wavelength Set Field | : : +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Output Wavelength Set Field | : : +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ + I = 1 or 0 indicates the presence or absence of the Input Wavelength + Set Field. + + O = 1 or 0 indicates the presence or absence of the Output + Wavelength Set Field. + + B = 1 indicates that a single wavelength set field represents both + input and output wavelength constraints. + + Currently the only valid combinations of (I,O,B) are (1,0,0), + (0,1,0), (1,1,0), (0,0,1). + RB Set Field: A set of resource blocks (RBs) which have the same wavelength restrictions. Input Wavelength Set Field: Indicates the wavelength input restrictions of the RBs in the - corresponding RB set. + corresponding RB set. This field is encoded via the Label Set field + of [Gen-Encode]. Output Wavelength Set Field: Indicates the wavelength output restrictions of RBs in the - corresponding RB set. + corresponding RB set. This field is encoded via the Label Set field + of [Gen-Encode]. 4.3. Resource Pool State Sub-TLV The state of the pool is given by the number of resources available with particular characteristics. A resource block set is used to encode all or a subset of the resources of interest. The usage state of resources within a resource block set is encoded as either a list - of 16 bit integer values indicating the number of available - resources in the resource block, or a bit map indicating whether a - particular resource is available or in use. The bit map encoding is - appropriate when resource blocks consist of a single resource. This - information can be relatively dynamic, i.e., can change when a - connection (LSP is established or torn down. + of 16 bit integer values or a bit map indicating whether a single + resource is available or in use. The bit map encoding is appropriate + when resource blocks consist of a single resource. This information + can be relatively dynamic, i.e., can change when a connection (LSP + 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Action | Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | RB Set Field | : : +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | RB Usage state | @@ -533,21 +562,21 @@ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | RB Set Field | : : +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | RB Usage state bitmap | : : +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ...... | Padding bits | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - RB Usage state: Variable Length but must be a multiple of 4 bytes. + RB Usage state: Variable Length but must be a multiple of 4 byes. Each bit indicates the usage status of one RB with 0 indicating the RB is available and 1 indicating the RB is in used. The sequence of the bit map is ordered according to the RB Set field with this sub- TLV. Padding bits: Variable Length 4.4. Block Shared Access Wavelength Availability sub-TLV @@ -556,166 +585,166 @@ to understand resource availability. 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |I|E| Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | RB Set Field | : : +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - | Ingress Available Wavelength Set Field | + | Input Available Wavelength Set Field | : (Optional) : +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - | Egress Available Wavelength Set Field | + | Output Available Wavelength Set Field | : (Optional) : +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - I bit: - Indicates whether the ingress available wavelength set field is + Indicates whether the input available wavelength set field is included (1) or not (0). E bit: - Indicates whether the egress available wavelength set field is + Indicates whether the output available wavelength set field is included (1) or not (0). RB Set Field: - A Resource Block set in which all the members share the same ingress - or egress fiber or both. + A Resource Block set in which all the members share the same input + or output fiber or both. - Ingress Available Wavelength Set Field: + Input Available Wavelength Set Field: Indicates the wavelengths currently available (not being used) on - the ingress fiber to this resource block. + the input fiber to this resource block. This field is encoded via + the Label Set field of [Gen-Encode]. - Egress Available Wavelength Set Field: + Output Available Wavelength Set Field: Indicates the wavelengths currently available (not being used) on - the egress fiber from this resource block. + the output fiber from this resource block. This field is encoded via + the Label Set field of [Gen-Encode]. 5. Resource Properties Encoding Within a WSON network element (NE) there may be resources with signal compatibility constraints. These resources be regenerators, wavelength converters, etc... Such resources may also constitute the network element as a whole as in the case of an electro optical switch. This section primarily focuses on the signal compatibility and processing properties of such a resource block. The fundamental properties of a resource block, such as a regenerator or wavelength converter, are: - (a) Input constraints (shared ingress, modulation, FEC, bit rate, + (a) Input constraints (shared input, modulation, FEC, bit rate, GPID) (b) Processing capabilities (number of resources in a block, regeneration, performance monitoring, vendor specific) - (c) Output Constraints (shared egress, modulation, FEC) + (c) Output Constraints (shared output, 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 compatibility properties, processing properties, 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | RB Set Field | : : +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |I|E| Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - | Input Modulation Type List Sub-Sub-TLV (opt) | + | Modulation Type List Sub-Sub-TLV (opt) | : : +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - | Input FEC Type List Sub-Sub-TLV (opt) | + | FEC Type List Sub-Sub-TLV (opt) | : : +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Input Client Signal Type Sub-Sub-TLV (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) | - : : - +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - Where I and E, the shared ingress/egress indicator, is set to 1 if - the resource blocks identified in the RB set field utilized a shared - fiber for ingress/egress access and set to 0 otherwise. - -5.2. Input Modulation Format List Sub-Sub-TLV + Where I and E, the shared input/output indicator, is set to 1 if the + resource blocks identified in the RB set field utilized a shared + fiber for input/output access and set to 0 otherwise. - This sub-sub-TLV contains a list of acceptable input modulation - formats. +5.2. Modulation Format List Sub-Sub-TLV - Type := Input Modulation Format List + This sub-sub-TLV contains a list of acceptable modulation formats. + Type := 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 standard modulation field 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 | Length | + |S|I|E| Modulation ID | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Where S bit set to 1 indicates a standardized modulation format and S bit set to 0 indicates a vendor specific modulation format. The length is the length in bytes of the entire modulation type field. Where I bit set to 1 indicates it is an input modulation constraint - and I bit set to 0 indicates it is an output modulation constraint. + and E bit set to 1 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 following I and E bit combination are defined: - The format for the standardized type for the input modulation is - given by: + I E + + 0 0 Invalid + + 1 0 Input modulation + + 0 1 Output modulation + + 1 1 Input and output modulation + + The format for the standardized type for the 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 | Length | + |1|X|X| Modulation ID | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 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. @@ -713,27 +742,26 @@ 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: + The format for vendor specific modulation 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 Modulation ID | Length | + |0|X|X| Vendor Modulation ID | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Enterprise Number | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ : Any vendor specific additional modulation parameters : +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Vendor Modulation ID This is a vendor assigned identifier for the modulation type. @@ -741,63 +769,59 @@ A unique identifier of an organization encoded as a 32-bit integer. Enterprise Numbers are assigned by IANA and managed through an IANA registry [RFC2578]. Vendor Specific Additional parameters There can be potentially additional parameters characterizing the vendor specific modulation. -5.3. Input FEC Type List Sub-Sub-TLV +5.3. FEC Type List Sub-Sub-TLV This sub-sub-TLV contains a list of acceptable FEC types. - Type := Input FEC Type field List + Type := FEC Type field List Value := A list of FEC type Fields 5.3.1. FEC Type Field The FEC type Field may consist of two different formats of fields: a standard FEC field or a vendor specific FEC 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| FEC ID | Length | + |S|I|E| FEC ID | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Possible additional FEC parameters depending upon | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ : the FEC ID : +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 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 length in bytes of the entire FEC type field. - Where I bit set to 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 same as the input FEC. In such case, no FEC conversion is - performed. + Where I bit set to 1 indicates it is an input FEC constraint and E + bit set to 1 indicates it is an output FEC constraint. The length is the length in bytes of the entire FEC type field. - The format for input standard FEC field is given by: + The format for 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 | Length | + |1|X|X| FEC ID | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Possible additional FEC parameters depending upon | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ : the FEC ID : +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Takes on the following currently defined values for the standard FEC ID: 0 Reserved @@ -827,21 +851,21 @@ (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 | Length | + |0|X|X| Vendor FEC ID | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Enterprise Number | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ : Any vendor specific additional FEC parameters : +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Vendor FEC ID This is a vendor assigned identifier for the FEC type. @@ -860,22 +884,22 @@ This sub-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 following bit rate - range field: + The bit rate range list sub-sub-TLV makes use of the 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Starting Bit Rate | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Ending Bit Rate | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ The starting and ending bit rates are given as 32 bit IEEE floating @@ -919,66 +943,53 @@ : | : +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | GPID #N | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Where the number of GPIDs is an integer greater than or equal to one. 5.6. Processing Capability List Sub-Sub-TLV - This sub-sub-TLV contains a list of resource block processing + This sub-sub-TLV contains a list of resource processing capabilities. Type := Processing Capabilities List Value := A list of Processing Capabilities Fields - The processing capability list sub-TLV is a list of WSON network - element (NE) that can perform signal processing functions including: - - 1. Number of Resources within the block + The processing capability list sub-sub-TLV is a list of capabilities + that can be achieved through the referred resources:: - 2. Regeneration capability + 1. Regeneration capability - 3. Fault and performance monitoring + 2. Fault and performance monitoring - 4. Vendor Specific capability + 3. Vendor Specific capability Note that the code points for Fault and performance monitoring and vendor specific capability are subject to further study. 5.6.1. Processing Capabilities Field The processing capability field is then given by: 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Processing Cap ID | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Possible additional capability parameters depending upon | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ : the processing ID : +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - When the processing Cap ID is "number of resources" the 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 - +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - | Processing Cap ID | Length = 8 | - +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - | Number of resources per block | - +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - When the processing Cap ID is "regeneration capability", the following additional capability parameters are provided in 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | T | C | Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ @@ -995,39 +1006,22 @@ Where C bit indicates the capability of regenerator: C=0: Reserved C=1: Fixed Regeneration Point C=2: Selective Regeneration Point Note that when the capability of regenerator is indicated to be Selective Regeneration Pools, regeneration pool properties such as - ingress and egress restrictions and availability need to be - specified. This encoding is to be determined in the later revision. - -5.7. Output Modulation Format List Sub-Sub-TLV - - This sub-sub-TLV contains a list of available output modulation - formats. - - Type := Output Modulation Format List - - Value := A list of Modulation Format Fields - -5.8. Output FEC Type List Sub-Sub-TLV - - This sub-sub-TLV contains a list of output FEC types. - - Type := Output FEC Type field List - - Value := A list of FEC type Fields + input and output restrictions and availability need to be specified. + This encoding is to be determined in the later revision. 6. Security Considerations This document defines protocol-independent encodings for WSON information and does not introduce any security issues. However, other documents that make use of these encodings within protocol extensions need to consider the issues and risks associated with, inspection, interception, modification, or spoofing of any of this information. It is expected that any such documents will @@ -1045,124 +1039,118 @@ This document was prepared using 2-Word-v2.0.template.dot. APPENDIX A: Encoding Examples A.1. Wavelength Converter Accessibility Sub-TLV Example: Figure 1 shows a wavelength converter pool architecture know as - "shared per fiber". In this case the ingress and egress pool - matrices are simply: + "shared per fiber". In this case the input and output pool matrices + are simply: +-----+ +-----+ | 1 1 | | 1 0 | WI =| |, WE =| | | 1 1 | | 0 1 | +-----+ +-----+ +-----------+ +------+ | |--------------------->| | | |--------------------->| C | /| | |--------------------->| o | /D+--->| |--------------------->| m | - + e+--->| | | b |=======> + + e+--->| | | b + |========> ========>| M| | Optical | +-----------+ | i | Port E1 Port I1 + u+--->| Switch | | WC Pool | | n | \x+--->| | | +-----+ | | e | \| | +----+->|WC #1|--+---->| r | | | | +-----+ | +------+ | | | | +------+ /| | | | +-----+ | | | /D+--->| +----+->|WC #2|--+---->| C | + e+--->| | | +-----+ | | o | - ========>| M| | | +-----------+ | m |=======> + ========>| M| | | +-----------+ | m + |========> Port I2 + u+--->| | | b | Port E2 \x+--->| |--------------------->| i | \| | |--------------------->| n | | |--------------------->| e | | |--------------------->| 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Connectivity=1| Reserved | Note: I1,I2 can connect to either WC1 or WC2 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - | Action=0 |0 1|0 0 0 0 0 0| Length = 12 | + | Action=0 |0| Reserved | Length = 12 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Link Local Identifier = #1 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Link Local Identifier = #2 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - | Action=0 |1| Reserved | Length = 12 | - +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - | RB ID = #1 | + | Action=0 |1| Reserved | Length = 8 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - | RB ID = #2 | + | RB ID = #1 | RB ID = #2 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - Note: WC1 can only connect to E1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - | Action=0 |1 0|0 0 0 0 0 0| Length = 8 | + | Action=0 |1| Reserved | Length = 8 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Link Local Identifier = #1 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Action=0 |0| Reserved | Length = 8 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - | RB ID = #1 | + | RB ID = #1 | zero padding | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - Note: WC2 can only connect to E2 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - | Action=0 |1 0|0 0 0 0 0 0| Length = 8 | + | Action=0 |1| Reserved | Length = 8 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Link Local Identifier = #2 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - | Action=0 |0| Reserved | Length = 8 | + | Action=0 |0| | Length = 8 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - | RB ID = #2 | + | RB ID = #2 | zero padding | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ A.2. Wavelength Conversion Range Sub-TLV Example: This example, based on figure 1, shows how to represent the wavelength conversion range of wavelength converters. Suppose the wavelength range of input and output of WC1 and WC2 are {L1, L2, L3, L4}: 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 | Length = 12 | - +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - | WC ID = #1 | + | Action=0 |1| Reserved | Length = 8 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - | WC ID = #2 | + | WC ID = #1 | WC ID = #2 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - Note: wavelength input range +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 2 | Num Wavelengths = 4 | Length = 8 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |Grid | C.S. | Reserved | 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 Figure 2 shows an electronic switch fabric surrounded by DWDM @@ -1180,37 +1168,40 @@ Hence the attention will be focused on the sub-TLV: ::= [...][...] /| +-----------+ +-------------+ +------+ /D+--->| +--->|Tunable Laser|-->| | + e+--->| | +-------------+ | C | - ========>| M| | | ... | o |=======> + ========>| M| | | ... | o + |========> Port I1 + u+--->| | +-------------+ | m | Port E1 \x+--->| |--->|Tunable Laser|-->| b | \| | Electric | +-------------+ +------+ | Switch | /| | | +-------------+ +------+ /D+--->| +--->|Tunable Laser|-->| | + e+--->| | +-------------+ | C | - ========>| M| | | ... | o |=======> + ========>| M| | | ... | o + |========> Port I2 + u+--->| | +-------------+ | m | Port E2 \x+--->| +--->|Tunable Laser|-->| b | \| | | +-------------+ +------+ | | /| | | +-------------+ +------+ /D+--->| |--->|Tunable Laser|-->| | + e+--->| | +-------------+ | C | - ========>| M| | | ... | o |=======> + ========>| M| | | ... | o + |========> Port I3 + u+--->| | +-------------+ | m | Port E3 \x+--->| |--->|Tunable Laser|-->| b | \| +-----------+ +-------------+ +------+ Figure 2 An optical switch built around an electronic switching fabric. The resource block information will tell us about the processing constraints of the receivers, transmitters and the electronic switch. The resource availability information, although very simple, @@ -1221,60 +1212,55 @@ : 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | RB Set Field | : (only one resource block in this example with shared | | input/output case) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - |0|0| Reserved | + |0|1|1| Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - | Input Modulation Type List Sub-Sub-TLV | - : (The receivers can only process NRZ) : + | Modulation Type List Sub-Sub-TLV | + : NRZ : +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - | Input FEC Type List Sub-Sub-TLV | - : (Only Standard SDH and G.709 FECs ) : + | FEC Type List Sub-Sub-TLV | + : Standard SDH, G.709 FEC : +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Input Client Signal Type Sub-TLV | : (GPIDs for SDH and G.709) : +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Input Bit Rate Range List Sub-Sub-TLV | : (2.5Gbps, 10Gbps) : +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Processing Capabilities List Sub-Sub-TLV | : Fixed (non optional) 3R regeneration : - +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - | Output Modulation Type List Sub-Sub-TLV | - : NRZ : - +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - | Output FEC Type List Sub-Sub-TLV | - : Standard SDH, G.709 FECs : + : : +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Since there is fixed connectivity to resource blocks (the electronic switch) the is: 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - | Connectivity=1|Reserved | | + | Connectivity=0|Reserved | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - | Ingress Link Set Field A #1 | - : (All ingress links connect to resource) : + | Input Link Set Field A #1 | + : (All input links connect to resource) : +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | RB Set Field A #1 | : (trivial set only one resource block) : +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ - | Egress Link Set Field B #1 | - : (All egress links connect to resource) : + | Output Link Set Field B #1 | + : (All output links connect to resource) : +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 9. References 9.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, @@ -1317,48 +1303,54 @@ Wavelength Assignment Information Model for Wavelength Switched Optical Networks", work in progress: draft-ietf- ccamp-rwa-info, March 2009. 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 + Pierre Peloso + ALU + + Email: pierre.peloso@alcatel-lucent.com + Cyril Margaria - Nokia Siemens Networks - St Martin Strasse 76 - Munich, 81541 - Germany - Phone: +49 89 5159 16934 + NSN + Email: cyril.margaria@nsn.com Authors' Addresses Greg M. Bernstein (ed.) Grotto Networking Fremont California, USA Phone: (510) 573-2237 Email: gregb@grotto-networking.com