From: Dave Taht <dave.taht@gmail.com>
To: Richard Brown <richard.e.brown@dartware.com>
Cc: "<cerowrt-devel@lists.bufferbloat.net>"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] CeroWrt port numbering
Date: Fri, 2 Mar 2012 08:51:50 -0800 [thread overview]
Message-ID: <CAA93jw61qd6o_6+s3gV+s75FNWUmhzjWyP+EkkEAQZ6vhscRjg@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw4rZH1GJfTJc8nUqrCBo7XHdUqjtJGb3sz1TSVxHsyEdw@mail.gmail.com>
On Fri, Mar 2, 2012 at 8:26 AM, Dave Taht <dave.taht@gmail.com> wrote:
>>> Privacy advocates are saying that the "easy way" to create a global IPv6 address is bad: it's too easy to plop the MAC address in the lower 64 bits of your address, and then the bad guys can use that as another (really powerful) tracking identifier. This is clearly not a CeroWrt-specific issue, and it's actively in discussion. (See, for example Barrera et al, in the Usenix Vol 36, Number 1, https://www.usenix.org/system/files/login/articles/105438-Barrera.pdf )
>>
>> This debate has been going on for a decade.
>>
>> I would like all those trying to make ipv6 even harder for mere
>> mortals to use to go off and work on ipv7, hip, and the like.
>>
>> DNS naming has been hopelessly screwed up as it is, and while I'm a
>> big privacy advocate, I'd like ip addresses to be mapped to DNS names
>> and I figure that that will bug that crowd, too.
>
> My position on this is considerably more nuanced than I allude to
> above, but I lack the time today to go into it in detail.
>
> briefly.
>
> IPv6's one big advantage is restoring end to end connectivity to the
> internet, this means that ip addresses do 'leak'.
>
> However, compared to all the other information that is tracked
> nowadays leaking that seems rather trivial, and having local
> connectivity that 'just works' would be nice to have compared to what
> we have nowadays. For thought-food, why should making a skype call to
> someone else in your office require a round trip through the internet?
>
> From a privacy standpoint there is the existing difference between the
> 'us' and 'them' views in bind, the plan has been
> to publish local ipv6 addresses in the 'us' view, and optionally in
> the them (public) view.
>
> the mdns whatever.local convention also applies to ipv6, and happens
> to work if you have the privacy extensions enabled on your machine,
> but needs a hook to talk to the local dns server that is standardized
> somehow....
>
> naming, privacy, and ipv6 are ratholes....
>
> gotta go
and btw, I happen to like the idea of hip
http://infrahip.hiit.fi/
and have been meaning to package it up and make it 'just work' for
ages. The former
seems straightforward, the latter....
also of interest are ipv6 nat (patches being floated around now), ccnx
(already packaged),
shim6, lisp, mobile-ipv6, etc.... but ENOTIME on my part.
>>>
>>
>>
>>
>> --
>> Dave Täht
>> SKYPE: davetaht
>> US Tel: 1-239-829-5608
>> http://www.bufferbloat.net
>
>
>
> --
> Dave Täht
> SKYPE: davetaht
> US Tel: 1-239-829-5608
> http://www.bufferbloat.net
--
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://www.bufferbloat.net
prev parent reply other threads:[~2012-03-02 16:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.2.1330632002.8558.cerowrt-devel@lists.bufferbloat.net>
2012-03-02 4:22 ` Richard Brown
2012-03-02 10:50 ` Dave Taht
2012-03-02 15:37 ` Richard Brown
2012-03-02 15:56 ` Dave Taht
2012-03-02 16:26 ` Dave Taht
2012-03-02 16:51 ` Dave Taht [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw61qd6o_6+s3gV+s75FNWUmhzjWyP+EkkEAQZ6vhscRjg@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=richard.e.brown@dartware.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox