draft-ietf-genarea-milestones-tool-04.txt   draft-ietf-genarea-milestones-tool-05.txt 
Network Working Group P. Hoffman Network Working Group P. Hoffman
Internet-Draft VPN Consortium Internet-Draft VPN Consortium
Updates: 6292 (if approved) August 5, 2011 Updates: 6292 (if approved) September 7, 2011
Intended status: Informational Intended status: Informational
Expires: February 6, 2012 Expires: March 10, 2012
Requirements for a Working Group Milestones Tool Requirements for a Working Group Milestones Tool
draft-ietf-genarea-milestones-tool-04 draft-ietf-genarea-milestones-tool-05
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 Groups. This document describes the requirements for the Working Group charters. This document describes the requirements for
proposed new tool, and it is intended as input to a later activity the proposed new tool, and it is intended as input to a later
for the design and development of such a tool. activity for the design and development of such a tool.
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 February 6, 2012. This Internet-Draft will expire on March 10, 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 11 skipping to change at page 2, line 11
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
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. The WG's Draft or the beginning of discussion on a particular topic. A WG's
milestones are commonly listed with the WG's charter, although the charter has several parts, with one of those parts is the milestones.
milestones are not formally part of the charter. Changing milestones currently requires Area Director (AD) 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 Area are performed manually. Normally, WG chairs send email to their AD
Director (AD) requesting that milestones be created or updated, or requesting that milestones be created or updated, or saying that one
saying that one or more milestone has been met. These messages or more milestone has been met. These messages used to come as part
sometimes come as part of charter creation or updating, but are often of charter creation or updating, but will be a separate tool after
separate (such as if a current milestone is met but there is no the requirements in this document and in [RFC6292] are met. WG
reason to update the charter itself). WG chairs sometimes send mail chairs sometimes send mail directly to the IETF Secretariat to make a
directly to the IETF Secretariat to make a change to the database of change to the database of milestones, such as to change the dates for
milestones, such as to change the dates for milestones or to say that milestones or to say that they are completed. When a WG chair sends
they are completed. 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, and the discussion it will hopefully engender, is This document is intended to bring that discussion to a general
intended to bring that discussion to a general consensus among WG consensus among WG chairs and ADs for the requirements for the
chairs and ADs for the requirements for the eventual tool. eventual tool.
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 RFP for the design and development of the tool.
This document was prepared at the request of the IAOC. 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. WG responsible AD, but ADs are not bound by such a limitation. (This is
chairs can only add or update milestones for WGs of which they are the same model used in the Datatracker for other actions: it allows
chairs. 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
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 WG chairs and 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.
skipping to change at page 4, line 17 skipping to change at page 4, line 20
to the AD for the WG as well as to the WG's chairs; the changes are to the AD for the WG as well as to the WG's chairs; the changes are
reflected immediately in the Datatracker without any need for reflected immediately in the Datatracker without any need for
approval from an AD. 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. As noted in Section 2, any AD can take any of these six actions. The
Secretariat should be able to take any of these 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. [[ NOTE: at the Quebec meeting, there the changes from that period.
was a discussion about this requirement. One proposal was that each
change would be sent to the WG mailing list, but there was a concern
that the mailing lists would get cluttered if a chair was making a
bunch of changes at once. Some WG chairs wanted to be able to
suppress the message so that they could send a message themselves
saying what was updated. Other WG chairs wanted the messages to be
batched, such as once a day. Comments about this are solicited. ]]
After this tool is launched, the IETF Secretariat will no longer need After this tool is launched, the IETF Secretariat will no longer need
to post a change to the database: the tool will do this without to post a change to the database: the tool will do this without
intervention by the Secretariat. intervention by the Secretariat.
5. Mapping Milestones to Internet-Drafts 5. Mapping Milestones to Internet-Drafts
There is currently no requirement how WG milestones map 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.
The new tool is required to make mappings between milestones and The new tool is required to make mappings between milestones and
Internet-Drafts explicit, and those drafts must be listed in views of Internet-Drafts explicit, and those drafts must be listed in views of
the milestone. This change will require a change to the Datatracker the milestone. This change will require a change to the Datatracker
skipping to change at page 5, line 23 skipping to change at page 5, line 20
milestone, so it is up to the WG chairs to decide what to do when milestone, so it is up to the WG chairs to decide what to do when
such a message is received. such a message is received.
6. Reminders for WG Chairs and ADs 6. Reminders for WG Chairs and ADs
Milestone changes that do not require AD approval are made Milestone changes that do not require AD approval are made
immediately. Requested changes that require AD approval are tracked immediately. Requested changes that require AD approval are tracked
by the tool. If the AD has not approved or rejected the change by the tool. If the AD has not approved or rejected the change
within a week, email listing the request and the request date is sent within a week, email listing the request and the request date is sent
to the WG chairs and AD. That email is sent every week until the AD to the WG chairs and AD. That email is sent every week until the AD
has approved or rejected the request. has approved or rejected the request; the WG chairs are CC'd on this
mail.
The tool will also send WG chairs reminders about pending milestones. The tool will also send WG chairs reminders about pending milestones.
A message is sent when a milestone is one month from being due, at A message is sent when a milestone is one month from being due, at
the time a milestone is due, and every month in which a milestone is the time a milestone is due, and every month in which a milestone is
overdue. overdue.
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 [RFC6292] 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
skipping to change at page 6, line 23 skipping to change at page 6, line 23
change when changes are viewed. These features should be found in change when changes are viewed. These features should be found in
the same place as the features described in Section 5.2 of [RFC6292]. 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
the month and year that it was completed.
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.
skipping to change at page 6, line 48 skipping to change at page 7, line 6
11. References 11. References
11.1. Normative References 11.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.
[RFC6292] Hoffman, P., "Requirements for a Working Group Charter [RFC6293] Hoffman, P., "Requirements for Internet-Draft Tracking by
Tool", RFC 6292, June 2011. the IETF Community in the Datatracker", RFC 6293,
June 2011.
11.2. Informative References 11.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.
Appendix A. Earlier Proposals [RFC6292] Hoffman, P., "Requirements for a Working Group Charter
Tool", RFC 6292, June 2011.
The first few drafts of this document had a different model for
approval of milestone additions and changes. Those drafts said "The
responsible AD for a WG can specify whether any of the following
actions can be made without the AD approval for milestones associated
with the WG: create new milestones, delete milestones, change
milestone descriptions, change milestone due dates, change which
Internet-Drafts are associated with a milestone, assert that a
milestone is completed." In addition, the earlier drafts said that
the default settings when the featured would have been launched would
be that all actions other than changing due dates and asserting
completion require AD approval.
The current draft has quite a different mechanism described in
Section 4.
Also, some participants in the early discussion felt that the new
tool should have a mode where milestones whose essence is that a
particular draft is sent to the IESG is automatically marked as
complete when the draft's state is that it has gone to IETF
consideration. However, there was a fair amount of disagrement about
the need for such a mode and whether it would end up restricting
actions that should remain flexible.
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. 18 change blocks. 
63 lines changed or deleted 47 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/