TCLP 2007-11-18 News (Comment Line 360-252-7284)

This is news cast 121.

In this week’s intro, contemplating the creative challenges presented by working for a small technology company. More so its impacts on personal creativity outside of work.

This week’s security alerts include Red Hat’s new Policy Kit and a back door in a NIST standard for pseudo-random number generation.

In this week’s news, a federal official wants us to re-define privacy though his argument may be a bit more nuanced than that, details of the OLPC mesh network implementation, a cipher challenge commemorating the war time efforts at Bletchley park (already won by a German amateur code breaker), and a blowable interface developed at Georgia Tech, really.

Following up this week, Warner’s chief owns up to some past mistakes and Google getting serious about a solo big in the upcoming spectrum auction.

Download the show directly. Grab the detailed show notes with time offsets and additional links either as PDF or OPML.

Creative Commons License
This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 United States License.

2 Replies to “TCLP 2007-11-18 News (Comment Line 360-252-7284)”

  1. Interesting discussion on mesh networking. While mesh networks may not show up in mainstream networks and applications for a while, there is quite a bit of work being done with them in regards to sensor networks. This may be a way in which mesh networking will slide into more wide spread use. I recently did some graduate work on a sensor network with mesh networking using junction tree protocol to setup and maintain the mesh. This type of use for mesh networks are already being used in areas such as such as monitoring soil moisture levels at wineries and monitoring temperature differences in blood storage facilities. If you are interested, I recommend you look into sensor networks (if you haven’t yet). Very interesting stuff. I’m looking forward to see where this technology will end up in the long run.

  2. Sensor networks, especially those deployed out of doors, would seem to have issues that a mesh would deal with extraordinarily well. I’m thinking sporadic connectivity, specifically, caused by environmental conditions of all kinds.

    Do sensor networks have favorable load characteristics for meshes, too? The one remaining criticism implicit in that OnLAMP piece was the notion that meshes place more load on the network itself, versus loading some specific and centralized resource like servers. Are sensor meshes low enough throughput to avoid any issues with that? I’d have to imagine that would be so, that you’d have very small amounts of data, pretty much constantly, but on a periodic rather than a continuous basis.

    May day job involves automation, more for security than sensing, but we’ve looked into adding sensors onto our products. Think adding flood and fire sensors on top of being able to tell the state of secured doors and control their behaviors.

Leave a Reply

Your email address will not be published. Required fields are marked *