Hi Cullen,
thanks for your comment. Actually I tend to proceed with 9), because I
already have that CHORD stuff completely, including data storage and
retrieval, finger stuff and so on :). However, your step by step guide
does watch the RELOAD path, which I totally left aside up to know. One
reason: It seems to be rather instable right now; instable in the sense
of "it is constantly changing". I already had made bad experiences with
following a draft a couple of years ago. It was the AODV draft from the
MANET group. So I don't want to spent too much time into things, which
are changing quite often.
Thanks for the steps. I'll watch that.
Regards
Cullen Jennings schrieb:
I might start with
1) get a minimal transport layer going with TCP
2) get a simple message parser going to deal with RELOAD messages
3) get AttachLite running to bring up a connection between two nodes
4) Fake out the bootstrap stuff and bring up two node where one can
send a JOIN to other
5) Add in minimal chord implementation to start managing the DHT ring
6) Initially get Chord going with no finger tables, everything just
routes around the edge
7) add UPDATE and finger table to ring
8) add a basic data model and get it so you can store and retrieve
some data
9) Go sleep because you have probably been up for 30 hours at this point
10) get DHT so it deal with corner cases of partition, rings with 1 entry
11) do bootstrap
12) make configuration work
13) get enrollment to work
14) add the other data models
15) get rest of methods working
16) get security working
17) make sure you have several Tylenol's handy and go do ICE
18) invent really cool usage on top of it :-)
On Oct 16, 2009, at 7:14 AM, neil.young wrote:
Hi,
I recently finished the development of a CHORD implementation in C#.
I already use a proprietary binary TCP communication protocol for the
CHORD messages (findsuccessor, the notify and stabilize routines, the
ping etc.). In near future I want to proceed to RELOAD, whereas the
desired implementation does not necessarily has to have full RELOAD
characteristics as the first result. Especially these items are not
required initially, so that the first implementation would more be a
REL instead of RELOAD :)
1) Security
2) NAT traversal
3) ICE STUN support
4) Enrollment server
Implementors, could you give me please some suggestions, where to
start with best under these circumstances?
Kind regards
_______________________________________________
P2PSIP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/p2psip
_______________________________________________
P2PSIP mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/p2psip
