Path: utzoo!mnetor!uunet!husc6!mailrus!ames!ucsd!sdcsvax!ucsdhub!hp-sdd!hplabs!sdcrdcf!sdcsmb!sea!eggert
From: eggert@sea.sm.unisys.com (Paul Eggert)
Newsgroups: news.admin
Subject: Re: Message-ID bugs in nntp and netnews?
Message-ID: <pQa9lz;@sea.sm.unisys.com>
Date: 12 Apr 88 17:17:01 GMT
References: <8804090600.AA14895@Larry.McRCIM.McGill.EDU> <IWMHjSy00VsLM4h7Rc@andrew.cmu.edu>
Reply-To: eggert@sea.sm.unisys.com (Paul Eggert)
Organization: Unisys Santa Monica
Lines: 21

In article <IWMHjSy00VsLM4h7Rc@andrew.cmu.edu> cfe+@andrew.cmu.edu (Craig F.
Everhart) writes:

	We went to the base-64 scheme a year or so ago because our Message-IDs
	were too long for some old netnews systems....  I'm interested in
	hearing about ... any additional constraints, other than what's
	already in RFC822.

Beware "%".  We use base 90 here, employing the following Ascii characters
(spaces denote Ascii characters that we don't use):

	 !"#$ &'()*+,-./0123456789:; = ?
	 ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_
	`abcdefghijklmnopqrstuvwxyz{|}~

The following printable characters were omitted:

	<,@,>	part of Message-ID syntax
	%	tickles a news.2.11 bug: a printf(x) should be a printf("%s",x)

Perhaps < need not be omitted?  I lack RFC822.  --paul