Antoin says:
So there's one more logical entity involved; most likely this way:
vvvvvvvvvvvvvvv vvvvvvvvvvvvv
dns_op(parent)-registry-registrar-reseller-registrant-dns_op(child)
The dns_op(child) might alternatively have a direct contractual
relationship with the reseller, registrar, or even registry instead
-- depending on business model, regulation, location in the DNS tree,
etc.
Many of {registrant, reseller, registrar} will not be interested
in tracing or even seeing the DNSSEC 'anchor' data passing by,
etc.
This type of reasoning implies that there is an (implicit) model
of business relarionships. I do think that we want a protocol which
doesn't not imply a certain model and can therefore be can used in
multiple situations.
jaap
_______________________________________________
DNSOP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dnsop
