1 / 5

HIP Experiment Report: Lessons Learned and Consequences of Identifier/Locator Separation

This report discusses the objectives, experiences, and implications of HIP-related experimentation. It examines the wide-scale adoption of identifier/locator separation in IP addresses and its consequences. The report explores end-host stack, application, infrastructure, and general implications, along with a list of individuals experimenting with HIP.

pattonj
Download Presentation

HIP Experiment Report: Lessons Learned and Consequences of Identifier/Locator Separation

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. Update on HIP experiment reportdraft-irtf-hip-experiment-01.txt IETF63 HIP RG Andrei Gurtov

  2. Objectives • Collective experiences and lessons learned from HIP related experimentation, and designs completed by the research group • Study consequences and effects that wide-scale adoption of any type of separation of the identifier and locator roles of IP addresses is likely to have • Whether the basic identifier/locator split assumption is valid falls beyond the scope of this research group

  3. Content • End-host Stack Implications • Application Implications • Infrastructure Implications • General Implications • List of people experimenting with HIP • Requested by IRTF chair

  4. Solicited contributions • Transport issues • Multi6/shim6 • IPv4 vs. IPv6 • Global management of new namespace • Access control lists with HITs • Debugging • Tying to PKIs

  5. Future • Experience with wider-scale HIP deployments • Scalability and security of DHTs • Need stable and easy to install HIP implementations to proceed!

More Related