[as112-ops] New AS112 node (sort of)

[Stephen Fulton]

A follow-up question for folks:

When announcing AS112 to your transits, have their required LOA's?  Have
"their" transits?  What have you found is sufficient to all parties?

I ask because I have a dual role, one at TorIX and $dayjob at a TorIX
peer which donates transit to TorIX, and I'd like to announce the TorIX
AS112 node to my $dayjob transits as well.

Thanks,

-- 
Stephen Fulton
Toronto Internet Exchange, Operations Group
http://torix.ca

On 2018-02-06 10:06 PM, Stephen Fulton wrote:
> Hi Joe,
>
> Currently the AS112 node is announced only to the TorIX route-servers,
> which ~ 80% of TorIX's peers use.  TekSavvy does not, so in order to
> reach the AS112 node, they would have to peer with the TorIX services
> peer directly.  As for eGate, they do peer with the route-servers but
> may very well be preferring another AS112 for whatever routing policy
> reason, like due to having the same BGP local preference for prefixes
> received by the route-servers as their transits. 
>
> As for disco, Nistor has strong feelings about that. :)
>