IETF Logo Mail Archive

Re: [Ianaplan] Review of draft-ietf-ianaplan-icg-response-01

Eliot Lear <lear@cisco.com> Sun, 26 October 2014 21:30 UTC

Return-Path: <lear@cisco.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 DB6881A1AA6 for <ianaplan@ietfa.amsl.com>; Sun, 26 Oct 2014 14:30:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 k1mqtoqqNSVM for <ianaplan@ietfa.amsl.com>; Sun, 26 Oct 2014 14:30:47 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 296C51A1A9E for <ianaplan@ietf.org>; Sun, 26 Oct 2014 14:30:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1733; q=dns/txt; s=iport; t=1414359047; x=1415568647; h=message-id:date:from:mime-version:to:subject:references: in-reply-to; bh=mDuGQt709qRhnWHhUtfvkzeo2xe2Nb9bb6lyOaXu+Lw=; b=kVPATNcy6lxmalgPH98cLLbGABOhdVt+U37fcE7rilU73IHj43Xd0Cej H6JEwyb7C652e9d1G3NaQzxjYzkWjt849ekYxPsHbbMiSYfHN+D8VC5cU q585H5NtV3zuVN756867nMsCpQhsdwn5x1O+IxBnt8Y0k0XfYfRhTcZoP Y=;
X-Files: signature.asc : 486
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqIEAPpmTVStJssW/2dsb2JhbABch0DRQAKBHwF9hAMBAQQjVRELDgoJFgsCAgkDAgECAUUGAQwIAQGIPbNok3QBAQEBAQEBAwEBAQEBAQEbkQ+Cd4FUAQSUF4FQh3qHbI5Cg3k8gnoBAQE
X-IronPort-AV: E=Sophos;i="5.04,791,1406592000"; d="asc'?scan'208";a="221540990"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP; 26 Oct 2014 21:30:45 +0000
Received: from [10.61.108.74] (dhcp-10-61-108-74.cisco.com [10.61.108.74]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s9QLUj5X029492; Sun, 26 Oct 2014 21:30:45 GMT
Message-ID: <544D680A.7030808@cisco.com>
Date: Sun, 26 Oct 2014 22:30:50 +0100
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Miles Fidelman <mfidelman@meetinghouse.net>, "ianaplan@ietf.org" <ianaplan@ietf.org>
References: <E74C02CC-8A35-4057-95E4-14925B332456@cooperw.in> <544B44BD.7030805@cisco.com> <734aafb2601d4c7f9fa3184daa6dddb1@EX13-MBX-13.ad.syr.edu> <544D3DC3.5000409@cisco.com> <544D4437.7080108@meetinghouse.net>
In-Reply-To: <544D4437.7080108@meetinghouse.net>
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="5KXRQhpbewDkaRCG1Po78NhskoUIlLWNk"
Archived-At: http://mailarchive.ietf.org/arch/msg/ianaplan/UDxriez3_XLgifEX0HoYdwRCytI
Subject: Re: [Ianaplan] Review of draft-ietf-ianaplan-icg-response-01
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: Sun, 26 Oct 2014 21:30:49 -0000

Hi Miles,

On 10/26/14, 7:57 PM, Miles Fidelman wrote:
>
> Also, note that, as far as the process is concerned - IAOC and IETF
> are the same entity (IAOC is the entity that reflects IETF when it
> comes to contracts).  Language like "the IAOC is asked" is cumbersome,
> since for legal and contractual purposes, that's the IETF asking the
> IETF to do something.  It's more accurate to say that "the IETF
> proposes that, before a transition occurs, that supplemental
> agreements be put in place.... with the IOAC acting as the legal and
> contracting representative of the IETF."
>

What we are writing right now is a proposal, not contract language.  We
are expressing both our desire and our intent.  As you point out, the
IAOC would handle the specific language.

Eliot

v2.23.0 | Report a Bug | By Email