Re: [3gpp-ietf-coord] IETF - 3GPP coordination meeting at IETF 116

Suresh Krishnan <suresh.krishnan@gmail.com> Wed, 29 March 2023 02:29 UTC

Return-Path: <suresh.krishnan@gmail.com>
X-Original-To: 3gpp-ietf-coord@ietfa.amsl.com
Delivered-To: 3gpp-ietf-coord@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BAEAC15155C for <3gpp-ietf-coord@ietfa.amsl.com>; Tue, 28 Mar 2023 19:29:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.095 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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8hutbHb0GCz2 for <3gpp-ietf-coord@ietfa.amsl.com>; Tue, 28 Mar 2023 19:29:31 -0700 (PDT)
Received: from mail-pj1-x1035.google.com (mail-pj1-x1035.google.com [IPv6:2607:f8b0:4864:20::1035]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 44CD6C14F73E for <3gpp-ietf-coord@ietf.org>; Tue, 28 Mar 2023 19:29:12 -0700 (PDT)
Received: by mail-pj1-x1035.google.com with SMTP id gp15-20020a17090adf0f00b0023d1bbd9f9eso17175712pjb.0 for <3gpp-ietf-coord@ietf.org>; Tue, 28 Mar 2023 19:29:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1680056951; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=jyYFxvpIDarHkem6MyRX8DjvcodWyUdwnlCQEpYWvxI=; b=TkjtEjj/4YO40WlT+oKOdDO6WjnS3QmzJn1asGG1lwV69NFTPC6TrHwKX5G3ENEp9q 2FnAi7lp+VZ+M3w9fQkYloYtP0tYyI7VlahIM2ober0+JBx3bk7E28ESOyJaKkYgPtiq fkoiOp2H15UR96HCz1FL5Hc1BZhIveO8QydXPvQT/Sjxyq6MLjEbug8bTf6j/kDEay7Y 1Q0/0/hLuhbqB3660IEztkuptqt5PSbL1LPpVyx4KZuIemeek9LU+3dzzZMJWJ+AsL2A /yUHMEiYTi0DN04CPjBGyYC8ceqbSIqx1g1Pb0++cgIPmwf7l0Yp7/tdTxGVEGkaFQkP aLNQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1680056951; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=jyYFxvpIDarHkem6MyRX8DjvcodWyUdwnlCQEpYWvxI=; b=neL/a0KtXSRZulLs0vQoAO1Pd34Eu/YKdah5klSeVIHqwgm9zn5Z8af5S6AxWu14ic O/bqb5MXrH3tK77u+Ev+FyAZ9iS5Rswyvzyh23v65nFOz3aoxmQHwIFJh7HB+/H4+mWy C2RpQ1boZSiDAmT3NvOcbbd6+HoFTIIK1Ac0MG5hXGLZauHvzkxnHWcOjmzEnpD1z4Cv ghKeWXR5WwaReB0YGkm5tE1JClCZkDifhFv2z47WwifDeFZsY/NNNUC6jox2HdLVFJX0 WwFFWkZ4gXBZjT6gJW8ag8av/G+tb3Bc6POQQ0ffcGPFkqV2siNDXZJt4XmwD0YgJzr1 ndMQ==
X-Gm-Message-State: AAQBX9dIwc5FoeLJDyXAl2XbZQV/vuTx+tXsw0dnN98WkNUa02wazD6y LtYgZdtPIs6hSRvUnW7ExuI+E3/I+AqB4sTayhs=
X-Google-Smtp-Source: AKy350bopW9CofiwIbqQJsO1fFo7MjGhTvoFc0PF/eqJhh37FpIFe4lRvN0+U+l/tUeYSrRqpIS5zYvsGcnWBr3wsvk=
X-Received: by 2002:a17:90a:4595:b0:23e:fad0:dda1 with SMTP id v21-20020a17090a459500b0023efad0dda1mr5158442pjg.1.1680056951404; Tue, 28 Mar 2023 19:29:11 -0700 (PDT)
MIME-Version: 1.0
References: <106A4CDF-4DA0-450C-A38C-EAE03225137E@cisco.com> <FE1A9B22-44DA-4642-8358-847E796BE43F@cisco.com> <CAKKJt-d6kbweJPfQiJGNnfYnV5sgbRs-VXzfJfQmsf=h6sLhRA@mail.gmail.com> <EBFF3DB9-3339-41F7-93B9-65571708E12A@cisco.com>
In-Reply-To: <EBFF3DB9-3339-41F7-93B9-65571708E12A@cisco.com>
From: Suresh Krishnan <suresh.krishnan@gmail.com>
Date: Wed, 29 Mar 2023 11:28:59 +0900
Message-ID: <CA+MHpBqMA_hPP=cb2VCSSw2LSGrPskXy4W9wmUUVbxNELR09zA@mail.gmail.com>
To: "Charles Eckel (eckelcu)" <eckelcu=40cisco.com@dmarc.ietf.org>
Cc: Spencer Dawkins <spencerdawkins.ietf@gmail.com>, "3gpp-ietf-coord@ietf.org" <3gpp-ietf-coord@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/3gpp-ietf-coord/0vNV9bX1SHzKQBaxBG6mUGO21ds>
Subject: Re: [3gpp-ietf-coord] IETF - 3GPP coordination meeting at IETF 116
X-BeenThere: 3gpp-ietf-coord@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: 3GPP IETF COORDINATION <3gpp-ietf-coord.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/3gpp-ietf-coord>, <mailto:3gpp-ietf-coord-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/3gpp-ietf-coord/>
List-Post: <mailto:3gpp-ietf-coord@ietf.org>
List-Help: <mailto:3gpp-ietf-coord-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/3gpp-ietf-coord>, <mailto:3gpp-ietf-coord-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Mar 2023 02:29:35 -0000

Hi Charles,
  Yep. RFC3113 is significantly out of date. I can certainly work on
an update to bring it more into the future but might need some help
from someone else on post 2020 changes in 3GPP ways of working.

Regards
Suresh

On Wed, Mar 29, 2023 at 11:13 AM Charles Eckel (eckelcu)
<eckelcu=40cisco.com@dmarc.ietf.org> wrote:
>
> Hi Spencer,
>
> Thanks for raising this topic. I view the coordination call we had yesterday as an example of a 3rd way for working together. I think it would be great to do something similar at 3GPP meetings, even if there need to be several such sessions in order to hit every group. Periodic conference calls not tied to any IETF or 3GPP meeting is also possible.
>
> I had a look at RFC 3113 before throwing my hat in the ring to be the IETF liaison manager to 3GPP and again in prep for this meeting. It was helpful, but some things have definitely changed and an update would be helpful. While admittedly not high on my todo list coming into this meeting, your note combined with the fact that I find myself learning many things about this collaboration effort by living it here in Yokohama makes me think now if a great time to start updating it. We can also experiment with your suggested 3rd way of collaborating, and we can document things as we find things that seem to work well.
>
> If anyone has a work in progress update to RFC 3113 or has the drive the create one before I do, please let me know.
>
> Thanks again,
> Charles
>
> On Mar 28, 2023, at 11:15 AM, Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> wrote:
>
> Hi, Charles and Lionel,
>
> I wouldn't think of suggesting this as a topic for a meeting that starts in less than 15 minutes, but I do wonder if is possible to imagine (in 2023) some way for our two organizations to communicate, cooperate, and collaborate, in a way that is
>
> more formal than telling participants in each organization that they should also participate in the other organization, and seeing what happens, but
> less formal than sending liaisons between the two organizations, which the IETF can send and respond to with e-mail approval, but 3GPP cannot, only agreeing to send and reply to liaisons at TSG meetings.
>
> To be clear, I'm not asking about a change to these two primary ways of coordination. I'm asking about introducing a third way of coordination.
>
> It might be that neither organization is ready for that, but it IS 2023, so I thought I'd ask. If RFC 3113 is still the governing document for our relationship, it was published in 2001. A lot of things have changed since then, and even if RFC 3113 was perfect in 2001, perhaps we can do better on this specific point.
>
> As I said, I'm not proposing this as a topic for discussion today, but perhaps this mailing list is an appropriate place to share thoughts between now and IETF 117.
>
> Best,
>
> Spencer
>
> On Mon, Mar 27, 2023 at 7:25 PM Charles Eckel (eckelcu) <eckelcu=40cisco.com@dmarc.ietf.org> wrote:
>>
>> Hi All,
>>
>> We have updated the agenda as follows:
>>
>> Round table
>> Ongoing LS
>>
>> Response to 3GPP SA2 LS on 3GPP 5G System acting as a DetNet node
>> LS on need for modeling isInvariant and SystemCreated in YANG
>> Updated LS to 3GPP regarding SCTP-AUTH and DTLS
>> Improving the handling of LS exchanged between IETF and 3GPP
>>
>> Ongoing IANA action
>> Status of the 3GPP-IETF dependencies
>> 3GPP Release Roadmap (informational)
>> AoB
>>
>>
>> Attached are slides to aid our discussion. We look forward to seeing everyone tomorrow.
>> https://datatracker.ietf.org/meeting/116/agenda?filters=ietf-3gpp-coordination
>>
>> Cheers,
>> Charles and Lionel
>>
>>
>> On Mar 17, 2023, at 7:05 AM, Charles Eckel (eckelcu) <eckelcu@cisco.com> wrote:
>>
>> Hi Everyone,
>>
>> We will have an IETF - 3GPP coordination meeting at IETF 116 on Tuesday during the lunch break (11:30 - 13:00).
>> For those attending in person, we will be meeting in G318 (3rd floor). Lunch will be provided.
>> Those attending remotely can join via Webex. Sorry, but no time zone appropriate meal provided in this scenario.
>>
>> https://datatracker.ietf.org/meeting/116/agenda?filters=ietf-3gpp-coordination
>>
>> The currently planned agenda for our meeting is as follows:
>>
>> Roundtable discussion
>> Status of the 3GPP-IETF dependencies
>> Ongoing IANA action
>> Incoming/Outgoing LSs
>> AoB
>>
>> Please feel free to suggest additional agenda items.
>> We look forward to meeting with you during IETF 116.
>>
>> Cheers,
>> Charles and Lionel
>>
>>
>> _______________________________________________
>> 3gpp-ietf-coord mailing list
>> 3gpp-ietf-coord@ietf.org
>> https://www.ietf.org/mailman/listinfo/3gpp-ietf-coord
>
>
> _______________________________________________
> 3gpp-ietf-coord mailing list
> 3gpp-ietf-coord@ietf.org
> https://www.ietf.org/mailman/listinfo/3gpp-ietf-coord