Re: New official link-layer type request

[Damir Franusic <damir.franusic () gmail com>]

That would be great thanks. That's all I ever wanted really, but now I understand the relevance of having a proper I-D. 
 And yes, you are correct regarding the Header/PDU; quite simple.

On May 12, 2019 10:38:21 PM GMT+02:00, Guy Harris <gharris () sonic net> wrote:
> On May 12, 2019, at 1:28 PM, Damir Franusic <damir.franusic () gmail com>
> wrote:
>
> > 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
>
> So a packet with the requested new LINKTYPE_ value would consist of an
> ELEE header, followed by an ELEE PDU, and that's it?
>
> We could then just have the entry on the tcpdump.org link-layer header
> types point to the draft, so that if you add new PDU types, the draft
> will be updated. If the draft ends up being published as an official
> I-D, we could point to that and, if it becomes an RFC, point to that.

-- 
Damir Franusic

http://socket.hr
http://github.com/dfranusic
_______________________________________________
tcpdump-workers mailing list
tcpdump-workers () lists tcpdump org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers