Is it possible to embed one protocol into another?

Nobody has claimed this yet.

So we have a TCP-based protocol (lets call it protocol A for now), that basically adds some additional fields to address specific components within our product.
These components may speak different protocols, so the payload of that first protocol can be a number of different protocols (protocol B, C, D, ...).

Is it possible to tell Rammbock that protocol B is prefixed with the header of protocol A?

Start by reviewing Rammbock's existing protocol-definition and payload-handling documentation or entry points. Determine how protocol A's header could wrap protocol B and whether the current model supports nested protocols; the issue is done when the supported approach or required scope is clearly established.

Written by the indexing model from the issue text.