Hi, Alissa, On Wed, Sep 12, 2018 at 2:22 PM Alissa Cooper <[email protected]> wrote:
> Alissa Cooper has entered the following ballot position for > draft-ietf-taps-minset-08: Discuss > > When responding, please keep the subject line intact and reply to all > email addresses included in the To and CC lines. (Feel free to cut this > introductory paragraph, however.) > > > Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html > for more information about IESG DISCUSS and COMMENT positions. > > > The document, along with other ballot positions, can be found here: > https://datatracker.ietf.org/doc/draft-ietf-taps-minset/ > > > > ---------------------------------------------------------------------- > DISCUSS: > ---------------------------------------------------------------------- > > I was wondering about why this document is going for informational rather > than > proposed standard. I see that draft-ietf-taps-interface-01 has a normative > reference to it, so this is effectively setting up a downref situation. > That > isn't necessarily a problem, but if the point is for this document to > recommend > an actual minimal set of transport services to be supported and exposed > via the > API specified in draft-ietf-taps-interface and other APIs, shouldn't that > set > be normative? > Understood. I'll need to talk about this with the TAPS chairs, and that won't happen before the telechat tomorrow morning, but I will talk with the TAPS chairs, and you'll have an answer. (So, "do we need to discuss that on this telechat?", "no, the Discuss is clear and actionable". - just to save wear and tear on the Secretariat!) Thanks, Spencer > ---------------------------------------------------------------------- > COMMENT: > ---------------------------------------------------------------------- > > It seems like this document will be in need of updating once QUIC is > published. > Is the plan to publish this now and then publish an update next year? Why > is > that preferable to waiting and just publishing once? > > >
_______________________________________________ Taps mailing list [email protected] https://www.ietf.org/mailman/listinfo/taps
