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
Fri Sep 5 19:36:20 CEST 2003
>>>>> "Peter" == Peter Koch <pk at TechFak.Uni-Bielefeld.DE> writes: >> A and AAAA should use the same namespace. Peter> apart from this more general statement, which I agree with, Peter> separating namespaces would cost more precious octets in Peter> the packet. I wonder if saving the odd octet here and there to squeeze stuff into a 512 byte payload is really the best approach. It is wise to apply the constraints of 1980's DNS to the world of IPv6 in the 21st century? This seems to be storing up trouble for the future and could make it awkward to get reasonable amounts of IPv6 glue deployed. How feasible would it be to mandate or recommend that IPv6-aware DNS clients use EDNS0 to get bigger payloads and complete glue RRsets? Could we just say "use EDNS0" and be done with it?
- 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 ]