Presentation is loading. Please wait.

Presentation is loading. Please wait.

Dave Meyer & Dino Farinacci LISP Designers: Dave Meyer, Vince Fuller, Darrel Lewis, Andrew Partan, John Zwiebel, Scott Brim, Noel Chiappa & Dino Farinacci.

Published byMeagan Hodges Modified over 8 years ago

Similar presentations

Presentation on theme: "Dave Meyer & Dino Farinacci LISP Designers: Dave Meyer, Vince Fuller, Darrel Lewis, Andrew Partan, John Zwiebel, Scott Brim, Noel Chiappa & Dino Farinacci."— Presentation transcript:

1 Dave Meyer & Dino Farinacci LISP Designers: Dave Meyer, Vince Fuller, Darrel Lewis, Andrew Partan, John Zwiebel, Scott Brim, Noel Chiappa & Dino Farinacci LISP: An Architectural Solution to Multi-homing, Traffic Engineering, and Internet Route Scaling

2 LISP ArchitectureNanog 45 - Jan 2009Slide 2 Agenda Problem Statement Architectural Concepts –Separating Identity and Location –Map-n-Encap to Implement Level of Indirection Unicast & Multicast Data Plane Operation Mapping Database Mechanism –LISP-ALT Locator Reachability Interworking LISP Sites and Legacy Sites Deployment Status –Present Prototype Implementation –Present World-Wide LISP Pilot Network Q&A

3 LISP ArchitectureNanog 45 - Jan 2009Slide 3 Problem Statement What provoked this? –Stimulated by problem statement effort at the Amsterdam IAB Routing Workshop on October 2006 RFC 4984 –More info on problem statement: http://www.vaf.net/~vaf/apricot-plenary.pdf

4 LISP ArchitectureNanog 45 - Jan 2009Slide 4 Scaling Internet Routing State

5 LISP ArchitectureNanog 45 - Jan 2009Slide 5 Routing Table Size Problem 10^7 routes Before LISP - all this state in red circle After LISP - this amount in red circle A 16-bit number!

6 LISP ArchitectureNanog 45 - Jan 2009Slide 6 Growth in Multi-Homing Provider A 10.0.0.0/8 Provider B 11.0.0.0/8 S (1) Improve site multi-homing R1R2 a) Can control egress with IGP routing b) Hard to control ingress without more specific route injection c) Desire to be low OpEx multi-homed (avoid complex protocols, no outsourcing) (2) Improve ISP multi-homing a) Same problem for providers, can control egress but not ingress, more specific routing only tool to circumvent BGP path selection BGP

7 LISP ArchitectureNanog 45 - Jan 2009Slide 7 Growth in Multi-Homing Provider A 10.0.0.0/8 Provider B 11.0.0.0/8 S R1R2 (3) Decouple site addressing from provider a) Avoid renumbering when site changes providers b) Site host and router addressing decoupled from core topology (4) Add new addressing domains a) From possibly separate allocation entities (5) Do 1) through 4) and reduce the size of the core routing tables

8 LISP ArchitectureNanog 45 - Jan 2009Slide 8 Separating (or adding) an Address Changing the semantics of the IP address LocatorID Locator.10.0.0.1 ID 2001:0102:0304:0506:1111:2222:3333:4444IPv6: ID & Location 209.131.36.158IPv4: ID & Location If PI, get new locator If PA, get new ID

9 LISP ArchitectureNanog 45 - Jan 2009Slide 9 Why the Separation? Level of Indirection allows us to: –Keep either ID or Location fixed while changing the other –Create separate namespaces which can have different allocation properties By keeping IDs fixed –Assign fixed addresses that never change to hosts and routers at a site You can change Locators –Now the sites can change providers –Now the hosts can move

10 LISP ArchitectureNanog 45 - Jan 2009Slide 10 Some Brief Definitions IDs or EIDs –End-site addresses for hosts and routers at the site –They go in DNS records –Generally not globally routed on underlying infrastructure –New namespace RLOCs or Locators –Infrastructure addresses for LISP routers and ISP routers –Hosts do not know about them –They are globally routed and aggregated along the Internet connectivity topology –Existing namespace

11 LISP ArchitectureNanog 45 - Jan 2009Slide 11 Provider A 10.0.0.0/8 Provider B 11.0.0.0/8 S Multi-Level Addressing EIDs are inside of sites RLOCs used in the core R2R1

12 LISP ArchitectureNanog 45 - Jan 2009Slide 12 What is LISP? Locator/ID Separation Protocol Ground rules for LISP –Network-based solution –No changes to hosts whatsoever –No new addressing changes to site devices –Very few configuration file changes –Imperative to be incrementally deployable –Address family agnostic

13 LISP ArchitectureNanog 45 - Jan 2009Slide 13 What is LISP? “Jack-Up” or “Map-n-Encap” Host Stack: supplies IDs Router: supplies RLOCs by adding new header

14 LISP ArchitectureNanog 45 - Jan 2009Slide 14 draft-farinacci-lisp-11.txt 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ / |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 | Dest Port (4341) | UDP +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ \ | UDP length | UDP Checksum | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ / | Locator Reach Bits | LISP +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ \ | Nonce | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ / |Version| IHL |Type of Service| Total Length | / +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ / | Identification |Flags| Fragment Offset | / +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ IH | Time to Live | Protocol | Header Checksum | \ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ \ | Source EID | \ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ \ | Destination EID | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

15 LISP ArchitectureNanog 45 - Jan 2009Slide 15 LISP for IPv6 Transition LISP HeaderIPv4 Header IPv4 Payload LISP HeaderIPv6 Header IPv6 Payload Legend: EIDs -> Green Locators -> Red LISP HeaderIPv4 HeaderIPv6 Header IPv6 Payload LISP HeaderIPv6 HeaderIPv4 Header IPv4 Payload

16 LISP ArchitectureNanog 45 - Jan 2009Slide 16 What is LISP? Data plane –Design for encapsulation and tunnel router placement –Design for locator reachability –Data-triggered mapping service Control plane –Design for a scalable mapping service –Examples are: CONS, NERD, ALT, EMACS

17 LISP ArchitectureNanog 45 - Jan 2009Slide 17 LISP Network Elements Ingress Tunnel Router (ITR) –Finds EID to RLOC mapping –Encapsulates to Locators at source site Egress Tunnel Router (ETR) –Owns EID to RLOC mapping –Decapsulates at destination site xTR –Term used when not referring to directionality –Basically a LISP router

18 LISP ArchitectureNanog 45 - Jan 2009Slide 18 Unicast Packet Forwarding Provider A 10.0.0.0/8 Provider B 11.0.0.0/8 S ITR D ETR Provider Y 13.0.0.0/8 Provider X 12.0.0.0/8 S1 S2 D1 D2 PI EID-prefix 1.0.0.0/8 PI EID-prefix 2.0.0.0/8 DNS entry: D.abc.com A 2.0.0.2 EID-prefix: 2.0.0.0/8 Locator-set: 12.0.0.2, priority: 1, weight: 50 (D1) 13.0.0.2, priority: 1, weight: 50 (D2) Mapping Entry 1.0.0.1 -> 2.0.0.2 11.0.0.1 -> 12.0.0.2 Legend: EIDs -> Green Locators -> Red 1.0.0.1 -> 2.0.0.2 11.0.0.1 -> 12.0.0.2 1.0.0.1 -> 2.0.0.2 12.0.0.2 13.0.0.2 10.0.0.1 11.0.0.1 Policy controlled by destination site

19 LISP ArchitectureNanog 45 - Jan 2009Slide 19 Multicast Packet Forwarding Keep EID state out of core network No head-end replication at source site Packets only go to receiver sites No changes to hosts, site routers, core routers Use existing protocols Support PIM SSM, don’t preclude ASM & Bidir Have separate unicast and multicast policies

20 LISP ArchitectureNanog 45 - Jan 2009Slide 20 Multicast Packet Forwarding Group addresses have neither ID or Location semantics –G is topologically opaque - can be used everywhere (S-EID, G) –S-EID is source host –G is group address receivers join to –State resides in source and receiver sites (S-RLOC, G) –S-RLOC is ITR on multicast tree –G is group address receivers join to –State resides in core

21 LISP ArchitectureNanog 45 - Jan 2009Slide 21 Multicast Packet Forwarding Provider A 10.0.0.0/8 Provider B 11.0.0.0/8 S ITR D ETR Provider Y 13.0.0.0/8 Provider X 12.0.0.0/8 S1 S2 D1 D2 12.0.0.2 13.0.0.2 10.0.0.1 11.0.0.1 R11 R1R2 R12 ETR R21 ETR R22 ETR R3 11.0.0.11 13.0.0.12 13.0.0.21 13.0.0.22 (S-EID,G) PIM JP (S-EID,G) PIM JP (S-EID,G) PIM JP (S2-RLOC,G) PIM JP (S-EID,G) PIM JP 1.0.0.1 (S2-RLOC,G) PIM JP Legend: EIDs -> Green Locators -> Red site or core PIM router regular PIM JP unicast PIM JP (S-EID,G) PIM JP

22 LISP ArchitectureNanog 45 - Jan 2009Slide 22 Multicast Packet Forwarding Provider A 10.0.0.0/8 Provider B 11.0.0.0/8 S ITR D ETR Provider Y 13.0.0.0/8 Provider X 12.0.0.0/8 S1 S2 D1 D2 12.0.0.2 13.0.0.2 10.0.0.1 11.0.0.1 R11 R1R2 R12 ETR R21 ETR R22 ETR R3 11.0.0.11 13.0.0.12 13.0.0.21 13.0.0.22 1.0.0.1 1.0.0.1 -> G 11.0.0.1 -> G 1.0.0.1 -> G ETR

23 LISP ArchitectureNanog 45 - Jan 2009Slide 23 When the xTR has no Mapping Need a scalable EID to Locator mapping lookup mechanism Network based solutions –Have query/reply latency –Can have packet loss characteristics –Or, have a full table like BGP does How does one design a scalable Mapping Service?

24 LISP ArchitectureNanog 45 - Jan 2009Slide 24 You need a “map” before you can “encap” We have designed several mapping database protocols –CONS, NERD, EMACS, ALT –Tradeoff push versus pull benefit/cost –Needs to be scalable to 10 10 entries ALT has the most promise –We are deploying ALT Mapping Database Designs

25 LISP ArchitectureNanog 45 - Jan 2009Slide 25 What is LISP+ALT? EID namespace is used at the site RLOC namespace is used in the Internet core Mappings need to be authoritative and reside at site ETRs Advertise EID-prefixes in BGP on an alternate topology of GRE tunnels ITRs get mappings by routing Map-Requests on ALT topology ETRs respond with Map-Replies

26 LISP ArchitectureNanog 45 - Jan 2009Slide 26 How LISP+ALT Works Legend: EIDs -> Green Locators -> Red GRE Tunnel Low Opex Physical link Data Packet Map-Request Map-Reply ETR ITR EID-prefix 240.1.2.0/24 ITR EID-prefix 240.1.1.0/24 ALT EID-prefix 240.2.1.0/24 240.0.0.1 -> 240.1.1.1 1.1.1.1 2.2.2.2 3.3.3.3 240.0.0.1 -> 240.1.1.1 EID-prefix 240.0.0.0/24 1.1.1.1 -> 11.0.0.1 240.0.0.1 -> 240.1.1.1 11.0.0.1 -> 1.1.1.1 ALT-rtr 12.0.0.1 11.0.0.1 ? 240.0.0.1 -> 240.1.1.1 11.0.0.1 -> 240.1.1.1 ? 240.0.0.1 -> 240.1.1.1 11.0.0.1 -> 240.1.1.1 ? <- 240.1.1.0/24 <- 240.1.2.0/24 < - 240.1.0.0/16 ?

27 LISP ArchitectureNanog 45 - Jan 2009Slide 27 Locator Reachability Provider A 10.0.0.0/8 Provider B 11.0.0.0/8 S ITR D ETR Provider Y 13.0.0.0/8 Provider X 12.0.0.0/8 S1 S2 D1 D2 PI EID-prefix 2.0.0.0/8 EID-prefix: 2.0.0.0/8 Locator-set: 12.0.0.2, priority: 1, weight: 50 (D1) 13.0.0.2, priority: 1, weight: 50 (D2) Mapping Entry Legend: EIDs -> Green Locators -> Red 12.0.0.2 13.0.0.2 10.0.0.1 11.0.0.1 -> ordinal 0 -> ordinal 1 loc-reach-bits: 0x0000 0003 S S D D 0003 D1 D2 D1 D2 7654 3210 b’xxxx xxxx’ 0002 D2 X X X

28 LISP ArchitectureNanog 45 - Jan 2009Slide 28 LISP Interworking LISP will not be widely deployed day-1 Need a way for LISP-capable sites to communicate with rest of Internet Two basic Techniques –LISP Network Address Translators (LISP-NAT) –Proxy Tunnel Routers (PTRs)

29 LISP ArchitectureNanog 45 - Jan 2009Slide 29 LISP Interworking These combinations must be supported –Non-LISP site to non-LISP site Today’s Internet –LISP site to LISP site Encapsulation over IPv4 makes this work IPv4-over-IPv4 or IPv6-over-IPv4 –LISP-R site to non-LISP site When LISP site has PI or PA routable addresses –LISP-NR site to non-LISP site When LISP site has PI or PA non-routable addresses

30 LISP ArchitectureNanog 45 - Jan 2009Slide 30 Interworking using LISP-NAT Legend: LISP Sites -> Green (and EIDs) non-LISP Sites -> Red (and RLOCs) xTR R-prefix 65.1.0.0/16 R-prefix 65.2.0.0/16 R-prefix 65.3.0.0/16 65.0.0.0/12 Encapsulate 65.3.3.3 -> 66.3.3.3 1.3.3.3 -> 65.3.3.3 65.3.3.3 -> 1.3.3.3 Forward 66.0.0.0/12 Forward Local/Uncoordinated Solution 1.1.1.1 -> 1.2.2.2 66.1.1.1 -> 66.2.2.2 NR-prefix 1.2.0.0/16 NR-prefix 1.1.0.0/16 NR-prefix 1.3.0.0/16 66.1.1.1 66.2.2.2 66.3.3.3 66.3.3.3 -> 65.3.3.3 Translate

31 LISP ArchitectureNanog 45 - Jan 2009Slide 31 R-prefix 65.1.0.0/16 R-prefix 65.2.0.0/16 R-prefix 65.3.0.0/16 65.0.0.0/12 66.0.0.0/12 Infrastructure Solution Legend: LISP Sites -> Green (and EIDs) non-LISP Sites -> Red (and RLOCs) xTR NR-prefix 1.2.0.0/16 NR-prefix 1.1.0.0/16 NR-prefix 1.3.0.0/16 66.1.1.1 66.2.2.2 Interworking using PTRs 66.3.3.3 65.9.2.1 PTR BGP Advertise: 1.0.0.0/8 PTR BGP Advertise: 1.0.0.0/8 PTR BGP Advertise: 1.0.0.0/8 65.9.3.1 65.9.1.1 65.1.1.1 -> 1.1.1.1 (1) 1.1.1.1 -> 65.1.1.1 Forward Natively (3) Encapsulate 65.1.1.1 -> 1.1.1.1 65.9.1.1 -> 66.1.1.1 (2)

32 LISP ArchitectureNanog 45 - Jan 2009Slide 32 Prototype Implementation cisco has a LISP prototype implementation Supports: draft-farinacci-lisp-11.txt draft-fuller-lisp-alt-03.txt draft-lewis-lisp-interworking-02.txt Software switching only Supports LISP for both IPv4 and IPv6 –ITR, ETR, and PTR –LISP-NAT for IPv4 only

33 LISP ArchitectureNanog 45 - Jan 2009Slide 33 Platform and OS NX-OS runs on Linux Used as a research platform Can run on Nexus 7K/5K & Service Blades

34 LISP ArchitectureNanog 45 - Jan 2009Slide 34 Implementation Schedule Started implementation at Prague IETF –March 2007 Implementation put on pilot network –July 2007 Since then released over 90 release builds –Releases occur on demand with new features and bug fixes concurrently We have phased testing –Unit/System Test done in development –Alpha test done on pilot network by Dave/Darrel/Vince/John/Andrew –Beta test done on pilot network by volunteers

35 LISP ArchitectureNanog 45 - Jan 2009Slide 35 Other Coding Efforts IOS implementation under-way –Loc/ID split functionality Considering IOS-XR implementation –TE-ITR/TE-ETR functionality OpenLISP implementation been available for FreeBSD a while and being updated –For testing the specs Considering native Linux implementation Any other efforts?

36 LISP ArchitectureNanog 45 - Jan 2009Slide 36 LISP Deployment LISP Pilot Network Operational –Deployed for nearly 2 years –~24 sites across 5 countries US, UK, BE, JP, UY –Uses the NX-OS Titanium Platform IOS and OpenLISP platforms to be added –EID-Prefixes used 153.16.0.0/16 and 2610:00d0::/32 –RLOCs used Current site attachment points to the Internet

37 LISP ArchitectureNanog 45 - Jan 2009Slide 37 LISP Deployment LISP-ALT Infrastructure Built –GRE tunnels numbered out of 240.0.0.0/4 –LISP-ALT uses 32-bit AS numbers Format is 32656.x (ASDot notation) –EID-prefixes BGP advertised from ‘lisp’ VRF –RLOCs in default VRF

38 LISP ArchitectureNanog 45 - Jan 2009Slide 38

39 LISP ArchitectureNanog 45 - Jan 2009Slide 39 Naming & Addressing Domain name lisp4.net –Contains hosts and routers from IPv4 EID space Domain name lisp6.net –Contains hosts and routers from IPv6 EID space

40 LISP ArchitectureNanog 45 - Jan 2009Slide 40 Naming & Addressing IPv4 EID Assignments from 153.16.0.0/16 –North America 153.16.0.0/20 /22 for regions in the US –Europe 153.16.32.0/20 –Asia 153.16.64.0/20 /21 for regions in Asia –Africa 153.16.96.0/20 –Latin America 153.16.128.0/20 –Reserved 153.16.{160,192,224}.0/20

41 LISP ArchitectureNanog 45 - Jan 2009Slide 41 Naming & Addressing IPv6 EID Assignments from 2610:00d0::/32 –2610:00d0:x000::/36 x is continent –2610:00d0:xy00::/40 y is region in continent x –2610:00d0:xy00::/48 Sites allocate out of /48

42 LISP ArchitectureNanog 45 - Jan 2009Slide 42 LISP Deployment LISP Interworking Deployed –Have LISP 1-to-1 address translation working http://www.translate.lisp4.net –Proxy Tunnel Router (PTR) IPv4 PTRs: –Andrew, ISC, and UY IPv6 PTRs: –Dave (UofO), ISC, and UY http://www.lisp6.net reachable through IPv6 PTR http://www.ptr.lisp4.net reachable through IPv4 PTR

43 LISP ArchitectureNanog 45 - Jan 2009Slide 43 Other Uses for LISP SLBs in Data Centers –ETRs directly connected to servers –ITRs at Data Center edge A/V Mobile Truck Roll –Avoid renumber at each event BGP-free Core –Intra-AS avoiding storing external routes –RLOCs are PE routers Building topological hierarchy with flat addressing –MAC addressing in L2 networks MAC address mobility for “extended subnets” In an environment of shortage address supply

44 LISP ArchitectureNanog 45 - Jan 2009Slide 44 Open Policy for LISP It’s been >2 years since the IAB Routing & Addressing WS –Some of us committed to working in the IETF and IRTF in an open environment This is not a Cisco only effort –We have approached and recruited others –There are no patents (cisco has no IPR on this) –All documents are Internet Drafts We need and seek new designers, implementors, and testers We need research analysis We want this to be an open effort!

45 LISP ArchitectureNanog 45 - Jan 2009Slide 45 Internet Drafts draft-farinacci-lisp-11.txt draft-farinacci-lisp-multicast-01.txt draft-fuller-lisp-alt-03.txt draft-lewis-lisp-interworking-02.txt draft-meyer-lisp-eid-block-01.txt draft-meyer-loc-id-implications-01.txt draft-mathy-lisp-dht-00.txt draft-iannone-openlisp-implementation-02.txt draft-brim-lisp-analysis-00.txt draft-meyer-lisp-cons-04.txt draft-lear-lisp-nerd-04.txt draft-curran-lisp-emacs-00.txt

46 LISP ArchitectureNanog 45 - Jan 2009Slide 46 References Public mailing list: lisp@ietf.org More info at: http://www.lisp4.net http://www.lisp6.net

47 LISP ArchitectureNanog 45 - Jan 2009Slide 47

Download ppt "Dave Meyer & Dino Farinacci LISP Designers: Dave Meyer, Vince Fuller, Darrel Lewis, Andrew Partan, John Zwiebel, Scott Brim, Noel Chiappa & Dino Farinacci."

Similar presentations

© Antônio M. Alberti 2011 Host Identification and Location Decoupling: A Comparison of Approaches Bruno Magalhães Martins Antônio Marcos Alberti.

© Antônio M. Alberti 2011 Host Identification and Location Decoupling: A Comparison of Approaches Bruno Magalhães Martins Antônio Marcos Alberti.
LISP Mobile Node LISP Mobile Node draft-meyer-lisp-mn-00.txt Dino Farinacci, Vince Fuller, Darrel Lewis and David Meyer IETF StockholmHiroshima LISP Working.

LISP Mobile Node LISP Mobile Node draft-meyer-lisp-mn-00.txt Dino Farinacci, Vince Fuller, Darrel Lewis and David Meyer IETF StockholmHiroshima LISP Working.
Overlay Transport Virtualization (OTV)

Overlay Transport Virtualization (OTV)
Why do current IP semantics cause scaling issues? −Today, “addressing follows topology,” which limits route aggregation compactness −Overloaded IP address.

Why do current IP semantics cause scaling issues? −Today, “addressing follows topology,” which limits route aggregation compactness −Overloaded IP address.
CPSC 441 - Network Layer4-1 IP addresses: how to get one? Q: How does a host get IP address? r hard-coded by system admin in a file m Windows: control-panel->network->configuration-

CPSC Network Layer4-1 IP addresses: how to get one? Q: How does a host get IP address? r hard-coded by system admin in a file m Windows: control-panel->network->configuration-
Transitioning to IPv6 April 15,2005 Presented By: Richard Moore PBS Enterprise Technology.

Transitioning to IPv6 April 15,2005 Presented By: Richard Moore PBS Enterprise Technology.
IPv4 to IPv6 Migration strategies. What is IPv4  Second revision in development of internet protocol  First version to be widely implied.  Connection.

IPv4 to IPv6 Migration strategies. What is IPv4  Second revision in development of internet protocol  First version to be widely implied.  Connection.
IPv6: The Next Generation Internet Protocol CEOS WGISS 18: Beijing, China September 2004 Dave Hartzell Computer Sciences Corp, NASA Ames

IPv6: The Next Generation Internet Protocol CEOS WGISS 18: Beijing, China September 2004 Dave Hartzell Computer Sciences Corp, NASA Ames
IPv6 Victor T. Norman.

IPv6 Victor T. Norman.
Project by: Palak Baid (pb2358) Gaurav Pandey (gip2103) Guided by: Jong Yul Kim.

Project by: Palak Baid (pb2358) Gaurav Pandey (gip2103) Guided by: Jong Yul Kim.
1 Internet Protocol Version 6 (IPv6) What the caterpillar calls the end of the world, nature calls a butterfly. - Anonymous.

1 Internet Protocol Version 6 (IPv6) What the caterpillar calls the end of the world, nature calls a butterfly. - Anonymous.
IP Version 6 Next generation IP Prof. P Venkataram ECE Dept. IISc.

IP Version 6 Next generation IP Prof. P Venkataram ECE Dept. IISc.
IETF 72 – July 2008 Vince Fuller, Darrel Lewis, Eliot Lear, Scott Brim, Dave Oran, Noel Chiappa, John Curran, Dino Farinacci, and David Meyer LISP Deployment.

IETF 72 – July 2008 Vince Fuller, Darrel Lewis, Eliot Lear, Scott Brim, Dave Oran, Noel Chiappa, John Curran, Dino Farinacci, and David Meyer LISP Deployment.
Introduction to LISP (not (the (programming ( language))))

Introduction to LISP (not (the (programming ( language))))
LISP-CONS A Mapping Database Service NANOG 41 David Meyer, Dino Farinacci, Vince Fuller, Darrel Lewis, Scott Brim, Noel Chiappa NANOG 41 October, 2007.

LISP-CONS A Mapping Database Service NANOG 41 David Meyer, Dino Farinacci, Vince Fuller, Darrel Lewis, Scott Brim, Noel Chiappa NANOG 41 October, 2007.
Internet Draft Status Internet Draft Status draft-farinacci-lisp-{00-12}.txt Dave Meyer, Vince Fuller, Darrel Lewis, Dino Farinacci IETF San Francisco.

Internet Draft Status Internet Draft Status draft-farinacci-lisp-{00-12}.txt Dave Meyer, Vince Fuller, Darrel Lewis, Dino Farinacci IETF San Francisco.
COM555: Mobile Technologies Location-Identifier Separation.

COM555: Mobile Technologies Location-Identifier Separation.
Network Layer Packet Forwarding IS250 Spring 2010

Network Layer Packet Forwarding IS250 Spring 2010
NANOG-46 Philadelphia, June 2009 Vince Fuller & Dave Meyer (for the rest of the LISP crew: Noel Chiappa, Dino Farinacci, Darrel Lewis, Andrew Partan, and.

NANOG-46 Philadelphia, June 2009 Vince Fuller & Dave Meyer (for the rest of the LISP crew: Noel Chiappa, Dino Farinacci, Darrel Lewis, Andrew Partan, and.
Oct 21, 2004CS573: Network Protocols and Standards1 IP: Addressing, ARP, Routing Network Protocols and Standards Autumn 2004-2005.

Oct 21, 2004CS573: Network Protocols and Standards1 IP: Addressing, ARP, Routing Network Protocols and Standards Autumn

Similar presentations

Ads by Google