[Ianaplan] IETF's role Re: control and negotiation (was Re: draft-ietf-ianaplan-icg-response-02 working group last call)

Suzanne Woolf <suzworldwide@gmail.com> Sat, 08 November 2014 14:59 UTC

Return-Path: <suzworldwide@gmail.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 816A51A1BA2 for <ianaplan@ietfa.amsl.com>; Sat, 8 Nov 2014 06:59:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 vkvS6cqWLCJg for <ianaplan@ietfa.amsl.com>; Sat, 8 Nov 2014 06:59:12 -0800 (PST)
Received: from mail-pa0-x229.google.com (mail-pa0-x229.google.com [IPv6:2607:f8b0:400e:c03::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0C9141A1BC5 for <ianaplan@ietf.org>; Sat, 8 Nov 2014 06:59:12 -0800 (PST)
Received: by mail-pa0-f41.google.com with SMTP id rd3so5412375pab.0 for <ianaplan@ietf.org>; Sat, 08 Nov 2014 06:59:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=uvqo5PKbJHR5ZxDp/3/D502yL99k/dTpyxV4nRa/aPQ=; b=WXMouC2MLHxixpev9JQp1bWJO37lnfG55vYf7MEXBsAk6uTtsDDiEuf+/yxRSPO/Bf 6W5Z70pseT4/V3GXn7FeQGWuevLAmY0JbqaAx6blccNQgmqW0/tcW8H6GCgTeiEfWSXf H2IpLVOFijzMMgUG0yHvrD/6I1s8wD9+NymJlPR7vINRzkjLHPEG2Te29r137/d510qc F9fL/J9z3xkoRSoIIDlFFEWHWTN1e9V3EQCuiX+JocpKC4F0m9XEE6cTzsJ7OhdSk0D1 7MydTzimN1Zsnka8cYD7Ds4vfoUiLiy67IgomCZ3yloDWARBFV0JWo5FA8fL7JxJsu5e dEBw==
X-Received: by 10.70.3.196 with SMTP id e4mr19724356pde.35.1415458751274; Sat, 08 Nov 2014 06:59:11 -0800 (PST)
Received: from [10.11.45.146] (rrcs-173-197-107-9.west.biz.rr.com. [173.197.107.9]) by mx.google.com with ESMTPSA id o5sm11733566pdr.50.2014.11.08.06.59.09 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 08 Nov 2014 06:59:10 -0800 (PST)
Content-Type: multipart/alternative; boundary="Apple-Mail=_7377184A-AE07-4DF5-8ED9-6C88697BFC07"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Suzanne Woolf <suzworldwide@gmail.com>
In-Reply-To: <CAD_dc6jaDbiw4kwy3yv9CwxK3SUDun1cC2Z1tSA1drGT+-qfig@mail.gmail.com>
Date: Sat, 08 Nov 2014 09:59:09 -0500
Message-Id: <ED92F18D-AEFF-4A02-A22F-7CD3E6C72FB5@gmail.com>
References: <GLEAIDJPBJDOLEICCGMNIEOJCNAA.rhill@hill-a.ch> <54594A50.4090305@meetinghouse.net> <20141105001731.GA30186@mx1.yitter.info> <54597BDB.7040305@meetinghouse.net> <5459BA98.1070006@gmail.com> <545A208A.7040304@meetinghouse.net> <631e3e3d29c843bd9c23151c63612989@EX13-MBX-13.ad.syr.edu> <20141105154903.GI30379@mx1.yitter.info> <498a39b81b774192bd2d609b3feab35f@EX13-MBX-13.ad.syr.edu> <20141105234444.GM31320@crankycanuck.ca> <545ABCB0.5080206@meetinghouse.net> <8f3dcda6c3db4cd8be1b77444f987d59@EX13-MBX-13.ad.syr.edu> <D0805C27.136BE7%jon.peterson@neustar.biz> <059f2b06a7b44f09b7568d8966861fb8@EX13-MBX-13.ad.syr.edu> <D0824FAD.137A42%jon.peterson@neustar.biz> <bcb86b6995de41feba256567c114265d@EX13-MBX-13.ad.syr.edu> <CAD_dc6jaDbiw4kwy3yv9CwxK3SUDun1cC2Z1tSA1drGT+-qfig@mail.gmail.com>
To: Seun Ojedeji <seun.ojedeji@gmail.com>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/ianaplan/k-unK1cDu8bkgXa7xsMY79tHJmE
Cc: ianaplan@ietf.org
Subject: [Ianaplan] IETF's role Re: control and negotiation (was Re: draft-ietf-ianaplan-icg-response-02 working group last call)
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: Sat, 08 Nov 2014 14:59:18 -0000

On Nov 7, 2014, at 4:16 PM, Seun Ojedeji <seun.ojedeji@gmail.com> wrote:
> Have been following the discussions and it's been quite interesting; much more interesting that it almost seem iana.org ownership is the deciding factor in this process[1].
> 
Have you read the draft? 

It seems to me that if you review both the mailing list and the draft, the work that's necessary for the IETF to reach consensus on what should go into the RFP response is mostly done.

It should perhaps also seem that most of the experienced IETF participants here don't regard anything about the iana.org domain name as "the deciding factor" in much of anything. Most of the pressure to make more of a point of what should happen to it in the event of a dispute is coming from people who are obviously deeply concerned about the future of the Internet, but whose primary experience of the IANA functions is not in the protocol parameters area or in how the IETF and its user communities interact with the IANA operator.
> The extent of back and fourth deliberation on the list, makes me wanna mention here that it will be good for IETF to start handling/addressing issues not only as a protocol parameter community but as the overall source of all the whole function. 
> For all it's worth, those who don't want to complicate the outcome of this process have great hope in IETF playing a leadership role in all these.
> 
I'm curious what you mean by this comment. Who thinks the IETF should be functioning here "not only as a protocol parameter community," what do they want instead, and how are they planning to make their requests or desires known?

As "the overall source of all the whole function," the IETF long ago delegated administration of certain protocol parameters to organizations deemed better able to address the related public policy concerns than the IETF is, or wants to be.  Are you suggesting revisiting that?
> I am beginning to wonder if this is the case.
> 
It looks to me as if the IETF is playing its part in a multi-stakeholder process, in which each of the operational communities directly affected by the IANA functions is expected to propose a transition plan for its area of concern. As far as I'd understood, and the ICG members here can certainly elaborate but the extensive public record is pretty clear, the ICG is then responsible for addressing gaps or conflicts between operational community plans. Its primary mechanism for resolving those conflicts is by engaging the affected operational communities to do so.

Certainly if later trouble can be avoided by communities collaborating now, we ought to try to make that happen. What do you think is missing?


thanks,
Suzanne

> Thanks.
> 
> Returning back to listening mode. ;)
> 
> Cheers!
> 1. Which IMO should just be a minimal component in this process especially as ntia is not the owner of the domain in the first place.
> sent from Google nexus 4
> kindly excuse brevity and typos.
> 
> On 7 Nov 2014 21:26, "Milton L Mueller" <mueller@syr.edu> wrote:
> > -----Original Message-----
> > Asking for a transfer sounds like a polite thing to do. Directing the IAOC to
> > "conclude a supplemental agreement" which "requires the transfer of any
> > associated marks and identifiers" - as the -02 text of the document reads
> > - sounds to me like an ultimatum which would antagonize other
> > stakeholders.
> 
> OK. I see the difference in the attitude with which we approach this. I am beginning to think it is a purely attitudinal matter and not all that substantive. So I have more sympathy for your position now but I still think you are focusing on the wrong things.
> 
> A request to the IAOC to "conclude an agreement" that "requires the transfer" is not an "ultimatum" it is a proposal for a rather impersonal set of institutional changes that sets the stage for long-term accountability improvements in Internet governance.
> 
> To put it more concretely, we are not talking to "nice people" sitting across the dinner table from us, asking them to pass the salt. We are trying to set the parameters for long term interactions among impersonal organizational entities and functions.
> 
> So if I were you I would focus on whether it is a good idea - for the general good of the Internet and for the IETF - for to have control of the iana.org domain and the trademark in the hands of the IETF trust or whether it is better for the public and the IETF to have it in the hands of ICANN. That's all that matters. The purpose of this exercise is to rearrange the institutional design to accommodate the withdrawal of the NTIA. The purpose is not to be polite or nice, or to avoid offending anyone. The purpose is to get it right.
> 
> If you sincerely believe that IETF should be permanently locked in to ICANN as IANA provider, should have no choice as to who performs those functions for it, and therefore the marks and domain should stay with ICANN, then fine. Please argue that position. I will engage with those arguments respectfully. But please let's not argue about etiquette!
> 
> _______________________________________________
> Ianaplan mailing list
> Ianaplan@ietf.org
> https://www.ietf.org/mailman/listinfo/ianaplan
> _______________________________________________
> Ianaplan mailing list
> Ianaplan@ietf.org
> https://www.ietf.org/mailman/listinfo/ianaplan