RFC 8021 on Generation of IPv6 Atomic Fragments Considered Harmful

rfc-editor@rfc-editor.org Fri, 06 January 2017 21:03 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 3A065129EDC; Fri, 6 Jan 2017 13:03:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.302
X-Spam-Level:
X-Spam-Status: No, score=-7.302 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-3.1, SPF_HELO_PASS=-0.001, SPF_PASS=-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 w36OAc41Xv-8; Fri, 6 Jan 2017 13:03:41 -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 97E66129EE8; Fri, 6 Jan 2017 13:03:41 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 909D0B80103; Fri, 6 Jan 2017 13:03:41 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8021 on Generation of IPv6 Atomic Fragments Considered Harmful
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170106210341.909D0B80103@rfc-editor.org>
Date: Fri, 6 Jan 2017 13:03:41 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/etCOvUN_j-HF_jiIfa2G9E4J1Do>
Cc: drafts-update-ref@iana.org, ipv6@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: Fri, 06 Jan 2017 21:03:43 -0000

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

        
        RFC 8021

        Title:      Generation of IPv6 Atomic Fragments 
                    Considered Harmful 
        Author:     F. Gont, W. Liu, T. Anderson
        Status:     Informational
        Stream:     IETF
        Date:       January 2017
        Mailbox:    fgont@si6networks.com, 
                    liushucheng@huawei.com, 
                    tore@redpill-linpro.com
        Pages:      12
        Characters: 25686
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-6man-deprecate-atomfrag-generation-08.txt

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

        DOI:        10.17487/RFC8021

This document discusses the security implications of the generation
of IPv6 atomic fragments and a number of interoperability issues
associated with IPv6 atomic fragments.  It concludes that the
aforementioned functionality is undesirable and thus documents the
motivation for removing this functionality from an upcoming revision
of the core IPv6 protocol specification (RFC 2460).

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