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] Draft recommendation for limiting the EDNS0 response size on authoritative name servers
- Previous message (by thread): [dns-wg] Draft recommendation for limiting the EDNS0 response size on authoritative name servers
- Next message (by thread): [dns-wg] Draft recommendation for limiting the EDNS0 response size on authoritative name servers
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Florian Weimer
fw at deneb.enyo.de
Fri Sep 21 19:39:31 CEST 2012
* Gijs van den Broek: > Hi Florian, > >> What's your stance on atomic fragments for IPv6? > > We did not particularly consider atomic fragments. Could you be a > bit more specific? I think we've got a classical pick-any-two situation: interoperability with existing clients, statelessness in the server, and compliance with the existing specification: You can send atomic fragments if you've recently received an ICMPv6 message requesting for a particular address. This requires state in the server. You can unconditionally send atomic fragments. This breaks interoperability with existing clients. You can never send atomic fragments. This is not what the specification requires. This overlaps with concerns in your proposal because the size of the Fragmentation header might have some impact on your size calculations.
- Previous message (by thread): [dns-wg] Draft recommendation for limiting the EDNS0 response size on authoritative name servers
- Next message (by thread): [dns-wg] Draft recommendation for limiting the EDNS0 response size on authoritative name servers
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]