IETF Logo Mail Archive

Re: [lemonade] Fwd: New Version Notification for draft-ncook-urlauth-accessid-00

Arnt Gulbrandsen <arnt@oryx.com> Mon, 19 January 2009 15:29 UTC

Return-Path: <lemonade-bounces@ietf.org>
X-Original-To: lemonade-archive@optimus.ietf.org
Delivered-To: ietfarch-lemonade-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B1BC03A6AEE; Mon, 19 Jan 2009 07:29:25 -0800 (PST)
X-Original-To: lemonade@core3.amsl.com
Delivered-To: lemonade@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B303E3A6A1D for <lemonade@core3.amsl.com>; Mon, 19 Jan 2009 07:29:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.548
X-Spam-Level:
X-Spam-Status: No, score=-2.548 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IFJ663NEkB2m for <lemonade@core3.amsl.com>; Mon, 19 Jan 2009 07:29:21 -0800 (PST)
Received: from kalyani.oryx.com (kalyani.oryx.com [195.30.37.30]) by core3.amsl.com (Postfix) with ESMTP id 36D4728C0EE for <lemonade@ietf.org>; Mon, 19 Jan 2009 07:29:21 -0800 (PST)
Received: from kalyani.oryx.com (localhost.oryx.com [127.0.0.1]) by kalyani.oryx.com (Postfix) with ESMTP id 4B8BF4AC5B; Mon, 19 Jan 2009 16:29:04 +0100 (CET)
Received: from arnt@oryx.com (HELO lochnagar.oryx.com) by kalyani.oryx.com (Archiveopteryx 3.1.0) with esmtp id 1232378943-52018-1/6/8 (3 recipients); Mon, 19 Jan 2009 16:29:03 +0100
Message-Id: <CDvPaISRoQuTCh1vO9GHIA.md5@lochnagar.oryx.com>
Date: Mon, 19 Jan 2009 16:29:25 +0100
From: Arnt Gulbrandsen <arnt@oryx.com>
To: lemonade@ietf.org
References: <20081208183940.4146B28C105@core3.amsl.com> <4E6BFEFF-3176-4DF0-BE6C-D6EE79AA0A7A@noware.co.uk> <569D3359-9BC3-48D8-8784-1EFBB9E13D15@standardstrack.com> <oEeBHinV0M8tXx9xKtGOag.md5@lochnagar.oryx.com> <07222EA7-EF69-4C65-9503-0F46C4F51D77@noware.co.uk>
In-Reply-To: <07222EA7-EF69-4C65-9503-0F46C4F51D77@noware.co.uk>
Mime-Version: 1.0
Subject: Re: [lemonade] Fwd: New Version Notification for draft-ncook-urlauth-accessid-00
X-BeenThere: lemonade@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Enhancements to Internet email to support diverse service enivronments <lemonade.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/lemonade>, <mailto:lemonade-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/lemonade>
List-Post: <mailto:lemonade@ietf.org>
List-Help: <mailto:lemonade-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lemonade>, <mailto:lemonade-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: lemonade-bounces@ietf.org
Errors-To: lemonade-bounces@ietf.org

Neil Cook writes:
> well I'm updating the doc at the moment, and I'm going to be including 
>  IANA definitions for the existing access identifiers anyway (as when 
>  establishing a new registry, you need all the existing definitions 
> to  be defined), so I think for clarity it might help to have the  
> requirements/definitions as well - this doc will formally update the  
> IMAPURL RFC.

In that case, maybe you ought to say something like "these rules are 
meant to be a straightforward extension of the ones in the IMAPURL RFC, 
but if there's anydifference, these rules apply, not the older ones 
from IMAPURL"

Arnt
_______________________________________________
lemonade mailing list
lemonade@ietf.org
https://www.ietf.org/mailman/listinfo/lemonade
Supplemental Web Site:
http://www.standardstrack.com/ietf/lemonade

v2.23.0 | Report a Bug | By Email