Re: [44net] My view to 44net's future

Yes. But... I think the question is what's the purpose of providing the addressing comes into play. ISPs are not always offering unfiltered inbound connections. Even though I had a public IPv4 address, I spent 11 years behind a connection that permitted few inbound ports because they wanted to drive people to their "business" plans which where irrationally expensive. IPv6 doesn't change that business driver. The other issue with IPv6 is portability. I don't know what your experiences are like, but it's only been within the last year that my current ISP's IPv6 PD /56 to me has been anything approaching stable. Constantly renumbering is a complete pain. Dynamic DNS helps for name-based services but not for things like routing, firewalls, etc. I gave up on trying to use my client PD for anything service-related years ago and pipe everything through he.net. I suppose he.net is a solution to the problem currently, but I am not sure if he.net will provider TunnelBroker forever. Most of them have closed down at this point. I'm all for a coalition-of-the-willing approach as others have suggested. I just think offering dual-stack would be helpful, at least in cases were numbering predictability and stability are important. The other question of not having a centralized service brings up is how to protect the network operators. Permitting ad hoc traffic through your network and bring operational and legal risk. Having a central, official organization to at least sit atop that issue would be helpful. I already offer services to other hams and groups, but only people I directly know or friend-of-a-friend arrangements - specifically because of liability and supportability concerns. Just my $0.02. Jason