Ed,
> 5 - "Resolver": search approach, configuration, timing, treatment of
> certain kinds of messages. "Resolver" meaning: iterating server,
> stub, cache, forward, etc.
that's covered in the general introductory text - and as discussed in Dallas
we'd need some terminology clarification to start with. I'd like to hear
more opinions on whether we should explicitly have a "high level work package"
like this:
5) {numbers likely to change}
develop and review guidelines for resolver (stub and full) behaviour,
including search path and timing issues as well as query strategies.
(A document actually saying that 'recursive servers' ==
'iterative resolvers' SHOULD issue queries with RD==0 only would fall
into this basket, as would probably anything around RFC1535bis)
> 6 - Performance: derive a recommended way to establish performance
> requirements and/or measurement of a server "constellation." Include
> consideration of anycast clouds, etc.
6) establish terminology and methodology for performance measurements
of servers, resolvers or the service as such.
('CNNP' comes to mind)
> The descriptions of each area are fuzzy here in an attempt to get
> some brain-storming on this.
Text change suggestions are welcome. Thanks, Ed.
-Peter
.
dnsop resources:_____________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html
mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html
