Skip to content

How do encoder parameters map to RFC 6330? #1

@davidcallanan

Description

@davidcallanan

Hey,

Amazing project, just trying to get it working.

I'd like to decode some data that I've encoded, and I'd like to figure out how the encoder parameters line up with RFC 6330.

It is my understanding that these are the parameters the RFC requires:

F  uint64
T  uint16
Z  uint8
N  uint16
Al uint8

How do the generated encoder parameters in your layout match up against the RFC parameters? Are some of them hardcoded?

I'm hoping I can deterministically decode my data based on pre-agreed configuration options and data length, without having to transmit these encoder parameters over the wire, so I need to understand the format of these encoder parameters so that I can generate them myself.

I feel I should be able to decode some data that is generated by any RFC-compliant implementation, where I don't have access to a layout file.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions