INTERNET-DRAFT S. Deering, Xerox PARC March 1, 1996 R. Hinden, Ipsilon Networks IPv6 Metro Addressing [Author's notes are enclosed in square brackets.] Status of this Memo This document is an Internet Draft. Internet Drafts are working documents of the Internet Engineering Task Force (IETF), its Areas, and its Working Groups. Note that other groups may also distribute working documents as Internet Drafts. Internet Drafts are draft documents valid for a maximum of six months. Internet Drafts may be updated, replaced, or obsoleted by other documents at any time. It is not appropriate to use Internet Drafts as reference material or to cite them other than as a ``working draft'' or ``work in progress.'' Please check the 1id-abstracts.txt listing contained in the internet- drafts Shadow Directories on nic.ddn.mil, nnsc.nsf.net, nic.nordu.net, ftp.nisc.sri.com, or munnari.oz.au to learn the current status of any Internet Draft. 1 Introduction We propose a scheme for allocating IPv6 Geographic Addresses for use in the Internet, as an alternative to the scheme recommended in [PROV]. This scheme is consistant with the IPv6 Addressing Architecture [ARCH] and uses the "100" Format Prefix. The essence of our scheme is that the IPv6 addresses allocated to a particular ``leaf'' routing domain, such as a campus, a corporate site, or a personal residence, have a prefix which identifies the country and city in or near which the leaf domain attaches to a transit routing domain, such as a regional or wide-area network. Such IPv6 addresses are similar to plain old telephone numbers, which start with country and city codes (or ``area codes'' in North America; we forgo the draft-deering-ipv6-metro-addr-00.txt [Page 1] INTERNET-DRAFT IPv6 Metro Addressing March 1, 1996 ``area'' terminology to avoid confusion with the previous use of that word). Unlike the current practice in the telephone system, however, we allow more than one ``carrier'' to offer transit delivery service into, out of, and within the geographic scope of a single city code. IPv6 addresses based on city codes identify where leaf domains obtain their transit service; they do not identify the carriers providing the service. The city code scheme achieves the same goal as [PROV]: it eliminates the need for wide-area routing domains, such as national and international backbones, to maintain and distribute routing information about large numbers of leaf domains. Wide-area routing is based simply on country and city codes. The main advantage of the city code scheme over [PROV] is that a leaf domain may be switched from one transit provider to another, or may be attached to a transit provider for the first time, without changing its IPv6 Addresses (provided that the new attachment point is within the geographic scope of the same city code). This is not true of the [PROV] scheme, since it requires that most leaf domains acquire their IPv6 Addresses out of a block belonging to currently- attached transit provider. Thus, using city codes, a leaf domain is not ``locked-in'' to its current transit provider; it can be switched to whichever provider offers the most desirable service without the burden of reconfiguring all internal hosts and routers (only part of which might yield to automated procedures) and without a lengthy transition period during which two providers may have to be paid. City codes also handle some ``multi-homed'' leaf domains, that is, leaf domains attached to more than one public transit service, more gracefully than the [PROV] approach. 2 Proposed IPv6 Address Structure We propose that IPv6 Addresses for a leaf domain be structured as follows:

where: is a numeric code identifying the country in which the leaf domain attaches to a transit service. It is not strictly necessary that country codes be one-to-one with countries. A single code may identify a contiguous set of countries (perhaps arising from the break-up of a larger country, like the U.S.S.R. or Canada). A draft-deering-ipv6-metro-addr-00.txt [Page 2] INTERNET-DRAFT IPv6 Metro Addressing March 1, 1996 single country may also have more than one country code (perhaps arising from the merger of several independent countries, like East and West Germany, or the wider European Community). And a country code may be assigned to a non-country, like Antarctica or the Moon. is a numeric code identifying the geographical region within a country, typically centered on a major metropolitan area (unless it happens to be Antarctica or the Moon!), in which the leaf domain attaches to a transit service. A country would not be expected to have more than a couple hundred metro codes. Unlike telephone area codes, a single large metro would not be partitioned into multiple, non-overlapping metro codes, although it would be permissible for two metro codes to overlap, geographically. is a numeric code identifying the particular leaf site within the metro of the attachment point. Every leaf site in a metro has a unique site ID, independent of the transit provider. Strategies for allocating site IDs are discussed below. is the part of the IPv6 Address upon which the leaf site performs its internal routing. In most cases this would consist of an and an . These components are encoded in an IPv6 address in the following manner. | 3 | 5 | 16-bits | 24-bits | 80-bits | +---+----+----------------+-------------+-----------------------+ |100|rsvd| Country/ Metro | Site | Intra-Site | | | | Code / ID | ID | | +---+----+----------------+-------------+-----------------------+ The "rsvd" field is reserved for future use. The Country-Code and Metro-ID use a total of 16-bits. The division between the two components is variable. Sample assignments for the country-code for countries can be found in Appendix A. Metro-ID's for Canada are in Appendix B. Metro-ID's for the United States of America are in Appendix C. draft-deering-ipv6-metro-addr-00.txt [Page 3] INTERNET-DRAFT IPv6 Metro Addressing March 1, 1996 3 Routing through Transit Domains We first consider the case of ``public'' transit routing domains that offer to deliver packets anywhere in the ``global internet''. Such routing domains do not themselves reach everywhere---they may span only a single metropolitan area or multiple cities, in one country or in multiple countries---but through bilateral and multilateral agreements with other transit domains (such as national and international backbones and various regional and metropolitan networks), they are able to offer universal delivery service. It is this set of interconnected, public transit domains that may be said to define the ``global internet''. Under the metro code scheme, each router in such a transit domain must maintain routing table entries to enable it to reach any metro in the global internet. Those entries may consist of interior routes to cities or countries directly reachable within the domain, obtained through the operation of a conventional intra-domain routing protocol, and exterior routes to specific cities, to specific countries (with the metro unspecified), and to ``default'' countries, injected at the domain's boundary routers by static configuration or an inter-domain routing protocol. The number of such inter-metro route entries in any one router is expected to be manageably small. For a single-metro regional, it may be just a single ``default'' entry, pointing to a wide-area backbone. For a larger regional, there will be entries for each of the cities served by that regional, plus zero or more country routes, plus a default. National backbones will probably have routes to all cities within one country, and international backbones will probably have routes to all countries. If by nothing else, the number of such entries is bounded by the total number of cities in the world. [I wonder how many there are?] A packet is routed towards its destination metro via the inter-metro route entries, using the conventional ``longest-match'' algorithm to choose a metro-specific route over a country-only route. Once the packet reaches a router in the destination metro, further routing is done using the site ID field. The router at which the packet arrives in the destination metro may or may not belong to a transit domain that is directly serving the destination leaf site. If it does, it will have a internal route for the given site ID. If it does not, the router must have some other information that will allow it to forward the packet to a transit domain that does directly serve the destination. [Here's comes the interesting bit, at last. Hope it makes sense.] draft-deering-ipv6-metro-addr-00.txt [Page 4] INTERNET-DRAFT IPv6 Metro Addressing March 1, 1996 In order for a packet to get shuttled to the right transit domain in the destination metro, all of the domains serving a single metro must be connected to each other, either directly or indirectly (through some other transit service), and they must exchange information about which transit domains serve which leaf domains. The simplest way to exchange that information is simply to have each transit domain export all of its leaf domain routes to all of the other transitdomains serving the same metro; that should suffice for cities with only a few hundred leaf sites. However, we may expect the number of leaf sites in a metro eventually to grow into the millions (when, someday, every telephone is replaced by a router). For large numbers of leaf sites, more efficient information exchange is possible: once a day, say, each transit site could simply send a list of all of the leaf site IDs it serves to each of its neighboring domains. The routers would then concatenate the lists from all of the domains, and use the resulting list as an indirection table for routing packets within the metro: the site ID of a packet's destination would first be looked up in the indirection table to find out who serves that ID, and then the routing table would be consulted to determine how to reach the serving domain. If the memory cost of storing the indirection table becomes prohibitive, it could reasonably be stored on disk, with only the recently-referenced site IDs being cached in memory. (The once a day exchange rate implies that it would take at most one day for a leaf site to start receiving service from a new transit domain.) The storage required for the list of site IDs could be further reduced by imposing some sub-structure on site IDs, assuming that most leaf sites will not, in fact, ever switch from their initial transit domain to some other transit domain. If that should be the case, then it would be reasonable to hand out blocks of site IDs to each transit domain serving a metro, structured as follows: where identifies the transit domain within the metro, and is simply incremented each time a new leaf site ID is to be assigned by that transit domain. A leaf site would obtain a site ID of that form from the first transit domain to which it connected. If the leaf domain later switched to another transit, it would still keep the same site ID, but it would report that ID to its new transit domain. Then, each transit site would only have to inform its neighbors of these ``exceptions'' (i.e., leaf sites whose site ID's field did not match their current transit provider), rather than complete lists of all served leaf sites. For ``semi-private'' transit domains, such as wide-area networks constrained to serving a limited clientele, routing could be draft-deering-ipv6-metro-addr-00.txt [Page 5] INTERNET-DRAFT IPv6 Metro Addressing March 1, 1996 performed on full

prefixes, treating them as a flat field. Alternatively, a semi-private domain could take advantage of the metro code structure to achieve the same scalability benefits as the public transit domains. The only difference would be that, in the semi-private case, if a packet arrives in its destination metro and the router there does not have an interior route to the destination leaf site, the router would simply drop the packet, it being addressed to an unauthorized destination. 4 Routing in Leaf Sites Within a leaf site, routing is normally performed using the IPv6 Address fields that follow the site ID. If a leaf site attaches to more than one transit domain in the same metro, it need not obtain multiple IPv6 Address allocations; packets with the same destination IPv6 Address may arrive via any of the attached transit domains. (The leaf site may control which transit domain it uses for outgoing traffic, based on the source and destination addresses of the traffic, quality-of-service fields, time-of-day, or any other information at hand, similar to the way modern office PBX systems select carriers for off-site calls. The choice of transit domain for incoming traffic, however, is under the control of the source leaf site and all of the intermediate transit domains. [Should I mention the possibility of explicitly allocating multiple IPv6 Address blocks with different site IDs for a multi-home site, in order to control incoming traffic via the addresses that are handed out to communicants?]). A leaf site may itself span multiple cities, or multiple countries. An example is a large private corporate internet interconnecting many branch offices. If such a site attached to the ``public'' internet in only one place, the IPv6 Addresses for all of the company's systems (or at least all systems with external access privileges) would contain the metro code for the attachment point, regardless of where the systems themselves were located. If the corporate site were attached to the public internet in more than one place, it would be reasonable for the systems inside the corporation to take their IPv6 Addresses from their nearest point of attachment, as discussed in [PROV]. This would mean the use of multiple IPv6 Address prefixes (country, metro, and site IDs) within the single corporate site. The intra-domain routing protocol could be configured to know about the specific prefixes belonging to the company, in order to keep intra- company traffic inside the corporate internet. The country and metro structure of those IPv6 Addresses could be exploited for their scalability benefits by the corporate routers. draft-deering-ipv6-metro-addr-00.txt [Page 6] INTERNET-DRAFT IPv6 Metro Addressing March 1, 1996 Alternatively, the company could use an entirely separate IPv6 Address address space for its systems, in addition to the IPv6 Addresses obtained from any public attachment points, similar to the way telephones in some large corporations may be ``addressed'' by both a normal, public phone number, and a number belonging to the corporation's own private phone system. One advantage of assigning both interior and exterior addresses to the company's systems might to allow the exterior addresses and public connectivity to be used for intra-company communication if the corporate internet should partition. 5 When IPv6 Addresses Change Under the metro code scheme, there are still occasions when it is necessary for a leaf site to change some or all of its IPv6 Addresses. For example, if a small company moves to a new metro and attaches its routing domain there, that site will have to use new IPv6 Addresses. However, such moves also entail changes of phone numbers, fax numbers, postal addresses, etc., so the change of IPv6 Addresses would not be unexpected or unreasonable. If a company with a wide-area private internet adds a new attachment point to the public internet, it is necessary to assign new IPv6 Addresses to some of the company's systems if it is desired that those systems receive packets via the new attachment point. However, the new addresses may be introduced gradually, and use of the old addresses may be allowed to continue for an indefinite transition period. Finally, if the country or metro code of an attachment point should happen to change, say, by annexation of the metro by a hostile neighboring country, leaf site IPv6 Addresses would have to change. IPv6 automatic address reassignment [AUTO] could be used to handle this renumbering. [Should add some discussion of ``800 numbers'', mobile hosts, and multicast. Nothing surprising.] draft-deering-ipv6-metro-addr-00.txt [Page 7] INTERNET-DRAFT IPv6 Metro Addressing March 1, 1996 Appendix A - Country Codes Country or Pop. (millions) max Code (binary) Code (hex) Territory 1992 2025 metros --------------------------------------------------------------------------- China 1,165.8 1,590.8 511 0001 000. .... .... 10xx and 11xx India 882.6 1,383.1 511 0001 001. .... .... 12xx and 13xx United States 255.6 327.5 511 0001 010. .... .... 14xx and 15xx Pakistan 121.7 281.4 511 0001 011. .... .... 16xx and 17xx Indonesia 184.5 278.2 511 0001 100. .... .... 18xx and 19xx Brazil 156.3 237.2 511 0001 101. .... .... 1Axx and 1Bxx Nigeria 90.1 216.2 511 0001 110. .... .... 1Cxx and 1Dxx Russian Fed. 149.3 170.7 511 0001 111. .... .... 1Exx and 1Fxx Bangladesh 111.4 211.6 255 0010 0000 .... .... 20xx Iran 59.7 159.2 255 0010 0001 .... .... 21xx Mexico 87.7 143.3 255 0010 0010 .... .... 22xx Ethiopia 54.3 140.2 255 0010 0011 .... .... 23xx Japan 124.4 127.5 255 0010 0100 .... .... 24xx Vietnam 69.2 108.2 255 0010 0101 .... .... 25xx Egypt 57.8 103.1 255 0010 0110 .... .... 26xx Philippines 63.7 100.8 255 0010 0111 .... .... 27xx Zaire 37.9 98.2 127 0010 1000 0... .... 280x to 287x Turkey 59.2 98.1 127 0010 1000 1... .... 288x to 28Fx South Africa 41.7 92.0 127 0010 1001 0... .... 290x to 297x Tanzania 27.4 77.9 127 0010 1001 1... .... 298x to 29Fx Thailand 56.3 76.4 127 0010 1010 0... .... 2A0x to 2A7x Germany 80.6 73.7 127 0010 1010 1... .... 2A8x to 2AFx Myanmar 42.5 69.9 127 0010 1011 0... .... 2B0x to 2B7x Kenya 26.2 62.3 127 0010 1011 1... .... 2B8x to 2BFx United Kingdom 57.8 61.0 127 0010 1100 0... .... 2C0x to 2C7x France 56.9 58.6 127 0010 1100 1... .... 2C8x to 2CFx Sudan 26.5 57.3 127 0010 1101 0... .... 2D0x to 2D7x Korea, South 44.3 54.8 127 0010 1101 1... .... 2D8x to 2DFx Columbia 34.3 54.2 127 0010 1110 0... .... 2E0x to 2E7x Ukraine 52.1 52.9 127 0010 1110 1... .... 2E8x to 2EFx Italy 58.0 51.9 127 0010 1111 0... .... 2F0x to 2F7x Iraq 18.2 51.9 127 0010 1111 1... .... 2F8x to 2FFx Uganda 17.5 49.6 63 0011 0000 00.. .... 300x to 303x Afganistan 16.9 48.5 63 0011 0000 01.. .... 304x to 307x Algeria 26.0 47.1 63 0011 0000 10.. .... 308x to 30Bx Saudi Arabia 16.1 47.1 63 0011 0000 11.. .... 30Cx to 30Fx Argentina 33.1 45.5 63 0011 0001 00.. .... 310x to 313x Morocco 26.2 43.9 63 0011 0001 01.. .... 314x to 317x Uzbekistan 21.3 43.1 63 0011 0001 10.. .... 318x to 31Bx Poland 38.4 42.7 63 0011 0001 11.. .... 31Cx to 31Fx draft-deering-ipv6-metro-addr-00.txt [Page 8] INTERNET-DRAFT IPv6 Metro Addressing March 1, 1996 Nepal 19.9 40.8 63 0011 0010 00.. .... 320x to 323x Spain 39.3 39.3 63 0011 0010 01.. .... 324x to 327x Cote d'Ivoire 13.0 39.3 63 0011 0010 10.. .... 328x to 32Bx Syria 13.7 38.7 63 0011 0010 11.. .... 32Cx to 32Fx Peru 22.5 37.4 63 0011 0011 00.. .... 330x to 333x Mozambique 16.6 35.6 63 0011 0011 01.. .... 334x to 337x Canada 27.4 35.0 63 0011 0011 10.. .... 338x to 33Bx Australia 17.8 23.9 63 0011 0011 11.. .... 33Cx to 33Fx Cameroon 12.7 36.3 31 0011 0100 000. .... 340x and 341x Ghana 16.0 35.4 31 0011 0100 001. .... 342x and 343x Malaysia 18.7 34.9 31 0011 0100 010. .... 344x and 345x Venezuala 18.9 34.6 31 0011 0100 011. .... 346x and 347x Korea, North 22.2 32.1 31 0011 0100 100. .... 348x and 349x Madagascar 11.9 31.7 31 0011 0100 101. .... 34Ax and 34Bx Yemen 10.4 29.9 31 0011 0100 110. .... 34Cx and 34Dx Kazakhstan 16.9 26.8 31 0011 0100 111. .... 34Ex and 34Fx Zambia 8.4 26.3 31 0011 0101 000. .... 350x and 351x Romania 22.7 25.7 31 0011 0101 001. .... 352x and 353x Taiwan 20.8 25.4 31 0011 0101 010. .... 354x and 355x Mali 8.5 24.8 31 0011 0101 011. .... 356x and 357x Angola 8.9 24.7 31 0011 0101 100. .... 358x and 359x Malawi 8.7 24.7 31 0011 0101 101. .... 35Ax and 35Bx Sri Lanka 17.6 24.0 31 0011 0101 110. .... 35Cx and 35Dx Burkina Faso 9.6 23.7 31 0011 0101 111. .... 35Ex and 35Fx Zimbabwe 10.3 22.6 31 0011 0110 000. .... 360x and 361x Guatemala 9.7 21.7 31 0011 0110 001. .... 362x and 363x Niger 8.3 21.5 31 0011 0110 010. .... 364x and 365x Chile 13.6 19.8 31 0011 0110 011. .... 366x and 367x Rwanda 7.7 18.8 31 0011 0110 100. .... 368x and 369x Somalia 8.3 18.7 31 0011 0110 101. .... 36Ax and 36Bx Bolivia 7.8 18.3 31 0011 0110 110. .... 36Cx and 36Dx Ecuador 10.3 17.9 31 0011 0110 111. .... 36Ex and 36Fx Czechoslovakia 15.7 17.2 31 0011 0111 000. .... 370x and 371x Senegal 7.9 17.0 31 0011 0111 001. .... 372x and 373x Netherlands 15.3 16.7 31 0011 0111 010. .... 374x and 375x (Unassigned) 0011 0111 011. .... 376x and 377x (Unassigned) 0011 0111 100. .... 378x and 379x (Unassigned) 0011 0111 101. .... 37Ax and 37Bx (Unassigned) 0011 0111 110. .... 37Cx and 37Dx (Unassigned) 0011 0111 111. .... 37Ex and 37Fx Guinea 7.8 15.3 15 0011 1000 0000 .... 380x Cambodia 9.1 14.0 15 0011 1000 0001 .... 381x Azerbaijan 7.1 14.0e 15 0011 1000 0010 .... 382x Tunisia 8.4 13.6 15 0011 1000 0011 .... 383x Haiti 6.4 13.2 15 0011 1000 0100 .... 384x Chad 5.2 13.2 15 0011 1000 0101 .... 385x draft-deering-ipv6-metro-addr-00.txt [Page 9] INTERNET-DRAFT IPv6 Metro Addressing March 1, 1996 Burundi 5.8 13.0 15 0011 1000 0110 .... 386x Cuba 10.8 12.9 15 0011 1000 0111 .... 387x Benin 5.0 12.6 15 0011 1000 1000 .... 388x Belarus 10.3 11.5 15 0011 1000 1001 .... 389x Honduras 5.5 11.5 15 0011 1000 1010 .... 38Ax Dominican Republic 7.5 11.4 15 0011 1000 1011 .... 38Bx El Salvador 5.6 11.3 15 0011 1000 1100 .... 38Cx Yugoslavia 10.0 11.0 15 0011 1000 1101 .... 38Dx Portugal 10.5 10.5 15 0011 1000 1110 .... 38Ex Hungary 10.3 10.4 15 0011 1000 1111 .... 38Fx Greece 10.3 10.0 15 0011 1001 0000 .... 390x Tajikistan 5.5 10.0e 15 0011 1001 0001 .... 391x Sierra Leone 4.4 10.0 15 0011 1001 0010 .... 392x Togo 3.8 9.9 15 0011 1001 0011 .... 393x Jordan 3.6 9.9 15 0011 1001 0100 .... 394x Belgium 10.0 9.3 15 0011 1001 0101 .... 395x Paraguay 4.5 9.2 15 0011 1001 0110 .... 396x Nicaragua 4.1 9.2 15 0011 1001 0111 .... 397x Kyrgyzstan 4.5 9.0e 15 0011 1001 1000 .... 398x Bulgaria 8.9 8.9 15 0011 1001 1001 .... 399x Sweden 8.7 8.6 15 0011 1001 1010 .... 39Ax Laos 4.4 8.6 15 0011 1001 1011 .... 39Bx (Unassigned) 0011 1001 1100 .... 39Cx (Unassigned) 0011 1001 1101 .... 39Dx (Unassigned) 0011 1001 1110 .... 39Ex (Unassigned) 0011 1001 1111 .... 39Fx Croatia 4.6 8.0e 7 0011 1010 0000 0... 3A00 to 3A07 Bosnia-Herzegovina 4.2 8.0e 7 0011 1010 0000 1... 3A08 to 3A0F Turkmenistan 3.9 8.0e 7 0011 1010 0001 0... 3A10 to 3A17 Central African Rep 3.2 7.9 7 0011 1010 0001 1... 3A18 to 3A1F Austria 7.9 7.3 7 0011 1010 0010 0... 3A20 to 3A27 Papua New Guinea 3.9 7.3 7 0011 1010 0010 1... 3A28 to 3A2F Liberia 2.8 7.2 7 0011 1010 0011 0... 3A30 to 3A37 Georgia 5.5 7.0e 7 0011 1010 0011 1... 3A38 to 3A3F Armenia 3.5 7.0e 7 0011 1010 0100 0... 3A40 to 3A47 Transkei (SA) 3.4 7.0e 7 0011 1010 0100 1... 3A48 to 3A4F Isreal 5.2 6.9 7 0011 1010 0101 0... 3A50 to 3A57 Switzerland 6.9 6.8 7 0011 1010 0101 1... 3A58 to 3A5F Congo 2.4 6.6 7 0011 1010 0110 0... 3A60 to 3A67 Hong Kong (UK) 5.7 6.5 7 0011 1010 0110 1... 3A68 to 3A6F Moldova 4.4 6.0e 7 0011 1010 0111 0... 3A70 to 3A77 Costa Rica 3.2 5.2 7 0011 1010 0111 1... 3A78 to 3A7F Finland 5.0 5.1 7 0011 1010 1000 0... 3A80 to 3A87 Mauritania 2.1 5.1 7 0011 1010 1000 1... 3A88 to 3A8F Lithuania 3.7 5.0e 7 0011 1010 1001 0... 3A90 to 3A97 Ireland 3.5 5.0 7 0011 1010 1001 1... 3A98 to 3A9F Albania 3.3 5.0 7 0011 1010 1010 0... 3AA0 to 3AA7 draft-deering-ipv6-metro-addr-00.txt [Page 10] INTERNET-DRAFT IPv6 Metro Addressing March 1, 1996 Denmark 5.2 4.9 7 0011 1010 1010 1... 3AA8 to 3AAF Mongolia 2.3 4.8 7 0011 1010 1011 0... 3AB0 to 3AB7 Oman 2.1 4.8 7 0011 1010 1011 1... 3AB8 to 3ABF Lebanon 3.4 4.7 7 0011 1010 1100 0... 3AC0 to 3AC7 Namibia 1.5 4.7 7 0011 1010 1100 1... 3AC8 to 3ACF Puerto Rico (US) 3.5 4.6 7 0011 1010 1101 0... 3AD0 to 3AD7 Norway 4.3 4.5 7 0011 1010 1101 1... 3AD8 to 3ADF Lesotho 1.9 4.4 7 0011 1010 1110 0... 3AE0 to 3AE7 New Zealand 3.4 4.1 7 0011 1010 1110 1... 3AE8 to 3AEF Bophuthatswana (SA) 2.0 4.0e 7 0011 1010 1111 0... 3AF0 to 3AF7 (Unassigned) 0011 1010 1111 1... 3AF8 to 3AFF (Unassigned) 0011 1011 cccc c... 3Bxx Panama 2.4 3.9 3 0011 1100 0000 00.. 3C00 to 3C03 Kuwait 1.4 3.8 3 0011 1100 0000 01.. 3C04 to 3C07 Uraguay 3.1 3.7 3 0011 1100 0000 10.. 3C08 to 3C0B Jamaica 2.5 3.5 3 0011 1100 0000 11.. 3C0C to 3C0F Botswana 1.4 3.4 3 0011 1100 0001 00.. 3C10 to 3C13 Singapore 2.8 3.3 3 0011 1100 0001 01.. 3C14 to 3C17 Bhutan 0.7 3.1 3 0011 1100 0001 10.. 3C18 to 3C1B Latvia 2.7 3.0e 3 0011 1100 0001 11.. 3C1C to 3C1F Macedonia 1.9 3.0e 3 0011 1100 0010 00.. 3C20 to 3C23 Slovenia 1.9 3.0e 3 0011 1100 0010 01.. 3C24 to 3C27 Gabon 1.1 2.9 3 0011 1100 0010 10.. 3C28 to 3C2B United Arab Emir. 2.5 2.7 3 0011 1100 0010 11.. 3C2C to 3C2F Swaziland 0.8 2.2 3 0011 1100 0011 00.. 3C30 to 3C33 Estonia 1.6 2.0e 3 0011 1100 0011 01.. 3C34 to 3C37 Trinidad & Tobago 1.3 2.0 3 0011 1100 0011 10.. 3C38 to 3C3B Ciskei (SA) 0.9 2.0e 3 0011 1100 0011 11.. 3C3C to 3C3F Guinea-Bissau 1.0 1.9 3 0011 1100 0100 00.. 3C40 to 3C43 Gambia 0.9 1.9 3 0011 1100 0100 01.. 3C44 to 3C47 Comoros 0.5 1.7 3 0011 1100 0100 10.. 3C48 to 3C4B Mauritius 1.1 1.4 3 0011 1100 0100 11.. 3C4C to 3C4F Libya 4.5 1.3 3 0011 1100 0101 00.. 3C50 to 3C53 Guyana 0.8 1.2 3 0011 1100 0101 01.. 3C54 to 3C57 Fiji 0.8 1.1 3 0011 1100 0101 10.. 3C58 to 3C5B Djibouti 0.4 1.1 3 0011 1100 0101 11.. 3C5C to 3C5F Macao (Port.) 0.5 1.0e 3 0011 1100 0110 00.. 3C60 to 3C63 Venda (SA) 0.5 1.0e 3 0011 1100 0110 01.. 3C64 to 3C67 Cyprus 0.7 0.9 3 0011 1100 0110 10.. 3C68 to 3C6B Reunion (Fr.) 0.6 0.9 3 0011 1100 0110 11.. 3C6C to 3C6F Bahrain 0.5 0.9 3 0011 1100 0111 00.. 3C70 to 3C73 Qatar 0.5 0.9 3 0011 1100 0111 01.. 3C74 to 3C77 Cape Verde 0.4 0.9 3 0011 1100 0111 10.. 3C78 to 3C7B Equatorial Guinea 0.4 0.8 3 0011 1100 0111 11.. 3C7C to 3C7F Solomon Islands 0.4 0.7 3 0011 1100 1000 00.. 3C80 to 3C83 Suriname 0.4 0.7 3 0011 1100 1000 01.. 3C84 to 3C87 Luxembourg 0.4 0.4 3 0011 1100 1000 10.. 3C88 to 3C8B draft-deering-ipv6-metro-addr-00.txt [Page 11] INTERNET-DRAFT IPv6 Metro Addressing March 1, 1996 Malta 0.4 0.4 3 0011 1100 1000 11.. 3C8C to 3C8F Guadeloupe (Fr.) 0.4 0.4e 3 0011 1100 1001 00.. 3C90 to 3C93 Martinique (Fr.) 0.4 0.4e 3 0011 1100 1001 01.. 3C94 to 3C97 Bahamas 0.3 0.4 3 0011 1100 1001 10.. 3C98 to 3C9B Brunei 0.3 0.4 3 0011 1100 1001 11.. 3C9C to 3C9F Maldives 0.2 0.4 3 0011 1100 1010 00.. 3CA0 to 3CA3 Barbados 0.3 0.3 3 0011 1100 1010 01.. 3CA4 to 3CA7 Iceland 0.3 0.3 3 0011 1100 1010 10.. 3CA8 to 3CAB (Unassigned) 0011 1100 1010 11.. 3CAC to 3CAF (Unassigned) 0011 1100 1011 00.. 3CB0 to 3CB3 (Unassigned) 0011 1100 1011 01.. 3CB4 to 3CB7 (Unassigned) 0011 1100 1011 10.. 3CB8 to 3CBB (Unassigned) 0011 1100 1011 11.. 3CBC to 3CBF (Unassigned) 0011 1100 11cc cc.. 3CCx to 3CFx Belize 0.2 0.3 1 0011 1101 0000 0000 3D00 Vanautu 0.2 0.3 1 0011 1101 0000 0001 3D01 St. Lucia 0.2 0.2 1 0011 1101 0000 0010 3D02 French Polynesia 0.2 0.2e 1 0011 1101 0000 0011 3D03 Neth. Antilles 0.2 0.2e 1 0011 1101 0000 0100 3D04 New Caledonia (Fr.) 0.2 0.2e 1 0011 1101 0000 0101 3D05 U.S. Virgin Islands 0.2 0.2e 1 0011 1101 0000 0110 3D06 Western Samoa 0.2 0.2e 1 0011 1101 0000 0111 3D07 Sao Tome & Principe 0.1 0.2 1 0011 1101 0000 1000 3D08 St. Vincent & Gren. 0.1 0.2 1 0011 1101 0000 1001 3D09 Andorra 0.1 0.1 1 0011 1101 0000 1010 3D0A Antigua & Barbuda 0.1 0.1 1 0011 1101 0000 1011 3D0B Aruba (Neth.) 0.1 0.1 1 0011 1101 0000 1100 3D0C Dominica 0.1 0.1 1 0011 1101 0000 1101 3D0D Grenada 0.1 0.1 1 0011 1101 0000 1110 3D0E Kiribati 0.1 0.1 1 0011 1101 0000 1111 3D0F Seychelles 0.1 0.1 1 0011 1101 0001 0000 3D10 Tonga 0.1 0.1 1 0011 1101 0001 0001 3D11 Burmuda (UK) 0.1 0.1e 1 0011 1101 0001 0010 3D12 French Guiana (Fr.) 0.1 0.1e 1 0011 1101 0001 0011 3D13 Greenland (Den.) 0.1 0.1e 1 0011 1101 0001 0100 3D14 Guam (US) 0.1 0.1e 1 0011 1101 0001 0101 3D15 Isle of Man (UK) 0.1 0.1e 1 0011 1101 0001 0110 3D16 Micronesia 0.1 0.1e 1 0011 1101 0001 0111 3D17 Liechtenstein <.1 <.1 1 0011 1101 0001 1000 3D18 Monaco <.1 <.1 1 0011 1101 0001 1001 3D19 Nauru <.1 <.1 1 0011 1101 0001 1010 3D1A St. Kitts & Nevis <.1 <.1 1 0011 1101 0001 1011 3D1B San Marino <.1 <.1 1 0011 1101 0001 1100 3D1C Tuvalu <.1 <.1 1 0011 1101 0001 1101 3D1D American Samoa (US) <.1 <.1e 1 0011 1101 0001 1110 3D1E British Virgin Is. <.1 <.1e 1 0011 1101 0001 1111 3D1F Cayman Islands (UK) <.1 <.1e 1 0011 1101 0010 0000 3D20 draft-deering-ipv6-metro-addr-00.txt [Page 12] INTERNET-DRAFT IPv6 Metro Addressing March 1, 1996 Channel Islands (UK)<.1 <.1e 1 0011 1101 0010 0001 3D21 Faeroe Is. (Den.) <.1 <.1e 1 0011 1101 0010 0010 3D22 Falkland Is. (UK) <.1 <.1e 1 0011 1101 0010 0011 3D23 Gibraltar (UK) <.1 <.1e 1 0011 1101 0010 0100 3D24 Mariana Islands (US)<.1 <.1e 1 0011 1101 0010 0101 3D25 Marshall Islands <.1 <.1e 1 0011 1101 0010 0110 3D26 Mayotte (Fr.) <.1 <.1e 1 0011 1101 0010 0111 3D27 Montserrat (UK) <.1 <.1e 1 0011 1101 0010 1000 3D28 Palau (US) <.1 <.1e 1 0011 1101 0010 1001 3D29 Pitcairn Island (UK)<.1 <.1e 1 0011 1101 0010 1010 3D2A St. Helena (UK) <.1 <.1e 1 0011 1101 0010 1011 3D2B St. Pierre&Miq (Fr.)<.1 <.1e 1 0011 1101 0010 1100 3D2C Turks & Caicos (UK) <.1 <.1e 1 0011 1101 0010 1101 3D2D Vatican City <.1 <.1e 1 0011 1101 0010 1110 3D2E Wallis&Futuna (Fr.) <.1 <.1e 1 0011 1101 0010 1111 3D2F (Unassigned) 0011 1101 0011 cccc 3D3x (Unassigned) 0011 1101 01cc cccc 3D4x to 3D7x (Unassigned) 0011 1101 10cc cccc 3D8x to 3DBx (Unassigned) 0011 1101 11cc cccc 3DCx to 3DFx -------------------------------------------------------------------------- TOTAL 5,433.5 8,569.0 225 countries & territories e - my own rough estimate ccc - unassigned country ID bits ... - any binary digits xxx - any hex digits draft-deering-ipv6-metro-addr-00.txt [Page 13] INTERNET-DRAFT IPv6 Metro Addressing March 1, 1996 Appendix B - Canada Metro Codes Metro Areas in prefix (binary) prefix (hex) Canada ------------------------------------------------------------- (reserved) 0011 0011 1000 0000 3380 Toronto 0011 0011 1000 0001 3381 Montreal 0011 0011 1000 0010 3382 Vancouver 0011 0011 1000 0011 3383 Edmonton 0011 0011 1000 0100 3384 Ottawa - Hull 0011 0011 1000 0101 3385 Calgary 0011 0011 1000 0110 3386 Hamilton 0011 0011 1000 0111 3387 Quebec City 0011 0011 1000 1000 3388 Winnipeg 0011 0011 1000 1001 3389 Halifax 0011 0011 1000 1010 338A Kitchener 0011 0011 1000 1011 338B London 0011 0011 1000 1100 338C St. Catherines - Niagara 0011 0011 1000 1101 338D Victoria 0011 0011 1000 1110 338E Windsor 0011 0011 1000 1111 338F Chicoutimi - Jonquiere 0011 0011 1001 0000 3390 Oshawa 0011 0011 1001 0001 3391 Regina 0011 0011 1001 0010 3392 St. John's 0011 0011 1001 0011 3393 Saskatoon 0011 0011 1001 0100 3394 Saint John 0011 0011 1001 0101 3395 Sherbrooke 0011 0011 1001 0110 3396 Sudbury 0011 0011 1001 0111 3397 Thunder Bay 0011 0011 1001 1000 3398 Trois-Rivieres 0011 0011 1001 1001 3399 (unassigned) 0011 0011 1001 101m 339A and 339B (unassigned) 0011 0011 1001 11mm 339C to 339F (unassigned) 0011 0011 101m mmmm 33A0 to 33BF draft-deering-ipv6-metro-addr-00.txt [Page 14] INTERNET-DRAFT IPv6 Metro Addressing March 1, 1996 Appendix C - USA Metro Codes Metro Areas in prefix (binary) prefix (hex) United States ---------------------------------------------------------------------------- (reserved) 0001 0100 0000 0000 1400 New York City - Northern NJ - Long Is 0001 0100 0000 0001 1401 Los Angeles - Anaheim - Riverside 0001 0100 0000 0010 1402 Chicago - Gary - Lake County 0001 0100 0000 0011 1403 San Francisco - Oakland - San Jose 0001 0100 0000 0100 1404 Philadelphia - Wilmington - Trenton 0001 0100 0000 0101 1405 Detroit - Ann Arbor 0001 0100 0000 0110 1406 Boston - Lawrence - Salem 0001 0100 0000 0111 1407 Washington, D.C. 0001 0100 0000 1000 1408 Dallas - Fort Worth 0001 0100 0000 1001 1409 Houston - Galveston - Brazoria 0001 0100 0000 1010 140A Miami - Fort Lauderdale 0001 0100 0000 1011 140B Atlanta 0001 0100 0000 1100 140C Cleveland - Akron - Lorain 0001 0100 0000 1101 140D Seattle - Tacoma 0001 0100 0000 1110 140E San Diego 0001 0100 0000 1111 140F Minneapolis - St. Paul 0001 0100 0001 0000 1410 St. Louis 0001 0100 0001 0001 1411 Baltimore 0001 0100 0001 0010 1412 Pittsburgh - Beaver Valley 0001 0100 0001 0011 1413 Phoenix 0001 0100 0001 0100 1414 Tampa - St. Petersburg - Clearwater 0001 0100 0001 0101 1415 Denver - Boulder 0001 0100 0001 0110 1416 Cincinnati - Hamilton 0001 0100 0001 0111 1417 Milwaukee - Racine 0001 0100 0001 1000 1418 Kansas City 0001 0100 0001 1001 1419 Sacramento 0001 0100 0001 1010 141A Portland - Vancouver 0001 0100 0001 1011 141B Norfolk - Virginia Beach - Newport News 0001 0100 0001 1100 141C Columbus 0001 0100 0001 1101 141D San Antonio 0001 0100 0001 1110 141E Indianapolis 0001 0100 0001 1111 141F New Orleans 0001 0100 0010 0000 1420 Buffalo - Niagara Falls 0001 0100 0010 0001 1421 Charlotte - Gastonia - Rock Hill 0001 0100 0010 0010 1422 Providence - Pawtucket - Fall River 0001 0100 0010 0011 1423 Hartford - New Britain - Middletown 0001 0100 0010 0100 1424 Orlando 0001 0100 0010 0101 1425 Salt Lake City 0001 0100 0010 0110 1426 Rochester 0001 0100 0010 0111 1427 Nashville 0001 0100 0010 1000 1428 Memphis 0001 0100 0010 1001 1429 Oklahoma City 0001 0100 0010 1010 142A draft-deering-ipv6-metro-addr-00.txt [Page 15] INTERNET-DRAFT IPv6 Metro Addressing March 1, 1996 Louisville 0001 0100 0010 1011 142B Dayton - Springfield 0001 0100 0010 1100 142C Greensboro - Winston - Salem - High Pt. 0001 0100 0010 1101 142D Birmingham 0001 0100 0010 1110 142E Jacksonville 0001 0100 0010 1111 142F Albany - Schenectady - Troy 0001 0100 0011 0000 1430 Richmond - Petersburg 0001 0100 0011 0001 1431 West Palm Beach - Boca Raton 0001 0100 0011 0010 1432 Honolulu 0001 0100 0011 0011 1433 Austin 0001 0100 0011 0100 1434 Las Vegas 0001 0100 0011 0101 1435 Raleigh-Durham 0001 0100 0011 0110 1436 Scranton - Wilkes-Barre 0001 0100 0011 0111 1437 Tulsa 0001 0100 0011 1000 1438 Grand Rapids 0001 0100 0011 1001 1439 Allentown - Bethlehem - Easton 0001 0100 0011 1010 143A Fresno 0001 0100 0011 1011 143B Tucson 0001 0100 0011 1100 143C Syracuse 0001 0100 0011 1101 143D Greenville - Spartanville 0001 0100 0011 1110 143E Omaha 0001 0100 0011 1111 143F Toledo 0001 0100 0100 0000 1440 Knoxville 0001 0100 0100 0001 1441 El Paso 0001 0100 0100 0010 1442 Harrisburg - Lebanon - Carlisle 0001 0100 0100 0011 1443 Bakersfield 0001 0100 0100 0100 1444 New Haven - Meriden 0001 0100 0100 0101 1445 Springfield 0001 0100 0100 0110 1446 Baton Rouge 0001 0100 0100 0111 1447 Little Rock - North Little Rock 0001 0100 0100 1000 1448 Charleston 0001 0100 0100 1001 1449 Youngstown - Warren 0001 0100 0100 1010 144A Wichita 0001 0100 0100 1011 144B Stockton 0001 0100 0100 1100 144C Albuquerque 0001 0100 0100 1101 144D Mobile 0001 0100 0100 1110 144E Columbia 0001 0100 0100 1111 144F Worcester 0001 0100 0101 0000 1450 Johnson City - Kingsport - Bristol 0001 0100 0101 0001 1451 Chattanooga 0001 0100 0101 0010 1452 Lansing - East Lansing 0001 0100 0101 0011 1453 Flint 0001 0100 0101 0100 1454 Lancaster 0001 0100 0101 0101 1455 York 0001 0100 0101 0110 1456 Lakeland - Winter Haven 0001 0100 0101 0111 1457 (unassigned) 0001 0100 0101 1mmm 1458 to 145F (unassigned) 0001 0100 011m mmmm 1460 to 147F (unassigned) 0001 0100 1mmm mmmm 1480 to 14FF draft-deering-ipv6-metro-addr-00.txt [Page 16] INTERNET-DRAFT IPv6 Metro Addressing March 1, 1996 (unassigned) 0001 0101 mmmm mmmm 1500 to 15FF draft-deering-ipv6-metro-addr-00.txt [Page 17] INTERNET-DRAFT IPv6 Metro Addressing March 1, 1996 Security Considerations Security issues are not discussed in this memo. Authors' Addresses Stephen E. Deering Robert M. Hinden Xerox Palo Alto Research Center Ipsilon Networks, Inc. 3333 Coyote Hill Road 2191 E. Bayshore Road Palo Alto, CA 94304 Palo Alto, CA 94303 USA USA phone: +1 415 812 4839 phone: +1 415 846 4604 fax: +1 415 812 4471 fax: +1 415 855 1414 email: deering@parc.xerox.com email: hinden@ipsilon.com References [ARCH] Hinden, R., S. Deering, "IP Version 6 Addressing Architecture", RFC-1884, December 1995. [ASSN] Tsuchiya, P., "On the Assignment of Subnet Numbers", RFC-1219, April 16, 1991. [AUTO] Thompson, S.,T. Nartin, "IPv6 Address Autoconfiguration", Internet Draft, December 1995. [PROV] Rekhter, Y., Li, T., "An Architecture for IPv6 Unicast Address Allocation", RFC-1887, December 1995. draft-deering-ipv6-metro-addr-00.txt [Page 18]