On Tue, Sep 11, 2007 at 11:19:17PM +0200, <ZioPRoTo (Saverio Proto)>:
~> 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.
Yes, but it's to early, because during the tests of the prototype we can
change it.
~> 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 ??
pyntk/core/qspn.py:105
TP = [(self.maproute.me[0], NullRem)]
etp = (R, [(0, TP)], flag_of_interest)
this is a fresh ETP,
R is the same set described in the paper,
flag_of_interest, is the same boolean value described in the paper,
[(0, TP)] is the tracker packet of the etp.
So, after some oops, the TP will be something like:
TP = [(11, NullRem), (22, Rem11_22), (33, Rem22_33)]
[(0, TP)]
suppose in this pkt, the hops are all nodes of the gnode 19 of lvl 1, i.e.
19.11, 19.22, 19.33
when pkt will overpass the level 0, by the group rule it'll become, something
like:
TP = [(111, NullRem), (122, Rem111_122), (133, Rem122_133)]
[(1, 19), (0, TP)]
and so on... (btw, it's better to read directly the source)
~> 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 ..?
yes
--
:wq!
"I don't know nothing" The One Who reached the Thinking Matter '.'
[ Alpt --- Freaknet Medialab ]
[ GPG Key ID 441CF0EE ]
[ Key fingerprint = 8B02 26E8 831A 7BB9 81A9 5277 BFF8 037E 441C F0EE ]
_______________________________________________
Netsukuku mailing list
[email protected]
http://lists.dyne.org/mailman/listinfo/netsukuku
