Subject: Re: [apps-discuss] [Editorial Errata Reported] RFC2849 (3646)

From: Barry Leiba <[email-masked]>
Date: Wed, 19 Jun 2013 11:12:58 -0400

The following errata report (which is about RFC 2849, in "Notes on
LDIF Syntax", note 4 (page 6)) seems correct to me.  "SAFE-UTF8-CHAR"
and "SAFE-INIT-UTF8-CHAR" are not defined in the ABNF, and it looks
like the note:

      4)  Any dn or rdn that contains characters other than those
          defined as "SAFE-UTF8-CHAR", or begins with a character other
          than those defined as "SAFE-INIT-UTF8-CHAR", above, MUST be
          base-64 encoded.  Other values MAY be base-64 encoded.  Any
          value that contains characters other than those defined as
          "SAFE-CHAR", or begins with a character other than those
          defined as "SAFE-INIT-CHAR", above, MUST be base-64 encoded.
          Other values MAY be base-64 encoded.

...was meant to use "SAFE-CHAR" and "SAFE-INIT-CHAR" in both sections
of the note (about dn or rdn, and about other values).

Does anyone here have comments about this report?  Does anyone think
it is *not* correct?

Barry, Applications AD

On Tue, Jun 11, 2013 at 7:12 AM, RFC Errata System
<[email-masked]> wrote:
> The following errata report has been submitted for RFC2849,
> "The LDAP Data Interchange Format (LDIF) - Technical Specification".
>
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=2849&eid=3646
>
> --------------------------------------
> Type: Editorial
> Reported by: Boris Kleint <[email-masked]>
>
> Section: Notes on LDI
>
> Original Text
> -------------
> Any dn or rdn that contains characters other than those
> defined as "SAFE-UTF8-CHAR", or begins with a character other
> than those defined as "SAFE-INIT-UTF8-CHAR",
>
> Corrected Text
> --------------
> Any dn or rdn that contains characters other than those
> defined as "SAFE-CHAR", or begins with a character other
> than those defined as "SAFE-INIT-CHAR",
>
> Notes
> -----
>
>
> Instructions:
> -------------
> This errata is currently posted as "Reported". If necessary, please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party (IESG)
> can log in to change the status and edit the report, if necessary.
>
> --------------------------------------
> RFC2849 (draft-good-ldap-ldif-06)
> --------------------------------------
> Title               : The LDAP Data Interchange Format (LDIF) - Technical Specification
> Publication Date    : June 2000
> Author(s)           : G. Good
> Category            : PROPOSED STANDARD
> Source              : IETF - NON WORKING GROUP
> Area                : N/A
> Stream              : IETF
> Verifying Party     : IESG