[chord] standard chord messages format

[Emil Sit]

On Sun, 21 May 2006 at 04:27 (-0700), Fatemeh Karimirad wrote:
>   We are going to simulate chord by extending ns-2. We have problems
>   finding a straight forward description of the standard format for
>   chord messages, for example messages for finding successor.  By the

I don't remember too much about ns-2 but does it require that
you literally replicate the wire format of our implementation?

If you do, the message formats are probably best documented at:

http://pdos.csail.mit.edu/cgi-bin/cvsweb.cgi/sfsnet/svc/transport_prot.x?rev=1.8
http://pdos.csail.mit.edu/cgi-bin/cvsweb.cgi/sfsnet/svc/chord_prot.x?rev=1.41
http://pdos.csail.mit.edu/cgi-bin/cvsweb.cgi/sfsnet/svc/recroute_prot.x?rev=1.2

The current implementation of Chord supports multiple routing types
but you are probably most interested in the recursive routing
implementation that is listed above.

In consultation with RFC 1831, you ought to be able to replicate
the wire format we use.  (Well, there is the caveat that our wire
protocol has an annoying issues with regards to how chordIDs are
marshalled; it is variable length and sometimes padded.  If you are
actually looking to do this, I can probably find a reference
implementation of the encoding.)

-- 
Emil Sit / MIT CSAIL PDOS / http://pdos.csail.mit.edu/chord/