RFC 3177 on IAB/IESG Recommendations on IPv6 Addresses
RFC Editor <rfc-ed@ISI.EDU> Sat, 20 October 2001 04:57 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA21380; Sat, 20 Oct 2001 00:57:31 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id AAA12771 for ietf-123-outbound.10@ietf.org; Sat, 20 Oct 2001 00:45:01 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id SAA07819 for <all-ietf@loki.ietf.org>; Fri, 19 Oct 2001 18:53:07 -0400 (EDT)
Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04190 for <all-ietf@ietf.org>; Fri, 19 Oct 2001 18:53:02 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id f9JMr5H06085; Fri, 19 Oct 2001 15:53:05 -0700 (PDT)
Message-Id: <200110192253.f9JMr5H06085@gamma.isi.edu>
To: IETF-Announce:;
Subject: RFC 3177 on IAB/IESG Recommendations on IPv6 Addresses
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Fri, 19 Oct 2001 15:53:05 -0700
From: RFC Editor <rfc-ed@ISI.EDU>
A new Request for Comments is now available in online RFC libraries. RFC 3177 Title: IAB/IESG Recommendations on IPv6 Address Allocations to Sites Author(s): IAB, IESG Status: Informational Date: September 2001 Mailbox: iab@iab.org, iesg@ietf.org Pages: 10 Characters: 23178 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-iesg-ipv6-addressing-recommendations-03.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3177.txt This document provides recommendations to the addressing registries (APNIC, ARIN and RIPE-NCC) on policies for assigning IPv6 address blocks to end sites. In particular, it recommends the assignment of /48 in the general case, /64 when it is known that one and only one subnet is needed and /128 when it is absolutely known that one and only one device is connecting. The original recommendations were made in an IAB/IESG statement mailed to the registries on September 1, 2000. This document refines the original recommendation and documents it for the historical record. This document is a product of the Internet Engineering Steering Group. 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.