Re: Call for review of proposed update to ID-Checklist

Keith Moore <moore@network-heretics.com> Wed, 09 July 2008 23:32 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 872683A687D; Wed, 9 Jul 2008 16:32:21 -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 E52483A6860 for <ietf@core3.amsl.com>; Wed, 9 Jul 2008 16:32:19 -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=[AWL=0.000, 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 oY1HpvWFdqzZ for <ietf@core3.amsl.com>; Wed, 9 Jul 2008 16:32:19 -0700 (PDT)
Received: from m1.imap-partners.net (m1.imap-partners.net [64.13.152.131]) by core3.amsl.com (Postfix) with ESMTP id CD5FA3A683C for <ietf@ietf.org>; Wed, 9 Jul 2008 16:32:19 -0700 (PDT)
Received: from lust.indecency.org (adsl-6-17-238.tys.bellsouth.net [65.6.17.238]) by m1.imap-partners.net (MOS 3.8.4-GA) with ESMTP id AWK60585 (AUTH admin@network-heretics.com) for ietf@ietf.org; Wed, 9 Jul 2008 16:22:29 -0700 (PDT)
Message-ID: <48754825.7000800@network-heretics.com>
Date: Wed, 09 Jul 2008 19:22:13 -0400
From: Keith Moore <moore@network-heretics.com>
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Call for review of proposed update to ID-Checklist
References: <20080708184427.5D55F28C0EC@core3.amsl.com> <p06250117c4996966b0d4@[75.145.176.242]> <DA239261F08994CDC795CDD5@p3.JCK.COM> <200807091419.m69EJ4TX025969@cichlid.raleigh.ibm.com> <D8C00052ED1EE1FDAF109DC7@p3.JCK.COM>
In-Reply-To: <D8C00052ED1EE1FDAF109DC7@p3.JCK.COM>
Cc: Thomas Narten <narten@us.ibm.com>, Pete Resnick <presnick@qualcomm.com>, IETF Chair <chair@ietf.org>, ietf@ietf.org, iesg@ietf.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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

John C Klensin wrote:

> 	(iii) The IETF has indicated enough times that domain
> 	names, not literal addresses, should be used in both
> 	protocols and documents that doing anything else should
> 	reasonably require clear and strong justification.

I take issue with that as a general statement.  There are plenty of 
applications where the ability to use literal addresses on an occasional 
basis is quite useful - e.g. for diagnostic purposes (of various kinds) 
or in a pinch when DNS is broken or not set up correctly.  Furthermore 
addresses are precise where domain names are not.

To remove the capability to use address literals is to cripple our 
protocols.

(your other three points seemed fine to me)

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