Requirements for Internet-Draft Tracking by the IETF Community in the Datatracker
RFC 6293

Document Type RFC - Informational (June 2011; No errata)
Last updated 2015-10-14
Stream IETF
Formats plain text pdf htmlized bibtex
Reviews
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state RFC 6293 (Informational)
Consensus Boilerplate Unknown
Telechat date
Responsible AD Russ Housley
Send notices to (None)
Internet Engineering Task Force (IETF)                        P. Hoffman
Request for Comments: 6293                                VPN Consortium
Category: Informational                                        June 2011
ISSN: 2070-1721

              Requirements for Internet-Draft Tracking by
                 the IETF Community in the Datatracker

Abstract

   The document gives a set of requirements for extending the IETF
   Datatracker to give individual IETF community members, including the
   IETF leadership, easy methods for tracking the progress of the
   Internet-Drafts and RFCs of interest to them.

Status of This Memo

   This document is not an Internet Standards Track specification; it is
   published for informational purposes.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Not all documents
   approved by the IESG are a candidate for any level of Internet
   Standard; see Section 2 of RFC 5741.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc6293.

Copyright Notice

   Copyright (c) 2011 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Hoffman                       Informational                     [Page 1]
RFC 6293           Datatracker Community Tracking Reqs         June 2011

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
     1.1.  Usage Scenarios  . . . . . . . . . . . . . . . . . . . . .  3
     1.2.  Context for This Document  . . . . . . . . . . . . . . . .  4
     1.3.  Definitions Used in This Document  . . . . . . . . . . . .  5
     1.4.  Expected User Interactions . . . . . . . . . . . . . . . .  6
   2.  Requirements for Tools Features  . . . . . . . . . . . . . . .  6
     2.1.  Lists  . . . . . . . . . . . . . . . . . . . . . . . . . .  6
       2.1.1.  Requirement: Lists of I-Ds and RFCs can be large . . .  6
       2.1.2.  Requirement: Every Datatracker user can create one
               list . . . . . . . . . . . . . . . . . . . . . . . . .  7
       2.1.3.  Requirement: Read-only views of private lists can
               be made visible to others  . . . . . . . . . . . . . .  7
       2.1.4.  Requirement: The Datatracker must support optional
               publicly-readable lists for WGs and Area Directors . .  7
       2.1.5.  Requirement: Specifying the I-Ds and RFCs that are
               in a list must be simple . . . . . . . . . . . . . . .  8
       2.1.6.  Requirement: Adding groups of I-Ds to a list by
               attribute must be simple . . . . . . . . . . . . . . .  8
       2.1.7.  Requirement: Private information must not be
               exposed in lists . . . . . . . . . . . . . . . . . . .  9
     2.2.  Notifications  . . . . . . . . . . . . . . . . . . . . . .  9
       2.2.1.  Requirement: Users can be notified when an I-D
               changes status . . . . . . . . . . . . . . . . . . . .  9
       2.2.2.  Requirement: Every list has Atom feeds associated
               with it  . . . . . . . . . . . . . . . . . . . . . . .  9
       2.2.3.  Requirement: Every list has mail streams
               associated with it . . . . . . . . . . . . . . . . . . 10
       2.2.4.  Requirement: Notifications need to specify which
               list caused the notification . . . . . . . . . . . . . 10
     2.3.  Display in the Datatracker . . . . . . . . . . . . . . . . 10
       2.3.1.  Requirement: Users can define their Datatracker
               document view  . . . . . . . . . . . . . . . . . . . . 10
       2.3.2.  Requirement: Users can choose which attributes to
               display  . . . . . . . . . . . . . . . . . . . . . . . 11
       2.3.3.  Requirement: Users can flag I-Ds with dates in the
               future . . . . . . . . . . . . . . . . . . . . . . . . 12
       2.3.4.  Requirement: Users can specify highlighting of
               I-Ds and RFCs with recent changes  . . . . . . . . . . 12
     2.4.  File Output  . . . . . . . . . . . . . . . . . . . . . . . 12
       2.4.1.  Requirement: Users can get their current list as a
               single file  . . . . . . . . . . . . . . . . . . . . . 12
Show full document text