Re: [Ianaplan] A draft for your review

S Moonesamy <> Sat, 30 August 2014 14:44 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 748131A03D2 for <>; Sat, 30 Aug 2014 07:44:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -0.288
X-Spam-Status: No, score=-0.288 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, RCVD_IN_SORBS_WEB=0.77, RP_MATCHES_RCVD=-0.668, T_DKIM_INVALID=0.01] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id tzXv1cNGinyc for <>; Sat, 30 Aug 2014 07:44:52 -0700 (PDT)
Received: from ( [IPv6:2001:470:f329:1::1]) by (Postfix) with ESMTP id 90A061A03B8 for <>; Sat, 30 Aug 2014 07:44:52 -0700 (PDT)
Received: from ([]) (authenticated bits=0) by (8.14.5/8.14.5) with ESMTP id s7UEiRUS028875 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 30 Aug 2014 07:44:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple;; s=mail2010; t=1409409885; x=1409496285; bh=F9NZyZt9g9Jw5xQ6vl4DC/3orXZkuFR7ASglZ+TG2a4=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=AuasRGXkFtLS0FbBWgeG2F4ZdNwX0piXSNktI2kEfaIuQ0ehXKehVkUqdmO8Dp7DL GEaqY4WobnReXYYCLb62ok2wqvUyXxmvWl5LIx2psWXB0yahNv92TkfcpiqqKV8nh2 hKZUWVR19yc073N2loIlCepE4kjE5OUiTmyHSU84=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple;; s=mail; t=1409409885; x=1409496285;; bh=F9NZyZt9g9Jw5xQ6vl4DC/3orXZkuFR7ASglZ+TG2a4=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=yUKq3pwd382VJIU0ZlDeNXEqcPRZkwuQcDyAQkQAGj7OhlliBEZcHeG9oEdbHJRyE r2IPWACjB9MqpqNwOg8TAmOPZ5deWPnzwVk56DHpT+d3Y3f6bX5wYrj/KjKfwWZjzB NJ5EQ5EqdKFNnc+wwrPdlOdAXWC/j/paQcFZeF6M=
Message-Id: <>
X-Mailer: QUALCOMM Windows Eudora Version
Date: Sat, 30 Aug 2014 07:38:33 -0700
To: Eliot Lear <>,
From: S Moonesamy <>
In-Reply-To: <>
References: <>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Cc: Russ Housley <>
Subject: Re: [Ianaplan] A draft for your review
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IANA Plan <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sat, 30 Aug 2014 14:44:54 -0000

Hi Eliot,
At 00:32 30-08-2014, Eliot Lear wrote:
>I have posted a -00 draft that seeks to respond to the most current 
>version of the RFP I could get my hands on.  Would you kindly 
>provide some thoughts about it?  I am most particularly concerned 
>about substance at the moment.  The sorts of things I'm looking for are these:
>Is the text in the "IETF Response" accurate and in fact responsive 
>to the question?
>Is there anything missing?
>Is there anything that does not parse well?  Did you think "Huh??" 
>when you read a sentence?
>My intent is to have a second version out prior to the cutoff for 
>the Honolulu meeting as a candidate for the IANAPLAN working group 
>to adopt, assuming the working group is chartered.

   "The IETF is a global voluntary standards organization whose goal is
    to make the Internet work better [RFC3595]."

The IETF cannot be a MIB module. :-)

Quoting from the draft:

   "The customer of the IANA protocol parameters function is the Internet
    Engineering Task Force (IETF)."

The above is inconsistent with a stated IETF position.

   "1.  The IETF protocol parameter registry function has been and
       continues to be capably provided by the Internet technical

What is the "Internet technical community"?

   "The IETF uses the IANA protocol parameter registries for
    this purpose."

The above is not aligned with the stated position of the IETF.

Quoting two parts of the responses out of context:

   "It is important to note that the IETF includes anyone who wishes to
    participate, including anyone from ICANN or the RIRs, and many people
    from those organizations regularly do."

   "In-person attendance is not required for participation, and many
    people participate in email discussions that have never attended
    an IETF meeting."

I scanned the ietf@ mailing list archives and I did not find anyone 
from ICANN or the RIRs participating on that mailing list.

   "Because of the nature of the agreement, questions of jurisdiction are

Why are questions of jurisdictions immaterial?

   "Any modifications to the protocol parameter registry function
    should be made using the IETF process"

The above is incorrect.

The IETF responses are not well-formulated in my opinion.  There 
isn't any reference to the IANA Functions contract.

As this topic has been mentioned I'll comment.  From

   "The mission of The Internet Corporation for Assigned Names and Numbers
    ("ICANN") is to coordinate, at the overall level, the global Internet's
    systems of unique identifiers, and in particular to ensure the stable
    and secure operation of the Internet's unique identifier systems.  In
    particular, ICANN:

    1. Coordinates the allocation and assignment of the three sets of unique
     identifiers for the Internet, which are

       "c. Protocol port and parameter numbers."

ICANN may have to adjust its bylaws if RFC 6220 is to be followed.

S. Moonesamy