RFC 4993, "A Lightweight UDP Transfer Protocol for the Internet Registry Information Service", August 2007Source of RFC: crisp (app)
See Also: RFC 4993 w/ inline errata
Errata ID: 1010
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2007-09-09
Verifier Name: Alexey Melnikov
Date Verified: 2010-07-07
Section 3.1.5 says:
The first paragraph of Section 3.1.5, on page 97of RFC 4993, says: | A payload type with version information ('vi') MUST be conformant to the XML defined in  and use the <versions> element as the root element.
It should say:
| A payload type with version information ('vi') sent from the server | to the client MUST be conformant to the XML defined in  and use the <versions> element as the root element.
As mentioned in other places of the text, this requirements language
is improper because it is intended to allow clients to send this
type of chunk as well, with unspecified (perhaps empty) content,
to be ignored by the server.
Note: This issue is a replication of the issue detailed in item (A.3)
for RFC 4992.