Re: [v6ops] Turning on IPv6 Routers

Lee Howard <lee@asgard.org> Thu, 03 August 2017 12:25 UTC

Return-Path: <lee@asgard.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CFD8131ECE for <v6ops@ietfa.amsl.com>; Thu, 3 Aug 2017 05:25:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e9RI5ut6CvCv for <v6ops@ietfa.amsl.com>; Thu, 3 Aug 2017 05:24:59 -0700 (PDT)
Received: from atl4mhob21.registeredsite.com (atl4mhob21.registeredsite.com [209.17.115.115]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 79729131EB9 for <v6ops@ietf.org>; Thu, 3 Aug 2017 05:24:58 -0700 (PDT)
Received: from mailpod.hostingplatform.com ([10.30.71.204]) by atl4mhob21.registeredsite.com (8.14.4/8.14.4) with ESMTP id v73COtDj001556 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <v6ops@ietf.org>; Thu, 3 Aug 2017 08:24:55 -0400
Received: (qmail 15798 invoked by uid 0); 3 Aug 2017 12:24:55 -0000
X-TCPREMOTEIP: 68.100.68.25
X-Authenticated-UID: lee@asgard.org
Received: from unknown (HELO ?192.168.1.160?) (lee@asgard.org@68.100.68.25) by 0 with ESMTPA; 3 Aug 2017 12:24:55 -0000
User-Agent: Microsoft-MacOutlook/14.7.2.170228
Date: Thu, 03 Aug 2017 08:24:49 -0400
From: Lee Howard <lee@asgard.org>
To: Nick Hilliard <nick@foobar.org>, Fred Baker <fredbaker.ietf@gmail.com>
CC: IPv6 Ops WG <v6ops@ietf.org>, 6man WG <ipv6@ietf.org>, draft-ietf-6man-rfc6434-bis@ietf.org
Message-ID: <D5A88B60.7F356%lee@asgard.org>
Thread-Topic: [v6ops] Turning on IPv6 Routers
References: <28757A47-53D8-459E-B76D-D5D5DE3D5897@gmail.com> <5970CB51.3090806@foobar.org>
In-Reply-To: <5970CB51.3090806@foobar.org>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/pB7LhHQAxllSGm4nbOH2Be_SEhM>
Subject: Re: [v6ops] Turning on IPv6 Routers
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Aug 2017 12:25:01 -0000


On 7/20/17, 5:25 PM, "v6ops on behalf of Nick Hilliard"
<v6ops-bounces@ietf.org on behalf of nick@foobar.org> wrote:

>Fred Baker wrote:
>> "If IPv4 router operation is enabled by default, enable IPv6 router
>> operation by default."
>
>this is undoubtedly well-intentioned, and the idealist bit in me
>sympathises with the principal.  However with my enable hat on, a
>recommendation like this isn't going to fix any problem associated with
>ipv6 adoption.

I completely disagree, but it’s dependent on where the router exists.
For a home gateway router, “IPv6 on by default” would increase the number
of people using IPv6, although I have no way to estimate the impact.

For an enterprise edge router, “IPv6 on by default” might accidentally get
IPv6 deployed. There’s potential risk if “IPv6 firewall on by default”
isn’t also enabled, but this is mentioned in the Security Considerations
section.

In data centers and core networks, there isn’t a strong case either way,
because those configurations should be tightly managed, and accidentally
enabling IPv6 is unlikely to leak anywhere else.

>
>The problems with ipv6 adoption revolve entirely around cost/benefit.

Well, yes, but not always in the way I think you mean it.
Tens of millions of people use IPv6 daily without ever having done a
cost-benefit analysis.

>Pressing problems still include things that should have been resolved
>years ago, e.g. vendors charging extra for ipv6 support (today's
>bugbear: provisioning system vendors, please note that charging extra
>for basic ipv6 functionality is destructive in the long term and
>corrosive for your customer relationships)

Yeah, that’s a bad vendor relationship, and a vendor doing that must be
pretty confident that their customer otherwise loves their product and
isn’t tempted to find an alternative vendor.

>
>As a separate issue, from an operational point of view, implicit
>enabling of functionality in one area when it's explicitly enabled in
>another is something that needs to be handled carefully because
>otherwise you can end up violating the principal of least astonishment.

Anyone astonished by IPv6 working needs to be astonished.

Lee


>
>Nick
>
>_______________________________________________
>v6ops mailing list
>v6ops@ietf.org
>https://www.ietf.org/mailman/listinfo/v6ops
>