Hi Dmitri, On Tue, Jan 26, 2021 at 5:10 PM Dmitri Tikhonov <[email protected]> wrote:
> I would dispense with examples and use precedent. That is, the second > work area is listed simply as "QUIC deployability" in the charter. Then, > the WG picks up (say) the load balancer draft based on the applicability > of the "deployability" rule. This establishes precedent what types of > work items the deployability work area covers. The precedent is used in > the future to figure out which new work items are applicable and which > are not. > my 2c as an individual: The Applicability, Manageability and Load Balancer documents are all already adopted by the QUIC WG, under current or previous charters. They address the work area of deployability. Arguably, they help *use* the QUIC protocol rather than extend or modify it. A loss bits specification possibly requires extension of the QUIC protocol, with the intent to improve manageability. Such work is likely to span the extension and deployability work areas. Waiting for the new documents to get proposed and adopted, as a new precedent for future work in this area doesn't IMO help much. We already have precedents, which I trust the WG to be capable of applying without being too literal. Cheers, Lucas
