Moving RFC 4693 to Historic
draft-yevstifeyev-ion-report-07

[Ballot discuss]
Process nit worthy of a DISCUSSion:

RFC 4693 itself does not appear on the agenda. I suspect this means that this approval it will not generate the appropriate "Protocol Action" message when we approve it.

[Ballot discuss]
Process nits that are worthy of a DISCUSSion:

1. The Last Call did not go out as stated in http://www.ietf.org/iesg/statement/designating-rfcs-as-historic.html . In particular, it did not include the words "RFC 4693 to Historic".

2. RFC 4693 itself does not appear on the agenda. I suspect this means that this approval it will not generate the appropriate "Protocol Action" message when we approve it.

State changed to In Last Call from Last Call Requested.

The following Last Call Announcement was sent out:

From: The IESG
To: IETF-Announce
Reply-To: ietf@ietf.org
Subject: Last Call:  (Report on the Experiment with IETF Operational Notes (IONs)) to Informational RFC


The IESG has received a request from an individual submitter to consider
the following document:
- 'Report on the Experiment with IETF Operational Notes (IONs)'
  as an 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@ietf.org mailing lists by 2011-08-09. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


  This document reports on the IETF Operational Notes (IONs) process
  experiment, conducted by RFC 4693 in accordance with RFC 3933.  It
  also updates RFC 4693 and changes its status to Historic.




The file can be obtained via
http://datatracker.ietf.org/doc/draft-yevstifeyev-ion-report/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-yevstifeyev-ion-report/


No IPR declarations have been submitted directly on this I-D.