IETF Logo Mail Archive

Re: Update of RFC 2606 based on the recent ICANN changes ?

Karl Auerbach <karl@cavebear.com> Mon, 07 July 2008 22:03 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D1EDF28C2E7; Mon, 7 Jul 2008 15:03:07 -0700 (PDT)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EC74828C2E8 for <ietf@core3.amsl.com>; Mon, 7 Jul 2008 15:03:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uHWKK0hgHXH3 for <ietf@core3.amsl.com>; Mon, 7 Jul 2008 15:03:05 -0700 (PDT)
Received: from lear.cavebear.com (lear.cavebear.com [64.62.206.88]) by core3.amsl.com (Postfix) with ESMTP id 214113A6B3A for <ietf@ietf.org>; Mon, 7 Jul 2008 15:03:05 -0700 (PDT)
Received: from klack.cavebear.com (desdemona.iwl.com [69.12.250.155]) (authenticated bits=0) by lear.cavebear.com (8.14.2/8.14.2) with ESMTP id m67M3CDR020836 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 7 Jul 2008 15:03:12 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=cavebear.com; s=04142008; t=1215468192; bh=34ZrLZ22WjQbXLd6L1HJsGNkVQIQGCZfNfB3Nw trbHU=; h=Message-ID:Date:From:MIME-Version:To:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=W9vMBhEVTb0Z p/iU9gbdsPf7YNflEfMMHJQky842pPEjwt4rPLoFfg6RhjGzM+5DZFE3Wqbciwcsd5Z 7ye0o7PO8/p/5rz1vevHLJ7gas3WF8ga4xkKncgg6Evn9XUfJy5CEKqqQJfjR6Woe4J t0wUvuOAhEq1kKGx7a67R9VFg=
Message-ID: <487292A0.3080401@cavebear.com>
Date: Mon, 07 Jul 2008 15:03:12 -0700
From: Karl Auerbach <karl@cavebear.com>
User-Agent: Thunderbird 2.0.0.14 (X11/20080501)
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>, ietf@ietf.org
Subject: Re: Update of RFC 2606 based on the recent ICANN changes ?
References: Your message of <200807022323.m62NNwVJ034275@drugs.dv.isc.org> <BLU137-W18376D2DBA85C8F712C06F93980@phx.gbl> <8953A1CE-E953-409F-A692-BD12DF4ADE61@acm.org> <48724347.6020500@dcrocker.net> <18BA25DED8BFD9F794A10E84@p3.JCK.COM>
In-Reply-To: <18BA25DED8BFD9F794A10E84@p3.JCK.COM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

I guess you've heard the old joke which asks "How could God create the 
world in only seven days? - Because He had no installed base."

If we move this thread up one level of abstraction much of the 
conversation is asking the question of how strongly we respect the 
installed base of software out there on the net.

Do we have any principles we can use to guide our choice of where we put 
the needle along the continuum from "no change, no way" to "any and 
every change is allowed"?

  		--karl--
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf

v2.23.0 | Report a Bug | By Email