17 Úno
2017
17 Úno
'17
10:31
Hi,
On 17-02-17 07:52, Chuck Musser wrote:
I only see the need for ECS in knot if you can stick in a plugin that
can do something useful with the client address and update the scope
prefix length appropriately.
A generic plugin won't be particular useful because how to use the
client address to tailor the response is left unspecified and everybody
is likely to do it different anyway.
Best regards,
Matthijs
Chuck
_______________________________________________
knot-dns-users mailing list
knot-dns-users(a)lists.nic.cz
https://lists.nic.cz/cgi-bin/mailman/listinfo/knot-dns-users
On Feb 15, 2017, at 4:17 AM, Vítězslav Kříž
<vitezslav.kriz(a)nic.cz> wrote:
Hi Chuck,
I have some questions about what you exactly need to support.
Do you want to include ECS to every response or only to responses which
contains ECS in query?
Only responses that contain it in the query. It’s probably
wise to only
send it in response to servers that appear able to use the information
and are likely to include ECS on subsequent requests.
Do you want to response with same Client Subnet used in query or always use Client Subnet
with prefix length of 0?
I think client subnet, with scope prefix length of zero.
The intent is to indicate that the
feature is supported but isn’t being used to (yet anyway) to tailor the response.