IETF Logo Mail Archive

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

Andrew Sullivan <ajs@anvilwalrusden.com> Mon, 10 November 2014 19:37 UTC

Return-Path: <ajs@anvilwalrusden.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 F362A1ABC75 for <ianaplan@ietfa.amsl.com>; Mon, 10 Nov 2014 11:37:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.141
X-Spam-Level:
X-Spam-Status: No, score=-0.141 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311] 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 ZOkYOJljWSfk for <ianaplan@ietfa.amsl.com>; Mon, 10 Nov 2014 11:37:26 -0800 (PST)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 163B21A00C0 for <ianaplan@ietf.org>; Mon, 10 Nov 2014 11:37:26 -0800 (PST)
Received: from mx1.yitter.info (dhcp-bfe9.meeting.ietf.org [31.133.191.233]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 69B9C8A031 for <ianaplan@ietf.org>; Mon, 10 Nov 2014 19:37:24 +0000 (UTC)
Date: Mon, 10 Nov 2014 14:37:20 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ianaplan@ietf.org
Message-ID: <20141110193720.GG39116@mx1.yitter.info>
References: <20141108155153.GB37292@mx1.yitter.info> <D083864D.138D18%jon.peterson@neustar.biz> <A6D94EF5-BD92-4080-8C18-E415BD0BB880@isi.edu> <C78A1523-316F-46A1-9FCE-D0D205679C84@gmail.com> <13B26DE5-315D-453F-B89B-377CCD338ED9@isi.edu> <A7BD5ECF-11E4-42F1-A2B7-BF9B399635C3@gmail.com> <14D42443-53E7-49FA-88DD-7F4BB6BC2DF4@istaff.org> <545F69FB.5000501@meetinghouse.net> <54601A01.2080407@cs.tcd.ie> <54611166.40307@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <54611166.40307@cisco.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: http://mailarchive.ietf.org/arch/msg/ianaplan/zpCtEinAiCJJMprveYTLQocjQy8
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
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, 10 Nov 2014 19:37:27 -0000

Hi Eliot,

On Mon, Nov 10, 2014 at 09:26:30AM -1000, Eliot Lear wrote:
> will also say that we don't want to make it any more difficult than it
> already is for people to make applications for our protocol parameters,
> nor do we want to break any processes (automated or human) that retrieve
> the protocol parameters so that they are included in the right places in
> various distributions.

I think that is a desirable state of affairs.  I think there is an
open question, however, about how valuable that is as compared to
other desiderata.  I think that may be part of what the discussion
recently has turned on.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

v2.23.0 | Report a Bug | By Email