FYI, I too like it and believe it should progress.
(We will likely implement it once it is published, too.)
Brian
On Tue, Oct 19, 2021 at 6:20 PM Bill Woodcock wrote:
>
>
> > On Oct 20, 2021, at 3:07 AM, Paul Hoffman
> wrote:
> >
> > Just noting that no one has said anything about this draft
Good folks,
I think that draft-ietf-dnsop-nsec3-guidance is fairly well boiled, so
I'm asking for a last call on moving toward a last call. The draft is
intentionally short and to the point but at the same time we've waited a
while to see what the industry would do with the guidance. Viktor's
Hi Paul,
> On 20 Oct 2021, at 02:07, Paul Hoffman wrote:
>
> Just noting that no one has said anything about this draft since it was
> published almost 6 months ago, and it is the topic of next week's interim
> meeting.
Thanks for that! The current version is a DNSOP working group adopted
Hi all,
although for me, as an implementer of an auth server, it's not too
important, I'd like to ask for clarification regarding the foreseen
reporting domain(s) setup in the (usual) case of many secondary auth
servers.
The draft says: "Each authoritative server SHOULD be configured with a
On 12/10/2021, Tony Finch wrote:
I view the term "in-bailiwick" as no longer suitable for use in careful
writing because its meaning has become thorougly confused and muddled.
I agree that without further qualification the meaning of "in-bailiwick"
isn't clear. And I'm personally not
