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

[[e-mail]]

Hi,

The real issue is that LS should be sent to the 3GPP liaison coordinator as a formatted document (word, pdf, ptt) that can be then forwarded by the 3GPP liaison coordinator to the WG.
Receiving only a email with the content of the LS in the email body implies to copy the email and paste it in a word document to be able to forward it to the WG.
Moreover, time to time, the LS is only sent to "3GPP" and not to specific WG(s), which make difficult to identify the relevant WG(s), which delays the handling of the LS.

Regards,

Lionel

.


Orange Restricted
De : 3gpp-ietf-coord <[e-mail]> De la part de Charles Eckel (eckelcu)
Envoyé : vendredi 17 mars 2023 17:25
À : Mirja Kuehlewind <[e-mail]>
Cc : Gonzalo Camarillo <gonzalo.camarillo=[e-mail]>; Magnus Westerlund <magnus.westerlund=[e-mail]>; [e-mail]
Objet : Re: [3gpp-ietf-coord] IETF - 3GPP coordination meeting at IETF 116

Thanks or bringing this up Magnus.

As I understand it, LSs to any 3GPP group are treated as any other meeting contribution to a 3GPP group. There are very specific formatting requirements for contributions in general, and there are additional requirements specifically for contributions corresponding to a LS to 3GPP.  The resulting document must be uploading into the meeting contribution tool used for all other 3GPP meeting contributions. I think of it as being similar to if IETF was to require LSs to IETF to be submitted as I-Ds.

In the short-term, I believe the question is who is responsible for making sure LSs from IETF to 3GPP are formatted and submitted as valid 3GPP meeting contributions. If the 3GPP secretariat is able and willing to take that on, great, otherwise, I think it falls on me and Lionel to work with anyone in IETF who wishes to send an LS to 3GPP.

In the long term, perhaps we can see if 3GPP is willing to relax their requirements for LSs, and we can see what can be accomplished with improved tooling.

Cheers,
Charles

On Mar 17, 2023, at 7:43 AM, Mirja Kuehlewind <[e-mail]<mailto:[e-mail]>> wrote:

You can also attached a PDF in the tool. However, if that is needed for 3gpp we need to document that clearly somewhere or even ask for tooling support that for 3gpp LS an attachment is required.



On 17. Mar 2023, at 14:29, Gonzalo Camarillo <gonzalo.camarillo=[e-mail]<mailto:gonzalo.camarillo=[e-mail]>> wrote:

Yes, this issue has surfaced as a result of having Liaison Statements sent directly from the tool, which is of course a very useful feature (if we get it to work properly).

Gonzalo

From: Magnus Westerlund <magnus.westerlund=[e-mail]<mailto:magnus.westerlund=[e-mail]>>
Sent: Friday, 17 March 2023 14:22
To: Gonzalo Camarillo <[e-mail]<mailto:[e-mail]>>; Charles Eckel (eckelcu) <[e-mail]<mailto:[e-mail]>>; [e-mail]<mailto:[e-mail]>
Subject: Re: IETF - 3GPP coordination meeting at IETF 116



  *   Right, a long time ago they asked us to simply put the email in a WORD document, which is what we have been doing all along. Alternatively, as you suggest, we could discuss with them so that they update their process and accept emails.

Well I think there might be some gap here, and the datatracker now sends out emails with the complete LS based on what is entered into the Datatracker and that will go to the 3GPP secretariat. So I think there might be need to have a bit discussion with the tools people here if what we send out should be written into a PDF or something in a structured way, or if there are some intermediate step that doesn't send out the LS before it has been put into a form that the receiver body will find acceptable.

Cheers

Magnus

_______________________________________________
3gpp-ietf-coord mailing list
[e-mail]<mailto:[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.