RFC Errata
RFC 5731, "Extensible Provisioning Protocol (EPP) Domain Name Mapping", August 2009
Source of RFC: IETF - NON WORKING GROUPArea Assignment: art
Errata ID: 4780
Status: Reported
Type: Editorial
Publication Format(s) : TEXT
Reported By: Romuald Brunet
Date Reported: 2016-08-18
Section 3.2.5 says:
- A <domain:registrant> element that contains the identifier for the human or organizational social information (contact) object to be associated with the domain object as the object registrant. This object identifier MUST be known to the server before the contact object can be associated with the domain object. An empty element can be used to remove registrant information. - A <domain:authInfo> element that contains authorization information associated with the domain object. This mapping includes a password-based authentication mechanism, but the schema allows new mechanisms to be defined in new schemas. A <domain: null> element can be used within the <domain:authInfo> element to remove authorization information.
It should say:
- An OPTIONAL <domain:registrant> element that contains the identifier for the human or organizational social information (contact) object to be associated with the domain object as the object registrant. This object identifier MUST be known to the server before the contact object can be associated with the domain object. An empty element can be used to remove registrant information. - An OPTIONAL <domain:authInfo> element that contains authorization information associated with the domain object. This mapping includes a password-based authentication mechanism, but the schema allows new mechanisms to be defined in new schemas. A <domain: null> element can be used within the <domain:authInfo> element to remove authorization information.
Notes:
The registrant and authinfo parameters are both optional according to the XML Schema specification.
But the text of the 3.2.5 is currently ambiguous (IMHO), and may lead to think both parameters are mandatory.