IETF Logo Mail Archive

Re: [apps-discuss] The acct: scheme question

SM <sm@resistor.net> Wed, 27 June 2012 06:23 UTC

Return-Path: <sm@resistor.net>
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 557DB11E8102 for <apps-discuss@ietfa.amsl.com>; Tue, 26 Jun 2012 23:23:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.42
X-Spam-Level:
X-Spam-Status: No, score=-102.42 tagged_above=-999 required=5 tests=[AWL=-0.121, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, 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 pH6hb-0reI5o for <apps-discuss@ietfa.amsl.com>; Tue, 26 Jun 2012 23:23:11 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 292B211E80C5 for <apps-discuss@ietf.org>; Tue, 26 Jun 2012 23:23:11 -0700 (PDT)
Received: from SUBMAN.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q5R6N0W4006846; Tue, 26 Jun 2012 23:23:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1340778188; bh=RIA0UnScuEKAPhcF3OSX3ZDLyNOfVvIFnb0tBTcqBD4=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=vThzU2Qg7jbGexLQYj2/vHm3ZAsJDxNkt7kA2mTWfjfPM05uBfwRvIE+Ezc1D/G3w 4CmqSupUtSvqtteXmzThQtUDHcfW0u0RY/3gqSDuz823ptiFGQ7dDjtLLvVjM9nDHs aRkaAXQ6BOMyv6VS3waZnjfTcKhlVCQlrx4IjWV0=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1340778188; i=@resistor.net; bh=RIA0UnScuEKAPhcF3OSX3ZDLyNOfVvIFnb0tBTcqBD4=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=BYelDQFwguQWqePUxYkF0OhWIrW44mCqrHGU8Ahkg22xmpVwtLys2oswKAIxklRol ba56D/uQRVxw4eNP8cOWtwj2TWMTEDhSiULFP0Loz8vzE8m3lwPniY++q2w9SjYboJ P1TQA65s6zwYRS6OpmEGkdlCZSBo+iNKL57843HU=
Message-Id: <6.2.5.6.2.20120626224534.0a8b4298@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 26 Jun 2012 23:06:54 -0700
To: "\"Martin J. Dürst\"" <duerst@it.aoyama.ac.jp>
From: SM <sm@resistor.net>
In-Reply-To: <4FEA6677.3020705@it.aoyama.ac.jp>
References: <9452079D1A51524AA5749AD23E00392812B6B6@exch-mbx901.corp.cloudmark.com> <CAKaEYhKpeayOw4sN4=NYaoXKJQ2e5P+pP8SqJqnt-=Barb=WqA@mail.gmail.com> <4FEA6677.3020705@it.aoyama.ac.jp>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format="flowed"
Content-Transfer-Encoding: quoted-printable
Cc: apps-discuss@ietf.org
Subject: Re: [apps-discuss] The acct: scheme question
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: Wed, 27 Jun 2012 06:23:13 -0000

Hi Martin,
At 18:48 26-06-2012, Martin J. Dürst wrote:
>Warning: procedural nitpicking ahead!
>
>I think we should be careful about this. 
>uri-review@ietf.org is for review of URI/IRI 
>schemes in general. This has a rather low 
>barrier. The fact that it gets approved there 
>doesn't mean that it will pass through the IETF 
>standardization process. On the other hand, if 
>the IETF standardizes it, it has the possibility 
>of overriding the decision on uri-review@ietf.org if that should be necessary.
>I'm just mentioning this here because we have 
>been through this for another URI scheme.

I don't like the idea of mixing registration 
criteria and the standardization process.  The 
authors of the other URI scheme were nice not to 
turn such a matter into an issue.  This is the 
sort of issue which generate controversies.  It 
will be detrimental to the IETF as people will walk away.

Regards,
-sm

v2.23.0 | Report a Bug | By Email