LinkTed

`DNSKEY` and `DS` are already supported and [`NSEC`](https://github.com/LinkTed/dns-message-parser/tree/NSEC) is currently not done yet.

The problem is, if we do it, what should be done for an unknown RR? If we use a dedicated struct then we have the issue that if the RData...

Thanks for the suggestion. It has to be prevented that the user or the parse creates a `Value::Unknown` with `Tag` for example equals to `issue`. Because it would be ambiguous...

> We can prevent the user from not making such a mistake by not exposing the enum or checking for such mistakes when encoding the packet. As for creating it...

How the user can access the different data? For example, a `DomainName`if it is a `Issue`or the `Url`if it is a `IoDef`.

This is because, each QClass number is mapped to a specific variant in the enum [QClass](https://docs.rs/dns-message-parser/0.4.6/src/dns_message_parser/question.rs.html#141-151). If there is no mapping for the number then an error is returned. I...

@iankressin could you print the DNS message, where you get this error message?

Is there any chance that it would be implemented in the near future? It sounds that it would be a great feature for the Nitrokey.

I implement a program, which unlocks a password database with a hardware token. I try to use OpenSC for the Nitrokey, but it only supports decryption operation and only the...

So, if I use OpenSC have to abstract and do the encryption stuff on my own, which is too much if you want to support the full interface (like: support...