@techreport{ietf-dnsop-parent-sig-00,
    number =    {draft-ietf-dnsop-parent-sig-00},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ietf-dnsop-parent-sig/00/},
    author =    {Miek Gieben and Miek Gieben and Ted Lindgreen},
    title =     {{Parent's SIG over child's KEY}},
    pagetotal = 0,
    year =      2001,
    month =     jan,
    day =       25,
    abstract =  {When dealing with large amounts of keys the procedures to update a zone and to sign a zone need to be clearly defined and practically possible. The current idea is to have the KEY RR and the parent's SIG to reside in the child's zone and perhaps also in the parent's zone. We feel that this would lead to very complicated procedures for large TLD's. We propose a alternative scheme in which the parent zone stores the parent's signature over the child's key and also a copy of the child's key itself. The advantage of this proposal is that all signatures signed by a key are in the same zone file as the producing key. This allows for a simple key rollover and resigning mechanism. For large TLD's this is extremely important. We further discuss the impact on a secure aware resolver/forwarder.},
}