RFC 2526 on Reserved IPv6 Subnet Anycast Addresses
RFC Editor <rfc-ed@ISI.EDU> Thu, 04 March 1999 04:15 UTC
Received: by ietf.org (8.9.1a/8.9.1a) id XAA05027 for ietf-123-outbound.10@ietf.org; Wed, 3 Mar 1999 23:15:08 -0500 (EST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27104 for <all-ietf@ietf.org>; Wed, 3 Mar 1999 18:32:36 -0500 (EST)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id PAA15889; Wed, 3 Mar 1999 15:32:35 -0800 (PST)
Message-Id: <199903032332.PAA15889@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2526 on Reserved IPv6 Subnet Anycast Addresses
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Wed, 03 Mar 1999 15:32:35 -0800
From: RFC Editor <rfc-ed@ISI.EDU>
A new Request for Comments is now available in online RFC libraries. RFC 2526: Title: Reserved IPv6 Subnet Anycast Addresses Author(s): D. Johnson, S. Deering Status: Proposed Standard Date: March 1999 Mailbox: dbj@cs.cmu.edu, deering@cisco.com Pages: 7 Characters: 14555 Updates/Obsoletes/See Also: None I-D Tag: draft-ietf-ipngwg-resv-anycast-02.txt URL: ftp://ftp.isi.edu/in-notes/rfc2526.txt The IP Version 6 addressing architecture defines an "anycast" address as an IPv6 address that is assigned to one or more network interfaces (typically belonging to different nodes), with the property that a packet sent to an anycast address is routed to the "nearest" interface having that address, according to the routing protocols' measure of distance. This document defines a set of reserved anycast addresses within each subnet prefix, and lists the initial allocation of these reserved subnet anycast addresses. This document is a product of the IPNG Working Group of the IETF. This is now a Proposed Standard Protocol. This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Alegre Ramos USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs.