IETF Logo Mail Archive

[DNSOP] (no subject)

johnl@iecc.com Sat, 08 October 2016 02:00 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C03031294D3 for <dnsop@ietfa.amsl.com>; Fri, 7 Oct 2016 19:00:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.919
X-Spam-Level:
X-Spam-Status: No, score=0.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, MISSING_SUBJECT=1.799, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9ov9V2QF2BpC for <dnsop@ietfa.amsl.com>; Fri, 7 Oct 2016 19:00:22 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0DD8512947F for <dnsop@ietf.org>; Fri, 7 Oct 2016 19:00:21 -0700 (PDT)
Received: (qmail 16132 invoked by uid 100); 8 Oct 2016 02:00:19 -0000
Date: Sat, 08 Oct 2016 01:59:57 -0000
Message-ID: <20161008015957.16131.qmail@submit.iecc.com>
From: johnl@iecc.com
Cc: recipient list not shown:;
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/iPUl3PD7uV6LT5pxes0PxOVcEcw>
X-Mailman-Approved-At: Fri, 07 Oct 2016 19:02:51 -0700
Subject: [DNSOP] (no subject)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Oct 2016 02:00:24 -0000

>From not-for-mail  Fri Oct  7 22:00:19 2016
To: list-iecc-lists-ietf-dnsop@johnlevine.com
Path: not-for-mail
Subject: Re: [DNSOP] In a vacuum, nobody can hear you scream, was On the call for adoption on Special Use Names
Date: Sat, 8 Oct 2016 02:00:18 +0000 (UTC)
Organization: Taughannock Networks, Trumansburg NY
Message-ID: <nt9jvi$es1$1@miucha.iecc.com>
References: <20161007012033.23623.qmail@ary.lan> <c290f7db-e6e2-3745-1adb-e6f122bd4f40@acm.org> <DC3D08B6-7518-4B67-9180-93E7E824E135@icann.org> <1b1fe5e9-2708-82de-a77d-a9fc20c3a02c@gnu.org>
Cleverness: some
X-Newsreader: trn 4.0-test77 (Sep 1, 2010)
Originator: johnl@aryv.lan (John L)
From: John Levine <johnl@taugh.com>

>We have .example and example.* for documentation, yet the XMPP
>documentation uses shakespeare.lit (I don't think .lit matches any SUN
>or any entry in any DNS-related RFC.) FWIW, wikipedia sends .lit to some
>Microsoft file extension.  One cannot say that Peter St Andre is
>ignorant of IETF processes.  Use of *example* in documentation and
>.invalid in free software is a good sign that developers are ready to
>follow suit and respect the norms.

In RFC 6120, it's shakespeare.example.com and shakespeare.example.  

If you're referring to some random web site, life is too short to
enumerate all of the things that are wrong on the web.

v2.23.0 | Report a Bug | By Email