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

Alexandre Petrescu <alexandre.petrescu@gmail.com> Mon, 07 October 2019 09:21 UTC

Return-Path: <alexandre.petrescu@gmail.com>
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 B855612008B for <homenet@ietfa.amsl.com>; Mon, 7 Oct 2019 02:21:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.632
X-Spam-Level:
X-Spam-Status: No, score=-2.632 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665] autolearn=ham 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 ruAxgafwGygY for <homenet@ietfa.amsl.com>; Mon, 7 Oct 2019 02:21:02 -0700 (PDT)
Received: from cirse-smtp-out.extra.cea.fr (cirse-smtp-out.extra.cea.fr [132.167.192.148]) (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 04E1A12006F for <homenet@ietf.org>; Mon, 7 Oct 2019 02:21:01 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x979L0oW013455 for <homenet@ietf.org>; Mon, 7 Oct 2019 11:21:00 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 793C0204D48 for <homenet@ietf.org>; Mon, 7 Oct 2019 11:21:00 +0200 (CEST)
Received: from muguet1-smtp-out.intra.cea.fr (muguet1-smtp-out.intra.cea.fr [132.166.192.12]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 6D5F0204BEC for <homenet@ietf.org>; Mon, 7 Oct 2019 11:21:00 +0200 (CEST)
Received: from [10.8.35.150] (is154594.intra.cea.fr [10.8.35.150]) by muguet1-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id x979L0CM014929 for <homenet@ietf.org>; Mon, 7 Oct 2019 11:21:00 +0200
To: homenet@ietf.org
References: <56255ECF-9002-4440-BA0D-665EFC4BA9C6@fugue.com> <F638F635-9A1C-409E-BDB8-C00DF00A64C8@employees.org> <alpine.DEB.2.20.1910040752050.968@uplift.swm.pp.se> <A52F076F-817D-4807-8CD6-280C2040AEBF@employees.org> <5F0D2E3D-BE20-4421-8A37-E81E6B93B3A5@fugue.com> <E50D25C7-8EF1-4685-9442-021F019F7F62@employees.org> <60B2C15B-E126-4F86-AA9A-9EB9A6C0EB2D@fugue.com> <FBCD2C32-9CBE-4499-A3E9-0FF4991E34DF@employees.org> <A5D12082-3D6A-4540-9AFB-2530D4FA6A32@fugue.com> <CAO42Z2yOdxkfMWJEBWK-J=UWPQ5CyPJ3j0b+HarwXWV4GkK87g@mail.gmail.com> <caa2254d-9800-8315-68c5-ce02e58f5a61@gmail.com> <0A6D0D44-5092-45AE-B5A1-37B9A2F91167@gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <5f7f23b3-7592-87fc-2995-65ef379b1395@gmail.com>
Date: Mon, 7 Oct 2019 11:21:00 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.1.1
MIME-Version: 1.0
In-Reply-To: <0A6D0D44-5092-45AE-B5A1-37B9A2F91167@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/3xFZ0354jDC3ym1jzyTwRz6PtP4>
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: Mon, 07 Oct 2019 09:21:04 -0000

Le 07/10/2019 à 06:05, Gyan Mishra a écrit :
[...]
> For IPv4 in general across the board all broadband routers openWrt or
> otherwise pnp setup have a dhcp wan IP and LAN side is RFC 1918
> 192.xx and nat overload is done from inside to outside.  Pretty basic
> and it works well.
> 
> For IPv6 we have the option of hiding the internal space doing a ULA
> on the lan side but only caveat that would require NAT64 DNS64 as
> well added complexity but that would work.

There are also several deployments in which the solution to connect ULA 
LANs to Internet is NAT66.  They are there, and should not be forgot.

openwrt does too NAT66, I think, with an easy to use GUI.

> The other option is PD on the wan side get a GUA /56 from the SP
> allocated dynamically to the home broadband router and then a /64 is
> doled our to lan interface via PD and all hosts in the home network
> sit on the GUA /64 and get a slaac address.
> 
> The later  I thin is the easiest as no nat requirement.

I think too it is easier.

But what do you mean by 'no nat requirement'?  I have not seen such a 
requirement.

Alex
[...]