> On May 11, 2018, at 7:29 AM, Daniel Margolis <[email protected]> wrote:
>
> If the number of resulting records is not one, senders MUST assume the
> recipient domain
> does not have an available MTA-STS policy and skip the remaining steps of
> policy
> discovery. (Note that lack of an available policy does not signal opting out
> of
> MTA-STS altogether if the sender has a previously cached policy for the
> recipient domain, as discussed in (#policy-application-control-flow), "Policy
> Application Control Flow".)
I think it is simpler to say that the text pertains only to policy discovery
when no previous policy is cached.
If a "none" policy cached, and the text record also goes away, I'd delete
the cached policy at that time.
As an implementor, if some other cached policy is in place, and it has
an associated non-empty id, I'd attempt to refresh the policy and store
any result under the empty id. That is, treat a missing or malformed TXT
RR as a TXT RR with an empty id when a policy other than "none" is cached.
Once a conformant TXT RR is back in place, the policy will be refreshed
again. I don't know whether that should be specified, but it seems a
prudent implementation strategy.
--
Viktor.
_______________________________________________
Uta mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/uta
