Why Operators Filter Fragments and What It Implies
draft-taylor-v6ops-fragdrop-00

The information below is for an old version of the document
Document Type Expired Internet-Draft (individual)
Last updated 2013-04-18 (latest revision 2012-10-15)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html
Stream Stream state (No stream defined)
Document shepherd None
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-taylor-v6ops-fragdrop-00.txt

Abstract

This memo is written to make application developers and network operators aware of the significant probability that IPv6 packets containing fragmentation extension headers will fail to reach their destination. Some assumptions about the ability to use TCP or UDP datagrams larger than a single packet may accordingly need adjustment. This memo provides observational evidence for the dropping of IPv6 fragments along a significant number of paths, explores the operational impact of fragmentation and the reasons why dropping occurs, and considers the effect of fragment dropping on applications particularly including DNS.

Authors

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)