draft-ietf-genarea-milestones-tool-05.txt   draft-ietf-genarea-milestones-tool-06.txt 
Network Working Group P. Hoffman Network Working Group P. Hoffman
Internet-Draft VPN Consortium Internet-Draft VPN Consortium
Updates: 6292 (if approved) September 7, 2011 Updates: 6292, 6293 October 6, 2011
(if approved)
Intended status: Informational Intended status: Informational
Expires: March 10, 2012 Expires: April 8, 2012
Requirements for a Working Group Milestones Tool Requirements for a Working Group Milestones Tool
draft-ietf-genarea-milestones-tool-05 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. activity for the design and development of such a tool. This
document updates RFC 6292 and RFC 6293.
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on March 10, 2012. This Internet-Draft will expire on April 8, 2012.
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 17 skipping to change at page 2, line 19
[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, with 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. Normally, WG chairs send email to their AD are performed manually by the Secretariat. Normally, WG chairs send
requesting that milestones be created or updated, or saying that one email to their AD requesting that milestones be created or updated.
or more milestone has been met. These messages used to come as part They send mail to the their AD, or directly to the Secretariat, when
of charter creation or updating, but will be a separate tool after one or more milestone has been met. Apart from during WG creation,
the requirements in this document and in [RFC6292] are met. WG these updates will be made through a separate tool after the
chairs sometimes send mail directly to the IETF Secretariat to make a requirements in this document and in [RFC6292] are met.
change to the database of milestones, such as to change the dates for
milestones or to say that they are completed. When a WG chair sends
email to the Secretariat, the Secretariat must obtain the approval of
the AD before taking the requested action.
In early 2011, the IETF approved a set of requirements for a tool In early 2011, the IETF approved a set of requirements for a tool
that helps ADs with the WG chartering and rechartering process that helps ADs with the WG chartering and rechartering process
[RFC6292]. During the IESG discussion of that document, it became [RFC6292]. During the IESG discussion of that document, it became
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 among WG chairs and ADs for the requirements for the consensus for the requirements for the eventual tool.
eventual tool.
Note that this document only discusses updating milestones that an
active WG is working against. As described in [RFC6292], when a WG
is rechartering, the new charter might also include new milestones.
The tool described here must not change the milestones that are
proposed for a WG recharter. That is, there must be two sets of
milestones kept by the Datatracker, one for the current WG charter
and ones that appear in a proposed recharter, and the tool described
here must only affect the first of these two sets.
The IAOC would like to create a better tool for the tasks of WG The IAOC would like to create a better tool for the tasks of WG
milestone creation and updating, and this document lists the milestone creation and updating, and this document lists the
requirements for such a tool. When complete, this document may be requirements for such a tool. When complete, this document may be
used to issue an RFP for the design and development of the tool. used to issue an request for proposals for the design and development
This document was prepared at the request of the IAOC. 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.
Any AD can add or update any milestone for any WG. Normally, an AD Any AD can add or update any milestone for any WG. Normally, an AD
would only add or update milestones in the WGs for which they are the would only add or update milestones in the WGs for which they are the
responsible AD, but ADs are not bound by such a limitation. (This is responsible AD, but ADs are not bound by such a limitation. (This is
the same model used in the Datatracker for other actions: it allows the same model used in the Datatracker for other actions: it allows
one AD to carry the load for an AD who is temporarily unable to one AD to carry the load for an AD who is temporarily unable to
perform such tasks.) WG chairs can only add or update milestones for perform such tasks.) WG chairs can only add or update milestones for
WGs of which they are chairs. WGs of which they are chairs.
The IETF Secretariat needs to be able to perform the same tasks as The IETF Secretariat needs to be able to perform the same tasks as
the WG chairs and ADs in order to fix problems or to make emergency the ADs in order to fix problems or to make emergency changes.
changes.
The database will record the date and person who initiates any The database will record the date and person who initiates any
addition of, or change to, a milestone. The contents of the database addition of, or change to, a milestone. The contents of the database
will be visible to the IETF community so that anyone can see who made will be visible to the IETF community so that anyone can see who made
a particular change to a milestone. a particular change to a milestone.
3. Updating, Adding, and Deleting Milestones 3. Updating, Adding, and Deleting Milestones
A WG chair needs to see all of the milestones for that chair's WG in A WG chair needs to see all of the milestones for that chair's WG in
the tool. The chair needs to be able to edit any milestone record the tool. The chair needs to be able to change any milestone record
for that chair's WG. In each existing record, the chair needs to be for that chair's WG. In each existing record, the chair needs to be
able to edit the due date, the finished date, the associated able to change the due date, the finished date, the associated
Internet-Drafts, and the description of the milestone. The chair Internet-Drafts, and the description of the milestone. The chair
also needs to be able to delete existing milestones. also needs to be able to delete existing milestones.
A WG chair needs to be able to add one or more milestone records to A WG chair needs to be able to add one or more milestone records to
the database for their WG. The chair needs to be able to specify the the database for their WG. The chair needs to be able to specify the
due date, zero or more associated Internet-Drafts, and the due date, zero or more associated Internet-Drafts, and the
description of the record that he or she is adding. A WG chair also description of the record that he or she is adding.
needs to be able to delete one or more existing milestones.
4. Acceptance of Milestone Additions and Changes 4. Acceptance of Milestone Additions and Changes
There are six actions associated with adding and changing milestones: There are six actions associated with adding and changing milestones:
o create new milestones o create new milestones
o delete milestones o delete milestones
o change milestone descriptions o change milestone descriptions
o change milestone due dates o change milestone due dates
o change which Internet-Drafts are associated with a milestone o change which Internet-Drafts are associated with a milestone
o assert that a milestone is completed
o assert that a milestone is no longer due
In addition to the above six actions, the tool must support
reordering of the list of milestones.
WG chairs can change milestone due dates, change which Internet- WG chairs can change milestone due dates, change which Internet-
Drafts are associated with a milestone, and can assert that a Drafts are associated with a milestone, can assert that a milestone
milestone is completed, for their WG. When any of these three is no longer due, for their WG, and reorder the list. When any of
actions are taken in the Datatracker, an email notification is sent these three actions are taken in the Datatracker, an email
to the AD for the WG as well as to the WG's chairs; the changes are notification is sent to the AD for the WG as well as to the WG's
reflected immediately in the Datatracker without any need for chairs; the changes are reflected immediately in the Datatracker
approval from an AD. without any need for approval from an AD.
WG chairs can also create new milestones, delete milestones, and WG chairs can also create new milestones, delete milestones, and
change milestone descriptions; however, any of these action are not change milestone descriptions; however, any of these action are not
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.
As noted in Section 2, any AD can take any of these six actions. The When creating a milestone, it must be possible to set a due date. It
Secretariat should be able to take any of these actions as well. must also be to change the due date at any time.
When asserting that a milestone is no longer due, it must be possible
to provide an arbitrary short description phrase. Often this phrase
will be "Done", but other phrases such as "On hold" are also allowed.
When the Datatracker presents milestones, it is not expected to
associate any semantic with the provided phrases other than that the
milestone is no longer due. The Datatracker will present the list of
milestones in the order given in the tool.
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
Secretariat will no longer need to post a change to the database
because the tool will do this without intervention by the
Secretariat; however, the Secretariat can take any of these six
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.
Once a day, the Datatracker will look for changes to the milestones Once a day, the Datatracker will look for changes to the milestones
for a WG. If changes to milestones have been made in the past 24 for a WG. If changes to milestones have been made in the past 24
hours, the Datatracker will send one message to the WG listing all hours, the Datatracker will send one message to the WG listing all
the changes from that period. the changes from that period.
After this tool is launched, the IETF Secretariat will no longer need The Datatracker needs to have a method for ADs and the Secretariat to
to post a change to the database: the tool will do this without see all the milestones that are pending approval. This list should
intervention by the Secretariat. be sorted by the responsible AD.
5. Mapping Milestones to Internet-Drafts 5. Mapping Milestones to Internet-Drafts
There is currently no mechanism to map WG milestones to Internet- There is currently no mechanism to map WG milestones to Internet-
Drafts. While most milestones map one-to-one with Internet-Drafts, Drafts. While most milestones map one-to-one with Internet-Drafts,
some milestones do not map to any Internet-Draft (such as those that some milestones do not map to any Internet-Draft (such as those that
say when a general discussion will begin or finish), and other say when a general discussion will begin or finish), and other
milestones map to multiple Internet-Drafts (such as a milestone that milestones map to multiple Internet-Drafts (such as a milestone that
covers a topic that has multiple related Internet-Drafts). Some covers a topic that has multiple related Internet-Drafts). Some
Internet-Drafts are part of more than one milestone. Internet-Drafts are part of more than one milestone.
skipping to change at page 5, line 38 skipping to change at page 6, line 17
The tool will also send WG chairs reminders about Internet-Drafts The tool will also send WG chairs reminders about Internet-Drafts
that are mapped to milestones. A message is sent when such a draft that are mapped to milestones. A message is sent when such a draft
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.
The Datatracker needs to have a method for ADs and the Secretariat to
see all the milestones that are pending approval.
7. Viewing Changes in Milestones 7. Viewing Changes in Milestones
Section 5 of [RFC6293] describes an extension to the Datatracker to Section 5 of [RFC6293] describes an extension to the Datatracker to
allow the IETF community to view, search, and track changes to WG allow the IETF community to view, search, and track changes to WG
charters. This document updates those requirements to allow the IETF charters. This document updates those requirements to allow the IETF
community to view, search, and track changes to WG milestones. community to 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, the full set of milestones is considered changed. its fields changed, or the list is re-ordered, the full set of
Someone should be able to easily compare two full sets of milestones. milestones is considered changed. Someone should be able to easily
They should also be able to see two more full sets of milestones with compare two full sets of milestones. They should also be able to see
the differences highlighted. The tool should show who made each two more full sets of milestones with the differences highlighted.
change when changes are viewed. These features should be found in The tool should show who made each change when changes are viewed.
the same place as the features described in Section 5.2 of [RFC6292]. These features should be found in the same place as the features
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 completed, the Datatracker will display When a milestone is marked as no longer due, the Datatracker will
the month and year that it was completed. display the month and year that this change was made and will display
the status (such as "Done" or "On hold").
8. IANA Considerations 8. IANA Considerations
None. [[ ...and thus this section can be removed before publication None. [[ ...and thus this section can be removed before publication
as an RFC... ]] as an RFC... ]]
9. Security Considerations 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.
 End of changes. 20 change blocks. 
49 lines changed or deleted 70 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/