INTERNET-DRAFT                                            M. Yevstifeyev
Intended Status: Informational                              July 7, 2011
Updates: 4693 (if approved)
Expires: January 8, 2012

      Report on the Experiment with IETF Operational Notes (IONs)
                    draft-yevstifeyev-ion-report-04

Abstract

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

Status of this Memo

   This Internet-Draft is submitted to IETF in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as
   Internet-Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/1id-abstracts.html

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

Copyright and License Notice

   Copyright (c) 2011 IETF Trust and the persons identified as the
   document authors. All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document. Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document. Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of



Yevstifeyev             Expires January 8, 2012                 [Page 1]


INTERNET DRAFT                IONs Report                   July 7, 2011


   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1. Introduction  . . . . . . . . . . . . . . . . . . . . . . . . .  2
   2. Background  . . . . . . . . . . . . . . . . . . . . . . . . . .  2
   3. Experiment Notes and Results  . . . . . . . . . . . . . . . . .  3
     3.1. Published IONs  . . . . . . . . . . . . . . . . . . . . . .  3
     3.2. Experiment Closure  . . . . . . . . . . . . . . . . . . . .  3
     3.3. Subsequent Actions on IONs  . . . . . . . . . . . . . . . .  4
     3.4. Archival Copies of IONs . . . . . . . . . . . . . . . . . .  5
   4. Conclusion  . . . . . . . . . . . . . . . . . . . . . . . . . .  5
   5. Security Considerations . . . . . . . . . . . . . . . . . . . .  5
   6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . .  5
   7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . .  5
   8. References  . . . . . . . . . . . . . . . . . . . . . . . . . .  5
     8.1. Normative References  . . . . . . . . . . . . . . . . . . .  5
     8.2. Informative References  . . . . . . . . . . . . . . . . . .  6
   Author's Addresses . . . . . . . . . . . . . . . . . . . . . . . .  7

1. Introduction

   This document is a report from the experiment with IETF Operational
   Notes (IONs), conducted by RFC 4693 [RFC4693] in accordance with RFC
   3933 [RFC3933].  It discusses the results of this experiment after
   first giving some background information on it in Section 2 and makes
   the appropriate conclusion.  This document updates RFC 4693 [RFC4693]
   and changes its status to Historic per RFC 2026 [RFC2026] and
   [HISTORIC].

2. Background

   IETF Operational Notes (IONs) are a series of documents established
   by RFC 4693 [RFC4693] on an experimental basis [RFC3933] in 2006.
   This series is (in accordance with RFC 4693 [RFC4693])

     intended for use as a repository for IETF operations documents,
     which should be more ephemeral than RFCs, but more referenceable
     than Internet-Drafts, and with more clear handling procedures than
     a random Web page.

   RFC 4693 [RFC4693] contains some regulations regarding this series,
   such as ION attributes ("front page matters"), approval procedure,
   ION store considerations, etc.  It also proposes a set off initial
   IONs to be published and sets the sunset period of 1 year.  See
   Section 5 of RFC 4693 [RFC4693] for more background information on
   this topic.



Yevstifeyev             Expires January 8, 2012                 [Page 2]


INTERNET DRAFT                IONs Report                   July 7, 2011


3. Experiment Notes and Results

3.1. Published IONs

   After establishing the IONs series per RFC 4693 [RFC4693], a number
   of IONs proposed by that document, as well as on some other topics,
   were published.  Particularly, the following IONs were issued (in
   alphabetical order):

   o ion-ad-sponsoring on "Guidance on Area Director Sponsoring of
     Documents" by Jari Arkko;

   o ion-agenda-and-minutes on "Formatting and Content of IETF Working
     Group Agendas and Minutes" by David Meyer and Olaf Kolkman;

   o ion-discuss-criteria on "DISCUSS Criteria in IESG Review" by the
     IESG members (at the date of approval);

   o ion-execd-tasks on "Tasks previously assigned to the IETF Executive
     Director" by Lucy Lynch and Brian Carpenter;

   o ion-ion-formats on "ION Format specification" by Brian Carpenter
     and Cullen Jennings;

   o ion-ion-store on "The ION Store" by Cullen Jennings and Brian
     Carpenter.

   o ion-meeting-network-requirements on "IETF Meeting Network
     Requirements" by Karen O'Donoghue, Jim Martin, Chris Elliott and
     Joel Jaeggli;

   o ion-procdocs on "The IETF Process: an Informal Guide" by Brian
     Carpenter;

   o ion-rfc-2026-in-practice on "RFC 2026 in Practice" by Brian
     Carpenter;

   o ion-subpoena on "Subpoenas in the IETF: Procedures" by Brian
     Carpenter;

   o ion-tsv-alt-cc on "Experimental Specification of New Congestion
     Control Algorithms" by Lars Eggert;

   The first 2 IONs were published on 11 January, 2007.  They were ion-
   ion-formats and ion-ion-store.  The latest ION was ion-meeting-
   network-requirements, published on 13 December, 2007.

3.2. Experiment Closure



Yevstifeyev             Expires January 8, 2012                 [Page 3]


INTERNET DRAFT                IONs Report                   July 7, 2011


   In 2008 it was identified that IONs experiment was terminated.

     The IESG has determined that IONs will not be used in the future.
     It is clear that the IESG, IAB, and IAOC need the ability to
     publish documents that do not expire and are easily updated.
     Information published as web pages, including IESG Statements, are
     sufficient for this purpose.

   was mentioned in IESG note on this topic [IESG-IONS] by Russ Housley.
    This note appeared on 28 April, 2008.  De facto, IONs experiment had
   already been concluded by that time.  This document is to have a
   permanent record of its closure, required by RFC 3933 [RFC3933].

3.3. Subsequent Actions on IONs

   All IONs were republished whether as IESG statements, Web Pages, or
   were discarded.  The full list is as follows (in alphabetical order):

   o ion-ad-sponsoring was republished as IESG statement "Guidance on
     Area Director Sponsoring of Documents" [SPONSOR];

   o ion-agenda-and-minutes was republished as Web Page "Formatting and
     Content of IETF Working Group Agendas and Minutes" [AGENDA];

   o ion-discuss criteria was republished as IESG Statement "DISCUSS
     Criteria in IESG Review" [DISCUSS];

   o ion-execd-tasks was republished as Web Page "Tasks previously
     assigned to the IETF Executive Director" [EXECD];

   o ion-ion-formats was discarded;

   o ion-ion-store was discarded.

   o ion-meeting-network-requirements was republished as Web Page "IETF
     Meeting Network Requirements" [MEETING];

   o ion-procdocs was republished as Web Page "The IETF Process: an
     Informal Guide" [PROCDOCS];

   o ion-rfc2026-in-practice was republished as the Internet-Draft "RFC
     2026 in Practice" [2026PRACTICE] (that, however, at the time of
     publication of this document, has not resulted in RFC and is
     expired);

   o ion-subpoena was republished as Web Page "Subpoenas in the IETF:
     Procedures" [SUBPOENAS];




Yevstifeyev             Expires January 8, 2012                 [Page 4]


INTERNET DRAFT                IONs Report                   July 7, 2011


   o ion-tsv-alt-cc was republished as IESG Statement "Experimental
     Specification of New Congestion Control Algorithms" [ALT-CC];

3.4. Archival Copies of IONs

   All IONs were located at
   <http://www.ietf.org/iesg/content/ions.html>, which is currently
   removed from IETF site.  However the Internet Wayback Machine project
   [WAYBACK] currently has some snapshots of this page, as well as all
   published or drafted IONs, the most current before the experiment
   closure dated 16 April, 2008.  You may freely access them at
   <http://replay.waybackmachine.org/20080416153527/http://www.ietf.org/
   IESG/content/ions.html>.

4. Conclusion

   Taking everything into account, it was considered that IONs added
   complications to the maintenance of documents but did not give a
   corresponding benefit to the IETF.  This document formally concludes
   the IONs experiment [RFC4693], as required by RFC 3933 [RFC3933].
   RFC 4693 is moved to Historic status per RFC 2026 [RFC2026] and
   [HISTORIC].

5. Security Considerations

   IONs did not include protocol specifications and therefore
   terminating this series is not believed to have any impact on
   security of the Internet.

6. IANA Considerations

   None.  RFC Editor must delete this section upon publication.

7. Acknowledgments

   Brian Carpenter provided useful comments on this document.

   Many thanks to Harald Alvestrand for his work on RFC 4693.

   I would also like to thank all the authors and editors of IONs for
   their input to the experiment, particularly (in alphabetical order)
   Jari Arkko, Brian Carpenter, Karen O'Donoghue, Lars Eggert, Chris
   Elliott, Joel Jaeggli, Cullen Jennings, Olaf Kolkman, Lucy Lynch, Jim
   Martin, David Meyer.

8. References

8.1. Normative References



Yevstifeyev             Expires January 8, 2012                 [Page 5]


INTERNET DRAFT                IONs Report                   July 7, 2011


   [RFC4693]   Alvestrand, H., "IETF Operational Notes", RFC 4693,
               October 2006.

8.2. Informative References

   [2026PRACTICE]
               Carpenter, B., "RFC 2026 in Practice", Expired Internet-
               Draft (draft-carpenter-rfc2026-practice-00), July 2008.

   [AGENDA]    D. Meyer and Kolkman, O., "Formatting and Content of IETF
               Working Group Agendas and Minutes", Web Page, January
               2007, <http://www.ietf.org/wg/agenda-minutes-
               procedures.html>.

   [ALT-CC]    L. Eggert, "Experimental Specification of New Congestion
               Control Algorithms", IESG Statement, July 2007,
               <http://www.ietf.org/iesg/statement/congestion-
               control.html>.

   [DISCUSS]   Peterson, J., "DISCUSS Criteria in IESG Review", IESG
               Statement, July 2007,
               <http://www.ietf.org/iesg/statement/discuss-
               criteria.html>.

   [EXECD]     IETF Administrative Oversight Committee, "Tasks
               previously assigned to the IETF Executive Director", Web
               Page, March 2007, <http://iaoc.ietf.org/execd-
               tasks.html>.

   [IESG-IONS] Housley, R., "IETF Operational Notes", Web Page, April
               2008,
               <http://www.ietf.org/old/2009/u/iesgcontent/ions.html>.

   [HISTORIC]  The IESG, "IESG Statement on Designating RFCs as
               Historic", IESG Statement, June 2011,
               <http://www.ietf.org/iesg/statement/designating-rfcs-as-
               historic.html>.

   [MEETING]   O'Donoghue, K., Martin, J., Elliott, C., and J. Jaeggli,
               "IETF Meeting Network Requirements", Web Page, June 2009,
               <http://iaoc.ietf.org/network_requirements.html>.

   [PROCDOCS]  Carpenter, B., Ed., "The IETF Process: an Informal
               Guide", Web Page, February 2011,
               <http://www.ietf.org/about/process-docs.html>.

   [RFC2026]   Bradner, S., "The Internet Standards Process -- Revision
               3", BCP 9, RFC 2026, October 1996.



Yevstifeyev             Expires January 8, 2012                 [Page 6]


INTERNET DRAFT                IONs Report                   July 7, 2011


   [RFC3933]   Klensin, J. and S. Dawkins, "A Model for IETF Process
               Experiments", BCP 93, RFC 3933, November 2004.

   [SPONSOR]   The IESG, "Guidance on Area Director Sponsoring of
               Documents", IESG Statement, March 2007,
               <http://www.ietf.org/iesg/statement/ad-sponsoring-
               docs.html>.

   [SUBPOENAS] Alvestrand, H., Carpenter, B. and R. Pelletier,
               "Subpoenas in the IETF: Procedures", Web Page, January
               2007, <http://iaoc.ietf.org/subpoena.html>.

   [WAYBACK]   Internet Archive, "Internet Archive: Wayback Machine,"
               Web Page, Undated, <http://www.archive.org/web/web.php>.

Author's Addresses

   Mykyta Yevstifeyev
   8 Kuzovkov St., Apt. 25,
   Kotovsk
   Ukraine

   EMail: evnikita2@gmail.com




























Yevstifeyev             Expires January 8, 2012                 [Page 7]