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

John Levine <johnl@iecc.com> Tue, 01 July 2008 22:36 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 D2A8D3A6BE8; Tue, 1 Jul 2008 15:36:48 -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 C06D23A6BF3 for <ietf@core3.amsl.com>; Tue, 1 Jul 2008 15:36:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.41
X-Spam-Level:
X-Spam-Status: No, score=-10.41 tagged_above=-999 required=5 tests=[AWL=0.489, BAYES_00=-2.599, RCVD_IN_BSP_TRUSTED=-4.3, RCVD_IN_DNSWL_MED=-4]
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 ifrKcY9E34Un for <ietf@core3.amsl.com>; Tue, 1 Jul 2008 15:36:47 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [208.31.42.53]) by core3.amsl.com (Postfix) with ESMTP id 9FC373A696F for <ietf@ietf.org>; Tue, 1 Jul 2008 15:36:46 -0700 (PDT)
Received: (qmail 46048 invoked from network); 1 Jul 2008 22:36:55 -0000
Received: from simone.iecc.com (208.31.42.47) by mail1.iecc.com with QMQP; 1 Jul 2008 22:36:55 -0000
Date: 1 Jul 2008 22:36:55 -0000
Message-ID: <20080701223655.14768.qmail@simone.iecc.com>
From: John Levine <johnl@iecc.com>
To: ietf@ietf.org
Subject: Re: Update of RFC 2606 based on the recent ICANN changes?
In-Reply-To: <p06240808c4905ec8295c@[10.20.30.162]>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Cc: paul.hoffman@vpnc.org
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-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

> This does not mean that ICANN won't listen to the IETF; it means
> that there will be voices more familiar to ICANN saying things
> different than we are.

One of the few ICANN committees that actually works is the SSAC, the
Security and Stability Advisory Committee.  It includes a lot of
people we know, starting with Steve Crocker, the chair.  I cannot ever
recall a time when ICANN acted contrary to the advice of the SSAC.

So although I agree that there's a lot not to like about ICANN, the
chances that they will do technically dangerous things are low.

http://www.icann.org/committees/security/

R's,
John
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf