Re: empty quoted strings and other oddities

Keith Moore <> Tue, 01 October 2002 15:13 UTC

Received: (from majordomo@localhost) by (8.11.6/8.11.3) id g91FDkS08343 for ietf-822-bks; Tue, 1 Oct 2002 08:13:46 -0700 (PDT)
Received: from ( []) by (8.11.6/8.11.3) with ESMTP id g91FDjv08339 for <>; Tue, 1 Oct 2002 08:13:45 -0700 (PDT)
Received: from (localhost []) by (cf 8.9.3) with ESMTP id g91FDk027592 for <>; Tue, 1 Oct 2002 11:13:46 -0400 (EDT)
Message-Id: <>
From: Keith Moore <>
Subject: Re: empty quoted strings and other oddities
In-reply-to: (Your message of "Mon, 30 Sep 2002 23:49:10 EDT.") <>
Date: Tue, 01 Oct 2002 11:13:46 -0400
Precedence: bulk
List-Archive: <>
List-ID: <>
List-Unsubscribe: <>

> RFC 2822 permits (as did 822) a quoted string which
> consists solely of a pair of DQUOTE characters.  It's
> not clear what the semantics of that are or ought to be.

it doesn't have to have semantics, since quoted-strings
can be used in places where they are opaque.  if someone wants their 
email address to be "" this is perfectly legal.

> Likewise, a domain literal can consist solely of the
> square brackets.

so? there are lots of addresses which are valid syntax but 
not valid because the domain is not defined or the IP
address (in the domain literal) does not exist or is not
assigned to a host.