Re: [Ianaplan] A draft for your review

Eliot Lear <lear@cisco.com> Mon, 01 September 2014 14:32 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 2DF191A7030 for <ianaplan@ietfa.amsl.com>; Mon, 1 Sep 2014 07:32:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -12.469
X-Spam-Level:
X-Spam-Status: No, score=-12.469 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.668, 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 OePfgBDSgNn3 for <ianaplan@ietfa.amsl.com>; Mon, 1 Sep 2014 07:32:27 -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 DE22A1A06E8 for <ianaplan@ietf.org>; Mon, 1 Sep 2014 07:10:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4746; q=dns/txt; s=iport; t=1409580614; x=1410790214; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=FNrronMGU2Dy54jw+sIdog6kzWsZybYoPMBPhWhGe+U=; b=I76ckPgdfakMCVPqXn00V4+snOTwjTjVMdJcgMY5/5l5fPJk/yq+VpQE j44HpwDfTNv91DGfKwT2AjWLJb6yvj9ronHtyYdrS8J3/atn0PkqIdGyR MfPjCQhDWcsj60G+0N4jU5CFsmL0oeIXboBoyBSZ9D+/GMIeN7Mq6g+Vm w=;
X-Files: signature.asc : 486
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqQEABV9BFStJssW/2dsb2JhbABZg2CDU8UHh0wBgSZ3hAMBAQEDASNLCxALGAkhAgIPAkYGAQwBBwEBEIgmCA2lE5RgARMEjmsRAVAHgnmBUwEEijWJAoFKgk2FDoc3jWeDYzuBPoFAAQEB
X-IronPort-AV: E=Sophos;i="5.04,442,1406592000"; d="asc'?scan'208";a="157159938"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP; 01 Sep 2014 14:10:11 +0000
Received: from [10.61.212.165] ([10.61.212.165]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s81EABat009001; Mon, 1 Sep 2014 14:10:11 GMT
Message-ID: <54047E4A.30503@cisco.com>
Date: Mon, 01 Sep 2014 16:10:18 +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: S Moonesamy <sm+ietf@elandsys.com>, ianaplan@ietf.org
References: <54017E09.8060504@cisco.com> <6.2.5.6.2.20140830052032.0c96c880@resistor.net>
In-Reply-To: <6.2.5.6.2.20140830052032.0c96c880@resistor.net>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="VPCr0Q7GakogxBrq8P5RJvUniJjT1ONpI"
Archived-At: http://mailarchive.ietf.org/arch/msg/ianaplan/zmt5-yGEbvn1Zhs7WWObDqWsNS0
Cc: Russ Housley <housley@vigilsec.com>
Subject: Re: [Ianaplan] A draft for your review
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: Mon, 01 Sep 2014 14:32:33 -0000

Hi SM,


On 8/30/14, 4:38 PM, S Moonesamy wrote:
> 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. :-)

Thanks.  Doh!  Fixed.

>
> 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
>       community."
>
> 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.

The above text was taken verbatim (I think) from the principles that
were developed in the Spring, even before we knew of the NTIA
announcement.  I'm not saying one can't disagree or even debate the
point, but that's where the text came from.

>
> 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.

Really?  No Dave Conrad?  No John Curran?  No Patrik Fältstrom?  (just
to name a few).
>
>   "Because of the nature of the agreement, questions of jurisdiction are
>    immaterial."
>
> 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.

That is a statement of principle.  How do you believe it to be 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
> https://www.icann.org/resources/pages/bylaws-2012-02-25-en
>
>   "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.

They've done fine thus far without having done so.

Eliot