RE: [Editorial Errata Reported] RFC4013 (1812)

[<Pasi.Eronen@xxxxxxxxx>]

Hmm.. it looks like there are Unicode characters that are in the
"prohibited output" list, but will get changed to another, allowed
characters during the "Map" or "Normalize" steps. 

Since "Prohibit" step is done after Map and Normalize, these
characters can actually appear in the input, right? (and this would 
not be an error)

(For example, it looks like U+0340 is prohibited by Table C.8, but
will get normalized to U+0300, which is allowed.)

So actually should the errata be something like this?

  OLD:
     This profile specifies the following characters as prohibited input:     
  NEW:
     This profile specifies the following characters as prohibited output:

 Discussion: Per RFC 3454, the check for prohibited characters
 is done after the "Map" and "Normalize" steps. Characters listed
 here are actually allowed as inputs if they get removed by the 
 "Map" or "Normalize" steps.

Best regards,
Pasi

> -----Original Message-----
> From: ext Kurt Zeilenga [mailto:Kurt@xxxxxxxxxxxx]
> Sent: 23 July, 2009 04:32
> To: Jeffrey Hutzelman
> Cc: Simon Josefsson; RFC Errata System; tim.polk@xxxxxxxx; Eronen Pasi
> (Nokia-NRC/Helsinki); tlyu@xxxxxxx; alexey.melnikov@xxxxxxxxx; ietf-
> sasl@xxxxxxx
> Subject: Re: [Editorial Errata Reported] RFC4013 (1812)
> 
> 
> On Jul 22, 2009, at 1:44 PM, Jeffrey Hutzelman wrote:
> 
> > There is, however, an error -- the first sentence of this section
> > does in fact claim to be specifying prohibited input characters.
> > The correct fix is to that text, not to the section title.
> 
> 
> I support the following errata:
> 
> OLD:
> 	prohibited input:
> 
> NEW
> 	prohibited:
> 
> 
> Discussion:
> Per RFC 3454, if a prohibited character appears in the input, an error
> must result.  That is, the prohibited characters cannot appear in the
> output.