[Ietf-not43] 3.2.6 Escrow Support and other thoughts

[Rick Wesson]

some more edits and language suggestions.

-rick


Since 3.2.6 is out of band and out of scope lets remove it. If an entity
wishes to use the schemas defined by crisp for escrow thats fine but
escrow has requirements unto its self that may be in opposition to the
requirements under discussion.


3.2.6 Escrow Support

   The service MUST provide a means to escrow data of domain registrars
   to an escrow entity using a common schema.  This escrow capability
   SHOULD be "off-line" and "out-of-band" from the normal operations of
   the service.

3.2.9 DNS Label Referencing

Is it the intent of section 3.2.9 to require that the information now
provided via the internic port 43 referal whois be published somehow in
the DNS? If that is not the intent please reprase this section as it is
not clear as to the intent nor the requirement.

4.7 Serialization Definition

lets strike data escrow from this section, as we are not doing
requirements for data escrow. Unless we update our charter to deal with
escrow and move those requirements to a seporate document.


7. Security Considerations

Please add the following to the end of section 7. Security Considerations

This document contains requirements for the distribution of queries
against a mesh of pariticpiants and the possable generation and
distribution of index hints both of which could be used in the development
of DDoS attacks against the entire mesh or used to create data minning
effors by Direct Marketers (see Section 2.4.7)