However, the allocation should always be in the portal and approved by your countries coordinator. Afaik an allocation that is not in the portal is technically not valid.

Hello Quan, I can give you my perspective as an AMPR coordinator on how BGP allocations usually get processed. When I receive a request from a user requesting a BGP prefix, I ask a bunch of questions to ensure the person understands the minimum requirements. My questions include: - Your callsign (is it valid with your government's amateur radio licensing body) - Your current home address (to know if you're in my AMPR coordination territory or not). The use of PO boxes or otherwise greatly complicate this Q&A discussion - I have never requested nor am I aware of Brian Kantor previously requesting copies of a person's photo-id to prove identity. This does NOT mean it's never been requested in the past - Would your use of address space be for primarily Internet-only focus traffic or RF-servicing traffic? - Your intended purpose for the address space (to ensure it meets the guidelines of AMPR's charter) - Your Justification for any requests larger than a /24 as our address space isn't unlimited - Your allocated ARIN ASN number ( associated to your name or to a company you directly control) Once I receive appropriate answers for all of the items above, I would either approve the AMPR subnet in the AMPR Portal or if more Internet-only facing traffic, have the user to close out the current AMPR request and create a new request in the 44.190/16 prefix managed by Jan DG8NGN for an allocation. At that point, Brian Kantor would then review the allocation with all the above Q&A answers. If Brian was satisfied with the details, he would begin the LOA process and ultimately send you an official approval email. At that point, some hosting ISPs would then send Brian Kantor a "consent letter" request that he would need to respond to. This response sometimes would require that it be from the ARDC on ARDC letterhead with Brian's hand signature. With all the paperwork completed, you or your hosting provided would then be able to start announcing your allocated prefix. I know this process can be invasive but you would be surprised how many bogus requests I've received over the years. I have to assume this is because of the scarcity of IPv4 addresses and/or people trying to do bad things over the Internet hoping that AMPR address space would shield them somehow. I would assume that if you followed a similar process for your BGP prefixes and can provide all the previous email exchanges with you, your local AMPR coordinator and Brian Kantor and most importantly his approval email, I would assume that Chris G1FEF would accept all that as a valid allocation. Beyond that, you can consider taking this discussion up with the ARDC board: https://www.ampr.org/about/who-we-are/ -- President/CEO: Phil Karn — KA9Q Treasurer: Bdale Garbee — KB0G John Gilmore — W0GNU K. C. Claffy — KC6KCC Technical Advisory Committee John Hays — K7VE Heikki Hannikainen — OH7LZB Tim Osburn — W7RSZ Tim Pozar — KC6GNJ Hope this helps. --David KI6ZHD Silicon Valley 44.4.x.x/16 AMPR Coordinator On 02/19/2020 09:18 PM, Quan Zhou via 44Net wrote: https://web.archive.org/web/20190731094938/https://www.ampr.org/terms-of-se… _________________________________________ 44Net mailing list 44Net(a)mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net

Hello Quan, I can give you my perspective as an AMPR coordinator on how BGP allocations usually get processed.  When I receive a request from a user requesting a BGP prefix, I ask a bunch of questions to ensure the person understands the minimum requirements.  My questions include:    - Your callsign (is it valid with your government's amateur radio licensing body)    - Your current home address (to know if you're in my AMPR coordination territory or not).  The use of PO boxes or otherwise greatly complicate this Q&A discussion    - I have never requested nor am I aware of Brian Kantor previously requesting copies of a person's photo-id to prove identity.  This does NOT mean it's never been requested in the past    - Would your use of address space be for primarily Internet-only focus traffic or RF-servicing traffic?    - Your intended purpose for the address space (to ensure it meets the guidelines of AMPR's charter)    - Your Justification for any requests larger than a /24 as our address space isn't unlimited    - Your allocated ARIN ASN number ( associated to your name or to a company you directly control) Once I receive appropriate answers for all of the items above, I would either approve the AMPR subnet in the AMPR Portal or if more Internet-only facing traffic, have the user to close out the current AMPR request and create a new request in the 44.190/16 prefix managed by Jan DG8NGN for an allocation.  At that point, Brian Kantor would then review the allocation with all the above Q&A answers.  If Brian was satisfied with the details, he would begin the LOA process and ultimately send you an official approval email. At that point, some hosting ISPs would then send Brian Kantor a "consent letter" request that he would need to respond to.  This response sometimes would require that it be from the ARDC on ARDC letterhead with Brian's hand signature.  With all the paperwork completed, you or your hosting provided would then be able to start announcing your allocated prefix. I know this process can be invasive but you would be surprised how many bogus requests I've received over the years.  I have to assume this is because of the scarcity of IPv4 addresses and/or people trying to do bad things over the Internet hoping that AMPR address space would shield them somehow.  I would assume that if you followed a similar process for your BGP prefixes and can provide all the previous email exchanges with you, your local AMPR coordinator and Brian Kantor and most importantly his approval email, I would assume that Chris G1FEF would accept all that as a valid allocation. Beyond that, you can consider taking this discussion up with the ARDC board:    https://www.ampr.org/about/who-we-are/    --    President/CEO:       Phil Karn — KA9Q    Treasurer:       Bdale Garbee — KB0G       John Gilmore — W0GNU       K. C. Claffy — KC6KCC    Technical Advisory Committee       John Hays — K7VE       Heikki Hannikainen — OH7LZB       Tim Osburn — W7RSZ       Tim Pozar — KC6GNJ Hope this helps. --David KI6ZHD Silicon Valley 44.4.x.x/16 AMPR Coordinator On 02/19/2020 09:18 PM, Quan Zhou via 44Net wrote: _________________________________________ 44Net mailing list 44Net(a)mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net

Is an ARIN ASN number mandatory in such a situation ? If not mandatory, would it be a good practice to have one ? If so, would RIPE deliver ASN numbers to people or companies that do not own any IPv4 range (I am not the owner of my 44 subnet, ARDC just grants me the right to announce it) ?

No. TK1 is not in the ARIN region. ARIN is for networks in North America. In RIPE region you should normally have a RIPE-assigned ASN.

It's not completely clear from your description of your situation. You said that you speak iBGP with a provider. What ASN are you using for this?

What happens when you decide to change providers? How will that transition work? Will you end up announcing your addresses with inconsistent origins? That is to be avoided.

Will you maintain direct (maybe tunneled) peering relationships with other networks in AMPR space?

It's important to think through what you want the routing policy to be for your network, now and in the forseeable future. The point of an ASN is basically to give an identifier to a network with a distinct routing policy.

For RIPE region, you will need to get a member (LIR) to ask for the ASN on your behalf. Only LIRs can get number resources from RIPE. The LIR might be but does not have to be your provider. There is a fee from RIPE, I think it's something like EUR50/year. The LIR may or may not charge a fee on top of this, depending on how friendly they are.

So, here are my questions : Is an ARIN ASN number mandatory in such a situation ? If not mandatory, would it be a good practice to have one ?

If so, would RIPE deliver ASN numbers to people or companies that do not own any IPv4 range (I am not the owner of my 44 subnet, ARDC just grants me the right to announce it) ?

On Feb 21, 2020, at 05:32, Toussaint OTTAVI via 44Net <44net(a)mailman.ampr.org> wrote: Hi all, Le 20/02/2020 à 17:42, David Ranch via 44Net a écrit : This points out something I never really understood well. I don't have any ARIN ASN number, and Brian didn't request for one when he gave me the LOA for my subnet. I'm currently announcing BGP via a Vultr VPS. I don't announce directly via BGP to other BGP peers. My network provider (currently Vultr) does it for me : I have an iBGP session with them, and they announce to the rest of the world. Moreover, I do not use BGP routing in my company, so I don't have any "business" ASN. So, here are my questions : Is an ARIN ASN number mandatory in such a situation ? If not mandatory, would it be a good practice to have one ? If so, would RIPE deliver ASN numbers to people or companies that do not own any IPv4 range (I am not the owner of my 44 subnet, ARDC just grants me the right to announce it) ? Thank you in advance. 73 de TK1BI _________________________________________ 44Net mailing list 44Net(a)mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net

More generally, learning about and experimenting with networking is something that we ought to encouraged. Generally, the spirit of autonomy in Amateur Radio (in the sense of not relying strongly on a single piece of infrastructure belonging to someone else) is well served by operating networks.

That's what I did, because I have no need to peer with anyone.  My provider does all of that.  All I had to do was to get the LOA (then from Brian) to them and possibly their upstream (there wa san extra little step required in the paperwork from memory), and once the paperwork was sorted, everything started working. :)

5. Is Chris Smith, G1FEF capable of handling sensitive personal data? He's handling data as natural person, or an legal entity that ARDC approves?

Sounds like Chris needs some help! By the way, did those guys ever get the DNS RRs straightened out for the 44.224.x.x & 44.225.x.x namespaces? I think not! I thought AMAZON owns those now!!! Oh WAIT, Google's public dns server shows that they do. Hey, I'll volunteer my services to administer the DNS zones if given the tools. Really! I'm retired and bored, so WHY NOT? Here's why I ask about this: ----------- Query from 44.0.0.1 = ; <<>> DiG 9.10.3-P4-Debian <<>> @44.0.0.1 -x 44.225.2.2 ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 23181 ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 3, ADDITIONAL: 1 ;; WARNING: recursion requested but not available ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;2.2.225.44.in-addr.arpa. IN PTR ;; AUTHORITY SECTION: 225.44.in-addr.arpa. 3600 IN NS db0fhn.efi.fh-nuernberg.de. 225.44.in-addr.arpa. 3600 IN NS ns.db0fhn.ampr.org. 225.44.in-addr.arpa. 3600 IN NS db0res.de. ;; Query time: 84 msec ;; SERVER: 44.0.0.1#53(44.0.0.1) ;; WHEN: Sat Feb 22 00:16:44 EST 2020 ;; MSG SIZE rcvd: 166 ----------- Query from 8.8.8.8 $ dig @8.8.8.8 -x 44.225.2.2 ; <<>> DiG 9.10.3-P4-Debian <<>> @8.8.8.8 -x 44.225.2.2 ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 48135 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;2.2.225.44.in-addr.arpa. IN PTR ;; ANSWER SECTION: 2.2.225.44.in-addr.arpa. 299 IN PTR ec2-44-225-2-2.us-west-2.compute.amazonaws.com. ;; Query time: 23 msec ;; SERVER: 8.8.8.8#53(8.8.8.8) ;; WHEN: Sat Feb 22 00:19:55 EST 2020 ;; MSG SIZE rcvd: 112 This has to be fixed ASAP! Chris? Phil? I'll help in any way I can if you need to spread the workload! Thomas / KG5ZI /8 -- DAYTON On Thu, Feb 20, 2020 at 12:20 AM Quan Zhou via 44Net < 44net(a)mailman.ampr.org&gt; wrote: https://web.archive.org/web/20190731094938/https://www.ampr.org/terms-of-se… _________________________________________ 44Net mailing list 44Net(a)mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net