draft-ietf-genarea-datatracker-community-00.txt   draft-ietf-genarea-datatracker-community-01.txt 
Network Working Group P. Hoffman Network Working Group P. Hoffman
Internet-Draft VPN Consortium Internet-Draft VPN Consortium
Intended status: Informational October 18, 2010 Intended status: Informational October 21, 2010
Expires: April 21, 2011 Expires: April 24, 2011
Requirements for Draft Tracking by the IETF Community in the Datatracker Requirements for Draft Tracking by the IETF Community in the Datatracker
draft-ietf-genarea-datatracker-community-00 draft-ietf-genarea-datatracker-community-01
Abstract Abstract
The document gives a set of requirements for extending the IETF The document gives a set of requirements for extending the IETF
Datatracker to give individual IETF community members, including the Datatracker to give individual IETF community members, including the
IETF leadership, easy methods for tracking the progress of the IETF leadership, easy methods for tracking the progress of the
Internet Drafts of interest to them. Internet Drafts of interest to them.
Status of this Memo Status of this Memo
skipping to change at page 1, line 33 skipping to change at page 1, line 33
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 April 21, 2011. This Internet-Draft will expire on April 24, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 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 45 skipping to change at page 2, line 45
2.4. File Output . . . . . . . . . . . . . . . . . . . . . . . 10 2.4. File Output . . . . . . . . . . . . . . . . . . . . . . . 10
2.4.1. Requirement: Users can get their current list as a 2.4.1. Requirement: Users can get their current list as a
single file . . . . . . . . . . . . . . . . . . . . . 10 single file . . . . . . . . . . . . . . . . . . . . . 10
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
4. Security Considerations . . . . . . . . . . . . . . . . . . . 10 4. Security Considerations . . . . . . . . . . . . . . . . . . . 10
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 11 5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 11
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11
6.1. Normative References . . . . . . . . . . . . . . . . . . . 11 6.1. Normative References . . . . . . . . . . . . . . . . . . . 11
6.2. Informative References . . . . . . . . . . . . . . . . . . 11 6.2. Informative References . . . . . . . . . . . . . . . . . . 11
Appendix A. Some Known Open Issues . . . . . . . . . . . . . . . 11 Appendix A. Some Known Open Issues . . . . . . . . . . . . . . . 11
Appendix B. Differences between -00 and -01 . . . . . . . . . . . 12
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 12 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 12
1. Introduction 1. Introduction
IMPORTANT NOTE: This is a very early draft of a set of requirements. IMPORTANT NOTE: This is a very early draft of a set of requirements.
It has gone through no general community review, and thus probably is It has gone through no general community review, and thus probably is
missing many things that should be included, and some of the things missing many things that should be included, and some of the things
in this draft are wrong and will be changed in future drafts. in this draft are wrong and will be changed in future drafts.
Nothing in this draft should be considered solid. Nothing in this draft should be considered solid.
skipping to change at page 4, line 38 skipping to change at page 4, line 38
o A "significant change in status" is all approvals and disposition. o A "significant change in status" is all approvals and disposition.
In the current process for drafts in the IETF stream, "all In the current process for drafts in the IETF stream, "all
approvals" means "publication requested" "in last call" (this is approvals" means "publication requested" "in last call" (this is
IETF last call, not WG last call), and "IESG evaluation"; IETF last call, not WG last call), and "IESG evaluation";
disposition is "approved" (for publication as an RFC), "RFC disposition is "approved" (for publication as an RFC), "RFC
published", and "dead". published", and "dead".
1.2. Discussion of These Requirements 1.2. Discussion of These Requirements
[[ There is no mailing list for this draft at this time; one will This document is being discussed on the datatracker-rqmts@ietf.org
hopefully appear before the next version of this draft. ]] mailing list. See
<https://www.ietf.org/mailman/listinfo/datatracker-rqmts> for more
information.
There will be a BoF at IETF 79 in Beijing to discuss this draft. It There will be a BoF at IETF 79 in Beijing to discuss this draft. It
is currently being called "iddtspec", which somehow stands for is currently being called "iddtspec", which somehow stands for
"Review of Datatracker Specifications to Follow Internet-Draft "Review of Datatracker Specifications to Follow Internet-Draft
Activities". Activities".
There is a plan to have one or two virtual meetings after Beijing to There is a plan to have one or two virtual meetings after Beijing to
discuss these requirements. discuss these requirements.
2. Requirements for Tools Features 2. Requirements for Tools Features
skipping to change at page 12, line 26 skipping to change at page 12, line 26
HTML examples and put them in the document. HTML examples and put them in the document.
o Thought: add a button in the normal Datatracker output to add a o Thought: add a button in the normal Datatracker output to add a
particular draft to a particular list. particular draft to a particular list.
o How prescriptive do we want to be? Should this say things like o How prescriptive do we want to be? Should this say things like
"JavaScript pop-up" and "CSS" and such? "JavaScript pop-up" and "CSS" and such?
o Should paging be supported for long lists in the HTML display? o Should paging be supported for long lists in the HTML display?
Appendix B. Differences between -00 and -01
Added info for the mailing list.
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. 6 change blocks. 
6 lines changed or deleted 13 lines changed or added

This html diff was produced by rfcdiff 1.40. The latest version is available from http://tools.ietf.org/tools/rfcdiff/