Re: [tsvwg] 3GPP Liaison Statement clarifying port requests
Martin Duke <martin.h.duke@gmail.com> Thu, 20 May 2021 20:50 UTC
Return-Path: <martin.h.duke@gmail.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 706933A2561 for <tsvwg@ietfa.amsl.com>; Thu, 20 May 2021 13:50:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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=gmail.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 xIkmN5K4fHlb for <tsvwg@ietfa.amsl.com>; Thu, 20 May 2021 13:50:14 -0700 (PDT)
Received: from mail-io1-xd2f.google.com (mail-io1-xd2f.google.com [IPv6:2607:f8b0:4864:20::d2f]) (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 4363E3A255D for <tsvwg@ietf.org>; Thu, 20 May 2021 13:50:14 -0700 (PDT)
Received: by mail-io1-xd2f.google.com with SMTP id a8so9892035ioa.12 for <tsvwg@ietf.org>; Thu, 20 May 2021 13:50:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=CiiCPCKMciz/O8Q7ToW0PNxSIJyK/IeakUuLCJQ0Iv8=; b=fFSGk8z6ui/cq0xvKTJUrSGIpRG/gE822CV6W2jaGpjUYhD2OX+SwYmrqYQwk3KRLP 49YOg8tghk0F92p6RyLZL9qfzePXWFKHlf+Ukv/p9wi76RiRHlbo3yYbfvDEvMqRdMeY DSIqlvRxZlj/Cr12xFSDpMmgi/ZcVHduJ3TceSTGMwh3qOygA0Jp3S3fXRJkgjKvhbXR r+Ri7olTftJl/RUsEq5lcjVs+QgtnzEKQzwD9vUh8k4t6mDVEC+ujSiV4qdA/cGbDtCj 8or59RJZCq/qxGzC+3ZYVDSOJRkeey9B8JB5UrZeKZXAClwLJ0c+stqiWrGUuwVMnek1 6VFA==
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; bh=CiiCPCKMciz/O8Q7ToW0PNxSIJyK/IeakUuLCJQ0Iv8=; b=fgFztCrTwINzk+5J5h8a3/UHuk3XItVIpydZiHlKA5OLTUijdnQ+vE7DzO0FqRftPk r90Zt6jIJEPUHM6V/W9gonjLFVk08vTxNtpJWN4k4P5hN/B6o6gO7I1OAnJNyKHLp5MZ 9e+mDRb+NGsA8j66DtHaraXzsrK82ai5Z0U6En7nFS2EH4ULsvJOwl9N1dxVqMxhMZ+N 0NhdaWLR9qUuefrXgXoMY5UPX4MYKBncKPBhPxVBIFbb+D2xUMWChq5Z6N2OsaSrqt8c SFFI5fjfaQJyAwg/sxkLIcCUy8sNdmHK3vHuSZJj7Ae6ziYuUX/1g8TQqQ0bmio9RwAP 2GJQ==
X-Gm-Message-State: AOAM5326Y8TMpgRO/3lj3ZlcQnBJa+yuH2zFEbu6AbgdHySFZL2vZzRf bbmNH/+8ZVvFZdLU17m52ErAmsGO6eWBEZ3l1Xw=
X-Google-Smtp-Source: ABdhPJy/QYmtcticzrlt7uKdC6IUfaO9l3ktLwc8ZVNnon7+CSZGmHVHQ8IFcKOI4E5+A9Z5uYUYSRuW595KbpkRVOM=
X-Received: by 2002:a02:5289:: with SMTP id d131mr8561999jab.121.1621543811899; Thu, 20 May 2021 13:50:11 -0700 (PDT)
MIME-Version: 1.0
References: <CAM4esxRcxJ7HZSG2gk75+sA1PRWjkQqQT0F7+1EsG8gLOy__yA@mail.gmail.com> <97D6795B-6654-4E88-AD69-5D06DF2FE5F7@gmail.com> <9E4D0013-A356-44C0-990B-7F40506F2B34@strayalpha.com> <1907_1621539673_60A6BB59_1907_248_1_85b8gh8rvs1j2vuvec20c7gr-pqgo202d9ey0yk725hum4wlw-8rgtm1mqnqh29ios2nrayhlq-vu9jjbn3u0px6qgf5d-sgqcz2j846vl1zpm5b-f2ep5eqwn1nd-notxi9-928iao36s9pn-7e6sdo.1621539669749@email.android.com>
In-Reply-To: <1907_1621539673_60A6BB59_1907_248_1_85b8gh8rvs1j2vuvec20c7gr-pqgo202d9ey0yk725hum4wlw-8rgtm1mqnqh29ios2nrayhlq-vu9jjbn3u0px6qgf5d-sgqcz2j846vl1zpm5b-f2ep5eqwn1nd-notxi9-928iao36s9pn-7e6sdo.1621539669749@email.android.com>
From: Martin Duke <martin.h.duke@gmail.com>
Date: Thu, 20 May 2021 13:50:01 -0700
Message-ID: <CAM4esxTe=sFG-TkvZV+O+Ke1hCk8vriuGzFctPHydYgqz2C=kg@mail.gmail.com>
To: lionel.morand@orange.com
Cc: Joseph Touch <touch@strayalpha.com>, Fred Baker <fredbaker.ietf@gmail.com>, "iana-port-experts@icann.org" <iana-port-experts@icann.org>, tsvwg <tsvwg@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000e5662705c2c9169a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/EMmuBagO6TKbzyjAbv6qEMEnJsU>
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 20:50:20 -0000
Lionel, I just submitted this for IESG review, and the 3GPP LS is addressed to the IESG, so this Tuesday is unlikely. On Thu, May 20, 2021 at 12:41 PM <lionel.morand@orange.com> wrote: > 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. > >
- [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… Joe Touch
- 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