Thank you, I have requested IETF LC be started on this document.
W
On Thu, Apr 11, 2024 at 9:03 AM, Peter Thomassen wrote:
> Dear DNSOP,
>
> Here's a quick change log, all are editorial:
>
> - Editorial changes from AD Review
> - Updated implementation section
> - Change capitalization of term
The IESG has received a request from the Domain Name System Operations WG
(dnsop) to consider the following document: - 'Automatic DNSSEC Bootstrapping
using Authenticated Signals from the
Zone's Operator'
as Proposed Standard
The IESG plans to make a decision in the next few weeks, and so
Dear Frederico A C Neves and Paul Wouters (cc: dnsop WG),
As the designated experts for the Underscored and Globally Scoped DNS Node
Names registry, can you review the proposed registration in
draft-ietf-dnsop-dnssec-bootstrapping-08 for us? Please see
https://datatracker.ietf.org/doc/draft-iet
On Fri, 12 Apr 2024, David Dong via RT wrote:
Dear Frederico A C Neves and Paul Wouters (cc: dnsop WG),
As the designated experts for the Underscored and Globally Scoped DNS Node
Names registry, can you review the proposed registration in
draft-ietf-dnsop-dnssec-bootstrapping-08 for us? Pleas
Hi Paul,
On 4/12/24 22:36, Paul Wouters wrote:
However, I would urge the authors/WG to pick a less generic and more
specific name than "_signal", such as "_dnssec-bootstrap". Especially
because there is also the well known "Signal" message client. Also,
in case of future different signaling, the
It appears that Peter Thomassen said:
>The _signal label generically indicates that ns2.foobar.fi likes to signal
>something about nohats.ca. Its presence is needed to allow separating the
>object from the source without ambiguity.
>
>We could change _signal to something else, but not to _dnsse
