Re: [dsii] Potential IETF Work Items

Guangqing Deng <dgq2011@gmail.com> Wed, 22 August 2012 07:54 UTC

Return-Path: <dgq2011@gmail.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 E6EC621F8680 for <dsii@ietfa.amsl.com>; Wed, 22 Aug 2012 00:54:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level:
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[AWL=0.654, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, SARE_HTML_USL_OBFU=1.666]
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 fZahv7EWYfDf for <dsii@ietfa.amsl.com>; Wed, 22 Aug 2012 00:54:47 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id BED5021F867A for <dsii@ietf.org>; Wed, 22 Aug 2012 00:54:47 -0700 (PDT)
Received: by yenm5 with SMTP id m5so504067yen.31 for <dsii@ietf.org>; Wed, 22 Aug 2012 00:54:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=yS4DRvlpdX/pVWII08VtOz9cXdCXVXUv8f7LqP0VeMU=; b=terQO3MlfnFHwq9efQ0/G7s+bZsSwbGVJG9ikh5HfS/9zzntpxIzR0Oo8tBWS6vSgx O3H672eBQUOxaeDPTBQroBxQ35nGrklmG/iQcm43p32UehMBpZlxsb+HWP4E2iTsXZCT IVVv4W/kqYb/QMHTmBwmAwf6ScNalKvzERickpzWQCsNTWGGU03UicL+XhDN+/zW9i7z /e3WyyusIyr6CRcjkwkmjdFN8isEsR8NgajSOgWXhbMDo7+o3thGZQwp0KsZdGBHhciA oqHJNWFefIsFPstd4SliWlu1SyNFkoBaI6OLSPvIaPm8glZkFm7mi/Tzf7LqQRqITWX5 FDKw==
MIME-Version: 1.0
Received: by 10.50.6.225 with SMTP id e1mr1229066iga.31.1345622086578; Wed, 22 Aug 2012 00:54:46 -0700 (PDT)
Received: by 10.64.52.68 with HTTP; Wed, 22 Aug 2012 00:54:46 -0700 (PDT)
In-Reply-To: <503290C2.7060608@nomountain.net>
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> <503290C2.7060608@nomountain.net>
Date: Wed, 22 Aug 2012 15:54:46 +0800
Message-ID: <CAL4OH3QkyDnPK8qxBMP-6C7C7b7pbzQh_YHSPvTsDm5RVCn6ig@mail.gmail.com>
From: Guangqing Deng <dgq2011@gmail.com>
To: dsii@ietf.org
Content-Type: multipart/alternative; boundary=e89a8f64662b78f31604c7d60e4d
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: Wed, 22 Aug 2012 07:54:52 -0000

When I see "Data Set Identifier" at the first time, what comes into my mind
is the identifier of objects in cloud storage system where all kinds of
data are stored with high availability and flexibility. Objects stored in a
cloud storage system also need identifying and interoperating, just as
those data objects stored in other data infrastructures, such as EUDAT. I
have read PPT files discussed in the IETF 84 BOF on DSII and find that no
file relates to cloud storage explicitly. Is it because the cloud storage
is too commercialized? Somehow it seems that cloud computing is not welcome
in IETF though it is very popular in industry.

2012/8/21 Melinda Shore <melinda.shore@nomountain.net>;

> 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."
>
>
> ______________________________**_________________
> dsii mailing list
> dsii@ietf.org
> https://www.ietf.org/mailman/**listinfo/dsii<https://www.ietf.org/mailman/listinfo/dsii>
>



-- 
Guangqing Deng