semantic
Click on the red underlined text to get to the source
...
The DNSSEC protocol has been through many iterations whose syntax and
semantics are not completely compatible. This has occurred as part
of the ordinary process of proposing a protocol, implementing it,
testing it in the increasingly complex and diverse environment of the
...
... Delegation
Signer's (DS) [RFC3658] introduction of new semantics for the NXT RR
that are incompatible with the semantics ...
... semantics for the NXT RR
that are incompatible with the semantics in [RFC2535]. Answers
provided by DS ...
... Delegation Signer (DS) introduces new semantics for the NXT RR that
are incompatible with the semantics ...
... semantics for the NXT RR that
are incompatible with the semantics in RFC 2535(-> 4035prop | 4034prop | 4033prop). In RFC 2535(-> 4035prop | 4034prop | 4033prop), NXT ...
... quite possible that more incompatibilities exist between DS and
earlier semantics. Legacy resolvers may also be confused by seeing
records they recognize (SIG and KEY) while being unable to find NXTs.
...
... DNSSEC records
with DS semantics is to have authoritative servers only send that
data to DS-aware resolvers. It's been proposed that assigning a new
...
... DA
bit unchanged, it would still see the new semantics, and it would
probably fail to see unsecure delegations. Since it's impractical to
...
... SIG and KEY.
The new types will have exactly the same syntax and semantics as
specified for SIG, KEY, and NXT ...
... 3) An RRSIG with a type-covered field of zero has undefined
semantics. The meaning of such a resource record may only be
defined by IETF Standards ...