> On 6 Jul 2023, at 12:32, Ted Lemon wrote:
>
> It’s not a problem to validate before translating if you’re a full service
> resolver.
Ted you are missing the point. It is impossible to *reliably* run a validating
client
behind a DNS64 server. DNS64 uses CD in a manner that is
On Thu, Apr 20, 2023 at 11:46 AM Paul Wouters wrote:
>
> > ### CNAME chaining
> >
> > In §3.2 we see the text "Another issue with CNAME records is that they
> must
> > not point to another CNAME" provided, with no reference. But CNAME
> chains are
> > in heavy use on the internet in practice
On Thu, Mar 30, 2023 at 4:52 PM Erik Nygren wrote:
> Hello,
>
> Thank you for pulling together this draft! Having worked on related
> systems a number of times it will be valuable to have something here
> standardized.
>
Thanks for the review Erik, sorry for our very late response, and thanks
I’ll repeat that it is a bad idea to make this an RFC. I’m saying this despite
adding
this to named.
It is perpetuating DNS64 which does not work with DNSSEC. It sends the wrong
signal
that DNS64 is a good protocol to deploy when we know that it breaks lots of
things.
The better solution
Hi Duane,
On Wed, Jul 5, 2023 at 18:32, Wessels, Duane
<[dwessels=40verisign@dmarc.ietf.org](mailto:On Wed, Jul 5, 2023 at 18:32,
Wessels, Duane < wrote:
> On Jun 30, 2023, at 2:32 PM, Joe Abley wrote:
>
>> I wonder whether another subsection of section 2 would be useful to discuss
>>
All
The authors of draft-ietf-dnsop-avoid-fragmentation worked with different
implementers to expand upon the index of Known Implementations, and what
they implement specifically.
The chairs would like to have a one week follow up Working Group Last Call
comment period. We are looking for
> On Jun 30, 2023, at 2:32 PM, Joe Abley wrote:
>
>
>
> I have read -04. i like it. I think it's useful and sensible and it should be
> published. Whether this particular rev is ready for publication I would say
> depends on whether the authors disagree with all the pedantic nonsense that
Hi Libor,
On 6/26/23 13:56, libor.peltan wrote:
My concerns are based on following situation. Imagine that:
- two servers publish inconsistent CDNSKEY+CDS records for some reason, e.g.
misconfiguration. This is the exact thing that the draft tries to address.
- this persists for quite
On 4 Jul 2023, at 10:03, Peter Thomassen wrote:
> Hi Scott,
>
> Thank you very much for your feedback -- responses inline.
> o "inline" the actual definition, but that was just a feeling.)
>
>> Also, “Signaling Name” sounds
>> confusing compared to the Signaling Domain. Would it be easier to
Erik
I placed your excellent comments into the author's issue tracker, then we
decided to split them up into separate issues.
Take a look to confirm. If anything is wrong, it's one me
tim
APEX domains, and hostnames vs domains
I think firmware size is a perfectly reasonable and sufficient motivation for
this draft, but I don't think it can be described as "performance".
--Ben Schwartz
From: Christian Amsüss
Sent: Wednesday, July 5, 2023 12:17 PM
To: Ben Schwartz
Cc: Martine Sophie
From: DNSOP on behalf of Viktor Dukhovni
Quoting from the draft:
...
> If the initial TLSA base domain is the start of a secure CNAME chain,
> clients MUST first try to use the end of the chain as the TLSA base
> domain, with fallback to the initial base domain, as described
All
Thanks for all the feedback on this document. We chairs understand there
are some questions around privacy considerations.
However, there was no comments on DNSOP adopting this work to resolve those
issues. The document can go to the Independent
Stream Editor and we can point them to this
Hello Ben,
picking one of the points in the thread and leaving the rest to another
subthread:
> > We have a paper on the performance benefits just accepted for CoNEXT,
> > which we will cite once it is published. An early pre-print (the final
> > paper underwent some major revisions though) is
Momoka
Thanks for making DNSOP aware of this. We encourage anyone with comments
on the document adoption to reach out.
Everything I've heard and read on this work (wearing no hats) is that this
is good work and should be adopted.
thanks
tim
On Tue, Jul 4, 2023 at 5:15 AM Momoka Yamamoto
From: Wes Hardaker
Ben Schwartz writes:
A few comments:
1. the MUST NOT in the first paragraph in 5.2 really feels like it should
be a SHOULD NOT. Though its not wise, there could be scenarios where
someone really wants to do it and if they feel it's operationally
possible then they should
All
The Working Group Last Call has completed and the chairs thank everyone for
their comments.
It appears that the authors have addressed all issues, and the document is
ready to advance.
tim
On Wed, Jun 21, 2023 at 11:00 AM Tim Wicinski wrote:
> All
>
> This starts a Working Group Last
Thanks James,
I will update the Drink POC link
Warmly,
Roy
> On 7 Jun 2023, at 22:10, James Gannon via Datatracker
> wrote:
>
> Reviewer: James Gannon
> Review result: Ready
>
> Hi Folks,
> I am the assigned DNSDIR reviewer for this draft.
> Thank you for a well-written draft that appears
Yaron, many thanks for your review. Comments inline:
> On 26 Jun 2023, at 13:24, Yaron Sheffer via Datatracker
> wrote:
>
> Reviewer: Yaron Sheffer
> Review result: Has Nits
>
> I am not a DNS expert so these may or may not be real issues. But I would
> appreciate the authors' clarifications.
Viktor, thanks for your feedback. Comments inline.
> On 26 Jun 2023, at 22:13, Viktor Dukhovni wrote:
>
> On Thu, Jun 08, 2023 at 11:59:59AM +0200, Benno Overeinder wrote:
>
>> This starts a two week Working Group Last Call process, and ends on:
>> June 22nd, 2023.
>
> I hope my feedback is
Hi Matt, Di,
Thank you for the follow-up.
We released a new version that addresses both your reviews. FWIW, a diff to
track the changes can be seen at:
https://author-tools.ietf.org/iddiff?url1=draft-ietf-dnsop-structured-dns-error-03=draft-ietf-dnsop-structured-dns-error-04=--html
Cheers,
A New Internet-Draft is available from the on-line Internet-Drafts
directories. This Internet-Draft is a work item of the Domain Name System
Operations (DNSOP) WG of the IETF.
Title : Structured Error Data for Filtered DNS
Authors : Dan Wing
A New Internet-Draft is available from the on-line Internet-Drafts
directories. This Internet-Draft is a work item of the Domain Name System
Operations (DNSOP) WG of the IETF.
Title : Fragmentation Avoidance in DNS
Authors : Kazunori Fujiwara
Paul
23 matches
Mail list logo
