Future Internet Architecture Proposals

From ResiliNetsWiki
Jump to: navigation, search


[Ratnasamy-Shenker-McCanne 2005 (doi) .]

Sylvia Ratnasamy, Scott Shenker, Steven McCanne,
"Towards an evolvable internet architecture",
Proceedings of the 2005 conference on Applications, technologies, architectures, and protocols for computer communications, 2005, pp. 313–324

ResiliNets Keywords: Anycast, Evolvability

Keywords: Network Architecture, Anycast

Abstract: "There is widespread agreement on the need for architectural change in the Internet, but very few believe that current ISPs will ever effect such changes. In this paper we ask what makes an architecture evolvable, by which we mean capable of gradual change led by the incumbent providers. This involves both technical and economic issues, since ISPs have to be able, and incented, to offer new architectures. Our study suggests that, with very minor modifications, the current Internet architecture could be evolvable."

Bibliographic Entries

[Stoica-Adkins-Zhuang-Shenker-Surana 2002 (doi) . ]

Ion Stoica, Daniel Adkins, Shelly Zhuang, scott Shenker, Sonesh Surana,
"Internet indirection infrastructure",
Proceedings of the 2002 conference on Applications, technologies, architectures, and protocols for computer communications, 2002, pp. 73–86

ResiliNets Keywords: list

Keywords: abstraction, architecture, indirection, internet, scalable

Abstract: "Attempts to generalize the Internet's point-to-point communication abstraction to provide services like multicast, anycast, and mobility have faced challenging technical problems and deployment barriers. To ease the deployment of such services, this paper proposes an overlay-based Internet Indirection Infrastructure ( I3) that offers a rendezvous-based communication abstraction. Instead of explicitly sending a packet to a destination, each packet is associated with an identifier; this identifier is then used by the receiver to obtain delivery of the packet. This level of indirection decouples the act of sending from the act of receiving, and allows I3 to efficiently support a wide variety of fundamental communication services. To demonstrate the feasibility of this approach, we have designed and built a prototype based on the Chord lookup protocol."

Bibliographic Entries

[Balakrishnan-Lakshminarayanan-Ratnasamy-Shenker-Stoica-Walfish 2004 (doi) . ]

Hari Balakrishnan, Karthik Lakshminarayanan, Sylvia Ratnasamy, Scott Shenker, Ion Stoica, Michael Walfish,
"A layered naming architecture for the internet",
Proceedings of the 2004 conference on Applications, technologies, architectures, and protocols for computer communications, 2004, pp. 343–352

ResiliNets Keywords: addressing, identifing, routing

Keywords: distributed hash tables, global identifiers, internet architecture, middleboxes, name resolution, naming

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 multi-homing 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."

Bibliographic Entries



Personal tools