On Wed, Aug 24, 2016 at 7:51 AM, Bodo Moeller <[email protected]> wrote: > Sean Turner <[email protected]>: >> >> I think it ought to editorial because I don't think an implementer would >> have gotten it wrong; > > > It's also not strictly technically wrong. The client TLS implementation > hands the ClientKeyExchange message to the component of the client that > actually sends something to the server, and in that step, the client indeed > "conveys [...] information to the client in the ClientKeyExchange message": > that's certainly not something that implementors need to be told about, and > it's not what the authors of the specification meant to tell implementors, > but it's still correct. (It's also not strictly necessary to tell the reader > here that the ClientKeyExchange message will be sent to the server -- it's > not as if this element of the protocol would be underspecified if we didn't > have this information here.)
No, this is wrong. There is a client and there is a server, and whatever internal arrangements are made are epiphenominal from the perspective of this standard. I doubt anyone was confused by what it said, but either way it needs to get fixed, and our trichotomizing is not helping with this. > > So, I certainly think that this really is a purely editorial error. > > Bodo > > > _______________________________________________ > TLS mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/tls > -- "Man is born free, but everywhere he is in chains". --Rousseau. _______________________________________________ TLS mailing list [email protected] https://www.ietf.org/mailman/listinfo/tls
