1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
|
<pre>Internet Engineering Task Force (IETF) D. Papadimitriou
Request for Comments: 6003 Alcatel-Lucent
Updates: <a href="./rfc3471">3471</a>, <a href="./rfc3473">3473</a> October 2010
Category: Standards Track
ISSN: 2070-1721
<span class="h1">Ethernet Traffic Parameters</span>
Abstract
This document describes the support of Metro Ethernet Forum (MEF)
Ethernet traffic parameters as described in MEF10.1 when using
Generalized Multi-Protocol Label Switching (GMPLS) Resource
ReSerVation Protocol - Traffic Engineering (RSVP-TE) signaling.
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 <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="http://www.rfc-editor.org/info/rfc6003">http://www.rfc-editor.org/info/rfc6003</a>.
Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) 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.
<span class="grey">Papadimitriou Standards Track [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc6003">RFC 6003</a> Ethernet Traffic Parameters October 2010</span>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
Per [<a href="./rfc3471" title=""Generalized Multi-Protocol Label Switching (GMPLS) Signaling Functional Description"">RFC3471</a>], Generalized Multi-Protocol Label Switching (GMPLS)
allows the inclusion of technology-specific parameters in signaling.
This document introduces Ethernet SENDER_TSPEC and FLOWSPEC-specific
objects in support of Metro Ethernet Forum (MEF) Ethernet traffic
parameters as specified in [<a href="#ref-MEF10.1" title=""Ethernet Services Attributes Phase 2"">MEF10.1</a>] and ITU-T Ethernet Service
Switching as discussed in [<a href="./rfc6004" title=""Generalized MPLS (GMPLS) Support for Metro Ethernet Forum and G.8011 Ethernet Services"">RFC6004</a>]. For example:
o For Ethernet Private Line (EPL) services [<a href="#ref-MEF6" title=""Ethernet Services Definitions - Phase I"">MEF6</a>], these traffic
parameters are applicable to each Ethernet Virtual Connection
(EVC) crossing a given port.
o For Ethernet Virtual Private Line (EVPL) services [<a href="#ref-MEF6" title=""Ethernet Services Definitions - Phase I"">MEF6</a>], these
traffic parameters are applicable per Ethernet Virtual Connection
(EVC) with a single or multiple Class of Service (CoS),
independent of its associated Virtual LAN ID (VID) or set of VIDs.
Association between EVC and VIDs is detailed in [<a href="#ref-MEF10.1" title=""Ethernet Services Attributes Phase 2"">MEF10.1</a>]. The
format and encoding of the VID (or set of VIDs) is documented in a
companion document [<a href="./rfc6004" title=""Generalized MPLS (GMPLS) Support for Metro Ethernet Forum and G.8011 Ethernet Services"">RFC6004</a>].
This does not preclude broader usage of the Ethernet SENDER_TSPEC and
FLOWSPEC-specific objects specified this document. For instance,
they may also be used for signaling Ethernet Label Switched Paths
(LSPs), in the Generalized Label Request (see [<a href="./rfc3471" title=""Generalized Multi-Protocol Label Switching (GMPLS) Signaling Functional Description"">RFC3471</a>]), the
Switching Type field is set to Layer 2 Switching Capability (L2SC)
and the LSP Encoding Type field to Ethernet.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Conventions Used in This Document</span>
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 <a href="./rfc2119">RFC 2119</a> [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>].
Moreover, the reader is assumed to be familiar with the terminology
in [<a href="#ref-MEF10.1" title=""Ethernet Services Attributes Phase 2"">MEF10.1</a>] as well as in [<a href="./rfc3471" title=""Generalized Multi-Protocol Label Switching (GMPLS) Signaling Functional Description"">RFC3471</a>] and [<a href="./rfc3473" title=""Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol- Traffic Engineering (RSVP-TE) Extensions"">RFC3473</a>].
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Overview</span>
In GMPLS RSVP-TE [<a href="./rfc3473" title=""Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol- Traffic Engineering (RSVP-TE) Extensions"">RFC3473</a>], the SENDER_TSPEC object is used on a Path
message to indicate the bandwidth that is requested for the LSP being
established, and the FLOWSPEC object is used on a Resv message to
indicate the bandwidth actually reserved for the LSP. The Ethernet
SENDER_TSPEC/FLOWSPEC object includes the Ethernet link type
(switching granularity) of the requested LSP and the MTU value for
<span class="grey">Papadimitriou Standards Track [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc6003">RFC 6003</a> Ethernet Traffic Parameters October 2010</span>
the LSP. Other information about the requested bandwidth
characteristics of the LSP are carried in the Bandwidth Profile as a
TLV within the Ethernet SENDER_TSPEC/FLOWSPEC object.
The Ethernet SENDER_TSPEC/FLOWSPEC object includes the Ethernet link
type (switching granularity) of the requested LSP and the MTU value
for the LSP.
The Bandwidth Profile defines the set of traffic parameters
applicable to a sequence of Service Frames, referred to as bandwidth
profile parameters (as specified in [<a href="#ref-MEF10.1" title=""Ethernet Services Attributes Phase 2"">MEF10.1</a>]):
o Committed Rate: indicates the rate at which traffic commits to be
sent to the Ethernet LSP. The committed rate is described in
terms of the CIR (Committed Information Rate) and CBS (Committed
Burst Size) traffic parameters.
o CIR is defined as the average rate (in bytes per unit of time)
up to which the network is committed to transfer frames and
meets its performance objectives.
o CBS defines a limit on the maximum number of information units
(e.g., bytes) available for a burst of frames sent at the
interface speed to remain CIR-conformant.
o Excess Rate: indicates the extent by which the traffic sent on an
Ethernet LSP exceeds the committed rate. The Excess Rate is
described in terms of the EIR (Excess Information Rate) and EBS
(Excess Burst Size) traffic parameters.
o EIR is defined as the average rate (in bytes per unit of time),
in excess of the CIR, up to which the network may transfer
frames without any performance objectives.
o EBS defines a limit on the maximum number of information units
(e.g., bytes) available for a burst of frames sent at the
interface speed to remain EIR-conformant.
o Color mode (CM): indicates whether the "color-aware" or "color-
blind" property is employed by the bandwidth profile.
o Coupling flag (CF): allows the choice between two modes of
operation of the rate enforcement algorithm.
<span class="grey">Papadimitriou Standards Track [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc6003">RFC 6003</a> Ethernet Traffic Parameters October 2010</span>
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Ethernet SENDER_TSPEC Object</span>
The Ethernet SENDER_TSPEC object (Class-Num = 12, Class-Type = 6) 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length | Class-Num (12)| C-Type (6) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Switching Granularity | MTU |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
~ TLVs ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Switching Granularity (SG): 16 bits
This field indicates the type of link that comprises the requested
Ethernet LSP.
The permitted Ethernet Link Type values are:
Value Switching Granularity
----- ---------------------
0 Provided in signaling. See [<a href="./rfc6004" title=""Generalized MPLS (GMPLS) Support for Metro Ethernet Forum and G.8011 Ethernet Services"">RFC6004</a>].
1 Ethernet Port (for port-based service)
2 Ethernet Frame (for EVC-based service)
255 Reserved
Values 0 to 2 are specified by the present document. Values 3
through 239 are to be assigned by IANA via Standards Action
[<a href="./rfc5226" title="">RFC5226</a>]. Value 255 is reserved by the present document (its
Length is to be determined by the RFC that will specify it).
Values 240 through 254 are reserved for vendor-specific use.
Values 256 through 65535 are not assigned at this time.
MTU: 16 bits
This is a two-octet value indicating the MTU in octets.
The MTU field MUST NOT take a value smaller than 46 bytes for
Ethernet v2 [<a href="#ref-ETHv2" title=""The Ethernet -- A Local Area Network: Data Link Layer and Physical Layer Specifications"">ETHv2</a>] and 38 bytes for IEEE 802.3 [<a href="#ref-IEEE802.3">IEEE802.3</a>].
<span class="grey">Papadimitriou Standards Track [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc6003">RFC 6003</a> Ethernet Traffic Parameters October 2010</span>
TLV (Type-Length-Value):
The Ethernet SENDER_TSPEC object MUST include at least one TLV and
MAY include more than one TLV.
Each TLV MUST 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 ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 16 bits
Defined values are:
Type Length Format Description
------------------------------------------------------
0 - Reserved Reserved value
1 - Reserved Reserved value
2 24 see <a href="#section-3.1">Section 3.1</a> Ethernet Bandwidth
Profile [<a href="#ref-MEF10.1" title=""Ethernet Services Attributes Phase 2"">MEF10.1</a>]
3 8 [<a href="./rfc6004" title=""Generalized MPLS (GMPLS) Support for Metro Ethernet Forum and G.8011 Ethernet Services"">RFC6004</a>] Layer 2 Control
Protocol (L2CP)
255 - Reserved Reserved value
Values 0, 1, and 255 are reserved by the present document. Values
2 and 3 are specified by the present document.
Values 4 through 239 are to be assigned by IANA via Standards
Action [<a href="./rfc5226" title="">RFC5226</a>].
Values 240 through 254 are reserved for vendor-specific use.
Values 256 through 65535 are not assigned at this time.
Length: 16 bits
Indicates the length in bytes of the whole TLV including the Type
and Length fields. A value field whose length is not a multiple
of four MUST be zero-padded (with trailing zeros) so that the TLV
is four-octet aligned.
<span class="grey">Papadimitriou Standards Track [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc6003">RFC 6003</a> Ethernet Traffic Parameters October 2010</span>
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Ethernet Bandwidth Profile TLV</span>
The Type 2 TLV specifies the Ethernet Bandwidth Profile (BW profile).
It defines an upper bound on the volume of the expected service
frames belonging to a particular Ethernet service instance. The
Ethernet SENDER_TSPEC object MAY include more than one Ethernet
Bandwidth Profile TLV.
The Type 2 TLV has the following format:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Profile | Index | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| CIR |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| CBS |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| EIR |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| EBS |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Profile: 8 bits
This field is defined as a bit vector of binary flags. The
following flags are defined:
Flag 1 (bit 0): Coupling Flag (CF)
Flag 2 (bit 1): Color Mode (CM)
Where bit 0 is the low order bit. Other flags are reserved, they
SHOULD be set to zero when sent, and SHOULD be ignored when
received.
A flag is set to value 1 to indicate that the corresponding
metering profile is requested.
The Flag 1 (CF) allows the choice between two modes of operation
of the rate enforcement algorithm.
The Flag 2 (CM) indicates whether the color-aware or color-blind
property [<a href="#ref-MEF10.2" title=""Ethernet Services Attributes Phase 2"">MEF10.2</a>] is employed by the bandwidth profile. When
Flag 2 is set to value 0 (1), the bandwidth profile algorithm is
said to be in color-blind (color-aware) mode.
<span class="grey">Papadimitriou Standards Track [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc6003">RFC 6003</a> Ethernet Traffic Parameters October 2010</span>
Index: 8 bits
The Index field is used to reference bandwidth allocated for a
given traffic class in case a multiple-class LSP is being
requested. The Index field value MUST correspond to at least one
of the Class-Type values included either in the CLASSTYPE object
[<a href="./rfc4124" title=""Protocol Extensions for Support of Diffserv-aware MPLS Traffic Engineering"">RFC4124</a>] or in the EXTENDED_CLASSTYPE object [<a href="#ref-MCOS" title=""Extensions for Differentiated Services-aware Traffic Engineered LSPs"">MCOS</a>].
A given index value j can be associated to at most N Class-Type
values CTi (i =< N) of the EXTENDED_CLASSTYPE object. This
association applies when a set of one or more CTIs maps to a
single (shared) BW profile. An example of value setting consists
in assigning an arbitrary value comprised within the range
[0x08,0xF8] associated to a set of CTi, the values in the range
[0xF8,0xFF] being selected for reserved sets. This allows mapping
to one of 248 predefined CTi sets.
A given index value j can be associated to a single CTi (1:1
correspondence). In this case, the index value setting consists
in assigning the 3 least significant bits of the Index field
itself to the CTi value itself (comprised in the range
[0x00,0x07]). This applies in case a single CTi maps a single
(dedicated) BW profile or multiple (dedicated) BW profiles. In
the former case, the Ethernet SENDER_TSPEC object includes a
single Ethernet Bandwidth Profile TLV. In the latter case, the
Ethernet SENDER_TSPEC includes a set of more than one Ethernet
Bandwidth Profile TLVs (whose respective index value is associated
to a single CTi value).
Note that the current specification allows for combining shared
and dedicated BW profiles to the same LSP. That is, an Ethernet
SENDER_TSPEC object MAY include multiple Ethernet Bandwidth
Profile TLVs whose respective index can be associated on a 1:1
basis to a single CTi or to a set of multiple CTis.
For each subobject of the EXTENDED_CLASSTYPE object [<a href="#ref-MCOS" title=""Extensions for Differentiated Services-aware Traffic Engineered LSPs"">MCOS</a>]:
o Each CTi value SHOULD correspond 1:1 to the MEF Customer
Edge VLAN CoS (CE-VLAN CoS).
o The BW requested per CTi field MAY be used for bandwidth
accounting purposes.
By default, the value of the Index field MUST be set to 0.
<span class="grey">Papadimitriou Standards Track [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc6003">RFC 6003</a> Ethernet Traffic Parameters October 2010</span>
Reserved: 16 bits
These bits SHOULD be set to zero when sent and MUST be ignored
when received.
CIR (Committed Information Rate): 32 bits
The value of the CIR is in units of bytes per second. The CIR is
encoded as a 32-bit IEEE single-precision floating-point number
(see [<a href="./rfc4506" title=""XDR: External Data Representation Standard"">RFC4506</a>]).
The CIR value MUST be greater than or equal to 0.
CBS (Committed Burst Size): 32 bits
The value of the CBS is in units of bytes. The CBS is encoded as
a 32-bit IEEE single-precision floating-point number (see
[<a href="./rfc4506" title=""XDR: External Data Representation Standard"">RFC4506</a>]).
When CIR is strictly greater than 0 (CIR > 0), the CBS MUST be
greater than or equal to the maximum frame size.
EIR (Excess Information Rate): 32 bits
The value of the EIR is in units of bytes per second. The EIR is
encoded as a 32-bit IEEE single-precision floating-point number
(see [<a href="./rfc4506" title=""XDR: External Data Representation Standard"">RFC4506</a>]).
The EIR value MUST be greater than or equal to 0.
EBS (Excess Burst Size): 32 bits
The value of the EBS is in units of bytes. The EBS is encoded as
a 32-bit IEEE single-precision floating-point number (see
[<a href="./rfc4506" title=""XDR: External Data Representation Standard"">RFC4506</a>]).
When EIR is strictly greater than 0 (EIR > 0), the EBS MUST be
greater than or equal to the maximum frame size.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Ethernet FLOWSPEC Object</span>
The Ethernet FLOWSPEC object (Class-Num = 9, Class-Type = 6) has the
same format as the Ethernet SENDER_TSPEC object.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Ethernet ADSPEC Object</span>
There is no ADSPEC object associated with the Ethernet SENDER_TSPEC
object.
<span class="grey">Papadimitriou Standards Track [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc6003">RFC 6003</a> Ethernet Traffic Parameters October 2010</span>
Either the ADSPEC object is omitted or an IntServ ADSPEC with the
Default General Characterization Parameters and Guaranteed Service
fragment is used, see [<a href="./rfc2210" title=""The Use of RSVP with IETF Integrated Services"">RFC2210</a>].
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Processing</span>
The Ethernet SENDER_TSPEC and FLOWSPEC objects specified in this
document MAY be used for signaling Ethernet LSP. For signaling such
an LSP, in the Generalized LABEL_REQUEST object (see [<a href="./rfc3471" title=""Generalized Multi-Protocol Label Switching (GMPLS) Signaling Functional Description"">RFC3471</a>]), the
Switching Type field MUST be set to the value 51 (L2SC) and the LSP
Encoding Type field MUST be set to the value 2 (Ethernet).
The Ethernet SENDER_TSPEC object carries the traffic specification
generated by the RSVP session sender. The Ethernet SENDER_TSPEC
object SHOULD be forwarded and delivered unchanged to both
intermediate and egress nodes.
The Ethernet FLOWSPEC object carries reservation request information
generated by receivers. As with any FLOWSPEC object, the Ethernet
FLOWSPEC object flows upstream toward the ingress node.
Intermediate and egress nodes MUST verify that the node itself and
the interfaces on which the LSP will be established can support the
requested Switching Granularity, MTU and values included in subobject
TLVs. These nodes MUST be configured with the same predefined CT
sets as the index value signaled as part of the Index field of the
Ethernet Bandwidth Profile TLV (see <a href="#section-4.1">Section 4.1</a>). If the requested
value(s) cannot be supported, the receiver node MUST generate a
PathErr message with the error code "Traffic Control Error" and the
error value "Service unsupported" (see [<a href="./rfc2205" title=""Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification"">RFC2205</a>]).
In addition, if the MTU field is received with a value smaller than
the minimum transfer unit size of the Ethernet frame (e.g., 46 bytes
for Ethernet v2, 38 bytes for IEEE 802.3), the node MUST generate a
PathErr message with the error code "Traffic Control Error" and the
error value "Bad Tspec value" (see [<a href="./rfc2205" title=""Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification"">RFC2205</a>]).
Error processing of the CLASSTYPE object follows rules defined in
[<a href="./rfc4124" title=""Protocol Extensions for Support of Diffserv-aware MPLS Traffic Engineering"">RFC4124</a>]. Error processing of the EXTENDED_CLASSTYPE object follows
rules defined in [<a href="#ref-MCOS" title=""Extensions for Differentiated Services-aware Traffic Engineered LSPs"">MCOS</a>]. Moreover, a Label Switching Router (LSR)
receiving a Path message with the EXTENDED_CLASSTYPE object, which
recognizes the object and the particular Class-Type but does detect a
mismatch in the index values, MUST send a PathErr message towards the
sender with the error code "Extended Class-Type Error" and the error
value "Class-Type mismatch" (see [<a href="./rfc2205" title=""Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification"">RFC2205</a>]).
<span class="grey">Papadimitriou Standards Track [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc6003">RFC 6003</a> Ethernet Traffic Parameters October 2010</span>
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Security Considerations</span>
This document introduces no new security considerations to [<a href="./rfc3473" title=""Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol- Traffic Engineering (RSVP-TE) Extensions"">RFC3473</a>].
GMPLS security is described in <a href="./rfc3471#section-11">Section 11 of [RFC3471]</a> and refers to
[<a href="./rfc3209" title=""RSVP-TE: Extensions to RSVP for LSP Tunnels"">RFC3209</a>] for RSVP-TE. Further details of MPLS-TE and GMPLS security
can be found in [<a href="./rfc5920" title=""Security Framework for MPLS and GMPLS Networks"">RFC5920</a>].
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. IANA Considerations</span>
IANA maintains registries and sub-registries for RSVP-TE as used by
GMPLS. IANA has made allocations from these registries as set out in
the following sections.
<span class="h3"><a class="selflink" id="section-9.1" href="#section-9.1">9.1</a>. RSVP Objects Class Types</span>
This document introduces two new Class Types for existing RSVP
objects. IANA has made allocations from the "Resource ReSerVation
Protocol (RSVP) Parameters" registry using the "Class Names, Class
Numbers, and Class Types" sub-registry.
Class Number Class Name Reference
------------ ----------------------- ---------
9 FLOWSPEC [<a href="./rfc2205" title=""Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification"">RFC2205</a>]
Class Type (C-Type):
6 Ethernet SENDER_TSPEC [<a href="./rfc6003">RFC6003</a>]
Class Number Class Name Reference
------------ ----------------------- ---------
12 SENDER_TSPEC [<a href="./rfc2205" title=""Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification"">RFC2205</a>]
Class Type (C-Type):
6 Ethernet SENDER_TSPEC [<a href="./rfc6003">RFC6003</a>]
<span class="h3"><a class="selflink" id="section-9.2" href="#section-9.2">9.2</a>. Ethernet Switching Granularities</span>
IANA maintains a registry of GMPLS parameters called "Generalized
Multi-Protocol Label Switching (GMPLS) Signaling Parameters".
IANA has created a new sub-registry called "Ethernet Switching
Granularities" to contain the values that may be carried in the
Switching Granularity field of the Ethernet SENDER_TSPEC object.
<span class="grey">Papadimitriou Standards Track [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc6003">RFC 6003</a> Ethernet Traffic Parameters October 2010</span>
Values are as follows:
0-2 See below.
3-239 Unassigned
240-254 Reserved for Vendor-Specific Use
255 Reserved
256-65535 Not assigned at this time
The registration procedure is Standards Action.
Initial entries in this sub-registry are as follows:
Value Switching Granularity Reference
----- -------------------------------------- ------------------
0 Provided in signaling. [<a href="./rfc6003">RFC6003</a>][RFC6004]
1 Ethernet Port (for port-based service) [<a href="./rfc6003">RFC6003</a>]
2 Ethernet Frame (for EVC-based service) [<a href="./rfc6003">RFC6003</a>]
255 Reserved [<a href="./rfc6003">RFC6003</a>]
<span class="h3"><a class="selflink" id="section-9.3" href="#section-9.3">9.3</a>. Ethernet Sender TSpec TLVs</span>
IANA maintains a registry of GMPLS parameters called "Generalized
Multi-Protocol Label Switching (GMPLS) Signaling Parameters".
IANA has created a new sub-registry called "Ethernet Sender TSpec
TLVs / Ethernet Flowspec TLVs" to contain the TLV type values for
TLVs carried in the Ethernet SENDER_TSPEC object.
Values are as follows:
0-3 See below.
4-239 Unassigned
240-254 Reserved for Vendor-Specific Use
255 Reserved
256-65535 Not assigned at this time
The registration procedure is Standards Action.
Initial entries in this sub-registry are as follows:
Type Description Reference
----- -------------------------------- ---------
0 Reserved [<a href="./rfc6003">RFC6003</a>]
1 Reserved [<a href="./rfc6003">RFC6003</a>]
2 Ethernet Bandwidth Profile [<a href="./rfc6003">RFC6003</a>]
3 Layer 2 Control Protocol (L2CP) [<a href="./rfc6003">RFC6003</a>]
255 Reserved [<a href="./rfc6003">RFC6003</a>]
<span class="grey">Papadimitriou Standards Track [Page 11]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
<span class="grey"><a href="./rfc6003">RFC 6003</a> Ethernet Traffic Parameters October 2010</span>
<span class="h3"><a class="selflink" id="section-9.4" href="#section-9.4">9.4</a>. Ethernet Bandwidth Profiles</span>
IANA maintains a registry of GMPLS parameters called "Generalized
Multi-Protocol Label Switching (GMPLS) Signaling Parameters".
IANA has created a new sub-registry called "Ethernet Bandwidth
Profiles" to contain bit flags carried in the Ethernet Bandwidth
Profile TLV of the Ethernet SENDER_TSPEC object.
Bits are to be allocated by IETF Standards Action. Bits are numbered
from bit 0 as the low order bit. Initial entries are as follows:
Bit Hex Description Reference
--- ---- -------------------------- -------------
0 0x01 Coupling Flag (CF) [<a href="./rfc6003">RFC6003</a>]
1 0x02 Color Mode (CM) [<a href="./rfc6003">RFC6003</a>]
<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. Acknowledgments</span>
Many thanks to Adrian Farrel for his comments. Lou Berger provided
the input on control traffic processing.
<span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>. References</span>
<span class="h3"><a class="selflink" id="section-11.1" href="#section-11.1">11.1</a>. Normative References</span>
[<a id="ref-MEF10.1">MEF10.1</a>] The MEF Technical Specification, "Ethernet Services
Attributes Phase 2", MEF 10.1, November 2006.
[<a id="ref-RFC2205">RFC2205</a>] Braden, R., Ed., Zhang, L., Berson, S., Herzog, S., and S.
Jamin, "Resource ReSerVation Protocol (RSVP) -- Version 1
Functional Specification", <a href="./rfc2205">RFC 2205</a>, September 1997.
[<a id="ref-RFC2210">RFC2210</a>] Wroclawski, J., "The Use of RSVP with IETF Integrated
Services", <a href="./rfc2210">RFC 2210</a>, September 1997.
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
[<a id="ref-RFC3209">RFC3209</a>] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V.,
and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP
Tunnels", <a href="./rfc3209">RFC 3209</a>, December 2001.
[<a id="ref-RFC3471">RFC3471</a>] Berger, L., Ed., "Generalized Multi-Protocol Label
Switching (GMPLS) Signaling Functional Description", <a href="./rfc3471">RFC</a>
<a href="./rfc3471">3471</a>, January 2003.
<span class="grey">Papadimitriou Standards Track [Page 12]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
<span class="grey"><a href="./rfc6003">RFC 6003</a> Ethernet Traffic Parameters October 2010</span>
[<a id="ref-RFC3473">RFC3473</a>] Berger, L., Ed., "Generalized Multi-Protocol Label
Switching (GMPLS) Signaling Resource ReserVation Protocol-
Traffic Engineering (RSVP-TE) Extensions", <a href="./rfc3473">RFC 3473</a>,
January 2003.
[<a id="ref-RFC4124">RFC4124</a>] Le Faucheur, F., Ed., "Protocol Extensions for Support of
Diffserv-aware MPLS Traffic Engineering", <a href="./rfc4124">RFC 4124</a>, June
2005.
[<a id="ref-RFC4506">RFC4506</a>] Eisler, M., Ed., "XDR: External Data Representation
Standard", STD 67, <a href="./rfc4506">RFC 4506</a>, May 2006.
[<a id="ref-RFC5226">RFC5226</a>] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>, <a href="./rfc5226">RFC 5226</a>,
May 2008.
[<a id="ref-RFC6004">RFC6004</a>] Berger, L. and D. Fedyk, "Generalized MPLS (GMPLS) Support
for Metro Ethernet Forum and G.8011 Ethernet Services",
<a href="./rfc6004">RFC 6004</a>, October 2010.
<span class="h3"><a class="selflink" id="section-11.2" href="#section-11.2">11.2</a>. Informative References</span>
[<a id="ref-ETHv2">ETHv2</a>] Digital, Intel, and Xerox, "The Ethernet -- A Local Area
Network: Data Link Layer and Physical Layer
Specifications", Version 2.0, November 1982.
[<a id="ref-IEEE802.3">IEEE802.3</a>]
IEEE 802.3 LAN/MAN CSMA/CD (Ethernet) Access Method, IEEE
Standard for Information technology- Specific requirements
- Part 3: Carrier Sense Multiple Access with Collision
Detection (CMSA/CD) Access Method and Physical Layer
Specifications, IEEE 802.3-2008.
[<a id="ref-MCOS">MCOS</a>] Minei, I., Gan, D., Kompella, K., and X. Li, "Extensions
for Differentiated Services-aware Traffic Engineered
LSPs", Work in Progress, June 2006.
[<a id="ref-MEF6">MEF6</a>] The Metro Ethernet Forum, "Ethernet Services Definitions -
Phase I", MEF 6, June 2004.
[<a id="ref-MEF10.2">MEF10.2</a>] The MEF Technical Specification, "Ethernet Services
Attributes Phase 2", MEF 10.2, October 2009.
[<a id="ref-RFC5920">RFC5920</a>] Fang, L., Ed., "Security Framework for MPLS and GMPLS
Networks", <a href="./rfc5920">RFC 5920</a>, July 2010.
<span class="grey">Papadimitriou Standards Track [Page 13]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
<span class="grey"><a href="./rfc6003">RFC 6003</a> Ethernet Traffic Parameters October 2010</span>
Author's Address
Dimitri Papadimitriou
Alcatel-Lucent Bell
Copernicuslaan 50
B-2018 Antwerpen, Belgium
Phone: +32 3 2408491
EMail: dimitri.papadimitriou@alcatel-lucent.be
Papadimitriou Standards Track [Page 14]
</pre>
|
