[194136] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: [NOC] ARIN contact needed: something bad happens with legacy IPv4

daemon@ATHENA.MIT.EDU (William Herrin)
Fri Mar 17 14:19:53 2017

X-Original-To: nanog@nanog.org
X-Really-To: <nanog@nanog.org>
In-Reply-To: <1ECCAF19-D44B-4C13-88E8-F43A537078B4@arin.net>
From: William Herrin <bill@herrin.us>
Date: Fri, 17 Mar 2017 14:08:01 -0400
To: Mark Kosters <markk@arin.net>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org

On Fri, Mar 17, 2017 at 1:42 PM, Mark Kosters <markk@arin.net> wrote:
> On 3/17/17, 12:26 PM, "NANOG on behalf of William Herrin" <
nanog-bounces@nanog.org on behalf of bill@herrin.us> wrote:
>>     Hmm. That sounds like an ARIN-side bug too. ARIN's code responded to
>>     corrupted data by zeroing out the data instead of using the last
known good
>
> there were no bugs in ARIN=E2=80=99s software in regards to this issue. W=
e
followed exactly what RIPE told us to do.

Hi Mark,

That shot my eyebrow up. You misspoke here, right? There's no bug -solely
because- you did what the design said to do? The design calls for some
self-check information and it's not a critical design bug to zero-out the
publish if the self-check fails?

Regards,
Bill Herrin



--=20
William Herrin ................ herrin@dirtside.com  bill@herrin.us
Dirtside Systems ......... Web: <http://www.dirtside.com/>

home help back first fref pref prev next nref lref last post