RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

Found 6 records.

Status: Verified (3)

RFC 5092, "IMAP URL Scheme", November 2007

Source of RFC: lemonade (app)

Errata ID: 1802

Status: Verified
Type: Technical

Reported By: Tony Hansen
Date Reported: 2009-07-06
Verifier Name: Alexey Melnikov
Date Verified: 2009-07-06

Section 9 says:

   If the following relative URL is located in that body part:

      <;section=1.4>

   this could result in the following client commands:

    C: A004 UID FETCH 20 (BODY.PEEK[1.2.MIME]
                                      ^
           BODY.PEEK[1.MIME]
           BODY.PEEK[HEADER.FIELDS (Content-Location)])

It should say:

   If the following relative URL is located in that body part:

      <;section=1.4>

   this could result in the following client commands:

    C: A004 UID FETCH 20 (BODY.PEEK[1.4.MIME]
                                      ^
           BODY.PEEK[1.MIME]
           BODY.PEEK[HEADER.FIELDS (Content-Location)])

Notes:

1.2.MIME should read 1.4.MIME

Errata ID: 1091

Status: Verified
Type: Editorial

Reported By: Alexey Melnikov
Date Reported: 2007-12-10
Verifier Name: Alexey Melnikov
Date Verified: 2009-06-19

Section 7 says:

[URI-GEN] defines four forms of relative URLs: <inetwork-path>,
<iabsolute-path>, <irelative-path>, and <ipath-empty>.  Their syntax
is defined in Section 11.

It should say:

[URI-GEN] defines four forms of relative URLs: <network-path>,
<absolute-path>, <relative-path>, and <path-empty>.  This document
introduces more restricted, IMAP-specific syntax corresponding to
these non-terminals, <inetwork-path>, <iabsolute-path>,
<irelative-path>, and <ipath-empty>.  Their syntax is defined
in Section 11.

Notes:

[URI-GEN] doesn't define <inetwork-path>, <iabsolute-path>, <irelative-path>, and <ipath-empty>, they are defined in the RFC 5092.

The issue was identified by Alfred Hœnes <ah@tr-sys.de>, he also suggested the new text.

Errata ID: 1092

Status: Verified
Type: Editorial

Reported By: Alexey Melnikov
Date Reported: 2007-12-10
Verifier Name: Alexey Melnikov
Date Verified: 2009-06-19

In Appendix A, it says:

/* Copyright (C) The IETF Trust (2007).  This version of
   sample C code is part of RFC XXXX; see the RFC itself
   for full legal notices.

   Regarding this sample C code (or any portion of it), the authors
   make no guarantees and are not responsible for any damage
   resulting from its use.  The authors grant irrevocable permission
   to anyone to use, modify, and distribute it in any way that does
   not diminish the rights of anyone else to use, modify, and
   distribute it, provided that redistributed derivative works do
   not contain misleading author or version information.

   Derivative works need not be licensed under similar terms.
 */

It should say:

/* Copyright (C) The IETF Trust (2007).  This version of
   sample C code is part of RFC 5092; see the RFC itself
   for full legal notices.

   Regarding this sample C code (or any portion of it), the authors
   make no guarantees and are not responsible for any damage
   resulting from its use.  The authors grant irrevocable permission
   to anyone to use, modify, and distribute it in any way that does
   not diminish the rights of anyone else to use, modify, and
   distribute it, provided that redistributed derivative works do
   not contain misleading author or version information.

   Derivative works need not be licensed under similar terms.
 */

Notes:

Changed RFC XXXX to RFC 5092.

The issue was reported by Alfred Hœnes <ah@tr-sys.de>.

Status: Held for Document Update (3)

RFC 5092, "IMAP URL Scheme", November 2007

Source of RFC: lemonade (app)

Errata ID: 2699

Status: Held for Document Update
Type: Editorial

Reported By: Mykyta Yevstifeyev
Date Reported: 2011-02-01
Held for Document Update by: Alexey Melnikov

Section 13.2 says:

[URI-REG]    Hansen, T., Hardie, T., and L. Masinter, "Guidelines and
             Registration Procedures for New URI Schemes", BCP 115,
             RFC 4395, February 2006.

It should say:

[URI-REG]    Hansen, T., Hardie, T., and L. Masinter, "Guidelines and
             Registration Procedures for New URI Schemes", BCP 35,
             RFC 4395, February 2006.

Notes:

RFC 4395 is not BCP 115, but BCP 35.

Errata ID: 2802

Status: Held for Document Update
Type: Editorial

Reported By: Mykyta Yevstifeyev
Date Reported: 2011-05-08
Held for Document Update by: Pete Resnick

Throughout the document, when it says:

imap: URI scheme

It should say:

'imap' URI Scheme

Notes:

The ":" (colon) character is not a part of URI scheme name. RFC 3986 says:

URI = scheme ":" hier-part [ "?" query ] [ "#" fragment ]
scheme = ALPHA *( ALPHA / DIGIT / "+" / "-" / "." )

i. e. ":" is a delimiter between scheme name and the remainder of URI.

Errata ID: 2846

Status: Held for Document Update
Type: Editorial

Reported By: Mykyta Yevstifeyev
Date Reported: 2011-06-28
Held for Document Update by: Peter Saint-Andre

Section 11 says:

   ipath-empty     = 0<pchar>
                    ; Zero characters.
                    ; The same-document reference.

It should say:

   ipath-empty     = ""
                    ; Zero characters.
                    ; The same-document reference.

Notes:

Copying Erratum report #2033 for RFC 3986 by Tanaka Akira. "0<foo>" assumes "foo" is <pros-val> of RFC 5234, which it isn't. Given this should identify null string, "" is appropriate, in my opinion.

Report New Errata



Search RFCs
Advanced Search
×