Hi Ben,

Ben Schwartz <[email protected]> writes:

> On Mon, Nov 16, 2026 at 12:37 PM Babak Farrokhi
> <[email protected]> wrote:
>> Today users have limited control over whether their resolver sends
>> client subnet information to authoritative servers. When using an
>> ECS-enabled resolver such as 8.8.8.8 or 9.9.9.11, a client can "opt-out"
>> with a SOURCE PREFIX-LENGTH of 0, but to ask for a shorter prefix it has
>> to supply its own address, which it does not know when it is behind NAT
>> or VPN.
>
> RFC 7871 says the address "MUST be truncated to the number of bits
> indicated by the SOURCE PREFIX-LENGTH field".  Even with a NAT or VPN
> in the way, I'm pretty sure I can figure out what my client address
> truncated to zero bits will be.
>
> --Ben

Agreed on /0. However the problem is non-zero limits e.g. /23 that need
the client's public address in ADDRESS. When behind a NAT or VPN the
client may not know it.
The option in our proposal does not need an address and only requires
the prefix length. The resolver uses "the  source address of the qurey"
(Section 3.3).

BR,

-- 
Babak Farrokhi

Attachment: signature.asc
Description: PGP signature

_______________________________________________
DNSOP mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to