IETF Logo Mail Archive

Re: [Ianaplan] returning to the topic of IANA trademarks and domains

Seun Ojedeji <seun.ojedeji@gmail.com> Sat, 19 September 2015 06:59 UTC

Return-Path: <seun.ojedeji@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 24CF51B5693 for <ianaplan@ietfa.amsl.com>; Fri, 18 Sep 2015 23:59:37 -0700 (PDT)
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 qwIDEH48cwqJ for <ianaplan@ietfa.amsl.com>; Fri, 18 Sep 2015 23:59:35 -0700 (PDT)
Received: from mail-wi0-x233.google.com (mail-wi0-x233.google.com [IPv6:2a00:1450:400c:c05::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 947D11A90BC for <ianaplan@ietf.org>; Fri, 18 Sep 2015 23:59:35 -0700 (PDT)
Received: by wicfx3 with SMTP id fx3so53854515wic.0 for <ianaplan@ietf.org>; Fri, 18 Sep 2015 23:59:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=se7n4sCZ4od+0H7ngMEvw/HPWi6pSwtyxVFBNtkzIf0=; b=0magoawfRVDB9XcrOHUkdkO5aFnDvt5Bm2pND70kUgJWTET8n8v6EMk2QVmbDrTXYC O8HJHS0qxwIJrnH0V37/IrEhfkG0lRk6iZRekRztztvKOU5R5e6qWVXzeyCiGc2TgH1j 2/7XUxVEpjr7EwBW6i9STbC+kwxq+TB09/HMhEqaAlHaApouxEOYaUhFphtjAINTeJU4 Fx2gott2ABwDEAQy6SvYOJF5r8Ewhpjq1tXG7TX1wsd77/tIQs4LOdnd2fndwrIb5Oje NGoMPW603hj84ORRtrajYpi0iPZbererJAOWVp7nrVOuu5locdJ61fdCOTAG10Lu4Aev jjeA==
MIME-Version: 1.0
X-Received: by 10.194.93.229 with SMTP id cx5mr11067127wjb.62.1442645974101; Fri, 18 Sep 2015 23:59:34 -0700 (PDT)
Received: by 10.194.171.170 with HTTP; Fri, 18 Sep 2015 23:59:34 -0700 (PDT)
Received: by 10.194.171.170 with HTTP; Fri, 18 Sep 2015 23:59:34 -0700 (PDT)
In-Reply-To: <757177E3-697A-43FA-960E-827AFA7C9869@piuha.net>
References: <695427AA-50BB-4C51-9764-4DCEAFF31993@piuha.net> <CAD_dc6gcuf8K95JYz1GjjLNow6aE0r4zeCV9nMGqxrebGCUbQw@mail.gmail.com> <757177E3-697A-43FA-960E-827AFA7C9869@piuha.net>
Date: Sat, 19 Sep 2015 07:59:34 +0100
Message-ID: <CAD_dc6h64ZFnyn_Z-CyYNBgYV4Jwq2uMPQ2489oMxVwDOfvE9Q@mail.gmail.com>
From: Seun Ojedeji <seun.ojedeji@gmail.com>
To: Jari Arkko <jari.arkko@piuha.net>
Content-Type: multipart/alternative; boundary="047d7beb98d2d2b5650520143006"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/zkFX_GeXjb3mNPHSgwUG6JlAFq0>
Cc: "Ianaplan@Ietf. Org" <ianaplan@ietf.org>
Subject: Re: [Ianaplan] returning to the topic of IANA trademarks and domains
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: <https://mailarchive.ietf.org/arch/browse/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, 19 Sep 2015 06:59:37 -0000

Thanks for the clarification Jari, it's very much understood now. Just a
minor clarification, I assume the IFO in agreement 3 would be specified by
the respective OCs in agreement 2 and any subsequent review of 3 will have
dependency on 2. Is that correct?

Cheers!
Sent from my Asus Zenfone2
Kindly excuse brevity and typos.
On 19 Sep 2015 06:17, "Jari Arkko" <jari.arkko@piuha.net> wrote:

> Seun,
>
> > Thanks for this update, the agreement categories does make sense.
>
> Thanks.
>
> > That said,  I think item 2 and 3 are somewhat interrelated and can be
> achieved with a single one
>
> This might be possible in the case where the operator and
> community are the same entity, but in the general case the
> three agreements would have different parties:
>
> 1. ICANN - Trust
> 2. Trust - an operational community
> 3. IANA functions operator - Trust
>
> Jari
>
>

v2.23.0 | Report a Bug | By Email