agree...of course...
just we need to start adding
security +cost+ considerations...
to drafts
> On Tue, Jul 3, 2018 at 8:19 AM, Jon Crowcroft
> wrote:
> > beware of sidechannel attacks - eg. a sequence of efficient routes can
> > determine a sequence of locations just from latency/rtt estimation
On Tue, Jul 3, 2018 at 8:19 AM, Jon Crowcroft
wrote:
> beware of sidechannel attacks - eg. a sequence of efficient routes can
> determine a sequence of locations just from latency/rtt estimation
> (observe outbound data and likely return path ack packets) - you want
> privacy, you're gonna pay
>
beware of sidechannel attacks - eg. a sequence of efficient routes can
determine a sequence of locations just from latency/rtt estimation
(observe outbound data and likely return path ack packets) - you want
privacy, you're gonna pay
On Tue, Jul 3, 2018 at 5:14 PM, Tom Herbert wrote:
> On Mon,
On Mon, Jul 2, 2018 at 10:01 PM, Jon Crowcroft
wrote:
> what we need is compact onion routing - maybe we could call it garlic routing.
>
> in all seriousness, if people are worried about privacy with regards
> network operators, or state actors co-ercing network operators, at
> this level, that
what we need is compact onion routing - maybe we could call it garlic routing.
in all seriousness, if people are worried about privacy with regards
network operators, or state actors co-ercing network operators, at
this level, that is what you want. otherwise forget about efficient
mobile routing