Re: [v6ops] Routers are hosts too! (Re: I-D Action: draft-ietf-v6ops-host-addr-availability-04.txt)

Alexandre Petrescu <alexandre.petrescu@gmail.com> Thu, 07 January 2016 13:26 UTC

Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A337F1A899C for <v6ops@ietfa.amsl.com>; Thu, 7 Jan 2016 05:26:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level:
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham
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 e2fmQLQ_x8lD for <v6ops@ietfa.amsl.com>; Thu, 7 Jan 2016 05:26:29 -0800 (PST)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2EB421A8992 for <v6ops@ietf.org>; Thu, 7 Jan 2016 05:26:28 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.15.2/8.15.2/CEAnet-Internet-out-2.4) with ESMTP id u07DQRAC011505; Thu, 7 Jan 2016 14:26:27 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id B049E2037AC; Thu, 7 Jan 2016 14:33:55 +0100 (CET)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 9AE8F2012D0; Thu, 7 Jan 2016 14:33:55 +0100 (CET)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet1.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id u07DQQaX017809; Thu, 7 Jan 2016 14:26:27 +0100
To: Gert Doering <gert@space.net>
References: <CAO42Z2zU12bHqh2DiCeT2MOE6txh1cKbU9DasSjozQ166knVdQ@mail.gmail.com> <568D8B33.1060301@isi.edu> <568E5C93.5050201@gmail.com> <20160107124237.GP58491@Space.Net> <568E6552.9030008@gmail.com> <20160107132117.GV58491@Space.Net>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <568E6782.1000205@gmail.com>
Date: Thu, 07 Jan 2016 14:26:26 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0
MIME-Version: 1.0
In-Reply-To: <20160107132117.GV58491@Space.Net>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/e7fygy72392RJDnw5kQAYuPdS80>
Cc: v6ops@ietf.org
Subject: Re: [v6ops] Routers are hosts too! (Re: I-D Action: draft-ietf-v6ops-host-addr-availability-04.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
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, 07 Jan 2016 13:26:30 -0000


Le 07/01/2016 14:21, Gert Doering a écrit :
> Hi,
>
> On Thu, Jan 07, 2016 at 02:17:06PM +0100, Alexandre Petrescu wrote:
>> Le 07/01/2016 13:42, Gert Doering a écrit :
>>> On Thu, Jan 07, 2016 at 01:39:47PM +0100, Alexandre Petrescu
>>> wrote:
>>>> - a router does implement longest-matching algorithms, a Host
>>>> doesn't.
>>>
>>> Of course hosts do.  Why would any implementor not do that?
>>
>> Why would a Host need to look out a nexthop in routing table?  To
>> forward to whom?
>
> Well, it needs to send its own packets somewhere, no?

YEs, to its router.  There's only one - the default.  There are no 
neighbors to distinguish from.

> And guess what, this is done using the normal routing table

Yes, the 'normal' routing table because that's what we're used with 
since linux and Ethernet.

But a Host using serial to connect to a router (e.g. a UE) does not need 
a routing table.

> which (if
> you set ip.forwarding=1) magically turns into a forwarding table.
>
> Hosts can have more than one interface, like "a LAN interface and a
> VPN tunnel interface".  It really helps if they know which packet
> goes where.

YEs, but these are not pure Hosts.  They are more like desktop PCs and 
smartphones.

Alex

>
> Gert Doering -- NetMaster
>