Re: Transmission of IPv6 Jumbograms as Atomic Fragments

Mark Smith <markzzzsmith@gmail.com> Fri, 19 November 2021 00:11 UTC

Return-Path: <markzzzsmith@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B97243A0C0A for <ipv6@ietfa.amsl.com>; Thu, 18 Nov 2021 16:11:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.037
X-Spam-Level:
X-Spam-Status: No, score=-1.037 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=0.559, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ABaSdwaIQpHe for <ipv6@ietfa.amsl.com>; Thu, 18 Nov 2021 16:11:17 -0800 (PST)
Received: from mail-io1-xd32.google.com (mail-io1-xd32.google.com [IPv6:2607:f8b0:4864:20::d32]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 65E633A0C09 for <ipv6@ietf.org>; Thu, 18 Nov 2021 16:11:17 -0800 (PST)
Received: by mail-io1-xd32.google.com with SMTP id k22so10409839iol.13 for <ipv6@ietf.org>; Thu, 18 Nov 2021 16:11:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=T3k4d1JXSGllGmKANO9mZRARCbCHOCbMNFLZtm3/9IQ=; b=HVuva3RhJDxii+5rr3flzc6l+5hrXcbiMQRjfHs7T6FoN9K11ZIe/Ve2k/Li1NFwi7 dIMTgvP9UYn3YftqAGBsXECtNO4XajAiOSiz3sm9LAlNk9g7keatseYCtOl1z065O3bW th3XYaImeHVvAkxfMXe2JNAv3r64SoFLD1xxjzbDR3t8nJs5wJ02cKiJXwU2qRJmytdI O0D446d5vJ3m7Pa3RHn2VvGwra7SIOnYUV3FWcTqTu1YPdS1QePCZVq53BSLaz1xm8N5 VEeK+IVitaggjK8wZXcDxPX6PFgNzSboTOHvzJtSB3DFg+FtG3ofs1S+0fy86zDqnKZ3 f3zw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=T3k4d1JXSGllGmKANO9mZRARCbCHOCbMNFLZtm3/9IQ=; b=8FneLzIxNkRauTLdvzZb0Tn1nJUBDyizBM23+S/xoOW4xVMh1IBmQ7RH+bCrnwBQVT Dz+DkFBu3dlHaSQsKHmCJYfZNqSfklyYZ9PH1evpDyLH34/GLr8/ze+BjRrmsszGH4b9 LQmJ7/fg1W72ToWWCe/iHtp5ySlvaO4AJgI+D/tXxyZPStyDu1hQNHIiADxJNuvSrMRU MB2afCDNTDi2eQUx6UXXpwd/7xvi2dEKPgKrlzIuZIyIuRmzAeuJDYYdLkJkPYkXiDbf k2Xj/s/kGz/qRmgBNdsHsViPQfbp9emzQ7/01d4QywqxnMAWmvq08RhC8doSRCdCpluj SjVQ==
X-Gm-Message-State: AOAM531qqk7XUDD0NwZxn6FsMUFPDWVNXtpODWNM0cnoYioHoJ1GQs20 JGUk3JKJTtJFHGyWx5eooJ9LX3C2bsGX9luIssQ=
X-Google-Smtp-Source: ABdhPJxc18LWPJ6jDW7EzQ62GIMByOn1DA1CqPuPV7yB1/t37WdM5y+WggN7J/xd54scrxYLzfclgVEe4uogK5Ll3NE=
X-Received: by 2002:a02:6901:: with SMTP id e1mr23534684jac.0.1637280676464; Thu, 18 Nov 2021 16:11:16 -0800 (PST)
MIME-Version: 1.0
References: <d355bbb78c964b6b89e12e3d784c2d51@boeing.com>
In-Reply-To: <d355bbb78c964b6b89e12e3d784c2d51@boeing.com>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Fri, 19 Nov 2021 11:10:50 +1100
Message-ID: <CAO42Z2w95cKOJuBvG4VUgiyQtraDnTjJWLuMOh2vVfkBs_OAJg@mail.gmail.com>
Subject: Re: Transmission of IPv6 Jumbograms as Atomic Fragments
To: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
Cc: Nick Hilliard <nick@foobar.org>, IPv6 List <ipv6@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000001e4c9e05d1191dbe"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/npdcM5PTjR0edxV4LW-ZU3ViGSI>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Nov 2021 00:11:22 -0000

On Fri, 19 Nov 2021, 07:12 Templin (US), Fred L, <Fred.L.Templin@boeing.com>
wrote:

> Nick,
>
> > Do you have a use case in mind for the ID field?
>
> Thank you for this timely question. I just got done posting a major update
> to the
> draft, which now is titled: "IPv6 Packet Identification" and considers all
> forms of
> IPv6 packets and not just Jumbograms. In answer to your question here is
> the new
> Section 2 text from the draft (link provided below):
>
> "2.  IPv6 Packet Identification
>
>    When IPv6 sources and destinations have some way of maintaining
>    "windows" of acceptable Identification values, the destination may be
>    able to examine received packet Identifications to determine whether
>    they likely originated from the source.


This seems to be describing the sequence number verification used in IPsec
AH per RFC 4302.

It may be worth either just using AH as is, and getting all of its other
benefits, or look at creating a simplified version of it rather than
modifying the jumbogram EH to start duplicating existing AH functionality.

According to RFC 4302 there are a range of reserved SPI values (1 through
255), you could use one of those to indicate a light weight version of AH
that just does packet identification, avoiding the need to set up Security
Associations with IKE.

Regards,
Mark.

The AERO
>    [I-D.templin-6man-aero] and OMNI [I-D.templin-6man-omni]
>    specifications discuss methods for maintaining windows of
>    unpredictable values that may reduce attack profiles in some
>    environments."
>
> Thanks, and here is the draft URL:
>
> https://datatracker.ietf.org/doc/draft-templin-6man-jumbofrag/
>
> Fred
>
> > -----Original Message-----
> > From: Nick Hilliard [mailto:nick@foobar.org]
> > Sent: Thursday, November 18, 2021 9:16 AM
> > To: Templin (US), Fred L <Fred.L.Templin@boeing.com>
> > Cc: IPv6 List <ipv6@ietf.org>
> > Subject: Re: Transmission of IPv6 Jumbograms as Atomic Fragments
> >
> >
> > Templin (US), Fred L wrote on 18/11/2021 15:23:
> > > Bob, what I want is exactly the Identification field that is found in
> the Fragment Header
> > > while simply leaving the rest of the fields of that header set to 0
> >
> > Do you have a use case in mind for the ID field?
> >
> > Nick
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>