Case Study: An ISP IPv6 Addressing Plan - RIPE 67 · Case Study: An ISP IPv6 Addressing Plan Yannis...

27
Case Study: Case Study: An ISP An ISP IPv6 Addressing Plan IPv6 Addressing Plan Yannis Nikolopoulos [email protected] RIPE 67, Athens - October 2013

Transcript of Case Study: An ISP IPv6 Addressing Plan - RIPE 67 · Case Study: An ISP IPv6 Addressing Plan Yannis...

Case Study: Case Study: An ISP An ISP

IPv6 Addressing PlanIPv6 Addressing PlanYannis Nikolopoulos [email protected]

RIPE 67, Athens - October 2013

Qualities of an (IPv6) Addressing PlanQualities of an (IPv6) Addressing Plan

Future-proof

Scalable

Sparing

Consistent

Produce easily aggregatable space

(security) Policy implementation should be made easy

S

Qualities of an (IPv6) Addressing PlanQualities of an (IPv6) Addressing Plan

Future-proof

Scalable

Sparing

Consistent

Produce easily aggregatable space

(security) Policy implementation should be made easy

Simple

Laying Some Ground RulesLaying Some Ground Rules

/29 allocation

Customers to get at least a /56 (except maybe in case of mobile)

No prefixes larger than /64 (special cases may arise)

t (sometimes too late)

Structure – Incorporating AspectsStructure – Incorporating Aspects

Location: City/PoP or terminating device (BRAS/BNG)

Service: internet access, VoIP, TV etc (QOS-friendly)

Traffic Type: trusted vs non-trusted

Incorporating Aspects - LocationIncorporating Aspects - Location

L L L L L L L L A A A A A A A A : A A A A A A A A x x x x x x x x

33 40 48 56

L: LocationA: Assignable

Incorporating Aspects - LocationIncorporating Aspects - Location

L L L L L L L L A A A A A A A A : A A A A A A A A x x x x x x x x

33 40 48 56

L: LocationA: Assignable

8 bits allowing for 256 locations

Incorporating Aspects - LocationIncorporating Aspects - Location

L L L L L L L L A A A A A A A A : A A A A A A A A x x x x x x x x

33 40 48 56

L: LocationA: Assignable

65k /56 per location(16 bits)

8 bits allowing for 256 locations

Incorporating Aspects - LocationIncorporating Aspects - Location

L L L L L L L L A A A A A A A A : A A A A A A A A x x x x x x x x

33 40 48 56

L: LocationA: Assignable

/56 subnet looks like:2a02:0585:LLAA:AAxx::/562a02:0585:LLAA:AAxx::/56

Example:

Athens:22 (00010110)2a02:585:2200::/40

Incorporating Aspects - ServiceIncorporating Aspects - Service

L L L L L L L L A A A A A A A A : A A A A A A A A S S S S S S S S

33 40 48 56

L: LocationA: AssignableS: Service

64

Incorporating Aspects - ServiceIncorporating Aspects - Service

L L L L L L L L A A A A A A A A : A A A A A A A A S S S S S S S S

33 40 48

L: LocationA: AssignableS: Service

64

8 bits allowing for 256 services

56

Incorporating Aspects - ServiceIncorporating Aspects - Service

33 40 48

L: LocationA: AssignableS: Service

64

8 bits allowing for 256 services

Multiple /64sper service possible(CPE customization)

L L L L L L L L A A A A A A A A : A A A A A A A A S S S S S S S S

56

Incorporating Aspects - ServiceIncorporating Aspects - Service

L L L L L L L L A A A A A A A A : A A A A A A A A S S S S S S S S

33 40 48

L: LocationA: AssignableS: Service

64

/64 subnet looks like:2a02:0585:LLAA:AASS::/642a02:0585:LLAA:AASS::/64

Example:

Internet access:01 (00000001)2a02:585:22xx:xx01::/64

56

Incorporating Aspects – Traffic TypeIncorporating Aspects – Traffic Type

33 40 48 56

T: Traffic TypeL: LocationA: AssignableS: Service

64

T T T L L L L L L L L A A A A A A A A : A A A A A A A A S S S S S S S S

Incorporating Aspects – Traffic TypeIncorporating Aspects – Traffic Type

T: Traffic TypeL: LocationA: AssignableS: Service

T T T L L L L L L L L A A A A A A A A : A A A A A A A A S S S S S S S S

● Split /29 into multiple /32● Use one /32 for infrastructure● Use many /32 for customers

33 40 48 56 64

Incorporating Aspects – Traffic TypeIncorporating Aspects – Traffic Type

T: Traffic TypeL: LocationA: AssignableS: Service

T T T L L L L L L L L A A A A A A A A : A A A A A A A A S S S S S S S S

● Split /29 into multiple /32● Use one /32 for infrastructure● Use many /32 for customers

33 40 48 56 64

Differentiate between Trusted and non-Trusted

Example:2a02:0587::/32 Trusted2a02:0580::/30 non-Trusted2a02:0584::/31 non-Trusted2a02:0586::/32 non-Trusted

Incorporating Aspects – Traffic TypeIncorporating Aspects – Traffic Type

T: Traffic TypeL: LocationA: AssignableS: Service

T T T L L L L L L L L A A A A A A A A : A A A A A A A A S S S S S S S S

33 40 48 56 64

subnet looks like:2a02:058T:LLAA:AASS::2a02:058T:LLAA:AASS::

Addressing CategoriesAddressing Categories

Customers' WANs

Customers' LANs

P-t-P Links

Loopbacks

VLANs

Addressing Categories – Users WANsAddressing Categories – Users WANs

Single IPv6 address (/128)

Single /64 (or /56) for each BNG/BRAS

Addressing Categories – Customers LANsAddressing Categories – Customers LANs

/56 Minimum

Up to Multiple /48s (w/ basic justification)

Addressing Categories – Customers LANsAddressing Categories – Customers LANs

Addressing Categories – Point-to-Point LinksAddressing Categories – Point-to-Point Links

Use /127 (rfc6164) from /64

A couple of /48s off a /40 (special location)

E

by their impact (sometimes too late)

Addressing Categories – Point-to-Point LinksAddressing Categories – Point-to-Point Links

Use /127 (rfc6164) from /64

A couple of /48s off a /40 (special location)

Example: Reserve location “de” and use “deaf” and “dead”

2a02:585:deaf::/48

2a02:585:dead::/48

by their impact (sometimes too late)

Addressing Categories – LoopbacksAddressing Categories – Loopbacks

/128 per loopback address

Use special location (e.g. “ff”)

Easy to differentiate between trusted/non-trusted

Addressing Categories – Infrastructure (V)LANsAddressing Categories – Infrastructure (V)LANs

Incorporate VLAN ID

Use the simplest way possible

Addressing Categories – Infrastructure (V)LANsAddressing Categories – Infrastructure (V)LANs

Incorporate VLAN ID

Use the simplest way possible

VLAN id IPv6 subnet

810 2a02:585:100:810::/64

35 2a02:585:100:35::/64

Thank You :)

Questions?