Untangling the Web from DNS这个网站从DNS.pptVIP

Foo Bar A Layered Naming Architecture Michael Walfish MIT Computer Science and Artificial Intelligence Lab Joint work with: H. Balakrishnan, M. Krohn, K. Lakshminarayanan, S. Ratnasamy, S. Shenker, I. Stoica, J. Stribling Outline Overview of “Layered Naming Architecture” Application-level example Network-level examples “A Layered Naming Architecture” “A Layered Naming Architecture”, Cont. The Layers Benefits SIDs in Action EIDs in Action (1): Remote Packet Filter EIDs in Action (2): Cascaded NATs High-level Points */ * IRTF HIP RG 6 August 2004 View: naming could solve some arch. probs. Principle 1: “don’t bind names too early” Need two new types of names SIDs (Service IDs) EIDs (End-point IDs) Principle 2: “names should be flat” Principle 3: “let names resolve to delegates” Dest (Target) Delegate EID e, IP = y EID: e IP: x Source (Querier) EID Resolution Service IP: y EID e, IP = ? Intent: “send to EID e’’ user-level descriptor (ULD) lookup(e.g., e-mail address, search string, etc.) SID resolution App gets SIDs corresponding to ULD via lookup or search service EID resolution App’s session protocol (e.g., HTTP) resolves SID to EIDs using SID resolution service IP address “resolution” (routing) Transport protocol resolves EID to IP addresses using EID resolution service Mobility and multi-homing (from HIP) Data and services become first-class Because they can be persistently named Architectural coherence for middleboxes One example: SFR A HREF= http://f012012 here is a dog/A HTTP GET: /spot.gif /spot.gif HTTP GET: /abc/dog.gif (,80, /spot.gif) (,80, /abc/dog.gif) /abc/dog.gif (Could use EIDs instead of , ) Imagine third-party firewall services Need robust notion of host identity Need ability to delegate EID: 0x8a.. IP: EIDs (not overloaded ports!) help demux Not focusing on specifics of implementation for now . . . Insights about network-level IDs apply to application-level IDs (and vice-versa!) Flat names, delegation powerful primitives These pr