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

"Peterson, Jon" <jon.peterson@neustar.biz> Tue, 04 November 2014 22:07 UTC

Return-Path: <jon.peterson@neustar.biz>
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 446161A0137 for <ianaplan@ietfa.amsl.com>; Tue, 4 Nov 2014 14:07:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.267
X-Spam-Level:
X-Spam-Status: No, score=-102.267 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 elLUvS6zgl1X for <ianaplan@ietfa.amsl.com>; Tue, 4 Nov 2014 14:07:34 -0800 (PST)
Received: from mx0a-0018ba01.pphosted.com (mx0a-0018ba01.pphosted.com [67.231.149.94]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 20D0E1A010C for <ianaplan@ietf.org>; Tue, 4 Nov 2014 14:07:34 -0800 (PST)
Received: from pps.filterd (m0049402.ppops.net [127.0.0.1]) by m0049402.ppops.net-0018ba01. (8.14.7/8.14.7) with SMTP id sA4M5C2X017068; Tue, 4 Nov 2014 17:07:33 -0500
Received: from stntexhc11.cis.neustar.com ([156.154.17.216]) by m0049402.ppops.net-0018ba01. with ESMTP id 1qf4uq887f-3 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 04 Nov 2014 17:07:33 -0500
Received: from STNTEXMB10.cis.neustar.com ([169.254.5.97]) by stntexhc11.cis.neustar.com ([::1]) with mapi id 14.03.0158.001; Tue, 4 Nov 2014 17:07:32 -0500
From: "Peterson, Jon" <jon.peterson@neustar.biz>
To: Miles Fidelman <mfidelman@meetinghouse.net>, "ianaplan@ietf.org" <ianaplan@ietf.org>
Thread-Topic: [Ianaplan] control and negotiation (was Re: draft-ietf-ianaplan-icg-response-02 working group last call)
Thread-Index: AQHP960iQbkZx6Ao80Cv4+wEz5Ij95xPyGuAgAA0/ACAAADXAIAAAw4AgACLogCAACs6gP//uiCAgADC1gCAAAfPgIAACgwAgAAESoD//32igIAAiAgAgAAA6YD//3yTAAARQdmA//99bYA=
Date: Tue, 04 Nov 2014 22:07:32 +0000
Message-ID: <D07E8C2E.135FA0%jon.peterson@neustar.biz>
References: <545944EA.7070903@meetinghouse.net> <GLEAIDJPBJDOLEICCGMNIEOJCNAA.rhill@hill-a.ch> <D07E8620.135F82%jon.peterson@neustar.biz> <54594B3D.4040202@meetinghouse.net>
In-Reply-To: <54594B3D.4040202@meetinghouse.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.4.4.140807
x-originating-ip: [192.168.129.162]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <AE421B9ECF09324C8BFCA6903F2B6C06@neustar.biz>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=nai engine=5600 definitions=7612 signatures=670572
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 kscore.is_bulkscore=2.1774748670822e-10 kscore.compositescore=0 circleOfTrustscore=0 compositescore=0.997362837850562 urlsuspect_oldscore=0.997362837850562 suspectscore=0 recipient_domain_to_sender_totalscore=0 phishscore=0 bulkscore=0 kscore.is_spamscore=0 recipient_to_sender_totalscore=0 recipient_domain_to_sender_domain_totalscore=0 rbsscore=0.997362837850562 spamscore=0 recipient_to_sender_domain_totalscore=0 urlsuspectscore=0.9 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1402240000 definitions=main-1411040199
Archived-At: http://mailarchive.ietf.org/arch/msg/ianaplan/t4Gi55MSV76tm89co1bYY_-PloA
Subject: Re: [Ianaplan] 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: Tue, 04 Nov 2014 22:07:37 -0000


>Pretty much ALL of the questions the ICG has posed are organizational
>and contractual in nature - roles, responsibilities, who does what, to
>whom.  Who develops policy, and by what process.  Who implements
>policy.  Who coordinates with whom.  What will change if and when the
>NTIA CONTRACT goes away; and what needs to change for that to work.
>
>Very little, if anything we've been asked to respond to is technical in
>nature.

... yes, and, we'll answer the organizational questions from our
perspective and be on our way. But those parts of the document are not
what has gotten us into this tight little thread. The controversial part
is what powers or rights we as an organization need in case of calamity.
Your assessment is that this a moral question that requires a political
confrontation. Mine is that this is a minor matter that is technical in
nature - it really isn't that exciting, or even that interesting.

>If we think such matters are "nonsense," and/or outside our scope of
>expertise - then, by definition, we should not be the (only) ones
>addressing them.

The nonsense is the cloud of political turmoil being kicked up around
these transition questions, which only distracts us from deciding what
steps, if any, we need to take to safeguard ourselves.

And the ICG's scope of inquiry is much larger than the IETF, with good
reason. The transition raises many questions that have little, or nothing,
to do with us.

Jon Peterson
Neustar, Inc.

>Miles Fidelman
>
>Peterson, Jon wrote:
>>
>>> I agree with Miles. The IANA transition is not an engineering
>>>exercise. It
>>> is a contractual exercise.
>> The question of what we safeguards we require in case of a dire
>> contingency is only a small component of the response we've been asked
>>to
>> deliver, but it's the only part under discussion in this corner of the
>> thread. Arguing that seizing assets and powers (arguably ones we never
>> held before) is the proper way to address this contingency would indeed
>> make it a contractual exercise. But that isn't the only type of
>>safeguard
>> under consideration.
>>
>>> If the IETF is not the right body to take care of those sorts of
>>>issues,
>>> then let's say so and ask somebody else to do the job.
>> We are the right body to issue a response to the questions the ICG has
>> asked, but after that we'll go back to being engineers and doing what we
>> do to make the Internet better. The sooner we're rid of this nonsense,
>>the
>> better.
>>
>> Jon Peterson
>> Neustar, Inc.
>>
>>> Best,
>>> Richard
>>>
>>>> -----Original Message-----
>>>> From: Ianaplan [mailto:ianaplan-bounces@ietf.org]On Behalf Of Miles
>>>> Fidelman
>>>> Sent: mardi, 4. novembre 2014 22:28
>>>> To: ianaplan@ietf.org
>>>> Subject: Re: [Ianaplan] control and negotiation (was Re:
>>>> draft-ietf-ianaplan-icg-response-02 working group last call)
>>>>
>>>>
>>>> Peterson, Jon wrote:
>>>>>> Somehow, this "oh, if ICANN doesn't do the job, we'll take our ball
>>>> and
>>>>>> move it elsewhere" seems a rather timid attitude and approach.
>>>>> No, it's just engineering. We're a body of engineers. If we can solve
>>>> a
>>>>> problem by engineering rather than engaging in politics, it plays to
>>>> our
>>>>> strengths. When we try to assert some authority over governments and
>>>>> corporations, then we are playing in a space where we have
>>>> little traction
>>>>> or competence and where we are likely to lose.
>>>>>
>>>>> Please stop trying to steer us there.
>>>>>
>>>> We are MORE than a body of engineers.  We are a body that promulgates
>>>> standards that are central to global infrastructure, and we are part
>>>>of
>>>> a body of contractually defined relationships that define roles and
>>>> responsibilities for how those standards are used and implemented.
>>>>
>>>> The whole point of the NTIA transition process is to clarify, and
>>>> re-align some of those roles and responsibilities when the NTIA
>>>>contract
>>>> goes away - which has very little to do with engineering, and a whole
>>>> lot to do with "techno-politics."
>>>>
>>>> Please stop trying to deny that, or steer us away from the reality of
>>>> the roles and responsibilities associated with the role the IETF
>>>>plays.
>>>>
>>>> Miles Fidelman
>>>>
>>>>
>>>> --
>>>> In theory, there is no difference between theory and practice.
>>>> In practice, there is.   .... Yogi Berra
>>>>
>>>> _______________________________________________
>>>> 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
>
>
>-- 
>In theory, there is no difference between theory and practice.
>In practice, there is.   .... Yogi Berra
>
>_______________________________________________
>Ianaplan mailing list
>Ianaplan@ietf.org
>https://www.ietf.org/mailman/listinfo/ianaplan