1 / 15

Managing IPv6 Addresses with TIPHON

afifi:. afifi:. Managing IPv6 Addresses with TIPHON. Afifi (INRIA), Bound (Compaq), Cadzow (ETSI), Scholl (ETSI), Toutain (ENST Bretagne). Outline. Context and Problem Elements of solution Hiding the routing information (No-NAT) Route optimization. Context. IPv6 (not available for v4)

tiger
Download Presentation

Managing IPv6 Addresses with TIPHON

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. afifi: afifi: Managing IPv6 Addresses with TIPHON Afifi (INRIA), Bound (Compaq), Cadzow (ETSI), Scholl (ETSI), Toutain (ENST Bretagne) Afifi, Bound, Cadzow Scholl, Toutain

  2. Outline • Context and Problem • Elements of solution • Hiding the routing information (No-NAT) • Route optimization Afifi, Bound, Cadzow Scholl, Toutain

  3. Context • IPv6 (not available for v4) • Mobile and possibly fixed environment (a base station is a gateway) • Try to use as much as we can available IP standards Afifi, Bound, Cadzow Scholl, Toutain

  4. Problems!!! • Clearly isolate an address from a name • so we don’t see the same problem as for E.164 • An address should contain routing information • It should also contain identification information • Give a route optimization means as proposed • Use IPv6 address in a new way • Hide the routing information that you don’t need to now • Be flexible to new concepts like portability… Afifi, Bound, Cadzow Scholl, Toutain

  5. Naming vs Addressing • Name = Label, technology independent • Address = Route, technology specific • Directory services associate name with address • X.500 • LDAP • Names are portable • Address associations change Afifi, Bound, Cadzow Scholl, Toutain

  6. Examples of names • Given name • Scott Cadzow • Resource identifier • bigcompany.com • Brand • Coca-cola • Ford Afifi, Bound, Cadzow Scholl, Toutain

  7. Examples of addresses • 15 The Street, The Town, The Country, The postcode • Time slot 1 of channel 15 at BS#4 • 127.0.0.1 Afifi, Bound, Cadzow Scholl, Toutain

  8. Elements of the solution • IPv6 address format: Deering & Hinden E.164 on 51 bits Prefix 7 digits Prefix Prefix E.164 Suffix E.164 128 bits Afifi, Bound, Cadzow Scholl, Toutain

  9. Elements of the solution • AIIH - DTI Model: Bound, Toutain & Afifi • Smooth TRANSPARENT transition • NO NAT solution (just end-to-end) • Assume native v6 routing in the cloud • Deals with two address spaces Afifi, Bound, Cadzow Scholl, Toutain

  10. DNS NAME SERVICE application V4 only V6 Tunnel V6 only DTI BOX V4 only Afifi, Bound, Cadzow Scholl, Toutain

  11. Hiding the address • Use the no-routing information field in IPv6 • We put a key in the Identification field • Send the packet to the destination • The gateway intercepts the packet • Replaces the key by the true routing information (could be an xMSI) Afifi, Bound, Cadzow Scholl, Toutain

  12. Cadzow@gsmgw.etsi.fr <gwPrefix.33.4.92.33.32.31.30> application Tiphon V6 Tunnel <gwPrefix.true routing suffix> 01010111011100 V6 only Afifi, Bound, Cadzow Scholl, Toutain

  13. Hiding the route • The key could be an E.164 number for the general case • The key could be a one time password for a telephonic communication (the sig Req.ID) • The key could carry information for a multi-party communication Afifi, Bound, Cadzow Scholl, Toutain

  14. Optimized Routing (to be studiedin more details) <gwprefix.E.164 number> <prefix.1> <prefix.4> <prefix.2> Afifi, Bound, Cadzow Scholl, Toutain

  15. Conclusion • We need to design a route optimization mechanism that fits in the GSM/TETRA model • We need to think about additional mechanisms for DNS lookup, DHCPv6 dynamic address assignement, route modification, etc… • We need to present it to IPNG... Afifi, Bound, Cadzow Scholl, Toutain

More Related