Re: Proposed Feature: Application Reputation system

2012-06-20 Thread Moheeb Abu Rajab
Hi Sid, Please find the answers inline. thanks Moheeb On Tue, Jun 19, 2012 at 3:03 PM, Sid Stamm wrote: > Thanks for the info, Moheeb! > > On 06/15/2012 11:35 AM, moh...@google.com wrote: >> Regarding the TLS bouncing idea. >> As the reputation system derives features in part from the submitt

Security Engineering Meeting 6/21 3 PM PDT

2012-06-20 Thread Ian Melven
Homer Simpson: Kids: there's three ways to do things; the right way, the wrong way and the Max Power way! Bart: Isn't that the wrong way? Homer Simpson: Yeah, but faster! ~*~*~*~*~*~*~*~ Our weekly Security Engineering meeting is open to the Mozilla community and will take place on Thursday J

Re: Implications of new TLDs

2012-06-20 Thread John Nagle
On 6/20/2012 9:54 AM, Kevin Chadwick wrote: Are you aware of actual plans to allow A records for TLDs? I don't have links to earlier discussion offhand, but I recall the consensus being that that shouldn't be allowed at all. Many of the ccTLDs already have them. I've mentioned "AI". That's

Re: Implications of new TLDs

2012-06-20 Thread Kevin Chadwick
> Are you aware of actual plans to allow A records for TLDs? I don't have > links to earlier discussion offhand, but I recall the consensus being > that that shouldn't be allowed at all. I wouldn't be surprised if disallowing that was one of the stipulations for pressing ahead but the money may

Re: Implications of new TLDs

2012-06-20 Thread Zack Weinberg
On 2012-06-20 3:44 AM, Gervase Markham wrote: On 19/06/12 17:24, Zack Weinberg wrote: Er, I'm confused. If I type "http://email/"; into my browser, you are saying we should refuse to do a DNS query? How do I then reach my intranet site? I'm fairly sure some intranet sites _only_ have a single-wo

Re: Implications of new TLDs

2012-06-20 Thread Gervase Markham
On 19/06/12 17:24, Zack Weinberg wrote: > I think we do need our own DNS resolver eventually (mostly because > DNSSEC) but it's not necessary for this. We'd just have to refuse to do > the DNS query at all for URLs whose hostname component did not contain a > dot, and/or which was equal to or a su