Re: [Ianaplan] Consensus? Question from the ICG

Jefsey <jefsey@jefsey.com> Mon, 16 February 2015 16:53 UTC

Return-Path: <jefsey@jefsey.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 16F951A1B61 for <ianaplan@ietfa.amsl.com>; Mon, 16 Feb 2015 08:53:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.631
X-Spam-Level: *
X-Spam-Status: No, score=1.631 tagged_above=-999 required=5 tests=[BAYES_50=0.8, IP_NOT_FRIENDLY=0.334, MISSING_MID=0.497] 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 ri00aW90Qcdp for <ianaplan@ietfa.amsl.com>; Mon, 16 Feb 2015 08:53:01 -0800 (PST)
Received: from host.presenceweb.org (host.presenceweb.org [67.222.106.46]) (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 018021A1B54 for <ianaplan@ietf.org>; Mon, 16 Feb 2015 08:53:00 -0800 (PST)
Received: from 194.217.130.77.rev.sfr.net ([77.130.217.194]:33930 helo=MORFIN-PC.mail.jefsey.com) by host.presenceweb.org with esmtpa (Exim 4.84) (envelope-from <jefsey@jefsey.com>) id 1YNOup-0005s7-GP; Mon, 16 Feb 2015 08:52:59 -0800
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 16 Feb 2015 17:52:49 +0100
To: "Leslie Daigle (ThinkingCat)" <ldaigle@thinkingcat.com>, "ianaplan@ietf.org" <ianaplan@ietf.org>
From: Jefsey <jefsey@jefsey.com>
In-Reply-To: <54E214E9.3020103@thinkingcat.com>
References: <54E214E9.3020103@thinkingcat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - host.presenceweb.org
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - jefsey.com
X-Get-Message-Sender-Via: host.presenceweb.org: authenticated_id: jefsey+jefsey.com/only user confirmed/virtual account not confirmed
X-Source:
X-Source-Args:
X-Source-Dir:
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/FAfePpHyVMvrFJGLEs20mbzvwvU>
Cc: Marc Blanchet <marc.blanchet@viagenie.ca>
Subject: Re: [Ianaplan] Consensus? Question from the ICG
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: Mon, 16 Feb 2015 16:53:02 -0000
X-Message-ID:
Message-ID: <20150216165304.16726.25093.ARCHIVE@ietfa.amsl.com>

At 17:03 16/02/2015, Leslie Daigle (ThinkingCat) wrote:
>There seems to be general agreement that there is not an 
>incompatibility between the RIR proposal requirement and the IETF's 
>proposal.  We would like to determine if there is consensus on the 
>following points, as expressed by Dave Crocker (thanks!) on February 9, 2015:
>
>     With regards to the IANA trademark and the IANA.ORG domain, 
> both are associated with the IANA Numbering Services and not with a 
> particular IANA Numbering Services Operator.

OK.

>     The IETF considers the IETF Trust to be an acceptable candidate 
> for holding the trademark and domain.

Due to the post-RFC 6852 implicit fork, this seems consistent with 
the WG/IANAPLAN consensus (I abstain).

>     The IETF would support a decision by the IETF Trust to hold the 
> IANA mark, and iana.org domain in behalf of the Internet community.

This wording should be corrected as "in behalf of the IETF community" 
(or this part to be removed) for multiple reasons including that:
* the IETF Trust is only concerned by IETF rights
* ICANN (or its successor) and its possible allies belong to the 
Internet community. In case of disagreement with the current operator 
(this is the case we consider) this wording would mean that the 
current operator is actually a legitimate co-owner of the domain name,
jfc