RFC 6164 on Using 127-Bit IPv6 Prefixes on Inter-Router Links
rfc-editor@rfc-editor.org Mon, 18 April 2011 16:40 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfc.amsl.com
Delivered-To: ietf-announce@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 49088E07FF; Mon, 18 Apr 2011 09:40:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.08
X-Spam-Level:
X-Spam-Status: No, score=-102.08 tagged_above=-999 required=5 tests=[AWL=-0.080, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hmcAu5LHfz0O; Mon, 18 Apr 2011 09:40:25 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by ietfc.amsl.com (Postfix) with ESMTP id 018E9E0805; Mon, 18 Apr 2011 09:40:21 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 6C778E0764; Mon, 18 Apr 2011 09:40:19 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6164 on Using 127-Bit IPv6 Prefixes on Inter-Router Links
From: rfc-editor@rfc-editor.org
Message-Id: <20110418164019.6C778E0764@rfc-editor.org>
Date: Mon, 18 Apr 2011 09:40:19 -0700
Cc: ipv6@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Apr 2011 16:40:26 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 6164
Title: Using 127-Bit IPv6 Prefixes on
Inter-Router Links
Author: M. Kohno, B. Nitzan,
R. Bush, Y. Matsuzaki,
L. Colitti, T. Narten
Status: Standards Track
Stream: IETF
Date: April 2011
Mailbox: mkohno@juniper.net,
nitzan@juniper.net,
randy@psg.com, maz@iij.ad.jp,
lorenzo@google.com, narten@us.ibm.com
Pages: 8
Characters: 16057
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-6man-prefixlen-p2p-01.txt
URL: http://www.rfc-editor.org/rfc/rfc6164.txt
On inter-router point-to-point links, it is useful, for security and
other reasons, to use 127-bit IPv6 prefixes. Such a practice
parallels the use of 31-bit prefixes in IPv4. This document
specifies the motivation for, and usages of, 127-bit IPv6 prefix
lengths on inter-router point-to-point links. [STANDARDS-TRACK]
This document is a product of the IPv6 Maintenance Working Group of the IETF.
This is now a Proposed Standard Protocol.
STANDARDS TRACK: 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-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
http://www.ietf.org/mailman/listinfo/ietf-announce
http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC