Re: [Secdispatch] [EXTERNAL] Re: Request a short agenda slot for draft-eastlake-fnv-18.txt

Benjamin Kaduk <kaduk@mit.edu> Wed, 13 July 2022 03:25 UTC

Return-Path: <kaduk@mit.edu>
X-Original-To: secdispatch@ietfa.amsl.com
Delivered-To: secdispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED53BC157B4A for <secdispatch@ietfa.amsl.com>; Tue, 12 Jul 2022 20:25:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mit.edu
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zTNMQMrCcC3H for <secdispatch@ietfa.amsl.com>; Tue, 12 Jul 2022 20:25:22 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 733F6C157B51 for <secdispatch@ietf.org>; Tue, 12 Jul 2022 20:25:20 -0700 (PDT)
Received: from kduck.mit.edu (c-73-169-244-254.hsd1.wa.comcast.net [73.169.244.254]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 26D3P5m9021117 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 12 Jul 2022 23:25:12 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mit.edu; s=outgoing; t=1657682714; bh=XgTIl54RvreKq1KTmGHbEEGGlw+0sgkyoRF2v+eoGb8=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=LGYkeb7luwQ5Jgr+DHD3VSUILPdDmY2QTpbqEv69RScae8ItXCq9HVKih/yUDlXo3 6wIGn8pwBJvF/+fn/9mCL/LzMEdIgej5edWXPVVHE/p/1ERAsFncUnGv9KPFM/1mvK N2Zti99xlLp+6sy/SOq84LbtG00HEiXvpxHlBlYRb5Vg5wI98vJ02JoK8DoR41Xbux OUbBPq7Gh6B9+d2cEdDIK0oYrX6lqHYlaQKPhW2SzaDR9+nzJTHt5gpuiSW1N/HFJF PAPK/vfl/LpoVkVEAGUY3J6CC0VEX2l12JYsVu+TFEWva9PwOpIwCfGirYbX2FzR9X pob+IH9ESpkSQ==
Date: Tue, 12 Jul 2022 20:25:04 -0700
From: Benjamin Kaduk <kaduk@mit.edu>
To: Mike Ounsworth <Mike.Ounsworth=40entrust.com@dmarc.ietf.org>
Cc: Donald Eastlake <d3e3e3@gmail.com>, Eric Rescorla <ekr@rtfm.com>, IETF SecDispatch <secdispatch@ietf.org>
Message-ID: <20220713032504.GP26442@kduck.mit.edu>
References: <165758360030.4959.14317065028417609939@ietfa.amsl.com> <CAF4+nEE414HVF1PnQ6qtoJhhfg-O2mDBn4LUVDXrXzyM7uJLNQ@mail.gmail.com> <CABcZeBPk-V6xz1DqqRjX_QVseeunK9yk7zpHxwyxRNsgdW+dWg@mail.gmail.com> <CAF4+nEFogK0hSegGSR6YyVzVfdRen0vGcwa2uLZx-DvPphdM+w@mail.gmail.com> <CH0PR11MB5739E8D419DBBDE3580C41A99F899@CH0PR11MB5739.namprd11.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CH0PR11MB5739E8D419DBBDE3580C41A99F899@CH0PR11MB5739.namprd11.prod.outlook.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdispatch/lYcile8VxzLpY8_us5y5ecBq9dg>
Subject: Re: [Secdispatch] [EXTERNAL] Re: Request a short agenda slot for draft-eastlake-fnv-18.txt
X-BeenThere: secdispatch@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Security Dispatch <secdispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdispatch>, <mailto:secdispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdispatch/>
List-Post: <mailto:secdispatch@ietf.org>
List-Help: <mailto:secdispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdispatch>, <mailto:secdispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jul 2022 03:25:27 -0000

Is anyone else bothered by the juxtaposition of "secure-sequence-numbers"
and "non-cryptographic hash"?

-Ben

On Wed, Jul 13, 2022 at 02:34:49AM +0000, Mike Ounsworth wrote:
> I see you added draft-ietf-bfd-secure-sequence-numbers as a dependent draft in your most recent versions, so should your FNV draft go through the BFD WG along with it?
> 
[...]
> -----Original Message-----
> From: Secdispatch <secdispatch-bounces@ietf.org> On Behalf Of Donald Eastlake
> Sent: July 12, 2022 9:17 PM
> To: Eric Rescorla <ekr@rtfm.com>
> Cc: IETF SecDispatch <secdispatch@ietf.org>
> Subject: [EXTERNAL] Re: [Secdispatch] Request a short agenda slot for draft-eastlake-fnv-18.txt
> 
> ______________________________________________________________________
> Security might not be the perfect Area for a non-cryptographic hash, but it seems to me like the closest fit.