RFC 3627 on Use of /127 Prefix Length Between Routers Considered Harmful
rfc-editor@rfc-editor.org Wed, 17 September 2003 23:54 UTC
Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06485 for <ietf-announce-web-archive@odin.ietf.org>; Wed, 17 Sep 2003 19:54:56 -0400 (EDT)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14) id 19zm2J-00084V-1U for ietf-announce-list@asgard.ietf.org; Wed, 17 Sep 2003 19:48:39 -0400
Received: from ietf.org ([10.27.2.28]) by asgard.ietf.org with esmtp (Exim 4.14) id 19zm0a-00081V-AC for all-ietf@asgard.ietf.org; Wed, 17 Sep 2003 19:46:52 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06126 for <all-ietf@ietf.org>; Wed, 17 Sep 2003 19:46:42 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19zm0Y-0005U9-00 for all-ietf@ietf.org; Wed, 17 Sep 2003 19:46:50 -0400
Received: from gamma.isi.edu ([128.9.144.145]) by ietf-mx with esmtp (Exim 4.12) id 19zm0Y-0005U6-00 for all-ietf@ietf.org; Wed, 17 Sep 2003 19:46:50 -0400
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6p2/8.11.2) with ESMTP id h8HNkoN14606; Wed, 17 Sep 2003 16:46:50 -0700 (PDT)
Message-Id: <200309172346.h8HNkoN14606@gamma.isi.edu>
To: IETF-Announce:;
Subject: RFC 3627 on Use of /127 Prefix Length Between Routers Considered Harmful
Cc: rfc-editor@rfc-editor.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Wed, 17 Sep 2003 16:46:50 -0700
Sender: owner-ietf-announce@ietf.org
Precedence: bulk
A new Request for Comments is now available in online RFC libraries. RFC 3627 Title: Use of /127 Prefix Length Between Routers Considered Harmful Author(s): P. Savola Status: Informational Date: September 2003 Mailbox: psavola@funet.fi Pages: 6 Characters: 12436 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-savola-ipv6-127-prefixlen-04.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3627.txt In some cases, the operational decision may be to use IPv6 /127 prefix lengths, especially on point-to-point links between routers. Under certain situations, this may lead to one router claiming both addresses due to subnet-router anycast being implemented. This document discusses the issue and offers a couple of solutions to the problem; nevertheless, /127 should be avoided between two routers. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. 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 Sandy Ginoza 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.