Re: [apps-discuss] proposing draft-farrell-ni as an appsarea wg item

Mykyta Yevstifeyev <evnikita2@gmail.com> Thu, 28 July 2011 05:13 UTC

Return-Path: <evnikita2@gmail.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F84421F8C0E for <apps-discuss@ietfa.amsl.com>; Wed, 27 Jul 2011 22:13:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.284
X-Spam-Level:
X-Spam-Status: No, score=-2.284 tagged_above=-999 required=5 tests=[AWL=-1.135, BAYES_00=-2.599, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_LOW=-1]
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 Pbgh+0rvwhip for <apps-discuss@ietfa.amsl.com>; Wed, 27 Jul 2011 22:13:38 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by ietfa.amsl.com (Postfix) with ESMTP id 88C7121F8C0C for <apps-discuss@ietf.org>; Wed, 27 Jul 2011 22:13:38 -0700 (PDT)
Received: by fxe6 with SMTP id 6so976644fxe.31 for <apps-discuss@ietf.org>; Wed, 27 Jul 2011 22:13:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=PoBwSVIq1wUWADEGc/G0cS0K1o8Bbm4f3jd8mbtNxGs=; b=l7W6BsCoRLdayLV4jIpj+7+aAKwLCJRMEN4OV9bC8FwweVmzHpFDFssKx1avjiPmYP Pac5NR9aLuZfPInG8HMrBZtklVb+GUVXEZO+XanuqfHHnI1DyDKKDzABSc+Qo+yYQN5z Rf9lE1wwZ02zfBphMRt4Af0Lop/FcFiqy/hQM=
Received: by 10.223.17.151 with SMTP id s23mr771969faa.13.1311830017561; Wed, 27 Jul 2011 22:13:37 -0700 (PDT)
Received: from [127.0.0.1] ([195.191.104.224]) by mx.google.com with ESMTPS id q5sm242525fah.30.2011.07.27.22.13.35 (version=SSLv3 cipher=OTHER); Wed, 27 Jul 2011 22:13:36 -0700 (PDT)
Message-ID: <4E30F028.2080408@gmail.com>
Date: Thu, 28 Jul 2011 08:14:16 +0300
From: Mykyta Yevstifeyev <evnikita2@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: apps-discuss@ietf.org
References: <CA56328E.2FE%tianlinyi@huawei.com>
In-Reply-To: <CA56328E.2FE%tianlinyi@huawei.com>
Content-Type: text/plain; charset="GB2312"
Content-Transfer-Encoding: 8bit
Subject: Re: [apps-discuss] proposing draft-farrell-ni as an appsarea wg item
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jul 2011 05:13:39 -0000

28.07.2011 4:25, Linyi Tian 01 wrote:
>
> On 11-7-27 上午11:49, "Stephen Farrell" <stephen.farrell@cs.tcd.ie> wrote:
>
>> Hi,
>>
>> Yesterday, I presented a draft [1] on a URI scheme for naming
>> stuff to the decade WG. There's interest in that there but
>> the idea behind this is really broader than just decade so
>> if there's interest here, doing this work in the appsarea WG
>> would I think be much better.
>>
>> The scheme is basically like HTTP URIs with one additional
>> thing, which is that it specifies a way to include a hash
>> function output in the name (and the related input, in case
>> you want to verify something later) which seems to me to be
>> a generally useful thing that various protocols could use
>> in various ways. Hence the idea of bringing it here.
> I am wondering how this would be used. Will it be used together with HTTP
> URIs? Is there any real life use case how I can use this URI.
+1. I think APPSAWG shouldn't accept this as WG item; I wouldn't also
recommend it for publication of it as AD-sponsored Individual submission
or in any other way as RFC.

There is no clear explanation of operations for new URI scheme. What
should the application do when resolving the 'ni' URI? What protocol
should be used? Also, <authority> includes <userinfo> and <port>, which
I don't how to be applied to 'ni' URI operations. I think that 'tag'
URIs, which only identify the resource (RFC 4151), are suitable for the
purposes of proposed 'ni' URI scheme.

Mykyta Yevstifeyev
>
>> So, comments appreciated,
>>
>> Thanks,
>> Stephen.
>>
>> [1] http://tools.ietf.org/html/draft-farrell-ni
>>
>> _______________________________________________
>> apps-discuss mailing list
>> apps-discuss@ietf.org
>> https://www.ietf.org/mailman/listinfo/apps-discuss
>
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss