RFC 3068: An Anycast Prefix for 6to4 Relay Routers
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 7526.
Current document in this lineage: RFC 7526 — Deprecating the Anycast Prefix for 6to4 Relay Routers
In plain English — editorial summary, not part of the RFC
This memo introduces a "6to4 anycast address" in order to simplify the configuration of 6to4 routers. It also defines how this address will be used by 6to4 relay routers, how the corresponding "6to4 anycast prefix" will be advertised in the IGP and in the EGP. The memo documents the reservation by IANA (Internet Assigned Numbers Authority) of the "6to4 relay anycast prefix." [STANDARDS-TRACK]
Document record
- Document ID
- RFC3068
- Published
- June 2001
- Authors
- C. Huitema
- Status
- HISTORIC
- Stream
- IETF
- Area
- ops
- Pages
- 9
- Also known as
- —
- Obsoleted by:
- RFC 7526
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 3068 (2001)
- RFC 6732 (2012)
- RFC 7526 (2015) ✓
Read the full history of Deprecating the Anycast Prefix for 6to4 Relay Routers →
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3359Reserved Type, Length and Value (TLV) Codepoints in Intermediate System to Intermediate SystemCurrent
August 2002
- RFC 3719Recommendations for Interoperable Networks using Intermediate System to Intermediate System (IS-IS)Current
February 2004
- RFC 3785Use of Interior Gateway Protocol (IGP) Metric as a second MPLS Traffic Engineering (TE) MetricCurrent
May 2004
- RFC 4124Protocol Extensions for Support of Diffserv-aware MPLS Traffic EngineeringCurrent
June 2005
- RFC 1930Guidelines for creation, selection, and registration of an Autonomous System (AS)Updated
March 1996
- RFC 4561Definition of a Record Route Object (RRO) Node-Id Sub-ObjectCurrent
June 2006
- RFC 1371Choosing a Common IGP for the IP InternetCurrent
October 1992
- RFC 4972Routing Extensions for Discovery of Multiprotocol (MPLS) Label Switch Router (LSR) Traffic Engineering (TE) Mesh MembershipCurrent
July 2007
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?