Re: [quicwg/base-drafts] Merge normative -spin-exp text into -transport (#2369)

[Marcus Ihlar <[e-mail]>]

That's an interesting perspective.
On that note though, an argument for describing how to set the bit in the transport draft is that version specific changes to the protocol will require updates to the text on how to set the bit.
We might see things like mulitpath, reliability modes with vastly different acking schemes etc, which could have direct impact on how/if/when to filp bits.

Also, it is only the normative text that would be included in the transport draft and that's not a large amount of text at all. 

Finally, there are two pieces of text relating to the bit that we want to publish, the normative part which is short and intended for implementors and text on how to detect the bit and how/what to measure etc. That second piece is the one which will require more text and is likely of less interest to implementors, therefore a good fit for it would be the manageability document. 

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/2369#issuecomment-457190877