rfc4193.txt revision 245bce4ef1e9b3e7e802141dba7c2ca878e4768b
0c27b3fe77ac1d5094ba3521e8142d9e7973133fMark Andrews
7bd455641455950eff7d21be652c8142b134d32fTinderbox User
0c27b3fe77ac1d5094ba3521e8142d9e7973133fMark Andrews
0c27b3fe77ac1d5094ba3521e8142d9e7973133fMark Andrews
0c27b3fe77ac1d5094ba3521e8142d9e7973133fMark Andrews
8cbf3b6fc35091abde426930f2eadb8f53476c98Evan Hunt
866d106459313499d0ca7bfccb4b2d23d5e4377cDavid LawrenceNetwork Working Group R. Hinden
74cb99072c4b0ebd2ccafcfa284288fa760f7a1aMark AndrewsRequest for Comments: 4193 Nokia
bff64bf12b58a6f80e740e94f2e42a32df18113aEvan HuntCategory: Standards Track B. Haberman
866d106459313499d0ca7bfccb4b2d23d5e4377cDavid Lawrence JHU-APL
7c74e180c206e6ed99e8beb820da5f399d845c3eDavid Lawrence October 2005
92b796c963e7ba0217debfa27a0709f94934f5d5Mark Andrews
03e200df5dc283f24a6a349f0b31d3eab26da893Mark Andrews
a5d43b72413db3edd6b36a58f9bdf2cf6ff692f2Bob Halley Unique Local IPv6 Unicast Addresses
a5d43b72413db3edd6b36a58f9bdf2cf6ff692f2Bob Halley
63dd46733010bb9622810faa17d88c3e3c28b730Mark AndrewsStatus of This Memo
a5d43b72413db3edd6b36a58f9bdf2cf6ff692f2Bob Halley
a5d43b72413db3edd6b36a58f9bdf2cf6ff692f2Bob Halley This document specifies an Internet standards track protocol for the
a5d43b72413db3edd6b36a58f9bdf2cf6ff692f2Bob Halley Internet community, and requests discussion and suggestions for
ccdac53c027e8964753b36c4d8c7b0e98af501c2Michael Graff improvements. Please refer to the current edition of the "Internet
f4ea363e3acc321b24ffe95a64a583e8041d6fd5Mark Andrews Official Protocol Standards" (STD 1) for the standardization state
f4ea363e3acc321b24ffe95a64a583e8041d6fd5Mark Andrews and status of this protocol. Distribution of this memo is unlimited.
f4ea363e3acc321b24ffe95a64a583e8041d6fd5Mark Andrews
f4ea363e3acc321b24ffe95a64a583e8041d6fd5Mark AndrewsCopyright Notice
f4ea363e3acc321b24ffe95a64a583e8041d6fd5Mark Andrews
f4ea363e3acc321b24ffe95a64a583e8041d6fd5Mark Andrews Copyright (C) The Internet Society (2005).
f4ea363e3acc321b24ffe95a64a583e8041d6fd5Mark Andrews
f4ea363e3acc321b24ffe95a64a583e8041d6fd5Mark AndrewsAbstract
f4ea363e3acc321b24ffe95a64a583e8041d6fd5Mark Andrews
f4ea363e3acc321b24ffe95a64a583e8041d6fd5Mark Andrews This document defines an IPv6 unicast address format that is globally
f4ea363e3acc321b24ffe95a64a583e8041d6fd5Mark Andrews unique and is intended for local communications, usually inside of a
f4ea363e3acc321b24ffe95a64a583e8041d6fd5Mark Andrews site. These addresses are not expected to be routable on the global
f4ea363e3acc321b24ffe95a64a583e8041d6fd5Mark Andrews Internet.
914eeb33149a0008e26741d9e7d89dcd6f8b6d0bMark Andrews
ccdac53c027e8964753b36c4d8c7b0e98af501c2Michael GraffTable of Contents
a903095bf4512dae561c7f6fc7854a51bebf334aMark Andrews
ccdac53c027e8964753b36c4d8c7b0e98af501c2Michael Graff 1. Introduction ....................................................2
ccdac53c027e8964753b36c4d8c7b0e98af501c2Michael Graff 2. Acknowledgements ................................................3
ccdac53c027e8964753b36c4d8c7b0e98af501c2Michael Graff 3. Local IPv6 Unicast Addresses ....................................3
ccdac53c027e8964753b36c4d8c7b0e98af501c2Michael Graff 3.1. Format .....................................................3
3d776d762914d1b675b4fd49728ce353ccf6f77eBrian Wellington 3.1.1. Background ..........................................4
5b7abbef511cea0b568be0bc8d5b3120a0b9034dEvan Hunt 3.2. Global ID ..................................................4
6b66ee9147e940572a0e873ecbd67456ccb85c39Mark Andrews 3.2.1. Locally Assigned Global IDs .........................5
ccdac53c027e8964753b36c4d8c7b0e98af501c2Michael Graff 3.2.2. Sample Code for Pseudo-Random Global ID Algorithm ...5
11dbf2fc38eea8c5d3fe7123718bf197a8bb2e6bMark Andrews 3.2.3. Analysis of the Uniqueness of Global IDs ............6
11dbf2fc38eea8c5d3fe7123718bf197a8bb2e6bMark Andrews 3.3. Scope Definition ...........................................6
11dbf2fc38eea8c5d3fe7123718bf197a8bb2e6bMark Andrews 4. Operational Guidelines ..........................................7
11dbf2fc38eea8c5d3fe7123718bf197a8bb2e6bMark Andrews 4.1. Routing ....................................................7
11dbf2fc38eea8c5d3fe7123718bf197a8bb2e6bMark Andrews 4.2. Renumbering and Site Merging ...............................7
11dbf2fc38eea8c5d3fe7123718bf197a8bb2e6bMark Andrews 4.3. Site Border Router and Firewall Packet Filtering ...........8
11dbf2fc38eea8c5d3fe7123718bf197a8bb2e6bMark Andrews 4.4. DNS Issues .................................................8
11dbf2fc38eea8c5d3fe7123718bf197a8bb2e6bMark Andrews 4.5. Application and Higher Level Protocol Issues ...............9
11dbf2fc38eea8c5d3fe7123718bf197a8bb2e6bMark Andrews 4.6. Use of Local IPv6 Addresses for Local Communication ........9
11dbf2fc38eea8c5d3fe7123718bf197a8bb2e6bMark Andrews 4.7. Use of Local IPv6 Addresses with VPNs .....................10
11dbf2fc38eea8c5d3fe7123718bf197a8bb2e6bMark Andrews
11dbf2fc38eea8c5d3fe7123718bf197a8bb2e6bMark Andrews
11463c0ac24692e229ec87f307f5e7df3c0a7e10Evan Hunt
11463c0ac24692e229ec87f307f5e7df3c0a7e10Evan HuntHinden & Haberman Standards Track [Page 1]
1c1290afabb3c8f4dd498170ac9592e5be450161Mark Andrews
1c1290afabb3c8f4dd498170ac9592e5be450161Mark AndrewsRFC 4193 Unique Local IPv6 Unicast Addresses October 2005
b123b265e3a3d9b72a14230b6517e0f6fdb5c5b5Mark Andrews
32ebb157b1d9409a186c86002827f8a1f4931f5aMark Andrews
32ebb157b1d9409a186c86002827f8a1f4931f5aMark Andrews 5. Global Routing Considerations ..................................11
740e7340c55e9f0cf80c6fbbf7e8d3c1bdeaa255Mark Andrews 5.1. From the Standpoint of the Internet .......................11
32ebb157b1d9409a186c86002827f8a1f4931f5aMark Andrews 5.2. From the Standpoint of a Site .............................11
84f95ddb2572641022619950a211aff49e331c98Mukund Sivaraman 6. Advantages and Disadvantages ...................................12
32ebb157b1d9409a186c86002827f8a1f4931f5aMark Andrews 6.1. Advantages ................................................12
32ebb157b1d9409a186c86002827f8a1f4931f5aMark Andrews 6.2. Disadvantages .............................................13
32ebb157b1d9409a186c86002827f8a1f4931f5aMark Andrews 7. Security Considerations ........................................13
71697fd082b1c76562dc80fa91787af3860146bfEvan Hunt 8. IANA Considerations ............................................13
1c1290afabb3c8f4dd498170ac9592e5be450161Mark Andrews 9. References .....................................................13
11463c0ac24692e229ec87f307f5e7df3c0a7e10Evan Hunt 9.1. Normative References ......................................13
a97185d9e01800850222878c2af93ea5cb08a68cMark Andrews 9.2. Informative References ....................................14
32ebb157b1d9409a186c86002827f8a1f4931f5aMark Andrews
32ebb157b1d9409a186c86002827f8a1f4931f5aMark Andrews1. Introduction
6fa84a3e255ef9e6233f0a8d134fc6d273f04599Evan Hunt
19d80ce5844e00a021643759adcbe27c11b485a0Witold Krecicki This document defines an IPv6 unicast address format that is globally
19d80ce5844e00a021643759adcbe27c11b485a0Witold Krecicki unique and is intended for local communications [IPV6]. These
19d80ce5844e00a021643759adcbe27c11b485a0Witold Krecicki addresses are called Unique Local IPv6 Unicast Addresses and are
19d80ce5844e00a021643759adcbe27c11b485a0Witold Krecicki abbreviated in this document as Local IPv6 addresses. They are not
19d80ce5844e00a021643759adcbe27c11b485a0Witold Krecicki expected to be routable on the global Internet. They are routable
19d80ce5844e00a021643759adcbe27c11b485a0Witold Krecicki inside of a more limited area such as a site. They may also be
19d80ce5844e00a021643759adcbe27c11b485a0Witold Krecicki routed between a limited set of sites.
19d80ce5844e00a021643759adcbe27c11b485a0Witold Krecicki
19d80ce5844e00a021643759adcbe27c11b485a0Witold Krecicki Local IPv6 unicast addresses have the following characteristics:
6fa84a3e255ef9e6233f0a8d134fc6d273f04599Evan Hunt
6fa84a3e255ef9e6233f0a8d134fc6d273f04599Evan Hunt - Globally unique prefix (with high probability of uniqueness).
1831311ac6179951c8fcca75aa29dc2f5c0218b9Francis Dupont
6fa84a3e255ef9e6233f0a8d134fc6d273f04599Evan Hunt - Well-known prefix to allow for easy filtering at site
206e697f24e47b8868bd68a5b6ef42f5f62e39d5Evan Hunt boundaries.
6fa84a3e255ef9e6233f0a8d134fc6d273f04599Evan Hunt
6fa84a3e255ef9e6233f0a8d134fc6d273f04599Evan Hunt - Allow sites to be combined or privately interconnected without
6fa84a3e255ef9e6233f0a8d134fc6d273f04599Evan Hunt creating any address conflicts or requiring renumbering of
6fa84a3e255ef9e6233f0a8d134fc6d273f04599Evan Hunt interfaces that use these prefixes.
6fa84a3e255ef9e6233f0a8d134fc6d273f04599Evan Hunt
6fa84a3e255ef9e6233f0a8d134fc6d273f04599Evan Hunt - Internet Service Provider independent and can be used for
6fa84a3e255ef9e6233f0a8d134fc6d273f04599Evan Hunt communications inside of a site without having any permanent or
6fa84a3e255ef9e6233f0a8d134fc6d273f04599Evan Hunt intermittent Internet connectivity.
6fa84a3e255ef9e6233f0a8d134fc6d273f04599Evan Hunt
6fa84a3e255ef9e6233f0a8d134fc6d273f04599Evan Hunt - If accidentally leaked outside of a site via routing or DNS,
6fa84a3e255ef9e6233f0a8d134fc6d273f04599Evan Hunt there is no conflict with any other addresses.
6fa84a3e255ef9e6233f0a8d134fc6d273f04599Evan Hunt
6fa84a3e255ef9e6233f0a8d134fc6d273f04599Evan Hunt - In practice, applications may treat these addresses like global
6fa84a3e255ef9e6233f0a8d134fc6d273f04599Evan Hunt scoped addresses.
6fa84a3e255ef9e6233f0a8d134fc6d273f04599Evan Hunt
6fa84a3e255ef9e6233f0a8d134fc6d273f04599Evan Hunt This document defines the format of Local IPv6 addresses, how to
6fa84a3e255ef9e6233f0a8d134fc6d273f04599Evan Hunt allocate them, and usage considerations including routing, site
6fa84a3e255ef9e6233f0a8d134fc6d273f04599Evan Hunt border routers, DNS, application support, VPN usage, and guidelines
6fa84a3e255ef9e6233f0a8d134fc6d273f04599Evan Hunt for how to use for local communication inside a site.
6fa84a3e255ef9e6233f0a8d134fc6d273f04599Evan Hunt
6fa84a3e255ef9e6233f0a8d134fc6d273f04599Evan Hunt
6fa84a3e255ef9e6233f0a8d134fc6d273f04599Evan Hunt
6fa84a3e255ef9e6233f0a8d134fc6d273f04599Evan Hunt
6fa84a3e255ef9e6233f0a8d134fc6d273f04599Evan HuntHinden & Haberman Standards Track [Page 2]
6fa84a3e255ef9e6233f0a8d134fc6d273f04599Evan Hunt
6fa84a3e255ef9e6233f0a8d134fc6d273f04599Evan HuntRFC 4193 Unique Local IPv6 Unicast Addresses October 2005
6fa84a3e255ef9e6233f0a8d134fc6d273f04599Evan Hunt
6fa84a3e255ef9e6233f0a8d134fc6d273f04599Evan Hunt
6fa84a3e255ef9e6233f0a8d134fc6d273f04599Evan Hunt The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
6fa84a3e255ef9e6233f0a8d134fc6d273f04599Evan Hunt "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
6fa84a3e255ef9e6233f0a8d134fc6d273f04599Evan Hunt document are to be interpreted as described in [RFC2119].
6fa84a3e255ef9e6233f0a8d134fc6d273f04599Evan Hunt
6fa84a3e255ef9e6233f0a8d134fc6d273f04599Evan Hunt2. Acknowledgements
6fa84a3e255ef9e6233f0a8d134fc6d273f04599Evan Hunt
6fa84a3e255ef9e6233f0a8d134fc6d273f04599Evan Hunt The underlying idea of creating Local IPv6 addresses described in
6fa84a3e255ef9e6233f0a8d134fc6d273f04599Evan Hunt this document has been proposed a number of times by a variety of
6fa84a3e255ef9e6233f0a8d134fc6d273f04599Evan Hunt people. The authors of this document do not claim exclusive credit.
6fa84a3e255ef9e6233f0a8d134fc6d273f04599Evan Hunt Credit goes to Brian Carpenter, Christian Huitema, Aidan Williams,
6fa84a3e255ef9e6233f0a8d134fc6d273f04599Evan Hunt Andrew White, Charlie Perkins, and many others. The authors would
6fa84a3e255ef9e6233f0a8d134fc6d273f04599Evan Hunt also like to thank Brian Carpenter, Charlie Perkins, Harald
6fa84a3e255ef9e6233f0a8d134fc6d273f04599Evan Hunt Alvestrand, Keith Moore, Margaret Wasserman, Shannon Behrens, Alan
6fa84a3e255ef9e6233f0a8d134fc6d273f04599Evan Hunt Beard, Hans Kruse, Geoff Huston, Pekka Savola, Christian Huitema, Tim
6fa84a3e255ef9e6233f0a8d134fc6d273f04599Evan Hunt Chown, Steve Bellovin, Alex Zinin, Tony Hain, Bill Fenner, Sam
6fa84a3e255ef9e6233f0a8d134fc6d273f04599Evan Hunt Hartman, and Elwyn Davies for their comments and suggestions on this
6fa84a3e255ef9e6233f0a8d134fc6d273f04599Evan Hunt document.
6fa84a3e255ef9e6233f0a8d134fc6d273f04599Evan Hunt
6fa84a3e255ef9e6233f0a8d134fc6d273f04599Evan Hunt3. Local IPv6 Unicast Addresses
6fa84a3e255ef9e6233f0a8d134fc6d273f04599Evan Hunt
6fa84a3e255ef9e6233f0a8d134fc6d273f04599Evan Hunt3.1. Format
6fa84a3e255ef9e6233f0a8d134fc6d273f04599Evan Hunt
6fa84a3e255ef9e6233f0a8d134fc6d273f04599Evan Hunt The Local IPv6 addresses are created using a pseudo-randomly
6fa84a3e255ef9e6233f0a8d134fc6d273f04599Evan Hunt allocated global ID. They have the following format:
6fa84a3e255ef9e6233f0a8d134fc6d273f04599Evan Hunt
206e697f24e47b8868bd68a5b6ef42f5f62e39d5Evan Hunt | 7 bits |1| 40 bits | 16 bits | 64 bits |
6fa84a3e255ef9e6233f0a8d134fc6d273f04599Evan Hunt +--------+-+------------+-----------+----------------------------+
6fa84a3e255ef9e6233f0a8d134fc6d273f04599Evan Hunt | Prefix |L| Global ID | Subnet ID | Interface ID |
6fa84a3e255ef9e6233f0a8d134fc6d273f04599Evan Hunt +--------+-+------------+-----------+----------------------------+
03e200df5dc283f24a6a349f0b31d3eab26da893Mark Andrews
03e200df5dc283f24a6a349f0b31d3eab26da893Mark Andrews Where:
03e200df5dc283f24a6a349f0b31d3eab26da893Mark Andrews
323a9f3430abf186f8f84d795549391a8ed7f274Francis Dupont Prefix FC00::/7 prefix to identify Local IPv6 unicast
03e200df5dc283f24a6a349f0b31d3eab26da893Mark Andrews addresses.
03e200df5dc283f24a6a349f0b31d3eab26da893Mark Andrews
03e200df5dc283f24a6a349f0b31d3eab26da893Mark Andrews L Set to 1 if the prefix is locally assigned.
75a4dd0d377dca2f85cea44e28bf110314c1fe8cDavid Lawrence Set to 0 may be defined in the future. See
75a4dd0d377dca2f85cea44e28bf110314c1fe8cDavid Lawrence Section 3.2 for additional information.
75a4dd0d377dca2f85cea44e28bf110314c1fe8cDavid Lawrence
75a4dd0d377dca2f85cea44e28bf110314c1fe8cDavid Lawrence Global ID 40-bit global identifier used to create a
75a4dd0d377dca2f85cea44e28bf110314c1fe8cDavid Lawrence globally unique prefix. See Section 3.2 for
91306d962f9d147d94b82fb14edb28f8d907cae7Andreas Gustafsson additional information.
91306d962f9d147d94b82fb14edb28f8d907cae7Andreas Gustafsson
91306d962f9d147d94b82fb14edb28f8d907cae7Andreas Gustafsson Subnet ID 16-bit Subnet ID is an identifier of a subnet
91306d962f9d147d94b82fb14edb28f8d907cae7Andreas Gustafsson within the site.
91306d962f9d147d94b82fb14edb28f8d907cae7Andreas Gustafsson
e893dce91279d7313a579f72caae3941f6dc5a27David Lawrence Interface ID 64-bit Interface ID as defined in [ADDARCH].
e893dce91279d7313a579f72caae3941f6dc5a27David Lawrence
e893dce91279d7313a579f72caae3941f6dc5a27David Lawrence
e893dce91279d7313a579f72caae3941f6dc5a27David Lawrence
e893dce91279d7313a579f72caae3941f6dc5a27David Lawrence
e893dce91279d7313a579f72caae3941f6dc5a27David LawrenceHinden & Haberman Standards Track [Page 3]
e893dce91279d7313a579f72caae3941f6dc5a27David Lawrence
e893dce91279d7313a579f72caae3941f6dc5a27David LawrenceRFC 4193 Unique Local IPv6 Unicast Addresses October 2005
e893dce91279d7313a579f72caae3941f6dc5a27David Lawrence
e893dce91279d7313a579f72caae3941f6dc5a27David Lawrence
3b77946b751f39bd4db5a7d1fe48a81e6b1e7a28Bob Halley3.1.1. Background
3b77946b751f39bd4db5a7d1fe48a81e6b1e7a28Bob Halley
3b77946b751f39bd4db5a7d1fe48a81e6b1e7a28Bob Halley There were a range of choices available when choosing the size of the
8e06cea14c857429ab7e7299af2dce5eeeaa5ff0Michael Graff prefix and Global ID field length. There is a direct tradeoff
ce8c568e0d6106bb87069453505e09bc66754b40Andreas Gustafsson between having a Global ID field large enough to support foreseeable
3b77946b751f39bd4db5a7d1fe48a81e6b1e7a28Bob Halley future growth and not using too much of the IPv6 address space
3b77946b751f39bd4db5a7d1fe48a81e6b1e7a28Bob Halley needlessly. A reasonable way of evaluating a specific field length
3b77946b751f39bd4db5a7d1fe48a81e6b1e7a28Bob Halley is to compare it to a projected 2050 world population of 9.3 billion
3b77946b751f39bd4db5a7d1fe48a81e6b1e7a28Bob Halley [POPUL] and the number of resulting /48 prefixes per person. A range
3b77946b751f39bd4db5a7d1fe48a81e6b1e7a28Bob Halley of prefix choices is shown in the following table:
3b77946b751f39bd4db5a7d1fe48a81e6b1e7a28Bob Halley
3b77946b751f39bd4db5a7d1fe48a81e6b1e7a28Bob Halley Prefix Global ID Number of Prefixes % of IPv6
3b77946b751f39bd4db5a7d1fe48a81e6b1e7a28Bob Halley Length /48 Prefixes per Person Address Space
3b77946b751f39bd4db5a7d1fe48a81e6b1e7a28Bob Halley
3b77946b751f39bd4db5a7d1fe48a81e6b1e7a28Bob Halley /11 37 137,438,953,472 15 0.049%
3b77946b751f39bd4db5a7d1fe48a81e6b1e7a28Bob Halley /10 38 274,877,906,944 30 0.098%
3b77946b751f39bd4db5a7d1fe48a81e6b1e7a28Bob Halley /9 39 549,755,813,888 59 0.195%
3b77946b751f39bd4db5a7d1fe48a81e6b1e7a28Bob Halley /8 40 1,099,511,627,776 118 0.391%
8e06cea14c857429ab7e7299af2dce5eeeaa5ff0Michael Graff /7 41 2,199,023,255,552 236 0.781%
8e06cea14c857429ab7e7299af2dce5eeeaa5ff0Michael Graff /6 42 4,398,046,511,104 473 1.563%
3ecf3394e37dc2848a09ffc643565d454e9e6974Andreas Gustafsson
3ecf3394e37dc2848a09ffc643565d454e9e6974Andreas Gustafsson A very high utilization ratio of these allocations can be assumed
a27fe4c990f96bd792f2a07ca4d38c78d5b9df2cTatuya JINMEI 神明達哉 because the Global ID field does not require internal structure, and
a27fe4c990f96bd792f2a07ca4d38c78d5b9df2cTatuya JINMEI 神明達哉 there is no reason to be able to aggregate the prefixes.
3ecf3394e37dc2848a09ffc643565d454e9e6974Andreas Gustafsson
3ecf3394e37dc2848a09ffc643565d454e9e6974Andreas Gustafsson The authors believe that a /7 prefix resulting in a 41-bit Global ID
3ecf3394e37dc2848a09ffc643565d454e9e6974Andreas Gustafsson space (including the L bit) is a good choice. It provides for a
3ecf3394e37dc2848a09ffc643565d454e9e6974Andreas Gustafsson large number of assignments (i.e., 2.2 trillion) and at the same time
1cefb9df3fa34d08734f29005cfafa6be5cf3e93Mark Andrews uses less than .8% of the total IPv6 address space. It is unlikely
1cefb9df3fa34d08734f29005cfafa6be5cf3e93Mark Andrews that this space will be exhausted. If more than this were to be
1cefb9df3fa34d08734f29005cfafa6be5cf3e93Mark Andrews needed, then additional IPv6 address space could be allocated for
1cefb9df3fa34d08734f29005cfafa6be5cf3e93Mark Andrews this purpose.
1cefb9df3fa34d08734f29005cfafa6be5cf3e93Mark Andrews
b5f6271f4daf1e54501af2cb7dd278d7e8003d65Mark Andrews3.2. Global ID
1cefb9df3fa34d08734f29005cfafa6be5cf3e93Mark Andrews
1cefb9df3fa34d08734f29005cfafa6be5cf3e93Mark Andrews The allocation of Global IDs is pseudo-random [RANDOM]. They MUST
9f5443280fcfd625a06f63a1b457ed2335840278Mark Andrews NOT be assigned sequentially or with well-known numbers. This is to
f6096b958c8b58c4709860d7c4dcdde5deeacb7aEvan Hunt ensure that there is not any relationship between allocations and to
f6096b958c8b58c4709860d7c4dcdde5deeacb7aEvan Hunt help clarify that these prefixes are not intended to be routed
f6096b958c8b58c4709860d7c4dcdde5deeacb7aEvan Hunt globally. Specifically, these prefixes are not designed to
f6096b958c8b58c4709860d7c4dcdde5deeacb7aEvan Hunt aggregate.
f6096b958c8b58c4709860d7c4dcdde5deeacb7aEvan Hunt
523f3d630243211ddfda852f5224f7eff681d3a5Evan Hunt This document defines a specific local method to allocate Global IDs,
f6096b958c8b58c4709860d7c4dcdde5deeacb7aEvan Hunt indicated by setting the L bit to 1. Another method, indicated by
1cefb9df3fa34d08734f29005cfafa6be5cf3e93Mark Andrews clearing the L bit, may be defined later. Apart from the allocation
1cefb9df3fa34d08734f29005cfafa6be5cf3e93Mark Andrews method, all Local IPv6 addresses behave and are treated identically.
523f3d630243211ddfda852f5224f7eff681d3a5Evan Hunt
1cefb9df3fa34d08734f29005cfafa6be5cf3e93Mark Andrews
1cefb9df3fa34d08734f29005cfafa6be5cf3e93Mark Andrews
1cefb9df3fa34d08734f29005cfafa6be5cf3e93Mark Andrews
1cefb9df3fa34d08734f29005cfafa6be5cf3e93Mark Andrews
1cefb9df3fa34d08734f29005cfafa6be5cf3e93Mark AndrewsHinden & Haberman Standards Track [Page 4]
523f3d630243211ddfda852f5224f7eff681d3a5Evan Hunt
523f3d630243211ddfda852f5224f7eff681d3a5Evan HuntRFC 4193 Unique Local IPv6 Unicast Addresses October 2005
523f3d630243211ddfda852f5224f7eff681d3a5Evan Hunt
1f27b7873c640771df00a47ee3be188c4079479cFrancis Dupont
523f3d630243211ddfda852f5224f7eff681d3a5Evan Hunt The local assignments are self-generated and do not need any central
523f3d630243211ddfda852f5224f7eff681d3a5Evan Hunt coordination or assignment, but have an extremely high probability of
523f3d630243211ddfda852f5224f7eff681d3a5Evan Hunt being unique.
f6096b958c8b58c4709860d7c4dcdde5deeacb7aEvan Hunt
f6096b958c8b58c4709860d7c4dcdde5deeacb7aEvan Hunt3.2.1. Locally Assigned Global IDs
f6096b958c8b58c4709860d7c4dcdde5deeacb7aEvan Hunt
f6096b958c8b58c4709860d7c4dcdde5deeacb7aEvan Hunt Locally assigned Global IDs MUST be generated with a pseudo-random
f6096b958c8b58c4709860d7c4dcdde5deeacb7aEvan Hunt algorithm consistent with [RANDOM]. Section 3.2.2 describes a
f6096b958c8b58c4709860d7c4dcdde5deeacb7aEvan Hunt suggested algorithm. It is important that all sites generating
f6096b958c8b58c4709860d7c4dcdde5deeacb7aEvan Hunt Global IDs use a functionally similar algorithm to ensure there is a
f6096b958c8b58c4709860d7c4dcdde5deeacb7aEvan Hunt high probability of uniqueness.
f6096b958c8b58c4709860d7c4dcdde5deeacb7aEvan Hunt
f6096b958c8b58c4709860d7c4dcdde5deeacb7aEvan Hunt The use of a pseudo-random algorithm to generate Global IDs in the
f6096b958c8b58c4709860d7c4dcdde5deeacb7aEvan Hunt locally assigned prefix gives an assurance that any network numbered
f6096b958c8b58c4709860d7c4dcdde5deeacb7aEvan Hunt using such a prefix is highly unlikely to have that address space
523f3d630243211ddfda852f5224f7eff681d3a5Evan Hunt clash with any other network that has another locally assigned prefix
470af54b4ec7ab38ad10a5bd22a0a20664838c99Evan Hunt allocated to it. This is a particularly useful property when
470af54b4ec7ab38ad10a5bd22a0a20664838c99Evan Hunt considering a number of scenarios including networks that merge,
470af54b4ec7ab38ad10a5bd22a0a20664838c99Evan Hunt overlapping VPN address space, or hosts mobile between such networks.
470af54b4ec7ab38ad10a5bd22a0a20664838c99Evan Hunt
523f3d630243211ddfda852f5224f7eff681d3a5Evan Hunt3.2.2. Sample Code for Pseudo-Random Global ID Algorithm
523f3d630243211ddfda852f5224f7eff681d3a5Evan Hunt
1f27b7873c640771df00a47ee3be188c4079479cFrancis Dupont The algorithm described below is intended to be used for locally
523f3d630243211ddfda852f5224f7eff681d3a5Evan Hunt assigned Global IDs. In each case the resulting global ID will be
523f3d630243211ddfda852f5224f7eff681d3a5Evan Hunt used in the appropriate prefix as defined in Section 3.2.
523f3d630243211ddfda852f5224f7eff681d3a5Evan Hunt
523f3d630243211ddfda852f5224f7eff681d3a5Evan Hunt 1) Obtain the current time of day in 64-bit NTP format [NTP].
523f3d630243211ddfda852f5224f7eff681d3a5Evan Hunt
523f3d630243211ddfda852f5224f7eff681d3a5Evan Hunt 2) Obtain an EUI-64 identifier from the system running this
523f3d630243211ddfda852f5224f7eff681d3a5Evan Hunt algorithm. If an EUI-64 does not exist, one can be created from
523f3d630243211ddfda852f5224f7eff681d3a5Evan Hunt a 48-bit MAC address as specified in [ADDARCH]. If an EUI-64
523f3d630243211ddfda852f5224f7eff681d3a5Evan Hunt cannot be obtained or created, a suitably unique identifier,
523f3d630243211ddfda852f5224f7eff681d3a5Evan Hunt local to the node, should be used (e.g., system serial number).
523f3d630243211ddfda852f5224f7eff681d3a5Evan Hunt
1cefb9df3fa34d08734f29005cfafa6be5cf3e93Mark Andrews 3) Concatenate the time of day with the system-specific identifier
1cefb9df3fa34d08734f29005cfafa6be5cf3e93Mark Andrews in order to create a key.
1cefb9df3fa34d08734f29005cfafa6be5cf3e93Mark Andrews
523f3d630243211ddfda852f5224f7eff681d3a5Evan Hunt 4) Compute an SHA-1 digest on the key as specified in [FIPS, SHA1];
523f3d630243211ddfda852f5224f7eff681d3a5Evan Hunt the resulting value is 160 bits.
1cefb9df3fa34d08734f29005cfafa6be5cf3e93Mark Andrews
523f3d630243211ddfda852f5224f7eff681d3a5Evan Hunt 5) Use the least significant 40 bits as the Global ID.
523f3d630243211ddfda852f5224f7eff681d3a5Evan Hunt
1cefb9df3fa34d08734f29005cfafa6be5cf3e93Mark Andrews 6) Concatenate FC00::/7, the L bit set to 1, and the 40-bit Global
1cefb9df3fa34d08734f29005cfafa6be5cf3e93Mark Andrews ID to create a Local IPv6 address prefix.
523f3d630243211ddfda852f5224f7eff681d3a5Evan Hunt
f6096b958c8b58c4709860d7c4dcdde5deeacb7aEvan Hunt This algorithm will result in a Global ID that is reasonably unique
f6096b958c8b58c4709860d7c4dcdde5deeacb7aEvan Hunt and can be used to create a locally assigned Local IPv6 address
f6096b958c8b58c4709860d7c4dcdde5deeacb7aEvan Hunt prefix.
f6096b958c8b58c4709860d7c4dcdde5deeacb7aEvan Hunt
f6096b958c8b58c4709860d7c4dcdde5deeacb7aEvan Hunt
f6096b958c8b58c4709860d7c4dcdde5deeacb7aEvan Hunt
f6096b958c8b58c4709860d7c4dcdde5deeacb7aEvan HuntHinden & Haberman Standards Track [Page 5]
523f3d630243211ddfda852f5224f7eff681d3a5Evan Hunt
523f3d630243211ddfda852f5224f7eff681d3a5Evan HuntRFC 4193 Unique Local IPv6 Unicast Addresses October 2005
523f3d630243211ddfda852f5224f7eff681d3a5Evan Hunt
523f3d630243211ddfda852f5224f7eff681d3a5Evan Hunt
523f3d630243211ddfda852f5224f7eff681d3a5Evan Hunt3.2.3. Analysis of the Uniqueness of Global IDs
523f3d630243211ddfda852f5224f7eff681d3a5Evan Hunt
1cefb9df3fa34d08734f29005cfafa6be5cf3e93Mark Andrews The selection of a pseudo random Global ID is similar to the
1cefb9df3fa34d08734f29005cfafa6be5cf3e93Mark Andrews selection of an SSRC identifier in RTP/RTCP defined in Section 8.1 of
1cefb9df3fa34d08734f29005cfafa6be5cf3e93Mark Andrews [RTP]. This analysis is adapted from that document.
1cefb9df3fa34d08734f29005cfafa6be5cf3e93Mark Andrews
66dddd906ada6035d65bbbad2ecbcd74037759a8Mark Andrews Since Global IDs are chosen randomly (and independently), it is
831f59eb43b56642b00f82e07722836d2f9593abEvan Hunt possible that separate networks have chosen the same Global ID. For
f6096b958c8b58c4709860d7c4dcdde5deeacb7aEvan Hunt any given network, with one or more random Global IDs, that has
1cefb9df3fa34d08734f29005cfafa6be5cf3e93Mark Andrews inter-connections to other such networks, having a total of N such
d7729155dff87d3c7a2b9103bf6e5164ea4d7dd7Mark Andrews IDs, the probability that two or more of these IDs will collide can
66dddd906ada6035d65bbbad2ecbcd74037759a8Mark Andrews be approximated using the formula:
831f59eb43b56642b00f82e07722836d2f9593abEvan Hunt
f6096b958c8b58c4709860d7c4dcdde5deeacb7aEvan Hunt P = 1 - exp(-N**2 / 2**(L+1))
1cefb9df3fa34d08734f29005cfafa6be5cf3e93Mark Andrews
66dddd906ada6035d65bbbad2ecbcd74037759a8Mark Andrews where P is the probability of collision, N is the number of
831f59eb43b56642b00f82e07722836d2f9593abEvan Hunt interconnected Global IDs, and L is the length of the Global ID.
f6096b958c8b58c4709860d7c4dcdde5deeacb7aEvan Hunt
1cefb9df3fa34d08734f29005cfafa6be5cf3e93Mark Andrews The following table shows the probability of a collision for a range
1cefb9df3fa34d08734f29005cfafa6be5cf3e93Mark Andrews of connections using a 40-bit Global ID field.
df3c4c7988b9bae7d121a8ac9ed17a23366a948dDavid Lawrence
df3c4c7988b9bae7d121a8ac9ed17a23366a948dDavid Lawrence Connections Probability of Collision
df3c4c7988b9bae7d121a8ac9ed17a23366a948dDavid Lawrence
b587e1d83f007ce68a9ae93097c461d8eb7aa373Mark Andrews 2 1.81*10^-12
df3c4c7988b9bae7d121a8ac9ed17a23366a948dDavid Lawrence 10 4.54*10^-11
df3c4c7988b9bae7d121a8ac9ed17a23366a948dDavid Lawrence 100 4.54*10^-09
df3c4c7988b9bae7d121a8ac9ed17a23366a948dDavid Lawrence 1000 4.54*10^-07
df3c4c7988b9bae7d121a8ac9ed17a23366a948dDavid Lawrence 10000 4.54*10^-05
df3c4c7988b9bae7d121a8ac9ed17a23366a948dDavid Lawrence
df3c4c7988b9bae7d121a8ac9ed17a23366a948dDavid Lawrence Based on this analysis, the uniqueness of locally generated Global
df3c4c7988b9bae7d121a8ac9ed17a23366a948dDavid Lawrence IDs is adequate for sites planning a small to moderate amount of
df3c4c7988b9bae7d121a8ac9ed17a23366a948dDavid Lawrence inter-site communication using locally generated Global IDs.
df3c4c7988b9bae7d121a8ac9ed17a23366a948dDavid Lawrence
df3c4c7988b9bae7d121a8ac9ed17a23366a948dDavid Lawrence3.3. Scope Definition
df3c4c7988b9bae7d121a8ac9ed17a23366a948dDavid Lawrence
df3c4c7988b9bae7d121a8ac9ed17a23366a948dDavid Lawrence By default, the scope of these addresses is global. That is, they
df3c4c7988b9bae7d121a8ac9ed17a23366a948dDavid Lawrence are not limited by ambiguity like the site-local addresses defined in
df3c4c7988b9bae7d121a8ac9ed17a23366a948dDavid Lawrence [ADDARCH]. Rather, these prefixes are globally unique, and as such,
df3c4c7988b9bae7d121a8ac9ed17a23366a948dDavid Lawrence their applicability is greater than site-local addresses. Their
df3c4c7988b9bae7d121a8ac9ed17a23366a948dDavid Lawrence limitation is in the routability of the prefixes, which is limited to
ae4cbb69eef32ced103fe4561e8d2031ee4c3497David Lawrence a site and any explicit routing agreements with other sites to
289ae548d52bc8f982d9823af64cafda7bd92232Mark Andrews propagate them (also see Section 4.1). Also, unlike site-locals, a
289ae548d52bc8f982d9823af64cafda7bd92232Mark Andrews site may have more than one of these prefixes and use them at the
289ae548d52bc8f982d9823af64cafda7bd92232Mark Andrews same time.
289ae548d52bc8f982d9823af64cafda7bd92232Mark Andrews
289ae548d52bc8f982d9823af64cafda7bd92232Mark Andrews
289ae548d52bc8f982d9823af64cafda7bd92232Mark Andrews
289ae548d52bc8f982d9823af64cafda7bd92232Mark Andrews
289ae548d52bc8f982d9823af64cafda7bd92232Mark Andrews
289ae548d52bc8f982d9823af64cafda7bd92232Mark Andrews
289ae548d52bc8f982d9823af64cafda7bd92232Mark Andrews
289ae548d52bc8f982d9823af64cafda7bd92232Mark AndrewsHinden & Haberman Standards Track [Page 6]
289ae548d52bc8f982d9823af64cafda7bd92232Mark Andrews
ae4cbb69eef32ced103fe4561e8d2031ee4c3497David LawrenceRFC 4193 Unique Local IPv6 Unicast Addresses October 2005
f6096b958c8b58c4709860d7c4dcdde5deeacb7aEvan Hunt
f6096b958c8b58c4709860d7c4dcdde5deeacb7aEvan Hunt
ae4cbb69eef32ced103fe4561e8d2031ee4c3497David Lawrence4. Operational Guidelines
df3c4c7988b9bae7d121a8ac9ed17a23366a948dDavid Lawrence
df3c4c7988b9bae7d121a8ac9ed17a23366a948dDavid Lawrence The guidelines in this section do not require any change to the
df3c4c7988b9bae7d121a8ac9ed17a23366a948dDavid Lawrence normal routing and forwarding functionality in an IPv6 host or
df3c4c7988b9bae7d121a8ac9ed17a23366a948dDavid Lawrence router. These are configuration and operational usage guidelines.
df3c4c7988b9bae7d121a8ac9ed17a23366a948dDavid Lawrence
df3c4c7988b9bae7d121a8ac9ed17a23366a948dDavid Lawrence4.1. Routing
df3c4c7988b9bae7d121a8ac9ed17a23366a948dDavid Lawrence
df3c4c7988b9bae7d121a8ac9ed17a23366a948dDavid Lawrence Local IPv6 addresses are designed to be routed inside of a site in
0293ad13207aa29bd5844cdc87d085ffc009d749David Lawrence the same manner as other types of unicast addresses. They can be
0293ad13207aa29bd5844cdc87d085ffc009d749David Lawrence carried in any IPv6 routing protocol without any change.
289ae548d52bc8f982d9823af64cafda7bd92232Mark Andrews
289ae548d52bc8f982d9823af64cafda7bd92232Mark Andrews It is expected that they would share the same Subnet IDs with
289ae548d52bc8f982d9823af64cafda7bd92232Mark Andrews provider-based global unicast addresses, if they were being used
289ae548d52bc8f982d9823af64cafda7bd92232Mark Andrews concurrently [GLOBAL].
289ae548d52bc8f982d9823af64cafda7bd92232Mark Andrews
289ae548d52bc8f982d9823af64cafda7bd92232Mark Andrews The default behavior of exterior routing protocol sessions between
289ae548d52bc8f982d9823af64cafda7bd92232Mark Andrews administrative routing regions must be to ignore receipt of and not
289ae548d52bc8f982d9823af64cafda7bd92232Mark Andrews advertise prefixes in the FC00::/7 block. A network operator may
289ae548d52bc8f982d9823af64cafda7bd92232Mark Andrews specifically configure prefixes longer than FC00::/7 for inter-site
289ae548d52bc8f982d9823af64cafda7bd92232Mark Andrews communication.
289ae548d52bc8f982d9823af64cafda7bd92232Mark Andrews
289ae548d52bc8f982d9823af64cafda7bd92232Mark Andrews If BGP is being used at the site border with an ISP, the default BGP
289ae548d52bc8f982d9823af64cafda7bd92232Mark Andrews configuration must filter out any Local IPv6 address prefixes, both
289ae548d52bc8f982d9823af64cafda7bd92232Mark Andrews incoming and outgoing. It must be set both to keep any Local IPv6
0293ad13207aa29bd5844cdc87d085ffc009d749David Lawrence address prefixes from being advertised outside of the site as well as
0293ad13207aa29bd5844cdc87d085ffc009d749David Lawrence to keep these prefixes from being learned from another site. The
df3c4c7988b9bae7d121a8ac9ed17a23366a948dDavid Lawrence exception to this is if there are specific /48 or longer routes
df3c4c7988b9bae7d121a8ac9ed17a23366a948dDavid Lawrence created for one or more Local IPv6 prefixes.
df3c4c7988b9bae7d121a8ac9ed17a23366a948dDavid Lawrence
df3c4c7988b9bae7d121a8ac9ed17a23366a948dDavid Lawrence For link-state IGPs, it is suggested that a site utilizing IPv6 local
df3c4c7988b9bae7d121a8ac9ed17a23366a948dDavid Lawrence address prefixes be contained within one IGP domain or area. By
df3c4c7988b9bae7d121a8ac9ed17a23366a948dDavid Lawrence containing an IPv6 local address prefix to a single link-state area
df3c4c7988b9bae7d121a8ac9ed17a23366a948dDavid Lawrence or domain, the distribution of prefixes can be controlled.
df3c4c7988b9bae7d121a8ac9ed17a23366a948dDavid Lawrence
657ce0b9d84fbd66514df53d61a087e8f1161187Michael Graff4.2. Renumbering and Site Merging
657ce0b9d84fbd66514df53d61a087e8f1161187Michael Graff
657ce0b9d84fbd66514df53d61a087e8f1161187Michael Graff The use of Local IPv6 addresses in a site results in making
657ce0b9d84fbd66514df53d61a087e8f1161187Michael Graff communication that uses these addresses independent of renumbering a
657ce0b9d84fbd66514df53d61a087e8f1161187Michael Graff site's provider-based global addresses.
1ce985ab3c6670662d555c108b35fed84a6a1001David Lawrence
289ae548d52bc8f982d9823af64cafda7bd92232Mark Andrews When merging multiple sites, the addresses created with these
289ae548d52bc8f982d9823af64cafda7bd92232Mark Andrews prefixes are unlikely to need to be renumbered because all of the
289ae548d52bc8f982d9823af64cafda7bd92232Mark Andrews addresses have a high probability of being unique. Routes for each
289ae548d52bc8f982d9823af64cafda7bd92232Mark Andrews specific prefix would have to be configured to allow routing to work
289ae548d52bc8f982d9823af64cafda7bd92232Mark Andrews correctly between the formerly separate sites.
289ae548d52bc8f982d9823af64cafda7bd92232Mark Andrews
4bcaefbcd3ced942139fdc830e007c6ea2b8d2feDavid Lawrence
4bcaefbcd3ced942139fdc830e007c6ea2b8d2feDavid Lawrence
4bcaefbcd3ced942139fdc830e007c6ea2b8d2feDavid Lawrence
4bcaefbcd3ced942139fdc830e007c6ea2b8d2feDavid Lawrence
4bcaefbcd3ced942139fdc830e007c6ea2b8d2feDavid LawrenceHinden & Haberman Standards Track [Page 7]
4bcaefbcd3ced942139fdc830e007c6ea2b8d2feDavid Lawrence
4bcaefbcd3ced942139fdc830e007c6ea2b8d2feDavid LawrenceRFC 4193 Unique Local IPv6 Unicast Addresses October 2005
4bcaefbcd3ced942139fdc830e007c6ea2b8d2feDavid Lawrence
4bcaefbcd3ced942139fdc830e007c6ea2b8d2feDavid Lawrence
4bcaefbcd3ced942139fdc830e007c6ea2b8d2feDavid Lawrence4.3. Site Border Router and Firewall Packet Filtering
4bcaefbcd3ced942139fdc830e007c6ea2b8d2feDavid Lawrence
4bcaefbcd3ced942139fdc830e007c6ea2b8d2feDavid Lawrence While no serious harm will be done if packets with these addresses
4bcaefbcd3ced942139fdc830e007c6ea2b8d2feDavid Lawrence are sent outside of a site via a default route, it is recommended
4bcaefbcd3ced942139fdc830e007c6ea2b8d2feDavid Lawrence that routers be configured by default to keep any packets with Local
4bcaefbcd3ced942139fdc830e007c6ea2b8d2feDavid Lawrence IPv6 addresses from leaking outside of the site and to keep any site
4bcaefbcd3ced942139fdc830e007c6ea2b8d2feDavid Lawrence prefixes from being advertised outside of their site.
657ce0b9d84fbd66514df53d61a087e8f1161187Michael Graff
657ce0b9d84fbd66514df53d61a087e8f1161187Michael Graff Site border routers and firewalls should be configured to not forward
657ce0b9d84fbd66514df53d61a087e8f1161187Michael Graff any packets with Local IPv6 source or destination addresses outside
657ce0b9d84fbd66514df53d61a087e8f1161187Michael Graff of the site, unless they have been explicitly configured with routing
657ce0b9d84fbd66514df53d61a087e8f1161187Michael Graff information about specific /48 or longer Local IPv6 prefixes. This
657ce0b9d84fbd66514df53d61a087e8f1161187Michael Graff will ensure that packets with Local IPv6 destination addresses will
657ce0b9d84fbd66514df53d61a087e8f1161187Michael Graff not be forwarded outside of the site via a default route. The
657ce0b9d84fbd66514df53d61a087e8f1161187Michael Graff default behavior of these devices should be to install a "reject"
657ce0b9d84fbd66514df53d61a087e8f1161187Michael Graff route for these prefixes. Site border routers should respond with
657ce0b9d84fbd66514df53d61a087e8f1161187Michael Graff the appropriate ICMPv6 Destination Unreachable message to inform the
5ff133b82082d82f0ba89b7c999c6b62b6298e46Andreas Gustafsson source that the packet was not forwarded. [ICMPV6]. This feedback is
5ff133b82082d82f0ba89b7c999c6b62b6298e46Andreas Gustafsson important to avoid transport protocol timeouts.
641da3ca1184d9951d5cf91538524a345bf5f271Mark Andrews
641da3ca1184d9951d5cf91538524a345bf5f271Mark Andrews Routers that maintain peering arrangements between Autonomous Systems
641da3ca1184d9951d5cf91538524a345bf5f271Mark Andrews throughout the Internet should obey the recommendations for site
641da3ca1184d9951d5cf91538524a345bf5f271Mark Andrews border routers, unless configured otherwise.
641da3ca1184d9951d5cf91538524a345bf5f271Mark Andrews
80badf38c74c326a694e24281ee258aa26984171Mark Andrews4.4. DNS Issues
641da3ca1184d9951d5cf91538524a345bf5f271Mark Andrews
641da3ca1184d9951d5cf91538524a345bf5f271Mark Andrews At the present time, AAAA and PTR records for locally assigned local
641da3ca1184d9951d5cf91538524a345bf5f271Mark Andrews IPv6 addresses are not recommended to be installed in the global DNS.
641da3ca1184d9951d5cf91538524a345bf5f271Mark Andrews
641da3ca1184d9951d5cf91538524a345bf5f271Mark Andrews For background on this recommendation, one of the concerns about
9fe28a624c659e380d47dbf45527637dab03b998Mark Andrews adding AAAA and PTR records to the global DNS for locally assigned
774c3a62d9adca187b44fe90919bb409a43a2f2aMark Andrews Local IPv6 addresses stems from the lack of complete assurance that
9fe28a624c659e380d47dbf45527637dab03b998Mark Andrews the prefixes are unique. There is a small possibility that the same
9fe28a624c659e380d47dbf45527637dab03b998Mark Andrews locally assigned IPv6 Local addresses will be used by two different
323a9f3430abf186f8f84d795549391a8ed7f274Francis Dupont organizations both claiming to be authoritative with different
774c3a62d9adca187b44fe90919bb409a43a2f2aMark Andrews contents. In this scenario, it is likely there will be a connection
9fe28a624c659e380d47dbf45527637dab03b998Mark Andrews attempt to the closest host with the corresponding locally assigned
9fe28a624c659e380d47dbf45527637dab03b998Mark Andrews IPv6 Local address. This may result in connection timeouts,
9fe28a624c659e380d47dbf45527637dab03b998Mark Andrews connection failures indicated by ICMP Destination Unreachable
9fe28a624c659e380d47dbf45527637dab03b998Mark Andrews messages, or successful connections to the wrong host. Due to this
774c3a62d9adca187b44fe90919bb409a43a2f2aMark Andrews concern, adding AAAA records for these addresses to the global DNS is
774c3a62d9adca187b44fe90919bb409a43a2f2aMark Andrews thought to be unwise.
774c3a62d9adca187b44fe90919bb409a43a2f2aMark Andrews
774c3a62d9adca187b44fe90919bb409a43a2f2aMark Andrews Reverse (address-to-name) queries for locally assigned IPv6 Local
774c3a62d9adca187b44fe90919bb409a43a2f2aMark Andrews addresses MUST NOT be sent to name servers for the global DNS, due to
774c3a62d9adca187b44fe90919bb409a43a2f2aMark Andrews the load that such queries would create for the authoritative name
774c3a62d9adca187b44fe90919bb409a43a2f2aMark Andrews servers for the ip6.arpa zone. This form of query load is not
774c3a62d9adca187b44fe90919bb409a43a2f2aMark Andrews specific to locally assigned Local IPv6 addresses; any current form
774c3a62d9adca187b44fe90919bb409a43a2f2aMark Andrews
774c3a62d9adca187b44fe90919bb409a43a2f2aMark Andrews
774c3a62d9adca187b44fe90919bb409a43a2f2aMark Andrews
d7896edb4e93c4785a9281ea86afba86b758e813Mark AndrewsHinden & Haberman Standards Track [Page 8]
d7896edb4e93c4785a9281ea86afba86b758e813Mark Andrews
d7896edb4e93c4785a9281ea86afba86b758e813Mark AndrewsRFC 4193 Unique Local IPv6 Unicast Addresses October 2005
d7896edb4e93c4785a9281ea86afba86b758e813Mark Andrews
d7896edb4e93c4785a9281ea86afba86b758e813Mark Andrews
89119e3cafff373426858f6cec7c09539f53e209Mark Andrews of local addressing creates additional load of this kind, due to
d7896edb4e93c4785a9281ea86afba86b758e813Mark Andrews reverse queries leaking out of the site. However, since allowing
d7896edb4e93c4785a9281ea86afba86b758e813Mark Andrews such queries to escape from the site serves no useful purpose, there
d7896edb4e93c4785a9281ea86afba86b758e813Mark Andrews is no good reason to make the existing load problems worse.
ab3aeba682460fd39deb7901aa69f976583c9f47Michael Graff
ab3aeba682460fd39deb7901aa69f976583c9f47Michael Graff The recommended way to avoid sending such queries to nameservers for
ab3aeba682460fd39deb7901aa69f976583c9f47Michael Graff the global DNS is for recursive name server implementations to act as
ab3aeba682460fd39deb7901aa69f976583c9f47Michael Graff if they were authoritative for an empty d.f.ip6.arpa zone and return
ab3aeba682460fd39deb7901aa69f976583c9f47Michael Graff RCODE 3 for any such query. Implementations that choose this
ab3aeba682460fd39deb7901aa69f976583c9f47Michael Graff strategy should allow it to be overridden, but returning an RCODE 3
ab3aeba682460fd39deb7901aa69f976583c9f47Michael Graff response for such queries should be the default, both because this
ab3aeba682460fd39deb7901aa69f976583c9f47Michael Graff will reduce the query load problem and also because, if the site
9fe28a624c659e380d47dbf45527637dab03b998Mark Andrews administrator has not set up the reverse tree corresponding to the
9fe28a624c659e380d47dbf45527637dab03b998Mark Andrews locally assigned IPv6 Local addresses in use, returning RCODE 3 is in
5b7abbef511cea0b568be0bc8d5b3120a0b9034dEvan Hunt fact the correct answer.
5b7abbef511cea0b568be0bc8d5b3120a0b9034dEvan Hunt
5b7abbef511cea0b568be0bc8d5b3120a0b9034dEvan Hunt4.5. Application and Higher Level Protocol Issues
5b7abbef511cea0b568be0bc8d5b3120a0b9034dEvan Hunt
5b7abbef511cea0b568be0bc8d5b3120a0b9034dEvan Hunt Application and other higher level protocols can treat Local IPv6
5b7abbef511cea0b568be0bc8d5b3120a0b9034dEvan Hunt addresses in the same manner as other types of global unicast
5b7abbef511cea0b568be0bc8d5b3120a0b9034dEvan Hunt addresses. No special handling is required. This type of address
5ff133b82082d82f0ba89b7c999c6b62b6298e46Andreas Gustafsson may not be reachable, but that is no different from other types of
5ff133b82082d82f0ba89b7c999c6b62b6298e46Andreas Gustafsson IPv6 global unicast address. Applications need to be able to handle
850b5e80930907e4747347201dc41e4d04e036f8Mark Andrews multiple addresses that may or may not be reachable at any point in
6342df69b05f2f62d060fd4affdf536e51504084Mark Andrews time. In most cases, this complexity should be hidden in APIs.
6342df69b05f2f62d060fd4affdf536e51504084Mark Andrews
6342df69b05f2f62d060fd4affdf536e51504084Mark Andrews From a host's perspective, the difference between Local IPv6 and
6342df69b05f2f62d060fd4affdf536e51504084Mark Andrews other types of global unicast addresses shows up as different
62ec9fd1681ffae7d6b0d54618599ecf650e3100Mark Andrews reachability and could be handled by default in that way. In some
62ec9fd1681ffae7d6b0d54618599ecf650e3100Mark Andrews cases, it is better for nodes and applications to treat them
62ec9fd1681ffae7d6b0d54618599ecf650e3100Mark Andrews differently from global unicast addresses. A starting point might be
6342df69b05f2f62d060fd4affdf536e51504084Mark Andrews to give them preference over global unicast, but fall back to global
5ff133b82082d82f0ba89b7c999c6b62b6298e46Andreas Gustafsson unicast if a particular destination is found to be unreachable. Much
5ff133b82082d82f0ba89b7c999c6b62b6298e46Andreas Gustafsson of this behavior can be controlled by how they are allocated to nodes
5ff133b82082d82f0ba89b7c999c6b62b6298e46Andreas Gustafsson and put into the DNS. However, it is useful if a host can have both
8486ce1efa5deded85415d21d5696e5a51c63357Mark Andrews types of addresses and use them appropriately.
c654449ccf403ccd2b81be2038b1013d6fbb06ccMark Andrews
5b02fc32d693bb811199308a40143df0adf818c1Mark Andrews Note that the address selection mechanisms of [ADDSEL], and in
6fcb2f0faad67a6d2cb2e30ec57157d75fbfe58fAndreas Gustafsson particular the policy override mechanism replacing default address
5506903c9215faf42586307c2288942fd804c579Evan Hunt selection, are expected to be used on a site where Local IPv6
5506903c9215faf42586307c2288942fd804c579Evan Hunt addresses are configured.
5506903c9215faf42586307c2288942fd804c579Evan Hunt
5506903c9215faf42586307c2288942fd804c579Evan Hunt4.6. Use of Local IPv6 Addresses for Local Communication
5506903c9215faf42586307c2288942fd804c579Evan Hunt
38cd4d14cc341c2663e574035074788bb6f0fce2Evan Hunt Local IPv6 addresses, like global scope unicast addresses, are only
38cd4d14cc341c2663e574035074788bb6f0fce2Evan Hunt assigned to nodes if their use has been enabled (via IPv6 address
38cd4d14cc341c2663e574035074788bb6f0fce2Evan Hunt autoconfiguration [ADDAUTO], DHCPv6 [DHCP6], or manually). They are
38cd4d14cc341c2663e574035074788bb6f0fce2Evan Hunt
38cd4d14cc341c2663e574035074788bb6f0fce2Evan Hunt
38cd4d14cc341c2663e574035074788bb6f0fce2Evan Hunt
d8f2dd46cba3a16c2433e85657a5b15543013ca6Mark Andrews
d8f2dd46cba3a16c2433e85657a5b15543013ca6Mark AndrewsHinden & Haberman Standards Track [Page 9]
d8f2dd46cba3a16c2433e85657a5b15543013ca6Mark Andrews
6fcb2f0faad67a6d2cb2e30ec57157d75fbfe58fAndreas GustafssonRFC 4193 Unique Local IPv6 Unicast Addresses October 2005
6fcb2f0faad67a6d2cb2e30ec57157d75fbfe58fAndreas Gustafsson
6fcb2f0faad67a6d2cb2e30ec57157d75fbfe58fAndreas Gustafsson
6fcb2f0faad67a6d2cb2e30ec57157d75fbfe58fAndreas Gustafsson not created automatically in the way that IPv6 link-local addresses
6fcb2f0faad67a6d2cb2e30ec57157d75fbfe58fAndreas Gustafsson are and will not appear or be used unless they are purposely
cd63e943104ab4f7f8b37da8d49738e91a8db1ddEvan Hunt configured.
47fd46791da765e3dbedd987e9b263b3bee25986Brian Wellington
47fd46791da765e3dbedd987e9b263b3bee25986Brian Wellington In order for hosts to autoconfigure Local IPv6 addresses, routers
47fd46791da765e3dbedd987e9b263b3bee25986Brian Wellington have to be configured to advertise Local IPv6 /64 prefixes in router
47fd46791da765e3dbedd987e9b263b3bee25986Brian Wellington advertisements, or a DHCPv6 server must have been configured to
47fd46791da765e3dbedd987e9b263b3bee25986Brian Wellington assign them. In order for a node to learn the Local IPv6 address of
47fd46791da765e3dbedd987e9b263b3bee25986Brian Wellington another node, the Local IPv6 address must have been installed in a
cd63e943104ab4f7f8b37da8d49738e91a8db1ddEvan Hunt naming system (e.g., DNS, proprietary naming system, etc.) For these
cd63e943104ab4f7f8b37da8d49738e91a8db1ddEvan Hunt reasons, controlling their usage in a site is straightforward.
6fcb2f0faad67a6d2cb2e30ec57157d75fbfe58fAndreas Gustafsson
6fcb2f0faad67a6d2cb2e30ec57157d75fbfe58fAndreas Gustafsson To limit the use of Local IPv6 addresses the following guidelines
87708bde16713bc02ff2598f4a82f98c699a2f2dMark Andrews apply:
6fcb2f0faad67a6d2cb2e30ec57157d75fbfe58fAndreas Gustafsson
5ff133b82082d82f0ba89b7c999c6b62b6298e46Andreas Gustafsson - Nodes that are to only be reachable inside of a site: The local
8f3dd8f8e73e4465221a5297819db70e6b383138Mark Andrews DNS should be configured to only include the Local IPv6
6e9efadbea9febb0494e713e54dfea6f7ef70383Mark Andrews addresses of these nodes. Nodes with only Local IPv6 addresses
43fe2897fc80bbec2115310ca79d432a252f3ea4Mark Andrews must not be installed in the global DNS.
43fe2897fc80bbec2115310ca79d432a252f3ea4Mark Andrews
43fe2897fc80bbec2115310ca79d432a252f3ea4Mark Andrews - Nodes that are to be limited to only communicate with other
43fe2897fc80bbec2115310ca79d432a252f3ea4Mark Andrews nodes in the site: These nodes should be set to only
43fe2897fc80bbec2115310ca79d432a252f3ea4Mark Andrews autoconfigure Local IPv6 addresses via [ADDAUTO] or to only
43fe2897fc80bbec2115310ca79d432a252f3ea4Mark Andrews receive Local IPv6 addresses via [DHCP6]. Note: For the case
43fe2897fc80bbec2115310ca79d432a252f3ea4Mark Andrews where both global and Local IPv6 prefixes are being advertised
43fe2897fc80bbec2115310ca79d432a252f3ea4Mark Andrews on a subnet, this will require a switch in the devices to only
43fe2897fc80bbec2115310ca79d432a252f3ea4Mark Andrews autoconfigure Local IPv6 addresses.
43fe2897fc80bbec2115310ca79d432a252f3ea4Mark Andrews
43fe2897fc80bbec2115310ca79d432a252f3ea4Mark Andrews - Nodes that are to be reachable from inside of the site and from
43fe2897fc80bbec2115310ca79d432a252f3ea4Mark Andrews outside of the site: The DNS should be configured to include
43fe2897fc80bbec2115310ca79d432a252f3ea4Mark Andrews the global addresses of these nodes. The local DNS may be
43fe2897fc80bbec2115310ca79d432a252f3ea4Mark Andrews configured to also include the Local IPv6 addresses of these
43fe2897fc80bbec2115310ca79d432a252f3ea4Mark Andrews nodes.
43fe2897fc80bbec2115310ca79d432a252f3ea4Mark Andrews
43fe2897fc80bbec2115310ca79d432a252f3ea4Mark Andrews - Nodes that can communicate with other nodes inside of the site
5ff133b82082d82f0ba89b7c999c6b62b6298e46Andreas Gustafsson and outside of the site: These nodes should autoconfigure global
754cca729dd82ae8363917dc00ad44f9d900635bMark Andrews addresses via [ADDAUTO] or receive global address via [DHCP6].
754cca729dd82ae8363917dc00ad44f9d900635bMark Andrews They may also obtain Local IPv6 addresses via the same
754cca729dd82ae8363917dc00ad44f9d900635bMark Andrews mechanisms.
754cca729dd82ae8363917dc00ad44f9d900635bMark Andrews
754cca729dd82ae8363917dc00ad44f9d900635bMark Andrews4.7. Use of Local IPv6 Addresses with VPNs
754cca729dd82ae8363917dc00ad44f9d900635bMark Andrews
754cca729dd82ae8363917dc00ad44f9d900635bMark Andrews Local IPv6 addresses can be used for inter-site Virtual Private
5ff133b82082d82f0ba89b7c999c6b62b6298e46Andreas Gustafsson Networks (VPN) if appropriate routes are set up. Because the
f02c22d58ac88777655e0b407b22b07864d39184Evan Hunt addresses are unique, these VPNs will work reliably and without the
f02c22d58ac88777655e0b407b22b07864d39184Evan Hunt need for translation. They have the additional property that they
f02c22d58ac88777655e0b407b22b07864d39184Evan Hunt will continue to work if the individual sites are renumbered or
f02c22d58ac88777655e0b407b22b07864d39184Evan Hunt merged.
f02c22d58ac88777655e0b407b22b07864d39184Evan Hunt
f02c22d58ac88777655e0b407b22b07864d39184Evan Hunt
f02c22d58ac88777655e0b407b22b07864d39184Evan Hunt
f02c22d58ac88777655e0b407b22b07864d39184Evan HuntHinden & Haberman Standards Track [Page 10]
f02c22d58ac88777655e0b407b22b07864d39184Evan Hunt
f02c22d58ac88777655e0b407b22b07864d39184Evan HuntRFC 4193 Unique Local IPv6 Unicast Addresses October 2005
f02c22d58ac88777655e0b407b22b07864d39184Evan Hunt
f02c22d58ac88777655e0b407b22b07864d39184Evan Hunt
f02c22d58ac88777655e0b407b22b07864d39184Evan Hunt5. Global Routing Considerations
f02c22d58ac88777655e0b407b22b07864d39184Evan Hunt
f02c22d58ac88777655e0b407b22b07864d39184Evan Hunt Section 4.1 provides operational guidelines that forbid default
f02c22d58ac88777655e0b407b22b07864d39184Evan Hunt routing of local addresses between sites. Concerns were raised to
f02c22d58ac88777655e0b407b22b07864d39184Evan Hunt the IPv6 working group and to the IETF as a whole that sites may
f02c22d58ac88777655e0b407b22b07864d39184Evan Hunt attempt to use local addresses as globally routed provider-
f02c22d58ac88777655e0b407b22b07864d39184Evan Hunt independent addresses. This section describes why using local
debd489a44363870f96f75818e89ec27d3cab736Francis Dupont addresses as globally-routed provider-independent addresses is
debd489a44363870f96f75818e89ec27d3cab736Francis Dupont unadvisable.
debd489a44363870f96f75818e89ec27d3cab736Francis Dupont
debd489a44363870f96f75818e89ec27d3cab736Francis Dupont5.1. From the Standpoint of the Internet
debd489a44363870f96f75818e89ec27d3cab736Francis Dupont
debd489a44363870f96f75818e89ec27d3cab736Francis Dupont There is a mismatch between the structure of IPv6 local addresses and
debd489a44363870f96f75818e89ec27d3cab736Francis Dupont the normal IPv6 wide area routing model. The /48 prefix of an IPv6
debd489a44363870f96f75818e89ec27d3cab736Francis Dupont local addresses fits nowhere in the normal hierarchy of IPv6 unicast
debd489a44363870f96f75818e89ec27d3cab736Francis Dupont addresses. Normal IPv6 unicast addresses can be routed
debd489a44363870f96f75818e89ec27d3cab736Francis Dupont hierarchically down to physical subnet (link) level and only have to
339c130823ff00cdfa70d1f0a8922199aa37f33cMark Andrews be flat-routed on the physical subnet. IPv6 local addresses would
debd489a44363870f96f75818e89ec27d3cab736Francis Dupont have to be flat-routed even over the wide area Internet.
debd489a44363870f96f75818e89ec27d3cab736Francis Dupont
debd489a44363870f96f75818e89ec27d3cab736Francis Dupont Thus, packets whose destination address is an IPv6 local address
40dd9cb8cc240c33d820fe79f176ed51e4c06a1aMark Andrews could be routed over the wide area only if the corresponding /48
40dd9cb8cc240c33d820fe79f176ed51e4c06a1aMark Andrews prefix were carried by the wide area routing protocol in use, such as
40dd9cb8cc240c33d820fe79f176ed51e4c06a1aMark Andrews BGP. This contravenes the operational assumption that long prefixes
40dd9cb8cc240c33d820fe79f176ed51e4c06a1aMark Andrews will be aggregated into many fewer short prefixes, to limit the table
40dd9cb8cc240c33d820fe79f176ed51e4c06a1aMark Andrews size and convergence time of the routing protocol. If a network uses
40dd9cb8cc240c33d820fe79f176ed51e4c06a1aMark Andrews both normal IPv6 addresses [ADDARCH] and IPv6 local addresses, these
40dd9cb8cc240c33d820fe79f176ed51e4c06a1aMark Andrews types of addresses will certainly not aggregate with each other,
40dd9cb8cc240c33d820fe79f176ed51e4c06a1aMark Andrews since they differ from the most significant bit onwards. Neither
40dd9cb8cc240c33d820fe79f176ed51e4c06a1aMark Andrews will IPv6 local addresses aggregate with each other, due to their
40dd9cb8cc240c33d820fe79f176ed51e4c06a1aMark Andrews random bit patterns. This means that there would be a very
40dd9cb8cc240c33d820fe79f176ed51e4c06a1aMark Andrews significant operational penalty for attempting to use IPv6 local
40dd9cb8cc240c33d820fe79f176ed51e4c06a1aMark Andrews address prefixes generically with currently known wide area routing
40dd9cb8cc240c33d820fe79f176ed51e4c06a1aMark Andrews technology.
40dd9cb8cc240c33d820fe79f176ed51e4c06a1aMark Andrews
40dd9cb8cc240c33d820fe79f176ed51e4c06a1aMark Andrews5.2. From the Standpoint of a Site
40dd9cb8cc240c33d820fe79f176ed51e4c06a1aMark Andrews
40dd9cb8cc240c33d820fe79f176ed51e4c06a1aMark Andrews There are a number of design factors in IPv6 local addresses that
40dd9cb8cc240c33d820fe79f176ed51e4c06a1aMark Andrews reduce the likelihood that IPv6 local addresses will be used as
40dd9cb8cc240c33d820fe79f176ed51e4c06a1aMark Andrews arbitrary global unicast addresses. These include:
40dd9cb8cc240c33d820fe79f176ed51e4c06a1aMark Andrews
386d3a99c190bad55edf44d076e6bd087e230ab8Tatuya JINMEI 神明達哉 - The default rules to filter packets and routes make it very
386d3a99c190bad55edf44d076e6bd087e230ab8Tatuya JINMEI 神明達哉 difficult to use IPv6 local addresses for arbitrary use across
386d3a99c190bad55edf44d076e6bd087e230ab8Tatuya JINMEI 神明達哉 the Internet. For a site to use them as general purpose unicast
3dfa202e4fea6b985bcf8761e2d11c176baa40d1Mark Andrews addresses, it would have to make sure that the default rules
3dfa202e4fea6b985bcf8761e2d11c176baa40d1Mark Andrews were not being used by all other sites and intermediate ISPs
3dfa202e4fea6b985bcf8761e2d11c176baa40d1Mark Andrews used for their current and future communication.
3dfa202e4fea6b985bcf8761e2d11c176baa40d1Mark Andrews
386d3a99c190bad55edf44d076e6bd087e230ab8Tatuya JINMEI 神明達哉
3dfa202e4fea6b985bcf8761e2d11c176baa40d1Mark Andrews
3dfa202e4fea6b985bcf8761e2d11c176baa40d1Mark Andrews
3dfa202e4fea6b985bcf8761e2d11c176baa40d1Mark AndrewsHinden & Haberman Standards Track [Page 11]
3dfa202e4fea6b985bcf8761e2d11c176baa40d1Mark Andrews
3dfa202e4fea6b985bcf8761e2d11c176baa40d1Mark AndrewsRFC 4193 Unique Local IPv6 Unicast Addresses October 2005
3dfa202e4fea6b985bcf8761e2d11c176baa40d1Mark Andrews
3dfa202e4fea6b985bcf8761e2d11c176baa40d1Mark Andrews
3dfa202e4fea6b985bcf8761e2d11c176baa40d1Mark Andrews - They are not mathematically guaranteed to be unique and are not
3dfa202e4fea6b985bcf8761e2d11c176baa40d1Mark Andrews registered in public databases. Collisions, while highly
386d3a99c190bad55edf44d076e6bd087e230ab8Tatuya JINMEI 神明達哉 unlikely, are possible and a collision can compromise the
386d3a99c190bad55edf44d076e6bd087e230ab8Tatuya JINMEI 神明達哉 integrity of the communications. The lack of public
386d3a99c190bad55edf44d076e6bd087e230ab8Tatuya JINMEI 神明達哉 registration creates operational problems.
386d3a99c190bad55edf44d076e6bd087e230ab8Tatuya JINMEI 神明達哉
386d3a99c190bad55edf44d076e6bd087e230ab8Tatuya JINMEI 神明達哉 - The addresses are allocated randomly. If a site had multiple
386d3a99c190bad55edf44d076e6bd087e230ab8Tatuya JINMEI 神明達哉 prefixes that it wanted to be used globally, the cost of
386d3a99c190bad55edf44d076e6bd087e230ab8Tatuya JINMEI 神明達哉 advertising them would be very high because they could not be
386d3a99c190bad55edf44d076e6bd087e230ab8Tatuya JINMEI 神明達哉 aggregated.
3dfa202e4fea6b985bcf8761e2d11c176baa40d1Mark Andrews
3dfa202e4fea6b985bcf8761e2d11c176baa40d1Mark Andrews - They have a long prefix (i.e., /48) so a single local address
386d3a99c190bad55edf44d076e6bd087e230ab8Tatuya JINMEI 神明達哉 prefix doesn't provide enough address space to be used
3dfa202e4fea6b985bcf8761e2d11c176baa40d1Mark Andrews exclusively by the largest organizations.
ddb35cf2f301ae1c3fa601792034f6d349efc8c5Mark Andrews
ddb35cf2f301ae1c3fa601792034f6d349efc8c5Mark Andrews6. Advantages and Disadvantages
3dfa202e4fea6b985bcf8761e2d11c176baa40d1Mark Andrews
ddb35cf2f301ae1c3fa601792034f6d349efc8c5Mark Andrews6.1. Advantages
3dfa202e4fea6b985bcf8761e2d11c176baa40d1Mark Andrews
3dfa202e4fea6b985bcf8761e2d11c176baa40d1Mark Andrews This approach has the following advantages:
3dfa202e4fea6b985bcf8761e2d11c176baa40d1Mark Andrews
3dfa202e4fea6b985bcf8761e2d11c176baa40d1Mark Andrews - Provides Local IPv6 prefixes that can be used independently of
3dfa202e4fea6b985bcf8761e2d11c176baa40d1Mark Andrews any provider-based IPv6 unicast address allocations. This is
3dfa202e4fea6b985bcf8761e2d11c176baa40d1Mark Andrews useful for sites not always connected to the Internet or sites
3dfa202e4fea6b985bcf8761e2d11c176baa40d1Mark Andrews that wish to have a distinct prefix that can be used to localize
3dfa202e4fea6b985bcf8761e2d11c176baa40d1Mark Andrews traffic inside of the site.
3dfa202e4fea6b985bcf8761e2d11c176baa40d1Mark Andrews
3dfa202e4fea6b985bcf8761e2d11c176baa40d1Mark Andrews - Applications can treat these addresses in an identical manner as
3dfa202e4fea6b985bcf8761e2d11c176baa40d1Mark Andrews any other type of global IPv6 unicast addresses.
3dfa202e4fea6b985bcf8761e2d11c176baa40d1Mark Andrews
b123b265e3a3d9b72a14230b6517e0f6fdb5c5b5Mark Andrews - Sites can be merged without any renumbering of the Local IPv6
b123b265e3a3d9b72a14230b6517e0f6fdb5c5b5Mark Andrews addresses.
3dfa202e4fea6b985bcf8761e2d11c176baa40d1Mark Andrews
386d3a99c190bad55edf44d076e6bd087e230ab8Tatuya JINMEI 神明達哉 - Sites can change their provider-based IPv6 unicast address
ddb35cf2f301ae1c3fa601792034f6d349efc8c5Mark Andrews without disrupting any communication that uses Local IPv6
ddb35cf2f301ae1c3fa601792034f6d349efc8c5Mark Andrews addresses.
ddb35cf2f301ae1c3fa601792034f6d349efc8c5Mark Andrews
386d3a99c190bad55edf44d076e6bd087e230ab8Tatuya JINMEI 神明達哉 - Well-known prefix that allows for easy filtering at site
386d3a99c190bad55edf44d076e6bd087e230ab8Tatuya JINMEI 神明達哉 boundary.
386d3a99c190bad55edf44d076e6bd087e230ab8Tatuya JINMEI 神明達哉
386d3a99c190bad55edf44d076e6bd087e230ab8Tatuya JINMEI 神明達哉 - Can be used for inter-site VPNs.
386d3a99c190bad55edf44d076e6bd087e230ab8Tatuya JINMEI 神明達哉
386d3a99c190bad55edf44d076e6bd087e230ab8Tatuya JINMEI 神明達哉 - If accidently leaked outside of a site via routing or DNS, there
386d3a99c190bad55edf44d076e6bd087e230ab8Tatuya JINMEI 神明達哉 is no conflict with any other addresses.
386d3a99c190bad55edf44d076e6bd087e230ab8Tatuya JINMEI 神明達哉
386d3a99c190bad55edf44d076e6bd087e230ab8Tatuya JINMEI 神明達哉
3dfa202e4fea6b985bcf8761e2d11c176baa40d1Mark Andrews
3dfa202e4fea6b985bcf8761e2d11c176baa40d1Mark Andrews
3dfa202e4fea6b985bcf8761e2d11c176baa40d1Mark Andrews
3dfa202e4fea6b985bcf8761e2d11c176baa40d1Mark Andrews
3dfa202e4fea6b985bcf8761e2d11c176baa40d1Mark Andrews
c0a76b3c0b42a110e14eb56103973944900400c4Mark AndrewsHinden & Haberman Standards Track [Page 12]
3dfa202e4fea6b985bcf8761e2d11c176baa40d1Mark Andrews
3dfa202e4fea6b985bcf8761e2d11c176baa40d1Mark AndrewsRFC 4193 Unique Local IPv6 Unicast Addresses October 2005
3dfa202e4fea6b985bcf8761e2d11c176baa40d1Mark Andrews
3dfa202e4fea6b985bcf8761e2d11c176baa40d1Mark Andrews
3dfa202e4fea6b985bcf8761e2d11c176baa40d1Mark Andrews6.2. Disadvantages
3dfa202e4fea6b985bcf8761e2d11c176baa40d1Mark Andrews
3dfa202e4fea6b985bcf8761e2d11c176baa40d1Mark Andrews This approach has the following disadvantages:
3dfa202e4fea6b985bcf8761e2d11c176baa40d1Mark Andrews
3dfa202e4fea6b985bcf8761e2d11c176baa40d1Mark Andrews - Not possible to route Local IPv6 prefixes on the global Internet
386d3a99c190bad55edf44d076e6bd087e230ab8Tatuya JINMEI 神明達哉 with current routing technology. Consequentially, it is
40dd9cb8cc240c33d820fe79f176ed51e4c06a1aMark Andrews necessary to have the default behavior of site border routers to
5ff133b82082d82f0ba89b7c999c6b62b6298e46Andreas Gustafsson filter these addresses.
5ff133b82082d82f0ba89b7c999c6b62b6298e46Andreas Gustafsson
5ff133b82082d82f0ba89b7c999c6b62b6298e46Andreas Gustafsson - There is a very low probability of non-unique locally assigned
5ff133b82082d82f0ba89b7c999c6b62b6298e46Andreas Gustafsson Global IDs being generated by the algorithm in Section 3.2.3.
5ff133b82082d82f0ba89b7c999c6b62b6298e46Andreas Gustafsson This risk can be ignored for all practical purposes, but it
963c48ba4d06a112c70d50328e827749e95f58dbMark Andrews leads to a theoretical risk of clashing address prefixes.
5ff133b82082d82f0ba89b7c999c6b62b6298e46Andreas Gustafsson
963c48ba4d06a112c70d50328e827749e95f58dbMark Andrews7. Security Considerations
5ff133b82082d82f0ba89b7c999c6b62b6298e46Andreas Gustafsson
5ff133b82082d82f0ba89b7c999c6b62b6298e46Andreas Gustafsson Local IPv6 addresses do not provide any inherent security to the
5ff133b82082d82f0ba89b7c999c6b62b6298e46Andreas Gustafsson nodes that use them. They may be used with filters at site
5ff133b82082d82f0ba89b7c999c6b62b6298e46Andreas Gustafsson boundaries to keep Local IPv6 traffic inside of the site, but this is
5ff133b82082d82f0ba89b7c999c6b62b6298e46Andreas Gustafsson no more or less secure than filtering any other type of global IPv6
5ff133b82082d82f0ba89b7c999c6b62b6298e46Andreas Gustafsson unicast addresses.
a1898260ad19d02e88ab76c1855d33c67add9defMark Andrews
5ff133b82082d82f0ba89b7c999c6b62b6298e46Andreas Gustafsson Local IPv6 addresses do allow for address-based security mechanisms,
289ae548d52bc8f982d9823af64cafda7bd92232Mark Andrews including IPsec, across end to end VPN connections.
5ff133b82082d82f0ba89b7c999c6b62b6298e46Andreas Gustafsson
5ff133b82082d82f0ba89b7c999c6b62b6298e46Andreas Gustafsson8. IANA Considerations
5ff133b82082d82f0ba89b7c999c6b62b6298e46Andreas Gustafsson
5ff133b82082d82f0ba89b7c999c6b62b6298e46Andreas Gustafsson The IANA has assigned the FC00::/7 prefix to "Unique Local Unicast".
5ff133b82082d82f0ba89b7c999c6b62b6298e46Andreas Gustafsson
5ff133b82082d82f0ba89b7c999c6b62b6298e46Andreas Gustafsson9. References
5ff133b82082d82f0ba89b7c999c6b62b6298e46Andreas Gustafsson
5ff133b82082d82f0ba89b7c999c6b62b6298e46Andreas Gustafsson9.1. Normative References
5ff133b82082d82f0ba89b7c999c6b62b6298e46Andreas Gustafsson
a1898260ad19d02e88ab76c1855d33c67add9defMark Andrews [ADDARCH] Hinden, R. and S. Deering, "Internet Protocol Version 6
5ff133b82082d82f0ba89b7c999c6b62b6298e46Andreas Gustafsson (IPv6) Addressing Architecture", RFC 3513, April 2003.
289ae548d52bc8f982d9823af64cafda7bd92232Mark Andrews
5ff133b82082d82f0ba89b7c999c6b62b6298e46Andreas Gustafsson [FIPS] "Federal Information Processing Standards Publication",
5ff133b82082d82f0ba89b7c999c6b62b6298e46Andreas Gustafsson (FIPS PUB) 180-1, Secure Hash Standard, 17 April 1995.
5ff133b82082d82f0ba89b7c999c6b62b6298e46Andreas Gustafsson
5ff133b82082d82f0ba89b7c999c6b62b6298e46Andreas Gustafsson [GLOBAL] Hinden, R., Deering, S., and E. Nordmark, "IPv6 Global
5ff133b82082d82f0ba89b7c999c6b62b6298e46Andreas Gustafsson Unicast Address Format", RFC 3587, August 2003.
5ff133b82082d82f0ba89b7c999c6b62b6298e46Andreas Gustafsson
5ff133b82082d82f0ba89b7c999c6b62b6298e46Andreas Gustafsson [ICMPV6] Conta, A. and S. Deering, "Internet Control Message
5ff133b82082d82f0ba89b7c999c6b62b6298e46Andreas Gustafsson Protocol (ICMPv6) for the Internet Protocol Version 6
5ff133b82082d82f0ba89b7c999c6b62b6298e46Andreas Gustafsson (IPv6) Specification", RFC 2463, December 1998.
5ff133b82082d82f0ba89b7c999c6b62b6298e46Andreas Gustafsson
5ff133b82082d82f0ba89b7c999c6b62b6298e46Andreas Gustafsson
90407942d3afe50f04ccea361de3b164a5a1702dMichael Graff
90407942d3afe50f04ccea361de3b164a5a1702dMichael Graff
90407942d3afe50f04ccea361de3b164a5a1702dMichael Graff
90407942d3afe50f04ccea361de3b164a5a1702dMichael Graff
90407942d3afe50f04ccea361de3b164a5a1702dMichael GraffHinden & Haberman Standards Track [Page 13]
13faa8b6a2d0d45e0659049983928366252ab3faMichael Graff
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan HuntRFC 4193 Unique Local IPv6 Unicast Addresses October 2005
13faa8b6a2d0d45e0659049983928366252ab3faMichael Graff
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt [IPV6] Deering, S. and R. Hinden, "Internet Protocol, Version 6
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt (IPv6) Specification", RFC 2460, December 1998.
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt [NTP] Mills, D., "Network Time Protocol (Version 3)
13faa8b6a2d0d45e0659049983928366252ab3faMichael Graff Specification, Implementation and Analysis", RFC 1305,
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt March 1992.
a53259c4cc558f86dd008eccc60cc89b6734a03cMark Andrews
d0803df3310ad09447c34b972e7594d576f5cbb5Evan Hunt [RANDOM] Eastlake, D., 3rd, Schiller, J., and S. Crocker,
a53259c4cc558f86dd008eccc60cc89b6734a03cMark Andrews "Randomness Requirements for Security", BCP 106, RFC 4086,
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt June 2005.
a53259c4cc558f86dd008eccc60cc89b6734a03cMark Andrews
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
a53259c4cc558f86dd008eccc60cc89b6734a03cMark Andrews Requirement Levels", BCP 14, RFC 2119, March 1997.
a53259c4cc558f86dd008eccc60cc89b6734a03cMark Andrews
a53259c4cc558f86dd008eccc60cc89b6734a03cMark Andrews [SHA1] Eastlake 3rd, D. and P. Jones, "US Secure Hash Algorithm 1
a53259c4cc558f86dd008eccc60cc89b6734a03cMark Andrews (SHA1)", RFC 3174, September 2001.
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt9.2. Informative References
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt [ADDAUTO] Thomson, S. and T. Narten, "IPv6 Stateless Address
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt Autoconfiguration", RFC 2462, December 1998.
a53259c4cc558f86dd008eccc60cc89b6734a03cMark Andrews
5f9e583552f53de12062bfff12e47250abce378fBrian Wellington [ADDSEL] Draves, R., "Default Address Selection for Internet
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt Protocol version 6 (IPv6)", RFC 3484, February 2003.
c5826852e6c789f59b301f8197e65a1dd4e09a44Mark Andrews
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt [DHCP6] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., and
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt M. Carney, "Dynamic Host Configuration Protocol for IPv6
568de8123acb1a94e2d7bfe9cc5eb5d099f6c1f5Mark Andrews (DHCPv6)", RFC 3315, July 2003.
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt [POPUL] Population Reference Bureau, "World Population Data Sheet
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt of the Population Reference Bureau 2002", August 2002.
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt
c5826852e6c789f59b301f8197e65a1dd4e09a44Mark Andrews [RTP] Schulzrinne, H., Casner, S., Frederick, R., and V.
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt Jacobson, "RTP: A Transport Protocol for Real-Time
d7729155dff87d3c7a2b9103bf6e5164ea4d7dd7Mark Andrews Applications", STD 64, RFC 3550, July 2003.
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt
c5826852e6c789f59b301f8197e65a1dd4e09a44Mark Andrews
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt
bb70b45c1f3869ec81678fc857e3dfad60da5de4Evan Hunt
bb70b45c1f3869ec81678fc857e3dfad60da5de4Evan Hunt
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt
d7729155dff87d3c7a2b9103bf6e5164ea4d7dd7Mark Andrews
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan HuntHinden & Haberman Standards Track [Page 14]
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt
5989aea4bbe79e09290792f04aeb557e2b2da02eAndreas GustafssonRFC 4193 Unique Local IPv6 Unicast Addresses October 2005
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan HuntAuthors' Addresses
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt Robert M. Hinden
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt Nokia
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt 313 Fairchild Drive
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt Mountain View, CA 94043
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt USA
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt Phone: +1 650 625-2004
d7729155dff87d3c7a2b9103bf6e5164ea4d7dd7Mark Andrews EMail: bob.hinden@nokia.com
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt Brian Haberman
d73de275987d29627dc11d5bd4a22874a29f7874Mark Andrews Johns Hopkins University
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt Applied Physics Lab
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt 11100 Johns Hopkins Road
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt Laurel, MD 20723
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt USA
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt Phone: +1 443 778 1319
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt EMail: brian@innovationslab.net
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt
d7729155dff87d3c7a2b9103bf6e5164ea4d7dd7Mark Andrews
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt
d7729155dff87d3c7a2b9103bf6e5164ea4d7dd7Mark Andrews
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt
d73de275987d29627dc11d5bd4a22874a29f7874Mark Andrews
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt
fda0a038810529d6e45b17822ddcc61d82964e83Mark Andrews
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt
fda0a038810529d6e45b17822ddcc61d82964e83Mark Andrews
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt
c2a6e9d347ea5364041d4241e4683d076d4e091bMark Andrews
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt
aaaf8d4f4873d21e55c3ffb4f656203d08339865Mark Andrews
c2a6e9d347ea5364041d4241e4683d076d4e091bMark Andrews
c2a6e9d347ea5364041d4241e4683d076d4e091bMark Andrews
c2a6e9d347ea5364041d4241e4683d076d4e091bMark Andrews
c2a6e9d347ea5364041d4241e4683d076d4e091bMark Andrews
c2a6e9d347ea5364041d4241e4683d076d4e091bMark Andrews
c2a6e9d347ea5364041d4241e4683d076d4e091bMark Andrews
c2a6e9d347ea5364041d4241e4683d076d4e091bMark Andrews
c2a6e9d347ea5364041d4241e4683d076d4e091bMark Andrews
c2a6e9d347ea5364041d4241e4683d076d4e091bMark Andrews
c2a6e9d347ea5364041d4241e4683d076d4e091bMark Andrews
c2a6e9d347ea5364041d4241e4683d076d4e091bMark AndrewsHinden & Haberman Standards Track [Page 15]
c2a6e9d347ea5364041d4241e4683d076d4e091bMark Andrews
c2a6e9d347ea5364041d4241e4683d076d4e091bMark AndrewsRFC 4193 Unique Local IPv6 Unicast Addresses October 2005
c2a6e9d347ea5364041d4241e4683d076d4e091bMark Andrews
c2a6e9d347ea5364041d4241e4683d076d4e091bMark Andrews
c2a6e9d347ea5364041d4241e4683d076d4e091bMark AndrewsFull Copyright Statement
c2a6e9d347ea5364041d4241e4683d076d4e091bMark Andrews
c2a6e9d347ea5364041d4241e4683d076d4e091bMark Andrews Copyright (C) The Internet Society (2005).
c2a6e9d347ea5364041d4241e4683d076d4e091bMark Andrews
c2a6e9d347ea5364041d4241e4683d076d4e091bMark Andrews This document is subject to the rights, licenses and restrictions
c2a6e9d347ea5364041d4241e4683d076d4e091bMark Andrews contained in BCP 78, and except as set forth therein, the authors
c2a6e9d347ea5364041d4241e4683d076d4e091bMark Andrews retain all their rights.
c2a6e9d347ea5364041d4241e4683d076d4e091bMark Andrews
c2a6e9d347ea5364041d4241e4683d076d4e091bMark Andrews This document and the information contained herein are provided on an
c2a6e9d347ea5364041d4241e4683d076d4e091bMark Andrews "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
c2a6e9d347ea5364041d4241e4683d076d4e091bMark Andrews OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
c2a6e9d347ea5364041d4241e4683d076d4e091bMark Andrews ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
c2a6e9d347ea5364041d4241e4683d076d4e091bMark Andrews INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
c2a6e9d347ea5364041d4241e4683d076d4e091bMark Andrews INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
c2a6e9d347ea5364041d4241e4683d076d4e091bMark Andrews WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
c2a6e9d347ea5364041d4241e4683d076d4e091bMark Andrews
c2a6e9d347ea5364041d4241e4683d076d4e091bMark AndrewsIntellectual Property
c2a6e9d347ea5364041d4241e4683d076d4e091bMark Andrews
c2a6e9d347ea5364041d4241e4683d076d4e091bMark Andrews The IETF takes no position regarding the validity or scope of any
c2a6e9d347ea5364041d4241e4683d076d4e091bMark Andrews Intellectual Property Rights or other rights that might be claimed to
c2a6e9d347ea5364041d4241e4683d076d4e091bMark Andrews pertain to the implementation or use of the technology described in
c2a6e9d347ea5364041d4241e4683d076d4e091bMark Andrews this document or the extent to which any license under such rights
c2a6e9d347ea5364041d4241e4683d076d4e091bMark Andrews might or might not be available; nor does it represent that it has
c2a6e9d347ea5364041d4241e4683d076d4e091bMark Andrews made any independent effort to identify any such rights. Information
c2a6e9d347ea5364041d4241e4683d076d4e091bMark Andrews on the procedures with respect to rights in RFC documents can be
c2a6e9d347ea5364041d4241e4683d076d4e091bMark Andrews found in BCP 78 and BCP 79.
c2a6e9d347ea5364041d4241e4683d076d4e091bMark Andrews
c2a6e9d347ea5364041d4241e4683d076d4e091bMark Andrews Copies of IPR disclosures made to the IETF Secretariat and any
c2a6e9d347ea5364041d4241e4683d076d4e091bMark Andrews assurances of licenses to be made available, or the result of an
c2a6e9d347ea5364041d4241e4683d076d4e091bMark Andrews attempt made to obtain a general license or permission for the use of
c2a6e9d347ea5364041d4241e4683d076d4e091bMark Andrews such proprietary rights by implementers or users of this
c2a6e9d347ea5364041d4241e4683d076d4e091bMark Andrews specification can be obtained from the IETF on-line IPR repository at
c2a6e9d347ea5364041d4241e4683d076d4e091bMark Andrews http://www.ietf.org/ipr.
c2a6e9d347ea5364041d4241e4683d076d4e091bMark Andrews
c2a6e9d347ea5364041d4241e4683d076d4e091bMark Andrews The IETF invites any interested party to bring to its attention any
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt copyrights, patents or patent applications, or other proprietary
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt rights that may cover technology that may be required to implement
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt this standard. Please address the information to the IETF at ietf-
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt ipr@ietf.org.
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan HuntAcknowledgement
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt Funding for the RFC Editor function is currently provided by the
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt Internet Society.
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan HuntHinden & Haberman Standards Track [Page 16]
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt
ba751492fcc4f161a18b983d4f018a1a52938cb9Evan Hunt