DNS Flag Day, Friday, Feb 1st, 2019

Thu Jan 31 03:49:46 UTC 2019

On Wed, Jan 30, 2019 at 6:23 PM Mark Andrews <marka at isc.org> wrote:

> You do realise that when the day was chosen it was just the date after
> which new versions of name servers by the original group of Open Source DNS
>

you do realize you are proposing to make a breaking change (breaking change
to a global system) on a friday.
delaying until the following monday would not have mattered to you, I'm
sure it's going to matter to other folks though.

thanks,
-chris

> developers would not have the work arounds incorporated?
>
> For ISC that will be BIND 9.14.0 and no that will not be available Feb 1
> but you can use the development version 9.13 which has had the code for a
> while now.
>
> Individual operators of resolvers will make their own decisions about when
> to deploy.
> --
> Mark Andrews
>
> On 31 Jan 2019, at 12:55, Christopher Morrow <morrowc.lists at gmail.com>
> wrote:
>
>
>
> On Wed, Jan 30, 2019 at 5:41 PM Jim Popovitch via NANOG <nanog at nanog.org>
> wrote:
>
>> On Wed, 2019-01-30 at 17:22 -0800, Matthew Petach wrote:
>> > Any chance this could wait until say the Tuesday
>> > *after* the Superbowl, when we aren't cutting an
>> > entire religion's worth of potential workers out of
>> > the workforce available to fix issues in case it
>> > turns out to be a bigger problem than is expected,
>> > and when we have less chance of annoying the
>> > vast army of football-loving fans of every sort?
>>
>> IIRC, DNS Flag Day was announce way before last years Super Bowl...
>> what did the people who aren't ready for DNS Flag Day do in the past
>> 364 days that they need a few more days to get ready for?
>>
>>
> Oh, so they had 365 days to plan the time of the event and still picked a
> friday for that event?
>
>
> https://www.opsview.com/resources/system-administrator/blog/three-reasons-why-not-make-major-it-changes-fridays
>
> I see.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20190130/192a8079/attachment.html>