During the last month's meeting in Dallas, I was asked by Warren to compile
a list of relevant criteria that we need to consider when evaluating the
potential of each document. The following are starting points, so please
consider them in mind while reading the different documents (and of course
feel free to add whatever you think relevant to enrich the discussion /
guide your opinion):
1. Can you implement the mechanism?
- Does it use existing or no existing technology.
- If you are using new technologies does it allow for unseen
problems; algorithms, etc.
- Actual implementation on the client; apps or stub.
- Does it provide flexibility of choosing providers?
2. Does it work?
- How middle boxes will re-act
3. Is it expensive at the server side?
- Would it allow for any issues like DDoS?
4. Does it provide what it claims to provide?
- Privacy.
5. Does it require client authentication.
- What a problem this raises?
- How that compares to encryption but not authenticated (client) --
giving the server a proof who they are indirectly by authenticating the
recursive.
6. Other issues:
- Is TCP anycast a problem? How it relates to the various documents?
Thanks,
Aziz
---------
Aziz Mohaisen
www.mohaisen.net
On Tue, Apr 7, 2015 at 3:33 PM, Warren Kumari <[email protected]> wrote:
> Hi all,
>
> We are planning on starting a call for adoption on the documents on April
> 15th.
>
> At the meeting in Dallas we heard that a number of people didn't feel
> that they had enough information / knowledge of the documents to make
> in informed decision, so we are giving y'all some extra time to read
> the documents before kicking off the CfA.
>
> Our plan is to have a *single* call for adoption, listing all 3
> documents, and ask people to put in a *clear* indication for each
> document if they would like it adopted or not.
>
> We will then decide which we will be adopting -- if we get really
> strong support for multiple documents we will adopt multiple...
>
>
> So, your homework is to read:
> Private-DNS -
> https://datatracker.ietf.org/doc/draft-hallambaker-privatedns/
>
> Confidential DNS -
> https://datatracker.ietf.org/doc/draft-wijngaards-dnsop-confidentialdns/
>
> TLS for DNS: Initiation and Performance Considerations -
> http://datatracker.ietf.org/doc/draft-hzhwm-dprive-start-tls-for-dns/
>
> before the 15th of this month....
>
> W
>
> --
> I don't think the execution is relevant when it was obviously a bad
> idea in the first place.
> This is like putting rabid weasels in your pants, and later expressing
> regret at having chosen those particular rabid weasels and that pair
> of pants.
> ---maf
>
> _______________________________________________
> dns-privacy mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/dns-privacy
>
_______________________________________________
dns-privacy mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dns-privacy
