Topic
Anycast
About: Anycast is a research topic. Over the lifetime, 1108 publications have been published within this topic receiving 18414 citations.
Papers published on a yearly basis
Papers
More filters
01 Dec 1995
TL;DR: This specification defines the addressing architecture of the IP Version 6 protocol [IPV6], which includes the IPv6 addressing model, text representations of IPv6 addresses, definition of IPv 6 unicast addresses, anycast addresses, and multicast addressing, and an IPv6 node's required addresses.
Abstract: This specification defines the addressing architecture of the IP Version 6 protocol [IPV6]. The document includes the IPv6 addressing model, text representations of IPv6 addresses, definition of IPv6 unicast addresses, anycast addresses, and multicast addresses, and an IPv6 node's required addresses.
771 citations
••
19 Aug 2002TL;DR: An overlay-based Internet Indirection Infrastructure that offers a rendezvous-based communication abstraction that decouples the act of sending from the acts of receiving, and allows I3 to efficiently support a wide variety of fundamental communication services.
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.
753 citations
01 Nov 1993
TL;DR: This RFC describes an internet anycasting service for IP and tries to be agnostic about how the service is actually provided by the internetwork.
Abstract: This RFC describes an internet anycasting service for IP. The primary purpose of this memo is to establish the semantics of an anycasting service within an IP internet. Insofar as is possible, this memo tries to be agnostic about how the service is actually provided by the internetwork. This memo describes an experimental service and does not propose a protocol. This memo is produced by the Internet Research Task Force (IRTF).
428 citations
••
TL;DR: A general, overlay-based Internet Indirection Infrastructure (i3) that offers a rendezvous-based communication abstraction that decouples the act of sending from the acts of receiving, and allows i3 to efficiently support a wide variety of fundamental communication services.
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 a general, 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.
362 citations
••
01 Oct 1995TL;DR: This paper considers the problem of choosing among a collection of replicated servers, focusing on the question of how to make choices that segregate client/server traffic according to network topology.
Abstract: In this paper we consider the problem of choosing among a collection of replicated servers, focusing on the question of how to make choices that segregate client/server traffic according to network topology. We explore the cost and effectiveness of a variety of approaches, ranging from those requiring routing layer support (e.g., anycast) to those that build location databases using application-level probe tools like traceroute. We uncover a number of tradeoffs between effectiveness, network cost, ease of deployment, and portability across different types of networks. We performed our experiments using a simulation parameterized by a topology collected from 7 survey sites across the United States, exploring a global collection of Network Time Protocol servers.
299 citations