Re: [3gpp-ietf-coord] IETF - 3GPP coordination meeting at IETF 116
Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Wed, 05 April 2023 22:44 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 B3383C14CE27 for <3gpp-ietf-coord@ietfa.amsl.com>; Wed, 5 Apr 2023 15:44:31 -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=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KKJ9kG0_l02s for <3gpp-ietf-coord@ietfa.amsl.com>; Wed, 5 Apr 2023 15:44:27 -0700 (PDT)
Received: from mail-pf1-x42d.google.com (mail-pf1-x42d.google.com [IPv6:2607:f8b0:4864:20::42d]) (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 EC7F8C14CE40 for <3gpp-ietf-coord@ietf.org>; Wed, 5 Apr 2023 15:44:27 -0700 (PDT)
Received: by mail-pf1-x42d.google.com with SMTP id q20so13533643pfs.2 for <3gpp-ietf-coord@ietf.org>; Wed, 05 Apr 2023 15:44:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1680734666; x=1683326666; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=4sxTk/ZgxlgDUg8f3+DCbgx94dBcawehdAy1FfTt7GU=; b=UtoV2zmfuEJrEWdyuzfyAjAhyNzDD382QDlxM1fia1xouCqJC49jHH/7DVZ7bJPVdP kyZpnp0RYmwJ937mlqQ3au7FfONSgZHKkJsaottQR9Aw+0/l6Y/qzjS3Ejc2Y57qqqFN iyCyLT76veTSkXl5/+uYSSXVXaZXT6Md46hjnt6gf+ZQe5F3rV/w/CE6gV+YukUupDvN 4lzq2GIhZspB3+xoCXFxFVn3bCatemXUFYD1VTMcTLR4hFdJg9PIxwtuSvkka8JGv9EZ iJe6LKTV5/dfuWU8XaqvVk9y4dmOqxmV/L/H9tFJ9Ff6nZqJy4XmEmxRfhCjyqRzTWIp gfLA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1680734666; x=1683326666; 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=4sxTk/ZgxlgDUg8f3+DCbgx94dBcawehdAy1FfTt7GU=; b=GxcFGwypVSJoWcOLNejM0/KtW9deMwxY950TJJQWsSAkjnv6ZBxXqMwOXfb7Jkak7/ BdUGeBPmnRhWyjPkwcto6xMoF9qEnTeL3Tw/5HmExaqh+3Z4vgITfrr9VoSC9It06qT1 s8hfFgQGKV02TRn7MIKslyDswlh6rdQJOQ1TYXgAmgKqPq+B/AIswbzcS8db8cwdxuep VDET20aBuCQlkiBkA8RiEZh9bLqBh0peNNuTFih9Fm0LvJ0kYM9gSzwKWbwjfYGax1mY xdKOyw+ftS1DfwEm+MOcSv1Zm6rMJDpaJgCLwXVlOFSWuy9hfFxJv/HIQ7vXTwS6HHmd 7D1w==
X-Gm-Message-State: AAQBX9dXpWO8UYBZo4EdJVzzxqeirKz0I2vBLjs4tYtsBqN8APhHnB9v 8+taHMRLjUXF17k7cRlROcxi0Ud1r7edg7hq9PU=
X-Google-Smtp-Source: AKy350a1PVO6L+9fccWue/Z/w/qPdvI9TQWuqCc7KvESLH0qtXeMy67/w5K6wI4aJ/tVJoB9O+fkrLEW9FO5rn1wVbI=
X-Received: by 2002:a63:2b58:0:b0:513:9705:2c45 with SMTP id r85-20020a632b58000000b0051397052c45mr2561107pgr.10.1680734665680; Wed, 05 Apr 2023 15:44:25 -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> <CAKKJt-e2zWAidFwzeUw8K96o352ZbZ+_VnneZWriTj3Ba3xi5w@mail.gmail.com> <3315F45C-CFF2-4A94-B45D-9560AC334CB1@kuehlewind.net>
In-Reply-To: <3315F45C-CFF2-4A94-B45D-9560AC334CB1@kuehlewind.net>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Wed, 05 Apr 2023 17:43:59 -0500
Message-ID: <CAKKJt-edLMfbof02T+utUg51DLzA-zjjCMXDnk2m3wny9G3Evw@mail.gmail.com>
To: Mirja Kuehlewind <ietf@kuehlewind.net>
Cc: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>, "3gpp-ietf-coord@ietf.org" <3gpp-ietf-coord@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b5addd05f89e8834"
Archived-At: <https://mailarchive.ietf.org/arch/msg/3gpp-ietf-coord/CBgzRobXxQIx28hT5TdmsEIycOM>
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, 05 Apr 2023 22:44:31 -0000
Hi, Mirja, On Thu, Mar 30, 2023 at 12:55 AM Mirja Kuehlewind <ietf@kuehlewind.net> wrote: > Hi Spencer, > > Just one high level question: Are actually trying to solve a specific > problem? I guess the coordination was less active during the pandemic but I > think it working well now, isn’t it? > Other folks would have their own sense of how well the coordination function is working now, but mine is that it's working about as well as it was before the pandemic lockdowns. You are asking an excellent question - I'm thinking that our post-pandemic recovery is an opportunity to ask if the coordination function could work *better *than it has worked in the past. I appreciate the feedback I've gotten so far - and the feedback has helped me better understand that I started out wondering if we could formally communicate more effectively, and am now thinking that if we could informally communicate more effectively, our formal communication methods might be just fine. But that's only one part of the way the two organizations work together, so I should let people with more experience in other aspects of our relationship think about what "working better" might mean to them. That's why I'm pleased to see people expressing a willingness to contribute to a revision to RFC 3113 <https://datatracker.ietf.org/doc/html/rfc3113>, when things are still working. 😇 Best, Spencer
- [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