1. LISP Map Server LISP WG IETF-74 San Francisco draft-fuller-lisp-ms-00.txt Vince Fuller & Dino Farinacci

2. LISP-MS IntroductionIETF-74 LISP BOF, March, 2009Slide 2 Introduction to LISP-MS draft-fuller-lisp-ms-00.txt Goal: eliminate ALT complexity in xTRs Map-Servers are co-located in access- layer LISP-ALT routers –first-hop from ITR called “Map-Resolver” –last-hop to ETR called “Map-Server” –conceptually akin to DNS resolver/server Transit LISP-ALT routers unchanged

3. LISP-MS IntroductionIETF-74 LISP BOF, March, 2009Slide 3 Map-Resolvers & Map-Servers Map-Resolver accepts Map-Request from ITR that needs an EID-to-RLOC mapping; forwards to ALT network –Optional caching functionality being developed Map-Server receives Map-Request from ALT and forwards to ETR –ETR returns Map-Reply to ITR Transit LISP-ALT routers forward Map- Request on the ALT network (no change) Map-Resolvers and Map-Servers are separated functions but can be co-located

4. LISP-MS IntroductionIETF-74 LISP BOF, March, 2009Slide 4 Map-Requests Map-Request originated by ITRs is LISP- encapsulated and sent on UDP port 4341 (LISP data port) Map-Resolver decapsulates and forwards Map-Request on ALT Map-Server receives Map-Request from ALT and encapsulates with LISP header, sends to ETR on UDP port 4341 ETR decapsulates, processes Map-Request and sends Map-Reply to requesting ITR

5. LISP-MS IntroductionIETF-74 LISP BOF, March, 2009Slide 5 Originating EID prefixes ETRs are the “authoritative” source of EID- to-RLOC mappings Registration process with Map-Servers –In place of BGP session to ALT –Send EID prefix set (verified by Map-Server) –Shared-key authentication New Map-Register message

6. LISP-MS IntroductionIETF-74 LISP BOF, March, 2009Slide 6 Map-Register Example ETR Map-Resolver LISP-ALT 2.2.2.2 ITR 65.1.1.1 66.2.2.2 Map-Server 1.1.1.1 240.1.1.0/24 Transit Legend: EIDs -> Green Locators -> Red BGP-over-GRE Physical link Map-Register BGP update (1) 2.2.2.2 -> 66.2.2.2 LISP Map-Register (in AH) (2) 240.1.1.0/24 240.1.0.0/16 (3)

7. LISP-MS IntroductionIETF-74 LISP BOF, March, 2009Slide 7 Map-Request Example Legend: EIDs -> Green Locators -> Red BGP-over-GRE Physical link Map-Request path ETR Map-Resolver LISP-ALT 2.2.2.2 ITR 65.1.1.1 1.1.1.1 -> 240.1.1.1 Map-Request UDP 4342 1.1.1.1 -> 240.1.1.1 Map-Request UDP 4342 1.1.1.1 -> 65.1.1.1 LISP Packet UDP 4341 66.2.2.2 Map-Server 1.1.1.1 -> 240.1.1.1 Map-Request UDP 4342 66.2.2.2 -> 2.2.2.2 LISP Packet UDP 4341 1.1.1.1 240.1.0.0/16 (1) (2) (3) (4) (6) (5) 2.2.2.2 -> 1.1.1.1 Map-Reply UDP 4342 Transit

8. LISP-MS IntroductionIETF-74 LISP BOF, March, 2009Slide 8 Interoperates with LISP-ALT Sites ETR LISP-ALT 2.2.2.2 ITR 65.1.1.1 66.2.2.2 1.1.1.1 ETR ITR ETR LISP-ALT Legend: BGP-over-GRE GRE only Physical link Map-Server Site Map-Server user site Map-Server user site LISP-ALT site LISP-ALT site Low OpEx GRE-only site Low OpEx GRE-only site Map-Resolver Map-Server Map-Resolver Map-Server

9. LISP-MS IntroductionIETF-74 LISP BOF, March, 2009Slide 9 Future Work Negative cache entries in ITRs Caching in Map-Resolvers –Change to service model: resolver must originate Map-Requests (instead of just forwarding) to cache Map-Replies Others?