[190414] in North American Network Operators' Group

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

Charter FYI - FW: [SANOG] Reliance Jio (AS55836) origating a /16

daemon@ATHENA.MIT.EDU (Ca By)
Sun Jul 3 15:32:32 2016

X-Original-To: nanog@nanog.org
In-Reply-To: <1087914762.17695.1467570260759.JavaMail.zimbra@baylink.com>
Date: Sun, 3 Jul 2016 12:32:27 -0700
From: Ca By <cb.list6@gmail.com>
To: "Jay R. Ashworth" <jra@baylink.com>
Cc: North American Network Operators' Group <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org

On Sunday, July 3, 2016, Jay R. Ashworth <jra@baylink.com
<javascript:_e(%7B%7D,'cvml','jra@baylink.com');>> wrote:

> ----- Original Message -----
> > From: "Suresh Ramasubramanian" <ops.lists@gmail.com>
>
> > On 03/07/16, 9:05 PM, "NANOG on behalf of Suresh Ramasubramanian"
> > <nanog-bounces@nanog.org on behalf of ops.lists@gmail.com> wrote:
> >
> >> Is anyone from Jio network engineering team on this list?
> >> I see AS55836 is originating  47.35.0.0/16 while the pool belongs to
> >> Charter. There's even /18 slices of the pool being announced by Charter.
> >
> > Acked / fixed in record time actually
>
> So carriers *still* aren't filtering incoming BGP announcements from
> subordinate carriers for sanity, huh?
>
>
Correct.

I am trying to chase down a hijack right now. AS12389 is passing a bad
route to Cogent, HE, GTT, and Hibernian. Email to noc@he got a quick fix,
still waiting on others.

Would have been nice for any of those folks to have used the correctly
published IRR, RPKI, or whois info instead of accepting and passing bad
routes.


Cheers,
> -- jr 'yes, yes, I know, but even still' a
> --
> Jay R. Ashworth                  Baylink
> jra@baylink.com
> Designer                     The Things I Think                       RFC
> 2100
> Ashworth & Associates       http://www.bcp38.info          2000 Land
> Rover DII
> St Petersburg FL USA      BCP38: Ask For It By Name!           +1 727 647
> 1274
>

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