draft-ietf-genarea-datatracker-iana-rfced-extns-03.txt   draft-ietf-genarea-datatracker-iana-rfced-extns-04.txt 
Internet Engineering Task Force (IETF) S. Ginoza Internet Engineering Task Force (IETF) S. Ginoza
Internet-Draft AMS Internet-Draft AMS
Intended Status: Informational M. Cotton Intended Status: Informational M. Cotton
Expires: December 16, 2011 ICANN Expires: December 20, 2011 ICANN
A. Morris A. Morris
AMS AMS
June 16, 2011 June 20, 2011
Datatracker Extensions to Datatracker Extensions to
Include IANA and RFC Editor Processing Information Include IANA and RFC Editor Processing Information
<draft-ietf-genarea-datatracker-iana-rfced-extns-03.txt> <draft-ietf-genarea-datatracker-iana-rfced-extns-04.txt>
Abstract Abstract
This document captures the requirements for integrating IANA and RFC This document captures the requirements for integrating IANA and RFC
Editor state information into the Datatracker to provide the Editor state information into the Datatracker to provide the
community with a unified tool to track the status of their document community with a unified tool to track the status of their document
as it progresses from Internet-Draft (I-D) version -00 to RFC. as it progresses from Internet-Draft (I-D) version -00 to RFC.
Extending the Datatracker to hold document data from I-D version -00 Extending the Datatracker to hold document data from I-D version -00
to RFC allows for increased automation between the Datatracker, IANA, to RFC allows for increased automation between the Datatracker, IANA,
and RFC Editor, thus reducing manual labor, processing errors, and and RFC Editor, thus reducing manual labor, processing errors, and
skipping to change at page 3, line 18 skipping to change at page 3, line 18
Additionally, this document lists the processes between the IANA, RFC Additionally, this document lists the processes between the IANA, RFC
Editor, and Secretariat (via the Datatracker) that should be Editor, and Secretariat (via the Datatracker) that should be
automated for accuracy and timely processing. While this document automated for accuracy and timely processing. While this document
includes some details of the IANA, RFC Editor, and Secretariat includes some details of the IANA, RFC Editor, and Secretariat
process, this document does not define any of the processes. The process, this document does not define any of the processes. The
processes are continually reviewed for process optimization and need processes are continually reviewed for process optimization and need
to remain flexible to adapt to new changes in policy and environment. to remain flexible to adapt to new changes in policy and environment.
Processes are defined and set by each of the entities respectively. Processes are defined and set by each of the entities respectively.
NOTE: The IANA and RFC Editor are independent functions and they The IANA and RFC Editor are functions independent of the IETF. When
retain ownership of their data, state names, and tracking an Internet-Draft enters the IANA queue, IANA retains ownership of
systems once a document enters their queues. This document its own data, state names, and tracking systems. Similarly, when an
discusses how the data from the IANA and RFC Editor queues Internet-Draft enters the RFC Editor's queue, the RFC Editor retains
can be better reflected in the Datatracker for ease of the ownership of its own data, state names, and tracking systems. This
community. If there is any discrepancy, the IANA and RFC document discusses how the data from the IANA and RFC Editor queues
Editor data are definitive (post approval for publication). can be better reflected in the Datatracker to help inform the IETF
Prior to a document being approved for publication, the community what the state of a document is throughout its lifetime.
Datatracker is definitive for tracking IANA status
information. The Datatracker should only allow for states
in which it is definitive to be administratively edited.
RFC Editor data is not editable via the Datatracker. The Prior to when an Internet-Draft is approved for publication as an
only way for RFC Editor substates to be updated in the RFC, the Datatracker is the definitive source for tracking IANA
Datatracker is to retrieve data from the definitive RFC status information, and the IANA data is editable (by IANA and the
Editor database. Secretariat) in the Datatracker. After an Internet-Draft is approved
for publication as an RFC, the IANA tracking system becomes the
definitive source for tracking IANA status information, and the data
can no longer be edited in the Datatracker. At that point, the data
in the Datatracker is only a reflection of the data in the IANA
tracking system. If there is a discrepancy at between the two after
this point, the data in the IANA tracking system is assumed to be
correct.
Post approval, IANA data is not editable via the The RFC Editor's tracking system is always the definitive source for
Datatracker. The only way for IANA substates to be updated tracking RFC Editor status of a document. RFC Editor data is not
in the Datatracker is to retrieve data from the definitive editable via the Datatracker. The information in the Datatracker is
IANA database. always a reflection of the information in the RFC Editor's tracking
system.
2. Integration of Data between the IANA and Datatracker 2. Integration of Data between the IANA and Datatracker
2.1. IANA Information To Be Added to the Datatracker 2.1. IANA Information To Be Added to the Datatracker
Currently, IANA reviews and touches documents at 4 different stages Currently, IANA reviews and touches documents at 4 different stages
in the process from I-D to RFC for IETF stream documents: IETF Last in the process from I-D to RFC for IETF stream documents: IETF Last
Call, IESG Review, Document Approval (for publication), and RFC Call, IESG Review, Document Approval (for publication), and RFC
Publication. Most of these state changes and issues are not captured Publication. Most of these state changes and issues are not captured
in the Datatracker. For the IRTF and INDEPENDENT streams, the IANA in the Datatracker. For the IRTF and INDEPENDENT streams, the IANA
 End of changes. 6 change blocks. 
22 lines changed or deleted 27 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/