> No, there isn't. You should read the source code, because it varies from > implementation to > implementation. The paper is abstract, it shouldn't mingle with implementation > details. > However, in python, you can think of a list [] of node IDs, f.e. > [ 51, 2, 11, 29, 120 ]
I understand that a paper explaining general concepts does not involve implementation details. But if you want to define Netsukuku protocol (to have maybe later multiple implementations in different coding languages) then it is essential to define packet structures, as for any other Internet Protocol, to guarantee correct interoperability of the different implementations. So, as far as I understand, a TP contains just a plain list of interger that identify nodes, no other information regarding route REM an so on ?? > Yes, they are all TP, but each handled in a different way. So into a TP there is at least a few bits that are telling me if this TP is from a TP or ATP or CTP ..? > > I don't know. Can you post some links? > I will tomorrow morning as soon as I can talk with my crypto expert at the university that is doing an heavy research work on that topic :) Have a good coding night everybody ;) Saverio _______________________________________________ Netsukuku mailing list [email protected] http://lists.dyne.org/mailman/listinfo/netsukuku
