# Protocol decoder

**URL:** https://community.zeek.org/t/protocol-decoder/3475
**Category:** Zeek
**Created:** [February 4, 2015, 2:54pm UTC](https://community.zeek.org/t/protocol-decoder/3475 "2015-02-04T14:54:29Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![Emmanuel\_TORQUATO](https://avatars.discourse-cdn.com/v4/letter/e/ecb155/32.png) [@Emmanuel\_TORQUATO](https://community.zeek.org/u/Emmanuel_TORQUATO)
#### Post date: [February 4, 2015, 2:54pm UTC](https://community.zeek.org/t/protocol-decoder/3475/1 "2015-02-04T14:54:29Z")

</div>

Hello,

I would like to know what is the best approach for protocol decoder. Is it better to use BinPAC or BinPAC++ ?

When does BinPAC++ will be supported for production?

Thanks

Emmanuel.

---

<div class="post-metadata">

### Author: ![robin](https://yyz1.discourse-cdn.com/flex011/user_avatar/community.zeek.org/robin/32/599_2.png) [@robin](https://community.zeek.org/u/robin)
#### Post date: [February 4, 2015, 4:28pm UTC](https://community.zeek.org/t/protocol-decoder/3475/2 "2015-02-04T16:28:03Z")

</div>

> I would like to know what is the best approach for protocol decoder. Is it better to use BinPAC or BinPAC++ ?

I would say it depends on your use case. If it's indeed "production",  
then BinPAC. BinPAC++ is still in prototype state. If you're just  
experimenting with some protocol though, it can make sense to give it  
a try.

> When does BinPAC++ will be supported for production?

Unclear, there's signficant work left. It's at the state where the  
research work has concluded and produced a solid prototype, but taking  
it to production will require additional resources that we don't have  
right now unfortunately.

Robin

---

<div class="post-metadata">

### Author: ![system](https://canada1.discourse-cdn.com/flex011/uploads/zeek/original/1X/f09d732bc2cc7c7cc7e35db67cf4e1d5233ce7a7.png) [@system](https://community.zeek.org/u/system)
#### Post date: [May 6, 2022, 3:42pm UTC](https://community.zeek.org/t/protocol-decoder/3475/3 "2022-05-06T15:42:26Z")

</div>


