Re: [rtcweb] Locus of API discussion

Ted Hardie <ted.ietf@gmail.com> Wed, 17 July 2013 22:40 UTC

Return-Path: <ted.ietf@gmail.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 5A1DA21F9C28 for <rtcweb@ietfa.amsl.com>; Wed, 17 Jul 2013 15:40:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.328
X-Spam-Level:
X-Spam-Status: No, score=-2.328 tagged_above=-999 required=5 tests=[AWL=0.271, BAYES_00=-2.599, 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 tpK0a3bCM8jy for <rtcweb@ietfa.amsl.com>; Wed, 17 Jul 2013 15:40:37 -0700 (PDT)
Received: from mail-ie0-x231.google.com (mail-ie0-x231.google.com [IPv6:2607:f8b0:4001:c03::231]) by ietfa.amsl.com (Postfix) with ESMTP id 1229421F9D4F for <rtcweb@ietf.org>; Wed, 17 Jul 2013 15:40:36 -0700 (PDT)
Received: by mail-ie0-f177.google.com with SMTP id aq17so5229818iec.8 for <rtcweb@ietf.org>; Wed, 17 Jul 2013 15:40:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Gv4nBqgcBEezlSwEzpLcyLS98CJAEARUozL3m3Hq2zU=; b=FlkZxeUnUbGgQzt/y95vaLfh3L/iqTAz1tiH4YEj7vt+xZXbpi+b8yAkyL0PgeXbpq h/swh0G8lJES5wyWhMPPH8fiOn0eNvLnAEUF7uVPC0kvCgNAIc2ceNI9cCV55iGk5Qep WObfYECnrZ6BqVT7+Oe/KBD7+FV7TgnmsxNe7ftTFfohrLeTBTLEvNtzaVHxiRwj/33K 2x/x+Z70zE9sdTP8SjI/qhfDGk9Q1ngE6rQJTqh8PMYgJfgtfk6lVYU8ptn3ZV0CIe0t SmaNzDutUolbcDWre7ISgUmUhwHnMhvJsrC/uL06Gf9iwOLVw9+Dk6tLyQ3cNzBcAotX mpLA==
MIME-Version: 1.0
X-Received: by 10.43.67.73 with SMTP id xt9mr5476719icb.99.1374100836377; Wed, 17 Jul 2013 15:40:36 -0700 (PDT)
Received: by 10.42.29.202 with HTTP; Wed, 17 Jul 2013 15:40:36 -0700 (PDT)
In-Reply-To: <AE1A6B5FD507DC4FB3C5166F3A05A484213E3F2D@TK5EX14MBXC265.redmond.corp.microsoft.com>
References: <CA+9kkMAaaT5RRLUrGvzs0zB0jXRQdHLm5HJH5-VkT5p1ZetVPQ@mail.gmail.com> <AE1A6B5FD507DC4FB3C5166F3A05A484213E3F2D@TK5EX14MBXC265.redmond.corp.microsoft.com>
Date: Wed, 17 Jul 2013 15:40:36 -0700
Message-ID: <CA+9kkMBnVEHXyOHLu+F7x=NOhDkm6gU013Hc=W-9F7wJ4EWs0g@mail.gmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
To: "Matthew Kaufman (SKYPE)" <matthew.kaufman@skype.net>
Content-Type: multipart/alternative; boundary=089e015370963e3d4a04e1bcc86a
Cc: "rtcweb@ietf.org" <rtcweb@ietf.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: Wed, 17 Jul 2013 22:40:38 -0000

On Wed, Jul 17, 2013 at 2:29 PM, Matthew Kaufman (SKYPE) <
matthew.kaufman@skype.net> wrote:

>
> I am frankly quite concerned given earlier comments that yes, the W3C had
> given responsibility for "JSEP" and the resulting SDP work to IETF, and so
> now we have the IETF WG making decisions but the discussion happening on
> the W3C list -- which means there's no "paper trail" prior to the IETF
> meeting on an IETF list about how the participants have weighed in -- and
> then conversely when the W3C spec gets to last call there will be no "paper
> trail" at the W3C showing how decisions had been reached about the SDP
> "API", as that happened over in the MMUSIC WG, which list was not even
> copied on this message.
>
>
All three lists you cited have public archives, so it is clearly not the
case that there is no "paper trail".   But it does occasionally get
confusing, and the chairs made the "locus of API discussions" point in
order to take a particular set of discussions proposing a significant
change to the API and reduce the number of places someone who have to
follow to contribute to that discussion.

I grieve that this has disappointed you,

Ted