IPv6 Adressvergabe und Adressierung

1,303 views

Published on

Ein Anlass des www.swissipv6council.ch
Referentin: Nathalie Trenaman, RIPE NCC

Nathalie Trenaman von RIPE wird in ihrem Referat Best Practices zur Adressierung vermitteln und aufzeigen, wie Firmen zu ihrem IPv6 Range kommen. Die definitive Agenda wird so bald wie möglich bekannt gegeben.

Das Referat wird in Englisch gehalten.

18:00 Uhr
Begrüssung durch Silvia Hagen, Präsidentin Swiss IPv6 Council

18:05 Uhr
Nathalie Trenaman, RIPE
Inhalt:
1. Teil
IPv6 Adressierung
Wie muss ich ein IPv6 Netzwerk konzeptionell aufsetzen?
2. Teil
Policies
Vorstellung der Möglichkeiten für Unternehmen, sich die IPv6 Adressen zu sichern
Wer bekommt welche Ranges?
Wie muss man sich bewerben?
Q&A

Über RIPE NCC
RIPE NCC is the Regional Internet Registry responsible for IPv6 distribution in Europe, Middle East and Central Asia. We build awareness among all Internet stakeholders of the need to deploy IPv6. At this moment, RIPE NCC has over 10.000 members. 69% of these members have a block of IPv6 addresses. The first hurdle of an IPv6 deployment is building a scalable IPv6 addressing plan. Since there are so many addresses and distribution is done in subnets, a lot of engineers and architects see this phase of the deployment as one of the most challenging. Nathalie will shine a light on current best practices, taking into account different transitioning mechanisms and end users.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,303
On SlideShare
0
From Embeds
0
Number of Embeds
591
Actions
Shares
0
Downloads
9
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

IPv6 Adressvergabe und Adressierung

  1. 1. IPv6 Addressing Fundamentals Nathalie Trenaman RIPE NCC Swiss IPv6 Council 28 April 2014 Tuesday, April 29, 2014
  2. 2. 2 • RIPE Policies • What ranges can I get, and where? • Allocation Process • How do I use this space? • IPv6 Addressing Guidelines • Recommendations Agenda Tuesday, April 29, 2014
  3. 3. Ferenc Csorba - 13 March 2014 RIPE NCC • Located in Amsterdam • Not for profit organisation • One of the 5 Regional Internet Registries RIPE NCC - who are we? 3 Tuesday, April 29, 2014
  4. 4. 4 “On 14 September 2012, the RIPE NCC ran out of their regular pool of IPv4” Tuesday, April 29, 2014
  5. 5. Section 1 IPv6 Policies Tuesday, April 29, 2014
  6. 6. IPv6 Address Basics 6IP Address Distribution Allocation PA Assignment PI Assignment IANA End User LIR RIR /3 /32 /12 /56/48 /48 Tuesday, April 29, 2014
  7. 7. Ferenc Csorba - 13 March 2014 RIPE Policies •IPv6 Address Allocation & Assignment Policy •RIPE-589 •Made by the RIPE Community •Consensus is the key 7 Tuesday, April 29, 2014
  8. 8. Getting it 8 • To qualify, an organisation must: • Be an LIR • Have a plan for making assignments within two years • Minimum allocation size /32 • Up to a /29 without additional justification • More if justified by customer numbers Getting an IPv6 allocation Tuesday, April 29, 2014
  9. 9. Getting it 9 • Give your customers enough addresses • up to a /48 • For more addresses send in request form • alternatively, make a sub-allocation • Every assignment must be registered in the RIPE Database Customer Assignments Tuesday, April 29, 2014
  10. 10. Getting it 10Comparison IPv4 and IPv6 status IPv4 IPv6 ALLOCATED PA ALLOCATED-BY-RIR ASSIGNED PA ASSIGNED ASSIGNED PA AGGREGATED-BY-LIR SUB-ALLOCATED PA ALLOCATED-BY-LIR ASSIGNED PI ASSIGNED PI Tuesday, April 29, 2014
  11. 11. Getting it 11 • Status is ASSIGNED • Minimum assignment size is a/64 • For more than a /48, send a request form Using ASSIGNED ALLOCATED-BY-RIR ASSIGNED /44 Tuesday, April 29, 2014
  12. 12. Getting it 12 • Can be used to group customers • broadband, for example • “assignment size” = assignment of each customer Using AGGREGATED-BY-LIR ALLOCATED-BY-RIR AGGREGATED-BY-LIR assignment-size: 56 /34 /56 /56/56/56/56 Tuesday, April 29, 2014
  13. 13. Getting it 13 inet6num:        2001:db8:1000::/36 netname:         Brightlife descr:      Broadband services country:          NL admin-c:         BN649-RIPE tech-c:          BN649-RIPE status:          AGGREGATED-BY-LIR assignment-size: 48 mnt-by:          BRIGHTLIFE-MNT notify:          noc@example.net changed:        noc@example.net 20130218 source:         RIPE AGGREGATED-BY-LIR in the RIPE DB Tuesday, April 29, 2014
  14. 14. Getting it 14 • Can be used for customers who expect large growth • or for your own infrastructure Using ALLOCATED-BY-LIR ALLOCATED-BY-RIR ALLOCATED-BY-LIR AGGREGATED-BY-LIR assignment-size: 48 /40 /36 Tuesday, April 29, 2014
  15. 15. Getting it 15Overview ALLOCATED-BY-RIR ALLOCATED-BY-LIR /48 /48/48/48/48 AGGREGATED-BY-LIR assignment-size: 48 /40 ASSIGNED AGGREGATED-BY-LIR assignment-size: 56 /34/44/36 Tuesday, April 29, 2014
  16. 16. Getting it 16 • To qualify, an organisation must: • 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 • not even 1 IP address Getting IPv6 PI address space Tuesday, April 29, 2014
  17. 17. Tips 17IPv6 RIPEness: 10238 LIRs 4 stars 21% 3 stars 14% 2 stars 8%1 star 25% No IPv6 32% Tuesday, April 29, 2014
  18. 18. Tips 18IPv6 RIPEness: Switzerland 350 LIRs 4 stars 24% 3 stars 19% 2 stars 8% 1 star 21% No IPv6 28% Tuesday, April 29, 2014
  19. 19. ? 19 Tuesday, April 29, 2014
  20. 20. Section 2 IPv6 Addressing Plans Tuesday, April 29, 2014
  21. 21. Why Create an Addressing Plan? Benefits of an IPv6 Addressing Plan: •Mental health during implementation(!) •Easier implementation of security policies •Efficient addressing plans are scalable •More efficient route aggregation 21 Tuesday, April 29, 2014
  22. 22. 4 Bit Boundaries IPv6 offers flexibility with addressing plans Network addressing can be done on 4 bit boundaries 22 Tuesday, April 29, 2014
  23. 23. Customers Customers should get a large block of addresses •/48 - Business •/48 or 56 - Residential For more than a /48, send a request form Every assignment must be registered 23 Tuesday, April 29, 2014
  24. 24. Example Situation Customer has 6 functions: •Servers •Office PCs •Network Engineers PCs •Guests •VPN (remote workers) • Infrastructure (point-to-point and loopbacks) 24 Tuesday, April 29, 2014
  25. 25. Example Situation Customer has 3 locations: •Main building floor 1 •Main building floor 2 •Secondary office 25 Tuesday, April 29, 2014
  26. 26. Example Assignment from LIR The customer gets 2001:0db8:1a2b::/48 Work on 4 bit boundary • 6 functions, leaves room for 10 new functions • 3 locations, leaves room for 13 new locations • We still have 8 bits! • Room for 256 networks per function per location 26 Tuesday, April 29, 2014
  27. 27. Example Plan 1 Putting this in the address: 2001:0db8:1a2b:FLXX::/64 •F = function (0=infrastructure, 1=servers, 2=office, 3 =engineers, e=vpn, f=guest) •L = location (0=main building 1, 1=main building 2, 2=secondary office •XX = Number for network of type +location 27 Tuesday, April 29, 2014
  28. 28. Example Plan Usage 28 Tuesday, April 29, 2014
  29. 29. Example Plan Usage 2001:0db8:1a2b:1000::/64 28 Tuesday, April 29, 2014
  30. 30. Example Plan Usage 2001:0db8:1a2b:1000::/64 •Servers in Main building, floor 1, network 0 28 Tuesday, April 29, 2014
  31. 31. Example Plan Usage 2001:0db8:1a2b:1000::/64 •Servers in Main building, floor 1, network 0 2001:0db8:1a2b:1200::/64 28 Tuesday, April 29, 2014
  32. 32. Example Plan Usage 2001:0db8:1a2b:1000::/64 •Servers in Main building, floor 1, network 0 2001:0db8:1a2b:1200::/64 •Servers in Secondary office, network 0 28 Tuesday, April 29, 2014
  33. 33. Example Plan Usage 2001:0db8:1a2b:1000::/64 •Servers in Main building, floor 1, network 0 2001:0db8:1a2b:1200::/64 •Servers in Secondary office, network 0 2001:0db8:1a2b:f009::/64 28 Tuesday, April 29, 2014
  34. 34. Example Plan Usage 2001:0db8:1a2b:1000::/64 •Servers in Main building, floor 1, network 0 2001:0db8:1a2b:1200::/64 •Servers in Secondary office, network 0 2001:0db8:1a2b:f009::/64 •Guest in Main Building, floor 1, network 9 28 Tuesday, April 29, 2014
  35. 35. Example Plan Usage 2001:0db8:1a2b:1000::/64 •Servers in Main building, floor 1, network 0 2001:0db8:1a2b:1200::/64 •Servers in Secondary office, network 0 2001:0db8:1a2b:f009::/64 •Guest in Main Building, floor 1, network 9 28 Tuesday, April 29, 2014
  36. 36. Example Plan Usage 29 Tuesday, April 29, 2014
  37. 37. Example Plan Usage 2001:0db8:1a2b:0000::1/128 29 Tuesday, April 29, 2014
  38. 38. Example Plan Usage 2001:0db8:1a2b:0000::1/128 •loopback address (location doesn’t apply!) 29 Tuesday, April 29, 2014
  39. 39. Example Plan Usage 2001:0db8:1a2b:0000::1/128 •loopback address (location doesn’t apply!) 2001:0db8:1a2b:0102::/64 29 Tuesday, April 29, 2014
  40. 40. Example Plan Usage 2001:0db8:1a2b:0000::1/128 •loopback address (location doesn’t apply!) 2001:0db8:1a2b:0102::/64 •point-to-point link (0 for infrastructure) 29 Tuesday, April 29, 2014
  41. 41. Example Plan Usage 2001:0db8:1a2b:0000::1/128 •loopback address (location doesn’t apply!) 2001:0db8:1a2b:0102::/64 •point-to-point link (0 for infrastructure) 2001:0db8:1a2b:e1ab::/64 29 Tuesday, April 29, 2014
  42. 42. Example Plan Usage 2001:0db8:1a2b:0000::1/128 •loopback address (location doesn’t apply!) 2001:0db8:1a2b:0102::/64 •point-to-point link (0 for infrastructure) 2001:0db8:1a2b:e1ab::/64 •VPN in main office, floor 1, user 171 29 Tuesday, April 29, 2014
  43. 43. Example Plan Usage 2001:0db8:1a2b:0000::1/128 •loopback address (location doesn’t apply!) 2001:0db8:1a2b:0102::/64 •point-to-point link (0 for infrastructure) 2001:0db8:1a2b:e1ab::/64 •VPN in main office, floor 1, user 171 29 Tuesday, April 29, 2014
  44. 44. Example Plan Usage 2001:0db8:1a2b:0000::1/128 •loopback address (location doesn’t apply!) 2001:0db8:1a2b:0102::/64 •point-to-point link (0 for infrastructure) 2001:0db8:1a2b:e1ab::/64 •VPN in main office, floor 1, user 171 29 Tuesday, April 29, 2014
  45. 45. Alternatives The previous example is just an idea •Adapt as necessary 2001:0db8:1a2b:FFLX::/64 •256 functions •16 locations •16 networks per function per location 30 Tuesday, April 29, 2014
  46. 46. End User Summary Tips: •Work on 4-bit boundary •Group subnets by function •Group subnets by location •Make a scalable addressing plan 31 Tuesday, April 29, 2014
  47. 47. ISP Addressing Plan What should an ISP Addressing Plan contain? •Address space for internal use • loopback interfaces • point-to-point connections • servers, routers and other infrastructure at PoPs •Use a /48 per POP •Address space for customers 32 Tuesday, April 29, 2014
  48. 48. Loopback Interfaces One /128 per device • One /64 contains enough space for 18.446.744.073.709.551.616 devices Take an easy to remember block for loopbacks • 2001:0db8:1a2b:0000:0000:0000:0000:0000 33 Tuesday, April 29, 2014
  49. 49. Point-to-Point Interfaces One /64 per point-to-point connection •Reserve 1 /64 for the link, but configure a / 127 (RFC6164) 34 Tuesday, April 29, 2014
  50. 50. ISP Guidelines In common cases: •One /48 per PoP •Calculate growth •Make it scalable 35 Tuesday, April 29, 2014
  51. 51. IPv6 Address Basics 36 • Every subnet should be a /64 • Customer assignments (sites) between: • /64 (1 subnet) • /48 (65,536 subnets) • Minimum allocation size /32 • 65,536 /48s • 16,777,216 /56s IPv6 Address Basics Tuesday, April 29, 2014
  52. 52. IPv6 Address Basics 37IPv6 Subnetting 0000:00002001:0DB8:0000:0000:0000:0000:0000:0000 IPv6 Subnetting /32 = 65536 /48 /48 = 65536 /64 /52 = 4096 /64 /56 = 256 /64 64 bits interface ID /60 = 16 /64 /64 Contact Training Services: ts@ripe.net Follow us on Twitter: www.twitter.com/TrainingRIPENCC www.ripe.net Tuesday, April 29, 2014
  53. 53. Tips 38 • Customers have no idea how to handle 65536 subnets! • Provide them with information • https://www.ripe.net/lir-services/training/material/ IPv6-for-LIRs-Training-Course/IPv6_addr_plan4.pdf Customers And Their /48 Tuesday, April 29, 2014
  54. 54. ? 39 Tuesday, April 29, 2014
  55. 55. Section 4 Transition Mechanisms Tuesday, April 29, 2014
  56. 56. Transition Mechanisms 41 • Maintaining connectivity to IPv4 hosts by sharing IPv4 addresses between clients • Extending the address space with NAT/CGN/LSN • Translating between IPv6 and IPv4 • Provide a mechanism to connect to the emerging IPv6-only networks • Tunneling IPv6 packets over IPv4-only networks Transitioning: Solving Two Problems Tuesday, April 29, 2014
  57. 57. Transition Mechanisms 42 • Manually configured tunnels towards a fixed tunnel broker like SixXS, Hurricane Electric or your own system • Stable and predictable but not easily deployed to the huge residential markets • MTU might cause issues 6in4 Tuesday, April 29, 2014
  58. 58. Transition Mechanisms 436in4 PROVIDERCUSTOMER INTERNET Home User IPv4 Infrastructure IPv4 Tunnel Broker IPv6 Internet Tunnel Server Tuesday, April 29, 2014
  59. 59. Transition Mechanisms 44 • 6to4 • “Automatic” tunnel, system can configure itself • IPv4 address is part of the IPv6 address • Requires a public IPv4 address • Uses anycast to reach a nearby server • Return traffic might choose another server • Teredo • Uses UDP to encapsulate packets • Works across (most) NAT implementations 6to4 and Teredo Tuesday, April 29, 2014
  60. 60. Transition Mechanisms 456to4 and Teredo PROVIDERCUSTOMER INTERNET Home User IPv4 IPv6 Internet Anycast 6to4 Tunnel Servers Infrastructure IPv4 Tuesday, April 29, 2014
  61. 61. Transition Mechanisms 46 • Quite similar to 6to4 • Encodes the IPv4 address in the IPv6 prefix • Uses address space assigned to the operator • The operator has full control over the relay • Traffic is symmetric across a relay • Or at least stays in your domain • Can work with both public and private space • Needs additional software for signaling 6RD Tuesday, April 29, 2014
  62. 62. Transition Mechanisms 476RD PROVIDERCUSTOMER INTERNET IPv6 Internet 6RD Tunnel Server IPv4 Internet Home User IPv4 Infrastructure IPv4 Tuesday, April 29, 2014
  63. 63. Transition Mechanisms 48 • Single-stack clients will only have IPv6 • Translator box will strip all headers and replace them with IPv4 • Requires some DNS “magic” • Capture responses and replace A with AAAA • Response is crafted based on target IPv4 address • Usually implies address sharing on IPv4 NAT64/DNS64 Tuesday, April 29, 2014
  64. 64. Transition Mechanisms 49NAT64/DNS64 PROVIDERCUSTOMER INTERNET Home User public IPv6 IPv6 Internet NAT64 Box IPv4 Internet DNS64 Infrastructure public IPv6 Tuesday, April 29, 2014
  65. 65. Transition Mechanisms 50 • Tunneling IPv4 over IPv6 • Allows clients to use RFC1918 addresses without doing NAT themselves • NAT is centrally located at the provider • Client’s IPv6 address is used to maintain state and to keep clients apart • Allows for duplicate IPv4 ranges DS-lite Tuesday, April 29, 2014
  66. 66. Transition Mechanisms 51DS-lite PROVIDERCUSTOMER INTERNET IPv6 Internet NAT44 Box IPv4 Internet Home User public IPv6 private IPv4 Infrastructure IPv6 Infrastructure IPv4 Tuesday, April 29, 2014
  67. 67. Tips 52 • Websites • http://www.getipv6.info • http://www.getipv6.info • http://datatracker.ietf.org/wg/v6ops/ • http://www.ripe.net/ripe/docs/ripe-554.html • Mailing lists • http://lists.cluenet.de/mailman/listinfo/ipv6-ops • http://www.ripe.net/mailman/listinfo/ipv6-wg Also useful Tuesday, April 29, 2014
  68. 68. ? 53 nathalie@ripe.net Tuesday, April 29, 2014

×