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

"Henrikson, Eric (Nokia - US)" <> Wed, 20 March 2019 19:49 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id AD3C513106E for <>; Wed, 20 Mar 2019 12:49:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 8_FAteK808MS for <>; Wed, 20 Mar 2019 12:49:13 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 187D112008F for <>; Wed, 20 Mar 2019 12:49:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=selector1-nokia-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=DJj4IqdNM+cKlSu8I3evbTUg0HnhcGkJnDjsCJ4mVmE=; b=B0loU+difSdi5ulCcqbdi58q75MANELPRnvD7e+yHis12m5Pakij1A/hWqw18Fia3jCcw8jfGZSHs7cZ473zFfVgNDLV0jRH56qMukk1/j2bHbT4J5r4WUgsY2Iw9+1FMk3/BzwjBTYZL0a+diq+I/lUqWxNKm13S/LGAM+I4hk=
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1709.16; Wed, 20 Mar 2019 19:49:10 +0000
Received: from ([fe80::504d:de80:689c:21e0]) by ([fe80::504d:de80:689c:21e0%6]) with mapi id 15.20.1709.015; Wed, 20 Mar 2019 19:49:10 +0000
From: "Henrikson, Eric (Nokia - US)" <>
To: "" <>
Thread-Topic: Reviving draft-ietf-mmusic-msrp-usage-data-channel
Thread-Index: AdTfVVOKj9Ru2Y4uSZ627n2xL0IwHw==
Date: Wed, 20 Mar 2019 19:49:10 +0000
Message-ID: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 865d48eb-458c-47af-b050-08d6ad6d1f03
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600127)(711020)(4605104)(4618075)(2017052603328)(7193020); SRVR:AM6PR07MB5974;
x-ms-traffictypediagnostic: AM6PR07MB5974:
x-ms-exchange-purlcount: 4
x-microsoft-antispam-prvs: <>
x-forefront-prvs: 098291215C
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(366004)(376002)(346002)(39860400002)(136003)(396003)(189003)(199004)(13464003)(27574002)(33656002)(14454004)(81166006)(8936002)(486006)(71190400001)(6436002)(1730700003)(52536014)(54906003)(68736007)(229853002)(71200400001)(4326008)(966005)(99286004)(81156014)(6246003)(6916009)(478600001)(74316002)(66066001)(8676002)(9686003)(6116002)(6506007)(25786009)(305945005)(97736004)(316002)(256004)(14444005)(107886003)(2351001)(105586002)(102836004)(7696005)(53546011)(26005)(53936002)(86362001)(5660300002)(186003)(476003)(6306002)(5024004)(7736002)(106356001)(2906002)(55016002)(3846002)(6346003)(2501003)(5640700003); DIR:OUT; SFP:1102; SCL:1; SRVR:AM6PR07MB5974;; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None ( does not designate permitted sender hosts)
authentication-results: spf=none (sender IP is );
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: EruLdUWV/Oa66eP1n8vfN7TAPa1qmDKZFvtWlxe1tXZRRyAZ/XfBY0i8lZOksz61PQA6dpeGKsWKZe0UEcYIFbZr236P+9N+bG+KMioI8fwniU2x/b4dgxsLSRURU6IH7mSBJSMQoX2qtvDSYE3GESXKF5BrnbW82I2ow/iyzd1Ipa6ckkGGYhAL+Z2Ep4FB36I4vq1R7FbtDn1tZ+nPzEt/+TU4VgQTJr5qXPZdmKh3MLbZCWfcVz7tPWOAi/hdzQzo66JiChgmL5/1Jm7y1XNYFtMEIgoV9WTFvmrrON+H0PSOI3rHKl1zUSFCr9YJ0YA6xJSdeOZosLVKpNOLfgpLhpDHpDyMgOb+4Zls1UHWhGeaiigqKETwKOQR8+F6BVGLpUGkm+HZzGyVZiYzvIyrfzLTDZQL4nLf3Mbr+xI=
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 865d48eb-458c-47af-b050-08d6ad6d1f03
X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Mar 2019 19:49:10.1318 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM6PR07MB5974
Archived-At: <>
Subject: Re: [MMUSIC] Reviving draft-ietf-mmusic-msrp-usage-data-channel
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 20 Mar 2019 19:52:02 -0000


I support reviving the work for draft-ietf-mmusic-msrp-usage-data-channel.  I will review it.

Eric Henrikson

-----Original Message-----
From: mmusic <> On Behalf Of
Sent: Tuesday, March 12, 2019 4:30 AM
Subject: mmusic Digest, Vol 179, Issue 10

Send mmusic mailing list submissions to

To subscribe or unsubscribe via the World Wide Web, visit
or, via email, send a message with subject or body 'help' to

You can reach the person managing the list at

When replying, please edit your Subject line so it is more specific than "Re: Contents of mmusic digest..."

Today's Topics:

   1. Re: Reviving draft-ietf-mmusic-msrp-usage-data-channel
      (Christer Holmberg)


Message: 1
Date: Tue, 12 Mar 2019 09:30:07 +0000
From: Christer Holmberg <>
To: "Maisonneuve, Julien (Nokia - FR/Paris-Saclay)"
	<>om>, Flemming Andreasen
	<>om>, "Makaraju, Raju (Nokia - US/Naperville)"
	<>om>, ""
	<>rg>, "" <>
Subject: Re: [MMUSIC] Reviving
Message-ID: <>
Content-Type: text/plain; charset="utf-8"

>> 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? ).
>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.



From: mmusic <> On Behalf Of Flemming Andreasen
Sent: Monday, March 11, 2019 7:45 PM
To: Christer Holmberg <>om>; Makaraju, Raju (Nokia - US/Naperville) <>om>;;
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.


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

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.



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

After a pause, we are putting renewed efforts to revive, resume 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 <<>>  (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!


mmusic mailing list<>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>


Subject: Digest Footer

mmusic mailing list


End of mmusic Digest, Vol 179, Issue 10