Hi Guy
I've tried to be as prompt and as accurate as possible so here is the
draft, I hope you'll appreciate the effort. I agree
that the initial thing I sent was an abomination. I will work on this
draft as the project progresses, but for now, it covers
everything implemented so far.
http://xml2rfc.tools.ietf.org/cgi-bin/xml2rfc.cgi?url=http://socket.hr/draft-dfranusic-elee-00.xml&modeAsFormat=html/ascii
On 5/11/19 11:30 PM, Guy Harris wrote:
On May 11, 2019, at 1:39 PM, Damir Franusic <damir.franu...@gmail.com> wrote:
Like I sad, I don't have the complete documentation ready,
When you have the complete documentation ready, let us know.
but this is the general format:
+---------------------------------+
| Version |
| (1 Octet) |
| |
+---------------------------------+
| PDU Type |
| (1 Octet) |
| |
What are the PDU type values?
+---------------------------------+
| Source ELLE Node |
| NULL terminated ASCII string |
| (1 Octet min for \0) |
So that's pure ASCII, without, for example, any letters with diacritical marks,
so it doesn't need full UTF-8?
| |
+---------------------------------+
| Destination ELEE Node |
| NULL terminated ASCII string |
| (1 Octet min for \0) |
And the same applies there?
| |
+---------------------------------+
| ELEE PDU Payload |
. (Remaining octets) .
. .
. .
PDU Payload part is the rest of the packet data
and will be interpreted based on PDU Type.
Presumably the formats of the PDU payloads will be described in the complete
documentation.
--
Damir Franusic
email: damir.franu...@gmail.com
http://ele2.io/
_______________________________________________
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers
