IETF Logo Mail Archive

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

Paul Hoffman <paul.hoffman@vpnc.org> Wed, 09 July 2008 17:03 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 5E6513A6B1A; Wed, 9 Jul 2008 10:03:23 -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 F12113A6B11 for <ietf@core3.amsl.com>; Wed, 9 Jul 2008 10:03:21 -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 xvGvnZY960Ps for <ietf@core3.amsl.com>; Wed, 9 Jul 2008 10:03:21 -0700 (PDT)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id C7A453A68B0 for <ietf@ietf.org>; Wed, 9 Jul 2008 10:03:20 -0700 (PDT)
Received: from [10.20.30.162] (dsl-63-249-108-169.cruzio.com [63.249.108.169]) (authenticated bits=0) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id m69H3Rpt079133 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Wed, 9 Jul 2008 10:03:28 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p06240811c49a9ee1da61@[10.20.30.162]>
In-Reply-To: <1907905599.20080709093728@pobox.com>
References: <20080708184427.5D55F28C0EC@core3.amsl.com> <0e6701c8e1db$6b9603a0$6501a8c0@china.huawei.com> <1907905599.20080709093728@pobox.com>
Date: Wed, 09 Jul 2008 10:03:26 -0700
To: IETF Discussion <ietf@ietf.org>
From: Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: Call for review of proposed update to ID-Checklist
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

At 9:37 AM -0700 7/9/08, Bill McQuillan wrote:
>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.

"foo" and "bar" seem fine for nerdy IETF examples. "bat" would pose 
similar security issues as "com" :-). "baz" seems awfully close to 
the ever-so-popular "biz" TLD.

"tld" seems like an excellent suggestion. Not much like any current 
TLDs; it's well-known in the field of use; it is unlikely that there 
is much commercial value to it; it's nearly impossible to pronounce 
without spelling out the acronym.

--Paul Hoffman, Director
--VPN Consortium
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf

v2.23.0 | Report a Bug | By Email