13 May
2018
13 May
'18
11:36 a.m.
Hello Marius,
Ok, this is clearer for me with the final piece being that if a HAM
wants to have non-public HAM resources using BGP announced prefixes,
they continue to request a prefix from their local coordinator.
--David
KI6ZHD
On 05/12/2018 11:30 PM, Marius Petrescu wrote:
Actually, if a block has tunnel support (BGP
advertised or not), it
should be requested in the portal, so its setup makes it into the RIP
broadcast data and should NOT be in the 44.190 space.
If it is ONLY BGP advertised and holds relevant public ham resources,
then it should go into that 44.190 block.
On 12.05.2018 20:48, David Ranch wrote:
It seems to me that with the creation of this new 44.190.0.0/16
network, there is now a new workflow. If I'm incorrect, could
someone please set me strait?
- If a new HAM desires to get and advertise an AMPR prefix via BGP
w/o any IPIP encaps support, they should request a 44.190/16 block.
If this is correct, the AMPR portal should be enhanced to send this
request off to whomever is this new 44.190/16 coordinator. Until
this portal changes occur, who should we forward the AMPR allocation
requests to?
- If a new HAM doesn't intend to advertise their block via BGP,
they should request a netblock via the current IP coordinators workflow
--David
KI6ZHD
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net