Hi all,
<hat="individual">
I agree with clarification #52 proposed by Tom.
http://trac.tools.ietf.org/wg/websec/trac/ticket/52
And agree with clarification #51
http://trac.tools.ietf.org/wg/websec/trac/ticket/51
For clarification #50:
http://trac.tools.ietf.org/wg/websec/trac/ticket/50
I am not sure the text is clear enough on what we mean by "a public key
pin cannot be formed."
Best regards, Tobias
On 11/08/12 22:30, Yoav Nir wrote:
Hi Tom
On Aug 11, 2012, at 11:57 PM, Tom Ritter wrote:
I don't know IETF procedure for making changes, but one of the
outstanding issues I don't think has been resolved with
draft-ietf-websec-key-pinning-02 is inherited DSA parameters. I
raised this issue here:
http://www.ietf.org/mail-archive/web/websec/current/msg01027.html with
suggested verbiage.
That message of yours flew under the radar. I don't know why.
The IETF procedure for making changes is to raise the suggestion on the mailing
list, and discuss it there until consensus is reached.
To help with that, we may use an issue tracker (similar to a bug tracker like
bugzilla). I've opened three tickets for the issues in your email:
http://trac.tools.ietf.org/wg/websec/trac/ticket/50
http://trac.tools.ietf.org/wg/websec/trac/ticket/51
http://trac.tools.ietf.org/wg/websec/trac/ticket/52
We can start a thread on each of them.
Easy way is the editors start the thread with "looking at issue #50, we agree and it
seems OK to us. Anyone object?", and then if nobody objects, the text is updated, a
new draft is published, and if you think it's OK, we close the ticket. If there are
objections (by the editors or others), they get discussed.
Yoav
_______________________________________________
websec mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/websec
_______________________________________________
websec mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/websec
