A layered naming architecture for the internet

Hari Balakrishnan, Karthik Lakshminarayanan, Sylvia Ratnasamy, Scott Shenker, Ion Stoica, Michael Walfish

Research output: Chapter in Book/Report/Conference proceedingConference contribution

Abstract

Currently the Internet has only one level of name resolution, DNS, which converts user-level domain names into IP addresses. In this paper we borrow liberally from the literature to argue that there should be three levels of name resolution: from user-level descriptors to service identifiers; from service identifiers to endpoint identifiers; and from endpoint identifiers to IP addresses. These additional levels of naming and resolution (1) allow services and data to be first class Internet objects (in that they can be directly and persistently named), (2) seamlessly accommodate mobility and multihoming and (3) integrate middleboxes (such as NATs and firewalls) into the Internet architecture. We further argue that flat names are a natural choice for the service and endpoint identifiers. Hence, this architecture requires scalable resolution of flat names, a capability that distributed hash tables (DHTs) can provide.

Original languageEnglish (US)
Title of host publicationComputer Communication Review
Pages343-352
Number of pages10
Volume34
Edition4
DOIs
StatePublished - 2004
EventACM SIGCOMM 2004: Conference on Computer Communications - Portland, OR, United States
Duration: Aug 30 2004Sep 3 2004

Other

OtherACM SIGCOMM 2004: Conference on Computer Communications
CountryUnited States
CityPortland, OR
Period8/30/049/3/04

Fingerprint

Internet
Computer system firewalls

Keywords

  • Distributed hash tables
  • Global identifiers
  • Internet architecture
  • Middleboxes
  • Name resolution
  • Naming

ASJC Scopus subject areas

  • Information Systems

Cite this

Balakrishnan, H., Lakshminarayanan, K., Ratnasamy, S., Shenker, S., Stoica, I., & Walfish, M. (2004). A layered naming architecture for the internet. In Computer Communication Review (4 ed., Vol. 34, pp. 343-352) https://doi.org/10.1145/1030194.1015505

A layered naming architecture for the internet. / Balakrishnan, Hari; Lakshminarayanan, Karthik; Ratnasamy, Sylvia; Shenker, Scott; Stoica, Ion; Walfish, Michael.

Computer Communication Review. Vol. 34 4. ed. 2004. p. 343-352.

Research output: Chapter in Book/Report/Conference proceedingConference contribution

Balakrishnan, H, Lakshminarayanan, K, Ratnasamy, S, Shenker, S, Stoica, I & Walfish, M 2004, A layered naming architecture for the internet. in Computer Communication Review. 4 edn, vol. 34, pp. 343-352, ACM SIGCOMM 2004: Conference on Computer Communications, Portland, OR, United States, 8/30/04. https://doi.org/10.1145/1030194.1015505
Balakrishnan H, Lakshminarayanan K, Ratnasamy S, Shenker S, Stoica I, Walfish M. A layered naming architecture for the internet. In Computer Communication Review. 4 ed. Vol. 34. 2004. p. 343-352 https://doi.org/10.1145/1030194.1015505
Balakrishnan, Hari ; Lakshminarayanan, Karthik ; Ratnasamy, Sylvia ; Shenker, Scott ; Stoica, Ion ; Walfish, Michael. / A layered naming architecture for the internet. Computer Communication Review. Vol. 34 4. ed. 2004. pp. 343-352
@inproceedings{133db09f9b0f4e1caaeddeee9f15c324,
title = "A layered naming architecture for the internet",
abstract = "Currently the Internet has only one level of name resolution, DNS, which converts user-level domain names into IP addresses. In this paper we borrow liberally from the literature to argue that there should be three levels of name resolution: from user-level descriptors to service identifiers; from service identifiers to endpoint identifiers; and from endpoint identifiers to IP addresses. These additional levels of naming and resolution (1) allow services and data to be first class Internet objects (in that they can be directly and persistently named), (2) seamlessly accommodate mobility and multihoming and (3) integrate middleboxes (such as NATs and firewalls) into the Internet architecture. We further argue that flat names are a natural choice for the service and endpoint identifiers. Hence, this architecture requires scalable resolution of flat names, a capability that distributed hash tables (DHTs) can provide.",
keywords = "Distributed hash tables, Global identifiers, Internet architecture, Middleboxes, Name resolution, Naming",
author = "Hari Balakrishnan and Karthik Lakshminarayanan and Sylvia Ratnasamy and Scott Shenker and Ion Stoica and Michael Walfish",
year = "2004",
doi = "10.1145/1030194.1015505",
language = "English (US)",
volume = "34",
pages = "343--352",
booktitle = "Computer Communication Review",
edition = "4",

}

TY - GEN

T1 - A layered naming architecture for the internet

AU - Balakrishnan, Hari

AU - Lakshminarayanan, Karthik

AU - Ratnasamy, Sylvia

AU - Shenker, Scott

AU - Stoica, Ion

AU - Walfish, Michael

PY - 2004

Y1 - 2004

N2 - Currently the Internet has only one level of name resolution, DNS, which converts user-level domain names into IP addresses. In this paper we borrow liberally from the literature to argue that there should be three levels of name resolution: from user-level descriptors to service identifiers; from service identifiers to endpoint identifiers; and from endpoint identifiers to IP addresses. These additional levels of naming and resolution (1) allow services and data to be first class Internet objects (in that they can be directly and persistently named), (2) seamlessly accommodate mobility and multihoming and (3) integrate middleboxes (such as NATs and firewalls) into the Internet architecture. We further argue that flat names are a natural choice for the service and endpoint identifiers. Hence, this architecture requires scalable resolution of flat names, a capability that distributed hash tables (DHTs) can provide.

AB - Currently the Internet has only one level of name resolution, DNS, which converts user-level domain names into IP addresses. In this paper we borrow liberally from the literature to argue that there should be three levels of name resolution: from user-level descriptors to service identifiers; from service identifiers to endpoint identifiers; and from endpoint identifiers to IP addresses. These additional levels of naming and resolution (1) allow services and data to be first class Internet objects (in that they can be directly and persistently named), (2) seamlessly accommodate mobility and multihoming and (3) integrate middleboxes (such as NATs and firewalls) into the Internet architecture. We further argue that flat names are a natural choice for the service and endpoint identifiers. Hence, this architecture requires scalable resolution of flat names, a capability that distributed hash tables (DHTs) can provide.

KW - Distributed hash tables

KW - Global identifiers

KW - Internet architecture

KW - Middleboxes

KW - Name resolution

KW - Naming

UR - http://www.scopus.com/inward/record.url?scp=21844450653&partnerID=8YFLogxK

UR - http://www.scopus.com/inward/citedby.url?scp=21844450653&partnerID=8YFLogxK

U2 - 10.1145/1030194.1015505

DO - 10.1145/1030194.1015505

M3 - Conference contribution

AN - SCOPUS:21844450653

VL - 34

SP - 343

EP - 352

BT - Computer Communication Review

ER -