Internet Society Frontpage

Events Membership
About the Internet Standards
Publications  Public Policy
About ISOC Education

Standards 

RFC Editor and Published Standards

Statements of Work 2005

Proposal to Internet Society for a Supplemental Agreement on the Request for Comments Editor Task

Period of Performance: 01-January-2005 thru 31-December-2005

BY
INFORMATION SCIENCES INSTITUTE
UNIVERSITY OF SOUTHERN CALIFORNIA
LOS ANGELES, CALIFORNIA 90089-1147

ISI Proposal No. 2004-ISI-161

ISI Contacts: Joyce K. Reynolds, Bob Braden
(310) 822-1511, {jkrey,braden}@isi.edu
FAX: (310) 823-6714

ISI Administrative Contact: Michelle C. Rodriguez
Contract & Grant Administrator
Tel: (213) 821-1106, Fax: (213) 740-6070, E-mail: michelle.r@usc.edu
University of Southern California
Department of Contracts & Grants
837 W. Downey Way, STO 330
Los Angeles, CA  90089-1147

Type of Business: Other Educational
Principal Investigator
Herbert Schorr, Executive Director, USC/ISI

Approved by the University by:
Paulina Tagle
Senior Contracts and Grants Administrator
University of Southern California

A. INTRODUCTION

This proposal is to extend and modify an existing agreement between the USC Information Sciences Institute (ISI) and the Internet Society (ISOC), under which ISI has been performing the Internet administrative function that is known as the “RFC Editor”. The existing agreement covers the period 01 January 2004 through 31 December 2004. This extension proposal amends the Statement of Work and the Budget sections of the existing agreement, to extend the period of performance for the one-year period 01 January 2005 through 31 December 2005.

B. STATEMENT OF WORK

ISI’s RFC Editor team will continue to edit and publish "RFC" documents under the terms of the existing agreement, by performing the following specific tasks.

(1) Publication Process

The RFC Editor will edit and publish RFCs in accordance with RFC 2026, RFC 3667, RFC 3668, and all other applicable agreed-upon documents and procedures, and according to the rules stated in the “RFC 2223bis” document.

RFC publication includes the following tasks:

  • Editing to maintain consistency of style, editorial standards, and clarity. At minimum, the RFC Editor will:
  • Copy-edit the documents. This includes checking spelling and grammar, ensuring readable formatting, checking for inconsistent notation, and resolving ill-formed or ambiguous sentences.
  • Enforce the formatting rules of Section 3 of RFC 2223bis.
  • Ensure that the title, abstract, and body follow guidelines and rules of Section 4 of RFC 2223bis
  • Verify the consistency of references and citations, and verify contents of references to RFCs and I-Ds.
  • Verify that all normative dependencies have been satisfied.
  • Verify satisfaction of the guidelines from Section 2 of RFC 2223bis with respect to: URLs, titles, abbreviations, IANA Considerations, author lists, and Requirement-Level words.
  • Supply the copyright and IPR boilerplate required by RFCs 3667, 3668.
  • Typeset the documents in the standard RFC style.
  • Perform mechanical verification of the formal correctness of MIBs, PIBs, ABNF definitions, XML, and XML schema.
  • Reviewing independent submissions for technical competence, relevance, and editorial quality, with the aid and advice from the Editorial Board. We will work with the authors when necessary to raise the quality of independent submissions.
  • Publishing new RFCs online by installing them in the official RFC archive, which is accessible via HTTP, FTP, SMTP, and rsync. The RFC Editor will also continue to provide compressed aggregate files containing subsets of the complete RFC series, accessible via HTTP and FTP.
  • Publicly announcing the availability of new RFCs via a mailing list.
  • Coordinating with the IANA for assignment of protocol parameter values for RFCs in the submission queue.
  • Coordinating closely with the IESG to ensure that the rules of RFC 2026 (or replacement) are followed. RFC Editor personnel attend IETF meetings. A designated RFC Editor person serves as liaison to the IAB and IESG.

(2) RFC Information

The RFC Editor will continue to publish the following status information via the Web and FTP:

  • The master index of all published RFCs, including bibliographic information and document categories. This index is published both in human and machine-readable (TXT and XML) forms.
  • The current “Official Internet Protocols” list. This is also periodically published as STD 1.
  • A list of errors (errata) found in published RFCs.
  • An "RFC Editor Queue" specifying the stage of every document in the process of editing, review, and publication.
  • An RFC Editor web site containing a search engine for RFCs, information on the RFC publication process, and links to the published items.

The RFC Editor will also operate the rfc-interest@rfc-editor.org email list, open to all members of the Internet community, for dissemination of detailed information about the RFC Editor and for discussion of all matters related to the RFC Editor.

Finally, the RFC Editor will respond to, and when appropriate redirect, the wide range of email queries received in the RFC Editor mailbox, within a reasonable time frame.

(3) Improvements and Extensions

The RFC Editor will devote modest effort to extending its services and improving its productivity tools, as resources are available from the primary tasks of document editing and production. Additional tasks that require significant resources may be accommodated by agreement between ISI and the TLG.

(3) RFC-Online

We will devote not more than 5% of our resources to completing the RFC Online project, to bring online those early RFCs that are currently available only in paper form.

(4) Reporting

We will produce at least the following reports:

  • A weekly summary of the RFC Editor queue, for the TLG (an oversight group comprised of the chair of the IAB, the chair of the IETF, and the CEO of the Internet Society).
  • A quarterly summary of financial information for the TLG.
  • A plenary report to each IETF meeting, preserved on the RFC Editor web site.
  • A monthly status report to the IETF community.

(5) RFC-Online

  • We will devote not more than 5% of our resources to completing the RFC Online project, to bring online those early RFCs that are currently available only in paper form.