Re: [homenet] Support for RFC 7084 on shipping devices...

Mikael Abrahamsson <swmike@swm.pp.se> Fri, 04 October 2019 06:20 UTC

Return-Path: <swmike@swm.pp.se>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E6341200F6; Thu, 3 Oct 2019 23:20:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level:
X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=swm.pp.se
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 8_jEnSDLfRmN; Thu, 3 Oct 2019 23:20:37 -0700 (PDT)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) (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 7C0B41200C1; Thu, 3 Oct 2019 23:20:36 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id D950BB1; Fri, 4 Oct 2019 08:20:32 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1570170032; bh=tpeikhaZ3OEIbfeOSHmiVPYbPDQUJVJk+XbYU2mUX9Q=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=tAuh/Z05wHn16DBspl3JJGuQgVbH0D4Z1m/64WKcdY0D6/7UzI5EBOxKX+/rcNoNd sP8tUZR2f3F2kmydrgiVYYN/IH5gHjaJ1C0QaQSXeBKVT1k0Mr4jpQmh5J7fLSgnIh e1PnUFj7F8oJDE2IKvjj+VI7ZSLNOe+lk26maRoM=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id D7128AF; Fri, 4 Oct 2019 08:20:32 +0200 (CEST)
Date: Fri, 4 Oct 2019 08:20:32 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Ole Troan <otroan@employees.org>
cc: Ted Lemon <mellon@fugue.com>, HOMENET <homenet@ietf.org>, 6MAN <6man@ietf.org>
In-Reply-To: <F638F635-9A1C-409E-BDB8-C00DF00A64C8@employees.org>
Message-ID: <alpine.DEB.2.20.1910040752050.968@uplift.swm.pp.se>
References: <56255ECF-9002-4440-BA0D-665EFC4BA9C6@fugue.com> <F638F635-9A1C-409E-BDB8-C00DF00A64C8@employees.org>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/-Hij_z8N_Gy5wCMwA_GbAd8Jvf8>
Subject: Re: [homenet] Support for RFC 7084 on shipping devices...
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Oct 2019 06:20:40 -0000

On Fri, 4 Oct 2019, Ole Troan wrote:

> Ted,
>
> [top posting]
>
> RFC7084 does not have any support for internal routers.

While this is true, OpenWrt does support DHCPv6-PD within the home, out of 
the box. I also have a report of AVN Fritzbox supporting sub-PD without 
additional configuration.

In all devices I've looked at the WAN is WAN, it comes up with firewalls 
on, requests PD etc, and if it doesn't get it then there is no GUA IPv6 on 
LAN.

In my opinion the work in homenet could be leveraged into an operational 
document where recommendations on what parts of homenet could be easily 
implemented to make it work within a home (without implementing 
everything), thinking primarily of "firewall off" and "service discovery 
proxy on". If no PD was available, turn ethertype 0x86dd bridging on 
between LAN and WAN. I guess we would still need to do NAT44 because 
without HNCP there wouldn't be a route to the IPv4 network on LAN of the 
"sub-router".

It would however mean that a printer on the sub-router LAN could be 
reached over IPv6. In order for this to happen without HNCP then this 
sub-router would need to send RAs on its WAN announcing reachability to 
its LAN IPv6 prefix (either GUA+ULA if PD is available, otherwise just 
ULA). I have never seen RA guard or similar functions in residential 
equipment, so I would expect this to work.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se