Re: [DNSOP] Asking for TCP and/or cookies: a trend? (Was: my lone hum against draft-wkumari-dnsop-multiple-responses

Mukund Sivaraman <muks@isc.org> Fri, 22 July 2016 12:52 UTC

Return-Path: <muks@isc.org>
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 EA87E12D09F for <dnsop@ietfa.amsl.com>; Fri, 22 Jul 2016 05:52:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level:
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
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 m1qqOKPNL2NK for <dnsop@ietfa.amsl.com>; Fri, 22 Jul 2016 05:52:48 -0700 (PDT)
Received: from mail.banu.com (mail.banu.com [46.4.129.225]) by ietfa.amsl.com (Postfix) with ESMTP id 47C3212D096 for <dnsop@ietf.org>; Fri, 22 Jul 2016 05:52:48 -0700 (PDT)
Received: from jurassic (unknown [115.118.40.163]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.banu.com (Postfix) with ESMTPSA id A0C792FA0829; Fri, 22 Jul 2016 12:52:44 +0000 (GMT)
Date: Fri, 22 Jul 2016 18:22:40 +0530
From: Mukund Sivaraman <muks@isc.org>
To: Paul Wouters <paul@nohats.ca>
Message-ID: <20160722125240.GA24166@jurassic>
References: <b00ec4.3833.15606420d47.Coremail.yzw_iplab@163.com> <236F5488-42D4-4A89-ACAB-B55FD2B5782A@fl1ger.de> <20160720051949.8FC154EF155E@rock.dv.isc.org> <36A593C1-1F01-4FE1-BC9A-3279F6460358@rfc1035.com> <D65E8617-107E-4B13-986F-24088D0C57C2@powerdns.com> <20160721133730.GA10324@nic.fr> <alpine.LRH.2.20.1607211101590.17541@bofh.nohats.ca> <20160721153845.GA13632@jurassic> <alpine.LRH.2.20.1607220638520.12891@bofh.nohats.ca>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha512"; protocol="application/pgp-signature"; boundary="VbJkn9YxBvnuCH5J"
Content-Disposition: inline
In-Reply-To: <alpine.LRH.2.20.1607220638520.12891@bofh.nohats.ca>
User-Agent: Mutt/1.6.2 (2016-07-01)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/kLGRsEWxgvkJVpG202GwQINsn3w>
Cc: IETF dnsop WG <dnsop@ietf.org>, Peter van Dijk <peter.van.dijk@powerdns.com>
Subject: Re: [DNSOP] Asking for TCP and/or cookies: a trend? (Was: my lone hum against draft-wkumari-dnsop-multiple-responses
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.17
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, 22 Jul 2016 12:52:50 -0000

Hi Paul

On Fri, Jul 22, 2016 at 06:45:16AM -0400, Paul Wouters wrote:
> > DJB's curveCP comes to mind about how it prevents amplification for the
> > initial handshake.
> 
> some googling only finds marketing material, not a specification I can
> read :P

Here it is:
http://curvecp.org/packets.html

(specifically, the section under "Client Hello packet details")

		Mukund