Re: Comments on draft-eastlake-additional-xmlsec-uris-07.txt

SM <sm@resistor.net> Fri, 08 February 2013 01:44 UTC

Return-Path: <sm@resistor.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 751181F0D09 for <ietf@ietfa.amsl.com>; Thu, 7 Feb 2013 17:44:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.565
X-Spam-Level:
X-Spam-Status: No, score=-102.565 tagged_above=-999 required=5 tests=[AWL=0.034, BAYES_00=-2.599, 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 G+eAMEt6sfEY for <ietf@ietfa.amsl.com>; Thu, 7 Feb 2013 17:44:13 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 400501F0CFF for <ietf@ietf.org>; Thu, 7 Feb 2013 17:44:12 -0800 (PST)
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 r181huQv020049; Thu, 7 Feb 2013 17:43:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1360287844; bh=lYHPbPiGZNanWoRe7usiZpvFvjJ+bt0m7tOVBUX7eZ8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=k2m1qyUTtY8GYFMv+wHXNLfR9Em+1YEDSYR+9/jfovO2AhHEuw1TpG4YqyPLWPI1E TRiZSxirHGt336ifPONV2I9qhhmTHbTFsAwhG13fsV/gnfktZqCPu1Ncjpci99XAjN nS4Y2yveaCUFtB+QgbF7+INUO8OcZjd09uuvhxAs=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1360287844; i=@resistor.net; bh=lYHPbPiGZNanWoRe7usiZpvFvjJ+bt0m7tOVBUX7eZ8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=HPxA74tJhHtW28yr86cdeQjFqReDbQ29fpAQPRCtg7808pyvqL5xsuOlTPY4zO8fd QRs7SSnWR7rq5dJdzopK7JkgfrPJ0AoSOLwJqtFx3ZOGiVWrV7l9gjmy2W9EXWjymP 6q5OaQDbSKJlAKj9zMxnSvIOcLk+ACtjLjNeDhFk=
Message-Id: <6.2.5.6.2.20130207173122.09a265f8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 07 Feb 2013 17:41:48 -0800
To: Donald Eastlake <d3e3e3@gmail.com>
From: SM <sm@resistor.net>
Subject: Re: Comments on draft-eastlake-additional-xmlsec-uris-07.txt
In-Reply-To: <CAF4+nEFpZChc8sRE=uEEd4zYMd0jzZqn7rJ7sBSxR6OtosGGSQ@mail.g mail.com>
References: <iae4h8939k1cccckiqhj6cve2k3pf2tvlk@hive.bjoern.hoehrmann.de> <CAF4+nEEOQ=t76VncAT4a7HeX1d=tZDJeoph=3TFKAvLJr3vT=w@mail.gmail.com> <6.2.5.6.2.20130206224118.0b15d738@resistor.net> <CAF4+nEFpZChc8sRE=uEEd4zYMd0jzZqn7rJ7sBSxR6OtosGGSQ@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Cc: draft-eastlake-additional-xmlsec-uris@tools.ietf.org, Bjoern Hoehrmann <derhoermi@gmx.net>, ietf@ietf.org, Frederick Hirsch <frederick.hirsch@nokia.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Feb 2013 01:44:14 -0000

Hi Donald,
At 07:37 07-02-2013, Donald Eastlake wrote:
>As I say, although I frequently put them near the front of my Internet
>Drafts, the RFC Editor always moves them to the end.

I understood. :-)

>they ask not to be listed. Anyway, my practice is not because anyone
>has asked to be listed nearer the beginning of the document but
>because I think they deserve to be so listed.

I like the practice.

>Well, I could rename Section 5 to be "Allocation Considerations" and
>provide two subsection, one "5.1 IANA Considerations" and one "5.2 W3C
>Allocation Considerations" or the like and perhaps also move some of
>the material at the beginning of Section 2 down to 5.2.

The IANA Considerations will be removed on publication.  You could 
move it to 5.2 and do the above.

>RFC4648 is Informational, so that would cause yet another downref. RFC
>2045 has not bee obsoleted and seems fine to me for this purpose.

I forgot about the Informational status.  It's easier to avoid the down-ref.

Regards,
-sm