Re: [rtcweb] Locus of API discussion

Peter Thatcher <pthatcher@google.com> Fri, 12 July 2013 14:37 UTC

Return-Path: <pthatcher@google.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 AC0C921F9F86 for <rtcweb@ietfa.amsl.com>; Fri, 12 Jul 2013 07:37:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.942
X-Spam-Level:
X-Spam-Status: No, score=-1.942 tagged_above=-999 required=5 tests=[AWL=0.035, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-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 RCPdoKeggLxZ for <rtcweb@ietfa.amsl.com>; Fri, 12 Jul 2013 07:37:11 -0700 (PDT)
Received: from mail-pa0-x236.google.com (mail-pa0-x236.google.com [IPv6:2607:f8b0:400e:c03::236]) by ietfa.amsl.com (Postfix) with ESMTP id E856121F9AC4 for <rtcweb@ietf.org>; Fri, 12 Jul 2013 07:37:10 -0700 (PDT)
Received: by mail-pa0-f54.google.com with SMTP id kx10so9041172pab.13 for <rtcweb@ietf.org>; Fri, 12 Jul 2013 07:37:10 -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=lf2g4pacBSFfZ8osAi03KsTgga0WzYj8Yvhx4/LFaro=; b=OZrJBKr6v8BmNhCwLOJdnx4NKQZ1N7G9AswV4PIcCc6G/HTOYUrkyTU9yDbnaxMOwq ZNV0MmVXTrKnlfN+Mi8zv6URu5yuGrej25KdoMo8FpLXatTSuRr4NqiPzvSiDR3E3dhz 5JOsUNI569PPuxQSMuHeHcHxWP0ECPWh0CsFubr44Pw+hiSyHlREPHmb2fMCynB7x5eR 9hp6hQ9JPZrK7W6Ytj+VhUZxTpToxdlX1kRdy0lgmZzsy03Dv0JQHKpCtTHAsx5zWgsk 33uTHKjl1n9AcSqy041XRW0kFtYltzwPABOY8/fT6Kru5/MYSMmpih8A9GYDhX7HL265 HqZw==
X-Google-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:x-gm-message-state; bh=lf2g4pacBSFfZ8osAi03KsTgga0WzYj8Yvhx4/LFaro=; b=pneJ4HCiT13O+C7e9GjbKUq7sMI4FPS8WpvYMTFFj89EzK66x2bfEjHV+qkmWoos0Q QV62tPTrhuorr0WFMOLKJhyBLrDWzhXPeVZ5OE1z7ALA5yauPZSDIRkEiNuXrKp5o7Tv VoZkDEl4lKYbs689HJjmRkE+Lr6fCZ4zZtpsPcCyXWxj036i7pyVdtaad+XQl8Il7kVG eZtgjC/+gTAYGiEkLw2wITDqWoXIZO0XHWwbcf0mtkwFsdKoXRjPANfdsG0dQ0PvnmHE r3Fj0Q4DdqL0r/yFH1cO1l94VI+fPBFHk1BvJ8AF+QGyNWMubyo+Z2GLpfmA8zbYr/la Hl0w==
X-Received: by 10.68.219.130 with SMTP id po2mr41932489pbc.54.1373639830523; Fri, 12 Jul 2013 07:37:10 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.66.78.169 with HTTP; Fri, 12 Jul 2013 07:36:30 -0700 (PDT)
In-Reply-To: <CABcZeBPC2FUZ+oCSNVHwAqzrSar=wTqz0AGZ6YqpoOfJjy0qSg@mail.gmail.com>
References: <CA+9kkMAaaT5RRLUrGvzs0zB0jXRQdHLm5HJH5-VkT5p1ZetVPQ@mail.gmail.com> <51DC3644.4020107@bbs.darktech.org> <CABcZeBPC2FUZ+oCSNVHwAqzrSar=wTqz0AGZ6YqpoOfJjy0qSg@mail.gmail.com>
From: Peter Thatcher <pthatcher@google.com>
Date: Fri, 12 Jul 2013 07:36:30 -0700
Message-ID: <CAJrXDUFhwgehsqxX6yirmtnaStEOKtYVcLnswAOd6V=9nxwSwQ@mail.gmail.com>
To: Eric Rescorla <ekr@rtfm.com>
Content-Type: multipart/alternative; boundary=e89a8ff2488125ead604e15172a5
X-Gm-Message-State: ALoCoQkepIVwodZWvq/eo7Xwz7DohCaerqwdg96fbaugdZxeI91ih/Rjqg79azit/qwnFR2hJu2khqvWWDGDy9BpdXumCR7gcyR9RJNzyZoXp8cVsOJjRJ5YN1cn6z+CDn4c1PYCbIrBVPzmMc4YldDdrSRLPLryBaG+y2is9HxkkP7CXq6dUCd/PvNPUpCSCou1tKijNj/n
Cc: cowwoc <cowwoc@bbs.darktech.org>, "rtcweb@ietf.org" <rtcweb@ietf.org>, "public-webrtc@w3.org" <public-webrtc@w3.org>
Subject: Re: [rtcweb] Locus of API discussion
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, 12 Jul 2013 14:37:11 -0000

A minor correction:  I haven't engaged anyone on public-webrtc.  I didn't
even realize there were discussions going on over there about the API,
since I wasn't keeping track and I thought they were all going on over
here.  Sorry about that.  I guess I'll head over there and start engaging
:).


On Tue, Jul 9, 2013 at 1:40 PM, Eric Rescorla <ekr@rtfm.com> wrote:

>
>
>
> On Tue, Jul 9, 2013 at 9:11 AM, cowwoc <cowwoc@bbs.darktech.org> wrote:
>
>> On 09/07/2013 11:33 AM, Ted Hardie wrote:
>>
>>> Howdy,
>>>
>>> The recent set of API discussions has been spread across both the rtcweb
>>> and public-webrtc mailing lists.  That's making it both harder to follow
>>> and harder for folks to work out who is saying what under which rules.  The
>>> chairs of both groups believe that the right place for the discussion to
>>> continue should be public-webrtc.  Please direct follow-ups on this topic
>>> to that list.
>>>
>>> regards,
>>>
>>> Ted Hardie
>>>
>> Ted,
>>
>>     I agree, with one caveat: virtually none of the high-level
>> stakeholders (spec editors, browser vendors, etc) bother to engage the
>> community on public-webrtc.
>>
>
> I'm not sure I understand this complaint. Is it that the aforementioned
> "high-level stakeholders"
> aren't engaging or merely that they are only engaging on RTCWEB? If it's
> the former, than
> I don't think that's actually true, since in the past week, you've had
> responses from (at least)
> the following people who fall into those categories:
>
> Cullen Jennings (spec editor)
> Adam Bergqvist (spec editor)
> Peter Thatcher (works on Chrome)
> Me (works on Firefox and Chrome; spec editor)
> Christer Holmberg (spec editor)
> Several people from Microsoft.
>
> Who, exactly, are you expecting to engage that hasn't engaged?
>
>
> If your complaint is just that they're engaging on the wrong mailing list,
> well
> that seems to reinforce Ted's point above.
>
> -Ekr
>
>
>
>
>     What's the point of discussing the API on this mailing list if our
>> opinion goes unnoticed? We shouldn't be moving the discussion to
>> public-webrtc as a nice way to filter us out. This discussion requires
>> their attention, be it on one mailing list or the other. I don't mind where
>> we discuss it, so long as they get involved.
>>
>>     Is it their intention to get involved on public-webrtc and summarize
>> the results on rtcweb?
>>
>> Thanks,
>> Gili
>>
>>
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>
>