IETF Logo Mail Archive

Re: [EAI] Shepherd report review of mailinglist-02

Alexey Melnikov <alexey.melnikov@isode.com> Fri, 13 July 2012 15:08 UTC

Return-Path: <alexey.melnikov@isode.com>
X-Original-To: ima@ietfa.amsl.com
Delivered-To: ima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 60DC721F8522 for <ima@ietfa.amsl.com>; Fri, 13 Jul 2012 08:08:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.923
X-Spam-Level:
X-Spam-Status: No, score=-102.923 tagged_above=-999 required=5 tests=[AWL=-0.324, BAYES_00=-2.599, 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 SrXh6TzlB7LY for <ima@ietfa.amsl.com>; Fri, 13 Jul 2012 08:08:27 -0700 (PDT)
Received: from waldorf.isode.com (cl-125.lon-03.gb.sixxs.net [IPv6:2a00:14f0:e000:7c::2]) by ietfa.amsl.com (Postfix) with ESMTP id 6010221F851E for <ima@ietf.org>; Fri, 13 Jul 2012 08:08:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1342192167; d=isode.com; s=selector; i=@isode.com; bh=QoToThlKcx/ORve11puNK/rcOj9mEg2zO74VofIiBIU=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=UIoIXMjIrZSOkIPLJTVyGdtzLq9fpyesyaBnrGRZ5C0QWjQ1i2FwqfMQhNsYE+WGe17vo2 balAROZuvIk1mqXH2MkQRVBWAgCXaEUuNhwziECYgkwyesIalel8XIMdFyhzPgd9xVz3bn XzyWBRZBrS72Y0nQjO0jDxAzoX776Bs=;
Received: from [172.16.1.29] (shiny.isode.com [62.3.217.250]) by waldorf.isode.com (submission channel) via TCP with ESMTPSA id <UAA6JgAkRH=G@waldorf.isode.com>; Fri, 13 Jul 2012 16:09:26 +0100
X-SMTP-Protocol-Errors: PIPELINING
Message-ID: <50003A2A.5080005@isode.com>
Date: Fri, 13 Jul 2012 16:09:30 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
To: John R Levine <johnl@taugh.com>
References: <CAF1dMVE+2_288HmqaFfqANyB1r+KzBYXQ37i0_Gm_x1w1COqVw@mail.gmail.com> <alpine.BSF.2.00.1207121737350.66870@joyce.lan> <5000022C.5020207@isode.com> <alpine.BSF.2.00.1207130936460.95156@joyce.lan>
In-Reply-To: <alpine.BSF.2.00.1207130936460.95156@joyce.lan>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: EAI WG <ima@ietf.org>
Subject: Re: [EAI] Shepherd report review of mailinglist-02
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ima>, <mailto:ima-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ima>
List-Post: <mailto:ima@ietf.org>
List-Help: <mailto:ima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Jul 2012 15:08:28 -0000

On 13/07/2012 14:39, John R Levine wrote:
>> I think you need Informative references for mailto:, http: and ftp: 
>> URI schemes. I am not sure why you removed the mailto: reference from 
>> the document.
>
> The various URIs only come up in the context of list headers, and 
> there's refefrence to RFC 2369 which defines them and does refer to 
> the sources of the various schemes.  If you really think we need to 
> tell people where to find mailto: and http: I can add refererences, 
> but since the only discussion is with respect to % signs in the 
> syntax, not to what they do, I don't see the need.

I believe the rule is that anything mentioned in the document that is 
not defined in it needs to be referenced.

v2.29.0 | Report a Bug | By Email | System Status