My current thoughts about how a new RR type should
look like:
We should not allocate a MARID record type (surprise!)
We should contact the DNS crew and cooperate with them
to invent a new generic binary container RR type, not
specific to MARID.
The link to MARID would be in the fqdn, i.e. the _marid. prefix.
Giving an entry it's content type not by the RR type only, but by
parts of the dns name also is not in the spirit of the original
DNS. DNS has nevertheless made this step already with
SRV records. So this should not be an issue.
This way we also have a container for future work, e.g. when
describing what kind of mail a receiver is willing to accept,
or records for other kinds of services. Or storing public keys,...
As I stated in earlier postings, DNS servers should not modify
or decode it, just forward it as it is.
It would be to be discussed with the DNS people whether
the container should contain
- any binary data
- ASN.1 encoded data only
- ASN.1 tagged with a OID for unambigous identification
of the content type
I vote for ASN.1 with OID.
I believe such an easy to implement and generic record
suitable for other uses than MARID too would be accepted
and implemented much faster.
regards
Hadmut