IP#without#IP#addresses# # h"p://ilnp.cs.st-andrews.ac.uk/#

Transcription

1 IP#without#IP#addresses# # h"p://ilnp.cs.st-andrews.ac.uk/# Saleem&Bha)& School&of&Computer&Science& University&of&St&Andrews& Italian&Networking&Workshop& Cavalese,&TrenBno,&Italy& 14&Jan&2015&

2 University8of8St8Andrews8 28

3 Thanks8 INW8arrangements:8 Prof.#Renato#Lo#Cigno# Prof.#Roberto#Gaudino# Dr8Ran8Atkinson8 PhD8students8at8St8Andrews:8 Ditchaphong8PhoomikiaEsak8 Bruce8Simpson8 IRTF8RouTng8Research8Group8(RRG):8 RRG8Chair8(at8the8Tme),8Tony8Li8(formerly8of8Cisco)8 IRTF8Chair,8Lars8Eggert8(NetApp)8+8RFC8Team8 h"p://ilnp.cs.st-andrews.ac.uk/88 (C)8Saleem8N.8BhaE,8148Jan

4 ILNP8 IdenTfier-Locator8Network8Protocol8 1.Why?# 2. What?8 3. How?8 (C)8Saleem8N.8BhaE,8148Jan

5 The8changing8world8of8IP8networks8 How8to8support8a8harmonised8solu-on.to.many. network#func>ons#in#a#scalable#manner?8 MulT-homing8(host8and8site).8 Mobility8(host8and8network).8 MulT-path8capable8transport8protocols.8 Localised8addressing8(NAT).8 Traffic8engineering8capability.8 Packet-level,8end-to-end8security.8 Virtual8machine8migraTon/mobility.8 Current8soluTons8for8such8funcTons8remain8 disparate,8do8not8functon8well8together8and/or8 may8not8scale8well.8 (C)8Saleem8N.8BhaE,8148Jan

6 Use8of8IP8addresses8today8 (C)8Saleem8N.8BhaE,8148Jan

7 Naming8Architecture:88IP8 Protocol#Layer# ApplicaTon8 Transport8 Network8 (Interface)8 IP# FQDN8or8 IP8address8 IP8address8 (+8port8number)8 IP8address8 IP8address8 Entanglement#!# FQDN8=8fully8qualified8domain8name8 (C)8Saleem8N.8BhaE,8148Jan

8 ! RFC21018(Feb81997)8 IPv48Address8Behaviour8Today8 RFC21018(IAB,8InformaTonal)8pp83-48! 3. Ideal properties.!!... it is easy to see the ideal! properties of identifiers and locators. Identifiers should be! assigned at birth, never change, and never be re-used. Locators! should describe the host's position in the network's topology, and! should change whenever the topology changes.! Unfortunately neither of the these ideals are met by IPv4 addresses.! (C)8Saleem8N.8BhaE,8148Jan

9 RFC49848(Sep82007)8 Report8from8the8IAB8Workshop8on8RouTng8and8Addressing8 RFC49848(IAB,8InformaTonal)8,8p688 &... workshop participants! concluded that the so-called "locator/identifier overload" of the IP! address semantics is one of the causes of the routing scalability! problem as we see today. Thus, a "split" seems necessary to scale! the routing system, although how to actually architect and implement! such a split was not explored in detail.! (C)8Saleem8N.8BhaE,8148Jan

10 IP8addresses8considered8harmful 8 IP#addresses#considered#harmful # Brian8E.8Carpenter8 ACM8SIGCOMM8CCR,8vol.844,8issue82,8Apr h"p://dl.acm.org/citaton.cfm?id= h"p://dx.doi.org/ / Abstract8 This8note8describes8how8the8Internet8has8got8 itself8into8deep8trouble8by8over-reliance8on8ip8 addresses8and8discusses8some8possible8ways8 forward. 8 (C)8Saleem8N.8BhaE,8148Jan

11 New8namespaces,8separate8semanTcs8 SemanTc8overload8of8IP8address:8 locator8semantcs8+8iden>fier8semantcs8 ease8implementaton8of8mult-homing,8mobility,8etc8 8 This8is8a8well-known8problem:8 RFC4984,8IAB8(2007)8 RFC2101,8IAB8(1997)8 IEN1#(1977)# Many8 ID/Locator8separaTon 8soluTons8proposed:8 HIP,8LISP,8SHIM6,8SixOne8 8re-use8of8IP8address8 ILNP# #deprecates#use#of#ip#addresses# (C)8Saleem8N.8BhaE,8148Jan

12 Naming8Architecture:88IP88vs88ILNP8 Protocol#Layer# ApplicaTon8 Transport8 Network8 (Interface)8 IP# FQDN8or8 IP8address8 IP8address8 (+8port8number)8 IP8address8 IP8address8 ILNP# FQDN8 (RFC1958)8 (Node)8IdenTfier8 (+8port8number)8 Locator8 (dynamic8mapping)8 Entanglement#!# FQDN8=8fully8qualified8domain8name8 Separa>on#"# (C)8Saleem8N.8BhaE,8148Jan

13 ILNP8 IdenTfier-Locator8Network8Protocol8 1. Why?8 2.What?# 3. How?8 (C)8Saleem8N.8BhaE,8148Jan

14 ILNP8 IdenTfier8Locator8Network8Protocol:8 h"p://ilnp.cs.st-andrews.ac.uk/8 ILNP8enhances8Internet8Protocol8funcTonality8 through8the8use8of8naming.8 March82010:8IRTF8RRG8Chairs8recommend8 ILNP8for8development8within8the8IETF8-8 RFC61158(Feb82011)8 IRTF#Experimental#protocol# RFCs#6740T6748# (C)8Saleem8N.8BhaE,8148Jan

15 IdenTfier-Locator8namespaces8in8ILNP8 Locator,#L:# Topologically#significant.# Names8a8(sub)network8(as8today s8network#prefix).8 Used8only8for8rouTng8and8forwarding8in8the8core.8 (Node)#Iden>fier,#(NID)#I:# Is#not#topologically#significant.# Names8a8logical/virtual/physical8node,8does8not8 name8an8interface.8 Upper#layer#protocols#bind#only#to#(NID)#I.# (C)8Saleem8N.8BhaE,8148Jan

16 ILNP:8transport8layer8state8example8 X8 Y8 Internet8 A8=8IP8address8 P8=8port8number8 8 At8X:8 <TCP:8A X,8P X,8A Y,8P Y >8<IP:8A X,8A Y >8 8 At8Y:8 <TCP:8A Y,8P Y,8A X,8P X >8<IP:8A Y,8A X >88 8 L8=8Locator8 I8=8(Node)8IdenTfier8 P8=8port8number8 8 At8X:8 <TCP:8I X,8P X,8I Y,8P Y >8<IP:8L X,8L Y >8 8 At8Y:8 <TCP:8I Y,8P Y,8I X,8P X >8<IP:8L Y,8L X >88 (C)8Saleem8N.8BhaE,8148Jan

17 Namespaces8&8namebindings8 IP8 8staTc8 ILNP8 8dynamic8 IP8address8 ApplicaTon8 Transport8 session8 IP8 subnetwork8 Physical8 interface8 animated knot from FQDN8 FQDN8 FQDN8 L8 NID8 L8 NID8 L8 NID8 ApplicaTon8 Transport8 session8 IP8 subnetwork8 Physical8 interface8 (C)8Saleem8N.8BhaE,8148Jan

18 ILNP:88Locator8ProperTes8 Locator8names8an8IP8(sub)network.8 Locator8is8equivalent8to8an8IP8rouTng8prefix:8 MulTple8Locators8can8be8used8simultaneously.8 Nodes#can#change#their#Locator#values#during# the#life>me#of#an#ilnp#session.# Enables8 NAT,8mobility,8mulT-homing,8end-toend8IPsec,8site-controlled8traffic8engineering,8etc.8 Locators8NEVER8used8for8transport8layer8state,8 e.g.8by8tcp,8udp,8sctp,8etc.8 endttotend#state#now#independent#of#topology# (C)8Saleem8N.8BhaE,8148Jan

19 ILNP:88IdenTfier8(NID)8ProperTes8 I8(NID)8names8a8node,8not8an8interface# Remains#constant8during8the8lifeTme8of8a8 transport8session8 Nodes8may8use8mulTple8NIDs8concurrently:8 only8one8nid8for8a8given8transport8session8 NIDs8can8be8stable8over8Tme8 IPv68NID8formats8supported8by8ILNP:8 e.g.8eui-64,8private8(rfc4941),8cga8(rfc3972)8 Only8NID8is8used8by8TCP,8UDP,8SCTP,8IPsec,8etc.8 (C)8Saleem8N.8BhaE,8148Jan

20 ILNP8 IdenTfier-Locator8Network8Protocol8 1. Why?8 2. What?8 3.How?# (C)8Saleem8N.8BhaE,8148Jan

21 ILNP:88Engineering8 Possible8to8try8 clean8slate,8but8not8practcal.8 Main8architectural8ideas8can8be8applied8as8 extensions8to8both8ipv48and8ipv6:8 current8rfcs8cover8both8 Focus8here8is8on8IPv6,8as8the8engineering8is8 cleaner,8but8ipv48is8also8possible.8 ILNP8extensions8to8IPv68 8ILNPv6:8 Routers8see8an8IPv68packet.8 ILNPv68hosts8see8an8ILNPv68packet.8 (C)8Saleem8N.8BhaE,8148Jan

22 ILNPv68 Can8be8seen8as8a8set8of8extensions8to8IPv6:8 Same8packet8format8as8IPv6,8with8extensions8 No8changes8required8in8core8IPv68routers8 Incrementally8deployable8on8IPv68networks8 Backwards8compaTble8with8IPv68devices8 Split8128-bit8IPv68address:8 64Tbit#Locator#(L64) # #(sub)network#name.# 64Tbit#Iden>fier#(NID) #node#name.# encode#nid#and#l64#into#exis>ng#ipv6#packet# (C)8Saleem8N.8BhaE,8148Jan

23 !!!! IPv68addresses8and8ILNPv68I-L8vectors8 encode#l64#and#nid#values#into#ipv6#packets# IPv6 address (as in RFC RFC4291):! 3 45 bits 8/16 bits 64 bits! ! Unicast Routing Prefix Interface Identifier! !! IPv6#rou>ng#(address)#prefix#! same#syntax,#different#seman>cs#!! ILNPv6 I-L vector (as in RFC6741):!! 64 bits 64 bits! ! Locator Node Identifier (NID)! ! same#syntax#and#seman>cs#as# IPv6#rou>ng#(address)#prefix# so#ipv6#core#routers#work#as#today# these#bits#only#examined#and# acted#upon#by#end#systems# (C)8Saleem8N.8BhaE,8148Jan

24 IPv68packet8header8 8router8view ! ! ! Version Traffic Class Flow Label! ! Payload Length Next Hdr Hop Limit! !! + Source IPv6 Address +!! +- -+!! + +!! !! + Destination IPv6 Address +!! +- -+!! + +!! ! (C)8Saleem8N.8BhaE,8148Jan

25 ILNPv68packet8header8 8host8view ! ! ! Version Traffic Class Flow Label! ! Payload Length Next Hdr Hop Limit! !! + Source Locator +!! !! + Source Identifier +!! !! + Destination Locator +!! !! + Destination Identifier +!! ! (C)8Saleem8N.8BhaE,8148Jan

26 Example:8 Mobile8Hosts8

27 Current8IETF8IP8mobility8model8 Use8of8proxies:8 home8agent8(ha),8foreign8agent8(fa)8 Use8of8indirecTon8via8tunnelling:8 mobile8hosts8looks8to8be8non-mobile8to8correspondent8 nodes8 IP-in-IP8tunnel8can8cause8problems8 Home8address8(HoA)8 8idenTty:8 DNS8lookup8resolves8to8HoA8 Care-of-Address8(CoA)8 8locator8 Similar8principle8for8mobile8networks8 IPv68improvements8for8Mobile8IPv68 (C)8Saleem8N.8BhaE,8148Jan

28 Mobile8IP8(MIP)8 8basic8operaTon8 1) MH arrives at FN, and locates FA (using agent advertisements from FA or by solicitation). HA home network HostA remote network 2) MH completes registration procedure with FA. 4 3) MH updates HA with its new CoA (i.e. the FA). 4) Host A now tries to contact MH. Packets for MH are intercepted by HA. 5 5) HA tunnels the packets from Host A to the CoA for MH (i.e. the FA) 7 6) The FA de-encapsulates the inner IP packet and transmits the packet locally to MH. 7) The packets from MH to Host A are sent directly from the FN. IP-in-IP encapsulation 2 FA 3 data src=hosta dst=mh data src=hosta dst=mh src=hosta dst=coa 6 foreign network Improved8in8Mobile8IPv6:8 mobile8host8can8act8as8its8own8fa8 use8of8binding8update8(bu)8 8send8CoA8to8HostA8 MH (C)8Saleem8N.8BhaE,8148Jan

29 Hard8handoff8 Hard8handoff8 model8used8by8mip8 ILNP8supports8hard8 handoff8also:8 move8from8one8cell8 to8another8 drop8locator8 (prefix)8l 1,8use8 locator8(prefix)8l 28 X X L 2 X L 1 L 2 (C)8Saleem8N.8BhaE,8148Jan

30 ILNP8Locator8Update8(LU)8[1]8 locator8 change8 triggered8 X8 Y8 <IP:8L 1,8L Y >8 <IP:8L Y,8L 1 >8 <IP:8L 2,8L Y >8 LU8(L 2 )8 LU-ACK8(L 2 )8 <IP:8L Y,8L 2 >8 potental8 packet8loss8 Hard#handoff# (similar8to8binding8update8for8mobile8ipv6)8 (new8l8values8can8be8learned8from8ipv68router8advertsements)8 (C)8Saleem8N.8BhaE,8148Jan

31 Sow8handoff8 ILNP8support8sow8 handoff8(similar8 concept8to8cdma)8 Both8old8locator8(L 1 )8 and8new8locator8(l 2 )8 used8in8overlap8 region8 Mobile8host8is8 multhomed8during8 handoff8 X X L 1 L 2 X L 1 L 2 (C)8Saleem8N.8BhaE,8148Jan

32 ILNP8Locator8Update8(LU)8[2]8 locator8 change8 triggered8 X8 <IP:8L 1,8L Y >8 <IP:8L Y,8L 1 >8 <IP:8L 1,8L Y >8 <IP:8L 2,8L Y >8 <IP:8L 2,8L Y >8 LU8(L 2 )8 LU-ACK8(L 2 )8 Y8 <IP:8L Y,8L 2 >8 Soa#handoff# (new8l8values8can8be8learned8from8ipv68router8advertsements)8 (C)8Saleem8N.8BhaE,8148Jan

33 Other8harmonised8funcTonality8...8 Mobile8networks8(not8just8individual8hosts)8 Improved8packet8and8network8security8 MulT-path8transport8protocols8 VM8migraTon/mobility8 Traffic8engineering8opTons8 See8papers:8 h"p://ilnp.cs.st-andrews.ac.uk/88 (C)8Saleem8N.8BhaE,8148Jan

34 Thank8you!8QuesTons?8 ILNP8further8informaTon:8 see8h"p://ilnp.cs.st-andrews.ac.uk/8for8 links8to8rfcs,8papers8and8talks8...8or8come8and8talk8to8me!8 I#have#PhD#posi>ons#open#"## Reading8 8start8off8with:8 Evolving8the8Internet8Architecture8Through8Naming,8 IEEE&JSAC,8Oct h"p://dx.doi.org/ /jsac RFC6740,8Nov820128h"p://tools.iez.org/html/rfc RFC6741,8Nov820128h"p://tools.iez.org/html/rfc (C)8Saleem8N.8BhaE,8148Jan