[v6ops] Turning on IPv6 Routers

Fred Baker <fredbaker.ietf@gmail.com> Thu, 20 July 2017 14:23 UTC

Return-Path: <fredbaker.ietf@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 895A312704A; Thu, 20 Jul 2017 07:23:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id w09TLvetl_rr; Thu, 20 Jul 2017 07:23:03 -0700 (PDT)
Received: from mail-wr0-x230.google.com (mail-wr0-x230.google.com [IPv6:2a00:1450:400c:c0c::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E3CC6120725; Thu, 20 Jul 2017 07:22:59 -0700 (PDT)
Received: by mail-wr0-x230.google.com with SMTP id y43so71452786wrd.3; Thu, 20 Jul 2017 07:22:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:content-transfer-encoding:mime-version:subject:message-id:date :cc:to; bh=LV3ZPW+3NdG7BQH3LQdUqBdoECgfOPgVcpp5dJ8SglI=; b=E87cmHA5Hyj6t6XJhpM1rEMRgmAMfhpGjDneX6r9u/Plnv/bbmN3dhLLNwV0oWQ3lu 9c6+SieUMSyiuyPSoSPDLRi0hXQ7pPKUVTny2waozM9cn2LMpU5o0Dc3TCGDgvrZwD/T T4AFpvC7j1ZTL49w+ZSyXRJqufQLWVOPcBpItWsDBmCFS3fuFhYmIHac5Fq3z8Wp24AB /2JvvzHqv2/+UBBRtgD8dUGCg+FOgOEMrOY3kjPXN/z3tZtpmomVPnccDN6f55ohViUa DS1MgyArfkszq6rZf/gsMCVB0wN/8GBOiJYRmaLSO5ByYvIHYYZBQ/zbrevsgVxlrqQn ntLA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:message-id:date:cc:to; bh=LV3ZPW+3NdG7BQH3LQdUqBdoECgfOPgVcpp5dJ8SglI=; b=DdKwwIkWNxxE5gTrlsmuu/ynoQHzDZRaKjNZZe+ryWCv+RzhD/LfkE72gR2ZCV/dh9 +HL6+EOBlCURCpdvPvRSTIta11xysO82CiUjqC/MJgzlT2d3Nfa8VBt1bhbFrY/JpP+L yIQNvoi3wxLN/PcxT7A1J+qLB3j01s35OFXB7rRXIlKQlo5gDVOjuumhTdKi/Q9o1rf+ CNcJ+VFI5TPkVNA2v2CYNwCtnl1jCayaFmKtz3RJwaQyJmAWBXQmIjkEAV5RcYgGUnYZ Q9WSI9AAd4gtnBIlWqNqDh7HuDuv4ahvUy/C5OG+DEFb1gik8ltnYczxA9pN5fagjpRw g43g==
X-Gm-Message-State: AIVw113O6EfQqUlLu+YEpOu6UYdT0JNlKWzBBEEaQX1uSdalmHreOB8e jxcyMLt+gJ7RGunKDjI=
X-Received: by with SMTP id y97mr7151884wrb.41.1500560578322; Thu, 20 Jul 2017 07:22:58 -0700 (PDT)
Received: from ?IPv6:2001:67c:1232:144:799c:671e:be9d:c1b3? ([2001:67c:1232:144:799c:671e:be9d:c1b3]) by smtp.gmail.com with ESMTPSA id 9sm2704684wmo.35.2017. (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 20 Jul 2017 07:22:57 -0700 (PDT)
From: Fred Baker <fredbaker.ietf@gmail.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 11.0 \(3439\))
Message-Id: <28757A47-53D8-459E-B76D-D5D5DE3D5897@gmail.com>
Date: Thu, 20 Jul 2017 16:22:56 +0200
Cc: 6man WG <ipv6@ietf.org>, IPv6 Ops WG <v6ops@ietf.org>
To: draft-ietf-6man-rfc6434-bis@ietf.org
X-Mailer: Apple Mail (2.3439)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/irvPMI3tXXFFbK1hQ0M1FzS7g9E>
Subject: [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, 20 Jul 2017 14:23:04 -0000

I write as co-chair of v6ops, under our charter element "comment to other working groups when it seems appropriate". 

One outcome from at least v6ops and I think a couple of other WGs and RGs this week - may I suggest a change to Node Requirements and a corresponding change to the IPv6 Ready Logo?

General Category: "Good grief, it's 2017 for goodness' sake!"

Something that would be helpful in IPv6 deployment would be to turn IPv6 on by default in residential routers. Note that this is not the general case. I can think of routers, whose vendors have C's and J's, and probably H's, in their names, whose default configuration is as an Internet Host. The following would apply to devices that are configured by default as an IP router with routing enabled.

Please add a requirement of the general form:

"If IPv4 router operation is enabled by default, enable IPv6 router operation by default."

Note that this is not as simple as it might sound. There are at least three configurations that must be allowed for upstream: bridging the ISP downstream and CPE downstream LANs, Address allocation via DHCP IA_NA, and address allocation via SLAAC, and on the CPE downstream LAN(s), address allocation via DHCP IA_NA and SLAAC. BBF TR-124 gives a flowchart for this or RFC 7084 defines the algorithms. The implementation is going to have to enable all three, see which works, and act accordingly.

There may also be considerations for PPPOE: if IPv4 is configured for PPPOE, turn it on for IPv6.

Good Grief. This is 2017 for goodness' sake, and there are implementations that turn IPv6 on by default and work. Do it. Just do it.