IETF Logo Mail Archive

Re: empty quoted strings and other oddities

"Gary Feldman" <gaf@ziplink.net> Wed, 02 October 2002 12:31 UTC

Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id g92CV5L17111 for ietf-822-bks; Wed, 2 Oct 2002 05:31:05 -0700 (PDT)
Received: from relay-2.ziplink.net (relay-2.ziplink.net [206.15.168.82]) by above.proper.com (8.11.6/8.11.3) with ESMTP id g92CV3v17107 for <ietf-822@imc.org>; Wed, 2 Oct 2002 05:31:04 -0700 (PDT)
Received: from alice (reston-ip-206136-183.dynamic.ziplink.net [206.15.136.183]) by relay-2.ziplink.net (8.11.6+Sun/8.10.2) with SMTP id g92CUrv02863 for <ietf-822@imc.org>; Wed, 2 Oct 2002 08:30:55 -0400 (EDT)
Message-ID: <002001c26a0f$f05437a0$b7880fce@alice>
From: Gary Feldman <gaf@ziplink.net>
To: ietf-822@imc.org
References: <200210011513.g91FDk027592@astro.cs.utk.edu>
Subject: Re: empty quoted strings and other oddities
Date: Wed, 02 Oct 2002 08:33:36 -0400
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Sender: owner-ietf-822@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-822/mail-archive/>
List-ID: <ietf-822.imc.org>
List-Unsubscribe: <mailto:ietf-822-request@imc.org?body=unsubscribe>

>From: "Keith Moore" <moore@cs.utk.edu>
>Sent: Tuesday, October 01, 2002 11:13 AM

> > 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.

I'm not sure I buy that reasoning.  You seem to be saying that since it's
not possible to detect all invalid addresses syntactically that the ability
to trap some syntactically (or more than currently trapped) is irrelevant.
I disagree.  I believe it's usually faster, simpler, and more reliable to
catch errors syntactically than relying on subsequent semantics.

Gary

v2.23.0 | Report a Bug | By Email