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
|
Layer Two Tunneling Protocol "L2TP" - [RFC2661]
(last updated 2007-12-17)
Registries included below:
- Control Message Attribute Value Pairs
- Message Type AVP (Attribute Type 0) Values
- Result Code AVP (Attribute Type 1) Values
- Proxy Authen Type AVP (Attribute Type 29) Values
- Service Category AVP (Attribute Type 42) Flag Field
- PPP Disconnect Cause Code (Attribute Type 46) Values
- ATM Alarm Status AVP (Attribute Type 88) Values
- Bearer Field definition
- Framing Field definition
- Leading Bits of the L2TP AVP Header
- Leading Bits of the L2TP Message Header
- L2TPv3 Pseudowire Types
- Circuit Status Bits
- Default L2-Specific Sublayer bits
- L2-Specific Sublayer Type
- Data Sequencing Level
- ATM-Specific Sublayer bits
Registry Name: Control Message Attribute Value Pairs
Reference: [RFC3438]
For registration procedures, please see [RFC3438].
To maximize extensibility while still permitting interoperability, a
uniform method for encoding message types and bodies is used
throughout L2TP. This encoding will be termed AVP (Attribute-Value
Pair).
The following sections contain a list of all L2TP AVPs defined in RFC
2661.
Attribute
Type Description Reference
--------- ------------------ ---------
0 Message Type AVP [RFC2661]
Also, see Message Type AVP values below
1 Result Code AVP [RFC2661]
Also, see Result Code AVP values below
2 Protocol Version AVP [RFC2661]
3 Framing Capabilities AVP [RFC2661]
Also, see Framing Field definition below
4 Bearer Capabilities AVP [RFC2661]
Also, see Bearer Field definition below
5 Tie Breaker AVP [RFC2661]
6 Firmware Revision AVP [RFC2661]
7 Host Name AVP [RFC2661]
8 Vendor Name AVP [RFC2661]
9 Assigned Tunnel ID AVP [RFC2661]
10 Receive Window Size AVP [RFC2661]
11 Challenge AVP [RFC2661]
12 Q.931 Cause Code AVP [RFC2661]
13 Response AVP [RFC2661]
14 Assigned Session ID AVP [RFC2661]
15 Call Serial Number AVP [RFC2661]
16 Minimum BPS AVP [RFC2661]
17 Maximum BPS AVP [RFC2661]
18 Bearer Type AVP [RFC2661]
Also, see Bearer Field definition below
19 Framing Type AVP [RFC2661]
Also, see Framing Field definition below
20 Reserved [RFC2661]
21 Called Number AVP [RFC2661]
22 Calling Number AVP [RFC2661]
23 Sub-Address AVP [RFC2661]
24 (Tx) Connect Speed BPS AVP [RFC2661]
25 Physical Channel ID AVP [RFC2661]
26 Initial Received LCP CONFREQ AVP [RFC2661]
27 Last Sent LCP CONFREQ AVP [RFC2661]
28 Last Received LCP CONFREQ AVP [RFC2661]
29 Proxy Authen Type AVP [RFC2661]
Also, see Proxy Authen Type AVP Values below
30 Proxy Authen Name AVP [RFC2661]
31 Proxy Authen Challenge AVP [RFC2661]
32 Proxy Authen ID AVP [RFC2661]
33 Proxy Authen Response AVP [RFC2661]
34 Call Errors AVP [RFC2661]
35 ACCM AVP [RFC2661]
36 Random Vector AVP [RFC2661]
37 Private Group ID AVP [RFC2661]
38 Rx Connect Speed AVP [RFC2661]
39 Sequencing Required AVP [RFC2661]
40 Rx Minimum BPS [RFC3301]
41 Rx Maximum BPS [RFC3301]
42 Service Category [RFC3301]
Also, see Service Category AVP Flag Fields
below
43 Service Name [RFC3301]
44 Calling Sub-Address [RFC3301]
45 VPI/VCI Identifier [RFC3301]
46 PPP Disconnect Cause Code [RFC3145]
Also, see PPP Disconnect Cause Code Values
below
47 CCDS AVP [RFC3308]
48 SDS AVP [RFC3308]
49 LCP Want Options [RFC3437]
50 LCP Allow Options [RFC3437]
51 LNS Last Sent LCP Confreq [RFC3437]
52 LNS Last Received LCP Confreq [RFC3437]
53 Modem On-Hold Capable AVP [RFC3573]
54 Modem On-Hold Status AVP [RFC3573]
55 PPPoE Relay AVP [RFC3817]
56 PPPoE Relay Response Capability AVP [RFC3817]
57 PPPoE Relay Forward Capability AVP [RFC3817]
58 Extended Vendor ID AVP [RFC3931]
59 Message Digest [RFC3931]
60 Router ID [RFC3931]
61 Assigned Control Connection ID [RFC3931]
62 Pseudowire Capabilities List [RFC3931]
63 Local Session ID [RFC3931]
64 Remote Session ID [RFC3931]
65 Assigned Cookie [RFC3931]
66 Remote End ID [RFC3931]
67 Application Code [RFC3931]
68 Pseudowire Type [RFC3931]
69 L2-Specific Sublayer [RFC3931]
70 Data Sequencing [RFC3931]
71 Circuit Status [RFC3931]
72 Preferred Language [RFC3931]
73 Control Message Authentication Nonce [RFC3931]
74 Tx Connect Speed [RFC3931]
75 Rx Connect Speed [RFC3931]
76 Failover Capability [RFC4951]
77 Tunnel Recovery [RFC4951]
78 Suggested Control Sequence [RFC4951]
79 Failover Session State [RFC4951]
80 Multicast Capability [RFC4045]
81 New Outgoing Sessions [RFC4045]
82 New Outgoing Sessions Acknowledgement [RFC4045]
83 Withdraw Outgoing Sessions [RFC4045]
84 Multicast Packets Priority [RFC4045]
85 Frame-Relay Header Length [RFC4591]
86 ATM Maximum Concatenated Cells AVP [RFC4454]
87 OAM Emulation Required AVP [RFC4454]
88 ATM Alarm Status AVP [RFC4454]
Also, see ATM Alarm Status AVP Values below
89 Attachment Group Identifier [RFC4667]
90 Local End Identifier [RFC4667]
91 Interface Maximum Transmission Unit [RFC4667]
92 FCS Retention [RFC4720]
93 Tunnel Switching Aggregator ID AVP [draft-ietf-l2tpext-tunnel-switching-06.txt]
94 Maximum Receive Unit (MRU) AVP [RFC4623]
95 Maximum Reassembled Receive Unit (MRRU) AVP [RFC4623]
96 VCCV Capability AVP [RFC5085]
Message Type AVP (Attribute Type 0) Values
------------------------------------------
Control Connection Management
0 (reserved)
1 (SCCRQ) Start-Control-Connection-Request
2 (SCCRP) Start-Control-Connection-Reply
3 (SCCCN) Start-Control-Connection-Connected
4 (StopCCN) Stop-Control-Connection-Notification
5 (reserved)
6 (HELLO) Hello
20 (ACK) Explicit Acknowledgement [RFC3931]
Call Management
7 (OCRQ) Outgoing-Call-Request
8 (OCRP) Outgoing-Call-Reply
9 (OCCN) Outgoing-Call-Connected
10 (ICRQ) Incoming-Call-Request
11 (ICRP) Incoming-Call-Reply
12 (ICCN) Incoming-Call-Connected
13 (reserved)
14 (CDN) Call-Disconnect-Notify
Link Status
15 (WEN) WAN-Error-Notify
16 (SLI) Set-Link-Info
17 (MDMST) Modem Status [RFC3573]
PPPoE Relay
18 (SRRQ) Service Relay Request Message [RFC3817]
19 (SRRP) Service Relay Reply Message [RFC3817]
Multicast Management
23 (MSRQ) Multicast-Session-Request [RFC4045]
24 (MSRP) Multicast-Session-Response [RFC4045]
25 (MSE) Multicast-Session-Establishment [RFC4045]
26 (MSI) Multicast-Session-Information [RFC4045]
27 (MSEN) Multicast-Session-End-Notify [RFC4045]
Failover Management
21 (FSQ) Failover Session Query [RFC4951]
22 (FSR) Failover Session Response [RFC4951]
Result Code AVP (Attribute Type 1) Values
-----------------------------------------
Defined Result Code values for the StopCCN message are:
0 - Reserved
1 - General request to clear control connection
2 - General error--Error Code indicates the problem
3 - Control channel already exists
4 - Requester is not authorized to establish a control
channel
5 - The protocol version of the requester is not
supported
Error Code indicates highest version supported
6 - Requester is being shut down
7 - Finite State Machine error
8 - Control connection due to mismatching CCDS value [RFC3308]
Defined Result Code values for the CDN message are:
0 - Reserved
1 - Call/Session disconnected due to loss of carrier
2 - Call/Session disconnected for the reason indicated
in error code
3 - Call/Session disconnected for administrative reasons
4 - Call/Session failed due to lack of appropriate facilities
being available (temporary condition)
5 - Call/Session failed due to lack of appropriate facilities being
available (permanent condition)
6 - Invalid destination
7 - Call failed due to no carrier detected
8 - Call failed due to detection of a busy signal
9 - Call failed due to lack of a dial tone
10 - Call was not established within time allotted by LAC
11 - Call was connected but no appropriate framing was
detected
12 - Disconnecting call due to mismatching SDS value [RFC3308]
13 - Session not established due to losing tie breaker (L2TPv3). [RFC3931]
14 - Session not established due to unsupported PW type (L2TPv3). [RFC3931]
15 - Session not established, sequencing required without valid [RFC3931]
L2-Specific Sublayer (L2TPv3).
16 - Finite state machine error or timeout. [RFC3931]
17 - FR PVC was deleted permanently (no longer provisioned) [RFC4591]
18 - FR PVC has been INACTIVE for an extended period of time [RFC4591]
19 - Mismatched FR Header Length [RFC4591]
20 - HDLC Link was deleted permanently (no longer provisioned) [RFC4349]
21 - HDLC Link has been INACTIVE for an extended period of time [RFC4349]
22 - Session not established due to other LCCE can not support [RFC4454]
the OAM Cell Emulation
23 - Mismatching interface MTU [RFC4667]
24 - Attempt to connect to non-existent forwarder [RFC4667]
25 - Attempt to connect to unauthorized forwarder [RFC4667]
26 - Loop Detected [draft-ietf-l2tpext-tunnel-switching-06.txt]
Defined Result Code values for the MSEN message are:
0 - Reserved
1 - No multicast traffic for the group [RFC4045]
2 - Session terminated for the reason indicated in the error code [RFC4045]
3 - No more receivers [RFC4045]
4 - No more receivers (filter-mode change) [RFC4045]
General Error Codes
0 - No general error
1 - No control connection exists yet for this LAC-LNS pair
2 - Length is wrong
3 - One of the field values was out of range or
reserved field was non-zero
4 - Insufficient resources to handle this operation now
5 - The Session ID is invalid in this context
6 - A generic vendor-specific error occurred in the LAC
7 - Try another. If LAC is aware of other possible LNS
destinations, it should try one of them. This can be
used to guide an LAC based on LNS policy, for instance,
the existence of multilink PPP bundles.
8 - Session or tunnel was shutdown due to receipt of an
unknown AVP with the M-bit set (see section 4.2). The Error
Message SHOULD contain the attribute of the offending AVP in
(human readable) text form.
9 - Try another directed. If an LAC or LNS is aware of other
possible destinations, it should inform the initiator of the
control connection or session. The Error Message MUST contain
a comma-separated list of addresses from which the initiator
may choose. If the L2TP data channel runs over IPv4, then
this would be a comma-separated list of IP addresses in the
canonical dotted-decimal format (e.g., "192.0.2.1, 192.0.2.2,
192.0.2.3") in the UTF-8 charset [RFC3629] using the Default
Language [RFC2277]. If there are no servers for the LAC or
LNS to suggest, then Error Code 7 should be used. For IPv4,
the delimiter between addresses MUST be precisely a single
comma and a single space. For IPv6, each literal address MUST
be enclosed in "[" and "]" characters, following the encoding
described in [RFC2732].
10 - Next hop unreachable. This identifies an error condition [draft-ietf-l2tpext-tunnel-switching-06.txt]
explicitly in the multi-TSA environment.
11 - Next hop busy. This identifies an error condition [draft-ietf-l2tpext-tunnel-switching-06.txt]
explicitly in the multi-TSA environment.
12 - TSA busy. This identifies an error condition [draft-ietf-l2tpext-tunnel-switching-06.txt]
explicitly in the multi-TSA environment.
Proxy Authen Type AVP (Attribute Type 29) Values
------------------------------------------------
0 - Reserved
1 - Textual username/password exchange
2 - PPP CHAP
3 - PPP PAP
4 - No Authentication
5 - Microsoft CHAP Version 1 (MSCHAPv1)
6 - Reserved
7 - EAP [draft-ietf-l2tpext-proxy-authen-ext-eap-00.txt]
Service Category AVP (Attribute Type 42) Flag Field
----------------------------------------------------
The Attribute Value field is a 16-bit field, with current
defined bits:
Value Description Reference
------ ------------------------------------ ---------
0x0001 S-bit (real-time) [RFC3301]
PPP Disconnect Cause Code (Attribute Type 46) Values
----------------------------------------------------
Global Errors
0 No information available
1 Administrative disconnect.
2 Link Control Protocol (LCP) renegotiation at
LNS disabled; LNS expects proxy LCP information,
LAC did not send it.
3 Normal Disconnection, LCP Terminate-Request sent.
Valid Direction values are:
1: LCP Terminate-Request sent by peer
2: LCP Terminate-Request sent by local
4 Compulsory encryption required by a PPP peer was
refused by the other.
Valid Direction values are:
1: Required by local; refused by peer
2: Required by peer; refused by local
LCP Errors
5 FSM (Finite State Machine) Timeout error.
(PPP event "TO-".)
6 No recognizable LCP packets were received.
7 LCP failure: Magic Number error; link possibly
looped back.
8 LCP link failure: Echo Request timeout.
9 Peer has unexpected Endpoint-Discriminator for
existing Multilink PPP (MP) bundle.
10 Peer has unexpected MRRU for existing MP bundle.
11 Peer has unexpected Short-Sequence-Number option
for existing MP bundle.
12 Compulsory call-back required by a PPP peer was
refused by the other.
Valid Direction values are:
1: Required by local; refused by peer
2: Required by peer; refused by local
Authentication Errors
13 FSM Timeout error.
14 Peer has unexpected authenticated name for
existing MP bundle.
15 PPP authentication failure: Authentication protocol
unacceptable.
Valid Direction values are:
1: All local authentication protocols were
rejected by the peer.
2: All authentication protocols requested by peer
were unacceptable or unimplemented locally.
16 PPP authentication failure: Authentication failed
(bad name, password, or secret).
Valid Direction values are:
1: Authentication of peer identity by local system.
2: Authentication of local identity by peer system.
Network Control Protocol (NCP) Errors
17 FSM Timeout error.
18 No NCPs available (all disabled or rejected); no NCPs
went to Opened state. (Control Protocol Number may be
zero only if neither peer has enabled NCPs.)
19 NCP failure: failed to converge on acceptable addresses.
Valid Direction values are:
1: Too many Configure-Naks received from peer.
2: Too many Configure-Naks sent to peer.
20 NCP failure: user not permitted to use any addresses.
Valid Direction values are:
1: Local link address not acceptable to peer.
2: Remote link address not acceptable to local system.
21-32767 Unassigned (by IESG Approval)
32768-65279 Unassigned (by the IANA)
65280-65535 Private or Experimental Use
ATM Alarm Status AVP (Attribute Type 88) Values - per [RFC4454]
-----------------------------------------------
Registration Procedures: Expert Review
Circuit Status Reason values for the SLI message are as follows:
Value Description Reference
----- -------------------------------------------------------- ---------
0 - Reserved [RFC4454]
1 - No alarm or alarm cleared (default for Active Status) [RFC4454]
2 - Unspecified or unknown Alarm Received (default for [RFC4454]
Inactive Status)
3 - ATM Circuit received F1 Alarm on ingress LCCE [RFC4454]
4 - ATM Circuit received F2 Alarm on ingress LCCE [RFC4454]
5 - ATM Circuit received F3 Alarm on ingress LCCE [RFC4454]
6 - ATM Circuit received F4 Alarm on ingress LCCE [RFC4454]
7 - ATM Circuit received F5 Alarm on ingress LCCE [RFC4454]
8 - ATM Circuit down due to ATM Port shutdown on Peer LCCE [RFC4454]
9 - ATM Circuit down due to loop-back timeout on ingress LCCE [RFC4454]
The general ATM Alarm failures are encoded as below:
Value Description Reference
----- -------------------------------------------------------- ---------
0 - Reserved [RFC4454]
1 - No Alarm type specified (default) [RFC4454]
2 - Alarm Indication Signal (AIS) [RFC4454]
3 - Remote Defect Indicator (RDI) [RFC4454]
4 - Loss of Signal (LOS) [RFC4454]
5 - Loss of pointer (LOP) [RFC4454]
6 - Loss of framer (LOF) [RFC4454]
7 - loopback cells (LB) [RFC4454]
8 - Continuity Check (CC) [RFC4454]
VCCV Capability AVP (Attribute Type 96) Values
Reference: [RFC5085]
Registration Procedures: IETF Consensus
Note: Bit numbering: In this sub-registry, the most significant (high order) bit
is labeled Bit 7, and the least significant (low order) bit is labeled Bit 0,
see parenthetical "Value".
L2TPv3 Control Channel (CC) Types
Bit (Value) Description Reference
----------- -------------------------------------- ----------
0 (0x01) L2-Specific Sublayer with V-bit set [RFC5085]
1 (0x02) Reserved [RFC5085]
2 (0x04) Reserved [RFC5085]
3 (0x08) Reserved [RFC5085]
4 (0x10) Reserved [RFC5085]
5 (0x20) Reserved [RFC5085]
6 (0x40) Reserved [RFC5085]
7 (0x80) Reserved [RFC5085]
L2TPv3 Connectivity Verification (CV) Types
Bit (Value) Description Reference
----------- -------------------------------------- ----------
0 (0x01) ICMP Ping [RFC5085]
1 (0x02) Reserved [RFC5085]
2 (0x04) Reserved [RFC5085]
3 (0x08) Reserved [RFC5085]
4 (0x10) Reserved [RFC5085]
5 (0x20) Reserved [RFC5085]
6 (0x40) Reserved [RFC5085]
7 (0x80) Reserved [RFC5085]
Bearer Field definition:
-----------------------
The Bearer field is used by the Bearer Capabilities and Bearer Type
AVPs. It is a 32-bit bit field, with current defined bit values of:
Value Meaning Reference
0x00000001 D-bit (Digital access requested) [RFC2661]
0x00000002 A-bit (Analogue access requested) [RFC2661]
0x00000004 B-bit (ATM Bearer support) [RFCXXXX]
Framing Field definition:
------------------------
The Framing field is used by the Framing Capabilities and Framing Type
AVPs. It is a 32-bit bit field, with current defined bit values of:
Value Meaning Reference
0x00000001 S-bit (synchronous framing) [RFC2661]
0x00000002 A-bit (asyncronous framing) [RFC2661]
Leading Bits of the L2TP AVP Header - per [RFC2661, RFC3931]
-----------------------------------
There are six bits at the beginning of the L2TP AVP header.
L2TPv2 and L2TPv3 share a common registry for the definitions
of the six leading bits. New bits are assigned via Standards
Action [RFC2434].
Bit 0 - Mandatory Bit, "M-bit" [RFC2661, RFC3931]
Bit 1 - Hidden Bit, "H-bit" [RFC2661, RFC3931]
Bit 2 - Reserved [RFC2661, RFC3931]
Bit 3 - Reserved [RFC2661, RFC3931]
Bit 4 - Reserved [RFC2661, RFC3931]
Bit 5 - Reserved [RFC2661, RFC3931]
Leading Bits of the L2TP Message Header - per [RFC2661, RFC3931]
---------------------------------------
There are 12 bits at the beginning of the L2TP Message Header.
L2TPv2 and L2TPv3 share a common registry for the definitions
of the 12 leading bits. Reserved bits should only be defined
by Standard Action [RFC2434].
Bit 0 - Message Type, "T-bit" [RFC2661, RFC3931]
Bit 1 - Length Field is Present, "L-bit" [RFC2661, RFC3931]
Bit 2 - Reserved [RFC2661, RFC3931]
Bit 3 - Reserved [RFC2661, RFC3931]
Bit 4 - Sequence Numbers Present, "S-bit" [RFC2661, RFC3931]
Bit 5 - Reserved [RFC2661, RFC3931]
Bit 6 - Offset Field is Present [RFC2661]
Bit 7 - Priority Bit, "P-bit" [RFC2661]
Bit 8 - B (Fragmentation) bit [RFC4623]
Bit 9 - E (Fragmentation) bit [RFC4623]
Bit 10 - Reserved [RFC2661, RFC3931]
Bit 11 - Reserved [RFC2661, RFC3931]
L2TPv3 Pseudowire Types - per [RFC3931]
-----------------------
The Pseudowire Type (PW Type, Section 5.4) is a two-octet value used
in the Pseudowire Type AVP and Pseudowire Capabilities List AVP
defined in Section 5.4.3. 0 to 32767 are assignable by Expert Review
[RFC2434], 32768 to 65535 by a First Come First Served policy
[RFC2434]. There are no specific pseudowire types assigned within
this document. Each pseudowire-specific document must allocate its
own PW types from IANA as necessary.
0x0001 - Frame Relay DLCI Pseudowire Type [RFC4591]
0x0002 - ATM AAL5 SDU VCC transport [RFC4454]
0x0003 - ATM Cell transparent Port Mode [RFC4454]
0x0004 - Ethernet VLAN Pseudowire Type [RFC4719]
0x0005 - Ethernet Pseudowire Type [RFC4719]
0x0006 - HDLC Pseudowire Type [RFC4349]
0x0009 - ATM Cell transport VCC Mode [RFC4454]
0x000A - ATM Cell transport VPC Mode [RFC4454]
0x000B - Unassigned
0x000C - MPEG-TS Payload Type (MPTPW) [DOCSIS CM-SP-DEPI] 30 January 2006
0x000D - Packet Streaming Protocol (PSPPW) [DOCSIS CM-SP-DEPI] 30 January 2006
Circuit Status Bits - per [RFC3931]
-------------------
The Circuit Status field is a 16 bit mask, with the two high order
bits assigned. Additional bits may be assigned by IETF Consensus
[RFC2434].
Bit 14 - N (New) bit [RFC3931]
Bit 15 - A (Active) bit [RFC3931]
Default L2-Specific Sublayer bits - per [RFC3931]
---------------------------------
The Default L2 Specific Sublayer contains 8 bits in the low-order
portion of the header. Reserved bits may be assigned by IETF
Consensus [RFC2434].
Bit 0 - V (VCCV) bit [RFC5085]
Bit 1 - S (Sequence) bit [RFC3931]
Bit 2 - B (Fragmentation) bit [RFC4623]
Bit 3 - E (Fragmentation) bit [RFC4623]
Bit 4 - Reserved [RFC3931]
Bit 5 - Reserved [RFC3931]
Bit 6 - Reserved [RFC3931]
Bit 7 - Reserved [RFC3931]
L2-Specific Sublayer Type - per [RFC3931]
-------------------------
The L2-Specific Sublayer Type is a 2 octet unsigned integer.
Additional values may be assigned by Expert Review [RFC2434].
0 - No L2-Specific Sublayer [RFC3931]
1 - Default L2-Specific Sublayer present [RFC3931]
2 - ATM-Specific Sublayer present [RFC4454]
3 - MPT-Specific Sublayer [DOCSIS CM-SP-DEPI] 30 January 2006
4 - PSP-Specific Sublayer [DOCSIS CM-SP-DEPI] 30 January 2006
Registry Name: Data Sequencing Level
Reference: [RFC3931]
Registration Procedures: Expert Review
Note:
The Data Sequencing Level is a 2 octet unsigned integer
Additional values may be assigned by Expert Review [RFC2434].
0 - No incoming data packets require sequencing. [RFC3931]
1 - Only non-IP data packets require sequencing. [RFC3931]
2 - All incoming data packets require sequencing. [RFC3931]
Registry Name: ATM-Specific Sublayer bits
Reference: [RFC4454]
Registration Procedures: IETF Consensus
Bit Description Reference
------- --------------------------- ---------
Bit 0 - V (VCCV) bit [RFC5085]
Bit 1 - S (Sequence) bit [RFC4454]
Bit 2 - B (Fragmentation) bit [RFC4454]
Bit 3 - E (Fragmentation) bit [RFC4454]
Bit 4 - T (Transport type) bit [RFC4454]
Bit 5 - G (EFCI) bit [RFC4454]
Bit 6 - C (CLP) bit [RFC4454]
Bit 7 - U (Command/Response) bit [RFC4454]
References
----------
[RFC2661] Townsley, W., et al., "Layer Two Tunneling Protocol "L2TP"",
RFC 2661, August 1999.
[RFC3145] R. Verma, M. Verma, and J. Carlson, "L2TP Disconnect
Cause Information", RFC 3145, July 2001.
[RFC3301] Y. T'Joens, P. Crivellari, and B. Sales, "Layer Two
Tunnelling Protocol : ATM access network extensions",
RFC 3301, June 2002.
[RFC3308] P. Calhoun, W. Luo, D. McPherson, and K. Peirce, "L2TP
Differentiated Services Extension", RFC 3308, November 2002.
[RFC3437] W. Palter and W. M. Townsley, "Layer-Two Tunneling Protocol
(L2TP) Extensions for PPP Link Control Protocol (LCP)
Negotiation, RFC 3437, November 2002.
[RFC3438] W. M. Townsley, "Layer Two Tunneling Protocol (L2TP) Internet
[BCP68] Assigned Numbers Authority (IANA) Considerations Update",
RFC 3438, BCP 68, November 2002.
[RFC3573] I. Goyret, "Signalling of Modem-On-Hold status in Layer 2
Tunneling Protocol (L2TP)", RFC 3573, July 2003.
[RFC3817] W. M. Townsley and R. da Silva, "Layer 2 Tunneling Protocol
(L2TP) Active Discovery Relay for PPP over Ethernet (PPPoE)",
RFC 3817, June 2004.
[RFC3931] J. Lau, M. Townsley, and I. Goyret, Eds., "Layer Two Tunneling
Protocol - Version 3 (L2TPv3)", RFC 3931, March 2005.
[RFC4045] G. Bourdon, "Extensions to support efficient carrying of multicast
traffic in Layer-2 Tunneling Protocol (L2TP)", RFC 4045, April 2005.
[RFC4349] C. Pignataro and W. M. Townsley, "HDLC Frames over L2TPv3",
RFC 4349, February 2006.
[RFC4454] S. Singh, W. M. Townsley and C. Pignataro, "ATM over L2TPv3",
RFC 4454, May 2006.
[RFC4591] W. M. Townsley, G. Wilkie, S. Booth, S. Bryant, and J. Lau,
"Frame-Relay over L2TPv3", RFC 4591, July 2006.
[draft-ietf-l2tpext-tunnel-switching-06.txt]
Work in progress. Added via Expert Review.
[draft-ietf-l2tpext-proxy-authen-ext-eap-00.txt]
Work in progress. Added via Expert Review.
[DOCSIS CM-SP-DEPI]
"Data-Over-Cable Service Interface Specifications: Downstream External PHY Interface
Specification CM-SP-DEPI-I01-050805", DOCSIS, August 2005, available at:
http://www.cablemodem.com/specifications/
http://www.cablelabs.com/specifications/archives/
[RFC4667] W. Luo, "L2VPN Extensions for L2TP", RFC 4667, September 2006.
[RFC4623] Andrew G. Malis, W. Mark Townsley, "PWE3 Fragmentation and Reassembly",
RFC 4623, August 2006.
[RFC4719] Aggarwal, R., Townsley, M., and M. Dos Santos, "Transport of
Ethernet Frames over Layer 2 Tunneling Protocol Version3
(L2TPv3)", RFC 4719, November 2006.
[RFC4720] A. Malis, D. Allan and N. Del Regno, "PWE3 Frame Check Sequence Retention",
RFC 4720, November 2006.
[RFC4951] V. Jain, "Fail Over extensions for L2TP "failover"", RFC 4951,
August 2007.
[RFC5085] T. Nadeau, Ed. and C. Pignataro, Ed., "Pseudowire Virtual Circuit
Connectivity Verification (VCCV) A Control Channel for Pseudowires",
RFC 5085, December 2007.
(created 2003-03)
[]
|
