Hello,
I'd like to join the board of ARDC. Having studied the situation a bit, it looks to me like ARDC is in a bad situation right now. Should Brian get hit by a bus, the corporation will no longer have any directors or officers. Its assets would then be disseminated by a court during the dismantling of the corporation. This means the address space would be given away to whoever the court decides, which could include ARIN for re-purposing as commercial space.
I'm not 100% on this, since there is scant documentation on the heritage of 44/8 and its present legal ownership status. I believe it's "legacy space", but ARIN doesn't seem to agree: the netblock suffix does not end with -Z. As "legacy space" there should be some chain of ownership documented somewhere, and I'm just not finding it.
Having read the bylaws, I also haven't managed to find how I might go about becoming elected. The processes for replacement and removal of directors are defined (majority vote of board members), but I don't see how elections to vacant positions are supposed to take place. I'd also like to say that a board electing itself is not the best model of governance for a non-profit corporation. Non-profits are supposed to serve some need: in this case the needs of amateurs who wish to make use of 44/8 space. I'd like to see a governance model where the users elect the directors who best represent their needs. This is one crucial governance change that I think absolutely needs to happen.
Aside from governance, there are several technical issues that I'd like to see brought up to speed with modern standards, and published as part of official interface specifications for AMPRnet. I don't want to get too detailed in this email, but a top-level list of technical things I'd push for as director includes:
1) Support for BGP 2) Support for IPsec(AH) 3) Support for anycasting 4) An improved gateway registration process with IP ownership verification 5) Support for DNS delegation 6) Support for DNSSEC signing 7) Deployment of multiple regional Internet gateways to remove the UCSD single point of failure 8) Adoption of the Extensible Provisioning Protocol 9) Publication of official multi-platform software which simplifies the AMPRnet user experience
I've experienced opposition on implementing points 3 and 5 so far, and I'm reluctant to attempt any more of these agenda items without some changes to how the organization makes decisions. There are no technical blockers here, as all of these technologies I mentioned are widely used on the Internet today. However, it's nearly impossible to achieve technical leadership when decisions require universal consensus, and/or the decision making process is undefined. AMPR needs more board members who can push such technologies forward, and participate in the official decision making process while relying on their deep technical expertise to ensure their votes are sound.
In terms of my qualifications for board duty, I founded the HamWAN organization in Washington which has deployed a regional microwave network, uses AMPRnet IP space, and has based its standard designs on the latest & greatest hardware and software has to offer. Professionally, I'd been running Internet services since 1996. Presently I work on routing for a major cloud provider. I'd like to bring the same kind of innovation to AMPRnet as I did with HamWAN. On the governance standpoint, I drafted the HamWAN bylaws in very intentional ways. Ways that empower the volunteers who are doing the active work that contributes to progress. Governance overhead is minimal so everyone can just mostly focus on the problems at hand.
So, what are the next steps here?
--Bart
All,
Bart has provided good leadership for the amateur data community here in "Pugetopolis."
All amateurs would be well served by placing Bart on the ARDC board. We should do this as soon as possible.
73 from Dan at K7MM
________________________________ From: Bart Kus me@bartk.us To: AMPRNet working group 44net@hamradio.ucsd.edu Sent: Wednesday, April 16, 2014 4:22 PM Subject: [44net] Running for ARDC director position
(Please trim inclusions from previous messages) _______________________________________________ Hello,
I'd like to join the board of ARDC. Having studied the situation a bit, it looks to me like ARDC is in a bad situation right now. Should Brian get hit by a bus, the corporation will no longer have any directors or officers. Its assets would then be disseminated by a court during the dismantling of the corporation. This means the address space would be given away to whoever the court decides, which could include ARIN for re-purposing as commercial space.
I'm not 100% on this, since there is scant documentation on the heritage of 44/8 and its present legal ownership status. I believe it's "legacy space", but ARIN doesn't seem to agree: the netblock suffix does not end with -Z. As "legacy space" there should be some chain of ownership documented somewhere, and I'm just not finding it.
Having read the bylaws, I also haven't managed to find how I might go about becoming elected. The processes for replacement and removal of directors are defined (majority vote of board members), but I don't see how elections to vacant positions are supposed to take place. I'd also like to say that a board electing itself is not the best model of governance for a non-profit corporation. Non-profits are supposed to serve some need: in this case the needs of amateurs who wish to make use of 44/8 space. I'd like to see a governance model where the users elect the directors who best represent their needs. This is one crucial governance change that I think absolutely needs to happen.
Aside from governance, there are several technical issues that I'd like to see brought up to speed with modern standards, and published as part of official interface specifications for AMPRnet. I don't want to get too detailed in this email, but a top-level list of technical things I'd push for as director includes:
1) Support for BGP 2) Support for IPsec(AH) 3) Support for anycasting 4) An improved gateway registration process with IP ownership verification 5) Support for DNS delegation 6) Support for DNSSEC signing 7) Deployment of multiple regional Internet gateways to remove the UCSD single point of failure 8) Adoption of the Extensible Provisioning Protocol 9) Publication of official multi-platform software which simplifies the AMPRnet user experience
I've experienced opposition on implementing points 3 and 5 so far, and I'm reluctant to attempt any more of these agenda items without some changes to how the organization makes decisions. There are no technical blockers here, as all of these technologies I mentioned are widely used on the Internet today. However, it's nearly impossible to achieve technical leadership when decisions require universal consensus, and/or the decision making process is undefined. AMPR needs more board members who can push such technologies forward, and participate in the official decision making process while relying on their deep technical expertise to ensure their votes are sound.
In terms of my qualifications for board duty, I founded the HamWAN organization in Washington which has deployed a regional microwave network, uses AMPRnet IP space, and has based its standard designs on the latest & greatest hardware and software has to offer. Professionally, I'd been running Internet services since 1996. Presently I work on routing for a major cloud provider. I'd like to bring the same kind of innovation to AMPRnet as I did with HamWAN. On the governance standpoint, I drafted the HamWAN bylaws in very intentional ways. Ways that empower the volunteers who are doing the active work that contributes to progress. Governance overhead is minimal so everyone can just mostly focus on the problems at hand.
So, what are the next steps here?
--Bart
_________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
Bart also has my support, working closely with him on actual doing real work directly related to HAM Radio use of 44 space, watching him give countless talks to groups of people with amazing detail, network design work, implementing current best practices related to routing and IP network/server technology, device testing in his RF Lab and genuinely interested to trying to make the HAM space a better place.
I agree with Dan on this too "All amateurs would be well served by placing Bart on the ARDC board. We should do this as soon as possible."
Tim Osburn www.osburn.com 206.812.6214 W7RSZ
On Wed, 16 Apr 2014, Bart Kus wrote:
Date: Wed, 16 Apr 2014 16:22:12 -0700 From: Bart Kus me@bartk.us Reply-To: AMPRNet working group 44net@hamradio.ucsd.edu To: AMPRNet working group 44net@hamradio.ucsd.edu Subject: [44net] Running for ARDC director position
Hello,
I'd like to join the board of ARDC.
...(cut)...
On Wed, Apr 16, 2014 at 4:22 PM, Bart Kus me@bartk.us wrote:
I'm not 100% on this, since there is scant documentation on the heritage of 44/8 and its present legal ownership status. I believe it's "legacy space", but ARIN doesn't seem to agree: the netblock suffix does not end with -Z. As "legacy space" there should be some chain of ownership documented somewhere, and I'm just not finding it.
44/8 is considered legacy space as it's inception was prior to 1997. ARIN chooses not to serve us as Brian has chosen not to agree nor disagree with the Legacy services agreement as to do so would incur costs.
https://www.arin.net/resources/legacy/
Personally, I believe this is a wise decision as it would introduce costs and rules that would ultimately destroy the network. (See above link)
As for a chain of ownership, all you need to do is look toward 'whois' for the netblock. Wikipedia has a nice article about the history of ampr.organd 44/8.
...
As for voting members, running for office, etc.... I don't believe 44net is incorporated or a non-profit. I don't believe there is a board of directors nor shareholders. Thus, I think it's a little premature to call for candidacy until there is a board to campaign for a seat upon. I don't recall reading any bylaws either. If there was, there would be legal requirements under incorporation as well as IRS filings which I don't believe exist.
44/8 is a special case. In many aspects, it's a miniature IANA in that the entire netblock covers the entire globe and not any particular country. Personally, I feel that to keep it fair, one or two representatives should represent the regions they are part of... one from north america, one from south america, europe, australia, asia, africa, etc... From there, the foundations can be written and developed.
Last thing that we want is a IFNA like scenario (for those old enough to remember).
https://www.youtube.com/watch?v=_Cm6EFYktRQ - BBS Documentary Video on Fidonet (the history and story of with the original players - of which I'm seeing many parallels happening here.. history repeating?)
Personally, I believe this is a wise decision as it would introduce costs and rules that would ultimately destroy the network. (See above link)
What rules would destroy the network? I'm very curious as to more details about those lines.
If the fees could be waved in their entirety, would you be open to the signing of an RSA?
...
As for voting members, running for office, etc.... I don't believe 44net is incorporated or a non-profit. I don't believe there is a board of directors nor shareholders. Thus, I think it's a little premature to call for candidacy until there is a board to campaign for a seat upon. I don't recall reading any bylaws either. If there was, there would be legal requirements under incorporation as well as IRS filings which I don't believe exist.
The IP space is owned by
Amateur Radio Digital Communications
per the whois.
ARIN requires a legal entity to exist in order to receive the IP space.
44/8 is a special case. In many aspects, it's a miniature IANA in that the entire netblock covers the entire globe and not any particular country.
Lots of folks have /8 that covers the globe. Most of the large carriers for example. Please don't compare yourself to IANA. :)
On Fri, 18 Apr 2014, charles@thefnf.org wrote:
The IP space is owned by
Amateur Radio Digital Communications
per the whois.
ARIN requires a legal entity to exist in order to receive the IP space.
Just a reminder to everyone - 44/8 was NOT received from ARIN. It is a legacy address block.
Antonio Querubin e-mail: tony@lavanauts.org xmpp: antonioquerubin@gmail.com
Yes. I realize that. Its an interesting position to be in for sure.
However its also about to become largely irrelevant. Ipv6 is seeing rapid uptake , so a /8 of v4 space while currently high in value will soon become worth about as much as 56k modems at the thrift shop.
I'll need to research some things around this and see what the exact state of the legacy space is. I believe some legal developments have taken place recently in this area.
Also doesn't IANA have some say as well? Not so sure that the address apace is as untouchable as folks seem to think it is. Signing an RSA might actually be better rather than worse. I'll reach out to John and my attorney on this matter, I'm curious what they'll have to say.
On April 18, 2014 2:21:12 PM CDT, Antonio Querubin tony@lavanauts.org wrote:
(Please trim inclusions from previous messages) _______________________________________________ On Fri, 18 Apr 2014, charles@thefnf.org wrote:
The IP space is owned by
Amateur Radio Digital Communications
per the whois.
ARIN requires a legal entity to exist in order to receive the IP
space.
Just a reminder to everyone - 44/8 was NOT received from ARIN. It is a legacy address block.
Antonio Querubin e-mail: tony@lavanauts.org xmpp: antonioquerubin@gmail.com _________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
!DSPAM:53517b4995418337228130!
On Fri, 18 Apr 2014, Charles N Wyble wrote:
Yes. I realize that. Its an interesting position to be in for sure.
However its also about to become largely irrelevant. Ipv6 is seeing rapid uptake , so a /8 of v4 space while currently high in value will soon become worth about as much as 56k modems at the thrift shop.
I concur. This argument over legacy IPv4 space does not become us. At the end of the day, we should be connecting amateur radio networks regardless of whether they're on IPv4 or IPv6 space, and right now this fight over net-44 governance seems to be consuming quite a bit of time and energy among some very passionate folks on various sides of a multi-boundary conflict. Seriously folks - can we tone down the rhetoric just a bit?
Even with the diverse nature of our craft and hobby, the wide expanse of IPv6 provides ample room to experiment and build networks however you want. We should not be spinning over how to share 24 bits of an IPv4 prefix.
I'll need to research some things around this and see what the exact state of the legacy space is. I believe some legal developments have taken place recently in this area.
Also doesn't IANA have some say as well? Not so sure that the address apace is as untouchable as folks seem to think it is. Signing an RSA might actually be better rather than worse. I'll reach out to John and my attorney on this matter, I'm curious what they'll have to say.
The legal status of legacy space has been discussed at length on NANOG and ARIN mailing lists multiple times - it isn't just about net-44. You may want to start there. But as someone has already alluded - beware digging too deep. Personally I don't think it's worth getting into because as you've said - it will become irrelevant. The challenge for us is how to remain relevant.
Antonio Querubin e-mail: tony@lavanauts.org xmpp: antonioquerubin@gmail.com
Alright. Finally got to this thread, and to this message which is the beginning of it.
Bart,
Let me start off by saying, that I'm new to both 44net and HamWAN. I'm also young (30 yo). So take those points for what they are worth.
Now I'm going to unload with both barrels on you. Everyone else has been far too polite. Yes I'm new to these forums, however they represent things that are of vital importance to me, and align with the goals/objectives/spirit of the non profit I co founded and have poured thousands of hours/dollars into.
This message is in very poor taste. You come across as a complete jerk. One doesn't just walk into a volunteer organization and demand to be on the board. Especially not with the tone you used.
On 2014-04-16 18:22, Bart Kus wrote:
(Please trim inclusions from previous messages) _______________________________________________ Hello,
I'd like to join the board of ARDC. Having studied the situation a bit, it looks to me like ARDC is in a bad situation right now. Should Brian get hit by a bus, the corporation will no longer have any directors or officers. Its assets would then be disseminated by a court during the dismantling of the corporation. This means the address space would be given away to whoever the court decides, which could include ARIN for re-purposing as commercial space.
You make quite a few assumptions. You come across as an ass. That's what happens when one makes assumptions. Instead of coaching the above as a series of exploratory questions in a respectful manner, you state them as fact then you have one line qualifying the statements as not fact.
I'm not 100% on this, since there is scant documentation on the heritage of 44/8 and its present legal ownership status. I believe it's "legacy space", but ARIN doesn't seem to agree: the netblock suffix does not end with -Z. As "legacy space" there should be some chain of ownership documented somewhere, and I'm just not finding it.
Arin whois shows it as a direct assignment:
http://whois.arin.net/rest/net/NET-44-0-0-0-1/pft
Let's look at some other space shall we:
http://whois.arin.net/rest/net/NET-16-0-0-0-1/pft
Exactly the same.
I won't go into the legacy space details. That's been discussed to death on NANOG etc. I'll reply to some of those messages after this.
Having read the bylaws, I also haven't managed to find how I might go about becoming elected. The processes for replacement and removal of directors are defined (majority vote of board members), but I don't see how elections to vacant positions are supposed to take place. I'd also like to say that a board electing itself is not the best model of governance for a non-profit corporation. Non-profits are supposed to serve some need: in this case the needs of amateurs who wish to make use of 44/8 space. I'd like to see a governance model where the users elect the directors who best represent their needs. This is one crucial governance change that I think absolutely needs to happen.
Non profit governance is a complex subject. Generally members (due paying, voting rights) do elect the board. However in the beginning of a non profit, no members other than the founders exist. As such, the board self elects. Often for the first couple of terms.
Aside from governance, there are several technical issues that I'd like to see brought up to speed with modern standards, and published as part of official interface specifications for AMPRnet. I don't want to get too detailed in this email, but a top-level list of technical things I'd push for as director includes:
- Support for BGP
- Support for IPsec(AH)
- Support for anycasting
- An improved gateway registration process with IP ownership
verification 5) Support for DNS delegation 6) Support for DNSSEC signing 7) Deployment of multiple regional Internet gateways to remove the UCSD single point of failure 8) Adoption of the Extensible Provisioning Protocol 9) Publication of official multi-platform software which simplifies the AMPRnet user experience
I presume you have working prototypes of all the above? You have a nice powerpoint presentation prepared on why these things are important and how folks can adopt them etc etc? You are proposing a pretty complete product/feature stack here. You also impose quite a bit of requirements. Also you need to flesh those points out a bit. Especially if they are core to your proposal for a leadership position.
I've experienced opposition on implementing points 3 and 5 so far,
That doesn't surprise me. Did you propose them in the same way you are trying to become elected to the board? Not to mention those things are pretty difficult to do correctly.
and
I'm reluctant to attempt any more of these agenda items without some changes to how the organization makes decisions. There are no technical blockers here, as all of these technologies I mentioned are widely used on the Internet today. However, it's nearly impossible to achieve technical leadership when decisions require universal consensus, and/or the decision making process is undefined.
Do they? Why can't you implement these things on HamWAN, document them, make a nice LiveCD with the tech bits and let folks who desire the functionality use it? Or just pay the 2k to ARIN and get your own v6 space and fork amprnet?
AMPR
needs more board members who can push such technologies forward, and participate in the official decision making process while relying on their deep technical expertise to ensure their votes are sound.
I'd propose those people need to be officers. Not board members.
In terms of my qualifications for board duty, I founded the HamWAN organization in Washington which has deployed a regional microwave network, uses AMPRnet IP space, and has based its standard designs on the latest & greatest hardware and software has to offer. Professionally, I'd been running Internet services since 1996. Presently I work on routing for a major cloud provider. I'd like to bring the same kind of innovation to AMPRnet as I did with HamWAN. On the governance standpoint, I drafted the HamWAN bylaws in very intentional ways. Ways that empower the volunteers who are doing the active work that contributes to progress. Governance overhead is minimal so everyone can just mostly focus on the problems at hand.
So, what are the next steps here?
1) Stop being such a jerk. 2) Apply for an officer position. 3) Put together a much more concrete proposal. 4) Have some respect for the community.
--Bart
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
!DSPAM:534f10c8267851092468892!