Last Call: <draft-ietf-intarea-frag-fragile-12.txt> (IP Fragmentation Considered Fragile) to Best Current Practice

The IESG <iesg-secretary@ietf.org> Thu, 20 June 2019 21:04 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Last Call: <draft-ietf-intarea-frag-fragile-12.txt> (IP Fragmentation Considered Fragile) to Best Current Practice
Auto-Submitted: auto-generated
Precedence: bulk
Sender: iesg-secretary@ietf.org
CC: draft-ietf-intarea-frag-fragile@ietf.org, int-area@ietf.org, suresh@kaloom.com, intarea-chairs@ietf.org
Content-Transfer-Encoding: 7bit
Reply-To: ietf@ietf.org
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Message-ID: <156106468060.1635.15353104701566613172.idtracker@ietfa.amsl.com>
Date: Thu, 20 Jun 2019 14:04:40 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/1E3jZ7yjlFooIgmAgOf3K4MyLMM>

The IESG has received a request from the Internet Area Working Group WG
(intarea) to consider the following document: - 'IP Fragmentation Considered
Fragile'
  <draft-ietf-intarea-frag-fragile-12.txt> as Best Current Practice

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2019-07-04. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the beginning of
the Subject line to allow automated sorting.

Abstract


   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.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-intarea-frag-fragile/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-intarea-frag-fragile/ballot/


No IPR declarations have been submitted directly on this I-D.


The document contains these normative downward references.
See RFC 3967 for additional information: 
    rfc1191: Path MTU discovery (Draft Standard - Legacy stream)
    rfc4821: Packetization Layer Path MTU Discovery (Proposed Standard - IETF stream)
    draft-ietf-tsvwg-datagram-plpmtud: Packetization Layer Path MTU Discovery for Datagram Transports (None - IETF stream)
    rfc6438: Using the IPv6 Flow Label for Equal Cost Multipath Routing and Link Aggregation in Tunnels (Proposed Standard - IETF stream)
    rfc6437: IPv6 Flow Label Specification (Proposed Standard - IETF stream)

Last Call: <draft-ietf-intarea-frag-fragile-12.tx… The IESG