Re: [Ianaplan] Question from the ICG

Milton L Mueller <mueller@syr.edu> Wed, 11 February 2015 02:53 UTC

Return-Path: <mueller@syr.edu>
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 A28731A6F11 for <ianaplan@ietfa.amsl.com>; Tue, 10 Feb 2015 18:53:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] 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 DLIgpbaLSvOa for <ianaplan@ietfa.amsl.com>; Tue, 10 Feb 2015 18:52:58 -0800 (PST)
Received: from smtp2.syr.edu (smtp2.syr.edu [128.230.18.92]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 60D321A6F30 for <ianaplan@ietf.org>; Tue, 10 Feb 2015 18:52:58 -0800 (PST)
Received: from EX13-MBX-03.ad.syr.edu (ex13-mbx-03.ad.syr.edu [128.230.108.133]) by smtp2.syr.edu (8.14.7/8.14.7) with ESMTP id t1B2quLu024481 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <ianaplan@ietf.org>; Tue, 10 Feb 2015 21:52:57 -0500
Received: from EX13-MBX-13.ad.syr.edu (128.230.108.144) by EX13-MBX-03.ad.syr.edu (128.230.108.133) with Microsoft SMTP Server (TLS) id 15.0.847.32; Tue, 10 Feb 2015 21:52:20 -0500
Received: from EX13-MBX-13.ad.syr.edu ([128.230.108.144]) by EX13-MBX-13.ad.syr.edu ([128.230.108.144]) with mapi id 15.00.0847.030; Tue, 10 Feb 2015 21:52:01 -0500
From: Milton L Mueller <mueller@syr.edu>
To: "ianaplan@ietf.org" <ianaplan@ietf.org>
Thread-Topic: [Ianaplan] Question from the ICG
Thread-Index: AQHQRC0IxVHZPheECUmrxB/6reEr+Zzod1GAgAA/EYCAAAPcgIAABKIAgAAbPICAAAVyAIAAGkKAgACk3YCAAJkhgIAA0D0A//+6WHA=
Date: Wed, 11 Feb 2015 02:52:01 +0000
Message-ID: <bc8508f79c6a4fb8b512658684f0bf40@EX13-MBX-13.ad.syr.edu>
References: <54DA08AF.9000508@meetinghouse.net> <20150211015854.4032.qmail@ary.lan>
In-Reply-To: <20150211015854.4032.qmail@ary.lan>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [199.91.193.37]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.13.68, 1.0.33, 0.0.0000 definitions=2015-02-11_01:2015-02-10,2015-02-11,1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1402240000 definitions=main-1502110027
Archived-At: <http://mailarchive.ietf.org/arch/msg/ianaplan/mGGpry0NXzM3P2OCoOn790dDBCY>
Subject: Re: [Ianaplan] 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: Wed, 11 Feb 2015 02:53:00 -0000


> -----Original Message-----
> If it would make CRISP happy, we can say that the IETF trust will accept the
> IANA domain name and trademark under mutually acceptable terms to be
> negotiated when an if a transfer becomes necessary.  But don't try to guess
> the details of what would be going on then.

This is precisely the time you do NOT want to discuss the terms and conditions of a trademark or domain transfer. That needs to be taken care of in advance of any conflict or transfer. You don't need to "guess the details of what would be going on" during a transfer to place the asset in hands (e.g., IETF trust) that are independent of any IANA functions contractor.