> EDNS0 RFC restricts EDNS0 to 4096 bytes, number of implementations > will not send more even if client ask for it. Firewalls will > enforce this.
RFC 2671 enforces no such limit - the strict limit is 65535, and §4.5.5 has a hint that 4K might be a reasonable amount of state to maintain for fragment reassembly. I seem to recall that BIND, however, will not permit the EDNS0 buffer size to be configured above 4096. I'm not in a position to double check that right now, though. Ray
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
