Re: [rtcweb] Locus of API discussion

"Matthew Kaufman (SKYPE)" <matthew.kaufman@skype.net> Tue, 09 July 2013 18:05 UTC

Return-Path: <matthew.kaufman@skype.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 7EA6B21F9EE5 for <rtcweb@ietfa.amsl.com>; Tue, 9 Jul 2013 11:05:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.445
X-Spam-Level:
X-Spam-Status: No, score=-3.445 tagged_above=-999 required=5 tests=[AWL=0.153, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 XkW1gt+1ViT6 for <rtcweb@ietfa.amsl.com>; Tue, 9 Jul 2013 11:05:00 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0243.outbound.protection.outlook.com [207.46.163.243]) by ietfa.amsl.com (Postfix) with ESMTP id 1ECE521F9EB7 for <rtcweb@ietf.org>; Tue, 9 Jul 2013 11:04:59 -0700 (PDT)
Received: from BN1BFFO11FD021.protection.gbl (10.58.52.203) by BN1AFFO11HUB032.protection.gbl (10.58.52.142) with Microsoft SMTP Server (TLS) id 15.0.717.3; Tue, 9 Jul 2013 18:04:58 +0000
Received: from TK5EX14HUBC102.redmond.corp.microsoft.com (131.107.125.37) by BN1BFFO11FD021.mail.protection.outlook.com (10.58.53.81) with Microsoft SMTP Server (TLS) id 15.0.717.3 via Frontend Transport; Tue, 9 Jul 2013 18:04:58 +0000
Received: from TK5EX14MBXC274.redmond.corp.microsoft.com ([169.254.3.70]) by TK5EX14HUBC102.redmond.corp.microsoft.com ([157.54.7.154]) with mapi id 14.03.0136.001; Tue, 9 Jul 2013 18:04:23 +0000
From: "Matthew Kaufman (SKYPE)" <matthew.kaufman@skype.net>
To: Ted Hardie <ted.ietf@gmail.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>, "public-webrtc@w3.org" <public-webrtc@w3.org>
Thread-Topic: [rtcweb] Locus of API discussion
Thread-Index: AQHOfLmwMutMwraSzEud0Hjh6FFtPplco6vQ
Date: Tue, 09 Jul 2013 18:04:22 +0000
Message-ID: <AE1A6B5FD507DC4FB3C5166F3A05A4841D143E48@TK5EX14MBXC274.redmond.corp.microsoft.com>
References: <CA+9kkMAaaT5RRLUrGvzs0zB0jXRQdHLm5HJH5-VkT5p1ZetVPQ@mail.gmail.com>
In-Reply-To: <CA+9kkMAaaT5RRLUrGvzs0zB0jXRQdHLm5HJH5-VkT5p1ZetVPQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [157.54.51.70]
Content-Type: multipart/alternative; boundary="_000_AE1A6B5FD507DC4FB3C5166F3A05A4841D143E48TK5EX14MBXC274r_"
MIME-Version: 1.0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(189002)(377454003)(199002)(80022001)(56816003)(33656001)(77096001)(20776003)(512954002)(47976001)(16236675002)(4396001)(81542001)(19300405004)(53806001)(16406001)(66066001)(74502001)(65816001)(15202345003)(47736001)(46102001)(6806003)(51856001)(83072001)(74706001)(59766001)(50986001)(69226001)(54316002)(56776001)(49866001)(77982001)(76482001)(31966008)(76796001)(74366001)(71186001)(79102001)(76786001)(54356001)(74876001)(47446002)(63696002)(81342001)(74662001)(55846006); DIR:OUT; SFP:; SCL:1; SRVR:BN1AFFO11HUB032; H:TK5EX14HUBC102.redmond.corp.microsoft.com; CLIP:131.107.125.37; RD:InfoDomainNonexistent; MX:1; A:1; LANG:en;
X-OriginatorOrg: microsoft.onmicrosoft.com
X-O365ENT-EOP-Header: Message processed by - O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 0902222726
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: Tue, 09 Jul 2013 18:05:06 -0000

Could you explain the reasoning behind moving the API discussion to the W3C list while leaving the actual API specification documents as Internet Drafts created and edited by the IETF WG?

I'm all for moving the API work (back) to W3C, but we should move all of it, don't you think?

Matthew Kaufman

From: rtcweb-bounces@ietf.org [mailto:rtcweb-bounces@ietf.org] On Behalf Of Ted Hardie
Sent: Tuesday, July 9, 2013 8:33 AM
To: rtcweb@ietf.org; public-webrtc@w3.org
Subject: [rtcweb] Locus of API discussion

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