Re: my 2 cents worth

Ian Duncan <id@cc.mcgill.ca> Tue, 07 June 1994 23:37 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa20508; 7 Jun 94 19:37 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa20504; 7 Jun 94 19:37 EDT
Received: from PO3.ANDREW.CMU.EDU by CNRI.Reston.VA.US id aa20723; 7 Jun 94 19:37 EDT
Received: (from postman@localhost) by po3.andrew.cmu.edu (8.6.7/8.6.6) id TAA08444; Tue, 7 Jun 1994 19:33:37 -0400
Received: via switchmail for ietf-pop3+@andrew.cmu.edu; Tue, 7 Jun 1994 19:33:37 -0400 (EDT)
Received: from po3.andrew.cmu.edu via qmail ID </afs/andrew.cmu.edu/service/mailqs/q002/QF.4hxECWi00UdbMUsU4j>; Tue, 7 Jun 1994 19:32:50 -0400 (EDT)
Received: from sifon.CC.McGill.CA (sifon.CC.McGill.CA [132.206.27.10]) by po3.andrew.cmu.edu (8.6.7/8.6.6) with ESMTP id TAA08413 for <ietf-pop3+@andrew.cmu.edu>; Tue, 7 Jun 1994 19:32:47 -0400
Received: from java.cc.mcgill.ca (java.CC.McGill.CA [132.206.35.22]) by sifon.CC.McGill.CA (8.6.8/8.6.6) with SMTP id TAA16262 for <ietf-pop3+@andrew.cmu.edu>; Tue, 7 Jun 1994 19:32:47 -0400
Date: Tue, 7 Jun 1994 19:32:46 -0400 (EDT)
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Ian Duncan <id@cc.mcgill.ca>
Subject: Re: my 2 cents worth
To: POP3 IETF Mailing List <ietf-pop3+@andrew.cmu.edu>
In-Reply-To: <chxDN7O00WBw010MI_@andrew.cmu.edu>
Message-ID: <Pine.3.89.9406071932.F16154-0100000@java.cc.mcgill.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Tue, 7 Jun 1994, John Gardiner Myers wrote:
> I also see no advantage to encoding the uid's in base64.  I would see
> an advantage to limiting their length, but on the other hand it is
> useful for servers to be able to use the contents of the Message-ID:
> header when it is assured such a header will exist.

Perhaps you're right. My suggestion started from wanting a very compact
value that could be carried in the LIST result. A subject for another 
day. 

I do think, for the sake of client writers, some care in making it easy to
manipulate is worthwhile. All a server ever needs to do is keep it unique
and spit them out when requested. For it to be useful on a client they
need to be managed in some sort of efficiently searchable form. 

   ...   ian   <id@cc.mcgill.ca>
Ian Duncan  ---  McGill University Computing Centre  ---  +.514.398.3710