[council] Proposed resolution in response to Stuart Lynn's request

[Bruce Tonkin <Bruce.Tonkin@melbourneit.com.au>]

Hello Elisabeth,

Following the discussion during the names council teleconference on 26 Sept
2002 on your proposed resolution, I recommend you consider the following
resolution that is derived 
from your whereas clause 10, and resolution (c).  The resolution focuses
only on the technical issues, and does not seek at this stage to define the
policies for who is responsible for carrying out certain checks.  The policy
discussion should follow after the technical work is done.  I note the
general DNS principle that at any point in the hierarchy there is a joint
relationship between the parent and child, and the parent has a
responsibility to ensure that information held about the child at the
parent's level is correct.

Here is the proposed resolution:


Whereas the stability of the DNS depends on the quality of the nameserver
information contained in the zones at all levels of the DNS hierarchy.

Whereas Stuart Lynn and Vint Cerf have written to the Names Council 
on 21 September seeking the opinion of the Names Council on the 
suggestion to ask the Committee on Security and Stability
(http://www.icann.org/committees/security/) to develop a recommendation on
the most sound technical practices to follow to improve the DNS data quality
at all levels in the system,
http://www.icann.org/correspondence/cerf-lynn-letter-to-names-council-20sep0
2.htm

The Names Council resolves that:
The ICANN Board should ask the Committee on Security and Stability to work
cooperatively with IANA, the TLD managers, and registrars, to develop a
recommendation on the most sound technical practices to follow to improve
the DNS data quality at all levels of the DNS hierarchy.


Regards,
Bruce Tonkin