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

Mirja Kuehlewind <mirja.kuehlewind@ericsson.com> Thu, 20 May 2021 09:04 UTC

Return-Path: <mirja.kuehlewind@ericsson.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 2AF4B3A02BE for <tsvwg@ietfa.amsl.com>; Thu, 20 May 2021 02:04:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.798
X-Spam-Level:
X-Spam-Status: No, score=-2.798 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.698, 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_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.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 qyb3uQ17X0iw for <tsvwg@ietfa.amsl.com>; Thu, 20 May 2021 02:04:45 -0700 (PDT)
Received: from EUR05-AM6-obe.outbound.protection.outlook.com (mail-am6eur05on2075.outbound.protection.outlook.com [40.107.22.75]) (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 AF6733A02C1 for <tsvwg@ietf.org>; Thu, 20 May 2021 02:04:44 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ln0rtnCZIXalX8wxE6ixIIH8foob4EOHFJrkbKZbnQnyWWWS3Eg9l7/vQE64pmnmKc1fVLiJOmELJzRCLtFqijgGU4xqKbCLzDfFB+onD0jgR7AcHTc6LGHHWW2eIjtcZ3PKJ/9xlCa8JWWiOBE5NQ8LMpRSK0nQAuHR8sWn2Sywl2K8bg6I3w4RmzAozlJHwoVV6LgULV1NasQtl+P53+2aCvyNS426uaTvgdVd8y9DubCSMOrh7uhlnL7Kl0ILlNF/eprzAhhzcpBZVM94QrslYLmZ7ZEPvINKel7jJBE2aMKUCGvuTI5bl4VE89uOLkReqBOboXUoxns38zC2vQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=CQFHyo02F2slbtbfE437ppc3FKp/fYFaxfEvCyJnyDE=; b=gA6vtQND/jCotH1CdY4NmFYl6k3AwkN8YnT3+g3t+7FywB/xYbGp9KKh5Z/h16zHQb5iL9KZR04fK1tF2avrPkEogYKWsX2Ir/sIZJQHK8AzuE7lu5s6O8az8IKTy1qXmuqX76gvXL5CpJAu6G9UekTgJMwdS1eeQkc19pcgZ8Qm70nLDCjY6LRUXHlE49ntLCghOtJvRJz2HyX1G0v+rUbd+yPT3/eVmEsyHxSSbFiyBtfBrVtJXyHqm5SHW+l3vN/mQ903ju12ifgPsxChvVGADn4KGFNaQHyWw/p7E0b9VuJaEwB49WVBM/wi6x7T9Z2q3ug4tJn2bNjCNzd5Cw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=CQFHyo02F2slbtbfE437ppc3FKp/fYFaxfEvCyJnyDE=; b=hgIPViXbIz90KqogNRuGu0vVYfvgguX6Xp00SLyqbK/1dGt/RMThnSBz/Ell8jzLbwAv4zaOklpHEqJdYecBUYuOIa9k6Mn1Fo/Q7lcd27rtXokKnHDYUDqHF5vtjMx0afde1JuWUq3sU5qJ5xSzRg3P1iZJEC7yR/IqT0d+ZGE=
Received: from AM0PR07MB3939.eurprd07.prod.outlook.com (2603:10a6:208:40::14) by AM0PR07MB6116.eurprd07.prod.outlook.com (2603:10a6:208:117::22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4150.11; Thu, 20 May 2021 09:04:41 +0000
Received: from AM0PR07MB3939.eurprd07.prod.outlook.com ([fe80::f5b3:5946:19c5:d8b8]) by AM0PR07MB3939.eurprd07.prod.outlook.com ([fe80::f5b3:5946:19c5:d8b8%6]) with mapi id 15.20.4129.023; Thu, 20 May 2021 09:04:41 +0000
From: Mirja Kuehlewind <mirja.kuehlewind@ericsson.com>
To: Martin Duke <martin.h.duke@gmail.com>, Joseph Touch <touch@strayalpha.com>
CC: Joseph Touch via IANA-Port-Experts <iana-port-experts@icann.org>, tsvwg <tsvwg@ietf.org>
Thread-Topic: [tsvwg] 3GPP Liaison Statement clarifying port requests
Thread-Index: AQHXTA5EB0i4U3pd4EaVxHcQwZ7vFKrqIEWAgAFZ/oCAAL19gA==
Date: Thu, 20 May 2021 09:04:41 +0000
Message-ID: <9A110E58-F531-4DCC-AFDB-0216EE706FB6@ericsson.com>
References: <CAM4esxRcxJ7HZSG2gk75+sA1PRWjkQqQT0F7+1EsG8gLOy__yA@mail.gmail.com> <4E4C4480-631E-4AA9-89F7-B173A57C0625@strayalpha.com> <CAM4esxSQtnuoBZHXnR1q77eKhpUb5-aFhZP_mKeKgqf6KJ0MtQ@mail.gmail.com>
In-Reply-To: <CAM4esxSQtnuoBZHXnR1q77eKhpUb5-aFhZP_mKeKgqf6KJ0MtQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.48.21041102
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=ericsson.com;
x-originating-ip: [2003:de:e707:b300:e9fd:a1ed:f10b:ff27]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: fb8cb0fd-5b2f-4384-9460-08d91b6e4df3
x-ms-traffictypediagnostic: AM0PR07MB6116:
x-microsoft-antispam-prvs: <AM0PR07MB611652D8B035D88AD6B13D70F42A9@AM0PR07MB6116.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:5797;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: vnNag30QkMj3s2Uehwz1L47KuzhIA1JuTtbZngKdlM1TzfJiDbMnZPimqQ6LhtIE/Is3awLNaVujyY7KzmzqgcjXqzyBjOQ5Apyftux3njNiHhAqEAICpxzC8u+Sz8LmL+BwWVYz0ljzHl3kbrGsTXiiqPSy/Cx+abK/qczuG2aipV4mRfY/AYduIDTiKpW8oC4M7DwPGhxyhtc7/rdL+JWyLhxJ6mWHLMUdcMy23yJvE/ZqxoaTcz8WOe/j2rrma9IEpIrC6InCMdWpasW/gjzyPSEhIDBkdf/ppg0tVvtD7wxRtqPfM7kD9UbU+W6sPx3s5OoMsIveOE3fFwzivj0coUUbY+heqSzDRDEFfvwN/A5vZWViOwYDVL7fQ+8q4veKf7nHwOPF4Y6poUEOIZxUrNIAwFQxyzMzjm9gvUztcnYAktLMVeV4cEy1O6KA6j8qxRYgvpmZVDvANujuJK8subvtkUdIV5Iki1r4PpiJj7G7ecLgrb9G+nLRcy+32YaMsyXcHwjm9P5wKqxpLDS38fJ/MoG9ENr8tE2LVJRODXmc55jr8Lwo8AEv2ohwMob9NqDiyT7HZjQsL/nyngDlHKjOkhiKcnwdvK4KaSxSh5vrVXsm+2t5LRNgbTuzdD3UBHjLltKw15ZYs6WUuS0ZsVfmJPm8ax6dpWu4fksmnbbaz+yYs1sJ7o11W9311ojzUAfUM4U/d6x3Z/nE17BnliIrAq8rFth4lQf2AmD5ZfSBeWs/OhfZLoOZ3t+vn+4kjK9uPlnzJSOQDaDOtQ==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:AM0PR07MB3939.eurprd07.prod.outlook.com; PTR:; CAT:NONE; SFS:(4636009)(39860400002)(396003)(366004)(346002)(136003)(376002)(6506007)(122000001)(5660300002)(6486002)(54906003)(66556008)(66446008)(66476007)(64756008)(53546011)(36756003)(71200400001)(110136005)(38100700002)(76116006)(66946007)(316002)(66574015)(91956017)(8936002)(166002)(6512007)(2616005)(4326008)(186003)(86362001)(33656002)(8676002)(44832011)(83380400001)(2906002)(478600001)(966005)(45980500001); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata: 2PLgyZKrrWrNGoF7yvClG2eQFlJfeu9rEDalH0WfOcgl6jm07rLRENljN7bzJUq6RyIQOP+LDjv+f+BL6WQ3C43B5a5KZ1JKUvU8RuYdJ3e1Y7lHOuw/5SsB99aW9sdTFdECojeYzXnpXBz6M8YOlMO0ALgAKnqn/tvgtbxQ+rr8irBQPqrKyDK1R21IN7ZepC5fFvG9XFTCIGzhfJHiGFn7Z2saNQ14NZ1iaku7p+cqbjP+NW99d2VXJxF88LULOMA2gY4OUqrl2xnlCU5e684XvxWW1iqjUfnS/xzrPilFrF706WNOhvTmoV/bybmj7q4JQ3lYriUc6vobM4/YNlWgSX+IE+zWKKXnXjKxci3B5Cx3An5ZxtVmTB+yXrZVYpsnObM/PLqZyzcZiiOLcEAsaiaRCdP6qTYjR4uUdSqyhu4R4OguDAx8seAAxFPf/b1rAj5ot37QNfyks1p5qPpPSmeQPSClgJXw07XpwZiUj0jbz2r0Zuvg6tRc5v6FEA/hrchLUVYH9dvjwOuj3g6bHGf4pXO+eO2CZ2WVzBLLa2fT2LvTbrBZ4f/pkUo8anJIIzTz06EKekDSqagKapfhMZtm5GWsXbSQ8ZveazY27BDri0nSqCS0Lg4qzZardji0Hqq/T9nYzNrVVdERHaban1DEPz8Hm5yaT8Q+zGX1XCTZj6UFUJoEqvkR3kBBGtEDxHwt/V9MAK2G9dKRsU91sgAKH1L9pKqtaSz2+w9pB6LHkhh6cPNGk1HDqZZ9wbJ7oJr2HQJ4zkBX2ogMLXDuLnHRQi9RIEbsSpiMYE7Jq0EjMBuE9dd9Cxc0w3objfh9fZlGJx/zLZO7/7f3iydscVw4hjemtQe2qU6Ck8s6ZHhrj/dWKEdnbhFOpl3h3t9zNmKLhGxY74LurHGGBJmEGIsjkPxesso1NozjjsZQgnd4Lf3R0mTdxYhNR0AGpvWrH+cIzJN6VPE+8sYiqpi6aVyTdvUyQXq6VjPsoTj4yLQSqnpB/l7TJdeb3eNWp3iBx/92lEUCgaHdI3QD8yISBwA/+WaZ/eEebWjI5V9xn6t5Zy7lOqTm0GKHQaGhkU19JPN/ZsHMErn4gsLqh/kHZfuRndBUUJy9dzm32L2YedKUxm/TRMFXU+NY134K8SiB04//vOs782BSnBhBJqO0R9AJ0eFS1Bgr4syEq57aIfahzk2C+iXOY4AL3BdC6lFgUvPEBQCD9+Wi895bb4eeBJTzb4mQRJchQK5fh9UvApcV+GwoPYaBR0AYaE8/dn8Q8kUubissqrcQzA0EWU2NCNa+hL2gCisPfbBMvoHnbS7PZR8Stu7mQINbY6qd4iQJMZfssYVz0Tw5jRO7SmhVzVjQqnnKmodEki4+w0QdazO38oEZ3OWczaXEXwEL
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_9A110E58F5314DCCAFDB0216EE706FB6ericssoncom_"
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: AM0PR07MB3939.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: fb8cb0fd-5b2f-4384-9460-08d91b6e4df3
X-MS-Exchange-CrossTenant-originalarrivaltime: 20 May 2021 09:04:41.6408 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: XCzP2FiqKt+eTRvLfMM+fYnLeX8UoWLeXVI9H0hmcaRTeKl0VytlOgfYWE9s7Qgo3viEI48ccBOgdV+go+6iKDwCWB7XFhvNEcEWm7MRqHs=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM0PR07MB6116
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/qRRKsS4WZhQs9iGwcNDLxR99rPI>
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 09:04:50 -0000

Hi Martin,

this generally looks good to me and keeping it short is probably the right approach. I believe one of their meta-concern is still that it is maybe not fully clear to them when they should ask for a port. Also I think if they specify any new services that could be used internet-wide, we actually want them to come to us.

Maybe a tiny little tweak could help:

OLD

A application justified by a particular use case will be evaluated in accordance with IETF and IANA policy, just like any other.

NEW

A application justified by a particular use case, especially if that use case is deployed over the open Internet, should be registered with IANA and will be evaluated in accordance with IETF and IANA policy, just like any other request.

Not sure if that is too much or helps at all but wanted to propose it for your consideration.

Mirja


From: tsvwg <tsvwg-bounces@ietf.org> on behalf of Martin Duke <martin.h.duke@gmail.com>
Date: Thursday, 20. May 2021 at 01:47
To: Joseph Touch <touch@strayalpha.com>
Cc: Joseph Touch via IANA-Port-Experts <iana-port-experts@icann.org>, tsvwg <tsvwg@ietf.org>
Subject: Re: [tsvwg] 3GPP Liaison Statement clarifying port requests

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<mailto: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<mailto: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