A Novel Data-Oriented Name Service

The Internet has evolved from its original design. (1)The user cares about what they are looking for, not which machine provides the data or the service. The host-to-host Internet tends to become a data-oriented network. (2) In the pressures of commerce and security, the middleboxes, such as network address translators (NATs), firewalls and caching servers, become commonplace in current Internet. They improve the performance of the applications and security, but also violate the Internet layering and are difficult to maintain and configure. To adapt these changes, we proposed the novel Data-Oriented Name Service (DONS), which gives a clean-slate redesign of Internet naming and name resolution. It achieves (1) permanence, getting the resource using the persistent name; (2) semantic-free, improving the flexibility and functionality of the network; (3) middlebox integration, allowing and facilitating the deployment of middleboxes; (4) self-certifying, authenticating the source.

[1]  Michael Walfish,et al.  A layered naming architecture for the internet , 2004, SIGCOMM '04.

[2]  Ryan Moats,et al.  URN Syntax , 1997, RFC.

[3]  Kevin R. Fall,et al.  A delay-tolerant network architecture for challenged internets , 2003, SIGCOMM '03.

[4]  Paul Francis,et al.  IPNL: A NAT-extended internet architecture , 2001, SIGCOMM 2001.

[5]  Karen R. Sollins,et al.  Functional Requirements for Uniform Resource Names , 1994, RFC.

[6]  William Adjie-Winoto,et al.  The design and implementation of an intentional naming system , 2000, OPSR.

[7]  Scott Shenker,et al.  A data-oriented (and beyond) network architecture , 2007, SIGCOMM 2007.

[8]  Lixia Zhang,et al.  Report from the IAB Workshop on Routing and Addressing , 2007, RFC.

[9]  David Mazières,et al.  Separating key management from file system security , 1999, SOSP.

[10]  Roy T. Fielding,et al.  Hypertext Transfer Protocol - HTTP/1.0 , 1996, RFC.

[11]  Krishna P. Gummadi,et al.  King: estimating latency between arbitrary internet end hosts , 2002, IMW '02.

[12]  Antonio Gulli,et al.  The indexable web is more than 11.5 billion pages , 2005, WWW '05.

[13]  Karen R. Sollins,et al.  Architectural Principles of Uniform Resource Name Resolution , 1998, RFC.

[14]  Pekka Nikander,et al.  Host Identity Protocol (HIP) Architecture , 2006, RFC.

[15]  Scott Shenker,et al.  Internet indirection infrastructure , 2002, SIGCOMM 2002.

[16]  Robert Tappan Morris,et al.  Comparing the Performance of Distributed Hash Tables Under Churn , 2004, IPTPS.

[17]  Emin Gün Sirer,et al.  The design and implementation of a next generation name service for the internet , 2004, SIGCOMM.

[18]  Saikat Guha,et al.  NUTSS: a SIP-based approach to UDP and TCP network connectivity , 2004, FDNA '04.

[19]  Michael Walfish,et al.  Untangling the Web from DNS , 2004, NSDI.

[20]  Pan Hui,et al.  Haggle: A networking architecture designed around mobile users , 2006 .

[21]  Bryan Ford,et al.  Unmanaged Internet Protocol , 2004, Comput. Commun. Rev..

[22]  Michael Walfish,et al.  Middleboxes No Longer Considered Harmful , 2004, OSDI.

[23]  Gade Krishna,et al.  A scalable peer-to-peer lookup protocol for Internet applications , 2012 .