Re: [rtcweb] No Plan

Emil Ivov <emcho@jitsi.org> Sat, 01 June 2013 05:40 UTC

Return-Path: <emil@sip-communicator.org>
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 2F95121F8916 for <rtcweb@ietfa.amsl.com>; Fri, 31 May 2013 22:40:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.139
X-Spam-Level:
X-Spam-Status: No, score=-2.139 tagged_above=-999 required=5 tests=[AWL=0.460, BAYES_00=-2.599]
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 EP6GaNaD9eWc for <rtcweb@ietfa.amsl.com>; Fri, 31 May 2013 22:40:11 -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 1DE6521F88FB for <rtcweb@ietf.org>; Fri, 31 May 2013 22:40:10 -0700 (PDT)
Received: by mail-ee0-f44.google.com with SMTP id b57so257177eek.3 for <rtcweb@ietf.org>; Fri, 31 May 2013 22:40:09 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding:x-gm-message-state; bh=g5KqXuiiKIk9RK+kTTDj+EEru6/WXTy/Lo9Znwnm/Rc=; b=DFj6BEL3Ps4SHOW+i3xylDdK2EYdwNr29+7mcFD7BoEDbrrzjJZoVb2zOCyS67zYFD q8av7FgkiS5COWUrjV0MjmPAV1scAvzHBx76ybGv2HE1hV7e3+HuvihL1nXxjbm7xzeI uKSQIzQyNWQzgHSR3KFP8148Tghs8M2FFsZA5bVVBozN3aJm/Y24Ccn94QFJsz2GigmO 8lKZ4+tQAMgLCZRxu6HQIVnqyLFwa214dRqsFBFe1MlUt9HisO0vhH0yhNlPYK7CwY6t e7BNCmFBd53XgCkg5VOnBWkD/qYGYD+aQHWFm1pAZKMx1Ni6EYmVwtAFdHPkvhFsijb0 eItw==
X-Received: by 10.14.174.8 with SMTP id w8mr15761459eel.115.1370065208846; Fri, 31 May 2013 22:40:08 -0700 (PDT)
Received: from camionet.local ([83.228.77.158]) by mx.google.com with ESMTPSA id b14sm516790ees.16.2013.05.31.22.40.07 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 31 May 2013 22:40:08 -0700 (PDT)
Message-ID: <51A98934.3000103@jitsi.org>
Date: Sat, 01 Jun 2013 08:40:04 +0300
From: Emil Ivov <emcho@jitsi.org>
Organization: Jitsi
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
References: <51A65017.4090502@jitsi.org> <51A65DB8.9060702@alum.mit.edu> <51A880A7.7010908@jitsi.org> <51A8F5D8.8070602@alum.mit.edu>
In-Reply-To: <51A8F5D8.8070602@alum.mit.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Gm-Message-State: ALoCoQnuKWvOlEYbdhWBEXGFxFJYj8Cuv5fXi2nRzlQG8VpH8XOd61V6OS2GHqdfw4OHMSbpfKwM
Cc: rtcweb@ietf.org
Subject: Re: [rtcweb] No Plan
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: Sat, 01 Jun 2013 05:40:12 -0000

On 31.05.13, 22:11, Paul Kyzivat wrote:
> On 5/31/13 6:51 AM, Emil Ivov wrote:
>> Hey Paul,
>>
>> On 29.05.13, 22:57, Paul Kyzivat wrote:
>>> Emil,
>>>
>>> I'm going to reserve judgment on this pending further discussion.
>>> I think this *might* work for CLUE, but I want to be certain.
>>
>> Sure!
>>
>>> I'm concerned with decomposed endpoints that can't manage all the
>>> streams on the same address/port. They will need multiple independent
>>> m-lines and/or bundle groups.
>>
>> This is obviously open for debate but the general idea of No Plan is
>> that: Offer/Answer is used for configuring media and RTP stacks and
>> additional signalling is not the browser's concern.
>>
>> Having extra m= lines, particularly when using BUNDLE, is in many ways
>> just extra signalling.
>
> You may be able to argue that adding extra m-lines into an existing
> bundle is "just extra signaling". But introducing an additional 5-tuple
> is more substantial. It requires configuring a new RTP stack and media.

Indeed, this would require BUNDLE to work.

Emil


>
> 	Thanks,
> 	Paul
>
>> If you'd like for that signalling to be in SDP, I
>> don't see any problem with it. However it would be best for this extra
>> layer of SDP signalling to appear at either the application layer or in
>> a signalling gateway (that is going to be there anyway).
>>
>> Does this make sense?
>>
>> Emil
>>
>>>
>>> Further questions:
>>>
>>> I presume that you expect bandwidth in the SDP to be an aggregate
>>> per-m-line, with application specific signaling for bandwidth at the
>>> per-RTP-stream level?
>>>
>>>      Thanks,
>>>      Paul
>>>
>>> On 5/29/13 2:59 PM, Emil Ivov wrote:
>>>> Hey all,
>>>>
>>>> Based on many of the discussions that we've had here, as well as many
>>>> others that we've had offlist, it seemed like a good idea to investigate
>>>> a negotiation alternative that relies on SDP and Offer/Answer just a
>>>> little bit less.
>>>>
>>>> The following "no plan" draft attempts to present one such approach:
>>>>
>>>> http://tools.ietf.org/html/draft-ivov-rtcweb-noplan
>>>>
>>>> The draft relies on conventional use of SDP O/A but leaves the
>>>> intricacies of multi-source scenarios to application-specific
>>>> signalling, with potentially a little help from RTP.
>>>>
>>>> Hopefully, proponents of Plans A and B would find that the
>>>> interoperability requirements that concerned them can still be met with
>>>> "no plan". Of course they would have to be addressed by
>>>> application-specific signalling and/or signalling gateways.
>>>>
>>>> Comments are welcome!
>>>>
>>>> Cheers,
>>>> Emil
>>>>
>>>
>>> _______________________________________________
>>> rtcweb mailing list
>>> rtcweb@ietf.org
>>> https://www.ietf.org/mailman/listinfo/rtcweb
>>> .
>>>
>>
>
> .
>

-- 
https://jitsi.org