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

Eliot Lear <lear@cisco.com> Fri, 11 July 2008 13:39 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 AC2DA3A6B13; Fri, 11 Jul 2008 06:39:24 -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 548A03A6B13; Fri, 11 Jul 2008 06:39:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.499
X-Spam-Level:
X-Spam-Status: No, score=-6.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, 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 rhzHxrF443mU; Fri, 11 Jul 2008 06:39:22 -0700 (PDT)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id D04443A6AD6; Fri, 11 Jul 2008 06:39:21 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.30,345,1212364800"; d="scan'208";a="14137887"
Received: from ams-dkim-2.cisco.com ([144.254.224.139]) by ams-iport-1.cisco.com with ESMTP; 11 Jul 2008 13:39:26 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m6BDdQ4p014979; Fri, 11 Jul 2008 15:39:26 +0200
Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com [144.254.231.87]) by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id m6BDdQnc014045; Fri, 11 Jul 2008 13:39:26 GMT
Received: from xfe-ams-331.emea.cisco.com ([144.254.231.72]) by xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 11 Jul 2008 15:39:26 +0200
Received: from adsl-247-5-fixip.tiscali.ch ([10.61.66.144]) by xfe-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 11 Jul 2008 15:39:25 +0200
Message-ID: <4877628D.9020200@cisco.com>
Date: Fri, 11 Jul 2008 15:39:25 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Thunderbird/3.0a2pre (Macintosh; 2008070903)
MIME-Version: 1.0
To: Bob Braden <braden@ISI.EDU>
Subject: Re: Call for review of proposed update to ID-Checklist
References: <200807101550.IAA16153@gra.isi.edu>
In-Reply-To: <200807101550.IAA16153@gra.isi.edu>
X-OriginalArrivalTime: 11 Jul 2008 13:39:25.0984 (UTC) FILETIME=[88FC8A00:01C8E35B]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1022; t=1215783566; x=1216647566; c=relaxed/simple; s=amsdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=lear@cisco.com; z=From:=20Eliot=20Lear=20<lear@cisco.com> |Subject:=20Re=3A=20Call=20for=20review=20of=20proposed=20u pdate=20to=20ID-Checklist |Sender:=20; bh=xga5oQUvot226je8gPbAGHhSAIqea+i7IsKtYaisxqA=; b=B/MplwlK3435CbxZbIHrkyxabDmVfHhvIL7Zzt9rr1AcGfY5cjtk+hKvi2 eUSucL9qWS1DXBMiVIBv/S/3VW0AZi7O23EhsElF2/8RCoqNyd5ueoSvhIxs obH1OBJiQq;
Authentication-Results: ams-dkim-2; header.From=lear@cisco.com; dkim=pass ( sig from cisco.com/amsdkim2001 verified; );
Cc: john-ietf@jck.com, iesg@ietf.org, moore@network-heretics.com, ietf@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

Bob,
> This contradicts Section 2.1 of RFDC 1123, which says an application
> SHOULD support literal addresses (and of course DNS support is a MUST) --
> Section 6.1.1.)
>    

Within the application space, which is what we were talking about with 
RFC 1123, I'd have to say that the times have changed.  Back in 1989 DNS 
was still relatively unproven, failures were common, and there was a 
need to be able to get around DNS.  Remember that even as late as two 
years prior, one had to edit SunOS binaries to gain access to DNS.  
Worse, use of literals in applications leads to their being placed in 
configuration files, and that's just bad juju in a dynamic world.  I'm 
not saying that DNS is perfect by any stretch, but the alternative is worse.

Still, I don't think John is suggesting that we prohibit applications 
from supporting literals.  I personally just think we shouldn't 
highlight such examples.

As I recall, John was in the room, by the way, when that text was discussed.

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