BCP 204, RFC 7934 on Host Address Availability Recommendations

rfc-editor@rfc-editor.org Wed, 20 July 2016 12:17 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50CA912DBC5; Wed, 20 Jul 2016 05:17:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.889
X-Spam-Level:
X-Spam-Status: No, score=-103.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-1.287, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mksc83a2Ctoj; Wed, 20 Jul 2016 05:17:07 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D0F1112D57B; Wed, 20 Jul 2016 05:17:07 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id CC0C2B80EDC; Wed, 20 Jul 2016 05:17:07 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: BCP 204, RFC 7934 on Host Address Availability Recommendations
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160720121707.CC0C2B80EDC@rfc-editor.org>
Date: Wed, 20 Jul 2016 05:17:07 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/5_flJoVC7xmMq7zrcJ6CM0NJJHs>
Cc: v6ops@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: ietf@ietf.org
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: <https://mailarchive.ietf.org/arch/browse/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: Wed, 20 Jul 2016 12:17:09 -0000

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

        BCP 204        
        RFC 7934

        Title:      Host Address Availability Recommendations 
        Author:     L. Colitti,
                    V. Cerf,
                    S. Cheshire,
                    D. Schinazi
        Status:     Best Current Practice
        Stream:     IETF
        Date:       July 2016
        Mailbox:    lorenzo@google.com, 
                    vint@google.com, 
                    cheshire@apple.com,
                    dschinazi@apple.com
        Pages:      15
        Characters: 37124
        See Also:   BCP 204

        I-D Tag:    draft-ietf-v6ops-host-addr-availability-07.txt

        URL:        https://www.rfc-editor.org/info/rfc7934

        DOI:        http://dx.doi.org/10.17487/RFC7934

This document recommends that networks provide general-purpose end
hosts with multiple global IPv6 addresses when they attach, and it
describes the benefits of and the options for doing so.

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


BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for 
improvements. Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

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