Home  ›  what is known as “one-to-nearest” addressing in ipv6?

what is known as “one-to-nearest” addressing in ipv6?

Written By Wednesday, April 6, 2022 Add Comment Edit

Label to identify a network interface of a computer or other network node

Decomposition of an IPv6 address into its binary form

An Internet Protocol Version 6 address (IPv6 address) is a numeric label that is used to identify and locate a network interface of a computer or a network node participating in an computer network using IPv6. IP addresses are included in the package header to bespeak the source and the destination of each packet. The IP accost of the destination is used to make decisions about routing IP packets to other networks.

IPv6 is the successor to the first addressing infrastructure of the Internet, Internet Protocol version 4 (IPv4). In contrast to IPv4, which defined an IP accost as a 32-bit value, IPv6 addresses accept a size of 128 bits. Therefore, in comparison, IPv6 has a vastly enlarged address space.

Addressing methods [edit]

IPv6 addresses are classified past the primary addressing and routing methodologies common in networking: unicast addressing, anycast addressing, and multicast addressing.[1]

A unicast address identifies a single network interface. The Internet Protocol delivers packets sent to a unicast address to that specific interface.

An anycast address is assigned to a group of interfaces, commonly belonging to different nodes. A packet sent to an anycast accost is delivered to just 1 of the member interfaces, typically the nearest host, co-ordinate to the routing protocol's definition of distance. Anycast addresses cannot be identified easily, they accept the same format as unicast addresses, and differ only by their presence in the network at multiple points. Virtually any unicast address can be employed as an anycast accost.

A multicast address is also used by multiple hosts that acquire the multicast accost destination by participating in the multicast distribution protocol among the network routers. A packet that is sent to a multicast accost is delivered to all interfaces that have joined the corresponding multicast group. IPv6 does not implement broadcast addressing. Broadcast's traditional role is subsumed by multicast addressing to the all-nodes link-local multicast grouping ff02::ane . All the same, the utilise of the all-nodes grouping is non recommended, and most IPv6 protocols use a dedicated link-local multicast group to avoid disturbing every interface in the network.

Address formats [edit]

An IPv6 address consists of 128 bits.[1] For each of the major addressing and routing methodologies, various accost formats are recognized by dividing the 128 address bits into bit groups and using established rules for associating the values of these bit groups with special addressing features.

Unicast and anycast accost format [edit]

Unicast and anycast addresses are typically composed of two logical parts: a 64-scrap network prefix used for routing, and a 64-bit interface identifier used to identify a host's network interface.

Full general unicast address format (routing prefix size varies)
bits 48 (or more) 16 (or fewer) 64
field routing prefix subnet id interface identifier

The network prefix (the routing prefix combined with the subnet id) is contained in the most significant 64 bits of the address. The size of the routing prefix may vary; a larger prefix size means a smaller subnet id size. The bits of the subnet id field are available to the network administrator to define subnets inside the given network. The 64-bit interface identifier is either automatically generated from the interface's MAC address using the modified EUI-64 format, obtained from a DHCPv6 server, automatically established randomly, or assigned manually.

Unique local addresses are addresses analogous to IPv4 private network addresses.

Unique local accost format
bits 7 ane forty 16 64
field prefix L random subnet id interface identifier

The prefix field contains the binary value 1111110. The L scrap is one for locally assigned addresses; the accost range with L ready to zero is currently not defined. The random field is called randomly once, at the inception of the / 48 routing prefix.

A link-local address is as well based on the interface identifier, but uses a different format for the network prefix.

Link-local address format
bits x 54 64
field prefix zeroes interface identifier

The prefix field contains the binary value 1111111010. The 54 zeroes that follow make the total network prefix the same for all link-local addresses ( fe80:: / 64 link-local address prefix), rendering them not-routable.

Multicast address format [edit]

Multicast addresses are formed according to several specific formatting rules, depending on the application.

General multicast address format
bits viii 4 4 112
field prefix flg sc group ID

For all multicast addresses, the prefix field holds the binary value 11111111.

Currently, three of the iv flag $.25 in the flg field are divers;[1] the most-significant flag flake is reserved for time to come use.

Multicast address flags[2]
bit flag Significant when 0 Meaning when one
eight reserved reserved reserved
9 R (Rendezvous)[3] Rendezvous point not embedded Rendezvous point embedded
10 P (Prefix)[four] Without prefix data Address based on network prefix
11 T (Transient)[one] Well-known multicast address Dynamically assigned multicast accost

The iv-bit scope field (sc) is used to signal where the address is valid and unique.

In improver, the telescopic field is used to place special multicast addresses, similar solicited node.

Solicited-node multicast address format
$.25 8 4 4 79 9 24
field prefix flg sc zeroes ones unicast address

The sc(ope) field holds the binary value 0010 (link-local). Solicited-node multicast addresses are computed as a function of a node's unicast or anycast addresses. A solicited-node multicast address is created by copying the last 24 bits of a unicast or anycast address to the terminal 24 bits of the multicast accost.

Unicast-prefix-based multicast accost format[three] [4]
bits 8 4 four 4 4 viii 64 32
field prefix flg sc res riid plen network prefix group ID

Link-scoped multicast addresses use a comparable format.[5]

Representation [edit]

An IPv6 address is represented equally viii groups of four hexadecimal digits, each grouping representing 16 bits[a] The groups are separated past colons (:). An example of an IPv6 accost is:

2001:0db8:85a3:0000:0000:8a2e:0370:7334

The standards provide flexibility in the representation of IPv6 addresses. The full representation of eight 4-digit groups may be simplified by several techniques, eliminating parts of the representation. In general, representations are shortened as much every bit possible. However, this do complicates several common operations, namely searching for a specific address or an address pattern in text documents or streams, and comparing addresses to make up one's mind equivalence. For mitigation of these complications, the IETF has defined a approved format for rendering IPv6 addresses in text:[8]

  • The hexadecimal digits are always compared in example-insensitive way, but IETF recommendations suggest the use of merely lower case letters. For instance, 2001:db8::1 is preferred over 2001:DB8::one;
  • Leading zeros in each xvi-bit field are suppressed, just each group must retain at least ane digit. For example, 2001:0db8::0001:0000 is rendered as 2001:db8::1:0 ;
  • The longest sequence of consecutive all-zero fields is replaced with two colons (::). If the address contains multiple runs of all-cypher fields of the same size, to prevent ambiguities, information technology is the leftmost that is compressed. For example, 2001:db8:0:0:i:0:0:1 is rendered as 2001:db8::1:0:0:1 rather than as 2001:db8:0:0:one::1 . :: is non used to represent simply a single all-nothing field. For example, 2001:db8:0:0:0:0:2:1 is shortened to 2001:db8::two:1 , but 2001:db8:0000:one:1:1:i:1 is rendered as 2001:db8:0:1:1:1:ane:1 .

These methods can lead to very short representations for IPv6 addresses. For example, the localhost (loopback) accost, 0:0:0:0:0:0:0:i , and the IPv6 unspecified address, 0:0:0:0:0:0:0:0 , are reduced to ::i and :: , respectively.

During the transition of the Net from IPv4 to IPv6, it is typical to operate in a mixed addressing environment. For such employ cases, a special annotation has been introduced, which expresses IPv4-mapped and IPv4-compatible IPv6 addresses past writing the least-significant 32 $.25 of an accost in the familiar IPv4 dot-decimal notation, whereas the 96 about-meaning bits are written in IPv6 format. For example, the IPv4-mapped IPv6 accost ::ffff:c000:0280 is written as ::ffff:192.0.two.128 , thus expressing clearly the original IPv4 address that was mapped to IPv6.

Networks [edit]

An IPv6 network uses an address block that is a contiguous group of IPv6 addresses of a size that is a ability of 2. The leading set of $.25 of the addresses are identical for all hosts in a given network, and are called the network'south address or routing prefix.

Network address ranges are written in CIDR notation. A network is denoted by the kickoff address in the block (ending in all zeroes), a slash (/), and a decimal value equal to the size in bits of the prefix. For case, the network written every bit 2001:db8:1234:: / 48 starts at accost 2001:db8:1234:0000:0000:0000:0000:0000 and ends at 2001:db8:1234:ffff:ffff:ffff:ffff:ffff .

The routing prefix of an interface address may exist straight indicated with the accost using CIDR notation. For example, the configuration of an interface with address 2001:db8:a::123 connected to subnet 2001:db8:a:: / 64 is written equally 2001:db8:a::123 / 64 .

Address block sizes [edit]

The size of a cake of addresses is specified by writing a slash (/) followed by a number in decimal whose value is the length of the network prefix in bits. For example, an address block with 48 bits in the prefix is indicated by / 48 . Such a block contains 2128 − 48 = 280 addresses. The smaller the value of the network prefix, the larger the block: a / 21 block is eight times larger than a / 24 block.

Literal IPv6 addresses in network resources identifiers [edit]

Colon (:) characters in IPv6 addresses may conflict with the established syntax of resource identifiers, such as URIs and URLs. The colon is conventionally used to terminate the host path before a port number.[ix] To alleviate this conflict, literal IPv6 addresses are enclosed in square brackets in such resources identifiers, for example:

http://[2001:db8:85a3:8d3:1319:8a2e:370:7348]/

When the URL also contains a port number the notation is:

https://[2001:db8:85a3:8d3:1319:8a2e:370:7348]:443/

where the trailing 443 is the instance's port number.

Scoped literal IPv6 addresses (with zone alphabetize) [edit]

For addresses with other than global telescopic (as described below), and in particular for link-local addresses, the choice of the network interface for sending a package may depend on which zone the address belongs to: the same accost may be valid in unlike zones, and be in use by a different host in each of those zones. Even if a single address is not in use in different zones, the address prefixes for addresses in those zones may nevertheless be identical, which makes the operating system unable to select an outgoing interface based on the information in the routing table (which is prefix-based).

In gild to resolve the ambiguity in textual addresses, a zone index must be appended to the address, the ii separated past a percent sign (%).[ten] The syntax of zone indices is an implementation-dependent cord, although numeric zone indices must be universally supported as well. The link-local address

fe80::1ff:fe23:4567:890a

could be expressed past

fe80::1ff:fe23:4567:890a%eth2

or:

fe80::1ff:fe23:4567:890a%three

The former (using an interface name) is customary on most Unix-similar operating systems (eastward.k., BSD, Linux, macOS). The latter (using an interface number) is the standard syntax on Microsoft Windows, but as support for this syntax is mandatory, it is also available on other operating systems.

BSD-based operating systems (including macOS) also support an alternative, non-standard syntax, where a numeric zone alphabetize is encoded in the second 16-fleck word of the address. E.g.:

fe80:3::1ff:fe23:4567:890a

In all operating systems mentioned above, the zone index for link-local addresses actually refers to an interface, not to a zone. As multiple interfaces may belong to the aforementioned zone (e.1000. when continued to the same switch), in exercise two addresses with different zone identifiers may actually be equivalent, and refer to the same host on the same link.

Use of zone indices in URIs [edit]

When used in uniform resource identifiers (URI), the utilise of the per centum sign causes a syntax conflict, therefore it must exist escaped via percentage-encoding,[11] due east.thou.:

http://[fe80::1ff:fe23:4567:890a%25eth0]/

Literal IPv6 addresses in UNC path names [edit]

In Microsoft Windows operating systems, IPv4 addresses are valid location identifiers in Uniform Naming Convention (UNC) path names. Withal, the colon is an illegal graphic symbol in a UNC path name. Thus, the utilise of IPv6 addresses is also illegal in UNC names. For this reason, Microsoft implemented a transcription algorithm to represent an IPv6 address in the form of a domain proper name that tin can exist used in UNC paths. For this purpose, Microsoft registered and reserved the 2d-level domain ipv6-literal.net on the Cyberspace (although they gave up the domain in January 2014[12]). IPv6 addresses are transcribed as a hostname or subdomain proper name inside this name space, in the following mode:

2001:db8:85a3:8d3:1319:8a2e:370:7348

is written every bit

2001-db8-85a3-8d3-1319-8a2e-370-7348.ipv6-literal.net

This notation is automatically resolved locally past Microsoft software, without whatever queries to DNS proper name servers.

If the IPv6 address contains a zone index, it is appended to the address portion after an 's' graphic symbol:

fe80::1ff:fe23:4567:890a%3

is written as

fe80--1ff-fe23-4567-890as3.ipv6-literal.net

Address scopes [edit]

Every IPv6 address, except the unspecified address ( :: ), has a "telescopic",[ten] which specifies in which part of the network it is valid.

Unicast [edit]

For unicast addresses, ii scopes are defined: link-local and global.

Link-local addresses and the loopback address have link-local scope, which means they tin can only be used on a single directly attached network (link). All other addresses (including Unique local addresses) have global (or universal) telescopic, which means they are (or could be) globally routable, and can exist used to connect to addresses with global scope anywhere, or to addresses with link-local scope on the direct attached network. Packets with a source or destination in one scope cannot be routed to a different telescopic.[thirteen]

Unique local addresses have global scope, but they are non globally administered. As a result, only other hosts in the same administrative domain (eastward.g., an organization), or within a cooperating authoritative domain are able to accomplish such addresses, if properly routed. Equally their telescopic is global, these addresses are valid as a source address when communicating with whatsoever other global-telescopic address, even though it may be impossible to route packets from the destination back to the source.

Anycast [edit]

Anycast addresses are syntactically identical to and indistinguishable from unicast addresses. Their only difference is authoritative. Scopes for anycast addresses are therefore the aforementioned as for unicast addresses.

Multicast [edit]

For multicast addresses, the four to the lowest degree-meaning bits of the 2d accost octet ( ff0s:: ) identify the address southcope, i.e. the domain in which the multicast bundle should exist propagated. Predefined and reserved scopes[1] are:

Telescopic values
Value Scope name Notes
0x0 reserved
0x1 interface-local Interface-local scope spans only a single interface on a node, and is useful only for loopback transmission of multicast.
0x2 link-local Link-local scope spans the aforementioned topological region as the corresponding unicast scope.
0x3 realm-local Realm-local scope is defined as larger than link-local, automatically determined by network topology and must not be larger than the following scopes.[14]
0x4 admin-local Admin-local scope is the smallest scope that must be administratively configured, i.due east., not automatically derived from concrete connectivity or other, not-multicast-related configuration.
0x5 site-local Site-local scope is intended to span a single site belonging to an organisation.
0x8 organisation-local System-local scope is intended to span all sites belonging to a single organisation.
0xe global Global scope spans all reachable nodes on the cyberspace - it is unbounded.
0xf reserved

All other scopes are unassigned, and bachelor to administrators for defining boosted regions.

Address space [edit]

General resource allotment [edit]

The management of IPv6 accost allocation process is delegated to the Internet Assigned Numbers Authority (IANA)[15] by the Internet Architecture Board and the Internet Engineering Steering Group. Its main function is the consignment of large address blocks to the regional Internet registries (RIRs), which have the delegated task of resource allotment to network service providers and other local registries. The IANA has maintained the official list of allocations of the IPv6 accost space since December 1995.[16]

Only one eighth of the total accost infinite is currently allocated for use on the Internet, 2000:: / 3 , in order to provide efficient route aggregation, thereby reducing the size of the Internet routing tables; the rest of the IPv6 address space is reserved for future use or for special purposes. The address space is assigned to the RIRs in large blocks of / 23 up to / 12 .[17]

The RIRs assign smaller blocks to local Internet registries that distributes them to users. These are typically in sizes from / 19 to / 32 .[eighteen] [nineteen] [20] The addresses are typically distributed in / 48 to / 56 sized blocks to the end users.[21]

Global unicast assignment records can be found at the various RIRs or other websites.[22]

IPv6 addresses are assigned to organizations in much larger blocks equally compared to IPv4 accost assignments—the recommended allotment is a / 48 block which contains 2lxxx addresses, existence 248 or about 2.8×1014 times larger than the entire IPv4 address space of 232 addresses and most 7.two×1016 times larger than the / viii blocks of IPv4 addresses, which are the largest allocations of IPv4 addresses. The total pool, however, is sufficient for the foreseeable future, because there are 2128 (exactly 340,282,366,920,938,463,463,374,607,431,768,211,456) or about iii.4×1038 (340 trillion trillion trillion) unique IPv6 addresses.

Each RIR can divide each of its multiple / 23 blocks into 512 / 32 blocks, typically 1 for each Isp; an Internet service provider can divide its / 32 cake into 65536 / 48 blocks, typically ane for each client;[23] customers can create 65536 / 64 networks from their assigned / 48 cake, each having two64 (xviii,446,744,073,709,551,616) addresses. In contrast, the entire IPv4 accost infinite has only 232 (exactly 4,294,967,296 or about four.3×10nine ) addresses.

Past design, only a very small fraction of the address space will really exist used. The large address space ensures that addresses are nearly ever available, which makes the use of network address translation (NAT) for the purposes of address conservation completely unnecessary. NAT has been increasingly used for IPv4 networks to help alleviate IPv4 address exhaustion.

Special allocation [edit]

To allow for provider changes without renumbering, provider-independent address space – assigned directly to the finish user by the RIRs – is taken from the special range 2001:678:: / 29 .

Internet Commutation Points (IXPs) are assigned special addresses from the ranges 2001:7f8:: / 32 , 2001:504:: / 30 , and 2001:7fa:: / 32 [24] for advice with their connected ISPs.

Root name servers have been assigned addresses from the range 2001:7f8:: / 29 .[25]

Reserved anycast addresses [edit]

The lowest accost within each subnet prefix (the interface identifier gear up to all zeroes) is reserved every bit the "subnet-router" anycast address.[1] Applications may apply this accost when talking to any i of the available routers, equally packets sent to this address are delivered to only ane router.

The 128 highest addresses within each / 64 subnet prefix are reserved to be used as anycast addresses.[26] These addresses usually have the first 57 bits of the interface identifier set up to 1, followed past the 7-bit anycast ID. Prefixes for the network, including subnets, are required to have a length of 64 bits, in which instance the universal/local bit must be prepare to 0 to point the address is not globally unique. The address with value 0x7e in the 7 least-significant bits is divers as a mobile IPv6 home agents anycast address. The address with value 0x7f (all bits 1) is reserved and may not be used. No more assignments from this range are made, then values 0x00 through 0x7d are reserved likewise.

Special addresses [edit]

There are a number of addresses with special meaning in IPv6.[27] They represent less than 2% of the entire address space:

Special address blocks
Accost cake (CIDR) First address Last accost Number of addresses Usage Purpose
::/0 :: ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff two128 Routing Default route (no specific route)
::/128 :: :: 1 Software Unspecified address
::one/128 ::1 ::1 1 Host Loopback address—a virtual interface that loops all traffic back to itself, the local host
::ffff:0:0/96 ::ffff:0.0.0.0 ::ffff:255.255.255.255 ii128 − 96 = 232 = 4294 967 296 Software IPv4-mapped addresses
::ffff:0:0:0/96 ::ffff:0:0.0.0.0 ::ffff:0:255.255.255.255 232 Software IPv4 translated addresses
64:ff9b::/96 64:ff9b::0.0.0.0 64:ff9b::255.255.255.255 232 Global Internet IPv4/IPv6 translation[28]
64:ff9b:1::/48 64:ff9b:1::0.0.0.0 64:ff9b:1:ffff:ffff:ffff:255.255.255.255 2eighty Private internets IPv4/IPv6 translation[29]
100::/64 100:: 100::ffff:ffff:ffff:ffff 264 Routing Discard prefix[30]
2001:0000::/32 2001:: 2001::ffff:ffff:ffff:ffff:ffff:ffff ii96 Global Cyberspace Teredo tunneling[31]
2001:20::/28 2001:20:: 2001:2f:ffff:ffff:ffff:ffff:ffff:ffff 2100 Software ORCHIDv2[32]
2001:db8::/32 2001:db8:: 2001:db8:ffff:ffff:ffff:ffff:ffff:ffff ii96 Documentation Addresses used in documentation and example source code[33]
2002::/16 2002:: 2002:ffff:ffff:ffff:ffff:ffff:ffff:ffff 2112 Global Internet The 6to4 addressing scheme (deprecated)[34]
fc00::/vii fc00:: fdff:ffff:ffff:ffff:ffff:ffff:ffff:ffff 2121 Private internets Unique local accost[35]
fe80::/64 from fe80::/10 fe80:: fe80::ffff:ffff:ffff:ffff 264 Link Link-local address
ff00::/8 ff00:: ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff ii120 Global Cyberspace Multicast address

Unicast addresses [edit]

Default route [edit]

  • :: / 0 — The default road address (corresponding to 0.0.0.0 / 0 in IPv4) for destination addresses (unicast, multicast and others) not specified elsewhere in a routing table.

Unspecified address [edit]

  • :: / 128 — The address with all zero $.25 is called the unspecified address (corresponding to 0.0.0.0 / 32 in IPv4).
    This accost must never be assigned to an interface and is to be used just in software before the application has learned its host's source address appropriate for a pending connection. Routers must not forward packets with the unspecified accost.
    Applications may be listening on one or more specific interfaces for incoming connections, which are shown in listings of active internet connections past a specific IP accost (and a port number, separated by a colon). When the unspecified address is shown it ways that an application is listening for incoming connections on all available interfaces.

Local addresses [edit]

  • ::1 / 128 — The loopback accost is a unicast localhost address (corresponding to 127.0.0.1 / viii in IPv4).
    If an application in a host sends packets to this accost, the IPv6 stack will loop these packets dorsum on the aforementioned virtual interface.
  • fe80:: / 10 — Addresses in the link-local prefix are only valid and unique on a unmarried link (comparable to the auto-configuration addresses 169.254.0.0 / 16 of IPv4).
    Within this prefix just one subnet is allocated (54 nada bits), yielding an constructive format of fe80:: / 64 . The least significant 64 bits are usually chosen as the interface hardware address constructed in modified EUI-64 format. A link-local address is required on every IPv6-enabled interface—in other words, applications may rely on the beingness of a link-local address fifty-fifty when there is no IPv6 routing.

Unique local addresses [edit]

  • fc00:: / vii — Unique local addresses (ULAs) are intended for local advice[35] (comparable to IPv4 private addresses 10.0.0.0 / eight , 172.sixteen.0.0 / 12 and 192.168.0.0 / 16 ).
    They are routable only inside a set of cooperating sites. The block is split into 2 halves. The lower one-half of the cake ( fc00:: / eight ) was intended for globally allocated prefixes, merely an allocation method has yet to be defined. The upper one-half ( fd00:: / 8 ) is used for "probabilistically unique" addresses in which the / 8 prefix is combined with a forty-bit locally generated pseudorandom number to obtain a / 48 private prefix. The fashion in which such a 40-bit number is chosen results in only a negligible take chances that two sites that wish to merge or communicate with each other will use the same 40-bit number, and thus employ the aforementioned / 48 prefix.[35]

Transition from IPv4 [edit]

  • ::ffff:0:0 / 96 — This prefix is used for IPv6 transition mechanisms and designated as an IPv4-mapped IPv6 address.
    With a few exceptions, this address blazon allows the transparent use of the transport layer protocols over IPv4 through the IPv6 networking application programming interface. Server applications only demand to open a single listening socket to handle connections from clients using IPv6 or IPv4 protocols. IPv6 clients volition be handled natively by default, and IPv4 clients announced as IPv6 clients at their IPv4-mapped IPv6 address. Transmission is handled similarly; established sockets may be used to transmit IPv4 or IPv6 datagram, based on the binding to an IPv6 address, or an IPv4-mapped address.
  • ::ffff:0:0:0 / 96 — A prefix used for IPv4-translated addresses.
    These are used by the Stateless IP/ICMP Translation (SIIT) protocol.[36]
  • 64:ff9b:: / 96 — The "Well-Known" Prefix.
    Addresses with this prefix are used for automatic IPv4/IPv6 translation.[28]
  • 64:ff9b:1:: / 48 — A prefix for locally translated IPv4/IPv6 addresses.
    Addresses with this prefix can be used for multiple IPv4/IPv6 translation mechanisms like NAT64 and SIIT.[29]
  • 2002:: / 16 — This prefix was used for 6to4 addressing (an address from the IPv4 network 192.88.99.0 / 24 was besides used).
    The 6to4 addressing scheme is deprecated.[34]

Main commodity: 6to4

Special-purpose addresses [edit]

IANA has reserved a so-called 'Sub-TLA ID' accost block for special assignments[27] [37] of 2001:: / 23 (divide into the range of 64 network prefixes 2001:0000:: / 29 through 2001:01f8:: / 29 ). 3 assignments from this cake are currently assigned:
  • 2001:: / 32 — Used for Teredo tunneling.
  • 2001:2:: / 48 — Used for benchmarking IPv6 (corresponding to 198.18.0.0 / 15 for benchmarking IPv4).
    Assigned to the Benchmarking Methodology Working Group (BMWG).[38]
  • 2001:twenty:: / 28 — ORCHIDv2 (Overlay Routable Cryptographic Hash Identifiers).[32]
    These are non-routed IPv6 addresses used for Cryptographic Hash Identifiers.

Documentation [edit]

  • 2001:db8:: / 32 — This prefix is used in documentation[33] (corresponding to 192.0.2.0 / 24 , 198.51.100.0 / 24 , and 203.0.113.0 / 24 in IPv4.)[39]
    The addresses should be used anywhere an case IPv6 accost is given or model networking scenarios are described.

Discard [edit]

  • 100:: / 64 — This prefix is used for discarding traffic.[xxx]

Deprecated and obsolete addresses [edit]

Further data: § Historical notes

Multicast addresses [edit]

The multicast addresses ff0x:: where x is any hexadecimal value are reserved[one] and should not exist assigned to any multicast group. The Internet Assigned Numbers Authority (IANA) manages address reservations.[40]

Some mutual IPv6 multicast addresses are the following:

Address Description Available Scopes
ff0X::i All nodes address, place the group of all IPv6 nodes Available in scope 1 (interface-local) and 2 (link-local):
  • ff01::ane → All nodes in the interface-local
  • ff02::1 → All nodes in the link-local
ff0X::ii All routers Available in telescopic i (interface-local), 2 (link-local) and five (site-local):
  • ff01::2 → All routers in the interface-local
  • ff02::ii → All routers in the link-local
  • ff05::ii → All routers in the site-local
ff02::five OSPFIGP 2 (link-local)
ff02::6 OSPFIGP designated routers 2 (link-local)
ff02::9 RIP routers ii (link-local)
ff02::a EIGRP routers ii (link-local)
ff02::d All PIM routers ii (link-local)
ff02::1a All RPL routers 2 (link-local)
ff0X::fb mDNSv6 Available in all scopes
ff0X::101 All NTP servers Available in all scopes
ff02::1:1 Link name 2 (link-local)
ff02::i:2 All-dhcp-agents (DHCPv6) 2 (link-local)
ff02::ane:3 Link-local multicast name resolution 2 (link-local)
ff05::1:3 All-dhcp-servers (DHCPv6) 5 (site-local)
ff02::1:ff00:0/104 Solicited-node multicast address. Meet below 2 (link-local)
ff02::two:ff00:0/104 Node information queries ii (link-local)

Solicited-node multicast accost [edit]

The to the lowest degree significant 24 bits of the solicited-node multicast accost grouping ID are filled with the least significant 24 bits of the interface's unicast or anycast address. These addresses let link layer accost resolution via Neighbor Discovery Protocol (NDP) on the link without disturbing all nodes on the local network. A host is required to join a solicited-node multicast group for each of its configured unicast or anycast addresses.

Stateless accost autoconfiguration [edit]

On system startup, a node automatically creates a link-local accost on each IPv6-enabled interface, even if globally routable addresses are manually configured or obtained through "configuration protocols" (see below). It does so independently and without whatsoever prior configuration past stateless address autoconfiguration (SLAAC),[41] using a component of the Neighbor Discovery Protocol. This accost is selected with the prefix fe80:: / 64 .

In IPv4, typical "configuration protocols" include DHCP or PPP. Although DHCPv6 exists, IPv6 hosts normally use the Neighbour Discovery Protocol to create a globally routable unicast address: the host sends router solicitation requests and an IPv6 router responds with a prefix assignment.[42]

The lower 64 bits of these addresses are populated with a 64-bit interface identifier in modified EUI-64 format. This identifier is unremarkably shared by all automatically configured addresses of that interface, which has the reward that only one multicast grouping needs to be joined for neighbor discovery. For this, a multicast address is used, formed from the network prefix ff02::1:ff00:0 / 104 and the 24 least significant $.25 of the address.

Modified EUI-64 [edit]

A 64-bit interface identifier is almost commonly derived from its 48-bit MAC address. A MAC accost 00-0C-29-0C-47-D5 is turned into a 64-scrap EUI-64 past inserting FF-Iron in the middle: 00-0C-29-FF-Fe-0C-47-D5 . When this EUI-64 is used to class an IPv6 address, it is modified:[one] the meaning of the Universal/Local bit (the 7th most significant bit of the EUI-64, starting from 1) is inverted, and so that a one now means Universal. To create an IPv6 address with the network prefix 2001:db8:1:2:: / 64 it yields the address 2001:db8:1:2:020c:29ff:fe0c:47d5 (with the Universal/Local fleck, the second-least-significant bit of the underlined quartet, inverted to 1 in this example because the MAC address is universally unique).

Indistinguishable address detection [edit]

The assignment of a unicast IPv6 address to an interface involves an internal test for the uniqueness of that address using Neighbor Solicitation and Neighbour Advertisement (ICMPv6 type 135 and 136) messages. While in the process of establishing uniqueness an address has a tentative country.

The node joins the solicited-node multicast address for the tentative address (if not already washed and then) and sends neighbour solicitations, with the tentative address as target address and the unspecified address ( :: / 128 ) as source address. The node also joins the all-hosts multicast accost ff02::1 , and so information technology volition be able to receive Neighbor Advertisements.

If a node receives a neighbour solicitation with its own tentative accost equally the target address, then that address is not unique. The same is true if the node receives a neighbor advertising with the tentative address as the source of the advertising. Only afterward having successfully established that an address is unique may it be assigned and used past an interface.

Address lifetime [edit]

Each IPv6 address that is bound to an interface has a stock-still lifetime. Lifetimes are infinite, unless configured to a shorter flow. There are two lifetimes that govern the country of an address: the preferred lifetime and the valid lifetime.[43] Lifetimes can be configured in routers that provide the values used for autoconfiguration, or specified when manually configuring addresses on interfaces.

When an address is assigned to an interface it gets the status "preferred", which it holds during its preferred-lifetime. After that lifetime expires the condition becomes "deprecated" and no new connections should be made using this address. The accost becomes "invalid" subsequently its valid-lifetime also expires; the address is removed from the interface and may be assigned somewhere else on the Internet.

Note: In nigh cases, the lifetime does non elapse because new Router Advertisements (RAs) refresh the timers. Merely if in that location are no more RAs, eventually the preferred lifetime elapses and the address becomes "deprecated".

Temporary addresses [edit]

The globally unique and static MAC addresses, used by stateless address autoconfiguration to create interface identifiers, offer an opportunity to track user equipment—across time and IPv6 network prefix changes—and so users.[44] To reduce the prospect of a user identity beingness permanently tied to an IPv6 address portion, a node may create temporary addresses with interface identifiers based on time-varying random chip strings[45] and relatively short lifetimes (hours to days), after which they are replaced with new addresses.

Temporary addresses may be used as source accost for originating connections, while external hosts use a public accost past querying the Domain Name Organisation.

Network interfaces configured for IPv6 apply temporary addresses by default in Os X Lion and later Apple systems as well as in Windows Vista, Windows 2008 Server and later Microsoft systems.

Cryptographically generated addresses [edit]

As a means to heighten security for Neighbor Discovery Protocol cryptographically generated addresses (or CGAs) were introduced in 2005[46] as office of the Secure Neighbor Discovery (Transport) Protocol.

Such an address is generated using 2 hash functions that take several inputs. The get-go uses a public key and a random modifier; the latter being incremented repeatedly until a specific amount of null bits of the resulting hash is caused. (Comparable with the 'proof of piece of work' field in Bitcoin mining.) The second hash function takes the network prefix and the previous hash value. The least significant 64 bits of the 2nd hash consequence is appended to the 64-fleck network prefix to form a 128-bit accost.

The hash functions tin also be used to verify if a specific IPv6 address satisfies the requirement of being a valid CGA. This manner, communication can be fix between trusted addresses exclusively.

Stable privacy addresses [edit]

The utilise of stateless autoconfigured addresses has serious implications for security and privacy concerns,[47] because the underlying hardware address (most typically the MAC address) is exposed beyond the local network, permitting the tracking of user activities and correlation of user accounts to other information. It too permits vendor-specific attack strategies, and reduces the size of the address space for searching for assault targets.

Stable privacy addresses were introduced to remedy these shortcomings. They are stable within a specific network but modify when moving to another, to improve privacy. They are chosen deterministically, but randomly, in the entire accost space of the network.

Generation of a stable privacy address is based on a hash function that uses several stable parameters. It is implementation specific, but information technology is recommended to use at to the lowest degree the network prefix, the name of the network interface, a duplicate address counter, and a secret key. The resulting hash value is used to construct the final accost: Typically the 64 least significant bits are concatenated to the 64-bit network prefix, to yield a 128-fleck address. If the network prefix is smaller than 64 bits, more $.25 of the hash are used. If the resulting address does not disharmonize with existing or reserved addresses, it is assigned to the interface.

Default address selection [edit]

IPv6-enabled network interfaces unremarkably have more than i IPv6 address, for example, a link-local and a global address. They may also have temporary addresses that change after a certain lifetime has expired. IPv6 introduces the concepts of accost scope and selection preference, yielding multiple choices for source and destination address selections in communication with another host.

The preference selection algorithm published in RFC 6724 selects the nearly appropriate address to employ in communications with a particular destination, including the use of IPv4-mapped addresses in dual-stack implementations.[48] It uses a configurable preference table that associates each routing prefix with a precedence level. The default table has the following content:[48]

Prefix Precedence Characterization Usage
::1/128 l 0 Localhost
::/0 40 i Default unicast
::ffff:0:0/96 35 iv IPv4-mapped IPv6 address
2002::/16 30 2 6to4
2001::/32 5 v Teredo tunneling
fc00::/vii 3 13 Unique local address
::/96 ane iii IPv4-compatible addresses (deprecated)
fec0::/ten ane 11 Site-local address (deprecated)
3ffe::/16 i 12 6bone (returned)

The default configuration places preference on IPv6 usage, and selects destination addresses within the smallest possible scope, so that link-local communication is preferred over globally routed paths when otherwise every bit suitable. The prefix policy table is similar to a routing table, with the precedence value serving as the role of a link price, where higher preference is expressed every bit a larger value. Source addresses are preferred to take the same characterization value equally the destination address. Addresses are matched to prefixes based on the longest matching most-significant scrap-sequence. Candidate source addresses are obtained from the operating system and candidate destination addresses may exist queried via the Domain Name System (DNS).

For minimizing the fourth dimension of establishing connections when multiple addresses are available for communication, the Happy Eyeballs algorithm was devised. It queries the Domain Proper name Arrangement for IPv6 and IPv4 addresses of the target host, sorts candidate addresses using the default address option table, and tries to establish connections in parallel. The kickoff connection that is established aborts current and future attempts to connect to other addresses.

Domain Proper noun System [edit]

In the Domain Proper noun System, hostnames are mapped to IPv6 addresses by AAAA resources records, so-chosen quad-A records.[49] For reverse lookup the IETF reserved the domain ip6.arpa, where the name infinite is hierarchically divided by the 1-digit hexadecimal representation of nibble units (4 bits) of the IPv6 address.

As in IPv4, each host is represented in the DNS by two DNS records: an address record and a contrary mapping arrow record. For example, a host computer named derrick in zone example.com has the Unique Local Address fdda:5cc1:23:4::1f . Its quad-A accost record is 

          derrick.example.com.  IN  AAAA  fdda:5cc1:23:iv::1f

and its IPv6 pointer record is 

          f.1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.four.0.0.0.3.2.0.0.one.c.c.5.a.d.d.f.ip6.arpa.  IN  PTR   derrick.case.com.

This pointer tape may be divers in a number of zones, depending on the chain of delegation of authorisation in the zone d.f.ip6.arpa.

The DNS protocol is independent of its transport layer protocol. Queries and replies may be transmitted over IPv6 or IPv4 transports regardless of the address family unit of the information requested.

AAAA record fields
NAME Domain name
Type AAAA (28)
CLASS Internet (1)
TTL Fourth dimension to alive in seconds
RDLENGTH Length of RDATA field
RDATA 128-scrap IPv6 address, network byte order

Historical notes [edit]

Deprecated and obsolete addresses [edit]

  • The site-local prefix fec0:: / 10 specifies that the accost is valid just within the site network of an arrangement. It was function of the original addressing compages[50] in December 1995, but its use was deprecated in September 2004[51] because the definition of the term site was ambiguous, which led to disruptive routing rules. New networks must not support this special type of accost. In October 2005, a new specification[35] replaced this address type with unique local addresses.
  • The address block 200:: / 7 was divers as an OSI NSAP-mapped prefix set in August 1996,[52] [53] but was deprecated in December 2004.[54]
  • The 96-bit zilch-value prefix :: / 96 , originally known as IPv4-uniform addresses, was mentioned in 1995[50] but beginning described in 1998.[55] [ failed verification ] This range of addresses was used to represent IPv4 addresses inside an IPv6 transition engineering. Such an IPv6 accost has its first (most significant) 96 bits fix to zero, while its terminal 32 bits are the IPv4 address that is represented. In Feb 2006, the Internet Technology Task Force (IETF) deprecated the use of IPv4-compatible addresses.[one] The only remaining employ of this address format is to represent an IPv4 address in a table or database with fixed size members that must also be able to store an IPv6 address.
  • Address cake 3ffe:: / sixteen was allocated for test purposes for the 6bone network in December 1998.[55] Prior to that, the address block 5f00:: / 8 was used for this purpose. Both address blocks were returned to the address pool in June 2006.[56]
  • Due to operational problems with 6to4 the use of address block 2002:: / xvi is diminishing, since the 6to4 mechanism is deprecated since May 2015.[34] Although IPv4 address block 192.88.99.0 / 24 is deprecated, 2002:: / 16 is not.
  • In Apr 2007 the address block 2001:10:: / 28 was assigned for Overlay Routable Cryptographic Hash Identifiers (ORCHID).[57] Information technology was intended for experimental use. In September 2014 a second version of ORCHID was specified,[32] and with the introduction of block 2001:twenty:: / 28 the original cake was returned to IANA.

Miscellaneous [edit]

  • For reverse DNS lookup, IPv6 addresses were originally registered in the DNS zone ip6.int, because it was expected that the superlative-level domain arpa would be retired. In 2000, the Cyberspace Architecture Board (IAB) reverted this intention, and decided in 2001 that arpa should retain its original function. Domains in ip6.int were moved to ip6.arpa[58] and zone ip6.int was officially removed on 6 June 2006.
  • In March 2011, the IETF refined the recommendations for resource allotment of address blocks to end sites.[21] Instead of assigning either a / 48 , / 64 , or / 128 (according to IAB's and IESG'southward views of 2001),[59] Internet service providers should consider assigning smaller blocks (for example a / 56 ) to stop users. The ARIN, RIPE & APNIC regional registries' policies encourage / 56 assignments where appropriate.[21]
  • Originally, 2 proposals existed for translating domain names to IPv6 addresses: one using AAAA records,[60] the other using A6 records.[61] AAAA records, the method that prevailed, are comparable to A records for IPv4, providing a simple mapping from hostname to IPv6 accost. The method using A6 records used a hierarchical scheme, in which the mapping of subsequent groups of address bits was specified by additional A6 records, providing the possibility to renumber all hosts in a network by changing a single A6 record. Equally the perceived benefits of the A6 format were not accounted to outweigh the perceived costs,[62] [63] [64] [65] the method was moved to experimental status in 2002,[63] and finally to historic status in 2012.[65]
  • In 2009, many DNS resolvers in habitation-networking NAT devices and routers were found to handle AAAA records improperly.[66] Some of these simply dropped DNS requests for such records, instead of properly returning the appropriate negative DNS response. Because the asking is dropped, the host sending the request has to wait for a timeout to trigger. This often causes a slow-downwards when connecting to dual-stack IPv6/IPv4 hosts, equally the client software will look for the IPv6 connection to fail earlier trying IPv4.

Notes [edit]

  1. ^ A 16 chip or two octet quantity is sometimes also chosen a hextet.[6] [7]

References [edit]

  1. ^ a b c d e f g h i R. Hinden; S. Deering (Feb 2006). IP Version 6 Addressing Compages. Network Working Group. doi:ten.17487/RFC4291. RFC 4291. Updated by: RFC 5952, RFC 6052, RFC 7136, RFC 7346, RFC 7371, RFC 8064.
  2. ^ Silvia Hagen (May 2006). IPv6 Essentials (Second ed.). O'Reilly. ISBN978-0-596-10058-2.
  3. ^ a b P. Savola; B. Haberman (Nov 2004). Embedding the Rendezvous Signal (RP) Address in an IPv6 Multicast Accost. Network Working Group. doi:10.17487/RFC3956. RFC 3956.
  4. ^ a b B. Haberman; D. Thaler (August 2002). Unicast-Prefix-based IPv6 Multicast Addresses. Network Working Group. doi:10.17487/RFC3306. RFC 3306.
  5. ^ J-S. Park; M-M. Shin; H-J. Kim (Apr 2006). A Method for Generating Link-Scoped IPv6 Multicast Addresses. Network Working Grouping. doi:10.17487/RFC4489. RFC 4489.
  6. ^ Graziani, Rick (2012). IPv6 Fundamentals: A Straightforward Approach to Understanding IPv6. Cisco Press. p. 55. ISBN978-0-13-303347-2.
  7. ^ Coffeen, Tom (2014). IPv6 Accost Planning: Designing an Address Plan for the Hereafter. O'Reilly Media. p. 170. ISBN978-one-4919-0326-1.
  8. ^ S. Kawamura; M. Kawashima (August 2010). A Recommendation for IPv6 Address Text Representation. IETF. doi:x.17487/RFC5952. ISSN 2070-1721. RFC 5952.
  9. ^ T. Berners-Lee; R. Fielding; L. Masinter (January 2005). Compatible Resource Identifier (URI): Generic Syntax. Network Working Grouping. doi:10.17487/RFC3986. STD 66. RFC 3986.
  10. ^ a b Southward.Deering; B. Haberman; T. Jinmei; Eastward. Nordmark; B. Zill (March 2005). IPv6 Scoped Accost Compages. Network Working Group. doi:10.17487/RFC4007. RFC 4007.
  11. ^ B. Carpenter; S. Cheshire; R. Hinden (February 2013). Representing IPv6 Zone Identifiers in Address Literals and Compatible Resources Identifiers. IETF. doi:10.17487/RFC6874. RFC 6874. Updates RFC 3986.
  12. ^ "ipv6-literal.cyberspace Domain History". who.is. Retrieved xx October 2014.
  13. ^ "Scope zones". IBM Knowledge Centre. 27 September 2013. Retrieved 13 December 2019. Packets that comprise a source or destination address of a given scope tin can be routed only inside the same telescopic zone, and cannot exist routed between dissimilar scope zone instances.
  14. ^ R Droms (August 2014). IPv6 Multicast Accost Scopes. IETF. doi:ten.17487/RFC7346. ISSN 2070-1721. RFC 7346.
  15. ^ IPv6 Address Allocation Management. Network Working Group, IETF. December 1995. doi:10.17487/RFC1881. RFC 1881.
  16. ^ IPv6 address space at IANA. Iana.org (2010-10-29). Retrieved on 2011-09-28.
  17. ^ IPv6 unicast address assignments, IANA
  18. ^ DE-TELEKOM-20050113 db.ripe.cyberspace. Retrieved 2011-09-28.
  19. ^ "ARIN Number Resource Policy Transmission: Initial resource allotment to ISPs".
  20. ^ "RIPE NCC IPv6 Address Allocation and Assignment Policy: Minimum allotment".
  21. ^ a b c T. Narten; G. Houston; 50. Roberts (March 2011). IPv6 Address Assignment to Finish Sites. IETF. doi:ten.17487/RFC6177. BCP 157. RFC 6177.
  22. ^ for example. Iana.org. Retrieved on 2011-09-28.
  23. ^ "IPv6 Addressing Plans". ARIN IPv6 Wiki. Retrieved 2018-07-xv . All customers get one / 48 unless they can show that they need more than 65k subnets. [...] If you have lots of consumer customers you may want to assign / 56 s to private residence sites.
  24. ^ "What are Bogons?". Retrieved 2021-11-15 .
  25. ^ "Address Space Managed past the RIPE NCC". Retrieved 2011-05-22 .
  26. ^ D. Johnson; S. Deering (March 1999). Reserved IPv6 Subnet Anycast Addresses. Network Working Grouping. doi:10.17487/RFC2526. RFC 2526.
  27. ^ a b M. Cotton; 50. Vegoda; B. Haberman (Apr 2013). R. Bonica (ed.). Special-Purpose IP Address Registries. IETF. doi:10.17487/RFC6890. ISSN 2070-1721. BCP 153. RFC 6890. Obsoletes RFC 4773, 5156, 5735 and 5736. Updated past RFC 8190.
  28. ^ a b C. Bao; C. Huitema; M. Bagnulo; Thou. Boucadair; 10. Li (October 2010). IPv6 Addressing of IPv4/IPv6 Translators. Internet Engineering Task Forcefulness. doi:10.17487/RFC6052. RFC 6052.
  29. ^ a b T. Anderson (Baronial 2017). Local-Use IPv4/IPv6 Translation Prefix. Internet Applied science Task Force. doi:10.17487/RFC8215. RFC 8215.
  30. ^ a b Due north. Hilliard; D. Freedman (August 2012). A Discard Prefix for IPv6. Internet Engineering Task Force. doi:x.17487/RFC6666. RFC 6666.
  31. ^ RFC 4680
  32. ^ a b c J. Laganier; F. Dupont (September 2014). An IPv6 Prefix for Overlay Routable Cryptographic Hash Identifiers Version 2 (ORCHIDv2). Internet Engineering Task Force. doi:x.17487/RFC7343. RFC 7343.
  33. ^ a b G. Huston; A. Lord; P. Smith (July 2004). IPv6 Accost Prefix Reserved for Documentation. Network Working Group. doi:ten.17487/RFC3849. RFC 3849.
  34. ^ a b c O. Troan (May 2015). B. Carpenter (ed.). Deprecating the Anycast Prefix for 6to4 Relay Routers. Internet Engineering Task Force. doi:x.17487/RFC7526. BCP 196. RFC 7526.
  35. ^ a b c d R. Hinden; B. Haberman (October 2005). Unique Local IPv6 Unicast Addresses. Network Working Group. doi:10.17487/RFC4193. RFC 4193.
  36. ^ C. Bao; 10. Li; F. Baker; T. Anderson; F. Gont (June 2016). Stateless IP/ICMP Translation Algorithm. doi:10.17487/RFC7915. RFC 7915.
  37. ^ R. Hinden; S. Deering; R. Fink; T. Hain (September 2000). Initial IPv6 Sub-TLA ID Assignments. Network Working Group. doi:10.17487/RFC2928. RFC 2928.
  38. ^ C. Popoviciu; A. Hamza; G. Van de Velde; D. Dugatkin (May 2008). IPv6 Benchmarking Methodology for Network Interconnect Devices. Network Working Grouping. doi:10.17487/RFC5180. RFC 5180.
  39. ^ J. Arkko; M. Cotton; Fifty. Vegoda (January 2010). IPv4 Address Blocks Reserved for Documentation. Internet Engineering Task Strength. doi:ten.17487/RFC5737. ISSN 2070-1721. RFC 5737.
  40. ^ IANA Internet Protocol Version 6 Multicast Addresses.
  41. ^ S. Thomson; T. Narten; T. Jinmei (September 2007). IPv6 Stateless Accost Autoconfiguration. Network Working Group. doi:10.17487/RFC4862. RFC 4862.
  42. ^ T. Narten; East. Nordmark; W. Simpson; H. Holiman (September 2007). Neighbor Discovery for IP version 6 (IPv6). Network Working Group. doi:10.17487/RFC4861. RFC 4861.
  43. ^ Iljitsch van Beijnum (2006). "IPv6 Internals". The Internet Protocol Journal. Vol. 9, no. iii. pp. 16–29.
  44. ^ The privacy implications of stateless IPv6 addressing. Portal.acm.org (2010-04-21). Retrieved on 2011-09-28.
  45. ^ T. Narten; R. Draves; S. Krishnan (September 2007). Privacy Extensions for Stateless Address Autoconfiguration in IPv6. Network Working Group. doi:10.17487/RFC4941. RFC 4941.
  46. ^ T. Aura (March 2005). Cryptographically Generated Addresses (CGA). Network Working Group IETF. doi:10.17487/RFC3972. RFC 3972.
  47. ^ F. Gont (Apr 2014). A Method for Generating Semantically Opaque Interface Identifiers with IPv6 Stateless Address Autoconfiguration (SLAAC). IETF. doi:10.17487/RFC7217. ISSN 2070-1721. RFC 7217.
  48. ^ a b D. Thaler; R. Draves; A. Matsumoto; T. Chown (September 2012). D. Thaler (ed.). Default Address Selection for Internet Protocol Version 6 (IPv6). IETF. doi:10.17487/RFC6724. ISSN 2070-1721. RFC 6724.
  49. ^ S. Thomson; C. Huitema; V. Ksinant; M. Souissi (October 2003). DNS Extensions to Support IP Version vi. Network Working Grouping. doi:10.17487/RFC3596. RFC 3596.
  50. ^ a b R. Hinden; S. Deering (Dec 1995). IP Version 6 Addressing Architecture. Network Working Group. doi:ten.17487/RFC1884. RFC 1884.
  51. ^ C. Huitema; B. Carpenter (September 2004). Deprecating Site Local Addresses. Network Working Group. doi:x.17487/RFC3879. RFC 3879.
  52. ^ Chiliad. Houston (Aug 2005). Proposed Changes to the Format of the IANA IPv6 Registry. Network Working Group. doi:x.17487/RFC4147. RFC 4147.
  53. ^ J. Spring; B. Carpenter; D. Harrington; J. Houldsworth; A. Lloyd (Aug 1996). OSI NSAPs and IPv6. Network Working Group. doi:10.17487/RFC1888. RFC 1888. Obsoleted by RFC 4048.
  54. ^ B. Carpenter (Apr 2005). RFC 1888 Is Obsolete. doi:10.17487/RFC4048. RFC 4048.
  55. ^ a b R. Hinden; R. Fink; J. Postel (Dec 1998). IPv6 Testing Address Allocation. doi:10.17487/RFC2471. RFC 2471. Obsoleted by RFC 3701.
  56. ^ R. Fink; R. Hinden (Mar 2004). 6bone (IPv6 Testing Address Allocation) Phaseout. Network Working Grouping. doi:x.17487/RFC3701. RFC 3701.
  57. ^ P. Nikander; J. Laganier; F. Dupont (Apr 2007). An IPv6 Prefix for Overlay Routable Cryptographic Hash Identifiers (ORCHID). Network Working Group. doi:x.17487/RFC4843. RFC 4843.
  58. ^ R. Bush (Aug 2001). Delegation of IP6.ARPA. doi:10.17487/RFC3152. RFC 3152. Obsoleted by RFC 3596
  59. ^ IAB; IESG (September 2001). IAB/IESG Recommendations on IPv6 Address Allocations to Sites. doi:ten.17487/RFC3177. RFC 3177.
  60. ^ S. Thomson; C. Huitema (December 1995). DNS Extensions to support IP version 6. Network Working Group. doi:10.17487/RFC1886. RFC 1886. Obsoleted past RFC 3596.
  61. ^ M. Crawford; C. Huitema (July 2000). DNS Extensions to Support IPv6 Address Aggregation and Renumbering. doi:10.17487/RFC2874. RFC 2874.
  62. ^ Comparison of AAAA and A6 (do we really need A6?), Jun-ichiro itojun Hagino, (July 2001)
  63. ^ a b R. Bush; A. Durand; B. Fink; O. Gudmundsson; T. Hain (Baronial 2002). Representing Cyberspace Protocol version 6 (IPv6) Addresses in the Domain Name Organization (DNS). Network Working Group. doi:10.17487/RFC3363. RFC 3363. .
  64. ^ R. Austein (Baronial 2002). Tradeoffs in Domain Proper name System (DNS) Support for Cyberspace Protocol version half-dozen (IPv6). Network Working Group. doi:x.17487/RFC3364. RFC 3364.
  65. ^ a b South. Jiang; D. Conrad; B. Carpenter (March 2012). Moving A6 to Celebrated Status. IETF. doi:10.17487/RFC6536. RFC 6536.
  66. ^ Y. Morishita; T. Jinmei (May 2005). Mutual Misbehavior Confronting DNS Queries for IPv6 Addresses. doi:x.17487/RFC4074. RFC 4074.

External links [edit]

  • IP Version 6 multicast addresses
  • Beijnum, van, Iljitsch (2005). Running IPv6. ISBN978-1-59059-527-5.
  • Elz, Robert (1996-04-01). A Compact Representation of IPv6 Addresses (RFC1924). IETF. doi:10.17487/RFC1924. RFC 1924. Represent any IPv6 address in xx octets. This humorous RFC specifies an alternative way of representing IPv6 addresses, using a base-85 encoding.

hopwoodareat1994.blogspot.com

Source: https://en.wikipedia.org/wiki/IPv6_address

0 Response to "what is known as “one-to-nearest” addressing in ipv6?"

Post a Comment

Subscribe to: Post Comments (Atom)

Iklan Atas Artikel

Iklan Tengah Artikel 1

Iklan Tengah Artikel 2

Iklan Bawah Artikel