Re: [rtcweb] No-Bundle in just one peer

Lorenzo Miniero <lorenzo@meetecho.com> Wed, 13 November 2013 11:22 UTC

Return-Path: <lorenzo@meetecho.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 14A4121F9EAF for <rtcweb@ietfa.amsl.com>; Wed, 13 Nov 2013 03:22:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.479
X-Spam-Level:
X-Spam-Status: No, score=-0.479 tagged_above=-999 required=5 tests=[AWL=-0.060, BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hifU8B1Lo9W1 for <rtcweb@ietfa.amsl.com>; Wed, 13 Nov 2013 03:22:50 -0800 (PST)
Received: from smtpdg96.aruba.it (smtpdg5.aruba.it [62.149.158.235]) by ietfa.amsl.com (Postfix) with ESMTP id E013621E80CE for <rtcweb@ietf.org>; Wed, 13 Nov 2013 03:22:49 -0800 (PST)
Received: from lminiero ([143.225.229.166]) by smtpcmd05.ad.aruba.it with bizsmtp id ozNm1m0193c3Lvj01zNmKv; Wed, 13 Nov 2013 12:22:47 +0100
Date: Wed, 13 Nov 2013 12:22:46 +0100
From: Lorenzo Miniero <lorenzo@meetecho.com>
To: =?UTF-8?B?ScOxYWtp?= Baz Castillo <ibc@aliax.net>
Message-ID: <20131113122246.366813a3@lminiero>
In-Reply-To: <CALiegfku7J75JcSTRrv_SuHcG0+jXk+GfbdM0hE4ZF0rg-rZEQ@mail.gmail.com>
References: <CALiegfn0mrYe2V8pWUmOCgxXWDp_8DTKJmh1Fuadu+vi1e+pOA@mail.gmail.com> <20131111191712.59e4e44d@lminiero> <CAOJ7v-0FLKQgGKHA5soJNhAja2aNgGNi-ZouBhTaOPCkcq_e3w@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1C5167D2@ESESSMB209.ericsson.se> <CALiegfku7J75JcSTRrv_SuHcG0+jXk+GfbdM0hE4ZF0rg-rZEQ@mail.gmail.com>
Organization: Meetecho
X-Mailer: Claws Mail 3.9.2 (GTK+ 2.24.19; x86_64-redhat-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] No-Bundle in just one peer
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Nov 2013 11:22:55 -0000

Il giorno Tue, 12 Nov 2013 01:58:45 +0100
Iñaki Baz Castillo <ibc@aliax.net> ha scritto:

> Clear. Thanks to all.
> 


Thanks Justin and Christer for the clarification (I just did my bundle
catchup reading the draft and MMUSIC posts, mea culpa!) and sorry Iñaki
for the misinformation. ;-)

Lorenzo


> 2013/11/12 Christer Holmberg <christer.holmberg@ericsson.com>om>:
> > Hi,
> >
> >
> >
> > Justin is correct.
> >
> >
> >
> > At one point we made a decision, that either both endpoints do
> > BUNDLE, or no endpoint does BUNDLE.
> >
> >
> >
> > A, not supporting BUNDLE, may not like receiving an SDP Answer from
> > B with a shared address assigned to multiple m- lines.
> >
> >
> >
> > Regards,
> >
> >
> >
> > Christer
> >
> >
> >
> >
> >
> > Lähettäjä: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org]
> > Puolesta Justin Uberti
> > Lähetetty: 11. marraskuuta 2013 23:04
> > Vastaanottaja: Lorenzo Miniero
> > Kopio: rtcweb@ietf.org
> > Aihe: Re: [rtcweb] No-Bundle in just one peer
> >
> >
> >
> > No, B cannot BUNDLE if A is not BUNDLEing. There are a number of
> > corner cases where things don't work right in the situation
> > described above.
> >
> >
> >
> > On Mon, Nov 11, 2013 at 10:17 AM, Lorenzo Miniero
> > <lorenzo@meetecho.com> wrote:
> >
> > Il giorno Mon, 11 Nov 2013 19:12:01 +0100
> > Iñaki Baz Castillo <ibc@aliax.net> ha scritto:
> >
> >
> >> Hi,
> >>
> >> In case peer A sends a SPD without Bundle support (so it needs to
> >> receive incoming tracks in separate ports and send tracks from
> >> separate ports) does it aslo mean that peer B must not use Bundle?
> >> Or could peer A use two local ports (no Bundle) to send/receive
> >> tracks to/from a single port in peer B?
> >>
> >> Thanks a lot.
> >>
> >> --
> >> Iñaki Baz Castillo
> >> <ibc@aliax.net>
> >
> > Hi Iñaki,
> >
> > not sure what the spec currently mandates, but this works already in
> > existing implementations. Peer A just needs to do the ICE and DTLS
> > dance twice from its two ports towards the single port in B (twice
> > or more, in case you're not muxing RTCP either).
> >
> > Lorenzo
> > _______________________________________________
> > rtcweb mailing list
> > rtcweb@ietf.org
> > https://www.ietf.org/mailman/listinfo/rtcweb
> >
> >
> >
> >
> > _______________________________________________
> > rtcweb mailing list
> > rtcweb@ietf.org
> > https://www.ietf.org/mailman/listinfo/rtcweb
> >
> 
> 
>