At 09:51 AM 12/16/2005, David Blacka wrote:
On Dec 15, 2005, at 7:47 PM, Daniel Senie wrote:
The thinking is simple: if the DNS server is able to tag all
outbound packets with some uniqueness information, then there is no
ambiguity concerning tracking down which server responded. Any
mechanism that relies on a subsequent query will provide a less
than perfect indication of the server involved, as load balancing
or similar could in fact shift focus to a new server. When I've
raised this issue previously, the response has been that the result
of the subsequent query will be "good enough."
Daniel,
Are you aware of draft-ietf-dnsext-nsid-00.txt?
I wasn't. Just reviewed it. Basically is what I personally believe is
the correct and sufficient solution. That it's in the queue of
another WG does, I think, strengthen my argument that the draft under
discussion in DNSOP is in fact not a good requirements document.
.
dnsop resources:_____________________________________________________
web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html
mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html
