This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[dns-wg] v6 ns/glue naming bcp
- Previous message (by thread): [dns-wg] v6 ns/glue naming bcp
- Next message (by thread): [dns-wg] v6 ns/glue naming bcp
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Peter Koch
pk at TechFak.Uni-Bielefeld.DE
Sat Sep 6 16:01:23 CEST 2003
Jim Reid wrote: > Indeed. However I wonder how much legacy IPv6 stuff exists and whether there's no "legacy IPv6" but a lot of EDNS0-unaware ("legacy") mostly IPv4 based clients, which have to deal with what fits into 512 bytes. > legacy stuff would continue with 512 byte payloads. It would see the > largely IPv4 internet just as they do right now, unless those clients > explicitly queried for (say) a AAAA record. 1886bis, currently in "AUTH48" state, instead modified all additional section processing from "add A" to "add A and AAAA". > compatibility for the probably small installed base of existing IPv6 > devices with resolvers that can't or won't be upgraded. I agree that the currently installed base of IPv6 hosts could be required to change, but I'm not concerned about those anyway. > there aren't any? Maybe it's something like that which accounts for > the high AAAA and A6 query rate you're seeing. Exactly. Most of these queries are for a single nameserver's name, which only has A but no AAAA and even less A6. -Peter
- Previous message (by thread): [dns-wg] v6 ns/glue naming bcp
- Next message (by thread): [dns-wg] v6 ns/glue naming bcp
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]