IETF Logo Mail Archive

Re: [MMUSIC] IETF#89: BUNDLE: Q12: Scope of non-RTP media de-mux procedures in BUNDLE?

Christer Holmberg <christer.holmberg@ericsson.com> Mon, 03 March 2014 05:50 UTC

Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ECF691A0BA2 for <mmusic@ietfa.amsl.com>; Sun, 2 Mar 2014 21:50:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.24
X-Spam-Level:
X-Spam-Status: No, score=-1.24 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, HOST_MISMATCH_NET=0.311, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oUY6opxO3LkZ for <mmusic@ietfa.amsl.com>; Sun, 2 Mar 2014 21:50:47 -0800 (PST)
Received: from sessmg20.mgmt.ericsson.se (sessmg20.ericsson.net [193.180.251.50]) by ietfa.amsl.com (Postfix) with ESMTP id EFC391A0B91 for <mmusic@ietf.org>; Sun, 2 Mar 2014 21:50:46 -0800 (PST)
X-AuditID: c1b4fb32-b7f4c8e0000012f5-41-53141832d32e
Received: from ESESSHC020.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg20.mgmt.ericsson.se (Symantec Mail Security) with SMTP id 6D.8F.04853.23814135; Mon, 3 Mar 2014 06:50:43 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.216]) by ESESSHC020.ericsson.se ([153.88.183.78]) with mapi id 14.02.0387.000; Mon, 3 Mar 2014 06:50:42 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] IETF#89: BUNDLE: Q12: Scope of non-RTP media de-mux procedures in BUNDLE?
Thread-Index: Ac82MKMUCOeiYc5PSXK9YNe83HDvFwAGwP2AAAI4pFAAAG5CgAATgQ7w
Date: Mon, 03 Mar 2014 05:50:41 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D1C5524@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D1C4C88@ESESSMB209.ericsson.se> <5313912D.9020202@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D1C4F63@ESESSMB209.ericsson.se> <5313A2F9.6000507@alum.mit.edu>
In-Reply-To: <5313A2F9.6000507@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [153.88.183.150]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrMLMWRmVeSWpSXmKPExsUyM+Jvja6xhEiwwfvl3BZTlz9msVix4QCr A5PH3/cfmDyWLPnJFMAUxWWTkpqTWZZapG+XwJUx5+setoLlLBXNC76xNDCuYu5i5OSQEDCR OPOnmxXCFpO4cG89WxcjF4eQwAlGietb5zNDOIsZJfoXr2fsYuTgYBOwkOj+pw3SICLgK/Hs 8W02EFtYIFHiyfxT7BDxJImWP9+YIGw3iTfLL4PFWQRUJH5M/AG2mBeo9+3tFhaI+VcZJS6d 3APWwCmgI7F453QWEJsR6KLvp9aAxZkFxCVuPZnPBHGpgMSSPeehPhCVePn4H9QHShIrtl9i hKjXkViw+xMbhK0tsWzha6jFghInZz5hmcAoOgvJ2FlIWmYhaZmFpGUBI8sqRsni1OLi3HQj A73c9NwSvdSizOTi4vw8veLUTYzAiDm45bfRDsaTe+wPMUpzsCiJ815nrQkSEkhPLEnNTk0t SC2KLyrNSS0+xMjEwSnVwGg+V9PhlZu4hNmVvEbH5+rNeqprzv1/Ih0kOtVp+Y0GzXksM9ql breKzbV/Ymb1aG/rs/pzLVfPK7D9d91dJK8rZ74ubuebaf1z1J9oG2RM+Cws8Phe7I6a74XO 3mcV15kdq/E7w3bb9ZGJzfyUTkGzM+rWnDtr6lbu6yvzWKYZfbRbaPuXc0osxRmJhlrMRcWJ ABzF83BmAgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/7g4a0MNflx5B7qJVi6ULlvghZq0
Subject: Re: [MMUSIC] IETF#89: BUNDLE: Q12: Scope of non-RTP media de-mux procedures in BUNDLE?
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic/>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Mar 2014 05:50:48 -0000

Hi,

> I'm not necessarily opposed to going in the direction you suggest.
> (I'm still listening to what others have to say before deciding.)
>
> But if we go that way then I think the bundle draft needs a big warning or implementers note 
> explaining the issues involved in this.

Yes.

> And then I expect that there ought to be an rtcweb document that specifies how to do this for the 
> common rtcweb cases.

Isn't DTLS/SRTP/STUN, which we will cover in the BUNDLE spec, the common rtcweb case?

Regards,

Christer

v2.23.0 | Report a Bug | By Email