Profile photo of me and my dog Emma.

AS50555
net.kagl.me
Keaton Alexander Guger Lair
A Saskatchewian guy who does
stuff and things's network.
©2020-2021. All rights reserved.

  AS50555 is currently used for services hosted by myself, Keaton A.G. Lair. However I am hoping on building it to service my home usage along with family from across mainly Saskatchewan and hopefully around the world through specific disconnected PoPs.

  Generally I have a open peering policy, as a general rule I do not do peering tunnels. I will not accept peering requests if we can exchange routes in the same locality via an IX that we both peer with the router server(s) unless there is a specific technical reason why not. If you do not peer with a RS and we share an IX, I will most likely accept your peering request. I will accept PNI requests if we share a signifigant amount of traffic (>1gbps max over 1 month world wide traffic) and/or there is no cost towards me. Peers agree not to send any malicious traffic nor to abuse the peering connection. Peering is entirely at my whim and I may shutdown any connection at any time for any reason. I am willing to be more negioable when it comes to Saskatchewian peers. Most of my transit will be provided by AS54874, Red Lily, as I own Red Lily.

I currently announce 6 prefixes (2x IPv4, 4x IPv6)

44.135.136.0/21 Seperate routing policy, need seperate ASN. Don't expect to recieve this route. On grant from ARDC to NCSAPRN
104.167.214.0/24 Unicast Services (including this site) On borrow from Red Lily
2605:F440:5600::/40 Unicast Services (including this site) Permanent reassignment from Red Lily
2605:F440:5652::/47 Aggragate Route for kagl.me DNS Servers. Currently Unicast, will be Anycast.
2605:F440:5652::/48 ns2.kagl.me Authoritivate DNS Server. Currently Unicast, will be Anycast.
2605:F440:5653::/48 ns1.kagl.me Authoritivate DNS Server. Currently Unicast, will be Anycast.

I attempt to implement as secure routing as I can. So all prefixes from AS50555 will be IRR Valid and RPKI Valid. I also do RPKI ROV, BCP38 enforcement, etc. I place records in as many databases as I can get a mntner into. Currently I place records in ARIN, RIPE, AFRINIC and ALTDB and hopefully I can add NTTCOM, RADB and BELL to that. route objects are not placed in RIPE or AFRINIC as all my prefixes held are from ARIN. I recommend and encourage that peers and other networks enforce strict RPKI ROV and AS-SET enforcement against AS50555. See the table below for specific records:

AS-KEATONAGLAIR Main AS-SET. ARIN, RIPE, AFRINIC, ALTDB.
RS-KEATONAGLAIR Main route set, includes all above prefixes (minus NCSAPRN). ARIN, RIPE, AFRINIC, ALTDB.
MNT-KAGLL Only ARIN Maintainer that should be trusted. ARIN
KEATONAGLAIR Only RIPE Maintainer that should be trusted. RIPE
KEATONAGLAIR-MNT Only AFRINIC Maintainer that should be trusted. AFRINIC
MAINT-KEATONAGLAIR Only ALTDB Maintainer that should be trusted. ALTDB
KAGL-ARIN Only ARIN Handle that should be used. ARIN
KAGL Only RIPE or AFRINIC Handle that should be used. RIPE, AFRINIC