Re: [MMUSIC] Reviving draft-ietf-mmusic-msrp-usage-data-channel

[Christer Holmberg <[e-mail]>]

>> As part of that process, the chairs would like to see a reasonable level of interest and contributions from more than just a couple of people. Indeed.
 >
>One of the main reasons to complete this work is that it is referenced and reused in a 3GPP specification (TS 24.371 “Web Real-Time Communications (WebRTC) access to the IP Multimedia (IM) >Core Network (CN) subsystem (IMS); Stage 3; Protocol specification” https://www.etsi.org/deliver/etsi_ts/124300_124399/124371/15.00.00_60/ts_124371v150000p.pdf ).
>
>As a result, a number of companies having implemented this specification may be interested to see the draft standardized.

Things don’t just “get standardized” – actual people need to do the work. That applies to IETF, 3GPP and every other SDO out there 😊

>The good news is that the draft was successfully implemented and that it should not be far from completion.

That’s what I was told when I took over ICEbis… 😊

Seriously, I personally think it’s great if someone wants to finalize this. However, I hope that the new editors haven’t agreed to the task based on an assumption that “it should not be far from completion”. Maybe that will be the case, but one always have to assume that issues may come up.

>The death of the draft was likely due to the imperfect coordination between IETF and 3GPP spec streams, along with the natural movement of authors.
>It could have been avoided, but it is fixable.

There was nothing wrong with the coordination. Everyone in IETF knew the draft was an 3GPP dependency. The problem was that there was nobody willing to finalize it.

Regards,

Christer




From: mmusic <[e-mail]> On Behalf Of Flemming Andreasen
Sent: Monday, March 11, 2019 7:45 PM
To: Christer Holmberg <[e-mail]>; Makaraju, Raju (Nokia - US/Naperville) <[e-mail]>; [e-mail]; [e-mail]
Subject: Re: [MMUSIC] Reviving draft-ietf-mmusic-msrp-usage-data-channel

That is correct. As part of that process, the chairs would like to see a reasonable level of interest and contributions from more than just a couple of people.

Thanks

-- Flemming (with chair hat on)
On 3/11/19 2:08 PM, Christer Holmberg wrote:
Hi,

As far as I understand, the WG will have to agree to continue the work, as the draft has been declared “dead” and removed from the list of deliverables.

Regards,

Christer

From: mmusic <[e-mail]><mailto:[e-mail]> on behalf of "Makaraju, Raju (Nokia - US/Naperville)" <[e-mail]><mailto:[e-mail]>
Date: Monday, 11 March 2019 at 15.44
To: "[e-mail]"<mailto:[e-mail]> <[e-mail]><mailto:[e-mail]>, "[e-mail]"<mailto:[e-mail]> <[e-mail]><mailto:[e-mail]>
Subject: [MMUSIC] Reviving draft-ietf-mmusic-msrp-usage-data-channel

All,
After a pause, we are putting renewed efforts to revive, resume draft-ietf-mmusic-msrp-usage-data-channel<https://datatracker.ietf.org/doc/draft-ietf-mmusic-msrp-usage-data-channel/> and complete the document to make it as an RFC.
This document is complete for the most part with some remaining comments, alignment with drafts/RFCs it refers to to be incorporated.
3gpp refers to this draft for MSRP over data channels interworking with MSRP/TLS (or TCP) and Nokia has an active implementation on as part of 3gpp ePCSCF based on this draft as well for this. Without reviving this draft 3gpp will remove the reference, but sooner or later an equivalent draft may have to be written (thus need to start fresh).

Julien will be representing Nokia for this draft while Jose M Recio <[e-mail]<mailto:[e-mail]>>  (thank you both!) and I will be providing  support for the technical discussion and most of the technical updates to the draft.

As usual, please provide your comments, concerns on this revival.

Thanks for your support!
Raju





_______________________________________________

mmusic mailing list

[e-mail]<mailto:[e-mail]>

https://www.ietf.org/mailman/listinfo/mmusic