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
|
<pre>Internet Engineering Task Force (IETF) L. Yong
Request for Comments: 7173 D. Eastlake 3rd
Category: Standards Track S. Aldrin
ISSN: 2070-1721 Huawei
J. Hudson
Brocade
May 2014
<span class="h1">Transparent Interconnection of Lots of Links (TRILL) Transport</span>
<span class="h1">Using Pseudowires</span>
Abstract
This document specifies how to interconnect a pair of Transparent
Interconnection of Lots of Links (TRILL) switch ports using
pseudowires under existing TRILL and Pseudowire Emulation End-to-End
(PWE3) standards.
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/rfc7173">http://www.rfc-editor.org/info/rfc7173</a>.
Copyright Notice
Copyright (c) 2014 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">Yong, et al. Standards Track [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc7173">RFC 7173</a> PWE3 TRILL Transport May 2014</span>
Table of Contents
<a href="#section-1">1</a>. Introduction.....................................................<a href="#page-2">2</a>
<a href="#section-1.1">1.1</a>. Conventions Used in This Document...........................<a href="#page-2">2</a>
<a href="#section-2">2</a>. PWE3 Interconnection of TRILL Switches...........................<a href="#page-3">3</a>
<a href="#section-2.1">2.1</a>. PWE3 Type-Independent Details...............................<a href="#page-3">3</a>
<a href="#section-2.2">2.2</a>. PPP PWE3 Transport of TRILL.................................<a href="#page-4">4</a>
<a href="#section-3">3</a>. Security Considerations..........................................<a href="#page-6">6</a>
<a href="#appendix-A">Appendix A</a>. Use of Other Pseudowire Types ..........................<a href="#page-7">7</a>
Acknowledgements ...................................................<a href="#page-8">8</a>
Normative References ...............................................<a href="#page-9">9</a>
Informative References ............................................<a href="#page-10">10</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
The Transparent Interconnection of Lots of Links (TRILL) protocol
[<a href="./rfc6325" title=""Routing Bridges (RBridges): Base Protocol Specification"">RFC6325</a>] provides optimal pair-wise data frame routing without
configuration in multi-hop networks with arbitrary topology. TRILL
supports multipathing of both unicast and multicast traffic. Devices
that implement TRILL are called TRILL switches or Routing Bridges
(RBridges).
Links between TRILL switches can be based on arbitrary link
protocols, for example, PPP [<a href="./rfc6361" title=""PPP Transparent Interconnection of Lots of Links (TRILL) Protocol Control Protocol"">RFC6361</a>], as well as Ethernet [<a href="./rfc6325" title=""Routing Bridges (RBridges): Base Protocol Specification"">RFC6325</a>].
A set of connected TRILL switches together form a TRILL campus that
is bounded by end stations and Layer 3 routers.
This document specifies how to interconnect a pair of TRILL switch
ports using a pseudowire under existing TRILL and PWE3 (Pseudowire
Emulation End-to-End) standards.
<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Conventions Used in This Document</span>
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in
[<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>].
Acronyms used in this document include the following:
IS-IS - Intermediate System to Intermediate System [<a href="#ref-IS-IS" title=""Information technology -- Telecommunications and information exchange between systems -- Intermediate System to Intermediate System intra-domain routeing information exchange protocol for use in conjunction with the protocol for providing the connectionless-mode network service (ISO 8473)"">IS-IS</a>]
MPLS - Multi-Protocol Label Switching
PPP - Point-to-Point Protocol [<a href="./rfc1661" title=""The Point-to-Point Protocol (PPP)"">RFC1661</a>]
PW - Pseudowire [<a href="./rfc3985" title=""Pseudo Wire Emulation Edge-to-Edge (PWE3) Architecture"">RFC3985</a>]
<span class="grey">Yong, et al. Standards Track [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc7173">RFC 7173</a> PWE3 TRILL Transport May 2014</span>
PWE3 - PW Emulation End-to-End
RBridge - Routing Bridge, an alternative name for a TRILL switch
TRILL - Transparent Interconnection of Lots of Links [<a href="./rfc6325" title=""Routing Bridges (RBridges): Base Protocol Specification"">RFC6325</a>]
TRILL Switch - A device implementing the TRILL protocol
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. PWE3 Interconnection of TRILL Switches</span>
When a pseudowire is used to interconnect a pair of TRILL switch
ports, a PPP [<a href="./rfc4618" title=""Encapsulation Methods for Transport of PPP/High-Level Data Link Control (HDLC) over MPLS Networks"">RFC4618</a>] pseudowire is used as described below. The
pseudowire between such ports can be signaled [<a href="./rfc4447" title=""Pseudowire Setup and Maintenance Using the Label Distribution Protocol (LDP)"">RFC4447</a>] or manually
configured. In this context, the TRILL switch ports at the ends of
the pseudowire are acting as native service processing (NSP) elements
[<a href="./rfc3985" title=""Pseudo Wire Emulation Edge-to-Edge (PWE3) Architecture"">RFC3985</a>] and, assuming that the pseudowires are over MPLS or IP
[<a href="./rfc4023" title=""Encapsulating MPLS in IP or Generic Routing Encapsulation (GRE)"">RFC4023</a>] networks, as label switched or IP routers at the TRILL
switch ports.
Pseudowires provide transparent transport, and the two TRILL switch
ports appear directly interconnected with a transparent link. With
such an interconnection, the TRILL adjacency over the link is
automatically discovered and established through TRILL IS-IS control
messages [<a href="./rfc7177" title=""Transparent Interconnection of Lots of Links (TRILL): Adjacency"">RFC7177</a>].
A pseudowire is carried over a packet switched network tunnel
[<a href="./rfc3985" title=""Pseudo Wire Emulation Edge-to-Edge (PWE3) Architecture"">RFC3985</a>], for example, an MPLS or MPLS-TP label switched path tunnel
in MPLS networks. Either a signaling protocol or manual
configuration can be used to configure a label switched path tunnel
between two TRILL switch ports. This application needs no additions
to the existing pseudowire standards.
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. PWE3 Type-Independent Details</span>
The sending pseudowire TRILL switch port SHOULD map the inner
priority of the TRILL Data packets being sent to the Traffic Class
field of the pseudowire label [<a href="./rfc5462" title=""Multiprotocol Label Switching (MPLS) Label Stack Entry: "">RFC5462</a>] so as to minimize the
probability that higher priority TRILL Data packets will be discarded
due to excessive TRILL Data packets of lower priority.
TRILL IS-IS PDUs critical to establishing and maintaining adjacency
(Hello and MTU PDUs) SHOULD be sent with the MPLS Traffic Class that
calls for handling with the maximum priority. Other TRILL IS-IS PDUs
SHOULD be sent with the MPLS Traffic Class denoting the highest
priority that is less than the maximum priority. TRILL Data packets
SHOULD be sent with appropriate MPLS Traffic Classes, typically
mapped from the TRILL Data packet priority, such that TRILL Data
packet Traffic Classes denote priorities less than the priorities
<span class="grey">Yong, et al. Standards Track [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc7173">RFC 7173</a> PWE3 TRILL Transport May 2014</span>
used for TRILL IS-IS PDUs. This minimizes the probability of other
traffic interfering with these important control PDUs and causing
false loss of adjacency or other control problems.
If a pseudowire supports fragmentation and reassembly (a feature that
has received little or no deployment), then there is no reason to do
TRILL MTU testing on it, and the pseudowire will not be a constraint
on the TRILL campus-wide MTU size (Sz) (see <a href="./rfc6325#section-4.3.1">Section 4.3.1 of
[RFC6325]</a>). If the pseudowire does not support fragmentation (the
more common case), then the available TRILL IS-IS packet payload size
over the pseudowire (taking into account MPLS encapsulation with a
control word) or some lower value, MUST be used in helping to
determine MTU size (Sz) (see <a href="./rfc7180#section-5">Section 5 of [RFC7180]</a>).
An intervening MPLS label switched router or similar packet switched
network device has no awareness of TRILL. Such devices will not
change the TRILL Header hop count.
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. PPP PWE3 Transport of TRILL</span>
For a PPP pseudowire (PW type = 0x0007), the two TRILL switch ports
being connected are configured to form a pseudowire with PPP
encapsulation [<a href="./rfc4618" title=""Encapsulation Methods for Transport of PPP/High-Level Data Link Control (HDLC) over MPLS Networks"">RFC4618</a>]. After the pseudowire is established and
TRILL use is negotiated within PPP, the two TRILL switch ports appear
directly connected with a PPP link [<a href="./rfc1661" title=""The Point-to-Point Protocol (PPP)"">RFC1661</a>] [<a href="./rfc6361" title=""PPP Transparent Interconnection of Lots of Links (TRILL) Protocol Control Protocol"">RFC6361</a>].
If pseudowire interconnection of two TRILL switch ports is signaled
[<a href="./rfc4447" title=""Pseudowire Setup and Maintenance Using the Label Distribution Protocol (LDP)"">RFC4447</a>], the initiating TRILL switch port MUST attempt the
connection setup with pseudowire type PPP (0x0007).
Behavior for TRILL with a PPP pseudowire continues to follow that of
TRILL over PPP as specified in <a href="./rfc6361#section-3">Section 3 of [RFC6361]</a>.
<span class="grey">Yong, et al. Standards Track [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc7173">RFC 7173</a> PWE3 TRILL Transport May 2014</span>
The following figures show what a TRILL Data packet and TRILL IS-IS
packet look like over such a pseudowire in the MPLS case, assuming no
TRILL Header extensions:
+--------------------------------+
| Server MPLS Tunnel Label(s) | n*4 octets (4 octets per label)
+--------------------------------+
| PW Label | 4 octets
+--------------------------------+
| Control Word | 4 octets
+--------------------------------+
| PPP Header 0x005d | 2 octets
+--------------------------------+
| TRILL Header | 6 octets
+--------------------------------+
| Destination MAC Address | 6 octets
+--------------------------------+
| Source MAC Address | 6 octets
+--------------------------------+
| Data Label | 4 or 8 octets
+--------------------------------+
| Payload Body | variable
+--------------------------------+
Figure 1: TRILL Data Packet in Pseudowire
"Data Label" is the VLAN Label or Fine-Grained Label [<a href="./rfc7172" title=""Transparent Interconnection of Lots of Links (TRILL): Fine-Grained Labeling"">RFC7172</a>] of the
payload.
+--------------------------------+
| Server MPLS Tunnel Label(s) | n*4 octets (4 octets per label)
+--------------------------------+
| PW Label | 4 octets
+--------------------------------+
| Control Word | 4 octets
+--------------------------------+
| PPP Header 0x405d | 2 octets
+--------------------------------+
| Common IS-IS Header | 8 octets
+--------------------------------+
| IS-IS PDU Type Specific Header | variable
+--------------------------------+
| IS-IS TLVs | variable
+--------------------------------+
Figure 2: TRILL IS-IS Packet in Pseudowire
<span class="grey">Yong, et al. Standards Track [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc7173">RFC 7173</a> PWE3 TRILL Transport May 2014</span>
The PPP Header fields (0x005d and 0x405d, respectively) for TRILL
Data and IS-IS packets shown above are specified in [<a href="./rfc6361" title=""PPP Transparent Interconnection of Lots of Links (TRILL) Protocol Control Protocol"">RFC6361</a>].
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Security Considerations</span>
TRILL-level security mechanisms, such as the ability to use
authentication with TRILL IS-IS PDUs [<a href="./rfc6325" title=""Routing Bridges (RBridges): Base Protocol Specification"">RFC6325</a>], are not affected by
link technology, such as the use of pseudowire links as specified in
this document.
Link security may be useful in improving TRILL campus security.
TRILL is transported over pseudowires as TRILL over PPP over
pseudowires, pseudowires are over MPLS or IP, and MPLS and IP are
over some lower-level link technology. Thus, link security below the
TRILL level for a pseudowire link could be provided by PPP security,
pseudowire security, MPLS or IP security, or security of the link
technology supporting MPLS or IP.
PPP TRILL security considerations are discussed in [<a href="./rfc6361" title=""PPP Transparent Interconnection of Lots of Links (TRILL) Protocol Control Protocol"">RFC6361</a>]. For
security considerations introduced by carrying PPP TRILL links over
pseudowires, see [<a href="./rfc3985" title=""Pseudo Wire Emulation Edge-to-Edge (PWE3) Architecture"">RFC3985</a>], which discusses the risks introduced by
sending protocols that previously assumed a point-to-point link on a
pseudowire built on a packet switched network (PSN). However, the
PPP layer in TRILL transport by pseudowire is somewhat vestigial and
intended primarily as a convenient way to use existing PPP code
points to identify TRILL Data packets and TRILL IS-IS packets.
Furthermore, existing PPP security standards are arguably
questionable in terms of current security criteria. For these
reasons, it is NOT RECOMMENDED to use PPP security in the transport
of TRILL by pseudowires as specified in this document.
It is RECOMMENDED that link security be provided at the layers
supporting pseudowires transporting TRILL, that is, at the MPLS or IP
layer or the link layer transporting MPLS or IP.
For applications involving sensitive data, end-to-end security should
always be considered, in addition to link security, to provide
security in depth. In this context, such end-to-end security should
be between the end stations involved so as to protect the entire path
to, through, and from the TRILL campus.
For general TRILL protocol security considerations, see [<a href="./rfc6325" title=""Routing Bridges (RBridges): Base Protocol Specification"">RFC6325</a>].
<span class="grey">Yong, et al. Standards Track [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc7173">RFC 7173</a> PWE3 TRILL Transport May 2014</span>
<span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">Appendix A</a>. Use of Other Pseudowire Types</span>
This informational appendix briefly discusses the use of pseudowire
types other than PPP for the transport of TRILL.
The use of Ethernet pseudowires [<a href="./rfc4448" title=""Encapsulation Methods for Transport of Ethernet over MPLS Networks"">RFC4448</a>] was examined by the authors
and would be possible without change to such pseudowires; however,
this would require an additional 12 or 16 bytes per packet within the
payload being transmitted over the pseudowire for a TRILL Data packet
(Figure 3) and a TRILL IS-IS packet (Figure 4) over such an Ethernet
pseudowire in the MPLS case, assuming no TRILL Header extensions
(compare with Figures 1 and 2):
+--------------------------------+
| Server MPLS Tunnel Label(s) | n*4 octets (4 octets per label)
+--------------------------------+
| PW Label | 4 octets
+--------------------------------+
| Optional Control Word | 4 octets
+--------------------------------+
| TRILL Hop Dest. MAC Address | 6 octets
+--------------------------------+
| TRILL Hop Source MAC Address | 6 octets
+--------------------------------+
|Optional VLAN and/or other tags | variable
+--------------------------------+
| TRILL Ethertype (0x22f3) | 2 octets
+--------------------------------+
| TRILL Header | 6 octets
+--------------------------------+
| Destination MAC Address | 6 octets
+--------------------------------+
| Source MAC Address | 6 octets
+--------------------------------+
| Data Label | 4 or 8 octets
+--------------------------------+
| Payload Body | variable
+--------------------------------+
Figure 3: TRILL Data Packet in Ethernet Pseudowire
"Data Label" is the VLAN Label or Fine-Grained Label [<a href="./rfc7172" title=""Transparent Interconnection of Lots of Links (TRILL): Fine-Grained Labeling"">RFC7172</a>] of the
payload.
<span class="grey">Yong, et al. Standards Track [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc7173">RFC 7173</a> PWE3 TRILL Transport May 2014</span>
+--------------------------------+
| Server MPLS Tunnel Label(s) | n*4 octets (4 octets per label)
+--------------------------------+
| PW Label | 4 octets
+--------------------------------+
| Optional Control Word | 4 octets
+--------------------------------+
| TRILL Hop Dest. MAC Address | 6 octets
+--------------------------------+
| TRILL Hop Source MAC Address | 6 octets
+--------------------------------+
|Optional VLAN and/or other tags | variable
+--------------------------------+
| Layer 2 IS-IS Ethertype 0x22f4 | 2 octets
+--------------------------------+
| Common IS-IS Header | 8 octets
+--------------------------------+
| IS-IS PDU Type Specific Header | variable
+--------------------------------+
| IS-IS TLVs | variable
+--------------------------------+
Figure 4: TRILL IS-IS Packet in Ethernet Pseudowire
It would also be possible to specify a new pseudowire type for TRILL
traffic, but the authors feel that any efficiency gain over PPP
pseudowires would be too small to be worth the complexity of adding
such a specification. Furthermore, using PPP pseudowire encoding
means that any traffic dissector that understands TRILL PPP encoding
[<a href="./rfc6361" title=""PPP Transparent Interconnection of Lots of Links (TRILL) Protocol Control Protocol"">RFC6361</a>] and PPP pseudowires [<a href="./rfc4618" title=""Encapsulation Methods for Transport of PPP/High-Level Data Link Control (HDLC) over MPLS Networks"">RFC4618</a>] will automatically be able to
recursively decode TRILL transported by pseudowire.
Acknowledgements
Thanks for the valuable comments from the following, who are listed
in alphabetic order:
Stewart Bryant, Stephen Farrell, Brian Haberman, Christer
Holmberg, Joel Jaeggli, Barry Leiba, Erik Nordmark, Yaron Sheffer,
and Yaakov (J) Stein.
<span class="grey">Yong, et al. Standards Track [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc7173">RFC 7173</a> PWE3 TRILL Transport May 2014</span>
Normative References
[<a id="ref-RFC1661">RFC1661</a>] Simpson, W., Ed., "The Point-to-Point Protocol (PPP)",
STD 51, <a href="./rfc1661">RFC 1661</a>, July 1994.
[<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-RFC4447">RFC4447</a>] Martini, L., Ed., Rosen, E., El-Aawar, N., Smith, T., and
G. Heron, "Pseudowire Setup and Maintenance Using the
Label Distribution Protocol (LDP)", <a href="./rfc4447">RFC 4447</a>, April 2006.
[<a id="ref-RFC4618">RFC4618</a>] Martini, L., Rosen, E., Heron, G., and A. Malis,
"Encapsulation Methods for Transport of PPP/High-Level
Data Link Control (HDLC) over MPLS Networks", <a href="./rfc4618">RFC 4618</a>,
September 2006.
[<a id="ref-RFC5462">RFC5462</a>] Andersson, L. and R. Asati, "Multiprotocol Label Switching
(MPLS) Label Stack Entry: "EXP" Field Renamed to "Traffic
Class" Field", <a href="./rfc5462">RFC 5462</a>, February 2009.
[<a id="ref-RFC6325">RFC6325</a>] Perlman, R., Eastlake 3rd, D., Dutt, D., Gai, S., and A.
Ghanwani, "Routing Bridges (RBridges): Base Protocol
Specification", <a href="./rfc6325">RFC 6325</a>, July 2011.
[<a id="ref-RFC6361">RFC6361</a>] Carlson, J. and D. Eastlake 3rd, "PPP Transparent
Interconnection of Lots of Links (TRILL) Protocol Control
Protocol", <a href="./rfc6361">RFC 6361</a>, August 2011.
[<a id="ref-RFC7172">RFC7172</a>] Eastlake 3rd, D., Zhang, M., Agarwal, P., Perlman, R., and
D. Dutt, "Transparent Interconnection of Lots of Links
(TRILL): Fine-Grained Labeling", <a href="./rfc7172">RFC 7172</a>, May 2014.
[<a id="ref-RFC7180">RFC7180</a>] Eastlake 3rd, D., Zhang, M., Ghanwani, A., Manral, V., and
A. Banerjee, "Transparent Interconnection of Lots of Links
(TRILL): Clarifications, Corrections, and Updates",
<a href="./rfc7180">RFC 7180</a>, May 2014.
<span class="grey">Yong, et al. Standards Track [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc7173">RFC 7173</a> PWE3 TRILL Transport May 2014</span>
Informative References
[<a id="ref-IS-IS">IS-IS</a>] ISO/IEC 10589:2002, Second Edition, "Information
technology -- Telecommunications and information exchange
between systems -- Intermediate System to Intermediate
System intra-domain routeing information exchange protocol
for use in conjunction with the protocol for providing the
connectionless-mode network service (ISO 8473)", 2002.
[<a id="ref-RFC3985">RFC3985</a>] Bryant, S., Ed., and P. Pate, Ed., "Pseudo Wire Emulation
Edge-to-Edge (PWE3) Architecture", <a href="./rfc3985">RFC 3985</a>, March 2005.
[<a id="ref-RFC4023">RFC4023</a>] Worster, T., Rekhter, Y., and E. Rosen, Ed.,
"Encapsulating MPLS in IP or Generic Routing Encapsulation
(GRE)", <a href="./rfc4023">RFC 4023</a>, March 2005.
[<a id="ref-RFC4448">RFC4448</a>] Martini, L., Ed., Rosen, E., El-Aawar, N., and G. Heron,
"Encapsulation Methods for Transport of Ethernet over MPLS
Networks", <a href="./rfc4448">RFC 4448</a>, April 2006.
[<a id="ref-RFC7177">RFC7177</a>] Eastlake 3rd, D., Perlman, R., Ghanwani, A., Yang, H., and
V. Manral, "Transparent Interconnection of Lots of Links
(TRILL): Adjacency", <a href="./rfc7177">RFC 7177</a>, May 2014.
<span class="grey">Yong, et al. Standards Track [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc7173">RFC 7173</a> PWE3 TRILL Transport May 2014</span>
Authors' Addresses
Lucy Yong
Huawei Technologies
5340 Legacy Drive
Plano, TX 75024
USA
Phone: +1-469-227-5837
EMail: lucy.yong@huawei.com
Donald E. Eastlake 3rd
Huawei Technologies
155 Beaver Street
Milford, MA 01757
USA
Phone: +1-508-333-2270
EMail: d3e3e3@gmail.com
Sam Aldrin
Huawei Technologies
2330 Central Expressway
Santa Clara, CA 95050
USA
Phone: +1-408-330-4517
EMail: sam.aldrin@huawei.com
Jon Hudson
Brocade
130 Holger Way
San Jose, CA 95134
USA
Phone: +1-408-333-4062
EMail: jon.hudson@gmail.com
Yong, et al. Standards Track [Page 11]
</pre>
|
