Hi Nick, We are currently in the process of migrating the ECS code from the feature branch into our main branch, using the new EDNS option handling. Regards, -- Ralph On 09-02-17 01:09, Nick Urbanik via Unbound-users wrote: > Dear Folks, > > On 15/12/16 09:40 +0100, W.C.A. Wijngaards via Unbound-users wrote: >> Features >> - Added generic EDNS code for registering known EDNS option codes, >> bypassing the cache response stage and uniquifying mesh states. Four >> EDNS option lists were added to module_qstate >> (module_qstate.edns_opts_*) to store EDNS options from/to front/back >> side. >> - Added two flags to module_qstate (no_cache_lookup, no_cache_store) >> that control the modules' cache interactions. > > Does this support EDNS Client Subnet extension (RFC 7871)? There was > discussion of this back in April 2015, where an experimental patch was > used. I am hoping that progress has been made since.