Re: [3gpp-ietf-coord] IETF - 3GPP coordination meeting at IETF 116

[[e-mail]]

Of course, I can help too 😊


Orange Restricted

> -----Message d'origine-----
> De : 3gpp-ietf-coord <[e-mail]> De la part de Charles
> Eckel (eckelcu)
> Envoyé : mercredi 29 mars 2023 04:50
> À : Suresh Krishnan <[e-mail]>
> Cc : Spencer Dawkins <[e-mail]>; 3gpp-ietf-
> [e-mail]
> Objet : Re: [3gpp-ietf-coord] IETF - 3GPP coordination meeting at IETF 116
> 
> Hi Suresh,
> 
> That would be fantastic. I am happy contribute what I have picked up about current
> 3GPP ways of working. Many changes were put into play in response to COVID, a
> few of which seem to be sticking as we transition back to being able to meet in
> person.
> 
> Cheers,
> Charles
> 
> > On Mar 29, 2023, at 11:28 AM, Suresh Krishnan <[e-mail]>
> wrote:
> >
> > Hi Charles,
> >  Yep. RFC3113 is significantly out of date. I can certainly work on an
> > update to bring it more into the future but might need some help from
> > someone else on post 2020 changes in 3GPP ways of working.
> >
> > Regards
> > Suresh
> >
> > On Wed, Mar 29, 2023 at 11:13 AM Charles Eckel (eckelcu)
> > <eckelcu=[e-mail]> wrote:
> >>
> >> Hi Spencer,
> >>
> >> Thanks for raising this topic. I view the coordination call we had yesterday as
> an example of a 3rd way for working together. I think it would be great to do
> something similar at 3GPP meetings, even if there need to be several such
> sessions in order to hit every group. Periodic conference calls not tied to any IETF
> or 3GPP meeting is also possible.
> >>
> >> I had a look at RFC 3113 before throwing my hat in the ring to be the IETF
> liaison manager to 3GPP and again in prep for this meeting. It was helpful, but
> some things have definitely changed and an update would be helpful. While
> admittedly not high on my todo list coming into this meeting, your note combined
> with the fact that I find myself learning many things about this collaboration effort
> by living it here in Yokohama makes me think now if a great time to start updating
> it. We can also experiment with your suggested 3rd way of collaborating, and we
> can document things as we find things that seem to work well.
> >>
> >> If anyone has a work in progress update to RFC 3113 or has the drive the
> create one before I do, please let me know.
> >>
> >> Thanks again,
> >> Charles
> >>
> >> On Mar 28, 2023, at 11:15 AM, Spencer Dawkins at IETF
> <[e-mail]> wrote:
> >>
> >> 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 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=[e-mail]> 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 DetNet node LS
> >>> on need for modeling isInvariant and SystemCreated in YANG Updated
> >>> LS to 3GPP regarding SCTP-AUTH and DTLS 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-co
> >>> ordination
> >>>
> >>> Cheers,
> >>> Charles and Lionel
> >>>
> >>>
> >>> On Mar 17, 2023, at 7:05 AM, Charles Eckel (eckelcu) <[e-mail]>
> 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 (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-co
> >>> ordination
> >>>
> >>> 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
> >>> [e-mail]
> >>> https://www.ietf.org/mailman/listinfo/3gpp-ietf-coord
> >>
> >>
> >> _______________________________________________
> >> 3gpp-ietf-coord mailing list
> >> [e-mail]
> >> https://www.ietf.org/mailman/listinfo/3gpp-ietf-coord
> 
> _______________________________________________
> 3gpp-ietf-coord mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/3gpp-ietf-coord

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.