Warren Kumari has entered the following ballot position for draft-ietf-taps-interface-22: Yes
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/about/groups/iesg/statements/handling-ballot-positions/ for more information about how to handle DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-taps-interface/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Firstly, thank you very much for writing this document -- I found it a fascinating read. I'd also like to thank Matt Brown for the DNS-DIR review, it was most helpful. I only have a few nits / suggestions to make: 1: S 1.4. Glossary of Key Terms *Endpoint: An identifier for one side of a Connection (local or remote), such as a hostnames or URL. I'm not really sure that the definition of "Endpoint" works. E.g: the definition of "Connection" is "Shared state of two or more endpoints that persists across Messages". Ok, fine. But can you really have shared state between two **identifiers**? I don't really see how I'd have shared state between e.g hostnames, but I can see how I'd have state between entities *identified* by an identifier like a hostname. I understand what you are aiming for (and also "endpoint" seems to be used in more than one context), but I don't think that the definition as written actually works... 2: S 2.1. Event-Driven API This paragraph compares and contrasts the Socket API and the Transport Services API, but in the paragraph starting with "For example, an application first issues a call to receive new data from the connection.", it is unclear under which paradigm you are meaning. I'd suggest: "For example, when using the Transport Services API, an application first ..." _______________________________________________ Taps mailing list [email protected] https://www.ietf.org/mailman/listinfo/taps
