Re: draft-klensin-net-utf8-06

John C Klensin <john-ietf@jck.com> Fri, 04 January 2008 21:34 UTC

Date: Fri, 04 Jan 2008 16:34:09 -0500
From: John C Klensin <john-ietf@jck.com>
To: Bill McQuillan <McQuilWP@pobox.com>, Apps-Discusssion <discuss@apps.ietf.org>
Subject: Re: draft-klensin-net-utf8-06
Message-ID: <92F9B0A1A09F6C8A70CDBED1@p3.JCK.COM>
In-Reply-To: <50134794.20071016093853@pobox.com>
References: <93F25E18AB3DA3EB0599F092@p3.JCK.COM> <50134794.20071016093853@pobox.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Cc:
Precedence: list
Errors-To: discuss-bounces@apps.ietf.org


--On Tuesday, 16 October, 2007 09:38 -0700 Bill McQuillan
<McQuilWP@pobox.com> wrote:

> In section 2.1, I understand that the ONLY way to indicate the
> end of a line, for text parsing purposes, is the pair <CRLF>.
> Any other appearance of either CR or LF, whether or not
> allowed by a SHOULD, MUST NOT be considered to be a
> "line-ending" and only can be considered as text mark up.
> 
> For example, this<LF>
>                   sentence is a single, malformed line.<CRLF>
> 
> Right?

Certainly it is a single line.  Under the original NVT rules, it
is not malformed although it is often bad news.

> A typo: Appendix B, bullet 4, penultimate line:
> 
>   interpreted as one or spaces, but, in general, it cannot be
>                        ^
>                        more

Got it.  Thanks.


     john

Re: draft-klensin-net-utf8-06 Frank Ellermann
Re: draft-klensin-net-utf8-06 Stephane Bortzmeyer
draft-klensin-net-utf8-06 John C Klensin
Re: draft-klensin-net-utf8-06 Stephane Bortzmeyer
Re: draft-klensin-net-utf8-06 Frank Ellermann
Re: draft-klensin-net-utf8-06 John C Klensin
Re: draft-klensin-net-utf8-06 Bill McQuillan
Re: draft-klensin-net-utf8-06 Tim Bray
Re: draft-klensin-net-utf8-06 Julian Reschke
Re: draft-klensin-net-utf8-06 Frank Ellermann
Re: draft-klensin-net-utf8-06 Tony Finch
Re: draft-klensin-net-utf8-06 John C Klensin