IETF Logo Mail Archive

Re: [tsvwg] Comment on draft-ietf-tsvwg-transport-encrypt

Joseph Touch <touch@strayalpha.com> Sat, 29 February 2020 02:03 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 02ED83A0975 for <tsvwg@ietfa.amsl.com>; Fri, 28 Feb 2020 18:03:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.319
X-Spam-Level:
X-Spam-Status: No, score=-1.319 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] 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 1lg_tLkjCbsx for <tsvwg@ietfa.amsl.com>; Fri, 28 Feb 2020 18:03:53 -0800 (PST)
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 CCB7E3A0925 for <tsvwg@ietf.org>; Fri, 28 Feb 2020 18:03:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; s=default; h=To:References:Message-Id: Content-Transfer-Encoding:Cc:Date:In-Reply-To:From:Subject:Mime-Version: Content-Type:Sender:Reply-To: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=/YRWW7Tr2rtbBnzsQHQpzrf0IVzVwMj7OM3zBsWrDGw=; b=ZOlnZU5dJC7nbNevmX2PkYHqM IpJnB9Q5+ud/GBGPJbNgJg6NTu3I747pCA92jshTmkx5SWhOWDZKPeILslKG8eiw8IV7li2QXdv09 B17wxJCPvKzUbdWMYBV1EyFa51MSsdZogJfrZAjOaSyDIsj1AQXNwq5851rTbQERgnrPDqLWHT5sL 48KvO2qb46EyHz/ybdFnctMxDdvuVKcDaj79nFIyJCaZ8/fgN6fTcWGO0juvfDwGlJGkusYeb8G0J d5lZMP5CxSZbyA00P6NDtb6BEvlGy4mzblvpRaNlFuBXr9Jy7Pjs7N5WW8NIDI7fXLOmStkbTbWw7 tu13+O8ug==;
Received: from cpe-172-250-225-198.socal.res.rr.com ([172.250.225.198]:59521 helo=[192.168.1.10]) by server217.web-hosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92) (envelope-from <touch@strayalpha.com>) id 1j7rTo-000xpx-LY; Fri, 28 Feb 2020 21:03:52 -0500
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Joseph Touch <touch@strayalpha.com>
In-Reply-To: <CALx6S37iBDc7KxOL60=HC_QkWH06-5MU2rqrK=w+mqiKkSdc0w@mail.gmail.com>
Date: Fri, 28 Feb 2020 18:03:47 -0800
Cc: tsvwg <tsvwg@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <5C993764-1D9A-4B04-A217-2B444008EBE2@strayalpha.com>
References: <CALx6S37iBDc7KxOL60=HC_QkWH06-5MU2rqrK=w+mqiKkSdc0w@mail.gmail.com>
To: Tom Herbert <tom@herbertland.com>
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/3IPpDdXTHTAsYfBX6dmRDp0uzq8>
Subject: Re: [tsvwg] Comment on draft-ietf-tsvwg-transport-encrypt
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: Sat, 29 Feb 2020 02:03:59 -0000

On Feb 28, 2020, at 12:30 PM, Tom Herbert <tom@herbertland.com> wrote:
> 
> While the draft certainly has improved both in tone and content, I
> still feel like there is one area that is very under-represented.
> Namely the possibility of using extension headers to carry necessary
> transport information that the network needs. I have brought this up
> several times, and don't believe it has been adequately addressed.

Tom, 

I thought the draft explains (IMO correctly) that the transport layer can make info available to the network layer, but that’s how it works. We shouldn’t expect that the transport header itself is available (for security and privacy reasons).

Joe

v2.23.0 | Report a Bug | By Email