RFC Errata
Found 6 records.
Status: Verified (1)
RFC 7483, "JSON Responses for the Registration Data Access Protocol (RDAP)", March 2015
Note: This RFC has been obsoleted by RFC 9083
Source of RFC: weirds (app)
Errata ID: 4503
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Scott Hollenbeck
Date Reported: 2015-10-14
Verifier Name: Barry Leiba
Date Verified: 2016-01-21
Section 5.2 and 5.3 says:
In Section 5.2: "ldhName" : "ns1.xn--fo-5ja.example", "unicodeName" : "ns1.foo.example", In Section 5.3: "ldhName" : "xn--fo-5ja.example", "unicodeName" : "foo.example", "ldhName" : "xn--fo-cka.example", "unicodeName" : "foo.example" "ldhName" : "xn--fo-fka.example", "unicodeName" : "foo.example" "ldhName": "xn--fo-8ja.example", "unicodeName" : "foo.example"
It should say:
In Section 5.2: "ldhName" : "ns1.xn--fo-5ja.example", "unicodeName" : "ns1.fóo.example", In Section 5.3: "ldhName" : "xn--fo-5ja.example", "unicodeName" : "fóo.example", "ldhName" : "xn--fo-cka.example", "unicodeName" : "fõo.example" "ldhName" : "xn--fo-fka.example", "unicodeName" : "föo.example" "ldhName" : "xn--fo-8ja.example", "unicodeName" : "fôo.example"
Notes:
The unicodeName examples in RFC 7483 are invalid per RFC 5890. Here's an example from Section 5.2 on page 23:
"unicodeName" : "ns1.foo.example",
Section 3 of 7483 says this about Unicode names:
"Unicode names: Textual representations of DNS names where one or more of the labels are U-labels as described by [RFC5890]."
5890 says: "A "U-label" is an IDNA-valid string of Unicode characters, in Normalization Form C (NFC) and including at least one non-ASCII character, expressed in a standard Unicode Encoding Form (such as UTF-8)."
The examples in 7483 contain all ASCII characters. Syntactically valid examples are shown in the corrected text.
Status: Reported (5)
RFC 7483, "JSON Responses for the Registration Data Access Protocol (RDAP)", March 2015
Note: This RFC has been obsoleted by RFC 9083
Source of RFC: weirds (app)
Errata ID: 4980
Status: Reported
Type: Technical
Publication Format(s) : TEXT
Reported By: Scott Hollenbeck
Date Reported: 2017-03-24
Section 5.5 says:
country -- a string containing the name of the two-character country code of the autnum
It should say:
country -- a string containing the two-character country code of the autnum
Notes:
As described in Section 3, country codes should consistently be represented as two-character string values. Note that this differs from the "full name" format used in jCard representations of entity objects.
Errata ID: 5667
Status: Reported
Type: Technical
Publication Format(s) : TEXT
Reported By: Andrew Newton
Date Reported: 2019-03-22
Section 4.8 says:
identifier -- a public identifier of the type denoted by "type"
It should say:
identifier -- a string denoting a public identifier of the type
related to "type"
Notes:
While the example given in section 4.8 shows "identifier" being a string, the prose description does not clearly state it.
Errata ID: 6158
Status: Reported
Type: Technical
Publication Format(s) : TEXT
Reported By: Scott Hollenbeck
Date Reported: 2020-05-06
Section 10.2.3 says:
Description: The object instance was transferred from one registrant to another.
It should say:
Description: The object instance was transferred from one registrar to another.
Notes:
I believe the corrected text is what was intended for this particular registry value, and is what is being implemented by operators today. Registrant-to-registrant transfers are also possible, but they're not performed using EPP and are not logged as an event action. The text in the RFC should be changed and the description of the action in the IANA registry should also be changed.
Errata ID: 4859
Status: Reported
Type: Editorial
Publication Format(s) : TEXT
Reported By: Marcos Sanz
Date Reported: 2016-11-10
Section 5.3 says:
"network" :
{
"objectClassName" : "ip network",
"handle" : "XXXX-RIR",
"startAddress" : "192.0.2.0",
"endAddress" : "192.0.2.255",
"ipVersion" : "v6",
It should say:
"network" :
{
"objectClassName" : "ip network",
"handle" : "XXXX-RIR",
"startAddress" : "192.0.2.0",
"endAddress" : "192.0.2.255",
"ipVersion" : "v4",
Errata ID: 5666
Status: Reported
Type: Editorial
Publication Format(s) : TEXT
Reported By: Andrew Newton
Date Reported: 2019-03-22
Section 3 says:
handle: DNRs and RIRs have registry-unique identifiers that
may be used to specifically reference an object
instance. The semantics of this data type as found
in this document are to be a registry-unique
reference to the closest enclosing object where the
value is found. The data type names "registryId",
"roid", "nic-handle", "registrationNo", etc., are
terms often synonymous with this data type. In
this document, the term "handle" is used. The term
exposed to users by clients is a presentation issue
beyond the scope of this document.
It should say:
handle: DNRs and RIRs have registry-unique identifiers that
may be used to specifically reference an object
instance. The semantics of this data type as found
in this document are to be a registry-unique
reference to the closest enclosing object where the
value is found. The data type names "registryId",
"roid", "nic-handle", "registrationNo", etc., are
terms often synonymous with this data type. In
this document, the term "handle" is used. The term
exposed to users by clients is a presentation issue
beyond the scope of this document. This value is a
simple string.
Notes:
All uses of handle in section 5 call "handle" out as being a string, but if a reader were to only read section 3 they would not know it.