Introduction to IP addressing and Regional Internet Registries. Marco Hogewoning External Relations Officer - Technical Advisor

Transcription

1 Introduction to IP addressing and Regional Internet Registries Marco Hogewoning External Relations Officer - Technical Advisor marcoh@ripe.net IETF89 - London, UK - March 2014

2 About the RIPE NCC 2 One of five Regional Internet Registries (RIR) Not-for-profit association Based in Amsterdam (NL) - Small offices in Dubai and Moscow (new!) Service Region is Europe, Middle East and parts of Central Asia (CIS Region) Funded by the membership

3 About Me 3 From the Netherlands Worked as a network engineer since 1997 Involved with RIPE and RIPE NCC since 1999 Joined RIPE NCC as a trainer in 2011! - Now in External Relations Team as Technical Advisor Also co-chair of the RIPE IPv6 Working Group

4 Topics 4 IP Address - Function - Format - Properties IP Address management - Internet Registries - Policies and policy development IP version 6 - Difference from IPv4 - Challenges }IETF }IETF, IANA, RIRs }Everybody

5 Packet Networking

6 Circuit Switched Networks 6

7 IP Packet 7

8 Packet Networking 8

9 Hour Glass Model 9

10 IP Packet 10

11 Packet Header 11

12 IP Packet Header 12 (Source: rfc 791)

13 ?

14 Address Properties

15 What are the necessary properties?

16 (IP) Address Properties 16 Every entity handling packets needs to be able to read and understand the address - Fixed format - Machine readable The address has to be unambiguous - Globally unique [*]

17 Footnote: Definition of Global 17 1) Spherical 2) of, relating to, or involving the entire world : worldwide <a global system of communication> 3) of, relating to, or applying to a whole (as a mathematical function or a computer program) : universal <a global search of a file> (Source:

18 Dual Function 18 Addresses can be used for two things: - Identify the sender and recipient - Tells where the packet needs to go Postal Address - Name - Street, house number - City - Zipcode IP address - One single number for both functions

19 ?

20 Address Formats

21 Machine Readable 21 Bits and Bytes One single number - 4 bytes of 8 bits

22 Human Readable 22 Decimal system 4 numbers between Each number represents a single byte

23 All the same x xffffffff !! 32 bits = 2^32 = unique addresses

24 ?

25 Evolutions in Address Management

26 The Story So Far 26 Nearly 4.3 billion possible addresses - Need to be globally unique - Need to able to use them for routing purposes - Need to be able to identify the user Arranging connectivity Troubleshooting! We need somebody to coordinate

27 Meet IANA 27 Jon Postel ( ) The Internet Assigned Numbers Authority

28 The First Idea 28 aaa.bbb.ccc.ddd Network Routing Computer Identification Split in 8 and 24 bit portion 256 blocks of 16.7 million addresses Each participating network gets one block

29 Publication in RFCs 29

30 One Size Fits Nobody 30 More networks started to join the Internet Not that many really have 16 million computers! Shift the boundary?

31 Plan B 31 aaa.bbb.ccc.ddd Move the split between network and computer Create more but smaller networks Maintain backwards compatibility - You don t want to break or change the current systems

32 Classful Addressing 32 Class A: bits for network, 16 million computers each - Includes existing networks Class B: bits for network, computers each Class C: bits for network, 256 computers each Class D: Multicast Class E: Reserved

33 Identification 33 RFC with assigned numbers contained a list of people and their address

34 ?

35 Evolution

36 Whois 36 SRI operated Network Information Center (NIC) Whois protocol to access central database - Domains - Users - Machines - IP addresses Provided scalability to the lists

37 Internationalisation 37 European academic networks started to join the Internet Different political landscape - Large number of smaller countries Rapid growth put stress on registration model! Need for a more scalable approach - Delegation of tasks - Handover responsibility for large blocks to be further divided amongst participants

38 Building a New Model 38 RFC 1174 (August 1990) by the IAB It is proposed to retain the centralized IANA and IR functions. In addition, however, the IR would also allocate to organizations approved by the Coordinating Committee for Intercontinental Research Networking (CCIRN) blocks of network and autonomous system numbers, as needed, and delegate to them further assignment authority.

39 Implementation 39 RFC 1466 (May 1993) describes the requirements: - networking authorities within the geographic area legitimize the organization - the organization is well-established and has legitimacy outside of the registry function - the organization will commit appropriate resources to provide stable, timely, and reliable service to the geographic region - is committed to allocate IP numbers according to the guidelines established by the IANA and the IR - is committed to coordinate with the IR to establish qualifications and strategies for sub-allocations of the regional allocation

40 Meanwhile in Europe 40 The European networks met in April in 1989 to exchange experience and coordinate work on the European Internet and interconnections Réseaux IP Européens - RIPE - Rob Blokzijl appointed as volunteer to monitor progress Continued with regular meetings ever since - RIPE 68 will be held in Warsaw, May 2014 and celebrates 25 years of RIPE

41 Starting the European RIR 41 RIPE did not exist as formal organisation Trans-European Research and Education Network Association (TERENA) based in Amsterdam - Agrees to start the RIPE Network Coordination Center - Staff and facilities provided by TERENA - RIPE NCC continued as separate association in January 1998! Matched the requirements in RFC 1466

42 ?

43 The RIRs

44 Five RIRs Globally 44

45 Regional Internet Registries 45 All five RIRs are not-for-profit associations Funded by the membership Responsible for allocation and assignment of Internet Number Resources (INR) in its service region - IPv4 Addresses - IPv6 Addresses - Autonomous System Numbers (ASN) Each RIR operates a whois database

46 Regional Address Policies 46 Each RIR has its own Policy Development Process Regional community decides on regional policies for address allocation, assignment and registration Communities are open to everyone to participate - You don t have to live in a specific service region Decisions are made by rough consensus - No voting! RIR to implement policy and operate accordingly

47 Global Policy Development 47 Global proposal on address policy Regional Regional Regional Regional Regional proposal proposal proposal proposal proposal 5x2 Regional Community Regional Community Regional Community Regional Community Regional Community PDP PDP PDP PDP PDP 5x1 AFRINIC ARIN APNIC LACNIC RIPE NCC ASO IANA ICANN

48 ?

49 Running Out

50 Goldilocks Problem 50 Classful allocations to an average network - A is too big - C is too small - B is about right There are only 16k class B networks - Will soon be exhausted! Give people a number of consecutive class C networks instead of a class B - Not everybody needs 256 of them

51 Bigger Problems 51 In IP a connection between 2 machines (point-topoint) is a network and it requires a subnet!! - Class C is the smallest available There are only 4 billion addresses It will never fit!

52 A Two Tier Approach 52 Fix the longterm problem of only having 4 billion addresses - Alter the protocol to extend the address space! In the short term find ways to improve efficiency in the existing numbering scheme - This will buy the time to design and implement the permanent solution

53 Short Term Solution 53 Let go of the fixed network sizes Classless Interdomain Routing (CIDR) uses a variable subnet length - Size depends on the number of addresses required! Class A, B and C no longer exist! - Now called /8, /16 and /24! Implemented by RIRs as justified need - Assignment sizes depend on number of end-points

54 IP Next Generation 54 IETF issued a call for proposals for the next version of the Internet Protocol - Bigger address space! - Lessons learned?! Resulted in IP version 6 - Version 5 was already used for something else First RFC published in December Updated in December The co-author Bob Hinden is here at IETF89

55 IPv6

56 IPv6 Protocol Basics 56 Functionally the same as IPv4 - Same cardboard box, slightly bigger label on it Address is 128 bits long (IPv4 uses 32 bits) - 2^128 addresses available options! It is 100 percent incompatible with IPv4 - Design feature

57 Footnote: How Big is Big? 57 7 billion people on earth (round it up to 10 billion)! - Assume everyone will have 100 devices - Each device will connect to sensors x 100 x = ! IPv6 address space will not run out - If it ever does, come back and claim the chocolate

58 Deploying IPv6: The Plan 58 IPv6 and IPv4 are not compatible - you can use both protocols at the same time on the same network without interference - You can retrofit IPv6 onto existing networks Computers which have both can choose wether to use IPv4 or IPv6! - Depending on the peers capability When both are available: use IPv6 - This will gradually phase out IPv4

59 Work in IETF Completed 59 The main protocol standardised in 1998 Together with essential extensions to protocols such as DNS and Border Gateway Protocol By design most protocols operate independent from the IP version - TCP and UDP unaltered - Remember the hour glass model

60 Chickens and Eggs 60 IPv6 suffers from a classic bootstrapping problem! For applications to support IPv6 you need the network to deliver packets - Networks don t supply IPv6 connectivity because there are not that many applications that support it Content and Services need to adopt IPv6, but there are no users who can access using IPv6 - There are no users, because there is no content

61 IPv6 is Invisible 61 Users ($$$) IPv6 Users ($$$)

62 There is no difference, there is just more of it

63 RIRs and IPv6 63 Encouraging the adoption of IPv6 for over 10 years - IPv6 resource allocation started late nineties Capacity building at different levels - High level information for decision makers - Hands-on training for engineers - Online, in situ, brochures, webinairs, conferences Cooperation with ISOC, IAB, ICANN, ITU-D, industry and governments

64 IPv6 is Taking Off 64 APNIC and RIPE NCC have exhausted their pools of IPv4 addresses - ARIN has 1.38 /8s left (23 million addresses) Networks now have to deploy IPv6 to grow - Sustaining IPv4 becomes expensive Global events such as World IPv6 Launch Day (

65 IPv6 Heat Map 65 (

66 What Can You Do? 66 Deploy IPv6 as quickly as you can - Alter procurement procedures - Start raising awareness - Start training people - Take the step of turning it on where you can Liaise with your RIR and ISOC - We can help you

67 ?