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

[Orie Steele via Datatracker <[e-mail]>]

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

Thanks to Arnt Gulbrandsen for the ARTART Review.
Thanks to Tommy Jensen for the shepherd write up.

I support Paul's Discuss, and agree with many of his comments.

In particular, Arnt mentioned in his review similar concerns regarding Section
7.

In Section 5, is misleading IT staff a security issue?
Its not clear how to protect end users in this section.
Consider MUST NOT display the URL to end users.

If you retain the recommendation to use text/html consider adding some guidance
regarding web app sec, scripts etc... This might better help explain your
requirement to use HTTPS?

Prefer to see some concrete examples of acceptable strategies for managing
reputation.