> comment from EBW (apparently his posts have fallen into a moderator's
> queue ...
i'm moving up in the world, but i'm still as dumb as a carp. there isn't
any chance that "parent" and "server" are used interchangably, as the
registry may be the sink for data describing an arbitrary sub-delegation
from some root, and parent and child w.r.t. that arbitrary point.
> 1) Client says "here's my DS, sign it for just a week at a time"
> 2) Servers says "okay, but warning, I signed it for 2 years."
in the dcp vs harald's-one-bit episode of joy, the client (one bit) does
cause an error if unsatisfied, not a warning.
> There's no undoing the publication of a record, you can pull it, but
> someone out there can copy it first and use it in replays. Akin to
> "privacy", it's hard to rescind information once it goes out, so we
> now think we want to play it conservatively.
<complexType name="dcpRetentionType">
<choice>
<element name="business"/>
<element name="indefinite"/>
<element name="legal"/>
<element name="none"/>
<element name="stated"/>
</choice>
</complexType>
this only expresses the retention by the policy announcing data collector
(server), not the policy of arbitrary 3rd-parties, which may be "indefinite".
ebw
.
dnsop resources:_____________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html
mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html
