Re: [rtcweb] #13: Transport of DATA_CHANNEL_OPEN

Matthew Kaufman <matthew@matthew.at> Fri, 26 April 2013 13:56 UTC

Return-Path: <matthew@matthew.at>
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 E1A0021F9742 for <rtcweb@ietfa.amsl.com>; Fri, 26 Apr 2013 06:56:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.429
X-Spam-Level:
X-Spam-Status: No, score=-1.429 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HELO_EQ_AT=0.424, HOST_EQ_AT=0.745, HTML_MESSAGE=0.001]
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 YBOEHncaUAWZ for <rtcweb@ietfa.amsl.com>; Fri, 26 Apr 2013 06:55:59 -0700 (PDT)
Received: from where.matthew.at (where.matthew.at [198.202.199.1]) by ietfa.amsl.com (Postfix) with ESMTP id E319A21F9017 for <rtcweb@ietf.org>; Fri, 26 Apr 2013 06:55:59 -0700 (PDT)
Received: from [10.10.155.2] (unknown [10.10.155.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by where.matthew.at (Postfix) with ESMTP id 9767A230005 for <rtcweb@ietf.org>; Fri, 26 Apr 2013 06:55:59 -0700 (PDT)
Message-ID: <517A8772.4090906@matthew.at>
Date: Fri, 26 Apr 2013 06:56:02 -0700
From: Matthew Kaufman <matthew@matthew.at>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <066.3120a55540cacaa74ee5fda0b5273a48@trac.tools.ietf.org> <5174C8D2.40504@matthew.at> <5177F7EE.1010909@matthew.at> <CAJrXDUGa1=Nqq9WPL57=OkUU9mG7yHz0uzG1KncS8yVzbSAM0A@mail.gmail.com> <AE1A6B5FD507DC4FB3C5166F3A05A484162816C1@tk5ex14mbxc272.redmond.corp.microsoft.com> <517A1102.1010906@alvestrand.no>
In-Reply-To: <517A1102.1010906@alvestrand.no>
Content-Type: multipart/alternative; boundary="------------050202090408000906040203"
Subject: Re: [rtcweb] #13: Transport of DATA_CHANNEL_OPEN
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: Fri, 26 Apr 2013 13:56:01 -0000

On 4/25/2013 10:30 PM, Harald Alvestrand wrote:
> On 04/25/2013 07:28 AM, Matthew Kaufman (SKYPE) wrote:
>>
>> It is a much simpler question as there's only a couple of options 
>> left... how about we throw it on the floor? That seems safest to me.
>>
>> I'd still love to hear why it is "needed" though.
>>
>
> The fact that Matthew doesn't want to accept the arguments for why it 
> is needed doesn't seem relevant to me.

Until Randell's message arrived a few hours before yours, there was no 
concise summary of why it might be needed.

Never mind that your personal view as to whether or not to just ignore 
my technical arguments offhand because they're sent by me is hardly 
relevant to the rest of the working group.

>
> I think people have said enough times that they see value in the label 
> concept, and they want some way to carry it. The OPEN message is a 
> simple way to fill that need (and also makes some other aspects of 
> setup simpler than they would otherwise be).
>
>

And as I pointed out in my original message on this topic, which until 
Randell's message was met with silence, the only thing that made sense 
to me was the label field, and yet the label can be null, so might also 
be useless.

Matthew Kaufman