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 ]
Patrik Fältström
paf at cisco.com
Sat Sep 6 10:44:12 CEST 2003
How many old clients and servers do _NOT_ handle a 1400 byte packet? When was the last time you saw one? (The pix blocks it in some configuration modes I can add before you all say _T_H_E__P_I_X_...) paf On 5 sep 2003, at 19.49, Peter Koch wrote: > Jim Reid said: > >> 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? > > that might be useful but will not solve the problem. > >> Could we just say "use EDNS0" and be done with it? > > Legacy, i.e. EDNS-unaware, clients will continue to use the 512 byte > limit, > so the servers - unless they call for more load - should be > conservative > and the zone administrators should be as well. > > Related to this, IPv6 already has an impact on server load. On our > system > we already see large amounts of AAAA and A6 type queries (each roughly > 85% > of the type A count), so I'd really favor a conservative approach. > > -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 ]