Q1: Should we allow name compression in the RDATA of DNSSEC RRs?

["Scott Rose" <scottr@nist.gov>]

Though it isn't just my opinion, there seems to be some concensus around the
WG that name compression in the RDATA of the DNSSEC RRs (SIG and NXT).
Generally, that it is a not something desired.

Q:  Should the text in the Resource Records draft of the DNSSEC spec be
changed to indicated that name compression "SHOULD NOT" be used when sending
security RRs over the wire?  This only applies to the "signer's name" field
of the SIG RR and "next domain name" of the NXT RR.
    note:  "SHOULD NOT" would be the suggestion.  "MUST NOT" may be too
strong, but if that is the concensus, then that will be the language.

The same requirements should not be applied to the resolver. i.e. that
resolvers should still accept and process RRs that use name compression in
the next domain name field of the NXT RR and signer's name of the SIG RR.



--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>