IETF Logo Mail Archive

[Ltru] "666 Marked meta-spam" (was Route 66)

r&d afrac <rd@afrac.org> Sat, 15 October 2005 12:52 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EQlW6-0004Tf-Iq; Sat, 15 Oct 2005 08:52:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EQlW5-0004Ta-F2 for ltru@megatron.ietf.org; Sat, 15 Oct 2005 08:52:01 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA08395 for <ltru@ietf.org>; Sat, 15 Oct 2005 08:51:55 -0400 (EDT)
Received: from montage.altserver.com ([63.247.74.122]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EQlh0-0003D1-1R for ltru@ietf.org; Sat, 15 Oct 2005 09:03:19 -0400
Received: from ver78-2-82-241-91-24.fbx.proxad.net ([82.241.91.24] helo=jfc.afrac.org) by montage.altserver.com with esmtpa (Exim 4.44) id 1EQlVq-0005Ty-IS; Sat, 15 Oct 2005 05:51:46 -0700
Message-Id: <6.2.3.4.2.20051015124601.0355e4d0@mail.afrac.org>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.3.4
Date: Sat, 15 Oct 2005 13:25:59 +0200
To: LTRU Working Group <ltru@ietf.org>
From: r&d afrac <rd@afrac.org>
In-Reply-To: <002f01c5d140$85a01460$030aa8c0@DEWELL>
References: <20051014220102.RDGT29651.edge4.adelphia.net@megatron.ietf.org> <002f01c5d140$85a01460$030aa8c0@DEWELL>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - montage.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - afrac.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Subject: [Ltru] "666 Marked meta-spam" (was Route 66)
X-BeenThere: ltru@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Language Tag Registry Update working group discussion list <ltru.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ltru>
List-Post: <mailto:ltru@ietf.org>
List-Help: <mailto:ltru-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ltru>, <mailto:ltru-request@ietf.org?subject=subscribe>
Sender: ltru-bounces@ietf.org
Errors-To: ltru-bounces@ietf.org

At 06:25 15/10/2005, Doug Ewell wrote:
>Misha Wolf <Misha dot Wolf at reuters dot com> wrote:
>
> > Will we ask for a number ending in 66?  If so, for which of the RFCs?
>
>I understand that the RFC Editor is solely responsible for issuing RFC
>numbers, and can pick any number imaginable.  I don't suppose it would
>hurt to ask, though, keeping the 1766 -> 3066 legacy in mind.

Dear all,
I cannot object "Route 66" is not a perfect name concept for the 
American Globalization document which, at perfect time, sides the 
IESG with the USG's positions to the eyes of the world.

Genuine arrogance or total inconsciousness, such a thread does not 
help pretending the IETF is multicultural/multinational. Why not to 
add St John the Evangelist among the authors and to wait for the RFC 
4666 number? It would be perfect mnemonic for the world to think of 
contents, protocols, Google searches leaking cultural/racial readers' 
characteristics as "4666 Marked".
jfc  


_______________________________________________
Ltru mailing list
Ltru@ietf.org
https://www1.ietf.org/mailman/listinfo/ltru

v2.23.0 | Report a Bug | By Email