On Tue, Feb 21, 2006 at 01:18:50PM +0100, Olaf M. Kolkman wrote:
to deal with. Most particular the middleboxes like load balancers should know about protocol extensions such as EDNS0 and DNSSEC.
I understand that this document is IPv6 specific but maybe being a little more generic here might help implementors to realize they have to do more.
I'm a bit afraid of losing focus here. This started as a survey of systems not properly serving AAAA RRs, then additional v6 considerations were added and now EDNS0 is on the table. While all these are serious operational issues, we might want to address them separately or point to and combine efforts which already deal with them. For example, there's work underway dealing with EDNS0 in the IETF and everyone here will be invited to contribute. For David's work there's the IPJ article including the reference to RFC 4074. What else is needed? It might help to continue these surveys, but we'd need to see what we're going to measure. o There are some old or problematic implementations out there and it might be the vendors (for fixes) or the operators (for upgrades) or both that need to become aware. Do we want to identify these implementations (-> fingerprinting) or their distribution? Who's going to do that? o Who's our target? End users/site administrators running name servers? ISPs? Registrars? Registries? {a possible recommendation _could_ be to include in DNS checks the correct server behaviour against AAAA queries} o There's also the middlebox issue (both vendors and operators), which already bites us with EDNS0. Again, who is the target? -Peter