Re: [homenet] Info about IS-IS demo from Bits N Bites Prague

Mikael Abrahamsson <swmike@swm.pp.se> Thu, 24 September 2015 06:10 UTC

Return-Path: <swmike@swm.pp.se>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5ABC01B319B for <homenet@ietfa.amsl.com>; Wed, 23 Sep 2015 23:10:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.961
X-Spam-Level:
X-Spam-Status: No, score=-3.961 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 LqjvuszPiSyU for <homenet@ietfa.amsl.com>; Wed, 23 Sep 2015 23:10:28 -0700 (PDT)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 61D941B319A for <homenet@ietf.org>; Wed, 23 Sep 2015 23:10:28 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id E8528A1; Thu, 24 Sep 2015 08:10:26 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1443075026; bh=1/Xtn75TFAfpgsWPuOucwUpw262CEGdCtF6+0OLv8uQ=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=aNXcrZyd+hRc8XBZZgfzWebiggEXGX3riw7h3uvdr0fNOOw3XVYZt4LUWOKzkomOa Gn3QgTieOUzyGjk7/k93A9gSXrWgXc84UcouYgsIlOyiYUDlO+4BR0RAUh6cgiy4Ss 8lgnYcjHJtPS7xawiD9ADEG3XBp6Mbl7ZZElaRXM=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id E41499F; Thu, 24 Sep 2015 08:10:26 +0200 (CEST)
Date: Thu, 24 Sep 2015 08:10:26 +0200
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
In-Reply-To: <87lhc3proz.wl-jch@pps.univ-paris-diderot.fr>
Message-ID: <alpine.DEB.2.02.1509240801390.8750@uplift.swm.pp.se>
References: <55FA3EF5.6000704@opensourcerouting.org> <87lhc3proz.wl-jch@pps.univ-paris-diderot.fr>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/QgN0zNBzylC6kBy12p6bURDSdbQ>
Cc: homenet@ietf.org, Christian Franke <chris@opensourcerouting.org>
Subject: Re: [homenet] Info about IS-IS demo from Bits N Bites Prague
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
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: Thu, 24 Sep 2015 06:10:35 -0000

On Fri, 18 Sep 2015, Juliusz Chroboczek wrote:

>> - Transport: both L2 & IPv6 (Link-Local)
>
> Which is suggested for Homenet?  The two don't interoperate, right?

Well, there is nothing that stops a device to form P2P neighbors over both 
ways, but since the feedback historically has been that L2 is hard in some 
devices (the protocol stack implementation is pretty much geared towards 
IPv4/IPv6), I'd suggest IPv6 LL for homenet.

>> - Point-to-Multi-Point or Broadcast over L2 or IPv6
>
> Which is suggested for Homenet?  Or do the two interoperate?

Historically you configure an interface as either LAN (default for 
ethernet) or P2P (default for point to point interfaces). My suggestion 
would be to use P2MP everywhere for simplicity, but I would really prefer 
to use LAN for wired ports, but since LAN ports can be bridged over all 
kinds of physical media, I guess P2MP is the safest way to go for 
everything to make sure we're not using multicast apart for discovery.

>> These are standard IS-IS wide metrics, although it makes use of the per
>> neighbor metrics available with draft-lamparter-isis-p2mp.
>
> Does this interoperate with standard IS-IS?

No, the draft explicitly states that P2MP is a new hello type and that 
P2MP routers must discard LAN and P2P Hello PDUs.

>> To address this, links without metric information (i.e. direct links
>> between clients) will not be considered for SPF. Since 802.11 frames
>> from clients to clients are relayed by the AP, this actually can reflect
>> the metrics better.
>
> Are you assuming that there are no dumb layer 2 APs in the network?

Yes, that is a tradeoff. If there are L2 APs then insight into the wifi 
layer is lost.

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