Address Space Allocation
This document describes the IP address plan we will use for this set of workshop exercises.
Wherever possible the plan tries to replicate real life as closely as possible.
The IPv4 address space used in these exercises is from subnets of 100.64.0.0/10 which is an [IPv4 Shared Address](https://tools.ietf.org/html/rfc6598) block. It must not be routed on the Internet.
Note that 2001:DB8::/32 is the [IPv6 Documentation Address](https://tools.ietf.org/html/rfc3849) block. It must not be routed on the Internet.
And finally note that the 2001:10::/28 address block has been listed in the [IANA special registry](http://www.iana.org/assignments/iana-ipv6-special-registry/iana-ipv6-special-registry.xhtml) for future use. It must not be routed on the Internet.
If using these labs as inspiration for your own infrastructure design, please replace all instances of private, documentation, and unassigned address space with your own address blocks.
If they are not a Regional Internet Registry member, end-site networks typically will receive a public IPv6 /48 and a very small public IPv4 block from their network operator.
We will use an IPv4 /24 for these exercises, reflecting the fact that in reality an end-site organisation will use a large private block like a /16 internally, NATed out into a small public IPv4 block like the /24 we are using here.
*The list will continue in the same pattern if there are more groups.*
Each group will then further partition their space as follows:
|100.68.X.0/24||2001:DB8:X::/48||Group address block|
|100.68.X.64/26||2001:DB8:X:4000::/50||End user space 1|
|100.68.X.128/26||2001:DB8:X:8000::/50||End user space 2|
|100.68.X.192/26||2001:DB8:X:C000::/50||End user space 3|
Where X is your group number (1,2,3…).
Prefixes for point-to-point links will be of length /30 for IPv4 and /127 for IPv6 (we will adopt the recommendations of [RFC6164](https://tools.ietf.org/html/rfc6164) for IPv6 inter-router links where we reserve a /64 for the link but subnet it as a /127):
|100.68.X.16/30||2001:DB8:X:10::/127||P2P CX ↔ BX|
|100.68.X.20/30||2001:DB8:X:11::/127||P2P CX ↔ PX|
|100.68.X.24/30||2001:DB8:X:12::/127||P2P CX ↔ AX|
|100.68.X.32/30||2001:DB8:X:20::/127||P2P AX ↔ CustX|
Router loopback address subnet masks will be /32 for IPv4 and /128 for IPv6:
Note that the convention used here assigns the beginning of the IPv4 and IPv6 address space for use for infrastructure. This is generally a matter of choice: some network operators use the beginning of the space, others use the end of the space.
Commercial network operators receive at minimum an IPv6 /32 from their regional internet registry. IPv4 allocations can range upwards from /22. We will use an IPv4 /16 for our exercises.
The point-to-point link addresses from Transit Providers 1 and 2 to the End-sites are listed next. Note that the Transit Providers will get the low address, and the end-site gets the high address in the subnet.
Note: The numbering started at the second /24 for the IPv4 point-to-point links to “end customers”. The first /24 is kept for number infrastructure within the ISP, for example: loopbacks, internal point-to-point links, etc. The same applies to IPv6, where the first sixteen /64s were kept for loopbacks (the first /64) and internal point-to-point links (the next fifteen /64s).
The address for the point to point link between Regional ISP 1 and Regional ISP 2 is given in this table:
|Transit 1 to Transit 2||100.121.0.0/30||2001:18:0:0::/127|
The following diagram shows the address plan as implemented in the lab topology.