draft-ietf-genarea-datatracker-iana-rfced-extns-02.txt   draft-ietf-genarea-datatracker-iana-rfced-extns-03.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 15, 2011 ICANN Expires: December 16, 2011 ICANN
A. Morris A. Morris
AMS AMS
June 15, 2011 June 16, 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-02.txt> <draft-ietf-genarea-datatracker-iana-rfced-extns-03.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 NOTE: The IANA and RFC Editor are independent functions and they
retain ownership of their data, state names, and tracking systems retain ownership of their data, state names, and tracking
once a document enters their queues. This document discusses how the systems once a document enters their queues. This document
data from the IANA and RFC Editor queues can be better reflected in discusses how the data from the IANA and RFC Editor queues
the Datatracker for ease of the community. If there is any can be better reflected in the Datatracker for ease of the
discrepancy, the IANA and RFC Editor data are definitive (post community. If there is any discrepancy, the IANA and RFC
approval for publication). Prior to a document being approved for Editor data are definitive (post approval for publication).
publication, the Datatracker is definitive for tracking IANA status Prior to a document being approved for publication, the
information. 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
only way for RFC Editor substates to be updated in the
Datatracker is to retrieve data from the definitive RFC
Editor database.
Post approval, IANA data is not editable via the
Datatracker. The only way for IANA substates to be updated
in the Datatracker is to retrieve data from the definitive
IANA database.
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
skipping to change at page 3, line 50 skipping to change at page 4, line 16
information in the Datatracker. information in the Datatracker.
- IETF Last Call Comments - IETF Last Call Comments
Currently, IANA reviews I-Ds that have been sent to IETF Last Currently, IANA reviews I-Ds that have been sent to IETF Last
Call, inputs comments in their data system, and then emails their Call, inputs comments in their data system, and then emails their
comments to authors, WG chairs, and then to the IESG. These comments to authors, WG chairs, and then to the IESG. These
comments are also manually entered into the Datatracker for the comments are also manually entered into the Datatracker for the
public record. However, it is difficult to determine whether the public record. However, it is difficult to determine whether the
IANA issues have been resolved. To help facilitate tracking of IANA issues have been resolved. To help facilitate tracking of
IANA issues, 5 new substates will be added to the Datatracker: IANA issues, a display is needed to show 5 new IANA substates, in
a similar fashion to how RFC Editor State is currently shown in
the Datatracker (see example of how IANA state information could
appear in the Datatracker for draft-example-00 below).
1) IANA Review Needed 1) IANA Review Needed
This substate will allow the community, Secretariat, and IANA This substate will allow the community, Secretariat, and IANA
to easily track which documents have or have not been reviewed to easily track which documents have or have not been reviewed
by IANA. If this substate is NOT set to IANA Not OK or IANA by IANA. If this substate is NOT set to IANA Not OK or IANA
OK, the substate should be set to "IANA review needed" by OK, the substate should be set to "IANA review needed" by
default (this is the first substate for tracking IANA data). default (this is the first substate for tracking IANA data).
For documents that originate from a non-IETF stream, the For documents that originate from a non-IETF stream, the
default will be used. default will be used.
skipping to change at page 8, line 8 skipping to change at page 8, line 33
2.3. Permissions to Change IANA State Information 2.3. Permissions to Change IANA State Information
IANA state changes should be automated, but IANA should have the IANA state changes should be automated, but IANA should have the
ability to log in to the Datatracker to manually update the system as ability to log in to the Datatracker to manually update the system as
well. well.
Additionally, the IETF Secretariat should also have the ability to Additionally, the IETF Secretariat should also have the ability to
change the IANA state if necessary. change the IANA state if necessary.
It is expected that this feature would only be used to correct
issues; it is not intended to be part of regular operations.
3. Integration of Data between the RFC Editor and Datatracker 3. Integration of Data between the RFC Editor and Datatracker
For quite some time, the RFC Editor was seen as a black box, where For quite some time, the RFC Editor was seen as a black box, where
documents were submitted for publication, went through some process, documents were submitted for publication, went through some process,
and came out as RFCs. Over time, the community asked for a more and came out as RFCs. Over time, the community asked for a more
transparent process; thus, state information was made available on transparent process; thus, state information was made available on
the RFC Editor website. Currently, some of that state information is the RFC Editor website. Currently, some of that state information is
available from the Datatracker. However, for additional transparency available from the Datatracker. However, for additional transparency
about the RFC Editor process, the Datatracker should be extended to about the RFC Editor process, the Datatracker should be extended to
hold supplementary RFC Editor state and process (e.g., MISSREF) hold supplementary RFC Editor state and process (e.g., MISSREF)
 End of changes. 6 change blocks. 
13 lines changed or deleted 31 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/