draft-ietf-genarea-milestones-tool-03.txt   draft-ietf-genarea-milestones-tool-04.txt 
Network Working Group P. Hoffman Network Working Group P. Hoffman
Internet-Draft VPN Consortium Internet-Draft VPN Consortium
Updates: 6292 (if approved) August 1, 2011 Updates: 6292 (if approved) August 5, 2011
Intended status: Informational Intended status: Informational
Expires: February 2, 2012 Expires: February 6, 2012
Requirements for a Working Group Milestones Tool Requirements for a Working Group Milestones Tool
draft-ietf-genarea-milestones-tool-03 draft-ietf-genarea-milestones-tool-04
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 35 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 February 2, 2012. This Internet-Draft will expire on February 6, 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 40 skipping to change at page 2, line 40
This document, and the discussion it will hopefully engender, is This document, and the discussion it will hopefully engender, is
intended to bring that discussion to a general consensus among WG intended to bring that discussion to a general consensus 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
This document is being discussed on the wgchairs@ietf.org mailing
list. See <https://www.ietf.org/mailman/listinfo/wgchairs> for more
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 [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
skipping to change at page 4, line 31 skipping to change at page 4, line 24
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.
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.
When any of these six actions is reflected in the Datatracker, an Once a day, the Datatracker will look for changes to the milestones
email notification is sent to the WG mailing list by the Datatracker. for a WG. If changes to milestones have been made in the past 24
[[ NOTE: at the Quebec meeting, there was a discussion about this hours, the Datatracker will send one message to the WG listing all
requirement. There was a concern that the mailing lists would get the changes from that period. [[ NOTE: at the Quebec meeting, there
cluttered if a chair was making a bunch of changes at once. Some WG was a discussion about this requirement. One proposal was that each
chairs wanted to be able to suppress the message so that they could change would be sent to the WG mailing list, but there was a concern
send a message themselves saying what was updated. Other WG chairs that the mailing lists would get cluttered if a chair was making a
wanted the messages to be batched, such as once a day. Comments bunch of changes at once. Some WG chairs wanted to be able to
about this are solicited. ]] 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 41 skipping to change at page 5, line 36
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 When a WG chair makes an Internet-Draft a WG work item, the
message to the WG chairs reminding them that they might want to add Datatracker will remind them that they may want to also add that
it to a milestone or create a new milestone for it. Once a month, document to a milestone.
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 [RFC6292] describes an extension to the Datatracker to Section 5 of [RFC6292] 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
 End of changes. 7 change blocks. 
25 lines changed or deleted 18 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/