IETF Logo Mail Archive

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

Joseph Touch <touch@strayalpha.com> Mon, 06 April 2020 15:00 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 68B813A0995 for <tsvwg@ietfa.amsl.com>; Mon, 6 Apr 2020 08:00:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.318
X-Spam-Level:
X-Spam-Status: No, score=-1.318 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, HTML_MESSAGE=0.001, 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 gCW11lkloNlg for <tsvwg@ietfa.amsl.com>; Mon, 6 Apr 2020 08:00:25 -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 32E133A09A0 for <tsvwg@ietf.org>; Mon, 6 Apr 2020 08:00:11 -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=nj1X9jBj1kPKyBFAVH1y05hrJNV5n617dM1sIMEGZMY=; b=ZewptvrBdGpryBJNmB2UdLtxT 5rP7IPIb3EfQZ67VoPQIMJ1jVrq5ENd1sDkYnbYa0iStW3xqn0GK33DRq456dotMaaNC303XBiZtZ 4XH2vYOyKtTnTbg54hoxcJs3W+P5Mlp+UXMNIge/78Drc5VUFjj3d/pJp/PWJPVJWvf1D3UATgeBI AeqCQKe4LK1wA5hbr3Z7C6MkradEG8YnWy4A/DFdViz2QOKRPDxXcScQlKmVWjFEtnJvINnRbZqGt 1rctf5b3D83tcZJaabMa/T5PxTcq3YwHiD/s3BOvtiRw49dCMjjRtP6yAoE6jDeaNOEUWXk1U6WOt 9bryhxasg==;
Received: from cpe-172-250-225-198.socal.res.rr.com ([172.250.225.198]:52372 helo=[192.168.1.10]) by server217.web-hosting.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93) (envelope-from <touch@strayalpha.com>) id 1jLTEL-000ZDH-Ov; Mon, 06 Apr 2020 11:00:10 -0400
Content-Type: multipart/alternative; boundary="Apple-Mail=_150E63EC-7034-45B6-A54A-D484175729AF"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.5\))
From: Joseph Touch <touch@strayalpha.com>
In-Reply-To: <fc94ff59-4972-3960-7c25-85f8953463f9@erg.abdn.ac.uk>
Date: Mon, 06 Apr 2020 08:00:00 -0700
Cc: "Black, David" <David.Black@dell.com>, tsvwg <tsvwg@ietf.org>
Message-Id: <62B8E2A9-2347-44E2-8B14-DD3CD81937AB@strayalpha.com>
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>
To: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
X-Mailer: Apple Mail (2.3445.9.5)
X-OutGoing-Spam-Status: No, score=-0.5
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/yVfouhG8BNx8L6zEtl0BBR3lWcQ>
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: Mon, 06 Apr 2020 15:00:27 -0000

Notes below...

> On Apr 6, 2020, at 3:23 AM, Gorry Fairhurst <gorry@erg.abdn.ac.uk> wrote:
> On 05/04/2020 23:50, Joseph Touch wrote:
>> 
>> 
>>> On Apr 5, 2020, at 3:32 PM, Black, David <David.Black@dell.com <mailto:David.Black@dell.com>> wrote:
>>> 
>>> ...
>>> ...
>>> OLD
>>>    UDP-based protocols often do not use well-known port numbers.  
>>> NEW
>>>    UDP-based protocols often do not use well-known port numbers,
>>>    and use of a well-known port number is not limited to the
>>>    protocol for which the port is well known [RFC7605].
>> 
>> RFC7605 doesn’t say this, or at least most of this.
>> 
>> Yes, there’s no rule that well-known port numbers are used. But that’s not either unique to nor biased towards UDP vs TCP.
>> 
>> Joe
> I understand, I think we can mention RFC7605 in 3.1.1 by adding this to the para about ports to read something like:
> 
> "In some uses, an assigned transport port (e.g., low-numbered port)
> 
(e.g., 0..49151)

[I would avoid the term ‘low-numbered’, which could be interpreted as meaning 0–1023]

>  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 well-known port numbers. The use of a well-known port number is also not limited to the protocol for which the port is well known. 
> 
Well-known often implies System.

As per RF7605, I’d encourage the use of “assigned” for the entire range from 0..49151.

Joe

v2.23.0 | Report a Bug | By Email