RFC 5375 on IPv6 Unicast Address Assignment Considerations

rfc-editor@rfc-editor.org Thu, 04 December 2008 00:20 UTC

Return-Path: <ietf-announce-bounces@ietf.org>
X-Original-To: ietf-announce-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-announce-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BFDAC28C1B8; Wed, 3 Dec 2008 16:20:07 -0800 (PST)
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BD6243A68CE for <ietf-announce@core3.amsl.com>; Wed, 3 Dec 2008 16:20:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.663
X-Spam-Level:
X-Spam-Status: No, score=-16.663 tagged_above=-999 required=5 tests=[AWL=0.936, BAYES_00=-2.599, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PX9-Ae2WamWq for <ietf-announce@core3.amsl.com>; Wed, 3 Dec 2008 16:20:04 -0800 (PST)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id C14A23A6452 for <ietf-announce@ietf.org>; Wed, 3 Dec 2008 16:20:04 -0800 (PST)
Received: by bosco.isi.edu (Postfix, from userid 70) id DC1EC193B3C; Wed, 3 Dec 2008 16:20:00 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5375 on IPv6 Unicast Address Assignment Considerations
From: rfc-editor@rfc-editor.org
Message-Id: <20081204002000.DC1EC193B3C@bosco.isi.edu>
Date: Wed, 03 Dec 2008 16:20:00 -0800
Cc: v6ops@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org

A new Request for Comments is now available in online RFC libraries.

        
        RFC 5375

        Title:      IPv6 Unicast Address Assignment Considerations 
        Author:     G. Van de Velde, C. Popoviciu, T. Chown,
                    O. Bonness, C. Hahn
        Status:     Informational
        Date:       December 2008
        Mailbox:    gunter@cisco.com, 
                    cpopovic@cisco.com, 
                    tjc@ecs.soton.ac.uk,
                    Olaf.Bonness@t-systems.com, 
                    HahnC@t-systems.com
        Pages:      35
        Characters: 83809
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-v6ops-addcon-10.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5375.txt

One fundamental aspect of any IP communications infrastructure is its
addressing plan.  With its new address architecture and allocation
policies, the introduction of IPv6 into a network means that network
designers and operators need to reconsider their existing approaches
to network addressing.  Lack of guidelines on handling this aspect of
network design could slow down the deployment and integration of
IPv6.  This document aims to provide the information and
recommendations relevant to planning the addressing aspects of IPv6
deployments.  The document also provides IPv6 addressing case studies
for both an enterprise and an ISP network.  This memo provides information
for the Internet community.

This document is a product of the IPv6 Operations Working Group of the IETF.


INFORMATIONAL: 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-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
USC/Information Sciences Institute


_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce