Subnet

A subnetwork or subnet is a logical subdivision of an IP net work.[1]: 1, 16 The pract ice of dividing
a net work int o t wo or more net works is called subnetting.

Creating a subnet by dividing the host identifier

Comput ers t hat belong t o t he same subnet are addressed wit h an ident ical group of it s most -
significant bit s of t heir IP addresses. This result s in t he logical division of an IP address int o t wo
fields: t he network number or routing prefix, and t he rest field or host identifier. The rest field is an
ident ifier for a specific host or net work int erface.

The routing prefix may be expressed as t he first address of a net work, writ t en in Classless Int er-
Domain Rout ing (CIDR) not at ion, followed by a slash charact er (/), and ending wit h t he bit -lengt h
of t he prefix. For example, 198.51.100.0/24 is t he prefix of t he Int ernet Prot ocol version 4
net work st art ing at t he given address, having 24 bit s allocat ed for t he net work prefix, and t he
remaining 8 bit s reserved for host addressing. Addresses in t he range 198.51.100.0 t o
198.51.100.255 belong t o t his net work, wit h 198.51.100.255 as t he subnet broadcast address.
The IPv6 address specificat ion 2001:db8::/32 is a large address block wit h 296 addresses, having
a 32-bit rout ing prefix.

For IPv4, a net work may also be charact erized by it s subnet mask or netmask, which is t he
bit mask t hat , when applied by a bit wise AND operat ion t o any IP address in t he net work, yields
t he rout ing prefix. Subnet masks are also expressed in dot -decimal not at ion like an IP address.
For example, t he prefix 198.51.100.0/24 would have t he subnet mask 255.255.255.0.

Traffic is exchanged bet ween subnet s t hrough rout ers when t he rout ing prefixes of t he source
address and t he dest inat ion address differ. A rout er serves as a logical or physical boundary
bet ween t he subnet s.

The benefit s of subnet t ing an exist ing net work vary wit h each deployment scenario. In t he
address allocat ion archit ect ure of t he Int ernet using CIDR and in large organizat ions, efficient
allocat ion of address space is necessary. Subnet t ing may also enhance rout ing efficiency, or have
advant ages in net work management when subnet s are administ rat ively cont rolled by different
ent it ies in a larger organizat ion. Subnet s may be arranged logically in a hierarchical archit ect ure,
part it ioning an organizat ion's net work address space int o a t ree-like rout ing st ruct ure, or ot her
st ruct ures, such as meshes.

Network addressing and

routing

The concept of subnetting the IPv4 address space 200.100.10.0/24,

which contains 256 addresses, into two smaller address spaces,
namely 200.100.10.0/25 and 200.100.10.128/25 with 128 addresses
each

Comput ers part icipat ing in an IP net work have at least one net work address. Usually, t his
address is unique t o each device and can eit her be configured aut omat ically by a net work service
wit h t he Dynamic Host Configurat ion Prot ocol (DHCP), manually by an administ rat or, or
aut omat ically by t he operat ing syst em wit h st at eless address aut oconfigurat ion.

An address fulfills t he funct ions of ident ifying t he host and locat ing it on t he net work in
dest inat ion rout ing. The most common net work addressing archit ect ure is Int ernet Prot ocol
version 4 (IPv4), but it s successor, IPv6, has been increasingly deployed since approximat ely
2006. An IPv4 address consist s of 32 bit s. An IPv6 address consist s of 128 bit s. In bot h
archit ect ures, an IP address is divided int o t wo logical part s, t he network prefix and t he host
identifier. All host s on a subnet have t he same net work prefix. This prefix occupies t he most -
significant bit s of t he address. The number of bit s allocat ed wit hin a net work t o t he prefix may
vary bet ween subnet s, depending on t he net work archit ect ure. The host ident ifier is a unique
local ident ificat ion and is eit her a host number on t he local net work or an int erface ident ifier.

This addressing st ruct ure permit s t he select ive rout ing of IP packet s across mult iple net works
via special gat eway comput ers, called rout ers, t o a dest inat ion host if t he net work prefixes of
originat ion and dest inat ion host s differ, or sent direct ly t o a t arget host on t he local net work if
t hey are t he same. Rout ers const it ut e logical or physical borders bet ween t he subnet s, and
manage t raffic bet ween t hem. Each subnet is served by a designat ed default rout er but may
consist int ernally of mult iple physical Et hernet segment s int erconnect ed by net work swit ches.

The rout ing prefix of an address is ident ified by t he subnet mask, writ t en in t he same form used
for IP addresses. For example, t he subnet mask for a rout ing prefix t hat is composed of t he
most -significant 24 bit s of an IPv4 address is writ t en as 255.255.255.0.

The modern st andard form of specificat ion of t he net work prefix is CIDR not at ion, used for bot h
IPv4 and IPv6. It count s t he number of bit s in t he prefix and appends t hat number t o t he address
aft er a slash (/) charact er separat or. This not at ion was int roduced wit h Classless Int er-Domain
Rout ing (CIDR).[2] In IPv6 t his is t he only st andards-based form t o denot e net work or rout ing
prefixes.

For example, t he IPv4 net work 192.0.2.0 wit h t he subnet mask 255.255.255.0 is writ t en as
192.0.2.0/24, and t he IPv6 not at ion 2001:db8::/32 designat es t he address 2001:db8:: and it s
net work prefix consist ing of t he most significant 32 bit s.

In classful net working in IPv4, before t he int roduct ion of CIDR, t he net work prefix could be
direct ly obt ained from t he IP address, based on it s highest -order bit sequence. This det ermined
t he class (A, B, C) of t he address and t herefore t he subnet mask. Since t he int roduct ion of CIDR,
however, t he assignment of an IP address t o a net work int erface requires t wo paramet ers, t he
address and a subnet mask.

Given an IPv4 source address, it s associat ed subnet mask, and t he dest inat ion address, a rout er
can det ermine whet her t he dest inat ion is on a locally connect ed net work or a remot e net work.
The subnet mask of t he dest inat ion is not needed, and is generally not known t o a rout er.[3] For
IPv6, however, on-link det erminat ion is different in det ail and requires t he Neighbor Discovery
Prot ocol (NDP).[4][5] IPv6 address assignment t o an int erface carries no requirement of a
mat ching on-link prefix and vice versa, wit h t he except ion of link-local addresses.

Since each locally connect ed subnet must be represent ed by a separat e ent ry in t he rout ing
t ables of each connect ed rout er, subnet t ing increases rout ing complexit y. However, by careful
design of t he net work, rout es t o collect ions of more dist ant subnet s wit hin t he branches of a
t ree hierarchy can be aggregat ed int o a supernet work and represent ed by single rout es.

Internet Protocol version 4

Determining the network prefix

An IPv4 subnet mask consist s of 32 bit s; it is a sequence of ones (1) followed by a block of
zeros (0). The ones indicat e bit s in t he address used for t he net work prefix and t he t railing block
of zeros designat es t hat part as being t he host ident ifier.

The following example shows t he separat ion of t he net work prefix and t he host ident ifier from
an address (192.0.2.130) and it s associat ed /24 subnet mask (255.255.255.0). The operat ion is
visualized in a t able using binary address format s.
 Binary form Dot-decimal notation

IP address 11000000.00000000.00000010.10000010 192.0.2.130

Subnet mask 11111111.11111111.11111111.00000000 255.255.255.0

Net work prefix 11000000.00000000.00000010.00000000 192.0.2.0

Host ident ifier 00000000.00000000.00000000.10000010 0.0.0.130

The result of t he bit wise AND operat ion of IP address and t he subnet mask is t he net work prefix
192.0.2.0. The host part , which is 130, is derived by t he bit wise AND operat ion of t he address
and t he ones' complement of t he subnet mask.

Subnetting
Subnet t ing is t he process of designat ing some high-order bit s from t he host part as part of t he
net work prefix and adjust ing t he subnet mask appropriat ely. This divides a net work int o smaller
subnet s. The following diagram modifies t he above example by moving 2 bit s from t he host part
t o t he net work prefix t o form four smaller subnet s each one quart er of t he previous size.

Binary form Dot-decimal notation

IP address 11000000.00000000.00000010.10000010 192.0.2.130

Subnet mask 11111111.11111111.11111111.11000000 255.255.255.192

Net work prefix 11000000.00000000.00000010.10000000 192.0.2.128

Host part 00000000.00000000.00000000.00000010 0.0.0.2

Special addresses and subnets

IPv4 uses specially designat ed address format s t o facilit at e recognit ion of special address
funct ionalit y. The first and t he last subnet s obt ained by subnet t ing a larger net work have
t radit ionally had a special designat ion and, early on, special usage implicat ions.[6] In addit ion, IPv4
uses t he all ones host address, i.e. t he last address wit hin a net work, for broadcast t ransmission
t o all host s on t he link.

The first subnet obt ained from subnet t ing a larger net work has all bit s in t he subnet bit group
set t o zero. It is t herefore called subnet zero.[7] The last subnet obt ained from subnet t ing a
larger net work has all bit s in t he subnet bit group set t o one. It is t herefore called t he all-ones
subnet.[8]

The IETF originally discouraged t he product ion use of t hese t wo subnet s. When t he prefix lengt h
is not available, t he larger net work and t he first subnet have t he same address, which may lead t o
confusion. Similar confusion is possible wit h t he broadcast address at t he end of t he last subnet .
Therefore, reserving t he subnet values consist ing of all zeros and all ones on t he public Int ernet
was recommended,[9] reducing t he number of available subnet s by t wo for each subnet t ing. This
inefficiency was removed, and t he pract ice was declared obsolet e in 1995 and is only relevant
when dealing wit h legacy equipment .[10]

Alt hough t he all-zeros and t he all-ones host values are reserved for t he net work address of t he
subnet and it s broadcast address, respect ively, in syst ems using CIDR all subnet s are available in
a subdivided net work. For example, a /24 net work can be divided int o sixt een usable /28
net works. Each broadcast address, i.e. *.15, *.31, …, *.255, reduces only t he host count in each
subnet s.

Subnet host count

The number of subnet s available and t he number of possible host s in a net work may be readily
calculat ed. For inst ance, t he 192.168.5.0/24 net work may be subdivided int o t he following four
/26 subnet s. The highlight ed t wo address bit s become part of t he net work number in t his
process.
 Network Network (binary) Broadcast address

192.168.5.0/26 11000000.10101000.00000101.00000000 192.168.5.63

192.168.5.64/26 11000000.10101000.00000101.01000000 192.168.5.127

192.168.5.128/26 11000000.10101000.00000101.10000000 192.168.5.191

192.168.5.192/26 11000000.10101000.00000101.11000000 192.168.5.255

The remaining bit s aft er t he subnet bit s are used for addressing host s wit hin t he subnet . In t he
above example, t he subnet mask consist s of 26 bit s, making it 255.255.255.192, leaving 6 bit s
for t he host ident ifier. This allows for 62 host combinat ions (26−2).

In general, t he number of available host s on a subnet is 2h−2, where h is t he number of bit s used
for t he host port ion of t he address. The number of available subnet s is 2n, where n is t he number
of bit s used for t he net work port ion of t he address.

There is an except ion t o t his rule for 31-bit subnet masks,[11] which means t he host ident ifier is
only one bit long for t wo permissible addresses. In such net works, usually point -t o-point links,
only t wo host s (t he endpoint s) may be connect ed and a specificat ion of net work and broadcast
addresses is not necessary.
Subnet masks and IP Addresses
Mask IP Addresses Hosts Netmask

/31 2 2 255.255.255.254

/30 4 2 255.255.255.252

/29 8 6 255.255.255.248

/28 16 14 255.255.255.240

/27 32 30 255.255.255.224

/26 64 62 255.255.255.192

/25 128 126 255.255.255.128

/24 256 254 255.255.255.0

/23 512 510 255.255.254.0

/22 1024 1022 255.255.252.0

/21 2048 2046 255.255.248.0

/20 4096 4094 255.255.240.0

/19 8192 8190 255.255.224.0

/18 16384 16382 255.255.192.0

/17 32768 32766 255.255.128.0

/16 65536 65534 255.255.0.0

Internet Protocol version 6

The design of t he IPv6 address space differs significant ly from IPv4. The primary reason for
subnet t ing in IPv4 is t o improve efficiency in t he ut ilizat ion of t he relat ively small address space
available, part icularly t o ent erprises. No such limit at ions exist in IPv6, as t he large address space
available, even t o end-users, is not a limit ing fact or.

As in IPv4, subnet t ing in IPv6 is based on t he concept s of variable-lengt h subnet masking

(VLSM) and t he Classless Int er-Domain Rout ing met hodology. It is used t o rout e t raffic bet ween
t he global allocat ion spaces and wit hin cust omer net works bet ween subnet s and t he Int ernet at
large.

A compliant IPv6 subnet always uses addresses wit h 64 bit s in t he host ident ifier.[12] Given t he
address size of 128 bit s, it t herefore has a /64 rout ing prefix. Alt hough it is t echnically possible
t o use smaller subnet s,[13] t hey are impract ical for local area net works based on Et hernet
t echnology, because 64 bit s are required for st at eless address aut oconfigurat ion.[14] The
Int ernet Engineering Task Force recommends t he use of /127 subnet s for point -t o-point links,
which have only t wo host s.[15][16]

IPv6 does not implement special address format s for broadcast t raffic or net work numbers,[17]
and t hus all addresses in a subnet are accept able for host addressing. The all-zeroes address is
reserved as t he subnet -rout er anycast address.[18] The subnet rout er anycast address is t he
lowest address in t he subnet , so it looks like t he “net work address”. If a rout er has mult iple
subnet s on t he same link, t hen it has mult iple subnet rout er anycast addresses on t hat link.[19]
The first and last address in any net work or subnet is not allowed t o be assigned t o any individual
host .

In t he past , t he recommended allocat ion for an IPv6 cust omer sit e was an address space wit h a
48-bit (/48) prefix.[20] However, t his recommendat ion was revised t o encourage smaller blocks,
for example using 56-bit prefixes.[21] Anot her common allocat ion size for resident ial cust omer
net works has a 64-bit prefix.

See also

Autonomous system (Internet)

Network segmentation
References

1. Jeffrey Mogul; Jon Postel (August 1985).

Internet Standard Subnetting Procedure (htt
ps://datatracker.ietf.org/doc/html/rfc950) .
IETF. doi:10.17487/RFC0950 (https://doi.or
g/10.17487%2FRFC0950) . RFC 950 (http
s://datatracker.ietf.org/doc/html/rfc950) .
Updated by RFC 6918.
2. V. Fuller; T. Li (August 2006). Classless
Inter-domain Routing (CIDR): The Internet
Address Assignment and Aggregation Plan
(https://datatracker.ietf.org/doc/html/rfc46
32) . Network Working Group.
doi:10.17487/RFC4632 (https://doi.org/10.
17487%2FRFC4632) . RFC 4632 (https://da
tatracker.ietf.org/doc/html/rfc4632) .
3. R. Braden, ed. (October 1989).
Requirements for Internet Hosts --
Communication Layers (https://datatracker.
ietf.org/doc/html/rfc1122#section-3.3.1) .
Network Working Group IETF. sec. 3.3.1.
doi:10.17487/RFC1122 (https://doi.org/10.
17487%2FRFC1122) . RFC 1122 (https://da
tatracker.ietf.org/doc/html/rfc1122) .
Updated by RFC 1349, RFC 4379, RFC 5884,
RFC 6093, RFC 6298, RFC 6633, RFC 6864,
RFC 8029.
4. T. Narten; E. Nordmark; W. Simpson; H.
Soliman (September 2007). Neighbor
Discovery for IP version 6 (IPv6) (https://da
tatracker.ietf.org/doc/html/rfc4861) .
Network Working Group.
doi:10.17487/RFC4861 (https://doi.org/10.
17487%2FRFC4861) . RFC 4861 (https://da
tatracker.ietf.org/doc/html/rfc4861) .
5. H. Singh; W. Beebee; E. Nordmark (July
2010). IPv6 Subnet Model: The
Relationship between Links and Subnet
Prefixes (https://datatracker.ietf.org/doc/ht
ml/rfc5942) . IETF. doi:10.17487/RFC5942
(https://doi.org/10.17487%2FRFC5942) .
RFC 5942 (https://datatracker.ietf.org/doc/
html/rfc5942) .
6. "Document ID 13711 - Subnet Zero and the
All-Ones Subnet" (http://www.cisco.com/e
n/US/tech/tk648/tk361/technologies_tech_
note09186a0080093f18.shtml) . Cisco
Systems. 2005-08-10. Archived (https://we
b.archive.org/web/20140209020855/htt
p://www.cisco.com/en/US/tech/tk648/tk36
1/technologies_tech_note09186a0080093f
18.shtml) from the original on 2014-02-09.
Retrieved 2010-04-25. "Traditionally, it was
strongly recommended that subnet zero
and the all-ones subnet not be used for
addressing. [...] Today, the use of subnet
zero and the all-ones subnet is generally
accepted and most vendors support their
use."
7. "Document ID 13711 - Subnet Zero and the
All-Ones Subnet" (http://www.cisco.com/e
n/US/tech/tk648/tk361/technologies_tech_
note09186a0080093f18.shtml) . Cisco
Systems. 2005-08-10. Archived (https://we
b.archive.org/web/20140209020855/htt
p://www.cisco.com/en/US/tech/tk648/tk36
1/technologies_tech_note09186a0080093f
18.shtml) from the original on 2014-02-09.
Retrieved 2010-04-23. "the first [...]
subnet[...], known as subnet zero"
8. "Document ID 13711 - Subnet Zero and the
All-Ones Subnet" (http://www.cisco.com/e
n/US/tech/tk648/tk361/technologies_tech_
note09186a0080093f18.shtml) . Cisco
Systems. 2005-08-10. Archived (https://we
b.archive.org/web/20140209020855/htt
p://www.cisco.com/en/US/tech/tk648/tk36
1/technologies_tech_note09186a0080093f
18.shtml) from the original on 2014-02-09.
Retrieved 2010-04-23. "[...] the last
subnet[...], known as [...] the all-ones
subnet"
9. Jeffrey Mogul; Jon Postel (August 1985).
Internet Standard Subnetting Procedure (htt
ps://datatracker.ietf.org/doc/html/rfc950#
page-6) . IETF. p. 6. doi:10.17487/RFC0950
(https://doi.org/10.17487%2FRFC0950) .
RFC 950 (https://datatracker.ietf.org/doc/ht
ml/rfc950) . "It is useful to preserve and
extend the interpretation of these special
addresses in subnetted networks. This
means the values of all zeros and all ones
in the subnet field should not be assigned
to actual (physical) subnets."
10. Troy Pummill; Bill Manning (December
1995). Variable Length Subnet Table For
IPv4 (https://datatracker.ietf.org/doc/html/
rfc1878) . IETF. doi:10.17487/RFC1878 (htt
ps://doi.org/10.17487%2FRFC1878) . RFC
1878 (https://datatracker.ietf.org/doc/htm
l/rfc1878) . "This practice is obsolete!
Modern software will be able to utilize all
definable networks." (Informational RFC,
demoted to category Historic)
11. A. Retana; R. White; V. Fuller; D. McPherson
(December 2000). Using 31-Bit Prefixes on
IPv4 Point-to-Point Links (https://datatrack
er.ietf.org/doc/html/rfc3021) .
doi:10.17487/RFC3021 (https://doi.org/10.
17487%2FRFC3021) . RFC 3021 (https://da
tatracker.ietf.org/doc/html/rfc3021) .
12. R. Hinden; S. Deering (February 2006). IP
Version 6 Addressing Architecture - section
2.5.1. Interface Identifiers (https://datatrack
er.ietf.org/doc/html/rfc4291#section-2.5.
1) . IETF. sec. 2.5.1.
doi:10.17487/RFC4291 (https://doi.org/10.
17487%2FRFC4291) . RFC 4291 (https://da
tatracker.ietf.org/doc/html/rfc4291) . "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.)
13. S. Thomson; T. Narten; T. Jinmei
(September 2007). IPv6 Stateless Address
Autoconfiguration - section 5.5.3.(d) Router
Advertisement Processing (https://datatrac
ker.ietf.org/doc/html/rfc4862#section-5.5.
3) . IETF. sec. 5.5.3.
doi:10.17487/RFC4862 (https://doi.org/10.
17487%2FRFC4862) . RFC 4862 (https://da
tatracker.ietf.org/doc/html/rfc4862) . "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." (Updated by RFC 7527.)
14. M. Crawford (December 1998).
Transmission of IPv6 Packets over Ethernet
Networks - section 4 Stateless
Autoconfiguration (https://datatracker.ietf.o
rg/doc/html/rfc2464#section-4) . IETF.
sec. 4. doi:10.17487/RFC2464 (https://doi.
org/10.17487%2FRFC2464) . RFC 2464 (ht
tps://datatracker.ietf.org/doc/html/rfc246
4) . "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.)
15. M. Kohno; B. Nitzan; R. Bush; Y. Matsuzaki;
L. Colitti; T. Narten (April 2011). Using 127-
Bit IPv6 Prefixes on Inter-Router Links (http
s://datatracker.ietf.org/doc/html/rfc6164) .
IETF. doi:10.17487/RFC6164 (https://doi.or
g/10.17487%2FRFC6164) . RFC 6164 (http
s://datatracker.ietf.org/doc/html/rfc6164) .
"On inter-router point-to-point links, it is
useful, for security and other reasons, to
use 127-bit IPv6 prefixes."
16. W. George (February 2012). RFC 3627 to
Historic Status (https://datatracker.ietf.org/
doc/html/rfc6547) . IETF.
doi:10.17487/RFC6547 (https://doi.org/10.
17487%2FRFC6547) . RFC 6547 (https://da
tatracker.ietf.org/doc/html/rfc6547) . "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)."
17. R. Hinden; S. Deering (February 2006). IP
Version 6 Addressing Architecture - section
2 IPv6 Addressing (https://datatracker.ietf.
org/doc/html/rfc4291#section-2) . IETF.
sec. 2. doi:10.17487/RFC4291 (https://doi.
org/10.17487%2FRFC4291) . RFC 4291 (ht
tps://datatracker.ietf.org/doc/html/rfc429
1) . "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."
18. R. Hinden; S. Deering (February 2006). IP
Version 6 Addressing Architecture - section
2.6.1 Required Anycast Address (https://da
tatracker.ietf.org/doc/html/rfc4291#sectio
n-2.6.1) . IETF. sec. 2.6.1.
doi:10.17487/RFC4291 (https://doi.org/10.
17487%2FRFC4291) . RFC 4291 (https://da
tatracker.ietf.org/doc/html/rfc4291) . "This
anycast address is syntactically the same
as a unicast address for an interface on the
link with the interface identifier set to zero."
19. "Subnet Router Anycast Addresses – what
are they, how do they work? – Into6" (http
s://into6.com.au/2014/03/30/subnet-route
r-anycast-addresses-what-are-they-how-do-
they-work/) . 30 March 2014. Archived (htt
ps://web.archive.org/web/2022070205422
0/https://into6.com.au/2014/03/30/subnet
-router-anycast-addresses-what-are-they-ho
w-do-they-work/) from the original on
2022-07-02. Retrieved 2022-06-09.
20. "IPv6 Addressing Plans" (http://www.getipv
6.info/index.php?title=IPv6_Addressing_Pla
ns&oldid=2998) . ARIN IPv6 Wiki. Archived
(https://web.archive.org/web/2010042616
1404/http://www.getipv6.info/index.php?tit
le=IPv6_Addressing_Plans&oldid=2998)
from the original on 2010-04-26. Retrieved
2010-04-25. "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."
21. T. Narten; G. Huston; L. Roberts (March
2011). IPv6 Address Assignment to End
Sites (https://datatracker.ietf.org/doc/html/
rfc6177) . IETF. doi:10.17487/RFC6177 (htt
ps://doi.org/10.17487%2FRFC6177) .
ISSN 2070-1721 (https://www.worldcat.or
g/issn/2070-1721) . BCP 157. RFC 6177 (h
ttps://datatracker.ietf.org/doc/html/rfc617
7) . "APNIC, ARIN, and RIPE have revised
the end site assignment policy to
encourage the assignment of smaller (i.e.,
/56) blocks to end sites."

Further reading

Requirements for IPv4 Wikiversity

has
Routers (https://datatra
learning
resources
cker.ietf.org/doc/html/ about
Subnetting
rfc1812) .
doi:10.17487/RFC1812 (https://doi.org/
10.17487%2FRFC1812) . RFC 1812 (http
s://datatracker.ietf.org/doc/html/rfc181
2) .
Utility of subnets of Internet networks (htt
ps://datatracker.ietf.org/doc/html/rfc91
7) . doi:10.17487/RFC0917 (https://doi.
org/10.17487%2FRFC0917) . RFC 917
(https://datatracker.ietf.org/doc/html/rf
c917) .
DNS Encodings of Network Names and
Other Type (https://datatracker.ietf.org/
doc/html/rfc1101) .
doi:10.17487/RFC1101 (https://doi.org/
10.17487%2FRFC1101) . RFC 1101 (http
s://datatracker.ietf.org/doc/html/rfc110
1) .
Blank, Andrew G. (2006). TCP/IP
Foundations. Wiley.
ISBN 9780782151138.
Lammle, Todd (2005). CCNA Cisco
Certified Network Associate Study Guide
5th Edition. San Francisco, London:
Sybex.
Groth, David; Skandier, Toby (2005).
Network + Study Guide (4th ed.). San
Francisco, London: Wiley.
Retrieved from
"https://en.wikipedia.org/w/index.php?
title=Subnet&oldid=1214407216"

This page was last edited on 18 March 2024, at

19:39 (UTC). •
Content is available under CC BY-SA 4.0 unless
otherwise noted.