registry/data/aut-num/AS4242423270

aut-num:            AS4242423270
as-name:            TAAVI-AS
admin-c:            TAAVI-DN42
tech-c:             TAAVI-DN42
mnt-by:             TAAVI-MNT
remarks:            Open for peering, see https://taavi.wtf/dn42 for details.
remarks:            Current locations:
remarks:            * Helsinki, FI.
source:             DN42
Join as AS4242423270 2021-01-14 08:33:59 +01:00			`aut-num: AS4242423270`
			`as-name: TAAVI-AS`
			`admin-c: TAAVI-DN42`
			`tech-c: TAAVI-DN42`
			`mnt-by: TAAVI-MNT`
TAAVI-MNT: register separate homenet asn Justification for separate resources: * Having a separate AS and advertising only the related prefixes makes implementing the different routing policies between my home network and the rest of my core network much easier. It's likely that my home network will have multiple connections to the rest of dn42 in the future. * The separate IPv4 block allows me to grow the core network in the future without having to fragment the network or re-number existing addresses. Both blocks are fairly small, hopefully this is not an issue. * I have a clearnet /48 from my ISP, and using a similarly sized dn42 block makes address translation between the two networks much simpler. 2021-04-05 12:31:57 +02:00			`remarks: Open for peering, see https://taavi.wtf/dn42 for details.`
			`remarks: Current locations:`
			`remarks: * Helsinki, FI.`
Join as AS4242423270 2021-01-14 08:33:59 +01:00			`source: DN42`