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
|
Layer Two Tunneling Protocol "L2TP" - RFC 2661
(last updated 2001 July 18)
Control Message Attribute Value Pairs
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 Firmward 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 [RFCATMEXT]
41 Rx Maximum BPS [RFCATMEXT]
42 Service Category [RFCATMEXT]
Also, see Service Category AVP Flag Fields
below
43 Service Name [RFCATMEXT]
44 Calling Sub-Address [RFCATMEXT]
45 VPI/VCI Identifier [RFCATMEXT]
46 PPP Disconnect Cause Code [RFC3145]
Also, see PPP Disconnect Cause Code Values
below
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
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
Error Reporting
15 (WEN) WAN-Error-Notify
PPP Session Control
16 (SLI) Set-Link-Info
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
Defined Result Code values for the CDN message are:
0 - Reserved
1 - Call disconnected due to loss of carrier
2 - Call disconnected for the reason indicated
in error code
3 - Call disconnected for administrative reasons
4 - Call failed due to lack of appropriate facilities
being available (temporary condition)
5 - Call 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
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.
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)
Service Category AVP (Attribute Type 42) Flags Field
----------------------------------------------------
The Attribute Value field is a 16-bit field, with current
defined bits:
Value Description Reference
------ ------------------------------------ ---------
0x0001 S-bit (real-time) [RFCATMEXT]
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
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]
References
----------
[RFC2661] Townsley, W., et al., "Layer Two Tunneling Protocol "L2TP"",
RFC 2661, August 1999.
[RFCATMEXT] Y. T'Joens, P. Crivellari, and B. Sales, "Layer Two
Tunnelling Protocol : ATM access network extensions",
RFC XXXX, Month 2001.
[RFC3145] R. Verma, M. Verma, and J. Carlson, "L2TP Disconnect
Cause Information", RFC 3145, July 2001.
(created 03/00)
[]
|
