[Add] Roman Danyliw's No Objection on draft-ietf-add-resolver-info-12: (with COMMENT)

[Roman Danyliw via Datatracker <[e-mail]>]

Roman Danyliw has entered the following ballot position for
draft-ietf-add-resolver-info-12: No Objection

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-add-resolver-info/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thank you to Mallory Knodel for the GENART review.

I support the DISCUSS positions of Paul Wouters and Warren Kumari.  Both of
these positions already capture the majority of the feedback I would have
provided.  I would emphasis the point made my Warren that additional text on
the use case and deployment environment might help illuminate the design
described in this document.

** Section 5.  Infourl
      The resolver information server MUST support the content-type
      'text/html'.
...
      The URL SHOULD be treated only as diagnostic
      information for IT staff.

-- Does this text imply that resolver information can be sent back in some
other content-type as long as the resolved information server supports
‘text/html’?  As constructed, this text doesn’t appear to restrict the
content-type of the information.

-- Under what circumstances would the IT staff use this for non-diagnostic
information?