Re: [Spud] New Version Notification for draft-herbert-transports-over-udp-00.txt

Brian Trammell <ietf@trammell.ch> Mon, 23 May 2016 14:32 UTC

Return-Path: <ietf@trammell.ch>
X-Original-To: spud@ietfa.amsl.com
Delivered-To: spud@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E85C812D944 for <spud@ietfa.amsl.com>; Mon, 23 May 2016 07:32:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.328
X-Spam-Level:
X-Spam-Status: No, score=-3.328 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.426, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham 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 Y7SKc46BReS1 for <spud@ietfa.amsl.com>; Mon, 23 May 2016 07:32:48 -0700 (PDT)
Received: from trammell.ch (trammell.ch [5.148.172.66]) by ietfa.amsl.com (Postfix) with ESMTP id 03AE812D93C for <spud@ietf.org>; Mon, 23 May 2016 07:32:47 -0700 (PDT)
Received: from [IPv6:2001:67c:64:49:b0cc:febd:b2ea:c9b0] (unknown [IPv6:2001:67c:64:49:b0cc:febd:b2ea:c9b0]) by trammell.ch (Postfix) with ESMTPSA id CC5F41A049E; Mon, 23 May 2016 16:32:46 +0200 (CEST)
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Content-Type: multipart/signed; boundary="Apple-Mail=_B47F3C89-A480-4BCF-B961-F376249D3C15"; protocol="application/pgp-signature"; micalg="pgp-sha512"
X-Pgp-Agent: GPGMail 2.6b2
From: Brian Trammell <ietf@trammell.ch>
In-Reply-To: <655C07320163294895BBADA28372AF5D48861FF5@FR712WXCHMBA15.zeu.alcatel-lucent.com>
Date: Mon, 23 May 2016 16:32:47 +0200
Message-Id: <BEE1A718-0D9E-49BC-B851-225CC2B42914@trammell.ch>
References: <CALx6S377qRfq7ufRVUx6Yn7ec4=EmK_=FL14PWT_qf4g840mbQ@mail.gmail.com> <20160519185943.GM12994@cisco.com> <CALx6S37qPpKpCT6ZpVQwRWf1XFKESYasOBcz26To9zw0GRyz5Q@mail.gmail.com> <573E31E1.807@isi.edu> <20160519221102.GS12994@cisco.com> <573E3C5E.2090300@isi.edu> <20160520001323.GC2511@cisco.com> <573E6303.8030701@isi.edu> <20160520012431.GF2511@cisco.com> <573F47C0.3010501@isi.edu> <20160520182115.GO2511@cisco.com> <CALx6S378X7bk5q-u7Kxu+s3w1ZZ5kZcyhCVEUyPG_=hVzNH2tA@mail.gmail.com> <655C07320163294895BBADA28372AF5D48860CBE@FR712WXCHMBA15.zeu.alcatel-lucent.com> <DM2PR0301MB06553A6249DB5BAD06D2A96BA84B0@DM2PR0301MB0655.namprd03.prod.outlook.com> <CALx6S35m9xCvzLqXyLgARdoep_WfZBoLsGFNUVUx8GfxXfiYNg@mail.gmail.com> <CAGD1bZZFkWNQ6dnETVoA0oat2h03JscCD6OcZPasFdKTYnkMQQ@mail.gmail.com> <655C07320163294895BBADA28372AF5D48861FF5@FR712WXCHMBA15.zeu.alcatel-lucent.com>
To: "Scharf, Michael (Nokia - DE)" <michael.scharf@nokia.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <http://mailarchive.ietf.org/arch/msg/spud/3s30ERBWjIt-48sSHNKbeu-VwyY>
Cc: "Toerless Eckert (eckert)" <eckert@cisco.com>, Joe Touch <touch@isi.edu>, Tom Herbert <tom@herbertland.com>, "spud@ietf.org" <spud@ietf.org>, Christian Huitema <huitema@microsoft.com>, Jana Iyengar <jri@google.com>
Subject: Re: [Spud] New Version Notification for draft-herbert-transports-over-udp-00.txt
X-BeenThere: spud@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Session Protocol Underneath Datagrams <spud.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spud>, <mailto:spud-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spud/>
List-Post: <mailto:spud@ietf.org>
List-Help: <mailto:spud-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spud>, <mailto:spud-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 May 2016 14:32:50 -0000

hi Michael,

On your questions as to the PLUS charter:

> On 22 May 2016, at 19:30, Scharf, Michael (Nokia - DE) <michael.scharf@nokia.com> wrote:
> 
> Furthermore, I believe that this discussions matters for PLUS/SPUD, since:
> 
> ·         If two different, worked-out candidate users of the common substrate seem to have similar requirements for signaling information in clear-text, this could be some lessons learnt for what may be required in the common substrate.

This is a good point, and a reason for coordination between the PLUS and QUIC efforts (should WGs be chartered here).

> ·         Even if this is not the case, the current excessive use of the term “encryption” in the PLUS/SPUD charter IMHO has to be reviewed, since at least two potential candidate protocols actually seems to use information in clear text. Example: “The primary goal of PLUS is to enable the deployment of arbitrary, fully encrypted transport protocols”. Well, at least I learn now that not everything is “fully” encrypted…

This is imprecise language and should be cleaned up. The point is that everything above a PLUS shim layer is encrypted, and everything below open to the path. There should probably be something outlining the broad architecture here, which would make this more clear.

> ·         Finally, from the current charter I don’t understand whether PLUS/SPUD would consider the requirements of middleboxes designed to provide user anonymity (e.g., TOR-like). I’d personally be fine with flagging their specific requirements as out-of-scope. But for sure there is a user community of that sort of infrastructure and it may make sense to discuss early how to deal with that.

I *think* this is orthogonal -- I can't see what in PLUS would break TOR, or how stuff in PLUS could make TOR work better, without partially redesigning both... can you say more about what your concerns are here?

Cheers,

Brian