IETF Logo Mail Archive

example TLH (was: Appeal against IESG blocking DISCUSS on draft-klensin-rfc2821bis)

"Frank Ellermann" <nobody@xyzzy.claranet.de> Tue, 17 June 2008 20:41 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 CEA7928C115; Tue, 17 Jun 2008 13:41:07 -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 1F12E3A6828 for <ietf@core3.amsl.com>; Tue, 17 Jun 2008 13:41:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.881
X-Spam-Level:
X-Spam-Status: No, score=-3.881 tagged_above=-999 required=5 tests=[AWL=-0.282, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 g4QRbT-EdHR2 for <ietf@core3.amsl.com>; Tue, 17 Jun 2008 13:41:06 -0700 (PDT)
Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by core3.amsl.com (Postfix) with ESMTP id E893D3A6ABE for <ietf@ietf.org>; Tue, 17 Jun 2008 13:41:05 -0700 (PDT)
Received: from list by ciao.gmane.org with local (Exim 4.43) id 1K8hzw-0004fC-Q7 for ietf@ietf.org; Tue, 17 Jun 2008 20:41:48 +0000
Received: from hmbg-d9b88e3e.pool.mediaways.net ([217.184.142.62]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <ietf@ietf.org>; Tue, 17 Jun 2008 20:41:48 +0000
Received: from nobody by hmbg-d9b88e3e.pool.mediaways.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for <ietf@ietf.org>; Tue, 17 Jun 2008 20:41:48 +0000
X-Injected-Via-Gmane: http://gmane.org/
To: ietf@ietf.org
From: Frank Ellermann <nobody@xyzzy.claranet.de>
Subject: example TLH (was: Appeal against IESG blocking DISCUSS on draft-klensin-rfc2821bis)
Date: Tue, 17 Jun 2008 22:43:33 +0200
Organization: <http://purl.net/xyzzy>
Lines: 33
Message-ID: <g397i3$t9t$1@ger.gmane.org>
References: <8832006D4D21836CBE6DB469@klensin-asus.vbn.inter-touch.net><485590E2.3080107@gmail.com><p06250116c47c330c7dd0@[75.145.176.242]><4856DE3A.3090804@gmail.com><g36r20$bgq$1@ger.gmane.org> <48575B7E.9030003@ca.afilias.info><87hcbse7du.fsf@mocca.josefsson.org> <5F8E4A149B8E771FC608EAFB@klensin-asus.vbn.inter-touch.net>
Mime-Version: 1.0
X-Complaints-To: usenet@ger.gmane.org
X-Gmane-NNTP-Posting-Host: hmbg-d9b88e3e.pool.mediaways.net
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1914
X-mimeole: Produced By Microsoft MimeOLE V6.00.2800.1914
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
List-Id: IETF Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ietf>
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

John C Klensin wrote:

> hypothesize that, at some point, an RFC 2606bis might be created
> (and go through the consensus process to BCP) that offers special
> reserved names for newsgroups or mailing lists as well as domain
> names

JFTR, with respect to newsgroups that is already specified in
http://tools.ietf.org/html/draft-ietf-usefor-usefor-12#section-3.1.4

| The following <newsgroup-name>s are reserved and MUST NOT be used as
| the name of a newsgroup:
|
| o  Groups whose first (or only) <component> is "example"

The (unnumbered) NetNews standard does not go into details for
which purpose the "example"-names are reserved, but I think it
is obvious.  The plan was to discuss such details in a separate
NetNews BCP later if needed.

> a reasonable reader might have trouble figuring out whether
> the footnote/reference anchor was part of the IMAP syntax
> and example or not.

+1  A consistent footnote style can be fine in Web pages, PDFs,
and similar document formats, but it is unsuited for the ASCII
text/plain xml2rfc output format(s).  

In the case of ABNF a single space could turn a clear concept into incomprehensible gibberish if the RFC line length limits
don't agree with adding this space. 

 Frank

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

v2.23.0 | Report a Bug | By Email