API tools faq
paste
brannondorsey

amprnet-allocation-request

brannondorsey
Sep 14th, 2019
375
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 8.02 KB | None | 0 0
raw download clone embed print report
  1. [AMPRNet] Allocation request KC3LZO
  2.  
  3.  
  4. ----------------------------------------------------------------------------
  5. 1. Subnet Assigned (CIDR notation): 44.56.207.0/24
  6.  
  7. a. Does your NSP (or you) need an ALTDB RDB
  8. route object entered for this prefix? (Y/N):
  9. ----------------------------------------------------------------------------
  10.  
  11. Not sure, would you mind elaborating a bit on this? I can follow up and
  12. ask this question of my NSP (Vultr.com) directly.
  13.  
  14.  
  15. ----------------------------------------------------------------------------
  16. 2. ASN that will advertise the subnet:
  17. ----------------------------------------------------------------------------
  18.  
  19. AS 20473 Choopa, LLC.
  20.  
  21. I am going to use Vultr.com to advertise my IPv4 subnet, and best I can
  22. tell, this is Vultr's ASN. (Vultr seems to be a subsidiary of Choopa). I've
  23. sent a follow up email to Vultr support to confirm this, and I will follow
  24. up if the ASN is different than the one listed above.
  25.  
  26.  
  27. ----------------------------------------------------------------------------
  28. 3. Your/Organization name:
  29. ----------------------------------------------------------------------------
  30.  
  31. Brannon Dorsey
  32.  
  33.  
  34. ----------------------------------------------------------------------------
  35. 4. Your/Organization postal address:
  36. ----------------------------------------------------------------------------
  37.  
  38. [REDACTED], Philadelphia PA
  39.  
  40.  
  41. ----------------------------------------------------------------------------
  42. 5. Your/Organization email:
  43. ----------------------------------------------------------------------------
  44.  
  45. [email protected]
  46.  
  47.  
  48. ----------------------------------------------------------------------------
  49. 6. Admin Representative name:
  50. ----------------------------------------------------------------------------
  51.  
  52. Brannon Dorsey
  53.  
  54.  
  55. ----------------------------------------------------------------------------
  56. 7. Admin Representative callsign:
  57. ----------------------------------------------------------------------------
  58.  
  59. KC3LZO
  60.  
  61.  
  62. ----------------------------------------------------------------------------
  63. 8. Admin Representative email:
  64. ----------------------------------------------------------------------------
  65.  
  66. [email protected]
  67.  
  68.  
  69. ----------------------------------------------------------------------------
  70. 9. Admin Representative telephone:
  71. ----------------------------------------------------------------------------
  72.  
  73. [REDACTED]
  74.  
  75.  
  76. ----------------------------------------------------------------------------
  77. 10. Tech Representative name:
  78. ----------------------------------------------------------------------------
  79.  
  80. Brannon Dorsey
  81.  
  82.  
  83. ----------------------------------------------------------------------------
  84. 11. Tech Representative callsign:
  85. ----------------------------------------------------------------------------
  86.  
  87. KC3LZO
  88.  
  89.  
  90. ----------------------------------------------------------------------------
  91. 12. Tech Representative email:
  92. ----------------------------------------------------------------------------
  93.  
  94. [email protected]
  95.  
  96.  
  97. ----------------------------------------------------------------------------
  98. 13. Tech Representative telephone:
  99. ----------------------------------------------------------------------------
  100.  
  101. [REDACTED]
  102.  
  103.  
  104. ----------------------------------------------------------------------------
  105. 14. Estimated number of real hosts:
  106. ----------------------------------------------------------------------------
  107.  
  108. 3-10, with the chance to grow significantly to dozens of hosts
  109.  
  110.  
  111. ----------------------------------------------------------------------------
  112. 15. Describe how this subnet will be used and how that usage
  113. will benefit the Amateur Radio community:
  114. ----------------------------------------------------------------------------
  115.  
  116. I plan on using this subnet to do general BGP peering and experimentation,
  117. as well as to configure a home network of several servers that are publicly
  118. routable. I am an active member of Philly 2600 <https://philly2600.net>, a
  119. local HOPE (Hackers on Planet Earth) chapter and we have 5-6 licensed hams
  120. that are interested in experimenting with APRS gateways and other
  121. avant-guard amateur radio networking practices. I'm hoping to use the /24
  122. public IP allocation to lead workshops and introduce others to concepts of
  123. BGP, IP networking, and amateur radio. I'm also involved with an ongoing
  124. alternative networks conference in NY called Radical Networks
  125. <https://radicalnetworks.org/>. The conference is dedicated to sharing
  126. alternative computer networking ideas with artists, activists, and
  127. programmers. I've lead several workshops there, and I am interested in
  128. leading another about creating DIY solar powered servers that are made
  129. available on the public network, perhaps using LoRa. I've also been
  130. developing my own packet radio protocol called Chattervox
  131. <https://github.com/brannondorsey/chattervox>, and I'd like to make a
  132. Chattervox node publicly available on the net at a 44/8 address. Long story
  133. short, I expect to use my /24 in a number of ways that will likely grow
  134. over time, with the primary goal of education and outreach to the larger
  135. amateur radio and alternative networking communities.
  136.  
  137.  
  138. ----------------------------------------------------------------------------
  139. 16. Anything else we should know?:
  140. ----------------------------------------------------------------------------
  141.  
  142. Having access to a subnet of Public IPv4s has been a dream of mine for
  143. quite some time! One that is seemingly possible only now that I am a ham!
  144. So thank you all for everything you do!
  145.  
  146. One follow up note. I am planning on using Vultr.com <http://Vultr.com> as
  147. my NSP, as they have offered to advertise my IPv4 addresses to their
  148. upstream BGP peers. I believe that their ASN is the one listed above, but
  149. I've reached out to their networking team to confirm. I'll follow up if I
  150. have the wrong ASN.
  151.  
  152.  
  153. ----------------------------------------------------------------------------
  154. 17. Network Service Provider name:
  155. ----------------------------------------------------------------------------
  156.  
  157. Vultr.com
  158.  
  159. http://www.whatmyip.co/view/ip_owners/413031/Vultr_Holdings_LLC.html
  160.  
  161.  
  162. ----------------------------------------------------------------------------
  163. 18. NSP postal address:
  164. ----------------------------------------------------------------------------
  165.  
  166. 14 Cliffwood Ave Suite 300, Metropark South Matawan, NJ 07747
  167.  
  168.  
  169. ----------------------------------------------------------------------------
  170. 19. NSP telephone:
  171. ----------------------------------------------------------------------------
  172.  
  173. Vultr doesn't have a phone number listed, but their parent Choopra company
  174. does: 1-866-224-6672 <https://www.choopa.com/contact/>
  175.  
  176.  
  177. ----------------------------------------------------------------------------
  178. 20. NSP email contact:
  179. ----------------------------------------------------------------------------
  180.  
  181. [email protected]
  182.  
  183.  
  184. ----------------------------------------------------------------------------
  185. 21. NSP ASN:
  186. ----------------------------------------------------------------------------
  187.  
  188. I strongly believe it's AS 20473 Choopa, LLC, but am awaiting confirmation
  189. from Vultr. Does this ASN differ from the ASN that will advertise my
  190. routes, if I am using Vultr as my NSP?
  191.  
  192.  
  193. ----------------------------------------------------------------------------
  194. 22. Will your NSP and/or its upstream providers require
  195. a written, signed-on-letterhead formal LoA? (Note: a
  196. 'Yes' answer may delay your application by several days.)
  197. Y/N?:
  198. ----------------------------------------------------------------------------
  199.  
  200. Yes. I do not believe upstreams need to be included in the LoA but I will
  201. follow up if my understanding is incorrect.
  202.  
  203.  
  204. ----------------------------------------------------------------------------
  205. NOTE: If it is required for your NSP's upstreams to be included
  206. in the formal LoA, please repeat list items 17 thru 21 above
  207. for each that should be so included.
  208. ----------------------------------------------------------------------------
Advertisement
Add Comment
Please, Sign In to add comment
Public Pastes
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!