IETF Logo Mail Archive

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

Tom Herbert <tom@herbertland.com> Tue, 07 April 2020 14:40 UTC

Return-Path: <tom@herbertland.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 0C62C3A0B1B for <tsvwg@ietfa.amsl.com>; Tue, 7 Apr 2020 07:40:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.888
X-Spam-Level:
X-Spam-Status: No, score=-1.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_NONE=0.001, T_SPF_HELO_TEMPERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=herbertland-com.20150623.gappssmtp.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 S0twJzbvI8CG for <tsvwg@ietfa.amsl.com>; Tue, 7 Apr 2020 07:40:27 -0700 (PDT)
Received: from mail-ed1-x52c.google.com (mail-ed1-x52c.google.com [IPv6:2a00:1450:4864:20::52c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B06443A0A4F for <tsvwg@ietf.org>; Tue, 7 Apr 2020 07:40:26 -0700 (PDT)
Received: by mail-ed1-x52c.google.com with SMTP id de14so4351657edb.4 for <tsvwg@ietf.org>; Tue, 07 Apr 2020 07:40:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herbertland-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=SuamoCsAWqqbpo0sBghhfgyzXblk/Tz7IFpMu8Eivxs=; b=e7abr8FKSuCGEbpUGutg8dKKEw9bO4I9toP+GwwuBRiqt9ofpNNid0BIlY/CJtw31+ 7BUrMLanefsN8yuLM9kHXDBYSW48Zc0mOu43jBeTFh5ZioyKoas0sNUX6+ObiAPFLKwq 7CQhy8RO/o4WZxcS0SY4RJi0cf6k34Vp4nx7sbwiCuNGidIhvFfCQrLcrdSMXbZNWP8V mmL+zZeij9VAYzYgso5O/WRkQeDsyBHgZqvS0RZp+yALW9/1XRkd6PG6bDCuY6S4Uxdj V0HJPOl1ufH4KzmY6Y2gcRtfz+f/S4TxMIqleBonAgX2pDI2gvNdSDpvqdYo1fGFBkJH Sb7Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=SuamoCsAWqqbpo0sBghhfgyzXblk/Tz7IFpMu8Eivxs=; b=YT71irvkBX1Ie+S4iRUe2Ty1noEYSRpoLtE7sTidIfM58Qsu2Umfq4E+RZX6hKDdwv eA3CBigQlgbL0GEykMWzEJUApII/RuVdq7HA93WLsuw0HLEmkTluH4qenj15fwvYOjol +MJdT5HpXTamUup8gql0djMMIu+SMe3UTpn9vpnM7hzoZ8weJpe+/F+92LO1NRhU2Ie0 rT3JlgARI92eYudqaoYfQ2suDeuUf0bC196Y7ZjNHDZ9uVi3YYtOeb55JNyJcczw9KMP TruelVMZ0AR85CWkKF2ppXQGYbDM8Haab7I8mVZbLa06UteGM+21A2Fg7ME4aqTJ1lhQ 6XUg==
X-Gm-Message-State: AGi0Pubd1jWQiUIjnPI9IZMC1/Zuv4Ez/VQO2nGnglerPKrmvQwVEC8E /NEVWWa8WzEESmIZRsAfnD9v/rt5YNq+6fJJzj9okyY0FlM=
X-Google-Smtp-Source: APiQypKxmhx+CG3579L8o2CjUsrsJFftp8uCJ48nYuGPQkek2S8TwiB5yKokIs2k73SpnWpivLPsF6cUE8pf8e88Hq4=
X-Received: by 2002:a05:6402:17c6:: with SMTP id s6mr2253043edy.212.1586270424759; Tue, 07 Apr 2020 07:40:24 -0700 (PDT)
MIME-Version: 1.0
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>
In-Reply-To: <10E067D5-0C17-400B-BA7F-3CB49C2C94B6@strayalpha.com>
From: Tom Herbert <tom@herbertland.com>
Date: Tue, 07 Apr 2020 07:40:14 -0700
Message-ID: <CALx6S36_HGekVYSBTiP-=uDigk+nzf2Yw2AtqopPrK5Y1gozgQ@mail.gmail.com>
To: Joseph Touch <touch@strayalpha.com>
Cc: Gorry Fairhurst <gorry@erg.abdn.ac.uk>, tsvwg <tsvwg@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/8tbsswSW1UlXim6dWYyyyTrMwNU>
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 14:40:31 -0000

On Mon, Apr 6, 2020 at 6:42 PM Joseph Touch <touch@strayalpha.com> 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,

RFC7605 acknowledges that port numbers are used to identify the
application protocol, but clearly doesn't condone the practice. I
suggest the text should just paraphrase RFC7605:

"Port numbers are sometimes used by intermediate devices on a network
path to interpret transport protocol payload, however any
interpretation of port numbers -- except at the endpoints -- may be
incorrect, because port numbers are
meaningful only at the endpoints [RFC7605]."

Tom

>
>
> Joe

v2.23.0 | Report a Bug | By Email