Re: [TLS] KeyUpdate and unbounded write obligations

2016-08-23 Thread Judson Wilson
> > > For the use cases you mentioned Keith, they seem to be specific to > application triggered key updates, i.e. key updates do not mean anything to > the TLS layer apart from I got a key update and I must change keys. The > fact that other side has thrown away it's key is only meaningful to the

Re: [TLS] [Technical Errata Reported] RFC4492 (4783)

2016-08-23 Thread Xiaoyin Liu
Why is the type editorial? According to [1], an editorial errata is "a spelling, grammar, punctuation, or syntax error that does not affect the technical meaning". Although the mistake in RFC4492 is clearly a typo, I think it does affect the technical meaning. So I would prefer to leave the type

Re: [TLS] [Technical Errata Reported] RFC4492 (4783)

2016-08-23 Thread Sean Turner
This looks correct, but I’d change the “type” to editorial. Unless anybody disagrees with by next Monday, I’ll ask Stephen to accept this. I’ve also submitted an issue in the 4492bis github repo to get this fixed in the new draft. I’d submit a PR, but I’m still digging out from being absent l

Re: [TLS] KeyUpdate and unbounded write obligations

2016-08-23 Thread Subodh Iyengar
For people that currently use keyupdates or who are planning to use key updates, which layer are you planning to trigger a key update? Would the TLS implementation itself trigger the update or would the application trigger it? For renegotation, I believe it was mostly triggered by the applicatio