Re: [3gpp-ietf-coord] My notes from the IETF-3GPP coordination meeting at IETF 119

[Spencer Dawkins at IETF <[e-mail]>]

Charles,

On Mon, Mar 18, 2024 at 5:45 PM Charles Eckel (eckelcu) <[e-mail]>
wrote:

> Hi Spencer,
>
> Thanks for these fantastic notes, especially in light of the challenges we
> experienced with the A/V.
> I will review and update if and where appropriate these later today, and I
> encourage others to do the same.
> My apologies to both those in the room and remote for the A/V issues.
> Thank you for your patience as we worked through them.
>

Thanks for the feedback, and for encouraging review by others who WERE in
the room!

It would be helpful if someone could add a couple of words about the
proposed Technology Deep Dive on 3GPP (it was on the agenda, but I was
still typing like mad on notes for the RFC 3113 update, and didn't surface
until the following agenda item on Charles' presentation on this
coordination team at the IABOPEN session at this IETF meeting).

Best,

Spencer


> Cheers,
> Charles
>
> On Mar 18, 2024, at 1:39 PM, Spencer Dawkins at IETF <
> [e-mail]> wrote:
>
> 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
> [e-mail] 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 [e-mail] 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 mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/3gpp-ietf-coord
>
>
>