Parental Agent side of draft-ietf-dnsop-dnssec-bootstrapping implemented at deSEC.io?

Hi,

section 5 mentions

that you implemented the child DNS-operator side.

Did you also implement the parental agent side in case someone has a child domain whose parent is located at deSEC or do we have to create DS records at the parent for childs manually?

Currently we have no concrete plans of an parental agent implementation at deSEC, but we are certainly open to this. As of now, DS records have to be created manually.

However deSEC does maintain a proof-of-concept implementation of parental-side scanning.