IETF Logo Mail Archive

Re: [apps-discuss] open issues with acct-uri spec

"Martin J. Dürst" <duerst@it.aoyama.ac.jp> Mon, 19 November 2012 09:34 UTC

Return-Path: <duerst@it.aoyama.ac.jp>
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 8B3F421F8549 for <apps-discuss@ietfa.amsl.com>; Mon, 19 Nov 2012 01:34:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.627
X-Spam-Level:
X-Spam-Status: No, score=-100.627 tagged_above=-999 required=5 tests=[AWL=-0.837, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
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 WP3+CyzNJe8z for <apps-discuss@ietfa.amsl.com>; Mon, 19 Nov 2012 01:34:59 -0800 (PST)
Received: from scintmta01.scbb.aoyama.ac.jp (scintmta01.scbb.aoyama.ac.jp [133.2.253.33]) by ietfa.amsl.com (Postfix) with ESMTP id F10B421F853C for <apps-discuss@ietf.org>; Mon, 19 Nov 2012 01:34:58 -0800 (PST)
Received: from scmse02.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta01.scbb.aoyama.ac.jp (secret/secret) with SMTP id qAJ9YqpS010015 for <apps-discuss@ietf.org>; Mon, 19 Nov 2012 18:34:52 +0900
Received: from (unknown [133.2.206.133]) by scmse02.scbb.aoyama.ac.jp with smtp id 55b6_d854_5eaa6e32_322c_11e2_b6ab_001d096c5782; Mon, 19 Nov 2012 18:34:51 +0900
Received: from [IPv6:::1] ([133.2.210.1]:36497) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S16160C0> for <apps-discuss@ietf.org> from <duerst@it.aoyama.ac.jp>; Mon, 19 Nov 2012 18:34:53 +0900
Message-ID: <50A9FD3B.7090908@it.aoyama.ac.jp>
Date: Mon, 19 Nov 2012 18:34:51 +0900
From: "\"Martin J. Dürst\"" <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: "apps-discuss@ietf.org" <apps-discuss@ietf.org>
References: <F4434DAC-80F4-41AE-9B09-C2DAE5BB887B@ve7jtb.com> <A723FC6ECC552A4D8C8249D9E07425A70F6714AB@xmb-rcd-x10.cisco.com> <C68CB012D9182D408CED7B884F441D4D1E37027548@nambxv01a.corp.adobe.com> <50A9F543.2040405@it.aoyama.ac.jp>
In-Reply-To: <50A9F543.2040405@it.aoyama.ac.jp>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Subject: Re: [apps-discuss] open issues with acct-uri spec
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: Mon, 19 Nov 2012 09:34:59 -0000

On 2012/11/19 18:00, "Martin J. Dürst" wrote:
> Hello Larry,
>
> On 2012/11/19 17:53, Larry Masinter wrote:

>> Now, if apps-discuss is willing to put so much energy into a single
>> URI scheme definition, perhaps some energy could be put into updating
>> the guidelines.
>>
>> Maybe someone who hasn't been working on this topic for 20 years could
>> find more energy to work on an update?
>
> Is the XML at
> http://tools.ietf.org/id/draft-ietf-iri-4395bis-irireg-04.xml
> up to date, or is there a more up-to-date internal version?
> If not, can one of the authors who is in possession of the newest
> version commit it to the IRI WG svg repo or some other suitable location
> and announce where it's avaliable?
>
> I have added a new issues for this in the IRI WG tracker.

I had to wait for Larry's mail to show up in the archives to create the 
issue. It's now at http://trac.tools.ietf.org/wg/iri/trac/ticket/137.

Regards,   Martin.

v2.23.0 | Report a Bug | By Email