Dear 44Net mailing list members,
Weaving through many of the messages from the past few weeks, I’m aware that folks have some questions around why G1FEF has been organizing BGP requests in 44.31/16. Behind these questions, in some cases, is a sense of uncertainty around whether or not ARDC is going to sell any more address space. Some members of the TAC have requested that I speak to you all about these issues, and to create space where you can ask questions. So here we go
G1FEF has been putting BGP allocations into 44.31/16 for a few reasons:
* Currently there are BGP “holes” randomly scattered throughout our address space. This makes it harder to manage, especially when trying to spot unauthorized announcements, which we get a lot of.
* We inherited the “give a /16 to every region or country” practice from the 1990’s which has resulted in extremely sparse use of the space. We'd be better “netizens” if we used the space more effectively.
* The HAMNET issue (needing a static set of addresses for BGP routing) is also a consideration, as they are the largest consumers of our address space by far.
All told, Chris is doing his best to engage in best practices absent a more robust policy around BGP. Creating that policy is definitely on the list, and ideally fits into a greater vision around next steps for the address space (PoPs? Better organizing assignments for one reason or another? etc.). Data from our recent assessment is helping us to put together that vision. Thank you to all of you who shared your thoughts.
In terms of whether ARDC is planning to sell more addresses: while it may happen at some point in the future, there are no current plans, short or medium term, to do so. The non-inconsequential effort involved in overcoming the tax and operational implications of such a move would only make sense after taking into account the views of the 44Net community on a vision for overall address space usage and associated future plans.
In the meantime, many thanks for your patience amid the uncertainty. Feel free to ask any questions you may have.
Sincerely, Rosy
Hi Rosy and thanks for your detailed email.
As a holder of 44.136.160 (BGP Advertised) it would be great to find out if I have to move to 44.31 and if so when. One of our use cases is part of a very large DMR repeater network. Many changes will require trips to very remote mountain tops to reprogram repeaters. These repeaters are located thousands of KM from each other and as you can understand it's a massive job. Ironically we changed the servers all to the 44 net so we would not have to re-number our addresses going forward which had been a limitation of commercial offerings in the past.
We understand and are grateful that ARDC has given us the space but would be very appreciative if we could have some warning of the changes and some time to cut over (at least 6 months) and if plans were forwarded to stakeholders by an official and unified channel. So far All I know about these changes have been gleamed from different emails in the mailing list that at times im to busy to concentrate on.
Thanks again for the update and I appreciate the opportunity to ask some questions.
Matt
VK2FLY - VKRadNET
Hi Matt,
Thank you for this message and for speaking to the real logistics required in the event of needing an address change. If/when that's the case, we will give as much advance warning as possible, though again, it's not on the table any time soon.
All the best, Rosy
Rosy Schechter - KJ7RYV Executive Director Amateur Radio Digital Communications (ARDC) ampr.org
On 8/2/22 4:13 PM, Matt - VK2FLY via 44net wrote:
Hi Rosy and thanks for your detailed email.
As a holder of 44.136.160 (BGP Advertised) it would be great to find out if I have to move to 44.31 and if so when. One of our use cases is part of a very large DMR repeater network. Many changes will require trips to very remote mountain tops to reprogram repeaters. These repeaters are located thousands of KM from each other and as you can understand it's a massive job. Ironically we changed the servers all to the 44 net so we would not have to re-number our addresses going forward which had been a limitation of commercial offerings in the past.
We understand and are grateful that ARDC has given us the space but would be very appreciative if we could have some warning of the changes and some time to cut over (at least 6 months) and if plans were forwarded to stakeholders by an official and unified channel. So far All I know about these changes have been gleamed from different emails in the mailing list that at times im to busy to concentrate on.
Thanks again for the update and I appreciate the opportunity to ask some questions.
Matt
VK2FLY - VKRadNET
Matt, I have similar transition issues, except that mine are more locally confined, but still involve the reassignment of over 200 IP addresses and liaising with multiple ham network coordinators (D-STAR and IRLP, along with the Echolink relays at a minimum require manual administrator intervention). This is a massive job, and I also turned to 44.x address space to avoid the commercial renumbering merry go round (I had renumbered at least 3 times previously). Also, having access to a /24 instead of a /28 allows me to provide more services to hams.
On 3/8/22 9:13 am, Matt - VK2FLY via 44net wrote:
Hi Rosy and thanks for your detailed email.
As a holder of 44.136.160 (BGP Advertised) it would be great to find out if I have to move to 44.31 and if so when. One of our use cases is part of a very large DMR repeater network. Many changes will require trips to very remote mountain tops to reprogram repeaters. These repeaters are located thousands of KM from each other and as you can understand it's a massive job. Ironically we changed the servers all to the 44 net so we would not have to re-number our addresses going forward which had been a limitation of commercial offerings in the past.
We understand and are grateful that ARDC has given us the space but would be very appreciative if we could have some warning of the changes and some time to cut over (at least 6 months) and if plans were forwarded to stakeholders by an official and unified channel. So far All I know about these changes have been gleamed from different emails in the mailing list that at times im to busy to concentrate on.
Thanks again for the update and I appreciate the opportunity to ask some questions.
Matt
VK2FLY - VKRadNET
On Wed, Aug 03, 2022 at 02:02:15PM +1000, Tony Langdon via 44net wrote:
Matt, I have similar transition issues, except that mine are more locally confined, but still involve the reassignment of over 200 IP addresses and liaising with multiple ham network coordinators (D-STAR and IRLP, along with the Echolink relays at a minimum require manual administrator intervention). This is a massive job, and I also turned to 44.x address space to avoid the commercial renumbering merry go round (I had renumbered at least 3 times previously). Also, having access to a /24 instead of a /28 allows me to provide more services to hams.
My /24 was moved from 44.135.x.x to 44.31.x.x a year or so ago, and I was given an overlap period to gradually make the transition. I'd have rather not had to make the change, but given the temporary overlap, it really wasn't too horrible.
I had the simultaneous issue of needing to change BGP advertisers, but I was able to solve that problem as well, and that's a problem that most people in this situation shouldn't face.
Jim
On 3/8/22 3:08 pm, Jim MacKenzie via 44net wrote:
My /24 was moved from 44.135.x.x to 44.31.x.x a year or so ago, and I was given an overlap period to gradually make the transition. I'd have rather not had to make the change, but given the temporary overlap, it really wasn't too horrible.
Yeah while I'd (obviously!) prefer to not have to change, I would consider a lengthy overlap period an acceptable compromise for me to make the change and notify all the relevant people of that change or their administrative updates. That would make such a change workable.
I had the simultaneous issue of needing to change BGP advertisers, but I was able to solve that problem as well, and that's a problem that most people in this situation shouldn't face.
I should be right there, no plans on changing providers. :)
Hi All,
Just to answer some of the questions and concerns regarding BGP announcements…
New requests for BGP announcements are going into 44.31/16 and yes, this is to replace 44.190/16
If anyone is willing to renumber into this range then that would be great and I am very happy to work with you to provide a new assignment with an overlap of whatever period you feel you need to complete the renumbering process. Please email me direct: chris@ardc.net mailto:chris@ardc.net to discuss.
As the license period for BGP assignments last for 5 years, I am asking folk to renumber when their current licence runs out, but again an overlap period is perfectly ok.
More generally, if you do currently have a BGP assignment, please do check when it was first issued so your licence/LOA can be renewed in good time, I am happy to renew LOA’s anytime in the last 12 months of their active period.
I would also like to remind everyone that you do need to login to the portal on a regular basis in order to keep your assignments. The system currently sends reminder emails out at 6 months, 9 months and 12 months. The wording of these emails get ever increasingly more “urgent”. If you login at least once every 6 months you will never be sent a reminder email.
At 15 months (of no login from you) your account is removed and any resources (address assignments, gateways) are removed. The only exception to this, is if you are a coordinator for a country or regional allocation, in which case your account is still removed, but the allocation is re-assigned to a special admin account that can’t be deleted. i.e. only “User” networks are ever removed.
I have been asked many times why we do this, the answer is that it’s the only way we have of keeping the portal at anything like up to date. The idea was originally Brian Kantor's, prior to the portal he had assignments on his spreadsheet for folks that had gone SK or just lost interest and stopped using the addresses. Unlike a commercial organisation, where if you stop paying for your resources they get taken away, we have no other way of knowing if someone has gone SK or just lost interest and moved on.
73, Chris - G1FEF
On 3/8/22 5:26 pm, Chris Smith via 44net wrote:
Hi All,
Just to answer some of the questions and concerns regarding BGP announcements…
New requests for BGP announcements are going into 44.31/16 and yes, this is to replace 44.190/16
If anyone is willing to renumber into this range then that would be great and I am very happy to work with you to provide a new assignment with an overlap of whatever period you feel you need to complete the renumbering process. Please email me direct: chris@ardc.net mailto:chris@ardc.net to discuss.
Thanks for the info Chris. As my license ends next year, I'll contact you privately to arrange a changeover. Timing looks (mostly) good.
I would also like to remind everyone that you do need to login to the portal on a regular basis in order to keep your assignments. The system currently sends reminder emails out at 6 months, 9 months and 12 months. The wording of these emails get ever increasingly more “urgent”. If you login at least once every 6 months you will never be sent a reminder email.
Yep, the emails have dated back to well before Brian's passing, nothing a quick login and look around can't sort.
I have had mine reissued in the new range. Only pet hate is each time you have to fill out the forms (different order on questions / wording). Should of been a bit more you have a current range, just swap over. Other than that process was easy plus the hand over period is pretty good compared to other industrial standards
73s 2e0emo
On Wed, 3 Aug 2022, 09:08 Tony Langdon via 44net, 44net@mailman.ampr.org wrote:
On 3/8/22 5:26 pm, Chris Smith via 44net wrote:
Hi All,
Just to answer some of the questions and concerns regarding BGP announcements…
New requests for BGP announcements are going into 44.31/16 and yes, this is to replace 44.190/16
If anyone is willing to renumber into this range then that would be great and I am very happy to work with you to provide a new assignment with an overlap of whatever period you feel you need to complete the renumbering process. Please email me direct: chris@ardc.net to discuss.
Thanks for the info Chris. As my license ends next year, I'll contact you privately to arrange a changeover. Timing looks (mostly) good.
I would also like to remind everyone that you do need to login to the portal on a regular basis in order to keep your assignments. The system currently sends reminder emails out at 6 months, 9 months and 12 months. The wording of these emails get ever increasingly more “urgent”. If you login at least once every 6 months you will never be sent a reminder email.
Yep, the emails have dated back to well before Brian's passing, nothing a quick login and look around can't sort.
-- 73 de Tony VK3JED/VK3IRLhttp://vkradio.com
44net mailing list -- 44net@mailman.ampr.org To unsubscribe send an email to 44net-leave@mailman.ampr.org
Chris,
Are you talking about only BGP subnets that where or are in the 44.190/16 space or any BGP announced subnet? As here in Michigan we have about 65 /24’s between our /19, /20, /20 and /24 allocations. We BGP announce and are on the IPIP mesh. Shrinking from the 44.103/16 we are in using 65 /24’s at the moment to another /16 just because we speak BGP doesn’t seem logical. Heck HamWAN is in it’s own /16 and BGP speaking they going to have to re-ip move as well? The time/money spent doing this just because we want make a excel document look better? If there is no need to sell more IP space what more justification is there?
Also what is the current time eta for contact requests/emails? We submitted a contact request via the portal end of June and a direct email to you on July 17th and haven’t heard any responses yet.
Thanks, -- Fredric Moses - W8FSM - WRPA678
Thanks for the detailed info Chris. I will be in contact.
Matt
On 3/8/2022 5:26 pm, Chris Smith via 44net wrote:
Hi All,
Just to answer some of the questions and concerns regarding BGP announcements…
New requests for BGP announcements are going into 44.31/16 and yes, this is to replace 44.190/16
If anyone is willing to renumber into this range then that would be great and I am very happy to work with you to provide a new assignment with an overlap of whatever period you feel you need to complete the renumbering process. Please email me direct: chris@ardc.net to discuss.
As the license period for BGP assignments last for 5 years, I am asking folk to renumber when their current licence runs out, but again an overlap period is perfectly ok.
More generally, if you do currently have a BGP assignment, please do check when it was first issued so your licence/LOA can be renewed in good time, I am happy to renew LOA’s anytime in the last 12 months of their active period.
I would also like to remind everyone that you do need to login to the portal on a regular basis in order to keep your assignments. The system currently sends reminder emails out at 6 months, 9 months and 12 months. The wording of these emails get ever increasingly more “urgent”. If you login at least once every 6 months you will never be sent a reminder email.
At 15 months (of no login from you) your account is removed and any resources (address assignments, gateways) are removed. The only exception to this, is if you are a coordinator for a country or regional allocation, in which case your account is still removed, but the allocation is re-assigned to a special admin account that can’t be deleted. i.e. only “User” networks are ever removed.
I have been asked many times why we do this, the answer is that it’s the only way we have of keeping the portal at anything like up to date. The idea was originally Brian Kantor's, prior to the portal he had assignments on his spreadsheet for folks that had gone SK or just lost interest and stopped using the addresses. Unlike a commercial organisation, where if you stop paying for your resources they get taken away, we have no other way of knowing if someone has gone SK or just lost interest and moved on.
73, Chris - G1FEF
44net mailing list --44net@mailman.ampr.org To unsubscribe send an email to44net-leave@mailman.ampr.org
Hello
-----Message d'origine----- De : Chris Smith via 44net 44net@mailman.ampr.org Envoyé : mercredi 3 août 2022 09:26 À : 44 net 44net@mailman.ampr.org Objet : [44net] Re: answering questions about BGP assignment locations, address space plans
Hi All,
Just to answer some of the questions and concerns regarding BGP announcements…
New requests for BGP announcements are going into 44.31/16 and yes, this is to replace 44.190/16
If anyone is willing to renumber into this range then that would be great and I am very happy to work with you to provide a new assignment with an overlap of whatever period you feel you need to complete the renumbering process. Please email me direct: mailto:chris@ardc.net to discuss.
I'm ok but did you receive my emails? I have no answer.
As the license period for BGP assignments last for 5 years, I am asking folk to renumber when their current licence runs out, but again an overlap period is perfectly ok.
More generally, if you do currently have a BGP assignment, please do check when it was first issued so your licence/LOA can be renewed in good time, I am happy to renew LOA’s anytime in the last 12 months of their active period.
I would also like to remind everyone that you do need to login to the portal on a regular basis in order to keep your assignments. The system currently sends reminder emails out at 6 months, 9 months and 12 months. The wording of these emails get ever increasingly more “urgent”. If you login at least once every 6 months you will never be sent a reminder email.
At 15 months (of no login from you) your account is removed and any resources (address assignments, gateways) are removed. The only exception to this, is if you are a coordinator for a country or regional allocation, in which case your account is still removed, but the allocation is re-assigned to a special admin account that can’t be deleted. i.e. only “User” networks are ever removed.
I have been asked many times why we do this, the answer is that it’s the only way we have of keeping the portal at anything like up to date. The idea was originally Brian Kantor's, prior to the portal he had assignments on his spreadsheet for folks that had gone SK or just lost interest and stopped using the addresses. Unlike a commercial organisation, where if you stop paying for your resources they get taken away, we have no other way of knowing if someone has gone SK or just lost interest and moved on.
73, Chris - G1FEF
Hi,
Le 03/08/2022 à 09:26, Chris Smith via 44net a écrit :
At 15 months (of no login from you) your account is removed and any resources (address assignments, gateways) are removed. The only exception to this, is if you are a coordinator for a country or regional allocation, in which case your account is still removed, but the allocation is re-assigned to a special admin account that can’t be deleted. i.e. only “User” networks are ever removed.
I am was the network administrator for a full région (the island of Corsica). But my allocations were deleted without any re-allocation, and without any previous warning. This is because I was considered as a "single user" and nor as a "region coordinator". This is one of the reasons that made us drop 44net addressing, and revert back to standard public addresses : the need of control and stability.
On the engineering point of view, I see several things that could be improved : - AFAIK the "region coordinator" role does not exist. I checked the "region allocation " checkbox on the portal during creation. But I still was considered as a "single user". That's why a simple mistake shut down a full region ! Maybe,you should create the role of "region coordinator", which may be something between the "country coordinator" and the "user". - A /24 subnet is not given to a single user (or I don't understand anything to the IP distribution policy). A /24 subnet means a network is located behind. Then, a /24 allocation should never be deleted without additional verification, because this may break a lot of things. Instead, it should (as suggested) be put on "parking", and allocated to the upstream coordinator. - My network monitoring and Vultr (my BGP provider) informed me that the BGP announcement has been stopped ! I did not receive any notification from ARDC ! That's a severe drawback ! IMHO, before doing such critical actions, a warning email must be sent 30, 15, 7, 3 and 1 day before !
Moreover, when our 44.190 allocation has been removed by mistake, and despite the fact renumbering to 44.31 was agreed, re-allocation of our 44.190 for a transition period has not been accepted immediately. I had to exchange several (more than 20) private emails with several people.
This dose of instability and uncertainty was the main reason why we decides to drop 44net BGP addressing, and switch to commercial IPs on which we have full control.
Other reasons can be found here : "In terms of whether ARDC is planning to sell more addresses: while it may happen at some point in the future, ../.." "ARDC have no plans to provide an SLA of any kind." "The IP addresses are offered free of charge to individual licensed radio amateurs on a best efforts basis. There is no guarantee that the IPs will remain available, ARDC also reserve the right to withdraw permission to use addresses for any reason."
-- We, sysop and network maintainers, spend a lot of time and money. Data center housings, virtual servers, fiber optics and transit are offered to the HAM community, but they are not free ! And even less when you're living on a remote island ! We can't afford building networks, VPN, POPs an regional-wide coverage, with still having the risk of things being completely taken down for any reason, and without any previous notification !
PS : The advocacy about our particular problem has been closed 2 weeks ago (An arrangement was proposed, but we decided to drop 44net, and switch to commercial IPs). I just hope those comments will help improve the 44Net allocation / withdrawal processes, so that sysops can obtain 44net addresses with sufficient level of stability. I have been an ardent 44net promoter during the last few years. During the next years, I'll remain an active follower...
73 de TK1BI
Hi Rosy,
Thanks for this information. I'm certainly all for managing our address space better. However, history has created a bit of a mess. For example, I have a /24 BGP assignment in the 44.190/16 range, which was setup at the time as a "region free" allocation, intended for Internet facing services (which 44.31/16 seems to fulfill these days - please correct me if I'm wrong).
If there's plans for ADRC to transition all BGP endpoints to 44.31/16, then can we please have input into how that transition would be achieved. For me, I have a massive renumbering job to do if/when that time comes, with several pieces of key amateur infrastructure relying on stable addressing, involving configuration of well over 200 individual IPs (mostly Echolink proxies).. I would certainly need a temporary overlap of ranges to pull this off with minimal downtime.
On 3/8/22 6:15 am, Rosy Schechter - KJ7RYV via 44net wrote:
Dear 44Net mailing list members,
Weaving through many of the messages from the past few weeks, I’m aware that folks have some questions around why G1FEF has been organizing BGP requests in 44.31/16. Behind these questions, in some cases, is a sense of uncertainty around whether or not ARDC is going to sell any more address space. Some members of the TAC have requested that I speak to you all about these issues, and to create space where you can ask questions. So here we go
G1FEF has been putting BGP allocations into 44.31/16 for a few reasons:
- Currently there are BGP “holes” randomly scattered throughout our
address space. This makes it harder to manage, especially when trying to spot unauthorized announcements, which we get a lot of.
- We inherited the “give a /16 to every region or country” practice
from the 1990’s which has resulted in extremely sparse use of the space. We'd be better “netizens” if we used the space more effectively.
- The HAMNET issue (needing a static set of addresses for BGP routing)
is also a consideration, as they are the largest consumers of our address space by far.
All told, Chris is doing his best to engage in best practices absent a more robust policy around BGP. Creating that policy is definitely on the list, and ideally fits into a greater vision around next steps for the address space (PoPs? Better organizing assignments for one reason or another? etc.). Data from our recent assessment is helping us to put together that vision. Thank you to all of you who shared your thoughts.
In terms of whether ARDC is planning to sell more addresses: while it may happen at some point in the future, there are no current plans, short or medium term, to do so. The non-inconsequential effort involved in overcoming the tax and operational implications of such a move would only make sense after taking into account the views of the 44Net community on a vision for overall address space usage and associated future plans.
In the meantime, many thanks for your patience amid the uncertainty. Feel free to ask any questions you may have.
Sincerely, Rosy
Hi Tony,
If there's plans for ADRC to transition all BGP endpoints to 44.31/16, then can we please have input into how that transition would be achieved. For me, I have a massive renumbering job to do if/when that time comes, with several pieces of key amateur infrastructure relying on stable addressing, involving configuration of well over 200 individual IPs (mostly Echolink proxies).. I would certainly need a temporary overlap of ranges to pull this off with minimal downtime.
There's not an official plan, but I do agree with Chris that it's a good idea to transition to 44.31/16. At this time, there's only a request to move into that space, not a mandate of any kind.
With that in mind, and in support of some better management practices, perhaps you can make a plan with Chris to make that transition? I don't see a reason why having an overlap for a period of time would be a problem at all.
Let us know what you think, Rosy
Rosy Schechter - KJ7RYV Executive Director Amateur Radio Digital Communications (ARDC) ampr.org
On 4/8/22 3:48 am, Rosy Schechter - KJ7RYV via 44net wrote:
There's not an official plan, but I do agree with Chris that it's a good idea to transition to 44.31/16. At this time, there's only a request to move into that space, not a mandate of any kind.
With that in mind, and in support of some better management practices, perhaps you can make a plan with Chris to make that transition? I don't see a reason why having an overlap for a period of time would be a problem at all.
I have sent Chris an email with a plan to transition to 44.31/16 space. With an appropriate changeover period, I will be able to do the renumbering.
Thanks Rosy for the posting.
It has been a long time since anyone came foward of the mailing list about what ARDC/AMPR had in plan and what would be the method in futur move about the adresse space.
Yes being a nice netizen a valuable goal, and we now know why Chris had been assigning BGP block in the 44.31/16
I see a nice futur for the group. Can wait to see the complete result of the survey
Pierre VE2PF
________________________________________ De : Rosy Schechter - KJ7RYV via 44net 44net@mailman.ampr.org Envoyé : 2 août 2022 16:15 À : Amprnet 44 Net Objet : [44net] answering questions about BGP assignment locations, address space plans
Dear 44Net mailing list members,
Weaving through many of the messages from the past few weeks, I’m aware that folks have some questions around why G1FEF has been organizing BGP requests in 44.31/16. Behind these questions, in some cases, is a sense of uncertainty around whether or not ARDC is going to sell any more address space. Some members of the TAC have requested that I speak to you all about these issues, and to create space where you can ask questions. So here we go
G1FEF has been putting BGP allocations into 44.31/16 for a few reasons:
* Currently there are BGP “holes” randomly scattered throughout our address space. This makes it harder to manage, especially when trying to spot unauthorized announcements, which we get a lot of.
* We inherited the “give a /16 to every region or country” practice from the 1990’s which has resulted in extremely sparse use of the space. We'd be better “netizens” if we used the space more effectively.
* The HAMNET issue (needing a static set of addresses for BGP routing) is also a consideration, as they are the largest consumers of our address space by far.
All told, Chris is doing his best to engage in best practices absent a more robust policy around BGP. Creating that policy is definitely on the list, and ideally fits into a greater vision around next steps for the address space (PoPs? Better organizing assignments for one reason or another? etc.). Data from our recent assessment is helping us to put together that vision. Thank you to all of you who shared your thoughts.
In terms of whether ARDC is planning to sell more addresses: while it may happen at some point in the future, there are no current plans, short or medium term, to do so. The non-inconsequential effort involved in overcoming the tax and operational implications of such a move would only make sense after taking into account the views of the 44Net community on a vision for overall address space usage and associated future plans.
In the meantime, many thanks for your patience amid the uncertainty. Feel free to ask any questions you may have.
Sincerely, Rosy
-- Rosy Schechter - KJ7RYV Executive Director Amateur Radio Digital Communications (ARDC) ampr.org _______________________________________________ 44net mailing list -- 44net@mailman.ampr.org To unsubscribe send an email to 44net-leave@mailman.ampr.org
And thanks, Pierre, for being one of the people who encouraged me to share this information :)
Rosy
Rosy Schechter - KJ7RYV Executive Director Amateur Radio Digital Communications (ARDC) ampr.org
On 8/3/22 8:36 AM, pete M wrote:
Thanks Rosy for the posting.
It has been a long time since anyone came foward of the mailing list about what ARDC/AMPR had in plan and what would be the method in futur move about the adresse space.
Yes being a nice netizen a valuable goal, and we now know why Chris had been assigning BGP block in the 44.31/16
I see a nice futur for the group. Can wait to see the complete result of the survey
Pierre VE2PF
De : Rosy Schechter - KJ7RYV via 44net 44net@mailman.ampr.org Envoyé : 2 août 2022 16:15 À : Amprnet 44 Net Objet : [44net] answering questions about BGP assignment locations, address space plans
Dear 44Net mailing list members,
Weaving through many of the messages from the past few weeks, I’m aware that folks have some questions around why G1FEF has been organizing BGP requests in 44.31/16. Behind these questions, in some cases, is a sense of uncertainty around whether or not ARDC is going to sell any more address space. Some members of the TAC have requested that I speak to you all about these issues, and to create space where you can ask questions. So here we go
G1FEF has been putting BGP allocations into 44.31/16 for a few reasons:
- Currently there are BGP “holes” randomly scattered throughout our
address space. This makes it harder to manage, especially when trying to spot unauthorized announcements, which we get a lot of.
- We inherited the “give a /16 to every region or country” practice from
the 1990’s which has resulted in extremely sparse use of the space. We'd be better “netizens” if we used the space more effectively.
- The HAMNET issue (needing a static set of addresses for BGP routing)
is also a consideration, as they are the largest consumers of our address space by far.
All told, Chris is doing his best to engage in best practices absent a more robust policy around BGP. Creating that policy is definitely on the list, and ideally fits into a greater vision around next steps for the address space (PoPs? Better organizing assignments for one reason or another? etc.). Data from our recent assessment is helping us to put together that vision. Thank you to all of you who shared your thoughts.
In terms of whether ARDC is planning to sell more addresses: while it may happen at some point in the future, there are no current plans, short or medium term, to do so. The non-inconsequential effort involved in overcoming the tax and operational implications of such a move would only make sense after taking into account the views of the 44Net community on a vision for overall address space usage and associated future plans.
In the meantime, many thanks for your patience amid the uncertainty. Feel free to ask any questions you may have.
Sincerely, Rosy
-- Rosy Schechter - KJ7RYV Executive Director Amateur Radio Digital Communications (ARDC) ampr.org _______________________________________________ 44net mailing list -- 44net@mailman.ampr.org To unsubscribe send an email to 44net-leave@mailman.ampr.org
How about those of us that were recently moved to 44.127 ? We (IRLP) now have hundreds of IPs assigned in that space. It will be very difficult to move folks (again).
— Dave K9DC, K9IP
On Aug 3, 2022, at 13:48, Rosy Schechter - KJ7RYV via 44net 44net@mailman.ampr.org wrote:
And thanks, Pierre, for being one of the people who encouraged me to share this information :)
Rosy
Rosy Schechter - KJ7RYV Executive Director Amateur Radio Digital Communications (ARDC) ampr.org
Oops, just responded to this one-on-one vs. on the wider list.
I'd like to check in with Chris to get his thoughts about this and will report back.
Again, moving is not an imperative, but I'd like to support anything that makes Chris' job managing BGP assignments easier.
Many thanks, Rosy
Rosy Schechter - KJ7RYV Executive Director Amateur Radio Digital Communications (ARDC) ampr.org
On 8/3/22 11:13 AM, Dave Gingrich via 44net wrote:
How about those of us that were recently moved to 44.127 ? We (IRLP) now have hundreds of IPs assigned in that space. It will be very difficult to move folks (again).
— Dave K9DC, K9IP
On Aug 3, 2022, at 13:48, Rosy Schechter - KJ7RYV via 44net 44net@mailman.ampr.org wrote:
And thanks, Pierre, for being one of the people who encouraged me to share this information :)
Rosy
Rosy Schechter - KJ7RYV Executive Director Amateur Radio Digital Communications (ARDC) ampr.org
-
Chris Smith -
Dave Gingrich -
F4HIN -
Fred Moses -
Jim MacKenzie -
Matt - VK2FLY -
Mitchell Southgate -
pete M -
Rosy Schechter - KJ7RYV -
Tony Langdon -
Toussaint OTTAVI