Locator/ID Separation Protocol (LISP)
|
|
- Marlene Edwards
- 5 years ago
- Views:
Transcription
1 Locator/ID Separation Protocol (LISP) Damien Saucez* INRIA Sophia Antipolis FRNOG 18, December 2 th, 2011 * special thanks to Olivier Bonaventure, Luigi Iannone and Dino Farinacci
2 Disclaimer Not a vendor Not an operator LISP will not solve all the problems try to stay with the facts (now) 2
3 Agenda Why Separating Identifiers from Locators? Locator/ID Separation Protocol (LISP) LISP Use Case Open Questions 3
4 Why Separating Identifiers from Locators? 4
5 Bad Traffic Engineering Outgoing TE is ok Incoming TE is not can be hard, only tricks (BGP, DNS, NAT) Scalability issues Table size (Memory) Churn (CPU) 5
6 The IP Schizophrenia The IP addresses currently used by endhosts play two complementary roles Identifier role: the IP address identifies (with port) the endpoint of transport flows Locator role: the IP address indicates the paths used to reach the endhost these paths are updated by routing protocols after each topology change 6
7 The Locator/Identifier Separation Today, changing the locator means changing the identifier, breaking the pending flows Separating the locator and the identifier roles to avoid breaking the flows Host-based approach Network-based approach 7
8 Host-based Loc/ID split Transport layer Network layer Roles Translates the packets so that Transport layer only sees the host identifier Network layer only sees locators Manages the set of locators Switches from one locator to another upon move or after link failure Hosts maintain flow state 8 [HIP, ILNP, shim6, Six/One, MPTCP(?)]
9 Host-based Loc/ID split Transport layer Network layer Identifier: Ia Roles Translates the packets so that Transport layer only sees the host identifier Network layer only sees locators Manages the set of locators Switches from one locator to another upon move or after link failure Hosts maintain flow state 8 [HIP, ILNP, shim6, Six/One, MPTCP(?)]
10 Host-based Loc/ID split Transport layer Identifier: Ia Roles Translates the packets so that Transport layer only sees the host identifier Network layer Locators: {Ra, Rb} Network layer only sees locators Manages the set of locators Switches from one locator to another upon move or after link failure Hosts maintain flow state 8 [HIP, ILNP, shim6, Six/One, MPTCP(?)]
11 Host-based Loc/ID split Transport layer Specific shim layer Identifier: Ia Roles Translates the packets so that Transport layer only sees the host identifier Network layer Locators: {Ra, Rb} Network layer only sees locators Manages the set of locators Switches from one locator to another upon move or after link failure Hosts maintain flow state 8 [HIP, ILNP, shim6, Six/One, MPTCP(?)]
12 Network-based Loc/ID split A/a A/a a C/c B/b B/b b
13 Network-based Loc/ID split Host s IP stack unchanged Each host has one stable IP address Used as identifier Not globally routable A/a A/a a C/c c B/b B/b b Transport layer Network layer 9
14 Network-based Loc/ID split Each edge router owns Globally routable addresses Used as locators Mapping mechanism is used to find locators associated to one identifier Packets from hosts are modified at the edge before being sent on Internet A/a A/a Host s IP stack unchanged a Each host has one stable IP address Used as identifier Not globally routable C/c c B/b B/b b Transport layer Network layer Locators for C/c: a.1.2.3, b
15 Benefits of Identifier and Locator separation* Reduction of the DFZ routing table size No provider lock-in More traffic control and cost-effective multihoming Mobility 10 * in theory
16 Locator/ID Separation Protocol (LISP) 11
17 Design Goals* No end-systems (hosts) changes (1) Minimize required changes to the Internet infrastructure (2) and the number of routers which have to be modified (5) Avoid or minimize packet loss when EID-to-RLOC mappings need to be performed (7) Be incrementally deployable (3) No router hardware change (4) and minimize router software changes (6) 12 *explicitly stated until -08
18 LISP Philosophy Split the IP address space in two at the border routers Endpoint IDentifiers (EID) identify end-systems and edge routers non-globally routable end systems in a site share the same EID prefix Routing LOCators (RLOC) attached to core routers (router interfaces) globally routable Use Map-and-Encap to glue the two spaces 13
19 Mapping System 2001:DB8B::/ % % 2001:DB8A::/ % % LISP in a nutshell AS4 3/8 AS2 1/ ETR 2001:DB8B::cafe AS5 2001:DB8B::/56 ETR ITR AS3 AS1 2001:DB8A::/56 ITR /8 2001:DB8A::beef 14
20 Mapping System 2001:DB8B::/ % % 2001:DB8A::/ % % LISP in a nutshell AS4 3/8 AS2 1/ ETR 2001:DB8B::cafe AS5 2001:DB8B::/56 ETR ITR AS3 AS1 2001:DB8A::/56 ITR /8 dst: cafe 2001:DB8A::beef 14
21 Mapping System 2001:DB8B::/ % % 2001:DB8A::/ % % LISP in a nutshell AS4 3/8 AS2 1/ ETR 2001:DB8B::cafe AS5 2001:DB8B::/56 ETR ITR dst: cafe AS1 2001:DB8A::/56 ITR AS3 2/8 2001:DB8A::beef 14
22 Mapping System 2001:DB8B::/ % % 2001:DB8A::/ % % LISP in a nutshell AS4 3/8 AS2 1/ ETR 2001:DB8B::cafe AS5 2001:DB8B::/56 ETR Map-Request: 2001:DB8B::cafe? ITR dst: cafe AS1 2001:DB8A::/56 ITR AS3 2/8 2001:DB8A::beef 14
23 Mapping System 2001:DB8B::/ % % 2001:DB8A::/ % % LISP in a nutshell AS4 3/8 AS2 1/ ETR 2001:DB8B::cafe AS5 2001:DB8B::/56 ETR Map-Reply: 2001:DB8B::/ % % ITR dst: cafe AS1 2001:DB8A::/56 ITR AS3 2/8 2001:DB8A::beef 14
24 Mapping System 2001:DB8B::/ % % 2001:DB8A::/ % % LISP in a nutshell AS4 3/8 AS ETR 2001:DB8B::cafe AS5 2001:DB8B::/56 ETR / dst: cafe ITR AS1 2001:DB8A::/56 ITR AS3 2/8 2001:DB8A::beef 14
25 Mapping System 2001:DB8B::/ % % 2001:DB8A::/ % % LISP in a nutshell AS4 3/8 AS2 1/ dst: cafe ETR :DB8B::cafe AS5 2001:DB8B::/56 ETR ITR AS3 AS1 2001:DB8A::/56 ITR /8 2001:DB8A::beef 14
26 Mapping System 2001:DB8B::/ % % 2001:DB8A::/ % % LISP in a nutshell AS4 3/8 AS2 1/ ETR 2001:DB8B::cafe AS5 dst: cafe 2001:DB8B::/56 ETR ITR AS3 AS1 2001:DB8A::/56 ITR /8 2001:DB8A::beef 14
27 Mapping System 2001:DB8B::/ % % 2001:DB8A::/ % % LISP in a nutshell AS4 3/8 AS2 1/ ETR 2001:DB8B::cafe AS5 2001:DB8B::/56 ETR dst: cafe ITR AS3 AS1 2001:DB8A::/56 ITR /8 2001:DB8A::beef 14
28 Mapping System 2001:DB8B::/ % % 2001:DB8A::/ % % LISP in a nutshell AS4 3/8 AS2 1/ ETR 2001:DB8B::cafe AS5 2001:DB8B::/56 ETR ITR AS3 AS1 2001:DB8A::/56 ITR /8 2001:DB8A::beef 15
29 Mapping System 2001:DB8B::/ % % 2001:DB8A::/ % % LISP in a nutshell AS4 3/8 AS2 1/ ETR 2001:DB8B::cafe AS5 2001:DB8B::/56 ETR :DB8A::beef ITR AS1 2001:DB8A::/56 15 ITR AS3 2/8 Endpoint Identifiers (EID)
30 Mapping System 2001:DB8B::/ % % 2001:DB8A::/ % % LISP in a nutshell AS4 3/8 AS2 1/ ETR 2001:DB8B::cafe AS5 2001:DB8B::/56 ETR ITR AS3 AS1 2001:DB8A::/56 ITR /8 2001:DB8A::beef 15
31 Mapping System 2001:DB8B::/ % LISP in a nutshell Routing Locators 100% (RLOC) Routing Locators (RLOC) 2001:DB8A::/ % % AS4 3/8 AS2 1/ ETR 2001:DB8B::cafe AS5 2001:DB8B::/56 ETR ITR AS3 AS1 2001:DB8A::/56 ITR /8 2001:DB8A::beef 15
32 Mapping System 2001:DB8B::/ % % 2001:DB8A::/ % % LISP in a nutshell AS4 3/8 AS2 1/ ETR 2001:DB8B::cafe AS5 2001:DB8B::/56 ETR ITR AS3 AS1 2001:DB8A::/56 ITR /8 2001:DB8A::beef 15
33 Mapping System 2001:DB8B::/ % % 2001:DB8A::/ % % LISP in a nutshell AS4 3/8 AS2 1/ ETR 2001:DB8B::cafe AS5 2001:DB8B::/56 Ingress Tunnel Routers (ITR) Ingress Tunnel Routers (ITR) ETR ITR AS3 AS1 2001:DB8A::/56 ITR /8 2001:DB8A::beef 15
34 Mapping System 2001:DB8B::/ % % 2001:DB8A::/ % % LISP in a nutshell AS4 3/8 AS2 1/ ETR 2001:DB8B::cafe AS5 2001:DB8B::/56 ETR ITR AS3 AS1 2001:DB8A::/56 ITR /8 2001:DB8A::beef 15
35 Mapping System 2001:DB8B::/ % % 2001:DB8A::/ % % LISP in a nutshell AS4 3/8 AS2 1/ ETR Egress Tunnel Routers (ETR) 2001:DB8B::cafe AS5 2001:DB8B::/56 ETR ITR AS3 AS1 2001:DB8A::/56 ITR /8 2001:DB8A::beef 15
36 Mapping System 2001:DB8B::/ % % 2001:DB8A::/ % % LISP in a nutshell AS4 3/8 AS2 1/ ETR 2001:DB8B::cafe AS5 2001:DB8B::/56 ETR ITR AS3 AS1 2001:DB8A::/56 ITR /8 2001:DB8A::beef 15
37 Mapping System 2001:DB8B::/ % % 2001:DB8A::/ % % LISP in a nutshell AS4 3/8 AS2 1/ ETR 2001:DB8B::cafe AS5 2001:DB8B::/56 ETR ITR EID-to-RLOC database AS1 2001:DB8A::/56 ITR AS3 2/8 2001:DB8A::beef 15
38 Mapping System 2001:DB8B::/ % % 2001:DB8A::/ % % LISP in a nutshell AS4 3/8 AS2 1/ ETR 2001:DB8B::cafe AS5 2001:DB8B::/56 ETR ITR AS3 AS1 2001:DB8A::/56 ITR /8 2001:DB8A::beef 15
39 Terminology Ingress Tunnel Router (ITR): a router which accepts a packet which addresses are identifiers. The router maps the destination address of the packet to an RLOC and prepends a LISP header before forwarding the encapsulated packet. Egress Tunnel Router (ETR): a router which accepts a LISP encapsulated packet. The router strips the LISP header and forwards the packet based on the next header 16
40 Terminology EID-to-RLOC Database: a globally distributed database that contains all known EID-prefix to RLOC mappings LISP Cache: EID-to-RLOC Database stored at the ITR LISP Database: EID-to-RLOC Database stored at the ETR 17
41 Under the hood 18
42 Data-plane packets (IP(UDP:4341(LISP(XXX)))) Encapsulating Encapsulated / Version IHL Type of Service Total Length / Identification Flags Fragment Offset OH Time to Live Protocol = 17 Header Checksum Source Routing Locator \ \ Destination Routing Locator / Source Port = xxxx Dest Port = 4341 UDP \ UDP Length UDP Checksum L N L E V I flags Nonce/Map-Version I \ S / Instance ID/Locator Status Bits P / Version IHL Type of Service Total Length / Identification Flags Fragment Offset IH Time to Live Protocol Header Checksum Source EID \ \ Destination EID Fixed Destination Port: 4341 Possible virtualization with Instance ID
43 Data-plane packets (IP(UDP:4341(LISP(XXX)))) Encapsulating Encapsulated / Version IHL Type of Service Total Length / Identification Flags Fragment Offset OH Time to Live Protocol = 17 Header Checksum Source Routing Locator \ \ Destination Routing Locator / Source Port = xxxx Dest Port = 4341 UDP \ UDP Length UDP Checksum L N L E V I flags Nonce/Map-Version I \ S / Instance ID/Locator Status Bits P / Version IHL Type of Service Total Length / Identification Flags Fragment Offset IH Time to Live Protocol Header Checksum Source EID \ \ Destination EID Src/Dst Locators: Source/Destination Locators IPv4 or IPv6 Fixed Destination Port: 4341 Possible virtualization with Instance ID Source/Destination Locators Src/Dst Identifiers: IPv4 or IPv6 or... RLOC AFI independent!
44 Control Plane Packets (IP(UDP:4342(LISP_control))) Map-Request (ITR => MR/ETR) request for a mapping Map-Reply (ETR/MS => ITR) provides the mapping requested by a Map-Request Map-Register (ETR => MS) register a mapping to the mapping system Map-Notify (MS => ETR) confirm a mapping registration IPv4 or IPv6 Header (uses RLOC addresses) / Source Port = xxxx Dest Port = 4342 UDP \ UDP Length UDP Checksum LCM LISP Control Message
45 What is in a mapping? A mapping associates an EID prefix to a list of RLOC of arbitrary AFI Each RLOC receives a priority and a weight L4-flows are balanced between RLOCs of same priority, proportionally to the weight Mappings can be empty to announce holes Mappings are time limited 21 +-> Record TTL R Locator Count EID mask-len ACT A Reserved e c Rsvd Map-Version Number EID-prefix-AFI o r EID-prefix d / Priority Weight M Priority M Weight L o Unused Flags L p R Loc-AFI c \ Locator +->
46 Infrastructure Mapping Database modularity Interworking of LISP and non LISP networks 22
47 Mapping Database modularity Mapping Database MR MS ITR ETR /24
48 Mapping Database modularity LISP+ALT Mapping ebgp Database overlay MR MS ITR ETR /24
49 Mapping Database modularity LISP+ALT IS-IS overlay LISP+ALT Mapping ebgp Database overlay MR MS ITR 23 ETR /24
50 Mapping Database modularity DHT LISP+ALT IS-IS overlay LISP+ALT Mapping ebgp Database overlay MR MS ITR 23 ETR /24
51 Mapping Database modularity DNS-based DHT LISP+ALT IS-IS overlay LISP+ALT Mapping ebgp Database overlay MR MS ITR 23 ETR /24
52 Mapping Database modularity LISP-DDT DNS-based DHT LISP+ALT IS-IS overlay LISP+ALT Mapping ebgp Database overlay MR MS ITR 23 ETR /24
53 Mapping Registration LISP+ALT ebgp overlay MR MS ITR 24 ETR /24
54 Mapping Registration LISP+ALT ebgp overlay MR MS 1. Map-Register: /24, ETR ITR 24 ETR /24
55 Mapping Registration LISP+ALT ebgp overlay 2. BGP Update MR /24 2 MS 1. Map-Register: /24, ETR ITR ETR /24
56 Mapping Registration LISP+ALT ebgp overlay 2. BGP Update MR /24 2 MS 1. Map-Register: /24, ETR 3. Map-Notify: 1 3 ITR /24, ETR ETR /24
57 Mapping retrieval LISP+ALT ebgp overlay MR MS ITR 25 ETR /24
58 Mapping retrieval LISP+ALT ebgp overlay MR MS. Packet to ITR 25 ETR /24
59 Mapping retrieval LISP+ALT ebgp overlay MR MS. Packet to Map-Request for to Encapsulated to MR 1 ITR 25 ETR /24
60 Mapping retrieval LISP+ALT ebgp overlay 3. Map-Request for to MR 3 MS. Packet to Map-Request for to Encapsulated to MR 1 ITR 25 ETR /24
61 Mapping retrieval LISP+ALT ebgp overlay 3. Map-Request for to Packet to MR 2 3 MS 4. Map-Request for Map-Request for to Encapsulated to to ETR 4 Encapsulated to MR 1 ITR 25 ETR /24
62 Mapping retrieval LISP+ALT ebgp overlay 3. Map-Request for to Packet to ITR MR /24, ETR 25 MS 4. Map-Request for Map-Request for to Encapsulated to to ETR Encapsulated to MR 5 5. Map-Reply: 4 ETR /24
63 Interworking LISP /24 xtr-luigi PITR PETR BGP update: /16 xtr-damien / /24
64 Non-LISP to LISP /16 xtr-luigi PITR PETR BGP update: /16 xtr-damien / /24
65 Non-LISP to LISP /16 xtr-luigi PITR 1. Packet to PETR BGP update: / xtr-damien / /24
66 Non-LISP to LISP /16 2. Packet to Encapsulated to xtr-luigi xtr-damien PITR 1. Packet to PETR 2 BGP update: / xtr-damien / /24
67 Non-LISP to LISP /16 2. Packet to Encapsulated to xtr-luigi xtr-damien PITR 1. Packet to PETR 2 BGP update: / xtr-damien 3 3. Packet to / /24
68 LISP to non-lisp /16 xtr-luigi PITR BGP update: /16 PETR xtr-damien / /24
69 LISP to non-lisp /16 xtr-luigi PITR BGP update: /16 PETR xtr-damien 1 1. Packet to / /24
70 LISP to non-lisp /16 2. Packet to xtr-luigi Encapsulated to PETR PITR BGP update: /16 PETR 2 xtr-damien 1 1. Packet to / /24
71 LISP to non-lisp /16 2. Packet to xtr-luigi Encapsulated to PETR PITR BGP update: /16 PETR Packet to xtr-damien Packet to / /24
72 LISP Use Cases 29
73 Low OpEx site multihoming 2001:DB8:F:: ETR-A /24 ETR-B
74 Low OpEx site Basic LISP feature multihoming 2001:DB8:F:: ETR-A /24 ETR-B
75 Low OpEx site multihoming Basic LISP feature ETR-A Primary, ETR-B Backup (IPv6 just in case...) , prio: 1, weight: , prio: 10, weight: :DB8:F:11, prio 100, weight: :DB8:F:: ETR-A /24 ETR-B
76 Low OpEx site multihoming Basic LISP feature ETR-A Primary, ETR-B Backup (IPv6 just in case...) , prio: 1, weight: , prio: 10, weight: :DB8:F:11, prio 100, weight: 100 ETR-A: 60%, ETR-B: 40% (IPv6 just in case...) , prio: 1, weight: , prio: 1, weight: :DB8:F:11, prio 99, weight: :DB8:F:: ETR-A / ETR-B
77 IPv6/IPv4 coexistence IPv6 BGP update: 2001:DB8:A::/56 PxTR 2001:DB8:F::/56 xtr / :DB8:A::/56 31
78 IPv6/IPv4 coexistence IPv6 BGP update: 2001:DB8:A::/56 PxTR 2001:DB8:F::/56 xtr 1 1. Packet to / :DB8:A::/ :DB8:F::1 31
79 IPv6/IPv4 coexistence IPv6 BGP update: 2001:DB8:A::/56 2. Packet to 2001:DB8:F::1 Encapsulated to PxTR 2 PxTR 2001:DB8:F::/56 xtr 1 1. Packet to / :DB8:A::/ :DB8:F::1 31
80 IPv6/IPv4 coexistence IPv6 3. Packet to BGP update: 2001:DB8:A::/56 2. Packet to 2001:DB8:F::1 2001:DB8:F::1 3 Encapsulated to PxTR PxTR 2001:DB8:F::/56 2 xtr 1 1. Packet to / :DB8:A::/ :DB8:F::1 31
81 IPv6/IPv4 coexistence IPv6 BGP update: 2001:DB8:A::/56 PxTR 2001:DB8:F::/56 xtr / :DB8:A::/56 32
82 IPv6/IPv4 coexistence IPv6 1. Packet to BGP update: 2001:DB8:A::/ :DB8:A::42 1 PxTR 2001:DB8:F::/56 xtr / :DB8:A::/56 32
83 IPv6/IPv4 coexistence IPv6 1. Packet to BGP update: 2001:DB8:A::/ :DB8:A::42 2. Packet to 2001:DB8:A::42 1 Encapsulated to xtr PxTR 2001:DB8:F::/56 2 xtr / :DB8:A::/56 32
84 IPv6/IPv4 coexistence IPv6 1. Packet to BGP update: 2001:DB8:A::/ :DB8:A::42 2. Packet to 2001:DB8:A::42 1 Encapsulated to xtr PxTR 2001:DB8:F::/56 2 xtr 2 3. Packet to / :DB8:A::/ :DB8:A::42 32
85 IPv6/IPv4 coexistence IPv6 BGP update: 2001:DB8:A::/56 PxTR 2001:DB8:F::/56 xtr / :DB8:A::/56 32
86 Multi-tenant VPN Sales /25 xtr_s xtr_rd R&D /25 xtr VLAN69 VLAN42 R&D Sales / /25 33
87 Multi-tenant VPN Sales /25 xtr_s xtr_rd R&D /25 VRF R&D: instance-id: /25: xtr_rd VLAN42 xtr VLAN69 Sales VRF Sales: instance-id /25: xtr_s 33 R&D / /25
88 Multi-tenant VPN 1. Packet to 1 Sales / xtr_rd R&D /25 xtr_s VRF R&D: instance-id: /25: xtr_rd VLAN42 xtr VLAN69 Sales VRF Sales: instance-id /25: xtr_s 33 R&D / /25
89 Multi-tenant VPN 1. Packet to 1 Sales /25 xtr_s Packet to xtr_rd Encapsulated to xtr, instance-id: 96 2 R&D /25 VRF R&D: instance-id: /25: xtr_rd VLAN42 xtr VLAN69 Sales VRF Sales: instance-id /25: xtr_s 33 R&D / /25
90 Multi-tenant VPN 1. Packet to 1 Sales /25 xtr_s Packet to xtr_rd Encapsulated to xtr, instance-id: 96 2 R&D /25 VRF R&D: instance-id: /25: xtr_rd VLAN42 xtr VLAN Packet to Sales VRF Sales: instance-id /25: xtr_s 33 R&D / /25 VLAN 69
91 LISP Mobile Nodes LISP+ALT ebgp overlay /24 MR BGP /24 MS / / /24
92 LISP Mobile Nodes LISP+ALT ebgp overlay /24 MR BGP /24 MS 1. Map-Register: /32, / / /24
93 LISP Mobile Nodes LISP+ALT ebgp overlay /24 MR BGP /24 MS / / /24
94 LISP Mobile Nodes LISP+ALT ebgp overlay /24 MR BGP /24 2. Map-Request for MS / / /24
95 LISP Mobile Nodes LISP+ALT ebgp overlay /24 MR BGP /24 MS / / /24
96 LISP Mobile Nodes LISP+ALT ebgp overlay /24 MR BGP /24 MS 3 3. Map-Reply: /32, / / /24
97 LISP Mobile Nodes LISP+ALT ebgp overlay /24 MR BGP /24 MS / / /24
98 LISP Mobile Nodes LISP+ALT ebgp overlay /24 MR BGP /24 MS / / /24
99 LISP Mobile Nodes LISP+ALT ebgp overlay / /24 MR BGP /24 MS /24
100 LISP Mobile Nodes MR LISP+ALT ebgp overlay 1. Map-Register: /32, BGP /24 1 MS / / /24 2. Change notification: /24, /24
101 LISP Mobile Nodes LISP+ALT ebgp overlay / / /24 MR BGP /24 MS /24
102 Open Questions 35
103 Network Resiliency Today, preserving the prefixes reachability is mainly performed locally In LISP, the legacy Internet is EID agnostic Recovery only once ITR discover ETR failure ITR periodically probes RLOCs Important part of LISP WG new charter 36
104 Network Security Who control the mappings control the traffic Denial of service Eavesdropping... Firewalls? DPI? Important part of LISP WG new charter 37
105 Conclusion 38
106 Summary LISP uses map-and-encap to separate IP s ID and locator roles Improve network multi-homing Transparent for the end-users Incrementally deployable Mobility support See 5:55 pm for a configuration hands on (possible to play with live routers) 39
107 Bibliography draft-ietf-lisp draft-ietf-lisp-alt draft-fuller-ddt draft-ietf-lisp-ms draft-ietf-lisp-map-versioning draft-ietf-lisp-mn draft-ietf-lisp-lig draft-ietf-lisp-threats draft-ietf-lisp-sec draft-farinacci-lisp-lcaf Jackab et al., LISP-TREE: A DNS Hierarchy to Support the LISP Mapping System Iannone and Bonaventure, On the cost of caching locacor/id mappings Kim et al, A Deep Dive into the LISP Cache and What ISPs Should Know about It Ohmori et al, Analyses on First Packet Drops of LISP in End-to-End Bidirectional Communications 40
108 ?? /**/ 41
109 Backup 42
110 LISP Philosophy 2/2 Follows the Map-and-Encap principle a mapping system maps EID prefixes onto site router s RLOCs ITR routers encapsulate the packets received from end systems before sending them toward the destination RLOC ETR routers decapsulate the packets received from the Internet before sending them towards the destination end system 43
111 LISP is over UDP UDP to traverse firewalls/nat, limit the impact of ECMP hashing on reordering... Source port is random but per-flow source port is recommended Destination port is fixed to 4341 Checksum is important if IPv6 RLOCs 44
112 Locator Status Bits A vector of 32 bits (L bit set to 1 if LSB is present) Each source locator is mapped to one position in the vector if locator_status_bit[i] = 1 RLOC i is reachable else RLOC i is not reachable Each RLOC has an implicit position in the LSB How to set the bit? What is her meaning? 45
113 Mapping Systems 46
114 NERD: A Not-so-novel EID to RLOC Database 47
115 NERD The only proposed push model Composed of 4 parts a network database format; a change distribution format; a database retrieval/bootstrapping method; a change distribution method Principles An authority computes the mapping database based on the stored registrations The database signed by the authority is stored on servers ITR poll regularly the database servers to update their own mapping database 48
116 LISP+ALT 49
117 LISP+ALT An pull model mapping system A mapping mechanism that relies on an alternate topology to distribute mapping requests to mapping servers LISP ITR routers sending mapping request messages to ALT routers ALT routers forward those mapping messages between themselves on an overlay topology built by using GRE tunnels 50
118 LISP+ALT BGP announces where the mappings can be found Map-Requests are forwarded on the ALT Map-Replies are forwarded on the legacy Internet (directly sent to the ITRs RLOC)! BGP does not give the mappings! 51
119 LISP+ALT 52
120 LISP+ALT issues Complex system with tunnels, BGP protocol (no discussion about policies),... Still relies on lots of error-prone manual configuration Scalability will depend on whether aggregation will be possible If mapping requests are lost due to congestion, difficult to diagnose the problem or send them via another path Security needs to be studied 53
121 LISP+ALT, big question How to deploy it? aggregation vs recovery vs TE how to cache the mappings? 54
122 Solving the reachability problem with the locator status bits C/c >a.1.2.3, p=1 b.1.2.3, p=2 a ETR1 C/c ITR ETR2 b ETR2 notices the failure and informs all ITRs to which it is sending LISP encapsulated packets by setting the reachability bit of ETR1 to 0 55
123 Solving the reachability problem with the locator status bits C/c >a.1.2.3, p=1 b.1.2.3, p=2 Status bits = a ETR1 PAYLOAD C/c ITR ETR2 b ETR2 notices the failure and informs all ITRs to which it is sending LISP encapsulated packets by setting the reachability bit of ETR1 to 0 55
124 Solving the reachability problem with the locator status bits C/c >a.1.2.3, p=1 b.1.2.3, p=2 Status bits = ITR PAYLOAD a ETR1 C/c ETR2 b ETR2 notices the failure and informs all ITRs to which it is sending LISP encapsulated packets by setting the reachability bit of ETR1 to 0 55
125 Solving the reachability problem with the locator status bits C/c >a.1.2.3, p=1 b.1.2.3, p=2 a ETR1 C/c ITR ETR2 b ETR2 notices the failure and informs all ITRs to which it is sending LISP encapsulated packets by setting the reachability bit of ETR1 to 0 55
126 Solving the reachability problem with the locator status bits C/c >a.1.2.3, p=1 b.1.2.3, p=2 a ETR1 C/c ITR ETR2 b Status bits = PAYLOAD ETR2 notices the failure and informs all ITRs to which it is sending LISP encapsulated packets by setting the reachability bit of ETR1 to 0 55
127 Solving the reachability problem with the locator status bits C/c >a.1.2.3, p=1 b.1.2.3, p=2 Status bits = ITR PAYLOAD a ETR1 ETR2 b C/c ETR2 notices the failure and informs all ITRs to which it is sending LISP encapsulated packets by setting the reachability bit of ETR1 to 0 55
128 Solving the reachability problem with the locator status bits C/c >a.1.2.3, p=1 b.1.2.3, p=2 a ETR1 C/c ITR ETR2 b ETR2 notices the failure and informs all ITRs to which it is sending LISP encapsulated packets by setting the reachability bit of ETR1 to 0 55
129 Solving the reachability problem with the locator status bits C/c >a.1.2.3, p=1 b.1.2.3, p=2 ETR1 C/c ITR ETR2 b ETR2 notices the failure and informs all ITRs to which it is sending LISP encapsulated packets by setting the reachability bit of ETR1 to 0 55
130 Solving the reachability problem with the locator status bits C/c >a.1.2.3, p=1 b.1.2.3, p=2 ETR1 C/c ITR ETR2 b Status bits = PAYLOAD ETR2 notices the failure and informs all ITRs to which it is sending LISP encapsulated packets by setting the reachability bit of ETR1 to 0 55
131 Solving the reachability problem with the locator status bits C/c >a.1.2.3, p=1 b.1.2.3, p=2 Status bits = ITR PAYLOAD ETR1 C/c ETR2 b ETR2 notices the failure and informs all ITRs to which it is sending LISP encapsulated packets by setting the reachability bit of ETR1 to 0 55
132 Solving the reachability problem with the locator status bits C/c >a.1.2.3, p=1 >b.1.2.3, p=2 Status bits = ITR PAYLOAD ETR1 C/c ETR2 b ETR2 notices the failure and informs all ITRs to which it is sending LISP encapsulated packets by setting the reachability bit of ETR1 to 0 55
133 Solving the reachability problem with the locator status bits C/c >a.1.2.3, p=1 >b.1.2.3, p=2 ETR1 C/c ITR ETR2 b ETR2 notices the failure and informs all ITRs to which it is sending LISP encapsulated packets by setting the reachability bit of ETR1 to 0 55
134 Solving the reachability problem with the SMR bit C/c >a.1.2.3, p=1 b.1.2.3, p=2 a ETR1 C/c ITR ETR2 b ETR1 has been decommissioned and ETR2 wants that all the sites currently sending encapsulated data to itself update the mapping 56
135 Solving the reachability problem with the SMR bit C/c >a.1.2.3, p=1 b.1.2.3, p=2 C/c ITR ETR2 b ETR1 has been decommissioned and ETR2 wants that all the sites currently sending encapsulated data to itself update the mapping 56
136 Solving the reachability problem with the SMR bit C/c >a.1.2.3, p=1 b.1.2.3, p=2 C/c ITR ETR2 SMR =1 b Map-Request ETR1 has been decommissioned and ETR2 wants that all the sites currently sending encapsulated data to itself update the mapping 56
137 Solving the reachability problem with the SMR bit C/c >a.1.2.3, p=1 b.1.2.3, p=2 SMR =1 ITR Map-Request C/c ETR2 b ETR1 has been decommissioned and ETR2 wants that all the sites currently sending encapsulated data to itself update the mapping 56
138 Solving the reachability problem with the SMR bit C/c >a.1.2.3, p=1 b.1.2.3, p=2 nonce = 1234 ITR Map-Request ETR2 b C/c ETR1 has been decommissioned and ETR2 wants that all the sites currently sending encapsulated data to itself update the mapping 56
139 Solving the reachability problem with the SMR bit C/c >a.1.2.3, p=1 b.1.2.3, p=2 C/c ITR ETR2 b nonce = 1234 Map-Request ETR1 has been decommissioned and ETR2 wants that all the sites currently sending encapsulated data to itself update the mapping 56
140 Solving the reachability problem with the SMR bit C/c >a.1.2.3, p=1 b.1.2.3, p=2 C/c ITR ETR2 b nonce = 1234 Map-Reply ETR1 has been decommissioned and ETR2 wants that all the sites currently sending encapsulated data to itself update the mapping 56
141 Solving the reachability problem with the SMR bit C/c >a.1.2.3, p=1 b.1.2.3, p=2 nonce = 1234 ITR Map-Reply C/c ETR2 b ETR1 has been decommissioned and ETR2 wants that all the sites currently sending encapsulated data to itself update the mapping 56
142 Solving the reachability problem with the SMR bit C/c C/c >a.1.2.3, p=1 >b.1.2.3, p=1 b.1.2.3, p=2 nonce = 1234 ITR Map-Reply C/c ETR2 b ETR1 has been decommissioned and ETR2 wants that all the sites currently sending encapsulated data to itself update the mapping 56
143 Solving the reachability problem with the SMR bit C/c C/c >a.1.2.3, p=1 >b.1.2.3, p=1 b.1.2.3, p=2 C/c ITR ETR2 b ETR1 has been decommissioned and ETR2 wants that all the sites currently sending encapsulated data to itself update the mapping 56
144 Solving the reachability problem with the Echo-Nonce Algorithm xtr I wants to know if the RLOC she uses to reach ETR E is reachable: generate a nonce n when encap to E set E=1 Next time E sends a packet to I, she sets the nonce to n If I receives the nonce within a given time, she considers the RLOC reachable, otherwise E is considered unreachable 57
145 The reachability problem Today, preserving the prefixes reachability is mainly performed locally In LISP, the legacy Internet is EID agnostic 58
146 The reachability problem in today s Internet A/a A/a A/a A/a A/a A/a In today s Internet, routing protocols converge after a link failure to ensure that multihomed prefixes such as A/a remain reachable 59
147 The reachability problem in today s Internet A/a A/a A/a A/a In today s Internet, routing protocols converge after a link failure to ensure that multihomed prefixes such as A/a remain reachable 59
148 The reachability problem in a LISP-based Internet C/c >a.1.2.3, p=1 b.1.2.3, p=2 A/a a A/a A ETR1 A/a C/c ITR B/b B/b B B/b ETR2 b Upon failure of ETR1, A continues to advertise A/a via BGP How can ITR notice that ETR1 failed and that ETR2 should be used instead? 60
149 The reachability problem in a LISP-based Internet C/c >a.1.2.3, p=1 b.1.2.3, p=2 A/a A/a A A/a C/c ITR B/b B/b B B/b ETR2 b Upon failure of ETR1, A continues to advertise A/a via BGP How can ITR notice that ETR1 failed and that ETR2 should be used instead? 60
150 Solving the reachability problem with RLOC Probing Periodically probe the RLOCs to check their reachability 61
151 Host vs Network-based Loc/ID split Both can coexist At home, connected directly to the wall Let my ISP do the stuff for me In the street, calling with Skype over WIFI&3G Prefer WIFI to 3G when possible 62
152 Header details (IP(UDP(LISP(IP)))) Encapsulating Encapsulated / Version IHL Type of Service Total Length / Identification Flags Fragment Offset OH Time to Live Protocol = 17 Header Checksum Source Routing Locator \ \ Destination Routing Locator / Source Port = xxxx Dest Port = 4341 UDP \ UDP Length UDP Checksum L N L E V I flags Nonce/Map-Version I \ S / Instance ID/Locator Status Bits P / Version IHL Type of Service Total Length / Identification Flags Fragment Offset IH Time to Live Protocol Header Checksum Source EID \ \ Destination EID
153 Header details (IP(UDP(LISP(IP)))) Encapsulating Source/Destination Locators Encapsulated / Version IHL Type of Service Total Length / Identification Flags Fragment Offset OH Time to Live Protocol = 17 Header Checksum Source Routing Locator \ \ Destination Routing Locator / Source Port = xxxx Dest Port = 4341 UDP \ UDP Length UDP Checksum L N L E V I flags Nonce/Map-Version I \ S / Instance ID/Locator Status Bits P / Version IHL Type of Service Total Length / Identification Flags Fragment Offset IH Time to Live Protocol Header Checksum Source EID \ \ Destination EID
154 Header details (IP(UDP(LISP(IP)))) Encapsulating Source/Destination Locators Hash based Source Port Encapsulated / Version IHL Type of Service Total Length / Identification Flags Fragment Offset OH Time to Live Protocol = 17 Header Checksum Source Routing Locator \ \ Destination Routing Locator / Source Port = xxxx Dest Port = 4341 UDP \ UDP Length UDP Checksum L N L E V I flags Nonce/Map-Version I \ S / Instance ID/Locator Status Bits P / Version IHL Type of Service Total Length / Identification Flags Fragment Offset IH Time to Live Protocol Header Checksum Source EID \ \ Destination EID
155 Header details (IP(UDP(LISP(IP)))) Encapsulating Source/Destination Locators Hash based Source Port Encapsulated / Version IHL Type of Service Total Length / Identification Flags Fragment Offset OH Time to Live Protocol = 17 Header Checksum Source Routing Locator \ \ Destination Routing Locator / Source Port = xxxx Dest Port = 4341 UDP \ UDP Length UDP Checksum L N L E V I flags Nonce/Map-Version I \ S / Instance ID/Locator Status Bits P / Version IHL Type of Service Total Length / Identification Flags Fragment Offset IH Time to Live Protocol Header Checksum Source EID \ \ Destination EID Fixed Destination port 63
156 Header details (IP(UDP(LISP(IP)))) Encapsulating Source/Destination Locators Hash based Source Port Encapsulated / Version IHL Type of Service Total Length / Identification Flags Fragment Offset OH Time to Live Protocol = 17 Header Checksum Source Routing Locator \ \ Destination Routing Locator / Source Port = xxxx Dest Port = 4341 UDP \ UDP Length UDP Checksum L N L E V I flags Nonce/Map-Version I \ S / Instance ID/Locator Status Bits P / Version IHL Type of Service Total Length / Identification Flags Fragment Offset IH Time to Live Protocol Header Checksum Source EID \ \ Destination EID Fixed Destination port Encap data integrity check 63
157 Header details (IP(UDP(LISP(IP)))) Encapsulating Source/Destination Locators Hash based Source Port Encapsulated N: Nonce present bit N: L: Locator Nonce present Status Bits bit present bit L: E: Locator Echo-Nonce Status request Bits present bit bit E: V: Echo-Nonce Map-Version request present bit I: Instance ID bit / Version IHL Type of Service Total Length / Identification Flags Fragment Offset OH Time to Live Protocol = 17 Header Checksum Source Routing Locator \ \ Destination Routing Locator / Source Port = xxxx Dest Port = 4341 UDP \ UDP Length UDP Checksum L N L E V I flags Nonce/Map-Version I \ S / Instance ID/Locator Status Bits P / Version IHL Type of Service Total Length / Identification Flags Fragment Offset IH Time to Live Protocol Header Checksum Source EID \ \ Destination EID Fixed Destination port Encap data integrity check 63
158 Header details (IP(UDP(LISP(IP)))) Encapsulating Source/Destination Locators Hash based Source Port Encapsulated N: Nonce present bit N: L: Locator Nonce present Status Bits bit present bit L: E: Locator Echo-Nonce Status request Bits present bit bit E: V: Echo-Nonce Map-Version request present bit I: Instance ID bit / Version IHL Type of Service Total Length / Identification Flags Fragment Offset OH Time to Live Protocol = 17 Header Checksum Source Routing Locator \ \ Destination Routing Locator / Source Port = xxxx Dest Port = 4341 UDP \ UDP Length UDP Checksum L N L E V I flags Nonce/Map-Version I \ S / Instance ID/Locator Status Bits P / Version IHL Type of Service Total Length / Identification Flags Fragment Offset IH Time to Live Protocol Header Checksum Source EID \ \ Destination EID Fixed Destination port Encap data integrity check Packet unique identifier or version 63
159 Header details (IP(UDP(LISP(IP)))) Encapsulating Source/Destination Locators Hash based Source Port Encapsulated N: Nonce present bit N: L: Locator Nonce present Status Bits bit present bit L: E: Locator Echo-Nonce Status request Bits present bit bit E: V: Echo-Nonce Map-Version request present bit I: Instance ID bit / Version IHL Type of Service Total Length / Identification Flags Fragment Offset OH Time to Live Protocol = 17 Header Checksum Source Routing Locator \ \ Destination Routing Locator / Source Port = xxxx Dest Port = 4341 UDP \ UDP Length UDP Checksum L N L E V I flags Nonce/Map-Version I \ S / Instance ID/Locator Status Bits P / Version IHL Type of Service Total Length / Identification Flags Fragment Offset IH Time to Live Protocol Header Checksum Source EID \ \ Destination EID Fixed Destination port Encap data integrity check Packet unique identifier or version Source locator reachability or Instance ID or both 63
LISP (Locator/Identifier Separation Protocol)
LISP (Locator/Identifier Separation Protocol) Damien Saucez* June 28 th, 2010 http://inl.info.ucl.ac.be *Thanks to Olivier Bonaventure and Pierre François Department of Computing Science and Engineering
More informationInternet of the future. Master ESTEL - March 17 th 2014
Internet of the future Master ESTEL - March 17 th 2014 Contact information Damien Saucez Email: damien.saucez@inria.fr Mobile: +32 497 19.34.83 Phone: +33 4 89.73.24.18 2 Internet today 3 Internet Protocol
More informationLISP-Click. D. Saucez, V. N. Nguyen and O. Bonaventure. Université catholique de Louvain.
LISP-Click D. Saucez, V. N. Nguyen and O. Bonaventure Université catholique de Louvain http://inl.info.ucl.ac.be A Click implementation of the Locator/ID Separation Protocol 2 The Internet is Broken! 3
More informationLISP: Intro and Update
LISP: Intro and Update RIPE Berlin May, 2008 Vince Fuller (for Dino, Dave, Darrel, et al) http://www.vaf.net/prezos/lisp-ripe-short.pdf Agenda What is LISP? What problem is LISP solving? www.vaf.net/prezos/rrg-prague.pdf
More informationInternet Engineering Task Force (IETF) Category: Experimental ISSN: D. Meyer D. Lewis. Cisco Systems. January 2013
Internet Engineering Task Force (IETF) Request for Comments: 6830 Category: Experimental ISSN: 2070-1721 D. Farinacci Cisco Systems V. Fuller D. Meyer D. Lewis Cisco Systems January 2013 The Locator/ID
More informationLISP: What and Why. RIPE Berlin May, Vince Fuller (for Dino, Dave, Darrel, et al)
LISP: What and Why RIPE Berlin May, 2008 Vince Fuller (for Dino, Dave, Darrel, et al) http://www.vaf.net/prezos/lisp-ripe-long.pdf Agenda What is the problem? What is LISP? Why Locator/ID Separation? Data
More informationNetwork in the Cloud: a Map-and-Encap Approach
Network in the Cloud: a Map-and-Encap Approach Damien Saucez Wassim Haddad Inria Ericsson IEEE CloudNet 12 Enterprise network www ISP1 SOHO ISP2 Internet 2 Enterprise network (contd.) Survey on 57 enterprise
More informationLocator ID Separation Protocol (LISP) Overview
Locator ID Separation Protocol (LISP) is a network architecture and protocol that implements the use of two namespaces instead of a single IP address: Endpoint identifiers (EIDs) assigned to end hosts.
More informationLISP: A Level of Indirection for Routing
LISP: A Level of Indirection for Routing ESCC/Internet2 Joint Techs Workshop University of Hawaii January 20-24, 2008 David Meyer & A Cast of 1000s (Vince Fuller, Darrel Lewis, Eliot Lear, Scott Brim,
More informationIP Mobility Design Considerations
CHAPTER 4 The Cisco Locator/ID Separation Protocol Technology in extended subnet mode with OTV L2 extension on the Cloud Services Router (CSR1000V) will be utilized in this DRaaS 2.0 System. This provides
More informationLISP Locator/ID Separation Protocol
LISP Locator/ID Separation Protocol Hernán Contreras G. Consulting Systems Engineer hcontrer@cisco.com LISP Next Gen Routing Architecture Locator-ID Separation Protocol (LISP) Elevator Pitch LISP is a
More informationVers un renforcement de l architecture Internet : le protocole LISP ( Locator/ID Separation Protocol )
Vers un renforcement de l architecture Internet : le protocole LISP ( Locator/ID Separation Protocol ) JCSA 2013" " " Luigi Iannone! 1 Institut Mines-Télécom Road Map" - Why LISP???! - LISP Data Plane!
More informationAPT: A Practical Transit-Mapping Service Overview and Comparisons
APT: A Practical Transit-Mapping Service Overview and Comparisons draft-jen-apt Dan Jen, Michael Meisel, Dan Massey, Lan Wang, Beichuan Zhang, and Lixia Zhang The Big Picture APT is similar to LISP at
More informationIntegration of LISP and LISP-MN in INET
Institute of Computer Science Chair of Communication Networks Prof. Dr.-Ing. P. Tran-Gia, Matthias Hartmann (University of Wuerzburg, Germany) Michael Höfling, Michael Menth (University of Tuebingen, Germany)
More informationCisco IOS LISP Application Note Series: Lab Testing Guide
Cisco IOS LISP Application Note Series: Lab Testing Guide Version 3.0 (28 April 2011) Background The LISP Application Note Series provides targeted information that focuses on the integration configuration
More informationLISP Router IPv6 Configuration Commands
ipv6 alt-vrf, page 2 ipv6 etr, page 4 ipv6 etr accept-map-request-mapping, page 6 ipv6 etr map-cache-ttl, page 8 ipv6 etr map-server, page 10 ipv6 itr, page 13 ipv6 itr map-resolver, page 15 ipv6 map-cache-limit,
More informationLISP Mobile-Node. draft-meyer-lisp-mn-05.txt. Chris White, Darrel Lewis, Dave Meyer, Dino Farinacci cisco Systems
LISP Mobile-Node draft-meyer-lisp-mn-05.txt Chris White, Darrel Lewis, Dave Meyer, Dino Farinacci cisco Systems EID: dino@cisco.com RLOC: IRTF MobOpts Quebec City July 28 2011 What if... A mobile device
More informationInternet Engineering Task Force (IETF) Category: Experimental. O. Bonaventure Universite catholique de Louvain January 2013
Internet Engineering Task Force (IETF) Request for Comments: 6834 Category: Experimental ISSN: 2070-1721 L. Iannone Telecom ParisTech D. Saucez INRIA Sophia Antipolis O. Bonaventure Universite catholique
More informationIP Routing: LISP Configuration Guide, Cisco IOS Release 15M&T
First Published: 2012-07-27 Last Modified: 2013-03-29 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387)
More informationLISP Parallel Model Virtualization
Finding Feature Information, page 1 Information About, page 1 How to Configure, page 6 Configuration Examples for, page 24 Additional References, page 25 Feature Information for, page 26 Finding Feature
More informationJacking-up the Internet Architecture by separating Location and Identity
Jacking-up the Internet Architecture by separating Location and Identity Luigi Iannone Senior Research Scientist Deutsche Telekom Laboratories Road Map Why we need a new Internet Architecture? How Loc/ID
More informationFuture Routing and Addressing Models
Future Routing and Addressing Models Rob Evans JANET(UK) The JNT Association 2008 Networkshop 36 1 If it ain't broke... BGP is the inter-domain protocol of choice. Not that there's much choice. Carries
More informationLocation ID Separation Protocol. Gregory Johnson -
Location ID Separation Protocol Gregory Johnson - grjohnso@cisco.com LISP - Agenda LISP Overview LISP Operations LISP Use Cases LISP Status (Standards and in the Community) Summary 2 LISP Overview 2010
More informationLISP Generalized SMR
The feature enables LISP xtr (ITR and ETR) to update map cache when there is a change in database mapping. Note There is no configuration commands for this feature. This feature is turned on automatically.
More informationCisco Nexus 7000 Series NX-OS LISP Configuration Guide
First Published: 2011-10-25 Last Modified: 2014-04-25 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387)
More informationCisco Nexus 7000 Series NX-OS LISP Command Reference
First Published: 2016-11-24 Last Modified: -- Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax:
More informationCisco IOS LISP Application Note Series: Access Control Lists
Cisco IOS LISP Application Note Series: Access Control Lists Version 1.1 (28 April 2011) Background The LISP Application Note Series provides targeted information that focuses on the integration and configuration
More informationLISP A Next-Generation Networking Architecture
LISP A Next-Generation Networking Architecture LISP Disjointed RLOC Space Technical Details Version 0.8 30 October 2013 LISP Disjointed RLOC Space Details Agenda LISP Disjointed RLOC Space Technical Details
More informationSeparating identifiers from locators to scale the Internet
Separating identifiers from locators to scale the Internet Olivier Bonaventure Department of Computing Science and Engineering Université catholique de Louvain (UCL) Place Sainte-Barbe, 2, B-1348, Louvain-la-Neuve
More informationDNA SA Border Node Support
Digital Network Architecture (DNA) Security Access (SA) is an Enterprise architecture that brings together multiple building blocks needed for a programmable, secure, and highly automated fabric. Secure
More informationCisco Nexus 7000 Series NX-OS LISP Configuration Guide
First Published: 2016-12-23 Last Modified: 2018-07-05 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387)
More informationTTL Propagate Disable and Site-ID Qualification
The TTL Propagate Disable feature supports disabling of the TTL (Time-To-Live) propagation for implementing the traceroute tool in a LISP network when RLOC and EID belong to different address-family. The
More informationIntended status: Informational. C. White Logical Elegance, LLC. October 24, 2011
Network Working Group Internet-Draft Intended status: Informational Expires: April 26, 2012 D. Farinacci D. Lewis D. Meyer cisco Systems C. White Logical Elegance, LLC. October 24, 2011 LISP Mobile Node
More informationMobility and Virtualization in the Data Center with LISP and OTV
Cisco Expo 2012 Mobility and Virtualization in the Data Center with LISP and OTV Tech DC2 Martin Diviš Cisco, CSE, mdivis@cisco.com Cisco Expo 2012 Cisco and/or its affiliates. All rights reserved. 1 Twitter
More informationGETVPN+LISP Lab Guide
GETVPN+LISP Lab Guide Developers and Lab Proctors This lab was created by: Gregg Schudel, TME LISP Development Team Version 1.0: Created by Gregg Schudel Lab proctor: Gregg Schudel (gschudel@cisco.com)
More informationRequest for Comments: 8112 Category: Informational. I. Kouvelas Arista D. Lewis Cisco Systems May 2017
Independent Submission Request for Comments: 8112 Category: Informational ISSN: 2070-1721 D. Farinacci lispers.net A. Jain Juniper Networks I. Kouvelas Arista D. Lewis Cisco Systems May 2017 Locator/ID
More informationInterdomain Traffic Engineering in a Locator/Identifier Separation Context
1 Interdomain Traffic Engineering in a Locator/Identifier Separation Context Damien Saucez, Benoit Donnet, Luigi Iannone, Olivier Bonaventure Université catholique de Louvain, Belgium Abstract The Routing
More informationLISP: A NOVEL APPROACH FOR FUTURE ATN/IPS
LISP: A NOVEL APPROACH FOR FUTURE ATN/IPS Bernhard Haindl, Manfred Lindner, Wolfgang Kampichler ICAO Meeting 07/2014 2014-07-15 HAINDL Bernhard Trends / Requirements For Future Networks Multihoming / Availability
More informationLISP. - innovative mobility w/ Cisco Architectures. Gerd Pflueger Consulting Systems Engineer Central Europe Version 0.
Version 0.2 22 March 2012 LISP - innovative mobility w/ Cisco Architectures Gerd Pflueger Consulting Systems Engineer Central Europe gerd@cisco.com 2012 Cisco and/or its affiliates. All rights reserved.
More informationOn the Dynamics of Locators in LISP
On the Dynamics of Locators in LISP Damien Saucez 1 and Benoit Donnet 2 1 INRIA, Sophia Antipolis, France 2 Université deliège, Liège, Belgium Abstract. In the Internet, IP addresses play the dual role
More informationIntended status: Experimental Expires: January 10, 2013 InTouch N.V. July 9, 2012
Network Working Group Internet-Draft Intended status: Experimental Expires: January 10, 2013 D. Farinacci D. Meyer cisco Systems J. Snijders InTouch N.V. July 9, 2012 LISP Canonical Address Format (LCAF)
More informationLecture 7 Advanced Networking Virtual LAN. Antonio Cianfrani DIET Department Networking Group netlab.uniroma1.it
Lecture 7 Advanced Networking Virtual LAN Antonio Cianfrani DIET Department Networking Group netlab.uniroma1.it Advanced Networking Scenario: Data Center Network Single Multiple, interconnected via Internet
More informationAN OPEN CONTROL-PLANE IMPLEMENTATION FOR LISP NETWORKS
Proceedings of IC-NIDC2012 AN OPEN CONTROL-PLANE IMPLEMENTATION FOR LISP NETWORKS Dung Phung Chi (1,2), Stefano Secci (2), Guy Pujolle (2), Patrick Raad (3), Pascal Gallard (3) (1) VNU, Hanoi, Vietnam,
More informationValidation of a LISP Simulator
Validation of a LISP Simulator Albert Cabellos-Aparicio, Jordi Domingo-Pascual Technical University of Catalonia Barcelona, Spain Damien Saucez, Olivier Bonaventure Université catholique de Louvain Louvain-La-Neuve,
More informationPrivacy extensions for LISP-MN
UPC - BarcelonaTech Master CANS Thesis Privacy extensions for LISP-MN Student: Alberto Rodríguez Natal Advisor: Albert Cabellos Aparicio Co-Advisor: Loránd Jakab June, 2012 Abstract The current Internet
More informationInternet Engineering Task Force (IETF) Request for Comments: 7835 Category: Informational. O. Bonaventure Universite catholique de Louvain April 2016
Internet Engineering Task Force (IETF) Request for Comments: 7835 Category: Informational ISSN: 2070-1721 D. Saucez INRIA L. Iannone Telecom ParisTech O. Bonaventure Universite catholique de Louvain April
More informationINTRODUCTION 2 DOCUMENT USE PREREQUISITES 2
Table of Contents INTRODUCTION 2 DOCUMENT USE PREREQUISITES 2 LISP MOBILITY MODES OF OPERATION/CONSUMPTION SCENARIOS 3 LISP SINGLE HOP SCENARIO 3 LISP MULTI- HOP SCENARIO 3 LISP IGP ASSIT MODE 4 LISP INTEGRATION
More informationInternet Engineering Task Force (IETF) Request for Comments: Cisco Systems January 2013
Internet Engineering Task Force (IETF) Request for Comments: 6831 Category: Experimental ISSN: 2070-1721 D. Farinacci D. Meyer J. Zwiebel S. Venaas Cisco Systems January 2013 The Locator/ID Separation
More informationEvaluating the Benefits of the Locator/Identifier Separation
Evaluating the Benefits of the Locator/Identifier Separation Bruno Quoitin IP Networking Lab Computer Science and Engineering Dept. Université catholique de Louvain, Belgium (bruno.quoitin@uclouvain.be)
More informationICN IDENTIFIER / LOCATOR. Marc Mosko Palo Alto Research Center ICNRG Interim Meeting (Berlin, 2016)
ICN IDENTIFIER / LOCATOR Marc Mosko Palo Alto Research Center ICNRG Interim Meeting (Berlin, 2016) 1 A brief review of ID/Locators in IETF It s long, and we ll skim over it Then we discuss the CCNx & NDN
More informationDeploying LISP Host Mobility with an Extended Subnet
CHAPTER 4 Deploying LISP Host Mobility with an Extended Subnet Figure 4-1 shows the Enterprise datacenter deployment topology where the 10.17.1.0/24 subnet in VLAN 1301 is extended between the West and
More informationStability and Consistency of the LISP Pull Routing Architecture
Stability and Consistency of the LISP Pull Routing Architecture Yue Li, Damien Saucez, Luigi Iannone, Benoit Donnet Telecom ParisTech France Université Côte d Azur, Inria France Université de Liège, Montefiore
More informationImprovements to LISP Mobile Node
Improvements to LISP Mobile Node Michael Menth, Dominik Klein, and Matthias Hartmann University of Würzburg, Institute of Computer Science, Germany Abstract The Locator/Identifier Separation Protocol (LISP)
More informationLISP-TREE: A DNS Hierarchy to Support the LISP Mapping System
1 LISP-TREE: A DNS Hierarchy to Support the LISP Mapping System Loránd Jakab, Albert Cabellos-Aparicio, Florin Coras, Damien Saucez, and Olivier Bonaventure Abstract During the last years, some operators
More informationEnterprise IPv6 Transition Strategy
Abstract Government mandates, e-business and Internet growth requirements, and impending IPv4 address exhaustion concerns are prompting many enterprises to begin implementing an IPv6 transition strategy.
More informationRouteviews Update + What Is LISP? Regional Interconnection Forum/NAPLA LACNIC XII May 2009 Panama City, Panama David Meyer
Routeviews Update + What Is LISP? Regional Interconnection Forum/NAPLA LACNIC XII May 2009 Panama City, Panama David Meyer dmm@1-4-5.net Agenda A Quick Bit About Routeviews History, Current Events & Futures
More informationLISP in Campus Networks
LISP in Campus Networks Divya Rao CCIE # 25083 Technical Marketing Engineer Enterprise Networking Group Abstract Session ID Title LISP in Campus Networks Abstract This session introduces LISP (Locator/ID
More informationMobility and Virtualization in the Data Center with LISP and OTV
Mobility and Virtualization in the Data Center with LISP and OTV Agenda Mobility and Virtualization in the Data Center Introduction to LISP LISP Data Center Use Cases LAN Extensions: OTV LISP + OTV Deployment
More informationMohammad Hossein Manshaei 1393
Mohammad Hossein Manshaei manshaei@gmail.com 1393 Mobile IP 2 Mobile Network Layer: Problems and Concerns Entities and Terminology in Mobile IP Mobile Indirect Routing Mobile IP Agent Advertisement Registration
More informationInternet Engineering Task Force (IETF) May Signal-Free Locator/ID Separation Protocol (LISP) Multicast
Internet Engineering Task Force (IETF) Request for Comments: 8378 Category: Experimental ISSN: 2070-1721 V. Moreno Cisco Systems D. Farinacci lispers.net May 2018 Abstract Signal-Free Locator/ID Separation
More informationA Location Management-aware Mapping System for ID/Locator Separation to Support Mobility
A Location Management-aware Mapping System for ID/Locator Separation to Support Mobility Mukankunga Bisamaza Angel and Choong Seon Hong Departement of Computer Engineering Kyung Hee University 1 Seocheon,
More informationEnhanced Mobility Control in Mobile LISP Networks
Enhanced Mobility Control in Mobile LISP Networks Moneeb Gohar School of Computer Science and Engineering Kyungpook National University Daegu, South Korea moneebgohar@gmail.com Ji In Kim School of Computer
More informationLISP CHARTER SAM HARTMAN PAINLESS SECURITY, LLC IETF 74 MARCH 25, 2008
LISP CHARTER SAM HARTMAN PAINLESS SECURITY, LLC IETF 74 MARCH 25, 2008 1 CONCERNS TO ADDRESS Accurately describe what LISP separates Describe properties of EIDs Discuss overlapping EIDs and RLOCs CHARTER
More informationInternet Engineering Task Force (IETF) Category: Experimental. D. Meyer Brocade V. Fuller September 2016
Internet Engineering Task Force (IETF) Request for Comments: 7954 Category: Experimental ISSN: 2070-1721 L. Iannone Telecom ParisTech D. Lewis Cisco Systems, Inc. D. Meyer Brocade V. Fuller September 2016
More informationInternet Engineering Task Force (IETF) Request for Comments: D. Lewis Cisco Systems January 2013
Internet Engineering Task Force (IETF) Request for Comments: 6836 Category: Experimental ISSN: 2070-1721 V. Fuller D. Farinacci D. Meyer D. Lewis Cisco Systems January 2013 Locator/ID Separation Protocol
More informationAn Identifier / Locator Split Architecture for Multi-homing and Mobility Support
IJCSNS International Journal of Computer Science and Network Security, VOL.13 No.5, May 2013 13 An Identifier / Locator Split Architecture for Multi-homing and Mobility Support Joonsuk KANG and Koji OKAMURA,
More informationLISP Multicast. Finding Feature Information. Prerequisites for LISP Multicast
The feature introduces support for carrying multicast traffic over a Locator ID Separation Protocol (LISP) overlay. This support currently allows for unicast transport of multicast traffic with head-end
More informationILNP: a whirlwind tour
ILNP: a whirlwind tour Saleem Bhatti, University of St Andrews, UK 2010-10-03 NANOG50. Copyright 2010 Saleem Bhatti. 1 Outline 1. What? Basic information about ILNP. 2. Why? The rationale for ILNP. 3.
More informationFuture Internet Technologies
Future Internet Technologies Future Internet Research Dr. Dennis Pfisterer Institut für Telematik, Universität zu Lübeck http://www.itm.uni-luebeck.de/people/pfisterer New requirements on TCP/IP Growth
More informationFixed Internetworking Protocols and Networks. IP mobility. Rune Hylsberg Jacobsen Aarhus School of Engineering
Fixed Internetworking Protocols and Networks IP mobility Rune Hylsberg Jacobsen Aarhus School of Engineering rhj@iha.dk 1 2011 ITIFN Mobile computing Vision Seamless, ubiquitous network access for mobile
More informationMPLS Segment Routing in IP Networks
MPLS Segment Routing in IP Networks draft-bryant-mpls-unified-ip-sr Stewart Bryant Adrian Farrel John Drake Jeff Tantsura
More informationShim6: Network Operator Concerns. Jason Schiller Senior Internet Network Engineer IP Core Infrastructure Engineering UUNET / MCI
Shim6: Network Operator Concerns Jason Schiller Senior Internet Network Engineer IP Core Infrastructure Engineering UUNET / MCI Not Currently Supporting IPv6? Many parties are going forward with IPv6 Japan
More informationHMS: Towards Hierarchical Mapping System for ID/Locator Separation
HMS: Towards Hierarchical Mapping System for ID/Locator Separation Mukankunga Bisamaza Angel, Rim Rhaw, Jun Lee and Choong Seon Hong Department of Computer Engineering Kyung Hee University 1 Seocheon,
More informationMulti-site Datacenter Network Infrastructures
Multi-site Datacenter Network Infrastructures Petr Grygárek rek 2009 Petr Grygarek, Advanced Computer Networks Technologies 1 Why Multisite Datacenters? Resiliency against large-scale site failures (geodiversity)
More informationTLEN 5710 Capstone. Final Paper. Date 4/25/2014. Defining a Routing Architecture for Multi-Tenant Virtual Data Centers to support Host.
TLEN 5710 Capstone Final Paper Date 4/25/2014 Defining a Routing Architecture for Multi-Tenant Virtual Data Centers to support Host Migration Members - Amit Kolekar, Ebin George, Deepak Pishe, Dipesh Rathod
More informationA Review of IPv6 Multihoming Solutions
A Review of IPv6 Multihoming Solutions Habib Naderi Department of Computer Science University of Auckland Auckland, New Zealand hnad002@aucklanduni.ac.nz Brian E. Carpenter Department of Computer Science
More informationLISP. Migration zu IPv6 mit LISP. Gerd Pflueger Version Feb. 2013
Version 0.7 24 Feb. 2013 LISP Migration zu IP mit LISP Gerd Pflueger gerd@cisco.com 2013 Cisco and/or its affiliates. All rights reserved. Cisco Public 1 2011 Cisco and/or its affiliates. All rights reserved.
More informationinternet technologies and standards
Institute of Telecommunications Warsaw University of Technology 2017 internet technologies and standards Piotr Gajowniczek Andrzej Bąk Michał Jarociński Network Layer The majority of slides presented in
More informationNetwork Working Group. Intended status: Informational Expires: July 27, 2009 January 23, 2009
Network Working Group D. Meyer Internet-Draft D. Lewis Intended status: Informational Cisco Expires: July 27, 2009 January 23, 2009 Status of this Memo Architectural Implications of Locator/ID Separation
More informationSR for SD-WAN over hybrid networks
SR for SD-WAN over hybrid networks to optimize SD-WAN services over long distance https://datatracker.ietf.org/doc/draft-dunbar-sr-sdwan-over-hybrid-networks/ Linda.Dunbar@Huawei.com Mehmet.toy@Verizon
More informationData Center Configuration. 1. Configuring VXLAN
Data Center Configuration 1. 1 1.1 Overview Virtual Extensible Local Area Network (VXLAN) is a virtual Ethernet based on the physical IP (overlay) network. It is a technology that encapsulates layer 2
More informationHIP Host Identity Protocol. October 2007 Patrik Salmela Ericsson
HIP Host Identity Protocol October 2007 Patrik Salmela Ericsson Agenda What is the Host Identity Protocol (HIP) What does HIP try to solve HIP basics Architecture The HIP base exchange HIP basic features
More informationMulticast in Identifier/Locator Separation Architectures
Multicast in Identifier/Locator Separation Architectures Michal Kryczka Universidad Carlos III de Madrid Email: michal.kryczka@imdea.org Abstract Many assumptions which were made during projecting current
More informationID/LOC Separation Network Architecture for Mobility Support in Future Internet
ID/LOC Separation Network Architecture for Mobility Support in Future Internet Nakjung Choi, Taewan You, Jungsoo Park, Taekyoung Kwon and Yanghee Choi School of Computer Science and Engineering, Seoul
More informationChapter 4: outline. 4.5 routing algorithms link state distance vector hierarchical routing. 4.6 routing in the Internet RIP OSPF BGP
Chapter 4: outline 4.1 introduction 4.2 virtual circuit and datagram networks 4.3 what s inside a router 4.4 IP: Internet Protocol datagram format IPv4 addressing ICMP 4.5 routing algorithms link state
More informationA Scalable Routing System Design for the Future Internet
A Scalable Routing System Design for the Future Internet Dan Massey (Colorado State University) Lan Wang (University of Memphis) Beichuan Zhang (University of Arizona) Lixia Zhang (UCLA) 1 Where We Are
More informationLECTURE 8. Mobile IP
1 LECTURE 8 Mobile IP What is Mobile IP? The Internet protocol as it exists does not support mobility Mobile IP tries to address this issue by creating an anchor for a mobile host that takes care of packet
More informationLARGE SCALE IP ROUTING LECTURE BY SEBASTIAN GRAF
LARGE SCALE IP ROUTING LECTURE BY SEBASTIAN GRAF MODULE 05 MULTIPROTOCOL LABEL SWITCHING (MPLS) AND LABEL DISTRIBUTION PROTOCOL (LDP) 1 by Xantaro IP Routing In IP networks, each router makes an independent
More informationCSE 4215/5431: Mobile Communications Winter Suprakash Datta
CSE 4215/5431: Mobile Communications Winter 2013 Suprakash Datta datta@cse.yorku.ca Office: CSEB 3043 Phone: 416-736-2100 ext 77875 Course page: http://www.cse.yorku.ca/course/4215 Some slides are adapted
More informationData Plane Monitoring in Segment Routing Networks Faisal Iqbal Cisco Systems Clayton Hassen Bell Canada
Data Plane Monitoring in Segment Routing Networks Faisal Iqbal Cisco Systems (faiqbal@cisco.com) Clayton Hassen Bell Canada (clayton.hassen@bell.ca) Reference Topology & Conventions SR control plane is
More informationA Deep Dive into the LISP Cache and What ISPs Should Know about It
A Deep Dive into the LISP Cache and What ISPs Should Know about It Juhoon Kim, Luigi Iannone, Anja Feldmann To cite this version: Juhoon Kim, Luigi Iannone, Anja Feldmann. A Deep Dive into the LISP Cache
More informationIdentifier and Locator separation in IP network
Identifier and Locator separation in IP network July 10, 2007 Taewan You (twyou@etri.re.kr) ETRI, PEC Contents IP Addresses in Internet Architecture Overloaded semantic Issues of ID/Loc separation Standardization
More information/14/$ IEEE
The OpenLISP Control Plane Architecture Dung Chi Phung, UPMC and VNU Stefano Secci, UPMC Damien Saucez, INRIA Sophia Antipolis Luigi Iannone, Telecom ParisTech Abstract Among many options tackling the
More informationEvolving your Campus Network with. Campus Fabric. Shawn Wargo. Technical Marketing Engineer BRKCRS-3800
Evolving your Campus Network with Campus Fabric Shawn Wargo Technical Marketing Engineer BRKCRS-3800 Campus Fabric Abstract Is your Campus network facing some, or all, of these challenges? Host Mobility
More informationMobile IP. Mobile IP 1
Mobile IP Mobile IP 1 Motivation for Mobile IP Routing based on IP destination address, network prefix (e.g. 129.13.42) determines physical subnet change of physical subnet implies change of IP address
More informationHAIR: Hierarchical Architecture for Internet Routing
HAIR: Hierarchical Architecture for Internet Routing Re-Architecting the Internet ReArch 09 Wolfgang Mühlbauer ETH Zürich / TU Berlin wolfgang.muehlbauer@tik.ee.ethz.ch Anja Feldmann Luca Cittadini Randy
More informationCSC 4900 Computer Networks: Network Layer
CSC 4900 Computer Networks: Network Layer Professor Henry Carter Fall 2017 Chapter 4: Network Layer 4. 1 Introduction 4.2 What s inside a router 4.3 IP: Internet Protocol Datagram format 4.4 Generalized
More informationLISP-MN. Mobile Networking through LISP. Noname manuscript No. (will be inserted by the editor)
Noname manuscript No. (will be inserted by the editor) LIP-MN Mobile Networking through LIP Alberto Rodríguez Natal Loránd Jakab Marc Portolés Vina Ermagan Preethi Natarajan Fabio Maino David Meyer Albert
More informationModule 28 Mobile IP: Discovery, Registration and Tunneling
Module 28 Mobile IP: Discovery, and Tunneling Learning Objectives Introduction to different phases of Mobile IP Understanding how a mobile node search the agents using Discovery process Understand how
More informationSecurizarea Calculatoarelor și a Rețelelor 32. Tehnologia MPLS VPN
Platformă de e-learning și curriculă e-content pentru învățământul superior tehnic Securizarea Calculatoarelor și a Rețelelor 32. Tehnologia MPLS VPN MPLS VPN 5-ian-2010 What this lecture is about: IP
More information