Re: [DNSOP] Fwd: New Version Notification for draft-sury-toorop-dns-cookies-algorithms-00.txt

Loganaden Velvindron <loganaden@gmail.com> Fri, 31 May 2019 18:09 UTC

Return-Path: <loganaden@gmail.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A172C120314 for <dnsop@ietfa.amsl.com>; Fri, 31 May 2019 11:09:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham 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 NBiAKAEdaKUS for <dnsop@ietfa.amsl.com>; Fri, 31 May 2019 11:09:41 -0700 (PDT)
Received: from mail-it1-x12f.google.com (mail-it1-x12f.google.com [IPv6:2607:f8b0:4864:20::12f]) (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 28295120313 for <dnsop@ietf.org>; Fri, 31 May 2019 11:09:41 -0700 (PDT)
Received: by mail-it1-x12f.google.com with SMTP id h9so2531676itk.3 for <dnsop@ietf.org>; Fri, 31 May 2019 11:09:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=/VpexF2u3MmC3XUOtWxokxpnaoP2D5JS+bV8O9uI9dM=; b=OJHNPSveSSgwjLj2eJ5+yZ+kUpTRZ2+J/gRn0ieIw2mLubXPq3K/cefxIVbkUYLlvm k1BOzJo7MWy631j8PNpJwurUIw5VBMWL9xGfMpHTS0EKvA9/Jb7xpu5KIT3QTElhsUO+ 1vuv4QNxV6oHPSr9sKYE8nf5drNI0Tpws082f8+bMVpNvBsXfVNUf+bFKBsZKAVhKicr xtGsIP7hzIYP6XFzF/HcBZGmWp3kRDNG2XAQctkAcXmQnkkiZ2VaCnsYN4CB5KHSiXn6 JRJ59/s3y/aWipbCvPjKsisLgVHumIePPhn/uqDJ6O/uB44zwk+6PNz5c8wi6FcisQxO 0HpA==
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=/VpexF2u3MmC3XUOtWxokxpnaoP2D5JS+bV8O9uI9dM=; b=mcQRzP76+NjZov+N61FhCfoADUVMZe8tvb4B7Bq/UBWn2omH2sHZNo8nns6/hHpdKD GeDpZjrojd4WD7RBbnVdMrDWPLWu6VuBqmtq4n2hy+JB5E5xYvVw49MQVYLYI1HmoQCS Le+Cmrp9gRBynBDRHOMQTXzuwVw6bQveI9/F6UNUqAKMwO569J5ea/HYZcYUzpXYHbNE b5wubSL6aqhyy0w1SEKYrTOQVggoamXuEB6Rn6LWHrpo7Ho8w4aWSaWZPDFig8ceXdss c+AWITKmVVNIcIgyY22PNx45VfzfVUVbc40vo2Al3zIw9s+aBv+Jvy+XPIIoG0K1wgRW vBxA==
X-Gm-Message-State: APjAAAVesTnP4Lxcv6LgoJQ6MAX7M57dU1msQ55sPicEWtEjPZO3ugHr +GYLh2pjCONkz+42MqCA7gt+Djt49zkhiBcY6k0=
X-Google-Smtp-Source: APXvYqy0f0QUvyBVmfJ8Z5mR1V6hZu2l5rbBlQgpNtB5wcWUsOSg3qSdOds2Y6IJSGODG0AZ3VNVB8yVQiZKceg5PuU=
X-Received: by 2002:a24:eec1:: with SMTP id b184mr8811894iti.61.1559326180491; Fri, 31 May 2019 11:09:40 -0700 (PDT)
MIME-Version: 1.0
References: <155232074470.23098.423370236233432374.idtracker@ietfa.amsl.com> <5ea56c94-5462-ac44-462f-0f0e0a435e5e@nlnetlabs.nl>
In-Reply-To: <5ea56c94-5462-ac44-462f-0f0e0a435e5e@nlnetlabs.nl>
From: Loganaden Velvindron <loganaden@gmail.com>
Date: Fri, 31 May 2019 22:09:29 +0400
Message-ID: <CAOp4FwRd1q+BtN0YQSbSYaft14LRXB1LdAtrHF6NeZ9utv3tYA@mail.gmail.com>
To: Willem Toorop <willem@nlnetlabs.nl>
Cc: dnsop <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000013c800058a32eb6d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/TA_z8EzXvY_SEs8SPkrq-PZHwEg>
Subject: Re: [DNSOP] Fwd: New Version Notification for draft-sury-toorop-dns-cookies-algorithms-00.txt
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 May 2019 18:09:44 -0000

On Tue, Mar 12, 2019 at 3:29 PM Willem Toorop <willem@nlnetlabs.nl> wrote:

> Dear DNSOP,
>
> A new draft has been submitted addressing the issue of DNS Cookies in
> multi-vendor anycast deployments.
>
> DNS Cookies are currently impractical in such deployments, because one
> implementation - even though it shares its secret with another
> implementation - cannot validate the Server Cookies constructed by that
> other implementation, because their methods for constructing Server
> Cookies differ.
>
> This draft provides precise directions for creating Server Cookies to
> align the implementations.  In doing so, this draft introduces a
> registry for functions suitable for Cookie construction.  More
> specifically, FNV and HMAC-SHA-256-64 are obsoleted and SipHash-2.4 is
> introduced as a suitable function.
>
> Willem
>
> -------- Forwarded Message --------
> Subject: New Version Notification for
> draft-sury-toorop-dns-cookies-algorithms-00.txt
> Date: Mon, 11 Mar 2019 09:12:24 -0700
> From: internet-drafts@ietf.org
> To: Willem Toorop <willem@nlnetlabs.nl>nl>, Ondrej Sury <ondrej@isc.org>
>
>
> A new version of I-D, draft-sury-toorop-dns-cookies-algorithms-00.txt
> has been successfully submitted by Willem Toorop and posted to the
> IETF repository.
>
> Name:           draft-sury-toorop-dns-cookies-algorithms
> Revision:       00
> Title:          Algorithms for Domain Name System (DNS) Cookies
> construction
> Document date:  2019-03-11
> Group:          Individual Submission
> Pages:          7
> URL:
>
> https://www.ietf.org/internet-drafts/draft-sury-toorop-dns-cookies-algorithms-00.txt
> Status:
> https://datatracker.ietf.org/doc/draft-sury-toorop-dns-cookies-algorithms/
> Htmlized:
> https://tools.ietf.org/html/draft-sury-toorop-dns-cookies-algorithms-00
> Htmlized:
>
> https://datatracker.ietf.org/doc/html/draft-sury-toorop-dns-cookies-algorithms
>
>
> Abstract:
>    [RFC7873] left the construction of Server Cookies to the discretion
>    of the DNS Server (implementer) which has resulted in a gallimaufry
>    of different implementations.  As a result, DNS Cookies are
>    impractical to deploy on multi-vendor anycast networks, because the
>    Server Cookie constructed by one implementation cannot be validated
>    by another.
>
>    This document provides precise directions for creating Server Cookies
>    to address this issue.  Furthermore, [FNV] is obsoleted as a suitable
>    Hash function for calculating DNS Cookies.  [SipHash-2.4] is
>    introduced as a new REQUIRED Hash function for calculating DNS
>    Cookies.
>
>    This document updates [RFC7873]
>
>
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> The IETF Secretariat
>
>
Small typo:
I would suggest this:
Section 4 4th paragraph:
"implement only a pseudorandom functions for DNS Cookies"
 to
"implement only a pseudorandom function for DNS Cookies"

  [SipHash-2.4] is a pseudorandom function suitable as message
   authentication code, and this document REQUIRES compliant DNS Server
   to use SipHash24 as a mandatory and default algorithm for DNS Cookies
   to ensure interoperability between the DNS Implementations.

Also, I would suggest explaining a little bit the advantages of SipHas-2.4:

fast computation + quite secure up to now.





_______________________________________________
> DNSOP mailing list
> DNSOP@ietf.org
> https://www.ietf.org/mailman/listinfo/dnsop
>