Internet Engineering Task Force (IETF)                 G. Bernstein, Ed.
Request for Comments: 7581                             Grotto Networking
Category: Standards Track                                    Y. Lee, Ed.
ISSN: 2070-1721                                                    D. Li
                                                                  Huawei
                                                              W. Imajuku
                                                                     NTT
                                                                  J. Han
                                                                  Huawei
                                                               June 2015
        
Internet Engineering Task Force (IETF)                 G. Bernstein, Ed.
Request for Comments: 7581                             Grotto Networking
Category: Standards Track                                    Y. Lee, Ed.
ISSN: 2070-1721                                                    D. Li
                                                                  Huawei
                                                              W. Imajuku
                                                                     NTT
                                                                  J. Han
                                                                  Huawei
                                                               June 2015
        

Routing and Wavelength Assignment Information Encoding for Wavelength Switched Optical Networks

波长交换光网络的路由和波长分配信息编码

Abstract

摘要

A Wavelength Switched Optical Network (WSON) requires certain key information fields be made available to facilitate path computation and the establishment of Label Switched Paths (LSPs). The information model described in "Routing and Wavelength Assignment Information Model for Wavelength Switched Optical Networks" (RFC 7446) shows what information is required at specific points in the WSON. Part of the WSON information model contains aspects that may be of general applicability to other technologies, while other parts are specific to WSONs.

波长交换光网络(WSON)要求提供某些关键信息字段,以便于路径计算和标签交换路径(LSP)的建立。“波长交换光网络的路由和波长分配信息模型”(RFC 7446)中描述的信息模型显示了WSON中特定点所需的信息。WSON信息模型的一部分包含可能对其他技术具有普遍适用性的方面,而其他部分则特定于WSON。

This document provides efficient, protocol-agnostic encodings for the WSON-specific information fields. It is intended that 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).

本文档为WSON特定信息字段提供了高效的、协议无关的编码。协议特定文件将参考本备忘录,以说明信息如何用于特定用途。这种编码可用于扩展GMPLS信令和路由协议。此外,这些编码可以被其他机制用来将相同的信息传递给路径计算元素(PCE)。

Status of This Memo

关于下段备忘

This is an Internet Standards Track document.

这是一份互联网标准跟踪文件。

This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741.

本文件是互联网工程任务组(IETF)的产品。它代表了IETF社区的共识。它已经接受了公众审查,并已被互联网工程指导小组(IESG)批准出版。有关互联网标准的更多信息,请参见RFC 5741第2节。

Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7581.

有关本文件当前状态、任何勘误表以及如何提供反馈的信息,请访问http://www.rfc-editor.org/info/rfc7581.

Copyright Notice

版权公告

Copyright (c) 2015 IETF Trust and the persons identified as the document authors. All rights reserved.

版权所有(c)2015 IETF信托基金和确定为文件作者的人员。版权所有。

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 warranty as described in the Simplified BSD License.

本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件,因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本,并提供简化BSD许可证中所述的无担保。

Table of Contents

目录

   1. Introduction ....................................................4
      1.1. Terminology ................................................4
      1.2. Conventions Used in This Document ..........................5
   2. Resources, Resource Blocks, and the Resource Pool ...............5
      2.1. Resource Block Set Field ...................................6
   3. Resource Accessibility/Availability .............................7
      3.1. Resource Accessibility Field ...............................7
      3.2. Resource Wavelength Constraints Field ......................9
      3.3. Resource Block Pool State Field ...........................10
      3.4. Resource Block Shared Access Wavelength
           Availability Field ........................................12
   4. Resource Block Information Field ...............................13
      4.1. Optical Interface Class List Subfield .....................15
           4.1.1. ITU-T G.698.1 Application Code Mapping .............17
           4.1.2. ITU-T G.698.2 Application Code Mapping .............18
           4.1.3. ITU-T G.959.1 Application Code Mapping .............20
           4.1.4. ITU-T G.695 Application Code Mapping ...............22
      4.2. Acceptable Client Signal List Subfield ....................23
      4.3. Input Bit Rate List Subfield ..............................24
      4.4. Processing Capability List Subfield .......................24
   5. Security Considerations ........................................26
   6. IANA Considerations ............................................26
      6.1. Types for Subfields of WSON Resource Block Information ....26
   7. References .....................................................27
      7.1. Normative References ......................................27
      7.2. Informative References ....................................28
   Appendix A. Encoding Examples .....................................30
      A.1. Wavelength Converter Accessibility Field ..................30
      A.2. Wavelength Conversion Range Field .........................32
      A.3. An OEO Switch with DWDM Optics ............................32
   Contributors ......................................................35
   Authors' Addresses ................................................37
        
   1. Introduction ....................................................4
      1.1. Terminology ................................................4
      1.2. Conventions Used in This Document ..........................5
   2. Resources, Resource Blocks, and the Resource Pool ...............5
      2.1. Resource Block Set Field ...................................6
   3. Resource Accessibility/Availability .............................7
      3.1. Resource Accessibility Field ...............................7
      3.2. Resource Wavelength Constraints Field ......................9
      3.3. Resource Block Pool State Field ...........................10
      3.4. Resource Block Shared Access Wavelength
           Availability Field ........................................12
   4. Resource Block Information Field ...............................13
      4.1. Optical Interface Class List Subfield .....................15
           4.1.1. ITU-T G.698.1 Application Code Mapping .............17
           4.1.2. ITU-T G.698.2 Application Code Mapping .............18
           4.1.3. ITU-T G.959.1 Application Code Mapping .............20
           4.1.4. ITU-T G.695 Application Code Mapping ...............22
      4.2. Acceptable Client Signal List Subfield ....................23
      4.3. Input Bit Rate List Subfield ..............................24
      4.4. Processing Capability List Subfield .......................24
   5. Security Considerations ........................................26
   6. IANA Considerations ............................................26
      6.1. Types for Subfields of WSON Resource Block Information ....26
   7. References .....................................................27
      7.1. Normative References ......................................27
      7.2. Informative References ....................................28
   Appendix A. Encoding Examples .....................................30
      A.1. Wavelength Converter Accessibility Field ..................30
      A.2. Wavelength Conversion Range Field .........................32
      A.3. An OEO Switch with DWDM Optics ............................32
   Contributors ......................................................35
   Authors' Addresses ................................................37
        
1. Introduction
1. 介绍

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)是波分复用(WDM)光网络,其中基于光信号的中心波长选择性地执行切换。

[RFC6163] describes a framework for Generalized Multiprotocol Label Switching (GMPLS) and Path Computation Element (PCE) control of a WSON. Based on this framework, [RFC7446] 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).

[RFC6163]描述了WSON的通用多协议标签交换(GMPLS)和路径计算元素(PCE)控制框架。基于此框架,[RFC7446]描述了一个信息模型,该模型指定了在WSON中的各个点需要哪些信息,以便计算路径和建立标签交换路径(LSP)。

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 PCE. Note that since these encodings are efficient, they can provide more accurate analysis of the control-plane communications/processing load for WSONs looking to utilize a GMPLS control plane.

本文档提供了WSON中路由和波长分配(RWA)过程所需信息的有效编码。这种编码可用于扩展GMPLS信令和路由协议。此外,这些编码可由其他机制用于将该相同信息传送到PCE。注意,由于这些编码是有效的,它们可以为希望利用GMPLS控制平面的WSON提供更精确的控制平面通信/处理负载分析。

In parallel to this document, [RFC7579] provides efficient encodings of information needed by the routing and label assignment process that are potentially applicable to a wider range of technologies.

与本文件平行,[RFC7579]提供了路由和标签分配过程所需信息的有效编码,这些信息可能适用于更广泛的技术。

1.1. Terminology
1.1. 术语

Refer to [RFC6163] for definitions of the following:

有关以下内容的定义,请参考[RFC6163]:

o Coarse Wavelength Division Multiplexing (CWDM)

o 粗波分复用(CWDM)

o Dense Wavelength Division Multiplexing (DWDM)

o 密集波分复用(DWDM)

o Routing and Wavelength Assignment (RWA)

o 路由和波长分配(RWA)

o Wavelength Division Multiplexing (WDM)

o 波分复用(WDM)

Refer to Section 5 of [RFC7446] for definitions of the following:

关于以下定义,请参考[RFC7446]第5节:

o resource

o 资源

o resource block

o 资源块

o resource pool

o 资源库

The Optical Interface (OI) Code Point is a unique number that identifies all information related to optical characteristics of a physical interface.

光学接口(OI)代码点是唯一的编号,用于标识与物理接口光学特性相关的所有信息。

1.2. Conventions Used in This Document
1.2. 本文件中使用的公约

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

本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照RFC 2119[RFC2119]中所述进行解释。

2. Resources, Resource Blocks, and the Resource Pool
2. 资源、资源块和资源池

This section provides encodings for the information fields defined in [RFC7446] that have applicability to WSON. The encodings are designed to be suitable for use in the GMPLS routing protocols OSPF [RFC4203] and IS-IS [RFC5307] and in the PCE Communication Protocol (PCEP) [RFC5440]. Note that the information distributed in [RFC4203] and [RFC5307] is arranged via the nesting of sub-TLVs within TLVs; this document defines elements to be used within such constructs. Specific constructs of sub-TLVs and the nesting of sub-TLVs of the information fields defined by this document will be defined in the respective protocol enhancement documents.

本节为[RFC7446]中定义的适用于WSON的信息字段提供编码。编码设计为适合在GMPLS路由协议OSPF[RFC4203]和IS-IS[RFC5307]以及PCE通信协议(PCEP)[RFC5440]中使用。注意,[RFC4203]和[RFC5307]中分布的信息是通过子TLV在TLV中的嵌套排列的;本文档定义了在此类构造中使用的元素。本文件定义的信息字段的子TLV的具体构造和子TLV的嵌套将在相应的协议增强文件中定义。

This document defines the following information fields pertaining to resources within an optical node:

本文档定义了与光节点内资源相关的以下信息字段:

o Resource Accessibility <ResourceAccessibility>

o 资源可访问性<资源可访问性>

o Resource Wavelength Constraints <ResourceWaveConstraints>

o 资源波长约束<ResourceWaveConstraints>

o Resource Block Pool State <RBPoolState>

o 资源块池状态<RBPoolState>

o Resource Block Shared Access Wavelength Availability <RBSharedAccessWaveAvailability>

o 资源块共享访问波长可用性<RBSharedAccessWaveAvailability>

o Resource Block Information <ResourceBlockInfo>

o 资源块信息<ResourceBlockInfo>

Each of these information fields works with one or more sets of resources rather than just a single resource block. This motivates the field definition in Section 2.1.

这些信息字段中的每一个都使用一组或多组资源,而不仅仅是单个资源块。这推动了第2.1节中的字段定义。

2.1. Resource Block Set Field
2.1. 资源块集字段

In a WSON node that includes resource blocks (RBs), denoting subsets of these blocks allows one to efficiently describe common properties of the blocks and to describe the structure and characteristics, if nontrivial, of the resource pool. The Resource Block Set (RB Set) Field is defined in a similar manner to the label set concept of [RFC3471].

在包括资源块(RBs)的WSON节点中,表示这些块的子集允许人们有效地描述块的公共属性,并描述资源池的结构和特征(如果不重要的话)。资源块集(RB集)字段的定义方式与[RFC3471]的标签集概念类似。

The information carried in an RB Set Field is defined as follows:

RB集合字段中携带的信息定义如下:

       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                 |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                        RB Identifier 1                        |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      :                               :                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                        RB Identifier n                        |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        
       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                 |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                        RB Identifier 1                        |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      :                               :                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                        RB Identifier n                        |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        

Action: 8 bits

动作:8位

0 - Inclusive List

0-包含列表

Indicates that the TLV contains one or more RB elements that are included in the list.

指示TLV包含列表中包含的一个或多个RB元素。

1 - Inclusive Range(s)

1-包含范围(个)

Indicates that the TLV contains one or more ranges of RBs. Each individual range is denoted by two 32-bit RB identifiers. The first 32 bits is the RB identifier for the start of the range, and the next 32 bits is the RB identifier for the end of the range. Note that the Length field is used to determine the number of ranges.

指示TLV包含一个或多个RB范围。每个单独的范围由两个32位RB标识符表示。前32位是范围开始的RB标识符,下32位是范围结束的RB标识符。请注意,长度字段用于确定范围的数量。

C (Connectivity bit)

C(连接位)

Set to 0 to denote fixed (possibly multicast) connectivity, and set to 1 to denote potential (switched) connectivity. Used in Resource Accessibility field. Ignored elsewhere.

设置为0表示固定(可能是多播)连接,设置为1表示潜在(交换)连接。用于资源可访问性字段。在别处被忽略了。

Reserved: 7 bits

保留:7位

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

此字段是保留的。传输时必须将其设置为零,接收时必须忽略。

Length: 16 bits

长度:16位

The total length of this field in bytes.

此字段的总长度(字节)。

RB Identifier:

RB标识符:

The RB identifier represents the ID of the resource block, which is a 32-bit integer. The scope of the RB identifier is local to the node on which it is applied.

RB标识符表示资源块的ID,它是一个32位整数。RB标识符的范围是应用它的节点的本地范围。

Usage Note: The inclusive range "Action" can result in very compact encoding of resource sets, and it can be advantageous to number resource blocks in such a way so that status updates (dynamic information) can take advantage of this efficiency.

用法说明:包含范围“Action”可以导致资源集的编码非常紧凑,以这种方式对资源块进行编号是有利的,以便状态更新(动态信息)可以利用这种效率。

3. Resource Accessibility/Availability
3. 资源可及性/可用性

This section defines the information fields for dealing with accessibility and availability of resource blocks within a pool of resources. These include the <ResourceAccessibility>, <ResourceWaveConstraints>, <RBPoolState>, and <RBSharedAccessWaveAvailability> fields.

本节定义了用于处理资源池中资源块的可访问性和可用性的信息字段。这些字段包括<ResourceAccessibility>、<ResourceWaveConstraints>、<RBPoolState>和<RBSharedAccessWaveAvailability>字段。

3.1. Resource Accessibility Field
3.1. 资源可访问性字段

This information field describes the structure of the resource pool in relation to the switching device. In particular, it indicates the ability of an input port to reach sets of resources and the ability of sets of resources to reach a particular output port. This is the <PoolInputMatrix> and <PoolOutputMatrix> of [RFC7446].

此信息字段描述与交换设备相关的资源池的结构。特别是,它表示输入端口访问资源集的能力和资源集访问特定输出端口的能力。这是[RFC7446]的<PoolOutputMatrix>和<PoolOutputMatrix>。

The Resource Accessibility field is defined as follows:

资源可访问性字段定义如下:

       0                   1                   2                   3
       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |Reserved(8bits)|C|             Reserved (23 bits)              |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                    Input Link Set Field A #1                  |
      :                                                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                          RB Set Field A #1                    |
      :                                                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |         Additional Link set and RB set pairs as needed to     |
      :                    specify PoolInputMatrix                    :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                Output Link Set Field B #1                     |
      :                                                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |             RB Set B Field #1 (for output connectivity)       |
      :                                                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |         Additional Link Set and RB set pairs as needed to     |
      :                    specify PoolOutputMatrix                   :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        
       0                   1                   2                   3
       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |Reserved(8bits)|C|             Reserved (23 bits)              |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                    Input Link Set Field A #1                  |
      :                                                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                          RB Set Field A #1                    |
      :                                                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |         Additional Link set and RB set pairs as needed to     |
      :                    specify PoolInputMatrix                    :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                Output Link Set Field B #1                     |
      :                                                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |             RB Set B Field #1 (for output connectivity)       |
      :                                                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |         Additional Link Set and RB set pairs as needed to     |
      :                    specify PoolOutputMatrix                   :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        

Where:

哪里:

C (Connectivity bit): Connectivity indicates how the input/output ports connect to the resource blocks.

C(连接性位):连接性表示输入/输出端口如何连接到资源块。

0 - the device is fixed (e.g., a connected port must go through the resource block)

0-设备是固定的(例如,连接的端口必须通过资源块)

1 - the device is switched (e.g., a port can be configured to go through a resource but isn't required)

1-设备是交换的(例如,端口可以配置为通过资源,但不是必需的)

For the Input and Output Link Set Fields, the Link Set Field encoding defined in [RFC7579] is to be used.

对于输入和输出链接集字段,将使用[RFC7579]中定义的链接集字段编码。

Note that the direction parameter within the Link Set Field is used 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 field.

请注意,“链接集”字段中的“方向”参数用于指示链接集是输入链接集还是输出链接集,此字段中不允许使用此参数的双向值。

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

有关此编码的说明,请参见附录A.1。

3.2. Resource Wavelength Constraints Field
3.2. 资源波长限制字段

Resources, such as wavelength converters, etc., may have 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 Constraints fields 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 Constraints                   |
      :                                                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                Output Wavelength Constraints                  |
      :                                                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        
       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 Constraints                   |
      :                                                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                Output Wavelength Constraints                  |
      :                                                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        

I (Input):

I(输入):

1 - indicates the presence of the Input Wavelength Constraints field

1-表示存在输入波长约束字段

0 - indicates otherwise.

0-表示相反。

O (Output):

O(输出):

1 - indicates the presence of the Output Wavelength Constraints field

1-表示存在输出波长约束字段

0 - indicates otherwise.

0-表示相反。

B (Both):

B(两者):

1 - indicates that a single Wavelength Constraints field represents both Input and Output Wavelength Constraints fields.

1-表示单个波长约束字段同时表示输入和输出波长约束字段。

Currently, the only valid combinations of (I,O,B) are (1,0,0), (0,1,0), (1,1,0), and (0,0,1).

目前,(I,O,B)的唯一有效组合是(1,0,0),(0,1,0),(1,1,0)和(0,0,1)。

RB Set Field:

RB集合字段:

A set of resource blocks (RBs) that have the same wavelength restrictions.

具有相同波长限制的一组资源块(RB)。

Input Wavelength Constraints:

输入波长限制:

Indicates the wavelength input restrictions of the RBs in the corresponding RB set. This field is encoded via the Label Set Field of [RFC7579].

指示相应RB集合中RBs的波长输入限制。该字段通过[RFC7579]的标签集字段进行编码。

Output Wavelength Constraints:

输出波长限制:

Indicates the wavelength output restrictions of RBs in the corresponding RB set. This field is encoded via the Label Set Field of [RFC7579].

指示相应RB集合中RBs的波长输出限制。该字段通过[RFC7579]的标签集字段进行编码。

3.3. Resource Block Pool State Field
3.3. 资源块池状态字段

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 or a bitmap indicating whether a single resource is available or in use. The bitmap 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.

池的状态由具有特定特征的可用资源的数量给出。资源块集用于对感兴趣的资源的所有或子集进行编码。资源块集中资源的使用状态编码为16位整数值列表或指示单个资源可用或正在使用的位图。当资源块由单个资源组成时,位图编码是合适的。该信息可以是相对动态的,即,当建立或断开连接(LSP)时,该信息可能会发生变化。

       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                               |
      :                                                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        
       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                               |
      :                                                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        

Where:

哪里:

Action = 0 denotes a list of 16-bit integers, and Action = 1 denotes a bitmap. Action = 0 covers the case where there are multiple elements for each resource block. Action = 1 covers the case where each resource block only contains a single element.

Action=0表示16位整数的列表,Action=1表示位图。Action=0涵盖了每个资源块有多个元素的情况。Action=1涵盖了每个资源块仅包含单个元素的情况。

In both cases, the elements of the RB Set Field are in a one-to-one correspondence with the values in the RB Usage State area.

在这两种情况下,RB集合字段的元素与RB使用状态区域中的值一一对应。

       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 = 0    |    Reserved                                   |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                     RB Set Field                              |
      :                                                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                  RB#1 State   |      RB#2 State               |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      :                                                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                 RB#n-1 State  |   RB#n State or Padding       |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        
       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 = 0    |    Reserved                                   |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                     RB Set Field                              |
      :                                                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                  RB#1 State   |      RB#2 State               |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      :                                                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                 RB#n-1 State  |   RB#n State or Padding       |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        

RB#i State (16 bits, unsigned integer): Indicates the number of resources available in Resource Block #i.

RB#i状态(16位,无符号整数):表示资源块#i中可用的资源数。

Whether the last 16 bits is a wavelength converter (RB) state or padding is determined by the number of elements in the RB Set Field.

最后16位是波长转换器(RB)状态还是填充由RB Set字段中的元素数决定。

       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 = 1    |    Reserved                                   |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                     RB Set Field                              |
      :                                                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                  RB Usage State Bitmap                        |
      :                                                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                     ......             |      Padding Bits    |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        
       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 = 1    |    Reserved                                   |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                     RB Set Field                              |
      :                                                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                  RB Usage State Bitmap                        |
      :                                                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                     ......             |      Padding Bits    |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        

RB Usage State Bitmap: Variable length but must be a multiple of 4 bytes.

RB使用状态位图:长度可变,但必须是4字节的倍数。

Each bit indicates the usage status of one RB with 0 indicating the RB is available and 1 indicating the RB is in use. The sequence of the bitmap is ordered according to the RB Set Field with this element.

每个位表示一个RB的使用状态,0表示RB可用,1表示RB正在使用。位图的顺序根据带有此元素的RB Set字段进行排序。

Padding bits: Variable length

填充位:可变长度

3.4. Resource Block Shared Access Wavelength Availability Field
3.4. 资源块共享访问波长可用性字段

Resource blocks may be accessed via a shared fiber. If this is the case, then wavelength availability on these shared fibers is needed 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|O|B|                        Reserved                         |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                     RB Set Field                              |
      :                                                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |            Input Available Wavelength Set Field               |
      :                          (Optional)                           :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |             Output Available Wavelength Set Field             |
      :                          (Optional)                           :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        
       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 Available Wavelength Set Field               |
      :                          (Optional)                           :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |             Output Available Wavelength Set Field             |
      :                          (Optional)                           :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        

I (Input):

I(输入):

1 - indicates the presence of the Input Available Wavelength Set Field.

1-表示存在输入可用波长设置字段。

0 - indicates the absence of the Input Available Wavelength Set Field.

0-表示没有输入可用波长设置字段。

O (Output):

O(输出):

1 - indicates the presence of the Output Available Wavelength Set Field.

1-表示存在输出可用波长设置字段。

0 - indicates the absence of the Output Available Wavelength Set Field.

0-表示没有输出可用波长设置字段。

B (Both):

B(两者):

1 - indicates that a single Available Wavelength Set Field represents both Input and Output Available Wavelength Set Fields.

1-表示单个可用波长集字段同时表示输入和输出可用波长集字段。

Currently, the only valid combinations of (I,O,B) are (1,0,0), (0,1,0), (1,1,0), and (0,0,1).

目前,(I,O,B)的唯一有效组合是(1,0,0),(0,1,0),(1,1,0)和(0,0,1)。

RB Set Field:

RB集合字段:

A resource block set in which all the members share the same input or output fiber or both.

一种资源块集,其中所有成员共享相同的输入或输出光纤或两者。

Input Available Wavelength Set Field:

输入可用波长设置字段:

Indicates the wavelengths currently available (not being used) on the input fiber to this resource block. This field is encoded via the Label Set Field of [RFC7579].

指示此资源块的输入光纤上当前可用(未使用)的波长。该字段通过[RFC7579]的标签集字段进行编码。

Output Available Wavelength Set Field:

输出可用波长设置字段:

Indicates the wavelengths currently available (not being used) on the output fiber from this resource block. This field is encoded via the Label Set Field of [RFC7579].

指示此资源块的输出光纤上当前可用(未使用)的波长。该字段通过[RFC7579]的标签集字段进行编码。

4. Resource Block Information Field
4. 资源块信息字段

As defined in [RFC7446], the Resource Block Information <ResourceBlockInfo> field is used to represent resource signal constraints and processing capabilities of a node.

如[RFC7446]中所定义,资源块信息<ResourceBlockInfo>字段用于表示节点的资源信号约束和处理能力。

The fundamental properties of a resource block are:

资源块的基本属性包括:

o Optical Interface Class List(s)

o 光学接口类别列表

o Acceptable Client Signal (shared input, modulation, Forward Error Correction (FEC), bit rate, and Generalized Protocol Identifier (G-PID))

o 可接受的客户端信号(共享输入、调制、前向纠错(FEC)、比特率和通用协议标识符(G-PID))

o Input Bit Rate

o 输入比特率

o Processing Capabilities (number of resources in a block, regeneration, performance monitoring, vendor specific)

o 处理能力(块中的资源数量、重新生成、性能监控、特定于供应商)

<ResourceBlockInfo> fields are used to convey relatively static information about individual resource blocks, including the resource block properties and the number of resources in a block.

<ResourceBlockInfo>字段用于传递有关单个资源块的相对静态信息,包括资源块属性和块中资源的数量。

When more than one <ResourceBlockInfo> field is used, there are no ordering requirements amongst these fields. The length of the <ResourceBlockInfo> field is determined from the length of the object that includes it.

当使用多个<ResourceBlockInfo>字段时,这些字段之间没有订购要求。<ResourceBlockInfo>字段的长度由包含它的对象的长度决定。

The <ResourceBlockInfo> field has the following format:

<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
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                          RB Set Field                         |
      :                                                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |I|O|B|                       Reserved                          |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                        Optional Subfield 1                    |
      :                              ...                              :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      :                               :                               :
      :                               :                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                        Optional Subfield N                    |
      :                                                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        
       0                   1                   2                   3
       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                          RB Set Field                         |
      :                                                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |I|O|B|                       Reserved                          |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                        Optional Subfield 1                    |
      :                              ...                              :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      :                               :                               :
      :                               :                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                        Optional Subfield N                    |
      :                                                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        

The RB Set Field is described in Section 2.1.

第2.1节描述了RB Set字段。

The shared input or output indication is indicated by the first bit (I), the second bit (O), and the third bit (B).

共享输入或输出指示由第一位(I)、第二位(O)和第三位(B)指示。

I (Input):

I(输入):

1 - indicates if the resource blocks identified in the RB Set Field utilized a shared fiber for input access.

1-指示RB Set字段中标识的资源块是否使用共享光纤进行输入访问。

0 - indicates otherwise.

0-表示相反。

O (Output):

O(输出):

1 - indicates if the resource blocks identified in the RB Set Field utilized a shared fiber for output access.

1-指示RB Set字段中标识的资源块是否使用共享光纤进行输出访问。

0 - indicates otherwise.

0-表示相反。

B (Both):

B(两者):

1 - indicates if the resource blocks identified in the RB Set Field utilized a shared fiber for both input and output access.

1-指示RB Set字段中标识的资源块是否使用共享光纤进行输入和输出访问。

0 - indicates otherwise.

0-表示相反。

Currently, the only valid combinations of (I,O,B) are (1,0,0), (0,1,0), (1,1,0), and (0,0,1).

目前,(I,O,B)的唯一有效组合是(1,0,0),(0,1,0),(1,1,0)和(0,0,1)。

Zero or more Optional Subfields MAY be present. Optional Subfields have the following format:

可能存在零个或多个可选子字段。可选子字段具有以下格式:

       0                   1                   2                   3
       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |              Type             |             Length            |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                            Value...                           |
      .                                                               .
      .                                                               .
      .                                                               .
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        
       0                   1                   2                   3
       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |              Type             |             Length            |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                            Value...                           |
      .                                                               .
      .                                                               .
      .                                                               .
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        

The Length field defines the length of the value portion in bytes (thus, a subfield with no value portion would have a length of zero). The subfield is padded to 4-byte alignment; padding is not included in the Length field (so a 3-byte value would have a length of three, but the total size of the subfield would be 8 bytes). Unrecognized types are not processed. If multiple subfields of the same type are present, only the first of the type SHOULD be processed.

长度字段以字节为单位定义值部分的长度(因此,没有值部分的子字段的长度为零)。子字段填充为4字节对齐;长度字段中不包括填充(因此3字节值的长度为3,但子字段的总大小为8字节)。不处理无法识别的类型。如果存在相同类型的多个子字段,则只应处理该类型的第一个子字段。

The following sub-TLV types are defined:

定义了以下子TLV类型:

Value Length Sub-TLV Type

值长度子TLV类型

1 variable Optical Interface Class List 2 variable Acceptable Client Signal List 3 variable Input Bit Rate List 4 variable Processing Capability List

1可变光接口类别列表2可变可接受客户端信号列表3可变输入比特率列表4可变处理能力列表

See the IANA Considerations section for allocation of new types.

有关新类型的分配,请参见IANA注意事项部分。

4.1. Optical Interface Class List Subfield
4.1. 光接口类列表子字段

The Optical Interface Class List subfield has the following format:

光学接口类别列表子字段的格式如下:

       0                   1                   2                   3
       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                           Reserved                        |I|O|
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                   Optical Interface Classes                   |
      :                                                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        
       0                   1                   2                   3
       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                           Reserved                        |I|O|
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                   Optical Interface Classes                   |
      :                                                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        

The following I and O combination are defined:

定义了以下I和O组合:

   I   O
   -----
   0   0   Invalid
        
   I   O
   -----
   0   0   Invalid
        

1 0 Optical Interface Class List acceptable in input

10输入中可接受的光学接口类别列表

0 1 Optical Interface Class List available in output

0 1输出中可用的光学接口类列表

1 1 Optical Interface Class List available on both input and output.

1光学接口类别列表,可用于输入和输出。

The resource block MAY contain one or more lists according to the input/output flags.

根据输入/输出标志,资源块可以包含一个或多个列表。

The Optical Interface Classes format is defined as follows:

光学接口类格式定义如下:

     0                   1                   2                   3
     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |S|     Reserved                |    OI Code Points             |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |         Optical Interface Class                               |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |         Optical Interface Class  (Cont.)                      |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        
     0                   1                   2                   3
     0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |S|     Reserved                |    OI Code Points             |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |         Optical Interface Class                               |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |         Optical Interface Class  (Cont.)                      |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        

Where the first 32 bits of the encoding shall be used to identify the semantics of the Optical Interface Class in the following way:

其中,编码的前32位应用于以下方式识别光学接口类的语义:

S (Standard bit):

S(标准位):

S=0: identifies non-ITU code points

S=0:标识非ITU代码点

S=1: identifies ITU application codes

S=1:标识ITU应用程序代码

With S=0, the OI Code Points field can take the following value:

S=0时,OI代码点字段可以采用以下值:

0: reserved

0:保留

Future work may add support for vendor-specific application codes once the ITU-T has completed its work in that area.

一旦ITU-T完成其在该领域的工作,未来的工作可能会增加对供应商特定应用程序代码的支持。

With S=1, the OI Code Points field can take the following values:

S=1时,OI代码点字段可以采用以下值:

0: reserved

0:保留

1: [G.698.1] application code

1:[G.698.1]申请代码

2: [G.698.2] application code

2:[G.698.2]申请代码

3: [G.959.1] application code

3:[G.959.1]应用程序代码

4: [G.695] application code

4:[G.695]申请代码

In the case of ITU application codes, the mapping between the string defining the application code and the 64 bits implementing the optical interface class is given in the following sections.

在ITU应用程序代码的情况下,定义应用程序代码的字符串与实现光接口类的64位之间的映射在以下部分中给出。

4.1.1. ITU-T G.698.1 Application Code Mapping
4.1.1. ITU-T G.698.1应用程序代码映射

[G.698.1] defines the following application codes: DScW-ytz(v) and B-DScW-ytz(v). Where:

[G.698.1]定义了以下应用代码:DScW ytz(v)和B-DScW-ytz(v)。哪里:

B: means Bidirectional

意思是双向的

D: means a DWDM application

D:表示DWDM应用程序

S: takes values N (narrow spectral excursion) or W (wide spectral excursion)

S:取值N(窄光谱偏移)或W(宽光谱偏移)

c: Channel Spacing (GHz)

c:信道间隔(GHz)

W: takes values S (short-haul) or L (long-haul)

W:取S(短距离)或L(长距离)的值

y: takes values 1 (NRZ 2.5G) or 2 (NRZ 10G)

y:取值1(NRZ 2.5G)或2(NRZ 10G)

t: only D value is defined (link does not contain optical amplifier)

t:仅定义了D值(链路不包含光放大器)

z: takes values 2 ([G.652] fibre), 3 ([G.653] fibre), or 5 ([G.655] fibre)

z:取值2([G.652]光纤)、3([G.653]光纤)或5([G.655]光纤)

v: takes values S (Short wavelength), C (Conventional), or L (Long wavelength)

v:取S(短波)、C(常规)或L(长波)的值

The F flag indicates the presence or absence of an optional FEC encoding suffix.

F标志表示是否存在可选的FEC编码后缀。

These get mapped into the 64-bit Optical Interface Class field as follows:

它们映射到64位光学接口类字段中,如下所示:

      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
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |B|  D  |S|   c   |   W   |   y   |   t   |   z   |  v  |   F   |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                           reserved                            |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        
      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
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |B|  D  |S|   c   |   W   |   y   |   t   |   z   |  v  |   F   |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                           reserved                            |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        

Where (values between parentheses refer to ITU-defined values as reported above):

式中(括号之间的值指上述ITU定义的值):

B: 1 bidirectional, 0 otherwise

B:1,否则为0

D (prefix): 0 reserved, 1 (D)

D(前缀):0保留,1(D)

S: 0 (N), 1 (W)

南:0(北),1(西)

c: Channel Spacing, 4 bits mapped according to the same definition as in the third figure in Section 3.2 of [RFC6205] (note that DWDM spacing applies here).

c:信道间隔,根据[RFC6205]第3.2节第三个图中相同的定义映射的4位(注意,DWDM间隔在此适用)。

W: 0 reserved, 2 (S), 3 (L)

W:0预留、2(S)、3(L)

y: 0 reserved, 1 (1), 2 (2)

y:0保留,1(1),2(2)

t: 0 reserved, 4 (D)

t:0保留,4(D)

z: 0 reserved, 2 (2), 3 (3), 5 (5)

z:0保留,2(2),3(3),5(5)

v: 0 reserved, 1 (S), 2 (C), 3 (L)

v:0保留、1(S)、2(C)、3(L)

F (suffix): 0 No FEC encoding suffix present, 1 FEC encoding suffix present

F(后缀):0不存在FEC编码后缀,1存在FEC编码后缀

Values not mentioned here are not allowed in this application code; the last 32 bits are reserved and shall be set to zero.

本应用程序代码中不允许使用此处未提及的值;最后32位为保留位,应设置为零。

4.1.2. ITU-T G.698.2 Application Code Mapping
4.1.2. ITU-T G.698.2应用程序代码映射

[G.698.2] defines the following application codes: DScW-ytz(v) and B-DScW-ytz(v). Where:

[G.698.2]定义了以下应用代码:DScW ytz(v)和B-DScW-ytz(v)。哪里:

B: means Bidirectional

意思是双向的

D: means a DWDM application

D:表示DWDM应用程序

S: takes values N (narrow spectral excursion) or W (wide spectral excursion)

S:取值N(窄光谱偏移)或W(宽光谱偏移)

c: Channel Spacing (GHz)

c:信道间隔(GHz)

W: takes values C (link is dispersion compensated) or U (link is dispersion uncompensated)

W:取值C(链路色散补偿)或U(链路色散未补偿)

y: takes values 1 (NRZ 2.5G) or 2 (NRZ 10G)

y:取值1(NRZ 2.5G)或2(NRZ 10G)

t: takes value A (link may contains optical amplifier)

t:取值A(链路可能包含光放大器)

z: takes values 2 ([G.652] fibre), 3 ([G.653] fibre), or 5 ([G.655] fibre)

z:取值2([G.652]光纤)、3([G.653]光纤)或5([G.655]光纤)

v: takes values S (Short wavelength), C (Conventional), or L (Long wavelength)

v:取S(短波)、C(常规)或L(长波)的值

An optional F can be added to indicate a FEC encoding.

可以添加可选的F以指示FEC编码。

These get mapped into the 64-bit Optical Interface Class field as follows:

它们映射到64位光学接口类字段中,如下所示:

      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
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |B|  D  |S|   c   |   W   |   y   |   t   |   z   |  v  |   F   |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                           reserved                            |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        
      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
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |B|  D  |S|   c   |   W   |   y   |   t   |   z   |  v  |   F   |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                           reserved                            |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        

Where (values between parentheses refer to ITU-defined values as reported above):

式中(括号之间的值指上述ITU定义的值):

B: 1 bidirectional, 0 otherwise

B:1,否则为0

D (prefix): 0 reserved, 1 (D)

D(前缀):0保留,1(D)

S: 0 (N), 1 (W)

南:0(北),1(西)

c: Channel Spacing, 4 bits mapped according to the same definition as in the third figure in Section 3.2 of [RFC6205] (note that DWDM spacing applies here).

c:信道间隔,根据[RFC6205]第3.2节第三个图中相同的定义映射的4位(注意,DWDM间隔在此适用)。

W: 0 reserved, 10 (C), 11 (U)

W:0保留、10(C)、11(U)

y: 0 reserved, 1 (1), 2 (2)

y:0保留,1(1),2(2)

t: 0 reserved, 1 (A)

t:0保留,1(A)

z: 0 reserved, 2 (2), 3 (3), 5 (5)

z:0保留,2(2),3(3),5(5)

v: 0 reserved, 1 (S), 2 (C), 3 (L)

v:0保留、1(S)、2(C)、3(L)

F (suffix): 0 reserved, 1 FEC encoding

F(后缀):0保留,1 FEC编码

Values not mentioned here are not allowed in this application code. The last 32 bits are reserved and shall be set to zero.

在此应用程序代码中不允许使用此处未提及的值。最后32位为保留位,应设置为零。

4.1.3. ITU-T G.959.1 Application Code Mapping
4.1.3. ITU-T G.959.1应用程序代码映射

[G.959.1] defines the following application codes: PnWx-ytz and BnWx-ytz. Where:

[G.959.1]定义了以下应用代码:PnWx ytz和BnWx ytz。哪里:

P,B: when present, indicate Plural or Bidirectional

P、 B:当出现时,表示复数或双向

n: maximum number of channels supported by the application code (i.e., an integer number)

n:应用程序代码支持的最大通道数(即整数)

W: takes values I (intra-office), S (short-haul), L (long-haul), V (very long-haul), or U (ultra long-haul)

W:取值I(办公室内部)、S(短途)、L(长途)、V(长途)或U(超长途)

x: maximum number of spans allowed within the application code (i.e., an integer number)

x:应用程序代码中允许的最大跨距数(即整数)

y: takes values 1 (NRZ 2.5G), 2 (NRZ 10G), 9 (NRZ 25G), 3 (NRZ 40G), or 7 (RZ 40G)

y:取值1(NRZ 2.5G)、2(NRZ 10G)、9(NRZ 25G)、3(NRZ 40G)或7(RZ 40G)

t: takes values A (power levels suitable for a booster amplifier in the originating ONE and power levels suitable for a pre-amplifier in the terminating ONE), B (booster amplifier only), C (pre-amplifier only), or D (no amplifiers)

t:取值A(适用于起始放大器的功率电平和适用于终止放大器的前置放大器的功率电平)、B(仅适用于前置放大器)、C(仅适用于前置放大器)或D(无放大器)

z: takes values 1 (1310 nm sources on [G.652] fibre), 2 (1550 nm sources on [G.652] fibre), 3 (1550 nm sources on [G.653] fibre), or 5 (1550 nm sources on [G.655] fibre).

z:取值1(1310 nm光源位于[G.652]光纤上)、2(1550 nm光源位于[G.652]光纤上)、3(1550 nm光源位于[G.653]光纤上)或5(1550 nm光源位于[G.655]光纤上)。

The following list of suffixes can be added to these application codes:

以下后缀列表可添加到这些应用程序代码中:

F: FEC encoding

F:FEC编码

D: Adaptive dispersion compensation

D:自适应色散补偿

E: receiver capable of dispersion compensation

E:能够进行色散补偿的接收机

r: reduced target distance

r:缩短目标距离

a: power levels appropriate to APD receivers

a:适用于APD接收器的功率水平

b: power levels appropriate to PIN receivers

b:适用于PIN接收器的功率水平

These values are 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
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      | p |  P  |       n           |   W   |     x     |   reserved  |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |   y   |   t   |   z   |   suffix  |          reserved         |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        
      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
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      | p |  P  |       n           |   W   |     x     |   reserved  |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |   y   |   t   |   z   |   suffix  |          reserved         |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        

Where (values between parentheses refer to ITU-defined values as reported above):

式中(括号之间的值指上述ITU定义的值):

p (prefix): 0 otherwise, 1 Bidirectional (B)

p(前缀):否则为0,1(B)

P (optional): 0 not present, 2 (P).

P(可选):0不存在,2(P)。

n: maximum number of channels (10 bits, up to 1023 channels)

n:最大通道数(10位,最多1023个通道)

W: 0 reserved, 1 (I), 2 (S), 3 (L), 4 (V), 5 (U)

W:0保留、1(I)、2(S)、3(L)、4(V)、5(U)

x: number of spans (6 bits, up to 64 spans)

x:跨距数(6位,最多64个跨距)

y: 0 reserved, 1 (1), 2 (2), 3 (3), 7 (7), 9 (9)

y:0保留,1(1),2(2),3(3),7(7),9(9)

t: 0 reserved, 1 (A), 2 (B), 3 (C), 4 (D)

t:0保留,1(A),2(B),3(C),4(D)

z: 0 reserved, 1 (1), 2 (2), 3 (3), 5 (5)

z:0保留,1(1),2(2),3(3),5(5)

suffix: a 6-bit bitmap, where a "1" in the appropriate slot indicates that the corresponding suffix has been added.

后缀:6位位图,其中相应插槽中的“1”表示已添加相应的后缀。

             0 1 2 3 4 5
            +-+-+-+-+-+-+
            |F|D|E|r|a|b|
            +-+-+-+-+-+-+
        
             0 1 2 3 4 5
            +-+-+-+-+-+-+
            |F|D|E|r|a|b|
            +-+-+-+-+-+-+
        
4.1.4. ITU-T G.695 Application Code Mapping
4.1.4. ITU-T G.695应用程序代码映射

[G.695] defines the following application codes: CnWx-ytz, B-CnWx-ytz, and S-CnWx-ytz.

[G.695]定义了以下应用代码:CnWx ytz、B-CnWx-ytz和S-CnWx-ytz。

Where the optional prefixes are:

其中可选前缀为:

B: Bidirectional

B:双向的

S: a system using a black link approach

S:使用黑链接方法的系统

And the rest of the application code is defined as:

其余的应用程序代码定义为:

C: CWDM (Coarse WDM) application

C:CWDM(粗波分复用)应用

n: maximum number of channels supported by the application code (i.e., an integer number)

n:应用程序代码支持的最大通道数(即整数)

W: takes values S (short-haul) or L (long-haul)

W:取S(短距离)或L(长距离)的值

x: maximum number of spans allowed

x:允许的最大跨距数

y: takes values 0 (NRZ 1.25G), 1 (NRZ 2.5G), or 2 (NRZ 10G).

y:取值为0(NRZ 1.25G)、1(NRZ 2.5G)或2(NRZ 10G)。

t: takes value D (link does not contain any optical amplifier).

t:取值D(链路不包含任何光放大器)。

z: takes values 1 (1310 nm region for [G.652] fibre), 2 (ITU-T [G.652] fibre), 3 ([G.653] fibre), or 5 ([G.655] fibre)

z:取值为1(1310 nm区域用于[G.652]光纤)、2(ITU-T[G.652]光纤)、3(G.653]光纤)或5(G.655]光纤)

The following list of suffixes can be added to these application codes:

以下后缀列表可添加到这些应用程序代码中:

F: FEC encoding

F:FEC编码

Since the application codes are very similar to the ones from the [G.959.1] section, most of the fields are reused. The 64-bit Optical Interface Class field is encoded as follows:

由于应用程序代码与[G.959.1]部分中的代码非常相似,因此大多数字段都被重用。64位光学接口类字段编码如下:

      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
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      | p |  C  |       n           |   W   |     x     |   reserved  |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |   y   |   t   |   z   |   suffix  |          reserved         |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        
      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
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      | p |  C  |       n           |   W   |     x     |   reserved  |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |   y   |   t   |   z   |   suffix  |          reserved         |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        

Where (values between parentheses refer to ITU-defined values as reported above):

式中(括号之间的值指上述ITU定义的值):

p: 0 no prefix, 1 (B) bidirectional, 2 (S) black link

p:0无前缀,1(B)双向,2(S)黑色链接

C: 0 reserved, 3 (C)

C:0保留,3(C)

n: maximum number of channels (10 bits, up to 1023 channels)

n:最大通道数(10位,最多1023个通道)

W: 0 reserved, 1 reserved, 2 (S), 3 (L), > 3 reserved

W:0保留,1保留,2(S),3(L),>3保留

x: number of spans (6 bits, up to 64 spans)

x:跨距数(6位,最多64个跨距)

y: 0 (0), 1 (1), 2 (2), > 2 reserved

y:0(0)、1(1)、2(2),>2保留

t: 4 (D), all other values are reserved

t:4(D),保留所有其他值

z: 0 reserved, 1 (1), 2 (2), 3 (3)

z:0保留,1(1),2(2),3(3)

suffix: a 6-bit bitmap, where a "1" in the appropriate slot indicates that the corresponding suffix has been added.

后缀:6位位图,其中相应插槽中的“1”表示已添加相应的后缀。

             0 1 2 3 4 5
            +-+-+-+-+-+-+
            |F|0|0|0|0|0|
            +-+-+-+-+-+-+
        
             0 1 2 3 4 5
            +-+-+-+-+-+-+
            |F|0|0|0|0|0|
            +-+-+-+-+-+-+
        
4.2. Acceptable Client Signal List Subfield
4.2. 可接受的客户端信号列表子字段

This subfield contains a list of acceptable input client signal types.

此子字段包含可接受的输入客户端信号类型列表。

The acceptable client signal list is a list of Generalized Protocol Identifiers (G-PIDs).

可接受的客户端信号列表是通用协议标识符(G-PID)的列表。

      0                   1                   2                   3
      0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |            Reserved           |       Number of G-PIDs        |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |            G-PID #1           |          G-PID #2             |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     :                               |                               :
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |            G-PID #N           |                               |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        
      0                   1                   2                   3
      0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |            Reserved           |       Number of G-PIDs        |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |            G-PID #1           |          G-PID #2             |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     :                               |                               :
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |            G-PID #N           |                               |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        

Number of G-PIDs: an integer greater than or equal to one.

G-PID数:大于或等于1的整数。

G-PIDs: assigned by IANA. Many are defined in [RFC3471] and [RFC4328].

G-PIDs:由IANA分配。许多在[RFC3471]和[RFC4328]中定义。

4.3. Input Bit Rate List Subfield
4.3. 输入比特率列表子字段

This subfield contains a list of bit rates of each input client signal type specified in the Input Client Signal List.

此子字段包含输入客户机信号列表中指定的每个输入客户机信号类型的比特率列表。

The number of Input Bit Rates MUST match the number of G-PIDs.

输入比特率的数量必须与G-PID的数量相匹配。

      0                   1                   2                   3
      0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |                   Input Bit Rate of G-PID #1                  |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     :                                                               :
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |                   Input Bit Rate of G-PID #N                  |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        
      0                   1                   2                   3
      0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |                   Input Bit Rate of G-PID #1                  |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     :                                                               :
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |                   Input Bit Rate of G-PID #N                  |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        

Input Bit Rates are in IEEE 754 floating point format [IEEE].

输入比特率采用IEEE 754浮点格式[IEEE]。

4.4. Processing Capability List Subfield
4.4. 处理能力列表子字段

The Processing Capability List subfield is a list of capabilities that can be achieved through the referred resources:

处理能力列表子字段是可通过参考资源实现的能力列表:

1. Regeneration capability

1. 再生能力

2. Fault and performance monitoring

2. 故障和性能监视

3. Vendor-specific capability

3. 供应商特定能力

Fault and performance monitoring and vendor-specific capability have no additional capability parameters.

故障和性能监控以及特定于供应商的能力没有额外的能力参数。

The Processing Capability List subfield is defined as:

处理能力列表子字段定义为:

      0                   1                   2                   3
      0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |            Reserved           |        Processing Cap ID      |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |   Possible additional capability parameters depending upon    |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     :   the processing ID                                           :
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        
      0                   1                   2                   3
      0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |            Reserved           |        Processing Cap ID      |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     |   Possible additional capability parameters depending upon    |
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
     :   the processing ID                                           :
     +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        

The Processing Cap ID field defines the following processing capabilities:

处理Cap ID字段定义了以下处理能力:

0: Reserved

0:保留

1: Regeneration capability

1:再生能力

2: Fault and performance monitoring

2:故障和性能监控

3: Vendor-specific capability

3:供应商特定能力

When the Processing Cap ID is "Regeneration capability", the following additional capability parameters are provided in the following field:

当处理Cap ID为“再生能力”时,以下字段中提供了以下附加能力参数:

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

Where the T bit indicates the type of regenerator:

其中T位表示再生器的类型:

T=0: Reserved

T=0:保留

T=1: 1R Regenerator

T=1:1R再生器

T=2: 2R Regenerator

T=2:2R再生器

T=3: 3R Regenerator

T=3:3R再生器

And where the C bit indicates the capability of the regenerator:

其中,C位表示再生器的能力:

C=0: Reserved

C=0:保留

C=1: Fixed Regeneration Point

C=1:固定再生点

C=2: Selective Regeneration Pools

C=2:选择性再生池

Note that when the capability of the regenerator is indicated to be "Selective Regeneration Pools", regeneration pool properties such as input and output restrictions and availability need to be specified. These properties will be encoded in the field providing additional capability parameters, starting with the bits marked Reserved in the figure immediately above. An additional specification describing the encoding of these parameters is required before the value C=2 can be used.

注意,当再生器的能力被指示为“选择性再生池”时,需要指定再生池属性,如输入和输出限制以及可用性。这些属性将在提供额外功能参数的字段中编码,从上图中标记为保留的位开始。在使用值C=2之前,需要一个描述这些参数编码的附加规范。

5. Security Considerations
5. 安全考虑

This document defines protocol-independent encodings for WSON information and does not introduce any security issues.

本文档为WSON信息定义了与协议无关的编码,并且没有引入任何安全问题。

However, other documents that make use of these encodings within protocol extensions need to consider the issues and risks associated with inspection, interception, modification, or spoofing of any of this information. It is expected that any such documents will describe the necessary security measures to provide adequate protection. A general discussion on security in GMPLS networks can be found in [RFC5920].

然而,在协议扩展中使用这些编码的其他文档需要考虑与这些信息的任何检查、拦截、修改或欺骗相关联的问题和风险。预计任何此类文件都将说明提供充分保护的必要安全措施。关于GMPLS网络安全性的一般性讨论见[RFC5920]。

6. IANA Considerations
6. IANA考虑

This document introduces a new top-level registry for GMPLS routing parameters for WSON encoding. This new IANA registry has been created to make the assignment of a new type and new values for the new "GMPLS Routing Parameters for WSON" registry. Note that this registry is only used in routing, not in signaling.

本文档为WSON编码的GMPLS路由参数引入了一个新的顶级注册表。创建此新IANA注册表是为了为新的“WSON GMPLS路由参数”注册表分配新类型和新值。请注意,此注册表仅用于路由,而不用于信令。

6.1. Types for Subfields of WSON Resource Block Information
6.1. WSON资源块信息子字段的类型

Under the new "GMPLS Routing Parameters for WSON" registry, a new IANA subregistry has been created for nested subfields of the Resource Block Information field to create a new section named "Types for Subfields of WSON Resource Block Information Registry". This registry will be maintained via Standards Action as defined by [RFC5226].

在新的“WSON GMPLS路由参数”注册表下,已为资源块信息字段的嵌套子字段创建了一个新的IANA子区域,以创建一个名为“WSON资源块信息注册表子字段类型”的新部分。该注册表将通过[RFC5226]定义的标准行动进行维护。

The initial values in the registry are as follows:

注册表中的初始值如下所示:

   Value      Length      Description                     Reference
   -----      ------      ------------                    ---------
   0                      Reserved
   1          variable    Optical Interface Class List    [RFC7581]
   2          variable    Acceptable Client Signal List   [RFC7581]
   3          variable    Input Bit Rate List             [RFC7581]
   4          variable    Processing Capability List      [RFC7581]
   5-65535                Unassigned
        
   Value      Length      Description                     Reference
   -----      ------      ------------                    ---------
   0                      Reserved
   1          variable    Optical Interface Class List    [RFC7581]
   2          variable    Acceptable Client Signal List   [RFC7581]
   3          variable    Input Bit Rate List             [RFC7581]
   4          variable    Processing Capability List      [RFC7581]
   5-65535                Unassigned
        
7. References
7. 工具书类
7.1. Normative References
7.1. 规范性引用文件

[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997, <http://www.rfc-editor.org/info/rfc2119>.

[RFC2119]Bradner,S.,“RFC中用于表示需求水平的关键词”,BCP 14,RFC 2119,DOI 10.17487/RFC2119,1997年3月<http://www.rfc-editor.org/info/rfc2119>.

[RFC4328] Papadimitriou, D., Ed., "Generalized Multi-Protocol Label Switching (GMPLS) Signaling Extensions for G.709 Optical Transport Networks Control", RFC 4328, DOI 10.17487/RFC4328, January 2006, <http://www.rfc-editor.org/info/rfc4328>.

[RFC4328]Papadimitriou,D.,编辑,“G.709光传输网络控制的通用多协议标签交换(GMPLS)信令扩展”,RFC 4328,DOI 10.17487/RFC4328,2006年1月<http://www.rfc-editor.org/info/rfc4328>.

[RFC6205] Otani, T., Ed., and D. Li, Ed., "Generalized Labels for Lambda-Switch-Capable (LSC) Label Switching Routers", RFC 6205, DOI 10.17487/RFC6205, March 2011, <http://www.rfc-editor.org/info/rfc6205>.

[RFC6205]Otani,T.,Ed.,和D.Li,Ed.,“Lambda交换机功能(LSC)标签交换路由器的通用标签”,RFC 6205,DOI 10.17487/RFC6205,2011年3月<http://www.rfc-editor.org/info/rfc6205>.

[RFC7446] Lee, Y., Ed., Bernstein, G., Ed., Li, D., and W. Imajuku, "Routing and Wavelength Assignment Information Model for Wavelength Switched Optical Networks", RFC 7446, DOI 10.17487/RFC7446, February 2015, <http://www.rfc-editor.org/info/rfc7446>.

[RFC7446]Lee,Y.,Ed.,Bernstein,G.,Ed.,Li,D.,和W.Imajuku,“波长交换光网络的路由和波长分配信息模型”,RFC 7446,DOI 10.17487/RFC7446,2015年2月<http://www.rfc-editor.org/info/rfc7446>.

[RFC7579] Bernstein, G., Ed., Lee, Y., Ed., Li, D., Imajuku, W., and J. Han, "General Network Element Constraint Encoding for GMPLS-Controlled Networks", RFC 7579, DOI 10.17487/RFC7579, June 2015, <http://www.rfc-editor.org/info/rfc7579>.

[RFC7579]Bernstein,G.,Ed.,Lee,Y.,Ed.,Li,D.,Imajuku,W.,和J.Han,“GMPLS控制网络的一般网元约束编码”,RFC 7579,DOI 10.17487/RFC7579,2015年6月<http://www.rfc-editor.org/info/rfc7579>.

7.2. Informative References
7.2. 资料性引用

[G.652] ITU-T, "Characteristics of a single-mode optical fibre and cable", ITU-T Recommendation G.652, November 2009.

[G.652]ITU-T,“单模光纤和光缆的特性”,ITU-T建议G.652,2009年11月。

[G.653] ITU-T, "Characteristics of a dispersion-shifted, single-mode optical fibre and cable", ITU-T Recommendation G.653, July 2010.

[G.653]ITU-T,“色散位移单模光纤和光缆的特性”,ITU-T建议G.653,2010年7月。

[G.655] ITU-T, "Characteristics of a non-zero dispersion-shifted single-mode optical fibre and cable", ITU-T Recommendation G.655, November 2009.

[G.655]ITU-T,“非零色散位移单模光纤和光缆的特性”,ITU-T建议G.655,2009年11月。

[G.695] ITU-T, "Optical interfaces for coarse wavelength division multiplexing applications", ITU-T Recommendation G.695, January 2015.

[G.695]ITU-T,“粗波分复用应用的光接口”,ITU-T建议G.695,2015年1月。

[G.698.1] ITU-T, "Multichannel DWDM applications with single-channel optical interfaces", ITU-T Recommendation G.698.1, November 2009.

[G.698.1]ITU-T,“具有单通道光学接口的多通道DWDM应用”,ITU-T建议G.698.1,2009年11月。

[G.698.2] ITU-T, "Amplified multichannel dense wavelength division multiplexing applications with single channel optical interfaces", ITU-T Recommendation G.698.2, November 2009.

[G.698.2]ITU-T,“具有单通道光学接口的放大多通道密集波分复用应用”,ITU-T建议G.698.2,2009年11月。

[G.959.1] ITU-T, "Optical transport network physical layer interfaces", ITU-T Recommendation G.959.1, February 2012.

[G.959.1]ITU-T,“光传输网络物理层接口”,ITU-T建议G.959.1,2012年2月。

[IEEE] IEEE, "IEEE Standard for Binary Floating-Point Arithmetic", IEEE Standard 754.

[IEEE]IEEE,“二进制浮点运算的IEEE标准”,IEEE标准754。

[RFC3471] Berger, L., Ed., "Generalized Multi-Protocol Label Switching (GMPLS) Signaling Functional Description", RFC 3471, DOI 10.17487/RFC3471, January 2003, <http://www.rfc-editor.org/info/rfc3471>.

[RFC3471]Berger,L.,Ed.“通用多协议标签交换(GMPLS)信令功能描述”,RFC 3471,DOI 10.17487/RFC3471,2003年1月<http://www.rfc-editor.org/info/rfc3471>.

[RFC4203] Kompella, K., Ed., and Y. Rekhter, Ed., "OSPF Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)", RFC 4203, DOI 10.17487/RFC4203, October 2005, <http://www.rfc-editor.org/info/rfc4203>.

[RFC4203]Kompella,K.,Ed.,和Y.Rekhter,Ed.,“支持通用多协议标签交换(GMPLS)的OSPF扩展”,RFC 4203,DOI 10.17487/RFC4203,2005年10月<http://www.rfc-editor.org/info/rfc4203>.

[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 5226, DOI 10.17487/RFC5226, May 2008, <http://www.rfc-editor.org/info/rfc5226>.

[RFC5226]Narten,T.和H.Alvestrand,“在RFCs中编写IANA注意事项部分的指南”,BCP 26,RFC 5226,DOI 10.17487/RFC5226,2008年5月<http://www.rfc-editor.org/info/rfc5226>.

[RFC5307] Kompella, K., Ed., and Y. Rekhter, Ed., "IS-IS Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)", RFC 5307, DOI 10.17487/RFC5307, October 2008, <http://www.rfc-editor.org/info/rfc5307>.

[RFC5307]Kompella,K.,Ed.,和Y.Rekhter,Ed.,“支持通用多协议标签交换(GMPLS)的IS-IS扩展”,RFC 5307,DOI 10.17487/RFC5307,2008年10月<http://www.rfc-editor.org/info/rfc5307>.

[RFC5440] Vasseur, JP., Ed., and JL. Le Roux, Ed., "Path Computation Element (PCE) Communication Protocol (PCEP)", RFC 5440, DOI 10.17487/RFC5440, March 2009, <http://www.rfc-editor.org/info/rfc5440>.

[RFC5440]Vasseur,JP.,Ed.,和JL。Le Roux主编,“路径计算元件(PCE)通信协议(PCEP)”,RFC 5440,DOI 10.17487/RFC5440,2009年3月<http://www.rfc-editor.org/info/rfc5440>.

[RFC5511] Farrel, A., "Routing Backus-Naur Form (RBNF): A Syntax Used to Form Encoding Rules in Various Routing Protocol Specifications", RFC 5511, DOI 10.17487/RFC5511, April 2009, <http://www.rfc-editor.org/info/rfc5511>.

[RFC5511]Farrel,A.,“路由Backus-Naur形式(RBNF):用于在各种路由协议规范中形成编码规则的语法”,RFC 5511,DOI 10.17487/RFC5511,2009年4月<http://www.rfc-editor.org/info/rfc5511>.

[RFC5920] Fang, L., Ed., "Security Framework for MPLS and GMPLS Networks", RFC 5920, DOI 10.17487/RFC5920, July 2010, <http://www.rfc-editor.org/info/rfc5920>.

[RFC5920]方,L.,编辑,“MPLS和GMPLS网络的安全框架”,RFC 5920,DOI 10.17487/RFC5920,2010年7月<http://www.rfc-editor.org/info/rfc5920>.

[RFC6163] Lee, Y., Ed., Bernstein, G., Ed., and W. Imajuku, "Framework for GMPLS and Path Computation Element (PCE) Control of Wavelength Switched Optical Networks (WSONs)", RFC 6163, DOI 10.17487/RFC6163, April 2011, <http://www.rfc-editor.org/info/rfc6163>.

[RFC6163]Lee,Y.,Ed.,Bernstein,G.,Ed.,和W.Imajuku,“波长交换光网络(WSON)的GMPLS和路径计算元件(PCE)控制框架”,RFC 6163,DOI 10.17487/RFC6163,2011年4月<http://www.rfc-editor.org/info/rfc6163>.

Appendix A. Encoding Examples
附录A.编码示例
A.1. Wavelength Converter Accessibility Field
A.1. 波长转换器可访问性字段

Figure 1 shows a wavelength converter pool architecture known as "shared per fiber". In this case, the input and output pool matrices are simply:

图1显示了一种称为“每光纤共享”的波长转换器池体系结构。在这种情况下,输入和输出池矩阵仅为:

              +-----+       +-----+
              | 1 1 |       | 1 0 |
          WI =|     |,  WE =|     |
              | 1 1 |       | 0 1 |
              +-----+       +-----+
        
              +-----+       +-----+
              | 1 1 |       | 1 0 |
          WI =|     |,  WE =|     |
              | 1 1 |       | 0 1 |
              +-----+       +-----+
        
                    +-----------+                      +------+
                    |           |--------------------->|      |
                    |           |--------------------->|  C   |
              /|    |           |--------------------->|  o   |
             /D+--->|           |--------------------->|  m   |
            + e+--->|           |                      |  b   |=======>
   ========>| M|    |  Optical  |    +-----------+     |  i   | Port O1
   Port I1  + u+--->|  Switch   |    |  WC Pool  |     |  n   |
             \x+--->|           |    |  +-----+  |     |  e   |
              \|    |           +----+->|WC #1|--+---->|  r   |
                    |           |    |  +-----+  |     +------+
                    |           |    |           |     +------+
              /|    |           |    |  +-----+  |     |      |
             /D+--->|           +----+->|WC #2|--+---->|  C   |
            + e+--->|           |    |  +-----+  |     |  o   |
   ========>| M|    |           |    +-----------+     |  m   |=======>
   Port I2  + u+--->|           |                      |  b   | Port O2
             \x+--->|           |--------------------->|  i   |
              \|    |           |--------------------->|  n   |
                    |           |--------------------->|  e   |
                    |           |--------------------->|  r   |
                    +-----------+                      +------+
        
                    +-----------+                      +------+
                    |           |--------------------->|      |
                    |           |--------------------->|  C   |
              /|    |           |--------------------->|  o   |
             /D+--->|           |--------------------->|  m   |
            + e+--->|           |                      |  b   |=======>
   ========>| M|    |  Optical  |    +-----------+     |  i   | Port O1
   Port I1  + u+--->|  Switch   |    |  WC Pool  |     |  n   |
             \x+--->|           |    |  +-----+  |     |  e   |
              \|    |           +----+->|WC #1|--+---->|  r   |
                    |           |    |  +-----+  |     +------+
                    |           |    |           |     +------+
              /|    |           |    |  +-----+  |     |      |
             /D+--->|           +----+->|WC #2|--+---->|  C   |
            + e+--->|           |    |  +-----+  |     |  o   |
   ========>| M|    |           |    +-----------+     |  m   |=======>
   Port I2  + u+--->|           |                      |  b   | Port O2
             \x+--->|           |--------------------->|  i   |
              \|    |           |--------------------->|  n   |
                    |           |--------------------->|  e   |
                    |           |--------------------->|  r   |
                    +-----------+                      +------+
        

Figure 1: An Optical Switch Featuring a Shared Per-Fiber Wavelength Converter Pool Architecture

图1:具有共享每光纤波长转换器池体系结构的光交换机

The wavelength converters are resource blocks and the wavelength converter pool is a resource block pool. This 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
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |    Reserved |1|                    Reserved                   |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                  Note: I1,I2 can connect to either WC1 or WC2
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |  Action=0     |0|  Reserved   |            Length = 12        |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                     Link Local Identifier = #1                |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                     Link Local Identifier = #2                |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |  Action=0     |1|  Reserved   |            Length = 8         |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                           RB ID = #1                          |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                           RB ID = #2                          |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                        Note: WC1 can only connect to O1
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |  Action=0     |1|  Reserved   |            Length = 8         |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                     Link Local Identifier = #1                |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |  Action=0     |0|  Reserved   |            Length = 8         |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                            RB ID = #1                         |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                        Note: WC2 can only connect to O2
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |  Action=0     |1|  Reserved   |            Length = 8         |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                     Link Local Identifier = #2                |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |  Action=0     |0|                |            Length = 8      |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                            RB ID = #2                         |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        
       0                   1                   2                   3
       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |    Reserved |1|                    Reserved                   |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                  Note: I1,I2 can connect to either WC1 or WC2
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |  Action=0     |0|  Reserved   |            Length = 12        |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                     Link Local Identifier = #1                |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                     Link Local Identifier = #2                |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |  Action=0     |1|  Reserved   |            Length = 8         |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                           RB ID = #1                          |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                           RB ID = #2                          |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                        Note: WC1 can only connect to O1
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |  Action=0     |1|  Reserved   |            Length = 8         |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                     Link Local Identifier = #1                |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |  Action=0     |0|  Reserved   |            Length = 8         |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                            RB ID = #1                         |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                        Note: WC2 can only connect to O2
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |  Action=0     |1|  Reserved   |            Length = 8         |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                     Link Local Identifier = #2                |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |  Action=0     |0|                |            Length = 8      |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                            RB ID = #2                         |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        
A.2. Wavelength Conversion Range Field
A.2. 波长转换范围场

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}:

此示例基于图1,显示了如何表示波长转换器的波长转换范围。假设WC1和WC2的输入和输出波长范围为{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 = 8                |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |           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   |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        
       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 = 8                |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |           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
A.3. 一种具有DWDM光学器件的OEO开关

Figure 2 shows an electronic switch fabric surrounded by DWDM optics. In this example, the electronic fabric can handle either G.709 or Synchronous Digital Hierarchy (SDH) signals only (2.5 or 10 Gbps). To describe this node, the following information in Reduced Backus-Naur Form (RBNF) form [RFC5511] is needed:

图2显示了由DWDM光学元件包围的电子交换机结构。在此示例中,电子结构只能处理G.709或同步数字体系(SDH)信号(2.5或10 Gbps)。为了描述该节点,需要简化巴科斯诺尔表(RBNF)表[RFC5511]中的以下信息:

      <Node_Info> ::= <Node_ID>
        
      <Node_Info> ::= <Node_ID>
        

[Other GMPLS info-elements]

[其他GMPLS信息元素]

[<ConnectivityMatrix>...]

[<ConnectivityMatrix>…]

[<ResourcePool>]

[<ResourcePool>]

[<RBPoolState>]

[<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, the <RBPoolState> element is not needed.

在这种情况下,存在完整的端口到端口连接,因此不需要<ConnectivityMatrix>。此外,由于有足够的端口处理所有波长信号,因此不需要<RBPoolState>元素。

Hence, the attention will be focused on the <ResourcePool> field:

因此,注意力将集中在<ResourcePool>字段上:

      <ResourcePool> ::= <ResourceBlockInfo>
        
      <ResourcePool> ::= <ResourceBlockInfo>
        

[<RBAccessibility>...]

[<RBAccessibility>…]

[<ResourceWaveConstraints>...]

[<ResourceWaveConstraints>…]

              /|    +-----------+    +-------------+   +------+
             /D+--->|           +--->|Tunable Laser|-->|      |
            + e+--->|           |    +-------------+   |  C   |
   ========>| M|    |           |        ...           |  o   |=======>
   Port I1  + u+--->|           |    +-------------+   |  m   | Port O1
             \x+--->|           |--->|Tunable Laser|-->|  b   |
              \|    |  Electric |    +-------------+   +------+
                    |   Switch  |
              /|    |           |    +-------------+   +------+
             /D+--->|           +--->|Tunable Laser|-->|      |
            + e+--->|           |    +-------------+   |  C   |
   ========>| M|    |           |        ...           |  o   |=======>
   Port I2  + u+--->|           |    +-------------+   |  m   | Port O2
             \x+--->|           +--->|Tunable Laser|-->|  b   |
              \|    |           |    +-------------+   +------+
                    |           |
              /|    |           |    +-------------+   +------+
             /D+--->|           |--->|Tunable Laser|-->|      |
            + e+--->|           |    +-------------+   |  C   |
   ========>| M|    |           |        ...           |  o   |=======>
   Port I3  + u+--->|           |    +-------------+   |  m   | Port O3
             \x+--->|           |--->|Tunable Laser|-->|  b   |
              \|    +-----------+    +-------------+   +------+
        
              /|    +-----------+    +-------------+   +------+
             /D+--->|           +--->|Tunable Laser|-->|      |
            + e+--->|           |    +-------------+   |  C   |
   ========>| M|    |           |        ...           |  o   |=======>
   Port I1  + u+--->|           |    +-------------+   |  m   | Port O1
             \x+--->|           |--->|Tunable Laser|-->|  b   |
              \|    |  Electric |    +-------------+   +------+
                    |   Switch  |
              /|    |           |    +-------------+   +------+
             /D+--->|           +--->|Tunable Laser|-->|      |
            + e+--->|           |    +-------------+   |  C   |
   ========>| M|    |           |        ...           |  o   |=======>
   Port I2  + u+--->|           |    +-------------+   |  m   | Port O2
             \x+--->|           +--->|Tunable Laser|-->|  b   |
              \|    |           |    +-------------+   +------+
                    |           |
              /|    |           |    +-------------+   +------+
             /D+--->|           |--->|Tunable Laser|-->|      |
            + e+--->|           |    +-------------+   |  C   |
   ========>| M|    |           |        ...           |  o   |=======>
   Port I3  + u+--->|           |    +-------------+   |  m   | Port O3
             \x+--->|           |--->|Tunable Laser|-->|  b   |
              \|    +-----------+    +-------------+   +------+
        

Figure 2: An Optical Switch Built around an Electronic Switching Fabric

图2:围绕电子交换结构构建的光开关

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, tells us that all signals must traverse the electronic fabric (fixed connectivity). The resource wavelength constraints are not needed since there are no special wavelength constraints for the resources that would not appear as port/wavelength constraints.

资源块信息将告诉我们接收机、发射机和电子开关的处理约束。资源可用性信息虽然非常简单,但告诉我们所有信号都必须穿过电子结构(固定连接)。不需要资源波长约束,因为对于不会显示为端口/波长约束的资源,没有特殊的波长约束。

The <ResourceBlockInfo> is encoded as follows:

<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
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                     RB Set Field                              |
      :  (only one resource block in this example with shared         |
      |                     input/output case)                        |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |1|1|0|                 Reserved                                |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                 Optical Interface Class List(s)               |
      :                                                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                    Input Client Signal Type                   |
      :                   (G-PIDs for SDH and G.709)                  :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                    Input Bit Rate Range List                  |
      :                      (2.5 Gbps, 10 Gbps)                      :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                   Processing Capabilities List                |
      :              Fixed (non optional) 3R regeneration             :
      :                                                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        
       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)                        |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |1|1|0|                 Reserved                                |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                 Optical Interface Class List(s)               |
      :                                                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                    Input Client Signal Type                   |
      :                   (G-PIDs for SDH and G.709)                  :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                    Input Bit Rate Range List                  |
      :                      (2.5 Gbps, 10 Gbps)                      :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                   Processing Capabilities List                |
      :              Fixed (non optional) 3R regeneration             :
      :                                                               :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        

Since there is fixed connectivity to resource blocks (the electronic switch), the <RBAccessibility> is:

由于与资源块(电子交换机)的连接是固定的,<RBAccessibility>是:

       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=0|Reserved                                       |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                    Input Link Set Field A #1                  |
      :                    (All input links connect to resource)      :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                          RB Set Field A #1                    |
      :              (trivial set only one resource block)            :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                Output Link Set Field B #1                     |
      :                    (All output links connect to resource)     :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        
       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=0|Reserved                                       |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                    Input Link Set Field A #1                  |
      :                    (All input links connect to resource)      :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                          RB Set Field A #1                    |
      :              (trivial set only one resource block)            :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                Output Link Set Field B #1                     |
      :                    (All output links connect to resource)     :
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
        

Contributors

贡献者

Diego Caviglia Ericsson Via A. Negrone 1/A 16153 Genoa Italy Phone: +39 010 600 3736 EMail: diego.caviglia@ericsson.com

Diego Caviglia Ericsson通过A.Negrone 1/A 16153意大利热那亚电话:+39 010 600 3736电子邮件:Diego。caviglia@ericsson.com

Anders Gavler Acreo AB Electrum 236 SE - 164 40 Kista Sweden EMail: Anders.Gavler@acreo.se

Anders Gavler Acreo AB Electrum 236 SE-164 40 Kista瑞典电子邮件:Anders。Gavler@acreo.se

Jonas Martensson Acreo AB Electrum 236 SE - 164 40 Kista Sweden EMail: Jonas.Martensson@acreo.se

Jonas Martenson Acreo AB Electrum 236 SE-164 40 Kista瑞典电子邮件: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

Itaru Nishioka NEC Corp.1753 Simonumabe Nakahara ku,神奈川川崎211-8666日本电话:+81 44 396 3287电子邮件:i-nishioka@cb.jp.nec.com

Pierre Peloso ALU EMail: pierre.peloso@alcatel-lucent.com

Pierre Peloso ALU电子邮件:Pierre。peloso@alcatel-朗讯网

Cyril Margaria EMail: cyril.margaria@gmail.com

西里尔·玛格丽亚电子邮件:西里尔。margaria@gmail.com

Giovanni Martinelli Cisco EMail: giomarti@cisco.com

Giovanni Martinelli Cisco电子邮件:giomarti@cisco.com

Gabriele M Galimberti Cisco EMail: ggalimbe@cisco.com

Gabriele M Galimberti Cisco电子邮件:ggalimbe@cisco.com

Lyndon Ong Ciena Corporation EMail: lyong@ciena.com

Lyndon Ong Ciena公司电子邮件:lyong@ciena.com

Daniele Ceccarelli Ericsson EMail: daniele.ceccarelli@ericsson.com

Daniele Ceccarelli Ericsson电子邮件:Daniele。ceccarelli@ericsson.com

Authors' Addresses

作者地址

Greg M. Bernstein (editor) Grotto Networking Fremont, California United States Phone: (510) 573-2237 EMail: gregb@grotto-networking.com

Greg M.Bernstein(编辑)Grotto Networking美国加利福尼亚州弗里蒙特电话:(510)573-2237电子邮件:gregb@grotto-网络

Young Lee (editor) Huawei Technologies 5340 Legacy Drive Build 3 Plano, TX 75024 United States Phone: (469) 277-5838 EMail: leeyoung@huawei.com

Young Lee(编辑)华为技术5340 Legacy Drive Build 3 Plano,TX 75024美国电话:(469)277-5838电子邮件:leeyoung@huawei.com

Dan Li Huawei Technologies Co., Ltd. F3-5-B R&D Center, Huawei Base, Bantian, Longgang District Shenzhen 518129 China Phone: +86-755-28973237 EMail: danli@huawei.com

丹丽华为技术有限公司深圳市龙岗区坂田华为基地F3-5-B研发中心518129中国电话:+86-755-28973237电子邮件: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

Wataru Imajuku NTT网络创新实验室1-1 Hikari no oka,神奈川日本电话:+81-(46)859-4315电子邮件: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 China Phone: +86-755-28972916 EMail: hanjianrui@huawei.com

韩建瑞华为技术有限公司深圳市龙岗区坂田华为基地F3-5-B研发中心518129中国电话:+86-755-28972916电子邮件:hanjianrui@huawei.com