IPv6 for LIRs & the Routing Registry ENOG/RIPE NCC Regional Meeting June 2011, Moscow Ferenc Csorba

Schedule •

IPv4 exhaustion

•

IPv6 address space

•

Russian and regional IPv6 deployment statistics

•

BGP multihoming

•

Routing & the RIPE Database

2

RIPE / RIPE NCC RIPE Operators community Develops addressing policies Working group mailing lists

RIPE NCC Located in Amsterdam Not for profit membership organisation One of five RIRs - distributes IP & ASN

3

How can you influence addressing policies •

Take part in email discussions -

•

RIPE website → RIPE → Mailing Lists

Come to the RIPE Meetings -

Amsterdam was in May, Vienna in October

Two free tickets for new LIRs - Remote participation possible -

4

IPv4 Address Pool Exhaustion

IANA IPv4 Pool 40%

30%

20%

10%

0% 2000

2001

2002

2003

2004

2005

2006

2007

2008

2009

2010

2011

6

IPv4 address distribution /0

IANA

/8

RIR

/21

/23

Allocation

LIR

/25

End User

/25

PA Assignment

PI Assignment 7

IANA and RIRs IPv4 pool IANA Pool

RIR Allocations

Advertised

RIR Pool

Today

256

Projection

Data

192

128

64

0 1999

2000

2001

2002

2003

2004

2005

2006

2007

2008

2009

2010

2011

2012

8

Our slice of the IPv4 pie Organisations Other IANA AfriNIC LACNIC

RIPE NCC

ARIN

APNIC 9

RIPE NCC’s IPv4 Pool

http://www.ripe.net/internet-coordination/ipv4-exhaustion/ipv4-available-pool-graph

10

IPv4 exhaustion phases

IPv4 still available. RIPE NCC continues distributing it

RIPE NCC’s allocation policy from last /8 applies

RIPE NCC can only distribute IPv6

time

now IANA pool exhausted

?

RIPE NCC reaches final /8

RIPE NCC pool exhausted

Each of the 5 RIRs given a /8

11

Run Out Fairly (of IPv4) •

Gradually reduced allocation / assignment periods

•

Needs for “Entire Period” of up to... 12 months (January 2010) - 9 months (July 2010) - 6 months (January 2011) - 3 months (July 2011) -

•

50% has to be used up by half-period

12

How will we evaluate your requests? •

Find all criteria at: ‘IPv4 Evaluation Procedures’ page http://www.ripe.net/lir-services/resource-management/ contact/ipv4-evaluation-procedures

13

New: All IPv4 Requests in one queue New and ongoing requests. Every email: new time stamp

request! robot! queue!

13:45:01 17:36:57 12.11.2010! 14.11.2010!

Time stamp!

IPRA! Questions?!

approval! 14

IPv4 exhaustion phases

IPv4 still available. RIPE NCC continues distributing it

RIPE NCC’s allocation policy from last /8 applies

RIPE NCC can only distribute IPv6

time

now IANA pool exhausted

?

RIPE NCC reaches final /8

RIPE NCC pool exhausted

Each of the 5 RIRs given a /8

15

RIPE NCC’s last /8 •

We do things differently!

•

Ensures IPv4 access for all members 16000+ /22s in a /8 - members can get one /22 (=1024 addresses) - must already hold IPv6 - must qualify for allocation -

•

/16 set aside for unforeseen situations -

•

if unused, will be distributed

No PI 16

IPv6 Address Space

Where do all the addresses come from? IETF

IANA

AfriNIC

ARIN

RIPE NCC

APNIC

LACNIC

7000 LIRs

End Users

18

Policy process: decision making Standards

IETF

IANA

AfriNIC

ARIN

RIPE NCC

RIPE Community: Open to everyone

APNIC

LACNIC

Operations

19

Registration

20

Conservation

21

Aggregation

22

Governing principles of addressing policy •

Registration (in RIR whois databases) Ensure uniqueness of Internet number resources - Provide contact information for users of Internet number resources -

•

Aggregation Introduction of Classless Inter Domain Routing (CIDR) - Provide scalable routing solution for Internet -

•

Conservation Policies to ensure fair usage - Number resources are distributed based on need -

23

/24 /25 /26 /27 /28 /29 /30 /31 /32 /33 /34 /35 /36 /37 /38 /39 /40 /41 /42 /43 /44 /45 /46 /47 /48 /49 /50 /51 /52 /53 /54 /55 /56 /57 /58 /59 /60 /61 /62 /63 /64

/48s

/56s

/64s

Bits

16M 8M 4M 2M 1M 512K 256K 128K 64K 32K 16K 8K 4K 2K 1K 512 256 128 64 32 16 8 4 2 1

4G 2G 1G 512M 256M 128M 64M 32M 16M 8M 4M 2M 1M 512K 256K 128K 64K 32K 16K 8K 4K 2K 1K 512 256 128 64 32 16 8 4 2 1

1T 512G 256G 128G 64G 32G 16G 8G 4G 2G 1G 512M 256M 128M 64M 32M 16M 8M 4M 1M 1M 512K 256K 128K 64K 32K 16K 8K 4K 2K 1K 512 256 128 64 32 16 8 4 2 1

104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64

IPv4 CIDR Chart IP Addresses 1 2 4 8 16 32 64 128 256 512 1K 2K 4K 8K 16 K 32 K 64 K 128 K 256 K 512 K 1M 2M 4M 8M 16 M 32 M 64 M 128 M 256 M 512 M 1024 M 2048 M 4096 M

RIPE NCC Bits

Prefix

Subnet Mask

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32

/32 /31 /30 /29 /28 /27 /26 /25 /24 /23 /22 /21 /20 /19 /18 /17 /16 /15 /14 /13 /12 /11 /10 /9 /8 /7 /6 /5 /4 /3 /2 /1 /0

255.255.255.255 255.255.255.254 255.255.255.252 255.255.255.248 255.255.255.240 255.255.255.224 255.255.255.192 255.255.255.128 255.255.255.0 255.255.254.0 255.255.252.0 255.255.248.0 255.255.240.0 255.255.224.0 255.255.192.0 255.255.128.0 255.255.0.0 255.254.0.0 255.252.0.0 255.248.0.0 255.240.0.0 255.224.0.0 255.192.0.0 255.128.0.0 255.0.0.0 254.0.0.0 252.0.0.0 248.0.0.0 240.0.0.0 224.0.0.0 192.0.0.0 128.0.0.0 0.0.0.0

Contact Registration Services: KRVWPDVWHU#ULSHQHWŘOLUKHOS#ULSHQHW

. Ř0 

Prefix

. Ř0 Ř* Ř7 

RIPE NCC

IPv6 Chart

Classless Inter-Domain Routing (CIDR)

www.ripe.net

24

IPv6 address distribution /3

IANA

/12

RIR

/32

/48

PA Allocation

LIR

/56

End User

/48

Provider Aggregatable Assignment

PI Assignment 25

IPv6 basics •

IPv6 address: 128 bits -

32 bits in IPv4

•

Every subnet should be a /64

•

Customer assignments (sites) between: /64 (1 subnet) - /48 (65536 subnets) -

•

Minimum allocation size /32 -

65536 /48’s

26

IPv4 vs IPv6 (rounded off, theoretically) IPv4

IPv6

addresses

4x109

2x1019

allocations to members

2x106

4x109

in each allocation:

in each allocation:

2048

4x109

addresses

subnets

subnets

27

Getting an IPv6 allocation •

To qualify, an organisation must: Be an LIR - Have a plan for making assignments within two years -

•

Minimum allocation size /32

•

Announcement as a single prefix recommended

28

What does the first IPv6 allocation cost?

for all - pending General Meeting decision -

or:

-

for approximately 97% of the LIRs -

more points, but not higher category!

29

Making addressing plans •

Number of hosts is irrelevant

•

Multiple /48s per pop can be used separate blocks for infrastructure and customers - document address needs for allocation criteria -

•

Use one /64 block per site for loopbacks

•

/64 for all subnets autoconfiguration works - renumbering easier - less typo errors because of simplicity -

30

Customer assignments •

Give your customers enough addresses -

•

For more addresses, send in request form -

•

Up to a /48

Alternatively, make a sub-allocation

Every assignment must now be registered in the RIPE database

31

Using AGGREGATED-BY-LIR /32

ALLOCATED-BY-RIR

ALLOCATED-BY-LIR

/36

AGGREGATED-BY-LIR

/40

assignment-size: 48

ASSIGNED

/44

AGGREGATED-BY-LIR assignment-size: 56

/34

hint :) /48

/48

/48

/48

/48

32

Getting IPv6 PI address space •

To qualify, an organisation must: Demonstrate it will multihome - Meet the contractual requirements for provider independent resources -

•

Minimum assignment size /48

33

Getting IPv6 PI address space for an LIR •

To qualify, an organisation must: Demonstrate it will multihome - Meet the contractual requirements for provider independent resources - LIRs must demonstrate special routing requirements -

•

Minimum assignment size /48

•

PI space can not be used for sub-assignments 34

LIR’s IPv6 PI cannot be used for •

DSL, cable, GPRS customers

•

Webhosting, if IP addresses not shared

35

IPv6 and IPv4 compatibility? •

IPv6 is a different protocol from IPv4

•

IPv6 hosts cannot talk to IPv4 hosts directly

•

Transition mechanisms NAT64 and DNS64 - Tools like 6rd and other tunnelling options - ... -

36

Dual Stack while you can Text

IPv6 Deployment Statistics

IPv6 Ripeness •

Rating system: -

One star if the LIR has an IPv6 allocation

-

Additional stars if:

-

-

IPv6 Prefix is announced on router

-

A route6 object is in the RIPE Database

-

Reverse DNS is set up

A list of all 4 star LIRs: http://ripeness.ripe.net/

39

IPv6 RIPEness: 7512 LIRs (31 May 2011) 1 star

2 stars

3 stars

4 stars

No IPv6

1 star 13%

No IPv6 58%

2 stars 5%

3 stars 10%

4 stars 15%

0

4star

Finnland (123 LIRs)

UK (857 LIRs)

3star

France (389 LIRs)

Germany (756 LIRs)

2star

Kazakhstan (46 LIRs)

Belarus (14 LIRs)

1star

Ukraine (146 LIRs)

Russia (1050 LIRs)

1200

Poland (202 LIRs)

Slovenia (42 LIRs)

IPv6 RIPEness – countries (31 May 2011) 0star

1000

800

600

400

200

41

0%

4star

Finnland (123 LIRs)

UK (857 LIRs)

3star

France (389 LIRs)

Germany (756 LIRs)

2star

Kazakhstan (46 LIRs)

Belarus (14 LIRs)

1star

Ukraine (146 LIRs)

Russia (1050 LIRs)

100%

Poland (202 LIRs)

Slovenia (42 LIRs)

IPv6 RIPEness – relative (31 May 2011) 0star

75%

50%

25%

42

IPv6 enabled ASes in global routing (31.05) _ALL

RU

UA

DE

FR

25%

http://v6ASNs.ripe.net 20%

15%

10%

5%

0%

2004

2005

2006

2007

2008

2009

2010

2011

43

World IPv6 Day •

8 June 2011

•

Initiated by ISOC

•

0:00 GMT - 23:59 GMT

•

Top 500 websites

•

-

Google

-

Facebook

-

Yahoo

-

and you?

Great test opportunity 44

RIPE NCC and World IPv6 Day •

RIPE NCC Measurements Measuring connectivity to World IPv6 Day participants - Testing connectivity and performance using TTM - Monitoring performance of 6to4 versus native IPv6 -

•

Coordinated events Amsterdam - Moscow -

•

Live reports on http://www.ripe.net/worldipv6day 45

RIPE NCC @ World IPv6 Day •

All of our content and services over IPv6

•

IPV6 Eyechart

•

IPv6 Day Measurements http://v6day.ripe.net/

http://ipv6eyechart.ripe.net/

46

Eye Chart for IPv6 Day

47

Measurements for IPv6 Day

48

Multihomed BGP Routing Setup

To be or not to be an LIR Type

Contract with:

Fee 2010 / 2011

End User

LIR

PI = ! 50 ASN = ! 50

LIR

Start-up fee + yearly fee PA RIPE NCC XS = ! 1300 allocations + PI + PI / ASN

Direct Start-up fee Assignment RIPE NCC + ! 1300 + User PI / ASN

Space

Member of RIPE NCC

Can influence RIPE policies

PI

No

Yes

Yes

Yes

No

Yes

PI

50

Scenario 1: LIR = PA allocation + ASN ISP 2

ISP 1

x AS3

AS7 AS4

•

AS5 AS6

Can make assignments to End Users 51

Scenario 2: End User = PI + ASN ISP 2

ISP 1

x

•

Can NOT sub-assign further!!! -

(in IPv4 can still use PI for xDSL, broadband...)

52

Scenario 3: LIR or DAU = PI + ASN ISP 2

ISP 1

x

•

Can NOT sub-assign further!!! -

(in IPv4 can still use PI for xDSL, broadband...)

53

Scenario 4: PI End User, not multihomed ISP 2

ISP 1

x •

Part of LIR’s AS number does not want to / can not run BGP - still wants “portable” addresses -

54

Scenario 5: PA assignment, multihomed ISP 1

ISP 2

x •

Very rare and complicated more specific PA prefix announced, to multiple ISPs - technically challenging, but “cheap” -

55

How to get an AS Number •

Assignment requirements Address space - Multihoming - One AS Number per network -

•

For LIR itself

•

For End User Sponsoring LIR requests it for End User - Direct Assignment User requests it for themselves -

56

32-bit AS Numbers and you •

New format: “AS4192351863”

•

Act now!

•

Prepare for 32-bit ASNs in your organisation: Check if hardware is compatible; if not, contact hardware vendor - Check if upstream uses compatible hardware; if not, they should upgrade! -

57

RIPE DB

Registration: RIPE Database •

Public Internet resources database

•

All LIRs objects are there: Address space: inetnum & inet6num - AS Number: aut-num - Contact details: person, role, organisation, - Strong protection: maintainer (key-cert, irt) -

59

Connection between objects

org:

aut-num:

AS12345

inetnum:

85.118.184.0/21

tech-c: mnt-by: mnt-routes: org:

LA789-RIPE LIR-MNT USER-MNT ORG-Bb2-RIPE

status: tech-c: mnt-lower: org:

ALLOCATED PA LA789-RIPE LIR-MNT ORG-Bb2-RIPE

ORG-Bb2-RIPE

mnt-by: mnt-ref: mnt-ref: admin-c:

RIPE-NCC-HM-MNT RIPE-NCC-HM-MNT LIR-MNT LA789-RIPE

mntner: LIR-MNT admin-c: LA789-RIPE tech-c: LA789-RIPE auth: MD5-PW $nje^6G

route: origin: mnt-by:

role:

LIR ADMIN

nic-hdl: mnt-by: tech-c: tech-c: e-mail:

LA789-RIPE LIR-MNT JD1-RIPE JM1-RIPE noc@provider

85.118.184.0/21 AS12345 LIR-MNT

person:

Jane Doe

nic-hdl: JD1-RIPE mnt-by: LIR-MNT address: somewhere phone: +31122345678 person:

John Malkovich

nic-hdl: JM1-RIPE mnt-by: LIR-MNT address: under the bridge phone: +312458765432

Finding and changing objects •

Querying the RIPE Database Command-line client - Web interface - Free text search (Glimpse) - & http://lab.db.ripe.net/portal/free-text/search.htm -

•

Updating = creating, modifying, deleting -

Web, sync, email

61

Protection

mntner: LIR-MNT

person:

auth: MD5-PW $1$o93Ux

nic-hdl: JS1-RIPE mnt-by:

John Smith

LIR-MNT

password: Clear_Text

62

Strong authentication •

Password (MD5-PW)

•

Private key / public key -

PGPKEY- and key-cert object X.509- and key-cert object

63

Protection inetnum: 85.118.184.0/24 status: ASSIGNED PA mnt-by: LIR-MNT

mntner: LIR-MNT auth: MD5-PW $1$o93Ux

person:

John Smith

nic-hdl: JS1-RIPE mnt-by:

LIR-MNT

aut-num: AS2 mnt-by: LIR-MNT password: Clear_Text 64

Routing & Routing Registry

What is “Internet Routing Registry”! •

Distributed databases with public routing policy information, mirroring each other: irr.net -

APNIC, RADB, Level3, SAVVIS...

•

RIPE NCC operates “RIPE Routing Registry”

•

Big operators make use of it -

AS286 (KPN), AS5400 (BT), AS1299 (Telia), AS8918 (Carrier1), AS2764 (Connect), AS3561 (Savvis), AS3356 (Level 3)... 66

Publishing routing policy in IRR •

Required by some Transit Providers & IXPs -

•

Allows for automated generation of prefix filters -

•

they use it for prefix-based filtering and router configuration commands, based on RR

Contributes to routing security -

prefix filtering based on IRR registered routes prevents accidental leaks and route hijacking

•

Consistent information between neighbors

•

Good housekeeping 67

85% match between BGP/RIS & RR •

According to the RIPE Labs article

68

RIPE RR is part of the RIPE Database •

route[6] object creation is responsibility of LIR -

•

every time you receive a new allocation, do create a route or route6 object

route and route6 objects represent routed prefix -

address space being announced by an AS number

those are two primary keys - only the holder of both address space and AS number can authorize creation of route[6] object -

69

Authenticating a route6 object for an LIR inet6num: 2001:db8::/32

aut-num: aut-num: AS2

status: ALLOCATED-BY-RIR mnt-by: RIPE-NCC-HM-MNT mnt-routes: LIR-MNT

mnt-by: LIR-MNT

AS2

route6: 2001:db8::/32 origin: mnt-by:

AS2 LIR-MNT

70

Automation of router configuration •

Describing routing policy in aut-num enables generation of route-maps for policy routing

•

Tools can read your policy towards peers -

•

translation from RPSL to router configuration commands

Tools collect the data your peers have in RR -

if their data changes, you only have to periodically run your scripts to collect updates

71

IPv6 in the Routing Registry Route6 object: route6:" origin:"

2001:DB8::/32 AS65550

Aut-num object: aut-num:" AS65550 mp-import:" afi ipv6.unicast from AS64496 accept ANY mp-export:" afi ipv6.unicast to AS64496 announce AS65550

72

RIPE NCC Resource Quality Assistance •

Address distribution - no claims about routability -

but assistance in case of filtering issues:

http://www.ripe.net/lir-services/resource-management/ ripe-ncc-resource-quality-assistance

73

Questions? [email protected]

The End!

Y Diwedd

Kрай

Fí

!"#$ Ende Konec

Beigas

Lõpp

‫הסוף‬

Fine

Einde

Liðugt

Finvezh Ënn

Kraj

Vége Endir

Finis Kiнець

Fund Son

An Críoch

Sfârşit

Конeц

Fin Slut

Pabaiga Fim

Amaia

Loppu

Kpaj

Tmiem

Τέλος Slutt Koniec