IETF-3GPP coordination meeting at IETF 120

Monday, 22 July 2024, 1145 - 1245
Room: English Bay, 34th floor, Hyatt Regency Vancouver
Remote Participation:
https://meetings.conf.meetecho.com/ietf120/?session=1003

Agenda

Welcome, notetakers, agenda bash

Notes from Spencer Dawkins, and Suresh Krishnan

Liaisons statements

SA5->NETMOD

• NETMOD to touch base with SA5 before requesting publication of this
  draft

SA3 and RAN3 -> TSVWG

• Design team and TSVWG working on draft, LS to be sent once solution
  ready for review by 3GPP
• To be discussed in more detail in Friday's session

DRIP -> SA2, SA3

• Liaison handling delayed on 3GPP side but is on the agenda for the
  3GPP August meeting

TEAS -> SA2, SA3, SA5, RAN3

• 2 liaisons are on the agenda for the 3GPP August meeting
• TEAS has requested feedback by the end of August

SA -> QUIC on QUIC security considerations

• Version liaised needed a security considerations section, but now it
  has one
• Work in QUIC is proceeding well in parallel (communication between
  SDOs for the win)
• Is a reply needed? It wouldn't hurt, especially if QUIC has thoughts
• Please reply to SA, cc: SA2 and SA3 so the TSGs can analyse the
  results
• Remember that the discussion should happen in QUIC, not in 3GPP SA
  TSGs

Dependencies

• Several dependencies are published as RFCs, so don't need to be
  tracked further
• STIR draft references were updated but not corresponding text, CRs
  are needed to reflect that, Peter to contact responsible chair to
  address
• STIR Passport RCD has MISSREF
• DETNET YANG model is also in MISSREF
• OPSAWG is going through IESG Review, no action needed here
• No concerns on QUIC Multipath or MIMI Content
• SIPCORE-rfc7976bis is processing WGLC responses
• MASQUE Connect Ethernet has been adopted. Not referenced in
  normative text yet, but was noted in conclusions in a TR, so a
  normative reference is coming soon.
• bhutton-json-schema is still an individual draft, but is being
  referenced, so needs to be tracked here. No author energy, so tell
  SA4 that this needs help - ART AD (Orie Steele) wants to help.
  Charles to email Orie with details.
• newton-json-content-rules is in the same situation - Peter Schmitt
  will forward email from SA4 chair

5QI to DiffServ DSCP Mapping

• draft-cbs-teas-5qi-to-dscp-mapping
• cbs-teas-5gi-to-dscp-mapping is on the agenda in TEAS now. David
  Black reports that four-five years ago, 3GPP was strongly opposed to
  IETF doing work in this space - it's good to level-set again before
  trying to move in any direction. Suresh suggested to Zahed to
  co-ordinate with Jim Guichard within the IESG to ensure that both
  Routing and Transport views on this topic are received and collated.
  Zahed also emphasized that tight coordination is required here.
  There were concerns about forum-shopping, so this needs to go to a
  single AD (Zahed suggested a routing AD). Coordination isn't
  premature - this is an important dependency for 3GPP, and if there's
  no interest in the IETF, 3GPP needs to come up with another plan.
  Maybe it's OK to wait and see how TEAS reacts to this draft, this
  week? If there is interest, we should be sending a LS to 3GPP from
  the IETF side that this work is being considered (e.g., individual
  draft out for adoption call in WG.

Coordination email list

• Datatracker has us as IAB now - is everyone subscribed after that
  change?
• Charles does moderate subscription requests - please let him know if
  there's any problem with that process

RFC 3113 update

• The IAB is choosing to do updates at a high-level only, and wants to
  move pretty much everything to a wiki
• Suresh is taking over the prime role for the bis document, to be in
  IAB stream
• Spencer had issues created in GitHub, but these aren't actually
  synchronized with the current IAB thinking
• Mirja suggested that the wiki could be part of the IAB wiki space
• The resulting bis RFC should be VERY short
• Suresh suspects that the level of detail in RFC 3113 wasn't actually
  helpful in guiding IETF participants to the right place in 3GPP (for
  example)

3GPP Tutorial

• Target tutorial and/or TDD for IETF 121 in Dublin
• Develop set of topics and put together and deliver based on who
  volunteers
• Warren prefers to do both tutorial and TDD

AoB

• Store and Forward
• Ed Birrane shared SA1 has related requirements and SA2 has a study
• Ed to draft text, circulate with WGs and AD, and share with Charles
  when ready to send LS