I read draft-dnsop-deleg-00.
It proposes new name resolution using only information on the parent side.
In the past, the dnsop WG debated parent centric name resolution
and child centric, and some people did not like parent centric.
If people prefer parent-centric/parent-only name resolution,
Moin!
On 30 Jan 2024, at 1:00, Wes Hardaker wrote:
> Edward Lewis writes:
>> But the DELEG resource record enables redesigning (portions or all of)
>> the DNS. I think the point is that DELEG allows the DNS namespace to
>> continue to be published while there are transitions in the DNS
>>
Edward Lewis writes:
> # 1.6. Facilities
> #
> #The DELEG record is extensible in such a way that future innovations
> #in the domain name system, such as new methods of secure transport,
> #message encoding, error reporting, etc, does not depend on a re-
> #design of the DNS.
IESG Secretary writes:
> The Domain Name System Operations (dnsop) WG will hold a virtual
> interim meeting on 2024-01-30 from 18:00 to 19:00 Europe/Amsterdam
> (17:00 to 18:00 UTC).
I'm sadly very day-job conflicted with this slot, but greatly look
forward to watching the replay afterward (I
The following errata report has been verified for RFC8552,
"Scoped Interpretation of DNS Resource Records through "Underscored" Naming of
Attribute Leaves".
--
You may review the report below and at:
https://www.rfc-editor.org/errata/eid7067
The following errata report has been verified for RFC8552,
"Scoped Interpretation of DNS Resource Records through "Underscored" Naming of
Attribute Leaves".
--
You may review the report below and at:
https://www.rfc-editor.org/errata/eid7066
Whoops, apologies, the previous reply was in my Drafts and I hit send on
the wrong version.
I will ask the IANA to update the reference to be RFC4340, and include a
link to this thread.
W
On Mon, Jan 29, 2024 at 1:27 PM, Warren Kumari wrote:
> On Mon, Jan 15, 2024 at 7:51 PM, John Levine
On Mon, Jan 15, 2024 at 7:51 PM, John Levine wrote:
> It appears that Paul Wouters said:
>
> Section 4.1.2. says:
> | URI| _dccp | [RFC7566] |
>
> I think this might have been part of a list used to "reserve" the names of
> (transport) protocols, so that
Thanks all, done!
W
On Tue, Jan 16, 2024 at 5:01 AM, Joe Abley wrote:
> Hi Warren,
>
> On 15 Jan 2024, at 22:49, Warren Kumari wrote:
>
> Seeing as the document says you should "expect: flag: aa to be present",
> it does seem like it would be better if it also said: "expect: flag: do to
> be
The following errata report has been held for document update
for RFC8906, "A Common Operational Problem in DNS Servers: Failure to
Communicate".
--
You may review the report below and at:
https://www.rfc-editor.org/errata/eid7689
All
This is a followup on our Working Group Last Call for
draft-ietf-dnsop-dnssec-bootstrapping is ongoing until Saturday February 3,
2024,
There has been support for publication, but we are always looking for more
feedback.
The comments raised appear to have been resolved by the authors. If
Hi Authors,
Just a note/reminder that I am stepping down as an AD in March. I don’t think
that I’ve seen any reply to my DISCUSS comments (perhaps the authors and/or WG
are still discussing the resolution), but if you are able to speed this up at
all so that I can clear my discuss before I
12 matches
Mail list logo
