5 Jun
2012
5 Jun
'12
4:24 p.m.
I think there is a separation of concerns here.
On the one hand, I think people want to eliminate the bottle-neck/single
point of failure that a single net 44.x.x.x routing point provides (UCSD).
This is where the discussion of delegation with or without a ASN is
rooted. Can all of 44.x.x.x be multi-homed using multiple ASNs (owned by
the providers) or do we need an ASN with multiple homes?
On the other hand, the "last mile" of net 44 might be a variety of
transports including everything from 1200-baud AX.25 transports to
multi-megabyte HSMM LANs. Since this is Amateur Radio, often these last
mile points of presence might include tunneling to upstream routers through
"consumer" Internet connections. For example, I have 25/25MB fiber to the
house ISP service, but would likely be unable to get a BGP agreement from
my ISP, though I already tunnel a Class-C network from a data center whose
ASN is associated with my network. This is the more likely scenario for
LANs whether wired or over RF. Also the network deployment may be
temporary and ad-hoc, for example, an emergency response team might create
a temporary LAN at a refugee camp and use RF to get back to the rest of
Net-44, having a pre-provisioned tunnel that a router could open would
facilitate connectivity. At Hamvention® and SEAPAC the last couple of
weeks, I brought a /27 subnet (off my Class-C) to the NW Digital Radio
booth through a L2TP tunnel, one weekend in Dayton, OH and one weekend in
Seaside, OR (over 2000 miles distance) -- before, between, and after that
same router was at my house in Edmonds, WA providing connectivity to a
D-STAR gateway and other services. In each location the tunnel uses a
dynamically allocated IP address for the remote to a static address at a
data center for transport.
Also, a LAN manager may want to restrict routing by a firewall, allow
outbound connections to the Internet, while restricting inbound connections
to certain ports where the source address is in 44.x.x.x -- to limit
traffic on RF for bandwidth management or content concerns.
So let's keep the two concepts in mind. Major routing infrastructure
(strategic) vs last mile (tactical). One size does not fit all.
------------------------------
John D. Hays
K7VE
PO Box 1223, Edmonds, WA 98020-1223
<http://k7ve.org/blog> <http://twitter.com/#!/john_hays>
<http://www.facebook.com/john.d.hays>
On Tue, Jun 5, 2012 at 1:44 PM, Bjorn Pehrson <bpehrson(a)kth.se> wrote:
(Please trim inclusions from previous messages)
______________________________**_________________
It seems as if I misinterpreted your earlier message summarizing the
offline discussions Brian.
Splitting up the address space by delegations of smaller chunks to
commercial service providers with different AS-numbers and policies will
lead to a historical mistake. Is that what you propose in your latest
message ? or am I missing something now?
The way to create the trust and support for a radio amateur policy is to
keep it together by keeping the delegations inside the community under an
amprnet as-number facilitating multi-homing without tunnels connecting
the delegations to the outside world anywhere via peering and transit
agreements and keeping the challenge of internal connectivity between
delegations as the driver of innovation that will take radio amateurism to
the next level.
Managing interdomain peering and transit via bgp, announcing delegated
pieces of the 44/8 via different border routers is not difficult and can be
done with low cost solutions and open source routing software, much cheaper
than most rigs.
In what way will the ham community benefit from splitting up the resource?
In no way that I can see, but there is a lot to loose.
Bjorn