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

Gorry Fairhurst <gorry@erg.abdn.ac.uk> Tue, 24 March 2020 07:42 UTC

Return-Path: <gorry@erg.abdn.ac.uk>
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 9A3AC3A1083 for <tsvwg@ietfa.amsl.com>; Tue, 24 Mar 2020 00:42:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=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 fA4prPd-9eAd for <tsvwg@ietfa.amsl.com>; Tue, 24 Mar 2020 00:42:37 -0700 (PDT)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [IPv6:2001:630:42:150::2]) by ietfa.amsl.com (Postfix) with ESMTP id 9C3653A0843 for <tsvwg@ietf.org>; Tue, 24 Mar 2020 00:42:37 -0700 (PDT)
Received: from GF-MacBook-Pro.local (fgrpf.plus.com [212.159.18.54]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id 833B21B00227; Tue, 24 Mar 2020 07:42:30 +0000 (GMT)
To: Joseph Touch <touch@strayalpha.com>, Tom Herbert <tom@herbertland.com>
Cc: tsvwg <tsvwg@ietf.org>
References: <CALx6S349SE2Ho0V2bJPSE7dh3+2f5Wiw1AofMke0RY4FwF=ebw@mail.gmail.com> <679FAA73-401E-499D-87CB-10F973E05DD6@strayalpha.com> <MN2PR19MB40455E00DB52880A38EB494C83F00@MN2PR19MB4045.namprd19.prod.outlook.com> <4FA8060E-C661-42FB-BCA1-43F32E5FA1F5@strayalpha.com> <MN2PR19MB40458C69C9C91C70AD889D3A83F10@MN2PR19MB4045.namprd19.prod.outlook.com> <CALx6S35J8K0bAmPp72svv+BuOKc1ZdrK_odfcJsPujmQz-iyyA@mail.gmail.com> <F652A257-88C7-4400-A119-8180200F0C3C@strayalpha.com>
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Message-ID: <9a4948ea-1fac-1db2-c969-b828734a9c68@erg.abdn.ac.uk>
Date: Tue, 24 Mar 2020 07:42:29 +0000
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:68.0) Gecko/20100101 Thunderbird/68.6.0
MIME-Version: 1.0
In-Reply-To: <F652A257-88C7-4400-A119-8180200F0C3C@strayalpha.com>
Content-Type: multipart/alternative; boundary="------------5DD28CEF8DDD16ED7D7A74DD"
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/PAu1WkxCwdcLuLU-eGnyFapQAPs>
Subject: Re: [tsvwg] Comment on draft-ietf-tsvwg-transport-encrypt-13
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: Tue, 24 Mar 2020 07:42:40 -0000

On 24/03/2020 03:49, Joseph Touch wrote:
> +1
>
>> On Mar 23, 2020, at 8:21 PM, Tom Herbert <tom@herbertland.com 
>> <mailto:tom@herbertland.com>> wrote:
>>
>>> NEW
>>>
>>>   o  On the one hand, protocols do not necessarily have an incentive to
>>>
>>>      expose information that is used by the protocol.  The incentive
>>>
>>>      to expose transport header information has to be considered when
>>>
>>>      proposing a method to do so.
>>>
>> David,
>>
>> That's changing the meaning of the text. The original text was making
>> a point that if transport layer information is exposed there needs to
>> be an incentive for the host to set the information honestly and
>> correctly. This is true, not just for transport layer information but
>> for everything the host tells the network. An obvious example is TOS
>> in IPv4-- left to their own devices everyone would just request the
>> highest level of service of traffic for all packets. So we need some
>> tangible incentive for user to be honest and correct. For instance,
>> TOS might have worked if the user were explicitly charged for the
>> higher level of service, but that would imply a contract between the
>> network and the host is established and a whole bunch of mechanisms
>> that require far more than just anonymously volunteering some
>> arbitrary amount of transport layer information.
>>
>> Tom

+1

Gorry