1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
|
<pre>Network Working Group K. Leung
Request for Comments: 4332 A. Patel
Category: Informational Cisco Systems
G. Tsirtsis
Flarion Technologies
E. Klovning
Birdstep Technology ASA
December 2005
<span class="h1">Cisco's Mobile IPv4 Host Configuration Extensions</span>
Status of This Memo
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2005).
IESG Note
This RFC is not a candidate for any level of Internet Standard. The
IETF disclaims any knowledge of the fitness of this RFC for any
purpose and in particular notes that the decision to publish is not
based on IETF review for such things as security, congestion control,
or inappropriate interaction with deployed protocols. The RFC Editor
has chosen to publish this document at its discretion. Readers of
this document should exercise caution in evaluating its value for
implementation and deployment. See <a href="./rfc3932">RFC 3932</a> for more information.
This RFC does not offer any security mechanisms to provide data
origin authentication and integrity, yet these security services are
vitally important in this context.
Abstract
An IP device requires basic host configuration to be able to
communicate. For example, it will typically require an IP address
and the address of a DNS server. This information is configured
statically or obtained dynamically using Dynamic Host Configuration
Protocol (DHCP) or Point-to-Point Protocol/IP Control Protocol
(PPP/IPCP). However, both DHCP and PPP/IPCP provide host
configuration based on the access network. In Mobile IPv4, the
registration process boots up a Mobile Node at an access network,
also known as a foreign network. The information to configure the
<span class="grey">Leung, et al. Informational [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc4332">RFC 4332</a> Host Config December 2005</span>
host needs to be based on the home network. This document describes
the Cisco vendor-specific extensions to Mobile IPv4 to provide the
base host configuration in Registration Request and Reply messages.
Table of Contents
<a href="#section-1">1</a>. Introduction ....................................................<a href="#page-2">2</a>
<a href="#section-2">2</a>. Host Configuration Extensions Summary ...........................<a href="#page-3">3</a>
<a href="#section-3">3</a>. Host Configuration Extensions ...................................<a href="#page-4">4</a>
<a href="#section-3.1">3.1</a>. Host Configuration Request Extension .......................<a href="#page-5">5</a>
<a href="#section-3.2">3.2</a>. Home Network Length Prefix Extension .......................<a href="#page-5">5</a>
<a href="#section-3.3">3.3</a>. DNS Server Extension .......................................<a href="#page-6">6</a>
<a href="#section-3.4">3.4</a>. DHCP Server Extension ......................................<a href="#page-6">6</a>
<a href="#section-3.5">3.5</a>. DHCP Client ID Extension ...................................<a href="#page-7">7</a>
<a href="#section-3.6">3.6</a>. Default Gateway Extension ..................................<a href="#page-7">7</a>
<a href="#section-3.7">3.7</a>. DNS Suffix Extension .......................................<a href="#page-8">8</a>
<a href="#section-3.8">3.8</a>. Configuration URL Extension ................................<a href="#page-8">8</a>
<a href="#section-4">4</a>. Security Considerations .........................................<a href="#page-9">9</a>
<a href="#section-5">5</a>. Acknowledgements ................................................<a href="#page-9">9</a>
<a href="#section-6">6</a>. Informative References ..........................................<a href="#page-9">9</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
An IPv4 device requires some basic configuration to communicate with
other nodes. Typically, it has an IP address for an interface and
DNS server's IP address to resolve the peer's hostname to an IP
address. DHCP [<a href="./rfc2131" title=""Dynamic Host Configuration Protocol"">RFC2131</a>] and PPP/IPCP [<a href="./rfc1332" title=""The PPP Internet Protocol Control Protocol (IPCP)"">RFC1332</a>] provide host
configuration information on the access network interface, but this
is inadequate in a Mobile IPv4 environment. In Mobile IPv4
[<a href="./rfc3344" title=""IP Mobility Support for IPv4"">RFC3344</a>], a Mobile Node has a virtual network interface on the home
network, anchored by the Home Agent. The IP address, home subnet
prefix, default gateway, and home network's DNS servers are essential
in the boot up of a network interface. In some cases, these are the
only pieces of information needed by the Mobile Node.
The Mobile IPv4 registration process provides the mechanism for a
Mobile Node to boot up on a foreign network. Upon the successful
registration, the Mobile Node can communicate with the Correspondent
Node. The need to provide an efficient method to obtain the host
configuration exists. If the Mobile Node is a DHCP client, it can
obtain configuration parameters from the DHCP server in the home
network after the initial registration.
This document introduces the Cisco vendor-specific extensions (VSEs)
[<a href="./rfc3115" title=""Mobile IP Vendor/ Organization-Specific Extensions"">RFC3115</a>] to provide the means for a Mobile Node to download some
fundamental configuration associated with the home network via the
<span class="grey">Leung, et al. Informational [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc4332">RFC 4332</a> Host Config December 2005</span>
Home Agent. These extensions provide information for home subnet
prefix, DNS server, DHCP server, DHCP client identifier, default
gateway, DNS suffix, and configuration URL.
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Host Configuration Extensions Summary</span>
The following Cisco vendor-specific extensions provide the host
configuration for a Mobile Node. The "Host Configuration Request"
extension is allowed only in the Registration Request. The rest of
the extensions are appended in the Registration Reply.
o Host Configuration Request
* Request for host configuration information from the Mobile Node
to the Home Agent.
o Home Network Prefix Length
* The length of the subnet prefix on the home network.
o Default Gateway
* The default gateway's IP address on the home network.
o DNS Server
* The DNS server's IP address in the home network.
o DNS Suffix
* The DNS suffix for hostname resolution in the home network.
o DHCP Client ID
* The DHCP Client ID used to obtain the IP address. When the
Mobile Node returns home and is responsible for managing its
own address, this information maps to the client identifier
option as defined in <a href="./rfc2132#section-9.14">section 9.14 of [RFC2132]</a> and referenced
in [<a href="./rfc2131" title=""Dynamic Host Configuration Protocol"">RFC2131</a>].
o DHCP Server
* The DHCP server's IP address in the home network.
o Configuration URL
* The URL for the Mobile Node to download configuration
parameters from a server.
<span class="grey">Leung, et al. Informational [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc4332">RFC 4332</a> Host Config December 2005</span>
When the Mobile Node needs to obtain its host configuration, the Host
Configuration Request VSE is appended to the Registration Request.
This VSE indicates to the Home Agent that either all or selected host
configuration VSEs need to be appended to the Registration Reply. If
the Home Agent retrieved the information from a DHCP server (in Proxy
DHCP mode), then the DHCP Client ID and DHCP Server extensions are
appended in the Registration Reply. These DHCP-related extensions
are populated with values that had been used in the DHCP messages
exchanged between the Home Agent and the DHCP server.
The VSEs are authenticated as part of the registration message using
any of the authentication mechanism defined for Mobile IP ([<a href="./rfc3344" title=""IP Mobility Support for IPv4"">RFC3344</a>],
[<a href="./rfc3012" title=""Mobile IPv4 Challenge/ Response Extensions"">RFC3012</a>]).
This message MAY contain extensions defined in Mobile IP, including
vendor-specific extensions [<a href="./rfc3115" title=""Mobile IP Vendor/ Organization-Specific Extensions"">RFC3115</a>].
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Host Configuration Extensions</span>
Cisco's host configuration extensions to Mobile IPv4 are based on the
vendor-specific extensions defined in [<a href="./rfc3115" title=""Mobile IP Vendor/ Organization-Specific Extensions"">RFC3115</a>]. The format of the
VSE TLV (Type-Length-Value) is as follows:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Vendor/Org-ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Vendor-NVSE-Type | Vendor-NVSE-Value ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: 134
Length:
Indicates the length (in bytes) of the data field within this
extension, excluding the Type and Length fields.
Reserved:
Reserved for future use. To be set to 0 while sending, ignored
on reception.
Vendor/Org-ID:
9 (Cisco Systems)
<span class="grey">Leung, et al. Informational [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc4332">RFC 4332</a> Host Config December 2005</span>
Vendor-NVSE-Type:
14 (Host Configuration)
Vendor-NVSE-Value:
Format is shown below for each subtype. The Sub-Type field is
an integer from 0 to 255.
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Host Configuration Request Extension</span>
This format of the Host Configuration Request extension is shown
below.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sub-Type | Selector |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Sub-Type:
0
Selector:
0 indicates all host configuration available to the Home
Agent (HA) is requested by the Mobile Node.
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Home Network Length Prefix Extension</span>
This format of the Home Network Prefix Length extension is shown
below.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sub-Type | Prefix Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Sub-Type:
1
Prefix Length:
The number of bits in the home subnet prefix.
<span class="grey">Leung, et al. Informational [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc4332">RFC 4332</a> Host Config December 2005</span>
<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. DNS Server Extension</span>
This format of the DNS Server extension is shown below.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sub-Type | Primary DNS Server
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. . . | Secondary DNS Server
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. . . |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Sub-Type:
2
Primary DNS Server:
The IP address of the primary DNS server.
Secondary DNS Server:
The IP address of the secondary DNS server.
<span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a>. DHCP Server Extension</span>
This format of the DHCP Server extension is shown below.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sub-Type | DHCP Server
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. . . |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Sub-Type:
3
DHCP Server:
The IP address of the DHCP server.
<span class="grey">Leung, et al. Informational [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc4332">RFC 4332</a> Host Config December 2005</span>
<span class="h3"><a class="selflink" id="section-3.5" href="#section-3.5">3.5</a>. DHCP Client ID Extension</span>
This format of the DHCP Client ID extension is shown below.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sub-Type | Client ID . . .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Sub-Type:
4
Client ID:
DHCP servers use this value to index their database of address
bindings. This value is expected to be unique for all clients
in an administrative domain. The size of field is between 2
and 255 octets.
<span class="h3"><a class="selflink" id="section-3.6" href="#section-3.6">3.6</a>. Default Gateway Extension</span>
This format of the Default Gateway extension is shown below.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sub-Type | Default Gateway
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. . . |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Sub-Type:
5
Default Gateway:
The IP address of the default gateway for the Mobile Node on
the home network.
<span class="grey">Leung, et al. Informational [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc4332">RFC 4332</a> Host Config December 2005</span>
<span class="h3"><a class="selflink" id="section-3.7" href="#section-3.7">3.7</a>. DNS Suffix Extension</span>
This format of the DNS Suffix extension is shown below.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sub-Type | DNS Suffix . . .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Sub-Type:
6
DNS Suffix:
The DNS suffix to be appended to the name of Mobile Node when
completing its fully qualified domain name (FQDN). The size of
field is between 1 and 246 octets.
<span class="h3"><a class="selflink" id="section-3.8" href="#section-3.8">3.8</a>. Configuration URL Extension</span>
This format of the Configuration URL extension is shown below.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sub-Type | URL String . . .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Sub-Type:
7
URL String:
The Mobile Node can retrieve configuration parameters via the
URL. The URL is at most 246 bytes in length.
<span class="grey">Leung, et al. Informational [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc4332">RFC 4332</a> Host Config December 2005</span>
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Security Considerations</span>
The host configuration extensions follow the same rules for Mobile IP
extensions in registration messages. See the Security Considerations
section in <a href="./rfc3344">RFC 3344</a>.
The Configuration URL extension may trigger the Mobile Node to
download the configuration parameters from a server. The protection
of the data transfer is outside the scope of this document. Possible
options include encryption of data before transfer or using HTTPS.
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Acknowledgements</span>
The authors would like to acknowledge Jayshree Bharatia, Kuntal
Chowdhury, Avi Lior, and Lila Madour for their contributions to the
work in progress titled "Mobile IPv4 Extension for Configuration
Options Exchange".
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Informative References</span>
[<a id="ref-RFC1332">RFC1332</a>] McGregor, G., "The PPP Internet Protocol Control Protocol
(IPCP)", <a href="./rfc1332">RFC 1332</a>, May 1992.
[<a id="ref-RFC2131">RFC2131</a>] Droms, R., "Dynamic Host Configuration Protocol",
<a href="./rfc2131">RFC 2131</a>, March 1997.
[<a id="ref-RFC2132">RFC2132</a>] Alexander, S. and R. Droms, "DHCP Options and BOOTP Vendor
Extensions", <a href="./rfc2132">RFC 2132</a>, March 1997.
[<a id="ref-RFC3012">RFC3012</a>] Perkins, C. and P. Calhoun, "Mobile IPv4 Challenge/
Response Extensions", <a href="./rfc3012">RFC 3012</a>, November 2000.
[<a id="ref-RFC3115">RFC3115</a>] Dommety, G. and K. Leung, "Mobile IP Vendor/
Organization-Specific Extensions", <a href="./rfc3115">RFC 3115</a>, April 2001.
[<a id="ref-RFC3344">RFC3344</a>] Perkins, C., "IP Mobility Support for IPv4", <a href="./rfc3344">RFC 3344</a>,
August 2002.
<span class="grey">Leung, et al. Informational [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc4332">RFC 4332</a> Host Config December 2005</span>
Authors' Addresses
Kent Leung
Cisco Systems
170 W. Tasman Drive
San Jose, CA 95134
US
Phone: +1 408-526-5030
EMail: kleung@cisco.com
Alpesh Patel
Cisco Systems
170 W. Tasman Drive
San Jose, CA 95134
US
Phone: +1 408-853-9580
EMail: alpesh@cisco.com
George Tsirtsis
Flarion Technologies
Bedminster One
135 Route 202/206 South
Bedminster, NJ 07921
US
Phone: +1 908-947-7059
EMail: g.tsirtsis@flarion.com
Espen Klovning
Birdstep Technology ASA
Bryggegata 7
Oslo, 0250
Norway
Phone: +47 95 20 26 29
EMail: espen@birdstep.com
<span class="grey">Leung, et al. Informational [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc4332">RFC 4332</a> Host Config December 2005</span>
Full Copyright Statement
Copyright (C) The Internet Society (2005).
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 at www.rfc-editor.org/copyright.html, 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 currently provided by the
Internet Society.
Leung, et al. Informational [Page 11]
</pre>
|
