Discuss mailing list

[Coyo <coyo AT darkdna.net>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Thankfully, there is such a thing as private ASNs and private IPs.

There are actually quite a lot of private ASNs, which can help if you
are designing a subversive "private" BGP-based private network.

I like VPNs, but I like RPNs (real private networks) more. The
difference is that RPNs do not rely on tunneling over existing
infrastructure to work. Many VPN softwares can tunnel over private
networks designed specifically for that just fine, including 100%
private non-globally-routable Ethernet-based WANs and RANs (wide-area
network and regional-area network, respectively), which can use
nothing but private ASNs and IPs. With VPN software, you don't need
global routability, only routability to the next VPN node.

Since DNS relies on lower layers such as UDP, TCP and IP to work,
being technically an application-layer protocol, such network designs
have unusual ramifications for DNS traffic patterns. Nameservers
running on such a network need to be carefully placed and designed to
ensure a non-globally-routable inter-network functions as an end-user
would expect.

On 3/6/2014 9:28 AM, Coyo wrote:
> Let me check...
> 
> according to ARIN, the American Registry for Internet Numbers (a 
> partner and delegate of IANA and ICANN), two-byte ASNs are nearing 
> depletion. Four-byte ASNs are somewhat easier to get.
> 
> Also, according to
> 
> https://www.arin.net/fees/fee_schedule.html#asns
> 
> an ASN, assuming you are approved, costs $550 USD to register the 
> first time, and $100 USD every year after that. If you fail to make
> a payment, they take the ASN from you, whether you've reconfigured
> your routers or not.
> 
> On 3/6/2014 8:02 AM, Alejandro Bonet wrote:
>> As i understand in your last coment speech, ICANN is responsable 
>> to assign AS numbers arbitrarily or with money base?
> 
> 
> 
> 
> 
> -------- You are a member of the OpenNIC Discuss list. You may
> unsubscribe by emailing
> discuss-unsubscribe AT lists.opennicproject.org
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJTGJZXAAoJEDEXTUGm1DyUVu8H/1jGyQU2ypPQtTFOVKFy1BKo
7cRBTXLAq2q6B+CciPkhZZBOX/feo+ZEH4uylGVlm+d0CCi63JHsKt77uRoTBxdP
KzTyoqmAUxZR1EfcpQUf2pHPEQNcUXHi1tzHzOdCCcQ0FA3e9Sjps3DzIDbDaGNR
KL82cFy0PVAIPKxvN6x+ybdIxeqLIo4769HgM9f/AektIZ0kKsWgLS9KHudtYEJW
cdu4vBpM1D+6oURtcv7R/l8LPEnHDxDu20XoMj6ujcjioZfaphxKWiu+Gtypb55h
efSQOjgVeq8pdJF2D6es1w2HqetjnIwFb3mgBkyIGK/w+U2VaxWIhrV4KwEOcDg=
=9TEO
-----END PGP SIGNATURE-----