nanog mailing list archives
Re: DOD prefixes and AS8003 / GRSCORP
From: Tom Beecher <beecher () beecher cc>
Date: Fri, 12 Mar 2021 07:32:49 -0500
However, it appears that a Certificate of Good Standing is not required or ARIN didn't validate it in this case.
You don't know what ARIN did or did not do, or really anything about the circumstances surrounding this other than what is gleanable from public records. It's not a good look to chuck rocks at them like this. Mr. Curran has helpfully provided the link to report suspected fraud. That's the best place to take this discussion. On Fri, Mar 12, 2021 at 6:36 AM Siyuan Miao <aveline () misaka io> wrote:
Hi John, My biggest concern is why the AS8003 was assigned to the company (GLOBAL RESOURCE SYSTEMS, LLC) even before its existence. When we were requesting resources or transfers, ARIN always asked us to provide a Certificate of Good Standing and we had to pay the state to order it. However, it appears that a Certificate of Good Standing is not required or ARIN didn't validate it in this case. Regards, Siyuan On Fri, Mar 12, 2021 at 7:17 PM John Curran <jcurran () arin net> wrote:On 11 Mar 2021, at 7:56 AM, Siyuan Miao <aveline () misaka io> wrote: Hi Folks, Just noticed that almost all DOD prefixes ( 7.0.0.0/8,11.0.0.0/8,22.0.0.0/8 and bunch of /22s) are now announced under AS8003 (GRSCORP) which was just formed a few months ago. It looks so suspicious. Does anyone know if it's authorized? Siyuan - If you have concerns, you can confirm whether these IP address blocks are being routed as intended by verification with their listed technical contacts - e.g. https://search.arin.net/rdap/?query=22.0.0.0 As I noted on this list several weeks back - "lack of routing history is not at all a reliable indicator of the potential for valid routing of a given IPv4 block in the future, so best practice suggest that allocated address space should not be blocked by others without specific cause. Doing otherwise opens one up to unexpected surprises when issued space suddenly becomes more active in routing and is yet is inexplicably unreachable for some destinations." Thanks! /John John Curran President and CEO American Registry for Internet Numbers
Current thread:
- Re: DOD prefixes and AS8003 / GRSCORP, (continued)
- Re: DOD prefixes and AS8003 / GRSCORP Eric Dugas via NANOG (Mar 11)
- Re: DOD prefixes and AS8003 / GRSCORP Javier Henderson (Mar 11)
- Re: DOD prefixes and AS8003 / GRSCORP Filip Hruska (Mar 11)
- Re: DOD prefixes and AS8003 / GRSCORP Alain Hebert (Mar 11)
- Re: DOD prefixes and AS8003 / GRSCORP Siyuan Miao (Mar 11)
- Re: DOD prefixes and AS8003 / GRSCORP Javier Henderson (Mar 11)
- Re: DOD prefixes and AS8003 / GRSCORP Eric Dugas via NANOG (Mar 11)
- Re: DOD prefixes and AS8003 / GRSCORP Siyuan Miao (Mar 12)
- Re: DOD prefixes and AS8003 / GRSCORP John Curran (Mar 12)
- Re: DOD prefixes and AS8003 / GRSCORP Nick Hilliard (Mar 12)
- Re: DOD prefixes and AS8003 / GRSCORP Siyuan Miao (Mar 12)
- Re: DOD prefixes and AS8003 / GRSCORP Tom Beecher (Mar 12)
- Re: DOD prefixes and AS8003 / GRSCORP Owen DeLong via NANOG (Mar 15)
- Re: DOD prefixes and AS8003 / GRSCORP Mel Beckman (Mar 15)
- Re: DOD prefixes and AS8003 / GRSCORP Mel Beckman (Mar 15)
- Re: DOD prefixes and AS8003 / GRSCORP Christopher Morrow (Mar 15)
- Re: DOD prefixes and AS8003 / GRSCORP Mel Beckman (Mar 15)
- Re: DOD prefixes and AS8003 / GRSCORP Christopher Morrow (Mar 15)
- Re: DOD prefixes and AS8003 / GRSCORP Mel Beckman (Mar 15)
- Re: DOD prefixes and AS8003 / GRSCORP John Curran (Mar 15)
- Re: DOD prefixes and AS8003 / GRSCORP Mel Beckman (Mar 15)