IETF Logo Mail Archive

Re: [tsvwg] 3GPP Liaison Statement clarifying port requests

Joseph Touch <touch@strayalpha.com> Thu, 20 May 2021 18:10 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 35C033A211B for <tsvwg@ietfa.amsl.com>; Thu, 20 May 2021 11:10:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 TzIa8-cTyIVt for <tsvwg@ietfa.amsl.com>; Thu, 20 May 2021 11:10:31 -0700 (PDT)
Received: from server217-5.web-hosting.com (server217-5.web-hosting.com [198.54.116.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 6831F3A212C for <tsvwg@ietf.org>; Thu, 20 May 2021 11:10:31 -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: 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=TUZ+q7LKfh8mYL+1xdHXrR3uSaUKznpuzj+x1sKDkuQ=; b=otXzYlwcUycTCxfJAD1A5l0YL+ iOg4o3O5YRWV4g+NGBUytl9Wfz1j7vjPo9tkJ3qcce1LsJb/zDpQkwAEf5H9bPUnDNuxus8wFOtkB QF5x7XSuKA7/FneDsdhW5tyMHaMthxm/zm/afSX2EYhrTHTkup7p8O6Wx1IYGR9VD7ecrWoguOP/0 mmJQS0uoezKn9ekk7d42EgtYyRHKg3Ml8R4qQqskPZukC1ebJZ11yJo9x8OFsNhDOxy84tL8rUpop EK0inYW0/2PyGqewtj7dBjFqgC5f/JU30xusYZdjWPKMNosJv5hIoMO2kNNQS3uYx8eCEQJVdpIou J12a+jOA==;
Received: from cpe-172-250-225-198.socal.res.rr.com ([172.250.225.198]:49154 helo=[192.168.1.14]) by server217.web-hosting.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <touch@strayalpha.com>) id 1ljn7n-0029lR-Ra; Thu, 20 May 2021 14:10:30 -0400
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\))
From: Joseph Touch <touch@strayalpha.com>
In-Reply-To: <97D6795B-6654-4E88-AD69-5D06DF2FE5F7@gmail.com>
Date: Thu, 20 May 2021 11:10:22 -0700
Cc: Martin Duke <martin.h.duke@gmail.com>, iana-port-experts@icann.org, tsvwg <tsvwg@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <9E4D0013-A356-44C0-990B-7F40506F2B34@strayalpha.com>
References: <CAM4esxRcxJ7HZSG2gk75+sA1PRWjkQqQT0F7+1EsG8gLOy__yA@mail.gmail.com> <97D6795B-6654-4E88-AD69-5D06DF2FE5F7@gmail.com>
To: Fred Baker <fredbaker.ietf@gmail.com>
X-Mailer: Apple Mail (2.3654.60.0.2.21)
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/WDKQfMNB_zVGiDbOPQMgw4KyVk0>
Subject: Re: [tsvwg] 3GPP Liaison Statement clarifying port requests
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: Thu, 20 May 2021 18:10:47 -0000

Hi, Fred,

Although any sort of description is useful, we don’t require drafts for port assignments.

They used to be required for system ports (actually, they need to be standards-track), but we deprecate assigning those ports anyway now.

Joe

> On May 20, 2021, at 10:43 AM, Fred Baker <fredbaker.ietf@gmail.com> wrote:
> 
> From my perspective, 3GPP is forever and always empowered to ask, as is anyone else. However, there is no mandate requiring IANA to respond positively to the request. I would hope that they would file an internet draft proposing the new port assignment and arguing for it.
> 
>> On May 18, 2021, at 10:48 AM, Martin Duke <martin.h.duke@gmail.com> wrote:
>> 
>> Hello TSVWG and port experts,
>> 
>> We got this 3GPP Liaison Statement last month:
>> https://datatracker.ietf.org/liaison/1726/
>> 
>> The key paragraphs are:
>> 3GPP understands that it could be possible to assign to 3GPP a port per
>> transport protocol (UDP, TCP, SCTP, DCCP) that will be used for service port
>> negotiation/discovery for all the future internal interfaces defined by 3GPP,
>> avoiding the need for a systematic IANA port assignment for interfaces used
>> only inside the 3GPP system...
>> 
>> 
>> ...it is also the 3GPP understanding that this statement cannot
>> prohibit 3GPP to request in the future a port assignment for a new service
>> application for which none of the port assignment alternatives would be
>> applicable.
>> 
>> 
>> They would like confirmation, IIUC, that they are not cut off from any further port assignments.
>> Any feedback on what I should tell them in response?
>> Your friendly AD,
>> Martin
>> 
>> 
>> 
>

v2.23.0 | Report a Bug | By Email