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
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
|
<pre>Network Working Group Y. T'Joens
Request for Comments: 3301 B. Sales
Category: Standards Track Alcatel
P. Crivellari
Belgacom
June 2002
<span class="h1">Layer Two Tunnelling Protocol (L2TP):</span>
<span class="h1">ATM access network extensions</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 (2002). All Rights Reserved.
Abstract
This document augments the procedures described in <a href="./rfc2661">RFC 2661</a> to
further support ATM SVC (Switched Virtual Circuits) or PVC (Permanent
Virtual Circuits) based access networks. L2TP (Layer 2 Tunneling
Protocol) specifies a protocol for tunnelling PPP packets over packet
based networks and over IP networks in particular. L2TP supports
remote access by ISDN and PSTN networks. The extensions defined
within this document allow for asymmetric bi-directional call
establishment and service selection in the ATM access network.
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 .................................................. <a href="#page-2">2</a>
<a href="#section-2">2</a>. Assumptions ................................................... <a href="#page-3">3</a>
<a href="#section-2.1">2.1</a> Topology ..................................................... <a href="#page-3">3</a>
<a href="#section-2.2">2.2</a> Connection Establishment ..................................... <a href="#page-3">3</a>
<a href="#section-2.3">2.3</a> LCP Negotiation .............................................. <a href="#page-3">3</a>
<a href="#section-3">3</a>. ATM access enhanced procedures ................................ <a href="#page-3">3</a>
<a href="#section-3.1">3.1</a> ATM connectivity ............................................. <a href="#page-4">4</a>
<a href="#section-3.2">3.2</a> Tunnel establishment ......................................... <a href="#page-4">4</a>
<a href="#section-3.3">3.3</a> Call establishment ........................................... <a href="#page-5">5</a>
<a href="#section-3.3.1">3.3.1</a> Incoming Call Establishment ................................ <a href="#page-5">5</a>
<a href="#section-3.3.2">3.3.2</a> Outgoing Call Establishment ................................ <a href="#page-6">6</a>
<span class="grey">T'Joens, 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="./rfc3301">RFC 3301</a> L2TP: ATM access network extensions June 2002</span>
<a href="#section-3.4">3.4</a> Framing ...................................................... <a href="#page-6">6</a>
<a href="#section-4">4</a>. Service model issues .......................................... <a href="#page-7">7</a>
<a href="#section-4.1">4.1</a> Authentication ............................................... <a href="#page-7">7</a>
<a href="#section-4.2">4.2</a> Authorization ................................................ <a href="#page-7">7</a>
<a href="#section-5">5</a>. New and extended AVPs ......................................... <a href="#page-7">7</a>
<a href="#section-5.1">5.1</a> New AVP Summary .............................................. <a href="#page-7">7</a>
<a href="#section-5.2">5.2</a> New AVP definition ........................................... <a href="#page-8">8</a>
<a href="#section-5.3">5.3</a> Changed AVP Definition ....................................... <a href="#page-12">12</a>
<a href="#section-6">6</a>. IANA considerations ........................................... <a href="#page-16">16</a>
<a href="#section-7">7</a>. Security considerations ....................................... <a href="#page-17">17</a>
<a href="#section-8">8</a>. Acknowledgements .............................................. <a href="#page-17">17</a>
<a href="#section-9">9</a>. References .................................................... <a href="#page-17">17</a>
<a href="#section-10">10</a>. Authors Addresses ............................................ <a href="#page-18">18</a>
<a href="#section-11">11</a>. Full Copyright Statement ..................................... <a href="#page-19">19</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
L2TP [<a href="./rfc2661" title=""Layer Two Tunnelling Protocol (L2TP)"">RFC2661</a>] defines the procedures for tunneling PPP sessions
between a so called L2TP Access Concentrator (LAC) and an L2TP
Network Server (LNS). The main focus of [<a href="./rfc2661" title=""Layer Two Tunnelling Protocol (L2TP)"">RFC2661</a>] is on supporting
HDLC based ISDN/PSTN access networks.
This document augments the procedures described in [<a href="./rfc2661" title=""Layer Two Tunnelling Protocol (L2TP)"">RFC2661</a>] to
further support ATM SVC or PVC based access networks. Support for
ATM access networks requires extensions to the present L2TP
procedures so as to cope with :
(a) the traffic management aspects of ATM connections (e.g.
asymmetric bandwidth allocation and service category selection
capabilities),
(b) the addressing format to be used in switched ATM networks [<a href="#ref-AESA" title="version 1.0">AESA</a>]
and
(c) the limitations imposed on LCP negotiation by transporting PPP
over AAL5 over the access network segment of the PPP connection
[<a href="./rfc2364" title=""PPP over AAL5"">RFC2364</a>].
Within this document, the necessary extensions to [<a href="./rfc2661" title=""Layer Two Tunnelling Protocol (L2TP)"">RFC2661</a>] are
defined to cope with issues (a) and (b), issue (c) which is not
specific to ATM may be solved as described in [<a href="#ref-L2TP_link" title=""L2TP Link Extensions"">L2TP_link</a>].
<span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a> Conventions</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" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>].
<span class="grey">T'Joens, 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="./rfc3301">RFC 3301</a> L2TP: ATM access network extensions June 2002</span>
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Assumptions</span>
In this section we describe some assumptions that have lead to the
extensions described in this document.
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a> Topology</span>
The procedures as defined in [<a href="./rfc2661" title=""Layer Two Tunnelling Protocol (L2TP)"">RFC2661</a>] apply mainly to access network
technology such as PSTN and ISDN, which may be respectively
asynchronous HDLC and synchronous HDLC based. The aim of this
document is to extend L2TP support to allow for user / LAC
communication based on ATM access network technology.
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a> Connection Establishment</span>
Due to the wide variety of existing signalling protocols and ATM
service categories, and their support or non-support within ATM based
access networks, this document takes as approach to provide for a
flexible identification of ATM connection characteristics while
establishing outgoing and incoming L2TP calls. The procedures as
defined within this document allow the allocation of asymmetric
bandwidth and service category selection in terms of real or non-real
time requirements on the ATM portion of the access network.
As such, the detailed signalling protocol specific information
elements that are necessary for switched VC service, are explicitly
not negotiated during call establishment over the L2TP tunnel.
In order to identify the endpoint of the ATM connection within the
ATM access network, SVCs can be established on the basis of the ATM
end system addressing format [<a href="#ref-AESA" title="version 1.0">AESA</a>]. For PVC based services, the PVC
can either be referred to by using the ATM end system addressing
procedure (Called/Calling Number), or by making use of a textual name
(Service Name). The latter is inspired by the procedures defined
within [<a href="#ref-Auto_PVC" title=""Auto-configuration of PVCs"">Auto_PVC</a>].
<span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a> LCP negotiation</span>
The procedures described within this document may be combined with
the procedures described in [<a href="#ref-L2TP_link" title=""L2TP Link Extensions"">L2TP_link</a>] to limit LCP negotiation
between LNS and user, so as to enforce PPP over AAL5 specific LCP
negotiation [<a href="./rfc2364" title=""PPP over AAL5"">RFC2364</a>].
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. ATM access enhanced procedures</span>
In order to illustrate the procedures specified within this document,
this section will provide an operational description of Virtual
dial-up access through an ATM based access network (e.g., ADSL).
<span class="grey">T'Joens, 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="./rfc3301">RFC 3301</a> L2TP: ATM access network extensions June 2002</span>
Note that the emphasis is on the changes proposed within this
document relative to [<a href="./rfc2661" title=""Layer Two Tunnelling Protocol (L2TP)"">RFC2661</a>].
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a> ATM connectivity</span>
Prior to initiating the PPP protocol layer, a Virtual Connection (VC)
MUST be established between the user and the Network Access Server
(LAC). This virtual connection MAY either be a preconfigured
Permanent VC(PVC), where the access network provider, NAS and user
agree beforehand on the characteristics of the PVC, or MAY be an on-
demand switched VC(SVC), where the negotiation between user, network
and NAS takes place by means of an ATM signalling protocol. Note
that for establishing PVCs, alternative use may be made of the
procedures as described in [<a href="#ref-Auto_PVC" title=""Auto-configuration of PVCs"">Auto_PVC</a>].
In both cases, the user is referred to as the virtual dial-in user.
Prior to accepting the switched connection from the virtual dial-in
user, the LAC MAY check with the LNS whether the call should be
accepted. In the latter situation, the LAC MAY determine based upon
parameters available within the call establishment message that this
concerns a virtual dial in user, or MAY undertake a partial
authentication of the end system/user, in order to bind the end
system/user with a specific LNS.
For PVC based users, the LAC MAY be triggered by the arrival of an
LCP Configure Request, or PPP Authentication request message from the
virtual dial-in user to initiate conversation with the LNS. Note
that the exact timing of triggering communication between LAC and LNS
is outside the scope of this document.
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a> Tunnel establishment</span>
If no tunnel connection currently exists to the desired LNS, one is
initiated. During the tunnel establishment, LNS and LAC indicate
bearer and framing capabilities to each other, according to normal
procedures.
The bearer capability is extended to allow the LAC to indicate its
support of ATM bearer devices. Positive receipt of this indication,
allows both LAC and LNS to use the extensions as defined within this
document to support ATM based incoming and outgoing calls.
If no compatibility between LNS and LAC exists according to the
extensions defined within this document, no tunnel establishment can
take place. This would be because the LAC does not support any
bearer capability which is expected by the LNS (e.g., an ATM based
LAC, that only signals the "Broadband" Bearer Capability), or vice
<span class="grey">T'Joens, 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="./rfc3301">RFC 3301</a> L2TP: ATM access network extensions June 2002</span>
versa. It is however encouraged that LAC or LNS implementations
would allow for seamless interworking with peer devices which do not
implement the extensions defined within this document. This could be
implemented by allowing a graceful fallback to digital bearer
capability.
<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a> call establishment</span>
During incoming and outgoing broadband call establishment, the
following extensions are defined to existing procedures.
<span class="h4"><a class="selflink" id="section-3.3.1" href="#section-3.3.1">3.3.1</a> Incoming Call Establishment</span>
The ATM connection between the virtual Dial-in user and LAC MAY
either be dynamically or statically established. When the VC
connection is dynamically established (Switched VC), the LAC will
receive a SETUP message over the interface that connects it to the
ATM network. This specification does not assume any specific
interface type (UNI or NNI). Permanent VC connections MAY either be
manually configured, or configured by use of the extensions to the
ILMI procedures as defined by [<a href="#ref-Auto_PVC" title=""Auto-configuration of PVCs"">Auto_PVC</a>].
For switched VC connections, the LAC MAY select the peer LNS on the
basis of connection establishment information, or by allowing partial
PPP authentication of the virtual Dial-in user. The connection
establishment information that can be used by the LAC include Called
Party AESA, Called Party AESA Subaddress, Calling Party AESA or
Calling Party AESA Subaddress.
For Permanent VC connections, the LAC MAY be triggered by (a) the
establishment of the PVC, (b) by an LCP configure request, (c) by
partially authenticating the virtual Dial-in user, or (d) by means
outside the scope of this specification.
Within the ICRQ, the LAC MUST indicate a broadband bearer in the
Bearer Type AVP (B bit set to 1), MAY include the Service Category
AVP, and MAY include the Service Name AVP. If the LNS would not
support the B Bearer bit, it will return an error on the ICRQ
message. In such a case, the implementation MAY decide to fall back
to digital bearer capability, and SHOULD refrain from using the
extensions defined within this document. Further, the ICRQ message
MAY contain the VPI/VCI identifier AVP. This identifier can further
be used at the LNS for management purposes next to or alternative to
the Physical Channel ID AVP.
Within the ICCN, both Tx Connect Speed AVP and Rx Connect Speed
SHOULD be used if an asymetric connection has been established.
<span class="grey">T'Joens, 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="./rfc3301">RFC 3301</a> L2TP: ATM access network extensions June 2002</span>
<span class="h4"><a class="selflink" id="section-3.3.2" href="#section-3.3.2">3.3.2</a> Outgoing Call Establishment</span>
Within an OCRQ, the LNS MUST indicate to the LAC minimum and maximum
speeds for receive and transmit traffic (from the LAC perspective).
This is to allow for the bi-directional asymmetric nature of ATM
traffic contracts. Note that in order to support UBR connections
between LAC and user, the Minimum BPS MUST be set to zero.
Further during OCRQ, the LNS MAY include the required Service
Category AVP, i.e., indicating real time (rt) or non-real time (nrt)
transport services. The combination of minimum and maximum receive
and transmit speed, and the indication of the required service
category allows the LAC to establish an ATM connection according to
its own capabilities, and the ATM access network capabilities,
however within the service requirement for the PPP layer.
Real time connectivity can be provided by either CBR or rt-VBR ATM
service categories, non-real time connectivity can be provided by
UBR, nrt-VBR, ABR or GFR ATM service categories.
Further the LNS MUST indicate to the LAC in OCRQ message the called
number according to the format described in this document (NSAP
format). When the called number carries an all zero payload, the LAC
SHOULD look at the Service Name AVP to bind the tunnel call to an ATM
VC connection.
Next to the normal AVPs, the OCRP message MAY contain the VPI/VCI
identifier AVP. This identifier can further be used at the LNS for
management purposes next to or alternative to the Physical Channel ID
AVP.
<span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a> Framing</span>
Within this document the PPP PDU refers to the concatenation of PPP
protocol ID, PPP Information and PPP padding fields.
In the direction of user to LNS, the PPP PDU will be carried on top
of an AAL5 connection between user and LAC. The LAC MUST strip off
the AAL5 specific fields based on the encapsulation mechanism in use
on the ATM connection, i.e. VC multiplexed or LLC encapsulated
[<a href="./rfc2364" title=""PPP over AAL5"">RFC2364</a>], and MUST encapsulate the PPP PDU with address and control
field, as per HDLC procedures, on the L2TP tunnel.
In the direction of LNS to user, the PPP PDU will be carried on top
of an AAL5 connection between LAC and user. The LAC MUST strip the
PPP PDU from the address and control field on the L2TP tunnel, and
<span class="grey">T'Joens, 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="./rfc3301">RFC 3301</a> L2TP: ATM access network extensions June 2002</span>
insert the AAL5 specific fields based on the encapsulation mechanism
in use on the ATM connection, i.e. VC multiplexed or LLC
encapsulated.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Service model issues</span>
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a> Authentication</span>
In case of ATM switched VC establishment, calling party number
information may be used for first level authentication much in the
same way as for PSTN or ISDN access. In case of permanent VC
establishment, authentication may not be an issue from the LAC side,
because of the permanent character of the VC. Bilateral agreement
between LAC and LNS providers may eliminate the authentication phase
in the latter case.
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a> Authorization</span>
Because of the flexibility of establishing ATM connections with
varying parameters, some authorization may be required prior to
accepting the establishment of a switched ATM connection from the
user with certain ATM traffic parameters. This authorization may be
performed against the ATM specific authentication information (e.g.
calling line id), or may be performed after partial authentication of
the user at the PPP level. Non authorized access requests result in
connection release.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. New and extended AVPs</span>
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a> New AVP Summary</span>
The following table lists the extra AVPs that are defined within this
document. The "attr" column indicates the integer value assigned to
this attribute. Note that the attribute value is relative compared
to the vendor ID. The "M" column indicates the setting of the
"Mandatory" bit of the AVP header for each attribute. The "LEN"
column indicates the size of the AVP including the AVP header. A "+"
in this column indicates that the length varies depending upon the
length of the actual contents of the value field.
The usage list for each entry indicates the message types that
utilize each AVP. An abbreviation shown in mixed or upper case
letters indicates that the corresponding AVP MUST be present in this
message type. All lower case indicates that the AVP MAY optionally
appear in this message type. Some AVPs MAY be present only when a
corresponding optional AVP or specific setting within the AVP is
present, these AVPs are shown in lower case as well.
<span class="grey">T'Joens, 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="./rfc3301">RFC 3301</a> L2TP: ATM access network extensions June 2002</span>
Attr M Len Attribute Name (usage)
40 0 10 Rx Minimum BPS (ocrq)
32-bit integer indicating the lowest acceptable line speed for the
call in the receive direction. Rx indicates the user to LAC
direction.
41 0 10 Rx Maximum BPS (ocrq)
32-bit integer indicating the highest acceptable line speed for
call in the receive direction. Rx indicates the user to LAC
direction.
42 0 8 Service Category (ocrq, icrq)
The Service Category indicates the service expected for the call,
e.g., real time or non-real time.
43 0 6+ Service Name (ocrq, icrq)
The Service Name indicates the service name linked to a
preestablished PVC.
44 0 26 Calling Sub-Address(icrq)
20 octet binary encoded NSAP subaddress indicating the Calling
Party Sub-Address.
45 0 10 VPI/VCI identifier (icrq, ocrp)
10 octet binary encoded identification of VPI/VCI values used for
incoming calls.
<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a> New AVP definition</span>
The following lists the new AVPs defined within this document, and
describes the expected behaviour when this AVP would be present
within a message.
Rx Minimum BPS (OCRQ)
The Rx Minimum BPS, Attribute Type 40, encodes the lowest
acceptable line speed for this call in the receive direction,
for these cases where asymmetric transmission is required.
The Attribute Value field for this AVP 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Rx Minimum BPS |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Rx Minimum BPS is a 32 bit value indicating the speed in
bits per second.
<span class="grey">T'Joens, 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="./rfc3301">RFC 3301</a> L2TP: ATM access network extensions June 2002</span>
This AVP MAY be included within the OCRQ, and SHOULD only be
included when the LAC indicated broadband bearer support in the
bearer capabilities AVP during tunnel establishment.
This AVP may be hidden (the H-bit may be set to 0 or 1). The
M- bit for this AVP must be set to 0. The Length (before
hiding) of this AVP is 10.
Rx Maximum BPS
The Rx Maximum BPS, Attribute Type 41, encodes the highest
acceptable line speed for this call in the receive direction,
for these cases where asymmetric transmission is required.
The Attribute Value field for this AVP 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Rx Maximum BPS |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Rx Maximum BPS is a 32 bit value indicating the speed in
bits per second.
This AVP MAY be included within the OCRQ, and SHOULD only be
included when the LAC indicated broadband bearer support in the
bearer capabilities AVP during tunnel establishment.
This AVP may be hidden (the H-bit may be set to 0 or 1). The
M- bit for this AVP must be set to 0. The Length (before
hiding) of this AVP is 10.
Service Category
The Service Category AVP, Attribute type 42, indicates optional
extra information on the Quality of Service expected for the
call establishment on the broadband bearer medium.
The Attribute Value field for this AVP has the following
format:
0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Resvd for future QoS ind. |S|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
<span class="grey">T'Joens, 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="./rfc3301">RFC 3301</a> L2TP: ATM access network extensions June 2002</span>
The Attribute Value field is a 16-bit mask, with one bit
defined. The S bit indicates either non real time (S bit set
to 0) or real time (S bit set to 1) service requirement. The
other bit fields are reserved for future use.
The Service Category AVP MAY be present in OCRQ and ICRQ
messages, and SHOULD only be included when the LAC indicated
broadband bearer support in the bearer capabilities AVP during
tunnel establishment.
This AVP may be hidden (the H-bit may be set to 0 or 1). The
M- bit for this AVP must be set to 0. The Length (before
hiding) of this AVP is 8.
Service Name
The Service Name AVP, Attribute Type 43, provides the peer with
an textual name for referring to an ATM VC connection.
The Attribute Value field for this AVP 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Service Name (arbitrary number of octets) ....
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Service Name is of arbitrary length, but must be at least 1
octet. The Service Name is UTF-8 encoded. [<a href="#ref-10646" title="May 1993">10646</a>]
The Service Name should be unique at least to the LNS/LAC
combination.
The Service Name AVP MAY only be provided when the Called
Number field is encoded as all zeros in OCRQ. The Service Name
AVP MAY be present in OCRQ and ICRQ messages, and SHOULD only
be included when the LAC indicated broadband bearer support in
the bearer capabilities AVP during tunnel establishment.
This AVP may be hidden (the H-bit may be set to 0 or 1). The
M- bit for this AVP must be set to 0. The length of this
attribute is arbitrary, however at least 7.
Calling Sub-Address (ICRQ)
The Calling Sub-Address AVP, Attribute Type 44, encodes
additional Calling Party subaddress information.
<span class="grey">T'Joens, 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="./rfc3301">RFC 3301</a> L2TP: ATM access network extensions June 2002</span>
The Attribute Value field for this AVP 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| NSAP |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| NSAP (cont'd) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| NSAP (cont'd) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| NSAP (cont'd) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| NSAP (cont'd) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Calling Sub-Address AVP MUST be encoded as a 20 octet
binary encoded NSAP address when the B bit is set in the Bearer
Type AVP. The NSAP binary encoded address provides a broader
range of address encapsulation methods than an ASCII field.
The structure of the NSAP address (e.g., E.164, ICD, DCC) is
defined in [<a href="#ref-AESA" title="version 1.0">AESA</a>].
The Calling Sub-Address number AVP MAY be present in ICRQ, and
SHOULD only be available if the Calling Party number is also
within the message.
This AVP may be hidden (the H-bit may be 0 or 1). The M-bit
for this AVP MUST be set to 0. The Length (before hiding) of
this AVP is 26.
VPI/VCI identifier(icrq, ocrp)
The VPI/VCI identifier, Attribute Type 45, encodes the VPI/VCI
value used at the ATM interface at the LAC.
The Attribute Value field for this AVP 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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|resvd | VPI | VCI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The VPI/VCI identifier is a 32 bit value encoding the VPI(12
bits) and VCI (16 bits) value.
<span class="grey">T'Joens, 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="./rfc3301">RFC 3301</a> L2TP: ATM access network extensions June 2002</span>
This AVP MAY be included within the ICRQ and OCRP, and SHOULD
only be included when the LAC indicated broadband bearer
support in the bearer capabilities AVP during tunnel
establishment.
This AVP may be hidden (the H-bit may be set to 0 or 1). The
M- bit for this AVP must be set to 0. The Length (before
hiding) of this AVP is 10.
<span class="h3"><a class="selflink" id="section-5.3" href="#section-5.3">5.3</a> Changed AVP Definition</span>
The following AVPs see their contents changed relative to [<a href="./rfc2661" title=""Layer Two Tunnelling Protocol (L2TP)"">RFC2661</a>]
in order to support the procedures described in this document.
Bearer Capabilities
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Resvd for future bearer capability definitions |B|A|D|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The bearer Capabilities AVP within a SCCRQ or SCCRP indicates
the bearer capabilities that the sender of this message can
provide for outgoing calls. This document extends the existing
AVP with the B bit. If bit B is set, broadband access is
supported (ATM).
Attempts to establish an outgoing call with the bearer type set
to B, while the bearer capability did not indicate this
capability will result in the call being rejected with Result
Code 5 'Call failed due to lack of appropriate facilities being
available (permanent condition)'.
In these cases where the LAC only supports the B bit, and the
LNS would not recognize the B bit, no outgoing calls are
possible. Note that when the LAC only has ATM based devices,
it may still opt for seamless fall back to digital bearer
types.
This specification assumes a non-compliant LNS to categorize a
Bearer Capabilities AVP where the B bit is set as unrecognized
AVP, upon which the tunnel establishment will fail. This is to
be indicated by a Result Code '2-General error - Error Code
indicates the problem', Error Code '3- Reserved field was non-
zero'.
<span class="grey">T'Joens, 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="./rfc3301">RFC 3301</a> L2TP: ATM access network extensions June 2002</span>
(Tx) Minimum BPS
The (Tx) Minimum BPS AVP encodes the lowest acceptable line
speed for this call in the transmit direction. The (Tx)
Minimum BPS AVP MAY be used in OCRQ. If the Rx Minimum BPS
AVP, as defined within this document, is not available in the
message, then symmetric transmission is implied, with both
minimum receive and transmit bit-rates equal to Minimum BPS.
(Tx) Maximum BPS
(Tx) Maximum BPS AVP encodes the highest acceptable line speed
for this call in the transmit direction. The (Tx) Maximum BPS
AVP MAY be used in OCRQ. If the Rx Maximum BPS AVP, as defined
within this document, is not available in the message, then
symmetric transmission is implied, with both maximum receive
and transmit bitrates equal to Maximum BPS.
Bearer Type
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Resvd for future bearer types definitions |B|A|D|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The bearer type AVP encodes the bearer type for the requested
call. This document extends the bearer types with an
indication of ATM bearer support (B-bit). If bit B is set,
broadband access is requested (ATM). If bit A is set, analogue
access is requested. If bit D is set, Digital access is
requested.
Note that in the OCRQ all 3 bits (B,A,D) may be set indicating
that the call may be of either type. The B bit SHOULD only be
set if the Broadband capability was indicated during tunnel
establishment.
Q.931 Cause Code
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Cause Code | Cause Msg | Advisory Msg...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
<span class="grey">T'Joens, 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="./rfc3301">RFC 3301</a> L2TP: ATM access network extensions June 2002</span>
The Cause code is not changed from [<a href="./rfc2661" title=""Layer Two Tunnelling Protocol (L2TP)"">RFC2661</a>], except for the
fact that it can also carry Cause Codes specific to ATM
signalling messages, these cause codes can be found in ATM
Forum UNI 4.0 [<a href="#ref-UNI" title="July">UNI</a>] and the references thereof. The Cause code
should be interpreted relative to the Bearer Type in use for
the specific call.
Called Number
The Called Number AVP, Attribute Type 21, encodes the AESA
number to be called for an OCRQ, and the Called number at the
LAC for an ICRQ.
The Attribute Value field for this AVP has a changed encoding
from [<a href="./rfc2661" title=""Layer Two Tunnelling Protocol (L2TP)"">RFC2661</a>]:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| NSAP |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| NSAP (cont'd) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| NSAP (cont'd) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| NSAP (cont'd) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| NSAP (cont'd) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Called Number AVP MUST be encoded as a 20 octet binary
encoded NSAP address when the B bit is set in the Bearer Type
AVP. The NSAP binary encoded address provides a broader range
of address encapsulation methods than an ASCII field. The
structure of the NSAP address (e.g., E.164, ICD, DCC) is
defined in [<a href="#ref-AESA" title="version 1.0">AESA</a>].
The Called number AVP MUST be present in OCRQ, and MAY be
present in ICRQ.
If the Called Number AVP in an OCRQ carries an all zero NSAP
address, the Service Name AVP SHOULD provide further
information to bind the L2TP call to a specific VC connection.
See also [<a href="#ref-Auto_PVC" title=""Auto-configuration of PVCs"">Auto_PVC</a>].
<span class="grey">T'Joens, et al. Standards Track [Page 14]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
<span class="grey"><a href="./rfc3301">RFC 3301</a> L2TP: ATM access network extensions June 2002</span>
This AVP may be hidden (the H-bit may be 0 or 1). The M-bit
for this AVP MUST be set to 0. The Length (before hiding) of
this AVP is 26.
Calling Number
The Calling Number AVP, Attribute Type 22, encodes the Calling
Party AESA as received from the Virtual Dial-in User.
The Attribute Value field for this AVP has a changed encoding
from [<a href="./rfc2661" title=""Layer Two Tunnelling Protocol (L2TP)"">RFC2661</a>]:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| NSAP |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| NSAP (cont'd) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| NSAP (cont'd) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| NSAP (cont'd) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| NSAP (cont'd) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Calling Number AVP MUST be encoded as a 20 octet binary
encoded NSAP address when the B bit is set in the Bearer Type
AVP. The NSAP binary encoded address provides a broader range
of address encapsulation methods than an ASCII field. The
structure of the NSAP address (e.g., E.164, ICD, DCC) is
defined in [<a href="#ref-AESA" title="version 1.0">AESA</a>].
The Calling number AVP MAY be present in ICRQ.
This AVP may be hidden (the H-bit may be 0 or 1). The M-bit
for this AVP MUST be set to 0. The Length (before hiding) of
this AVP is 26.
Sub-Address
The Sub-Address AVP, Attribute Type 23, encodes additional
Called Party subaddress information.
The Attribute Value field for this AVP has a changed encoding
from [<a href="./rfc2661" title=""Layer Two Tunnelling Protocol (L2TP)"">RFC2661</a>]:
<span class="grey">T'Joens, et al. Standards Track [Page 15]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
<span class="grey"><a href="./rfc3301">RFC 3301</a> L2TP: ATM access network extensions June 2002</span>
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| NSAP |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| NSAP (cont'd) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| NSAP (cont'd) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| NSAP (cont'd) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| NSAP (cont'd) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Sub-Address AVP MUST be encoded as a 20 octet binary
encoded NSAP address when the B bit is set in the Bearer Type
AVP. The NSAP binary encoded address provides a broader range
of address encapsulation methods than an ASCII field. The
structure of the NSAP address (e.g., E.164, ICD, DCC) is
defined in [<a href="#ref-AESA" title="version 1.0">AESA</a>].
The Sub-Address number AVP MAY be present in ICRQ and OCRQ, and
SHOULD only be available if the Called Party number is also
within the message.
This AVP may be hidden (the H-bit may be 0 or 1). The M-bit
for this AVP MUST be set to 0. The Length (before hiding) of
this AVP is 26.
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. IANA Considerations</span>
This document requires IANA to allocate 6 new type values for the
following AVPs (see <a href="#section-5.2">section 5.2</a>) :
- Rx Minimum BPS
- Rx Maximum BPS
- Service Category
- Service Name
- Calling Sub-Address
- VPI/VCI Identifier
This document further defines a new bit (B) in the bearer
capabilities and bearer type AVPs (<a href="#section-5.3">section 5.3</a>).
<span class="grey">T'Joens, et al. Standards Track [Page 16]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
<span class="grey"><a href="./rfc3301">RFC 3301</a> L2TP: ATM access network extensions June 2002</span>
This document defines a flag field in the Service Category AVP, only
one bit in this flag has been assigned within this document (S).
Further assignments fall under the rule of "Specification Required",
i.e. Values and their meaning must be documented in an RFC or other
permanent and readily available reference, in sufficient detail so
that interoperability between independent implementations is
possible.
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Security Considerations</span>
No extra security risk outside these specified by [<a href="./rfc2661" title=""Layer Two Tunnelling Protocol (L2TP)"">RFC2661</a>] are
foreseen.
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Acknowledgements</span>
The authors would like to thank Laurent Hermans for his work on
earlier versions of this document, Juha Heinanen (Telia) and David
Allen (Nortel Networks) for their constructive discussion on the
document during the Minneapolis IETF meeting, Mark Townsley (cisco)
for his hint on the use of the VPI/VCI identifier AVP.
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. References</span>
[<a id="ref-RFC2661">RFC2661</a>] Townsley, W., Valencia, A., Rubens, A., Singh Pall, G.,
Zorn, G. and B. Palter, "Layer Two Tunnelling Protocol
(L2TP)", <a href="./rfc2661">RFC 2661</a>, August 1999.
[<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-RFC2364">RFC2364</a>] Gross, G., Kaycee, M., Lin, A., Malis, A. and J.
Stephens, "PPP over AAL5", <a href="./rfc2364">RFC 2364</a>, July 1998.
[<a id="ref-UNI">UNI</a>] User-Network Interface (UNI) Specification, Version 4.0,
ATM Forum, July, 1996
[<a id="ref-AESA">AESA</a>] ATM Forum Addressing : Reference Guide, version 1.0, ATM
Forum, Final Ballot, January 1999
[<a id="ref-L2TP_link">L2TP_link</a>] Townsley, M. and W. Palter, <a style="text-decoration: none" href='https://www.google.com/search?sitesearch=datatracker.ietf.org%2Fdoc%2Fhtml%2F&q=inurl:draft-+%22L2TP+Link+Extensions%22'>"L2TP Link Extensions"</a>, Work
in Progress.
[<a id="ref-Auto_PVC">Auto_PVC</a>] ATM Forum, "Auto-configuration of PVCs", af-nm-0122.000,
March 1999
[<a id="ref-10646">10646</a>] ISO/IEC, Information Technology - Universal Multiple-
Octet Coded Character Set (UCS) - Part 1: Architecture
and Basic Multilingual Plane, May 1993, with amendments
<span class="grey">T'Joens, et al. Standards Track [Page 17]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
<span class="grey"><a href="./rfc3301">RFC 3301</a> L2TP: ATM access network extensions June 2002</span>
<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. Authors Addresses</span>
Yves T'joens
Alcatel Network Strategy Group
Francis Wellesplein 1, 2018 Antwerp, Belgium
Phone : +32 3 240 7890
EMail : yves.tjoens@alcatel.be
Paolo Crivellari
Belgacom
bd du Roi Albert II 27
B-1030 Bruxelles
Phone: +32 2 202 9698
EMail: paolo.crivellari@belgacom.be
Bernard Sales
Alcatel Network Strategy Group
Francis Wellesplein 1, 2018 Antwerp, Belgium
Phone : +32 3 240 9574
EMail : bernard.sales@alcatel.be
<span class="grey">T'Joens, et al. Standards Track [Page 18]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
<span class="grey"><a href="./rfc3301">RFC 3301</a> L2TP: ATM access network extensions June 2002</span>
<span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>. Full Copyright Statement</span>
Copyright (C) The Internet Society (2002). All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS 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.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
T'Joens, et al. Standards Track [Page 19]
</pre>
|
