W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2013

Re: Proxy User Stories

From: Amos Jeffries <squid3@treenet.co.nz>
Date: Mon, 09 Dec 2013 22:18:46 +1300
Message-ID: <52A58AF6.4070103@treenet.co.nz>
To: ietf-http-wg@w3.org
LadleNet

LadleNet is a DIY project started by some engineering students which has
grown to span a large metropolitan area. True to its DIY roots the
network is still comprised of a large ad-hoc collection of commercial
devices mixed with home made networking kit or all kinds. Connectivity
within the network is primarily wireless or wired but also includes
other experimental Thing-Thing connectivity relay points added randomly
by users. Underlying link protocols vary widely but are mapped to either
TCP or UDP packets my model software depending on the bandwidth reliability.

HTTP traffic over this unruly collection is governed by a combined
captive-portal and explicit proxy system CookieJar. It is multi-homed in
the truest sense of the word with each users ISP connection providing a
portal to the rest of the Internet with varying amount of available
bandwidth and speed. A custom Ant routing algorithm uses these metrics
along with blacklist rules and PAYG credits exchanged with all
neighbourhood nodes for generating route rules.

Each local household uses explicit proxy configuration on their
end-devices to connect to their node, and other nodes use ad-hoc
discovery via the Ant protocol to connect as well. For security messages
classified as private travelling over LadleNet are always encrypted
individually. But sufficient information to identify final routing
destination and categorize the traffic is always left exposed publicly.
Other messages are always unencrypted. Nodes include AV scanner and
policing software checking classifications randomly.

Amos
Received on Monday, 9 December 2013 09:19:17 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:11:20 UTC