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

"Richard Hill" <rhill@hill-a.ch> Tue, 04 November 2014 09:46 UTC

Return-Path: <rhill@hill-a.ch>
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 27B5F1A893E for <ianaplan@ietfa.amsl.com>; Tue, 4 Nov 2014 01:46:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 l8tIHOap3bFy for <ianaplan@ietfa.amsl.com>; Tue, 4 Nov 2014 01:46:56 -0800 (PST)
Received: from smtp3.infomaniak.ch (smtp3.infomaniak.ch [IPv6:2001:1600:2:5:92b1:1cff:fe01:147]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7C04C1A8932 for <ianaplan@ietf.org>; Tue, 4 Nov 2014 01:46:56 -0800 (PST)
Received: from Laurie (adsl-178-39-117-99.adslplus.ch [178.39.117.99]) (authenticated bits=0) by smtp3.infomaniak.ch (8.14.5/8.14.5) with ESMTP id sA49kmOr022083; Tue, 4 Nov 2014 10:46:48 +0100
From: Richard Hill <rhill@hill-a.ch>
To: Alissa Cooper <alissa@cooperw.in>, Eliot Lear <lear@cisco.com>
Date: Tue, 04 Nov 2014 10:46:40 +0100
Message-ID: <GLEAIDJPBJDOLEICCGMNMENGCNAA.rhill@hill-a.ch>
MIME-Version: 1.0
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <BD280D79-F0F5-4E6C-8A99-BE6BA822CF3A@cooperw.in>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157
Archived-At: http://mailarchive.ietf.org/arch/msg/ianaplan/MUo7Ur9PgLdFnlzUc1lInpXp5ps
Cc: ianaplan@ietf.org, Andrew Sullivan <ajs@anvilwalrusden.com>
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
Reply-To: rhill@hill-a.ch
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 09:46:58 -0000

Thank you for this, but I still prefer the language that I proposed in my
previous message, that is:

"2.  results in the transfer of any associated marks and identifiers to the
IETF Trust, with the understanding that current and subsequent operators of
the IANA function shall be allowed to use them free of charge."

Best,
Richard

> -----Original Message-----
> From: Ianaplan [mailto:ianaplan-bounces@ietf.org]On Behalf Of Alissa
> Cooper
> Sent: mardi, 4. novembre 2014 02:27
> To: Eliot Lear
> Cc: ianaplan@ietf.org; Andrew Sullivan
> Subject: Re: [Ianaplan] control and negotiation (was Re:
> draft-ietf-ianaplan-icg-response-02 working group last call)
>
>
> Hi Eliot,
>
> On Nov 3, 2014, at 5:15 PM, Eliot Lear <lear@cisco.com> wrote:
>
> >
> > On 11/3/14, 5:12 PM, Alissa Cooper wrote:
> >> Hi Eliot,
> >>
> >> On Nov 3, 2014, at 2:03 PM, Eliot Lear <lear@cisco.com> wrote:
> >>
> >>> I suggest that if
> >>> the IETF/IAB or IETF trust takes control of the name, it do
> so with the
> >>> understanding that it take responsibility for seeing that backward
> >>> compatibility continue for each customer (names, numbers, protocol
> >>> parameters, in particular) for so long as it is safe to do so.  If
> >>> someone else wants to take control of the name, they should make that
> >>> same promise.
> >> This is so close to the language that I suggested that it’s
> hard for me to tell the difference between what you’re suggesting
> and what I suggested. To state the above requirement concisely:
> >>
> >> "Whoever owns the marks and identifiers has responsibility for
> ensuring backwards compatibility in the event that IANA
> operations shift to different entit(ies).”
> >>
> >> The requirement is that the owner of the marks/identifiers has
> to enable a smooth transition of the operations — regardless of
> whether the marks owner is the same as the operator or different
> or if there are multiple operators. Because the current owner is
> ICANN, this requirement would fall on ICANN.
> >>
> >> I would be satisfied if we substitute the above requirement in
> place of the one currently in the draft about the transfer of
> marks and identifiers. Do I read your email correctly that you
> would be satisfied as well?
> >
> > Very much so!!
>
> Cool. So I would suggest something like this:
>
> "To address concerns regarding appropriate contingencies to transition
>    to another operator, the IAOC is asked to conclude a supplemental
>    agreement that-
>
> ...
>
>    2.  requires the owner of any associated marks and identifiers
> to ensure backwards compatibility with subsequent operators.”
>
> Alissa
>
>
> >
> > Eliot
> >
>
> _______________________________________________
> Ianaplan mailing list
> Ianaplan@ietf.org
> https://www.ietf.org/mailman/listinfo/ianaplan
>
>