[Ianaplan] draft-lear-iana-icg-response-01 release
Eliot Lear <lear@cisco.com> Fri, 12 September 2014 06:49 UTC
Return-Path: <lear@cisco.com>
X-Original-To: ianaplan@ietfa.amsl.com
Delivered-To: ianaplan@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F0F4A1A0584 for <ianaplan@ietfa.amsl.com>; Thu, 11 Sep 2014 23:49:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.152
X-Spam-Level:
X-Spam-Status: No, score=-16.152 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.652, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SkF1svZA-WMk for <ianaplan@ietfa.amsl.com>; Thu, 11 Sep 2014 23:49:34 -0700 (PDT)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8ED831A0481 for <ianaplan@ietf.org>; Thu, 11 Sep 2014 23:49:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10791; q=dns/txt; s=iport; t=1410504573; x=1411714173; h=message-id:date:from:mime-version:to:subject; bh=aIJ78lX2a9J+5qQiWA2tBXu+QReoBSNkbbxSNjVgLyA=; b=GvoaieMzX3+lMGS9lVu4nCafhYiDkl7snWTepUawW2tM8b1VIVfKlkBl E7BAlB73br5ZeAljMbqTbOsYGpFo4KvrFKLKOIms9uDhWURop5hA7VzSj O/OW2VYah5DRSXXgUrSgLCwqYbtC1Sy93PqGeys69gKI5h0UpWB2dJvmY E=;
X-Files: signature.asc : 486
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AsEEAPKWElStJssW/2dsb2JhbABgg2AJSgSCfMViiHB4hC0EUSAdFgsCCwMCAQIBSw0IAQEFC4guCAWYbI80lXgBF5JNgVMFk1OBS2KCPYRGgV+FZY13g2M7LwGCTgEBAQ
X-IronPort-AV: E=Sophos;i="5.04,511,1406592000"; d="asc'?scan'208,217";a="170333632"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP; 12 Sep 2014 06:49:31 +0000
Received: from [10.61.214.144] ([10.61.214.144]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s8C6nVcU028170 for <ianaplan@ietf.org>; Fri, 12 Sep 2014 06:49:31 GMT
Message-ID: <5412977C.6080107@cisco.com>
Date: Fri, 12 Sep 2014 08:49:32 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: "ianaplan@ietf.org" <ianaplan@ietf.org>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="LftAbtq30htV9I6ovlJPBOJrO03JoQ8hj"
Archived-At: http://mailarchive.ietf.org/arch/msg/ianaplan/-ug1F-dTEeuFF34ekjZ78md9fH4
Subject: [Ianaplan] draft-lear-iana-icg-response-01 release
X-BeenThere: ianaplan@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IANA Plan <ianaplan.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ianaplan>, <mailto:ianaplan-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ianaplan/>
List-Post: <mailto:ianaplan@ietf.org>
List-Help: <mailto:ianaplan-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ianaplan>, <mailto:ianaplan-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Sep 2014 06:49:36 -0000
Hi everyone, You will have seen the announcement for the release of draft-lear-iana-icg-response-01. This message explains the changes. * The first change is probably the most notable. We've have changed the way questions from the RFP appear by using ">>> ". Russ has suggested that we consult the RFC Editor about this, and I think that's a good idea, but now seems like a good time to get feedback on this change. * Amusingly, we failed to include the "IANA Considerations" section in the -00 draft. Please review the simple text that is there. * There is now a very brief Security Considerations section. * We've attempted to spell out acronyms on first use. Thanks to Greg Wood for pointing this out. * The front matter now states "IANAPLAN" as opposed to "Network Working Group". IMHO that probably needs to change to IETF & IAB at the end. * The RFP has been updated to a later version. * The role of the IESG has been spelled out a bit more (Issue 19 on Github) * Special use registries have been clarified as discussed (Issues 14 and 15) * Russ' comment was taken out. * Last calls are open to anyone (Issue 17). * RFC 2418 is explicitly mentioned. * Extraneous overlap text removed (Issue 21) * The IETF is not a MIB module (Issue 7) * Answer order was reverted, as suggested by Leslie Daigle. * The IAB's responsibility explicitly stated. * Amended -> Supplemented and slightly reworded to explain what those supplements are (Issue 20) * Various URL references were not listed (fixed). * Reference added to IANA metrics. * A bunch of idnits addressed. * Other editorials. The authors ponder moving the introductory text from the ICG into an appendix. Views on that welcome as well as any other comments. Eliot
--- Begin Message ---A new version of I-D, draft-lear-iana-icg-response-01.txt has been successfully submitted by Eliot Lear and posted to the IETF repository. Name: draft-lear-iana-icg-response Revision: 01 Title: Draft Response to the Internet Coordination Group Request for Proposals on IANA Document date: 2014-09-12 Group: Individual Submission Pages: 20 URL: http://www.ietf.org/internet-drafts/draft-lear-iana-icg-response-01.txt Status: https://datatracker.ietf.org/doc/draft-lear-iana-icg-response/ Htmlized: http://tools.ietf.org/html/draft-lear-iana-icg-response-01 Diff: http://www.ietf.org/rfcdiff?url2=draft-lear-iana-icg-response-01 Abstract: This document contains the a draft response to a request for proposals from the IANA Stewardship Transition Coordination Group regarding the protocol parameters registries. It is meant to be included in an aggregate proposal that also includes contributions covering names and addresses that will be submitted from their respective operational communities. The IETF community is invited to comment and propose changes to this document. Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. The IETF Secretariat--- End Message ---