Hi all,
Following up on this; does the group agree that "_dnssec" is OK?
Thank you.
Best regards,
David Dong
IANA Services Sr. Specialist
On Mon Apr 22 11:42:15 2024, scott.r...@nist.gov wrote:
> On 20 Apr 2024, at 19:38, Paul Wouters wrote:
>
> > On Sat, 20 Apr 2024, Peter Thomassen wrote:
On 20 Apr 2024, at 19:38, Paul Wouters wrote:
> On Sat, 20 Apr 2024, Peter Thomassen wrote:
>
>> The authors certainly don't insist, but we'd need to pick a suitable
>> replacement for the "_signal" label.
>>
>> John proposed "_dnssec-signal" elsewhere in this thread.
>>
>> The authors would
Hello all,
We (Knot DNS) don't see any issue with updating our implementation if necessary.
Personally I'm fine with the current format.
Daniel
On 4/21/24 01:38, Paul Wouters wrote:
On Sat, 20 Apr 2024, Peter Thomassen wrote:
The authors certainly don't insist, but we'd need to pick a
On Sat, 20 Apr 2024, Peter Thomassen wrote:
The authors certainly don't insist, but we'd need to pick a suitable
replacement for the "_signal" label.
John proposed "_dnssec-signal" elsewhere in this thread.
The authors would like to note that adding "_dnssec-" eats up 8 more bytes,
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?
Hi Paul,
The authors certainly don't insist, but we'd need to pick a suitable replacement for the
"_signal" label.
John proposed "_dnssec-signal" elsewhere in this thread.
The authors would like to note that adding "_dnssec-" eats up 8 more bytes, increasing
chances that bootstrapping will
If the authors insist, then as DE of this registry, this entry is okay.
My point below still holds, but I will leave that up to the authors and IESG.
Paul
Sent using a virtual keyboard on a phone
> On Apr 19, 2024, at 18:47, David Dong via RT
> wrote:
>
> Hi Paul,
>
> Just a ping on this;
Hi Paul,
Just a ping on this; thank you.
Best regards,
David Dong
IANA Services Sr. Specialist
On Sat Apr 13 01:24:13 2024, pe...@desec.io wrote:
> 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
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
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,
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?
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
12 matches
Mail list logo
