Re: [3gpp-ietf-coord] IETF - 3GPP coordination meeting at IETF 116
Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Tue, 28 March 2023 02:15 UTC
Return-Path: <spencerdawkins.ietf@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 B540AC151548 for <3gpp-ietf-coord@ietfa.amsl.com>; Mon, 27 Mar 2023 19:15:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.094
X-Spam-Level:
X-Spam-Status: No, score=-2.094 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_NONE=-0.0001, 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 sZ6IcUNdvxTI for <3gpp-ietf-coord@ietfa.amsl.com>; Mon, 27 Mar 2023 19:15:39 -0700 (PDT)
Received: from mail-pj1-x1030.google.com (mail-pj1-x1030.google.com [IPv6:2607:f8b0:4864:20::1030]) (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 EDE7EC15152E for <3gpp-ietf-coord@ietf.org>; Mon, 27 Mar 2023 19:15:39 -0700 (PDT)
Received: by mail-pj1-x1030.google.com with SMTP id o6-20020a17090a9f8600b0023f32869993so13735432pjp.1 for <3gpp-ietf-coord@ietf.org>; Mon, 27 Mar 2023 19:15:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1679969739; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=7y1fB+rg+VgNrMyjQPtC9/0PsWVcVsmGfUwW1Bmp7hE=; b=nNj178WAAPQCsBv/FHSgFEAk3fDSHVuP10Josjl0SFJJ4ulEfMUcv3MGun5QR1snms 0D4T0dpmHkmUzRPYgSXbyHYIDpEtg6xODcfit2NOsYbWWGqip7A9cgCotw8R2sG9POgV Wm9js5zyGfO45UCKtHazVc+uy41gf6xccL44vnINttdFhRD7JaIwY7QkD8JVTpidXUXN W2Fb5JO0ZEJ/KJHzi7lCuoVuIE3ahTmhyNxwcN8xc3EoT1idWbBJ0tuTBFzXpC5+9pRT M6FcEZ4+rxvPOnqHoM2KGA5LunpyekzJ05Bp8ImtAmki7QesVdId+/KTpwIxd3sOJgGO 3HOw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1679969739; h=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=7y1fB+rg+VgNrMyjQPtC9/0PsWVcVsmGfUwW1Bmp7hE=; b=bkl107/BWZ5Q8skrE+sExphk5QFyO9RCZEc8m4QLOiuD5m93NQxH6aoy69/eC14ima Gv1x79thJRytRDRsmxP/7U+h3MKdMFoM/yhtbjD7bjvf2tN5yxKyap44E7iCZmGqUwKN VcP6y1TYbxcEbIfJNG3RHm663qDce9DSRNVhVQxoeGybBJiDSB4JAq7HXme9eodpb3jT ADysRwM972MVJUpOyzToW5QAFDBkslRmTgFEBOLywImluPv1poX+6XxCLRbxC1J7gJOQ Ba4chXS2grWWxGirwN9MOuYbbOV6tpFIXRhieCgtFhjrVzIj7vcUrxgMhMVCZEZ9LVCF D+qw==
X-Gm-Message-State: AAQBX9cAZ9tOOe0sSEFUb2MOZc8Hbqie7XoqBdity0wBzkxaPL2KLl5T L2sn6/EHH95fyD+7PTvPfVKGq4nbRJ0zaIZ0XaSODysH6m7nKQ==
X-Google-Smtp-Source: AKy350ZhLKb6jtm7Vu+mjWDOnNnC+wnByt+Liv0RAOJ27ns+PFBVd4Yyqqeh4jvG8ZadNYqZB9d5YQoSOSF+MDnW33I=
X-Received: by 2002:a17:902:7b89:b0:19f:2c5a:5786 with SMTP id w9-20020a1709027b8900b0019f2c5a5786mr4833255pll.8.1679969739314; Mon, 27 Mar 2023 19:15:39 -0700 (PDT)
MIME-Version: 1.0
References: <106A4CDF-4DA0-450C-A38C-EAE03225137E@cisco.com> <FE1A9B22-44DA-4642-8358-847E796BE43F@cisco.com>
In-Reply-To: <FE1A9B22-44DA-4642-8358-847E796BE43F@cisco.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Tue, 28 Mar 2023 11:15:12 +0900
Message-ID: <CAKKJt-d6kbweJPfQiJGNnfYnV5sgbRs-VXzfJfQmsf=h6sLhRA@mail.gmail.com>
To: "Charles Eckel (eckelcu)" <eckelcu=40cisco.com@dmarc.ietf.org>
Cc: "3gpp-ietf-coord@ietf.org" <3gpp-ietf-coord@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000008b9c3105f7ec6f24"
Archived-At: <https://mailarchive.ietf.org/arch/msg/3gpp-ietf-coord/rV7bE2prAJ3P4yTa7TebeUgdl-U>
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: Tue, 28 Mar 2023 02:15:43 -0000
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 <https://datatracker.ietf.org/doc/html/rfc3113>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 > <https://datatracker.ietf.org/liaison/1816/>DetNet > <https://datatracker.ietf.org/liaison/1816/> node > <https://datatracker.ietf.org/liaison/1816/> > - LS on need for modeling > <https://datatracker.ietf.org/liaison/1818/>isInvariant > <https://datatracker.ietf.org/liaison/1818/> and > <https://datatracker.ietf.org/liaison/1818/>SystemCreated > <https://datatracker.ietf.org/liaison/1818/> in YANG > <https://datatracker.ietf.org/liaison/1818/> > - Updated LS to 3GPP regarding SCTP-AUTH and DTLS > <https://datatracker.ietf.org/liaison/1806/> > - 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 > <https://datatracker.ietf.org/meeting/116/floor-plan?room=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] IETF - 3GPP coordination meetin… Charles Eckel (eckelcu)
- Re: [3gpp-ietf-coord] IETF - 3GPP coordination me… Magnus Westerlund
- Re: [3gpp-ietf-coord] IETF - 3GPP coordination me… lionel.morand
- Re: [3gpp-ietf-coord] IETF - 3GPP coordination me… Gonzalo Camarillo
- Re: [3gpp-ietf-coord] IETF - 3GPP coordination me… Magnus Westerlund
- Re: [3gpp-ietf-coord] IETF - 3GPP coordination me… Gonzalo Camarillo
- Re: [3gpp-ietf-coord] IETF - 3GPP coordination me… Mirja Kuehlewind
- Re: [3gpp-ietf-coord] IETF - 3GPP coordination me… Charles Eckel (eckelcu)
- Re: [3gpp-ietf-coord] IETF - 3GPP coordination me… lionel.morand
- Re: [3gpp-ietf-coord] IETF - 3GPP coordination me… Magnus Westerlund
- Re: [3gpp-ietf-coord] IETF - 3GPP coordination me… Charles Eckel (eckelcu)
- Re: [3gpp-ietf-coord] IETF - 3GPP coordination me… Spencer Dawkins at IETF
- Re: [3gpp-ietf-coord] IETF - 3GPP coordination me… Charles Eckel (eckelcu)
- Re: [3gpp-ietf-coord] IETF - 3GPP coordination me… Suresh Krishnan
- Re: [3gpp-ietf-coord] IETF - 3GPP coordination me… Charles Eckel (eckelcu)
- Re: [3gpp-ietf-coord] IETF - 3GPP coordination me… lionel.morand
- Re: [3gpp-ietf-coord] IETF - 3GPP coordination me… Spencer Dawkins at IETF
- Re: [3gpp-ietf-coord] IETF - 3GPP coordination me… Mirja Kuehlewind
- Re: [3gpp-ietf-coord] IETF - 3GPP coordination me… Spencer Dawkins at IETF