[Taps] Lars Eggert's Abstain on draft-ietf-taps-interface-24: (with COMMENT)

[Lars Eggert via Datatracker <[e-mail]>]

Lars Eggert has entered the following ballot position for
draft-ietf-taps-interface-24: Abstain

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:
----------------------------------------------------------------------

I'm abstaining on this document, because I disagree that
Proposed Standard is appropriate. This document (and its companion)
outline an extremely intricate design without going into the - in
my opinion - necessary details to fully explain all aspects. I
appreciate that the WG intends this to be an "abstract API" that
therefore can be described at a higher level of abstraction, but
that is IMO exactly why PS is not a suitable RFC status here -
we won't be able to determine implementation conformance and hence
interoperability to this spec. If the intend is to publish an API
as a PS, it would IMO need to be described at a level where that is
feasible.