- From: Harald Alvestrand <harald@alvestrand.no>
- Date: Mon, 15 Oct 2018 17:16:50 +0200
- To: public-webrtc@w3.org
Den 15. okt. 2018 13:53, skrev Bernard Aboba: > Given that the current WebRTC-QUIC specification is a work-in-progress undergoing a (major) revision, and the IETF QUIC specification is also changing, have these tests ever been run successfully? > > While we might move the tests to another directory, the existing tests seem to be Overtaken-by-Events. Because of the way web-platform-tests currently integrates with the Chrome build system, we know exactly what the status of these tests is. Given that there's no -expected files in the relevant directories, we know that these tests pass with the current version of the webrtc-quic experimental support in Chrome. https://cs.chromium.org/chromium/src/third_party/WebKit/LayoutTests/external/wpt/webrtc/RTCQuicTransport-helper.js?q=quic+wpt+webrtc&sq=package:chromium&dr=CSs&l=20 I think it's very reasonable to move them to another directory given that they test a different spec (either webrtc/quic or webrtc-quic), but they do serve as an important part of the deliverable for the team that is working on the current proposal. Test-as-you-specify. > >> On Oct 14, 2018, at 21:49, youenn fablet <yfablet@apple.com> wrote: >> >> I agree with Lennart that these tests should be isolated from other WPT tests: >> - These tests are not as mature as the other tests which might be used to validate WebRTC 1.0 compliance and spec coverage. >> - It should be easy to not import these tests until one decides to add support for this feature. >> webrtc/quic sounds like a good compromise to me. >> Y >> >>> On Oct 13, 2018, at 3:22 AM, Lennart Grahl <lennart.grahl@gmail.com> wrote: >>> >>> Sorry for digging this up: I would like to come back to the WPT tests >>> here for a second: Since we have not adopted the QUIC extension so far, >>> it should not be in the "webrtc" directory because that is misleading. I >>> would propose to move these tests into their own "webrtc-quic" directory >>> or into a subdirectory "drafts" or "experimental". >>> >>> What do you think and what would you prefer? >>> >>> Cheers >>> Lennart >>> >>>> On 30.08.2018 00:52, Bernard Aboba wrote: >>>> The QUIC API for WebRTC[4] was originally developed by the ORTC CG as part of the ORTC specification [5]. >>>> >>>> >>>> Peter Thatcher presented it to the WebRTC WG at last year's TPAC meeting in SFO [1]. So as to make it easier for the WEBRTC WG to evaluate, the QUIC-related sections of the ORTC specification were broken out into a separate specification using respec boilerplate which referred to the WEBRTC WG, rather than the ORTC CG. >>>> >>>> >>>> Feedback on WebRTC-QUIC and WebRTC-ICE was subsequently solicited from the WEBRTC WG on the mailing list [2], at the January 11, 2018 Virtual Interim meeting [3] and also at the F2F meeting in Stockholm. >>>> >>>> >>>> As you noted, at the Stockholm WEBRTC WG meeting, there was no consensus to adopt WebRTC-QUIC. The minutes do show interest in further work relating to ICE. >>>> >>>> >>>> So it appears to me that WebRTC-QUIC is currently a work item of the ORTC CG and probably should have its boilerplate modified to indicate that status. WebRTC-ICE also has WebRTC WG boilerplate, but it is not related to work in the ORTC CG.> >>>> [1] Presentation: https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2011%2F04%2Fwebrtc%2Fwiki%2Fimages%2F8%2F8a%2FWebRTCWG-2017-TPAC.pdf&data=02%7C01%7CBernard.Aboba%40microsoft.com%7Cbedac03d3a72454e287008d63248c7b5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636751685502707995&sdata=RBu2NJYI0n7znzTlKgOubmsRYjUT%2FCrtyUwNdUpRwAQ%3D&reserved=0 (starting at slide 82) >>>> Minutes: https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.w3.org%2F2017%2F11%2F06-webrtc-minutes.html%23item24&data=02%7C01%7CBernard.Aboba%40microsoft.com%7Cbedac03d3a72454e287008d63248c7b5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636751685502707995&sdata=oQfDF%2FFfLV%2BwCp0if%2BQiQ3vFu5JLZp%2BYG30F2R7zn%2Bg%3D&reserved=0 >>>> >>>> [2] https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.w3.org%2FArchives%2FPublic%2Fpublic-webrtc%2F2018Jan%2F0037.html&data=02%7C01%7CBernard.Aboba%40microsoft.com%7Cbedac03d3a72454e287008d63248c7b5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636751685502707995&sdata=PsUufUvfYsmaZ%2F9pV6mPiQGMtUoxJbpktNYgGP%2FKATg%3D&reserved=0 [3] https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2018%2F01%2F11-webrtc-minutes%23item05&data=02%7C01%7CBernard.Aboba%40microsoft.com%7Cbedac03d3a72454e287008d63248c7b5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636751685502707995&sdata=RMNHEoDeHUuBYUyE0oIj89BXaO39SYtOnU%2B%2FQ67sT9k%3D&reserved=0 [4] https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fw3c.github.io%2Fwebrtc-quic%2F&data=02%7C01%7CBernard.Aboba%40microsoft.com%7Cbedac03d3a72454e287008d63248c7b5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636751685502707995&sdata=T0QLvlYmZKz4Tb6aPaJ5bY7fMQ6S%2F9b0DPkltd%2Fw%2Bm0%3D&reserved=0 [5] https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdraft.ortc.org%2F&data=02%7C01%7CBernard.Aboba%40microsoft.com%7Cbedac03d3a72454e287008d63248c7b5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636751685502707995&sdata=%2BuH4f2wsXEovahbs%2FEEJ7nxOHCyuLNnaUOICD7vuG5w%3D&reserved=0 >>> >> >> >
Received on Monday, 15 October 2018 15:17:21 UTC