Hi all RFC3597 says this:
> Receiving servers MUST decompress domain names in RRs of well-known
> type, and SHOULD also decompress RRs of type RP, AFSDB, RT, SIG, PX,
> NXT, NAPTR, and SRV (although the current specification of the SRV RR
> in [RFC2782] prohibits compression, [RFC2052] mandated it, and some
> servers following that earlier specification are still in use).
>
> Future specifications for new RR types that contain domain names
> within their RDATA MUST NOT allow the use of name compression for
> those names, and SHOULD explicitly state that the embedded domain
> names MUST NOT be compressed.
If a DNS message is received on the wire, that has a compressed name in
some RR's RDATA which it should not have (going by its type), is it fair
to still accept it as a valid message and process it if the
implementation is able to do so? i.e., can Postel's law be followed
here, or must the implementation strictly reject such messages?
Mukund
signature.asc
Description: PGP signature
_______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
