Re: [tsvwg] Comments on draft-ietf-tsvwg-transport-encrypt-14

Gorry Fairhurst <gorry@erg.abdn.ac.uk> Tue, 07 April 2020 06:51 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 7A4AF3A17A2 for <tsvwg@ietfa.amsl.com>; Mon, 6 Apr 2020 23:51:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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 gmwuywbAdob1 for <tsvwg@ietfa.amsl.com>; Mon, 6 Apr 2020 23:51:50 -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 BD6BE3A17A4 for <tsvwg@ietf.org>; Mon, 6 Apr 2020 23:51:49 -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 3C59A1B0022B; Tue, 7 Apr 2020 07:51:44 +0100 (BST)
To: Joseph Touch <touch@strayalpha.com>
Cc: tsvwg <tsvwg@ietf.org>
References: <CALx6S345Ta5LjSkZ+XmNmH8dxKnM++VRCej2iGxfdUqDc+M-Jw@mail.gmail.com> <MN2PR19MB4045652C80DB5348A5A3505F83C70@MN2PR19MB4045.namprd19.prod.outlook.com> <CALx6S36yzDTLaxUhWibZjmK5Cxu2zfzxiawFRCbVn9aPF4rs1A@mail.gmail.com> <MN2PR19MB4045E873D0908044343F8C2283C40@MN2PR19MB4045.namprd19.prod.outlook.com> <42914e6a-5602-7911-7447-e400d36eb0e6@erg.abdn.ac.uk> <MN2PR19MB404585DB4796DD1EF29FDF0C83C50@MN2PR19MB4045.namprd19.prod.outlook.com> <6CC67993-37FF-4B02-A45A-4F30E9D6686C@strayalpha.com> <fc94ff59-4972-3960-7c25-85f8953463f9@erg.abdn.ac.uk> <62B8E2A9-2347-44E2-8B14-DD3CD81937AB@strayalpha.com> <737cf948-065b-0702-ca15-6cc216d73bc9@erg.abdn.ac.uk> <10E067D5-0C17-400B-BA7F-3CB49C2C94B6@strayalpha.com>
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Message-ID: <864fd833-6b77-a6c1-f60c-0768357ed911@erg.abdn.ac.uk>
Date: Tue, 7 Apr 2020 07:51:43 +0100
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: <10E067D5-0C17-400B-BA7F-3CB49C2C94B6@strayalpha.com>
Content-Type: multipart/alternative; boundary="------------3DE2CD95B4C56F83F2F2FB1F"
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/fDVHurpqSX62vgws8_K5Y6dBMyE>
Subject: Re: [tsvwg] Comments on draft-ietf-tsvwg-transport-encrypt-14
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, 07 Apr 2020 06:51:51 -0000

On 07/04/2020 02:42, Joseph Touch wrote:
> Hi, Gorry,
>
> I’d suggest as follows (just to follow through on the changes):
>
>
>     In some uses, an assigned transport port (e.g., 0..49151)
>     can identify the protocol [RFC7605]. However, port
>     information alone is not sufficient to guarantee identification.
>     Applications can use arbitrary ports and do not need to use
>     assigned port numbers. The use of an assigned port number is also
>     not limited to the protocol for which the port is intended.
>
>
> Joe

That also works for me, thank you for this replacement text, we have 
used this for rev -15.

Gorry