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

Bjoern Hoehrmann <derhoermi@gmx.net> Thu, 28 June 2012 00:37 UTC

Return-Path: <derhoermi@gmx.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 80D0D21F85FD for <apps-discuss@ietfa.amsl.com>; Wed, 27 Jun 2012 17:37:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.528
X-Spam-Level:
X-Spam-Status: No, score=-4.528 tagged_above=-999 required=5 tests=[AWL=-1.929, BAYES_00=-2.599]
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 3L4Ueytc7KPY for <apps-discuss@ietfa.amsl.com>; Wed, 27 Jun 2012 17:37:48 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id 2784B21F85F6 for <apps-discuss@ietf.org>; Wed, 27 Jun 2012 17:37:47 -0700 (PDT)
Received: (qmail invoked by alias); 28 Jun 2012 00:37:46 -0000
Received: from dslb-094-223-203-200.pools.arcor-ip.net (EHLO HIVE) [94.223.203.200] by mail.gmx.net (mp002) with SMTP; 28 Jun 2012 02:37:46 +0200
X-Authenticated: #723575
X-Provags-ID: V01U2FsdGVkX195jvRegZJ57omJ61GRUb3bM35J9q33KP3AYg3ZkW bqVNL8xaddlrMl
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: SM <sm@resistor.net>
Date: Thu, 28 Jun 2012 02:37:45 +0200
Message-ID: <5d8nu71haq67135l28h9nbotmm31v1avvb@hive.bjoern.hoehrmann.de>
References: <9452079D1A51524AA5749AD23E00392812B6B6@exch-mbx901.corp.cloudmark.com> <CAKaEYhKpeayOw4sN4=NYaoXKJQ2e5P+pP8SqJqnt-=Barb=WqA@mail.gmail.com> <4FEA6677.3020705@it.aoyama.ac.jp> <6.2.5.6.2.20120626224534.0a8b4298@resistor.net> <4FEB3060.1040805@ninebynine.org> <1340818030.8183.YahooMailNeo@web31806.mail.mud.yahoo.com> <047501cd54ae$c6848a30$538d9e90$@packetizer.com> <6.2.5.6.2.20120627163004.08f6ad50@resistor.net>
In-Reply-To: <6.2.5.6.2.20120627163004.08f6ad50@resistor.net>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-Y-GMX-Trusted: 0
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: Thu, 28 Jun 2012 00:37:52 -0000

* SM wrote:
>At 14:49 27-06-2012, Paul E. Jones wrote:
>>Moving it to a separate document should not be necessary.  We can 
>>publish the WF RFC with the "acct" URI scheme and work to get URI 
>>reviewer approval in parallel.  Is URI reviewer approval required 
>>first?  I don't think so.  Graham suggested that having it agreed in 
>>a standards-track RFC carries a lot of weight.
>
>If the draft is on-track as an IETF RFC, the URI review should not be 
>a problem.  Graham already suggested the easy path.  If you completed 
>the steps to request a URI review, it's not worth worrying about that 
>if the draft is making progress.

I believe for proposals in Standards Track documents, as is the case
here, the process consists of asking for review on the uri-review list
and addressing any feedback there. Anything else, like asking the ex-
pert reviewer whether they approve or coordinating IANA registration,
would be done by the IESG or otherwise happen automatically after the
IESG is asked to consider the document for publication. A request for
review has been posted to the uri-review list, so if there is anything
else Paul has to initiate, could you spell that out?
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/