hip resolution rendezvous problem description draft eggert hiprg rr prob desc 00 n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
HIP Resolution & Rendezvous Problem Description draft-eggert-hiprg-rr-prob-desc-00 PowerPoint Presentation
Download Presentation
HIP Resolution & Rendezvous Problem Description draft-eggert-hiprg-rr-prob-desc-00

Loading in 2 Seconds...

play fullscreen
1 / 13

HIP Resolution & Rendezvous Problem Description draft-eggert-hiprg-rr-prob-desc-00 - PowerPoint PPT Presentation


  • 96 Views
  • Uploaded on

HIP Resolution & Rendezvous Problem Description draft-eggert-hiprg-rr-prob-desc-00. IETF-61, Washington, DC, USA November 12, 2004. About. ID does not propose specific rendezvous/resolution solutions instead, describes rendezvous/resolution problem specific associated issues

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

HIP Resolution & Rendezvous Problem Description draft-eggert-hiprg-rr-prob-desc-00


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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
hip resolution rendezvous problem description draft eggert hiprg rr prob desc 00

HIP Resolution & Rendezvous Problem Descriptiondraft-eggert-hiprg-rr-prob-desc-00

IETF-61, Washington, DC, USA

November 12, 2004

about
About
  • ID does not propose specific rendezvous/resolution solutions
  • instead, describes
    • rendezvous/resolution problem
    • specific associated issues
  • proposed solutions can reference ID and discuss whether and how they address the issues

draft-eggert-hiprg-rr-prob-desc-00

terminology
Terminology
  • resolution
    • resolving a host identity into its set of IP addresses
  • rendezvous
    • process by which two nodes obtain enough information about one another to initiate communication
    • purposefully vague, need to refine

draft-eggert-hiprg-rr-prob-desc-00

issue 1 dns dependency
Issue 1: DNS Dependency
  • IP works fine without a deployed DNS
    • HIP currently uses DNS infrastructure to resolve FQDN into <HIT*, IP*>
  • changing the architecture to depend on a deployed DNS is problematic

+--------+ DNS lookup +--------------------+

| domain |-------------------------------->| host | IP |

| name |<--------------------------+ | identity | address |

+--------+ reverse DNS lookup | +--------------------+

| |

+---------------------+

draft-eggert-hiprg-rr-prob-desc-00

issue 2 direct communication
Issue 2: Direct Communication
  • HIP’s current use of DNS prevents direct communication
    • must know the peer’s FQDN
    • can’t talk to a peer even when HIT is known
  • problematic, if the goal is to replace IP addresses with HITs above the network layer

+--------+ DNS lookup +--------------------+

| domain |-------------------------------->| host | IP |

| name |<--------------------------+ | identity | address |

+--------+ reverse DNS lookup | +--------------------+

| |

+---------------------+

draft-eggert-hiprg-rr-prob-desc-00

issue 3 reverse lookup
Issue 3: Reverse Lookup
  • reverse lookups are useful
    • from IP to HIT
    • from HIT to FQDN
  • current DNS-based WG draft may support
    • IP to HIT with new entries inin-addr.arpa
    • HIT to FQDN with a new root hit.arpa
  • possible new resolvers should support reverse lookups, too

draft-eggert-hiprg-rr-prob-desc-00

issue 4 rendezvous with dns
Issue 4: Rendezvous with DNS
  • HIP currently requires DNS reachable at known IP addresses
  • it may be useful to let hosts use HIP to talk to DNS servers
    • DNS servers would have well known identities instead of IP addresses
    • DNS servers could be easily mobile and multihomed
      • (easier than with anycast)

draft-eggert-hiprg-rr-prob-desc-00

issue 5 1 middlebox traversal
Issue 5.1: Middlebox Traversal
  • middleboxes are a reality
  • for deployment success, the rendezvous procedure must traverse them
  • problem description exists
    • draft-stiemerling-hip-nat-02
  • solutions being investigated
    • result of workshop, HIP-over-STUN, etc.

draft-eggert-hiprg-rr-prob-desc-00

issue 5 2 location privacy
Issue 5.2: Location Privacy
  • some operators are concerned about exposing globally routable IP addresses to end hosts
    • “you can attack it more easily if you know where it is”
  • proposals should consider if and how they may support location privacy

draft-eggert-hiprg-rr-prob-desc-00

issue 5 3 mobility multihoming
Issue 5.3: Mobility & Multihoming
  • how to rendezvous between moving peers
    • for new HIP associations
    • (existing ones use REA)
  • tradeoffs
    • reachability
    • routing efficiency
    • high-rate mobility
  • proposed solutions should discuss if and how they support this

draft-eggert-hiprg-rr-prob-desc-00

issue 5 4 legacy interoperation
Issue 5.4: Legacy Interoperation
  • how to interoperate between HIP and non-HIP nodes
    • “just use IP”
    • but would be nice if some of the benefits of HIP could be had
  • proposed solutions should discuss how they interact with legacy nodes

draft-eggert-hiprg-rr-prob-desc-00

next steps
Next Steps
  • would like more group feedback!
    • are all identified issues valid?
    • are we missing any?
  • make this an RG document?

draft-eggert-hiprg-rr-prob-desc-00

questions draft eggert hiprg rr prob desc 00

Questionsdraft-eggert-hiprg-rr-prob-desc-00

lars.eggert@netlab.nec.de

ju@sun.com