idnits 2.17.1 draft-savola-ipv6-127-prefixlen-04.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3627 5 Title: Use of /127 Prefix Length Between Routers 6 Considered Harmful 7 Author(s): P. Savola 8 Status: Informational 9 Date: September 2003 10 Mailbox: psavola@funet.fi 11 Pages: 6 12 Characters: 12436 13 Updates/Obsoletes/SeeAlso: None 15 I-D Tag: draft-savola-ipv6-127-prefixlen-04.txt 17 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3627.txt 19 In some cases, the operational decision may be to use IPv6 /127 20 prefix lengths, especially on point-to-point links between routers. 21 Under certain situations, this may lead to one router claiming both 22 addresses due to subnet-router anycast being implemented. This 23 document discusses the issue and offers a couple of solutions to the 24 problem; nevertheless, /127 should be avoided between two routers. 26 This memo provides information for the Internet community. It does 27 not specify an Internet standard of any kind. Distribution of this 28 memo is unlimited. 30 This announcement is sent to the IETF list and the RFC-DIST list. 31 Requests to be added to or deleted from the IETF distribution list 32 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 33 added to or deleted from the RFC-DIST distribution list should 34 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 36 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 37 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 38 help: ways_to_get_rfcs. For example: 40 To: rfc-info@RFC-EDITOR.ORG 41 Subject: getting rfcs 43 help: ways_to_get_rfcs 45 Requests for special distribution should be addressed to either the 46 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 47 specifically noted otherwise on the RFC itself, all RFCs are for 48 unlimited distribution.echo 49 Submissions for Requests for Comments should be sent to 50 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 51 Authors, for further information.