Re: [v6ops] RFC7084 - absence of req of prefix presence in PIO on LAN?

Alexandre Petrescu <alexandre.petrescu@gmail.com> Fri, 15 November 2019 09:57 UTC

Return-Path: <alexandre.petrescu@gmail.com>
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 DFAEF1201CE for <v6ops@ietfa.amsl.com>; Fri, 15 Nov 2019 01:57:46 -0800 (PST)
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 BUih1bVucB3t for <v6ops@ietfa.amsl.com>; Fri, 15 Nov 2019 01:57:44 -0800 (PST)
Received: from oxalide-smtp-out.extra.cea.fr (oxalide-smtp-out.extra.cea.fr [132.168.224.13]) (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 92079120143 for <v6ops@ietf.org>; Fri, 15 Nov 2019 01:57:44 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id xAF9vfIe027181; Fri, 15 Nov 2019 10:57:41 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 82FC4206714; Fri, 15 Nov 2019 10:57:41 +0100 (CET)
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 730FE202770; Fri, 15 Nov 2019 10:57:41 +0100 (CET)
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 xAF9vfGl019966; Fri, 15 Nov 2019 10:57:41 +0100
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: Timothy Winters <twinters@iol.unh.edu>, "v6ops@ietf.org" <v6ops@ietf.org>
References: <c4791cdd-6021-de83-6863-4d77ef1d1694@gmail.com> <CAOSSMjWu7C9jmG+8Yg7V++3GWzG+BSzFu0o0nHHYJY60P2T2oA@mail.gmail.com> <835b8b49-b00a-6fe3-1f47-7db7d5a76b92@gmail.com> <3e0779de-b740-a9e6-02ce-e18d43795f5c@gmail.com> <4568b864-ceff-f2d5-6941-638dd9d10027@gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <b2ab3879-d7ca-4f8d-9e98-688c86b82bf3@gmail.com>
Date: Fri, 15 Nov 2019 10:57:41 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.2.2
MIME-Version: 1.0
In-Reply-To: <4568b864-ceff-f2d5-6941-638dd9d10027@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/v6ops/NV43W0tZ6_mxzQaxG1ecsf9CiHA>
Subject: Re: [v6ops] RFC7084 - absence of req of prefix presence in PIO on LAN?
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 15 Nov 2019 09:57:47 -0000


Le 14/11/2019 à 19:16, Brian E Carpenter a écrit :
> On 15-Nov-19 01:49, Alexandre Petrescu wrote:
> ...
>> I think RFC8028 sounds in context: "First-Hop Router Selection in a
>> Multi-Prefix Network".
>>
>> However, I am not sure where RFC8028 would apply: is it between the CE
>> Router and the two ISPs?  Or is it between in-house Host and the single
>> CE Router?
> 
> It is only useful in the case of *more than one* CE Router. As far as
> I know, that is not illegal.

I think too that a design of the home network should allow for more than 
one CE Router.  Some home networks do that.  For that it makes sense to 
require the use of RFC8028.

However, I am not sure how to express the need of RIO.

There might be no need of the use of RIO if there is only one CE Router, 
because that is the default router for Hosts in home.  As such, it is 
strange that RFC7084 requires RIO without telling why.

If there are two CE Routers, I am not sure how to fit the use of RIO.

If RIO _is_ used in the context of two CE Routers, then there are 
certainly some requirements on how to use them, in combination with the 
default router capability, and with a requirement to avoid large loops 
cross-ISPs.

There might be a case where only one of the CE Router is the default 
router for Hosts at home, and thus it must not use RIO.  The other CE 
Router must use RIO but must not advertise itself as a default router.

There might be a case where both CE Routers are default routers for 
Hosts at home, but each advertises in PIO a distinct prefix.  In that 
case, there is no need of RIO at all.

Then, there might be cases where there are 3 CE Routers, or more.  That 
would need to be described as well.

Alex