Yep, we are in a much better position than we were in 2019. Most failures are
well < 1% when talking to authoritative servers. Broken firewall defaults have
been fixed and mostly deployed.
> On 27 Feb 2024, at 16:41, George Michaelson wrote:
>
> so yet again, I voice things which show my
so yet again, I voice things which show my ignorance, not yours. I
thank you for the gentle clue-stick hit, it was educational.
-G
On Tue, Feb 27, 2024 at 12:24 PM Shumon Huque wrote:
>
> On Tue, Feb 27, 2024 at 12:01 AM Mark Andrews wrote:
>>
>>
>> > On 27 Feb 2024, at 15:53, George
On Tue, Feb 27, 2024 at 12:01 AM Mark Andrews wrote:
>
> > On 27 Feb 2024, at 15:53, George Michaelson wrote:
> >
> > Not in any way to stop this specific draft, I wonder if this is a more
> > general principle of exercising code points which are not marked
> > "never to be used" and should
> On 27 Feb 2024, at 15:53, George Michaelson wrote:
>
> Not in any way to stop this specific draft, I wonder if this is a more
> general principle of exercising code points which are not marked
> "never to be used" and should also be raised cross-area, or in another
> place?
>
> Maybe the
Not in any way to stop this specific draft, I wonder if this is a more
general principle of exercising code points which are not marked
"never to be used" and should also be raised cross-area, or in another
place?
Maybe the best path is to get this proved here, and then embrace-extend.
I tend
Hi folks,
Mark Andrews and I have submitted a new draft on 'Greasing Protocol
Extension Points in the DNS'.
https://www.ietf.org/archive/id/draft-huque-dnsop-grease-00.html
(datatracker link:
https://datatracker.ietf.org/doc/draft-huque-dnsop-grease/ )
We'd like to see if there is
Dear WG,
Just a friendly reminder to submit your request for agenda time for the
upcoming DNSOP WG meeting at IETF 119. For instructions on requesting a
time slot during one of the sessions, please refer to the email below.
The DNSOP WG has two sessions scheduled as follows:
- Monday, March
