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

[Joe Abley]

I think the whois-accessible metadata for the nets concerned points to
DNS-OARC, and I'm guessing they could probably post a general-purpose
LOA on as112.net if someone asked them nicely.

I seem to recall, years ago, there was some talk of writing up a LOA
as an RFC so that people could just point transit providers at that.
Perhaps we should have done that in an appendix of RFC7534. Probably
your average transit provider is going to be happier with a
conventional-looking scan of a letter with a signature, though, I
guess.

Back when I did these kinds of things at ISC and Afilias I do remember
being asked for a LOA but when I said "no that's silly" they stopped
asking. That was eleventy years ago though so things might have
changed.

> On Feb 7, 2018, at 00:09, Stephen Fulton <sfulton at torix.ca> wrote:
>
> 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. :)
>>
>
> _______________________________________________
> as112-ops mailing list
> as112-ops at lists.dns-oarc.net
> https://lists.dns-oarc.net/mailman/listinfo/as112-ops