RFC 5731 3.1.1 seems to clearly prevent a to be sent when
avail="1".
But RFC 9095 6.1.1 has an example with a for avail="1".
So, is it really forbidden to send a to the client when the
domain is available but you want to send some extra conditions?
Hello,
On 9/29/21 13:01, Stephane Bortzmeyer wrote:
> RFC 5731 3.1.1 seems to clearly prevent a to be sent when
> avail="1".
>
> But RFC 9095 6.1.1 has an example with a for avail="1".
>
> So, is it really forbidden to send a to the client when the
> domain is available but you want to send
I would be more concerned about injecting domain names into the check response
that were not queried for in the command than the inclusion of the optional
reason element to explain why the domain name was added. I looked at the
approach taken with a similar extension, which is the Related Domai
The IESG has received a request from the Registration Protocols Extensions WG
(regext) to consider the following document: - 'Finding the Authoritative
Registration Data (RDAP) Service'
as Internet Standard
The IESG plans to make a decision in the next few weeks, and solicits final
comments o
