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 ]
Jim Reid
jim at rfc1035.com
Mon Sep 8 20:23:55 CEST 2003
>>>>> "Peter" == Peter Koch <pk at TechFak.Uni-Bielefeld.DE> writes: Peter> there's no "legacy IPv6" but a lot of EDNS0-unaware Peter> ("legacy") mostly IPv4 based clients, which have to deal Peter> with what fits into 512 bytes. Indeed. This stuff mostly doesn't know or care about IPv6, so let's try to ensure they never see AAAA records or get into problems caused by truncation isses as IPv6 glue comes along. >> 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. Peter> 1886bis, currently in "AUTH48" state, instead modified all Peter> additional section processing from "add A" to "add A and Peter> AAAA". I'd not read this draft. It seems to be what I've been suggesting. Thanks for the tip 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 ]