Re: Last Call: <draft-ietf-genarea-datatracker-community-06.txt> (Requirements for Internet-Draft Tracking by the IETF Community in the Datatracker) to Informational RFC
Paul Hoffman <paul.hoffman@vpnc.org> Tue, 15 March 2011 16:00 UTC
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DB90F3A6D76 for <ietf@core3.amsl.com>; Tue, 15 Mar 2011 09:00:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.598
X-Spam-Level:
X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, URIBL_RED=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F8OFQld2Ziyf for <ietf@core3.amsl.com>; Tue, 15 Mar 2011 09:00:52 -0700 (PDT)
Received: from hoffman.proper.com (unknown [IPv6:2001:4870:a30c:41::81]) by core3.amsl.com (Postfix) with ESMTP id 63F8F3A6D66 for <ietf@ietf.org>; Tue, 15 Mar 2011 09:00:52 -0700 (PDT)
Received: from MacBook-08.local (69-170-62-67.static-ip.telepacific.net [69.170.62.67]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p2FG2FlH050461 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 15 Mar 2011 09:02:16 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Message-ID: <4D7F8D87.6070801@vpnc.org>
Date: Tue, 15 Mar 2011 09:02:15 -0700
From: Paul Hoffman <paul.hoffman@vpnc.org>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: datatracker-reqmts@ietf.org
Subject: Re: Last Call: <draft-ietf-genarea-datatracker-community-06.txt> (Requirements for Internet-Draft Tracking by the IETF Community in the Datatracker) to Informational RFC
References: <20110304224654.24845.31877.idtracker@localhost> <54309CC0-259E-4766-817F-35E2D11F150B@nostrum.com>
In-Reply-To: <54309CC0-259E-4766-817F-35E2D11F150B@nostrum.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Mar 2011 16:00:54 -0000
On 3/14/11 2:26 PM, Robert Sparks wrote: > Paul - > > 1) If we publish this as an RFC, note that imgur.com will only keep > an image if it's viewed at least once every three months. Good catch. I have added a note in the upcoming -08 that the sentence removed before publication. FWIW, I do not know whether or not there is an intention to publish this document as an RFC. > 2) In the list of things constituting an "update to an RFC", could > you call out marking an RFC as Historic, and changing the maturity > level of an RFC in place (such as was done for 5652) Sure. Done in -07. > 3) 2.1.2 talks of the ease of use to create a datatracker account. I > think we have that already through the tools system. Are you thinking > this will require the creation of a different system? Getting a Datatracker account is different than getting a Tools account. Currently, going to <https://datatracker.ietf.org/> does not show you how to get a Datatracker account. Even if you try the meme of "try to log in and see what happens if you fail", you do not get presented with a "here's how to get a Datatracker account" message. If we expect these tools to be widely-used, we need to be sure that it is easier than it is today to get a Datatracker account. On 3/14/11 2:46 PM, Robert Sparks wrote: > How much would the list of attributes in 2.1.6 need to be expanded > to make one of these user-defined lists > enough to satisfy the initial "Reporting Requirements" in section > 4.3 of draft-ietf-genarea-datatracker-iana-rfced-extns-00? > Should we add the ability to match against the values (or absence of > value) of a state for the various state machines tracked by the > tracker? Given that the document is completely new and has had thin review so far, we might be better off waiting for it to progress and doing a revision to the tool than waiting to know what the actual states are. Note that the wording in that section is quite indefinite: "For example, the initial set of discrepancies could include...". It would be easy to add more attributes to the ones in 2.1.6 later. --Paul Hoffman
- Fwd: Last Call: <draft-ietf-genarea-datatracker-c… Paul Hoffman
- Re: Last Call: <draft-ietf-genarea-datatracker-co… Robert Sparks
- Re: Last Call: <draft-ietf-genarea-datatracker-co… Robert Sparks
- Re: Last Call: <draft-ietf-genarea-datatracker-co… Paul Hoffman