I really love this draft and would like to see browser side implementation for
the benefit of customers user experience.
Today several services are implemented on top of DNS to filter malicious or
unwanted traffic in an effective way, but customers cannot distinguish the
blocking from a
Hi All
We had so much fun the first timeActually this chair wishes to thank Mr
Abley and Mr Huston for catching our error so quickly, and we apologize for
any and all inconvenience.
I did go back and looked at the history AND also reread the document.
I do wish to point out that there are 4
All
I know this was a bit longer than a week, but we wanted to receive some
confirmations from folks with questions on implementations. We've received
that, and the chairs feel the consensus is to move forward.
Thanks
tim
On Tue, Sep 19, 2023 at 2:27 PM Tim Wicinski wrote:
> (forgive my
Tim Wicinski has requested publication of
draft-ietf-dnsop-avoid-fragmentation-15 as Best Current Practice on behalf of
the DNSOP working group.
Please verify the document's state at
https://datatracker.ietf.org/doc/draft-ietf-dnsop-avoid-fragmentation/
> Le 9 oct. 2023 à 20:34, Paul Wouters a écrit :
>
> On Oct 9, 2023, at 10:02, Ben Schwartz
> wrote:
>>
>>
>> This is fun to think about, but it seems to me that these networks should
>> avoid any reliance on the ICANN DNS tree. I doubt that any network of space
>> probes on Io can
> Le 9 oct. 2023 à 19:30, George Michaelson a écrit :
Thanks for constructive comments. appreciated.
>
> I wonder if some kind of "limited licence local signing key" model
> could be used, to get a signed permit from a "real" TA in the DNS to
> specify the zone(s) that a limited licence key
