Stephane, (and dropping IESG as I don't think my comment needs to go to them)
On Oct 6, 2014, at 10:47 AM, Daniel Kahn Gillmor <[email protected]<mailto:[email protected]>> wrote: On 10/06/2014 08:44 AM, Stephane Bortzmeyer wrote: I do not see why the group is limited to this point. But it is not limited. The full text of the paragraph you've quoted is: <snip> So the argument appears to be that we should focus on standardizing private communication between clients and resolvers, but if we happen to be able to solve private between resolvers and authoritative nameservers as well, that would also be considered in-scope. I agree with Daniel on this interpretation of the charter. I'm not sure i have strong opinions either way, but focusing on solving one problem concretely can be useful if it means we don't get bogged down in wrangling over which problem to solve first. Exactly. If we go back to the DNSE BOF at IETF 89 where this was all discussed, there seemed to be a division between people who wanted to solve the client/resolver issue and people who wanted to solve the resolver/authoritative issue. (And varying opinions about whether there *were* issues with each and whether those issues were even solvable.) I like the approach of picking *one* of the problem areas and trying to tackle THAT first. If it turns out to be easy to settle on something for the client→resolver link, it sounds like we can move on to solving the resolver→authoritative link without trouble. Yes... or if in looking at solutions for the client/resolver link we happen to come up with one that ALSO works for the resolver/authoritative link, that work would certainly be allowed under this charter. My 2 cents, Dan -- Dan York Senior Content Strategist, Internet Society [email protected]<mailto:[email protected]> +1-802-735-1624 Jabber: [email protected]<mailto:[email protected]> Skype: danyork http://twitter.com/danyork http://www.internetsociety.org/deploy360/
_______________________________________________ dns-privacy mailing list [email protected] https://www.ietf.org/mailman/listinfo/dns-privacy
