Re: [Ianaplan] I-D Action: draft-ietf-ianaplan-icg-response-10.txt

Eliot Lear <> Thu, 28 July 2016 22:03 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 6D67012D911; Thu, 28 Jul 2016 15:03:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -15.807
X-Spam-Status: No, score=-15.807 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, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=unavailable autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id DGIwYnh-gLix; Thu, 28 Jul 2016 15:03:16 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 7830312D59E; Thu, 28 Jul 2016 14:45:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=8317; q=dns/txt; s=iport; t=1469742309; x=1470951909; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to; bh=IKf1gIBv36QjTG87mCqKHyiIhzRp67oiu9m8ptNdk0k=; b=KlktvROJ+mONE9rSKNFf+L9AvvsVl90jeMxYXsNdEJSJUgvOGRrb0U8K DxJm7dwby9k9WlpRTSAi59VTrrMvcfUR2DGmhMnwg5p0qDWN4EeWfOQzT KIF7KbGa9dts1ZkvL5iyUuTmEX7SsG7MNjAu4X73hpoSWKLZDjzbJky4C E=;
X-Files: signature.asc : 481
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AfCwCIe5pX/xbLJq1chBsqUrN6hwIkh?= =?us-ascii?q?S9KAoIAAQEBAQEBXieEXQEFAQEhSwsQCxgqAgInMAcMBgIBAYgtDq4ijWoBAQE?= =?us-ascii?q?BAQEBAQIBAQEBAQEBAQEBAQ4OiCKCVYdBgloFmTKDOoFwbohlgWtOhAyDDoVsj?= =?us-ascii?q?C6DeFSDfDoyiQEBAQE?=
X-IronPort-AV: E=Sophos;i="5.28,435,1464652800"; d="asc'?scan'208,217";a="639838795"
Received: from (HELO ([]) by with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 28 Jul 2016 21:45:07 +0000
Received: from [] ([]) by (8.14.5/8.14.5) with ESMTP id u6SLj6iF007580; Thu, 28 Jul 2016 21:45:06 GMT
References: <>
From: Eliot Lear <>
Message-ID: <>
Date: Thu, 28 Jul 2016 23:45:06 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="uJoWsexvSTk2RbGNQOSFBpkuvLf6JAEEa"
Archived-At: <>
Subject: Re: [Ianaplan] I-D Action: draft-ietf-ianaplan-icg-response-10.txt
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IANA Plan <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 28 Jul 2016 22:03:17 -0000

Hi there,

This document contains a number of very small changes that the WG agreed
would happen after the approval of the proposal by NTIA.  Specifically:

  * A reference to the entire proposal by the ICG is included.
  * Copies of correspondence to the ICG is included.
  * The tense in a small number of cases in the introduction has been
    change from past imperfect to past perfect to match the moment in
    time we are now in.


On 7/28/16 11:42 PM, wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Planning for the IANA/NTIA Transition of the IETF.
>         Title           : Response to the IANA Stewardship Transition Coordination Group (ICG) Request for Proposals on the IANA protocol parameters registries
>         Authors         : Eliot Lear
>                           Russ Housley
> 	Filename        : draft-ietf-ianaplan-icg-response-10.txt
> 	Pages           : 37
> 	Date            : 2016-07-28
> Abstract:
>    The U.S.  NTIA solicited a request from ICANN to propose how the NTIA
>    should end its oversight of the IANA functions.  After broad
>    consultations, ICANN in turn created the IANA Stewardship Transition
>    Coordination Group.  That group solicited proposals for thre three
>    major IANA functions: names, numbers, and protocol parameters.  This
>    document contains the IETF response to that solicitation for protocol
>    parameters.  It was included in an aggregate response to the NTIA
>    alongside those for names and numbering resources that are being
>    developed by their respective operational communities.  A reference
>    to that response may be found in the introduction, and additional
>    correspendence is included in the Appendix.
> The IETF datatracker status page for this draft is:
> There's also a htmlized version available at:
> A diff from the previous version is available at:
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at
> Internet-Drafts are also available by anonymous FTP at:
> _______________________________________________
> Ianaplan mailing list