Re: [dnsext] draft-levine-dnsextlang-02

Miek Gieben <miek@miek.nl> wrote:
>
> * Base32 should be supported in the rdata (for NSEC3).
> * There probably should be an rdata type called BitMap (for NSEC/NSEC3).

Yes.

> * NSEC3 has a salt length which isn't used in the text representation of the
>   record. How is this handled?

There should probably be a qualifier for a length prefix on hex data, as
there is for base64.

> * The HIP record also has fields not used in the text representation: "PK length
>   field".
> * The HIP record ends with an array of domain names. How should that be encoded?
> * The HIP contains a base64 field that can not contain spaces in the
>   presentation format (unlike all other b64 fields in other RRs). How to deal
>   with that?

HIP RDATA is horrible. It would be slightly easier if the length fields
prefixed the data they describe. The non-standard base64 restriction is
ugly. The rendezvois servers should probably be listed in separate RRs of
a different type, which would also solve the base64 problem. I think that
awkward RRtypes like this should have special case handling, e.g. describe
the RDATA as a single field of HIP type, or just leave it to RFC 3597
generic representation.

Ideally in the future RRDATA layouts will be simpler than this.

>   Same holds true for TXT records.

There are qualifiers to specify multi-field textual data.

> * The IPSECKEY RR uses some internal subtyping: if "gatewaytype" is 0 there is no
>   gateway. If it is 1 or 2 its an IP address and if its 3 the gateway is a
>   domain name. How to encode that?

Again I think this has to be handled in special case code. Really they
should have used a different RR type for each layout.

Another awkward case is the variable-length IPv6 address field in A6
records, but that has been deprecated forcefully enough that it is no
problem to handle with RFC 3597 generic layout.

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
Dogger: Northwesterly 5 or 6, occasionally 7 in northeast. Moderate or rough.
Fair. Moderate or good.
_______________________________________________
dnsext mailing list
dnsext@ietf.org
https://www.ietf.org/mailman/listinfo/dnsext