draft-ietf-genarea-milestones-tool-06.txt   rfc6433.txt 
Network Working Group P. Hoffman Internet Engineering Task Force (IETF) P. Hoffman
Internet-Draft VPN Consortium Request for Comments: 6433 VPN Consortium
Updates: 6292, 6293 October 6, 2011 Updates: 6292 November 2011
(if approved) Category: Informational
Intended status: Informational ISSN: 2070-1721
Expires: April 8, 2012
Requirements for a Working Group Milestones Tool Requirements for a Working Group Milestones Tool
draft-ietf-genarea-milestones-tool-06
Abstract Abstract
The IETF intends to provide a new tool to Working Group chairs and The IETF intends to provide a new tool to Working Group chairs and
Area Directors for the creation and updating of milestones for Area Directors for the creation and updating of milestones for
Working Group charters. This document describes the requirements for Working Group charters. This document describes the requirements for
the proposed new tool, and it is intended as input to a later the proposed new tool, and it is intended as input to a later
activity for the design and development of such a tool. This activity for the design and development of such a tool. This
document updates RFC 6292 and RFC 6293. document updates RFC 6292.
Status of this Memo
This Internet-Draft is submitted in full conformance with the Status of This Memo
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering This document is not an Internet Standards Track specification; it is
Task Force (IETF). Note that other groups may also distribute published for informational purposes.
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Not all documents
approved by the IESG are a candidate for any level of Internet
Standard; see Section 2 of RFC 5741.
This Internet-Draft will expire on April 8, 2012. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc6433.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 14 skipping to change at page 2, line 11
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
1. Introduction 1. Introduction
[RFC2418] describes the guidelines and procedures for operation of [RFC2418] describes the guidelines and procedures for operation of
IETF Working Groups (WGs). Every WG has milestones that the WG is IETF Working Groups (WGs). Every WG has milestones that the WG is
supposed to meet, such as the publication of a particular Internet- supposed to meet, such as the publication of a particular Internet-
Draft or the beginning of discussion on a particular topic. A WG's Draft or the beginning of discussion on a particular topic. A WG's
charter has several parts, with one of those parts is the milestones. charter has several parts; one of those parts is the milestones.
Changing milestones currently requires Area Director (AD) approval, Changing milestones currently requires Area Director (AD) approval,
but changing the charter text requires IESG approval. but changing the charter text requires IESG approval.
Today, the tasks associated with creating and updating WG milestones Today, the tasks associated with creating and updating WG milestones
are performed manually by the Secretariat. Normally, WG chairs send are performed manually by the Secretariat. Normally, WG chairs send
email to their AD requesting that milestones be created or updated. email to their AD requesting that milestones be created or updated.
They send mail to the their AD, or directly to the Secretariat, when They send mail to the their AD, or directly to the Secretariat, when
one or more milestone has been met. Apart from during WG creation, one or more milestone has been met. Apart from during WG creation,
these updates will be made through a separate tool after the these updates will be made through a separate tool after the
requirements in this document and in [RFC6292] are met. requirements in this document and in [RFC6292] are met.
skipping to change at page 2, line 39 skipping to change at page 2, line 36
clear that everyone wanted more automation to the milestones process. clear that everyone wanted more automation to the milestones process.
This document is intended to bring that discussion to a general This document is intended to bring that discussion to a general
consensus for the requirements for the eventual tool. consensus for the requirements for the eventual tool.
Note that this document only discusses updating milestones that an Note that this document only discusses updating milestones that an
active WG is working against. As described in [RFC6292], when a WG active WG is working against. As described in [RFC6292], when a WG
is rechartering, the new charter might also include new milestones. is rechartering, the new charter might also include new milestones.
The tool described here must not change the milestones that are The tool described here must not change the milestones that are
proposed for a WG recharter. That is, there must be two sets of proposed for a WG recharter. That is, there must be two sets of
milestones kept by the Datatracker, one for the current WG charter milestones kept by the Datatracker, one for the current WG charter
and ones that appear in a proposed recharter, and the tool described and one for a proposed recharter; the tool described here must only
here must only affect the first of these two sets. affect the first of these two sets.
The IAOC would like to create a better tool for the tasks of WG The IETF Administrative Oversight Committee (IAOC) would like to
milestone creation and updating, and this document lists the create a better tool for the tasks of WG milestone creation and
requirements for such a tool. When complete, this document may be updating, and this document lists the requirements for such a tool.
used to issue an request for proposals for the design and development When complete, this document may be used to issue an request for
of the tool. This document was prepared at the request of the IAOC. proposals for the design and development of the tool. This document
was prepared at the request of the IAOC.
2. Users of the Tool 2. Users of the Tool
This tool can only be used by WG chairs and ADs, not by other members This tool can only be used by WG chairs and ADs, not by other members
of the IETF community. The tool will use the login and access of the IETF community. The tool will use the login and access
control features that will already be in place from the outcome of control features that will already be in place from the outcome of
the tool created by [RFC6292]. It is important to note that some the tool created by [RFC6292]. It is important to note that some
people are chairs for more than one WG, and everyone must be able to people are chairs for more than one WG, and everyone must be able to
use the tool for all of the WGs that they chair. use the tool for all of the WGs that they chair.
skipping to change at page 4, line 37 skipping to change at page 4, line 31
reflected in the Datatracker until the action is approved by an AD. reflected in the Datatracker until the action is approved by an AD.
When a WG chair makes the proposed change, an email notification is When a WG chair makes the proposed change, an email notification is
sent to the AD for the WG as well as to the WG's chairs. sent to the AD for the WG as well as to the WG's chairs.
When creating a milestone, it must be possible to set a due date. It When creating a milestone, it must be possible to set a due date. It
must also be to change the due date at any time. must also be to change the due date at any time.
When asserting that a milestone is no longer due, it must be possible When asserting that a milestone is no longer due, it must be possible
to provide an arbitrary short description phrase. Often this phrase to provide an arbitrary short description phrase. Often this phrase
will be "Done", but other phrases such as "On hold" are also allowed. will be "Done", but other phrases such as "On hold" are also allowed.
When the Datatracker presents milestones, it is not expected to When the Datatracker presents a milestone, the only information that
associate any semantic with the provided phrases other than that the is expected to be associated with the provided phrase is that the
milestone is no longer due. The Datatracker will present the list of milestone is no longer due. The Datatracker will present the list of
milestones in the order given in the tool. milestones in the order given in the tool.
As noted in Section 2, any AD can take any of these six actions, as As noted in Section 2, any AD can take any of these six actions, as
well reordering the list. After this tool is launched, the IETF well as reordering the list. After this tool is launched, the IETF
Secretariat will no longer need to post a change to the database Secretariat will no longer need to post a change to the database
because the tool will do this without intervention by the because the tool will do this without intervention by the
Secretariat; however, the Secretariat can take any of these six Secretariat; however, the Secretariat can take any of these six
actions as well. actions as well.
When adding or editing a milestone, the AD or WG Chair must be able When adding or editing a milestone, the AD or WG Chair must be able
to review and change the proposed change before committing the change to review and change the proposed change before committing the change
to the Datatracker. This will help prevent errors and reduce the to the Datatracker. This will help prevent errors and reduce the
number of fixes that need to be made. number of fixes that need to be made.
skipping to change at page 6, line 19 skipping to change at page 6, line 11
is one month from expiring, and at the time that a draft expires. If is one month from expiring, and at the time that a draft expires. If
a milestone is mapped to a draft that is expired, mail reminding the a milestone is mapped to a draft that is expired, mail reminding the
chairs of this will be sent weekly. chairs of this will be sent weekly.
When a WG chair makes an Internet-Draft a WG work item, the When a WG chair makes an Internet-Draft a WG work item, the
Datatracker will remind them that they may want to also add that Datatracker will remind them that they may want to also add that
document to a milestone. document to a milestone.
7. Viewing Changes in Milestones 7. Viewing Changes in Milestones
Section 5 of [RFC6293] describes an extension to the Datatracker to [RFC6292] describes an extension to the Datatracker to allow the IETF
allow the IETF community to view, search, and track changes to WG community to view, search, and track changes to WG charters. This
charters. This document updates those requirements to allow the IETF document updates those requirements to allow the IETF community to
community to view, search, and track changes to WG milestones. view, search, and track changes to WG milestones.
Section 5.1 of [RFC6292] is updated to allow searching for any text Section 5.1 of [RFC6292] is updated to allow searching for any text
in a milestone's description, as well as for the name of any in a milestone's description, as well as for the name of any
Internet-Draft name that is mapped to any milestone. Internet-Draft name that is mapped to any milestone.
A new capability will be added to the Datatracker that is similar to A new capability will be added to the Datatracker that is similar to
that described in Section 5.2 of [RFC6292], but instead of showing that described in Section 5.2 of [RFC6292], but instead of showing
differences between charters, it shows differences between the full differences between charters, it shows differences between the full
set of milestones. Any time a milestone is added, deleted, or any of set of milestones. Any time a milestone is added, deleted, or any of
its fields changed, or the list is re-ordered, the full set of its fields changed, or the list is reordered, the full set of
milestones is considered changed. Someone should be able to easily milestones is considered changed. A user should be able to easily
compare two full sets of milestones. They should also be able to see compare two full sets of milestones with the differences highlighted.
two more full sets of milestones with the differences highlighted.
The tool should show who made each change when changes are viewed. The tool should show who made each change when changes are viewed.
These features should be found in the same place as the features These features should be found in the same place as the features
described in Section 5.2 of [RFC6292]. described in Section 5.2 of [RFC6292].
The tool needs to provide an Atom feed [RFC4287] for the changes in The tool needs to provide an Atom feed [RFC4287] for the changes in
the milestones for a WG. The contents of the feed are the full WG the milestones for a WG. The contents of the feed are the full WG
record, plus an indication of what changed since the last entry in record, plus an indication of what changed since the last entry in
the feed and who made the change. This feed is different than the the feed and who made the change. This feed is different than the
feed described in Section 5.3 of [RFC6292], but it should be offered feed described in Section 5.3 of [RFC6292], but it should be offered
to users in the same places as that feed is offered. to users in the same places as that feed is offered.
When a milestone is marked as no longer due, the Datatracker will When a milestone is marked as no longer due, the Datatracker will
display the month and year that this change was made and will display display the month and year that this change was made and will display
the status (such as "Done" or "On hold"). the status (such as "Done" or "On hold").
8. IANA Considerations 8. Security Considerations
None. [[ ...and thus this section can be removed before publication
as an RFC... ]]
9. Security Considerations
Creating a new tool for updating the milestones of WGs does not Creating a new tool for updating the milestones of WGs does not
affect the security of the Internet in any significant fashion. affect the security of the Internet in any significant fashion.
10. Acknowledgements 9. Acknowledgements
This document draws heavily on ideas from various WG chairs and ADs This document draws heavily on ideas from various WG chairs and ADs
on the wgchairs@ietf.org mailing list. on the wgchairs@ietf.org mailing list.
11. References 10. References
11.1. Normative References 10.1. Normative References
[RFC2418] Bradner, S., "IETF Working Group Guidelines and [RFC2418] Bradner, S., "IETF Working Group Guidelines and
Procedures", BCP 25, RFC 2418, September 1998. Procedures", BCP 25, RFC 2418, September 1998.
[RFC6174] Juskevicius, E., "Definition of IETF Working Group [RFC6174] Juskevicius, E., "Definition of IETF Working Group
Document States", RFC 6174, March 2011. Document States", RFC 6174, March 2011.
[RFC6293] Hoffman, P., "Requirements for Internet-Draft Tracking by [RFC6292] Hoffman, P., "Requirements for a Working Group Charter
the IETF Community in the Datatracker", RFC 6293, Tool", RFC 6292, June 2011.
June 2011.
11.2. Informative References 10.2. Informative References
[RFC4287] Nottingham, M., Ed. and R. Sayre, Ed., "The Atom [RFC4287] Nottingham, M., Ed. and R. Sayre, Ed., "The Atom
Syndication Format", RFC 4287, December 2005. Syndication Format", RFC 4287, December 2005.
[RFC6292] Hoffman, P., "Requirements for a Working Group Charter
Tool", RFC 6292, June 2011.
Author's Address Author's Address
Paul Hoffman Paul Hoffman
VPN Consortium VPN Consortium
Email: paul.hoffman@vpnc.org EMail: paul.hoffman@vpnc.org
 End of changes. 22 change blocks. 
56 lines changed or deleted 44 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/