At 1:22 +0100 3/21/06, Peter Koch wrote:
Dear WG,
1) develop or review guidelines for chosing zone configuration
parameters that affect inter-server or server-resolver communication,
including but not limited to SOA RR parameters, TTL values, and glue
information
2) develop or review guidelines for any DNSSEC specific operational
parameters, such as key length or key validity periods
3) develop or review operational guidelines that address the specifics of
IPv4/v6 coexistence and transition
4) review the use of existing DNS frameworks (SRV, DDDS) in other protocols,
especially focussing on operational consequences and scalability
I would consider two other areas:
5) Resolver
6) Performance
5 - "Resolver": search approach, configuration, timing, treatment of
certain kinds of messages. "Resolver" meaning: iterating server,
stub, cache, forward, etc.
6 - Performance: derive a recommended way to establish performance
requirements and/or measurement of a server "constellation." Include
consideration of anycast clouds, etc.
The descriptions of each area are fuzzy here in an attempt to get
some brain-storming on this.
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis +1-571-434-5468
NeuStar
Nothin' more exciting than going to the printer to watch the toner drain...
.
dnsop resources:_____________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html
mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html