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

Thomas Narten <narten@us.ibm.com> Wed, 09 July 2008 14:19 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 D89123A6AD2; Wed, 9 Jul 2008 07:19:01 -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 D5DED3A6AC7; Wed, 9 Jul 2008 07:19:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[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 Ts57ZcUMUpyM; Wed, 9 Jul 2008 07:19:00 -0700 (PDT)
Received: from e35.co.us.ibm.com (e35.co.us.ibm.com [32.97.110.153]) by core3.amsl.com (Postfix) with ESMTP id 4C11228C17B; Wed, 9 Jul 2008 07:18:58 -0700 (PDT)
Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com [9.17.195.106]) by e35.co.us.ibm.com (8.13.8/8.13.8) with ESMTP id m69EJ9uS003790; Wed, 9 Jul 2008 10:19:09 -0400
Received: from d03av03.boulder.ibm.com (d03av03.boulder.ibm.com [9.17.195.169]) by d03relay04.boulder.ibm.com (8.13.8/8.13.8/NCO v9.0) with ESMTP id m69EJ8fB177600; Wed, 9 Jul 2008 08:19:08 -0600
Received: from d03av03.boulder.ibm.com (loopback [127.0.0.1]) by d03av03.boulder.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id m69EJ7oq030971; Wed, 9 Jul 2008 08:19:07 -0600
Received: from cichlid.raleigh.ibm.com (sig-9-48-33-10.mts.ibm.com [9.48.33.10]) by d03av03.boulder.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id m69EJ6GA030830 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 9 Jul 2008 08:19:07 -0600
Received: from cichlid.raleigh.ibm.com (cichlid-new [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.2/8.12.5) with ESMTP id m69EJ4TX025969; Wed, 9 Jul 2008 10:19:04 -0400
Message-Id: <200807091419.m69EJ4TX025969@cichlid.raleigh.ibm.com>
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Call for review of proposed update to ID-Checklist
In-reply-to: <DA239261F08994CDC795CDD5@p3.JCK.COM>
References: <20080708184427.5D55F28C0EC@core3.amsl.com> <p06250117c4996966b0d4@[75.145.176.242]> <DA239261F08994CDC795CDD5@p3.JCK.COM>
Comments: In-reply-to John C Klensin <john-ietf@jck.com> message dated "Tue, 08 Jul 2008 16:04:33 -0400."
Date: Wed, 09 Jul 2008 10:19:04 -0400
From: Thomas Narten <narten@us.ibm.com>
Cc: Pete Resnick <presnick@qualcomm.com>, IETF Chair <chair@ietf.org>, ietf@ietf.org, IETF Announcement list <ietf-announce@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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

John C Klensin <john-ietf@jck.com> writes:

> While I agree, I believe that it would be of great help if the
> IESG  gave indications of the situations in which an exception
> to a "SHOULD" would be appropriate.

Yes.

And on the particular question of example DNS names:


> 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.

Thomas

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