| 1 |
<pre>Internet Engineering Task Force (IETF) F. Zhang, Ed. |
| 2 |
Request for Comments: 7139 Huawei |
| 3 |
Updates: <a href="./rfc4328">4328</a> G. Zhang |
| 4 |
Category: Standards Track CATR |
| 5 |
ISSN: 2070-1721 S. Belotti |
| 6 |
Alcatel-Lucent |
| 7 |
D. Ceccarelli |
| 8 |
Ericsson |
| 9 |
K. Pithewan |
| 10 |
Infinera |
| 11 |
March 2014 |
| 12 |
|
| 13 |
|
| 14 |
<span class="h1">GMPLS Signaling Extensions</span> |
| 15 |
<span class="h1">for Control of Evolving G.709 Optical Transport Networks</span> |
| 16 |
|
| 17 |
Abstract |
| 18 |
|
| 19 |
ITU-T Recommendation G.709 [<a href="#ref-G709-2012" title=""Interfaces for the Optical Transport Network (OTN)"">G709-2012</a>] introduced new Optical channel |
| 20 |
Data Unit (ODU) containers (ODU0, ODU4, ODU2e, and ODUflex) and |
| 21 |
enhanced Optical Transport Network (OTN) flexibility. |
| 22 |
|
| 23 |
This document updates the ODU-related portions of <a href="./rfc4328">RFC 4328</a> to provide |
| 24 |
extensions to GMPLS signaling to control the full set of OTN |
| 25 |
features, including ODU0, ODU4, ODU2e, and ODUflex. |
| 26 |
|
| 27 |
Status of This Memo |
| 28 |
|
| 29 |
This is an Internet Standards Track document. |
| 30 |
|
| 31 |
This document is a product of the Internet Engineering Task Force |
| 32 |
(IETF). It represents the consensus of the IETF community. It has |
| 33 |
received public review and has been approved for publication by the |
| 34 |
Internet Engineering Steering Group (IESG). Further information on |
| 35 |
Internet Standards is available in <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>. |
| 36 |
|
| 37 |
Information about the current status of this document, any errata, |
| 38 |
and how to provide feedback on it may be obtained at |
| 39 |
<a href="http://www.rfc-editor.org/info/rfc7139">http://www.rfc-editor.org/info/rfc7139</a>. |
| 40 |
|
| 41 |
|
| 42 |
|
| 43 |
|
| 44 |
|
| 45 |
|
| 46 |
|
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Zhang, et al. Standards Track [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc7139">RFC 7139</a> GMPLS Extensions for G.709 March 2014</span> |
| 55 |
|
| 56 |
|
| 57 |
Copyright Notice |
| 58 |
|
| 59 |
Copyright (c) 2014 IETF Trust and the persons identified as the |
| 60 |
document authors. All rights reserved. |
| 61 |
|
| 62 |
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal |
| 63 |
Provisions Relating to IETF Documents |
| 64 |
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of |
| 65 |
publication of this document. Please review these documents |
| 66 |
carefully, as they describe your rights and restrictions with respect |
| 67 |
to this document. Code Components extracted from this document must |
| 68 |
include Simplified BSD License text as described in Section 4.e of |
| 69 |
the Trust Legal Provisions and are provided without warranty as |
| 70 |
described in the Simplified BSD License. |
| 71 |
|
| 72 |
Table of Contents |
| 73 |
|
| 74 |
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-3">3</a> |
| 75 |
<a href="#section-2">2</a>. Terminology .....................................................<a href="#page-3">3</a> |
| 76 |
<a href="#section-3">3</a>. GMPLS Extensions for the Evolving G.709 -- Overview .............<a href="#page-3">3</a> |
| 77 |
<a href="#section-4">4</a>. Generalized Label Request .......................................<a href="#page-4">4</a> |
| 78 |
<a href="#section-5">5</a>. Extensions for Traffic Parameters for Evolving G.709 OTNs .......<a href="#page-7">7</a> |
| 79 |
<a href="#section-5.1">5.1</a>. Usage of ODUflex(CBR) Traffic Parameters ...................<a href="#page-8">8</a> |
| 80 |
<a href="#section-5.2">5.2</a>. Usage of ODUflex(GFP) Traffic Parameters ..................<a href="#page-10">10</a> |
| 81 |
<a href="#section-5.3">5.3</a>. Notification on Errors of OTN-TDM Traffic Parameters ......<a href="#page-11">11</a> |
| 82 |
<a href="#section-6">6</a>. Generalized Label ..............................................<a href="#page-12">12</a> |
| 83 |
<a href="#section-6.1">6.1</a>. OTN-TDM Switching Type Generalized Label ..................<a href="#page-12">12</a> |
| 84 |
<a href="#section-6.2">6.2</a>. Procedures ................................................<a href="#page-14">14</a> |
| 85 |
<a href="#section-6.2.1">6.2.1</a>. Notification on Label Error ........................<a href="#page-16">16</a> |
| 86 |
<a href="#section-6.3">6.3</a>. Supporting Virtual Concatenation and Multiplication .......<a href="#page-17">17</a> |
| 87 |
<a href="#section-6.4">6.4</a>. Examples ..................................................<a href="#page-17">17</a> |
| 88 |
<a href="#section-7">7</a>. Supporting Hitless Adjustment of ODUflex(GFP) ..................<a href="#page-19">19</a> |
| 89 |
8. Operations, Administration, and Maintenance (OAM) |
| 90 |
Considerations .................................................<a href="#page-20">20</a> |
| 91 |
<a href="#section-9">9</a>. Control-Plane Backward-Compatibility Considerations ............<a href="#page-20">20</a> |
| 92 |
<a href="#section-10">10</a>. Security Considerations .......................................<a href="#page-21">21</a> |
| 93 |
<a href="#section-11">11</a>. IANA Considerations ...........................................<a href="#page-21">21</a> |
| 94 |
<a href="#section-12">12</a>. References ....................................................<a href="#page-23">23</a> |
| 95 |
<a href="#section-12.1">12.1</a>. Normative References .....................................<a href="#page-23">23</a> |
| 96 |
<a href="#section-12.2">12.2</a>. Informative References ...................................<a href="#page-24">24</a> |
| 97 |
<a href="#section-13">13</a>. Contributors ..................................................<a href="#page-25">25</a> |
| 98 |
<a href="#section-14">14</a>. Acknowledgments ...............................................<a href="#page-26">26</a> |
| 99 |
|
| 100 |
|
| 101 |
|
| 102 |
|
| 103 |
|
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Zhang, et al. Standards Track [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc7139">RFC 7139</a> GMPLS Extensions for G.709 March 2014</span> |
| 111 |
|
| 112 |
|
| 113 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 114 |
|
| 115 |
With the evolution and deployment of Optical Transport Network (OTN) |
| 116 |
technology, it is necessary that appropriate enhanced control |
| 117 |
technology support be provided for [<a href="#ref-G709-2012" title=""Interfaces for the Optical Transport Network (OTN)"">G709-2012</a>]. |
| 118 |
|
| 119 |
[<a id="ref-RFC7062">RFC7062</a>] provides a framework to allow the development of protocol |
| 120 |
extensions to support GMPLS and Path Computation Element (PCE) |
| 121 |
control of OTN as specified in [<a href="#ref-G709-2012" title=""Interfaces for the Optical Transport Network (OTN)"">G709-2012</a>]. Based on this framework, |
| 122 |
[<a href="./rfc7096" title=""Evaluation of Existing GMPLS Encoding against G.709v3 Optical Transport Networks (OTNs)"">RFC7096</a>] evaluates the information needed by the routing and |
| 123 |
signaling process in OTNs to support GMPLS control of OTN. |
| 124 |
|
| 125 |
[<a id="ref-RFC4328">RFC4328</a>] describes the control technology details that are specific |
| 126 |
to the 2001 revision of the G.709 specification. This document |
| 127 |
updates the ODU-related portions of [<a href="./rfc4328" title=""Generalized Multi-Protocol Label Switching (GMPLS) Signaling Extensions for G.709 Optical Transport Networks Control"">RFC4328</a>] to provide Resource |
| 128 |
Reservation Protocol - Traffic Engineering (RSVP-TE) extensions to |
| 129 |
support control for [<a href="#ref-G709-2012" title=""Interfaces for the Optical Transport Network (OTN)"">G709-2012</a>]. |
| 130 |
|
| 131 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Terminology</span> |
| 132 |
|
| 133 |
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", |
| 134 |
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this |
| 135 |
document are to be interpreted as described in [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>]. |
| 136 |
|
| 137 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. GMPLS Extensions for the Evolving G.709 -- Overview</span> |
| 138 |
|
| 139 |
New features for the evolving OTN, for example, new ODU0, ODU2e, |
| 140 |
ODU4, and ODUflex containers, are specified in [<a href="#ref-G709-2012" title=""Interfaces for the Optical Transport Network (OTN)"">G709-2012</a>]. The |
| 141 |
corresponding new Signal Types are summarized below: |
| 142 |
|
| 143 |
- Optical channel Transport Unit (OTUk): |
| 144 |
o OTU4 |
| 145 |
|
| 146 |
- Optical channel Data Unit (ODUk): |
| 147 |
o ODU0 |
| 148 |
o ODU2e |
| 149 |
o ODU4 |
| 150 |
o ODUflex |
| 151 |
|
| 152 |
A new tributary slot granularity (i.e., 1.25 Gbps) is also described |
| 153 |
in [<a href="#ref-G709-2012" title=""Interfaces for the Optical Transport Network (OTN)"">G709-2012</a>]. Thus, there are now two tributary slot (TS) |
| 154 |
granularities for the foundation OTN ODU1, ODU2, and ODU3 containers. |
| 155 |
The TS granularity at 2.5 Gbps is used on the legacy interfaces while |
| 156 |
the new 1.25 Gbps is used on the new interfaces. |
| 157 |
|
| 158 |
|
| 159 |
|
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Zhang, et al. Standards Track [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc7139">RFC 7139</a> GMPLS Extensions for G.709 March 2014</span> |
| 167 |
|
| 168 |
|
| 169 |
In addition to the support of ODUk mapping into OTUk (k = 1, 2, 3, |
| 170 |
4), [<a href="#ref-G709-2012" title=""Interfaces for the Optical Transport Network (OTN)"">G709-2012</a>] encompasses the multiplexing of ODUj (j = 0, 1, 2, |
| 171 |
2e, 3, flex) into an ODUk (k > j), as described in <a href="./rfc7062#section-3.1.2">Section 3.1.2 of |
| 172 |
[RFC7062]</a>. |
| 173 |
|
| 174 |
Virtual Concatenation (VCAT) of Optical channel Payload Unit-k (OPUk) |
| 175 |
(OPUk-Xv, k = 1/2/3, X = 1...256) is also supported by [<a href="#ref-G709-2012" title=""Interfaces for the Optical Transport Network (OTN)"">G709-2012</a>]. |
| 176 |
Note that VCAT of OPU0 / OPU2e / OPU4 / OPUflex is not supported per |
| 177 |
[<a href="#ref-G709-2012" title=""Interfaces for the Optical Transport Network (OTN)"">G709-2012</a>]. |
| 178 |
|
| 179 |
[<a id="ref-RFC4328">RFC4328</a>] describes GMPLS signaling extensions to support the control |
| 180 |
for the 2001 revision of the G.709 specification. However, [<a href="./rfc7096" title=""Evaluation of Existing GMPLS Encoding against G.709v3 Optical Transport Networks (OTNs)"">RFC7096</a>] |
| 181 |
does not provide the means to signal all the new Signal Types and |
| 182 |
related mapping and multiplexing functionalities. Moreover, it |
| 183 |
supports only the deprecated auto-MSI (Multiframe Structure |
| 184 |
Identifier) mode, which assumes that the Tributary Port Number (TPN) |
| 185 |
is automatically assigned in the transmit direction and not checked |
| 186 |
in the receive direction. |
| 187 |
|
| 188 |
This document extends the G.709 Traffic Parameters described in |
| 189 |
[<a href="./rfc4328" title=""Generalized Multi-Protocol Label Switching (GMPLS) Signaling Extensions for G.709 Optical Transport Networks Control"">RFC4328</a>] and presents a new flexible and scalable OTN-TDM |
| 190 |
Generalized Label format. (Here, TDM refers to Time-Division |
| 191 |
Multiplexing.) Additionally, procedures about Tributary Port Number |
| 192 |
assignment through the control plane are also provided in this |
| 193 |
document. |
| 194 |
|
| 195 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Generalized Label Request</span> |
| 196 |
|
| 197 |
The GENERALIZED_LABEL_REQUEST object, as described in [<a href="./rfc3471" title=""Generalized Multi-Protocol Label Switching (GMPLS) Signaling Functional Description"">RFC3471</a>], |
| 198 |
carries the Label Switched Path (LSP) Encoding Type, the Switching |
| 199 |
Type, and the Generalized Protocol Identifier (G-PID). |
| 200 |
|
| 201 |
[<a id="ref-RFC4328">RFC4328</a>] extends the GENERALIZED_LABEL_REQUEST object, introducing |
| 202 |
two new code-points for the LSP Encoding Type (i.e., G.709 ODUk |
| 203 |
(Digital Path) and G.709 Optical Channel) and adding a list of G-PID |
| 204 |
values in order to accommodate the 2001 revision of the G.709 |
| 205 |
specification. |
| 206 |
|
| 207 |
This document follows these extensions and introduces a new Switching |
| 208 |
Type to indicate the ODUk Switching Capability [<a href="#ref-G709-2012" title=""Interfaces for the Optical Transport Network (OTN)"">G709-2012</a>] in order |
| 209 |
to support backward compatibility with [<a href="./rfc4328" title=""Generalized Multi-Protocol Label Switching (GMPLS) Signaling Extensions for G.709 Optical Transport Networks Control"">RFC4328</a>], as described in |
| 210 |
[<a href="./rfc7062" title=""Framework for GMPLS and PCE Control of G.709 Optical Transport Networks"">RFC7062</a>]. The new Switching Type (OTN-TDM Switching Type) is |
| 211 |
defined in [<a href="./rfc7138" title=""Traffic Engineering Extensions to OSPF for GMPLS Control of Evolving G.709 Optical Transport Networks"">RFC7138</a>]. |
| 212 |
|
| 213 |
|
| 214 |
|
| 215 |
|
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Zhang, et al. Standards Track [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc7139">RFC 7139</a> GMPLS Extensions for G.709 March 2014</span> |
| 223 |
|
| 224 |
|
| 225 |
This document also updates the G-PID values defined in [<a href="./rfc4328" title=""Generalized Multi-Protocol Label Switching (GMPLS) Signaling Extensions for G.709 Optical Transport Networks Control"">RFC4328</a>]: |
| 226 |
|
| 227 |
Value G-PID Type |
| 228 |
----- ---------- |
| 229 |
|
| 230 |
47 Type field updated from "G.709 ODUj" to "ODU-2.5G" to |
| 231 |
indicate transport of Digital Paths (e.g., at 2.5, 10, and |
| 232 |
40 Gbps) via 2.5 Gbps TS granularity. |
| 233 |
|
| 234 |
56 Type field updated from "ESCON" to "SBCON/ESCON" to align |
| 235 |
with [<a href="#ref-G709-2012" title=""Interfaces for the Optical Transport Network (OTN)"">G709-2012</a>] payload type 0x1A. |
| 236 |
|
| 237 |
Note: Value 47 includes mapping of Synchronous Digital Hierarchy |
| 238 |
(SDH). |
| 239 |
|
| 240 |
In the case of ODU multiplexing, the Lower Order ODU (LO ODU) (i.e., |
| 241 |
the client signal) may be multiplexed into a Higher Order ODU (HO |
| 242 |
ODU) via 1.25G TS granularity, 2.5G TS granularity, or ODU-any. |
| 243 |
Since the G-PID type "ODUk" defined in [<a href="./rfc4328" title=""Generalized Multi-Protocol Label Switching (GMPLS) Signaling Extensions for G.709 Optical Transport Networks Control"">RFC4328</a>] is only used for 2.5 |
| 244 |
Gbps TS granularity, two new G-PID types are defined as follows: |
| 245 |
|
| 246 |
- ODU-1.25G: Transport of Digital Paths at 1.25, 2.5, 10, 40, and |
| 247 |
100 Gbps via 1.25 Gbps TS granularity. |
| 248 |
|
| 249 |
- ODU-any: Transport of Digital Paths at 1.25, 2.5, 10, 40, and |
| 250 |
100 Gbps via 1.25 or 2.5 Gbps TS granularity (i.e., |
| 251 |
the fallback procedure is enabled and the default |
| 252 |
value of 1.25 Gbps TS granularity can fall back to 2.5 |
| 253 |
Gbps if needed). |
| 254 |
|
| 255 |
The full list of payload types defined in [<a href="#ref-G709-2012" title=""Interfaces for the Optical Transport Network (OTN)"">G709-2012</a>] and their |
| 256 |
mapping to existing and new G-PID types are as follows: |
| 257 |
|
| 258 |
G.709 |
| 259 |
Payload |
| 260 |
Type G-PID Type/Comment LSP Encoding |
| 261 |
==== ===== ===================== =================== |
| 262 |
0x01 No standard value |
| 263 |
0x02 49 CBRa G.709 ODUk |
| 264 |
0x03 50 CBRb G.709 ODUk |
| 265 |
0x04 32 ATM G.709 ODUk |
| 266 |
0x05 59 Framed GFP G.709 ODUk |
| 267 |
54 Ethernet MAC (framed GFP) G.709 ODUk |
| 268 |
70 64B/66B GFP-F Ethernet G.709 ODUk (k=2) |
| 269 |
0x06 Not signaled |
| 270 |
0x07 55 Ethernet PHY G.709 ODUk (k=0,3,4) |
| 271 |
(transparent GFP) |
| 272 |
0x08 58 Fiber Channel G.709 ODUk (k=2e) |
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Zhang, et al. Standards Track [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc7139">RFC 7139</a> GMPLS Extensions for G.709 March 2014</span> |
| 279 |
|
| 280 |
|
| 281 |
0x09 59 Framed GFP G.709 ODUk (k=2) |
| 282 |
70 64B/66B GFP-F Ethernet G.709 ODUk (k=2) |
| 283 |
0x0A 60 STM-1 G.709 ODUk (k=0) |
| 284 |
0x0B 61 STM-4 G.709 ODUk (k=0) |
| 285 |
0x0C 58 Fiber Channel G.709 ODUk (k=0) |
| 286 |
0x0D 58 Fiber Channel G.709 ODUk (k=1) |
| 287 |
0x0E 58 Fiber Channel G.709 ODUflex |
| 288 |
0x0F 58 Fiber Channel G.709 ODUflex |
| 289 |
0x10 51 BSOT G.709 ODUk |
| 290 |
0x11 52 BSNT G.709 ODUk |
| 291 |
0x12 62 InfiniBand G.709 ODUflex |
| 292 |
0x13 62 InfiniBand G.709 ODUflex |
| 293 |
0x14 62 InfiniBand G.709 ODUflex |
| 294 |
0x15 63 Serial Digital Interface G.709 ODUk (k=0) |
| 295 |
0x16 64 SDI/1.001 G.709 ODUk (k=1) |
| 296 |
0x17 63 Serial Digital Interface G.709 ODUk (k=1) |
| 297 |
0x18 64 SDI/1.001 G.709 ODUflex |
| 298 |
0x19 63 Serial Digital Interface G.709 ODUflex |
| 299 |
0x1A 56 SBCON/ESCON G.709 ODUk (k=0) |
| 300 |
0x1B 65 DVB_ASI G.709 ODUk (k=0) |
| 301 |
0x1C 58 Fiber Channel G.709 ODUk |
| 302 |
0x20 47 G.709 ODU-2.5G G.709 ODUk (k=2,3) |
| 303 |
66 G.709 ODU-1.25G G.709 ODUk (k=1) |
| 304 |
0x21 66 G.709 ODU-1.25G G.709 ODUk (k=2,3,4) |
| 305 |
67 G.709 ODU-any G.709 ODUk (k=2,3) |
| 306 |
0x55 No standard value |
| 307 |
0x66 No standard value |
| 308 |
0x80-0x8F No standard value |
| 309 |
0xFD 68 Null Test G.709 ODUk |
| 310 |
0xFE 69 Random Test G.709 ODUk |
| 311 |
0xFF No standard value |
| 312 |
|
| 313 |
Note: Values 59 and 70 include mapping of SDH. |
| 314 |
|
| 315 |
Note that the mapping types for ODUj into OPUk are unambiguously per |
| 316 |
Table 7-10 of [<a href="#ref-G709-2012" title=""Interfaces for the Optical Transport Network (OTN)"">G709-2012</a>], so there is no need to carry mapping type |
| 317 |
information in the signaling. |
| 318 |
|
| 319 |
Note also that additional information on G.709 client mapping can be |
| 320 |
found in [<a href="#ref-G7041" title=""Generic framing procedure"">G7041</a>]. |
| 321 |
|
| 322 |
|
| 323 |
|
| 324 |
|
| 325 |
|
| 326 |
|
| 327 |
|
| 328 |
|
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Zhang, et al. Standards Track [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc7139">RFC 7139</a> GMPLS Extensions for G.709 March 2014</span> |
| 335 |
|
| 336 |
|
| 337 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Extensions for Traffic Parameters for Evolving G.709 OTNs</span> |
| 338 |
|
| 339 |
The Traffic Parameters for the OTN-TDM-capable Switching Type are |
| 340 |
carried in the OTN-TDM SENDER_TSPEC object in the Path message and |
| 341 |
the OTN-TDM FLOWSPEC object in the Resv message. The objects have |
| 342 |
the following class and type: |
| 343 |
|
| 344 |
- OTN-TDM SENDER_TSPEC object: Class = 12, C-Type = 7 |
| 345 |
- OTN-TDM FLOWSPEC object: Class = 9, C-Type = 7 |
| 346 |
|
| 347 |
The format of Traffic Parameters in these two objects is defined as |
| 348 |
follows: |
| 349 |
|
| 350 |
0 1 2 3 |
| 351 |
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 |
| 352 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 353 |
| Signal Type | Reserved | |
| 354 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 355 |
| NVC | Multiplier (MT) | |
| 356 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 357 |
| Bit_Rate | |
| 358 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 359 |
|
| 360 |
Signal Type: 8 bits |
| 361 |
|
| 362 |
As defined in <a href="./rfc4328#section-3.2.1">Section 3.2.1 of [RFC4328]</a>, with the following |
| 363 |
additional values: |
| 364 |
|
| 365 |
Value Type |
| 366 |
----- ---- |
| 367 |
4 ODU4 (i.e., 100 Gbps) |
| 368 |
9 OCh at 100 Gbps |
| 369 |
10 ODU0 (i.e., 1.25 Gbps) |
| 370 |
11 ODU2e (i.e., 10 Gbps for FC1200 and GE LAN) |
| 371 |
12-19 Reserved (for future use) |
| 372 |
20 ODUflex(CBR) (i.e., 1.25*N Gbps) |
| 373 |
21 ODUflex(GFP-F), resizable (i.e., 1.25*N Gbps) |
| 374 |
22 ODUflex(GFP-F), non-resizable (i.e., 1.25*N Gbps) |
| 375 |
23-255 Reserved (for future use) |
| 376 |
|
| 377 |
Note: Above, CBR stands for Constant Bit Rate, and GFP-F stands for |
| 378 |
Generic Framing Procedure - Framed. |
| 379 |
|
| 380 |
NVC (Number of Virtual Components): 16 bits |
| 381 |
|
| 382 |
As defined in <a href="./rfc4328#section-3.2.3">Section 3.2.3 of [RFC4328]</a>. This field MUST be set |
| 383 |
to 0 for ODUflex Signal Types. |
| 384 |
|
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Zhang, et al. Standards Track [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc7139">RFC 7139</a> GMPLS Extensions for G.709 March 2014</span> |
| 391 |
|
| 392 |
|
| 393 |
Multiplier (MT): 16 bits |
| 394 |
|
| 395 |
As defined in <a href="./rfc4328#section-3.2.4">Section 3.2.4 of [RFC4328]</a>. This field MUST be set |
| 396 |
to 1 for ODUflex Signal Types. |
| 397 |
|
| 398 |
Bit_Rate: 32 bits |
| 399 |
|
| 400 |
In the case of ODUflex, including ODUflex(CBR) and ODUflex(GFP) |
| 401 |
Signal Types, this field indicates the nominal bit rate of ODUflex |
| 402 |
expressed in bytes per second, encoded as a 32-bit IEEE single- |
| 403 |
precision floating-point number (referring to [<a href="./rfc4506" title=""XDR: External Data Representation Standard"">RFC4506</a>] and |
| 404 |
[<a href="#ref-IEEE" title=""IEEE Standard for Binary Floating-Point Arithmetic"">IEEE</a>]). For other Signal Types, this field MUST be set to zero |
| 405 |
on transmission, MUST be ignored on receipt, and SHOULD be passed |
| 406 |
unmodified by transit nodes. |
| 407 |
|
| 408 |
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. Usage of ODUflex(CBR) Traffic Parameters</span> |
| 409 |
|
| 410 |
In the case of ODUflex(CBR), the Bit_Rate information carried in the |
| 411 |
ODUflex Traffic Parameters MUST be used to determine the actual |
| 412 |
bandwidth of ODUflex(CBR) (i.e., Bit_Rate * (1 +/- Tolerance)). |
| 413 |
Therefore, the total number of tributary slots N in the HO ODUk link |
| 414 |
can be reserved correctly. Where: |
| 415 |
|
| 416 |
N = Ceiling of |
| 417 |
|
| 418 |
ODUflex(CBR) nominal bit rate * (1 + ODUflex(CBR) bit rate tolerance) |
| 419 |
--------------------------------------------------------------------- |
| 420 |
ODTUk.ts nominal bit rate * (1 - HO OPUk bit rate tolerance) |
| 421 |
|
| 422 |
In this formula, the ODUflex(CBR) nominal bit rate is the bit rate of |
| 423 |
the ODUflex(CBR) on the line side, i.e., the client signal bit rate |
| 424 |
after applying the 239/238 factor (according to Clause 7.3, Table 7-2 |
| 425 |
of [<a href="#ref-G709-2012" title=""Interfaces for the Optical Transport Network (OTN)"">G709-2012</a>]) and the transcoding factor T (if needed) on the CBR |
| 426 |
client. According to Clauses 17.7.3, 17.7.4, and 17.7.5 of |
| 427 |
[<a href="#ref-G709-2012" title=""Interfaces for the Optical Transport Network (OTN)"">G709-2012</a>]: |
| 428 |
|
| 429 |
ODUflex(CBR) nominal bit rate = CBR client bit rate * (239/238) / T |
| 430 |
|
| 431 |
The ODTUk.ts (Optical channel Data Tributary Unit k with ts tributary |
| 432 |
slots) nominal bit rate is the nominal bit rate of the tributary slot |
| 433 |
of ODUk, as shown in Table 1 (referring to Table 7-7 of [<a href="#ref-G709-2012" title=""Interfaces for the Optical Transport Network (OTN)"">G709-2012</a>]). |
| 434 |
|
| 435 |
|
| 436 |
|
| 437 |
|
| 438 |
|
| 439 |
|
| 440 |
|
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Zhang, et al. Standards Track [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc7139">RFC 7139</a> GMPLS Extensions for G.709 March 2014</span> |
| 447 |
|
| 448 |
|
| 449 |
ODUk.ts Minimum Nominal Maximum |
| 450 |
----------------------------------------------------------- |
| 451 |
ODU2.ts 1,249,384.632 1,249,409.620 1,249,434.608 |
| 452 |
ODU3.ts 1,254,678.635 1,254,703.729 1,254,728.823 |
| 453 |
ODU4.ts 1,301,683.217 1,301,709.251 1,301,735.285 |
| 454 |
|
| 455 |
Table 1: Actual TS Bit Rate of ODUk (in Kbps) |
| 456 |
|
| 457 |
Note that: |
| 458 |
|
| 459 |
Minimum bit rate of ODUTk.ts = |
| 460 |
ODTUk.ts nominal bit rate * (1 - HO OPUk bit rate tolerance) |
| 461 |
|
| 462 |
Maximum bit rate of ODTUk.ts = |
| 463 |
ODTUk.ts nominal bit rate * (1 + HO OPUk bit rate tolerance) |
| 464 |
|
| 465 |
Where: HO OPUk bit rate tolerance = 20 ppm (parts per million) |
| 466 |
|
| 467 |
Note that the bit rate tolerance is implicit in Signal Type and the |
| 468 |
ODUflex(CBR) bit rate tolerance is fixed and it is equal to 100 ppm |
| 469 |
as described in Table 7-2 of [<a href="#ref-G709-2012" title=""Interfaces for the Optical Transport Network (OTN)"">G709-2012</a>]. |
| 470 |
|
| 471 |
Therefore, a node receiving a Path message containing an ODUflex(CBR) |
| 472 |
nominal bit rate can allocate a precise number of tributary slots and |
| 473 |
set up the cross-connection for the ODUflex service. |
| 474 |
|
| 475 |
Note that for different ODUk, the bit rates of the tributary slots |
| 476 |
are different, so the total number of tributary slots to be reserved |
| 477 |
for the ODUflex(CBR) may not be the same on different HO ODUk links. |
| 478 |
|
| 479 |
An example is given below to illustrate the usage of ODUflex(CBR) |
| 480 |
Traffic Parameters. |
| 481 |
|
| 482 |
+-----+ +---------+ +-----+ |
| 483 |
| +-------------+ +-----+ +-------------+ | |
| 484 |
| +=============+\| ODU |/+=============+ | |
| 485 |
| +=============+/| flex+-+=============+ | |
| 486 |
| +-------------+ | |\+=============+ | |
| 487 |
| +-------------+ +-----+ +-------------+ | |
| 488 |
| | | | | | |
| 489 |
| | ....... | | ....... | | |
| 490 |
| A +-------------+ B +-------------+ C | |
| 491 |
+-----+ HO ODU4 +---------+ HO ODU2 +-----+ |
| 492 |
|
| 493 |
=========: TSs occupied by ODUflex |
| 494 |
---------: available TSs |
| 495 |
|
| 496 |
Figure 1: Example of ODUflex(CBR) Traffic Parameters |
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">Zhang, et al. Standards Track [Page 9]</span></pre> |
| 501 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span> |
| 502 |
<span class="grey"><a href="./rfc7139">RFC 7139</a> GMPLS Extensions for G.709 March 2014</span> |
| 503 |
|
| 504 |
|
| 505 |
As shown in Figure 1, assume there is an ODUflex(CBR) service |
| 506 |
requesting a bandwidth of 2.5 Gbps from node A to node C. |
| 507 |
|
| 508 |
In other words, the ODUflex Traffic Parameters indicate that Signal |
| 509 |
Type is 20 (ODUflex(CBR)) and Bit_Rate is 2.5 Gbps (note that the |
| 510 |
tolerance is not signaled as explained above). |
| 511 |
|
| 512 |
- On the HO ODU4 link between node A and B: |
| 513 |
|
| 514 |
The maximum bit rate of the ODUflex(CBR) equals 2.5 Gbps * (1 + |
| 515 |
100 ppm), and the minimum bit rate of the tributary slot of ODU4 |
| 516 |
equals 1,301,683.217 Kbps, so the total number of tributary slots |
| 517 |
N1 to be reserved on this link is: |
| 518 |
|
| 519 |
N1 = ceiling (2.5 Gbps * (1 + 100 ppm) / 1,301,683.217 Kbps) = 2 |
| 520 |
|
| 521 |
- On the HO ODU2 link between node B and C: |
| 522 |
|
| 523 |
The maximum bit rate of the ODUflex equals 2.5 Gbps * (1 + 100 |
| 524 |
ppm), and the minimum bit rate of the tributary slot of ODU2 |
| 525 |
equals 1,249,384.632 Kbps, so the total number of tributary slots |
| 526 |
N2 to be reserved on this link is: |
| 527 |
|
| 528 |
N2 = ceiling (2.5 Gbps * (1 + 100 ppm) / 1,249,384.632 Kbps) = 3 |
| 529 |
|
| 530 |
<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. Usage of ODUflex(GFP) Traffic Parameters</span> |
| 531 |
|
| 532 |
[<a id="ref-G709-2012">G709-2012</a>] recommends that the ODUflex(GFP) fill an integral number |
| 533 |
of tributary slots of the smallest HO ODUk path over which the |
| 534 |
ODUflex(GFP) may be carried, as shown in Table 2. |
| 535 |
|
| 536 |
ODU Type | Nominal Bit Rate | Tolerance |
| 537 |
---------------------------------+------------------+----------- |
| 538 |
ODUflex(GFP) of n TSs, 1<=n<=8 | n * ODU2.ts | +/-100 ppm |
| 539 |
ODUflex(GFP) of n TSs, 9<=n<=32 | n * ODU3.ts | +/-100 ppm |
| 540 |
ODUflex(GFP) of n TSs, 33<=n<=80 | n * ODU4.ts | +/-100 ppm |
| 541 |
|
| 542 |
Table 2: Recommended ODUflex(GFP) Bit Rates and Tolerance |
| 543 |
|
| 544 |
According to this table, the Bit_Rate field for ODUflex(GFP) MUST be |
| 545 |
equal to one of the 80 values listed below: |
| 546 |
|
| 547 |
1 * ODU2.ts; 2 * ODU2.ts; ...; 8 * ODU2.ts; |
| 548 |
9 * ODU3.ts; 10 * ODU3.ts, ...; 32 * ODU3.ts; |
| 549 |
33 * ODU4.ts; 34 * ODU4.ts; ...; 80 * ODU4.ts. |
| 550 |
|
| 551 |
|
| 552 |
|
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
<span class="grey">Zhang, et al. Standards Track [Page 10]</span></pre> |
| 557 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span> |
| 558 |
<span class="grey"><a href="./rfc7139">RFC 7139</a> GMPLS Extensions for G.709 March 2014</span> |
| 559 |
|
| 560 |
|
| 561 |
In this way, the number of required tributary slots for the |
| 562 |
ODUflex(GFP) (i.e., the value of "n" in Table 2) can be deduced from |
| 563 |
the Bit_Rate field. |
| 564 |
|
| 565 |
<span class="h3"><a class="selflink" id="section-5.3" href="#section-5.3">5.3</a>. Notification on Errors of OTN-TDM Traffic Parameters</span> |
| 566 |
|
| 567 |
There is no Adspec associated with the OTN-TDM SENDER_TSPEC object. |
| 568 |
Either the Adspec is omitted or an Int-serv Adspec with the Default |
| 569 |
General Characterization Parameters and Guaranteed Service fragment |
| 570 |
is used (see [<a href="./rfc2210" title=""The Use of RSVP with IETF Integrated Services"">RFC2210</a>]). |
| 571 |
|
| 572 |
For a particular sender in a session, the contents of the OTN-TDM |
| 573 |
FLOWSPEC object received in a Resv message SHOULD be identical to the |
| 574 |
contents of the OTN-TDM SENDER_TSPEC object received in the |
| 575 |
corresponding Path message. If the objects do not match, a ResvErr |
| 576 |
message with a "Traffic Control Error/Bad Flowspec value" error MUST |
| 577 |
be generated. |
| 578 |
|
| 579 |
Intermediate and egress nodes MUST verify that the node itself, and |
| 580 |
the interfaces on which the LSP will be established, can support the |
| 581 |
requested Signal Type, NVC, and Bit_Rate values. If the requested |
| 582 |
value(s) cannot be supported, the receiver node MUST generate a |
| 583 |
PathErr message with a "Traffic Control Error/Service unsupported" |
| 584 |
indication (see [<a href="./rfc2205" title=""Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification"">RFC2205</a>]). |
| 585 |
|
| 586 |
In addition, if the MT field is received with a zero value, the node |
| 587 |
MUST generate a PathErr message with a "Traffic Control Error/Bad |
| 588 |
Tspec value" indication (see [<a href="./rfc2205" title=""Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification"">RFC2205</a>]). |
| 589 |
|
| 590 |
Further, if the Signal Type is not ODU1, ODU2, or ODU3, and the NVC |
| 591 |
field is not 0, the node MUST generate a PathErr message with a |
| 592 |
"Traffic Control Error/Bad Tspec value" indication (see [<a href="./rfc2205" title=""Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification"">RFC2205</a>]). |
| 593 |
|
| 594 |
|
| 595 |
|
| 596 |
|
| 597 |
|
| 598 |
|
| 599 |
|
| 600 |
|
| 601 |
|
| 602 |
|
| 603 |
|
| 604 |
|
| 605 |
|
| 606 |
|
| 607 |
|
| 608 |
|
| 609 |
|
| 610 |
|
| 611 |
|
| 612 |
<span class="grey">Zhang, et al. Standards Track [Page 11]</span></pre> |
| 613 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span> |
| 614 |
<span class="grey"><a href="./rfc7139">RFC 7139</a> GMPLS Extensions for G.709 March 2014</span> |
| 615 |
|
| 616 |
|
| 617 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Generalized Label</span> |
| 618 |
|
| 619 |
This section defines the format of the OTN-TDM Generalized Label. |
| 620 |
|
| 621 |
<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. OTN-TDM Switching Type Generalized Label</span> |
| 622 |
|
| 623 |
The following is the GENERALIZED_LABEL object format that MUST be |
| 624 |
used with the OTN-TDM Switching Type: |
| 625 |
|
| 626 |
0 1 2 3 |
| 627 |
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 |
| 628 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 629 |
| TPN | Reserved | Length | |
| 630 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 631 |
~ Bit Map ...... ~ |
| 632 |
~ ...... | Padding Bits ~ |
| 633 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 634 |
|
| 635 |
The OTN-TDM GENERALIZED_LABEL object is used to indicate how the LO |
| 636 |
ODUj signal is multiplexed into the HO ODUk link. Note that the LO |
| 637 |
OUDj Signal Type is indicated by Traffic Parameters, while the type |
| 638 |
of HO ODUk link is identified by the selected interface carried in |
| 639 |
the IF_ID RSVP_HOP object. |
| 640 |
|
| 641 |
TPN: 12 bits |
| 642 |
|
| 643 |
Indicates the TPN for the assigned tributary slot(s). |
| 644 |
|
| 645 |
- In the case of an LO ODUj multiplexed into an HO |
| 646 |
ODU1/ODU2/ODU3, only the lower 6 bits of the TPN field are |
| 647 |
significant; the other bits of the TPN field MUST be set to 0. |
| 648 |
|
| 649 |
- In the case of an LO ODUj multiplexed into an HO ODU4, only the |
| 650 |
lower 7 bits of the TPN field are significant; the other bits |
| 651 |
of the TPN field MUST be set to 0. |
| 652 |
|
| 653 |
- In the case of ODUj mapped into OTUk (j=k), the TPN is not |
| 654 |
needed, and this field MUST be set to 0. |
| 655 |
|
| 656 |
Per [<a href="#ref-G709-2012" title=""Interfaces for the Optical Transport Network (OTN)"">G709-2012</a>], the TPN is used to allow for correct |
| 657 |
demultiplexing in the data plane. When an LO ODUj is multiplexed |
| 658 |
into an HO ODUk occupying one or more TSs, a new TPN value is |
| 659 |
configured at the two ends of the HO ODUk link and is put into the |
| 660 |
related MSI byte(s) in the OPUk overhead at the (traffic) ingress |
| 661 |
end of the link, so that the other end of the link can learn which |
| 662 |
TS(s) is/are used by the LO ODUj in the data plane. |
| 663 |
|
| 664 |
|
| 665 |
|
| 666 |
|
| 667 |
|
| 668 |
<span class="grey">Zhang, et al. Standards Track [Page 12]</span></pre> |
| 669 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span> |
| 670 |
<span class="grey"><a href="./rfc7139">RFC 7139</a> GMPLS Extensions for G.709 March 2014</span> |
| 671 |
|
| 672 |
|
| 673 |
According to [<a href="#ref-G709-2012" title=""Interfaces for the Optical Transport Network (OTN)"">G709-2012</a>], the TPN field MUST be set according to |
| 674 |
the following tables: |
| 675 |
|
| 676 |
+-------+-------+----+-------------------------------------------+ |
| 677 |
|HO ODUk|LO ODUj|TPN | TPN Assignment Rules | |
| 678 |
+-------+-------+----+-------------------------------------------+ |
| 679 |
| ODU2 | ODU1 |1-4 |Fixed, = TS# occupied by ODU1 | |
| 680 |
+-------+-------+----+-------------------------------------------+ |
| 681 |
| | ODU1 |1-16|Fixed, = TS# occupied by ODU1 | |
| 682 |
| ODU3 +-------+----+-------------------------------------------+ |
| 683 |
| | ODU2 |1-4 |Flexible, != other existing LO ODU2s' TPNs | |
| 684 |
+-------+-------+----+-------------------------------------------+ |
| 685 |
|
| 686 |
Table 3: TPN Assignment Rules (2.5 Gbps TS Granularity) |
| 687 |
|
| 688 |
+-------+-------+----+-------------------------------------------+ |
| 689 |
|HO ODUk|LO ODUj|TPN | TPN Assignment Rules | |
| 690 |
+-------+-------+----+-------------------------------------------+ |
| 691 |
| ODU1 | ODU0 |1-2 |Fixed, = TS# occupied by ODU0 | |
| 692 |
+-------+-------+----+-------------------------------------------+ |
| 693 |
| | ODU1 |1-4 |Flexible, != other existing LO ODU1s' TPNs | |
| 694 |
| ODU2 +-------+----+-------------------------------------------+ |
| 695 |
| |ODU0 & |1-8 |Flexible, != other existing LO ODU0s and | |
| 696 |
| |ODUflex| |ODUflexes' TPNs | |
| 697 |
+-------+-------+----+-------------------------------------------+ |
| 698 |
| | ODU1 |1-16|Flexible, != other existing LO ODU1s' TPNs | |
| 699 |
| +-------+----+-------------------------------------------+ |
| 700 |
| | ODU2 |1-4 |Flexible, != other existing LO ODU2s' TPNs | |
| 701 |
| ODU3 +-------+----+-------------------------------------------+ |
| 702 |
| |ODU0 & | |Flexible, != other existing LO ODU0s and | |
| 703 |
| |ODU2e &|1-32|ODU2s and ODUflexes' TPNs | |
| 704 |
| |ODUflex| | | |
| 705 |
+-------+-------+----+-------------------------------------------+ |
| 706 |
| ODU4 |Any ODU|1-80|Flexible, != ANY other existing LO ODUs' | |
| 707 |
| | | |TPNs | |
| 708 |
+-------+-------+----+-------------------------------------------+ |
| 709 |
|
| 710 |
Table 4: TPN Assignment Rules (1.25 Gbps TS Granularity) |
| 711 |
|
| 712 |
Note that in the case of "Flexible", the value of TPN MAY not |
| 713 |
correspond to the TS number as per [<a href="#ref-G709-2012" title=""Interfaces for the Optical Transport Network (OTN)"">G709-2012</a>]. |
| 714 |
|
| 715 |
Length: 12 bits |
| 716 |
|
| 717 |
Indicates the number of bits of the Bit Map field, i.e., the total |
| 718 |
number of TSs in the HO ODUk link. The TS granularity, 1.25 Gbps |
| 719 |
or 2.5 Gbps, may be derived by dividing the HO ODUk link's rate by |
| 720 |
|
| 721 |
|
| 722 |
|
| 723 |
|
| 724 |
<span class="grey">Zhang, et al. Standards Track [Page 13]</span></pre> |
| 725 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span> |
| 726 |
<span class="grey"><a href="./rfc7139">RFC 7139</a> GMPLS Extensions for G.709 March 2014</span> |
| 727 |
|
| 728 |
|
| 729 |
the value of the Length field. In the context of [<a href="#ref-G709-2012" title=""Interfaces for the Optical Transport Network (OTN)"">G709-2012</a>], the |
| 730 |
values of 4 and 16 indicate a TS granularity of 2.5 Gbps, and the |
| 731 |
values 2, 8, 32, and 80 indicate a TS granularity of 1.25 Gbps. |
| 732 |
|
| 733 |
In the case of an ODUk mapped into OTUk, there is no need to |
| 734 |
indicate which tributary slots will be used, so the Length field |
| 735 |
MUST be set to 0. |
| 736 |
|
| 737 |
Bit Map: variable |
| 738 |
|
| 739 |
Indicates which tributary slots in the HO ODUk that the LO ODUj |
| 740 |
will be multiplexed into. The sequence of the Bit Map is |
| 741 |
consistent with the sequence of the tributary slots in the HO |
| 742 |
ODUk. Each bit in the bit map represents the corresponding |
| 743 |
tributary slot in the HO ODUk with a value of 1 or 0 indicating |
| 744 |
whether the tributary slot will be used by the LO ODUj or not. |
| 745 |
|
| 746 |
Padding Bits |
| 747 |
|
| 748 |
Are added after the Bit Map to make the whole label a multiple of |
| 749 |
four bytes if necessary. Padding bits MUST be set to 0 and MUST |
| 750 |
be ignored on receipt. |
| 751 |
|
| 752 |
<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Procedures</span> |
| 753 |
|
| 754 |
The ingress node MUST generate a Path message and specify the OTN-TDM |
| 755 |
Switching Type and corresponding G-PID in the |
| 756 |
GENERALIZED_LABEL_REQUEST object, which MUST be processed as defined |
| 757 |
in [<a href="./rfc3473" title=""Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions"">RFC3473</a>]. |
| 758 |
|
| 759 |
The ingress node of an LSP MAY include a Label ERO (Explicit Route |
| 760 |
Object) subobject to indicate the label in each hop along the path. |
| 761 |
Note that the TPN in the Label ERO subobject need not be assigned by |
| 762 |
the ingress node. When the TPN is assigned by a node, the node MUST |
| 763 |
assign a valid TPN value and then put this value into the TPN field |
| 764 |
of the GENERALIZED_LABEL object when receiving a Path message. |
| 765 |
|
| 766 |
In order to create bidirectional LSP, the ingress node and upstream |
| 767 |
node MUST generate an UPSTREAM_LABEL object on the outgoing interface |
| 768 |
to indicate the reserved TSs of ODUk and the assigned TPN value in |
| 769 |
the upstream direction. This UPSTREAM_LABEL object is sent to the |
| 770 |
downstream node via a Path massage for upstream resource reservation. |
| 771 |
|
| 772 |
The ingress node or upstream node MAY generate a LABEL_SET object to |
| 773 |
indicate which labels on the outgoing interface in the downstream |
| 774 |
direction are acceptable. The downstream node will restrict its |
| 775 |
choice of labels, i.e., TS resource and TPN value, to one that is in |
| 776 |
the LABEL_SET object. |
| 777 |
|
| 778 |
|
| 779 |
|
| 780 |
<span class="grey">Zhang, et al. Standards Track [Page 14]</span></pre> |
| 781 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span> |
| 782 |
<span class="grey"><a href="./rfc7139">RFC 7139</a> GMPLS Extensions for G.709 March 2014</span> |
| 783 |
|
| 784 |
|
| 785 |
The ingress node or upstream node MAY also generate a SUGGESTED_LABEL |
| 786 |
object to indicate the preference of TS resource and TPN value on the |
| 787 |
outgoing interface in the downstream direction. The downstream node |
| 788 |
is not required to use the suggested labels; it may use another label |
| 789 |
based on local decision and send it to the upstream node, as |
| 790 |
described in [<a href="./rfc3473" title=""Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions"">RFC3473</a>]. |
| 791 |
|
| 792 |
When an upstream node receives a Resv message containing a |
| 793 |
GENERALIZED_LABEL object with an OTN-TDM label, it MUST first |
| 794 |
identify which ODU Signal Type is multiplexed or mapped into which |
| 795 |
ODU Signal Type according to the Traffic Parameters and the IF_ID |
| 796 |
RSVP_HOP object in the received message. |
| 797 |
|
| 798 |
- In the case of ODUj-to-ODUk multiplexing, the node MUST retrieve |
| 799 |
the reserved tributary slots in the ODUk by its downstream |
| 800 |
neighbor node according to the position of the bits that are set |
| 801 |
to 1 in the Bit Map field. The node determines the TS granularity |
| 802 |
(according to the total TS number of the ODUk or pre-configured TS |
| 803 |
granularity), so that the node can multiplex the ODUj into the |
| 804 |
ODUk based on the TS granularity. The node MUST also retrieve the |
| 805 |
TPN value assigned by its downstream neighbor node from the label |
| 806 |
and fill the TPN into the related MSI byte(s) in the OPUk overhead |
| 807 |
in the data plane, so that the downstream neighbor node can check |
| 808 |
whether the TPN received from the data plane is consistent with |
| 809 |
the Expected MSI (ExMSI) and determine whether there is any |
| 810 |
mismatch defect. |
| 811 |
|
| 812 |
- In the case of ODUk-to-OTUk mapping, the size of the Bit Map field |
| 813 |
MUST be 0, and no additional procedure is needed. |
| 814 |
|
| 815 |
When a downstream node or egress node receives a Path message |
| 816 |
containing a GENERALIZED_LABEL_REQUEST object for setting up an ODUj |
| 817 |
LSP from its upstream neighbor node, the node MUST generate an OTN- |
| 818 |
TDM label according to the Signal Type of the requested LSP and the |
| 819 |
available resources (i.e., available tributary slots of ODUk) that |
| 820 |
will be reserved for the LSP and send the label to its upstream |
| 821 |
neighbor node. |
| 822 |
|
| 823 |
- In the case of ODUj-to-ODUk multiplexing, the node MUST first |
| 824 |
determine the size of the Bit Map field according to the Signal |
| 825 |
Type and the tributary slot type of ODUk and then set the bits to |
| 826 |
1 in the Bit Map field corresponding to the reserved tributary |
| 827 |
slots. The node MUST also assign a valid TPN, which MUST NOT |
| 828 |
collide with other TPN values used by existing LO ODU connections |
| 829 |
in the selected HO ODU link, and configure the Expected MSI |
| 830 |
(ExMSI) using this TPN. Then, the assigned TPN MUST be filled |
| 831 |
into the label. |
| 832 |
|
| 833 |
|
| 834 |
|
| 835 |
|
| 836 |
<span class="grey">Zhang, et al. Standards Track [Page 15]</span></pre> |
| 837 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span> |
| 838 |
<span class="grey"><a href="./rfc7139">RFC 7139</a> GMPLS Extensions for G.709 March 2014</span> |
| 839 |
|
| 840 |
|
| 841 |
- In the case of ODUk-to-OTUk mapping, the TPN field MUST be set to |
| 842 |
0. Bit Map information is not required and MUST NOT be included, |
| 843 |
so the Length field MUST be set to 0 as well. |
| 844 |
|
| 845 |
<span class="h4"><a class="selflink" id="section-6.2.1" href="#section-6.2.1">6.2.1</a>. Notification on Label Error</span> |
| 846 |
|
| 847 |
When an upstream node receives a Resv message containing a |
| 848 |
GENERALIZED_LABEL object with an OTN-TDM label, the node MUST verify |
| 849 |
if the label is acceptable. If the label is not acceptable, the node |
| 850 |
MUST generate a ResvErr message with a "Routing problem/Unacceptable |
| 851 |
label value" indication. Per [<a href="./rfc3473" title=""Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions"">RFC3473</a>], the generated ResvErr |
| 852 |
message MAY include an ACCEPTABLE_LABEL_SET object. With the |
| 853 |
exception of label semantics, a downstream node processing a received |
| 854 |
ResvErr message and ACCEPTABLE_LABEL_SET object is not modified by |
| 855 |
this document. |
| 856 |
|
| 857 |
Similarly, when a downstream node receives a Path message containing |
| 858 |
an UPSTREAM_LABEL object with an OTN-TDM label, the node MUST verify |
| 859 |
if the label is acceptable. If the label is not acceptable, the node |
| 860 |
MUST generate a PathErr message with a "Routing problem/Unacceptable |
| 861 |
label value" indication. Per [<a href="./rfc3473" title=""Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions"">RFC3473</a>], the generated PathErr |
| 862 |
message MAY include an ACCEPTABLE_LABEL_SET object. With the |
| 863 |
exception of label semantics, the upstream nodes processing a |
| 864 |
received PathErr message and ACCEPTABLE_LABEL_SET object are not |
| 865 |
modified by this document. |
| 866 |
|
| 867 |
A received label SHALL be considered unacceptable when one of the |
| 868 |
following cases occurs: |
| 869 |
|
| 870 |
- The received label doesn't conform to local policy; |
| 871 |
|
| 872 |
- An invalid value appears in the Length field; |
| 873 |
|
| 874 |
- The selected link only supports 2.5 Gbps TS granularity while the |
| 875 |
Length field in the label along with ODUk Signal Type indicates |
| 876 |
the 1.25 Gbps TS granularity; |
| 877 |
|
| 878 |
- The label includes an invalid TPN value that breaks the TPN |
| 879 |
assignment rules; and |
| 880 |
|
| 881 |
- The indicated resources (i.e., the number of "1"s in the Bit Map |
| 882 |
field) are inconsistent with the Traffic Parameters. |
| 883 |
|
| 884 |
|
| 885 |
|
| 886 |
|
| 887 |
|
| 888 |
|
| 889 |
|
| 890 |
|
| 891 |
|
| 892 |
<span class="grey">Zhang, et al. Standards Track [Page 16]</span></pre> |
| 893 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span> |
| 894 |
<span class="grey"><a href="./rfc7139">RFC 7139</a> GMPLS Extensions for G.709 March 2014</span> |
| 895 |
|
| 896 |
|
| 897 |
<span class="h3"><a class="selflink" id="section-6.3" href="#section-6.3">6.3</a>. Supporting Virtual Concatenation and Multiplication</span> |
| 898 |
|
| 899 |
Per [<a href="./rfc6344" title=""Operating Virtual Concatenation (VCAT) and the Link Capacity Adjustment Scheme (LCAS) with Generalized Multi-Protocol Label Switching (GMPLS)"">RFC6344</a>], the Virtual Concatenation Groups (VCGs) can be created |
| 900 |
using the One LSP approach or the Multiple LSPs approach. |
| 901 |
|
| 902 |
In the case of the One LSP approach, the explicit ordered list of all |
| 903 |
labels MUST reflect the order of VCG members, which is similar to |
| 904 |
[<a href="./rfc4328" title=""Generalized Multi-Protocol Label Switching (GMPLS) Signaling Extensions for G.709 Optical Transport Networks Control"">RFC4328</a>]. In the case of multiplexed virtually concatenated signals |
| 905 |
(NVC > 1), the first label MUST indicate the components of the first |
| 906 |
virtually concatenated signal; the second label MUST indicate the |
| 907 |
components of the second virtually concatenated signal; and so on. |
| 908 |
In the case of multiplication of multiplexed virtually concatenated |
| 909 |
signals (MT > 1), the first label MUST indicate the components of the |
| 910 |
first multiplexed virtually concatenated signal; the second label |
| 911 |
MUST indicate components of the second multiplexed virtually |
| 912 |
concatenated signal; and so on. |
| 913 |
|
| 914 |
Support for Virtual Concatenation of ODU1, ODU2, and ODU3 Signal |
| 915 |
Types, as defined by [<a href="./rfc6344" title=""Operating Virtual Concatenation (VCAT) and the Link Capacity Adjustment Scheme (LCAS) with Generalized Multi-Protocol Label Switching (GMPLS)"">RFC6344</a>], is not modified by this document. |
| 916 |
Virtual Concatenation of other Signal Types is not supported by |
| 917 |
[<a href="#ref-G709-2012" title=""Interfaces for the Optical Transport Network (OTN)"">G709-2012</a>]. |
| 918 |
|
| 919 |
Multiplier (MT) usage is as defined in [<a href="./rfc6344" title=""Operating Virtual Concatenation (VCAT) and the Link Capacity Adjustment Scheme (LCAS) with Generalized Multi-Protocol Label Switching (GMPLS)"">RFC6344</a>] and [<a href="./rfc4328" title=""Generalized Multi-Protocol Label Switching (GMPLS) Signaling Extensions for G.709 Optical Transport Networks Control"">RFC4328</a>]. |
| 920 |
|
| 921 |
<span class="h3"><a class="selflink" id="section-6.4" href="#section-6.4">6.4</a>. Examples</span> |
| 922 |
|
| 923 |
The following examples are given in order to illustrate the label |
| 924 |
format described in <a href="#section-6.1">Section 6.1</a> of this document. |
| 925 |
|
| 926 |
(1) ODUk-to-OTUk Mapping: |
| 927 |
|
| 928 |
In this scenario, the downstream node along an LSP returns a label |
| 929 |
indicating that the ODUk (k=1, 2, 3, 4) is directly mapped into the |
| 930 |
corresponding OTUk. The following example label indicates an ODU1 |
| 931 |
mapped into OTU1. |
| 932 |
|
| 933 |
0 1 2 3 |
| 934 |
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 |
| 935 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 936 |
| TPN = 0 | Reserved | Length = 0 | |
| 937 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 938 |
|
| 939 |
(2) ODUj-to-ODUk Multiplexing: |
| 940 |
|
| 941 |
|
| 942 |
|
| 943 |
|
| 944 |
|
| 945 |
|
| 946 |
|
| 947 |
|
| 948 |
<span class="grey">Zhang, et al. Standards Track [Page 17]</span></pre> |
| 949 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span> |
| 950 |
<span class="grey"><a href="./rfc7139">RFC 7139</a> GMPLS Extensions for G.709 March 2014</span> |
| 951 |
|
| 952 |
|
| 953 |
In this scenario, this label indicates that an ODUj is multiplexed |
| 954 |
into several tributary slots of OPUk and then mapped into OTUk. Some |
| 955 |
instances are shown as follows: |
| 956 |
|
| 957 |
- ODU0-to-ODU2 Multiplexing: |
| 958 |
|
| 959 |
0 1 2 3 |
| 960 |
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 |
| 961 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 962 |
| TPN = 2 | Reserved | Length = 8 | |
| 963 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 964 |
|0 1 0 0 0 0 0 0| Padding Bits (0) | |
| 965 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 966 |
|
| 967 |
The label above indicates an ODU0 multiplexed into the second |
| 968 |
tributary slot of ODU2, wherein there are 8 TSs in ODU2 (i.e., the |
| 969 |
type of the tributary slot is 1.25 Gbps), and the TPN value is 2. |
| 970 |
|
| 971 |
- ODU1-to-ODU2 Multiplexing with 1.25 Gbps TS Granularity: |
| 972 |
|
| 973 |
0 1 2 3 |
| 974 |
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 |
| 975 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 976 |
| TPN = 1 | Reserved | Length = 8 | |
| 977 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 978 |
|0 1 0 1 0 0 0 0| Padding Bits (0) | |
| 979 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 980 |
|
| 981 |
The label above indicates an ODU1 multiplexed into the 2nd and the |
| 982 |
4th tributary slots of ODU2, wherein there are 8 TSs in ODU2 (i.e., |
| 983 |
the type of the tributary slot is 1.25 Gbps), and the TPN value is 1. |
| 984 |
|
| 985 |
- ODU2 into ODU3 Multiplexing with 2.5 Gbps TS Granularity: |
| 986 |
|
| 987 |
0 1 2 3 |
| 988 |
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 |
| 989 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 990 |
| TPN = 1 | Reserved | Length = 16 | |
| 991 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 992 |
|0 1 1 0 1 0 1 0 0 0 0 0 0 0 0 0| Padding Bits (0) | |
| 993 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |
| 994 |
|
| 995 |
The label above indicates an ODU2 multiplexed into the 2nd, 3rd, 5th, |
| 996 |
and 7th tributary slots of ODU3, wherein there are 16 TSs in ODU3 |
| 997 |
(i.e., the type of the tributary slot is 2.5 Gbps), and the TPN value |
| 998 |
is 1. |
| 999 |
|
| 1000 |
|
| 1001 |
|
| 1002 |
|
| 1003 |
|
| 1004 |
<span class="grey">Zhang, et al. Standards Track [Page 18]</span></pre> |
| 1005 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span> |
| 1006 |
<span class="grey"><a href="./rfc7139">RFC 7139</a> GMPLS Extensions for G.709 March 2014</span> |
| 1007 |
|
| 1008 |
|
| 1009 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Supporting Hitless Adjustment of ODUflex(GFP)</span> |
| 1010 |
|
| 1011 |
[<a id="ref-G7044">G7044</a>] describes the procedure of ODUflex(GFP) hitless resizing |
| 1012 |
using the Link Connection Resize (LCR) and Bandwidth Resize (BWR) |
| 1013 |
protocols in the OTN data plane. |
| 1014 |
|
| 1015 |
For the control plane, signaling messages are REQUIRED to initiate |
| 1016 |
the adjustment procedure. Sections <a href="#section-2.5">2.5</a> and <a href="#section-4.6.4">4.6.4</a> of [<a href="./rfc3209" title=""RSVP-TE: Extensions to RSVP for LSP Tunnels"">RFC3209</a>] |
| 1017 |
describe how the Shared Explicit (SE) style is used in the Traffic |
| 1018 |
Engineering (TE) network for bandwidth increasing and decreasing, |
| 1019 |
which is still applicable for triggering the ODUflex(GFP) adjustment |
| 1020 |
procedure in the data plane. |
| 1021 |
|
| 1022 |
Note that the SE style MUST be used at the beginning when creating a |
| 1023 |
resizable ODUflex connection (Signal Type = 21). Otherwise an error |
| 1024 |
with Error Code "Conflicting reservation style" MUST be generated |
| 1025 |
when performing bandwidth adjustment. |
| 1026 |
|
| 1027 |
- Bandwidth Increasing |
| 1028 |
|
| 1029 |
For the ingress node, in order to increase the bandwidth of an |
| 1030 |
ODUflex(GFP) connection, a Path message with SE style (keeping |
| 1031 |
Tunnel ID unchanged and assigning a new LSP ID) MUST be sent along |
| 1032 |
the path. |
| 1033 |
|
| 1034 |
The ingress node will trigger the BWR protocol when successful |
| 1035 |
completion of LCR protocols on every hop after the Resv message is |
| 1036 |
processed. On success of BWR, the ingress node SHOULD send a |
| 1037 |
PathTear message to delete the old control state (i.e., the |
| 1038 |
control state of the ODUflex(GFP) before resizing) on the control |
| 1039 |
plane. |
| 1040 |
|
| 1041 |
A downstream node receiving a Path message with SE style compares |
| 1042 |
the old Traffic Parameters (stored locally) with the new one |
| 1043 |
carried in the Path message to determine the number of TSs to be |
| 1044 |
added. After choosing and reserving new available TS(s), the |
| 1045 |
downstream node MUST send back a Resv message carrying both the |
| 1046 |
old and new GENERALIZED_LABEL objects in the SE flow descriptor. |
| 1047 |
|
| 1048 |
An upstream neighbor receiving a Resv message with an SE flow |
| 1049 |
descriptor MUST determine which TS(s) is/are added and trigger the |
| 1050 |
LCR protocol between itself and its downstream neighbor node. |
| 1051 |
|
| 1052 |
- Bandwidth Decreasing |
| 1053 |
|
| 1054 |
For the ingress node, a Path message with SE style SHOULD also be |
| 1055 |
sent for decreasing the ODUflex bandwidth. |
| 1056 |
|
| 1057 |
|
| 1058 |
|
| 1059 |
|
| 1060 |
<span class="grey">Zhang, et al. Standards Track [Page 19]</span></pre> |
| 1061 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span> |
| 1062 |
<span class="grey"><a href="./rfc7139">RFC 7139</a> GMPLS Extensions for G.709 March 2014</span> |
| 1063 |
|
| 1064 |
|
| 1065 |
The ingress node will trigger the BWR protocol when successful |
| 1066 |
completion of LCR handshake on every hop after Resv message is |
| 1067 |
processed. On success of BWR, the second step of LCR, i.e., link |
| 1068 |
connection decrease procedure will be started on every hop of the |
| 1069 |
connection. After decreasing the bandwidth, the ingress node |
| 1070 |
SHOULD send a ResvErr message to tear down the old control state. |
| 1071 |
|
| 1072 |
A downstream node receiving a Path message with SE style compares |
| 1073 |
the old Traffic Parameters with the new one carried in the Path |
| 1074 |
message to determine the number of TSs to be decreased. After |
| 1075 |
choosing TSs to be decreased, the downstream node MUST send back a |
| 1076 |
Resv message carrying both the old and new GENERALIZED_LABEL |
| 1077 |
objects in the SE flow descriptor. |
| 1078 |
|
| 1079 |
An upstream neighbor receiving a Resv message with an SE flow |
| 1080 |
descriptor MUST determine which TS(s) is/are decreased and trigger |
| 1081 |
the first step of the LCR protocol (i.e., LCR handshake) between |
| 1082 |
itself and its downstream neighbor node. |
| 1083 |
|
| 1084 |
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Operations, Administration, and Maintenance (OAM) Considerations</span> |
| 1085 |
|
| 1086 |
OTN OAM configuration could be done through either Network Management |
| 1087 |
Systems (NMSs) or the GMPLS control plane as defined in [<a href="#ref-TDM-OAM" title=""GMPLS RSVP-TE Extensions for SONET/SDH and OTN OAM Configuration"">TDM-OAM</a>]. |
| 1088 |
[<a href="./rfc4783" title=""GMPLS - Communication of Alarm Information"">RFC4783</a>] SHOULD be used for communication of alarm information in |
| 1089 |
GMPLS-based OTN. |
| 1090 |
|
| 1091 |
Management Information Bases (MIBs) may need be extended to read new |
| 1092 |
information (e.g., OTN-TDM Generalized Label and OTN-TDM |
| 1093 |
SENDER_TSPEC / FLOWSPEC) from the OTN devices. This is outside the |
| 1094 |
scope of this document. |
| 1095 |
|
| 1096 |
More information about the management aspects for GMPLS-based OTN, |
| 1097 |
refer to <a href="./rfc7062#section-5.7">Section 5.7 of [RFC7062]</a>. |
| 1098 |
|
| 1099 |
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Control-Plane Backward-Compatibility Considerations</span> |
| 1100 |
|
| 1101 |
As described in [<a href="./rfc7062" title=""Framework for GMPLS and PCE Control of G.709 Optical Transport Networks"">RFC7062</a>], since [<a href="./rfc4328" title=""Generalized Multi-Protocol Label Switching (GMPLS) Signaling Extensions for G.709 Optical Transport Networks Control"">RFC4328</a>] has been deployed in the |
| 1102 |
network for the nodes that support the 2001 revision of the G.709 |
| 1103 |
specification, control-plane backward compatibility SHOULD be taken |
| 1104 |
into consideration. More specifically: |
| 1105 |
|
| 1106 |
o Nodes supporting this document SHOULD support [<a href="./rfc7138" title=""Traffic Engineering Extensions to OSPF for GMPLS Control of Evolving G.709 Optical Transport Networks"">RFC7138</a>]. |
| 1107 |
|
| 1108 |
o Nodes supporting this document MAY support [<a href="./rfc4328" title=""Generalized Multi-Protocol Label Switching (GMPLS) Signaling Extensions for G.709 Optical Transport Networks Control"">RFC4328</a>] signaling. |
| 1109 |
|
| 1110 |
o A node supporting both sets of procedures (i.e., [<a href="./rfc4328" title=""Generalized Multi-Protocol Label Switching (GMPLS) Signaling Extensions for G.709 Optical Transport Networks Control"">RFC4328</a>] and |
| 1111 |
this document) is not required to signal an LSP using both |
| 1112 |
procedures, i.e., to act as a signaling version translator. |
| 1113 |
|
| 1114 |
|
| 1115 |
|
| 1116 |
<span class="grey">Zhang, et al. Standards Track [Page 20]</span></pre> |
| 1117 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span> |
| 1118 |
<span class="grey"><a href="./rfc7139">RFC 7139</a> GMPLS Extensions for G.709 March 2014</span> |
| 1119 |
|
| 1120 |
|
| 1121 |
o Ingress nodes that support both sets of procedures MAY select |
| 1122 |
which set of procedures to follow based on routing information or |
| 1123 |
local policy. |
| 1124 |
|
| 1125 |
o Per [<a href="./rfc3473" title=""Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions"">RFC3473</a>], nodes that do not support this document will |
| 1126 |
generate a PathErr message, with a "Routing problem/Switching |
| 1127 |
Type" indication. |
| 1128 |
|
| 1129 |
<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. Security Considerations</span> |
| 1130 |
|
| 1131 |
This document is a modification to [<a href="./rfc3473" title=""Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions"">RFC3473</a>] and [<a href="./rfc4328" title=""Generalized Multi-Protocol Label Switching (GMPLS) Signaling Extensions for G.709 Optical Transport Networks Control"">RFC4328</a>]; it only |
| 1132 |
differs in specific information communicated. As such, this document |
| 1133 |
introduces no new security considerations to the existing GMPLS |
| 1134 |
signaling protocols. Refer to [<a href="./rfc3473" title=""Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions"">RFC3473</a>] and [<a href="./rfc4328" title=""Generalized Multi-Protocol Label Switching (GMPLS) Signaling Extensions for G.709 Optical Transport Networks Control"">RFC4328</a>] for further |
| 1135 |
details of the specific security measures. Additionally, [<a href="./rfc5920" title=""Security Framework for MPLS and GMPLS Networks"">RFC5920</a>] |
| 1136 |
provides an overview of security vulnerabilities and protection |
| 1137 |
mechanisms for the GMPLS control plane. |
| 1138 |
|
| 1139 |
<span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>. IANA Considerations</span> |
| 1140 |
|
| 1141 |
IANA has made the following assignments in the "Class Types or C- |
| 1142 |
Types - 9 FLOWSPEC" and "Class Types or C-Types - 12 SENDER_TSPEC" |
| 1143 |
section of the "Resource Reservation Protocol (RSVP) Parameters" |
| 1144 |
registry located at <<a href="http://www.iana.org/assignments/rsvp-parameters">http://www.iana.org/assignments/</a> |
| 1145 |
<a href="http://www.iana.org/assignments/rsvp-parameters">rsvp-parameters</a>>. |
| 1146 |
|
| 1147 |
Value Description Reference |
| 1148 |
7 OTN-TDM [<a href="./rfc7139">RFC7139</a>] |
| 1149 |
|
| 1150 |
IANA maintains the "Generalized Multi-Protocol Label Switching |
| 1151 |
(GMPLS) Signaling Parameters" registry (see |
| 1152 |
<<a href="http://www.iana.org/assignments/gmpls-sig-parameters">http://www.iana.org/assignments/gmpls-sig-parameters</a>>). The |
| 1153 |
"Generalized PIDs (G-PID)" subregistry is included in this registry, |
| 1154 |
which is extended and updated by this document as detailed below. |
| 1155 |
|
| 1156 |
|
| 1157 |
|
| 1158 |
|
| 1159 |
|
| 1160 |
|
| 1161 |
|
| 1162 |
|
| 1163 |
|
| 1164 |
|
| 1165 |
|
| 1166 |
|
| 1167 |
|
| 1168 |
|
| 1169 |
|
| 1170 |
|
| 1171 |
|
| 1172 |
<span class="grey">Zhang, et al. Standards Track [Page 21]</span></pre> |
| 1173 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span> |
| 1174 |
<span class="grey"><a href="./rfc7139">RFC 7139</a> GMPLS Extensions for G.709 March 2014</span> |
| 1175 |
|
| 1176 |
|
| 1177 |
Value Type Technology Reference |
| 1178 |
===== ====================== ========== ========= |
| 1179 |
47 G.709 ODU-2.5G G.709 ODUk [<a href="./rfc4328" title=""Generalized Multi-Protocol Label Switching (GMPLS) Signaling Extensions for G.709 Optical Transport Networks Control"">RFC4328</a>] |
| 1180 |
(IANA updated the Type field) [<a href="./rfc7139">RFC7139</a>] |
| 1181 |
56 SBCON/ESCON G.709 ODUk, [<a href="./rfc4328" title=""Generalized Multi-Protocol Label Switching (GMPLS) Signaling Extensions for G.709 Optical Transport Networks Control"">RFC4328</a>] |
| 1182 |
(IANA updated the Type field) Lambda, Fiber [<a href="./rfc7139">RFC7139</a>] |
| 1183 |
59 Framed GFP G.709 ODUk [<a href="./rfc7139">RFC7139</a>] |
| 1184 |
60 STM-1 G.709 ODUk [<a href="./rfc7139">RFC7139</a>] |
| 1185 |
61 STM-4 G.709 ODUk [<a href="./rfc7139">RFC7139</a>] |
| 1186 |
62 InfiniBand G.709 ODUflex [<a href="./rfc7139">RFC7139</a>] |
| 1187 |
63 SDI (Serial Digital Interface) G.709 ODUk [<a href="./rfc7139">RFC7139</a>] |
| 1188 |
64 SDI/1.001 G.709 ODUk [<a href="./rfc7139">RFC7139</a>] |
| 1189 |
65 DVB_ASI G.709 ODUk [<a href="./rfc7139">RFC7139</a>] |
| 1190 |
66 G.709 ODU-1.25G G.709 ODUk [<a href="./rfc7139">RFC7139</a>] |
| 1191 |
67 G.709 ODU-any G.709 ODUk [<a href="./rfc7139">RFC7139</a>] |
| 1192 |
68 Null Test G.709 ODUk [<a href="./rfc7139">RFC7139</a>] |
| 1193 |
69 Random Test G.709 ODUk [<a href="./rfc7139">RFC7139</a>] |
| 1194 |
70 64B/66B GFP-F Ethernet G.709 ODUk [<a href="./rfc7139">RFC7139</a>] |
| 1195 |
|
| 1196 |
The new G-PIDs are shown in the TC MIB managed by IANA at |
| 1197 |
<<a href="https://www.iana.org/assignments/ianagmplstc-mib">https://www.iana.org/assignments/ianagmplstc-mib</a>> as follows: |
| 1198 |
|
| 1199 |
g709FramedGFP(59), |
| 1200 |
g709STM1(60), |
| 1201 |
g709STM4(61), |
| 1202 |
g709InfiniBand(62), |
| 1203 |
g709SDI(63), |
| 1204 |
g709SDI1point001(64), |
| 1205 |
g709DVBASI(65), |
| 1206 |
g709ODU1point25G(66), |
| 1207 |
g709ODUAny(67), |
| 1208 |
g709NullTest(68), |
| 1209 |
g709RandomTest(69), |
| 1210 |
g709GFPFEthernet(70) |
| 1211 |
|
| 1212 |
Note that IANA has not changed the names of the objects in this MIB |
| 1213 |
module with the values 47 and 56. |
| 1214 |
|
| 1215 |
|
| 1216 |
|
| 1217 |
|
| 1218 |
|
| 1219 |
|
| 1220 |
|
| 1221 |
|
| 1222 |
|
| 1223 |
|
| 1224 |
|
| 1225 |
|
| 1226 |
|
| 1227 |
|
| 1228 |
<span class="grey">Zhang, et al. Standards Track [Page 22]</span></pre> |
| 1229 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span> |
| 1230 |
<span class="grey"><a href="./rfc7139">RFC 7139</a> GMPLS Extensions for G.709 March 2014</span> |
| 1231 |
|
| 1232 |
|
| 1233 |
IANA has defined an "OTN Signal Type" subregistry to the "Generalized |
| 1234 |
Multi-Protocol Label Switching (GMPLS) Signaling Parameters" |
| 1235 |
registry: |
| 1236 |
|
| 1237 |
Value Signal Type Reference |
| 1238 |
----- ----------- --------- |
| 1239 |
0 Not significant [<a href="./rfc4328" title=""Generalized Multi-Protocol Label Switching (GMPLS) Signaling Extensions for G.709 Optical Transport Networks Control"">RFC4328</a>] |
| 1240 |
1 ODU1 (i.e., 2.5 Gbps) [<a href="./rfc4328" title=""Generalized Multi-Protocol Label Switching (GMPLS) Signaling Extensions for G.709 Optical Transport Networks Control"">RFC4328</a>] |
| 1241 |
2 ODU2 (i.e., 10 Gbps) [<a href="./rfc4328" title=""Generalized Multi-Protocol Label Switching (GMPLS) Signaling Extensions for G.709 Optical Transport Networks Control"">RFC4328</a>] |
| 1242 |
3 ODU3 (i.e., 40 Gbps) [<a href="./rfc4328" title=""Generalized Multi-Protocol Label Switching (GMPLS) Signaling Extensions for G.709 Optical Transport Networks Control"">RFC4328</a>] |
| 1243 |
4 ODU4 (i.e., 100 Gbps) [<a href="./rfc7139">RFC7139</a>] |
| 1244 |
5 Unassigned [<a href="./rfc4328" title=""Generalized Multi-Protocol Label Switching (GMPLS) Signaling Extensions for G.709 Optical Transport Networks Control"">RFC4328</a>] |
| 1245 |
6 Och at 2.5 Gbps [<a href="./rfc4328" title=""Generalized Multi-Protocol Label Switching (GMPLS) Signaling Extensions for G.709 Optical Transport Networks Control"">RFC4328</a>] |
| 1246 |
7 OCh at 10 Gbps [<a href="./rfc4328" title=""Generalized Multi-Protocol Label Switching (GMPLS) Signaling Extensions for G.709 Optical Transport Networks Control"">RFC4328</a>] |
| 1247 |
8 OCh at 40 Gbps [<a href="./rfc4328" title=""Generalized Multi-Protocol Label Switching (GMPLS) Signaling Extensions for G.709 Optical Transport Networks Control"">RFC4328</a>] |
| 1248 |
9 OCh at 100 Gbps [<a href="./rfc7139">RFC7139</a>] |
| 1249 |
10 ODU0 (i.e., 1.25 Gbps) [<a href="./rfc7139">RFC7139</a>] |
| 1250 |
11 ODU2e (i.e., 10 Gbps for FC1200 [<a href="./rfc7139">RFC7139</a>] |
| 1251 |
and GE LAN) |
| 1252 |
12-19 Unassigned [<a href="./rfc7139">RFC7139</a>] |
| 1253 |
20 ODUflex(CBR) (i.e., 1.25*N Gbps) [<a href="./rfc7139">RFC7139</a>] |
| 1254 |
21 ODUflex(GFP-F), resizable [<a href="./rfc7139">RFC7139</a>] |
| 1255 |
(i.e., 1.25*N Gbps) |
| 1256 |
22 ODUflex(GFP-F), non-resizable [<a href="./rfc7139">RFC7139</a>] |
| 1257 |
(i.e., 1.25*N Gbps) |
| 1258 |
23-255 Unassigned [<a href="./rfc7139">RFC7139</a>] |
| 1259 |
|
| 1260 |
New values are to be assigned via Standards Action as defined in |
| 1261 |
[<a href="./rfc5226" title="">RFC5226</a>]. |
| 1262 |
|
| 1263 |
<span class="h2"><a class="selflink" id="section-12" href="#section-12">12</a>. References</span> |
| 1264 |
|
| 1265 |
<span class="h3"><a class="selflink" id="section-12.1" href="#section-12.1">12.1</a>. Normative References</span> |
| 1266 |
|
| 1267 |
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate |
| 1268 |
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997. |
| 1269 |
|
| 1270 |
[<a id="ref-RFC2205">RFC2205</a>] Braden, R., Ed., Zhang, L., Berson, S., Herzog, S., and |
| 1271 |
S. Jamin, "Resource ReSerVation Protocol (RSVP) -- |
| 1272 |
Version 1 Functional Specification", <a href="./rfc2205">RFC 2205</a>, September |
| 1273 |
1997. |
| 1274 |
|
| 1275 |
[<a id="ref-RFC2210">RFC2210</a>] Wroclawski, J., "The Use of RSVP with IETF Integrated |
| 1276 |
Services", <a href="./rfc2210">RFC 2210</a>, September 1997. |
| 1277 |
|
| 1278 |
[<a id="ref-RFC3209">RFC3209</a>] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V., |
| 1279 |
and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP |
| 1280 |
Tunnels", <a href="./rfc3209">RFC 3209</a>, December 2001. |
| 1281 |
|
| 1282 |
|
| 1283 |
|
| 1284 |
<span class="grey">Zhang, et al. Standards Track [Page 23]</span></pre> |
| 1285 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span> |
| 1286 |
<span class="grey"><a href="./rfc7139">RFC 7139</a> GMPLS Extensions for G.709 March 2014</span> |
| 1287 |
|
| 1288 |
|
| 1289 |
[<a id="ref-RFC3471">RFC3471</a>] Berger, L., Ed., "Generalized Multi-Protocol Label |
| 1290 |
Switching (GMPLS) Signaling Functional Description", <a href="./rfc3471">RFC</a> |
| 1291 |
<a href="./rfc3471">3471</a>, January 2003. |
| 1292 |
|
| 1293 |
[<a id="ref-RFC3473">RFC3473</a>] Berger, L., Ed., "Generalized Multi-Protocol Label |
| 1294 |
Switching (GMPLS) Signaling Resource ReserVation |
| 1295 |
Protocol-Traffic Engineering (RSVP-TE) Extensions", <a href="./rfc3473">RFC</a> |
| 1296 |
<a href="./rfc3473">3473</a>, January 2003. |
| 1297 |
|
| 1298 |
[<a id="ref-RFC4328">RFC4328</a>] Papadimitriou, D., Ed., "Generalized Multi-Protocol Label |
| 1299 |
Switching (GMPLS) Signaling Extensions for G.709 Optical |
| 1300 |
Transport Networks Control", <a href="./rfc4328">RFC 4328</a>, January 2006. |
| 1301 |
|
| 1302 |
[<a id="ref-RFC4506">RFC4506</a>] Eisler, M., Ed., "XDR: External Data Representation |
| 1303 |
Standard", STD 67, <a href="./rfc4506">RFC 4506</a>, May 2006. |
| 1304 |
|
| 1305 |
[<a id="ref-RFC4783">RFC4783</a>] Berger, L., Ed., "GMPLS - Communication of Alarm |
| 1306 |
Information", <a href="./rfc4783">RFC 4783</a>, December 2006. |
| 1307 |
|
| 1308 |
[<a id="ref-RFC6344">RFC6344</a>] Bernstein, G., Ed., Caviglia, D., Rabbat, R., and H. van |
| 1309 |
Helvoort, "Operating Virtual Concatenation (VCAT) and the |
| 1310 |
Link Capacity Adjustment Scheme (LCAS) with Generalized |
| 1311 |
Multi-Protocol Label Switching (GMPLS)", <a href="./rfc6344">RFC 6344</a>, August |
| 1312 |
2011. |
| 1313 |
|
| 1314 |
[<a id="ref-RFC7138">RFC7138</a>] Ceccarelli, D., Ed., Zhang, F., Belotti, S., Rao, R., and |
| 1315 |
J. Drake, "Traffic Engineering Extensions to OSPF for |
| 1316 |
GMPLS Control of Evolving G.709 Optical Transport |
| 1317 |
Networks", <a href="./rfc7138">RFC 7138</a>, March 2014. |
| 1318 |
|
| 1319 |
[<a id="ref-G709-2012">G709-2012</a>] ITU-T, "Interfaces for the Optical Transport Network |
| 1320 |
(OTN)", G.709/Y.1331 Recommendation, February 2012. |
| 1321 |
|
| 1322 |
[<a id="ref-G7044">G7044</a>] ITU-T, "Hitless adjustment of ODUflex", G.7044/Y.1347, |
| 1323 |
October 2011. |
| 1324 |
|
| 1325 |
[<a id="ref-G7041">G7041</a>] ITU-T, "Generic framing procedure", G.7041/Y.1303, April |
| 1326 |
2011. |
| 1327 |
|
| 1328 |
[<a id="ref-IEEE">IEEE</a>] "IEEE Standard for Binary Floating-Point Arithmetic", |
| 1329 |
ANSI/IEEE Standard 754-1985, Institute of Electrical and |
| 1330 |
Electronics Engineers, August 1985. |
| 1331 |
|
| 1332 |
<span class="h3"><a class="selflink" id="section-12.2" href="#section-12.2">12.2</a>. Informative References</span> |
| 1333 |
|
| 1334 |
[<a id="ref-RFC5226">RFC5226</a>] Narten, T. and H. Alvestrand, "Guidelines for Writing an |
| 1335 |
IANA Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>, <a href="./rfc5226">RFC 5226</a>, |
| 1336 |
May 2008. |
| 1337 |
|
| 1338 |
|
| 1339 |
|
| 1340 |
<span class="grey">Zhang, et al. Standards Track [Page 24]</span></pre> |
| 1341 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span> |
| 1342 |
<span class="grey"><a href="./rfc7139">RFC 7139</a> GMPLS Extensions for G.709 March 2014</span> |
| 1343 |
|
| 1344 |
|
| 1345 |
[<a id="ref-RFC5920">RFC5920</a>] Fang, L., Ed., "Security Framework for MPLS and GMPLS |
| 1346 |
Networks", <a href="./rfc5920">RFC 5920</a>, July 2010. |
| 1347 |
|
| 1348 |
[<a id="ref-RFC7062">RFC7062</a>] Zhang, F., Ed., Li, D., Li, H., Belotti, S., and D. |
| 1349 |
Ceccarelli, "Framework for GMPLS and PCE Control of G.709 |
| 1350 |
Optical Transport Networks", <a href="./rfc7062">RFC 7062</a>, November 2013. |
| 1351 |
|
| 1352 |
[<a id="ref-RFC7096">RFC7096</a>] Belotti, S., Ed., Grandi, P., Ceccarelli, D., Ed., |
| 1353 |
Caviglia, D., Zhang, F., and D. Li, "Evaluation of |
| 1354 |
Existing GMPLS Encoding against G.709v3 Optical Transport |
| 1355 |
Networks (OTNs)", <a href="./rfc7096">RFC 7096</a>, January 2014. |
| 1356 |
|
| 1357 |
[<a id="ref-TDM-OAM">TDM-OAM</a>] Kern, A., and A. Takacs, "GMPLS RSVP-TE Extensions for |
| 1358 |
SONET/SDH and OTN OAM Configuration", Work in Progress, |
| 1359 |
November 2013. |
| 1360 |
|
| 1361 |
<span class="h2"><a class="selflink" id="section-13" href="#section-13">13</a>. Contributors</span> |
| 1362 |
|
| 1363 |
Yi Lin |
| 1364 |
Huawei Technologies |
| 1365 |
F3-5-B R&D Center, Huawei Base |
| 1366 |
Bantian, Longgang District |
| 1367 |
Shenzhen 518129 |
| 1368 |
P.R. China |
| 1369 |
Phone: +86-755-28972914 |
| 1370 |
EMail: [email protected] |
| 1371 |
|
| 1372 |
Yunbin Xu |
| 1373 |
China Academy of Telecommunication Research of MII |
| 1374 |
11 Yue Tan Nan Jie |
| 1375 |
Beijing |
| 1376 |
P.R. China |
| 1377 |
Phone: +86-10-68094134 |
| 1378 |
EMail: [email protected] |
| 1379 |
|
| 1380 |
Pietro Grandi |
| 1381 |
Alcatel-Lucent |
| 1382 |
Optics CTO |
| 1383 |
Via Trento 30 20059 Vimercate |
| 1384 |
Milano |
| 1385 |
Italy |
| 1386 |
Phone: +39 039 6864930 |
| 1387 |
EMail: [email protected] |
| 1388 |
|
| 1389 |
|
| 1390 |
|
| 1391 |
|
| 1392 |
|
| 1393 |
|
| 1394 |
|
| 1395 |
|
| 1396 |
<span class="grey">Zhang, et al. Standards Track [Page 25]</span></pre> |
| 1397 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span> |
| 1398 |
<span class="grey"><a href="./rfc7139">RFC 7139</a> GMPLS Extensions for G.709 March 2014</span> |
| 1399 |
|
| 1400 |
|
| 1401 |
Diego Caviglia |
| 1402 |
Ericsson |
| 1403 |
Via A. Negrone 1/A |
| 1404 |
Genova - Sestri Ponente |
| 1405 |
Italy |
| 1406 |
EMail: [email protected] |
| 1407 |
|
| 1408 |
Rajan Rao |
| 1409 |
Infinera Corporation |
| 1410 |
169, Java Drive |
| 1411 |
Sunnyvale, CA 94089 |
| 1412 |
USA |
| 1413 |
EMail: [email protected] |
| 1414 |
|
| 1415 |
John E Drake |
| 1416 |
Juniper |
| 1417 |
EMail: [email protected] |
| 1418 |
|
| 1419 |
Igor Bryskin |
| 1420 |
Adva Optical |
| 1421 |
EMail: [email protected] |
| 1422 |
|
| 1423 |
Jonathan Sadler, Tellabs |
| 1424 |
EMail: [email protected] |
| 1425 |
|
| 1426 |
Kam LAM, Alcatel-Lucent |
| 1427 |
EMail: [email protected] |
| 1428 |
|
| 1429 |
Francesco Fondelli, Ericsson |
| 1430 |
EMail: [email protected] |
| 1431 |
|
| 1432 |
Lyndon Ong, Ciena |
| 1433 |
EMail: [email protected] |
| 1434 |
|
| 1435 |
Biao Lu, infinera |
| 1436 |
EMail: [email protected] |
| 1437 |
|
| 1438 |
<span class="h2"><a class="selflink" id="section-14" href="#section-14">14</a>. Acknowledgments</span> |
| 1439 |
|
| 1440 |
The authors would like to thank Lou Berger, Deborah Brungard, and |
| 1441 |
Xiaobing Zi for their useful comments regarding this document. |
| 1442 |
|
| 1443 |
|
| 1444 |
|
| 1445 |
|
| 1446 |
|
| 1447 |
|
| 1448 |
|
| 1449 |
|
| 1450 |
|
| 1451 |
|
| 1452 |
<span class="grey">Zhang, et al. Standards Track [Page 26]</span></pre> |
| 1453 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span> |
| 1454 |
<span class="grey"><a href="./rfc7139">RFC 7139</a> GMPLS Extensions for G.709 March 2014</span> |
| 1455 |
|
| 1456 |
|
| 1457 |
Authors' Addresses |
| 1458 |
|
| 1459 |
Fatai Zhang (editor) |
| 1460 |
Huawei Technologies |
| 1461 |
F3-5-B R&D Center, Huawei Base |
| 1462 |
Bantian, Longgang District |
| 1463 |
Shenzhen 518129 |
| 1464 |
P.R. China |
| 1465 |
Phone: +86-755-28972912 |
| 1466 |
EMail: [email protected] |
| 1467 |
|
| 1468 |
|
| 1469 |
Guoying Zhang |
| 1470 |
China Academy of Telecommunication Research of MII |
| 1471 |
11 Yue Tan Nan Jie |
| 1472 |
Beijing |
| 1473 |
P.R. China |
| 1474 |
Phone: +86-10-68094272 |
| 1475 |
EMail: [email protected] |
| 1476 |
|
| 1477 |
|
| 1478 |
Sergio Belotti |
| 1479 |
Alcatel-Lucent |
| 1480 |
Optics CTO |
| 1481 |
Via Trento 30 20059 Vimercate |
| 1482 |
Milano |
| 1483 |
Italy |
| 1484 |
Phone: +39 039 6863033 |
| 1485 |
EMail: [email protected] |
| 1486 |
|
| 1487 |
|
| 1488 |
Daniele Ceccarelli |
| 1489 |
Ericsson |
| 1490 |
Via A. Negrone 1/A |
| 1491 |
Genova - Sestri Ponente |
| 1492 |
Italy |
| 1493 |
EMail: [email protected] |
| 1494 |
|
| 1495 |
|
| 1496 |
Khuzema Pithewan |
| 1497 |
Infinera Corporation |
| 1498 |
169, Java Drive |
| 1499 |
Sunnyvale, CA 94089 |
| 1500 |
USA |
| 1501 |
EMail: [email protected] |
| 1502 |
|
| 1503 |
|
| 1504 |
|
| 1505 |
|
| 1506 |
|
| 1507 |
|
| 1508 |
Zhang, et al. Standards Track [Page 27] |
| 1509 |
</pre> |