New Policy Brief published on Community Networks and Access to Spectrum
Yesterday we published a new policy brief: Spectrum Approaches for Community Networks
Access to affordable and available spectrum is critical for Community Networks. Policy makers can play a key role in ensuring adequate access to spectrum. The policy brief examines the various ways that Community Networks can gain access to spectrum, including:
- the use of unlicensed spectrum,
- sharing licensed spectrum, and
- innovative licensing.
Network operators also play a key role in helping Community Networks. The policy brief outlines recommendations for operators which include:
- access to backhaul infrastructure at fair rates,
- equipment and training partnerships, and
- the sharing of infrastructure as well as spectrum.
Please read our press release for more information about this new paper. Also visit our World Telecommunications Development Conference (WTDC) 2017 page for more about what our team is doing there in Buenos Aires this week.
The post New Policy Brief published on Community Networks and Access to Spectrum appeared first on Internet Society.

He played a key role in moving HPE into the SDN and NFV space.
Company executives had touted its cloud business as part of its Q2 results.
The data center software also integrates with Kubernetes.
The new book should be out around the 29th of December, give or take a few days. For readers interested in what Ethan and I (and Ryan, and Pete Welcher, and Jordan Martin, and Nick Russo, and… the entire list is in the front matter), the general idea is essentially grounded in RFC1925, rule 11. There is really only a moderately sized set of problems computer system needs to solve in order to carry data from one application to another. For instance, in order to transport data across a network, you need to somehow format the data so everyone can agree on how to write and read it, ensure the data is carried without errors, ensure neither the sender nor the receiver overrun or underrun one another, and find some way to allow multiple applications (hosts, etc.), to talk over the same media. These four problems have somewhat proper names, of course: marshaling, which involves dictionaries and grammars; error control; flow control; and multiplexing. So the first step in understanding network engineering is to figure out what the problems are, and how to break them apart.
The company’s virtualization effort is Project Ocean.