[dsii] Potential IETF Work Items

Russ Housley <housley@vigilsec.com> Tue, 14 August 2012 14:16 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: dsii@ietfa.amsl.com
Delivered-To: dsii@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5DC5D21F86D8 for <dsii@ietfa.amsl.com>; Tue, 14 Aug 2012 07:16:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yDBPk4Ol6jU8 for <dsii@ietfa.amsl.com>; Tue, 14 Aug 2012 07:16:30 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id 5E72321F86B8 for <dsii@ietf.org>; Tue, 14 Aug 2012 07:16:30 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id EFE7BF24094 for <dsii@ietf.org>; Tue, 14 Aug 2012 10:16:32 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id 9+2n71Fdbfk8 for <dsii@ietf.org>; Tue, 14 Aug 2012 10:16:24 -0400 (EDT)
Received: from [192.168.1.3] (96-37-2-47.dhcp.sffl.va.charter.com [96.37.2.47]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id DA540F24090 for <dsii@ietf.org>; Tue, 14 Aug 2012 10:16:28 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <E1AB8352-7B89-4D5A-9B36-4872DF105392@vigilsec.com>
Date: Tue, 14 Aug 2012 10:16:25 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <7F45CB6F-2FE2-4A25-8A18-C94674489E39@vigilsec.com>
References: <E1AB8352-7B89-4D5A-9B36-4872DF105392@vigilsec.com>
To: dsii@ietf.org
X-Mailer: Apple Mail (2.1084)
Subject: [dsii] Potential IETF Work Items
X-BeenThere: dsii@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <dsii.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dsii>, <mailto:dsii-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dsii>
List-Post: <mailto:dsii@ietf.org>
List-Help: <mailto:dsii-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dsii>, <mailto:dsii-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Aug 2012 14:16:31 -0000

At the DSII BOF in Vancouver, Andy Maffei gave a list of potential work items.  Is there interest in pursuing any of them in the IETF?

Tom my memory, Andy raised this list of potential action items:

* Summarize existing schemes being used for PIDs

* Develop recommendations on a limiting number of PID schemes

* Define an "Interoperability API" for registering dataset identifiers (perhaps based on the EZID API)

* Specify a core set of metadata to be provided by all dataset (probably includes a number of dublin core attributes as well as a digital fingerprint)

* Specify a set of conventions for resolving PIDs associated with datasets.

In addition, there seems to be some overlap with the CDNI WG.  They are also considering some metadata issues; see, for example,  http://datatracker.ietf.org/doc/draft-cjlmw-cdni-metadata.  

Should the IETF specify conventions for paths of PIDs for data objects?  These might include location metadata, access policy, authentication methods, authentication credential, and so on.

Russ