BCP 230, RFC 8900 on IP Fragmentation Considered Fragile

rfc-editor@rfc-editor.org Fri, 11 September 2020 23:22 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 09CE03A0C7E; Fri, 11 Sep 2020 16:22:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 Tb81eGJvzKiL; Fri, 11 Sep 2020 16:22:12 -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 F0A5D3A0951; Fri, 11 Sep 2020 16:22:11 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id E9CDAF40788; Fri, 11 Sep 2020 16:21:47 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?QkNQIDIzMCwgUkZDIDg5MDAgb24gSVAgRnJhZ21lbnRhdGlvbiBDb25zaWRlcmVkIEZyYWdpbGU=?=
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, int-area@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20200911232147.E9CDAF40788@rfc-editor.org>
Date: Fri, 11 Sep 2020 16:21:47 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/BOySZFfDsDcKVRfzlLGP_4W4qlg>
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: Fri, 11 Sep 2020 23:22:18 -0000

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

        BCP 230        
        RFC 8900

        Title:      IP Fragmentation Considered Fragile 
        Author:     R. Bonica,
                    F. Baker,
                    G. Huston,
                    B. Hinden,
                    O. Troan,
                    F. Gont
        Status:     Best Current Practice
        Stream:     IETF
        Date:       September 2020
        Mailbox:    rbonica@juniper.net, 
                    fredbaker.ietf@gmail.com, 
                    gih@apnic.net, 
                    bob.hinden@gmail.com, 
                    ot@cisco.com, 
                    fgont@si6networks.com
        Pages:      23
        See Also:   BCP 230

        I-D Tag:    draft-ietf-intarea-frag-fragile-17.txt

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

        DOI:        10.17487/RFC8900

This document describes IP fragmentation and explains how it
introduces fragility to Internet communication.

This document also proposes alternatives to IP fragmentation and
provides recommendations for developers and network operators.

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