first frame in this TCP stream: 0.030199000 seconds]
[Time since previous frame in this TCP stream: 0.002911000 seconds]
TCP payload (6 bytes)
Post Office Protocol
STAT\r\n
Request command: STAT
--
Damir Franusic
email: damir.fra
ctets) .
. .
. .
PDU Payload part is the rest of the packet data
and will be interpreted based on PDU Type.
On 5/11/19 10:09 PM, Guy Harris wrote:
On May 11, 2019, at 7:26 AM, Damir Franusic wrote:
*Example tshark output for IRI:*
...
ELEE Protocol
Protocol ve
#x27;t include
all the values available today.
No disrespect and sorry if I sound a bit rude, I would just like to get this
DLT as soon as possible and also define a simple easily extendable header.
Cheers
On May 11, 2019 11:27:57 PM GMT+02:00, Guy Harris wrote:
>On May 11, 2019, at 1:39 PM, Da
No problem, I will do my best to describe the current version, you'll get it
tomorrow.
Thank You for being so prompt
On May 12, 2019 12:02:42 AM GMT+02:00, Guy Harris wrote:
>On May 11, 2019, at 2:51 PM, Damir Franusic
>wrote:
>
>> PDU types are extendable and there migh
er than **TYPE** all over the
place. Maybe you are writing in HTML, in which case realize that you shouldn't.
Damir Franusic wrote:
> they describe everything in great detail by using *ASN.1*notation which
is
> then encoded using
> *BER *when sent by wire.
Wow, talk ab
| ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works|IoT architect [
] m...@sandelman.ca http://www.sandelman.ca/| ruby on rails[
--
Damir Franusic
email: damir.franu...@gmail.com
http://ele2.io/
___
Hi, it would be great if you just typed, rather than **TYPE** all over the
place. Maybe you are writing in HTML, in which case realize that you shouldn't.
Damir Franusic wrote:
> they describe everything in great detail by using *ASN.1*notation which
is
> then encoded using
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 wrote:
Like I sad, I don't have the complete documentation ready,
When yo
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 wrote:
>On May 12, 2019, at 1:28 PM, Damir
ank You again for all the help
On May 12, 2019 11:00:16 PM GMT+02:00, Guy Harris wrote:
>On May 12, 2019, at 1:48 PM, Damir Franusic
>wrote:
>
>> That would be great thanks. That's all I ever wanted really, but now
>I understand the relevance of having a proper I-D.
>
&
:00:16 PM GMT+02:00, Guy Harris wrote:
>On May 12, 2019, at 1:48 PM, Damir Franusic
>wrote:
>
>> That would be great thanks. That's all I ever wanted really, but now
>I understand the relevance of having a proper I-D.
>
>It will also be useful for documenting the p
/15/19 9:08 AM, Damir Franusic wrote:
Hi Guy
I just made a little TOC change in the draft but that's all. Version 00 is
there and you can link it and it with a new LINKTYPE_ELEE.
http://xml2rfc.tools.ietf.org/cgi-bin/xml2rfc.cgi?url=http://socket.hr/draft-dfranusic-elee-00.xml&modeAsFo
I apologize for my previous mail, issues with email client. What I wanted to
ask is whether I should name the draft like this:
draft-dfranusic-tsvwg-elee-00
Thanks,
--
Damir Franusic
http://socket.hr
http://github.com/dfranusic
On May 17, 2019 8:29:34 PM GMT+02:00, Damir Franusic
wrote
Hmm In wouldn't want to ask for a new group but from all the those groups,
opsawg seems somehow appropriate, or maybe not?
--
Damir Franusic
http://socket.hr
http://github.com/dfranusic
On May 17, 2019 10:26:42 PM GMT+02:00, Guy Harris wrote:
>On May 17, 2019, at 11:34 AM, Damir
his draft?
--
Damir Franusic
http://socket.hr
http://github.com/dfranusic
On May 17, 2019 10:42:29 PM GMT+02:00, Guy Harris wrote:
>On May 17, 2019, at 1:35 PM, Damir Franusic
>wrote:
>
>> Hmm In wouldn't want to ask for a new group but from all the those
>groups, opsawg see
Cheers Guy and thank You for all Your assistance.
--
Damir Franusic
http://socket.hr
http://github.com/dfranusic
On May 17, 2019 11:05:48 PM GMT+02:00, Guy Harris wrote:
>On May 17, 2019, at 1:50 PM, Damir Franusic
>wrote:
>
>> Can we conclude this and make a nek LINKTYPE_
rget a specific group like opsawg.
--
Damir Franusic
http://socket.hr
http://github.com/dfranusic
On May 18, 2019 11:19:30 PM GMT+02:00, Michael Richardson
wrote:
>Damir Franusic wrote:
>> for Lawful Interception Data which can also use SCTP for transport,
>should I
>> us
Hi
I know it's extensible but ELEE is used for different purpose but I get you're
trying to say.
--
Damir Franusic
http://socket.hr
http://github.com/dfranusic
On May 18, 2019 11:18:00 PM GMT+02:00, Michael Richardson
wrote:
>Damir Franusic wrote:
>> Hi
>
>&g
ld be
ignored in case of CC data), but like I said it's work in progress.
On 5/19/19 12:21 AM, Guy Harris wrote:
On May 12, 2019, at 1:28 PM, Damir Franusic wrote:
I've tried to be as prompt and as accurate as possible so here is the draft, I
hope you'll appreciate the eff
n-opsawg-pcapng.xml&modeAsFormat=html/ascii&type=ascii#section_epb>
On 5/19/19 12:53 AM, Guy Harris wrote:
On May 18, 2019, at 3:05 PM, Damir Franusic wrote:
I know it's extensible but ELEE is used for different purpose
LINKTYPE_ELEE is used for the *same* purpose as pcapng
ation.
To be fair, those programs would *also* have to be modified to handle
LINKTYPE_ELEE - and programs that can read pcapng would at least be able to
read the intercepted packets without change, assuming they just ignore unknown
block and option types (which they should do!).
--
Damir F
And does wireshark currently support new block types and custom options in
EPBs. I would need to access them in dissector plugin, that's what I'm worried
about.
--
Damir Franusic
http://socket.hr
http://github.com/dfranusic
On May 19, 2019 2:00:19 AM GMT+02:00, Guy Harris wrote:
ca/mailman/listinfo/tcpdump-workers
--
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
I explained here, I would really
appreciate it.
Thanks
On 5/19/19 2:00 AM, Guy Harris wrote:
On May 18, 2019, at 4:33 PM, Damir Franusic wrote:
No I get now what you you're saying. You think that I should rewrite the draft
to explain custom options in
Enhanced Packet Block, rather than us
24 matches
Mail list logo
