[3gpp-ietf-coord] My notes from the IETF-3GPP coordination meeting at IETF 119
Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Mon, 18 March 2024 03:39 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 5CF06C14F6AF for <3gpp-ietf-coord@ietfa.amsl.com>; Sun, 17 Mar 2024 20:39:34 -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, 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, T_KAM_HTML_FONT_INVALID=0.01, T_SCC_BODY_TEXT_LINE=-0.01, 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 zooCa7U6iBUF for <3gpp-ietf-coord@ietfa.amsl.com>; Sun, 17 Mar 2024 20:39:29 -0700 (PDT)
Received: from mail-oa1-x2b.google.com (mail-oa1-x2b.google.com [IPv6:2001:4860:4864:20::2b]) (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 CBCC9C14F6AE for <3gpp-ietf-coord@ietf.org>; Sun, 17 Mar 2024 20:39:29 -0700 (PDT)
Received: by mail-oa1-x2b.google.com with SMTP id 586e51a60fabf-2218b571776so2467928fac.0 for <3gpp-ietf-coord@ietf.org>; Sun, 17 Mar 2024 20:39:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1710733168; x=1711337968; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=WKn7MKlHMcOTPdjaqkRyHYQUogZiMo/RxfF6mroZ4mA=; b=QcUGWVxO129qQEtdExLaXIC/evh/SBqR0/uXoW8L4IWK2rC6XxoIee5sIG0Lq+/KN9 ObsKqoL0B1dY2bJOu80qZ88ygFnSLTeaSNzxZgUxDhdl4DfxCuvEaaY+revZIahTH21u tP7YHnj+6lrvl+xxV8Ugcb8OM7CyL17u4KjH5qF8rqMdHvG4xU6GYWim9WPGg+aExEON 7q6kBlkj0juNvXCpDgNxa7/E32i6z9vot4xjxR/t+/VJUXLHWPHv2fgBJ99jkYhlcYs6 H/51fUycHHecjb/zUo5XbFDAPwYm1lfMSl5u5x7YudCVxRi7aEIb5nLPCQcNtzmDuNZF R8Eg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1710733168; x=1711337968; 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=WKn7MKlHMcOTPdjaqkRyHYQUogZiMo/RxfF6mroZ4mA=; b=hNGF6EstnS+ugDGrd1fY8l68bWndICcy9aNabQiqeuoMYYoxN5SGueWHCBHJ8qGiuY C962vCU/4RnljH9lEH2fNZg0TEZObQRVMLKTaFSflf2H12RJa7tNgIwtODkFMUx0rSKI x5R+r4EraPOYbM5pJRoclosDF/rLeZZrSeeZwj57eclSZokNj+JOZgkX1DjcdpVOhaaO A12HysTKMWObZ9br2DX8tI3I7lYVsiMx64pz9sM2K69uEu0H9cW0KoQExPVxwK05dhbB BWTc0NxcgCvgLyrpwIVF/HxUJtJZi7a28uFM64dwJ7XPZofpJvZTmAq6PBc+KTT53CbK lhWQ==
X-Gm-Message-State: AOJu0YzEDuqHqu6OFhFHCZlKFhRsGFFg07WHawaDFQFxj+2DNkYNI2IO wE2vPRYNGW+xZwN/XRIMLNQRpb9ssmCUmkI9zOssSdGHAdGyvLl5v6FCwS/IYy/uob59cS57Vkf bAvCBiXM/Wli6X3FFvAyNO3eoksk=
X-Google-Smtp-Source: AGHT+IHNB1mutQMdjnhPdEZJn8c4Nm4WBRYy8RV7mOJ7/shgsICYicBsObIRj+YQuk6e5Z9YHJkr8oxzWaGKc25jpw8=
X-Received: by 2002:a05:6870:304e:b0:221:bca9:3b81 with SMTP id u14-20020a056870304e00b00221bca93b81mr13602298oau.22.1710733168268; Sun, 17 Mar 2024 20:39:28 -0700 (PDT)
MIME-Version: 1.0
References: <4C244213-2CB5-496E-BDA3-4533D83F7A0A@cisco.com>
In-Reply-To: <4C244213-2CB5-496E-BDA3-4533D83F7A0A@cisco.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Sun, 17 Mar 2024 22:39:02 -0500
Message-ID: <CAKKJt-fMdMOP0n9YjGKn3qJQDwmEjtUe6qJcj4u9ZA06YBDKGQ@mail.gmail.com>
To: "Charles Eckel (eckelcu)" <eckelcu=40cisco.com@dmarc.ietf.org>, Peter Schmitt <peter.schmitt@huawei.com>
Cc: "3gpp-ietf-coord@ietf.org" <3gpp-ietf-coord@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000ccdd590613e71a08"
Archived-At: <https://mailarchive.ietf.org/arch/msg/3gpp-ietf-coord/Sc7Y5dHG7C43xliQjNZet72lbsc>
Subject: [3gpp-ietf-coord] My notes from the IETF-3GPP coordination meeting at IETF 119
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: Mon, 18 Mar 2024 03:39:34 -0000
Hi, Charles and Peter, Here are my notes from today's meeting. I should mention that only Charles, Spencer, and Francesca signed in - could people do that, at the bottom of the HedgeDoc <https://notes.ietf.org/tK-BTcZVQUKvqowjJg9Zog?both#Attendees>? Best, Spencer IETF-3GPP coordination IETF 119 Monday, 18 March, 1145 - 1245 Room: P6-7 Remote participation: https://ietf.webex.com/meet/ietfsidemeeting2 <https://notes.ietf.org/#Agenda>Agenda <https://notes.ietf.org/#Welcome-notetakers-agenda-bash>Welcome, notetakers, agenda bash Spencer Dawkins took notes in HedgeDoc <https://notes.ietf.org/tK-BTcZVQUKvqowjJg9Zog?both> (Spencer could not hear a significant part of the discussion in the meeting room due to A/V issues - corrections would be AWESOME) <https://notes.ietf.org/#Teleconferences-between-IETF-meeting>Teleconferences between IETF meeting No teleconferences since the last IETF meeting - Charles thinks those won’t be automatic, but will be scheduled when there’s something to coordinate <https://notes.ietf.org/#Liaisons>Liaisons 1. SA5 -> NETMOD - needed draft has been adopted 2. SA3 and RAN3 -> TSVWG 3. (Spencer missed one liaison exchange here) 4. SA5 -> TM Forum, cc: IETF on autonomous networks, for information, no action required, shared with the IESG 5. TSVWG -> CT1, CT3, CT4, RAN2, SA2, SA4 - notification of work that is completed, contribution was noted <https://notes.ietf.org/#Dependencies>Dependencies 1. RFC 9201 has been published 2. RFC 9202 has been published 3. RFC 9203 has been published 4. RFC 9430 has been published 5. RFC ??? has been published - Spencer missed the number 6. stir-passport-rcd is in RFC Editor queue 7. detnet-yang is in RFC Editor queue 8. No dependencies in IESG Evaluation 9. quic-multipath is still in the working group 10. opsawg-teas-attachment-circuit recently adopted by the working group and being actively worked on, no concerns here 11. jesske-update-p-visited-network - this is part of an RFC 7969 bis, and we discovered that there are already errata related to the change - need to make sure the draft and errata are aligned 12. schwarz-mmusic-sdp-for-gw no longer needed - CP240006 removes this dependency We don’t have to send LSes to elevate attention for a dependency draft <https://notes.ietf.org/#Coordination-email-list>Coordination email list New IESG members to be invited to the mailing list, retiring members are welcome to stay, but they can remove themselves from the mailing list, so Do The Right Thing <https://notes.ietf.org/#RFC-3113-update>RFC 3113 update Spencer has migrated the text of RFC 3113 into kramdown-rfc, and uploaded it into GitHub here <https://github.com/SpencerDawkins/rfc3113bis>. RFC 3113 is old enough that it seemed useful to make some changes (for instance, RFC 3113 has a terminology section and then the Introduction, but most Internet-Drafts begin with an Introduction). The diff between what’s in RFC 3113 and what’s in draft-dawkins-iab-rfc3113bis-latest is here <https://author-tools.ietf.org/iddiff?url1=https://www.rfc-editor.org/rfc/rfc3113.txt&url2=https://raw.githubusercontent.com/SpencerDawkins/rfc3113bis/main/draft-dawkins-iab-rfc3113bis.md&difftype=--html>, for your perusal. Spencer has added himself as editor, and Charles and Peter as co-authors. Spencer has notified John Klensin and Scott Bradner (IETF and IAB-side co-authors of RFC 3113) as a courtesy, and will notify Karl Heinz Rosenbrock and Raj Sanmugam (3GPP-side co-authors of RFC 3113) soon. Spencer has discussed details about working practices for the update with Charles and with Peter, but the most important thing for this group to know, is that we expect to have discussions using the 3gpp-ietf-coord@ietf.org mailing list, and that’s a good place for us to keep in touch as work proceeds. We can’t just do a bis on RFC 3113 - it was also approved on the 3GPP side, so we expect any update would also be approved on both sides Mirja noted that if we are doing minor corrections and tuning, we might be able to publish errata, or put up a wiki, or something else that’s lightweight. Spencer’s understanding is that Spencer, Charles, and Peter will - coordinate with Suresh as our IAB contact, to keep the IAB informed, - submit the minimal-difference main branch that’s in GitHub now, as draft-dawkins-iab-rfc3113bis-00, - use GitHub issues to identify needed corrections to RFC3113, and any topics that we need to add to the resulting RFC, - discuss significant changes on the 3gpp-ietf-coord@ietf.org mailing list, - summarize discussion on issues and proposed text changes on the same mailing list, and - submit draft revisions to the IETF datatracker periodically (Spencer suggested once per IETF cycle), so that both communities remain informed about this work <https://notes.ietf.org/#3GPP-Tutorial>3GPP Tutorial (Spencer was still writing notes from the previous section) <https://notes.ietf.org/#IAB-Open>IAB Open Charles will be talking about this coordination group during IABOPEN this week <https://notes.ietf.org/#AoB>AoB None noted on the call <https://notes.ietf.org/#Attendees>Attendees Charles Eckel, Cisco Spencer Dawkins, Tencent America Francesca Palombini, Ericsson
- [3gpp-ietf-coord] IETF-3GPP coordination meeting … Charles Eckel (eckelcu)
- [3gpp-ietf-coord] My notes from the IETF-3GPP coo… Spencer Dawkins at IETF
- Re: [3gpp-ietf-coord] My notes from the IETF-3GPP… Charles Eckel (eckelcu)
- Re: [3gpp-ietf-coord] My notes from the IETF-3GPP… Spencer Dawkins at IETF