Ideology to auto parse packetIn

[vtolstov]

I think after i'm add tcp.go to pacit we can automatic parse icmp, arp, udp, tcp messages.
What about messages on top of this protocols? Do we need to parse it automatic and determine it types or we provide to users only raw udp/tcp/arp/icmp and after that users can cast message to needed type and try to parse it?

[vtolstov]

And also: may be best of all split pacit to subprojects?
For example:

icmp
ip    ->   tcp
      ->   udp -> dhcp
arp

does it reasonable? And i think we can create something like this: https://github.com/osrg/ryu/blob/master/doc/source/library_packet.rst

pacit.Discover for example can be used to PacketIn pkt and via type switch we can determine packet type.
Also i think for determine we can provide array of interesting packets, for speedup parsing..
What you think?
Is that reasonable - may you rewrite pacit to start support this ? And i by template you create rewrite all stuff?
Now i see that dhcp parsing not too small and needs many cons options that now needs prefix via DHCP_ to not overlap other consts from pacit.