draft-ietf-genarea-milestones-tool-02.txt   draft-ietf-genarea-milestones-tool-03.txt 
Network Working Group P. Hoffman Network Working Group P. Hoffman
Internet-Draft VPN Consortium Internet-Draft VPN Consortium
Updates: July 11, 2011 Updates: 6292 (if approved) August 1, 2011
raft-ietf-genarea-charter-tool
(if approved)
Intended status: Informational Intended status: Informational
Expires: January 12, 2012 Expires: February 2, 2012
Requirements for a Working Group Milestones Tool Requirements for a Working Group Milestones Tool
draft-ietf-genarea-milestones-tool-02 draft-ietf-genarea-milestones-tool-03
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 Groups. This document describes the requirements for the
proposed new tool, and it is intended as input to a later activity proposed new tool, and it is intended as input to a later activity
for the design and development of such a tool. for the design and development of such a tool.
Status of this Memo Status of this Memo
skipping to change at page 1, line 37 skipping to change at page 1, line 35
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 January 12, 2012. This Internet-Draft will expire on February 2, 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 30 skipping to change at page 2, line 28
saying that one or more milestone has been met. These messages saying that one or more milestone has been met. These messages
sometimes come as part of charter creation or updating, but are often sometimes come as part of charter creation or updating, but are often
separate (such as if a current milestone is met but there is no separate (such as if a current milestone is met but there is no
reason to update the charter itself). WG chairs sometimes send mail reason to update the charter itself). WG chairs sometimes send mail
directly to the IETF Secretariat to make a change to the database of directly to the IETF Secretariat to make a change to the database of
milestones, such as to change the dates for milestones or to say that milestones, such as to change the dates for milestones or to say that
they are completed. they are completed.
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
[CHARTER-TOOL]. During the IESG discussion of that document, it [RFC6292]. During the IESG discussion of that document, it became
became clear that everyone wanted more automation to the milestones clear that everyone wanted more automation to the milestones process.
process. This document, and the discussion it will hopefully This document, and the discussion it will hopefully engender, is
engender, is intended to bring that discussion to a general consensus intended to bring that discussion to a general consensus among WG
among WG chairs and ADs for the requirements for the eventual tool. chairs and ADs for the requirements for the 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.
1.1. Discussion of These Requirements 1.1. Discussion of These Requirements
This document is being discussed on the wgchairs@ietf.org mailing This document is being discussed on the wgchairs@ietf.org mailing
list. See <https://www.ietf.org/mailman/listinfo/wgchairs> for more list. See <https://www.ietf.org/mailman/listinfo/wgchairs> for more
information. [[ This subsection is to be deleted before publication. information. [[ This subsection is to be deleted before publication.
]] ]]
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 [CHARTER-TOOL]. It is important to note that the tool created by [RFC6292]. It is important to note that some
some people are chairs for more than one WG, and everyone must be people are chairs for more than one WG, and everyone must be able to
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. WG
chairs can only add or update milestones for WGs of which they are chairs can only add or update milestones for WGs of which they are
chairs. 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.
skipping to change at page 3, line 44 skipping to change at page 3, line 40
able to edit the due date, the finished date, the associated able to edit 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. A WG chair also
needs to be able to delete one or more existing milestones. needs to be able to delete one or more existing milestones.
4. Automatic Acceptance of Milestone Additions and Changes 4. Acceptance of Milestone Additions and Changes
Each change made by a WG chair will be automatically accepted by the There are six actions associated with adding and changing milestones:
tool. If either chair of a WG wants to revert a change, such as if a
change was made in error, those WG chairs can make a subsequent
change. It is likely that such change-and-revert cycles will happen
as WG chairs get used to the new tool.
As noted in Section 2, any AD can change any milestone. Thus, if a o create new milestones
WG chair makes an erroneous change to a milestone and does not fix
the error themselves, any AD may fix it for them. In practice, it o delete milestones
would be better if those who make errors fix the errors themselves.
o change milestone descriptions
o change milestone due dates
o change which Internet-Drafts are associated with a milestone
o assert that a milestone is completed
WG chairs can change milestone due dates, change which Internet-
Drafts are associated with a milestone, and can assert that a
milestone is completed, for their WG. When any of these three
actions are taken in the Datatracker, an email notification is sent
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
approval from an AD.
WG chairs can also create new milestones, delete milestones, and
change milestone descriptions; however, any of these action are not
reflected in the Datatracker until the action is approved by an AD.
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.
As noted in Section 2, any AD can take any of these six actions.
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 the Datatracker. This will help prevent errors and reduce the
number of fixes that need to be made.
When any of these six actions is reflected in the Datatracker, an
email notification is sent to the WG mailing list by the Datatracker.
[[ NOTE: at the Quebec meeting, there was a discussion about this
requirement. 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 requirement how WG milestones map 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
skipping to change at page 5, line 11 skipping to change at page 5, line 41
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 an Internet-Draft is added to a WG, the Datatracker will send a
message to the WG chairs reminding them that they might want to add
it to a milestone or create a new milestone for it. Once a month,
the Datatracker will send mail to the WG chairs if there are WG
Internet-Drafts that are not in any WG milestones.
7. Viewing Changes in Milestones 7. Viewing Changes in Milestones
Section 5 of [CHARTER-TOOL] describes an extension to the Datatracker Section 5 of [RFC6292] describes an extension to the Datatracker to
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 [CHARTER-TOOL] is updated to allow searching for any Section 5.1 of [RFC6292] is updated to allow searching for any text
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 [CHARTER-TOOL], but instead of that described in Section 5.2 of [RFC6292], but instead of showing
showing differences between charters, it shows differences between differences between charters, it shows differences between the full
the full set of milestones. Any time a milestone is added, deleted, set of milestones. Any time a milestone is added, deleted, or any of
or any of its fields changed, the full set of milestones is its fields changed, the full set of milestones is considered changed.
considered changed. Someone should be able to easily compare two Someone should be able to easily compare two full sets of milestones.
full sets of milestones. They should also be able to see two more They should also be able to see two more full sets of milestones with
full sets of milestones with the differences highlighted. The tool the differences highlighted. The tool should show who made each
should show who made each change when changes are viewed. These change when changes are viewed. These features should be found in
features should be found in the same place as the features described the same place as the features described in Section 5.2 of [RFC6292].
in Section 5.2 of [CHARTER-TOOL].
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 [CHARTER-TOOL], but it should be feed described in Section 5.3 of [RFC6292], but it should be offered
offered to users in the same places as that feed is offered. to users in the same places as that feed is offered.
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 11 skipping to change at page 7, line 4
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 10. 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 11. References
11.1. Normative References 11.1. Normative References
[CHARTER-TOOL]
Hoffman, P., "Requirements for a Working Group Charter
Tool", draft-ietf-genarea-charter-tool (work in progress),
April 2011.
[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
Tool", RFC 6292, 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 Appendix A. Earlier Proposals
The first few drafts of this document had a different model for The first few drafts of this document had a different model for
approval of milestone additions and changes. Those drafts said "The approval of milestone additions and changes. Those drafts said "The
responsible AD for a WG can specify whether any of the following responsible AD for a WG can specify whether any of the following
 End of changes. 17 change blocks. 
46 lines changed or deleted 79 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/