IPv6 Address Planning

WEBINAR COURSE

1 v1.0
Overview

• IPv6 Address Recap

• Address Planning
• ISP Infrastructure
• Enterprise Customer
• Broadband Customer
• Data Centre
• Address Planning – Traffic Shaping & Routing
• Example Address Plan

2 v1.0
IPv6 Address Recap
0 127
Network Prefix Interface ID

32

16

16
ISP /32
64
Customer Site /48

End Site Subnet /64

Device 128 Bit Address

3 v1.0
IPv6 Address Planning

• Network Operators allocated /32 by RIRs

• Global Routing prefix /48

o /56 (ISPs to end site)
o upstream could filter anything smaller
o Consider the routing table size!

4 v1.0
IPv6 Address Planning

• Future traffic engineering needs?

o Contiguous assignment vs Split assignment

• Shift in thought:
o IPv4: number of hosts
o IPv6: number of subnets!

5 v1.0
IPv6 Address Planning: ISP Infrastructure

• Loopbacks

• Point-to-Point links

• Internal Server LAN

o also called NOC LAN
o not seen from outside

• External Server LAN

o Mail, DNS, etc

6 v1.0
IPv6 Address Planning: ISP Infrastructure

• Dedicate a /40 (or /48) for the backbone infrastructure

o Every infrastructure assignment from this block!
o Carried by IGP (NOT iBGP)

• Loopbacks
o Generally one /48 (/60 and /64 also common) for all loopbacks
- /128 as each loopback address

• Point-to-Point links (e.g: one /48 for all P2P links)

o RFC6164 recommends /127
6164
- Reserve /64 per link but use /127

7 v1.0
IPv6 Address Planning: ISP Infrastructure

• Internal Server/NOC LAN

o /60 (if different subnets within the NOC), or
o /64

• External Server LAN

o /64 (allows up to 2^64 services to be hosted)

8 v1.0
IPv6 Address Planning: Enterprise Customer

• RFC6177:
o Obsoletes RFC3177 specification, which recommended end-sites should
get a /48 by default

o Suggests that end-sites are still given more than a /64 to allow for future
growth (multiple subnets)
- Multiples of /64, or better still
- /60, /56, or /52 (nibble boundaries)

6177

9 v1.0
IPv6 Address Planning: Enterprise Customer

• Consider regional delegation

o Aggregation in mind!
o /40 per region?

• One /48 per customer

o Could be transit customers or leased line customers
o Could be given additional /48s as they grow (more than 65K subnets)

• We also see ISPs give:

o /52 or /56 to mid-sized customers ()
o /60 for very small customers
o /64 to end-sites NOT recommended!!

10 v1.0
IPv6 Address Planning: Broadband Customer

• Depends on your deployment

o ND-RA for CPE WAN side
- A /64 prefix on BRAS can still support 2^64 CPEs through SLAAC

o DHCPv6-PD for CPE LAN side

- A /48 pool on each BRAS (65k /64s can be delegated)

• Dedicate a /40 (or bigger) for Broadband network

o /48s out of the /40 to each BRAS
o Announced in iBGP by BRAS

11 v1.0
IPv6 Address Planning: DC Services

• DC infrastructure blocks from your infrastructure block

o Loopbacks
o PtP links

• Dedicate /40 for DC (hosted) services

o Depends on DC architecture
o Dedicated VLAN/subnet per service?
- /64 per VLAN/subnet (2^64 servers)
o Dedicated subnet per customer (customer buys VMs/hosts services)?
- /64 per customer or subnet (2^64 VMs)
o Announced in iBGP (DC border router)

12 v1.0
IPv6 Address Planning: Traffic Shaping

• Borrow from IPv4

o Sub-aggregates to shape traffic
o Difficult with contiguous assignment

• Assign customer prefixes (that attract traffic) from both ends of

address space
o Infrastructure prefix do not attract traffic

13 v1.0
IPv6 Address Planning: Traffic Shaping
ISP/32

/33 /33

/34 /34 /34 /34

Customer 3 Customer 2 Customer 4

Customer 1 /48
/48 /48 /48

• Customer prefixes assigned from each /33 sub-prefix

o Similar to IPv4 sub-aggregates!
o Allows us to balance incoming traffic

14 v1.0
IPv6 Address Planning: Routing

• IGP to carry next-hop reachability information

o Infrastructure blocks (PtPs, loopbacks)
o Aggregation desirable in IGP

• Customer prefixes (Enterprise, broadband, DC customers/services)

o Sub-aggregates for traffic shaping (multihoming)
o Consider regional delegation
o iBGP carries all customer prefixes
- Aggregation may interfere with traffic shaping
o Aggregation necessary in eBGP (pull up routes)

15 v1.0
IPv6 Address Planning: Example
# Prefix Comments
• ISP has 2001:0db8::/32 prefix 1 2001:0db8:0000::/36
2 2001:0db8:1000::/36
o 16x /36s
3 2001:0db8:2000::/36
o easier to play at nibble boundaries 4 2001:0db8:3000::/36 First /33
5 2001:0db8:4000::/36
6 2001:0db8:5000::/36
7 2001:0db8:6000::/36
8 2001:0db8:7000::/36
9 2001:0db8:8000::/36
10 2001:0db8:9000::/36
11 2001:0db8:a000::/36
12 2001:0db8:b000::/36 Second /33
13 2001:0db8:c000::/36
14 2001:0db8:d000::/36
15 2001:0db8:e000::/36
16 2001:0db8:f000::/36

16 v1.0
Example: High Level Plan
# Prefix Assignment Comment
1 2001:0db8:0000::/36 Infrastructure +
Customer
2 2001:0db8:1000::/36
3 2001:0db8:2000::/36
First /33
4 2001:0db8:3000::/36
5 2001:0db8:4000::/36
6 2001:0db8:5000::/36
7 2001:0db8:6000::/36
8 2001:0db8:7000::/36 Customer
9 2001:0db8:8000::/36
10 2001:0db8:9000::/36
11 2001:0db8:a000::/36
12 2001:0db8:b000::/36
Second /33
13 2001:0db8:c000::/36
14 2001:0db8:d000::/36
15 2001:0db8:e000::/36
16 2001:0db8:f000::/36
17 v1.0
Example: High Level

# Prefix Assignment Comment

1 2001:0db8:0000::/36 Infrastructure + Customers
1 2001:0db8:0000:0000::/40 Backbone Infra (PtP, Loopbacks)
2 2001:0db8:0100:0000::/40 Enterprise Customer Reg1
3 2001:0db8:0200:0000::/40 Broadband Region1
4 2001:0db8:0300:0000::/40
5 2001:0db8:0400:0000::/40
First /33
6 2001:0db8:0500:0000::/40
7 2001:0db8:0600:0000::/40
Future Customers
:
:
:
:
16 2001:0db8:0f00:0000::/40

18 v1.0
Example: High Level

# Prefix Assignment Comments

9 2001:0db8:8000::/36 Customers
1 2001:0db8:8000::/40 Broadband Region2
2 2001:0db8:8100::/40 Enterprise Customer Reg2
3 2001:0db8:8200::/40
4 2001:0db8:8300::/40
5 2001:0db8:8400::/40
Second /33
6 2001:0db8:8500::/40
7 2001:0db8:8600::/40
Future Customers
:
:
:
:
16 2001:0db8:8f00::/40

19 v1.0
Example: Infrastructure

# Prefix Assignment Comments

1 2001:0db8:0000::/36 Infrastructure +
Customers
1 2001:0db8:0000::/40 Backbone Infrastructure
1 2001:0db8:0000::/48 Loopbacks
2 2001:0db8:0001::/48 Point-to-Point
3 2001:0db8:0002::/48
4 2001:0db8:0003::/48 First /33
5 2001:0db8:0004::/48
6 2001:0db8:0005::/48 Future Infra use
:
:
:
:
256 2001:0db8:00ff::/48

20 v1.0
Example: Customers

# Prefix Assignment Comments

1 2001:0db8:0000::/36 Infrastructure + Customers
2 2001:0db8:0100::/40 Enterprise Customer Reg1
1 2001:0db8:0100::/48 Customer WAN links
2 2001:0db8:0101::/48 Customer 1.1
3 2001:0db8:0102::/48 Customer 1.2
4 2001:0db8:0103::/48 First /33
5 2001:0db8:0104::/48 Future Customers
6 2001:0db8:0105::/48
7 2001:0db8:0106::/48
8 2001:0db8:0107::/48
:
:
256 2001:0db8:01ff::/48

21 v1.0
Example: Customers

# Prefix Assignment Comments

1 2001:0db8:0000::/36 Infrastructure + Customers
3 2001:0db8:0200::/40 Broadband Reg1
1 2001:0db8:0100::/48 BRAS 1
2 2001:0db8:0101::/48 BRAS 2
3 2001:0db8:0102::/48 BRAS 3
4 2001:0db8:0103::/48
First /33
5 2001:0db8:0104::/48
Future Customers
6 2001:0db8:0105::/48
7 2001:0db8:0106::/48
8 2001:0db8:0107::/48
:
:
256 2001:0db8:01ff::/48

22 v1.0
Example: Customers

# Prefix Assignment Comments

9 2001:0db8:8000::/36 Customers

1 2001:0db8:8000::/40 Broadband Reg2

1 2001:0db8:8000::/48 BRAS1

2 2001:0db8:8001::/48 BRAS2

3 2001:0db8:8002::/48 BRAS3 Second /33

4 2001:0db8:8003::/48

5 2001:0db8:8004::/48
Future BRAS
:

256 2001:0db8:80ff::/48

23 v1.0
Example: Customers

# Prefix Assignment Comments

9 2001:0db8:8000::/36 Customers

2 2001:0db8:8100::/40 Enterprise Customer Reg2

1 2001:0db8:8100::/48 Customer 2.1

2 2001:0db8:8101::/48 Customer 2.2

3 2001:0db8:8102::/48 Second /33

4 2001:0db8:8103::/48

5 2001:0db8:8104::/48
Future Customers
:

256 2001:0db8:81ff::/48

24 v1.0
IPv6@APNIC

25 v1.0
APNIC Helpdesk Chat

26 v1.0
Acknowledgements

Some materials used in this course were originated from the Cisco ISP/IXP
Workshop Programme developed by Philip Smith & Barry Greene.

All images and icons used on these slides, that include an APNIC
logo, are licensed or owned by APNIC.

27 v1.0