Andrew,
Yes, RDDS is aware of the data but not of all the business rules that is needed
to support the SRS. RDDS is a lookup protocol and just because there is one or
some implementations out there that have included additional logic does not
mean that it is a standard that “we” need to conform to. We need to keep the
SRS logic in the SRS and leave RDDS to strictly a lookup protocol.
--
JG
James F. Gould
Distinguished Engineer
Verisign
jgo...@verisign.com
On 12/7/16, 12:04 PM, "regext on behalf of Andrew Sullivan"
<regext-boun...@ietf.org on behalf of a...@anvilwalrusden.com> wrote:
On Wed, Dec 07, 2016 at 03:30:24PM +0000, Gould, James wrote:
> It sounds like you’re attempting to morph RDDS into the SRS.
Nope.
>RDDS is a lookup service and the SRS is an OLTP system. A lookup
> service either has the data or it doesn’t. Extra business logic
> associated with availability (variant blocking, relationship
> blocking, reserved domains, etc.) should be left to the appropriate
> channel which is the SRS and not RDDS.
Also nope. The idea that the Registration Data Directory Service
doesn't have knowledge about the Registration Data such that the
repository policies are a secret from the RDDS strikes me as at least
unintuitive. Moreover, since one RDDS service (whois) already
actually has mechanisms for communicating such information today at
least in some implementations, we have running code that we need to
conform to.
Best regards,
A
--
Andrew Sullivan
a...@anvilwalrusden.com
_______________________________________________
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext
_______________________________________________
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext
