On 10/07/15 15:38, Ben Laurie wrote:
On 10 July 2015 at 15:23, Stephen Kent <[email protected]> wrote:
Ben,
...
To restate our position
first issue: does "our" = Google or just the authors of this document?
Google.
FWIW, since I'm not a Googler but I am one of the authors of this
document, let me just state that I also agree with this position.
<snip>
For example, right now, the only client I know of that reacts to CT is
Chrome/Chromium, and the behaviour it (at least for Chrome - Chromium
comes in multiple flavours) currently exhibits is that text in some
dialogues is changed depending on whether CT is present and meets
Chrome's policies or not, and in the display/non-display of the EV
indicators for EV certificates. This behaviour has already been
through several versions and policy changes, and will continue to
evolve - and is not arrived at by IETF consensus, nor will it ever be.
nice of you to reaffirm that Google doesn't care about IETF standards
in this context.
Does _anyone_ care about IETF standards when it comes to UI?
Has IETF ever actually published any standards relating to web browser UI?
Let me just note that CABForum has no influence over Chrome's UI either,
so please don't feel that IETF is being ignored any more than any other
standards organization. ;-)
--
Rob Stradling
Senior Research & Development Scientist
COMODO - Creating Trust Online
_______________________________________________
Trans mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/trans
