IETF Logo Mail Archive

Re: 8bit & i18n (was Re: ietf-nntp My notes ...)

Brian Hernacki <bhern@netscape.com> Thu, 19 December 1996 03:25 UTC

Received: from cnri by ietf.org id aa17021; 18 Dec 96 22:25 EST
Received: from ACADEM2.ACADEM.COM by CNRI.Reston.VA.US id aa01844; 18 Dec 96 22:25 EST
Received: (from majordomo@localhost) by academ2.academ.com (8.8.3/8.7.3) id VAA11630 for ietf-nntp-outgoing; Wed, 18 Dec 1996 21:22:00 -0600 (CST)
X-Authentication-Warning: academ2.academ.com: majordomo set sender to owner-ietf-nntp using -f
Received: from academ.com (root@ACADEM.COM [198.137.249.2]) by academ2.academ.com (8.8.3/8.7.3) with ESMTP id VAA11625 for <ietf-nntp@ACADEM2.ACADEM.COM>; Wed, 18 Dec 1996 21:21:58 -0600 (CST)
Received: from r2d2.mcom.com (h-205-217-237-47.netscape.com [205.217.237.47]) by academ.com (8.8.3/8.7.1) with ESMTP id VAA06439 for <ietf-nntp@academ.com>; Wed, 18 Dec 1996 21:21:56 -0600 (CST)
Received: from dredd.mcom.com (dredd.mcom.com [205.217.237.54]) by r2d2.mcom.com (8.7.5/8.7.3) with ESMTP id TAA26728 for <ietf-nntp@academ.com>; Wed, 18 Dec 1996 19:21:20 -0800 (PST)
Received: from ventnor.mcom.com ([207.1.137.53]) by dredd.mcom.com (Netscape Mail Server v2.02) with SMTP id AAA21524; Wed, 18 Dec 1996 19:21:18 -0800
Message-ID: <32B8B4E5.659D@netscape.com>
Date: Wed, 18 Dec 1996 19:22:13 -0800
From: Brian Hernacki <bhern@netscape.com>
Organization: Netscape, Floating Point Division
X-Mailer: Mozilla 3.0GoldC (X11; U; SunOS 5.5 sun4u)
MIME-Version: 1.0
To: Anthony Talltree <aad@nwnet.net>
CC: ietf-nntp@academ.com
Subject: Re: 8bit & i18n (was Re: ietf-nntp My notes ...)
References: <Pine.SOL.3.95.961218161124.14276O-100000@eleanor.innosoft.com> <Ami_lLP0I0om02HJw0@nwnet.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-nntp@academ.com
Precedence: bulk

Anthony Talltree wrote:
> 
> While we're at it, should/can we address the issue of what is and isn't
> a valid newsgroup name?  I've seen newsgroups created with ' in their
> name, and Microsoft has ones with &.  Less critical are the use of
> non-lowercase & numeric components and their lengths.

A good start would be the specification in son-of-1036. It is pretty
precise and list some of the historical reasons for certain
limitations.  

http://www.ifi.uio.no/~larsi/notes/son-of-rfc1036.txt

--brian

v2.8.7 | Report a Bug | By Email