BCP 220, RFC 8504 on IPv6 Node Requirements

rfc-editor@rfc-editor.org Wed, 30 January 2019 18:39 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 3762C130EA2; Wed, 30 Jan 2019 10:39:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 jJ9sjg6dYy9x; Wed, 30 Jan 2019 10:38:59 -0800 (PST)
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 3D49E130E6E; Wed, 30 Jan 2019 10:38:59 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 8E307B82F28; Wed, 30 Jan 2019 10:38:58 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?QkNQIDIyMCwgUkZDIDg1MDQgb24gSVB2NiBOb2RlIFJlcXVpcmVtZW50cw==?=
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, ipv6@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20190130183858.8E307B82F28@rfc-editor.org>
Date: Wed, 30 Jan 2019 10:38:58 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/gjsAFdzXM11abNHNzdrEnfI2PSw>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
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: <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, 30 Jan 2019 18:39:01 -0000

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

        BCP 220        
        RFC 8504

        Title:      IPv6 Node Requirements 
        Author:     T. Chown, 
                    J. Loughney,
                    T. Winters
        Status:     Best Current Practice
        Stream:     IETF
        Date:       January 2019
        Mailbox:    tim.chown@jisc.ac.uk, 
                    john.loughney@gmail.com, 
                    twinters@iol.unh.edu
        Pages:      42
        Characters: 96133
        Obsoletes:  RFC 6434
        See Also:   BCP 220

        I-D Tag:    draft-ietf-6man-rfc6434-bis-09.txt

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

        DOI:        10.17487/RFC8504

This document defines requirements for IPv6 nodes.  It is expected
that IPv6 will be deployed in a wide range of devices and situations.
Specifying the requirements for IPv6 nodes allows IPv6 to function
well and interoperate in a large number of situations and
deployments.

This document obsoletes RFC 6434, and in turn RFC 4294.

This document is a product of the IPv6 Maintenance 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