by the time layer 7 is reached, there is only one address to be concerned about... or should be. if the "library" your thinking of tests reachability, then you have moved the routing function into the host - which is a much larger problem space. DISCOVER, unlike QUERY, is designed to deal with multiple replies to a question - e.g. what address(s) map to this name? whereas QUERY will take the first thing it gets back. On Mon, Jan 07, 2008 at 10:00:32AM +1300, Brian E Carpenter wrote: > Bill, > > From the layer 7 point of view, I don't see what DISCOVER > would offer in addition to getaddrinfo(). The library > I'm thinking of would also have to handle reachability > checking - and as John said, would ideally also be stateful > to avoid repeating the same timeouts. > > Brian > > On 2008-01-06 11:45, Bill Manning wrote: > > the IETF has refused to adopt the DISCOVER opcode for > >the DNS - which pretty much handles this problem. Others > >may have developed other techniques. > > > >--bill > > > > > >>As Phill H-B has implied more than once, there's scope > >>for a library on top of the socket API that takes care > >>of this once and for all. Does anyone have such a library? > >> > >> Brian -- --bill Opinions expressed may not even be mine by the time you read them, and certainly don't reflect those of any other entity (legal or otherwise). _______________________________________________ Ietf@xxxxxxxx https://www1.ietf.org/mailman/listinfo/ietf