RFC 6540 on IPv6 Support Required for All IP-Capable Nodes

rfc-editor@rfc-editor.org Thu, 12 April 2012 23:48 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 3B6BA21F851D; Thu, 12 Apr 2012 16:48:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.124
X-Spam-Level:
X-Spam-Status: No, score=-102.124 tagged_above=-999 required=5 tests=[AWL=-0.124, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4H7w-6JQPvLn; Thu, 12 Apr 2012 16:48:40 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id D577521F851B; Thu, 12 Apr 2012 16:48:40 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 2EC756219F; Thu, 12 Apr 2012 16:48:00 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6540 on IPv6 Support Required for All IP-Capable Nodes
From: rfc-editor@rfc-editor.org
Message-Id: <20120412234800.2EC756219F@rfc-editor.org>
Date: Thu, 12 Apr 2012 16:48:00 -0700
Cc: int-area@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: Thu, 12 Apr 2012 23:48:41 -0000

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

        BCP 177
        RFC 6540

        Title:      IPv6 Support Required for All 
                    IP-Capable Nodes 
        Author:     W. George, C. Donley,
                    C. Liljenstolpe, L. Howard
        Status:     Standards Track
        Stream:     IETF
        Date:       April 2012
        Mailbox:    wesley.george@twcable.com, 
                    C.Donley@cablelabs.com, 
                    cdl@asgaard.org,  lee.howard@twcable.com
        Pages:      6
        Characters: 12883
        See Also:   BCP0177

        I-D Tag:    draft-ietf-intarea-ipv6-required-02.txt

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

Given the global lack of available IPv4 space, and limitations in
IPv4 extension and transition technologies, this document advises
that IPv6 support is no longer considered optional.  It also cautions
that there are places in existing IETF documents where the term "IP"
is used in a way that could be misunderstood by implementers as the
term "IP" becomes a generic that can mean IPv4 + IPv6, IPv6-only, or
IPv4-only, depending on context and application.  This memo documents 
an Internet Best Current Practice.

This document is a product of the Internet Area Working Group 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