RTCQuicStream: bi-directional or unidirectional?

At the QUIC WG interim in Seattle last week, there was discussion about bi-directional vs. uni-directional QUIC streams.  This has potential implications both for the protocol specification, as well as the QUIC stream abstraction surfaced in APIs.

Here is a post from EKR about an implementation in Minq and a presentation relating to that:
https://www.ietf.org/mail-archive/web/quic/current/msg02295.html<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmail-archive%2Fweb%2Fquic%2Fcurrent%2Fmsg02295.html&data=02%7C01%7CBernard.Aboba%40microsoft.com%7Cc144486e788649b1decb08d510da36c8%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636433451802014745&sdata=8SjaO50u1glP0Wk1dwPHcavG9AU5M5yts%2BbTsdPJx2Q%3D&reserved=0>
https://github.com/ekr/wg-materials/blob/404898fa2d2f0a9f9bd244d2c945e66ea88502a2/interim-17-10/Unidirectional%20Streams%20in%20Minq.pdf<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fekr%2Fwg-materials%2Fblob%2F404898fa2d2f0a9f9bd244d2c945e66ea88502a2%2Finterim-17-10%2FUnidirectional%2520Streams%2520in%2520Minq.pdf&data=02%7C01%7CBernard.Aboba%40microsoft.com%7Cc144486e788649b1decb08d510da36c8%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C1%7C636433451802024749&sdata=F%2Bg3fsBBlU1XkSLYypL6Xn2HLeQxvtLN8Nu2fiMAKyA%3D&reserved=0>

Here is a pointer to the QUIC WG github Issue on the QUIC streams abstraction and a presentation from Mike Bishop:
https://github.com/quicwg/base-drafts/issues/783<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fquicwg%2Fbase-drafts%2Fissues%2F783&data=02%7C01%7CBernard.Aboba%40microsoft.com%7Cc144486e788649b1decb08d510da36c8%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636433451802024749&sdata=2DYfxIB5%2BWyb7Dh2%2Fw1CRATY0bEViqtN2hIkChblhUw%3D&reserved=0>
https://github.com/quicwg/wg-materials/blob/master/interim-17-10/stream-abstraction.pdf<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fquicwg%2Fwg-materials%2Fblob%2Fmaster%2Finterim-17-10%2Fstream-abstraction.pdf&data=02%7C01%7CBernard.Aboba%40microsoft.com%7Cc144486e788649b1decb08d510da36c8%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C1%7C636433451802024749&sdata=p0J3VY2miYcOkpCVYCI%2Bz9o0BBBTEDl%2BiGSYoGDX2Pk%3D&reserved=0>

Here are pointers to the Seattle QUIC WG Interim meeting agenda and the minutes of the meeting:
https://datatracker.ietf.org/meeting/interim-2017-quic-04/materials/agenda-interim-2017-quic-04-sessa/<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fmeeting%2Finterim-2017-quic-04%2Fmaterials%2Fagenda-interim-2017-quic-04-sessa%2F&data=02%7C01%7CBernard.Aboba%40microsoft.com%7Cc144486e788649b1decb08d510da36c8%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636433451802014745&sdata=20KtTTZHSKO39eD4qDmtE4yg997qgD7WbPKqU6YCiUI%3D&reserved=0>
https://github.com/quicwg/wg-materials/blob/master/interim-17-10/minutes.md<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fquicwg%2Fwg-materials%2Fblob%2Fmaster%2Finterim-17-10%2Fminutes.md&data=02%7C01%7CBernard.Aboba%40microsoft.com%7Cc144486e788649b1decb08d510da36c8%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636433451802014745&sdata=F50YPElzpiujXqbM0Im9jKEDNyMO27HoBkYfwFo%2FXcw%3D&reserved=0>