IETF Logo Mail Archive

Re: [tsvwg] Possible UDP-Option: Cookie

Joe Touch <touch@strayalpha.com> Wed, 20 March 2019 14:26 UTC

Return-Path: <touch@strayalpha.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC3621275E9 for <tsvwg@ietfa.amsl.com>; Wed, 20 Mar 2019 07:26:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.22
X-Spam-Level:
X-Spam-Status: No, score=-1.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_NEUTRAL=0.779] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=strayalpha.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 bgooLgyJ1QmL for <tsvwg@ietfa.amsl.com>; Wed, 20 Mar 2019 07:26:36 -0700 (PDT)
Received: from server217-3.web-hosting.com (server217-3.web-hosting.com [198.54.115.226]) (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 04A9E126D00 for <tsvwg@ietf.org>; Wed, 20 Mar 2019 07:26:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; s=default; h=To:References:Message-Id:Cc:Date:In-Reply-To: From:Subject:Mime-Version:Content-Type:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=dXZ6FMgybu6nNy/jIskEj0mTZm9ONyccCRvdRbCgCPw=; b=3sYZDzp71xpJckup/Wy0HbQR9 eKhXCHszdrievOOJdnIJ+N11jxeekuBVef+dva+CVJ3P1DplWCn061Ak77N8jXyNxb0a4t1e+en74 egj3d4QavHG1koBVh2dxVaHNCCNTM9JQxcGPHRoaynPZClhK1OanLmgM3XsPT0Mh1Jxc9tIg5/gA1 U/w3SU+iCAcoLn6OHqi9NS15MElY34I5bBW30oP0TIg8ReaO3H6yp1SSSEtuor5uJ61anRfEJNAHu D4BA2wPdO4mQBuZtRw4FxR67t+kZHVOfde+CKtfYNdnj55/K/WX3/aLmHH5qj+1HzIqWCAcRuf3ud WSpqt11gA==;
Received: from cpe-172-250-240-132.socal.res.rr.com ([172.250.240.132]:50104 helo=[192.168.1.77]) by server217.web-hosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91) (envelope-from <touch@strayalpha.com>) id 1h6cAq-003IEP-Rp; Wed, 20 Mar 2019 10:26:35 -0400
Content-Type: multipart/alternative; boundary="Apple-Mail=_DD36EFAF-50A8-47A4-BFF6-70FDA6C5B786"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Joe Touch <touch@strayalpha.com>
In-Reply-To: <20190320100743.GA19737@bugle.employees.org>
Date: Wed, 20 Mar 2019 07:26:32 -0700
Cc: tsvwg <tsvwg@ietf.org>
Message-Id: <B78767DA-1C50-4973-AB60-C0CB0C9397C5@strayalpha.com>
References: <5C8FDEED.8010701@erg.abdn.ac.uk> <CALx6S36fQcRdgvCG3XS78EecFjdb36D22iBzovXcODH_W+BHbg@mail.gmail.com> <5be88c76-d65a-c491-86be-74a52fef7687@strayalpha.com> <CALx6S35h+ANRpqrEyC97JocXUrDw_+b85a8bP7QgjSchMPXF-g@mail.gmail.com> <62f9f885-5dd6-78d4-2d8a-8fab83871529@strayalpha.com> <CALx6S35bb5YpjR16OfQN+JJw3O3LG=NqkdFEnKdTEd3UoZWo5A@mail.gmail.com> <190BFA86-2DE3-4BB1-A833-E67D49B641FB@strayalpha.com> <CALx6S35vym9jfN5E6HVLU5RJj0k2p0i=dc1a+pb=ETx1WQUoxg@mail.gmail.com> <57E0E8CF-EA9A-4BC8-89D2-296D3CBBF7BA@strayalpha.com> <20190319231309.GA38527@bugle.employees.org> <20190320100743.GA19737@bugle.employees.org>
To: Derek Fawcus <dfawcus+lists-tsvwg@employees.org>
X-Mailer: Apple Mail (2.3445.9.1)
X-OutGoing-Spam-Status: No, score=-1.0
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server217.web-hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - strayalpha.com
X-Get-Message-Sender-Via: server217.web-hosting.com: authenticated_id: touch@strayalpha.com
X-Authenticated-Sender: server217.web-hosting.com: touch@strayalpha.com
X-Source:
X-Source-Args:
X-Source-Dir:
X-From-Rewrite: unmodified, already matched
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/D8PGE71t5iePB_TJSFjOqcUtp50>
Subject: Re: [tsvwg] Possible UDP-Option: Cookie
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Mar 2019 14:26:37 -0000


> On Mar 20, 2019, at 3:07 AM, Derek Fawcus <dfawcus+lists-tsvwg@employees.org> wrote:
> 
> So do we need some text in the security considerations section to discuss
> this, or maybe even a new cookie option to allow for a form of soft state
> acknowledged handshake?

Soft state can be accomplished in a variety of ways; there’s no reason to force a single way of doing this.

Joe

v2.23.0 | Report a Bug | By Email