RE: Review of webrtc-pc (deadline: May 31st)

My requirements review was sent to the list:
https://lists.w3.org/Archives/Public/public-webrtc/2017May/0017.html

Based on subsequent discussion, the potential Issues uncovered relate to ICE:

a. STUN/TURN/ICE references (probably more of an IETF issue)
b. HTTP traversal (support for TLS candidates, dependent on progress in IETF)
c. STUN/TURN discovery (previously discussed and closed in https://github.com/w3c/webrtc-pc/issues/941 )

Since it is not clear there are any required changes to the API at this time, I am not planning to file any CR-blocking requirements issues (though I will file other non-CR blocking Issues). 
________________________________________
From: Stefan Håkansson LK [stefan.lk.hakansson@ericsson.com]
Sent: Tuesday, May 16, 2017 12:17 AM
To: Bernard Aboba; Cullen Jennings; Eric Rescorla; deadbeef@google.com
Cc: public-webrtc@w3.org
Subject: Review of webrtc-pc (deadline: May 31st)

Hi Bernard, Cullen, Ekr and Taylor (cc group),

You all committed to review the webrtc-pc document, and we encourage
others to do the same (the more eyes we get reading it the better the
quality will be).

We’d like you to report findings in the form of github Issues at [1].

The review was triggered by the ambition to move to CR. The bar to move
to CR is that the spec fulfills the technical requirements, but we would
be glad to see everything you find reported (including editorial
things). However, we intend to categorize the Issues; only the ones that
are about technical requirements should hold off a transition to CR (the
other ones we can deal with after getting to CR).

Things will be simpler if you all review the same version, so please use
the version at [2].

The technical requirements are listed in [3] (especially the API
requirements “Axx” are in scope) and to some extent in [4].

We’re doodling [5] for a June meeting to deal with the Issues reported,
so please finalize the review by May 31st.

Stefan for the chairs

[1] https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fw3c%2Fwebrtc-pc%2Fissues&data=02%7C01%7CBernard.Aboba%40microsoft.com%7C47cbd49c183d45109c5308d49c2bb06a%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636305158839096281&sdata=hmjNSRvDUvTc%2F2Thul7JE7P2pLhKQ2Nj%2BfTyVrVoNnY%3D&reserved=0
[2] https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fw3c.github.io%2Fwebrtc-pc%2Farchives%2F20170515%2Fwebrtc.html&data=02%7C01%7CBernard.Aboba%40microsoft.com%7C47cbd49c183d45109c5308d49c2bb06a%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636305158839106289&sdata=liBsqbbk%2B2rkpe2RMN8JzidF8SIeVhDjsdrZlmO79f4%3D&reserved=0
[3] https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Frfc7478&data=02%7C01%7CBernard.Aboba%40microsoft.com%7C47cbd49c183d45109c5308d49c2bb06a%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636305158839106289&sdata=YfDSUFBcbAryXftvrephHFnW2O2X9%2BQJQ5VTtBNp0Jc%3D&reserved=0
[4] https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Fdraft-ietf-rtcweb-security-arch&data=02%7C01%7CBernard.Aboba%40microsoft.com%7C47cbd49c183d45109c5308d49c2bb06a%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636305158839106289&sdata=fDevtyFRGhswYItPcfRxQw9WEE%2FWCN%2FIxSPHBrTRQDU%3D&reserved=0
[5] https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdoodle.com%2Fpoll%2Fx6zgi3mbuwc4qpw9&data=02%7C01%7CBernard.Aboba%40microsoft.com%7C47cbd49c183d45109c5308d49c2bb06a%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636305158839106289&sdata=dCJ9JqAqMtR78hBVkV2QkxSNUVvqMBzVyEvVrz5fOqw%3D&reserved=0

Received on Wednesday, 17 May 2017 01:14:26 UTC