draft-ietf-ccamp-rwa-wson-encode-14.txt   draft-ietf-ccamp-rwa-wson-encode-15.txt 
Network Working Group G. Bernstein Network Working Group G. Bernstein
Internet Draft Grotto Networking Internet Draft Grotto Networking
Intended status: Standards Track Y. Lee Intended status: Standards Track Y. Lee
Expires: October 2012 D. Li Expires: February 2013 D. Li
Huawei Huawei
W. Imajuku W. Imajuku
NTT NTT
April 24, 2012 August 8, 2012
Routing and Wavelength Assignment Information Encoding for Routing and Wavelength Assignment Information Encoding for
Wavelength Switched Optical Networks Wavelength Switched Optical Networks
draft-ietf-ccamp-rwa-wson-encode-14.txt draft-ietf-ccamp-rwa-wson-encode-15.txt
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with This Internet-Draft is submitted to IETF in full conformance with
the provisions of BCP 78 and BCP 79. the provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 38 skipping to change at page 1, line 38
months and may be updated, replaced, or obsoleted by other documents months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as at any time. It is inappropriate to use Internet-Drafts as
reference material or to cite them other than as "work in progress." reference material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
This Internet-Draft will expire on September 24, 2012. This Internet-Draft will expire on February 8, 2013.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 43 skipping to change at page 2, line 43
information to a path computation element (PCE). information to a path computation element (PCE).
Conventions used in this document Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC-2119 [RFC2119]. document are to be interpreted as described in RFC-2119 [RFC2119].
Table of Contents Table of Contents
1. Introduction...................................................4 1. Introduction...................................................3
1.1. Revision History..........................................4 1.1. Revision History..........................................4
1.1.1. Changes from 00 draft................................4 1.1.1. Changes from 00 draft................................4
1.1.2. Changes from 01 draft................................5 1.1.2. Changes from 01 draft................................5
1.1.3. Changes from 02 draft................................5 1.1.3. Changes from 02 draft................................5
1.1.4. Changes from 03 draft................................5 1.1.4. Changes from 03 draft................................5
1.1.5. Changes from 04 draft................................5 1.1.5. Changes from 04 draft................................5
1.1.6. Changes from 05 draft................................5 1.1.6. Changes from 05 draft................................5
1.1.7. Changes from 06 draft................................5 1.1.7. Changes from 06 draft................................5
1.1.8. Changes from 07 draft................................6 1.1.8. Changes from 07 draft................................5
1.1.9. Changes from 08 draft................................6 1.1.9. Changes from 08 draft................................6
1.1.10. Changes from 09 draft...............................6 1.1.10. Changes from 09 draft...............................6
1.1.11. Changes from 10 draft...............................6 1.1.11. Changes from 10 draft...............................6
1.1.12. Changes from 11 draft...............................6 1.1.12. Changes from 11 draft...............................6
1.1.13. Changes from 12 draft...............................6 1.1.13. Changes from 12 draft...............................6
1.1.14. Changes from 13 draft...............................6 1.1.14. Changes from 13 draft...............................6
1.1.15. Changes from 14 draft...............................7
2. Terminology....................................................7 2. Terminology....................................................7
3. Resources, Blocks, Sets, and the Resource Pool.................7 3. Resources, Blocks, Sets, and the Resource Pool.................7
3.1. Resource Block Set Field..................................8 3.1. Resource Block Set Field..................................8
4. Resource Pool Accessibility/Availability......................10 4. Resource Pool Accessibility/Availability......................10
4.1. Resource Pool Accessibility Sub-TLV......................10 4.1. Resource Pool Accessibility Sub-TLV......................10
4.2. Resource Block Wavelength Constraints Sub-TLV............12 4.2. Resource Block Wavelength Constraints Sub-TLV............12
4.3. Resource Pool State Sub-TLV..............................14 4.3. Resource Pool State Sub-TLV..............................14
4.4. Block Shared Access Wavelength Availability sub-TLV......15 4.4. Block Shared Access Wavelength Availability sub-TLV......15
5. Resource Properties Encoding..................................16 5. Resource Properties Encoding..................................16
5.1. Resource Block Information Sub-TLV.......................17 5.1. Resource Block Information Sub-TLV.......................17
5.2. Modulation Format List Sub-Sub-TLV.......................17 5.2. Optical Interface Class List(s) Sub-Sub-TLV..............17
5.2.1. Modulation Format Field.............................18 5.2.1. Optical Interface Class Format......................18
5.3. FEC Type List Sub-Sub-TLV................................20 5.3. Input Client Signal List Sub-Sub-TLV.....................19
5.3.1. FEC Type Field......................................20 5.4. Processing Capability List Sub-Sub-TLV...................20
5.4. Input Bit Range List Sub-Sub-TLV.........................22 5.4.1. Processing Capabilities Field.......................20
5.4.1. Bit Range Field.....................................22 6. Security Considerations.......................................22
5.5. Input Client Signal List Sub-Sub-TLV.....................23 7. IANA Considerations...........................................22
5.6. Processing Capability List Sub-Sub-TLV...................24 8. Acknowledgments...............................................22
5.6.1. Processing Capabilities Field.......................24 APPENDIX A: Encoding Examples....................................23
6. Security Considerations.......................................26 A.1. Wavelength Converter Accessibility Sub-TLV...............23
7. IANA Considerations...........................................26 A.2. Wavelength Conversion Range Sub-TLV......................25
8. Acknowledgments...............................................26 A.3. An OEO Switch with DWDM Optics...........................25
APPENDIX A: Encoding Examples....................................27 9. References....................................................28
A.1. Wavelength Converter Accessibility Sub-TLV...............27 9.1. Normative References.....................................28
A.2. Wavelength Conversion Range Sub-TLV......................29 9.2. Informative References...................................28
A.3. An OEO Switch with DWDM Optics...........................29 10. Contributors.................................................30
9. References....................................................32 Authors' Addresses...............................................31
9.1. Normative References.....................................32 Intellectual Property Statement..................................32
9.2. Informative References...................................32 Disclaimer of Validity...........................................32
10. Contributors.................................................34
Authors' Addresses...............................................35
Intellectual Property Statement..................................36
Disclaimer of Validity...........................................36
1. Introduction 1. Introduction
A Wavelength Switched Optical Network (WSON) is a Wavelength A Wavelength Switched Optical Network (WSON) is a Wavelength
Division Multiplexing (WDM) optical network in which switching is Division Multiplexing (WDM) optical network in which switching is
performed selectively based on the center wavelength of an optical performed selectively based on the center wavelength of an optical
signal. signal.
[RFC6163] describes a framework for Generalized Multiprotocol Label [RFC6163] describes a framework for Generalized Multiprotocol Label
Switching (GMPLS) and Path Computation Element (PCE) control of a Switching (GMPLS) and Path Computation Element (PCE) control of a
skipping to change at page 7, line 14 skipping to change at page 7, line 8
Enhanced section 4.2 encoding to allow for optionality of input or Enhanced section 4.2 encoding to allow for optionality of input or
output wavelength set fields. output wavelength set fields.
Clarified that wavelength set fields use the Label Set field Clarified that wavelength set fields use the Label Set field
encoding from [Gen-Encode]. encoding from [Gen-Encode].
Enhanced section 5.1 encoding to simplify the Modulation and FEC Enhanced section 5.1 encoding to simplify the Modulation and FEC
input and output cases. input and output cases.
1.1.15. Changes from 14 draft
OIC changes per workgroup request. Removed FEC type and modulation
type. Fixed versioning error and return RB identifiers to 32 bits.
2. Terminology 2. Terminology
CWDM: Coarse Wavelength Division Multiplexing. CWDM: Coarse Wavelength Division Multiplexing.
DWDM: Dense Wavelength Division Multiplexing. DWDM: Dense Wavelength Division Multiplexing.
FOADM: Fixed Optical Add/Drop Multiplexer. FOADM: Fixed Optical Add/Drop Multiplexer.
ROADM: Reconfigurable Optical Add/Drop Multiplexer. A reduced port ROADM: Reconfigurable Optical Add/Drop Multiplexer. A reduced port
count wavelength selective switching element featuring input and count wavelength selective switching element featuring input and
skipping to change at page 9, line 8 skipping to change at page 9, line 8
of these blocks allows one to efficiently describe common properties of these blocks allows one to efficiently describe common properties
of 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 non-trivial, of the resource pool. The RB Set field is defined in a
similar manner to the label set concept of [RFC3471]. similar manner to the label set concept of [RFC3471].
The information carried in a RB set field is defined by: The information carried in a RB set field is defined by:
0 1 2 3 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 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 | | Action |C| Reserved | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| RB Identifier 1 | RB Identifier 2 | | RB Identifier 1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: : : : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| RB Identifier n-1 | RB Identifier n | | RB Identifier n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Action: 8 bits Action: 8 bits
0 - Inclusive List 0 - Inclusive List
Indicates that the TLV contains one or more RB elements that are Indicates that the TLV contains one or more RB elements that are
included in the list. included in the list.
2 - Inclusive Range(s) 2 - Inclusive Range(s)
Indicates that the TLV contains one or more ranges of RBs. Each 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 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 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 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 range. Note that the Length field is used to determine the number of
ranges. ranges.
E (Even bit): Set to 0 denotes an odd number of RB identifiers in C (Connectivity bit): Set to 0 to denote fixed (possibly multi-
the list (last entry zero pad); Set to 1 denotes an even number of cast) connectivity; Set to 1 to denote potential (switched)
RB identifiers in the list (no zero padding). This applies only if connectivity. Used in resource pool accessibility sub-TLV. Ignored
Action == 0. elsewhere.
Reserved: 7 bits Reserved: 7 bits
This field is reserved. It MUST be set to zero on transmission and This field is reserved. It MUST be set to zero on transmission and
MUST be ignored on receipt. MUST be ignored on receipt.
Length: 16 bits Length: 16 bits
The total length of this field in bytes. The total length of this field in bytes.
skipping to change at page 17, line 24 skipping to change at page 17, line 24
This sub-TLV has the following format: This sub-TLV has the following format:
0 1 2 3 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 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 | | RB Set Field |
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I|E| Reserved | |I|E| Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Modulation Type List Sub-Sub-TLV (opt) | | Optical Interface Class List(s) Sub-Sub-TLV (opt) |
: :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| FEC Type List Sub-Sub-TLV (opt) |
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Client Signal Type Sub-Sub-TLV (opt) | | Input Client Signal Type Sub-Sub-TLV (opt) |
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Input Bit Rate Range List Sub-Sub-TLV (opt) | | Input Bit Rate Range List Sub-Sub-TLV (opt) |
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Processing Capabilities List Sub-Sub-TLV (opt) | | Processing Capabilities List Sub-Sub-TLV (opt) |
: : : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Where I and E, the shared input/output indicator, is set to 1 if the 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 resource blocks identified in the RB set field utilized a shared
fiber for input/output access and set to 0 otherwise. fiber for input/output access and set to 0 otherwise.
5.2. Modulation Format List Sub-Sub-TLV 5.2. Optical Interface Class List(s) Sub-Sub-TLV
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|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 E bit set to 1 indicates it is an output modulation constraint.
The following I and E bit combination are defined:
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|X|X| Modulation ID | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Possible additional modulation parameters depending upon |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: the modulation ID :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 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|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.
Enterprise Number
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. FEC Type List Sub-Sub-TLV
This sub-sub-TLV contains a list of acceptable FEC types.
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|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 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 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|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
1 G.709 RS FEC
2 G.709V compliant Ultra FEC
3 G.975.1 Concatenated FEC The list of Optical Interface Class sub-sub-TLV has the following
(RS(255,239)/CSOC(n0/k0=7/6,J=8)) format:
4 G.975.1 Concatenated FEC (BCH(3860,3824)/BCH(2040,1930)) 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Reserved |I|E|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Optical Interface Classes |
: :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5 G.975.1 Concatenated FEC (RS(1023,1007)/BCH(2407,1952)) The following I and E combination are defined:
6 G.975.1 Concatenated FEC (RS(1901,1855)/Extended Hamming I E
Product Code (512,502)X(510,500))
7 G.975.1 LDPC Code 0 0 Invalid
8 G.975.1 Concatenated FEC (Two orthogonally concatenated 1 0 Optical Interface Class List acceptable in input
BCH codes)
9 G.975.1 RS(2720,2550) 0 1 Optical Interface Class List available in output
10 G.975.1 Concatenated FEC (Two interleaved extended BCH 1 1 Optical Interface Class List available on both input and
(1020,988) codes) output.
Where RS stands for Reed-Solomon and BCH for Bose-Chaudhuri- The Resource Block MAY contain one or more lists according to
Hocquengham. input/output flags. The Optical Interface Class format is defined
within [x-ref-tbd].
The format for input vendor-specific FEC field is given by: 5.2.1. Optical Interface Class Format
0 1 2 3 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 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|X|X| Vendor FEC ID | Length | |S| Reserved | OI Code Points |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Enterprise Number | | Optical Interface Class |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: Any vendor specific additional FEC parameters : | Optical Interface Class (Cont.) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Vendor FEC ID Where the first 32 bits of the encoding shall be used to identify
the semantic of the Optical Interface Class in the following way:
This is a vendor assigned identifier for the FEC type.
Enterprise Number
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 FEC parameters S Standard bit.
There can be potentially additional parameters characterizing the S=0, identify not ITU code points
vendor specific FEC.
5.4. Input Bit Range List Sub-Sub-TLV S=1, identify ITU application codes
This sub-sub-TLV contains a list of acceptable input bit rate With S=0, the OI Code Points field can take the following
ranges. values:
Type := Input Bit Range List 0: reserved
Value := A list of Bit Range Fields 1: Vendor Specific Optical Interface Class.
5.4.1. Bit Range Field With S=1, the OI Code Points field can take the following
values:
The bit rate range list sub-sub-TLV makes use of the following bit 0: reserved
rate range field:
0 1 2 3 1: [ITU-G.698.1] application code.
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 2: [ITU-G.698.2] application code.
point numbers in bits per second. Note that the starting bit rate is
less than or equal to the ending bit rate.
The bit rate range list sub-TLV is then given by: 3: [ITU-G.959.1] application code.
0 1 2 3 In case of ITU Application Code, there should be a mapping between
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 the string defining the application code and the 64 bits number
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ implementing the optical interface class.
| |
+-+-+-+-+-+-+-+-+-+-+-+-+ Bit Range Field #1 +-+-+-+-+-+-+-+-+-+
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: : :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+-+-+-+-+-+-+-+-+-+-+-+-+ Bit Range Field #M +-+-+-+-+-+-+-+-+-+
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
5.5. Input Client Signal List Sub-Sub-TLV 5.3. Input Client Signal List Sub-Sub-TLV
This sub-sub-TLV contains a list of acceptable input client signal This sub-sub-TLV contains a list of acceptable input client signal
types. types.
Type := Input Client Signal List Type := Input Client Signal List
Value := A list of GPIDs Value := A list of GPIDs
The acceptable client signal list sub-TLV is a list of Generalized The acceptable client signal list sub-TLV is a list of Generalized
Protocol Identifiers (GPIDs). GPIDs are assigned by IANA and many Protocol Identifiers (GPIDs). GPIDs are assigned by IANA and many
skipping to change at page 24, line 18 skipping to change at page 20, line 18
| Number of GPIDs | GPID #1 | | Number of GPIDs | GPID #1 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
: | : : | :
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| GPID #N | | | GPID #N | |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Where the number of GPIDs is an integer greater than or equal to Where the number of GPIDs is an integer greater than or equal to
one. one.
5.6. Processing Capability List Sub-Sub-TLV 5.4. Processing Capability List Sub-Sub-TLV
This sub-sub-TLV contains a list of resource processing This sub-sub-TLV contains a list of resource processing
capabilities. capabilities.
Type := Processing Capabilities List Type := Processing Capabilities List
Value := A list of Processing Capabilities Fields Value := A list of Processing Capabilities Fields
The processing capability list sub-sub-TLV is a list of capabilities The processing capability list sub-sub-TLV is a list of capabilities
that can be achieved through the referred resources:: that can be achieved through the referred resources::
1. Regeneration capability 1. Regeneration capability
2. Fault and performance monitoring 2. Fault and performance monitoring
3. Vendor Specific capability 3. Vendor Specific capability
Note that the code points for Fault and performance monitoring and Note that the code points for Fault and performance monitoring and
vendor specific capability are subject to further study. vendor specific capability are subject to further study.
5.6.1. Processing Capabilities Field 5.4.1. Processing Capabilities Field
The processing capability field is then given by: The processing capability field is then given by:
0 1 2 3 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 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 | | Processing Cap ID | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Possible additional capability parameters depending upon | | Possible additional capability parameters depending upon |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 End of changes. 45 change blocks. 
254 lines changed or deleted 87 lines changed or added

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