[datatracker-rqmts] Fwd: draft-ietf-genarea-datatracker-iana-rfced-extns requirements questions

Robert Sparks <rjsparks@nostrum.com> Tue, 15 March 2011 01:54 UTC

Return-Path: <rjsparks@nostrum.com>
X-Original-To: datatracker-rqmts@core3.amsl.com
Delivered-To: datatracker-rqmts@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 74C213A68AB for <datatracker-rqmts@core3.amsl.com>; Mon, 14 Mar 2011 18:54:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.596
X-Spam-Level:
X-Spam-Status: No, score=-102.596 tagged_above=-999 required=5 tests=[AWL=0.003, BAYES_00=-2.599, HTML_MESSAGE=0.001, SPF_PASS=-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 HuAcucKvlMTv for <datatracker-rqmts@core3.amsl.com>; Mon, 14 Mar 2011 18:54:19 -0700 (PDT)
Received: from nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by core3.amsl.com (Postfix) with ESMTP id 890423A6973 for <datatracker-rqmts@ietf.org>; Mon, 14 Mar 2011 18:54:18 -0700 (PDT)
Received: from [192.168.2.105] (pool-173-57-91-217.dllstx.fios.verizon.net [173.57.91.217]) (authenticated bits=0) by nostrum.com (8.14.3/8.14.3) with ESMTP id p2F1tfxv072867 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <datatracker-rqmts@ietf.org>; Mon, 14 Mar 2011 20:55:41 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
From: Robert Sparks <rjsparks@nostrum.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-6--275605998
Date: Mon, 14 Mar 2011 20:55:41 -0500
References: <95C23749-47F2-440B-87B5-ABC365B4B3E2@nostrum.com>
To: datatracker-rqmts@ietf.org
Message-Id: <FECC9330-7557-4B58-88D7-DB692BBB405A@nostrum.com>
Mime-Version: 1.0 (Apple Message framework v1082)
X-Mailer: Apple Mail (2.1082)
Received-SPF: pass (nostrum.com: 173.57.91.217 is authenticated by a trusted mechanism)
Subject: [datatracker-rqmts] Fwd: draft-ietf-genarea-datatracker-iana-rfced-extns requirements questions
X-BeenThere: datatracker-rqmts@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <datatracker-rqmts.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/datatracker-rqmts>, <mailto:datatracker-rqmts-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/datatracker-rqmts>
List-Post: <mailto:datatracker-rqmts@ietf.org>
List-Help: <mailto:datatracker-rqmts-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/datatracker-rqmts>, <mailto:datatracker-rqmts-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Mar 2011 01:54:20 -0000

and of course my mail program remembered the typo in the list name for me :(...
Resending to get this to the list as well.

RjS

Begin forwarded message:

> From: Robert Sparks <rjsparks@nostrum.com>;
> Date: March 14, 2011 4:56:49 PM CDT
> To: draft-ietf-genarea-datatracker-iana-rfced-extns@tools.ietf.org, datatracker-reqmts@ietf.org
> Subject: draft-ietf-genarea-datatracker-iana-rfced-extns requirements questions
> 
> Hi Sandy, Michelle, and Alexa -
> 
> As the datatracker-iana-rfced document is refined, I think it would help to be
> more explicit about what you want to be machine-machine automated between
> the datatracker and the IANA and RFC Editor systems, and what you expect to
> remain as manual entry.
> 
> Every bit of information in the tracker that is a copy of information that is authoritatively
> kept somewhere else is a presents an opportunity for error, and a need for automated
> consistency checking and (often manual) reconciliation. Would it be feasible to build
> an interface across the systems that would let the tracker ask for the authoritative information
> when it needed it to respond to a request, rather than rely on a having a duplicate of that information
> entered into the tracker's databases? (We could, of course, look at caching the results of such
> a query).
> 
> As I asked Paul in response to the LC of the genart-datatracker-community document, how
> much of the discrepancy seeking reporting do you think you could achieve with the dynamic
> list feature being required there (if the ability to compare against state values were added)?
> 
> RjS