Debian Codegraph @

rfc2374.html

raw
1 <pre>Network Working Group R. Hinden
2 Request for Comments: 2374 Nokia
3 Obsoletes: <a href="./rfc2073">2073</a> M. O'Dell
4 Category: Standards Track UUNET
5 S. Deering
6 Cisco
7 July 1998
8
9
10 <span class="h1">An IPv6 Aggregatable Global Unicast Address Format</span>
11
12 Status of this Memo
13
14 This document specifies an Internet standards track protocol for the
15 Internet community, and requests discussion and suggestions for
16 improvements. Please refer to the current edition of the "Internet
17 Official Protocol Standards" (STD 1) for the standardization state
18 and status of this protocol. Distribution of this memo is unlimited.
19
20 Copyright Notice
21
22 Copyright (C) The Internet Society (1998). All Rights Reserved.
23
24 <span class="h3"><a class="selflink" id="section-1.0" href="#section-1.0">1.0</a> Introduction</span>
25
26 This document defines an IPv6 aggregatable global unicast address
27 format for use in the Internet. The address format defined in this
28 document is consistent with the IPv6 Protocol [<a href="#ref-IPV6" title="&quot;Internet Protocol, Version 6 (IPv6) Specification&quot;">IPV6</a>] and the "IPv6
29 Addressing Architecture" [<a href="#ref-ARCH" title="&quot;IP Version 6 Addressing Architecture&quot;">ARCH</a>]. It is designed to facilitate
30 scalable Internet routing.
31
32 This documented replaces <a href="./rfc2073">RFC 2073</a>, "An IPv6 Provider-Based Unicast
33 Address Format". <a href="./rfc2073">RFC 2073</a> will become historic. The Aggregatable
34 Global Unicast Address Format is an improvement over <a href="./rfc2073">RFC 2073</a> in a
35 number of areas. The major changes include removal of the registry
36 bits because they are not needed for route aggregation, support of
37 EUI-64 based interface identifiers, support of provider and exchange
38 based aggregation, separation of public and site topology, and new
39 aggregation based terminology.
40
41 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
42 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
43 document are to be interpreted as described in [<a href="./rfc2119">RFC 2119</a>].
44
45
46
47
48
49
50
51
52 <span class="grey">Hinden, et. al. Standards Track [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc2374">RFC 2374</a> IPv6 Global Unicast Address Format July 1998</span>
55
56
57 <span class="h3"><a class="selflink" id="section-2.0" href="#section-2.0">2.0</a> Overview of the IPv6 Address</span>
58
59 IPv6 addresses are 128-bit identifiers for interfaces and sets of
60 interfaces. There are three types of addresses: Unicast, Anycast,
61 and Multicast. This document defines a specific type of Unicast
62 address.
63
64 In this document, fields in addresses are given specific names, for
65 example "subnet". When this name is used with the term "ID" (for
66 "identifier") after the name (e.g., "subnet ID"), it refers to the
67 contents of the named field. When it is used with the term "prefix"
68 (e.g. "subnet prefix") it refers to all of the addressing bits to
69 the left of and including this field.
70
71 IPv6 unicast addresses are designed assuming that the Internet
72 routing system makes forwarding decisions based on a "longest prefix
73 match" algorithm on arbitrary bit boundaries and does not have any
74 knowledge of the internal structure of IPv6 addresses. The structure
75 in IPv6 addresses is for assignment and allocation. The only
76 exception to this is the distinction made between unicast and
77 multicast addresses.
78
79 The specific type of an IPv6 address is indicated by the leading bits
80 in the address. The variable-length field comprising these leading
81 bits is called the Format Prefix (FP).
82
83 This document defines an address format for the 001 (binary) Format
84 Prefix for Aggregatable Global Unicast addresses. The same address
85 format could be used for other Format Prefixes, as long as these
86 Format Prefixes also identify IPv6 unicast addresses. Only the "001"
87 Format Prefix is defined here.
88
89 <span class="h3"><a class="selflink" id="section-3.0" href="#section-3.0">3.0</a> IPv6 Aggregatable Global Unicast Address Format</span>
90
91 This document defines an address format for the IPv6 aggregatable
92 global unicast address assignment. The authors believe that this
93 address format will be widely used for IPv6 nodes connected to the
94 Internet. This address format is designed to support both the
95 current provider-based aggregation and a new type of exchange-based
96 aggregation. The combination will allow efficient routing
97 aggregation for sites that connect directly to providers and for
98 sites that connect to exchanges. Sites will have the choice to
99 connect to either type of aggregation entity.
100
101
102
103
104
105
106
107
108 <span class="grey">Hinden, et. al. Standards Track [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc2374">RFC 2374</a> IPv6 Global Unicast Address Format July 1998</span>
111
112
113 While this address format is designed to support exchange-based
114 aggregation (in addition to current provider-based aggregation) it is
115 not dependent on exchanges for it's overall route aggregation
116 properties. It will provide efficient route aggregation with only
117 provider-based aggregation.
118
119 Aggregatable addresses are organized into a three level hierarchy:
120
121 - Public Topology
122 - Site Topology
123 - Interface Identifier
124
125 Public topology is the collection of providers and exchanges who
126 provide public Internet transit services. Site topology is local to
127 a specific site or organization which does not provide public transit
128 service to nodes outside of the site. Interface identifiers identify
129 interfaces on links.
130
131 ______________ ______________
132 --+/ \+--------------+/ \+----------
133 ( P1 ) +----+ ( P3 ) +----+
134 +\______________/ | |----+\______________/+--| |--
135 | +--| X1 | +| X2 |
136 | ______________ / | |-+ ______________ / | |--
137 +/ \+ +-+--+ \ / \+ +----+
138 ( P2 ) / \ +( P4 )
139 --+\______________/ / \ \______________/
140 | / \ | |
141 | / | | |
142 | / | | |
143 _|_ _/_ _|_ _|_ _|_
144 / \ / \ / \ / \ / \
145 ( S.A ) ( S.B ) ( P5 ) ( P6 )( S.C )
146 \___/ \___/ \___/ \___/ \___/
147 | / \
148 _|_ _/_ \ ___
149 / \ / \ +-/ \
150 ( S.D ) ( S.E ) ( S.F )
151 \___/ \___/ \___/
152
153 As shown in the figure above, the aggregatable address format is
154 designed to support long-haul providers (shown as P1, P2, P3, and
155 P4), exchanges (shown as X1 and X2), multiple levels of providers
156 (shown at P5 and P6), and subscribers (shown as S.x) Exchanges
157 (unlike current NAPs, FIXes, etc.) will allocate IPv6 addresses.
158 Organizations who connect to these exchanges will also subscribe
159 (directly, indirectly via the exchange, etc.) for long-haul service
160 from one or more long-haul providers. Doing so, they will achieve
161
162
163
164 <span class="grey">Hinden, et. al. Standards Track [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc2374">RFC 2374</a> IPv6 Global Unicast Address Format July 1998</span>
167
168
169 addressing independence from long-haul transit providers. They will
170 be able to change long-haul providers without having to renumber
171 their organization. They can also be multihomed via the exchange to
172 more than one long-haul provider without having to have address
173 prefixes from each long-haul provider. Note that the mechanisms used
174 for this type of provider selection and portability are not discussed
175 in the document.
176
177 <span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a> Aggregatable Global Unicast Address Structure</span>
178
179 The aggregatable global unicast address format is as follows:
180
181 | 3| 13 | 8 | 24 | 16 | 64 bits |
182 +--+-----+---+--------+--------+--------------------------------+
183 |FP| TLA |RES| NLA | SLA | Interface ID |
184 | | ID | | ID | ID | |
185 +--+-----+---+--------+--------+--------------------------------+
186
187 &lt;--Public Topology---&gt; Site
188 &lt;--------&gt;
189 Topology
190 &lt;------Interface Identifier-----&gt;
191
192 Where
193
194 FP Format Prefix (001)
195 TLA ID Top-Level Aggregation Identifier
196 RES Reserved for future use
197 NLA ID Next-Level Aggregation Identifier
198 SLA ID Site-Level Aggregation Identifier
199 INTERFACE ID Interface Identifier
200
201 The following sections specify each part of the IPv6 Aggregatable
202 Global Unicast address format.
203
204 <span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a> Top-Level Aggregation ID</span>
205
206 Top-Level Aggregation Identifiers (TLA ID) are the top level in the
207 routing hierarchy. Default-free routers must have a routing table
208 entry for every active TLA ID and will probably have additional
209 entries providing routing information for the TLA ID in which they
210 are located. They may have additional entries in order to optimize
211 routing for their specific topology, but the routing topology at all
212 levels must be designed to minimize the number of additional entries
213 fed into the default free routing tables.
214
215
216
217
218
219
220 <span class="grey">Hinden, et. al. Standards Track [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc2374">RFC 2374</a> IPv6 Global Unicast Address Format July 1998</span>
223
224
225 This addressing format supports 8,192 (2^13) TLA ID's. Additional
226 TLA ID's may be added by either growing the TLA field to the right
227 into the reserved field or by using this format for additional format
228 prefixes.
229
230 The issues relating to TLA ID assignment are beyond the scope of this
231 document. They will be described in a document under preparation.
232
233 <span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a> Reserved</span>
234
235 The Reserved field is reserved for future use and must be set to
236 zero.
237
238 The Reserved field allows for future growth of the TLA and NLA fields
239 as appropriate. See <a href="#section-4.0">section 4.0</a> for a discussion.
240
241 <span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a> Next-Level Aggregation Identifier</span>
242
243 Next-Level Aggregation Identifier's are used by organizations
244 assigned a TLA ID to create an addressing hierarchy and to identify
245 sites. The organization can assign the top part of the NLA ID in a
246 manner to create an addressing hierarchy appropriate to its network.
247 It can use the remainder of the bits in the field to identify sites
248 it wishes to serve. This is shown as follows:
249
250 | n | 24-n bits | 16 | 64 bits |
251 +-----+--------------------+--------+-----------------+
252 |NLA1 | Site ID | SLA ID | Interface ID |
253 +-----+--------------------+--------+-----------------+
254
255 Each organization assigned a TLA ID receives 24 bits of NLA ID space.
256 This NLA ID space allows each organization to provide service to
257 approximately as many organizations as the current IPv4 Internet can
258 support total networks.
259
260 Organizations assigned TLA ID's may also support NLA ID's in their
261 own Site ID space. This allows the organization assigned a TLA ID to
262 provide service to organizations providing public transit service and
263 to organizations who do not provide public transit service. These
264 organizations receiving an NLA ID may also choose to use their Site
265 ID space to support other NLA ID's. This is shown as follows:
266
267
268
269
270
271
272
273
274
275
276 <span class="grey">Hinden, et. al. Standards Track [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc2374">RFC 2374</a> IPv6 Global Unicast Address Format July 1998</span>
279
280
281 | n | 24-n bits | 16 | 64 bits |
282 +-----+--------------------+--------+-----------------+
283 |NLA1 | Site ID | SLA ID | Interface ID |
284 +-----+--------------------+--------+-----------------+
285
286 | m | 24-n-m | 16 | 64 bits |
287 +-----+--------------+--------+-----------------+
288 |NLA2 | Site ID | SLA ID | Interface ID |
289 +-----+--------------+--------+-----------------+
290
291 | o |24-n-m-o| 16 | 64 bits |
292 +-----+--------+--------+-----------------+
293 |NLA3 | Site ID| SLA ID | Interface ID |
294 +-----+--------+--------+-----------------+
295
296 The design of the bit layout of the NLA ID space for a specific TLA
297 ID is left to the organization responsible for that TLA ID. Likewise
298 the design of the bit layout of the next level NLA ID is the
299 responsibility of the previous level NLA ID. It is recommended that
300 organizations assigning NLA address space use "slow start" allocation
301 procedures similar to [<a href="./rfc2050" title="&quot;Internet Registry IP Allocation Guidelines&quot;">RFC2050</a>].
302
303 The design of an NLA ID allocation plan is a tradeoff between routing
304 aggregation efficiency and flexibility. Creating hierarchies allows
305 for greater amount of aggregation and results in smaller routing
306 tables. Flat NLA ID assignment provides for easier allocation and
307 attachment flexibility, but results in larger routing tables.
308
309 <span class="h3"><a class="selflink" id="section-3.5" href="#section-3.5">3.5</a> Site-Level Aggregation Identifier</span>
310
311 The SLA ID field is used by an individual organization to create its
312 own local addressing hierarchy and to identify subnets. This is
313 analogous to subnets in IPv4 except that each organization has a much
314 greater number of subnets. The 16 bit SLA ID field support 65,535
315 individual subnets.
316
317 Organizations may choose to either route their SLA ID "flat" (e.g.,
318 not create any logical relationship between the SLA identifiers that
319 results in larger routing tables), or to create a two or more level
320 hierarchy (that results in smaller routing tables) in the SLA ID
321 field. The latter is shown as follows:
322
323
324
325
326
327
328
329
330
331
332 <span class="grey">Hinden, et. al. Standards Track [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc2374">RFC 2374</a> IPv6 Global Unicast Address Format July 1998</span>
335
336
337 | n | 16-n | 64 bits |
338 +-----+------------+-------------------------------------+
339 |SLA1 | Subnet | Interface ID |
340 +-----+------------+-------------------------------------+
341
342 | m |16-n-m | 64 bits |
343 +----+-------+-------------------------------------+
344 |SLA2|Subnet | Interface ID |
345 +----+-------+-------------------------------------+
346
347 The approach chosen for structuring an SLA ID field is the
348 responsibility of the individual organization.
349
350 The number of subnets supported in this address format should be
351 sufficient for all but the largest of organizations. Organizations
352 which need additional subnets can arrange with the organization they
353 are obtaining Internet service from to obtain additional site
354 identifiers and use this to create additional subnets.
355
356 <span class="h3"><a class="selflink" id="section-3.6" href="#section-3.6">3.6</a> Interface ID</span>
357
358 Interface identifiers are used to identify interfaces on a link.
359 They are required to be unique on that link. They may also be unique
360 over a broader scope. In many cases an interfaces identifier will be
361 the same or be based on the interface's link-layer address.
362 Interface IDs used in the aggregatable global unicast address format
363 are required to be 64 bits long and to be constructed in IEEE EUI-64
364 format [EUI-64]. These identifiers may have global scope when a
365 global token (e.g., IEEE 48bit MAC) is available or may have local
366 scope where a global token is not available (e.g., serial links,
367 tunnel end-points, etc.). The "u" bit (universal/local bit in IEEE
368 EUI-64 terminology) in the EUI-64 identifier must be set correctly,
369 as defined in [<a href="#ref-ARCH" title="&quot;IP Version 6 Addressing Architecture&quot;">ARCH</a>], to indicate global or local scope.
370
371 The procedures for creating EUI-64 based Interface Identifiers is
372 defined in [<a href="#ref-ARCH" title="&quot;IP Version 6 Addressing Architecture&quot;">ARCH</a>]. The details on forming interface identifiers is
373 defined in the appropriate "IPv6 over &lt;link&gt;" specification such as
374 "IPv6 over Ethernet" [<a href="#ref-ETHER" title="&quot;Transmission of IPv6 Packets over Ethernet Networks&quot;">ETHER</a>], "IPv6 over FDDI" [<a href="#ref-FDDI" title="&quot;Transmission of IPv6 Packets over FDDI Networks&quot;">FDDI</a>], etc.
375
376 <span class="h3"><a class="selflink" id="section-4.0" href="#section-4.0">4.0</a> Technical Motivation</span>
377
378 The design choices for the size of the fields in the aggregatable
379 address format were based on the need to meet a number of technical
380 requirements. These are described in the following paragraphs.
381
382 The size of the Top-Level Aggregation Identifier is 13 bits. This
383 allows for 8,192 TLA ID's. This size was chosen to insure that the
384 default-free routing table in top level routers in the Internet is
385
386
387
388 <span class="grey">Hinden, et. al. Standards Track [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc2374">RFC 2374</a> IPv6 Global Unicast Address Format July 1998</span>
391
392
393 kept within the limits, with a reasonable margin, of the current
394 routing technology. The margin is important because default-free
395 routers will also carry a significant number of longer (i.e., more-
396 specific) prefixes for optimizing paths internal to a TLA and between
397 TLAs.
398
399 The important issue is not only the size of the default-free routing
400 table, but the complexity of the topology that determines the number
401 of copies of the default-free routes that a router must examine while
402 computing a forwarding table. Current practice with IPv4 it is
403 common to see a prefix announced fifteen times via different paths.
404
405 The complexity of Internet topology is very likely to increase in the
406 future. It is important that IPv6 default-free routing support
407 additional complexity as well as a considerably larger internet.
408
409 It should be noted for comparison that at the time of this writing
410 (spring, 1998) the IPv4 default-free routing table contains
411 approximately 50,000 prefixes. While this shows that it is possible
412 to support more routes than 8,192 it is matter of debate if the
413 number of prefixes supported today in IPv4 is already too high for
414 current routing technology. There are serious issues of route
415 stability as well as cases of providers not supporting all top level
416 prefixes. The technical requirement was to pick a TLA ID size that
417 was below, with a reasonable margin, what was being done with IPv4.
418
419 The choice of 13 bits for the TLA field was an engineering
420 compromise. Fewer bits would have been too small by not supporting
421 enough top level organizations. More bits would have exceeded what
422 can be reasonably accommodated, with a reasonable margin, with
423 current routing technology in order to deal with the issues described
424 in the previous paragraphs.
425
426 If in the future, routing technology improves to support a larger
427 number of top level routes in the default-free routing tables there
428 are two choices on how to increase the number TLA identifiers. The
429 first is to expand the TLA ID field into the reserved field. This
430 would increase the number of TLA ID's to approximately 2 million.
431 The second approach is to allocate another format prefix (FP) for use
432 with this address format. Either or a combination of these
433 approaches allows the number of TLA ID's to increase significantly.
434
435 The size of the Reserved field is 8 bits. This size was chosen to
436 allow significant growth of either the TLA ID and/or the NLA ID
437 fields.
438
439 The size of the Next-Level Aggregation Identifier field is 24 bits.
440
441
442
443
444 <span class="grey">Hinden, et. al. Standards Track [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc2374">RFC 2374</a> IPv6 Global Unicast Address Format July 1998</span>
447
448
449 This allows for approximately sixteen million NLA ID's if used in a
450 flat manner. Used hierarchically it allows for a complexity roughly
451 equivalent to the IPv4 address space (assuming an average network
452 size of 254 interfaces). If in the future additional room for
453 complexity is needed in the NLA ID, this may be accommodated by
454 extending the NLA ID into the Reserved field.
455
456 The size of the Site-Level Aggregation Identifier field is 16 bits.
457 This supports 65,535 individual subnets per site. The design goal
458 for the size of this field was to be sufficient for all but the
459 largest of organizations. Organizations which need additional
460 subnets can arrange with the organization they are obtaining Internet
461 service from to obtain additional site identifiers and use this to
462 create additional subnets.
463
464 The Site-Level Aggregation Identifier field was given a fixed size in
465 order to force the length of all prefixes identifying a particular
466 site to be the same length (i.e., 48 bits). This facilitates
467 movement of sites in the topology (e.g., changing service providers
468 and multi-homing to multiple service providers).
469
470 The Interface ID Interface Identifier field is 64 bits. This size
471 was chosen to meet the requirement specified in [<a href="#ref-ARCH" title="&quot;IP Version 6 Addressing Architecture&quot;">ARCH</a>] to support
472 EUI-64 based Interface Identifiers.
473
474 <span class="h3"><a class="selflink" id="section-5.0" href="#section-5.0">5.0</a> Acknowledgments</span>
475
476 The authors would like to express our thanks to Thomas Narten, Bob
477 Fink, Matt Crawford, Allison Mankin, Jim Bound, Christian Huitema,
478 Scott Bradner, Brian Carpenter, John Stewart, and Daniel Karrenberg
479 for their review and constructive comments.
480
481 <span class="h3"><a class="selflink" id="section-6.0" href="#section-6.0">6.0</a> References</span>
482
483 [<a id="ref-ALLOC">ALLOC</a>] IAB and IESG, "IPv6 Address Allocation Management",
484 <a href="./rfc1881">RFC 1881</a>, December 1995.
485
486 [<a id="ref-ARCH">ARCH</a>] Hinden, R., "IP Version 6 Addressing Architecture",
487 <a href="./rfc2373">RFC 2373</a>, July 1998.
488
489 [<a id="ref-AUTH">AUTH</a>] Atkinson, R., "IP Authentication Header", <a href="./rfc1826">RFC 1826</a>, August
490 1995.
491
492 [<a id="ref-AUTO">AUTO</a>] Thompson, S., and T. Narten., "IPv6 Stateless Address
493 Autoconfiguration", <a href="./rfc1971">RFC 1971</a>, August 1996.
494
495 [<a id="ref-ETHER">ETHER</a>] Crawford, M., "Transmission of IPv6 Packets over Ethernet
496 Networks", Work in Progress.
497
498
499
500 <span class="grey">Hinden, et. al. Standards Track [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc2374">RFC 2374</a> IPv6 Global Unicast Address Format July 1998</span>
503
504
505 [<a id="ref-EUI64">EUI64</a>] IEEE, "Guidelines for 64-bit Global Identifier (EUI-64)
506 Registration Authority",
507 <a href="http://standards.ieee.org/db/oui/tutorials/EUI64.html">http://standards.ieee.org/db/oui/tutorials/EUI64.html</a>,
508 March 1997.
509
510 [<a id="ref-FDDI">FDDI</a>] Crawford, M., "Transmission of IPv6 Packets over FDDI
511 Networks", Work in Progress.
512
513 [<a id="ref-IPV6">IPV6</a>] Deering, S., and R. Hinden, "Internet Protocol, Version 6
514 (IPv6) Specification", <a href="./rfc1883">RFC 1883</a>, December 1995.
515
516 [<a id="ref-RFC2050">RFC2050</a>] Hubbard, K., Kosters, M., Conrad, D., Karrenberg, D.,
517 and J. Postel, "Internet Registry IP Allocation
518 Guidelines", <a href="https://www.rfc-editor.org/bcp/bcp12">BCP 12</a>, <a href="./rfc1466">RFC 1466</a>, November 1996.
519
520 [<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
521 Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
522
523 <span class="h3"><a class="selflink" id="section-7.0" href="#section-7.0">7.0</a> Security Considerations</span>
524
525 IPv6 addressing documents do not have any direct impact on Internet
526 infrastructure security. Authentication of IPv6 packets is defined
527 in [<a href="#ref-AUTH" title="&quot;IP Authentication Header&quot;">AUTH</a>].
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 <span class="grey">Hinden, et. al. Standards Track [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc2374">RFC 2374</a> IPv6 Global Unicast Address Format July 1998</span>
559
560
561 <span class="h3"><a class="selflink" id="section-8.0" href="#section-8.0">8.0</a> Authors' Addresses</span>
562
563 Robert M. Hinden
564 Nokia
565 232 Java Drive
566 Sunnyvale, CA 94089
567 USA
568
569 Phone: 1 408 990-2004
570 EMail: [email protected]
571
572
573 Mike O'Dell
574 UUNET Technologies, Inc.
575 3060 Williams Drive
576 Fairfax, VA 22030
577 USA
578
579 Phone: 1 703 206-5890
580 EMail: [email protected]
581
582
583 Stephen E. Deering
584 Cisco Systems, Inc.
585 170 West Tasman Drive
586 San Jose, CA 95134-1706
587 USA
588
589 Phone: 1 408 527-8213
590 EMail: [email protected]
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612 <span class="grey">Hinden, et. al. Standards Track [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc2374">RFC 2374</a> IPv6 Global Unicast Address Format July 1998</span>
615
616
617 <span class="h3"><a class="selflink" id="section-9.0" href="#section-9.0">9.0</a> Full Copyright Statement</span>
618
619 Copyright (C) The Internet Society (1998). All Rights Reserved.
620
621 This document and translations of it may be copied and furnished to
622 others, and derivative works that comment on or otherwise explain it
623 or assist in its implementation may be prepared, copied, published
624 and distributed, in whole or in part, without restriction of any
625 kind, provided that the above copyright notice and this paragraph are
626 included on all such copies and derivative works. However, this
627 document itself may not be modified in any way, such as by removing
628 the copyright notice or references to the Internet Society or other
629 Internet organizations, except as needed for the purpose of
630 developing Internet standards in which case the procedures for
631 copyrights defined in the Internet Standards process must be
632 followed, or as required to translate it into languages other than
633 English.
634
635 The limited permissions granted above are perpetual and will not be
636 revoked by the Internet Society or its successors or assigns.
637
638 This document and the information contained herein is provided on an
639 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
640 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
641 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
642 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
643 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
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 Hinden, et. al. Standards Track [Page 12]
669 </pre>