IETF Logo Mail Archive

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

Bill McQuillan <McQuilWP@pobox.com> Wed, 09 July 2008 16:37 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 5A27D3A6AF9; Wed, 9 Jul 2008 09:37:25 -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 37E4A3A6A88 for <ietf@core3.amsl.com>; Wed, 9 Jul 2008 09:37:24 -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 faoifnaaHs3i for <ietf@core3.amsl.com>; Wed, 9 Jul 2008 09:37:23 -0700 (PDT)
Received: from sasl.smtp.pobox.com (a-sasl-fastnet.sasl.smtp.pobox.com [207.106.133.19]) by core3.amsl.com (Postfix) with ESMTP id 6C0D83A6AB0 for <ietf@ietf.org>; Wed, 9 Jul 2008 09:37:23 -0700 (PDT)
Received: from localhost.localdomain (localhost [127.0.0.1]) by a-sasl-fastnet.sasl.smtp.pobox.com (Postfix) with ESMTP id 6D2CC27EB3; Wed, 9 Jul 2008 12:37:33 -0400 (EDT)
Received: from [192.168.0.3] (ip68-107-60-165.sd.sd.cox.net [68.107.60.165]) by a-sasl-fastnet.sasl.smtp.pobox.com (Postfix) with ESMTPA id E46BA27EB1; Wed, 9 Jul 2008 12:37:29 -0400 (EDT)
Date: Wed, 09 Jul 2008 09:37:28 -0700
From: Bill McQuillan <McQuilWP@pobox.com>
X-Priority: 3 (Normal)
Message-ID: <1907905599.20080709093728@pobox.com>
To: IETF Discussion <ietf@ietf.org>
Subject: Re: Call for review of proposed update to ID-Checklist
In-Reply-To: <0e6701c8e1db$6b9603a0$6501a8c0@china.huawei.com>
References: <20080708184427.5D55F28C0EC@core3.amsl.com> <0e6701c8e1db$6b9603a0$6501a8c0@china.huawei.com>
MIME-Version: 1.0
X-Pobox-Relay-ID: 54A3395E-4DD5-11DD-92B9-CE28B26B55AE-02871704!a-sasl-fastnet.pobox.com
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

On Wed, 2008-07-09, Spencer Dawkins wrote:
> If an example describes a complex network topology, it could be 
> appropriate to use a variety of names, IP addresses or prefixes that are 
> easily disambiguated, so that the reader might follow the example more 
> easily.

I wonder if it would make it easier to use "example" DNS names if, in
addition to the verbose and clumsy: "*.example", IMHO, we reserved gTLDs
like "*.foo", "*.bar", "*.bat", "*.baz", as well as the one used quite
frequently on this list lately: "*.tld", for use as example DNS names.

Or do we assume that economic concerns would triumph here?

-- 
Bill McQuillan <McQuilWP@pobox.com>

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

v2.23.0 | Report a Bug | By Email