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>Network Working Group M. Townsley
Request for Comments: 4591 G. Wilkie
Category: Standards Track S. Booth
S. Bryant
Cisco Systems
J. Lau
July 2006
<span class="h1">Frame Relay over Layer 2 Tunneling Protocol Version 3 (L2TPv3)</span>
Status of This Memo
This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2006).
Abstract
The Layer 2 Tunneling Protocol, Version 3, (L2TPv3) defines a
protocol for tunneling a variety of data link protocols over IP
networks. This document describes the specifics of how to tunnel
Frame Relay over L2TPv3, including frame encapsulation, virtual-
circuit creation and deletion, and status change notification.
<span class="grey">Townsley, 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="./rfc4591">RFC 4591</a> Frame Relay over L2TPv3 July 2006</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>. Abbreviations ..............................................<a href="#page-3">3</a>
<a href="#section-1.2">1.2</a>. Specification of Requirements ..............................<a href="#page-3">3</a>
<a href="#section-2">2</a>. Control Connection Establishment ................................<a href="#page-3">3</a>
<a href="#section-3">3</a>. PVC Status Notification and Session Establishment ...............<a href="#page-3">3</a>
<a href="#section-3.1">3.1</a>. L2TPv3 Session Establishment ...............................<a href="#page-4">4</a>
<a href="#section-3.2">3.2</a>. L2TPv3 Session Teardown ....................................<a href="#page-5">5</a>
<a href="#section-3.3">3.3</a>. L2TPv3 Session Maintenance .................................<a href="#page-5">5</a>
<a href="#section-3.4">3.4</a>. Use of the Circuit Status AVP for Frame Relay ..............<a href="#page-6">6</a>
<a href="#section-3.5">3.5</a>. Frame Relay Header Length AVP ..............................<a href="#page-7">7</a>
<a href="#section-4">4</a>. Encapsulation ...................................................<a href="#page-7">7</a>
<a href="#section-4.1">4.1</a>. Data Packet Encapsulation ..................................<a href="#page-7">7</a>
<a href="#section-4.2">4.2</a>. Data Packet Sequencing .....................................<a href="#page-9">9</a>
<a href="#section-4.3">4.3</a>. MTU Considerations .........................................<a href="#page-9">9</a>
<a href="#section-5">5</a>. Applicability Statement ........................................<a href="#page-10">10</a>
<a href="#section-6">6</a>. Security Considerations ........................................<a href="#page-10">10</a>
<a href="#section-7">7</a>. IANA Considerations ............................................<a href="#page-11">11</a>
<a href="#section-7.1">7.1</a>. Pseudowire Type ...........................................<a href="#page-11">11</a>
<a href="#section-7.2">7.2</a>. Result Code AVP Values ....................................<a href="#page-11">11</a>
<a href="#section-7.3">7.3</a>. Control Message Attribute Value Pairs (AVPs) ..............<a href="#page-11">11</a>
<a href="#section-8">8</a>. Acknowledgements ...............................................<a href="#page-11">11</a>
<a href="#section-9">9</a>. References .....................................................<a href="#page-12">12</a>
<a href="#section-9.1">9.1</a>. Normative References ......................................<a href="#page-12">12</a>
<a href="#section-9.2">9.2</a>. Informative References ....................................<a href="#page-12">12</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
[<a id="ref-RFC3931">RFC3931</a>] defines a base protocol for Layer 2 Tunneling over IP
networks. This document defines the specifics necessary for
tunneling Frame Relay over L2TPv3. Such emulated circuits are
referred to as Frame Relay Pseudowires (FRPWs).
Protocol specifics defined in this document for L2TPv3 FRPWs
operating in a "virtual circuit-to-virtual circuit" mode include
those necessary for frame encapsulation, PVC creation and deletion,
and status change notification. Frame Relay traffic may also be
transported in a "port-to-port" or "interface-to-interface" fashion
using High-Level Data Link Control (HDLC) Pseudowires as defined in
[<a href="./rfc4349" title=""High-Level Data Link Control (HDLC) Frames over Layer 2 Tunneling Protocol, Version 3 (L2TPv3)"">RFC4349</a>]. Support for Switched Virtual Circuits (SVCs) and
Switched/Soft Permanent Virtual Circuits (SPVCs) are outside the
scope of this document.
The reader is expected to be very familiar with the terminology and
protocol constructs defined in [<a href="./rfc3931" title=""Layer Two Tunneling Protocol - Version 3 (L2TPv3)"">RFC3931</a>].
<span class="grey">Townsley, 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="./rfc4591">RFC 4591</a> Frame Relay over L2TPv3 July 2006</span>
<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Abbreviations</span>
FR Frame Relay
FRPW Frame Relay Pseudowire
LCCE L2TP Control Connection Endpoint (See [<a href="./rfc3931" title=""Layer Two Tunneling Protocol - Version 3 (L2TPv3)"">RFC3931</a>])
PVC Permanent virtual circuit
PW Pseudowire
VC Virtual circuit
<span class="h3"><a class="selflink" id="section-1.2" href="#section-1.2">1.2</a>. Specification of Requirements</span>
In this document, several words are used to signify the requirements
of the specification. These words are often capitalized. 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" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>].
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Control Connection Establishment</span>
In order to tunnel a Frame Relay circuit over IP using L2TPv3, an
L2TPv3 Control Connection MUST first be established as described in
[<a href="./rfc3931" title=""Layer Two Tunneling Protocol - Version 3 (L2TPv3)"">RFC3931</a>]. The L2TPv3 SCCRQ Control Message and corresponding SCCRP
Control Message MUST include the Frame Relay Data Link Connection
Identifier (DLCI) PW Type of 0x0001 (see IANA Considerations), in the
Pseudowire Capabilities List, as defined in <a href="./rfc3931#section-5.4.3">Section 5.4.3 of
[RFC3931]</a>. This identifies the control connection as able to
establish L2TP sessions to support Frame Relay Pseudowires (FRPWs).
An LCCE MUST be able to identify itself uniquely in the SCCRQ and
SCCRP messages via a globally unique value. By default, this is
advertised via the structured Router ID Attribute Value Pairs (AVP)
[<a href="./rfc3931" title=""Layer Two Tunneling Protocol - Version 3 (L2TPv3)"">RFC3931</a>], though the unstructured Hostname AVP [<a href="./rfc3931" title=""Layer Two Tunneling Protocol - Version 3 (L2TPv3)"">RFC3931</a>] MAY be used
to identify LCCEs as well.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. PVC Status Notification and Session Establishment</span>
This section specifies how the status of a PVC is reported between
two LCCEs. This includes what should happen when a PVC is created,
deleted or when it changes state between ACTIVE and INACTIVE. When
emulating a Frame Relay service, if the procedures for PVC status
management defined in [<a href="#ref-Q933" title=""Signalling specifications for frame mode switched and permanent virtual connection control and status monitoring"">Q933</a>] Annex A are being used between an LCCE
and the attached Remote System, an LCCE MUST participate in them (see
<a href="#section-3.3">Section 3.3</a>).
<span class="grey">Townsley, 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="./rfc4591">RFC 4591</a> Frame Relay over L2TPv3 July 2006</span>
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. L2TPv3 Session Establishment</span>
PVC creation (provisioning) results in establishment of an L2TP
session via the standard three-way handshake described in <a href="./rfc3931#section-3.4.1">Section</a>
<a href="./rfc3931#section-3.4.1">3.4.1 of [RFC3931]</a>. An LCCE MAY initiate the session immediately
upon PVC creation or wait until the PVC state transitions to ACTIVE
before attempting to establish a session for the PVC. Waiting until
the PVC transitions to ACTIVE may be preferred, as it delays
allocation of L2TP resources until it is absolutely necessary.
The Pseudowire Type AVP defined in <a href="./rfc3931#section-5.4.4">Section 5.4.4 of [RFC3931]</a>,
Attribute Type 68, MUST be present in the Incoming-Call-Request
(ICRQ) messages and MUST include the Frame Relay DLCI PW Type of
0x0001 for FRPWs.
The Circuit Status AVP (see <a href="#section-3.4">Section 3.4</a>) MUST be present in the ICRQ
and Incoming-Call-Reply (ICRP) messages and MAY be present in the Set
Link Info (SLI) message for FRPWs.
The Frame Relay Header Length AVP (see <a href="#section-3.5">Section 3.5</a>) MAY be present in
the ICRQ and ICRP messages.
The following is an example of the L2TP messages exchanged for an
FRPW that is initiated after a new PVC is provisioned and becomes
ACTIVE.
LCCE (LAC) A LCCE (LAC) B
------------------ ------------------
FR PVC Provisioned
FR PVC Provisioned
FR PVC ACTIVE
ICRQ (status = 0x03) ---->
FR PVC ACTIVE
<---- ICRP (status = 0x03)
L2TP session established,
OK to send data into tunnel
ICCN ----->
L2TP session established,
OK to send data into tunnel
In the example above, an ICRQ is sent after the PVC is created and
becomes ACTIVE. The Circuit Status AVP indicates that this PVC is
ACTIVE and New (0x03). The Remote End ID AVP [<a href="./rfc3931" title=""Layer Two Tunneling Protocol - Version 3 (L2TPv3)"">RFC3931</a>] MUST be
<span class="grey">Townsley, 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="./rfc4591">RFC 4591</a> Frame Relay over L2TPv3 July 2006</span>
present in the ICRQ in order to identify the PVC (together with the
identity of the LCCE itself, as defined in <a href="#section-2">Section 2</a>) to associate
the L2TP session with. The Remote End ID AVP, defined in [<a href="./rfc3931" title=""Layer Two Tunneling Protocol - Version 3 (L2TPv3)"">RFC3931</a>],
is of opaque form and variable length, though one MUST at a minimum
support use of an unstructured four-octet value that is known to both
LCCEs (either by direct configuration, or some other means). The
exact method of how this value is configured, retrieved, discovered,
or otherwise determined at each LCCE is outside the scope of this
document.
As with the ICRQ, the ICRP is sent only after the FR PVC transitions
to ACTIVE as well. If LCCE B had not been provisioned for the PVC
identified in the ICRQ, a Call-Disconnect-Notify (CDN) would have
been immediately returned indicating that the circuit was not
provisioned or available at this LCCE. LCCE A SHOULD then exhibit a
periodic retry mechanism. If so, the period and maximum number of
retries MUST be configurable.
An Implementation MAY send an ICRQ or ICRP before a PVC is ACTIVE, as
long as the Circuit Status AVP reflects that the PVC is INACTIVE and
an SLI is sent when the PVC becomes ACTIVE (see <a href="#section-3.3">Section 3.3</a>).
The Incoming-Call-Connected (ICCN) is the final stage in the session
establishment, confirming the receipt of the ICRP with acceptable
parameters to allow bidirectional traffic.
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. L2TPv3 Session Teardown</span>
In the event that a PVC is deleted (unprovisioned) at either LCCE,
the associated L2TP session MUST be torn down via the CDN message
defined in <a href="./rfc3931#section-3.4.3">Section 3.4.3 of [RFC3931]</a>.
General Result Codes regarding L2TP session establishment are defined
in [<a href="./rfc3931" title=""Layer Two Tunneling Protocol - Version 3 (L2TPv3)"">RFC3931</a>]. Additional Frame Relay result codes are defined as
follows:
17: FR PVC was deleted permanently (no longer provisioned) 18: FR
PVC has been INACTIVE for an extended period of time 19:
Mismatched FR Header Length
<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. L2TPv3 Session Maintenance</span>
FRPW over L2TP makes use of the SLI control message defined in
[<a href="./rfc3931" title=""Layer Two Tunneling Protocol - Version 3 (L2TPv3)"">RFC3931</a>] to signal Frame Relay link status notifications between
LCCEs. This includes ACTIVE or INACTIVE notifications of the VC, and
any other parameters that may need to be shared between the tunnel
endpoints or LCCEs in order to provide proper PW emulation. The SLI
message is a single message that is sent over the L2TP control
<span class="grey">Townsley, 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="./rfc4591">RFC 4591</a> Frame Relay over L2TPv3 July 2006</span>
channel signalling the state change. Since the message is delivered
reliably, there is no additional response or action required of the
PW subsystem to ensure that the state change notification was
received by the tunnel peer.
The SLI message MUST be sent any time there is a circuit status
change that may be reported by any values identified in the Circuit
Status AVP. The only exceptions to this are the initial ICRQ, ICRP,
and CDN messages, which establish and tear down the L2TP session
itself when the PVC is created or deleted. The SLI message may be
sent from either LCCE at any time after the first ICRQ is sent (and
perhaps before an ICRP is received, requiring that the peer to
perform a reverse Session ID lookup).
An LCCE participating in the procedures for PVC status management
defined in [<a href="#ref-Q933" title=""Signalling specifications for frame mode switched and permanent virtual connection control and status monitoring"">Q933</a>], Annex A, MUST transmit an SLI message including
the Circuit Status AVP (see <a href="#section-3.4">Section 3.4</a>) when it detects a change in
the status for a particular local FR PVC (i.e., when it detects a
service-affecting condition or the clearing of such a condition). An
LCCE receiving an SLI message indicating a change in the status of a
particular FRPW SHOULD generate corresponding updates for the FR PVC
towards the Remote System, as defined in [<a href="#ref-Q933" title=""Signalling specifications for frame mode switched and permanent virtual connection control and status monitoring"">Q933</a>], Annex A.
All sessions established by a given control connection utilize the
L2TP Hello facility, defined in <a href="./rfc3931#section-4.4">Section 4.4 of [RFC3931]</a>, for session
keepalive. This gives all sessions basic dead peer and path
detection between LCCEs.
<span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a>. Use of the Circuit Status AVP for Frame Relay</span>
Frame Relay circuit status is reported via the Circuit Status AVP
defined in [<a href="./rfc3931" title=""Layer Two Tunneling Protocol - Version 3 (L2TPv3)"">RFC3931</a>], Attribute Type 71. For reference, this AVP is
shown below:
0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Reserved |N|A|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Value is a 16-bit mask with the two least significant bits
defined and the remaining bits reserved for future use. Reserved
bits MUST be set to 0 by the sender and ignored by the receiver.
The N (New) bit indicates whether the Circuit Status indication is
for a new FR PVC (1) or an existing FR PVC (0).
<span class="grey">Townsley, 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="./rfc4591">RFC 4591</a> Frame Relay over L2TPv3 July 2006</span>
The A (Active) bit indicates whether the FR PVC is ACTIVE (1) or
INACTIVE (0).
<span class="h3"><a class="selflink" id="section-3.5" href="#section-3.5">3.5</a>. Frame Relay Header Length AVP</span>
The "Frame Relay Header Length AVP", Attribute type 85, indicates the
number of bytes in the Frame Relay header. The two peer LCCEs MUST
agree on the length of the Frame Relay header.
This AVP is exchanged during session negotiation (in ICRQ, ICRP). If
the other LCCE supports a different Frame Relay header length, the
associated L2TP session MUST be torn down via CDN message with result
code 19 (see <a href="#section-3.2">Section 3.2</a>).
If the Frame Relay Header Length AVP is not signalled, it MUST be
assumed that the peer uses a 2-byte Frame Relay header.
The Attribute Value field for this AVP has the following format:
Frame Relay Header Length (ICRQ, ICRP)
0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Frame Relay Header Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Frame Relay Header Length Type is a 2-octet unsigned integer with
the following values defined in this document:
2: Two-octet Frame Relay Header 4: Four-octet Frame Relay Header
This AVP MAY be hidden (the H bit MAY be 0 or 1). The M bit for this
AVP MAY be set to 0 but MAY vary (see <a href="./rfc3931#section-5.2">Section 5.2 of [RFC3931]</a>). The
length (before hiding) of this AVP is 8.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Encapsulation</span>
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>. Data Packet Encapsulation</span>
The FR PDU is transported in its entirety, excluding the opening and
closing High Level Data Link Control (HDLC) flags and the frame check
sequence (FCS). Bit stuffing is undone. The L2TPv3 Session Header
is that as defined in [<a href="./rfc3931" title=""Layer Two Tunneling Protocol - Version 3 (L2TPv3)"">RFC3931</a>]. If sequencing or other features
require presence of an L2-Specific Sublayer, the Default format
defined in <a href="./rfc3931#section-4.6">Section 4.6 of [RFC3931]</a> MUST be used.
<span class="grey">Townsley, 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="./rfc4591">RFC 4591</a> Frame Relay over L2TPv3 July 2006</span>
The FR header is defined in [<a href="#ref-Q922" title=""ISDN Data Link Layer Specification for Frame Mode Bearer Services"">Q922</a>]; however, the notation used
differs from that used in IETF specifications. For reference, the FR
header (referred to as Address Field in [<a href="#ref-Q922" title=""ISDN Data Link Layer Specification for Frame Mode Bearer Services"">Q922</a>]) in IETF notation is
0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| hi dlci |C|0|lo dlci|F|B|D|1|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Two-octet FR Header
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| hi dlci |C|0| dlci |F|B|D|0| dlci |0| dlci_lo |0|1|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Four-octet FR Header
C/R (bit 6) FR frame C/R (command/response) bit [<a href="#ref-Q922" title=""ISDN Data Link Layer Specification for Frame Mode Bearer Services"">Q922</a>].
F - FECN (bit 12): FR FECN (Forward Explicit Congestion
Notification) bit [<a href="#ref-Q922" title=""ISDN Data Link Layer Specification for Frame Mode Bearer Services"">Q922</a>].
B - BECN (bit 13):
FR BECN (Backward Explicit Congestion Notification) bit [<a href="#ref-Q922" title=""ISDN Data Link Layer Specification for Frame Mode Bearer Services"">Q922</a>].
D - DE (bit 14) FR DE bit indicates the discard eligibility [<a href="#ref-Q922" title=""ISDN Data Link Layer Specification for Frame Mode Bearer Services"">Q922</a>].
Usage of the C/R, FECN, BECN, and DE bits is as specified in [<a href="#ref-Q922" title=""ISDN Data Link Layer Specification for Frame Mode Bearer Services"">Q922</a>].
The C/R bit is conveyed transparently. Its value MUST NOT be changed
by the LCCE.
The FECN bit MAY be set by the LCCE to notify the receiving end-user
that the frames it receives have encountered congestion. The end-
user may use this indication for destination-controlled transmit rate
adjustment. The bit must never be cleared by the LCCE. If the LCCE
does not support FECN, it shall pass the bit unchanged.
The BECN bit MAY be set by the LCCE to notify the receiving end-user
that the frames it transmits may encounter congestion. The end-user
may use this indication to adjust its transmit rate. The bit must
never be cleared by the LCCE. If the LCCE does not support BECN, it
shall pass the bit unchanged.
<span class="grey">Townsley, 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="./rfc4591">RFC 4591</a> Frame Relay over L2TPv3 July 2006</span>
The DE bit MAY be set by a policing function on the LCCE to indicate
that this frame SHOULD be discarded in preference to other frames in
a congestion situation. The bit must never be cleared by the LCCE.
If the LCCE does not support DE, it shall pass the bit unchanged.
The encapsulation of Frame Relay frames with the two-octet FR Header
is REQUIRED. The encapsulation of Frame Relay frames with the four-
octet FR Header is OPTIONAL. The encapsulation of Frame Relay frames
with the three-octet FR Header is outside the scope of this document.
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>. Data Packet Sequencing</span>
Data Packet Sequencing MAY be enabled for FRPWs. The sequencing
mechanisms described in [<a href="./rfc3931" title=""Layer Two Tunneling Protocol - Version 3 (L2TPv3)"">RFC3931</a>] MUST be used for signalling
sequencing support. FRPW over L2TP MUST request the presence of the
L2TPv3 Default L2-Specific Sublayer when sequencing is enabled and
MAY request its presence at all times.
If the FRPW is known to be carrying data that does not require packet
order be strictly maintained (such as IP), then packet sequencing for
the FRPW SHOULD NOT be enabled.
<span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a>. MTU Considerations</span>
With L2TPv3 as the tunneling protocol, the packet resulted from the
encapsulation is N bytes longer than Frame Relay frame without the
opening and closing HDLC flags or FCS. The value of N depends on the
following fields:
L2TP Session Header:
Flags, Ver, Res 4 octets (L2TPv3 over UDP only)
Session ID 4 octets
Cookie Size 0, 4, or 8 octets
L2-Specific Sublayer 0 or 4 octets (i.e., with sequencing)
Thus, the range for N in octets is:
N = 4 - 16 L2TPv3 data messages are over IP
N = 16 - 28 L2TPv3 data messages are over UDP
(N does not include the IP header)
The MTU and fragmentation implications resulting from this are
discussed in <a href="./rfc3931#section-4.1.4">Section 4.1.4 of [RFC3931]</a>.
<span class="grey">Townsley, 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="./rfc4591">RFC 4591</a> Frame Relay over L2TPv3 July 2006</span>
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Applicability Statement</span>
The Frame Relay PW emulation described in this document allows a
service provider to offer a Frame Relay PVC-based service across an
IP packet-switched network (PSN). A Frame Relay port-based service
can be offered using [<a href="./rfc4349" title=""High-Level Data Link Control (HDLC) Frames over Layer 2 Tunneling Protocol, Version 3 (L2TPv3)"">RFC4349</a>].
The FRPW emulation has the following characteristics in relationship
to the native service:
o There is a one-to-one mapping between a Frame Relay PVC and an
FRPW, supporting bi-directional transport of variable length
frames. The Frame Relay frame is transported in its entirety,
including the DLCI and the C/R, FECN, BECN, and DE bits, but
excluding the opening and closing flags and the FCS. The egress
LCCE re-writes the DLCI and regenerates the FCS.
o Two- and four-octet address fields are supported. The length is
negotiated between LCCEs during session establishment (see <a href="#section-3.5">Section</a>
<a href="#section-3.5">3.5</a>).
o The availability or unavailability of the PVC is signalled between
LCCEs using the Circuit Status AVP (see <a href="#section-3.4">Section 3.4</a>). Loss of
connectivity between LCCEs can be detected by the L2TPv3 keepalive
mechanism (see <a href="./rfc3931#section-4.4">Section 4.4 in [RFC3931]</a>). These indications can be
used to determine the PVC status to be signalled through [<a href="#ref-Q933" title=""Signalling specifications for frame mode switched and permanent virtual connection control and status monitoring"">Q933</a>]
procedures at the Frame Relay interface.
o The maximum frame size that can be supported is limited by the PSN
MTU, unless fragmentation and reassembly is used (see <a href="./rfc3931#section-4.1.4">Section 4.1.4
of [RFC3931]</a>).
o Sequencing may be enabled on the FRPW to ensure that frames are
delivered in order (see <a href="#section-4.2">Section 4.2</a>).
o Quality of Service characteristics, such as throughput (CIR),
committed burst size (bc), excess burst size (be), and priority,
can be provided by leveraging Quality of Service features of the
LCCEs and the underlying PSN.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Security Considerations</span>
Frame Relay over L2TPv3 is subject to the security considerations
defined in [<a href="./rfc3931" title=""Layer Two Tunneling Protocol - Version 3 (L2TPv3)"">RFC3931</a>]. There are no additional considerations
specific to carrying Frame Relay that are not present for carrying
other data link types.
<span class="grey">Townsley, 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="./rfc4591">RFC 4591</a> Frame Relay over L2TPv3 July 2006</span>
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. IANA Considerations</span>
<span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>. Pseudowire Type</span>
The following value for the Frame Relay DLCI PW Type (see Pseudowire
Capabilities List, as defined in 5.4.3 of [<a href="./rfc3931" title=""Layer Two Tunneling Protocol - Version 3 (L2TPv3)"">RFC3931</a>], and L2TPv3
Pseudowire Types in 10.6 of [<a href="./rfc3931" title=""Layer Two Tunneling Protocol - Version 3 (L2TPv3)"">RFC3931</a>]) is allocated by the IANA
(number space already created as part of publication of [<a href="./rfc3931" title=""Layer Two Tunneling Protocol - Version 3 (L2TPv3)"">RFC3931</a>]):
L2TPv3 Pseudowire Types
-----------------------
0x0001: Frame Relay DLCI Pseudowire Type
<span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>. Result Code AVP Values</span>
This number space is managed by IANA as described in <a href="./rfc3438#section-2.3">Section 2.3 of
[RFC3438]</a>. Three new L2TP Result Codes for the CDN message appear in
<a href="#section-3.2">Section 3.2</a>. The following is a summary:
Result Code AVP (Attribute Type 1) Values
-----------------------------------------
17: PVC was deleted permanently (no longer provisioned)
18: PVC has been INACTIVE for an extended period of time
19: Mismatched FR Header Length
<span class="h3"><a class="selflink" id="section-7.3" href="#section-7.3">7.3</a>. Control Message Attribute Value Pairs (AVPs)</span>
This number space is managed by IANA as described in <a href="./rfc3438#section-2.2">Section 2.2 of
[RFC3438]</a>. An additional AVP Attribute, specified in <a href="#section-3.5">Section 3.5</a>,
was allocated for this specification:
Control Message Attribute Value Pairs
-------------------------------------
85: Frame Relay Header Length
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Acknowledgements</span>
The first Frame Relay over L2TP document, "Frame Relay Service Type
for L2TP", was published in February of 2001, by Nishit Vasavada, Jim
Boyle, Chris Garner, Serge Maskalik, and Vijay Gill. This document
is substantially different, but the basic concept of carrying Frame
Relay over L2TP is the same.
<span class="grey">Townsley, et al. Standards Track [Page 11]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
<span class="grey"><a href="./rfc4591">RFC 4591</a> Frame Relay over L2TPv3 July 2006</span>
Thanks to Lloyd Wood for a razor-sharp review.
Carlos Pignataro helped with review and editing of the document.
During IETF Last Call, Mark Lewis provided thorough review and
comments.
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. References</span>
<span class="h3"><a class="selflink" id="section-9.1" href="#section-9.1">9.1</a>. Normative References</span>
[<a id="ref-RFC3931">RFC3931</a>] Lau, J., Townsley, M., and I. Goyret, "Layer Two Tunneling
Protocol - Version 3 (L2TPv3)", <a href="./rfc3931">RFC 3931</a>, March 2005.
[<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-RFC4349">RFC4349</a>] Pignataro, C. and M. Townsley, "High-Level Data Link
Control (HDLC) Frames over Layer 2 Tunneling Protocol,
Version 3 (L2TPv3)", <a href="./rfc4349">RFC 4349</a>, February 2006.
<span class="h3"><a class="selflink" id="section-9.2" href="#section-9.2">9.2</a>. Informative References</span>
[<a id="ref-RFC3438">RFC3438</a>] Townsley, W., "Layer Two Tunneling Protocol (L2TP) Internet
Assigned Numbers Authority (IANA) Considerations Update",
<a href="https://www.rfc-editor.org/bcp/bcp68">BCP 68</a>, <a href="./rfc3438">RFC 3438</a>, December 2002.
[<a id="ref-Q922">Q922</a>] ITU-T Recommendation Q.922, "ISDN Data Link Layer
Specification for Frame Mode Bearer Services", ITU, Geneva,
1992.
[<a id="ref-Q933">Q933</a>] ITU-T Recommendation Q.933, "Signalling specifications for
frame mode switched and permanent virtual connection
control and status monitoring", ITU, Geneva, 2003.
<span class="grey">Townsley, et al. Standards Track [Page 12]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
<span class="grey"><a href="./rfc4591">RFC 4591</a> Frame Relay over L2TPv3 July 2006</span>
Authors' Addresses
W. Mark Townsley
Cisco Systems
7025 Kit Creek Road
PO Box 14987
Research Triangle Park, NC 27709
EMail: mark@townsley.net
George Wilkie
Cisco Systems
96 Commercial Street
Edinburgh, EH6 6LX
United Kingdom
EMail: gwilkie@cisco.com
Skip Booth
Cisco Systems
7025 Kit Creek Road
PO Box 14987
Research Triangle Park, NC 27709
EMail: ebooth@cisco.com
Stewart Bryant
Cisco Systems
250 Longwater Ave
Green Park
Reading RG2 6GB
United Kingdom
EMail: stbryant@cisco.com
Jed Lau
EMail: jedlau@gmail.com
<span class="grey">Townsley, et al. Standards Track [Page 13]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
<span class="grey"><a href="./rfc4591">RFC 4591</a> Frame Relay over L2TPv3 July 2006</span>
Full Copyright Statement
Copyright (C) The Internet Society (2006).
This document is subject to the rights, licenses and restrictions
contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and <a href="https://www.rfc-editor.org/bcp/bcp79">BCP 79</a>.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
<a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
Acknowledgement
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
Townsley, et al. Standards Track [Page 14]
</pre>
|
