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="">Spotted by one of the GSoC 2018 students...<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">Begin forwarded message:</div><br class="Apple-interchange-newline"><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">From: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class="">RFC Errata System <<a href="mailto:rfc-editor@rfc-editor.org" class="">rfc-editor@rfc-editor.org</a>><br class=""></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">Subject: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class=""><b class="">[Technical Errata Reported] RFC3996 (5413)</b><br class=""></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">Date: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class="">June 28, 2018 at 8:55:26 AM EDT<br class=""></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">To: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class=""><a href="mailto:bob@herriot.com" class="">bob@herriot.com</a>, <a href="mailto:tom.hastings@alum.mit.edu" class="">tom.hastings@alum.mit.edu</a>, <a href="mailto:harryl@us.ibm.com" class="">harryl@us.ibm.com</a>, <a href="mailto:ben@nostrum.com" class="">ben@nostrum.com</a>, <a href="mailto:aamelnikov@fastmail.fm" class="">aamelnikov@fastmail.fm</a>, <a href="mailto:adam@nostrum.com" class="">adam@nostrum.com</a>, <a href="mailto:carl@manros.com" class="">carl@manros.com</a><br class=""></span></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=""><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif; color:rgba(0, 0, 0, 1.0);" class=""><b class="">Cc: </b></span><span style="font-family: -webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class=""><a href="mailto:msweet@apple.com" class="">msweet@apple.com</a>, <a href="mailto:rfc-editor@rfc-editor.org" class="">rfc-editor@rfc-editor.org</a><br class=""></span></div><br class=""><div class=""><div class="">The following errata report has been submitted for RFC3996,<br class="">"Internet Printing Protocol (IPP): The 'ippget' Delivery Method for Event Notifications".<br class=""><br class="">--------------------------------------<br class="">You may review the report below and at:<br class=""><a href="http://www.rfc-editor.org/errata/eid5413" class="">http://www.rfc-editor.org/errata/eid5413</a><br class=""><br class="">--------------------------------------<br class="">Type: Technical<br class="">Reported by: Michael Sweet <msweet@apple.com><br class=""><br class="">Section: 5.2.1<br class=""><br class="">Original Text<br class="">-------------<br class=""> The value of this attribute MUST be at least as large as that of the<br class=""> Printer's "ippget-event-life" Printer Description attribute (see<br class=""> section 8.1). The Printer MAY return a value that is larger than<br class=""> that of the "ippget-event-life" Printer Description attribute<br class=""> provided that the Printer increases the Event Life for this<br class=""> Subscription object so that Notification Recipients taking account of<br class=""> the larger value and polling with a longer interval will not miss<br class=""> events. Note: Implementing such an algorithm requires some hidden<br class=""> attributes in the Subscription object that are IMPLEMENTATION<br class=""> DEPENDENT.<br class=""><br class=""><br class="">Corrected Text<br class="">--------------<br class=""> If the value of this attribute is larger than that of the<br class=""> "ippget-event-life" Printer Description attribute, the Printer MUST<br class=""> increase the Event Life for this Subscription object so that<br class=""> Notification Recipients taking account of the larger value and<br class=""> polling with a longer interval will not miss events. Note:<br class=""> Implementing such an algorithm requires some hidden state in the<br class=""> Subscription object that is IMPLEMENTATION DEPENDENT.<br class=""><br class=""><br class="">Notes<br class="">-----<br class="">The range of values allowed for the "notify-get-interval" attribute (0 to 2^31-1) is different from the "ippget-event-life" attribute (15 to 2^31-1), and implementations have ignored this requirement because it makes no sense. Furthermore, the use of MAY for larger values does not clearly capture the requirement to extend event lives in order to avoid missing notifications.<br class=""><br class="">Instructions:<br class="">-------------<br class="">This erratum is currently posted as "Reported". If necessary, please<br class="">use "Reply All" to discuss whether it should be verified or<br class="">rejected. When a decision is reached, the verifying party <br class="">can log in to change the status and edit the report, if necessary. <br class=""><br class="">--------------------------------------<br class="">RFC3996 (draft-ietf-ipp-notify-get-10)<br class="">--------------------------------------<br class="">Title : Internet Printing Protocol (IPP): The 'ippget' Delivery Method for Event Notifications<br class="">Publication Date : March 2005<br class="">Author(s) : R. Herriot, T. Hastings, H. Lewis<br class="">Category : PROPOSED STANDARD<br class="">Source : Internet Printing Protocol<br class="">Area : Applications<br class="">Stream : IETF<br class="">Verifying Party : IESG<br class=""></div></div></blockquote></div><br class=""><div class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">_________________________________________________________<br class="">Michael Sweet, Senior Printing System Engineer<br class=""></div></div></div>
</div>
<br class=""></body></html>