[tsvwg] 3GPP Liaison Statement clarifying port requests
Martin Duke <martin.h.duke@gmail.com> Tue, 18 May 2021 17:49 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 3E5AE3A1B3E for <tsvwg@ietfa.amsl.com>; Tue, 18 May 2021 10:49:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, 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 TZYfpzrwQPkr for <tsvwg@ietfa.amsl.com>; Tue, 18 May 2021 10:49:03 -0700 (PDT)
Received: from mail-il1-x133.google.com (mail-il1-x133.google.com [IPv6:2607:f8b0:4864:20::133]) (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 D09463A1B06 for <tsvwg@ietf.org>; Tue, 18 May 2021 10:49:03 -0700 (PDT)
Received: by mail-il1-x133.google.com with SMTP id c16so9921674ilo.1 for <tsvwg@ietf.org>; Tue, 18 May 2021 10:49:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=aZbOZ6BhAN9PRhenuToEKfuLOhrHgWHpmWdkHy6F2FM=; b=G+yUyVtxGEJu28EwQ35456Ljn22dTH9DZnJgKUitpY9XKU3FWh2Xpo4IDYpU2/2l4J PqCdglxykNCVZvb8ySfkUIViaQBUNg+mtMO/5PpRXStiwN7h5KntzFF0nnXgEmylGjyS o2aD88efh+J7Mj5IRaI9i7fZN4SKWtpyiPlRYKpaCREOgFqKpE+sRg1dh/tiVw1dwzCh +kIUSrJQfZl0fSIDb9YAbmK50Sr9OH2OySzbQBnG4sQVpCVfYNZziJG6m3K/oqvWrFnt fyOKk4RLJPkn0i8joDgfSe9TjVNFJwRgnzUQzJ6jNjGAbTRJzhIM3PAWfi7XQ3SfAJ1e 22rA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=aZbOZ6BhAN9PRhenuToEKfuLOhrHgWHpmWdkHy6F2FM=; b=Dx5pf8LmDst6qE9JLg7SusRkDfXF6/ClOXMVldaau+RCHU9iSrcCGZa+XESrtIj268 Gxt+Gr0b2oUQGF+PNEnriY+GVQkmS+2vuxUcux1G5Ef+97Mq43ERpNh967QP+bxJ/qKy CHFS8nCptg7+ZuXl+8ckNhejqDObbU4kfB8U5RIHpzanhjtAyWRU7GMNHDbUxjh1vmh+ MWEEeeCSEfz5tkpvbzEKMTrzMdlmfLVd9+9FrVMdbVrnbZuVtAZEDb+Rwv+oDvtsP0Vj ioYgCb9i0Lk7+RWBppmvHtsTfBQ8m0y0wWlSLfzCCfNC2m1I06EH2ec+ACjyPdhW4Qf0 TI4A==
X-Gm-Message-State: AOAM531Cogc/xGWK7OkbqnvxRSuLfhWcTFgtukL0w5V2I/KRkDEup3Uu a+F/isqBLzjgQ4ogEOsvEnfnrBBMariJSY2RBC5bqDHLE6NxPA==
X-Google-Smtp-Source: ABdhPJysFVkAm2YDpw9PJckeGKATCZgMRpPljtwEwX8L/vL+jw9cLZXlVOAd1tE1PaeVgVvq8xfY0NESUVnzkZpwZdw=
X-Received: by 2002:a05:6e02:1a03:: with SMTP id s3mr5615243ild.272.1621360142216; Tue, 18 May 2021 10:49:02 -0700 (PDT)
MIME-Version: 1.0
From: Martin Duke <martin.h.duke@gmail.com>
Date: Tue, 18 May 2021 10:48:58 -0700
Message-ID: <CAM4esxRcxJ7HZSG2gk75+sA1PRWjkQqQT0F7+1EsG8gLOy__yA@mail.gmail.com>
To: iana-port-experts@icann.org, tsvwg <tsvwg@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000054725905c29e5311"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/EBfKhPtyfvt-D485VjyS689mNF0>
Subject: [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: Tue, 18 May 2021 17:49:20 -0000
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