Re: Last Call: <draft-ietf-mile-template-04.txt> (Guidelines for Defining Extensions to IODEF) to Informational RFC

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



At 14:53 16-05-2012, The IESG wrote:
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

The Abstract mentions that this draft contains a template for [writing] Internet-Drafts describing [extensions to IODEF]. Why is a RFC needed for a template to write I-Ds? It seems like the WG is encouraging future authors to copy and paste the text and generate new RFCs.

Regards,
-sm


[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Fedora Users]