Hi, The inclusion of the template as an Appendix in the document is confusing - right now A.1 through A.7 define sections in the future I-Ds, while A.8 and A.9 describe appendices in the future I-D. This document has two sections each titled Appendix A and Appendix B. Moreover, this inclusion has the disadvantage that if changes or updates need to be brought up for reasons whatsoever, a new RFC needs to be written. Did the author and the WG considered adopting the approach taken by RFC 5249 which located the templates under the IETF tools web pages and only referred them from the RFC? Regards, Dan > -----Original Message----- > From: ietf-announce-bounces@xxxxxxxx [mailto:ietf-announce- > bounces@xxxxxxxx] On Behalf Of The IESG > Sent: Thursday, May 17, 2012 12:53 AM > To: IETF-Announce > Cc: mile@xxxxxxxx > Subject: Last Call: <draft-ietf-mile-template-04.txt> (Guidelines for > DefiningExtensions to IODEF) to Informational RFC > > > The IESG has received a request from the Managed Incident Lightweight > Exchange WG (mile) to consider the following document: > - 'Guidelines for Defining Extensions to IODEF' > <draft-ietf-mile-template-04.txt> as Informational RFC > > The IESG plans to make a decision in the next few weeks, and solicits > final comments on this action. Please send substantive comments to the > ietf@xxxxxxxx mailing lists by 2012-05-30. Exceptionally, comments may > be > sent to iesg@xxxxxxxx instead. In either case, please retain the > beginning of the Subject line to allow automated sorting. > > Abstract > > > This document provides guidelines for extensions to IODEF [RFC5070] > for exchange of incident management data, and contains a template > for > Internet-Drafts describing those extensions, in order to ease the > work and improve the quality of extension descriptions. > > > > > The file can be obtained via > http://datatracker.ietf.org/doc/draft-ietf-mile-template/ > > IESG discussion can be tracked via > http://datatracker.ietf.org/doc/draft-ietf-mile-template/ballot/ > > > No IPR declarations have been submitted directly on this I-D. >