Re: [Ianaplan] IANA stewardship transition RFP

S Moonesamy <sm+ietf@elandsys.com> Tue, 09 September 2014 07:19 UTC

Return-Path: <sm@elandsys.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 CECAF1A0B72 for <ianaplan@ietfa.amsl.com>; Tue, 9 Sep 2014 00:19:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.442
X-Spam-Level:
X-Spam-Status: No, score=-3.442 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-1.652, T_DKIM_INVALID=0.01] 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 2O6Nlsd8xANE for <ianaplan@ietfa.amsl.com>; Tue, 9 Sep 2014 00:19:54 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id AF5631A0B14 for <ianaplan@ietf.org>; Tue, 9 Sep 2014 00:19:54 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.139.179]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s897JT04022419 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 9 Sep 2014 00:19:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1410247183; x=1410333583; bh=jxqUiC3UJ0g6fYffCuoy6Qu1kJVWdOZTcj6w+r7JIKI=; h=Date:To:From:Subject:In-Reply-To:References; b=gFMGBdDpVEI30U0Insi6kMvE6xLdIfisVMTxhU10aMpuEKt8qn3CI4mk9UXeTWTAy 0h76Y8LelcOVaQFoLTgLUUt2Sm+JYHi9tLZl21+Wnb3810W1ngszuxb9M5Wi8vsUqy ENdOlAMzOJDkfdC3ICsKv6ZcdrscAC/2TW7puQTk=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1410247183; x=1410333583; i=@elandsys.com; bh=jxqUiC3UJ0g6fYffCuoy6Qu1kJVWdOZTcj6w+r7JIKI=; h=Date:To:From:Subject:In-Reply-To:References; b=18SZLxyFdxaumSdSEWds84r0LQUMtOr4wBRPkqYSipIS6EPvl2iQeN+9XVQxxYKcB cWs26YXb0DozUO4hzixieWoeCUbDgXsrh21VzvkZxaD+GzT8l5i+rBtl/JgB8V/DkD JV3qKWNDn8eJriDleCEC2r6H8HO4XHtXMALLCeoc=
Message-Id: <6.2.5.6.2.20140908211756.0b771830@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 08 Sep 2014 23:38:11 -0700
To: Alissa Cooper <alissa@cooperw.in>, ianaplan@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <D02B9040.554E5%alissa@cooperw.in>
References: <D02B9040.554E5%alissa@cooperw.in>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: http://mailarchive.ietf.org/arch/msg/ianaplan/dmEBbXywjP_6WiWysFDGnHg8Jaw
Subject: Re: [Ianaplan] IANA stewardship transition RFP
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: Tue, 09 Sep 2014 07:19:55 -0000

Hi Alissa,
At 05:18 02-09-2014, Alissa Cooper wrote:
>The IANA stewardship coordination group (ICG) has produced a stable draft RFP

This is a late comment; I am okay if it is ignored.

On Page 3:

   "Identify which category of the IANA functions this submission proposes
    to address:

     [ ] Names [ ] Numbers [ ] Protocol Parameters"

 From the United States Department of Commerce web site:

     The IANA functions have historically included:  (1) the 
coordination of the
     assignment of technical Internet protocol parameters; (2) the 
administration
     of certain responsibilities associated with Internet DNS root 
zone management;
     (3) the allocation of Internet numbering resources; and (4) other services
     related to the management of the .ARPA and .INT top-level domains."

In my opinion the text on Page 3 conflates those with direct 
operational or service relationships with the IANA functions 
operator; namely names, numbers, protocol
parameters, with the IANA functions.

The IANAPLAN working group Charter uses the term "IANA function".  It 
does not make sense (to me) to argue that .ARPA falls under the 
"Protocol Parameters" category.  It might be less disputable if the 
text follows the definition provided on the United States Department 
of Commerce web site.

Regards,
S. Moonesamy