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

Keith Moore <moore@network-heretics.com> Wed, 09 July 2008 20:16 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 E0A2C3A6B73; Wed, 9 Jul 2008 13:16:47 -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 438EF3A6B72 for <ietf@core3.amsl.com>; Wed, 9 Jul 2008 13:16:47 -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 bLPBWEzSFm9c for <ietf@core3.amsl.com>; Wed, 9 Jul 2008 13:16:46 -0700 (PDT)
Received: from m1.imap-partners.net (m1.imap-partners.net [64.13.152.131]) by core3.amsl.com (Postfix) with ESMTP id E16F13A6B5F for <ietf@ietf.org>; Wed, 9 Jul 2008 13:16:15 -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 AWK41095 (AUTH admin@network-heretics.com) for ietf@ietf.org; Wed, 9 Jul 2008 13:06:25 -0700 (PDT)
Message-ID: <48751A3F.6030702@network-heretics.com>
Date: Wed, 09 Jul 2008 16:06:23 -0400
From: Keith Moore <moore@network-heretics.com>
User-Agent: Thunderbird 2.0.0.14 (Macintosh/20080421)
MIME-Version: 1.0
To: Thomas Narten <narten@us.ibm.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>
In-Reply-To: <200807091419.m69EJ4TX025969@cichlid.raleigh.ibm.com>
Cc: ietf@ietf.org, Pete Resnick <presnick@qualcomm.com>, IETF Chair <chair@ietf.org>, iesg@ietf.org, John C Klensin <john-ietf@jck.com>, IETF Announcement list <ietf-announce@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

> 
>> 6.  Addresses used in examples SHOULD use fully qualified domain names
>>     instead of literal IP addresses, and SHOULD use example fqdn's
>>     such as foo.example.com instead of real-world fqdn's. See
>>     [RFC2606] (Eastlake, D. and A. Panitz, "Reserved Top Level DNS
>>     Names," June 1999.) for example domain names that can be used.
> 
> Why the SHOULD? Presumably, because you don't want naive folk to take
> the examples in the RFC and use them in local config files and such,
> causing problems or other undesirable effects when they (unexpectedly)
> get used in the real world..
> 
> But in cases where this really is not a concern, there is also
> presumably not a need to _require_ use of the example names.

+1

Also, I'm convinced that in a document requiring numerous example 
domains, that restricting to 2606 domains can reduce readability.
(the DSN specifications come immediately to mind)

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