In message <alpine.LRH.2.00.0811140811531.5889@xxxxxxxxxx>, Pekka Savola writes: > On Fri, 14 Nov 2008, Mark Andrews wrote: > > In message > > <alpine.LSU.2.00.0811131135530.14367@xxxxxxxxxxxxxxxxxxxxxx>, Tony F > > inch writes: > >> You also need the server to provide a verifiable TLS certificate. > >> The vast majority of them are not. This problem is perhaps even > >> harder to fix than the lack of DNSSEC. > > > > Just use DNSSEC and CERT records to do that. > ...> > > If self signed, look in the DNS for the CERT. Accept if > > signed and validated by DNSSEC. > > How does an application do "accept if signed and validated by DNSSEC"? You validate the CERT RRset using the techniques in RFC 4033, 4034 and 4035. If the answer is "secure" then it was signed and validated. You the match offered cert to the CERT RRs using the information from RFC 4398. Do you need more detail or is that enough guidance? Mark -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: Mark_Andrews@xxxxxxx _______________________________________________ Ietf@xxxxxxxx https://www.ietf.org/mailman/listinfo/ietf