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

"Maisonneuve, Julien (Nokia - FR/Paris-Saclay)" <> Tue, 12 March 2019 09:19 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 559AC130F20; Tue, 12 Mar 2019 02:19:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=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 xVUZ8SaGiFDI; Tue, 12 Mar 2019 02:19:02 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 518951310CB; Tue, 12 Mar 2019 02:19:01 -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=GgUz5ZM+3Le75d4sfrMVCvs5QO9x475lFE6QZaNPaqY=; b=JEdAUNUBqX8oDPx+fMzQIB1FNGk/x0lbu330kkuuIEeX/iQ3VzO32D5OLvRokXTM4L8kE8TEdOgWRKDqhyd+hL2E9fHnvqduo/ZHbW5iQkr2DqUAqO8AgoY58TjZJJdukdnFocArue8S7jNtOctktnKMg/kRkpoq0HuqucAR398=
Received: from ( by ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1709.13; Tue, 12 Mar 2019 09:18:58 +0000
Received: from ([fe80::e418:f972:6526:7e36]) by ([fe80::e418:f972:6526:7e36%2]) with mapi id 15.20.1709.011; Tue, 12 Mar 2019 09:18:58 +0000
From: "Maisonneuve, Julien (Nokia - FR/Paris-Saclay)" <>
To: Flemming Andreasen <>, Christer Holmberg <>, "Makaraju, Raju (Nokia - US/Naperville)" <>, "" <>, "" <>
Thread-Topic: [MMUSIC] Reviving draft-ietf-mmusic-msrp-usage-data-channel
Thread-Index: AQHU2DVgLOqmRnA70kON+TtfZFDXbaYGxK4AgAAc5cA=
Date: Tue, 12 Mar 2019 09:18:58 +0000
Message-ID: <>
References: <> <>
In-Reply-To: <>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: yes
x-originating-ip: []
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 054e79eb-41a8-4ed3-a12b-08d6a6cbc242
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)(49563074)(7193020); SRVR:DB6PR07MB3094;
x-ms-traffictypediagnostic: DB6PR07MB3094:
x-ms-exchange-purlcount: 4
x-microsoft-antispam-prvs: <>
x-forefront-prvs: 09749A275C
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(366004)(136003)(376002)(396003)(39860400002)(346002)(189003)(199004)(66066001)(6346003)(102836004)(26005)(81166006)(110136005)(8676002)(81156014)(316002)(606006)(76176011)(7696005)(99286004)(186003)(229853002)(6506007)(53546011)(5660300002)(6436002)(8936002)(105586002)(106356001)(74316002)(52536013)(7736002)(25786009)(2906002)(68736007)(6116002)(790700001)(33656002)(55016002)(3846002)(236005)(2201001)(86362001)(6306002)(54896002)(9686003)(6246003)(97736004)(99936001)(53936002)(2501003)(256004)(14444005)(14454004)(478600001)(11346002)(486006)(71200400001)(476003)(71190400001)(966005)(446003); DIR:OUT; SFP:1102; SCL:1; SRVR:DB6PR07MB3094;; 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: LzN+ABb6uUZsTL7uenV9k0hUbclJngwfn70eOOZfltE3dFkFVxgi/u5GJKwjHSmtnw6HeP0isoy0gdBofrSJAvpvLpDWfbvYU3/jopKEkIWJVxFY0Qz1v42wU5Vixj8ICIguto1rrGTDNhQOGnyKV4rEoVXpRnd/vXYu4R4JD8Sc+O/EkjtpsswCtQuDKwSO9R72Dwgo7J1CsspEqcaAqadcbVFdUMEjswLHoWdUWvJkE14YW7Dpduq19NYsmJSV+Mte/wA7ZVS4ReLzwiYtScOKhuMTKtNE708KDeeE2QV+s4kzslWI3d44V2BtNd7mfPUEBBLF8zr27Gp3xI8DohCB0OfyNpuUIVx1PIkTxBkOAJCOKWCarkkmyhYuZffZHixlMbO1fUSMc653+nlBx/UGBe5Ay60qfla+bd8uv6c=
Content-Type: multipart/mixed; boundary="_004_DB6PR07MB3464B352C298C4F8463D87EA92490DB6PR07MB3464eurp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 054e79eb-41a8-4ed3-a12b-08d6a6cbc242
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Mar 2019 09:18:58.5821 (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: DB6PR07MB3094
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: Tue, 12 Mar 2019 09:19:12 -0000

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

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.
The good news is that the draft was successfully implemented and that it should not be far from completion.

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.

What is needed now is a few reviews to identify whether is reasonably complete and can move forward.
Thanks for your attention.

Best regards,
Julien Maisonneuve, Nokia Corporate Standards.

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<>

--- Begin Message ---
Windows 10 upgrade to release 1709

Your computer account for PC N-5CG6190CKK has been disabled

Distribution: Employees and external resources with a Nokia Windows 10 PC still running windows 10 1607

Dear User of IT services,

The computer account for your inactive PC N-5CG6190CKK has been disabled and the PC can no longer connect to the Nokia network.  This action was taken because the PC is running an old version of Windows 10 that is not secure.

If this PC does need to access the Nokia network, you can create a service desk ticket to request that the account is re-enabled for a 2 week period to allow you to upgrade to Windows 10 release 1709.  If after the 2 weeks the PC is still running Windows 10 1607, the computer account will be disabled again.

More information

*       Check the Windows 10 upgrade to release 1709 user guide<> for details
*       Read more on the Windows 10 update service page<>
*       Join the discussion and check for updates in our Yammer group<>
*       For IT support turn to IT Service Desk<>

Best regards,
Nokia IT

© Nokia 2018

--- End Message ---