Write Your
Own TCP/IP
TCP/IP takes into consideration anybody to compose a convention on top of it since it decouples the exchange of the information from the semantics of the information itself, i.e. TCP/IP does not mind what information is being exchanged.
I am not mindful of any such assets, and would be astonished if there existed any assets that reveal to you how to compose a convention. I say this on the grounds that a convention can essentially do anything, and all things considered there are no guidelines to characterizing one. It's what you characterize as tenets that makes a convention. Also, what you characterize ought to be represented by what you need your application to do.