
From nobody Sat Mar  1 02:06:04 2014
Return-Path: <emcho@sip-communicator.org>
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 5204D1A0903 for <mmusic@ietfa.amsl.com>; Sat,  1 Mar 2014 02:06:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 FceKglATu7zF for <mmusic@ietfa.amsl.com>; Sat,  1 Mar 2014 02:06:00 -0800 (PST)
Received: from mail-ea0-f171.google.com (mail-ea0-f171.google.com [209.85.215.171]) by ietfa.amsl.com (Postfix) with ESMTP id 1F74B1A0900 for <mmusic@ietf.org>; Sat,  1 Mar 2014 02:05:59 -0800 (PST)
Received: by mail-ea0-f171.google.com with SMTP id n15so1757213ead.16 for <mmusic@ietf.org>; Sat, 01 Mar 2014 02:05:57 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=elyzsWLBTNl7OHXAy5Ye5GzQSJ9Vo5kldYY0nRR9AZE=; b=baTFAF+aKGpU2XbhjKQ+SN5cWdYLAvc4V4ax729ywbHvhGPEBlD5RFeLmQJkjL8Aom fBCeUQUdnfC4ikKERocz/f17paH2EXTmNQZ7YZGxdFlOotqcqWFG8LTXDhn/1uK5wIuV cnAjrz+PFl/ouEp83ViJKwxe0F9br6Z1zBzxkzWp0Wk1ViAh7Odq4OfpILa5Qair6um9 6VsbAnsfps5gnZaGx4fGKo0vBEAZ8FMVKloMKGOZWCq+mp/Q1SdSm+cypL6cCrgpG+wi MOHGXGjEa04oAl0KoIWzs0VrpXWUJ+nQT5ZEKgpRlZi/ErLWjTmZ5qQYa88GVuInJrgS TL3A==
X-Gm-Message-State: ALoCoQkaQk3S3LvqKus/o3jBLZ7++oCmqotYl9LTgidTqU0x9+zyN3RcfFz0Tcu8casvoIHVX4Y4
X-Received: by 10.14.216.193 with SMTP id g41mr27476390eep.13.1393668356958; Sat, 01 Mar 2014 02:05:56 -0800 (PST)
Received: from [192.168.43.67] ([212.5.158.93]) by mx.google.com with ESMTPSA id x6sm21531688eew.20.2014.03.01.02.05.50 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 01 Mar 2014 02:05:51 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Emil Ivov <emcho@jitsi.org>
In-Reply-To: <530EAED1.7090609@alvestrand.no>
Date: Sat, 1 Mar 2014 12:05:48 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <69B22B83-A3B8-4B67-8C07-DE4A0A7728B5@jitsi.org>
References: <52FEAA17.9070406@nostrum.com> <53014BFC.3070406@alum.mit.edu> <530EAED1.7090609@alvestrand.no>
To: Harald Alvestrand <harald@alvestrand.no>
X-Mailer: Apple Mail (2.1827)
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/nerDj6rm7AlB5MMDbO5R8dk5teY
Cc: mmusic@ietf.org
Subject: Re: [MMUSIC] POF/PAN draft update - move BUNDLE-specific stuff to bundle draft
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: Sat, 01 Mar 2014 10:06:02 -0000

On 27.02.2014, at 05:19, Harald Alvestrand <harald@alvestrand.no> wrote:

> On 02/17/2014 12:38 AM, Paul Kyzivat wrote:
>> Another comment on this draft:
>>=20
>> While the mechanism described in this draft is strongly motivated by
>> BUNDLE, it is conceptually independent of BUNDLE. IMO all the
>> BUNDLE-specific behavior should be removed from this draft, and
>> instead placed into the BUNDLE draft.
>>=20
>> I realize there is a chicken/egg thing here. It would make sense to
>> keep the bundle-specifics here, so they don't get forgotten, until
>> they are incorporated into the bundle draft.
>=20
> If moving the BUNDLE-specific stuff to the BUNDLE draft means that
> BUNDLE is dependent on completion of POF/PAN before considered
> completed, I'm strongly opposed to this.
>=20
> BUNDLE should not depend on POF/PAN. If BUNDLE-specific aspects of
> POF/PAN need to be broken out, there needs to be a third draft that
> references both.

Agreed! I don't believe everyone implementing BUNDLE would be interested =
in POF/PAN and I am not convinced that the lives of the two specs would =
continue evolving together with the same pace. A third =
bundle-with-pof-pan sounds most reasonable here

Emil
=20
>=20
>=20
>>=20
>>    Thanks,
>>    Paul
>>=20
>>=20
>> On 2/14/14 6:43 PM, Adam Roach wrote:
>>> I've updated the partial offer/partial answer draft to reflect the
>>> conversations we had in Vancouver:
>>> http://tools.ietf.org/html/draft-roach-mmusic-pof-pan-02
>>>=20
>>> Diffs:
>>> http://tools.ietf.org/rfcdiff?url2=3Ddraft-roach-mmusic-pof-pan-02.txt=

>>>=20
>>> Note that this relies on the following draft for group membership
>>> manipulation:
>>> http://tools.ietf.org/html/draft-roach-mmusic-groupid
>>>=20
>>> Please point out whether you think I've missed any of the Vancouver
>>> discussions or other feedback. Thanks!
>>>=20
>>> /a
>>>=20
>>>=20
>>> _______________________________________________
>>> mmusic mailing list
>>> mmusic@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mmusic
>>>=20
>>=20
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www.ietf.org/mailman/listinfo/mmusic
>=20
>=20
> --=20
> Surveillance is pervasive. Go Dark.
>=20
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic

--=20
https://jitsi.org


From nobody Sat Mar  1 02:08:49 2014
Return-Path: <emcho@sip-communicator.org>
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 36D0F1A0901 for <mmusic@ietfa.amsl.com>; Sat,  1 Mar 2014 02:08:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.301
X-Spam-Level: 
X-Spam-Status: No, score=-2.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 m9FKzgqXMfl0 for <mmusic@ietfa.amsl.com>; Sat,  1 Mar 2014 02:08:46 -0800 (PST)
Received: from mail-ea0-f175.google.com (mail-ea0-f175.google.com [209.85.215.175]) by ietfa.amsl.com (Postfix) with ESMTP id 699B81A08FD for <mmusic@ietf.org>; Sat,  1 Mar 2014 02:08:46 -0800 (PST)
Received: by mail-ea0-f175.google.com with SMTP id d10so99695eaj.20 for <mmusic@ietf.org>; Sat, 01 Mar 2014 02:08:43 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=sW4zs1KvtOxvgY19ZNhbgMjYczgWhzKkTyQVpOEVHzI=; b=AervhzTvHR6Q+shzYTEK140/h+GEqQvydvdM3Ifg+P03VyD4LnIX3OqpYD4Y8meAhU mToVEBv/SA/H6hKiibdOLv3egFU+NlTbTdmiSO+OShQvRzKozS5r06bpjSWnmlmcfqQK A1w1DCbb1KWxHvJbo1sjGsQ0DqgQs/Qg0E3g5PYSihl6tCGElgOaHzfvmbWy3V2XcI5m G2Oe69sIZhY7WSzpQlue2Wuhp2GZ6H8dhcRBw0Inou3VXWhk57iFrbZKNbWYhmUCi2N4 CSbtMcv06q1tGQO+Lk815RZrx2EJf5Zp3mjxWl/Hv4rm3U/TZ1FYJ/CWg53iskzU3wQy yucw==
X-Gm-Message-State: ALoCoQm8EE2cagHoergWT3orj/UGCXO0ZFxUKV/XEHMYIcMQfcxVflnZOqGgC5HdlrIJOt0LYV4W
X-Received: by 10.15.56.130 with SMTP id y2mr27355720eew.17.1393668523786; Sat, 01 Mar 2014 02:08:43 -0800 (PST)
Received: from [192.168.43.67] ([212.5.158.93]) by mx.google.com with ESMTPSA id 46sm21598970ees.4.2014.03.01.02.08.39 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 01 Mar 2014 02:08:40 -0800 (PST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Emil Ivov <emcho@jitsi.org>
In-Reply-To: <5310B236.7050108@ericsson.com>
Date: Sat, 1 Mar 2014 12:08:38 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <25289CDD-23B0-4060-A12B-EE9F7CCD64F3@jitsi.org>
References: <5310B236.7050108@ericsson.com>
To: =?iso-8859-1?Q?Ari_Ker=E4nen?= <ari.keranen@ericsson.com>
X-Mailer: Apple Mail (2.1827)
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/NFvzZ5mFJOuSv0fQXkfxS6t8K0k
Cc: mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] ICE options: need new optional and/or required attributes?
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: Sat, 01 Mar 2014 10:08:48 -0000

On 28.02.2014, at 17:58, Ari Ker=E4nen <ari.keranen@ericsson.com> wrote:

> Hi all,
>=20
> One open issue regarding ICE-bis has been the semantics of the =
ice-options attribute. Currently there is no way of saying "do =
aggressive ICE even if you don't understand this option" or "reject my =
offer if you don't understand this option".
>=20
> One way of solving this would be to introduce a new attribute like:
>=20
> a=3Dice-options-required:foo
>=20
> That is, if "foo" is unknown option to the answerer, the offer is =
rejected. In addition to solving the second case, it could also be used =
to test for the first and if option was not understood, simply leave it =
out of the new offer. Of course this would result in one signaling =
exchange of delay, and hence for the first case (do still aggressive) we =
could also introduce yet another option:
>=20
> a=3Dice-options-optional:bar

I don't have a strong opinion on this but the latter seems to be the =
only one offering consistency with existing implementations.

Emil

>=20
> Opinions?
>=20
>=20
> Cheers,
> Ari
>=20
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic

--=20
https://jitsi.org


From nobody Sat Mar  1 16:55:48 2014
Return-Path: <ari.keranen@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 CE5681A0B43 for <mmusic@ietfa.amsl.com>; Sat,  1 Mar 2014 16:55:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.551
X-Spam-Level: 
X-Spam-Status: No, score=-3.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 cVOPNmizl4QQ for <mmusic@ietfa.amsl.com>; Sat,  1 Mar 2014 16:55:45 -0800 (PST)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id DA1E11A02F1 for <mmusic@ietf.org>; Sat,  1 Mar 2014 16:55:44 -0800 (PST)
X-AuditID: c1b4fb2d-b7f5d8e000002a7b-19-5312818da36f
Received: from ESESSHC014.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 7D.F9.10875.D8182135; Sun,  2 Mar 2014 01:55:41 +0100 (CET)
Received: from mail.lmf.ericsson.se (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.62) with Microsoft SMTP Server id 14.2.347.0; Sun, 2 Mar 2014 01:55:41 +0100
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se [131.160.33.3])	by mail.lmf.ericsson.se (Postfix) with ESMTP id 527531101F3; Sun,  2 Mar 2014 02:55:41 +0200 (EET)
Received: from nomadiclab.lmf.ericsson.se (localhost [127.0.0.1])	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 48FA456B22;	Sun,  2 Mar 2014 02:55:36 +0200 (EET)
Received: from As-MacBook-Air.local (localhost [127.0.0.1])	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id CD46751706;	Sun,  2 Mar 2014 02:55:35 +0200 (EET)
Message-ID: <5312818A.9010705@ericsson.com>
Date: Sun, 2 Mar 2014 00:55:38 +0000
From: =?ISO-8859-1?Q?Ari_Ker=E4nen?= <ari.keranen@ericsson.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Emil Ivov <emcho@jitsi.org>
References: <5310B236.7050108@ericsson.com> <25289CDD-23B0-4060-A12B-EE9F7CCD64F3@jitsi.org>
In-Reply-To: <25289CDD-23B0-4060-A12B-EE9F7CCD64F3@jitsi.org>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrALMWRmVeSWpSXmKPExsUyM+JvjW5vo1CwweOdZhZrdk5gsbh25h+j xdTlj1kcmD12zrrL7rFkyU8mj/9vAgOYo7hsUlJzMstSi/TtErgyvhx9xF5wgKti4u2HbA2M ezm6GDk5JARMJDbPn8QKYYtJXLi3nq2LkYtDSOAQo8TdSU3sEM56Rokf6/dAZfYwSuxf/xMq s5ZRonfDb0YIZzmjRFdDD9AwDg5eAW2J7lWpIHNZBFQkpsy8yA5iswnYS9yccB3MFhVIlrj5 /TMbiM0rIChxcuYTFhBbREBeorttEROIzSzgLnFxVz9YjbBAgMTJPxfBbCGBGImf99+A1XAK 2Eosaz3KCFFvK3FhznUWCFteonnrbGaI39Qkrp7bxAzRqypx9d8rxgmMorOQrJ6FpH0WkvYF jMyrGNlzEzNz0ssNNzECY+Hglt+6OxhPnRM5xCjNwaIkzvvhrXOQkEB6YklqdmpqQWpRfFFp TmrxIUYmDk6pBkbBKunyLo+Knx5nVigonf27bZPn/nOPN/Xw3hV2VWdeUix/+I0+X77QjFWz hBOV3l9eyXh+6xY/t4scKw2mMsyr/3zBaYJpk0936GSZxP+Ce3SVJl7bacix+ZAKg0i2c23D k/dRm++0bl/RYssWcSUhw8UxcW7v5EcqvJI6eZEioi81T/+55KTEUpyRaKjFXFScCAA+SLN0 UwIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/x-K2s6EV-mF-EWRrHsiRorolSmQ
Cc: mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] ICE options: need new optional and/or required attributes?
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: Sun, 02 Mar 2014 00:55:47 -0000

On 3/1/14 10:08 AM, Emil Ivov wrote:
>
> On 28.02.2014, at 17:58, Ari Keränen <ari.keranen@ericsson.com> wrote:
>
>> Hi all,
>>
>> One open issue regarding ICE-bis has been the semantics of the ice-options attribute. Currently there is no way of saying "do aggressive ICE even if you don't understand this option" or "reject my offer if you don't understand this option".
>>
>> One way of solving this would be to introduce a new attribute like:
>>
>> a=ice-options-required:foo
>>
>> That is, if "foo" is unknown option to the answerer, the offer is rejected. In addition to solving the second case, it could also be used to test for the first and if option was not understood, simply leave it out of the new offer. Of course this would result in one signaling exchange of delay, and hence for the first case (do still aggressive) we could also introduce yet another option:
>>
>> a=ice-options-optional:bar
>
> I don't have a strong opinion on this but the latter seems to be the only one offering consistency with existing implementations.

Do you mean that existing implementations ignore unknown options and 
still do aggressive ICE?

The first one, understand or fail, is what Martin Thomson requested at 
the previous meeting. With that you can actually accomplish both, but 
with some penalty.


Cheers,
Ari


From nobody Sat Mar  1 17:18:22 2014
Return-Path: <emcho@sip-communicator.org>
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 804161A0B43 for <mmusic@ietfa.amsl.com>; Sat,  1 Mar 2014 17:18:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.679
X-Spam-Level: 
X-Spam-Status: No, score=-1.679 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-0.7, 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 NQo-QON8Wytj for <mmusic@ietfa.amsl.com>; Sat,  1 Mar 2014 17:18:18 -0800 (PST)
Received: from mail-ve0-f176.google.com (mail-ve0-f176.google.com [209.85.128.176]) by ietfa.amsl.com (Postfix) with ESMTP id B47BA1A0319 for <mmusic@ietf.org>; Sat,  1 Mar 2014 17:18:18 -0800 (PST)
Received: by mail-ve0-f176.google.com with SMTP id cz12so2308279veb.21 for <mmusic@ietf.org>; Sat, 01 Mar 2014 17:18:16 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=VIRRJsB0JU4hcshADEeIAd0Xuog98Hlb7vMJ4QLf+xk=; b=JYO4cXnkq1ERbULFd/wh08+HC19CbVWM1N2sZt8V8tUtud/WAsI2PoiiiItz3yGIHI K2vpyjMknW5CyRwPBeMAl8+DJJg2ezcwpqdikHlZzo6GAX1NzaOL9Mx4nKqsHt8mVr9O 5IjWauHTwb9QCNSK9+mVGH0LRD61QWiluk4xk6eB8TZlE3dr1xU5qEBvo9lRkXK9Qn3F jdh+XnCjjHtHUqj+ghrQt+6gd/MmBPG0RqY1N9q5dQevun3xtw6cSAoDgf+GKafWpxAW 6vCIgMhMeCVSLyzkCB9J0p5uFSDn0HIE/BncHp0xbJlRztLjb/nJaXnZghbcDro5W8wr MjZQ==
X-Gm-Message-State: ALoCoQn+kZj35h/K/2W22xeJpZdfnUPadZ6f+luPikanrd4z/S0yv9vxbliyL0CdthquqbxzruP9
X-Received: by 10.220.188.10 with SMTP id cy10mr57547vcb.36.1393723096206; Sat, 01 Mar 2014 17:18:16 -0800 (PST)
Received: from mail-ve0-f176.google.com (mail-ve0-f176.google.com [209.85.128.176]) by mx.google.com with ESMTPSA id ay4sm21642872vdb.4.2014.03.01.17.18.15 for <mmusic@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 01 Mar 2014 17:18:15 -0800 (PST)
Received: by mail-ve0-f176.google.com with SMTP id cz12so2308273veb.21 for <mmusic@ietf.org>; Sat, 01 Mar 2014 17:18:15 -0800 (PST)
X-Received: by 10.52.179.198 with SMTP id di6mr19917366vdc.7.1393723095650; Sat, 01 Mar 2014 17:18:15 -0800 (PST)
MIME-Version: 1.0
Received: by 10.220.191.130 with HTTP; Sat, 1 Mar 2014 17:17:55 -0800 (PST)
In-Reply-To: <5312818A.9010705@ericsson.com>
References: <5310B236.7050108@ericsson.com> <25289CDD-23B0-4060-A12B-EE9F7CCD64F3@jitsi.org> <5312818A.9010705@ericsson.com>
From: Emil Ivov <emcho@jitsi.org>
Date: Sun, 2 Mar 2014 01:17:55 +0000
Message-ID: <CAPvvaa+MiieyZxAUo50DyqxxKtG5ZxQ528syWT5AjOZYt7Vy_A@mail.gmail.com>
To: =?ISO-8859-1?Q?Ari_Ker=E4nen?= <ari.keranen@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/gTi6KfvHTGpvgLPl4XURk0h70OU
Cc: mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] ICE options: need new optional and/or required attributes?
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: Sun, 02 Mar 2014 01:18:20 -0000

On Sun, Mar 2, 2014 at 12:55 AM, Ari Ker=E4nen <ari.keranen@ericsson.com> w=
rote:
> On 3/1/14 10:08 AM, Emil Ivov wrote:
>>
>>
>> On 28.02.2014, at 17:58, Ari Ker=E4nen <ari.keranen@ericsson.com> wrote:
>>
>>> Hi all,
>>>
>>> One open issue regarding ICE-bis has been the semantics of the
>>> ice-options attribute. Currently there is no way of saying "do aggressi=
ve
>>> ICE even if you don't understand this option" or "reject my offer if yo=
u
>>> don't understand this option".
>>>
>>> One way of solving this would be to introduce a new attribute like:
>>>
>>> a=3Dice-options-required:foo
>>>
>>> That is, if "foo" is unknown option to the answerer, the offer is
>>> rejected. In addition to solving the second case, it could also be used=
 to
>>> test for the first and if option was not understood, simply leave it ou=
t of
>>> the new offer. Of course this would result in one signaling exchange of
>>> delay, and hence for the first case (do still aggressive) we could also
>>> introduce yet another option:
>>>
>>> a=3Dice-options-optional:bar
>>
>>
>> I don't have a strong opinion on this but the latter seems to be the onl=
y
>> one offering consistency with existing implementations.
>
> Do you mean that existing implementations ignore unknown options and stil=
l
> do aggressive ICE?

No, the opposite actually.

> The first one, understand or fail, is what Martin Thomson requested at th=
e
> previous meeting. With that you can actually accomplish both, but with so=
me
> penalty.

I might be misunderstanding the semantics you imply in
ice-options-optional and ice-options-requied so let's get that
clarified first:

Are you suggesting them as alternatives (which is what I thought you
meant) or that we adopt both of them together?

My point was that "ice-opitons-optional" fits nicely with what we have
right now. Trickle is a good example of how you could be lacking
support for an option and still be perfectly capable of nominating
aggressively.

I am a bit confused with "ice-options-required" because a) it kind of
overlaps with the SIP Requires header and b) I am not a big fan of
"let's try an offer *this* way and if it fails we'll try it *that*
way". This inevitably leads to the question "are we sure we actually
know why it failed?" (and the common answer "... eer ... not really".

Then again, I don't really mind that much. Still, if people have cases
where this is necessary, I'd be curious to hear them.

Cheers,
Emil

--=20
https://jitsi.org


From nobody Sat Mar  1 17:35:09 2014
Return-Path: <ari.keranen@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 1CA501A035F for <mmusic@ietfa.amsl.com>; Sat,  1 Mar 2014 17:35:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.601
X-Spam-Level: 
X-Spam-Status: No, score=-1.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, 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 SocS98YDgskK for <mmusic@ietfa.amsl.com>; Sat,  1 Mar 2014 17:35:04 -0800 (PST)
Received: from sesbmg20.ericsson.net (sesbmg20.ericsson.net [193.180.251.56]) by ietfa.amsl.com (Postfix) with ESMTP id 2D62C1A032E for <mmusic@ietf.org>; Sat,  1 Mar 2014 17:35:04 -0800 (PST)
X-AuditID: c1b4fb38-b7f418e000001099-bf-53128ac46b55
Received: from ESESSHC021.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg20.ericsson.net (Symantec Mail Security) with SMTP id 47.03.04249.4CA82135; Sun,  2 Mar 2014 02:35:01 +0100 (CET)
Received: from mail.lmf.ericsson.se (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.83) with Microsoft SMTP Server id 14.2.347.0; Sun, 2 Mar 2014 02:35:00 +0100
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se [131.160.33.3])	by mail.lmf.ericsson.se (Postfix) with ESMTP id BA6EF1101F3; Sun,  2 Mar 2014 03:35:00 +0200 (EET)
Received: from nomadiclab.lmf.ericsson.se (localhost [127.0.0.1])	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 74FC956B2B;	Sun,  2 Mar 2014 03:34:55 +0200 (EET)
Received: from As-MacBook-Air.local (localhost [127.0.0.1])	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id CF9AC56B17;	Sun,  2 Mar 2014 03:34:54 +0200 (EET)
Message-ID: <53128AC1.1050506@ericsson.com>
Date: Sun, 2 Mar 2014 01:34:57 +0000
From: =?ISO-8859-1?Q?Ari_Ker=E4nen?= <ari.keranen@ericsson.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Emil Ivov <emcho@jitsi.org>, Martin Thomson <martin.thomson@gmail.com>
References: <5310B236.7050108@ericsson.com> <25289CDD-23B0-4060-A12B-EE9F7CCD64F3@jitsi.org> <5312818A.9010705@ericsson.com> <CAPvvaa+MiieyZxAUo50DyqxxKtG5ZxQ528syWT5AjOZYt7Vy_A@mail.gmail.com>
In-Reply-To: <CAPvvaa+MiieyZxAUo50DyqxxKtG5ZxQ528syWT5AjOZYt7Vy_A@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrILMWRmVeSWpSXmKPExsUyM+Jvje7RLqFgg9aPHBZrdk5gsbh25h+j xdTlj1kcmD12zrrL7rFkyU8mj/9vAgOYo7hsUlJzMstSi/TtErgyDp56wVLQI1HRMHs9cwPj QuEuRk4OCQETiYvLLzBB2GISF+6tZwOxhQSOMEqcb7TsYuQCstczStx8PZkdwtnDKLH+yn5m CGcto8SF1R1QmeWMEncaNzGD9PMKaEt8+rcTaBYHB4uAisTsT3IgYTYBe4mbE66zg9iiAskS N79/ZoMoF5Q4OfMJC4gtIuAl8frAJ1YQm1lARmLG2Uaw84QFAiRO/rnIBrHrIKPEsxuXwIo4 BQIlHnU2QjXYSlyYc50FwpaXaN46mxniNzWJq+cgbhMSUJW4+u8V4wRG0VlIds9C0j4LSfsC RuZVjBzFqcVJuelGBpsYgdFwcMtvix2Ml//aHGKU5mBREuf9+NY5SEggPbEkNTs1tSC1KL6o NCe1+BAjEwenVANjwlMeH/6aO7e+ztx6TC31/b1/SwSfbXw0OUrj6W2rPTu79+1dzqx6O/jm XW7zU2xt6ZwBVW02ixNfcy6ddSaeJWpdJPPn1kX5PkJrypKbZTIKNjEzSzE8KE3hZ5kfmmpi e1p6m+LTEp3di99HtXC+zfm8a9b3q1vE/kY6+Du9Dp6okbuZ9XCKEktxRqKhFnNRcSIA7bVK 6lQCAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/hNofZoSrZF5fK7-0y2R_0vCYA8w
Cc: mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] ICE options: need new optional and/or required attributes?
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: Sun, 02 Mar 2014 01:35:06 -0000

On 3/2/14 1:17 AM, Emil Ivov wrote:
> On Sun, Mar 2, 2014 at 12:55 AM, Ari Keränen <ari.keranen@ericsson.com> wrote:
>> On 3/1/14 10:08 AM, Emil Ivov wrote:
>>>
>>>
>>> On 28.02.2014, at 17:58, Ari Keränen <ari.keranen@ericsson.com> wrote:
>>>
>>>> Hi all,
>>>>
>>>> One open issue regarding ICE-bis has been the semantics of the
>>>> ice-options attribute. Currently there is no way of saying "do aggressive
>>>> ICE even if you don't understand this option" or "reject my offer if you
>>>> don't understand this option".
>>>>
>>>> One way of solving this would be to introduce a new attribute like:
>>>>
>>>> a=ice-options-required:foo
>>>>
>>>> That is, if "foo" is unknown option to the answerer, the offer is
>>>> rejected. In addition to solving the second case, it could also be used to
>>>> test for the first and if option was not understood, simply leave it out of
>>>> the new offer. Of course this would result in one signaling exchange of
>>>> delay, and hence for the first case (do still aggressive) we could also
>>>> introduce yet another option:
>>>>
>>>> a=ice-options-optional:bar
>>>
>>>
>>> I don't have a strong opinion on this but the latter seems to be the only
>>> one offering consistency with existing implementations.
>>
>> Do you mean that existing implementations ignore unknown options and still
>> do aggressive ICE?
>
> No, the opposite actually.
>
>> The first one, understand or fail, is what Martin Thomson requested at the
>> previous meeting. With that you can actually accomplish both, but with some
>> penalty.
>
> I might be misunderstanding the semantics you imply in
> ice-options-optional and ice-options-requied so let's get that
> clarified first:
>
> Are you suggesting them as alternatives (which is what I thought you
> meant) or that we adopt both of them together?

I was suggesting (potentially) both, but perhaps the 
ice-options-optional alone makes more sense as you point out below.

> My point was that "ice-opitons-optional" fits nicely with what we have
> right now. Trickle is a good example of how you could be lacking
> support for an option and still be perfectly capable of nominating
> aggressively.

Good point. And I would assume this applies to many other extensions too.

> I am a bit confused with "ice-options-required" because a) it kind of
> overlaps with the SIP Requires header and b) I am not a big fan of
> "let's try an offer *this* way and if it fails we'll try it *that*
> way". This inevitably leads to the question "are we sure we actually
> know why it failed?" (and the common answer "... eer ... not really".

This seems to indicate that the -required may not necessarily be a good 
idea. Would be great to hear more opinions on this though.

> Then again, I don't really mind that much. Still, if people have cases
> where this is necessary, I'd be curious to hear them.

Martin, do you happen to remember what kind of case you had in mind for 
this? And would that be solvable with the SIP Requires header?


Cheers,
Ari


From nobody Sat Mar  1 17:52:00 2014
Return-Path: <ari.keranen@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 7126A1A035B for <mmusic@ietfa.amsl.com>; Sat,  1 Mar 2014 17:51:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.551
X-Spam-Level: 
X-Spam-Status: No, score=-3.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 zX-BqOwxkSI7 for <mmusic@ietfa.amsl.com>; Sat,  1 Mar 2014 17:51:58 -0800 (PST)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id C20551A032E for <mmusic@ietf.org>; Sat,  1 Mar 2014 17:51:57 -0800 (PST)
X-AuditID: c1b4fb25-b7f038e000005d01-83-53128ebaba87
Received: from ESESSHC007.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 29.94.23809.ABE82135; Sun,  2 Mar 2014 02:51:54 +0100 (CET)
Received: from mail.lmf.ericsson.se (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.41) with Microsoft SMTP Server id 14.2.347.0; Sun, 2 Mar 2014 02:51:54 +0100
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se [131.160.33.3])	by mail.lmf.ericsson.se (Postfix) with ESMTP id 178B81101F3 for <mmusic@ietf.org>; Sun,  2 Mar 2014 03:51:54 +0200 (EET)
Received: from nomadiclab.lmf.ericsson.se (localhost [127.0.0.1])	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 0E58856B2B	for <mmusic@ietf.org>; Sun,  2 Mar 2014 03:51:49 +0200 (EET)
Received: from As-MacBook-Air.local (localhost [127.0.0.1])	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id A44DF56B17	for <mmusic@ietf.org>; Sun,  2 Mar 2014 03:51:48 +0200 (EET)
Message-ID: <53128EB8.9070305@ericsson.com>
Date: Sun, 2 Mar 2014 01:51:52 +0000
From: =?ISO-8859-1?Q?Ari_Ker=E4nen?= <ari.keranen@ericsson.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: mmusic <mmusic@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupkluLIzCtJLcpLzFFi42KZGfG3RndXn1Cwwc5OLYupyx+zODB6LFny kymAMYrLJiU1J7MstUjfLoEro+3MXPaCCVwVk4/PY29gPMPexcjJISFgInF202woW0ziwr31 bF2MXBxCAocYJZ6eOskI4axnlGiY/wAqc4lRYs3slWAtQgKHGSVebhWBSOxllLh0ZDUTSIJX QFui49IXMJtFQEXiRstBNhCbTcBe4uaE62DNogLJEje/f2aDqBeUODnzCQuILSIgI7F302Zm EFtYwFbiefNWVhCbGci+MOc6C4QtL7H97RxmiLvVJK6e28QMcZCqxNV/rxgnMArNQjJ2FpL2 WUjaFzAyr2Jkz03MzEkvN9rECAzOg1t+q+5gvHNO5BCjNAeLkjjvh7fOQUIC6YklqdmpqQWp RfFFpTmpxYcYmTg4pRoYlxqbBXPsfGxzfgPbr/sbr1srvI5ZKDPde/Kej+JHwj5cZjZS2XL5 cb1B1bV72uxaLWcu7LnnYLLipNSi3EV+B5sWLltkZHG7p9D8mknApmNH5Y9EL75sc2uW+KvX zRsP/ty9NjjkVbLbo+QMIS+FTbez7xpk5bxZbfjXnrV25b5DAufjspJ/VSixFGckGmoxFxUn AgC0vC+9HAIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/BcDMlGPTcn1V3czrYm5WBM34GgU
Subject: [MMUSIC] Comments on draft-reddy-mmusic-ice-happy-eyeballs-06
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: Sun, 02 Mar 2014 01:51:59 -0000

Hi,

I think the new version of the happy eyeballs method looks better.

However, I was wondering does the Cmax in the example algorithm need to 
be negotiated or should some default value (range?) be recommended?

Also, wouldn't the IPv6 brokenness be discovered when the IPv6 server 
reflexive candidates are gathered?


And a few more specific comments on the text in the draft:

    The resulting checklist will depend on the priorities of the remote
    candidates.  It is not possible to ensure an even spread of IPv4 and
    IPv6 addresses unless both the remote and local sides uses the simple
    recommendations in this draft.

I guess it doesn't matter what algorithm is used, as long as it's the 
same and with same parameters.


    It is worth noting that there is a
    good chance it will some effect even if the remote side does not
    support this.

I'm not really sure what is the effect?


    (1)  HOST  IPv6 (1) Priority: 2129289471
    (2)  HOST  IPv6 (1) Priority: 2129289471
    (3)  HOST  IPv6 (1) Priority: 2129289471
    (4)  HOST  IPv6 (2) Priority: 2129289470
    (5)  HOST  IPv6 (2) Priority: 2129289470
    (6)  HOST  IPv6 (2) Priority: 2129289470

Is that 2x3 candidates with the same priority intentional?


Cheers,
Ari


From nobody Sun Mar  2 00:44:55 2014
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 80BAB1A0652 for <mmusic@ietfa.amsl.com>; Sun,  2 Mar 2014 00:44:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 H1sUwa-Vgqlg for <mmusic@ietfa.amsl.com>; Sun,  2 Mar 2014 00:44:51 -0800 (PST)
Received: from sesbmg20.ericsson.net (sesbmg20.ericsson.net [193.180.251.56]) by ietfa.amsl.com (Postfix) with ESMTP id 9CB641A0868 for <mmusic@ietf.org>; Sun,  2 Mar 2014 00:44:50 -0800 (PST)
X-AuditID: c1b4fb38-b7f418e000001099-c9-5312ef7eb0cc
Received: from ESESSHC008.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg20.ericsson.net (Symantec Mail Security) with SMTP id 26.82.04249.E7FE2135; Sun,  2 Mar 2014 09:44:47 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.216]) by ESESSHC008.ericsson.se ([153.88.183.42]) with mapi id 14.02.0387.000; Sun, 2 Mar 2014 09:44:46 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: IETF#89: BUNDLE: Q9: What are the criteria for allowing usage of the same PT value within multiple m- lines?
Thread-Index: Ac818yLx23ucJzjaSbubJw5GhjG+yg==
Date: Sun, 2 Mar 2014 08:44:45 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D1C368D@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.154]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1D1C368DESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrMLMWRmVeSWpSXmKPExsUyM+JvjW79e6Fgg4VfOC2mLn/M4sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujLkTbjMWbFGq6Fi5i7mB8ZRsFyMHh4SAicS3k4xdjJxAppjE hXvr2boYuTiEBI4wSvy89YQFJCEksJhR4sy5MpB6NgELie5/2iBhEQF1ia97e5hBbGGBcom2 7a2sEPEaiXszJjND2HoSn5feBIuzCKhITLhxjAnE5hXwlTiytAfMZgTa+/3UGjCbWUBc4taT +UwQ9whILNlznhnCFpV4+fgfK4StJLHo9mcmkHOYBfIl3r+PgRgpKHFy5hOWCYxCs5BMmoVQ NQtJFUSJjsSC3Z/YIGxtiWULXzPD2GcOPGZCFl/AyL6KkaM4tTgpN93IYBMjMOAPbvltsYPx 8l+bQ4zSHCxK4rwf3zoHCQmkJ5akZqemFqQWxReV5qQWH2Jk4uCUamBMXO5q7Sq42qJf525m /iTZvltnjTUmvUxdUJkd+zP1lY32gfzE4vDurU5H/7D4Lbt+0P1X/arkDt4IvfyCaVx5/9KD XSQmFlt/eSV72Ec63Nqz/g6bw+svwRZfl2Ye+uD2ada5vAX+HUdz/uVs/LvjOIsO81mhwA+e 6iYMosze395Eb+2/q6bEUpyRaKjFXFScCABRyFiJRgIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/qAi2rj6YUMSgGiD2LIULdzaw5fc
Subject: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for allowing usage of the same PT value within multiple m- lines?
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: Sun, 02 Mar 2014 08:44:53 -0000

--_000_7594FB04B1934943A5C02806D1A2204B1D1C368DESESSMB209erics_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

One of the open issues we have in BUNDLE, is when it is allowed to use the =
same PT value within multiple m- lines.

We tried to come up with different criteria, including a "codec configurati=
on" concept, but we never managed to agree on something.

So, in London, I intend to suggest that we simply say: if you offer the sam=
e PT value within multiple m- line, make sure you can handle the associated=
 media when it arrives - period (keep in mind that you always indicate what=
 you want to RECEIVE - the remote peer can still ask you to SEND using diff=
erent PT values).

If you don't like this, please provide an alternative solution, because I w=
ant to close this issue in London. There is no idea to keep "taking the iss=
ue back to the list". We've done that for a few meetings already.

Regards,

Christer

--_000_7594FB04B1934943A5C02806D1A2204B1D1C368DESESSMB209erics_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-GB" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">One of the open issues we have in BUNDLE, is when it=
 is allowed to use the same PT value within multiple m- lines.<o:p></o:p></=
p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">We tried to come up with different criteria, includi=
ng a &#8220;codec configuration&#8221; concept, but we never managed to agr=
ee on something.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">So, in London, I intend to suggest that we simply sa=
y: if you offer the same PT value within multiple m- line, make sure you ca=
n handle the associated media when it arrives &#8211; period (keep in mind =
that you always indicate what you want to
 RECEIVE &#8211; the remote peer can still ask you to SEND using different =
PT values).<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">If you don&#8217;t like this, please provide an alte=
rnative solution, because I want to close this issue in London. There is no=
 idea to keep &#8220;taking the issue back to the list&#8221;. We&#8217;ve =
done that for a few meetings already.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Regards,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Christer<o:p></o:p></p>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B1D1C368DESESSMB209erics_--


From nobody Sun Mar  2 02:34:14 2014
Return-Path: <suhasietf@gmail.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 D5C611A0C99 for <mmusic@ietfa.amsl.com>; Sun,  2 Mar 2014 02:34:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 aEGD0De1BgLq for <mmusic@ietfa.amsl.com>; Sun,  2 Mar 2014 02:34:09 -0800 (PST)
Received: from mail-wg0-x22c.google.com (mail-wg0-x22c.google.com [IPv6:2a00:1450:400c:c00::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 3615C1A0C97 for <mmusic@ietf.org>; Sun,  2 Mar 2014 02:34:09 -0800 (PST)
Received: by mail-wg0-f44.google.com with SMTP id a1so1994749wgh.3 for <mmusic@ietf.org>; Sun, 02 Mar 2014 02:34:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=zna7LTgrPE28DsthThCc63lR7QuOUGVWmNWTDryh3MM=; b=M4Kumm3kNBWHEsgtb+ebJ2ekeniRd1KmlXlbtMtaIyca3PaM3j8ExqKZUIHor2kTm9 bR27M0mBd/z8272ypbUDsbiC9E++EyKvRuth/Xu4elaMBoT3/keg5spHpIyEIyynKECk f+werCZ5oYrHM212sc5oHXMp1KVKkRiUpebXVIgwR8KbOl0RLvPqj93TW8YcCZhu8tqK OIwGGxIsizvUXzojpfRSHJ3lbxkfMcnFAcoO2IlsTiYAeJ2gMTbYAXpONvUhhDZ2cf3w OiDYq4ViF+Zd5yKAj/BZZkpzYHI3a+ZtT55F2C5WZAFdCS+KA8FQiPbz3epcsldY56gM s8Uw==
MIME-Version: 1.0
X-Received: by 10.180.149.206 with SMTP id uc14mr10602265wib.44.1393756446119;  Sun, 02 Mar 2014 02:34:06 -0800 (PST)
Received: by 10.195.12.134 with HTTP; Sun, 2 Mar 2014 02:34:06 -0800 (PST)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D1C368D@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D1C368D@ESESSMB209.ericsson.se>
Date: Sun, 2 Mar 2014 10:34:06 +0000
Message-ID: <CAMRcRGRq5zrZJNBwvPpX-nshqar8vS2u3Kefu91GhoGXTtoJYA@mail.gmail.com>
From: Suhas Nandakumar <suhasietf@gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary=001a11c38008dfdd6004f39d3505
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/b2E1TSAk17R67rQU51ItyOiBdKc
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for allowing usage of the same PT value within multiple m- lines?
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: Sun, 02 Mar 2014 10:34:12 -0000

--001a11c38008dfdd6004f39d3505
Content-Type: text/plain; charset=ISO-8859-1

+1 on closing this action item

I support either a clearly specified codec configuration definition or
something on the lines above

Cheers
Suhas

On Sunday, March 2, 2014, Christer Holmberg <christer.holmberg@ericsson.com>
wrote:

>  Hi,
>
>
>
> One of the open issues we have in BUNDLE, is when it is allowed to use the
> same PT value within multiple m- lines.
>
>
>
> We tried to come up with different criteria, including a "codec
> configuration" concept, but we never managed to agree on something.
>
>
>
> So, in London, I intend to suggest that we simply say: if you offer the
> same PT value within multiple m- line, make sure you can handle the
> associated media when it arrives - period (keep in mind that you always
> indicate what you want to RECEIVE - the remote peer can still ask you to
> SEND using different PT values).
>
>
>
> If you don't like this, please provide an alternative solution, because I
> want to close this issue in London. There is no idea to keep "taking the
> issue back to the list". We've done that for a few meetings already.
>
>
>
> Regards,
>
>
>
> Christer
>

--001a11c38008dfdd6004f39d3505
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

+1 on closing this action item<div><br></div><div>I support either a clearl=
y specified codec configuration definition or something on the lines above<=
/div><div><br></div><div>Cheers</div><div>Suhas&nbsp;<span></span><br><br>O=
n Sunday, March 2, 2014, Christer Holmberg &lt;<a href=3D"mailto:christer.h=
olmberg@ericsson.com">christer.holmberg@ericsson.com</a>&gt; wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">





<div lang=3D"EN-GB" link=3D"#0563C1" vlink=3D"#954F72">
<div>
<p class=3D"MsoNormal">Hi,<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal">One of the open issues we have in BUNDLE, is when it=
 is allowed to use the same PT value within multiple m- lines.<u></u><u></u=
></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal">We tried to come up with different criteria, includi=
ng a &ldquo;codec configuration&rdquo; concept, but we never managed to agr=
ee on something.<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal">So, in London, I intend to suggest that we simply sa=
y: if you offer the same PT value within multiple m- line, make sure you ca=
n handle the associated media when it arrives &ndash; period (keep in mind =
that you always indicate what you want to
 RECEIVE &ndash; the remote peer can still ask you to SEND using different =
PT values).<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal">If you don&rsquo;t like this, please provide an alte=
rnative solution, because I want to close this issue in London. There is no=
 idea to keep &ldquo;taking the issue back to the list&rdquo;. We&rsquo;ve =
done that for a few meetings already.<u></u><u></u></p>

<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal">Regards,<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal">Christer<u></u><u></u></p>
</div>
</div>

</blockquote></div>

--001a11c38008dfdd6004f39d3505--


From nobody Sun Mar  2 05:18:17 2014
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 BD7641A0CEE for <mmusic@ietfa.amsl.com>; Sun,  2 Mar 2014 05:18:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.85
X-Spam-Level: 
X-Spam-Status: No, score=-3.85 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 9U4ekh94Qs0b for <mmusic@ietfa.amsl.com>; Sun,  2 Mar 2014 05:18:11 -0800 (PST)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id F2D2E1A0CC8 for <mmusic@ietf.org>; Sun,  2 Mar 2014 05:18:10 -0800 (PST)
X-AuditID: c1b4fb25-b7f038e000005d01-ae-53132f8fa519
Received: from ESESSHC020.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 70.0F.23809.F8F23135; Sun,  2 Mar 2014 14:18:07 +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; Sun, 2 Mar 2014 14:18:06 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Suhas Nandakumar <suhasietf@gmail.com>
Thread-Topic: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for allowing usage of the same PT value within multiple m- lines?
Thread-Index: Ac818yLx23ucJzjaSbubJw5GhjG+ygAB2s0AAAfSnOc=
Date: Sun, 2 Mar 2014 13:18:05 +0000
Message-ID: <82q8no58hvgf81e3x2o3mnbt.1393766282956@email.android.com>
References: <7594FB04B1934943A5C02806D1A2204B1D1C368D@ESESSMB209.ericsson.se>,  <CAMRcRGRq5zrZJNBwvPpX-nshqar8vS2u3Kefu91GhoGXTtoJYA@mail.gmail.com>
In-Reply-To: <CAMRcRGRq5zrZJNBwvPpX-nshqar8vS2u3Kefu91GhoGXTtoJYA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_82q8no58hvgf81e3x2o3mnbt1393766282956emailandroidcom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrJLMWRmVeSWpSXmKPExsUyM+JvjW6/vnCwwfLDOhZTlz9msdg5t4PZ gclj56y77B5LlvxkCmCK4rJJSc3JLEst0rdL4MroejidveCIYsX3HT3sDYyLZboYOTkkBEwk fj2+yQxhi0lcuLeerYuRi0NI4BCjxK7985khnMWMEjePd7J2MXJwsAlYSHT/0wZpEBHQkli9 eC4TSJhZQF3i6uIgkLCwQAujxK1XdSCtIgKtjBJT+o8wQdRbSbzc84gdxGYRUJGY33qPEcTm FXCTeP3zHivErkmMEl9mPmEDSXAKBEqcvH0arJkR6Lrvp9aA2cwC4hK3nsxngrhaQGLJnvNQ H4hKvHz8jxWiJkfi+snfTBALBCVOznzCMoFRZBaS9llIymYhKYOIG0i8PzefGcLWlli28DWU rS+x8ctZRmTxBYzsqxjZcxMzc9LLjTYxAqPn4JbfqjsY75wTOcQozcGiJM774a1zkJBAemJJ anZqakFqUXxRaU5q8SFGJg5OqQZGdnupLLura9TnfZzstt8mPEys6mvMzo6/h5m+TD8vurG+ /5Zq4gmDQPM1D1p+iVncip+o0TkxUGTKGyFr86+X8mdPUuzzDVXjEflp4VOuPOuGyib1KQ0W yfFSPkumr5H27j17LdBNJDep4fjSk847PJdKPOS/XbpLnz+OZTNzi+sVG9NHrkpKLMUZiYZa zEXFiQA4U4BQbAIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/cRQJqm6PLCQzZ7RZPxLQqipk_QA
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for allowing usage of the same PT value within multiple m- lines?
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: Sun, 02 Mar 2014 13:18:14 -0000

--_000_82q8no58hvgf81e3x2o3mnbt1393766282956emailandroidcom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

And, as we don't have any text for a clearly specified codec configuration,=
 the choice is easy :)

Regards,

Christer

Sent from my Sony Ericsson Xperia arc S

Suhas Nandakumar <suhasietf@gmail.com> wrote:



+1 on closing this action item

I support either a clearly specified codec configuration definition or some=
thing on the lines above

Cheers
Suhas

On Sunday, March 2, 2014, Christer Holmberg <christer.holmberg@ericsson.com=
<mailto:christer.holmberg@ericsson.com>> wrote:
Hi,

One of the open issues we have in BUNDLE, is when it is allowed to use the =
same PT value within multiple m- lines.

We tried to come up with different criteria, including a =93codec configura=
tion=94 concept, but we never managed to agree on something.

So, in London, I intend to suggest that we simply say: if you offer the sam=
e PT value within multiple m- line, make sure you can handle the associated=
 media when it arrives =96 period (keep in mind that you always indicate wh=
at you want to RECEIVE =96 the remote peer can still ask you to SEND using =
different PT values).

If you don=92t like this, please provide an alternative solution, because I=
 want to close this issue in London. There is no idea to keep =93taking the=
 issue back to the list=94. We=92ve done that for a few meetings already.

Regards,

Christer

--_000_82q8no58hvgf81e3x2o3mnbt1393766282956emailandroidcom_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body>
<pre style=3D"word-wrap:break-word; font-size:10.0pt; font-family:Tahoma; c=
olor:black">And, as we don't have any text for a clearly specified codec co=
nfiguration, the choice is easy :)=0A=
=0A=
Regards,=0A=
=0A=
Christer=0A=
=0A=
Sent from my Sony Ericsson Xperia arc S=0A=
=0A=
Suhas Nandakumar &lt;suhasietf@gmail.com&gt; wrote:=0A=
=0A=
</pre>
<div>&#43;1 on closing this action item
<div><br>
</div>
<div>I support either a clearly specified codec configuration definition or=
 something on the lines above</div>
<div><br>
</div>
<div>Cheers</div>
<div>Suhas&nbsp;<span></span><br>
<br>
On Sunday, March 2, 2014, Christer Holmberg &lt;<a href=3D"mailto:christer.=
holmberg@ericsson.com">christer.holmberg@ericsson.com</a>&gt; wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex; border-left:1=
px #ccc solid; padding-left:1ex">
<div lang=3D"EN-GB">
<div>
<p class=3D"MsoNormal">Hi,<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal">One of the open issues we have in BUNDLE, is when it=
 is allowed to use the same PT value within multiple m- lines.<u></u><u></u=
></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal">We tried to come up with different criteria, includi=
ng a =93codec configuration=94 concept, but we never managed to agree on so=
mething.<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal">So, in London, I intend to suggest that we simply sa=
y: if you offer the same PT value within multiple m- line, make sure you ca=
n handle the associated media when it arrives =96 period (keep in mind that=
 you always indicate what you want to
 RECEIVE =96 the remote peer can still ask you to SEND using different PT v=
alues).<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal">If you don=92t like this, please provide an alternat=
ive solution, because I want to close this issue in London. There is no ide=
a to keep =93taking the issue back to the list=94. We=92ve done that for a =
few meetings already.<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal">Regards,<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
<p class=3D"MsoNormal">Christer<u></u><u></u></p>
</div>
</div>
</blockquote>
</div>
</div>
</body>
</html>

--_000_82q8no58hvgf81e3x2o3mnbt1393766282956emailandroidcom_--


From nobody Sun Mar  2 08:03:51 2014
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 8BD621A07A2 for <mmusic@ietfa.amsl.com>; Sun,  2 Mar 2014 08:03:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.85
X-Spam-Level: 
X-Spam-Status: No, score=-3.85 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 sDk1P3w5GFY8 for <mmusic@ietfa.amsl.com>; Sun,  2 Mar 2014 08:03:48 -0800 (PST)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 7150A1A07FA for <mmusic@ietf.org>; Sun,  2 Mar 2014 08:03:47 -0800 (PST)
X-AuditID: c1b4fb2d-b7f5d8e000002a7b-ce-5313565f68fe
Received: from ESESSHC018.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 15.BC.10875.F5653135; Sun,  2 Mar 2014 17:03:44 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.216]) by ESESSHC018.ericsson.se ([153.88.183.72]) with mapi id 14.02.0387.000; Sun, 2 Mar 2014 17:03:43 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: IETF#89: BUNDLE: Q12: Scope of non-RTP media de-mux procedures in BUNDLE?
Thread-Index: Ac82MKMUCOeiYc5PSXK9YNe83HDvFw==
Date: Sun, 2 Mar 2014 16:03:43 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D1C4C88@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.148]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1D1C4C88ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrGLMWRmVeSWpSXmKPExsUyM+JvjW5CmHCwwcd9/BZTlz9mcWD0WLLk J1MAYxSXTUpqTmZZapG+XQJXxtMfJ9gL3ppXLH30namB8Z5BFyMnh4SAicSr9insELaYxIV7 69m6GLk4hAQOMUrM/nicBcJZzCixducU5i5GDg42AQuJ7n/aIA0iAuoSX/f2MIPYwgIhEp8/ fmSBiEdKXDu9ngnC1pNY/ncemM0ioCLxo3cvWA2vgK9E68M1bCA2I9Di76fWgNUwC4hL3Hoy nwniIAGJJXvOM0PYohIvH/9jhbCVJBqXPGGFqM+X2L9iAjvETEGJkzOfsExgFJqFZNQsJGWz kJRBxHUkFuz+xAZha0ssW/iaGcY+c+AxE7L4Akb2VYzsuYmZOenlhpsYgWF/cMtv3R2Mp86J HGKU5mBREuf98NY5SEggPbEkNTs1tSC1KL6oNCe1+BAjEwenVAMj9++GFr6JyeqdP1ZufXOY LXbLrb9cd3OdDdP2/RWISve7Lfbz/ppJPRKGhsutTaYtY3CaNufS0aijzB9kf5q9u+H5xuSl iGwq89SpFxWD+TbnljLPfqgyv/7Od5f/Bn6vDMJL51w7GGP2ZvHWq/p9l6KeHNi23J6h3iJl 4/edH5vOZlktncEpocRSnJFoqMVcVJwIAJZ6MqxJAgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/t-2-X-GqhzVHuJFOYkjUZqtxPBM
Subject: [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: Sun, 02 Mar 2014 16:03:50 -0000

--_000_7594FB04B1934943A5C02806D1A2204B1D1C4C88ESESSMB209erics_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

One of the open issues is what we, in the BUNDLE spec, are going to say abo=
ut de-multiplexing about different media types, and for which (if any) medi=
a types we are going to specify how the de-multiplexing is done.

We have previously agreed that we are NOT going to describe all different p=
ossibilities in BUNDLE, and that separate specifications how to perform (an=
d, indicate support of) de-multiplexing will have to be written. However, w=
e haven't really agreed on the details.

I intend to suggest the following in London.

In the BUNDLE spec we:


1)      Reference to RFC 5764 for how to de-multiplex DTLS/SRTP/STUN; and

2)      Separate specifications are required to describe how to de-mulitple=
x other media types, and any type of information that needs to be exchanged=
 between peers in order to perform the de-multiplexing.

I think that DTLS/SRTP/STUN is going to be the main use-case (not only for =
WebRTC) in the near future, so I think it's a good approach.

Regards,

Christer

--_000_7594FB04B1934943A5C02806D1A2204B1D1C4C88ESESSMB209erics_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1252005315;
	mso-list-type:hybrid;
	mso-list-template-ids:-287561610 134807569 134807577 134807579 134807567 1=
34807577 134807579 134807567 134807577 134807579;}
@list l0:level1
	{mso-level-text:"%1\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-GB" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">One of the open issues is what we, in the BUNDLE spe=
c, are going to say about de-multiplexing about different media types, and =
for which (if any) media types we are going to specify how the de-multiplex=
ing is done.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">We have previously agreed that we are NOT going to d=
escribe all different possibilities in BUNDLE, and that separate specificat=
ions how to perform (and, indicate support of) de-multiplexing will have to=
 be written. However, we haven&#8217;t really
 agreed on the details.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I intend to suggest the following in London.<o:p></o=
:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">In the BUNDLE spec we:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l0 leve=
l1 lfo1"><![if !supportLists]><span style=3D"mso-list:Ignore">1)<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>Reference to RFC 5764 for how to de-multiplex DTLS/=
SRTP/STUN; and<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-18.0pt;mso-list:l0 leve=
l1 lfo1"><![if !supportLists]><span style=3D"mso-list:Ignore">2)<span style=
=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span><![endif]>Separate specifications are required to describe ho=
w to de-mulitplex other media types, and any type of information that needs=
 to be exchanged between peers in order to perform the de-multiplexing.<o:p=
></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I think that DTLS/SRTP/STUN is going to be the main =
use-case (not only for WebRTC) in the near future, so I think it&#8217;s a =
good approach.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Regards,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Christer<o:p></o:p></p>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B1D1C4C88ESESSMB209erics_--


From nobody Sun Mar  2 09:11:27 2014
Return-Path: <Raju.Makaraju@alcatel-lucent.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 DEF861A0988 for <mmusic@ietfa.amsl.com>; Sun,  2 Mar 2014 09:11:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level: 
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5] autolearn=ham
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 r8sM5kgiN1te for <mmusic@ietfa.amsl.com>; Sun,  2 Mar 2014 09:11:19 -0800 (PST)
Received: from ihemail3.lucent.com (ihemail3.lucent.com [135.245.0.37]) by ietfa.amsl.com (Postfix) with ESMTP id 199C61A0985 for <mmusic@ietf.org>; Sun,  2 Mar 2014 09:11:19 -0800 (PST)
Received: from us70uusmtp4.zam.alcatel-lucent.com (h135-5-2-66.lucent.com [135.5.2.66]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id s22HB5vv021583 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sun, 2 Mar 2014 11:11:06 -0600 (CST)
Received: from US70TWXCHHUB04.zam.alcatel-lucent.com (us70twxchhub04.zam.alcatel-lucent.com [135.5.2.36]) by us70uusmtp4.zam.alcatel-lucent.com (GMO) with ESMTP id s22HB5qK015437 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 2 Mar 2014 12:11:05 -0500
Received: from US70UWXCHMBA02.zam.alcatel-lucent.com ([169.254.8.212]) by US70TWXCHHUB04.zam.alcatel-lucent.com ([135.5.2.36]) with mapi id 14.02.0247.003; Sun, 2 Mar 2014 12:11:05 -0500
From: "Makaraju, Maridi Raju (Raju)" <Raju.Makaraju@alcatel-lucent.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, Mary Barnes <mary.ietf.barnes@gmail.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: IETF#89: First version of CLUE Data Channel slide set.
Thread-Index: AQHPNW3bGiqdS9LZRZu/XRhtec89PJrM/r0AgADHGRCAAHIogP//rM2AgABip4D//7uAwA==
Date: Sun, 2 Mar 2014 17:11:04 +0000
Message-ID: <E1FE4C082A89A246A11D7F32A95A17826E003961@US70UWXCHMBA02.zam.alcatel-lucent.com>
References: <7594FB04B1934943A5C02806D1A2204B1D1C0E03@ESESSMB209.ericsson.se> <CAHBDyN75R1Wr5BODSQ9RNmNP9G7QZdOjZ9Lw+Vz3DCEUUYh4-Q@mail.gmail.com> <CAHBDyN5aDiJHy0fZ3=A8bLyCGAEhSojxu0_kAdLvOTykykE36Q@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1D1C2DF7@ESESSMB209.ericsson.se> <E1FE4C082A89A246A11D7F32A95A17826E003463@US70UWXCHMBA02.zam.alcatel-lucent.com> <7594FB04B1934943A5C02806D1A2204B1D1C3A97@ESESSMB209.ericsson.se> <E1FE4C082A89A246A11D7F32A95A17826E003836@US70UWXCHMBA02.zam.alcatel-lucent.com> <7594FB04B1934943A5C02806D1A2204B1D1C4C1F@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D1C4C1F@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.5.27.17]
Content-Type: multipart/alternative; boundary="_000_E1FE4C082A89A246A11D7F32A95A17826E003961US70UWXCHMBA02z_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/g2MSElu_bJN_QvnVdXt6ceGfzxA
Cc: "DRAGE, Keith \(Keith\)" <keith.drage@alcatel-lucent.com>, "pkyzivat@alum.mit.edu" <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] IETF#89: First version of CLUE Data Channel slide set.
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: Sun, 02 Mar 2014 17:11:22 -0000

--_000_E1FE4C082A89A246A11D7F32A95A17826E003961US70UWXCHMBA02z_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

+ mmusic to cover some of the discussions.

Hi,
Please see comments inline.

Hi,

For the gateway use-case, do we really need to indicate the SCTP stream dur=
ing Offer/Answer?

Or, would it be enough if we indicate that the data channel is going to be =
used for CLUE, and the gateway then figures out which stream is used when i=
t receives DCEP OPEN?
[Raju] This approach has 2 implications:

1.       The gateway needs to look at bearer packets and notify the signali=
ng layer about the streams. Though possible, this is computationally intens=
ive and new mechanism needed for such notification between bearer and signa=
ling layers.

Why does it need to inform the signalling layer about the streams? The cont=
roller needs to tell the media gateway: "please let CLUE go through"
[Raju] "Please let CLUE through" is a simple scenario without much interwor=
king and other needs.
I want to point out couple of other interworking scenarios:

1.       Lawful intercept (LI): A CLUE channel may have to be reported to L=
I agents per regulatory requirements. For various reasons such reporting ma=
y have to be interworked with non-data channel SCTP/dTLS transport (e.g. TC=
P).

2.       For Non-LI reasons, a CLUE could be interworked to a TCP based tra=
nsport in an end-to-access-edge kind of approach.
In either of these cases, the media gateway will not be aware of how to do =
such interworkings. Even if controller can ask gateway ahead of time what t=
o do (in a yet to be defined complex way by protocols like H.248/Megaco) th=
en still gateway have to report the TCP transport address back to controlle=
r so that it can inform LI agents about this address.
Essentially, not having external negotiation will complicate other protocol=
s (like H.248/Megaco MG-MGC protocol) and still won't avoid per-data channe=
l notification to the signaling entity (controller). Please note that such =
"media gateway centric/driven" complex procedures may not even be allowed b=
y H.248/Megaco as controllers wants be the one making such decisions as the=
y happen.


2.       There could be several streams using the same subprotocol. Then ho=
w does gateway know which maps to what? CLUE may have just one data channel=
 stream; but we may also have to think about CLUE combined with other data =
channels under same SCTP association. Even for single CLUE stream case item=
 (1) is still an issue though.

The gateway is going to get DCEP for each subprotocol, so it knows which on=
e is CLUE.
[Raju] As noted, since in this specific case there is one single CLUE data =
channel a gateway unambigously can map. But still the above mentioned inter=
working requires controller involvement as the data channels are open.

Regards
Raju

Regards,

Christer

--_000_E1FE4C082A89A246A11D7F32A95A17826E003961US70UWXCHMBA02z_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle23
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1201279069;
	mso-list-type:hybrid;
	mso-list-template-ids:-1914295502 874819218 67698713 67698715 67698703 676=
98713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-weight:bold;
	mso-ansi-font-style:italic;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#7030A0">&#43; mmusic to cover som=
e of the discussions.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#7030A0"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#7030A0">Hi,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#7030A0">Please see comments inlin=
e.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#548235">Hi,<o:p></=
o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">For the ga=
teway use-case, do we really need to indicate the SCTP stream during Offer/=
Answer?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Or, would =
it be enough if we indicate that the data channel is going to be used for C=
LUE, and the gateway then figures out which stream is used
 when it receives DCEP OPEN?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><b><i><span lang=3D"EN-GB" style=3D"font-size:11.0pt=
;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#C00000">[Raj=
u] This approach has 2 implications:<o:p></o:p></span></i></b></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in"><b><i><span lang=
=3D"EN-GB" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;=
sans-serif&quot;;color:#C00000">1.</span></i></b><b><i><span lang=3D"EN-GB"=
 style=3D"font-size:7.0pt;color:#C00000">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;
</span></i></b><span lang=3D"EN-GB" style=3D"font-size:11.0pt;font-family:&=
quot;Calibri&quot;,&quot;sans-serif&quot;;color:#C00000">The gateway needs =
to look at bearer packets and notify the signaling layer about the streams.=
 Though possible, this is computationally intensive and
 new mechanism needed for such notification between bearer and signaling la=
yers.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:29.0pt"><span lang=3D"EN-GB" st=
yle=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:#548235">Why does it need to inform the signalling layer about th=
e streams? The controller needs to tell the media gateway: &#8220;please
 let CLUE go through&#8221;<o:p></o:p></span></p>
<p class=3D"MsoNormal"><b><i><span lang=3D"EN-GB" style=3D"font-size:11.0pt=
;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#7030A0">[Raj=
u] &#8220;Please let CLUE through&#8221; is a simple scenario without much =
interworking and other needs.<o:p></o:p></span></i></b></p>
<p class=3D"MsoNormal"><b><i><span lang=3D"EN-GB" style=3D"font-size:11.0pt=
;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#7030A0">I wa=
nt to point out couple of other interworking scenarios:<o:p></o:p></span></=
i></b></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><b><i><span lang=3D"EN-GB" style=3D"font-size:=
11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#7030A0=
"><span style=3D"mso-list:Ignore">1.<span style=3D"font:7.0pt &quot;Times N=
ew Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span></i></b><![endif]><span lang=3D"EN-GB" style=3D"font-s=
ize:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#70=
30A0">Lawful intercept (LI): A CLUE channel may have to be reported to LI a=
gents per regulatory requirements. For various reasons such
 reporting may have to be interworked with non-data channel SCTP/dTLS trans=
port (e.g. TCP).<o:p></o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in;mso-list:l0 level=
1 lfo1"><![if !supportLists]><b><i><span lang=3D"EN-GB" style=3D"font-size:=
11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#7030A0=
"><span style=3D"mso-list:Ignore">2.<span style=3D"font:7.0pt &quot;Times N=
ew Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
</span></span></span></i></b><![endif]><span lang=3D"EN-GB" style=3D"font-s=
ize:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#70=
30A0">For Non-LI reasons, a CLUE could be interworked to a TCP based transp=
ort in an end-to-access-edge kind of approach.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#7030A0">In either =
of these cases, the media gateway will not be aware of how to do such inter=
workings. Even if controller can ask gateway ahead of time
 what to do (in a yet to be defined complex way by protocols like H.248/Meg=
aco) then still gateway have to report the TCP transport address back to co=
ntroller so that it can inform LI agents about this address.<o:p></o:p></sp=
an></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#7030A0">Essentiall=
y, not having external negotiation will complicate other protocols (like H.=
248/Megaco MG-MGC protocol) and still won&#8217;t avoid per-data
 channel notification to the signaling entity (controller). Please note tha=
t such &#8220;media gateway centric/driven&#8221; complex procedures may no=
t even be allowed by H.248/Megaco as controllers wants be the one making su=
ch decisions as they happen.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<p class=3D"MsoListParagraph" style=3D"text-indent:-.25in"><b><i><span lang=
=3D"EN-GB" style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;=
sans-serif&quot;;color:#C00000">2.</span></i></b><b><i><span lang=3D"EN-GB"=
 style=3D"font-size:7.0pt;color:#C00000">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;
</span></i></b><span lang=3D"EN-GB" style=3D"font-size:11.0pt;font-family:&=
quot;Calibri&quot;,&quot;sans-serif&quot;;color:#C00000">There could be sev=
eral streams using the same subprotocol. Then how does gateway know which m=
aps to what? CLUE may have just one data channel stream;
 but we may also have to think about CLUE combined with other data channels=
 under same SCTP association. Even for single CLUE stream case item (1) is =
still an issue though.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB" style=3D"font-size:11.0pt;font-=
family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp=
;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:23.5pt"><span lang=3D"EN-GB" st=
yle=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:#548235">The gateway is going to get DCEP for each subprotocol, s=
o it knows which one is CLUE.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><b><i><span lang=3D"EN-GB" style=3D"font-size:11.0pt=
;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#7030A0">[Raj=
u] As noted, since in this specific case there is one single CLUE data chan=
nel a gateway unambigously can map. But still the above mentioned
 interworking requires controller involvement as the data channels are open=
.<o:p></o:p></span></i></b></p>
<p class=3D"MsoNormal"><b><i><span lang=3D"EN-GB" style=3D"font-size:11.0pt=
;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#7030A0"><o:p=
>&nbsp;</o:p></span></i></b></p>
<p class=3D"MsoNormal"><b><i><span lang=3D"EN-GB" style=3D"font-size:11.0pt=
;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#7030A0">Rega=
rds<o:p></o:p></span></i></b></p>
<p class=3D"MsoNormal"><b><i><span lang=3D"EN-GB" style=3D"font-size:11.0pt=
;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#7030A0">Raju=
</span></i></b><span lang=3D"EN-GB" style=3D"font-size:11.0pt;font-family:&=
quot;Calibri&quot;,&quot;sans-serif&quot;;color:#7030A0"><o:p></o:p></span>=
</p>
<p class=3D"MsoNormal" style=3D"margin-left:23.5pt"><span lang=3D"EN-GB" st=
yle=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:#548235"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:23.5pt"><span lang=3D"EN-GB" st=
yle=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:#548235">Regards,<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:23.5pt"><span lang=3D"EN-GB" st=
yle=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:#548235"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:23.5pt"><span lang=3D"EN-GB" st=
yle=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&qu=
ot;;color:#548235">Christer<o:p></o:p></span></p>
</div>
</div>
</div>
</body>
</html>

--_000_E1FE4C082A89A246A11D7F32A95A17826E003961US70UWXCHMBA02z_--


From nobody Sun Mar  2 12:08:32 2014
Return-Path: <thomas.stach@unify.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 566681A0AA2 for <mmusic@ietfa.amsl.com>; Sun,  2 Mar 2014 12:08:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.146
X-Spam-Level: 
X-Spam-Status: No, score=-2.146 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.547] autolearn=ham
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 olme28lc384W for <mmusic@ietfa.amsl.com>; Sun,  2 Mar 2014 12:08:29 -0800 (PST)
Received: from mx12.unify.com (mx12.unify.com [62.134.46.10]) by ietfa.amsl.com (Postfix) with ESMTP id C3DD81A0AA1 for <mmusic@ietf.org>; Sun,  2 Mar 2014 12:08:28 -0800 (PST)
Received: from MCHP02HTC.global-ad.net (unknown [172.29.42.235]) by mx12.unify.com (Server) with ESMTP id 393AF23F0430; Sun,  2 Mar 2014 21:08:25 +0100 (CET)
Received: from MCHP04MSX.global-ad.net ([169.254.1.208]) by MCHP02HTC.global-ad.net ([172.29.42.235]) with mapi id 14.03.0174.001; Sun, 2 Mar 2014 21:08:25 +0100
From: "Stach, Thomas" <thomas.stach@unify.com>
To: =?iso-8859-1?Q?Ari_Ker=E4nen?= <ari.keranen@ericsson.com>
Thread-Topic: Comment on the ICE updated offer procedures
Thread-Index: Ac82UynstLVpW+NhS5ORd1Q4pZhv3Q==
Date: Sun, 2 Mar 2014 20:08:23 +0000
Message-ID: <F81CEE99482EFE438DAE2A652361EE1217A537BC@MCHP04MSX.global-ad.net>
Accept-Language: de-AT, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.29.42.225]
Content-Type: multipart/alternative; boundary="_000_F81CEE99482EFE438DAE2A652361EE1217A537BCMCHP04MSXglobal_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/YJRg2GFW9098F80bGDG7tuqY3vc
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: [MMUSIC] Comment on the ICE updated offer procedures
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: Sun, 02 Mar 2014 20:08:30 -0000

--_000_F81CEE99482EFE438DAE2A652361EE1217A537BCMCHP04MSXglobal_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Ari,

the slides  for IETF 89 propose that always an updated offer shall be sent.
You also mention the issues with that as listed in draft-elwell-mmusic-ice-=
updated-offer.
This was also discussed in IETF 80.
Draft-elwell-mmusic-ice-updated-offer acknowledges that there are middle bo=
xes that need such updated offer to work properly.
However, there are also cases and other types of middle boxes that break or=
 show undesirable behavior, just because of the updated offer.
Because of these issues, I think that always sending the updated offer shou=
ld not be required.
Instead, it should be made configurable if the updated offer is sent or not=
 sent, possibly together with some signaling (ice-options/ice-options-requi=
red?) which behavior is to be applied.

Regards
Thomas


--_000_F81CEE99482EFE438DAE2A652361EE1217A537BCMCHP04MSXglobal_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Ari,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">the slides &nbsp;for IETF 89 propose that always an =
updated offer shall be sent.<o:p></o:p></p>
<p class=3D"MsoNormal">You also mention the issues with that as listed in d=
raft-elwell-mmusic-ice-updated-offer.<o:p></o:p></p>
<p class=3D"MsoNormal">This was also discussed in IETF 80.<o:p></o:p></p>
<p class=3D"MsoNormal">Draft-elwell-mmusic-ice-updated-offer acknowledges t=
hat there are middle boxes that need such updated offer to work properly.<o=
:p></o:p></p>
<p class=3D"MsoNormal">However, there are also cases and other types of mid=
dle boxes that break or show undesirable behavior, just because of the upda=
ted offer.<o:p></o:p></p>
<p class=3D"MsoNormal">Because of these issues, I think that always sending=
 the updated offer should not be required.<o:p></o:p></p>
<p class=3D"MsoNormal">Instead, it should be made configurable if the updat=
ed offer is sent or not sent, possibly together with some signaling (ice-op=
tions/ice-options-required?) which behavior is to be applied.<o:p></o:p></p=
>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Regards<o:p></o:p></p>
<p class=3D"MsoNormal">Thomas<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_F81CEE99482EFE438DAE2A652361EE1217A537BCMCHP04MSXglobal_--


From nobody Sun Mar  2 12:16:52 2014
Return-Path: <pkyzivat@alum.mit.edu>
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 C6BE61A0AAC for <mmusic@ietfa.amsl.com>; Sun,  2 Mar 2014 12:16:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] 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 bPnhbMAA3-tq for <mmusic@ietfa.amsl.com>; Sun,  2 Mar 2014 12:16:48 -0800 (PST)
Received: from QMTA11.westchester.pa.mail.comcast.net (qmta11.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:211]) by ietfa.amsl.com (Postfix) with ESMTP id C10C51A0A7E for <mmusic@ietf.org>; Sun,  2 Mar 2014 12:16:47 -0800 (PST)
Received: from omta02.westchester.pa.mail.comcast.net ([76.96.62.19]) by QMTA11.westchester.pa.mail.comcast.net with comcast id YiyM1n0050QuhwU5BkGliP; Sun, 02 Mar 2014 20:16:45 +0000
Received: from dhcp-hotel-wifi-157-6c.meeting.ietf.org ([130.129.157.108]) by omta02.westchester.pa.mail.comcast.net with comcast id YkEc1n00f2LcPnE3NkEfZ3; Sun, 02 Mar 2014 20:14:43 +0000
Message-ID: <5313912D.9020202@alum.mit.edu>
Date: Sun, 02 Mar 2014 20:14:37 +0000
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: mmusic@ietf.org
References: <7594FB04B1934943A5C02806D1A2204B1D1C4C88@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D1C4C88@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1393791405; bh=CDlW81Tldtj/t8LRZAs6WZBaZtlxs+tV+j4Cj22gvk8=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=hZCPE+/seXJogJwfIc9tJuLFzDgQ0wMqCcVPu++12hsgYxWxSuRc9XWcnlGsNGbto ujNyKrYt0/15CCNX3sF4iqDIkYQPUV5mvuvQtl8ZfqRiY3Bd1rdGw3/mgW6b88i6Xb Q7ak7dXx4sqkYTZQhmcNXznz5eVV4pTQULdjAQmThAYLrG6kMVOdNCFZhCA+h6mUpb sptzjRJq4eVTTTwiKXD0xi/kFPYrZtosTFublFIs4TyfZXEWhc8YCdUtzWwWCgByHX h8ol3+h2i3H0WpEeWRysAe/BJZ8/byjyy3ILI0pVVvK2e7ikwVhfchQJJVjFOX5DCp Ouhlo+klrjaSA==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/VluQNhwlILmS6WKKsWHiaUfkjUM
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: Sun, 02 Mar 2014 20:16:50 -0000

On 3/2/14 4:03 PM, Christer Holmberg wrote:
> Hi,
>
> One of the open issues is what we, in the BUNDLE spec, are going to say
> about de-multiplexing about different media types, and for which (if
> any) media types we are going to specify how the de-multiplexing is done.
>
> We have previously agreed that we are NOT going to describe all
> different possibilities in BUNDLE, and that separate specifications how
> to perform (and, indicate support of) de-multiplexing will have to be
> written. However, we haven’t really agreed on the details.
>
> I intend to suggest the following in London.
>
> In the BUNDLE spec we:
>
> 1)Reference to RFC 5764 for how to de-multiplex DTLS/SRTP/STUN; and
>
> 2)Separate specifications are required to describe how to de-mulitplex
> other media types, and any type of information that needs to be
> exchanged between peers in order to perform the de-multiplexing.
>
> I think that DTLS/SRTP/STUN is going to be the main use-case (not only
> for WebRTC) in the near future, so I think it’s a good approach.

Note that 5764 is sufficient to demux SRTP traffic from DTLS payload 
messages. It doesn't say anything about what those payload messages are 
used for.

It will take another reference to specify that when using proto 
DTLS/SCTP those payload messages are used exclusively for SCTP.

	Thanks,
	Paul


From nobody Sun Mar  2 12:21:53 2014
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 B13C71A0AC7 for <mmusic@ietfa.amsl.com>; Sun,  2 Mar 2014 12:21:50 -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 dMlGOvlL0zfm for <mmusic@ietfa.amsl.com>; Sun,  2 Mar 2014 12:21:49 -0800 (PST)
Received: from sessmg20.mgmt.ericsson.se (sessmg20.ericsson.net [193.180.251.50]) by ietfa.amsl.com (Postfix) with ESMTP id 4D1741A0AC0 for <mmusic@ietf.org>; Sun,  2 Mar 2014 12:21:49 -0800 (PST)
X-AuditID: c1b4fb32-b7f4c8e0000012f5-5b-531392d936b9
Received: from ESESSHC016.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg20.mgmt.ericsson.se (Symantec Mail Security) with SMTP id 60.33.04853.9D293135; Sun,  2 Mar 2014 21:21:46 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.216]) by ESESSHC016.ericsson.se ([153.88.183.66]) with mapi id 14.02.0387.000; Sun, 2 Mar 2014 21:21:45 +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: Ac82MKMUCOeiYc5PSXK9YNe83HDvFwAGwP2AAAI4pFA=
Date: Sun, 2 Mar 2014 20:21:44 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D1C4F63@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D1C4C88@ESESSMB209.ericsson.se> <5313912D.9020202@alum.mit.edu>
In-Reply-To: <5313912D.9020202@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.149]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrALMWRmVeSWpSXmKPExsUyM+Jvje6tScLBBm+O8FhMXf6YxWLFhgOs Dkwef99/YPJYsuQnUwBTFJdNSmpOZllqkb5dAlfGhL/H2Apu81QsaNzK1sA4nauLkZNDQsBE 4uDcf6wQtpjEhXvr2boYuTiEBE4wSqy61MAC4SxmlPiw5h1QFQcHm4CFRPc/bZAGEQFfiWeP b7OB2MICiRJP5p9ih4gnSbT8+cYEYVtJzOufxgxiswioSOxdsJoFZAwvUG/jMTYQU0ggX+LM TA2QCk4BHYlPq1vAOhmBzvl+ag2YzSwgLnHryXwmiDMFJJbsOc8MYYtKvHwMc76SxNrD21kg 6nUkFuz+xAZha0ssW/garJ5XQFDi5MwnLBMYRWchGTsLScssJC2zkLQsYGRZxShZnFpcnJtu ZKCXm55bopdalJlcXJyfp1ecuokRGCsHt/w22sF4co/9IUZpDhYlcd7rrDVBQgLpiSWp2amp BalF8UWlOanFhxiZODilGhiNlujEeM1aY35L59CO75m7d9rPk1X84lxl80dh8ouZrpqFmodK 3jpMrGyxFZJ/s7enn6tTc7rxDcmn7H/vbU4J+zT14LSAN3OC3ke73D+52aa7/j3/2Qd88Y2q VRoLTh6wSp6wKGm6pN3a0xzvJQtsn9z7ZLR3s52rQYqz36bnR6QO/5lY+GaOEktxRqKhFnNR cSIAy/RIvmMCAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/qT291t3WYtzw0kDxmbUbnDcIU4w
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: Sun, 02 Mar 2014 20:21:50 -0000

Hi,

>> One of the open issues is what we, in the BUNDLE spec, are going to=20
>> say about de-multiplexing about different media types, and for which=20
>> (if any) media types we are going to specify how the de-multiplexing is =
done.
>>
>> We have previously agreed that we are NOT going to describe all=20
>> different possibilities in BUNDLE, and that separate specifications=20
>> how to perform (and, indicate support of) de-multiplexing will have to=20
>> be written. However, we haven't really agreed on the details.
>>
>> I intend to suggest the following in London.
>>
>> In the BUNDLE spec we:
>>
>> 1)Reference to RFC 5764 for how to de-multiplex DTLS/SRTP/STUN; and
>>
>> 2)Separate specifications are required to describe how to de-mulitplex=20
>> other media types, and any type of information that needs to be=20
>> exchanged between peers in order to perform the de-multiplexing.
>>
>> I think that DTLS/SRTP/STUN is going to be the main use-case (not only=20
>> for WebRTC) in the near future, so I think it's a good approach.
>
> Note that 5764 is sufficient to demux SRTP traffic from DTLS payload mess=
ages. It doesn't say=20
> anything about what those payload messages are used for.
>
> It will take another reference to specify that when using proto DTLS/SCTP=
 those payload messages > are used exclusively for SCTP.

I am fully aware of that. But, my proposal remains :)

If you want to transport different things (e.g. data channel and something =
else) over DTLS, you need a specification that describes how the separation=
 is done.

Regards,

Christer


From nobody Sun Mar  2 12:55:03 2014
Return-Path: <pkyzivat@alum.mit.edu>
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 426871A0AEB for <mmusic@ietfa.amsl.com>; Sun,  2 Mar 2014 12:55:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] 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 LAbNHjhv8tSk for <mmusic@ietfa.amsl.com>; Sun,  2 Mar 2014 12:55:00 -0800 (PST)
Received: from qmta09.westchester.pa.mail.comcast.net (qmta09.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:96]) by ietfa.amsl.com (Postfix) with ESMTP id AED5F1A0AE3 for <mmusic@ietf.org>; Sun,  2 Mar 2014 12:55:00 -0800 (PST)
Received: from omta16.westchester.pa.mail.comcast.net ([76.96.62.88]) by qmta09.westchester.pa.mail.comcast.net with comcast id YkeX1n0041uE5Es59kuyq4; Sun, 02 Mar 2014 20:54:58 +0000
Received: from dhcp-hotel-wifi-157-6c.meeting.ietf.org ([130.129.157.108]) by omta16.westchester.pa.mail.comcast.net with comcast id YksY1n0052LcPnE3cksa0c; Sun, 02 Mar 2014 20:52:56 +0000
Message-ID: <53139A10.1040502@alum.mit.edu>
Date: Sun, 02 Mar 2014 20:52:32 +0000
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: "Makaraju, Maridi Raju (Raju)" <Raju.Makaraju@alcatel-lucent.com>,  Christer Holmberg <christer.holmberg@ericsson.com>, Mary Barnes <mary.ietf.barnes@gmail.com>,  "mmusic@ietf.org" <mmusic@ietf.org>
References: <7594FB04B1934943A5C02806D1A2204B1D1C0E03@ESESSMB209.ericsson.se>	<CAHBDyN75R1Wr5BODSQ9RNmNP9G7QZdOjZ9Lw+Vz3DCEUUYh4-Q@mail.gmail.com> <CAHBDyN5aDiJHy0fZ3=A8bLyCGAEhSojxu0_kAdLvOTykykE36Q@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1D1C2DF7@ESESSMB209.ericsson.se> <E1FE4C082A89A246A11D7F32A95A17826E003463@US70UWXCHMBA02.zam.alcatel-lucent.com> <7594FB04B1934943A5C02806D1A2204B1D1C3A97@ESESSMB209.ericsson.se> <E1FE4C082A89A246A11D7F32A95A17826E003836@US70UWXCHMBA02.zam.alcatel-lucent.com> <7594FB04B1934943A5C02806D1A2204B1D1C4C1F@ESESSMB209.ericsson.se> <E1FE4C082A89A246A11D7F32A95A17826E003961@US70UWXCHMBA02.zam.alcatel-lucent.com>
In-Reply-To: <E1FE4C082A89A246A11D7F32A95A17826E003961@US70UWXCHMBA02.zam.alcatel-lucent.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1393793698; bh=ICAfARQR+Z/kJuxBYjkSnQ/s4bZOTld2a17SPsywUkg=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=CmITPbz8jdx0Unr9hnrL18lOEAYXRQN9dLQZXjpfC07Pq3wi870YJx1E3oyDGVOXY AO0wPX3t+7hK5apTO/KpMBZnQkjIyt+81Ex2G2RloI4BmTuMBkN6vGF8FEMFGWP40A pUDecm8QFCYUC4PoFjIexiuu/ssqPd9QoeLfmiWgc88es92FSDro6wwjTImFecuOWh cnm6Og8LsSUINWAZmmPu0NPlSOnHwvVI7f6qrkQGRBgA3Mtipc2amtsg93oONaV4EQ crVT8+VwC9KZTyoU/ImHgjD6KWUi9wkezesDgDxT7AZPHb3tXmHLqEsoMka4JXBXF2 anfVbFZyuOLLg==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/pkWTJ9eWc7GRfnyORGe6YG_D4r8
Cc: "DRAGE, Keith \(Keith\)" <keith.drage@alcatel-lucent.com>
Subject: Re: [MMUSIC] IETF#89: First version of CLUE Data Channel slide set.
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: Sun, 02 Mar 2014 20:55:02 -0000

On 3/2/14 5:11 PM, Makaraju, Maridi Raju (Raju) wrote:
> + mmusic to cover some of the discussions.
>
> Hi,
>
> Please see comments inline.
>
> Hi,
>
> For the gateway use-case, do we really need to indicate the SCTP stream
> during Offer/Answer?
>
> Or, would it be enough if we indicate that the data channel is going to
> be used for CLUE, and the gateway then figures out which stream is used
> when it receives DCEP OPEN?
>
> */[Raju] This approach has 2 implications:/*
>
> */1./**//*The gateway needs to look at bearer packets and notify the
> signaling layer about the streams. Though possible, this is
> computationally intensive and new mechanism needed for such notification
> between bearer and signaling layers.
>
> Why does it need to inform the signalling layer about the streams? The
> controller needs to tell the media gateway: “please let CLUE go through”
>
> */[Raju] “Please let CLUE through” is a simple scenario without much
> interworking and other needs./*
>
> */I want to point out couple of other interworking scenarios:/*
>
> */1./*Lawful intercept (LI): A CLUE channel may have to be reported to
> LI agents per regulatory requirements. For various reasons such
> reporting may have to be interworked with non-data channel SCTP/dTLS
> transport (e.g. TCP).

By explicit policy we don't consider lawful intercept in IETF.
The same issue exists for the RTP.

> */2./*For Non-LI reasons, a CLUE could be interworked to a TCP based
> transport in an end-to-access-edge kind of approach.

??? CLUE protocol over TCP? Why? Who will specify that? The intent is to 
use DTLS/SCTP based data channel even when no webrtc in use.

Or do you mean interworking with some non-clue TP protocol?

	Thanks,
	Paul

> In either of these cases, the media gateway will not be aware of how to
> do such interworkings. Even if controller can ask gateway ahead of time
> what to do (in a yet to be defined complex way by protocols like
> H.248/Megaco) then still gateway have to report the TCP transport
> address back to controller so that it can inform LI agents about this
> address.
>
> Essentially, not having external negotiation will complicate other
> protocols (like H.248/Megaco MG-MGC protocol) and still won’t avoid
> per-data channel notification to the signaling entity (controller).
> Please note that such “media gateway centric/driven” complex procedures
> may not even be allowed by H.248/Megaco as controllers wants be the one
> making such decisions as they happen.
>
> */2./**//*There could be several streams using the same subprotocol.
> Then how does gateway know which maps to what? CLUE may have just one
> data channel stream; but we may also have to think about CLUE combined
> with other data channels under same SCTP association. Even for single
> CLUE stream case item (1) is still an issue though.
>
> The gateway is going to get DCEP for each subprotocol, so it knows which
> one is CLUE.
>
> */[Raju] As noted, since in this specific case there is one single CLUE
> data channel a gateway unambigously can map. But still the above
> mentioned interworking requires controller involvement as the data
> channels are open./*
>
> *//*
>
> */Regards/*
>
> */Raju/*
>
> Regards,
>
> Christer
>


From nobody Sun Mar  2 13:32:52 2014
Return-Path: <pkyzivat@alum.mit.edu>
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 6C65F1A0B1A for <mmusic@ietfa.amsl.com>; Sun,  2 Mar 2014 13:32:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] 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 w_ECwG1n75jb for <mmusic@ietfa.amsl.com>; Sun,  2 Mar 2014 13:32:47 -0800 (PST)
Received: from qmta12.westchester.pa.mail.comcast.net (qmta12.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:227]) by ietfa.amsl.com (Postfix) with ESMTP id 187981A0B18 for <mmusic@ietf.org>; Sun,  2 Mar 2014 13:32:46 -0800 (PST)
Received: from omta11.westchester.pa.mail.comcast.net ([76.96.62.36]) by qmta12.westchester.pa.mail.comcast.net with comcast id Ykgy1n0070mv7h05ClYkeW; Sun, 02 Mar 2014 21:32:44 +0000
Received: from dhcp-hotel-wifi-157-6c.meeting.ietf.org ([130.129.157.108]) by omta11.westchester.pa.mail.comcast.net with comcast id YlWY1n00T2LcPnE3XlWbRY; Sun, 02 Mar 2014 21:30:42 +0000
Message-ID: <5313A2F9.6000507@alum.mit.edu>
Date: Sun, 02 Mar 2014 21:30:33 +0000
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>,  "mmusic@ietf.org" <mmusic@ietf.org>
References: <7594FB04B1934943A5C02806D1A2204B1D1C4C88@ESESSMB209.ericsson.se> <5313912D.9020202@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D1C4F63@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D1C4F63@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1393795964; bh=HtSwPDDgv99COjJY5M3Z00DsyjLKdKUmNto24CBuj9g=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=rnBRmM2VUh9KAGIoYIzbVQtc+19VPKCm+Y8W3Y5L00B7hHI0BhQVJ2hb/Nykeh91z 6QhKegpO8TndsxaGHyX8eH9QAT9CW40ODikjzIQWvt2Z/XZJl5Vsxh4Fjafvx4Gfh7 pt2TpGy1H1gCEGn9doH3JUCCUqQjGfKp+DMbsZMkTo8O71i4gXiOaWq8lvSVuqp71D IUI/qXci6K80JIaz32T30Oq5P0+Z/5kcVozRyIoB8gAoMcVdVSj1LoQfj9XhJos7+f oiv4x8Wk68HMSKUitIJ/Zj5d8x1lNxd0LaFxdQYKRf7RrVbJYvbp2i8S3/BmkqjYEg FoWOqZdtJW9Ow==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/5hFAQWjf8GQ9T_NVlIhN1wA8CDA
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: Sun, 02 Mar 2014 21:32:48 -0000

Christer,

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.

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

	Thanks,
	Paul

On 3/2/14 8:21 PM, Christer Holmberg wrote:
> Hi,
>
>>> One of the open issues is what we, in the BUNDLE spec, are going to
>>> say about de-multiplexing about different media types, and for which
>>> (if any) media types we are going to specify how the de-multiplexing is done.
>>>
>>> We have previously agreed that we are NOT going to describe all
>>> different possibilities in BUNDLE, and that separate specifications
>>> how to perform (and, indicate support of) de-multiplexing will have to
>>> be written. However, we haven't really agreed on the details.
>>>
>>> I intend to suggest the following in London.
>>>
>>> In the BUNDLE spec we:
>>>
>>> 1)Reference to RFC 5764 for how to de-multiplex DTLS/SRTP/STUN; and
>>>
>>> 2)Separate specifications are required to describe how to de-mulitplex
>>> other media types, and any type of information that needs to be
>>> exchanged between peers in order to perform the de-multiplexing.
>>>
>>> I think that DTLS/SRTP/STUN is going to be the main use-case (not only
>>> for WebRTC) in the near future, so I think it's a good approach.
>>
>> Note that 5764 is sufficient to demux SRTP traffic from DTLS payload messages. It doesn't say
>> anything about what those payload messages are used for.
>>
>> It will take another reference to specify that when using proto DTLS/SCTP those payload messages > are used exclusively for SCTP.
>
> I am fully aware of that. But, my proposal remains :)
>
> If you want to transport different things (e.g. data channel and something else) over DTLS, you need a specification that describes how the separation is done.
>
> Regards,
>
> Christer
>
>


From nobody Sun Mar  2 13:59:07 2014
Return-Path: <pkyzivat@alum.mit.edu>
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 60BD41A0B31 for <mmusic@ietfa.amsl.com>; Sun,  2 Mar 2014 13:59:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.635
X-Spam-Level: 
X-Spam-Status: No, score=-0.635 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, J_CHICKENPOX_15=0.6, SPF_SOFTFAIL=0.665] 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 K-at8war_Qcb for <mmusic@ietfa.amsl.com>; Sun,  2 Mar 2014 13:59:00 -0800 (PST)
Received: from qmta12.westchester.pa.mail.comcast.net (qmta12.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:227]) by ietfa.amsl.com (Postfix) with ESMTP id A9EA21A0B44 for <mmusic@ietf.org>; Sun,  2 Mar 2014 13:59:00 -0800 (PST)
Received: from omta24.westchester.pa.mail.comcast.net ([76.96.62.76]) by qmta12.westchester.pa.mail.comcast.net with comcast id YlNh1n0031ei1Bg5Clyydh; Sun, 02 Mar 2014 21:58:58 +0000
Received: from dhcp-hotel-wifi-157-6c.meeting.ietf.org ([130.129.157.108]) by omta24.westchester.pa.mail.comcast.net with comcast id Ylwj1n00W2LcPnE3klwlwd; Sun, 02 Mar 2014 21:56:56 +0000
Message-ID: <5313A91C.2030407@alum.mit.edu>
Date: Sun, 02 Mar 2014 21:56:44 +0000
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: "Makaraju, Maridi Raju (Raju)" <Raju.Makaraju@alcatel-lucent.com>,  Christer Holmberg <christer.holmberg@ericsson.com>, "mmusic@ietf.org" <mmusic@ietf.org>, "rtcweb@ietf.org" <rtcweb@ietf.org>
References: <7594FB04B1934943A5C02806D1A2204B1D1BC516@ESESSMB209.ericsson.se> <CAJuyhsyk4jO_TS=5khD9ROAx7uYU1YAkCV0Xy4QVUkiqXBJJfg@mail.gmail.com> <E1FE4C082A89A246A11D7F32A95A17826DFFB545@US70UWXCHMBA02.zam.alcatel-lucent.com> <530E4E34.4010707@alum.mit.edu> <E1FE4C082A89A246A11D7F32A95A17826DFFEDAB@US70UWXCHMBA02.zam.alcatel-lucent.com> <7594FB04B1934943A5C02806D1A2204B1D1C023A@ESESSMB209.ericsson.se> <E1FE4C082A89A246A11D7F32A95A17826DFFF2E4@US70UWXCHMBA02.zam.alcatel-lucent.com> <5310B14E.4000809@alum.mit.edu> <E1FE4C082A89A246A11D7F32A95A17826E0011F6@US70UWXCHMBA02.zam.alcatel-lucent.com>
In-Reply-To: <E1FE4C082A89A246A11D7F32A95A17826E0011F6@US70UWXCHMBA02.zam.alcatel-lucent.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1393797538; bh=mDLs93P4I8OW62UI7nMzZhDhtW0DubkRJG0wN3OwNl0=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=nRElNnjkn+nAumbwdFqN1eiDMqCcfKUrDL/ozUS+T51X1MOCJYUbU5UgOegk/c8ob 4qx41HgnO0t/ey7WjjN0CVJgyPHoG49hJurVw8x/bfnDXjc8crDwhEbe6ks08sCNmh 0Kx8+US4Pbjmm6yCP7jDI5aF8m8lKovd/2WtSOGgPkfcIDPHJBo26P2PPLXaEOE0pc +TwxqE0vU7fJ5p7c1I16PeOxzq20Vuru2UZxapcgQfSwZgtpWukNUOv/M+LoOp9xRG HavCoXd/nZ15Fvl/4jLQ9iJ8MlMS/UbeF6i4HROYpAmVzykjLmHnIoQdIv1PD66NTV YvkzGWnGg/2xA==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/iSGn69QCf8JHNi0HDYrh7dH7GEY
Subject: Re: [MMUSIC] draft-ejzak-mmusic-data-channel-sdpneg: external rejection of channel
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: Sun, 02 Mar 2014 21:59:02 -0000

I suspect we are not understanding one another.

On 2/28/14 4:46 PM, Makaraju, Maridi Raju (Raju) wrote:
> Hi Paul,
>
>
>>>> Isn't it enough to, in the data channel protocol spec, say that the
>> odd/even
>>>> rule applies unless the stream id is explicitly negotiated using some
>> other
>>>> mechanism?
>>>>
>>> [Raju] Yes, that is sufficient from DCP draft. draft-ejzak-mmusic-data-
>> channel-sdpneg should still need to say that "when both external and DCP are
>> used, even for DCP created streams the stream ids have to be specified and
>> managed by the application (else DCP stack will default to odd/even rule per
>> DTLS role which may conflict with SDP offer/answer rule)".
>>
>> Can we assume there must be a mechanism for using DCEP and still
>> controlling which channels are used?
>
> [Raju] Yes, we can assume that and it is already supported by :
> http://tools.ietf.org/html/draft-ietf-rtcweb-data-channel-07#section-6.5
> and
> http://dev.w3.org/2011/webrtc/editor/webrtc.html#widl-RTCDataChannel-id
> I believe it is safe to assume non-browser implementations of
> data channel stack gives an option for application to select
> stream ids independent of DCEP or external negotiation.
>
>
>>
>> It might help if the O/A negotiation also followed the even/odd rule.
> [Raju] May be I am missing something here. Richard's draft already has
> a specific even/odd rule for O/A. But the issue is TLS based rule may
> conflict with the O/A rule as TLS roles may change depending on a=setup.
>
>> But there are difficulties in knowing who is even and who is odd for the
>> first O/A.
>
> [Raju] Not related to first or subsequent O/A, but rather a conflict
> between TLS roles vs. O/A.

OK. I didn't state what I meant clearly, and I forgot Richard had an 
even/odd rule. For O/A there really isn't a need for one, since the only 
cases this will be a problem result in O/A glare, and that is then 
resolved via backoff.

What I meant was it might help if the O/A proposal and DCEP followed the 
*same* rule. I think that is what Richard wanted. But he showed why O/A 
can't use the existing DCEP rule, so *that* would be required to change.

>> If the offerer always creates the channel before sending the offer, then
>> that will prevent the two mechanisms from stepping on one another's
>> stream ids.
> [Raju]
> In some cases, initial offer may not have a data channel stream created.
> I don't know how this can prevent stepping on each other?!
> May be I am missing something here?! In most cases TLS role is
> determined after O/A is completed, but offerer creates a data
> channel before answer, then how does it know even/odd rule?
> So, trying to use TLS role for external negotiation is problematic.

For channels negotiated at the same time the SCTP association is 
negotiated the offerer can use *any* ids, since there can yet be no 
conflict.

Then, once the association is established, the channels declared in the 
SDP need to be "opened" (activated?), independently by both sides. They 
will then be reserved.

After that, if the application follows the DCEP even/odd rule, and 
creates the channel at its end before sending an offer, then that cannot 
conflict with channels dynamically allocated by DCEP. And both sides 
then understand who is even and who is odd, so there will be no 
conflicts by the two sides choosing the same channel.

	Thanks,
	Paul


From nobody Sun Mar  2 14:22:55 2014
Return-Path: <ari.keranen@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 26DFD1A0B5D for <mmusic@ietfa.amsl.com>; Sun,  2 Mar 2014 14:22:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.551
X-Spam-Level: 
X-Spam-Status: No, score=-3.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 IaURkVFa3L6P for <mmusic@ietfa.amsl.com>; Sun,  2 Mar 2014 14:22:51 -0800 (PST)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 5023F1A0B5E for <mmusic@ietf.org>; Sun,  2 Mar 2014 14:22:50 -0800 (PST)
X-AuditID: c1b4fb2d-b7f5d8e000002a7b-7a-5313af362aaf
Received: from ESESSHC020.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id EF.F8.10875.63FA3135; Sun,  2 Mar 2014 23:22:46 +0100 (CET)
Received: from ESESSMB205.ericsson.se ([169.254.5.210]) by ESESSHC020.ericsson.se ([153.88.183.78]) with mapi id 14.02.0387.000; Sun, 2 Mar 2014 23:22:46 +0100
From: =?iso-8859-1?Q?Ari_Ker=E4nen?= <ari.keranen@ericsson.com>
To: "Stach, Thomas" <thomas.stach@unify.com>
Thread-Topic: Comment on the ICE updated offer procedures
Thread-Index: Ac82UynstLVpW+NhS5ORd1Q4pZhv3QACmLsA
Date: Sun, 2 Mar 2014 22:22:44 +0000
Message-ID: <1ECDA76B-D54B-4DF2-BE1C-A826B18F28AD@ericsson.com>
References: <F81CEE99482EFE438DAE2A652361EE1217A537BC@MCHP04MSX.global-ad.net>
In-Reply-To: <F81CEE99482EFE438DAE2A652361EE1217A537BC@MCHP04MSX.global-ad.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.148]
Content-Type: multipart/signed; boundary="Apple-Mail=_5647F6B5-9B9E-4487-ADBA-682046349A1B"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrPLMWRmVeSWpSXmKPExsUyM+Jvja7ZeuFgg1s3zC2mLn/MYnFy5zZm ByaPJUt+Mnls73nMEsAUxWWTkpqTWZZapG+XwJVx9OcZloKrphX3f+5gbGC8YtTFyMkhIWAi cf/xbhYIW0ziwr31bF2MXBxCAocYJe6v/gGWEBJYzCjxe5YniM0mYC8xec1HRhBbREBHYvbM x+xdjBwczALqElcXB4GEhQUsJO5M72WCKLGU2PzwLwuEbSQx6etvMJtFQEVi6tcesFZeoJEn X3uDmEICfhITumNBKjgF/CXu3dgIVs0IdNn3U2vAJjILiEvcejKfCeJiEYmHF0+zQdiiEi8f /2OFsJUkGpc8YQX5hFlgCqPEpNbj7CAJXgFBiZMzn7BMYBSdhWTWLGR1s5DUQRRpSyxb+JoZ wtaTeNn0jh3CNpV4ffQjI4RtLTHj10E2CFtRYkr3Q/YFjByrGNlzEzNz0ssNNzECI+3glt+6 OxhPnRM5xCjNwaIkzvvhrXOQkEB6YklqdmpqQWpRfFFpTmrxIUYmDk6pBkaJWPsd9/tNdENe lqoFSZyTZLixy0NUMfWcyJEW+ydPI25sWp86/8y6xgPSq3+qem/kCvl4/yIbx8lZDdOSrs7Y XPCmO0pq9Vcr4SPxi1d0L+mImdEmKeYQlJpe/4ul5d6pLd8YSu8lhl+PuXLOV7VnvY99UBbb be0eJZ6pp8yMs+9UPQpZfkOJpTgj0VCLuag4EQCNg/61ggIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/NUwxvteBZaGdWu9E2ryxdxKLgYY
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Comment on the ICE updated offer procedures
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: Sun, 02 Mar 2014 22:22:53 -0000

--Apple-Mail=_5647F6B5-9B9E-4487-ADBA-682046349A1B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

Hi Thomas,

On Mar 2, 2014, at 8:08 PM, Stach, Thomas wrote:
> the slides  for IETF 89 propose that always an updated offer shall be =
sent.
> You also mention the issues with that as listed in =
draft-elwell-mmusic-ice-updated-offer.
> This was also discussed in IETF 80.
> Draft-elwell-mmusic-ice-updated-offer acknowledges that there are =
middle boxes that need such updated offer to work properly.
> However, there are also cases and other types of middle boxes that =
break or show undesirable behavior, just because of the updated offer.
> Because of these issues, I think that always sending the updated offer =
should not be required.
> Instead, it should be made configurable if the updated offer is sent =
or not sent, possibly together with some signaling =
(ice-options/ice-options-required?) which behavior is to be applied.

Having this configurable and defaulting to always doing the updated =
offer makes sense to me. And perhaps this should be then signaled in an =
ice-options-optional since it should not affect whether aggressive =
nomination can be used or not.


Cheers,
Ari=

--Apple-Mail=_5647F6B5-9B9E-4487-ADBA-682046349A1B
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIM5zCCBCkw
ggMRoAMCAQICEHUXW0wyaUIpWRrHJ12Tze0wDQYJKoZIhvcNAQEFBQAwOTERMA8GA1UECgwIRXJp
Y3Nzb24xJDAiBgNVBAMMG0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMTAeFw0xMTA4MjkxMDE3
NTVaFw0xNDA4MjkxMDE3NTNaMGQxETAPBgNVBAoMCEVyaWNzc29uMRQwEgYDVQQDDAtBcmkgS2Vy
YW5lbjEQMA4GA1UEBRMHZWFyaWtlcjEnMCUGCSqGSIb3DQEJARYYYXJpLmtlcmFuZW5AZXJpY3Nz
b24uY29tMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCm4x97wE30RDy+zuTcBMTX8qP50L+I
Esx/fO+aFCKlJJtrO1OJaEvX7IGXnYK2ncKwKwxchOWpaDKSqwEf1kH/Eh+d+TGn6x4+gG6HDhHG
sOqRz5NsWPMOpAohgJKKlG4qeeUzKVnWWPmscZD+JvLZI2sNSE+3SEASAFxVbTUrfwIDAQABo4IB
hDCCAYAwgcAGA1UdHwSBuDCBtTCBsqCBr6CBrIY3aHR0cDovL2NybC50cnVzdC50ZWxpYS5jb20v
RXJpY3Nzb25OTEluZGl2aWR1YWxDQTAxLmNybIZxbGRhcDovL2xkYXAudHJ1c3QudGVsaWEuY29t
L2NuPUVyaWNzc29uJTIwTkwlMjBJbmRpdmlkdWFsJTIwQ0EwMSxvPUVyaWNzc29uP2NlcnRpZmlj
YXRlcmV2b2NhdGlvbmxpc3Q7YmluYXJ5P2Jhc2UwIwYDVR0RBBwwGoEYYXJpLmtlcmFuZW5AZXJp
Y3Nzb24uY29tMEYGA1UdIAQ/MD0wOwYGKoVwawEBMDEwLwYIKwYBBQUHAgEWI2h0dHA6Ly93d3cu
ZXJpY3Nzb24uY29tL2xlZ2FsLnNodG1sMB0GA1UdDgQWBBQu6W+n7/tHp8pbgczjKSXcAoV7VTAf
BgNVHSMEGDAWgBSWJ8O43qVfXUQ+OVLlRbF2X2MwmzAOBgNVHQ8BAf8EBAMCBaAwDQYJKoZIhvcN
AQEFBQADggEBAFJiqLOimWRaFtpwgOpZgo/wqN9bPEewLl2z1+iv2WU3DnOGXmf4/e0IgpfvGtJX
gYnGPql87Cd+jIccHRoq2Z83cjcXyoY1TK0tMe4uhHV87UnmEUN5ewlWnyP4rlzBfO/BBTXA5S17
PsogWaaIvuy0IHTkbYj03sZ8nB4O/UDpSj2hfzcycyne0Y7bTEQY/OZRRbC1sWVQEkA8rOrn5+AR
Wc+qrugsgPYi8iamXdzgxJaCDsSTdzC9gQl1h8pwRr64H1ybkD4Y4K6Gri4+AvHHBIWBjQod9vhC
lRnUbFoFnHnhbcT2rg4JPxmjxtCvQ5q9LCTL0EeCOBZWb6WMxMEwggRFMIIDLaADAgECAhATyer/
3iatqdykyiOBg0fjMA0GCSqGSIb3DQEBBQUAMEQxGjAYBgNVBAoMEVRlbGlhU29uZXJhIEdyb3Vw
MSYwJAYDVQQDDB1UZWxpYVNvbmVyYSBQdWJsaWMgUm9vdCBDQSB2MTAeFw0wNjEwMDYxMDAwNTNa
Fw0xNjEwMDIwNTA0MTdaMDkxETAPBgNVBAoMCEVyaWNzc29uMSQwIgYDVQQDDBtFcmljc3NvbiBO
TCBJbmRpdmlkdWFsIENBMDEwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC2EHfkNR7r
h8Q8jRhZRD8wsbjzxTuVtscq/p6glZzSeEGBXtRwAqmr6jS8FBiKiBMh79ay537m/SwXO3UKUR45
f3YIIp9DjThSd+p2xhG3x4yyc9gczlr8JfOEnPhcdPSKw1P0mUlhUn4ak7t009/Ye/W6x3UZHTwV
IAWILIhSq4hyNE4z+RvOtvB9uwQ86lKcxi0mFoLev7acLjh+ZXHzXx1jHAmF0ZaG79CpbvJcRuWp
lqgJ6qx+hAjsmCU0Wx07GkyGTh8vUMP9Hlz7oyk+7VOccUiNknXHias1GwM9qBUUOj8e/xsnaTP0
ZfqmKBj3Grh1C9WknlSWagxanCBdAgMBAAGjggE8MIIBODASBgNVHRMBAf8ECDAGAQH/AgEAMEYG
A1UdIAQ/MD0wOwYHKoVwIwIBATAwMC4GCCsGAQUFBwIBFiJodHRwczovL3JlcG9zaXRvcnkudHJ1
c3QudGVsaWEuY29tMIGJBgNVHR8EgYEwfzB9oHugeYZ3bGRhcDovL2xkYXAudHJ1c3QudGVsaWEu
Y29tL2NuPVRlbGlhU29uZXJhJTIwUHVibGljJTIwUm9vdCUyMENBJTIwdjEsbz1UZWxpYVNvbmVy
YSUyMEdyb3VwP2F1dGhvcml0eXJldm9jYXRpb25saXN0P2Jhc2UwDgYDVR0PAQH/BAQDAgEGMB0G
A1UdDgQWBBSWJ8O43qVfXUQ+OVLlRbF2X2MwmzAfBgNVHSMEGDAWgBRF2/CPuBpioagjG2OIOKPb
4Bpi8TANBgkqhkiG9w0BAQUFAAOCAQEAdgBKKkM/jN0WvWpZKZ/2J8IVyL+rT44VL0rjbNNDYXdE
/V4ZSFN2uuQmgf1Ckqp2shNLe0NEKt6/sfxit4p/5opPIvzytv6vB7rc2BUs8+jac7aaNiRuwBCj
iT1Wnnm454OOZurzQu0SH81PbBtiwUf4XsEvLOnRRZ+9MO/ecVMCQVmeuzsyCl6yFVbx0zmKW1gP
jBEigF8BYZ1Tjazk1pVcKzFIuB24j1qTpPsUG4HoQhIu5rt3F7GlNV6t5DF7ojbgu1SqKG/JhTva
PUU/nZYqw9rkV8Dabwrt27reisobtPp78tolxio3ZcZVk7HQ8rpV2M/jmAjGfZRVkczCDzCCBG0w
ggNVoAMCAQICEQCcsIwEmsuXInhjYrYbhlo9MA0GCSqGSIb3DQEBBQUAMDoxGTAXBgNVBAoTEFJT
QSBTZWN1cml0eSBJbmMxHTAbBgNVBAsTFFJTQSBTZWN1cml0eSAyMDQ4IFYzMB4XDTA2MTAzMTIw
NDIyN1oXDTE2MTEwMTE1NDIyNVowRDEaMBgGA1UECgwRVGVsaWFTb25lcmEgR3JvdXAxJjAkBgNV
BAMMHVRlbGlhU29uZXJhIFB1YmxpYyBSb290IENBIHYxMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8A
MIIBCgKCAQEAyk8QA2qQgKt5qZV+EeIDbflmXuUChp2lREEsmO5SAiheQ7lXVjzCxw484cOSMw3f
OtGWcf9Fa4Rgdw5j+EgyFgiqNj8b2OTXJHQVj1qf09rmkHTgMIKh6TdKXtV+/43pefVrFmFyhoP/
NVrYe92Sv4HhOxs/T749S1OjeGISzIKKMSpwkvmYweYnFgIPkHdUKUIReOh9Ym6ei7AVg6eejD6Y
PBeV+suzBlXCmC3Zyzj7POLsUVvarNZAaKc0AY+rOUslYfAPo+ZYgwY4IV2KcP/qWhhHahz3khWM
WSniWrZoxCi2JcXGVkSn+N+ir0APYwYTBJsrTDWxonEdZkR+rQIDAQABo4IBYjCCAV4wHwYDVR0j
BBgwFoAUB8NRMKSq6UWuNST6/yQsM9CxnYwwHQYDVR0OBBYEFEXb8I+4GmKhqCMbY4g4o9vgGmLx
MBIGA1UdEwEB/wQIMAYBAf8CAQQwgYUGA1UdIAR+MHwwPQYJKoZIhvcNBQYBMDAwLgYIKwYBBQUH
AgEWImh0dHBzOi8vcmVwb3NpdG9yeS50cnVzdC50ZWxpYS5jb20wOwYHKoVwIwIBATAwMC4GCCsG
AQUFBwIBFiJodHRwczovL3JlcG9zaXRvcnkudHJ1c3QudGVsaWEuY29tMHAGA1UdHwRpMGcwZaBj
oGGGX2h0dHA6Ly93d3cucnNhc2VjdXJpdHkuY29tL3Byb2R1Y3RzL2tlb24vcmVwb3NpdG9yeS9j
ZXJ0aWZpY2F0ZV9zdGF0dXMvUlNBX1NlY3VyaXR5XzIwNDhfdjMuQ1JMMA4GA1UdDwEB/wQEAwIB
BjANBgkqhkiG9w0BAQUFAAOCAQEABF6aLNgpyJu//O9srUqxB1mYL4TlBJFJtuT1n/15FpKONU2i
/byEtUugHVgoTalpp2Ikuxn2iIgzPbNQ+iu4YnVgQzpuOmzXTN2cITMgwn5AyUoHidMPu2Jo7wob
u4Fqg2QrG7WeYANYsQk3Q57mQeuyRkjxluq+93KK2gz/HYjqYkKLjLzOmyrkzwR/9aaC3HLFMbCo
K0NtyQvS1gkW/HGB5GY1xR9SuOE7CJeS53tqE9CSN6cHQNr+ozuKfzix57T/p6Y8D23nTD1GZA2A
pHdy0sY/HNyU8bQPEpTwrSBxNYYeucYoYNSUSJYkqYa6q/ZG38B3XlcT3TiORrQ2DzGCAhIwggIO
AgEBME0wOTERMA8GA1UECgwIRXJpY3Nzb24xJDAiBgNVBAMMG0VyaWNzc29uIE5MIEluZGl2aWR1
YWwgQ0EwMQIQdRdbTDJpQilZGscnXZPN7TAJBgUrDgMCGgUAoIIBGzAYBgkqhkiG9w0BCQMxCwYJ
KoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xNDAzMDIyMjIyNDRaMCMGCSqGSIb3DQEJBDEWBBTn
SfumjmHq8qyTIuAVwkucy+fNujBcBgkrBgEEAYI3EAQxTzBNMDkxETAPBgNVBAoMCEVyaWNzc29u
MSQwIgYDVQQDDBtFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBMDECEHUXW0wyaUIpWRrHJ12Tze0w
XgYLKoZIhvcNAQkQAgsxT6BNMDkxETAPBgNVBAoMCEVyaWNzc29uMSQwIgYDVQQDDBtFcmljc3Nv
biBOTCBJbmRpdmlkdWFsIENBMDECEHUXW0wyaUIpWRrHJ12Tze0wDQYJKoZIhvcNAQEBBQAEgYBs
5p1TpiFi9tI+pNDh+eDd09d0JMg2GmhhioZtUAgpktqewItVHbiYCcKnyA1bRrXKLvTFZ2c8MFvz
GOjQFnCZz+aWg/mqMcpn65aX+cB+kBwVKs4nqmeaiNRLNP4ycB9AGr+yw13JEGjt7LDnbIV7p5zM
cQwstFNx9wcCsi91aAAAAAAAAA==

--Apple-Mail=_5647F6B5-9B9E-4487-ADBA-682046349A1B--


From nobody Sun Mar  2 14:47:01 2014
Return-Path: <jonathan@vidyo.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 403D81A0932 for <mmusic@ietfa.amsl.com>; Sun,  2 Mar 2014 14:47:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 K33nL1TMfkNe for <mmusic@ietfa.amsl.com>; Sun,  2 Mar 2014 14:46:57 -0800 (PST)
Received: from server209.appriver.com (server209g.appriver.com [8.31.233.122]) by ietfa.amsl.com (Postfix) with ESMTP id 8058E1A0202 for <mmusic@ietf.org>; Sun,  2 Mar 2014 14:46:57 -0800 (PST)
X-Note-AR-ScanTimeLocal: 3/2/2014 5:46:54 PM
X-Policy: GLOBAL - vidyo.com
X-Policy: GLOBAL - vidyo.com
X-Primary: jonathan@vidyo.com
X-Note: This Email was scanned by AppRiver SecureTide
X-Virus-Scan: V-
X-Note-SnifferID: 0
X-Note: TCH-CT/SI:0-80/SG:5 3/2/2014 5:46:17 PM
X-GBUdb-Analysis: 0, 162.209.16.213, Ugly c=0.841003 p=-0.988578 Source White
X-Signature-Violations: 0-0-0-14432-c
X-Note-419: 15.6003 ms. Fail:0 Chk:1345 of 1345 total
X-Note: SCH-CT/SI:0-1345/SG:1 3/2/2014 5:46:43 PM
X-Note: Spam Tests Failed: 
X-Country-Path: ->UNITED STATES->LOCAL
X-Note-Sending-IP: 162.209.16.213
X-Note-Reverse-DNS: mail2.vidyo.com
X-Note-Return-Path: jonathan@vidyo.com
X-Note: User Rule Hits: 
X-Note: Global Rule Hits: G327 G328 G329 G330 G334 G335 G445 
X-Note: Encrypt Rule Hits: 
X-Note: Mail Class: VALID
X-Note: Headers Injected
Received: from [162.209.16.213] (HELO mail.vidyo.com) by server209.appriver.com (CommuniGate Pro SMTP 6.0.8) with ESMTPS id 76593803; Sun, 02 Mar 2014 17:46:54 -0500
Received: from 492133-EXCH2.vidyo.com ([fe80::50:56ff:fe85:6b62]) by 492132-EXCH1.vidyo.com ([fe80::50:56ff:fe85:4f77%13]) with mapi id 14.03.0146.000; Sun, 2 Mar 2014 16:46:53 -0600
From: Jonathan Lennox <jonathan@vidyo.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Thread-Topic: [MMUSIC] IETF#89: BUNDLE: Q12: Scope of non-RTP media de-mux procedures in BUNDLE?
Thread-Index: Ac82MKMUCOeiYc5PSXK9YNe83HDvFwAavSeA
Date: Sun, 2 Mar 2014 22:46:52 +0000
Message-ID: <822454EF-2BBF-4C9A-8ADE-734F3643120B@vidyo.com>
References: <7594FB04B1934943A5C02806D1A2204B1D1C4C88@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D1C4C88@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [130.129.3.252]
Content-Type: multipart/alternative; boundary="_000_822454EF2BBF4C9A8ADE734F3643120Bvidyocom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/KT_TIg6O_2av5EKkfuMRNlcWix8
Cc: mmusic <mmusic@ietf.org>
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: Sun, 02 Mar 2014 22:47:00 -0000

--_000_822454EF2BBF4C9A8ADE734F3643120Bvidyocom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable



On Mar 2, 2014, at 4:03 PM, Christer Holmberg <christer.holmberg@ericsson.c=
om<mailto:christer.holmberg@ericsson.com>> wrote:

Hi,

One of the open issues is what we, in the BUNDLE spec, are going to say abo=
ut de-multiplexing about different media types, and for which (if any) medi=
a types we are going to specify how the de-multiplexing is done.

We have previously agreed that we are NOT going to describe all different p=
ossibilities in BUNDLE, and that separate specifications how to perform (an=
d, indicate support of) de-multiplexing will have to be written. However, w=
e haven=92t really agreed on the details.

I intend to suggest the following in London.

In the BUNDLE spec we:

1)      Reference to RFC 5764 for how to de-multiplex DTLS/SRTP/STUN; and
2)      Separate specifications are required to describe how to de-mulitple=
x other media types, and any type of information that needs to be exchanged=
 between peers in order to perform the de-multiplexing.

In addition to this, I think BUNDLE should say explicitly that: You MUST NO=
T send an offer or answer with a bundle you don=92t know how to de-multiple=
x (or multiplex).  If you receive an offer for a bundle you don=92t know ho=
w to mux or de-mux, you MUST unbundle or reject m-lines so you know how to =
mux and demux the remaining bundle, or reject the offer.

I=92m uncertain how explicitly this should define =93know how to=94, i.e. i=
f the procedure has to be a normative spec.  I could imagine a scenario whe=
re there are multiple possibilities as to how to mix or de-mux two protocol=
s (e.g., by restricting some field in one or the other protocol to a subset=
 of its valid values, and there are multiple ways to pick the subsets), and=
 if two endpoints have different approaches to muxing/de-muxing you would h=
ave interop failures.


I think that DTLS/SRTP/STUN is going to be the main use-case (not only for =
WebRTC) in the near future, so I think it=92s a good approach.

Regards,

Christer
_______________________________________________
mmusic mailing list
mmusic@ietf.org<mailto:mmusic@ietf.org>
https://www.ietf.org/mailman/listinfo/mmusic


--_000_822454EF2BBF4C9A8ADE734F3643120Bvidyocom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <9C756344C9FD9A479D9C02220934364A@vidyo.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space;">
<div><br>
</div>
<br>
<div>
<div>On Mar 2, 2014, at 4:03 PM, Christer Holmberg &lt;<a href=3D"mailto:ch=
rister.holmberg@ericsson.com">christer.holmberg@ericsson.com</a>&gt; wrote:=
</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite">
<div lang=3D"EN-GB" link=3D"#0563C1" vlink=3D"#954F72" style=3D"font-family=
: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; fon=
t-weight: normal; letter-spacing: normal; line-height: normal; orphans: aut=
o; text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">
<div class=3D"WordSection1" style=3D"page: WordSection1;">
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif;">
Hi,<o:p></o:p></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif;">
<o:p>&nbsp;</o:p></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif;">
One of the open issues is what we, in the BUNDLE spec, are going to say abo=
ut de-multiplexing about different media types, and for which (if any) medi=
a types we are going to specify how the de-multiplexing is done.<o:p></o:p>=
</div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif;">
<o:p>&nbsp;</o:p></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif;">
We have previously agreed that we are NOT going to describe all different p=
ossibilities in BUNDLE, and that separate specifications how to perform (an=
d, indicate support of) de-multiplexing will have to be written. However, w=
e haven=92t really agreed on the details.<o:p></o:p></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif;">
<o:p>&nbsp;</o:p></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif;">
I intend to suggest the following in London.<o:p></o:p></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif;">
<o:p>&nbsp;</o:p></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif;">
In the BUNDLE spec we:<o:p></o:p></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif;">
<o:p>&nbsp;</o:p></div>
<div style=3D"margin: 0cm 0cm 0.0001pt 36pt; font-size: 11pt; font-family: =
Calibri, sans-serif; text-indent: -18pt;">
<span>1)<span style=3D"font-style: normal; font-variant: normal; font-weigh=
t: normal; font-size: 7pt; line-height: normal; font-family: 'Times New Rom=
an';">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<span class=3D"Apple-converted-space">&=
nbsp;</span></span></span>Reference to RFC 5764 for how to de-multiplex
 DTLS/SRTP/STUN; and<o:p></o:p></div>
<div style=3D"margin: 0cm 0cm 0.0001pt 36pt; font-size: 11pt; font-family: =
Calibri, sans-serif; text-indent: -18pt;">
<span>2)<span style=3D"font-style: normal; font-variant: normal; font-weigh=
t: normal; font-size: 7pt; line-height: normal; font-family: 'Times New Rom=
an';">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<span class=3D"Apple-converted-space">&=
nbsp;</span></span></span>Separate specifications are required to
 describe how to de-mulitplex other media types, and any type of informatio=
n that needs to be exchanged between peers in order to perform the de-multi=
plexing.</div>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>In addition to this, I think BUNDLE should say explicitly that: You MU=
ST NOT send an offer or answer with a bundle you don=92t know how to de-mul=
tiplex (or multiplex). &nbsp;If you receive an offer for a bundle you don=
=92t know how to mux or de-mux, you MUST unbundle
 or reject m-lines so you know how to mux and demux the remaining bundle, o=
r reject the offer.</div>
<div><br>
</div>
<div>I=92m uncertain how explicitly this should define =93know how to=94, i=
.e. if the procedure has to be a normative spec. &nbsp;I could imagine a sc=
enario where there are multiple possibilities as to how to mix or de-mux tw=
o protocols (e.g., by restricting some field
 in one or the other protocol to a subset of its valid values, and there ar=
e multiple ways to pick the subsets), and if two endpoints have different a=
pproaches to muxing/de-muxing you would have interop failures.</div>
<br>
<blockquote type=3D"cite">
<div lang=3D"EN-GB" link=3D"#0563C1" vlink=3D"#954F72" style=3D"font-family=
: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; fon=
t-weight: normal; letter-spacing: normal; line-height: normal; orphans: aut=
o; text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">
<div class=3D"WordSection1" style=3D"page: WordSection1;">
<div style=3D"margin: 0cm 0cm 0.0001pt 36pt; font-size: 11pt; font-family: =
Calibri, sans-serif; text-indent: -18pt;">
<o:p></o:p></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif;">
<o:p>&nbsp;</o:p></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif;">
I think that DTLS/SRTP/STUN is going to be the main use-case (not only for =
WebRTC) in the near future, so I think it=92s a good approach.<o:p></o:p></=
div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif;">
<o:p>&nbsp;</o:p></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif;">
Regards,<o:p></o:p></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif;">
<o:p>&nbsp;</o:p></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif;">
Christer<o:p></o:p></div>
</div>
_______________________________________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" style=3D"color: rgb(149, 79, 114); text-=
decoration: underline;">mmusic@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" style=3D"color: rg=
b(149, 79, 114); text-decoration: underline;">https://www.ietf.org/mailman/=
listinfo/mmusic</a></div>
</blockquote>
</div>
<br>
</body>
</html>

--_000_822454EF2BBF4C9A8ADE734F3643120Bvidyocom_--


From nobody Sun Mar  2 15:00:46 2014
Return-Path: <Raju.Makaraju@alcatel-lucent.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 DDAE61A0A82 for <mmusic@ietfa.amsl.com>; Sun,  2 Mar 2014 15:00:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] autolearn=ham
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 9DslBXy0yUVc for <mmusic@ietfa.amsl.com>; Sun,  2 Mar 2014 15:00:43 -0800 (PST)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id EA7941A0A7C for <mmusic@ietf.org>; Sun,  2 Mar 2014 15:00:42 -0800 (PST)
Received: from us70tusmtp2.zam.alcatel-lucent.com (h135-5-2-64.lucent.com [135.5.2.64]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id s22N0Vb4016889 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sun, 2 Mar 2014 17:00:33 -0600 (CST)
Received: from US70TWXCHHUB04.zam.alcatel-lucent.com (us70twxchhub04.zam.alcatel-lucent.com [135.5.2.36]) by us70tusmtp2.zam.alcatel-lucent.com (GMO) with ESMTP id s22N0VxY002067 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 2 Mar 2014 18:00:31 -0500
Received: from US70UWXCHMBA02.zam.alcatel-lucent.com ([169.254.8.212]) by US70TWXCHHUB04.zam.alcatel-lucent.com ([135.5.2.36]) with mapi id 14.02.0247.003; Sun, 2 Mar 2014 18:00:31 -0500
From: "Makaraju, Maridi Raju (Raju)" <Raju.Makaraju@alcatel-lucent.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, Christer Holmberg <christer.holmberg@ericsson.com>, Mary Barnes <mary.ietf.barnes@gmail.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: IETF#89: First version of CLUE Data Channel slide set.
Thread-Index: AQHPNW3bGiqdS9LZRZu/XRhtec89PJrM/r0AgADHGRCAAHIogP//rM2AgABip4D//7uAwIAAmK0A///L61A=
Date: Sun, 2 Mar 2014 23:00:30 +0000
Message-ID: <E1FE4C082A89A246A11D7F32A95A17826E003DC8@US70UWXCHMBA02.zam.alcatel-lucent.com>
References: <7594FB04B1934943A5C02806D1A2204B1D1C0E03@ESESSMB209.ericsson.se> <CAHBDyN75R1Wr5BODSQ9RNmNP9G7QZdOjZ9Lw+Vz3DCEUUYh4-Q@mail.gmail.com> <CAHBDyN5aDiJHy0fZ3=A8bLyCGAEhSojxu0_kAdLvOTykykE36Q@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1D1C2DF7@ESESSMB209.ericsson.se> <E1FE4C082A89A246A11D7F32A95A17826E003463@US70UWXCHMBA02.zam.alcatel-lucent.com> <7594FB04B1934943A5C02806D1A2204B1D1C3A97@ESESSMB209.ericsson.se> <E1FE4C082A89A246A11D7F32A95A17826E003836@US70UWXCHMBA02.zam.alcatel-lucent.com> <7594FB04B1934943A5C02806D1A2204B1D1C4C1F@ESESSMB209.ericsson.se> <E1FE4C082A89A246A11D7F32A95A17826E003961@US70UWXCHMBA02.zam.alcatel-lucent.com> <53139A10.1040502@alum.mit.edu>
In-Reply-To: <53139A10.1040502@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.5.27.16]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/sMo9yO6SXFCXITK_8XXDhp1u3C4
Cc: "DRAGE, Keith \(Keith\)" <keith.drage@alcatel-lucent.com>
Subject: Re: [MMUSIC] IETF#89: First version of CLUE Data Channel slide set.
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: Sun, 02 Mar 2014 23:00:45 -0000

Comments inline.

> From: Paul Kyzivat [mailto:pkyzivat@alum.mit.edu]
> On 3/2/14 5:11 PM, Makaraju, Maridi Raju (Raju) wrote:
> > + mmusic to cover some of the discussions.
> >
> > Hi,
> >
> > Please see comments inline.
> >
> > Hi,
> >
> > For the gateway use-case, do we really need to indicate the SCTP stream
> > during Offer/Answer?
> >
> > Or, would it be enough if we indicate that the data channel is going to
> > be used for CLUE, and the gateway then figures out which stream is used
> > when it receives DCEP OPEN?
> >
> > */[Raju] This approach has 2 implications:/*
> >
> > */1./**//*The gateway needs to look at bearer packets and notify the
> > signaling layer about the streams. Though possible, this is
> > computationally intensive and new mechanism needed for such notificatio=
n
> > between bearer and signaling layers.
> >
> > Why does it need to inform the signalling layer about the streams? The
> > controller needs to tell the media gateway: "please let CLUE go through=
"
> >
> > */[Raju] "Please let CLUE through" is a simple scenario without much
> > interworking and other needs./*
> >
> > */I want to point out couple of other interworking scenarios:/*
> >
> > */1./*Lawful intercept (LI): A CLUE channel may have to be reported to
> > LI agents per regulatory requirements. For various reasons such
> > reporting may have to be interworked with non-data channel SCTP/dTLS
> > transport (e.g. TCP).
>=20
> By explicit policy we don't consider lawful intercept in IETF.
> The same issue exists for the RTP.

[Raju] I understand LI is a very sensitive subject and by no means I am mak=
ing any statements about it. My comment was providing one use case to which=
 a service provider may be legally obligated to oblige.

There are other cases that may require interworking at gateways.

>=20
> > */2./*For Non-LI reasons, a CLUE could be interworked to a TCP based
> > transport in an end-to-access-edge kind of approach.
>=20
> ??? CLUE protocol over TCP? Why? Who will specify that? The intent is to
> use DTLS/SCTP based data channel even when no webrtc in use.
>=20
> Or do you mean interworking with some non-clue TP protocol?
[Raju] I meant both. None of these are defined yet for CLUE. I am thinking =
of these future possibilities. If one approach allows these future possibil=
ties with little overhead, my vote is to go with such approach.
Also, as stated earlier such SDP framework makes it easy to negotiate subpr=
otocol attributes which comes naturally with SDP and fits well with SDP bas=
ed approach.

Thanks
Raju


From nobody Sun Mar  2 16:08:51 2014
Return-Path: <pkyzivat@alum.mit.edu>
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 91F9E1A0B38 for <mmusic@ietfa.amsl.com>; Sun,  2 Mar 2014 16:08:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] 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 AWdl2Vg_ir0v for <mmusic@ietfa.amsl.com>; Sun,  2 Mar 2014 16:08:46 -0800 (PST)
Received: from qmta02.westchester.pa.mail.comcast.net (qmta02.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:24]) by ietfa.amsl.com (Postfix) with ESMTP id C2FA01A0B37 for <mmusic@ietf.org>; Sun,  2 Mar 2014 16:08:45 -0800 (PST)
Received: from omta16.westchester.pa.mail.comcast.net ([76.96.62.88]) by qmta02.westchester.pa.mail.comcast.net with comcast id Yo511n0041uE5Es51o8jWQ; Mon, 03 Mar 2014 00:08:43 +0000
Received: from dhcp-hotel-wifi-157-6c.meeting.ietf.org ([130.129.157.108]) by omta16.westchester.pa.mail.comcast.net with comcast id Yo6G1n00J2LcPnE3co6JJ0; Mon, 03 Mar 2014 00:06:41 +0000
Message-ID: <5313C778.2040105@alum.mit.edu>
Date: Mon, 03 Mar 2014 00:06:16 +0000
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: "Makaraju, Maridi Raju (Raju)" <Raju.Makaraju@alcatel-lucent.com>,  Christer Holmberg <christer.holmberg@ericsson.com>, Mary Barnes <mary.ietf.barnes@gmail.com>,  "mmusic@ietf.org" <mmusic@ietf.org>
References: <7594FB04B1934943A5C02806D1A2204B1D1C0E03@ESESSMB209.ericsson.se>	<CAHBDyN75R1Wr5BODSQ9RNmNP9G7QZdOjZ9Lw+Vz3DCEUUYh4-Q@mail.gmail.com> <CAHBDyN5aDiJHy0fZ3=A8bLyCGAEhSojxu0_kAdLvOTykykE36Q@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1D1C2DF7@ESESSMB209.ericsson.se> <E1FE4C082A89A246A11D7F32A95A17826E003463@US70UWXCHMBA02.zam.alcatel-lucent.com> <7594FB04B1934943A5C02806D1A2204B1D1C3A97@ESESSMB209.ericsson.se> <E1FE4C082A89A246A11D7F32A95A17826E003836@US70UWXCHMBA02.zam.alcatel-lucent.com> <7594FB04B1934943A5C02806D1A2204B1D1C4C1F@ESESSMB209.ericsson.se> <E1FE4C082A89A246A11D7F32A95A17826E003961@US70UWXCHMBA02.zam.alcatel-lucent.com> <53139A10.1040502@alum.mit.edu> <E1FE4C082A89A246A11D7F32A95A17826E003DC8@US70UWXCHMBA02.zam.alcatel-lucent.com>
In-Reply-To: <E1FE4C082A89A246A11D7F32A95A17826E003DC8@US70UWXCHMBA02.zam.alcatel-lucent.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1393805323; bh=9NcHnpqCbISjx2H2ShUY576TxEaauwXYfsro9UNUhVY=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=nA1LzrlO1KH9TIDKx7d8ZI4p0SMA7pkxxg+6+9XlRyGaInJqlr5wr2/4WOhL5Qdjr 2UXff8jQwOeSIxeRfc38T7BHz0dutmxc+xCgQ2rrNtpA0Jcxz5WrFuygYZietMloRf HmOSmdc/mHIv6cCoZPO/IZffHtSP0aROKNvrWi4Z/KL9qyVpIevPwjvx4jlNGKf5uw l9r7N6+fpvNN0DPetVlC6Q9d2EzE1jwfGir+mZ3Dhuyq5L8uWNEPY3VsCnIAO1gA6H SwUcSQqwk7u16PiDS7g0qhtJZyWM1lurn4CrqjRiWNb/EXK/+HsDtXkIuZr58Oswhl 1TAgTfmGH5www==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/getwsfBdRgRQ47O0r9V2VBUgFbk
Cc: "DRAGE, Keith \(Keith\)" <keith.drage@alcatel-lucent.com>
Subject: Re: [MMUSIC] IETF#89: First version of CLUE Data Channel slide set.
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 00:08:47 -0000

I started out preferring an SDP approach (such as Richard's draft) for 
negotiating the clue channel. But IMO *the* reason we are using SCTP is 
to get interop with CLUE. (Otherwise we could just use TLS.)

And at the moment going with DCEP appears to be the low risk approach 
for us. With it we have fewer dependencies, and the ones we have are on 
paths that will be well exercised in the short run. There is less total 
stuff to implement, and it is sufficient for our needs. And it will be 
the path of least resistance for getting an webrtc clue client working.

(I'm fairly confident that Simon will have one going sooner rather than 
later. They already have prototypes of pieces, and we don't have the 
specs done yet.)

	Thanks,
	Paul

On 3/2/14 11:00 PM, Makaraju, Maridi Raju (Raju) wrote:
> Comments inline.
>
>> From: Paul Kyzivat [mailto:pkyzivat@alum.mit.edu]
>> On 3/2/14 5:11 PM, Makaraju, Maridi Raju (Raju) wrote:
>>> + mmusic to cover some of the discussions.
>>>
>>> Hi,
>>>
>>> Please see comments inline.
>>>
>>> Hi,
>>>
>>> For the gateway use-case, do we really need to indicate the SCTP stream
>>> during Offer/Answer?
>>>
>>> Or, would it be enough if we indicate that the data channel is going to
>>> be used for CLUE, and the gateway then figures out which stream is used
>>> when it receives DCEP OPEN?
>>>
>>> */[Raju] This approach has 2 implications:/*
>>>
>>> */1./**//*The gateway needs to look at bearer packets and notify the
>>> signaling layer about the streams. Though possible, this is
>>> computationally intensive and new mechanism needed for such notification
>>> between bearer and signaling layers.
>>>
>>> Why does it need to inform the signalling layer about the streams? The
>>> controller needs to tell the media gateway: "please let CLUE go through"
>>>
>>> */[Raju] "Please let CLUE through" is a simple scenario without much
>>> interworking and other needs./*
>>>
>>> */I want to point out couple of other interworking scenarios:/*
>>>
>>> */1./*Lawful intercept (LI): A CLUE channel may have to be reported to
>>> LI agents per regulatory requirements. For various reasons such
>>> reporting may have to be interworked with non-data channel SCTP/dTLS
>>> transport (e.g. TCP).
>>
>> By explicit policy we don't consider lawful intercept in IETF.
>> The same issue exists for the RTP.
>
> [Raju] I understand LI is a very sensitive subject and by no means I am making any statements about it. My comment was providing one use case to which a service provider may be legally obligated to oblige.
>
> There are other cases that may require interworking at gateways.
>
>>
>>> */2./*For Non-LI reasons, a CLUE could be interworked to a TCP based
>>> transport in an end-to-access-edge kind of approach.
>>
>> ??? CLUE protocol over TCP? Why? Who will specify that? The intent is to
>> use DTLS/SCTP based data channel even when no webrtc in use.
>>
>> Or do you mean interworking with some non-clue TP protocol?
> [Raju] I meant both. None of these are defined yet for CLUE. I am thinking of these future possibilities. If one approach allows these future possibilties with little overhead, my vote is to go with such approach.
> Also, as stated earlier such SDP framework makes it easy to negotiate subprotocol attributes which comes naturally with SDP and fits well with SDP based approach.
>
> Thanks
> Raju
>
>


From nobody Sun Mar  2 16:29:40 2014
Return-Path: <pkyzivat@alum.mit.edu>
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 7DC7C1A0B3B for <mmusic@ietfa.amsl.com>; Sun,  2 Mar 2014 16:29:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.035
X-Spam-Level: 
X-Spam-Status: No, score=-0.035 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, J_CHICKENPOX_15=0.6, J_CHICKENPOX_16=0.6, SPF_SOFTFAIL=0.665] 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 lS_aTWOsT9Uf for <mmusic@ietfa.amsl.com>; Sun,  2 Mar 2014 16:29:37 -0800 (PST)
Received: from qmta13.westchester.pa.mail.comcast.net (qmta13.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:243]) by ietfa.amsl.com (Postfix) with ESMTP id 0EBEE1A09C2 for <mmusic@ietf.org>; Sun,  2 Mar 2014 16:29:36 -0800 (PST)
Received: from omta23.westchester.pa.mail.comcast.net ([76.96.62.74]) by qmta13.westchester.pa.mail.comcast.net with comcast id YoMU1n0051c6gX85DoVa5z; Mon, 03 Mar 2014 00:29:34 +0000
Received: from dhcp-hotel-wifi-157-6c.meeting.ietf.org ([130.129.157.108]) by omta23.westchester.pa.mail.comcast.net with comcast id YoTR1n00U2LcPnE3joTUy9; Mon, 03 Mar 2014 00:27:32 +0000
Message-ID: <5313CC6D.4060809@alum.mit.edu>
Date: Mon, 03 Mar 2014 00:27:25 +0000
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: mmusic@ietf.org
References: <7594FB04B1934943A5C02806D1A2204B1D1C4C88@ESESSMB209.ericsson.se> <822454EF-2BBF-4C9A-8ADE-734F3643120B@vidyo.com>
In-Reply-To: <822454EF-2BBF-4C9A-8ADE-734F3643120B@vidyo.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1393806574; bh=wIkIj9G1oTY/P79slvsKNNrjGkCNpeDDQwLC6gRG7Ic=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=LaqAtJFx+bk2wl+sGU6DTDJRwYiPnh6vbII2Kbnsm2e5MdUOuHzNP9zHqP1ggUSD0 cQL32jyifh9eYt8Nlqv0L0SZnkmP6eTfjYLT5zmOZ+ZSWH6bQYEjP4FowX6sE9Fbt4 kJF07YDYQmI9tFeVpQWw0eY1J0Buc1IDCkp+ZziJ5L94uM9bZiFvIuXHWjXZaQuCTf fTyHe3oXpEFXUldIg/2weOc4/wiatrn3m9U5eG0X8M9whqyU1Flw1J0S3XSDcUAwf+ Vjv0sHAFzj0ifq8cXIgcMMfjE+xLuIXsZ+VniyirPIR85qmEKFGlF3QNpLmhEHpaft p77PMeU5C2OuQ==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/9WkZebPT55PZSjmBjnGRMe68_xs
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 00:29:38 -0000

On 3/2/14 10:46 PM, Jonathan Lennox wrote:
>
>
> On Mar 2, 2014, at 4:03 PM, Christer Holmberg
> <christer.holmberg@ericsson.com <mailto:christer.holmberg@ericsson.com>>
> wrote:
>
>> Hi,
>> One of the open issues is what we, in the BUNDLE spec, are going to
>> say about de-multiplexing about different media types, and for which
>> (if any) media types we are going to specify how the de-multiplexing
>> is done.
>> We have previously agreed that we are NOT going to describe all
>> different possibilities in BUNDLE, and that separate specifications
>> how to perform (and, indicate support of) de-multiplexing will have to
>> be written. However, we haven’t really agreed on the details.
>> I intend to suggest the following in London.
>> In the BUNDLE spec we:
>> 1)Reference to RFC 5764 for how to de-multiplex DTLS/SRTP/STUN; and
>> 2)Separate specifications are required to describe how to de-mulitplex
>> other media types, and any type of information that needs to be
>> exchanged between peers in order to perform the de-multiplexing.
>
> In addition to this, I think BUNDLE should say explicitly that: You MUST
> NOT send an offer or answer with a bundle you don’t know how to
> de-multiplex (or multiplex).  If you receive an offer for a bundle you
> don’t know how to mux or de-mux, you MUST unbundle or reject m-lines so
> you know how to mux and demux the remaining bundle, or reject the offer.
>
> I’m uncertain how explicitly this should define “know how to”, i.e. if
> the procedure has to be a normative spec.  I could imagine a scenario
> where there are multiple possibilities as to how to mix or de-mux two
> protocols (e.g., by restricting some field in one or the other protocol
> to a subset of its valid values, and there are multiple ways to pick the
> subsets), and if two endpoints have different approaches to
> muxing/de-muxing you would have interop failures.

This is my concern too.

For things to work, I must mux things consistently with the way you 
demux them, and visa versa.

For instance, suppose the individual m-lines had attributes declaring 
both SSRCs and AppIDs. (This sounds like a bad idea, but unless somebody 
writes a spec that says to not do this it is possible.) As sender I 
might intend that each m-line correspond to an AppID, but you decide to 
demux them based on SSRC. Makes a mess.

OTOH, if somebody wrote a spec that said rtp m-lines may be 
distinguished by unique a=AppIds, or, if lacking that, then unique 
a=SSRCs, then everyone could agree to that.

	Thanks,
	Paul


From nobody Sun Mar  2 21:48:36 2014
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 657291A0BA2 for <mmusic@ietfa.amsl.com>; Sun,  2 Mar 2014 21:48:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 3r2WOFG0dsC3 for <mmusic@ietfa.amsl.com>; Sun,  2 Mar 2014 21:48:31 -0800 (PST)
Received: from sesbmg20.ericsson.net (sesbmg20.ericsson.net [193.180.251.56]) by ietfa.amsl.com (Postfix) with ESMTP id 106AE1A0D12 for <mmusic@ietf.org>; Sun,  2 Mar 2014 21:48:30 -0800 (PST)
X-AuditID: c1b4fb38-b7f418e000001099-23-531417aad71a
Received: from ESESSHC023.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg20.ericsson.net (Symantec Mail Security) with SMTP id F9.DA.04249.AA714135; Mon,  3 Mar 2014 06:48:27 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.216]) by ESESSHC023.ericsson.se ([153.88.183.87]) with mapi id 14.02.0387.000; Mon, 3 Mar 2014 06:48:26 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Jonathan Lennox <jonathan@vidyo.com>
Thread-Topic: [MMUSIC] IETF#89: BUNDLE: Q12: Scope of non-RTP media de-mux procedures in BUNDLE?
Thread-Index: Ac82MKMUCOeiYc5PSXK9YNe83HDvFwAavSeAAAIL69A=
Date: Mon, 3 Mar 2014 05:48:26 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D1C5507@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D1C4C88@ESESSMB209.ericsson.se> <822454EF-2BBF-4C9A-8ADE-734F3643120B@vidyo.com>
In-Reply-To: <822454EF-2BBF-4C9A-8ADE-734F3643120B@vidyo.com>
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: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1D1C5507ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrCLMWRmVeSWpSXmKPExsUyM+Jvje5qcZFggzN/eSz2Lz7PbDF1+WMW ByaPJUt+Mnm0PbvDHsAUxWWTkpqTWZZapG+XwJVxf8MuxoJJwRX3bvawNjD+8ehi5OSQEDCR uNSymQnCFpO4cG89WxcjF4eQwBFGiRezj7BAOIsZJW7cWMzcxcjBwSZgIdH9TxukQURAQ+Li sw9sIDazgIzEjLONYIOEBRIlnsw/xQ5RkyTR8ucbE0iriICVRNMKPhCTRUBF4tA1GZAKXgFf iWVHXkJtamCUWH7iHjNIglPAVqLl5SFGEJsR6Lbvp9YwQawSl7j1ZD7UzQISS/acZ4awRSVe Pv7HCmErSazYfokRoj5f4u2d68wQywQlTs58wjKBUXQWklGzkJTNQlIGEdeRWLD7ExuErS2x bOFrZhj7zIHHTMjiCxjZVzFyFKcWJ+WmGxlsYgTG1MEtvy12MF7+a3OIUZqDRUmc9+Nb5yAh gfTEktTs1NSC1KL4otKc1OJDjEwcnFINjOL8cdEv3mco+91rPCHQan6yTszVTGHXwqv5B5P3 TUw8NLXp8lXPaxdCbn9+Xmpx87Z/fVH31nVxzxas2VRjlc9RfD9P4FSFrFnv/BXRc99IaAsf tRTivycrd184o3CO2Ja0pQ0CyZmebbyHCnce+jWV8/Gx+8mStRkRrh6t4cbnLkz95XCYRYml OCPRUIu5qDgRABFErFV3AgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/kUvJALlh7YR30CH7tUQWYts4_X8
Cc: mmusic <mmusic@ietf.org>
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:48:35 -0000

--_000_7594FB04B1934943A5C02806D1A2204B1D1C5507ESESSMB209erics_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

One of the open issues is what we, in the BUNDLE spec, are going to say abo=
ut de-multiplexing about different media types, and for which (if any) medi=
a types we are going to specify how the de-multiplexing is done.

We have previously agreed that we are NOT going to describe all different p=
ossibilities in BUNDLE, and that separate specifications how to perform (an=
d, indicate support of) de-multiplexing will have to be written. However, w=
e haven't really agreed on the details.

I intend to suggest the following in London.

In the BUNDLE spec we:

1)      Reference to RFC 5764 for how to de-multiplex DTLS/SRTP/STUN; and
2)      Separate specifications are required to describe how to de-mulitple=
x other media types, and any type of information that needs to be exchanged=
 between peers in order to perform the de-multiplexing.

In addition to this, I think BUNDLE should say explicitly that: You MUST NO=
T send an offer or answer with a bundle you don't know how to de-multiplex =
(or multiplex).  If you receive an offer for a bundle you don't know how to=
 mux or de-mux, you MUST unbundle or reject m-lines so you know how to mux =
and demux the remaining bundle, or reject the offer.

Sure, there would be text describing that.

I'm uncertain how explicitly this should define "know how to", i.e. if the =
procedure has to be a normative spec.  I could imagine a scenario where the=
re are multiple possibilities as to how to mix or de-mux two protocols (e.g=
., by restricting some field in one or the other protocol to a subset of it=
s valid values, and there are multiple ways to pick the subsets), and if tw=
o endpoints have different approaches to muxing/de-muxing you would have in=
terop failures.

If e.g. some information needs to be exchanged between the endpoints, or if=
 there are some media plane level parameter values that need to be set in c=
ertain way, the spec would have to describe that.

We do need to work out good text describing that.

Regards,

Christer


--_000_7594FB04B1934943A5C02806D1A2204B1D1C5507ESESSMB209erics_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.apple-converted-space
	{mso-style-name:apple-converted-space;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:red;mso-fareast-language:EN-US">Hi=
,<o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">One of the open issues is what we, in t=
he BUNDLE spec, are going to say about de-multiplexing about different medi=
a types, and for which (if any) media types we are going
 to specify how the de-multiplexing is done.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">We have previously agreed that we are N=
OT going to describe all different possibilities in BUNDLE, and that separa=
te specifications how to perform (and, indicate support
 of) de-multiplexing will have to be written. However, we haven&#8217;t rea=
lly agreed on the details.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">I intend to suggest the following in Lo=
ndon.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">In the BUNDLE spec we:<o:p></o:p></span=
></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">&nbsp;<o:p></o:p></span></p>
</div>
<div style=3D"margin-left:36.0pt">
<p class=3D"MsoNormal" style=3D"text-indent:-18.0pt"><span style=3D"font-si=
ze:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">1)</span>=
<span style=3D"font-size:7.0pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<span class=
=3D"apple-converted-space">&nbsp;</span></span><span style=3D"font-size:11.=
0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Reference
 to RFC 5764 for how to de-multiplex DTLS/SRTP/STUN; and<o:p></o:p></span><=
/p>
</div>
<div style=3D"margin-left:36.0pt">
<p class=3D"MsoNormal" style=3D"text-indent:-18.0pt"><span style=3D"font-si=
ze:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">2)</span>=
<span style=3D"font-size:7.0pt">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<span class=
=3D"apple-converted-space">&nbsp;</span></span><span style=3D"font-size:11.=
0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;">Separate
 specifications are required to describe how to de-mulitplex other media ty=
pes, and any type of information that needs to be exchanged between peers i=
n order to perform the de-multiplexing.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">In addition to this, I think BUNDLE should say expli=
citly that: You MUST NOT send an offer or answer with a bundle you don&#821=
7;t know how to de-multiplex (or multiplex). &nbsp;If you receive an offer =
for a bundle you don&#8217;t know how to mux or de-mux,
 you MUST unbundle or reject m-lines so you know how to mux and demux the r=
emaining bundle, or reject the offer.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:red">Sure, there would be text des=
cribing that.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
</div>
<div>
<p class=3D"MsoNormal">I&#8217;m uncertain how explicitly this should defin=
e &#8220;know how to&#8221;, i.e. if the procedure has to be a normative sp=
ec. &nbsp;I could imagine a scenario where there are multiple possibilities=
 as to how to mix or de-mux two protocols (e.g., by restricting
 some field in one or the other protocol to a subset of its valid values, a=
nd there are multiple ways to pick the subsets), and if two endpoints have =
different approaches to muxing/de-muxing you would have interop failures.<o=
:p></o:p></p>
</div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:red">If e.g. some information need=
s to be exchanged between the endpoints, or if there are some media plane l=
evel parameter values that need to be set in certain way,
 the spec would have to describe that.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:red"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:red">We do need to work out good t=
ext describing that.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:red"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:red">Regards,<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:red"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:red">Christer<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:red"><o:p>&nbsp;</o:p></span></p>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B1D1C5507ESESSMB209erics_--


From nobody Sun Mar  2 21:50:50 2014
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, 3 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 o=
r implementers note=20
> explaining the issues involved in this.

Yes.

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

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

Regards,

Christer


From nobody Sun Mar  2 21:57:40 2014
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 346891A0CF6 for <mmusic@ietfa.amsl.com>; Sun,  2 Mar 2014 21:57:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.651
X-Spam-Level: 
X-Spam-Status: No, score=-2.651 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, J_CHICKENPOX_15=0.6, J_CHICKENPOX_16=0.6, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 6vHbUcrD1jTt for <mmusic@ietfa.amsl.com>; Sun,  2 Mar 2014 21:57:37 -0800 (PST)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id 3F4591A0B9B for <mmusic@ietf.org>; Sun,  2 Mar 2014 21:57:37 -0800 (PST)
X-AuditID: c1b4fb25-b7f038e000005d01-0a-531419cd343d
Received: from ESESSHC003.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 51.7B.23809.DC914135; Mon,  3 Mar 2014 06:57:33 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.216]) by ESESSHC003.ericsson.se ([153.88.183.27]) with mapi id 14.02.0387.000; Mon, 3 Mar 2014 06:57:03 +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: Ac82MKMUCOeiYc5PSXK9YNe83HDvFwAavSeA//+mwID//5RwwA==
Date: Mon, 3 Mar 2014 05:57:03 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D1C5536@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D1C4C88@ESESSMB209.ericsson.se> <822454EF-2BBF-4C9A-8ADE-734F3643120B@vidyo.com> <5313CC6D.4060809@alum.mit.edu>
In-Reply-To: <5313CC6D.4060809@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+NgFtrPLMWRmVeSWpSXmKPExsUyM+Jvje5ZSZFgg+8tlhZTlz9msVix4QCr A5PH3/cfmDyWLPnJFMAUxWWTkpqTWZZapG+XwJWx9E8PU0G7eEXPNIUGxj1CXYycHBICJhJb tnQxQdhiEhfurWfrYuTiEBI4xCixY/piJghnMZDz4jFQhoODTcBCovufNkiDiICvxLPHt9lA bGGBRIkn80+xQ8STJFr+fGOCsJ0kTn49wwhiswioSPR17WQCGcML1Nu3Mhxi/CJGiXvfJoPV cAroSGw8sIwFxGYEOuj7qTVgc5gFxCVuPZkPdaiAxJI955khbFGJl4//sULYShIrtl9ihKjX kViw+xMbhK0tsWzha7B6XgFBiZMzn7BMYBSdhWTsLCQts5C0zELSsoCRZRUje25iZk56udEm RmAkHNzyW3UH451zIocYpTlYlMR5P7x1DhISSE8sSc1OTS1ILYovKs1JLT7EyMTBKdXAqBDH 9/irSsqU2oNRmgskrGw2hFftPP5I1H7L5x3drvnFmVP3CbziXs4jNv9baDVL+YojhovTN/5i Unx7JKlpK6Pvn3K1+V/4jDcsmXsn2s3ESJK9zn/NrqDC3a5OdXxe3j7Jfv+cSzreFZ171Mt5 ardHZMYJ2947ZdyrWtaf3Oknv2+Wt+0pJZbijERDLeai4kQACreSKlICAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/bo0gEB34mePpaz_k4Ta2o47eQDw
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:57:39 -0000

Hi,

>>> One of the open issues is what we, in the BUNDLE spec, are going to=20
>>> say about de-multiplexing about different media types, and for which=20
>>> (if any) media types we are going to specify how the de-multiplexing=20
>>> is done.
>>> We have previously agreed that we are NOT going to describe all=20
>>> different possibilities in BUNDLE, and that separate specifications=20
>>> how to perform (and, indicate support of) de-multiplexing will have=20
>>> to be written. However, we haven't really agreed on the details.
>>> I intend to suggest the following in London.
>>> In the BUNDLE spec we:
>>> 1)Reference to RFC 5764 for how to de-multiplex DTLS/SRTP/STUN; and=20
>>> 2)Separate specifications are required to describe how to=20
>>> de-mulitplex other media types, and any type of information that=20
>>> needs to be exchanged between peers in order to perform the de-multiple=
xing.
>>
>> In addition to this, I think BUNDLE should say explicitly that: You=20
>> MUST NOT send an offer or answer with a bundle you don't know how to=20
>> de-multiplex (or multiplex).  If you receive an offer for a bundle you=20
>> don't know how to mux or de-mux, you MUST unbundle or reject m-lines=20
>> so you know how to mux and demux the remaining bundle, or reject the off=
er.
>>
>> I'm uncertain how explicitly this should define "know how to", i.e. if=20
>> the procedure has to be a normative spec.  I could imagine a scenario=20
>> where there are multiple possibilities as to how to mix or de-mux two=20
>> protocols (e.g., by restricting some field in one or the other=20
>> protocol to a subset of its valid values, and there are multiple ways=20
>> to pick the subsets), and if two endpoints have different approaches=20
>> to muxing/de-muxing you would have interop failures.
>
> This is my concern too.
>
> For things to work, I must mux things consistently with the way you demux=
 them, and visa versa.
>
> For instance, suppose the individual m-lines had attributes declaring bot=
h SSRCs and AppIDs. (This > sounds like a bad idea, but unless somebody wri=
tes a spec that says to not do this it is possible.) As > sender I might in=
tend that each m-line correspond to an AppID, but you decide to demux them=
=20
> based on SSRC. Makes a mess.
>
> OTOH, if somebody wrote a spec that said rtp m-lines may be distinguished=
 by unique a=3DAppIds,
> or, if lacking that, then unique a=3DSSRCs, then everyone could agree to =
that.

If there are different ways things could be done, the peers need to agree (=
using whatever attributes, option-tags, etc) on which one to use, and the s=
pec will have to describe that. I think that is all we can say in BUNDLE. O=
r, do you have another suggestion?

We are obviously not going to cover all multiplexing variants in BUNDLE, an=
d I don't think we want to FORBID other variants in BUNDLE either.

Regards,

Christer


From nobody Sun Mar  2 23:03:48 2014
Return-Path: <Christian.Groves@nteczone.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 A43B91A0D48 for <mmusic@ietfa.amsl.com>; Sun,  2 Mar 2014 23:03:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 eoJxIAH_1XuU for <mmusic@ietfa.amsl.com>; Sun,  2 Mar 2014 23:03:44 -0800 (PST)
Received: from cserver5.myshophosting.com (cserver5.myshophosting.com [175.107.161.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E1A31A0D4D for <mmusic@ietf.org>; Sun,  2 Mar 2014 23:03:37 -0800 (PST)
Received: from [130.129.152.129] (port=52072 helo=[127.0.0.1]) by cserver5.myshophosting.com with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from <Christian.Groves@nteczone.com>) id 1WKMop-00061O-Am; Mon, 03 Mar 2014 17:57:44 +1100
Message-ID: <5314293E.7090409@nteczone.com>
Date: Mon, 03 Mar 2014 18:03:26 +1100
From: Christian Groves <Christian.Groves@nteczone.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@alum.mit.edu>,  "Makaraju, Maridi Raju (Raju)" <Raju.Makaraju@alcatel-lucent.com>, Christer Holmberg <christer.holmberg@ericsson.com>,  Mary Barnes <mary.ietf.barnes@gmail.com>, "mmusic@ietf.org" <mmusic@ietf.org>
References: <7594FB04B1934943A5C02806D1A2204B1D1C0E03@ESESSMB209.ericsson.se>	<CAHBDyN75R1Wr5BODSQ9RNmNP9G7QZdOjZ9Lw+Vz3DCEUUYh4-Q@mail.gmail.com> <CAHBDyN5aDiJHy0fZ3=A8bLyCGAEhSojxu0_kAdLvOTykykE36Q@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1D1C2DF7@ESESSMB209.ericsson.se> <E1FE4C082A89A246A11D7F32A95A17826E003463@US70UWXCHMBA02.zam.alcatel-lucent.com> <7594FB04B1934943A5C02806D1A2204B1D1C3A97@ESESSMB209.ericsson.se> <E1FE4C082A89A246A11D7F32A95A17826E003836@US70UWXCHMBA02.zam.alcatel-lucent.com> <7594FB04B1934943A5C02806D1A2204B1D1C4C1F@ESESSMB209.ericsson.se> <E1FE4C082A89A246A11D7F32A95A17826E003961@US70UWXCHMBA02.zam.alcatel-lucent.com> <53139A10.1040502@alum.mit.edu> <E1FE4C082A89A246A11D7F32A95A17826E003DC8@US70UWXCHMBA02.zam.alcatel-lucent.com> <5313C778.2040105@alum.mit.edu>
In-Reply-To: <5313C778.2040105@alum.mit.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - cserver5.myshophosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - nteczone.com
X-Get-Message-Sender-Via: cserver5.myshophosting.com: authenticated_id: christian.groves@nteczone.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/Wp3iD2cb-rRf8FrE1jVSb3dDCmU
Cc: "DRAGE, Keith \(Keith\)" <keith.drage@alcatel-lucent.com>
Subject: Re: [MMUSIC] IETF#89: First version of CLUE Data Channel slide set.
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 07:03:46 -0000

I support Raju's comments. By not having an SDP approach to negotiate 
what protocol/s are being used  the SCTP association are going to 
complicate things for gateways that have to provide some interworking 
between endpoints.
DCEP is useful for opening the SCTP streams but I don't see where the 
negotiation of what will go over the streams will take place in 
non-rtcweb systems?

Regards, Christian

On 3/03/2014 11:06 AM, Paul Kyzivat wrote:
> I started out preferring an SDP approach (such as Richard's draft) for 
> negotiating the clue channel. But IMO *the* reason we are using SCTP 
> is to get interop with CLUE. (Otherwise we could just use TLS.)
>
> And at the moment going with DCEP appears to be the low risk approach 
> for us. With it we have fewer dependencies, and the ones we have are 
> on paths that will be well exercised in the short run. There is less 
> total stuff to implement, and it is sufficient for our needs. And it 
> will be the path of least resistance for getting an webrtc clue client 
> working.
>
> (I'm fairly confident that Simon will have one going sooner rather 
> than later. They already have prototypes of pieces, and we don't have 
> the specs done yet.)
>
>     Thanks,
>     Paul
>
> On 3/2/14 11:00 PM, Makaraju, Maridi Raju (Raju) wrote:
>> Comments inline.
>>
>>> From: Paul Kyzivat [mailto:pkyzivat@alum.mit.edu]
>>> On 3/2/14 5:11 PM, Makaraju, Maridi Raju (Raju) wrote:
>>>> + mmusic to cover some of the discussions.
>>>>
>>>> Hi,
>>>>
>>>> Please see comments inline.
>>>>
>>>> Hi,
>>>>
>>>> For the gateway use-case, do we really need to indicate the SCTP 
>>>> stream
>>>> during Offer/Answer?
>>>>
>>>> Or, would it be enough if we indicate that the data channel is 
>>>> going to
>>>> be used for CLUE, and the gateway then figures out which stream is 
>>>> used
>>>> when it receives DCEP OPEN?
>>>>
>>>> */[Raju] This approach has 2 implications:/*
>>>>
>>>> */1./**//*The gateway needs to look at bearer packets and notify the
>>>> signaling layer about the streams. Though possible, this is
>>>> computationally intensive and new mechanism needed for such 
>>>> notification
>>>> between bearer and signaling layers.
>>>>
>>>> Why does it need to inform the signalling layer about the streams? The
>>>> controller needs to tell the media gateway: "please let CLUE go 
>>>> through"
>>>>
>>>> */[Raju] "Please let CLUE through" is a simple scenario without much
>>>> interworking and other needs./*
[CNG] It's not about simply letting "CLUE go through." CLUE will need to 
be interworked/encodings updated etc depending on the gateway 
policy/capabilities.
>>>>
>>>> */I want to point out couple of other interworking scenarios:/*
>>>>
>>>> */1./*Lawful intercept (LI): A CLUE channel may have to be reported to
>>>> LI agents per regulatory requirements. For various reasons such
>>>> reporting may have to be interworked with non-data channel SCTP/dTLS
>>>> transport (e.g. TCP).
>>>
>>> By explicit policy we don't consider lawful intercept in IETF.
>>> The same issue exists for the RTP.
>>
>> [Raju] I understand LI is a very sensitive subject and by no means I 
>> am making any statements about it. My comment was providing one use 
>> case to which a service provider may be legally obligated to oblige.
>>
>> There are other cases that may require interworking at gateways.
>>
>>>
>>>> */2./*For Non-LI reasons, a CLUE could be interworked to a TCP based
>>>> transport in an end-to-access-edge kind of approach.
>>>
>>> ??? CLUE protocol over TCP? Why? Who will specify that? The intent 
>>> is to
>>> use DTLS/SCTP based data channel even when no webrtc in use.
>>>
>>> Or do you mean interworking with some non-clue TP protocol?
>> [Raju] I meant both. None of these are defined yet for CLUE. I am 
>> thinking of these future possibilities. If one approach allows these 
>> future possibilties with little overhead, my vote is to go with such 
>> approach.
>> Also, as stated earlier such SDP framework makes it easy to negotiate 
>> subprotocol attributes which comes naturally with SDP and fits well 
>> with SDP based approach.
[CNG] I agree.
>>
>> Thanks
>> Raju
>>
>>
>
>


From nobody Mon Mar  3 00:42:06 2014
Return-Path: <harald@alvestrand.no>
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 798EE1A0AF2 for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 00:41:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.344
X-Spam-Level: 
X-Spam-Status: No, score=0.344 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, RDNS_NONE=0.793] 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 8Y0C2sAiXCoB for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 00:41:54 -0800 (PST)
Received: from mork.alvestrand.no (unknown [IPv6:2001:700:1:2::117]) by ietfa.amsl.com (Postfix) with ESMTP id E4D4A1A0958 for <mmusic@ietf.org>; Mon,  3 Mar 2014 00:41:53 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mork.alvestrand.no (Postfix) with ESMTP id BDD037C4F60 for <mmusic@ietf.org>; Mon,  3 Mar 2014 09:41:50 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at alvestrand.no
Received: from mork.alvestrand.no ([127.0.0.1]) by localhost (mork.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id msKXEAKuEqkR for <mmusic@ietf.org>; Mon,  3 Mar 2014 09:41:50 +0100 (CET)
Received: from [31.133.161.198] (dhcp-a1c6.meeting.ietf.org [31.133.161.198]) by mork.alvestrand.no (Postfix) with ESMTPSA id EB2B17C4F5F for <mmusic@ietf.org>; Mon,  3 Mar 2014 09:41:49 +0100 (CET)
Message-ID: <5314404D.5070500@alvestrand.no>
Date: Mon, 03 Mar 2014 09:41:49 +0100
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: mmusic@ietf.org
References: <7594FB04B1934943A5C02806D1A2204B1D1C0E03@ESESSMB209.ericsson.se> <CAHBDyN75R1Wr5BODSQ9RNmNP9G7QZdOjZ9Lw+Vz3DCEUUYh4-Q@mail.gmail.com> <CAHBDyN5aDiJHy0fZ3=A8bLyCGAEhSojxu0_kAdLvOTykykE36Q@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1D1C2DF7@ESESSMB209.ericsson.se> <E1FE4C082A89A246A11D7F32A95A17826E003463@US70UWXCHMBA02.zam.alcatel-lucent.com> <7594FB04B1934943A5C02806D1A2204B1D1C3A97@ESESSMB209.ericsson.se> <E1FE4C082A89A246A11D7F32A95A17826E003836@US70UWXCHMBA02.zam.alcatel-lucent.com> <7594FB04B1934943A5C02806D1A2204B1D1C4C1F@ESESSMB209.ericsson.se> <E1FE4C082A89A246A11D7F32A95A17826E003961@US70UWXCHMBA02.zam.alcatel-lucent.com> <53139A10.1040502@alum.mit.edu> <E1FE4C082A89A246A11D7F32A95A17826E003DC8@US70UWXCHMBA02.zam.alcatel-lucent.com>
In-Reply-To: <E1FE4C082A89A246A11D7F32A95A17826E003DC8@US70UWXCHMBA02.zam.alcatel-lucent.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/tQT6IthvX4_-CrO671hO5PiV2VY
Subject: [MMUSIC] Lawful intercept - don't (Re: IETF#89: First version of CLUE Data Channel slide set.)
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 08:41:57 -0000

On 03/03/2014 12:00 AM, Makaraju, Maridi Raju (Raju) wrote:
>>> > > */1./*Lawful intercept (LI): A CLUE channel may have to be reported to
>>> > > LI agents per regulatory requirements. For various reasons such
>>> > > reporting may have to be interworked with non-data channel SCTP/dTLS
>>> > > transport (e.g. TCP).
>> > 
>> > By explicit policy we don't consider lawful intercept in IETF.
>> > The same issue exists for the RTP.
> [Raju] I understand LI is a very sensitive subject and by no means I am making any statements about it. My comment was providing one use case to which a service provider may be legally obligated to oblige.
>
> There are other cases that may require interworking at gateways.
>

When stating the use case, just say that one of the participants in a
CLUE channel (including the gateway) may choose to share the content (or
the existence of the channel - I can't tell which you mean by "report"
here) with a third party.

There are lots of reasons why someone may choose to do that, including,
for instance, the requirement for recording financial advice given over
the phone in many countries, and calling out legal intercept is just
going to generate lots of heat but little light.

-- 
Surveillance is pervasive. Go Dark.


From nobody Mon Mar  3 01:33:44 2014
Return-Path: <csp@csperkins.org>
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 D26581A0D86 for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 01:33:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001] autolearn=ham
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 sD7VwHj3cNZy for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 01:33:40 -0800 (PST)
Received: from haggis.mythic-beasts.com (haggis.mythic-beasts.com [IPv6:2a00:1098:0:86:1000:0:2:1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D5801A0D76 for <mmusic@ietf.org>; Mon,  3 Mar 2014 01:33:40 -0800 (PST)
Received: from [31.133.156.67] (port=58666 helo=dhcp-9c43.meeting.ietf.org) by haggis.mythic-beasts.com with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from <csp@csperkins.org>) id 1WKPFf-0008GY-Qj; Mon, 03 Mar 2014 09:33:36 +0000
Content-Type: multipart/alternative; boundary="Apple-Mail=_93E9248B-9DFA-4512-B701-C9B0473B7493"
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D1C368D@ESESSMB209.ericsson.se>
Date: Mon, 3 Mar 2014 09:33:34 +0000
Message-Id: <7A9A37FB-196F-4F79-805B-95CE9B67C344@csperkins.org>
References: <7594FB04B1934943A5C02806D1A2204B1D1C368D@ESESSMB209.ericsson.se>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.1874)
X-BlackCat-Spam-Score: -28
X-Mythic-Debug: Threshold =  On = 
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/TitpzL5iWPLHJi_abQjuLhyjwZE
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for allowing usage of the same PT value within multiple m- lines?
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 09:33:43 -0000

--Apple-Mail=_93E9248B-9DFA-4512-B701-C9B0473B7493
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Christer,

The bundled m=3D lines form a single RTP session. That means that they =
share a single RTP payload number space. The rule therefore has to be =
that you can only reuse the payload type across bundled m=3D lines if it =
refers to the exact same configuration of the exact same codec in all =
cases, where =93exact same configuration=94 means that the a=3Dfmtp: =
line and all other SDP attributes that configure the codec and =
packetisation of the media are identical.

If that=92s not specific enough, then MUST NOT reuse payload types =
across m=3D lines in a bundled group is the safe choice. I believe your =
propose that it=92s okay if you can handle the media is too vague, and =
will cause us problems down the line.

Colin




On 2 Mar 2014, at 08:44, Christer Holmberg =
<christer.holmberg@ericsson.com> wrote:
> Hi,
> =20
> One of the open issues we have in BUNDLE, is when it is allowed to use =
the same PT value within multiple m- lines.
> =20
> We tried to come up with different criteria, including a =93codec =
configuration=94 concept, but we never managed to agree on something.
> =20
> So, in London, I intend to suggest that we simply say: if you offer =
the same PT value within multiple m- line, make sure you can handle the =
associated media when it arrives =96 period (keep in mind that you =
always indicate what you want to RECEIVE =96 the remote peer can still =
ask you to SEND using different PT values).
> =20
> If you don=92t like this, please provide an alternative solution, =
because I want to close this issue in London. There is no idea to keep =
=93taking the issue back to the list=94. We=92ve done that for a few =
meetings already.
> =20
> Regards,
> =20
> Christer
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic



--=20
Colin Perkins
http://csperkins.org/




--Apple-Mail=_93E9248B-9DFA-4512-B701-C9B0473B7493
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;">Christer,<div><br></div><div>The bundled m=3D lines =
form a single RTP session. That means that they share a single RTP =
payload number space. The rule therefore has to be that you can only =
reuse the payload type across bundled m=3D lines if it refers to the =
exact same configuration of the exact same codec in all cases, where =
=93exact same configuration=94 means that the a=3Dfmtp: line and all =
other SDP attributes that configure the codec and packetisation of the =
media are identical.</div><div><br></div><div>If that=92s not specific =
enough, then MUST NOT reuse payload types across m=3D lines in a bundled =
group is the safe choice. I believe your propose that it=92s okay if you =
can handle the media is too vague, and will cause us problems down the =
line.</div><div><br></div><div>Colin</div><div><br></div><div><br></div><d=
iv><br></div><div><br><div><div>On 2 Mar 2014, at 08:44, Christer =
Holmberg &lt;<a =
href=3D"mailto:christer.holmberg@ericsson.com">christer.holmberg@ericsson.=
com</a>&gt; wrote:</div><blockquote type=3D"cite">

<meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered =
medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->

<div lang=3D"EN-GB" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1"><p class=3D"MsoNormal">Hi,<o:p></o:p></p><p =
class=3D"MsoNormal"><o:p>&nbsp;</o:p></p><p class=3D"MsoNormal">One of =
the open issues we have in BUNDLE, is when it is allowed to use the same =
PT value within multiple m- lines.<o:p></o:p></p><p =
class=3D"MsoNormal"><o:p>&nbsp;</o:p></p><p class=3D"MsoNormal">We tried =
to come up with different criteria, including a =93codec configuration=94 =
concept, but we never managed to agree on something.<o:p></o:p></p><p =
class=3D"MsoNormal"><o:p>&nbsp;</o:p></p><p class=3D"MsoNormal">So, in =
London, I intend to suggest that we simply say: if you offer the same PT =
value within multiple m- line, make sure you can handle the associated =
media when it arrives =96 period (keep in mind that you always indicate =
what you want to
 RECEIVE =96 the remote peer can still ask you to SEND using different =
PT values).<o:p></o:p></p><p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p><p =
class=3D"MsoNormal">If you don=92t like this, please provide an =
alternative solution, because I want to close this issue in London. =
There is no idea to keep =93taking the issue back to the list=94. We=92ve =
done that for a few meetings already.<o:p></o:p></p><p =
class=3D"MsoNormal"><o:p>&nbsp;</o:p></p><p =
class=3D"MsoNormal">Regards,<o:p></o:p></p><p =
class=3D"MsoNormal"><o:p>&nbsp;</o:p></p><p =
class=3D"MsoNormal">Christer<o:p></o:p></p>
</div>
</div>

_______________________________________________<br>mmusic mailing =
list<br><a =
href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>https://www.ietf.or=
g/mailman/listinfo/mmusic<br></blockquote></div><br><div =
apple-content-edited=3D"true">
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
color: rgb(0, 0, 0); font-family: 'Lucida Sans Typewriter'; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-align: -webkit-auto; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px;  "><div><br =
class=3D"Apple-interchange-newline"><br =
class=3D"khtml-block-placeholder"></div><div>--&nbsp;</div><div></div><div=
>Colin Perkins</div><div><a =
href=3D"http://csperkins.org/">http://csperkins.org/</a></div><div><br></d=
iv></span><br class=3D"Apple-interchange-newline">

</div>
<br></div></body></html>=

--Apple-Mail=_93E9248B-9DFA-4512-B701-C9B0473B7493--


From nobody Mon Mar  3 02:08:31 2014
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 32DBD1A0E08 for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 02:08:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.85
X-Spam-Level: 
X-Spam-Status: No, score=-3.85 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 wFctUoTBtA1Y for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 02:08:24 -0800 (PST)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 6D4201A0DF9 for <mmusic@ietf.org>; Mon,  3 Mar 2014 02:08:23 -0800 (PST)
X-AuditID: c1b4fb2d-b7f5d8e000002a7b-c7-531454931496
Received: from ESESSHC013.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 00.09.10875.39454135; Mon,  3 Mar 2014 11:08:19 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.216]) by ESESSHC013.ericsson.se ([153.88.183.57]) with mapi id 14.02.0387.000; Mon, 3 Mar 2014 11:08:19 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Colin Perkins <csp@csperkins.org>
Thread-Topic: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for allowing usage of the same PT value within multiple m- lines?
Thread-Index: Ac818yLx23ucJzjaSbubJw5GhjG+ygAyCDEAAAM6QvA=
Date: Mon, 3 Mar 2014 10:08:19 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D1C5A25@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D1C368D@ESESSMB209.ericsson.se> <7A9A37FB-196F-4F79-805B-95CE9B67C344@csperkins.org>
In-Reply-To: <7A9A37FB-196F-4F79-805B-95CE9B67C344@csperkins.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.154]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1D1C5A25ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrKLMWRmVeSWpSXmKPExsUyM+Jvje7kEJFgg2v7zC2WvzzBaDF1+WMW ByaPaffvs3ksWfKTKYApissmJTUnsyy1SN8ugSvjylGRgv64iqkf3jI3MH4P7GLk5JAQMJE4 +WoiI4QtJnHh3nq2LkYuDiGBQ4wSd5q/MEM4ixkl9q38xNTFyMHBJmAh0f1PG6RBREBVYsfx f4wgYWYBdYmri4NAyoUFWhglWs8cYAdxRARaGSWm9B9hgmiwknj8ag8biM0ioCJx6dsksDiv gK/EprNNjBDLgLobr31jBUlwCjhKNKy/B3YeI9B530+tAWtgFhCXuPVkPhPE2QISS/acZ4aw RSVePv7HCmErSSy6/RmqPl9i+6ZuqGWCEidnPmGZwCg6C8moWUjKZiEpg4jrSCzY/YkNwtaW WLbwNTOMfebAYyZk8QWM7KsY2XMTM3PSyw03MQKj6uCW37o7GE+dEznEKM3BoiTO++Gtc5CQ QHpiSWp2ampBalF8UWlOavEhRiYOTqkGxprDAa2BUxU3VWnsk7rTEH+KWzPQVHdK+GG/WTOM PD2/ep8X0jmlVXHleKxEXtIWeYs7s9wbX0h9nxPD5sPw/evbjRtyE9eaRr/hl1/Sa9/AILC6 86zL7/IHH5XuyXb3CIY2aT1tXHDhaIzx+757AvvFVbvVfNcq8Dpdqz7+7s/z1c8PJEm9VGIp zkg01GIuKk4EAOeNoth4AgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/bt9i6InKZVEiT57I8m8QSlRRt08
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for allowing usage of the same PT value within multiple m- lines?
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 10:08:28 -0000

--_000_7594FB04B1934943A5C02806D1A2204B1D1C5A25ESESSMB209erics_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Colin,

We tried to define "codec configuration", but we never got text that people=
 could agree to.

Personally I don't have any strong opinion which way we go (personally I am=
 also ok forbidding re-usage of the same PT value). I just want to close th=
e issue, and not once again "take it to the list".

Regards,

Christer

From: Colin Perkins [mailto:csp@csperkins.org]
Sent: 03 March 2014 11:34
To: Christer Holmberg
Cc: mmusic@ietf.org
Subject: Re: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for allowi=
ng usage of the same PT value within multiple m- lines?

Christer,

The bundled m=3D lines form a single RTP session. That means that they shar=
e a single RTP payload number space. The rule therefore has to be that you =
can only reuse the payload type across bundled m=3D lines if it refers to t=
he exact same configuration of the exact same codec in all cases, where "ex=
act same configuration" means that the a=3Dfmtp: line and all other SDP att=
ributes that configure the codec and packetisation of the media are identic=
al.

If that's not specific enough, then MUST NOT reuse payload types across m=
=3D lines in a bundled group is the safe choice. I believe your propose tha=
t it's okay if you can handle the media is too vague, and will cause us pro=
blems down the line.

Colin




On 2 Mar 2014, at 08:44, Christer Holmberg <christer.holmberg@ericsson.com<=
mailto:christer.holmberg@ericsson.com>> wrote:
Hi,

One of the open issues we have in BUNDLE, is when it is allowed to use the =
same PT value within multiple m- lines.

We tried to come up with different criteria, including a "codec configurati=
on" concept, but we never managed to agree on something.

So, in London, I intend to suggest that we simply say: if you offer the sam=
e PT value within multiple m- line, make sure you can handle the associated=
 media when it arrives - period (keep in mind that you always indicate what=
 you want to RECEIVE - the remote peer can still ask you to SEND using diff=
erent PT values).

If you don't like this, please provide an alternative solution, because I w=
ant to close this issue in London. There is no idea to keep "taking the iss=
ue back to the list". We've done that for a few meetings already.

Regards,

Christer
_______________________________________________
mmusic mailing list
mmusic@ietf.org<mailto:mmusic@ietf.org>
https://www.ietf.org/mailman/listinfo/mmusic


--
Colin Perkins
http://csperkins.org/




--_000_7594FB04B1934943A5C02806D1A2204B1D1C5A25ESESSMB209erics_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"Lucida Sans Typewriter";
	panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.apple-style-span
	{mso-style-name:apple-style-span;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-GB" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi Colin,<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">We tried to define &#8=
220;codec configuration&#8221;, but we never got text that people could agr=
ee to.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Personally I don&#8217=
;t have any strong opinion which way we go (personally I am also ok forbidd=
ing re-usage of the same PT value). I just want to close the issue, and not=
 once again &#8220;take it to the list&#8221;.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Regards,<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Christer<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><a name=3D"_MailEndCompose"><span style=3D"color:#1F=
497D"><o:p>&nbsp;</o:p></span></a></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"mso-fareast-languag=
e:EN-GB">From:</span></b><span lang=3D"EN-US" style=3D"mso-fareast-language=
:EN-GB"> Colin Perkins [mailto:csp@csperkins.org]
<br>
<b>Sent:</b> 03 March 2014 11:34<br>
<b>To:</b> Christer Holmberg<br>
<b>Cc:</b> mmusic@ietf.org<br>
<b>Subject:</b> Re: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for=
 allowing usage of the same PT value within multiple m- lines?<o:p></o:p></=
span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Christer,<span style=3D"font-size:12.0pt;mso-fareast=
-language:EN-GB"><o:p></o:p></span></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">The bundled m=3D lines form a single RTP session. Th=
at means that they share a single RTP payload number space. The rule theref=
ore has to be that you can only reuse the payload type across bundled m=3D =
lines if it refers to the exact same configuration
 of the exact same codec in all cases, where &#8220;exact same configuratio=
n&#8221; means that the a=3Dfmtp: line and all other SDP attributes that co=
nfigure the codec and packetisation of the media are identical.<o:p></o:p><=
/p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">If that&#8217;s not specific enough, then MUST NOT r=
euse payload types across m=3D lines in a bundled group is the safe choice.=
 I believe your propose that it&#8217;s okay if you can handle the media is=
 too vague, and will cause us problems down the
 line.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Colin<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<p class=3D"MsoNormal">On 2 Mar 2014, at 08:44, Christer Holmberg &lt;<a hr=
ef=3D"mailto:christer.holmberg@ericsson.com">christer.holmberg@ericsson.com=
</a>&gt; wrote:<o:p></o:p></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal">Hi,<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal">One of the open issues we have in BUNDLE, is when it=
 is allowed to use the same PT value within multiple m- lines.<o:p></o:p></=
p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal">We tried to come up with different criteria, includi=
ng a &#8220;codec configuration&#8221; concept, but we never managed to agr=
ee on something.<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal">So, in London, I intend to suggest that we simply sa=
y: if you offer the same PT value within multiple m- line, make sure you ca=
n handle the associated media when it arrives &#8211; period (keep in mind =
that you always indicate what you want to
 RECEIVE &#8211; the remote peer can still ask you to SEND using different =
PT values).<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal">If you don&#8217;t like this, please provide an alte=
rnative solution, because I want to close this issue in London. There is no=
 idea to keep &#8220;taking the issue back to the list&#8221;. We&#8217;ve =
done that for a few meetings already.<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal">Regards,<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal">Christer<o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB">_________=
______________________________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic">https://www.ietf.o=
rg/mailman/listinfo/mmusic</a><o:p></o:p></span></p>
</blockquote>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB"><o:p>&nbs=
p;</o:p></span></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-s=
ize:12.0pt;font-family:&quot;Lucida Sans Typewriter&quot;,&quot;serif&quot;=
;color:black;mso-fareast-language:EN-GB"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Lu=
cida Sans Typewriter&quot;,&quot;serif&quot;;color:black;mso-fareast-langua=
ge:EN-GB">--&nbsp;<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Lu=
cida Sans Typewriter&quot;,&quot;serif&quot;;color:black;mso-fareast-langua=
ge:EN-GB">Colin Perkins<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Lu=
cida Sans Typewriter&quot;,&quot;serif&quot;;color:black;mso-fareast-langua=
ge:EN-GB"><a href=3D"http://csperkins.org/">http://csperkins.org/</a><o:p><=
/o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Lu=
cida Sans Typewriter&quot;,&quot;serif&quot;;color:black;mso-fareast-langua=
ge:EN-GB"><o:p>&nbsp;</o:p></span></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB"><o:p>&nbs=
p;</o:p></span></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB"><o:p>&nbs=
p;</o:p></span></p>
</div>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B1D1C5A25ESESSMB209erics_--


From nobody Mon Mar  3 02:20:48 2014
Return-Path: <csp@csperkins.org>
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 376501A0E3F for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 02:20:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001] autolearn=ham
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 RPUmNUVOZ3Fa for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 02:20:44 -0800 (PST)
Received: from haggis.mythic-beasts.com (haggis.mythic-beasts.com [IPv6:2a00:1098:0:86:1000:0:2:1]) by ietfa.amsl.com (Postfix) with ESMTP id B99851A0DF3 for <mmusic@ietf.org>; Mon,  3 Mar 2014 02:20:43 -0800 (PST)
Received: from [31.133.156.67] (port=58834 helo=dhcp-9c43.meeting.ietf.org) by haggis.mythic-beasts.com with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from <csp@csperkins.org>) id 1WKPzC-0002E1-Mz; Mon, 03 Mar 2014 10:20:39 +0000
Content-Type: multipart/alternative; boundary="Apple-Mail=_2B6F36F9-0E08-4E2B-B047-D8BC75700947"
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D1C5A25@ESESSMB209.ericsson.se>
Date: Mon, 3 Mar 2014 10:20:36 +0000
Message-Id: <97FFA3D1-8159-43B8-BD02-02BF420D4464@csperkins.org>
References: <7594FB04B1934943A5C02806D1A2204B1D1C368D@ESESSMB209.ericsson.se> <7A9A37FB-196F-4F79-805B-95CE9B67C344@csperkins.org> <7594FB04B1934943A5C02806D1A2204B1D1C5A25@ESESSMB209.ericsson.se>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.1874)
X-BlackCat-Spam-Score: -28
X-Mythic-Debug: Threshold =  On = 
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/rCky2bL6MZ8uFY9T7FY2LcvB3hM
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for allowing usage of the same PT value within multiple m- lines?
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 10:20:46 -0000

--Apple-Mail=_2B6F36F9-0E08-4E2B-B047-D8BC75700947
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Hi,

I did suggest a definition of =93codec configuration=94 in my message. =
If that=92s not acceptable, then I suggest forbidding payload number =
reuse across m=3D lines.

Colin



On 3 Mar 2014, at 10:08, Christer Holmberg =
<christer.holmberg@ericsson.com> wrote:
> Hi Colin,
> =20
> We tried to define =93codec configuration=94, but we never got text =
that people could agree to.
> =20
> Personally I don=92t have any strong opinion which way we go =
(personally I am also ok forbidding re-usage of the same PT value). I =
just want to close the issue, and not once again =93take it to the =
list=94.
> =20
> Regards,
> =20
> Christer
> =20
> From: Colin Perkins [mailto:csp@csperkins.org]=20
> Sent: 03 March 2014 11:34
> To: Christer Holmberg
> Cc: mmusic@ietf.org
> Subject: Re: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for =
allowing usage of the same PT value within multiple m- lines?
> =20
> Christer,
> =20
> The bundled m=3D lines form a single RTP session. That means that they =
share a single RTP payload number space. The rule therefore has to be =
that you can only reuse the payload type across bundled m=3D lines if it =
refers to the exact same configuration of the exact same codec in all =
cases, where =93exact same configuration=94 means that the a=3Dfmtp: =
line and all other SDP attributes that configure the codec and =
packetisation of the media are identical.
> =20
> If that=92s not specific enough, then MUST NOT reuse payload types =
across m=3D lines in a bundled group is the safe choice. I believe your =
propose that it=92s okay if you can handle the media is too vague, and =
will cause us problems down the line.
> =20
> Colin
> =20
> =20
> =20
> =20
> On 2 Mar 2014, at 08:44, Christer Holmberg =
<christer.holmberg@ericsson.com> wrote:
> Hi,
> =20
> One of the open issues we have in BUNDLE, is when it is allowed to use =
the same PT value within multiple m- lines.
> =20
> We tried to come up with different criteria, including a =93codec =
configuration=94 concept, but we never managed to agree on something.
> =20
> So, in London, I intend to suggest that we simply say: if you offer =
the same PT value within multiple m- line, make sure you can handle the =
associated media when it arrives =96 period (keep in mind that you =
always indicate what you want to RECEIVE =96 the remote peer can still =
ask you to SEND using different PT values).
> =20
> If you don=92t like this, please provide an alternative solution, =
because I want to close this issue in London. There is no idea to keep =
=93taking the issue back to the list=94. We=92ve done that for a few =
meetings already.
> =20
> Regards,
> =20
> Christer
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
> =20
> =20
>=20
> --=20
> Colin Perkins
> http://csperkins.org/
> =20
> =20
> =20



--=20
Colin Perkins
http://csperkins.org/




--Apple-Mail=_2B6F36F9-0E08-4E2B-B047-D8BC75700947
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;">Hi,<div><br></div><div>I did suggest a definition of =
=93codec configuration=94 in my message. If that=92s not acceptable, =
then I suggest forbidding payload number reuse across m=3D =
lines.</div><div><br></div><div>Colin</div><div><br></div><div><br></div><=
div><br><div><div>On 3 Mar 2014, at 10:08, Christer Holmberg &lt;<a =
href=3D"mailto:christer.holmberg@ericsson.com">christer.holmberg@ericsson.=
com</a>&gt; wrote:</div><blockquote type=3D"cite">

<meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered =
medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"Lucida Sans Typewriter";
	panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.apple-style-span
	{mso-style-name:apple-style-span;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->

<div lang=3D"EN-GB" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1"><p class=3D"MsoNormal"><span =
style=3D"color:#1F497D">Hi Colin,<o:p></o:p></span></p><p =
class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span></p><p =
class=3D"MsoNormal"><span style=3D"color:#1F497D">We tried to define =
=93codec configuration=94, but we never got text that people could agree =
to.<o:p></o:p></span></p><p class=3D"MsoNormal"><span =
style=3D"color:#1F497D">&nbsp;</span></p><p class=3D"MsoNormal"><span =
style=3D"color:#1F497D">Personally I don=92t have any strong opinion =
which way we go (personally I am also ok forbidding re-usage of the same =
PT value). I just want to close the issue, and not once again =93take it =
to the list=94.<o:p></o:p></span></p><p class=3D"MsoNormal"><span =
style=3D"color:#1F497D">&nbsp;</span></p><p class=3D"MsoNormal"><span =
style=3D"color:#1F497D">Regards,<o:p></o:p></span></p><p =
class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span></p><p =
class=3D"MsoNormal"><span =
style=3D"color:#1F497D">Christer<o:p></o:p></span></p><p =
class=3D"MsoNormal"><a name=3D"_MailEndCompose"><span =
style=3D"color:#1F497D">&nbsp;</span></a></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt =
0cm 0cm 0cm"><p class=3D"MsoNormal"><b><span lang=3D"EN-US" =
style=3D"mso-fareast-language:EN-GB">From:</span></b><span lang=3D"EN-US" =
style=3D"mso-fareast-language:EN-GB"> Colin Perkins [<a =
href=3D"mailto:csp@csperkins.org">mailto:csp@csperkins.org</a>]
<br>
<b>Sent:</b> 03 March 2014 11:34<br>
<b>To:</b> Christer Holmberg<br>
<b>Cc:</b> <a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
<b>Subject:</b> Re: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria =
for allowing usage of the same PT value within multiple m- =
lines?<o:p></o:p></span></p>
</div>
</div><p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p><p =
class=3D"MsoNormal">Christer,<span =
style=3D"font-size:12.0pt;mso-fareast-language:EN-GB"><o:p></o:p></span></=
p>
<div><p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div><p class=3D"MsoNormal">The bundled m=3D lines form a single RTP =
session. That means that they share a single RTP payload number space. =
The rule therefore has to be that you can only reuse the payload type =
across bundled m=3D lines if it refers to the exact same configuration
 of the exact same codec in all cases, where =93exact same =
configuration=94 means that the a=3Dfmtp: line and all other SDP =
attributes that configure the codec and packetisation of the media are =
identical.<o:p></o:p></p>
</div>
<div><p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div><p class=3D"MsoNormal">If that=92s not specific enough, then MUST =
NOT reuse payload types across m=3D lines in a bundled group is the safe =
choice. I believe your propose that it=92s okay if you can handle the =
media is too vague, and will cause us problems down the
 line.<o:p></o:p></p>
</div>
<div><p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div><p class=3D"MsoNormal">Colin<o:p></o:p></p>
</div>
<div><p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div><p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div><p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div><p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div><p class=3D"MsoNormal">On 2 Mar 2014, at 08:44, Christer Holmberg =
&lt;<a =
href=3D"mailto:christer.holmberg@ericsson.com">christer.holmberg@ericsson.=
com</a>&gt; wrote:<o:p></o:p></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div><p class=3D"MsoNormal">Hi,<o:p></o:p></p><p =
class=3D"MsoNormal">&nbsp;<o:p></o:p></p><p class=3D"MsoNormal">One of =
the open issues we have in BUNDLE, is when it is allowed to use the same =
PT value within multiple m- lines.<o:p></o:p></p><p =
class=3D"MsoNormal">&nbsp;<o:p></o:p></p><p class=3D"MsoNormal">We tried =
to come up with different criteria, including a =93codec configuration=94 =
concept, but we never managed to agree on something.<o:p></o:p></p><p =
class=3D"MsoNormal">&nbsp;<o:p></o:p></p><p class=3D"MsoNormal">So, in =
London, I intend to suggest that we simply say: if you offer the same PT =
value within multiple m- line, make sure you can handle the associated =
media when it arrives =96 period (keep in mind that you always indicate =
what you want to
 RECEIVE =96 the remote peer can still ask you to SEND using different =
PT values).<o:p></o:p></p><p class=3D"MsoNormal">&nbsp;<o:p></o:p></p><p =
class=3D"MsoNormal">If you don=92t like this, please provide an =
alternative solution, because I want to close this issue in London. =
There is no idea to keep =93taking the issue back to the list=94. We=92ve =
done that for a few meetings already.<o:p></o:p></p><p =
class=3D"MsoNormal">&nbsp;<o:p></o:p></p><p =
class=3D"MsoNormal">Regards,<o:p></o:p></p><p =
class=3D"MsoNormal">&nbsp;<o:p></o:p></p><p =
class=3D"MsoNormal">Christer<o:p></o:p></p>
</div><p class=3D"MsoNormal"><span =
style=3D"font-size:12.0pt;font-family:&quot;Times New =
Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB">________________=
_______________________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
<a =
href=3D"https://www.ietf.org/mailman/listinfo/mmusic">https://www.ietf.org=
/mailman/listinfo/mmusic</a><o:p></o:p></span></p>
</blockquote>
</div><p class=3D"MsoNormal"><span =
style=3D"font-size:12.0pt;font-family:&quot;Times New =
Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB">&nbsp;</span></p=
>
<div>
<div><p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span =
style=3D"font-size: 12pt; font-family: 'Lucida Sans Typewriter', =
serif;">&nbsp;</span></p>
</div>
<div><p class=3D"MsoNormal"><span style=3D"font-size: 12pt; font-family: =
'Lucida Sans Typewriter', serif;">--&nbsp;<o:p></o:p></span></p>
</div>
<div><p class=3D"MsoNormal"><span style=3D"font-size: 12pt; font-family: =
'Lucida Sans Typewriter', serif;">Colin Perkins<o:p></o:p></span></p>
</div>
<div><p class=3D"MsoNormal"><span style=3D"font-size: 12pt; font-family: =
'Lucida Sans Typewriter', serif;"><a =
href=3D"http://csperkins.org/">http://csperkins.org/</a><o:p></o:p></span>=
</p>
</div>
<div><p class=3D"MsoNormal"><span style=3D"font-size: 12pt; font-family: =
'Lucida Sans Typewriter', serif;">&nbsp;</span></p>
</div><p class=3D"MsoNormal"><span =
style=3D"font-size:12.0pt;font-family:&quot;Times New =
Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB">&nbsp;</span></p=
>
</div><p class=3D"MsoNormal"><span =
style=3D"font-size:12.0pt;font-family:&quot;Times New =
Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB">&nbsp;</span></p=
>
</div>
</div>
</div>

</blockquote></div><br><div apple-content-edited=3D"true">
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
color: rgb(0, 0, 0); font-family: 'Lucida Sans Typewriter'; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-align: -webkit-auto; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px;  "><div><br =
class=3D"Apple-interchange-newline"><br =
class=3D"khtml-block-placeholder"></div><div>--&nbsp;</div><div></div><div=
>Colin Perkins</div><div><a =
href=3D"http://csperkins.org/">http://csperkins.org/</a></div><div><br></d=
iv></span><br class=3D"Apple-interchange-newline">

</div>
<br></div></body></html>=

--Apple-Mail=_2B6F36F9-0E08-4E2B-B047-D8BC75700947--


From nobody Mon Mar  3 02:35:00 2014
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 4104D1A0E64 for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 02:34:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.85
X-Spam-Level: 
X-Spam-Status: No, score=-3.85 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 WJ-mUSxrXBaI for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 02:34:54 -0800 (PST)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id 5C5771A0E80 for <mmusic@ietf.org>; Mon,  3 Mar 2014 02:34:44 -0800 (PST)
X-AuditID: c1b4fb25-b7f038e000005d01-fb-53145ac1cf5a
Received: from ESESSHC023.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 63.16.23809.1CA54135; Mon,  3 Mar 2014 11:34:41 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.216]) by ESESSHC023.ericsson.se ([153.88.183.87]) with mapi id 14.02.0387.000; Mon, 3 Mar 2014 11:26:33 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Colin Perkins <csp@csperkins.org>
Thread-Topic: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for allowing usage of the same PT value within multiple m- lines?
Thread-Index: Ac818yLx23ucJzjaSbubJw5GhjG+ygAyCDEAAAM6QvD///NSAP//7o6g
Date: Mon, 3 Mar 2014 10:26:33 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D1C5BBF@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D1C368D@ESESSMB209.ericsson.se> <7A9A37FB-196F-4F79-805B-95CE9B67C344@csperkins.org> <7594FB04B1934943A5C02806D1A2204B1D1C5A25@ESESSMB209.ericsson.se> <97FFA3D1-8159-43B8-BD02-02BF420D4464@csperkins.org>
In-Reply-To: <97FFA3D1-8159-43B8-BD02-02BF420D4464@csperkins.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.154]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1D1C5BBFESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrGLMWRmVeSWpSXmKPExsUyM+Jvje7BKJFgg8kvNC2WvzzBaDF1+WMW ByaPaffvs3ksWfKTKYApissmJTUnsyy1SN8ugStj47N1bAXH6yq+7fnM1sD4LK+LkZNDQsBE 4sjkzawQtpjEhXvr2boYuTiEBA4xSlzdu5gFwlnMKHH7ym2gDAcHm4CFRPc/bZAGEQFViR3H /zGChJkF1CWuLg4CKRcWaGGUaD1zgB3EERFoZZSY0n+ECaLBTaJ3bgsjiM0ioCKxuWMtC4jN K+Ar8fpIG9Tm/4wSExrngCU4BRwlli1aygxiMwKd9/3UGrBBzALiEreezGeCOFtAYsme88wQ tqjEy8f/oN5Rklh0+zNUfb5E46YedohlghInZz5hmcAoOgvJqFlIymYhKYOI60gs2P2JDcLW lli28DUzjH3mwGMmZPEFjOyrGNlzEzNz0suNNjEC4+rglt+qOxjvnBM5xCjNwaIkzvvhrXOQ kEB6YklqdmpqQWpRfFFpTmrxIUYmDk6pBsY4Y9tlPidypf/rbCgPi5lao7Cln+f7o6bXlxYd +fqxaQVDa7qG0ZdWv+M1caeVrwmVXCq7kPmyokN8RooL07prPRtzDc40u16aee2FueBSMR3l aJkAw/W2ve9fuscYz3orkJrJrZS7W+eEPXOL6aW3otFTjwTpfY/oDsxKYdxV8jzHnOtgkxJL cUaioRZzUXEiAKXYKhB5AgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/ZLUnHckQ2f2pVuzhA8_-kZZLfuc
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for allowing usage of the same PT value within multiple m- lines?
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 10:34:58 -0000

--_000_7594FB04B1934943A5C02806D1A2204B1D1C5BBFESESSMB209erics_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

>I did suggest a definition of "codec configuration" in my message. If that=
's not acceptable, then I >suggest forbidding payload number reuse across m=
=3D lines.

I was also told off-line that, in order to distinguish multiple media using=
 the same PT value, the SSRC values that are going to be used needs to be s=
ignalled.

However, when the initial offer is sent, the offerer does not know what the=
 answerer supports.

Regards,

Christer




On 3 Mar 2014, at 10:08, Christer Holmberg <christer.holmberg@ericsson.com<=
mailto:christer.holmberg@ericsson.com>> wrote:
Hi Colin,

We tried to define "codec configuration", but we never got text that people=
 could agree to.

Personally I don't have any strong opinion which way we go (personally I am=
 also ok forbidding re-usage of the same PT value). I just want to close th=
e issue, and not once again "take it to the list".

Regards,

Christer

From: Colin Perkins [mailto:csp@csperkins.org]
Sent: 03 March 2014 11:34
To: Christer Holmberg
Cc: mmusic@ietf.org<mailto:mmusic@ietf.org>
Subject: Re: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for allowi=
ng usage of the same PT value within multiple m- lines?

Christer,

The bundled m=3D lines form a single RTP session. That means that they shar=
e a single RTP payload number space. The rule therefore has to be that you =
can only reuse the payload type across bundled m=3D lines if it refers to t=
he exact same configuration of the exact same codec in all cases, where "ex=
act same configuration" means that the a=3Dfmtp: line and all other SDP att=
ributes that configure the codec and packetisation of the media are identic=
al.

If that's not specific enough, then MUST NOT reuse payload types across m=
=3D lines in a bundled group is the safe choice. I believe your propose tha=
t it's okay if you can handle the media is too vague, and will cause us pro=
blems down the line.

Colin




On 2 Mar 2014, at 08:44, Christer Holmberg <christer.holmberg@ericsson.com<=
mailto:christer.holmberg@ericsson.com>> wrote:
Hi,

One of the open issues we have in BUNDLE, is when it is allowed to use the =
same PT value within multiple m- lines.

We tried to come up with different criteria, including a "codec configurati=
on" concept, but we never managed to agree on something.

So, in London, I intend to suggest that we simply say: if you offer the sam=
e PT value within multiple m- line, make sure you can handle the associated=
 media when it arrives - period (keep in mind that you always indicate what=
 you want to RECEIVE - the remote peer can still ask you to SEND using diff=
erent PT values).

If you don't like this, please provide an alternative solution, because I w=
ant to close this issue in London. There is no idea to keep "taking the iss=
ue back to the list". We've done that for a few meetings already.

Regards,

Christer
_______________________________________________
mmusic mailing list
mmusic@ietf.org<mailto:mmusic@ietf.org>
https://www.ietf.org/mailman/listinfo/mmusic


--
Colin Perkins
http://csperkins.org/





--
Colin Perkins
http://csperkins.org/




--_000_7594FB04B1934943A5C02806D1A2204B1D1C5BBFESESSMB209erics_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"Lucida Sans Typewriter";}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.apple-style-span
	{mso-style-name:apple-style-span;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-GB" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi,<o:p></o:p></span><=
/p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&gt;</span>I did sugge=
st a definition of &#8220;codec configuration&#8221; in my message. If that=
&#8217;s not acceptable, then I
<span style=3D"color:#1F497D">&gt;</span>suggest forbidding payload number =
reuse across m=3D lines.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">I was also told off-li=
ne that, in order to distinguish multiple media using the same PT value, th=
e SSRC values that are going to be used needs to be signalled.<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">However, when the init=
ial offer is sent, the offerer does not know what the answerer supports.<o:=
p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Regards,<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Christer<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<p class=3D"MsoNormal">On 3 Mar 2014, at 10:08, Christer Holmberg &lt;<a hr=
ef=3D"mailto:christer.holmberg@ericsson.com">christer.holmberg@ericsson.com=
</a>&gt; wrote:<o:p></o:p></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi Colin,</span><o:p><=
/o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><o:p></o:=
p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">We tried to define &#8=
220;codec configuration&#8221;, but we never got text that people could agr=
ee to.</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><o:p></o:=
p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Personally I don&#8217=
;t have any strong opinion which way we go (personally I am also ok forbidd=
ing re-usage of the same PT value). I just want to close the issue, and not=
 once again &#8220;take it to the list&#8221;.</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><o:p></o:=
p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Regards,</span><o:p></=
o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><o:p></o:=
p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Christer</span><o:p></=
o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><o:p></o:=
p></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"mso-fareast-languag=
e:EN-GB">From:</span></b><span lang=3D"EN-US" style=3D"mso-fareast-language=
:EN-GB"> Colin Perkins [<a href=3D"mailto:csp@csperkins.org">mailto:csp@csp=
erkins.org</a>]
<br>
<b>Sent:</b> 03 March 2014 11:34<br>
<b>To:</b> Christer Holmberg<br>
<b>Cc:</b> <a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
<b>Subject:</b> Re: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for=
 allowing usage of the same PT value within multiple m- lines?</span><o:p><=
/o:p></p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal">Christer,<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">The bundled m=3D lines form a single RTP session. Th=
at means that they share a single RTP payload number space. The rule theref=
ore has to be that you can only reuse the payload type across bundled m=3D =
lines if it refers to the exact same configuration
 of the exact same codec in all cases, where &#8220;exact same configuratio=
n&#8221; means that the a=3Dfmtp: line and all other SDP attributes that co=
nfigure the codec and packetisation of the media are identical.<o:p></o:p><=
/p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">If that&#8217;s not specific enough, then MUST NOT r=
euse payload types across m=3D lines in a bundled group is the safe choice.=
 I believe your propose that it&#8217;s okay if you can handle the media is=
 too vague, and will cause us problems down the
 line.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Colin<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal">On 2 Mar 2014, at 08:44, Christer Holmberg &lt;<a hr=
ef=3D"mailto:christer.holmberg@ericsson.com">christer.holmberg@ericsson.com=
</a>&gt; wrote:<o:p></o:p></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal">Hi,<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal">One of the open issues we have in BUNDLE, is when it=
 is allowed to use the same PT value within multiple m- lines.<o:p></o:p></=
p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal">We tried to come up with different criteria, includi=
ng a &#8220;codec configuration&#8221; concept, but we never managed to agr=
ee on something.<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal">So, in London, I intend to suggest that we simply sa=
y: if you offer the same PT value within multiple m- line, make sure you ca=
n handle the associated media when it arrives &#8211; period (keep in mind =
that you always indicate what you want to
 RECEIVE &#8211; the remote peer can still ask you to SEND using different =
PT values).<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal">If you don&#8217;t like this, please provide an alte=
rnative solution, because I want to close this issue in London. There is no=
 idea to keep &#8220;taking the issue back to the list&#8221;. We&#8217;ve =
done that for a few meetings already.<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal">Regards,<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal">Christer<o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB">_________=
______________________________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic">https://www.ietf.o=
rg/mailman/listinfo/mmusic</a></span><o:p></o:p></p>
</blockquote>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB">&nbsp;</s=
pan><o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-s=
ize:12.0pt;font-family:&quot;Lucida Sans Typewriter&quot;">&nbsp;</span><o:=
p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Lu=
cida Sans Typewriter&quot;">--&nbsp;</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Lu=
cida Sans Typewriter&quot;">Colin Perkins</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Lu=
cida Sans Typewriter&quot;"><a href=3D"http://csperkins.org/">http://csperk=
ins.org/</a></span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Lu=
cida Sans Typewriter&quot;">&nbsp;</span><o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB">&nbsp;</s=
pan><o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB">&nbsp;</s=
pan><o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB"><o:p>&nbs=
p;</o:p></span></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span class=3D"apple-=
style-span"><span style=3D"font-family:&quot;Lucida Sans Typewriter&quot;;c=
olor:black"><o:p>&nbsp;</o:p></span></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span class=3D"apple-style-span"><span style=3D"font=
-size:12.0pt;font-family:&quot;Lucida Sans Typewriter&quot;;color:black;mso=
-fareast-language:EN-GB">--&nbsp;<o:p></o:p></span></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span class=3D"apple-style-span"><span style=3D"font=
-size:12.0pt;font-family:&quot;Lucida Sans Typewriter&quot;;color:black;mso=
-fareast-language:EN-GB">Colin Perkins<o:p></o:p></span></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span class=3D"apple-style-span"><span style=3D"font=
-size:12.0pt;font-family:&quot;Lucida Sans Typewriter&quot;;color:black;mso=
-fareast-language:EN-GB"><a href=3D"http://csperkins.org/">http://csperkins=
.org/</a><o:p></o:p></span></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span class=3D"apple-style-span"><span style=3D"font=
-size:12.0pt;font-family:&quot;Lucida Sans Typewriter&quot;;color:black;mso=
-fareast-language:EN-GB"><o:p>&nbsp;</o:p></span></span></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Times New Roman&quo=
t;,&quot;serif&quot;"><o:p>&nbsp;</o:p></span></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB"><o:p>&nbs=
p;</o:p></span></p>
</div>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B1D1C5BBFESESSMB209erics_--


From nobody Mon Mar  3 02:36:37 2014
Return-Path: <csp@csperkins.org>
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 9E16C1A0EAA for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 02:36:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001] autolearn=ham
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 DJhndcLg3ASO for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 02:36:31 -0800 (PST)
Received: from haggis.mythic-beasts.com (haggis.mythic-beasts.com [IPv6:2a00:1098:0:86:1000:0:2:1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F5031A0EA7 for <mmusic@ietf.org>; Mon,  3 Mar 2014 02:36:31 -0800 (PST)
Received: from [31.133.156.67] (port=59027 helo=dhcp-9c43.meeting.ietf.org) by haggis.mythic-beasts.com with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from <csp@csperkins.org>) id 1WKQEU-00061R-1Z; Mon, 03 Mar 2014 10:36:27 +0000
Content-Type: multipart/alternative; boundary="Apple-Mail=_A2A31F13-E316-4495-AE3C-3B9C52F7AB30"
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D1C5BBF@ESESSMB209.ericsson.se>
Date: Mon, 3 Mar 2014 10:36:24 +0000
Message-Id: <D1A5B4EB-45E0-4BFA-BB93-96119F1B8152@csperkins.org>
References: <7594FB04B1934943A5C02806D1A2204B1D1C368D@ESESSMB209.ericsson.se> <7A9A37FB-196F-4F79-805B-95CE9B67C344@csperkins.org> <7594FB04B1934943A5C02806D1A2204B1D1C5A25@ESESSMB209.ericsson.se> <97FFA3D1-8159-43B8-BD02-02BF420D4464@csperkins.org> <7594FB04B1934943A5C02806D1A2204B1D1C5BBF@ESESSMB209.ericsson.se>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.1874)
X-BlackCat-Spam-Score: -28
X-Mythic-Debug: Threshold =  On = 
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/cbS7HIAUOzKH9K4HPmimYPn1w3A
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for allowing usage of the same PT value within multiple m- lines?
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 10:36:34 -0000

--Apple-Mail=_A2A31F13-E316-4495-AE3C-3B9C52F7AB30
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

On 3 Mar 2014, at 10:26, Christer Holmberg =
<christer.holmberg@ericsson.com> wrote:
> Hi,
> =20
> >I did suggest a definition of =93codec configuration=94 in my =
message. If that=92s not acceptable, then I >suggest forbidding payload =
number reuse across m=3D lines.
> =20
> I was also told off-line that, in order to distinguish multiple media =
using the same PT value, the SSRC values that are going to be used needs =
to be signalled.

I don=92t think the method works with RTP. The payload type number space =
is per RTP session, not per SSRC.

Colin




> However, when the initial offer is sent, the offerer does not know =
what the answerer supports.
> =20
> Regards,
> =20
> Christer
> =20
> =20
> =20
> =20
> On 3 Mar 2014, at 10:08, Christer Holmberg =
<christer.holmberg@ericsson.com> wrote:
> Hi Colin,
> =20
> We tried to define =93codec configuration=94, but we never got text =
that people could agree to.
> =20
> Personally I don=92t have any strong opinion which way we go =
(personally I am also ok forbidding re-usage of the same PT value). I =
just want to close the issue, and not once again =93take it to the =
list=94.
> =20
> Regards,
> =20
> Christer
> =20
> From: Colin Perkins [mailto:csp@csperkins.org]=20
> Sent: 03 March 2014 11:34
> To: Christer Holmberg
> Cc: mmusic@ietf.org
> Subject: Re: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for =
allowing usage of the same PT value within multiple m- lines?
> =20
> Christer,
> =20
> The bundled m=3D lines form a single RTP session. That means that they =
share a single RTP payload number space. The rule therefore has to be =
that you can only reuse the payload type across bundled m=3D lines if it =
refers to the exact same configuration of the exact same codec in all =
cases, where =93exact same configuration=94 means that the a=3Dfmtp: =
line and all other SDP attributes that configure the codec and =
packetisation of the media are identical.
> =20
> If that=92s not specific enough, then MUST NOT reuse payload types =
across m=3D lines in a bundled group is the safe choice. I believe your =
propose that it=92s okay if you can handle the media is too vague, and =
will cause us problems down the line.
> =20
> Colin
> =20
> =20
> =20
> =20
> On 2 Mar 2014, at 08:44, Christer Holmberg =
<christer.holmberg@ericsson.com> wrote:
> Hi,
> =20
> One of the open issues we have in BUNDLE, is when it is allowed to use =
the same PT value within multiple m- lines.
> =20
> We tried to come up with different criteria, including a =93codec =
configuration=94 concept, but we never managed to agree on something.
> =20
> So, in London, I intend to suggest that we simply say: if you offer =
the same PT value within multiple m- line, make sure you can handle the =
associated media when it arrives =96 period (keep in mind that you =
always indicate what you want to RECEIVE =96 the remote peer can still =
ask you to SEND using different PT values).
> =20
> If you don=92t like this, please provide an alternative solution, =
because I want to close this issue in London. There is no idea to keep =
=93taking the issue back to the list=94. We=92ve done that for a few =
meetings already.
> =20
> Regards,
> =20
> Christer
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
> =20
> =20
>=20
> --=20
> Colin Perkins
> http://csperkins.org/
> =20
> =20
> =20
> =20
> =20
>=20
> --=20
> Colin Perkins
> http://csperkins.org/
> =20
> =20
> =20



--=20
Colin Perkins
http://csperkins.org/




--Apple-Mail=_A2A31F13-E316-4495-AE3C-3B9C52F7AB30
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">On 3 Mar 2014, at 10:26, Christer Holmberg &lt;<a =
href=3D"mailto:christer.holmberg@ericsson.com">christer.holmberg@ericsson.=
com</a>&gt; wrote:<div><blockquote type=3D"cite">

<meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dus-ascii" class=3D"">
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)" =
class=3D"">
<style class=3D""><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"Lucida Sans Typewriter";}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.apple-style-span
	{mso-style-name:apple-style-span;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->

<div lang=3D"EN-GB" link=3D"#0563C1" vlink=3D"#954F72" class=3D"">
<div class=3D"WordSection1"><p class=3D"MsoNormal"><span =
style=3D"color:#1F497D" class=3D"">Hi,<o:p class=3D""></o:p></span></p>
<div class=3D""><p class=3D"MsoNormal"><o:p class=3D"">&nbsp;</o:p></p>
</div>
<div class=3D""><p class=3D"MsoNormal"><span style=3D"color:#1F497D" =
class=3D"">&gt;</span>I did suggest a definition of =93codec =
configuration=94 in my message. If that=92s not acceptable, then I
<span style=3D"color:#1F497D" class=3D"">&gt;</span>suggest forbidding =
payload number reuse across m=3D lines.<o:p class=3D""></o:p></p>
</div>
<div class=3D""><p class=3D"MsoNormal"><span style=3D"color:#1F497D" =
class=3D"">&nbsp;</span></p><p class=3D"MsoNormal"><span =
style=3D"color:#1F497D" class=3D"">I was also told off-line that, in =
order to distinguish multiple media using the same PT value, the SSRC =
values that are going to be used needs to be =
signalled.</span></p></div></div></div></blockquote><div><br></div>I =
don=92t think the method works with RTP. The payload type number space =
is per RTP session, not per =
SSRC.</div><div><br></div><div>Colin</div><div><br></div><div><br></div><d=
iv><br class=3D""><br class=3D""><blockquote type=3D"cite"><div =
lang=3D"EN-GB" link=3D"#0563C1" vlink=3D"#954F72" class=3D""><div =
class=3D"WordSection1"><div class=3D""><p class=3D"MsoNormal"><span =
style=3D"color:#1F497D" class=3D"">However, when the initial offer is =
sent, the offerer does not know what the answerer supports.<o:p =
class=3D""></o:p></span></p><p class=3D"MsoNormal"><span =
style=3D"color:#1F497D" class=3D"">&nbsp;</span></p><p =
class=3D"MsoNormal"><span style=3D"color:#1F497D" class=3D"">Regards,<o:p =
class=3D""></o:p></span></p><p class=3D"MsoNormal"><span =
style=3D"color:#1F497D" class=3D"">&nbsp;</span></p><p =
class=3D"MsoNormal"><span style=3D"color:#1F497D" class=3D"">Christer<o:p =
class=3D""></o:p></span></p><p class=3D"MsoNormal"><span =
style=3D"color:#1F497D" class=3D"">&nbsp;</span></p>
</div>
<div class=3D""><p class=3D"MsoNormal"><o:p class=3D"">&nbsp;</o:p></p>
</div>
<div class=3D""><p class=3D"MsoNormal"><o:p class=3D"">&nbsp;</o:p></p>
</div>
<div class=3D""><p class=3D"MsoNormal"><o:p class=3D"">&nbsp;</o:p></p>
<div class=3D"">
<div class=3D""><p class=3D"MsoNormal">On 3 Mar 2014, at 10:08, Christer =
Holmberg &lt;<a href=3D"mailto:christer.holmberg@ericsson.com" =
class=3D"">christer.holmberg@ericsson.com</a>&gt; wrote:<o:p =
class=3D""></o:p></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt" class=3D"">
<div class=3D""><p class=3D"MsoNormal"><span style=3D"color:#1F497D" =
class=3D"">Hi Colin,</span><o:p class=3D""></o:p></p><p =
class=3D"MsoNormal"><span style=3D"color:#1F497D" =
class=3D"">&nbsp;</span><o:p class=3D""></o:p></p><p =
class=3D"MsoNormal"><span style=3D"color:#1F497D" class=3D"">We tried to =
define =93codec configuration=94, but we never got text that people =
could agree to.</span><o:p class=3D""></o:p></p><p =
class=3D"MsoNormal"><span style=3D"color:#1F497D" =
class=3D"">&nbsp;</span><o:p class=3D""></o:p></p><p =
class=3D"MsoNormal"><span style=3D"color:#1F497D" class=3D"">Personally =
I don=92t have any strong opinion which way we go (personally I am also =
ok forbidding re-usage of the same PT value). I just want to close the =
issue, and not once again =93take it to the list=94.</span><o:p =
class=3D""></o:p></p><p class=3D"MsoNormal"><span style=3D"color:#1F497D" =
class=3D"">&nbsp;</span><o:p class=3D""></o:p></p><p =
class=3D"MsoNormal"><span style=3D"color:#1F497D" =
class=3D"">Regards,</span><o:p class=3D""></o:p></p><p =
class=3D"MsoNormal"><span style=3D"color:#1F497D" =
class=3D"">&nbsp;</span><o:p class=3D""></o:p></p><p =
class=3D"MsoNormal"><span style=3D"color:#1F497D" =
class=3D"">Christer</span><o:p class=3D""></o:p></p><p =
class=3D"MsoNormal"><span style=3D"color:#1F497D" =
class=3D"">&nbsp;</span><o:p class=3D""></o:p></p>
<div class=3D"">
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt =
0cm 0cm 0cm" class=3D""><p class=3D"MsoNormal"><b class=3D""><span =
lang=3D"EN-US" style=3D"mso-fareast-language:EN-GB" =
class=3D"">From:</span></b><span lang=3D"EN-US" =
style=3D"mso-fareast-language:EN-GB" class=3D""> Colin Perkins [<a =
href=3D"mailto:csp@csperkins.org" class=3D"">mailto:csp@csperkins.org</a>]=

<br class=3D"">
<b class=3D"">Sent:</b> 03 March 2014 11:34<br class=3D"">
<b class=3D"">To:</b> Christer Holmberg<br class=3D"">
<b class=3D"">Cc:</b> <a href=3D"mailto:mmusic@ietf.org" =
class=3D"">mmusic@ietf.org</a><br class=3D"">
<b class=3D"">Subject:</b> Re: [MMUSIC] IETF#89: BUNDLE: Q9: What are =
the criteria for allowing usage of the same PT value within multiple m- =
lines?</span><o:p class=3D""></o:p></p>
</div>
</div><p class=3D"MsoNormal">&nbsp;<o:p class=3D""></o:p></p><p =
class=3D"MsoNormal">Christer,<o:p class=3D""></o:p></p>
<div class=3D""><p class=3D"MsoNormal">&nbsp;<o:p class=3D""></o:p></p>
</div>
<div class=3D""><p class=3D"MsoNormal">The bundled m=3D lines form a =
single RTP session. That means that they share a single RTP payload =
number space. The rule therefore has to be that you can only reuse the =
payload type across bundled m=3D lines if it refers to the exact same =
configuration
 of the exact same codec in all cases, where =93exact same =
configuration=94 means that the a=3Dfmtp: line and all other SDP =
attributes that configure the codec and packetisation of the media are =
identical.<o:p class=3D""></o:p></p>
</div>
<div class=3D""><p class=3D"MsoNormal">&nbsp;<o:p class=3D""></o:p></p>
</div>
<div class=3D""><p class=3D"MsoNormal">If that=92s not specific enough, =
then MUST NOT reuse payload types across m=3D lines in a bundled group =
is the safe choice. I believe your propose that it=92s okay if you can =
handle the media is too vague, and will cause us problems down the
 line.<o:p class=3D""></o:p></p>
</div>
<div class=3D""><p class=3D"MsoNormal">&nbsp;<o:p class=3D""></o:p></p>
</div>
<div class=3D""><p class=3D"MsoNormal">Colin<o:p class=3D""></o:p></p>
</div>
<div class=3D""><p class=3D"MsoNormal">&nbsp;<o:p class=3D""></o:p></p>
</div>
<div class=3D""><p class=3D"MsoNormal">&nbsp;<o:p class=3D""></o:p></p>
</div>
<div class=3D""><p class=3D"MsoNormal">&nbsp;<o:p class=3D""></o:p></p>
</div>
<div class=3D""><p class=3D"MsoNormal">&nbsp;<o:p class=3D""></o:p></p>
<div class=3D"">
<div class=3D""><p class=3D"MsoNormal">On 2 Mar 2014, at 08:44, Christer =
Holmberg &lt;<a href=3D"mailto:christer.holmberg@ericsson.com" =
class=3D"">christer.holmberg@ericsson.com</a>&gt; wrote:<o:p =
class=3D""></o:p></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt" class=3D"">
<div class=3D""><p class=3D"MsoNormal">Hi,<o:p class=3D""></o:p></p><p =
class=3D"MsoNormal">&nbsp;<o:p class=3D""></o:p></p><p =
class=3D"MsoNormal">One of the open issues we have in BUNDLE, is when it =
is allowed to use the same PT value within multiple m- lines.<o:p =
class=3D""></o:p></p><p class=3D"MsoNormal">&nbsp;<o:p =
class=3D""></o:p></p><p class=3D"MsoNormal">We tried to come up with =
different criteria, including a =93codec configuration=94 concept, but =
we never managed to agree on something.<o:p class=3D""></o:p></p><p =
class=3D"MsoNormal">&nbsp;<o:p class=3D""></o:p></p><p =
class=3D"MsoNormal">So, in London, I intend to suggest that we simply =
say: if you offer the same PT value within multiple m- line, make sure =
you can handle the associated media when it arrives =96 period (keep in =
mind that you always indicate what you want to
 RECEIVE =96 the remote peer can still ask you to SEND using different =
PT values).<o:p class=3D""></o:p></p><p class=3D"MsoNormal">&nbsp;<o:p =
class=3D""></o:p></p><p class=3D"MsoNormal">If you don=92t like this, =
please provide an alternative solution, because I want to close this =
issue in London. There is no idea to keep =93taking the issue back to =
the list=94. We=92ve done that for a few meetings already.<o:p =
class=3D""></o:p></p><p class=3D"MsoNormal">&nbsp;<o:p =
class=3D""></o:p></p><p class=3D"MsoNormal">Regards,<o:p =
class=3D""></o:p></p><p class=3D"MsoNormal">&nbsp;<o:p =
class=3D""></o:p></p><p class=3D"MsoNormal">Christer<o:p =
class=3D""></o:p></p>
</div><p class=3D"MsoNormal"><span =
style=3D"font-size:12.0pt;font-family:&quot;Times New =
Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB" =
class=3D"">_______________________________________________<br class=3D"">
mmusic mailing list<br class=3D"">
<a href=3D"mailto:mmusic@ietf.org" class=3D"">mmusic@ietf.org</a><br =
class=3D"">
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" =
class=3D"">https://www.ietf.org/mailman/listinfo/mmusic</a></span><o:p =
class=3D""></o:p></p>
</blockquote>
</div><p class=3D"MsoNormal"><span =
style=3D"font-size:12.0pt;font-family:&quot;Times New =
Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB" =
class=3D"">&nbsp;</span><o:p class=3D""></o:p></p>
<div class=3D"">
<div class=3D""><p style=3D"margin-bottom:12.0pt" =
class=3D"MsoNormal"><span =
style=3D"font-size:12.0pt;font-family:&quot;Lucida Sans =
Typewriter&quot;" class=3D"">&nbsp;</span><o:p class=3D""></o:p></p>
</div>
<div class=3D""><p class=3D"MsoNormal"><span =
style=3D"font-size:12.0pt;font-family:&quot;Lucida Sans =
Typewriter&quot;" class=3D"">--&nbsp;</span><o:p class=3D""></o:p></p>
</div>
<div class=3D""><p class=3D"MsoNormal"><span =
style=3D"font-size:12.0pt;font-family:&quot;Lucida Sans =
Typewriter&quot;" class=3D"">Colin Perkins</span><o:p =
class=3D""></o:p></p>
</div>
<div class=3D""><p class=3D"MsoNormal"><span =
style=3D"font-size:12.0pt;font-family:&quot;Lucida Sans =
Typewriter&quot;" class=3D""><a href=3D"http://csperkins.org/" =
class=3D"">http://csperkins.org/</a></span><o:p class=3D""></o:p></p>
</div>
<div class=3D""><p class=3D"MsoNormal"><span =
style=3D"font-size:12.0pt;font-family:&quot;Lucida Sans =
Typewriter&quot;" class=3D"">&nbsp;</span><o:p class=3D""></o:p></p>
</div><p class=3D"MsoNormal"><span =
style=3D"font-size:12.0pt;font-family:&quot;Times New =
Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB" =
class=3D"">&nbsp;</span><o:p class=3D""></o:p></p>
</div><p class=3D"MsoNormal"><span =
style=3D"font-size:12.0pt;font-family:&quot;Times New =
Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB" =
class=3D"">&nbsp;</span><o:p class=3D""></o:p></p>
</div>
</div>
</blockquote>
</div><p class=3D"MsoNormal"><span =
style=3D"font-size:12.0pt;font-family:&quot;Times New =
Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB" =
class=3D"">&nbsp;</span></p>
<div class=3D"">
<div class=3D""><p style=3D"margin-bottom:12.0pt" =
class=3D"MsoNormal"><span class=3D"apple-style-span"><span =
style=3D"font-family: 'Lucida Sans Typewriter';" =
class=3D"">&nbsp;</span></span></p>
</div>
<div class=3D""><p class=3D"MsoNormal"><span =
class=3D"apple-style-span"><span style=3D"font-size: 12pt; font-family: =
'Lucida Sans Typewriter';" class=3D"">--&nbsp;<o:p =
class=3D""></o:p></span></span></p>
</div>
<div class=3D""><p class=3D"MsoNormal"><span =
class=3D"apple-style-span"><span style=3D"font-size: 12pt; font-family: =
'Lucida Sans Typewriter';" class=3D"">Colin Perkins<o:p =
class=3D""></o:p></span></span></p>
</div>
<div class=3D""><p class=3D"MsoNormal"><span =
class=3D"apple-style-span"><span style=3D"font-size: 12pt; font-family: =
'Lucida Sans Typewriter';" class=3D""><a href=3D"http://csperkins.org/" =
class=3D"">http://csperkins.org/</a><o:p =
class=3D""></o:p></span></span></p>
</div>
<div class=3D""><p class=3D"MsoNormal"><span =
class=3D"apple-style-span"><span style=3D"font-size: 12pt; font-family: =
'Lucida Sans Typewriter';" class=3D"">&nbsp;</span></span></p>
</div><p class=3D"MsoNormal"><span style=3D"font-family:&quot;Times New =
Roman&quot;,&quot;serif&quot;" class=3D"">&nbsp;</span></p>
</div><p class=3D"MsoNormal"><span =
style=3D"font-size:12.0pt;font-family:&quot;Times New =
Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB" =
class=3D"">&nbsp;</span></p>
</div>
</div>
</div>

</blockquote></div><br class=3D""><div apple-content-edited=3D"true" =
class=3D"">
<span style=3D"border-collapse: separate; border-spacing: 0px;" =
class=3D"Apple-style-span"><div class=3D""><br =
class=3D"Apple-interchange-newline"><br =
class=3D"khtml-block-placeholder"></div><div class=3D"">--&nbsp;</div><div=
 class=3D""></div><div class=3D"">Colin Perkins</div><div class=3D""><a =
href=3D"http://csperkins.org/">http://csperkins.org/</a></div><div =
class=3D""><br class=3D""></div></span><br =
class=3D"Apple-interchange-newline">

</div>
<br class=3D""></body></html>=

--Apple-Mail=_A2A31F13-E316-4495-AE3C-3B9C52F7AB30--


From nobody Mon Mar  3 02:48:55 2014
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 3B4071A0ED6 for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 02:48:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 V4HT-rqbA2Nj for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 02:48:49 -0800 (PST)
Received: from sesbmg20.ericsson.net (sesbmg20.ericsson.net [193.180.251.56]) by ietfa.amsl.com (Postfix) with ESMTP id 36A871A0ECF for <mmusic@ietf.org>; Mon,  3 Mar 2014 02:48:48 -0800 (PST)
X-AuditID: c1b4fb38-b7f418e000001099-9d-53145e0c4757
Received: from ESESSHC020.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg20.ericsson.net (Symantec Mail Security) with SMTP id FB.D9.04249.C0E54135; Mon,  3 Mar 2014 11:48:44 +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 11:48:43 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Colin Perkins <csp@csperkins.org>
Thread-Topic: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for allowing usage of the same PT value within multiple m- lines?
Thread-Index: Ac818yLx23ucJzjaSbubJw5GhjG+ygAyCDEAAAM6QvD///NSAP//7o6ggAAV3AD//+xLsA==
Date: Mon, 3 Mar 2014 10:48:42 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D1C5CCE@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D1C368D@ESESSMB209.ericsson.se> <7A9A37FB-196F-4F79-805B-95CE9B67C344@csperkins.org> <7594FB04B1934943A5C02806D1A2204B1D1C5A25@ESESSMB209.ericsson.se> <97FFA3D1-8159-43B8-BD02-02BF420D4464@csperkins.org> <7594FB04B1934943A5C02806D1A2204B1D1C5BBF@ESESSMB209.ericsson.se> <D1A5B4EB-45E0-4BFA-BB93-96119F1B8152@csperkins.org>
In-Reply-To: <D1A5B4EB-45E0-4BFA-BB93-96119F1B8152@csperkins.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.154]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1D1C5CCEESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrJLMWRmVeSWpSXmKPExsUyM+JvjS5PnEiwwft1GhbLX55gtJi6/DGL A5PHtPv32TyWLPnJFMAUxWWTkpqTWZZapG+XwJVxcOZC9oIXqxgrGt8uYW5g3DqNsYuRk0NC wERi4qp7zBC2mMSFe+vZuhi5OIQEjjBKnDq+gwXCWcwocWTzfNYuRg4ONgELie5/2iANIgKq EjuO/2MECTMLqEtcXRwEUi4s0MIo0XrmADuIIyLQyigxpf8IE0RDmMSzr+tZQWwWARWJPa9u g13BK+ArcX7LEVaIZb+YJJZNes4CkuAUcJQ4unQWWAMj0HnfT60BG8QsIC5x68l8JoizBSSW 7DkP9YKoxMvH/1ghbCWJRbc/Q9XnS5zdsosJYpmgxMmZT1gmMIrOQjJqFpKyWUjKIOI6Egt2 f2KDsLUlli18zQxjnznwmAlZfAEj+ypGjuLU4qTcdCODTYzA6Dq45bfFDsbLf20OMUpzsCiJ 83586xwkJJCeWJKanZpakFoUX1Sak1p8iJGJg1OqgTF9l3tY6FFNR/ara7JTI2y5XJVSzjRH cWuYaV59lMp4aeaqRC6761nfHOeejrixfA9HjaJoN7/5/D9eqXENmyJTq6Ye4Uo+XMP5slri sHbpYvewvRxrX25kYt5ZdWjHHT/zFQ4RvtLNzmuP3GBI/D9v0ffru1fdzL95R/rolZ/T02R2 /TGN6lFiKc5INNRiLipOBACmv9l+fAIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/vlIMaIuAVitmyBpZGe5ZQC3xrO0
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for allowing usage of the same PT value within multiple m- lines?
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 10:48:52 -0000

--_000_7594FB04B1934943A5C02806D1A2204B1D1C5CCEESESSMB209erics_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Colin,

Within an RTP session, if you receive two media streams, both using the sam=
e PT value (let's assume they use the same codec configuration), how will y=
ou separate the received media packets?

Regards,

Christer

From: Colin Perkins [mailto:csp@csperkins.org]
Sent: 03 March 2014 12:36
To: Christer Holmberg
Cc: mmusic@ietf.org
Subject: Re: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for allowi=
ng usage of the same PT value within multiple m- lines?

On 3 Mar 2014, at 10:26, Christer Holmberg <christer.holmberg@ericsson.com<=
mailto:christer.holmberg@ericsson.com>> wrote:
Hi,

>I did suggest a definition of "codec configuration" in my message. If that=
's not acceptable, then I >suggest forbidding payload number reuse across m=
=3D lines.

I was also told off-line that, in order to distinguish multiple media using=
 the same PT value, the SSRC values that are going to be used needs to be s=
ignalled.

I don't think the method works with RTP. The payload type number space is p=
er RTP session, not per SSRC.

Colin





However, when the initial offer is sent, the offerer does not know what the=
 answerer supports.

Regards,

Christer




On 3 Mar 2014, at 10:08, Christer Holmberg <christer.holmberg@ericsson.com<=
mailto:christer.holmberg@ericsson.com>> wrote:
Hi Colin,

We tried to define "codec configuration", but we never got text that people=
 could agree to.

Personally I don't have any strong opinion which way we go (personally I am=
 also ok forbidding re-usage of the same PT value). I just want to close th=
e issue, and not once again "take it to the list".

Regards,

Christer

From: Colin Perkins [mailto:csp@csperkins.org]
Sent: 03 March 2014 11:34
To: Christer Holmberg
Cc: mmusic@ietf.org<mailto:mmusic@ietf.org>
Subject: Re: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for allowi=
ng usage of the same PT value within multiple m- lines?

Christer,

The bundled m=3D lines form a single RTP session. That means that they shar=
e a single RTP payload number space. The rule therefore has to be that you =
can only reuse the payload type across bundled m=3D lines if it refers to t=
he exact same configuration of the exact same codec in all cases, where "ex=
act same configuration" means that the a=3Dfmtp: line and all other SDP att=
ributes that configure the codec and packetisation of the media are identic=
al.

If that's not specific enough, then MUST NOT reuse payload types across m=
=3D lines in a bundled group is the safe choice. I believe your propose tha=
t it's okay if you can handle the media is too vague, and will cause us pro=
blems down the line.

Colin




On 2 Mar 2014, at 08:44, Christer Holmberg <christer.holmberg@ericsson.com<=
mailto:christer.holmberg@ericsson.com>> wrote:
Hi,

One of the open issues we have in BUNDLE, is when it is allowed to use the =
same PT value within multiple m- lines.

We tried to come up with different criteria, including a "codec configurati=
on" concept, but we never managed to agree on something.

So, in London, I intend to suggest that we simply say: if you offer the sam=
e PT value within multiple m- line, make sure you can handle the associated=
 media when it arrives - period (keep in mind that you always indicate what=
 you want to RECEIVE - the remote peer can still ask you to SEND using diff=
erent PT values).

If you don't like this, please provide an alternative solution, because I w=
ant to close this issue in London. There is no idea to keep "taking the iss=
ue back to the list". We've done that for a few meetings already.

Regards,

Christer
_______________________________________________
mmusic mailing list
mmusic@ietf.org<mailto:mmusic@ietf.org>
https://www.ietf.org/mailman/listinfo/mmusic


--
Colin Perkins
http://csperkins.org/





--
Colin Perkins
http://csperkins.org/





--
Colin Perkins
http://csperkins.org/




--_000_7594FB04B1934943A5C02806D1A2204B1D1C5CCEESESSMB209erics_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"Lucida Sans Typewriter";}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.apple-style-span
	{mso-style-name:apple-style-span;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle21
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-GB" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi Colin,<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Within an RTP session,=
 if you receive two media streams, both using the same PT value (let&#8217;=
s assume they use the same codec configuration), how will you separate the =
received media packets?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Regards,<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Christer<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><a name=3D"_MailEndCompose"><span style=3D"color:#1F=
497D"><o:p>&nbsp;</o:p></span></a></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"mso-fareast-languag=
e:EN-GB">From:</span></b><span lang=3D"EN-US" style=3D"mso-fareast-language=
:EN-GB"> Colin Perkins [mailto:csp@csperkins.org]
<br>
<b>Sent:</b> 03 March 2014 12:36<br>
<b>To:</b> Christer Holmberg<br>
<b>Cc:</b> mmusic@ietf.org<br>
<b>Subject:</b> Re: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for=
 allowing usage of the same PT value within multiple m- lines?<o:p></o:p></=
span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">On 3 Mar 2014, at 10:26, Christer Holmberg &lt;<a hr=
ef=3D"mailto:christer.holmberg@ericsson.com">christer.holmberg@ericsson.com=
</a>&gt; wrote:<span style=3D"font-size:12.0pt;mso-fareast-language:EN-GB">=
<o:p></o:p></span></p>
<div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi,</span><o:p></o:p><=
/p>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&gt;</span>I did sugge=
st a definition of &#8220;codec configuration&#8221; in my message. If that=
&#8217;s not acceptable, then I
<span style=3D"color:#1F497D">&gt;</span>suggest forbidding payload number =
reuse across m=3D lines.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><o:p></o:=
p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">I was also told off-li=
ne that, in order to distinguish multiple media using the same PT value, th=
e SSRC values that are going to be used needs to be signalled.</span><o:p><=
/o:p></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB"><o:p>&nbs=
p;</o:p></span></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB">I don&#82=
17;t think the method works with RTP. The payload type number space is per =
RTP session, not per SSRC.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB"><o:p>&nbs=
p;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB">Colin<o:p=
></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB"><o:p>&nbs=
p;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB"><o:p>&nbs=
p;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB"><br>
<br>
<br>
<o:p></o:p></span></p>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">However, when the init=
ial offer is sent, the offerer does not know what the answerer supports.</s=
pan><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><o:p></o:=
p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Regards,</span><o:p></=
o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><o:p></o:=
p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Christer</span><o:p></=
o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><o:p></o:=
p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal">On 3 Mar 2014, at 10:08, Christer Holmberg &lt;<a hr=
ef=3D"mailto:christer.holmberg@ericsson.com">christer.holmberg@ericsson.com=
</a>&gt; wrote:<o:p></o:p></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi Colin,</span><o:p><=
/o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><o:p></o:=
p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">We tried to define &#8=
220;codec configuration&#8221;, but we never got text that people could agr=
ee to.</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><o:p></o:=
p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Personally I don&#8217=
;t have any strong opinion which way we go (personally I am also ok forbidd=
ing re-usage of the same PT value). I just want to close the issue, and not=
 once again &#8220;take it to the list&#8221;.</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><o:p></o:=
p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Regards,</span><o:p></=
o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><o:p></o:=
p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Christer</span><o:p></=
o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><o:p></o:=
p></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"mso-fareast-languag=
e:EN-GB">From:</span></b><span lang=3D"EN-US" style=3D"mso-fareast-language=
:EN-GB"> Colin Perkins [<a href=3D"mailto:csp@csperkins.org">mailto:csp@csp=
erkins.org</a>]
<br>
<b>Sent:</b> 03 March 2014 11:34<br>
<b>To:</b> Christer Holmberg<br>
<b>Cc:</b> <a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
<b>Subject:</b> Re: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for=
 allowing usage of the same PT value within multiple m- lines?</span><o:p><=
/o:p></p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal">Christer,<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">The bundled m=3D lines form a single RTP session. Th=
at means that they share a single RTP payload number space. The rule theref=
ore has to be that you can only reuse the payload type across bundled m=3D =
lines if it refers to the exact same configuration
 of the exact same codec in all cases, where &#8220;exact same configuratio=
n&#8221; means that the a=3Dfmtp: line and all other SDP attributes that co=
nfigure the codec and packetisation of the media are identical.<o:p></o:p><=
/p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">If that&#8217;s not specific enough, then MUST NOT r=
euse payload types across m=3D lines in a bundled group is the safe choice.=
 I believe your propose that it&#8217;s okay if you can handle the media is=
 too vague, and will cause us problems down the
 line.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Colin<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal">On 2 Mar 2014, at 08:44, Christer Holmberg &lt;<a hr=
ef=3D"mailto:christer.holmberg@ericsson.com">christer.holmberg@ericsson.com=
</a>&gt; wrote:<o:p></o:p></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal">Hi,<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal">One of the open issues we have in BUNDLE, is when it=
 is allowed to use the same PT value within multiple m- lines.<o:p></o:p></=
p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal">We tried to come up with different criteria, includi=
ng a &#8220;codec configuration&#8221; concept, but we never managed to agr=
ee on something.<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal">So, in London, I intend to suggest that we simply sa=
y: if you offer the same PT value within multiple m- line, make sure you ca=
n handle the associated media when it arrives &#8211; period (keep in mind =
that you always indicate what you want to
 RECEIVE &#8211; the remote peer can still ask you to SEND using different =
PT values).<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal">If you don&#8217;t like this, please provide an alte=
rnative solution, because I want to close this issue in London. There is no=
 idea to keep &#8220;taking the issue back to the list&#8221;. We&#8217;ve =
done that for a few meetings already.<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal">Regards,<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal">Christer<o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB">_________=
______________________________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic">https://www.ietf.o=
rg/mailman/listinfo/mmusic</a></span><o:p></o:p></p>
</blockquote>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB">&nbsp;</s=
pan><o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-s=
ize:12.0pt;font-family:&quot;Lucida Sans Typewriter&quot;">&nbsp;</span><o:=
p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Lu=
cida Sans Typewriter&quot;">--&nbsp;</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Lu=
cida Sans Typewriter&quot;">Colin Perkins</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Lu=
cida Sans Typewriter&quot;"><a href=3D"http://csperkins.org/">http://csperk=
ins.org/</a></span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Lu=
cida Sans Typewriter&quot;">&nbsp;</span><o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB">&nbsp;</s=
pan><o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB">&nbsp;</s=
pan><o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB">&nbsp;</s=
pan><o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span class=3D"apple-=
style-span"><span style=3D"font-family:&quot;Lucida Sans Typewriter&quot;">=
&nbsp;</span></span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span class=3D"apple-style-span"><span style=3D"font=
-size:12.0pt;font-family:&quot;Lucida Sans Typewriter&quot;">--&nbsp;</span=
></span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span class=3D"apple-style-span"><span style=3D"font=
-size:12.0pt;font-family:&quot;Lucida Sans Typewriter&quot;">Colin Perkins<=
/span></span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span class=3D"apple-style-span"><span style=3D"font=
-size:12.0pt;font-family:&quot;Lucida Sans Typewriter&quot;"><a href=3D"htt=
p://csperkins.org/">http://csperkins.org/</a></span></span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span class=3D"apple-style-span"><span style=3D"font=
-size:12.0pt;font-family:&quot;Lucida Sans Typewriter&quot;">&nbsp;</span><=
/span><o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Times New Roman&quo=
t;,&quot;serif&quot;">&nbsp;</span><o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB">&nbsp;</s=
pan><o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB"><o:p>&nbs=
p;</o:p></span></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span class=3D"apple-=
style-span"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span class=3D"apple-style-span"><span style=3D"font=
-size:12.0pt;font-family:&quot;Times New Roman&quot;,&quot;serif&quot;;mso-=
fareast-language:EN-GB">--&nbsp;<o:p></o:p></span></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span class=3D"apple-style-span"><span style=3D"font=
-size:12.0pt;font-family:&quot;Times New Roman&quot;,&quot;serif&quot;;mso-=
fareast-language:EN-GB">Colin Perkins<o:p></o:p></span></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span class=3D"apple-style-span"><span style=3D"font=
-size:12.0pt;font-family:&quot;Times New Roman&quot;,&quot;serif&quot;;mso-=
fareast-language:EN-GB"><a href=3D"http://csperkins.org/">http://csperkins.=
org/</a><o:p></o:p></span></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span class=3D"apple-style-span"><span style=3D"font=
-size:12.0pt;font-family:&quot;Times New Roman&quot;,&quot;serif&quot;;mso-=
fareast-language:EN-GB"><o:p>&nbsp;</o:p></span></span></p>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB"><o:p>&nbs=
p;</o:p></span></p>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B1D1C5CCEESESSMB209erics_--


From nobody Mon Mar  3 02:58:21 2014
Return-Path: <csp@csperkins.org>
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 BE5D91A0EEA for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 02:58:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001] autolearn=ham
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 Ak-nrAdmZm56 for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 02:58:13 -0800 (PST)
Received: from haggis.mythic-beasts.com (haggis.mythic-beasts.com [IPv6:2a00:1098:0:86:1000:0:2:1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E06E1A0D87 for <mmusic@ietf.org>; Mon,  3 Mar 2014 02:58:11 -0800 (PST)
Received: from [31.133.156.67] (port=59221 helo=dhcp-9c43.meeting.ietf.org) by haggis.mythic-beasts.com with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from <csp@csperkins.org>) id 1WKQZS-0001Vy-Eo; Mon, 03 Mar 2014 10:58:07 +0000
Content-Type: multipart/alternative; boundary="Apple-Mail=_5853D7D7-A45D-4796-B84E-E8FC16F878E7"
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D1C5CCE@ESESSMB209.ericsson.se>
Date: Mon, 3 Mar 2014 10:58:05 +0000
Message-Id: <FF73D8EC-D4EB-4E53-8D05-63D4624F4B01@csperkins.org>
References: <7594FB04B1934943A5C02806D1A2204B1D1C368D@ESESSMB209.ericsson.se> <7A9A37FB-196F-4F79-805B-95CE9B67C344@csperkins.org> <7594FB04B1934943A5C02806D1A2204B1D1C5A25@ESESSMB209.ericsson.se> <97FFA3D1-8159-43B8-BD02-02BF420D4464@csperkins.org> <7594FB04B1934943A5C02806D1A2204B1D1C5BBF@ESESSMB209.ericsson.se> <D1A5B4EB-45E0-4BFA-BB93-96119F1B8152@csperkins.org> <7594FB04B1934943A5C02806D1A2204B1D1C5CCE@ESESSMB209.ericsson.se>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.1874)
X-BlackCat-Spam-Score: -28
X-Mythic-Debug: Threshold =  On = 
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/YZbkS4Rw07vEUlFN4fZMruxWlIM
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for allowing usage of the same PT value within multiple m- lines?
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 10:58:17 -0000

--Apple-Mail=_5853D7D7-A45D-4796-B84E-E8FC16F878E7
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Christer,

The same way you separate every other stream: SSRC to identify the media =
source, then direct to the right decoder path based on the PT mapping =
table.=20

Colin



On 3 Mar 2014, at 10:48, Christer Holmberg =
<christer.holmberg@ericsson.com> wrote:

> Hi Colin,
> =20
> Within an RTP session, if you receive two media streams, both using =
the same PT value (let=92s assume they use the same codec =
configuration), how will you separate the received media packets?
> =20
> Regards,
> =20
> Christer
> =20
> From: Colin Perkins [mailto:csp@csperkins.org]=20
> Sent: 03 March 2014 12:36
> To: Christer Holmberg
> Cc: mmusic@ietf.org
> Subject: Re: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for =
allowing usage of the same PT value within multiple m- lines?
> =20
> On 3 Mar 2014, at 10:26, Christer Holmberg =
<christer.holmberg@ericsson.com> wrote:
> Hi,
> =20
> >I did suggest a definition of =93codec configuration=94 in my =
message. If that=92s not acceptable, then I >suggest forbidding payload =
number reuse across m=3D lines.
> =20
> I was also told off-line that, in order to distinguish multiple media =
using the same PT value, the SSRC values that are going to be used needs =
to be signalled.
> =20
> I don=92t think the method works with RTP. The payload type number =
space is per RTP session, not per SSRC.
> =20
> Colin
> =20
> =20
>=20
>=20
>=20
> However, when the initial offer is sent, the offerer does not know =
what the answerer supports.
> =20
> Regards,
> =20
> Christer
> =20
> =20
> =20
> =20
> On 3 Mar 2014, at 10:08, Christer Holmberg =
<christer.holmberg@ericsson.com> wrote:
> Hi Colin,
> =20
> We tried to define =93codec configuration=94, but we never got text =
that people could agree to.
> =20
> Personally I don=92t have any strong opinion which way we go =
(personally I am also ok forbidding re-usage of the same PT value). I =
just want to close the issue, and not once again =93take it to the =
list=94.
> =20
> Regards,
> =20
> Christer
> =20
> From: Colin Perkins [mailto:csp@csperkins.org]=20
> Sent: 03 March 2014 11:34
> To: Christer Holmberg
> Cc: mmusic@ietf.org
> Subject: Re: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for =
allowing usage of the same PT value within multiple m- lines?
> =20
> Christer,
> =20
> The bundled m=3D lines form a single RTP session. That means that they =
share a single RTP payload number space. The rule therefore has to be =
that you can only reuse the payload type across bundled m=3D lines if it =
refers to the exact same configuration of the exact same codec in all =
cases, where =93exact same configuration=94 means that the a=3Dfmtp: =
line and all other SDP attributes that configure the codec and =
packetisation of the media are identical.
> =20
> If that=92s not specific enough, then MUST NOT reuse payload types =
across m=3D lines in a bundled group is the safe choice. I believe your =
propose that it=92s okay if you can handle the media is too vague, and =
will cause us problems down the line.
> =20
> Colin
> =20
> =20
> =20
> =20
> On 2 Mar 2014, at 08:44, Christer Holmberg =
<christer.holmberg@ericsson.com> wrote:
> Hi,
> =20
> One of the open issues we have in BUNDLE, is when it is allowed to use =
the same PT value within multiple m- lines.
> =20
> We tried to come up with different criteria, including a =93codec =
configuration=94 concept, but we never managed to agree on something.
> =20
> So, in London, I intend to suggest that we simply say: if you offer =
the same PT value within multiple m- line, make sure you can handle the =
associated media when it arrives =96 period (keep in mind that you =
always indicate what you want to RECEIVE =96 the remote peer can still =
ask you to SEND using different PT values).
> =20
> If you don=92t like this, please provide an alternative solution, =
because I want to close this issue in London. There is no idea to keep =
=93taking the issue back to the list=94. We=92ve done that for a few =
meetings already.
> =20
> Regards,
> =20
> Christer
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
> =20
> =20
>=20
> --=20
> Colin Perkins
> http://csperkins.org/
> =20
> =20
> =20
> =20
> =20
>=20
> --=20
> Colin Perkins
> http://csperkins.org/
> =20
> =20
> =20
> =20
> =20
>=20
> --=20
> Colin Perkins
> http://csperkins.org/
> =20
> =20
> =20



--=20
Colin Perkins
http://csperkins.org/




--Apple-Mail=_5853D7D7-A45D-4796-B84E-E8FC16F878E7
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;">Christer,<div><br></div><div>The same way you =
separate every other stream: SSRC to identify the media source, then =
direct to the right decoder path based on the PT mapping =
table.&nbsp;</div><div><br></div><div>Colin</div><div><br></div><div><br><=
/div><div><br><div><div><div>On 3 Mar 2014, at 10:48, Christer Holmberg =
&lt;<a =
href=3D"mailto:christer.holmberg@ericsson.com">christer.holmberg@ericsson.=
com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite">

<meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered =
medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"Lucida Sans Typewriter";}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.apple-style-span
	{mso-style-name:apple-style-span;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle21
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->

<div lang=3D"EN-GB" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1"><p class=3D"MsoNormal"><span =
style=3D"color:#1F497D">Hi Colin,<o:p></o:p></span></p><p =
class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span></p><p =
class=3D"MsoNormal"><span style=3D"color:#1F497D">Within an RTP session, =
if you receive two media streams, both using the same PT value (let=92s =
assume they use the same codec configuration), how will you separate the =
received media packets?<o:p></o:p></span></p><p class=3D"MsoNormal"><span =
style=3D"color:#1F497D">&nbsp;</span></p><p class=3D"MsoNormal"><span =
style=3D"color:#1F497D">Regards,<o:p></o:p></span></p><p =
class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span></p><p =
class=3D"MsoNormal"><span =
style=3D"color:#1F497D">Christer<o:p></o:p></span></p><p =
class=3D"MsoNormal"><a name=3D"_MailEndCompose"><span =
style=3D"color:#1F497D">&nbsp;</span></a></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt =
0cm 0cm 0cm"><p class=3D"MsoNormal"><b><span lang=3D"EN-US" =
style=3D"mso-fareast-language:EN-GB">From:</span></b><span lang=3D"EN-US" =
style=3D"mso-fareast-language:EN-GB"> Colin Perkins [<a =
href=3D"mailto:csp@csperkins.org">mailto:csp@csperkins.org</a>]
<br>
<b>Sent:</b> 03 March 2014 12:36<br>
<b>To:</b> Christer Holmberg<br>
<b>Cc:</b> <a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
<b>Subject:</b> Re: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria =
for allowing usage of the same PT value within multiple m- =
lines?<o:p></o:p></span></p>
</div>
</div><p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p><p =
class=3D"MsoNormal">On 3 Mar 2014, at 10:26, Christer Holmberg &lt;<a =
href=3D"mailto:christer.holmberg@ericsson.com">christer.holmberg@ericsson.=
com</a>&gt; wrote:<span =
style=3D"font-size:12.0pt;mso-fareast-language:EN-GB"><o:p></o:p></span></=
p>
<div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div><p class=3D"MsoNormal"><span =
style=3D"color:#1F497D">Hi,</span><o:p></o:p></p>
<div><p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div><p class=3D"MsoNormal"><span style=3D"color:#1F497D">&gt;</span>I =
did suggest a definition of =93codec configuration=94 in my message. If =
that=92s not acceptable, then I
<span style=3D"color:#1F497D">&gt;</span>suggest forbidding payload =
number reuse across m=3D lines.<o:p></o:p></p>
</div>
<div><p class=3D"MsoNormal"><span =
style=3D"color:#1F497D">&nbsp;</span><o:p></o:p></p><p =
class=3D"MsoNormal"><span style=3D"color:#1F497D">I was also told =
off-line that, in order to distinguish multiple media using the same PT =
value, the SSRC values that are going to be used needs to be =
signalled.</span><o:p></o:p></p>
</div>
</div>
</blockquote>
<div><p class=3D"MsoNormal"><span =
style=3D"font-size:12.0pt;font-family:&quot;Times New =
Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB">&nbsp;</span></p=
>
</div><p class=3D"MsoNormal"><span =
style=3D"font-size:12.0pt;font-family:&quot;Times New =
Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB">I don=92t =
think the method works with RTP. The payload type number space is per =
RTP session, not per SSRC.<o:p></o:p></span></p>
</div>
<div><p class=3D"MsoNormal"><span =
style=3D"font-size:12.0pt;font-family:&quot;Times New =
Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB">&nbsp;</span></p=
>
</div>
<div><p class=3D"MsoNormal"><span =
style=3D"font-size:12.0pt;font-family:&quot;Times New =
Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB">Colin<o:p></o:p>=
</span></p>
</div>
<div><p class=3D"MsoNormal"><span =
style=3D"font-size:12.0pt;font-family:&quot;Times New =
Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB">&nbsp;</span></p=
>
</div>
<div><p class=3D"MsoNormal"><span =
style=3D"font-size:12.0pt;font-family:&quot;Times New =
Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB">&nbsp;</span></p=
>
</div>
<div><p class=3D"MsoNormal"><span =
style=3D"font-size:12.0pt;font-family:&quot;Times New =
Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB"><br>
<br>
<br>
<o:p></o:p></span></p>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div><p class=3D"MsoNormal"><span style=3D"color:#1F497D">However, when =
the initial offer is sent, the offerer does not know what the answerer =
supports.</span><o:p></o:p></p><p class=3D"MsoNormal"><span =
style=3D"color:#1F497D">&nbsp;</span><o:p></o:p></p><p =
class=3D"MsoNormal"><span =
style=3D"color:#1F497D">Regards,</span><o:p></o:p></p><p =
class=3D"MsoNormal"><span =
style=3D"color:#1F497D">&nbsp;</span><o:p></o:p></p><p =
class=3D"MsoNormal"><span =
style=3D"color:#1F497D">Christer</span><o:p></o:p></p><p =
class=3D"MsoNormal"><span =
style=3D"color:#1F497D">&nbsp;</span><o:p></o:p></p>
</div>
<div><p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div><p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div><p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<div>
<div><p class=3D"MsoNormal">On 3 Mar 2014, at 10:08, Christer Holmberg =
&lt;<a =
href=3D"mailto:christer.holmberg@ericsson.com">christer.holmberg@ericsson.=
com</a>&gt; wrote:<o:p></o:p></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div><p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi =
Colin,</span><o:p></o:p></p><p class=3D"MsoNormal"><span =
style=3D"color:#1F497D">&nbsp;</span><o:p></o:p></p><p =
class=3D"MsoNormal"><span style=3D"color:#1F497D">We tried to define =
=93codec configuration=94, but we never got text that people could agree =
to.</span><o:p></o:p></p><p class=3D"MsoNormal"><span =
style=3D"color:#1F497D">&nbsp;</span><o:p></o:p></p><p =
class=3D"MsoNormal"><span style=3D"color:#1F497D">Personally I don=92t =
have any strong opinion which way we go (personally I am also ok =
forbidding re-usage of the same PT value). I just want to close the =
issue, and not once again =93take it to the =
list=94.</span><o:p></o:p></p><p class=3D"MsoNormal"><span =
style=3D"color:#1F497D">&nbsp;</span><o:p></o:p></p><p =
class=3D"MsoNormal"><span =
style=3D"color:#1F497D">Regards,</span><o:p></o:p></p><p =
class=3D"MsoNormal"><span =
style=3D"color:#1F497D">&nbsp;</span><o:p></o:p></p><p =
class=3D"MsoNormal"><span =
style=3D"color:#1F497D">Christer</span><o:p></o:p></p><p =
class=3D"MsoNormal"><span =
style=3D"color:#1F497D">&nbsp;</span><o:p></o:p></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt =
0cm 0cm 0cm"><p class=3D"MsoNormal"><b><span lang=3D"EN-US" =
style=3D"mso-fareast-language:EN-GB">From:</span></b><span lang=3D"EN-US" =
style=3D"mso-fareast-language:EN-GB"> Colin Perkins [<a =
href=3D"mailto:csp@csperkins.org">mailto:csp@csperkins.org</a>]
<br>
<b>Sent:</b> 03 March 2014 11:34<br>
<b>To:</b> Christer Holmberg<br>
<b>Cc:</b> <a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
<b>Subject:</b> Re: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria =
for allowing usage of the same PT value within multiple m- =
lines?</span><o:p></o:p></p>
</div>
</div><p class=3D"MsoNormal">&nbsp;<o:p></o:p></p><p =
class=3D"MsoNormal">Christer,<o:p></o:p></p>
<div><p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div><p class=3D"MsoNormal">The bundled m=3D lines form a single RTP =
session. That means that they share a single RTP payload number space. =
The rule therefore has to be that you can only reuse the payload type =
across bundled m=3D lines if it refers to the exact same configuration
 of the exact same codec in all cases, where =93exact same =
configuration=94 means that the a=3Dfmtp: line and all other SDP =
attributes that configure the codec and packetisation of the media are =
identical.<o:p></o:p></p>
</div>
<div><p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div><p class=3D"MsoNormal">If that=92s not specific enough, then MUST =
NOT reuse payload types across m=3D lines in a bundled group is the safe =
choice. I believe your propose that it=92s okay if you can handle the =
media is too vague, and will cause us problems down the
 line.<o:p></o:p></p>
</div>
<div><p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div><p class=3D"MsoNormal">Colin<o:p></o:p></p>
</div>
<div><p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div><p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div><p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div><p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<div>
<div><p class=3D"MsoNormal">On 2 Mar 2014, at 08:44, Christer Holmberg =
&lt;<a =
href=3D"mailto:christer.holmberg@ericsson.com">christer.holmberg@ericsson.=
com</a>&gt; wrote:<o:p></o:p></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div><p class=3D"MsoNormal">Hi,<o:p></o:p></p><p =
class=3D"MsoNormal">&nbsp;<o:p></o:p></p><p class=3D"MsoNormal">One of =
the open issues we have in BUNDLE, is when it is allowed to use the same =
PT value within multiple m- lines.<o:p></o:p></p><p =
class=3D"MsoNormal">&nbsp;<o:p></o:p></p><p class=3D"MsoNormal">We tried =
to come up with different criteria, including a =93codec configuration=94 =
concept, but we never managed to agree on something.<o:p></o:p></p><p =
class=3D"MsoNormal">&nbsp;<o:p></o:p></p><p class=3D"MsoNormal">So, in =
London, I intend to suggest that we simply say: if you offer the same PT =
value within multiple m- line, make sure you can handle the associated =
media when it arrives =96 period (keep in mind that you always indicate =
what you want to
 RECEIVE =96 the remote peer can still ask you to SEND using different =
PT values).<o:p></o:p></p><p class=3D"MsoNormal">&nbsp;<o:p></o:p></p><p =
class=3D"MsoNormal">If you don=92t like this, please provide an =
alternative solution, because I want to close this issue in London. =
There is no idea to keep =93taking the issue back to the list=94. We=92ve =
done that for a few meetings already.<o:p></o:p></p><p =
class=3D"MsoNormal">&nbsp;<o:p></o:p></p><p =
class=3D"MsoNormal">Regards,<o:p></o:p></p><p =
class=3D"MsoNormal">&nbsp;<o:p></o:p></p><p =
class=3D"MsoNormal">Christer<o:p></o:p></p>
</div><p class=3D"MsoNormal"><span =
style=3D"font-size:12.0pt;font-family:&quot;Times New =
Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB">________________=
_______________________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
<a =
href=3D"https://www.ietf.org/mailman/listinfo/mmusic">https://www.ietf.org=
/mailman/listinfo/mmusic</a></span><o:p></o:p></p>
</blockquote>
</div><p class=3D"MsoNormal"><span =
style=3D"font-size:12.0pt;font-family:&quot;Times New =
Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB">&nbsp;</span><o:=
p></o:p></p>
<div>
<div><p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span =
style=3D"font-size:12.0pt;font-family:&quot;Lucida Sans =
Typewriter&quot;">&nbsp;</span><o:p></o:p></p>
</div>
<div><p class=3D"MsoNormal"><span =
style=3D"font-size:12.0pt;font-family:&quot;Lucida Sans =
Typewriter&quot;">--&nbsp;</span><o:p></o:p></p>
</div>
<div><p class=3D"MsoNormal"><span =
style=3D"font-size:12.0pt;font-family:&quot;Lucida Sans =
Typewriter&quot;">Colin Perkins</span><o:p></o:p></p>
</div>
<div><p class=3D"MsoNormal"><span =
style=3D"font-size:12.0pt;font-family:&quot;Lucida Sans =
Typewriter&quot;"><a =
href=3D"http://csperkins.org/">http://csperkins.org/</a></span><o:p></o:p>=
</p>
</div>
<div><p class=3D"MsoNormal"><span =
style=3D"font-size:12.0pt;font-family:&quot;Lucida Sans =
Typewriter&quot;">&nbsp;</span><o:p></o:p></p>
</div><p class=3D"MsoNormal"><span =
style=3D"font-size:12.0pt;font-family:&quot;Times New =
Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB">&nbsp;</span><o:=
p></o:p></p>
</div><p class=3D"MsoNormal"><span =
style=3D"font-size:12.0pt;font-family:&quot;Times New =
Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB">&nbsp;</span><o:=
p></o:p></p>
</div>
</div>
</blockquote>
</div><p class=3D"MsoNormal"><span =
style=3D"font-size:12.0pt;font-family:&quot;Times New =
Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB">&nbsp;</span><o:=
p></o:p></p>
<div>
<div><p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span =
class=3D"apple-style-span"><span style=3D"font-family:&quot;Lucida Sans =
Typewriter&quot;">&nbsp;</span></span><o:p></o:p></p>
</div>
<div><p class=3D"MsoNormal"><span class=3D"apple-style-span"><span =
style=3D"font-size:12.0pt;font-family:&quot;Lucida Sans =
Typewriter&quot;">--&nbsp;</span></span><o:p></o:p></p>
</div>
<div><p class=3D"MsoNormal"><span class=3D"apple-style-span"><span =
style=3D"font-size:12.0pt;font-family:&quot;Lucida Sans =
Typewriter&quot;">Colin Perkins</span></span><o:p></o:p></p>
</div>
<div><p class=3D"MsoNormal"><span class=3D"apple-style-span"><span =
style=3D"font-size:12.0pt;font-family:&quot;Lucida Sans =
Typewriter&quot;"><a =
href=3D"http://csperkins.org/">http://csperkins.org/</a></span></span><o:p=
></o:p></p>
</div>
<div><p class=3D"MsoNormal"><span class=3D"apple-style-span"><span =
style=3D"font-size:12.0pt;font-family:&quot;Lucida Sans =
Typewriter&quot;">&nbsp;</span></span><o:p></o:p></p>
</div><p class=3D"MsoNormal"><span style=3D"font-family:&quot;Times New =
Roman&quot;,&quot;serif&quot;">&nbsp;</span><o:p></o:p></p>
</div><p class=3D"MsoNormal"><span =
style=3D"font-size:12.0pt;font-family:&quot;Times New =
Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB">&nbsp;</span><o:=
p></o:p></p>
</div>
</div>
</blockquote>
</div><p class=3D"MsoNormal"><span =
style=3D"font-size:12.0pt;font-family:&quot;Times New =
Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB">&nbsp;</span></p=
>
<div>
<div><p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span =
class=3D"apple-style-span">&nbsp;</span></p>
</div>
<div><p class=3D"MsoNormal"><span class=3D"apple-style-span"><span =
style=3D"font-size:12.0pt;font-family:&quot;Times New =
Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB">--&nbsp;<o:p></o=
:p></span></span></p>
</div>
<div><p class=3D"MsoNormal"><span class=3D"apple-style-span"><span =
style=3D"font-size:12.0pt;font-family:&quot;Times New =
Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB">Colin =
Perkins<o:p></o:p></span></span></p>
</div>
<div><p class=3D"MsoNormal"><span class=3D"apple-style-span"><span =
style=3D"font-size:12.0pt;font-family:&quot;Times New =
Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB"><a =
href=3D"http://csperkins.org/">http://csperkins.org/</a><o:p></o:p></span>=
</span></p>
</div>
<div><p class=3D"MsoNormal"><span class=3D"apple-style-span"><span =
style=3D"font-size:12.0pt;font-family:&quot;Times New =
Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB">&nbsp;</span></s=
pan></p>
</div><p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div><p class=3D"MsoNormal"><span =
style=3D"font-size:12.0pt;font-family:&quot;Times New =
Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB">&nbsp;</span></p=
>
</div>
</div>

</blockquote></div><br><div apple-content-edited=3D"true">
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
color: rgb(0, 0, 0); font-family: 'Lucida Sans Typewriter'; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-align: -webkit-auto; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px;  "><div><br =
class=3D"Apple-interchange-newline"><br =
class=3D"khtml-block-placeholder"></div><div>--&nbsp;</div><div></div><div=
>Colin Perkins</div><div><a =
href=3D"http://csperkins.org/">http://csperkins.org/</a></div><div><br></d=
iv></span><br class=3D"Apple-interchange-newline">

</div>
<br></div></div></body></html>=

--Apple-Mail=_5853D7D7-A45D-4796-B84E-E8FC16F878E7--


From nobody Mon Mar  3 03:00:26 2014
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 EB5361A0DFA for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 03:00:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.239
X-Spam-Level: 
X-Spam-Status: No, score=-1.239 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, HOST_MISMATCH_NET=0.311, HTML_MESSAGE=0.001, 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 Eomxo4KKhfVm for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 03:00:18 -0800 (PST)
Received: from sessmg20.mgmt.ericsson.se (sessmg20.ericsson.net [193.180.251.50]) by ietfa.amsl.com (Postfix) with ESMTP id 162E11A0903 for <mmusic@ietf.org>; Mon,  3 Mar 2014 03:00:16 -0800 (PST)
X-AuditID: c1b4fb32-b7f4c8e0000012f5-e6-531460bd00af
Received: from ESESSHC022.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg20.mgmt.ericsson.se (Symantec Mail Security) with SMTP id 1B.5F.04853.DB064135; Mon,  3 Mar 2014 12:00:13 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.216]) by ESESSHC022.ericsson.se ([153.88.183.84]) with mapi id 14.02.0387.000; Mon, 3 Mar 2014 12:00:12 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Colin Perkins <csp@csperkins.org>
Thread-Topic: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for allowing usage of the same PT value within multiple m- lines?
Thread-Index: Ac818yLx23ucJzjaSbubJw5GhjG+ygAyCDEAAAM6QvD///NSAP//7o6ggAAV3AD//+xLsIAAGcSA///u21A=
Date: Mon, 3 Mar 2014 11:00:12 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D1C5DDF@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D1C368D@ESESSMB209.ericsson.se> <7A9A37FB-196F-4F79-805B-95CE9B67C344@csperkins.org> <7594FB04B1934943A5C02806D1A2204B1D1C5A25@ESESSMB209.ericsson.se> <97FFA3D1-8159-43B8-BD02-02BF420D4464@csperkins.org> <7594FB04B1934943A5C02806D1A2204B1D1C5BBF@ESESSMB209.ericsson.se> <D1A5B4EB-45E0-4BFA-BB93-96119F1B8152@csperkins.org> <7594FB04B1934943A5C02806D1A2204B1D1C5CCE@ESESSMB209.ericsson.se> <FF73D8EC-D4EB-4E53-8D05-63D4624F4B01@csperkins.org>
In-Reply-To: <FF73D8EC-D4EB-4E53-8D05-63D4624F4B01@csperkins.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.154]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1D1C5DDFESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrJLMWRmVeSWpSXmKPExsUyM+Jvje7eBJFgg4PzpS2WvzzBaDF1+WMW ByaPaffvs3ksWfKTKYApissmJTUnsyy1SN8ugSvj9IH5LAWbTzFWPOpdxtjAeHsTYxcjB4eE gInEoq32XYycQKaYxIV769m6GLk4hAROMEpMvXGICcJZzCjRfPAtC0gDm4CFRPc/bZAGEQFV iR3H/4HNYRZQl7i6OAikXFighVGi9cwBdhBHRKCVUWJK/xEmiIYkiSV9u5lBbBYBFYlz72aw gdi8Ar4S8yfOYoFY9pVZ4smJzYwgCU4BR4nWz3NZQWxGoPO+n1oDNohZQFzi1pP5TBBnC0gs 2XOeGcIWlXj5+B8rhK0ksej2Z6j6fIkvtzewQCwTlDg58wnLBEbRWUhGzUJSNgtJGURcR2LB 7k9sELa2xLKFr5lh7DMHHjMhiy9gZF/FKFmcWlycm25koJebnluil1qUmVxcnJ+nV5y6iREY fQe3/DbawXhyj/0hRmkOFiVx3uusNUFCAumJJanZqakFqUXxRaU5qcWHGJk4OKUaGEMT9//Q erz8lY3q+SObF87PDE55t/bixzxtsZTzy7dYs1ftWbixU/+8p9glbsNGIdfb1578/lc0Ifbx 2xvR78qW8i44IX95yybfq07TF/PJ2Hc4LA//sSrj0IvoSom5qZqiLj3eErOOFc3zVVFPatx1 /9HlV+uWn/E847tD2n1e/cO7mkwv50grsRRnJBpqMRcVJwIA9UuVqowCAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/gWJbC1IuOhRWyyzv9lRAM2OvPuY
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for allowing usage of the same PT value within multiple m- lines?
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 11:00:22 -0000

--_000_7594FB04B1934943A5C02806D1A2204B1D1C5DDFESESSMB209erics_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

>The same way you separate every other stream: SSRC to identify the media s=
ource, then direct to >the right decoder path based on the PT mapping table=
.

Yes, but then you need to know which SSRC(s) are going to be used for each =
media stream.

Regards,

Christer




On 3 Mar 2014, at 10:48, Christer Holmberg <christer.holmberg@ericsson.com<=
mailto:christer.holmberg@ericsson.com>> wrote:


Hi Colin,

Within an RTP session, if you receive two media streams, both using the sam=
e PT value (let's assume they use the same codec configuration), how will y=
ou separate the received media packets?

Regards,

Christer

From: Colin Perkins [mailto:csp@csperkins.org]
Sent: 03 March 2014 12:36
To: Christer Holmberg
Cc: mmusic@ietf.org<mailto:mmusic@ietf.org>
Subject: Re: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for allowi=
ng usage of the same PT value within multiple m- lines?

On 3 Mar 2014, at 10:26, Christer Holmberg <christer.holmberg@ericsson.com<=
mailto:christer.holmberg@ericsson.com>> wrote:
Hi,

>I did suggest a definition of "codec configuration" in my message. If that=
's not acceptable, then I >suggest forbidding payload number reuse across m=
=3D lines.

I was also told off-line that, in order to distinguish multiple media using=
 the same PT value, the SSRC values that are going to be used needs to be s=
ignalled.

I don't think the method works with RTP. The payload type number space is p=
er RTP session, not per SSRC.

Colin






However, when the initial offer is sent, the offerer does not know what the=
 answerer supports.

Regards,

Christer




On 3 Mar 2014, at 10:08, Christer Holmberg <christer.holmberg@ericsson.com<=
mailto:christer.holmberg@ericsson.com>> wrote:
Hi Colin,

We tried to define "codec configuration", but we never got text that people=
 could agree to.

Personally I don't have any strong opinion which way we go (personally I am=
 also ok forbidding re-usage of the same PT value). I just want to close th=
e issue, and not once again "take it to the list".

Regards,

Christer

From: Colin Perkins [mailto:csp@csperkins.org]
Sent: 03 March 2014 11:34
To: Christer Holmberg
Cc: mmusic@ietf.org<mailto:mmusic@ietf.org>
Subject: Re: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for allowi=
ng usage of the same PT value within multiple m- lines?

Christer,

The bundled m=3D lines form a single RTP session. That means that they shar=
e a single RTP payload number space. The rule therefore has to be that you =
can only reuse the payload type across bundled m=3D lines if it refers to t=
he exact same configuration of the exact same codec in all cases, where "ex=
act same configuration" means that the a=3Dfmtp: line and all other SDP att=
ributes that configure the codec and packetisation of the media are identic=
al.

If that's not specific enough, then MUST NOT reuse payload types across m=
=3D lines in a bundled group is the safe choice. I believe your propose tha=
t it's okay if you can handle the media is too vague, and will cause us pro=
blems down the line.

Colin




On 2 Mar 2014, at 08:44, Christer Holmberg <christer.holmberg@ericsson.com<=
mailto:christer.holmberg@ericsson.com>> wrote:
Hi,

One of the open issues we have in BUNDLE, is when it is allowed to use the =
same PT value within multiple m- lines.

We tried to come up with different criteria, including a "codec configurati=
on" concept, but we never managed to agree on something.

So, in London, I intend to suggest that we simply say: if you offer the sam=
e PT value within multiple m- line, make sure you can handle the associated=
 media when it arrives - period (keep in mind that you always indicate what=
 you want to RECEIVE - the remote peer can still ask you to SEND using diff=
erent PT values).

If you don't like this, please provide an alternative solution, because I w=
ant to close this issue in London. There is no idea to keep "taking the iss=
ue back to the list". We've done that for a few meetings already.

Regards,

Christer
_______________________________________________
mmusic mailing list
mmusic@ietf.org<mailto:mmusic@ietf.org>
https://www.ietf.org/mailman/listinfo/mmusic


--
Colin Perkins
http://csperkins.org/





--
Colin Perkins
http://csperkins.org/





--
Colin Perkins
http://csperkins.org/





--
Colin Perkins
http://csperkins.org/




--_000_7594FB04B1934943A5C02806D1A2204B1D1C5DDFESESSMB209erics_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"Lucida Sans Typewriter";}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.apple-style-span
	{mso-style-name:apple-style-span;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle22
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-GB" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi,<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&gt;</span>The same wa=
y you separate every other stream: SSRC to identify the media source, then =
direct to
<span style=3D"color:#1F497D">&gt;</span>the right decoder path based on th=
e PT mapping table.&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Yes, but then you need=
 to know which SSRC(s) are going to be used for each media stream.<o:p></o:=
p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Regards,<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Christer<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<div>
<p class=3D"MsoNormal">On 3 Mar 2014, at 10:48, Christer Holmberg &lt;<a hr=
ef=3D"mailto:christer.holmberg@ericsson.com">christer.holmberg@ericsson.com=
</a>&gt; wrote:<o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><br>
<br>
<o:p></o:p></p>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi Colin,</span><o:p><=
/o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><o:p></o:=
p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Within an RTP session,=
 if you receive two media streams, both using the same PT value (let&#8217;=
s assume they use the same codec configuration), how will you separate the =
received media packets?</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><o:p></o:=
p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Regards,</span><o:p></=
o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><o:p></o:=
p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Christer</span><o:p></=
o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><o:p></o:=
p></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"mso-fareast-languag=
e:EN-GB">From:</span></b><span lang=3D"EN-US" style=3D"mso-fareast-language=
:EN-GB"> Colin Perkins [<a href=3D"mailto:csp@csperkins.org">mailto:csp@csp=
erkins.org</a>]
<br>
<b>Sent:</b> 03 March 2014 12:36<br>
<b>To:</b> Christer Holmberg<br>
<b>Cc:</b> <a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
<b>Subject:</b> Re: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for=
 allowing usage of the same PT value within multiple m- lines?</span><o:p><=
/o:p></p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal">On 3 Mar 2014, at 10:26, Christer Holmberg &lt;<a hr=
ef=3D"mailto:christer.holmberg@ericsson.com">christer.holmberg@ericsson.com=
</a>&gt; wrote:<o:p></o:p></p>
<div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi,</span><o:p></o:p><=
/p>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&gt;</span>I did sugge=
st a definition of &#8220;codec configuration&#8221; in my message. If that=
&#8217;s not acceptable, then I
<span style=3D"color:#1F497D">&gt;</span>suggest forbidding payload number =
reuse across m=3D lines.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><o:p></o:=
p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">I was also told off-li=
ne that, in order to distinguish multiple media using the same PT value, th=
e SSRC values that are going to be used needs to be signalled.</span><o:p><=
/o:p></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB">&nbsp;</s=
pan><o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB">I don&#82=
17;t think the method works with RTP. The payload type number space is per =
RTP session, not per SSRC.</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB">&nbsp;</s=
pan><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB">Colin</sp=
an><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB">&nbsp;</s=
pan><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB">&nbsp;</s=
pan><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB"><br>
<br>
<br>
<br>
</span><o:p></o:p></p>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">However, when the init=
ial offer is sent, the offerer does not know what the answerer supports.</s=
pan><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><o:p></o:=
p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Regards,</span><o:p></=
o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><o:p></o:=
p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Christer</span><o:p></=
o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><o:p></o:=
p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal">On 3 Mar 2014, at 10:08, Christer Holmberg &lt;<a hr=
ef=3D"mailto:christer.holmberg@ericsson.com">christer.holmberg@ericsson.com=
</a>&gt; wrote:<o:p></o:p></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi Colin,</span><o:p><=
/o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><o:p></o:=
p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">We tried to define &#8=
220;codec configuration&#8221;, but we never got text that people could agr=
ee to.</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><o:p></o:=
p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Personally I don&#8217=
;t have any strong opinion which way we go (personally I am also ok forbidd=
ing re-usage of the same PT value). I just want to close the issue, and not=
 once again &#8220;take it to the list&#8221;.</span><o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><o:p></o:=
p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Regards,</span><o:p></=
o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><o:p></o:=
p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Christer</span><o:p></=
o:p></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span><o:p></o:=
p></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"mso-fareast-languag=
e:EN-GB">From:</span></b><span lang=3D"EN-US" style=3D"mso-fareast-language=
:EN-GB"> Colin Perkins [<a href=3D"mailto:csp@csperkins.org">mailto:csp@csp=
erkins.org</a>]
<br>
<b>Sent:</b> 03 March 2014 11:34<br>
<b>To:</b> Christer Holmberg<br>
<b>Cc:</b> <a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
<b>Subject:</b> Re: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for=
 allowing usage of the same PT value within multiple m- lines?</span><o:p><=
/o:p></p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal">Christer,<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">The bundled m=3D lines form a single RTP session. Th=
at means that they share a single RTP payload number space. The rule theref=
ore has to be that you can only reuse the payload type across bundled m=3D =
lines if it refers to the exact same configuration
 of the exact same codec in all cases, where &#8220;exact same configuratio=
n&#8221; means that the a=3Dfmtp: line and all other SDP attributes that co=
nfigure the codec and packetisation of the media are identical.<o:p></o:p><=
/p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">If that&#8217;s not specific enough, then MUST NOT r=
euse payload types across m=3D lines in a bundled group is the safe choice.=
 I believe your propose that it&#8217;s okay if you can handle the media is=
 too vague, and will cause us problems down the
 line.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Colin<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal">On 2 Mar 2014, at 08:44, Christer Holmberg &lt;<a hr=
ef=3D"mailto:christer.holmberg@ericsson.com">christer.holmberg@ericsson.com=
</a>&gt; wrote:<o:p></o:p></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class=3D"MsoNormal">Hi,<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal">One of the open issues we have in BUNDLE, is when it=
 is allowed to use the same PT value within multiple m- lines.<o:p></o:p></=
p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal">We tried to come up with different criteria, includi=
ng a &#8220;codec configuration&#8221; concept, but we never managed to agr=
ee on something.<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal">So, in London, I intend to suggest that we simply sa=
y: if you offer the same PT value within multiple m- line, make sure you ca=
n handle the associated media when it arrives &#8211; period (keep in mind =
that you always indicate what you want to
 RECEIVE &#8211; the remote peer can still ask you to SEND using different =
PT values).<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal">If you don&#8217;t like this, please provide an alte=
rnative solution, because I want to close this issue in London. There is no=
 idea to keep &#8220;taking the issue back to the list&#8221;. We&#8217;ve =
done that for a few meetings already.<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal">Regards,<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal">Christer<o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB">_________=
______________________________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic">https://www.ietf.o=
rg/mailman/listinfo/mmusic</a></span><o:p></o:p></p>
</blockquote>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB">&nbsp;</s=
pan><o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-s=
ize:12.0pt;font-family:&quot;Lucida Sans Typewriter&quot;">&nbsp;</span><o:=
p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Lu=
cida Sans Typewriter&quot;">--&nbsp;</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Lu=
cida Sans Typewriter&quot;">Colin Perkins</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Lu=
cida Sans Typewriter&quot;"><a href=3D"http://csperkins.org/">http://csperk=
ins.org/</a></span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Lu=
cida Sans Typewriter&quot;">&nbsp;</span><o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB">&nbsp;</s=
pan><o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB">&nbsp;</s=
pan><o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB">&nbsp;</s=
pan><o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span class=3D"apple-=
style-span"><span style=3D"font-family:&quot;Lucida Sans Typewriter&quot;">=
&nbsp;</span></span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span class=3D"apple-style-span"><span style=3D"font=
-size:12.0pt;font-family:&quot;Lucida Sans Typewriter&quot;">--&nbsp;</span=
></span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span class=3D"apple-style-span"><span style=3D"font=
-size:12.0pt;font-family:&quot;Lucida Sans Typewriter&quot;">Colin Perkins<=
/span></span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span class=3D"apple-style-span"><span style=3D"font=
-size:12.0pt;font-family:&quot;Lucida Sans Typewriter&quot;"><a href=3D"htt=
p://csperkins.org/">http://csperkins.org/</a></span></span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span class=3D"apple-style-span"><span style=3D"font=
-size:12.0pt;font-family:&quot;Lucida Sans Typewriter&quot;">&nbsp;</span><=
/span><o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Times New Roman&quo=
t;,&quot;serif&quot;">&nbsp;</span><o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB">&nbsp;</s=
pan><o:p></o:p></p>
</div>
</div>
</blockquote>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB">&nbsp;</s=
pan><o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span class=3D"apple-=
style-span">&nbsp;</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span class=3D"apple-style-span"><span style=3D"font=
-size:12.0pt;font-family:&quot;Times New Roman&quot;,&quot;serif&quot;;mso-=
fareast-language:EN-GB">--&nbsp;</span></span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span class=3D"apple-style-span"><span style=3D"font=
-size:12.0pt;font-family:&quot;Times New Roman&quot;,&quot;serif&quot;;mso-=
fareast-language:EN-GB">Colin Perkins</span></span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span class=3D"apple-style-span"><span style=3D"font=
-size:12.0pt;font-family:&quot;Times New Roman&quot;,&quot;serif&quot;;mso-=
fareast-language:EN-GB"><a href=3D"http://csperkins.org/">http://csperkins.=
org/</a></span></span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span class=3D"apple-style-span"><span style=3D"font=
-size:12.0pt;font-family:&quot;Times New Roman&quot;,&quot;serif&quot;;mso-=
fareast-language:EN-GB">&nbsp;</span></span><o:p></o:p></p>
</div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB">&nbsp;</s=
pan><o:p></o:p></p>
</div>
</blockquote>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB"><o:p>&nbs=
p;</o:p></span></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span class=3D"apple-=
style-span"><span style=3D"font-family:&quot;Lucida Sans Typewriter&quot;;c=
olor:black"><o:p>&nbsp;</o:p></span></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span class=3D"apple-style-span"><span style=3D"font=
-size:12.0pt;font-family:&quot;Lucida Sans Typewriter&quot;;color:black;mso=
-fareast-language:EN-GB">--&nbsp;<o:p></o:p></span></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span class=3D"apple-style-span"><span style=3D"font=
-size:12.0pt;font-family:&quot;Lucida Sans Typewriter&quot;;color:black;mso=
-fareast-language:EN-GB">Colin Perkins<o:p></o:p></span></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span class=3D"apple-style-span"><span style=3D"font=
-size:12.0pt;font-family:&quot;Lucida Sans Typewriter&quot;;color:black;mso=
-fareast-language:EN-GB"><a href=3D"http://csperkins.org/">http://csperkins=
.org/</a><o:p></o:p></span></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span class=3D"apple-style-span"><span style=3D"font=
-size:12.0pt;font-family:&quot;Lucida Sans Typewriter&quot;;color:black;mso=
-fareast-language:EN-GB"><o:p>&nbsp;</o:p></span></span></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Times New Roman&quo=
t;,&quot;serif&quot;"><o:p>&nbsp;</o:p></span></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB"><o:p>&nbs=
p;</o:p></span></p>
</div>
</div>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B1D1C5DDFESESSMB209erics_--


From nobody Mon Mar  3 03:01:46 2014
Return-Path: <csp@csperkins.org>
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 D07191A0DFA for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 03:01:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001] autolearn=ham
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 i8JNtQtSa0YV for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 03:01:41 -0800 (PST)
Received: from haggis.mythic-beasts.com (haggis.mythic-beasts.com [IPv6:2a00:1098:0:86:1000:0:2:1]) by ietfa.amsl.com (Postfix) with ESMTP id 8EA3D1A0CB7 for <mmusic@ietf.org>; Mon,  3 Mar 2014 03:01:41 -0800 (PST)
Received: from [31.133.156.67] (port=59263 helo=dhcp-9c43.meeting.ietf.org) by haggis.mythic-beasts.com with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from <csp@csperkins.org>) id 1WKQcr-0003Dc-Gu; Mon, 03 Mar 2014 11:01:38 +0000
Content-Type: multipart/alternative; boundary="Apple-Mail=_EE46B561-E0BB-4885-B4A3-613FA9C84F88"
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D1C5DDF@ESESSMB209.ericsson.se>
Date: Mon, 3 Mar 2014 11:01:36 +0000
Message-Id: <331AFD56-7C29-4BB3-9B63-00D1E9317F9C@csperkins.org>
References: <7594FB04B1934943A5C02806D1A2204B1D1C368D@ESESSMB209.ericsson.se> <7A9A37FB-196F-4F79-805B-95CE9B67C344@csperkins.org> <7594FB04B1934943A5C02806D1A2204B1D1C5A25@ESESSMB209.ericsson.se> <97FFA3D1-8159-43B8-BD02-02BF420D4464@csperkins.org> <7594FB04B1934943A5C02806D1A2204B1D1C5BBF@ESESSMB209.ericsson.se> <D1A5B4EB-45E0-4BFA-BB93-96119F1B8152@csperkins.org> <7594FB04B1934943A5C02806D1A2204B1D1C5CCE@ESESSMB209.ericsson.se> <FF73D8EC-D4EB-4E53-8D05-63D4624F4B01@csperkins.org> <7594FB04B1934943A5C02806D1A2204B1D1C5DDF@ESESSMB209.ericsson.se>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.1874)
X-BlackCat-Spam-Score: -28
X-Mythic-Debug: Threshold =  On = 
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/UPTX0U9ff_2HvlDspuQL1Vcj1lY
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for allowing usage of the same PT value within multiple m- lines?
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 11:01:44 -0000

--Apple-Mail=_EE46B561-E0BB-4885-B4A3-613FA9C84F88
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

On 3 Mar 2014, at 11:00, Christer Holmberg =
<christer.holmberg@ericsson.com> wrote:
> >The same way you separate every other stream: SSRC to identify the =
media source, then direct to >the right decoder path based on the PT =
mapping table.=20
> =20
> Yes, but then you need to know which SSRC(s) are going to be used for =
each media stream.

Huh? You may have to explain, because I don=92t see that.


--=20
Colin Perkins
http://csperkins.org/




--Apple-Mail=_EE46B561-E0BB-4885-B4A3-613FA9C84F88
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">On 3 =
Mar 2014, at 11:00, Christer Holmberg &lt;<a =
href=3D"mailto:christer.holmberg@ericsson.com">christer.holmberg@ericsson.=
com</a>&gt; wrote:<br><div><blockquote type=3D"cite"><div lang=3D"EN-GB" =
link=3D"#0563C1" vlink=3D"#954F72"><div class=3D"WordSection1"><div><p =
class=3D"MsoNormal"><span style=3D"color:#1F497D">&gt;</span>The same =
way you separate every other stream: SSRC to identify the media source, =
then direct to
<span style=3D"color:#1F497D">&gt;</span>the right decoder path based on =
the PT mapping table.&nbsp;<o:p></o:p></p>
</div>
<div><p class=3D"MsoNormal"><span =
style=3D"color:#1F497D">&nbsp;</span></p><p class=3D"MsoNormal"><span =
style=3D"color:#1F497D">Yes, but then you need to know which SSRC(s) are =
going to be used for each media =
stream.<o:p></o:p></span></p></div></div></div></blockquote><br></div><div=
>Huh? You may have to explain, because I don=92t see that.</div><div =
apple-content-edited=3D"true"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; border-spacing: 0px;"><div><br =
class=3D"Apple-interchange-newline"><br =
class=3D"khtml-block-placeholder"></div><div>--&nbsp;</div><div></div><div=
>Colin Perkins</div><div><a =
href=3D"http://csperkins.org/">http://csperkins.org/</a></div><div><br></d=
iv></span><br class=3D"Apple-interchange-newline">

</div>
<br><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"Lucida Sans Typewriter";}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.apple-style-span
	{mso-style-name:apple-style-span;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle22
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style></body></html>=

--Apple-Mail=_EE46B561-E0BB-4885-B4A3-613FA9C84F88--


From nobody Mon Mar  3 03:06:04 2014
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 B672C1A0C5A for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 03:06:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.239
X-Spam-Level: 
X-Spam-Status: No, score=-1.239 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, HOST_MISMATCH_NET=0.311, HTML_MESSAGE=0.001, 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 zBRfe29iF6sk for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 03:06:01 -0800 (PST)
Received: from sessmg20.mgmt.ericsson.se (sessmg20.ericsson.net [193.180.251.50]) by ietfa.amsl.com (Postfix) with ESMTP id 622031A0785 for <mmusic@ietf.org>; Mon,  3 Mar 2014 03:05:59 -0800 (PST)
X-AuditID: c1b4fb32-b7f4c8e0000012f5-db-531462145d58
Received: from ESESSHC012.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg20.mgmt.ericsson.se (Symantec Mail Security) with SMTP id E3.60.04853.41264135; Mon,  3 Mar 2014 12:05:56 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.216]) by ESESSHC012.ericsson.se ([153.88.183.54]) with mapi id 14.02.0387.000; Mon, 3 Mar 2014 12:05:55 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Colin Perkins <csp@csperkins.org>
Thread-Topic: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for allowing usage of the same PT value within multiple m- lines?
Thread-Index: Ac818yLx23ucJzjaSbubJw5GhjG+ygAyCDEAAAM6QvD///NSAP//7o6ggAAV3AD//+xLsIAAGcSA///u21AAAkQTAP//7vZw
Date: Mon, 3 Mar 2014 11:05:55 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D1C5E15@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D1C368D@ESESSMB209.ericsson.se> <7A9A37FB-196F-4F79-805B-95CE9B67C344@csperkins.org> <7594FB04B1934943A5C02806D1A2204B1D1C5A25@ESESSMB209.ericsson.se> <97FFA3D1-8159-43B8-BD02-02BF420D4464@csperkins.org> <7594FB04B1934943A5C02806D1A2204B1D1C5BBF@ESESSMB209.ericsson.se> <D1A5B4EB-45E0-4BFA-BB93-96119F1B8152@csperkins.org> <7594FB04B1934943A5C02806D1A2204B1D1C5CCE@ESESSMB209.ericsson.se> <FF73D8EC-D4EB-4E53-8D05-63D4624F4B01@csperkins.org> <7594FB04B1934943A5C02806D1A2204B1D1C5DDF@ESESSMB209.ericsson.se> <331AFD56-7C29-4BB3-9B63-00D1E9317F9C@csperkins.org>
In-Reply-To: <331AFD56-7C29-4BB3-9B63-00D1E9317F9C@csperkins.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.154]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1D1C5E15ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrMLMWRmVeSWpSXmKPExsUyM+Jvja5IkkiwwbtufYvlL08wWkxd/pjF gclj2v37bB5LlvxkCmCK4rJJSc3JLEst0rdL4Mpo/vGDrWCyccXP/wvZGxhn6XYxcnBICJhI fF8Z2MXICWSKSVy4t54NxBYSOMEo8e+2excjF5C9mFGiqX8tG0g9m4CFRPc/bZAaEQFViR3H /zGChJkF1CWuLg4CKRcWaGGUaD1zgB3EERFoZZSY0n+ECaIhT+L0zM/sIDaLgIpE++H9YHFe AV+JGXN3M0Is+8ACdMVPJpCpnAKOEp/W5oHUMAId9/3UGrB6ZgFxiVtP5jNBHC0gsWTPeWYI W1Ti5eN/rBC2ksSi25+ZII7Llzj9Vh1ilaDEyZlPWCYwis5CMmkWQtUsJFUQJToSC3Z/YoOw tSWWLXzNDGOfOfCYCVl8ASP7KkbJ4tTi4tx0IwO93PTcEr3Uoszk4uL8PL3i1E2MwIg7uOW3 0Q7Gk3vsDzFKc7AoifNeZ60JEhJITyxJzU5NLUgtii8qzUktPsTIxMEp1cC4bEf0obd5CU8i dY34zsaeepWgq/tWWcChQMt5y5OfgvpZc3LSlj3JmHdc+/rExXP1Zpr87F8v51LtVzrhlOWx ZQFXPq6pumXVbG+crT/npvCx09tzp/SLl3SuEVcvKv695YjezYWxzesbdCew3d8b/+qBv6fM 7K/6pzR6S7YnpjH4lLx3WCCixFKckWioxVxUnAgAEcfrHIYCAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/v2FZFxu7c2dlLZeXfBp7J3VxHIg
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for allowing usage of the same PT value within multiple m- lines?
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 11:06:03 -0000

--_000_7594FB04B1934943A5C02806D1A2204B1D1C5E15ESESSMB209erics_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,
>The same way you separate every other stream: SSRC to identify the media s=
ource, then direct to >the right decoder path based on the PT mapping table=
.

Yes, but then you need to know which SSRC(s) are going to be used for each =
media stream.

Huh? You may have to explain, because I don't see that.

Assume you have two video m- lines.
On both m- lines, you indicate that you can receive a codec using PT value =
Y.
Then, you receive a video media packet, with PT value Y, and SSRC value 123=
4567. How do you know which of the two m- lines this media packet is associ=
ated with?
Regards,
Christer





--
Colin Perkins
http://csperkins.org/




--_000_7594FB04B1934943A5C02806D1A2204B1D1C5E15ESESSMB209erics_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.apple-style-span
	{mso-style-name:apple-style-span;}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle23
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-GB" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi,<o:p></o:p></span><=
/p>
<div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:#1F497D">&gt;</span>The same way you separate=
 every other stream: SSRC to identify the media source, then direct to
<span style=3D"color:#1F497D">&gt;</span>the right decoder path based on th=
e PT mapping table.&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:#1F497D">Yes, but then you need to know which=
 SSRC(s) are going to be used for each media stream.</span><o:p></o:p></p>
</div>
</div>
</div>
</blockquote>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Huh? You may have to explain, because I don&#8217;t =
see that.<o:p></o:p></p>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"color:=
#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"color:=
red">Assume you have two video m- lines.<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"color:=
red">On both m- lines, you indicate that you can receive a codec using PT v=
alue Y.<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"color:=
red">Then, you receive a video media packet, with PT value Y, and SSRC valu=
e 1234567. How do you know which of the two m- lines this media packet is a=
ssociated with?<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"color:=
red">Regards,<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"color:=
red">Christer<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"color:=
red"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"color:=
red"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"color:=
#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"color:=
#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"color:=
#1F497D"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal">--&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Colin Perkins<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><a href=3D"http://csperkins.org/">http://csperkins.o=
rg/</a><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt;font-family:&quot;Ti=
mes New Roman&quot;,&quot;serif&quot;;mso-fareast-language:EN-GB"><o:p>&nbs=
p;</o:p></span></p>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B1D1C5E15ESESSMB209erics_--


From nobody Mon Mar  3 03:12:02 2014
Return-Path: <csp@csperkins.org>
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 CB78D1A0F1D for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 03:12:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001] autolearn=ham
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 NOSfN8FcnAbJ for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 03:11:56 -0800 (PST)
Received: from haggis.mythic-beasts.com (haggis.mythic-beasts.com [IPv6:2a00:1098:0:86:1000:0:2:1]) by ietfa.amsl.com (Postfix) with ESMTP id 24B131A0CC6 for <mmusic@ietf.org>; Mon,  3 Mar 2014 03:11:56 -0800 (PST)
Received: from [130.209.254.3] (port=59346 helo=vpn3.dcs.gla.ac.uk) by haggis.mythic-beasts.com with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from <csp@csperkins.org>) id 1WKQmh-00077e-Kv; Mon, 03 Mar 2014 11:11:52 +0000
Content-Type: multipart/alternative; boundary="Apple-Mail=_D24F4CF8-1777-40AD-BB4D-D48FFF2B6FF4"
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Colin Perkins <csp@csperkins.org>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D1C5E15@ESESSMB209.ericsson.se>
Date: Mon, 3 Mar 2014 11:11:46 +0000
Message-Id: <A140A09A-20C9-4294-82F7-487606F98C68@csperkins.org>
References: <7594FB04B1934943A5C02806D1A2204B1D1C368D@ESESSMB209.ericsson.se> <7A9A37FB-196F-4F79-805B-95CE9B67C344@csperkins.org> <7594FB04B1934943A5C02806D1A2204B1D1C5A25@ESESSMB209.ericsson.se> <97FFA3D1-8159-43B8-BD02-02BF420D4464@csperkins.org> <7594FB04B1934943A5C02806D1A2204B1D1C5BBF@ESESSMB209.ericsson.se> <D1A5B4EB-45E0-4BFA-BB93-96119F1B8152@csperkins.org> <7594FB04B1934943A5C02806D1A2204B1D1C5CCE@ESESSMB209.ericsson.se> <FF73D8EC-D4EB-4E53-8D05-63D4624F4B01@csperkins.org> <7594FB04B1934943A5C02806D1A2204B1D1C5DDF@ESESSMB209.ericsson.se> <331AFD56-7C29-4BB3-9B63-00D1E9317F9C@csperkins.org> <7594FB04B1934943A5C02806D1A2204B1D1C5E15@ESESSMB209.ericsson.se>
To: Christer Holmberg <christer.holmberg@ericsson.com>
X-Mailer: Apple Mail (2.1874)
X-BlackCat-Spam-Score: -28
X-Mythic-Debug: Threshold =  On = 
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/7-9p2MNyhzl_EXZHM0iENYQd8XE
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for allowing usage of the same PT value within multiple m- lines?
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 11:12:02 -0000

--Apple-Mail=_D24F4CF8-1777-40AD-BB4D-D48FFF2B6FF4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

On 3 Mar 2014, at 11:05, Christer Holmberg =
<christer.holmberg@ericsson.com> wrote:
> Hi,
> >The same way you separate every other stream: SSRC to identify the =
media source, then direct to >the right decoder path based on the PT =
mapping table.=20
> =20
> Yes, but then you need to know which SSRC(s) are going to be used for =
each media stream.
> =20
> Huh? You may have to explain, because I don=92t see that.
> =20
>=20
> Assume you have two video m- lines.
>=20
> On both m- lines, you indicate that you can receive a codec using PT =
value Y.
>=20
> Then, you receive a video media packet, with PT value Y, and SSRC =
value 1234567. How do you know which of the two m- lines this media =
packet is associated with?
>=20

We=92ve discussed this multiple times before. If payload types numbers =
are unique across m=3D lines, then obviously you can use them to =
identify the m=3D line. If you reuse payload type values across m=3D =
lines, then you need some other way of identifying m=3D lines, if you =
care about doing so. Signalled SSRC values are one approach, something =
like AppID might be another. =20


--=20
Colin Perkins
http://csperkins.org/




--Apple-Mail=_D24F4CF8-1777-40AD-BB4D-D48FFF2B6FF4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">On 3 =
Mar 2014, at 11:05, Christer Holmberg &lt;<a =
href=3D"mailto:christer.holmberg@ericsson.com">christer.holmberg@ericsson.=
com</a>&gt; wrote:<div><blockquote type=3D"cite">

<meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered =
medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.apple-style-span
	{mso-style-name:apple-style-span;}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle23
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->

<div lang=3D"EN-GB" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1"><p class=3D"MsoNormal"><span =
style=3D"color:#1F497D">Hi,<o:p></o:p></span></p>
<div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<div><p class=3D"MsoNormal" =
style=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span =
style=3D"color:#1F497D">&gt;</span>The same way you separate every other =
stream: SSRC to identify the media source, then direct to
<span style=3D"color:#1F497D">&gt;</span>the right decoder path based on =
the PT mapping table.&nbsp;<o:p></o:p></p>
</div>
<div><p class=3D"MsoNormal" =
style=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span =
style=3D"color:#1F497D">&nbsp;</span><o:p></o:p></p><p class=3D"MsoNormal"=
 style=3D"mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span =
style=3D"color:#1F497D">Yes, but then you need to know which SSRC(s) are =
going to be used for each media stream.</span><o:p></o:p></p>
</div>
</div>
</div>
</blockquote><p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div><p class=3D"MsoNormal">Huh? You may have to explain, because I =
don=92t see that.<o:p></o:p></p>
</div>
<div>
<div><p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span =
style=3D"color:#1F497D">&nbsp;</span></p><p class=3D"MsoNormal" =
style=3D"margin-bottom:12.0pt"><span style=3D"color:red">Assume you have =
two video m- lines.<o:p></o:p></span></p><p class=3D"MsoNormal" =
style=3D"margin-bottom:12.0pt"><span style=3D"color:red">On both m- =
lines, you indicate that you can receive a codec using PT value =
Y.<o:p></o:p></span></p><p class=3D"MsoNormal" =
style=3D"margin-bottom:12.0pt"><span style=3D"color:red">Then, you =
receive a video media packet, with PT value Y, and SSRC value 1234567. =
How do you know which of the two m- lines this media packet is =
associated =
with?<o:p></o:p></span></p></div></div></div></div></blockquote></div><div=
 apple-content-edited=3D"true"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; border-spacing: 0px;"><div>We=92ve =
discussed this multiple times before. If payload types numbers are =
unique across m=3D lines, then obviously you can use them to identify =
the m=3D line. If you reuse payload type values across m=3D lines, then =
you need some other way of identifying m=3D lines, if you care about =
doing so. Signalled SSRC values are one approach, something like AppID =
might be another. =
&nbsp;</div><div><br></div><div><br></div><div>--&nbsp;</div><div></div><d=
iv>Colin Perkins</div><div><a =
href=3D"http://csperkins.org/">http://csperkins.org/</a></div><div><br></d=
iv></span><br class=3D"Apple-interchange-newline">

</div>
<br></body></html>=

--Apple-Mail=_D24F4CF8-1777-40AD-BB4D-D48FFF2B6FF4--


From nobody Mon Mar  3 03:13:56 2014
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 B09F61A0DE4 for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 03:13:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.85
X-Spam-Level: 
X-Spam-Status: No, score=-3.85 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 TFpLi--gxLxY for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 03:13:54 -0800 (PST)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 3DEDC1A0CC6 for <mmusic@ietf.org>; Mon,  3 Mar 2014 03:13:53 -0800 (PST)
X-AuditID: c1b4fb2d-b7f5d8e000002a7b-46-531463ed961c
Received: from ESESSHC016.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 76.93.10875.DE364135; Mon,  3 Mar 2014 12:13:49 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.216]) by ESESSHC016.ericsson.se ([153.88.183.66]) with mapi id 14.02.0387.000; Mon, 3 Mar 2014 12:13:48 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Colin Perkins <csp@csperkins.org>
Thread-Topic: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for allowing usage of the same PT value within multiple m- lines?
Thread-Index: Ac818yLx23ucJzjaSbubJw5GhjG+ygAyCDEAAAM6QvD///NSAP//7o6ggAAV3AD//+xLsIAAGcSA///u21AAAkQTAP//7vZw///sHgD//8c0cA==
Date: Mon, 3 Mar 2014 11:13:48 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D1C5E62@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D1C368D@ESESSMB209.ericsson.se> <7A9A37FB-196F-4F79-805B-95CE9B67C344@csperkins.org> <7594FB04B1934943A5C02806D1A2204B1D1C5A25@ESESSMB209.ericsson.se> <97FFA3D1-8159-43B8-BD02-02BF420D4464@csperkins.org> <7594FB04B1934943A5C02806D1A2204B1D1C5BBF@ESESSMB209.ericsson.se> <D1A5B4EB-45E0-4BFA-BB93-96119F1B8152@csperkins.org> <7594FB04B1934943A5C02806D1A2204B1D1C5CCE@ESESSMB209.ericsson.se> <FF73D8EC-D4EB-4E53-8D05-63D4624F4B01@csperkins.org> <7594FB04B1934943A5C02806D1A2204B1D1C5DDF@ESESSMB209.ericsson.se> <331AFD56-7C29-4BB3-9B63-00D1E9317F9C@csperkins.org> <7594FB04B1934943A5C02806D1A2204B1D1C5E15@ESESSMB209.ericsson.se> <A140A09A-20C9-4294-82F7-487606F98C68@csperkins.org>
In-Reply-To: <A140A09A-20C9-4294-82F7-487606F98C68@csperkins.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.154]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1D1C5E62ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrMLMWRmVeSWpSXmKPExsUyM+Jvje7bZJFggy2nRC2WvzzBaDF1+WMW ByaPaffvs3ksWfKTKYApissmJTUnsyy1SN8ugSvj99PfrAXbDSuunTjD0sC4TbuLkYNDQsBE omN3TBcjJ5ApJnHh3no2EFtI4BCjRFN3ShcjF5C9mFHi78YFrCD1bAIWEt3/tEFqRARUJXYc /8cIEmYWUJe4ujgIpFxYoIVRovXMAXYQR0SglVFiSv8RJpAiEYE6iZ2TIkB6WQRUJLrON7OD 2LwCvhLT195khtj1mlWiu6uVFSTBKeAo0finGewgRqDjvp9awwRiMwuIS9x6Mp8J4mgBiSV7 zjND2KISLx//Y4WwlSQW3f4MVZ8v8XnxTFaIZYISJ2c+YZnAKDoLyahZSMpmISmDiOtILNj9 iQ3C1pZYtvA1M4x95sBjJmTxBYzsqxjZcxMzc9LLDTcxAiPq4JbfujsYT50TOcQozcGiJM77 4a1zkJBAemJJanZqakFqUXxRaU5q8SFGJg5OqQbG7nb94JlB+1d3mmZO67HW7mAwTUmVCGW8 vMf6wNuEhu5gVumoST2lxwqiunjmnBCqusQuviDkZehy38DpPa8PnRcLcKsJ0FdY9Dz6jJmH zecVth25R659sXa8oaI0Ne/sgi9RH3V7NWezmjDtuLCvbJ2qddLa6w+ZWaczR4oF8ry/7xpY m6LEUpyRaKjFXFScCAAXfHo3dgIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/ZmoLKuHFUKTkc8AN9urbvJV1qj8
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for allowing usage of the same PT value within multiple m- lines?
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 11:13:55 -0000

--_000_7594FB04B1934943A5C02806D1A2204B1D1C5E62ESESSMB209erics_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,
Assume you have two video m- lines.
On both m- lines, you indicate that you can receive a codec using PT value =
Y.
Then, you receive a video media packet, with PT value Y, and SSRC value 123=
4567. How do you know which of the two m- lines this media packet is associ=
ated with?
We've discussed this multiple times before. If payload types numbers are un=
ique across m=3D lines, then obviously you can use them to identify the m=
=3D line. If you reuse payload type values across m=3D lines, then you need=
 some other way of identifying m=3D lines, if you care about doing so. Sign=
alled SSRC values are one approach, something like AppID might be another.

...which takes us back to what I said in the beginning: when you send your =
initial offer, and assign the PT values you want to receive, you don't know=
 whether the remote peer supports AppID, or whatever other mechanism that c=
ould be used.

Regards,

Christer

--_000_7594FB04B1934943A5C02806D1A2204B1D1C5E62ESESSMB209erics_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.apple-style-span
	{mso-style-name:apple-style-span;}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle23
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle24
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-GB" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi,</span><span style=
=3D"color:#1F497D">&nbsp;</span><span style=3D"color:#1F497D"><o:p></o:p></=
span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"color:=
red">Assume you have two video m- lines.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"color:=
red">On both m- lines, you indicate that you can receive a codec using PT v=
alue Y.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"color:=
red">Then, you receive a video media packet, with PT value Y, and SSRC valu=
e 1234567. How do you know which of the two m- lines this media packet is a=
ssociated with?</span><o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal"><span class=3D"apple-style-span"><span style=3D"font=
-size:12.0pt;font-family:&quot;Times New Roman&quot;,&quot;serif&quot;;mso-=
fareast-language:EN-GB">We&#8217;ve discussed this multiple times before. I=
f payload types numbers are unique across m=3D lines, then obviously
 you can use them to identify the m=3D line. If you reuse payload type valu=
es across m=3D lines, then you need some other way of identifying m=3D line=
s, if you care about doing so. Signalled SSRC values are one approach, some=
thing like AppID might be another. &nbsp;<span style=3D"color:#1F497D"><o:p=
></o:p></span></span></span></p>
<p class=3D"MsoNormal"><span class=3D"apple-style-span"><span style=3D"colo=
r:#1F497D;mso-fareast-language:EN-GB"><o:p>&nbsp;</o:p></span></span></p>
<p class=3D"MsoNormal"><span class=3D"apple-style-span"><span style=3D"colo=
r:#1F497D;mso-fareast-language:EN-GB">&#8230;which takes us back to what I =
said in the beginning: when you send your initial offer, and assign the PT =
values you want to receive, you don&#8217;t know whether
 the remote peer supports AppID, or whatever other mechanism that could be =
used.<o:p></o:p></span></span></p>
<p class=3D"MsoNormal"><span class=3D"apple-style-span"><span style=3D"colo=
r:#1F497D;mso-fareast-language:EN-GB"><o:p>&nbsp;</o:p></span></span></p>
<p class=3D"MsoNormal"><span class=3D"apple-style-span"><span style=3D"colo=
r:#1F497D;mso-fareast-language:EN-GB">Regards,<o:p></o:p></span></span></p>
<p class=3D"MsoNormal"><span class=3D"apple-style-span"><span style=3D"colo=
r:#1F497D;mso-fareast-language:EN-GB"><o:p>&nbsp;</o:p></span></span></p>
<p class=3D"MsoNormal"><span class=3D"apple-style-span"><span style=3D"colo=
r:#1F497D;mso-fareast-language:EN-GB">Christer<o:p></o:p></span></span></p>
</div>
</div>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B1D1C5E62ESESSMB209erics_--


From nobody Mon Mar  3 03:14:52 2014
Return-Path: <suhasietf@gmail.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 90A371A0CC6 for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 03:14:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 UI61X6p8865u for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 03:14:47 -0800 (PST)
Received: from mail-we0-x229.google.com (mail-we0-x229.google.com [IPv6:2a00:1450:400c:c03::229]) by ietfa.amsl.com (Postfix) with ESMTP id 8CCF11A0DE4 for <mmusic@ietf.org>; Mon,  3 Mar 2014 03:14:47 -0800 (PST)
Received: by mail-we0-f169.google.com with SMTP id w62so1193827wes.0 for <mmusic@ietf.org>; Mon, 03 Mar 2014 03:14:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=rWYrd4KjGVB0VKRGZS6pDTFyF0fQf7sG80wp6iiGWNo=; b=TXHi7O23GRvGLPCaohrWKHf0w7PgpBe1Dpjqd09MgxWzbzHo1Nz53AMzRwBUVtP7TX d2nOHz7IeGwrIxm2E8ALGF0S6zOXucHgG84KHKIx1Z7YYS75TAhFj0L+mh6+mQVjLAZX U2diCfYLkd5RnBlgdq7rpeeEVDjARGw637GZnqGewr7blk5o7acnFeSpg+dxWvZgNxV1 IoTaaw7gzJ0BD1KPdVyxUkD+ENBUfMDH09RGjbPNC0kCr+p+lPsTRID1KjDDjUyj/ytz 7F9Ug+oFKt88jwIH30M0/Nfy4XgEXWNcybmi99xL+ZZLSOhV1iu1UmEHIyUbFn9BCF2s ItNg==
MIME-Version: 1.0
X-Received: by 10.194.21.193 with SMTP id x1mr16186395wje.33.1393845284312; Mon, 03 Mar 2014 03:14:44 -0800 (PST)
Received: by 10.195.12.134 with HTTP; Mon, 3 Mar 2014 03:14:44 -0800 (PST)
In-Reply-To: <A140A09A-20C9-4294-82F7-487606F98C68@csperkins.org>
References: <7594FB04B1934943A5C02806D1A2204B1D1C368D@ESESSMB209.ericsson.se> <7A9A37FB-196F-4F79-805B-95CE9B67C344@csperkins.org> <7594FB04B1934943A5C02806D1A2204B1D1C5A25@ESESSMB209.ericsson.se> <97FFA3D1-8159-43B8-BD02-02BF420D4464@csperkins.org> <7594FB04B1934943A5C02806D1A2204B1D1C5BBF@ESESSMB209.ericsson.se> <D1A5B4EB-45E0-4BFA-BB93-96119F1B8152@csperkins.org> <7594FB04B1934943A5C02806D1A2204B1D1C5CCE@ESESSMB209.ericsson.se> <FF73D8EC-D4EB-4E53-8D05-63D4624F4B01@csperkins.org> <7594FB04B1934943A5C02806D1A2204B1D1C5DDF@ESESSMB209.ericsson.se> <331AFD56-7C29-4BB3-9B63-00D1E9317F9C@csperkins.org> <7594FB04B1934943A5C02806D1A2204B1D1C5E15@ESESSMB209.ericsson.se> <A140A09A-20C9-4294-82F7-487606F98C68@csperkins.org>
Date: Mon, 3 Mar 2014 11:14:44 +0000
Message-ID: <CAMRcRGRYLUSiz3FOTqhj=W3x++VLVW+Lwa42-PASRDEB-QLEYw@mail.gmail.com>
From: Suhas Nandakumar <suhasietf@gmail.com>
To: Colin Perkins <csp@csperkins.org>
Content-Type: multipart/alternative; boundary=047d7b5d56100b1a6104f3b1e570
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/KAtqCtVgnMS1Djkva1OrD1yyhjg
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for allowing usage of the same PT value within multiple m- lines?
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 11:14:50 -0000

--047d7b5d56100b1a6104f3b1e570
Content-Type: text/plain; charset=ISO-8859-1

On Monday, March 3, 2014, Colin Perkins <csp@csperkins.org> wrote:

> On 3 Mar 2014, at 11:05, Christer Holmberg <christer.holmberg@ericsson.com<javascript:_e(%7B%7D,'cvml','christer.holmberg@ericsson.com');>>
> wrote:
>
>  Hi,
>
>  >The same way you separate every other stream: SSRC to identify the
> media source, then direct to >the right decoder path based on the PT
> mapping table.
>
>
>
> Yes, but then you need to know which SSRC(s) are going to be used for each
> media stream.
>
>
>
> Huh? You may have to explain, because I don't see that.
>
>
>
> Assume you have two video m- lines.
>
> On both m- lines, you indicate that you can receive a codec using PT value
> Y.
>
> Then, you receive a video media packet, with PT value Y, and SSRC value
> 1234567. How do you know which of the two m- lines this media packet is
> associated with?
>
> We've discussed this multiple times before. If payload types numbers are
> unique across m= lines, then obviously you can use them to identify the m=
> line. If you reuse payload type values across m= lines, then you need some
> other way of identifying m= lines, if you care about doing so. Signalled
> SSRC values are one approach, something like AppID might be another.
>
>
I agree with Colin. There needs to be a way to correlate incoming rtp
streams in this scenario and early media scenario

>
> --
> Colin Perkins
> http://csperkins.org/
>
>
>
>

--047d7b5d56100b1a6104f3b1e570
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><br>On Monday, March 3, 2014, Colin Perkins &lt;<a href=3D"mailto:csp@c=
sperkins.org">csp@csperkins.org</a>&gt; wrote:<br><blockquote class=3D"gmai=
l_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left=
:1ex">
<div style=3D"word-wrap:break-word">On 3 Mar 2014, at 11:05, Christer Holmb=
erg &lt;<a href=3D"javascript:_e(%7B%7D,&#39;cvml&#39;,&#39;christer.holmbe=
rg@ericsson.com&#39;);" target=3D"_blank">christer.holmberg@ericsson.com</a=
>&gt; wrote:<div>
<blockquote type=3D"cite">





<div lang=3D"EN-GB" link=3D"#0563C1" vlink=3D"#954F72">
<div><p class=3D"MsoNormal"><span style=3D"color:#1f497d">Hi,<u></u><u></u>=
</span></p>
<div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<div><p class=3D"MsoNormal"><span style=3D"color:#1f497d">&gt;</span>The sa=
me way you separate every other stream: SSRC to identify the media source, =
then direct to
<span style=3D"color:#1f497d">&gt;</span>the right decoder path based on th=
e PT mapping table.&nbsp;<u></u><u></u></p>
</div>
<div><p class=3D"MsoNormal"><span style=3D"color:#1f497d">&nbsp;</span><u><=
/u><u></u></p><p class=3D"MsoNormal"><span style=3D"color:#1f497d">Yes, but=
 then you need to know which SSRC(s) are going to be used for each media st=
ream.</span><u></u><u></u></p>

</div>
</div>
</div>
</blockquote><p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
<div><p class=3D"MsoNormal">Huh? You may have to explain, because I don&rsq=
uo;t see that.<u></u><u></u></p>
</div>
<div>
<div><p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"c=
olor:#1f497d">&nbsp;</span></p><p class=3D"MsoNormal" style=3D"margin-botto=
m:12.0pt"><span style=3D"color:red">Assume you have two video m- lines.<u><=
/u><u></u></span></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"color:=
red">On both m- lines, you indicate that you can receive a codec using PT v=
alue Y.<u></u><u></u></span></p><p class=3D"MsoNormal" style=3D"margin-bott=
om:12.0pt">
<span style=3D"color:red">Then, you receive a video media packet, with PT v=
alue Y, and SSRC value 1234567. How do you know which of the two m- lines t=
his media packet is associated with?<u></u><u></u></span></p></div></div>
</div></div></blockquote></div><div><span style=3D"border-collapse:separate=
;border-spacing:0px"><div>We&rsquo;ve discussed this multiple times before.=
 If payload types numbers are unique across m=3D lines, then obviously you =
can use them to identify the m=3D line. If you reuse payload type values ac=
ross m=3D lines, then you need some other way of identifying m=3D lines, if=
 you care about doing so. Signalled SSRC values are one approach, something=
 like AppID might be another. &nbsp;</div>
<div><br></div></span></div></div></blockquote><div><br></div><div>I agree =
with Colin. There needs to be a&nbsp;way to correlate incoming rtp streams&=
nbsp;in this scenario and early media scenario<span></span><br></div><block=
quote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc=
 solid;padding-left:1ex">
<div style=3D"word-wrap:break-word"><div><span style=3D"border-collapse:sep=
arate;border-spacing:0px"><div><br></div><div>--&nbsp;</div><div></div><div=
>Colin Perkins</div><div><a href=3D"http://csperkins.org/" target=3D"_blank=
">http://csperkins.org/</a></div>
<div><br></div></span><br>

</div>
<br></div></blockquote>

--047d7b5d56100b1a6104f3b1e570--


From nobody Mon Mar  3 03:15:05 2014
Return-Path: <jonathan@vidyo.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 24C2C1A0EEF for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 03:15:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham
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 r9p106TaGl5p for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 03:14:56 -0800 (PST)
Received: from server209.appriver.com (server209c.appriver.com [8.31.233.118]) by ietfa.amsl.com (Postfix) with ESMTP id BE0F81A0E51 for <mmusic@ietf.org>; Mon,  3 Mar 2014 03:14:55 -0800 (PST)
X-Note-AR-ScanTimeLocal: 3/3/2014 6:14:52 AM
X-Policy: GLOBAL - vidyo.com
X-Policy: GLOBAL - vidyo.com
X-Policy: GLOBAL - vidyo.com
X-Primary: jonathan@vidyo.com
X-Note: This Email was scanned by AppRiver SecureTide
X-Virus-Scan: V-
X-Note-SnifferID: 0
X-Note: TCH-CT/SI:0-135/SG:5 3/3/2014 6:14:49 AM
X-GBUdb-Analysis: 0, 162.209.16.213, Ugly c=0.869799 p=-0.987908 Source White
X-Signature-Violations: 0-0-0-15761-c
X-Note-419: 15.6005 ms. Fail:0 Chk:1345 of 1345 total
X-Note: SCH-CT/SI:0-1345/SG:1 3/3/2014 6:14:48 AM
X-Note: Spam Tests Failed: 
X-Country-Path: ->UNITED STATES->LOCAL
X-Note-Sending-IP: 162.209.16.213
X-Note-Reverse-DNS: mail1.vidyo.com
X-Note-Return-Path: jonathan@vidyo.com
X-Note: User Rule Hits: 
X-Note: Global Rule Hits: G327 G328 G329 G330 G334 G335 G445 
X-Note: Encrypt Rule Hits: 
X-Note: Mail Class: VALID
X-Note: Headers Injected
Received: from [162.209.16.213] (HELO mail.vidyo.com) by server209.appriver.com (CommuniGate Pro SMTP 6.0.2) with ESMTPS id 102475061; Mon, 03 Mar 2014 06:14:52 -0500
Received: from 492133-EXCH2.vidyo.com ([fe80::50:56ff:fe85:6b62]) by 492132-EXCH1.vidyo.com ([fe80::50:56ff:fe85:4f77%13]) with mapi id 14.03.0146.000; Mon, 3 Mar 2014 05:14:51 -0600
From: Jonathan Lennox <jonathan@vidyo.com>
To: Colin Perkins <csp@csperkins.org>
Thread-Topic: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for allowing usage of the same PT value within multiple m- lines?
Thread-Index: AQHPNs+935bAAhX3u0OFIZqx0T37gJrPmosA
Date: Mon, 3 Mar 2014 11:14:51 +0000
Message-ID: <38BBC1E1-A5DE-477D-AADB-DB1B602644CC@vidyo.com>
References: <7594FB04B1934943A5C02806D1A2204B1D1C368D@ESESSMB209.ericsson.se> <7A9A37FB-196F-4F79-805B-95CE9B67C344@csperkins.org>
In-Reply-To: <7A9A37FB-196F-4F79-805B-95CE9B67C344@csperkins.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [31.133.187.226]
Content-Type: multipart/alternative; boundary="_000_38BBC1E1A5DE477DAADBDB1B602644CCvidyocom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/LB4Kxaf3PWvQbe9fegMQ9FiDUAI
Cc: mmusic <mmusic@ietf.org>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for allowing usage of the same PT value within multiple m- lines?
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 11:15:02 -0000

--_000_38BBC1E1A5DE477DAADBDB1B602644CCvidyocom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable


On Mar 3, 2014, at 9:33 AM, Colin Perkins <csp@csperkins.org<mailto:csp@csp=
erkins.org>> wrote:

Christer,

The bundled m=3D lines form a single RTP session. That means that they shar=
e a single RTP payload number space. The rule therefore has to be that you =
can only reuse the payload type across bundled m=3D lines if it refers to t=
he exact same configuration of the exact same codec in all cases, where =93=
exact same configuration=94 means that the a=3Dfmtp: line and all other SDP=
 attributes that configure the codec and packetisation of the media are ide=
ntical.

I agree with this, with the addition that "all other SDP attributes that co=
nfigure the codec and packetisation of the media=94 is something that we=92=
re going to need to specify in draft-ietf-mmusic-sdp-mux-attributes.

There will need to be a new category in that draft, to indicate which SDP a=
ttributes that specify configuration on a per-PT basis need to be IDENTICAL=
-PER-PT.

If that=92s not specific enough, then MUST NOT reuse payload types across m=
=3D lines in a bundled group is the safe choice. I believe your propose tha=
t it=92s okay if you can handle the media is too vague, and will cause us p=
roblems down the line.

Colin




On 2 Mar 2014, at 08:44, Christer Holmberg <christer.holmberg@ericsson.com<=
mailto:christer.holmberg@ericsson.com>> wrote:
Hi,

One of the open issues we have in BUNDLE, is when it is allowed to use the =
same PT value within multiple m- lines.

We tried to come up with different criteria, including a =93codec configura=
tion=94 concept, but we never managed to agree on something.

So, in London, I intend to suggest that we simply say: if you offer the sam=
e PT value within multiple m- line, make sure you can handle the associated=
 media when it arrives =96 period (keep in mind that you always indicate wh=
at you want to RECEIVE =96 the remote peer can still ask you to SEND using =
different PT values).

If you don=92t like this, please provide an alternative solution, because I=
 want to close this issue in London. There is no idea to keep =93taking the=
 issue back to the list=94. We=92ve done that for a few meetings already.

Regards,

Christer
_______________________________________________
mmusic mailing list
mmusic@ietf.org<mailto:mmusic@ietf.org>
https://www.ietf.org/mailman/listinfo/mmusic



--
Colin Perkins
http://csperkins.org/



_______________________________________________
mmusic mailing list
mmusic@ietf.org<mailto:mmusic@ietf.org>
https://www.ietf.org/mailman/listinfo/mmusic


--_000_38BBC1E1A5DE477DAADBDB1B602644CCvidyocom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <A2A9062A80E2EF46A9B26F104351FE2E@vidyo.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space;">
<br>
<div>
<div>On Mar 3, 2014, at 9:33 AM, Colin Perkins &lt;<a href=3D"mailto:csp@cs=
perkins.org">csp@csperkins.org</a>&gt; wrote:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite">
<div style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; line-hei=
ght: normal; orphans: auto; text-align: start; text-indent: 0px; text-trans=
form: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-t=
ext-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -we=
bkit-line-break: after-white-space;">
Christer,
<div><br>
</div>
<div>The bundled m=3D lines form a single RTP session. That means that they=
 share a single RTP payload number space. The rule therefore has to be that=
 you can only reuse the payload type across bundled m=3D lines if it refers=
 to the exact same configuration of
 the exact same codec in all cases, where =93exact same configuration=94 me=
ans that the a=3Dfmtp: line and all other SDP attributes that configure the=
 codec and packetisation of the media are identical.</div>
</div>
</blockquote>
<div><br>
</div>
I agree with this, with the addition that &quot;all other SDP attributes th=
at configure the codec and packetisation of the media=94 is something that =
we=92re going to need to specify in draft-ietf-mmusic-sdp-mux-attributes.</=
div>
<div><br>
</div>
<div>There will need to be a new category in that draft, to indicate which =
SDP attributes that specify configuration on a per-PT basis need to be IDEN=
TICAL-PER-PT.<br>
<br>
<blockquote type=3D"cite">
<div style=3D"font-family: Helvetica; font-size: 12px; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; line-hei=
ght: normal; orphans: auto; text-align: start; text-indent: 0px; text-trans=
form: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-t=
ext-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -we=
bkit-line-break: after-white-space;">
<div>If that=92s not specific enough, then MUST NOT reuse payload types acr=
oss m=3D lines in a bundled group is the safe choice. I believe your propos=
e that it=92s okay if you can handle the media is too vague, and will cause=
 us problems down the line.</div>
<div><br>
</div>
<div>Colin</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
<div>
<div>On 2 Mar 2014, at 08:44, Christer Holmberg &lt;<a href=3D"mailto:chris=
ter.holmberg@ericsson.com" style=3D"color: rgb(149, 79, 114); text-decorati=
on: underline;">christer.holmberg@ericsson.com</a>&gt; wrote:</div>
<blockquote type=3D"cite">
<div lang=3D"EN-GB" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1" style=3D"page: WordSection1;">
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif;">
Hi,<o:p></o:p></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif;">
<o:p>&nbsp;</o:p></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif;">
One of the open issues we have in BUNDLE, is when it is allowed to use the =
same PT value within multiple m- lines.<o:p></o:p></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif;">
<o:p>&nbsp;</o:p></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif;">
We tried to come up with different criteria, including a =93codec configura=
tion=94 concept, but we never managed to agree on something.<o:p></o:p></di=
v>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif;">
<o:p>&nbsp;</o:p></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif;">
So, in London, I intend to suggest that we simply say: if you offer the sam=
e PT value within multiple m- line, make sure you can handle the associated=
 media when it arrives =96 period (keep in mind that you always indicate wh=
at you want to RECEIVE =96 the remote
 peer can still ask you to SEND using different PT values).<o:p></o:p></div=
>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif;">
<o:p>&nbsp;</o:p></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif;">
If you don=92t like this, please provide an alternative solution, because I=
 want to close this issue in London. There is no idea to keep =93taking the=
 issue back to the list=94. We=92ve done that for a few meetings already.<o=
:p></o:p></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif;">
<o:p>&nbsp;</o:p></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif;">
Regards,<o:p></o:p></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif;">
<o:p>&nbsp;</o:p></div>
<div style=3D"margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calib=
ri, sans-serif;">
Christer<o:p></o:p></div>
</div>
</div>
_______________________________________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" style=3D"color: rgb(149, 79, 114); text-=
decoration: underline;">mmusic@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" style=3D"color: rg=
b(149, 79, 114); text-decoration: underline;">https://www.ietf.org/mailman/=
listinfo/mmusic</a><br>
</blockquote>
</div>
<br>
<div apple-content-edited=3D"true"><span class=3D"Apple-style-span" style=
=3D"border-collapse: separate; font-family: 'Lucida Sans Typewriter'; borde=
r-spacing: 0px;">
<div><br class=3D"Apple-interchange-newline">
<br class=3D"khtml-block-placeholder">
</div>
<div>--&nbsp;</div>
<div></div>
<div>Colin Perkins</div>
<div><a href=3D"http://csperkins.org/" style=3D"color: rgb(149, 79, 114); t=
ext-decoration: underline;">http://csperkins.org/</a></div>
<div><br>
</div>
</span><br class=3D"Apple-interchange-newline">
</div>
<br>
</div>
_______________________________________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" style=3D"color: rgb(149, 79, 114); text-=
decoration: underline;">mmusic@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" style=3D"color: rg=
b(149, 79, 114); text-decoration: underline;">https://www.ietf.org/mailman/=
listinfo/mmusic</a></div>
</blockquote>
</div>
<br>
</body>
</html>

--_000_38BBC1E1A5DE477DAADBDB1B602644CCvidyocom_--


From nobody Mon Mar  3 03:17:47 2014
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 D4CBF1A0E46 for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 03:17:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.85
X-Spam-Level: 
X-Spam-Status: No, score=-3.85 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 sxKFt8CmxXLO for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 03:17:43 -0800 (PST)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id 22E131A0CC6 for <mmusic@ietf.org>; Mon,  3 Mar 2014 03:17:42 -0800 (PST)
X-AuditID: c1b4fb25-b7f038e000005d01-f4-531464d386aa
Received: from ESESSHC001.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id B6.0D.23809.3D464135; Mon,  3 Mar 2014 12:17:39 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.216]) by ESESSHC001.ericsson.se ([153.88.183.21]) with mapi id 14.02.0387.000; Mon, 3 Mar 2014 12:17:38 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Suhas Nandakumar <suhasietf@gmail.com>, Colin Perkins <csp@csperkins.org>
Thread-Topic: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for allowing usage of the same PT value within multiple m- lines?
Thread-Index: Ac818yLx23ucJzjaSbubJw5GhjG+ygAyCDEAAAM6QvD///NSAP//7o6ggAAV3AD//+xLsIAAGcSA///u21AAAkQTAP//7vZw///sHgD//9doAP//nX0A
Date: Mon, 3 Mar 2014 11:17:38 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D1C5EAF@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D1C368D@ESESSMB209.ericsson.se> <7A9A37FB-196F-4F79-805B-95CE9B67C344@csperkins.org> <7594FB04B1934943A5C02806D1A2204B1D1C5A25@ESESSMB209.ericsson.se> <97FFA3D1-8159-43B8-BD02-02BF420D4464@csperkins.org> <7594FB04B1934943A5C02806D1A2204B1D1C5BBF@ESESSMB209.ericsson.se> <D1A5B4EB-45E0-4BFA-BB93-96119F1B8152@csperkins.org> <7594FB04B1934943A5C02806D1A2204B1D1C5CCE@ESESSMB209.ericsson.se> <FF73D8EC-D4EB-4E53-8D05-63D4624F4B01@csperkins.org> <7594FB04B1934943A5C02806D1A2204B1D1C5DDF@ESESSMB209.ericsson.se> <331AFD56-7C29-4BB3-9B63-00D1E9317F9C@csperkins.org> <7594FB04B1934943A5C02806D1A2204B1D1C5E15@ESESSMB209.ericsson.se> <A140A09A-20C9-4294-82F7-487606F98C68@csperkins.org> <CAMRcRGRYLUSiz3FOTqhj=W3x++VLVW+Lwa42-PASRDEB-QLEYw@mail.gmail.com>
In-Reply-To: <CAMRcRGRYLUSiz3FOTqhj=W3x++VLVW+Lwa42-PASRDEB-QLEYw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.154]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1D1C5EAFESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrLLMWRmVeSWpSXmKPExsUyM+Jvje7lFJFgg+7/shbLX55gtJi6/DGL xc65HcwOzB7T7t9n89g56y67x5IlP5kCmKO4bFJSczLLUov07RK4Mn7/WMBYsFSjYsIkpwbG HcpdjBwcEgImEnuX2nQxcgKZYhIX7q1n62Lk4hASOMQosWjiXyhnMaPE/dUX2EEa2AQsJLr/ aYOYIgK+Er8X2YCYzALqElcXB4FUCwu0MEq0njnADuKICLQySkzpP8IE4TQxSmyY8ocZZBuL gIrE5VMXWUG6eYEGzZ8UB7FrE5vE4Q8bGUFqOAUCJe7OuAlmMwJd9/3UGiYQm1lAXOLWk/lM EFcLSCzZc54ZwhaVePn4HyuErSSx6PZnqPp8iVWXtrKD2LwCghInZz5hmcAoOgvJqFlIymYh KYOI60gs2P2JDcLWlli28DUzjH3mwGMmZPEFjOyrGNlzEzNz0suNNjECo+zglt+qOxjvnBM5 xCjNwaIkzvvhrXOQkEB6YklqdmpqQWpRfFFpTmrxIUYmDk6pBkZBhm9PPL/ee6mcdsXthlPH U87vAcqXLrzPubu+RuTAHJa9Lz137JvgJ5ygUJgv6PPmY5bvJ7PibUFTkuIbG55a7K4QW71S etIeTyOt5Z+eu8ht2zeRr8FQPqPy38/3PXmORzdkJhySiH/fKvNSu8XhmqDvNmXbmLWCovNO aj8+dyd+9sU72RZKLMUZiYZazEXFiQAw5JUtgAIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/2kjHAG2YS70aPfJjm8ZL9k65bRc
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for allowing usage of the same PT value within multiple m- lines?
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 11:17:46 -0000

--_000_7594FB04B1934943A5C02806D1A2204B1D1C5EAFESESSMB209erics_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

We've discussed this multiple times before. If payload types numbers are un=
ique across m=3D lines, then obviously you can use them to identify the m=
=3D line. If you reuse payload type values across m=3D lines, then you need=
 some other way of identifying m=3D lines, if you care about doing so. Sign=
alled SSRC values are one approach, something like AppID might be another.


I agree with Colin. There needs to be a way to correlate incoming rtp strea=
ms in this scenario and early media scenario

I agree. The question is: when you send the first offer, and assign the PT =
values you want to receive, how do you know whether the remote peer support=
s "a way"?

Regards,

Christer

--_000_7594FB04B1934943A5C02806D1A2204B1D1C5EAFESESSMB209erics_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D;mso-fareast-language:EN-US=
">Hi,<o:p></o:p></span></p>
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal">We&#8217;ve discussed this multiple times before. If=
 payload types numbers are unique across m=3D lines, then obviously you can=
 use them to identify the m=3D line. If you reuse payload type values acros=
s m=3D lines, then you need some other way of
 identifying m=3D lines, if you care about doing so. Signalled SSRC values =
are one approach, something like AppID might be another. &nbsp;<o:p></o:p><=
/p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">I agree with Colin. There needs to be a&nbsp;way to =
correlate incoming rtp streams&nbsp;in this scenario and early media scenar=
io<o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">I agree. The question is:=
 when you send the first offer, and assign the PT values you want to receiv=
e, how do you know whether the remote peer supports &#8220;a way&#8221;?<o:=
p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Regards,<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Christer<o:p></o:p></span=
></p>
</div>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B1D1C5EAFESESSMB209erics_--


From nobody Mon Mar  3 05:17:54 2014
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 62B181A0051 for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 05:17:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.85
X-Spam-Level: 
X-Spam-Status: No, score=-3.85 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 16CQs9ku-cyy for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 05:17:51 -0800 (PST)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id B2E3B1A0040 for <mmusic@ietf.org>; Mon,  3 Mar 2014 05:17:50 -0800 (PST)
X-AuditID: c1b4fb2d-b7f5d8e000002a7b-cf-531480fb48aa
Received: from ESESSHC005.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 47.B5.10875.BF084135; Mon,  3 Mar 2014 14:17:47 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.216]) by ESESSHC005.ericsson.se ([153.88.183.33]) with mapi id 14.02.0387.000; Mon, 3 Mar 2014 14:17:46 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: IETF#89: BUNDLE: Q9: What are the criteria for allowing usage of the same PT value within multiple m- lines? - A new take.
Thread-Index: Ac824vtSFLJVCI5rSOGVBTMx34MhTQ==
Date: Mon, 3 Mar 2014 13:17:45 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D1C6336@ESESSMB209.ericsson.se>
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: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1D1C6336ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrBLMWRmVeSWpSXmKPExsUyM+Jvje7vBpFgg2urhC2mLn/M4sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujAu7/jAXNNtW9PRsZWtg3GnexcjJISFgInH/0gZGCFtM4sK9 9WxdjFwcQgKHGCWOX3vKCOEsZpT4/bMByOHgYBOwkOj+pw3SICKgLvF1bw8zSI2wQCujxOxf m1hAHBGBLkaJzZ0PWCGq9CR+XXvMBmKzCKhITDx/CGwdr4CvxNeLv8FqGIFWfz+1hgnEZhYQ l7j1ZD4TxEkCEkv2nGeGsEUlXj7+xwphK0ms2H6JEaI+X+LbiRWsEDMFJU7OfMIygVFoFpJR s5CUzUJSBhHXkViw+xMbhK0tsWzha2YY+8yBx0zI4gsY2VcxsucmZuaklxtuYgSG/sEtv3V3 MJ46J3KIUZqDRUmc98Nb5yAhgfTEktTs1NSC1KL4otKc1OJDjEwcnFINjOX1AuqWeddMfa6L B0aq7jl6+OneCTmzk4MWX1+ia+XOJ8XfI3JnzdTemUFGDRXcIouEXrtbzr7LLq5UPHG54sM7 M90PKWv+k6vkbduYeJb10qlvZ9/EvDXe+3iSnd/BeQWfny7YWztZhqFhhakfw5uHE40u5J95 vcDKYu7f6Uqtz1hM50Xf/aPEUpyRaKjFXFScCADSqxDZSwIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/_9WCPT3VR56KaynHdgoPr_lAeDE
Subject: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for allowing usage of the same PT value within multiple m- lines? - A new take.
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 13:17:53 -0000

--_000_7594FB04B1934943A5C02806D1A2204B1D1C6336ESESSMB209erics_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

Based on the discussions, we basically have two alternatives:

Alternative 1: Forbid the usage of the same PT value within multiple m- lin=
es.

Alternative 2: Allow usage of the same PT value within multiple m- lines, a=
nd if the answer does not support whatever extensions that are needed for t=
he offerer to distinguish the media, the offer needs to handle that, e.g. b=
y sending a new offer with unique PT values.

IF we choose Alternative 2, we still need to decide whether we let the offe=
rer decide when it's "appropriate" when to use the same PT value, or whethe=
r we need to specify some rules (as suggested by Colin). My personal propos=
al is still to let the offerer decide, and not specify any rules.

Regards,

Christer









--_000_7594FB04B1934943A5C02806D1A2204B1D1C6336ESESSMB209erics_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D;mso-fareast-language:EN-US=
">Hi,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D;mso-fareast-language:EN-US=
"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D;mso-fareast-language:EN-US=
">Based on the discussions, we basically have two alternatives:<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D;mso-fareast-language:EN-US=
"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D;mso-fareast-language:EN=
-US">Alternative 1</span></b><span style=3D"font-size:11.0pt;font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D;mso-fareast-language=
:EN-US">:
 Forbid the usage of the same PT value within multiple m- lines.<o:p></o:p>=
</span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D;mso-fareast-language:EN-US=
"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D;mso-fareast-language:EN=
-US">Alternative 2</span></b><span style=3D"font-size:11.0pt;font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D;mso-fareast-language=
:EN-US">:
 Allow usage of the same PT value within multiple m- lines, and if the answ=
er does not support whatever extensions that are needed for the offerer to =
distinguish the media, the offer needs to handle that, e.g. by sending a ne=
w offer with unique PT values.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D;mso-fareast-language:EN-US=
"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D;mso-fareast-language:EN-US=
">IF we choose Alternative 2, we still need to decide whether we let the of=
ferer decide when it&#8217;s &#8220;appropriate&#8221; when to use the same
 PT value, or whether we need to specify some rules (as suggested by Colin)=
. My personal proposal is still to let the offerer decide, and not specify =
any rules.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D;mso-fareast-language:EN-US=
"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D;mso-fareast-language:EN-US=
">Regards,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D;mso-fareast-language:EN-US=
"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D;mso-fareast-language:EN-US=
">Christer<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D;mso-fareast-language:EN-US=
"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D;mso-fareast-language:EN-US=
"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D;mso-fareast-language:EN-US=
"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D;mso-fareast-language:EN-US=
"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D;mso-fareast-language:EN-US=
"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D;mso-fareast-language:EN-US=
"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D;mso-fareast-language:EN-US=
"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D;mso-fareast-language:EN-US=
"><o:p>&nbsp;</o:p></span></p>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B1D1C6336ESESSMB209erics_--


From nobody Mon Mar  3 05:21:00 2014
Return-Path: <Raju.Makaraju@alcatel-lucent.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 161A71A0105 for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 05:20:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.7
X-Spam-Level: 
X-Spam-Status: No, score=-5.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_14=0.6, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_HI=-5] autolearn=ham
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 GOC7tcsoVVyX for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 05:20:55 -0800 (PST)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id 8F0B41A00FD for <mmusic@ietf.org>; Mon,  3 Mar 2014 05:20:55 -0800 (PST)
Received: from us70tusmtp2.zam.alcatel-lucent.com (h135-5-2-64.lucent.com [135.5.2.64]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id s23DKjBu007303 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 3 Mar 2014 07:20:45 -0600 (CST)
Received: from US70TWXCHHUB04.zam.alcatel-lucent.com (us70twxchhub04.zam.alcatel-lucent.com [135.5.2.36]) by us70tusmtp2.zam.alcatel-lucent.com (GMO) with ESMTP id s23DKgmt003706 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 3 Mar 2014 08:20:44 -0500
Received: from US70UWXCHMBA02.zam.alcatel-lucent.com ([169.254.8.212]) by US70TWXCHHUB04.zam.alcatel-lucent.com ([135.5.2.36]) with mapi id 14.02.0247.003; Mon, 3 Mar 2014 08:20:42 -0500
From: "Makaraju, Maridi Raju (Raju)" <Raju.Makaraju@alcatel-lucent.com>
To: Christian Groves <Christian.Groves@nteczone.com>, Paul Kyzivat <pkyzivat@alum.mit.edu>, Christer Holmberg <christer.holmberg@ericsson.com>, Mary Barnes <mary.ietf.barnes@gmail.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: IETF#89: First version of CLUE Data Channel slide set.
Thread-Index: AQHPNW3bGiqdS9LZRZu/XRhtec89PJrM/r0AgADHGRCAAHIogP//rM2AgABip4D//7uAwIAAmK0A///L61AAEWDhaAAKMUzg
Date: Mon, 3 Mar 2014 13:20:42 +0000
Deferred-Delivery: Mon, 3 Mar 2014 13:20:00 +0000
Message-ID: <E1FE4C082A89A246A11D7F32A95A17826E004CCC@US70UWXCHMBA02.zam.alcatel-lucent.com>
References: <7594FB04B1934943A5C02806D1A2204B1D1C0E03@ESESSMB209.ericsson.se> <CAHBDyN75R1Wr5BODSQ9RNmNP9G7QZdOjZ9Lw+Vz3DCEUUYh4-Q@mail.gmail.com> <CAHBDyN5aDiJHy0fZ3=A8bLyCGAEhSojxu0_kAdLvOTykykE36Q@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1D1C2DF7@ESESSMB209.ericsson.se> <E1FE4C082A89A246A11D7F32A95A17826E003463@US70UWXCHMBA02.zam.alcatel-lucent.com> <7594FB04B1934943A5C02806D1A2204B1D1C3A97@ESESSMB209.ericsson.se> <E1FE4C082A89A246A11D7F32A95A17826E003836@US70UWXCHMBA02.zam.alcatel-lucent.com> <7594FB04B1934943A5C02806D1A2204B1D1C4C1F@ESESSMB209.ericsson.se> <E1FE4C082A89A246A11D7F32A95A17826E003961@US70UWXCHMBA02.zam.alcatel-lucent.com> <53139A10.1040502@alum.mit.edu> <E1FE4C082A89A246A11D7F32A95A17826E003DC8@US70UWXCHMBA02.zam.alcatel-lucent.com> <5313C778.2040105@alum.mit.edu> <5314293E.7090409@nteczone.com>
In-Reply-To: <5314293E.7090409@nteczone.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.5.27.18]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/x0S5gXrPzXTlDJoz8Lt6a2cPhiE
Cc: "DRAGE, Keith \(Keith\)" <keith.drage@alcatel-lucent.com>
Subject: Re: [MMUSIC] IETF#89: First version of CLUE Data Channel slide set.
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 13:20:59 -0000

IMHO, we should not just think about "low risk/resistance"=20
vs. "high risk" approach, rather do the right thing and select the=20
right approach to serve near and long term needs. The "risk" mentioned
wrt ejzak's adaption is completely within MMUSIC control and can be
managed IMHO. For this draft, besides CLUE, there are other strong use=20
cases to interwork existing subprotocols such as MSRP; no support=20
is needed for this draft from rtcweb (or from browsers)!

Issues summary:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
There are three issues that need to be addressed if DCEP is used:
a. How middle boxes know about the data channel streams (DCS)?
b. How to negotiate subprotocol properties per DCS?
c. How to select stream ids? Who initiates DC OPEN?
Issue (c) is relatively easy to handle by associating it to TLS role.
But actual TLS role is typically NOT available to the application.
Application need to determine the role by looking into a=3Dsetup.
(will it ever be different from the actual role used at DTLS layer?)

But issue (a) requires complex changes at media gateways, which are
questionable and probably not allowed with current architecture.
Issue (b) requires DCEP to make changes to allow exchange of=20
subprotocol properties as part of DC OPEN. Then media gateways
have to inform controllers of these properties as needed.

I understand that=20
- some implementations want to go with internal=20
- and others want to go with external negotiation;=20
- yet some others want to go with internal but want=20
  to negotiate stream ids and/or subprotocol properties=20
  externally.=20

To facilitate all these possibilities, I want to make=20
the following proposal.

PROPOSAL
=3D=3D=3D=3D=3D=3D=3D=3D
1. Use of DCEP only
   SDP offer does not have Ejzak's a=3Ddcmap, a=3Ddcsa
   This results in using DCEP. The applicaion is fully aware
   of the limitations, if any, and fine with them.
   Issue (c) need to be addressed explictly.

2. Use of DCEP only (essentially same as (1)).
   SDP offer has Ejzak's a=3Ddcmap, optionally a=3Ddcsa
   Answerer ignores a=3Ddcmap and a=3Ddcsa (per SDP rules)
   and won't include them in SDP answer.
   DCEP will be used.
  =20
3. External or DCEP negotiated, no subprotocol parameters=20
   SDP offer has Ejzak's a=3Ddcmap, optionally a=3Ddcsa
   A new parameter "protocol" will be added to a=3Ddcmap.
   protocol=3Dexternal (default) indicates offerer wants to use
   external negotiation for that stream; protocol=3Dinternal=20
   indicates DCEP. SDP answerer may decide just to use a=3Ddcmap=20
   to get stream id, subprotocol and changes 'protocol' parameter=20
   as needed and include it in SDP answer.
   a=3Ddcsa are ignored and not sent back in SDP answer.=20
   NOTE: if offer says "external" and answer selects "internal"
   then the previously created data channel, at offering side,
   with external negotiation (negotiated=3Dtrue in PeerConnection=20
   API case) has to be closed and has to be reopened with=20
   same stream id but with internal protocol(negotiated=3Dfalse).

4. External or DCEP negotiated, with subprotocol parameters=20
   SDP offer has Ejzak's a=3Ddcmap and a=3Ddcsa.
   External or DCEP is negotiated per (3).
   SDP answerer decides to use both dcmap and dcsa and=20
   echoes them back in SDP answer.

CLUE applications can go with any of the above 4 options=20
as they sees fit.

Thanks
Raju

> -----Original Message-----
> From: Christian Groves [mailto:Christian.Groves@nteczone.com]
> Sent: Monday, March 03, 2014 1:03 AM
> To: Paul Kyzivat; Makaraju, Maridi Raju (Raju); Christer Holmberg; Mary
> Barnes; mmusic@ietf.org
> Cc: Richard Ejzak; DRAGE, Keith (Keith); Liuyan (Scarlett)
> Subject: Re: IETF#89: First version of CLUE Data Channel slide set.
>=20
> I support Raju's comments. By not having an SDP approach to negotiate
> what protocol/s are being used  the SCTP association are going to
> complicate things for gateways that have to provide some interworking
> between endpoints.
> DCEP is useful for opening the SCTP streams but I don't see where the
> negotiation of what will go over the streams will take place in
> non-rtcweb systems?
>=20
> Regards, Christian
>=20
> On 3/03/2014 11:06 AM, Paul Kyzivat wrote:
> > I started out preferring an SDP approach (such as Richard's draft) for
> > negotiating the clue channel. But IMO *the* reason we are using SCTP
> > is to get interop with CLUE. (Otherwise we could just use TLS.)
> >
> > And at the moment going with DCEP appears to be the low risk approach
> > for us. With it we have fewer dependencies, and the ones we have are
> > on paths that will be well exercised in the short run. There is less
> > total stuff to implement, and it is sufficient for our needs. And it
> > will be the path of least resistance for getting an webrtc clue client
> > working.
> >
> > (I'm fairly confident that Simon will have one going sooner rather
> > than later. They already have prototypes of pieces, and we don't have
> > the specs done yet.)
> >
> >     Thanks,
> >     Paul
> >
> > On 3/2/14 11:00 PM, Makaraju, Maridi Raju (Raju) wrote:
> >> Comments inline.
> >>
> >>> From: Paul Kyzivat [mailto:pkyzivat@alum.mit.edu]
> >>> On 3/2/14 5:11 PM, Makaraju, Maridi Raju (Raju) wrote:
> >>>> + mmusic to cover some of the discussions.
> >>>>
> >>>> Hi,
> >>>>
> >>>> Please see comments inline.
> >>>>
> >>>> Hi,
> >>>>
> >>>> For the gateway use-case, do we really need to indicate the SCTP
> >>>> stream
> >>>> during Offer/Answer?
> >>>>
> >>>> Or, would it be enough if we indicate that the data channel is
> >>>> going to
> >>>> be used for CLUE, and the gateway then figures out which stream is
> >>>> used
> >>>> when it receives DCEP OPEN?
> >>>>
> >>>> */[Raju] This approach has 2 implications:/*
> >>>>
> >>>> */1./**//*The gateway needs to look at bearer packets and notify the
> >>>> signaling layer about the streams. Though possible, this is
> >>>> computationally intensive and new mechanism needed for such
> >>>> notification
> >>>> between bearer and signaling layers.
> >>>>
> >>>> Why does it need to inform the signalling layer about the streams? T=
he
> >>>> controller needs to tell the media gateway: "please let CLUE go
> >>>> through"
> >>>>
> >>>> */[Raju] "Please let CLUE through" is a simple scenario without much
> >>>> interworking and other needs./*
> [CNG] It's not about simply letting "CLUE go through." CLUE will need to
> be interworked/encodings updated etc depending on the gateway
> policy/capabilities.
> >>>>
> >>>> */I want to point out couple of other interworking scenarios:/*
> >>>>
> >>>> */1./*Lawful intercept (LI): A CLUE channel may have to be reported =
to
> >>>> LI agents per regulatory requirements. For various reasons such
> >>>> reporting may have to be interworked with non-data channel SCTP/dTLS
> >>>> transport (e.g. TCP).
> >>>
> >>> By explicit policy we don't consider lawful intercept in IETF.
> >>> The same issue exists for the RTP.
> >>
> >> [Raju] I understand LI is a very sensitive subject and by no means I
> >> am making any statements about it. My comment was providing one use
> >> case to which a service provider may be legally obligated to oblige.
> >>
> >> There are other cases that may require interworking at gateways.
> >>
> >>>
> >>>> */2./*For Non-LI reasons, a CLUE could be interworked to a TCP based
> >>>> transport in an end-to-access-edge kind of approach.
> >>>
> >>> ??? CLUE protocol over TCP? Why? Who will specify that? The intent
> >>> is to
> >>> use DTLS/SCTP based data channel even when no webrtc in use.
> >>>
> >>> Or do you mean interworking with some non-clue TP protocol?
> >> [Raju] I meant both. None of these are defined yet for CLUE. I am
> >> thinking of these future possibilities. If one approach allows these
> >> future possibilties with little overhead, my vote is to go with such
> >> approach.
> >> Also, as stated earlier such SDP framework makes it easy to negotiate
> >> subprotocol attributes which comes naturally with SDP and fits well
> >> with SDP based approach.
> [CNG] I agree.
> >>
> >> Thanks
> >> Raju
> >>
> >>
> >
> >


From nobody Mon Mar  3 05:27:58 2014
Return-Path: <Raju.Makaraju@alcatel-lucent.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 3B0111A0125 for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 05:27:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] autolearn=ham
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 UNkBW3BiiDXR for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 05:27:55 -0800 (PST)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by ietfa.amsl.com (Postfix) with ESMTP id A4C7F1A0117 for <mmusic@ietf.org>; Mon,  3 Mar 2014 05:27:55 -0800 (PST)
Received: from us70tusmtp2.zam.alcatel-lucent.com (h135-5-2-64.lucent.com [135.5.2.64]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id s23DOkCm008573 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 3 Mar 2014 07:24:46 -0600 (CST)
Received: from US70UWXCHHUB02.zam.alcatel-lucent.com (us70uwxchhub02.zam.alcatel-lucent.com [135.5.2.49]) by us70tusmtp2.zam.alcatel-lucent.com (GMO) with ESMTP id s23DOd0Z004865 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 3 Mar 2014 08:24:46 -0500
Received: from US70UWXCHMBA02.zam.alcatel-lucent.com ([169.254.8.212]) by US70UWXCHHUB02.zam.alcatel-lucent.com ([135.5.2.49]) with mapi id 14.02.0247.003; Mon, 3 Mar 2014 08:24:39 -0500
From: "Makaraju, Maridi Raju (Raju)" <Raju.Makaraju@alcatel-lucent.com>
To: Harald Alvestrand <harald@alvestrand.no>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] Lawful intercept - don't (Re: IETF#89: First version of CLUE Data Channel slide set.)
Thread-Index: AQHPNuPtojrwWNrIz0u/GKnujYzdjw==
Date: Mon, 3 Mar 2014 13:24:38 +0000
Message-ID: <E1FE4C082A89A246A11D7F32A95A17826E004D0E@US70UWXCHMBA02.zam.alcatel-lucent.com>
References: <7594FB04B1934943A5C02806D1A2204B1D1C0E03@ESESSMB209.ericsson.se> <CAHBDyN75R1Wr5BODSQ9RNmNP9G7QZdOjZ9Lw+Vz3DCEUUYh4-Q@mail.gmail.com> <CAHBDyN5aDiJHy0fZ3=A8bLyCGAEhSojxu0_kAdLvOTykykE36Q@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1D1C2DF7@ESESSMB209.ericsson.se> <E1FE4C082A89A246A11D7F32A95A17826E003463@US70UWXCHMBA02.zam.alcatel-lucent.com> <7594FB04B1934943A5C02806D1A2204B1D1C3A97@ESESSMB209.ericsson.se> <E1FE4C082A89A246A11D7F32A95A17826E003836@US70UWXCHMBA02.zam.alcatel-lucent.com> <7594FB04B1934943A5C02806D1A2204B1D1C4C1F@ESESSMB209.ericsson.se> <E1FE4C082A89A246A11D7F32A95A17826E003961@US70UWXCHMBA02.zam.alcatel-lucent.com> <53139A10.1040502@alum.mit.edu> <E1FE4C082A89A246A11D7F32A95A17826E003DC8@US70UWXCHMBA02.zam.alcatel-lucent.com> <5314404D.5070500@alvestrand.no>
In-Reply-To: <5314404D.5070500@alvestrand.no>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.5.27.18]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/7_Mf31B7D5CgGJVQLPAboTUz7Xw
Subject: Re: [MMUSIC] Lawful intercept - don't (Re: IETF#89: First version of CLUE Data Channel slide set.)
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 13:27:57 -0000

> From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Harald Alvestr=
and
> Sent: Monday, March 03, 2014 2:42 AM

> On 03/03/2014 12:00 AM, Makaraju, Maridi Raju (Raju) wrote:
> >>> > > */1./*Lawful intercept (LI): A CLUE channel may have to be report=
ed
> to
> >>> > > LI agents per regulatory requirements. For various reasons such
> >>> > > reporting may have to be interworked with non-data channel SCTP/d=
TLS
> >>> > > transport (e.g. TCP).
> >> >
> >> > By explicit policy we don't consider lawful intercept in IETF.
> >> > The same issue exists for the RTP.
> > [Raju] I understand LI is a very sensitive subject and by no means I am
> making any statements about it. My comment was providing one use case to
> which a service provider may be legally obligated to oblige.
> >
> > There are other cases that may require interworking at gateways.
> >
>=20
> When stating the use case, just say that one of the participants in a
> CLUE channel (including the gateway) may choose to share the content (or
> the existence of the channel - I can't tell which you mean by "report"
> here) with a third party.

[Raju] Both (existence/control, content) are possible with various levels o=
f "reporting".

>=20
> There are lots of reasons why someone may choose to do that, including,
> for instance, the requirement for recording financial advice given over
> the phone in many countries, and calling out legal intercept is just
> going to generate lots of heat but little light.

[Raju] Thanks for providing a non-controversial use case! :-)

Thanks
Raju


From nobody Mon Mar  3 05:40:33 2014
Return-Path: <juberti@google.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 9E10E1A0174 for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 05:40:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.625
X-Spam-Level: 
X-Spam-Status: No, score=-1.625 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.547, 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 qTASEaGqQLtX for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 05:40:29 -0800 (PST)
Received: from mail-ve0-x229.google.com (mail-ve0-x229.google.com [IPv6:2607:f8b0:400c:c01::229]) by ietfa.amsl.com (Postfix) with ESMTP id C6F571A0171 for <mmusic@ietf.org>; Mon,  3 Mar 2014 05:40:28 -0800 (PST)
Received: by mail-ve0-f169.google.com with SMTP id pa12so3741469veb.28 for <mmusic@ietf.org>; Mon, 03 Mar 2014 05:40:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=RmMWo5QV85//YvUPTfCOdNNSkjSQJFZvB2jnQj/BaAI=; b=mlOXw/szVEPaM2GjjAXSpRU+JoLgsJMF/tRv9AnLNwMtkBuUrfpfrEJipTGnbHt8dv 3kquJ6Kp12BQ8R9vLJyxO1BpZr1IPrRCn6s+HMt8FGWESfh6WDjtL02uqyVtuhYCGhQ0 RL5jQTEC9FERXEYJFXGJNo1d8P/x8goRRJvKJfRUkMofvX3ZNMf+3HWw1qlUd8fKwfU3 SVsproGyqQRneDqURNjA/n05wxv/yeZ9I/J7TfnyE0sptz3ea7+RyAtylIW8USsLj0bf LXMrd1AKSi2PbmPXHbxTkXKUco7a9Ql9ec10PaP2q4PuRHyZnmXT/gObNgrL1MIN17yz yZLw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=RmMWo5QV85//YvUPTfCOdNNSkjSQJFZvB2jnQj/BaAI=; b=ai6gXQWSTIem7yYBsVVk3R/IAi/AzPycTgteGOlT0lt91BMjGAB49wtJH0QSlgooq6 vgeeI/cykwTpgR6UBLXTFmBcu5kflkYRE4RA1dMIf2hodX6zXDHxq4Rg8EFDMWj5Omnk LWAxd/vbZRiZb5tCUn7VlqwjME2Yjpa8UBRU7KpQvHfMJ7+E7IhMjK+/52y/a4zbGx3y 0Ct2neUi5kILdXEcUDUjZlQQyq9nwkQnoPxrmN4uRGLM+23t7St7SSgLG/Rag3AGkgR+ mtdSwT1kExAnLR3mxo1D9lzI7WqHyse1D2CCEi04DR3M6JNGB+5mE8Aq/EeRFeqTQW+x i6BQ==
X-Gm-Message-State: ALoCoQkF3AznM9vQNwRUVEpl8BqcRUSz4Z2ldwJMTpoQGn4It4l0gyM13B7YF6KrKGP8A1A4+Nxb5e1jL/+ezsVYT7ejN9Jh9V7ewIg0IRQcLkRkhUc/sJcstPDOaJPeTZbJhrO5rc+dAXpIsn9h+FGuth8Mys1eccYRjOXYh6hvWE/8p86LSVdVeU6vjpxO0ICJsYYvVKRo
X-Received: by 10.52.165.237 with SMTP id zb13mr22144vdb.76.1393854025712; Mon, 03 Mar 2014 05:40:25 -0800 (PST)
MIME-Version: 1.0
Received: by 10.52.89.170 with HTTP; Mon, 3 Mar 2014 05:40:05 -0800 (PST)
In-Reply-To: <5310A120.4@ericsson.com>
References: <526147C3.9040204@ericsson.com> <CAPvvaa+8osKGTNCS6RJywS9Bmf+RdbnChN=XqA9d+gLnBBAGow@mail.gmail.com> <5261704B.9090307@nostrum.com> <CAOJ7v-0dFsd1jxkaMMMAx36ezLex7tTWvy8XnDS8Ak26roz8Xw@mail.gmail.com> <5310A120.4@ericsson.com>
From: Justin Uberti <juberti@google.com>
Date: Mon, 3 Mar 2014 05:40:05 -0800
Message-ID: <CAOJ7v-0nZ+BOZS_mqYWO-7ULRT_XiymSUm21M15bS1vWLeMJdg@mail.gmail.com>
To: =?UTF-8?B?QXJpIEtlcsOkbmVu?= <ari.keranen@ericsson.com>
Content-Type: multipart/alternative; boundary=001a11c24e7412647f04f3b3eef4
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/fQ5vbtJXpFHwRu44dV9qYd8-A4Y
Cc: mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] ICE-bis: pacing of ICE connectivity checks
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 13:40:31 -0000

--001a11c24e7412647f04f3b3eef4
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Sorry, I didn't read this until now. I can check with the team when I get
back and see when we could have some numbers to share.


On Fri, Feb 28, 2014 at 6:45 AM, Ari Ker=C3=A4nen <ari.keranen@ericsson.com=
>wrote:

> Hi Justin,
>
> We discussed this issue at the previous IETF meeting and back then you
> were doing large scale measurements with Chrome on the sensible
> connectivity check values. Did you come into some conclusions with those
> studies? Anything new we could recommend based on the results?
>
>
> Cheers,
> Ari
>
>
> On 18/10/13 21:34, Justin Uberti wrote:
>
>> FWIW, we are now doing trials to understand what is the absolute lower
>> bound for ICE checks on today's internet (i.e. what is the minimum time
>> to allow for a NAT to create a new UDP binding).
>>
>>
>> On Fri, Oct 18, 2013 at 10:30 AM, Adam Roach <adam@nostrum.com
>> <mailto:adam@nostrum.com>> wrote:
>>
>>     On 10/18/13 09:44, Emil Ivov wrote:
>>
>>>     It might be worth reminding exactly what these 50ms would be
>>>     protecting us against
>>>
>>
>>     They're protecting us against RTP arriving at a rate of 20ms per
>> packet.
>>
>>
>>      and why is it that we don't need to be
>>>     protected against it in the case of RTP where 20ms is accepted as a
>>>     fine default value.
>>>
>>
>>     Well, it's not. This is exactly why we ended up requiring ICE: it
>>     ensures explicit consent before you start blowing media at someone.
>>
>>     See also
>>     http://www.ietf.org/mail-archive/web/mmusic/current/msg04589.html
>>
>>     /a
>>
>>     _______________________________________________
>>     mmusic mailing list
>>     mmusic@ietf.org <mailto:mmusic@ietf.org>
>>     https://www.ietf.org/mailman/listinfo/mmusic
>>
>>
>>
>>
>>
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www.ietf.org/mailman/listinfo/mmusic
>>
>>
>

--001a11c24e7412647f04f3b3eef4
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Sorry, I didn&#39;t read this until now. I can check with =
the team when I get back and see when we could have some numbers to share.<=
/div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Fri, =
Feb 28, 2014 at 6:45 AM, Ari Ker=C3=A4nen <span dir=3D"ltr">&lt;<a href=3D"=
mailto:ari.keranen@ericsson.com" target=3D"_blank">ari.keranen@ericsson.com=
</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Hi Justin,<br>
<br>
We discussed this issue at the previous IETF meeting and back then you were=
 doing large scale measurements with Chrome on the sensible connectivity ch=
eck values. Did you come into some conclusions with those studies? Anything=
 new we could recommend based on the results?<br>


<br>
<br>
Cheers,<br>
Ari<div class=3D""><br>
<br>
On 18/10/13 21:34, Justin Uberti wrote:<br>
</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex"><div class=3D"">
FWIW, we are now doing trials to understand what is the absolute lower<br>
bound for ICE checks on today&#39;s internet (i.e. what is the minimum time=
<br>
to allow for a NAT to create a new UDP binding).<br>
<br>
<br>
On Fri, Oct 18, 2013 at 10:30 AM, Adam Roach &lt;<a href=3D"mailto:adam@nos=
trum.com" target=3D"_blank">adam@nostrum.com</a><br></div><div class=3D"">
&lt;mailto:<a href=3D"mailto:adam@nostrum.com" target=3D"_blank">adam@nostr=
um.com</a>&gt;&gt; wrote:<br>
<br>
=C2=A0 =C2=A0 On 10/18/13 09:44, Emil Ivov wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
=C2=A0 =C2=A0 It might be worth reminding exactly what these 50ms would be<=
br>
=C2=A0 =C2=A0 protecting us against<br>
</blockquote>
<br>
=C2=A0 =C2=A0 They&#39;re protecting us against RTP arriving at a rate of 2=
0ms per packet.<br>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
=C2=A0 =C2=A0 and why is it that we don&#39;t need to be<br>
=C2=A0 =C2=A0 protected against it in the case of RTP where 20ms is accepte=
d as a<br>
=C2=A0 =C2=A0 fine default value.<br>
</blockquote>
<br>
=C2=A0 =C2=A0 Well, it&#39;s not. This is exactly why we ended up requiring=
 ICE: it<br>
=C2=A0 =C2=A0 ensures explicit consent before you start blowing media at so=
meone.<br>
<br>
=C2=A0 =C2=A0 See also<br>
=C2=A0 =C2=A0 <a href=3D"http://www.ietf.org/mail-archive/web/mmusic/curren=
t/msg04589.html" target=3D"_blank">http://www.ietf.org/mail-<u></u>archive/=
web/mmusic/current/<u></u>msg04589.html</a><br>
<br>
=C2=A0 =C2=A0 /a<br>
<br>
=C2=A0 =C2=A0 ______________________________<u></u>_________________<br>
=C2=A0 =C2=A0 mmusic mailing list<br></div>
=C2=A0 =C2=A0 <a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@i=
etf.org</a> &lt;mailto:<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank"=
>mmusic@ietf.org</a>&gt;<br>
=C2=A0 =C2=A0 <a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" targ=
et=3D"_blank">https://www.ietf.org/mailman/<u></u>listinfo/mmusic</a><div c=
lass=3D""><br>
<br>
<br>
<br>
<br>
______________________________<u></u>_________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" target=3D"_blank">=
https://www.ietf.org/mailman/<u></u>listinfo/mmusic</a><br>
<br>
</div></blockquote>
<br>
</blockquote></div><br></div>

--001a11c24e7412647f04f3b3eef4--


From nobody Mon Mar  3 05:55:34 2014
Return-Path: <ari.keranen@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 3DC8B1A00FE for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 05:55:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.601
X-Spam-Level: 
X-Spam-Status: No, score=-1.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, 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 Qx3duM9XQ9Io for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 05:55:32 -0800 (PST)
Received: from sesbmg20.ericsson.net (sesbmg20.ericsson.net [193.180.251.56]) by ietfa.amsl.com (Postfix) with ESMTP id 8E58B1A0114 for <mmusic@ietf.org>; Mon,  3 Mar 2014 05:55:31 -0800 (PST)
X-AuditID: c1b4fb38-b7f418e000001099-7c-531489cfc4b4
Received: from ESESSHC017.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg20.ericsson.net (Symantec Mail Security) with SMTP id 7E.E4.04249.FC984135; Mon,  3 Mar 2014 14:55:28 +0100 (CET)
Received: from mail.lmf.ericsson.se (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.71) with Microsoft SMTP Server id 14.2.347.0; Mon, 3 Mar 2014 14:55:27 +0100
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se [131.160.33.3])	by mail.lmf.ericsson.se (Postfix) with ESMTP id AE7631101F4; Mon,  3 Mar 2014 15:55:27 +0200 (EET)
Received: from nomadiclab.lmf.ericsson.se (localhost [127.0.0.1])	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 99D4756B4B;	Mon,  3 Mar 2014 15:55:22 +0200 (EET)
Received: from dhcp-bbf0.meeting.ietf.org (localhost [127.0.0.1])	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 3EDF356B4A;	Mon,  3 Mar 2014 15:55:22 +0200 (EET)
Message-ID: <531489CF.9020607@ericsson.com>
Date: Mon, 3 Mar 2014 13:55:27 +0000
From: =?UTF-8?B?QXJpIEtlcsOkbmVu?= <ari.keranen@ericsson.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Justin Uberti <juberti@google.com>
References: <526147C3.9040204@ericsson.com> <CAPvvaa+8osKGTNCS6RJywS9Bmf+RdbnChN=XqA9d+gLnBBAGow@mail.gmail.com> <5261704B.9090307@nostrum.com> <CAOJ7v-0dFsd1jxkaMMMAx36ezLex7tTWvy8XnDS8Ak26roz8Xw@mail.gmail.com> <5310A120.4@ericsson.com> <CAOJ7v-0nZ+BOZS_mqYWO-7ULRT_XiymSUm21M15bS1vWLeMJdg@mail.gmail.com>
In-Reply-To: <CAOJ7v-0nZ+BOZS_mqYWO-7ULRT_XiymSUm21M15bS1vWLeMJdg@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format=flowed
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrOLMWRmVeSWpSXmKPExsUyM+Jvje6FTpFggw2v+Sy2ThWymLr8MYsD k8eCTaUeS5b8ZApgiuKySUnNySxLLdK3S+DK6L59m6Vgs2jF/ONbWRsYb/J1MXJySAiYSJzf u4gZwhaTuHBvPRuILSRwhFFi5kLFLkYuIHs9o8TzmwdZIZw9jBIbN5xgh3DWMkpcfNTFCOfs 3vgIrJ9XQFvi2I4N7CA2i4CKxLGuY2BxNgFbidWvbrKA2KICyRI3v3+GqheUODnzCVhcREBN 4uGsXawgNrOAjMSMs41MILawgIPE8zfroDZvZpK493UZI0iCUyBQYnHTa3aIBguJxW8OQtny Es1bZ0M9pyZx9dwmZojnVCWu/nvFOIFRdBaS3bOQtM9C0r6AkXkVI0dxanFSbrqRwSZGYOAf 3PLbYgfj5b82hxilOViUxHk/vnUOEhJITyxJzU5NLUgtii8qzUktPsTIxMEp1cDYX5p3bULo 3PBL19aLq+RqPIpVF2GadktwQVC+ln/H3dn6b6+v2aGq2f2W5fKBXqNtqcvNS6fEce9zv+le 2KA4ca3N/SVXU0z3VrtzX47YdMVrRmfs3FcH9nyfc1nu8Ibtd/ZXrf/6Y868j6UXV6usefDC 7Mb7V/8PrPbpX/Y+4LTZl3Oi36a89lNiKc5INNRiLipOBAAnCNThSgIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/reFGBH60qZ5rZo-D5dMUmXT3J1g
Cc: mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] ICE-bis: pacing of ICE connectivity checks
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 13:55:33 -0000

That would be great! Thanks Justin.


Cheers,
Ari

On 3/3/14 1:40 PM, Justin Uberti wrote:
> Sorry, I didn't read this until now. I can check with the team when I
> get back and see when we could have some numbers to share.
>
>
> On Fri, Feb 28, 2014 at 6:45 AM, Ari KerÃ¤nen <ari.keranen@ericsson.com
> <mailto:ari.keranen@ericsson.com>> wrote:
>
>     Hi Justin,
>
>     We discussed this issue at the previous IETF meeting and back then
>     you were doing large scale measurements with Chrome on the sensible
>     connectivity check values. Did you come into some conclusions with
>     those studies? Anything new we could recommend based on the results?
>
>
>     Cheers,
>     Ari
>
>
>     On 18/10/13 21:34, Justin Uberti wrote:
>
>         FWIW, we are now doing trials to understand what is the absolute
>         lower
>         bound for ICE checks on today's internet (i.e. what is the
>         minimum time
>         to allow for a NAT to create a new UDP binding).
>
>
>         On Fri, Oct 18, 2013 at 10:30 AM, Adam Roach <adam@nostrum.com
>         <mailto:adam@nostrum.com>
>         <mailto:adam@nostrum.com <mailto:adam@nostrum.com>>> wrote:
>
>              On 10/18/13 09:44, Emil Ivov wrote:
>
>                  It might be worth reminding exactly what these 50ms
>             would be
>                  protecting us against
>
>
>              They're protecting us against RTP arriving at a rate of
>         20ms per packet.
>
>
>                  and why is it that we don't need to be
>                  protected against it in the case of RTP where 20ms is
>             accepted as a
>                  fine default value.
>
>
>              Well, it's not. This is exactly why we ended up requiring
>         ICE: it
>              ensures explicit consent before you start blowing media at
>         someone.
>
>              See also
>         http://www.ietf.org/mail-__archive/web/mmusic/current/__msg04589.html
>         <http://www.ietf.org/mail-archive/web/mmusic/current/msg04589.html>
>
>              /a
>
>              _________________________________________________
>              mmusic mailing list
>         mmusic@ietf.org <mailto:mmusic@ietf.org> <mailto:mmusic@ietf.org
>         <mailto:mmusic@ietf.org>>
>         https://www.ietf.org/mailman/__listinfo/mmusic
>         <https://www.ietf.org/mailman/listinfo/mmusic>
>
>
>
>
>
>         _________________________________________________
>         mmusic mailing list
>         mmusic@ietf.org <mailto:mmusic@ietf.org>
>         https://www.ietf.org/mailman/__listinfo/mmusic
>         <https://www.ietf.org/mailman/listinfo/mmusic>
>
>
>


From nobody Mon Mar  3 06:01:06 2014
Return-Path: <suhasietf@gmail.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 955191A0112 for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 06:01:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.799
X-Spam-Level: 
X-Spam-Status: No, score=-0.799 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_14=0.6, J_CHICKENPOX_15=0.6, 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 ZvnZgveMjyLy for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 06:01:00 -0800 (PST)
Received: from mail-we0-x234.google.com (mail-we0-x234.google.com [IPv6:2a00:1450:400c:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id 634441A0117 for <mmusic@ietf.org>; Mon,  3 Mar 2014 06:00:57 -0800 (PST)
Received: by mail-we0-f180.google.com with SMTP id p61so2058325wes.39 for <mmusic@ietf.org>; Mon, 03 Mar 2014 06:00:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=LhUTyzWVkM74bHxdL+Rndqe9mgb2gdh2+2/2RJpxGsY=; b=fngUeuEZKVtS869O5ibtxTZvkV4gHkYYPE6I25D//wKcBtcSNE+AioliJnpAZl2kR5 qUggXRXSEkQu3eLa4U7llLIe42jqYa54vl8qO+EuxwmnUjkfjoauxNmGuTzmNC/TdNQk bgx/wr5UcT/frp2q7ir+K6Tgz4Kx+BfLD05F9WN2wkID6bFqLkRkx5wSDvXZEmxvS7a0 FnT93zxkRrc/GnsEO4rSIWGZXPcAd0JmSfSn60xqJjfYis224u9TZISyPFsJ18qCDyJd +QVBlEtjr260jNnViGuqOn8BxruvnG7ejYxW2ym9bV5+iH2+GeufcK2DCINE3fd9tV2i i1pw==
MIME-Version: 1.0
X-Received: by 10.195.13.17 with SMTP id eu17mr18285708wjd.24.1393855254123; Mon, 03 Mar 2014 06:00:54 -0800 (PST)
Received: by 10.195.12.134 with HTTP; Mon, 3 Mar 2014 06:00:54 -0800 (PST)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D1C6336@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D1C6336@ESESSMB209.ericsson.se>
Date: Mon, 3 Mar 2014 14:00:54 +0000
Message-ID: <CAMRcRGRu_BHBvNH8D+CgeEj9RUXiw-0fHj2UuGqhT7HUG=pJxw@mail.gmail.com>
From: Suhas Nandakumar <suhasietf@gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary=047d7bd91a7a4a5a1004f3b437e5
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/El7p8nW5yr_t91NZrltcxDSsr5A
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for allowing usage of the same PT value within multiple m- lines? - A new take.
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 14:01:02 -0000

--047d7bd91a7a4a5a1004f3b437e5
Content-Type: text/plain; charset=ISO-8859-1

Hello Christer

  A small twist on your proposal

  I think the recommendation in the BUNDLE document should say 2 points

  1. Reuse of PT is allowed only in the cases where the end-point is able
to uniquely map the incoming RTP Streams to its corresponding m=line. The
specific mechanisms to do so are out of the scope of this document .
Informally, SSRC, AppID or similar stream correlators can be used.

Also using the same PT across multiple m=lines implies the same underlying
codec configuration.

  2. Otherwise, reuse of PT across multiple m=lines MUST NOT be performed
while multiplexing.

We can add example for either if needed


Any thoughts

Thanks
Suhas


On Mon, Mar 3, 2014 at 1:17 PM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

>  Hi,
>
>
>
> Based on the discussions, we basically have two alternatives:
>
>
>
> *Alternative 1*: Forbid the usage of the same PT value within multiple m-
> lines.
>
>
>
> *Alternative 2*: Allow usage of the same PT value within multiple m-
> lines, and if the answer does not support whatever extensions that are
> needed for the offerer to distinguish the media, the offer needs to handle
> that, e.g. by sending a new offer with unique PT values.
>
>
>
> IF we choose Alternative 2, we still need to decide whether we let the
> offerer decide when it's "appropriate" when to use the same PT value, or
> whether we need to specify some rules (as suggested by Colin). My personal
> proposal is still to let the offerer decide, and not specify any rules.
>
>
>
> Regards,
>
>
>
> Christer
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>
>

--047d7bd91a7a4a5a1004f3b437e5
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hello Christer<div><br></div><div>&nbsp; A small twist on =
your proposal</div><div><br></div><div>&nbsp; I think the recommendation in=
 the BUNDLE document should say 2 points</div><div>&nbsp;&nbsp;</div><div>&=
nbsp; 1. Reuse of PT is allowed only in the cases where the end-point is ab=
le to uniquely map the incoming RTP Streams to its corresponding m=3Dline. =
The specific mechanisms to do so are out of the scope of this document . In=
formally, SSRC, AppID or similar stream correlators can be used.</div>
<div>&nbsp;</div><div>Also using the same PT across multiple m=3Dlines impl=
ies the same underlying codec configuration.</div><div><br></div><div>&nbsp=
; 2. Otherwise, reuse of PT across multiple m=3Dlines MUST NOT be performed=
 while multiplexing.</div>
<div><br></div><div>We can add example for either if needed</div><div><br><=
/div><div><br></div><div>Any thoughts&nbsp;</div><div><br></div><div>Thanks=
</div><div>Suhas</div></div><div class=3D"gmail_extra"><br><br><div class=
=3D"gmail_quote">
On Mon, Mar 3, 2014 at 1:17 PM, Christer Holmberg <span dir=3D"ltr">&lt;<a =
href=3D"mailto:christer.holmberg@ericsson.com" target=3D"_blank">christer.h=
olmberg@ericsson.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex=
">






<div lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Hi,<u></u><u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>&nbsp;<u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Based on the discussions,=
 we basically have two alternatives:<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>&nbsp;<u></u></spa=
n></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Alternative 1</span></=
b><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;san=
s-serif&quot;;color:#1f497d">:
 Forbid the usage of the same PT value within multiple m- lines.<u></u><u><=
/u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>&nbsp;<u></u></spa=
n></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Alternative 2</span></=
b><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;san=
s-serif&quot;;color:#1f497d">:
 Allow usage of the same PT value within multiple m- lines, and if the answ=
er does not support whatever extensions that are needed for the offerer to =
distinguish the media, the offer needs to handle that, e.g. by sending a ne=
w offer with unique PT values.<u></u><u></u></span></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>&nbsp;<u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">IF we choose Alternative =
2, we still need to decide whether we let the offerer decide when it&rsquo;=
s &ldquo;appropriate&rdquo; when to use the same
 PT value, or whether we need to specify some rules (as suggested by Colin)=
. My personal proposal is still to let the offerer decide, and not specify =
any rules.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>&nbsp;<u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Regards,<span class=3D"HO=
EnZb"><font color=3D"#888888"><u></u><u></u></font></span></span></p><span =
class=3D"HOEnZb"><font color=3D"#888888">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>&nbsp;<u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Christer<u></u><u></u></s=
pan></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>&nbsp;<u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>&nbsp;<u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>&nbsp;<u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>&nbsp;<u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>&nbsp;<u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>&nbsp;<u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>&nbsp;<u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>&nbsp;<u></u></spa=
n></p>
</font></span></div>
</div>

<br>_______________________________________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/mmusic</a><br>
<br></blockquote></div><br></div>

--047d7bd91a7a4a5a1004f3b437e5--


From nobody Mon Mar  3 06:07:17 2014
Return-Path: <pkyzivat@alum.mit.edu>
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 A7CD11A017C for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 06:07:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] 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 B3plZkE6OPHZ for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 06:07:15 -0800 (PST)
Received: from qmta09.westchester.pa.mail.comcast.net (qmta09.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:96]) by ietfa.amsl.com (Postfix) with ESMTP id E8C481A015F for <mmusic@ietf.org>; Mon,  3 Mar 2014 06:07:14 -0800 (PST)
Received: from omta03.westchester.pa.mail.comcast.net ([76.96.62.27]) by qmta09.westchester.pa.mail.comcast.net with comcast id Z1LE1n0020bG4ec5927CKK; Mon, 03 Mar 2014 14:07:12 +0000
Received: from dhcp-a45e.meeting.ietf.org ([31.133.164.94]) by omta03.westchester.pa.mail.comcast.net with comcast id Z2531n00G22X6kn3P2550M; Mon, 03 Mar 2014 14:05:10 +0000
Message-ID: <53148C0F.4090806@alum.mit.edu>
Date: Mon, 03 Mar 2014 14:05:03 +0000
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: mmusic@ietf.org
References: <7594FB04B1934943A5C02806D1A2204B1D1C368D@ESESSMB209.ericsson.se> <7A9A37FB-196F-4F79-805B-95CE9B67C344@csperkins.org>
In-Reply-To: <7A9A37FB-196F-4F79-805B-95CE9B67C344@csperkins.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1393855632; bh=vaQb/8dfgZGdkVJ3LccSKvPFiu8goPedkOqExlnvWn8=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=ZJwoPnXrkbadS+QR/Vkdj7GLd6pNnONRema0adx3qDqaZxkXtdlYWA6S9cOkdaUla MvNjgCpiBl692lyO768SnyeNvacCCb9NVFUmitYWJriwP7xqxbN/8StDt1iIM35VEz qZn3Y8TckEkc0azgk2pyGYcyHI60knAkqKJQY9Is8JDcsPoTpcD4WBGwiM/Mo/3NPq oNufxbp67CdMXyxxodAY4Imd5AlRx/dtlldZCPthfWmLWUGUQX3sVVYOS2tTZK1Yh6 Hek/K7KXWpVy/xlr4jBXBLosZeenxn9MNfE4are4+jW+OJBt7fNSPtlvgnwnjCGCrv xU/lNguXCPQNA==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/N0T1JW1cxcBKQ-6LVmtU8I2z5Wo
Subject: Re: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for allowing usage of the same PT value within multiple m- lines?
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 14:07:16 -0000

The general case is that when the sender is sending a packet, it must 
have *one* particular m-line in the bundle that it intends the packet to 
be associated with. When the receiver receives a packet, it must, based 
on info received in the packet, or prior packets, be able associate the 
packet with *one* particular m-line. It is an error if the sender don't 
agree on which m-line is intended.

(There is an exception for RTCP, which doesn't have to be associated 
with particular m-lines.)

My thought has been that the O/A should only succeed if there is 
agreement between the two sides about how to classify packets, 
sufficient to ensure that all packets will be consistently classified.

	Thanks,
	Paul

On 3/3/14 9:33 AM, Colin Perkins wrote:
> Christer,
>
> The bundled m= lines form a single RTP session. That means that they
> share a single RTP payload number space. The rule therefore has to be
> that you can only reuse the payload type across bundled m= lines if it
> refers to the exact same configuration of the exact same codec in all
> cases, where “exact same configuration” means that the a=fmtp: line and
> all other SDP attributes that configure the codec and packetisation of
> the media are identical.
>
> If that’s not specific enough, then MUST NOT reuse payload types across
> m= lines in a bundled group is the safe choice. I believe your propose
> that it’s okay if you can handle the media is too vague, and will cause
> us problems down the line.
>
> Colin
>
>
>
>
> On 2 Mar 2014, at 08:44, Christer Holmberg
> <christer.holmberg@ericsson.com <mailto:christer.holmberg@ericsson.com>>
> wrote:
>>
>> Hi,
>>
>> One of the open issues we have in BUNDLE, is when it is allowed to use
>> the same PT value within multiple m- lines.
>>
>> We tried to come up with different criteria, including a “codec
>> configuration” concept, but we never managed to agree on something.
>>
>> So, in London, I intend to suggest that we simply say: if you offer
>> the same PT value within multiple m- line, make sure you can handle
>> the associated media when it arrives – period (keep in mind that you
>> always indicate what you want to RECEIVE – the remote peer can still
>> ask you to SEND using different PT values).
>>
>> If you don’t like this, please provide an alternative solution,
>> because I want to close this issue in London. There is no idea to keep
>> “taking the issue back to the list”. We’ve done that for a few
>> meetings already.
>>
>> Regards,
>>
>> Christer
>>
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org <mailto:mmusic@ietf.org>
>> https://www.ietf.org/mailman/listinfo/mmusic
>
>
>
> --
> Colin Perkins
> http://csperkins.org/
>
>
>
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>


From nobody Mon Mar  3 06:27:22 2014
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 E52F31A0126 for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 06:27:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.039
X-Spam-Level: 
X-Spam-Status: No, score=-0.039 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, HOST_MISMATCH_NET=0.311, HTML_MESSAGE=0.001, J_CHICKENPOX_14=0.6, J_CHICKENPOX_15=0.6, 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 Y9yrPjJ0SKdp for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 06:27:19 -0800 (PST)
Received: from sessmg20.mgmt.ericsson.se (sessmg20.ericsson.net [193.180.251.50]) by ietfa.amsl.com (Postfix) with ESMTP id 9BDEB1A0017 for <mmusic@ietf.org>; Mon,  3 Mar 2014 06:27:18 -0800 (PST)
X-AuditID: c1b4fb32-b7f4c8e0000012f5-a6-5314914282a4
Received: from ESESSHC024.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg20.mgmt.ericsson.se (Symantec Mail Security) with SMTP id 5A.CC.04853.24194135; Mon,  3 Mar 2014 15:27:15 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.216]) by ESESSHC024.ericsson.se ([153.88.183.90]) with mapi id 14.02.0387.000; Mon, 3 Mar 2014 15:27:14 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Suhas Nandakumar <suhasietf@gmail.com>
Thread-Topic: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for allowing usage of the same PT value within multiple m- lines? - A new take.
Thread-Index: Ac824vtSFLJVCI5rSOGVBTMx34MhTf//+0EA///oubA=
Date: Mon, 3 Mar 2014 14:27:13 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D1C654F@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D1C6336@ESESSMB209.ericsson.se> <CAMRcRGRu_BHBvNH8D+CgeEj9RUXiw-0fHj2UuGqhT7HUG=pJxw@mail.gmail.com>
In-Reply-To: <CAMRcRGRu_BHBvNH8D+CgeEj9RUXiw-0fHj2UuGqhT7HUG=pJxw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.148]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1D1C654FESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrBLMWRmVeSWpSXmKPExsUyM+Jvja7zRJFggyenmCymLn/MYrFzbgez A5PHzll32T2WLPnJFMAUxWWTkpqTWZZapG+XwJWx9G4jW8E244qWt0dZGxgP6nYxcnJICJhI nOw6zQhhi0lcuLeerYuRi0NI4ASjxPFD06GcxYwSs2/PZu1i5OBgE7CQ6P6nDdIgIqAlsXrx XCaQMLOAusTVxUEg5cICkxgljq2exAriiAhMZpTYefI5G0SDlUTP7jUsIDaLgIpEx8wfYDav gK/EpXVfWSCWTWGUON+/gwkkwSkQKNE1bReYzQh03vdTa8BsZgFxiVtP5jNBnC0gsWTPeWYI W1Ti5eN/rBC2kkTjkiesEPX5Ei+3fmCCWCYocXLmE5YJjKKzkIyahaRsFpIyiLiOxILdn9gg bG2JZQtfM8PYZw48ZkIWX8DIvopRsji1uDg33chALzc9t0QvtSgzubg4P0+vOHUTIzD2Dm75 bbSD8eQe+0OM0hwsSuK811lrgoQE0hNLUrNTUwtSi+KLSnNSiw8xMnFwSjUwai2TeVGpuezQ O1tFxoSZl19yP8yzWm9Z5a2k8veLY6LPBT/3NcW738QHqG0NNGhirk48umP+qoWBl9d5bz0c /cDXdrldZNndXPOFEqtOHdPQZpCc/C9kPSv35KxbJl31T9p5FFksYn9fqpKy0Dsm9a1P8Zam lE7apYOBD4JlVy3Ik3x39pyhEktxRqKhFnNRcSIA5OQ3aYsCAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/KRWV1SyksYkGQnoPc8y1dCE2Dfw
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for allowing usage of the same PT value within multiple m- lines? - A new take.
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 14:27:21 -0000

--_000_7594FB04B1934943A5C02806D1A2204B1D1C654FESESSMB209erics_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

>  A small twist on your proposal
>
>  I think the recommendation in the BUNDLE document should say 2 points
>
>  1. Reuse of PT is allowed only in the cases where the end-point is able =
to uniquely map the >   incoming RTP Streams to its corresponding m=3Dline.=
 The specific mechanisms to do so are >   out of the scope of this document=
 . Informally, SSRC, AppID or similar stream correlators >   can be used.

But, again, when you send the offer, how do you know what "correlators" the=
 answerer supports? Should we say that is out of the scope?

> Also using the same PT across multiple m=3Dlines implies the same underly=
ing codec
> configuration.

So, what is YOUR definition of "codec configuration"? :)

Regards,

Christer

--_000_7594FB04B1934943A5C02806D1A2204B1D1C654FESESSMB209erics_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.hoenzb
	{mso-style-name:hoenzb;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D;mso-fareast-language:EN-US=
">Hi,<o:p></o:p></span></p>
<div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&gt;</span>&nbsp; A sm=
all twist on your proposal<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&gt;</span><o:p>&nbsp;=
</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&gt;</span>&nbsp; I th=
ink the recommendation in the BUNDLE document should say 2 points<o:p></o:p=
></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&gt;</span>&nbsp;&nbsp=
;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&gt;</span>&nbsp; 1. R=
euse of PT is allowed only in the cases where the end-point is able to uniq=
uely map the
<span style=3D"color:#1F497D">&gt;&nbsp;&nbsp; </span>incoming RTP Streams =
to its corresponding m=3Dline. The specific mechanisms to do so are
<span style=3D"color:#1F497D">&gt;&nbsp;&nbsp; </span>out of the scope of t=
his document . Informally, SSRC, AppID or similar stream correlators
<span style=3D"color:#1F497D">&gt;&nbsp;&nbsp; </span>can be used.<o:p></o:=
p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">But, again, when you send=
 the offer, how do you know what &#8220;correlators&#8221; the answerer sup=
ports? Should we say that is out of the scope?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&gt; </span>Also using=
 the same PT across multiple m=3Dlines implies the same underlying codec
<span style=3D"color:#1F497D"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&gt; </span>configurat=
ion.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">So, what is YOUR definiti=
on of &#8220;codec configuration&#8221;?
</span><span style=3D"font-size:11.0pt;font-family:Wingdings;color:#1F497D"=
>J</span><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Regards,<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Christer<o:p></o:p></span=
></p>
</div>
</div>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B1D1C654FESESSMB209erics_--


From nobody Mon Mar  3 06:31:04 2014
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 824161A01C9 for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 06:31:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham
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 vo0i8DkL9MLB for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 06:31:01 -0800 (PST)
Received: from sesbmg20.ericsson.net (sesbmg20.ericsson.net [193.180.251.56]) by ietfa.amsl.com (Postfix) with ESMTP id 72E861A00A6 for <mmusic@ietf.org>; Mon,  3 Mar 2014 06:31:00 -0800 (PST)
X-AuditID: c1b4fb38-b7f418e000001099-c2-53149220daca
Received: from ESESSHC023.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg20.ericsson.net (Symantec Mail Security) with SMTP id 50.A9.04249.02294135; Mon,  3 Mar 2014 15:30:57 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.216]) by ESESSHC023.ericsson.se ([153.88.183.87]) with mapi id 14.02.0387.000; Mon, 3 Mar 2014 15:30:56 +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: Q9: What are the criteria for allowing usage of the same PT value within multiple m- lines?
Thread-Index: Ac818yLx23ucJzjaSbubJw5GhjG+ygA9sF6PAAC/deA=
Date: Mon, 3 Mar 2014 14:30:56 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D1C656E@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D1C368D@ESESSMB209.ericsson.se> <7A9A37FB-196F-4F79-805B-95CE9B67C344@csperkins.org> <53148C0F.4090806@alum.mit.edu>
In-Reply-To: <53148C0F.4090806@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.148]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrMLMWRmVeSWpSXmKPExsUyM+Jvja7iJJFgg9ePWC2mLn/MYrFiwwFW ByaPv+8/MHksWfKTKYApissmJTUnsyy1SN8ugSvj3pfXrAUXOSqedp1naWD8wNbFyMkhIWAi cWvmGkYIW0ziwr31QHEuDiGBI4wSV3Z1sEM4ixklDqw+B+RwcLAJWEh0/9MGaRAR8JV49vg2 WIOwQAujROuZA2ANIgKtjBJT+o8wQVRZSXw+upcFxGYRUJE4cvMV2CBeoO7LzZIQC5YxSqx/ OQHsJE4BHYk/s+6A2YxAJ30/tQZsDrOAuMStJ/OZIE4VkFiy5zwzhC0q8fLxP1YIW0micckT Voh6HYkFuz+xQdjaEssWvgar5xUQlDg58wnLBEbRWUjGzkLSMgtJyywkLQsYWVYxchSnFifl phsZbGIERsTBLb8tdjBe/mtziFGag0VJnPfjW+cgIYH0xJLU7NTUgtSi+KLSnNTiQ4xMHJxS DYxlB//umer99V1LZE8nq3/xtF+9otobPxxjdJVl/77P6H7jCT7jJ6d9egMLZp3zC+R/nWDJ +jlj6W7fPQu2qVwQ91c7IX1H4vWE/QpRnrv0Nl8sfFoS3s+ueG6259vfL8p/L7Yyuuz7amlh wszkbfF/46YEcRaJzDwg9n59xbTF7J27mdg4vBiVWIozEg21mIuKEwE35sMuVgIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/qI3RcmA5lVr3TAinJCRB5-egR2M
Subject: Re: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for allowing usage of the same PT value within multiple m- lines?
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 14:31:03 -0000

Hi,

>The general case is that when the sender is sending a packet, it must have=
 *one* particular m-line in >the bundle that it intends the packet to be as=
sociated with. When the receiver receives a packet, it >must, based on info=
 received in the packet, or prior packets, be able associate the packet wit=
h >*one* particular m-line. It is an error if the sender don't agree on whi=
ch m-line is intended.
>
>(There is an exception for RTCP, which doesn't have to be associated with =
particular m-lines.)
>
>My thought has been that the O/A should only succeed if there is agreement=
 between the two sides >about how to classify packets, sufficient to ensure=
 that all packets will be consistently classified.

So, do you agree with the following: if the offerer wants to use the same P=
T value, but the answerer does not provide whatever information (SSRC, AppI=
D...) that is needed for the offerer to associate a received packet with an=
 m- line, the offerer should either send a new offer (with unique PT values=
), or terminate the session?

Regards,

Christer


From nobody Mon Mar  3 06:33:24 2014
Return-Path: <suhasietf@gmail.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 9E27F1A00A6 for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 06:33:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.799
X-Spam-Level: 
X-Spam-Status: No, score=-0.799 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_14=0.6, J_CHICKENPOX_15=0.6, 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 0vbOKRZM5QXP for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 06:33:21 -0800 (PST)
Received: from mail-we0-x22b.google.com (mail-we0-x22b.google.com [IPv6:2a00:1450:400c:c03::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 5F77D1A0126 for <mmusic@ietf.org>; Mon,  3 Mar 2014 06:33:21 -0800 (PST)
Received: by mail-we0-f171.google.com with SMTP id t61so801265wes.30 for <mmusic@ietf.org>; Mon, 03 Mar 2014 06:33:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=oqNBOR785QnCd4rkrYvMzowIVze9jHnIDoCS4OhBMkg=; b=Ys7TWLvoRfRfJR2JnedaqoXUb9+DlFwsiCJmVJag2PTitDCK2zZCiUvU4cfDC+ptiu 82HWUDl831dAp4DdKeNH4JjnKqHioUOFIoWX1aRDhKrPMvn35kqvkqliryf2mQCsmCqB qFfTcn9tasE5/2bspf71uNN2dB+q5G0UI+46uBk6xhP+DFUzrwYHacdUPHMOlwsGyM6H p5ymVihPczOfx4sEvIMW8bdUrOTE9k03uLNg4pB5xmqs9efTOqGbk/iSEPf7ohsLgagd 9momHMC3rKBuuCebUTZd0XIlbBN+GOstSXgBTrHPnQFlUZfJNlpPfPCx18sNijF4k6zT yZ2Q==
MIME-Version: 1.0
X-Received: by 10.195.13.17 with SMTP id eu17mr18571570wjd.24.1393857198055; Mon, 03 Mar 2014 06:33:18 -0800 (PST)
Received: by 10.195.12.134 with HTTP; Mon, 3 Mar 2014 06:33:18 -0800 (PST)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D1C654F@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D1C6336@ESESSMB209.ericsson.se> <CAMRcRGRu_BHBvNH8D+CgeEj9RUXiw-0fHj2UuGqhT7HUG=pJxw@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1D1C654F@ESESSMB209.ericsson.se>
Date: Mon, 3 Mar 2014 14:33:18 +0000
Message-ID: <CAMRcRGQG6e8iUM8NowR9STnjRNAXdqkFvnXkCJe4wTO6Oku6yg@mail.gmail.com>
From: Suhas Nandakumar <suhasietf@gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary=047d7bd91a7a28868e04f3b4abab
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/DtlLwVqQFci-1Iz91VHE069XBXc
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for allowing usage of the same PT value within multiple m- lines? - A new take.
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 14:33:23 -0000

--047d7bd91a7a28868e04f3b4abab
Content-Type: text/plain; charset=ISO-8859-1

Hello Christer

  Comments Inline.

Cheers
Suhas


On Mon, Mar 3, 2014 at 2:27 PM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

>  Hi,
>
>
>
> >  A small twist on your proposal
>
> >
>
> >  I think the recommendation in the BUNDLE document should say 2 points
>
> >
>
> >  1. Reuse of PT is allowed only in the cases where the end-point is
> able to uniquely map the >   incoming RTP Streams to its corresponding
> m=line. The specific mechanisms to do so are >   out of the scope of this
> document . Informally, SSRC, AppID or similar stream correlators >   can
> be used.
>
>
>
> But, again, when you send the offer, how do you know what "correlators"
> the answerer supports? Should we say that is out of the scope?
>
>
>

[Suhas] I am happy with some text similar to here:
https://tools.ietf.org/html/draft-roach-mmusic-unified-plan-00#section-3.2.

If the Offer/Answer can't prove any mechanism possible, It would imply new
Offer/Answer with unique PTs. I don't see if one can escape the worst-case
scenario though.




>   > Also using the same PT across multiple m=lines implies the same
> underlying codec
>
> > configuration.
>
>
>
> So, what is YOUR definition of "codec configuration"? J
>
>
>
[Suhas] I shall stick with Colin's suggestion.


>  Regards,
>
>
>
> Christer
>

--047d7bd91a7a28868e04f3b4abab
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hello Christer<div><br></div><div>&nbsp; Comments Inline.<=
/div><div><br></div><div>Cheers</div><div>Suhas</div><div class=3D"gmail_ex=
tra"><br><br><div class=3D"gmail_quote">On Mon, Mar 3, 2014 at 2:27 PM, Chr=
ister Holmberg <span dir=3D"ltr">&lt;<a href=3D"mailto:christer.holmberg@er=
icsson.com" target=3D"_blank">christer.holmberg@ericsson.com</a>&gt;</span>=
 wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">





<div lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)">Hi,<u></u><u></u></span></p>
<div><div class=3D"">
<div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:rgb(31,73,125)">&gt;</span>&nbs=
p; A small twist on your proposal<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:rgb(31,73,125)">&gt;</span><u><=
/u>&nbsp;<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:rgb(31,73,125)">&gt;</span>&nbs=
p; I think the recommendation in the BUNDLE document should say 2 points<u>=
</u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:rgb(31,73,125)">&gt;</span>&nbs=
p;&nbsp;<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:rgb(31,73,125)">&gt;</span>&nbs=
p; 1. Reuse of PT is allowed only in the cases where the end-point is able =
to uniquely map the
<span style=3D"color:rgb(31,73,125)">&gt;&nbsp;&nbsp; </span>incoming RTP S=
treams to its corresponding m=3Dline. The specific mechanisms to do so are
<span style=3D"color:rgb(31,73,125)">&gt;&nbsp;&nbsp; </span>out of the sco=
pe of this document . Informally, SSRC, AppID or similar stream correlators
<span style=3D"color:rgb(31,73,125)">&gt;&nbsp;&nbsp; </span>can be used.<u=
></u><u></u></p>
</div>
</div><div>
<p class=3D"MsoNormal">&nbsp;<u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)">But, again, when you send the offer, how do =
you know what &ldquo;correlators&rdquo; the answerer supports? Should we sa=
y that is out of the scope?<u></u><u></u></span></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)"><u></u>&nbsp;</span></p></div></div></div></=
div></blockquote><div><br></div><div>[Suhas] I am happy with some text simi=
lar to here:&nbsp;<a href=3D"https://tools.ietf.org/html/draft-roach-mmusic=
-unified-plan-00#section-3.2">https://tools.ietf.org/html/draft-roach-mmusi=
c-unified-plan-00#section-3.2</a>.</div>
<div><br></div><div>If the Offer/Answer can&#39;t prove any mechanism possi=
ble, It would imply new Offer/Answer with unique PTs. I don&#39;t see if on=
e can escape the worst-case scenario though.</div><div><br></div><div><br>
</div><div>&nbsp;</div><blockquote class=3D"gmail_quote" style=3D"margin:0p=
x 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);bo=
rder-left-style:solid;padding-left:1ex"><div lang=3D"EN-GB" link=3D"blue" v=
link=3D"purple">
<div><div><div><p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-fa=
mily:Calibri,sans-serif;color:rgb(31,73,125)"><u></u></span></p>
</div><div class=3D"">
<div>
<p class=3D"MsoNormal"><span style=3D"color:rgb(31,73,125)">&gt; </span>Als=
o using the same PT across multiple m=3Dlines implies the same underlying c=
odec
<span style=3D"color:rgb(31,73,125)"><u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"color:rgb(31,73,125)">&gt; </span>con=
figuration.<u></u><u></u></p>
</div>
</div><div>
<p class=3D"MsoNormal"><span style=3D"color:rgb(31,73,125)"><u></u>&nbsp;<u=
></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)">So, what is YOUR definition of &ldquo;codec =
configuration&rdquo;?
</span><span style=3D"font-size:11pt;font-family:Wingdings;color:rgb(31,73,=
125)">J</span><span style=3D"font-size:11pt;font-family:Calibri,sans-serif;=
color:rgb(31,73,125)"><u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)"><u></u>&nbsp;</span></p></div></div></div></=
div></blockquote><div>[Suhas] I shall stick with Colin&#39;s suggestion.&nb=
sp;</div>
<div>&nbsp;</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-l=
eft-style:solid;padding-left:1ex"><div lang=3D"EN-GB" link=3D"blue" vlink=
=3D"purple"><div>
<div><div><p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:=
Calibri,sans-serif;color:rgb(31,73,125)"><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)">Regards,<span class=3D""><font color=3D"#888=
888"><u></u><u></u></font></span></span></p><span class=3D""><font color=3D=
"#888888">
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)"><u></u>&nbsp;<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11pt;font-family:Calibri,sa=
ns-serif;color:rgb(31,73,125)">Christer<u></u><u></u></span></p>
</font></span></div>
</div>
</div>
</div>

</blockquote></div><br></div></div>

--047d7bd91a7a28868e04f3b4abab--


From nobody Mon Mar  3 06:40:56 2014
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 4CA411A00A5 for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 06:40:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.639
X-Spam-Level: 
X-Spam-Status: No, score=-0.639 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, HOST_MISMATCH_NET=0.311, HTML_MESSAGE=0.001, J_CHICKENPOX_14=0.6, 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 2en1bTWf-vx3 for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 06:40:53 -0800 (PST)
Received: from sessmg20.mgmt.ericsson.se (sessmg20.ericsson.net [193.180.251.50]) by ietfa.amsl.com (Postfix) with ESMTP id E4F561A005E for <mmusic@ietf.org>; Mon,  3 Mar 2014 06:40:52 -0800 (PST)
X-AuditID: c1b4fb32-b7f4c8e0000012f5-ff-5314947145ff
Received: from ESESSHC022.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg20.mgmt.ericsson.se (Symantec Mail Security) with SMTP id 3B.7E.04853.17494135; Mon,  3 Mar 2014 15:40:49 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.216]) by ESESSHC022.ericsson.se ([153.88.183.84]) with mapi id 14.02.0387.000; Mon, 3 Mar 2014 15:40:48 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Suhas Nandakumar <suhasietf@gmail.com>
Thread-Topic: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for allowing usage of the same PT value within multiple m- lines? - A new take.
Thread-Index: Ac824vtSFLJVCI5rSOGVBTMx34MhTf//+0EA///oubCAACBVAP//7g/A
Date: Mon, 3 Mar 2014 14:40:47 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D1C65C8@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D1C6336@ESESSMB209.ericsson.se> <CAMRcRGRu_BHBvNH8D+CgeEj9RUXiw-0fHj2UuGqhT7HUG=pJxw@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1D1C654F@ESESSMB209.ericsson.se> <CAMRcRGQG6e8iUM8NowR9STnjRNAXdqkFvnXkCJe4wTO6Oku6yg@mail.gmail.com>
In-Reply-To: <CAMRcRGQG6e8iUM8NowR9STnjRNAXdqkFvnXkCJe4wTO6Oku6yg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.148]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1D1C65C8ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrOLMWRmVeSWpSXmKPExsUyM+JvjW7hFJFgg+uLxC2mLn/MYrFzbgez A5PHzll32T2WLPnJFMAUxWWTkpqTWZZapG+XwJXRePg1c8Ei84o7P6cxNjC+Mehi5OSQEDCR 2Nu7ixnCFpO4cG89WxcjF4eQwAlGiab5d1ghnMWMEr87NrF3MXJwsAlYSHT/0wZpEBHQkli9 eC4TSJhZQF3i6uIgkHJhgUmMEsdWTwLrFRGYzCix8+RzNogGN4m7XfNYQWwWARWJ1Ye2soDY vAK+Ej9/XQGrERKYzyTx5Ic6iM0pEChxsG0ZI4jNCHTd91NrmEBsZgFxiVtP5jNBXC0gsWTP eagPRCVePv7HCmErSTQuecIKUZ8vsWjfMXaIXYISJ2c+YZnAKDoLyahZSMpmISmDiOtILNj9 iQ3C1pZYtvA1M4x95sBjJmTxBYzsqxgli1OLi3PTjQz0ctNzS/RSizKTi4vz8/SKUzcxAiPv 4JbfRjsYT+6xP8QozcGiJM57nbUmSEggPbEkNTs1tSC1KL6oNCe1+BAjEwenVANj1AyndTEF PYV/clbOqZArc01W1/5/KWLBy5NG1fkVabMZL2TNO2he/6s6Knct45KDy2dN1WIsXtwlWneG s/ndR9O+h1vq/Ga77imRufBw6YVV155w6DT7vj8699Uj5ulRapNTC2ZHH+NpiK9U7t97/VlH fOX8vtgCFp+Oq5vvHjiw0yBr240yJZbijERDLeai4kQAfk8SjIoCAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/yfade1wkwoHFD5FSLpEMyRzeuag
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for allowing usage of the same PT value within multiple m- lines? - A new take.
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 14:40:55 -0000

--_000_7594FB04B1934943A5C02806D1A2204B1D1C65C8ESESSMB209erics_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,
>  I think the recommendation in the BUNDLE document should say 2 points
>
>  1. Reuse of PT is allowed only in the cases where the end-point is able =
to uniquely map the >   incoming RTP Streams to its corresponding m=3Dline.=
 The specific mechanisms to do so are >   out of the scope of this document=
 . Informally, SSRC, AppID or similar stream correlators >   can be used.
But, again, when you send the offer, how do you know what "correlators" the=
 answerer supports? Should we say that is out of the scope?

[Suhas] I am happy with some text similar to here: https://tools.ietf.org/h=
tml/draft-roach-mmusic-unified-plan-00#section-3.2.

If the Offer/Answer can't prove any mechanism possible, It would imply new =
Offer/Answer with unique PTs. I don't see if one can escape the worst-case =
scenario though.

If people are ok with that, it works for me.

I guess that means that we would need a flag in the API to indicate whether=
 the same PT value can be used or not.

Regards,

Christer

--_000_7594FB04B1934943A5C02806D1A2204B1D1C65C8ESESSMB209erics_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:red;mso-fareast-language:EN-US">Hi=
,<o:p></o:p></span></p>
<div>
<div>
<div>
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<div>
<div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:#1F497D">&gt;</span>&nbsp; I think the recomm=
endation in the BUNDLE document should say 2 points<span style=3D"color:#1F=
497D"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:#1F497D">&gt;</span>&nbsp;&nbsp;<span style=
=3D"color:#1F497D"><o:p></o:p></span></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"color:#1F497D">&gt;</span>&nbsp; 1. Reuse of PT is =
allowed only in the cases where the end-point is able to uniquely map the
<span style=3D"color:#1F497D">&gt;&nbsp;&nbsp; </span>incoming RTP Streams =
to its corresponding m=3Dline. The specific mechanisms to do so are
<span style=3D"color:#1F497D">&gt;&nbsp;&nbsp; </span>out of the scope of t=
his document . Informally, SSRC, AppID or similar stream correlators
<span style=3D"color:#1F497D">&gt;&nbsp;&nbsp; </span>can be used.<span sty=
le=3D"color:#1F497D"><o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">But, again, when you send the offer, ho=
w do you know what &#8220;correlators&#8221; the answerer supports? Should
 we say that is out of the scope?</span><span style=3D"color:#1F497D"><o:p>=
</o:p></span></p>
</div>
</div>
</div>
</blockquote>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">[Suhas] I am happy with some text similar to here:&n=
bsp;<a href=3D"https://tools.ietf.org/html/draft-roach-mmusic-unified-plan-=
00#section-3.2">https://tools.ietf.org/html/draft-roach-mmusic-unified-plan=
-00#section-3.2</a>.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">If the Offer/Answer can't prove any mechanism possib=
le, It would imply new Offer/Answer with unique PTs. I don't see if one can=
 escape the worst-case scenario though.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:red">If people are ok with that, i=
t works for me.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:red"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:red">I guess that means that we wo=
uld need a flag in the API to indicate whether the same PT value can be use=
d or not.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:red"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:red">Regards,<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:red"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:red">Christer<o:p></o:p></span></p=
>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B1D1C65C8ESESSMB209erics_--


From nobody Mon Mar  3 10:20:58 2014
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 32EB31A01E7 for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 10:20:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 dPAfBzSBwKxr for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 10:20:50 -0800 (PST)
Received: from sesbmg20.ericsson.net (sesbmg20.ericsson.net [193.180.251.56]) by ietfa.amsl.com (Postfix) with ESMTP id 217961A0166 for <mmusic@ietf.org>; Mon,  3 Mar 2014 10:20:49 -0800 (PST)
X-AuditID: c1b4fb38-b7f418e000001099-fc-5314c7feb657
Received: from ESESSHC004.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg20.ericsson.net (Symantec Mail Security) with SMTP id 4B.C5.04249.EF7C4135; Mon,  3 Mar 2014 19:20:46 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.216]) by ESESSHC004.ericsson.se ([153.88.183.30]) with mapi id 14.02.0387.000; Mon, 3 Mar 2014 19:20:46 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: IETF#89: BUNDLE: Q9: What are the criteria for allowing usage of the same PT value within multiple m- lines? - Episode III
Thread-Index: Ac83DFupdRhkltXgRlCL5+jMoUQ74Q==
Date: Mon, 3 Mar 2014 18:20:45 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D1C7D2C@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.149]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1D1C7D2CESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrBLMWRmVeSWpSXmKPExsUyM+Jvje6/4yLBBifualpMXf6YxYHRY8mS n0wBjFFcNimpOZllqUX6dglcGU2rt7EUTLeuOL7/MXsDY49pFyMnh4SAicT+3m/MELaYxIV7 69m6GLk4hASOMErsWn2PFcJZzCjx89d9li5GDg42AQuJ7n/aIA0iAuoSX/f2gDULC7QySiy+ XQZSLyLQxSjx9+JVVogiPYn7N84xgtgsAioSly98AIvzCvhKbNx+FCzOCLT5+6k1TCA2s4C4 xK0n85kgLhKQWLLnPNR1ohIvH/9jhbCVJNYe3s4CUZ8v8fPGYaiZghInZz5hmcAoNAvJqFlI ymYhKYOI60gs2P2JDcLWlli28DUzjH3mwGMmZPEFjOyrGDmKU4uTctONDDYxAkP/4JbfFjsY L/+1OcQozcGiJM778a1zkJBAemJJanZqakFqUXxRaU5q8SFGJg5OqQbGhAB9CZ8DLyYmenPr vZUzfBmr0RKrXrX40WKRucZCjjMlViYsEwk7zDlVYFH8gpxdn7cKN/m8qkoRDyqzTeePjvQJ 6p53p0+X73q03jrdQuNjHXdqFh++en3X/Wc7rLy9+184e+0V2JodZpF5q/LY0TyD02+LA+z+ +/VMqe4IFKyxVJvfc02JpTgj0VCLuag4EQD4dIuRSwIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/YbhKs6q0ns9FKW9DZyK44V2pBNU
Subject: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for allowing usage of the same PT value within multiple m- lines? - Episode III
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 18:20:53 -0000

--_000_7594FB04B1934943A5C02806D1A2204B1D1C7D2CESESSMB209erics_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

Based on some further off-line discussions, I have the following suggestion=
:

Q1: Identical PT values in initial Offer

We allow an offerer to include identical PT values already in the initial o=
ffer.

BUT, we also MANDATE BUNDLE entities to support SOME mechanism (offerer det=
ermined) which can be used to distinguish received media. At this point we =
don't need to decide what "SOME" is. It could be SSRC, "AppId", or somethin=
g else.

If an BUNDLE endpoint doesn't want to, or for some reason can't use "SOME",=
 it will have to terminate the BUNDLE group and fall back to individual 5-t=
uple for each m- line.

Does anyone have a problem with this approach?


Q2: Codec configuration

People are ok to allow PT value re-usage for the same "codec configuration"=
, but it means that we need text what that means (Colin sent something). I =
do NOT want to word smith text during the presentation.

Regards,

Christer

--_000_7594FB04B1934943A5C02806D1A2204B1D1C7D2CESESSMB209erics_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Hi,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Based on some further off=
-line discussions, I have the following suggestion:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Q1: Identical PT value=
s in initial Offer<o:p></o:p></span></b></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">We allow an offerer to in=
clude identical PT values already in the initial offer.<o:p></o:p></span></=
p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">BUT, we also MANDATE BUND=
LE entities to support SOME mechanism (offerer determined) which can be use=
d to distinguish received media. At this point we don&#8217;t
 need to decide what &#8220;SOME&#8221; is. It could be SSRC, &#8220;AppId&=
#8221;, or something else. <o:p>
</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">If an BUNDLE endpoint doe=
sn&#8217;t want to, or for some reason can&#8217;t use &#8220;SOME&#8221;, =
it will have to terminate the BUNDLE group and fall back to individual 5-tu=
ple for
 each m- line.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Does anyone have a proble=
m with this approach?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:#1F497D">Q2: Codec configuratio=
n<o:p></o:p></span></b></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">People are ok to allow PT=
 value re-usage for the same &#8220;codec configuration&#8221;, but it mean=
s that we need text what that means (Colin sent something). I do NOT
 want to word smith text during the presentation.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Regards,<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Christer<o:p></o:p></span=
></p>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B1D1C7D2CESESSMB209erics_--


From nobody Mon Mar  3 10:30:22 2014
Return-Path: <suhasietf@gmail.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 C160E1A031A for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 10:30:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 rvj1S0n3xonG for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 10:30:17 -0800 (PST)
Received: from mail-wg0-x22e.google.com (mail-wg0-x22e.google.com [IPv6:2a00:1450:400c:c00::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 150B01A02BD for <mmusic@ietf.org>; Mon,  3 Mar 2014 10:30:12 -0800 (PST)
Received: by mail-wg0-f46.google.com with SMTP id z12so3673213wgg.17 for <mmusic@ietf.org>; Mon, 03 Mar 2014 10:30:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=h0Pic3RzPVs++lRAEQNtJlaMmc2jI1/Zr84OyGPTyU4=; b=WCN2wsjSVClNWYUnhuFuQ4hTGhoGmVb6i4olCrBGNKCj1zGBLMkjTp+tEynuZBCMBx u7GMvPE3fpcYviJDnDYfh6H/5SjcmBDEGUjlabWVaRlIIYIMzo4HGcb/ASEXTypwn3uA Gs5N8ZKmRMmfaYa1w9gsbRzIhODoCv4wZ1cBj75+GZXOQaSjCYSnweu3iWqGx6edMk47 n7T1a0o7M4vjxS2cu3byOlvfqgZvdcxBM3E75+0+HiuJ7gTa1On8BgO8G4gaCWFPozg0 vpXXN4jXdITP8K8MTqTrCCB9uQ6I88zfOqDhsq4murigbLEJwkKcQIIXDg3XkUwn9z52 yr+A==
MIME-Version: 1.0
X-Received: by 10.195.13.17 with SMTP id eu17mr20573104wjd.24.1393871409719; Mon, 03 Mar 2014 10:30:09 -0800 (PST)
Received: by 10.195.12.134 with HTTP; Mon, 3 Mar 2014 10:30:09 -0800 (PST)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D1C7D2C@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D1C7D2C@ESESSMB209.ericsson.se>
Date: Mon, 3 Mar 2014 18:30:09 +0000
Message-ID: <CAMRcRGQT_9gsh3LeRkZWO8DAuKOOkEGVEfb9fF3coHdLcmY6ag@mail.gmail.com>
From: Suhas Nandakumar <suhasietf@gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary=047d7bd91a7a3d303e04f3b7fa28
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/Udw3OJdT9psqmx82unFbrRSWONU
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for allowing usage of the same PT value within multiple m- lines? - Episode III
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 18:30:20 -0000

--047d7bd91a7a3d303e04f3b7fa28
Content-Type: text/plain; charset=ISO-8859-1

Hello Christer

  Please see inline

Thanks
Suhas


On Mon, Mar 3, 2014 at 6:20 PM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

>  Hi,
>
>
>
> Based on some further off-line discussions, I have the following
> suggestion:
>
>
>
> *Q1: Identical PT values in initial Offer*
>
>
>
> We allow an offerer to include identical PT values already in the initial
> offer.
>
>
>
 BUT, we also MANDATE BUNDLE entities to support SOME mechanism (offerer
> determined) which can be used to distinguish received media. At this point
> we don't need to decide what "SOME" is. It could be SSRC, "AppId", or
> something else.
>
>
>
[Suhas] Agree on the SOME need not be decided now and I feel it is out of
scope of the BUNDLE draft


>  If an BUNDLE endpoint doesn't want to, or for some reason can't use
> "SOME", it will have to terminate the BUNDLE group and fall back to
> individual 5-tuple for each m- line.
>
>
>

 [Suhas] Seems alright but the first point seems too conservative as
explained below

 If an BUNDLE endpoint doesn't want to use identical PT values, it can
still use unique PT values and be in the BUNDLE group unless it has
exhausted the PT space.

But I am OK with the proposed solution if everyone agrees.

 Does anyone have a problem with this approach?
>
>
>
>
>
> *Q2: Codec configuration*
>
>
>
> People are ok to allow PT value re-usage for the same "codec
> configuration", but it means that we need text what that means (Colin sent
> something). I do NOT want to word smith text during the presentation.
>
>
>
 [Suhas] +1 ..


>  Regards,
>
>
>
> Christer
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>
>

--047d7bd91a7a3d303e04f3b7fa28
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hello Christer<div><br></div><div>&nbsp; Please see inline=
</div><div><br></div><div>Thanks</div><div>Suhas<br><div class=3D"gmail_ext=
ra"><br><br><div class=3D"gmail_quote">On Mon, Mar 3, 2014 at 6:20 PM, Chri=
ster Holmberg <span dir=3D"ltr">&lt;<a href=3D"mailto:christer.holmberg@eri=
csson.com" target=3D"_blank">christer.holmberg@ericsson.com</a>&gt;</span> =
wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">





<div lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Hi,<u></u><u></u></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>&nbsp;<u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Based on some further off=
-line discussions, I have the following suggestion:<u></u><u></u></span></p=
>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>&nbsp;<u></u></spa=
n></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Q1: Identical PT value=
s in initial Offer<u></u><u></u></span></b></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>&nbsp;<u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">We allow an offerer to in=
clude identical PT values already in the initial offer.<u></u><u></u></span=
></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>&nbsp;</span></p><=
/div></div></blockquote><blockquote class=3D"gmail_quote" style=3D"margin:0=
px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);b=
order-left-style:solid;padding-left:1ex">
<div lang=3D"EN-GB" link=3D"blue" vlink=3D"purple"><div><p class=3D"MsoNorm=
al"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;s=
ans-serif&quot;;color:#1f497d"><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">BUT, we also MANDATE BUND=
LE entities to support SOME mechanism (offerer determined) which can be use=
d to distinguish received media. At this point we don&rsquo;t
 need to decide what &ldquo;SOME&rdquo; is. It could be SSRC, &ldquo;AppId&=
rdquo;, or something else. <u></u>
<u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>&nbsp;</span></p><=
/div></div></blockquote><div>[Suhas] Agree on the SOME need not be decided =
now and I feel it is out of scope of the BUNDLE draft</div>
<div>&nbsp;</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-l=
eft-style:solid;padding-left:1ex"><div lang=3D"EN-GB" link=3D"blue" vlink=
=3D"purple"><div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">If an BUNDLE endpoint doe=
sn&rsquo;t want to, or for some reason can&rsquo;t use &ldquo;SOME&rdquo;, =
it will have to terminate the BUNDLE group and fall back to individual 5-tu=
ple for
 each m- line.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>&nbsp;</span></p><=
/div></div></blockquote><div><br></div><div>&nbsp;[Suhas] Seems alright but=
 the first point seems too conservative as explained below</div>
<div><br></div><div>&nbsp;If an BUNDLE endpoint doesn&#39;t want to use ide=
ntical PT values, it can still use unique PT values and be in the BUNDLE gr=
oup unless it has exhausted the PT space.&nbsp;</div><div><br></div><div>Bu=
t I am OK with the proposed solution if everyone agrees.</div>
<div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex"><div lang=3D"EN-GB" link=3D"b=
lue" vlink=3D"purple"><div><p class=3D"MsoNormal"><span style=3D"font-size:=
11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d=
"><u></u></span></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Does anyone have a proble=
m with this approach?<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>&nbsp;<u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>&nbsp;<u></u></spa=
n></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Q2: Codec configuratio=
n<u></u><u></u></span></b></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>&nbsp;<u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">People are ok to allow PT=
 value re-usage for the same &ldquo;codec configuration&rdquo;, but it mean=
s that we need text what that means (Colin sent something). I do NOT
 want to word smith text during the presentation.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>&nbsp;</span></p><=
/div></div></blockquote><div>&nbsp;[Suhas] +1 ..</div><div>&nbsp;</div><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex">
<div lang=3D"EN-GB" link=3D"blue" vlink=3D"purple"><div><p class=3D"MsoNorm=
al"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&quot;s=
ans-serif&quot;;color:#1f497d"><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Regards,<span class=3D"HO=
EnZb"><font color=3D"#888888"><u></u><u></u></font></span></span></p><span =
class=3D"HOEnZb"><font color=3D"#888888">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>&nbsp;<u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Christer<u></u><u></u></s=
pan></p>
</font></span></div>
</div>

<br>_______________________________________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/mmusic</a><br>
<br></blockquote></div><br></div></div></div>

--047d7bd91a7a3d303e04f3b7fa28--


From nobody Mon Mar  3 10:37:45 2014
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 AAE2A1A033C for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 10:37:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.239
X-Spam-Level: 
X-Spam-Status: No, score=-1.239 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, HOST_MISMATCH_NET=0.311, HTML_MESSAGE=0.001, 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 gp4PzTtj5krl for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 10:37:41 -0800 (PST)
Received: from sessmg20.mgmt.ericsson.se (sessmg20.ericsson.net [193.180.251.50]) by ietfa.amsl.com (Postfix) with ESMTP id 4529F1A033B for <mmusic@ietf.org>; Mon,  3 Mar 2014 10:37:39 -0800 (PST)
X-AuditID: c1b4fb32-b7f4c8e0000012f5-e8-5314cbf0138a
Received: from ESESSHC005.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg20.mgmt.ericsson.se (Symantec Mail Security) with SMTP id 46.4B.04853.0FBC4135; Mon,  3 Mar 2014 19:37:36 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.216]) by ESESSHC005.ericsson.se ([153.88.183.33]) with mapi id 14.02.0387.000; Mon, 3 Mar 2014 19:37:36 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Suhas Nandakumar <suhasietf@gmail.com>
Thread-Topic: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for allowing usage of the same PT value within multiple m- lines? - Episode III
Thread-Index: Ac83DFupdRhkltXgRlCL5+jMoUQ74f//87uA///t/HA=
Date: Mon, 3 Mar 2014 18:37:35 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D1C7F28@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D1C7D2C@ESESSMB209.ericsson.se> <CAMRcRGQT_9gsh3LeRkZWO8DAuKOOkEGVEfb9fF3coHdLcmY6ag@mail.gmail.com>
In-Reply-To: <CAMRcRGQT_9gsh3LeRkZWO8DAuKOOkEGVEfb9fF3coHdLcmY6ag@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.149]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1D1C7F28ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrOLMWRmVeSWpSXmKPExsUyM+Jvje6H0yLBBq+3qFpMXf6YxWLn3A5m ByaPnbPusnssWfKTKYApissmJTUnsyy1SN8ugSvj98ylTAUHsise7j3M2sDYndDFyMkhIWAi cWDJSWYIW0ziwr31bF2MXBxCAicYJdYufgXlLGaU+H69A6iKg4NNwEKi+582SIOIgJbE6sVz mUDCzALqElcXB4GUCwtMYpT4tbeZGcQREZjMKLHh/mpGiAYrickPtrGA2CwCKhJbfuxkBWnm FfCV2H7PCWLXFEaJQ5ubweo5BQIlVlxoZwKxGYGu+35qDZjNLCAucevJfCaIqwUkluw5D/WB qMTLx/9YIWwlibWHt7NA1OdLrLg+ASzOKyAocXLmE5YJjKKzkIyahaRsFpIyiLiOxILdn9gg bG2JZQtfM8PYZw48ZkIWX8DIvopRsji1uDg33chALzc9t0QvtSgzubg4P0+vOHUTIzDyDm75 bbSD8eQe+0OM0hwsSuK811lrgoQE0hNLUrNTUwtSi+KLSnNSiw8xMnFwSjUwBqcsC+D5mPvw VfaX9BrGrW73roncjrCO2r6topOXb+a9ew8TC+pLPzK989vFvmfV3Zb8CNVns/2fSMR6VlwK zT3CNPfDvxfNKyTkZtmVlKkUJtV9ZPwqlCp+vb7gt23mlsLK1JBfHd8Xx2S8zeJlWHBw9oOn y/dL10fesazy2v+lXFRru5GDEktxRqKhFnNRcSIAed6bLIoCAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/czlRP9m5GPxdFc4p45QyPM88IJ8
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for allowing usage of the same PT value within multiple m- lines? - Episode III
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 18:37:44 -0000

--_000_7594FB04B1934943A5C02806D1A2204B1D1C7F28ESESSMB209erics_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,
Based on some further off-line discussions, I have the following suggestion=
:

Q1: Identical PT values in initial Offer
We allow an offerer to include identical PT values already in the initial o=
ffer.
BUT, we also MANDATE BUNDLE entities to support SOME mechanism (offerer det=
ermined) which can be used to distinguish received media. At this point we =
don't need to decide what "SOME" is. It could be SSRC, "AppId", or somethin=
g else.
[Suhas] Agree on the SOME need not be decided now and I feel it is out of s=
cope of the BUNDLE draft

I didn't suggest that it is out of scope of the BUNDLE draft (we can for su=
re discuss that also) - only that we don't need to decide what SOME is at t=
his point.


If an BUNDLE endpoint doesn't want to, or for some reason can't use "SOME",=
 it will have to terminate the BUNDLE group and fall back to individual 5-t=
uple for each m- line.

 [Suhas] Seems alright but the first point seems too conservative as explai=
ned below

 If an BUNDLE endpoint doesn't want to use identical PT values, it can stil=
l use unique PT values and be in the BUNDLE group unless it has exhausted t=
he PT space.

I should have been more clear. I was referring to an endpoint receiving an =
offer with identical PT values, but does not want to, or can't, use the SOM=
E mechanism. In such case the endpoint will have to fallback.

Regards,

Christer



But I am OK with the proposed solution if everyone agrees.

Does anyone have a problem with this approach?


Q2: Codec configuration

People are ok to allow PT value re-usage for the same "codec configuration"=
, but it means that we need text what that means (Colin sent something). I =
do NOT want to word smith text during the presentation.

 [Suhas] +1 ..

Regards,

Christer

_______________________________________________
mmusic mailing list
mmusic@ietf.org<mailto:mmusic@ietf.org>
https://www.ietf.org/mailman/listinfo/mmusic


--_000_7594FB04B1934943A5C02806D1A2204B1D1C7F28ESESSMB209erics_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.hoenzb
	{mso-style-name:hoenzb;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:red;mso-fareast-language:EN-US">Hi=
,<o:p></o:p></span></p>
<div>
<div>
<div>
<div>
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">Based on some further off-line discussi=
ons, I have the following suggestion:</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;=
,&quot;sans-serif&quot;;color:#1F497D">Q1: Identical PT values in initial O=
ffer</span></b><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&qu=
ot;,&quot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span style=3D"color=
:#1F497D"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">We allow an offerer to include identica=
l PT values already in the initial offer.</span><span style=3D"color:#1F497=
D"><o:p></o:p></span></p>
</div>
</div>
</blockquote>
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">BUT, we also MANDATE BUNDLE entities to=
 support SOME mechanism (offerer determined) which can be
 used to distinguish received media. At this point we don&#8217;t need to d=
ecide what &#8220;SOME&#8221; is. It could be SSRC, &#8220;AppId&#8221;, or=
 something else.
</span><span style=3D"color:#1F497D"><o:p></o:p></span></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal">[Suhas] Agree on the SOME need not be decided now an=
d I feel it is out of scope of the BUNDLE draft<o:p></o:p></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:red">I didn&#8217;t suggest that i=
t is out of scope of the BUNDLE draft (we can for sure discuss that also) &=
#8211; only that we don&#8217;t need to decide what SOME is at this point.<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:red"><o:p>&nbsp;</o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">If an BUNDLE endpoint doesn&#8217;t wan=
t to, or for some reason can&#8217;t use &#8220;SOME&#8221;, it will have t=
o terminate
 the BUNDLE group and fall back to individual 5-tuple for each m- line.&nbs=
p;</span><span style=3D"color:#1F497D"><o:p></o:p></span></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;[Suhas] Seems alright but the first point seem=
s too conservative as explained below<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;If an BUNDLE endpoint doesn't want to use iden=
tical PT values, it can still use unique PT values and be in the BUNDLE gro=
up unless it has exhausted the PT space.&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:red">I should have been more clear=
. I was referring to an endpoint receiving an offer with identical PT value=
s, but does not want to, or can&#8217;t, use the SOME mechanism.
 In such case the endpoint will have to fallback.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:red"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:red">Regards,<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:red"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:red">Christer<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
</div>
<div>
<p class=3D"MsoNormal">But I am OK with the proposed solution if everyone a=
grees.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">Does anyone have a problem with this ap=
proach?</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><b><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;=
,&quot;sans-serif&quot;;color:#1F497D">Q2: Codec configuration</span></b><o=
:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">People are ok to allow PT value re-usag=
e for the same &#8220;codec configuration&#8221;, but it means that we
 need text what that means (Colin sent something). I do NOT want to word sm=
ith text during the presentation.</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><o:p></o:p></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal">&nbsp;[Suhas] &#43;1 ..<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
<blockquote style=3D"border:none;border-left:solid #CCCCCC 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">Regards,</span><o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">&nbsp;</span><span style=3D"color:#8888=
88"><o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,&q=
uot;sans-serif&quot;;color:#1F497D">Christer</span><span style=3D"color:#88=
8888"><o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
_______________________________________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/mmusic</a><o:p></o:p></p>
</blockquote>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B1D1C7F28ESESSMB209erics_--


From nobody Mon Mar  3 10:59:34 2014
Return-Path: <suhasietf@gmail.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 6B8E81A038D for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 10:59:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 9lgrz9IsBR-Y for <mmusic@ietfa.amsl.com>; Mon,  3 Mar 2014 10:59:25 -0800 (PST)
Received: from mail-wg0-x233.google.com (mail-wg0-x233.google.com [IPv6:2a00:1450:400c:c00::233]) by ietfa.amsl.com (Postfix) with ESMTP id C725E1A0389 for <mmusic@ietf.org>; Mon,  3 Mar 2014 10:59:24 -0800 (PST)
Received: by mail-wg0-f51.google.com with SMTP id a1so3773268wgh.22 for <mmusic@ietf.org>; Mon, 03 Mar 2014 10:59:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=VslWZQmjh1lbXXGOse2ymX33Tt4lh9QbN58vPZtDE8U=; b=v2MbGwr+SV8Lz3Uki+dKe53NrSvGs5LMvuudExs+CelbaXtzAYoD7G1Yc1obcnnikU 9eHvoGtJYskmC1qi5V2iov+aCGpMQivyUN5QWZy/IHzQRciVszaQ1Ne01c2QoVAAoiAK 7Q6ZXaGiDNTG/iqoKRwb/2NJMMWnLFoqlOcqL8ScpBuRRq1bfTuv4/MrTQZiGXA4nKtn zwE5/LlHVXVgUD6csnc+ZFBN3zGqEFCA5SrySZQpcJAOBcoUtVolhO2ok/os8/rxKSdk lUvjv2PPvcAZcf1XWd6lpAt2QI3JQdZvwv/alCzqUZ/EOQHphRGcp0nm7Cdrc+7DTxz8 HcKw==
MIME-Version: 1.0
X-Received: by 10.194.202.230 with SMTP id kl6mr21003213wjc.9.1393873161297; Mon, 03 Mar 2014 10:59:21 -0800 (PST)
Received: by 10.195.12.134 with HTTP; Mon, 3 Mar 2014 10:59:21 -0800 (PST)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D1C7F28@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D1C7D2C@ESESSMB209.ericsson.se> <CAMRcRGQT_9gsh3LeRkZWO8DAuKOOkEGVEfb9fF3coHdLcmY6ag@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1D1C7F28@ESESSMB209.ericsson.se>
Date: Mon, 3 Mar 2014 18:59:21 +0000
Message-ID: <CAMRcRGSZGFDDsS=ZaccYdiQ1pfP9UOfVFFSbES+eZ-vuHNgesw@mail.gmail.com>
From: Suhas Nandakumar <suhasietf@gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary=047d7b873a10a43a6504f3b862d6
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/r3DNPvqMRzZVoJsvL7Bh6PhVfkA
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] IETF#89: BUNDLE: Q9: What are the criteria for allowing usage of the same PT value within multiple m- lines? - Episode III
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 18:59:28 -0000

--047d7b873a10a43a6504f3b862d6
Content-Type: text/plain; charset=ISO-8859-1

Thanks Christer. That makes it clear :)

Cheers
Suhas


On Mon, Mar 3, 2014 at 6:37 PM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

>  Hi,
>
>  Based on some further off-line discussions, I have the following
> suggestion:
>
>
>
> *Q1: Identical PT values in initial Offer*
>
> We allow an offerer to include identical PT values already in the initial
> offer.
>
>   BUT, we also MANDATE BUNDLE entities to support SOME mechanism (offerer
> determined) which can be used to distinguish received media. At this point
> we don't need to decide what "SOME" is. It could be SSRC, "AppId", or
> something else.
>
>  [Suhas] Agree on the SOME need not be decided now and I feel it is out
> of scope of the BUNDLE draft
>
>
>
> I didn't suggest that it is out of scope of the BUNDLE draft (we can for
> sure discuss that also) - only that we don't need to decide what SOME is at
> this point.
>
>
>
>
>
>  If an BUNDLE endpoint doesn't want to, or for some reason can't use
> "SOME", it will have to terminate the BUNDLE group and fall back to
> individual 5-tuple for each m- line.
>
>
>
>  [Suhas] Seems alright but the first point seems too conservative as
> explained below
>
>
>
>  If an BUNDLE endpoint doesn't want to use identical PT values, it can
> still use unique PT values and be in the BUNDLE group unless it has
> exhausted the PT space.
>
>
>
> I should have been more clear. I was referring to an endpoint receiving an
> offer with identical PT values, but does not want to, or can't, use the
> SOME mechanism. In such case the endpoint will have to fallback.
>
>
>
> Regards,
>
>
>
> Christer
>
>
>
>
>
>
>
> But I am OK with the proposed solution if everyone agrees.
>
>
>
>  Does anyone have a problem with this approach?
>
>
>
>
>
> *Q2: Codec configuration*
>
>
>
> People are ok to allow PT value re-usage for the same "codec
> configuration", but it means that we need text what that means (Colin sent
> something). I do NOT want to word smith text during the presentation.
>
>
>
>   [Suhas] +1 ..
>
>
>
>  Regards,
>
>
>
> Christer
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>
>
>

--047d7b873a10a43a6504f3b862d6
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Thanks Christer. That makes it clear :)&nbsp;<div><br></di=
v><div>Cheers</div><div>Suhas</div><div><div class=3D"gmail_extra"><br><br>=
<div class=3D"gmail_quote">On Mon, Mar 3, 2014 at 6:37 PM, Christer Holmber=
g <span dir=3D"ltr">&lt;<a href=3D"mailto:christer.holmberg@ericsson.com" t=
arget=3D"_blank">christer.holmberg@ericsson.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">





<div lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:red">Hi,<u></u><u></u></span></p>
<div>
<div>
<div>
<div><div class=3D"">
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Based on some further off=
-line discussions, I have the following suggestion:</span><u></u><u></u></p=
>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">&nbsp;</span><u></u><u></=
u></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Q1: Identical PT value=
s in initial Offer</span></b><span style=3D"font-size:11.0pt;font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">&nbsp;</span><span =
style=3D"color:#1f497d"><u></u><u></u></span></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">We allow an offerer to in=
clude identical PT values already in the initial offer.</span><span style=
=3D"color:#1f497d"><u></u><u></u></span></p>

</div>
</div>
</blockquote>
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">BUT, we also MANDATE BUND=
LE entities to support SOME mechanism (offerer determined) which can be
 used to distinguish received media. At this point we don&rsquo;t need to d=
ecide what &ldquo;SOME&rdquo; is. It could be SSRC, &ldquo;AppId&rdquo;, or=
 something else.
</span><span style=3D"color:#1f497d"><u></u><u></u></span></p>
</div>
</div>
</blockquote>
</div><div><div class=3D"">
<p class=3D"MsoNormal">[Suhas] Agree on the SOME need not be decided now an=
d I feel it is out of scope of the BUNDLE draft<u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>&nbsp;<u></u></spa=
n></p>
</div><p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;;color:red">I didn&rsquo;t suggest =
that it is out of scope of the BUNDLE draft (we can for sure discuss that a=
lso) &ndash; only that we don&rsquo;t need to decide what SOME is at this p=
oint.<u></u><u></u></span></p>

<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:red"><u></u>&nbsp;<u></u></span></=
p>
</div><div class=3D"">
<div>
<p class=3D"MsoNormal">&nbsp;<u></u><u></u></p>
</div>
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">If an BUNDLE endpoint doe=
sn&rsquo;t want to, or for some reason can&rsquo;t use &ldquo;SOME&rdquo;, =
it will have to terminate
 the BUNDLE group and fall back to individual 5-tuple for each m- line.&nbs=
p;</span><span style=3D"color:#1f497d"><u></u><u></u></span></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;[Suhas] Seems alright but the first point seem=
s too conservative as explained below<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;If an BUNDLE endpoint doesn&#39;t want to use =
identical PT values, it can still use unique PT values and be in the BUNDLE=
 group unless it has exhausted the PT space.&nbsp;<u></u><u></u></p>
</div>
</div><div>
<p class=3D"MsoNormal"><span style=3D"color:#1f497d"><u></u>&nbsp;<u></u></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:red">I should have been more clear=
. I was referring to an endpoint receiving an offer with identical PT value=
s, but does not want to, or can&rsquo;t, use the SOME mechanism.
 In such case the endpoint will have to fallback.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:red"><u></u>&nbsp;<u></u></span></=
p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:red">Regards,<span class=3D"HOEnZb=
"><font color=3D"#888888"><u></u><u></u></font></span></span></p><span clas=
s=3D"HOEnZb"><font color=3D"#888888">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:red"><u></u>&nbsp;<u></u></span></=
p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:red">Christer<u></u><u></u></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>&nbsp;<u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>&nbsp;<u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>&nbsp;<u></u></spa=
n></p>
</font></span></div><div class=3D"">
<div>
<p class=3D"MsoNormal">But I am OK with the proposed solution if everyone a=
grees.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Does anyone have a proble=
m with this approach?</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">&nbsp;</span><u></u><u></=
u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">&nbsp;</span><u></u><u></=
u></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;;color:#1f497d">Q2: Codec configuratio=
n</span></b><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">&nbsp;</span><u></u><u></=
u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">People are ok to allow PT=
 value re-usage for the same &ldquo;codec configuration&rdquo;, but it mean=
s that we
 need text what that means (Colin sent something). I do NOT want to word sm=
ith text during the presentation.</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">&nbsp;</span><u></u><u></=
u></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal">&nbsp;[Suhas] +1 ..<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp;<u></u><u></u></p>
</div>
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0c=
m 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Regards,</span><u></u><u>=
</u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">&nbsp;</span><span style=
=3D"color:#888888"><u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Christer</span><span styl=
e=3D"color:#888888"><u></u><u></u></span></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
_______________________________________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/mmusic</a><u></u><u></u></p>
</blockquote>
</div></div>
<p class=3D"MsoNormal"><u></u>&nbsp;<u></u></p>
</div>
</div>
</div>
</div>
</div>

</blockquote></div><br></div></div></div>

--047d7b873a10a43a6504f3b862d6--


From nobody Wed Mar  5 03:03:43 2014
Return-Path: <thomas.stach@unify.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 C3BEF1A0447 for <mmusic@ietfa.amsl.com>; Wed,  5 Mar 2014 03:03:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.147
X-Spam-Level: 
X-Spam-Status: No, score=-2.147 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.547] autolearn=ham
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 4Ee1A-gHeTk4 for <mmusic@ietfa.amsl.com>; Wed,  5 Mar 2014 03:03:40 -0800 (PST)
Received: from mx12.unify.com (mx12.unify.com [62.134.46.10]) by ietfa.amsl.com (Postfix) with ESMTP id 779331A0431 for <mmusic@ietf.org>; Wed,  5 Mar 2014 03:03:40 -0800 (PST)
Received: from MCHP02HTC.global-ad.net (unknown [172.29.42.235]) by mx12.unify.com (Server) with ESMTP id 3951423F0561; Wed,  5 Mar 2014 12:03:36 +0100 (CET)
Received: from MCHP04MSX.global-ad.net ([169.254.1.208]) by MCHP02HTC.global-ad.net ([172.29.42.235]) with mapi id 14.03.0174.001; Wed, 5 Mar 2014 12:03:36 +0100
From: "Stach, Thomas" <thomas.stach@unify.com>
To: =?iso-8859-1?Q?Ari_Ker=E4nen?= <ari.keranen@ericsson.com>
Thread-Topic: Comment on the ICE updated offer procedures
Thread-Index: Ac82UynstLVpW+NhS5ORd1Q4pZhv3QACmLsAAHzoIFA=
Date: Wed, 5 Mar 2014 11:03:35 +0000
Message-ID: <F81CEE99482EFE438DAE2A652361EE1217A5DDC9@MCHP04MSX.global-ad.net>
References: <F81CEE99482EFE438DAE2A652361EE1217A537BC@MCHP04MSX.global-ad.net> <1ECDA76B-D54B-4DF2-BE1C-A826B18F28AD@ericsson.com>
In-Reply-To: <1ECDA76B-D54B-4DF2-BE1C-A826B18F28AD@ericsson.com>
Accept-Language: de-AT, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.29.42.225]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/Ql-V8ugbyT5SN-8zpPJh5OnC0ZY
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Comment on the ICE updated offer procedures
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: Wed, 05 Mar 2014 11:03:42 -0000

> > the slides  for IETF 89 propose that always an updated offer shall be s=
ent.
> > You also mention the issues with that as listed in draft-elwell-mmusic-=
ice-
> updated-offer.
> > This was also discussed in IETF 80.
> > Draft-elwell-mmusic-ice-updated-offer acknowledges that there are middl=
e
> boxes that need such updated offer to work properly.
> > However, there are also cases and other types of middle boxes that brea=
k or
> show undesirable behavior, just because of the updated offer.
> > Because of these issues, I think that always sending the updated offer
> should not be required.
> > Instead, it should be made configurable if the updated offer is sent or=
 not
> sent, possibly together with some signaling (ice-options/ice-options-
> required?) which behavior is to be applied.
>=20
> Having this configurable and defaulting to always doing the updated offer
> makes sense to me. And perhaps this should be then signaled in an ice-opt=
ions-
> optional since it should not affect whether aggressive nomination can be =
used
> or not.

[TS] Yes, defaulting to doing the updated offer seems reasonable since 5245=
 agents would do it anyhow in most cases.
I agree that aggressive nomination shouldn't be impacted, so using a tag in=
 ice-options-optional is fine.
Thanks
Thomas

>=20
>=20
> Cheers,
> Ari


From nobody Wed Mar  5 09:39:35 2014
Return-Path: <ari.keranen@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 7F3681A0503 for <mmusic@ietfa.amsl.com>; Wed,  5 Mar 2014 09:39:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.94
X-Spam-Level: 
X-Spam-Status: No, score=-0.94 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, HOST_MISMATCH_NET=0.311, MIME_8BIT_HEADER=0.3, 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 omZMvHKHu4gT for <mmusic@ietfa.amsl.com>; Wed,  5 Mar 2014 09:39:33 -0800 (PST)
Received: from sessmg20.mgmt.ericsson.se (sessmg20.ericsson.net [193.180.251.50]) by ietfa.amsl.com (Postfix) with ESMTP id BC2321A0191 for <mmusic@ietf.org>; Wed,  5 Mar 2014 09:39:32 -0800 (PST)
X-AuditID: c1b4fb32-b7f4c8e0000012f5-f4-53176150b5b6
Received: from ESESSHC023.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg20.mgmt.ericsson.se (Symantec Mail Security) with SMTP id 2A.5B.04853.05167135; Wed,  5 Mar 2014 18:39:28 +0100 (CET)
Received: from ESESSMB205.ericsson.se ([169.254.5.210]) by ESESSHC023.ericsson.se ([153.88.183.87]) with mapi id 14.02.0387.000; Wed, 5 Mar 2014 18:39:28 +0100
From: =?iso-8859-1?Q?Ari_Ker=E4nen?= <ari.keranen@ericsson.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: ICE and offer/answer terminology
Thread-Index: AQHPOJna7SG03fIDLkewtCIdyBCjCw==
Date: Wed, 5 Mar 2014 17:39:26 +0000
Message-ID: <9E803A35-8AF5-4F91-8280-0DD2263B71D5@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.150]
Content-Type: multipart/signed; boundary="Apple-Mail=_F8F84E16-9EAA-4395-BC68-B4BB99E218A3"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrGLMWRmVeSWpSXmKPExsUyM+JvjW5AoniwQfspDYupyx+zODB6LFny kymAMYrLJiU1J7MstUjfLoEr48bOY4wFO0wrHrzaxtzAuNKoi5GTQ0LARGLLuafMELaYxIV7 69m6GLk4hAROMEr0PLzBBOEsZpRY9eA2E0gVm4C9xOQ1HxlBbBEBdYmve3vAuoUFNCU+330E FdeTeDzxA5y99Po9NhCbRUBF4tndTawgNi/QnPMfnrGD2IxAm7+fWgM2n1lAXOLWk/lMEBeJ SDy8eJoNwhaVePn4HyuErSSxYvslRpDjmAWmMEq8a/nCDjFUUOLkzCcsExiFZiGZNQtZ3Swk dRBF2hLLFr5mnsXIAWTrSExeyAgRNpV4ffQjlG0tMePXQTYIW1FiSvdD9gWMHKsYJYtTi4tz 040M9HLTc0v0Uosyk4uL8/P0ilM3MQLj5uCW30Y7GE/usT/EKM3BoiTOe521JkhIID2xJDU7 NbUgtSi+qDQntfgQIxMHp1QDY92Ep8leO3wfNRhcbXshGPP19YaN95tnimjP9+a2WLC3P3CK cv7Jd9vqjvCG50mIzj9wmoV7waqSaju/6JtiCa7L0vyy3F+/eTV3bfIK7bPpERlzmJ5xsLOn vGtk3r0nZ/XyaUqv934T9Ljy/0USY63IF780zRfXnydWWIWv+vpqR+3NJ787e5VYijMSDbWY i4oTAV8PpBZpAgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/7FiwRbIi6O-naX1aqeteG6RdQqQ
Subject: [MMUSIC] ICE and offer/answer terminology
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: Wed, 05 Mar 2014 17:39:34 -0000

--Apple-Mail=_F8F84E16-9EAA-4395-BC68-B4BB99E218A3
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi all,

We didn't have time for this open issue on Monday meeting so we'll take =
it here on the list.

While ICE is no longer bound to SIP and SDP offer/answer, the document =
uses terms "offer" and "answer" heavily, starting in the title ("ICE: A =
Protocol for NAT Traversal for Offer/Answer Protocols") and abstract =
("ICE can be used by any protocol utilizing the offer/answer model =
[...]").

I think we need to update the title and abstract so that it's more clear =
that protocols that don't follow the o/a model are not excluded. Text =
suggestions are welcome. Maybe in title we call this just "ICE: A =
Protocol for NAT Traversal".

Then, throughout the text we need to refer to the exchange of candidates =
somehow. Originally this was referred to as the "SDP offer" and "SDP =
answer". Currently we use "ICE offer" and "ICE answer". My suggestion =
would be to keep the "(ICE) offer/answer" terminology here but clarify =
in the beginning of the document that with the offer and answer we refer =
to the ICE candidate exchange.

Opinions?


Cheers,
Ari=

--Apple-Mail=_F8F84E16-9EAA-4395-BC68-B4BB99E218A3
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIM5zCCBCkw
ggMRoAMCAQICEHUXW0wyaUIpWRrHJ12Tze0wDQYJKoZIhvcNAQEFBQAwOTERMA8GA1UECgwIRXJp
Y3Nzb24xJDAiBgNVBAMMG0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMTAeFw0xMTA4MjkxMDE3
NTVaFw0xNDA4MjkxMDE3NTNaMGQxETAPBgNVBAoMCEVyaWNzc29uMRQwEgYDVQQDDAtBcmkgS2Vy
YW5lbjEQMA4GA1UEBRMHZWFyaWtlcjEnMCUGCSqGSIb3DQEJARYYYXJpLmtlcmFuZW5AZXJpY3Nz
b24uY29tMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCm4x97wE30RDy+zuTcBMTX8qP50L+I
Esx/fO+aFCKlJJtrO1OJaEvX7IGXnYK2ncKwKwxchOWpaDKSqwEf1kH/Eh+d+TGn6x4+gG6HDhHG
sOqRz5NsWPMOpAohgJKKlG4qeeUzKVnWWPmscZD+JvLZI2sNSE+3SEASAFxVbTUrfwIDAQABo4IB
hDCCAYAwgcAGA1UdHwSBuDCBtTCBsqCBr6CBrIY3aHR0cDovL2NybC50cnVzdC50ZWxpYS5jb20v
RXJpY3Nzb25OTEluZGl2aWR1YWxDQTAxLmNybIZxbGRhcDovL2xkYXAudHJ1c3QudGVsaWEuY29t
L2NuPUVyaWNzc29uJTIwTkwlMjBJbmRpdmlkdWFsJTIwQ0EwMSxvPUVyaWNzc29uP2NlcnRpZmlj
YXRlcmV2b2NhdGlvbmxpc3Q7YmluYXJ5P2Jhc2UwIwYDVR0RBBwwGoEYYXJpLmtlcmFuZW5AZXJp
Y3Nzb24uY29tMEYGA1UdIAQ/MD0wOwYGKoVwawEBMDEwLwYIKwYBBQUHAgEWI2h0dHA6Ly93d3cu
ZXJpY3Nzb24uY29tL2xlZ2FsLnNodG1sMB0GA1UdDgQWBBQu6W+n7/tHp8pbgczjKSXcAoV7VTAf
BgNVHSMEGDAWgBSWJ8O43qVfXUQ+OVLlRbF2X2MwmzAOBgNVHQ8BAf8EBAMCBaAwDQYJKoZIhvcN
AQEFBQADggEBAFJiqLOimWRaFtpwgOpZgo/wqN9bPEewLl2z1+iv2WU3DnOGXmf4/e0IgpfvGtJX
gYnGPql87Cd+jIccHRoq2Z83cjcXyoY1TK0tMe4uhHV87UnmEUN5ewlWnyP4rlzBfO/BBTXA5S17
PsogWaaIvuy0IHTkbYj03sZ8nB4O/UDpSj2hfzcycyne0Y7bTEQY/OZRRbC1sWVQEkA8rOrn5+AR
Wc+qrugsgPYi8iamXdzgxJaCDsSTdzC9gQl1h8pwRr64H1ybkD4Y4K6Gri4+AvHHBIWBjQod9vhC
lRnUbFoFnHnhbcT2rg4JPxmjxtCvQ5q9LCTL0EeCOBZWb6WMxMEwggRFMIIDLaADAgECAhATyer/
3iatqdykyiOBg0fjMA0GCSqGSIb3DQEBBQUAMEQxGjAYBgNVBAoMEVRlbGlhU29uZXJhIEdyb3Vw
MSYwJAYDVQQDDB1UZWxpYVNvbmVyYSBQdWJsaWMgUm9vdCBDQSB2MTAeFw0wNjEwMDYxMDAwNTNa
Fw0xNjEwMDIwNTA0MTdaMDkxETAPBgNVBAoMCEVyaWNzc29uMSQwIgYDVQQDDBtFcmljc3NvbiBO
TCBJbmRpdmlkdWFsIENBMDEwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQC2EHfkNR7r
h8Q8jRhZRD8wsbjzxTuVtscq/p6glZzSeEGBXtRwAqmr6jS8FBiKiBMh79ay537m/SwXO3UKUR45
f3YIIp9DjThSd+p2xhG3x4yyc9gczlr8JfOEnPhcdPSKw1P0mUlhUn4ak7t009/Ye/W6x3UZHTwV
IAWILIhSq4hyNE4z+RvOtvB9uwQ86lKcxi0mFoLev7acLjh+ZXHzXx1jHAmF0ZaG79CpbvJcRuWp
lqgJ6qx+hAjsmCU0Wx07GkyGTh8vUMP9Hlz7oyk+7VOccUiNknXHias1GwM9qBUUOj8e/xsnaTP0
ZfqmKBj3Grh1C9WknlSWagxanCBdAgMBAAGjggE8MIIBODASBgNVHRMBAf8ECDAGAQH/AgEAMEYG
A1UdIAQ/MD0wOwYHKoVwIwIBATAwMC4GCCsGAQUFBwIBFiJodHRwczovL3JlcG9zaXRvcnkudHJ1
c3QudGVsaWEuY29tMIGJBgNVHR8EgYEwfzB9oHugeYZ3bGRhcDovL2xkYXAudHJ1c3QudGVsaWEu
Y29tL2NuPVRlbGlhU29uZXJhJTIwUHVibGljJTIwUm9vdCUyMENBJTIwdjEsbz1UZWxpYVNvbmVy
YSUyMEdyb3VwP2F1dGhvcml0eXJldm9jYXRpb25saXN0P2Jhc2UwDgYDVR0PAQH/BAQDAgEGMB0G
A1UdDgQWBBSWJ8O43qVfXUQ+OVLlRbF2X2MwmzAfBgNVHSMEGDAWgBRF2/CPuBpioagjG2OIOKPb
4Bpi8TANBgkqhkiG9w0BAQUFAAOCAQEAdgBKKkM/jN0WvWpZKZ/2J8IVyL+rT44VL0rjbNNDYXdE
/V4ZSFN2uuQmgf1Ckqp2shNLe0NEKt6/sfxit4p/5opPIvzytv6vB7rc2BUs8+jac7aaNiRuwBCj
iT1Wnnm454OOZurzQu0SH81PbBtiwUf4XsEvLOnRRZ+9MO/ecVMCQVmeuzsyCl6yFVbx0zmKW1gP
jBEigF8BYZ1Tjazk1pVcKzFIuB24j1qTpPsUG4HoQhIu5rt3F7GlNV6t5DF7ojbgu1SqKG/JhTva
PUU/nZYqw9rkV8Dabwrt27reisobtPp78tolxio3ZcZVk7HQ8rpV2M/jmAjGfZRVkczCDzCCBG0w
ggNVoAMCAQICEQCcsIwEmsuXInhjYrYbhlo9MA0GCSqGSIb3DQEBBQUAMDoxGTAXBgNVBAoTEFJT
QSBTZWN1cml0eSBJbmMxHTAbBgNVBAsTFFJTQSBTZWN1cml0eSAyMDQ4IFYzMB4XDTA2MTAzMTIw
NDIyN1oXDTE2MTEwMTE1NDIyNVowRDEaMBgGA1UECgwRVGVsaWFTb25lcmEgR3JvdXAxJjAkBgNV
BAMMHVRlbGlhU29uZXJhIFB1YmxpYyBSb290IENBIHYxMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8A
MIIBCgKCAQEAyk8QA2qQgKt5qZV+EeIDbflmXuUChp2lREEsmO5SAiheQ7lXVjzCxw484cOSMw3f
OtGWcf9Fa4Rgdw5j+EgyFgiqNj8b2OTXJHQVj1qf09rmkHTgMIKh6TdKXtV+/43pefVrFmFyhoP/
NVrYe92Sv4HhOxs/T749S1OjeGISzIKKMSpwkvmYweYnFgIPkHdUKUIReOh9Ym6ei7AVg6eejD6Y
PBeV+suzBlXCmC3Zyzj7POLsUVvarNZAaKc0AY+rOUslYfAPo+ZYgwY4IV2KcP/qWhhHahz3khWM
WSniWrZoxCi2JcXGVkSn+N+ir0APYwYTBJsrTDWxonEdZkR+rQIDAQABo4IBYjCCAV4wHwYDVR0j
BBgwFoAUB8NRMKSq6UWuNST6/yQsM9CxnYwwHQYDVR0OBBYEFEXb8I+4GmKhqCMbY4g4o9vgGmLx
MBIGA1UdEwEB/wQIMAYBAf8CAQQwgYUGA1UdIAR+MHwwPQYJKoZIhvcNBQYBMDAwLgYIKwYBBQUH
AgEWImh0dHBzOi8vcmVwb3NpdG9yeS50cnVzdC50ZWxpYS5jb20wOwYHKoVwIwIBATAwMC4GCCsG
AQUFBwIBFiJodHRwczovL3JlcG9zaXRvcnkudHJ1c3QudGVsaWEuY29tMHAGA1UdHwRpMGcwZaBj
oGGGX2h0dHA6Ly93d3cucnNhc2VjdXJpdHkuY29tL3Byb2R1Y3RzL2tlb24vcmVwb3NpdG9yeS9j
ZXJ0aWZpY2F0ZV9zdGF0dXMvUlNBX1NlY3VyaXR5XzIwNDhfdjMuQ1JMMA4GA1UdDwEB/wQEAwIB
BjANBgkqhkiG9w0BAQUFAAOCAQEABF6aLNgpyJu//O9srUqxB1mYL4TlBJFJtuT1n/15FpKONU2i
/byEtUugHVgoTalpp2Ikuxn2iIgzPbNQ+iu4YnVgQzpuOmzXTN2cITMgwn5AyUoHidMPu2Jo7wob
u4Fqg2QrG7WeYANYsQk3Q57mQeuyRkjxluq+93KK2gz/HYjqYkKLjLzOmyrkzwR/9aaC3HLFMbCo
K0NtyQvS1gkW/HGB5GY1xR9SuOE7CJeS53tqE9CSN6cHQNr+ozuKfzix57T/p6Y8D23nTD1GZA2A
pHdy0sY/HNyU8bQPEpTwrSBxNYYeucYoYNSUSJYkqYa6q/ZG38B3XlcT3TiORrQ2DzGCAhIwggIO
AgEBME0wOTERMA8GA1UECgwIRXJpY3Nzb24xJDAiBgNVBAMMG0VyaWNzc29uIE5MIEluZGl2aWR1
YWwgQ0EwMQIQdRdbTDJpQilZGscnXZPN7TAJBgUrDgMCGgUAoIIBGzAYBgkqhkiG9w0BCQMxCwYJ
KoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xNDAzMDUxNzM5MzBaMCMGCSqGSIb3DQEJBDEWBBQ8
Mq+qbbdE84Qg+pyBnmJqbB7mPTBcBgkrBgEEAYI3EAQxTzBNMDkxETAPBgNVBAoMCEVyaWNzc29u
MSQwIgYDVQQDDBtFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBMDECEHUXW0wyaUIpWRrHJ12Tze0w
XgYLKoZIhvcNAQkQAgsxT6BNMDkxETAPBgNVBAoMCEVyaWNzc29uMSQwIgYDVQQDDBtFcmljc3Nv
biBOTCBJbmRpdmlkdWFsIENBMDECEHUXW0wyaUIpWRrHJ12Tze0wDQYJKoZIhvcNAQEBBQAEgYAZ
fuEDBlZ6BaUgJOa0tyzWuoh9EBxc9GIwuBedvG/LZW15bahmPIA0EnGpA6if2ZVYzkTneQpo6ygI
lINDYFOYIu3O1RJNP5nXpEvyHgUzW4xv0gFyl9BdlHj37zlEmI2/5I4L+yx0PX/TkLHW2iE3yTn9
rl7M0xjgTDHIfugKdgAAAAAAAA==

--Apple-Mail=_F8F84E16-9EAA-4395-BC68-B4BB99E218A3--


From nobody Thu Mar  6 01:56:42 2014
Return-Path: <thomas.stach@unify.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 4675C1A01E0 for <mmusic@ietfa.amsl.com>; Thu,  6 Mar 2014 01:56:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.147
X-Spam-Level: 
X-Spam-Status: No, score=-2.147 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.547] autolearn=ham
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 5rjt09udICEu for <mmusic@ietfa.amsl.com>; Thu,  6 Mar 2014 01:56:34 -0800 (PST)
Received: from mx11.unify.com (mx11.unify.com [62.134.46.9]) by ietfa.amsl.com (Postfix) with ESMTP id 204441A01E8 for <mmusic@ietf.org>; Thu,  6 Mar 2014 01:56:34 -0800 (PST)
Received: from MCHP02HTC.global-ad.net (unknown [172.29.42.235]) by mx11.unify.com (Server) with ESMTP id 929441EB8682; Thu,  6 Mar 2014 10:56:29 +0100 (CET)
Received: from MCHP04MSX.global-ad.net ([169.254.1.208]) by MCHP02HTC.global-ad.net ([172.29.42.235]) with mapi id 14.03.0174.001; Thu, 6 Mar 2014 10:56:29 +0100
From: "Stach, Thomas" <thomas.stach@unify.com>
To: =?iso-8859-1?Q?Ari_Ker=E4nen?= <ari.keranen@ericsson.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: ICE and offer/answer terminology
Thread-Index: AQHPOJna7SG03fIDLkewtCIdyBCjC5rT0wUg
Date: Thu, 6 Mar 2014 09:56:28 +0000
Message-ID: <F81CEE99482EFE438DAE2A652361EE1217A5EAC2@MCHP04MSX.global-ad.net>
References: <9E803A35-8AF5-4F91-8280-0DD2263B71D5@ericsson.com>
In-Reply-To: <9E803A35-8AF5-4F91-8280-0DD2263B71D5@ericsson.com>
Accept-Language: de-AT, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.29.42.225]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/So6iEqUkjI8-_JvBHkS8oRArLys
Subject: Re: [MMUSIC] ICE and offer/answer terminology
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: Thu, 06 Mar 2014 09:56:36 -0000

I think this is fine

Regards
Thomas


>=20
> Hi all,
>=20
> We didn't have time for this open issue on Monday meeting so we'll take i=
t
> here on the list.
>=20
> While ICE is no longer bound to SIP and SDP offer/answer, the document us=
es
> terms "offer" and "answer" heavily, starting in the title ("ICE: A Protoc=
ol
> for NAT Traversal for Offer/Answer Protocols") and abstract ("ICE can be =
used
> by any protocol utilizing the offer/answer model [...]").
>=20
> I think we need to update the title and abstract so that it's more clear =
that
> protocols that don't follow the o/a model are not excluded. Text suggesti=
ons
> are welcome. Maybe in title we call this just "ICE: A Protocol for NAT
> Traversal".
>=20
> Then, throughout the text we need to refer to the exchange of candidates
> somehow. Originally this was referred to as the "SDP offer" and "SDP answ=
er".
> Currently we use "ICE offer" and "ICE answer". My suggestion would be to =
keep
> the "(ICE) offer/answer" terminology here but clarify in the beginning of=
 the
> document that with the offer and answer we refer to the ICE candidate
> exchange.
>=20
> Opinions?
>=20
>=20
> Cheers,
> Ari


From nobody Thu Mar  6 03:22:31 2014
Return-Path: <magnus.westerlund@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 2DB3B1A02BA for <mmusic@ietfa.amsl.com>; Thu,  6 Mar 2014 03:22:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham
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 oLxhEgATO8JS for <mmusic@ietfa.amsl.com>; Thu,  6 Mar 2014 03:22:27 -0800 (PST)
Received: from sesbmg20.ericsson.net (sesbmg20.ericsson.net [193.180.251.56]) by ietfa.amsl.com (Postfix) with ESMTP id 3EB951A0272 for <mmusic@ietf.org>; Thu,  6 Mar 2014 03:22:27 -0800 (PST)
X-AuditID: c1b4fb38-b7f418e000001099-fe-53185a6ec533
Received: from ESESSHC021.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg20.ericsson.net (Symantec Mail Security) with SMTP id 98.08.04249.E6A58135; Thu,  6 Mar 2014 12:22:22 +0100 (CET)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.83) with Microsoft SMTP Server id 14.2.347.0; Thu, 6 Mar 2014 12:22:21 +0100
Message-ID: <53185A62.1000504@ericsson.com>
Date: Thu, 6 Mar 2014 11:22:10 +0000
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: "mmusic (E-mail)" <mmusic@ietf.org>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrEJMWRmVeSWpSXmKPExsUyM+JvjW5elESwwfFLFhZTlz9mcWD0WLLk J1MAYxSXTUpqTmZZapG+XQJXxsUTPWwFrVwVp788Zm5gnMrRxcjJISFgInHrx2ZGCFtM4sK9 9WxdjFwcQgJHGCWOfpoE5SxjlDj37jRYFa+AtsTz9n6WLkYODhYBFYktfyRAwmwCFhI3fzSy gdiiAsESOw/8hioXlDg58wkLiC0ioC7RurmPFcQWFvCUuHWjkw1kjISAuERPYxBImFlAT2LK 1RZGCFteonnrbGYQWwhoa0NTB+sERv5ZSKbOQtIyC0nLAkbmVYwcxanFSbnpRgabGIHhdHDL b4sdjJf/2hxilOZgURLn/fjWOUhIID2xJDU7NbUgtSi+qDQntfgQIxMHp1QD47Jbx3UfSjw/ ftuidtM3+Wmvftgp/4nUX+qa5Gn0yiG76dvNzz8CNxXmrGP48FwqRXPC6p4NBYaPzkza1/Hi BvuRK1nfluVL/5Xf4yvbWLmUOfEg0+by4IX3brBO6zc/sFX1rkHzrWjzND+TgM2lezZ4Pl9x kysof+9dwfuF/xZbpywUfiXJY6PEUpyRaKjFXFScCABhTNHW9QEAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/VoYQGx0SDnrL9ZMImuAxsvSnWGI
Subject: [MMUSIC] DSCP and multiplexing in draft-ietf-mmusic-sdp-mux-attributes-01
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: Thu, 06 Mar 2014 11:22:29 -0000

Hi,

This is in regards to Section 14. "Multiplexing Media Streams and DSCP
Markings" as brought up in todays MMUSIC meeting.

My opinion is that this section shouldn't contain normative text if
something is allowed or not. It should bring up that having different
DSCP for packets being transmitted over the same 5-tuple, i.e. what is
being in the same bundle, has issues per the DART document. Thus keeping
this to a high level issue notice.

I don't see the need for this document to discuss DSCP usages associated
with a single "media flow", i.e. a single RTP packet stream, or even a
combination of RTP packet streams that make up a WebRTC MediaStreamTrack
or a SCTP association, or TCP flow. They are up to the individual protocol.

Have I missed some implication here?

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Färögatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From nobody Thu Mar  6 03:27:28 2014
Return-Path: <Christian.Groves@nteczone.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 9D2341A0272 for <mmusic@ietfa.amsl.com>; Thu,  6 Mar 2014 03:27:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.001
X-Spam-Level: 
X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[BAYES_20=-0.001] autolearn=ham
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 P9xaYiqOrRpb for <mmusic@ietfa.amsl.com>; Thu,  6 Mar 2014 03:27:25 -0800 (PST)
Received: from cserver5.myshophosting.com (cserver5.myshophosting.com [175.107.161.1]) by ietfa.amsl.com (Postfix) with ESMTP id 966141A01C9 for <mmusic@ietf.org>; Thu,  6 Mar 2014 03:27:25 -0800 (PST)
Received: from dhcp-a3d5.meeting.ietf.org ([31.133.163.213]:57292 helo=[127.0.0.1]) by cserver5.myshophosting.com with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from <Christian.Groves@nteczone.com>) id 1WLWSN-00033g-Vj for mmusic@ietf.org; Thu, 06 Mar 2014 22:27:20 +1100
Message-ID: <53185B8E.2070808@nteczone.com>
Date: Thu, 06 Mar 2014 22:27:10 +1100
From: Christian Groves <Christian.Groves@nteczone.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: mmusic mailing list <mmusic@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - cserver5.myshophosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - nteczone.com
X-Get-Message-Sender-Via: cserver5.myshophosting.com: authenticated_id: christian.groves@nteczone.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/m7OMrq1RAnY3PT0ITEdtPvVj0jg
Subject: [MMUSIC] SCTP AppID
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: Thu, 06 Mar 2014 11:27:27 -0000

Hello Martin,

When you mentioned ALPN is this the draft you were talking about? 
http://tools.ietf.org/html/draft-ietf-tls-applayerprotoneg-05

Regards,
Christian


From nobody Thu Mar  6 03:28:25 2014
Return-Path: <salvatore.loreto@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 ECCD21A02BA for <mmusic@ietfa.amsl.com>; Thu,  6 Mar 2014 03:28:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham
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 NYpeZKHAVjhg for <mmusic@ietfa.amsl.com>; Thu,  6 Mar 2014 03:28:21 -0800 (PST)
Received: from sesbmg20.ericsson.net (sesbmg20.ericsson.net [193.180.251.56]) by ietfa.amsl.com (Postfix) with ESMTP id 1F7B01A01C9 for <mmusic@ietf.org>; Thu,  6 Mar 2014 03:28:20 -0800 (PST)
X-AuditID: c1b4fb38-b7f418e000001099-1b-53185bd059f9
Received: from ESESSHC013.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg20.ericsson.net (Symantec Mail Security) with SMTP id 81.29.04249.0DB58135; Thu,  6 Mar 2014 12:28:16 +0100 (CET)
Received: from ESESSMB109.ericsson.se ([169.254.9.128]) by ESESSHC013.ericsson.se ([153.88.183.57]) with mapi id 14.02.0387.000; Thu, 6 Mar 2014 12:28:16 +0100
From: Salvatore Loreto <salvatore.loreto@ericsson.com>
To: Christian Groves <Christian.Groves@nteczone.com>
Thread-Topic: [MMUSIC] SCTP AppID
Thread-Index: AQHPOS8NfxpP/0XfyUaZJY1aq+ki1prT2zMA
Date: Thu, 6 Mar 2014 11:28:15 +0000
Message-ID: <C8EB64C0-3140-477C-9373-BD36B4B1A64B@ericsson.com>
References: <53185B8E.2070808@nteczone.com>
In-Reply-To: <53185B8E.2070808@nteczone.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.154]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <844644B463F9B24DB505018B5CC68C72@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrKLMWRmVeSWpSXmKPExsUyM+Jvje6FaIlgg8YPBhZf3jeyWExd/pjF gcljyZKfTB4rzs9kCWCK4rJJSc3JLEst0rdL4MrYNWE5a8Fh5orXs/vZGhi/MXUxcnJICJhI PPj/jB3CFpO4cG89WxcjF4eQwBFGiYubLjBBOIsZJW5/eQFWxSZgJvH84RbmLkYODhGg7vln NUHCzAKaEhO6n7CB2MICChITlv4Gs0UEFCXOX5rPAmEbSRzd8JYVxGYRUJFYNWMl2BG8AvYS XZfWgNlCAtoSsybeYASxOQV0JKad6gfrZQQ67vspiBpmAXGJW0/mQz0gILFkz3lmCFtU4uXj f6wQtpLEotufoep1JBbs/sQGYVtLbOm4DxXXlli28DUzxA2CEidnPmGZwCg+C8mKWUjaZyFp n4WkfRaS9gWMrKsYOYpTi5Ny040MNjECo+rglt8WOxgv/7U5xCjNwaIkzvvxrXOQkEB6Yklq dmpqQWpRfFFpTmrxIUYmDk6pBsbNc69Ou8s27fbUyVcrmuxMZig++Lr4Qck/9riPM3vNb8ju PhR6MGeT9lbPgvC312M3y+xLneUp4q18Y2Ji8JY5Ao4FTlOE2yadcd8gduV2uerv3TprupWt avZl8zxMMvl3+Ljw84O93pL+J2e5ToyVnnH4S9HMrjVGajHpkQV1ot+uhrNunqiqxFKckWio xVxUnAgABSZ9zngCAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/pTeZu8SZ-LYq9AbHt64sZLJGQ5Y
Cc: mmusic mailing list <mmusic@ietf.org>
Subject: Re: [MMUSIC] SCTP AppID
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: Thu, 06 Mar 2014 11:28:24 -0000

yet it is

/Sal

On Mar 6, 2014, at 11:27 AM, Christian Groves <Christian.Groves@nteczone.co=
m>
 wrote:

> Hello Martin,
>=20
> When you mentioned ALPN is this the draft you were talking about? http://=
tools.ietf.org/html/draft-ietf-tls-applayerprotoneg-05
>=20
> Regards,
> Christian
>=20
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic


From nobody Thu Mar  6 05:12:10 2014
Return-Path: <Christian.Groves@nteczone.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 265071A02C4 for <mmusic@ietfa.amsl.com>; Thu,  6 Mar 2014 05:12:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 UvXUzMf2t_Bx for <mmusic@ietfa.amsl.com>; Thu,  6 Mar 2014 05:12:03 -0800 (PST)
Received: from cserver5.myshophosting.com (cserver5.myshophosting.com [175.107.161.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44A3B1A025E for <mmusic@ietf.org>; Thu,  6 Mar 2014 05:12:03 -0800 (PST)
Received: from [130.129.156.216] (port=59562 helo=[127.0.0.1]) by cserver5.myshophosting.com with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from <Christian.Groves@nteczone.com>) id 1WLY5d-0001T0-Co; Fri, 07 Mar 2014 00:11:57 +1100
Message-ID: <53187415.2000108@nteczone.com>
Date: Fri, 07 Mar 2014 00:11:49 +1100
From: Christian Groves <Christian.Groves@nteczone.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Salvatore Loreto <salvatore.loreto@ericsson.com>
References: <53185B8E.2070808@nteczone.com> <C8EB64C0-3140-477C-9373-BD36B4B1A64B@ericsson.com>
In-Reply-To: <C8EB64C0-3140-477C-9373-BD36B4B1A64B@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - cserver5.myshophosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - nteczone.com
X-Get-Message-Sender-Via: cserver5.myshophosting.com: authenticated_id: christian.groves@nteczone.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/bqGytVakwejbpff9kQvAlAU7LEs
Cc: mmusic mailing list <mmusic@ietf.org>
Subject: Re: [MMUSIC] SCTP AppID
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: Thu, 06 Mar 2014 13:12:07 -0000

Hello Salvatore,

OK, I guess one of the RTCweb drafts would then include the request to 
IANA to register an ALPN for the data channel.

One thing I'm still missing is how you specify multiple apps/alpns 
(whatever we're calling them) being used in a single SCTP association, 
without using datachannel?


Christian

On 6/03/2014 10:28 PM, Salvatore Loreto wrote:
> yet it is
>
> /Sal
>
> On Mar 6, 2014, at 11:27 AM, Christian Groves <Christian.Groves@nteczone.com>
>   wrote:
>
>> Hello Martin,
>>
>> When you mentioned ALPN is this the draft you were talking about? http://tools.ietf.org/html/draft-ietf-tls-applayerprotoneg-05
>>
>> Regards,
>> Christian
>>
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www.ietf.org/mailman/listinfo/mmusic
>


From nobody Thu Mar  6 05:17:53 2014
Return-Path: <internet-drafts@ietf.org>
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 3415F1A01F3; Thu,  6 Mar 2014 05:17:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 m6rewMQPek6I; Thu,  6 Mar 2014 05:17:45 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 79EB31A004C; Thu,  6 Mar 2014 05:17:45 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.1.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140306131745.12359.94750.idtracker@ietfa.amsl.com>
Date: Thu, 06 Mar 2014 05:17:45 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/nOPrZ2OQPcYH76675Co0fgefNCg
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D Action: draft-ietf-mmusic-msid-05.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
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: Thu, 06 Mar 2014 13:17:48 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Multiparty Multimedia Session Control Working Group of the IETF.

        Title           : WebRTC MediaStream Identification in the Session Description Protocol
        Author          : Harald Alvestrand
	Filename        : draft-ietf-mmusic-msid-05.txt
	Pages           : 15
	Date            : 2014-03-06

Abstract:
   This document specifies a grouping mechanism for RTP media streams
   that can be used to specify relations between media streams.

   This mechanism is used to signal the association between the SDP
   concept of "m-line" and the WebRTC concept of "MediaStream" /
   "MediaStreamTrack" using SDP signaling.

   This document is a work item of the MMUSIC WG, whose discussion list
   is mmusic@ietf.org.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-mmusic-msid/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-mmusic-msid-05

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-msid-05


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Thu Mar  6 05:19:47 2014
Return-Path: <harald@alvestrand.no>
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 B003E1A02CD for <mmusic@ietfa.amsl.com>; Thu,  6 Mar 2014 05:19:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level: 
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547] autolearn=ham
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 hDW6J1uMUHBW for <mmusic@ietfa.amsl.com>; Thu,  6 Mar 2014 05:19:39 -0800 (PST)
Received: from mork.alvestrand.no (mork.alvestrand.no [158.38.152.117]) by ietfa.amsl.com (Postfix) with ESMTP id 16EEC1A017A for <mmusic@ietf.org>; Thu,  6 Mar 2014 05:19:39 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mork.alvestrand.no (Postfix) with ESMTP id 78FA37C321D for <mmusic@ietf.org>; Thu,  6 Mar 2014 14:19:34 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at alvestrand.no
Received: from mork.alvestrand.no ([127.0.0.1]) by localhost (mork.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g5gUh4jkkrQt for <mmusic@ietf.org>; Thu,  6 Mar 2014 14:19:34 +0100 (CET)
Received: from [31.133.178.19] (dhcp-b213.meeting.ietf.org [31.133.178.19]) by mork.alvestrand.no (Postfix) with ESMTPSA id B77037C321B for <mmusic@ietf.org>; Thu,  6 Mar 2014 14:19:33 +0100 (CET)
Message-ID: <531875E3.9000605@alvestrand.no>
Date: Thu, 06 Mar 2014 14:19:31 +0100
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: mmusic <mmusic@ietf.org>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/TLx_5kkRLo0z358u1VZU_EXkTIk
Subject: [MMUSIC] Updated MSID draft
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: Thu, 06 Mar 2014 13:19:42 -0000

I have uploaded an updated msid draft, without the msid-control: section.

As I said in the WG meeting, I think this is now uncontroversial, and
should be ready for WG Last Call.

I request that the WG chairs consider whether they agree with this opinion.

-- 
Surveillance is pervasive. Go Dark.


From nobody Thu Mar  6 05:25:46 2014
Return-Path: <harald@alvestrand.no>
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 581131A01FE for <mmusic@ietfa.amsl.com>; Thu,  6 Mar 2014 05:25:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.446
X-Spam-Level: 
X-Spam-Status: No, score=-2.446 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.547] autolearn=ham
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 tg3BT0yNvlXp for <mmusic@ietfa.amsl.com>; Thu,  6 Mar 2014 05:25:40 -0800 (PST)
Received: from mork.alvestrand.no (mork.alvestrand.no [158.38.152.117]) by ietfa.amsl.com (Postfix) with ESMTP id 2DF881A019D for <mmusic@ietf.org>; Thu,  6 Mar 2014 05:25:40 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mork.alvestrand.no (Postfix) with ESMTP id E748B7C321B for <mmusic@ietf.org>; Thu,  6 Mar 2014 14:25:35 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at alvestrand.no
Received: from mork.alvestrand.no ([127.0.0.1]) by localhost (mork.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2SneZ-2u8cbe for <mmusic@ietf.org>; Thu,  6 Mar 2014 14:25:35 +0100 (CET)
Received: from [31.133.178.19] (dhcp-b213.meeting.ietf.org [31.133.178.19]) by mork.alvestrand.no (Postfix) with ESMTPSA id E60F77C3218 for <mmusic@ietf.org>; Thu,  6 Mar 2014 14:25:34 +0100 (CET)
Message-ID: <5318774D.5090705@alvestrand.no>
Date: Thu, 06 Mar 2014 14:25:33 +0100
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: mmusic@ietf.org
References: <9E803A35-8AF5-4F91-8280-0DD2263B71D5@ericsson.com>
In-Reply-To: <9E803A35-8AF5-4F91-8280-0DD2263B71D5@ericsson.com>
X-Enigmail-Version: 1.6
Content-Type: multipart/alternative; boundary="------------070000020608060406040001"
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/ovJyCPS2M6oZ_MRucEOifm5tYYg
Subject: Re: [MMUSIC] ICE and offer/answer terminology
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: Thu, 06 Mar 2014 13:25:42 -0000

This is a multi-part message in MIME format.
--------------070000020608060406040001
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit

On 03/05/2014 06:39 PM, Ari Keränen wrote:
> Hi all,
>
> We didn't have time for this open issue on Monday meeting so we'll take it here on the list.
>
> While ICE is no longer bound to SIP and SDP offer/answer, the document uses terms "offer" and "answer" heavily, starting in the title ("ICE: A Protocol for NAT Traversal for Offer/Answer Protocols") and abstract ("ICE can be used by any protocol utilizing the offer/answer model [...]").
>
> I think we need to update the title and abstract so that it's more clear that protocols that don't follow the o/a model are not excluded. Text suggestions are welcome. Maybe in title we call this just "ICE: A Protocol for NAT Traversal".
>
> Then, throughout the text we need to refer to the exchange of candidates somehow. Originally this was referred to as the "SDP offer" and "SDP answer". Currently we use "ICE offer" and "ICE answer". My suggestion would be to keep the "(ICE) offer/answer" terminology here but clarify in the beginning of the document that with the offer and answer we refer to the ICE candidate exchange.
>
> Opinions?

Given that we do not have any requirement that exchange of candidates
happen in a particular sequence, I suggest that we call this "exchange
of candidates", not "offer/answer".

Examples of models where offer/answer would be a misnomer:

- All participants write their candidates into a common server-side
store; participants wishing to communicate fetch the candidate sets for
the entities they wish to communicate with, as long as the candidate set
is fresh enough.

- Trickle ICE


>
>
> Cheers,
> Ari
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic


-- 
Surveillance is pervasive. Go Dark.


--------------070000020608060406040001
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 03/05/2014 06:39 PM, Ari Ker&auml;nen
      wrote:<br>
    </div>
    <blockquote
      cite="mid:9E803A35-8AF5-4F91-8280-0DD2263B71D5@ericsson.com"
      type="cite">
      <pre wrap="">Hi all,

We didn't have time for this open issue on Monday meeting so we'll take it here on the list.

While ICE is no longer bound to SIP and SDP offer/answer, the document uses terms "offer" and "answer" heavily, starting in the title ("ICE: A Protocol for NAT Traversal for Offer/Answer Protocols") and abstract ("ICE can be used by any protocol utilizing the offer/answer model [...]").

I think we need to update the title and abstract so that it's more clear that protocols that don't follow the o/a model are not excluded. Text suggestions are welcome. Maybe in title we call this just "ICE: A Protocol for NAT Traversal".

Then, throughout the text we need to refer to the exchange of candidates somehow. Originally this was referred to as the "SDP offer" and "SDP answer". Currently we use "ICE offer" and "ICE answer". My suggestion would be to keep the "(ICE) offer/answer" terminology here but clarify in the beginning of the document that with the offer and answer we refer to the ICE candidate exchange.

Opinions?</pre>
    </blockquote>
    <br>
    Given that we do not have any requirement that exchange of
    candidates happen in a particular sequence, I suggest that we call
    this "exchange of candidates", not "offer/answer".<br>
    <br>
    Examples of models where offer/answer would be a misnomer:<br>
    <br>
    - All participants write their candidates into a common server-side
    store; participants wishing to communicate fetch the candidate sets
    for the entities they wish to communicate with, as long as the
    candidate set is fresh enough.<br>
    <br>
    - Trickle ICE<br>
    <br>
    <br>
    <blockquote
      cite="mid:9E803A35-8AF5-4F91-8280-0DD2263B71D5@ericsson.com"
      type="cite">
      <pre wrap="">


Cheers,
Ari</pre>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
mmusic mailing list
<a class="moz-txt-link-abbreviated" href="mailto:mmusic@ietf.org">mmusic@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/mmusic">https://www.ietf.org/mailman/listinfo/mmusic</a>
</pre>
    </blockquote>
    <br>
    <br>
    <pre class="moz-signature" cols="72">-- 
Surveillance is pervasive. Go Dark.
</pre>
  </body>
</html>

--------------070000020608060406040001--


From nobody Thu Mar  6 05:25:59 2014
Return-Path: <fandreas@cisco.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 3AE7B1A0282 for <mmusic@ietfa.amsl.com>; Thu,  6 Mar 2014 05:25:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.048
X-Spam-Level: 
X-Spam-Status: No, score=-10.048 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 gU1S1l2GWbgu for <mmusic@ietfa.amsl.com>; Thu,  6 Mar 2014 05:25:49 -0800 (PST)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) by ietfa.amsl.com (Postfix) with ESMTP id A07811A0228 for <mmusic@ietf.org>; Thu,  6 Mar 2014 05:25:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=587; q=dns/txt; s=iport; t=1394112346; x=1395321946; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=hBxoCvg7A7p8qei/2BtQ2Ko0vX9KHnChFwdmJ2Ys3Vs=; b=WUm8tDAGB4L/SRJnNvts6oGWBch+ZbI+qdqPkRrwSxnNccxJGNf3GP5R D7G2JdfQ6MQL1yKoXxEAHyN8U8N8URWiQhd3LLnkR9sUSU2E5Ib97hQsO XbIs/A3xH1tzv1Nm82rDesyen4UBOC3FRdj3i9RW73bGcNgK5ERFZrKh7 M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AiEFAHJ2GFOtJXHA/2dsb2JhbABagwbCJwqBExZ0giUBAQEEOEARCxgJFg8JAwIBAgFFBgEMCAEBh3XPIReOYoQ4AQOJTI5ykiuDSx4
X-IronPort-AV: E=Sophos;i="4.97,600,1389744000"; d="scan'208";a="25389499"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by alln-iport-7.cisco.com with ESMTP; 06 Mar 2014 13:25:45 +0000
Received: from Flemmings-MacBook-Pro.local ([10.86.244.133]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id s26DPi0w028311; Thu, 6 Mar 2014 13:25:44 GMT
Message-ID: <53187758.1080403@cisco.com>
Date: Thu, 06 Mar 2014 08:25:44 -0500
From: Flemming Andreasen <fandreas@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Harald Alvestrand <harald@alvestrand.no>, mmusic <mmusic@ietf.org>
References: <531875E3.9000605@alvestrand.no>
In-Reply-To: <531875E3.9000605@alvestrand.no>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/F7TBmV0mDJOCQXBOnGyvQ8yK9iE
Subject: Re: [MMUSIC] Updated MSID draft
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: Thu, 06 Mar 2014 13:25:51 -0000

I think the draft needs a bit more work in a few places (largely 
editorial and more text on some of the procedures). I'll sign up to do a 
pre-WGLC individual review to get you some more tangible and 
constructive feedback on that.

Thanks

-- Flemming


On 3/6/14, 8:19 AM, Harald Alvestrand wrote:
> I have uploaded an updated msid draft, without the msid-control: section.
>
> As I said in the WG meeting, I think this is now uncontroversial, and
> should be ready for WG Last Call.
>
> I request that the WG chairs consider whether they agree with this opinion.
>


From nobody Thu Mar  6 05:36:30 2014
Return-Path: <salvatore.loreto@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 AF7231A0300 for <mmusic@ietfa.amsl.com>; Thu,  6 Mar 2014 05:36:21 -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 uRkCrU02Xw4x for <mmusic@ietfa.amsl.com>; Thu,  6 Mar 2014 05:36:20 -0800 (PST)
Received: from sessmg20.mgmt.ericsson.se (sessmg20.ericsson.net [193.180.251.50]) by ietfa.amsl.com (Postfix) with ESMTP id 8BB9F1A0307 for <mmusic@ietf.org>; Thu,  6 Mar 2014 05:36:19 -0800 (PST)
X-AuditID: c1b4fb32-b7f4c8e0000012f5-9e-531879ce471b
Received: from ESESSHC014.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg20.mgmt.ericsson.se (Symantec Mail Security) with SMTP id 0A.8C.04853.EC978135; Thu,  6 Mar 2014 14:36:15 +0100 (CET)
Received: from ESESSMB109.ericsson.se ([169.254.9.128]) by ESESSHC014.ericsson.se ([153.88.183.60]) with mapi id 14.02.0387.000; Thu, 6 Mar 2014 14:36:14 +0100
From: Salvatore Loreto <salvatore.loreto@ericsson.com>
To: Christian Groves <Christian.Groves@nteczone.com>
Thread-Topic: [MMUSIC] SCTP AppID
Thread-Index: AQHPOS8NfxpP/0XfyUaZJY1aq+ki1prT2zMAgAAc74CAAAbSAA==
Date: Thu, 6 Mar 2014 13:36:13 +0000
Message-ID: <C1D662DF-E3E3-45CD-991F-8090CD7130E0@ericsson.com>
References: <53185B8E.2070808@nteczone.com> <C8EB64C0-3140-477C-9373-BD36B4B1A64B@ericsson.com> <53187415.2000108@nteczone.com>
In-Reply-To: <53187415.2000108@nteczone.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.149]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <495AA47A7DF45C4999F982D70C778467@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrKLMWRmVeSWpSXmKPExsUyM+Jvje75Solgg5mKFl/eN7JYTF3+mMWB yWPJkp9MHivOz2QJYIrisklJzcksSy3St0vgyjh2fi1LwQ3eiq83D7M1MP7g6mLk5JAQMJH4 sOc4E4QtJnHh3nq2LkYuDiGBE4wS+2efgnIWM0pcnDoJrIpNwEzi+cMtzF2MHBwiQN3zz2qC hJkFNCUmdD9hA7GFBRQkJiz9DWaLCChKnL80nwWi3Eli65pIkDCLgIrEqWOPWEBsXgF7idaO S6wQq5oZJT5eO8MIkuAU0JG41v+SHcRmBDru+6k1TBC7xCVuPZkPdbSAxJI955khbFGJl4// sULYShJrD29ngajXk7gxdQobhG0tMavpFiOErS2xbOFrZogjBCVOznzCMoFRfBaSFbOQtM9C 0j4LSfssJO0LGFlXMUoWpxYX56YbGejlpueW6KUWZSYXF+fn6RWnbmIERt3BLb+NdjCe3GN/ iFGag0VJnPc6a02QkEB6YklqdmpqQWpRfFFpTmrxIUYmDk6pBsadzB856mMyHdO6JOVufBIK mmeyqeXj1ru8x3hlz5Z5rlC1iXxuoqd+d3LtDde/4VlOs29skP/8ZHp158N9AtGZO6WWSeQw TdJ7KdgzQ/rm+iQ5jYdX7Jxeibw16Pj40jvuZkErZ1zV3YJTpWXsTe4bN6fv67VI3Sv0Y8/i mOvmXWzvLN9O0FNiKc5INNRiLipOBABmeD0OiAIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/6twhyg7Prc8jl1ZoekCJR1ZW-pc
Cc: mmusic mailing list <mmusic@ietf.org>
Subject: Re: [MMUSIC] SCTP AppID
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: Thu, 06 Mar 2014 13:36:21 -0000

Hi Christian

to be clear I don't think to register an ALPN for data channel is the right=
 solution=20

I understood Martin was only proposing to look at how ALPN defines and hand=
les the registry
and do something similar not using it. Am I wrong?
IMO ALPN parameter defines the protocol that will run on top of TLS (not su=
re it can be used for DTLS to)
We are running SCTP over DTLS, so we could use it at least to say SCTP

the app parameter is trying to define how SCTP streams are handled here
i.e. "data channel" is a pair of one incoming stream and one outgoing SCTP=
=20
stream having the same stream SCTP identifier.

the protocol or better subprotocol will run then on top of the data channel

/Sal


On Mar 6, 2014, at 1:11 PM, Christian Groves <Christian.Groves@nteczone.com=
>
 wrote:

> Hello Salvatore,
>=20
> OK, I guess one of the RTCweb drafts would then include the request to IA=
NA to register an ALPN for the data channel.
>=20
> One thing I'm still missing is how you specify multiple apps/alpns (whate=
ver we're calling them) being used in a single SCTP association, without us=
ing datachannel?
>=20
>=20
> Christian
>=20
> On 6/03/2014 10:28 PM, Salvatore Loreto wrote:
>> yet it is
>>=20
>> /Sal
>>=20
>> On Mar 6, 2014, at 11:27 AM, Christian Groves <Christian.Groves@nteczone=
.com>
>>  wrote:
>>=20
>>> Hello Martin,
>>>=20
>>> When you mentioned ALPN is this the draft you were talking about? http:=
//tools.ietf.org/html/draft-ietf-tls-applayerprotoneg-05
>>>=20
>>> Regards,
>>> Christian
>>>=20
>>> _______________________________________________
>>> mmusic mailing list
>>> mmusic@ietf.org
>>> https://www.ietf.org/mailman/listinfo/mmusic
>>=20
>=20


From nobody Thu Mar  6 05:48:14 2014
Return-Path: <juberti@google.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 0AD801A01FE for <mmusic@ietfa.amsl.com>; Thu,  6 Mar 2014 05:48:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.925
X-Spam-Level: 
X-Spam-Status: No, score=-1.925 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001] autolearn=ham
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 fE0xSCKi2T9z for <mmusic@ietfa.amsl.com>; Thu,  6 Mar 2014 05:48:07 -0800 (PST)
Received: from mail-ve0-x232.google.com (mail-ve0-x232.google.com [IPv6:2607:f8b0:400c:c01::232]) by ietfa.amsl.com (Postfix) with ESMTP id 48D191A019C for <mmusic@ietf.org>; Thu,  6 Mar 2014 05:48:07 -0800 (PST)
Received: by mail-ve0-f178.google.com with SMTP id jw12so2590722veb.37 for <mmusic@ietf.org>; Thu, 06 Mar 2014 05:48:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=vDkH00FezZzie/bNBfqyNPekrkAHe6iBRmQwsN8/ejA=; b=nNltxx+Sf22NNevKOzYvGWYx6560HvElXW9pUOFSE+2b0U2hN/TePlvidL5zgPJeDe +MEzW1QgZqPQFbroppvnqHP9QxaaiLoRXA5McOacXIU4Phrz7wxT2eU2WTpgPmv1kY5v xLws/3FAUHC/+ZZ11hCphGTqie2XrDEIjoHK6EtBDgB52oBOpOnmZU50tqAWhbjA7rST PmKo33ilnjUqhKQRaak5WccpbP+o8q9H/tadm200BdlPPpNVFDEuyHeh4uOdqMOLZKBH abVrRIaq0RorMOw2K/bYxOYyxw5uoPx0kdOXgbaAZpnEIsVZMK0pIvm2ZSZZzCAUQIsY L+iA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=vDkH00FezZzie/bNBfqyNPekrkAHe6iBRmQwsN8/ejA=; b=J/HAoLOKwLDt/VWBDv1r1M2Wv++tzm6FGQrNgY+vXFWQQEl74iB+4awM4z9J+e/l6b Jr1/zN2tU33jaNzunj0KOfTahldFAwpbdVOtENCni/C0wEN1x9RqFIPrPR3a0mxiZpaq guPCNfTxL/rCBdWzeMTZ58139zvApsyhcTXwd4JOY36VOjRiivkpGI06FOoHiDY4mnzL Hoa9XT2mmDH7ar0nE9DkKYy9eCpZcnfrN7qBjZoZNc6p3eHFY2L5dsH3w9rS3aCgbigh SLb+xLhKiLgxK8qzCFGqAw45+SkH8UNWHnGX53shQVDm6y++/rZMIn0cvTEsu7KJ+hCf gXfQ==
X-Gm-Message-State: ALoCoQluEKqRXEwIOz2ZVlOyhZ3d3ZtW7D16skYygmlSfagaO/fgCz5MxogYcLjGDpp/AnBXTd06ge7UehmVAp7A6mERaB7JE0M76UBCDP2CkO/HAlzyavkrQX3jsauXkUupXIZgFNkHx8ZfD0rm/jR8trRoAqsDNCF6eJE9hsX++A+Ik+OUozhUxLQytnlgp+XqWied5DFy
X-Received: by 10.58.201.5 with SMTP id jw5mr5247356vec.6.1394113682930; Thu, 06 Mar 2014 05:48:02 -0800 (PST)
MIME-Version: 1.0
Received: by 10.52.26.43 with HTTP; Thu, 6 Mar 2014 05:47:42 -0800 (PST)
In-Reply-To: <5318774D.5090705@alvestrand.no>
References: <9E803A35-8AF5-4F91-8280-0DD2263B71D5@ericsson.com> <5318774D.5090705@alvestrand.no>
From: Justin Uberti <juberti@google.com>
Date: Thu, 6 Mar 2014 13:47:42 +0000
Message-ID: <CAOJ7v-3gFQ=xvz9=ZzZ23m+CvbKgK2OPpxPv9h56qFwNoXg9GQ@mail.gmail.com>
To: Harald Alvestrand <harald@alvestrand.no>
Content-Type: multipart/alternative; boundary=047d7bd6aea2d91c6404f3f0626b
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/B0op2fiqvxwfKPK6nvDhfcqNL_0
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] ICE and offer/answer terminology
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: Thu, 06 Mar 2014 13:48:10 -0000

--047d7bd6aea2d91c6404f3f0626b
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

The ICE ufrag/pwd and options do need to be exchanged somehow, but we could
just call them the local and remote ICE configurations.


On Thu, Mar 6, 2014 at 1:25 PM, Harald Alvestrand <harald@alvestrand.no>wro=
te:

>  On 03/05/2014 06:39 PM, Ari Ker=C3=A4nen wrote:
>
> Hi all,
>
> We didn't have time for this open issue on Monday meeting so we'll take i=
t here on the list.
>
> While ICE is no longer bound to SIP and SDP offer/answer, the document us=
es terms "offer" and "answer" heavily, starting in the title ("ICE: A Proto=
col for NAT Traversal for Offer/Answer Protocols") and abstract ("ICE can b=
e used by any protocol utilizing the offer/answer model [...]").
>
> I think we need to update the title and abstract so that it's more clear =
that protocols that don't follow the o/a model are not excluded. Text sugge=
stions are welcome. Maybe in title we call this just "ICE: A Protocol for N=
AT Traversal".
>
> Then, throughout the text we need to refer to the exchange of candidates =
somehow. Originally this was referred to as the "SDP offer" and "SDP answer=
". Currently we use "ICE offer" and "ICE answer". My suggestion would be to=
 keep the "(ICE) offer/answer" terminology here but clarify in the beginnin=
g of the document that with the offer and answer we refer to the ICE candid=
ate exchange.
>
> Opinions?
>
>
> Given that we do not have any requirement that exchange of candidates
> happen in a particular sequence, I suggest that we call this "exchange of
> candidates", not "offer/answer".
>
> Examples of models where offer/answer would be a misnomer:
>
> - All participants write their candidates into a common server-side store=
;
> participants wishing to communicate fetch the candidate sets for the
> entities they wish to communicate with, as long as the candidate set is
> fresh enough.
>
> - Trickle ICE
>
>
>
>
>
> Cheers,
> Ari
>
>
>
> _______________________________________________
> mmusic mailing listmmusic@ietf.orghttps://www.ietf.org/mailman/listinfo/m=
music
>
>
>
> --
> Surveillance is pervasive. Go Dark.
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>
>

--047d7bd6aea2d91c6404f3f0626b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">The ICE ufrag/pwd and options do need to be exchanged some=
how, but we could just call them the local and remote ICE configurations.</=
div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Thu, M=
ar 6, 2014 at 1:25 PM, Harald Alvestrand <span dir=3D"ltr">&lt;<a href=3D"m=
ailto:harald@alvestrand.no" target=3D"_blank">harald@alvestrand.no</a>&gt;<=
/span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
 =20
   =20
 =20
  <div bgcolor=3D"#FFFFFF" text=3D"#000000"><div><div class=3D"h5">
    <div>On 03/05/2014 06:39 PM, Ari Ker=C3=A4nen
      wrote:<br>
    </div>
    <blockquote type=3D"cite">
      <pre>Hi all,

We didn&#39;t have time for this open issue on Monday meeting so we&#39;ll =
take it here on the list.

While ICE is no longer bound to SIP and SDP offer/answer, the document uses=
 terms &quot;offer&quot; and &quot;answer&quot; heavily, starting in the ti=
tle (&quot;ICE: A Protocol for NAT Traversal for Offer/Answer Protocols&quo=
t;) and abstract (&quot;ICE can be used by any protocol utilizing the offer=
/answer model [...]&quot;).

I think we need to update the title and abstract so that it&#39;s more clea=
r that protocols that don&#39;t follow the o/a model are not excluded. Text=
 suggestions are welcome. Maybe in title we call this just &quot;ICE: A Pro=
tocol for NAT Traversal&quot;.

Then, throughout the text we need to refer to the exchange of candidates so=
mehow. Originally this was referred to as the &quot;SDP offer&quot; and &qu=
ot;SDP answer&quot;. Currently we use &quot;ICE offer&quot; and &quot;ICE a=
nswer&quot;. My suggestion would be to keep the &quot;(ICE) offer/answer&qu=
ot; terminology here but clarify in the beginning of the document that with=
 the offer and answer we refer to the ICE candidate exchange.

Opinions?</pre>
    </blockquote>
    <br></div></div>
    Given that we do not have any requirement that exchange of
    candidates happen in a particular sequence, I suggest that we call
    this &quot;exchange of candidates&quot;, not &quot;offer/answer&quot;.<=
br>
    <br>
    Examples of models where offer/answer would be a misnomer:<br>
    <br>
    - All participants write their candidates into a common server-side
    store; participants wishing to communicate fetch the candidate sets
    for the entities they wish to communicate with, as long as the
    candidate set is fresh enough.<br>
    <br>
    - Trickle ICE<div class=3D""><br>
    <br>
    <br>
    <blockquote type=3D"cite">
      <pre>

Cheers,
Ari</pre>
      <br>
      <fieldset></fieldset>
      <br>
      <pre>_______________________________________________
mmusic mailing list
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/mmusic</a>
</pre>
    </blockquote>
    <br>
    <br>
    </div><span class=3D"HOEnZb"><font color=3D"#888888"><pre cols=3D"72">-=
-=20
Surveillance is pervasive. Go Dark.
</pre>
  </font></span></div>

<br>_______________________________________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/mmusic</a><br>
<br></blockquote></div><br></div>

--047d7bd6aea2d91c6404f3f0626b--


From nobody Thu Mar  6 06:02:28 2014
Return-Path: <jonathan@vidyo.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 F1A3D1A01FE for <mmusic@ietfa.amsl.com>; Thu,  6 Mar 2014 06:02:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 9XEbbltspEq5 for <mmusic@ietfa.amsl.com>; Thu,  6 Mar 2014 06:02:20 -0800 (PST)
Received: from server209.appriver.com (server209e.appriver.com [8.31.233.120]) by ietfa.amsl.com (Postfix) with ESMTP id 963651A010A for <mmusic@ietf.org>; Thu,  6 Mar 2014 06:02:16 -0800 (PST)
X-Note-AR-ScanTimeLocal: 3/6/2014 9:02:11 AM
X-Policy: GLOBAL - vidyo.com
X-Policy: GLOBAL - vidyo.com
X-Policy: GLOBAL - vidyo.com
X-Primary: jonathan@vidyo.com
X-Note: This Email was scanned by AppRiver SecureTide
X-Virus-Scan: V-
X-Note-SnifferID: 0
X-Note: TCH-CT/SI:0-240/SG:5 3/6/2014 9:01:34 AM
X-GBUdb-Analysis: 0, 162.209.16.213, Ugly c=0.909734 p=-0.983585 Source White
X-Signature-Violations: 0-0-0-13157-c
X-Note-419: 15.6003 ms. Fail:0 Chk:1345 of 1345 total
X-Note: SCH-CT/SI:0-1345/SG:1 3/6/2014 9:02:01 AM
X-Note: Spam Tests Failed: 
X-Country-Path: ->UNITED STATES->LOCAL
X-Note-Sending-IP: 162.209.16.213
X-Note-Reverse-DNS: mail2.vidyo.com
X-Note-Return-Path: jonathan@vidyo.com
X-Note: User Rule Hits: 
X-Note: Global Rule Hits: G327 G328 G329 G330 G334 G335 G445 
X-Note: Encrypt Rule Hits: 
X-Note: Mail Class: VALID
X-Note: Headers Injected
Received: from [162.209.16.213] (HELO mail.vidyo.com) by server209.appriver.com (CommuniGate Pro SMTP 6.0.8) with ESMTPS id 77806403; Thu, 06 Mar 2014 09:02:11 -0500
Received: from 492133-EXCH2.vidyo.com ([fe80::50:56ff:fe85:6b62]) by 492132-EXCH1.vidyo.com ([fe80::50:56ff:fe85:4f77%13]) with mapi id 14.03.0146.000; Thu, 6 Mar 2014 08:02:11 -0600
From: Jonathan Lennox <jonathan@vidyo.com>
To: Justin Uberti <juberti@google.com>
Thread-Topic: [MMUSIC] ICE and offer/answer terminology
Thread-Index: AQHPOUPOzZRLuYuucU65lvAKc0ogTZrUe2IA
Date: Thu, 6 Mar 2014 14:02:10 +0000
Message-ID: <7A2DF86F-A968-4C02-819B-5CBE29CCA0F3@vidyo.com>
References: <9E803A35-8AF5-4F91-8280-0DD2263B71D5@ericsson.com> <5318774D.5090705@alvestrand.no> <CAOJ7v-3gFQ=xvz9=ZzZ23m+CvbKgK2OPpxPv9h56qFwNoXg9GQ@mail.gmail.com>
In-Reply-To: <CAOJ7v-3gFQ=xvz9=ZzZ23m+CvbKgK2OPpxPv9h56qFwNoXg9GQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [31.133.187.226]
Content-Type: multipart/alternative; boundary="_000_7A2DF86FA9684C02819B5CBE29CCA0F3vidyocom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/N_ysMmL2T02P8sYHJfyMhwaHWuY
Cc: mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] ICE and offer/answer terminology
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: Thu, 06 Mar 2014 14:02:25 -0000

--_000_7A2DF86FA9684C02819B5CBE29CCA0F3vidyocom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

There also needs to be the decision about who=92s the controlling endpoint =
by default.

On Mar 6, 2014, at 1:47 PM, Justin Uberti <juberti@google.com<mailto:jubert=
i@google.com>> wrote:

The ICE ufrag/pwd and options do need to be exchanged somehow, but we could=
 just call them the local and remote ICE configurations.


On Thu, Mar 6, 2014 at 1:25 PM, Harald Alvestrand <harald@alvestrand.no<mai=
lto:harald@alvestrand.no>> wrote:
On 03/05/2014 06:39 PM, Ari Ker=E4nen wrote:

Hi all,

We didn't have time for this open issue on Monday meeting so we'll take it =
here on the list.

While ICE is no longer bound to SIP and SDP offer/answer, the document uses=
 terms "offer" and "answer" heavily, starting in the title ("ICE: A Protoco=
l for NAT Traversal for Offer/Answer Protocols") and abstract ("ICE can be =
used by any protocol utilizing the offer/answer model [...]").

I think we need to update the title and abstract so that it's more clear th=
at protocols that don't follow the o/a model are not excluded. Text suggest=
ions are welcome. Maybe in title we call this just "ICE: A Protocol for NAT=
 Traversal".

Then, throughout the text we need to refer to the exchange of candidates so=
mehow. Originally this was referred to as the "SDP offer" and "SDP answer".=
 Currently we use "ICE offer" and "ICE answer". My suggestion would be to k=
eep the "(ICE) offer/answer" terminology here but clarify in the beginning =
of the document that with the offer and answer we refer to the ICE candidat=
e exchange.

Opinions?

Given that we do not have any requirement that exchange of candidates happe=
n in a particular sequence, I suggest that we call this "exchange of candid=
ates", not "offer/answer".

Examples of models where offer/answer would be a misnomer:

- All participants write their candidates into a common server-side store; =
participants wishing to communicate fetch the candidate sets for the entiti=
es they wish to communicate with, as long as the candidate set is fresh eno=
ugh.

- Trickle ICE





Cheers,
Ari



_______________________________________________
mmusic mailing list
mmusic@ietf.org<mailto:mmusic@ietf.org>
https://www.ietf.org/mailman/listinfo/mmusic




--
Surveillance is pervasive. Go Dark.


_______________________________________________
mmusic mailing list
mmusic@ietf.org<mailto:mmusic@ietf.org>
https://www.ietf.org/mailman/listinfo/mmusic


_______________________________________________
mmusic mailing list
mmusic@ietf.org<mailto:mmusic@ietf.org>
https://www.ietf.org/mailman/listinfo/mmusic


--_000_7A2DF86FA9684C02819B5CBE29CCA0F3vidyocom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <A1712F3D4A2C3A4EBE9511C762DE7F42@vidyo.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space;">
<div>There also needs to be the decision about who=92s the controlling endp=
oint by default.</div>
<br>
<div>
<div>On Mar 6, 2014, at 1:47 PM, Justin Uberti &lt;<a href=3D"mailto:jubert=
i@google.com">juberti@google.com</a>&gt; wrote:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite">
<div dir=3D"ltr">The ICE ufrag/pwd and options do need to be exchanged some=
how, but we could just call them the local and remote ICE configurations.</=
div>
<div class=3D"gmail_extra"><br>
<br>
<div class=3D"gmail_quote">On Thu, Mar 6, 2014 at 1:25 PM, Harald Alvestran=
d <span dir=3D"ltr">
&lt;<a href=3D"mailto:harald@alvestrand.no" target=3D"_blank">harald@alvest=
rand.no</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div bgcolor=3D"#FFFFFF" text=3D"#000000">
<div>
<div class=3D"h5">
<div>On 03/05/2014 06:39 PM, Ari Ker=E4nen wrote:<br>
</div>
<blockquote type=3D"cite">
<pre>Hi all,

We didn't have time for this open issue on Monday meeting so we'll take it =
here on the list.

While ICE is no longer bound to SIP and SDP offer/answer, the document uses=
 terms &quot;offer&quot; and &quot;answer&quot; heavily, starting in the ti=
tle (&quot;ICE: A Protocol for NAT Traversal for Offer/Answer Protocols&quo=
t;) and abstract (&quot;ICE can be used by any protocol utilizing the offer=
/answer model [...]&quot;).

I think we need to update the title and abstract so that it's more clear th=
at protocols that don't follow the o/a model are not excluded. Text suggest=
ions are welcome. Maybe in title we call this just &quot;ICE: A Protocol fo=
r NAT Traversal&quot;.

Then, throughout the text we need to refer to the exchange of candidates so=
mehow. Originally this was referred to as the &quot;SDP offer&quot; and &qu=
ot;SDP answer&quot;. Currently we use &quot;ICE offer&quot; and &quot;ICE a=
nswer&quot;. My suggestion would be to keep the &quot;(ICE) offer/answer&qu=
ot; terminology here but clarify in the beginning of the document that with=
 the offer and answer we refer to the ICE candidate exchange.

Opinions?</pre>
</blockquote>
<br>
</div>
</div>
Given that we do not have any requirement that exchange of candidates happe=
n in a particular sequence, I suggest that we call this &quot;exchange of c=
andidates&quot;, not &quot;offer/answer&quot;.<br>
<br>
Examples of models where offer/answer would be a misnomer:<br>
<br>
- All participants write their candidates into a common server-side store; =
participants wishing to communicate fetch the candidate sets for the entiti=
es they wish to communicate with, as long as the candidate set is fresh eno=
ugh.<br>
<br>
- Trickle ICE
<div class=3D""><br>
<br>
<br>
<blockquote type=3D"cite">
<pre>
Cheers,
Ari</pre>
<br>
<fieldset></fieldset> <br>
<pre>_______________________________________________
mmusic mailing list
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/mmusic</a>
</pre>
</blockquote>
<br>
<br>
</div>
<span class=3D"HOEnZb"><font color=3D"#888888">
<pre cols=3D"72">--=20
Surveillance is pervasive. Go Dark.
</pre>
</font></span></div>
<br>
_______________________________________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/mmusic</a><br>
<br>
</blockquote>
</div>
<br>
</div>
_______________________________________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
https://www.ietf.org/mailman/listinfo/mmusic<br>
</blockquote>
</div>
<br>
</body>
</html>

--_000_7A2DF86FA9684C02819B5CBE29CCA0F3vidyocom_--


From nobody Thu Mar  6 06:10:43 2014
Return-Path: <Christian.Groves@nteczone.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 2789E1A017E for <mmusic@ietfa.amsl.com>; Thu,  6 Mar 2014 06:10:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 fmwGkSuhGELr for <mmusic@ietfa.amsl.com>; Thu,  6 Mar 2014 06:10:38 -0800 (PST)
Received: from cserver5.myshophosting.com (cserver5.myshophosting.com [175.107.161.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CEA01A0297 for <mmusic@ietf.org>; Thu,  6 Mar 2014 06:10:37 -0800 (PST)
Received: from [130.129.156.216] (port=60087 helo=[127.0.0.1]) by cserver5.myshophosting.com with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from <Christian.Groves@nteczone.com>) id 1WLZ0I-0008Fu-P4; Fri, 07 Mar 2014 01:10:31 +1100
Message-ID: <531881CF.2010105@nteczone.com>
Date: Fri, 07 Mar 2014 01:10:23 +1100
From: Christian Groves <Christian.Groves@nteczone.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Salvatore Loreto <salvatore.loreto@ericsson.com>
References: <53185B8E.2070808@nteczone.com> <C8EB64C0-3140-477C-9373-BD36B4B1A64B@ericsson.com> <53187415.2000108@nteczone.com> <C1D662DF-E3E3-45CD-991F-8090CD7130E0@ericsson.com>
In-Reply-To: <C1D662DF-E3E3-45CD-991F-8090CD7130E0@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - cserver5.myshophosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - nteczone.com
X-Get-Message-Sender-Via: cserver5.myshophosting.com: authenticated_id: christian.groves@nteczone.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/MLWifufz6tw5gU8Pks9qzFYGIAU
Cc: mmusic mailing list <mmusic@ietf.org>
Subject: Re: [MMUSIC] SCTP AppID
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: Thu, 06 Mar 2014 14:10:40 -0000

Hello Salvatore,

I don't know that's why I'm asking. I can't see anything special about 
the ALPN registry versus any other registry if we're using it as an example.

Do you have an answer for the second part of the previous email?
i.e One thing I'm still missing is how you specify multiple app/alpns 
(whatever we're calling them) being used in a single SCTP association, 
without using datachannel?

Regards, Christian

On 7/03/2014 12:36 AM, Salvatore Loreto wrote:
> Hi Christian
>
> to be clear I don't think to register an ALPN for data channel is the right solution
>
> I understood Martin was only proposing to look at how ALPN defines and handles the registry
> and do something similar not using it. Am I wrong?
> IMO ALPN parameter defines the protocol that will run on top of TLS (not sure it can be used for DTLS to)
> We are running SCTP over DTLS, so we could use it at least to say SCTP
>
> the app parameter is trying to define how SCTP streams are handled here
> i.e. "data channel" is a pair of one incoming stream and one outgoing SCTP
> stream having the same stream SCTP identifier.
>
> the protocol or better subprotocol will run then on top of the data channel
>
> /Sal
>
>
> On Mar 6, 2014, at 1:11 PM, Christian Groves <Christian.Groves@nteczone.com>
>   wrote:
>
>> Hello Salvatore,
>>
>> OK, I guess one of the RTCweb drafts would then include the request to IANA to register an ALPN for the data channel.
>>
>> One thing I'm still missing is how you specify multiple apps/alpns (whatever we're calling them) being used in a single SCTP association, without using datachannel?
>>
>>
>> Christian
>>
>> On 6/03/2014 10:28 PM, Salvatore Loreto wrote:
>>> yet it is
>>>
>>> /Sal
>>>
>>> On Mar 6, 2014, at 11:27 AM, Christian Groves <Christian.Groves@nteczone.com>
>>>   wrote:
>>>
>>>> Hello Martin,
>>>>
>>>> When you mentioned ALPN is this the draft you were talking about? http://tools.ietf.org/html/draft-ietf-tls-applayerprotoneg-05
>>>>
>>>> Regards,
>>>> Christian
>>>>
>>>> _______________________________________________
>>>> mmusic mailing list
>>>> mmusic@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/mmusic
>


From nobody Thu Mar  6 06:14:40 2014
Return-Path: <martin.thomson@gmail.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 445A01A036B for <mmusic@ietfa.amsl.com>; Thu,  6 Mar 2014 06:14:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 0ZusUxJAGVxA for <mmusic@ietfa.amsl.com>; Thu,  6 Mar 2014 06:14:36 -0800 (PST)
Received: from mail-we0-x234.google.com (mail-we0-x234.google.com [IPv6:2a00:1450:400c:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id 532931A0380 for <mmusic@ietf.org>; Thu,  6 Mar 2014 06:14:22 -0800 (PST)
Received: by mail-we0-f180.google.com with SMTP id p61so3137355wes.25 for <mmusic@ietf.org>; Thu, 06 Mar 2014 06:14:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=yCyfAuqbZXPpCWjD2Spo+t+yhanznKb5TqcUENXZCHM=; b=qaNiOdpTtKC02DShCeH+qWZknpxiV9DQGApYkjfNNKez8uDJmMyBLmL45OoCjBta8r K5Zh0TGOmQwZi3XsRaYh8+EeU2dJobeRulfKTUMOlnlShIN12ruOV/JsjtIrzwFCKhLQ YJM6jla+MU5XIhwrN1eYwAwGkua4WttZRzM6Q4KdrIR8lX1nTBMTWE7SincO8InmLaoT Z32PE6Z8shqLc9MQmFI8OZ58/F0nGB4zaegfbHkznSut6OGE1PS//VarCwcsC0s8k4nK I4QYPBi5/gdJ4eddA/ztDPawJWpm2+I/1YYr9jlPO6zg93kxqr8UZHow37Lb03v7/91z drlg==
MIME-Version: 1.0
X-Received: by 10.194.170.167 with SMTP id an7mr10435084wjc.39.1394115258028;  Thu, 06 Mar 2014 06:14:18 -0800 (PST)
Received: by 10.227.10.196 with HTTP; Thu, 6 Mar 2014 06:14:17 -0800 (PST)
In-Reply-To: <C1D662DF-E3E3-45CD-991F-8090CD7130E0@ericsson.com>
References: <53185B8E.2070808@nteczone.com> <C8EB64C0-3140-477C-9373-BD36B4B1A64B@ericsson.com> <53187415.2000108@nteczone.com> <C1D662DF-E3E3-45CD-991F-8090CD7130E0@ericsson.com>
Date: Thu, 6 Mar 2014 14:14:17 +0000
Message-ID: <CABkgnnWOVf-72jeLbo74dbpxwhiYwgOjsfte2Cx3Voi_YRxdTg@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Salvatore Loreto <salvatore.loreto@ericsson.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/5PJwdrvmvpjL0jskxZo37PpwH6M
Cc: mmusic mailing list <mmusic@ietf.org>
Subject: Re: [MMUSIC] SCTP AppID
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: Thu, 06 Mar 2014 14:14:38 -0000

On 6 March 2014 13:36, Salvatore Loreto <salvatore.loreto@ericsson.com> wrote:
> I understood Martin was only proposing to look at how ALPN defines and handles the registry
> and do something similar not using it. Am I wrong?

Yes, you are wrong.

My intent was to say that you should be using the registry in an
unadulterated form.

ALPN is being used now in a number of places to identify protocols.
We've more or less unilaterally decided in httpbis that this means the
entire protocol stack.  I'm thinking that the protocol we're
identifying here is the following stack of protocols:

Data channel protocol (the combination of the data chennel
establishment protocol and the use of the text and binary PPIDs).
SCTP
DTLS
UDP
IP

Yes, there are cases where there are other users, or protocols perched
on top of this tower.  Those could also be identified with an ALPN
identifier too, if they wanted to.

One such higher-level protocol is the combination of this glorious
protocol tower with SRTP.  That's another ALPN identifier.


From nobody Thu Mar  6 06:28:30 2014
Return-Path: <salvatore.loreto@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 BA1281A03E0 for <mmusic@ietfa.amsl.com>; Thu,  6 Mar 2014 06:28:26 -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 ln7bacepy3Fd for <mmusic@ietfa.amsl.com>; Thu,  6 Mar 2014 06:28:26 -0800 (PST)
Received: from sessmg20.mgmt.ericsson.se (sessmg20.ericsson.net [193.180.251.50]) by ietfa.amsl.com (Postfix) with ESMTP id 970121A03DE for <mmusic@ietf.org>; Thu,  6 Mar 2014 06:28:25 -0800 (PST)
X-AuditID: c1b4fb32-b7f4c8e0000012f5-21-531886048aa5
Received: from ESESSHC021.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg20.mgmt.ericsson.se (Symantec Mail Security) with SMTP id FF.84.04853.40688135; Thu,  6 Mar 2014 15:28:21 +0100 (CET)
Received: from ESESSMB109.ericsson.se ([169.254.9.128]) by ESESSHC021.ericsson.se ([153.88.183.81]) with mapi id 14.02.0387.000; Thu, 6 Mar 2014 15:28:20 +0100
From: Salvatore Loreto <salvatore.loreto@ericsson.com>
To: Martin Thomson <martin.thomson@gmail.com>
Thread-Topic: [MMUSIC] SCTP AppID
Thread-Index: AQHPOS8NfxpP/0XfyUaZJY1aq+ki1prT2zMAgAAc74CAAAbSAIAACqKAgAAD7oA=
Date: Thu, 6 Mar 2014 14:28:20 +0000
Message-ID: <6418C6ED-F200-4EB8-ABCA-9EE20EEEDDF6@ericsson.com>
References: <53185B8E.2070808@nteczone.com> <C8EB64C0-3140-477C-9373-BD36B4B1A64B@ericsson.com> <53187415.2000108@nteczone.com> <C1D662DF-E3E3-45CD-991F-8090CD7130E0@ericsson.com> <CABkgnnWOVf-72jeLbo74dbpxwhiYwgOjsfte2Cx3Voi_YRxdTg@mail.gmail.com>
In-Reply-To: <CABkgnnWOVf-72jeLbo74dbpxwhiYwgOjsfte2Cx3Voi_YRxdTg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.148]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <FA0AC338BE1BCA488A0AAD789FD1E8FD@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpgkeLIzCtJLcpLzFFi42KZGfG3Rpe1TSLY4PFfTosv7xtZLK6d+cdo MXX5YxYHZo+ds+6yeyxZ8pPJY8X5mSwBzFFcNimpOZllqUX6dglcGesvHmIsuMRfceBBF0sD 4wyeLkZODgkBE4mH+zexQ9hiEhfurWfrYuTiEBI4wSixfsFDVpCEkMBiRokrf2pBbDYBM4nn D7cwg9giAroSi84+AGtmFoiVOP18MSOILSygIDFh6W82iBpFifOX5rNA2H4S19/PBKthEVCR uL63EWgOBwevgL3Ev7nCEHsbmCTWrJ8HVs8pECjR2PsFrJ4R6Ljvp9YwQewSl7j1ZD4TxNEC Ekv2nGeGsEUlXj7+xwphK0k0LnnCClFvIPH+3HxmCNta4u2lU1BztCWWLXwNFucVEJQ4OfMJ ywRG8VlIVsxC0j4LSfssJO2zkLQvYGRdxShZnFpcnJtuZKCXm55bopdalJlcXJyfp1ecuokR GIsHt/w22sF4co/9IUZpDhYlcd7rrDVBQgLpiSWp2ampBalF8UWlOanFhxiZODilGhi3zjh8 2qp8VeeM1xVa1Rwx67oaDT53cV96WMk2JUaqtlpYZJIa303TGzdEd3CxtL1d09Ix62rHroDN 71u3dC32O7c/WGU96y79ommp82XX52Sdz20t+szyM/Pr6kabCd5TeXOM1t1xW7nlZVY1S6bz 0mNOT1yvpV679kHLPav9t+bOCM+kCXFKLMUZiYZazEXFiQAVwI9kkwIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/aMVmTg_1qLGq_9CNNPjGou-hyIA
Cc: mmusic mailing list <mmusic@ietf.org>
Subject: Re: [MMUSIC] SCTP AppID
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: Thu, 06 Mar 2014 14:28:26 -0000

On Mar 6, 2014, at 2:14 PM, Martin Thomson <martin.thomson@gmail.com>
 wrote:

> On 6 March 2014 13:36, Salvatore Loreto <salvatore.loreto@ericsson.com> w=
rote:
>> I understood Martin was only proposing to look at how ALPN defines and h=
andles the registry
>> and do something similar not using it. Am I wrong?
>=20
> Yes, you are wrong.
I was sure to be wrong
using it would make my life easier and I would love to use it
 but I have still some concerns about it that maybe you can help me to solv=
e

>=20
> My intent was to say that you should be using the registry in an
> unadulterated form.
>=20
> ALPN is being used now in a number of places to identify protocols.
can you point me to those?

> We've more or less unilaterally decided in httpbis that this means the
> entire protocol stack.
I know of the decision in httpbis
but as it is not written down clearly anywhere I was and I am not sure abou=
t=20
leveraging on that decision.


>  I'm thinking that the protocol we're
> identifying here is the following stack of protocols:
>=20
> Data channel protocol (the combination of the data chennel
> establishment protocol and the use of the text and binary PPIDs).
> SCTP
> DTLS
> UDP
> IP

another concern is about=85
are we allowed to register also value that has DTLS and not TLS in the towe=
r?

on more point is that WebRTC is a mess!!!
you can end up of a situation where you already have a DTLS association est=
ablished=20
because you need the key to crypto to be used in SRTP
and then at some point the user decide to  "reuse" the same DTLS associatio=
n to run=20
an SCTP association on top of it


>=20
> Yes, there are cases where there are other users, or protocols perched
> on top of this tower.  Those could also be identified with an ALPN
> identifier too, if they wanted to.
>=20
> One such higher-level protocol is the combination of this glorious
> protocol tower with SRTP.  That's another ALPN identifier.


From nobody Thu Mar  6 08:39:01 2014
Return-Path: <martin.thomson@gmail.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 4C3AD1A01F7 for <mmusic@ietfa.amsl.com>; Thu,  6 Mar 2014 02:01:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 LIjQmjojrjPd for <mmusic@ietfa.amsl.com>; Thu,  6 Mar 2014 02:01:47 -0800 (PST)
Received: from mail-we0-x22f.google.com (mail-we0-x22f.google.com [IPv6:2a00:1450:400c:c03::22f]) by ietfa.amsl.com (Postfix) with ESMTP id C26651A01EF for <mmusic@ietf.org>; Thu,  6 Mar 2014 02:01:46 -0800 (PST)
Received: by mail-we0-f175.google.com with SMTP id q58so2749026wes.34 for <mmusic@ietf.org>; Thu, 06 Mar 2014 02:01:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:date:message-id:subject:from:to:content-type; bh=gBb0wcILWIyZf0juZZ6ux1W14BQJbX5zajJFO/E1lgk=; b=esA8lYdx9Aw/ibaleNLX/y/fi72ISoIoTpXGan8qzihI/1JwZDJAsqMBULFjNful/F JZcyFm4mPB9DXOyNfUfOJp/eoarNlZDMc1nXUxCSZX2DaNgPvX7anpW13/AEBis2omdZ wstQCtX1QOI3pAHoLahbJLN6dZdDgQ89U2+76yl6pbOjP3LZxSNDt9cQQJONB42GPxh1 8hhgvtbsQaBxdpxotHij2vaiGBHBat8ddSPF3e4jiRAy7p5DV/tEmOP2kg8jrVdAVG+2 RFQTx1ddrZPRSyH7uFtMGqCNtg33/AalfSbM17QF30KYtMCj7Cp+vTrL7jQGg041GJDW PwCQ==
MIME-Version: 1.0
X-Received: by 10.194.188.41 with SMTP id fx9mr8516313wjc.56.1394100102546; Thu, 06 Mar 2014 02:01:42 -0800 (PST)
Received: by 10.227.10.196 with HTTP; Thu, 6 Mar 2014 02:01:42 -0800 (PST)
Date: Thu, 6 Mar 2014 10:01:42 +0000
Message-ID: <CABkgnnWUSQsZdUhivYuCxoTPkciWcePvYi03YaYG+cbVoSXtbQ@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: tram@ietf.org
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/8lKrawfDn4Buz-mBeu-xEeDOgv8
X-Mailman-Approved-At: Thu, 06 Mar 2014 08:39:00 -0800
Subject: [MMUSIC] Demux of STUN in RFC 5764
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: Thu, 06 Mar 2014 10:01:51 -0000

FYI, I've submitted an erratum on RFC 5764 regarding STUN demux.
Triggered by the discussion in MMUSIC (on bcc).

http://www.rfc-editor.org/errata_search.php?rfc=5764&eid=3913

This shouldn't really affect anything in BUNDLE, unless you are
intending to refer to specific values on the first byte.

For any STUN work, pointing this out would probably be a good idea.


From nobody Thu Mar  6 11:16:03 2014
Return-Path: <emcho@sip-communicator.org>
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 5C0F51A00B4 for <mmusic@ietfa.amsl.com>; Thu,  6 Mar 2014 11:16:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.979
X-Spam-Level: 
X-Spam-Status: No, score=-1.979 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 8ywhpBgcvD1T for <mmusic@ietfa.amsl.com>; Thu,  6 Mar 2014 11:15:57 -0800 (PST)
Received: from mail-ve0-f172.google.com (mail-ve0-f172.google.com [209.85.128.172]) by ietfa.amsl.com (Postfix) with ESMTP id A6C101A0102 for <mmusic@ietf.org>; Thu,  6 Mar 2014 11:15:57 -0800 (PST)
Received: by mail-ve0-f172.google.com with SMTP id jx11so3151589veb.3 for <mmusic@ietf.org>; Thu, 06 Mar 2014 11:15:53 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=azc0mhxxeVQCA5ht+e4d1PhlQT+eH25pN9rNskWDvlw=; b=bIFddpTJ0ybzMxflKYwPlMwtkuAhTo51Wzox8L5BpcpRRriMpnClzsjlTAGkCXJRuW 1P9AtdogWNvQsP0laMkWiMIRBK3xWYdFa0yWEKY8dUKs/HCVwMHYPdndbKzi0pwOTWGT sc3HlM9THuHBiAbTruI+S1xEEqNFOWDkPk2WZTEaaeQKZxz+qddTC0v7l//S8d9WKpni bUI9B3IQgB+xSKhBEGbruUWfENYPlDh7pzyLa7xtqJuLS/WPgW+NhKwfd6XBHtLiBEdi ozuN2CwLeTfrL7hv2l7L4SbFD9tBavaRdx1d9dMGJGhuKBMA1YZ550m9rrlV74ge4dw0 OHOA==
X-Gm-Message-State: ALoCoQnN/cRpI3F0K69SBc7LCfWk2HY+RZXWYeLWpte7h+6GwAddHtlkVVhQxtiVzs3dLKVwQA4Q
X-Received: by 10.220.11.141 with SMTP id t13mr2022179vct.30.1394133353449; Thu, 06 Mar 2014 11:15:53 -0800 (PST)
Received: from mail-vc0-f174.google.com (mail-vc0-f174.google.com [209.85.220.174]) by mx.google.com with ESMTPSA id tu9sm17581019vdc.10.2014.03.06.11.15.52 for <mmusic@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 06 Mar 2014 11:15:52 -0800 (PST)
Received: by mail-vc0-f174.google.com with SMTP id im17so3040623vcb.19 for <mmusic@ietf.org>; Thu, 06 Mar 2014 11:15:52 -0800 (PST)
X-Received: by 10.58.170.69 with SMTP id ak5mr2322058vec.28.1394133352858; Thu, 06 Mar 2014 11:15:52 -0800 (PST)
MIME-Version: 1.0
Received: by 10.220.191.130 with HTTP; Thu, 6 Mar 2014 11:15:32 -0800 (PST)
In-Reply-To: <7A2DF86F-A968-4C02-819B-5CBE29CCA0F3@vidyo.com>
References: <9E803A35-8AF5-4F91-8280-0DD2263B71D5@ericsson.com> <5318774D.5090705@alvestrand.no> <CAOJ7v-3gFQ=xvz9=ZzZ23m+CvbKgK2OPpxPv9h56qFwNoXg9GQ@mail.gmail.com> <7A2DF86F-A968-4C02-819B-5CBE29CCA0F3@vidyo.com>
From: Emil Ivov <emcho@jitsi.org>
Date: Thu, 6 Mar 2014 19:15:32 +0000
Message-ID: <CAPvvaaJ6i=pY=qVMm_Nk2XTnViFX0AgdD3bgUBNeMUtLYsbtdA@mail.gmail.com>
To: Jonathan Lennox <jonathan@vidyo.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/gVrkGP2whsHvTO6BWrK7g-UbAkk
Cc: mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] ICE and offer/answer terminology
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: Thu, 06 Mar 2014 19:16:00 -0000

There's also need to negotiate support for options (such as trickle).

I think I like ICE Offer and ICE Answer because they are intuitive and
yet mark a difference with O/A.

We'd just need to come up with a little bit of text as to how their
semantics work and how they map to actual Offer/Answer.

I'd be happy to do that in the following days if that would help.

Emil

On Thu, Mar 6, 2014 at 2:02 PM, Jonathan Lennox <jonathan@vidyo.com> wrote:
> There also needs to be the decision about who's the controlling endpoint =
by
> default.
>
> On Mar 6, 2014, at 1:47 PM, Justin Uberti <juberti@google.com> wrote:
>
> The ICE ufrag/pwd and options do need to be exchanged somehow, but we cou=
ld
> just call them the local and remote ICE configurations.
>
>
> On Thu, Mar 6, 2014 at 1:25 PM, Harald Alvestrand <harald@alvestrand.no>
> wrote:
>>
>> On 03/05/2014 06:39 PM, Ari Ker=E4nen wrote:
>>
>> Hi all,
>>
>> We didn't have time for this open issue on Monday meeting so we'll take =
it
>> here on the list.
>>
>> While ICE is no longer bound to SIP and SDP offer/answer, the document
>> uses terms "offer" and "answer" heavily, starting in the title ("ICE: A
>> Protocol for NAT Traversal for Offer/Answer Protocols") and abstract ("I=
CE
>> can be used by any protocol utilizing the offer/answer model [...]").
>>
>> I think we need to update the title and abstract so that it's more clear
>> that protocols that don't follow the o/a model are not excluded. Text
>> suggestions are welcome. Maybe in title we call this just "ICE: A Protoc=
ol
>> for NAT Traversal".
>>
>> Then, throughout the text we need to refer to the exchange of candidates
>> somehow. Originally this was referred to as the "SDP offer" and "SDP
>> answer". Currently we use "ICE offer" and "ICE answer". My suggestion wo=
uld
>> be to keep the "(ICE) offer/answer" terminology here but clarify in the
>> beginning of the document that with the offer and answer we refer to the=
 ICE
>> candidate exchange.
>>
>> Opinions?
>>
>>
>> Given that we do not have any requirement that exchange of candidates
>> happen in a particular sequence, I suggest that we call this "exchange o=
f
>> candidates", not "offer/answer".
>>
>> Examples of models where offer/answer would be a misnomer:
>>
>> - All participants write their candidates into a common server-side stor=
e;
>> participants wishing to communicate fetch the candidate sets for the
>> entities they wish to communicate with, as long as the candidate set is
>> fresh enough.
>>
>> - Trickle ICE
>>
>> Cheers,
>> Ari

--
https://jitsi.org


From nobody Thu Mar  6 11:27:17 2014
Return-Path: <ari.keranen@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 A9ABC1A0068 for <mmusic@ietfa.amsl.com>; Thu,  6 Mar 2014 11:27:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.551
X-Spam-Level: 
X-Spam-Status: No, score=-3.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 pM9dzjcNrPRN for <mmusic@ietfa.amsl.com>; Thu,  6 Mar 2014 11:27:13 -0800 (PST)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id BE5411A0040 for <mmusic@ietf.org>; Thu,  6 Mar 2014 11:27:12 -0800 (PST)
X-AuditID: c1b4fb2d-b7f5d8e000002a7b-2f-5318cc0b6a69
Received: from ESESSHC019.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 98.65.10875.B0CC8135; Thu,  6 Mar 2014 20:27:08 +0100 (CET)
Received: from mail.lmf.ericsson.se (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.77) with Microsoft SMTP Server id 14.2.347.0; Thu, 6 Mar 2014 20:27:07 +0100
Received: from nomadiclab.lmf.ericsson.se (nomadiclab.lmf.ericsson.se [131.160.33.3])	by mail.lmf.ericsson.se (Postfix) with ESMTP id 8A30F1101FA; Thu,  6 Mar 2014 21:27:07 +0200 (EET)
Received: from nomadiclab.lmf.ericsson.se (localhost [127.0.0.1])	by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id 4E41456BCA;	Thu,  6 Mar 2014 21:27:02 +0200 (EET)
Received: from dhcp-hotel-wifi-153-7c.meeting.ietf.org (localhost [127.0.0.1]) by nomadiclab.lmf.ericsson.se (Postfix) with ESMTP id A75125316B; Thu,  6 Mar 2014 21:27:01 +0200 (EET)
Message-ID: <5318CC08.8030706@ericsson.com>
Date: Thu, 6 Mar 2014 19:27:04 +0000
From: =?ISO-8859-1?Q?Ari_Ker=E4nen?= <ari.keranen@ericsson.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Emil Ivov <emcho@jitsi.org>, Jonathan Lennox <jonathan@vidyo.com>
References: <9E803A35-8AF5-4F91-8280-0DD2263B71D5@ericsson.com> <5318774D.5090705@alvestrand.no> <CAOJ7v-3gFQ=xvz9=ZzZ23m+CvbKgK2OPpxPv9h56qFwNoXg9GQ@mail.gmail.com> <7A2DF86F-A968-4C02-819B-5CBE29CCA0F3@vidyo.com> <CAPvvaaJ6i=pY=qVMm_Nk2XTnViFX0AgdD3bgUBNeMUtLYsbtdA@mail.gmail.com>
In-Reply-To: <CAPvvaaJ6i=pY=qVMm_Nk2XTnViFX0AgdD3bgUBNeMUtLYsbtdA@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrDLMWRmVeSWpSXmKPExsUyM+JvjS7PGYlgg44HAhZrdk5gsTjW18Vm sX/xeWaLqcsfsziweFyZcIXVY8mSn0we/98EerQ9u8MewBLFZZOSmpNZllqkb5fAlbH97A3G gjbJig+LDjA3MDaLdDFyckgImEi0HP3ADGGLSVy4t56ti5GLQ0jgEKPE/Odb2SGc9YwSRw7s YYRw9jBKvDz/E6psLaPErHt/WCCcXYwSDa9/MYEM4xXQlpj3rRvMZhFQkeg9fJMRxGYTsJe4 OeE6O4gtKpAscfP7ZzaIekGJkzOfsIDYIgKuEs9vPQKrYRbwkdjZ1wJWIyxgJvHw8GImiGWz mSRePJzACpLgFAiUeHdsA1SDrcSFOddZIGx5ieats6G+U5O4em4TmC0koCpx9d8rxgmMorOQ 7J6FpH0WkvYFjMyrGNlzEzNz0ssNNzECY+Tglt+6OxhPnRM5xCjNwaIkzvvhrXOQkEB6Yklq dmpqQWpRfFFpTmrxIUYmDk6pBsaIaA/91MVnE6OSNC/8v3n3vfmuyQbM0iZfrL5V7RRcyyy0 iUHk7ueSkGW3hE9tYJ3rk7nwtPXb5nqeDYtu6s3Vd6h98PBhma+noNZTqwdHxKwd7fZ17F2o 7WTKxvzXblN3xNUattmuuwV+bZmamjnj1Dr5N6vfX+rrtKs4Gpl3yD9Z5fObQFElluKMREMt 5qLiRACkcdSSXwIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/K2KZAwZlaOZPe3XK2kpaw28-oU0
Cc: mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] ICE and offer/answer terminology
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: Thu, 06 Mar 2014 19:27:15 -0000

On 3/6/14 7:15 PM, Emil Ivov wrote:
> There's also need to negotiate support for options (such as trickle).
>
> I think I like ICE Offer and ICE Answer because they are intuitive and
> yet mark a difference with O/A.
>
> We'd just need to come up with a little bit of text as to how their
> semantics work and how they map to actual Offer/Answer.
>
> I'd be happy to do that in the following days if that would help.

That would be great! Thanks.

> On Thu, Mar 6, 2014 at 2:02 PM, Jonathan Lennox <jonathan@vidyo.com> wrote:
>> There also needs to be the decision about who's the controlling endpoint by
>> default.

Or can we let the ice-breaker just handle this in cases where there's 
ambiguity?

Also Harald's server-side storage scenario was interesting, but I guess 
the tie-breaker is sufficient also for that. I would still be inclined 
to call that "ICE offer" and "ICE answer" though.


Cheers,
Ari

>> On Mar 6, 2014, at 1:47 PM, Justin Uberti <juberti@google.com> wrote:
>>
>> The ICE ufrag/pwd and options do need to be exchanged somehow, but we could
>> just call them the local and remote ICE configurations.
>>
>>
>> On Thu, Mar 6, 2014 at 1:25 PM, Harald Alvestrand <harald@alvestrand.no>
>> wrote:
>>>
>>> On 03/05/2014 06:39 PM, Ari Keränen wrote:
>>>
>>> Hi all,
>>>
>>> We didn't have time for this open issue on Monday meeting so we'll take it
>>> here on the list.
>>>
>>> While ICE is no longer bound to SIP and SDP offer/answer, the document
>>> uses terms "offer" and "answer" heavily, starting in the title ("ICE: A
>>> Protocol for NAT Traversal for Offer/Answer Protocols") and abstract ("ICE
>>> can be used by any protocol utilizing the offer/answer model [...]").
>>>
>>> I think we need to update the title and abstract so that it's more clear
>>> that protocols that don't follow the o/a model are not excluded. Text
>>> suggestions are welcome. Maybe in title we call this just "ICE: A Protocol
>>> for NAT Traversal".
>>>
>>> Then, throughout the text we need to refer to the exchange of candidates
>>> somehow. Originally this was referred to as the "SDP offer" and "SDP
>>> answer". Currently we use "ICE offer" and "ICE answer". My suggestion would
>>> be to keep the "(ICE) offer/answer" terminology here but clarify in the
>>> beginning of the document that with the offer and answer we refer to the ICE
>>> candidate exchange.
>>>
>>> Opinions?
>>>
>>>
>>> Given that we do not have any requirement that exchange of candidates
>>> happen in a particular sequence, I suggest that we call this "exchange of
>>> candidates", not "offer/answer".
>>>
>>> Examples of models where offer/answer would be a misnomer:
>>>
>>> - All participants write their candidates into a common server-side store;
>>> participants wishing to communicate fetch the candidate sets for the
>>> entities they wish to communicate with, as long as the candidate set is
>>> fresh enough.
>>>
>>> - Trickle ICE
>>>
>>> Cheers,
>>> Ari
>
> --
> https://jitsi.org
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>


From nobody Fri Mar  7 00:43:09 2014
Return-Path: <martin.thomson@gmail.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 517F91A0107 for <mmusic@ietfa.amsl.com>; Fri,  7 Mar 2014 00:43:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 ARxSr5wNav-1 for <mmusic@ietfa.amsl.com>; Fri,  7 Mar 2014 00:43:06 -0800 (PST)
Received: from mail-we0-x230.google.com (mail-we0-x230.google.com [IPv6:2a00:1450:400c:c03::230]) by ietfa.amsl.com (Postfix) with ESMTP id 7A1771A0103 for <mmusic@ietf.org>; Fri,  7 Mar 2014 00:43:06 -0800 (PST)
Received: by mail-we0-f176.google.com with SMTP id x48so4422361wes.7 for <mmusic@ietf.org>; Fri, 07 Mar 2014 00:43:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=UcL1W1+0PGM6XbiMwYF9PlsN6B6x6daJ76lmLEDY+Vk=; b=fZI9vaxw9hW1mvIb0dhyEGF5fB6Yb848lnQ7Sr80aCdJheQNYMWVfPuDrq2elBG6Ob 5606Kz7/f2Kl+VCINzReHvKHljmFcD3BxHFW2SXim86SSkX/vrpuXT0m2uxSG7s8eTJl DLpwC2arNCdu25i4pUcbLE1XvpHp9xSMIUzQdDjwujDrgpWBtxtxEbe4mQbQ1PGFXs6q zQJOoMI7Ywqid8G1xwo5WLTvVNGOb/y8UHQIyQbWrLAYON+tvOjdkgQ/EQCL78uT5IZv /KSCCbUcYaeort2FVZf/gtC4KGbb4x9oiw4rBcvWZ13tzBpvxh7XX8fiEfqMJVJbF5ky GX4Q==
MIME-Version: 1.0
X-Received: by 10.194.206.102 with SMTP id ln6mr16892469wjc.43.1394181781879;  Fri, 07 Mar 2014 00:43:01 -0800 (PST)
Received: by 10.227.10.196 with HTTP; Fri, 7 Mar 2014 00:43:01 -0800 (PST)
In-Reply-To: <6418C6ED-F200-4EB8-ABCA-9EE20EEEDDF6@ericsson.com>
References: <53185B8E.2070808@nteczone.com> <C8EB64C0-3140-477C-9373-BD36B4B1A64B@ericsson.com> <53187415.2000108@nteczone.com> <C1D662DF-E3E3-45CD-991F-8090CD7130E0@ericsson.com> <CABkgnnWOVf-72jeLbo74dbpxwhiYwgOjsfte2Cx3Voi_YRxdTg@mail.gmail.com> <6418C6ED-F200-4EB8-ABCA-9EE20EEEDDF6@ericsson.com>
Date: Fri, 7 Mar 2014 08:43:01 +0000
Message-ID: <CABkgnnUL_nHjzVveo4Az-5zQ2i7dwBKGoUOYukBaM2EtdVNcKg@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Salvatore Loreto <salvatore.loreto@ericsson.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/mKWoXauyK_Sei08AxXR4pD_VjbM
Cc: mmusic mailing list <mmusic@ietf.org>
Subject: Re: [MMUSIC] SCTP AppID
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: Fri, 07 Mar 2014 08:43:08 -0000

I think that the only uses so far are in proposals.

On 6 March 2014 14:28, Salvatore Loreto <salvatore.loreto@ericsson.com> wrote:
> are we allowed to register also value that has DTLS and not TLS in the tower?

Yes, it's a different tower, but that's OK.

> on more point is that WebRTC is a mess!!!
> you can end up of a situation where you already have a DTLS association established
> because you need the key to crypto to be used in SRTP
> and then at some point the user decide to  "reuse" the same DTLS association to run
> an SCTP association on top of it

Of course.  The solution there would be that you negotiate the
combination of protocols, even if you aren't using all of them
initially.


From nobody Fri Mar  7 02:50:23 2014
Return-Path: <ron.even.tlv@gmail.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 2D6911A01CB for <mmusic@ietfa.amsl.com>; Fri,  7 Mar 2014 02:50:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 X3dY106MmeDo for <mmusic@ietfa.amsl.com>; Fri,  7 Mar 2014 02:50:20 -0800 (PST)
Received: from mail-wg0-x231.google.com (mail-wg0-x231.google.com [IPv6:2a00:1450:400c:c00::231]) by ietfa.amsl.com (Postfix) with ESMTP id 563EC1A01C7 for <mmusic@ietf.org>; Fri,  7 Mar 2014 02:50:20 -0800 (PST)
Received: by mail-wg0-f49.google.com with SMTP id a1so376569wgh.8 for <mmusic@ietf.org>; Fri, 07 Mar 2014 02:50:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:to:subject:date:message-id:mime-version:content-type :thread-index:content-language; bh=brujjO+rf4y4WcjdtH23HV3/monyHHXX++cx8KpKQLo=; b=aiPjtVv4msommQdF9FQqrTOhrPEKq6x7qSTWz5LJXEWpU5xKaYy0Ik79NkVlkfQXwg PFPaKoILeVCOnRNMCge7scTVRcaS3z0nNovBRJveLVTKp1V8lOQFw5FGknUEtSbJJ5FV jYg1ynm23RJ8efOum9ylV+4UXDlKgbUL9hnk8TJCD0A1vGif3AYBEw95ot+M/h2HkLZC gxTry89UThBz1gw3iFLO3YEFqols9muvfD5WMade1wivLflwVmT8bWm+l8GBjBy4+sBT ZSzyQ6xzYwDNkZpDK2CHgqQ2dBqUPy10biQM5ZlkxzhrZmtzDc83gYNhnLx6OPWpQgns Ef/A==
X-Received: by 10.194.61.210 with SMTP id s18mr18152554wjr.10.1394189415698; Fri, 07 Mar 2014 02:50:15 -0800 (PST)
Received: from RoniE ([2001:67c:370:160:bc11:5870:4234:480d]) by mx.google.com with ESMTPSA id f7sm7618865wjb.7.2014.03.07.02.50.14 for <mmusic@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 07 Mar 2014 02:50:15 -0800 (PST)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <mmusic@ietf.org>
Date: Fri, 7 Mar 2014 12:50:12 +0200
Message-ID: <021001cf39f3$04e8de40$0eba9ac0$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0211_01CF3A03.C871FC60"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac8576j/ZLk0sCPhSmugTuLrbZo+3A==
Content-Language: en-us
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/tt9QdkT6muA4j_R1Bkl4rbjSfKA
Subject: [MMUSIC] Bundle: Q13 receiver-Id
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: Fri, 07 Mar 2014 10:50:22 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0211_01CF3A03.C871FC60
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi,

In draft-even-mmusic-application-token-02
<http://tools.ietf.org/html/draft-even-mmusic-application-token-02>  there
is a recv-appId token that can be used as the receiver-Id. Based on the
discussion in the meeting it seems that the recv-appId  usage  will be
needed for the case when the offerer receives media before the SDP answer
and can use the recv-appId to identify the correlation to an m-line / RTP
stream   in the SDP.  This will also works for the same PT number.

 

Roni 


------=_NextPart_000_0211_01CF3A03.C871FC60
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p =
class=3DMsoNormal>Hi,<o:p></o:p></p><p class=3DMsoNormal>In <a =
href=3D"http://tools.ietf.org/html/draft-even-mmusic-application-token-02=
">draft-even-mmusic-application-token-02</a> there is a recv-appId token =
that can be used as the receiver-Id. Based on the discussion in the =
meeting it seems that the recv-appId &nbsp;usage &nbsp;will be needed =
for the case when the offerer receives media before the SDP answer and =
can use the recv-appId to identify the correlation to an m-line / RTP =
stream &nbsp;&nbsp;in the SDP.&nbsp; This will also works for the same =
PT number.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Roni <o:p></o:p></p></div></body></html>
------=_NextPart_000_0211_01CF3A03.C871FC60--


From nobody Fri Mar  7 03:10:43 2014
Return-Path: <harald@alvestrand.no>
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 CDDE01A01EF for <mmusic@ietfa.amsl.com>; Fri,  7 Mar 2014 03:10:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level: 
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547] autolearn=ham
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 4eo6CzwTcE5n for <mmusic@ietfa.amsl.com>; Fri,  7 Mar 2014 03:10:39 -0800 (PST)
Received: from mork.alvestrand.no (mork.alvestrand.no [158.38.152.117]) by ietfa.amsl.com (Postfix) with ESMTP id 16F761A01C8 for <mmusic@ietf.org>; Fri,  7 Mar 2014 03:10:39 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mork.alvestrand.no (Postfix) with ESMTP id 876C37C3266 for <mmusic@ietf.org>; Fri,  7 Mar 2014 12:10:34 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at alvestrand.no
Received: from mork.alvestrand.no ([127.0.0.1]) by localhost (mork.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wg+HL9SrPowD for <mmusic@ietf.org>; Fri,  7 Mar 2014 12:10:33 +0100 (CET)
Received: from [IPv6:2001:67c:370:176:dc71:4cbb:f962:3326] (unknown [IPv6:2001:67c:370:176:dc71:4cbb:f962:3326]) by mork.alvestrand.no (Postfix) with ESMTPSA id 9F30D7C325E for <mmusic@ietf.org>; Fri,  7 Mar 2014 12:10:33 +0100 (CET)
Message-ID: <5319A928.8040703@alvestrand.no>
Date: Fri, 07 Mar 2014 12:10:32 +0100
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: mmusic@ietf.org
References: <53185B8E.2070808@nteczone.com> <C8EB64C0-3140-477C-9373-BD36B4B1A64B@ericsson.com> <53187415.2000108@nteczone.com> <C1D662DF-E3E3-45CD-991F-8090CD7130E0@ericsson.com> <CABkgnnWOVf-72jeLbo74dbpxwhiYwgOjsfte2Cx3Voi_YRxdTg@mail.gmail.com>
In-Reply-To: <CABkgnnWOVf-72jeLbo74dbpxwhiYwgOjsfte2Cx3Voi_YRxdTg@mail.gmail.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/73n3fgK2bQRz8ebzNgbJe956rmw
Subject: Re: [MMUSIC] SCTP AppID
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: Fri, 07 Mar 2014 11:10:41 -0000

On 03/06/2014 03:14 PM, Martin Thomson wrote:
> On 6 March 2014 13:36, Salvatore Loreto <salvatore.loreto@ericsson.com> wrote:
>> I understood Martin was only proposing to look at how ALPN defines and handles the registry
>> and do something similar not using it. Am I wrong?
> Yes, you are wrong.
>
> My intent was to say that you should be using the registry in an
> unadulterated form.
>
> ALPN is being used now in a number of places to identify protocols.
> We've more or less unilaterally decided in httpbis that this means the
> entire protocol stack.  I'm thinking that the protocol we're
> identifying here is the following stack of protocols:
>
> Data channel protocol (the combination of the data chennel
> establishment protocol and the use of the text and binary PPIDs).
> SCTP
> DTLS
> UDP
> IP

Nit:

One irritating case in our particular use case is that we actually don't
know the lowest layers ahead of time.

Due to ICE candidates working their thing, we can end up with

SCTP/DTLS/UDP/IPv4
SCTP/DTLS/RFC3401-encap/TCP/IPv6 (I think the RFC number is wrong, though)
SCTP/DTLS/TURN-encap/TCP/IPv4
SCTP/DTLS/TURN-encap/UDP/IPv6

and permutations.

You see where I'm going - an identifier needs to identify only the parts
we're sure will be part of the package. In this case, Data channel
protocol / SCTP / DTLS.



>
> Yes, there are cases where there are other users, or protocols perched
> on top of this tower.  Those could also be identified with an ALPN
> identifier too, if they wanted to.
>
> One such higher-level protocol is the combination of this glorious
> protocol tower with SRTP.  That's another ALPN identifier.
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic


-- 
Surveillance is pervasive. Go Dark.


From nobody Fri Mar  7 03:22:16 2014
Return-Path: <martin.thomson@gmail.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 551461A018A for <mmusic@ietfa.amsl.com>; Fri,  7 Mar 2014 03:22:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 SVekdQXNV4Fb for <mmusic@ietfa.amsl.com>; Fri,  7 Mar 2014 03:22:11 -0800 (PST)
Received: from mail-we0-x22d.google.com (mail-we0-x22d.google.com [IPv6:2a00:1450:400c:c03::22d]) by ietfa.amsl.com (Postfix) with ESMTP id CFB701A0218 for <mmusic@ietf.org>; Fri,  7 Mar 2014 03:22:10 -0800 (PST)
Received: by mail-we0-f173.google.com with SMTP id w61so4792202wes.18 for <mmusic@ietf.org>; Fri, 07 Mar 2014 03:22:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Yz1MyusjWfyJPPtIpQWv0MTIVf60H4x8oVOrIP4Yf0w=; b=YJ25eEwsDoBgMWKRCLu9TZPACOgPU2G92m3dFcNrRi6ja70YXAQL599W5dt7tmtC1i 9+A9rnjzzbn8JH3EkIhKRbaT4EkuUUpHR6VQunbGlkxApo1gthtiqFuhnI2SYGCSmtth Xn9+0K6mzTJ+9k6jqDNnxuNls3EQ4SdvBMrGFG7K6THX84SQmeKjokHK2i3OnvrLY+Lo rToyWfmzNhdtvcwqxazOFKQwzp1rAFktbcMJR8Efotv4yGqN+cmcC60Hz5YadvTUJHKx i2AMwv+whXZJlbGp9+7x3Uv97/2fx5sI13uJSZa99IU7Pt6tL2ZoSkSu8q8rLGnPHJYg Xp3g==
MIME-Version: 1.0
X-Received: by 10.194.174.197 with SMTP id bu5mr17755794wjc.71.1394191326174;  Fri, 07 Mar 2014 03:22:06 -0800 (PST)
Received: by 10.227.10.196 with HTTP; Fri, 7 Mar 2014 03:22:06 -0800 (PST)
In-Reply-To: <5319A928.8040703@alvestrand.no>
References: <53185B8E.2070808@nteczone.com> <C8EB64C0-3140-477C-9373-BD36B4B1A64B@ericsson.com> <53187415.2000108@nteczone.com> <C1D662DF-E3E3-45CD-991F-8090CD7130E0@ericsson.com> <CABkgnnWOVf-72jeLbo74dbpxwhiYwgOjsfte2Cx3Voi_YRxdTg@mail.gmail.com> <5319A928.8040703@alvestrand.no>
Date: Fri, 7 Mar 2014 11:22:06 +0000
Message-ID: <CABkgnnVghjLVBPQiYwjgH1uVac1Qm5MwWj09e1uk90shVjss3w@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Harald Alvestrand <harald@alvestrand.no>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/ijTlkA4vTpCz_DJa7VecdW6fVB8
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] SCTP AppID
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: Fri, 07 Mar 2014 11:22:12 -0000

On 7 March 2014 11:10, Harald Alvestrand <harald@alvestrand.no> wrote:
> One irritating case in our particular use case is that we actually don't
> know the lowest layers ahead of time.

The fact that we are using wired Ethernet vs. WiFi is generally not
visible at the level we're doing this identification either.

If it does not matter to the protocol semantics, then I believe it to
be safe to use the same identifier for two similar-but-not-identical
stacks.

Yes, one might argue that TURN-TCP encapsulation is tangibly different
to non-encapsulated SRTP.  We can talk about those distinctions and
whether they require different identifiers, but in this case, I don't
see any need for distinction.


From nobody Fri Mar  7 05:33:56 2014
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 0C2D11A01C9 for <mmusic@ietfa.amsl.com>; Fri,  7 Mar 2014 05:33:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.919
X-Spam-Level: 
X-Spam-Status: No, score=-0.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_FONT_FACE_BAD=0.981, HTML_MESSAGE=0.001, 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 ScPZp3BXkH-T for <mmusic@ietfa.amsl.com>; Fri,  7 Mar 2014 05:33:54 -0800 (PST)
Received: from sesbmg20.ericsson.net (sesbmg20.ericsson.net [193.180.251.56]) by ietfa.amsl.com (Postfix) with ESMTP id 8F4321A019D for <mmusic@ietf.org>; Fri,  7 Mar 2014 05:33:53 -0800 (PST)
X-AuditID: c1b4fb38-b7f418e000001099-67-5319cabcfb54
Received: from ESESSHC004.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg20.ericsson.net (Symantec Mail Security) with SMTP id 28.78.04249.CBAC9135; Fri,  7 Mar 2014 14:33:48 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.216]) by ESESSHC004.ericsson.se ([153.88.183.30]) with mapi id 14.02.0387.000; Fri, 7 Mar 2014 14:33:48 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Roni Even <ron.even.tlv@gmail.com>, 'mmusic' <mmusic@ietf.org>
Thread-Topic: [MMUSIC] Bundle: Q13 receiver-Id
Thread-Index: Ac8576j/ZLk0sCPhSmugTuLrbZo+3AAGjTjU
Date: Fri, 7 Mar 2014 13:33:47 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D1D8C3D@ESESSMB209.ericsson.se>
References: <021001cf39f3$04e8de40$0eba9ac0$@gmail.com>
In-Reply-To: <021001cf39f3$04e8de40$0eba9ac0$@gmail.com>
Accept-Language: en-US
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1D1D8C3DESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrFLMWRmVeSWpSXmKPExsUyM+Jvje6eU5LBBrO3mVlMXf6YxeJvO7MD k8fOWXfZPZYs+ckUwBTFZZOSmpNZllqkb5fAlbGgbwJ7Qb9Gxaf/Z5gbGNuUuxg5OCQETCSu vrbpYuQEMsUkLtxbz9bFyMUhJHCEUeLKgk5GCGcxo0T/6T52kAY2AQuJ7n/aIA0iAk4S2xsW MILYwgK6EluPP2YFKRER0JP4dCYaosRI4tLFqewgNouAisSeE/+YQWxeAV+J/iUtYHEhAXOJ R7Oa2EBsTqDp955uABvJCHTP91NrmEBsZgFxiaYvK1kh7hSQWLLnPDOELSrx8vE/VoiafIlj /56zQ8wXlDg58wnLBEbhWUjaZyEpm4WkDCJuIPHl/W0oW1ti2cLXzBC2vkT3+9NMyOILGNlX MXIUpxYn5aYbGWxiBMbHwS2/LXYwXv5rc4hRmoNFSZz341vnICGB9MSS1OzU1ILUovii0pzU 4kOMTBycUg2MRxbr2P+d4Wpa+eJe3N+XBdGeGpYcyRO7W9awz3CaofotIDPzkoZmsjmv8+LA daFB1Wab/N4aPb6dHWtzaiv3xTLhrDmlfSdad/lyJVfsFPiTmi0R9+jg96leYXPKg+/F3ilf xtg73ctSbEtT68b8+aeeCTKaP/yTd6eGV0912hJuse2HprEpsRRnJBpqMRcVJwIAARHuh10C AAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/lPCIrAFm-5RCgerBfwuTlBC8SPI
Subject: Re: [MMUSIC] Bundle: Q13 receiver-Id
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: Fri, 07 Mar 2014 13:33:55 -0000

--_000_7594FB04B1934943A5C02806D1A2204B1D1D8C3DESESSMB209erics_
Content-Type: text/plain; charset="windows-1256"
Content-Transfer-Encoding: quoted-printable

Thank you for the input, Roni!

I assume that, for the purpose of associating media with an m- line, an ent=
ity would not need to support the OTHER attributes in the draft, right?

Regards,

Christer

Sent from Windows Mail

From: Roni Even<mailto:ron.even.tlv@gmail.com>
Sent: =FDFriday=FD, =FD7=FD =FDMarch=FD =FD2014 =FD12=FD:=FD50
To: 'mmusic'<mailto:mmusic@ietf.org>

Hi,
In draft-even-mmusic-application-token-02<http://tools.ietf.org/html/draft-=
even-mmusic-application-token-02> there is a recv-appId token that can be u=
sed as the receiver-Id. Based on the discussion in the meeting it seems tha=
t the recv-appId  usage  will be needed for the case when the offerer recei=
ves media before the SDP answer and can use the recv-appId to identify the =
correlation to an m-line / RTP stream   in the SDP.  This will also works f=
or the same PT number.

Roni

--_000_7594FB04B1934943A5C02806D1A2204B1D1D8C3DESESSMB209erics_
Content-Type: text/html; charset="windows-1256"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dwindows-1=
256">
<meta name=3D"generator" content=3D"Windows Mail 17.5.9600.20413">
<style><!--=0A=
p.MsoNormal, li.MsoNormal, div.MsoNormal {=0A=
margin:0in;=0A=
margin-bottom:.0001pt;=0A=
font-size:11.0pt;=0A=
font-family:"Calibri","sans-serif";=0A=
}=0A=
=0A=
a:link, span.MsoHyperlink {=0A=
color:blue;=0A=
text-decoration:underline;=0A=
}=0A=
=0A=
span.MsoHyperlinkFollowed {=0A=
color:purple;=0A=
text-decoration:underline;=0A=
}=0A=
=0A=
span.EmailStyle17 {=0A=
font-family:"Calibri","sans-serif";=0A=
color:windowtext;=0A=
}=0A=
=0A=
.MsoChpDefault {=0A=
font-family:"Calibri","sans-serif";=0A=
}=0A=
=0A=
div.WordSection1 {=0A=
}=0A=
--></style><style data-externalstyle=3D"true"><!--=0A=
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph {=0A=
margin-top:0in;=0A=
margin-right:0in;=0A=
margin-bottom:0in;=0A=
margin-left:.5in;=0A=
margin-bottom:.0001pt;=0A=
}=0A=
p.MsoNormal, li.MsoNormal, div.MsoNormal {=0A=
margin:0in;=0A=
margin-bottom:.0001pt;=0A=
}=0A=
p.MsoListParagraphCxSpFirst, li.MsoListParagraphCxSpFirst, div.MsoListParag=
raphCxSpFirst, =0A=
p.MsoListParagraphCxSpMiddle, li.MsoListParagraphCxSpMiddle, div.MsoListPar=
agraphCxSpMiddle, =0A=
p.MsoListParagraphCxSpLast, li.MsoListParagraphCxSpLast, div.MsoListParagra=
phCxSpLast {=0A=
margin-top:0in;=0A=
margin-right:0in;=0A=
margin-bottom:0in;=0A=
margin-left:.5in;=0A=
margin-bottom:.0001pt;=0A=
line-height:115%;=0A=
}=0A=
--></style>
</head>
<body dir=3D"ltr">
<div data-externalstyle=3D"false" dir=3D"ltr" style=3D"font-family: 'Calibr=
i', 'Segoe UI', 'Meiryo', 'Microsoft YaHei UI', 'Microsoft JhengHei UI', 'M=
algun Gothic', 'sans-serif';font-size:12pt;">
<div>Thank you for the input, Roni!</div>
<div><br>
</div>
<div>I assume that, for the purpose of associating media with an m- line, a=
n entity would not need to support the OTHER attributes in the draft, right=
?</div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Christer<br>
</div>
<div data-signatureblock=3D"true">
<div><br>
</div>
<div>Sent from Windows Mail</div>
<div><br>
</div>
</div>
<div style=3D"padding-top: 5px; border-top-color: rgb(229, 229, 229); borde=
r-top-width: 1px; border-top-style: solid;">
<div><font face=3D" 'Calibri', 'Segoe UI', 'Meiryo', 'Microsoft YaHei UI', =
'Microsoft JhengHei UI', 'Malgun Gothic', 'sans-serif'" style=3D"line-heigh=
t: 15pt; letter-spacing: 0.02em; font-family: &quot;Calibri&quot;, &quot;Se=
goe UI&quot;, &quot;Meiryo&quot;, &quot;Microsoft YaHei UI&quot;, &quot;Mic=
rosoft JhengHei UI&quot;, &quot;Malgun Gothic&quot;, &quot;sans-serif&quot;=
; font-size: 12pt;"><b>From:</b>&nbsp;<a href=3D"mailto:ron.even.tlv@gmail.=
com" target=3D"_parent">Roni
 Even</a><br>
<b>Sent:</b>&nbsp;=FDFriday=FD, =FD7=FD =FDMarch=FD =FD2014 =FD12=FD:=FD50<=
br>
<b>To:</b>&nbsp;<a href=3D"mailto:mmusic@ietf.org" target=3D"_parent">'mmus=
ic'</a></font></div>
</div>
<div><br>
</div>
<div dir=3D"">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi,</p>
<p class=3D"MsoNormal">In <a href=3D"http://tools.ietf.org/html/draft-even-=
mmusic-application-token-02" target=3D"_parent">
draft-even-mmusic-application-token-02</a> there is a recv-appId token that=
 can be used as the receiver-Id. Based on the discussion in the meeting it =
seems that the recv-appId &nbsp;usage &nbsp;will be needed for the case whe=
n the offerer receives media before the SDP
 answer and can use the recv-appId to identify the correlation to an m-line=
 / RTP stream &nbsp;&nbsp;in the SDP.&nbsp; This will also works for the sa=
me PT number.</p>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal">Roni </p>
</div>
</div>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B1D1D8C3DESESSMB209erics_--


From nobody Sun Mar  9 23:21:51 2014
Return-Path: <juberti@google.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 53C541A03D9 for <mmusic@ietfa.amsl.com>; Sun,  9 Mar 2014 23:21:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.925
X-Spam-Level: 
X-Spam-Status: No, score=-1.925 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001] autolearn=ham
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 a54-JbnplAug for <mmusic@ietfa.amsl.com>; Sun,  9 Mar 2014 23:21:44 -0700 (PDT)
Received: from mail-ve0-x22d.google.com (mail-ve0-x22d.google.com [IPv6:2607:f8b0:400c:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 02BFD1A03D3 for <mmusic@ietf.org>; Sun,  9 Mar 2014 23:21:43 -0700 (PDT)
Received: by mail-ve0-f173.google.com with SMTP id oy12so6545541veb.18 for <mmusic@ietf.org>; Sun, 09 Mar 2014 23:21:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=VFL9/+zF4UL1bMU00UVxmZWMP9GdU8QGKzlkKOgoo48=; b=iqVh4VEOEISZBSp1y3uOs17A+NC9qiYphPDoHY8/Z95bfyp4hpAM4yjeKWcie1c9TE O8yZ9bbrhvLbh16qwfxVkRvW8DRYmLgeQ5w2bDZgampuUC8JxVnD+Mauqmyuy92KNs1M 0WTnfWge7AhOeLlphx1Q/QMtVfE3uzRH9YRguPuDbEw+9/8kZKfjLpVxA4usLZGOb7XX 0jhIfCFlP3o9DVwGhZI8EJtglmQiE9oKscGDe7lvwBv8K5R5y9LS8XuoI4yaKiSiXZ7V mHIaMlSE7H24kQoCty5dKnPsn5d8bljvXMt8K7WF6JSQUZGFL0DZvVJVyDJMwpW/IwGm 6eXQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to :content-type; bh=VFL9/+zF4UL1bMU00UVxmZWMP9GdU8QGKzlkKOgoo48=; b=QTTCaHx33SzAPS8tP8z2oHZFqNmcm1LPNeME7OVrpKTLKRywgzdXXKgSfVvF8T2Px5 SOOLKp7jsDuOHJQ9fOLF/UCyiJFQO2iAB/UAtKI9I2jbO7Es8cA4Vxsytg16fBRZHjhx kz9UlWFo1QTpo9Y4HZEiyTVZyvqBSaw55Fh2XAD+VkwzrE1lr0MlnbQUWG0FhaQMmWLH YbLin9JItERUaL/iQ89nICmQ+vkitwySPOG8jWTGne5dfAkvW1amB2plh4xw4G6ZKw9w /t3wq8VUTXRBbd1rhtiQAxhN6whX2aQpXg3RvSQS+tm59nypyDZNfHjKIZOudysIdSjD ujdQ==
X-Gm-Message-State: ALoCoQnrPfbcQWXLvr3wrSd0/UfCFrMHZYdRwYNIbRrn2idtK+abjpfrNEqFSjH4HkGU7HS6+clGjQ8jSwW58TGGF6AnRmQiPtMbJn+BtQKzBl5+LQbMLneGcve3KdRFX4Uhmtu3yW7eyJlOBDYo6rshiprzLS5KYHTM7Bt1fKsQMIC3H+00U1rtnR8IqyE2p+Jr/ISZdIBz
X-Received: by 10.58.100.100 with SMTP id ex4mr21490634veb.2.1394432498467; Sun, 09 Mar 2014 23:21:38 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.26.43 with HTTP; Sun, 9 Mar 2014 23:21:18 -0700 (PDT)
From: Justin Uberti <juberti@google.com>
Date: Mon, 10 Mar 2014 06:21:18 +0000
Message-ID: <CAOJ7v-3oi-Qtsk6qiPVsAUfzEQsvgt4h6RhgfKDNUv_-47wpOA@mail.gmail.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>, Martin Thomson <martin.thomson@gmail.com>
Content-Type: multipart/alternative; boundary=047d7b33c706bc1c6e04f43a9dd6
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/uQdckZB8SuyTA3eUjGjqw87IY4w
Subject: [MMUSIC] Generalizing the aggressive nomination bugfix
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, 10 Mar 2014 06:21:50 -0000

--047d7b33c706bc1c6e04f43a9dd6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

In the WG session on Monday, Ari mentioned that the aggressive nomination
bug of controller and controlled not agreeing on the candidate pair to use
could be rectified by having the controlled side switch its preferred
candidate pair to be the one that it received secure media on (or if not
using controlled media, when the controlling side=E2=80=99s ICE checks fina=
lly got
through).

I think there is an opportunity here to improve the overall flexibility of
ICE. Currently, Regular Nomination allows the controller to have a fair
amount of discretion in choosing which candidate pair it wants to pick; it
could use metrics such as RTT, or perhaps one of the values mentioned in
DISCUSS to make its selection, instead of using the static PRIORITY value.
Aggressive Nomination, while faster in initially establishing media, does
not afford this same discretion; according to 5245, S 8.1.1.2, ICE uses the
highest PRIORITY candidate pair. So it would be great if there was a way to
allow the controller have the same discretion for choosing the selected
candidate pair, while also doing Aggressive Nomination.

I think this can easily be done using Ari=E2=80=99s solution in a general w=
ay. In
short, any time secure media packets are received by the controlled side,
it should use that candidate pair to send its own media. (Secure media is
needed to prevent an attacker from tricking the controlled side into
sending media to an arbitrary address.) If secure media is not used, the
controller could include a new attribute, something like a new
PREFERRED-CANDIDATE attribute (or perhaps an updated PRIORITY attribute,
set to the max ICE priority), to tell the controlled side which candidate
pair should be used.

This would allow the controller to do periodic RTT checks, perhaps using
the ICE consent mechanism, and dynamically change the media path as needed.

--047d7b33c706bc1c6e04f43a9dd6
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">







<p class=3D"">In the WG session on Monday, Ari mentioned that the aggressiv=
e nomination bug of controller and controlled not agreeing on the candidate=
 pair to use could be rectified by having the controlled side switch its pr=
eferred candidate pair to be the one that it received secure media on (or i=
f not using controlled media, when the controlling side=E2=80=99s ICE check=
s finally got through).</p>


<p class=3D"">I think there is an opportunity here to improve the overall f=
lexibility of ICE. Currently, Regular Nomination allows the controller to h=
ave a fair amount of discretion in choosing which candidate pair it wants t=
o pick; it could use metrics such as RTT, or perhaps one of the values ment=
ioned in DISCUSS to make its selection, instead of using the static PRIORIT=
Y value. Aggressive Nomination, while faster in initially establishing medi=
a, does not afford this same discretion; according to 5245, S 8.1.1.2, ICE =
uses the highest PRIORITY candidate pair. So it would be great if there was=
 a way to allow the controller have the same discretion for choosing the se=
lected candidate pair, while also doing Aggressive Nomination.</p>


<p class=3D"">I think this can easily be done using Ari=E2=80=99s solution =
in a general way. In short, any time secure media packets are received by t=
he controlled side, it should use that candidate pair to send its own media=
. (Secure media is needed to prevent an attacker from tricking the controll=
ed side into sending media to an arbitrary address.) If secure media is not=
 used, the controller could include a new attribute, something like a new P=
REFERRED-CANDIDATE attribute (or perhaps an updated PRIORITY attribute, set=
 to the max ICE priority), to tell the controlled side which candidate pair=
 should be used.</p>


<p class=3D"">This would allow the controller to do periodic RTT checks, pe=
rhaps using the ICE consent mechanism, and dynamically change the media pat=
h as needed.<br></p></div>

--047d7b33c706bc1c6e04f43a9dd6--


From nobody Mon Mar 10 05:26:50 2014
Return-Path: <harald@alvestrand.no>
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 EA9DB1A0423 for <mmusic@ietfa.amsl.com>; Mon, 10 Mar 2014 05:26:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level: 
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547] autolearn=ham
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 0nL_7bXRo3xY for <mmusic@ietfa.amsl.com>; Mon, 10 Mar 2014 05:26:43 -0700 (PDT)
Received: from mork.alvestrand.no (mork.alvestrand.no [158.38.152.117]) by ietfa.amsl.com (Postfix) with ESMTP id 1310F1A041D for <mmusic@ietf.org>; Mon, 10 Mar 2014 05:26:43 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mork.alvestrand.no (Postfix) with ESMTP id 6BDDB7C49BD; Mon, 10 Mar 2014 13:26:37 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at alvestrand.no
Received: from mork.alvestrand.no ([127.0.0.1]) by localhost (mork.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WEETHgK+ccM7; Mon, 10 Mar 2014 13:26:36 +0100 (CET)
Received: from [IPv6:2001:470:de0a:27:8cc5:2f88:5199:2784] (unknown [IPv6:2001:470:de0a:27:8cc5:2f88:5199:2784]) by mork.alvestrand.no (Postfix) with ESMTPSA id CB3E77C034B; Mon, 10 Mar 2014 13:26:35 +0100 (CET)
Message-ID: <531DAF79.6070505@alvestrand.no>
Date: Mon, 10 Mar 2014 13:26:33 +0100
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Martin Thomson <martin.thomson@gmail.com>
References: <53185B8E.2070808@nteczone.com>	<C8EB64C0-3140-477C-9373-BD36B4B1A64B@ericsson.com>	<53187415.2000108@nteczone.com>	<C1D662DF-E3E3-45CD-991F-8090CD7130E0@ericsson.com>	<CABkgnnWOVf-72jeLbo74dbpxwhiYwgOjsfte2Cx3Voi_YRxdTg@mail.gmail.com>	<5319A928.8040703@alvestrand.no> <CABkgnnVghjLVBPQiYwjgH1uVac1Qm5MwWj09e1uk90shVjss3w@mail.gmail.com>
In-Reply-To: <CABkgnnVghjLVBPQiYwjgH1uVac1Qm5MwWj09e1uk90shVjss3w@mail.gmail.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/r6HTDpYOoVJ5xlUdiaGqI9esy78
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] SCTP AppID
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, 10 Mar 2014 12:26:48 -0000

On 03/07/2014 12:22 PM, Martin Thomson wrote:
> On 7 March 2014 11:10, Harald Alvestrand <harald@alvestrand.no> wrote:
>> One irritating case in our particular use case is that we actually don't
>> know the lowest layers ahead of time.
> The fact that we are using wired Ethernet vs. WiFi is generally not
> visible at the level we're doing this identification either.
>
> If it does not matter to the protocol semantics, then I believe it to
> be safe to use the same identifier for two similar-but-not-identical
> stacks.
>
> Yes, one might argue that TURN-TCP encapsulation is tangibly different
> to non-encapsulated SRTP.  We can talk about those distinctions and
> whether they require different identifiers, but in this case, I don't
> see any need for distinction.
I think we're both arguing that a tag should only identify
SCTP-over-DTLS as the protocol stack. If so, we agree,

No opinion on whether ALPN is useful for our use case; I don't
understand it yet (haven't read the spec), so haven't formed one.

          Harald

-- 
Surveillance is pervasive. Go Dark.


From nobody Tue Mar 11 00:56:55 2014
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 D780F1A0139 for <mmusic@ietfa.amsl.com>; Tue, 11 Mar 2014 00:56:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.869
X-Spam-Level: 
X-Spam-Status: No, score=-2.869 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, HTML_FONT_FACE_BAD=0.981, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 c8L39E6HJjXq for <mmusic@ietfa.amsl.com>; Tue, 11 Mar 2014 00:56:52 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id 89FB21A0369 for <mmusic@ietf.org>; Tue, 11 Mar 2014 00:56:51 -0700 (PDT)
X-AuditID: c1b4fb2d-b7f5d8e000002a7b-cd-531ec1bdc3b0
Received: from ESESSHC012.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 05.D7.10875.DB1CE135; Tue, 11 Mar 2014 08:56:45 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.216]) by ESESSHC012.ericsson.se ([153.88.183.54]) with mapi id 14.02.0387.000; Tue, 11 Mar 2014 08:56:44 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Roni Even <ron.even.tlv@gmail.com>, 'mmusic' <mmusic@ietf.org>
Thread-Topic: [MMUSIC] Bundle: Q13 receiver-Id
Thread-Index: Ac8576j/ZLk0sCPhSmugTuLrbZo+3AAGjTjUAL1GWy4=
Date: Tue, 11 Mar 2014 07:56:44 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D2009EF@ESESSMB209.ericsson.se>
References: <021001cf39f3$04e8de40$0eba9ac0$@gmail.com>, <7594FB04B1934943A5C02806D1A2204B1D1D8C3D@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D1D8C3D@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.16]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1D2009EFESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrMLMWRmVeSWpSXmKPExsUyM+Jvje7eg3LBBlNny1hMXf6YxeJvO7MD k8fOWXfZPZYs+ckUwBTFZZOSmpNZllqkb5fAlTGh1aDguVnFvMd5DYx9+l2MnBwSAiYSt+Zf Y4GwxSQu3FvP1sXIxSEkcIhRYv7kvSwQzhJGiSN/LzN1MXJwsAlYSHT/0wZpEBFwktjesIAR xBYW0JV4e+sSC0iJiICexKcz0RAlVhKtc2ezgtgsAqoS5xceYQUp4RXwlbjxKAwkLCRQKXG4 5TfYCZwCfhLfOk8ygdiMQOd8P7UGzGYWEJe49WQ+E8SZAhJL9pxnhrBFJV4+/scKYStK7Dzb zgxRny9x6VMj2ExeAUGJkzOfsExgFJmFZNQsJGWzkJRBxA0kvry/DWVrSyxb+JoZwtaX6H5/ mglZfAEj+ypG9tzEzJz0csNNjMCIObjlt+4OxlPnRA4xSnOwKInzfnjrHCQkkJ5YkpqdmlqQ WhRfVJqTWnyIkYmDU6qBMaR1Lt/m9LxPxQ0sJikqtumGaf+aZuzYmaRz+u3FD9W2+ktL91f5 sWdwvml7JHDI+cyjlVd3vhD0DujoNas6WMM1/RhjXtPK5RZ/ZBRULp9Iv7zpn9AtQ8v9+dGK M6fKfUhiv5i3Z+JBn6gC02l/7/8QvmSd+IPx0K1DW9ZeX3x1Fl+LbG2pqBJLcUaioRZzUXEi AGVhRyJmAgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/ftRv1uGcG1uMNrJNM8YKYUg-Ik4
Subject: Re: [MMUSIC] Bundle: Q13 receiver-Id
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: Tue, 11 Mar 2014 07:56:54 -0000

--_000_7594FB04B1934943A5C02806D1A2204B1D2009EFESESSMB209erics_
Content-Type: text/plain; charset="windows-1256"
Content-Transfer-Encoding: quoted-printable


Hi,

If people are ok with using the mechanism in Roni's draft, please indicate =
so.

Please also indicate if you are NOT ok to use it, or you think there is ano=
ther mechanism we should at least verify.

Please also indicate if you don't care what mechanism we use - just to make=
 sure we get community input :)

Note that if the "receiver-id" will require a new draft, the publication of=
 BUNDLE will be dependent of that draft, so I think we should make a decisi=
on which way to go asap.

Regards,

Christer


________________________________
From: mmusic [mmusic-bounces@ietf.org] on behalf of Christer Holmberg [chri=
ster.holmberg@ericsson.com]
Sent: Friday, 07 March 2014 3:33 PM
To: Roni Even; 'mmusic'
Subject: Re: [MMUSIC] Bundle: Q13 receiver-Id

Thank you for the input, Roni!

I assume that, for the purpose of associating media with an m- line, an ent=
ity would not need to support the OTHER attributes in the draft, right?

Regards,

Christer

Sent from Windows Mail

From: Roni Even<mailto:ron.even.tlv@gmail.com>
Sent: =FDFriday=FD, =FD7=FD =FDMarch=FD =FD2014 =FD12=FD:=FD50
To: 'mmusic'<mailto:mmusic@ietf.org>

Hi,
In draft-even-mmusic-application-token-02<http://tools.ietf.org/html/draft-=
even-mmusic-application-token-02> there is a recv-appId token that can be u=
sed as the receiver-Id. Based on the discussion in the meeting it seems tha=
t the recv-appId  usage  will be needed for the case when the offerer recei=
ves media before the SDP answer and can use the recv-appId to identify the =
correlation to an m-line / RTP stream   in the SDP.  This will also works f=
or the same PT number.

Roni

--_000_7594FB04B1934943A5C02806D1A2204B1D2009EFESESSMB209erics_
Content-Type: text/html; charset="windows-1256"
Content-Transfer-Encoding: quoted-printable

<html dir=3D"ltr">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dwindows-1=
256">
<style>=0A=
<!--=0A=
p.MsoNormal, li.MsoNormal, div.MsoNormal=0A=
	{margin:0in;=0A=
	margin-bottom:.0001pt;=0A=
	font-size:11.0pt;=0A=
	font-family:"Calibri","sans-serif"}=0A=
a:link, span.MsoHyperlink=0A=
	{color:blue;=0A=
	text-decoration:underline}=0A=
span.MsoHyperlinkFollowed=0A=
	{color:purple;=0A=
	text-decoration:underline}=0A=
span.EmailStyle17=0A=
	{font-family:"Calibri","sans-serif";=0A=
	color:windowtext}=0A=
.MsoChpDefault=0A=
	{font-family:"Calibri","sans-serif"}=0A=
-->=0A=
</style><style>=0A=
<!--=0A=
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph=0A=
	{margin-top:0in;=0A=
	margin-right:0in;=0A=
	margin-bottom:0in;=0A=
	margin-left:.5in;=0A=
	margin-bottom:.0001pt}=0A=
p.MsoNormal, li.MsoNormal, div.MsoNormal=0A=
	{margin:0in;=0A=
	margin-bottom:.0001pt}=0A=
p.MsoListParagraphCxSpFirst, li.MsoListParagraphCxSpFirst, div.MsoListParag=
raphCxSpFirst, p.MsoListParagraphCxSpMiddle, li.MsoListParagraphCxSpMiddle,=
 div.MsoListParagraphCxSpMiddle, p.MsoListParagraphCxSpLast, li.MsoListPara=
graphCxSpLast, div.MsoListParagraphCxSpLast=0A=
	{margin-top:0in;=0A=
	margin-right:0in;=0A=
	margin-bottom:0in;=0A=
	margin-left:.5in;=0A=
	margin-bottom:.0001pt;=0A=
	line-height:115%}=0A=
-->=0A=
</style><style id=3D"owaParaStyle" type=3D"text/css">P {margin-top:0;margin=
-bottom:0;}</style>
</head>
<body ocsi=3D"0" fpstyle=3D"1" dir=3D"ltr">
<div style=3D"direction: ltr;font-family: Tahoma;color: #000000;font-size: =
10pt;"><br>
Hi,<br>
<br>
If people are ok with using the mechanism in Roni's draft, please indicate =
so.<br>
<br>
Please also indicate if you are NOT ok to use it, or you think there is ano=
ther mechanism we should at least verify.<br>
<br>
Please also indicate if you don't care what mechanism we use - just to make=
 sure we get community input :)<br>
<br>
Note that if the &quot;receiver-id&quot; will require a new draft, the publ=
ication of BUNDLE will be dependent of that draft, so I think we should mak=
e a decision which way to go asap.<br>
<br>
Regards,<br>
<br>
Christer<br>
<br>
<br>
<div style=3D"font-family: Times New Roman; color: #000000; font-size: 16px=
">
<hr tabindex=3D"-1">
<div style=3D"direction: ltr;" id=3D"divRpF548279"><font color=3D"#000000" =
face=3D"Tahoma" size=3D"2"><b>From:</b> mmusic [mmusic-bounces@ietf.org] on=
 behalf of Christer Holmberg [christer.holmberg@ericsson.com]<br>
<b>Sent:</b> Friday, 07 March 2014 3:33 PM<br>
<b>To:</b> Roni Even; 'mmusic'<br>
<b>Subject:</b> Re: [MMUSIC] Bundle: Q13 receiver-Id<br>
</font><br>
</div>
<div></div>
<div>
<div dir=3D"ltr" style=3D"font-family:'Calibri','Segoe UI','Meiryo','Micros=
oft YaHei UI','Microsoft JhengHei UI','Malgun Gothic','sans-serif'; font-si=
ze:12pt">
<div>Thank you for the input, Roni!</div>
<div><br>
</div>
<div>I assume that, for the purpose of associating media with an m- line, a=
n entity would not need to support the OTHER attributes in the draft, right=
?</div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Christer<br>
</div>
<div>
<div><br>
</div>
<div>Sent from Windows Mail</div>
<div><br>
</div>
</div>
<div style=3D"padding-top:5px; border-top-color:rgb(229,229,229); border-to=
p-width:1px; border-top-style:solid">
<div><font style=3D"line-height:15pt; letter-spacing:0.02em; font-family:&q=
uot;Calibri&quot;,&quot;Segoe UI&quot;,&quot;Meiryo&quot;,&quot;Microsoft Y=
aHei UI&quot;,&quot;Microsoft JhengHei UI&quot;,&quot;Malgun Gothic&quot;,&=
quot;sans-serif&quot;; font-size:12pt" face=3D" 'Calibri', 'Segoe UI', 'Mei=
ryo', 'Microsoft YaHei UI', 'Microsoft JhengHei UI', 'Malgun Gothic', 'sans=
-serif'"><b>From:</b>&nbsp;<a href=3D"mailto:ron.even.tlv@gmail.com" target=
=3D"_blank">Roni
 Even</a><br>
<b>Sent:</b>&nbsp;=FDFriday=FD, =FD7=FD =FDMarch=FD =FD2014 =FD12=FD:=FD50<=
br>
<b>To:</b>&nbsp;<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">'mmusi=
c'</a></font></div>
</div>
<div><br>
</div>
<div dir=3D"">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi,</p>
<p class=3D"MsoNormal">In <a href=3D"http://tools.ietf.org/html/draft-even-=
mmusic-application-token-02" target=3D"_blank">
draft-even-mmusic-application-token-02</a> there is a recv-appId token that=
 can be used as the receiver-Id. Based on the discussion in the meeting it =
seems that the recv-appId &nbsp;usage &nbsp;will be needed for the case whe=
n the offerer receives media before the SDP
 answer and can use the recv-appId to identify the correlation to an m-line=
 / RTP stream &nbsp;&nbsp;in the SDP.&nbsp; This will also works for the sa=
me PT number.</p>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal">Roni </p>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B1D2009EFESESSMB209erics_--


From nobody Tue Mar 11 01:56:43 2014
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 DA1281A03DB for <mmusic@ietfa.amsl.com>; Tue, 11 Mar 2014 01:56:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 9uap8OUr2vQe for <mmusic@ietfa.amsl.com>; Tue, 11 Mar 2014 01:56:38 -0700 (PDT)
Received: from sesbmg20.ericsson.net (sesbmg20.ericsson.net [193.180.251.56]) by ietfa.amsl.com (Postfix) with ESMTP id 291521A03D9 for <mmusic@ietf.org>; Tue, 11 Mar 2014 01:56:36 -0700 (PDT)
X-AuditID: c1b4fb38-b7f418e000001099-53-531ecfbe0899
Received: from ESESSHC011.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg20.ericsson.net (Symantec Mail Security) with SMTP id 43.44.04249.EBFCE135; Tue, 11 Mar 2014 09:56:30 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.216]) by ESESSHC011.ericsson.se ([153.88.183.51]) with mapi id 14.02.0387.000; Tue, 11 Mar 2014 09:56:29 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: BUNDLE: Q9/Q13: Payload type value re-usage and associating RTP packets with m- line
Thread-Index: Ac89B6OYHyKFgXivSIaXJxW+k4A5DQ==
Date: Tue, 11 Mar 2014 08:56:29 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D202004@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.17]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1D202004ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrMLMWRmVeSWpSXmKPExsUyM+Jvje6+83LBBtevmFpMXf6YxYHRY8mS n0wBjFFcNimpOZllqUX6dglcGXsfbWMrWJJccXLKKtYGxhshXYwcHBICJhI3L1Z2MXICmWIS F+6tZwOxhQSOMEp0LGbtYuQCspcwShzs7mcHqWcTsJDo/qcNUiMioC7xdW8PM0hYWCBeouWQ OkQ4RWLbrs/MELaexLKOI0wgNouAqsTeGZcZQWxeAV+J6fNvsILYjEBrv59aA1bDLCAucevJ fCaIcwQkluw5zwxhi0q8fPyPFeJiRYnl/XIQ5fkSZ18vZIcYKShxcuYTlgmMQrOQTJqFpGwW kjKIuI7Egt2f2CBsbYllC18zw9hnDjxmQhZfwMi+ipGjOLU4KTfdyGATIzDgD275bbGD8fJf m0OM0hwsSuK8H986BwkJpCeWpGanphakFsUXleakFh9iZOLglGpgjOmoqbyyKVl6OdvaO7tr LxuLtrMFdsztdezt3764W1Jz6+kpiZ8OF5pv761UWrjk09pda3ptm4rlvL69kS79EvHzbP86 mX9e2prT4x6GvHKW6Ou5Wfuo0/DqmfdpqWXfn5i6vmqNP1T+5AxbwK+pMc/+3rLMfBckXzhr vZy+0S39B4s2cTG8UmIpzkg01GIuKk4EAE3TQ4tGAgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/ORaQYzfaN1subFrROSIud93_FpY
Subject: [MMUSIC] BUNDLE: Q9/Q13: Payload type value re-usage and associating RTP packets with m- line
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: Tue, 11 Mar 2014 08:56:42 -0000

--_000_7594FB04B1934943A5C02806D1A2204B1D202004ESESSMB209erics_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

Based on the discussion/decision in London, I've drafted the following text=
 regarding the usage of identical PT values, and the usage of the "receiver=
-id" value in order to be able to associate received RTP packets with the c=
orrect m- line (when the same payload type value is used inside multiple m-=
 lines within the BUNDLE group).

I may change some words later, in order to align with the rest of the docum=
ent, but please take a look and see whether you are ok with the content, an=
d whether you think it reflects the decisions in the meeting.
Regards,

Christer

---------------------------------------


X.X         RTP Considerations

X.X.1      Multiple Usage Of Identical Payload Type (PT) Value Within A BUN=
DLE Group

A BUNDLE group can contain multiple m- lines associated with RTP media. As =
all RTP media associated with those m- lines belong to the same RTP session=
 [insert-reference], in order for a payload type value to used inside more =
than one m- line, all codecs associated with the payload type numbers MUST =
share an identical codec configuration. This means that the codecs MUST sha=
re the same media type, encoding name, clock rate and any parameter that ca=
n affect the codec configuration and packetizsation. [ID.draft-ietf-mmusic-=
sdp-mux-attributes] lists SDP attribute values that must be identical for a=
ll codecs using the same payload type value.

X.X.2      Associating RTP Packets With Correct SDP Media Description Withi=
n A BUNDLE Group

In general, there are multiple mechanisms that can be used by an endpoint i=
n order to associate received RTP packets with the m- line associated with =
the RTP packets. Such mechanisms include using the local address:port on wh=
ich the RTP packets are received, the payload type value carried inside the=
 RTP packets, the SSRC values carried inside the RTP packets, and other m- =
line specific information carried inside the RTP packets.

Within a BUNDLE group, as all RTP packets are transported using the same 5-=
tuple, the local address:port cannot be used to associate received RTP pack=
ets with the correct m- line.

As described in section X.X.1, the same payload type value might be used in=
side RTP packets associated with multiple m- lines. In such cases, the payl=
oad type value cannot be used to associate received RTP packets with the co=
rrect m- line.

Endpoints can inform each other which SSRC values they will use inside sent=
 RTP packets by, in SDP Offers and Answers, assigning an SDP 'ssrc' attribu=
te [ref-to-be-added] to each m- line which contains a payload type value th=
at is also used inside another m- line within the BUNDLE group. As the SSRC=
 values will be carried inside the RTP packets, the endpoints can then use =
that information to associate received RTP packets with the correct m- line=
. However, an offerer will not know which SSRC values the answerer will use=
 until it has received the SDP Answer providing that information. Due to th=
is, before the offerer has received the SDP Answer, it will not be able to =
associate received RTP packets with the correct m- line using the SSRC valu=
es.

In order for endpoints to always be able to associate received RTP packets =
with the correct m- line they MUST, in SDP Offers and Answers, assign an SD=
P "receiver-id" attribute [receiver-id-reference-to-be-added] to each m- li=
ne which contains a payload type value that is also used inside another m- =
line within the BUNDLE group. If an endpoint accepts a BUNDLE group, it MUS=
T insert the "receiver-id" value in the associated RTP packets, associated =
with the BUNDLE group, sent towards the remote endpoint, as described in [r=
eceiver-id-reference-to-be-added]. If the endpoint cannot, or is not willin=
g to, insert the "receiver-id" value in sent RTP packets, it MUST NOT accep=
t the BUNDLE group.

Editor's note: [receiver-id-reference-to-be-added] will describe in how man=
y RTP packets the receiver-id value will be sent.



--_000_7594FB04B1934943A5C02806D1A2204B1D202004ESESSMB209erics_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Hi,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Based on the discussion/decisio=
n in London, I&#8217;ve drafted the following text regarding the usage of i=
dentical PT values, and the usage of the &#8220;receiver-id&#8221; value in=
 order to be able to associate received RTP packets with
 the correct m- line (when the same payload type value is used inside multi=
ple m- lines within the BUNDLE group).<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">I may change some words later, =
in order to align with the rest of the document, but please take a look and=
 see whether you are ok with the content, and whether you think it reflects=
 the decisions in the meeting.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Regards,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Christer<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">-------------------------------=
--------<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">X.X&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp; RTP Considerations<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">X.X.1&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; Multiple Usage Of Identical Payload Type (PT) Value Within A BUNDLE Gr=
oup<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">A BUNDLE group can contain mult=
iple m- lines associated with RTP media. As all RTP media associated with t=
hose m- lines belong to the same RTP session [insert-reference], in order f=
or a payload type value to used inside
 more than one m- line, all codecs associated with the payload type numbers=
 MUST share an identical codec configuration. This means that the codecs MU=
ST share the same media type, encoding name, clock rate and any parameter t=
hat can affect the codec configuration
 and packetizsation. [ID.</span>draft-ietf-mmusic-sdp-mux-attributes] lists=
 SDP attribute values that must be identical for all codecs using the same =
payload type value.<span lang=3D"EN-GB"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">X.X.2&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; Associating RTP Packets With Correct SDP Media Description Within A BU=
NDLE Group<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">In general, there are multiple =
mechanisms that can be used by an endpoint in order to associate received R=
TP packets with the m- line associated with the RTP packets. Such mechanism=
s include using the local address:port
 on which the RTP packets are received, the payload type value carried insi=
de the RTP packets, the SSRC values carried inside the RTP packets, and oth=
er m- line specific information carried inside the RTP packets.<o:p></o:p><=
/span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Within a BUNDLE group, as all R=
TP packets are transported using the same 5-tuple, the local address:port c=
annot be used to associate received RTP packets with the correct m- line.<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">As described in section X.X.1, =
the same payload type value might be used inside RTP packets associated wit=
h multiple m- lines. In such cases, the payload type value cannot be used t=
o associate received RTP packets with
 the correct m- line.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Endpoints can inform each other=
 which SSRC values they will use inside sent RTP packets by, in SDP Offers =
and Answers, assigning an SDP &#8216;ssrc&#8217; attribute [ref-to-be-added=
] to each m- line which contains a payload type
 value that is also used inside another m- line within the BUNDLE group. As=
 the SSRC values will be carried inside the RTP packets, the endpoints can =
then use that information to associate received RTP packets with the correc=
t m- line. However, an offerer will
 not know which SSRC values the answerer will use until it has received the=
 SDP Answer providing that information. Due to this, before the offerer has=
 received the SDP Answer, it will not be able to associate received RTP pac=
kets with the correct m- line using
 the SSRC values.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">In order for endpoints to alway=
s be able to associate received RTP packets with the correct m- line they M=
UST, in SDP Offers and Answers, assign an SDP &#8220;receiver-id&#8221; att=
ribute [receiver-id-reference-to-be-added] to each
 m- line which contains a payload type value that is also used inside anoth=
er m- line within the BUNDLE group. If an endpoint accepts a BUNDLE group, =
it MUST insert the &#8220;receiver-id&#8221; value in the associated RTP pa=
ckets, associated with the BUNDLE group, sent
 towards the remote endpoint, as described in [receiver-id-reference-to-be-=
added]. If the endpoint cannot, or is not willing to, insert the &#8220;rec=
eiver-id&#8221; value in sent RTP packets, it MUST NOT accept the BUNDLE gr=
oup.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Editor&#8217;s note: [receiver-=
id-reference-to-be-added] will describe in how many RTP packets the receive=
r-id value will be sent.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B1D202004ESESSMB209erics_--


From nobody Tue Mar 11 03:49:23 2014
Return-Path: <fredrik.bergholtz@sverigesradio.se>
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 5FFF21A068D for <mmusic@ietfa.amsl.com>; Tue, 11 Mar 2014 03:49:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.05
X-Spam-Level: 
X-Spam-Status: No, score=-1.05 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_SE=0.35, HTML_MESSAGE=0.001, J_CHICKENPOX_18=0.6, 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 b_nMKIUXNuS4 for <mmusic@ietfa.amsl.com>; Tue, 11 Mar 2014 03:49:19 -0700 (PDT)
Received: from mail-1.sr.se (mail-1.sr.se [IPv6:2001:67c:d8:ed80::87]) by ietfa.amsl.com (Postfix) with ESMTP id B423A1A040E for <mmusic@ietf.org>; Tue, 11 Mar 2014 03:49:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sverigesradio.se; s=sverigesradio; h=x-halon-id:cc:received:received:from:to:subject:thread-topic:thread-index: date:message-id:accept-language:content-language:x-ms-has-attach: x-ms-tnef-correlator:content-type:mime-version; bh=qsbqG8NPulYwJeU7UOOCkj22xXvDIBwfjkplPDRXFI0=; b=BCpqsw63RPGLGoSBpNyPl3JH62z+QjkoY64KEWfmxkho2ElyBGDvDen1B/AXBctwFDIiVdsgA7V/1 CFMkm1UE1sw9+EPl+DCc6/nq549rSX2h4QQAH2A6N8TXpQ5N+69iKnBmZdVTJg+nL2c5QowM11Ja0m q4Nb39GwT+EhvESU=
X-Halon-ID: b00f3555-a90a-11e3-915d-000c299c41b4
CC: 
Received: from STOEXCASHT02.sr.se (unknown [134.25.11.15]) by mail-1.sr.se (Halon Mail Gateway) with ESMTPS for <mmusic@ietf.org>; Tue, 11 Mar 2014 11:48:31 +0100 (CET)
Received: from STOEXMBX01.sr.se ([fe80::3ca4:10d1:e63f:5b7f]) by STOEXCASHT02.sr.se ([fe80::88c7:d3b3:5c76:acd7%13]) with mapi id 14.03.0174.001; Tue, 11 Mar 2014 11:49:08 +0100
From: Fredrik Bergholtz <fredrik.bergholtz@sverigesradio.se>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: RFC 4317, RFC 4566: SDP asymmetry and port numbers?
Thread-Index: Ac89F0YMwAxICnqGQ1OxOxqbT8X6cA==
Date: Tue, 11 Mar 2014 10:49:07 +0000
Message-ID: <6A5A8D4EF65AF1439301480747E29F434E320938@STOEXMBX01.sr.se>
Accept-Language: en-GB, sv-SE, en-US
Content-Language: sv-SE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_6A5A8D4EF65AF1439301480747E29F434E320938STOEXMBX01srse_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/G1QdeORK0SAa9gZleQAvgQhEU-s
Subject: [MMUSIC] RFC 4317, RFC 4566: SDP asymmetry and port numbers?
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: Tue, 11 Mar 2014 10:49:21 -0000

--_000_6A5A8D4EF65AF1439301480747E29F434E320938STOEXMBX01srse_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi, I have three questions about existing RFCs related to SDP.

The first is about RFC 4317 - Session Description Protocol (SDP) Offer/Answ=
er Examples. In sections 2.9 and 2.10 of version 01 of the draft there are =
examples of using a=3Dsendonly and a=3Drecvonly to define asymmetrical conn=
ections, i.e. different coding or bit rates in different directions. In the=
 next version of the draft, these examples are gone.

My question is: Why were they removed?

The second question is about RFC 4566 - SDP itself and might contain the an=
swer to the question above. In section 5.14, where media descriptions are d=
efined, I can read the following paragraph:

      The semantics of multiple "m=3D" lines using the same transport
      address are undefined.  This implies that, unlike limited past
      practice, there is no implicit grouping defined by such means and
      an explicit grouping framework (for example, [18]) should instead
      be used to express the intended semantics.

Does this also apply when the use of a=3Dsendonly and a=3Drecvonly make the=
 semantics clear?

If the above paragraph does disallow usage like the deleted examples of RFC=
 4317, how should something like that be signalled so that the intent is we=
ll defined and 100% compliant with existing standards?

Best Regards
Fredrik Bergholtz
Swedish Radio


--_000_6A5A8D4EF65AF1439301480747E29F434E320938STOEXMBX01srse_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.E-postmall17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"SV" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Hi, I have three questions abou=
t existing RFCs related to SDP.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">The first is about RFC 4317 - S=
ession Description Protocol (SDP) Offer/Answer Examples. In sections 2.9 an=
d 2.10 of version 01 of the draft there are examples of using a=3Dsendonly =
and a=3Drecvonly to define asymmetrical
 connections, i.e. different coding or bit rates in different directions. I=
n the next version of the draft, these examples are gone.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">My question is: Why were they r=
emoved?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">The second question is about RF=
C 4566 - SDP itself and might contain the answer to the question above. In =
section 5.14, where media descriptions are defined, I can read the followin=
g paragraph:<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
The semantics of multiple &quot;m=3D&quot; lines using the same transport<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
address are undefined.&nbsp; This implies that, unlike limited past<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
practice, there is no implicit grouping defined by such means and<o:p></o:p=
></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
an explicit grouping framework (for example, [18]) should instead<o:p></o:p=
></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
be used to express the intended semantics.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Does this also apply when the u=
se of a=3Dsendonly and a=3Drecvonly make the semantics clear?<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">If the above paragraph does dis=
allow usage like the deleted examples of RFC 4317, how should something lik=
e that be signalled so that the intent is well defined and 100% compliant w=
ith existing standards?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Best Regards<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Fredrik Bergholtz<o:p></o:p></s=
pan></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Swedish Radio<o:p></o:p></span>=
</p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
</div>
</body>
</html>

--_000_6A5A8D4EF65AF1439301480747E29F434E320938STOEXMBX01srse_--


From nobody Tue Mar 11 21:44:19 2014
Return-Path: <juberti@google.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 827711A08DB for <mmusic@ietfa.amsl.com>; Tue, 11 Mar 2014 21:44:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.925
X-Spam-Level: 
X-Spam-Status: No, score=-1.925 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001] autolearn=ham
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 DWeEWqLOZAPL for <mmusic@ietfa.amsl.com>; Tue, 11 Mar 2014 21:44:14 -0700 (PDT)
Received: from mail-ve0-x22e.google.com (mail-ve0-x22e.google.com [IPv6:2607:f8b0:400c:c01::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 5DD6D1A03AC for <mmusic@ietf.org>; Tue, 11 Mar 2014 21:44:14 -0700 (PDT)
Received: by mail-ve0-f174.google.com with SMTP id oz11so9632499veb.33 for <mmusic@ietf.org>; Tue, 11 Mar 2014 21:44:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=GuE1qhLIWcKzIs6tV5M7E8uo4fBAuFQXx30NFu/bOsI=; b=X6T/ZXIY6VCSFxGHpaUYfIsSZxQfRg5QkPMcBvHxQOydN11xElk4X28RJp/FKBPo3m YFxHcEt5s3pfOm0n9h1Bf2GKEeUGHBAnbiGnUpIvfMjw11EAarCthinuWVXRzKSkwHNy 3GT6ShPXDBFSLYKYzmqta5rMsiM0XzjzOcjRSvSxnN6/9Hm+K8G+FsmJxMzRIvl6usvB fzWZq3Rh679Ig1l9YHh+MFX5KPK+V+SYUjtE/PTpohWmZ1akVMsCNiRh2RYxGee52YcH R7Uvu9FMWFT/H3nbe0bk5hvJs1hxoxnZPba/PL6l+pNCAVapzHrmWzxJnf9/SZEfRU2i 2ENA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=GuE1qhLIWcKzIs6tV5M7E8uo4fBAuFQXx30NFu/bOsI=; b=gtnyc5uv/36WG65JTSQceuH276uSfsiMNTv7+Wn1aQcp1BbeqtlQmvWDKqRVaL8UOa Ujdw02UKisVWGlKfs0Q7mXsseBofH5Y//o+oJTELSfuzYNTHLNhsheQrUNDkBSPtpbrk pEQfJeqNDa8Wlyo6ZY6awZOsgFOXQq+xRNox8CPaDHHd8STK2WPpOrHaT3bnBkHbypes TBJ2uB4gKEp8DbU8xRvGQgMZLrkJa1/gV5p17AT6U+nlSSlololaSeyGLm77WdTExYSf XUpbAXLptCWv3S+YQijTElKNNtebvIitkkubHym7I+lbqyAAmYUS0nSfvtZXI6Y7oKui R17g==
X-Gm-Message-State: ALoCoQmISjkoDSGuJrqNey/+4Tlf5T1Ns1chQFMfiam72ugVAqkMpv25203ldcMQ84mpS5/bA5mY312ipy6S3o2Lnmqe6AF52R1ZOXVi6jNPYEpht59cBB4GZWosT8f+J++sneBcZmMOk2vEdYrT19QWfj9vbrCv9oY1tbH2Mpb0YGtzAezUvC8eHc98V3qVVMl8kn5Mno+I
X-Received: by 10.58.95.161 with SMTP id dl1mr13133157veb.21.1394599448302; Tue, 11 Mar 2014 21:44:08 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.26.43 with HTTP; Tue, 11 Mar 2014 21:43:35 -0700 (PDT)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D202004@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D202004@ESESSMB209.ericsson.se>
From: Justin Uberti <juberti@google.com>
Date: Tue, 11 Mar 2014 21:43:35 -0700
Message-ID: <CAOJ7v-085Zdv7gTKyrU_kCFBB8rdAytE7YjQFeFsUeqWKWoW+g@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary=089e013cb996b86ff304f4617c26
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/6MWNuU_SM96v0eOqYsclc4L-a9I
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] BUNDLE: Q9/Q13: Payload type value re-usage and associating RTP packets with m- line
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: Wed, 12 Mar 2014 04:44:17 -0000

--089e013cb996b86ff304f4617c26
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

As I understand it, the 'receiver-id' will not identify a BUNDLE group, but
rather a m=3D section or packet stream.


On Tue, Mar 11, 2014 at 1:56 AM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

>  Hi,
>
>
>
> Based on the discussion/decision in London, I=E2=80=99ve drafted the foll=
owing
> text regarding the usage of identical PT values, and the usage of the
> =E2=80=9Creceiver-id=E2=80=9D value in order to be able to associate rece=
ived RTP packets
> with the correct m- line (when the same payload type value is used inside
> multiple m- lines within the BUNDLE group).
>
>
>
> I may change some words later, in order to align with the rest of the
> document, but please take a look and see whether you are ok with the
> content, and whether you think it reflects the decisions in the meeting.
>
>  Regards,
>
>
>
> Christer
>
>
>
> ---------------------------------------
>
>
>
>
>
> X.X         RTP Considerations
>
>
>
> X.X.1      Multiple Usage Of Identical Payload Type (PT) Value Within A
> BUNDLE Group
>
>
>
> A BUNDLE group can contain multiple m- lines associated with RTP media. A=
s
> all RTP media associated with those m- lines belong to the same RTP sessi=
on
> [insert-reference], in order for a payload type value to used inside more
> than one m- line, all codecs associated with the payload type numbers MUS=
T
> share an identical codec configuration. This means that the codecs MUST
> share the same media type, encoding name, clock rate and any parameter th=
at
> can affect the codec configuration and packetizsation. [ID.draft-ietf-mmu=
sic-sdp-mux-attributes]
> lists SDP attribute values that must be identical for all codecs using th=
e
> same payload type value.
>
>
>
> X.X.2      Associating RTP Packets With Correct SDP Media Description
> Within A BUNDLE Group
>
>
>
> In general, there are multiple mechanisms that can be used by an endpoint
> in order to associate received RTP packets with the m- line associated wi=
th
> the RTP packets. Such mechanisms include using the local address:port on
> which the RTP packets are received, the payload type value carried inside
> the RTP packets, the SSRC values carried inside the RTP packets, and othe=
r
> m- line specific information carried inside the RTP packets.
>
>
>
> Within a BUNDLE group, as all RTP packets are transported using the same
> 5-tuple, the local address:port cannot be used to associate received RTP
> packets with the correct m- line.
>
>
>
> As described in section X.X.1, the same payload type value might be used
> inside RTP packets associated with multiple m- lines. In such cases, the
> payload type value cannot be used to associate received RTP packets with
> the correct m- line.
>
>
>
> Endpoints can inform each other which SSRC values they will use inside
> sent RTP packets by, in SDP Offers and Answers, assigning an SDP =E2=80=
=98ssrc=E2=80=99
> attribute [ref-to-be-added] to each m- line which contains a payload type
> value that is also used inside another m- line within the BUNDLE group. A=
s
> the SSRC values will be carried inside the RTP packets, the endpoints can
> then use that information to associate received RTP packets with the
> correct m- line. However, an offerer will not know which SSRC values the
> answerer will use until it has received the SDP Answer providing that
> information. Due to this, before the offerer has received the SDP Answer,
> it will not be able to associate received RTP packets with the correct m-
> line using the SSRC values.
>
>
>
> In order for endpoints to always be able to associate received RTP packet=
s
> with the correct m- line they MUST, in SDP Offers and Answers, assign an
> SDP =E2=80=9Creceiver-id=E2=80=9D attribute [receiver-id-reference-to-be-=
added] to each m-
> line which contains a payload type value that is also used inside another
> m- line within the BUNDLE group. If an endpoint accepts a BUNDLE group, i=
t
> MUST insert the =E2=80=9Creceiver-id=E2=80=9D value in the associated RTP=
 packets,
> associated with the BUNDLE group, sent towards the remote endpoint, as
> described in [receiver-id-reference-to-be-added]. If the endpoint cannot,
> or is not willing to, insert the =E2=80=9Creceiver-id=E2=80=9D value in s=
ent RTP packets,
> it MUST NOT accept the BUNDLE group.
>
>
>
> Editor=E2=80=99s note: [receiver-id-reference-to-be-added] will describe =
in how
> many RTP packets the receiver-id value will be sent.
>
>
>
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>
>

--089e013cb996b86ff304f4617c26
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">As I understand it, the &#39;receiver-id&#39; will not ide=
ntify a BUNDLE group, but rather a m=3D section or packet stream.</div><div=
 class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Tue, Mar 11, 2=
014 at 1:56 AM, Christer Holmberg <span dir=3D"ltr">&lt;<a href=3D"mailto:c=
hrister.holmberg@ericsson.com" target=3D"_blank">christer.holmberg@ericsson=
.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">





<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Hi,<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Based on the discussion/decisio=
n in London, I=E2=80=99ve drafted the following text regarding the usage of=
 identical PT values, and the usage of the =E2=80=9Creceiver-id=E2=80=9D va=
lue in order to be able to associate received RTP packets with
 the correct m- line (when the same payload type value is used inside multi=
ple m- lines within the BUNDLE group).<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">I may change some words later, =
in order to align with the rest of the document, but please take a look and=
 see whether you are ok with the content, and whether you think it reflects=
 the decisions in the meeting.<u></u><u></u></span></p>


<p class=3D"MsoNormal"><span lang=3D"EN-GB"><u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Regards,<u></u><u></u></span></=
p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Christer<u></u><u></u></span></=
p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">-------------------------------=
--------<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">X.X=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 RTP Considerations<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">X.X.1=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 Multiple Usage Of Identical Payload Type (PT) Value Within A BUNDLE =
Group<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">A BUNDLE group can contain mult=
iple m- lines associated with RTP media. As all RTP media associated with t=
hose m- lines belong to the same RTP session [insert-reference], in order f=
or a payload type value to used inside
 more than one m- line, all codecs associated with the payload type numbers=
 MUST share an identical codec configuration. This means that the codecs MU=
ST share the same media type, encoding name, clock rate and any parameter t=
hat can affect the codec configuration
 and packetizsation. [ID.</span>draft-ietf-mmusic-sdp-mux-attributes] lists=
 SDP attribute values that must be identical for all codecs using the same =
payload type value.<span lang=3D"EN-GB"><u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">X.X.2=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 Associating RTP Packets With Correct SDP Media Description Within A =
BUNDLE Group<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">In general, there are multiple =
mechanisms that can be used by an endpoint in order to associate received R=
TP packets with the m- line associated with the RTP packets. Such mechanism=
s include using the local address:port
 on which the RTP packets are received, the payload type value carried insi=
de the RTP packets, the SSRC values carried inside the RTP packets, and oth=
er m- line specific information carried inside the RTP packets.<u></u><u></=
u></span></p>


<p class=3D"MsoNormal"><span lang=3D"EN-GB"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Within a BUNDLE group, as all R=
TP packets are transported using the same 5-tuple, the local address:port c=
annot be used to associate received RTP packets with the correct m- line.<u=
></u><u></u></span></p>


<p class=3D"MsoNormal"><span lang=3D"EN-GB"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">As described in section X.X.1, =
the same payload type value might be used inside RTP packets associated wit=
h multiple m- lines. In such cases, the payload type value cannot be used t=
o associate received RTP packets with
 the correct m- line.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Endpoints can inform each other=
 which SSRC values they will use inside sent RTP packets by, in SDP Offers =
and Answers, assigning an SDP =E2=80=98ssrc=E2=80=99 attribute [ref-to-be-a=
dded] to each m- line which contains a payload type
 value that is also used inside another m- line within the BUNDLE group. As=
 the SSRC values will be carried inside the RTP packets, the endpoints can =
then use that information to associate received RTP packets with the correc=
t m- line. However, an offerer will
 not know which SSRC values the answerer will use until it has received the=
 SDP Answer providing that information. Due to this, before the offerer has=
 received the SDP Answer, it will not be able to associate received RTP pac=
kets with the correct m- line using
 the SSRC values.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">In order for endpoints to alway=
s be able to associate received RTP packets with the correct m- line they M=
UST, in SDP Offers and Answers, assign an SDP =E2=80=9Creceiver-id=E2=80=9D=
 attribute [receiver-id-reference-to-be-added] to each
 m- line which contains a payload type value that is also used inside anoth=
er m- line within the BUNDLE group. If an endpoint accepts a BUNDLE group, =
it MUST insert the =E2=80=9Creceiver-id=E2=80=9D value in the associated RT=
P packets, associated with the BUNDLE group, sent
 towards the remote endpoint, as described in [receiver-id-reference-to-be-=
added]. If the endpoint cannot, or is not willing to, insert the =E2=80=9Cr=
eceiver-id=E2=80=9D value in sent RTP packets, it MUST NOT accept the BUNDL=
E group.<u></u><u></u></span></p>


<p class=3D"MsoNormal"><span lang=3D"EN-GB"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Editor=E2=80=99s note: [receive=
r-id-reference-to-be-added] will describe in how many RTP packets the recei=
ver-id value will be sent.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><u></u>=C2=A0<u></u></span></p>
</div>
</div>

<br>_______________________________________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/mmusic</a><br>
<br></blockquote></div><br></div>

--089e013cb996b86ff304f4617c26--


From nobody Tue Mar 11 21:46:05 2014
Return-Path: <juberti@google.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 1F9661A08D9 for <mmusic@ietfa.amsl.com>; Tue, 11 Mar 2014 21:46:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.944
X-Spam-Level: 
X-Spam-Status: No, score=-0.944 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_FONT_FACE_BAD=0.981, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.547, 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 YN_66jkX2l19 for <mmusic@ietfa.amsl.com>; Tue, 11 Mar 2014 21:46:02 -0700 (PDT)
Received: from mail-ve0-x231.google.com (mail-ve0-x231.google.com [IPv6:2607:f8b0:400c:c01::231]) by ietfa.amsl.com (Postfix) with ESMTP id 32F951A03AC for <mmusic@ietf.org>; Tue, 11 Mar 2014 21:46:02 -0700 (PDT)
Received: by mail-ve0-f177.google.com with SMTP id sa20so9406099veb.8 for <mmusic@ietf.org>; Tue, 11 Mar 2014 21:45:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=ZF3GJrLPcdzZllO3dZdrMnWvta8hFUE/5XLnqnINwJ8=; b=F5O8QlM58QJAY5s8Eue2P/vyYqxAhhTJJuYenePNHomsgtvXBSjV5nnrcXrr6VeakO JBqQrJDPncbKJJc5lUqplxT4SpE3dynGq8Y2YKxVpHe26rvSVGGwSC8H0IJU1iTAi4tN LoGWShsoNojbN1LG5poYj90dWb9xkcuIXoi1j/OeYJJnW8oUkMU18yR7iklzeGvAtaPZ KzBPGmiz9vf9t/XTLtu+Z0i2xQClKUBatWnJMKQ+TJwYNn7ODiQbRD8PbmwIznr4i+Sv hkIf59lxp+6z9iIMSRXLT7YjM1UdpZXN5FkxC1nlUmHzhDX4yDR+iJFKh615q/oEaJpG HDgA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=ZF3GJrLPcdzZllO3dZdrMnWvta8hFUE/5XLnqnINwJ8=; b=UlyCd/78r34K2mxijoHYg0kecTyPa4DA2nDFz8zhvn/IQK5eBoceM82iF5STQ2760R FthjPH2e8oXJSCpgLBT9SUZYvxyZXBneoz9+aTI7Yh3oDQDZoE0zrB+y7AYhX/TAd/QJ OTqdcDj/gxKIcKZ9clp7hqi9ru6hbnmolpz2Yh0tixWWMZ+2Ga519N2nLgoWGWbe+zkz 8g/dfpDXPEr1OTLzX9C7WgjSqg1XpMglz/IekWj7JQBY+5y8+6A5rnGmP1ec5pK1E4rt GWsbZno6aewq8kyTDDX2+6a3e0I9UXvx81V4eGmUVbIqpTVhzFi8f+mamARuoiS/S/Ij pNlA==
X-Gm-Message-State: ALoCoQkR31ZmwG7ppdBV0T5OxpX1jRVav+8nXge38MqAoaGZxX2Hw3qn8juV08+mgtz3NC2eGDFjTadJ12zCtooRS7N2aG7jFcH2cVblhlqVuNgKET10tIf9Co1K7LFcyMBc5WfsL7OSb11gYbflFLEWXttFnppv0i564tNG74d3F4M8VpeknfaIM6EFmtei+l4F7EaDiCUA
X-Received: by 10.221.55.133 with SMTP id vy5mr30597557vcb.17.1394599556062; Tue, 11 Mar 2014 21:45:56 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.26.43 with HTTP; Tue, 11 Mar 2014 21:45:35 -0700 (PDT)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D2009EF@ESESSMB209.ericsson.se>
References: <021001cf39f3$04e8de40$0eba9ac0$@gmail.com> <7594FB04B1934943A5C02806D1A2204B1D1D8C3D@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B1D2009EF@ESESSMB209.ericsson.se>
From: Justin Uberti <juberti@google.com>
Date: Tue, 11 Mar 2014 21:45:35 -0700
Message-ID: <CAOJ7v-1Oe4TBMXWZR8Z_pO6xQmT4PcE9QoLzBpPqKbaQ6y5nFA@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary=001a113376fe24b91804f461834f
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/6QBsnmM8J-O6yPXkWcRNbtDsaJU
Cc: mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] Bundle: Q13 receiver-Id
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: Wed, 12 Mar 2014 04:46:04 -0000

--001a113376fe24b91804f461834f
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

application-token is currently the only mechanism that has been proposed. I
am OK with using it for BUNDLE.


On Tue, Mar 11, 2014 at 12:56 AM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

>
> Hi,
>
> If people are ok with using the mechanism in Roni's draft, please indicat=
e
> so.
>
> Please also indicate if you are NOT ok to use it, or you think there is
> another mechanism we should at least verify.
>
> Please also indicate if you don't care what mechanism we use - just to
> make sure we get community input :)
>
> Note that if the "receiver-id" will require a new draft, the publication
> of BUNDLE will be dependent of that draft, so I think we should make a
> decision which way to go asap.
>
> Regards,
>
> Christer
>
>
>  ------------------------------
> *From:* mmusic [mmusic-bounces@ietf.org] on behalf of Christer Holmberg [
> christer.holmberg@ericsson.com]
> *Sent:* Friday, 07 March 2014 3:33 PM
> *To:* Roni Even; 'mmusic'
> *Subject:* Re: [MMUSIC] Bundle: Q13 receiver-Id
>
>   Thank you for the input, Roni!
>
>  I assume that, for the purpose of associating media with an m- line, an
> entity would not need to support the OTHER attributes in the draft, right=
?
>
>  Regards,
>
>  Christer
>
>  Sent from Windows Mail
>
>   *From:* Roni Even <ron.even.tlv@gmail.com>
> *Sent:* =E2=80=8EFriday=E2=80=8E, =E2=80=8E7=E2=80=8E =E2=80=8EMarch=E2=
=80=8E =E2=80=8E2014 =E2=80=8E12=E2=80=8E:=E2=80=8E50
> *To:* 'mmusic' <mmusic@ietf.org>
>
>   Hi,
>
> In draft-even-mmusic-application-token-02<http://tools.ietf.org/html/draf=
t-even-mmusic-application-token-02>there is a recv-appId token that can be =
used as the receiver-Id. Based on
> the discussion in the meeting it seems that the recv-appId  usage  will b=
e
> needed for the case when the offerer receives media before the SDP answer
> and can use the recv-appId to identify the correlation to an m-line / RTP
> stream   in the SDP.  This will also works for the same PT number.
>
>
>
> Roni
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>
>

--001a113376fe24b91804f461834f
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">application-token is currently the only mechanism that has=
 been proposed. I am OK with using it for BUNDLE.</div><div class=3D"gmail_=
extra"><br><br><div class=3D"gmail_quote">On Tue, Mar 11, 2014 at 12:56 AM,=
 Christer Holmberg <span dir=3D"ltr">&lt;<a href=3D"mailto:christer.holmber=
g@ericsson.com" target=3D"_blank">christer.holmberg@ericsson.com</a>&gt;</s=
pan> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">




<div dir=3D"ltr">
<div style=3D"direction:ltr;font-size:10pt;font-family:Tahoma"><br>
Hi,<br>
<br>
If people are ok with using the mechanism in Roni&#39;s draft, please indic=
ate so.<br>
<br>
Please also indicate if you are NOT ok to use it, or you think there is ano=
ther mechanism we should at least verify.<br>
<br>
Please also indicate if you don&#39;t care what mechanism we use - just to =
make sure we get community input :)<br>
<br>
Note that if the &quot;receiver-id&quot; will require a new draft, the publ=
ication of BUNDLE will be dependent of that draft, so I think we should mak=
e a decision which way to go asap.<br>
<br>
Regards,<br>
<br>
Christer<br>
<br>
<br>
<div style=3D"font-size:16px;font-family:Times New Roman">
<hr>
<div style=3D"direction:ltr"><font color=3D"#000000" face=3D"Tahoma"><b>Fro=
m:</b> mmusic [<a href=3D"mailto:mmusic-bounces@ietf.org" target=3D"_blank"=
>mmusic-bounces@ietf.org</a>] on behalf of Christer Holmberg [<a href=3D"ma=
ilto:christer.holmberg@ericsson.com" target=3D"_blank">christer.holmberg@er=
icsson.com</a>]<br>


<b>Sent:</b> Friday, 07 March 2014 3:33 PM<br>
<b>To:</b> Roni Even; &#39;mmusic&#39;<br>
<b>Subject:</b> Re: [MMUSIC] Bundle: Q13 receiver-Id<br>
</font><br>
</div><div><div class=3D"h5">
<div></div>
<div>
<div dir=3D"ltr" style=3D"font-family:&#39;Calibri&#39;,&#39;Segoe UI&#39;,=
&#39;Meiryo&#39;,&#39;Microsoft YaHei UI&#39;,&#39;Microsoft JhengHei UI&#3=
9;,&#39;Malgun Gothic&#39;,&#39;sans-serif&#39;;font-size:12pt">
<div>Thank you for the input, Roni!</div>
<div><br>
</div>
<div>I assume that, for the purpose of associating media with an m- line, a=
n entity would not need to support the OTHER attributes in the draft, right=
?</div>
<div><br>
</div>
<div>Regards,</div>
<div><br>
</div>
<div>Christer<br>
</div>
<div>
<div><br>
</div>
<div>Sent from Windows Mail</div>
<div><br>
</div>
</div>
<div style=3D"padding-top:5px;border-top-color:rgb(229,229,229);border-top-=
width:1px;border-top-style:solid">
<div><font style=3D"line-height:15pt;letter-spacing:0.02em;font-family:&quo=
t;Calibri&quot;,&quot;Segoe UI&quot;,&quot;Meiryo&quot;,&quot;Microsoft YaH=
ei UI&quot;,&quot;Microsoft JhengHei UI&quot;,&quot;Malgun Gothic&quot;,&qu=
ot;sans-serif&quot;;font-size:12pt" face=3D" &#39;Calibri&#39;, &#39;Segoe =
UI&#39;, &#39;Meiryo&#39;, &#39;Microsoft YaHei UI&#39;, &#39;Microsoft Jhe=
ngHei UI&#39;, &#39;Malgun Gothic&#39;, &#39;sans-serif&#39;"><b>From:</b>=
=C2=A0<a href=3D"mailto:ron.even.tlv@gmail.com" target=3D"_blank">Roni
 Even</a><br>
<b>Sent:</b>=C2=A0=E2=80=8EFriday=E2=80=8E, =E2=80=8E7=E2=80=8E =E2=80=8EMa=
rch=E2=80=8E =E2=80=8E2014 =E2=80=8E12=E2=80=8E:=E2=80=8E50<br>
<b>To:</b>=C2=A0<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">&#39;m=
music&#39;</a></font></div>
</div>
<div><br>
</div>
<div dir=3D"">
<div>
<p class=3D"MsoNormal">Hi,</p>
<p class=3D"MsoNormal">In <a href=3D"http://tools.ietf.org/html/draft-even-=
mmusic-application-token-02" target=3D"_blank">
draft-even-mmusic-application-token-02</a> there is a recv-appId token that=
 can be used as the receiver-Id. Based on the discussion in the meeting it =
seems that the recv-appId =C2=A0usage =C2=A0will be needed for the case whe=
n the offerer receives media before the SDP
 answer and can use the recv-appId to identify the correlation to an m-line=
 / RTP stream =C2=A0=C2=A0in the SDP.=C2=A0 This will also works for the sa=
me PT number.</p>
<p class=3D"MsoNormal">=C2=A0</p>
<p class=3D"MsoNormal">Roni </p>
</div>
</div>
</div>
</div>
</div></div></div>
</div>
</div>

<br>_______________________________________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/mmusic</a><br>
<br></blockquote></div><br></div>

--001a113376fe24b91804f461834f--


From nobody Wed Mar 12 00:55:19 2014
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 7F3FB1A0914 for <mmusic@ietfa.amsl.com>; Wed, 12 Mar 2014 00:55:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham
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 Vg1cqRTVkTBQ for <mmusic@ietfa.amsl.com>; Wed, 12 Mar 2014 00:55:15 -0700 (PDT)
Received: from sesbmg20.ericsson.net (sesbmg20.ericsson.net [193.180.251.56]) by ietfa.amsl.com (Postfix) with ESMTP id B37771A090F for <mmusic@ietf.org>; Wed, 12 Mar 2014 00:55:14 -0700 (PDT)
X-AuditID: c1b4fb38-b7f418e000001099-f2-532012dce4e5
Received: from ESESSHC007.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg20.ericsson.net (Symantec Mail Security) with SMTP id 44.CF.04249.CD210235; Wed, 12 Mar 2014 08:55:08 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.216]) by ESESSHC007.ericsson.se ([153.88.183.39]) with mapi id 14.02.0387.000; Wed, 12 Mar 2014 08:55:07 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Justin Uberti <juberti@google.com>
Thread-Topic: [MMUSIC] BUNDLE: Q9/Q13: Payload type value re-usage and associating RTP packets with m- line
Thread-Index: Ac89B6OYHyKFgXivSIaXJxW+k4A5DQAnZs6AAAi36ZA=
Date: Wed, 12 Mar 2014 07:55:06 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D20A557@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D202004@ESESSMB209.ericsson.se> <CAOJ7v-085Zdv7gTKyrU_kCFBB8rdAytE7YjQFeFsUeqWKWoW+g@mail.gmail.com>
In-Reply-To: <CAOJ7v-085Zdv7gTKyrU_kCFBB8rdAytE7YjQFeFsUeqWKWoW+g@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.17]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrOLMWRmVeSWpSXmKPExsUyM+Jvje4dIYVgg4cdghZbpwpZTF3+mMWB yWPBplKPJUt+MgUwRXHZpKTmZJalFunbJXBl3Lu1gLHgln7Fsvdn2RsY9+h1MXJwSAiYSFw7 nt7FyAlkiklcuLeerYuRi0NI4AijxOznB5ggnCWMEl0f/jGBNLAJWEh0/9MGaRARUJN4OGsX K0iYWUBd4uriIJCwsECOxJMpB9ghSnKBqjeyQthWEvu7Z7OB2CwCqhKdHycygti8Ar4Sm5r/ MEOsmsIocWwXRIJTIFDi97RLYDYj0HHfT61hArGZBcQlbj2ZzwRxtIDEkj3nmSFsUYmXj/+x QvylKLG8Xw7iNE2J9bv0IToVJaZ0P2SHWCsocXLmE5YJjGKzkAydhdAxC0nHLCQdCxhZVjFy FKcWJ+WmGxlsYgRGxsEtvy12MF7+a3OIUZqDRUmc9+Nb5yAhgfTEktTs1NSC1KL4otKc1OJD jEwcnFINjLYHztvmLD1oIHzUR+jAG9bXl87d2Lzvenu62QJJwzmCV6yrS82bzhkfL5itmFXv w/o1WjF957Uvh3SnxxmEbDhTlSRxISsoucT1qdJzO07j3qObTmm8iEwNiAyb5fx5XtvVo7Yr i9Y+nx6TtuNT0T0rTfnp/Wprm34ErTI1bH6S0t7190uzkRJLcUaioRZzUXEiAPuz+65aAgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/z4JfkjVGBHJmNVhMd2y0tvSF9nk
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] BUNDLE: Q9/Q13: Payload type value re-usage and associating RTP packets with m- line
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: Wed, 12 Mar 2014 07:55:17 -0000

SGkgSnVzdGluLA0KDQo+QXMgSSB1bmRlcnN0YW5kIGl0LCB0aGUgJ3JlY2VpdmVyLWlkJyB3aWxs
IG5vdCBpZGVudGlmeSBhIEJVTkRMRSBncm91cCwgYnV0IHJhdGhlciBhIG09IHNlY3Rpb24gb3Ig
cGFja2V0IHN0cmVhbS4NCg0KQ29ycmVjdC4gDQoNCkRvIHlvdSB0aGluayB0aGUgdGV4dCBpbmRp
Y2F0ZXMgb3RoZXJ3aXNlPw0KDQpSZWdhcmRzLA0KDQpDaHJpc3Rlcg0KDQoNCg0KT24gVHVlLCBN
YXIgMTEsIDIwMTQgYXQgMTo1NiBBTSwgQ2hyaXN0ZXIgSG9sbWJlcmcgPGNocmlzdGVyLmhvbG1i
ZXJnQGVyaWNzc29uLmNvbT4gd3JvdGU6DQpIaSwNCsKgDQpCYXNlZCBvbiB0aGUgZGlzY3Vzc2lv
bi9kZWNpc2lvbiBpbiBMb25kb24sIEnigJl2ZSBkcmFmdGVkIHRoZSBmb2xsb3dpbmcgdGV4dCBy
ZWdhcmRpbmcgdGhlIHVzYWdlIG9mIGlkZW50aWNhbCBQVCB2YWx1ZXMsIGFuZCB0aGUgdXNhZ2Ug
b2YgdGhlIOKAnHJlY2VpdmVyLWlk4oCdIHZhbHVlIGluIG9yZGVyIHRvIGJlIGFibGUgdG8gYXNz
b2NpYXRlIHJlY2VpdmVkIFJUUCBwYWNrZXRzIHdpdGggdGhlIGNvcnJlY3QgbS0gbGluZSAod2hl
biB0aGUgc2FtZSBwYXlsb2FkIHR5cGUgdmFsdWUgaXMgdXNlZCBpbnNpZGUgbXVsdGlwbGUgbS0g
bGluZXMgd2l0aGluIHRoZSBCVU5ETEUgZ3JvdXApLg0KwqANCkkgbWF5IGNoYW5nZSBzb21lIHdv
cmRzIGxhdGVyLCBpbiBvcmRlciB0byBhbGlnbiB3aXRoIHRoZSByZXN0IG9mIHRoZSBkb2N1bWVu
dCwgYnV0IHBsZWFzZSB0YWtlIGEgbG9vayBhbmQgc2VlIHdoZXRoZXIgeW91IGFyZSBvayB3aXRo
IHRoZSBjb250ZW50LCBhbmQgd2hldGhlciB5b3UgdGhpbmsgaXQgcmVmbGVjdHMgdGhlIGRlY2lz
aW9ucyBpbiB0aGUgbWVldGluZy4NClJlZ2FyZHMsDQrCoA0KQ2hyaXN0ZXINCsKgDQotLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCsKgDQrCoA0KWC5YwqDCoMKgwqDCoMKg
wqDCoCBSVFAgQ29uc2lkZXJhdGlvbnMNCsKgDQpYLlguMcKgwqDCoMKgwqAgTXVsdGlwbGUgVXNh
Z2UgT2YgSWRlbnRpY2FsIFBheWxvYWQgVHlwZSAoUFQpIFZhbHVlIFdpdGhpbiBBIEJVTkRMRSBH
cm91cA0KwqANCkEgQlVORExFIGdyb3VwIGNhbiBjb250YWluIG11bHRpcGxlIG0tIGxpbmVzIGFz
c29jaWF0ZWQgd2l0aCBSVFAgbWVkaWEuIEFzIGFsbCBSVFAgbWVkaWEgYXNzb2NpYXRlZCB3aXRo
IHRob3NlIG0tIGxpbmVzIGJlbG9uZyB0byB0aGUgc2FtZSBSVFAgc2Vzc2lvbiBbaW5zZXJ0LXJl
ZmVyZW5jZV0sIGluIG9yZGVyIGZvciBhIHBheWxvYWQgdHlwZSB2YWx1ZSB0byB1c2VkIGluc2lk
ZSBtb3JlIHRoYW4gb25lIG0tIGxpbmUsIGFsbCBjb2RlY3MgYXNzb2NpYXRlZCB3aXRoIHRoZSBw
YXlsb2FkIHR5cGUgbnVtYmVycyBNVVNUIHNoYXJlIGFuIGlkZW50aWNhbCBjb2RlYyBjb25maWd1
cmF0aW9uLiBUaGlzIG1lYW5zIHRoYXQgdGhlIGNvZGVjcyBNVVNUIHNoYXJlIHRoZSBzYW1lIG1l
ZGlhIHR5cGUsIGVuY29kaW5nIG5hbWUsIGNsb2NrIHJhdGUgYW5kIGFueSBwYXJhbWV0ZXIgdGhh
dCBjYW4gYWZmZWN0IHRoZSBjb2RlYyBjb25maWd1cmF0aW9uIGFuZCBwYWNrZXRpenNhdGlvbi4g
W0lELmRyYWZ0LWlldGYtbW11c2ljLXNkcC1tdXgtYXR0cmlidXRlc10gbGlzdHMgU0RQIGF0dHJp
YnV0ZSB2YWx1ZXMgdGhhdCBtdXN0IGJlIGlkZW50aWNhbCBmb3IgYWxsIGNvZGVjcyB1c2luZyB0
aGUgc2FtZSBwYXlsb2FkIHR5cGUgdmFsdWUuDQrCoA0KWC5YLjLCoMKgwqDCoMKgIEFzc29jaWF0
aW5nIFJUUCBQYWNrZXRzIFdpdGggQ29ycmVjdCBTRFAgTWVkaWEgRGVzY3JpcHRpb24gV2l0aGlu
IEEgQlVORExFIEdyb3VwDQrCoA0KSW4gZ2VuZXJhbCwgdGhlcmUgYXJlIG11bHRpcGxlIG1lY2hh
bmlzbXMgdGhhdCBjYW4gYmUgdXNlZCBieSBhbiBlbmRwb2ludCBpbiBvcmRlciB0byBhc3NvY2lh
dGUgcmVjZWl2ZWQgUlRQIHBhY2tldHMgd2l0aCB0aGUgbS0gbGluZSBhc3NvY2lhdGVkIHdpdGgg
dGhlIFJUUCBwYWNrZXRzLiBTdWNoIG1lY2hhbmlzbXMgaW5jbHVkZSB1c2luZyB0aGUgbG9jYWwg
YWRkcmVzczpwb3J0IG9uIHdoaWNoIHRoZSBSVFAgcGFja2V0cyBhcmUgcmVjZWl2ZWQsIHRoZSBw
YXlsb2FkIHR5cGUgdmFsdWUgY2FycmllZCBpbnNpZGUgdGhlIFJUUCBwYWNrZXRzLCB0aGUgU1NS
QyB2YWx1ZXMgY2FycmllZCBpbnNpZGUgdGhlIFJUUCBwYWNrZXRzLCBhbmQgb3RoZXIgbS0gbGlu
ZSBzcGVjaWZpYyBpbmZvcm1hdGlvbiBjYXJyaWVkIGluc2lkZSB0aGUgUlRQIHBhY2tldHMuDQrC
oA0KV2l0aGluIGEgQlVORExFIGdyb3VwLCBhcyBhbGwgUlRQIHBhY2tldHMgYXJlIHRyYW5zcG9y
dGVkIHVzaW5nIHRoZSBzYW1lIDUtdHVwbGUsIHRoZSBsb2NhbCBhZGRyZXNzOnBvcnQgY2Fubm90
IGJlIHVzZWQgdG8gYXNzb2NpYXRlIHJlY2VpdmVkIFJUUCBwYWNrZXRzIHdpdGggdGhlIGNvcnJl
Y3QgbS0gbGluZS4NCsKgDQpBcyBkZXNjcmliZWQgaW4gc2VjdGlvbiBYLlguMSwgdGhlIHNhbWUg
cGF5bG9hZCB0eXBlIHZhbHVlIG1pZ2h0IGJlIHVzZWQgaW5zaWRlIFJUUCBwYWNrZXRzIGFzc29j
aWF0ZWQgd2l0aCBtdWx0aXBsZSBtLSBsaW5lcy4gSW4gc3VjaCBjYXNlcywgdGhlIHBheWxvYWQg
dHlwZSB2YWx1ZSBjYW5ub3QgYmUgdXNlZCB0byBhc3NvY2lhdGUgcmVjZWl2ZWQgUlRQIHBhY2tl
dHMgd2l0aCB0aGUgY29ycmVjdCBtLSBsaW5lLg0KwqANCkVuZHBvaW50cyBjYW4gaW5mb3JtIGVh
Y2ggb3RoZXIgd2hpY2ggU1NSQyB2YWx1ZXMgdGhleSB3aWxsIHVzZSBpbnNpZGUgc2VudCBSVFAg
cGFja2V0cyBieSwgaW4gU0RQIE9mZmVycyBhbmQgQW5zd2VycywgYXNzaWduaW5nIGFuIFNEUCDi
gJhzc3Jj4oCZIGF0dHJpYnV0ZSBbcmVmLXRvLWJlLWFkZGVkXSB0byBlYWNoIG0tIGxpbmUgd2hp
Y2ggY29udGFpbnMgYSBwYXlsb2FkIHR5cGUgdmFsdWUgdGhhdCBpcyBhbHNvIHVzZWQgaW5zaWRl
IGFub3RoZXIgbS0gbGluZSB3aXRoaW4gdGhlIEJVTkRMRSBncm91cC4gQXMgdGhlIFNTUkMgdmFs
dWVzIHdpbGwgYmUgY2FycmllZCBpbnNpZGUgdGhlIFJUUCBwYWNrZXRzLCB0aGUgZW5kcG9pbnRz
IGNhbiB0aGVuIHVzZSB0aGF0IGluZm9ybWF0aW9uIHRvIGFzc29jaWF0ZSByZWNlaXZlZCBSVFAg
cGFja2V0cyB3aXRoIHRoZSBjb3JyZWN0IG0tIGxpbmUuIEhvd2V2ZXIsIGFuIG9mZmVyZXIgd2ls
bCBub3Qga25vdyB3aGljaCBTU1JDIHZhbHVlcyB0aGUgYW5zd2VyZXIgd2lsbCB1c2UgdW50aWwg
aXQgaGFzIHJlY2VpdmVkIHRoZSBTRFAgQW5zd2VyIHByb3ZpZGluZyB0aGF0IGluZm9ybWF0aW9u
LiBEdWUgdG8gdGhpcywgYmVmb3JlIHRoZSBvZmZlcmVyIGhhcyByZWNlaXZlZCB0aGUgU0RQIEFu
c3dlciwgaXQgd2lsbCBub3QgYmUgYWJsZSB0byBhc3NvY2lhdGUgcmVjZWl2ZWQgUlRQIHBhY2tl
dHMgd2l0aCB0aGUgY29ycmVjdCBtLSBsaW5lIHVzaW5nIHRoZSBTU1JDIHZhbHVlcy4NCsKgDQpJ
biBvcmRlciBmb3IgZW5kcG9pbnRzIHRvIGFsd2F5cyBiZSBhYmxlIHRvIGFzc29jaWF0ZSByZWNl
aXZlZCBSVFAgcGFja2V0cyB3aXRoIHRoZSBjb3JyZWN0IG0tIGxpbmUgdGhleSBNVVNULCBpbiBT
RFAgT2ZmZXJzIGFuZCBBbnN3ZXJzLCBhc3NpZ24gYW4gU0RQIOKAnHJlY2VpdmVyLWlk4oCdIGF0
dHJpYnV0ZSBbcmVjZWl2ZXItaWQtcmVmZXJlbmNlLXRvLWJlLWFkZGVkXSB0byBlYWNoIG0tIGxp
bmUgd2hpY2ggY29udGFpbnMgYSBwYXlsb2FkIHR5cGUgdmFsdWUgdGhhdCBpcyBhbHNvIHVzZWQg
aW5zaWRlIGFub3RoZXIgbS0gbGluZSB3aXRoaW4gdGhlIEJVTkRMRSBncm91cC4gSWYgYW4gZW5k
cG9pbnQgYWNjZXB0cyBhIEJVTkRMRSBncm91cCwgaXQgTVVTVCBpbnNlcnQgdGhlIOKAnHJlY2Vp
dmVyLWlk4oCdIHZhbHVlIGluIHRoZSBhc3NvY2lhdGVkIFJUUCBwYWNrZXRzLCBhc3NvY2lhdGVk
IHdpdGggdGhlIEJVTkRMRSBncm91cCwgc2VudCB0b3dhcmRzIHRoZSByZW1vdGUgZW5kcG9pbnQs
IGFzIGRlc2NyaWJlZCBpbiBbcmVjZWl2ZXItaWQtcmVmZXJlbmNlLXRvLWJlLWFkZGVkXS4gSWYg
dGhlIGVuZHBvaW50IGNhbm5vdCwgb3IgaXMgbm90IHdpbGxpbmcgdG8sIGluc2VydCB0aGUg4oCc
cmVjZWl2ZXItaWTigJ0gdmFsdWUgaW4gc2VudCBSVFAgcGFja2V0cywgaXQgTVVTVCBOT1QgYWNj
ZXB0IHRoZSBCVU5ETEUgZ3JvdXAuDQrCoA0KRWRpdG9y4oCZcyBub3RlOiBbcmVjZWl2ZXItaWQt
cmVmZXJlbmNlLXRvLWJlLWFkZGVkXSB3aWxsIGRlc2NyaWJlIGluIGhvdyBtYW55IFJUUCBwYWNr
ZXRzIHRoZSByZWNlaXZlci1pZCB2YWx1ZSB3aWxsIGJlIHNlbnQuDQrCoA0KwqANCg0KX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCm1tdXNpYyBtYWlsaW5n
IGxpc3QNCm1tdXNpY0BpZXRmLm9yZw0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0
aW5mby9tbXVzaWMNCg0K


From nobody Wed Mar 12 06:18:43 2014
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 4CEA01A0993 for <mmusic@ietfa.amsl.com>; Wed, 12 Mar 2014 06:18:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.851
X-Spam-Level: 
X-Spam-Status: No, score=-3.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 MGyzs2up2icD for <mmusic@ietfa.amsl.com>; Wed, 12 Mar 2014 06:18:38 -0700 (PDT)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id C87271A0960 for <mmusic@ietf.org>; Wed, 12 Mar 2014 06:18:37 -0700 (PDT)
X-AuditID: c1b4fb25-b7f038e000005d01-3e-53205ea6f0e6
Received: from ESESSHC020.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id FE.39.23809.6AE50235; Wed, 12 Mar 2014 14:18:31 +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; Wed, 12 Mar 2014 14:18:30 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: BUNDLE: Q12: Scope of non-RTP media de-mux procedures in BUNDLE - Suggested text
Thread-Index: Ac899XSO6qIzXSXmQrWOUHoH8F5ihA==
Date: Wed, 12 Mar 2014 13:18:29 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D20D51B@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.17]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprDLMWRmVeSWpSXmKPExsUyM+Jvje7yOIVgg/2P+CymLn/M4sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujP39N1kL3vFWXN66lKWBcTt3FyMnh4SAicSquQdZIGwxiQv3 1rN1MXJxCAkcYpS4ePEElLOEUeLewhusXYwcHGwCFhLd/7RBGkQE1CW+7u1hBrGFBaIl/p+a wAhSIiKQIHG80RuiRE9i3oHN7CA2i4CqRNerB2A2r4CvxLrNc9hAbEagvd9PrWECsZkFxCVu PZnPBHGPgMSSPeeZIWxRiZeP/4FdICGgKLG8Xw6iXEdiwe5PbBC2tsSyha+ZIcYLSpyc+YRl AqPwLCRTZyFpmYWkZRaSlgWMLKsY2XMTM3PSy402MQJD+OCW36o7GO+cEznEKM3BoiTO++Gt c5CQQHpiSWp2ampBalF8UWlOavEhRiYOTqkGRq9SaTPTBOGIj1ZtX+/vUzpqbmMmc+NbxaQ5 3hsfbp2zmIv3t/2WusKu1c5/1pyfZGc0R/PSo/3v/M/F3WR6u+/z3f/LLm+S3ZV9i/FT4bcq 060XNjnIL5qpueB34UadIglhrokvU85WdJd86RWUuLnr1MFamx71fuad0xrY13zvmMC3KNhC e40SS3FGoqEWc1FxIgCon7HaLwIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/F57sMTSxnmNeVfEBwmpehvSaVjM
Subject: [MMUSIC] BUNDLE: Q12: Scope of non-RTP media de-mux procedures in BUNDLE - Suggested text
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: Wed, 12 Mar 2014 13:18:40 -0000

Hi,

Based on the discussion/agreement in London, I've drafted the=20
following text regarding protocol identification.

Regards,

Christer

-------------------------------

Y. Protocol Identification

Y.1. General

If m- lines within a BUNDLE group describe usage of different protocols,=20
there MUST exist a specification describing a mechanism, for this specific=
=20
combination of protocols, how to associate received packets with the=20
correct protocol. In addition, if received packets for a given protocol=20
can be associated with more than one m- line, there MUST exist a=20
specification describing a mechanism for associating the received packet=20
with the correct m- line.

Y.2. STUN, DTLS and SRTP

Section X.X.X of RFC 5764 describes a mechanism for identifying the=20
protocol among the STUN, DTLS and SRTP protocols (in any combination).=20
An entity that includes m- lines describing these protocol within in a=20
BUNDLE group MUST support the mechanism described in RFC 5764=20
for identifying the protocols, and no explicit negotiation is required=20
in order to indicate support and usage of the mechanism.=20

RFC 5764 does not describe how to identity different protocols=20
transported on DTLS, only how to identify the DTLS protocol itself. If=20
multiple protocols are transported on DTLS, there MUST exist a=20
specification describing a mechanism for identifying each individual=20
protocol.  In addition, if received DTLS packets can be associated=20
with more than one m- line, there MUST exist a specification describing
a mechanism for associating the received DTLS packet with the correct=20
m- line.

Section X describes how to associate received (S)RTP packets with the=20
correct m- line.


From nobody Wed Mar 12 08:17:43 2014
Return-Path: <dwing@cisco.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 C536E1A073C for <mmusic@ietfa.amsl.com>; Wed, 12 Mar 2014 08:17:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -13.998
X-Spam-Level: 
X-Spam-Status: No, score=-13.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_12_24=1.049, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 cI4oVuyv-t1Q for <mmusic@ietfa.amsl.com>; Wed, 12 Mar 2014 08:17:34 -0700 (PDT)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id B10E21A045D for <mmusic@ietf.org>; Wed, 12 Mar 2014 08:17:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6638; q=dns/txt; s=iport; t=1394637449; x=1395847049; h=mime-version:subject:from:in-reply-to:date:cc:message-id: references:to; bh=r4PGqGmTxLOZsHcvYwVGq2iogT5ai8cfJgHmSMOH6io=; b=EQxPVdSiRdME8FmY8awbqul0h4YlBtcA3zDP1BDnqMNTNmNUyLCNeFo+ OxAv+aFzeEPeUREU+m44d1U9Zj7QGjcmUUmbECnXMCEm3U4bjifhikeHc EekNV6oF3ftshW1UP9+s2TO9i4pKXJI2JAfJ515pLGhWQv2ZyE3gdhaPV U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgkFAEp5IFOrRDoH/2dsb2JhbABagwbCZoEcFnSCJQEBAQMBeQULCw44VwYTG4dWB9IXF45cB4MkgRQEmEWGTIthgy09
X-IronPort-AV: E=Sophos;i="4.97,638,1389744000";  d="scan'208,217";a="107960295"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-4.cisco.com with ESMTP; 12 Mar 2014 15:17:28 +0000
Received: from [10.21.79.5] ([10.21.79.5]) by mtv-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s2CFGxxv018410; Wed, 12 Mar 2014 15:17:27 GMT
Content-Type: multipart/alternative; boundary="Apple-Mail=_792C02C5-057A-4A7D-B83E-72E7E8073C87"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Dan Wing <dwing@cisco.com>
In-Reply-To: <CAOJ7v-3oi-Qtsk6qiPVsAUfzEQsvgt4h6RhgfKDNUv_-47wpOA@mail.gmail.com>
Date: Tue, 11 Mar 2014 23:49:23 +0000
Message-Id: <BFFAE2A7-089D-452F-867E-BEF622BEFB77@cisco.com>
References: <CAOJ7v-3oi-Qtsk6qiPVsAUfzEQsvgt4h6RhgfKDNUv_-47wpOA@mail.gmail.com>
To: Justin Uberti <juberti@google.com>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/aO_8orNHmj-EppkOuL_8D_LCr3U
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Generalizing the aggressive nomination bugfix
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: Wed, 12 Mar 2014 15:17:40 -0000

--Apple-Mail=_792C02C5-057A-4A7D-B83E-72E7E8073C87
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On Mar 10, 2014, at 6:21 AM, Justin Uberti <juberti@google.com> wrote:

> In the WG session on Monday, Ari mentioned that the aggressive =
nomination bug of controller and controlled not agreeing on the =
candidate pair to use could be rectified by having the controlled side =
switch its preferred candidate pair to be the one that it received =
secure media on (or if not using controlled media, when the controlling =
side=92s ICE checks finally got through).
>=20
> I think there is an opportunity here to improve the overall =
flexibility of ICE. Currently, Regular Nomination allows the controller =
to have a fair amount of discretion in choosing which candidate pair it =
wants to pick; it could use metrics such as RTT, or perhaps one of the =
values mentioned in DISCUSS to make its selection, instead of using the =
static PRIORITY value. Aggressive Nomination, while faster in initially =
establishing media, does not afford this same discretion; according to =
5245, S 8.1.1.2, ICE uses the highest PRIORITY candidate pair. So it =
would be great if there was a way to allow the controller have the same =
discretion for choosing the selected candidate pair, while also doing =
Aggressive Nomination.
>=20
> I think this can easily be done using Ari=92s solution in a general =
way. In short, any time secure media packets are received by the =
controlled side, it should use that candidate pair to send its own =
media. (Secure media is needed to prevent an attacker from tricking the =
controlled side into sending media to an arbitrary address.) If secure =
media is not used, the controller could include a new attribute, =
something like a new PREFERRED-CANDIDATE attribute (or perhaps an =
updated PRIORITY attribute, set to the max ICE priority), to tell the =
controlled side which candidate pair should be used.
>=20
That all sounds good.

> This would allow the controller to do periodic RTT checks, perhaps =
using the ICE consent mechanism, and dynamically change the media path =
as needed.
>=20

I think we need additional signaling to switch interfaces, because each =
endpoint needs to participate in the decision (e.g., =
draft-wing-mmusic-ice-mobility).  For example, the controlling endpoint =
might have unmetered Internet access, whereas the other endpoint has =
fast metered Internet (e.g., LTE) and slower unmetered Internet (e.g., =
DSL) -- but if the controlling endpoint effectively ignores the ICE =
priorities in favor of round trip time calculations, the controlled =
endpoint will use LTE.  ICE priorities allows both ends to indicate =
their preferences.  We might need something more than ICE priorities, =
too, or a way to strongly say an interface is not preferred (because =
that interface is metered).

-d


--Apple-Mail=_792C02C5-057A-4A7D-B83E-72E7E8073C87
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On Mar 10, 2014, at 6:21 AM, Justin Uberti &lt;<a =
href=3D"mailto:juberti@google.com">juberti@google.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"><div dir=3D"ltr"><p class=3D"">In the WG session on =
Monday, Ari mentioned that the aggressive nomination bug of controller =
and controlled not agreeing on the candidate pair to use could be =
rectified by having the controlled side switch its preferred candidate =
pair to be the one that it received secure media on (or if not using =
controlled media, when the controlling side=92s ICE checks finally got =
through).</p><p class=3D"">I think there is an opportunity here to =
improve the overall flexibility of ICE. Currently, Regular Nomination =
allows the controller to have a fair amount of discretion in choosing =
which candidate pair it wants to pick; it could use metrics such as RTT, =
or perhaps one of the values mentioned in DISCUSS to make its selection, =
instead of using the static PRIORITY value. Aggressive Nomination, while =
faster in initially establishing media, does not afford this same =
discretion; according to 5245, S 8.1.1.2, ICE uses the highest PRIORITY =
candidate pair. So it would be great if there was a way to allow the =
controller have the same discretion for choosing the selected candidate =
pair, while also doing Aggressive Nomination.</p><p class=3D"">I think =
this can easily be done using Ari=92s solution in a general way. In =
short, any time secure media packets are received by the controlled =
side, it should use that candidate pair to send its own media. (Secure =
media is needed to prevent an attacker from tricking the controlled side =
into sending media to an arbitrary address.) If secure media is not =
used, the controller could include a new attribute, something like a new =
PREFERRED-CANDIDATE attribute (or perhaps an updated PRIORITY attribute, =
set to the max ICE priority), to tell the controlled side which =
candidate pair should be used.</p></div></blockquote><div>That all =
sounds good.</div><br><blockquote type=3D"cite"><div dir=3D"ltr"><p =
class=3D"">This would allow the controller to do periodic RTT checks, =
perhaps using the ICE consent mechanism, and dynamically change the =
media path as needed.</p></div></blockquote></div><div>I think we need =
additional signaling to switch interfaces, because each endpoint needs =
to participate in the decision (e.g., draft-wing-mmusic-ice-mobility). =
&nbsp;For example, the controlling endpoint might have unmetered =
Internet access, whereas the other endpoint has fast metered Internet =
(e.g., LTE) and slower unmetered Internet (e.g., DSL) -- but if the =
controlling endpoint effectively ignores the ICE priorities in favor of =
round trip time calculations, the controlled endpoint will use LTE. =
&nbsp;ICE priorities allows both ends to indicate their preferences. =
&nbsp;We might need something more than ICE priorities, too, or a way to =
strongly say an interface is not preferred (because that interface is =
metered).</div><div><br></div><div>-d</div><div><br></div></body></html>=

--Apple-Mail=_792C02C5-057A-4A7D-B83E-72E7E8073C87--


From nobody Wed Mar 12 09:20:08 2014
Return-Path: <juberti@google.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 5959A1A09D7 for <mmusic@ietfa.amsl.com>; Wed, 12 Mar 2014 09:20:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.925
X-Spam-Level: 
X-Spam-Status: No, score=-1.925 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001] autolearn=ham
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 Vuj33VVl_jcN for <mmusic@ietfa.amsl.com>; Wed, 12 Mar 2014 09:20:02 -0700 (PDT)
Received: from mail-vc0-x22b.google.com (mail-vc0-x22b.google.com [IPv6:2607:f8b0:400c:c03::22b]) by ietfa.amsl.com (Postfix) with ESMTP id B67F51A09CD for <mmusic@ietf.org>; Wed, 12 Mar 2014 09:20:02 -0700 (PDT)
Received: by mail-vc0-f171.google.com with SMTP id lg15so3991298vcb.16 for <mmusic@ietf.org>; Wed, 12 Mar 2014 09:19:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=+f7qt2UeDmVna4Cp8Fxk77WufthmshZHb7FJxMOr9k0=; b=T02ZotSZ1bFyBBZ/uaLJBQVTkuIGU52TGjLmHlbsCdu1o4jc08EOmYFuDXbtxBZ3E8 M3o4FgrI3trETNSYd+Wvf0D5kcIL2tMyP6JtHpSb+eFgx1gWteHwloeQb0VpAHdloO0t 7tD8v2Yh18x+1XwFvNBVie2I2Q8ElBEvAov/Wy0vZgkuidy4aDNxLmV82DO+AYWvBbyS VCyf0jk1/qkQAvF9FwEDAVYYwdhIdFXt91i0AVJFAXiH78k84Wc7471fbYzidSWg3Uga IkGeGsAGw8o8jdKySdZMoEgIBjMml/auc2A8phSsM2SbmrkOg6WI3flFXz3ZM3/8R+th yJGA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=+f7qt2UeDmVna4Cp8Fxk77WufthmshZHb7FJxMOr9k0=; b=N37DfZ8hYGJisX5ipZ77ffRLywXsru679TNgLtbW4baZiNLg+BW75ikOLMmryxTTuY bRae8096YHGcQkDt43lahoBX9L2lbvBiX+uh+IeDHoMulkDBBhDfVlJaiPnHHugoI9zV sAdY0tcwa9+cwLIdby21AfvMu4K2dKtv/UDSwuqTndDPeydNkgNg8Ad8d7rRi4TfjvMx dabrFOlNPUaUVvUuRddesZXoI1XWZMepoAWgbYF70dM6FcniHPUIHar59LAR73laZmU+ RhM3KDTrj/R4FM6mFI6cxFWLOrhfwYBcb7ME50Av5AO12vWRKkOuHhW70cgs2g6slUZM IAzQ==
X-Gm-Message-State: ALoCoQmSNhYkdDUHSryZHSf/ZjJoW52jEM0AkVxGea5D+wzPefZe2iUbHXlxZCJ3ryqjl1tMEaItQftRjhPMk6+hS1AjQbJJxOyZll54j1bG+Md95CY3994ZS+0CVhJ2P7ZkI21R7AA571liPYQmBXP4YmmL0e1Ernq0xzBgcIcbMITmlkBCKUGSLJsuoLwZPmKcgmqv0CFT
X-Received: by 10.220.188.70 with SMTP id cz6mr31347vcb.59.1394641196489; Wed, 12 Mar 2014 09:19:56 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.26.43 with HTTP; Wed, 12 Mar 2014 09:19:36 -0700 (PDT)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D20A557@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D202004@ESESSMB209.ericsson.se> <CAOJ7v-085Zdv7gTKyrU_kCFBB8rdAytE7YjQFeFsUeqWKWoW+g@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1D20A557@ESESSMB209.ericsson.se>
From: Justin Uberti <juberti@google.com>
Date: Wed, 12 Mar 2014 09:19:36 -0700
Message-ID: <CAOJ7v-2EQ3-qAi7TR_-96i8YB4cD2Xr8taZXsTQZHmtgPs5CrQ@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary=089e012951261b395c04f46b357b
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/mrLL6GDAKcPlJWW5Cjn9P7ZL-_o
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] BUNDLE: Q9/Q13: Payload type value re-usage and associating RTP packets with m- line
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: Wed, 12 Mar 2014 16:20:05 -0000

--089e012951261b395c04f46b357b
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Wed, Mar 12, 2014 at 12:55 AM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

> Hi Justin,
>
> >As I understand it, the 'receiver-id' will not identify a BUNDLE group,
> but rather a m=3D section or packet stream.
>
> Correct.
>
> Do you think the text indicates otherwise?
>

>From the text below, it appears that the receiver-id is associated with a
BUNDLE group.

*If an endpoint accepts a BUNDLE group, it MUST insert the =E2=80=9Creceive=
r-id=E2=80=9D
value in the associated RTP packets, associated with the BUNDLE group, sent
towards the remote endpoint, as described in
[receiver-id-reference-to-be-added]. *

Since the receiver-id mechanism is independent of BUNDLE, it's not clear to
me that BUNDLE needs to say anything about this, other than that the
receiver-id mechanism MUST be used.

--089e012951261b395c04f46b357b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Wed, Mar 12, 2014 at 12:55 AM, Christer Holmberg <span dir=3D"lt=
r">&lt;<a href=3D"mailto:christer.holmberg@ericsson.com" target=3D"_blank">=
christer.holmberg@ericsson.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">Hi Justin,<br>
<div class=3D""><br>
&gt;As I understand it, the &#39;receiver-id&#39; will not identify a BUNDL=
E group, but rather a m=3D section or packet stream.<br>
<br>
</div>Correct.<br>
<br>
Do you think the text indicates otherwise?<br></blockquote><div><br></div><=
div>From the text below, it appears that the receiver-id is associated with=
 a BUNDLE group.</div><div><br></div><div><i><span style=3D"font-family:Cal=
ibri,sans-serif;font-size:15px">If an endpoint accepts a BUNDLE group, it M=
UST insert the =E2=80=9Creceiver-id=E2=80=9D value in the associated RTP pa=
ckets, associated with the BUNDLE group, sent towards the remote endpoint, =
as described in [receiver-id-reference-to-be-</span><span style=3D"font-fam=
ily:Calibri,sans-serif;font-size:15px">added].</span>=C2=A0</i></div>

<div><i><br></i></div><div>Since the receiver-id mechanism is independent o=
f BUNDLE, it&#39;s not clear to me that BUNDLE needs to say anything about =
this, other than that the receiver-id mechanism MUST be used.</div></div>

</div></div>

--089e012951261b395c04f46b357b--


From nobody Wed Mar 12 09:25:45 2014
Return-Path: <palmarti@cisco.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 8E95B1A0759 for <mmusic@ietfa.amsl.com>; Wed, 12 Mar 2014 09:25:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.047
X-Spam-Level: 
X-Spam-Status: No, score=-15.047 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 r2SUeUFN567B for <mmusic@ietfa.amsl.com>; Wed, 12 Mar 2014 09:25:34 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id 4DFBE1A09B3 for <mmusic@ietf.org>; Wed, 12 Mar 2014 09:25:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9125; q=dns/txt; s=iport; t=1394641528; x=1395851128; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=JHOoZgQAHlokPRzME2MeqmsMiDFNqP+paeBeG4Whi9g=; b=H8Ip50xej/NvsQ6aNy8k9iZO7Xa0rKNOvgj7NIvQJCXF2TORWFeXXuNQ X/1Bv4Z7snGs/9KJedkkS5TI1aGS8uNxxvOtDFThyi53dOqbgay2MfZR3 PL3DL5sto/QWZnktU9HlY56yhHD6+rGpzBvuyWMKvLOVB/+HDvVwgL30e g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag8FAO2JIFOtJXG//2dsb2JhbABagwY7Swy6JoZfT4EdFnSCJgEBBAEBAWsLEAIBCD8HJwsUEQIEDgUbh14N0gcTBI5cB4MkgRQEmEWSLYMtgis
X-IronPort-AV: E=Sophos;i="4.97,639,1389744000";  d="scan'208,217";a="309633728"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by rcdn-iport-1.cisco.com with ESMTP; 12 Mar 2014 16:25:28 +0000
Received: from xhc-rcd-x08.cisco.com (xhc-rcd-x08.cisco.com [173.37.183.82]) by rcdn-core2-4.cisco.com (8.14.5/8.14.5) with ESMTP id s2CGPR7n030320 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 12 Mar 2014 16:25:27 GMT
Received: from xmb-rcd-x06.cisco.com ([169.254.6.236]) by xhc-rcd-x08.cisco.com ([173.37.183.82]) with mapi id 14.03.0123.003; Wed, 12 Mar 2014 11:25:27 -0500
From: "Pal Martinsen (palmarti)" <palmarti@cisco.com>
To: "Dan Wing (dwing)" <dwing@cisco.com>
Thread-Topic: [MMUSIC] Generalizing the aggressive nomination bugfix
Thread-Index: AQHPPCkKLN1DOCWPa0SWR1AF6tYgUprc5I2AgAEWTAA=
Date: Wed, 12 Mar 2014 16:25:27 +0000
Message-ID: <68EE741D-B0CF-4029-AC67-AC7782213138@cisco.com>
References: <CAOJ7v-3oi-Qtsk6qiPVsAUfzEQsvgt4h6RhgfKDNUv_-47wpOA@mail.gmail.com> <BFFAE2A7-089D-452F-867E-BEF622BEFB77@cisco.com>
In-Reply-To: <BFFAE2A7-089D-452F-867E-BEF622BEFB77@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.55.154.71]
Content-Type: multipart/alternative; boundary="_000_68EE741DB0CF4029AC67AC7782213138ciscocom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/qBEkls6ZHDLaIaoU5wAz43D_M0M
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Generalizing the aggressive nomination bugfix
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: Wed, 12 Mar 2014 16:25:39 -0000

--_000_68EE741DB0CF4029AC67AC7782213138ciscocom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable


On 12 Mar 2014, at 00:49, Dan Wing <dwing@cisco.com<mailto:dwing@cisco.com>=
> wrote:


On Mar 10, 2014, at 6:21 AM, Justin Uberti <juberti@google.com<mailto:juber=
ti@google.com>> wrote:


In the WG session on Monday, Ari mentioned that the aggressive nomination b=
ug of controller and controlled not agreeing on the candidate pair to use c=
ould be rectified by having the controlled side switch its preferred candid=
ate pair to be the one that it received secure media on (or if not using co=
ntrolled media, when the controlling side=92s ICE checks finally got throug=
h).

I think there is an opportunity here to improve the overall flexibility of =
ICE. Currently, Regular Nomination allows the controller to have a fair amo=
unt of discretion in choosing which candidate pair it wants to pick; it cou=
ld use metrics such as RTT, or perhaps one of the values mentioned in DISCU=
SS to make its selection, instead of using the static PRIORITY value. Aggre=
ssive Nomination, while faster in initially establishing media, does not af=
ford this same discretion; according to 5245, S 8.1.1.2, ICE uses the highe=
st PRIORITY candidate pair. So it would be great if there was a way to allo=
w the controller have the same discretion for choosing the selected candida=
te pair, while also doing Aggressive Nomination.

I think this can easily be done using Ari=92s solution in a general way. In=
 short, any time secure media packets are received by the controlled side, =
it should use that candidate pair to send its own media. (Secure media is n=
eeded to prevent an attacker from tricking the controlled side into sending=
 media to an arbitrary address.) If secure media is not used, the controlle=
r could include a new attribute, something like a new PREFERRED-CANDIDATE a=
ttribute (or perhaps an updated PRIORITY attribute, set to the max ICE prio=
rity), to tell the controlled side which candidate pair should be used.


If the PREFERRED-CANDIDATE attribute also had a priority associated with it=
, it would be possible to mach up candidate pairs that would suite both age=
nts. Something like a simplified version of the pair priority formula. Some=
 clever rules to make sure we always will end up with a pair with connectiv=
ity might also be needed.

That all sounds good.


This would allow the controller to do periodic RTT checks, perhaps using th=
e ICE consent mechanism, and dynamically change the media path as needed.

I think we need additional signaling to switch interfaces, because each end=
point needs to participate in the decision (e.g., draft-wing-mmusic-ice-mob=
ility).  For example, the controlling endpoint might have unmetered Interne=
t access, whereas the other endpoint has fast metered Internet (e.g., LTE) =
and slower unmetered Internet (e.g., DSL) -- but if the controlling endpoin=
t effectively ignores the ICE priorities in favor of round trip time calcul=
ations, the controlled endpoint will use LTE.  ICE priorities allows both e=
nds to indicate their preferences.  We might need something more than ICE p=
riorities, too, or a way to strongly say an interface is not preferred (bec=
ause that interface is metered).

If we end up in a situation where connectivity can only happen if either A =
or B is on a metered interface, how should we decide who have to pay? (Base=
d on link cost or salary?) :-)

It is an interesting problem to solve.

.-.
P=E5l-Erik


-d

_______________________________________________
mmusic mailing list
mmusic@ietf.org<mailto:mmusic@ietf.org>
https://www.ietf.org/mailman/listinfo/mmusic


--_000_68EE741DB0CF4029AC67AC7782213138ciscocom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <734E919E7092754EAE85EC45F32F01F0@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space;">
<br>
<div>
<div>On 12 Mar 2014, at 00:49, Dan Wing &lt;<a href=3D"mailto:dwing@cisco.c=
om">dwing@cisco.com</a>&gt; wrote:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space; ">
<br>
<div>
<div>On Mar 10, 2014, at 6:21 AM, Justin Uberti &lt;<a href=3D"mailto:juber=
ti@google.com">juberti@google.com</a>&gt; wrote:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite">
<div dir=3D"ltr">
<p class=3D"">In the WG session on Monday, Ari mentioned that the aggressiv=
e nomination bug of controller and controlled not agreeing on the candidate=
 pair to use could be rectified by having the controlled side switch its pr=
eferred candidate pair to be the one
 that it received secure media on (or if not using controlled media, when t=
he controlling side=92s ICE checks finally got through).</p>
<p class=3D"">I think there is an opportunity here to improve the overall f=
lexibility of ICE. Currently, Regular Nomination allows the controller to h=
ave a fair amount of discretion in choosing which candidate pair it wants t=
o pick; it could use metrics such
 as RTT, or perhaps one of the values mentioned in DISCUSS to make its sele=
ction, instead of using the static PRIORITY value. Aggressive Nomination, w=
hile faster in initially establishing media, does not afford this same disc=
retion; according to 5245, S 8.1.1.2,
 ICE uses the highest PRIORITY candidate pair. So it would be great if ther=
e was a way to allow the controller have the same discretion for choosing t=
he selected candidate pair, while also doing Aggressive Nomination.</p>
<p class=3D"">I think this can easily be done using Ari=92s solution in a g=
eneral way. In short, any time secure media packets are received by the con=
trolled side, it should use that candidate pair to send its own media. (Sec=
ure media is needed to prevent an attacker
 from tricking the controlled side into sending media to an arbitrary addre=
ss.) If secure media is not used, the controller could include a new attrib=
ute, something like a new PREFERRED-CANDIDATE attribute (or perhaps an upda=
ted PRIORITY attribute, set to the
 max ICE priority), to tell the controlled side which candidate pair should=
 be used.</p>
<div><br>
</div>
</div>
</blockquote>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>If the PREFERRED-CANDIDATE attribute also had a priority associated wi=
th it, it would be possible to mach up candidate pairs that would suite bot=
h agents. Something like a simplified version of the pair priority formula.=
 Some clever rules to make sure
 we always will end up with a pair with connectivity might also be needed.&=
nbsp;</div>
<br>
<blockquote type=3D"cite">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space; ">
<div>
<div>That all sounds good.</div>
<br>
<blockquote type=3D"cite">
<div dir=3D"ltr">
<p class=3D"">This would allow the controller to do periodic RTT checks, pe=
rhaps using the ICE consent mechanism, and dynamically change the media pat=
h as needed.</p>
</div>
</blockquote>
</div>
<div>I think we need additional signaling to switch interfaces, because eac=
h endpoint needs to participate in the decision (e.g., draft-wing-mmusic-ic=
e-mobility). &nbsp;For example, the controlling endpoint might have unmeter=
ed Internet access, whereas the other
 endpoint has fast metered Internet (e.g., LTE) and slower unmetered Intern=
et (e.g., DSL) -- but if the controlling endpoint effectively ignores the I=
CE priorities in favor of round trip time calculations, the controlled endp=
oint will use LTE. &nbsp;ICE priorities
 allows both ends to indicate their preferences. &nbsp;We might need someth=
ing more than ICE priorities, too, or a way to strongly say an interface is=
 not preferred (because that interface is metered).</div>
</div>
</blockquote>
<div><br>
</div>
<div>If we end up in a situation where connectivity can only happen if eith=
er A or B is on a metered interface, how should we decide who have to pay? =
(Based on link cost or salary?) :-)</div>
<div><br>
</div>
<div>It is an interesting problem to solve.&nbsp;</div>
<div><br>
</div>
<div>.-.</div>
<div>P=E5l-Erik</div>
<br>
<blockquote type=3D"cite">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line=
-break: after-white-space; ">
<div><br>
</div>
<div>-d</div>
<div><br>
</div>
</div>
_______________________________________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
https://www.ietf.org/mailman/listinfo/mmusic<br>
</blockquote>
</div>
<br>
</body>
</html>

--_000_68EE741DB0CF4029AC67AC7782213138ciscocom_--


From nobody Wed Mar 12 09:28:07 2014
Return-Path: <juberti@google.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 422C11A0499 for <mmusic@ietfa.amsl.com>; Wed, 12 Mar 2014 09:28:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.925
X-Spam-Level: 
X-Spam-Status: No, score=-1.925 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001] autolearn=ham
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 mMMSJpkzJ4IT for <mmusic@ietfa.amsl.com>; Wed, 12 Mar 2014 09:28:00 -0700 (PDT)
Received: from mail-ve0-x234.google.com (mail-ve0-x234.google.com [IPv6:2607:f8b0:400c:c01::234]) by ietfa.amsl.com (Postfix) with ESMTP id A8CA11A0755 for <mmusic@ietf.org>; Wed, 12 Mar 2014 09:27:59 -0700 (PDT)
Received: by mail-ve0-f180.google.com with SMTP id jz11so10483621veb.11 for <mmusic@ietf.org>; Wed, 12 Mar 2014 09:27:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=Cpyb5VAr7Z8EsshJOnD5C9srS7ZqTlNUePXdHSJsD/c=; b=mbEcrc83fJKEWxqs9IlIJ/z2DnHUfxe2Ozdvl1IT7E3t1rjwPmmVFSsIInE6djIW7l ZhqczSF0rX5GXdeBXVZacME0x47GIbMdfHDiiLyyIEVfn13gmA/2YAtXY7W9YIiHnZ5E /AAeHChBiy90/7gg8dwoOIwTW6kcZMdBabj8ALToc1Jq/naW7k7vyGamFlofaxOPOWZw N8tz7REcDplpQYWMcWJGIKis/erALeAxS3IbWcyZfEJ7cfwH7fo29qcbVFnx5zWgr8Wa 6ihkJ0hvlhilD4kszEZV7jP6XASeoRuEdcZzGzuwZwPzQ8keE+R6LSXccCc7Ih4PRWBJ i88g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=Cpyb5VAr7Z8EsshJOnD5C9srS7ZqTlNUePXdHSJsD/c=; b=bHAAphZh2P3uxxad3/FDRoj3YHi9wbTqoStct1YbMmxQSYV42If6r9wiJu72NwKagg 0bPD5m6NxRFO221NJzyyWin1Q8EKxZk7OcP5cRUaStE0qe3QIusylreJ7Okl44k/m5QM +TI6REE3fu4Rh8h/FQY3/6pjuX9F8mX8rO7z2KLcsdmBAl3rK8aaum7HRDbN+bMdRUJV fJnRb4hB/cPDpVh8uEIiRmYvXKCcV5Z6UYpneMf59mfvUtDAy18WB0SddyJ1ZXlBov0z Y61VVo9ZFZN7Jk85FJrS6+0O7a78rs+/NcfMO8x8k5G5wwDLCjgJlMAbkjoBu/L9nYxM 07Pw==
X-Gm-Message-State: ALoCoQnzbvTE2JWOAIVpEvUdO6B9W6MtKonHw71qXIo8eQrEM38nJZ/+G+UTTinnYU8sZjEf58mIKmNLClsEw2hQOx/RbVqmFexGjP1MbQcANxzVqdnqojCR4Nv1H+dBQ2Jh1eu6Vb4qxmRZgDE/Zmi5H65p4GMlO3SsKsOJKK2VM2XwG7NnVFFa6BDc6x2Zv2H1tyamLAg5
X-Received: by 10.52.34.137 with SMTP id z9mr10701867vdi.12.1394641673387; Wed, 12 Mar 2014 09:27:53 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.26.43 with HTTP; Wed, 12 Mar 2014 09:27:33 -0700 (PDT)
In-Reply-To: <BFFAE2A7-089D-452F-867E-BEF622BEFB77@cisco.com>
References: <CAOJ7v-3oi-Qtsk6qiPVsAUfzEQsvgt4h6RhgfKDNUv_-47wpOA@mail.gmail.com> <BFFAE2A7-089D-452F-867E-BEF622BEFB77@cisco.com>
From: Justin Uberti <juberti@google.com>
Date: Wed, 12 Mar 2014 09:27:33 -0700
Message-ID: <CAOJ7v-0d1bng-LHkdZ+J3Swdoic+zOF73JVfK464N0n4fY9=fw@mail.gmail.com>
To: Dan Wing <dwing@cisco.com>
Content-Type: multipart/alternative; boundary=20cf30780f6288190804f46b51fd
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/NMMxEJvEKOszVvYtNOGj9Vqx_GM
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Generalizing the aggressive nomination bugfix
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: Wed, 12 Mar 2014 16:28:05 -0000

--20cf30780f6288190804f46b51fd
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Tue, Mar 11, 2014 at 4:49 PM, Dan Wing <dwing@cisco.com> wrote:

>
> On Mar 10, 2014, at 6:21 AM, Justin Uberti <juberti@google.com> wrote:
>
> In the WG session on Monday, Ari mentioned that the aggressive nomination
> bug of controller and controlled not agreeing on the candidate pair to us=
e
> could be rectified by having the controlled side switch its preferred
> candidate pair to be the one that it received secure media on (or if not
> using controlled media, when the controlling side=E2=80=99s ICE checks fi=
nally got
> through).
>
> I think there is an opportunity here to improve the overall flexibility o=
f
> ICE. Currently, Regular Nomination allows the controller to have a fair
> amount of discretion in choosing which candidate pair it wants to pick; i=
t
> could use metrics such as RTT, or perhaps one of the values mentioned in
> DISCUSS to make its selection, instead of using the static PRIORITY value=
.
> Aggressive Nomination, while faster in initially establishing media, does
> not afford this same discretion; according to 5245, S 8.1.1.2, ICE uses t=
he
> highest PRIORITY candidate pair. So it would be great if there was a way =
to
> allow the controller have the same discretion for choosing the selected
> candidate pair, while also doing Aggressive Nomination.
>
> I think this can easily be done using Ari=E2=80=99s solution in a general=
 way. In
> short, any time secure media packets are received by the controlled side,
> it should use that candidate pair to send its own media. (Secure media is
> needed to prevent an attacker from tricking the controlled side into
> sending media to an arbitrary address.) If secure media is not used, the
> controller could include a new attribute, something like a new
> PREFERRED-CANDIDATE attribute (or perhaps an updated PRIORITY attribute,
> set to the max ICE priority), to tell the controlled side which candidate
> pair should be used.
>
> That all sounds good.
>
> This would allow the controller to do periodic RTT checks, perhaps using
> the ICE consent mechanism, and dynamically change the media path as neede=
d.
>
> I think we need additional signaling to switch interfaces, because each
> endpoint needs to participate in the decision (e.g.,
> draft-wing-mmusic-ice-mobility).  For example, the controlling endpoint
> might have unmetered Internet access, whereas the other endpoint has fast
> metered Internet (e.g., LTE) and slower unmetered Internet (e.g., DSL) --
> but if the controlling endpoint effectively ignores the ICE priorities in
> favor of round trip time calculations, the controlled endpoint will use
> LTE.  ICE priorities allows both ends to indicate their preferences.  We
> might need something more than ICE priorities, too, or a way to strongly
> say an interface is not preferred (because that interface is metered).
>
> 5245 seems to indicate that the controlling endpoint is in the driver's
seat, as explained in S 2.6:


   More fundamentally, however, the prioritization
   defined by this specification may not yield "optimal" results.  As an
   example, if the aim is to select low-latency media paths, usage of a
   relay is a hint that latencies may be higher, but it is nothing more
   than a hint.  An actual round-trip time (RTT) measurement could be
   made, and it might demonstrate that a pair with lower priority is
   actually better than one with higher priority.



   Consequently, ICE assigns one of the agents in the role of the
   CONTROLLING AGENT, and the other of the CONTROLLED AGENT.  The
   controlling agent gets to nominate which candidate pairs will get
   used for media amongst the ones that are valid.


I agree it would be useful to allow the controlled side to give some
hints to the controlling side though.

--20cf30780f6288190804f46b51fd
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Tue, Mar 11, 2014 at 4:49 PM, Dan Wing <span dir=3D"ltr">&lt;<a =
href=3D"mailto:dwing@cisco.com" target=3D"_blank">dwing@cisco.com</a>&gt;</=
span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex"><div style=3D"word-wrap:break-word"><br><div><div><div cla=
ss=3D"h5">

<div>On Mar 10, 2014, at 6:21 AM, Justin Uberti &lt;<a href=3D"mailto:juber=
ti@google.com" target=3D"_blank">juberti@google.com</a>&gt; wrote:</div><br=
><blockquote type=3D"cite"><div dir=3D"ltr"><p>In the WG session on Monday,=
 Ari mentioned that the aggressive nomination bug of controller and control=
led not agreeing on the candidate pair to use could be rectified by having =
the controlled side switch its preferred candidate pair to be the one that =
it received secure media on (or if not using controlled media, when the con=
trolling side=E2=80=99s ICE checks finally got through).</p>

<p>I think there is an opportunity here to improve the overall flexibility =
of ICE. Currently, Regular Nomination allows the controller to have a fair =
amount of discretion in choosing which candidate pair it wants to pick; it =
could use metrics such as RTT, or perhaps one of the values mentioned in DI=
SCUSS to make its selection, instead of using the static PRIORITY value. Ag=
gressive Nomination, while faster in initially establishing media, does not=
 afford this same discretion; according to 5245, S 8.1.1.2, ICE uses the hi=
ghest PRIORITY candidate pair. So it would be great if there was a way to a=
llow the controller have the same discretion for choosing the selected cand=
idate pair, while also doing Aggressive Nomination.</p>

<p>I think this can easily be done using Ari=E2=80=99s solution in a genera=
l way. In short, any time secure media packets are received by the controll=
ed side, it should use that candidate pair to send its own media. (Secure m=
edia is needed to prevent an attacker from tricking the controlled side int=
o sending media to an arbitrary address.) If secure media is not used, the =
controller could include a new attribute, something like a new PREFERRED-CA=
NDIDATE attribute (or perhaps an updated PRIORITY attribute, set to the max=
 ICE priority), to tell the controlled side which candidate pair should be =
used.</p>

</div></blockquote></div></div><div>That all sounds good.</div><div class=
=3D""><br><blockquote type=3D"cite"><div dir=3D"ltr"><p>This would allow th=
e controller to do periodic RTT checks, perhaps using the ICE consent mecha=
nism, and dynamically change the media path as needed.</p>

</div></blockquote></div></div><div>I think we need additional signaling to=
 switch interfaces, because each endpoint needs to participate in the decis=
ion (e.g., draft-wing-mmusic-ice-mobility). =C2=A0For example, the controll=
ing endpoint might have unmetered Internet access, whereas the other endpoi=
nt has fast metered Internet (e.g., LTE) and slower unmetered Internet (e.g=
., DSL) -- but if the controlling endpoint effectively ignores the ICE prio=
rities in favor of round trip time calculations, the controlled endpoint wi=
ll use LTE. =C2=A0ICE priorities allows both ends to indicate their prefere=
nces. =C2=A0We might need something more than ICE priorities, too, or a way=
 to strongly say an interface is not preferred (because that interface is m=
etered).</div>

<span class=3D""><font color=3D"#888888"><div><br></div></font></span></div=
></blockquote><div>5245 seems to indicate that the controlling endpoint is =
in the driver&#39;s seat, as explained in S 2.6:</div><div><br></div><pre c=
lass=3D"" style=3D"font-size:1em;margin-top:0px;margin-bottom:0px;color:rgb=
(0,0,0)">

   More fundamentally, however, the prioritization
   defined by this specification may not yield &quot;optimal&quot; results.=
  As an
   example, if the aim is to select low-latency media paths, usage of a
   relay is a hint that latencies may be higher, but it is nothing more
   than a hint.  An actual round-trip time (RTT) measurement could be
   made, and it might demonstrate that a pair with lower priority is
   actually better than one with higher priority.
</pre><pre class=3D"" style=3D"font-size:1em;margin-top:0px;margin-bottom:0=
px;color:rgb(0,0,0)"><br></pre><pre class=3D"" style=3D"font-size:1em;margi=
n-top:0px;margin-bottom:0px;color:rgb(0,0,0)"><pre class=3D"" style=3D"font=
-size:1em;margin-top:0px;margin-bottom:0px">

   Consequently, ICE assigns one of the agents in the role of the
   CONTROLLING AGENT, and the other of the CONTROLLED AGENT.  The
   controlling agent gets to nominate which candidate pairs will get
   used for media amongst the ones that are valid.</pre><pre class=3D"" sty=
le=3D"font-size:1em;margin-top:0px;margin-bottom:0px"><br></pre><pre class=
=3D"" style=3D"font-size:1em;margin-top:0px;margin-bottom:0px"><span style=
=3D"color:rgb(34,34,34);font-family:arial;font-size:small;white-space:norma=
l">I agree it would be useful to allow the controlled side to give some hin=
ts to the controlling side though.=C2=A0</span><br>

</pre></pre><div>=C2=A0</div></div><br></div></div>

--20cf30780f6288190804f46b51fd--


From nobody Wed Mar 12 09:31:03 2014
Return-Path: <juberti@google.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 ECD511A0451 for <mmusic@ietfa.amsl.com>; Wed, 12 Mar 2014 09:31:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.925
X-Spam-Level: 
X-Spam-Status: No, score=-1.925 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001] autolearn=ham
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 x322YIQZ-vVR for <mmusic@ietfa.amsl.com>; Wed, 12 Mar 2014 09:30:55 -0700 (PDT)
Received: from mail-vc0-x22b.google.com (mail-vc0-x22b.google.com [IPv6:2607:f8b0:400c:c03::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 571FE1A0492 for <mmusic@ietf.org>; Wed, 12 Mar 2014 09:30:54 -0700 (PDT)
Received: by mail-vc0-f171.google.com with SMTP id lg15so4006913vcb.16 for <mmusic@ietf.org>; Wed, 12 Mar 2014 09:30:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=9+b0XZNawomDj93trUOFAJFkfDxGJZF5wABhAC0M9fw=; b=BfbR1xE3O7MFLJnZ4/JEiLJqAhlmbROSELWS/XoVM19U6QNhKT8E+cOOZYNi3Dbrey NKU58e38EJL98+GniufjMBeDEKCW3m2fAsEBkHBuPu2dRSU/O5wF4/jqUklmdRSplJ1m BdeYZEWx7fkqBDmPAaXpaRNDnZt4F9yeF+RMmoQ+eCnqNOGtgCrymPY0Uhiu5LZuVSpZ MmWiZg9jQk4vLyeLLhBWFSIpuQ5LnzZ+CYT8H7PZv5ZlzOAos/+/AYydtsP5/6vD9T+Z DRPJAq1jxxHRUUzdlivBZVgGz3vU23RzPm22VyESX3Eym45Ew/As2+JLWWW2SY0LY8Qv SnDg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=9+b0XZNawomDj93trUOFAJFkfDxGJZF5wABhAC0M9fw=; b=IgnLkCCxbf4He36s6cZguj+b0GL4gLVIUlphOTtU3JB1enflPw31oKCe1+RDUyrif0 X+o8RURXvflZl6LwdjSRDvXZkrisycqcsZUZkp5yp1AWOyWs0x5csjnWIqEuBwEDzoKn 3orfaWau/ND9HD1k0rQ4RjtcXgY0gHEOi9uNZyiRX4BagMhvNCyrpKjPI3p1sGTlhXZk 7WmnT7rCo8r42WxqFoj39Ca9ZQgRuBSHIHsBsbQnRJaX6xx4D0tHDy3+xVHaqkEGYNkv zvU5QVgiAys26xJVXTTSEW4hemBVJfgfuYl3lPHUHDbhYyJDXQciK4snrZrPR8JqtUCM nU1Q==
X-Gm-Message-State: ALoCoQkewSasyGKJh0noU4KXhUOtg2YUScVmY8BlveqPPW6qO/xPKAK4M7KZU1BK99HpjP5g8eovUPYDVSKNPBPJC7NgpMb0i7m+EPQEplpXyZN3GuqURdtz8xZIEZBuB01PFXKO0N0MArayuZF0+njUMyVOdKKYfVOtqQ95GvzEZp8Y9fea0vBbqZ32TFuSV+8eYiXxdwGr
X-Received: by 10.52.136.231 with SMTP id qd7mr161240vdb.71.1394641848035; Wed, 12 Mar 2014 09:30:48 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.26.43 with HTTP; Wed, 12 Mar 2014 09:30:27 -0700 (PDT)
In-Reply-To: <68EE741D-B0CF-4029-AC67-AC7782213138@cisco.com>
References: <CAOJ7v-3oi-Qtsk6qiPVsAUfzEQsvgt4h6RhgfKDNUv_-47wpOA@mail.gmail.com> <BFFAE2A7-089D-452F-867E-BEF622BEFB77@cisco.com> <68EE741D-B0CF-4029-AC67-AC7782213138@cisco.com>
From: Justin Uberti <juberti@google.com>
Date: Wed, 12 Mar 2014 09:30:27 -0700
Message-ID: <CAOJ7v-3FUEkFWxdA6+M8pPA35MhnSOJHXnXnoB0oyPeBVWiHGA@mail.gmail.com>
To: "Pal Martinsen (palmarti)" <palmarti@cisco.com>
Content-Type: multipart/alternative; boundary=bcaec5196161f1063304f46b5bfc
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/-hQJFnsn3mMoFvjUe54lYHGSN78
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, "Dan Wing \(dwing\)" <dwing@cisco.com>
Subject: Re: [MMUSIC] Generalizing the aggressive nomination bugfix
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: Wed, 12 Mar 2014 16:31:02 -0000

--bcaec5196161f1063304f46b5bfc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Wed, Mar 12, 2014 at 9:25 AM, Pal Martinsen (palmarti) <
palmarti@cisco.com> wrote:

>
>  On 12 Mar 2014, at 00:49, Dan Wing <dwing@cisco.com> wrote:
>
>
>  On Mar 10, 2014, at 6:21 AM, Justin Uberti <juberti@google.com> wrote:
>
>  In the WG session on Monday, Ari mentioned that the aggressive
> nomination bug of controller and controlled not agreeing on the candidate
> pair to use could be rectified by having the controlled side switch its
> preferred candidate pair to be the one that it received secure media on (=
or
> if not using controlled media, when the controlling side=E2=80=99s ICE ch=
ecks
> finally got through).
>
> I think there is an opportunity here to improve the overall flexibility o=
f
> ICE. Currently, Regular Nomination allows the controller to have a fair
> amount of discretion in choosing which candidate pair it wants to pick; i=
t
> could use metrics such as RTT, or perhaps one of the values mentioned in
> DISCUSS to make its selection, instead of using the static PRIORITY value=
.
> Aggressive Nomination, while faster in initially establishing media, does
> not afford this same discretion; according to 5245, S 8.1.1.2, ICE uses t=
he
> highest PRIORITY candidate pair. So it would be great if there was a way =
to
> allow the controller have the same discretion for choosing the selected
> candidate pair, while also doing Aggressive Nomination.
>
> I think this can easily be done using Ari=E2=80=99s solution in a general=
 way. In
> short, any time secure media packets are received by the controlled side,
> it should use that candidate pair to send its own media. (Secure media is
> needed to prevent an attacker from tricking the controlled side into
> sending media to an arbitrary address.) If secure media is not used, the
> controller could include a new attribute, something like a new
> PREFERRED-CANDIDATE attribute (or perhaps an updated PRIORITY attribute,
> set to the max ICE priority), to tell the controlled side which candidate
> pair should be used.
>
>
>  If the PREFERRED-CANDIDATE attribute also had a priority associated with
> it, it would be possible to mach up candidate pairs that would suite both
> agents. Something like a simplified version of the pair priority formula.
> Some clever rules to make sure we always will end up with a pair with
> connectivity might also be needed.
>
>   That all sounds good.
>
>  This would allow the controller to do periodic RTT checks, perhaps using
> the ICE consent mechanism, and dynamically change the media path as neede=
d.
>
>  I think we need additional signaling to switch interfaces, because each
> endpoint needs to participate in the decision (e.g.,
> draft-wing-mmusic-ice-mobility).  For example, the controlling endpoint
> might have unmetered Internet access, whereas the other endpoint has fast
> metered Internet (e.g., LTE) and slower unmetered Internet (e.g., DSL) --
> but if the controlling endpoint effectively ignores the ICE priorities in
> favor of round trip time calculations, the controlled endpoint will use
> LTE.  ICE priorities allows both ends to indicate their preferences.  We
> might need something more than ICE priorities, too, or a way to strongly
> say an interface is not preferred (because that interface is metered).
>
>
>  If we end up in a situation where connectivity can only happen if either
> A or B is on a metered interface, how should we decide who have to pay?
> (Based on link cost or salary?) :-)
>

In this case I would expect the controlling side wins, unless we determine
that we need something more complex.

--bcaec5196161f1063304f46b5bfc
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Wed, Mar 12, 2014 at 9:25 AM, Pal Martinsen (palmarti) <span dir=
=3D"ltr">&lt;<a href=3D"mailto:palmarti@cisco.com" target=3D"_blank">palmar=
ti@cisco.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">



<div style=3D"word-wrap:break-word">
<br>
<div><div class=3D"">
<div>On 12 Mar 2014, at 00:49, Dan Wing &lt;<a href=3D"mailto:dwing@cisco.c=
om" target=3D"_blank">dwing@cisco.com</a>&gt; wrote:</div>
<br>
<blockquote type=3D"cite">
<div style=3D"word-wrap:break-word">
<br>
<div>
<div>On Mar 10, 2014, at 6:21 AM, Justin Uberti &lt;<a href=3D"mailto:juber=
ti@google.com" target=3D"_blank">juberti@google.com</a>&gt; wrote:</div>
<br>
<blockquote type=3D"cite">
<div dir=3D"ltr">
<p>In the WG session on Monday, Ari mentioned that the aggressive nominatio=
n bug of controller and controlled not agreeing on the candidate pair to us=
e could be rectified by having the controlled side switch its preferred can=
didate pair to be the one
 that it received secure media on (or if not using controlled media, when t=
he controlling side=E2=80=99s ICE checks finally got through).</p>
<p>I think there is an opportunity here to improve the overall flexibility =
of ICE. Currently, Regular Nomination allows the controller to have a fair =
amount of discretion in choosing which candidate pair it wants to pick; it =
could use metrics such
 as RTT, or perhaps one of the values mentioned in DISCUSS to make its sele=
ction, instead of using the static PRIORITY value. Aggressive Nomination, w=
hile faster in initially establishing media, does not afford this same disc=
retion; according to 5245, S 8.1.1.2,
 ICE uses the highest PRIORITY candidate pair. So it would be great if ther=
e was a way to allow the controller have the same discretion for choosing t=
he selected candidate pair, while also doing Aggressive Nomination.</p>


<p>I think this can easily be done using Ari=E2=80=99s solution in a genera=
l way. In short, any time secure media packets are received by the controll=
ed side, it should use that candidate pair to send its own media. (Secure m=
edia is needed to prevent an attacker
 from tricking the controlled side into sending media to an arbitrary addre=
ss.) If secure media is not used, the controller could include a new attrib=
ute, something like a new PREFERRED-CANDIDATE attribute (or perhaps an upda=
ted PRIORITY attribute, set to the
 max ICE priority), to tell the controlled side which candidate pair should=
 be used.</p>
<div><br>
</div>
</div>
</blockquote>
</div>
</div>
</blockquote>
<div><br>
</div>
</div><div>If the PREFERRED-CANDIDATE attribute also had a priority associa=
ted with it, it would be possible to mach up candidate pairs that would sui=
te both agents. Something like a simplified version of the pair priority fo=
rmula. Some clever rules to make sure
 we always will end up with a pair with connectivity might also be needed.=
=C2=A0</div><div class=3D"">
<br>
<blockquote type=3D"cite">
<div style=3D"word-wrap:break-word">
<div>
<div>That all sounds good.</div>
<br>
<blockquote type=3D"cite">
<div dir=3D"ltr">
<p>This would allow the controller to do periodic RTT checks, perhaps using=
 the ICE consent mechanism, and dynamically change the media path as needed=
.</p>
</div>
</blockquote>
</div>
<div>I think we need additional signaling to switch interfaces, because eac=
h endpoint needs to participate in the decision (e.g., draft-wing-mmusic-ic=
e-mobility). =C2=A0For example, the controlling endpoint might have unmeter=
ed Internet access, whereas the other
 endpoint has fast metered Internet (e.g., LTE) and slower unmetered Intern=
et (e.g., DSL) -- but if the controlling endpoint effectively ignores the I=
CE priorities in favor of round trip time calculations, the controlled endp=
oint will use LTE. =C2=A0ICE priorities
 allows both ends to indicate their preferences. =C2=A0We might need someth=
ing more than ICE priorities, too, or a way to strongly say an interface is=
 not preferred (because that interface is metered).</div>
</div>
</blockquote>
<div><br>
</div>
</div><div>If we end up in a situation where connectivity can only happen i=
f either A or B is on a metered interface, how should we decide who have to=
 pay? (Based on link cost or salary?) :-)</div></div></div></blockquote>

<div><br></div><div>In this case I would expect the controlling side wins, =
unless we determine that we need something more complex.=C2=A0</div></div><=
br></div></div>

--bcaec5196161f1063304f46b5bfc--


From nobody Wed Mar 12 09:33:24 2014
Return-Path: <dwing@cisco.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 BCCFE1A0492 for <mmusic@ietfa.amsl.com>; Wed, 12 Mar 2014 09:33:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.047
X-Spam-Level: 
X-Spam-Status: No, score=-15.047 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 q1WcQs-u57iU for <mmusic@ietfa.amsl.com>; Wed, 12 Mar 2014 09:33:16 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id 8A0421A0484 for <mmusic@ietf.org>; Wed, 12 Mar 2014 09:33:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11110; q=dns/txt; s=iport; t=1394641991; x=1395851591; h=mime-version:subject:from:in-reply-to:date:cc:message-id: references:to; bh=kLDy3Osskg5Ind/xByHsAjE+tIxRqtyx/tAP6h/odyM=; b=mZ3XVLlx8NSJQusYH5L0/Plqe2R7RMni8RlMGqsKsou/4Iwmzh/1ItYT 7fth9CKPo/gTE0TPUXba6f8pytBdECGKtUXGLTwUJnYS0JaXJdSen7N9K Z1E0wlFlvw3PlDrxzuBsagPgLW3upv+NdnqPhxoNXHcLqGZ2WXBdDRKlI c=;
X-IronPort-AV: E=Sophos;i="4.97,639,1389744000";  d="scan'208,217";a="309910699"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by rcdn-iport-4.cisco.com with ESMTP; 12 Mar 2014 16:33:10 +0000
Received: from [10.21.79.5] ([10.21.79.5]) by mtv-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s2CGX8aa021288; Wed, 12 Mar 2014 16:33:09 GMT
Content-Type: multipart/alternative; boundary="Apple-Mail=_376BF166-8ADC-4DE4-8297-704933E9C71F"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Dan Wing <dwing@cisco.com>
In-Reply-To: <68EE741D-B0CF-4029-AC67-AC7782213138@cisco.com>
Date: Wed, 12 Mar 2014 09:33:08 -0700
Message-Id: <0D158D24-AF4B-4ECC-816F-FA8EA28B0744@cisco.com>
References: <CAOJ7v-3oi-Qtsk6qiPVsAUfzEQsvgt4h6RhgfKDNUv_-47wpOA@mail.gmail.com> <BFFAE2A7-089D-452F-867E-BEF622BEFB77@cisco.com> <68EE741D-B0CF-4029-AC67-AC7782213138@cisco.com>
To: "Pal Martinsen (palmarti)" <palmarti@cisco.com>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/tVmudf93ZGrBrxs1hO3MkVhJZs4
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Generalizing the aggressive nomination bugfix
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: Wed, 12 Mar 2014 16:33:22 -0000

--Apple-Mail=_376BF166-8ADC-4DE4-8297-704933E9C71F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On Mar 12, 2014, at 9:25 AM, "Pal Martinsen (palmarti)" =
<palmarti@cisco.com> wrote:

>=20
> On 12 Mar 2014, at 00:49, Dan Wing <dwing@cisco.com> wrote:
>=20
>>=20
>> On Mar 10, 2014, at 6:21 AM, Justin Uberti <juberti@google.com> =
wrote:
>>=20
>>> In the WG session on Monday, Ari mentioned that the aggressive =
nomination bug of controller and controlled not agreeing on the =
candidate pair to use could be rectified by having the controlled side =
switch its preferred candidate pair to be the one that it received =
secure media on (or if not using controlled media, when the controlling =
side=92s ICE checks finally got through).
>>>=20
>>> I think there is an opportunity here to improve the overall =
flexibility of ICE. Currently, Regular Nomination allows the controller =
to have a fair amount of discretion in choosing which candidate pair it =
wants to pick; it could use metrics such as RTT, or perhaps one of the =
values mentioned in DISCUSS to make its selection, instead of using the =
static PRIORITY value. Aggressive Nomination, while faster in initially =
establishing media, does not afford this same discretion; according to =
5245, S 8.1.1.2, ICE uses the highest PRIORITY candidate pair. So it =
would be great if there was a way to allow the controller have the same =
discretion for choosing the selected candidate pair, while also doing =
Aggressive Nomination.
>>>=20
>>> I think this can easily be done using Ari=92s solution in a general =
way. In short, any time secure media packets are received by the =
controlled side, it should use that candidate pair to send its own =
media. (Secure media is needed to prevent an attacker from tricking the =
controlled side into sending media to an arbitrary address.) If secure =
media is not used, the controller could include a new attribute, =
something like a new PREFERRED-CANDIDATE attribute (or perhaps an =
updated PRIORITY attribute, set to the max ICE priority), to tell the =
controlled side which candidate pair should be used.
>>>=20
>>>=20
>=20
> If the PREFERRED-CANDIDATE attribute also had a priority associated =
with it, it would be possible to mach up candidate pairs that would =
suite both agents. Something like a simplified version of the pair =
priority formula. Some clever rules to make sure we always will end up =
with a pair with connectivity might also be needed.=20

Yes, I like that.  Probably best to signal in ICE rather than in SDP, =
for lots of reasons, too.  That idea is similar (but not identical) to =
MPTCP's MP_PRIO to indicate backup/standby path, =
http://tools.ietf.org/html/rfc6824#section-2.5.


>=20
>> That all sounds good.
>>=20
>>> This would allow the controller to do periodic RTT checks, perhaps =
using the ICE consent mechanism, and dynamically change the media path =
as needed.
>>>=20
>>=20
>> I think we need additional signaling to switch interfaces, because =
each endpoint needs to participate in the decision (e.g., =
draft-wing-mmusic-ice-mobility).  For example, the controlling endpoint =
might have unmetered Internet access, whereas the other endpoint has =
fast metered Internet (e.g., LTE) and slower unmetered Internet (e.g., =
DSL) -- but if the controlling endpoint effectively ignores the ICE =
priorities in favor of round trip time calculations, the controlled =
endpoint will use LTE.  ICE priorities allows both ends to indicate =
their preferences.  We might need something more than ICE priorities, =
too, or a way to strongly say an interface is not preferred (because =
that interface is metered).
>=20
> If we end up in a situation where connectivity can only happen if =
either A or B is on a metered interface, how should we decide who have =
to pay? (Based on link cost or salary?) :-)
>=20
> It is an interesting problem to solve.=20

I don't think it is solvable with protocols, except to allow both ends =
to have enough information to make a smarter policy decision.

-d



>=20
> .-.
> P=E5l-Erik
>=20
>>=20
>> -d
>>=20
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www.ietf.org/mailman/listinfo/mmusic
>=20


--Apple-Mail=_376BF166-8ADC-4DE4-8297-704933E9C71F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On Mar 12, 2014, at 9:25 AM, "Pal Martinsen (palmarti)" =
&lt;<a href=3D"mailto:palmarti@cisco.com">palmarti@cisco.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite">

<meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3DWindows-1252">

<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space;">
<br>
<div>
<div>On 12 Mar 2014, at 00:49, Dan Wing &lt;<a =
href=3D"mailto:dwing@cisco.com">dwing@cisco.com</a>&gt; wrote:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">
<br>
<div>
<div>On Mar 10, 2014, at 6:21 AM, Justin Uberti &lt;<a =
href=3D"mailto:juberti@google.com">juberti@google.com</a>&gt; =
wrote:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite">
<div dir=3D"ltr"><p class=3D"">In the WG session on Monday, Ari =
mentioned that the aggressive nomination bug of controller and =
controlled not agreeing on the candidate pair to use could be rectified =
by having the controlled side switch its preferred candidate pair to be =
the one
 that it received secure media on (or if not using controlled media, =
when the controlling side=92s ICE checks finally got through).</p><p =
class=3D"">I think there is an opportunity here to improve the overall =
flexibility of ICE. Currently, Regular Nomination allows the controller =
to have a fair amount of discretion in choosing which candidate pair it =
wants to pick; it could use metrics such
 as RTT, or perhaps one of the values mentioned in DISCUSS to make its =
selection, instead of using the static PRIORITY value. Aggressive =
Nomination, while faster in initially establishing media, does not =
afford this same discretion; according to 5245, S 8.1.1.2,
 ICE uses the highest PRIORITY candidate pair. So it would be great if =
there was a way to allow the controller have the same discretion for =
choosing the selected candidate pair, while also doing Aggressive =
Nomination.</p><p class=3D"">I think this can easily be done using Ari=92s=
 solution in a general way. In short, any time secure media packets are =
received by the controlled side, it should use that candidate pair to =
send its own media. (Secure media is needed to prevent an attacker
 from tricking the controlled side into sending media to an arbitrary =
address.) If secure media is not used, the controller could include a =
new attribute, something like a new PREFERRED-CANDIDATE attribute (or =
perhaps an updated PRIORITY attribute, set to the
 max ICE priority), to tell the controlled side which candidate pair =
should be used.</p>
<div><br>
</div>
</div>
</blockquote>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>If the PREFERRED-CANDIDATE attribute also had a priority associated =
with it, it would be possible to mach up candidate pairs that would =
suite both agents. Something like a simplified version of the pair =
priority formula. Some clever rules to make sure
 we always will end up with a pair with connectivity might also be =
needed.&nbsp;</div></div></div></blockquote><div><br></div><div>Yes, I =
like that. &nbsp;Probably best to signal in ICE rather than in SDP, for =
lots of reasons, too. &nbsp;That idea is similar (but not identical) to =
MPTCP's MP_PRIO to indicate backup/standby path, <a =
href=3D"http://tools.ietf.org/html/rfc6824#section-2.5">http://tools.ietf.=
org/html/rfc6824#section-2.5</a>.</div><div><br></div><br><blockquote =
type=3D"cite"><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space;"><div>
<br>
<blockquote type=3D"cite">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">
<div>
<div>That all sounds good.</div>
<br>
<blockquote type=3D"cite">
<div dir=3D"ltr"><p class=3D"">This would allow the controller to do =
periodic RTT checks, perhaps using the ICE consent mechanism, and =
dynamically change the media path as needed.</p>
</div>
</blockquote>
</div>
<div>I think we need additional signaling to switch interfaces, because =
each endpoint needs to participate in the decision (e.g., =
draft-wing-mmusic-ice-mobility). &nbsp;For example, the controlling =
endpoint might have unmetered Internet access, whereas the other
 endpoint has fast metered Internet (e.g., LTE) and slower unmetered =
Internet (e.g., DSL) -- but if the controlling endpoint effectively =
ignores the ICE priorities in favor of round trip time calculations, the =
controlled endpoint will use LTE. &nbsp;ICE priorities
 allows both ends to indicate their preferences. &nbsp;We might need =
something more than ICE priorities, too, or a way to strongly say an =
interface is not preferred (because that interface is metered).</div>
</div>
</blockquote>
<div><br>
</div>
<div>If we end up in a situation where connectivity can only happen if =
either A or B is on a metered interface, how should we decide who have =
to pay? (Based on link cost or salary?) :-)</div>
<div><br>
</div>
<div>It is an interesting problem to =
solve.&nbsp;</div></div></div></blockquote><div><br></div><div>I don't =
think it is solvable with protocols, except to allow both ends to have =
enough information to make a smarter policy =
decision.</div><div><br></div><div>-d</div><div><br></div><div><br></div><=
br><blockquote type=3D"cite"><div style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div>
<div><br>
</div>
<div>.-.</div>
<div>P=E5l-Erik</div>
<br>
<blockquote type=3D"cite">
<div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">
<div><br>
</div>
<div>-d</div>
<div><br>
</div>
</div>
_______________________________________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
<a =
href=3D"https://www.ietf.org/mailman/listinfo/mmusic">https://www.ietf.org=
/mailman/listinfo/mmusic</a><br>
</blockquote>
</div>
<br>
</div>

</blockquote></div><br></body></html>=

--Apple-Mail=_376BF166-8ADC-4DE4-8297-704933E9C71F--


From nobody Wed Mar 12 09:35:55 2014
Return-Path: <dwing@cisco.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 0D3EC1A078C for <mmusic@ietfa.amsl.com>; Wed, 12 Mar 2014 09:35:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.047
X-Spam-Level: 
X-Spam-Status: No, score=-10.047 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 Hv-Xu1vNIVhX for <mmusic@ietfa.amsl.com>; Wed, 12 Mar 2014 09:35:45 -0700 (PDT)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) by ietfa.amsl.com (Postfix) with ESMTP id 6F2121A0745 for <mmusic@ietf.org>; Wed, 12 Mar 2014 09:35:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10743; q=dns/txt; s=iport; t=1394642137; x=1395851737; h=mime-version:subject:from:in-reply-to:date:cc:message-id: references:to; bh=7m1eevfSlY1Q4Ye+ETiKncdMoveApvZs+jtFfrzUyMU=; b=Ajv7hegY9rkyyhOzoKgoU95DOECNXQnAsNl7Yx9axdfF15ZL1CkKMp8x +CjQwgN+DhZ/zv20zGZfcIjYggMAb1ZqNuTU45j7Tt5qVTtJuZ1f8lkuq AxS2xwraJNT0gWfR7SGV/CjtVtJlvzbij3WyJB3soKUKO3gh67Bd8rINm E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgkFANiLIFOrRDoG/2dsb2JhbABagwbCZoEdFnSCJQEBAQMBeRALDgouVwYTG4dWB9IXF45cB4MkgRQEiVGOdIZMi2GDTR0
X-IronPort-AV: E=Sophos; i="4.97,639,1389744000"; d="scan'208,217"; a="26914467"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by alln-iport-6.cisco.com with ESMTP; 12 Mar 2014 16:35:36 +0000
Received: from [10.21.79.5] ([10.21.79.5]) by mtv-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s2CGZZJa028882; Wed, 12 Mar 2014 16:35:36 GMT
Content-Type: multipart/alternative; boundary="Apple-Mail=_3BFCC0D3-8204-43A9-A153-22AA041C67DE"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Dan Wing <dwing@cisco.com>
In-Reply-To: <CAOJ7v-0d1bng-LHkdZ+J3Swdoic+zOF73JVfK464N0n4fY9=fw@mail.gmail.com>
Date: Wed, 12 Mar 2014 09:35:35 -0700
Message-Id: <9450C3A0-9509-4D1E-8C6C-54B884086B38@cisco.com>
References: <CAOJ7v-3oi-Qtsk6qiPVsAUfzEQsvgt4h6RhgfKDNUv_-47wpOA@mail.gmail.com> <BFFAE2A7-089D-452F-867E-BEF622BEFB77@cisco.com> <CAOJ7v-0d1bng-LHkdZ+J3Swdoic+zOF73JVfK464N0n4fY9=fw@mail.gmail.com>
To: Justin Uberti <juberti@google.com>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/WySkPvRVXM5Xuff7lPz6L1ltK2g
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Generalizing the aggressive nomination bugfix
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: Wed, 12 Mar 2014 16:35:51 -0000

--Apple-Mail=_3BFCC0D3-8204-43A9-A153-22AA041C67DE
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On Mar 12, 2014, at 9:27 AM, Justin Uberti <juberti@google.com> wrote:

>=20
>=20
>=20
> On Tue, Mar 11, 2014 at 4:49 PM, Dan Wing <dwing@cisco.com> wrote:
>=20
> On Mar 10, 2014, at 6:21 AM, Justin Uberti <juberti@google.com> wrote:
>=20
>> In the WG session on Monday, Ari mentioned that the aggressive =
nomination bug of controller and controlled not agreeing on the =
candidate pair to use could be rectified by having the controlled side =
switch its preferred candidate pair to be the one that it received =
secure media on (or if not using controlled media, when the controlling =
side=92s ICE checks finally got through).
>>=20
>> I think there is an opportunity here to improve the overall =
flexibility of ICE. Currently, Regular Nomination allows the controller =
to have a fair amount of discretion in choosing which candidate pair it =
wants to pick; it could use metrics such as RTT, or perhaps one of the =
values mentioned in DISCUSS to make its selection, instead of using the =
static PRIORITY value. Aggressive Nomination, while faster in initially =
establishing media, does not afford this same discretion; according to =
5245, S 8.1.1.2, ICE uses the highest PRIORITY candidate pair. So it =
would be great if there was a way to allow the controller have the same =
discretion for choosing the selected candidate pair, while also doing =
Aggressive Nomination.
>>=20
>> I think this can easily be done using Ari=92s solution in a general =
way. In short, any time secure media packets are received by the =
controlled side, it should use that candidate pair to send its own =
media. (Secure media is needed to prevent an attacker from tricking the =
controlled side into sending media to an arbitrary address.) If secure =
media is not used, the controller could include a new attribute, =
something like a new PREFERRED-CANDIDATE attribute (or perhaps an =
updated PRIORITY attribute, set to the max ICE priority), to tell the =
controlled side which candidate pair should be used.
>>=20
>=20
> That all sounds good.
>=20
>> This would allow the controller to do periodic RTT checks, perhaps =
using the ICE consent mechanism, and dynamically change the media path =
as needed.
>>=20
>=20
> I think we need additional signaling to switch interfaces, because =
each endpoint needs to participate in the decision (e.g., =
draft-wing-mmusic-ice-mobility).  For example, the controlling endpoint =
might have unmetered Internet access, whereas the other endpoint has =
fast metered Internet (e.g., LTE) and slower unmetered Internet (e.g., =
DSL) -- but if the controlling endpoint effectively ignores the ICE =
priorities in favor of round trip time calculations, the controlled =
endpoint will use LTE.  ICE priorities allows both ends to indicate =
their preferences.  We might need something more than ICE priorities, =
too, or a way to strongly say an interface is not preferred (because =
that interface is metered).
>=20
> 5245 seems to indicate that the controlling endpoint is in the =
driver's seat, as explained in S 2.6:
>=20
>=20
>    More fundamentally, however, the prioritization
>    defined by this specification may not yield "optimal" results.  As =
an
>    example, if the aim is to select low-latency media paths, usage of =
a
>    relay is a hint that latencies may be higher, but it is nothing =
more
>    than a hint.  An actual round-trip time (RTT) measurement could be
>    made, and it might demonstrate that a pair with lower priority is
>    actually better than one with higher priority.
>=20
>=20
>    Consequently, ICE assigns one of the agents in the role of the
>    CONTROLLING AGENT, and the other of the CONTROLLED AGENT.  The
>    controlling agent gets to nominate which candidate pairs will get
>    used for media amongst the ones that are valid.
>=20
> I agree it would be useful to allow the controlled side to give some =
hints to the controlling side though.=20

I agree the controlling side is controlling.  But it needs to be =
influenced by the controlled side, or else users will have to manually =
toggle their interfaces on/off to avoid overage charges.  That toggling =
is a p.i.t.a.

-d


--Apple-Mail=_3BFCC0D3-8204-43A9-A153-22AA041C67DE
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On Mar 12, 2014, at 9:27 AM, Justin Uberti &lt;<a =
href=3D"mailto:juberti@google.com">juberti@google.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"><div dir=3D"ltr"><br><div =
class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Tue, Mar 11, =
2014 at 4:49 PM, Dan Wing <span dir=3D"ltr">&lt;<a =
href=3D"mailto:dwing@cisco.com" =
target=3D"_blank">dwing@cisco.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px =
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left=
-style:solid;padding-left:1ex"><div =
style=3D"word-wrap:break-word"><br><div><div><div class=3D"h5">

<div>On Mar 10, 2014, at 6:21 AM, Justin Uberti &lt;<a =
href=3D"mailto:juberti@google.com" =
target=3D"_blank">juberti@google.com</a>&gt; wrote:</div><br><blockquote =
type=3D"cite"><div dir=3D"ltr"><p>In the WG session on Monday, Ari =
mentioned that the aggressive nomination bug of controller and =
controlled not agreeing on the candidate pair to use could be rectified =
by having the controlled side switch its preferred candidate pair to be =
the one that it received secure media on (or if not using controlled =
media, when the controlling side=92s ICE checks finally got =
through).</p><p>I think there is an opportunity here to improve the =
overall flexibility of ICE. Currently, Regular Nomination allows the =
controller to have a fair amount of discretion in choosing which =
candidate pair it wants to pick; it could use metrics such as RTT, or =
perhaps one of the values mentioned in DISCUSS to make its selection, =
instead of using the static PRIORITY value. Aggressive Nomination, while =
faster in initially establishing media, does not afford this same =
discretion; according to 5245, S 8.1.1.2, ICE uses the highest PRIORITY =
candidate pair. So it would be great if there was a way to allow the =
controller have the same discretion for choosing the selected candidate =
pair, while also doing Aggressive Nomination.</p><p>I think this can =
easily be done using Ari=92s solution in a general way. In short, any =
time secure media packets are received by the controlled side, it should =
use that candidate pair to send its own media. (Secure media is needed =
to prevent an attacker from tricking the controlled side into sending =
media to an arbitrary address.) If secure media is not used, the =
controller could include a new attribute, something like a new =
PREFERRED-CANDIDATE attribute (or perhaps an updated PRIORITY attribute, =
set to the max ICE priority), to tell the controlled side which =
candidate pair should be used.</p>

</div></blockquote></div></div><div>That all sounds good.</div><div =
class=3D""><br><blockquote type=3D"cite"><div dir=3D"ltr"><p>This would =
allow the controller to do periodic RTT checks, perhaps using the ICE =
consent mechanism, and dynamically change the media path as needed.</p>

</div></blockquote></div></div><div>I think we need additional signaling =
to switch interfaces, because each endpoint needs to participate in the =
decision (e.g., draft-wing-mmusic-ice-mobility). &nbsp;For example, the =
controlling endpoint might have unmetered Internet access, whereas the =
other endpoint has fast metered Internet (e.g., LTE) and slower =
unmetered Internet (e.g., DSL) -- but if the controlling endpoint =
effectively ignores the ICE priorities in favor of round trip time =
calculations, the controlled endpoint will use LTE. &nbsp;ICE priorities =
allows both ends to indicate their preferences. &nbsp;We might need =
something more than ICE priorities, too, or a way to strongly say an =
interface is not preferred (because that interface is metered).</div>

<span class=3D""><font =
color=3D"#888888"><br></font></span></div></blockquote><div>5245 seems =
to indicate that the controlling endpoint is in the driver's seat, as =
explained in S 2.6:</div><div><br></div><pre class=3D"" =
style=3D"font-size: 1em; margin-top: 0px; margin-bottom: 0px; ">
   More fundamentally, however, the prioritization
   defined by this specification may not yield "optimal" results.  As an
   example, if the aim is to select low-latency media paths, usage of a
   relay is a hint that latencies may be higher, but it is nothing more
   than a hint.  An actual round-trip time (RTT) measurement could be
   made, and it might demonstrate that a pair with lower priority is
   actually better than one with higher priority.
</pre><pre class=3D"" style=3D"font-size: 1em; margin-top: 0px; =
margin-bottom: 0px; "><br></pre><pre class=3D"" style=3D"font-size: 1em; =
margin-top: 0px; margin-bottom: 0px; "><pre class=3D"" =
style=3D"font-size:1em;margin-top:0px;margin-bottom:0px">
   Consequently, ICE assigns one of the agents in the role of the
   CONTROLLING AGENT, and the other of the CONTROLLED AGENT.  The
   controlling agent gets to nominate which candidate pairs will get
   used for media amongst the ones that are valid.</pre><pre class=3D"" =
style=3D"font-size:1em;margin-top:0px;margin-bottom:0px"><br></pre><pre =
class=3D"" style=3D"font-size:1em;margin-top:0px;margin-bottom:0px"><span =
style=3D"color:rgb(34,34,34);font-family:arial;font-size:small;white-space=
:normal">I agree it would be useful to allow the controlled side to give =
some hints to the controlling side =
though.&nbsp;</span></pre></pre></div></div></div></blockquote><br></div><=
div>I agree the controlling side is controlling. &nbsp;But it needs to =
be influenced by the controlled side, or else users will have to =
manually toggle their interfaces on/off to avoid overage charges. =
&nbsp;That toggling is a =
p.i.t.a.</div><div><br></div><div>-d</div><div><br></div></body></html>=

--Apple-Mail=_3BFCC0D3-8204-43A9-A153-22AA041C67DE--


From nobody Wed Mar 12 14:11:08 2014
Return-Path: <pkyzivat@alum.mit.edu>
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 388C51A0644 for <mmusic@ietfa.amsl.com>; Wed, 12 Mar 2014 14:11:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] 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 v1X041nMjQPY for <mmusic@ietfa.amsl.com>; Wed, 12 Mar 2014 14:11:06 -0700 (PDT)
Received: from qmta07.westchester.pa.mail.comcast.net (qmta07.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:64]) by ietfa.amsl.com (Postfix) with ESMTP id D07371A074C for <mmusic@ietf.org>; Wed, 12 Mar 2014 14:11:05 -0700 (PDT)
Received: from omta08.westchester.pa.mail.comcast.net ([76.96.62.12]) by qmta07.westchester.pa.mail.comcast.net with comcast id cdNt1n0020Fqzac57lAzM0; Wed, 12 Mar 2014 21:10:59 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta08.westchester.pa.mail.comcast.net with comcast id clAz1n00D3ZTu2S3UlAz2j; Wed, 12 Mar 2014 21:10:59 +0000
Message-ID: <5320CD63.8080904@alum.mit.edu>
Date: Wed, 12 Mar 2014 17:10:59 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: mmusic@ietf.org
References: <53185B8E.2070808@nteczone.com>	<C8EB64C0-3140-477C-9373-BD36B4B1A64B@ericsson.com>	<53187415.2000108@nteczone.com>	<C1D662DF-E3E3-45CD-991F-8090CD7130E0@ericsson.com>	<CABkgnnWOVf-72jeLbo74dbpxwhiYwgOjsfte2Cx3Voi_YRxdTg@mail.gmail.com>	<5319A928.8040703@alvestrand.no> <CABkgnnVghjLVBPQiYwjgH1uVac1Qm5MwWj09e1uk90shVjss3w@mail.gmail.com> <531DAF79.6070505@alvestrand.no>
In-Reply-To: <531DAF79.6070505@alvestrand.no>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1394658659; bh=HmkElrPNFQOfD806JoW9/2AzibiYm4YufYLkU/pSWSs=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=NmMavGhoD7rqo0Fxm6FYMddCZtQTqJGiGmEomBJv8cwPZ4wXonVgYBAxNgIuif6// gOLkOC7mdJztsKPFLh42JGoFjPUkJqyDflShVBIlsJMDxw3nNuT+unpbpQMvYcaoW3 Qm9v4UTfqfPaX2/LaQwhOodcT/GqxAj0cUje4YwhvJKQo4nOZ6S7DzkPyn40MBszKI 1cWHJ6T8dPYCVkSVIx72OKaFMF2Pk47aLDsNDVDoMPUoRT+79EU4mylil6Q5GsIHp0 ksXWpbKfuNPdSoaycgO+Eyk/sQcWOWiPqmjH3mC5iosH58imko7IpQCcNcBOmkwmQg 9YSmV7hpMC6Yg==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/CBC7RUm4ETfO2X-9KK8pM1UL3R8
Subject: Re: [MMUSIC] SCTP AppID
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: Wed, 12 Mar 2014 21:11:07 -0000

(Disclaimer - ALPN is new to me. I just read the latest draft on it.)

Based on an initial reading, I question the applicability of ALPN to our 
situation. IIUC the "application layer protocols" described in this 
registry are intended to be appropriate candidates for use over TLS. I 
think that means they are defined to be used over a reliable byte single 
byte stream protocol. Certainly that is so for the ones in the initial 
registration.

It would make *no* sense to offer to run data channels over TLS. The 
definition requires SCTP as the underlying transport protocol.

And what we are defining isn't a single "protocol" in the conventional 
sense. It is a convention for using multiple SCTP streams, including the 
negotiation of an individual protocol for each one.

Arguably, ALPN would be more appropriate for declaring/negotiating the 
protocol on individual data channels. (But not really, since they are 
message oriented, not stream oriented, and reliability is optional, etc.)

I suppose ALPN could be generalized to be more widely applicable. But 
that would simply complicate it for its current intended use.

IMO we have something new here.

	Thanks,
	Paul

On 3/10/14 8:26 AM, Harald Alvestrand wrote:
> On 03/07/2014 12:22 PM, Martin Thomson wrote:
>> On 7 March 2014 11:10, Harald Alvestrand <harald@alvestrand.no> wrote:
>>> One irritating case in our particular use case is that we actually don't
>>> know the lowest layers ahead of time.
>> The fact that we are using wired Ethernet vs. WiFi is generally not
>> visible at the level we're doing this identification either.
>>
>> If it does not matter to the protocol semantics, then I believe it to
>> be safe to use the same identifier for two similar-but-not-identical
>> stacks.
>>
>> Yes, one might argue that TURN-TCP encapsulation is tangibly different
>> to non-encapsulated SRTP.  We can talk about those distinctions and
>> whether they require different identifiers, but in this case, I don't
>> see any need for distinction.
> I think we're both arguing that a tag should only identify
> SCTP-over-DTLS as the protocol stack. If so, we agree,
>
> No opinion on whether ALPN is useful for our use case; I don't
> understand it yet (haven't read the spec), so haven't formed one.
>
>            Harald
>


From nobody Wed Mar 12 22:12:32 2014
Return-Path: <juberti@google.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 518C01A08BF for <mmusic@ietfa.amsl.com>; Wed, 12 Mar 2014 22:12:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.925
X-Spam-Level: 
X-Spam-Status: No, score=-1.925 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001] autolearn=ham
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 aDzDOQo6NrAN for <mmusic@ietfa.amsl.com>; Wed, 12 Mar 2014 22:12:26 -0700 (PDT)
Received: from mail-vc0-x230.google.com (mail-vc0-x230.google.com [IPv6:2607:f8b0:400c:c03::230]) by ietfa.amsl.com (Postfix) with ESMTP id 07F1F1A08BA for <mmusic@ietf.org>; Wed, 12 Mar 2014 22:12:25 -0700 (PDT)
Received: by mail-vc0-f176.google.com with SMTP id lc6so535031vcb.21 for <mmusic@ietf.org>; Wed, 12 Mar 2014 22:12:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=HeL4LXUqx4rVlp3j/FFInWl/XBlhlAXJ8AVX4Ya4Qco=; b=H4eusNUxkCkerC3HYBaoL8HAaBMw41in0sdvaCXwxccS/zi+v9YgSUE/iR/v41Yf22 8RS9s4Dq/483WnlJLEtsbY9Q/5l/KPxQlZxqOfwyLlrLcw4zAhcmOQJzPWYeSCH5NrV1 gplwWgUUj5WRXoicsNZhIkohwzlefYyyfdo3Xj9Fc3wcFKW8uKcKzDH+GcZG49hlfRI/ 5MmvIAKDn2JV/xaPkG2dA7S6nxHZRYcyi6QHxPfbLqzaZc+Rv03PnPK7Uk32nGeHqM4W guWx9uF/dU1ACTdhEv6nok3hw0EjhKrs6k7i7dYAlmomi0lXWl1MEWAeksZZ1hRrgHsw dPIQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=HeL4LXUqx4rVlp3j/FFInWl/XBlhlAXJ8AVX4Ya4Qco=; b=cPlTd9h1kC1tHxT6kPE56gJdEn6MedNlgRlwwnakHU8r/Gg1LU1/yurnrMF8wf07fd Xpx5Eyp+jfHwaCTgqHGEch1IOgkHJdCnTBMYLJ8PimWCqEQZstd7q6cepL8B6HIKALu+ 3nt+VtIOgXleCtqPQAushlGdvgIkeI87UwnyUdURWIhSKSjH5aKsIsoESG9qdXTvAhAI FSIyImXM3aKyuwTXfPNvZdlECpnoBcud1SUFF3rA/xOlDG5A7fVVnrnJlMPoUP2N7dyP iv6ATeTYxKkeE7nu7aocmnV1lQhohAWI5zBGfcGJ2Jr23b+UldaqoAe+/8+TqxyMKVj/ 2NJQ==
X-Gm-Message-State: ALoCoQkLKVcn6N7FcWhSpuB0yODM2W/l1tMrweMvulexvL/1XIX9NMjICcY2sJ9EW3WYQ+Ao40DU/G1jcHJovkMPJnQkEw6X3cC7+K9CadFzPuG5uA/7KOlrK5TIpcGD/uLJ2BY3W6sIcQ1W1Jy9DCXHb5z2jejR9hTzRfC1LgL5E+S6mgZzGrcfA9ob43fwfGX+Roij4zSV
X-Received: by 10.52.83.229 with SMTP id t5mr75740vdy.91.1394687539311; Wed, 12 Mar 2014 22:12:19 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.26.43 with HTTP; Wed, 12 Mar 2014 22:11:59 -0700 (PDT)
In-Reply-To: <9450C3A0-9509-4D1E-8C6C-54B884086B38@cisco.com>
References: <CAOJ7v-3oi-Qtsk6qiPVsAUfzEQsvgt4h6RhgfKDNUv_-47wpOA@mail.gmail.com> <BFFAE2A7-089D-452F-867E-BEF622BEFB77@cisco.com> <CAOJ7v-0d1bng-LHkdZ+J3Swdoic+zOF73JVfK464N0n4fY9=fw@mail.gmail.com> <9450C3A0-9509-4D1E-8C6C-54B884086B38@cisco.com>
From: Justin Uberti <juberti@google.com>
Date: Wed, 12 Mar 2014 22:11:59 -0700
Message-ID: <CAOJ7v-3Z=x=1kDuB3LCu3g1gZ6M4BytrwbJ3FJnjOpAy-um6PQ@mail.gmail.com>
To: Dan Wing <dwing@cisco.com>
Content-Type: multipart/alternative; boundary=001a1136b1145ad20f04f475ffd6
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/Ar0PpP871Nb1KoRYvWVSP84nKGM
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Generalizing the aggressive nomination bugfix
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: Thu, 13 Mar 2014 05:12:29 -0000

--001a1136b1145ad20f04f475ffd6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Wed, Mar 12, 2014 at 9:35 AM, Dan Wing <dwing@cisco.com> wrote:

>
> On Mar 12, 2014, at 9:27 AM, Justin Uberti <juberti@google.com> wrote:
>
>
>
>
> On Tue, Mar 11, 2014 at 4:49 PM, Dan Wing <dwing@cisco.com> wrote:
>
>>
>> On Mar 10, 2014, at 6:21 AM, Justin Uberti <juberti@google.com> wrote:
>>
>> In the WG session on Monday, Ari mentioned that the aggressive nominatio=
n
>> bug of controller and controlled not agreeing on the candidate pair to u=
se
>> could be rectified by having the controlled side switch its preferred
>> candidate pair to be the one that it received secure media on (or if not
>> using controlled media, when the controlling side=E2=80=99s ICE checks f=
inally got
>> through).
>>
>> I think there is an opportunity here to improve the overall flexibility
>> of ICE. Currently, Regular Nomination allows the controller to have a fa=
ir
>> amount of discretion in choosing which candidate pair it wants to pick; =
it
>> could use metrics such as RTT, or perhaps one of the values mentioned in
>> DISCUSS to make its selection, instead of using the static PRIORITY valu=
e.
>> Aggressive Nomination, while faster in initially establishing media, doe=
s
>> not afford this same discretion; according to 5245, S 8.1.1.2, ICE uses =
the
>> highest PRIORITY candidate pair. So it would be great if there was a way=
 to
>> allow the controller have the same discretion for choosing the selected
>> candidate pair, while also doing Aggressive Nomination.
>>
>> I think this can easily be done using Ari=E2=80=99s solution in a genera=
l way. In
>> short, any time secure media packets are received by the controlled side=
,
>> it should use that candidate pair to send its own media. (Secure media i=
s
>> needed to prevent an attacker from tricking the controlled side into
>> sending media to an arbitrary address.) If secure media is not used, the
>> controller could include a new attribute, something like a new
>> PREFERRED-CANDIDATE attribute (or perhaps an updated PRIORITY attribute,
>> set to the max ICE priority), to tell the controlled side which candidat=
e
>> pair should be used.
>>
>> That all sounds good.
>>
>> This would allow the controller to do periodic RTT checks, perhaps using
>> the ICE consent mechanism, and dynamically change the media path as need=
ed.
>>
>> I think we need additional signaling to switch interfaces, because each
>> endpoint needs to participate in the decision (e.g.,
>> draft-wing-mmusic-ice-mobility).  For example, the controlling endpoint
>> might have unmetered Internet access, whereas the other endpoint has fas=
t
>> metered Internet (e.g., LTE) and slower unmetered Internet (e.g., DSL) -=
-
>> but if the controlling endpoint effectively ignores the ICE priorities i=
n
>> favor of round trip time calculations, the controlled endpoint will use
>> LTE.  ICE priorities allows both ends to indicate their preferences.  We
>> might need something more than ICE priorities, too, or a way to strongly
>> say an interface is not preferred (because that interface is metered).
>>
>> 5245 seems to indicate that the controlling endpoint is in the driver's
> seat, as explained in S 2.6:
>
>
>    More fundamentally, however, the prioritization
>    defined by this specification may not yield "optimal" results.  As an
>    example, if the aim is to select low-latency media paths, usage of a
>    relay is a hint that latencies may be higher, but it is nothing more
>    than a hint.  An actual round-trip time (RTT) measurement could be
>    made, and it might demonstrate that a pair with lower priority is
>    actually better than one with higher priority.
>
>
>    Consequently, ICE assigns one of the agents in the role of the
>    CONTROLLING AGENT, and the other of the CONTROLLED AGENT.  The
>    controlling agent gets to nominate which candidate pairs will get
>    used for media amongst the ones that are valid.
>
>
> I agree it would be useful to allow the controlled side to give some hint=
s to the controlling side though.
>
>
> I agree the controlling side is controlling.  But it needs to be
> influenced by the controlled side, or else users will have to manually
> toggle their interfaces on/off to avoid overage charges.  That toggling i=
s
> a p.i.t.a.
>
>
Agreed. The ability to mark an interface as only-if-absolutely-necessary
seems like it would suffice. The controlling side would then only switch to
such a candidate if no other pair was viable, similar to the handling of
backup paths in 6824.

--001a1136b1145ad20f04f475ffd6
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Wed, Mar 12, 2014 at 9:35 AM, Dan Wing <span dir=3D"ltr">&lt;<a =
href=3D"mailto:dwing@cisco.com" target=3D"_blank">dwing@cisco.com</a>&gt;</=
span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div style=3D"word-wrap:break-word"><div><di=
v class=3D"h5"><br><div><div>On Mar 12, 2014, at 9:27 AM, Justin Uberti &lt=
;<a href=3D"mailto:juberti@google.com" target=3D"_blank">juberti@google.com=
</a>&gt; wrote:</div>

<br><blockquote type=3D"cite"><div dir=3D"ltr"><br><div class=3D"gmail_extr=
a"><br><br><div class=3D"gmail_quote">On Tue, Mar 11, 2014 at 4:49 PM, Dan =
Wing <span dir=3D"ltr">&lt;<a href=3D"mailto:dwing@cisco.com" target=3D"_bl=
ank">dwing@cisco.com</a>&gt;</span> wrote:<br>



<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex"><div style=3D"word-wrap:break-word"><br><div><div><div>

<div>On Mar 10, 2014, at 6:21 AM, Justin Uberti &lt;<a href=3D"mailto:juber=
ti@google.com" target=3D"_blank">juberti@google.com</a>&gt; wrote:</div><br=
><blockquote type=3D"cite"><div dir=3D"ltr"><p>In the WG session on Monday,=
 Ari mentioned that the aggressive nomination bug of controller and control=
led not agreeing on the candidate pair to use could be rectified by having =
the controlled side switch its preferred candidate pair to be the one that =
it received secure media on (or if not using controlled media, when the con=
trolling side=E2=80=99s ICE checks finally got through).</p>

<p>I think there is an opportunity here to improve the overall flexibility =
of ICE. Currently, Regular Nomination allows the controller to have a fair =
amount of discretion in choosing which candidate pair it wants to pick; it =
could use metrics such as RTT, or perhaps one of the values mentioned in DI=
SCUSS to make its selection, instead of using the static PRIORITY value. Ag=
gressive Nomination, while faster in initially establishing media, does not=
 afford this same discretion; according to 5245, S 8.1.1.2, ICE uses the hi=
ghest PRIORITY candidate pair. So it would be great if there was a way to a=
llow the controller have the same discretion for choosing the selected cand=
idate pair, while also doing Aggressive Nomination.</p>

<p>I think this can easily be done using Ari=E2=80=99s solution in a genera=
l way. In short, any time secure media packets are received by the controll=
ed side, it should use that candidate pair to send its own media. (Secure m=
edia is needed to prevent an attacker from tricking the controlled side int=
o sending media to an arbitrary address.) If secure media is not used, the =
controller could include a new attribute, something like a new PREFERRED-CA=
NDIDATE attribute (or perhaps an updated PRIORITY attribute, set to the max=
 ICE priority), to tell the controlled side which candidate pair should be =
used.</p>



</div></blockquote></div></div><div>That all sounds good.</div><div><br><bl=
ockquote type=3D"cite"><div dir=3D"ltr"><p>This would allow the controller =
to do periodic RTT checks, perhaps using the ICE consent mechanism, and dyn=
amically change the media path as needed.</p>



</div></blockquote></div></div><div>I think we need additional signaling to=
 switch interfaces, because each endpoint needs to participate in the decis=
ion (e.g., draft-wing-mmusic-ice-mobility). =C2=A0For example, the controll=
ing endpoint might have unmetered Internet access, whereas the other endpoi=
nt has fast metered Internet (e.g., LTE) and slower unmetered Internet (e.g=
., DSL) -- but if the controlling endpoint effectively ignores the ICE prio=
rities in favor of round trip time calculations, the controlled endpoint wi=
ll use LTE. =C2=A0ICE priorities allows both ends to indicate their prefere=
nces. =C2=A0We might need something more than ICE priorities, too, or a way=
 to strongly say an interface is not preferred (because that interface is m=
etered).</div>



<span><font color=3D"#888888"><br></font></span></div></blockquote><div>524=
5 seems to indicate that the controlling endpoint is in the driver&#39;s se=
at, as explained in S 2.6:</div><div><br></div><pre style=3D"font-size:1em;=
margin-top:0px;margin-bottom:0px">

   More fundamentally, however, the prioritization
   defined by this specification may not yield &quot;optimal&quot; results.=
  As an
   example, if the aim is to select low-latency media paths, usage of a
   relay is a hint that latencies may be higher, but it is nothing more
   than a hint.  An actual round-trip time (RTT) measurement could be
   made, and it might demonstrate that a pair with lower priority is
   actually better than one with higher priority.
</pre><pre style=3D"font-size:1em;margin-top:0px;margin-bottom:0px"><br></p=
re><pre style=3D"font-size:1em;margin-top:0px;margin-bottom:0px"><pre style=
=3D"font-size:1em;margin-top:0px;margin-bottom:0px">   Consequently, ICE as=
signs one of the agents in the role of the
   CONTROLLING AGENT, and the other of the CONTROLLED AGENT.  The
   controlling agent gets to nominate which candidate pairs will get
   used for media amongst the ones that are valid.</pre><pre style=3D"font-=
size:1em;margin-top:0px;margin-bottom:0px"><br></pre><pre style=3D"font-siz=
e:1em;margin-top:0px;margin-bottom:0px"><span style=3D"color:rgb(34,34,34);=
font-family:arial;font-size:small;white-space:normal">I agree it would be u=
seful to allow the controlled side to give some hints to the controlling si=
de though.=C2=A0</span></pre>

</pre></div></div></div></blockquote><br></div></div></div><div>I agree the=
 controlling side is controlling. =C2=A0But it needs to be influenced by th=
e controlled side, or else users will have to manually toggle their interfa=
ces on/off to avoid overage charges. =C2=A0That toggling is a p.i.t.a.</div=
>

<span class=3D"HOEnZb"><font color=3D"#888888"><div><br></div></font></span=
></div></blockquote><div><br></div><div>Agreed. The ability to mark an inte=
rface as only-if-absolutely-necessary seems like it would suffice. The cont=
rolling side would then only switch to such a candidate if no other pair wa=
s viable, similar to the handling of backup paths in 6824.</div>

</div><br></div></div>

--001a1136b1145ad20f04f475ffd6--


From nobody Thu Mar 13 06:08:55 2014
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 040FD1A07D9 for <mmusic@ietfa.amsl.com>; Thu, 13 Mar 2014 06:08:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.851
X-Spam-Level: 
X-Spam-Status: No, score=-3.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 D4QPB6sGoUMi for <mmusic@ietfa.amsl.com>; Thu, 13 Mar 2014 06:08:52 -0700 (PDT)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id CF5471A082B for <mmusic@ietf.org>; Thu, 13 Mar 2014 06:08:51 -0700 (PDT)
X-AuditID: c1b4fb25-b7f038e000005d01-06-5321addc71d9
Received: from ESESSHC009.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id B4.BE.23809.CDDA1235; Thu, 13 Mar 2014 14:08:44 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.216]) by ESESSHC009.ericsson.se ([153.88.183.45]) with mapi id 14.02.0387.000; Thu, 13 Mar 2014 14:08:44 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Justin Uberti <juberti@google.com>
Thread-Topic: [MMUSIC] BUNDLE: Q9/Q13: Payload type value re-usage and associating RTP packets with m- line
Thread-Index: Ac89B6OYHyKFgXivSIaXJxW+k4A5DQAnZs6AAAi36ZAAD5b3AAAtofjQ
Date: Thu, 13 Mar 2014 13:08:43 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D212ADA@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D202004@ESESSMB209.ericsson.se> <CAOJ7v-085Zdv7gTKyrU_kCFBB8rdAytE7YjQFeFsUeqWKWoW+g@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1D20A557@ESESSMB209.ericsson.se> <CAOJ7v-2EQ3-qAi7TR_-96i8YB4cD2Xr8taZXsTQZHmtgPs5CrQ@mail.gmail.com>
In-Reply-To: <CAOJ7v-2EQ3-qAi7TR_-96i8YB4cD2Xr8taZXsTQZHmtgPs5CrQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.18]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrBLMWRmVeSWpSXmKPExsUyM+Jvje6dtYrBBgsvWlpsnSpkMXX5YxYH Jo8Fm0o9liz5yRTAFMVlk5Kak1mWWqRvl8CVcb73LUvBDe6KFf2vGRsYN3B3MXJySAiYSJy/ uJ0dwhaTuHBvPVsXIxeHkMAhRomO5m3MEM4SRonNk7cxdTFycLAJWEh0/9MGaRARUJN4OGsX K0iYWUBd4uriIJCwsECOxJMpB9ghSnKBqjeyQthuEtfvH2UCsVkEVCWu3b0BFucV8JWYevcD 1N75TBLrf/exgCQ4BQIlpv//yQhiMwId9/3UGrBmZgFxiVtP5jNBHC0gsWTPeWYIW1Ti5eN/ rBC2osTHV/sYIW7TlFi/Sx+iVVFiSvdDdoi9ghInZz5hmcAoNgvJ1FkIHbOQdMxC0rGAkWUV I3tuYmZOernRJkZgbBzc8lt1B+OdcyKHGKU5WJTEeT+8dQ4SEkhPLEnNTk0tSC2KLyrNSS0+ xMjEwSnVwBi1ZNvh5JsJuVv07nGtvyx9cgOrwfPdh7lXmXbZ6ebZ2585K/Hma6Rniu0s3Y3H AkVa/Bf/F1F+Yy4ay8ux8IdSTbhD9h2h1QZ5R/y2HdrkJlVjs2It79nab3MTYhen3ixyW/Rn +YHUo1pVAXGFTmqW2T0L+jon8Abnv9I0X+uu6XWg5ktmrRJLcUaioRZzUXEiAA4Af8ZbAgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/9gQ8BpUz68qW6vtYADp3c3Thlw8
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] BUNDLE: Q9/Q13: Payload type value re-usage and associating RTP packets with m- line
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: Thu, 13 Mar 2014 13:08:54 -0000

SGkgSnVzdGluLA0KDQo+Pj5BcyBJIHVuZGVyc3RhbmQgaXQsIHRoZSAncmVjZWl2ZXItaWQnIHdp
bGwgbm90IGlkZW50aWZ5IGEgQlVORExFIGdyb3VwLCBidXQgcmF0aGVyIGEgbT0gc2VjdGlvbiBv
ciBwYWNrZXQgc3RyZWFtLg0KPj5Db3JyZWN0Lg0KPj4NCj4+RG8geW91IHRoaW5rIHRoZSB0ZXh0
IGluZGljYXRlcyBvdGhlcndpc2U/DQo+Pg0KPkZyb20gdGhlIHRleHQgYmVsb3csIGl0IGFwcGVh
cnMgdGhhdCB0aGUgcmVjZWl2ZXItaWQgaXMgYXNzb2NpYXRlZCB3aXRoIGEgQlVORExFIGdyb3Vw
Lg0KPg0KPklmIGFuIGVuZHBvaW50IGFjY2VwdHMgYSBCVU5ETEUgZ3JvdXAsIGl0IE1VU1QgaW5z
ZXJ0IHRoZSDigJxyZWNlaXZlci1pZOKAnSB2YWx1ZSBpbiB0aGUgYXNzb2NpYXRlZCBSVFAgcGFj
a2V0cywgYXNzb2NpYXRlZCB3aXRoIHRoZSBCVU5ETEUgZ3JvdXAsIHNlbnQgdG93YXJkcyB0aGUg
cmVtb3RlIGVuZHBvaW50LCBhcyBkZXNjcmliZWQgaW4gW3JlY2VpdmVyLWlkLXJlZmVyZW5jZS10
by1iZS1hZGRlZF0uwqANCj4NCj5TaW5jZSB0aGUgcmVjZWl2ZXItaWQgbWVjaGFuaXNtIGlzIGlu
ZGVwZW5kZW50IG9mIEJVTkRMRSwgaXQncyBub3QgY2xlYXIgdG8gbWUgdGhhdCBCVU5ETEUgbmVl
ZHMgdG8gc2F5IGFueXRoaW5nIGFib3V0IHRoaXMsIG90aGVyIHRoYW4gdGhhdCB0aGUgcmVjZWl2
ZXItaWQgbWVjaGFuaXNtIE1VU1QgYmUgdXNlZC4NCg0KV2VsbCwgaXQgTVVTVCBvbmx5IGJlIHVz
ZWQgd2l0aCBSVFAgcGFja2V0cyBhc3NvY2lhdGVkIHdpdGggbS0gbGluZXMgd2l0aGluIGEgQlVO
RExFIGdyb3VwLiBJZiBhbiBtLSBsaW5lIGlzIG5vdCB3aXRoaW4gYSBCVU5ETEUgZ3JvdXAsIEkg
ZG9uJ3QgdGhpbmsgQlVORExFIG5lZWRzIHRvIG1hbmRhdGUgdXNhZ2Ugb2YgdGhlIHJlY2VpdmVy
LWlkIG1lY2hhbmlzbSBmb3IgUlRQIHBhY2tldHMgYXNzb2NpYXRlZCB3aXRoIHRoYXQgbS0gbGlu
ZS4NCg0KQnV0LCBJIGFncmVlIHRoZSB0ZXh0IHlvdSByZWZlcnJlZCB0byBpcyBhIGxpdHRsZSB1
bmNsZWFyLCBzbyBJJ2xsIHRyeSB0byBpbXByb3ZlIGl0Lg0KDQpSZWdhcmRzLA0KDQpDaHJpc3Rl
cg0KDQoNCg==


From nobody Thu Mar 13 06:33:07 2014
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 63D5F1A0848 for <mmusic@ietfa.amsl.com>; Thu, 13 Mar 2014 06:33:05 -0700 (PDT)
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 LDnejkv4qTAY for <mmusic@ietfa.amsl.com>; Thu, 13 Mar 2014 06:33:04 -0700 (PDT)
Received: from sessmg20.mgmt.ericsson.se (sessmg20.ericsson.net [193.180.251.50]) by ietfa.amsl.com (Postfix) with ESMTP id 348FD1A096E for <mmusic@ietf.org>; Thu, 13 Mar 2014 06:33:03 -0700 (PDT)
X-AuditID: c1b4fb32-b7f4c8e0000012f5-7b-5321b3886bf2
Received: from ESESSHC001.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg20.mgmt.ericsson.se (Symantec Mail Security) with SMTP id 64.6D.04853.883B1235; Thu, 13 Mar 2014 14:32:57 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.216]) by ESESSHC001.ericsson.se ([153.88.183.21]) with mapi id 14.02.0387.000; Thu, 13 Mar 2014 14:32:56 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Christian Groves <Christian.Groves@nteczone.com>, Salvatore Loreto <salvatore.loreto@ericsson.com>
Thread-Topic: [MMUSIC] SCTP AppID
Thread-Index: AQHPOS8Nc6UA2CfhSkqx8lJA4yEdXprT2zKAgAAc8ICAAAbRgIAACYyAgAsGBzA=
Date: Thu, 13 Mar 2014 13:32:55 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D212B7E@ESESSMB209.ericsson.se>
References: <53185B8E.2070808@nteczone.com> <C8EB64C0-3140-477C-9373-BD36B4B1A64B@ericsson.com> <53187415.2000108@nteczone.com> <C1D662DF-E3E3-45CD-991F-8090CD7130E0@ericsson.com> <531881CF.2010105@nteczone.com>
In-Reply-To: <531881CF.2010105@nteczone.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.18]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrPLMWRmVeSWpSXmKPExsUyM+JvjW7nZsVgg8U32Sy+vG9ksZi6/DGL A5PHkiU/mTxWnJ/JEsAUxWWTkpqTWZZapG+XwJVx8dNZloKzzBV/p7WyNzC+Z+pi5OSQEDCR uN35ix3CFpO4cG89WxcjF4eQwAlGida955ggnCWMEnOu7wVyODjYBCwkuv9pgzSICGRItJ65 xwZiMwtoSkzofgJmCwsoSBx/fY8ZokZR4vyl+SwQtp/EwrMXwGwWAVWJL//+gNXzCvhKTJ27 iR1i121GiV/L34JdxymgI9H+7SqYzQh03fdTa5gglolL3HoyH+oDAYkle84zQ9iiEi8f/2OF sBUlPr7axwhRryOxYPcnqEO1JZYtfM0MsVhQ4uTMJywTGMVmIRk7C0nLLCQts5C0LGBkWcUo WZxaXJybbmSgl5ueW6KXWpSZXFycn6dXnLqJERhJB7f8NtrBeHKP/SFGaQ4WJXHe66w1QUIC 6YklqdmpqQWpRfFFpTmpxYcYmTg4pRoY9Xfxi/benRbfI9n13/DRlci4d3z3LQv9/p4WOVz5 zO7jlr3+7eJGeTElBzvljXe5ei/iurJS7I7rTecT7y4WdfVt2lxnpuUuXOPRIyzFtaNEvsPi UxLXN8YfvAUBj7eIp905ZHnxI8scmU3W8yP+/uFjUPtjIRr46Ort/VM0z6y1yw3tP8GqxFKc kWioxVxUnAgAikyzmHICAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/PQZdLkDYZ4Pk8SaDEgbjPScZ1Fo
Cc: mmusic mailing list <mmusic@ietf.org>
Subject: Re: [MMUSIC] SCTP AppID
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: Thu, 13 Mar 2014 13:33:05 -0000

Hi Christian,

> Do you have an answer for the second part of the previous email?
> i.e One thing I'm still missing is how you specify multiple app/alpns (wh=
atever we're calling them) being used in a single SCTP association, without=
 using datachannel?

My understanding is that it is no longer possible. You can only assign *one=
* sctpmap attribute (e.g. indicating webrtc-datachannel) to any given SCTPo=
DTLS m- line.

Regards,

Christer


From nobody Thu Mar 13 07:25:12 2014
Return-Path: <pkyzivat@alum.mit.edu>
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 6E6E31A09D8 for <mmusic@ietfa.amsl.com>; Thu, 13 Mar 2014 07:25:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] 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 WOFaupInpYNC for <mmusic@ietfa.amsl.com>; Thu, 13 Mar 2014 07:25:08 -0700 (PDT)
Received: from qmta10.westchester.pa.mail.comcast.net (qmta10.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:17]) by ietfa.amsl.com (Postfix) with ESMTP id D43F91A09C7 for <mmusic@ietf.org>; Thu, 13 Mar 2014 07:25:07 -0700 (PDT)
Received: from omta05.westchester.pa.mail.comcast.net ([76.96.62.43]) by qmta10.westchester.pa.mail.comcast.net with comcast id czs21n0030vyq2s5A2R1rY; Thu, 13 Mar 2014 14:25:01 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta05.westchester.pa.mail.comcast.net with comcast id d2R01n00g3ZTu2S3R2R1Nx; Thu, 13 Mar 2014 14:25:01 +0000
Message-ID: <5321BFBC.30304@alum.mit.edu>
Date: Thu, 13 Mar 2014 10:25:00 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: mmusic@ietf.org
References: <53185B8E.2070808@nteczone.com> <C8EB64C0-3140-477C-9373-BD36B4B1A64B@ericsson.com> <53187415.2000108@nteczone.com> <C1D662DF-E3E3-45CD-991F-8090CD7130E0@ericsson.com> <531881CF.2010105@nteczone.com> <7594FB04B1934943A5C02806D1A2204B1D212B7E@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D212B7E@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1394720701; bh=rQqZzSzXT+lLSwQTc7PJtJLXTWa+VxNmoz96Wn3nToE=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=BpS7BO+12Gbjgp6MlsR0vMBsW6SX2MVL/qYhC87vFvuKDvK5unaZdncYdRONuaW6a 9bI8/pgzg+roQ03Bzo354yGzVijZX8DTggOMYchsSZm57Su6L3hG3RlH/mVZfYjV/A UPglD9xRQ4XnISjvXQXCRbVwGLibbhFvEGopXSREh6ok9XEO3ynsYjkjp/b/rSjv87 qLK5dCpnf/lxX7+qrpNOctHXo17wHRoeQz8Aqbn5G2yw3IZFU+sym+aU0+uykd+3bf Xc8f2XRVntxXI8LFbCxNva2l7/AyHOpAL+OfI7AMr4hh/MMWeNr7CheUUTcFt1ww05 od1l37dDoqpxQ==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/rA5TwUZgWoaj29CnZkT4InvwENc
Subject: Re: [MMUSIC] SCTP AppID
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: Thu, 13 Mar 2014 14:25:09 -0000

On 3/13/14 9:32 AM, Christer Holmberg wrote:
> Hi Christian,
>
>> Do you have an answer for the second part of the previous email?
>> i.e One thing I'm still missing is how you specify multiple app/alpns (whatever we're calling them) being used in a single SCTP association, without using datachannel?
>
> My understanding is that it is no longer possible. You can only assign *one* sctpmap attribute (e.g. indicating webrtc-datachannel) to any given SCTPoDTLS m- line.

I never understood this question. This is describing the use of the 
association as a whole, not not a particular channel.

	Thanks,
	Paul


From nobody Thu Mar 13 09:57:20 2014
Return-Path: <martin.thomson@gmail.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 7A0771A0A19 for <mmusic@ietfa.amsl.com>; Thu, 13 Mar 2014 09:57:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 nZwwLtIvSl46 for <mmusic@ietfa.amsl.com>; Thu, 13 Mar 2014 09:57:14 -0700 (PDT)
Received: from mail-wg0-x231.google.com (mail-wg0-x231.google.com [IPv6:2a00:1450:400c:c00::231]) by ietfa.amsl.com (Postfix) with ESMTP id B48C31A088B for <mmusic@ietf.org>; Thu, 13 Mar 2014 09:57:13 -0700 (PDT)
Received: by mail-wg0-f49.google.com with SMTP id a1so1124871wgh.20 for <mmusic@ietf.org>; Thu, 13 Mar 2014 09:57:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=SitWo8Cq1MKip8PCHlR3MOZLZTb2fc4jBhty3o+TWZQ=; b=jbrTY1lQCuAOFBElQhkFHFYtp7NSYM8Bsg7yWkJxAvrwCfL/PXp9GUzaIjkmZ1upd3 vbDTQu+WnrKgXV0jykQPbR7tFVrW2mL8EPibWow3wvpv8AJbKuFCDH1tsrUpxgjRKMH2 raODKSfRUm4vaMuw3xPmHXvV4G95XdttrEwDHOaEqG5WqrPH3z9AZs24vQzJ5EpDorGz VLY4J9KqxYJcuN0U/877uaJr1BhFi8mJp9IgPh9mNQk+ZtQ1im8PQYXFqUZvJV79HJ06 NtQR7TyCnJ4X6iF9iI1bXhfYCr6+A4UCmNjVCwchYWY53xMXOICgpnppjwxCcpYC96U5 UDWQ==
MIME-Version: 1.0
X-Received: by 10.180.77.129 with SMTP id s1mr2442585wiw.56.1394729826666; Thu, 13 Mar 2014 09:57:06 -0700 (PDT)
Received: by 10.227.10.196 with HTTP; Thu, 13 Mar 2014 09:57:06 -0700 (PDT)
In-Reply-To: <CAOJ7v-3Z=x=1kDuB3LCu3g1gZ6M4BytrwbJ3FJnjOpAy-um6PQ@mail.gmail.com>
References: <CAOJ7v-3oi-Qtsk6qiPVsAUfzEQsvgt4h6RhgfKDNUv_-47wpOA@mail.gmail.com> <BFFAE2A7-089D-452F-867E-BEF622BEFB77@cisco.com> <CAOJ7v-0d1bng-LHkdZ+J3Swdoic+zOF73JVfK464N0n4fY9=fw@mail.gmail.com> <9450C3A0-9509-4D1E-8C6C-54B884086B38@cisco.com> <CAOJ7v-3Z=x=1kDuB3LCu3g1gZ6M4BytrwbJ3FJnjOpAy-um6PQ@mail.gmail.com>
Date: Thu, 13 Mar 2014 09:57:06 -0700
Message-ID: <CABkgnnWSAdcQ+xbFc7TqMMaRbwWy+=APzSNp_nXAQ1HCDh2E3A@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Justin Uberti <juberti@google.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/KjF0NW1CRAc2t8HqvgGq78bFMeI
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Dan Wing <dwing@cisco.com>
Subject: Re: [MMUSIC] Generalizing the aggressive nomination bugfix
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: Thu, 13 Mar 2014 16:57:15 -0000

On 12 March 2014 22:11, Justin Uberti <juberti@google.com> wrote:
> Agreed. The ability to mark an interface as only-if-absolutely-necessary
> seems like it would suffice. The controlling side would then only switch to
> such a candidate if no other pair was viable, similar to the handling of
> backup paths in 6824.

That might be a useful function to exploit to shift traffic away from
relays as well.


From nobody Thu Mar 13 09:59:20 2014
Return-Path: <martin.thomson@gmail.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 1F6BC1A0A4D for <mmusic@ietfa.amsl.com>; Thu, 13 Mar 2014 09:59:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 nSLPSkWzt3qq for <mmusic@ietfa.amsl.com>; Thu, 13 Mar 2014 09:59:18 -0700 (PDT)
Received: from mail-wg0-x230.google.com (mail-wg0-x230.google.com [IPv6:2a00:1450:400c:c00::230]) by ietfa.amsl.com (Postfix) with ESMTP id AC53D1A0A23 for <mmusic@ietf.org>; Thu, 13 Mar 2014 09:59:17 -0700 (PDT)
Received: by mail-wg0-f48.google.com with SMTP id l18so1123263wgh.19 for <mmusic@ietf.org>; Thu, 13 Mar 2014 09:59:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=0T8k+J2mP08gCMqFm/tW+oAghhz9w5gams9ztYKKiac=; b=Kne5RpWZ+6FqLajCuHk1YarwdQO96tSmlvjMvqrNH3zqAwgH7CAK7xMggeTnuaH5PP bkvbGnpgudfgDjR9cxxe944UnTl+p0nKQNjA2xUnE5Vb/10INtBuMigR4EuJH5NVvScS PV9Ir/3G0TH2r9wfzRHmFhp5T9gd1cJ9sqKEirMXsqzEyEr5LBSqc5S7rxs7i7nzifpV b1u2AIWlLy4MCe6ztGTUPJrwBUHcfOS4H+FVVSLW2erq3apJPmxxdYNbaJFs2zd6Huxj xnmlrDElHkkxDVJLhris3ELSk4LtuDc8vnPhY3j07apFgFLIvpV0gmlIUSK+PN8uRL7r Suhw==
MIME-Version: 1.0
X-Received: by 10.180.77.129 with SMTP id s1mr2449652wiw.56.1394729950761; Thu, 13 Mar 2014 09:59:10 -0700 (PDT)
Received: by 10.227.10.196 with HTTP; Thu, 13 Mar 2014 09:59:10 -0700 (PDT)
In-Reply-To: <5320CD63.8080904@alum.mit.edu>
References: <53185B8E.2070808@nteczone.com> <C8EB64C0-3140-477C-9373-BD36B4B1A64B@ericsson.com> <53187415.2000108@nteczone.com> <C1D662DF-E3E3-45CD-991F-8090CD7130E0@ericsson.com> <CABkgnnWOVf-72jeLbo74dbpxwhiYwgOjsfte2Cx3Voi_YRxdTg@mail.gmail.com> <5319A928.8040703@alvestrand.no> <CABkgnnVghjLVBPQiYwjgH1uVac1Qm5MwWj09e1uk90shVjss3w@mail.gmail.com> <531DAF79.6070505@alvestrand.no> <5320CD63.8080904@alum.mit.edu>
Date: Thu, 13 Mar 2014 09:59:10 -0700
Message-ID: <CABkgnnWbGXaB1gJt18KqFBQLrZhhDorZ=LHK_5CiwRzKHsiFBw@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/210aCk-wu5-Xa8O1nLJifhctqhY
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] SCTP AppID
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: Thu, 13 Mar 2014 16:59:19 -0000

On 12 March 2014 14:10, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
> I think that means they are defined to be used over a reliable byte single
> byte stream protocol.

I don't believe that this was ever the intent.  The abstract mentions
UDP explicitly, but I'll concede that DTLS isn't called out.  I'll
send the authors a note, maybe they can add a ref.


From nobody Thu Mar 13 10:38:29 2014
Return-Path: <pkyzivat@alum.mit.edu>
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 4BFC31A072C for <mmusic@ietfa.amsl.com>; Thu, 13 Mar 2014 10:38:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] 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 DxyC41bRWgIG for <mmusic@ietfa.amsl.com>; Thu, 13 Mar 2014 10:38:25 -0700 (PDT)
Received: from qmta01.westchester.pa.mail.comcast.net (qmta01.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:16]) by ietfa.amsl.com (Postfix) with ESMTP id 4B0A11A0492 for <mmusic@ietf.org>; Thu, 13 Mar 2014 10:38:25 -0700 (PDT)
Received: from omta20.westchester.pa.mail.comcast.net ([76.96.62.71]) by qmta01.westchester.pa.mail.comcast.net with comcast id d5Ss1n0051YDfWL515eJmH; Thu, 13 Mar 2014 17:38:18 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta20.westchester.pa.mail.comcast.net with comcast id d5eJ1n0083ZTu2S3g5eJ0J; Thu, 13 Mar 2014 17:38:18 +0000
Message-ID: <5321ED0A.1010800@alum.mit.edu>
Date: Thu, 13 Mar 2014 13:38:18 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Martin Thomson <martin.thomson@gmail.com>
References: <53185B8E.2070808@nteczone.com>	<C8EB64C0-3140-477C-9373-BD36B4B1A64B@ericsson.com>	<53187415.2000108@nteczone.com>	<C1D662DF-E3E3-45CD-991F-8090CD7130E0@ericsson.com>	<CABkgnnWOVf-72jeLbo74dbpxwhiYwgOjsfte2Cx3Voi_YRxdTg@mail.gmail.com>	<5319A928.8040703@alvestrand.no>	<CABkgnnVghjLVBPQiYwjgH1uVac1Qm5MwWj09e1uk90shVjss3w@mail.gmail.com>	<531DAF79.6070505@alvestrand.no>	<5320CD63.8080904@alum.mit.edu> <CABkgnnWbGXaB1gJt18KqFBQLrZhhDorZ=LHK_5CiwRzKHsiFBw@mail.gmail.com>
In-Reply-To: <CABkgnnWbGXaB1gJt18KqFBQLrZhhDorZ=LHK_5CiwRzKHsiFBw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1394732298; bh=2sIpBQH49H/PEMkFZ9XnEK9DBbOtmDdTluN2wsdAv7M=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=k6LoCP+EC8XW+tuembn0D/ef3pxwjyqMyLPUwWmv3C6kbepk8vYQm5U5vxzg/HDIk nNCveDVfSziqQaB/o8iY3UjWAXgDa1ztP6ZNacxWLaVLRkDo1qyjavvZVQTI2usAP+ sfmEjKfx0BpsOakXAZp3FATvhT72mZ3cKUxrBoM1FIoLv4KtJsLJRO6QjzRfVawYaU OdHdq2ZqzAetBu4goA+5dCJoAbr2GbyxE6lahL5Nqo51QDdLy5ZfA/1RYJf2TeU9KP 2AHKJsice5rnNN1bzcx58mdLFaCyc7IqeNNaMscPyCtY08t17ZT9U6hMdImzdFOm8a dIX63W+PGoBhA==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/AD18-_6xem4E1yyZmsYQqPZQ6LA
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] SCTP AppID
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: Thu, 13 Mar 2014 17:38:26 -0000

On 3/13/14 12:59 PM, Martin Thomson wrote:
> On 12 March 2014 14:10, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
>> I think that means they are defined to be used over a reliable byte single
>> byte stream protocol.
>
> I don't believe that this was ever the intent.  The abstract mentions
> UDP explicitly, but I'll concede that DTLS isn't called out.  I'll
> send the authors a note, maybe they can add a ref.

I don't see any reference to UDP.

Based on my *brief* skim of the draft, it appears to me that the primary 
intent is to identify *alternatives*. That would presumably mean things 
work over the same lower layer and that do essentially the same job.

The initial protocols registered by the draft are http/1.1, http/2.1, 
spdy/1, spdy/2, spdy/3. WebRtc Data Channels aren't an alternative to those.

IMO we would be better off with a new registry.

	Thanks,
	Paul



From nobody Thu Mar 13 11:03:03 2014
Return-Path: <martin.thomson@gmail.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 62DAE1A0A54 for <mmusic@ietfa.amsl.com>; Thu, 13 Mar 2014 11:03:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 mragqUusx19L for <mmusic@ietfa.amsl.com>; Thu, 13 Mar 2014 11:02:59 -0700 (PDT)
Received: from mail-we0-x232.google.com (mail-we0-x232.google.com [IPv6:2a00:1450:400c:c03::232]) by ietfa.amsl.com (Postfix) with ESMTP id E3CDF1A0A4B for <mmusic@ietf.org>; Thu, 13 Mar 2014 11:02:58 -0700 (PDT)
Received: by mail-we0-f178.google.com with SMTP id u56so1187223wes.9 for <mmusic@ietf.org>; Thu, 13 Mar 2014 11:02:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=pXGoeN1q+pNWTIfVYrfFvADQGJU5dVuDU5zo3NRwGNw=; b=Th4lDY0HfHDOfHVU7XeLeDTV+WQ2AZP8ncE6oh3bQzEQxSvrN55KDG+jb5eHZ0tmQx bJl+Sy9C9jGgsr3doRwHxJecqMS94BlyIuX7lPyhNWegmtPcFYDSVl9OlcxqLn7dPHEg AujQTX7tYxZPv1mfxGYDlV8g0UwAke716CQ1BB1jGe6cbivUIzXW8IjYvop4j40vfRsv /YBaonnFBptBPYbRnw96vln3tc/rYgoFVg4zB9Cx7elEjgJnYcHS2XSXPl/MaV9i6X6v zqfeyAzMnm61x1wvrPuQCBrmivLkcQHTRZPe70elUBfBbnnzxCNA46DuA2hdhPN0bccD vtNQ==
MIME-Version: 1.0
X-Received: by 10.180.185.197 with SMTP id fe5mr2697736wic.56.1394733771944; Thu, 13 Mar 2014 11:02:51 -0700 (PDT)
Received: by 10.227.10.196 with HTTP; Thu, 13 Mar 2014 11:02:51 -0700 (PDT)
In-Reply-To: <5321ED0A.1010800@alum.mit.edu>
References: <53185B8E.2070808@nteczone.com> <C8EB64C0-3140-477C-9373-BD36B4B1A64B@ericsson.com> <53187415.2000108@nteczone.com> <C1D662DF-E3E3-45CD-991F-8090CD7130E0@ericsson.com> <CABkgnnWOVf-72jeLbo74dbpxwhiYwgOjsfte2Cx3Voi_YRxdTg@mail.gmail.com> <5319A928.8040703@alvestrand.no> <CABkgnnVghjLVBPQiYwjgH1uVac1Qm5MwWj09e1uk90shVjss3w@mail.gmail.com> <531DAF79.6070505@alvestrand.no> <5320CD63.8080904@alum.mit.edu> <CABkgnnWbGXaB1gJt18KqFBQLrZhhDorZ=LHK_5CiwRzKHsiFBw@mail.gmail.com> <5321ED0A.1010800@alum.mit.edu>
Date: Thu, 13 Mar 2014 11:02:51 -0700
Message-ID: <CABkgnnUdBCMrOVAKY0rFFXPcSR1L4_yg1KLoxSmj2AmLPw7e2A@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/JjpXFsO_Pbv26hm33c65IxNXkEM
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] SCTP AppID
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: Thu, 13 Mar 2014 18:03:00 -0000

On 13 March 2014 10:38, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
> I don't see any reference to UDP.

In the Abstract:
   For instances in which the TLS connection is established over a well
   known TCP or UDP port not associated with the desired application
   layer protocol, this extension allows the application layer to
   negotiate which protocol will be used within the TLS connection.


From nobody Thu Mar 13 11:34:58 2014
Return-Path: <pkyzivat@alum.mit.edu>
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 F19D81A0A40 for <mmusic@ietfa.amsl.com>; Thu, 13 Mar 2014 11:34:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] 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 mvhLrUPz3aqM for <mmusic@ietfa.amsl.com>; Thu, 13 Mar 2014 11:34:56 -0700 (PDT)
Received: from QMTA11.westchester.pa.mail.comcast.net (qmta11.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:211]) by ietfa.amsl.com (Postfix) with ESMTP id E49B01A0A33 for <mmusic@ietf.org>; Thu, 13 Mar 2014 11:34:51 -0700 (PDT)
Received: from omta24.westchester.pa.mail.comcast.net ([76.96.62.76]) by QMTA11.westchester.pa.mail.comcast.net with comcast id d1hq1n0031ei1Bg5B6al0U; Thu, 13 Mar 2014 18:34:45 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta24.westchester.pa.mail.comcast.net with comcast id d6al1n0013ZTu2S3k6alh7; Thu, 13 Mar 2014 18:34:45 +0000
Message-ID: <5321FA45.1060800@alum.mit.edu>
Date: Thu, 13 Mar 2014 14:34:45 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Martin Thomson <martin.thomson@gmail.com>
References: <53185B8E.2070808@nteczone.com>	<C8EB64C0-3140-477C-9373-BD36B4B1A64B@ericsson.com>	<53187415.2000108@nteczone.com>	<C1D662DF-E3E3-45CD-991F-8090CD7130E0@ericsson.com>	<CABkgnnWOVf-72jeLbo74dbpxwhiYwgOjsfte2Cx3Voi_YRxdTg@mail.gmail.com>	<5319A928.8040703@alvestrand.no>	<CABkgnnVghjLVBPQiYwjgH1uVac1Qm5MwWj09e1uk90shVjss3w@mail.gmail.com>	<531DAF79.6070505@alvestrand.no>	<5320CD63.8080904@alum.mit.edu>	<CABkgnnWbGXaB1gJt18KqFBQLrZhhDorZ=LHK_5CiwRzKHsiFBw@mail.gmail.com>	<5321ED0A.1010800@alum.mit.edu> <CABkgnnUdBCMrOVAKY0rFFXPcSR1L4_yg1KLoxSmj2AmLPw7e2A@mail.gmail.com>
In-Reply-To: <CABkgnnUdBCMrOVAKY0rFFXPcSR1L4_yg1KLoxSmj2AmLPw7e2A@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1394735685; bh=102rH063sqnKf0t/+B/mcjb2n/u0BY3+mkFg5O59lSs=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=GPWxYaZrYl9vT08wYzgz62kSigjhnspq0h4NcnQ7+5b7HYZ6W7lrKQqhjIocDM+OT 5PSNeGh+tydJG3K58EW3/L831a9KQa6o3TkU0r2JD8nrfYiUcBwfGhZseQTRop9SB3 PpN9rTZuAiJuuBNt3a+XoXBPYMfbHFdEdLz0Lkmna4IHQihYgPNNrrjIdTKpQoAdwD 5yxizgMSuzIOhpEJaGw7xwQX6clQ449t5grB7HCnxI2pPuXzKbhIn61xmZnbPiW9Ia q7GOsMeo6mwkav1+EeggGWlc4Gv8FAl2ZDGNeh7JVwH1YNErZYbXAWK52VHWjy2TH+ CzBfxVEua0Q/Q==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/ajb5aLTPfCmVfQYfdfOkCVzXJsk
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] SCTP AppID
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: Thu, 13 Mar 2014 18:34:57 -0000

On 3/13/14 2:02 PM, Martin Thomson wrote:
> On 13 March 2014 10:38, Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:
>> I don't see any reference to UDP.
>
> In the Abstract:
>     For instances in which the TLS connection is established over a well
>     known TCP or UDP port not associated with the desired application
>     layer protocol, this extension allows the application layer to
>     negotiate which protocol will be used within the TLS connection.
>

Oh, sorry - I was looking at an older version.

	Paul


From cmatsuura@vivint.com  Thu Mar 13 16:22:27 2014
Return-Path: <cmatsuura@vivint.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 E6A9E1A0783 for <mmusic@ietfa.amsl.com>; Thu, 13 Mar 2014 16:22:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.002
X-Spam-Level: 
X-Spam-Status: No, score=-0.002 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, SPF_PASS=-0.001] autolearn=ham
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 jrHknJA2HQbO for <mmusic@ietfa.amsl.com>; Thu, 13 Mar 2014 16:22:26 -0700 (PDT)
Received: from inferno.apxalarm.com (inferno.apxalarm.com [65.181.58.40]) by ietfa.amsl.com (Postfix) with ESMTP id 608181A06EE for <mmusic@ietf.org>; Thu, 13 Mar 2014 16:22:26 -0700 (PDT)
Received: from MAILBOX.APEX.Local ([192.168.0.1]) by mail01.APEX.Local ([10.2.0.11]) with mapi; Thu, 13 Mar 2014 17:22:19 -0600
From: Craig Matsuura <cmatsuura@vivint.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Date: Thu, 13 Mar 2014 17:22:18 -0600
Thread-Topic: RTSP questions in regards to the control channel socket
Thread-Index: Ac8/ExPLGQBYTesrS7Wb7tzatid3Vw==
Message-ID: <53223DAA.4040107@vivint.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/w3cxmXwWXSq7v0fkuNZWmNZnK-c
Subject: [MMUSIC] RTSP questions in regards to the control channel socket
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: Thu, 13 Mar 2014 23:28:54 -0000

Hi this is my first time posting here.  I have a basic question about=20
how a RTSP server should handled a connect and disconnect for what I am=20
calling the control channel (connection or transport). The control=20
channel (please correct me) is what sends the DESCRIBE, SETUP, OPTIONS,=20
PLAY commands to the RTSP SERVER.

Should a server treat the first DESCRIBE connection as its session. So=20
in the case where a socket connects to a RTSP server and sends a=20
DESCRIBE, is disconnected either by the client or some failure on the=20
server should the following SETUP succeed?

Also if using a RTSP Proxy and in the same scenario, but after the=20
DESCRIBE and closing of the socket a new socket is open to send an=20
OPTIONS (for keepalive) should the following SETUP succeed?

 From what I understood from the RFC2326 Section 1.7 RTSP State, it=20
should not matter how many connections are used to control the RTSP Stream.

1. Control Socket is not prevent a client from connecting and=20
disconnecting to send Transport commands.
2. The keep-alive for a session should not start until a SETUP command,=20
which can optional report the timeout for the session.

Thanks,
Craig=


From nobody Fri Mar 14 00:29:53 2014
Return-Path: <Christian.Groves@nteczone.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 C86181A0097 for <mmusic@ietfa.amsl.com>; Fri, 14 Mar 2014 00:29:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.001
X-Spam-Level: 
X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[BAYES_40=-0.001] autolearn=ham
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 VC_yzvlOsFXP for <mmusic@ietfa.amsl.com>; Fri, 14 Mar 2014 00:29:48 -0700 (PDT)
Received: from cserver5.myshophosting.com (cserver5.myshophosting.com [175.107.161.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA7B21A006B for <mmusic@ietf.org>; Fri, 14 Mar 2014 00:29:47 -0700 (PDT)
Received: from 212-147-18-59.fix.access.vtx.ch ([212.147.18.59]:61737 helo=[127.0.0.1]) by cserver5.myshophosting.com with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from <Christian.Groves@nteczone.com>) id 1WOMYk-00073c-W7 for mmusic@ietf.org; Fri, 14 Mar 2014 18:29:39 +1100
Message-ID: <5322AFD9.8090108@nteczone.com>
Date: Fri, 14 Mar 2014 18:29:29 +1100
From: Christian Groves <Christian.Groves@nteczone.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: mmusic@ietf.org
References: <53185B8E.2070808@nteczone.com> <C8EB64C0-3140-477C-9373-BD36B4B1A64B@ericsson.com> <53187415.2000108@nteczone.com> <C1D662DF-E3E3-45CD-991F-8090CD7130E0@ericsson.com> <531881CF.2010105@nteczone.com> <7594FB04B1934943A5C02806D1A2204B1D212B7E@ESESSMB209.ericsson.se> <5321BFBC.30304@alum.mit.edu>
In-Reply-To: <5321BFBC.30304@alum.mit.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - cserver5.myshophosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - nteczone.com
X-Get-Message-Sender-Via: cserver5.myshophosting.com: authenticated_id: christian.groves@nteczone.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/DAmx5KR_i_PnD2W6VNNf4Z4B1JM
Subject: Re: [MMUSIC] SCTP AppID
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: Fri, 14 Mar 2014 07:29:51 -0000

On 14/03/2014 1:25 AM, Paul Kyzivat wrote:
> On 3/13/14 9:32 AM, Christer Holmberg wrote:
>> Hi Christian,
>>
>>> Do you have an answer for the second part of the previous email?
>>> i.e One thing I'm still missing is how you specify multiple 
>>> app/alpns (whatever we're calling them) being used in a single SCTP 
>>> association, without using datachannel?
>>
>> My understanding is that it is no longer possible. You can only 
>> assign *one* sctpmap attribute (e.g. indicating webrtc-datachannel) 
>> to any given SCTPoDTLS m- line.
>
> I never understood this question. This is describing the use of the 
> association as a whole, not not a particular channel.
[CNG] I didn't mention channel. I am talking about the association as a 
whole. The sctpmap attribute indicates what app is in the SCTP 
association. The current syntax only allows one app. So basically I can 
run "foo" over an SCTP association natively but as soon as I want to run 
"foo" and "bar" over an SCTP association I need to use the 
webrtc-datachannel protocol.

I just wanted to check that behavior was planned not just as an 
unplanned consequence of updated the draft version.

Regards, Christian

>
>     Thanks,
>     Paul
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>


From nobody Fri Mar 14 01:36:12 2014
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 136611A00A6 for <mmusic@ietfa.amsl.com>; Fri, 14 Mar 2014 01:36:03 -0700 (PDT)
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 3gytiCr_FAVj for <mmusic@ietfa.amsl.com>; Fri, 14 Mar 2014 01:36:02 -0700 (PDT)
Received: from sessmg20.mgmt.ericsson.se (sessmg20.ericsson.net [193.180.251.50]) by ietfa.amsl.com (Postfix) with ESMTP id 79D461A00BB for <mmusic@ietf.org>; Fri, 14 Mar 2014 01:36:01 -0700 (PDT)
X-AuditID: c1b4fb32-b7f4c8e0000012f5-0c-5322bf691e39
Received: from ESESSHC023.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg20.mgmt.ericsson.se (Symantec Mail Security) with SMTP id 5E.C6.04853.96FB2235; Fri, 14 Mar 2014 09:35:54 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.216]) by ESESSHC023.ericsson.se ([153.88.183.87]) with mapi id 14.02.0387.000; Fri, 14 Mar 2014 09:35:53 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Christian Groves <Christian.Groves@nteczone.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] SCTP AppID
Thread-Index: AQHPOS8Nc6UA2CfhSkqx8lJA4yEdXprT2zKAgAAc8ICAAAbRgIAACYyAgAsGBzD///5gAIABHj2AgAAiyrA=
Date: Fri, 14 Mar 2014 08:35:52 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D214F6B@ESESSMB209.ericsson.se>
References: <53185B8E.2070808@nteczone.com> <C8EB64C0-3140-477C-9373-BD36B4B1A64B@ericsson.com> <53187415.2000108@nteczone.com> <C1D662DF-E3E3-45CD-991F-8090CD7130E0@ericsson.com> <531881CF.2010105@nteczone.com> <7594FB04B1934943A5C02806D1A2204B1D212B7E@ESESSMB209.ericsson.se> <5321BFBC.30304@alum.mit.edu> <5322AFD9.8090108@nteczone.com>
In-Reply-To: <5322AFD9.8090108@nteczone.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.18]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrELMWRmVeSWpSXmKPExsUyM+JvjW7WfqVgg875HBZf3jeyWExd/pjF gcljyZKfTB4rzs9kCWCK4rJJSc3JLEst0rdL4MqY1+dS8J2zYmvvH8YGxi/sXYycHBICJhKn 3/axQthiEhfurWfrYuTiEBI4wSjxccYyVghnCaPEk4WLWLoYOTjYBCwkuv9pgzSICERLTFrY zAZiCwsoSBx/fY8ZIq4ocf7SfBYIO0ni9o2JYDUsAqoS/xY2gC3mFfCVmPB7KtSy+0wS186v ZgRJcAroSHz/uhvsIkagi76fWsMEYjMLiEvcejKfCeJSAYkle84zQ9iiEi8f/4P6QFHi46t9 jBD1OhILdn9ig7C1JZYtfM0MsVhQ4uTMJywTGEVnIRk7C0nLLCQts5C0LGBkWcUoWZxaXJyb bmSgl5ueW6KXWpSZXFycn6dXnLqJERgvB7f8NtrBeHKP/SFGaQ4WJXHe66w1QUIC6Yklqdmp qQWpRfFFpTmpxYcYmTg4pRoY5aamnDtT1L1ujc5fgS/qtl+Pbq78fP7n9ihPiyNXdXfsPLlq /pEuz4+yTofdEvinxXivsgqSLJRzqq9X2Kb0qEd8BefVm9+Y7E8e49F5OVtMav5+9XRGW59I La3Tb7pKkjax8h/bPkn5eurV2CbFnKsxVbdaNn9bf2WOrsmCr5kbYo/9f2hzS4mlOCPRUIu5 qDgRAHJwPTtlAgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/xbj4t--Zk6cclLwBLgAiK9-AnbI
Subject: Re: [MMUSIC] SCTP AppID
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: Fri, 14 Mar 2014 08:36:03 -0000

Hi,

>>>> Do you have an answer for the second part of the previous email?
>>>> i.e One thing I'm still missing is how you specify multiple=20
>>>> app/alpns (whatever we're calling them) being used in a single SCTP=20
>>>> association, without using datachannel?
>>>
>>> My understanding is that it is no longer possible. You can only=20
>>> assign *one* sctpmap attribute (e.g. indicating webrtc-datachannel)=20
>>> to any given SCTPoDTLS m- line.
>>
>> I never understood this question. This is describing the use of the=20
>> association as a whole, not not a particular channel.
> [CNG] I didn't mention channel. I am talking about the association as a w=
hole. The sctpmap attribute indicates what app is in the SCTP association. =
The current syntax only allows one app.

Correct.

> So basically I can run "foo" over an SCTP association natively but as soo=
n as I want to run "foo" and "bar" over an SCTP association I need to use t=
he webrtc-datachannel protocol.

You can use two SCTP associations.

> I just wanted to check that behavior was planned not just as an unplanned=
 consequence of updated the draft version.

My understanding is that it is planned, but the authors can of course verif=
y :)

Regards,

Christer


From nobody Fri Mar 14 02:56:13 2014
Return-Path: <magnus.westerlund@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 CFE791A00FE for <mmusic@ietfa.amsl.com>; Fri, 14 Mar 2014 02:56:11 -0700 (PDT)
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 f-MKDTTF9ULi for <mmusic@ietfa.amsl.com>; Fri, 14 Mar 2014 02:56:10 -0700 (PDT)
Received: from sessmg20.mgmt.ericsson.se (sessmg20.ericsson.net [193.180.251.50]) by ietfa.amsl.com (Postfix) with ESMTP id D25641A00EC for <mmusic@ietf.org>; Fri, 14 Mar 2014 02:56:09 -0700 (PDT)
X-AuditID: c1b4fb32-b7f4c8e0000012f5-24-5322d23248a6
Received: from ESESSHC018.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg20.mgmt.ericsson.se (Symantec Mail Security) with SMTP id 11.04.04853.232D2235; Fri, 14 Mar 2014 10:56:02 +0100 (CET)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.74) with Microsoft SMTP Server id 14.2.347.0; Fri, 14 Mar 2014 10:56:01 +0100
Message-ID: <5322D231.2010909@ericsson.com>
Date: Fri, 14 Mar 2014 10:56:01 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: "mmusic (E-mail)" <mmusic@ietf.org>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrIJMWRmVeSWpSXmKPExsUyM+Jvja7RJaVgg+2T5SymLn/M4sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujEN30gr2qVWcf7eDvYFxsnwXIyeHhICJxIpbW9kgbDGJC/fW A9lcHEICJxglDt69zwjhLGeU6L26lbmLkYODV0BbYsFzKxCTRUBVYvZCUZBeNgELiZs/GsHm iAoES+w88JsRxOYVEJQ4OfMJC4gtIqAu0bq5jxXEFhbQlWj6dI0dZIyEgLhET2MQSJhZQE9i ytUWRghbXqJ562xmEFsIaGlDUwfrBEb+WUimzkLSMgtJywJG5lWMksWpxcW56UYGernpuSV6 qUWZycXF+Xl6xambGIHBdnDLb6MdjCf32B9ilOZgURLnvc5aEyQkkJ5YkpqdmlqQWhRfVJqT WnyIkYmDU6qB0bHvFsMlJSs55UDTjdHC8bF/7HQX13gE//I+abdn/sx5z8pVtuyLf7fkQN4m G4/wzOwDBxmPHqp19b789OGuOPVX96cssI5QtepMm/mL9ZFowAIJ7qO/ovk6c4QeRb+a9rrt 16f5poFHLzDfPXq/YkeF5V1BTVb+KfFhJ5zzp3EEGrPc+x7+XomlOCPRUIu5qDgRAKdbA5ME AgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/2ZC8fs9uFSxjxUw9b4XINTtF4v4
Subject: [MMUSIC] On the sparsity of RTP Payload types
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: Fri, 14 Mar 2014 09:56:12 -0000

MMUSIC,

There's have been a number of people not believing in that RTP payload
types may become a limiting factor when trying to express configurations
in SDP or other signaling. Thus, I would like to share my concerns over
how the combination of various mechanism effects the number of actual
payload type configurations needed to negotiated.

First a set of mechanism that do affect Payload Type usage.

1. RTCP MUX (RFC 5761)
If one uses RTCP RTP multiplexing, then a number of the RTP payload
types are reserved for identifying the RTCP packets, rather than RTP
payload formats. The default reservation is to reserve PT numbers 64-95.
This limits the 128 PTs to 96 available ones.

2. BUNDLE (draft-ietf-mmusic-sdp-bundle-negotiation)
When using BUNDLE, all listed m= sections within a bundle group are in
the same RTP session, thus all the PTs share a single common PT
numbering space. Bundle has done what it can to allow re-use across the
m= sections for the same configurations.

3. Multi-Media RTP sessions (draft-ietf-avtcore-multi-media-rtp-session)
This mechanism allows multiple media types, like audio, video and text
to share the same RTP session. This in itself does not reduce the
availability, but increases the number of codec configurations that
might be required (or desired) to signal support for.

4. RTP Retransmission (RFC 4588)
RTP retransmission payload format, requires one PT per PT that one want
to be able to retransmit. If the answer is all of the payload formats,
this doubles the payload format consumption.

5. XOR based FEC (RFC 5109)
This RTP payload format would normally just consume one PT as it is
capable of recovering the original PT field of a lost packet. However,
it is commonly used with the redundancy payload format (RED) (RFC 2198).
And RED requires one to have one RTP payload type per Redundancy
combination. Thus, this results in at least as many PT as PTs one like
to be able to apply FEC on.


Lets try using the above in combination and see what the implications are.

So we have 96 available values using RTCP mux, we like to use RTP
Retransmission as well as XOR FEC, to be able to cope with whatever RTT
the path provides and still be robust to packet losses within that
single RTP session. Thus, we end up with a maximum of 32 PTs for
encoding configurations.

As this is an RTP session that contains both Audio and Video we need to
create a number of configurations for both of media types. This endpoint
do support a descent amount of codecs to be compatible with various systems.

Audio: PCMA, PCMU, OPUS, AMR, AMR-WB, EVRC, EVRCWB, G.719, G.722, G.729
Video: H.264, H.265, VP8, VP9, SVC

On the audio side (10 codecs), this is actually a relative small subset
of the audio codecs that may be carried in RTP. Considering the
different configurations or annex extensions, there is no problem to
actually triple this list when it comes to audio. For video these 5 is a
selection of what might be in use in the near future. Also here there
are some potential, although less to offer additional PTs based on the
codec configurations. H.264 could run amok and offer a huge number if
one have a codec implementation that supports many profiles, as each
profile requires its own PT to be offered. As H.264 has 10+ profiles it
is possible. But, a more realistic count is likely 3 PTs.

The main point is that just the codecs listed above are themselves 15.
With some need to have different configurations for some of them, the
number can relatively easily be doubled and result in that one is up
against the limit (32).

There are clearly choices that one can make to reduce the usage and save
some number of PT values. My main concern is that one more mechanism
that results in equal number of PTs of its own in regards to what it is
associated with, is likely to cause significant concern. And we do have
some that has the potential. Multi stream scalability or simulcast if we
would require to indicate each codec configuration with its own payload
type will increase the requirement with a significant factor.

Thus, this is a potential issue, and an issue that can't be dismissed,
just because your set of limitations makes it unlikely that you will run
into it. We do need to ensure that mechanisms doesn't waste PT values to
achieve some other gain. This is becoming a real limitation.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Färögatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From nobody Fri Mar 14 03:18:04 2014
Return-Path: <magnus.westerlund@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 203E31A010F for <mmusic@ietfa.amsl.com>; Fri, 14 Mar 2014 03:18:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.851
X-Spam-Level: 
X-Spam-Status: No, score=-3.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 ZRxswT17TiHu for <mmusic@ietfa.amsl.com>; Fri, 14 Mar 2014 03:17:56 -0700 (PDT)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id 0D8261A00ED for <mmusic@ietf.org>; Fri, 14 Mar 2014 03:17:54 -0700 (PDT)
X-AuditID: c1b4fb25-b7f038e000005d01-bc-5322d74bdc05
Received: from ESESSHC008.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id C8.BC.23809.B47D2235; Fri, 14 Mar 2014 11:17:47 +0100 (CET)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.44) with Microsoft SMTP Server id 14.2.347.0; Fri, 14 Mar 2014 11:17:45 +0100
Message-ID: <5322D749.8020306@ericsson.com>
Date: Fri, 14 Mar 2014 11:17:45 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Craig Matsuura <cmatsuura@vivint.com>, "mmusic@ietf.org" <mmusic@ietf.org>
References: <53223DAA.4040107@vivint.com>
In-Reply-To: <53223DAA.4040107@vivint.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpmluLIzCtJLcpLzFFi42KZGfG3Rtf7ulKwQfdvXYvdl74yW0xd/pjF gcljyZKfTB7nnl1lDWCK4rJJSc3JLEst0rdL4MpoWNzPUvBfuOLzh7PsDYzdAl2MnBwSAiYS p0/fZIewxSQu3FvP1sXIxSEkcIhRornjHjOEs5xRYu3/00wgVbwC2hLntm4G62ARUJW4seQh mM0mYCFx80cjG4gtKhAssfPAb0aIekGJkzOfsIDYIgJ+EjMu/wabIyzgKzHl7FqwGiEBTYkl 59cC9XJwcApoSfzZ7gViSgiIS/Q0BoFUMAvoSUy52sIIYctLNG+dzQzRqS3R0NTBOoFRcBaS ZbOQtMxC0rKAkXkVI3tuYmZOernRJkZgQB7c8lt1B+OdcyKHGKU5WJTEeT+8dQ4SEkhPLEnN Tk0tSC2KLyrNSS0+xMjEwSnVwFi4n8dI8nSz3tWIkkl7ysq89nzbcKSO1eqK8+2P8Wz7OPgT oiZWH6mrm5B01qYg0pxRdOWsom8nef1WtX1+/e1u03thC+7E5qCXFSaPzp7utqx4GZG56vm2 pc8ent1767PifQ8x+4rHc5WfX9scUrmD/X9nvWBiS+GhSxtX+nqkHdh/udK29YwSS3FGoqEW c1FxIgCyC7l6FgIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/xiYiNL75vHAv_JeL1n6KFtGmRvM
Subject: Re: [MMUSIC] RTSP questions in regards to the control channel socket
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: Fri, 14 Mar 2014 10:18:02 -0000

On 2014-03-14 00:22, Craig Matsuura wrote:
> Hi this is my first time posting here.  I have a basic question about 
> how a RTSP server should handled a connect and disconnect for what I am 
> calling the control channel (connection or transport). The control 
> channel (please correct me) is what sends the DESCRIBE, SETUP, OPTIONS, 
> PLAY commands to the RTSP SERVER.
> 
> Should a server treat the first DESCRIBE connection as its session. So 
> in the case where a socket connects to a RTSP server and sends a 
> DESCRIBE, is disconnected either by the client or some failure on the 
> server should the following SETUP succeed?

No, DESCRIBE is a state less operation. If one needs a linkage between
the Describe response body and the setup, then one should use etags and
conditional requests to ensure that one is establishing the session with
a relevant session description.

> 
> Also if using a RTSP Proxy and in the same scenario, but after the 
> DESCRIBE and closing of the socket a new socket is open to send an 
> OPTIONS (for keepalive) should the following SETUP succeed?

Yes the SETUP should succeed if otherwise valid.

> 
>  From what I understood from the RFC2326 Section 1.7 RTSP State, it 
> should not matter how many connections are used to control the RTSP Stream.
> 
> 1. Control Socket is not prevent a client from connecting and 
> disconnecting to send Transport commands.

I am uncertain what you mean with the Control socket, if you means the
Socket the server listens to incoming TCP connection establishments and
their data, it needs to be accepting those comming and going.

> 2. The keep-alive for a session should not start until a SETUP command, 
> which can optional report the timeout for the session.

Exact, the keep-alive is associated with the RTSP session, not the
signalling connection used to send RTSP requests and response between
the server and client.

You might find RTSP 2.0's text on this being clearer:
https://datatracker.ietf.org/doc/draft-ietf-mmusic-rfc2326bis/

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Färögatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From nobody Fri Mar 14 03:24:34 2014
Return-Path: <ron.even.tlv@gmail.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 43BBF1A0105 for <mmusic@ietfa.amsl.com>; Fri, 14 Mar 2014 03:24:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 dYY15PuwdOp7 for <mmusic@ietfa.amsl.com>; Fri, 14 Mar 2014 03:24:30 -0700 (PDT)
Received: from mail-ee0-x22c.google.com (mail-ee0-x22c.google.com [IPv6:2a00:1450:4013:c00::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 7BF3C1A00FF for <mmusic@ietf.org>; Fri, 14 Mar 2014 03:24:30 -0700 (PDT)
Received: by mail-ee0-f44.google.com with SMTP id e49so1182259eek.31 for <mmusic@ietf.org>; Fri, 14 Mar 2014 03:24:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:to:references:in-reply-to:subject:date:message-id:mime-version :content-type:content-transfer-encoding:thread-index :content-language; bh=gjhlunRfSmBZ2zIDXX1klyffkgi/kBnixF5hGina0xc=; b=I4otNU6fI5xUQXTG6AY8N5UoITPBDIclvloKaAkTxKAW66I0vc0nkR8w+Wv0NsBxvp FCLZqfImynIPgHrYxBZvkMTbK6Mmf3eSGEh9ptDgx5ZpKjxQhv/xayPWIr4ZJCYzmbJW sqNS3/L75AAjlDRL7m1HGQmfvfO8yqh96ogYdIpydCXJglEFMFHRBYkA3W+kltMxwOrx o+IT4uM9RO1iGmruKMvRE2EJU6aXQRpKwRVocJN+3pj4XZEyV4TBPGhk/W15FQbkfstE z2CgQmxj7nUl1LRWHw0atz7/WMenUJdZbHqcaYe3qV7tXaG3r3LHN92icYpD6Jy5bveI MeOg==
X-Received: by 10.14.213.135 with SMTP id a7mr7521708eep.57.1394792663239; Fri, 14 Mar 2014 03:24:23 -0700 (PDT)
Received: from RoniE (bzq-79-179-150-91.red.bezeqint.net. [79.179.150.91]) by mx.google.com with ESMTPSA id 43sm16155495eeh.13.2014.03.14.03.24.21 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 14 Mar 2014 03:24:22 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'Magnus Westerlund'" <magnus.westerlund@ericsson.com>, "'mmusic \(E-mail\)'" <mmusic@ietf.org>
References: <5322D231.2010909@ericsson.com>
In-Reply-To: <5322D231.2010909@ericsson.com>
Date: Fri, 14 Mar 2014 12:24:18 +0200
Message-ID: <012a01cf3f6f$90299e00$b07cda00$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHAQdxJoaeR3qB6iQFUH21DnYorUpr+WptQ
Content-Language: en-us
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/n-lKchsaJW4F63tbyXr-f1eVSCA
Subject: Re: [MMUSIC] On the sparsity of RTP Payload types
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: Fri, 14 Mar 2014 10:24:33 -0000

Hi Magnus,
I think that also the static payload types limit the number of available =
PT
Roni

> -----Original Message-----
> From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Magnus
> Westerlund
> Sent: 14 March, 2014 11:56 AM
> To: mmusic (E-mail)
> Subject: [MMUSIC] On the sparsity of RTP Payload types
>=20
> MMUSIC,
>=20
> There's have been a number of people not believing in that RTP payload
types
> may become a limiting factor when trying to express configurations in =
SDP
or
> other signaling. Thus, I would like to share my concerns over how the
> combination of various mechanism effects the number of actual payload =
type
> configurations needed to negotiated.
>=20
> First a set of mechanism that do affect Payload Type usage.
>=20
> 1. RTCP MUX (RFC 5761)
> If one uses RTCP RTP multiplexing, then a number of the RTP payload =
types
are
> reserved for identifying the RTCP packets, rather than RTP payload
formats.
> The default reservation is to reserve PT numbers 64-95.
> This limits the 128 PTs to 96 available ones.
>=20
> 2. BUNDLE (draft-ietf-mmusic-sdp-bundle-negotiation)
> When using BUNDLE, all listed m=3D sections within a bundle group are =
in the
> same RTP session, thus all the PTs share a single common PT numbering
space.
> Bundle has done what it can to allow re-use across the m=3D sections =
for the
> same configurations.
>=20
> 3. Multi-Media RTP sessions =
(draft-ietf-avtcore-multi-media-rtp-session)
> This mechanism allows multiple media types, like audio, video and text =
to
share
> the same RTP session. This in itself does not reduce the availability, =
but
> increases the number of codec configurations that might be required =
(or
> desired) to signal support for.
>=20
> 4. RTP Retransmission (RFC 4588)
> RTP retransmission payload format, requires one PT per PT that one =
want to
be
> able to retransmit. If the answer is all of the payload formats, this
doubles the
> payload format consumption.
>=20
> 5. XOR based FEC (RFC 5109)
> This RTP payload format would normally just consume one PT as it is
capable of
> recovering the original PT field of a lost packet. However, it is =
commonly
used
> with the redundancy payload format (RED) (RFC 2198).
> And RED requires one to have one RTP payload type per Redundancy
> combination. Thus, this results in at least as many PT as PTs one like =
to
be able
> to apply FEC on.
>=20
>=20
> Lets try using the above in combination and see what the implications =
are.
>=20
> So we have 96 available values using RTCP mux, we like to use RTP
> Retransmission as well as XOR FEC, to be able to cope with whatever =
RTT
the
> path provides and still be robust to packet losses within that single =
RTP
session.
> Thus, we end up with a maximum of 32 PTs for encoding configurations.
>=20
> As this is an RTP session that contains both Audio and Video we need =
to
create
> a number of configurations for both of media types. This endpoint do
support a
> descent amount of codecs to be compatible with various systems.
>=20
> Audio: PCMA, PCMU, OPUS, AMR, AMR-WB, EVRC, EVRCWB, G.719, G.722,
> G.729
> Video: H.264, H.265, VP8, VP9, SVC
>=20
> On the audio side (10 codecs), this is actually a relative small =
subset of
the
> audio codecs that may be carried in RTP. Considering the different
> configurations or annex extensions, there is no problem to actually =
triple
this
> list when it comes to audio. For video these 5 is a selection of what
might be in
> use in the near future. Also here there are some potential, although =
less
to
> offer additional PTs based on the codec configurations. H.264 could =
run
amok
> and offer a huge number if one have a codec implementation that =
supports
> many profiles, as each profile requires its own PT to be offered. As =
H.264
has
> 10+ profiles it is possible. But, a more realistic count is likely 3 =
PTs.
>=20
> The main point is that just the codecs listed above are themselves 15.
> With some need to have different configurations for some of them, the
number
> can relatively easily be doubled and result in that one is up against =
the
limit
> (32).
>=20
> There are clearly choices that one can make to reduce the usage and =
save
> some number of PT values. My main concern is that one more mechanism =
that
> results in equal number of PTs of its own in regards to what it is
associated
> with, is likely to cause significant concern. And we do have some that =
has
the
> potential. Multi stream scalability or simulcast if we would require =
to
indicate
> each codec configuration with its own payload type will increase the
> requirement with a significant factor.
>=20
> Thus, this is a potential issue, and an issue that can't be dismissed,
just because
> your set of limitations makes it unlikely that you will run into it. =
We do
need to
> ensure that mechanisms doesn't waste PT values to achieve some other =
gain.
> This is becoming a real limitation.
>=20
> Cheers
>=20
> Magnus Westerlund
>=20
> ----------------------------------------------------------------------
> Services, Media and Network features, Ericsson Research EAB/TXM
> ----------------------------------------------------------------------
> Ericsson AB                 | Phone  +46 10 7148287
> F=E4r=F6gatan 6                 | Mobile +46 73 0949079
> SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
>=20
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic


From nobody Fri Mar 14 03:42:11 2014
Return-Path: <magnus.westerlund@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 5EC321A0100 for <mmusic@ietfa.amsl.com>; Fri, 14 Mar 2014 03:42:08 -0700 (PDT)
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 PcDm3p7YOVzj for <mmusic@ietfa.amsl.com>; Fri, 14 Mar 2014 03:42:06 -0700 (PDT)
Received: from sessmg20.mgmt.ericsson.se (sessmg20.ericsson.net [193.180.251.50]) by ietfa.amsl.com (Postfix) with ESMTP id 740CD1A010E for <mmusic@ietf.org>; Fri, 14 Mar 2014 03:42:05 -0700 (PDT)
X-AuditID: c1b4fb32-b7f4c8e0000012f5-c4-5322dcf5c421
Received: from ESESSHC017.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg20.mgmt.ericsson.se (Symantec Mail Security) with SMTP id 24.AB.04853.5FCD2235; Fri, 14 Mar 2014 11:41:58 +0100 (CET)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.71) with Microsoft SMTP Server id 14.2.347.0; Fri, 14 Mar 2014 11:41:57 +0100
Message-ID: <5322DCF5.9000602@ericsson.com>
Date: Fri, 14 Mar 2014 11:41:57 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Roni Even <ron.even.tlv@gmail.com>, "'mmusic (E-mail)'" <mmusic@ietf.org>
References: <5322D231.2010909@ericsson.com> <012a01cf3f6f$90299e00$b07cda00$@gmail.com>
In-Reply-To: <012a01cf3f6f$90299e00$b07cda00$@gmail.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprMLMWRmVeSWpSXmKPExsUyM+Jvje63O0rBBlNb2CymLn/MYvG3ndmB yWPnrLvsHkuW/GQKYIrisklJzcksSy3St0vgyuh8doml4LdJxeXLm5kbGNdqdTFyckgImEg0 zN7ADmGLSVy4t54NxBYSOMEoseFsYBcjF5C9nFFi1s35zCAJXgFtia0vXgHZHBwsAqoS+75E gITZBCwkbv5oBOsVFQiW2HngNyNEuaDEyZlPWEBsEQFfiePTvoDFhQWsJNq2PGeH2BUuMefH c7DxnEBzvnSdYQIZLyEgLtHTGAQSZhbQk5hytYURwpaXaN46mxmiVVuioamDdQKj4Cwk22Yh aZmFpGUBI/MqRsni1OLi3HQjA73c9NwSvdSizOTi4vw8veLUTYzAgD245bfRDsaTe+wPMUpz sCiJ815nrQkSEkhPLEnNTk0tSC2KLyrNSS0+xMjEwSnVwNiy26HNvClr0ZGb5Txhp/5eV5+p kDzb8+KWlb+sGeTuKx/unjZ/zsQfYtsuv799b0FvW+K838lmh498V2zY48H2hpHrVdf+z5G5 PxY+qJrRcO8Uc0/X1rk1Uyfa1xxdfZtzsyvnctG9c1+sPrU3aCavjEv4/+6e7UwvdpZO/i+9 IGD2alfer18jlViKMxINtZiLihMBtdE9rCYCAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/RTqfW7BwSljtSGglJh11e8FRJj8
Subject: Re: [MMUSIC] On the sparsity of RTP Payload types
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: Fri, 14 Mar 2014 10:42:08 -0000

On 2014-03-14 11:24, Roni Even wrote:
> Hi Magnus,
> I think that also the static payload types limit the number of available PT

Not really, a modern user of SDP you should be able to override any of
the static PT value with whatever you want to use it for. But, I agree
it is the PT values you like to consume last as they might have issues
with redefining or getting accurate monitoring on them due to
misinterpretation of them as the static codec assignment.

But, if you need to avoid using them you loose 24 values for actually
assigned ones, and another 3 are reserved.

/Magnus

> Roni
> 
>> -----Original Message-----
>> From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Magnus
>> Westerlund
>> Sent: 14 March, 2014 11:56 AM
>> To: mmusic (E-mail)
>> Subject: [MMUSIC] On the sparsity of RTP Payload types
>>
>> MMUSIC,
>>
>> There's have been a number of people not believing in that RTP payload
> types
>> may become a limiting factor when trying to express configurations in SDP
> or
>> other signaling. Thus, I would like to share my concerns over how the
>> combination of various mechanism effects the number of actual payload type
>> configurations needed to negotiated.
>>
>> First a set of mechanism that do affect Payload Type usage.
>>
>> 1. RTCP MUX (RFC 5761)
>> If one uses RTCP RTP multiplexing, then a number of the RTP payload types
> are
>> reserved for identifying the RTCP packets, rather than RTP payload
> formats.
>> The default reservation is to reserve PT numbers 64-95.
>> This limits the 128 PTs to 96 available ones.
>>
>> 2. BUNDLE (draft-ietf-mmusic-sdp-bundle-negotiation)
>> When using BUNDLE, all listed m= sections within a bundle group are in the
>> same RTP session, thus all the PTs share a single common PT numbering
> space.
>> Bundle has done what it can to allow re-use across the m= sections for the
>> same configurations.
>>
>> 3. Multi-Media RTP sessions (draft-ietf-avtcore-multi-media-rtp-session)
>> This mechanism allows multiple media types, like audio, video and text to
> share
>> the same RTP session. This in itself does not reduce the availability, but
>> increases the number of codec configurations that might be required (or
>> desired) to signal support for.
>>
>> 4. RTP Retransmission (RFC 4588)
>> RTP retransmission payload format, requires one PT per PT that one want to
> be
>> able to retransmit. If the answer is all of the payload formats, this
> doubles the
>> payload format consumption.
>>
>> 5. XOR based FEC (RFC 5109)
>> This RTP payload format would normally just consume one PT as it is
> capable of
>> recovering the original PT field of a lost packet. However, it is commonly
> used
>> with the redundancy payload format (RED) (RFC 2198).
>> And RED requires one to have one RTP payload type per Redundancy
>> combination. Thus, this results in at least as many PT as PTs one like to
> be able
>> to apply FEC on.
>>
>>
>> Lets try using the above in combination and see what the implications are.
>>
>> So we have 96 available values using RTCP mux, we like to use RTP
>> Retransmission as well as XOR FEC, to be able to cope with whatever RTT
> the
>> path provides and still be robust to packet losses within that single RTP
> session.
>> Thus, we end up with a maximum of 32 PTs for encoding configurations.
>>
>> As this is an RTP session that contains both Audio and Video we need to
> create
>> a number of configurations for both of media types. This endpoint do
> support a
>> descent amount of codecs to be compatible with various systems.
>>
>> Audio: PCMA, PCMU, OPUS, AMR, AMR-WB, EVRC, EVRCWB, G.719, G.722,
>> G.729
>> Video: H.264, H.265, VP8, VP9, SVC
>>
>> On the audio side (10 codecs), this is actually a relative small subset of
> the
>> audio codecs that may be carried in RTP. Considering the different
>> configurations or annex extensions, there is no problem to actually triple
> this
>> list when it comes to audio. For video these 5 is a selection of what
> might be in
>> use in the near future. Also here there are some potential, although less
> to
>> offer additional PTs based on the codec configurations. H.264 could run
> amok
>> and offer a huge number if one have a codec implementation that supports
>> many profiles, as each profile requires its own PT to be offered. As H.264
> has
>> 10+ profiles it is possible. But, a more realistic count is likely 3 PTs.
>>
>> The main point is that just the codecs listed above are themselves 15.
>> With some need to have different configurations for some of them, the
> number
>> can relatively easily be doubled and result in that one is up against the
> limit
>> (32).
>>
>> There are clearly choices that one can make to reduce the usage and save
>> some number of PT values. My main concern is that one more mechanism that
>> results in equal number of PTs of its own in regards to what it is
> associated
>> with, is likely to cause significant concern. And we do have some that has
> the
>> potential. Multi stream scalability or simulcast if we would require to
> indicate
>> each codec configuration with its own payload type will increase the
>> requirement with a significant factor.
>>
>> Thus, this is a potential issue, and an issue that can't be dismissed,
> just because
>> your set of limitations makes it unlikely that you will run into it. We do
> need to
>> ensure that mechanisms doesn't waste PT values to achieve some other gain.
>> This is becoming a real limitation.
>>
>> Cheers
>>
>> Magnus Westerlund
>>
>> ----------------------------------------------------------------------
>> Services, Media and Network features, Ericsson Research EAB/TXM
>> ----------------------------------------------------------------------
>> Ericsson AB                 | Phone  +46 10 7148287
>> Färögatan 6                 | Mobile +46 73 0949079
>> SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
>> ----------------------------------------------------------------------
>>
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www.ietf.org/mailman/listinfo/mmusic
> 
> 
> 


-- 

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Färögatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From nobody Fri Mar 14 08:30:58 2014
Return-Path: <pkyzivat@alum.mit.edu>
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 C7CEB1A0161 for <mmusic@ietfa.amsl.com>; Fri, 14 Mar 2014 08:30:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] 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 sWwRkU0n7DmV for <mmusic@ietfa.amsl.com>; Fri, 14 Mar 2014 08:30:55 -0700 (PDT)
Received: from qmta07.westchester.pa.mail.comcast.net (qmta07.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:64]) by ietfa.amsl.com (Postfix) with ESMTP id 975E21A015B for <mmusic@ietf.org>; Fri, 14 Mar 2014 08:30:55 -0700 (PDT)
Received: from omta14.westchester.pa.mail.comcast.net ([76.96.62.60]) by qmta07.westchester.pa.mail.comcast.net with comcast id dQ251n0041HzFnQ57TWol9; Fri, 14 Mar 2014 15:30:48 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta14.westchester.pa.mail.comcast.net with comcast id dTWo1n00M3ZTu2S3aTWo4N; Fri, 14 Mar 2014 15:30:48 +0000
Message-ID: <532320A8.6050302@alum.mit.edu>
Date: Fri, 14 Mar 2014 11:30:48 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: mmusic@ietf.org
References: <53185B8E.2070808@nteczone.com> <C8EB64C0-3140-477C-9373-BD36B4B1A64B@ericsson.com> <53187415.2000108@nteczone.com> <C1D662DF-E3E3-45CD-991F-8090CD7130E0@ericsson.com> <531881CF.2010105@nteczone.com> <7594FB04B1934943A5C02806D1A2204B1D212B7E@ESESSMB209.ericsson.se> <5321BFBC.30304@alum.mit.edu> <5322AFD9.8090108@nteczone.com>
In-Reply-To: <5322AFD9.8090108@nteczone.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1394811048; bh=QRQw+16dRwlCrYNNKmPBSCZedr1xDe4X3Cdf0iD2upw=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=rNHXoLvPWOrzpZscJVzi+PYmNGkPVKRTgIHbYgeZgO/6q+NnQ0C9JGJ1xWoVANhH6 bIebFbnSq5PhgjQiZ+OlO3Yxy0eR2XzpD8MouUa0Vrf17zd/aTtiUprs6Ly3CebXwA d0r1bsyj4NxJgd+FsnC8NzA60Qo84M2wPl4hDp7R2c58hQFuUsIjqVQwezTvh4REVK IHs8Cn3YdVZcqv6d61hYuaiCDSU+M5lTmDbDnuo1FbZPDOoe3z7YnV5/EwAD2DiAXu ldw8jTAXRZFcacSvs6rXHPEb21MLOhNmnickBMq4FHwqkGDPgZIDsWFGUTU5DvyDtd Z3sKbsWAQYKpQ==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/6Pq2BnTbr-nojLTX1GVMiSBoWTk
Subject: Re: [MMUSIC] SCTP AppID
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: Fri, 14 Mar 2014 15:30:57 -0000

On 3/14/14 3:29 AM, Christian Groves wrote:
>
> On 14/03/2014 1:25 AM, Paul Kyzivat wrote:
>> On 3/13/14 9:32 AM, Christer Holmberg wrote:
>>> Hi Christian,
>>>
>>>> Do you have an answer for the second part of the previous email?
>>>> i.e One thing I'm still missing is how you specify multiple
>>>> app/alpns (whatever we're calling them) being used in a single SCTP
>>>> association, without using datachannel?
>>>
>>> My understanding is that it is no longer possible. You can only
>>> assign *one* sctpmap attribute (e.g. indicating webrtc-datachannel)
>>> to any given SCTPoDTLS m- line.
>>
>> I never understood this question. This is describing the use of the
>> association as a whole, not not a particular channel.
> [CNG] I didn't mention channel. I am talking about the association as a
> whole. The sctpmap attribute indicates what app is in the SCTP
> association. The current syntax only allows one app. So basically I can
> run "foo" over an SCTP association natively but as soon as I want to run
> "foo" and "bar" over an SCTP association I need to use the
> webrtc-datachannel protocol.
>
> I just wanted to check that behavior was planned not just as an
> unplanned consequence of updated the draft version.

This is the problem with using the term "app" here.
*Something* must coordinate the overall use of the association. Having 
multiple things use it without coordination won't work. If you have 
multiple "applications", they could coexist by using DCEP to assign data 
channels for each application. But then DCEP, and Data Channels in 
general, is the "app" on top of SCTP. (Even then, the multiple apps need 
to agree on naming of channels in order to coexist.)

IMO what you are actually naming here is a *convention* for use of the 
association and the streams it contains.

	Thanks,
	Paul


From nobody Fri Mar 14 09:15:22 2014
Return-Path: <albrecht.schwarz@alcatel-lucent.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 1F7321A015B for <mmusic@ietfa.amsl.com>; Fri, 14 Mar 2014 09:15:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] autolearn=ham
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 xx9kBVwOTz0Z for <mmusic@ietfa.amsl.com>; Fri, 14 Mar 2014 09:15:13 -0700 (PDT)
Received: from hoemail1.alcatel.com (hoemail1.alcatel.com [192.160.6.148]) by ietfa.amsl.com (Postfix) with ESMTP id D20AE1A00F1 for <mmusic@ietf.org>; Fri, 14 Mar 2014 09:15:13 -0700 (PDT)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (h135-239-2-122.lucent.com [135.239.2.122]) by hoemail1.alcatel.com (8.13.8/IER-o) with ESMTP id s2EGF39f009746 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 14 Mar 2014 11:15:04 -0500 (CDT)
Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id s2EGF2iT005141 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 14 Mar 2014 17:15:02 +0100
Received: from FR711WXCHMBA03.zeu.alcatel-lucent.com ([169.254.3.116]) by FR711WXCHHUB02.zeu.alcatel-lucent.com ([135.239.2.112]) with mapi id 14.02.0247.003; Fri, 14 Mar 2014 17:15:02 +0100
From: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] SCTP AppID
Thread-Index: AQHPP5qC9y8Vj1ODtUqaa4uall1ZAJrgvknQ
Date: Fri, 14 Mar 2014 16:15:02 +0000
Message-ID: <786615F3A85DF44AA2A76164A71FE1AC1B3422@FR711WXCHMBA03.zeu.alcatel-lucent.com>
References: <53185B8E.2070808@nteczone.com> <C8EB64C0-3140-477C-9373-BD36B4B1A64B@ericsson.com> <53187415.2000108@nteczone.com> <C1D662DF-E3E3-45CD-991F-8090CD7130E0@ericsson.com> <531881CF.2010105@nteczone.com> <7594FB04B1934943A5C02806D1A2204B1D212B7E@ESESSMB209.ericsson.se> <5321BFBC.30304@alum.mit.edu> <5322AFD9.8090108@nteczone.com> <532320A8.6050302@alum.mit.edu>
In-Reply-To: <532320A8.6050302@alum.mit.edu>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.239.27.39]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/Qe6ucQ5hM3ICfUlGFKG1KcLX3kI
Subject: Re: [MMUSIC] SCTP AppID
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: Fri, 14 Mar 2014 16:15:19 -0000

> This is the problem with using the term "app" here.

Guess the issue of naming/terminology is related to "protocol layer".
Perhaps a way forward could be to look at the more abstract model of "layer=
ed services", rather the "layered protocol architecture" everyone has in mi=
nd.
Such a generic model could be based ITU-T X.200, =A7 5.7 "The nature of the=
 (N)-service", which is fairly generic.

Here, a "layered service" model could look like (just assigning 'N' to the =
SCTP association service):

Service:
- Application       (N+2)-service
- SCTP Stream       (N+1)-service
- SCTP Association   (N)-service
- SCTP Path         (N-1)-service
- DTLS Session      (N-2)-service
- UDP Transport     (N-3)-service
- IP connection     (N-4)-service

Such a model may allow to overcome the naming, terminology issue (where the=
 single protocol layer "SCTP" aggregates the three services N-1, N and N+1)=
.

The DC protocol would use the (N+1)-service.
An application could use an (N+1)-service ("application multiplexing over a=
 single SCTP Assoc"), or an (N)-service ("1:1 mapping between application a=
n SCTP Assoc").

Regards,
Albrecht

PS
Of course, not every x-service is visible from signalling plane, etc



-----Original Message-----
From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Paul Kyzivat
Sent: Freitag, 14. M=E4rz 2014 16:31
To: mmusic@ietf.org
Subject: Re: [MMUSIC] SCTP AppID

On 3/14/14 3:29 AM, Christian Groves wrote:
>
> On 14/03/2014 1:25 AM, Paul Kyzivat wrote:
>> On 3/13/14 9:32 AM, Christer Holmberg wrote:
>>> Hi Christian,
>>>
>>>> Do you have an answer for the second part of the previous email?
>>>> i.e One thing I'm still missing is how you specify multiple=20
>>>> app/alpns (whatever we're calling them) being used in a single SCTP=20
>>>> association, without using datachannel?
>>>
>>> My understanding is that it is no longer possible. You can only=20
>>> assign *one* sctpmap attribute (e.g. indicating webrtc-datachannel)=20
>>> to any given SCTPoDTLS m- line.
>>
>> I never understood this question. This is describing the use of the=20
>> association as a whole, not not a particular channel.
> [CNG] I didn't mention channel. I am talking about the association as=20
> a whole. The sctpmap attribute indicates what app is in the SCTP=20
> association. The current syntax only allows one app. So basically I=20
> can run "foo" over an SCTP association natively but as soon as I want=20
> to run "foo" and "bar" over an SCTP association I need to use the=20
> webrtc-datachannel protocol.
>
> I just wanted to check that behavior was planned not just as an=20
> unplanned consequence of updated the draft version.

This is the problem with using the term "app" here.
*Something* must coordinate the overall use of the association. Having mult=
iple things use it without coordination won't work. If you have multiple "a=
pplications", they could coexist by using DCEP to assign data channels for =
each application. But then DCEP, and Data Channels in general, is the "app"=
 on top of SCTP. (Even then, the multiple apps need to agree on naming of c=
hannels in order to coexist.)

IMO what you are actually naming here is a *convention* for use of the asso=
ciation and the streams it contains.

	Thanks,
	Paul

_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www.ietf.org/mailman/listinfo/mmusic


From nobody Fri Mar 14 10:34:14 2014
Return-Path: <juberti@google.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 A299F1A01A7 for <mmusic@ietfa.amsl.com>; Fri, 14 Mar 2014 10:34:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.925
X-Spam-Level: 
X-Spam-Status: No, score=-1.925 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001] autolearn=ham
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 kmsBByiBvULH for <mmusic@ietfa.amsl.com>; Fri, 14 Mar 2014 10:34:10 -0700 (PDT)
Received: from mail-ve0-x229.google.com (mail-ve0-x229.google.com [IPv6:2607:f8b0:400c:c01::229]) by ietfa.amsl.com (Postfix) with ESMTP id D12631A01A6 for <mmusic@ietf.org>; Fri, 14 Mar 2014 10:34:09 -0700 (PDT)
Received: by mail-ve0-f169.google.com with SMTP id pa12so3133016veb.28 for <mmusic@ietf.org>; Fri, 14 Mar 2014 10:34:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=3xfTfMkDap0VF9AjZL37xeD/+uDenQqGpAueouqsz2A=; b=gGy3q/scF6Ya500tCKsan8OFE/dcIrZwwj+urRVCb2tzTxzgXjsdiYOvuZaCSVKBs7 R24YzbJ0okgQD9V2okKNa0pibBsBg35vtVVhyEtCUJflwOdfnOyGX2YCVnEp9qZOG2EK kXdttRNYWqX6ckb24rN20H4aO0xswCJneBARt4z/uKELpdaHiNEjMaErsiBuY1OLNPqI 41374flvz/kr/yFOzKOowu/gvdqb4+o04afkCPXEV/RQKIpItnKnFi1WP1IlGLLEXHuP zkki6OzR6pV9KaLz2lw4ShyzRTDem18Ded8knFhf4C3mUMcsXRQc8FLQRWjG+dQgQwVw 5/Kg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=3xfTfMkDap0VF9AjZL37xeD/+uDenQqGpAueouqsz2A=; b=gFBT2rGum32c0FTOMWYTc+totNS9ZQX2MXpOcIE48NyiYFkd57tdtirbz/9Q3FuEAg hMtm0VK02jEMbj9Hvm91DBVTTdB8Fq3ZgNaMfHkcLB1LbTTnegpezO3JMxnQ4CkY4ohE RBRix8iOuJgOxqE9XKIjMY87HmWm1b6FcOHUzfnIgB4CERz30YzweGCu/BP2RaN/5BKi LFQ91xaUPX2quyKSeVB/QsYgS/+wuDHaGDjah9iGCYwoagV1m/jtsbLOQTpNYcVcO4JF Cd0u8soBfVpvzsLhG0i1AOYwtdrgVo4zeO1ejsZLt44qFXWa6r2uNlGz1TQ0hw7kOOdF Afqg==
X-Gm-Message-State: ALoCoQlZwSDZW1aq3go4KGbL+GY+iA2ktY6xXYuzdrtq7/HtVA0SM8Vsm06tmjNLDYt9/GzoXXlFJbvDDZtoiF1exsH48hfuHhHPBUsQfVzVj3DS1UQS9joYfCFfplOlkV8pb9ks34kCugYZ+BLE/+yUXnV1DFcmJzvarrW5IdXwgVWbigGaZKv+U4Bu3joW9gJbhU83tWcc
X-Received: by 10.52.161.130 with SMTP id xs2mr51542vdb.49.1394818442484; Fri, 14 Mar 2014 10:34:02 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.26.43 with HTTP; Fri, 14 Mar 2014 10:33:42 -0700 (PDT)
In-Reply-To: <5322D231.2010909@ericsson.com>
References: <5322D231.2010909@ericsson.com>
From: Justin Uberti <juberti@google.com>
Date: Fri, 14 Mar 2014 10:33:42 -0700
Message-ID: <CAOJ7v-0WD6wcmFFXFQ1YuMqSm4UBzyU=7-o3MtKO3JXHiTna8w@mail.gmail.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Content-Type: multipart/alternative; boundary=089e0160c980ca716404f49479c1
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/v29xjZUz3ovXG0RrQZrLIZWWMVE
Cc: "mmusic \(E-mail\)" <mmusic@ietf.org>
Subject: Re: [MMUSIC] On the sparsity of RTP Payload types
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: Fri, 14 Mar 2014 17:34:12 -0000

--089e0160c980ca716404f49479c1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Agree this is a real limitation. In addition to the codecs listed above,
note that CN and telephone-event are often needed, and potentially in
multiple clockrates.

(which is why I think we shouldn't burn PTs on demultiplexing)




On Fri, Mar 14, 2014 at 2:56 AM, Magnus Westerlund <
magnus.westerlund@ericsson.com> wrote:

> MMUSIC,
>
> There's have been a number of people not believing in that RTP payload
> types may become a limiting factor when trying to express configurations
> in SDP or other signaling. Thus, I would like to share my concerns over
> how the combination of various mechanism effects the number of actual
> payload type configurations needed to negotiated.
>
> First a set of mechanism that do affect Payload Type usage.
>
> 1. RTCP MUX (RFC 5761)
> If one uses RTCP RTP multiplexing, then a number of the RTP payload
> types are reserved for identifying the RTCP packets, rather than RTP
> payload formats. The default reservation is to reserve PT numbers 64-95.
> This limits the 128 PTs to 96 available ones.
>
> 2. BUNDLE (draft-ietf-mmusic-sdp-bundle-negotiation)
> When using BUNDLE, all listed m=3D sections within a bundle group are in
> the same RTP session, thus all the PTs share a single common PT
> numbering space. Bundle has done what it can to allow re-use across the
> m=3D sections for the same configurations.
>
> 3. Multi-Media RTP sessions (draft-ietf-avtcore-multi-media-rtp-session)
> This mechanism allows multiple media types, like audio, video and text
> to share the same RTP session. This in itself does not reduce the
> availability, but increases the number of codec configurations that
> might be required (or desired) to signal support for.
>
> 4. RTP Retransmission (RFC 4588)
> RTP retransmission payload format, requires one PT per PT that one want
> to be able to retransmit. If the answer is all of the payload formats,
> this doubles the payload format consumption.
>
> 5. XOR based FEC (RFC 5109)
> This RTP payload format would normally just consume one PT as it is
> capable of recovering the original PT field of a lost packet. However,
> it is commonly used with the redundancy payload format (RED) (RFC 2198).
> And RED requires one to have one RTP payload type per Redundancy
> combination. Thus, this results in at least as many PT as PTs one like
> to be able to apply FEC on.
>
>
> Lets try using the above in combination and see what the implications are=
.
>
> So we have 96 available values using RTCP mux, we like to use RTP
> Retransmission as well as XOR FEC, to be able to cope with whatever RTT
> the path provides and still be robust to packet losses within that
> single RTP session. Thus, we end up with a maximum of 32 PTs for
> encoding configurations.
>
> As this is an RTP session that contains both Audio and Video we need to
> create a number of configurations for both of media types. This endpoint
> do support a descent amount of codecs to be compatible with various
> systems.
>
> Audio: PCMA, PCMU, OPUS, AMR, AMR-WB, EVRC, EVRCWB, G.719, G.722, G.729
> Video: H.264, H.265, VP8, VP9, SVC
>
> On the audio side (10 codecs), this is actually a relative small subset
> of the audio codecs that may be carried in RTP. Considering the
> different configurations or annex extensions, there is no problem to
> actually triple this list when it comes to audio. For video these 5 is a
> selection of what might be in use in the near future. Also here there
> are some potential, although less to offer additional PTs based on the
> codec configurations. H.264 could run amok and offer a huge number if
> one have a codec implementation that supports many profiles, as each
> profile requires its own PT to be offered. As H.264 has 10+ profiles it
> is possible. But, a more realistic count is likely 3 PTs.
>
> The main point is that just the codecs listed above are themselves 15.
> With some need to have different configurations for some of them, the
> number can relatively easily be doubled and result in that one is up
> against the limit (32).
>
> There are clearly choices that one can make to reduce the usage and save
> some number of PT values. My main concern is that one more mechanism
> that results in equal number of PTs of its own in regards to what it is
> associated with, is likely to cause significant concern. And we do have
> some that has the potential. Multi stream scalability or simulcast if we
> would require to indicate each codec configuration with its own payload
> type will increase the requirement with a significant factor.
>
> Thus, this is a potential issue, and an issue that can't be dismissed,
> just because your set of limitations makes it unlikely that you will run
> into it. We do need to ensure that mechanisms doesn't waste PT values to
> achieve some other gain. This is becoming a real limitation.
>
> Cheers
>
> Magnus Westerlund
>
> ----------------------------------------------------------------------
> Services, Media and Network features, Ericsson Research EAB/TXM
> ----------------------------------------------------------------------
> Ericsson AB                 | Phone  +46 10 7148287
> F=C3=A4r=C3=B6gatan 6                 | Mobile +46 73 0949079
> SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>

--089e0160c980ca716404f49479c1
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Agree this is a real limitation. In addition to the codecs=
 listed above, note that CN and telephone-event are often needed, and poten=
tially in multiple clockrates.<div><br></div><div>(which is why I think we =
shouldn&#39;t burn PTs on demultiplexing)<br>

<div><br></div><div><br></div></div></div><div class=3D"gmail_extra"><br><b=
r><div class=3D"gmail_quote">On Fri, Mar 14, 2014 at 2:56 AM, Magnus Wester=
lund <span dir=3D"ltr">&lt;<a href=3D"mailto:magnus.westerlund@ericsson.com=
" target=3D"_blank">magnus.westerlund@ericsson.com</a>&gt;</span> wrote:<br=
>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">MMUSIC,<br>
<br>
There&#39;s have been a number of people not believing in that RTP payload<=
br>
types may become a limiting factor when trying to express configurations<br=
>
in SDP or other signaling. Thus, I would like to share my concerns over<br>
how the combination of various mechanism effects the number of actual<br>
payload type configurations needed to negotiated.<br>
<br>
First a set of mechanism that do affect Payload Type usage.<br>
<br>
1. RTCP MUX (RFC 5761)<br>
If one uses RTCP RTP multiplexing, then a number of the RTP payload<br>
types are reserved for identifying the RTCP packets, rather than RTP<br>
payload formats. The default reservation is to reserve PT numbers 64-95.<br=
>
This limits the 128 PTs to 96 available ones.<br>
<br>
2. BUNDLE (draft-ietf-mmusic-sdp-bundle-negotiation)<br>
When using BUNDLE, all listed m=3D sections within a bundle group are in<br=
>
the same RTP session, thus all the PTs share a single common PT<br>
numbering space. Bundle has done what it can to allow re-use across the<br>
m=3D sections for the same configurations.<br>
<br>
3. Multi-Media RTP sessions (draft-ietf-avtcore-multi-media-rtp-session)<br=
>
This mechanism allows multiple media types, like audio, video and text<br>
to share the same RTP session. This in itself does not reduce the<br>
availability, but increases the number of codec configurations that<br>
might be required (or desired) to signal support for.<br>
<br>
4. RTP Retransmission (RFC 4588)<br>
RTP retransmission payload format, requires one PT per PT that one want<br>
to be able to retransmit. If the answer is all of the payload formats,<br>
this doubles the payload format consumption.<br>
<br>
5. XOR based FEC (RFC 5109)<br>
This RTP payload format would normally just consume one PT as it is<br>
capable of recovering the original PT field of a lost packet. However,<br>
it is commonly used with the redundancy payload format (RED) (RFC 2198).<br=
>
And RED requires one to have one RTP payload type per Redundancy<br>
combination. Thus, this results in at least as many PT as PTs one like<br>
to be able to apply FEC on.<br>
<br>
<br>
Lets try using the above in combination and see what the implications are.<=
br>
<br>
So we have 96 available values using RTCP mux, we like to use RTP<br>
Retransmission as well as XOR FEC, to be able to cope with whatever RTT<br>
the path provides and still be robust to packet losses within that<br>
single RTP session. Thus, we end up with a maximum of 32 PTs for<br>
encoding configurations.<br>
<br>
As this is an RTP session that contains both Audio and Video we need to<br>
create a number of configurations for both of media types. This endpoint<br=
>
do support a descent amount of codecs to be compatible with various systems=
.<br>
<br>
Audio: PCMA, PCMU, OPUS, AMR, AMR-WB, EVRC, EVRCWB, G.719, G.722, G.729<br>
Video: H.264, H.265, VP8, VP9, SVC<br>
<br>
On the audio side (10 codecs), this is actually a relative small subset<br>
of the audio codecs that may be carried in RTP. Considering the<br>
different configurations or annex extensions, there is no problem to<br>
actually triple this list when it comes to audio. For video these 5 is a<br=
>
selection of what might be in use in the near future. Also here there<br>
are some potential, although less to offer additional PTs based on the<br>
codec configurations. H.264 could run amok and offer a huge number if<br>
one have a codec implementation that supports many profiles, as each<br>
profile requires its own PT to be offered. As H.264 has 10+ profiles it<br>
is possible. But, a more realistic count is likely 3 PTs.<br>
<br>
The main point is that just the codecs listed above are themselves 15.<br>
With some need to have different configurations for some of them, the<br>
number can relatively easily be doubled and result in that one is up<br>
against the limit (32).<br>
<br>
There are clearly choices that one can make to reduce the usage and save<br=
>
some number of PT values. My main concern is that one more mechanism<br>
that results in equal number of PTs of its own in regards to what it is<br>
associated with, is likely to cause significant concern. And we do have<br>
some that has the potential. Multi stream scalability or simulcast if we<br=
>
would require to indicate each codec configuration with its own payload<br>
type will increase the requirement with a significant factor.<br>
<br>
Thus, this is a potential issue, and an issue that can&#39;t be dismissed,<=
br>
just because your set of limitations makes it unlikely that you will run<br=
>
into it. We do need to ensure that mechanisms doesn&#39;t waste PT values t=
o<br>
achieve some other gain. This is becoming a real limitation.<br>
<br>
Cheers<br>
<br>
Magnus Westerlund<br>
<br>
----------------------------------------------------------------------<br>
Services, Media and Network features, Ericsson Research EAB/TXM<br>
----------------------------------------------------------------------<br>
Ericsson AB =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 | Phone=
 =C2=A0+46 10 7148287<br>
F=C3=A4r=C3=B6gatan 6 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 | Mobile +46 73 0949079<br>
SE-164 80 Stockholm, Sweden | mailto: <a href=3D"mailto:magnus.westerlund@e=
ricsson.com">magnus.westerlund@ericsson.com</a><br>
----------------------------------------------------------------------<br>
<br>
_______________________________________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/mmusic</a><br>
</blockquote></div><br></div>

--089e0160c980ca716404f49479c1--


From nobody Fri Mar 14 10:38:33 2014
Return-Path: <juberti@google.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 BAD1F1A01A0 for <mmusic@ietfa.amsl.com>; Fri, 14 Mar 2014 10:38:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.925
X-Spam-Level: 
X-Spam-Status: No, score=-1.925 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001] autolearn=ham
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 pZS1DN1grOFL for <mmusic@ietfa.amsl.com>; Fri, 14 Mar 2014 10:38:29 -0700 (PDT)
Received: from mail-vc0-x232.google.com (mail-vc0-x232.google.com [IPv6:2607:f8b0:400c:c03::232]) by ietfa.amsl.com (Postfix) with ESMTP id E50111A01A6 for <mmusic@ietf.org>; Fri, 14 Mar 2014 10:38:28 -0700 (PDT)
Received: by mail-vc0-f178.google.com with SMTP id im17so3198560vcb.9 for <mmusic@ietf.org>; Fri, 14 Mar 2014 10:38:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=g/D3sEV75nh7DK0AyOCTtIQqXgPYbB5s5X2VJbHSWFg=; b=YFIar2+DN+uEjoSlxdpQ24b40qo8oTyJK/01S1LhZsVuRV6KyAVox/Yy9uyFVobeSz BNcH0mgDCWJ41hyTMsMwuq/fzFtm8yuvN15baUd2PQLatSMOSoZtMbuK5N6NysM95lPS lu9aBAsBJLSEOcvWXx+t1dC/xSBVHlAlCvX/QRsM4cvfQs7cy8Ra8s8eNspe7wunT/io JCm6QuAzpP4uuW2Hcriyn6H00m4BPo+w10AzoLGoStgy+M/U0IuvYn9tst41Owm61my1 v0DqQOHE1nbCwHKU+OPYI3FPXNYgX295RdLFm8MAzLsWNb/aOM1nNRsO4blr8PnBpJG5 4CqQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=g/D3sEV75nh7DK0AyOCTtIQqXgPYbB5s5X2VJbHSWFg=; b=WjYS2B2N3624lYKwjDg/+2Ku5+c8DPUn94WEsT0EBDYT9oWklpPWCbdcFuX6QaiGnR PoIlDjIOL5a3bA2LNoQZxjy9i5muuLg4uaEdkaRYJJnbeogETGQNCsUE3KqkBaOh7D8w 4GCnzou8aDu0dmPEuk/FQAy26vgWCG5uzqOqzYlliqa28Duhj5HM3IJjpLQjd/QfcLOz LHN2nXIA0OIREJw3S4wUEQCaMcEwQAm17xr3zg5pfDBzsVZ9631VBPEsRuB0YTGDc3cf 7jOMdXKPl8v52Nk6IjIn7WCDIXFamRKwGeMFpuk2dLfNpy4+7fNWNH6L5hZ5rH/S+Qdr 1G2g==
X-Gm-Message-State: ALoCoQnjES+DOnDKvd1vBKdL3OKwnsQVQqCAZdqAJml5CYmtd6kVZLIdZEh2PQSab8qrnEP+ZxdFrhmNYgHJKkN57vVsl5TgnnKpRFnvzt9b1ndOQKIKfOC7HCXFebprAFtcdVa/u7ZuHoo7mFXB+0h4O7yMerwIcE2AIjFkpniL4Fg76HnqgckPLR+i4eJ2Z67EkSvh7CF4
X-Received: by 10.52.15.132 with SMTP id x4mr1683746vdc.31.1394818701875; Fri, 14 Mar 2014 10:38:21 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.26.43 with HTTP; Fri, 14 Mar 2014 10:38:01 -0700 (PDT)
In-Reply-To: <CABkgnnWSAdcQ+xbFc7TqMMaRbwWy+=APzSNp_nXAQ1HCDh2E3A@mail.gmail.com>
References: <CAOJ7v-3oi-Qtsk6qiPVsAUfzEQsvgt4h6RhgfKDNUv_-47wpOA@mail.gmail.com> <BFFAE2A7-089D-452F-867E-BEF622BEFB77@cisco.com> <CAOJ7v-0d1bng-LHkdZ+J3Swdoic+zOF73JVfK464N0n4fY9=fw@mail.gmail.com> <9450C3A0-9509-4D1E-8C6C-54B884086B38@cisco.com> <CAOJ7v-3Z=x=1kDuB3LCu3g1gZ6M4BytrwbJ3FJnjOpAy-um6PQ@mail.gmail.com> <CABkgnnWSAdcQ+xbFc7TqMMaRbwWy+=APzSNp_nXAQ1HCDh2E3A@mail.gmail.com>
From: Justin Uberti <juberti@google.com>
Date: Fri, 14 Mar 2014 10:38:01 -0700
Message-ID: <CAOJ7v-3OE3-ZtW8s+-tT8Xu0b6x7N8DJTaozucYc-9A8wJB5=w@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Content-Type: multipart/alternative; boundary=20cf3033474140812304f4948975
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/LDUgzGjTbA08b6Bmyy2Fcl6aLx0
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Dan Wing <dwing@cisco.com>
Subject: Re: [MMUSIC] Generalizing the aggressive nomination bugfix
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: Fri, 14 Mar 2014 17:38:31 -0000

--20cf3033474140812304f4948975
Content-Type: text/plain; charset=UTF-8

On Thu, Mar 13, 2014 at 9:57 AM, Martin Thomson <martin.thomson@gmail.com>wrote:

> On 12 March 2014 22:11, Justin Uberti <juberti@google.com> wrote:
> > Agreed. The ability to mark an interface as only-if-absolutely-necessary
> > seems like it would suffice. The controlling side would then only switch
> to
> > such a candidate if no other pair was viable, similar to the handling of
> > backup paths in 6824.
>
> That might be a useful function to exploit to shift traffic away from
> relays as well.
>

That seems more nuanced. If you are getting a better RTT running through a
relay, the app will probably want to use it, so we would need some way to
specify that a relay is 'only-if-needed' or not (either in RTCIceServer, or
part of TURN)

--20cf3033474140812304f4948975
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Thu, Mar 13, 2014 at 9:57 AM, Martin Thomson <span dir=3D"ltr">&=
lt;<a href=3D"mailto:martin.thomson@gmail.com" target=3D"_blank">martin.tho=
mson@gmail.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"">On 12 March 2014 22:11, Just=
in Uberti &lt;<a href=3D"mailto:juberti@google.com">juberti@google.com</a>&=
gt; wrote:<br>


&gt; Agreed. The ability to mark an interface as only-if-absolutely-necessa=
ry<br>
&gt; seems like it would suffice. The controlling side would then only swit=
ch to<br>
&gt; such a candidate if no other pair was viable, similar to the handling =
of<br>
&gt; backup paths in 6824.<br>
<br>
</div>That might be a useful function to exploit to shift traffic away from=
<br>
relays as well.<br></blockquote><div><br></div><div>That seems more nuanced=
. If you are getting a better RTT running through a relay, the app will pro=
bably want to use it, so we would need some way to specify that a relay is =
&#39;only-if-needed&#39; or not (either in RTCIceServer, or part of TURN)</=
div>

</div><br></div></div>

--20cf3033474140812304f4948975--


From nobody Fri Mar 14 10:41:54 2014
Return-Path: <pkyzivat@alum.mit.edu>
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 967231A018C for <mmusic@ietfa.amsl.com>; Fri, 14 Mar 2014 10:41:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] 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 UGyhYRG__JvU for <mmusic@ietfa.amsl.com>; Fri, 14 Mar 2014 10:41:51 -0700 (PDT)
Received: from qmta01.westchester.pa.mail.comcast.net (qmta01.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:16]) by ietfa.amsl.com (Postfix) with ESMTP id A7E911A0170 for <mmusic@ietf.org>; Fri, 14 Mar 2014 10:41:51 -0700 (PDT)
Received: from omta04.westchester.pa.mail.comcast.net ([76.96.62.35]) by qmta01.westchester.pa.mail.comcast.net with comcast id dPqU1n0010ldTLk51Vhkac; Fri, 14 Mar 2014 17:41:44 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta04.westchester.pa.mail.comcast.net with comcast id dVhk1n0053ZTu2S01Vhkqu; Fri, 14 Mar 2014 17:41:44 +0000
Message-ID: <53233F58.7050303@alum.mit.edu>
Date: Fri, 14 Mar 2014 13:41:44 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>,  "mmusic@ietf.org" <mmusic@ietf.org>
References: <53185B8E.2070808@nteczone.com> <C8EB64C0-3140-477C-9373-BD36B4B1A64B@ericsson.com> <53187415.2000108@nteczone.com> <C1D662DF-E3E3-45CD-991F-8090CD7130E0@ericsson.com> <531881CF.2010105@nteczone.com> <7594FB04B1934943A5C02806D1A2204B1D212B7E@ESESSMB209.ericsson.se> <5321BFBC.30304@alum.mit.edu> <5322AFD9.8090108@nteczone.com> <532320A8.6050302@alum.mit.edu> <786615F3A85DF44AA2A76164A71FE1AC1B3422@FR711WXCHMBA03.zeu.alcatel-lucent.com>
In-Reply-To: <786615F3A85DF44AA2A76164A71FE1AC1B3422@FR711WXCHMBA03.zeu.alcatel-lucent.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1394818904; bh=Pm0N2CS3mrveJi/Rsj00FhifAZY9HPozeObS8U0f2zU=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=NEbesk9bKDE4YUgWzYS7f7PDYhXfZsO+5oa1xqnhYsks07ibZl6x4dEXkaB2o9mzi 3N59Ec9lTRSBQb7VNgce97FGyBHAZZCJGMNWSGTyKR4EbL8wOiCONdsmWP33qQ8zDZ A7YMjTM+pDs9wbYa+T3mzxOAUXiPL7PCrTOl7C6Jrye44AiL5YwXbkJcKwxq25i5Md N/0hkIMRJYe+hiJsBNHWVrjpfzBXdCTAHY9I8EYi/IpD9Qdz6OFPTEW7LPPAH9wWek 4Iiu2oDdj3LjI55LA/g5WUiR+APZJF00mh5YoBtST+Cxl1FQBKOEGrcsEf/U41nH3c NG2U1QxlatVoA==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/TCkBVQcne5ybvKdXzPwEX2LfLC0
Subject: Re: [MMUSIC] SCTP AppID
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: Fri, 14 Mar 2014 17:41:53 -0000

On 3/14/14 12:15 PM, Schwarz, Albrecht (Albrecht) wrote:
>> This is the problem with using the term "app" here.
>
> Guess the issue of naming/terminology is related to "protocol layer".
> Perhaps a way forward could be to look at the more abstract model of "layered services", rather the "layered protocol architecture" everyone has in mind.
> Such a generic model could be based ITU-T X.200, § 5.7 "The nature of the (N)-service", which is fairly generic.
>
> Here, a "layered service" model could look like (just assigning 'N' to the SCTP association service):
>
> Service:
> - Application       (N+2)-service
> - SCTP Stream       (N+1)-service
> - SCTP Association   (N)-service
> - SCTP Path         (N-1)-service
> - DTLS Session      (N-2)-service
> - UDP Transport     (N-3)-service
> - IP connection     (N-4)-service
>
> Such a model may allow to overcome the naming, terminology issue (where the single protocol layer "SCTP" aggregates the three services N-1, N and N+1).
>
> The DC protocol would use the (N+1)-service.
> An application could use an (N+1)-service ("application multiplexing over a single SCTP Assoc"), or an (N)-service ("1:1 mapping between application an SCTP Assoc").

The above is helpful for the discussion. But the situation is a little 
more complicated.

DC and DCEP aren't per-SCTP-stream. DC defines that pairs of opposite 
direction streams having the same ID are bound together to form a 
channel. And DCEP defines how channels are assigned. Those behaviors 
don't stack neatly on top of an SCTP Stream.

My view is that DC & DCEP "own" an SCTP Association, and present a new 
Data Channel interface as well as a mechanism for assigning and 
releasing data channels. IMO this isn't an "application", but that 
determination is very subjective depending on your viewpoint. (And is 
the reason not to use that word.)

Perhaps the thing on top of an SCTP Association could be called an SCTP 
Association Usage.

	Thanks,
	Paul

> Regards,
> Albrecht
>
> PS
> Of course, not every x-service is visible from signalling plane, etc
>
>
>
> -----Original Message-----
> From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Paul Kyzivat
> Sent: Freitag, 14. März 2014 16:31
> To: mmusic@ietf.org
> Subject: Re: [MMUSIC] SCTP AppID
>
> On 3/14/14 3:29 AM, Christian Groves wrote:
>>
>> On 14/03/2014 1:25 AM, Paul Kyzivat wrote:
>>> On 3/13/14 9:32 AM, Christer Holmberg wrote:
>>>> Hi Christian,
>>>>
>>>>> Do you have an answer for the second part of the previous email?
>>>>> i.e One thing I'm still missing is how you specify multiple
>>>>> app/alpns (whatever we're calling them) being used in a single SCTP
>>>>> association, without using datachannel?
>>>>
>>>> My understanding is that it is no longer possible. You can only
>>>> assign *one* sctpmap attribute (e.g. indicating webrtc-datachannel)
>>>> to any given SCTPoDTLS m- line.
>>>
>>> I never understood this question. This is describing the use of the
>>> association as a whole, not not a particular channel.
>> [CNG] I didn't mention channel. I am talking about the association as
>> a whole. The sctpmap attribute indicates what app is in the SCTP
>> association. The current syntax only allows one app. So basically I
>> can run "foo" over an SCTP association natively but as soon as I want
>> to run "foo" and "bar" over an SCTP association I need to use the
>> webrtc-datachannel protocol.
>>
>> I just wanted to check that behavior was planned not just as an
>> unplanned consequence of updated the draft version.
>
> This is the problem with using the term "app" here.
> *Something* must coordinate the overall use of the association. Having multiple things use it without coordination won't work. If you have multiple "applications", they could coexist by using DCEP to assign data channels for each application. But then DCEP, and Data Channels in general, is the "app" on top of SCTP. (Even then, the multiple apps need to agree on naming of channels in order to coexist.)
>
> IMO what you are actually naming here is a *convention* for use of the association and the streams it contains.
>
> 	Thanks,
> 	Paul
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>


From nobody Fri Mar 14 11:41:33 2014
Return-Path: <alissa@cooperw.in>
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 408391A01A0 for <mmusic@ietfa.amsl.com>; Fri, 14 Mar 2014 11:41:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.298
X-Spam-Level: 
X-Spam-Status: No, score=-1.298 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
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 Z-gowZYO_r4G for <mmusic@ietfa.amsl.com>; Fri, 14 Mar 2014 11:41:30 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 424511A0188 for <mmusic@ietf.org>; Fri, 14 Mar 2014 11:41:30 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 366DF211C3; Fri, 14 Mar 2014 14:41:23 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute3.internal (MEProxy); Fri, 14 Mar 2014 14:41:23 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=cooperw.in; h=date :subject:from:to:message-id:mime-version:content-type; s=mesmtp; bh=dWjFCHhbaM5rijm6Th+RU38EBvU=; b=kSRFnoui13ABU9RSMomnXKbZX/1f mQmcCtVl/IBsI4QzeaYhx5/qG11SK+bRKttWafbnc9NHFfN438W27qh5zXKumthf lpFEuL10TR9uY5Lsj5j+DH202jQYnntmXaWapCy1WEXDGJ2PbKeK0Hb/ivTPwQCe sxHxRwnqKlYqj5M=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=date:subject:from:to:message-id :mime-version:content-type; s=smtpout; bh=dWjFCHhbaM5rijm6Th+RU3 8EBvU=; b=tFq6G7R5jbNLbsFRyEgOEAHtCom/CWEFGyne50GbWz34PlBvvaO+U0 9XVCp8a+Y8b/J6PbX5PnHz/31bh5DTuatZ5+enOshog4CBR3wbwLbUd+TEt1mGFH 7OU4TD6X5Hk/RIwzm5+XPs7a4tCC/e11Hgd/dwdbLWV3b1yBRdCgg=
X-Sasl-enc: bcrJlryIugmEarATf2AYqY1Cn8C4Yu3n1WwT46Vl+zFQ 1394822482
Received: from [171.68.18.51] (unknown [171.68.18.51]) by mail.messagingengine.com (Postfix) with ESMTPA id A0773680237; Fri, 14 Mar 2014 14:41:21 -0400 (EDT)
User-Agent: Microsoft-MacOutlook/14.3.9.131030
Date: Fri, 14 Mar 2014 11:41:17 -0700
From: Alissa Cooper <alissa@cooperw.in>
To: <mmusic@ietf.org>, <draft-ietf-mmusic-latching@tools.ietf.org>
Message-ID: <CF489B5D.25EB0%alissa@cooperw.in>
Thread-Topic: AD evaluation: draft-ietf-mmusic-latching-04
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3477642082_60078394"
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/YAnNPqwjE_ZLeNoQnTdB2D0DZhw
Subject: [MMUSIC] AD evaluation: draft-ietf-mmusic-latching-04
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: Fri, 14 Mar 2014 18:41:32 -0000

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3477642082_60078394
Content-type: text/plain;
	charset="US-ASCII"
Content-transfer-encoding: 7bit

I have reviewed this draft in preparation for IETF LC. I have one issue that
I'd like to see the group discuss before issuing the LC: Section 1 says "the
latching mechanism is considered inappropriate for general use on the
Internet unless all security considerations are taken into account and
solved." But given the lack of mitigations for attacks originating from
behind large-scale NATs as described in Section 5, it's not obvious to me
that that condition can realistically be met. If it can't be, it seems to me
that this document should be making a stronger statement about the
inappropriateness of latching.

Also, I found a  couple of nits to address with any LC comments:

Section 1:

s/handle traffic in way that/handle traffic in a way that/

Section 2:

s/UA sends packet out first/UA sends packets out first/

Section 4:

s/IETF members/IETF participants/ (two occurrences)

s/the one the best suits/the one that best suits/

s/address information in in offers/address information in offers/

There is an in-text reference to "[tcp-splicing]," but there is no such
reference in the references section.



--B_3477642082_60078394
Content-type: text/html;
	charset="US-ASCII"
Content-transfer-encoding: quoted-printable

<html><head></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: s=
pace; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size:=
 14px; font-family: Calibri, sans-serif; "><div><div style=3D"font-family: Con=
solas, monospace; font-size: 12px; ">I have reviewed this draft in preparati=
on for IETF LC. I have one issue that I'd like to see the group discuss befo=
re issuing the LC: Section 1 says&nbsp;"the latching&nbsp;mechanism is consi=
dered inappropriate for general use on the Internet&nbsp;unless all security=
 considerations are taken into account and solved." But given the lack of mi=
tigations for attacks originating from behind large-scale NATs as described =
in Section 5, it's not obvious to me that that condition can realistically b=
e met. If it can't be, it seems to me that this document should be making a =
stronger statement about the inappropriateness of latching.</div><div style=3D=
"font-family: Consolas, monospace; font-size: 12px; "><br></div><div style=3D"=
font-family: Consolas, monospace; font-size: 12px; ">Also, I found a &nbsp;c=
ouple of nits to address with any LC comments:</div><div style=3D"font-family:=
 Consolas, monospace; font-size: 12px; "><br></div><div style=3D"font-family: =
Consolas, monospace; font-size: 12px; ">Section 1:</div><div style=3D"font-fam=
ily: Consolas, monospace; font-size: 12px; "><br></div><div style=3D"font-fami=
ly: Consolas, monospace; font-size: 12px; ">s/handle traffic in way that/han=
dle traffic in a way that/</div><div style=3D"font-family: Consolas, monospace=
; font-size: 12px; "><br></div><div style=3D"font-family: Consolas, monospace;=
 font-size: 12px; ">Section 2:</div><div style=3D"font-family: Consolas, monos=
pace; font-size: 12px; "><br></div><div style=3D"font-family: Consolas, monosp=
ace; font-size: 12px; ">s/UA sends packet out first/UA sends packets out fir=
st/</div><div style=3D"font-family: Consolas, monospace; font-size: 12px; "><b=
r></div><div style=3D"font-family: Consolas, monospace; font-size: 12px; ">Sec=
tion 4:</div><div style=3D"font-family: Consolas, monospace; font-size: 12px; =
"><br></div><div style=3D"font-family: Consolas, monospace; font-size: 12px; "=
>s/IETF members/IETF participants/ (two occurrences)</div><div style=3D"font-f=
amily: Consolas, monospace; font-size: 12px; "><br></div><div style=3D"font-fa=
mily: Consolas, monospace; font-size: 12px; ">s/the one the best suits/the o=
ne that best suits/</div><div style=3D"font-family: Consolas, monospace; font-=
size: 12px; "><br></div><div style=3D"font-family: Consolas, monospace; font-s=
ize: 12px; ">s/address information in in offers/address information in offer=
s/</div><div style=3D"font-family: Consolas, monospace; font-size: 12px; "><br=
></div><div style=3D"font-family: Consolas, monospace; font-size: 12px; ">Ther=
e is an in-text reference to "[tcp-splicing]," but there is no such referenc=
e in the references section.</div></div></body></html>

--B_3477642082_60078394--



From nobody Sat Mar 15 08:22:14 2014
Return-Path: <juberti@google.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 E7B361A0289 for <mmusic@ietfa.amsl.com>; Sat, 15 Mar 2014 08:22:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.925
X-Spam-Level: 
X-Spam-Status: No, score=-1.925 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001] autolearn=ham
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 OSk_lBk2AubL for <mmusic@ietfa.amsl.com>; Sat, 15 Mar 2014 08:22:11 -0700 (PDT)
Received: from mail-ve0-x235.google.com (mail-ve0-x235.google.com [IPv6:2607:f8b0:400c:c01::235]) by ietfa.amsl.com (Postfix) with ESMTP id 31AAC1A0175 for <mmusic@ietf.org>; Sat, 15 Mar 2014 08:22:11 -0700 (PDT)
Received: by mail-ve0-f181.google.com with SMTP id oy12so4062619veb.12 for <mmusic@ietf.org>; Sat, 15 Mar 2014 08:22:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=hy4szna/HdXbk0PmuDtCyWvI93GA7Sf8frI4HwYrwGQ=; b=n7468bwRJZbjqsbEvcrt2HHKd7KoJhAQ6If340oQWlF61lrmQwYf6EU6BM2YER0lqh LL+U33kuSHTaKqqWcHBi1fjvn7NQM6v6qQbpGDv+5gUfaeXvBKWirIE5VGoRZBLx4foC vyfTFSNhvOmzB3jLgXQ4Bdcy73HdOxn9s1zP54sou0YGI4ydvrtS0Lw5YX0Usi4R/bZK RtbrUDbUdfZE+USLfY7FU4spS1Rdwx8+zyPVlEO0KmhUDnvEokTMs/JnR4vua7MEMvQn 7aqW4i87kj6KnC+heW8T0N47KzCMsjv/Whve/EH96Yt8XySdFtiWnZQJi5YtIgsC+kcc c0zA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=hy4szna/HdXbk0PmuDtCyWvI93GA7Sf8frI4HwYrwGQ=; b=duaOy3hYx7qpggCmsxv6NO7/Aj3pk9qqopFuT88DXGg04jxo4/PBL1KdRWkUKLNmy7 3tuNdu5nhQgfMEz9m59lj+nQyCC1vcco2VKYVcVSgEXEAGfBz1eSb3ad1RRC+zhx5SMR urYi+S79k0u/65TF+RFGC0OwjW88pDUYbqubS1E2UxCTpW9UixvQePP3dlFG4j/3ngOL it60nZ9AV66YjccqjnRiqd3/wwT8X3j8xf+LNZkCEz+AkDIUoY4JSAlPGsveEB6CKsx9 qetLOYoaF/hEHOFTHkoeIVSCF87mc8waA/ialMEX3wGXa+9hpqADb0gcMyiCJYi7VlA4 O3Zw==
X-Gm-Message-State: ALoCoQm3tgjbWbulL+K2lNOhPf246OdMaizeLXcpFA5jA6mByxXsHH37RRNDm57oKCqe91CyuJ/TpdTSaMeXXtCHUgz+fV2ibvkvn293Omo4GwtaHXetPjJo5F5iS4SWgiigFc3NmmneDYV4oQlrYDuWKGtwqT5xQ6e8kQagQ3jars1NoSU23Nf2BAzC7uZSk/R4TVCwEEi1
X-Received: by 10.52.69.146 with SMTP id e18mr9669137vdu.15.1394896923643; Sat, 15 Mar 2014 08:22:03 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.26.43 with HTTP; Sat, 15 Mar 2014 08:21:43 -0700 (PDT)
In-Reply-To: <CAOJ7v-3OE3-ZtW8s+-tT8Xu0b6x7N8DJTaozucYc-9A8wJB5=w@mail.gmail.com>
References: <CAOJ7v-3oi-Qtsk6qiPVsAUfzEQsvgt4h6RhgfKDNUv_-47wpOA@mail.gmail.com> <BFFAE2A7-089D-452F-867E-BEF622BEFB77@cisco.com> <CAOJ7v-0d1bng-LHkdZ+J3Swdoic+zOF73JVfK464N0n4fY9=fw@mail.gmail.com> <9450C3A0-9509-4D1E-8C6C-54B884086B38@cisco.com> <CAOJ7v-3Z=x=1kDuB3LCu3g1gZ6M4BytrwbJ3FJnjOpAy-um6PQ@mail.gmail.com> <CABkgnnWSAdcQ+xbFc7TqMMaRbwWy+=APzSNp_nXAQ1HCDh2E3A@mail.gmail.com> <CAOJ7v-3OE3-ZtW8s+-tT8Xu0b6x7N8DJTaozucYc-9A8wJB5=w@mail.gmail.com>
From: Justin Uberti <juberti@google.com>
Date: Sat, 15 Mar 2014 08:21:43 -0700
Message-ID: <CAOJ7v-1TaBRn3sL7zNLw2hy-XmJpxMux2kx74ddcD6D_hP7O5Q@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Content-Type: multipart/alternative; boundary=20cf3071cd0ea1f03704f4a6bf15
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/eIrF0eICb2A7tlSgQebyUlkVjHw
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Dan Wing <dwing@cisco.com>
Subject: Re: [MMUSIC] Generalizing the aggressive nomination bugfix
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: Sat, 15 Mar 2014 15:22:13 -0000

--20cf3071cd0ea1f03704f4a6bf15
Content-Type: text/plain; charset=UTF-8

What do you suggest as next steps here? This seems like something that
should go into ICE-bis; should this be filed as errata against 5245, or
written up as a separate I-D?


On Fri, Mar 14, 2014 at 10:38 AM, Justin Uberti <juberti@google.com> wrote:

>
>
>
> On Thu, Mar 13, 2014 at 9:57 AM, Martin Thomson <martin.thomson@gmail.com>wrote:
>
>> On 12 March 2014 22:11, Justin Uberti <juberti@google.com> wrote:
>> > Agreed. The ability to mark an interface as only-if-absolutely-necessary
>> > seems like it would suffice. The controlling side would then only
>> switch to
>> > such a candidate if no other pair was viable, similar to the handling of
>> > backup paths in 6824.
>>
>> That might be a useful function to exploit to shift traffic away from
>> relays as well.
>>
>
> That seems more nuanced. If you are getting a better RTT running through a
> relay, the app will probably want to use it, so we would need some way to
> specify that a relay is 'only-if-needed' or not (either in RTCIceServer, or
> part of TURN)
>
>

--20cf3071cd0ea1f03704f4a6bf15
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">What do you suggest as next steps here? This seems like so=
mething that should go into ICE-bis; should this be filed as errata against=
 5245, or written up as a separate I-D?</div><div class=3D"gmail_extra"><br=
>

<br><div class=3D"gmail_quote">On Fri, Mar 14, 2014 at 10:38 AM, Justin Ube=
rti <span dir=3D"ltr">&lt;<a href=3D"mailto:juberti@google.com" target=3D"_=
blank">juberti@google.com</a>&gt;</span> wrote:<br><blockquote class=3D"gma=
il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef=
t:1ex">

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote"><div><div class=3D"h5">On Thu, Mar 13, 2014 at 9:57 AM, Martin Thom=
son <span dir=3D"ltr">&lt;<a href=3D"mailto:martin.thomson@gmail.com" targe=
t=3D"_blank">martin.thomson@gmail.com</a>&gt;</span> wrote:<br>


<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div>On 12 March 2014 22:11, Justin Uberti &=
lt;<a href=3D"mailto:juberti@google.com" target=3D"_blank">juberti@google.c=
om</a>&gt; wrote:<br>



&gt; Agreed. The ability to mark an interface as only-if-absolutely-necessa=
ry<br>
&gt; seems like it would suffice. The controlling side would then only swit=
ch to<br>
&gt; such a candidate if no other pair was viable, similar to the handling =
of<br>
&gt; backup paths in 6824.<br>
<br>
</div>That might be a useful function to exploit to shift traffic away from=
<br>
relays as well.<br></blockquote><div><br></div></div></div><div>That seems =
more nuanced. If you are getting a better RTT running through a relay, the =
app will probably want to use it, so we would need some way to specify that=
 a relay is &#39;only-if-needed&#39; or not (either in RTCIceServer, or par=
t of TURN)</div>


</div><br></div></div>
</blockquote></div><br></div>

--20cf3071cd0ea1f03704f4a6bf15--


From nobody Sat Mar 15 10:41:25 2014
Return-Path: <cmatsuura@vivint.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 9E47E1A017D for <mmusic@ietfa.amsl.com>; Sat, 15 Mar 2014 10:41:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham
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 rbrUFXgrJ6D9 for <mmusic@ietfa.amsl.com>; Sat, 15 Mar 2014 10:41:21 -0700 (PDT)
Received: from inferno.apxalarm.com (inferno.apxalarm.com [65.181.58.40]) by ietfa.amsl.com (Postfix) with ESMTP id 6D2EE1A017B for <mmusic@ietf.org>; Sat, 15 Mar 2014 10:41:21 -0700 (PDT)
Received: from MAILBOX.APEX.Local ([192.168.0.1]) by mail01.APEX.Local ([10.2.0.11]) with mapi; Sat, 15 Mar 2014 11:41:13 -0600
From: Craig Matsuura <cmatsuura@vivint.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>, "mmusic@ietf.org" <mmusic@ietf.org>
Date: Sat, 15 Mar 2014 11:41:12 -0600
Thread-Topic: [MMUSIC] RTSP questions in regards to the control channel socket
Thread-Index: Ac9AdcH/WGtXjQZpT8y68D7aJEG83Q==
Message-ID: <532490B8.7020208@vivint.com>
References: <53223DAA.4040107@vivint.com> <5322D749.8020306@ericsson.com>
In-Reply-To: <5322D749.8020306@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/MQvqNamZIVxf33hx12QPh2F6e0E
Subject: Re: [MMUSIC] RTSP questions in regards to the control channel socket
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: Sat, 15 Mar 2014 17:41:23 -0000

Hi Magnus,

Thanks for your response, to be clear when I was referring to a Control=20
Socket I mean the connection that sends commands such as the DESCRIBE,=20
OPTIONS, SETUP.  So to restate, it should not matter if a connection for=20
the transports comes or goes to server.  For example if a server flow to=20
a client is:

C->S - Send DESCRIBE Command, C gets 200 response from S.
Close connection and start new connection
C->S - Send OPTIONS command, C gets 200 response from S.
Close connection and start new connection
C->S - Send SETUP command, C gets ??? response from S.

So at the SETUP the response should be 200? or fail (400)?  I'm trying=20
to clear up an issue I have with a vendors RTSP Server implementation=20
and would like to know if the sequence above should work to a RTSP=20
Server.  Based on the Section 1.1 and 1.7 seems the above should work. =20
The only issue would be after the SETUP the session id needs to=20
accompany commands that follow?

Thanks,
Craig


On 03/14/2014 04:17 AM, Magnus Westerlund wrote:
> On 2014-03-14 00:22, Craig Matsuura wrote:
>> Hi this is my first time posting here.  I have a basic question about
>> how a RTSP server should handled a connect and disconnect for what I am
>> calling the control channel (connection or transport). The control
>> channel (please correct me) is what sends the DESCRIBE, SETUP, OPTIONS,
>> PLAY commands to the RTSP SERVER.
>>
>> Should a server treat the first DESCRIBE connection as its session. So
>> in the case where a socket connects to a RTSP server and sends a
>> DESCRIBE, is disconnected either by the client or some failure on the
>> server should the following SETUP succeed?
> No, DESCRIBE is a state less operation. If one needs a linkage between
> the Describe response body and the setup, then one should use etags and
> conditional requests to ensure that one is establishing the session with
> a relevant session description.
>
>> Also if using a RTSP Proxy and in the same scenario, but after the
>> DESCRIBE and closing of the socket a new socket is open to send an
>> OPTIONS (for keepalive) should the following SETUP succeed?
> Yes the SETUP should succeed if otherwise valid.
>
>>   From what I understood from the RFC2326 Section 1.7 RTSP State, it
>> should not matter how many connections are used to control the RTSP Stre=
am.
>>
>> 1. Control Socket is not prevent a client from connecting and
>> disconnecting to send Transport commands.
> I am uncertain what you mean with the Control socket, if you means the
> Socket the server listens to incoming TCP connection establishments and
> their data, it needs to be accepting those comming and going.
>
>> 2. The keep-alive for a session should not start until a SETUP command,
>> which can optional report the timeout for the session.
> Exact, the keep-alive is associated with the RTSP session, not the
> signalling connection used to send RTSP requests and response between
> the server and client.
>
> You might find RTSP 2.0's text on this being clearer:
> https://datatracker.ietf.org/doc/draft-ietf-mmusic-rfc2326bis/
>
> Cheers
>
> Magnus Westerlund
>
> ----------------------------------------------------------------------
> Services, Media and Network features, Ericsson Research EAB/TXM
> ----------------------------------------------------------------------
> Ericsson AB                 | Phone  +46 10 7148287
> F=E4r=F6gatan 6                 | Mobile +46 73 0949079
> SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
>


From nobody Sun Mar 16 07:16:50 2014
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 9F2331A02ED for <mmusic@ietfa.amsl.com>; Sun, 16 Mar 2014 07:16:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.251
X-Spam-Level: 
X-Spam-Status: No, score=-3.251 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, J_CHICKENPOX_17=0.6, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 P75yn4YgzmD2 for <mmusic@ietfa.amsl.com>; Sun, 16 Mar 2014 07:16:45 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id F33581A02DF for <mmusic@ietf.org>; Sun, 16 Mar 2014 07:16:44 -0700 (PDT)
X-AuditID: c1b4fb2d-b7f5d8e000002a7b-59-5325b2433aef
Received: from ESESSHC014.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id 48.78.10875.342B5235; Sun, 16 Mar 2014 15:16:36 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.213]) by ESESSHC014.ericsson.se ([153.88.183.60]) with mapi id 14.02.0387.000; Sun, 16 Mar 2014 15:16:35 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Justin Uberti <juberti@google.com>, Magnus Westerlund <magnus.westerlund@ericsson.com>
Thread-Topic: BUNDLE Q14: Mandate usage of RTP/RTCP mux within a BUNDLE group? [was: On the sparsity of RTP Payload types]
Thread-Index: AQHPQSJW5SOYVCaDbkiksfP7ze4/Vw==
Date: Sun, 16 Mar 2014 14:16:34 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D23329D@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.20]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrILMWRmVeSWpSXmKPExsUyM+Jvja7LJtVgg/3XOCy2ThWymLr8MYsD k8eCTaUeS5b8ZApgiuKySUnNySxLLdK3S+DK2L9tNmPBTIOKJ1ufsTcwzlLvYuTkkBAwkfj0 8ygrhC0mceHeerYuRi4OIYFDjBJP329khXCWMEpc2bOJvYuRg4NNwEKi+582iCkiECPx7mgx SC+zgLpEz+8WZhBbWKBc4vqLpUwgtohAjcTNVbuZIWw9iZuX3rKA2CwCqhIbN1xlBLF5BXwl dt9YDVbDCHTD91NrmCBmikvcejKfCeI2AYkle84zQ9iiEi8f/4O6WVHi6vTlUPV6EjemTmGD sLUlli18zQwxX1Di5MwnLBMYRWYhGTsLScssJC2zkLQsYGRZxciem5iZk15uuIkRGOwHt/zW 3cF46pzIIUZpDhYlcd4Pb52DhATSE0tSs1NTC1KL4otKc1KLDzEycXBKNTDy6vkv8bVjvuX5 6UfPpjSNgwzXyiNu3LvanynqdTjj9HTT3L8pN45e/9R5MO1fz0szhymyTJyZcasKdszy6jMR FWL/e/qhnGDNPe0tt3u+eDCYs6bar1D6fyRHV8wqwsrw6i+He0c/rn54sPDiKVem/18F7oXZ WE1PPHbE+LJ0zv8Z2vfKVsYosRRnJBpqMRcVJwIAQoPRqEQCAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/upRELrzm_GmGIYlwgK6MiffcgbA
Cc: "mmusic \(E-mail\)" <mmusic@ietf.org>
Subject: [MMUSIC] BUNDLE Q14: Mandate usage of RTP/RTCP mux within a BUNDLE group? [was: On the sparsity of RTP Payload types]
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: Sun, 16 Mar 2014 14:16:48 -0000

Hi,

Do other people have opinions on this?

Just to clarify: the support of RTP/RTCP mux is already mandated in BUNDLE,=
 and question is not whether the included the a=3Drtcpmux attribute or not =
when RTP/RTCP mux is used - it shall be included. The question is whether w=
e should mandate usage of RTP/RTCP mux within a BUNDLE group.

Regards,

Christer



________________________________________
From: mmusic [mmusic-bounces@ietf.org] on behalf of Justin Uberti [juberti@=
google.com]
Sent: Friday, 14 March 2014 7:33 PM
To: Magnus Westerlund
Cc: mmusic (E-mail)
Subject: Re: [MMUSIC] On the sparsity of RTP Payload types

Agree this is a real limitation. In addition to the codecs listed above, no=
te that CN and telephone-event are often needed, and potentially in multipl=
e clockrates.

(which is why I think we shouldn't burn PTs on demultiplexing)




On Fri, Mar 14, 2014 at 2:56 AM, Magnus Westerlund <magnus.westerlund@erics=
son.com<mailto:magnus.westerlund@ericsson.com>> wrote:
MMUSIC,

There's have been a number of people not believing in that RTP payload
types may become a limiting factor when trying to express configurations
in SDP or other signaling. Thus, I would like to share my concerns over
how the combination of various mechanism effects the number of actual
payload type configurations needed to negotiated.

First a set of mechanism that do affect Payload Type usage.

1. RTCP MUX (RFC 5761)
If one uses RTCP RTP multiplexing, then a number of the RTP payload
types are reserved for identifying the RTCP packets, rather than RTP
payload formats. The default reservation is to reserve PT numbers 64-95.
This limits the 128 PTs to 96 available ones.

2. BUNDLE (draft-ietf-mmusic-sdp-bundle-negotiation)
When using BUNDLE, all listed m=3D sections within a bundle group are in
the same RTP session, thus all the PTs share a single common PT
numbering space. Bundle has done what it can to allow re-use across the
m=3D sections for the same configurations.

3. Multi-Media RTP sessions (draft-ietf-avtcore-multi-media-rtp-session)
This mechanism allows multiple media types, like audio, video and text
to share the same RTP session. This in itself does not reduce the
availability, but increases the number of codec configurations that
might be required (or desired) to signal support for.

4. RTP Retransmission (RFC 4588)
RTP retransmission payload format, requires one PT per PT that one want
to be able to retransmit. If the answer is all of the payload formats,
this doubles the payload format consumption.

5. XOR based FEC (RFC 5109)
This RTP payload format would normally just consume one PT as it is
capable of recovering the original PT field of a lost packet. However,
it is commonly used with the redundancy payload format (RED) (RFC 2198).
And RED requires one to have one RTP payload type per Redundancy
combination. Thus, this results in at least as many PT as PTs one like
to be able to apply FEC on.


Lets try using the above in combination and see what the implications are.

So we have 96 available values using RTCP mux, we like to use RTP
Retransmission as well as XOR FEC, to be able to cope with whatever RTT
the path provides and still be robust to packet losses within that
single RTP session. Thus, we end up with a maximum of 32 PTs for
encoding configurations.

As this is an RTP session that contains both Audio and Video we need to
create a number of configurations for both of media types. This endpoint
do support a descent amount of codecs to be compatible with various systems=
.

Audio: PCMA, PCMU, OPUS, AMR, AMR-WB, EVRC, EVRCWB, G.719, G.722, G.729
Video: H.264, H.265, VP8, VP9, SVC

On the audio side (10 codecs), this is actually a relative small subset
of the audio codecs that may be carried in RTP. Considering the
different configurations or annex extensions, there is no problem to
actually triple this list when it comes to audio. For video these 5 is a
selection of what might be in use in the near future. Also here there
are some potential, although less to offer additional PTs based on the
codec configurations. H.264 could run amok and offer a huge number if
one have a codec implementation that supports many profiles, as each
profile requires its own PT to be offered. As H.264 has 10+ profiles it
is possible. But, a more realistic count is likely 3 PTs.

The main point is that just the codecs listed above are themselves 15.
With some need to have different configurations for some of them, the
number can relatively easily be doubled and result in that one is up
against the limit (32).

There are clearly choices that one can make to reduce the usage and save
some number of PT values. My main concern is that one more mechanism
that results in equal number of PTs of its own in regards to what it is
associated with, is likely to cause significant concern. And we do have
some that has the potential. Multi stream scalability or simulcast if we
would require to indicate each codec configuration with its own payload
type will increase the requirement with a significant factor.

Thus, this is a potential issue, and an issue that can't be dismissed,
just because your set of limitations makes it unlikely that you will run
into it. We do need to ensure that mechanisms doesn't waste PT values to
achieve some other gain. This is becoming a real limitation.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
F=E4r=F6gatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com<mailto=
:magnus.westerlund@ericsson.com>
----------------------------------------------------------------------

_______________________________________________
mmusic mailing list
mmusic@ietf.org<mailto:mmusic@ietf.org>
https://www.ietf.org/mailman/listinfo/mmusic


From nobody Mon Mar 17 06:01:31 2014
Return-Path: <magnus.westerlund@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 4706A1A03FC for <mmusic@ietfa.amsl.com>; Mon, 17 Mar 2014 06:01:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.851
X-Spam-Level: 
X-Spam-Status: No, score=-3.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 Zx5_rDV8k7EK for <mmusic@ietfa.amsl.com>; Mon, 17 Mar 2014 06:01:23 -0700 (PDT)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id E57921A0110 for <mmusic@ietf.org>; Mon, 17 Mar 2014 06:01:22 -0700 (PDT)
X-AuditID: c1b4fb25-b7f038e000005d01-8a-5326f21a4c95
Received: from ESESSHC022.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 95.17.23809.A12F6235; Mon, 17 Mar 2014 14:01:14 +0100 (CET)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.86) with Microsoft SMTP Server id 14.2.347.0; Mon, 17 Mar 2014 14:01:13 +0100
Message-ID: <5326F219.7060207@ericsson.com>
Date: Mon, 17 Mar 2014 14:01:13 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Justin Uberti <juberti@google.com>
References: <5322D231.2010909@ericsson.com> <CAOJ7v-0WD6wcmFFXFQ1YuMqSm4UBzyU=7-o3MtKO3JXHiTna8w@mail.gmail.com>
In-Reply-To: <CAOJ7v-0WD6wcmFFXFQ1YuMqSm4UBzyU=7-o3MtKO3JXHiTna8w@mail.gmail.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupjluLIzCtJLcpLzFFi42KZGfG3Rlfqk1qwwcdDEhZbpwpZTF3+mMWB yWPBplKPJUt+MgUwRXHZpKTmZJalFunbJXBlTF/YxlTQb15xf8kGtgbGNq0uRk4OCQETiSO9 Z9khbDGJC/fWs3UxcnEICRxilGjdeIsJwlnOKNHee5EJpIpXQFvi1OonbCA2i4CqxL/W42Bx NgELiZs/GsHiogLBEjsP/GaEqBeUODnzCQuILSKgJvFw1i5WEJtZQF2i53cLM4gtLGAl0bbl OdgVQgIFEsu65oDVcwoESkzcDzKTA+g6cYmexiCIVk2J1u2/2SFseYnmrbOZIVq1JRqaOlgn MArNQrJ5FpKWWUhaFjAyr2Jkz03MzEkvN9rECAzTg1t+q+5gvHNO5BCjNAeLkjjvh7fOQUIC 6YklqdmpqQWpRfFFpTmpxYcYmTg4pRoY44w/TuuptVplICzwKarV9VaczozXPv7mTT1nT9vI 5jXmrjntGeEY88u6Rc7Te9N1p5v3omoWvem7f83MtynEN2X7qQBHmY91npcEcvYfC9EMFv2X /vFMgVn06r3H+J/uDHeqK51k7519eRrD+th1f71M+2X9Ogwivh+Z1PHPZta3RWv27BRTYinO SDTUYi4qTgQAGMIwUCECAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/N6SlO0_BvndyhY0G_ngQEetI3Aw
Cc: "mmusic \(E-mail\)" <mmusic@ietf.org>
Subject: Re: [MMUSIC] On the sparsity of RTP Payload types
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, 17 Mar 2014 13:01:27 -0000

On 2014-03-14 18:33, Justin Uberti wrote:
> Agree this is a real limitation. In addition to the codecs listed above,
> note that CN and telephone-event are often needed, and potentially in
> multiple clockrates.

Correct, I forgot to include these in the audio examples.

> 
> (which is why I think we shouldn't burn PTs on demultiplexing)

And here I assume you mean associating one incoming RTP packet stream
with a specific usage and m= section in the signalling?

I think we are making progress on that functionality, and I have hope
after hallway discussion in London that we will see a basic targeted
version of "appid" for this purpose (1-to-1 association) pretty soon.

Cheers

Magnus

> 
> 
> 
> 
> On Fri, Mar 14, 2014 at 2:56 AM, Magnus Westerlund
> <magnus.westerlund@ericsson.com <mailto:magnus.westerlund@ericsson.com>>
> wrote:
> 
>     MMUSIC,
> 
>     There's have been a number of people not believing in that RTP payload
>     types may become a limiting factor when trying to express configurations
>     in SDP or other signaling. Thus, I would like to share my concerns over
>     how the combination of various mechanism effects the number of actual
>     payload type configurations needed to negotiated.
> 
>     First a set of mechanism that do affect Payload Type usage.
> 
>     1. RTCP MUX (RFC 5761)
>     If one uses RTCP RTP multiplexing, then a number of the RTP payload
>     types are reserved for identifying the RTCP packets, rather than RTP
>     payload formats. The default reservation is to reserve PT numbers 64-95.
>     This limits the 128 PTs to 96 available ones.
> 
>     2. BUNDLE (draft-ietf-mmusic-sdp-bundle-negotiation)
>     When using BUNDLE, all listed m= sections within a bundle group are in
>     the same RTP session, thus all the PTs share a single common PT
>     numbering space. Bundle has done what it can to allow re-use across the
>     m= sections for the same configurations.
> 
>     3. Multi-Media RTP sessions (draft-ietf-avtcore-multi-media-rtp-session)
>     This mechanism allows multiple media types, like audio, video and text
>     to share the same RTP session. This in itself does not reduce the
>     availability, but increases the number of codec configurations that
>     might be required (or desired) to signal support for.
> 
>     4. RTP Retransmission (RFC 4588)
>     RTP retransmission payload format, requires one PT per PT that one want
>     to be able to retransmit. If the answer is all of the payload formats,
>     this doubles the payload format consumption.
> 
>     5. XOR based FEC (RFC 5109)
>     This RTP payload format would normally just consume one PT as it is
>     capable of recovering the original PT field of a lost packet. However,
>     it is commonly used with the redundancy payload format (RED) (RFC 2198).
>     And RED requires one to have one RTP payload type per Redundancy
>     combination. Thus, this results in at least as many PT as PTs one like
>     to be able to apply FEC on.
> 
> 
>     Lets try using the above in combination and see what the
>     implications are.
> 
>     So we have 96 available values using RTCP mux, we like to use RTP
>     Retransmission as well as XOR FEC, to be able to cope with whatever RTT
>     the path provides and still be robust to packet losses within that
>     single RTP session. Thus, we end up with a maximum of 32 PTs for
>     encoding configurations.
> 
>     As this is an RTP session that contains both Audio and Video we need to
>     create a number of configurations for both of media types. This endpoint
>     do support a descent amount of codecs to be compatible with various
>     systems.
> 
>     Audio: PCMA, PCMU, OPUS, AMR, AMR-WB, EVRC, EVRCWB, G.719, G.722, G.729
>     Video: H.264, H.265, VP8, VP9, SVC
> 
>     On the audio side (10 codecs), this is actually a relative small subset
>     of the audio codecs that may be carried in RTP. Considering the
>     different configurations or annex extensions, there is no problem to
>     actually triple this list when it comes to audio. For video these 5 is a
>     selection of what might be in use in the near future. Also here there
>     are some potential, although less to offer additional PTs based on the
>     codec configurations. H.264 could run amok and offer a huge number if
>     one have a codec implementation that supports many profiles, as each
>     profile requires its own PT to be offered. As H.264 has 10+ profiles it
>     is possible. But, a more realistic count is likely 3 PTs.
> 
>     The main point is that just the codecs listed above are themselves 15.
>     With some need to have different configurations for some of them, the
>     number can relatively easily be doubled and result in that one is up
>     against the limit (32).
> 
>     There are clearly choices that one can make to reduce the usage and save
>     some number of PT values. My main concern is that one more mechanism
>     that results in equal number of PTs of its own in regards to what it is
>     associated with, is likely to cause significant concern. And we do have
>     some that has the potential. Multi stream scalability or simulcast if we
>     would require to indicate each codec configuration with its own payload
>     type will increase the requirement with a significant factor.
> 
>     Thus, this is a potential issue, and an issue that can't be dismissed,
>     just because your set of limitations makes it unlikely that you will run
>     into it. We do need to ensure that mechanisms doesn't waste PT values to
>     achieve some other gain. This is becoming a real limitation.
> 
>     Cheers
> 
>     Magnus Westerlund
> 
>     ----------------------------------------------------------------------
>     Services, Media and Network features, Ericsson Research EAB/TXM
>     ----------------------------------------------------------------------
>     Ericsson AB                 | Phone  +46 10 7148287
>     FÃ¤rÃ¶gatan 6                 | Mobile +46 73 0949079
>     SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
>     <mailto:magnus.westerlund@ericsson.com>
>     ----------------------------------------------------------------------
> 
>     _______________________________________________
>     mmusic mailing list
>     mmusic@ietf.org <mailto:mmusic@ietf.org>
>     https://www.ietf.org/mailman/listinfo/mmusic
> 
> 


-- 

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
FÃ¤rÃ¶gatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From nobody Mon Mar 17 06:04:01 2014
Return-Path: <magnus.westerlund@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 AB8A21A03DD for <mmusic@ietfa.amsl.com>; Mon, 17 Mar 2014 06:03:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.851
X-Spam-Level: 
X-Spam-Status: No, score=-3.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 1HtF5gaKfPoO for <mmusic@ietfa.amsl.com>; Mon, 17 Mar 2014 06:03:53 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id ECA161A0110 for <mmusic@ietf.org>; Mon, 17 Mar 2014 06:03:18 -0700 (PDT)
X-AuditID: c1b4fb2d-b7f5d8e000002a7b-1d-5326f28d1a97
Received: from ESESSHC017.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id DE.3F.10875.D82F6235; Mon, 17 Mar 2014 14:03:09 +0100 (CET)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.71) with Microsoft SMTP Server id 14.2.347.0; Mon, 17 Mar 2014 14:03:09 +0100
Message-ID: <5326F28C.4070504@ericsson.com>
Date: Mon, 17 Mar 2014 14:03:08 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Craig Matsuura <cmatsuura@vivint.com>, "mmusic@ietf.org" <mmusic@ietf.org>
References: <53223DAA.4040107@vivint.com> <5322D749.8020306@ericsson.com> <532490B8.7020208@vivint.com>
In-Reply-To: <532490B8.7020208@vivint.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpmluLIzCtJLcpLzFFi42KZGfG3Rrf3k1qwQetODYvdl74yW0xd/pjF gcljyZKfTB7nnl1lDWCK4rJJSc3JLEst0rdL4Mp49mQye8EE5Yop17exNDBOkuli5OSQEDCR 2PX3ODOELSZx4d56ti5GLg4hgUOMEveOPGMESQgJLGeU+HjdBsTmFdCWWHb9OSuIzSKgKrH5 xXkWEJtNwELi5o9GNhBbVCBYYueB34wQ9YISJ2c+AasREfCTmHH5NxOILSzgKzHl7Fqo+ekS 1w51gtmcAloS7z5tBqrhADpIXKKnMQgkzCygJzHlagsjhC0v0bx1NjNEq7ZEQ1MH6wRGwVlI ts1C0jILScsCRuZVjOy5iZk56eWGmxiBAXlwy2/dHYynzokcYpTmYFES5/3w1jkI6KDEktTs 1NSC1KL4otKc1OJDjEwcnFINjEaFDrF3Pps9DX7oEzVXVNPmcdrvmhkli5amHejefzZtSfky 2dZ5h0L+vdg2w6GDLcQp6vSVTc5X/hye1tq2VNPppssxB8bJAglWlmKRxZpdE9f8L2PqeHkt zPhGukDQHc75CZfOXqmM2iUc+MLkzaoa+1LWpx2Gtcl2Cd+OJ7pP/vVuzlxxayWW4oxEQy3m ouJEABDeiSIWAgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/MzcW9s1e3uyRxMiiMSPVCtm2BhY
Subject: Re: [MMUSIC] RTSP questions in regards to the control channel socket
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, 17 Mar 2014 13:03:57 -0000

On 2014-03-15 18:41, Craig Matsuura wrote:
> Hi Magnus,
> 
> Thanks for your response, to be clear when I was referring to a Control 
> Socket I mean the connection that sends commands such as the DESCRIBE, 
> OPTIONS, SETUP.  So to restate, it should not matter if a connection for 
> the transports comes or goes to server.  For example if a server flow to 
> a client is:
> 
> C->S - Send DESCRIBE Command, C gets 200 response from S.
> Close connection and start new connection
> C->S - Send OPTIONS command, C gets 200 response from S.
> Close connection and start new connection
> C->S - Send SETUP command, C gets ??? response from S.
> 
> So at the SETUP the response should be 200? or fail (400)?  I'm trying 
> to clear up an issue I have with a vendors RTSP Server implementation 
> and would like to know if the sequence above should work to a RTSP 
> Server.  Based on the Section 1.1 and 1.7 seems the above should work.  
> The only issue would be after the SETUP the session id needs to 
> accompany commands that follow?

Yes, according to my interpretation of RFC 2326 that should be
completely valid and the SETUP request result in a 200 OK with a session
ID that is later used to reference that session.

/Magnus

> 
> Thanks,
> Craig
> 
> 
> On 03/14/2014 04:17 AM, Magnus Westerlund wrote:
>> On 2014-03-14 00:22, Craig Matsuura wrote:
>>> Hi this is my first time posting here.  I have a basic question about
>>> how a RTSP server should handled a connect and disconnect for what I am
>>> calling the control channel (connection or transport). The control
>>> channel (please correct me) is what sends the DESCRIBE, SETUP, OPTIONS,
>>> PLAY commands to the RTSP SERVER.
>>>
>>> Should a server treat the first DESCRIBE connection as its session. So
>>> in the case where a socket connects to a RTSP server and sends a
>>> DESCRIBE, is disconnected either by the client or some failure on the
>>> server should the following SETUP succeed?
>> No, DESCRIBE is a state less operation. If one needs a linkage between
>> the Describe response body and the setup, then one should use etags and
>> conditional requests to ensure that one is establishing the session with
>> a relevant session description.
>>
>>> Also if using a RTSP Proxy and in the same scenario, but after the
>>> DESCRIBE and closing of the socket a new socket is open to send an
>>> OPTIONS (for keepalive) should the following SETUP succeed?
>> Yes the SETUP should succeed if otherwise valid.
>>
>>>   From what I understood from the RFC2326 Section 1.7 RTSP State, it
>>> should not matter how many connections are used to control the RTSP Stream.
>>>
>>> 1. Control Socket is not prevent a client from connecting and
>>> disconnecting to send Transport commands.
>> I am uncertain what you mean with the Control socket, if you means the
>> Socket the server listens to incoming TCP connection establishments and
>> their data, it needs to be accepting those comming and going.
>>
>>> 2. The keep-alive for a session should not start until a SETUP command,
>>> which can optional report the timeout for the session.
>> Exact, the keep-alive is associated with the RTSP session, not the
>> signalling connection used to send RTSP requests and response between
>> the server and client.
>>
>> You might find RTSP 2.0's text on this being clearer:
>> https://datatracker.ietf.org/doc/draft-ietf-mmusic-rfc2326bis/
>>
>> Cheers
>>
>> Magnus Westerlund
>>
>> ----------------------------------------------------------------------
>> Services, Media and Network features, Ericsson Research EAB/TXM
>> ----------------------------------------------------------------------
>> Ericsson AB                 | Phone  +46 10 7148287
>> Färögatan 6                 | Mobile +46 73 0949079
>> SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
>> ----------------------------------------------------------------------
>>
> 


-- 

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Färögatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From nobody Mon Mar 17 12:49:07 2014
Return-Path: <internet-drafts@ietf.org>
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 7EC021A04B7; Mon, 17 Mar 2014 12:49:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.9
X-Spam-Level: 
X-Spam-Status: No, score=-3.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_INVITATION=-2] autolearn=ham
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 bs2acCNLoZdY; Mon, 17 Mar 2014 12:49:00 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id EEFF11A0436; Mon, 17 Mar 2014 12:48:59 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.1.0p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140317194859.4227.66600.idtracker@ietfa.amsl.com>
Date: Mon, 17 Mar 2014 12:48:59 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/qiZhruVCKowIZdZqnFCVgkOSOsw
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D Action: draft-ietf-mmusic-rfc4566bis-10.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
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, 17 Mar 2014 19:49:01 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Multiparty Multimedia Session Control Working Group of the IETF.

        Title           : SDP: Session Description Protocol
        Authors         : Mark Handley
                          Van Jacobson
                          Colin Perkins
                          Ali Begen
	Filename        : draft-ietf-mmusic-rfc4566bis-10.txt
	Pages           : 51
	Date            : 2014-03-17

Abstract:
   This memo defines the Session Description Protocol (SDP).  SDP is
   intended for describing multimedia sessions for the purposes of
   session announcement, session invitation, and other forms of
   multimedia session initiation.  This document obsoletes RFC 4566.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-mmusic-rfc4566bis/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-mmusic-rfc4566bis-10

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-rfc4566bis-10


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Mon Mar 17 12:51:47 2014
Return-Path: <abegen@cisco.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 A20211A0492 for <mmusic@ietfa.amsl.com>; Mon, 17 Mar 2014 12:51:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.048
X-Spam-Level: 
X-Spam-Status: No, score=-17.048 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, GB_I_INVITATION=-2, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 KRKRAv0lNycZ for <mmusic@ietfa.amsl.com>; Mon, 17 Mar 2014 12:51:43 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id 9EC5E1A0200 for <mmusic@ietf.org>; Mon, 17 Mar 2014 12:51:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1866; q=dns/txt; s=iport; t=1395085896; x=1396295496; h=from:to:subject:date:message-id:references:content-id: content-transfer-encoding:mime-version; bh=NPi46wcY/LuxolhQGit3LZxYdrEX7oBxRQ1uhBl0gAU=; b=STf0BWiqWOYRYPBKMGh2jY8yKDS9qk1ulBnxOwjZmTB8UpUSw7STn5/E qEGCxTJDNxgISAAufkkOUOK9tl2voMf2QWMAuDVLKfKy4jQApkoL2tTdi QWcmBx1P0rYwarO20TOJWz842RJ4LKZjWEXvYsZ3f0eHrKtvcJ126gfNl s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AuAFAI9RJ1OtJXG//2dsb2JhbABZgmUhO1EGwhKBIxZ0giUBAQEDATo9BwsCARkDAQIfEDIbAggCBBMJh2gIAQcF0zUXjnWDHoEUBJhGgTKQfoMtgis
X-IronPort-AV: E=Sophos;i="4.97,671,1389744000"; d="scan'208";a="310916886"
Received: from rcdn-core2-4.cisco.com ([173.37.113.191]) by rcdn-iport-6.cisco.com with ESMTP; 17 Mar 2014 19:51:35 +0000
Received: from xhc-aln-x03.cisco.com (xhc-aln-x03.cisco.com [173.36.12.77]) by rcdn-core2-4.cisco.com (8.14.5/8.14.5) with ESMTP id s2HJpZ0M012136 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <mmusic@ietf.org>; Mon, 17 Mar 2014 19:51:35 GMT
Received: from xmb-aln-x01.cisco.com ([fe80::747b:83e1:9755:d453]) by xhc-aln-x03.cisco.com ([173.36.12.77]) with mapi id 14.03.0123.003; Mon, 17 Mar 2014 14:51:35 -0500
From: "Ali C. Begen (abegen)" <abegen@cisco.com>
To: "<mmusic@ietf.org>" <mmusic@ietf.org>
Thread-Topic: New Version Notification for draft-ietf-mmusic-rfc4566bis-10.txt
Thread-Index: AQHPQhnvs7sD7ErLTkKWPHal8UlS9w==
Date: Mon, 17 Mar 2014 19:51:34 +0000
Message-ID: <05442941-FAB9-4A9A-B2D8-0B8A70F623CB@cisco.com>
References: <20140317194900.4227.77172.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.66.246.93]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <D056D1286616D141B97EF9E41BA6F029@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/VXUVEpshxMKzOqwQMJvXrS-OHMU
Subject: [MMUSIC] Fwd: New Version Notification for draft-ietf-mmusic-rfc4566bis-10.txt
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, 17 Mar 2014 19:51:45 -0000

This is a keep-alive update.

We had some discussions about "fixing" some of the IANA registrations/ABNFs=
 that were done in 4566 but whether this will be done or not is TBD.=20

-acbegen

Begin forwarded message:

> From: <internet-drafts@ietf.org>
> Subject: New Version Notification for draft-ietf-mmusic-rfc4566bis-10.txt
> Date: March 18, 2014 at 6:49:00 AM GMT+11
> To: Van Jacobson <van@parc.com>, "Mark J. Handley" <m.handley@cs.ucl.ac.u=
k>, "Ali C. Begen" <abegen@cisco.com>, "Dr. Colin Perkins" <csp@csperkins.o=
rg>, Colin Perkins <csp@csperkins.org>, Van Jacobson <van@parc.com>, Ali Be=
gen <abegen@cisco.com>, Mark Handley <m.handley@cs.ucl.ac.uk>
>=20
>=20
> A new version of I-D, draft-ietf-mmusic-rfc4566bis-10.txt
> has been successfully submitted by Ali Begen and posted to the
> IETF repository.
>=20
> Name:		draft-ietf-mmusic-rfc4566bis
> Revision:	10
> Title:		SDP: Session Description Protocol
> Document date:	2014-03-17
> Group:		mmusic
> Pages:		51
> URL:            http://www.ietf.org/internet-drafts/draft-ietf-mmusic-rfc=
4566bis-10.txt
> Status:         https://datatracker.ietf.org/doc/draft-ietf-mmusic-rfc456=
6bis/
> Htmlized:       http://tools.ietf.org/html/draft-ietf-mmusic-rfc4566bis-1=
0
> Diff:           http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mmusic-rfc4=
566bis-10
>=20
> Abstract:
>   This memo defines the Session Description Protocol (SDP).  SDP is
>   intended for describing multimedia sessions for the purposes of
>   session announcement, session invitation, and other forms of
>   multimedia session initiation.  This document obsoletes RFC 4566.
>=20
>=20
>=20
>=20
> Please note that it may take a couple of minutes from the time of submiss=
ion
> until the htmlized version and diff are available at tools.ietf.org.
>=20
> The IETF Secretariat
>=20


From nobody Mon Mar 17 16:55:46 2014
Return-Path: <partha@parthasarathi.co.in>
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 1997B1A0325 for <mmusic@ietfa.amsl.com>; Mon, 17 Mar 2014 16:55:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.699
X-Spam-Level: 
X-Spam-Status: No, score=0.699 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham
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 8kBvBmtPxQES for <mmusic@ietfa.amsl.com>; Mon, 17 Mar 2014 16:55:43 -0700 (PDT)
Received: from outbound.mailhostbox.com (outbound.mailhostbox.com [162.222.225.12]) by ietfa.amsl.com (Postfix) with ESMTP id E3BDA1A021A for <mmusic@ietf.org>; Mon, 17 Mar 2014 16:55:42 -0700 (PDT)
Received: from userPC (unknown [122.167.209.16]) (Authenticated sender: partha@parthasarathi.co.in) by outbound.mailhostbox.com (Postfix) with ESMTPA id 1B2CA197800D; Mon, 17 Mar 2014 23:55:29 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=parthasarathi.co.in; s=20120823; t=1395100534; bh=5uz7thHkCAemqhqbkn6QYQYXu9XOoBzmnCwVTaIny0I=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:Content-Type: Content-Transfer-Encoding; b=UfUlKCLcGfwpqa0TCDqCuxQFuGg/xhk4QJ70W1BLcxKwpWzC3/gP0X2FYAQbZjenW AehZ1aXGmg4SPHMsAzFkfja8lOL13ywKtOyV2Szn6e4YREneODOpGDYHpkQhmq9SYi nIZUZ78mD9rwVNlsDE1y1S+yaEx5rlPEitNJau5o=
From: "Parthasarathi R" <partha@parthasarathi.co.in>
To: "'Emil Ivov'" <emcho@jitsi.org>, "'Enrico Marocco \(TiLab\)'" <enrico.marocco@telecomitalia.it>, "'Christer Holmberg'" <christer.holmberg@ericsson.com>
Date: Tue, 18 Mar 2014 05:25:07 +0530
Message-ID: <01e601cf423c$57255890$057009b0$@co.in>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac9CPFJy24/vzsmBSZKQcuFN40F13Q==
Content-Language: en-us
X-CTCH-RefID: str=0001.0A020203.53278B76.0075, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0
X-CTCH-VOD: Unknown
X-CTCH-Spam: Unknown
X-CTCH-Score: 0.000
X-CTCH-Rules: 
X-CTCH-Flags: 0
X-CTCH-ScoreCust: 0.000
X-CTCH-SenderID: partha@parthasarathi.co.in
X-CTCH-SenderID-TotalMessages: 1
X-CTCH-SenderID-TotalSpam: 0
X-CTCH-SenderID-TotalSuspected: 0
X-CTCH-SenderID-TotalBulk: 0
X-CTCH-SenderID-TotalConfirmed: 0
X-CTCH-SenderID-TotalRecipients: 0
X-CTCH-SenderID-TotalVirus: 0
X-CTCH-SenderID-BlueWhiteFlag: 0
X-Scanned-By: MIMEDefang 2.72 on 70.87.28.138
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/KjJBx1s48iCfSRf1vQYqLYI4mhM
Cc: mmusic@ietf.org
Subject: [MMUSIC] Comment on SIP Trickle based on INFO draft
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, 17 Mar 2014 23:55:45 -0000

Hi all,

SIP Trickle INFO is projected as the back channel for collecting the
candidates in IETF-89 MMUSIC meeting. Unfortunately, it impacts Offer/answer
(RFC 3264) in case one another offer/answer started before SIP trickle INFO
is completed. The race condition between second offer/answer and earlier SIP
trickle INFO is not stated in the draft-ivov-mmusic-trickle-ice-sip. I have
explained those issues in
http://www.ietf.org/mail-archive/web/mmusic/current/msg12666.html and no
reply from you folks. This race condition is very much possible during early
dialog scenarios with UPDATE.

Could you please explain how SIP trickle ICE using INFO works for

1) UPDATE from remote before Trickle ICE is completed

    a) INVITE from local
    b) 183 session progress from remote
    c) PRACK from local
    d) INFO from local (relay candidates)
    e) UPDATE from remote 

Here, the remote has to consider whether INFO belongs to UPDATE or INVITE as
it is possible for INFO to reach before 200 OK for UPDATE as well in the
same sequence. Also, RFC 2976 clarifies that 

" - The extensions that use the INFO message MUST NOT rely on the
     INFO message to do anything that effects the SIP call state or the
     state of related sessions."

But SIP Trickle ICE state is depend upon the "state of related sessions" as
UPDATE would have change the state in the remote.   

2) Trickle ICE INFO with serial forking

  a) INVITE from local
  b) INVITE is forked by proxy to first remote destination
  c) 100 trying is reaching local
  d) INFO with Trickle ICE from local
  e) INFO is forward by proxy to first remote destination
  f) INVITE is forked by proxy to second remote destination
  g) Whether INFO has to be forked?

It is not mentioned in the draft whether INFO has to be forked to the second
remote destination as well. Could you please explain the expect behavior for
this scenario.

Thanks
Partha   


From nobody Wed Mar 19 01:52:22 2014
Return-Path: <emcho@sip-communicator.org>
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 7A64C1A06FC for <mmusic@ietfa.amsl.com>; Wed, 19 Mar 2014 01:52:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.979
X-Spam-Level: 
X-Spam-Status: No, score=-1.979 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 zqWzHtjEemkR for <mmusic@ietfa.amsl.com>; Wed, 19 Mar 2014 01:52:19 -0700 (PDT)
Received: from mail-ve0-f182.google.com (mail-ve0-f182.google.com [209.85.128.182]) by ietfa.amsl.com (Postfix) with ESMTP id 46F5A1A04B4 for <mmusic@ietf.org>; Wed, 19 Mar 2014 01:52:19 -0700 (PDT)
Received: by mail-ve0-f182.google.com with SMTP id jw12so8584904veb.13 for <mmusic@ietf.org>; Wed, 19 Mar 2014 01:52:10 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=34PauieQoEz2iK5nD4lDJwYRBT4MTCWINycTu5sLz9w=; b=HI3HqjOehG7aNngQyw0oeNyKtdz1ffq5DORXP6WPDTRlwiGKWHfYMhfmedku/9+hhh FLvmmaSVZ4viGC1eFXMD7A0gLlUxbyjjmsZKF9QSGHJWsQkF804cdtpZdmGqhNSKyPKf FsA1jYHZKxt7KsKg+geWiLC3IZ6UCMCEb0RugAqLD9thlEaXr6+WVrTRAgdmMYBNIyap 1BAaf2rkGmMcY/O3SNhtxkGdSxbc0grD8N2ptX5owmtY9diMD/HcILnMfY1+carj6PaO qNG9RTrUdyEn+449yEyAYarKHP3Mo4jbWEu+bL8c67Fbd2XHaOogdBweqNBi54jEIwix ty8Q==
X-Gm-Message-State: ALoCoQlioasgc5HC6t76pFxaDUoGZbOrc9G2S60ya5xY35AY1ZomDcMim3VATQL5FcohE1XbtT+m
X-Received: by 10.220.164.80 with SMTP id d16mr28674471vcy.15.1395219130215; Wed, 19 Mar 2014 01:52:10 -0700 (PDT)
Received: from mail-ve0-f176.google.com (mail-ve0-f176.google.com [209.85.128.176]) by mx.google.com with ESMTPSA id zb18sm24783557vdb.18.2014.03.19.01.52.09 for <mmusic@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 19 Mar 2014 01:52:09 -0700 (PDT)
Received: by mail-ve0-f176.google.com with SMTP id cz12so8516095veb.35 for <mmusic@ietf.org>; Wed, 19 Mar 2014 01:52:09 -0700 (PDT)
X-Received: by 10.58.238.35 with SMTP id vh3mr28706660vec.16.1395219129396; Wed, 19 Mar 2014 01:52:09 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.191.130 with HTTP; Wed, 19 Mar 2014 01:51:49 -0700 (PDT)
In-Reply-To: <CF489B5D.25EB0%alissa@cooperw.in>
References: <CF489B5D.25EB0%alissa@cooperw.in>
From: Emil Ivov <emcho@jitsi.org>
Date: Wed, 19 Mar 2014 10:51:49 +0200
Message-ID: <CAPvvaaKM7S0jRA1dQgCZLGfg4ryNRriMfvSM3V6sD+=3TX4Jzw@mail.gmail.com>
To: Alissa Cooper <alissa@cooperw.in>
Content-Type: text/plain; charset=ISO-8859-1
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/CKSbJUEolfPXHhV7wanKiufBIdc
Cc: draft-ietf-mmusic-latching@tools.ietf.org, mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] AD evaluation: draft-ietf-mmusic-latching-04
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: Wed, 19 Mar 2014 08:52:21 -0000

Hey Alissa,

Apologies for the delay. My mail filters were somewhat messed up and I
missed on some of the MMUSIC traffic.

More inline.

On Fri, Mar 14, 2014 at 8:41 PM, Alissa Cooper <alissa@cooperw.in> wrote:
> I have reviewed this draft in preparation for IETF LC. I have one issue that
> I'd like to see the group discuss before issuing the LC: Section 1 says "the
> latching mechanism is considered inappropriate for general use on the
> Internet unless all security considerations are taken into account and
> solved." But given the lack of mitigations for attacks originating from
> behind large-scale NATs as described in Section 5, it's not obvious to me
> that that condition can realistically be met.

The draft suggests use of SRTP for authenticating media which does
resolve the security issues (from a privacy/confidentiality
perspective). That's part of section 5:

   Naturally, SRTP [RFC3711] would help mitigate such threats and should
   be used independently of HNT.  For example, in cases where end-to-end
   encryption is used it would still be possible for an attacker to
   hijack a session despite the use of SRTP and perform a denial of
   service attack.  However, media integrity would not be compromised.

How does this sound to you?

Now that I am reading it actually, I am thinking that there's no need
for such a DoS to have permanent consequences. As long as an SRTP
supporting SBC continues to latch to any new source until it
authenticates one, then things should be fine.

If this sounds reasonable, we will update the text in the next iteration.

Also it is worth reminding that the above threats apply mostly to
generic Internet deployments. Many people using latching today, do so
in controlled environments, where that kind of hijacking could not
occur.

I am obviously not suggesting we go and recommend the practice but the
purpose of the draft is to, above all, describe a hugely popular
practice so that we can have an informative (and only informative)
reference.

> If it can't be, it seems to me
> that this document should be making a stronger statement about the
> inappropriateness of latching.

We actually did a couple of back and forths (mostly with Cullen) on
making sure that the "LATCHING IS BAD" message is loud enough (in my
personal opinion we are even making it sound scarier that it needs to
be), but if anyone else has text that would better describe the
situation, suggestions are most welcome!

> Also, I found a  couple of nits to address with any LC comments:
>
> Section 1:
>
> s/handle traffic in way that/handle traffic in a way that/
>
> Section 2:
>
> s/UA sends packet out first/UA sends packets out first/
>
> Section 4:
>
> s/IETF members/IETF participants/ (two occurrences)
>
> s/the one the best suits/the one that best suits/
>
> s/address information in in offers/address information in offers/

Fixed! Thanks very much!

> There is an in-text reference to "[tcp-splicing]," but there is no such
> reference in the references section.

Oh right! Do we have a good reference about this at the IETF?
Otherwise we could just go for something like this:

"TCP Splice for application layer proxy performance" DA Maltz, P
Bhagwat - Journal of High Speed Networks, 1999 - IOS Pressure

Emil

-- 
https://jitsi.org


From nobody Wed Mar 19 17:14:23 2014
Return-Path: <juberti@google.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 DFB131A0836 for <mmusic@ietfa.amsl.com>; Wed, 19 Mar 2014 17:14:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.325
X-Spam-Level: 
X-Spam-Status: No, score=-1.325 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_17=0.6, RP_MATCHES_RCVD=-0.547, 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 iLuxXE6L9B1j for <mmusic@ietfa.amsl.com>; Wed, 19 Mar 2014 17:14:18 -0700 (PDT)
Received: from mail-ve0-x231.google.com (mail-ve0-x231.google.com [IPv6:2607:f8b0:400c:c01::231]) by ietfa.amsl.com (Postfix) with ESMTP id BF3EE1A0821 for <mmusic@ietf.org>; Wed, 19 Mar 2014 17:14:17 -0700 (PDT)
Received: by mail-ve0-f177.google.com with SMTP id sa20so98720veb.22 for <mmusic@ietf.org>; Wed, 19 Mar 2014 17:14:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=CUmYa8T3IsS1JmsQ74rWbGuaOmODHH9PyPVsh22fr8I=; b=bcY5I2nGkPvRgWmpU6C5vXqmfbSLbldOjP2karOeBEqU7hPJk1TiM7a8zrawX/EJVE romI4ip8mOW/rFJvMDS7qDGovzZblWWFun/MtqKU1vyRJUEvN952+3qTILtGLtlH9iLq VUp7Zoxf3yhs57LUgUUcBarEM9C4Y5rN0YMkOvosF+yp0kOupO2SRBP7GXOzHRHfkQV0 3atGgItuuChN69mB4bVL1g5Wxg7SoNBlFf1YrbRbHXBgJl2aiVGD8yCua6tTw+SltEtd JnnJfD5p7E3wRgTsxqGo/Yqi1f7xHIKNcqCsGutxDx5xyhOMFFCN8WAJO7UyhMaKH2Fz /QKw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=CUmYa8T3IsS1JmsQ74rWbGuaOmODHH9PyPVsh22fr8I=; b=f1w2n7qThGPSg0RUV0LxHj1Wie/cD+5jWE8QoXoBC8x2rLHsNiOZsfdFcu8dDotCeA ybYvx0lxUX+iwuiPc9zfjIkdns8bcbPfMVvhDgdmgVuA/12QmwILQ+LMuUZgAlDkqGEd ju1dV2YMUZhfr657Djr6PrMVPgL7P98sjnjzOsx8w/gzxl5C7VW1PFAs9DgRPPyfEDxp AH4zFnb+InsV3mVuB/x00x1GNn8TZG6bDAfhrI+Enp0LnYEFVyu5b0sc8MxT+1MTx/Px acrjI7AzT0V7jSkiYDqTAUTKGWhcWZjbtxU32t9qztmt+caBVE4OFYxyWomBvOqyPP9i 9qXw==
X-Gm-Message-State: ALoCoQkjBqSJLcYbj44RQ2K3GiYtWGRwoCJNu4/cPepI4JKKcCmpdWZYl0L6wldExlHf0zUy9CxMlkDEXcKjvvYNnfIpHf5Jeq2y5y2WTZ9VHeo/HWHWzrqfYsWuz85QyliwMV14FbqA0BvpKQtPzyekWGQ+Rcb7HIqWXpEiSLo+2xBz4LkIt0jF17naVt2LGehMC5wxBPTH
X-Received: by 10.221.37.1 with SMTP id tc1mr2293423vcb.32.1395274448675; Wed, 19 Mar 2014 17:14:08 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.26.43 with HTTP; Wed, 19 Mar 2014 17:13:40 -0700 (PDT)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D23329D@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D23329D@ESESSMB209.ericsson.se>
From: Justin Uberti <juberti@google.com>
Date: Wed, 19 Mar 2014 17:13:40 -0700
Message-ID: <CAOJ7v-0Lt9o-wzzA5ppPYb1fVyjbS=mXLSEooD=xXDh4RjiB7A@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary=001a11334c38e0c3eb04f4fea5d6
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/4kI2ckGLBZleok_wysVDQlidDxc
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, "mmusic \(E-mail\)" <mmusic@ietf.org>
Subject: Re: [MMUSIC] BUNDLE Q14: Mandate usage of RTP/RTCP mux within a BUNDLE group? [was: On the sparsity of RTP Payload types]
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: Thu, 20 Mar 2014 00:14:22 -0000

--001a11334c38e0c3eb04f4fea5d6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Note that the current text indicates that rtcp-mux is mandatory-to-use when
bundling. The question here is whether we should reopen that discussion.

*6.2.3.  rtcp-mux Attribute

   For each "m=3D" line in a BUNDLE group, an Offerer and Answerer MUST
   assign an SDP rtcp-mux attribute [RFC5761].*


My feeling is no, since it creates odd edge cases, such as when you
have an existing audio m=3D line with rtcp-mux on, and then want to
bundle an audio m=3D line without rtcp-mux onto the existing transport;
since you don't have enough ICE components in the existing transport,
it's not clear how to perform the bundling.





On Sun, Mar 16, 2014 at 7:16 AM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

>
> Hi,
>
> Do other people have opinions on this?
>
> Just to clarify: the support of RTP/RTCP mux is already mandated in
> BUNDLE, and question is not whether the included the a=3Drtcpmux attribut=
e or
> not when RTP/RTCP mux is used - it shall be included. The question is
> whether we should mandate usage of RTP/RTCP mux within a BUNDLE group.
>
> Regards,
>
> Christer
>
>
>
> ________________________________________
> From: mmusic [mmusic-bounces@ietf.org] on behalf of Justin Uberti [
> juberti@google.com]
> Sent: Friday, 14 March 2014 7:33 PM
> To: Magnus Westerlund
> Cc: mmusic (E-mail)
> Subject: Re: [MMUSIC] On the sparsity of RTP Payload types
>
> Agree this is a real limitation. In addition to the codecs listed above,
> note that CN and telephone-event are often needed, and potentially in
> multiple clockrates.
>
> (which is why I think we shouldn't burn PTs on demultiplexing)
>
>
>
>
> On Fri, Mar 14, 2014 at 2:56 AM, Magnus Westerlund <
> magnus.westerlund@ericsson.com<mailto:magnus.westerlund@ericsson.com>>
> wrote:
> MMUSIC,
>
> There's have been a number of people not believing in that RTP payload
> types may become a limiting factor when trying to express configurations
> in SDP or other signaling. Thus, I would like to share my concerns over
> how the combination of various mechanism effects the number of actual
> payload type configurations needed to negotiated.
>
> First a set of mechanism that do affect Payload Type usage.
>
> 1. RTCP MUX (RFC 5761)
> If one uses RTCP RTP multiplexing, then a number of the RTP payload
> types are reserved for identifying the RTCP packets, rather than RTP
> payload formats. The default reservation is to reserve PT numbers 64-95.
> This limits the 128 PTs to 96 available ones.
>
> 2. BUNDLE (draft-ietf-mmusic-sdp-bundle-negotiation)
> When using BUNDLE, all listed m=3D sections within a bundle group are in
> the same RTP session, thus all the PTs share a single common PT
> numbering space. Bundle has done what it can to allow re-use across the
> m=3D sections for the same configurations.
>
> 3. Multi-Media RTP sessions (draft-ietf-avtcore-multi-media-rtp-session)
> This mechanism allows multiple media types, like audio, video and text
> to share the same RTP session. This in itself does not reduce the
> availability, but increases the number of codec configurations that
> might be required (or desired) to signal support for.
>
> 4. RTP Retransmission (RFC 4588)
> RTP retransmission payload format, requires one PT per PT that one want
> to be able to retransmit. If the answer is all of the payload formats,
> this doubles the payload format consumption.
>
> 5. XOR based FEC (RFC 5109)
> This RTP payload format would normally just consume one PT as it is
> capable of recovering the original PT field of a lost packet. However,
> it is commonly used with the redundancy payload format (RED) (RFC 2198).
> And RED requires one to have one RTP payload type per Redundancy
> combination. Thus, this results in at least as many PT as PTs one like
> to be able to apply FEC on.
>
>
> Lets try using the above in combination and see what the implications are=
.
>
> So we have 96 available values using RTCP mux, we like to use RTP
> Retransmission as well as XOR FEC, to be able to cope with whatever RTT
> the path provides and still be robust to packet losses within that
> single RTP session. Thus, we end up with a maximum of 32 PTs for
> encoding configurations.
>
> As this is an RTP session that contains both Audio and Video we need to
> create a number of configurations for both of media types. This endpoint
> do support a descent amount of codecs to be compatible with various
> systems.
>
> Audio: PCMA, PCMU, OPUS, AMR, AMR-WB, EVRC, EVRCWB, G.719, G.722, G.729
> Video: H.264, H.265, VP8, VP9, SVC
>
> On the audio side (10 codecs), this is actually a relative small subset
> of the audio codecs that may be carried in RTP. Considering the
> different configurations or annex extensions, there is no problem to
> actually triple this list when it comes to audio. For video these 5 is a
> selection of what might be in use in the near future. Also here there
> are some potential, although less to offer additional PTs based on the
> codec configurations. H.264 could run amok and offer a huge number if
> one have a codec implementation that supports many profiles, as each
> profile requires its own PT to be offered. As H.264 has 10+ profiles it
> is possible. But, a more realistic count is likely 3 PTs.
>
> The main point is that just the codecs listed above are themselves 15.
> With some need to have different configurations for some of them, the
> number can relatively easily be doubled and result in that one is up
> against the limit (32).
>
> There are clearly choices that one can make to reduce the usage and save
> some number of PT values. My main concern is that one more mechanism
> that results in equal number of PTs of its own in regards to what it is
> associated with, is likely to cause significant concern. And we do have
> some that has the potential. Multi stream scalability or simulcast if we
> would require to indicate each codec configuration with its own payload
> type will increase the requirement with a significant factor.
>
> Thus, this is a potential issue, and an issue that can't be dismissed,
> just because your set of limitations makes it unlikely that you will run
> into it. We do need to ensure that mechanisms doesn't waste PT values to
> achieve some other gain. This is becoming a real limitation.
>
> Cheers
>
> Magnus Westerlund
>
> ----------------------------------------------------------------------
> Services, Media and Network features, Ericsson Research EAB/TXM
> ----------------------------------------------------------------------
> Ericsson AB                 | Phone  +46 10 7148287
> F=C3=A4r=C3=B6gatan 6                 | Mobile +46 73 0949079
> SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> <mailto:magnus.westerlund@ericsson.com>
> ----------------------------------------------------------------------
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org<mailto:mmusic@ietf.org>
> https://www.ietf.org/mailman/listinfo/mmusic
>
>

--001a11334c38e0c3eb04f4fea5d6
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Note that the current text indicates that rtcp-mux is mand=
atory-to-use when bundling. The question here is whether we should reopen t=
hat discussion.=C2=A0<div><br></div><div><pre style=3D"line-height:1.2em;ma=
rgin-top:0px;margin-bottom:0px;color:rgb(0,0,0);font-size:13px">

<i><span class=3D"" style=3D"font-family:arial;font-weight:bold">6.2.3.  rt=
cp-mux Attribute</span>

   For each &quot;m=3D&quot; line in a BUNDLE group, an Offerer and Answere=
r MUST
   assign an SDP rtcp-mux attribute [RFC5761].</i></pre><pre style=3D"line-=
height:1.2em;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0);font-size:13=
px"><i><br></i></pre><pre style=3D"line-height:1.2em;margin-top:0px;margin-=
bottom:0px;color:rgb(0,0,0);font-size:13px">

<span style=3D"color:rgb(34,34,34);font-family:arial;font-size:small;line-h=
eight:normal;white-space:normal">My feeling is no, since it creates odd edg=
e cases, such as when you have an existing audio m=3D line with rtcp-mux on=
, and then want to bundle an audio m=3D line without rtcp-mux onto the exis=
ting transport; since you don&#39;t have enough ICE components in the exist=
ing transport, it&#39;s not clear how to perform the bundling.</span><br>

</pre><pre style=3D"line-height:1.2em;margin-top:0px;margin-bottom:0px;colo=
r:rgb(0,0,0);font-size:13px"><i><br></i></pre><pre style=3D"line-height:1.2=
em;margin-top:0px;margin-bottom:0px;color:rgb(0,0,0);font-size:13px"><i><br=
>

</i></pre></div></div><div class=3D"gmail_extra"><br><br><div class=3D"gmai=
l_quote">On Sun, Mar 16, 2014 at 7:16 AM, Christer Holmberg <span dir=3D"lt=
r">&lt;<a href=3D"mailto:christer.holmberg@ericsson.com" target=3D"_blank">=
christer.holmberg@ericsson.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><br>
Hi,<br>
<br>
Do other people have opinions on this?<br>
<br>
Just to clarify: the support of RTP/RTCP mux is already mandated in BUNDLE,=
 and question is not whether the included the a=3Drtcpmux attribute or not =
when RTP/RTCP mux is used - it shall be included. The question is whether w=
e should mandate usage of RTP/RTCP mux within a BUNDLE group.<br>


<br>
Regards,<br>
<br>
Christer<br>
<br>
<br>
<br>
________________________________________<br>
From: mmusic [<a href=3D"mailto:mmusic-bounces@ietf.org">mmusic-bounces@iet=
f.org</a>] on behalf of Justin Uberti [<a href=3D"mailto:juberti@google.com=
">juberti@google.com</a>]<br>
Sent: Friday, 14 March 2014 7:33 PM<br>
To: Magnus Westerlund<br>
Cc: mmusic (E-mail)<br>
Subject: Re: [MMUSIC] On the sparsity of RTP Payload types<br>
<br>
Agree this is a real limitation. In addition to the codecs listed above, no=
te that CN and telephone-event are often needed, and potentially in multipl=
e clockrates.<br>
<br>
(which is why I think we shouldn&#39;t burn PTs on demultiplexing)<br>
<br>
<br>
<br>
<br>
On Fri, Mar 14, 2014 at 2:56 AM, Magnus Westerlund &lt;<a href=3D"mailto:ma=
gnus.westerlund@ericsson.com">magnus.westerlund@ericsson.com</a>&lt;mailto:=
<a href=3D"mailto:magnus.westerlund@ericsson.com">magnus.westerlund@ericsso=
n.com</a>&gt;&gt; wrote:<br>


MMUSIC,<br>
<br>
There&#39;s have been a number of people not believing in that RTP payload<=
br>
types may become a limiting factor when trying to express configurations<br=
>
in SDP or other signaling. Thus, I would like to share my concerns over<br>
how the combination of various mechanism effects the number of actual<br>
payload type configurations needed to negotiated.<br>
<br>
First a set of mechanism that do affect Payload Type usage.<br>
<br>
1. RTCP MUX (RFC 5761)<br>
If one uses RTCP RTP multiplexing, then a number of the RTP payload<br>
types are reserved for identifying the RTCP packets, rather than RTP<br>
payload formats. The default reservation is to reserve PT numbers 64-95.<br=
>
This limits the 128 PTs to 96 available ones.<br>
<br>
2. BUNDLE (draft-ietf-mmusic-sdp-bundle-negotiation)<br>
When using BUNDLE, all listed m=3D sections within a bundle group are in<br=
>
the same RTP session, thus all the PTs share a single common PT<br>
numbering space. Bundle has done what it can to allow re-use across the<br>
m=3D sections for the same configurations.<br>
<br>
3. Multi-Media RTP sessions (draft-ietf-avtcore-multi-media-rtp-session)<br=
>
This mechanism allows multiple media types, like audio, video and text<br>
to share the same RTP session. This in itself does not reduce the<br>
availability, but increases the number of codec configurations that<br>
might be required (or desired) to signal support for.<br>
<br>
4. RTP Retransmission (RFC 4588)<br>
RTP retransmission payload format, requires one PT per PT that one want<br>
to be able to retransmit. If the answer is all of the payload formats,<br>
this doubles the payload format consumption.<br>
<br>
5. XOR based FEC (RFC 5109)<br>
This RTP payload format would normally just consume one PT as it is<br>
capable of recovering the original PT field of a lost packet. However,<br>
it is commonly used with the redundancy payload format (RED) (RFC 2198).<br=
>
And RED requires one to have one RTP payload type per Redundancy<br>
combination. Thus, this results in at least as many PT as PTs one like<br>
to be able to apply FEC on.<br>
<br>
<br>
Lets try using the above in combination and see what the implications are.<=
br>
<br>
So we have 96 available values using RTCP mux, we like to use RTP<br>
Retransmission as well as XOR FEC, to be able to cope with whatever RTT<br>
the path provides and still be robust to packet losses within that<br>
single RTP session. Thus, we end up with a maximum of 32 PTs for<br>
encoding configurations.<br>
<br>
As this is an RTP session that contains both Audio and Video we need to<br>
create a number of configurations for both of media types. This endpoint<br=
>
do support a descent amount of codecs to be compatible with various systems=
.<br>
<br>
Audio: PCMA, PCMU, OPUS, AMR, AMR-WB, EVRC, EVRCWB, G.719, G.722, G.729<br>
Video: H.264, H.265, VP8, VP9, SVC<br>
<br>
On the audio side (10 codecs), this is actually a relative small subset<br>
of the audio codecs that may be carried in RTP. Considering the<br>
different configurations or annex extensions, there is no problem to<br>
actually triple this list when it comes to audio. For video these 5 is a<br=
>
selection of what might be in use in the near future. Also here there<br>
are some potential, although less to offer additional PTs based on the<br>
codec configurations. H.264 could run amok and offer a huge number if<br>
one have a codec implementation that supports many profiles, as each<br>
profile requires its own PT to be offered. As H.264 has 10+ profiles it<br>
is possible. But, a more realistic count is likely 3 PTs.<br>
<br>
The main point is that just the codecs listed above are themselves 15.<br>
With some need to have different configurations for some of them, the<br>
number can relatively easily be doubled and result in that one is up<br>
against the limit (32).<br>
<br>
There are clearly choices that one can make to reduce the usage and save<br=
>
some number of PT values. My main concern is that one more mechanism<br>
that results in equal number of PTs of its own in regards to what it is<br>
associated with, is likely to cause significant concern. And we do have<br>
some that has the potential. Multi stream scalability or simulcast if we<br=
>
would require to indicate each codec configuration with its own payload<br>
type will increase the requirement with a significant factor.<br>
<br>
Thus, this is a potential issue, and an issue that can&#39;t be dismissed,<=
br>
just because your set of limitations makes it unlikely that you will run<br=
>
into it. We do need to ensure that mechanisms doesn&#39;t waste PT values t=
o<br>
achieve some other gain. This is becoming a real limitation.<br>
<br>
Cheers<br>
<br>
Magnus Westerlund<br>
<br>
----------------------------------------------------------------------<br>
Services, Media and Network features, Ericsson Research EAB/TXM<br>
----------------------------------------------------------------------<br>
Ericsson AB =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 | Phone=
 =C2=A0+46 10 7148287<br>
F=C3=A4r=C3=B6gatan 6 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 | Mobile +46 73 0949079<br>
SE-164 80 Stockholm, Sweden | mailto: <a href=3D"mailto:magnus.westerlund@e=
ricsson.com">magnus.westerlund@ericsson.com</a>&lt;mailto:<a href=3D"mailto=
:magnus.westerlund@ericsson.com">magnus.westerlund@ericsson.com</a>&gt;<br>


----------------------------------------------------------------------<br>
<br>
_______________________________________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a>&lt;mailto:<a href=3D=
"mailto:mmusic@ietf.org">mmusic@ietf.org</a>&gt;<br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/mmusic</a><br>
<br>
</blockquote></div><br></div>

--001a11334c38e0c3eb04f4fea5d6--


From nobody Wed Mar 19 19:28:34 2014
Return-Path: <martin.thomson@gmail.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 82F711A063C for <mmusic@ietfa.amsl.com>; Wed, 19 Mar 2014 19:28:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.399
X-Spam-Level: 
X-Spam-Status: No, score=-1.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_17=0.6, 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 TfDc6X2AzltO for <mmusic@ietfa.amsl.com>; Wed, 19 Mar 2014 19:28:28 -0700 (PDT)
Received: from mail-wi0-x230.google.com (mail-wi0-x230.google.com [IPv6:2a00:1450:400c:c05::230]) by ietfa.amsl.com (Postfix) with ESMTP id 6F5081A0471 for <mmusic@ietf.org>; Wed, 19 Mar 2014 19:28:28 -0700 (PDT)
Received: by mail-wi0-f176.google.com with SMTP id hr14so5715294wib.3 for <mmusic@ietf.org>; Wed, 19 Mar 2014 19:28:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=VrlP+36rkrCq7xasZBN7cXa/y4dsa4PTuYFM2SccGHE=; b=K4e4R37z3bjSydC7Fz8rLLw8MJAwiZWoyGU8wRWhgmGOOx6BZOVekrzDpxCjbfdTDf fxIo9/T/TNv8zZeOXFhSkZavpvWetb3SEYLDprEBwcUfthJUS3fD8IgY1hVLqHZGdg2x c7wyfjTWKgay1DKECw3IqDbVY+R1ILu/DHVqsV7eI/IPLfOFsQ0Zyg7C1EHDisc5rdvu X/lEGP9cdtJ0yEu2bw1fcBl1+AnSXjFXXOxjb3+2vSP42GEdTQ4sJ7V1V3d0uYrqBn5y SfC7V6fRjDW6De0nBCZt0jLLKFxC3mRoVUCUUfIJQh+r9T9dvfeotNVO+ZWspjxlHYkG iTOw==
MIME-Version: 1.0
X-Received: by 10.180.84.73 with SMTP id w9mr21598344wiy.58.1395282499075; Wed, 19 Mar 2014 19:28:19 -0700 (PDT)
Received: by 10.227.147.10 with HTTP; Wed, 19 Mar 2014 19:28:19 -0700 (PDT)
Received: by 10.227.147.10 with HTTP; Wed, 19 Mar 2014 19:28:19 -0700 (PDT)
In-Reply-To: <CAOJ7v-0Lt9o-wzzA5ppPYb1fVyjbS=mXLSEooD=xXDh4RjiB7A@mail.gmail.com>
References: <7594FB04B1934943A5C02806D1A2204B1D23329D@ESESSMB209.ericsson.se> <CAOJ7v-0Lt9o-wzzA5ppPYb1fVyjbS=mXLSEooD=xXDh4RjiB7A@mail.gmail.com>
Date: Wed, 19 Mar 2014 19:28:19 -0700
Message-ID: <CABkgnnWzd6ko3o7VKVe2Xt5W50pxkJ7fv7hVcvt7REZMN5pGOQ@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Justin Uberti <juberti@google.com>
Content-Type: multipart/alternative; boundary=f46d04440492b805e504f500855c
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/QwKbjh8JxyjZZpgOR-flENLBvzI
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, mmusic@ietf.org, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] BUNDLE Q14: Mandate usage of RTP/RTCP mux within a BUNDLE group? [was: On the sparsity of RTP Payload types]
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: Thu, 20 Mar 2014 02:28:32 -0000

--f46d04440492b805e504f500855c
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I have to agree with Justin here. Fewer moving parts that way. BUNGLE is
already complex enough.
On Mar 19, 2014 5:14 PM, "Justin Uberti" <juberti@google.com> wrote:

> Note that the current text indicates that rtcp-mux is mandatory-to-use
> when bundling. The question here is whether we should reopen that
> discussion.
>
>
> *6.2.3.  rtcp-mux Attribute
>
>    For each "m=3D" line in a BUNDLE group, an Offerer and Answerer MUST
>    assign an SDP rtcp-mux attribute [RFC5761].*
>
>
>
> My feeling is no, since it creates odd edge cases, such as when you have =
an existing audio m=3D line with rtcp-mux on, and then want to bundle an au=
dio m=3D line without rtcp-mux onto the existing transport; since you don't=
 have enough ICE components in the existing transport, it's not clear how t=
o perform the bundling.
>
>
>
>
>
>
> On Sun, Mar 16, 2014 at 7:16 AM, Christer Holmberg <
> christer.holmberg@ericsson.com> wrote:
>
>>
>> Hi,
>>
>> Do other people have opinions on this?
>>
>> Just to clarify: the support of RTP/RTCP mux is already mandated in
>> BUNDLE, and question is not whether the included the a=3Drtcpmux attribu=
te or
>> not when RTP/RTCP mux is used - it shall be included. The question is
>> whether we should mandate usage of RTP/RTCP mux within a BUNDLE group.
>>
>> Regards,
>>
>> Christer
>>
>>
>>
>> ________________________________________
>> From: mmusic [mmusic-bounces@ietf.org] on behalf of Justin Uberti [
>> juberti@google.com]
>> Sent: Friday, 14 March 2014 7:33 PM
>> To: Magnus Westerlund
>> Cc: mmusic (E-mail)
>> Subject: Re: [MMUSIC] On the sparsity of RTP Payload types
>>
>> Agree this is a real limitation. In addition to the codecs listed above,
>> note that CN and telephone-event are often needed, and potentially in
>> multiple clockrates.
>>
>> (which is why I think we shouldn't burn PTs on demultiplexing)
>>
>>
>>
>>
>> On Fri, Mar 14, 2014 at 2:56 AM, Magnus Westerlund <
>> magnus.westerlund@ericsson.com<mailto:magnus.westerlund@ericsson.com>>
>> wrote:
>> MMUSIC,
>>
>> There's have been a number of people not believing in that RTP payload
>> types may become a limiting factor when trying to express configurations
>> in SDP or other signaling. Thus, I would like to share my concerns over
>> how the combination of various mechanism effects the number of actual
>> payload type configurations needed to negotiated.
>>
>> First a set of mechanism that do affect Payload Type usage.
>>
>> 1. RTCP MUX (RFC 5761)
>> If one uses RTCP RTP multiplexing, then a number of the RTP payload
>> types are reserved for identifying the RTCP packets, rather than RTP
>> payload formats. The default reservation is to reserve PT numbers 64-95.
>> This limits the 128 PTs to 96 available ones.
>>
>> 2. BUNDLE (draft-ietf-mmusic-sdp-bundle-negotiation)
>> When using BUNDLE, all listed m=3D sections within a bundle group are in
>> the same RTP session, thus all the PTs share a single common PT
>> numbering space. Bundle has done what it can to allow re-use across the
>> m=3D sections for the same configurations.
>>
>> 3. Multi-Media RTP sessions (draft-ietf-avtcore-multi-media-rtp-session)
>> This mechanism allows multiple media types, like audio, video and text
>> to share the same RTP session. This in itself does not reduce the
>> availability, but increases the number of codec configurations that
>> might be required (or desired) to signal support for.
>>
>> 4. RTP Retransmission (RFC 4588)
>> RTP retransmission payload format, requires one PT per PT that one want
>> to be able to retransmit. If the answer is all of the payload formats,
>> this doubles the payload format consumption.
>>
>> 5. XOR based FEC (RFC 5109)
>> This RTP payload format would normally just consume one PT as it is
>> capable of recovering the original PT field of a lost packet. However,
>> it is commonly used with the redundancy payload format (RED) (RFC 2198).
>> And RED requires one to have one RTP payload type per Redundancy
>> combination. Thus, this results in at least as many PT as PTs one like
>> to be able to apply FEC on.
>>
>>
>> Lets try using the above in combination and see what the implications ar=
e.
>>
>> So we have 96 available values using RTCP mux, we like to use RTP
>> Retransmission as well as XOR FEC, to be able to cope with whatever RTT
>> the path provides and still be robust to packet losses within that
>> single RTP session. Thus, we end up with a maximum of 32 PTs for
>> encoding configurations.
>>
>> As this is an RTP session that contains both Audio and Video we need to
>> create a number of configurations for both of media types. This endpoint
>> do support a descent amount of codecs to be compatible with various
>> systems.
>>
>> Audio: PCMA, PCMU, OPUS, AMR, AMR-WB, EVRC, EVRCWB, G.719, G.722, G.729
>> Video: H.264, H.265, VP8, VP9, SVC
>>
>> On the audio side (10 codecs), this is actually a relative small subset
>> of the audio codecs that may be carried in RTP. Considering the
>> different configurations or annex extensions, there is no problem to
>> actually triple this list when it comes to audio. For video these 5 is a
>> selection of what might be in use in the near future. Also here there
>> are some potential, although less to offer additional PTs based on the
>> codec configurations. H.264 could run amok and offer a huge number if
>> one have a codec implementation that supports many profiles, as each
>> profile requires its own PT to be offered. As H.264 has 10+ profiles it
>> is possible. But, a more realistic count is likely 3 PTs.
>>
>> The main point is that just the codecs listed above are themselves 15.
>> With some need to have different configurations for some of them, the
>> number can relatively easily be doubled and result in that one is up
>> against the limit (32).
>>
>> There are clearly choices that one can make to reduce the usage and save
>> some number of PT values. My main concern is that one more mechanism
>> that results in equal number of PTs of its own in regards to what it is
>> associated with, is likely to cause significant concern. And we do have
>> some that has the potential. Multi stream scalability or simulcast if we
>> would require to indicate each codec configuration with its own payload
>> type will increase the requirement with a significant factor.
>>
>> Thus, this is a potential issue, and an issue that can't be dismissed,
>> just because your set of limitations makes it unlikely that you will run
>> into it. We do need to ensure that mechanisms doesn't waste PT values to
>> achieve some other gain. This is becoming a real limitation.
>>
>> Cheers
>>
>> Magnus Westerlund
>>
>> ----------------------------------------------------------------------
>> Services, Media and Network features, Ericsson Research EAB/TXM
>> ----------------------------------------------------------------------
>> Ericsson AB                 | Phone  +46 10 7148287
>> F=C3=A4r=C3=B6gatan 6                 | Mobile +46 73 0949079
>> SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
>> <mailto:magnus.westerlund@ericsson.com>
>> ----------------------------------------------------------------------
>>
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org<mailto:mmusic@ietf.org>
>> https://www.ietf.org/mailman/listinfo/mmusic
>>
>>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>
>

--f46d04440492b805e504f500855c
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr">I have to agree with Justin here. Fewer moving parts that wa=
y. BUNGLE is already complex enough.</p>
<div class=3D"gmail_quote">On Mar 19, 2014 5:14 PM, &quot;Justin Uberti&quo=
t; &lt;<a href=3D"mailto:juberti@google.com">juberti@google.com</a>&gt; wro=
te:<br type=3D"attribution"><blockquote class=3D"gmail_quote" style=3D"marg=
in:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir=3D"ltr">Note that the current text indicates that rtcp-mux is mand=
atory-to-use when bundling. The question here is whether we should reopen t=
hat discussion.=C2=A0<div><br></div><div><pre style=3D"line-height:1.2em;fo=
nt-size:13px;margin-bottom:0px;margin-top:0px">


<i><span style=3D"font-family:arial;font-weight:bold">6.2.3.  rtcp-mux Attr=
ibute</span>

   For each &quot;m=3D&quot; line in a BUNDLE group, an Offerer and Answere=
r MUST
   assign an SDP rtcp-mux attribute [RFC5761].</i></pre><pre style=3D"line-=
height:1.2em;font-size:13px;margin-bottom:0px;margin-top:0px"><i><br></i></=
pre><pre style=3D"line-height:1.2em;font-size:13px;margin-bottom:0px;margin=
-top:0px">


<span style=3D"color:rgb(34,34,34);font-family:arial;font-size:small;line-h=
eight:normal;white-space:normal">My feeling is no, since it creates odd edg=
e cases, such as when you have an existing audio m=3D line with rtcp-mux on=
, and then want to bundle an audio m=3D line without rtcp-mux onto the exis=
ting transport; since you don&#39;t have enough ICE components in the exist=
ing transport, it&#39;s not clear how to perform the bundling.</span><br>


</pre><pre style=3D"line-height:1.2em;font-size:13px;margin-bottom:0px;marg=
in-top:0px"><i><br></i></pre><pre style=3D"line-height:1.2em;font-size:13px=
;margin-bottom:0px;margin-top:0px"><i><br>

</i></pre></div></div><div class=3D"gmail_extra"><br><br><div class=3D"gmai=
l_quote">On Sun, Mar 16, 2014 at 7:16 AM, Christer Holmberg <span dir=3D"lt=
r">&lt;<a href=3D"mailto:christer.holmberg@ericsson.com" target=3D"_blank">=
christer.holmberg@ericsson.com</a>&gt;</span> wrote:<br>


<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><br>
Hi,<br>
<br>
Do other people have opinions on this?<br>
<br>
Just to clarify: the support of RTP/RTCP mux is already mandated in BUNDLE,=
 and question is not whether the included the a=3Drtcpmux attribute or not =
when RTP/RTCP mux is used - it shall be included. The question is whether w=
e should mandate usage of RTP/RTCP mux within a BUNDLE group.<br>



<br>
Regards,<br>
<br>
Christer<br>
<br>
<br>
<br>
________________________________________<br>
From: mmusic [<a href=3D"mailto:mmusic-bounces@ietf.org" target=3D"_blank">=
mmusic-bounces@ietf.org</a>] on behalf of Justin Uberti [<a href=3D"mailto:=
juberti@google.com" target=3D"_blank">juberti@google.com</a>]<br>
Sent: Friday, 14 March 2014 7:33 PM<br>
To: Magnus Westerlund<br>
Cc: mmusic (E-mail)<br>
Subject: Re: [MMUSIC] On the sparsity of RTP Payload types<br>
<br>
Agree this is a real limitation. In addition to the codecs listed above, no=
te that CN and telephone-event are often needed, and potentially in multipl=
e clockrates.<br>
<br>
(which is why I think we shouldn&#39;t burn PTs on demultiplexing)<br>
<br>
<br>
<br>
<br>
On Fri, Mar 14, 2014 at 2:56 AM, Magnus Westerlund &lt;<a href=3D"mailto:ma=
gnus.westerlund@ericsson.com" target=3D"_blank">magnus.westerlund@ericsson.=
com</a>&lt;mailto:<a href=3D"mailto:magnus.westerlund@ericsson.com" target=
=3D"_blank">magnus.westerlund@ericsson.com</a>&gt;&gt; wrote:<br>



MMUSIC,<br>
<br>
There&#39;s have been a number of people not believing in that RTP payload<=
br>
types may become a limiting factor when trying to express configurations<br=
>
in SDP or other signaling. Thus, I would like to share my concerns over<br>
how the combination of various mechanism effects the number of actual<br>
payload type configurations needed to negotiated.<br>
<br>
First a set of mechanism that do affect Payload Type usage.<br>
<br>
1. RTCP MUX (RFC 5761)<br>
If one uses RTCP RTP multiplexing, then a number of the RTP payload<br>
types are reserved for identifying the RTCP packets, rather than RTP<br>
payload formats. The default reservation is to reserve PT numbers 64-95.<br=
>
This limits the 128 PTs to 96 available ones.<br>
<br>
2. BUNDLE (draft-ietf-mmusic-sdp-bundle-negotiation)<br>
When using BUNDLE, all listed m=3D sections within a bundle group are in<br=
>
the same RTP session, thus all the PTs share a single common PT<br>
numbering space. Bundle has done what it can to allow re-use across the<br>
m=3D sections for the same configurations.<br>
<br>
3. Multi-Media RTP sessions (draft-ietf-avtcore-multi-media-rtp-session)<br=
>
This mechanism allows multiple media types, like audio, video and text<br>
to share the same RTP session. This in itself does not reduce the<br>
availability, but increases the number of codec configurations that<br>
might be required (or desired) to signal support for.<br>
<br>
4. RTP Retransmission (RFC 4588)<br>
RTP retransmission payload format, requires one PT per PT that one want<br>
to be able to retransmit. If the answer is all of the payload formats,<br>
this doubles the payload format consumption.<br>
<br>
5. XOR based FEC (RFC 5109)<br>
This RTP payload format would normally just consume one PT as it is<br>
capable of recovering the original PT field of a lost packet. However,<br>
it is commonly used with the redundancy payload format (RED) (RFC 2198).<br=
>
And RED requires one to have one RTP payload type per Redundancy<br>
combination. Thus, this results in at least as many PT as PTs one like<br>
to be able to apply FEC on.<br>
<br>
<br>
Lets try using the above in combination and see what the implications are.<=
br>
<br>
So we have 96 available values using RTCP mux, we like to use RTP<br>
Retransmission as well as XOR FEC, to be able to cope with whatever RTT<br>
the path provides and still be robust to packet losses within that<br>
single RTP session. Thus, we end up with a maximum of 32 PTs for<br>
encoding configurations.<br>
<br>
As this is an RTP session that contains both Audio and Video we need to<br>
create a number of configurations for both of media types. This endpoint<br=
>
do support a descent amount of codecs to be compatible with various systems=
.<br>
<br>
Audio: PCMA, PCMU, OPUS, AMR, AMR-WB, EVRC, EVRCWB, G.719, G.722, G.729<br>
Video: H.264, H.265, VP8, VP9, SVC<br>
<br>
On the audio side (10 codecs), this is actually a relative small subset<br>
of the audio codecs that may be carried in RTP. Considering the<br>
different configurations or annex extensions, there is no problem to<br>
actually triple this list when it comes to audio. For video these 5 is a<br=
>
selection of what might be in use in the near future. Also here there<br>
are some potential, although less to offer additional PTs based on the<br>
codec configurations. H.264 could run amok and offer a huge number if<br>
one have a codec implementation that supports many profiles, as each<br>
profile requires its own PT to be offered. As H.264 has 10+ profiles it<br>
is possible. But, a more realistic count is likely 3 PTs.<br>
<br>
The main point is that just the codecs listed above are themselves 15.<br>
With some need to have different configurations for some of them, the<br>
number can relatively easily be doubled and result in that one is up<br>
against the limit (32).<br>
<br>
There are clearly choices that one can make to reduce the usage and save<br=
>
some number of PT values. My main concern is that one more mechanism<br>
that results in equal number of PTs of its own in regards to what it is<br>
associated with, is likely to cause significant concern. And we do have<br>
some that has the potential. Multi stream scalability or simulcast if we<br=
>
would require to indicate each codec configuration with its own payload<br>
type will increase the requirement with a significant factor.<br>
<br>
Thus, this is a potential issue, and an issue that can&#39;t be dismissed,<=
br>
just because your set of limitations makes it unlikely that you will run<br=
>
into it. We do need to ensure that mechanisms doesn&#39;t waste PT values t=
o<br>
achieve some other gain. This is becoming a real limitation.<br>
<br>
Cheers<br>
<br>
Magnus Westerlund<br>
<br>
----------------------------------------------------------------------<br>
Services, Media and Network features, Ericsson Research EAB/TXM<br>
----------------------------------------------------------------------<br>
Ericsson AB =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 | Phone=
 =C2=A0+46 10 7148287<br>
F=C3=A4r=C3=B6gatan 6 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 | Mobile +46 73 0949079<br>
SE-164 80 Stockholm, Sweden | mailto: <a href=3D"mailto:magnus.westerlund@e=
ricsson.com" target=3D"_blank">magnus.westerlund@ericsson.com</a>&lt;mailto=
:<a href=3D"mailto:magnus.westerlund@ericsson.com" target=3D"_blank">magnus=
.westerlund@ericsson.com</a>&gt;<br>



----------------------------------------------------------------------<br>
<br>
_______________________________________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.org</a>&lt=
;mailto:<a href=3D"mailto:mmusic@ietf.org" target=3D"_blank">mmusic@ietf.or=
g</a>&gt;<br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/mmusic</a><br>
<br>
</blockquote></div><br></div>
<br>_______________________________________________<br>
mmusic mailing list<br>
<a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/mmusic" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/mmusic</a><br>
<br></blockquote></div>

--f46d04440492b805e504f500855c--


From nobody Thu Mar 20 00:50:35 2014
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 E0DBE1A0844 for <mmusic@ietfa.amsl.com>; Thu, 20 Mar 2014 00:50:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.251
X-Spam-Level: 
X-Spam-Status: No, score=-3.251 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, J_CHICKENPOX_17=0.6, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 je5d3pFEnh8F for <mmusic@ietfa.amsl.com>; Thu, 20 Mar 2014 00:50:29 -0700 (PDT)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id 199841A066E for <mmusic@ietf.org>; Thu, 20 Mar 2014 00:50:28 -0700 (PDT)
X-AuditID: c1b4fb25-b7f038e000005d01-71-532a9dbb1e8d
Received: from ESESSHC015.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id EE.7D.23809.BBD9A235; Thu, 20 Mar 2014 08:50:19 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.213]) by ESESSHC015.ericsson.se ([153.88.183.63]) with mapi id 14.02.0387.000; Thu, 20 Mar 2014 08:49:25 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Justin Uberti <juberti@google.com>
Thread-Topic: BUNDLE Q14: Mandate usage of RTP/RTCP mux within a BUNDLE group? [was: On the sparsity of RTP Payload types]
Thread-Index: AQHPQSJW5SOYVCaDbkiksfP7ze4/V5rpD3UAgACN8/A=
Date: Thu, 20 Mar 2014 07:49:25 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D2545A1@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D23329D@ESESSMB209.ericsson.se> <CAOJ7v-0Lt9o-wzzA5ppPYb1fVyjbS=mXLSEooD=xXDh4RjiB7A@mail.gmail.com>
In-Reply-To: <CAOJ7v-0Lt9o-wzzA5ppPYb1fVyjbS=mXLSEooD=xXDh4RjiB7A@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.17]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrOLMWRmVeSWpSXmKPExsUyM+Jvje7uuVrBBjOPSVlsnSpkMXX5YxYH Jo8Fm0o9liz5yRTAFMVlk5Kak1mWWqRvl8CVMXfBMvaCdwEVz6csYmpgfOLXxcjJISFgIjFx zS4WCFtM4sK99WxdjFwcQgKHGCUmzFvLCOEsYZS433cCKMPBwSZgIdH9TxukQURATeLhrF2s IGFmgViJI3/AZgoLVEv0Xm1lgiipkbi5ajczhG0lcfvYH0YQm0VAVeLNmaXsIDavgK/EjNZO VohVUxglLt9eBdbAKRAIdMNLMJsR6Ljvp9aADWUWEJe49WQ+E8TRAhJL9pxnhrBFJV4+/gd2 j4SAosTyfjmI0zQl1u/Sh+hUlJjS/RBqraDEyZlPWCYwis1CMnQWQscsJB2zkHQsYGRZxcie m5iZk15utIkRGBkHt/xW3cF455zIIUZpDhYlcd4Pb52DhATSE0tSs1NTC1KL4otKc1KLDzEy cXBKNTBW5EvN0efm2C1wPOu5rZvWlYAQb8sZkluq/+y3vcLxb7LF98e83L41z7QTvliyBodE 5N16IiTl+6D9tG3nRa/8fXxvAmrL/heoXra8MnFJTLxEzdMXwp9vJk1iuSkuIr/iqeJBxQtv Jfp2r1YIrZ3gVVx3bYr2aocljhUflZ/U/w5oW1xzZLUSS3FGoqEWc1FxIgAXpbdzWgIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/u3LC5jOiGZN4JBj4c14FHmKQW3c
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, "mmusic \(E-mail\)" <mmusic@ietf.org>
Subject: Re: [MMUSIC] BUNDLE Q14: Mandate usage of RTP/RTCP mux within a BUNDLE group? [was: On the sparsity of RTP Payload types]
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: Thu, 20 Mar 2014 07:50:33 -0000

SGksDQoNCj42LjIuMy4gIHJ0Y3AtbXV4IEF0dHJpYnV0ZQ0KPg0KPiAgIEZvciBlYWNoICJtPSIg
bGluZSBpbiBhIEJVTkRMRSBncm91cCwgYW4gT2ZmZXJlciBhbmQgQW5zd2VyZXIgTVVTVA0KPiAg
IGFzc2lnbiBhbiBTRFAgcnRjcC1tdXggYXR0cmlidXRlIFtSRkM1NzYxXS4NCj4NCj4NCj4NCj4g
TXkgZmVlbGluZyBpcyBubywgc2luY2UgaXQgY3JlYXRlcyBvZGQgZWRnZSBjYXNlcywgc3VjaCBh
cyB3aGVuIHlvdSBoYXZlIGFuIGV4aXN0aW5nIGF1ZGlvIG09IGxpbmUgd2l0aCBydGNwLW11eCBv
biwgYW5kIHRoZW4gd2FudCB0byBidW5kbGUgYW4gDQo+IGF1ZGlvIG09IGxpbmUgd2l0aG91dCBy
dGNwLW11eCBvbnRvIHRoZSBleGlzdGluZyB0cmFuc3BvcnQ7IHNpbmNlIHlvdSBkb24ndCBoYXZl
IGVub3VnaCBJQ0UgY29tcG9uZW50cyBpbiB0aGUgZXhpc3RpbmcgdHJhbnNwb3J0LCBpdCdzIG5v
dCBjbGVhciBob3cgdG8gcGVyZm9ybSB0aGUgYnVuZGxpbmcuDQoNCldpdGhpbiBhIEJVTkRMRSBn
cm91cCwgb25lIGNhbm5vdCB1c2UgUlRQL1JUQ1AgbXV4IGZvciBzb21lIG0tIGxpbmVzLCBhbmQg
bm90IHVzZSBSVFAvUlRDUCBtdXggZm9yIHNvbWUgb3RoZXIgbS0gbGluZXMuIEVpdGhlciB5b3Ug
dXNlIFJUUC9SVENQIG11eCBmb3IgdGhlIHdob2xlIEJVTkRMRSBncm91cCwgb3IgeW91IGRvbid0
IHVzZSBpdC4gSWYgdGhhdCBpcyB1bmNsZWFyIGluIHRoZSBzcGVjLCB3ZSBjYW4gYWRkIHNvbWUg
dGV4dCBhYm91dCB0aGF0Lg0KDQpUaGVuLCBpZiB0aGUgY29uY2VybiBpcyB3aGVuIGFkZGluZyBu
ZXcgbS0gbGluZXMgdG8gYW4gZXhpc3RpbmcgQlVORExFIGdyb3VwLCB3ZSBjb3VsZCBhbHdheXMg
c2F5IHRoYXQsIGlmIHlvdSBoYXZlIGFuIGV4aXN0aW5nIEJVTkRMRSBncm91cCB3aXRoIFJUUC9S
VENQIG11eCwgbmV3IG0tIGxpbmVzIGFkZGVkIHRvIHRoYXQgQlVORExFIGdyb3VwIE1VU1QgYWxz
byB1c2UgUlRQL1JUQ1AgbXV4Lg0KDQpJIGd1ZXNzIHRoZSBiaWcgcXVlc3Rpb24gaGVyZSBpcyB3
aGV0aGVyIHRoZXJlIHdpbGwgYmUgYSByaXNrIG9mIHJ1bm5pbmcgb3V0IG9mIHBheWxvYWQgdHlw
ZSB2YWx1ZXMgaWYgbWFuZGF0aW5nIFJUUC9SVENQIG11eC4gTWFnbnVzIGFuZCBKdXN0aW4gaGF2
ZSBnaXZlbiBzb21lIGdvb2QgaW5zaWdodCBpbnRvICJwYXlsb2FkIHR5cGUgY29uc3VtcHRpb24i
Lg0KDQpSZWdhcmRzLA0KDQpDaHJpc3Rlcg0KDQpOb3RlOiBXaGVuIHRhbGtpbmcgYWJvdXQgbS0g
bGluZXMsIEkgcmVmZXIgdG8gbS0gbGluZXMgZm9yIFJUUCB0cmFuc3BvcnQuIA0KDQoNCg0KDQoN
Cg0KDQoNCk9uIFN1biwgTWFyIDE2LCAyMDE0IGF0IDc6MTYgQU0sIENocmlzdGVyIEhvbG1iZXJn
IDxjaHJpc3Rlci5ob2xtYmVyZ0Blcmljc3Nvbi5jb20+IHdyb3RlOg0KDQpIaSwNCg0KRG8gb3Ro
ZXIgcGVvcGxlIGhhdmUgb3BpbmlvbnMgb24gdGhpcz8NCg0KSnVzdCB0byBjbGFyaWZ5OiB0aGUg
c3VwcG9ydCBvZiBSVFAvUlRDUCBtdXggaXMgYWxyZWFkeSBtYW5kYXRlZCBpbiBCVU5ETEUsIGFu
ZCBxdWVzdGlvbiBpcyBub3Qgd2hldGhlciB0aGUgaW5jbHVkZWQgdGhlIGE9cnRjcG11eCBhdHRy
aWJ1dGUgb3Igbm90IHdoZW4gUlRQL1JUQ1AgbXV4IGlzIHVzZWQgLSBpdCBzaGFsbCBiZSBpbmNs
dWRlZC4gVGhlIHF1ZXN0aW9uIGlzIHdoZXRoZXIgd2Ugc2hvdWxkIG1hbmRhdGUgdXNhZ2Ugb2Yg
UlRQL1JUQ1AgbXV4IHdpdGhpbiBhIEJVTkRMRSBncm91cC4NCg0KUmVnYXJkcywNCg0KQ2hyaXN0
ZXINCg0KDQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCkZyb206
IG1tdXNpYyBbbW11c2ljLWJvdW5jZXNAaWV0Zi5vcmddIG9uIGJlaGFsZiBvZiBKdXN0aW4gVWJl
cnRpIFtqdWJlcnRpQGdvb2dsZS5jb21dDQpTZW50OiBGcmlkYXksIDE0IE1hcmNoIDIwMTQgNzoz
MyBQTQ0KVG86IE1hZ251cyBXZXN0ZXJsdW5kDQpDYzogbW11c2ljIChFLW1haWwpDQpTdWJqZWN0
OiBSZTogW01NVVNJQ10gT24gdGhlIHNwYXJzaXR5IG9mIFJUUCBQYXlsb2FkIHR5cGVzDQoNCkFn
cmVlIHRoaXMgaXMgYSByZWFsIGxpbWl0YXRpb24uIEluIGFkZGl0aW9uIHRvIHRoZSBjb2RlY3Mg
bGlzdGVkIGFib3ZlLCBub3RlIHRoYXQgQ04gYW5kIHRlbGVwaG9uZS1ldmVudCBhcmUgb2Z0ZW4g
bmVlZGVkLCBhbmQgcG90ZW50aWFsbHkgaW4gbXVsdGlwbGUgY2xvY2tyYXRlcy4NCg0KKHdoaWNo
IGlzIHdoeSBJIHRoaW5rIHdlIHNob3VsZG4ndCBidXJuIFBUcyBvbiBkZW11bHRpcGxleGluZykN
Cg0KDQoNCg0KT24gRnJpLCBNYXIgMTQsIDIwMTQgYXQgMjo1NiBBTSwgTWFnbnVzIFdlc3Rlcmx1
bmQgPG1hZ251cy53ZXN0ZXJsdW5kQGVyaWNzc29uLmNvbTxtYWlsdG86bWFnbnVzLndlc3Rlcmx1
bmRAZXJpY3Nzb24uY29tPj4gd3JvdGU6DQpNTVVTSUMsDQoNClRoZXJlJ3MgaGF2ZSBiZWVuIGEg
bnVtYmVyIG9mIHBlb3BsZSBub3QgYmVsaWV2aW5nIGluIHRoYXQgUlRQIHBheWxvYWQNCnR5cGVz
IG1heSBiZWNvbWUgYSBsaW1pdGluZyBmYWN0b3Igd2hlbiB0cnlpbmcgdG8gZXhwcmVzcyBjb25m
aWd1cmF0aW9ucw0KaW4gU0RQIG9yIG90aGVyIHNpZ25hbGluZy4gVGh1cywgSSB3b3VsZCBsaWtl
IHRvIHNoYXJlIG15IGNvbmNlcm5zIG92ZXINCmhvdyB0aGUgY29tYmluYXRpb24gb2YgdmFyaW91
cyBtZWNoYW5pc20gZWZmZWN0cyB0aGUgbnVtYmVyIG9mIGFjdHVhbA0KcGF5bG9hZCB0eXBlIGNv
bmZpZ3VyYXRpb25zIG5lZWRlZCB0byBuZWdvdGlhdGVkLg0KDQpGaXJzdCBhIHNldCBvZiBtZWNo
YW5pc20gdGhhdCBkbyBhZmZlY3QgUGF5bG9hZCBUeXBlIHVzYWdlLg0KDQoxLiBSVENQIE1VWCAo
UkZDIDU3NjEpDQpJZiBvbmUgdXNlcyBSVENQIFJUUCBtdWx0aXBsZXhpbmcsIHRoZW4gYSBudW1i
ZXIgb2YgdGhlIFJUUCBwYXlsb2FkDQp0eXBlcyBhcmUgcmVzZXJ2ZWQgZm9yIGlkZW50aWZ5aW5n
IHRoZSBSVENQIHBhY2tldHMsIHJhdGhlciB0aGFuIFJUUA0KcGF5bG9hZCBmb3JtYXRzLiBUaGUg
ZGVmYXVsdCByZXNlcnZhdGlvbiBpcyB0byByZXNlcnZlIFBUIG51bWJlcnMgNjQtOTUuDQpUaGlz
IGxpbWl0cyB0aGUgMTI4IFBUcyB0byA5NiBhdmFpbGFibGUgb25lcy4NCg0KMi4gQlVORExFIChk
cmFmdC1pZXRmLW1tdXNpYy1zZHAtYnVuZGxlLW5lZ290aWF0aW9uKQ0KV2hlbiB1c2luZyBCVU5E
TEUsIGFsbCBsaXN0ZWQgbT0gc2VjdGlvbnMgd2l0aGluIGEgYnVuZGxlIGdyb3VwIGFyZSBpbg0K
dGhlIHNhbWUgUlRQIHNlc3Npb24sIHRodXMgYWxsIHRoZSBQVHMgc2hhcmUgYSBzaW5nbGUgY29t
bW9uIFBUDQpudW1iZXJpbmcgc3BhY2UuIEJ1bmRsZSBoYXMgZG9uZSB3aGF0IGl0IGNhbiB0byBh
bGxvdyByZS11c2UgYWNyb3NzIHRoZQ0KbT0gc2VjdGlvbnMgZm9yIHRoZSBzYW1lIGNvbmZpZ3Vy
YXRpb25zLg0KDQozLiBNdWx0aS1NZWRpYSBSVFAgc2Vzc2lvbnMgKGRyYWZ0LWlldGYtYXZ0Y29y
ZS1tdWx0aS1tZWRpYS1ydHAtc2Vzc2lvbikNClRoaXMgbWVjaGFuaXNtIGFsbG93cyBtdWx0aXBs
ZSBtZWRpYSB0eXBlcywgbGlrZSBhdWRpbywgdmlkZW8gYW5kIHRleHQNCnRvIHNoYXJlIHRoZSBz
YW1lIFJUUCBzZXNzaW9uLiBUaGlzIGluIGl0c2VsZiBkb2VzIG5vdCByZWR1Y2UgdGhlDQphdmFp
bGFiaWxpdHksIGJ1dCBpbmNyZWFzZXMgdGhlIG51bWJlciBvZiBjb2RlYyBjb25maWd1cmF0aW9u
cyB0aGF0DQptaWdodCBiZSByZXF1aXJlZCAob3IgZGVzaXJlZCkgdG8gc2lnbmFsIHN1cHBvcnQg
Zm9yLg0KDQo0LiBSVFAgUmV0cmFuc21pc3Npb24gKFJGQyA0NTg4KQ0KUlRQIHJldHJhbnNtaXNz
aW9uIHBheWxvYWQgZm9ybWF0LCByZXF1aXJlcyBvbmUgUFQgcGVyIFBUIHRoYXQgb25lIHdhbnQN
CnRvIGJlIGFibGUgdG8gcmV0cmFuc21pdC4gSWYgdGhlIGFuc3dlciBpcyBhbGwgb2YgdGhlIHBh
eWxvYWQgZm9ybWF0cywNCnRoaXMgZG91YmxlcyB0aGUgcGF5bG9hZCBmb3JtYXQgY29uc3VtcHRp
b24uDQoNCjUuIFhPUiBiYXNlZCBGRUMgKFJGQyA1MTA5KQ0KVGhpcyBSVFAgcGF5bG9hZCBmb3Jt
YXQgd291bGQgbm9ybWFsbHkganVzdCBjb25zdW1lIG9uZSBQVCBhcyBpdCBpcw0KY2FwYWJsZSBv
ZiByZWNvdmVyaW5nIHRoZSBvcmlnaW5hbCBQVCBmaWVsZCBvZiBhIGxvc3QgcGFja2V0LiBIb3dl
dmVyLA0KaXQgaXMgY29tbW9ubHkgdXNlZCB3aXRoIHRoZSByZWR1bmRhbmN5IHBheWxvYWQgZm9y
bWF0IChSRUQpIChSRkMgMjE5OCkuDQpBbmQgUkVEIHJlcXVpcmVzIG9uZSB0byBoYXZlIG9uZSBS
VFAgcGF5bG9hZCB0eXBlIHBlciBSZWR1bmRhbmN5DQpjb21iaW5hdGlvbi4gVGh1cywgdGhpcyBy
ZXN1bHRzIGluIGF0IGxlYXN0IGFzIG1hbnkgUFQgYXMgUFRzIG9uZSBsaWtlDQp0byBiZSBhYmxl
IHRvIGFwcGx5IEZFQyBvbi4NCg0KDQpMZXRzIHRyeSB1c2luZyB0aGUgYWJvdmUgaW4gY29tYmlu
YXRpb24gYW5kIHNlZSB3aGF0IHRoZSBpbXBsaWNhdGlvbnMgYXJlLg0KDQpTbyB3ZSBoYXZlIDk2
IGF2YWlsYWJsZSB2YWx1ZXMgdXNpbmcgUlRDUCBtdXgsIHdlIGxpa2UgdG8gdXNlIFJUUA0KUmV0
cmFuc21pc3Npb24gYXMgd2VsbCBhcyBYT1IgRkVDLCB0byBiZSBhYmxlIHRvIGNvcGUgd2l0aCB3
aGF0ZXZlciBSVFQNCnRoZSBwYXRoIHByb3ZpZGVzIGFuZCBzdGlsbCBiZSByb2J1c3QgdG8gcGFj
a2V0IGxvc3NlcyB3aXRoaW4gdGhhdA0Kc2luZ2xlIFJUUCBzZXNzaW9uLiBUaHVzLCB3ZSBlbmQg
dXAgd2l0aCBhIG1heGltdW0gb2YgMzIgUFRzIGZvcg0KZW5jb2RpbmcgY29uZmlndXJhdGlvbnMu
DQoNCkFzIHRoaXMgaXMgYW4gUlRQIHNlc3Npb24gdGhhdCBjb250YWlucyBib3RoIEF1ZGlvIGFu
ZCBWaWRlbyB3ZSBuZWVkIHRvDQpjcmVhdGUgYSBudW1iZXIgb2YgY29uZmlndXJhdGlvbnMgZm9y
IGJvdGggb2YgbWVkaWEgdHlwZXMuIFRoaXMgZW5kcG9pbnQNCmRvIHN1cHBvcnQgYSBkZXNjZW50
IGFtb3VudCBvZiBjb2RlY3MgdG8gYmUgY29tcGF0aWJsZSB3aXRoIHZhcmlvdXMgc3lzdGVtcy4N
Cg0KQXVkaW86IFBDTUEsIFBDTVUsIE9QVVMsIEFNUiwgQU1SLVdCLCBFVlJDLCBFVlJDV0IsIEcu
NzE5LCBHLjcyMiwgRy43MjkNClZpZGVvOiBILjI2NCwgSC4yNjUsIFZQOCwgVlA5LCBTVkMNCg0K
T24gdGhlIGF1ZGlvIHNpZGUgKDEwIGNvZGVjcyksIHRoaXMgaXMgYWN0dWFsbHkgYSByZWxhdGl2
ZSBzbWFsbCBzdWJzZXQNCm9mIHRoZSBhdWRpbyBjb2RlY3MgdGhhdCBtYXkgYmUgY2FycmllZCBp
biBSVFAuIENvbnNpZGVyaW5nIHRoZQ0KZGlmZmVyZW50IGNvbmZpZ3VyYXRpb25zIG9yIGFubmV4
IGV4dGVuc2lvbnMsIHRoZXJlIGlzIG5vIHByb2JsZW0gdG8NCmFjdHVhbGx5IHRyaXBsZSB0aGlz
IGxpc3Qgd2hlbiBpdCBjb21lcyB0byBhdWRpby4gRm9yIHZpZGVvIHRoZXNlIDUgaXMgYQ0Kc2Vs
ZWN0aW9uIG9mIHdoYXQgbWlnaHQgYmUgaW4gdXNlIGluIHRoZSBuZWFyIGZ1dHVyZS4gQWxzbyBo
ZXJlIHRoZXJlDQphcmUgc29tZSBwb3RlbnRpYWwsIGFsdGhvdWdoIGxlc3MgdG8gb2ZmZXIgYWRk
aXRpb25hbCBQVHMgYmFzZWQgb24gdGhlDQpjb2RlYyBjb25maWd1cmF0aW9ucy4gSC4yNjQgY291
bGQgcnVuIGFtb2sgYW5kIG9mZmVyIGEgaHVnZSBudW1iZXIgaWYNCm9uZSBoYXZlIGEgY29kZWMg
aW1wbGVtZW50YXRpb24gdGhhdCBzdXBwb3J0cyBtYW55IHByb2ZpbGVzLCBhcyBlYWNoDQpwcm9m
aWxlIHJlcXVpcmVzIGl0cyBvd24gUFQgdG8gYmUgb2ZmZXJlZC4gQXMgSC4yNjQgaGFzIDEwKyBw
cm9maWxlcyBpdA0KaXMgcG9zc2libGUuIEJ1dCwgYSBtb3JlIHJlYWxpc3RpYyBjb3VudCBpcyBs
aWtlbHkgMyBQVHMuDQoNClRoZSBtYWluIHBvaW50IGlzIHRoYXQganVzdCB0aGUgY29kZWNzIGxp
c3RlZCBhYm92ZSBhcmUgdGhlbXNlbHZlcyAxNS4NCldpdGggc29tZSBuZWVkIHRvIGhhdmUgZGlm
ZmVyZW50IGNvbmZpZ3VyYXRpb25zIGZvciBzb21lIG9mIHRoZW0sIHRoZQ0KbnVtYmVyIGNhbiBy
ZWxhdGl2ZWx5IGVhc2lseSBiZSBkb3VibGVkIGFuZCByZXN1bHQgaW4gdGhhdCBvbmUgaXMgdXAN
CmFnYWluc3QgdGhlIGxpbWl0ICgzMikuDQoNClRoZXJlIGFyZSBjbGVhcmx5IGNob2ljZXMgdGhh
dCBvbmUgY2FuIG1ha2UgdG8gcmVkdWNlIHRoZSB1c2FnZSBhbmQgc2F2ZQ0Kc29tZSBudW1iZXIg
b2YgUFQgdmFsdWVzLiBNeSBtYWluIGNvbmNlcm4gaXMgdGhhdCBvbmUgbW9yZSBtZWNoYW5pc20N
CnRoYXQgcmVzdWx0cyBpbiBlcXVhbCBudW1iZXIgb2YgUFRzIG9mIGl0cyBvd24gaW4gcmVnYXJk
cyB0byB3aGF0IGl0IGlzDQphc3NvY2lhdGVkIHdpdGgsIGlzIGxpa2VseSB0byBjYXVzZSBzaWdu
aWZpY2FudCBjb25jZXJuLiBBbmQgd2UgZG8gaGF2ZQ0Kc29tZSB0aGF0IGhhcyB0aGUgcG90ZW50
aWFsLiBNdWx0aSBzdHJlYW0gc2NhbGFiaWxpdHkgb3Igc2ltdWxjYXN0IGlmIHdlDQp3b3VsZCBy
ZXF1aXJlIHRvIGluZGljYXRlIGVhY2ggY29kZWMgY29uZmlndXJhdGlvbiB3aXRoIGl0cyBvd24g
cGF5bG9hZA0KdHlwZSB3aWxsIGluY3JlYXNlIHRoZSByZXF1aXJlbWVudCB3aXRoIGEgc2lnbmlm
aWNhbnQgZmFjdG9yLg0KDQpUaHVzLCB0aGlzIGlzIGEgcG90ZW50aWFsIGlzc3VlLCBhbmQgYW4g
aXNzdWUgdGhhdCBjYW4ndCBiZSBkaXNtaXNzZWQsDQpqdXN0IGJlY2F1c2UgeW91ciBzZXQgb2Yg
bGltaXRhdGlvbnMgbWFrZXMgaXQgdW5saWtlbHkgdGhhdCB5b3Ugd2lsbCBydW4NCmludG8gaXQu
IFdlIGRvIG5lZWQgdG8gZW5zdXJlIHRoYXQgbWVjaGFuaXNtcyBkb2Vzbid0IHdhc3RlIFBUIHZh
bHVlcyB0bw0KYWNoaWV2ZSBzb21lIG90aGVyIGdhaW4uIFRoaXMgaXMgYmVjb21pbmcgYSByZWFs
IGxpbWl0YXRpb24uDQoNCkNoZWVycw0KDQpNYWdudXMgV2VzdGVybHVuZA0KDQotLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tDQpTZXJ2aWNlcywgTWVkaWEgYW5kIE5ldHdvcmsgZmVhdHVyZXMsIEVyaWNzc29uIFJlc2Vh
cmNoIEVBQi9UWE0NCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCkVyaWNzc29uIEFCIMKgIMKgIMKgIMKgIMKgIMKg
IMKgIMKgIHwgUGhvbmUgwqArNDYgMTAgNzE0ODI4Nw0KRsOkcsO2Z2F0YW4gNiDCoCDCoCDCoCDC
oCDCoCDCoCDCoCDCoCB8IE1vYmlsZSArNDYgNzMgMDk0OTA3OQ0KU0UtMTY0IDgwIFN0b2NraG9s
bSwgU3dlZGVuIHwgbWFpbHRvOiBtYWdudXMud2VzdGVybHVuZEBlcmljc3Nvbi5jb208bWFpbHRv
Om1hZ251cy53ZXN0ZXJsdW5kQGVyaWNzc29uLmNvbT4NCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCg0KX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCm1tdXNpYyBtYWlsaW5n
IGxpc3QNCm1tdXNpY0BpZXRmLm9yZzxtYWlsdG86bW11c2ljQGlldGYub3JnPg0KaHR0cHM6Ly93
d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9tbXVzaWMNCg0K


From nobody Thu Mar 20 02:50:17 2014
Return-Path: <magnus.westerlund@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 8F19D1A06F8 for <mmusic@ietfa.amsl.com>; Thu, 20 Mar 2014 02:50:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.851
X-Spam-Level: 
X-Spam-Status: No, score=-3.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 Um1Cjb-3XXo0 for <mmusic@ietfa.amsl.com>; Thu, 20 Mar 2014 02:50:12 -0700 (PDT)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id 1F04E1A0699 for <mmusic@ietf.org>; Thu, 20 Mar 2014 02:50:11 -0700 (PDT)
X-AuditID: c1b4fb25-b7f038e000005d01-47-532ab9cae56b
Received: from ESESSHC001.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id C7.A2.23809.AC9BA235; Thu, 20 Mar 2014 10:50:02 +0100 (CET)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.23) with Microsoft SMTP Server id 14.2.347.0; Thu, 20 Mar 2014 10:50:01 +0100
Message-ID: <532AB9C9.1020602@ericsson.com>
Date: Thu, 20 Mar 2014 10:50:01 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>, Justin Uberti <juberti@google.com>
References: <7594FB04B1934943A5C02806D1A2204B1D23329D@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D23329D@ESESSMB209.ericsson.se>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFuplluLIzCtJLcpLzFFi42KZGfG3RvfUTq1gg0VX5C22ThWymLr8MYsD k8eCTaUeS5b8ZApgiuKySUnNySxLLdK3S+DK+L9kAWvBfqGK11/+MzYwNvJ3MXJySAiYSNxY O48FwhaTuHBvPVsXIxeHkMAhRomzN+6yQDjLGSWOn17M1MXIwcEroC0x8Z0TSAOLgKpE+6w5 YM1sAhYSN380soHYogLBEjsP/GYEsXkFBCVOznwCViMiECPxq+8OWJxZQF2i53cLM4gtLFAt 0X9hM1hcSMBXYuekJ2BxTgE/ifuLN4CtlRAQl+hpDIJo1ZOYcrUFaoy8RPPW2cwQrdoSDU0d rBMYhWYh2TwLScssJC0LGJlXMbLnJmbmpJcbbWIEBunBLb9VdzDeOSdyiFGag0VJnPfDW+cg IYH0xJLU7NTUgtSi+KLSnNTiQ4xMHJxSDYwTjnZMuJj98v53AT7PNVdtixdotM3Ye/DM/YsC R60vSs9ds2Dm5walz2oTHvn/n8t+Y4JNqNfqtx2i7ofSYqquaL5t4uU+qy0sMF9Z9VzX5LDi Dp87k8/3TTG5dvKlzEvh6v8xHh39izd2KVn362090lv+VC1Kgb/A5sBboaxLDeFMRqsnrLdS YinOSDTUYi4qTgQAR2zsDyACAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/7svqimfXSXlAxcdFc3wyGUwdty4
Cc: "mmusic \(E-mail\)" <mmusic@ietf.org>
Subject: Re: [MMUSIC] BUNDLE Q14: Mandate usage of RTP/RTCP mux within a BUNDLE group? [was: On the sparsity of RTP Payload types]
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: Thu, 20 Mar 2014 09:50:14 -0000

On 2014-03-16 15:16, Christer Holmberg wrote:
> 
> Hi,
> 
> Do other people have opinions on this?

I have considered this proposal in a wider context and have the
following reflections and also an additional motivation why I personally
consider it important that a bundle-group shall be possible to be
established with RTCP on either the same transport flow (5-tuple) as
RTP, i.e. using a=rtcp-mux, or using separate transport flows (one for
RTP, one for RTCP), i.e. no a=rtcp-mux.

First of all BUNDLE is a general signaling mechanism it is possible to
apply to any user of SDP offer/answer. WebRTC is the first and the one
which pushed it into existence, but I am pretty certain it will not be
the only user of  the mechanism.

What Justin is pushing for, prevents one to have multiple media streams
of different or the same type, i.e. what ever you put in the same bundle
group, to have RTCP separated on transport level from RTP.

In most cases this doesn't matter, but where it can matter is when using
QoS, for example in cellular environments. Being forced to put RTCP on
the same QoS treatment as the media will either reduce the achievable
quality or increase the cost. Being able to spend these commonly 5% of
bandwidth on improving media or avoiding higher cost is significant in
such an environment.

Thus, I think everyone needs to thing twice about this. Shall really
relatively minor implementation concerns and focus on general Internet
only deployments win out over BUNDLEs applicability and the possibility
to get the most out of any QoS when available.

To be clear, I am fine with having usage of a=rtcp-mux as default
behavior, but from my perspective we need to be able to actually
negotiate if one turns on RTP/RTCP multiplexing using the a=rtcp-mux
attribute when doing an round of offer/answer based signaling.

cheers

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Färögatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From nobody Thu Mar 20 07:56:24 2014
Return-Path: <pkyzivat@alum.mit.edu>
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 6707F1A076E for <mmusic@ietfa.amsl.com>; Thu, 20 Mar 2014 07:56:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] 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 X1J9iukydkdz for <mmusic@ietfa.amsl.com>; Thu, 20 Mar 2014 07:56:20 -0700 (PDT)
Received: from qmta13.westchester.pa.mail.comcast.net (qmta13.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:243]) by ietfa.amsl.com (Postfix) with ESMTP id BCB051A046A for <mmusic@ietf.org>; Thu, 20 Mar 2014 07:56:19 -0700 (PDT)
Received: from omta09.westchester.pa.mail.comcast.net ([76.96.62.20]) by qmta13.westchester.pa.mail.comcast.net with comcast id fokk1n0060SCNGk5DqwAkv; Thu, 20 Mar 2014 14:56:10 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta09.westchester.pa.mail.comcast.net with comcast id fqwA1n00M3ZTu2S3VqwAyT; Thu, 20 Mar 2014 14:56:10 +0000
Message-ID: <532B018A.4080504@alum.mit.edu>
Date: Thu, 20 Mar 2014 10:56:10 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: mmusic@ietf.org
References: <7594FB04B1934943A5C02806D1A2204B1D23329D@ESESSMB209.ericsson.se> <532AB9C9.1020602@ericsson.com>
In-Reply-To: <532AB9C9.1020602@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1395327370; bh=4kIgmGFE77yIM8opaUg9mMBzE9Sdae71nm8e9As2o0s=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=Jp/sRahq3+JAbZyVOQ8x6Po9BEvXj6pynPZaq+DnneU0RRwo6Ylg+kJHKasDfC4Si Ckwk1tHXtZzpW5RcBhzPuYZ5z2JZm4l0N+jNYbyQp7pqwHAUExg7wr9DspBNwPWcVa ub9Z7T5z6JdCTm/RDXgpr5ySUAfzoyGk4ChFDBDEqjVd2HyZo1QMsTyoyo9/KkSBcx ynYdlMASdOihh+TUZUboTDACa2a7bCcBF2mguwEHbBPUdel8lSZZGjX01gGijuou7V k2GOSf1uGr63G5C1D4R52kbFCUff5zSZakILxbJagryQ0ugtVvDnn7ql6U017Sq8n1 nWm00k4ff/qjg==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/K3ufOsvgy_D7IoE7O97TF-TIFCI
Subject: Re: [MMUSIC] BUNDLE Q14: Mandate usage of RTP/RTCP mux within a BUNDLE group? [was: On the sparsity of RTP Payload types]
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: Thu, 20 Mar 2014 14:56:21 -0000

One comment inline

On 3/20/14 5:50 AM, Magnus Westerlund wrote:
> On 2014-03-16 15:16, Christer Holmberg wrote:
>>
>> Hi,
>>
>> Do other people have opinions on this?
>
> I have considered this proposal in a wider context and have the
> following reflections and also an additional motivation why I personally
> consider it important that a bundle-group shall be possible to be
> established with RTCP on either the same transport flow (5-tuple) as
> RTP, i.e. using a=rtcp-mux, or using separate transport flows (one for
> RTP, one for RTCP), i.e. no a=rtcp-mux.
>
> First of all BUNDLE is a general signaling mechanism it is possible to
> apply to any user of SDP offer/answer. WebRTC is the first and the one
> which pushed it into existence, but I am pretty certain it will not be
> the only user of  the mechanism.
>
> What Justin is pushing for, prevents one to have multiple media streams
> of different or the same type, i.e. what ever you put in the same bundle
> group, to have RTCP separated on transport level from RTP.
>
> In most cases this doesn't matter, but where it can matter is when using
> QoS, for example in cellular environments. Being forced to put RTCP on
> the same QoS treatment as the media will either reduce the achievable
> quality or increase the cost. Being able to spend these commonly 5% of
> bandwidth on improving media or avoiding higher cost is significant in
> such an environment.
>
> Thus, I think everyone needs to thing twice about this. Shall really
> relatively minor implementation concerns and focus on general Internet
> only deployments win out over BUNDLEs applicability and the possibility
> to get the most out of any QoS when available.
>
> To be clear, I am fine with having usage of a=rtcp-mux as default
> behavior, but from my perspective we need to be able to actually
> negotiate if one turns on RTP/RTCP multiplexing using the a=rtcp-mux
> attribute when doing an round of offer/answer based signaling.

IMO, if rtcp-mux is to be an option in bundles, then I am *not* fine 
with having it as default behavior. Doing so would mean the default is 
one way with bundle, and a different way without bundle. Such an 
inconsistency is crazy - it will lead to a lot of confusion.

Especially consider what happens if offer is constructed with bundle and 
says nothing about rtcp-mux, but the answerer doesn't support bundle. 
Are you doing rtcp-mux or not?

	Thanks,
	Paul


> cheers
>
> Magnus Westerlund
>
> ----------------------------------------------------------------------
> Services, Media and Network features, Ericsson Research EAB/TXM
> ----------------------------------------------------------------------
> Ericsson AB                 | Phone  +46 10 7148287
> Färögatan 6                 | Mobile +46 73 0949079
> SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>


From nobody Thu Mar 20 08:51:35 2014
Return-Path: <magnus.westerlund@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 C1D551A075F for <mmusic@ietfa.amsl.com>; Thu, 20 Mar 2014 08:51:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.851
X-Spam-Level: 
X-Spam-Status: No, score=-3.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 NDy-PfKW77mX for <mmusic@ietfa.amsl.com>; Thu, 20 Mar 2014 08:51:28 -0700 (PDT)
Received: from mailgw1.ericsson.se (mailgw1.ericsson.se [193.180.251.45]) by ietfa.amsl.com (Postfix) with ESMTP id B6FED1A0743 for <mmusic@ietf.org>; Thu, 20 Mar 2014 08:51:27 -0700 (PDT)
X-AuditID: c1b4fb2d-b7f5d8e000002a7b-70-532b0e7535d2
Received: from ESESSHC013.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw1.ericsson.se (Symantec Mail Security) with SMTP id F9.9F.10875.57E0B235; Thu, 20 Mar 2014 16:51:18 +0100 (CET)
Received: from [127.0.0.1] (153.88.183.153) by smtp.internal.ericsson.com (153.88.183.59) with Microsoft SMTP Server id 14.2.347.0; Thu, 20 Mar 2014 16:51:17 +0100
Message-ID: <532B0E75.6050305@ericsson.com>
Date: Thu, 20 Mar 2014 16:51:17 +0100
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, <mmusic@ietf.org>
References: <7594FB04B1934943A5C02806D1A2204B1D23329D@ESESSMB209.ericsson.se> <532AB9C9.1020602@ericsson.com> <532B018A.4080504@alum.mit.edu>
In-Reply-To: <532B018A.4080504@alum.mit.edu>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpmluLIzCtJLcpLzFFi42KZGfG3RreMTzvYoLeD0WLq8scsFis2HGB1 YPL4+/4Dk8eSJT+ZApiiuGxSUnMyy1KL9O0SuDK+POUv+Cdesf7caqYGxk3CXYycHBICJhIz VvxhhLDFJC7cW88GYgsJHGKU+Nfi28XIBWQvZ5T4fn4CexcjBwevgLbEsY18IDUsAqoST/99 Zgex2QQsJG7+aATrFRUIllg6ZzELiM0rIChxcuYTMFtEwFri5YpTLCAzhQVaGCUmnz3LDrGg l1Fi+YzjYJM4BXQknnz6B7ZMQkBcoqcxCCTMLKAnMeVqCyOELS/RvHU2M8Sh2hINTR2sExgF ZyHZNwtJyywkLQsYmVcxsucmZuaklxtuYgQG5MEtv3V3MJ46J3KIUZqDRUmc98Nb5yAhgfTE ktTs1NSC1KL4otKc1OJDjEwcnFINjIFz1I+y6TnofX6/30EiKVasoG39mRzdG5enVojFt1z4 W8p8Ml5wQu1Z3rDWI0HrmJekBh850ZvZpLL8h9hE1ubVC+T669YfaqmZtdqe6fiPkIKfgdNl Tu1q09kXYXGI+eTLA3Gal24dLdm0oeLlhoN75Y/6z2i9Nv2rl6FntmR7W4Ez0wn/V0osxRmJ hlrMRcWJAHX6KF8WAgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/5pPRaaaelaD7Hp199QUZEesL82I
Subject: Re: [MMUSIC] BUNDLE Q14: Mandate usage of RTP/RTCP mux within a BUNDLE group? [was: On the sparsity of RTP Payload types]
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: Thu, 20 Mar 2014 15:51:30 -0000

On 2014-03-20 15:56, Paul Kyzivat wrote:
> One comment inline
> 
> On 3/20/14 5:50 AM, Magnus Westerlund wrote:
>> On 2014-03-16 15:16, Christer Holmberg wrote:

>> To be clear, I am fine with having usage of a=rtcp-mux as default
>> behavior, but from my perspective we need to be able to actually
>> negotiate if one turns on RTP/RTCP multiplexing using the a=rtcp-mux
>> attribute when doing an round of offer/answer based signaling.
> 
> IMO, if rtcp-mux is to be an option in bundles, then I am *not* fine
> with having it as default behavior. Doing so would mean the default is
> one way with bundle, and a different way without bundle. Such an
> inconsistency is crazy - it will lead to a lot of confusion.
> 

What I meant with default, being the recommended starting behavior if
you haven't a reason to do otherwise. What the offering parties really
like to do is explicitly signalled, always! If one wants to use
a=rtcp-mux one MUST include it, if not don't include it.

> Especially consider what happens if offer is constructed with bundle and
> says nothing about rtcp-mux, but the answerer doesn't support bundle.
> Are you doing rtcp-mux or not?

Well, you do that initial offer with a=rtcp-mux. If the answer removes
both BUNDLE and the a=rtcp-mux, then you don't use either. Then you have
to use the separate transports that you are required to include for this
reason when offering BUNDLE initially. For subsequent offers, the offer
knowing the receiver was known to support BUNDLE one can use that
assumption. Thus, one can avoid the inclusion of RTCP transports if one
offers a=rtcp-mux. That is the reason I find it good to mandate support
of a=rtcp-mux. However, as I wrote in the previous message, there are
reasons why an Offerer should be able to allocate transports and then
remove the a=rtcp-mux from its new Offer.


I am worried that people appear think that just because you offer
BUNDLE, you can have a lot of values set by not explicitly indicating
them in the SDP. That, is from my perspective NUTS. We have to be
explicit about the usage and configuration of other mechanisms. In some
cases BUNDLE leads to restrictions, for example across the m= lines in
the BUNDLE group. Attributes that you would include on a single m=
section when not using BUNDLE do have to be included in all the  m=
sections when using it. When doing BUNDLE the common start assumptions
should be that normal non-BUNDLE behavior applies. There might be
exceptions and that is what the SDP mux drafts tries to make clear.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Färögatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From nobody Thu Mar 20 08:56:02 2014
Return-Path: <pkyzivat@alum.mit.edu>
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 B32EA1A08C9 for <mmusic@ietfa.amsl.com>; Thu, 20 Mar 2014 08:56:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] 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 M_R8Vb3F7iey for <mmusic@ietfa.amsl.com>; Thu, 20 Mar 2014 08:55:59 -0700 (PDT)
Received: from qmta07.westchester.pa.mail.comcast.net (qmta07.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:64]) by ietfa.amsl.com (Postfix) with ESMTP id F3D9E1A08C8 for <mmusic@ietf.org>; Thu, 20 Mar 2014 08:55:38 -0700 (PDT)
Received: from omta23.westchester.pa.mail.comcast.net ([76.96.62.74]) by qmta07.westchester.pa.mail.comcast.net with comcast id fnNx1n0041c6gX857rvVrH; Thu, 20 Mar 2014 15:55:29 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta23.westchester.pa.mail.comcast.net with comcast id frvV1n00f3ZTu2S3jrvVfm; Thu, 20 Mar 2014 15:55:29 +0000
Message-ID: <532B0F71.5070106@alum.mit.edu>
Date: Thu, 20 Mar 2014 11:55:29 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: mmusic@ietf.org
References: <021001cf39f3$04e8de40$0eba9ac0$@gmail.com>, <7594FB04B1934943A5C02806D1A2204B1D1D8C3D@ESESSMB209.ericsson.se> <7594FB04B1934943A5C02806D1A2204B1D2009EF@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D2009EF@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1395330929; bh=LOwdB5gG84ZoXmJ3X2jm2HEZg1u6tl06WxAYOC62ycI=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=ldmNgHp1zpTuZ4FPFSxlaiLCg7O67nv7N0a+bLasSAwVu8sDPERpOlD0cLQJxv7vY rLOipyAphIRz6yyzOmjMLuZqaPAzdY6V2GeiTtDh8OXomVeAFLh29ycyqokE7yIFHu hznV7FpWxnBStk+VzFZT0HJ3KptERNUG9ubob7UTThdaLCwzsj8RlJTJN1Z58hMZwv f3iIul/zwxvcPKppR+wxVsq+Q30ijD8NmA6g3lVhCRMqiL9tRYjuYIO0kLw+6rtOii uMJ733VI4U29dlEBebiBxLFy0xgOf8b2k2r9lGbY4WDtHJxlmeXnMBNlGht/N79DkN VwxNB061e6svg==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/ZBgzpMiYS1Ph8xRO_3XW5WdGq0M
Subject: Re: [MMUSIC] Bundle: Q13 receiver-Id
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: Thu, 20 Mar 2014 15:56:01 -0000

On 3/11/14 3:56 AM, Christer Holmberg wrote:
>
> Hi,
>
> If people are ok with using the mechanism in Roni's draft, please
> indicate so.

Yes, I'm in favor of this.
Based on the comments, there is work to do on that draft, but it in on 
track to provide the right semantics.

	Thanks,
	Paul

> Please also indicate if you are NOT ok to use it, or you think there is
> another mechanism we should at least verify.
>
> Please also indicate if you don't care what mechanism we use - just to
> make sure we get community input :)
>
> Note that if the "receiver-id" will require a new draft, the publication
> of BUNDLE will be dependent of that draft, so I think we should make a
> decision which way to go asap.
>
> Regards,
>
> Christer
>
>
> ------------------------------------------------------------------------
> *From:* mmusic [mmusic-bounces@ietf.org] on behalf of Christer Holmberg
> [christer.holmberg@ericsson.com]
> *Sent:* Friday, 07 March 2014 3:33 PM
> *To:* Roni Even; 'mmusic'
> *Subject:* Re: [MMUSIC] Bundle: Q13 receiver-Id
>
> Thank you for the input, Roni!
>
> I assume that, for the purpose of associating media with an m- line, an
> entity would not need to support the OTHER attributes in the draft, right?
>
> Regards,
>
> Christer
>
> Sent from Windows Mail
>
> *From:* Roni Even <mailto:ron.even.tlv@gmail.com>
> *Sent:* â€ŽFridayâ€Ž, â€Ž7â€Ž â€ŽMarchâ€Ž â€Ž2014 â€Ž12â€Ž:â€Ž50
> *To:* 'mmusic' <mailto:mmusic@ietf.org>
>
> Hi,
>
> In draft-even-mmusic-application-token-02
> <http://tools.ietf.org/html/draft-even-mmusic-application-token-02>
> there is a recv-appId token that can be used as the receiver-Id. Based
> on the discussion in the meeting it seems that the recv-appId  usage
>   will be needed for the case when the offerer receives media before the
> SDP answer and can use the recv-appId to identify the correlation to an
> m-line / RTP stream   in the SDP.  This will also works for the same PT
> number.
>
> Roni
>
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>


From nobody Thu Mar 20 09:50:47 2014
Return-Path: <pkyzivat@alum.mit.edu>
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 F33A51A07C5 for <mmusic@ietfa.amsl.com>; Thu, 20 Mar 2014 09:50:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] 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 rB5Js6WZFUDF for <mmusic@ietfa.amsl.com>; Thu, 20 Mar 2014 09:50:43 -0700 (PDT)
Received: from qmta08.westchester.pa.mail.comcast.net (qmta08.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:80]) by ietfa.amsl.com (Postfix) with ESMTP id ADD3F1A08DC for <mmusic@ietf.org>; Thu, 20 Mar 2014 09:50:42 -0700 (PDT)
Received: from omta24.westchester.pa.mail.comcast.net ([76.96.62.76]) by qmta08.westchester.pa.mail.comcast.net with comcast id foKT1n0041ei1Bg58sqZHj; Thu, 20 Mar 2014 16:50:33 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta24.westchester.pa.mail.comcast.net with comcast id fsqZ1n00q3ZTu2S3ksqZdP; Thu, 20 Mar 2014 16:50:33 +0000
Message-ID: <532B1C59.5000100@alum.mit.edu>
Date: Thu, 20 Mar 2014 12:50:33 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Magnus Westerlund <magnus.westerlund@ericsson.com>, mmusic@ietf.org
References: <7594FB04B1934943A5C02806D1A2204B1D23329D@ESESSMB209.ericsson.se> <532AB9C9.1020602@ericsson.com> <532B018A.4080504@alum.mit.edu> <532B0E75.6050305@ericsson.com>
In-Reply-To: <532B0E75.6050305@ericsson.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1395334233; bh=NYPDkkoSAS99WaEg1KA7rdc3/hAToaOSOJYTyhgk0Gk=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=DHh5PDF63RFLtWcEqhxhhuJ+IXVZYOvRFCFqIu5CULKRCddS3gFcdTY+GHMwLvbNx asSnYzWhKiffjpGaaaYPVacfDd1eqne4xy488zGgAwFYuSOC565rLC/YkIT9uKGKf6 po0rxoqXWs0zY7dhJS5VdljIfkeCFw4y1G+Ze31FzYtnXLs/M6Cs2A7lKo8QGdp/Br 32NqfpesBd8wJ2y6vObwNX1Mkk1vwnbU8COmZDVHI3W0y5TcRcPQzvwflQdSARKCfp a5iQsWN5yuVStErvl1+gu0yw0QtF46wrcATWmND04RUE6eMm6eXXmYi6Wk/YxFAAeE fWCRkFNiT4q5w==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/BarKs_WAe0ay0av_3QqCrFCbPOw
Subject: Re: [MMUSIC] BUNDLE Q14: Mandate usage of RTP/RTCP mux within a BUNDLE group? [was: On the sparsity of RTP Payload types]
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: Thu, 20 Mar 2014 16:50:45 -0000

OK. We are in agreement. I misunderstood what you meant by "default". I 
think you meant "recommended initial setting".

	Thanks,
	Paul

On 3/20/14 11:51 AM, Magnus Westerlund wrote:
> On 2014-03-20 15:56, Paul Kyzivat wrote:
>> One comment inline
>>
>> On 3/20/14 5:50 AM, Magnus Westerlund wrote:
>>> On 2014-03-16 15:16, Christer Holmberg wrote:
>
>>> To be clear, I am fine with having usage of a=rtcp-mux as default
>>> behavior, but from my perspective we need to be able to actually
>>> negotiate if one turns on RTP/RTCP multiplexing using the a=rtcp-mux
>>> attribute when doing an round of offer/answer based signaling.
>>
>> IMO, if rtcp-mux is to be an option in bundles, then I am *not* fine
>> with having it as default behavior. Doing so would mean the default is
>> one way with bundle, and a different way without bundle. Such an
>> inconsistency is crazy - it will lead to a lot of confusion.
>>
>
> What I meant with default, being the recommended starting behavior if
> you haven't a reason to do otherwise. What the offering parties really
> like to do is explicitly signalled, always! If one wants to use
> a=rtcp-mux one MUST include it, if not don't include it.
>
>> Especially consider what happens if offer is constructed with bundle and
>> says nothing about rtcp-mux, but the answerer doesn't support bundle.
>> Are you doing rtcp-mux or not?
>
> Well, you do that initial offer with a=rtcp-mux. If the answer removes
> both BUNDLE and the a=rtcp-mux, then you don't use either. Then you have
> to use the separate transports that you are required to include for this
> reason when offering BUNDLE initially. For subsequent offers, the offer
> knowing the receiver was known to support BUNDLE one can use that
> assumption. Thus, one can avoid the inclusion of RTCP transports if one
> offers a=rtcp-mux. That is the reason I find it good to mandate support
> of a=rtcp-mux. However, as I wrote in the previous message, there are
> reasons why an Offerer should be able to allocate transports and then
> remove the a=rtcp-mux from its new Offer.
>
>
> I am worried that people appear think that just because you offer
> BUNDLE, you can have a lot of values set by not explicitly indicating
> them in the SDP. That, is from my perspective NUTS. We have to be
> explicit about the usage and configuration of other mechanisms. In some
> cases BUNDLE leads to restrictions, for example across the m= lines in
> the BUNDLE group. Attributes that you would include on a single m=
> section when not using BUNDLE do have to be included in all the  m=
> sections when using it. When doing BUNDLE the common start assumptions
> should be that normal non-BUNDLE behavior applies. There might be
> exceptions and that is what the SDP mux drafts tries to make clear.
>
> Cheers
>
> Magnus Westerlund
>
> ----------------------------------------------------------------------
> Services, Media and Network features, Ericsson Research EAB/TXM
> ----------------------------------------------------------------------
> Ericsson AB                 | Phone  +46 10 7148287
> Färögatan 6                 | Mobile +46 73 0949079
> SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
>
>


From nobody Thu Mar 20 10:48:42 2014
Return-Path: <rjsparks@nostrum.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 046681A0700; Thu, 20 Mar 2014 10:48:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.115
X-Spam-Level: 
X-Spam-Status: No, score=-2.115 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, IP_NOT_FRIENDLY=0.334, RP_MATCHES_RCVD=-0.547, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 vYuqohEwKX9p; Thu, 20 Mar 2014 10:48:30 -0700 (PDT)
Received: from nostrum.com (raven.nostrum.com [69.55.229.100]) by ietfa.amsl.com (Postfix) with ESMTP id 5A52A1A0790; Thu, 20 Mar 2014 10:48:30 -0700 (PDT)
Received: from unnumerable.local (pool-173-71-10-88.dllstx.fios.verizon.net [173.71.10.88]) (authenticated bits=0) by nostrum.com (8.14.8/8.14.7) with ESMTP id s2KHl5Di080514 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=OK); Thu, 20 Mar 2014 12:47:06 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host pool-173-71-10-88.dllstx.fios.verizon.net [173.71.10.88] claimed to be unnumerable.local
Message-ID: <532B299C.3070909@nostrum.com>
Date: Thu, 20 Mar 2014 12:47:08 -0500
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: dispatch@ietf.org, mmusic@ietf.org, rtcweb@ietf.org, avt@ietf.org, sipcore@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/BhaBdGungY90hip_BAHzVCgWxZg
Subject: [MMUSIC] Registration for SIPit 31 is open
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: rai@ietf.org
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: Thu, 20 Mar 2014 17:48:32 -0000

(Please forgive the crosspost, and reply only to the rai list):
Please see
<http://mailarchive.ietf.org/arch/msg/rai/llvQvf7FWMRM-3ZV0R1aDE5wpRg>


From nobody Thu Mar 20 11:02:12 2014
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 415121A0429 for <mmusic@ietfa.amsl.com>; Thu, 20 Mar 2014 11:02:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham
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 wv_kW3ofA_9k for <mmusic@ietfa.amsl.com>; Thu, 20 Mar 2014 11:02:08 -0700 (PDT)
Received: from sesbmg20.ericsson.net (sesbmg20.ericsson.net [193.180.251.56]) by ietfa.amsl.com (Postfix) with ESMTP id A12601A0406 for <mmusic@ietf.org>; Thu, 20 Mar 2014 11:02:07 -0700 (PDT)
X-AuditID: c1b4fb38-b7f418e000001099-f8-532b2d15f750
Received: from ESESSHC018.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg20.ericsson.net (Symantec Mail Security) with SMTP id CB.F7.04249.51D2B235; Thu, 20 Mar 2014 19:01:58 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.213]) by ESESSHC018.ericsson.se ([153.88.183.72]) with mapi id 14.02.0387.000; Thu, 20 Mar 2014 19:01:57 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>, Paul Kyzivat <pkyzivat@alum.mit.edu>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] BUNDLE Q14: Mandate usage of RTP/RTCP mux within a BUNDLE group? [was: On the sparsity of RTP Payload types]
Thread-Index: AQHPQSJW5SOYVCaDbkiksfP7ze4/V5rpsH2AgABViQCAAA9ngIAANLch
Date: Thu, 20 Mar 2014 18:01:57 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D256324@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D23329D@ESESSMB209.ericsson.se> <532AB9C9.1020602@ericsson.com> <532B018A.4080504@alum.mit.edu>,<532B0E75.6050305@ericsson.com>
In-Reply-To: <532B0E75.6050305@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.16]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrMLMWRmVeSWpSXmKPExsUyM+Jvja6YrnawQd9DVoupyx+zWKzYcIDV gcnj7/sPTB5LlvxkCmCK4rJJSc3JLEst0rdL4MqYuqyo4J5cxcRHt9kaGHskuxg5OSQETCRe LPrKCmGLSVy4t56ti5GLQ0jgCKPE5JvLmCCcJYwSs9s62bsYOTjYBCwkuv9pg8RFBJoZJc79 us4C4ggLtDBKPN++jQUi08oosfjqdGaQuSICbhLrL7YwgtgsAqoSH95vBtvHK+ArcWnOCTYQ W0hgI6PEocXxIDangI7E5nWbwOKMQDd9P7WGCcRmFhCXuPVkPhPErQISS/acZ4awRSVePv4H 9YOixM6z7cwQ9XoSN6ZOYYOwtSWWLXzNDLFXUOLkzCcsExhFZyEZOwtJyywkLbOQtCxgZFnF yFGcWpyUm25ksIkRGBEHt/y22MF4+a/NIUZpDhYlcd6Pb52DhATSE0tSs1NTC1KL4otKc1KL DzEycXBKNTCWT6mPeRHAbnMp+8Gc/C23Y2WEZB7tUTgQ8XjZ8rM108XlT3pX7arY9lJg3VQ/ TyHteU9t7s9IdVfraT7jvVYze4HglwOP9nyJz2XWcdY5JPxzQ+vPXal/tV9n2v0JObN09xxO ycjM7fuYEr9teVlRYa61cr6S+rvSPS1qj92f3FxRoLf97CIxJZbijERDLeai4kQAhN9s71YC AAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/CA4pGFh0Te2pKpzRPCzDgDvburc
Subject: Re: [MMUSIC] BUNDLE Q14: Mandate usage of RTP/RTCP mux within a BUNDLE group? [was: On the sparsity of RTP Payload types]
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: Thu, 20 Mar 2014 18:02:10 -0000

Hi,

Please note that NOBODY has suggested that we would have RTP/RTCP mux WITHO=
UT explicit indication using a=3Drtcp-mux.=20

The question is whether we shall mandate the usage of RTP/RTCP mux (and, he=
nce a=3Drtcp-mux) in BUNDLE, or whether we shall allow BUNDLE groups with s=
eparate RTP- and RTCP ports.

Regards,

Christer


________________________________________
From: mmusic [mmusic-bounces@ietf.org] on behalf of Magnus Westerlund [magn=
us.westerlund@ericsson.com]
Sent: Thursday, 20 March 2014 5:51 PM
To: Paul Kyzivat; mmusic@ietf.org
Subject: Re: [MMUSIC] BUNDLE Q14: Mandate usage of RTP/RTCP mux within a BU=
NDLE group? [was: On the sparsity of RTP Payload types]

On 2014-03-20 15:56, Paul Kyzivat wrote:
> One comment inline
>
> On 3/20/14 5:50 AM, Magnus Westerlund wrote:
>> On 2014-03-16 15:16, Christer Holmberg wrote:

>> To be clear, I am fine with having usage of a=3Drtcp-mux as default
>> behavior, but from my perspective we need to be able to actually
>> negotiate if one turns on RTP/RTCP multiplexing using the a=3Drtcp-mux
>> attribute when doing an round of offer/answer based signaling.
>
> IMO, if rtcp-mux is to be an option in bundles, then I am *not* fine
> with having it as default behavior. Doing so would mean the default is
> one way with bundle, and a different way without bundle. Such an
> inconsistency is crazy - it will lead to a lot of confusion.
>

What I meant with default, being the recommended starting behavior if
you haven't a reason to do otherwise. What the offering parties really
like to do is explicitly signalled, always! If one wants to use
a=3Drtcp-mux one MUST include it, if not don't include it.

> Especially consider what happens if offer is constructed with bundle and
> says nothing about rtcp-mux, but the answerer doesn't support bundle.
> Are you doing rtcp-mux or not?

Well, you do that initial offer with a=3Drtcp-mux. If the answer removes
both BUNDLE and the a=3Drtcp-mux, then you don't use either. Then you have
to use the separate transports that you are required to include for this
reason when offering BUNDLE initially. For subsequent offers, the offer
knowing the receiver was known to support BUNDLE one can use that
assumption. Thus, one can avoid the inclusion of RTCP transports if one
offers a=3Drtcp-mux. That is the reason I find it good to mandate support
of a=3Drtcp-mux. However, as I wrote in the previous message, there are
reasons why an Offerer should be able to allocate transports and then
remove the a=3Drtcp-mux from its new Offer.


I am worried that people appear think that just because you offer
BUNDLE, you can have a lot of values set by not explicitly indicating
them in the SDP. That, is from my perspective NUTS. We have to be
explicit about the usage and configuration of other mechanisms. In some
cases BUNDLE leads to restrictions, for example across the m=3D lines in
the BUNDLE group. Attributes that you would include on a single m=3D
section when not using BUNDLE do have to be included in all the  m=3D
sections when using it. When doing BUNDLE the common start assumptions
should be that normal non-BUNDLE behavior applies. There might be
exceptions and that is what the SDP mux drafts tries to make clear.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Services, Media and Network features, Ericsson Research EAB/TXM
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
F=E4r=F6gatan 6                 | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------

_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www.ietf.org/mailman/listinfo/mmusic


From nobody Sat Mar 22 18:39:53 2014
Return-Path: <fluffy@iii.ca>
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 BE4DF1A6F0B for <mmusic@ietfa.amsl.com>; Sat, 22 Mar 2014 18:39:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.642
X-Spam-Level: *
X-Spam-Status: No, score=1.642 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DATE_IN_PAST_06_12=1.543, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_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 JFEEWX1qoK18 for <mmusic@ietfa.amsl.com>; Sat, 22 Mar 2014 18:39:45 -0700 (PDT)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id E3AE81A6F05 for <mmusic@ietf.org>; Sat, 22 Mar 2014 18:39:44 -0700 (PDT)
Received: from [10.21.74.45] (unknown [128.107.239.233]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 60A2722E1FA; Sat, 22 Mar 2014 21:39:38 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <CAPvvaaKM7S0jRA1dQgCZLGfg4ryNRriMfvSM3V6sD+=3TX4Jzw@mail.gmail.com>
Date: Sat, 22 Mar 2014 12:59:44 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <735A4CD3-A4CB-43F0-B823-516E38664620@iii.ca>
References: <CF489B5D.25EB0%alissa@cooperw.in> <CAPvvaaKM7S0jRA1dQgCZLGfg4ryNRriMfvSM3V6sD+=3TX4Jzw@mail.gmail.com>
To: Emil Ivov <emcho@jitsi.org>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/9AocYpBDeDVK1895O8wEKFMQk40
Cc: draft-ietf-mmusic-latching@tools.ietf.org, mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] AD evaluation: draft-ietf-mmusic-latching-04
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: Sun, 23 Mar 2014 01:39:46 -0000

On Mar 19, 2014, at 2:51 AM, Emil Ivov <emcho@jitsi.org> wrote:

> Also it is worth reminding that the above threats apply mostly to
> generic Internet deployments. Many people using latching today, do so
> in controlled environments, where that kind of hijacking could not
> occur.

Could you provide a bit more about where you see this being used? Most =
the latching I have seen is in exactly the places where network is not =
at all controlled. In a managed network you can vernally avoid the need =
for latching.=20


From nobody Sun Mar 23 04:00:38 2014
Return-Path: <partha@parthasarathi.co.in>
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 7A2611A09B3 for <mmusic@ietfa.amsl.com>; Sun, 23 Mar 2014 04:00:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.699
X-Spam-Level: 
X-Spam-Status: No, score=0.699 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham
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 US522roVgWW5 for <mmusic@ietfa.amsl.com>; Sun, 23 Mar 2014 04:00:21 -0700 (PDT)
Received: from outbound.mailhostbox.com (outbound.mailhostbox.com [162.222.225.25]) by ietfa.amsl.com (Postfix) with ESMTP id 355571A0997 for <mmusic@ietf.org>; Sun, 23 Mar 2014 04:00:03 -0700 (PDT)
Received: from userPC (unknown [122.167.205.77]) (Authenticated sender: partha@parthasarathi.co.in) by outbound.mailhostbox.com (Postfix) with ESMTPA id 48562868A8D; Sun, 23 Mar 2014 10:59:57 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=parthasarathi.co.in; s=20120823; t=1395572403; bh=bbnOJhE5bdoGL4twdmpgLzNbiGNT8vIGmuz4li/Aes8=; h=From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type:Content-Transfer-Encoding; b=acQeJc58sZA8LC9Cx4N1NWLTbF7YTTkfW/h3whxW4zWa4dNZxZB45KH6j+Sp5Zq+o V7vCw/oYPhbJ1C+QEBwfmSHS6aTHmjtLrursk0pNiG79geIUmErI190PZvAcv1X3sp jUd7MY59NSNiGxoEzlCRd5bAgVgkH1c1B2ox5G+A=
From: "Parthasarathi R" <partha@parthasarathi.co.in>
To: "'Emil Ivov'" <emcho@jitsi.org>, "'Enrico Marocco \(TiLab\)'" <enrico.marocco@telecomitalia.it>, "'Christer Holmberg'" <christer.holmberg@ericsson.com>
References: <01e601cf423c$57255890$057009b0$@co.in>
In-Reply-To: <01e601cf423c$57255890$057009b0$@co.in>
Date: Sun, 23 Mar 2014 16:29:53 +0530
Message-ID: <00c901cf4687$0a48dbb0$1eda9310$@co.in>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac9CPFJy24/vzsmBSZKQcuFN40F13QESLNjg
Content-Language: en-us
X-CTCH-RefID: str=0001.0A020204.532EBEB2.00A4, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0
X-CTCH-VOD: Unknown
X-CTCH-Spam: Unknown
X-CTCH-Score: 0.000
X-CTCH-Rules: 
X-CTCH-Flags: 0
X-CTCH-ScoreCust: 0.000
X-CTCH-SenderID: partha@parthasarathi.co.in
X-CTCH-SenderID-TotalMessages: 1
X-CTCH-SenderID-TotalSpam: 0
X-CTCH-SenderID-TotalSuspected: 0
X-CTCH-SenderID-TotalBulk: 0
X-CTCH-SenderID-TotalConfirmed: 0
X-CTCH-SenderID-TotalRecipients: 0
X-CTCH-SenderID-TotalVirus: 0
X-CTCH-SenderID-BlueWhiteFlag: 0
X-Scanned-By: MIMEDefang 2.72 on 172.18.214.93
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/CfkDlzSz-Mi30g_MBNRbGSEsls0
Cc: mmusic@ietf.org
Subject: Re: [MMUSIC] Comment on SIP Trickle ICE based on INFO draft
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: Sun, 23 Mar 2014 11:00:35 -0000

Hi all,

The below mentioned UPDATE overlap with INFO usecase and INFO forking
scenario has to be clarified before adopting this draft as WG item as I'm
not seeing any solution with INFO based mechanism.

Thanks
Partha

> -----Original Message-----
> From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of
> Parthasarathi R
> Sent: Tuesday, March 18, 2014 5:25 AM
> To: 'Emil Ivov'; 'Enrico Marocco (TiLab)'; 'Christer Holmberg'
> Cc: mmusic@ietf.org
> Subject: [MMUSIC] Comment on SIP Trickle based on INFO draft
> 
> Hi all,
> 
> SIP Trickle INFO is projected as the back channel for collecting the
> candidates in IETF-89 MMUSIC meeting. Unfortunately, it impacts
> Offer/answer
> (RFC 3264) in case one another offer/answer started before SIP trickle
> INFO
> is completed. The race condition between second offer/answer and
> earlier SIP
> trickle INFO is not stated in the draft-ivov-mmusic-trickle-ice-sip. I
> have
> explained those issues in
> http://www.ietf.org/mail-archive/web/mmusic/current/msg12666.html and
> no
> reply from you folks. This race condition is very much possible during
> early
> dialog scenarios with UPDATE.
> 
> Could you please explain how SIP trickle ICE using INFO works for
> 
> 1) UPDATE from remote before Trickle ICE is completed
> 
>     a) INVITE from local
>     b) 183 session progress from remote
>     c) PRACK from local
>     d) INFO from local (relay candidates)
>     e) UPDATE from remote
> 
> Here, the remote has to consider whether INFO belongs to UPDATE or
> INVITE as
> it is possible for INFO to reach before 200 OK for UPDATE as well in
> the
> same sequence. Also, RFC 2976 clarifies that
> 
> " - The extensions that use the INFO message MUST NOT rely on the
>      INFO message to do anything that effects the SIP call state or the
>      state of related sessions."
> 
> But SIP Trickle ICE state is depend upon the "state of related
> sessions" as
> UPDATE would have change the state in the remote.
> 
> 2) Trickle ICE INFO with serial forking
> 
>   a) INVITE from local
>   b) INVITE is forked by proxy to first remote destination
>   c) 100 trying is reaching local
>   d) INFO with Trickle ICE from local
>   e) INFO is forward by proxy to first remote destination
>   f) INVITE is forked by proxy to second remote destination
>   g) Whether INFO has to be forked?
> 
> It is not mentioned in the draft whether INFO has to be forked to the
> second
> remote destination as well. Could you please explain the expect
> behavior for
> this scenario.
> 
> Thanks
> Partha
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic


From nobody Sun Mar 23 04:54:34 2014
Return-Path: <emcho@sip-communicator.org>
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 1A7831A6F6A for <mmusic@ietfa.amsl.com>; Sun, 23 Mar 2014 04:54:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 M65K8k_yDguQ for <mmusic@ietfa.amsl.com>; Sun, 23 Mar 2014 04:54:29 -0700 (PDT)
Received: from mail-vc0-f175.google.com (mail-vc0-f175.google.com [209.85.220.175]) by ietfa.amsl.com (Postfix) with ESMTP id C56071A06CD for <mmusic@ietf.org>; Sun, 23 Mar 2014 04:54:29 -0700 (PDT)
Received: by mail-vc0-f175.google.com with SMTP id lh14so4501513vcb.6 for <mmusic@ietf.org>; Sun, 23 Mar 2014 04:54:29 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=l8khObi5zYsKSVj4XbkuQ+vazjiC1yhRiQKn0BRXkMw=; b=aov94lc1sfbibKVYc4zUEbCW+v7nvrGLxd7xuNfr/zieehZyVy5+OhGJBlTXXHK5HD BFUGe5+rDQ8QWolOK7p3BR9r/SG9wEqYTFBXMbpbEh5KSFueIWAx+NifMxh0wiy67br3 /kbGNX0KA6sT1woWSNeLw7hzq22bW0wqlV4pGLclDs9VFksDLOXe1lWPwqpWokNSq4aW P6+XHgpbmpZ/Fc4YHEZsUPG4pOExY0APJe26cR2jkMH+jUyDnIhvbW8yo/ELN9XzShjd b20Xt4FBvdHkKmddXwWlvTud4Lbz6ZLsTzQ5cOZiOb/L8glSjOu69t5jsF9/tPyeGCSu enlg==
X-Gm-Message-State: ALoCoQmU3J96fMqoHlHOvW60BYRcBSXiIF9zs/9ThSoWNKnQRdw7GjzA4n+0ZUZQuI6DIK2XGq0g
X-Received: by 10.52.139.237 with SMTP id rb13mr59005vdb.33.1395575669093; Sun, 23 Mar 2014 04:54:29 -0700 (PDT)
Received: from mail-vc0-f169.google.com (mail-vc0-f169.google.com [209.85.220.169]) by mx.google.com with ESMTPSA id lz2sm12054015veb.10.2014.03.23.04.54.27 for <mmusic@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 23 Mar 2014 04:54:27 -0700 (PDT)
Received: by mail-vc0-f169.google.com with SMTP id ik5so4677895vcb.0 for <mmusic@ietf.org>; Sun, 23 Mar 2014 04:54:27 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.221.40.10 with SMTP id to10mr65887vcb.22.1395575667584; Sun, 23 Mar 2014 04:54:27 -0700 (PDT)
Received: by 10.220.191.130 with HTTP; Sun, 23 Mar 2014 04:54:27 -0700 (PDT)
Received: by 10.220.191.130 with HTTP; Sun, 23 Mar 2014 04:54:27 -0700 (PDT)
In-Reply-To: <00c901cf4687$0a48dbb0$1eda9310$@co.in>
References: <01e601cf423c$57255890$057009b0$@co.in> <00c901cf4687$0a48dbb0$1eda9310$@co.in>
Date: Sun, 23 Mar 2014 12:54:27 +0100
Message-ID: <CAPvvaaKW+vxhJFqUPRZ-YfPQ4dHOS-=YwZaW+=NS3DttaaXD=Q@mail.gmail.com>
From: Emil Ivov <emcho@jitsi.org>
To: Parthasarathi R <partha@parthasarathi.co.in>
Content-Type: multipart/alternative; boundary=001a11337576ec921804f544c75b
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/BP9FnfDvTmSkBPJghKXX5y7pbH8
Cc: mmusic <mmusic@ietf.org>, Christer Holmberg <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] Comment on SIP Trickle ICE based on INFO draft
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: Sun, 23 Mar 2014 11:54:32 -0000

--001a11337576ec921804f544c75b
Content-Type: text/plain; charset=ISO-8859-1

Hello,

On 23 Mar 2014 12:00 PM, "Parthasarathi R" <partha@parthasarathi.co.in>
wrote:
>
> Hi all,
>
> The below mentioned UPDATE overlap with INFO usecase and INFO forking
> scenario has to be clarified before adopting this draft as WG item as I'm
> not seeing any solution with INFO based mechanism.
>
> Thanks
> Partha
>
> > -----Original Message-----
> > From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of
> > Parthasarathi R
> > Sent: Tuesday, March 18, 2014 5:25 AM
> > To: 'Emil Ivov'; 'Enrico Marocco (TiLab)'; 'Christer Holmberg'
> > Cc: mmusic@ietf.org
> > Subject: [MMUSIC] Comment on SIP Trickle based on INFO draft
> >
> > Hi all,
> >
> > SIP Trickle INFO is projected as the back channel for collecting the
> > candidates in IETF-89 MMUSIC meeting. Unfortunately, it impacts
> > Offer/answer
> > (RFC 3264) in case one another offer/answer started before SIP trickle
> > INFO
> > is completed.

I am still not sure why you think that and exactly what you have in mind.

> > The race condition between second offer/answer and
> > earlier SIP
> > trickle INFO is not stated in the draft-ivov-mmusic-trickle-ice-sip.

No, indeed it hasn't but it has been mentioned in discussions many times: a
new offer answer would generally cause an ICE restart.

> > I
> > have
> > explained those issues in
> > http://www.ietf.org/mail-archive/web/mmusic/current/msg12666.html and
> > no
> > reply from you folks.

I am sorry, I don't understand the mail you point to above. It says it
raises issues in 3264 situations but then refers to BUNDLE and UPDATEs.

If the scenario below is the one you are worried about, then I'll answer
there.

> > This race condition is very much possible during
> > early
> > dialog scenarios with UPDATE.
> >
> > Could you please explain how SIP trickle ICE using INFO works for
> >
> > 1) UPDATE from remote before Trickle ICE is completed

This is analogous to an UPDATE that is received before regular 5245 ICE
processing has completed.

> >     a) INVITE from local
> >     b) 183 session progress from remote
> >     c) PRACK from local
> >     d) INFO from local (relay candidates)
> >     e) UPDATE from remote
> >
> > Here, the remote has to consider whether INFO belongs to UPDATE or
> > INVITE as
> > it is possible for INFO to reach before 200 OK for UPDATE as well in
> > the
> > same sequence.

And CSeq headers wouldn't help here because ....?

> > Also, RFC 2976

which FWIW is obsoleted by RFC6086

> > clarifies that
> >
> > " - The extensions that use the INFO message MUST NOT rely on the
> >      INFO message to do anything that effects the SIP call state or the
> >      state of related sessions."

And I don't believe that it does.

> > But SIP Trickle ICE state is depend upon the "state of related
> > sessions" as
> > UPDATE would have change the state in the remote.

I am not sure what you are saying or why it is a problem.

> > 2) Trickle ICE INFO with serial forking

INFO requests are sent within a dialog. They will go through the prong
associated with that dialog and would not be forked.

> >   a) INVITE from local
> >   b) INVITE is forked by proxy to first remote destination
> >   c) 100 trying is reaching local
> >   d) INFO with Trickle ICE from local

No, this should't happen. We can't send the INFO before we have a dialog.

> >   e) INFO is forward by proxy to first remote destination
> >   f) INVITE is forked by proxy to second remote destination
> >   g) Whether INFO has to be forked?

See above.

> > It is not mentioned in the draft whether INFO has to be forked to the
> > second
> > remote destination as well. Could you please explain the expect
> > behavior for
> > this scenario.

I think the above commencts should answer your questions. We will make sure
we add those as clarifications before our next submission (hopefully as a
WG document)

Emil

> > Thanks
> > Partha
> >
> > _______________________________________________
> > mmusic mailing list
> > mmusic@ietf.org
> > https://www.ietf.org/mailman/listinfo/mmusic
>

--001a11337576ec921804f544c75b
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr">Hello,</p>
<p dir=3D"ltr">On 23 Mar 2014 12:00 PM, &quot;Parthasarathi R&quot; &lt;<a =
href=3D"mailto:partha@parthasarathi.co.in">partha@parthasarathi.co.in</a>&g=
t; wrote:<br>
&gt;<br>
&gt; Hi all,<br>
&gt;<br>
&gt; The below mentioned UPDATE overlap with INFO usecase and INFO forking<=
br>
&gt; scenario has to be clarified before adopting this draft as WG item as =
I&#39;m<br>
&gt; not seeing any solution with INFO based mechanism.<br>
&gt;<br>
&gt; Thanks<br>
&gt; Partha<br>
&gt;<br>
&gt; &gt; -----Original Message-----<br>
&gt; &gt; From: mmusic [mailto:<a href=3D"mailto:mmusic-bounces@ietf.org">m=
music-bounces@ietf.org</a>] On Behalf Of<br>
&gt; &gt; Parthasarathi R<br>
&gt; &gt; Sent: Tuesday, March 18, 2014 5:25 AM<br>
&gt; &gt; To: &#39;Emil Ivov&#39;; &#39;Enrico Marocco (TiLab)&#39;; &#39;C=
hrister Holmberg&#39;<br>
&gt; &gt; Cc: <a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
&gt; &gt; Subject: [MMUSIC] Comment on SIP Trickle based on INFO draft<br>
&gt; &gt;<br>
&gt; &gt; Hi all,<br>
&gt; &gt;<br>
&gt; &gt; SIP Trickle INFO is projected as the back channel for collecting =
the<br>
&gt; &gt; candidates in IETF-89 MMUSIC meeting. Unfortunately, it impacts<b=
r>
&gt; &gt; Offer/answer<br>
&gt; &gt; (RFC 3264) in case one another offer/answer started before SIP tr=
ickle<br>
&gt; &gt; INFO<br>
&gt; &gt; is completed. </p>
<p dir=3D"ltr">I am still not sure why you think that and exactly what you =
have in mind.</p>
<p dir=3D"ltr">&gt; &gt; The race condition between second offer/answer and=
<br>
&gt; &gt; earlier SIP<br>
&gt; &gt; trickle INFO is not stated in the draft-ivov-mmusic-trickle-ice-s=
ip.</p>
<p dir=3D"ltr">No, indeed it hasn&#39;t but it has been mentioned in discus=
sions many times: a new offer answer would generally cause an ICE restart.<=
/p>
<p dir=3D"ltr">&gt; &gt; I<br>
&gt; &gt; have<br>
&gt; &gt; explained those issues in<br>
&gt; &gt; <a href=3D"http://www.ietf.org/mail-archive/web/mmusic/current/ms=
g12666.html">http://www.ietf.org/mail-archive/web/mmusic/current/msg12666.h=
tml</a> and<br>
&gt; &gt; no<br>
&gt; &gt; reply from you folks.</p>
<p dir=3D"ltr">I am sorry, I don&#39;t understand the mail you point to abo=
ve. It says it raises issues in 3264 situations but then refers to BUNDLE a=
nd UPDATEs. </p>
<p dir=3D"ltr">If the scenario below is the one you are worried about, then=
 I&#39;ll answer there.</p>
<p dir=3D"ltr">&gt; &gt; This race condition is very much possible during<b=
r>
&gt; &gt; early<br>
&gt; &gt; dialog scenarios with UPDATE.<br>
&gt; &gt;<br>
&gt; &gt; Could you please explain how SIP trickle ICE using INFO works for=
<br>
&gt; &gt;<br>
&gt; &gt; 1) UPDATE from remote before Trickle ICE is completed</p>
<p dir=3D"ltr">This is analogous to an UPDATE that is received before regul=
ar 5245 ICE processing has completed.</p>
<p dir=3D"ltr">&gt; &gt; =A0 =A0 a) INVITE from local<br>
&gt; &gt; =A0 =A0 b) 183 session progress from remote<br>
&gt; &gt; =A0 =A0 c) PRACK from local<br>
&gt; &gt; =A0 =A0 d) INFO from local (relay candidates)<br>
&gt; &gt; =A0 =A0 e) UPDATE from remote<br>
&gt; &gt;<br>
&gt; &gt; Here, the remote has to consider whether INFO belongs to UPDATE o=
r<br>
&gt; &gt; INVITE as<br>
&gt; &gt; it is possible for INFO to reach before 200 OK for UPDATE as well=
 in<br>
&gt; &gt; the<br>
&gt; &gt; same sequence.</p>
<p dir=3D"ltr">And CSeq headers wouldn&#39;t help here because ....?</p>
<p dir=3D"ltr">&gt; &gt; Also, RFC 2976 </p>
<p dir=3D"ltr">which FWIW is obsoleted by RFC6086</p>
<p dir=3D"ltr">&gt; &gt; clarifies that<br>
&gt; &gt;<br>
&gt; &gt; &quot; - The extensions that use the INFO message MUST NOT rely o=
n the<br>
&gt; &gt; =A0 =A0 =A0INFO message to do anything that effects the SIP call =
state or the<br>
&gt; &gt; =A0 =A0 =A0state of related sessions.&quot;</p>
<p dir=3D"ltr">And I don&#39;t believe that it does.</p>
<p dir=3D"ltr">&gt; &gt; But SIP Trickle ICE state is depend upon the &quot=
;state of related<br>
&gt; &gt; sessions&quot; as<br>
&gt; &gt; UPDATE would have change the state in the remote.</p>
<p dir=3D"ltr">I am not sure what you are saying or why it is a problem.</p=
>
<p dir=3D"ltr">&gt; &gt; 2) Trickle ICE INFO with serial forking</p>
<p dir=3D"ltr">INFO requests are sent within a dialog. They will go through=
 the prong associated with that dialog and would not be forked.</p>
<p dir=3D"ltr">&gt; &gt; =A0 a) INVITE from local<br>
&gt; &gt; =A0 b) INVITE is forked by proxy to first remote destination<br>
&gt; &gt; =A0 c) 100 trying is reaching local<br>
&gt; &gt; =A0 d) INFO with Trickle ICE from local</p>
<p dir=3D"ltr">No, this should&#39;t happen. We can&#39;t send the INFO bef=
ore we have a dialog.</p>
<p dir=3D"ltr">&gt; &gt; =A0 e) INFO is forward by proxy to first remote de=
stination<br>
&gt; &gt; =A0 f) INVITE is forked by proxy to second remote destination<br>
&gt; &gt; =A0 g) Whether INFO has to be forked?</p>
<p dir=3D"ltr">See above.</p>
<p dir=3D"ltr">&gt; &gt; It is not mentioned in the draft whether INFO has =
to be forked to the<br>
&gt; &gt; second<br>
&gt; &gt; remote destination as well. Could you please explain the expect<b=
r>
&gt; &gt; behavior for<br>
&gt; &gt; this scenario.</p>
<p dir=3D"ltr">I think the above commencts should answer your questions. We=
 will make sure we add those as clarifications before our next submission (=
hopefully as a WG document)</p>
<p dir=3D"ltr">Emil</p>
<p dir=3D"ltr">&gt; &gt; Thanks<br>
&gt; &gt; Partha<br>
&gt; &gt;<br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; mmusic mailing list<br>
&gt; &gt; <a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
&gt; &gt; <a href=3D"https://www.ietf.org/mailman/listinfo/mmusic">https://=
www.ietf.org/mailman/listinfo/mmusic</a><br>
&gt;<br>
</p>

--001a11337576ec921804f544c75b--


From nobody Sun Mar 23 08:14:47 2014
Return-Path: <emcho@sip-communicator.org>
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 1F66E1A098D for <mmusic@ietfa.amsl.com>; Sun, 23 Mar 2014 08:14:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 fLQ4A9rpZbBF for <mmusic@ietfa.amsl.com>; Sun, 23 Mar 2014 08:14:40 -0700 (PDT)
Received: from mail-we0-f180.google.com (mail-we0-f180.google.com [74.125.82.180]) by ietfa.amsl.com (Postfix) with ESMTP id 122561A6FD7 for <mmusic@ietf.org>; Sun, 23 Mar 2014 08:14:39 -0700 (PDT)
Received: by mail-we0-f180.google.com with SMTP id p61so2754313wes.39 for <mmusic@ietf.org>; Sun, 23 Mar 2014 08:14:38 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=1d+KKhtp0XejuPNyMZhw87Ln6kMVjJjDOAlDV7epsko=; b=EbD1AfZBRloUWJnvyKfQ7/cVFXKugy8KALwP/bfCuZIocLah6vahMTOfiC9TbPBgYK XSNhfETwMV4u1e+xx+GnIXaIeYFEbomzZfZNXzdSiGy1wt3tKj31rAz+bUIDDDfL4EtQ 4rgwnsuTl8mt42SKVo1WgPnTHlx5jMPMlNIKmao5Fj2NvLASsnOQt1L6aURAXn7sMNqs Nn7hqkSyF8bnmMvaOZQhJQ5HoxnW6oV2UG9f/BfwAiu4be1nBtOO1sAecBp7BDKF4jKf docwz5y5pU680dyLLvQIZZKrUkPpe0hvfHOGhkZ2k+lAL9NJ1mffFodNJIYuE6qqdu0U pJHg==
X-Gm-Message-State: ALoCoQmN7a3+43k2FJulPcXyCWB2AUVe33A23qXxIVLh5HGqaci8yvOsayKR2pI2j6Q4L7cPlqSk
X-Received: by 10.180.72.239 with SMTP id g15mr9962480wiv.45.1395587678621; Sun, 23 Mar 2014 08:14:38 -0700 (PDT)
Received: from camionet.local (neu67-4-88-160-65-79.fbx.proxad.net. [88.160.65.79]) by mx.google.com with ESMTPSA id rx9sm20167583wjb.20.2014.03.23.08.14.36 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 23 Mar 2014 08:14:37 -0700 (PDT)
Message-ID: <532EFA5B.7060502@jitsi.org>
Date: Sun, 23 Mar 2014 16:14:35 +0100
From: Emil Ivov <emcho@jitsi.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Cullen Jennings <fluffy@iii.ca>
References: <CF489B5D.25EB0%alissa@cooperw.in> <CAPvvaaKM7S0jRA1dQgCZLGfg4ryNRriMfvSM3V6sD+=3TX4Jzw@mail.gmail.com> <735A4CD3-A4CB-43F0-B823-516E38664620@iii.ca>
In-Reply-To: <735A4CD3-A4CB-43F0-B823-516E38664620@iii.ca>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/6Kokmoc2nF-YyLDZfbxor3vb5q0
Cc: draft-ietf-mmusic-latching@tools.ietf.org, mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] AD evaluation: draft-ietf-mmusic-latching-04
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: Sun, 23 Mar 2014 15:14:43 -0000

On 22.03.14, 19:59, Cullen Jennings wrote:
>
> On Mar 19, 2014, at 2:51 AM, Emil Ivov <emcho@jitsi.org> wrote:
>
>> Also it is worth reminding that the above threats apply mostly to
>> generic Internet deployments. Many people using latching today, do
>> so in controlled environments, where that kind of hijacking could
>> not occur.
>
> Could you provide a bit more about where you see this being used?

Test services for one. Multi-site enterprise networks in combination 
with VPN. Public podcast-like conference calls with no access control.

I am sure there are others ... but I don't think it's worth spending 
time on them. The document already advises against latching. You 
personally approved the text and we all have other, more important 
drafts to worry about.

> Most the latching I have seen is in exactly the places where network
> is not at all controlled.

Absolutely there's a lot of that and all the people running services 
that way should have a read at the security considerations section in 
that draft. One more reason to get it out the door.

Emil


-- 
https://jitsi.org


From nobody Sun Mar 23 11:01:27 2014
Return-Path: <pkyzivat@alum.mit.edu>
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 5C9F61A6FF5 for <mmusic@ietfa.amsl.com>; Sun, 23 Mar 2014 11:01:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] 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 OceZbeacJTeg for <mmusic@ietfa.amsl.com>; Sun, 23 Mar 2014 11:01:19 -0700 (PDT)
Received: from qmta13.westchester.pa.mail.comcast.net (qmta13.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:243]) by ietfa.amsl.com (Postfix) with ESMTP id F35351A6FF4 for <mmusic@ietf.org>; Sun, 23 Mar 2014 11:01:18 -0700 (PDT)
Received: from omta17.westchester.pa.mail.comcast.net ([76.96.62.89]) by qmta13.westchester.pa.mail.comcast.net with comcast id h5jU1n0061vXlb85D61J6Z; Sun, 23 Mar 2014 18:01:18 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta17.westchester.pa.mail.comcast.net with comcast id h61J1n00K3ZTu2S3d61JP5; Sun, 23 Mar 2014 18:01:18 +0000
Message-ID: <532F216E.7090400@alum.mit.edu>
Date: Sun, 23 Mar 2014 14:01:18 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: mmusic@ietf.org
References: <01e601cf423c$57255890$057009b0$@co.in> <00c901cf4687$0a48dbb0$1eda9310$@co.in> <CAPvvaaKW+vxhJFqUPRZ-YfPQ4dHOS-=YwZaW+=NS3DttaaXD=Q@mail.gmail.com>
In-Reply-To: <CAPvvaaKW+vxhJFqUPRZ-YfPQ4dHOS-=YwZaW+=NS3DttaaXD=Q@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1395597678; bh=zsHWOFwhgBRzso+MX//983H0SRi1VHYt8HZdlyGfciE=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=OIKF4GW1BtDFth0z+UA+dvOcqVqs2ktd9BMXtYowhIkWUtcRcNrp9dKAzzQXO8PRa +/9iPFwqVBza5oZJovTZl0Y6+3XaVl6EMQ4MN213FRm/U8t8agogdATgCYKCzEzniJ K9At4sq00Gxxv/hG3FNCuhBBFZOzdmuKh0+elT75HUZs7eT6ZqEy2GUv3BnRZmfuag ramJHHOw5o3YMIKkSAdmY3yYZzzvXpEcSEigzEvvXHiLPoNQOe6s9dpstVzDe200KF /E7diOhc1wMTcSO/Fj12wMSbhfc1CLYsSNw23mH+c69v2GvKOuDeRJdB+ShAmmBiNg zh8x0qNf89fnQ==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/7FpMtT3DSaNS-Y2AVUTlYw7mQ2s
Subject: Re: [MMUSIC] Comment on SIP Trickle ICE based on INFO draft
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: Sun, 23 Mar 2014 18:01:20 -0000

One comment

On 3/23/14 7:54 AM, Emil Ivov wrote:

> This is analogous to an UPDATE that is received before regular 5245 ICE
> processing has completed.
>
>  > >     a) INVITE from local
>  > >     b) 183 session progress from remote
>  > >     c) PRACK from local
>  > >     d) INFO from local (relay candidates)
>  > >     e) UPDATE from remote
>  > >
>  > > Here, the remote has to consider whether INFO belongs to UPDATE or
>  > > INVITE as
>  > > it is possible for INFO to reach before 200 OK for UPDATE as well in
>  > > the
>  > > same sequence.
>
> And CSeq headers wouldn't help here because ....?

IIUC, the question is whether the remote can tell whether the INFO was 
sent before or after receiving the UPDATE.

CSeq values are independent in each direction. So they are useless to 
answer this question. Something else will be needed.

	Thanks,
	Paul


From nobody Sun Mar 23 11:53:12 2014
Return-Path: <emcho@sip-communicator.org>
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 E581D1A08ED for <mmusic@ietfa.amsl.com>; Sun, 23 Mar 2014 11:53:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 cdb5-dELHejU for <mmusic@ietfa.amsl.com>; Sun, 23 Mar 2014 11:53:04 -0700 (PDT)
Received: from mail-wi0-f181.google.com (mail-wi0-f181.google.com [209.85.212.181]) by ietfa.amsl.com (Postfix) with ESMTP id 81FBC1A07A0 for <mmusic@ietf.org>; Sun, 23 Mar 2014 11:53:04 -0700 (PDT)
Received: by mail-wi0-f181.google.com with SMTP id hm4so1824210wib.14 for <mmusic@ietf.org>; Sun, 23 Mar 2014 11:53:03 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=30M85hZUYGJ2zAQNV59h2rciYC6OddeolpI6rNhP2O4=; b=iPqczUMHSIHGmubPWbL8mSFna1CZYDqU4lmCCp7xzgNK30V+qvLWyaWqA8Ibu0gYMW jCaTPH+fyjtkUa88ut5KkPiZyiEapco8UFg91WEtXel/pxEj3ywoYYD3f/OBhWWIeN1x J+rXUTqvLJtNqQEALgOKbqlWTpeM4NHDa+UHAMintdxXoPFquFiK7XHhVx7UVUqS4XgY Fo1jjia1a4KPulb/VZAMXYx4iDb7xwlcbR9M3gbLGHTjyfW2t/LnhonlIWaFY3+iNlBp JPsrTWtR+knQVK+4MM0F3YGMXVjzhx5ToQa0dhNXmZTY7ffWssXfnZGelirpUA3X3LC8 zkdQ==
X-Gm-Message-State: ALoCoQmKkaGBH0/r0OXNiFNo+5tutWVrdALy4hG8jb6ukIa8HgznFgklbOP7l71jmLukY/0W2ViR
X-Received: by 10.180.185.232 with SMTP id ff8mr10137034wic.25.1395600783116;  Sun, 23 Mar 2014 11:53:03 -0700 (PDT)
Received: from camionet.local (neu67-4-88-160-65-79.fbx.proxad.net. [88.160.65.79]) by mx.google.com with ESMTPSA id hd7sm12731715wjc.11.2014.03.23.11.53.01 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 23 Mar 2014 11:53:02 -0700 (PDT)
Message-ID: <532F2D8C.2010104@jitsi.org>
Date: Sun, 23 Mar 2014 19:53:00 +0100
From: Emil Ivov <emcho@jitsi.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, mmusic@ietf.org
References: <01e601cf423c$57255890$057009b0$@co.in> <00c901cf4687$0a48dbb0$1eda9310$@co.in> <CAPvvaaKW+vxhJFqUPRZ-YfPQ4dHOS-=YwZaW+=NS3DttaaXD=Q@mail.gmail.com> <532F216E.7090400@alum.mit.edu>
In-Reply-To: <532F216E.7090400@alum.mit.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/mlmNVyEPinqPfWhnh2GoG3taqFE
Subject: Re: [MMUSIC] Comment on SIP Trickle ICE based on INFO draft
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: Sun, 23 Mar 2014 18:53:07 -0000

On 23.03.14, 19:01, Paul Kyzivat wrote:
> One comment
>
> On 3/23/14 7:54 AM, Emil Ivov wrote:
>
>> This is analogous to an UPDATE that is received before regular 5245 ICE
>> processing has completed.
>>
>>  > >     a) INVITE from local
>>  > >     b) 183 session progress from remote
>>  > >     c) PRACK from local
>>  > >     d) INFO from local (relay candidates)
>>  > >     e) UPDATE from remote
>>  > >
>>  > > Here, the remote has to consider whether INFO belongs to UPDATE or
>>  > > INVITE as
>>  > > it is possible for INFO to reach before 200 OK for UPDATE as well in
>>  > > the
>>  > > same sequence.
>>
>> And CSeq headers wouldn't help here because ....?
>
> IIUC, the question is whether the remote can tell whether the INFO was
> sent before or after receiving the UPDATE.
>
> CSeq values are independent in each direction. So they are useless to
> answer this question. Something else will be needed.

OK, I see. Then the easiest way to tackle this would be to mandate that 
all INFOs contain the ICE ufrag and pwd of the offer/answer they are 
pertaining to.

Does anyone see a problem with that?

Emil

-- 
https://jitsi.org


From nobody Tue Mar 25 04:15:21 2014
Return-Path: <internet-drafts@ietf.org>
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 142661A03B9; Tue, 25 Mar 2014 04:14:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 qPZ5ibLaTVYo; Tue, 25 Mar 2014 04:14:33 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 685491A0198; Tue, 25 Mar 2014 04:14:33 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 5.2.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140325111433.26810.28806.idtracker@ietfa.amsl.com>
Date: Tue, 25 Mar 2014 04:14:33 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/j5iQVKxmI3wmVFfkbCrpySgW5X8
Cc: mmusic@ietf.org
Subject: [MMUSIC] I-D Action: draft-ietf-mmusic-udptl-dtls-06.txt
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 25 Mar 2014 11:14:35 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Multiparty Multimedia Session Control Working Group of the IETF.

        Title           : UDP Transport Layer (UDPTL) over Datagram Transport Layer Security (DTLS)
        Authors         : Christer Holmberg
                          Ivo Sedlacek
                          Gonzalo Salgueiro
	Filename        : draft-ietf-mmusic-udptl-dtls-06.txt
	Pages           : 23
	Date            : 2014-03-25

Abstract:
   This document specifies how the UDP Transport Layer (UDPTL) protocol,
   the predominant transport protocol for T.38 fax, can be transported
   over the Datagram Transport Layer Security (DTLS) protocol, how the
   usage of UDPTL over DTLS is indicated in the Session Description
   Protocol (SDP), and how UDPTL over DTLS is negotiated in a session
   established using the Session Initiation Protocol (SIP).


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-mmusic-udptl-dtls/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-mmusic-udptl-dtls-06

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-udptl-dtls-06


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Tue Mar 25 04:17:31 2014
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 0B8651A03B9 for <mmusic@ietfa.amsl.com>; Tue, 25 Mar 2014 04:17:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.239
X-Spam-Level: 
X-Spam-Status: No, score=-1.239 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, HOST_MISMATCH_NET=0.311, HTML_MESSAGE=0.001, 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 p2cxDR8g9fVA for <mmusic@ietfa.amsl.com>; Tue, 25 Mar 2014 04:17:01 -0700 (PDT)
Received: from sessmg21.mgmt.ericsson.se (sessmg21.ericsson.net [193.180.251.40]) by ietfa.amsl.com (Postfix) with ESMTP id 5B8451A0198 for <mmusic@ietf.org>; Tue, 25 Mar 2014 04:17:01 -0700 (PDT)
X-AuditID: c1b4fb28-b7f8e8e000007f0a-c5-533165ab0016
Received: from ESESSHC023.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg21.mgmt.ericsson.se (Symantec Mail Security) with SMTP id 9E.BC.32522.BA561335; Tue, 25 Mar 2014 12:16:59 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.213]) by ESESSHC023.ericsson.se ([153.88.183.87]) with mapi id 14.02.0387.000; Tue, 25 Mar 2014 12:16:58 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "mmusic (E-mail)" <mmusic@ietf.org>
Thread-Topic: Draft new version: draft-ietf-mmusic-udptl-dtls-06
Thread-Index: Ac9IG4mMkcTL4w1QT1G6WY9p1Ch1lg==
Date: Tue, 25 Mar 2014 11:16:58 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D260017@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.147]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B1D260017ESESSMB209erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrNLMWRmVeSWpSXmKPExsUyM+Jvje7qVMNgg86Nphb/9iZZTF3+mMWB yWPJkp9MHl8uf2YLYIrisklJzcksSy3St0vgyrjV85ql4IBYxdvWn+wNjL+Euxg5OCQETCRu XtLtYuQEMsUkLtxbz9bFyMUhJHCCUWL7rcOsEM4SRom7DfsYQRrYBCwkuv9pgzSICKhLtG7u YwWxmQUcJc7e2s4EYgsLWEtMXveRCaLGQeLxq9XsELaeRPebD8wgNouAqsSmhrNgNbwCvhIH p/azgNiMQEd8P7WGCWKmuMStJ/OZII4TkFiy5zwzhC0q8fLxP1aI+5Ukpm1NgyjPl1jdf4kV YqSgxMmZT1gmMArPQjJpFpKyWUjKIOI6Egt2f2KDsLUlli18zQxjnznwmAlZfAEj+ypGyeLU 4uLcdCNDvdz03BK91KLM5OLi/Dy94tRNjMAIOrjlt8YOxu5r9ocYpTlYlMR5q2Z2BgkJpCeW pGanphakFsUXleakFh9iZOLglGpgtC2MufCV1UKZ2VZe+UPkkyWKy8SF59xhYuds6X5y19/X okylbWPz9TkszBqzzqif3rMi0GRV6BWDJS28lWebO63fz7pyrI4vc1eIlculLkYxxUyBdczv Tp9c3M/83nd+X8Tca2v2qa/f47bx6ItPNx+eec77cTNHyH7H9Ut/nr644Ub1lf8WHkosxRmJ hlrMRcWJAEGh7otuAgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/4aNYUb_cMgHEzHZikK6wu3OzGhA
Cc: "mmusic-chairs@tools.ietf.org" <mmusic-chairs@tools.ietf.org>
Subject: [MMUSIC] Draft new version: draft-ietf-mmusic-udptl-dtls-06
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: Tue, 25 Mar 2014 11:17:03 -0000

--_000_7594FB04B1934943A5C02806D1A2204B1D260017ESESSMB209erics_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi,

Based on Flemming's comments, we've submitted a new version of the udptl-dt=
ls draft.

The changes are mainly editorial, with the biggest change being that the SD=
P O/A procedures are now structured according to RFC 3264.

Regards,

Christer

--_000_7594FB04B1934943A5C02806D1A2204B1D260017ESESSMB209erics_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Based on Flemming&#8217;s comments, we&#8217;ve subm=
itted a new version of the udptl-dtls draft.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The changes are mainly editorial, with the biggest c=
hange being that the SDP O/A procedures are now structured according to RFC=
 3264.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Regards,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Christer<o:p></o:p></p>
</div>
</body>
</html>

--_000_7594FB04B1934943A5C02806D1A2204B1D260017ESESSMB209erics_--


From nobody Tue Mar 25 13:24:40 2014
Return-Path: <fandreas@cisco.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 CBA9F1A0240 for <mmusic@ietfa.amsl.com>; Tue, 25 Mar 2014 13:24:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 Oa5Hlu90_rB2 for <mmusic@ietfa.amsl.com>; Tue, 25 Mar 2014 13:24:36 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id D32A81A020B for <mmusic@ietf.org>; Tue, 25 Mar 2014 13:24:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12187; q=dns/txt; s=iport; t=1395779074; x=1396988674; h=message-id:date:from:mime-version:to:cc:subject; bh=ZUnHMZUVaVUrY/20W7U0ReWPaOd/zYL8jKM5DDDb5uY=; b=FypPtxDMTlzq8ABXKy2kwLyyU9uSF0e52vNExXsLzszmfr0hWqMfAjfM CS5fS8UWywcwJjDELhWRNBi0cOnbuZlxuTbxFQZr6Mei/9El3kNvcHO/y 3294Fxrs861SQ37w4vPl3rT5GjrmdI391vpGENNf1p82uiyUdLPsalxxy s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ArsKAGHlMVOrRDoI/2dsb2JhbABZgwY7UYhroHILmQqBHRZ0gklbATwWGAMCAQIBSw0BBwEBBYdvCQXPZxeObhCELwSYTYEykQCDSiE
X-IronPort-AV: E=Sophos;i="4.97,730,1389744000";  d="scan'208,217";a="106436804"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-3.cisco.com with ESMTP; 25 Mar 2014 20:24:33 +0000
Received: from dhcp-10-155-84-30.cisco.com (dhcp-10-155-84-30.cisco.com [10.155.84.30]) by mtv-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s2PKOXvB024214; Tue, 25 Mar 2014 20:24:33 GMT
Message-ID: <5331E601.8070605@cisco.com>
Date: Tue, 25 Mar 2014 16:24:33 -0400
From: Flemming Andreasen <fandreas@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: mmusic <mmusic@ietf.org>
Content-Type: multipart/alternative; boundary="------------040407040906020009040409"
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/zHIVRxFyqlcIWHZYwYDY8ppi7P0
Cc: draft-ietf-mmusic-udptl-dtls@tools.ietf.org
Subject: [MMUSIC] WGLC for draft-ietf-mmusic-udptl-dtls-06
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: Tue, 25 Mar 2014 20:24:39 -0000

This is a multi-part message in MIME format.
--------------040407040906020009040409
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

This is to announce a 2 week Working Group Last Call for

     draft-ietf-mmusic-udptl-dtls-06

as Proposed Standard. Please review and provide any comments you may 
have on the document by April 8, 2014. Comments should be sent to the 
document authors and the MMUSIC WG list. If you review the document but 
do not have any comments, please send a note to that effect as well.


Thanks

        Flemming



Draft info:

This draft is a work item of the Multiparty Multimedia Session Control Working Group of the IETF.

         Title           : UDP Transport Layer (UDPTL) over Datagram Transport Layer Security (DTLS)
         Authors         : Christer Holmberg
                           Ivo Sedlacek
                           Gonzalo Salgueiro
	Filename        : draft-ietf-mmusic-udptl-dtls-06.txt
	Pages           : 23
	Date            : 2014-03-25

Abstract:
    This document specifies how the UDP Transport Layer (UDPTL) protocol,
    the predominant transport protocol for T.38 fax, can be transported
    over the Datagram Transport Layer Security (DTLS) protocol, how the
    usage of UDPTL over DTLS is indicated in the Session Description
    Protocol (SDP), and how UDPTL over DTLS is negotiated in a session
    established using the Session Initiation Protocol (SIP).


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-mmusic-udptl-dtls/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-mmusic-udptl-dtls-06

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-udptl-dtls-06


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/



--------------040407040906020009040409
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    This is to announce a 2 week Working Group Last Call for<br>
    &nbsp;&nbsp;&nbsp; <br>
    &nbsp;&nbsp;&nbsp; draft-ietf-mmusic-udptl-dtls-06<br>
    &nbsp;&nbsp;&nbsp; <br>
    as Proposed Standard. Please review and provide any comments you may
    have on the document by April 8, 2014. Comments should be sent to
    the document authors and the MMUSIC WG list. If you review the
    document but do not have any comments, please send a note to that
    effect as well. <br>
    <br>
    <span class="Apple-style-span" style="border-collapse: separate;
      color: rgb(0, 0, 0); font-family: Arial; font-size: medium;
      font-style: normal; font-variant: normal; font-weight: normal;
      letter-spacing: normal; line-height: normal; orphans: 2;
      text-indent: 0px; text-transform: none; white-space: normal;
      widows: 2; word-spacing: 0px;"><span class="Apple-style-span"
        style="border-collapse: separate; color: rgb(0, 0, 0);
        font-family: Arial; font-size: medium; font-style: normal;
        font-variant: normal; font-weight: normal; letter-spacing:
        normal; line-height: normal; orphans: 2; text-indent: 0px;
        text-transform: none; white-space: normal; widows: 2;
        word-spacing: 0px;"><span class="Apple-style-span"
          style="border-collapse: separate; color: rgb(0, 0, 0);
          font-family: Arial; font-size: medium; font-style: normal;
          font-variant: normal; font-weight: normal; letter-spacing:
          normal; line-height: normal; orphans: 2; text-indent: 0px;
          text-transform: none; white-space: normal; widows: 2;
          word-spacing: 0px;"><span class="Apple-style-span"
            style="border-collapse: separate; color: rgb(0, 0, 0);
            font-family: Arial; font-size: medium; font-style: normal;
            font-variant: normal; font-weight: normal; letter-spacing:
            normal; line-height: normal; orphans: 2; text-indent: 0px;
            text-transform: none; white-space: normal; widows: 2;
            word-spacing: 0px;"><span class="Apple-style-span"
              style="border-collapse: separate; color: rgb(0, 0, 0);
              font-family: Arial; font-size: medium; font-style: normal;
              font-variant: normal; font-weight: normal; letter-spacing:
              normal; line-height: normal; orphans: 2; text-indent: 0px;
              text-transform: none; white-space: normal; widows: 2;
              word-spacing: 0px;"><span class="Apple-style-span"
                style="border-collapse: separate; color: rgb(0, 0, 0);
                font-family: Arial; font-size: medium; font-style:
                normal; font-variant: normal; font-weight: normal;
                letter-spacing: normal; line-height: normal; orphans: 2;
                text-indent: 0px; text-transform: none; white-space:
                normal; widows: 2; word-spacing: 0px;"><span
                  class="Apple-style-span" style="border-collapse:
                  separate; color: rgb(0, 0, 0); font-family: Arial;
                  font-size: medium; font-style: normal; font-variant:
                  normal; font-weight: normal; letter-spacing: normal;
                  line-height: normal; orphans: 2; text-indent: 0px;
                  text-transform: none; white-space: normal; widows: 2;
                  word-spacing: 0px;"><span class="Apple-style-span"
                    style="border-collapse: separate; color: rgb(0, 0,
                    0); font-family: Arial; font-size: medium;
                    font-style: normal; font-variant: normal;
                    font-weight: normal; letter-spacing: normal;
                    line-height: normal; orphans: 2; text-indent: 0px;
                    text-transform: none; white-space: normal; widows:
                    2; word-spacing: 0px;"><span
                      class="Apple-style-span" style="border-collapse:
                      separate; color: rgb(0, 0, 0); font-family: Arial;
                      font-size: medium; font-style: normal;
                      font-variant: normal; font-weight: normal;
                      letter-spacing: normal; line-height: normal;
                      orphans: 2; text-indent: 0px; text-transform:
                      none; white-space: normal; widows: 2;
                      word-spacing: 0px;"><span class="Apple-style-span"
                        style="border-collapse: separate; color: rgb(0,
                        0, 0); font-family: Arial; font-size: medium;
                        font-style: normal; font-variant: normal;
                        font-weight: normal; letter-spacing: normal;
                        line-height: normal; orphans: 2; text-indent:
                        0px; text-transform: none; white-space: normal;
                        widows: 2; word-spacing: 0px;"><span
                          class="Apple-style-span"
                          style="border-collapse: separate; color:
                          rgb(0, 0, 0); font-family: Arial; font-size:
                          medium; font-style: normal; font-variant:
                          normal; font-weight: normal; letter-spacing:
                          normal; line-height: normal; orphans: 2;
                          text-indent: 0px; text-transform: none;
                          white-space: normal; widows: 2; word-spacing:
                          0px;"><span class="Apple-style-span"
                            style="border-collapse: separate; color:
                            rgb(0, 0, 0); font-family: Arial; font-size:
                            medium; font-style: normal; font-variant:
                            normal; font-weight: normal; letter-spacing:
                            normal; line-height: normal; orphans: 2;
                            text-indent: 0px; text-transform: none;
                            white-space: normal; widows: 2;
                            word-spacing: 0px;"><span
                              class="Apple-style-span"
                              style="border-collapse: separate; color:
                              rgb(0, 0, 0); font-family: Arial;
                              font-size: medium; font-style: normal;
                              font-variant: normal; font-weight: normal;
                              letter-spacing: normal; line-height:
                              normal; orphans: 2; text-indent: 0px;
                              text-transform: none; white-space: normal;
                              widows: 2; word-spacing: 0px;"><span
                                class="Apple-style-span"
                                style="border-collapse: separate; color:
                                rgb(0, 0, 0); font-family: Arial;
                                font-size: medium; font-style: normal;
                                font-variant: normal; font-weight:
                                normal; letter-spacing: normal;
                                line-height: normal; orphans: 2;
                                text-indent: 0px; text-transform: none;
                                white-space: normal; widows: 2;
                                word-spacing: 0px;"><br>
                                Thanks <br>
                                <br>
                                &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Flemming<br>
                                <br>
                                <br>
                                <br>
                                Draft info:<br>
                              </span></span></span></span></span></span></span></span></span></span></span></span></span></span>
    <pre wrap="">This draft is a work item of the Multiparty Multimedia Session Control Working Group of the IETF.

        Title           : UDP Transport Layer (UDPTL) over Datagram Transport Layer Security (DTLS)
        Authors         : Christer Holmberg
                          Ivo Sedlacek
                          Gonzalo Salgueiro
	Filename        : draft-ietf-mmusic-udptl-dtls-06.txt
	Pages           : 23
	Date            : 2014-03-25

Abstract:
   This document specifies how the UDP Transport Layer (UDPTL) protocol,
   the predominant transport protocol for T.38 fax, can be transported
   over the Datagram Transport Layer Security (DTLS) protocol, how the
   usage of UDPTL over DTLS is indicated in the Session Description
   Protocol (SDP), and how UDPTL over DTLS is negotiated in a session
   established using the Session Initiation Protocol (SIP).


The IETF datatracker status page for this draft is:
<a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/draft-ietf-mmusic-udptl-dtls/">https://datatracker.ietf.org/doc/draft-ietf-mmusic-udptl-dtls/</a>

There's also a htmlized version available at:
<a class="moz-txt-link-freetext" href="http://tools.ietf.org/html/draft-ietf-mmusic-udptl-dtls-06">http://tools.ietf.org/html/draft-ietf-mmusic-udptl-dtls-06</a>

A diff from the previous version is available at:
<a class="moz-txt-link-freetext" href="http://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-udptl-dtls-06">http://www.ietf.org/rfcdiff?url2=draft-ietf-mmusic-udptl-dtls-06</a>


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
<a class="moz-txt-link-freetext" href="ftp://ftp.ietf.org/internet-drafts/">ftp://ftp.ietf.org/internet-drafts/</a></pre>
    <br>
  </body>
</html>

--------------040407040906020009040409--


From nobody Tue Mar 25 18:35:47 2014
Return-Path: <partha@parthasarathi.co.in>
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 EFCE81A0040 for <mmusic@ietfa.amsl.com>; Tue, 25 Mar 2014 18:35:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.699
X-Spam-Level: 
X-Spam-Status: No, score=0.699 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham
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 rd96Mx26XD2k for <mmusic@ietfa.amsl.com>; Tue, 25 Mar 2014 18:35:43 -0700 (PDT)
Received: from outbound.mailhostbox.com (outbound.mailhostbox.com [162.222.225.14]) by ietfa.amsl.com (Postfix) with ESMTP id E24D31A0030 for <mmusic@ietf.org>; Tue, 25 Mar 2014 18:35:42 -0700 (PDT)
Received: from userPC (unknown [122.167.132.183]) (Authenticated sender: partha@parthasarathi.co.in) by outbound.mailhostbox.com (Postfix) with ESMTPA id EFC6B1908611; Wed, 26 Mar 2014 01:35:36 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=parthasarathi.co.in; s=20120823; t=1395797740; bh=EEMgRq/9cl5SOYiTP9xPlSXJzqOzm22nJU3uJ/X9JqY=; h=From:To:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type:Content-Transfer-Encoding; b=W/AzhI3xgTMNB/wLWwT+X0+JlC/JSOqyQtnBX8FOSrkoEQLRHknrBXoNkPlj4EOcA 5Cg8+UJ7RKnCcADJXSGGTb2r/44rJy21ix6herm9Zn/a8fnQ8n0oyQmG0AtEoOFGZz gn/iz62MmjSRR0pIUO5zen0vLtii6G/u2UAWBEos=
From: "Parthasarathi R" <partha@parthasarathi.co.in>
To: "'Emil Ivov'" <emcho@jitsi.org>, "'Paul Kyzivat'" <pkyzivat@alum.mit.edu>,  <mmusic@ietf.org>
References: <01e601cf423c$57255890$057009b0$@co.in> <00c901cf4687$0a48dbb0$1eda9310$@co.in> <CAPvvaaKW+vxhJFqUPRZ-YfPQ4dHOS-=YwZaW+=NS3DttaaXD=Q@mail.gmail.com> <532F216E.7090400@alum.mit.edu> <532F2D8C.2010104@jitsi.org>
In-Reply-To: <532F2D8C.2010104@jitsi.org>
Date: Wed, 26 Mar 2014 07:05:28 +0530
Message-ID: <01b701cf4893$afbf0e80$0f3d2b80$@co.in>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac9GySWWywyls2hzQym+UDzw8mRFLQBycSDw
Content-Language: en-us
X-CTCH-RefID: str=0001.0A020206.53322EEC.0023, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0
X-CTCH-VOD: Unknown
X-CTCH-Spam: Unknown
X-CTCH-Score: 0.000
X-CTCH-Rules: 
X-CTCH-Flags: 0
X-CTCH-ScoreCust: 0.000
X-CTCH-SenderID: partha@parthasarathi.co.in
X-CTCH-SenderID-TotalMessages: 1
X-CTCH-SenderID-TotalSpam: 0
X-CTCH-SenderID-TotalSuspected: 0
X-CTCH-SenderID-TotalBulk: 0
X-CTCH-SenderID-TotalConfirmed: 0
X-CTCH-SenderID-TotalRecipients: 0
X-CTCH-SenderID-TotalVirus: 0
X-CTCH-SenderID-BlueWhiteFlag: 0
X-Scanned-By: MIMEDefang 2.72 on 70.87.28.138
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/3dbVGBb6T-58QKpw0UQgbuqyZr0
Subject: Re: [MMUSIC] Comment on SIP Trickle ICE based on INFO draft
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: Wed, 26 Mar 2014 01:35:46 -0000

Hi Emil,

<snip> > OK, I see. Then the easiest way to tackle this would be to mandate
that
> all INFOs contain the ICE ufrag and pwd of the offer/answer they are
> pertaining to.
> 
> Does anyone see a problem with that?
</snip>

I guess that your intention is to pass the corresponding Origin ("o") line
in each INFO message by which INFO will be identified for the corresponding
SDP by which the ICE candidates are passed. I'm saying so as there is no
purpose of passing ICE ufrag & pwd in each INFO message 

Thanks
Partha 


> -----Original Message-----
> From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Emil Ivov
> Sent: Monday, March 24, 2014 12:23 AM
> To: Paul Kyzivat; mmusic@ietf.org
> Subject: Re: [MMUSIC] Comment on SIP Trickle ICE based on INFO draft
> 
> 
> 
> On 23.03.14, 19:01, Paul Kyzivat wrote:
> > One comment
> >
> > On 3/23/14 7:54 AM, Emil Ivov wrote:
> >
> >> This is analogous to an UPDATE that is received before regular 5245
> ICE
> >> processing has completed.
> >>
> >>  > >     a) INVITE from local
> >>  > >     b) 183 session progress from remote
> >>  > >     c) PRACK from local
> >>  > >     d) INFO from local (relay candidates)
> >>  > >     e) UPDATE from remote
> >>  > >
> >>  > > Here, the remote has to consider whether INFO belongs to UPDATE
> or
> >>  > > INVITE as
> >>  > > it is possible for INFO to reach before 200 OK for UPDATE as
> well in
> >>  > > the
> >>  > > same sequence.
> >>
> >> And CSeq headers wouldn't help here because ....?
> >
> > IIUC, the question is whether the remote can tell whether the INFO
> was
> > sent before or after receiving the UPDATE.
> >
> > CSeq values are independent in each direction. So they are useless to
> > answer this question. Something else will be needed.
> 
> OK, I see. Then the easiest way to tackle this would be to mandate that
> all INFOs contain the ICE ufrag and pwd of the offer/answer they are
> pertaining to.
> 
> Does anyone see a problem with that?
> 
> Emil
> 
> --
> https://jitsi.org
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic


From nobody Tue Mar 25 20:00:23 2014
Return-Path: <dhanes@cisco.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 DF2631A0292 for <mmusic@ietfa.amsl.com>; Tue, 25 Mar 2014 20:00:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level: 
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 9sd8K9R_q27Z for <mmusic@ietfa.amsl.com>; Tue, 25 Mar 2014 20:00:17 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id 4B3401A0035 for <mmusic@ietf.org>; Tue, 25 Mar 2014 20:00:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=14023; q=dns/txt; s=iport; t=1395802816; x=1397012416; h=from:to:cc:subject:date:message-id:in-reply-to: mime-version; bh=uNSNE2OMi7tsKVW1tu8bHr6cJA+U0g7EFNcdvsunwQs=; b=e7SZTEtQzOWsQ/2Y2Kqtr2SMVtYxKvhcF55B3KKn/uyaWr9shkIPX298 zUlrKeUVGZNxzYbqnMf6q041/sCB/df8y3yF6vAOs/nGLbL2N8QWazk9G K3Czo7AyEUnk29s2CLbhK+afzk6aRoJzcUisSAkuqug5sGkCNSGKrdE8K I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ah4FAIZCMlOtJXHA/2dsb2JhbABZgkJEO1EGwnuBGxZ0giUBAgQdXBIBCBEDAQIoORQJCAIEAQ0FCYdwCAXPUheOXREHCYQvBJhNgTKRAIMugis
X-IronPort-AV: E=Sophos;i="4.97,733,1389744000";  d="scan'208,217";a="312701966"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-1.cisco.com with ESMTP; 26 Mar 2014 03:00:16 +0000
Received: from xhc-rcd-x14.cisco.com (xhc-rcd-x14.cisco.com [173.37.183.88]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id s2Q30FYn026160 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 26 Mar 2014 03:00:15 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.194]) by xhc-rcd-x14.cisco.com ([173.37.183.88]) with mapi id 14.03.0123.003; Tue, 25 Mar 2014 22:00:15 -0500
From: "David Hanes (dhanes)" <dhanes@cisco.com>
To: "Flemming Andreasen (fandreas)" <fandreas@cisco.com>, mmusic <mmusic@ietf.org>
Thread-Topic: [MMUSIC] WGLC for draft-ietf-mmusic-udptl-dtls-06
Thread-Index: AQHPSGhCJtYrpraNHUaC5zJp3AGN9JryvvaA
Date: Wed, 26 Mar 2014 03:00:14 +0000
Message-ID: <CF576335.19A58%dhanes@cisco.com>
In-Reply-To: <5331E601.8070605@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.8.130913
x-originating-ip: [10.117.39.196]
Content-Type: multipart/alternative; boundary="_000_CF57633519A58dhanesciscocom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/DkgKUlBoEQJ_1N__Hd7LtukjxnM
Cc: "draft-ietf-mmusic-udptl-dtls@tools.ietf.org" <draft-ietf-mmusic-udptl-dtls@tools.ietf.org>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-udptl-dtls-06
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: Wed, 26 Mar 2014 03:00:20 -0000

--_000_CF57633519A58dhanesciscocom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I provided earlier comments on this draft and went ahead and reviewed it ag=
ain. I do not have any additional comments and I fully support this draft m=
oving forward as a proposed standard.

-David



From: "Flemming Andreasen (fandreas)" <fandreas@cisco.com<mailto:fandreas@c=
isco.com>>
Date: Tuesday, March 25, 2014 at 4:24 PM
To: mmusic <mmusic@ietf.org<mailto:mmusic@ietf.org>>
Cc: "draft-ietf-mmusic-udptl-dtls@tools.ietf.org<mailto:draft-ietf-mmusic-u=
dptl-dtls@tools.ietf.org>" <draft-ietf-mmusic-udptl-dtls@tools.ietf.org<mai=
lto:draft-ietf-mmusic-udptl-dtls@tools.ietf.org>>
Subject: [MMUSIC] WGLC for draft-ietf-mmusic-udptl-dtls-06

This is to announce a 2 week Working Group Last Call for

    draft-ietf-mmusic-udptl-dtls-06

as Proposed Standard. Please review and provide any comments you may have o=
n the document by April 8, 2014. Comments should be sent to the document au=
thors and the MMUSIC WG list. If you review the document but do not have an=
y comments, please send a note to that effect as well.


Thanks

       Flemming



Draft info:

This draft is a work item of the Multiparty Multimedia Session Control Work=
ing Group of the IETF.

        Title           : UDP Transport Layer (UDPTL) over Datagram Transpo=
rt Layer Security (DTLS)
        Authors         : Christer Holmberg
                          Ivo Sedlacek
                          Gonzalo Salgueiro
        Filename        : draft-ietf-mmusic-udptl-dtls-06.txt
        Pages           : 23
        Date            : 2014-03-25

Abstract:
   This document specifies how the UDP Transport Layer (UDPTL) protocol,
   the predominant transport protocol for T.38 fax, can be transported
   over the Datagram Transport Layer Security (DTLS) protocol, how the
   usage of UDPTL over DTLS is indicated in the Session Description
   Protocol (SDP), and how UDPTL over DTLS is negotiated in a session
   established using the Session Initiation Protocol (SIP).


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-mmusic-udptl-dtls/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-mmusic-udptl-dtls-06

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mmusic-udptl-dtls-06


Please note that it may take a couple of minutes from the time of submissio=
n
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


--_000_CF57633519A58dhanesciscocom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <7A5A13E1122D89479B5B0C01366A8648@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif;">
<div>I provided earlier comments on this draft and went ahead and reviewed =
it again. I do not have any additional comments and I fully support this dr=
aft moving forward as a proposed standard.</div>
<div><br>
</div>
<div>-David</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div style=3D"font-family:Calibri; font-size:11pt; text-align:left; color:b=
lack; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM:=
 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid;=
 BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style=3D"font-weight:bold">From: </span>&quot;Flemming Andreasen (fan=
dreas)&quot; &lt;<a href=3D"mailto:fandreas@cisco.com">fandreas@cisco.com</=
a>&gt;<br>
<span style=3D"font-weight:bold">Date: </span>Tuesday, March 25, 2014 at 4:=
24 PM<br>
<span style=3D"font-weight:bold">To: </span>mmusic &lt;<a href=3D"mailto:mm=
usic@ietf.org">mmusic@ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Cc: </span>&quot;<a href=3D"mailto:draft-i=
etf-mmusic-udptl-dtls@tools.ietf.org">draft-ietf-mmusic-udptl-dtls@tools.ie=
tf.org</a>&quot; &lt;<a href=3D"mailto:draft-ietf-mmusic-udptl-dtls@tools.i=
etf.org">draft-ietf-mmusic-udptl-dtls@tools.ietf.org</a>&gt;<br>
<span style=3D"font-weight:bold">Subject: </span>[MMUSIC] WGLC for draft-ie=
tf-mmusic-udptl-dtls-06<br>
</div>
<div><br>
</div>
<div>
<div bgcolor=3D"#FFFFFF" text=3D"#000000">This is to announce a 2 week Work=
ing Group Last Call for<br>
&nbsp;&nbsp;&nbsp; <br>
&nbsp;&nbsp;&nbsp; draft-ietf-mmusic-udptl-dtls-06<br>
&nbsp;&nbsp;&nbsp; <br>
as Proposed Standard. Please review and provide any comments you may have o=
n the document by April 8, 2014. Comments should be sent to the document au=
thors and the MMUSIC WG list. If you review the document but do not have an=
y comments, please send a note to
 that effect as well. <br>
<br>
<span class=3D"Apple-style-span" style=3D"border-collapse: separate;
      color: rgb(0, 0, 0); font-family: Arial; font-size: medium;
      font-style: normal; font-variant: normal; font-weight: normal;
      letter-spacing: normal; line-height: normal; orphans: 2;
      text-indent: 0px; text-transform: none; white-space: normal;
      widows: 2; word-spacing: 0px;"><span class=3D"Apple-style-span" style=
=3D"border-collapse: separate; color: rgb(0, 0, 0);
        font-family: Arial; font-size: medium; font-style: normal;
        font-variant: normal; font-weight: normal; letter-spacing:
        normal; line-height: normal; orphans: 2; text-indent: 0px;
        text-transform: none; white-space: normal; widows: 2;
        word-spacing: 0px;"><span class=3D"Apple-style-span" style=3D"borde=
r-collapse: separate; color: rgb(0, 0, 0);
          font-family: Arial; font-size: medium; font-style: normal;
          font-variant: normal; font-weight: normal; letter-spacing:
          normal; line-height: normal; orphans: 2; text-indent: 0px;
          text-transform: none; white-space: normal; widows: 2;
          word-spacing: 0px;"><span class=3D"Apple-style-span" style=3D"bor=
der-collapse: separate; color: rgb(0, 0, 0);
            font-family: Arial; font-size: medium; font-style: normal;
            font-variant: normal; font-weight: normal; letter-spacing:
            normal; line-height: normal; orphans: 2; text-indent: 0px;
            text-transform: none; white-space: normal; widows: 2;
            word-spacing: 0px;"><span class=3D"Apple-style-span" style=3D"b=
order-collapse: separate; color: rgb(0, 0, 0);
              font-family: Arial; font-size: medium; font-style: normal;
              font-variant: normal; font-weight: normal; letter-spacing:
              normal; line-height: normal; orphans: 2; text-indent: 0px;
              text-transform: none; white-space: normal; widows: 2;
              word-spacing: 0px;"><span class=3D"Apple-style-span" style=3D=
"border-collapse: separate; color: rgb(0, 0, 0);
                font-family: Arial; font-size: medium; font-style:
                normal; font-variant: normal; font-weight: normal;
                letter-spacing: normal; line-height: normal; orphans: 2;
                text-indent: 0px; text-transform: none; white-space:
                normal; widows: 2; word-spacing: 0px;"><span class=3D"Apple=
-style-span" style=3D"border-collapse:
                  separate; color: rgb(0, 0, 0); font-family: Arial;
                  font-size: medium; font-style: normal; font-variant:
                  normal; font-weight: normal; letter-spacing: normal;
                  line-height: normal; orphans: 2; text-indent: 0px;
                  text-transform: none; white-space: normal; widows: 2;
                  word-spacing: 0px;"><span class=3D"Apple-style-span" styl=
e=3D"border-collapse: separate; color: rgb(0, 0,
                    0); font-family: Arial; font-size: medium;
                    font-style: normal; font-variant: normal;
                    font-weight: normal; letter-spacing: normal;
                    line-height: normal; orphans: 2; text-indent: 0px;
                    text-transform: none; white-space: normal; widows:
                    2; word-spacing: 0px;"><span class=3D"Apple-style-span"=
 style=3D"border-collapse:
                      separate; color: rgb(0, 0, 0); font-family: Arial;
                      font-size: medium; font-style: normal;
                      font-variant: normal; font-weight: normal;
                      letter-spacing: normal; line-height: normal;
                      orphans: 2; text-indent: 0px; text-transform:
                      none; white-space: normal; widows: 2;
                      word-spacing: 0px;"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0,
                        0, 0); font-family: Arial; font-size: medium;
                        font-style: normal; font-variant: normal;
                        font-weight: normal; letter-spacing: normal;
                        line-height: normal; orphans: 2; text-indent:
                        0px; text-transform: none; white-space: normal;
                        widows: 2; word-spacing: 0px;"><span class=3D"Apple=
-style-span" style=3D"border-collapse: separate; color:
                          rgb(0, 0, 0); font-family: Arial; font-size:
                          medium; font-style: normal; font-variant:
                          normal; font-weight: normal; letter-spacing:
                          normal; line-height: normal; orphans: 2;
                          text-indent: 0px; text-transform: none;
                          white-space: normal; widows: 2; word-spacing:
                          0px;"><span class=3D"Apple-style-span" style=3D"b=
order-collapse: separate; color:
                            rgb(0, 0, 0); font-family: Arial; font-size:
                            medium; font-style: normal; font-variant:
                            normal; font-weight: normal; letter-spacing:
                            normal; line-height: normal; orphans: 2;
                            text-indent: 0px; text-transform: none;
                            white-space: normal; widows: 2;
                            word-spacing: 0px;"><span class=3D"Apple-style-=
span" style=3D"border-collapse: separate; color:
                              rgb(0, 0, 0); font-family: Arial;
                              font-size: medium; font-style: normal;
                              font-variant: normal; font-weight: normal;
                              letter-spacing: normal; line-height:
                              normal; orphans: 2; text-indent: 0px;
                              text-transform: none; white-space: normal;
                              widows: 2; word-spacing: 0px;"><span class=3D=
"Apple-style-span" style=3D"border-collapse: separate; color:
                                rgb(0, 0, 0); font-family: Arial;
                                font-size: medium; font-style: normal;
                                font-variant: normal; font-weight:
                                normal; letter-spacing: normal;
                                line-height: normal; orphans: 2;
                                text-indent: 0px; text-transform: none;
                                white-space: normal; widows: 2;
                                word-spacing: 0px;"><br>
Thanks <br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Flemming<br>
<br>
<br>
<br>
Draft info:<br>
</span></span></span></span></span></span></span></span></span></span></spa=
n></span></span></span>
<pre wrap=3D"">This draft is a work item of the Multiparty Multimedia Sessi=
on Control Working Group of the IETF.

        Title           : UDP Transport Layer (UDPTL) over Datagram Transpo=
rt Layer Security (DTLS)
        Authors         : Christer Holmberg
                          Ivo Sedlacek
                          Gonzalo Salgueiro
	Filename        : draft-ietf-mmusic-udptl-dtls-06.txt
	Pages           : 23
	Date            : 2014-03-25

Abstract:
   This document specifies how the UDP Transport Layer (UDPTL) protocol,
   the predominant transport protocol for T.38 fax, can be transported
   over the Datagram Transport Layer Security (DTLS) protocol, how the
   usage of UDPTL over DTLS is indicated in the Session Description
   Protocol (SDP), and how UDPTL over DTLS is negotiated in a session
   established using the Session Initiation Protocol (SIP).


The IETF datatracker status page for this draft is:
<a class=3D"moz-txt-link-freetext" href=3D"https://datatracker.ietf.org/doc=
/draft-ietf-mmusic-udptl-dtls/">https://datatracker.ietf.org/doc/draft-ietf=
-mmusic-udptl-dtls/</a>

There's also a htmlized version available at:
<a class=3D"moz-txt-link-freetext" href=3D"http://tools.ietf.org/html/draft=
-ietf-mmusic-udptl-dtls-06">http://tools.ietf.org/html/draft-ietf-mmusic-ud=
ptl-dtls-06</a>

A diff from the previous version is available at:
<a class=3D"moz-txt-link-freetext" href=3D"http://www.ietf.org/rfcdiff?url2=
=3Ddraft-ietf-mmusic-udptl-dtls-06">http://www.ietf.org/rfcdiff?url2=3Ddraf=
t-ietf-mmusic-udptl-dtls-06</a>


Please note that it may take a couple of minutes from the time of submissio=
n
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
<a class=3D"moz-txt-link-freetext" href=3D"ftp://ftp.ietf.org/internet-draf=
ts/">ftp://ftp.ietf.org/internet-drafts/</a></pre>
<br>
</div>
</div>
</span>
</body>
</html>

--_000_CF57633519A58dhanesciscocom_--


From nobody Tue Mar 25 22:52:53 2014
Return-Path: <emcho@sip-communicator.org>
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 6406B1A021B for <mmusic@ietfa.amsl.com>; Tue, 25 Mar 2014 22:52:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 Oq6paqiY05Mk for <mmusic@ietfa.amsl.com>; Tue, 25 Mar 2014 22:52:51 -0700 (PDT)
Received: from mail-ve0-f177.google.com (mail-ve0-f177.google.com [209.85.128.177]) by ietfa.amsl.com (Postfix) with ESMTP id 281B91A00F1 for <mmusic@ietf.org>; Tue, 25 Mar 2014 22:52:50 -0700 (PDT)
Received: by mail-ve0-f177.google.com with SMTP id sa20so1743713veb.8 for <mmusic@ietf.org>; Tue, 25 Mar 2014 22:52:49 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=h/5kbtN02I8UW8q2ND6P8E8RPaLxlyuV2fiO+4WjWkA=; b=mxUSII2bDoIOFHFPgyGytmcGr0NWVbzngNLJssfo9pm/GyQ8oeR26lMUu944cyzPob 8BBcX/K29TQkmj5QXjwFKKPwm38IMKV/KGZ6OK18BpHKy3KvkZZ2UlCoPggmpOg4JWJq S2EOIh05tnC6wBtOvUB7hgBG/ecNsnoN37G3/W2gHvoq4BG+JKo1GupHIkgJcwifXoc6 w1gP+Lg90Sa118naT3BN6f11KrKRC2DhSmg3+99Lhbu+/IEdXTedlGjmAYgWInrXn/FH LoI1yFDKcd45HoVx3B5VI0kSutEhmcOEpu+VRugOuNKiJ28kF+v+hsDwYgfQmbXemrL5 hrzQ==
X-Gm-Message-State: ALoCoQlEi0vE1pR3tYJ+ZmDs3zKYQ1pIMBpk39tXw/EpwjFu0b3dpRvnjG5k0spgFkzM8Rx648gt
X-Received: by 10.59.7.102 with SMTP id db6mr3772297ved.17.1395813169480; Tue, 25 Mar 2014 22:52:49 -0700 (PDT)
Received: from mail-vc0-f179.google.com (mail-vc0-f179.google.com [209.85.220.179]) by mx.google.com with ESMTPSA id bh12sm2437871vdd.16.2014.03.25.22.52.48 for <mmusic@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 25 Mar 2014 22:52:48 -0700 (PDT)
Received: by mail-vc0-f179.google.com with SMTP id ij19so1809449vcb.24 for <mmusic@ietf.org>; Tue, 25 Mar 2014 22:52:48 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.220.104.210 with SMTP id q18mr49849268vco.9.1395813168484; Tue, 25 Mar 2014 22:52:48 -0700 (PDT)
Received: by 10.220.191.130 with HTTP; Tue, 25 Mar 2014 22:52:48 -0700 (PDT)
Received: by 10.220.191.130 with HTTP; Tue, 25 Mar 2014 22:52:48 -0700 (PDT)
In-Reply-To: <01b701cf4893$afbf0e80$0f3d2b80$@co.in>
References: <01e601cf423c$57255890$057009b0$@co.in> <00c901cf4687$0a48dbb0$1eda9310$@co.in> <CAPvvaaKW+vxhJFqUPRZ-YfPQ4dHOS-=YwZaW+=NS3DttaaXD=Q@mail.gmail.com> <532F216E.7090400@alum.mit.edu> <532F2D8C.2010104@jitsi.org> <01b701cf4893$afbf0e80$0f3d2b80$@co.in>
Date: Wed, 26 Mar 2014 06:52:48 +0100
Message-ID: <CAPvvaaKCxnU=-SAefSDOkwms=Y=g9VoBpq57UPCqvGvYxV1VNw@mail.gmail.com>
From: Emil Ivov <emcho@jitsi.org>
To: Parthasarathi R <partha@parthasarathi.co.in>
Content-Type: multipart/alternative; boundary=047d7b3436bc14ad8304f57c14eb
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/nzC8U6KtuC73nU_3KzvSYyVKY7M
Cc: mmusic <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Comment on SIP Trickle ICE based on INFO draft
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: Wed, 26 Mar 2014 05:52:53 -0000

--047d7b3436bc14ad8304f57c14eb
Content-Type: text/plain; charset=ISO-8859-1

On 26 Mar 2014 2:35 AM, "Parthasarathi R" <partha@parthasarathi.co.in>
wrote:
>
> Hi Emil,
>
> <snip> > OK, I see. Then the easiest way to tackle this would be to
mandate
> that
> > all INFOs contain the ICE ufrag and pwd of the offer/answer they are
> > pertaining to.
> >
> > Does anyone see a problem with that?
> </snip>
>
> I guess that your intention is to pass the corresponding Origin ("o") line
> in each INFO message by which INFO will be identified for the
corresponding
> SDP by which the ICE candidates are passed.

No, that wasn't my intention but sending the origin line would also work
indeed. Thanks for pointing it out!

We could actually make that a requirement of the sdpfrag format.

--sent from my mobile

> I'm saying so as there is no
> purpose of passing ICE ufrag & pwd in each INFO message
>
> Thanks
> Partha
>
>
> > -----Original Message-----
> > From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Emil Ivov
> > Sent: Monday, March 24, 2014 12:23 AM
> > To: Paul Kyzivat; mmusic@ietf.org
> > Subject: Re: [MMUSIC] Comment on SIP Trickle ICE based on INFO draft
> >
> >
> >
> > On 23.03.14, 19:01, Paul Kyzivat wrote:
> > > One comment
> > >
> > > On 3/23/14 7:54 AM, Emil Ivov wrote:
> > >
> > >> This is analogous to an UPDATE that is received before regular 5245
> > ICE
> > >> processing has completed.
> > >>
> > >>  > >     a) INVITE from local
> > >>  > >     b) 183 session progress from remote
> > >>  > >     c) PRACK from local
> > >>  > >     d) INFO from local (relay candidates)
> > >>  > >     e) UPDATE from remote
> > >>  > >
> > >>  > > Here, the remote has to consider whether INFO belongs to UPDATE
> > or
> > >>  > > INVITE as
> > >>  > > it is possible for INFO to reach before 200 OK for UPDATE as
> > well in
> > >>  > > the
> > >>  > > same sequence.
> > >>
> > >> And CSeq headers wouldn't help here because ....?
> > >
> > > IIUC, the question is whether the remote can tell whether the INFO
> > was
> > > sent before or after receiving the UPDATE.
> > >
> > > CSeq values are independent in each direction. So they are useless to
> > > answer this question. Something else will be needed.
> >
> > OK, I see. Then the easiest way to tackle this would be to mandate that
> > all INFOs contain the ICE ufrag and pwd of the offer/answer they are
> > pertaining to.
> >
> > Does anyone see a problem with that?
> >
> > Emil
> >
> > --
> > https://jitsi.org
> >
> > _______________________________________________
> > mmusic mailing list
> > mmusic@ietf.org
> > https://www.ietf.org/mailman/listinfo/mmusic
>

--047d7b3436bc14ad8304f57c14eb
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr"><br>
On 26 Mar 2014 2:35 AM, &quot;Parthasarathi R&quot; &lt;<a href=3D"mailto:p=
artha@parthasarathi.co.in">partha@parthasarathi.co.in</a>&gt; wrote:<br>
&gt;<br>
&gt; Hi Emil,<br>
&gt;<br>
&gt; &lt;snip&gt; &gt; OK, I see. Then the easiest way to tackle this would=
 be to mandate<br>
&gt; that<br>
&gt; &gt; all INFOs contain the ICE ufrag and pwd of the offer/answer they =
are<br>
&gt; &gt; pertaining to.<br>
&gt; &gt;<br>
&gt; &gt; Does anyone see a problem with that?<br>
&gt; &lt;/snip&gt;<br>
&gt;<br>
&gt; I guess that your intention is to pass the corresponding Origin (&quot=
;o&quot;) line<br>
&gt; in each INFO message by which INFO will be identified for the correspo=
nding<br>
&gt; SDP by which the ICE candidates are passed.</p>
<p dir=3D"ltr">No, that wasn&#39;t my intention but sending the origin line=
 would also work indeed. Thanks for pointing it out!<br>
 <br>
We could actually make that a requirement of the sdpfrag format.</p>
<p dir=3D"ltr">--sent from my mobile</p>
<p dir=3D"ltr">&gt; I&#39;m saying so as there is no<br>
&gt; purpose of passing ICE ufrag &amp; pwd in each INFO message<br>
&gt;<br>
&gt; Thanks<br>
&gt; Partha<br>
&gt;<br>
&gt;<br>
&gt; &gt; -----Original Message-----<br>
&gt; &gt; From: mmusic [mailto:<a href=3D"mailto:mmusic-bounces@ietf.org">m=
music-bounces@ietf.org</a>] On Behalf Of Emil Ivov<br>
&gt; &gt; Sent: Monday, March 24, 2014 12:23 AM<br>
&gt; &gt; To: Paul Kyzivat; <a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.=
org</a><br>
&gt; &gt; Subject: Re: [MMUSIC] Comment on SIP Trickle ICE based on INFO dr=
aft<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; On 23.03.14, 19:01, Paul Kyzivat wrote:<br>
&gt; &gt; &gt; One comment<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; On 3/23/14 7:54 AM, Emil Ivov wrote:<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt;&gt; This is analogous to an UPDATE that is received before r=
egular 5245<br>
&gt; &gt; ICE<br>
&gt; &gt; &gt;&gt; processing has completed.<br>
&gt; &gt; &gt;&gt;<br>
&gt; &gt; &gt;&gt; =A0&gt; &gt; =A0 =A0 a) INVITE from local<br>
&gt; &gt; &gt;&gt; =A0&gt; &gt; =A0 =A0 b) 183 session progress from remote=
<br>
&gt; &gt; &gt;&gt; =A0&gt; &gt; =A0 =A0 c) PRACK from local<br>
&gt; &gt; &gt;&gt; =A0&gt; &gt; =A0 =A0 d) INFO from local (relay candidate=
s)<br>
&gt; &gt; &gt;&gt; =A0&gt; &gt; =A0 =A0 e) UPDATE from remote<br>
&gt; &gt; &gt;&gt; =A0&gt; &gt;<br>
&gt; &gt; &gt;&gt; =A0&gt; &gt; Here, the remote has to consider whether IN=
FO belongs to UPDATE<br>
&gt; &gt; or<br>
&gt; &gt; &gt;&gt; =A0&gt; &gt; INVITE as<br>
&gt; &gt; &gt;&gt; =A0&gt; &gt; it is possible for INFO to reach before 200=
 OK for UPDATE as<br>
&gt; &gt; well in<br>
&gt; &gt; &gt;&gt; =A0&gt; &gt; the<br>
&gt; &gt; &gt;&gt; =A0&gt; &gt; same sequence.<br>
&gt; &gt; &gt;&gt;<br>
&gt; &gt; &gt;&gt; And CSeq headers wouldn&#39;t help here because ....?<br=
>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; IIUC, the question is whether the remote can tell whether th=
e INFO<br>
&gt; &gt; was<br>
&gt; &gt; &gt; sent before or after receiving the UPDATE.<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; CSeq values are independent in each direction. So they are u=
seless to<br>
&gt; &gt; &gt; answer this question. Something else will be needed.<br>
&gt; &gt;<br>
&gt; &gt; OK, I see. Then the easiest way to tackle this would be to mandat=
e that<br>
&gt; &gt; all INFOs contain the ICE ufrag and pwd of the offer/answer they =
are<br>
&gt; &gt; pertaining to.<br>
&gt; &gt;<br>
&gt; &gt; Does anyone see a problem with that?<br>
&gt; &gt;<br>
&gt; &gt; Emil<br>
&gt; &gt;<br>
&gt; &gt; --<br>
&gt; &gt; <a href=3D"https://jitsi.org">https://jitsi.org</a><br>
&gt; &gt;<br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; mmusic mailing list<br>
&gt; &gt; <a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
&gt; &gt; <a href=3D"https://www.ietf.org/mailman/listinfo/mmusic">https://=
www.ietf.org/mailman/listinfo/mmusic</a><br>
&gt;<br>
</p>

--047d7b3436bc14ad8304f57c14eb--


From nobody Wed Mar 26 06:56:31 2014
Return-Path: <oscar.ohlsson@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 D25FD1A00FB for <mmusic@ietfa.amsl.com>; Wed, 26 Mar 2014 06:56:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 IRrtpZT3RJDw for <mmusic@ietfa.amsl.com>; Wed, 26 Mar 2014 06:56:25 -0700 (PDT)
Received: from sesbmg20.ericsson.net (sesbmg20.ericsson.net [193.180.251.56]) by ietfa.amsl.com (Postfix) with ESMTP id 7C22A1A00E3 for <mmusic@ietf.org>; Wed, 26 Mar 2014 06:56:24 -0700 (PDT)
X-AuditID: c1b4fb38-b7f418e000001099-b7-5332dc8647f0
Received: from ESESSHC019.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg20.ericsson.net (Symantec Mail Security) with SMTP id 0E.2F.04249.68CD2335; Wed, 26 Mar 2014 14:56:22 +0100 (CET)
Received: from ESESSMB301.ericsson.se ([169.254.1.249]) by ESESSHC019.ericsson.se ([153.88.183.75]) with mapi id 14.02.0387.000; Wed, 26 Mar 2014 14:56:21 +0100
From: Oscar Ohlsson <oscar.ohlsson@ericsson.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, "mmusic (E-mail)" <mmusic@ietf.org>
Thread-Topic: Draft new version: draft-ietf-mmusic-udptl-dtls-06
Thread-Index: Ac9IG4mMkcTL4w1QT1G6WY9p1Ch1lgA34Zhg
Date: Wed, 26 Mar 2014 13:56:21 +0000
Message-ID: <C643F355C8D33C48B983F1C1EA702A451295B992@ESESSMB301.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D260017@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D260017@ESESSMB209.ericsson.se>
Accept-Language: sv-SE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.18]
Content-Type: multipart/alternative; boundary="_000_C643F355C8D33C48B983F1C1EA702A451295B992ESESSMB301erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrCLMWRmVeSWpSXmKPExsUyM+JvjW7bHaNgg+vP5S3+7U2ymLr8MYsD k8eSJT+ZPL5c/swWwBTFZZOSmpNZllqkb5fAlfGk8zNjwVSNipuPFzM1MN5T7mLk5JAQMJHY dGYlO4QtJnHh3nq2LkYuDiGBI4wS9zZsYoJwljBKtH0+ygRSxSZgIHHr/kkWEFtEIFZiR08v WDezgKPE2VvbwWqEBewl+rruM0LUOEg8frUaqIYDyDaSOHQnCSTMIqAqced7J1g5r4CvxOnZ s9hAbCEg+9rdp2BxTgE/iQfTd4CtYhSQlbj//R4LxCpxiVtP5jNBHC0gsWTPeWYIW1Ti5eN/ rBC2osTHV/sYIerzJT4+aWCD2CUocXLmE5YJjKKzkIyahaRsFpIyiLiOxILdn9ggbG2JZQtf M8PYZw48ZkIWX8DIvoqRozi1OCk33chgEyMwpg5u+W2xg/HyX5tDjNIcLErivB/fOgcJCaQn lqRmp6YWpBbFF5XmpBYfYmTi4JRqYIz4URXrXSsr+6lHZLnSEqfkDW8/lk7gu1nkV3R7TtVU 9xU75Cbb9P98fm+y2A+lojrJ2zNarjC8SLjyZtuCk6FPl/5V0nVo+7daaotm98cJFQf3PTp6 ZJJ12lHm2OhJd/X5vRdc1i3Tn7V17mNno0Mhhldt602Od1Zlf1yxaulDKxNWhR+9RZeVWIoz Eg21mIuKEwElY2H1dwIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/pnw__mM2siNXZEmLHm5plXapjU8
Cc: "mmusic-chairs@tools.ietf.org" <mmusic-chairs@tools.ietf.org>
Subject: Re: [MMUSIC] Draft new version: draft-ietf-mmusic-udptl-dtls-06
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: Wed, 26 Mar 2014 13:56:28 -0000

--_000_C643F355C8D33C48B983F1C1EA702A451295B992ESESSMB301erics_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Christer,

I had a look at  the latest version of the draft (-06) and see no issues wi=
th the changes.

/Oscar


From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Christer Holmber=
g
Sent: den 25 mars 2014 12:17
To: mmusic (E-mail)
Cc: mmusic-chairs@tools.ietf.org
Subject: [MMUSIC] Draft new version: draft-ietf-mmusic-udptl-dtls-06

Hi,

Based on Flemming's comments, we've submitted a new version of the udptl-dt=
ls draft.

The changes are mainly editorial, with the biggest change being that the SD=
P O/A procedures are now structured according to RFC 3264.

Regards,

Christer

--_000_C643F355C8D33C48B983F1C1EA702A451295B992ESESSMB301erics_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"SV" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Hi Chri=
ster,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">I had a=
 look at&nbsp; the latest version of the draft (-06) and see no issues with=
 the changes.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">/Oscar =
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&qu=
ot;sans-serif&quot;"> mmusic [mailto:mmusic-bounces@ietf.org]
<b>On Behalf Of </b>Christer Holmberg<br>
<b>Sent:</b> den 25 mars 2014 12:17<br>
<b>To:</b> mmusic (E-mail)<br>
<b>Cc:</b> mmusic-chairs@tools.ietf.org<br>
<b>Subject:</b> [MMUSIC] Draft new version: draft-ietf-mmusic-udptl-dtls-06=
<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Hi,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Based on Flemming&#8217;s comme=
nts, we&#8217;ve submitted a new version of the udptl-dtls draft.<o:p></o:p=
></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">The changes are mainly editoria=
l, with the biggest change being that the SDP O/A procedures are now struct=
ured according to RFC 3264.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Regards,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Christer<o:p></o:p></span></p>
</div>
</body>
</html>

--_000_C643F355C8D33C48B983F1C1EA702A451295B992ESESSMB301erics_--


From nobody Wed Mar 26 07:31:27 2014
Return-Path: <pkyzivat@alum.mit.edu>
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 043FB1A0113 for <mmusic@ietfa.amsl.com>; Wed, 26 Mar 2014 07:31:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] 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 pKXozLOfSfRd for <mmusic@ietfa.amsl.com>; Wed, 26 Mar 2014 07:31:25 -0700 (PDT)
Received: from qmta08.westchester.pa.mail.comcast.net (qmta08.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:80]) by ietfa.amsl.com (Postfix) with ESMTP id D26701A00E3 for <mmusic@ietf.org>; Wed, 26 Mar 2014 07:31:24 -0700 (PDT)
Received: from omta01.westchester.pa.mail.comcast.net ([76.96.62.11]) by qmta08.westchester.pa.mail.comcast.net with comcast id iCqk1n0050EZKEL58EXPx5; Wed, 26 Mar 2014 14:31:23 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta01.westchester.pa.mail.comcast.net with comcast id iEXN1n00y3ZTu2S3MEXPeZ; Wed, 26 Mar 2014 14:31:23 +0000
Message-ID: <5332E4BA.40203@alum.mit.edu>
Date: Wed, 26 Mar 2014 10:31:22 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Emil Ivov <emcho@jitsi.org>, Parthasarathi R <partha@parthasarathi.co.in>
References: <01e601cf423c$57255890$057009b0$@co.in>	<00c901cf4687$0a48dbb0$1eda9310$@co.in>	<CAPvvaaKW+vxhJFqUPRZ-YfPQ4dHOS-=YwZaW+=NS3DttaaXD=Q@mail.gmail.com>	<532F216E.7090400@alum.mit.edu>	<532F2D8C.2010104@jitsi.org>	<01b701cf4893$afbf0e80$0f3d2b80$@co.in> <CAPvvaaKCxnU=-SAefSDOkwms=Y=g9VoBpq57UPCqvGvYxV1VNw@mail.gmail.com>
In-Reply-To: <CAPvvaaKCxnU=-SAefSDOkwms=Y=g9VoBpq57UPCqvGvYxV1VNw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1395844283; bh=0VSlww0/IIcGGQ380lGsyTyH8u/cYEcr3uZgklpxDk4=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=ujUfg9HjcKSLaMqwgp1nD/F7xeDcPA6UiJrEZuB+UJZ/JwmpTZ4fZ1f+fLAYb/9iX Q0ku4bCKRwQPy63rJgIiQZc3C/gP9QVbTfZd8AhLSoL2tj7CbMahB8wQ1n1lFGhwJ2 Wgyr02RSBnsbtHOgkGyaaYT4yKQR/+vDHeDzyVJd4UFO92pNm2d/P0OogDGQ8NRXqF ek9YryD7x22USrAC/AkbBhFjlSSkTAAcHrOoVJ82XDjswB6jfqJkya834LrAGPT4so u+PTEjiVz/S0gYmi/f10GjiH6JAxP1GOF1vFtNBThnfXRaS0VIfroKyi/vkaBxm/6h V7dpht3c9agvA==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/liqnjAet3NHcdtXR4iUZ47aRuBc
Cc: mmusic <mmusic@ietf.org>
Subject: Re: [MMUSIC] Comment on SIP Trickle ICE based on INFO draft
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: Wed, 26 Mar 2014 14:31:26 -0000

On 3/26/14 1:52 AM, Emil Ivov wrote:
>
> On 26 Mar 2014 2:35 AM, "Parthasarathi R" <partha@parthasarathi.co.in
> <mailto:partha@parthasarathi.co.in>> wrote:
>  >
>  > Hi Emil,
>  >
>  > <snip> > OK, I see. Then the easiest way to tackle this would be to
> mandate
>  > that
>  > > all INFOs contain the ICE ufrag and pwd of the offer/answer they are
>  > > pertaining to.
>  > >
>  > > Does anyone see a problem with that?
>  > </snip>
>  >
>  > I guess that your intention is to pass the corresponding Origin ("o")
> line
>  > in each INFO message by which INFO will be identified for the
> corresponding
>  > SDP by which the ICE candidates are passed.
>
> No, that wasn't my intention but sending the origin line would also work
> indeed. Thanks for pointing it out!
>
> We could actually make that a requirement of the sdpfrag format.

There is a conflict between such rules and defining sipfrag as a generic 
format.  As a generic format, imposing a requirement that it include an 
origin line seems unreasonable. As a requirement for using this for 
trickle ICE it makes sense.

I suggest either:
- leave sipfrag generic, impose presence of origin line as an additional
   requirement when sipfrag is used for trickle ICE
or
- define a content type that is specific to trickle ICE,
   being much more specific about what it contains, and
   with a name appropriate to that usage.

	Thanks,
	Paul


From nobody Wed Mar 26 07:42:55 2014
Return-Path: <agensler@cisco.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 D0A321A0147 for <mmusic@ietfa.amsl.com>; Wed, 26 Mar 2014 07:42:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.51
X-Spam-Level: 
X-Spam-Status: No, score=-9.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 DFkqBnjw6Ntt for <mmusic@ietfa.amsl.com>; Wed, 26 Mar 2014 07:42:49 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) by ietfa.amsl.com (Postfix) with ESMTP id 258DA1A0145 for <mmusic@ietf.org>; Wed, 26 Mar 2014 07:42:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10116; q=dns/txt; s=iport; t=1395844968; x=1397054568; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=cnmgSphu21iRgvjoR18/dua2TytQ2fcHSFbJ8aK+58g=; b=hOZe/tonbvv+kV1A5Q99NMFKka60Q/4AbgG/FuwHzr2pQUTYPf/gNkee aKsg/jKCRfT/DtRd10xPZxMs4k3g1TFI800Uo/+CI4nOa0lLXIeMZODLx rpTIc/EOmd6OAwr4xOWn2ponuAgXUslT2gRUcbeAizvmTuXcFRkuNaZpO Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ArMGABTmMlOtJXG+/2dsb2JhbABZgkJEO0sGBroBiHSBHRZ0giUBAQEEHVwQAgEIEQQBASgHMhQJCAIEDgUJh3AIBdAPF45tBAYBCYQvBJhNgTORAIMugis
X-IronPort-AV: E=Sophos; i="4.97,735,1389744000"; d="scan'208,217"; a="30520952"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by alln-iport-4.cisco.com with ESMTP; 26 Mar 2014 14:42:47 +0000
Received: from xhc-aln-x10.cisco.com (xhc-aln-x10.cisco.com [173.36.12.84]) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id s2QEgl9U028246 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <mmusic@ietf.org>; Wed, 26 Mar 2014 14:42:47 GMT
Received: from xmb-aln-x05.cisco.com ([169.254.11.185]) by xhc-aln-x10.cisco.com ([173.36.12.84]) with mapi id 14.03.0123.003; Wed, 26 Mar 2014 09:42:46 -0500
From: "Adam Gensler (agensler)" <agensler@cisco.com>
To: "Flemming Andreasen (fandreas)" <fandreas@cisco.com>
Thread-Topic: [MMUSIC] WGLC for draft-ietf-mmusic-udptl-dtls-06
Thread-Index: AQHPSGhBkGgOUI/R1UC6/eMZQzB+K5ryQK/wgAFClAA=
Date: Wed, 26 Mar 2014 14:42:46 +0000
Message-ID: <CF585DEB.488E%agensler@cisco.com>
References: <5331E601.8070605@cisco.com> <7594FB04B1934943A5C02806D1A2204B1D2610E8@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D2610E8@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.9.131030
x-originating-ip: [10.82.212.12]
Content-Type: multipart/alternative; boundary="_000_CF585DEB488Eagenslerciscocom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/ELPFffrFXl30Tq1JxHPCvdnYYM0
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-udptl-dtls-06
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: Wed, 26 Mar 2014 14:42:52 -0000

--_000_CF585DEB488Eagenslerciscocom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I've reviewed this latest draft and have no comments.

Best regards,
Adam


From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Flemming Andreas=
en
Sent: 25 March 2014 22:25
To: mmusic
Cc: draft-ietf-mmusic-udptl-dtls@tools.ietf.org<mailto:draft-ietf-mmusic-ud=
ptl-dtls@tools.ietf.org>
Subject: [MMUSIC] WGLC for draft-ietf-mmusic-udptl-dtls-06

This is to announce a 2 week Working Group Last Call for

    draft-ietf-mmusic-udptl-dtls-06

as Proposed Standard. Please review and provide any comments you may have o=
n the document by April 8, 2014. Comments should be sent to the document au=
thors and the MMUSIC WG list. If you review the document but do not have an=
y comments, please send a note to that effect as well.


Thanks

       Flemming



Draft info:


This draft is a work item of the Multiparty Multimedia Session Control Work=
ing Group of the IETF.



        Title           : UDP Transport Layer (UDPTL) over Datagram Transpo=
rt Layer Security (DTLS)

        Authors         : Christer Holmberg

                          Ivo Sedlacek

                          Gonzalo Salgueiro

        Filename        : draft-ietf-mmusic-udptl-dtls-06.txt

        Pages           : 23

        Date            : 2014-03-25



Abstract:

   This document specifies how the UDP Transport Layer (UDPTL) protocol,

   the predominant transport protocol for T.38 fax, can be transported

   over the Datagram Transport Layer Security (DTLS) protocol, how the

   usage of UDPTL over DTLS is indicated in the Session Description

   Protocol (SDP), and how UDPTL over DTLS is negotiated in a session

   established using the Session Initiation Protocol (SIP).





The IETF datatracker status page for this draft is:

https://datatracker.ietf.org/doc/draft-ietf-mmusic-udptl-dtls/



There's also a htmlized version available at:

http://tools.ietf.org/html/draft-ietf-mmusic-udptl-dtls-06



A diff from the previous version is available at:

http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mmusic-udptl-dtls-06





Please note that it may take a couple of minutes from the time of submissio=
n

until the htmlized version and diff are available at tools.ietf.org.



Internet-Drafts are also available by anonymous FTP at:

ftp://ftp.ietf.org/internet-drafts/


--_000_CF585DEB488Eagenslerciscocom_
Content-Type: text/html; charset="us-ascii"
Content-ID: <809DBAA2E0637F48A1E4C119EDBA2647@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-fami=
ly: Calibri, sans-serif;">
<div>I've reviewed this latest draft and have no comments.</div>
<div><br>
</div>
<div>Best regards,</div>
<div>Adam</div>
<div><br>
</div>
<div><br>
</div>
<span id=3D"OLK_SRC_BODY_SECTION">
<div xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micro=
soft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" x=
mlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:/=
/www.w3.org/TR/REC-html40">
<div bgcolor=3D"white" lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size: 11pt; fo=
nt-family: Calibri, sans-serif; color: windowtext;">From:</span></b><span l=
ang=3D"EN-US" style=3D"font-size: 11pt; font-family: Calibri, sans-serif; c=
olor: windowtext;"> mmusic [<a href=3D"mailto:mmusic-bounces@ietf.org">mail=
to:mmusic-bounces@ietf.org</a>]
<b>On Behalf Of </b>Flemming Andreasen<br>
<b>Sent:</b> 25 March 2014 22:25<br>
<b>To:</b> mmusic<br>
<b>Cc:</b> <a href=3D"mailto:draft-ietf-mmusic-udptl-dtls@tools.ietf.org">d=
raft-ietf-mmusic-udptl-dtls@tools.ietf.org</a><br>
<b>Subject:</b> [MMUSIC] WGLC for draft-ietf-mmusic-udptl-dtls-06<o:p></o:p=
></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">This is to announce a 2 week Working Group Last Call=
 for<br>
&nbsp;&nbsp;&nbsp; <br>
&nbsp;&nbsp;&nbsp; draft-ietf-mmusic-udptl-dtls-06<br>
&nbsp;&nbsp;&nbsp; <br>
as Proposed Standard. Please review and provide any comments you may have o=
n the document by April 8, 2014. Comments should be sent to the document au=
thors and the MMUSIC WG list. If you review the document but do not have an=
y comments, please send a note to
 that effect as well. <br>
<br>
<span style=3D"font-size: 13.5pt; font-family: Arial, sans-serif;"><br>
<span class=3D"apple-style-span">Thanks </span><br>
<br>
<span class=3D"apple-style-span">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Flemm=
ing</span><br>
<br>
<br>
<br>
<span class=3D"apple-style-span">Draft info:</span><br>
<br>
</span><o:p></o:p></p>
<pre>This draft is a work item of the Multiparty Multimedia Session Control=
 Working Group of the IETF.<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Title&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : UDP Transport Layer (UDPTL) over D=
atagram Transport Layer Security (DTLS)<o:p></o:p></pre>
<pre>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Authors&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp; : Christer Holmberg<o:p></o:p></pre>
<pre>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; Ivo Sedlacek<o:p></o:p></pre>
<pre>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; Gonzalo Salgueiro<o:p></o:p></pre>
<pre>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Filename&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp; : draft-ietf-mmusic-udptl-dtls-06.txt<o:p></o:p></p=
re>
<pre>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Pages&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : 23<o:p></o:p></pre>
<pre>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Date&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : 2014-03-25<o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>Abstract:<o:p></o:p></pre>
<pre>&nbsp;&nbsp; This document specifies how the UDP Transport Layer (UDPT=
L) protocol,<o:p></o:p></pre>
<pre>&nbsp;&nbsp; the predominant transport protocol for T.38 fax, can be t=
ransported<o:p></o:p></pre>
<pre>&nbsp;&nbsp; over the Datagram Transport Layer Security (DTLS) protoco=
l, how the<o:p></o:p></pre>
<pre>&nbsp;&nbsp; usage of UDPTL over DTLS is indicated in the Session Desc=
ription<o:p></o:p></pre>
<pre>&nbsp;&nbsp; Protocol (SDP), and how UDPTL over DTLS is negotiated in =
a session<o:p></o:p></pre>
<pre>&nbsp;&nbsp; established using the Session Initiation Protocol (SIP).<=
o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>The IETF datatracker status page for this draft is:<o:p></o:p></pre>
<pre><a href=3D"https://datatracker.ietf.org/doc/draft-ietf-mmusic-udptl-dt=
ls/">https://datatracker.ietf.org/doc/draft-ietf-mmusic-udptl-dtls/</a><o:p=
></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>There's also a htmlized version available at:<o:p></o:p></pre>
<pre><a href=3D"http://tools.ietf.org/html/draft-ietf-mmusic-udptl-dtls-06"=
>http://tools.ietf.org/html/draft-ietf-mmusic-udptl-dtls-06</a><o:p></o:p><=
/pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>A diff from the previous version is available at:<o:p></o:p></pre>
<pre><a href=3D"http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mmusic-udptl-=
dtls-06">http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-mmusic-udptl-dtls-06=
</a><o:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>Please note that it may take a couple of minutes from the time of subm=
ission<o:p></o:p></pre>
<pre>until the htmlized version and diff are available at tools.ietf.org.<o=
:p></o:p></pre>
<pre><o:p>&nbsp;</o:p></pre>
<pre>Internet-Drafts are also available by anonymous FTP at:<o:p></o:p></pr=
e>
<pre><a href=3D"ftp://ftp.ietf.org/internet-drafts/">ftp://ftp.ietf.org/int=
ernet-drafts/</a><o:p></o:p></pre>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</div>
</span><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
span.apple-style-span
	{mso-style-name:apple-style-span;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;
	color:black;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style>
</body>
</html>

--_000_CF585DEB488Eagenslerciscocom_--


From nobody Wed Mar 26 10:49:58 2014
Return-Path: <partha@parthasarathi.co.in>
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 2F0751A0078 for <mmusic@ietfa.amsl.com>; Wed, 26 Mar 2014 10:49:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 2DsJG2RqVqx8 for <mmusic@ietfa.amsl.com>; Wed, 26 Mar 2014 10:49:52 -0700 (PDT)
Received: from outbound.mailhostbox.com (outbound.mailhostbox.com [162.222.225.29]) by ietfa.amsl.com (Postfix) with ESMTP id 8A68A1A01CC for <mmusic@ietf.org>; Wed, 26 Mar 2014 10:49:48 -0700 (PDT)
Received: from userPC (unknown [122.167.132.183]) (Authenticated sender: partha@parthasarathi.co.in) by outbound.mailhostbox.com (Postfix) with ESMTPA id 579AB869091; Wed, 26 Mar 2014 17:49:43 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=parthasarathi.co.in; s=20120823; t=1395856187; bh=W+VnJ1zFIzMVTwiocqy97/L7SozUPBRN4+9/zv/Cktw=; h=From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type; b=U0qfip4Z5WlspNFxWxoQH+vL1rSp6sX3/eVKCgLJFXu0YqhSp6vrLgiW9FoN8/MIl cCU3mK8+M5wb+9TjknzYgqOguJmHMMdJwkR1+Qdw03Jc7c7EiibXHv0hCRttiupqbW BCfVLnVVSH7HYF2D1tRFQeEsDdMAuWn3J4a0SeUQ=
From: "Parthasarathi R" <partha@parthasarathi.co.in>
To: "'Emil Ivov'" <emcho@jitsi.org>
References: <01e601cf423c$57255890$057009b0$@co.in>	<00c901cf4687$0a48dbb0$1eda9310$@co.in>	<CAPvvaaKW+vxhJFqUPRZ-YfPQ4dHOS-=YwZaW+=NS3DttaaXD=Q@mail.gmail.com>	<532F216E.7090400@alum.mit.edu>	<532F2D8C.2010104@jitsi.org>	<01b701cf4893$afbf0e80$0f3d2b80$@co.in> <CAPvvaaKCxnU=-SAefSDOkwms=Y=g9VoBpq57UPCqvGvYxV1VNw@mail.gmail.com>
In-Reply-To: <CAPvvaaKCxnU=-SAefSDOkwms=Y=g9VoBpq57UPCqvGvYxV1VNw@mail.gmail.com>
Date: Wed, 26 Mar 2014 23:19:34 +0530
Message-ID: <010501cf491b$c44b0830$4ce11890$@co.in>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0106_01CF4949.DE034430"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac9It57zNjPRSOqbSsea180mQZmSsAAYNK3A
Content-Language: en-us
X-CTCH-RefID: str=0001.0A020205.5333133A.0220, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0
X-CTCH-VOD: Unknown
X-CTCH-Spam: Unknown
X-CTCH-Score: 0.000
X-CTCH-Rules: 
X-CTCH-Flags: 0
X-CTCH-ScoreCust: 0.000
X-CTCH-SenderID: partha@parthasarathi.co.in
X-CTCH-SenderID-TotalMessages: 1
X-CTCH-SenderID-TotalSpam: 0
X-CTCH-SenderID-TotalSuspected: 0
X-CTCH-SenderID-TotalBulk: 0
X-CTCH-SenderID-TotalConfirmed: 0
X-CTCH-SenderID-TotalRecipients: 0
X-CTCH-SenderID-TotalVirus: 0
X-CTCH-SenderID-BlueWhiteFlag: 0
X-Scanned-By: MIMEDefang 2.72 on 172.18.214.93
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/rLGn4Nsx8BUdGdLHV6kcHmjA8U4
Cc: 'mmusic' <mmusic@ietf.org>, 'Paul Kyzivat' <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] Comment on SIP Trickle ICE based on INFO draft
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: Wed, 26 Mar 2014 17:49:56 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0106_01CF4949.DE034430
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi Emil,

 

Could you please clarify your intention of sending Origin "o" line or
ICE-ufrag & ICE-pwd in this INFO & UPDATE scenario.

 

I have mentioned  "o" line by which it will be trivial for everybody to
understand that offer/answer state machine is impacted by these INFO.

 

Thanks

Partha

 

From: Emil Ivov [mailto:emcho@jitsi.org] 
Sent: Wednesday, March 26, 2014 11:23 AM
To: Parthasarathi R
Cc: Paul Kyzivat; mmusic
Subject: RE: [MMUSIC] Comment on SIP Trickle ICE based on INFO draft

 


On 26 Mar 2014 2:35 AM, "Parthasarathi R" <partha@parthasarathi.co.in>
wrote:
>
> Hi Emil,
>
> <snip> > OK, I see. Then the easiest way to tackle this would be to
mandate
> that
> > all INFOs contain the ICE ufrag and pwd of the offer/answer they are
> > pertaining to.
> >
> > Does anyone see a problem with that?
> </snip>
>
> I guess that your intention is to pass the corresponding Origin ("o") line
> in each INFO message by which INFO will be identified for the
corresponding
> SDP by which the ICE candidates are passed.

No, that wasn't my intention but sending the origin line would also work
indeed. Thanks for pointing it out!

We could actually make that a requirement of the sdpfrag format.

--sent from my mobile

> I'm saying so as there is no
> purpose of passing ICE ufrag & pwd in each INFO message
>
> Thanks
> Partha
>
>
> > -----Original Message-----
> > From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of Emil Ivov
> > Sent: Monday, March 24, 2014 12:23 AM
> > To: Paul Kyzivat; mmusic@ietf.org
> > Subject: Re: [MMUSIC] Comment on SIP Trickle ICE based on INFO draft
> >
> >
> >
> > On 23.03.14, 19:01, Paul Kyzivat wrote:
> > > One comment
> > >
> > > On 3/23/14 7:54 AM, Emil Ivov wrote:
> > >
> > >> This is analogous to an UPDATE that is received before regular 5245
> > ICE
> > >> processing has completed.
> > >>
> > >>  > >     a) INVITE from local
> > >>  > >     b) 183 session progress from remote
> > >>  > >     c) PRACK from local
> > >>  > >     d) INFO from local (relay candidates)
> > >>  > >     e) UPDATE from remote
> > >>  > >
> > >>  > > Here, the remote has to consider whether INFO belongs to UPDATE
> > or
> > >>  > > INVITE as
> > >>  > > it is possible for INFO to reach before 200 OK for UPDATE as
> > well in
> > >>  > > the
> > >>  > > same sequence.
> > >>
> > >> And CSeq headers wouldn't help here because ....?
> > >
> > > IIUC, the question is whether the remote can tell whether the INFO
> > was
> > > sent before or after receiving the UPDATE.
> > >
> > > CSeq values are independent in each direction. So they are useless to
> > > answer this question. Something else will be needed.
> >
> > OK, I see. Then the easiest way to tackle this would be to mandate that
> > all INFOs contain the ICE ufrag and pwd of the offer/answer they are
> > pertaining to.
> >
> > Does anyone see a problem with that?
> >
> > Emil
> >
> > --
> > https://jitsi.org
> >
> > _______________________________________________
> > mmusic mailing list
> > mmusic@ietf.org
> > https://www.ietf.org/mailman/listinfo/mmusic
>


------=_NextPart_000_0106_01CF4949.DE034430
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Latha;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Hi Emil,<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Could you please clarify your intention of sending Origin =
&#8220;o&#8221;
line or ICE-ufrag &amp; ICE-pwd in this INFO &amp; UPDATE =
scenario.<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>I have mentioned&nbsp; &#8220;o&#8221; line by which it =
will be
trivial for everybody to understand that offer/answer state machine is =
impacted
by these INFO.<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Thanks<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Partha<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in =
0in 4.0pt'>

<div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt =
0in 0in 0in'>

<p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Emil Ivov
[mailto:emcho@jitsi.org] <br>
<b>Sent:</b> Wednesday, March 26, 2014 11:23 AM<br>
<b>To:</b> Parthasarathi R<br>
<b>Cc:</b> Paul Kyzivat; mmusic<br>
<b>Subject:</b> RE: [MMUSIC] Comment on SIP Trickle ICE based on INFO =
draft<o:p></o:p></span></p>

</div>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p><br>
On 26 Mar 2014 2:35 AM, &quot;Parthasarathi R&quot; &lt;<a
href=3D"mailto:partha@parthasarathi.co.in">partha@parthasarathi.co.in</a>=
&gt;
wrote:<br>
&gt;<br>
&gt; Hi Emil,<br>
&gt;<br>
&gt; &lt;snip&gt; &gt; OK, I see. Then the easiest way to tackle this =
would be
to mandate<br>
&gt; that<br>
&gt; &gt; all INFOs contain the ICE ufrag and pwd of the offer/answer =
they are<br>
&gt; &gt; pertaining to.<br>
&gt; &gt;<br>
&gt; &gt; Does anyone see a problem with that?<br>
&gt; &lt;/snip&gt;<br>
&gt;<br>
&gt; I guess that your intention is to pass the corresponding Origin
(&quot;o&quot;) line<br>
&gt; in each INFO message by which INFO will be identified for the
corresponding<br>
&gt; SDP by which the ICE candidates are passed.<o:p></o:p></p>

<p>No, that wasn't my intention but sending the origin line would also =
work
indeed. Thanks for pointing it out!<br>
<br>
We could actually make that a requirement of the sdpfrag =
format.<o:p></o:p></p>

<p>--sent from my mobile<o:p></o:p></p>

<p>&gt; I'm saying so as there is no<br>
&gt; purpose of passing ICE ufrag &amp; pwd in each INFO message<br>
&gt;<br>
&gt; Thanks<br>
&gt; Partha<br>
&gt;<br>
&gt;<br>
&gt; &gt; -----Original Message-----<br>
&gt; &gt; From: mmusic [mailto:<a =
href=3D"mailto:mmusic-bounces@ietf.org">mmusic-bounces@ietf.org</a>]
On Behalf Of Emil Ivov<br>
&gt; &gt; Sent: Monday, March 24, 2014 12:23 AM<br>
&gt; &gt; To: Paul Kyzivat; <a =
href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
&gt; &gt; Subject: Re: [MMUSIC] Comment on SIP Trickle ICE based on INFO =
draft<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; On 23.03.14, 19:01, Paul Kyzivat wrote:<br>
&gt; &gt; &gt; One comment<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; On 3/23/14 7:54 AM, Emil Ivov wrote:<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt;&gt; This is analogous to an UPDATE that is received =
before
regular 5245<br>
&gt; &gt; ICE<br>
&gt; &gt; &gt;&gt; processing has completed.<br>
&gt; &gt; &gt;&gt;<br>
&gt; &gt; &gt;&gt; &nbsp;&gt; &gt; &nbsp; &nbsp; a) INVITE from =
local<br>
&gt; &gt; &gt;&gt; &nbsp;&gt; &gt; &nbsp; &nbsp; b) 183 session progress =
from
remote<br>
&gt; &gt; &gt;&gt; &nbsp;&gt; &gt; &nbsp; &nbsp; c) PRACK from local<br>
&gt; &gt; &gt;&gt; &nbsp;&gt; &gt; &nbsp; &nbsp; d) INFO from local =
(relay
candidates)<br>
&gt; &gt; &gt;&gt; &nbsp;&gt; &gt; &nbsp; &nbsp; e) UPDATE from =
remote<br>
&gt; &gt; &gt;&gt; &nbsp;&gt; &gt;<br>
&gt; &gt; &gt;&gt; &nbsp;&gt; &gt; Here, the remote has to consider =
whether
INFO belongs to UPDATE<br>
&gt; &gt; or<br>
&gt; &gt; &gt;&gt; &nbsp;&gt; &gt; INVITE as<br>
&gt; &gt; &gt;&gt; &nbsp;&gt; &gt; it is possible for INFO to reach =
before 200
OK for UPDATE as<br>
&gt; &gt; well in<br>
&gt; &gt; &gt;&gt; &nbsp;&gt; &gt; the<br>
&gt; &gt; &gt;&gt; &nbsp;&gt; &gt; same sequence.<br>
&gt; &gt; &gt;&gt;<br>
&gt; &gt; &gt;&gt; And CSeq headers wouldn't help here because ....?<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; IIUC, the question is whether the remote can tell whether =
the
INFO<br>
&gt; &gt; was<br>
&gt; &gt; &gt; sent before or after receiving the UPDATE.<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; CSeq values are independent in each direction. So they =
are
useless to<br>
&gt; &gt; &gt; answer this question. Something else will be needed.<br>
&gt; &gt;<br>
&gt; &gt; OK, I see. Then the easiest way to tackle this would be to =
mandate
that<br>
&gt; &gt; all INFOs contain the ICE ufrag and pwd of the offer/answer =
they are<br>
&gt; &gt; pertaining to.<br>
&gt; &gt;<br>
&gt; &gt; Does anyone see a problem with that?<br>
&gt; &gt;<br>
&gt; &gt; Emil<br>
&gt; &gt;<br>
&gt; &gt; --<br>
&gt; &gt; <a href=3D"https://jitsi.org">https://jitsi.org</a><br>
&gt; &gt;<br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; mmusic mailing list<br>
&gt; &gt; <a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
&gt; &gt; <a =
href=3D"https://www.ietf.org/mailman/listinfo/mmusic">https://www.ietf.or=
g/mailman/listinfo/mmusic</a><br>
&gt;<o:p></o:p></p>

</div>

</div>

</body>

</html>

------=_NextPart_000_0106_01CF4949.DE034430--


From nobody Wed Mar 26 11:45:02 2014
Return-Path: <partha@parthasarathi.co.in>
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 D78D61A0386 for <mmusic@ietfa.amsl.com>; Wed, 26 Mar 2014 11:44:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 fxubSG7e-GHl for <mmusic@ietfa.amsl.com>; Wed, 26 Mar 2014 11:44:52 -0700 (PDT)
Received: from outbound.mailhostbox.com (outbound.mailhostbox.com [162.222.225.18]) by ietfa.amsl.com (Postfix) with ESMTP id 183A11A03A0 for <mmusic@ietf.org>; Wed, 26 Mar 2014 11:44:51 -0700 (PDT)
Received: from userPC (unknown [122.167.132.183]) (Authenticated sender: partha@parthasarathi.co.in) by outbound.mailhostbox.com (Postfix) with ESMTPA id 6BD2E638F31; Wed, 26 Mar 2014 18:44:45 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=parthasarathi.co.in; s=20120823; t=1395859491; bh=fNzYZNxiFLM/1d14/aAJR20y0FBEJQLmzSn5lHm7HDc=; h=From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type; b=mkBjmpzKG09NNxMZ570KJLf1/pUaVYZBpiZVF9fFL7oDDZIXz46Uu4bmDv3ySBVvA u9KIM+fIS0Cip1IlAPepdwDPGhCgOXsON06O0bMa+m/+SR7Yy9zBPhfTBHhzRpAmfP mCwYfE6TzBgb0fczNng3nfKhZDOzmf8y6IB73nYM=
From: "Parthasarathi R" <partha@parthasarathi.co.in>
To: "'Emil Ivov'" <emcho@jitsi.org>
References: <01e601cf423c$57255890$057009b0$@co.in>	<00c901cf4687$0a48dbb0$1eda9310$@co.in> <CAPvvaaKW+vxhJFqUPRZ-YfPQ4dHOS-=YwZaW+=NS3DttaaXD=Q@mail.gmail.com>
In-Reply-To: <CAPvvaaKW+vxhJFqUPRZ-YfPQ4dHOS-=YwZaW+=NS3DttaaXD=Q@mail.gmail.com>
Date: Thu, 27 Mar 2014 00:14:38 +0530
Message-ID: <013601cf4923$754b35e0$5fe1a1a0$@co.in>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0137_01CF4951.8F0371E0"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac9GjqXrfrWkqld3Q5K37pjTPWysEQCjTavQ
Content-Language: en-us
X-CTCH-RefID: str=0001.0A020208.53332022.0101, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0
X-CTCH-VOD: Unknown
X-CTCH-Spam: Unknown
X-CTCH-Score: 0.000
X-CTCH-Rules: 
X-CTCH-Flags: 0
X-CTCH-ScoreCust: 0.000
X-CTCH-SenderID: partha@parthasarathi.co.in
X-CTCH-SenderID-TotalMessages: 1
X-CTCH-SenderID-TotalSpam: 0
X-CTCH-SenderID-TotalSuspected: 0
X-CTCH-SenderID-TotalBulk: 0
X-CTCH-SenderID-TotalConfirmed: 0
X-CTCH-SenderID-TotalRecipients: 0
X-CTCH-SenderID-TotalVirus: 0
X-CTCH-SenderID-BlueWhiteFlag: 0
X-Scanned-By: MIMEDefang 2.72 on 172.18.214.134
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/yCi7jkwkCPcceAel3t6jOkl63sg
Cc: 'mmusic' <mmusic@ietf.org>, 'Christer Holmberg' <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] Comment on SIP Trickle ICE based on INFO draft
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: Wed, 26 Mar 2014 18:44:57 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0137_01CF4951.8F0371E0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi Emil,

 

Please read inline for more comments.

 

Thanks

Partha

 

From: Emil Ivov [mailto:emcho@jitsi.org] 
Sent: Sunday, March 23, 2014 5:24 PM
To: Parthasarathi R
Cc: mmusic; Christer Holmberg; Enrico Marocco (TiLab)
Subject: RE: [MMUSIC] Comment on SIP Trickle ICE based on INFO draft

 

Hello,

On 23 Mar 2014 12:00 PM, "Parthasarathi R" <partha@parthasarathi.co.in>
wrote:
>
> Hi all,
>
> The below mentioned UPDATE overlap with INFO usecase and INFO forking
> scenario has to be clarified before adopting this draft as WG item as I'm
> not seeing any solution with INFO based mechanism.
>
> Thanks
> Partha
>
> > -----Original Message-----
> > From: mmusic [mailto:mmusic-bounces@ietf.org] On Behalf Of
> > Parthasarathi R
> > Sent: Tuesday, March 18, 2014 5:25 AM
> > To: 'Emil Ivov'; 'Enrico Marocco (TiLab)'; 'Christer Holmberg'
> > Cc: mmusic@ietf.org
> > Subject: [MMUSIC] Comment on SIP Trickle based on INFO draft
> >
> > Hi all,
> >
> > SIP Trickle INFO is projected as the back channel for collecting the
> > candidates in IETF-89 MMUSIC meeting. Unfortunately, it impacts
> > Offer/answer
> > (RFC 3264) in case one another offer/answer started before SIP trickle
> > INFO
> > is completed. 

I am still not sure why you think that and exactly what you have in mind.

<Partha> As I mentioned in the another mail thread
(http://www.ietf.org/mail-archive/web/mmusic/current/msg13267.html),
offer/answer is impacted in case SIP ICE trickle INFO has to be implemented
</Partha>

> > The race condition between second offer/answer and
> > earlier SIP
> > trickle INFO is not stated in the draft-ivov-mmusic-trickle-ice-sip.

No, indeed it hasn't but it has been mentioned in discussions many times: a
new offer answer would generally cause an ICE restart.

<Partha> INFO & UPDATE example is one of the example for this discussion.
</Partha>

> > I
> > have
> > explained those issues in
> > http://www.ietf.org/mail-archive/web/mmusic/current/msg12666.html and
> > no
> > reply from you folks.

I am sorry, I don't understand the mail you point to above. It says it
raises issues in 3264 situations but then refers to BUNDLE and UPDATEs. 

<Partha> Sorry in case BUNDLE confused the discussion. The main point is
that how 3264 offer/answer impacted by this INFO based Trickle ICE proposal.
Also, the mail thread points out the limitation in RFC 3264 to adapt Trickle
ICE. </Partha>

If the scenario below is the one you are worried about, then I'll answer
there.

> > This race condition is very much possible during
> > early
> > dialog scenarios with UPDATE.
> >
> > Could you please explain how SIP trickle ICE using INFO works for
> >
> > 1) UPDATE from remote before Trickle ICE is completed

This is analogous to an UPDATE that is received before regular 5245 ICE
processing has completed.

<Partha> No, in case UDPATE before the offer is completed, 491 response will
send out whereas it will not happen in case of INFO </Partha>

> >     a) INVITE from local
> >     b) 183 session progress from remote
> >     c) PRACK from local
> >     d) INFO from local (relay candidates)
> >     e) UPDATE from remote
> >
> > Here, the remote has to consider whether INFO belongs to UPDATE or
> > INVITE as
> > it is possible for INFO to reach before 200 OK for UPDATE as well in
> > the
> > same sequence.

And CSeq headers wouldn't help here because ....?

> > Also, RFC 2976 

which FWIW is obsoleted by RFC6086

<Partha> Thanks..I still majorly interwork with RFC 2976 implementation :-(
but please note that RFC 6086 does not change much in these SIP dialog or
session aspects. The exact snippet of RFC 6086 is as follows:

"Note that the INFO method is not used to update characteristics of a

   SIP dialog or session, but to allow the applications that use the SIP

   session to exchange information (which might update the state of

   those applications)."

 </Partha>

> > clarifies that
> >
> > " - The extensions that use the INFO message MUST NOT rely on the
> >      INFO message to do anything that effects the SIP call state or the
> >      state of related sessions."

And I don't believe that it does.

<Partha> No, it is not possible to implement this draft without impact
offer/answer state machine </Partha>

> > But SIP Trickle ICE state is depend upon the "state of related
> > sessions" as
> > UPDATE would have change the state in the remote.

I am not sure what you are saying or why it is a problem.

<Partha> By now, you would have realized that how offer/answer "o" line has
dependency in INFO trickle ICE </Partha>

> > 2) Trickle ICE INFO with serial forking

INFO requests are sent within a dialog. They will go through the prong
associated with that dialog and would not be forked.

<Partha> IOW, Trickle ICE INFO will be buffered till 18x response is
received. So, INFO has no much advantage compare to UPDATE except for the
non-reliable response scenario. Please note that INFO is not possible to be
handled 491 scenario wherein offer/answer is impacted </Partha>

> >   a) INVITE from local
> >   b) INVITE is forked by proxy to first remote destination
> >   c) 100 trying is reaching local
> >   d) INFO with Trickle ICE from local

No, this should't happen. We can't send the INFO before we have a dialog.

> >   e) INFO is forward by proxy to first remote destination
> >   f) INVITE is forked by proxy to second remote destination
> >   g) Whether INFO has to be forked?

See above.

> > It is not mentioned in the draft whether INFO has to be forked to the
> > second
> > remote destination as well. Could you please explain the expect
> > behavior for
> > this scenario.

I think the above commencts should answer your questions. We will make sure
we add those as clarifications before our next submission (hopefully as a WG
document)

Emil

> > Thanks
> > Partha
> >
> > _______________________________________________
> > mmusic mailing list
> > mmusic@ietf.org
> > https://www.ietf.org/mailman/listinfo/mmusic
>


------=_NextPart_000_0137_01CF4951.8F0371E0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Latha;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Courier New";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
.MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Hi Emil,<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Please read inline for more =
comments.<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Thanks<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Partha<o:p></o:p></span></p>

<p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in =
0in 4.0pt'>

<div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt =
0in 0in 0in'>

<p class=3DMsoNormal><b><span =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span>=
</b><span
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Emil Ivov
[mailto:emcho@jitsi.org] <br>
<b>Sent:</b> Sunday, March 23, 2014 5:24 PM<br>
<b>To:</b> Parthasarathi R<br>
<b>Cc:</b> mmusic; Christer Holmberg; Enrico Marocco (TiLab)<br>
<b>Subject:</b> RE: [MMUSIC] Comment on SIP Trickle ICE based on INFO =
draft<o:p></o:p></span></p>

</div>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p>Hello,<o:p></o:p></p>

<p>On 23 Mar 2014 12:00 PM, &quot;Parthasarathi R&quot; &lt;<a
href=3D"mailto:partha@parthasarathi.co.in">partha@parthasarathi.co.in</a>=
&gt;
wrote:<br>
&gt;<br>
&gt; Hi all,<br>
&gt;<br>
&gt; The below mentioned UPDATE overlap with INFO usecase and INFO =
forking<br>
&gt; scenario has to be clarified before adopting this draft as WG item =
as I'm<br>
&gt; not seeing any solution with INFO based mechanism.<br>
&gt;<br>
&gt; Thanks<br>
&gt; Partha<br>
&gt;<br>
&gt; &gt; -----Original Message-----<br>
&gt; &gt; From: mmusic [mailto:<a =
href=3D"mailto:mmusic-bounces@ietf.org">mmusic-bounces@ietf.org</a>]
On Behalf Of<br>
&gt; &gt; Parthasarathi R<br>
&gt; &gt; Sent: Tuesday, March 18, 2014 5:25 AM<br>
&gt; &gt; To: 'Emil Ivov'; 'Enrico Marocco (TiLab)'; 'Christer =
Holmberg'<br>
&gt; &gt; Cc: <a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
&gt; &gt; Subject: [MMUSIC] Comment on SIP Trickle based on INFO =
draft<br>
&gt; &gt;<br>
&gt; &gt; Hi all,<br>
&gt; &gt;<br>
&gt; &gt; SIP Trickle INFO is projected as the back channel for =
collecting the<br>
&gt; &gt; candidates in IETF-89 MMUSIC meeting. Unfortunately, it =
impacts<br>
&gt; &gt; Offer/answer<br>
&gt; &gt; (RFC 3264) in case one another offer/answer started before SIP
trickle<br>
&gt; &gt; INFO<br>
&gt; &gt; is completed. <o:p></o:p></p>

<p>I am still not sure why you think that and exactly what you have in =
mind.<o:p></o:p></p>

<p><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&lt;Partha&gt;
As I mentioned in the another mail thread (<a
href=3D"http://www.ietf.org/mail-archive/web/mmusic/current/msg13267.html=
">http://www.ietf.org/mail-archive/web/mmusic/current/msg13267.html</a>),=

offer/answer is impacted in case SIP ICE trickle INFO has to be =
implemented
&lt;/Partha&gt;<o:p></o:p></span></p>

<p>&gt; &gt; The race condition between second offer/answer and<br>
&gt; &gt; earlier SIP<br>
&gt; &gt; trickle INFO is not stated in the =
draft-ivov-mmusic-trickle-ice-sip.<o:p></o:p></p>

<p>No, indeed it hasn't but it has been mentioned in discussions many =
times: a
new offer answer would generally cause an ICE restart.<o:p></o:p></p>

<p><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&lt;Partha&gt;
INFO &amp; UPDATE example is one of the example for this discussion. =
&nbsp;&lt;/Partha&gt;<o:p></o:p></span></p>

<p>&gt; &gt; I<br>
&gt; &gt; have<br>
&gt; &gt; explained those issues in<br>
&gt; &gt; <a
href=3D"http://www.ietf.org/mail-archive/web/mmusic/current/msg12666.html=
">http://www.ietf.org/mail-archive/web/mmusic/current/msg12666.html</a>
and<br>
&gt; &gt; no<br>
&gt; &gt; reply from you folks.<o:p></o:p></p>

<p>I am sorry, I don't understand the mail you point to above. It says =
it
raises issues in 3264 situations but then refers to BUNDLE and UPDATEs. =
<o:p></o:p></p>

<p><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&lt;Partha&gt;
Sorry in case BUNDLE confused the discussion. The main point is that how =
3264
offer/answer impacted by this INFO based Trickle ICE proposal. Also, the =
mail
thread points out the limitation in RFC 3264 to adapt Trickle ICE. =
&lt;/Partha&gt;<o:p></o:p></span></p>

<p>If the scenario below is the one you are worried about, then I'll =
answer
there.<o:p></o:p></p>

<p>&gt; &gt; This race condition is very much possible during<br>
&gt; &gt; early<br>
&gt; &gt; dialog scenarios with UPDATE.<br>
&gt; &gt;<br>
&gt; &gt; Could you please explain how SIP trickle ICE using INFO works =
for<br>
&gt; &gt;<br>
&gt; &gt; 1) UPDATE from remote before Trickle ICE is =
completed<o:p></o:p></p>

<p>This is analogous to an UPDATE that is received before regular 5245 =
ICE
processing has completed.<o:p></o:p></p>

<p><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&lt;Partha&gt;
No, in case UDPATE before the offer is completed, 491 response will send =
out
whereas it will not happen in case of INFO =
&lt;/Partha&gt;<o:p></o:p></span></p>

<p>&gt; &gt; &nbsp; &nbsp; a) INVITE from local<br>
&gt; &gt; &nbsp; &nbsp; b) 183 session progress from remote<br>
&gt; &gt; &nbsp; &nbsp; c) PRACK from local<br>
&gt; &gt; &nbsp; &nbsp; d) INFO from local (relay candidates)<br>
&gt; &gt; &nbsp; &nbsp; e) UPDATE from remote<br>
&gt; &gt;<br>
&gt; &gt; Here, the remote has to consider whether INFO belongs to =
UPDATE or<br>
&gt; &gt; INVITE as<br>
&gt; &gt; it is possible for INFO to reach before 200 OK for UPDATE as =
well in<br>
&gt; &gt; the<br>
&gt; &gt; same sequence.<o:p></o:p></p>

<p>And CSeq headers wouldn't help here because ....?<o:p></o:p></p>

<p>&gt; &gt; Also, RFC 2976 <o:p></o:p></p>

<p>which FWIW is obsoleted by RFC6086<o:p></o:p></p>

<p><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&lt;Partha&gt;
Thanks..I still majorly interwork with RFC 2976 implementation :-( but =
please
note that RFC 6086 does not change much in these SIP dialog or session =
aspects.
The exact snippet of RFC 6086 is as follows:<o:p></o:p></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:7.5pt;page-break-before:always'><span
lang=3DEN style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&#8220;Note that the
INFO method is not used to update characteristics of =
a<o:p></o:p></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:7.5pt;page-break-before:always'><span
lang=3DEN style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp; SIP
dialog or session, but to allow the applications that use the =
SIP<o:p></o:p></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:7.5pt;page-break-before:always'><span
lang=3DEN style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp; session
to exchange information (which might update the state =
of<o:p></o:p></span></p>

<p class=3DMsoNormal =
style=3D'margin-left:7.5pt;page-break-before:always'><span
lang=3DEN style=3D'font-size:10.0pt;font-family:"Courier =
New"'>&nbsp;&nbsp; those
applications).&#8221;<o:p></o:p></span></p>

<p><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&nbsp;&lt;/Partha&gt;<o:p></o:p></span></p>

<p>&gt; &gt; clarifies that<br>
&gt; &gt;<br>
&gt; &gt; &quot; - The extensions that use the INFO message MUST NOT =
rely on
the<br>
&gt; &gt; &nbsp; &nbsp; &nbsp;INFO message to do anything that effects =
the SIP
call state or the<br>
&gt; &gt; &nbsp; &nbsp; &nbsp;state of related =
sessions.&quot;<o:p></o:p></p>

<p>And I don't believe that it does.<o:p></o:p></p>

<p><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&lt;Partha&gt;
No, it is not possible to implement this draft without impact =
offer/answer
state machine &lt;/Partha&gt;<o:p></o:p></span></p>

<p>&gt; &gt; But SIP Trickle ICE state is depend upon the &quot;state of
related<br>
&gt; &gt; sessions&quot; as<br>
&gt; &gt; UPDATE would have change the state in the =
remote.<o:p></o:p></p>

<p>I am not sure what you are saying or why it is a =
problem.<o:p></o:p></p>

<p><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&lt;Partha&gt;
By now, you would have realized that how offer/answer &#8220;o&#8221; =
line has
dependency in INFO trickle ICE &lt;/Partha&gt;<o:p></o:p></span></p>

<p>&gt; &gt; 2) Trickle ICE INFO with serial forking<o:p></o:p></p>

<p>INFO requests are sent within a dialog. They will go through the =
prong
associated with that dialog and would not be forked.<o:p></o:p></p>

<p><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>&lt;Partha&gt;
IOW, Trickle ICE INFO will be buffered till 18x response is received. =
So, INFO
has no much advantage compare to UPDATE except for the non-reliable =
response
scenario. Please note that INFO is not possible to be handled 491 =
scenario
wherein offer/answer is impacted &lt;/Partha&gt;<o:p></o:p></span></p>

<p>&gt; &gt; &nbsp; a) INVITE from local<br>
&gt; &gt; &nbsp; b) INVITE is forked by proxy to first remote =
destination<br>
&gt; &gt; &nbsp; c) 100 trying is reaching local<br>
&gt; &gt; &nbsp; d) INFO with Trickle ICE from local<o:p></o:p></p>

<p>No, this should't happen. We can't send the INFO before we have a =
dialog.<o:p></o:p></p>

<p>&gt; &gt; &nbsp; e) INFO is forward by proxy to first remote =
destination<br>
&gt; &gt; &nbsp; f) INVITE is forked by proxy to second remote =
destination<br>
&gt; &gt; &nbsp; g) Whether INFO has to be forked?<o:p></o:p></p>

<p>See above.<o:p></o:p></p>

<p>&gt; &gt; It is not mentioned in the draft whether INFO has to be =
forked to
the<br>
&gt; &gt; second<br>
&gt; &gt; remote destination as well. Could you please explain the =
expect<br>
&gt; &gt; behavior for<br>
&gt; &gt; this scenario.<o:p></o:p></p>

<p>I think the above commencts should answer your questions. We will =
make sure
we add those as clarifications before our next submission (hopefully as =
a WG
document)<o:p></o:p></p>

<p>Emil<o:p></o:p></p>

<p>&gt; &gt; Thanks<br>
&gt; &gt; Partha<br>
&gt; &gt;<br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; mmusic mailing list<br>
&gt; &gt; <a href=3D"mailto:mmusic@ietf.org">mmusic@ietf.org</a><br>
&gt; &gt; <a =
href=3D"https://www.ietf.org/mailman/listinfo/mmusic">https://www.ietf.or=
g/mailman/listinfo/mmusic</a><br>
&gt;<o:p></o:p></p>

</div>

</div>

</body>

</html>

------=_NextPart_000_0137_01CF4951.8F0371E0--


From nobody Wed Mar 26 12:07:02 2014
Return-Path: <pkyzivat@alum.mit.edu>
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 326E01A02D7 for <mmusic@ietfa.amsl.com>; Wed, 26 Mar 2014 12:07:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] 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 jyu7EyhgSWYY for <mmusic@ietfa.amsl.com>; Wed, 26 Mar 2014 12:06:57 -0700 (PDT)
Received: from qmta13.westchester.pa.mail.comcast.net (qmta13.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:243]) by ietfa.amsl.com (Postfix) with ESMTP id 056721A01AB for <mmusic@ietf.org>; Wed, 26 Mar 2014 12:06:56 -0700 (PDT)
Received: from omta04.westchester.pa.mail.comcast.net ([76.96.62.35]) by qmta13.westchester.pa.mail.comcast.net with comcast id iCKV1n0050ldTLk5DK6vGS; Wed, 26 Mar 2014 19:06:55 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta04.westchester.pa.mail.comcast.net with comcast id iK6v1n0023ZTu2S01K6vUJ; Wed, 26 Mar 2014 19:06:55 +0000
Message-ID: <5333254E.1060804@alum.mit.edu>
Date: Wed, 26 Mar 2014 15:06:54 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Parthasarathi R <partha@parthasarathi.co.in>,  'Emil Ivov' <emcho@jitsi.org>
References: <01e601cf423c$57255890$057009b0$@co.in>	<00c901cf4687$0a48dbb0$1eda9310$@co.in>	<CAPvvaaKW+vxhJFqUPRZ-YfPQ4dHOS-=YwZaW+=NS3DttaaXD=Q@mail.gmail.com>	<532F216E.7090400@alum.mit.edu>	<532F2D8C.2010104@jitsi.org>	<01b701cf4893$afbf0e80$0f3d2b80$@co.in> <CAPvvaaKCxnU=-SAefSDOkwms=Y=g9VoBpq57UPCqvGvYxV1VNw@mail.gmail.com> <010501cf491b$c44b0830$4ce11890$@co.in>
In-Reply-To: <010501cf491b$c44b0830$4ce11890$@co.in>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1395860815; bh=AsQo8K+Qoi8pSGrTjmJb9F5+Sl57MuIuX7SnGycAsXU=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=j3sAr+NiZPGVJRJvnIr6ELBD6b3rw8y1TQw0Bb2wARRa5pwOIAbq7PtXDHSJsXa9Q KypdSDoBYLB6g1XPHnJETKV2dalgEAEGbOMEQMlfYt4JUsO/z7wcVspTo38hRwd9VK BZW9/KhtC1zZ8HoWFeEkVe877x9KMNpZ8pwPTvxkx6pla7C1rQnJlHKTld1D/Bj0dA hCfdm3ko8AaZWf+h7mib6caGqtrRipf7a1K4ztRzeSFEy6MX/5G1yWovcE+hsPX7iW eCXagcSapu1gTgG6sngp64da8pcH+r7JHUki1Ib/G6GXy3O6ca5vWkGsnwf09UOiYG mmhooio/5h5UQ==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/ektww7s4C0-40LvUbwjjlHzCIpA
Cc: 'mmusic' <mmusic@ietf.org>
Subject: Re: [MMUSIC] Comment on SIP Trickle ICE based on INFO draft
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: Wed, 26 Mar 2014 19:07:00 -0000

I think it makes sense to include the o= line. It will still require 
some text to fully explain what it means and how to use it.

Note that the values of o= are also independent in the two directions, 
so (like CSeq) can't be used directly to correlate messages in opposite 
directions.

However the O/A process does correlate pairs of o=, one from each side.

What we end up with is:

- a session has a series of O/A exchanges. Each O and A contains an
   SDP. And each SDP has has an o= line.
- From that you can identify a series of SDP pairs. Viewed from one
   side each pair has one local and one remote SDP.
- the version numbers in the o= lines of the local SDPs form a
   non-decreasing sequence. The same is true for the remote SDPs.
   (But two in a sequence may have the *same* version.)

What we are talking about is for the trickle ICE SDP fragments to 
contain the o= line from the SDP most recently sent in an offer or 
answer by the sender of the fragment.

If you receive a trickle ICE fragment, then you should compare the o= 
line to that of the most recent SDP received in an offer or answer. If 
those match, and you have no unanswered offer outstanding, then all is ok.

If they differ and you have no unanswered offer outstanding, then 
something is wrong. (I haven't thought through all the possibilities here.)

If they differ and you have an unanswered outstanding offer, then it may 
be that an answer is enroute and this trickle was intended to follow it.

Note that if you have an unanswered offer outstanding, it is possible 
that the answer will be identical to the prior offer, and that the 
trickle fragment was sent after the answer. I *think* this doesn't 
matter - treating it as if it was sent first will yield the same result.

	Thanks,
	Paul

On 3/26/14 1:49 PM, Parthasarathi R wrote:
> Hi Emil,
>
> Could you please clarify your intention of sending Origin “o” line or
> ICE-ufrag & ICE-pwd in this INFO & UPDATE scenario.
>
> I have mentioned  “o” line by which it will be trivial for everybody to
> understand that offer/answer state machine is impacted by these INFO.
>
> Thanks
>
> Partha
>
> *From:*Emil Ivov [mailto:emcho@jitsi.org]
> *Sent:* Wednesday, March 26, 2014 11:23 AM
> *To:* Parthasarathi R
> *Cc:* Paul Kyzivat; mmusic
> *Subject:* RE: [MMUSIC] Comment on SIP Trickle ICE based on INFO draft
>
>
> On 26 Mar 2014 2:35 AM, "Parthasarathi R" <partha@parthasarathi.co.in
> <mailto:partha@parthasarathi.co.in>> wrote:
>  >
>  > Hi Emil,
>  >
>  > <snip> > OK, I see. Then the easiest way to tackle this would be to
> mandate
>  > that
>  > > all INFOs contain the ICE ufrag and pwd of the offer/answer they are
>  > > pertaining to.
>  > >
>  > > Does anyone see a problem with that?
>  > </snip>
>  >
>  > I guess that your intention is to pass the corresponding Origin ("o")
> line
>  > in each INFO message by which INFO will be identified for the
> corresponding
>  > SDP by which the ICE candidates are passed.
>
> No, that wasn't my intention but sending the origin line would also work
> indeed. Thanks for pointing it out!
>
> We could actually make that a requirement of the sdpfrag format.
>
> --sent from my mobile
>
>  > I'm saying so as there is no
>  > purpose of passing ICE ufrag & pwd in each INFO message
>  >
>  > Thanks
>  > Partha
>  >
>  >
>  > > -----Original Message-----
>  > > From: mmusic [mailto:mmusic-bounces@ietf.org
> <mailto:mmusic-bounces@ietf.org>] On Behalf Of Emil Ivov
>  > > Sent: Monday, March 24, 2014 12:23 AM
>  > > To: Paul Kyzivat; mmusic@ietf.org <mailto:mmusic@ietf.org>
>  > > Subject: Re: [MMUSIC] Comment on SIP Trickle ICE based on INFO draft
>  > >
>  > >
>  > >
>  > > On 23.03.14, 19:01, Paul Kyzivat wrote:
>  > > > One comment
>  > > >
>  > > > On 3/23/14 7:54 AM, Emil Ivov wrote:
>  > > >
>  > > >> This is analogous to an UPDATE that is received before regular 5245
>  > > ICE
>  > > >> processing has completed.
>  > > >>
>  > > >>  > >     a) INVITE from local
>  > > >>  > >     b) 183 session progress from remote
>  > > >>  > >     c) PRACK from local
>  > > >>  > >     d) INFO from local (relay candidates)
>  > > >>  > >     e) UPDATE from remote
>  > > >>  > >
>  > > >>  > > Here, the remote has to consider whether INFO belongs to UPDATE
>  > > or
>  > > >>  > > INVITE as
>  > > >>  > > it is possible for INFO to reach before 200 OK for UPDATE as
>  > > well in
>  > > >>  > > the
>  > > >>  > > same sequence.
>  > > >>
>  > > >> And CSeq headers wouldn't help here because ....?
>  > > >
>  > > > IIUC, the question is whether the remote can tell whether the INFO
>  > > was
>  > > > sent before or after receiving the UPDATE.
>  > > >
>  > > > CSeq values are independent in each direction. So they are useless to
>  > > > answer this question. Something else will be needed.
>  > >
>  > > OK, I see. Then the easiest way to tackle this would be to mandate that
>  > > all INFOs contain the ICE ufrag and pwd of the offer/answer they are
>  > > pertaining to.
>  > >
>  > > Does anyone see a problem with that?
>  > >
>  > > Emil
>  > >
>  > > --
>  > > https://jitsi.org
>  > >
>  > > _______________________________________________
>  > > mmusic mailing list
>  > > mmusic@ietf.org <mailto:mmusic@ietf.org>
>  > > https://www.ietf.org/mailman/listinfo/mmusic
>  >
>


From nobody Wed Mar 26 15:46:50 2014
Return-Path: <emcho@sip-communicator.org>
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 57F741A03DC for <mmusic@ietfa.amsl.com>; Wed, 26 Mar 2014 15:46:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_16=0.6, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 Sbv6joY5Fooc for <mmusic@ietfa.amsl.com>; Wed, 26 Mar 2014 15:46:45 -0700 (PDT)
Received: from mail-wi0-f177.google.com (mail-wi0-f177.google.com [209.85.212.177]) by ietfa.amsl.com (Postfix) with ESMTP id 8EC441A03DB for <mmusic@ietf.org>; Wed, 26 Mar 2014 15:46:45 -0700 (PDT)
Received: by mail-wi0-f177.google.com with SMTP id cc10so2444374wib.16 for <mmusic@ietf.org>; Wed, 26 Mar 2014 15:46:43 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=+KEKbsJ5pIPhgYL+WgnyMW/jgo2r19dDgH4xfjIDuZ8=; b=X6tVCSKSAuuyGL/4wl9AEU9AIOmeWvtXlRXfqeJxSV08WonwLGjiI7OIX9kHogIobZ 3G7oL0PkNfibri2tbT2Km1OsHlON209tZ/3ox0zCH2kejHPW35DL9QnVUO3aNwsrvfEq YRLSrGw6P7nTOWoaV4mZjJr9mFbFcXk9w3g1kJsa19DHmkLO0FaGAOpJz/DKOri0Is84 B1OuKgFQ8nv2jWMDJGvsaAjXPGDqu8CPYyvzFPfNiKo+xrss1zaUdrrDD+BfzPlujLQ9 aU507IRB5h1S/MnYauesjCH39pPud1/cEbhYNglpFFVp3lTu3Hw8siPTwlvdu1UM8Zpv dnIQ==
X-Gm-Message-State: ALoCoQkLUQFLSR4ovp1JN1jvENNz7HCYOzeY451ejGi05u6T5W7dWarvO8+dYemMm79XvSj1wZ7s
X-Received: by 10.180.96.200 with SMTP id du8mr35542737wib.43.1395874003097; Wed, 26 Mar 2014 15:46:43 -0700 (PDT)
Received: from camionet.local (neu67-4-88-160-65-79.fbx.proxad.net. [88.160.65.79]) by mx.google.com with ESMTPSA id di9sm1251733wid.6.2014.03.26.15.46.40 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 26 Mar 2014 15:46:41 -0700 (PDT)
Message-ID: <533358CF.1080107@jitsi.org>
Date: Wed, 26 Mar 2014 23:46:39 +0100
From: Emil Ivov <emcho@jitsi.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
References: <01e601cf423c$57255890$057009b0$@co.in>	<00c901cf4687$0a48dbb0$1eda9310$@co.in>	<CAPvvaaKW+vxhJFqUPRZ-YfPQ4dHOS-=YwZaW+=NS3DttaaXD=Q@mail.gmail.com>	<532F216E.7090400@alum.mit.edu>	<532F2D8C.2010104@jitsi.org>	<01b701cf4893$afbf0e80$0f3d2b80$@co.in> <CAPvvaaKCxnU=-SAefSDOkwms=Y=g9VoBpq57UPCqvGvYxV1VNw@mail.gmail.com> <010501cf491b$c44b0830$4ce11890$@co.in> <5333254E.1060804@alum.mit.edu>
In-Reply-To: <5333254E.1060804@alum.mit.edu>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/opWlFpp0Z331m3uuY48KfHDRqRM
Cc: 'mmusic' <mmusic@ietf.org>
Subject: Re: [MMUSIC] Comment on SIP Trickle ICE based on INFO draft
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: Wed, 26 Mar 2014 22:46:48 -0000

On 26.03.14, 20:06, Paul Kyzivat wrote:
> I think it makes sense to include the o= line. It will still require
> some text to fully explain what it means and how to use it.

After reading your mail I am not so sure any more.

> Note that the values of o= are also independent in the two directions,
> so (like CSeq) can't be used directly to correlate messages in opposite
> directions.
>
> However the O/A process does correlate pairs of o=, one from each side.
>
> What we end up with is:
>
> - a session has a series of O/A exchanges. Each O and A contains an
>    SDP. And each SDP has has an o= line.
> - From that you can identify a series of SDP pairs. Viewed from one
>    side each pair has one local and one remote SDP.
> - the version numbers in the o= lines of the local SDPs form a
>    non-decreasing sequence. The same is true for the remote SDPs.
>    (But two in a sequence may have the *same* version.)
>
> What we are talking about is for the trickle ICE SDP fragments to
> contain the o= line from the SDP most recently sent in an offer or
> answer by the sender of the fragment.
>
> If you receive a trickle ICE fragment, then you should compare the o=
> line to that of the most recent SDP received in an offer or answer. If
> those match, and you have no unanswered offer outstanding, then all is ok.
>
> If they differ and you have no unanswered offer outstanding, then
> something is wrong. (I haven't thought through all the possibilities here.)
>
> If they differ and you have an unanswered outstanding offer, then it may
> be that an answer is enroute and this trickle was intended to follow it.
>
> Note that if you have an unanswered offer outstanding, it is possible
> that the answer will be identical to the prior offer, and that the
> trickle fragment was sent after the answer. I *think* this doesn't
> matter - treating it as if it was sent first will yield the same result.

This is really great insight! Thanks Paul!

It does make me wonder however if o= is the best way to handle things 
here though. For example, it hadn't occurred to me that an O/A can 
increment the o=values without having an impact on ICE processing. This 
would happen if ice-ufrag and ice-pwd remain the same.

So all this makes me think that ufrag and pwd may still be the easiest 
and most straightforward way of matching INFOs to a specific ICE context.

Thoughts?
Emil

>
>      Thanks,
>      Paul
>
> On 3/26/14 1:49 PM, Parthasarathi R wrote:
>> Hi Emil,
>>
>> Could you please clarify your intention of sending Origin “o” line or
>> ICE-ufrag & ICE-pwd in this INFO & UPDATE scenario.
>>
>> I have mentioned  “o” line by which it will be trivial for everybody to
>> understand that offer/answer state machine is impacted by these INFO.
>>
>> Thanks
>>
>> Partha
>>
>> *From:*Emil Ivov [mailto:emcho@jitsi.org]
>> *Sent:* Wednesday, March 26, 2014 11:23 AM
>> *To:* Parthasarathi R
>> *Cc:* Paul Kyzivat; mmusic
>> *Subject:* RE: [MMUSIC] Comment on SIP Trickle ICE based on INFO draft
>>
>>
>> On 26 Mar 2014 2:35 AM, "Parthasarathi R" <partha@parthasarathi.co.in
>> <mailto:partha@parthasarathi.co.in>> wrote:
>>  >
>>  > Hi Emil,
>>  >
>>  > <snip> > OK, I see. Then the easiest way to tackle this would be to
>> mandate
>>  > that
>>  > > all INFOs contain the ICE ufrag and pwd of the offer/answer they are
>>  > > pertaining to.
>>  > >
>>  > > Does anyone see a problem with that?
>>  > </snip>
>>  >
>>  > I guess that your intention is to pass the corresponding Origin ("o")
>> line
>>  > in each INFO message by which INFO will be identified for the
>> corresponding
>>  > SDP by which the ICE candidates are passed.
>>
>> No, that wasn't my intention but sending the origin line would also work
>> indeed. Thanks for pointing it out!
>>
>> We could actually make that a requirement of the sdpfrag format.
>>
>> --sent from my mobile
>>
>>  > I'm saying so as there is no
>>  > purpose of passing ICE ufrag & pwd in each INFO message
>>  >
>>  > Thanks
>>  > Partha
>>  >
>>  >
>>  > > -----Original Message-----
>>  > > From: mmusic [mailto:mmusic-bounces@ietf.org
>> <mailto:mmusic-bounces@ietf.org>] On Behalf Of Emil Ivov
>>  > > Sent: Monday, March 24, 2014 12:23 AM
>>  > > To: Paul Kyzivat; mmusic@ietf.org <mailto:mmusic@ietf.org>
>>  > > Subject: Re: [MMUSIC] Comment on SIP Trickle ICE based on INFO draft
>>  > >
>>  > >
>>  > >
>>  > > On 23.03.14, 19:01, Paul Kyzivat wrote:
>>  > > > One comment
>>  > > >
>>  > > > On 3/23/14 7:54 AM, Emil Ivov wrote:
>>  > > >
>>  > > >> This is analogous to an UPDATE that is received before regular
>> 5245
>>  > > ICE
>>  > > >> processing has completed.
>>  > > >>
>>  > > >>  > >     a) INVITE from local
>>  > > >>  > >     b) 183 session progress from remote
>>  > > >>  > >     c) PRACK from local
>>  > > >>  > >     d) INFO from local (relay candidates)
>>  > > >>  > >     e) UPDATE from remote
>>  > > >>  > >
>>  > > >>  > > Here, the remote has to consider whether INFO belongs to
>> UPDATE
>>  > > or
>>  > > >>  > > INVITE as
>>  > > >>  > > it is possible for INFO to reach before 200 OK for UPDATE as
>>  > > well in
>>  > > >>  > > the
>>  > > >>  > > same sequence.
>>  > > >>
>>  > > >> And CSeq headers wouldn't help here because ....?
>>  > > >
>>  > > > IIUC, the question is whether the remote can tell whether the INFO
>>  > > was
>>  > > > sent before or after receiving the UPDATE.
>>  > > >
>>  > > > CSeq values are independent in each direction. So they are
>> useless to
>>  > > > answer this question. Something else will be needed.
>>  > >
>>  > > OK, I see. Then the easiest way to tackle this would be to
>> mandate that
>>  > > all INFOs contain the ICE ufrag and pwd of the offer/answer they are
>>  > > pertaining to.
>>  > >
>>  > > Does anyone see a problem with that?
>>  > >
>>  > > Emil
>>  > >
>>  > > --
>>  > > https://jitsi.org
>>  > >
>>  > > _______________________________________________
>>  > > mmusic mailing list
>>  > > mmusic@ietf.org <mailto:mmusic@ietf.org>
>>  > > https://www.ietf.org/mailman/listinfo/mmusic
>>  >
>>
>

-- 
https://jitsi.org


From nobody Wed Mar 26 16:07:12 2014
Return-Path: <emcho@sip-communicator.org>
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 CDD281A03F8 for <mmusic@ietfa.amsl.com>; Wed, 26 Mar 2014 16:07:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 35EM-Smae_3Q for <mmusic@ietfa.amsl.com>; Wed, 26 Mar 2014 16:07:06 -0700 (PDT)
Received: from mail-wg0-f43.google.com (mail-wg0-f43.google.com [74.125.82.43]) by ietfa.amsl.com (Postfix) with ESMTP id 6CD831A03F7 for <mmusic@ietf.org>; Wed, 26 Mar 2014 16:07:06 -0700 (PDT)
Received: by mail-wg0-f43.google.com with SMTP id x13so1811899wgg.26 for <mmusic@ietf.org>; Wed, 26 Mar 2014 16:07:04 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=8zwrGuOm47Sk9BoQ16vonBfH8DdDkaz1dcfQt99Cdvo=; b=dEXoBoY0udbUhtdxvYomm+dcRWrm4SrCqhvAI9y/A+DzYB7t0PpVQ+u5g3D7DYuV71 HocZLviaAfNJn3g1pIGNG+F2k/zwOSNgF4LSpWy2WSeb1OSLfePX3wZrebxjWdc6m5A5 Q+nxkuXc3zeX/85+KiyyoIB5+eg9jmqGWgJulTePTvATpuEcWsgguY5S7s3a1uWwJBPa Kq3s6kcCzp6oRKDg8cvEXBGhc53kC2rYUSxzoeeFAip6VxKd53RBndfcPHlGtUdP+a4w FtMt8WNvIufsJ9X/Z+JXqnYWkiHIsE9duweg7rL7mX9r0F4Ez7LY+fNqOTArKYEU5sNH ui5g==
X-Gm-Message-State: ALoCoQmDz8O/Z9w28CbVeE2p93cyeo551Iwa+dc5K5XsSnwu/EaSgcliG5r9yoyBpgLmrwsmHmGV
X-Received: by 10.180.72.136 with SMTP id d8mr35533521wiv.44.1395875224371; Wed, 26 Mar 2014 16:07:04 -0700 (PDT)
Received: from camionet.local (neu67-4-88-160-65-79.fbx.proxad.net. [88.160.65.79]) by mx.google.com with ESMTPSA id bi8sm6480637wib.3.2014.03.26.16.07.02 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 26 Mar 2014 16:07:03 -0700 (PDT)
Message-ID: <53335D95.6000806@jitsi.org>
Date: Thu, 27 Mar 2014 00:07:01 +0100
From: Emil Ivov <emcho@jitsi.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Parthasarathi R <partha@parthasarathi.co.in>
References: <01e601cf423c$57255890$057009b0$@co.in>	<00c901cf4687$0a48dbb0$1eda9310$@co.in> <CAPvvaaKW+vxhJFqUPRZ-YfPQ4dHOS-=YwZaW+=NS3DttaaXD=Q@mail.gmail.com> <013601cf4923$754b35e0$5fe1a1a0$@co.in>
In-Reply-To: <013601cf4923$754b35e0$5fe1a1a0$@co.in>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/ENDmzfckbTSeujiKwIUJpNr1g1E
Cc: 'mmusic' <mmusic@ietf.org>, 'Christer Holmberg' <christer.holmberg@ericsson.com>
Subject: Re: [MMUSIC] Comment on SIP Trickle ICE based on INFO draft
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: Wed, 26 Mar 2014 23:07:10 -0000

On 26.03.14, 19:44, Parthasarathi R wrote:
>  > > This race condition is very much possible during
>  > > early
>  > > dialog scenarios with UPDATE.
>  > >
>  > > Could you please explain how SIP trickle ICE using INFO works for
>  > >
>  > > 1) UPDATE from remote before Trickle ICE is completed
>
> This is analogous to an UPDATE that is received before regular 5245 ICE
> processing has completed.
>
> <Partha> No, in case UDPATE before the offer is completed, 491 response
> will send out whereas it will not happen in case of INFO </Partha>

I think you might be confusing "before ICE processing has completed" and 
"before O/A has completed"

An UPDATE that is received while "vanilla ICE processing is in progress" 
would have exactly the same effect as an UPDATE received while "trickle 
ICE processing is in progress". If O/A has completed then the UPDATE 
will NOT cause a 491 in either case.

>  > >     a) INVITE from local
>  > >     b) 183 session progress from remote
>  > >     c) PRACK from local
>  > >     d) INFO from local (relay candidates)
>  > >     e) UPDATE from remote
>  > >
>  > > Here, the remote has to consider whether INFO belongs to UPDATE or
>  > > INVITE as
>  > > it is possible for INFO to reach before 200 OK for UPDATE as well in
>  > > the
>  > > same sequence.
>
> And CSeq headers wouldn't help here because ....?
>
>  > > Also, RFC 2976
>
> which FWIW is obsoleted by RFC6086
>
> <Partha> Thanks..I still majorly interwork with RFC 2976 implementation
> :-( but please note that RFC 6086 does not change much in these SIP
> dialog or session aspects. The exact snippet of RFC 6086 is as follows:
>
> “Note that the INFO method is not used to update characteristics of a
>     SIP dialog or session, but to allow the applications that use the SIP
>     session to exchange information (which might update the state of
>     those applications).”

Trickle ICE does not update the characteristics of a SIP dialog and I 
don't believe it violates the above in any way.

>  > > " - The extensions that use the INFO message MUST NOT rely on the
>  > >      INFO message to do anything that effects the SIP call state or the
>  > >      state of related sessions."
>
> And I don't believe that it does.
>
> <Partha> No, it is not possible to implement this draft without impact
> offer/answer state machine </Partha>

Please provide an example where you think it actually breaks something. 
(It might be worth waiting until we submit the new version, which should 
probably clarify a few things).

>  > > 2) Trickle ICE INFO with serial forking
>
> INFO requests are sent within a dialog. They will go through the prong
> associated with that dialog and would not be forked.
>
> <Partha> IOW, Trickle ICE INFO will be buffered till 18x response is
> received. So, INFO has no much advantage compare to UPDATE except for
> the non-reliable response scenario.

No advantage? INFOs can be send in both directions and arrive completely 
asynchronously without ever causing glare or without having to worry 
whose turn it is to send an offer or an answer because you need to 
piggyback candidates on top of it.

We've been through this exact same argument several times already, you 
haven't pointed out any flaws with this logic so I can't see a reason 
why you keep coming back to it.

You claim you are worried about needing to modify the offer/answer state 
machine in your implementation, but that is a very strange argument 
since that implementation would be much more heavily impacted if you 
were to try and trickle with offers and answers.

I think the source of the confusion might be the fact that the draft is 
currently in a relatively poor state, which is my fault, and I am 
hopeful that you may find many of your answers in the next version.

Emil

-- 
https://jitsi.org


From nobody Thu Mar 27 02:48:17 2014
Return-Path: <albrecht.schwarz@alcatel-lucent.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 2833F1A010C for <mmusic@ietfa.amsl.com>; Thu, 27 Mar 2014 02:48:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] autolearn=ham
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 PbTQ38xEdYhA for <mmusic@ietfa.amsl.com>; Thu, 27 Mar 2014 02:48:13 -0700 (PDT)
Received: from hoemail1.alcatel.com (hoemail1.alcatel.com [192.160.6.148]) by ietfa.amsl.com (Postfix) with ESMTP id DF3F41A04A3 for <mmusic@ietf.org>; Thu, 27 Mar 2014 02:48:12 -0700 (PDT)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (h135-239-2-122.lucent.com [135.239.2.122]) by hoemail1.alcatel.com (8.13.8/IER-o) with ESMTP id s2R9m9ZU013086 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <mmusic@ietf.org>; Thu, 27 Mar 2014 04:48:10 -0500 (CDT)
Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (fr712wxchhub03.zeu.alcatel-lucent.com [135.239.2.74]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id s2R9m8Yb013481 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <mmusic@ietf.org>; Thu, 27 Mar 2014 10:48:08 +0100
Received: from FR711WXCHMBA03.zeu.alcatel-lucent.com ([169.254.3.70]) by FR712WXCHHUB03.zeu.alcatel-lucent.com ([135.239.2.74]) with mapi id 14.02.0247.003; Thu, 27 Mar 2014 10:48:09 +0100
From: "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>
To: "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: I-D Action: draft-schwarz-sdp-for-gw-01.txt
Thread-Index: AQHPSZ11tlxeVOi9qUaF/6Ya6nB3kJr0rpiA
Date: Thu, 27 Mar 2014 09:48:08 +0000
Message-ID: <786615F3A85DF44AA2A76164A71FE1AC1DAAF2@FR711WXCHMBA03.zeu.alcatel-lucent.com>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.239.27.39]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/AiuFuAdy6q4pqVHHejgECPamSGE
Subject: [MMUSIC] FW: I-D Action: draft-schwarz-sdp-for-gw-01.txt
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: Thu, 27 Mar 2014 09:48:15 -0000

fyi, this is a spin off activity from
	draft-ietf-mmusic-udptl-dtls=20
in order to define additional codepoints as required for DTLS security sess=
ion termination (so called end-to-access edge security mode) and DTLS trans=
parent forwarding (e.g. as part of end-to-end security mode) in middleboxes=
.
-Albrecht

-----Original Message-----
From: I-D-Announce [mailto:i-d-announce-bounces@ietf.org] On Behalf Of inte=
rnet-drafts@ietf.org
Sent: Donnerstag, 27. M=E4rz 2014 10:03
To: i-d-announce@ietf.org
Subject: I-D Action: draft-schwarz-sdp-for-gw-01.txt


A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.


        Title           : SDP codepoints for gateway control
        Author          : Albrecht Schwarz
	Filename        : draft-schwarz-sdp-for-gw-01.txt
	Pages           : 12
	Date            : 2014-03-27

Abstract:
   SDP is used in many signalling protocols at call control level (such
   as SAP, SIP, BICC), bearer control level (such as RTSP, IPBCP) and
   gateway control level (such as H.248/MEGACO, MGCP). Scope of this RFC
   is related to gateway control specific SDP usage. Gateway control
   protocols do usually NOT define and introduce any new SDP parameters,
   however, gateway control protocols need specific SDP parameter values
   in addition to SDP usage at call or bearer control level. Such SDP
   codepoints are collected by this RFC with the purpose of registration
   with IANA.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-schwarz-sdp-for-gw/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-schwarz-sdp-for-gw-01=20

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-schwarz-sdp-for-gw-01


Please note that it may take a couple of minutes from the time of submissio=
n until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html or ftp://ftp.ie=
tf.org/ietf/1shadow-sites.txt


From nobody Thu Mar 27 09:03:25 2014
Return-Path: <pkyzivat@alum.mit.edu>
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 251751A0186 for <mmusic@ietfa.amsl.com>; Thu, 27 Mar 2014 09:03:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] 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 Xe5eeGJjAP0q for <mmusic@ietfa.amsl.com>; Thu, 27 Mar 2014 09:03:21 -0700 (PDT)
Received: from qmta14.westchester.pa.mail.comcast.net (qmta14.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:212]) by ietfa.amsl.com (Postfix) with ESMTP id 31BD21A016A for <mmusic@ietf.org>; Thu, 27 Mar 2014 09:03:21 -0700 (PDT)
Received: from omta21.westchester.pa.mail.comcast.net ([76.96.62.72]) by qmta14.westchester.pa.mail.comcast.net with comcast id idrx1n0051ZXKqc5Eg3Kmz; Thu, 27 Mar 2014 16:03:19 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta21.westchester.pa.mail.comcast.net with comcast id ig3K1n0043ZTu2S3hg3Kfj; Thu, 27 Mar 2014 16:03:19 +0000
Message-ID: <53344BC7.3040409@alum.mit.edu>
Date: Thu, 27 Mar 2014 12:03:19 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: mmusic@ietf.org
References: <5331E601.8070605@cisco.com>
In-Reply-To: <5331E601.8070605@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1395936199; bh=ujB01VEhv40nDKxuKzaz8qiS4bgVEubtvNdOEdZMsWg=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=ZSSSGr3Jwq/icuu0fc/5ss9rZUz56qymSDDvUZIoOL3cX9Ysa/t3MWyAtNq7+Mc59 Fks0FVY/T4sJ5CzqdAnjdEhIuqv3ioS0HhyfxEVIojAlDDq3jKwVb8oXIAjyrqPmus vGB1extCcfUcxW4y3n8cHdMkdsaW7zVDVgOPhFXpnVcAMuwYVLtapWDEL5xHe7AIzt GlQoCtEohJHIo+oopG8HxSunc7wA6bMuXWe0H1FIHenwTIEZdMEHALqAcThtOqB12o fuCrlt6RaRXn4ZK4+vGG5y8alkmbwTO9Wmyw3EDDZseSVkmKixMy0t8ENyLaiQyl3R srmyynky1l22A==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/i0qPSEerNjziWlOiYhUUcOZO2dU
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-udptl-dtls-06
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: Thu, 27 Mar 2014 16:03:23 -0000

Here are my comments based on a quick review of this draft:

Section 4.5:

nit: s/are unchanged are unchanged/are unchanged/

If a new DTLS association is to be established, is it well defined when 
to cut over to it? ISTM that some procedures are required here to ensure 
that data isn't lost, or replicated.

Section A.2, Figure 3:

This shows the entire DTLS handshake taking place before the UAS sends 
*any* sip response. I assume this is only for convenience, and isn't 
intended to imply that this is how it should be done. In reality, it is 
likely that *some* sip response will be sent and received before the 
DTLS handshake completes - maybe before it starts.

It would be helpful to comment on this.

Of the above, the one about cut over could call for significant new 
content. But I expect there to be discussion of that one first. The 
others are editorial.

Otherwise this draft seems ready to me.

	Thanks,
	Paul


From nobody Thu Mar 27 11:28:59 2014
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 5B8421A01AF for <mmusic@ietfa.amsl.com>; Thu, 27 Mar 2014 11:28:58 -0700 (PDT)
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 FXyHNL_4_-7H for <mmusic@ietfa.amsl.com>; Thu, 27 Mar 2014 11:28:57 -0700 (PDT)
Received: from sessmg20.mgmt.ericsson.se (sessmg20.ericsson.net [193.180.251.50]) by ietfa.amsl.com (Postfix) with ESMTP id 9C5B61A0165 for <mmusic@ietf.org>; Thu, 27 Mar 2014 11:28:56 -0700 (PDT)
X-AuditID: c1b4fb32-b7f4c8e0000012f5-8b-53346de501d9
Received: from ESESSHC021.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg20.mgmt.ericsson.se (Symantec Mail Security) with SMTP id E3.3A.04853.5ED64335; Thu, 27 Mar 2014 19:28:53 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.213]) by ESESSHC021.ericsson.se ([153.88.183.81]) with mapi id 14.02.0387.000; Thu, 27 Mar 2014 19:28:53 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] WGLC for draft-ietf-mmusic-udptl-dtls-06
Thread-Index: AQHPSGhBkGgOUI/R1UC6/eMZQzB+K5r1Co+AgAA1L2A=
Date: Thu, 27 Mar 2014 18:28:52 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D265686@ESESSMB209.ericsson.se>
References: <5331E601.8070605@cisco.com>,<53344BC7.3040409@alum.mit.edu>
In-Reply-To: <53344BC7.3040409@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.20]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrHLMWRmVeSWpSXmKPExsUyM+Jvje7TXJNgg6OPtCymLn/MYrFiwwFW ByaPv+8/MHksWfKTKYApissmJTUnsyy1SN8ugSvjweF2poInfBW9jzvZGhh3cXcxcnJICJhI dM86wwphi0lcuLeerYuRi0NI4ASjxMRtR6GcJYwS1ye9A3I4ONgELCS6/2mDNIgI+Eo8e3wb LCwsYCdx9wwnRNhe4sDH6cxdjOxAtpXEDQeQKIuAqsTZN0vBinmBGl9t4QEJCwl4SFzdvYgZ xOYU0JFYvecPI4jNCHTM91NrmEBsZgFxiVtP5jNBHCkgsWTPeWYIW1Ti5eN/UMcrSlydvhyq Xkdiwe5PbBC2tsSyha/B6nkFBCVOznzCMoFRdBaSsbOQtMxC0jILScsCRpZVjJLFqcXFuelG Bnq56bkleqlFmcnFxfl5esWpmxiBcXJwy2+jHYwn99gfYpTmYFES573OWhMkJJCeWJKanZpa kFoUX1Sak1p8iJGJg1OqgdF8+Q8NldUGH72Slr3rfTxhqUgj41k/402fA5iCPuyRftN6Z77r 86ke6rWqz9k/Wvqs3zp1i9YvTy+z9X5FXvfkli58GLkw5qvkrsuu4deaDdd57GNd+olH5lmQ uFXsLK8l377WPq3o8tqX6f/MVuqx2CHNVT23li6RW8dyXH7NkvSDLEzdkV5KLMUZiYZazEXF iQBlfyfRYQIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/xiHUoEOtnKBJkScTHuxbJPyFCNU
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-udptl-dtls-06
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: Thu, 27 Mar 2014 18:28:58 -0000

Hi,

>Here are my comments based on a quick review of this draft:
>
>Section 4.5:
>
>nit: s/are unchanged are unchanged/are unchanged/

I'll fix that.


---------------------------


>If a new DTLS association is to be established, is it well defined when
>to cut over to it? ISTM that some procedures are required here to ensure
>that data isn't lost, or replicated.

I don't think we can define any exact procedures for that. DTLS-SRTP doesn'=
t define any exact procedures either. RFC 5763 only says:

  "Once the new session keys are established, the session can switch to usi=
ng these and abandon the old keys."

...and I don't think we can say much more.

In addition, I assume there are procedures on the fax application layer for=
 avoiding lost data.

Also, I think it will be rare that the keys and/or transport parameters cha=
nge during a fax transmission. Or, if they do, perhaps a fax transmission f=
ailure is acceptable?


---------------------------


> Section A.2, Figure 3:
>
> This shows the entire DTLS handshake taking place before the UAS sends
> *any* sip response. I assume this is only for convenience, and isn't
> intended to imply that this is how it should be done. In reality, it is
> likely that *some* sip response will be sent and received before the
> DTLS handshake completes - maybe before it starts.
>
> It would be helpful to comment on this.

Flemming had a similar comment. We addressed that by adding the following p=
aragraph to the description text for Message (4):

      "Note that, unlike in this example, it is not necessary to wait for
      the DTLS handshake to finish before the SDP answer is sent.  If
      Bob has sent the SIP 200 (OK) response and later detects that the
      certificate fingerprints do not match, he will terminate the
      session."

Regards,

Christer


From nobody Thu Mar 27 11:36:28 2014
Return-Path: <gsalguei@cisco.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 9476E1A01CC for <mmusic@ietfa.amsl.com>; Thu, 27 Mar 2014 11:36:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.511
X-Spam-Level: 
X-Spam-Status: No, score=-9.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 K0-dAoue6-X7 for <mmusic@ietfa.amsl.com>; Thu, 27 Mar 2014 11:36:24 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) by ietfa.amsl.com (Postfix) with ESMTP id 70EAB1A0182 for <mmusic@ietf.org>; Thu, 27 Mar 2014 11:36:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2348; q=dns/txt; s=iport; t=1395945382; x=1397154982; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=SmzsaRS0FDgJhCKrATD5Tq1N4gtq6AiCQ897d6tWpgc=; b=frVo866un1PICeZxU8Hk/P2FT4xqthoO6ufeoqvf7l+0eEwxeOrfgg3r fNFxrpiUf66AvvnQVmE5OxHu9PDEVNJMe3YREE+k2d4nqA9cCJjYN1KOH DZ0cRKa2YEftOi2LLJ4+RtSeswYQUcHQUO1N0XvpOye4nsku5A8ag3G7f Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AkYFAKhuNFOtJXHB/2dsb2JhbABZgwY7V7smhmZRgR4WdIIlAQEBAwEBAQE3NAsQAgEINhAnCyUCBA4Fh3EIDdEbEwSORzMHgySBFASYTZI0gy+CKw
X-IronPort-AV: E=Sophos;i="4.97,744,1389744000"; d="scan'208";a="30916025"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by alln-iport-2.cisco.com with ESMTP; 27 Mar 2014 18:36:20 +0000
Received: from xhc-rcd-x06.cisco.com (xhc-rcd-x06.cisco.com [173.37.183.80]) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id s2RIaKu9029353 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 27 Mar 2014 18:36:20 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.5]) by xhc-rcd-x06.cisco.com ([173.37.183.80]) with mapi id 14.03.0123.003; Thu, 27 Mar 2014 13:36:19 -0500
From: "Gonzalo Salgueiro (gsalguei)" <gsalguei@cisco.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Thread-Topic: [MMUSIC] WGLC for draft-ietf-mmusic-udptl-dtls-06
Thread-Index: AQHPSGhBJKPOVBvPeUSLNNz5ik5Wcpr1Co+AgAA1L2CAAFomgA==
Date: Thu, 27 Mar 2014 18:36:19 +0000
Message-ID: <618CB82A-1BDD-4283-B0BA-09DE422A340A@cisco.com>
References: <5331E601.8070605@cisco.com>,<53344BC7.3040409@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D265686@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D265686@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.82.234.45]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <8FF01F9F9939B643854B4D787CE7736F@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/_sygEGVlel9Vz1k6GmZG2HJxtY0
Cc: "mmusic@ietf.org" <mmusic@ietf.org>, Paul Kyzivat <pkyzivat@alum.mit.edu>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-udptl-dtls-06
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: Thu, 27 Mar 2014 18:36:26 -0000

On Mar 27, 2014, at 2:28 PM, Christer Holmberg <christer.holmberg@ericsson.=
com> wrote:

>=20
> Hi,
>=20
>> Here are my comments based on a quick review of this draft:
>>=20
>> Section 4.5:
>>=20
>> nit: s/are unchanged are unchanged/are unchanged/
>=20
> I'll fix that.
>=20
>=20
> ---------------------------
>=20
>=20
>> If a new DTLS association is to be established, is it well defined when
>> to cut over to it? ISTM that some procedures are required here to ensure
>> that data isn't lost, or replicated.
>=20
> I don't think we can define any exact procedures for that. DTLS-SRTP does=
n't define any exact procedures either. RFC 5763 only says:
>=20
>  "Once the new session keys are established, the session can switch to us=
ing these and abandon the old keys."
>=20
> ...and I don't think we can say much more.
>=20
> In addition, I assume there are procedures on the fax application layer f=
or avoiding lost data.
>=20
> Also, I think it will be rare that the keys and/or transport parameters c=
hange during a fax transmission. Or, if they do, perhaps a fax transmission=
 failure is acceptable?

Data loss prevention/recovery mechanisms are in place at the fax layer.

-G

> ---------------------------
>=20
>=20
>> Section A.2, Figure 3:
>>=20
>> This shows the entire DTLS handshake taking place before the UAS sends
>> *any* sip response. I assume this is only for convenience, and isn't
>> intended to imply that this is how it should be done. In reality, it is
>> likely that *some* sip response will be sent and received before the
>> DTLS handshake completes - maybe before it starts.
>>=20
>> It would be helpful to comment on this.
>=20
> Flemming had a similar comment. We addressed that by adding the following=
 paragraph to the description text for Message (4):
>=20
>      "Note that, unlike in this example, it is not necessary to wait for
>      the DTLS handshake to finish before the SDP answer is sent.  If
>      Bob has sent the SIP 200 (OK) response and later detects that the
>      certificate fingerprints do not match, he will terminate the
>      session."
>=20
> Regards,
>=20
> Christer
>=20
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic


From nobody Fri Mar 28 08:39:05 2014
Return-Path: <pkyzivat@alum.mit.edu>
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 22CBB1A02DB for <mmusic@ietfa.amsl.com>; Fri, 28 Mar 2014 08:39:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] 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 j-ZvgHnenkqN for <mmusic@ietfa.amsl.com>; Fri, 28 Mar 2014 08:39:01 -0700 (PDT)
Received: from qmta07.westchester.pa.mail.comcast.net (qmta07.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:64]) by ietfa.amsl.com (Postfix) with ESMTP id D1BBA1A0110 for <mmusic@ietf.org>; Fri, 28 Mar 2014 08:39:00 -0700 (PDT)
Received: from omta01.westchester.pa.mail.comcast.net ([76.96.62.11]) by qmta07.westchester.pa.mail.comcast.net with comcast id j0oJ1n0080EZKEL573eymz; Fri, 28 Mar 2014 15:38:58 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta01.westchester.pa.mail.comcast.net with comcast id j3ey1n00F3ZTu2S3M3eyi7; Fri, 28 Mar 2014 15:38:58 +0000
Message-ID: <53359792.5090603@alum.mit.edu>
Date: Fri, 28 Mar 2014 11:38:58 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: "Gonzalo Salgueiro (gsalguei)" <gsalguei@cisco.com>,  Christer Holmberg <christer.holmberg@ericsson.com>
References: <5331E601.8070605@cisco.com>, <53344BC7.3040409@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D265686@ESESSMB209.ericsson.se> <618CB82A-1BDD-4283-B0BA-09DE422A340A@cisco.com>
In-Reply-To: <618CB82A-1BDD-4283-B0BA-09DE422A340A@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1396021138; bh=jcWSOWXpUyHl8qHWonlw79NmnGhDn6zMtDxKYBXL0BI=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=AA32yK4Y5ceapgM0gOVaHtwkQpXMKN42l/nNWr2++1WqUgKTmyLASDlVEwuVGuy9A XikJCyEu2ErsnsUHHwQ8f2wuR52Kz+g3ElPya0pVRTSzsyZSSun0HJvwzsuK61dvUk hvGa4A7HMzI7yV/62lN2UgQZoxYWb5y7YdPldDvCDH3kGsaZl7Ne+OpN0qsvKMwN+4 l9wQYCWrBQPCuRyzq1MfKdAuMqPCvNE4BYEszEVSbB3qkXZAHxHaNhndqBejyRb7CS HScGNTcJi6qFI/8uGJNK8xUUfpAeKMF+5DmiIKmi3Jtxicvfsl8yFFYvamu81ZimYV QzbxWsb3Nk4Og==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/DnY2v4Ekkk-i-4TS5kGDy_AFA8c
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-udptl-dtls-06
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: Fri, 28 Mar 2014 15:39:02 -0000

On 3/27/14 2:36 PM, Gonzalo Salgueiro (gsalguei) wrote:
>
> On Mar 27, 2014, at 2:28 PM, Christer Holmberg <christer.holmberg@ericsson.com> wrote:
>
>>
>> Hi,
>>
>>> Here are my comments based on a quick review of this draft:
>>>
>>> Section 4.5:
>>>
>>> nit: s/are unchanged are unchanged/are unchanged/
>>
>> I'll fix that.
>>
>>
>> ---------------------------
>>
>>
>>> If a new DTLS association is to be established, is it well defined when
>>> to cut over to it? ISTM that some procedures are required here to ensure
>>> that data isn't lost, or replicated.
>>
>> I don't think we can define any exact procedures for that. DTLS-SRTP doesn't define any exact procedures either. RFC 5763 only says:
>>
>>   "Once the new session keys are established, the session can switch to using these and abandon the old keys."
>>
>> ...and I don't think we can say much more.
>>
>> In addition, I assume there are procedures on the fax application layer for avoiding lost data.
>>
>> Also, I think it will be rare that the keys and/or transport parameters change during a fax transmission. Or, if they do, perhaps a fax transmission failure is acceptable?
>
> Data loss prevention/recovery mechanisms are in place at the fax layer.

The case I'm talking about is: A new O/A results in establishing a new 
connection, replacing a prior one. At some point during that process 
both the old and new connections are usable. Then, at some point the 
sender stops sending to the old connection and starts sending to the new 
one.

For the receiver to get all the data, it must keep reading from the old 
one until it has received the last packet sent there, and must start 
reading on the new connection soon enough to get the first data sent 
there. And there is a possibility that the packets won't arrive in the 
order sent, so ceasing to read from the new one once something has been 
received from the old one could cause something to be lost. (Or course 
these aren't reliable protocols, so something could be lost in the 
network too.)

Are you saying that the fax layer is sufficient to deal with this? (I 
haven't looked at it.)

I realize that this problem isn't unique here - it applies any time O/A 
results in a change to the media path. I've wondered about it for a long 
time, but have assumed it has typically been considered acceptable to 
get a "glitch" in an audio or video stream in such a case. But it is 
less acceptable for fax.

	Thanks,
	Paul


From nobody Fri Mar 28 11:25:43 2014
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 44D3E1A0713 for <mmusic@ietfa.amsl.com>; Fri, 28 Mar 2014 11:25:42 -0700 (PDT)
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 pY9r1ZUVpZbN for <mmusic@ietfa.amsl.com>; Fri, 28 Mar 2014 11:25:41 -0700 (PDT)
Received: from sesbmg21.mgmt.ericsson.se (sesbmg21.ericsson.net [193.180.251.49]) by ietfa.amsl.com (Postfix) with ESMTP id 766A01A06CB for <mmusic@ietf.org>; Fri, 28 Mar 2014 11:25:40 -0700 (PDT)
X-AuditID: c1b4fb31-b7f888e000000826-36-5335bea1f915
Received: from ESESSHC010.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg21.mgmt.ericsson.se (Symantec Mail Security) with SMTP id 14.BA.02086.1AEB5335; Fri, 28 Mar 2014 19:25:37 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.213]) by ESESSHC010.ericsson.se ([153.88.183.48]) with mapi id 14.02.0387.000; Fri, 28 Mar 2014 19:25:36 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "Gonzalo Salgueiro (gsalguei)" <gsalguei@cisco.com>
Thread-Topic: [MMUSIC] WGLC for draft-ietf-mmusic-udptl-dtls-06
Thread-Index: AQHPSGhBkGgOUI/R1UC6/eMZQzB+K5r1Co+AgAA1L2D///WRgIABYMgAgAA+SHo=
Date: Fri, 28 Mar 2014 18:25:36 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D267A12@ESESSMB209.ericsson.se>
References: <5331E601.8070605@cisco.com>,<53344BC7.3040409@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D265686@ESESSMB209.ericsson.se> <618CB82A-1BDD-4283-B0BA-09DE422A340A@cisco.com>, <53359792.5090603@alum.mit.edu>
In-Reply-To: <53359792.5090603@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.17]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrCLMWRmVeSWpSXmKPExsUyM+Jvje7CfabBBhe+CVvMneJnMXX5YxaL FRsOsDowe/x9/4HJY8rvjaweS5b8ZApgjuKySUnNySxLLdK3S+DKuLGzkaVgo0jFh39lDYw/ +bsYOTkkBEwkPn9ZywZhi0lcuLceyObiEBI4wSjRsvQxlLOEUeLAph+sXYwcHGwCFhLd/7RB GkQE4iXuHmhhBAkzC6hLXF0cBGIKC9hJ3D3DCVFhL3Hg43RmCNtP4uzEiSwgNouAqsS6putg cV4BX4nl/+4yQmy6zyixqPE6O0iCU0BH4szyNWBFjEC3fT+1hgnEZhYQl7j1ZD4TxM0CEkv2 nGeGsEUlXj7+B3alhICixPJ+OYhyHYkFuz+xQdjaEssWvobaKyhxcuYTlgmMYrOQTJ2FpGUW kpZZSFoWMLKsYpQsTi1Oyk03MtTLTc8t0UstykwuLs7P0ytO3cQIjKmDW34b7mCceM3+EKM0 B4uSOC/D9M4gIYH0xJLU7NTUgtSi+KLSnNTiQ4xMHJxSDYzuTBMVe8TPnC87HHsx7MPDBTle hluTQpv15Crqpdljt/+acDn3W7BgxPzu2p0f717Y+HhHxZozW7TmlEj7+Rxzm3KhqKH22Z7d jMU6ytryyeJ30uRrJn6+HPnHb1bI63ldWR4KKVIH56q4SKsWvChJ3HCI9Qnvs1Vubh/PX7EU 024Uu2pw00CJpTgj0VCLuag4EQBH3/x4dwIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/r7YwcFWE886tzEuM0B6O4XtvT8o
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-udptl-dtls-06
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: Fri, 28 Mar 2014 18:25:42 -0000

Hi,

>>>> If a new DTLS association is to be established, is it well defined whe=
n
>>>> to cut over to it? ISTM that some procedures are required here to ensu=
re
>>>> that data isn't lost, or replicated.
>>>
>>> I don't think we can define any exact procedures for that. DTLS-SRTP do=
esn't define any exact procedures either. RFC 5763 only says:
>>>
>>>   "Once the new session keys are established, the session can switch to=
 using these and abandon the old keys."
>>>
>>> ...and I don't think we can say much more.
>>>
>>> In addition, I assume there are procedures on the fax application layer=
 for avoiding lost data.
>>>
>>> Also, I think it will be rare that the keys and/or transport parameters=
 change during a fax transmission. Or, if they do, perhaps a fax transmissi=
on failure is acceptable?
>>
>> Data loss prevention/recovery mechanisms are in place at the fax layer.
>
> The case I'm talking about is: A new O/A results in establishing a new
> connection, replacing a prior one. At some point during that process
> both the old and new connections are usable. Then, at some point the
> sender stops sending to the old connection and starts sending to the new
> one.

Yes.

> For the receiver to get all the data, it must keep reading from the old
> one until it has received the last packet sent there, and must start
> reading on the new connection soon enough to get the first data sent
> there. And there is a possibility that the packets won't arrive in the
> order sent, so ceasing to read from the new one once something has been
> received from the old one could cause something to be lost. (Or course
> these aren't reliable protocols, so something could be lost in the
> network too.)
>
> Are you saying that the fax layer is sufficient to deal with this? (I
> haven't looked at it.)

Yes.

I don't think the receiver should cease to read from the new one if it rece=
ives something from the old one.

If it helps, we could add a sentence saying that the receiver needs to be p=
repared to receive data on both the new and old connections, as long as the=
y are both alive.

> I realize that this problem isn't unique here - it applies any time O/A
> results in a change to the media path. I've wondered about it for a long
> time, but have assumed it has typically been considered acceptable to
> get a "glitch" in an audio or video stream in such a case. But it is
> less acceptable for fax.

It is not even introduced by this draft, as FoIP using SDP O/A has been aro=
und for many years.

Regards,

Christer


From nobody Fri Mar 28 13:16:09 2014
Return-Path: <pkyzivat@alum.mit.edu>
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 2A1801A0344 for <mmusic@ietfa.amsl.com>; Fri, 28 Mar 2014 13:16:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] 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 L68bAIMB_HIf for <mmusic@ietfa.amsl.com>; Fri, 28 Mar 2014 13:16:04 -0700 (PDT)
Received: from qmta12.westchester.pa.mail.comcast.net (qmta12.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:227]) by ietfa.amsl.com (Postfix) with ESMTP id 8A2E11A0303 for <mmusic@ietf.org>; Fri, 28 Mar 2014 13:16:04 -0700 (PDT)
Received: from omta09.westchester.pa.mail.comcast.net ([76.96.62.20]) by qmta12.westchester.pa.mail.comcast.net with comcast id j1dN1n0010SCNGk5C8G28n; Fri, 28 Mar 2014 20:16:02 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta09.westchester.pa.mail.comcast.net with comcast id j8G21n0023ZTu2S3V8G2eb; Fri, 28 Mar 2014 20:16:02 +0000
Message-ID: <5335D881.4@alum.mit.edu>
Date: Fri, 28 Mar 2014 16:16:01 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: mmusic@ietf.org
References: <5331E601.8070605@cisco.com>, <53344BC7.3040409@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D265686@ESESSMB209.ericsson.se> <618CB82A-1BDD-4283-B0BA-09DE422A340A@cisco.com>, <53359792.5090603@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D267A12@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D267A12@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1396037762; bh=PLsdgJZ+TSCThVn0yr+u736WkDmMkovDamgH/9zmx1k=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=qdq8uPl/v7BmmuIOXX6/R/Egrg4jznHXJGY8qx+FjBV3x7FOKXhIY3nqoWgifZhCi vgABMBAXK+WW3zV1aP6tE0H8B2w/Oa+BliwILQ+Iy+gdXLTgkfGNFXL2oOUh3C50A2 EtDyUg8PCkI4wxVx5D/1CXXaEllsGIf3FlWAp8d91bcGyEXY18uHxsCU3PUveCYpgE 6tbcKHNtu7yoIibPZTT7XG8bXBHMaByEjn8p6o/uGTaoIfHL5XQtcsqDWmUKSECMex 64o+4CiGPpy7gayKuKBatRT3c43muc+jzJSVqkUwcrDsY/j02NB++aCDyo1XBzBOnF ry1iT380oV9oA==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/kPQlUZxpWxB8CAu8kHdzR8KTjMg
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-udptl-dtls-06
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: Fri, 28 Mar 2014 20:16:07 -0000

I've had my say on this. I'll be satisfied with whatever you decide to 
do about it, including nothing.

	Thanks,
	Paul

On 3/28/14 2:25 PM, Christer Holmberg wrote:
>
> Hi,
>
>>>>> If a new DTLS association is to be established, is it well defined when
>>>>> to cut over to it? ISTM that some procedures are required here to ensure
>>>>> that data isn't lost, or replicated.
>>>>
>>>> I don't think we can define any exact procedures for that. DTLS-SRTP doesn't define any exact procedures either. RFC 5763 only says:
>>>>
>>>>    "Once the new session keys are established, the session can switch to using these and abandon the old keys."
>>>>
>>>> ...and I don't think we can say much more.
>>>>
>>>> In addition, I assume there are procedures on the fax application layer for avoiding lost data.
>>>>
>>>> Also, I think it will be rare that the keys and/or transport parameters change during a fax transmission. Or, if they do, perhaps a fax transmission failure is acceptable?
>>>
>>> Data loss prevention/recovery mechanisms are in place at the fax layer.
>>
>> The case I'm talking about is: A new O/A results in establishing a new
>> connection, replacing a prior one. At some point during that process
>> both the old and new connections are usable. Then, at some point the
>> sender stops sending to the old connection and starts sending to the new
>> one.
>
> Yes.
>
>> For the receiver to get all the data, it must keep reading from the old
>> one until it has received the last packet sent there, and must start
>> reading on the new connection soon enough to get the first data sent
>> there. And there is a possibility that the packets won't arrive in the
>> order sent, so ceasing to read from the new one once something has been
>> received from the old one could cause something to be lost. (Or course
>> these aren't reliable protocols, so something could be lost in the
>> network too.)
>>
>> Are you saying that the fax layer is sufficient to deal with this? (I
>> haven't looked at it.)
>
> Yes.
>
> I don't think the receiver should cease to read from the new one if it receives something from the old one.
>
> If it helps, we could add a sentence saying that the receiver needs to be prepared to receive data on both the new and old connections, as long as they are both alive.
>
>> I realize that this problem isn't unique here - it applies any time O/A
>> results in a change to the media path. I've wondered about it for a long
>> time, but have assumed it has typically been considered acceptable to
>> get a "glitch" in an audio or video stream in such a case. But it is
>> less acceptable for fax.
>
> It is not even introduced by this draft, as FoIP using SDP O/A has been around for many years.
>
> Regards,
>
> Christer
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>


From nobody Sat Mar 29 02:46:56 2014
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 6BBA41A07AC for <mmusic@ietfa.amsl.com>; Sat, 29 Mar 2014 02:46:55 -0700 (PDT)
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 HMuT9yGsM6cu for <mmusic@ietfa.amsl.com>; Sat, 29 Mar 2014 02:46:53 -0700 (PDT)
Received: from sessmg20.mgmt.ericsson.se (sessmg20.ericsson.net [193.180.251.50]) by ietfa.amsl.com (Postfix) with ESMTP id 69C341A04B6 for <mmusic@ietf.org>; Sat, 29 Mar 2014 02:46:52 -0700 (PDT)
X-AuditID: c1b4fb32-b7fe98e0000034f3-78-5336968989a4
Received: from ESESSHC023.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg20.mgmt.ericsson.se (Symantec Mail Security) with SMTP id 4E.A3.13555.98696335; Sat, 29 Mar 2014 10:46:49 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.213]) by ESESSHC023.ericsson.se ([153.88.183.87]) with mapi id 14.03.0174.001; Sat, 29 Mar 2014 10:46:49 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "mmusic@ietf.org" <mmusic@ietf.org>
Thread-Topic: [MMUSIC] WGLC for draft-ietf-mmusic-udptl-dtls-06
Thread-Index: AQHPSGhBkGgOUI/R1UC6/eMZQzB+K5r1Co+AgAA1L2D///WRgIABYMgAgAA+SHqAAA8ggIAA80yb
Date: Sat, 29 Mar 2014 09:46:48 +0000
Message-ID: <cc7877jlxn0aytqbutml3k0s.1396086405009@email.android.com>
References: <5331E601.8070605@cisco.com>, <53344BC7.3040409@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D265686@ESESSMB209.ericsson.se> <618CB82A-1BDD-4283-B0BA-09DE422A340A@cisco.com>, <53359792.5090603@alum.mit.edu> <7594FB04B1934943A5C02806D1A2204B1D267A12@ESESSMB209.ericsson.se>, <5335D881.4@alum.mit.edu>
In-Reply-To: <5335D881.4@alum.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrKLMWRmVeSWpSXmKPExsUyM+JvjW7nNLNgg9a1ZhZTlz9msVix4QCr A5PH3/cfmDyWLPnJFMAUxWWTkpqTWZZapG+XwJXxdl1cwVnJilkd51kbGKeJdDFycEgImEjs 2m7VxcgJZIpJXLi3nq2LkYtDSOAEo0T3pSeMEM4SRonWl2uYQBrYBCwkuv9pgzSICPhKPHt8 mw3EFhawkzi1fD0LRNxe4sDH6cwQdpTE6wef2EFsFgFVideP+hhBbF4BN4lJrz+wQMw/yCQx +c56sAZOATWJi40HwIYyAl30/RTIXk4OZgFxiVtP5jNBXCogsWTPeWYIW1Ti5eN/rBA1OhIL dn9ig7C1JZYtfM0MsUxQ4uTMJywTGEVmIRk1C0nLLCQts5C0LGBkWcUoWZxaXJybbmSgl5ue W6KXWpSZXFycn6dXnLqJERgVB7f8NtrBeHKP/SFGaQ4WJXHe66w1QUIC6YklqdmpqQWpRfFF pTmpxYcYmTg4pRoYS34kX/kqM19M1tvhiHq6oHdWT7X4+SbuQjG9Z+lLhAoUynK1H211PfLg lXzDncDy6oSJDuL5d1hmrt63L2/2Lvn5U6Q/rLyiPOn5g1XK70VWHei1vRRjtb7eKV83rOPw l50b/Ndf5tq7zFZljlAVi2HFp8Jzc+Zorgw4n86+0VyEW0Zc3nCGEktxRqKhFnNRcSIAxoNK jVgCAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/NunU5kzI_N-BE1_Q7AkCfM5_E6E
Subject: Re: [MMUSIC] WGLC for draft-ietf-mmusic-udptl-dtls-06
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: Sat, 29 Mar 2014 09:46:55 -0000

Thanks, Paul!

Regards,

Christer

Sent from my Sony Ericsson Xperia arc S

Paul Kyzivat <pkyzivat@alum.mit.edu> wrote:


I've had my say on this. I'll be satisfied with whatever you decide to
do about it, including nothing.

        Thanks,
        Paul

On 3/28/14 2:25 PM, Christer Holmberg wrote:
>
> Hi,
>
>>>>> If a new DTLS association is to be established, is it well defined wh=
en
>>>>> to cut over to it? ISTM that some procedures are required here to ens=
ure
>>>>> that data isn't lost, or replicated.
>>>>
>>>> I don't think we can define any exact procedures for that. DTLS-SRTP d=
oesn't define any exact procedures either. RFC 5763 only says:
>>>>
>>>>    "Once the new session keys are established, the session can switch =
to using these and abandon the old keys."
>>>>
>>>> ...and I don't think we can say much more.
>>>>
>>>> In addition, I assume there are procedures on the fax application laye=
r for avoiding lost data.
>>>>
>>>> Also, I think it will be rare that the keys and/or transport parameter=
s change during a fax transmission. Or, if they do, perhaps a fax transmiss=
ion failure is acceptable?
>>>
>>> Data loss prevention/recovery mechanisms are in place at the fax layer.
>>
>> The case I'm talking about is: A new O/A results in establishing a new
>> connection, replacing a prior one. At some point during that process
>> both the old and new connections are usable. Then, at some point the
>> sender stops sending to the old connection and starts sending to the new
>> one.
>
> Yes.
>
>> For the receiver to get all the data, it must keep reading from the old
>> one until it has received the last packet sent there, and must start
>> reading on the new connection soon enough to get the first data sent
>> there. And there is a possibility that the packets won't arrive in the
>> order sent, so ceasing to read from the new one once something has been
>> received from the old one could cause something to be lost. (Or course
>> these aren't reliable protocols, so something could be lost in the
>> network too.)
>>
>> Are you saying that the fax layer is sufficient to deal with this? (I
>> haven't looked at it.)
>
> Yes.
>
> I don't think the receiver should cease to read from the new one if it re=
ceives something from the old one.
>
> If it helps, we could add a sentence saying that the receiver needs to be=
 prepared to receive data on both the new and old connections, as long as t=
hey are both alive.
>
>> I realize that this problem isn't unique here - it applies any time O/A
>> results in a change to the media path. I've wondered about it for a long
>> time, but have assumed it has typically been considered acceptable to
>> get a "glitch" in an audio or video stream in such a case. But it is
>> less acceptable for fax.
>
> It is not even introduced by this draft, as FoIP using SDP O/A has been a=
round for many years.
>
> Regards,
>
> Christer
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>

_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www.ietf.org/mailman/listinfo/mmusic


From nobody Sun Mar 30 02:38:40 2014
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 35B721A0838 for <mmusic@ietfa.amsl.com>; Sun, 30 Mar 2014 02:38:40 -0700 (PDT)
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 otMeSTydZgCV for <mmusic@ietfa.amsl.com>; Sun, 30 Mar 2014 02:38:38 -0700 (PDT)
Received: from sessmg20.mgmt.ericsson.se (sessmg20.ericsson.net [193.180.251.50]) by ietfa.amsl.com (Postfix) with ESMTP id DE3711A07AE for <mmusic@ietf.org>; Sun, 30 Mar 2014 02:38:37 -0700 (PDT)
X-AuditID: c1b4fb32-b7fe98e0000034f3-62-5337e619a78f
Received: from ESESSHC014.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg20.mgmt.ericsson.se (Symantec Mail Security) with SMTP id 14.88.13555.916E7335; Sun, 30 Mar 2014 11:38:34 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.213]) by ESESSHC014.ericsson.se ([153.88.183.60]) with mapi id 14.03.0174.001; Sun, 30 Mar 2014 11:38:33 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Emil Ivov <emcho@jitsi.org>, Parthasarathi R <partha@parthasarathi.co.in>
Thread-Topic: [MMUSIC] Comment on SIP Trickle ICE based on INFO draft
Thread-Index: AQHPRocL8dnxxOHFaUGVW6LszOxaAJruf3aAgAUpmQCAAElPgIAFdqWN
Date: Sun, 30 Mar 2014 09:38:32 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D26BE29@ESESSMB209.ericsson.se>
References: <01e601cf423c$57255890$057009b0$@co.in> <00c901cf4687$0a48dbb0$1eda9310$@co.in> <CAPvvaaKW+vxhJFqUPRZ-YfPQ4dHOS-=YwZaW+=NS3DttaaXD=Q@mail.gmail.com> <013601cf4923$754b35e0$5fe1a1a0$@co.in>,<53335D95.6000806@jitsi.org>
In-Reply-To: <53335D95.6000806@jitsi.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.17]
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrALMWRmVeSWpSXmKPExsUyM+Jvja7UM/Nggwc7mCzW7JzAYtFyx8ti 6vLHLBaTP/WxOrB4LFnyk8nj/5tAjw/zv7B7tJzrZQ9gieKySUnNySxLLdK3S+DKuD75PWvB MrWKuV0LmRsY78p2MXJySAiYSMxd+IEVwhaTuHBvPVsXIxeHkMBJRonth0ESIM4SRomH91uA MhwcbAIWEt3/tEEaRAR8JW5vb2UGsZkF4iSez77CBmILC7hI/FqygRmixlXi6/JN7BC2m8Tc xycYQWwWAVWJne8bwBbzAs35cvw21OLXjBLtex+AFXEKaEpM+tgKVsQIdN33U2uYIJaJS9x6 Mp8J4moBiSV7zjND2KISLx//YwW5U0JAUWJ5vxxEuYHE+3Pzoe7Ulli28DUzxF5BiZMzn7BM YBSbhWTqLCQts5C0zELSsoCRZRWjZHFqcXFuupGBXm56bolealFmcnFxfp5eceomRmCsHdzy 22gH48k99ocYpTlYlMR5r7PWBAkJpCeWpGanphakFsUXleakFh9iZOLglGpgLG5pPMEjJKDJ P3VrkFXPybqzDZWfAmZZntu0ozs6j5Xt1tXau5vtTrhfZgnfO2dTVY2elP1Hv/N2wuftVs+w Nz7Rvtr7+CeTKin749n8b8UrX+tLl/ysfRzjUvBth/N1DdEd+49c3zFB1XKJ3IzC0w7Lubn2 BVgunmLo/G5LVdSp/e/mHZ2xXYmlOCPRUIu5qDgRAIBCEISDAgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/Yl0biCBBeofwrhxv-JIBKKURQTk
Cc: 'mmusic' <mmusic@ietf.org>
Subject: Re: [MMUSIC] Comment on SIP Trickle ICE based on INFO draft
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: Sun, 30 Mar 2014 09:38:40 -0000

Hi,

I have tried to understand the whole issue discussed here, with little succ=
ess :)

So, rather than trying to come up with a solution, I think we first need to=
 agree on some basic assumptions.

If we claim that Trickle ICE has no impact on the SDP O/A state, then:

1) There should be no need to figure out whether an INFO is sent before an =
UPDATE; and
2) There should be no need to include the o=3D line, or any other informati=
on that binds the INFO to a specific SDP O/A state.

Instead, Trickle ICE is only a mechanism to transport candidate information=
 from one endpoint to another. Endpoints may of course add those candidates=
 to subsequent Offer/Answers.


Regards,

Christer



________________________________________
From: Emil Ivov [emcho@jitsi.org]
Sent: Thursday, 27 March 2014 1:07 AM
To: Parthasarathi R
Cc: 'mmusic'; Christer Holmberg; 'Enrico Marocco (TiLab)'
Subject: Re: [MMUSIC] Comment on SIP Trickle ICE based on INFO draft

On 26.03.14, 19:44, Parthasarathi R wrote:
>  > > This race condition is very much possible during
>  > > early
>  > > dialog scenarios with UPDATE.
>  > >
>  > > Could you please explain how SIP trickle ICE using INFO works for
>  > >
>  > > 1) UPDATE from remote before Trickle ICE is completed
>
> This is analogous to an UPDATE that is received before regular 5245 ICE
> processing has completed.
>
> <Partha> No, in case UDPATE before the offer is completed, 491 response
> will send out whereas it will not happen in case of INFO </Partha>

I think you might be confusing "before ICE processing has completed" and
"before O/A has completed"

An UPDATE that is received while "vanilla ICE processing is in progress"
would have exactly the same effect as an UPDATE received while "trickle
ICE processing is in progress". If O/A has completed then the UPDATE
will NOT cause a 491 in either case.

>  > >     a) INVITE from local
>  > >     b) 183 session progress from remote
>  > >     c) PRACK from local
>  > >     d) INFO from local (relay candidates)
>  > >     e) UPDATE from remote
>  > >
>  > > Here, the remote has to consider whether INFO belongs to UPDATE or
>  > > INVITE as
>  > > it is possible for INFO to reach before 200 OK for UPDATE as well in
>  > > the
>  > > same sequence.
>
> And CSeq headers wouldn't help here because ....?
>
>  > > Also, RFC 2976
>
> which FWIW is obsoleted by RFC6086
>
> <Partha> Thanks..I still majorly interwork with RFC 2976 implementation
> :-( but please note that RFC 6086 does not change much in these SIP
> dialog or session aspects. The exact snippet of RFC 6086 is as follows:
>
> =93Note that the INFO method is not used to update characteristics of a
>     SIP dialog or session, but to allow the applications that use the SIP
>     session to exchange information (which might update the state of
>     those applications).=94

Trickle ICE does not update the characteristics of a SIP dialog and I
don't believe it violates the above in any way.

>  > > " - The extensions that use the INFO message MUST NOT rely on the
>  > >      INFO message to do anything that effects the SIP call state or =
the
>  > >      state of related sessions."
>
> And I don't believe that it does.
>
> <Partha> No, it is not possible to implement this draft without impact
> offer/answer state machine </Partha>

Please provide an example where you think it actually breaks something.
(It might be worth waiting until we submit the new version, which should
probably clarify a few things).

>  > > 2) Trickle ICE INFO with serial forking
>
> INFO requests are sent within a dialog. They will go through the prong
> associated with that dialog and would not be forked.
>
> <Partha> IOW, Trickle ICE INFO will be buffered till 18x response is
> received. So, INFO has no much advantage compare to UPDATE except for
> the non-reliable response scenario.

No advantage? INFOs can be send in both directions and arrive completely
asynchronously without ever causing glare or without having to worry
whose turn it is to send an offer or an answer because you need to
piggyback candidates on top of it.

We've been through this exact same argument several times already, you
haven't pointed out any flaws with this logic so I can't see a reason
why you keep coming back to it.

You claim you are worried about needing to modify the offer/answer state
machine in your implementation, but that is a very strange argument
since that implementation would be much more heavily impacted if you
were to try and trickle with offers and answers.

I think the source of the confusion might be the fact that the draft is
currently in a relatively poor state, which is my fault, and I am
hopeful that you may find many of your answers in the next version.

Emil

--
https://jitsi.org=


From nobody Sun Mar 30 02:48:46 2014
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 BCC5D1A07AE for <mmusic@ietfa.amsl.com>; Sun, 30 Mar 2014 02:48:45 -0700 (PDT)
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 hSCrJBFrZPS4 for <mmusic@ietfa.amsl.com>; Sun, 30 Mar 2014 02:48:44 -0700 (PDT)
Received: from sesbmg21.mgmt.ericsson.se (sesbmg21.ericsson.net [193.180.251.49]) by ietfa.amsl.com (Postfix) with ESMTP id 1DE7F1A0473 for <mmusic@ietf.org>; Sun, 30 Mar 2014 02:48:43 -0700 (PDT)
X-AuditID: c1b4fb31-b7f688e000003e64-e8-5337e878178e
Received: from ESESSHC020.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg21.mgmt.ericsson.se (Symantec Mail Security) with SMTP id 4A.F8.15972.878E7335; Sun, 30 Mar 2014 11:48:40 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.213]) by ESESSHC020.ericsson.se ([153.88.183.78]) with mapi id 14.03.0174.001; Sun, 30 Mar 2014 11:48:39 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Parthasarathi R <partha@parthasarathi.co.in>, 'Emil Ivov' <emcho@jitsi.org>, "'Enrico Marocco (TiLab)'" <enrico.marocco@telecomitalia.it>
Thread-Topic: [MMUSIC] Comment on SIP Trickle ICE based on INFO draft - FORKING
Thread-Index: AQHPS/02PLTBD8bHIkyTiQF+pdjMCw==
Date: Sun, 30 Mar 2014 09:48:38 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D26BE6A@ESESSMB209.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.17]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrKLMWRmVeSWpSXmKPExsUyM+JvjW7FC/Ngg60bpCzW7JzAYtFyx8ti 6vLHLBaTP/WxOrB4LFnyk8nj/5tAjw/zv7B7tJzrZQ9gieKySUnNySxLLdK3S+DKWHtiJ0vB W46KX63xDYwv2boYOTkkBEwkLt59ywRhi0lcuLceKM7FISRwklHiyOHbUM4SRonNt+YwdzFy cLAJWEh0/9MGiYsITGSUOPD/DFicWUBd4uriIJBBwgIBEs+//WYDCYsIBEqsu8cKEhYR0JPY +/4VI4jNIqAqcXbVNHYQm1fAV2Ly9qdgNYxAN3w/tQbsHmYBcYlbT+ZD3SYgsWTPeWYIW1Ti 5eN/rCDjJQQUJZb3y0GU60gs2P2JDcLWlli28DUzxHhBiZMzn7BMYBSZhWTqLCQts5C0zELS soCRZRWjZHFqcVJuupGhXm56bolealFmcnFxfp5eceomRmDUHNzy23AH48Rr9ocYpTlYlMR5 GaZ3BgkJpCeWpGanphakFsUXleakFh9iZOLglGpgtKsx/+AbxBnB9FQ886C1hrBS3sod88Im FAsuEfFn37AzbaepVHqQeOuUaMnsdxN6NO6vayya28k6dYr8ydWttVv6f7Z907tlq5vz/seh yYsfGZye6vf/um/0Y3XrpNg3M9z6F2g53o+c8tn7nWFFr99XkW8f3hZvvXDn94QHYdzlP4ul Vvg6KrEUZyQaajEXFScCABrKgMBoAgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/rKZfcpUnHu1F1NCqh4nQFiPVHg0
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Comment on SIP Trickle ICE based on INFO draft - FORKING
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: Sun, 30 Mar 2014 09:48:46 -0000

Hi,

> 2) Trickle ICE INFO with serial forking
>
>   a) INVITE from local
>   b) INVITE is forked by proxy to first remote destination
>   c) 100 trying is reaching local
>   d) INFO with Trickle ICE from local
>   e) INFO is forward by proxy to first remote destination
>   f) INVITE is forked by proxy to second remote destination
>   g) Whether INFO has to be forked?
>
> It is not mentioned in the draft whether INFO has to be forked to the
> second remote destination as well. Could you please explain the expect
> behavior for this scenario.

I am not sure what you mean by the INFO being forked.

When a new fork is created (i.e. when the offerer receives a 18x response f=
rom a new destination), whatever candidates have been trickled on previousl=
y created fork(s) of course need to be provided also on the new fork.

And, when multiple forks exist, whenever a new candidate is to be trickled,=
 an INFO carrying the candidate needs to be sent on each fork.

I don't see a problem with this, but if it is unclear in the spec then some=
 additional text might be needed.

Regards,

Christer=


From nobody Sun Mar 30 13:30:42 2014
Return-Path: <emcho@sip-communicator.org>
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 508021A08D4 for <mmusic@ietfa.amsl.com>; Sun, 30 Mar 2014 13:30:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 vYB5kOPZ2R-3 for <mmusic@ietfa.amsl.com>; Sun, 30 Mar 2014 13:30:37 -0700 (PDT)
Received: from mail-wi0-f171.google.com (mail-wi0-f171.google.com [209.85.212.171]) by ietfa.amsl.com (Postfix) with ESMTP id 2042A1A08D1 for <mmusic@ietf.org>; Sun, 30 Mar 2014 13:30:36 -0700 (PDT)
Received: by mail-wi0-f171.google.com with SMTP id q5so2358966wiv.10 for <mmusic@ietf.org>; Sun, 30 Mar 2014 13:30:33 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=UXlr6+07VzGsVhRVDcH7fk/dQg4cDnya+K2qZge/Pps=; b=bkwObGDW86hjSmnDE86GeMSi05WY5B5PmuG7oNpsXouR/JtIiAIvxhNOUHeD4G5b3F TvNH0L+dBywFQ8LP/ENS9g6A6Mo6nHhZsf3MWC6wotWn52BLd/ttnOpt+TM0uwGU5YwC 5xXx9rtmjeTktEXrWgi5e0F/92a4ygraMRRYnbIKzXVzjRjkkVuxAdDm9K9LMRc94RAy oy5bGqEaWlu38NjvAyWAQN9M4a1MDXfHY+aWS24Vq22Iirto+YsqnnL628qsgEBBSYSe TU85+WSsK0CWXtdD01cyPipbwAdL8s5PsiFzWAnoV4pmKbYWJ8Sv1Z8B5Wfe7snGrqoc fNyg==
X-Gm-Message-State: ALoCoQmilRb1CgMsMZc4QFcLmTQAy1Ayf5s5kyYFXg0mKY37iFdD7awRprfpf7YpHndGbaC9B+Mm
X-Received: by 10.194.59.226 with SMTP id c2mr9162610wjr.6.1396211433397; Sun, 30 Mar 2014 13:30:33 -0700 (PDT)
Received: from camionet.local (neu67-4-88-160-65-79.fbx.proxad.net. [88.160.65.79]) by mx.google.com with ESMTPSA id fs4sm22281798wib.11.2014.03.30.13.30.30 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 30 Mar 2014 13:30:32 -0700 (PDT)
Message-ID: <53387EE5.3050501@jitsi.org>
Date: Sun, 30 Mar 2014 22:30:29 +0200
From: Emil Ivov <emcho@jitsi.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>,  Parthasarathi R <partha@parthasarathi.co.in>
References: <01e601cf423c$57255890$057009b0$@co.in>	<00c901cf4687$0a48dbb0$1eda9310$@co.in> <CAPvvaaKW+vxhJFqUPRZ-YfPQ4dHOS-=YwZaW+=NS3DttaaXD=Q@mail.gmail.com> <013601cf4923$754b35e0$5fe1a1a0$@co.in>, <53335D95.6000806@jitsi.org> <7594FB04B1934943A5C02806D1A2204B1D26BE29@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D26BE29@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/yTdlnSCmJsBgUzdjIpMtcv8iYcY
Cc: 'mmusic' <mmusic@ietf.org>
Subject: Re: [MMUSIC] Comment on SIP Trickle ICE based on INFO draft
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: Sun, 30 Mar 2014 20:30:40 -0000

On 30.03.14, 11:38, Christer Holmberg wrote:
> Hi,
>
> I have tried to understand the whole issue discussed here, with little success :)
>
> So, rather than trying to come up with a solution, I think we first need to agree on some basic assumptions.
>
> If we claim that Trickle ICE has no impact on the SDP O/A state, then:
>
> 1) There should be no need to figure out whether an INFO is sent before an UPDATE; and

That's not exactly true because, like ICE, trickle ICE does depend on 
O/A in order to operate. In other words: if you change your location and 
do a new Offer/Answer, you don't expect vanilla ICE to magically 
continue, blissfully ignorant of that fact. It needs to restart and so 
does Trickle ICE.

> 2) There should be no need to include the o= line, or any other information that binds the INFO to a specific SDP O/A state.

The main reason you need that is so that you can drop stray INFOs that 
have been delayed and have arrived when the ICE processing context they 
were related to is no longer valid (i.e. after an ICE restart).

But I agree that an o= line is not the most convenient way to handle 
this and using ice-ufrag and ice-pwd would be better.

> Instead, Trickle ICE is only a mechanism to transport candidate information from one endpoint to another.

Agreed.

> Endpoints may of course add those candidates to subsequent Offer/Answers.

This should be clarified. I think it's not necessary. Basically an O/A 
can have the following two possible relations to trickle ICE:

1. ICE restart: (ice-ufrag and ice-pwd have changed). This basically 
means that your addressing situation has most likely changed and you 
need to start everything from scratch. So you do.

2. Non-ICE session modification: you are currently doing ICE and while 
you are at it, you change some aspect of your session that has 
no-relation to addressing. For example, you add formats, change the 
direction of a stream, or something like that. In this case trickle ICE 
continues with no modification.

Case 1 obviously doesn't need any of the trickle candidates but they can 
be included if the agent is comfortable reusing them. This is compatible 
with 5245 which says something like this:

    If ICE is restarting [...] the set of candidates MAY include some,
    none, or all of the previous candidates for that stream and MAY
    include a totally new set of candidates

Case 2 is less obvious to me. Requiring agents to include all currently 
known addresses sounds a bit risky to me because it's easy to get into 
situations where an agent receives a set of candidates that does not 
match its current view of the session:

Case 2.1: New candidates appear
Case 2.2: Some candidates are not there.

Case 2.1 is easy to handle: the new candidates are handled as if they 
were trickled.

Case 2.2 is kind of a headache. 5245 says that it MUST NOT happen but I 
don't think this can be guaranteed because various race conditions may 
cause trickled candidates to arrive before the O/A and make an agent 
believe that some of them are lacking.

I think the easiest way to handle this would be to say that, when using 
Trickle ICE, candidates and addressinf information from offers that DO 
NOT restart ICE MUST be ignored.

Thoughts?

Emil

--
https://jitsi.org


>
>
> Regards,
>
> Christer
>
>
>
> ________________________________________
> From: Emil Ivov [emcho@jitsi.org]
> Sent: Thursday, 27 March 2014 1:07 AM
> To: Parthasarathi R
> Cc: 'mmusic'; Christer Holmberg; 'Enrico Marocco (TiLab)'
> Subject: Re: [MMUSIC] Comment on SIP Trickle ICE based on INFO draft
>
> On 26.03.14, 19:44, Parthasarathi R wrote:
>>   > > This race condition is very much possible during
>>   > > early
>>   > > dialog scenarios with UPDATE.
>>   > >
>>   > > Could you please explain how SIP trickle ICE using INFO works for
>>   > >
>>   > > 1) UPDATE from remote before Trickle ICE is completed
>>
>> This is analogous to an UPDATE that is received before regular 5245 ICE
>> processing has completed.
>>
>> <Partha> No, in case UDPATE before the offer is completed, 491 response
>> will send out whereas it will not happen in case of INFO </Partha>
>
> I think you might be confusing "before ICE processing has completed" and
> "before O/A has completed"
>
> An UPDATE that is received while "vanilla ICE processing is in progress"
> would have exactly the same effect as an UPDATE received while "trickle
> ICE processing is in progress". If O/A has completed then the UPDATE
> will NOT cause a 491 in either case.
>
>>   > >     a) INVITE from local
>>   > >     b) 183 session progress from remote
>>   > >     c) PRACK from local
>>   > >     d) INFO from local (relay candidates)
>>   > >     e) UPDATE from remote
>>   > >
>>   > > Here, the remote has to consider whether INFO belongs to UPDATE or
>>   > > INVITE as
>>   > > it is possible for INFO to reach before 200 OK for UPDATE as well in
>>   > > the
>>   > > same sequence.
>>
>> And CSeq headers wouldn't help here because ....?
>>
>>   > > Also, RFC 2976
>>
>> which FWIW is obsoleted by RFC6086
>>
>> <Partha> Thanks..I still majorly interwork with RFC 2976 implementation
>> :-( but please note that RFC 6086 does not change much in these SIP
>> dialog or session aspects. The exact snippet of RFC 6086 is as follows:
>>
>> “Note that the INFO method is not used to update characteristics of a
>>      SIP dialog or session, but to allow the applications that use the SIP
>>      session to exchange information (which might update the state of
>>      those applications).”
>
> Trickle ICE does not update the characteristics of a SIP dialog and I
> don't believe it violates the above in any way.
>
>>   > > " - The extensions that use the INFO message MUST NOT rely on the
>>   > >      INFO message to do anything that effects the SIP call state or the
>>   > >      state of related sessions."
>>
>> And I don't believe that it does.
>>
>> <Partha> No, it is not possible to implement this draft without impact
>> offer/answer state machine </Partha>
>
> Please provide an example where you think it actually breaks something.
> (It might be worth waiting until we submit the new version, which should
> probably clarify a few things).
>
>>   > > 2) Trickle ICE INFO with serial forking
>>
>> INFO requests are sent within a dialog. They will go through the prong
>> associated with that dialog and would not be forked.
>>
>> <Partha> IOW, Trickle ICE INFO will be buffered till 18x response is
>> received. So, INFO has no much advantage compare to UPDATE except for
>> the non-reliable response scenario.
>
> No advantage? INFOs can be send in both directions and arrive completely
> asynchronously without ever causing glare or without having to worry
> whose turn it is to send an offer or an answer because you need to
> piggyback candidates on top of it.
>
> We've been through this exact same argument several times already, you
> haven't pointed out any flaws with this logic so I can't see a reason
> why you keep coming back to it.
>
> You claim you are worried about needing to modify the offer/answer state
> machine in your implementation, but that is a very strange argument
> since that implementation would be much more heavily impacted if you
> were to try and trickle with offers and answers.
>
> I think the source of the confusion might be the fact that the draft is
> currently in a relatively poor state, which is my fault, and I am
> hopeful that you may find many of your answers in the next version.
>
> Emil


From nobody Sun Mar 30 13:37:06 2014
Return-Path: <emcho@sip-communicator.org>
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 1F6121A08D4 for <mmusic@ietfa.amsl.com>; Sun, 30 Mar 2014 13:37:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 CD_fqIdiwxoM for <mmusic@ietfa.amsl.com>; Sun, 30 Mar 2014 13:37:03 -0700 (PDT)
Received: from mail-we0-f177.google.com (mail-we0-f177.google.com [74.125.82.177]) by ietfa.amsl.com (Postfix) with ESMTP id 42BC41A07D7 for <mmusic@ietf.org>; Sun, 30 Mar 2014 13:37:03 -0700 (PDT)
Received: by mail-we0-f177.google.com with SMTP id u57so3839199wes.8 for <mmusic@ietf.org>; Sun, 30 Mar 2014 13:36:59 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=U5HGFsuTwzDBtoPiUvBFKdXA2TTP6kuDRQ9m22s9dtQ=; b=O40fPFh/LLAUJiFHzQlp494Bos5pt/hdqLFvyp8s+RCQuak7xty+XvtIK7KxQGTN/9 R2mAvXHVtTkiFoOY0hLsPJTWJug1k+sOQgwa9bU7llkUBD+mDnZ/pcdguNH4hGWgPv4M /nRb4UwBO0YFCvbAFYkPZAe3imW2FiA6ks7MzMUHOaBINZW2L7aAsbf2eIH/UWfRaM6g zHJ4CSB7quZRiysDPnu2mIujyqUTNKyuY5e2KRoANmLY67Pxc3B1CySQlotF9zi9wto0 f/XpExMM9v2iZIvPbwD7i5sdvPA/3nfwQQubfknGByJL/rS6MXOlNU89MVSZ0NUpSXla 3CjQ==
X-Gm-Message-State: ALoCoQmsqulliWKzht9Fnh7+tKMQ+xt//WUPEAKLCWisn8TDc7ykjJ31fAIL5YErOcXAFkE66s0j
X-Received: by 10.180.109.231 with SMTP id hv7mr7413444wib.38.1396211819482; Sun, 30 Mar 2014 13:36:59 -0700 (PDT)
Received: from camionet.local (neu67-4-88-160-65-79.fbx.proxad.net. [88.160.65.79]) by mx.google.com with ESMTPSA id k4sm22284272wib.19.2014.03.30.13.36.57 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 30 Mar 2014 13:36:58 -0700 (PDT)
Message-ID: <53388068.1050209@jitsi.org>
Date: Sun, 30 Mar 2014 22:36:56 +0200
From: Emil Ivov <emcho@jitsi.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Christer Holmberg <christer.holmberg@ericsson.com>,  Parthasarathi R <partha@parthasarathi.co.in>, "'Enrico Marocco (TiLab)'" <enrico.marocco@telecomitalia.it>
References: <7594FB04B1934943A5C02806D1A2204B1D26BE6A@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D26BE6A@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/Junxf1uJ4orBGRWpXdnWad1rtm8
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Comment on SIP Trickle ICE based on INFO draft - FORKING
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: Sun, 30 Mar 2014 20:37:05 -0000

On 30.03.14, 11:48, Christer Holmberg wrote:
> Hi,
>
>> 2) Trickle ICE INFO with serial forking
>>
>>    a) INVITE from local
>>    b) INVITE is forked by proxy to first remote destination
>>    c) 100 trying is reaching local
>>    d) INFO with Trickle ICE from local
>>    e) INFO is forward by proxy to first remote destination
>>    f) INVITE is forked by proxy to second remote destination
>>    g) Whether INFO has to be forked?
>>
>> It is not mentioned in the draft whether INFO has to be forked to the
>> second remote destination as well. Could you please explain the expect
>> behavior for this scenario.
>
> I am not sure what you mean by the INFO being forked.
>
> When a new fork is created (i.e. when the offerer receives a 18x response from a new destination), whatever candidates have been trickled on previously created fork(s) of course need to be provided also on the new fork.
>
> And, when multiple forks exist, whenever a new candidate is to be trickled, an INFO carrying the candidate needs to be sent on each fork.
>
> I don't see a problem with this, but if it is unclear in the spec then some additional text might be needed.

Making sure we are on the same page:

1. These additional INFOs need to be trickled by the ICE agent that 
generated them in the first place.

2. This would happen as an explicit step that is visible to the TU and 
the ICE agent. That is, it's not something that would be automatically 
handled by a SIP stack, by simply resending all the INFOs from the first 
prong of the fork to the second one.

3. Those INFOs may or may not contain the same candidates (e.g. the 
agent may have chosen to use different port numbers for that prong) and 
they may or may not be the same number (e.g. if the agent is reusing 
addresses, it may decide to send them all in a single INFO, rather than 
in a sequence of INFOs).

Do we agree?

Emil


-- 
https://jitsi.org


From nobody Sun Mar 30 14:01:43 2014
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 BC8BE1A08D7 for <mmusic@ietfa.amsl.com>; Sun, 30 Mar 2014 14:01:41 -0700 (PDT)
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 K3ms--fGrH6K for <mmusic@ietfa.amsl.com>; Sun, 30 Mar 2014 14:01:40 -0700 (PDT)
Received: from sessmg21.mgmt.ericsson.se (sessmg21.ericsson.net [193.180.251.40]) by ietfa.amsl.com (Postfix) with ESMTP id 1329E1A08D1 for <mmusic@ietf.org>; Sun, 30 Mar 2014 14:01:39 -0700 (PDT)
X-AuditID: c1b4fb28-b7fd58e000007bb5-86-53388630f462
Received: from ESESSHC016.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg21.mgmt.ericsson.se (Symantec Mail Security) with SMTP id 8C.FB.31669.03688335; Sun, 30 Mar 2014 23:01:36 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.213]) by ESESSHC016.ericsson.se ([153.88.183.66]) with mapi id 14.03.0174.001; Sun, 30 Mar 2014 23:01:35 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Emil Ivov <emcho@jitsi.org>, Parthasarathi R <partha@parthasarathi.co.in>,  "'Enrico Marocco (TiLab)'" <enrico.marocco@telecomitalia.it>
Thread-Topic: [MMUSIC] Comment on SIP Trickle ICE based on INFO draft - FORKING
Thread-Index: AQHPS/02PLTBD8bHIkyTiQF+pdjMC5r59hMAgAAnDLc=
Date: Sun, 30 Mar 2014 21:01:34 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D26C457@ESESSMB209.ericsson.se>
References: <7594FB04B1934943A5C02806D1A2204B1D26BE6A@ESESSMB209.ericsson.se>,  <53388068.1050209@jitsi.org>
In-Reply-To: <53388068.1050209@jitsi.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.147]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrLLMWRmVeSWpSXmKPExsUyM+Jvja5Bm0WwwcX/whZrdk5gsWi542Ux dfljFovJn/pYHVg8liz5yeTx/02gx4f5X9g9Ws71sgewRHHZpKTmZJalFunbJXBldO3byFpw U7Di6aqp7A2MN3m7GDk5JARMJOYc+cACYYtJXLi3nq2LkYtDSOAko8SJqwsYIZwljBL7Dv1h 7WLk4GATsJDo/qcNEhcR6GWU2LtuNgtInFlAXeLq4iCQQcICARLPv/1mAwmLCARKrLvHChIW EbCS+P9nFtguFgFVifUTJjOD2LwCvhI3fp0CiwsJZEl8O3GOEaSVU0BToudmGkiYEei076fW MIHYzALiEreezGeCOFlAYsme88wQtqjEy8f/wI6UEFCSmLY1DaJcR2LB7k9sELa2xLKFr6G2 CkqcnPmEZQKj2CwkU2chaZmFpGUWkpYFjCyrGCWLU4uLc9ONDPVy03NL9FKLMpOLi/Pz9IpT NzECo+zglt8aOxi7r9kfYpTmYFES562a2RkkJJCeWJKanZpakFoUX1Sak1p8iJGJg1OqgTHg cV35BOnPwct2ucp/vJt1olK+wvsRq8cxnrrFayeomL9mWS5780V128NDC5cknZee7K7l+rRJ VmbuRn4Bi8OtsrNtDnY94uEI+ZfmX6mzVWDl7Tau+ws9Hgo+46rV819gIbfmggZLvta8R/lP Wf+17Svqb+B80PZn2p9589/OWpd1zttcvliJpTgj0VCLuag4EQAZl9PrgAIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/Cyjiu1AzbvaibY-yTgQynSKQXmk
Cc: "mmusic@ietf.org" <mmusic@ietf.org>
Subject: Re: [MMUSIC] Comment on SIP Trickle ICE based on INFO draft - FORKING
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: Sun, 30 Mar 2014 21:01:42 -0000

Hi,

>>> 2) Trickle ICE INFO with serial forking
>>>
>>>    a) INVITE from local
>>>    b) INVITE is forked by proxy to first remote destination
>>>    c) 100 trying is reaching local
>>>    d) INFO with Trickle ICE from local
>>>    e) INFO is forward by proxy to first remote destination
>>>    f) INVITE is forked by proxy to second remote destination
>>>    g) Whether INFO has to be forked?
>>>
>>> It is not mentioned in the draft whether INFO has to be forked to the
>>> second remote destination as well. Could you please explain the expect
>>> behavior for this scenario.
>>
>> I am not sure what you mean by the INFO being forked.
>>
>> When a new fork is created (i.e. when the offerer receives a 18x respons=
e from a new destination), whatever candidates have been trickled on previo=
usly created fork(s) of course need to be provided also on the new fork.
>>
>> And, when multiple forks exist, whenever a new candidate is to be trickl=
ed, an INFO carrying the candidate needs to be sent on each fork.
>>
>> I don't see a problem with this, but if it is unclear in the spec then s=
ome additional text might be needed.
>
> Making sure we are on the same page:
>
> 1. These additional INFOs need to be trickled by the ICE agent that
> generated them in the first place.

Yes.

> 2. This would happen as an explicit step that is visible to the TU and
> the ICE agent. That is, it's not something that would be automatically
> handled by a SIP stack, by simply resending all the INFOs from the first
> prong of the fork to the second one.

It would be handled by the ICE agent.=20

>3. Those INFOs may or may not contain the same candidates (e.g. the
>agent may have chosen to use different port numbers for that prong) and
>they may or may not be the same number (e.g. if the agent is reusing
>addresses, it may decide to send them all in a single INFO, rather than
>in a sequence of INFOs).

Correct. The INFOs would contain whatever candiates are "valid" at that giv=
en point. The point was that, IF candidates have previously been trickled o=
n other forks, and they are still "valid", they need to be trickled also on=
 the new fork.

>Do we agree?

We always do :)

Regards,

Christer=


From nobody Sun Mar 30 15:00:53 2014
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 6CA641A07DC for <mmusic@ietfa.amsl.com>; Sun, 30 Mar 2014 15:00:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham
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 5X6FrvfU_6d5 for <mmusic@ietfa.amsl.com>; Sun, 30 Mar 2014 15:00:39 -0700 (PDT)
Received: from sesbmg20.ericsson.net (sesbmg20.ericsson.net [193.180.251.56]) by ietfa.amsl.com (Postfix) with ESMTP id ECFF91A0344 for <mmusic@ietf.org>; Sun, 30 Mar 2014 15:00:38 -0700 (PDT)
X-AuditID: c1b4fb38-b7f518e000000889-26-533894026274
Received: from ESESSHC019.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg20.ericsson.net (Symantec Mail Security) with SMTP id 20.BB.02185.20498335; Mon, 31 Mar 2014 00:00:35 +0200 (CEST)
Received: from ESESSMB209.ericsson.se ([169.254.9.213]) by ESESSHC019.ericsson.se ([153.88.183.75]) with mapi id 14.03.0174.001; Mon, 31 Mar 2014 00:00:34 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Emil Ivov <emcho@jitsi.org>, Parthasarathi R <partha@parthasarathi.co.in>
Thread-Topic: [MMUSIC] Comment on SIP Trickle ICE based on INFO draft
Thread-Index: AQHPRocL8dnxxOHFaUGVW6LszOxaAJruf3aAgAUpmQCAAElPgIAFdqWNgACWL4CAADN1hA==
Date: Sun, 30 Mar 2014 22:00:33 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D26C6D2@ESESSMB209.ericsson.se>
References: <01e601cf423c$57255890$057009b0$@co.in> <00c901cf4687$0a48dbb0$1eda9310$@co.in> <CAPvvaaKW+vxhJFqUPRZ-YfPQ4dHOS-=YwZaW+=NS3DttaaXD=Q@mail.gmail.com> <013601cf4923$754b35e0$5fe1a1a0$@co.in>,<53335D95.6000806@jitsi.org> <7594FB04B1934943A5C02806D1A2204B1D26BE29@ESESSMB209.ericsson.se>, <53387EE5.3050501@jitsi.org>
In-Reply-To: <53387EE5.3050501@jitsi.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.147]
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrLLMWRmVeSWpSXmKPExsUyM+JvjS7zFItgg0n3eSzW7JzAYtFyx8ti 6vLHLBaTP/WxOrB4LFnyk8nj/5tAjw/zv7B7tJzrZQ9gieKySUnNySxLLdK3S+DK2PF+A3PB F7uKUx1hDYzdhl2MHBwSAiYSDY1BXYycQKaYxIV769m6GLk4hASOMkpMa3rLCuEsYZSYuq+b DaSBTcBCovufNkiDiICvxO3trcwgNrNAnMTz2VfYQGxhAReJX0s2MEPUuEp8Xb6JHcIOk7j5 ZzFYnEVAVeLx0zNMIDYv0Jy2VyBxkF1nmCQ6tv4AG8QpoCnx7fEnRhCbEei676fWMEEsE5e4 9WQ+E8TVAhJL9pxnhrBFJV4+/scK8ZiSxLStaRDlBhLvz82HulNbYtnC18wQewUlTs58wjKB UWwWkqmzkLTMQtIyC0nLAkaWVYwcxanFSbnpRgabGIFRdHDLb4sdjJf/2hxilOZgURLn/fjW OUhIID2xJDU7NbUgtSi+qDQntfgQIxMHp1QDI7v5y9UzDmQei697L/Dl7VqbFqU5F98ni7z/ 3OpcnOpgk7DtlVOsdWzN3cbT9haeSs3sjYd3B6t9fHZGSd4rIme6q/7augmVq0vE3fJfXEsJ uRtz6F/Qn67Jd9kvF2tl+QiutCxMlOCcLHDJ5e2UgJmy9luUfyvOr/ob/Pz3p7btLLN0kgtv KLEUZyQaajEXFScCAKAjaORwAgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/mmusic/qSP-BdN-Hec-F9QC3y_97VFo580
Cc: 'mmusic' <mmusic@ietf.org>
Subject: Re: [MMUSIC] Comment on SIP Trickle ICE based on INFO draft
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: Sun, 30 Mar 2014 22:00:51 -0000

Hi,

>> I have tried to understand the whole issue discussed here, with little s=
uccess :)
>>
>> So, rather than trying to come up with a solution, I think we first need=
 to agree on some basic assumptions.
>>
>> If we claim that Trickle ICE has no impact on the SDP O/A state, then:
>>
>> 1) There should be no need to figure out whether an INFO is sent before =
an UPDATE; and
>
> That's not exactly true because, like ICE, trickle ICE does depend on
> O/A in order to operate. In other words: if you change your location and
> do a new Offer/Answer, you don't expect vanilla ICE to magically
> continue, blissfully ignorant of that fact. It needs to restart and so
> does Trickle ICE.

Ok, I hear what you are syaing. You need a way to indicate whether the tric=
kled candidates are pre-restart or not.

>> 2) There should be no need to include the o=3D line, or any other inform=
ation that binds the INFO to a specific SDP O/A state.
>
> The main reason you need that is so that you can drop stray INFOs that
> have been delayed and have arrived when the ICE processing context they
> were related to is no longer valid (i.e. after an ICE restart).
>
> But I agree that an o=3D line is not the most convenient way to handle
> this and using ice-ufrag and ice-pwd would be better.

Or, some part of the o=3D line.

Keep in mind that you don't need to put everything in the INFO message body=
. You can also define parameters associated with the info package.

>>> Instead, Trickle ICE is only a mechanism to transport candidate informa=
tion from one endpoint to another.
>>
>> Agreed.
>>
>> Endpoints may of course add those candidates to subsequent Offer/Answers=
.
>
>This should be clarified. I think it's not necessary. Basically an O/A
>can have the following two possible relations to trickle ICE:
>
>1. ICE restart: (ice-ufrag and ice-pwd have changed). This basically
>means that your addressing situation has most likely changed and you
>need to start everything from scratch. So you do.
>
>2. Non-ICE session modification: you are currently doing ICE and while
>you are at it, you change some aspect of your session that has
>no-relation to addressing. For example, you add formats, change the
>direction of a stream, or something like that. In this case trickle ICE
>continues with no modification.
>
>Case 1 obviously doesn't need any of the trickle candidates but they can
>be included if the agent is comfortable reusing them. This is compatible
>with 5245 which says something like this:
>
>    If ICE is restarting [...] the set of candidates MAY include some,
>    none, or all of the previous candidates for that stream and MAY
>    include a totally new set of candidates
>
>Case 2 is less obvious to me. Requiring agents to include all currently
>known addresses sounds a bit risky to me because it's easy to get into
>situations where an agent receives a set of candidates that does not
>match its current view of the session:
>
>Case 2.1: New candidates appear
>Case 2.2: Some candidates are not there.
>
>Case 2.1 is easy to handle: the new candidates are handled as if they
>were trickled.
>
>Case 2.2 is kind of a headache. 5245 says that it MUST NOT happen but I
>don't think this can be guaranteed because various race conditions may
>cause trickled candidates to arrive before the O/A and make an agent
>believe that some of them are lacking.
>
>I think the easiest way to handle this would be to say that, when using
>Trickle ICE, candidates and addressinf information from offers that DO
>NOT restart ICE MUST be ignored.

Well, you can't ignore the "ice completed" Offer, can you?

Regards,

Christer



> ________________________________________
> From: Emil Ivov [emcho@jitsi.org]
> Sent: Thursday, 27 March 2014 1:07 AM
> To: Parthasarathi R
> Cc: 'mmusic'; Christer Holmberg; 'Enrico Marocco (TiLab)'
> Subject: Re: [MMUSIC] Comment on SIP Trickle ICE based on INFO draft
>
> On 26.03.14, 19:44, Parthasarathi R wrote:
>>   > > This race condition is very much possible during
>>   > > early
>>   > > dialog scenarios with UPDATE.
>>   > >
>>   > > Could you please explain how SIP trickle ICE using INFO works for
>>   > >
>>   > > 1) UPDATE from remote before Trickle ICE is completed
>>
>> This is analogous to an UPDATE that is received before regular 5245 ICE
>> processing has completed.
>>
>> <Partha> No, in case UDPATE before the offer is completed, 491 response
>> will send out whereas it will not happen in case of INFO </Partha>
>
> I think you might be confusing "before ICE processing has completed" and
> "before O/A has completed"
>
> An UPDATE that is received while "vanilla ICE processing is in progress"
> would have exactly the same effect as an UPDATE received while "trickle
> ICE processing is in progress". If O/A has completed then the UPDATE
> will NOT cause a 491 in either case.
>
>>   > >     a) INVITE from local
>>   > >     b) 183 session progress from remote
>>   > >     c) PRACK from local
>>   > >     d) INFO from local (relay candidates)
>>   > >     e) UPDATE from remote
>>   > >
>>   > > Here, the remote has to consider whether INFO belongs to UPDATE or
>>   > > INVITE as
>>   > > it is possible for INFO to reach before 200 OK for UPDATE as well =
in
>>   > > the
>>   > > same sequence.
>>
>> And CSeq headers wouldn't help here because ....?
>>
>>   > > Also, RFC 2976
>>
>> which FWIW is obsoleted by RFC6086
>>
>> <Partha> Thanks..I still majorly interwork with RFC 2976 implementation
>> :-( but please note that RFC 6086 does not change much in these SIP
>> dialog or session aspects. The exact snippet of RFC 6086 is as follows:
>>
>> =93Note that the INFO method is not used to update characteristics of a
>>      SIP dialog or session, but to allow the applications that use the S=
IP
>>      session to exchange information (which might update the state of
>>      those applications).=94
>
> Trickle ICE does not update the characteristics of a SIP dialog and I
> don't believe it violates the above in any way.
>
>>   > > " - The extensions that use the INFO message MUST NOT rely on the
>>   > >      INFO message to do anything that effects the SIP call state o=
r the
>>   > >      state of related sessions."
>>
>> And I don't believe that it does.
>>
>> <Partha> No, it is not possible to implement this draft without impact
>> offer/answer state machine </Partha>
>
> Please provide an example where you think it actually breaks something.
> (It might be worth waiting until we submit the new version, which should
> probably clarify a few things).
>
>>   > > 2) Trickle ICE INFO with serial forking
>>
>> INFO requests are sent within a dialog. They will go through the prong
>> associated with that dialog and would not be forked.
>>
>> <Partha> IOW, Trickle ICE INFO will be buffered till 18x response is
>> received. So, INFO has no much advantage compare to UPDATE except for
>> the non-reliable response scenario.
>
> No advantage? INFOs can be send in both directions and arrive completely
> asynchronously without ever causing glare or without having to worry
> whose turn it is to send an offer or an answer because you need to
> piggyback candidates on top of it.
>
> We've been through this exact same argument several times already, you
> haven't pointed out any flaws with this logic so I can't see a reason
> why you keep coming back to it.
>
> You claim you are worried about needing to modify the offer/answer state
> machine in your implementation, but that is a very strange argument
> since that implementation would be much more heavily impacted if you
> were to try and trickle with offers and answers.
>
> I think the source of the confusion might be the fact that the draft is
> currently in a relatively poor state, which is my fault, and I am
> hopeful that you may find many of your answers in the next version.
>
> Emil=

