W3C home > Mailing lists > Public > public-webrtc@w3.org > January 2020

Re: [EXTERNAL] New charter for WebRTC Working Group

From: Bernard Aboba <Bernard.Aboba@microsoft.com>
Date: Thu, 23 Jan 2020 16:50:43 +0000
To: Dominique Hazael-Massieux <dom@w3.org>, "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-ID: <CY1PR00MB0123877C4613BDC28A0BEC3CEC0F0@CY1PR00MB0123.namprd00.prod.outlook.com>
One bit of feedback.

The Charter does not mention the WebRTC-ICE specification<https://w3c.github.io/webrtc-ice/>. At TPAC 2019<https://docs.google.com/presentation/d/1Xprz0ElNTUWRDdX6kyp11cZ4ItTvUFUmzoXsKZdXxuU/edit#slide=id.g5fbe90bfc8_0_415>, the WG discussed issuing a Call for Consensus to adopt it as a WG draft, once the specification had added enhancements (known as "Flex ICE").

Peter Thatcher has now checked in enhancements to the Chrome WebRTC-ICE implementation:
https://webrtc-review.googlesource.com/c/src/+/162241

Now that we have two implementations of a standalone RTCIceTransport supporting enhancements such as ICE forking (the other being Ortc lib), it should be possible to add the new functionality into the WebRTC-ICE specification.
________________________________
From: Dominique Hazael-Massieux <dom@w3.org>
Sent: Tuesday, January 21, 2020 1:09 AM
To: public-webrtc@w3.org <public-webrtc@w3.org>
Subject: [EXTERNAL] New charter for WebRTC Working Group

Dear all,

As we discussed during TPAC [1], our current charter [2] expires by the
end of March 2020, and we will need to recharter the group to continue
the existing work and possibly start new work as identified in the
WebRTC NV use cases [3].

In collaboration with the Chairs, I have prepared a draft new charter:
  https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fw3c.github.io%2Fwebrtc-charter%2Fwebrtc-charter.html&amp;data=02%7C01%7CBernard.Aboba%40microsoft.com%7C92c81ab0f30c419516a408d79e51e94f%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637151946962918295&amp;sdata=EoDyTkvhWZcVySA%2BEDKDtlocfpt2h3ozala6q4p0hB8%3D&amp;reserved=0


https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fservices.w3.org%2Fhtmldiff%3Fdoc1%3Dhttps%253A%252F%252Fwww.w3.org%252F2018%252F07%252Fwebrtc-charter.html%26doc2%3Dhttps%253A%252F%252Fw3c.github.io%252Fwebrtc-charter%252Fwebrtc-charter.html&amp;data=02%7C01%7CBernard.Aboba%40microsoft.com%7C92c81ab0f30c419516a408d79e51e94f%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637151946962918295&amp;sdata=NFlT0yuERfbcxTfpKuz0Yrd8tqQybGJwCBJwtaEj%2FmU%3D&amp;reserved=0

In addition to updating our deliverable lists based on our latest set of
known specs, the charter also paves the way for moving the work on
media-related functions to a different group, should the opportunity
arise - a desire that was discussed during our TPAC meeting as an option
to consider.

Your feedback on this new proposed charter would be most welcomed.

Thanks,

Dom

1. https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2019%2F09%2F19-webrtc-minutes.html%23item03&amp;data=02%7C01%7CBernard.Aboba%40microsoft.com%7C92c81ab0f30c419516a408d79e51e94f%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637151946962918295&amp;sdata=LyJpZota%2BJv1hLeyCEIRK2LgPFvZfGkHcGVj6vtlegs%3D&amp;reserved=0
2. https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2018%2F07%2Fwebrtc-charter.html&amp;data=02%7C01%7CBernard.Aboba%40microsoft.com%7C92c81ab0f30c419516a408d79e51e94f%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637151946962918295&amp;sdata=iK62q3efR7K3svV2LNYW2%2BQg%2FnIYkVdDtY3drIvAgvE%3D&amp;reserved=0
3. https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fw3c.github.io%2Fwebrtc-nv-use-cases%2F&amp;data=02%7C01%7CBernard.Aboba%40microsoft.com%7C92c81ab0f30c419516a408d79e51e94f%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637151946962918295&amp;sdata=upd9myTwLVpB8Vmbg0sLpVyGq1e2ra36kb6qHoPAH7M%3D&amp;reserved=0
Received on Thursday, 23 January 2020 16:50:50 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 23 January 2020 16:50:51 UTC