Re: [DNSOP] Working Group Last Call for draft-ietf-dnsop-edns-client-subnet

2015-09-29 Thread Wilmer van der Gaast
g from: An attempt at suppressing ECS silently getting ignored. That seemed worse. I do welcome better alternatives. IMHO transitivity was enough of a corner case that behaviour on rejecting it was not a terribly interesting detail. All in all, I'm very gla

Re: [DNSOP] draft-ietf-dnsop-edns-client-subnet-01

2015-06-12 Thread Wilmer van der Gaast
Just to add my ยข2 on this point: In the last version of the draft that I wrote (and the one used for most implementations), there was no MUST/SHOULD terminology, so it was a little vague. Reason we've added the truncation at the time is to save space. This is DNS, where saving bytes is sometimes

Re: [DNSOP] draft-ietf-dnsop-edns-client-subnet-00 Birthday Attack

2015-05-01 Thread Wilmer van der Gaast
go from here. Not echoing the option after all > is the proper EDNS way of signalling lack of support for said option. > So dropping the option-less answer is also not a good idea. > Probably the safest, and then reissue a single query without ECS instead of continuing

Re: [DNSOP] comments on draft-ietf-dnsop-edns-client-subnet-00

2015-01-08 Thread Wilmer van der Gaast
ss 0.0.0.0/0 to get it cached for many hosts). > > Another IPv4-centric description. This should probably be, e.g. > "with the SCOPE NETMASK being 0, meaning an empty prefix". > It's just an example, I went for an IP address to save on words. COuld consider mixing ::/0 (less typing in fact!) and 0.0.0.0/0 in various examples. -- Wilmer van der Gaast, London Traffic/Edge SRE. ___ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop