RFC Errata
Found 2 records.
Status: Reported (1)
RFC 4452, "The "info" URI Scheme for Information Assets with Identifiers in Public Namespaces", April 2006
Source of RFC: IETF - NON WORKING GROUPArea Assignment: app
Errata ID: 7674
Status: Reported
Type: Technical
Publication Format(s) : TEXT
Reported By: Fabian Cohen
Date Reported: 2023-10-11
Section 4.1 says:
info-URI = info-scheme ":" info-identifier [ "#" fragment ]
It should say:
info-URI = info-scheme ":" info-identifier [ "#" Absolute]
Notes:
In practice, it is possible to generate a URI reference to a relative path of a web service. But in many cases, problems exist in resolving names and reverse name resolution.
Problems exist in the journal/truncated information of the relative URL (e.g., thomas-signe.co).
Good practice/compliance is to use the absolute path and correct reference in the Root Domain and reverse lookup.
Status: Held for Document Update (1)
RFC 4452, "The "info" URI Scheme for Information Assets with Identifiers in Public Namespaces", April 2006
Source of RFC: IETF - NON WORKING GROUPArea Assignment: app
Errata ID: 2700
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Mykyta Yevstifeyev
Date Reported: 2011-02-01
Held for Document Update by: Pete Resnick
Section 10.1 says:
[RFC4395] Hansen, T., Hardie, T., and L. Masinter, "Guidelines and Registration Procedures for New URI Schemes", BCP 115, RFC 4395, February 2006.
It should say:
[RFC4395] 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