- From: Robin Raymond <robin@hookflash.com>
- Date: Tue, 09 Jul 2013 15:43:16 -0400
- To: "Matthew Kaufman (SKYPE)" <matthew.kaufman@skype.net>
- CC: Ted Hardie <ted.ietf@gmail.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>, "public-webrtc@w3.org" <public-webrtc@w3.org>
- Message-ID: <51DC67D4.9050101@hookflash.com>
Agreed, and in addition, is SDP with offer / answer a mandated surface API by the RTCWEB WG or the W3C? (i.e. a mandate that some use cases are only solvable with touching the SDP, and web developer must know about offer/answer in the process) If so, which group is mandating that requirement be part of the web developer's API? This helps define which group is appropriate to address those kinds of concerns. -Robin > Matthew Kaufman (SKYPE) <mailto:matthew.kaufman@skype.net> > 9 July, 2013 2:04 PM > > 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 > > _______________________________________________ > rtcweb mailing list > rtcweb@ietf.org > https://www.ietf.org/mailman/listinfo/rtcweb > Ted Hardie <mailto:ted.ietf@gmail.com> > 9 July, 2013 11:33 AM > 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 > _______________________________________________ > rtcweb mailing list > rtcweb@ietf.org > https://www.ietf.org/mailman/listinfo/rtcweb
Received on Tuesday, 9 July 2013 19:43:47 UTC