Re: NULL

Ned Freed <NED@sigurd.innosoft.com> Wed, 19 October 1994 04:08 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa18536; 19 Oct 94 0:08 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa18532; 19 Oct 94 0:08 EDT
Received: from dimacs.rutgers.edu by CNRI.Reston.VA.US id aa26021; 19 Oct 94 0:08 EDT
Received: by dimacs.rutgers.edu (5.59/SMI4.0/RU1.5/3.08) id AA26836; Tue, 18 Oct 94 23:40:46 EDT
Received: from SIGURD.INNOSOFT.COM by dimacs.rutgers.edu (5.59/SMI4.0/RU1.5/3.08) id AA26832; Tue, 18 Oct 94 23:40:45 EDT
Received: from SIGURD.INNOSOFT.COM by SIGURD.INNOSOFT.COM (PMDF V4.4-0 #2001) id <01HIFD1EJGHC8ZEKJJ@SIGURD.INNOSOFT.COM>; Tue, 18 Oct 1994 20:40:27 -0700 (PDT)
Date: Tue, 18 Oct 1994 20:39:39 -0700 (PDT)
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Ned Freed <NED@sigurd.innosoft.com>
Subject: Re: NULL
In-Reply-To: Your message dated "Tue, 18 Oct 1994 11:06:28 +0100" <"relay1.pip.790:18.09.94.10.06.42"@pipex.net>
To: Tim Goodwin <tim@pipex.net>
Cc: ietf-822@dimacs.rutgers.edu
Message-Id: <01HIFO8FCZ8E8ZEKJJ@SIGURD.INNOSOFT.COM>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT
References: <199410180659.CAA06187@wilma.cs.utk.edu>

> It would also be useful to hear from any implementors of RFC-1652: do
> they, in fact, "preserve all bits in each octet passed using the DATA
> command"?

PMDF handles NULs just fine and doesn't lose them, but this is easy given
that PMDF uses counted strings rather than null terminated strings throughout.

					Ned