netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: "Bjørn Mork" <bjorn@mork.no>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
	Tom Herbert <tom@herbertland.com>,
	Sam Patton <sam@enhancedip.org>,
	Linux Kernel Network Developers <netdev@vger.kernel.org>
Subject: Re: ANNOUNCE: Enhanced IP v1.4
Date: Tue, 5 Jun 2018 14:41:28 +0200	[thread overview]
Message-ID: <20180605124128.GA15100@1wt.eu> (raw)
In-Reply-To: <87y3ft9zwg.fsf@miraculix.mork.no>

On Tue, Jun 05, 2018 at 02:33:03PM +0200, Bjørn Mork wrote:
> > I do have IPv6 at home (a /48, waste of addressing space, I'd be fine
> > with less),
> 
> Any reason you would want less?  Any reason the ISP should give you
> less?

What I mean is that *if* the availability of /48 networks was an issue
for some ISPs, I'd be fine with less because I don't plan to deploy 64k
networks at home, though I already have ~9 around the firewall and don't
expect to go much further.

> > Maybe setting up a public list of ISPs where users don't have at least
> > a /60 by default could help, but I suspect that most of them will
> > consider that as long as their competitors are on the list there's no
> > emergency.
> 
> Exactly.  And the number of users using the list as the primary
> parameter for selecting an ISP would be close to 0.  The critical part
> is not the list, but making large enough groups of users consider IPv6
> an important parameter when selecting ISPs.

In fact the IoT trend could play a role here by letting users know that
they can remotely access their fridge and whatever stupid device they've
deployed. But the reality is the opposite : some gateway services are/will
be offered at a paid price to make these devices remotely accessible, and
the claimed security provided by this gateway will be presented as a real
benefit compared to the risks of anyone directly accessing your private
life over IPv6. So I'm not getting much hopes for the future in this area
either.

Willy

      reply	other threads:[~2018-06-05 12:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-02  1:48 ANNOUNCE: Enhanced IP v1.4 Sam Patton
2018-06-02  5:57 ` Willy Tarreau
2018-06-02 16:17   ` Sam Patton
2018-06-02 17:02     ` Willy Tarreau
2018-06-03 20:37     ` Tom Herbert
2018-06-03 22:41       ` Eric Dumazet
2018-06-04  4:34         ` Willy Tarreau
2018-06-04  5:58           ` 答复: " PKU.孙斌
2018-06-04 13:02             ` Eric Dumazet
2018-06-04 14:56               ` Tom Herbert
2018-06-05 12:33           ` Bjørn Mork
2018-06-05 12:41             ` Willy Tarreau [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180605124128.GA15100@1wt.eu \
    --to=w@1wt.eu \
    --cc=bjorn@mork.no \
    --cc=eric.dumazet@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=sam@enhancedip.org \
    --cc=tom@herbertland.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;
as well as URLs for NNTP newsgroup(s).