Hi John, Thanks for the input, and you’re correct that I simplified NOTIFY unnecesasrily. I agree that the semantics don’t line up with what EXPIRE needs. NOTIFY is something happened, poll sooner; where EXPIRE is a single, self-contained, authenticated deletion with no follow-up required. Appreciate the clarification.
Best, Duane > On Nov 21, 2025, at 19:54, John Levine <[email protected]> wrote: > > It appears that Duane Powers <[email protected]> said: >> Hi Kevin, >> >> Great timing on this, I've just spent a bit of time considering it. >> >> The difficulty is that NOTIFY’s existing semantics and operational >> expectations don’t really line up with what EXPIRE needs to do. >> >> Operationally, NOTIFY is almost always constrained to authoritative -> >> secondary, with specific firewall, ACL, and traffic handling provisions. > > Not any more. Generalized notify goes from one authoritative to another, > typically up the tree. > > Nonetheless I agree with you that it's not the right tool here. All of > the existing uses of NOTIFY say "something happened so do a poll you > were planning to do, but do it sooner." EXPIRE seems rather unlike > that. > > R's, > John >
_______________________________________________ DNSOP mailing list -- [email protected] To unsubscribe send an email to [email protected]
