Hi all,


as promised here is the overview of (non-editorial issues) and PRs for the 
applicability statement. Please comment preferably on github. Maybe we can 
resolve some of them before the meeting and save the meeting time for something 
else :-)



PRs:



Text on datagrams<https://github.com/quicwg/ops-drafts/pull/273> #273 addresses 
#269<https://github.com/quicwg/ops-drafts/issues/269>

-> This PR already got some good feedback and people are positive about adding 
this new section. Flagging this here because it discusses an extension and not 
the base protocol which is new for these drafts. Datagram support, however, 
seems to be an important feature for application to know about and therefore 
ths PR proposed to add a new section on this!



Recommendation on ACKing<https://github.com/quicwg/ops-drafts/pull/233> #233 
addresses #234<https://github.com/quicwg/ops-drafts/issues/234>

-> This PR also already received some positive feedback. Flagging this here as 
this adds new recommendations to the document.



Wording proposal by Gorry on exposing numbers of streams and 
such<https://github.com/quicwg/ops-drafts/pull/277> #277

-> Small proposed wording change. Flagging this to confirm that text is only 
clarifying but not changing the meaning.



Issues:



Clarify Stream ID assignment<https://github.com/quicwg/ops-drafts/issues/283> 
#283

-> This is a new issue and input is needed



App: What does "prime a CC" 
mean?<https://github.com/quicwg/ops-drafts/issues/197> #197

-> More input is needed if this should be reworded to clarify or removed



App: Sect 4.3. Flow Control - we should have a subsection also encouraging 
timely credits<https://github.com/quicwg/ops-drafts/issues/193> #193

-> No input needed right now. This is ready for text and Lucas agreed propose a 
PR



Discuss application-layer graceful/scheduled 
close<https://github.com/quicwg/ops-drafts/issues/175> #175

-> No input needed right now. This is ready for text and Lucas agreed propose a 
PR



Thanks,

Mirja and Brian










Reply via email to