> From Christopher Allen <ChristopherA@consensus.com> > The short outline of "tls-changes" is: > > 1. MAC algorithm > 2. MAC contents > 3. Block padding > 4. Message order standardization > 5. Certificate chain contents > 6. The no_certificate alert > 7. Additional alerts > 8. Seperation of Record and Handshake layers > 9. Additional Record Protocol clients I strongly recommend that these be separated into 2 parts: those that force a change the current protocol (bits on the wire), and those that are clarifications of current practice. In particular points 1., 2., and 6. above would make all current implementations non-conforming. Do we have examples of interoperability between the proposed protocol and existing implementations? Would the version number be rolled forward? I suspect that those at the meeting will want to treat these proposals independently. PK -- Philip L. Karlton karlton@netscape.com Principal Curmudgeon http://www.netscape.com/people/karlton Netscape Communications Corporation Everything should be made as simple as possible, but not simpler. -- Albert EinsteinReceived on Monday, 2 December 1996 14:17:29 EST
This archive was generated by hypermail pre-2.1.9 : Wednesday, 24 September 2003 06:34:55 EDT