Sounds like a lot of work to me. In the era of xml2rfc, that could be error-prone as well. For the particular issue, having a notice in the Conventions section might do (it may be there already...). However, it doesn't address the fundamental issue raised by the appeal. I don't think the IETF wants to go the path of U.N.-sponsored treaty organization SDO's [if you have no clue what I am referring to, just ask Tom Taylor or Rich Shockey who would love to earn beers for telling about their experiences]. The goal is not just to negotiate a "settlement", but to fix the problem. We are engineers, after alll. Moreover, I do not think the "problem" is an individual, where the fix is "fixing" the individual. I would encourage everyone to re-read John's original post. The fundamental problem of not knowing what is critical and what isn't needs to be made clear, and via the IETF's accepted processes. Sent from my Verizon Wireless BlackBerry -----Original Message----- From: Simon Josefsson <simon@xxxxxxxxxxxxx> Date: Tue, 17 Jun 2008 11:30:05 To:Brian Dickson <briand@xxxxxxxxxxxxxxx> Cc:Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@xxxxxxxxx>, ietf@xxxxxxxx Subject: Re: Appeal against IESG blocking DISCUSS on draft-klensin-rfc2821bis Brian Dickson <briand@xxxxxxxxxxxxxxx> writes: > Here's my suggestion: > > List 2606 in the informative references, and footnote the examples used > to indicate > that they are "grandfathered" non-2606 examples. > > So, in text that previously read "not-example.com", it might read > "not-example.com [*]", > with the references section having "[*] Note - non-RFC2606 examples > used. Please read RFC2606." > > Something along those lines, should hopefully be enough to keep both > sides happy, and resolve the DISCUSS, > and hopefully both set a suitable precedent *and* make moot the appeal. I think this sounds like a good compromise, and it does improve the document quality IMHO. John, would this be an acceptable addition to the document? Thanks, Simon _______________________________________________ IETF mailing list IETF@xxxxxxxx https://www.ietf.org/mailman/listinfo/ietf _______________________________________________ IETF mailing list IETF@xxxxxxxx https://www.ietf.org/mailman/listinfo/ietf