From nobody Sat Dec  5 10:59:24 2020
Return-Path: <ekr@rtfm.com>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
 by ietfa.amsl.com (Postfix) with ESMTP id AA4BC3A0762
 for <secdir@ietfa.amsl.com>; Sat,  5 Dec 2020 10:59:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level: 
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
 HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001,
 URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key)
 header.d=rtfm-com.20150623.gappssmtp.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 0FjrMhoy1zRl for <secdir@ietfa.amsl.com>;
 Sat,  5 Dec 2020 10:59:17 -0800 (PST)
Received: from mail-lf1-x130.google.com (mail-lf1-x130.google.com
 [IPv6:2a00:1450:4864:20::130])
 (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 CF5663A074B
 for <secdir@ietf.org>; Sat,  5 Dec 2020 10:59:16 -0800 (PST)
Received: by mail-lf1-x130.google.com with SMTP id v14so12336342lfo.3
 for <secdir@ietf.org>; Sat, 05 Dec 2020 10:59:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=rtfm-com.20150623.gappssmtp.com; s=20150623;
 h=mime-version:references:in-reply-to:from:date:message-id:subject:to
 :cc; bh=+Y/NZITf/yqVml9sTuFJ9ZdqXkbpFTLZHUBv8OLEsWg=;
 b=GWcgFhuelKbr7ijaY5ECiaZ4amvt1fRHwiOP2Jn7OGmEyWCbYqyeHP8reI2jmaJM1Q
 cdzCFAfdN+PdGK/vmnL386w5C5N62e8aRvCPUw9kkjfIxkC6zS1F6Wu7vIsWqv55l+l6
 ytTSzVjXN0QmqM0D/Pbwxv/NP0sEMduNv1NOPtYJU8NeCg+2VPDQRZgbiLdT6g8RwHM4
 soiDmKFXlLCXu8icL0EKmszLwdoE95uEXvmzYlTohgZuqnlj099LRJVYv8ouZW+3Az+h
 XYHWJnv0PR2LcepJnZ7md9B/xdt+pcTvGIwYm7ezbAMPBgUW6WRvRndv1Tp2wOVznRLW
 kfbA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:mime-version:references:in-reply-to:from:date
 :message-id:subject:to:cc;
 bh=+Y/NZITf/yqVml9sTuFJ9ZdqXkbpFTLZHUBv8OLEsWg=;
 b=tFVq8ujduPp4utuQe5+H+Vs+H31cc2BWZvBa4qier4f3eKGsG1xEZpdQ53C0usBKIM
 AIP/W0fB27etYkk3qplBx7EF1inA9Bd8LbRDfr4ZaqNOLtYXIBTIt7OcRel5nsOkNvcT
 MlvuwnMbGE06qWS6ECiiMximkyASl1/Jvw/ts1vXWfLuwjb/pFvzOYgxBNjWwXkuuPSW
 jSsSrzqXCpQlt9VkuDRKNJbMyJpjHEreVPVDXi0Uu78RPZb57B56x0/HKJEUVBWIF1F8
 yXvNZYBHiIazsTtCgfMW/PKF63Is0ETegSkXibnrQSrimHDflN0OulHsAB2Dswg36IPd
 tE7Q==
X-Gm-Message-State: AOAM5326l0V53PWjAlABXTeXfArW0jx2yVX0vMbkTXVXbWBz1OsrCBdk
 LrYOS4s+GrM+w2Id9BmuOg0dxaHJIwijGENHrGYloQ==
X-Google-Smtp-Source: ABdhPJw453E+pvza93ecJbOEqYnkjc2Dodat3F4YnA8MILQGLwK+dh8Gg2vhZQASEeD33xIN7/zqIOqz4QeGhThqAK0=
X-Received: by 2002:a05:6512:368a:: with SMTP id
 d10mr5510438lfs.579.1607194755036; 
 Sat, 05 Dec 2020 10:59:15 -0800 (PST)
MIME-Version: 1.0
References: <160693121881.9413.5642470305677631145@ietfa.amsl.com>
 <17AFD6F5-11DA-41BC-8C37-E1893648041D@isc.org>
 <CABcZeBPRn3aTBsApawvk_Ecyzdbi+SX9=b74y0_uhYx_Y8p-5w@mail.gmail.com>
 <51A61472-45D7-4133-80BC-1F470B5CBD84@isc.org>
 <20201204203635.GS64351@kduck.mit.edu>
 <320692C5-9C47-4CE6-8D6C-A62C2B50728F@akamai.com>
In-Reply-To: <320692C5-9C47-4CE6-8D6C-A62C2B50728F@akamai.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Sat, 5 Dec 2020 10:58:38 -0800
Message-ID: <CABcZeBOQXcihkksYGa1Khc0ZZgvb-EJ3iy5S9MEQVeL95pohqQ@mail.gmail.com>
To: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>
Cc: Benjamin Kaduk <kaduk@mit.edu>,
 =?UTF-8?B?T25kxZllaiBTdXLDvQ==?= <ondrej@isc.org>, 
 "last-call@ietf.org" <last-call@ietf.org>, 
 "draft-ietf-dnsop-server-cookies.all@ietf.org"
 <draft-ietf-dnsop-server-cookies.all@ietf.org>, dnsop WG <dnsop@ietf.org>, 
 "secdir@ietf.org" <secdir@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000758c5305b5bc3052"
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/wZq9M2c3hrd5SpOc1KAM3TuPH0w>
Subject: Re: [secdir] [DNSOP] [Last-Call] Secdir last call review of
 draft-ietf-dnsop-server-cookies-04
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>,
 <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdir/>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>,
 <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Dec 2020 18:59:20 -0000

--000000000000758c5305b5bc3052
Content-Type: text/plain; charset="UTF-8"

On Sat, Dec 5, 2020 at 6:58 AM Salz, Rich <rsalz=40akamai.com@dmarc.ietf.org>
wrote:

> There is a fair amount of academic study around SipHash, and while
> everyone can make mistakes, its creators have a pretty good reputation. I
> don't think we can say SipHash is unknown in the industry.
>
> The TLSWG made it a practice to ask CFRG to "approve" all crypto it used
> (except perhapd HKDF, but that's a side note). The DNSOP has no such
> practice.
>

I recognize that this is a bigger issue, but I believe this should be the
practice for the IETF as a whole and I would encourage the SEC ADs to work
to make it so.

-Ekr



> If SECDIR or the Ads thinks SipHash isn't good, it would be great to hear
> reasons.  I haven't heard any yet.
>
>
> _______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>

--000000000000758c5305b5bc3052
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Sat, Dec 5, 2020 at 6:58 AM Salz, =
Rich &lt;rsalz=3D<a href=3D"mailto:40akamai.com@dmarc.ietf.org">40akamai.co=
m@dmarc.ietf.org</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" =
style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pa=
dding-left:1ex">There is a fair amount of academic study around SipHash, an=
d while everyone can make mistakes, its creators have a pretty good reputat=
ion. I don&#39;t think we can say SipHash is unknown in the industry.<br>
<br>
The TLSWG made it a practice to ask CFRG to &quot;approve&quot; all crypto =
it used (except perhapd HKDF, but that&#39;s a side note). The DNSOP has no=
 such practice.<br></blockquote><div><br></div><div>I recognize that this i=
s a bigger issue, but I believe this should be the practice for the IETF as=
 a whole and I would encourage the SEC ADs to work to make it so.<br></div>=
<div><br></div><div>-Ekr</div><div><br></div><div><br></div><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid =
rgb(204,204,204);padding-left:1ex">
<br>
If SECDIR or the Ads thinks SipHash isn&#39;t good, it would be great to he=
ar reasons.=C2=A0 I haven&#39;t heard any yet.<br>
<br>
<br>
_______________________________________________<br>
DNSOP mailing list<br>
<a href=3D"mailto:DNSOP@ietf.org" target=3D"_blank">DNSOP@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/dnsop" rel=3D"noreferrer" =
target=3D"_blank">https://www.ietf.org/mailman/listinfo/dnsop</a><br>
</blockquote></div></div>

--000000000000758c5305b5bc3052--

