IETF Logo Mail Archive

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

Iñaki Baz Castillo <ibc@aliax.net> Tue, 12 November 2013 00:59 UTC

Return-Path: <ibc@aliax.net>
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 33B2C11E8145 for <rtcweb@ietfa.amsl.com>; Mon, 11 Nov 2013 16:59:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.677
X-Spam-Level:
X-Spam-Status: No, score=-2.677 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
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 iBSxmWXnZWro for <rtcweb@ietfa.amsl.com>; Mon, 11 Nov 2013 16:59:05 -0800 (PST)
Received: from mail-qe0-f54.google.com (mail-qe0-f54.google.com [209.85.128.54]) by ietfa.amsl.com (Postfix) with ESMTP id C118421E80C1 for <rtcweb@ietf.org>; Mon, 11 Nov 2013 16:59:05 -0800 (PST)
Received: by mail-qe0-f54.google.com with SMTP id 1so5194477qec.13 for <rtcweb@ietf.org>; Mon, 11 Nov 2013 16:59:05 -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=eBRasLvvzCJrN5ivStqOtPMtvFsAARJVwHVm7s+LGMw=; b=Iu9R+TMlR55NNe13KmmDPSe/2/yY5wIZ+Y/Gep8yJciLUBpYgAWVTckd44OmwGIWhP E6tdPEPZiWFPKZnbFd/R6Fq03cXS8hfVctRRSHQzT/zwtdY46f6ftt3TKuYbSyXdsvDv 3EMWT0bN1n0tQOLqaMGH/aCDW1V/H0Smw9El1jn84/DucKmoSXrhLKjAfLLvwbLNSOxX Tj8hEbu5eSk+weYXAdssNgrBlKqw3/MD7gq9wezDZg5Qys/4T1nCXg2X4+mRbS5B2Fbi UDcmw0efKLUXo63dNgVL4LO1qNqNGvo9EnMhYZMuDTqqQ0NOmv0pN8fNmg/BngYE7fAL Gv6w==
X-Gm-Message-State: ALoCoQl/e/ysfYbu88a1OxAzddvCVweZfvcbuif2ktKnwedPZtiSm+ZxXm4IFTAmvNhzUMBtrLAO
X-Received: by 10.224.36.201 with SMTP id u9mr54084929qad.76.1384217945093; Mon, 11 Nov 2013 16:59:05 -0800 (PST)
MIME-Version: 1.0
Received: by 10.96.71.8 with HTTP; Mon, 11 Nov 2013 16:58:45 -0800 (PST)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1C5167D2@ESESSMB209.ericsson.se>
References: <CALiegfn0mrYe2V8pWUmOCgxXWDp_8DTKJmh1Fuadu+vi1e+pOA@mail.gmail.com> <20131111191712.59e4e44d@lminiero> <CAOJ7v-0FLKQgGKHA5soJNhAja2aNgGNi-ZouBhTaOPCkcq_e3w@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1C5167D2@ESESSMB209.ericsson.se>
From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Tue, 12 Nov 2013 01:58:45 +0100
Message-ID: <CALiegfku7J75JcSTRrv_SuHcG0+jXk+GfbdM0hE4ZF0rg-rZEQ@mail.gmail.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>
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: Tue, 12 Nov 2013 00:59:10 -0000

Clear. Thanks to all.

2013/11/12 Christer Holmberg <christer.holmberg@ericsson.com>:
> 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
>



-- 
Iñaki Baz Castillo
<ibc@aliax.net>

v2.23.0 | Report a Bug | By Email