<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<?rfc toc="yes"?>
<?rfc tocompact="yes"?>
<?rfc tocdepth="3"?>
<?rfc tocindent="yes"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?>
<?rfc comments="yes"?>
<?rfc inline="yes"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>
<?rfc strict='yes'?>
<?rfc iprnotified='no'?>
<rfc category="std" docName="draft-templin-6man-jumbofrag-00"
     ipr="trust200902" updates="RFC2675">
  <front>
    <title abbrev="IPv6 Jumbogram Atomic Fragments">Transmission of IPv6
    Jumbograms as Atomic Fragments</title>

    <author fullname="Fred L. Templin" initials="F. L." role="editor"
            surname="Templin">
      <organization>Boeing Research &amp; Technology</organization>

      <address>
        <postal>
          <street>P.O. Box 3707</street>

          <city>Seattle</city>

          <region>WA</region>

          <code>98124</code>

          <country>USA</country>
        </postal>

        <email>fltemplin@acm.org</email>
      </address>
    </author>

    <date day="17" month="November" year="2021"/>

    <keyword>I-D</keyword>

    <keyword>Internet-Draft</keyword>

    <abstract>
      <t>Internet Protocol, Version 6 (IPv6) provides a service for
      transmission of IPv6 packets larger than 65,535 octets known as
      "jumbograms". Such large packets are not eligible for fragmentation, and
      the current specification forbids the inclusion of a fragment header of
      any kind. However, some implementations may wish to include an
      Identification value with each jumbogram; hence this document proposes
      the transmission of IPv6 jumbograms as "atomic fragments".</t>
    </abstract>
  </front>

  <middle>
    <section anchor="intro" title="Introduction">
      <t>Internet Protocol version 6 (IPv6) <xref target="RFC8200"/> provides
      a jumbogram service for transmission of IPv6 packets larger than 65,535
      octets <xref target="RFC2675"/>. Such large packets are not eligible for
      fragmentation, and the current specification forbids sources from
      including a Fragment Header of any kind. However, some implementations
      may wish to include an unpredictable Identification value with each
      jumbogram <xref target="RFC7739"/>. This document therefore proposes the
      transmission of IPv6 jumbograms as "atomic fragments" and in the process
      updates <xref target="RFC2675"/>.</t>

      <t>Atomic fragments are defined as "IPv6 packets that contain a Fragment
      Header with the Fragment Offset set to 0 and the M flag set to 0" <xref
      target="RFC6946"/>. Such Fragment Headers may be inserted by the
      original source only and may not be modified by any intermediate IPv6
      nodes on the path. Hence, an atomic fragment generated by the original
      source will remain as an atomic fragment along the entire path up to and
      including the final destination. The original source should therefore be
      permitted to include an atomic fragment Fragment Header in the
      jumbograms it produces. The following section recommends updates to
      <xref target="RFC2675"/> to permit the transmission of IPv6 jumbograms
      as atomic fragments.</t>
    </section>

    <section anchor="issues" title="RFC2675 Updates">
      <t>The following updates to <xref target="RFC2675"/> are requested:<list
          style="symbols">
          <t>Section 3, third paragraph, change: "The Jumbo Payload option
          must not be used in a packet that carries a Fragment header" to:
          "The Jumbo Payload option must not be used in a packet that carries
          a non-atomic Fragment header <xref target="RFC6946"/>".</t>

          <t>Section 3, in the list of errors, change: "error: Jumbo Payload
          option present and Fragment header present" to: "error: Jumbo
          Payload option present and non-atomic Fragment header present".</t>

          <t>Add [RFC6946] to Informative References.</t>
        </list></t>
    </section>

    <section anchor="implement" title="Implementation Status">
      <t>TBD.</t>
    </section>

    <section anchor="iana" title="IANA Considerations">
      <t>This document has no IANA considerations.</t>
    </section>

    <section anchor="secure" title="Security Considerations">
      <t>Communications networking security is necessary to preserve
      confidentiality, integrity and availability.</t>
    </section>

    <section anchor="ack" title="Acknowledgements">
      <t>This work was inspired by ongoing AERO/OMNI/DTN investigations.</t>

      <t>.</t>
    </section>
  </middle>

  <back>
    <references title="Normative References">
      <?rfc ?>

      <?rfc ?>

      <?rfc ?>

      <?rfc include="reference.RFC.2675"?>

      <?rfc ?>

      <?rfc include="reference.RFC.8200" ?>
    </references>

    <references title="Informative References">
      <?rfc ?>

      <?rfc ?>

      <?rfc include="reference.RFC.6946"?>

      <?rfc include="reference.RFC.7739"?>

      <?rfc ?>

      <?rfc ?>
    </references>
  </back>
</rfc>
