Eggert, Lars writes: > On 2015-7-21, at 09:23, Tero Kivinen <[email protected]> wrote: > > - For TLS means a complete profile for TCPINC > > I thought we agreed on a complete, *self-contained* profile for TLS. > Self-contained meaning one doc that someone can hand to their dev > team which they can read without the need to consult (too many) > other documents to understand what an implementation would entail.
Yes, that something that I would like to see. I am not competely sure whether it needs to be completely self-contained. I mean in my ikev2 minimal draft, I had 6 pages of actual description of the protocol, and that is the important part to understand how IKEv2 works, and what needs to be done. Then at the end of that document there is about 20 pages of payload formats for payloads used in the protocol. In my case I cut & pasted the actual payload formats from the IKEv2 RFC, but I could have just provided references, i.e. for "Key Exchange Payload" look at section 3.4 of RFC 7296. > (In other words, not a document that says "read and understand all > of TLS, and then ignore pieces X, Y and Z.) Yes, I would not consider that as complete profile. I think this is what the current draft is now, but not even fully mentioning which pieces to ignore... -- [email protected] _______________________________________________ Tcpinc mailing list [email protected] https://www.ietf.org/mailman/listinfo/tcpinc
