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

lionel.morand@orange.com Thu, 20 May 2021 19:41 UTC

Return-Path: <lionel.morand@orange.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 9A4553A2363 for <tsvwg@ietfa.amsl.com>; Thu, 20 May 2021 12:41:22 -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, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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=orange.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 reE9O-PFvqba for <tsvwg@ietfa.amsl.com>; Thu, 20 May 2021 12:41:17 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.70.36]) (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 900413A235D for <tsvwg@ietf.org>; Thu, 20 May 2021 12:41:17 -0700 (PDT)
Received: from opfednr00.francetelecom.fr (unknown [xx.xx.xx.64]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by opfednr25.francetelecom.fr (ESMTP service) with ESMTPS id 4FmKqF6VSLzCsX6; Thu, 20 May 2021 21:41:13 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1621539673; bh=/C1+E19Cj49vKgyq+KWHFPD0tovBadEIyNJX6fQSvIQ=; h=From:To:Subject:Date:Message-ID:Content-Type:MIME-Version; b=hBtwaXhdoeLosoqZk0sK2JCmGXJo6LiKqyKxZ6JC1WgVMkD0X1G2JOecxmisDpjKb gM5l256tik/nQuD+/OL8T/oQf13zxDg8FHwWeB+f6Sik6QPXdn/knVlAFEbrBaCVCn bibrrqK5nIWM47BS5kk0vqBbKEjjlXrSluI6l3k5JO8ZZE89TQHl9VFB4y7j6WXI+T kvbaP7VEkb5hze8/U/L2FVFRCGerGrAgw/0lirwdQjHpd+w9DwRjFxnYmrAhA1dHuc 2wsCebgW5INVJRoPd2Bay2sewvRL2SvUodxqDbDhBCXx21yRDvyjdeLLw4IfhIWjtq tTKzCODS/kYOw==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by opfednr00.francetelecom.fr (ESMTP service) with ESMTPS id 4FmKqF5hJBzDq7Y; Thu, 20 May 2021 21:41:13 +0200 (CEST)
From: lionel.morand@orange.com
To: Joseph Touch <touch@strayalpha.com>, Fred Baker <fredbaker.ietf@gmail.com>
CC: "iana-port-experts@icann.org" <iana-port-experts@icann.org>, tsvwg <tsvwg@ietf.org>
Thread-Topic: Re : [tsvwg] 3GPP Liaison Statement clarifying port requests
Thread-Index: AQHXTA5BU9koRxhQ3029dResys9qMQ==
Date: Thu, 20 May 2021 19:41:12 +0000
Message-ID: <1907_1621539673_60A6BB59_1907_248_1_85b8gh8rvs1j2vuvec20c7gr-pqgo202d9ey0yk725hum4wlw-8rgtm1mqnqh29ios2nrayhlq-vu9jjbn3u0px6qgf5d-sgqcz2j846vl1zpm5b-f2ep5eqwn1nd-notxi9-928iao36s9pn-7e6sdo.1621539669749@email.android.com>
References: <CAM4esxRcxJ7HZSG2gk75+sA1PRWjkQqQT0F7+1EsG8gLOy__yA@mail.gmail.com> <97D6795B-6654-4E88-AD69-5D06DF2FE5F7@gmail.com> <9E4D0013-A356-44C0-990B-7F40506F2B34@strayalpha.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: multipart/alternative; boundary="_000_85b8gh8rvs1j2vuvec20c7grpqgo202d9ey0yk725hum4wlw8rgtm1m_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/0tbUdV0RtQZEa6Bk8hSoTjyRdO8>
Subject: [tsvwg] Re : 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 19:41:23 -0000

Hi,

To Fred:

When a port is requested by 3GPP, the solution requiring the new port is described in a 3GPP normative specification, document accepted by the IANA policy. Obviously, if the proposed solution is of general interest for Internet, an RFC publication will be requested.
And it is clear that it is not requested to be able to bypass the IANA policy regarding port number allocation nor to be automatic blessing for any request (as indicated in the liaison). I admit that it was not so clear in the past for some 3GPP folks.

To Martin:

The current proposed answer is fine for me. It is the level of feedback requested by 3GPP.

I don't know when the final version will be available but it would be great if an official LS reply could be received on Tuesday next week at the latest. The 3GPP CT4 working group is currently in virtual meeting.

Regards,

Lionel


-------- Message original --------
De : Joseph Touch <touch@strayalpha.com>
Date : jeu. 20 mai 2021 à 20:11
À : Fred Baker <fredbaker.ietf@gmail.com>
Cc : iana-port-experts@icann.org, tsvwg <tsvwg@ietf.org>
Objet : Re: [tsvwg] 3GPP Liaison Statement clarifying port requests
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
>>
>>
>>
>


_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.