Re: [Ianaplan] A draft for your review

S Moonesamy <sm+ietf@elandsys.com> Fri, 24 October 2014 15:06 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 DF5471A1A48 for <ianaplan@ietfa.amsl.com>; Fri, 24 Oct 2014 08:06:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.8
X-Spam-Level:
X-Spam-Status: No, score=-1.8 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, T_DKIM_INVALID=0.01, T_RP_MATCHES_RCVD=-0.01] autolearn=no
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 Ma13B0F5r8-k for <ianaplan@ietfa.amsl.com>; Fri, 24 Oct 2014 08:06:07 -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 189671A1A4A for <ianaplan@ietf.org>; Fri, 24 Oct 2014 08:06:07 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.134.110]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s9OF5g4e017443 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 24 Oct 2014 08:05:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1414163158; x=1414249558; bh=1Gdyqw9uyKPvvPuM837hPVB1WKtkUNrqCFed2Z5cSG0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=zzI6y0cmBT3cJXpnqo/whhGZFIhKLeQ7DVxGVXU1LqWLblT8xME9NV6FtYok1BQJp GBF8wSztRkkIMEw8gQy0p5H/RChndr0bHAQ/EsRC4egpAE2TKXJuG1d+C3w3wcAmUO FFLetIvu+Hi03V+V98i6v0mZkYOq9eadgj6wqbCE=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1414163158; x=1414249558; i=@elandsys.com; bh=1Gdyqw9uyKPvvPuM837hPVB1WKtkUNrqCFed2Z5cSG0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=MU3CpoZ/0Zuu658RnP/tM+VxcTnXmgKWLsrCVQsSGWe65yw3c7jUKKWba0lAKqi25 QKT/sdX6Mmiq/jDEYE/mTibEsfM1AXyWt55nJPuXxz5/SkIdAmNw8PTvy67+rWIKTR LkG17qTAr11kw0rijYut8H4Z6qXMH9cgou86rtz4=
Message-Id: <6.2.5.6.2.20141024060709.0b2a6610@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 24 Oct 2014 06:21:51 -0700
To: Suzanne Woolf <suzworldwide@gmail.com>
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <4C1255B9-68C3-45D5-A618-2C7553386DF4@gmail.com>
References: <54017E09.8060504@cisco.com> <6.2.5.6.2.20140830052032.0c96c880@resistor.net> <54047E4A.30503@cisco.com> <6.2.5.6.2.20140901094544.0b305698@resistor.net> <54059587.8070608@cisco.com> <6.2.5.6.2.20141024004255.0b5ef5d8@resistor.net> <4C1255B9-68C3-45D5-A618-2C7553386DF4@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Archived-At: http://mailarchive.ietf.org/arch/msg/ianaplan/CSAkNV1EfLg4LnLaVjo3SXu70ng
Cc: ianaplan@ietf.org, Eliot Lear <lear@cisco.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: Fri, 24 Oct 2014 15:06:09 -0000

Hi Suzanne,
At 05:50 24-10-2014, Suzanne Woolf wrote:
>Off the top of my head, just in the groups I follow closely: There 
>is another ICANN staffer I know of participating in DPRIVE; he also 
>has a long history as a protocol designer and implementer in matters 
>DNS and WHOIS/PROVREG/WEIRDS. There's at least one person who's held 
>formal roles in the GNSO who has also been an IETF participant, 
>including discussions in DNSOP (and at least a couple more who have 
>posted to IANAPLAN). The CTO of APNIC posted just the other day to 
>WEIRDS, and some other APNIC staff are extremely well-known in DNS 
>and routing groups in the IETF. Staff from RIPE and LACNIC 
>participate in DNSOP discussions and other DNS-related work such as 
>recent BOFs. Assorted technologists, some very senior, associated 
>with TLD operators participate in both ICANN and IETF discussions, 
>and various TLD operators sponsor IETF participation for employees 
>and contractors as contributors, including WG chairs and IAB members 
>from time to time.
>
>It depends a bit on what you mean by "affiliated," if you're 
>seriously trying to assess cross-participation, but if nothing else, 
>experience suggests that counting noses (or email addresses) isn't 
>actually that helpful.

I usually count reviews.  For what it is worth, I was not counting 
email addresses.

>Would it be better if there was slightly more overlap among 
>ICANN/RIR staff, participants in their processes from other 
>organizations, and participation in the IETF? Probably. (For 
>example, we'd want input from people intimately familiar with 
>matters ICANN in any process to revisit RFC 6761, whether they were 
>ICANN staff or not.) Is the option open to everyone? Yes. Do they 
>sometimes take advantage of it? Yes.
>
>Eliot's language could stand some tinkering, but I can live with it. 
>Since I owe him text on another point, I'll suggest while I'm here 
>the following revision:
>
>"It is important to note that the IETF includes anyone who wishes to 
>participate, including staff or other participants from ICANN or the 
>Regional Internet Registries (RIRs), and people affiliated with 
>those organizations regularly do."

The suggested text looks better than what is currently in the 
draft.  I could settle for that.

Regards,
S. Moonesamy