Re: [44net] 44net is not just for tunneling

As has been discussed at length on this mailing list, there are things that have to be done before we can start delegating subnets. What is going on is that we (our nonprofit) is attempting to get organized. That means getting the legal documents handled, setting up an advisory committee, work out an agreement with ARIN regarding our delegation policies, writing an acceptable use policy and subnet delegation contract, establishing procedures to evaluate delegation requests, and figure out some way to fund all of this. To get an ASN we will need to negotiate with ARIN regarding their standard AS contract; it appears to require those applying for an ASN to relinquish a significant amount of autonomy, an amount that I believe is incompatable with the way we wish to continue to operate network 44.

Note also that an ASN costs $500 plus an annual maintenance fee. The nonprofit is already about $1k in the hole, financed entirely by me. We have no source of funds; everything is being done by volunteers including a significant amount of pro-bono work by a networking-policy-savvy attorney who has kindly volunteered her time even though she is not a ham radio licensee (yet).

We need to set up an rwhois server to advise of the delegations. This is an ARIN requirement and good network citizenship. It should be integrated with the web system.

So we've not been idle; things are slowly moving forward. We *will* be delegating subnets when the necessaries are in place. Sorry it's taking so long. Anyone want to help? - Brian PS: perhaps I misunderstand Internet peering, but I don't see any need to get an ASN before delegating subnets. It might be convenient but I don't think it's a prerequisite. Perhaps someone knowledgeable could comment on this.