I would agree it must not be there when DF is 1. When DF is zero, there is always the possibility that a forwarding router will fragment the packet. From a practical standpoint, one wants the originator of the packet to provide the option whenever sending to a different subnet.
I would also suggest requiring originators to configure whether and under what circumstances the option is used. Or perhaps some sort of automatic configuration protocol? Thinking a little more, I worry about the amount of manual experimentation/configuration needed to deploy this. It seems like it’s very subject to configuration rot over time. What about combining this with some IP options to enable a simple IPSec transport using just MD5 or GMAC authentication (for data integrity only)? >From Phone ________________________________ From: Int-area <int-area-boun...@ietf.org> on behalf of to...@strayalpha.com <to...@strayalpha.com> Sent: Saturday, July 29, 2023 10:55:10 AM To: Templin (US), Fred L <fred.l.temp...@boeing.com> Cc: IETF intarea WG <int-area@ietf.org>; IPv6 List <i...@ietf.org>; ietf <i...@ietf.org> Subject: [EXTERNAL] Re: [Int-area] I-D Action: draft-templin-intarea-ipid-ext-00.txt [EXTERNAL SENDER: This email originated from outside of Stratus Technologies. Do not click links or open attachments unless you recognize the sender and know the content is safe.] ________________________________ Hi, Fred (et al.), It might be useful to be clear whether this option MUST NOT be used on atomic datagrams (i.e., where IPv4 DF==1 or when not source fragmented) and that it cannot be used for purposes other than reassembly (as the regular ID is per RFC 6484). Joe — Dr. Joe Touch, temporal epistemologist www.strayalpha.com<http://www.strayalpha.com> On Jul 28, 2023, at 12:54 PM, Templin (US), Fred L <fred.l.temp...@boeing.com> wrote: -----Original Message----- From: I-D-Announce <i-d-announce-boun...@ietf.org> On Behalf Of internet-dra...@ietf.org Sent: Friday, July 28, 2023 12:29 PM To: i-d-annou...@ietf.org Subject: I-D Action: draft-templin-intarea-ipid-ext-00.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Identification Extension Options for the Internet Protocol Author : Fred L. Templin Filename : draft-templin-intarea-ipid-ext-00.txt Pages : 10 Date : 2023-07-28 Abstract: The Internet Protocol, version 4 (IPv4) header includes a 16 bit Identification field in all packets, but this length is too small to ensure reassembly integrity even at moderate data rates in modern networks. Even for Internet Protocol, version 6 (IPv6), the 32 bit Identification field may be smaller than desired for some intended uses. This document addresses these limitations by defining both an Identification Extension option for IPv4 and a corresponding Destination Option for IPv6. The IETF datatracker status page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-templin-intarea-ipid-ext/<https://protect-us.mimecast.com/s/NyAZClYEPYtO4AJ8SyGMHu/> There is also an htmlized version available at: https://datatracker.ietf.org/doc/html/draft-templin-intarea-ipid-ext-00<https://datatracker.ietf.org/doc/html/draft-templin-intarea-ipid-ext-00> Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts _______________________________________________ I-D-Announce mailing list i-d-annou...@ietf.org https://www.ietf.org/mailman/listinfo/i-d-announce<https://www.ietf.org/mailman/listinfo/i-d-announce> Internet-Draft directories: http://www.ietf.org/shadow.html<http://www.ietf.org/shadow.html> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt<ftp://ftp.ietf.org/ietf/1shadow-sites.txt> _______________________________________________ Int-area mailing list Int-area@ietf.org https://www.ietf.org/mailman/listinfo/int-area<https://www.ietf.org/mailman/listinfo/int-area>
_______________________________________________ Int-area mailing list Int-area@ietf.org https://www.ietf.org/mailman/listinfo/int-area
