Re: [dsii] Potential IETF Work Items

Melinda Shore <melinda.shore@nomountain.net> Mon, 20 August 2012 19:32 UTC

Return-Path: <melinda.shore@nomountain.net>
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 0A99721F8606 for <dsii@ietfa.amsl.com>; Mon, 20 Aug 2012 12:32:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ezsVTprbyvGw for <dsii@ietfa.amsl.com>; Mon, 20 Aug 2012 12:32:21 -0700 (PDT)
Received: from homiemail-a90.g.dreamhost.com (caiajhbdcahe.dreamhost.com [208.97.132.74]) by ietfa.amsl.com (Postfix) with ESMTP id 54A2921F8532 for <dsii@ietf.org>; Mon, 20 Aug 2012 12:32:21 -0700 (PDT)
Received: from homiemail-a90.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a90.g.dreamhost.com (Postfix) with ESMTP id E87832AC06E for <dsii@ietf.org>; Mon, 20 Aug 2012 12:32:20 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=nomountain.net; h=message-id:date :from:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=nomountain.net ; b=MudMpKEDuIEeHBBf4F3yJk/H+TzToxZIs11bddez0cmvQwDomxb0V97r15xU hVT4vSADAIvapuJjwgAUhIKtiYAi+1AIZUHi1y1fYEe+FoxSd8HRSq9+9ptz7BIV bgAbUR76pWrTqpRsESVcR+jhxfX1z+yKvxc0ZenxH6ZCmQY=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=nomountain.net; h= message-id:date:from:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; s= nomountain.net; bh=J3EDI30+4n8o6CKMT7NY2cUX7ug=; b=tQaQopBkxBzhb j726hEQ0/qOw4bUfWWNAZVQKthIZW5utfUbw3RPNVbsFzZ8RCjAAbHcPQ7/NbD+b GFs71c9J1W+8jviDjcTsCxjPB7bmDfwtKNNEKGTAfCTJZYZYp/Iv/fm9abNiXpVk WOrtzj0VYaQ3BQSwoJqXyWx2yXK0OM=
Received: from spandex.local (66-230-81-200-rb1.fai.dsl.dynamic.acsalaska.net [66.230.81.200]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: melinda.shore@nomountain.net) by homiemail-a90.g.dreamhost.com (Postfix) with ESMTPSA id 98E7F2AC059 for <dsii@ietf.org>; Mon, 20 Aug 2012 12:32:20 -0700 (PDT)
Message-ID: <503290C2.7060608@nomountain.net>
Date: Mon, 20 Aug 2012 11:32:18 -0800
From: Melinda Shore <melinda.shore@nomountain.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: dsii@ietf.org
References: <E1AB8352-7B89-4D5A-9B36-4872DF105392@vigilsec.com> <7F45CB6F-2FE2-4A25-8A18-C94674489E39@vigilsec.com> <CAPv4CP-SOmFAKqdm+3Xa9oBwNxd_f4dGyAQu7aesaEbc_quLgQ@mail.gmail.com> <CA+9kkMBpwaxHUMXegcQ6j1pPqgmb4k=130BaoDVp6HQ_Kh1Syw@mail.gmail.com> <502BC103.4040107@nomountain.net> <CA+9kkMCDF7LeeJw+G9-DHhxTsz3wC_8SWbPRjyzSDgaTzyA77g@mail.gmail.com>
In-Reply-To: <CA+9kkMCDF7LeeJw+G9-DHhxTsz3wC_8SWbPRjyzSDgaTzyA77g@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [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: Mon, 20 Aug 2012 19:32:22 -0000

I'm still trying to figure out what's being proposed here and I
realized that my mental model might be considerably different from
that being used by the work's proponents.  Where I'm coming from,
someone who needs a chunk of data and isn't sure where it is (or,
in some cases, whether or not it exists) does a search, and the
search returns a set of stuff, where "stuff" includes descriptive
information (metadata) and an identifier that's actually a
locator.  The locator is used to access the data.

Is that consistent with what proponents have in mind?

Melinda

-- 
Melinda Shore
No Mountain Software
melinda.shore@nomountain.com

"Software longa, hardware brevis."