attachment
<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">All,<div class=""><br class=""></div><div class="">Now that IPP/1.1 is an Internet Standard, we generally should just be referencing the collection of RFCs (8010 and 8011) and not the individual documents or sections within a specific RFC, for example:</div><div class=""><br class=""></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class=""><div class="">The keyword attribute values defined in this document will be published by IANA according to the procedures in the Internet Printing Protocol/1.1 [STD92] in the following file:</div></div></blockquote><div class=""><br class=""></div><div class="">The reference for STD 92 is just:</div><div class=""><br class=""></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class="">[STD92] M. Sweet, I. McDonald, "Internet Printing Protocol/1.1", STD 92, June 2018, <a href="https://tools.ietf.org/html/std92" class="">https://tools.ietf.org/html/std92</a></div></blockquote><div class=""><br class=""></div><div class="">If a general reference is ambiguous or not obvious, use the RFC reference form with a section reference, for example:</div><div class=""><br class=""></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class="">Most Authenticated User: The most authoritative user name for the current request as defined in section 9.3 of the Internet Printing Protocol/1.1: Model and Semantics [RFC8011].</div></blockquote><div class=""><br class=""></div><div class=""><div class="">_________________________________________________________<br class="">Michael Sweet, Senior Printing System Engineer</div><br class=""></div></body></html>