[31834] in North American Network Operators' Group
Re: DOS Attacks and reliable network contact data.
daemon@ATHENA.MIT.EDU (bmanning@vacation.karoshi.com)
Sun Oct 22 20:48:36 2000
From: bmanning@vacation.karoshi.com
Message-Id: <200010230047.AAA00352@vacation.karoshi.com>
To: jshaw@insync.net (Joe Shaw)
Date: Mon, 23 Oct 2000 00:47:58 +0000 (UCT)
Cc: raistlin@tacorp.net (Jason Slagle), nanog@nanog.org
In-Reply-To: <Pine.GSO.4.21.0010221507490.29485-100000@vellocet.insync.net> from "Joe Shaw" at Oct 22, 2000 07:13:57 PM
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Errors-To: owner-nanog-outgoing@merit.edu
Which JPNIC block? The original JPNIC delegation was from SRI,
predating NSI, APNIC and ARIN. And no, there is no standard for
whois data that is published, let alone publishing at all.
>
>
>
> Ah, now I see the issue. That's insanely sparse on the
> information. Since I'm really quite ignorant in the area, who gives JPNIC
> the power to assign netblocks? APNIC I presume, after checking with
> APNIC's whois database. I guess there's no policy for standards and the
> like. How do things like standards get enforced amongst registry entities
> outside the US?
>
> --
> Joseph W. Shaw - jshaw@insync.net
> Sr. Security Specialist for <Big company not to be named>.
>
> On Sun, 22 Oct 2000, Jason Slagle wrote:
>
> > Yes, but even geektools falls flat on it's face for lets say
> > 210.251.128.255.
> >
> > :sigh: I really wish we could get a common format for these.
> >
> > I really like the ripe style databases.
>
>
>
