Re: What is a secure page?

> Basically, I think that the current situation where the primary
> browser security indicator is tied to the TLS protocol is not a
> very good approach. I think we should (in this group) derive an
> abstraction of the security context available (which may include
> historic information as well as 3rd party information) and we
> should then try figure out how to map that to some GUI that makes
> sense to various types of user (and in doing that we should IMO
> more-or-less ignore the existence of protocol experts - EKR is
> not a user here:-)

I agree that that is core to our work on displaying usably (displaying 
robustly is another core). 

        Mez