RFC 7094: Architectural Considerations of IP Anycast
In plain English — editorial summary, not part of the RFC
This memo discusses architectural implications of IP anycast and provides some historical analysis of anycast use by various IETF protocols.
Document record
- Document ID
- RFC7094
- Published
- January 2014
- Authors
- D. McPherson; D. Oran; D. Thaler; E. Osterweil
- Status
- INFORMATIONAL
- Stream
- IAB
- Area
- —
- Pages
- 22
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5694Peer-to-Peer (P2P) Architecture: Definition, Taxonomies, Examples, and ApplicabilityCurrent
November 2009
- RFC 3238IAB Architectural and Policy Considerations for Open Pluggable Edge ServicesCurrent
January 2002
- RFC 2956Overview of 1999 IAB Network Layer WorkshopCurrent
October 2000
- RFC 2902Overview of the 1998 IAB Routing WorkshopCurrent
August 2000
- RFC 2101IPv4 Address Behaviour TodayCurrent
February 1997
- RFC 7426Software-Defined Networking (SDN): Layers and Architecture TerminologyCurrent
January 2015
- RFC 7534AS112 Nameserver OperationsCurrent
May 2015
- RFC 6377DomainKeys Identified Mail (DKIM) and Mailing ListsCurrent
September 2011
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?