At Mon, 28 Dec 2015 07:59:14 +0530, Mukund Sivaraman <m...@isc.org> wrote:
> https://tools.ietf.org/html/draft-ietf-dnsop-edns-client-subnet-06 > > One of the main concerns while implementing EDNS client-subnet is about > keeping the size of cache small and in check. It seems cache handling > for EDNS client-subnet can be improved by changes to the option > syntax. While the draft may be describing an existing scheme used in > some existing implementations, it needs changes before this draft goes > any further, otherwise it would lead to more duplication in the cache > than necessary. I have to admit I've not closely looked at all of the text, but I have a couple of high level comments: - Whether you like it or not, any protocol change will be out of scope of this particular draft (although the result of IETF last call and IESG decision might change that) - (in my understanding) that's the decision the wg made quite a long time ago. If you want to introduce any final change, that will have to be something that doesn't involve a protocol change. - From a quick read, the concern you raised seems to be related to the case where more and less-specific prefixes are to be configured at the ECS-supporting authoritative server. In my understanding that was actually one of the unclear points, but the wg decided to defer any detailed discussions to a currently-imaginary successor of this document. You should be able to find some related discussions in the dnsop list archive. -- JINMEI, Tatuya _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
