> On 31 Oct 2023, at 23:38, Paul Wouters wrote:
>
> On Oct 31, 2023, at 19:17, Frederico A C Neves wrote:
>>
>> Dear David,
>>
>> Section 7 of the draft is sufficiently clear, precise, and complete.
>>
>> This registration at the time it is approved by the IESG, taking in
>> account the
On 1 Nov 2023, at 12:50, Frederico A C Neves
wrote:
> Because of the additive nature of the spec on cascading/concatenating
> error situations I would guess that the authors opted for the shortest
> node name available to fit as much errors as possible.
Also if the only remaining point of
Paul,
On Wed, Nov 01, 2023 at 12:38:09AM +0100, Paul Wouters wrote:
> On Oct 31, 2023, at 19:17, Frederico A C Neves wrote:
> >
> > Dear David,
> >
> > Section 7 of the draft is sufficiently clear, precise, and complete.
> >
> > This registration at the time it is approved by the IESG,
On Oct 31, 2023, at 19:17, Frederico A C Neves wrote:
>
> Dear David,
>
> Section 7 of the draft is sufficiently clear, precise, and complete.
>
> This registration at the time it is approved by the IESG, taking in
> account the fact that currently there is no other request for TXT _er
> on
Dear David,
On Tue, Oct 24, 2023 at 07:39:27PM +, 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
>
Dear Frederico A C Neves and Paul Wouters (cc: dnsop WG),
Following up on this; as the designated experts for the Underscored and
Globally Scoped DNS Node Names registry, can you review the proposed
registration in draft-ietf-dnsop-dns-error-reporting-06 for us? Please see:
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-dns-error-reporting-06 for us? Please see:
