FW: I-D Action: draft-leiba-cotton-iana-5226bis-12.txt

"Adrian Farrel" <adrian@olddog.co.uk> Tue, 05 April 2016 15:26 UTC

Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id B051512D1C1 for <ietf@ietfa.amsl.com>; Tue, 5 Apr 2016 08:26:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.62
X-Spam-Status: No, score=-2.62 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id HhISL4xhgtcj for <ietf@ietfa.amsl.com>; Tue, 5 Apr 2016 08:26:51 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com []) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A7DD312D157 for <ietf@ietf.org>; Tue, 5 Apr 2016 08:26:50 -0700 (PDT)
Received: from asmtp1.iomartmail.com (localhost.localdomain []) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id u35FQmcF021450; Tue, 5 Apr 2016 16:26:48 +0100
Received: from 950129200 (dhcp-b176.meeting.ietf.org []) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id u35FQiKo021442 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Tue, 5 Apr 2016 16:26:46 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <draft-leiba-cotton-iana-5226bis.all@tools.ietf.org>
References: <20160405133227.25939.47740.idtracker@ietfa.amsl.com>
In-Reply-To: <20160405133227.25939.47740.idtracker@ietfa.amsl.com>
Subject: FW: I-D Action: draft-leiba-cotton-iana-5226bis-12.txt
Date: Tue, 5 Apr 2016 16:26:41 +0100
Message-ID: <049e01d18f4f$904a45b0$b0ded110$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQDUrZL7Ep9u/D4LkqTUWDcSII0yHaF1Qe3w
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-
X-TM-AS-Result: No--12.153-10.0-31-10
X-imss-scan-details: No--12.153-10.0-31-10
X-TMASE-MatchedRID: uIXscqjWAPlCBQieSpAGz3BRIrj8R47Fh8Ytn75ClDM9APipIEm6xP62 cy+dCX5TaMQFL6nCTW02c6uDK/rF8/H/rEyV9ntVibD9NG8qYdP6gI/+ywuCj11d55ms0luCrWV wOu7Bu1vVsXfkupVIqRar2jEX1DCkXSJ4c3nT+QdoMLOoNHsM9s9ZbgogvG8ExaQNbiRXdZohOd waoiaUInzvHCKIwjZeIx2isBen1esO0G36v8LMKszWN98iBBeGDZlTFg+eXzsLNAv/WTKB/liqA yk7LkbkdS/l9fGXMz0fzXumXQL3DAzyMxeMEX6wOX/V8P8ail3Yr6U3ZlQkdsRB0bsfrpPIfiAq rjYtFiQev05iH2BBogfdS2trjeLApSzXyni4ojivpy7uZTPpWH7cGd19dSFd
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/Oxv-JVaQ9XmD-F_9qN6p-mWLDlI>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: adrian@olddog.co.uk
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 05 Apr 2016 15:26:52 -0000

Michelle and Barry,

Thanks for resurrecting this document. It's been a while and IIRC the document
was somewhere in the IESG process post IETF last call. You seem to have made
some pretty substantial changes: I wonder if you could post a summary. I also
wonder whether the Shepherding AD could let us know whether this will come back
for a further IETF last call (I can relax and read it later) or plans to go for
approval with only IESG sign-off (I need to read it urgently and scream if there
are issues).

FWIW, I noticed that section 1.2 now has some text in double square brackets
that seeks to (temporarily?) describe what material should go on the first
version of https://iana.org/help/protocol-registration. Can I suggest that you
make the RFC-to-be stable and future-proof by converting this to a description
of a minimal subset of information that should be on the web page in the first
and all subsequent versions (i.e., information that should be on the page,
period) and then you can remove the brackets.


> -----Original Message-----
> From: I-D-Announce [mailto:i-d-announce-bounces@ietf.org] On Behalf Of
> internet-drafts@ietf.org
> Sent: 05 April 2016 14:32
> To: i-d-announce@ietf.org
> Subject: I-D Action: draft-leiba-cotton-iana-5226bis-12.txt
> A New Internet-Draft is available from the on-line Internet-Drafts