Re: [tsvwg] 3GPP Liaison Statement clarifying port requests
Joe Touch <touch@strayalpha.com> Wed, 19 May 2021 23:48 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 D0A133A2422 for <tsvwg@ietfa.amsl.com>; Wed, 19 May 2021 16:48:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.087
X-Spam-Level:
X-Spam-Status: No, score=-2.087 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, MIME_QP_LONG_LINE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=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=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 ar1nlvJPjyGz for <tsvwg@ietfa.amsl.com>; Wed, 19 May 2021 16:47:56 -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 1AD383A243A for <tsvwg@ietf.org>; Wed, 19 May 2021 16:47:55 -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-Transfer-Encoding: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=ChDnTW8kyMUHM3dDJtLlp/vjxM7nYFISHsydA5hO/qY=; b=QX0nzDrHlxm/2HFSbxfLWv4aW9 adpBO7nPN+ZdNx6zp2ouhQr5mIJR1ygbIR+bO1Q5pTrERPmxRCwYWPBkCDXPsbssDWX24Wl6kWDDP nrsaNjv+eIiEEanCWzinHIN1zU8qlroR7vJe5fvbwOTFOhXQ0LHmz52Ix4MSQIbaO47XYNfpxO2S7 FNlxb69MxKvfdMWavtI7+bqHYS7RKe6pcuTxZJjeSC4rtJLECO2f+id3Wk0i+HQvD9ypgO2Mk3Ogf XbT14ASE0wl/RTa3Vwa5HyOBT4PcIFr4jlewC5pd161DjhlNbqamcq2VMB2esG7yUZAMmiBnYjrHN K+pUQ9Fw==;
Received: from cpe-172-250-225-198.socal.res.rr.com ([172.250.225.198]:56601 helo=smtpclient.apple) 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 1ljVuo-000JpN-4P; Wed, 19 May 2021 19:47:54 -0400
Content-Type: multipart/alternative; boundary="Apple-Mail-53FCF38D-9C75-4692-80AE-50A1FC24042E"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (1.0)
From: Joe Touch <touch@strayalpha.com>
In-Reply-To: <CAM4esxSQtnuoBZHXnR1q77eKhpUb5-aFhZP_mKeKgqf6KJ0MtQ@mail.gmail.com>
Date: Wed, 19 May 2021 16:47:49 -0700
Cc: Joseph Touch via IANA-Port-Experts <iana-port-experts@icann.org>, tsvwg <tsvwg@ietf.org>
Message-Id: <81D6A3DD-CA6C-4532-BA42-06230E3AB4BB@strayalpha.com>
References: <CAM4esxSQtnuoBZHXnR1q77eKhpUb5-aFhZP_mKeKgqf6KJ0MtQ@mail.gmail.com>
To: Martin Duke <martin.h.duke@gmail.com>
X-Mailer: iPhone Mail (18E212)
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/fLT2Ug1D_lQsdgIb2sVNryQJWKc>
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: Wed, 19 May 2021 23:48:03 -0000
Looks good to me. > On May 19, 2021, at 4:47 PM, Martin Duke <martin.h.duke@gmail.com> wrote: > > > OK, here's what I have: > > Thank you for your correspondence about port allocation. In your latest message you write: > > “However, besides the assignment of transport protocol port(s) that could be > requested by 3GPP for the deployment of specific service discovery > mechanism(s), 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.” > > Your understanding is correct. Our previous statements on this subject are intended to reduce port requests with a low chance of approval, but no party is ever prohibited from requesting a port assignment. A application justified by a particular use case will be evaluated in accordance with IETF and IANA policy, just like any other. > > *** > anything to add, or is that good enough? > >> On Tue, May 18, 2021 at 8:08 PM Joseph Touch <touch@strayalpha.com> wrote: >> Hi, Martin, >> >> The only response I can imagine would be: >> >> “Port assignments are assigned as per RFC6335 and RCC7605. No party is ever directly prohibited from applying for port assignments. Those terms are set by the IETF and IANA, and are updated by IETF consensus; they are not subject to negotiation.” >> >> I.e., although what they state is true, it is not true by some sort of agreement between the IETF and 3GPP. >> >> Joe >> >>> 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 >>> >>
- Re: [tsvwg] 3GPP Liaison Statement clarifying por… Joe Touch
- [tsvwg] 3GPP Liaison Statement clarifying port re… Martin Duke
- Re: [tsvwg] 3GPP Liaison Statement clarifying por… Joseph Touch
- Re: [tsvwg] 3GPP Liaison Statement clarifying por… Martin Duke
- Re: [tsvwg] 3GPP Liaison Statement clarifying por… Mirja Kuehlewind
- Re: [tsvwg] 3GPP Liaison Statement clarifying por… Spencer Dawkins at IETF
- Re: [tsvwg] 3GPP Liaison Statement clarifying por… Martin Duke
- Re: [tsvwg] 3GPP Liaison Statement clarifying por… Fred Baker
- Re: [tsvwg] 3GPP Liaison Statement clarifying por… Joseph Touch
- [tsvwg] Re : 3GPP Liaison Statement clarifying po… lionel.morand
- Re: [tsvwg] 3GPP Liaison Statement clarifying por… Martin Duke