Editing Subnet (section)

==References==
{{Reflist|refs=
<ref name="rfc4291-2-5-1">{{Cite IETF
    | rfc        = 4291
    | title      = IP Version 6 Addressing Architecture - section 2.5.1. Interface Identifiers
    | publisher  = [[IETF]]
    | section    = 2.5.1
    | author1    = R. Hinden
    | author2    = S. Deering
    | authorlink2= Steve Deering
    | date       = February 2006
    | quote      = For all unicast addresses, except those that start with the binary value 000, Interface IDs are required to be 64 bits long and to be constructed in Modified EUI-64 format.
}} (Updated by RFC 5952, RFC 6052, RFC 7136, RFC 7346, RFC 7371, RFC 8064.)</ref>
<ref name="rfc4862">{{Cite IETF
    | rfc        = 4862
    | title      = IPv6 Stateless Address Autoconfiguration - section 5.5.3.(d) Router Advertisement Processing
    | publisher  = [[IETF]]
    | section    = 5.5.3
    | author1    = S. Thomson
    | author2    = T. Narten
    | author3    = T. Jinmei
    | quote      = It is the responsibility of the system administrator to ensure that the lengths of prefixes contained in Router Advertisements are consistent with the length of interface identifiers for that link type. [...] an implementation should not assume a particular constant. Rather, it should expect any lengths of interface identifiers.
    | date       = September 2007
}} (Updated by RFC 7527.)</ref>
<ref name="rfc2464">{{Cite IETF
    | rfc        = 2464
    | title      = Transmission of IPv6 Packets over Ethernet Networks - section 4 Stateless Autoconfiguration
    | publisher  = [[IETF]]
    | section    = 4
    | author    = M. Crawford
    | date       = December 1998
    | quote      = The Interface Identifier [AARCH] for an Ethernet interface is based on the EUI-64 identifier [EUI64] derived from the interface's built-in 48-bit IEEE 802 address. [...] An IPv6 address prefix used for stateless autoconfiguration [ACONF] of an Ethernet interface must have a length of 64 bits.
}} (Updated by RFC 6085, RFC 8064.)</ref>
<ref name="rfc6164">{{Cite IETF
    | rfc        = 6164
    | title      = Using 127-Bit IPv6 Prefixes on Inter-Router Links
    | publisher  = [[IETF]]
    | author1    = M. Kohno
    | author2    = B. Nitzan
    | author3    = R. Bush
    | author4    = Y. Matsuzaki
    | author5    = L. Colitti
    | author6    = T. Narten
    | date       = April 2011
    | quote      = On inter-router point-to-point links, it is useful, for security and other reasons, to use 127-bit IPv6 prefixes.
}}</ref>
<ref name="rfc6547">{{Cite IETF
    | rfc        = 6547
    | title      = RFC 3627 to Historic Status
    | author     = W. George
    | publisher  = [[IETF]]
    | date       = February 2012
    | quote      = This document moves "Use of /127 Prefix Length Between Routers Considered Harmful" (RFC 3627) to Historic status to reflect the updated guidance contained in "Using 127-Bit IPv6 Prefixes on Inter-Router Links" (RFC 6164).
}}</ref>
<ref name="rfc4291-2">{{Cite IETF
    | rfc        = 4291
    | title      = IP Version 6 Addressing Architecture - section 2 IPv6 Addressing
    | publisher  = [[IETF]]
    | section    = 2
    | author1    = R. Hinden
    | author2    = S. Deering
    | authorlink2= Steve Deering
    | date       = February 2006
    | quote      = There are no broadcast addresses in IPv6, their function being superseded by multicast addresses. [...] In IPv6, all zeros and all ones are legal values for any field, unless specifically excluded.
}}</ref>
<ref name="rfc4291-2-6-1">{{Cite IETF
    | rfc        = 4291
    | title      = IP Version 6 Addressing Architecture - section 2.6.1 Required Anycast Address
    | section    = 2.6.1
    | publisher  = [[IETF]]
    | author1    = R. Hinden
    | author2    = S. Deering
    | authorlink2= Steve Deering
    | date       = February 2006
    | quote      = This anycast address is syntactically the same as a unicast address for an interface on the link with the interface identifier set to zero.
}}</ref>
<ref name="ARIN">{{cite web
    | title      = IPv6 Addressing Plans
    | publisher      = ARIN IPv6 Wiki
    | url      = http://www.getipv6.info/index.php?title=IPv6_Addressing_Plans&oldid=2998
    | quote      = 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 /56s to private residence sites.
    | access-date      = 2010-04-25
    | archive-date      = 2010-04-26
    | archive-url      = https://web.archive.org/web/20100426161404/http://www.getipv6.info/index.php?title=IPv6_Addressing_Plans&oldid=2998
    | url-status      = live
    }}</ref>
<ref name="RFC 6177">{{Cite IETF
    | rfc        = 6177
    | bcp        = 157
    | title      = IPv6 Address Assignment to End Sites
    | author1    = T. Narten
    | author2    = G. Huston
    | author3    = L. Roberts
    | date       = March 2011
    | publisher  = [[IETF]]
    | issn       = 2070-1721
    | quote      = APNIC, ARIN, and RIPE have revised the end site assignment policy to encourage the assignment of smaller (i.e., /56) blocks to end sites.
}}</ref>
}}