<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.templin-6man-jumbofrag" target="https://datatracker.ietf.org/doc/html/draft-templin-6man-jumbofrag-01">
   <front>
      <title>IPv6 Packet Identification</title>
      <author initials="F." surname="Templin" fullname="Fred Templin">
         <organization>Boeing Research &amp; Technology</organization>
      </author>
      <date month="November" day="18" year="2021" />
      <abstract>
	 <t>   Unlike Internet Protocol, version 4 (IPv4), Internet Protocol,
   version 6 (IPv6) does not include an Identification field in the
   basic packet header.  Instead, IPv6 includes a 32-bit Identification
   field in a Fragment Header extension since the architecture assumed
   that the sole purpose for the Identification is to support the
   fragmentation and reassembly process.  This document asserts that
   per-packet Identifications may be useful for other purposes, e.g., to
   allow recipients to detect spurious packets that may have been
   injected into the network by an attacker.  But, rather than defining
   a new extension header, this document recommends employing the
   existing Fragment Header for per-packet identification even if the
   packet itself appears as an &quot;atomic fragment&quot;.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-templin-6man-jumbofrag-01" />
   
</reference>
