Hi
I support the publication of this document.
Oli
(SWITCH ; ch./li.)
___
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
Hi
Am 20.04.2024 um 12:13 schrieb Peter Thomassen:
[...]
The main question then is to get implementations updated. I'm thus
copying a few implementers so they can comment w.r.t. making this change
in their implementation. I suppose that barring their objections, it's
fine to go ahead?
Updat
Hi
I support the draft progressing to an RFC. Switch (.ch / .li ) is
considering an implementation for our DS automation process based on
this draft.
Best regards
Oli
___
DNSOP mailing list -- dnsop@ietf.org
To unsubscribe send an email to dnsop-le
Hi
(I hope this doesn't mess up threading.. our mail system is apparently
not prepared to handle duplicate mailing list + cc messages ...)
Since Oli Schacher claims to have this draft already implemented, I
wonder, what decisions did you take when implementing this?
Our implement
Thanks for this work — it’s very helpful to have the operational
considerations for DS automation written down in one place.
I agree with Matthew’s point that these may not always be 'best
practices', but rather design decisions that depend on operational context.
For example, the recommendat
Hi
On 28.05.2025 14:40, Ondřej Surý wrote:
Hey everyone,
this starts a Working Group Last Call for draft-ietf-dnsop-cds-consistency
Current versions of the draft is available here:
https://datatracker.ietf.org/doc/draft-ietf-dnsop-cds-consistency/
The Current Intended Status of this document
