
From nobody Mon Feb  2 15:57:04 2015
Return-Path: <brian.e.carpenter@gmail.com>
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 54C4E1A86E8 for <homenet@ietfa.amsl.com>; Mon,  2 Feb 2015 15:57:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 KOkiQ3KfbJ_g for <homenet@ietfa.amsl.com>; Mon,  2 Feb 2015 15:57:01 -0800 (PST)
Received: from mail-pa0-x22f.google.com (mail-pa0-x22f.google.com [IPv6:2607:f8b0:400e:c03::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E12A21A86DD for <homenet@ietf.org>; Mon,  2 Feb 2015 15:57:00 -0800 (PST)
Received: by mail-pa0-f47.google.com with SMTP id lj1so88463799pab.6 for <homenet@ietf.org>; Mon, 02 Feb 2015 15:57:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=rycHo9eCTYpf7S+lTuEBy7KF/RRJcrgvqWGheefYQf8=; b=JbSROUG6PVKO5tzJnrW4SI+egFyRg7EturhdtpQvffZ+G8iiA9Ac1jr3oeMlCPJ3pc 9MYcRtYMC3Zt3ZCk6055E3J7ukdiCX525u5U1Gve5vkq2zvAY6bnYs8xHAPV7VMCY8l5 tbGGJNVgjY6DzClZIdnPpxvwyRKdYsHCdfODAwZf4H/kaOWVkZi7CUeIxQShk/wr0pa9 rtP77MjNuk9bKibwpmjL1ZmYSaNsZLRmEgl7SjCRVr8jyJmN58SIkxDIGQGPxA0gvKPx BKKZsRkwieHxUa49RUhedu0KxuPnCfuk42ZFq8WYH33r53phogDL9RykkFChqBftPV69 marw==
X-Received: by 10.66.162.41 with SMTP id xx9mr33717025pab.68.1422921420147; Mon, 02 Feb 2015 15:57:00 -0800 (PST)
Received: from ?IPv6:2001:df0:0:2006:c0da:ac17:5f6d:8e76? ([2001:df0:0:2006:c0da:ac17:5f6d:8e76]) by mx.google.com with ESMTPSA id pn2sm177526pbb.42.2015.02.02.15.56.57 for <homenet@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 02 Feb 2015 15:56:59 -0800 (PST)
Message-ID: <54D00ECA.1070802@gmail.com>
Date: Tue, 03 Feb 2015 12:56:58 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: HOMENET <homenet@ietf.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/Zln_Zh3M_EQlNqNDLSWyXxyUWVU>
Subject: [homenet] Homenets and MPVD
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 02 Feb 2015 23:57:02 -0000

Hi,

I find myself wondering how draft-ietf-homenet-prefix-assignment
and draft-ietf-homenet-hncp will be reconciled with the MIF
MPVD architecture
(http://datatracker.ietf.org/doc/draft-ietf-mif-mpvd-arch/).
Has anybody thought about that yet?


Regards
   Brian


From nobody Mon Feb  2 23:46:58 2015
Return-Path: <pierre.pfister@darou.fr>
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 2B0801A86EF for <homenet@ietfa.amsl.com>; Mon,  2 Feb 2015 23:46:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.357
X-Spam-Level: 
X-Spam-Status: No, score=-1.357 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553, T_RP_MATCHES_RCVD=-0.01] autolearn=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 gQBbGwtARFLf for <homenet@ietfa.amsl.com>; Mon,  2 Feb 2015 23:46:54 -0800 (PST)
Received: from ks395963.kimsufi.com (darou.fr [IPv6:2001:41d0:8:408c::1111]) by ietfa.amsl.com (Postfix) with ESMTP id 4EB5C1A86E3 for <homenet@ietf.org>; Mon,  2 Feb 2015 23:46:54 -0800 (PST)
Received: by ks395963.kimsufi.com (Postfix, from userid 112) id 697FE60900; Tue,  3 Feb 2015 08:46:53 +0100 (CET)
Received: from [IPv6:2001:470:c974:1:c186:5caf:7a1f:fc54] (unknown [IPv6:2001:470:c974:1:c186:5caf:7a1f:fc54]) (Authenticated sender: pierre@darou.fr) by ks395963.kimsufi.com (Postfix) with ESMTPSA id 9EBB260653; Tue,  3 Feb 2015 08:46:51 +0100 (CET)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Pierre Pfister <pierre.pfister@darou.fr>
In-Reply-To: <54D00ECA.1070802@gmail.com>
Date: Tue, 3 Feb 2015 08:46:53 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <84ECBDCC-DAE1-4227-B7C6-27978063CB3D@darou.fr>
References: <54D00ECA.1070802@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/kwpn-wexxqwPPZqYAj182ISrnnk>
Cc: HOMENET <homenet@ietf.org>
Subject: Re: [homenet] Homenets and MPVD
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Tue, 03 Feb 2015 07:46:56 -0000

Hello Brian,

MIF targets host configuration with PVDs. For that purpose, they are =
likely to do it using DHCP and RA options.
Service providers will also use such options for CPE routers =
configuration, associated with the delegated prefixes during the DHCP =
exchange.

Current HNCP strategy is to abstract what can be conveyed inside DHCP =
options by sharing them directly with all other routers.
For every external connection, CPE routers will advertise an External =
Connection TLV (Section 6.1. in HNCP).
This TLV may contain one or multiple Delegated Prefix TLVs as well as =
raw DHCP options (in the DHCPv4 or DHCPv6 TLV) associated with the =
external connection (e.g. DNS delegated zone or search domains).
Each Delegated Prefix may as well be associated with different DHCP =
options (e.g. Prefix class options).

All routers gather this information through HNCP and use it to configure =
hosts. DHCP options that are associated with a given delegated prefix =
are given to hosts associated with the link prefix provided by the =
prefix assignment algorithm. DHCP options that are not associated with a =
delegated prefix are aggregated and given to the host (Excepted for the =
DNS server option, as the router is used as DNS relay).
For now, the aggregation of such information is not specified (although =
in practice it can be done quite easily for most DHCP options).
But I believe it will be much clearer once MIF provides PVD =
specifications.

I think this approach will be sufficient. If it happen to not be, =
External Connection TLVs and Delegated Prefixes TLVs could contain other =
types of TLVs.

Regards,

  Pierre


Le 3 f=E9vr. 2015 =E0 00:56, Brian E Carpenter =
<brian.e.carpenter@gmail.com> a =E9crit :

> Hi,
>=20
> I find myself wondering how draft-ietf-homenet-prefix-assignment
> and draft-ietf-homenet-hncp will be reconciled with the MIF
> MPVD architecture
> (http://datatracker.ietf.org/doc/draft-ietf-mif-mpvd-arch/).
> Has anybody thought about that yet?
>=20
>=20
> Regards
>   Brian
>=20
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet


From nobody Tue Feb  3 00:53:23 2015
Return-Path: <markus.stenberg@iki.fi>
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 A77811A870F for <homenet@ietfa.amsl.com>; Tue,  3 Feb 2015 00:53:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.121
X-Spam-Level: 
X-Spam-Status: No, score=-1.121 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_NEUTRAL=0.779] autolearn=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 4c6-DUYMsL-w for <homenet@ietfa.amsl.com>; Tue,  3 Feb 2015 00:53:20 -0800 (PST)
Received: from kirsi1.inet.fi (mta-out1.inet.fi [62.71.2.195]) by ietfa.amsl.com (Postfix) with ESMTP id 099721A870E for <homenet@ietf.org>; Tue,  3 Feb 2015 00:53:19 -0800 (PST)
Received: from poro.lan (80.220.64.126) by kirsi1.inet.fi (8.5.142.08) (authenticated as stenma-47) id 54C8A39200B051ED; Tue, 3 Feb 2015 10:53:17 +0200
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Markus Stenberg <markus.stenberg@iki.fi>
In-Reply-To: <84ECBDCC-DAE1-4227-B7C6-27978063CB3D@darou.fr>
Date: Tue, 3 Feb 2015 10:53:16 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <F7309B04-BBA5-40F0-B87F-118E3F4C2B43@iki.fi>
References: <54D00ECA.1070802@gmail.com> <84ECBDCC-DAE1-4227-B7C6-27978063CB3D@darou.fr>
To: Pierre Pfister <pierre.pfister@darou.fr>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/79s5IhmMSk9HabCdivvMkeG3T_o>
Cc: HOMENET <homenet@ietf.org>, Markus Stenberg <markus.stenberg@iki.fi>
Subject: Re: [homenet] Homenets and MPVD
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Tue, 03 Feb 2015 08:53:21 -0000

On 3.2.2015, at 9.46, Pierre Pfister <pierre.pfister@darou.fr> wrote:
> All routers gather this information through HNCP and use it to =
configure hosts. DHCP options that are associated with a given delegated =
prefix are given to hosts associated with the link prefix provided by =
the prefix assignment algorithm. DHCP options that are not associated =
with a delegated prefix are aggregated and given to the host (Excepted =
for the DNS server option, as the router is used as DNS relay).

DNS server option is mostly changed so we can do in-home service =
discovery. In MIF world, we would probably pass along DNS servers within =
PVDs as is, provide (e.g.) =91.home=92 PVD for in-home services only, =
and provide only to legacy clients the =91relay=92 DNS server address. =
So oddly enough, current scheme would work, most likely as-is ;) The =
unknown new PVD option would be passed along as is, and the clients =
would treat the provided legacy DNS server (+search path) as an extra =
implicit PVD with hopefully lower priority than the explicit PVDs.

Not changing PVDs may be crucial if the PVD authentication ever takes =
hold, as changing it=92s content then may make it altogether invalid =
from the client=92s point of view.=20

Cheers,

-Markus=


From nobody Tue Feb  3 01:07:55 2015
Return-Path: <ot@cisco.com>
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 CB0251A8711 for <homenet@ietfa.amsl.com>; Tue,  3 Feb 2015 01:07:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 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_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 iOemw-JXBYv0 for <homenet@ietfa.amsl.com>; Tue,  3 Feb 2015 01:07:52 -0800 (PST)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 736B91A871D for <homenet@ietf.org>; Tue,  3 Feb 2015 01:07:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1658; q=dns/txt; s=iport; t=1422954471; x=1424164071; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=/jlcUeo5bUHs2ea538tCiqKmdzFzo9KPWt1A2Rd8Abw=; b=jHut/9PteJ0kkW1ShrZ5s5YlRQvmaq8snXgxmy38wrIFVOo7FsX/keQZ wZG2TCnkk65t9toJYUxvNxIgsaVBbksmdX3C1nxvgsCtKlYfaOnFbYnRa 3s8uRJOOZqLWEXTntuEmVoal05SJ5j3JdY8Iy59ZLBNAQpSF4Ij4BMYQ2 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ClBABMj9BU/xbLJq1agmTMRQKBXwEBAQEBfYQNAQEDAXkQC0ZXBog4CAHVZQEBAQEBAQEBAQEBAQEBAQEBAQEBARePRTMHgxaBEwWYLpJcIoNvgzABAQE
X-IronPort-AV: E=Sophos;i="5.09,511,1418083200"; d="scan'208";a="332703316"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP; 03 Feb 2015 09:07:49 +0000
Received: from OTROAN-M-Q0RH.localdomain (ssh-ams-2.cisco.com [144.254.73.146]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id t1397mMe006944 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 3 Feb 2015 09:07:49 GMT
Received: from [IPv6:::1] (localhost [IPv6:::1]) by OTROAN-M-Q0RH.localdomain (Postfix) with ESMTP id 60B613DE34A7; Tue,  3 Feb 2015 10:07:52 +0100 (CET)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Ole Troan <ot@cisco.com>
In-Reply-To: <F7309B04-BBA5-40F0-B87F-118E3F4C2B43@iki.fi>
Date: Tue, 3 Feb 2015 10:07:52 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <4193A650-550D-4CA5-B23D-06AECA4F645A@cisco.com>
References: <54D00ECA.1070802@gmail.com> <84ECBDCC-DAE1-4227-B7C6-27978063CB3D@darou.fr> <F7309B04-BBA5-40F0-B87F-118E3F4C2B43@iki.fi>
To: Markus Stenberg <markus.stenberg@iki.fi>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/BtIp_DNgvw84ryhqbKb-9x37Ng4>
Cc: HOMENET <homenet@ietf.org>, Pierre Pfister <pierre.pfister@darou.fr>
Subject: Re: [homenet] Homenets and MPVD
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Tue, 03 Feb 2015 09:07:54 -0000

Markus,

>> All routers gather this information through HNCP and use it to =
configure hosts. DHCP options that are associated with a given delegated =
prefix are given to hosts associated with the link prefix provided by =
the prefix assignment algorithm. DHCP options that are not associated =
with a delegated prefix are aggregated and given to the host (Excepted =
for the DNS server option, as the router is used as DNS relay).
>=20
> DNS server option is mostly changed so we can do in-home service =
discovery. In MIF world, we would probably pass along DNS servers within =
PVDs as is, provide (e.g.) =91.home=92 PVD for in-home services only, =
and provide only to legacy clients the =91relay=92 DNS server address. =
So oddly enough, current scheme would work, most likely as-is ;) The =
unknown new PVD option would be passed along as is, and the clients =
would treat the provided legacy DNS server (+search path) as an extra =
implicit PVD with hopefully lower priority than the explicit PVDs.
>=20
> Not changing PVDs may be crucial if the PVD authentication ever takes =
hold, as changing it=92s content then may make it altogether invalid =
from the client=92s point of view.=20

is it actually obvious that you'd pass the PVDs to the hosts in =
homenets?
PVDs contain policy. and allowing them to pass the administrative =
boundary into a home is also up to policy.
given that we already have options to control DNS server selection =
policy. why can't the home border amalgamate that information (according =
to local policy)?

sorry, I'm struggling to understand the PVD use case I suppose.

cheers,
Ole=


From nobody Tue Feb  3 01:27:32 2015
Return-Path: <markus.stenberg@iki.fi>
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 A7C2D1A0062 for <homenet@ietfa.amsl.com>; Tue,  3 Feb 2015 01:27:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.121
X-Spam-Level: 
X-Spam-Status: No, score=-1.121 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_NEUTRAL=0.779] autolearn=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 KUkYqZsWxTkg for <homenet@ietfa.amsl.com>; Tue,  3 Feb 2015 01:27:29 -0800 (PST)
Received: from jenni2.inet.fi (mta-out1.inet.fi [62.71.2.203]) by ietfa.amsl.com (Postfix) with ESMTP id 072B01A0055 for <homenet@ietf.org>; Tue,  3 Feb 2015 01:27:29 -0800 (PST)
Received: from poro.lan (80.220.64.126) by jenni2.inet.fi (8.5.142.08) (authenticated as stenma-47) id 54C8F2EA00A95B24; Tue, 3 Feb 2015 11:27:23 +0200
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Markus Stenberg <markus.stenberg@iki.fi>
In-Reply-To: <4193A650-550D-4CA5-B23D-06AECA4F645A@cisco.com>
Date: Tue, 3 Feb 2015 11:27:22 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <749396A0-A21C-47DF-94E1-DB3FDB7C1485@iki.fi>
References: <54D00ECA.1070802@gmail.com> <84ECBDCC-DAE1-4227-B7C6-27978063CB3D@darou.fr> <F7309B04-BBA5-40F0-B87F-118E3F4C2B43@iki.fi> <4193A650-550D-4CA5-B23D-06AECA4F645A@cisco.com>
To: Ole Troan <ot@cisco.com>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/PfNsIfE1sYFc077O95-GbTCvBWA>
Cc: HOMENET <homenet@ietf.org>, Markus Stenberg <markus.stenberg@iki.fi>, Pierre Pfister <pierre.pfister@darou.fr>
Subject: Re: [homenet] Homenets and MPVD
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Tue, 03 Feb 2015 09:27:30 -0000

On 3.2.2015, at 11.07, Ole Troan <ot@cisco.com> wrote:
>>> All routers gather this information through HNCP and use it to =
configure hosts. DHCP options that are associated with a given delegated =
prefix are given to hosts associated with the link prefix provided by =
the prefix assignment algorithm. DHCP options that are not associated =
with a delegated prefix are aggregated and given to the host (Excepted =
for the DNS server option, as the router is used as DNS relay).
>>=20
>> DNS server option is mostly changed so we can do in-home service =
discovery. In MIF world, we would probably pass along DNS servers within =
PVDs as is, provide (e.g.) =91.home=92 PVD for in-home services only, =
and provide only to legacy clients the =91relay=92 DNS server address. =
So oddly enough, current scheme would work, most likely as-is ;) The =
unknown new PVD option would be passed along as is, and the clients =
would treat the provided legacy DNS server (+search path) as an extra =
implicit PVD with hopefully lower priority than the explicit PVDs.
>>=20
>> Not changing PVDs may be crucial if the PVD authentication ever takes =
hold, as changing it=92s content then may make it altogether invalid =
from the client=92s point of view.=20
> is it actually obvious that you'd pass the PVDs to the hosts in =
homenets?
> PVDs contain policy. and allowing them to pass the administrative =
boundary into a home is also up to policy.
> given that we already have options to control DNS server selection =
policy. why can't the home border amalgamate that information (according =
to local policy)?
>=20
> sorry, I=92m struggling to understand the PVD use case I suppose.

I vaguely remember one homenet design goal to be as transparent to =
clients as possible.

PVD tell you also about the kind of connectivity available there etc. =
While I am sure we _could_ fabricate local one, it is much easier to =
tell that e.g. one upstream connection is pay-per-byte 4g, and other one =
is VDSL2 and let hosts make educated choices instead of guesses about =
source prefixes to use.

Is this covered somewhere elsewhere in the DHCP option jungle?

Cheers,

-Markus


From nobody Tue Feb  3 04:01:00 2015
Return-Path: <mellon@fugue.com>
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 4B30D1A8850 for <homenet@ietfa.amsl.com>; Tue,  3 Feb 2015 04:00:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 b1B-FHWRhx2z for <homenet@ietfa.amsl.com>; Tue,  3 Feb 2015 04:00:54 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id B87571A00F9 for <homenet@ietf.org>; Tue,  3 Feb 2015 04:00:54 -0800 (PST)
Received: from [172.19.131.133] (unknown [12.130.116.26]) by toccata.fugue.com (Postfix) with ESMTPSA id B08492380431; Tue,  3 Feb 2015 07:00:52 -0500 (EST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <4193A650-550D-4CA5-B23D-06AECA4F645A@cisco.com>
Date: Tue, 3 Feb 2015 07:00:40 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <D88EC731-65EC-4157-80CE-5C49503A499A@fugue.com>
References: <54D00ECA.1070802@gmail.com> <84ECBDCC-DAE1-4227-B7C6-27978063CB3D@darou.fr> <F7309B04-BBA5-40F0-B87F-118E3F4C2B43@iki.fi> <4193A650-550D-4CA5-B23D-06AECA4F645A@cisco.com>
To: Ole Troan <ot@cisco.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/jLPjbl4ab4Qjn6CA0neEbucmpeo>
Cc: HOMENET <homenet@ietf.org>, Markus Stenberg <markus.stenberg@iki.fi>, Pierre Pfister <pierre.pfister@darou.fr>
Subject: Re: [homenet] Homenets and MPVD
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Tue, 03 Feb 2015 12:00:57 -0000

On Feb 3, 2015, at 4:07 AM, Ole Troan <ot@cisco.com> wrote:
> is it actually obvious that you'd pass the PVDs to the hosts in =
homenets?
> PVDs contain policy. and allowing them to pass the administrative =
boundary into a home is also up to policy.
> given that we already have options to control DNS server selection =
policy. why can't the home border amalgamate that information (according =
to local policy)?

This is actually accounted for in the MPVD arch document.   However, =
that document does not contain a specific description of how to make =
PVDs work in a homenet--it just mentions the possibility that one might =
want to relay some information from the ISP intact to preserve signature =
information.   I think that there should be a follow-on document that =
explains how to do MPVD in a homenet environment and goes through the =
various scenarios.   What Markus described is pretty much what we had in =
mind.


From nobody Tue Feb  3 04:03:04 2015
Return-Path: <mellon@fugue.com>
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 484C11A89BB for <homenet@ietfa.amsl.com>; Tue,  3 Feb 2015 04:03:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 f0tbKM1nNtWx for <homenet@ietfa.amsl.com>; Tue,  3 Feb 2015 04:02:58 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id A006B1A89FE for <homenet@ietf.org>; Tue,  3 Feb 2015 04:02:56 -0800 (PST)
Received: from [172.19.131.133] (unknown [12.130.116.26]) by toccata.fugue.com (Postfix) with ESMTPSA id 4304C2380431; Tue,  3 Feb 2015 07:02:55 -0500 (EST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <749396A0-A21C-47DF-94E1-DB3FDB7C1485@iki.fi>
Date: Tue, 3 Feb 2015 07:02:53 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <3C89B71C-E9FA-44F3-9576-B0A7E9DD6D13@fugue.com>
References: <54D00ECA.1070802@gmail.com> <84ECBDCC-DAE1-4227-B7C6-27978063CB3D@darou.fr> <F7309B04-BBA5-40F0-B87F-118E3F4C2B43@iki.fi> <4193A650-550D-4CA5-B23D-06AECA4F645A@cisco.com> <749396A0-A21C-47DF-94E1-DB3FDB7C1485@iki.fi>
To: Markus Stenberg <markus.stenberg@iki.fi>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/WR3kQene6sO9gPSlCgBTGkpazUk>
Cc: Ole Troan <ot@cisco.com>, HOMENET <homenet@ietf.org>, Pierre Pfister <pierre.pfister@darou.fr>
Subject: Re: [homenet] Homenets and MPVD
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Tue, 03 Feb 2015 12:03:02 -0000

On Feb 3, 2015, at 4:27 AM, Markus Stenberg <markus.stenberg@iki.fi> =
wrote:
> PVD tell you also about the kind of connectivity available there etc. =
While I am sure we _could_ fabricate local one, it is much easier to =
tell that e.g. one upstream connection is pay-per-byte 4g, and other one =
is VDSL2 and let hosts make educated choices instead of guesses about =
source prefixes to use.

One of the design goals of the PVD architecture is to make it possible =
to get the same behavior in a 4G handset with a Wifi interface and in a =
laptop with no 4G interface that's connected to a network with a 4G PVD =
and a wireline PVD.

> Is this covered somewhere elsewhere in the DHCP option jungle?

A document is being worked on to address this, but no, it is not yet =
covered.


From nobody Tue Feb  3 05:57:41 2015
Return-Path: <otroan@employees.org>
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 E0E521A0362 for <homenet@ietfa.amsl.com>; Tue,  3 Feb 2015 05:57:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.011
X-Spam-Level: 
X-Spam-Status: No, score=-2.011 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 NngFFQP_fL11 for <homenet@ietfa.amsl.com>; Tue,  3 Feb 2015 05:57:37 -0800 (PST)
Received: from banjo.employees.org (banjo.employees.org [198.137.202.19]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1FCF31A03A9 for <homenet@ietf.org>; Tue,  3 Feb 2015 05:57:37 -0800 (PST)
Received: from banjo.employees.org (localhost [127.0.0.1]) by banjo.employees.org (Postfix) with ESMTP id 3457F629F; Tue,  3 Feb 2015 05:57:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s= selector1; bh=hGdLrNez9Jma4Jwi0suWAKkHTJE=; b=P2TafEh7B67ommZtq0 GdRo1jWfmlRNbpLqVTOwEQpF44fP9xEu15IAC6m/ePMZddrCu1mqnhfWcvRZQJ/s RpnSLN6UQ/JLdxq0EjvHYXygBIPG/U6hb5wpvGugEwe2QZ4llXSry5FI6Zfqpdj0 WhG9yP7Is5IUj6eOQjqWSRtcM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; q=dns; s= selector1; b=J10zE2pLlaH25Dk1XIybV12Lki/Y3xEA8Ky2MeAmpuKF+snHaht Pj5v+FGT8MkpBpygnM7waRXJRdo6P3yJOdJVgbV+GvRivIyw8Gt0StkKRj/swR72 1OVxPD+F1lsUY80g8oQhIEpG5AJKTmPWm9cPKu4ppeiG/9dflYfrfO8c=
Received: from OTROAN-M-Q0RH.localdomain (unknown [195.159.234.46]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id DF75E628B; Tue,  3 Feb 2015 05:57:35 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by OTROAN-M-Q0RH.localdomain (Postfix) with ESMTP id 6DF753DEBFCA; Tue,  3 Feb 2015 14:57:33 +0100 (CET)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Ole Troan <otroan@employees.org>
In-Reply-To: <3C89B71C-E9FA-44F3-9576-B0A7E9DD6D13@fugue.com>
Date: Tue, 3 Feb 2015 14:57:33 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <DEF142FA-C85C-471D-96E5-4773494DBD0D@employees.org>
References: <54D00ECA.1070802@gmail.com> <84ECBDCC-DAE1-4227-B7C6-27978063CB3D@darou.fr> <F7309B04-BBA5-40F0-B87F-118E3F4C2B43@iki.fi> <4193A650-550D-4CA5-B23D-06AECA4F645A@cisco.com> <749396A0-A21C-47DF-94E1-DB3FDB7C1485@iki.fi> <3C89B71C-E9FA-44F3-9576-B0A7E9DD6D13@fugue.com>
To: Ted Lemon <mellon@fugue.com>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/nYVeQdmyVBagOeRwjeKjUKoABAE>
Cc: HOMENET <homenet@ietf.org>, Markus Stenberg <markus.stenberg@iki.fi>, Pierre Pfister <pierre.pfister@darou.fr>
Subject: Re: [homenet] Homenets and MPVD
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Tue, 03 Feb 2015 13:57:39 -0000

>> PVD tell you also about the kind of connectivity available there etc. =
While I am sure we _could_ fabricate local one, it is much easier to =
tell that e.g. one upstream connection is pay-per-byte 4g, and other one =
is VDSL2 and let hosts make educated choices instead of guesses about =
source prefixes to use.
>=20
> One of the design goals of the PVD architecture is to make it possible =
to get the same behavior in a 4G handset with a Wifi interface and in a =
laptop with no 4G interface that's connected to a network with a 4G PVD =
and a wireline PVD.

what behaviour is that?

>> Is this covered somewhere elsewhere in the DHCP option jungle?
>=20
> A document is being worked on to address this, but no, it is not yet =
covered.
>=20

cheers,
Ole


From nobody Tue Feb  3 06:09:45 2015
Return-Path: <mellon@fugue.com>
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 7CE431A0065 for <homenet@ietfa.amsl.com>; Tue,  3 Feb 2015 06:09:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 2P24wwbG2h2k for <homenet@ietfa.amsl.com>; Tue,  3 Feb 2015 06:09:12 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 00D501A0382 for <homenet@ietf.org>; Tue,  3 Feb 2015 06:09:11 -0800 (PST)
Received: from [172.19.131.133] (unknown [12.130.116.26]) by toccata.fugue.com (Postfix) with ESMTPSA id 2FF9A2380431; Tue,  3 Feb 2015 09:09:04 -0500 (EST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <DEF142FA-C85C-471D-96E5-4773494DBD0D@employees.org>
Date: Tue, 3 Feb 2015 08:08:44 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <1D6A0F78-F153-40FB-85FF-4AD7A1A25C94@fugue.com>
References: <54D00ECA.1070802@gmail.com> <84ECBDCC-DAE1-4227-B7C6-27978063CB3D@darou.fr> <F7309B04-BBA5-40F0-B87F-118E3F4C2B43@iki.fi> <4193A650-550D-4CA5-B23D-06AECA4F645A@cisco.com> <749396A0-A21C-47DF-94E1-DB3FDB7C1485@iki.fi> <3C89B71C-E9FA-44F3-9576-B0A7E9DD6D13@fugue.com> <DEF142FA-C85C-471D-96E5-4773494DBD0D@employees.org>
To: Ole Troan <otroan@employees.org>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/CrtDDT64OvDWOXiKRf8oqxuU8mA>
Cc: HOMENET <homenet@ietf.org>, Markus Stenberg <markus.stenberg@iki.fi>, Pierre Pfister <pierre.pfister@darou.fr>
Subject: Re: [homenet] Homenets and MPVD
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Tue, 03 Feb 2015 14:09:21 -0000

On Feb 3, 2015, at 7:57 AM, Ole Troan <otroan@employees.org> wrote:
> what behaviour is that?

At the moment, handsets typically prefer wifi if available.   Android 5 =
will actually use both interfaces in an MPVD-style separation, so that =
the presence of a WiFi interface is taken advantage of if it works, but =
doesn't break the 4G service if WiFi is nonfunctional.   This is one of =
the general goals of the MPVD architecture.

It would be nice if the same behavior could be achieved on a homenet.


From nobody Sun Feb  8 05:38:17 2015
Return-Path: <internet-drafts@ietf.org>
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 5C4AE1A8F4D; Sun,  8 Feb 2015 05:38:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 PF8A4i9LkEBC; Sun,  8 Feb 2015 05:38:08 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A5B711A8F51; Sun,  8 Feb 2015 05:38:05 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.10.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150208133805.7282.74527.idtracker@ietfa.amsl.com>
Date: Sun, 08 Feb 2015 05:38:05 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/A17AvAbF-yREB1iegpH48VGyw0k>
Cc: homenet@ietf.org
Subject: [homenet] I-D Action: draft-ietf-homenet-prefix-assignment-03.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sun, 08 Feb 2015 13:38:10 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Home Networking Working Group of the IETF.

        Title           : Distributed Prefix Assignment Algorithm
        Authors         : Pierre Pfister
                          Benjamin Paterson
                          Jari Arkko
	Filename        : draft-ietf-homenet-prefix-assignment-03.txt
	Pages           : 18
	Date            : 2015-02-08

Abstract:
   This document specifies a distributed algorithm for automatic prefix
   assignment.  Given a set of delegated prefixes, it ensures that at
   most one prefix is assigned from each delegated prefix to each link.
   Nodes may assign available prefixes to the links they are directly
   connected to, or for other private purposes.  The algorithm
   eventually converges and ensures that all assigned prefixes do not
   overlap.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-homenet-prefix-assignment/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-homenet-prefix-assignment-03

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-homenet-prefix-assignment-03


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Tue Feb 10 07:42:14 2015
Return-Path: <boutier@pps.univ-paris-diderot.fr>
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 0B5951A0470 for <homenet@ietfa.amsl.com>; Tue, 10 Feb 2015 07:42:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.15
X-Spam-Level: *
X-Spam-Status: No, score=1.15 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_EQ_FR=0.35] autolearn=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 PvtKyiAWdHVi for <homenet@ietfa.amsl.com>; Tue, 10 Feb 2015 07:42:10 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 BF43D1A0469 for <homenet@ietf.org>; Tue, 10 Feb 2015 07:42:09 -0800 (PST)
Received: from potemkin.univ-paris7.fr (potemkin.univ-paris7.fr [IPv6:2001:660:3301:8000::1:1]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t1AFg7fx024879 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <homenet@ietf.org>; Tue, 10 Feb 2015 16:42:07 +0100
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by potemkin.univ-paris7.fr (8.14.4/8.14.4/relay2/56228) with ESMTP id t1AFg7FF029631 for <homenet@ietf.org>; Tue, 10 Feb 2015 16:42:07 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 7F2652BDB79 for <homenet@ietf.org>; Tue, 10 Feb 2015 16:42:07 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id 7klshoHEk1D2; Tue, 10 Feb 2015 16:42:05 +0100 (CET)
Received: from host-36-84.sg.lan (unknown [172.23.36.84]) (Authenticated sender: boutier) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 79C4A2BDB78; Tue, 10 Feb 2015 16:42:02 +0100 (CET)
From: Matthieu Boutier <boutier@pps.univ-paris-diderot.fr>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Tue, 10 Feb 2015 16:42:03 +0100
Message-Id: <3D172733-DDDD-49BB-A91E-75BA6BB078AE@pps.univ-paris-diderot.fr>
To: HOMENET <homenet@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1283)
X-Mailer: Apple Mail (2.1283)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]); Tue, 10 Feb 2015 16:42:07 +0100 (CET)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Tue, 10 Feb 2015 16:42:07 +0100 (CET)
X-Miltered: at korolev with ID 54DA26CF.003 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 54DA26CF.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54DA26CF.003 from potemkin.univ-paris7.fr/potemkin.univ-paris7.fr/null/potemkin.univ-paris7.fr/<boutier@pps.univ-paris-diderot.fr>
X-j-chkmail-Enveloppe: 54DA26CF.001 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<boutier@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54DA26CF.003 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 54DA26CF.001 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/BtGz4TMqF4pP7-e9vVJRy5GJikg>
Cc: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: [homenet] User-space multipath-UDP in Mosh
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Tue, 10 Feb 2015 15:42:12 -0000

Hello,

We made a multipath version of Mosh[1], taking benefit of =
source-specific routing.  It is built at the application layer over UDP. =
 The following paper relates our experience:

    http://arxiv.org/abs/1502.02402

The source code is available on:

    https://github.com/boutier/mosh

Matthieu


From nobody Fri Feb 13 13:12:31 2015
Return-Path: <mark@townsley.net>
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 213F71A1A57 for <homenet@ietfa.amsl.com>; Fri, 13 Feb 2015 13:12:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.983
X-Spam-Level: 
X-Spam-Status: No, score=0.983 tagged_above=-999 required=5 tests=[BAYES_50=0.8, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, HTML_OBFUSCATE_05_10=0.26, RCVD_IN_DNSWL_LOW=-0.7] 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 nZTOQQbxiAvY for <homenet@ietfa.amsl.com>; Fri, 13 Feb 2015 13:12:26 -0800 (PST)
Received: from mail-lb0-f170.google.com (mail-lb0-f170.google.com [209.85.217.170]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D012A1A1A58 for <homenet@ietf.org>; Fri, 13 Feb 2015 13:12:25 -0800 (PST)
Received: by mail-lb0-f170.google.com with SMTP id u14so17847123lbd.1 for <homenet@ietf.org>; Fri, 13 Feb 2015 13:12:23 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=OfXsp93vjHCkdjI7LlsekFX3YNQ6RWLzk/8m490rrYE=; b=d5VF2YrOetJGiFy0BeTpmdC54jylQQN0ehf/40D32EA7PcJGHI4/r9aNAYtV00cSn9 f7MnXdJAuJvcDUPt4UDUHSwyc0mkOLgZwomXK8em4E3sWnLl5bwb1F61db/XnUrjROBg CgPDdWSvBFRCR8lCCpRFkow1MvdzIeJwqx0FjK7QC9U9zlw9JlzW1Ew/xtAEQTIT0SgD txJMGaSarWNcFfx/ZF2Scy7z34puWQ/zct9QGmOSa9VXN8fPkzJmWRp4f7PcuQ+NwR4I BGgdNmQg5m03wcs5dJsHHghobdoamGJZor2CGACTnN8HqimnTN9I8FjE8HQTY4GyfKLq Xsbw==
X-Gm-Message-State: ALoCoQkoEId3NhU192VEcHnJWTPa7q6r++hpfQktbWxQA/KeSZM3kjTcZhexsCtcQEik8o/u2NvG
MIME-Version: 1.0
X-Received: by 10.112.140.74 with SMTP id re10mr10396151lbb.80.1423861942877;  Fri, 13 Feb 2015 13:12:22 -0800 (PST)
Received: by 10.112.170.73 with HTTP; Fri, 13 Feb 2015 13:12:22 -0800 (PST)
Date: Fri, 13 Feb 2015 22:12:22 +0100
Message-ID: <CAESTAVu3rezc33G_LZb+inVS-Ui0CX_EN8Yi9u7XcavEmoW1PQ@mail.gmail.com>
From: Mark Townsley <mark@townsley.net>
To: "homenet@ietf.org Group" <homenet@ietf.org>
Content-Type: multipart/alternative; boundary=001a11c341e050926c050efeb1a4
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/XvhQ-tDGuuTGw5ZkESRBJ3AOUuY>
Subject: [homenet] Getting ready for Dallas
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 13 Feb 2015 21:12:29 -0000

--001a11c341e050926c050efeb1a4
Content-Type: text/plain; charset=UTF-8

Howdy Y'all,

Ray and I would like to move forward with a few actions.

1. Last call on draft-ietf-homenet-prefix-assignment
<https://tools.ietf.org/wg/homenet/draft-ietf-homenet-prefix-assignment/>.
The fundamental mechanism documented here dates back as far as Oct 2011 (
draft-arkko-homenet-prefix-assignment-00), and has gone through quite a bit
of review and refinement. There are at least two open source
implementations, one in OSPF and the other HNCP.  Last call will commence
officially in the coming days (watch for the notice in the datatracker).

2. Move draft-stenberg-homenet-dnssd-hybrid-proxy-zeroconf
<https://tools.ietf.org/id/draft-stenberg-homenet-dnssd-hybrid-proxy-zeroconf-02.txt>
to
a Homenet WG document. This document is essentially a homenet application
of draft-ietf-dnssd-hybrid
<https://tools.ietf.org/wg/dnssd/draft-ietf-dnssd-hybrid/>, which is being
advanced within the dnssd WG. There is at least one open source
implementation, and the document has been presented and reviewed multiple
times.

3. We would like to call for review of draft-ietf-homenet-dncp
<https://tools.ietf.org/wg/homenet/draft-ietf-homenet-dncp/> in preparation
for Last Call by Dallas. This -00 document is the result of a document
reorg and generalization of functionality from HNCP. There is at least one
open source implementation available.

4. We would like to call for reivew of
draft-ietf-homenet-naming-architecture-dhc-options
<https://tools.ietf.org/wg/homenet/draft-ietf-homenet-naming-architecture-dhc-options/>
 and draft-ietf-homenet-front-end-naming-delegation
<https://tools.ietf.org/wg/homenet/draft-ietf-homenet-front-end-naming-delegation/>
in
preparation for Last Call by Dallas. These documents have been presented
numerous times, with comments integrated.

5. draft-ietf-homenet-hncp
<https://tools.ietf.org/wg/homenet/draft-ietf-homenet-hncp/> should contain
solely the Homenet-specific application of DNCP and PA, as well as
discussion on routing. This document will remain open until the "Routing
Protocol" question is resolved, which will be the main focus of Dallas
(alongside any review comments from the above 4 actions). To assist in that
discussion, Margaret has been working with ISIS and babel experts to pull
together a document which you may have seen posted as a -00 a few days ago
if you were watching very carefully. Unfortunately, this -00 was a bit
premature, and the authors have promised a -01 very soon. Please note that
this document is not a representation of consensus among the authors, and
is not the out put of a design team, but simply a collection of facts,
observations, and points of view by the authors in order to facilitate
discussion. Expect an email to the list once the -01 document has been
published by Margaret (within days if not hours).

Finally, please get ready for a lively discussion on list and in Dallas.
Don't hold back! And, If you want agenda time in Dallas, please make Ray
and I aware.

Thanks!

- Mark

--001a11c341e050926c050efeb1a4
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div>Howdy Y&#39;all,</div><div><br></div><div>Ray and=
 I would like to move forward with a few actions.=C2=A0</div><div><br></div=
><div>1. Last call on=C2=A0<a href=3D"https://tools.ietf.org/wg/homenet/dra=
ft-ietf-homenet-prefix-assignment/" style=3D"color:rgb(68,0,136);border-bot=
tom-width:0px;font-family:&#39;Times New Roman&#39;,times,serif;font-size:1=
4.6666669845581px">draft-ietf-homenet-prefix-assignment</a>. The fundamenta=
l mechanism documented here dates back as far as Oct 2011 (<span style=3D"c=
olor:rgb(0,0,0);white-space:pre-wrap">draft-arkko-homenet-prefix-assignment=
-00)</span>, and has gone through quite a bit of review and refinement. The=
re are at least two open source implementations, one in OSPF and the other =
HNCP.=C2=A0 Last call will commence officially in the coming days (watch fo=
r the notice in the datatracker).=C2=A0</div><div><br></div><div>2. Move=C2=
=A0<a href=3D"https://tools.ietf.org/id/draft-stenberg-homenet-dnssd-hybrid=
-proxy-zeroconf-02.txt" style=3D"color:rgb(68,0,136);border-bottom-width:0p=
x;font-family:&#39;Times New Roman&#39;,times,serif;font-size:14.6666669845=
581px">draft-stenberg-homenet-dnssd-hybrid-proxy-zeroconf</a>=C2=A0to a Hom=
enet WG document. This document is essentially a homenet application of=C2=
=A0<a href=3D"https://tools.ietf.org/wg/dnssd/draft-ietf-dnssd-hybrid/" sty=
le=3D"color:rgb(68,0,136);border-bottom-width:0px;font-family:&#39;Times Ne=
w Roman&#39;,times,serif;font-size:14.6666669845581px">draft-ietf-dnssd-hyb=
rid</a>, which is being advanced within the dnssd WG. There is at least one=
 open source implementation, and the document has been presented and review=
ed multiple times.</div><div><br></div><div>3. We would like to call for re=
view of=C2=A0<a href=3D"https://tools.ietf.org/wg/homenet/draft-ietf-homene=
t-dncp/" style=3D"color:rgb(68,0,136);border-bottom-width:0px;font-family:&=
#39;Times New Roman&#39;,times,serif;font-size:14.6666669845581px">draft-ie=
tf-homenet-dncp</a>=C2=A0in preparation for Last Call by Dallas. This -00 d=
ocument is the result of a document reorg and generalization of functionali=
ty from HNCP. There is at least one open source implementation available.=
=C2=A0</div><div><br></div><div>4. We would like to call for reivew of=C2=
=A0<a href=3D"https://tools.ietf.org/wg/homenet/draft-ietf-homenet-naming-a=
rchitecture-dhc-options/" style=3D"color:rgb(68,0,136);border-bottom-width:=
0px;font-family:&#39;Times New Roman&#39;,times,serif;font-size:14.66666698=
45581px">draft-ietf-homenet-naming-architecture-dhc-options</a>=C2=A0and=C2=
=A0<a href=3D"https://tools.ietf.org/wg/homenet/draft-ietf-homenet-front-en=
d-naming-delegation/" style=3D"color:rgb(68,0,136);border-bottom-width:0px;=
font-family:&#39;Times New Roman&#39;,times,serif;font-size:14.666666984558=
1px">draft-ietf-homenet-front-end-naming-delegation</a>=C2=A0in preparation=
 for Last Call by Dallas. These documents have been presented numerous time=
s, with comments integrated.</div><div><br></div><div>5.=C2=A0<a href=3D"ht=
tps://tools.ietf.org/wg/homenet/draft-ietf-homenet-hncp/" style=3D"color:rg=
b(68,0,136);border-bottom-width:0px;font-family:&#39;Times New Roman&#39;,t=
imes,serif;font-size:14.6666669845581px">draft-ietf-homenet-hncp</a>=C2=A0s=
hould contain solely the Homenet-specific application of DNCP and PA, as we=
ll as discussion on routing. This document will remain open until the &quot=
;Routing Protocol&quot; question is resolved, which will be the main focus =
of Dallas (alongside any review comments from the above 4 actions). To assi=
st in that discussion, Margaret has been working with ISIS and babel expert=
s to pull together a document which you may have seen posted as a -00 a few=
 days ago if you were watching very carefully. Unfortunately, this -00 was =
a bit premature, and the authors have promised a -01 very soon. Please note=
 that this document is not a representation of consensus among the authors,=
 and is not the out put of a design team, but simply a collection of facts,=
 observations, and points of view by the authors in order to facilitate dis=
cussion. Expect an email to the list once the -01 document has been publish=
ed by Margaret (within days if not hours).</div><div><br></div><div>Finally=
, please get ready for a lively discussion on list and in Dallas. Don&#39;t=
 hold back! And, If you want agenda time in Dallas, please make Ray and I a=
ware.</div><div><br></div><div>Thanks!</div><div><br></div><div>- Mark</div=
><div><br></div><div><br></div></div>

--001a11c341e050926c050efeb1a4--


From nobody Sun Feb 15 10:33:51 2015
Return-Path: <mark@townsley.net>
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 132011A6F01 for <homenet@ietfa.amsl.com>; Sun, 15 Feb 2015 10:33:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] 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 eLKsQFBug2zA for <homenet@ietfa.amsl.com>; Sun, 15 Feb 2015 10:33:48 -0800 (PST)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E38601A001A for <homenet@ietf.org>; Sun, 15 Feb 2015 10:33:47 -0800 (PST)
Received: by mail-lb0-f172.google.com with SMTP id p9so22777452lbv.3 for <homenet@ietf.org>; Sun, 15 Feb 2015 10:33:46 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=mKhYCI0z4nz8fgEN1/nyIj1LLp3b9ckIpHaPN545Cb0=; b=XmMkFL3UJP0hYe6WGPFqsBEMpFOLGhSnI8Aip7cEgzkWNAIF4n1PW4JFSyNLnu6Clg F4i0YxxN8NllNEpYJyiWBB7hPSYiXkxIbyPwa57KjO3/CR925tk4FU/4jmW3JHDqKB67 OeAdjki/0KGv31VeVuA/oYsM9rlX30cs/gE2v4a+Xawaj2fZQx0mxGtkZ0/bxdF6phs+ iKs11rpGee9dXb86Ow9KwIQZ2sxWFNZPSOo+qjOqVVNEgPsDsJzhUoWUe8LVYwIAkDwM ezLjxbpw15ewyEuZLx1SK5zqxKxJV6vzVAMzD3h94SwKf95/IlRbAoqxwIpW+9lQf7f+ nNRw==
X-Gm-Message-State: ALoCoQldY9d5VN51FCi98njPgLgiZOvrhWa/QSrQyg2V4ta76DsunK8vKkQlkihoqwLqdT2LsWlz
MIME-Version: 1.0
X-Received: by 10.152.245.38 with SMTP id xl6mr10288029lac.68.1424025226223; Sun, 15 Feb 2015 10:33:46 -0800 (PST)
Received: by 10.112.170.73 with HTTP; Sun, 15 Feb 2015 10:33:46 -0800 (PST)
Date: Sun, 15 Feb 2015 19:33:46 +0100
Message-ID: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com>
From: Mark Townsley <mark@townsley.net>
To: "homenet@ietf.org Group" <homenet@ietf.org>
Content-Type: multipart/alternative; boundary=001a113459f6c2ac0e050f24b560
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/jvS2IiX33QmAlJyotJHsn3xhrqg>
Subject: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sun, 15 Feb 2015 18:33:50 -0000

--001a113459f6c2ac0e050f24b560
Content-Type: text/plain; charset=UTF-8

Dear WG,

In Hawaii, Margaret offered to pull together a document providing a summary
of ISIS and Babel within the context of homenet. Working with Chris Hopps
and Juliusz Chroboczek, Margaret just posted
draft-mrw-homenet-rtg-comparison-01.txt. Many thanks to all 3 authors for
this input, I'm sure it will help the WG make a more informed decision.

While there was a great deal of discussion and collaboration amongst the
authors, this document does not represent the authors' consensus in its
current form. This document is not intended to make a final recommendation
one way or another at this time, rather it is a starting point for those
who want more information but do not want to dive into the entire
repertoire of documents (or code) for ISIS or Babel.

As such, I would like to invite everyone to use this as a starting point to
familiarize yourselves with these two options. State your questions,
comments, and opinions with at as much lively debate as we heard at the
microphone and in the hallways in Hawaii.

Thank you,

- Mark

--001a113459f6c2ac0e050f24b560
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><br></div><div>Dear WG,</div><br><div>In Hawaii, Marg=
aret offered to pull together a document providing a summary of ISIS and Ba=
bel within the context of homenet. Working with Chris Hopps and Juliusz=C2=
=A0<span style=3D"color:rgb(0,0,0);font-size:1em">Chroboczek, Margaret just=
 posted=C2=A0</span><font color=3D"#000000">draft-mrw-homenet-rtg-compariso=
n-01.txt.=C2=A0</font><span style=3D"color:rgb(0,0,0)">Many thanks to all 3=
 authors for this input, I&#39;m sure it will help the WG make a more infor=
med decision.=C2=A0</span></div><div><span style=3D"color:rgb(0,0,0)"><br><=
/span></div><div><span style=3D"color:rgb(0,0,0)">While there was a great d=
eal of discussion and collaboration amongst the authors, this document does=
 not represent the authors&#39; consensus in its current form. This documen=
t is not intended to make a final recommendation one way or another at this=
 time, rather it is a starting point for those who want more information bu=
t do not want to dive into the entire repertoire of documents (or code) for=
 ISIS or Babel.</span></div><div><span style=3D"color:rgb(0,0,0)"><br></spa=
n></div><div><span style=3D"color:rgb(0,0,0)">As such, I would like to invi=
te everyone to use this as a starting point to familiarize yourselves with =
these two options. State your questions, comments, and opinions with at as =
much lively debate as we heard at the microphone and in the hallways in Haw=
aii.=C2=A0</span></div><div><span style=3D"color:rgb(0,0,0)"><br></span></d=
iv><div><span style=3D"color:rgb(0,0,0)">Thank you,</span></div><div><span =
style=3D"color:rgb(0,0,0)"><br></span></div><div><span style=3D"color:rgb(0=
,0,0)">- Mark</span></div><div><font color=3D"#000000"><br></font></div><di=
v><br></div><div><span style=3D"color:rgb(0,0,0);font-size:1em">=C2=A0</spa=
n></div></div>

--001a113459f6c2ac0e050f24b560--


From nobody Sun Feb 15 10:37:55 2015
Return-Path: <mark@townsley.net>
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 9060E1A3B9F for <homenet@ietfa.amsl.com>; Sun, 15 Feb 2015 10:37:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] 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 Ausp0oBeGF2J for <homenet@ietfa.amsl.com>; Sun, 15 Feb 2015 10:37:49 -0800 (PST)
Received: from mail-la0-f48.google.com (mail-la0-f48.google.com [209.85.215.48]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 55C1A1A6EE9 for <homenet@ietf.org>; Sun, 15 Feb 2015 10:37:49 -0800 (PST)
Received: by labhz20 with SMTP id hz20so24606249lab.0 for <homenet@ietf.org>; Sun, 15 Feb 2015 10:37:47 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=eWvSNPZbFIUb1lYaJgaDK3kSeF4GXrQ1q2z1hZ7E+u4=; b=JPKMlXGvRyJjmEcYaq2h0xCG2tCPOBq93jz49L035ETCDIpUvjJAxx6G2HDBkYfQKk MS10g1eq7ww+yroP8JzfByM2IT5qHHQUb/TrDjIhJhuxUnttHWD7f+SQGI+Kh4sENZPm rxeFIDXEeBzzjRzeIzkWkBdF1nTZkOB+lnwmpx5FjlQ6a2EcKd4YGQ3XjSUZisU7wfgk XiApuA0ZT9NcTDEEHhWtgBvYoEbp01o7fYe0cYbBaRQpwrOU0lYSe25Kgb29kASpp/W/ 6wro6Uw8mrC0hix3LgGJBzhtOwRP7AqAARv/RCrc//thLxpZrrm7svh2TTQBcw+rcNAe RiMQ==
X-Gm-Message-State: ALoCoQmL7uzla8RVM4vCFo3I9fgSMcZD7sPvpkwYyPV7SZIROfc21XWxufECJMEzWxpnGyeNnzyR
MIME-Version: 1.0
X-Received: by 10.152.5.6 with SMTP id o6mr18499242lao.59.1424025467720; Sun, 15 Feb 2015 10:37:47 -0800 (PST)
Received: by 10.112.170.73 with HTTP; Sun, 15 Feb 2015 10:37:47 -0800 (PST)
Date: Sun, 15 Feb 2015 19:37:47 +0100
Message-ID: <CAESTAVuvtfr9_25k-Z4LZ0Tu_HW+fm3doNLPz+W3Q9pF+ueMaw@mail.gmail.com>
From: Mark Townsley <mark@townsley.net>
To: "homenet@ietf.org Group" <homenet@ietf.org>
Content-Type: multipart/alternative; boundary=089e01419d1a27ac29050f24c4a9
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/GSw6BnCPuvKDMsG6E6dFTaueQSA>
Subject: [homenet] Where to find ISIS and babel users
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sun, 15 Feb 2015 18:37:51 -0000

--089e01419d1a27ac29050f24c4a9
Content-Type: text/plain; charset=UTF-8

Just FYI:

ISIS of course has a WG in the IETF, so most of you should know where to go
to find ISIS specific discussion.

Babel has an open mailing list, and has been made aware of Margaret's
draft. If you want to jump in and ask any questions there, of course feel
free:

   babel-users@lists.alioth.debian.org
   http://lists.alioth.debian.org/mailman/listinfo/babel-users
   nntp://news.gmane.org/gmane.network.routing.babel.user

--089e01419d1a27ac29050f24c4a9
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><br></div><div>Just FYI:</div><br><div>ISIS of course=
 has a WG in the IETF, so most of you should know where to go to find ISIS =
specific discussion.</div><div><br></div><div>Babel has an open mailing lis=
t, and has been made aware of Margaret&#39;s draft. If you want to jump in =
and ask any questions there, of course feel free:</div><div><br></div><div>=
<span style=3D"font-size:12.8000001907349px">=C2=A0 =C2=A0</span><a href=3D=
"mailto:babel-users@lists.alioth.debian.org" style=3D"font-size:12.80000019=
07349px">babel-users@lists.alioth.debian.org</a><br style=3D"font-size:12.8=
000001907349px"><span style=3D"font-size:12.8000001907349px">=C2=A0 =C2=A0<=
/span><a href=3D"http://lists.alioth.debian.org/mailman/listinfo/babel-user=
s" target=3D"_blank" style=3D"font-size:12.8000001907349px">http://lists.al=
ioth.debian.org/mailman/listinfo/babel-users</a><br></div><div><span style=
=3D"font-size:12.8000001907349px">=C2=A0 =C2=A0nntp://</span><a href=3D"htt=
p://news.gmane.org/gmane.network.routing.babel.user" target=3D"_blank" styl=
e=3D"font-size:12.8000001907349px">news.gmane.org/gmane.network.routing.bab=
el.user</a><br></div></div>

--089e01419d1a27ac29050f24c4a9--


From nobody Sun Feb 15 10:42:58 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 97D0B1A6EF3 for <homenet@ietfa.amsl.com>; Sun, 15 Feb 2015 10:42:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35] autolearn=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 BsMFQgJ5Vw2K for <homenet@ietfa.amsl.com>; Sun, 15 Feb 2015 10:42:51 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 56DBE1A001A for <homenet@ietf.org>; Sun, 15 Feb 2015 10:42:51 -0800 (PST)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t1FIgndt003266; Sun, 15 Feb 2015 19:42:49 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 825E82BF549; Sun, 15 Feb 2015 19:42:49 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id 9aIwZVtJJ39k; Sun, 15 Feb 2015 19:42:42 +0100 (CET)
Received: from pirx.pps.jussieu.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id AD2922BF548; Sun, 15 Feb 2015 19:42:42 +0100 (CET)
Date: Sun, 15 Feb 2015 19:42:41 +0100
Message-ID: <87bnkvrp7i.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Mark Townsley <mark@townsley.net>
In-Reply-To: <CAESTAVuvtfr9_25k-Z4LZ0Tu_HW+fm3doNLPz+W3Q9pF+ueMaw@mail.gmail.com>
References: <CAESTAVuvtfr9_25k-Z4LZ0Tu_HW+fm3doNLPz+W3Q9pF+ueMaw@mail.gmail.com>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Sun, 15 Feb 2015 19:42:49 +0100 (CET)
X-Miltered: at korolev with ID 54E0E8A9.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54E0E8A9.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54E0E8A9.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/9Yc1-KNTbWoefAYEHx-bHMzL1_4>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Where to find ISIS and babel users
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sun, 15 Feb 2015 18:42:53 -0000

> Babel has an open mailing list, and has been made aware of Margaret's draft.
> If you want to jump in and ask any questions there, of course feel free:
>
>    babel-users@lists.alioth.debian.org
>    http://lists.alioth.debian.org/mailman/listinfo/babel-users
>    nntp://news.gmane.org/gmane.network.routing.babel.user

The Babel web page has links to some of the Babel-related stuff I'm aware of:

  http://www.pps.univ-paris-diderot.fr/~jch/software/babel/

-- Juliusz



From nobody Sun Feb 15 11:21:37 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 28F2E1A0069 for <homenet@ietfa.amsl.com>; Sun, 15 Feb 2015 11:21:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.349
X-Spam-Level: 
X-Spam-Status: No, score=0.349 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HELO_EQ_FR=0.35] autolearn=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 qudHhz_PZycF for <homenet@ietfa.amsl.com>; Sun, 15 Feb 2015 11:21:34 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 790431A3B9F for <homenet@ietf.org>; Sun, 15 Feb 2015 11:21:34 -0800 (PST)
Received: from potemkin.univ-paris7.fr (potemkin.univ-paris7.fr [IPv6:2001:660:3301:8000::1:1]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t1FJLWIB014635 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 15 Feb 2015 20:21:32 +0100
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by potemkin.univ-paris7.fr (8.14.4/8.14.4/relay2/56228) with ESMTP id t1FJLWi0026910; Sun, 15 Feb 2015 20:21:32 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id AE3FB2BF548; Sun, 15 Feb 2015 20:21:32 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id wp0nhy20dyJ0; Sun, 15 Feb 2015 20:21:25 +0100 (CET)
Received: from pirx.pps.jussieu.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 8F01B2BF547; Sun, 15 Feb 2015 20:21:24 +0100 (CET)
Date: Sun, 15 Feb 2015 20:21:23 +0100
Message-ID: <877fvjrnf0.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Mark Townsley <mark@townsley.net>
In-Reply-To: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]); Sun, 15 Feb 2015 20:21:33 +0100 (CET)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Sun, 15 Feb 2015 20:21:32 +0100 (CET)
X-Miltered: at korolev with ID 54E0F1BC.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 54E0F1BC.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54E0F1BC.000 from potemkin.univ-paris7.fr/potemkin.univ-paris7.fr/null/potemkin.univ-paris7.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Enveloppe: 54E0F1BC.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54E0F1BC.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 54E0F1BC.000 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/ldBRef4rRJQqnnzwV1Xgd0ZHpxk>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sun, 15 Feb 2015 19:21:36 -0000

> Working with Chris Hopps and Juliusz Chroboczek, Margaret just posted
> draft-mrw-homenet-rtg-comparison-01.txt.

This is on

    https://tools.ietf.org/html/draft-mrw-homenet-rtg-comparison

As Mark mentioned, we didn't attempt to reach consensus with this
document -- we tried to produce something that's reasonably informative as
quickly as possible.

Here's my initial list of things that we might consider tweaking for -02:

1. The table in Section 13.3 compares the available implementation of
   Source-Specific Babel with the available implementation of
   Source-Specific IS-IS, which is written in Erlang and requires massive
   resources.  We should add a column with the sizes of Quagga's C version
   of IS-IS -- while this version is incomplete and not source-specific,
   this should give a rough idea of how much we can expect to be able to
   scale down IS-IS.

   (This is a little more work than you might expect, since it requires
   isolating just the isisd, zebra and libzebra bits of Quagga.  I hope
   Steven volunteers ;-) )

2. We didn't discuss the fact that Babel runs over UDP, while IS-IS runs
   directly over layer 2.  This has a number of consequences, most notably
   related to ease of implementation, portability, and the ability to run
   over tunnels (say, GRE or OpenVPN in tun mode).  I refer you to my
   previous posting to this list:

     http://mid.gmane.org/87iookwzgj.wl%25jch@pps.univ-paris-diderot.fr

3. Section 3.3 makes some rather strong claims about IS-IS scalability.
   Since we later argue in favour of a single-area implementation of
   IS-IS, I feel that these claims require some justification.  However,
   since I'm not convinced that scalability beyond 200 nodes or so is an
   important issue for Homenet, I won't try to push this particular point.

-- Juliusz


From nobody Sun Feb 15 12:03:20 2015
Return-Path: <cyrus@openwrt.org>
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 0B0BE1A6F2B for <homenet@ietfa.amsl.com>; Sun, 15 Feb 2015 12:03:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.85
X-Spam-Level: 
X-Spam-Status: No, score=-0.85 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-0.7] 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 Y-FrD5c3Vjce for <homenet@ietfa.amsl.com>; Sun, 15 Feb 2015 12:03:12 -0800 (PST)
Received: from mail.core-networks.de (mail.core-networks.de [82.96.72.7]) by ietfa.amsl.com (Postfix) with ESMTP id 6D91F1A6F34 for <homenet@ietf.org>; Sun, 15 Feb 2015 12:02:51 -0800 (PST)
Received: from localhost ([127.0.0.1]) by mail.core-networks.de id 1YN5Ou-0002h0-Nw with ESMTPSA (TLSv1.2:DHE-RSA-AES128-SHA:128) for ; Sun, 15 Feb 2015 21:02:44 +0100
Message-ID: <54E0FB64.8010009@openwrt.org>
Date: Sun, 15 Feb 2015 21:02:44 +0100
From: Steven Barth <cyrus@openwrt.org>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: "homenet@ietf.org Group" <homenet@ietf.org>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com>
In-Reply-To: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/bPWdF6eTaHxHCHZioZvHrTihuII>
Cc: draft-mrw-homenet-rtg-comparison@tools.ietf.org
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sun, 15 Feb 2015 20:03:16 -0000

Thanks for writing up the document.


As a general comment:
I think it should be added that there is a huge difference in building 
enterprise routers and home routers in terms of budgets for development 
/ support and margins.
This should somehow reflect in the complexity of the specifications and 
reference software we choose or produce in this WG.


A few more specific ones.

wrt. Link State Algorithm
"This information can be used by other applications outside the routing 
protocol itself. Additionally the flooding algorithm has been found as 
an efficient method for other applications to distribute node-specific 
application data, although some care must be taken with this use so as 
not to disrupt the fundamental routing function."

Is this relevant for the homenet case, since this additional information 
(Prefix Assignment, Naming, Security, etc.) is exchanged using HNCP already?


wrt. Algorithm Comparison
"Loop-Avoiding Distance Vector [...] scales badly in extremely dense 
deployments, where a single node has thousands of direct neighbours"

Are thousands of direct neighbors relevant for the homenet usecase?
In general if we are talking about 100-200 routers here we've built OLSR 
and BATMAN mesh networks in that range with WRT54GLs and similar devices 
back then.


wrt. Link Metrics
Do the protocols assign any metrics by default (e.g. based on link speed 
/ delay / reliability)? For Babel it is mentioned that it does so for 
WiFi however is there a generic case? Does IS-IS do something similar?
I mean in the end what good does a 16-bit or 24-bit metric space do us 
in a more or less unmanged environment if all hops "cost" the same by 
default unless otherwise configured?


wrt. Security Features
"We should just state whether each protocol supports auth or encryption, 
and whether it supports symmetric or something more exciting."

I agree. To my knowledge it seemed that none of the protocols supported 
encryption or asymmetric authentication. While we can manage PSKs in 
HNCP to solve the authentication issue we might want to mention the 
potential insight that someone might gain from sniffing the unencrypted 
traffic of either routing protocol.


wrt. IS-IS
"all major router vendors implement IS-IS" "As all major routing vendors 
have (proprietary) IS-IS implementations"

Is this really true for home router vendors? I don't doubt it is for 
enterprise routers but really the only routing protocol I've seen in 
home router firmwares so far is RIP and even that only in very few 
cases. Somewhat related: is source-specific routing in general deployed 
anywhere in the enterprise (or similar) space already?


Cheers,

Steven


From nobody Sun Feb 15 13:00:42 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 0DFBF1A01BA for <homenet@ietfa.amsl.com>; Sun, 15 Feb 2015 13:00:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.349
X-Spam-Level: 
X-Spam-Status: No, score=0.349 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, HELO_EQ_FR=0.35] autolearn=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 vRHNakWwceLa for <homenet@ietfa.amsl.com>; Sun, 15 Feb 2015 13:00:39 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 4B6A61A0154 for <homenet@ietf.org>; Sun, 15 Feb 2015 13:00:39 -0800 (PST)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t1FL0b3d011723; Sun, 15 Feb 2015 22:00:37 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id B86B52BF558; Sun, 15 Feb 2015 22:00:37 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id u8IoxQ8GSkiV; Sun, 15 Feb 2015 22:00:31 +0100 (CET)
Received: from pirx.pps.jussieu.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 24AB12BF556; Sun, 15 Feb 2015 22:00:31 +0100 (CET)
Date: Sun, 15 Feb 2015 22:00:30 +0100
Message-ID: <87k2ziritt.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Steven Barth <cyrus@openwrt.org>
In-Reply-To: <54E0FB64.8010009@openwrt.org>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E0FB64.8010009@openwrt.org>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Sun, 15 Feb 2015 22:00:37 +0100 (CET)
X-Miltered: at korolev with ID 54E108F5.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54E108F5.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54E108F5.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/hqBCfLdItX--1jajRDHWYtVq2YU>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sun, 15 Feb 2015 21:00:41 -0000

> wrt. Algorithm Comparison
> "Loop-Avoiding Distance Vector [...] scales badly in extremely dense
> deployments, where a single node has thousands of direct neighbours"

> Are thousands of direct neighbors relevant for the homenet usecase?

It's not relevant to any reasonable use case.  There is no widely
deplyed, cheap link technology that can support that many neighbours.

More generally, I think -01 puts undue stress on scaling and convergence
speed.  Sections 3 and 4 can be summarised as "any reasonable routing
protocol scales sufficiently well and converges sufficiently fast for the
needs of Homenet".

-- Juliusz


From nobody Sun Feb 15 13:04:33 2015
Return-Path: <margaretw42@gmail.com>
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 B02FC1A6EFE for <homenet@ietfa.amsl.com>; Sun, 15 Feb 2015 13:04:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level: 
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=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 0aXP3QH3efa7 for <homenet@ietfa.amsl.com>; Sun, 15 Feb 2015 13:04:30 -0800 (PST)
Received: from mail-pa0-x22f.google.com (mail-pa0-x22f.google.com [IPv6:2607:f8b0:400e:c03::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6BFD71A0154 for <homenet@ietf.org>; Sun, 15 Feb 2015 13:04:30 -0800 (PST)
Received: by mail-pa0-f47.google.com with SMTP id lf10so30701064pab.6 for <homenet@ietf.org>; Sun, 15 Feb 2015 13:04:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=QaqaTtddP1QgqoA0rcRkPZ7NcHXtbTOOWASfRDSwGnI=; b=wNDv05GPX0upELm7Jzzcwg5/lj49tDCBsQzdu6RDgS5v1a4FeFvYE+15q1xbDVdFZV tmKawYBkXdVYvZpVWEuR3uV/Ig4+OXUmNrlwj3sr03qIl70GTeiKtcx60wNX9Ermk4/W PiQih26+jVcBebmTSnuBXmcmKiSsOQz/MFadsgTsFCMOo6Kdc2pGvxFoIG46Rx8o/IJb n5lnt7uSlcOXbz3b0G1XtSuVSiOgXVs5brxC3Zn4fjm03gCEgBWM9ykKPuA2a6Z+7Xc2 HGamkIxFUqhIwheRy4HdsJPgAB8s03QrONHXJQ1hZxh0bhZ+19mCjEjGaXGYGrogrbSP Bs+Q==
X-Received: by 10.70.138.35 with SMTP id qn3mr14051336pdb.47.1424034268741; Sun, 15 Feb 2015 13:04:28 -0800 (PST)
Received: from [192.168.7.248] (wsip-24-248-179-54.ph.ph.cox.net. [24.248.179.54]) by mx.google.com with ESMTPSA id vo8sm657355pab.22.2015.02.15.13.04.27 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 15 Feb 2015 13:04:28 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Margaret Wasserman <margaretw42@gmail.com>
In-Reply-To: <87k2ziritt.wl-jch@pps.univ-paris-diderot.fr>
Date: Sun, 15 Feb 2015 16:04:27 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <D80DC12D-AFBA-45D1-9D19-E4D4B24961FA@gmail.com>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E0FB64.8010009@openwrt.org> <87k2ziritt.wl-jch@pps.univ-paris-diderot.fr>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
X-Mailer: Apple Mail (2.1510)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/Zgny2189HefC1kOHY2Dup99XFJE>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sun, 15 Feb 2015 21:04:32 -0000

On Feb 15, 2015, at 4:00 PM, Juliusz Chroboczek =
<jch@pps.univ-paris-diderot.fr> wrote:
> More generally, I think -01 puts undue stress on scaling and =
convergence
> speed.  Sections 3 and 4 can be summarised as "any reasonable routing
> protocol scales sufficiently well and converges sufficiently fast for =
the
> needs of Homenet".

The sections in the document started from a list of routing =
features/properties that were discussed in the WG meeting.  There was =
quite a bit of discussion of scaling.  In particular, there was a lot of =
discussion of how these protocols will scale "on Wi-Fi".  I wasn't =
entirely sure, during the meeting, what special requirements there are =
for a routing protocol to scale well on Wi-Fi vs. other link types, but =
perhaps someone on the WG mailing list can clarify?

Margaret



From nobody Sun Feb 15 13:10:49 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 F1DC51A001B for <homenet@ietfa.amsl.com>; Sun, 15 Feb 2015 13:10:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.349
X-Spam-Level: 
X-Spam-Status: No, score=0.349 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, HELO_EQ_FR=0.35] autolearn=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 ZIrV4VbzvWPr for <homenet@ietfa.amsl.com>; Sun, 15 Feb 2015 13:10:36 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 39DD41A6EFE for <homenet@ietf.org>; Sun, 15 Feb 2015 13:10:34 -0800 (PST)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t1FLAWCp014549; Sun, 15 Feb 2015 22:10:32 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 3AE2D2BF55A; Sun, 15 Feb 2015 22:10:32 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id 7Y2ar3TIPnCb; Sun, 15 Feb 2015 22:10:25 +0100 (CET)
Received: from pirx.pps.jussieu.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id C46A92BF558; Sun, 15 Feb 2015 22:10:25 +0100 (CET)
Date: Sun, 15 Feb 2015 22:10:24 +0100
Message-ID: <87d25aridb.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Margaret Wasserman <margaretw42@gmail.com>
In-Reply-To: <D80DC12D-AFBA-45D1-9D19-E4D4B24961FA@gmail.com>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E0FB64.8010009@openwrt.org> <87k2ziritt.wl-jch@pps.univ-paris-diderot.fr> <D80DC12D-AFBA-45D1-9D19-E4D4B24961FA@gmail.com>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Sun, 15 Feb 2015 22:10:32 +0100 (CET)
X-Miltered: at korolev with ID 54E10B48.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54E10B48.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54E10B48.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/mvdbCDJ05hRZFvR7QB3azdnaxTg>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sun, 15 Feb 2015 21:10:48 -0000

> The sections in the document started from a list of routing
> features/properties that were discussed in the WG meeting.  There was
> quite a bit of discussion of scaling.  In particular, there was a lot of
> discussion of how these protocols will scale "on Wi-Fi".

Performance and scaling on WiFi is discussed in Section 13.  That's
a different issue from the algorithmic scaling discussed in Section 3.

-- Juliusz



From nobody Mon Feb 16 01:16:25 2015
Return-Path: <markus.stenberg@iki.fi>
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 4DFBF1A1A74 for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 01:16:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.778
X-Spam-Level: 
X-Spam-Status: No, score=0.778 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_NEUTRAL=0.779] autolearn=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 EDrJWog6ZtL0 for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 01:16:22 -0800 (PST)
Received: from kirsi2.inet.fi (mta-out1.inet.fi [62.71.2.227]) by ietfa.amsl.com (Postfix) with ESMTP id B31FB1A00D4 for <homenet@ietf.org>; Mon, 16 Feb 2015 01:16:20 -0800 (PST)
Received: from poro.lan (80.220.64.126) by kirsi2.inet.fi (8.5.142.08) (authenticated as stenma-47) id 54C8EEAE003450F2; Mon, 16 Feb 2015 11:16:18 +0200
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Markus Stenberg <markus.stenberg@iki.fi>
In-Reply-To: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com>
Date: Mon, 16 Feb 2015 11:16:17 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <8041EA49-EB50-491B-A3C4-B25FAB52C8FC@iki.fi>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com>
To: Mark Townsley <mark@townsley.net>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/FC6NL-Qkef2vg5rB68XS68YkQb0>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Markus Stenberg <markus.stenberg@iki.fi>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 16 Feb 2015 09:16:24 -0000

On 15.2.2015, at 20.33, Mark Townsley <mark@townsley.net> wrote:
> In Hawaii, Margaret offered to pull together a document providing a =
summary of ISIS and Babel within the context of homenet. Working with =
Chris Hopps and Juliusz Chroboczek, Margaret just posted =
draft-mrw-homenet-rtg-comparison-01.txt. Many thanks to all 3 authors =
for this input, I=E2=80=99m sure it will help the WG make a more =
informed decision.=20

Finally. Thanks to the authors :)

Section 3.3:=20

As link state algorithms distribute all state, their (computation, state =
synchronization) cost is essentially a function of network size and =
network churn.=20

Quote:
   Link state algorithms scales to very large, very dense networks.

I would like to add, =E2=80=99static=E2=80=99 there, because given =
dynamic network, it will not simply work, at least not in One Huge =
Area(tm) mode we seem to currently envision for the homenet.=20

I am also not sure what this logical LSP stuff really tells us here, nor =
why is it relevant. (Low-level protocol detail.)

Section 4:

Convergence of any real routing protocol is =E2=80=98fast enough=E2=80=99.=
=20

I find it amusing that it is even discussed, as the main problem is =
hardware support of detecting link loss in the very heterogenous =
environment that is the home network.. Think dumb switches, wireless, =
weird L2s without carrier sense; hell, most _Linux home routers_ do not =
do good carrier sense on their physical LAN ports.

If you assume the need for L3+ keep-alive, convergence is a rounding =
error, unless you are very wasteful with the keep-alives.

Section 6.1:

We assume a =E2=80=98cleartext password=E2=80=99 for IS-IS in a home? =
What does this mean?

Section 7.1:

Woah, 24 bits of link metric? Show me the metric, baby! (And as noted by =
Steven, the extra stuff for prefixes is just not needed assuming HNCP.)

Anyway, I would like to hear in Section 7 in general what the metrics =
are used for, and how they are computed, in a zero-configuration home =
network. I hope the answer is not =E2=80=98operator can configure =
wireless to be not preferred over wired=E2=80=99.

Section 10.1:

Is someone actually using IS-IS multicast? Even outside homenet case? =
Considering there is only one homenet-y IS-IS implementation currently, =
I assume =E2=80=98available implementations=E2=80=99 here refers to all =
IS-IS implementations?=20

Section 11:

Source-specific routing IS required thanks to BCP-38, we do not want to =
(auto-)tunnel in the home due to crippled routing protocol choice. Is =
the HOMENET IS-IS production-quality? E.g. is someone using it in =
production?=20

Section 13.1:

How much churn is there in those =E2=80=98hundreds of nodes=E2=80=99 =
deployments, and do they run on $20 hardware per node?

Section 15.1/2:

Marketing, please make it stop.. (I could poke fun at some of the claims =
but I choose not to.)

Section 15.2.{1,2}:

(Speaking only for myself based on marginal knowledge of what is inside =
$CHEAP and $NOT-SO-CHEAP routers)=20

The major hurdle for any existing vendor is NOT the routing protocol, =
but the support for source specific routing. For those using Linux, it =
is relatively cheap =3D> adding support for RP with it is not bad. If =
using old Linux, or something crippled, it may be horrendously expensive =
if it involves e.g. drastic changes to how RIB, FIB, or both of them =
work (FIB may also bey on ASIC and relatively limited in terms of what =
you can change before it starts costing $$$).

Section {15.3.*, 15.8.1}

What do =E2=80=9Coperational=E2=80=9D networks and my home network have =
in common? I am not sure.

Section 15.5.1:

I would like to see the significantly pared version of IS-IS, with an =
implementation, before making any claims. Devil IS in the details =
sometimes.

To summarize my thinking based on reading the draft:

On high level, looking at the routing protocols=E2=80=99 =
_implementations_ I could pick up and use right now, so far, I see only =
one =E2=80=98big=E2=80=99 IS-IS implementation with zero users that I =
know of, and Babel that is used by some hobbyists and has small =
footprint.

We can make academic choice of IS-IS and hope that a small, robust =
open-source implementation comes up some day (and works without =
=E2=80=98operator=E2=80=99 twiddling metrics etc); or we can make =
practical choice and ship stuff this year.

Cheers,

-Markus


From nobody Mon Feb 16 01:26:28 2015
Return-Path: <gert@Space.Net>
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 2FEE21A878B for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 01:26:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 4aJWBnrzQaKg for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 01:26:25 -0800 (PST)
Received: from mobil.space.net (mobil.space.net [IPv6:2001:608:2:81::67]) (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 8D9D81A8787 for <homenet@ietf.org>; Mon, 16 Feb 2015 01:26:20 -0800 (PST)
X-Original-To: homenet@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id BA3A16035E for <homenet@ietf.org>; Mon, 16 Feb 2015 10:26:18 +0100 (CET)
X-SpaceNet-Relay: true
Received: from moebius3.space.net (moebius3.Space.Net [IPv6:2001:608:2:2::250]) by mobil.space.net (Postfix) with ESMTPS id 725F0600AC for <homenet@ietf.org>; Mon, 16 Feb 2015 10:26:18 +0100 (CET)
Received: (qmail 17899 invoked by uid 1007); 16 Feb 2015 10:26:18 +0100
Date: Mon, 16 Feb 2015 10:26:18 +0100
From: Gert Doering <gert@space.net>
To: Steven Barth <cyrus@openwrt.org>
Message-ID: <20150216092618.GQ34798@Space.Net>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E0FB64.8010009@openwrt.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <54E0FB64.8010009@openwrt.org>
X-NCC-RegID: de.space
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/flJQPFnqJGkDF31_BKkhqOhA0ns>
Cc: draft-mrw-homenet-rtg-comparison@tools.ietf.org, "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 16 Feb 2015 09:26:27 -0000

Hi,

On Sun, Feb 15, 2015 at 09:02:44PM +0100, Steven Barth wrote:
> Somewhat related: is source-specific routing in general deployed 
> anywhere in the enterprise (or similar) space already?

Not in the way homenet/babels tackle this.

Enterprise/ISP space does VRF and per-VRF routing tables, and all that,
or policy based routing with manual configuration.  But not "we have a
single routing protocol that transports (src,dest) routing info" - at
least I've never seen anything in $C or $J land.

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444           USt-IdNr.: DE813185279


From nobody Mon Feb 16 02:11:02 2015
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 F1CF21A883D for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 02:10:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.039
X-Spam-Level: *
X-Spam-Status: No, score=1.039 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_SE=0.35, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 9-u8rBDmPsXs for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 02:10:56 -0800 (PST)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 39FB71A8848 for <homenet@ietf.org>; Mon, 16 Feb 2015 02:10:31 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 0F0DAA2; Mon, 16 Feb 2015 11:10:29 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1424081429; bh=ozgCeHElqF3w5iZfUr93jwAtr/E+4asrGtyWBCDrFsc=; h=Date:From:To:Subject:In-Reply-To:References:From; b=QqjdTKoPqXXC5fmRAeoESTw+LCT4yl9k5AbLG32R055/Of4F9B/kikCMCN0U3UoTC 6uVnNnktpfEte9ALmZot3qf72pb8HotUx3RSbQR49JZO+vkntJ2K4HChwfcTGU3Bli SgbNJF/HDMGtwCFaYW0L+QFYI+I/chQaFI+yScmU=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 0B5069F for <homenet@ietf.org>; Mon, 16 Feb 2015 11:10:29 +0100 (CET)
Date: Mon, 16 Feb 2015 11:10:29 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: "homenet@ietf.org Group" <homenet@ietf.org>
In-Reply-To: <8041EA49-EB50-491B-A3C4-B25FAB52C8FC@iki.fi>
Message-ID: <alpine.DEB.2.02.1502161024030.4007@uplift.swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <8041EA49-EB50-491B-A3C4-B25FAB52C8FC@iki.fi>
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/DlGjsdCIPPwQE7xFbgiCWzzNJxM>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 16 Feb 2015 10:10:58 -0000

On Mon, 16 Feb 2015, Markus Stenberg wrote:

> The major hurdle for any existing vendor is NOT the routing protocol, 
> but the support for source specific routing. For those using Linux, it 
> is relatively cheap => adding support for RP with it is not bad. If 
> using old Linux, or something crippled, it may be horrendously expensive 
> if it involves e.g. drastic changes to how RIB, FIB, or both of them 
> work (FIB may also bey on ASIC and relatively limited in terms of what 
> you can change before it starts costing $$$).

With current routers out there, they either do forwarding based on pure 
CPU (this would be the ones that can handle up to around 100-200 
megabit/s), or they use packet forwarding hardware acceleration to achieve 
gig speeds.

The first class is "relatively cheap" to create src/dst extensions for, 
especially since if they target OpenWRT that seems to have 3.10 as its 
kernel (and I've seen this kernel pop up in more places).

The second class with hardware acceleration is more complicated, the 
changes they've done to the Linux kernel (often 3.2) is extensive, and 
creating newer kernels is harder.

However, it's my firm belief that when homenet is going to become more 
prevalent (a few years down the line), we're going to have SoCs that do 
gig speed in pure CPU where flash/ram/cpu resources are going to be big by 
todays standards.

On the protocol implementation part, let's not forget that ISIS was 
running on 68k processors in the 90-ties. This on routers that did CPU 
based forwarding at the same time. The current Auto-ISIS implementation 
requires an Erlang environment. This is what uses most of the resources, 
not the Auto-ISIS code itself. If you need more Erlang based software on 
the same box, then the Erlang environment is shared.

If ISIS is chosen, I am sure we'll see additional implementations of this 
in C or similar programming language. I know some rudimentary 
implementations in Python as well, that people wrote in very little time.

More to the point, the L2 way ISIS works seems to not be a significant 
problem.

There are numerous factors that would influence our choice, but one I 
would like to put to rest anyway, both protocols scale CPU-wise to the 
homenet use-case of number of nodes and expected topology we're going to 
see.


From nobody Mon Feb 16 02:35:57 2015
Return-Path: <markus.stenberg@iki.fi>
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 57C4B1A8774 for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 02:35:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.279
X-Spam-Level: 
X-Spam-Status: No, score=0.279 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RCVD_IN_DNSWL_NONE=-0.0001, SPF_NEUTRAL=0.779] autolearn=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 C0RsCUKDtJMX for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 02:35:50 -0800 (PST)
Received: from kirsi2.inet.fi (mta-out1.inet.fi [62.71.2.227]) by ietfa.amsl.com (Postfix) with ESMTP id 49FA31A0158 for <homenet@ietf.org>; Mon, 16 Feb 2015 02:35:50 -0800 (PST)
Received: from poro.lan (80.220.64.126) by kirsi2.inet.fi (8.5.142.08) (authenticated as stenma-47) id 54C8EEAE00349BA8; Mon, 16 Feb 2015 12:35:47 +0200
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Markus Stenberg <markus.stenberg@iki.fi>
In-Reply-To: <alpine.DEB.2.02.1502161024030.4007@uplift.swm.pp.se>
Date: Mon, 16 Feb 2015 12:35:47 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <8111DC7E-05BD-4EC2-91F1-44E7D6E31695@iki.fi>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <8041EA49-EB50-491B-A3C4-B25FAB52C8FC@iki.fi> <alpine.DEB.2.02.1502161024030.4007@uplift.swm.pp.se>
To: Mikael Abrahamsson <swmike@swm.pp.se>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/9lP25BZ9737TPRBikIikzSb1xxQ>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Markus Stenberg <markus.stenberg@iki.fi>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 16 Feb 2015 10:35:53 -0000

On 16.2.2015, at 12.10, Mikael Abrahamsson <swmike@swm.pp.se> wrote:
>> The major hurdle for any existing vendor is NOT the routing protocol, =
but the support for source specific routing. For those using Linux, it =
is relatively cheap =3D> adding support for RP with it is not bad. If =
using old Linux, or something crippled, it may be horrendously expensive =
if it involves e.g. drastic changes to how RIB, FIB, or both of them =
work (FIB may also bey on ASIC and relatively limited in terms of what =
you can change before it starts costing $$$).
> With current routers out there, they either do forwarding based on =
pure CPU (this would be the ones that can handle up to around 100-200 =
megabit/s), or they use packet forwarding hardware acceleration to =
achieve gig speeds.
>=20
> The first class is =E2=80=9Crelatively cheap" to create src/dst =
extensions for, especially since if they target OpenWRT that seems to =
have 3.10 as its kernel (and I've seen this kernel pop up in more =
places).

The extension is also backported even to 2.6.32 stable series =
(.6something), and also all other currently active stable trees. If a =
router vendor is using Linux but not basing on stable tree, it is their =
problem ;)

> The second class with hardware acceleration is more complicated, the =
changes they've done to the Linux kernel (often 3.2) is extensive, and =
creating newer kernels is harder.
>=20
> However, it=E2=80=99s my firm belief that when homenet is going to =
become more prevalent (a few years down the line), we're going to have =
SoCs that do gig speed in pure CPU where flash/ram/cpu resources are =
going to be big by todays standards.

The trend has been so far reverse; it used to be all-software, and now =
some hardware forwarding even in homes. Of course, adding e.g. routing =
to the mix might reverse the trend. Currently lan-lan port traffic is =
handled usually purely as L2 bridging on about _all_ hardware, but =
homenet-y router would require routing of the traffic in software or =
much more complex hardware FIB.

I am not sure ram/flash will grow automatically. Currently there is lots =
of stuff that ships with 4MB flash still (unlike the optimistic =
document), because the distro of the vendor=E2=80=99s choice fits into =
3.*MB with the set of features the vendor wants to support. As long as =
there is a market for those low-end chips (and no compelling reason to =
upgrade for the router vendors), the baseline numbers will not increase =
despite the Moore=E2=80=99s law. The savings will of course grow less =
and less, and eventually the economies of scale may force an upgrade, =
but I am not holding my breath with that.=20

For an amusing anecdote of 12 years of home router progress, look at =
https://en.wikipedia.org/wiki/Linksys_WRT54G_series .. both ram and =
flash have decreased. (TL;DR: 16->8, 4->2MB respectively)

> On the protocol implementation part, let's not forget that ISIS was =
running on 68k processors in the 90-ties. This on routers that did CPU =
based forwarding at the same time. The current Auto-ISIS implementation =
requires an Erlang environment. This is what uses most of the resources, =
not the Auto-ISIS code itself. If you need more Erlang based software on =
the same box, then the Erlang environment is shared.

I am not sure my home devices could afford the memory, but point taken. =
I guess we can toast to world domination of Erlang soon too ;)

> If ISIS is chosen, I am sure we'll see additional implementations of =
this in C or similar programming language. I know some rudimentary =
implementations in Python as well, that people wrote in very little =
time.

I have written fast hacks in $scripting-language-du-jour, but I am not =
convinced e.g. IS-IS implementation in C can be considered one. =
Considering the effort various parties have poured into the two OS IS-IS =
implementations that seem to be maintained nowadays, and OS IS-IS world =
domination is still waiting to happen, I am not perhaps as optimistic as =
you are.

> More to the point, the L2 way ISIS works seems to not be a significant =
problem.

Agreed. Most of the sections in the document are =E2=80=99not =
significant problem=E2=80=99.

> There are numerous factors that would influence our choice, but one I =
would like to put to rest anyway, both protocols scale CPU-wise to the =
homenet use-case of number of nodes and expected topology we=E2=80=99re =
going to see.

Do you care to enumerate the relevant factors from your point of view?

=46rom my point of view, they are more or less:

[1] does it work =E2=80=98well=E2=80=99 zeroconf + do source-specific =
routing (both are MUST)
[2] does it work in the topologies it will get thrown at.
[3] can I ship it this year if I feel like it, using OS code that fits =
on the devices
- also,  is it =E2=80=98economical enough=E2=80=99 in it=E2=80=99s use =
of computing/memory/bandwidth of the router=20

but I am very results oriented. [1] is addressed by both at least on =
paper. [2] I am not sure about (IS-IS metrics without operator =3D ? - =
all I know is the fancy 24 bits). [3] seems to favor Babel currently.

Cheers,

-Markus=


From nobody Mon Feb 16 02:50:33 2015
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 3BC791A87BE for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 02:50:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.461
X-Spam-Level: 
X-Spam-Status: No, score=-0.461 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, J_CHICKENPOX_31=0.6, J_CHICKENPOX_52=0.6, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 UkK93eyokyn7 for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 02:50:29 -0800 (PST)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 810301A8779 for <homenet@ietf.org>; Mon, 16 Feb 2015 02:50:25 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id E0C81A2; Mon, 16 Feb 2015 11:50:23 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1424083823; bh=SNjoL3ZT5u5nL6GrCBaCsG6Gu1WY8rdRstLpTKnhX5I=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=yR2ExliWIA7luqoAUo6yOcRLkFqb1Kr2RAgGws4DMGVZ1LcW0w/0692XSH1LdXFTP VciSqzO6V2JkvO0ADDd0LenYoFg2zAl5bpQFxRKik2+JIj1fZhtLHF8cFQ+rxZ7WSY ltGRp0M0fIbfeZe28BRwkHxn+fZb1Plcas4IKGdw=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id DCDCC9F; Mon, 16 Feb 2015 11:50:23 +0100 (CET)
Date: Mon, 16 Feb 2015 11:50:23 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Markus Stenberg <markus.stenberg@iki.fi>
In-Reply-To: <8111DC7E-05BD-4EC2-91F1-44E7D6E31695@iki.fi>
Message-ID: <alpine.DEB.2.02.1502161138050.4007@uplift.swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <8041EA49-EB50-491B-A3C4-B25FAB52C8FC@iki.fi> <alpine.DEB.2.02.1502161024030.4007@uplift.swm.pp.se> <8111DC7E-05BD-4EC2-91F1-44E7D6E31695@iki.fi>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="-137064504-2056730456-1424083823=:4007"
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/8jdKAwRc9M5DU0xWrg-qipa0JGI>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 16 Feb 2015 10:50:31 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

---137064504-2056730456-1424083823=:4007
Content-Type: TEXT/PLAIN; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8BIT

On Mon, 16 Feb 2015, Markus Stenberg wrote:

> The extension is also backported even to 2.6.32 stable series 
> (.6something), and also all other currently active stable trees. If a 
> router vendor is using Linux but not basing on stable tree, it is their 
> problem ;)

Well, considering the push-back I've been getting when asking for newer 
kernels, I'd say it's their problem, but also our problem.

> The trend has been so far reverse; it used to be all-software, and now 
> some hardware forwarding even in homes. Of course, adding e.g. routing 
> to the mix might reverse the trend. Currently lan-lan port traffic is 
> handled usually purely as L2 bridging on about _all_ hardware, but 
> homenet-y router would require routing of the traffic in software or 
> much more complex hardware FIB.

I didn't even count the L2 switch chip there, that's just for cheap 
connectivity. Homenet won't fit (at least initially) in cheap hardware at 
all. Just the fact that you need src/dst routing means most current 
mid/higher end hardware won't work at all (or will require significant 
microcode update to work).

> I am not sure ram/flash will grow automatically. Currently there is lots 
> of stuff that ships with 4MB flash still (unlike the optimistic 
> document), because the distro of the vendorâ€™s choice fits into 3.*MB 
> with the set of features the vendor wants to support. As long as there 
> is a market for those low-end chips (and no compelling reason to upgrade 
> for the router vendors), the baseline numbers will not increase despite 
> the Mooreâ€™s law. The savings will of course grow less and less, and 
> eventually the economies of scale may force an upgrade, but I am not 
> holding my breath with that.

In the race to the bottom, Homenet is unneccearily complicated and for 
those who want to save on the cent level for hardware, for them Homenet is 
completely useless. So for me, this point isn't valid. Looking forward, I 
believe the mobile SoC:s will start to show up in routers as well and this 
is where we'll be headed.

> For an amusing anecdote of 12 years of home router progress, look at 
> https://en.wikipedia.org/wiki/Linksys_WRT54G_series .. both ram and 
> flash have decreased. (TL;DR: 16->8, 4->2MB respectively)

Was WRT54G ever a device an ISP would have bought and deployed to their 
customers? Isn't it the 150USD enthusiast product of today?

> I am not sure my home devices could afford the memory, but point taken. 
> I guess we can toast to world domination of Erlang soon too ;)

Well, most non-compiled languages have the same behaviour. Do you need 
Python on your HGW? Just the pyton executable on my debian system is 2.7 
megabyte in size.

>> There are numerous factors that would influence our choice, but one I 
>> would like to put to rest anyway, both protocols scale CPU-wise to the 
>> homenet use-case of number of nodes and expected topology weâ€™re going 
>> to see.
>
> Do you care to enumerate the relevant factors from your point of view?

Both protocols seems to handle hundreds of links and hundreds of routers, 
which for me seems like overkill for a homenet.

> From my point of view, they are more or less:
>
> [1] does it work â€˜wellâ€™ zeroconf + do source-specific routing (both are MUST)
> [2] does it work in the topologies it will get thrown at.
> [3] can I ship it this year if I feel like it, using OS code that fits on the devices
> - also,  is it â€˜economical enoughâ€™ in itâ€™s use of computing/memory/bandwidth of the router
>
> but I am very results oriented. [1] is addressed by both at least on 
> paper. [2] I am not sure about (IS-IS metrics without operator = ? - all 
> I know is the fancy 24 bits). [3] seems to favor Babel currently.

ISIS metrics is a tool. If we don't want it, then we don't need it. We can 
just do a fixed metric, or interface speed metric, or interface type 
metric, or combination, or whatever we want.

I would not deploy homenet router in my home if it didn't at least 
mimic:ed my current setup, ie could do gigabit/s forwarding within my 
home. (this is what the L2 switch chip does currently). So for me, it's a 
moot point to be able to deploy immediately becase we have no hardware 
that makes sense to deploy on.

I am not aware of any device that fits your requirements, ie src/dst 
routing at gig speeds (well, that's my requirement, you didn't 
specifically write that), can run mainline Linux kernel, has small flash, 
small CPU, and not a lot of RAM.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se
---137064504-2056730456-1424083823=:4007--


From nobody Mon Feb 16 03:00:57 2015
Return-Path: <markus.stenberg@iki.fi>
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 91B991A1AB6 for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 03:00:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.879
X-Spam-Level: 
X-Spam-Status: No, score=0.879 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, J_CHICKENPOX_52=0.6, RCVD_IN_DNSWL_NONE=-0.0001, SPF_NEUTRAL=0.779] autolearn=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 mLtHjMAeltit for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 03:00:48 -0800 (PST)
Received: from jenni2.inet.fi (mta-out1.inet.fi [62.71.2.195]) by ietfa.amsl.com (Postfix) with ESMTP id 23C631A1AB3 for <homenet@ietf.org>; Mon, 16 Feb 2015 03:00:48 -0800 (PST)
Received: from poro.lan (80.220.64.126) by jenni2.inet.fi (8.5.142.08) (authenticated as stenma-47) id 54C8F2EA02888E8E; Mon, 16 Feb 2015 13:00:46 +0200
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Markus Stenberg <markus.stenberg@iki.fi>
In-Reply-To: <alpine.DEB.2.02.1502161138050.4007@uplift.swm.pp.se>
Date: Mon, 16 Feb 2015 13:00:46 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <9DB24798-DAC1-49A4-88DA-6A60B4A107BB@iki.fi>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <8041EA49-EB50-491B-A3C4-B25FAB52C8FC@iki.fi> <alpine.DEB.2.02.1502161024030.4007@uplift.swm.pp.se> <8111DC7E-05BD-4EC2-91F1-44E7D6E31695@iki.fi> <alpine.DEB.2.02.1502161138050.4007@uplift.swm.pp.se>
To: Mikael Abrahamsson <swmike@swm.pp.se>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/tv8SxY8qR0JJI9epGRXIgibCAvo>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Markus Stenberg <markus.stenberg@iki.fi>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 16 Feb 2015 11:00:54 -0000

On 16.2.2015, at 12.50, Mikael Abrahamsson <swmike@swm.pp.se> wrote:
>> For an amusing anecdote of 12 years of home router progress, look at =
https://en.wikipedia.org/wiki/Linksys_WRT54G_series .. both ram and =
flash have decreased. (TL;DR: 16->8, 4->2MB respectively)
> Was WRT54G ever a device an ISP would have bought and deployed to =
their customers? Isn=E2=80=99t it the 150USD enthusiast product of =
today?

Do you consider ISPs more or less cost conscious than the home users? =
And yes, I know some ISPs have deployed it at some point, and the non-GL =
was definitely non-enthusiast product at some point as it transitioned =
from Linux to VxWorks while chasing smaller footprint.

>> I am not sure my home devices could afford the memory, but point =
taken. I guess we can toast to world domination of Erlang soon too ;)
> Well, most non-compiled languages have the same behaviour. Do you need =
Python on your HGW? Just the pyton executable on my debian system is 2.7 =
megabyte in size.

OpenWrt can fit Lua UI equipped OS to 4MB of flash..

Sure, sticking a (full) JVM in a router might be bad idea. Jury is still =
out on Erlang.

>> =46rom my point of view, they are more or less:
>>=20
>> [1] does it work =E2=80=98well=E2=80=99 zeroconf + do source-specific =
routing (both are MUST)
>> [2] does it work in the topologies it will get thrown at.
>> [3] can I ship it this year if I feel like it, using OS code that =
fits on the devices
>> - also,  is it =E2=80=98economical enough=E2=80=99 in it=E2=80=99s =
use of computing/memory/bandwidth of the router
>>=20
>> but I am very results oriented. [1] is addressed by both at least on =
paper. [2] I am not sure about (IS-IS metrics without operator =3D ? - =
all I know is the fancy 24 bits). [3] seems to favor Babel currently.
> ISIS metrics is a tool. If we don't want it, then we don't need it. We =
can just do a fixed metric, or interface speed metric, or interface type =
metric, or combination, or whatever we want.

Right. But Babel does sensible things by default. So I am not sure =E2=80=99=
24 bits=E2=80=99 is really =E2=80=98pro=E2=80=99 IS-IS here. (And =
sensible things in this case are sufficiently dynamic that they do not =
work well in a link state routing protocol on scale, at least.)

> I would not deploy homenet router in my home if it didn't at least =
mimic:ed my current setup, ie could do gigabit/s forwarding within my =
home. (this is what the L2 switch chip does currently). So for me, it's =
a moot point to be able to deploy immediately becase we have no hardware =
that makes sense to deploy on.
> I am not aware of any device that fits your requirements, ie src/dst =
routing at gig speeds (well, that's my requirement, you didn't =
specifically write that), can run mainline Linux kernel, has small =
flash, small CPU, and not a lot of RAM.

As long as my ISP does not offer gigabit, I can L2 bridge the LANs =
still, and route (e.g. wlans, wan port) and get useful performance given =
current hardware. (Not quite gigabit, but as my upstream is 100mbit and =
real wireless is also sub-gigabit, it is enough.) I do have 2 upstream =
connections, and run homenet stuff on existing hardware.

The year most home connections are gigabit I guess this is no longer a =
valid choice, but I have some optimism about the hardware at that point =
too.

Cheers,

-Markus

P.S. Still waiting for your criteria list ;)


From nobody Mon Feb 16 04:31:29 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 99CFC1A1AE5 for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 04:31:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.15
X-Spam-Level: *
X-Spam-Status: No, score=1.15 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_EQ_FR=0.35] autolearn=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 2qzQkyKHPb38 for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 04:31:26 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 4BFD51A0087 for <homenet@ietf.org>; Mon, 16 Feb 2015 04:31:26 -0800 (PST)
Received: from potemkin.univ-paris7.fr (potemkin.univ-paris7.fr [IPv6:2001:660:3301:8000::1:1]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t1GCVOu7022923 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 16 Feb 2015 13:31:24 +0100
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by potemkin.univ-paris7.fr (8.14.4/8.14.4/relay2/56228) with ESMTP id t1GCVOwC019443; Mon, 16 Feb 2015 13:31:24 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 4CF862BF903; Mon, 16 Feb 2015 13:31:24 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id mi6UYSbACRQ8; Mon, 16 Feb 2015 13:31:22 +0100 (CET)
Received: from pirx.pps.jussieu.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 00A342BF8FD; Mon, 16 Feb 2015 13:31:19 +0100 (CET)
Date: Mon, 16 Feb 2015 13:31:19 +0100
Message-ID: <87vbj22g2w.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Mikael Abrahamsson <swmike@swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1502161138050.4007@uplift.swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <8041EA49-EB50-491B-A3C4-B25FAB52C8FC@iki.fi> <alpine.DEB.2.02.1502161024030.4007@uplift.swm.pp.se> <8111DC7E-05BD-4EC2-91F1-44E7D6E31695@iki.fi> <alpine.DEB.2.02.1502161138050.4007@uplift.swm.pp.se>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]); Mon, 16 Feb 2015 13:31:24 +0100 (CET)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Mon, 16 Feb 2015 13:31:24 +0100 (CET)
X-Miltered: at korolev with ID 54E1E31C.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 54E1E31C.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54E1E31C.001 from potemkin.univ-paris7.fr/potemkin.univ-paris7.fr/null/potemkin.univ-paris7.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Enveloppe: 54E1E31C.001 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54E1E31C.001 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 54E1E31C.001 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/vrGWr-iSHhb1ehCx3ATtSKQgHhw>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Markus Stenberg <markus.stenberg@iki.fi>
Subject: [homenet] Source-Specific routing on older kernels [was: Routing protocol...]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 16 Feb 2015 12:31:28 -0000

> Just the fact that you need src/dst routing means most current
> mid/higher end hardware won't work at all (or will require significant
> microcode update to work).

I'd like to point out that one of the conclusions of the work of Matthieu
is that source-specific routing can be easily implemented on any
hardware/kernel that supports policy routing -- see Section V.B of
http://arxiv.org/abs/1403.0445 .  This is implemented in Babel, of course.

(Sorry for the blatant self-promotion.  I couldn't resist.)

-- Juliusz


From nobody Mon Feb 16 04:44:39 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 7FD311A1ADA for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 04:44:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.15
X-Spam-Level: *
X-Spam-Status: No, score=1.15 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_EQ_FR=0.35] autolearn=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 Y1KlGLyR2AOZ for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 04:44:32 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 B9EEA1A1ADC for <homenet@ietf.org>; Mon, 16 Feb 2015 04:44:30 -0800 (PST)
Received: from potemkin.univ-paris7.fr (potemkin.univ-paris7.fr [IPv6:2001:660:3301:8000::1:1]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t1GCiTjJ030352 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 16 Feb 2015 13:44:29 +0100
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by potemkin.univ-paris7.fr (8.14.4/8.14.4/relay2/56228) with ESMTP id t1GCiTlr026641; Mon, 16 Feb 2015 13:44:29 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 475BC2BF907; Mon, 16 Feb 2015 13:44:29 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id NFY_RVy6uJ6d; Mon, 16 Feb 2015 13:44:27 +0100 (CET)
Received: from pirx.pps.jussieu.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id C33962BF904; Mon, 16 Feb 2015 13:44:27 +0100 (CET)
Date: Mon, 16 Feb 2015 13:44:27 +0100
Message-ID: <87twym2fh0.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Mikael Abrahamsson <swmike@swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1502161024030.4007@uplift.swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <8041EA49-EB50-491B-A3C4-B25FAB52C8FC@iki.fi> <alpine.DEB.2.02.1502161024030.4007@uplift.swm.pp.se>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]); Mon, 16 Feb 2015 13:44:29 +0100 (CET)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Mon, 16 Feb 2015 13:44:29 +0100 (CET)
X-Miltered: at korolev with ID 54E1E62D.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 54E1E62D.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54E1E62D.000 from potemkin.univ-paris7.fr/potemkin.univ-paris7.fr/null/potemkin.univ-paris7.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Enveloppe: 54E1E62D.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54E1E62D.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 54E1E62D.000 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/XVb5YjT_29BwCSdzVZzNiLyQHeY>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: [homenet] Implementations of IS-IS [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 16 Feb 2015 12:44:34 -0000

> If ISIS is chosen, I am sure we'll see additional implementations of this
> in C or similar programming language. I know some rudimentary
> implementations in Python as well, that people wrote in very little time.

The Python implementation I'm aware of is not just rudimentary, it's not
done (as in not even having an implementation of SPF).

If you know of any reasonably complete open source implementations of
IS-IS other than the Erlang implementation and the (alpha quality) Quagga
implementation, please let me know (perhaps by private mail), so I can
mention them in -02.

-- Juliusz


From nobody Mon Feb 16 04:46:20 2015
Return-Path: <eckert@cisco.com>
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 42B691A1ACE for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 04:46:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -13.911
X-Spam-Level: 
X-Spam-Status: No, score=-13.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_31=0.6, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 LCEGVzUCls-d for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 04:46:15 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 850B01A1AD0 for <homenet@ietf.org>; Mon, 16 Feb 2015 04:46:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6052; q=dns/txt; s=iport; t=1424090775; x=1425300375; h=from:to:cc:subject:date:message-id:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=bXWGXPeIY64G8/JAOgH0asCdnwY2yjyxyep9+CnE34Q=; b=XsilO3aD5T36ilkK5zYqtgr1sps43F32bFLW/n+XcpTg9a016AFruppv wT2srQnk0FXtSH5fNxnJM0CuLBn//VGPyq/obpPq2RJ1ESHsSUXHmTePC 7lZfJtwNc95d8U7kt8h2I+8Icr7QkXNv7pUx2XDaiiXsMiKXtSx1FxjP0 Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlMFAKTl4VStJV2a/2dsb2JhbABcgwZSWgTCOYVxAoEWQwEBAQEBAXyEDQEBBCdSEgEIDgpgJQIEAQ0FiC0NzDIBAQEBAQEBAQEBAQEBAQEBAQEBARQEiwyECxEBHTMHhCoFjziDV4VggRiLLoMJgz4iggIcgVBvgQs5fwEBAQ
X-IronPort-AV: E=Sophos;i="5.09,587,1418083200"; d="scan'208";a="393367794"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-9.cisco.com with ESMTP; 16 Feb 2015 12:46:14 +0000
Received: from xhc-aln-x15.cisco.com (xhc-aln-x15.cisco.com [173.36.12.89]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id t1GCkEEm005301 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 16 Feb 2015 12:46:14 GMT
Received: from xmb-rcd-x15.cisco.com ([169.254.5.72]) by xhc-aln-x15.cisco.com ([173.36.12.89]) with mapi id 14.03.0195.001; Mon, 16 Feb 2015 06:46:14 -0600
From: "Toerless Eckert (eckert)" <eckert@cisco.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>, Markus Stenberg <markus.stenberg@iki.fi>
Thread-Topic: [homenet] Routing protocol comparison document
Thread-Index: AQHQSU34U8YuILOLXEC65ZU2TP7SwJzzZGmAgAAPJICAAAcSgIAABBSAgAAWxwA=
Date: Mon, 16 Feb 2015 12:46:13 +0000
Message-ID: <D1078D96.6A553%eckert@cisco.com>
In-Reply-To: <alpine.DEB.2.02.1502161138050.4007@uplift.swm.pp.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.2.2.120421
x-originating-ip: [10.24.178.96]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <43ABAE8399BE7744A64BA406559619D3@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/DRg4iN2S8CtoxItVaPsJ-P8S_Js>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 16 Feb 2015 12:46:18 -0000

If you allow a clueless question here by someone who hasen't tracked the
details of this space too much:

If I am thinking longer term, I would like to see simple L2 switches in
the home be replaced with homenet switches. Or lets say at least I would
like to make sure that the homenet/OSS work makes it possible to go that
way.

What I don't know is how the PI (platform independent) / PD (platform
dependent) stack should look like to enable this. How useful is the
internal structure in linux for example such that the upper layers can
nicely act as PI enabling white box hardware to  build out easily a PD
layer that uses actual HW-acceleration ?

So far I am mostly aware of API sets like OpenFlow being used as a target
to talk to PD. But I don't think (famous last words ?) that OpenFlow can
be used as a PD below the PI linux kernel code, or can it ?

The other option people seem to like are a bunch of (probably IETF
developed) YANG models specifying sufficient data models to provide the
desired forwarding (I2RS comes to mind). But is there work to define that
for the (S/M,D/M) requirements of homenet and/or do folks think this is a
realistic path to use  for whitebox hardware / PD code ?

Thanks
   Toerless

On 2/16/15 11:50 AM, "Mikael Abrahamsson" <swmike@swm.pp.se> wrote:

>On Mon, 16 Feb 2015, Markus Stenberg wrote:
>
>> The extension is also backported even to 2.6.32 stable series
>> (.6something), and also all other currently active stable trees. If a
>> router vendor is using Linux but not basing on stable tree, it is their
>> problem ;)
>
>Well, considering the push-back I've been getting when asking for newer
>kernels, I'd say it's their problem, but also our problem.
>
>> The trend has been so far reverse; it used to be all-software, and now
>> some hardware forwarding even in homes. Of course, adding e.g. routing
>> to the mix might reverse the trend. Currently lan-lan port traffic is
>> handled usually purely as L2 bridging on about _all_ hardware, but
>> homenet-y router would require routing of the traffic in software or
>> much more complex hardware FIB.
>
>I didn't even count the L2 switch chip there, that's just for cheap
>connectivity. Homenet won't fit (at least initially) in cheap hardware at
>all. Just the fact that you need src/dst routing means most current
>mid/higher end hardware won't work at all (or will require significant
>microcode update to work).
>
>> I am not sure ram/flash will grow automatically. Currently there is
>>lots=20
>> of stuff that ships with 4MB flash still (unlike the optimistic
>> document), because the distro of the vendor=B9s choice fits into 3.*MB
>> with the set of features the vendor wants to support. As long as there
>> is a market for those low-end chips (and no compelling reason to
>>upgrade=20
>> for the router vendors), the baseline numbers will not increase despite
>> the Moore=B9s law. The savings will of course grow less and less, and
>> eventually the economies of scale may force an upgrade, but I am not
>> holding my breath with that.
>
>In the race to the bottom, Homenet is unneccearily complicated and for
>those who want to save on the cent level for hardware, for them Homenet
>is=20
>completely useless. So for me, this point isn't valid. Looking forward, I
>believe the mobile SoC:s will start to show up in routers as well and
>this=20
>is where we'll be headed.
>
>> For an amusing anecdote of 12 years of home router progress, look at
>> https://en.wikipedia.org/wiki/Linksys_WRT54G_series .. both ram and
>> flash have decreased. (TL;DR: 16->8, 4->2MB respectively)
>
>Was WRT54G ever a device an ISP would have bought and deployed to their
>customers? Isn't it the 150USD enthusiast product of today?
>
>> I am not sure my home devices could afford the memory, but point taken.
>> I guess we can toast to world domination of Erlang soon too ;)
>
>Well, most non-compiled languages have the same behaviour. Do you need
>Python on your HGW? Just the pyton executable on my debian system is 2.7
>megabyte in size.
>
>>> There are numerous factors that would influence our choice, but one I
>>> would like to put to rest anyway, both protocols scale CPU-wise to the
>>> homenet use-case of number of nodes and expected topology we=B9re going
>>> to see.
>>
>> Do you care to enumerate the relevant factors from your point of view?
>
>Both protocols seems to handle hundreds of links and hundreds of routers,
>which for me seems like overkill for a homenet.
>
>> From my point of view, they are more or less:
>>
>> [1] does it work =8Cwell=B9 zeroconf + do source-specific routing (both =
are
>>MUST)
>> [2] does it work in the topologies it will get thrown at.
>> [3] can I ship it this year if I feel like it, using OS code that fits
>>on the devices
>> - also,  is it =8Ceconomical enough=B9 in it=B9s use of
>>computing/memory/bandwidth of the router
>>
>> but I am very results oriented. [1] is addressed by both at least on
>> paper. [2] I am not sure about (IS-IS metrics without operator =3D ? -
>>all=20
>> I know is the fancy 24 bits). [3] seems to favor Babel currently.
>
>ISIS metrics is a tool. If we don't want it, then we don't need it. We
>can=20
>just do a fixed metric, or interface speed metric, or interface type
>metric, or combination, or whatever we want.
>
>I would not deploy homenet router in my home if it didn't at least
>mimic:ed my current setup, ie could do gigabit/s forwarding within my
>home. (this is what the L2 switch chip does currently). So for me, it's a
>moot point to be able to deploy immediately becase we have no hardware
>that makes sense to deploy on.
>
>I am not aware of any device that fits your requirements, ie src/dst
>routing at gig speeds (well, that's my requirement, you didn't
>specifically write that), can run mainline Linux kernel, has small flash,
>small CPU, and not a lot of RAM.
>
>--=20
>Mikael Abrahamsson    email: swmike@swm.pp.se


From nobody Mon Feb 16 05:17:49 2015
Return-Path: <Ray.Bellis@nominet.org.uk>
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 5DDD81A1B3F for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 05:17:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.31
X-Spam-Level: 
X-Spam-Status: No, score=-4.31 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, 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 qREcJQPm5q2b for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 05:17:46 -0800 (PST)
Received: from mx2.nominet.org.uk (mail.nominet.org.uk [213.248.242.49]) by ietfa.amsl.com (Postfix) with ESMTP id 6190D1A888C for <homenet@ietf.org>; Mon, 16 Feb 2015 05:17:43 -0800 (PST)
DomainKey-Signature: s=main2.dk.nominet.selector; d=nominet.org.uk; c=nofws; q=dns;  h=Received:Received:From:To:CC:Subject:Thread-Topic: Thread-Index:Date:Message-ID:References:In-Reply-To: Accept-Language:Content-Language:X-MS-Has-Attach: X-MS-TNEF-Correlator:x-originating-ip:Content-Type: Content-ID:Content-Transfer-Encoding:MIME-Version; b=yBtr9NJ7t3RIfzFrs9c1C2Zye4ooq1yjGp/d9Ira236mHzZ4mmgBcv92 0ci5Zoq1+8ynH9IiiUKMzV9zHZd+LyGORwkGlxgqoyb9AeFG0agLGwiq5 myT2FBloTnz827DaiEplfMZ4cirdUPrwr8sIb0jkPsN8+PcvhEDaRP5F/ o2EUvnHmgg5bB0EcWaBO+8ef4hYJSSwjapSwALnN0amxI1g/59A5mxatA yFuzkklXhO5T6sJIJIZZfa32x2PLH;
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nominet.org.uk; i=@nominet.org.uk; q=dns/txt; s=main2.dkim.nominet.selector; t=1424092664; x=1455628664; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=QPQPIxROo3wkKwg24Itt7IGj2CAFzF3duLD4hrUGrwo=; b=wmBK2dSohDimBCqtEq58+0sD8M7nFc6+IAzab983rAD1PWvkolMkOFrl kwDlEU7LiPxHN/ca4l8wSSKfRngjGnSlOStv3hkCLz9I9uFWv7kU22GQO I+Wu5RZHj4zl5RLQjcIdm0IVgd7zAO9K4iErzwsf0+HtSITVa1UL8gxMk 75z+6NTooLeqi4F63h2LM5j/KnmQ0FNp4S8aWVceG/Q0uexCqJ/ZN/u99 lCm7RRuYlvGeGXASE2dJcITFQoqPI;
Received: from wds-exc2.okna.nominet.org.uk ([213.248.197.145]) by mx2.nominet.org.uk with ESMTP; 16 Feb 2015 13:17:42 +0000
Received: from WDS-EXC1.okna.nominet.org.uk ([fe80::1593:1394:a91f:8f5f]) by wds-exc2.okna.nominet.org.uk ([fe80::7577:eaca:5241:25d4%16]) with mapi id 14.03.0181.006; Mon, 16 Feb 2015 13:17:42 +0000
From: Ray Bellis <Ray.Bellis@nominet.org.uk>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Thread-Topic: [homenet] Implementations of IS-IS [was: Routing protocol comparison document]
Thread-Index: AQHQSeZZnoEwSlXdHECmKdgFdcst0pzzQhWA
Date: Mon, 16 Feb 2015 13:17:41 +0000
Message-ID: <FAE12FF5-6EFF-4D2B-A6EE-2435F647706F@nominet.org.uk>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <8041EA49-EB50-491B-A3C4-B25FAB52C8FC@iki.fi> <alpine.DEB.2.02.1502161024030.4007@uplift.swm.pp.se> <87twym2fh0.wl-jch@pps.univ-paris-diderot.fr>
In-Reply-To: <87twym2fh0.wl-jch@pps.univ-paris-diderot.fr>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.2.1]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <C0B4F8FE969B0843A70FC4D946882009@okna.nominet.org.uk>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/ofexW0NqQDArNuT82xsVQxWu2qU>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Implementations of IS-IS [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 16 Feb 2015 13:17:48 -0000

> On 16 Feb 2015, at 12:44, Juliusz Chroboczek <jch@pps.univ-paris-diderot.=
fr> wrote:
>=20
> If you know of any reasonably complete open source implementations of
> IS-IS other than the Erlang implementation and the (alpha quality) Quagga
> implementation, please let me know (perhaps by private mail), so I can
> mention them in -02.

Actually, the Chairs would like to know of this too :)

thanks,

Ray


From nobody Mon Feb 16 05:25:25 2015
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 74F0E1A1B3E for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 05:25:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.661
X-Spam-Level: 
X-Spam-Status: No, score=-1.661 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 ukffBXOOj0I8 for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 05:25:22 -0800 (PST)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 552611A1B36 for <homenet@ietf.org>; Mon, 16 Feb 2015 05:25:22 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 70D7FA2; Mon, 16 Feb 2015 14:25:20 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1424093120; bh=3YKnCKHKL5C8RfoGXIOUNGGNC9YsCeEAni8tT0qutlY=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=IEfQlcyaCoJWNqdcbnawvh6gvB8BFEVh2iO1iofXrx/0ZXBvNZXwXnC+U1NOG7qGL +hn+JkIZzHNdbmiq+m4ABmpJathHVRqOSFNu4STzBa+qDAiijTVuJXCE10KcoR/JRS X3+UfN2zViYacoMVcDKMCrTVY7V+Ff69A07X4JzE=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 6C6559F; Mon, 16 Feb 2015 14:25:20 +0100 (CET)
Date: Mon, 16 Feb 2015 14:25:20 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Markus Stenberg <markus.stenberg@iki.fi>
In-Reply-To: <9DB24798-DAC1-49A4-88DA-6A60B4A107BB@iki.fi>
Message-ID: <alpine.DEB.2.02.1502161415320.4007@uplift.swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <8041EA49-EB50-491B-A3C4-B25FAB52C8FC@iki.fi> <alpine.DEB.2.02.1502161024030.4007@uplift.swm.pp.se> <8111DC7E-05BD-4EC2-91F1-44E7D6E31695@iki.fi> <alpine.DEB.2.02.1502161138050.4007@uplift.swm.pp.se> <9DB24798-DAC1-49A4-88DA-6A60B4A107BB@iki.fi>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="-137064504-721075220-1424092715=:4007"
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/UPGFAn_kQuQ8fAXk8qFmzsYZ12w>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 16 Feb 2015 13:25:24 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

---137064504-721075220-1424092715=:4007
Content-Type: TEXT/PLAIN; CHARSET=ISO-8859-7; FORMAT=flowed
Content-Transfer-Encoding: 8BIT

On Mon, 16 Feb 2015, Markus Stenberg wrote:

> Do you consider ISPs more or less cost conscious than the home users? 
> And yes, I know some ISPs have deployed it at some point, and the non-GL 
> was definitely non-enthusiast product at some point as it transitioned 
> from Linux to VxWorks while chasing smaller footprint.

ISPs are more cost conscious than home users. Home users do not chose 
providers based on 5-10 cent difference because they're buying millions of 
them.

> Right. But Babel does sensible things by default. So I am not sure ¢24 
> bits¢ is really ¡pro¢ IS-IS here. (And sensible things in this case are 
> sufficiently dynamic that they do not work well in a link state routing 
> protocol on scale, at least.)

I agree that 24 bit ISIS metrics isn't a great argument for ISIS.

> As long as my ISP does not offer gigabit, I can L2 bridge the LANs 
> still, and route (e.g. wlans, wan port) and get useful performance given 
> current hardware. (Not quite gigabit, but as my upstream is 100mbit and 
> real wireless is also sub-gigabit, it is enough.) I do have 2 upstream 
> connections, and run homenet stuff on existing hardware.

I for instance do backups within my home. I would like to have wifi and 
LAN on different subnets, but then I need gig speed routing between these 
LANs.

So since there is nothing (reasonable) I can buy that'll do homenet at gig 
speeds, I don't see the rush. Sure, your use case where you only need to 
load share between two different ISPs and you don't have high speed (= 
more than 100 megabit/s) traffic outside the L2, then current hw works for 
you.

>
> The year most home connections are gigabit I guess this is no longer a 
> valid choice, but I have some optimism about the hardware at that point 
> too.

I do too.

> P.S. Still waiting for your criteria list ;)

What critera list is that?

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se
---137064504-721075220-1424092715=:4007--


From nobody Mon Feb 16 05:26:08 2015
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 DCBFB1A1B3F for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 05:26:06 -0800 (PST)
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 yc3v_IxSWdXV for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 05:26:05 -0800 (PST)
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 3D4861A1B36 for <homenet@ietf.org>; Mon, 16 Feb 2015 05:26:05 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 73917A2; Mon, 16 Feb 2015 14:26:03 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1424093163; bh=CjoCxZZKPXwHLMZ0OCQN90dpKOuZKknn4QaE12b79i0=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=A0kLL177t2+O8IJ+XOkBAfUEqNlrVzja24XfVIQinJDX00xnDMdYytKkhuvTx311R 9uDuU9Dnu9ilAO+fXymbW9BCuqD9TLC2jOPLqNta7JA7JBK1JKJhDKej5a2LmLe2iw 7t6pQva42/9EZJBR7xwwXQvDiSsppT8G9rpM42CY=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 6D1589F; Mon, 16 Feb 2015 14:26:03 +0100 (CET)
Date: Mon, 16 Feb 2015 14:26:03 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
In-Reply-To: <87vbj22g2w.wl-jch@pps.univ-paris-diderot.fr>
Message-ID: <alpine.DEB.2.02.1502161425300.4007@uplift.swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <8041EA49-EB50-491B-A3C4-B25FAB52C8FC@iki.fi> <alpine.DEB.2.02.1502161024030.4007@uplift.swm.pp.se> <8111DC7E-05BD-4EC2-91F1-44E7D6E31695@iki.fi> <alpine.DEB.2.02.1502161138050.4007@uplift.swm.pp.se> <87vbj22g2w.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/2o3N77ZigjHXlAr3JzpopXpLdJc>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Markus Stenberg <markus.stenberg@iki.fi>
Subject: Re: [homenet] Source-Specific routing on older kernels [was: Routing protocol...]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 16 Feb 2015 13:26:07 -0000

On Mon, 16 Feb 2015, Juliusz Chroboczek wrote:

>> Just the fact that you need src/dst routing means most current
>> mid/higher end hardware won't work at all (or will require significant
>> microcode update to work).
>
> I'd like to point out that one of the conclusions of the work of Matthieu
> is that source-specific routing can be easily implemented on any
> hardware/kernel that supports policy routing -- see Section V.B of
> http://arxiv.org/abs/1403.0445 .  This is implemented in Babel, of course.

Again, the hardware accelerators used in current hw will not necessarily 
support policy routing just because you can configure it in the kernel.

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


From nobody Mon Feb 16 05:28:21 2015
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 DAD201A1B36 for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 05:28:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.661
X-Spam-Level: 
X-Spam-Status: No, score=-1.661 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 V0PsQVT89XEJ for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 05:28:19 -0800 (PST)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DCAEF1A1AF5 for <homenet@ietf.org>; Mon, 16 Feb 2015 05:28:18 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 779C4A3; Mon, 16 Feb 2015 14:28:17 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1424093297; bh=pI3HuqyVTcIXWN100JxM7elz8h2GgvrnNyfqcvQ1iik=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=Rfhy9jIxzBUlaiPF516P53X874sc4yyS3DK+aGtNdzFZ7aCeARO3PuN615jD2Dcwq pur3FD6/dNMuK35U9TZhsZm9jJ5ILwKV5YAQ5U/npCfLDVKXe3KIJHMolVSudlr0f4 UZW+P0sYV2tsjgHhCGC1wt/kBPaKm1GKgtpqB3iM=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 704F39F; Mon, 16 Feb 2015 14:28:17 +0100 (CET)
Date: Mon, 16 Feb 2015 14:28:17 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
In-Reply-To: <87twym2fh0.wl-jch@pps.univ-paris-diderot.fr>
Message-ID: <alpine.DEB.2.02.1502161426230.4007@uplift.swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <8041EA49-EB50-491B-A3C4-B25FAB52C8FC@iki.fi> <alpine.DEB.2.02.1502161024030.4007@uplift.swm.pp.se> <87twym2fh0.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; format=flowed; charset=US-ASCII
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/bqWGIzUF5AdkjmUWJt7Ql0YDWKU>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Implementations of IS-IS [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 16 Feb 2015 13:28:20 -0000

On Mon, 16 Feb 2015, Juliusz Chroboczek wrote:

> If you know of any reasonably complete open source implementations of 
> IS-IS other than the Erlang implementation and the (alpha quality) 
> Quagga implementation, please let me know (perhaps by private mail), so 
> I can mention them in -02.

No, they are not complete.

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


From nobody Mon Feb 16 05:32:11 2015
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 6FA141A1AF5 for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 05:31:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.661
X-Spam-Level: 
X-Spam-Status: No, score=-1.661 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 0tScmtKG-BRW for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 05:31:55 -0800 (PST)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4BC621A1AE7 for <homenet@ietf.org>; Mon, 16 Feb 2015 05:31:55 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id ABFDDA4; Mon, 16 Feb 2015 14:31:53 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1424093513; bh=OWrqypj9GN+yf1jq2OQisQtzDhbTt5DHbvLumeIO1Fc=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=r5M5u23IBJ9JhKCwo/m3hiVX2Kplm3jxCR5bgcC2J5Ix2CHr2u/vhnXdSCMx5qGe1 YndIzXJYjy9YxYZyzAOj4wuaNTbuArnGaM8v8eH/qAMpVnhgJvQkrowGfn0OOPA4js W01cAtI81rGtHzYegIucXm59GEynF6Aj2Am56lA8=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id A48CB9F; Mon, 16 Feb 2015 14:31:53 +0100 (CET)
Date: Mon, 16 Feb 2015 14:31:53 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Ray Bellis <Ray.Bellis@nominet.org.uk>
In-Reply-To: <FAE12FF5-6EFF-4D2B-A6EE-2435F647706F@nominet.org.uk>
Message-ID: <alpine.DEB.2.02.1502161429130.4007@uplift.swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <8041EA49-EB50-491B-A3C4-B25FAB52C8FC@iki.fi> <alpine.DEB.2.02.1502161024030.4007@uplift.swm.pp.se> <87twym2fh0.wl-jch@pps.univ-paris-diderot.fr> <FAE12FF5-6EFF-4D2B-A6EE-2435F647706F@nominet.org.uk>
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/otyAiAAAvLCFopMSkiaBIoZmOVg>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] Implementations of IS-IS [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 16 Feb 2015 13:31:59 -0000

On Mon, 16 Feb 2015, Ray Bellis wrote:

>
>> On 16 Feb 2015, at 12:44, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr> wrote:
>>
>> If you know of any reasonably complete open source implementations of
>> IS-IS other than the Erlang implementation and the (alpha quality) Quagga
>> implementation, please let me know (perhaps by private mail), so I can
>> mention them in -02.
>
> Actually, the Chairs would like to know of this too :)

My point was not to say that there were other ISIS implementations (I 
would have said so earlier if that was the case), but that you can write 
ISIS in basically any language (including Erlang and Pyton), so the 
comment about ISIS needing L2 access (and that it isn't IP), isn't 
something that seems to be a real issue in real life.

ISIS can provide topology and get brought up before HNCP has even come up, 
and can provide topology. If this is a feature or a duplication of 
functionality is up to each individual to decide :P

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


From nobody Mon Feb 16 05:48:29 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 10E451A1B49 for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 05:48:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35] autolearn=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 KVIDSKoR4l76 for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 05:48:26 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 AF5871A1B0D for <homenet@ietf.org>; Mon, 16 Feb 2015 05:48:25 -0800 (PST)
Received: from potemkin.univ-paris7.fr (potemkin.univ-paris7.fr [IPv6:2001:660:3301:8000::1:1]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t1GDmOPu004672 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 16 Feb 2015 14:48:24 +0100
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by potemkin.univ-paris7.fr (8.14.4/8.14.4/relay2/56228) with ESMTP id t1GDmOJU028083; Mon, 16 Feb 2015 14:48:24 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 1E3892BF910; Mon, 16 Feb 2015 14:48:24 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id MJZQNGCXKzCr; Mon, 16 Feb 2015 14:48:22 +0100 (CET)
Received: from pirx.pps.jussieu.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id BB7522BF90A; Mon, 16 Feb 2015 14:48:21 +0100 (CET)
Date: Mon, 16 Feb 2015 14:48:21 +0100
Message-ID: <87mw4e2cii.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Mikael Abrahamsson <swmike@swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1502161429130.4007@uplift.swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <8041EA49-EB50-491B-A3C4-B25FAB52C8FC@iki.fi> <alpine.DEB.2.02.1502161024030.4007@uplift.swm.pp.se> <87twym2fh0.wl-jch@pps.univ-paris-diderot.fr> <FAE12FF5-6EFF-4D2B-A6EE-2435F647706F@nominet.org.uk> <alpine.DEB.2.02.1502161429130.4007@uplift.swm.pp.se>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]); Mon, 16 Feb 2015 14:48:24 +0100 (CET)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Mon, 16 Feb 2015 14:48:24 +0100 (CET)
X-Miltered: at korolev with ID 54E1F528.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 54E1F528.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54E1F528.000 from potemkin.univ-paris7.fr/potemkin.univ-paris7.fr/null/potemkin.univ-paris7.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Enveloppe: 54E1F528.001 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54E1F528.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 54E1F528.001 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/E3BwSPvUzK2zpWk9jq448at6DTo>
Cc: Ray Bellis <Ray.Bellis@nominet.org.uk>, "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Implementations of IS-IS [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 16 Feb 2015 13:48:27 -0000

> ISIS needing L2 access (and that it isn't IP), isn't something that
> seems to be a real issue in real life.

As I mentioned previously, it has two consequences:

  - IS-IS cannot be implemented using the portable and familiar RFC 3493 APIs;
  - IS-IS cannot run over a GRE tunnel (without specific support).

Whether these are "real issues in real life" is open to discussion, but
I think we should be mentioning this in -02.

> ISIS can provide topology and get brought up before HNCP has even come up,
> and can provide topology.

Just like IS-IS, Babel can establish adjacencies and start routing IPv6
before it gets an address, and doesn't need to reconverge when IPv6
renumbers: link-local IPv6 addresses are almost as stable as MAC
addresses.

(Interestingly enough, getting the notion of neighbour association just
right is what caused the last incompatible protocol change, back in 2008.)

-- Juliusz


From nobody Mon Feb 16 05:58:33 2015
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 D702F1A1B4B for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 05:58:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.661
X-Spam-Level: 
X-Spam-Status: No, score=-1.661 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 WfRieA_j_FU2 for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 05:58:27 -0800 (PST)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 555331A1B54 for <homenet@ietf.org>; Mon, 16 Feb 2015 05:58:25 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 75DADA2; Mon, 16 Feb 2015 14:58:23 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1424095103; bh=IgjeZF+Oe/S31oVC5DjlXg9NzI2PT/Obday6OVkCX0I=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=fKJc4SXny4JPDf4d5aZiCNulf0QjlwdMp60myKwUo5pfExITJ9OBpVYK6M2s249mq 6dc7TFHRkVcsg9XqLh5hjkdgPko8wjYyon5pDf/5IDF7P+5bVRethHX+gqUdNzBnZU wqkl33DlQUTsUNbcSFFvJ53FfZf6G53j5b8EEQlY=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 6DE149F; Mon, 16 Feb 2015 14:58:23 +0100 (CET)
Date: Mon, 16 Feb 2015 14:58:23 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
In-Reply-To: <87mw4e2cii.wl-jch@pps.univ-paris-diderot.fr>
Message-ID: <alpine.DEB.2.02.1502161451020.4007@uplift.swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <8041EA49-EB50-491B-A3C4-B25FAB52C8FC@iki.fi> <alpine.DEB.2.02.1502161024030.4007@uplift.swm.pp.se> <87twym2fh0.wl-jch@pps.univ-paris-diderot.fr> <FAE12FF5-6EFF-4D2B-A6EE-2435F647706F@nominet.org.uk> <alpine.DEB.2.02.1502161429130.4007@uplift.swm.pp.se> <87mw4e2cii.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/7jMvWSRlwGREzgF-NK3QlLucvoA>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Implementations of IS-IS [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 16 Feb 2015 13:58:29 -0000

On Mon, 16 Feb 2015, Juliusz Chroboczek wrote:

>> ISIS can provide topology and get brought up before HNCP has even come up,
>> and can provide topology.
>
> Just like IS-IS, Babel can establish adjacencies and start routing IPv6
> before it gets an address, and doesn't need to reconverge when IPv6
> renumbers: link-local IPv6 addresses are almost as stable as MAC
> addresses.

That is not the same thing as I wrote. Babel can't provide topology, 
correct? You need to be a link-state protocol to do that as far as I have 
understood?

HNCP contains the same thing as a link-state protocol to find out 
topology. HNCP could theoretically use the ISIS topology instead of its 
own, but it couldn't rely on Babel to do the same job, right?

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


From nobody Mon Feb 16 06:10:24 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 E73D01A1AE0 for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 06:10:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35] autolearn=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 t3cf9Tr5zvNA for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 06:10:20 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 70A681A1AEA for <homenet@ietf.org>; Mon, 16 Feb 2015 06:10:20 -0800 (PST)
Received: from potemkin.univ-paris7.fr (potemkin.univ-paris7.fr [IPv6:2001:660:3301:8000::1:1]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t1GEAIxr016980 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 16 Feb 2015 15:10:18 +0100
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by potemkin.univ-paris7.fr (8.14.4/8.14.4/relay2/56228) with ESMTP id t1GEAIoL007092; Mon, 16 Feb 2015 15:10:18 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id A2A122BF912; Mon, 16 Feb 2015 15:10:18 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id 7JLd1YjQZkjj; Mon, 16 Feb 2015 15:10:17 +0100 (CET)
Received: from pirx.pps.jussieu.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 2D9272BF90A; Mon, 16 Feb 2015 15:10:17 +0100 (CET)
Date: Mon, 16 Feb 2015 15:10:17 +0100
Message-ID: <87k2zi2bhy.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Mikael Abrahamsson <swmike@swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1502161451020.4007@uplift.swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <8041EA49-EB50-491B-A3C4-B25FAB52C8FC@iki.fi> <alpine.DEB.2.02.1502161024030.4007@uplift.swm.pp.se> <87twym2fh0.wl-jch@pps.univ-paris-diderot.fr> <FAE12FF5-6EFF-4D2B-A6EE-2435F647706F@nominet.org.uk> <alpine.DEB.2.02.1502161429130.4007@uplift.swm.pp.se> <87mw4e2cii.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502161451020.4007@uplift.swm.pp.se>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]); Mon, 16 Feb 2015 15:10:18 +0100 (CET)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Mon, 16 Feb 2015 15:10:18 +0100 (CET)
X-Miltered: at korolev with ID 54E1FA4A.004 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 54E1FA4A.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54E1FA4A.004 from potemkin.univ-paris7.fr/potemkin.univ-paris7.fr/null/potemkin.univ-paris7.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Enveloppe: 54E1FA4A.001 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54E1FA4A.004 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 54E1FA4A.001 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/RYlYyq9GqprebKoIA27pICy7lU4>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Implementations of IS-IS [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 16 Feb 2015 14:10:22 -0000

> HNCP contains the same thing as a link-state protocol to find out
> topology. HNCP could theoretically use the ISIS topology instead of its
> own, but it couldn't rely on Babel to do the same job, right?

Correct.

-- Juliusz


From nobody Mon Feb 16 06:12:07 2015
Return-Path: <cyrus@openwrt.org>
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 EF13E1A1B36 for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 06:12:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.25
X-Spam-Level: 
X-Spam-Status: No, score=-2.25 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-0.7] 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 7UE_bg2xUAwq for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 06:11:57 -0800 (PST)
Received: from mail.core-networks.de (mail.core-networks.de [82.96.72.7]) by ietfa.amsl.com (Postfix) with ESMTP id C81BB1A1B51 for <homenet@ietf.org>; Mon, 16 Feb 2015 06:11:56 -0800 (PST)
Received: from localhost ([127.0.0.1]) by mail.core-networks.de id 1YNMOv-0001Am-CW with ESMTPSA (TLSv1.2:DHE-RSA-AES128-SHA:128) for ; Mon, 16 Feb 2015 15:11:53 +0100
Message-ID: <54E1FAA8.6050809@openwrt.org>
Date: Mon, 16 Feb 2015 15:11:52 +0100
From: Steven Barth <cyrus@openwrt.org>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Ray Bellis <Ray.Bellis@nominet.org.uk>,  Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <8041EA49-EB50-491B-A3C4-B25FAB52C8FC@iki.fi> <alpine.DEB.2.02.1502161024030.4007@uplift.swm.pp.se> <87twym2fh0.wl-jch@pps.univ-paris-diderot.fr> <FAE12FF5-6EFF-4D2B-A6EE-2435F647706F@nominet.org.uk>
In-Reply-To: <FAE12FF5-6EFF-4D2B-A6EE-2435F647706F@nominet.org.uk>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/PzO6W51PcNlyMfbFp3OfYrLZ708>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Implementations of IS-IS [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 16 Feb 2015 14:12:03 -0000

>> On 16 Feb 2015, at 12:44, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr> wrote:
>>
>> If you know of any reasonably complete open source implementations of
>> IS-IS other than the Erlang implementation and the (alpha quality) Quagga
>> implementation, please let me know (perhaps by private mail), so I can
>> mention them in -02.
> Actually, the Chairs would like to know of this too :)
I think it would be equally interesting to see a specification of that 
homenet-variant/subset of IS-IS. The comparison draft is very vague on 
that front and judging by some on-list and off-list discussions there 
seems to be a lack of consensus for at least some of the details. I mean 
not (yet) having an implementation is one thing, but not even knowing 
what the protocol will look like doesn't really help here either.



From nobody Mon Feb 16 06:26:30 2015
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 0BD411A1B98 for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 06:26:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.661
X-Spam-Level: 
X-Spam-Status: No, score=-1.661 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 Xeyb6CXs0KEP for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 06:26:22 -0800 (PST)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 26F331A1B9B for <homenet@ietf.org>; Mon, 16 Feb 2015 06:26:21 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 71401A2; Mon, 16 Feb 2015 15:26:19 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1424096779; bh=CT/0SlzCgyrxV4+8HxvCtR2/w1eRuJ7dQj8FNBq9u1w=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=viPNx1U7FG4qmNVCVdP1kct0fPl5Yf9bGtEsHlm4WMwEc0W6GAH7eoBwLIIUZCDzz KdpAUamQKthlGkWxYzpj/+jhg2b3LH3c0QFws9/t7+em6Tr6XL1zmTcIuFCZsv3LZK vGBdFF3yn+gUDuZW7IgLNpwMCDj9+cXOVfvSbSyY=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 6D9799F; Mon, 16 Feb 2015 15:26:19 +0100 (CET)
Date: Mon, 16 Feb 2015 15:26:19 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Steven Barth <cyrus@openwrt.org>
In-Reply-To: <54E1FAA8.6050809@openwrt.org>
Message-ID: <alpine.DEB.2.02.1502161521530.4007@uplift.swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <8041EA49-EB50-491B-A3C4-B25FAB52C8FC@iki.fi> <alpine.DEB.2.02.1502161024030.4007@uplift.swm.pp.se> <87twym2fh0.wl-jch@pps.univ-paris-diderot.fr> <FAE12FF5-6EFF-4D2B-A6EE-2435F647706F@nominet.org.uk> <54E1FAA8.6050809@openwrt.org>
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/e5iLz0Ks6Gvi68vi7hUsOqtfJMo>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Implementations of IS-IS [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 16 Feb 2015 14:26:24 -0000

On Mon, 16 Feb 2015, Steven Barth wrote:

> I think it would be equally interesting to see a specification of that 
> homenet-variant/subset of IS-IS. The comparison draft is very vague on 
> that front and judging by some on-list and off-list discussions there 
> seems to be a lack of consensus for at least some of the details. I mean 
> not (yet) having an implementation is one thing, but not even knowing 
> what the protocol will look like doesn't really help here either.

You mean what the TLVs look like exactly for the src/dst extensions to 
ISIS?

That is being worked on together with the ISIS WG. There are a few 
different ways of doing it, nothing that would fundamentally change the 
inner workings of it as far as I know. It's mostly what TLVs would be 
used.

Or do you want to know what way the current implementation does it?

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


From nobody Mon Feb 16 06:34:56 2015
Return-Path: <gert@Space.Net>
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 97AD21A1B67 for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 06:34:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.61
X-Spam-Level: 
X-Spam-Status: No, score=-2.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 a2Oa1d-UJbhu for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 06:34:52 -0800 (PST)
Received: from mobil.space.net (mobil.space.net [195.30.115.67]) (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 AB43E1A1B7A for <homenet@ietf.org>; Mon, 16 Feb 2015 06:34:33 -0800 (PST)
X-Original-To: homenet@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id B7F5B6045E for <homenet@ietf.org>; Mon, 16 Feb 2015 15:34:31 +0100 (CET)
X-SpaceNet-Relay: true
Received: from moebius3.space.net (moebius3.Space.Net [IPv6:2001:608:2:2::250]) by mobil.space.net (Postfix) with ESMTPS id 82AF660054 for <homenet@ietf.org>; Mon, 16 Feb 2015 15:34:31 +0100 (CET)
Received: (qmail 80048 invoked by uid 1007); 16 Feb 2015 15:34:31 +0100
Date: Mon, 16 Feb 2015 15:34:31 +0100
From: Gert Doering <gert@space.net>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Message-ID: <20150216143431.GK34798@Space.Net>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <8041EA49-EB50-491B-A3C4-B25FAB52C8FC@iki.fi> <alpine.DEB.2.02.1502161024030.4007@uplift.swm.pp.se> <87twym2fh0.wl-jch@pps.univ-paris-diderot.fr> <FAE12FF5-6EFF-4D2B-A6EE-2435F647706F@nominet.org.uk> <alpine.DEB.2.02.1502161429130.4007@uplift.swm.pp.se>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.DEB.2.02.1502161429130.4007@uplift.swm.pp.se>
X-NCC-RegID: de.space
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/37Ia4SPzbH8ibm0UCkIPtr2LqHg>
Cc: Ray Bellis <Ray.Bellis@nominet.org.uk>, "homenet@ietf.org Group" <homenet@ietf.org>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] Implementations of IS-IS [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 16 Feb 2015 14:34:54 -0000

Hi,

On Mon, Feb 16, 2015 at 02:31:53PM +0100, Mikael Abrahamsson wrote:
> My point was not to say that there were other ISIS implementations (I 
> would have said so earlier if that was the case), but that you can write 
> ISIS in basically any language (including Erlang and Pyton), so the 
> comment about ISIS needing L2 access (and that it isn't IP), isn't 
> something that seems to be a real issue in real life.

Out of interest: how is ISIS done on "Linuxish" devices?  Grabbing 
ISIS packets off the link with libpcap?

This is one of the nice aspects of HNCP and Babel - "just use plain UDP
over link-local v6", so no need to mess with packet capturing etc.

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444           USt-IdNr.: DE813185279


From nobody Mon Feb 16 06:43:34 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 CE3A11A1B0C for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 06:43:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35] autolearn=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 TIA4pzSBETQw for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 06:43:30 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 8503B1A1B0A for <homenet@ietf.org>; Mon, 16 Feb 2015 06:43:30 -0800 (PST)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t1GEhSn4010068; Mon, 16 Feb 2015 15:43:29 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id D86CB2BF918; Mon, 16 Feb 2015 15:43:28 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id AReDv90LbVBj; Mon, 16 Feb 2015 15:43:27 +0100 (CET)
Received: from pirx.pps.jussieu.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 208EF2BF917; Mon, 16 Feb 2015 15:43:27 +0100 (CET)
Date: Mon, 16 Feb 2015 15:43:27 +0100
Message-ID: <87h9ul3oj4.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Mikael Abrahamsson <swmike@swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1502161521530.4007@uplift.swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <8041EA49-EB50-491B-A3C4-B25FAB52C8FC@iki.fi> <alpine.DEB.2.02.1502161024030.4007@uplift.swm.pp.se> <87twym2fh0.wl-jch@pps.univ-paris-diderot.fr> <FAE12FF5-6EFF-4D2B-A6EE-2435F647706F@nominet.org.uk> <54E1FAA8.6050809@openwrt.org> <alpine.DEB.2.02.1502161521530.4007@uplift.swm.pp.se>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Mon, 16 Feb 2015 15:43:29 +0100 (CET)
X-Miltered: at korolev with ID 54E20210.002 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54E20210.002 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54E20210.002 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/_ujhBj3SbTE8a5TxnAoK79qot7Y>
Cc: Steven Barth <cyrus@openwrt.org>, "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Implementations of IS-IS [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 16 Feb 2015 14:43:32 -0000

>> I think it would be equally interesting to see a specification of that
>> homenet-variant/subset of IS-IS. The comparison draft is very vague on
>> that front

> You mean what the TLVs look like exactly for the src/dst extensions to
> ISIS?

No, I don't think that's what Steve means.

Sections 12 and 15.5 of the comparison draft claim that Homenet will use
a single-area subset of IS-IS without the overly exciting features of the
protocol (partition repair, multi-topology, etc.).  To quote:

   For HOMENET we need a level-1 only implementation supporting a common
   topology for IPv4 and IPv6 over broadcast (i.e., ethernet) link
   types.  Additionally, we only require support of the latest extended
   metric TLVs (i.e., not implement legacy metric support).

Now, "everyone" knows that this can be done -- since there is no such
thing as a complete implementation of IS-IS, the IS-IS crowd have a lot of
experience implementing unspecified subsets of the protocol.  However,
those of us with more of an IETF background would feel somewhat more
comfortable if the advocated subset were clearly defined, or even
implemented.  As Markus is keen on repeating, the devil is often in the
details.

-- Juliusz


From nobody Mon Feb 16 06:49:43 2015
Return-Path: <cyrus@openwrt.org>
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 44DC11A1B7B for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 06:49:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.25
X-Spam-Level: 
X-Spam-Status: No, score=-2.25 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-0.7] 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 IdBQ-stY1Bpf for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 06:49:38 -0800 (PST)
Received: from mail.core-networks.de (mail.core-networks.de [82.96.72.7]) by ietfa.amsl.com (Postfix) with ESMTP id 7F41F1A1B0D for <homenet@ietf.org>; Mon, 16 Feb 2015 06:49:38 -0800 (PST)
Received: from localhost ([127.0.0.1]) by mail.core-networks.de id 1YNMzP-0002g3-Cg with ESMTPSA (TLSv1.2:DHE-RSA-AES128-SHA:128) for ; Mon, 16 Feb 2015 15:49:35 +0100
Message-ID: <54E2037E.9010104@openwrt.org>
Date: Mon, 16 Feb 2015 15:49:34 +0100
From: Steven Barth <cyrus@openwrt.org>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Mikael Abrahamsson <swmike@swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <8041EA49-EB50-491B-A3C4-B25FAB52C8FC@iki.fi> <alpine.DEB.2.02.1502161024030.4007@uplift.swm.pp.se> <87twym2fh0.wl-jch@pps.univ-paris-diderot.fr> <FAE12FF5-6EFF-4D2B-A6EE-2435F647706F@nominet.org.uk> <54E1FAA8.6050809@openwrt.org> <alpine.DEB.2.02.1502161521530.4007@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1502161521530.4007@uplift.swm.pp.se>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/nDi1E2_KZlQb36FPftGfFv0Dd3o>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Implementations of IS-IS [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 16 Feb 2015 14:49:40 -0000

> You mean what the TLVs look like exactly for the src/dst extensions to 
> ISIS?
>
Well not all too specific. I want to read or at least scan through the 
specifications that tell me how this homenet-variant of IS-IS would look 
like, i.e. what drafts / RFCs or chapters of these are relevant and 
which aren't.

For IS-IS the comparison draft points me to RFC 1142 which seems to be 
the obsoleted OSI-standard and then straight to the auto-conf and 
source-specific drafts which doesn't really help (at least me) very much.

For Babel I can read: RFC 6126 and draft-boutier-babel-source-specific 
about 50-60 pages and that seems to be it.
What's the equivalent of that for the homenet IS-IS variant?


From nobody Mon Feb 16 06:53:26 2015
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 A25071A1B0D for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 06:53:21 -0800 (PST)
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 STg1utaHP_hs for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 06:53:15 -0800 (PST)
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 9695C1A1AE0 for <homenet@ietf.org>; Mon, 16 Feb 2015 06:53:15 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 32C14A2; Mon, 16 Feb 2015 15:53:14 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1424098394; bh=3AIEv5QELeQkzLEk3fIdXLrAzVWstfO8GvEGMA3UKCc=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=ZWCnBIjjPNIZgWLX/ViX1SMmdnNvY7zR0SKDYpCgIwIUKYj6e7ugWErlCGDTfkrVW Bx9fYycO7L4oM9XgrU0JEoBxHPQp6nB4/+UlC4cauh59LcS/BAGzQTjn8z9ZA+WcB+ 34MubNlbFf/+YDziNacIxY5WodrXlSWLI7VnDuAw=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 2EE6D9F; Mon, 16 Feb 2015 15:53:14 +0100 (CET)
Date: Mon, 16 Feb 2015 15:53:14 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Steven Barth <cyrus@openwrt.org>
In-Reply-To: <54E2037E.9010104@openwrt.org>
Message-ID: <alpine.DEB.2.02.1502161551460.4007@uplift.swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <8041EA49-EB50-491B-A3C4-B25FAB52C8FC@iki.fi> <alpine.DEB.2.02.1502161024030.4007@uplift.swm.pp.se> <87twym2fh0.wl-jch@pps.univ-paris-diderot.fr> <FAE12FF5-6EFF-4D2B-A6EE-2435F647706F@nominet.org.uk> <54E1FAA8.6050809@openwrt.org> <alpine.DEB.2.02.1502161521530.4007@uplift.swm.pp.se> <54E2037E.9010104@openwrt.org>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/n0mq0ZDweuxW-Jt1k8Bf8UT1BKc>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Implementations of IS-IS [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 16 Feb 2015 14:53:21 -0000

On Mon, 16 Feb 2015, Steven Barth wrote:

> For IS-IS the comparison draft points me to RFC 1142 which seems to be 
> the obsoleted OSI-standard and then straight to the auto-conf and 
> source-specific drafts which doesn't really help (at least me) very 
> much.

Ok, understood. I will investigate.

> For Babel I can read: RFC 6126 and draft-boutier-babel-source-specific about 
> 50-60 pages and that seems to be it.
> What's the equivalent of that for the homenet IS-IS variant?

Check. In the meantime, could we get confirmation that your above "that 
seems to be it" assumption is true for babel? Juliusz?

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


From nobody Mon Feb 16 07:07:45 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 2F37A1A1BBB for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 07:07:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.15
X-Spam-Level: 
X-Spam-Status: No, score=-0.15 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, HELO_EQ_FR=0.35] autolearn=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 ggaw8xxethMJ for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 07:07:42 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 CA0741A1B88 for <homenet@ietf.org>; Mon, 16 Feb 2015 07:07:41 -0800 (PST)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t1GF7eRs006447; Mon, 16 Feb 2015 16:07:40 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 5462F2BF920; Mon, 16 Feb 2015 16:07:40 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id JgKGy9kxMfA1; Mon, 16 Feb 2015 16:07:38 +0100 (CET)
Received: from pirx.pps.jussieu.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id DDC412BF912; Mon, 16 Feb 2015 16:07:38 +0100 (CET)
Date: Mon, 16 Feb 2015 16:07:38 +0100
Message-ID: <87fva53net.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Gert Doering <gert@space.net>
In-Reply-To: <20150216143431.GK34798@Space.Net>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <8041EA49-EB50-491B-A3C4-B25FAB52C8FC@iki.fi> <alpine.DEB.2.02.1502161024030.4007@uplift.swm.pp.se> <87twym2fh0.wl-jch@pps.univ-paris-diderot.fr> <FAE12FF5-6EFF-4D2B-A6EE-2435F647706F@nominet.org.uk> <alpine.DEB.2.02.1502161429130.4007@uplift.swm.pp.se> <20150216143431.GK34798@Space.Net>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Mon, 16 Feb 2015 16:07:40 +0100 (CET)
X-Miltered: at korolev with ID 54E207BC.002 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54E207BC.002 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54E207BC.002 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/EqlNRakLQIq719hPsxUEmFT4x04>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Implementations of IS-IS
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 16 Feb 2015 15:07:43 -0000

> Out of interest: how is ISIS done on "Linuxish" devices?  Grabbing 
> ISIS packets off the link with libpcap?

The Erlang version uses a PF_PACKET, SOCK_RAW socket.

The alpha Quagga version appears to have three implementations:

  - on Linux, it uses a PF_PACKET, SOCK_DGRAM socket;
  - on Solaris, it uses STREAMS DLPI;
  - otherwise, it uses BPF.

(I have no idea which of these implementations are functional, I'm just
looking at the source.)

-- Juliusz


From nobody Mon Feb 16 07:12:49 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 1502E1A1BBB for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 07:12:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35] autolearn=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 aKy2m6NP2t5f for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 07:12:46 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 B0C921A1EF3 for <homenet@ietf.org>; Mon, 16 Feb 2015 07:12:45 -0800 (PST)
Received: from potemkin.univ-paris7.fr (potemkin.univ-paris7.fr [IPv6:2001:660:3301:8000::1:1]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t1GFCiSn012684 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 16 Feb 2015 16:12:44 +0100
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by potemkin.univ-paris7.fr (8.14.4/8.14.4/relay2/56228) with ESMTP id t1GFCihP020230; Mon, 16 Feb 2015 16:12:44 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 1E1E52BF91B; Mon, 16 Feb 2015 16:12:44 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id k6kANfsTvUVb; Mon, 16 Feb 2015 16:12:42 +0100 (CET)
Received: from pirx.pps.jussieu.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 95B752BF912; Mon, 16 Feb 2015 16:12:42 +0100 (CET)
Date: Mon, 16 Feb 2015 16:12:42 +0100
Message-ID: <87egpp3n6d.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Mikael Abrahamsson <swmike@swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1502161551460.4007@uplift.swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <8041EA49-EB50-491B-A3C4-B25FAB52C8FC@iki.fi> <alpine.DEB.2.02.1502161024030.4007@uplift.swm.pp.se> <87twym2fh0.wl-jch@pps.univ-paris-diderot.fr> <FAE12FF5-6EFF-4D2B-A6EE-2435F647706F@nominet.org.uk> <54E1FAA8.6050809@openwrt.org> <alpine.DEB.2.02.1502161521530.4007@uplift.swm.pp.se> <54E2037E.9010104@openwrt.org> <alpine.DEB.2.02.1502161551460.4007@uplift.swm.pp.se>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]); Mon, 16 Feb 2015 16:12:44 +0100 (CET)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Mon, 16 Feb 2015 16:12:44 +0100 (CET)
X-Miltered: at korolev with ID 54E208EC.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 54E208EC.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54E208EC.000 from potemkin.univ-paris7.fr/potemkin.univ-paris7.fr/null/potemkin.univ-paris7.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Enveloppe: 54E208EC.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54E208EC.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 54E208EC.000 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/A0BWfXwljFRTbbk8GJHMrRpjYmI>
Cc: Steven Barth <cyrus@openwrt.org>, "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Implementations of IS-IS [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 16 Feb 2015 15:12:48 -0000

>> For Babel I can read: RFC 6126 and draft-boutier-babel-source-specific
>> about 50-60 pages and that seems to be it.
>> What's the equivalent of that for the homenet IS-IS variant?
>
> Check. In the meantime, could we get confirmation that your above "that
> seems to be it" assumption is true for babel? Juliusz?

There's also draft-chroboczek-babel-extension-mechanism, which is 5 pages
not counting IANA considerations.

-- Juliusz


From nobody Mon Feb 16 07:17:07 2015
Return-Path: <margaretw42@gmail.com>
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 B42F11A88AE for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 07:16:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level: 
X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] 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 cYDCx42x1KbK for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 07:16:44 -0800 (PST)
Received: from mail-pd0-f176.google.com (mail-pd0-f176.google.com [209.85.192.176]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 630821A1BBB for <homenet@ietf.org>; Mon, 16 Feb 2015 07:16:44 -0800 (PST)
Received: by pdev10 with SMTP id v10so36354263pde.7 for <homenet@ietf.org>; Mon, 16 Feb 2015 07:16:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=q/YD9Yu1AG78ngITMgEBCjNZgqFvCEGqH39aoCa3v2A=; b=OOrc/tN5OheVtd+Cr1GsUvmPMRqY7QjdYwUZoHssEBoZk2aRbKIh74Bl39tjxbuflG Ug/2+QR2/G6XNi8pZ/OUeluYCpI2I+VlloMttyzuhYMmfyazfCBHLd37btiY84t9J95z hJeq14J4yKisT4HsH9rMRNv5+lCr2OtAzPTVSa7H0TOqy8UDsmb3131mN6XOzJ31+GXe 7KBlR34zObh12zVLCwe5XTSQiUOFa4ynaBqkaBmZxLHm4WEa3bdp1zLx9UJ+N77bW0qt AhH7rZp6jQYDIHDGjrNVoXZ4nJLMl3bMGrmGtX3EchM+UV7ZeCR6dOVIMC0nD2QZPWdA yZUA==
X-Received: by 10.66.192.106 with SMTP id hf10mr41109266pac.90.1424099803077;  Mon, 16 Feb 2015 07:16:43 -0800 (PST)
Received: from [192.168.7.248] (wsip-24-248-179-54.ph.ph.cox.net. [24.248.179.54]) by mx.google.com with ESMTPSA id th8sm14989880pbc.38.2015.02.16.07.16.41 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 16 Feb 2015 07:16:42 -0800 (PST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Margaret Wasserman <margaretw42@gmail.com>
In-Reply-To: <alpine.DEB.2.02.1502161429130.4007@uplift.swm.pp.se>
Date: Mon, 16 Feb 2015 10:16:39 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <282DBA30-FDCA-47EF-825A-7B44EA47C897@gmail.com>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <8041EA49-EB50-491B-A3C4-B25FAB52C8FC@iki.fi> <alpine.DEB.2.02.1502161024030.4007@uplift.swm.pp.se> <87twym2fh0.wl-jch@pps.univ-paris-diderot.fr> <FAE12FF5-6EFF-4D2B-A6EE-2435F647706F@nominet.org.uk> <alpine.DEB.2.02.1502161429130.4007@uplift.swm.pp.se>
To: Mikael Abrahamsson <swmike@swm.pp.se>
X-Mailer: Apple Mail (2.1510)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/CbQwBNU1XeutaLZ0wtuReT07nUE>
Cc: Ray Bellis <Ray.Bellis@nominet.org.uk>, "homenet@ietf.org Group" <homenet@ietf.org>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] Implementations of IS-IS [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 16 Feb 2015 15:16:59 -0000

Hi Juliusz,

On 16 Feb 2015, at 12:44, Juliusz Chroboczek =
<jch@pps.univ-paris-diderot.fr> wrote:
> If you know of any reasonably complete open source implementations of
> IS-IS other than the Erlang implementation and the (alpha quality) =
Quagga
> implementation, please let me know (perhaps by private mail), so I can
> mention them in -02.

You keep mentioning that Quagga is "alpha quality" but i am not sure =
that provides any pertinent information.  The fact that Quagga make a =
distinction between different levels of quality and maturity and has =
tagged their current IS-IS release to indicate that it is "alpha quality =
is only pertinent if you make the same types of distinctions for the =
Babel code, and the Babel code is at a higher level of stability and =
maturity.

When you add features, such as source specific routing, to your Babel =
codebase, do you go through a full formal release process with Alpha, =
Beta and Production versions?  How many beta testers need to return =
positive feedback before you have a production release?  If you don't go =
through that sort of process, do you have some other way of indicating =
the maturity and stability of the code base?  If so, what stage is the =
version of Babel that contains the source-specific routing in now, and =
what level of regression testing, testbed operational testing and =
success in production environments does that represent?

If I understood correctly, you mentioned in a private thread that the =
Quagga IS-IS codebase is not being maintained right now.  Is that =
correct?  I co consider that to be a pertinent fact.

I would also be interested in knowing whether the Quagga version of =
IS-IS works.  Does anyone have any experience with it?=20

You have mentioned that Babel is "in OpenWRT" or something along those =
lines=85  Is the version with source-specific routing included in =
OpenWRT yet?  If not, what is the process by which that will be included =
in an OpenWRT release?

How many commercial router vendors have it enabled in their products?  =
Is it being used on any operational networks.  [BTW, for the person who =
asked elsewhere "operational network"  means "a network that is =
currently working to allow people do real work, not just to test your =
software", it doesn't mean that the network is managed or involves an =
"operator".  The Verizon network in my home is quite "operational", as =
is the one here at my hotel.

It is quite possible that your specific Babel codebase is better =
maintained, more completely tested, in use on more operational networks, =
and more functional than the Alpha-quality Quagga release of IS-IS, but =
I would like to understand that in terms that are meaningful.

Thanks,
Margaret






From nobody Mon Feb 16 07:57:36 2015
Return-Path: <markus.stenberg@iki.fi>
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 55A181A1BA7 for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 07:57:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.121
X-Spam-Level: 
X-Spam-Status: No, score=-1.121 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_NEUTRAL=0.779] autolearn=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 qNWk3qjAA3Qy for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 07:57:32 -0800 (PST)
Received: from jenni2.inet.fi (mta-out1.inet.fi [62.71.2.203]) by ietfa.amsl.com (Postfix) with ESMTP id BF8561A1EF7 for <homenet@ietf.org>; Mon, 16 Feb 2015 07:57:31 -0800 (PST)
Received: from poro.lan (80.220.64.126) by jenni2.inet.fi (8.5.142.08) (authenticated as stenma-47) id 54C8F2EA029691A0; Mon, 16 Feb 2015 17:57:27 +0200
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Markus Stenberg <markus.stenberg@iki.fi>
In-Reply-To: <282DBA30-FDCA-47EF-825A-7B44EA47C897@gmail.com>
Date: Mon, 16 Feb 2015 17:57:25 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <C6504EC1-3F29-419B-88E4-6EB96BA9CE67@iki.fi>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <8041EA49-EB50-491B-A3C4-B25FAB52C8FC@iki.fi> <alpine.DEB.2.02.1502161024030.4007@uplift.swm.pp.se> <87twym2fh0.wl-jch@pps.univ-paris-diderot.fr> <FAE12FF5-6EFF-4D2B-A6EE-2435F647706F@nominet.org.uk> <alpine.DEB.2.02.1502161429130.4007@uplift.swm.pp.se> <282DBA30-FDCA-47EF-825A-7B44EA47C897@gmail.com>
To: Margaret Wasserman <margaretw42@gmail.com>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/_SmTPK3teCG1-7SqpfcndeWDVFU>
Cc: Ray Bellis <Ray.Bellis@nominet.org.uk>, "homenet@ietf.org Group" <homenet@ietf.org>, Markus Stenberg <markus.stenberg@iki.fi>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] Implementations of IS-IS [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 16 Feb 2015 15:57:35 -0000

On 16.2.2015, at 17.16, Margaret Wasserman <margaretw42@gmail.com> =
wrote:
> You have mentioned that Babel is "in OpenWRT" or something along those =
lines=85  Is the version with source-specific routing included in =
OpenWRT yet?  If not, what is the process by which that will be included =
in an OpenWRT release?

It is - in routing feed, there is both traditional, as well as =
source-specific Babel version package. I assume this will go away once =
source-specific code shows up in the next main release.

> How many commercial router vendors have it enabled in their products?  =
Is it being used on any operational networks.  [BTW, for the person who =
asked elsewhere "operational network"  means "a network that is =
currently working to allow people do real work, not just to test your =
software", it doesn't mean that the network is managed or involves an =
"operator".  The Verizon network in my home is quite "operational", as =
is the one here at my hotel.

If you use that wide =91operational=92 definition, almost any routing =
daemon ever written (minus AutoISIS perhaps) is in (for some definition) =
wide operational use.

Very few people write them just for fun and never use them. I believe =
whole Babel effort started =91operational=92, using that definition.. I =
am not sure if the meaningful is useful if it is really that broad.=20

Cheers,

-Markus

P.S. I have babels (source-specific OpenWrt package) in operational use.


From nobody Mon Feb 16 07:58:55 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 E653A1A700B for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 07:58:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.15
X-Spam-Level: *
X-Spam-Status: No, score=1.15 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_EQ_FR=0.35] autolearn=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 mQuhlI5jjGIt for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 07:58:51 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 58FE61A1BF2 for <homenet@ietf.org>; Mon, 16 Feb 2015 07:58:51 -0800 (PST)
Received: from potemkin.univ-paris7.fr (potemkin.univ-paris7.fr [IPv6:2001:660:3301:8000::1:1]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t1GFwnt7014787 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 16 Feb 2015 16:58:49 +0100
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by potemkin.univ-paris7.fr (8.14.4/8.14.4/relay2/56228) with ESMTP id t1GFwn0p031895; Mon, 16 Feb 2015 16:58:49 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 045B22BF928; Mon, 16 Feb 2015 16:58:49 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id 1bGMqsQxJz32; Mon, 16 Feb 2015 16:58:46 +0100 (CET)
Received: from pirx.pps.jussieu.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id B85952BF926; Mon, 16 Feb 2015 16:58:46 +0100 (CET)
Date: Mon, 16 Feb 2015 16:58:46 +0100
Message-ID: <87bnkt3l1l.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Margaret Wasserman <margaretw42@gmail.com>
In-Reply-To: <282DBA30-FDCA-47EF-825A-7B44EA47C897@gmail.com>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <8041EA49-EB50-491B-A3C4-B25FAB52C8FC@iki.fi> <alpine.DEB.2.02.1502161024030.4007@uplift.swm.pp.se> <87twym2fh0.wl-jch@pps.univ-paris-diderot.fr> <FAE12FF5-6EFF-4D2B-A6EE-2435F647706F@nominet.org.uk> <alpine.DEB.2.02.1502161429130.4007@uplift.swm.pp.se> <282DBA30-FDCA-47EF-825A-7B44EA47C897@gmail.com>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]); Mon, 16 Feb 2015 16:58:49 +0100 (CET)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Mon, 16 Feb 2015 16:58:49 +0100 (CET)
X-Miltered: at korolev with ID 54E213B9.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 54E213B9.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54E213B9.000 from potemkin.univ-paris7.fr/potemkin.univ-paris7.fr/null/potemkin.univ-paris7.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Enveloppe: 54E213B9.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54E213B9.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 54E213B9.000 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/sOkpUOLGcHvLGioPJL4j_dDShwk>
Cc: Ray Bellis <Ray.Bellis@nominet.org.uk>, "homenet@ietf.org Group" <homenet@ietf.org>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] Implementations of IS-IS [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 16 Feb 2015 15:58:54 -0000

> You keep mentioning that Quagga is "alpha quality" but i am not sure that
> provides any pertinent information.

Oh, sorry if I wasn't clear.  Quagga has excellent, production quality
implementations of OSPF, RIPv2 and BGP, and a simplistic but workable
implementation of RIPng.  On the other hand, their IS-IS documentation
says:

    isisd is ALPHA quality at the moment and hasn't any way ready for  pro-
    duction use.

    isisd eats bugs for breakfast. If you have food for the maintainers try
    http://bugzilla.quagga.net

> If I understood correctly, you mentioned in a private thread that the
> Quagga IS-IS codebase is not being maintained right now.  Is that correct?

According to their commit history, the last significant changes date from
November 2012.  Of course, it is possible that work is being done out of
tree, perhaps David can clarify.

> When you add features, such as source specific routing, to your Babel
> codebase, do you go through a full formal release process with Alpha, Beta
> and Production versions?

Significant new features live in a separate branch, usually for months or
even years.  They are carefully reviewed, then merged into trunk.  After
they've had some time to (not) break, I make a release.

For example, the RTT-based metric was implemented by Baptiste Jonglez
during the summer of 2013.  It was exhaustively tested, and almost
completely rewritten in November 2013.  It was carefully reviewed by
myself in April-May 2014, and merged into trunk on 16 May 2014.  It was
further tweaked by both Baptiste and myself, all the tests were redone,
and it was released as babeld 1.5.0 on 22 May 2014.  So that took almost
a year, notwithstanding the friendly bullying by the company who wanted
the feature (no, they don't pay me, and I'm not under NDA; full disclaimer:
they bought me lunch once).

Similarly, the source-specific extension was first implemented by Matthieu
Boutier in the spring of 2013, then extensively modified.  We have been
doing serious testing since early 2014.  I've started systematically
reviewing his patches in the summer of 2014 (which involved some changes
to the data structures, Matthieu wasn't pleased), but then I ran out of
time.  I've set aside some time in February to finish the merge, at which
point I plan to let it simmer for a few weeks before releasing 1.6.0.

> You have mentioned that Babel is "in OpenWRT" or something along those
> linesâ€¦ Is the version with source-specific routing included in OpenWRT
> yet?

Yes, in the package babels, which is separate from the mainline babeld
package.  Users have been complaining about this situation, which is why
I need to finish the merge as soon as I have the necessary peace of mind.

> what is the process by which that will be included in an OpenWRT release?

After I release babeld-1.6.0, hopefully in early March, Gabriel Kerneis
will include it in OpenWRT (he usually does so within a couple of days)
and StÃ©phane Glondu will include it in Debian (he usually takes longer).
At that point, we'll discuss on babel-users whether we want to delete the
OpenWRT babels package, or make a dummy package to ease the transition,
and Gabriel will make the final decision.

> How many commercial router vendors have it enabled in their products?

None, as far as I'm aware.  It is widely available for researchers to
experiment with, and is enabled by default in CeroWRT.

I hope that this clarifies things, please do not hesitate to tell me if
you feel that I make claims that are not backed by hard data.

-- Juliusz


From nobody Mon Feb 16 08:13:50 2015
Return-Path: <markus.stenberg@iki.fi>
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 103091A8915 for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 08:13:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.121
X-Spam-Level: 
X-Spam-Status: No, score=-1.121 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_NEUTRAL=0.779] autolearn=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 W1VSYYpUsrBY for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 08:13:43 -0800 (PST)
Received: from kirsi2.inet.fi (mta-out1.inet.fi [62.71.2.227]) by ietfa.amsl.com (Postfix) with ESMTP id 5C6091A88AF for <homenet@ietf.org>; Mon, 16 Feb 2015 08:11:41 -0800 (PST)
Received: from poro.lan (80.220.64.126) by kirsi2.inet.fi (8.5.142.08) (authenticated as stenma-47) id 54C8EEAE0035C591; Mon, 16 Feb 2015 18:11:38 +0200
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Markus Stenberg <markus.stenberg@iki.fi>
In-Reply-To: <C6504EC1-3F29-419B-88E4-6EB96BA9CE67@iki.fi>
Date: Mon, 16 Feb 2015 18:11:36 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <9B9204F4-BB31-4158-AFE0-088584029039@iki.fi>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <8041EA49-EB50-491B-A3C4-B25FAB52C8FC@iki.fi> <alpine.DEB.2.02.1502161024030.4007@uplift.swm.pp.se> <87twym2fh0.wl-jch@pps.univ-paris-diderot.fr> <FAE12FF5-6EFF-4D2B-A6EE-2435F647706F@nominet.org.uk> <alpine.DEB.2.02.1502161429130.4007@uplift.swm.pp.se> <282DBA30-FDCA-47EF-825A-7B44EA47C897@gmail.com> <C6504EC1-3F29-419B-88E4-6EB96BA9CE67@iki.fi>
To: Margaret Wasserman <margaretw42@gmail.com>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/MmabDyfRQNn-AdawkgjYB6fKs10>
Cc: Ray Bellis <Ray.Bellis@nominet.org.uk>, "homenet@ietf.org Group" <homenet@ietf.org>, Markus Stenberg <markus.stenberg@iki.fi>, Mikael Abrahamsson <swmike@swm.pp.se>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] Implementations of IS-IS [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 16 Feb 2015 16:13:49 -0000

On 16.2.2015, at 17.57, Markus Stenberg <markus.stenberg@iki.fi> wrote:
> If you use that wide =91operational=92 definition, almost any routing =
daemon ever written (minus AutoISIS perhaps) is in (for some definition) =
wide operational use.
>=20
> Very few people write them just for fun and never use them. I believe =
whole Babel effort started =91operational=92, using that definition.. I =
am not sure if the meaningful is useful if it is really that broad.=20

Argh. =91meaning is useful=92 is what I planned to type, sorry for spam. =
At any rate, 15.3.1 definition is then rather suspicious as it says =
essentially only =91widely used=92 (and =91wildly successful=92 and =
other earlier related claims seem to stress that point too).

As Mikael says, the number of homenet WG installations is 0 right now, =
and it remains to be seen what is wildly successful there.

Cheers,

-Markus=


From nobody Mon Feb 16 10:09:19 2015
Return-Path: <gert@Space.Net>
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 EA9A81A1DBC for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 10:09:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.61
X-Spam-Level: 
X-Spam-Status: No, score=-2.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 F9OcpYbDUghE for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 10:08:53 -0800 (PST)
Received: from mobil.space.net (mobil.space.net [195.30.115.67]) (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 0E4D41A6EFB for <homenet@ietf.org>; Mon, 16 Feb 2015 10:08:50 -0800 (PST)
X-Original-To: homenet@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id B059160182 for <homenet@ietf.org>; Mon, 16 Feb 2015 19:08:48 +0100 (CET)
X-SpaceNet-Relay: true
Received: from moebius3.space.net (moebius3.Space.Net [IPv6:2001:608:2:2::250]) by mobil.space.net (Postfix) with ESMTPS id 79A4C60102 for <homenet@ietf.org>; Mon, 16 Feb 2015 19:08:48 +0100 (CET)
Received: (qmail 18488 invoked by uid 1007); 16 Feb 2015 19:08:48 +0100
Date: Mon, 16 Feb 2015 19:08:48 +0100
From: Gert Doering <gert@space.net>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Message-ID: <20150216180848.GN34798@Space.Net>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <8041EA49-EB50-491B-A3C4-B25FAB52C8FC@iki.fi> <alpine.DEB.2.02.1502161024030.4007@uplift.swm.pp.se> <87twym2fh0.wl-jch@pps.univ-paris-diderot.fr> <FAE12FF5-6EFF-4D2B-A6EE-2435F647706F@nominet.org.uk> <alpine.DEB.2.02.1502161429130.4007@uplift.swm.pp.se> <20150216143431.GK34798@Space.Net> <87fva53net.wl-jch@pps.univ-paris-diderot.fr>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Lf5sCh8FbX4wWn6w"
Content-Disposition: inline
In-Reply-To: <87fva53net.wl-jch@pps.univ-paris-diderot.fr>
X-NCC-RegID: de.space
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/b5R6K0R_cpj5haCKriKCXjktXl0>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Gert Doering <gert@space.net>
Subject: Re: [homenet] Implementations of IS-IS
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 16 Feb 2015 18:09:11 -0000

--Lf5sCh8FbX4wWn6w
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi,

On Mon, Feb 16, 2015 at 04:07:38PM +0100, Juliusz Chroboczek wrote:
> > Out of interest: how is ISIS done on "Linuxish" devices?  Grabbing=20
> > ISIS packets off the link with libpcap?
>=20
> The Erlang version uses a PF_PACKET, SOCK_RAW socket.
>=20
> The alpha Quagga version appears to have three implementations:
>=20
>   - on Linux, it uses a PF_PACKET, SOCK_DGRAM socket;

I was aware that you can use that to *send* raw frames, but didn't know
you could use that to receive as well (done via joining the [ethernet]
multicast groups).

Interesting.

thanks,

Gert Doering
        -- NetMaster
--=20
have you enabled IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444           USt-IdNr.: DE813185279

--Lf5sCh8FbX4wWn6w
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIVAwUBVOIyMN9WwGXkzn/FAQKKqRAAqs6Wlj8ay+ft0vrOJ+qAz/e8yaiSwDAF
kneqoOJFUpLRzHJLUiUTRfcxi0Nej8FyaaNDvvMSaghDN+WEKFlgewY3vKoBtoZ1
9d2mp07K7WWzAVY1vLrjh8nKNdplO5v5JIxjPZRwdCY7Vhnf9jCaA6EEDqMVqsxE
RlgZl8n686GUhNrLf+hyVA0GpuqVd3OzE3FKkfpaHWmnVlavLNGsZbqikFgeojrj
k47/+56LRrgmXlOe7oeJrKw3xsDK35kq82j+nHE1Ke/oPXjOdBhzLFtpx+ROiyzE
6WElElgFX/Q/CzE4CZl257CxW6QGu+P3ICqyAwPB+FOqF+USlvXuGIGFryUgFClI
0zbolA9k4CvCBW/NGIvLwvej48OFB9uziPiqF0+hfdPcSnuY7YJcBLHdxVGscGZp
xOaSN7Nt2vDmnPJsbsA/4PaoIEI96SN73nuwlkLm1frP6cL3yKJCgmhEDKxUxUNi
0+rGZy8E7VM0g+cZwFB8m5TcZ1ZkppI2BjBrKFsBel2k/XYUc9SdxAbsigIxznHY
tJu7l95EmLp4XgQ2KtN0DGQWGpG8MRlzpaQPNJMAgiuews8WQtkzlWhEh5tit1aF
WpNw05hh4jouWtLLCW0j5MGkTPjAKzSjAMEpbmH8atbT8Cibp1U2Taf1FGkTnzr5
VabcypBnMek=
=u7L2
-----END PGP SIGNATURE-----

--Lf5sCh8FbX4wWn6w--


From nobody Mon Feb 16 10:27:33 2015
Return-Path: <cyrus@openwrt.org>
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 285B01A6F0A for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 10:27:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.25
X-Spam-Level: 
X-Spam-Status: No, score=-2.25 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-0.7] 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 brwDwF2txA7y for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 10:27:29 -0800 (PST)
Received: from mail.core-networks.de (mail.core-networks.de [82.96.72.7]) by ietfa.amsl.com (Postfix) with ESMTP id D300A1A6EDE for <homenet@ietf.org>; Mon, 16 Feb 2015 10:27:28 -0800 (PST)
Received: from localhost ([127.0.0.1]) by mail.core-networks.de id 1YNQOE-0002Wc-7U with ESMTPSA (TLSv1.2:DHE-RSA-AES128-SHA:128) for ; Mon, 16 Feb 2015 19:27:26 +0100
Message-ID: <54E2368C.7010603@openwrt.org>
Date: Mon, 16 Feb 2015 19:27:24 +0100
From: Steven Barth <cyrus@openwrt.org>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Gert Doering <gert@space.net>,  Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <8041EA49-EB50-491B-A3C4-B25FAB52C8FC@iki.fi> <alpine.DEB.2.02.1502161024030.4007@uplift.swm.pp.se> <87twym2fh0.wl-jch@pps.univ-paris-diderot.fr> <FAE12FF5-6EFF-4D2B-A6EE-2435F647706F@nominet.org.uk> <alpine.DEB.2.02.1502161429130.4007@uplift.swm.pp.se> <20150216143431.GK34798@Space.Net> <87fva53net.wl-jch@pps.univ-paris-diderot.fr> <20150216180848.GN34798@Space.Net>
In-Reply-To: <20150216180848.GN34798@Space.Net>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/tSZ4P0oxf4FIoJCSLrnJ_H20kNU>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Implementations of IS-IS
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 16 Feb 2015 18:27:31 -0000

> Out of interest: how is ISIS done on "Linuxish" devices? Grabbing ISIS 
> packets off the link with libpcap?
>> The Erlang version uses a PF_PACKET, SOCK_RAW socket.
>>
>> The alpha Quagga version appears to have three implementations:
>>
>>    - on Linux, it uses a PF_PACKET, SOCK_DGRAM socket;
> I was aware that you can use that to *send* raw frames, but didn't know
> you could use that to receive as well (done via joining the [ethernet]
> multicast groups).
libpcap is just the higher-level userspace interface to PF_PACKET on 
Linux. That said in any case you have to be a bit careful with PF_PACKET 
sockets and their settings especially if you use them to broadly (e.g. 
capture all L3 messages) your forwarding performance will go down even 
if you have a BPF-filter attached since the kernel has to copy / inspect 
a lot of packages.


From nobody Mon Feb 16 23:49:31 2015
Return-Path: <margaretw42@gmail.com>
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 483501A86E1 for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 23:49:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level: 
X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] 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 xDZNBRrRSxeg for <homenet@ietfa.amsl.com>; Mon, 16 Feb 2015 23:49:27 -0800 (PST)
Received: from mail-pa0-f47.google.com (mail-pa0-f47.google.com [209.85.220.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A3E3F1A020D for <homenet@ietf.org>; Mon, 16 Feb 2015 23:49:27 -0800 (PST)
Received: by padfb1 with SMTP id fb1so4461424pad.8 for <homenet@ietf.org>; Mon, 16 Feb 2015 23:49:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=u0SJCjbZxgNWKNvPO51qQfZ2zLdZZSgGeX0V6SRkArY=; b=WgEKhlAJXGJ5yURTnXeV/CeR91hBsSJi7sU3RJKUFkbhVihHWOoY6JHLt/6xzDMaQr rTrL4Bi7eBJ8IDVVv2HCQa1toZZmwIvx0PWN8GNXbz/sAZ0kfPX8wOV8Lyb6HeNDCgy1 4RFShs5PzBrnokFaTxLVvyBhpAKn/LiJuZI75fWMKmRiX9E9AJMlQy5k7210fxWBWFDN wrxKbJobu/gwgOwXbT5FrfhEEt7xgMxtn2r2WgLitcf7+1OMPQvKAiqV97MFOA2EO9pM fxoOGf5uuw2ZaIGhN+3jzQciNWJ+O3GofANmy3edr/fep4sAsOo5ojul5nPURRSzbIEm rxVg==
X-Received: by 10.68.136.137 with SMTP id qa9mr46500880pbb.127.1424159367349;  Mon, 16 Feb 2015 23:49:27 -0800 (PST)
Received: from [192.168.7.248] (wsip-24-248-179-54.ph.ph.cox.net. [24.248.179.54]) by mx.google.com with ESMTPSA id yf6sm16976019pab.26.2015.02.16.23.49.26 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 16 Feb 2015 23:49:26 -0800 (PST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Margaret Wasserman <margaretw42@gmail.com>
In-Reply-To: <87bnkt3l1l.wl-jch@pps.univ-paris-diderot.fr>
Date: Tue, 17 Feb 2015 02:49:25 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <66EB759E-6B62-42D4-B505-2A37BD6C2567@gmail.com>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <8041EA49-EB50-491B-A3C4-B25FAB52C8FC@iki.fi> <alpine.DEB.2.02.1502161024030.4007@uplift.swm.pp.se> <87twym2fh0.wl-jch@pps.univ-paris-diderot.fr> <FAE12FF5-6EFF-4D2B-A6EE-2435F647706F@nominet.org.uk> <alpine.DEB.2.02.1502161429130.4007@uplift.swm.pp.se> <282DBA30-FDCA-47EF-825A-7B44EA47C897@gmail.com> <87bnkt3l1l.wl-jch@pps.univ-paris-diderot.fr>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
X-Mailer: Apple Mail (2.1510)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/2vG131KBQr7HdF4wP1d_0sRii7k>
Cc: Ray Bellis <Ray.Bellis@nominet.org.uk>, "homenet@ietf.org Group" <homenet@ietf.org>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] Implementations of IS-IS [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Tue, 17 Feb 2015 07:49:30 -0000

Thanks, Juliusz.  This was very helpful to me in understanding the =
status of these implementations.

Margaret

On Feb 16, 2015, at 10:58 AM, Juliusz Chroboczek =
<jch@pps.univ-paris-diderot.fr> wrote:

>> You keep mentioning that Quagga is "alpha quality" but i am not sure =
that
>> provides any pertinent information.
>=20
> Oh, sorry if I wasn't clear.  Quagga has excellent, production quality
> implementations of OSPF, RIPv2 and BGP, and a simplistic but workable
> implementation of RIPng.  On the other hand, their IS-IS documentation
> says:
>=20
>    isisd is ALPHA quality at the moment and hasn't any way ready for  =
pro-
>    duction use.
>=20
>    isisd eats bugs for breakfast. If you have food for the maintainers =
try
>    http://bugzilla.quagga.net
>=20
>> If I understood correctly, you mentioned in a private thread that the
>> Quagga IS-IS codebase is not being maintained right now.  Is that =
correct?
>=20
> According to their commit history, the last significant changes date =
from
> November 2012.  Of course, it is possible that work is being done out =
of
> tree, perhaps David can clarify.
>=20
>> When you add features, such as source specific routing, to your Babel
>> codebase, do you go through a full formal release process with Alpha, =
Beta
>> and Production versions?
>=20
> Significant new features live in a separate branch, usually for months =
or
> even years.  They are carefully reviewed, then merged into trunk.  =
After
> they've had some time to (not) break, I make a release.
>=20
> For example, the RTT-based metric was implemented by Baptiste Jonglez
> during the summer of 2013.  It was exhaustively tested, and almost
> completely rewritten in November 2013.  It was carefully reviewed by
> myself in April-May 2014, and merged into trunk on 16 May 2014.  It =
was
> further tweaked by both Baptiste and myself, all the tests were =
redone,
> and it was released as babeld 1.5.0 on 22 May 2014.  So that took =
almost
> a year, notwithstanding the friendly bullying by the company who =
wanted
> the feature (no, they don't pay me, and I'm not under NDA; full =
disclaimer:
> they bought me lunch once).
>=20
> Similarly, the source-specific extension was first implemented by =
Matthieu
> Boutier in the spring of 2013, then extensively modified.  We have =
been
> doing serious testing since early 2014.  I've started systematically
> reviewing his patches in the summer of 2014 (which involved some =
changes
> to the data structures, Matthieu wasn't pleased), but then I ran out =
of
> time.  I've set aside some time in February to finish the merge, at =
which
> point I plan to let it simmer for a few weeks before releasing 1.6.0.
>=20
>> You have mentioned that Babel is "in OpenWRT" or something along =
those
>> lines=85 Is the version with source-specific routing included in =
OpenWRT
>> yet?
>=20
> Yes, in the package babels, which is separate from the mainline babeld
> package.  Users have been complaining about this situation, which is =
why
> I need to finish the merge as soon as I have the necessary peace of =
mind.
>=20
>> what is the process by which that will be included in an OpenWRT =
release?
>=20
> After I release babeld-1.6.0, hopefully in early March, Gabriel =
Kerneis
> will include it in OpenWRT (he usually does so within a couple of =
days)
> and St=E9phane Glondu will include it in Debian (he usually takes =
longer).
> At that point, we'll discuss on babel-users whether we want to delete =
the
> OpenWRT babels package, or make a dummy package to ease the =
transition,
> and Gabriel will make the final decision.
>=20
>> How many commercial router vendors have it enabled in their products?
>=20
> None, as far as I'm aware.  It is widely available for researchers to
> experiment with, and is enabled by default in CeroWRT.
>=20
> I hope that this clarifies things, please do not hesitate to tell me =
if
> you feel that I make claims that are not backed by hard data.
>=20
> -- Juliusz


From nobody Tue Feb 17 11:33:28 2015
Return-Path: <internet-drafts@ietf.org>
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 30F9F1A90A0; Tue, 17 Feb 2015 11:33:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 1-MxtJCX8cJB; Tue, 17 Feb 2015 11:33:25 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 771AB1A90AC; Tue, 17 Feb 2015 11:33:24 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.11.0.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150217193324.25368.88002.idtracker@ietfa.amsl.com>
Date: Tue, 17 Feb 2015 11:33:24 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/XQn6ENelF2hTz5TagLsKn1rHbHw>
Cc: homenet@ietf.org
Subject: [homenet] I-D Action: draft-ietf-homenet-naming-architecture-dhc-options-01.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Tue, 17 Feb 2015 19:33:27 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Home Networking Working Group of the IETF.

        Title           : DHCP Options for Homenet Naming Architecture
        Authors         : Daniel Migault
                          Wouter Cloetens
                          Chris Griffiths
                          Ralf Weber
	Filename        : draft-ietf-homenet-naming-architecture-dhc-options-01.txt
	Pages           : 28
	Date            : 2015-02-16

Abstract:
   CPEs are usually constraint devices with reduced network and CPU
   capacities.  As such, a CPE hosting on the Internet the authoritative
   naming service for its home network may become vulnerable to resource
   exhaustion attacks.  One way to avoid exposing CPE is to outsource
   the authoritative service to a third party.  This third party can be
   the ISP or any other independent third party.

   Outsourcing the authoritative naming service to a third party
   requires setting up an architecture which may be unappropriated for
   most end users.  To leverage this issue, this document proposes DHCP
   Options so any agnostic CPE can automatically proceed to the
   appropriated configuration and outsource the authoritative naming
   service for the home network.  This document shows that in most
   cases, these DHCP Options make outsourcing to a third party (be it
   the ISP or any ISP independent service provider) transparent for the
   end user.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-homenet-naming-architecture-dhc-options/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-homenet-naming-architecture-dhc-options-01

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-homenet-naming-architecture-dhc-options-01


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Tue Feb 17 11:36:27 2015
Return-Path: <internet-drafts@ietf.org>
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 D7D011A90BE; Tue, 17 Feb 2015 11:36:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 RNQKP-vudyBf; Tue, 17 Feb 2015 11:36:23 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 341591A90A9; Tue, 17 Feb 2015 11:36:23 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 5.11.0.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150217193623.25643.39237.idtracker@ietfa.amsl.com>
Date: Tue, 17 Feb 2015 11:36:23 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/1T7wCzEzMC2cEdkjZWBar8qY_YY>
Cc: homenet@ietf.org
Subject: [homenet] I-D Action: draft-ietf-homenet-front-end-naming-delegation-01.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Tue, 17 Feb 2015 19:36:25 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Home Networking Working Group of the IETF.

        Title           : Outsourcing Home Network Authoritative Naming Service
        Authors         : Daniel Migault
                          Wouter Cloetens
                          Chris Griffiths
                          Ralf Weber
	Filename        : draft-ietf-homenet-front-end-naming-delegation-01.txt
	Pages           : 25
	Date            : 2015-02-16

Abstract:
   CPEs are designed to provide IP connectivity to home networks.  Most
   CPEs assign IP addresses to the nodes of the home network which makes
   it a good candidate for hosting the naming service.  With IPv6, the
   naming service makes nodes reachable from the home network as well as
   from the Internet.

   However, CPEs have not been designed to host such a naming service
   exposed on the Internet.  This may expose the CPEs to resource
   exhaustion which would make the home network unreachable, and most
   probably would also affect the home network inner communications.

   In addition, DNSSEC management and configuration may not be well
   understood or mastered by regular end users.  Misconfiguration may
   also results in naming service disruption, thus these end users may
   prefer to rely on third party naming providers.

   This document describes a homenet naming architecture where the CPEs
   manage the DNS zone associates to its home network, and outsources
   the naming service and eventually the DNSSEC management on the
   Internet to a third party designated as the Public Authoritative
   Servers.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-homenet-front-end-naming-delegation/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-homenet-front-end-naming-delegation-01

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-homenet-front-end-naming-delegation-01


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Tue Feb 17 13:13:34 2015
Return-Path: <mglt.ietf@gmail.com>
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 5065A1A876C for <homenet@ietfa.amsl.com>; Tue, 17 Feb 2015 13:13:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 YyTUbUxa3K-n for <homenet@ietfa.amsl.com>; Tue, 17 Feb 2015 13:13:30 -0800 (PST)
Received: from mail-wg0-x235.google.com (mail-wg0-x235.google.com [IPv6:2a00:1450:400c:c00::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 09B0A1A1EF8 for <homenet@ietf.org>; Tue, 17 Feb 2015 13:13:30 -0800 (PST)
Received: by mail-wg0-f53.google.com with SMTP id a1so21938607wgh.12 for <homenet@ietf.org>; Tue, 17 Feb 2015 13:13:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=HInmnbG+B3Q1VbQCnCj336b8SVF5MIa5X0+C/9tGaR8=; b=v+Z/QKbJ9O9DxXnFdISNlaggTPElUAH256eyJisSS2awX7+LrNZgM5kBFzjvx3Dd1q yrWrZiwViztIzD+SZnpJNBGuEklmYn0IvVqByoNWPanJe6pwLf03pnG+YS1uK+SvuimV 50IQqxUiHAfSeUvTCcYM8vsv5cGhnO1JPJuhz43h1sJ828Khi0+0LMPgXOVxB8UPajbT gZjmG7+CveoOHdgR0H8YfmYcNTXaO5VA9oGeYupWrTIdied6VfB494BnqHaefhwabxCu eHBkDTfOSvNiaMx/zIKTooxlPVrN7Ec+KbI29F8gXkSpbk+YZEJQboQLDHigWUaTyjeY hFdA==
MIME-Version: 1.0
X-Received: by 10.194.192.167 with SMTP id hh7mr2128053wjc.151.1424207608787;  Tue, 17 Feb 2015 13:13:28 -0800 (PST)
Received: by 10.194.68.39 with HTTP; Tue, 17 Feb 2015 13:13:28 -0800 (PST)
In-Reply-To: <20150217193623.25643.39237.idtracker@ietfa.amsl.com>
References: <20150217193623.25643.39237.idtracker@ietfa.amsl.com>
Date: Tue, 17 Feb 2015 22:13:28 +0100
Message-ID: <CADZyTknzSqZwkBBqyabNkXoLpaawRv+=_4FFq77unvRYc6JKoA@mail.gmail.com>
From: Daniel Migault <mglt.ietf@gmail.com>
To: "homenet@ietf.org" <homenet@ietf.org>
Content-Type: multipart/alternative; boundary=047d7b8743f89bb704050f4f2c4a
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/j-uffyfyoK1AxL2kLbfFFJbSPPI>
Cc: Ralf Weber <Ralf.Weber@nominum.com>, Wouter Cloetens <wouter.cloetens@softathome.com>, Chris Griffiths <cgriffiths@dyn.com>
Subject: [homenet] Fwd: I-D Action: draft-ietf-homenet-front-end-naming-delegation-01.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Tue, 17 Feb 2015 21:13:33 -0000

--047d7b8743f89bb704050f4f2c4a
Content-Type: text/plain; charset=UTF-8

Hi,

Please find the new version of the Outsourcing Home Network Authoritative
Naming Service
<http://tools.ietf.org/html/draft-ietf-homenet-front-end-naming-delegation-01>.


We believed we addressed all comments we received through the list and off
list. By the way thanks to all those that provided feedbacks, and feel free
to provide more feed backs.

Here are the main modifications:

    - 1) We clarify how the CPE is involved in the DNS resolution and how
the home network requirements are met -- more specifically how naming
resolution inside the home network is provided even though IP connectivity
is down. Regarding this issues, we were in line with the received comments,
so the new version is mostly clarifying this aspect.

    - 2) A number of issues were related to names that are not expected to
be publish on the public Internet, and remain published only within the
home network. This includes link-local, site-local and NAT IP addresses as
well as Private domain names. As these requirements results in two
different views, a "private" and a "public" view we describe the problem
and provide guidance on how to deal with each of these cases in section 7
"handling on different views". I believe all raised issues so far have been
considered as discussed on the mailing list.

    - 3) A privacy section has been added. It exposes the privacy concerns
of outsourcing the DNS service.

    - 4) Text has been added on how reverse zone may be handled as an
alternative to the generation of an explicit reverse zone.

    - 5) We clarify the pro/con about outsourcing the zone signature
operation. The recommended way is clearly not to outsource it. This is the
recommendation running for a while now, so we hope the text is clear by
now. If not let us know.

    - 6) We clarify when needed when col-localization of the functions is
needed. More specifically, when two functions needs to run on the same
hardware. Such considerations only happened outside the master/slave
architecture.

    - 7) RFC2308 has been added for the SOA


BR,
Daniel

---------- Forwarded message ----------
From: <internet-drafts@ietf.org>
Date: Tue, Feb 17, 2015 at 8:36 PM
Subject: [homenet] I-D Action:
draft-ietf-homenet-front-end-naming-delegation-01.txt
To: i-d-announce@ietf.org
Cc: homenet@ietf.org



A New Internet-Draft is available from the on-line Internet-Drafts
directories.
 This draft is a work item of the Home Networking Working Group of the IETF.

        Title           : Outsourcing Home Network Authoritative Naming
Service
        Authors         : Daniel Migault
                          Wouter Cloetens
                          Chris Griffiths
                          Ralf Weber
        Filename        :
draft-ietf-homenet-front-end-naming-delegation-01.txt
        Pages           : 25
        Date            : 2015-02-16

Abstract:
   CPEs are designed to provide IP connectivity to home networks.  Most
   CPEs assign IP addresses to the nodes of the home network which makes
   it a good candidate for hosting the naming service.  With IPv6, the
   naming service makes nodes reachable from the home network as well as
   from the Internet.

   However, CPEs have not been designed to host such a naming service
   exposed on the Internet.  This may expose the CPEs to resource
   exhaustion which would make the home network unreachable, and most
   probably would also affect the home network inner communications.

   In addition, DNSSEC management and configuration may not be well
   understood or mastered by regular end users.  Misconfiguration may
   also results in naming service disruption, thus these end users may
   prefer to rely on third party naming providers.

   This document describes a homenet naming architecture where the CPEs
   manage the DNS zone associates to its home network, and outsources
   the naming service and eventually the DNSSEC management on the
   Internet to a third party designated as the Public Authoritative
   Servers.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-homenet-front-end-naming-delegation/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-homenet-front-end-naming-delegation-01

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-homenet-front-end-naming-delegation-01


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
homenet mailing list
homenet@ietf.org
https://www.ietf.org/mailman/listinfo/homenet



-- 
Daniel Migault
Ericsson

--047d7b8743f89bb704050f4f2c4a
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi, <br><br>Please find the new version of the <a hre=
f=3D"http://tools.ietf.org/html/draft-ietf-homenet-front-end-naming-delegat=
ion-01">Outsourcing Home Network Authoritative Naming Service</a>. <br><br>=
We believed we addressed all comments we received through the list and off =
list. By the way thanks to all those that provided feedbacks, and feel free=
 to provide more feed backs.<br><br>Here are the main modifications:<br><br=
></div><div>=C2=A0=C2=A0=C2=A0 - 1) We clarify how the CPE is involved in t=
he DNS resolution and how the home network requirements are met -- more spe=
cifically how naming resolution inside the home network is provided even th=
ough IP connectivity is down. Regarding this issues, we were in line with t=
he received comments, so the new version is mostly clarifying this aspect.<=
br><br></div><div>=C2=A0=C2=A0=C2=A0 - 2) A number of issues were related t=
o names that are not expected to be publish on the public Internet, and rem=
ain published only within the home network. This includes link-local, site-=
local and NAT IP addresses as well as Private domain names. As these requir=
ements results in two different views, a &quot;private&quot; and a &quot;pu=
blic&quot; view we describe the problem and provide guidance on how to deal=
 with each of these cases in section 7 &quot;handling on different views&qu=
ot;. I believe all raised issues so far have been considered as discussed o=
n the mailing list.<br><br></div><div>=C2=A0=C2=A0=C2=A0 - 3) A privacy sec=
tion has been added. It exposes the privacy concerns of outsourcing the DNS=
 service.<br><br></div><div>=C2=A0=C2=A0=C2=A0 - 4) Text has been added on =
how reverse zone may be handled as an alternative to the generation of an e=
xplicit reverse zone.<br><br></div><div>=C2=A0 =C2=A0 - 5) We clarify the p=
ro/con about outsourcing the zone signature operation. The recommended way =
is clearly not to outsource it. This is the recommendation running for a wh=
ile now, so we hope the text is clear by now. If not let us know.<br><br></=
div><div>=C2=A0 =C2=A0 - 6) We clarify when needed when col-localization of=
 the functions is needed. More specifically, when two functions needs to ru=
n on the same hardware. Such considerations only happened outside the maste=
r/slave architecture.<br><br>=C2=A0=C2=A0=C2=A0 - 7) RFC2308 has been added=
 for the SOA<br></div><br><div><br></div><div>BR, <br></div><div>Daniel<br>=
</div><div><div><br><div class=3D"gmail_quote">---------- Forwarded message=
 ----------<br>From: <b class=3D"gmail_sendername"></b> <span dir=3D"ltr">&=
lt;<a href=3D"mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</a>=
&gt;</span><br>Date: Tue, Feb 17, 2015 at 8:36 PM<br>Subject: [homenet] I-D=
 Action: draft-ietf-homenet-front-end-naming-delegation-01.txt<br>To: <a hr=
ef=3D"mailto:i-d-announce@ietf.org">i-d-announce@ietf.org</a><br>Cc: <a hre=
f=3D"mailto:homenet@ietf.org">homenet@ietf.org</a><br><br><br><br>
A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.<br>
=C2=A0This draft is a work item of the Home Networking Working Group of the=
 IETF.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 Outsourcing Home Network Authoritative Naming Service<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Authors=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: Dani=
el Migault<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 Wouter Cloetens<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 Chris Griffiths<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 Ralf Weber<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Filename=C2=A0 =C2=A0 =C2=A0 =C2=A0 : draft-iet=
f-homenet-front-end-naming-delegation-01.txt<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Pages=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 25<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Date=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 :=
 2015-02-16<br>
<br>
Abstract:<br>
=C2=A0 =C2=A0CPEs are designed to provide IP connectivity to home networks.=
=C2=A0 Most<br>
=C2=A0 =C2=A0CPEs assign IP addresses to the nodes of the home network whic=
h makes<br>
=C2=A0 =C2=A0it a good candidate for hosting the naming service.=C2=A0 With=
 IPv6, the<br>
=C2=A0 =C2=A0naming service makes nodes reachable from the home network as =
well as<br>
=C2=A0 =C2=A0from the Internet.<br>
<br>
=C2=A0 =C2=A0However, CPEs have not been designed to host such a naming ser=
vice<br>
=C2=A0 =C2=A0exposed on the Internet.=C2=A0 This may expose the CPEs to res=
ource<br>
=C2=A0 =C2=A0exhaustion which would make the home network unreachable, and =
most<br>
=C2=A0 =C2=A0probably would also affect the home network inner communicatio=
ns.<br>
<br>
=C2=A0 =C2=A0In addition, DNSSEC management and configuration may not be we=
ll<br>
=C2=A0 =C2=A0understood or mastered by regular end users.=C2=A0 Misconfigur=
ation may<br>
=C2=A0 =C2=A0also results in naming service disruption, thus these end user=
s may<br>
=C2=A0 =C2=A0prefer to rely on third party naming providers.<br>
<br>
=C2=A0 =C2=A0This document describes a homenet naming architecture where th=
e CPEs<br>
=C2=A0 =C2=A0manage the DNS zone associates to its home network, and outsou=
rces<br>
=C2=A0 =C2=A0the naming service and eventually the DNSSEC management on the=
<br>
=C2=A0 =C2=A0Internet to a third party designated as the Public Authoritati=
ve<br>
=C2=A0 =C2=A0Servers.<br>
<br>
<br>
The IETF datatracker status page for this draft is:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-homenet-front-end-na=
ming-delegation/" target=3D"_blank">https://datatracker.ietf.org/doc/draft-=
ietf-homenet-front-end-naming-delegation/</a><br>
<br>
There&#39;s also a htmlized version available at:<br>
<a href=3D"http://tools.ietf.org/html/draft-ietf-homenet-front-end-naming-d=
elegation-01" target=3D"_blank">http://tools.ietf.org/html/draft-ietf-homen=
et-front-end-naming-delegation-01</a><br>
<br>
A diff from the previous version is available at:<br>
<a href=3D"http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-homenet-front-end-=
naming-delegation-01" target=3D"_blank">http://www.ietf.org/rfcdiff?url2=3D=
draft-ietf-homenet-front-end-naming-delegation-01</a><br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at <a href=3D"http://tool=
s.ietf.org" target=3D"_blank">tools.ietf.org</a>.<br>
<br>
Internet-Drafts are also available by anonymous FTP at:<br>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/" target=3D"_blank">ftp://ftp=
.ietf.org/internet-drafts/</a><br>
<br>
_______________________________________________<br>
homenet mailing list<br>
<a href=3D"mailto:homenet@ietf.org">homenet@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/homenet" target=3D"_blank"=
>https://www.ietf.org/mailman/listinfo/homenet</a><br>
</div><br><br clear=3D"all"><br>-- <br><div class=3D"gmail_signature"><div =
dir=3D"ltr"><div>Daniel Migault<br></div><div>Ericsson</div></div></div>
</div></div></div>

--047d7b8743f89bb704050f4f2c4a--


From nobody Tue Feb 17 18:22:53 2015
Return-Path: <mglt.ietf@gmail.com>
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 37D6E1A6F27 for <homenet@ietfa.amsl.com>; Tue, 17 Feb 2015 18:22:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] 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 FA6h2fg6WMhm for <homenet@ietfa.amsl.com>; Tue, 17 Feb 2015 18:22:50 -0800 (PST)
Received: from mail-we0-f172.google.com (mail-we0-f172.google.com [74.125.82.172]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ED4B01A9237 for <homenet@ietf.org>; Tue, 17 Feb 2015 18:22:48 -0800 (PST)
Received: by wesx3 with SMTP id x3so1975691wes.6 for <homenet@ietf.org>; Tue, 17 Feb 2015 18:22:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=HedYJ5cNGgMA5lRxGFpPmvQaz0qD27UpIPmlNIkR4E0=; b=YSSImL3tDUeLFFsTykHdXE+VeresOFoveBa5pOJQQlzPfIAG40JpnHv/xuPnirJ3PM KQOyepG4J5Ss8GR0FZ+//tIclPVnVOuZwUjoNnXLU3OZsAUAVGCuR7Wpy1Yz3FZi1T8R RIYPGA6Y08PLLznoN+K87x2q5o1gFfVwcpJuzgZg6JGQimpAPqmC91nXTDHqDMXWLrEN ZdiIT7V7VYS1bbhulVw8/aKCqKdTsMPlNUZNcEGQAnGd9ucYVzu1sWMVfDGkqeq4PyCh izmaSJq69LSvVC8XpYlnB6cEfwTQ4iWcg6LhwUYXksPC/sAmnZdEYQm7QRRKcysVH7kA 96mA==
MIME-Version: 1.0
X-Received: by 10.180.11.205 with SMTP id s13mr364105wib.32.1424226167496; Tue, 17 Feb 2015 18:22:47 -0800 (PST)
Received: by 10.194.68.39 with HTTP; Tue, 17 Feb 2015 18:22:47 -0800 (PST)
In-Reply-To: <20150217193324.25368.88002.idtracker@ietfa.amsl.com>
References: <20150217193324.25368.88002.idtracker@ietfa.amsl.com>
Date: Wed, 18 Feb 2015 03:22:47 +0100
Message-ID: <CADZyTknR_5Csm+gD_BbtNtKYxdycuikeyHt+cxMuqWw3fHvdkQ@mail.gmail.com>
From: Daniel Migault <mglt.ietf@gmail.com>
To: "homenet@ietf.org" <homenet@ietf.org>
Content-Type: multipart/alternative; boundary=001a11c23eeecb25d1050f537e9c
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/beC7qhi-kneAEdfQ2RUrzt_Moqs>
Subject: [homenet] Fwd: I-D Action: draft-ietf-homenet-naming-architecture-dhc-options-01.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Wed, 18 Feb 2015 02:22:52 -0000

--001a11c23eeecb25d1050f537e9c
Content-Type: text/plain; charset=UTF-8

Hi,

Please find the new version of DHCP Options for Homenet Naming Architecture
<https://datatracker.ietf.org/doc/draft-ietf-homenet-naming-architecture-dhc-options/>
.

The issue raised on the previous version was how these options were
compatible with multiple ISPs. This use case is illustrated in section A. 4
multiple ISPs.

BR,
Daniel


---------- Forwarded message ----------
From: <internet-drafts@ietf.org>
Date: Tue, Feb 17, 2015 at 8:33 PM
Subject: [homenet] I-D Action:
draft-ietf-homenet-naming-architecture-dhc-options-01.txt
To: i-d-announce@ietf.org
Cc: homenet@ietf.org



A New Internet-Draft is available from the on-line Internet-Drafts
directories.
 This draft is a work item of the Home Networking Working Group of the IETF.

        Title           : DHCP Options for Homenet Naming Architecture
        Authors         : Daniel Migault
                          Wouter Cloetens
                          Chris Griffiths
                          Ralf Weber
        Filename        :
draft-ietf-homenet-naming-architecture-dhc-options-01.txt
        Pages           : 28
        Date            : 2015-02-16

Abstract:
   CPEs are usually constraint devices with reduced network and CPU
   capacities.  As such, a CPE hosting on the Internet the authoritative
   naming service for its home network may become vulnerable to resource
   exhaustion attacks.  One way to avoid exposing CPE is to outsource
   the authoritative service to a third party.  This third party can be
   the ISP or any other independent third party.

   Outsourcing the authoritative naming service to a third party
   requires setting up an architecture which may be unappropriated for
   most end users.  To leverage this issue, this document proposes DHCP
   Options so any agnostic CPE can automatically proceed to the
   appropriated configuration and outsource the authoritative naming
   service for the home network.  This document shows that in most
   cases, these DHCP Options make outsourcing to a third party (be it
   the ISP or any ISP independent service provider) transparent for the
   end user.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-homenet-naming-architecture-dhc-options/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-homenet-naming-architecture-dhc-options-01

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-homenet-naming-architecture-dhc-options-01


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
homenet mailing list
homenet@ietf.org
https://www.ietf.org/mailman/listinfo/homenet



-- 
Daniel Migault
Ericsson

--001a11c23eeecb25d1050f537e9c
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div><div>Hi, <br><br></div>Please find the new versi=
on of <a href=3D"https://datatracker.ietf.org/doc/draft-ietf-homenet-naming=
-architecture-dhc-options/">DHCP Options for Homenet Naming Architecture</a=
>.<br></div><br>The issue raised on the previous version was how these opti=
ons were compatible with multiple ISPs. This use case is illustrated in sec=
tion A. 4 multiple ISPs.<br><br></div>BR, <br>Daniel<br><div><div><br><br><=
div><div><div class=3D"gmail_quote">---------- Forwarded message ----------=
<br>From: <b class=3D"gmail_sendername"></b> <span dir=3D"ltr">&lt;<a href=
=3D"mailto:internet-drafts@ietf.org" target=3D"_blank">internet-drafts@ietf=
.org</a>&gt;</span><br>Date: Tue, Feb 17, 2015 at 8:33 PM<br>Subject: [home=
net] I-D Action: draft-ietf-homenet-naming-architecture-dhc-options-01.txt<=
br>To: <a href=3D"mailto:i-d-announce@ietf.org" target=3D"_blank">i-d-annou=
nce@ietf.org</a><br>Cc: <a href=3D"mailto:homenet@ietf.org" target=3D"_blan=
k">homenet@ietf.org</a><br><br><br><br>
A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.<br>
=C2=A0This draft is a work item of the Home Networking Working Group of the=
 IETF.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 DHCP Options for Homenet Naming Architecture<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Authors=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: Dani=
el Migault<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 Wouter Cloetens<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 Chris Griffiths<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 Ralf Weber<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Filename=C2=A0 =C2=A0 =C2=A0 =C2=A0 : draft-iet=
f-homenet-naming-architecture-dhc-options-01.txt<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Pages=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0:=
 28<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Date=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 :=
 2015-02-16<br>
<br>
Abstract:<br>
=C2=A0 =C2=A0CPEs are usually constraint devices with reduced network and C=
PU<br>
=C2=A0 =C2=A0capacities.=C2=A0 As such, a CPE hosting on the Internet the a=
uthoritative<br>
=C2=A0 =C2=A0naming service for its home network may become vulnerable to r=
esource<br>
=C2=A0 =C2=A0exhaustion attacks.=C2=A0 One way to avoid exposing CPE is to =
outsource<br>
=C2=A0 =C2=A0the authoritative service to a third party.=C2=A0 This third p=
arty can be<br>
=C2=A0 =C2=A0the ISP or any other independent third party.<br>
<br>
=C2=A0 =C2=A0Outsourcing the authoritative naming service to a third party<=
br>
=C2=A0 =C2=A0requires setting up an architecture which may be unappropriate=
d for<br>
=C2=A0 =C2=A0most end users.=C2=A0 To leverage this issue, this document pr=
oposes DHCP<br>
=C2=A0 =C2=A0Options so any agnostic CPE can automatically proceed to the<b=
r>
=C2=A0 =C2=A0appropriated configuration and outsource the authoritative nam=
ing<br>
=C2=A0 =C2=A0service for the home network.=C2=A0 This document shows that i=
n most<br>
=C2=A0 =C2=A0cases, these DHCP Options make outsourcing to a third party (b=
e it<br>
=C2=A0 =C2=A0the ISP or any ISP independent service provider) transparent f=
or the<br>
=C2=A0 =C2=A0end user.<br>
<br>
<br>
The IETF datatracker status page for this draft is:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-homenet-naming-archi=
tecture-dhc-options/" target=3D"_blank">https://datatracker.ietf.org/doc/dr=
aft-ietf-homenet-naming-architecture-dhc-options/</a><br>
<br>
There&#39;s also a htmlized version available at:<br>
<a href=3D"http://tools.ietf.org/html/draft-ietf-homenet-naming-architectur=
e-dhc-options-01" target=3D"_blank">http://tools.ietf.org/html/draft-ietf-h=
omenet-naming-architecture-dhc-options-01</a><br>
<br>
A diff from the previous version is available at:<br>
<a href=3D"http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-homenet-naming-arc=
hitecture-dhc-options-01" target=3D"_blank">http://www.ietf.org/rfcdiff?url=
2=3Ddraft-ietf-homenet-naming-architecture-dhc-options-01</a><br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at <a href=3D"http://tool=
s.ietf.org" target=3D"_blank">tools.ietf.org</a>.<br>
<br>
Internet-Drafts are also available by anonymous FTP at:<br>
<a href=3D"ftp://ftp.ietf.org/internet-drafts/" target=3D"_blank">ftp://ftp=
.ietf.org/internet-drafts/</a><br>
<br>
_______________________________________________<br>
homenet mailing list<br>
<a href=3D"mailto:homenet@ietf.org" target=3D"_blank">homenet@ietf.org</a><=
br>
<a href=3D"https://www.ietf.org/mailman/listinfo/homenet" target=3D"_blank"=
>https://www.ietf.org/mailman/listinfo/homenet</a><br>
</div><br><br clear=3D"all"><br>-- <br><div><div dir=3D"ltr"><div>Daniel Mi=
gault<br></div><div>Ericsson</div></div></div>
</div></div></div></div></div>

--001a11c23eeecb25d1050f537e9c--


From nobody Wed Feb 18 04:45:29 2015
Return-Path: <v6ops@globis.net>
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 9CAC81A1A91 for <homenet@ietfa.amsl.com>; Wed, 18 Feb 2015 04:45:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 R3cwX520JvPI for <homenet@ietfa.amsl.com>; Wed, 18 Feb 2015 04:45:26 -0800 (PST)
Received: from globis01.globis.net (mail.globis.net [IPv6:2001:470:1f15:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id 6AA5A1A0158 for <homenet@ietf.org>; Wed, 18 Feb 2015 04:45:26 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id EB95C87161E for <homenet@ietf.org>; Wed, 18 Feb 2015 13:45:24 +0100 (CET)
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BojC83SCoHA1 for <homenet@ietf.org>; Wed, 18 Feb 2015 13:45:24 +0100 (CET)
Received: from Rays-iMac.local (092-111-140-211.static.chello.nl [92.111.140.211]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPSA id CA1E1870027 for <homenet@ietf.org>; Wed, 18 Feb 2015 13:45:24 +0100 (CET)
Message-ID: <54E48963.5030109@globis.net>
Date: Wed, 18 Feb 2015 13:45:23 +0100
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.11 (Macintosh/20140602)
MIME-Version: 1.0
To: "homenet@ietf.org Group" <homenet@ietf.org>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com>
In-Reply-To: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/30D8M-b_Oix0MqOvYYePpBxGEKw>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Wed, 18 Feb 2015 12:45:28 -0000

Mark Townsley wrote:
>
> Dear WG,
>
> In Hawaii, Margaret offered to pull together a document providing a 
> summary of ISIS and Babel within the context of homenet. Working with 
> Chris Hopps and Juliusz Chroboczek, Margaret just posted 
> draft-mrw-homenet-rtg-comparison-01.txt. Many thanks to all 3 authors 
> for this input, I'm sure it will help the WG make a more informed 
> decision.
>
> While there was a great deal of discussion and collaboration amongst 
> the authors, this document does not represent the authors' consensus 
> in its current form. This document is not intended to make a final 
> recommendation one way or another at this time, rather it is a 
> starting point for those who want more information but do not want to 
> dive into the entire repertoire of documents (or code) for ISIS or Babel.
>
> As such, I would like to invite everyone to use this as a starting 
> point to familiarize yourselves with these two options. State your 
> questions, comments, and opinions with at as much lively debate as we 
> heard at the microphone and in the hallways in Hawaii.
>
> Thank you,
>
> - Mark
>
>
I have read this draft, as well as the WG discussion up until 18/2. 
Thanks to the authors for compiling this document.

I think there are still several clarification/improvement points to be 
made, even if we assume that this draft will never be published/serve as 
a useful reference beyond the life of the WG.

Section 4. seems to be largely irrelevant as currently written as far as 
I can see.

What would interest me more is whether there is a practical difference 
in behaviour given an unstable link in the Homenet network e.g. a 
powerline link that suffers from interference and bounces regularly.

Does IS IS behave differently to Babel when one link is unstable in the 
Homenet?

Is the forwarding freeze during link-state calculation at all 
significant, given the claimed convergence times?

Is there a significant difference in the (native) detection of neighbor 
down between the two protocols?

Or do they rely heavily on interface/link/carrier down?

I also don't currently see anything about interfaces to low power devices.

Is there a significant difference between Babel and IS IS behaviour in a 
completely stable network, especially with respect to battery life?

Section 12.

 >  The code size of IS-IS depends greatly on what aspects of the 
protocol have been implemented.


When talking about IS IS, I'm not entirely sure what we would be 
importing into Homenet if we did a #include IS-IS , and also what 
incompatibilities that might generate given multiple implementations 
with varying feature sets.

This comment has already been raised by others and I agree it requires 
further clarification. Exactly which feature set of IS IS are we talking 
about?

I also think there should also be more explicit links back into the 
Homenet Architecture document 
https://datatracker.ietf.org/doc/rfc7368/?include_text=1.

Especially section 3.5 where we agreed requirements for the routing 
protocol.

Perhaps a table with "complies" "does not comply" or "partially 
complies" per paragraph or phrase?


I'd also be interested in reading about the practicality of my 
smartphone being able to participate as a (stub) Homenet router. I think 
that's a nice use case for "running code."

Would I need to jailbreak my phone to be able to load IS IS? or Babel? 
Especially re: access to operating system APIs?

If it's not there today, how difficult would it be for a 3rd party App 
Developer to build such a solution?

Or would users have to depend on the phone manufacturer incorporating 
Homenet out of the shrink wrap?

-- 
Regards,
RayH


From nobody Wed Feb 18 06:19:37 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 351D51A8932 for <homenet@ietfa.amsl.com>; Wed, 18 Feb 2015 06:19:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.15
X-Spam-Level: 
X-Spam-Status: No, score=-0.15 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, HELO_EQ_FR=0.35] autolearn=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 NsPSAADHFN8t for <homenet@ietfa.amsl.com>; Wed, 18 Feb 2015 06:19:33 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 1115B1A8797 for <homenet@ietf.org>; Wed, 18 Feb 2015 06:19:32 -0800 (PST)
Received: from potemkin.univ-paris7.fr (potemkin.univ-paris7.fr [IPv6:2001:660:3301:8000::1:1]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t1IEJUJv002848 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 18 Feb 2015 15:19:30 +0100
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by potemkin.univ-paris7.fr (8.14.4/8.14.4/relay2/56228) with ESMTP id t1IEJUbQ005227; Wed, 18 Feb 2015 15:19:30 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 2FC682C0477; Wed, 18 Feb 2015 15:19:30 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id tLroT7KwIgy6; Wed, 18 Feb 2015 15:19:28 +0100 (CET)
Received: from pirx.pps.jussieu.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 6F3D02C0479; Wed, 18 Feb 2015 15:19:28 +0100 (CET)
Date: Wed, 18 Feb 2015 15:19:28 +0100
Message-ID: <874mqj715b.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Ray Hunter <v6ops@globis.net>
In-Reply-To: <54E48963.5030109@globis.net>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]); Wed, 18 Feb 2015 15:19:30 +0100 (CET)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Wed, 18 Feb 2015 15:19:30 +0100 (CET)
X-Miltered: at korolev with ID 54E49F72.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 54E49F72.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54E49F72.001 from potemkin.univ-paris7.fr/potemkin.univ-paris7.fr/null/potemkin.univ-paris7.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Enveloppe: 54E49F72.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54E49F72.001 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 54E49F72.000 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/5jdvjILWize04EBXoy68kPqv19U>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Wed, 18 Feb 2015 14:19:35 -0000

> I also think there should also be more explicit links back into the
> Homenet Architecture document
[...]
> Perhaps a table with "complies" "does not comply" or "partially complies"
> per paragraph or phrase?

Good point.  Here's a quick reading of Section 3.5 of RFC 7368:

  - border discovery: out of scope, done by HNCP.

  - self configuring: yes for both, see Section 5.

  - behaviour during reconfiguration/reconvergence:
     - both protocols are able to route IPv6 before they get an address;
     - Babel will avoid creating loops even when reconverging, but might
       create blackholes; IS-IS will collapse during reconvergence;
     - HNCP doesn't depend on unicast, so it's not impacted by routing
       reconvergence; however, the loops created by IS-IS might create
       enough wireless interference to impact the performance of HNCP.
    This could be a useful addition to Section 4.

  - the homenet routing protocol should be based on a previously deployed
    protocol: IS-IS is more widely deployed in carrier networks, Babel is
    more widely deployed in small networks.  As for the source-specific
    extensions, only the Babel implementation has seen deployment.

  - v4 support: both protocols are double-stack.

  - only Babel is able to deal intelligently with multiple link
    technologies.  This argues for expansion of Section 7.

  - multihoming support: yes for both, see Section 6.

  - LLNs and other non-transit networks: a tiny stub implementation of
    Babel is available.  It is not known whether a small stub-only
    implementation of IS-IS is possible (I think it isn't -- an IS-IS
    router must participate in reliable flooding, and must perform SPF).
    This argues for expansion of Section 8.

-- Juliusz


From nobody Wed Feb 18 06:21:36 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 D78ED1A8835 for <homenet@ietfa.amsl.com>; Wed, 18 Feb 2015 06:21:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35] autolearn=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 rMoNjGTOriIS for <homenet@ietfa.amsl.com>; Wed, 18 Feb 2015 06:21:34 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 ADFBC1A87F0 for <homenet@ietf.org>; Wed, 18 Feb 2015 06:21:33 -0800 (PST)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t1IELVh8004265; Wed, 18 Feb 2015 15:21:31 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 133282C0477; Wed, 18 Feb 2015 15:21:31 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id yQuB739eIwoW; Wed, 18 Feb 2015 15:21:29 +0100 (CET)
Received: from pirx.pps.jussieu.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 628642C046B; Wed, 18 Feb 2015 15:21:29 +0100 (CET)
Date: Wed, 18 Feb 2015 15:21:29 +0100
Message-ID: <873863711y.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Daniel Migault <mglt.ietf@gmail.com>
In-Reply-To: <CADZyTknzSqZwkBBqyabNkXoLpaawRv+=_4FFq77unvRYc6JKoA@mail.gmail.com>
References: <20150217193623.25643.39237.idtracker@ietfa.amsl.com> <CADZyTknzSqZwkBBqyabNkXoLpaawRv+=_4FFq77unvRYc6JKoA@mail.gmail.com>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Wed, 18 Feb 2015 15:21:31 +0100 (CET)
X-Miltered: at korolev with ID 54E49FEB.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54E49FEB.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54E49FEB.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/g-6MWeUDWjVj2wnxtCaYzYJS_Fs>
Cc: "homenet@ietf.org" <homenet@ietf.org>, Wouter Cloetens <wouter.cloetens@softathome.com>, Ralf Weber <Ralf.Weber@nominum.com>, Chris Griffiths <cgriffiths@dyn.com>
Subject: Re: [homenet] Fwd: I-D Action: draft-ietf-homenet-front-end-naming-delegation-01.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Wed, 18 Feb 2015 14:21:35 -0000

> Please find the new version of the Outsourcing Home Network Authoritative
> Naming Service.
>
> We believed we addressed all comments we received through the list and off
> list.

I'm a little confused.  One of the comments was about how the draft binds
the role of the authoritative hidden master to the CPE.  Perhaps I'm
missing something, but I have the impression that this version still makes
this co-location compulsory.

-- Juliusz


From nobody Wed Feb 18 06:28:34 2015
Return-Path: <acee@cisco.com>
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 B76BF1A87F0 for <homenet@ietfa.amsl.com>; Wed, 18 Feb 2015 06:28:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 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_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 l2q6u3KkD8Oc for <homenet@ietfa.amsl.com>; Wed, 18 Feb 2015 06:28:30 -0800 (PST)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A1D181A8797 for <homenet@ietf.org>; Wed, 18 Feb 2015 06:28:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2448; q=dns/txt; s=iport; t=1424269710; x=1425479310; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=k5JlPECwS0MvUApGxT7QYxvKBaWCnZQr3IcAX3J1/2Q=; b=f7dC9JdEId11kpB6amktbRPjXHjNgKVXG2xMzrxu2jcQsSgziMrmmZaU cs8zn8PTzejpzG9N1cVBgly/17aKVP/qAI74RbiH87H6ke261huTzaWRj Mh990PVFL51nV6UFg3upDldw9Y5NOPdtdHzd7WsjjmARX0nN1X51s+gqp Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0D0CwADoeRU/5JdJa1bgwZSWgTBbmAKhSdKAoEcQwEBAQEBAXyEDQEBAwEBAQFkBwsQAgEIDgQ0JwsXDgIEAQ0FiCcIDdI7AQEBAQEBAQEBAQEBAQEBAQEBAQEBEwSLD4Q7MweEKgWKFIUviTyKZogsIoNub4FEfwEBAQ
X-IronPort-AV: E=Sophos;i="5.09,602,1418083200"; d="scan'208";a="124703227"
Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by alln-iport-7.cisco.com with ESMTP; 18 Feb 2015 14:28:29 +0000
Received: from xhc-aln-x14.cisco.com (xhc-aln-x14.cisco.com [173.36.12.88]) by rcdn-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id t1IESTdV012992 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 18 Feb 2015 14:28:29 GMT
Received: from xmb-aln-x06.cisco.com ([169.254.1.175]) by xhc-aln-x14.cisco.com ([173.36.12.88]) with mapi id 14.03.0195.001; Wed, 18 Feb 2015 08:28:29 -0600
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>, Ray Hunter <v6ops@globis.net>
Thread-Topic: [homenet] Routing protocol comparison document
Thread-Index: AQHQS3jCzCpCWpppzEK6EAHeEyOLf5z22XIA//+usgA=
Date: Wed, 18 Feb 2015 14:28:29 +0000
Message-ID: <D10A0AA4.EA4F%acee@cisco.com>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr>
In-Reply-To: <874mqj715b.wl-jch@pps.univ-paris-diderot.fr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.116.152.197]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <949231678AB208488F1F7EE80CF91FCC@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/CTx5DTVOvITZGpCpZPZnI195tTU>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Wed, 18 Feb 2015 14:28:32 -0000

On 2/18/15, 9:19 AM, "Juliusz Chroboczek" <jch@pps.univ-paris-diderot.fr>
wrote:

>> I also think there should also be more explicit links back into the
>> Homenet Architecture document
>[...]
>> Perhaps a table with "complies" "does not comply" or "partially
>>complies"
>> per paragraph or phrase?
>
>Good point.  Here's a quick reading of Section 3.5 of RFC 7368:
>
>  - border discovery: out of scope, done by HNCP.
>
>  - self configuring: yes for both, see Section 5.
>
>  - behaviour during reconfiguration/reconvergence:
>     - both protocols are able to route IPv6 before they get an address;
>     - Babel will avoid creating loops even when reconverging, but might
>       create blackholes; IS-IS will collapse during reconvergence;

I would say the IS-IS will create micro-loops and blackholes during
reconvergence. I wouldn=B9t say it would =B3collapse=B2. Note that these is=
sues
have been addressed with extensions in SP networks but I=B9m not sure we
should consider this for the homenet discussion. Also, I=B9d point out that
ISIS would converge extremely fast in smaller networks.



>     - HNCP doesn't depend on unicast, so it's not impacted by routing
>       reconvergence; however, the loops created by IS-IS might create
>       enough wireless interference to impact the performance of HNCP.
>    This could be a useful addition to Section 4.
>
>  - the homenet routing protocol should be based on a previously deployed
>    protocol: IS-IS is more widely deployed in carrier networks, Babel is
>    more widely deployed in small networks.  As for the source-specific
>    extensions, only the Babel implementation has seen deployment.
>
>  - v4 support: both protocols are double-stack.
>
>  - only Babel is able to deal intelligently with multiple link
>    technologies.  This argues for expansion of Section 7.
>
>  - multihoming support: yes for both, see Section 6.
>
>  - LLNs and other non-transit networks: a tiny stub implementation of
>    Babel is available.  It is not known whether a small stub-only
>    implementation of IS-IS is possible (I think it isn't -- an IS-IS
>    router must participate in reliable flooding, and must perform SPF).
>    This argues for expansion of Section 8.
>
>-- Juliusz
>
>_______________________________________________
>homenet mailing list
>homenet@ietf.org
>https://www.ietf.org/mailman/listinfo/homenet


From nobody Wed Feb 18 06:53:01 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 89FF71A892C for <homenet@ietfa.amsl.com>; Wed, 18 Feb 2015 06:52:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.349
X-Spam-Level: 
X-Spam-Status: No, score=0.349 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HELO_EQ_FR=0.35] autolearn=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 VpUPzbOgffSd for <homenet@ietfa.amsl.com>; Wed, 18 Feb 2015 06:52:58 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 1CEBE1A87A1 for <homenet@ietf.org>; Wed, 18 Feb 2015 06:52:57 -0800 (PST)
Received: from potemkin.univ-paris7.fr (potemkin.univ-paris7.fr [IPv6:2001:660:3301:8000::1:1]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t1IEqrW2024933 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 18 Feb 2015 15:52:53 +0100
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by potemkin.univ-paris7.fr (8.14.4/8.14.4/relay2/56228) with ESMTP id t1IEqq1P025053; Wed, 18 Feb 2015 15:52:52 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id C99F82C0486; Wed, 18 Feb 2015 15:52:52 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id 3tkbNf_F6ENl; Wed, 18 Feb 2015 15:52:46 +0100 (CET)
Received: from pirx.pps.jussieu.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id B1A7D2C047C; Wed, 18 Feb 2015 15:52:46 +0100 (CET)
Date: Wed, 18 Feb 2015 15:52:46 +0100
Message-ID: <87zj8b5l1d.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: "Acee Lindem (acee)" <acee@cisco.com>
In-Reply-To: <D10A0AA4.EA4F%acee@cisco.com>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <D10A0AA4.EA4F%acee@cisco.com>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]); Wed, 18 Feb 2015 15:52:53 +0100 (CET)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Wed, 18 Feb 2015 15:52:52 +0100 (CET)
X-Miltered: at korolev with ID 54E4A745.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 54E4A744.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54E4A745.000 from potemkin.univ-paris7.fr/potemkin.univ-paris7.fr/null/potemkin.univ-paris7.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Enveloppe: 54E4A744.001 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54E4A745.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 54E4A744.001 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/s9FeW6YJ7ZcL8i-84YyQLNDlG3M>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: [homenet] IS-IS reconvergence over WiFi [was: Routing protocol comparison]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Wed, 18 Feb 2015 14:52:59 -0000

>> - Babel will avoid creating loops even when reconverging, but might
>> create blackholes; IS-IS will collapse during reconvergence;

> I would say the IS-IS will create micro-loops and blackholes during
> reconvergence. I wouldn¹t say it would ³collapse². Note that these issues
> have been addressed with extensions in SP networks but I¹m not sure we
> should consider this for the homenet discussion. Also, I¹d point out that
> ISIS would converge extremely fast in smaller networks.

On wired networks, that's certainly true -- IS-IS and OSPF don't need to
guarantee good behaviour during reconvergence, since the combination of
stable links with a reliable flooding protocol gives high probability
bounds on reconvergence time.

Is there any experimental data that measures the behaviour of IS-IS's
reliable multicast subprotocol over the 802.11 MAC, in the presence of
marginal links?  Recall that 802.11 multicast is unprotected by ARQ, and
that excessive distributed traffic may cause beaconing to fail, causing
stations to disassiociate.

FWIW, I've had some unpleasant surprises with earlier versions of Babel
causing the 802.11 MAC to collapse for minutes (!) after a major network
disruption (rebooting the whole network simultaneously).  Fixing that
particular issue involved making reconvergence less aggressive, which of
course harmed convergence speed on wired links (which I don't care
about -- anything converges fast enough on Ethernet).  Granted, that was
in IBSS mode, infra mode probably behaves better.

-- Juliusz


From nobody Wed Feb 18 07:04:33 2015
Return-Path: <acee@cisco.com>
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 027FB1A916C for <homenet@ietfa.amsl.com>; Wed, 18 Feb 2015 07:04:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 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_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 FrDWahfi7vjq for <homenet@ietfa.amsl.com>; Wed, 18 Feb 2015 07:04:28 -0800 (PST)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 64B941A924A for <homenet@ietf.org>; Wed, 18 Feb 2015 07:04:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2924; q=dns/txt; s=iport; t=1424271855; x=1425481455; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=Azp8MRyqJEnnA167qt2qqN1CpURfH8/jEvJVYG3juEU=; b=acU30wTke1iVrwAnHh+AFy+ee/+daT7OacqWD7Ok9CQ9TAhWDG5m1pBR Gh1K6ZmS4k1VpMOvMOzZMqAzl6Yn9v5gEgye2I1gCzKxlOFcivbo+0nKN 42jYX5kFJ3a9cq3T3IWpfZN6Q6jMT35Znj7lkJnwZkA+zVcnwTORStSs4 E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ADDADIqORU/5tdJa1bgwaBLASDBL5qhlsCHIEAQwEBAQEBAXyEDQEBBDQ3DhACAQgODigCAjAlAgQOBYgvnTecZAaYMwEBAQEBAQEBAQEBAQEBAQEBAQEZgRuJdIQ7MweCYoFIBY9DiTyKZogsIoICHIFQb4FEfwEBAQ
X-IronPort-AV: E=Sophos;i="5.09,602,1418083200"; d="scan'208";a="124646113"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by alln-iport-8.cisco.com with ESMTP; 18 Feb 2015 15:04:14 +0000
Received: from xhc-rcd-x11.cisco.com (xhc-rcd-x11.cisco.com [173.37.183.85]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id t1IF4Ec8007577 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 18 Feb 2015 15:04:14 GMT
Received: from xmb-aln-x06.cisco.com ([169.254.1.175]) by xhc-rcd-x11.cisco.com ([173.37.183.85]) with mapi id 14.03.0195.001; Wed, 18 Feb 2015 09:04:14 -0600
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Thread-Topic: IS-IS reconvergence over WiFi [was: Routing protocol comparison]
Thread-Index: AQHQS4qVB7c6GPzStE+b0WkBVAdS8pz2kfwA
Date: Wed, 18 Feb 2015 15:04:14 +0000
Message-ID: <D10A12BF.EA90%acee@cisco.com>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <D10A0AA4.EA4F%acee@cisco.com> <87zj8b5l1d.wl-jch@pps.univ-paris-diderot.fr>
In-Reply-To: <87zj8b5l1d.wl-jch@pps.univ-paris-diderot.fr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.116.152.197]
Content-Type: text/plain; charset="euc-kr"
Content-ID: <A24981E19924BE44A579652E55AF288B@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/U3vhX_Bh87De1rS2vbMp1BjtDF0>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] IS-IS reconvergence over WiFi [was: Routing protocol comparison]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Wed, 18 Feb 2015 15:04:32 -0000

DQpPbiAyLzE4LzE1LCA5OjUyIEFNLCAiSnVsaXVzeiBDaHJvYm9jemVrIiA8amNoQHBwcy51bml2
LXBhcmlzLWRpZGVyb3QuZnI+DQp3cm90ZToNCg0KPj4+IC0gQmFiZWwgd2lsbCBhdm9pZCBjcmVh
dGluZyBsb29wcyBldmVuIHdoZW4gcmVjb252ZXJnaW5nLCBidXQgbWlnaHQNCj4+PiBjcmVhdGUg
YmxhY2tob2xlczsgSVMtSVMgd2lsbCBjb2xsYXBzZSBkdXJpbmcgcmVjb252ZXJnZW5jZTsNCj4N
Cj4+IEkgd291bGQgc2F5IHRoZSBJUy1JUyB3aWxsIGNyZWF0ZSBtaWNyby1sb29wcyBhbmQgYmxh
Y2tob2xlcyBkdXJpbmcNCj4+IHJlY29udmVyZ2VuY2UuIEkgd291bGRuqfZ0IHNheSBpdCB3b3Vs
ZCCp+GNvbGxhcHNlqfcuIE5vdGUgdGhhdCB0aGVzZQ0KPj5pc3N1ZXMNCj4+IGhhdmUgYmVlbiBh
ZGRyZXNzZWQgd2l0aCBleHRlbnNpb25zIGluIFNQIG5ldHdvcmtzIGJ1dCBJqfZtIG5vdCBzdXJl
IHdlDQo+PiBzaG91bGQgY29uc2lkZXIgdGhpcyBmb3IgdGhlIGhvbWVuZXQgZGlzY3Vzc2lvbi4g
QWxzbywgSan2ZCBwb2ludCBvdXQNCj4+dGhhdA0KPj4gSVNJUyB3b3VsZCBjb252ZXJnZSBleHRy
ZW1lbHkgZmFzdCBpbiBzbWFsbGVyIG5ldHdvcmtzLg0KPg0KPk9uIHdpcmVkIG5ldHdvcmtzLCB0
aGF0J3MgY2VydGFpbmx5IHRydWUgLS0gSVMtSVMgYW5kIE9TUEYgZG9uJ3QgbmVlZCB0bw0KPmd1
YXJhbnRlZSBnb29kIGJlaGF2aW91ciBkdXJpbmcgcmVjb252ZXJnZW5jZSwgc2luY2UgdGhlIGNv
bWJpbmF0aW9uIG9mDQo+c3RhYmxlIGxpbmtzIHdpdGggYSByZWxpYWJsZSBmbG9vZGluZyBwcm90
b2NvbCBnaXZlcyBoaWdoIHByb2JhYmlsaXR5DQo+Ym91bmRzIG9uIHJlY29udmVyZ2VuY2UgdGlt
ZS4NCj4NCj5JcyB0aGVyZSBhbnkgZXhwZXJpbWVudGFsIGRhdGEgdGhhdCBtZWFzdXJlcyB0aGUg
YmVoYXZpb3VyIG9mIElTLUlTJ3MNCj5yZWxpYWJsZSBtdWx0aWNhc3Qgc3VicHJvdG9jb2wgb3Zl
ciB0aGUgODAyLjExIE1BQywgaW4gdGhlIHByZXNlbmNlIG9mDQo+bWFyZ2luYWwgbGlua3M/ICBS
ZWNhbGwgdGhhdCA4MDIuMTEgbXVsdGljYXN0IGlzIHVucHJvdGVjdGVkIGJ5IEFSUSwgYW5kDQo+
dGhhdCBleGNlc3NpdmUgZGlzdHJpYnV0ZWQgdHJhZmZpYyBtYXkgY2F1c2UgYmVhY29uaW5nIHRv
IGZhaWwsIGNhdXNpbmcNCj5zdGF0aW9ucyB0byBkaXNhc3Npb2NpYXRlLg0KDQpJoa92ZSBvbmx5
IGhlYXJkIHRoZSBzdG9yaWVzIG9mIHRoZXNlIHByb2JsZW1zIGluIElFRUUgODAyLjExIG5ldHdv
cmtzLiBPbmUNCndvdWxkIGhvcGUgdGhhdCBiYXNpYyBtdWx0aWNhc3QgcHJvYmxlbXMgYXQgTGF5
ZXItMiB3b3VsZG6hr3QgcGVybWVhdGUgdXANCmludG8gdGhlIHJvdXRpbmcgcHJvdG9jb2yhpiAg
SGF2aW5nIHNhaWQgdGhhdCwgSSBrbm93IG9mIG5vIHN0YW5kYXJkDQpleHRlbnNpb25zIHRvIElT
SVMgdG8gYWRkcmVzcyB0aGlzIHByb2JsZW0uIEmhrnZlIGFsc28gaGVhcmQgdGhlcmUgYXJlDQpw
cm9wcmlldGFyeSBmaXhlcyB0aGF0IGhhdmVuoa90IG1hZGUgaXQgaW50byB0aGUgSUVFRSBzdGFu
ZGFyZHMgYnV0IGJ5IG5vDQptZWFucyBjbGFpbSB0byBiZSBhbiBleHBlcnQgaW4gdGhpcyBhcmVh
Lg0KDQpUaGFua3MsDQpBY2VlIA0KDQoNCj4NCj5GV0lXLCBJJ3ZlIGhhZCBzb21lIHVucGxlYXNh
bnQgc3VycHJpc2VzIHdpdGggZWFybGllciB2ZXJzaW9ucyBvZiBCYWJlbA0KPmNhdXNpbmcgdGhl
IDgwMi4xMSBNQUMgdG8gY29sbGFwc2UgZm9yIG1pbnV0ZXMgKCEpIGFmdGVyIGEgbWFqb3IgbmV0
d29yaw0KPmRpc3J1cHRpb24gKHJlYm9vdGluZyB0aGUgd2hvbGUgbmV0d29yayBzaW11bHRhbmVv
dXNseSkuICBGaXhpbmcgdGhhdA0KPnBhcnRpY3VsYXIgaXNzdWUgaW52b2x2ZWQgbWFraW5nIHJl
Y29udmVyZ2VuY2UgbGVzcyBhZ2dyZXNzaXZlLCB3aGljaCBvZg0KPmNvdXJzZSBoYXJtZWQgY29u
dmVyZ2VuY2Ugc3BlZWQgb24gd2lyZWQgbGlua3MgKHdoaWNoIEkgZG9uJ3QgY2FyZQ0KPmFib3V0
IC0tIGFueXRoaW5nIGNvbnZlcmdlcyBmYXN0IGVub3VnaCBvbiBFdGhlcm5ldCkuICBHcmFudGVk
LCB0aGF0IHdhcw0KPmluIElCU1MgbW9kZSwgaW5mcmEgbW9kZSBwcm9iYWJseSBiZWhhdmVzIGJl
dHRlci4NCj4NCj4tLSBKdWxpdXN6DQoNCg==


From nobody Wed Feb 18 07:07:14 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 792C31A89C6 for <homenet@ietfa.amsl.com>; Wed, 18 Feb 2015 07:07:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.15
X-Spam-Level: *
X-Spam-Status: No, score=1.15 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_EQ_FR=0.35] autolearn=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 2gw9ZS8eSHew for <homenet@ietfa.amsl.com>; Wed, 18 Feb 2015 07:07:11 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 048451A8835 for <homenet@ietf.org>; Wed, 18 Feb 2015 07:07:10 -0800 (PST)
Received: from potemkin.univ-paris7.fr (potemkin.univ-paris7.fr [IPv6:2001:660:3301:8000::1:1]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t1IF79Rv000714 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 18 Feb 2015 16:07:09 +0100
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by potemkin.univ-paris7.fr (8.14.4/8.14.4/relay2/56228) with ESMTP id t1IF79Nq032336; Wed, 18 Feb 2015 16:07:09 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 16E1D2C0488; Wed, 18 Feb 2015 16:07:09 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id EnvlOuTq4YF1; Wed, 18 Feb 2015 16:07:07 +0100 (CET)
Received: from pirx.pps.jussieu.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 13C4B2C0486; Wed, 18 Feb 2015 16:07:07 +0100 (CET)
Date: Wed, 18 Feb 2015 16:07:07 +0100
Message-ID: <87twyj5kdg.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Ray Hunter <v6ops@globis.net>
In-Reply-To: <54E48963.5030109@globis.net>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]); Wed, 18 Feb 2015 16:07:09 +0100 (CET)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Wed, 18 Feb 2015 16:07:09 +0100 (CET)
X-Miltered: at korolev with ID 54E4AA9D.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 54E4AA9D.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54E4AA9D.000 from potemkin.univ-paris7.fr/potemkin.univ-paris7.fr/null/potemkin.univ-paris7.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Enveloppe: 54E4AA9D.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54E4AA9D.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 54E4AA9D.000 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/o_wLfBrzleBuXXfu5Ci3lP5TL6I>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: [homenet] Homenet on smartphones [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Wed, 18 Feb 2015 15:07:12 -0000

> I'd also be interested in reading about the practicality of my smartphone
> being able to participate as a (stub) Homenet router.

Babel has been ported to Android, but most of the Android work is being
done with OLSR, notably within the Commotion Wireless project.

    https://commotionwireless.net/

There are two fundamental reasons why the Commotion software requires
a rooted phone, and only works on selected hardware:

  - manipulating the kernel's routing table requires being root;
  - stock Android doesn't support IBSS (ad-hoc) mode.

The latter point is hopefully not relevant to Homenet, but the former is
probably impossible to solve without action from Google.

-- Juliusz


From nobody Wed Feb 18 07:50:54 2015
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 960D61A8996 for <homenet@ietfa.amsl.com>; Wed, 18 Feb 2015 07:50:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.661
X-Spam-Level: 
X-Spam-Status: No, score=-1.661 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 TzBw-py15dK5 for <homenet@ietfa.amsl.com>; Wed, 18 Feb 2015 07:50:43 -0800 (PST)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 941521A8992 for <homenet@ietf.org>; Wed, 18 Feb 2015 07:50:43 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 7A4FAA2; Wed, 18 Feb 2015 16:50:40 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1424274640; bh=c4BAzIHyrRfxIhNihMHVld9vGtpVcBs13PXt/3cvpBo=; h=Date:From:To:Subject:In-Reply-To:References:From; b=w/gxyzMhn8C0x3/ECt2XbduYT28BEoxU/duaMGVpYj7ghEhZdL0KuAzwgyCFdA+tX dYNot9AE/78HbyP1KEmzw1FFhbaLXRiH4jdTzfD+2dmf8BriIyScg/a9i3b7GtIQT+ rkbR6ATmsEaVqxiHvo+aAtbkZq2cW8yfxgOG+tlk=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 7443FA1 for <homenet@ietf.org>; Wed, 18 Feb 2015 16:50:40 +0100 (CET)
Date: Wed, 18 Feb 2015 16:50:40 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: "homenet@ietf.org Group" <homenet@ietf.org>
In-Reply-To: <874mqj715b.wl-jch@pps.univ-paris-diderot.fr>
Message-ID: <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.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/cRIkaWYDbBx5kU14mhquvBaTZRA>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Wed, 18 Feb 2015 15:50:45 -0000

On Wed, 18 Feb 2015, Juliusz Chroboczek wrote:

>       create blackholes; IS-IS will collapse during reconvergence;

Collapse?

>  - LLNs and other non-transit networks: a tiny stub implementation of
>    Babel is available.  It is not known whether a small stub-only
>    implementation of IS-IS is possible (I think it isn't -- an IS-IS
>    router must participate in reliable flooding, and must perform SPF).
>    This argues for expansion of Section 8.

This is being investigated, I hope to have an answer by next week.

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


From nobody Wed Feb 18 08:13:42 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 4D26C1A899B for <homenet@ietfa.amsl.com>; Wed, 18 Feb 2015 08:13:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.349
X-Spam-Level: 
X-Spam-Status: No, score=0.349 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HELO_EQ_FR=0.35] autolearn=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 nWHEJk-6GGDb for <homenet@ietfa.amsl.com>; Wed, 18 Feb 2015 08:13:40 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 083271A8879 for <homenet@ietf.org>; Wed, 18 Feb 2015 08:13:29 -0800 (PST)
Received: from potemkin.univ-paris7.fr (potemkin.univ-paris7.fr [IPv6:2001:660:3301:8000::1:1]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t1IGDSRw010852 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 18 Feb 2015 17:13:28 +0100
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by potemkin.univ-paris7.fr (8.14.4/8.14.4/relay2/56228) with ESMTP id t1IGDSps005710; Wed, 18 Feb 2015 17:13:28 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 4687A2C05BC; Wed, 18 Feb 2015 17:13:28 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id RQd5z0cp4sbE; Wed, 18 Feb 2015 17:13:26 +0100 (CET)
Received: from pirx.pps.jussieu.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id B210A2C05B9; Wed, 18 Feb 2015 17:13:26 +0100 (CET)
Date: Wed, 18 Feb 2015 17:13:25 +0100
Message-ID: <87d2575hay.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Mikael Abrahamsson <swmike@swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]); Wed, 18 Feb 2015 17:13:28 +0100 (CET)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Wed, 18 Feb 2015 17:13:28 +0100 (CET)
X-Miltered: at korolev with ID 54E4BA28.002 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 54E4BA28.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54E4BA28.002 from potemkin.univ-paris7.fr/potemkin.univ-paris7.fr/null/potemkin.univ-paris7.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Enveloppe: 54E4BA28.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54E4BA28.002 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 54E4BA28.000 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/dn3hg8iZV1BdevVcd0sPKuJlawQ>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Wed, 18 Feb 2015 16:13:41 -0000

>> create blackholes; IS-IS will collapse during reconvergence;

> Collapse?

Okay.  I'll reformulate that.

I am not aware of any results in the open litterature that describe the
behaviour of single-area IS-IS during reconvergence.

I am not aware of any results in the open litterature that describe the
performance of IS-IS's reliable flooding, and hence its convergence speed,
over the 802.11 MAC in the presence of marginal links.

-- Juliusz


From nobody Wed Feb 18 08:20:05 2015
Return-Path: <gettysjim@gmail.com>
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 608B21A889C for <homenet@ietfa.amsl.com>; Wed, 18 Feb 2015 08:20:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level: 
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 n_cJbbUJa-pO for <homenet@ietfa.amsl.com>; Wed, 18 Feb 2015 08:20:02 -0800 (PST)
Received: from mail-ob0-x22d.google.com (mail-ob0-x22d.google.com [IPv6:2607:f8b0:4003:c01::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D68C51A1B07 for <homenet@ietf.org>; Wed, 18 Feb 2015 08:20:01 -0800 (PST)
Received: by mail-ob0-f173.google.com with SMTP id uy5so3812820obc.4 for <homenet@ietf.org>; Wed, 18 Feb 2015 08:20:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=uSVChgamt2XZvTf/rTirsKjfvMVFum4QtXoXVmmpzG8=; b=ZbYSFXRb7Un6RamAM+0CgjO+xK/SEEsOb94scZciw3WTjixPotpsC+KnYnDTC646pe KyA7JEEPC4bYyVcaf3NG8RrSiOe/odzwczHARPrjlcNoHE3PlXnPc4uEWG66xUd1kKja F4BNX8QcItMpr4i+SNcD4Gu/q/IpO/iZF+EsytreVLTeNuv3ZwXhUtBadlHuwXBQzS/h MCq+cXFo9tKIQeCFMQu+OBnni/R3XSeq7DBfIpJr0tnRzPvWPWv61tSLs1O5jtpatrQ7 93wKGqKU4f32vsh0FqYu+20BifTvtG7/1+xEdvdJtFFy+s59fd5yna8K/98hXYbShEoj jVIg==
MIME-Version: 1.0
X-Received: by 10.202.174.69 with SMTP id x66mr21263030oie.79.1424276401116; Wed, 18 Feb 2015 08:20:01 -0800 (PST)
Sender: gettysjim@gmail.com
Received: by 10.76.76.5 with HTTP; Wed, 18 Feb 2015 08:20:01 -0800 (PST)
In-Reply-To: <87d2575hay.wl-jch@pps.univ-paris-diderot.fr>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr>
Date: Wed, 18 Feb 2015 11:20:01 -0500
X-Google-Sender-Auth: KWohlzdim3Z-1i5YRbXD4hStnDA
Message-ID: <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com>
From: Jim Gettys <jg@freedesktop.org>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Content-Type: multipart/alternative; boundary=001a113ce962f3668d050f5f303a
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/xeBHOw8U366j7GCy01e80ATlfD8>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Wed, 18 Feb 2015 16:20:03 -0000

--001a113ce962f3668d050f5f303a
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Wed, Feb 18, 2015 at 11:13 AM, Juliusz Chroboczek <
jch@pps.univ-paris-diderot.fr> wrote:

> >> create blackholes; IS-IS will collapse during reconvergence;
>
> > Collapse?
>
> Okay.  I'll reformulate that.
>
> I am not aware of any results in the open litterature that describe the
> behaviour of single-area IS-IS during reconvergence.
>
> I am not aware of any results in the open litterature that describe the
> performance of IS-IS's reliable flooding, and hence its convergence speed=
,
> over the 802.11 MAC in the presence of marginal links.
>
>
=E2=80=8BNote that it is exactly collapse that =E2=80=8B
=E2=80=8Bworries me most (having seen it first hand, in the most extreme po=
ssible
way, in the 802.11s mesh we used at OLPC).=E2=80=8B  In that case, there wa=
s (maybe
still is) an N squared algorithmic issue in a "dense mesh", so scaling the
network up failed entirely at dismayingly few number of nodes.
                                                  - Jim

--001a113ce962f3668d050f5f303a
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
On Wed, Feb 18, 2015 at 11:13 AM, Juliusz Chroboczek <span dir=3D"ltr">&lt;=
<a href=3D"mailto:jch@pps.univ-paris-diderot.fr" target=3D"_blank">jch@pps.=
univ-paris-diderot.fr</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_q=
uote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e=
x"><span class=3D"">&gt;&gt; create blackholes; IS-IS will collapse during =
reconvergence;<br>
<br>
&gt; Collapse?<br>
<br>
</span>Okay.=C2=A0 I&#39;ll reformulate that.<br>
<br>
I am not aware of any results in the open litterature that describe the<br>
behaviour of single-area IS-IS during reconvergence.<br>
<br>
I am not aware of any results in the open litterature that describe the<br>
performance of IS-IS&#39;s reliable flooding, and hence its convergence spe=
ed,<br>
over the 802.11 MAC in the presence of marginal links.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br></font></span></blockquo=
te><div><br></div><div><div class=3D"gmail_default" style=3D"font-size:smal=
l;display:inline">=E2=80=8BNote that it is exactly collapse that =E2=80=8B<=
/div><div class=3D"gmail_default" style=3D"font-size:small;display:inline">=
=E2=80=8Bworries me most (having seen it first hand, in the most extreme po=
ssible way, in the 802.11s mesh we used at OLPC).=E2=80=8B =C2=A0In that ca=
se, there was (maybe still is) an N squared algorithmic issue in a &quot;de=
nse mesh&quot;, so scaling the network up failed entirely at dismayingly fe=
w number of nodes.</div></div><div><div class=3D"gmail_default" style=3D"fo=
nt-size:small;display:inline">=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 - Jim</div></div><d=
iv><div class=3D"gmail_default" style=3D"font-size:small;display:inline"><b=
r></div></div></div></div></div>

--001a113ce962f3668d050f5f303a--


From nobody Wed Feb 18 15:23:04 2015
Return-Path: <dave.taht@gmail.com>
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 A9C681A1B60 for <homenet@ietfa.amsl.com>; Wed, 18 Feb 2015 15:23:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.701
X-Spam-Level: 
X-Spam-Status: No, score=0.701 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 cNr0LcLtMpTI for <homenet@ietfa.amsl.com>; Wed, 18 Feb 2015 15:23:00 -0800 (PST)
Received: from mail-ob0-x233.google.com (mail-ob0-x233.google.com [IPv6:2607:f8b0:4003:c01::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7557F1A1B80 for <homenet@ietf.org>; Wed, 18 Feb 2015 15:23:00 -0800 (PST)
Received: by mail-ob0-f179.google.com with SMTP id wp4so8334350obc.10 for <homenet@ietf.org>; Wed, 18 Feb 2015 15:22:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=r+un/xvX9LEdJL+9sbuSn1xnl9BBg4eC6Cw9PZ1Mt2U=; b=GK39K5JPgyIo2q3S9A2/N5jRtTemahwk2t3W54GM/oLqrx+3mHxQlovRZDbvZAdMEU 6Hv5VWIqdDKmAgAsqVXfZtXjjIXoDmfG6azmb/0OhZJedmuXZ1knuFDj3+nwrui9c1ZP iF6nC3VUfdrvZSkBGIzmU7Wnd7pSqWgyRy2Xnldn1MXO6aXg+g2zCQXH7qmaFe6wlb7v gEGWQLYUvIP9+2iNH6v8ouVKe317bDjdZxDXEVA5WlCl3Lfw6/6WMxB6ahu+LnxgDMTG i8koLMaqoOUqoeFNE8ARFRcH83XlQto0P66stRMVloBCvyXgls58HsLYvQv55tnQlATu wIew==
MIME-Version: 1.0
X-Received: by 10.182.230.165 with SMTP id sz5mr1131519obc.29.1424301779824; Wed, 18 Feb 2015 15:22:59 -0800 (PST)
Received: by 10.202.51.66 with HTTP; Wed, 18 Feb 2015 15:22:59 -0800 (PST)
In-Reply-To: <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com>
Date: Wed, 18 Feb 2015 15:22:59 -0800
Message-ID: <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com>
From: Dave Taht <dave.taht@gmail.com>
To: Jim Gettys <jg@freedesktop.org>
Content-Type: multipart/alternative; boundary=001a11c3251ea3b501050f65195b
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/OtiOBYhaKVuEH5nmIdryrsINYAI>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Mikael Abrahamsson <swmike@swm.pp.se>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Wed, 18 Feb 2015 23:23:03 -0000

--001a11c3251ea3b501050f65195b
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I wanted to note that I embrace and endorse Juliusz=C2=B4s and Markus=C2=B4=
s comments
on this thread, and most of the rest of the discussion seems pretty
sensible.

Some random comments:

* I miss the days when rip was ubiquitous. When you needed a routing
protocol, you
generally *really* needed one, and being reduced to bridging everything is
a PITA.
Sure, rip sucked, but it was helpful to always have around.

* While ram and flash have grown to be essentially "free" I really dont see
home router and cpe makers rushing to embrace slower languages or bigger
flash
and memory requirements anytime soon.

Requiring Erlang in a router is a complete non starter for me. Proposing
java is almost palatable - a headless android, for example -
but these are devices that are presently struggling to forward packets at
speeds faster than 100mbit.

I incidentally happen to LIKE Erlang - hot patching is useful (and recently
entered the linux kernel itself). But the market has spoken here. (It also
seems to be speaking for the resurgence of c-replacement compiled languages
like rust and go - I was
amazed to see folk reimplementing coreutils in rust recently)

* There are other routing protocols out there - OLSR, already mentioned, is
popular, and there are others at layer 2, notably batman and 802.11s.

I would like *all* these routing protocols to gain support for source
specific
routing. It is a really worthy feature; it is really needed.

I have generally ruled out batman because it is A) linux-only and B) at
layer 2.

My experience, like jim=C2=B4s with 802.11s, was horrible, but for all I kn=
ow it
can be improved, and there is pretty general support for it out there. At
least some testing with 802.11s + another routing protocol connected to
ethernet connected to 802.14 would be sane.

* I, to this day, have never really got the whole link state argument. With
DV, if I want to know the topology, I do a traceroute.

* Moving forward, there are a couple concerns I would like to see
addressed, or declared out of scope. Maybe they already have, I honestly
havent been reading much homenet stuff for a year now. I got stuck on
waiting for hnetd to stablize before more fully rolling out source specific
routing than I have (3 exit nodes, not 6 as planned, and a hacky non-hnetd
solution for address distribution). I do plan a bigger deployment as part
of the make-wifi-fast project.

A) I would like, for one, to actually be able to use a routing protocol to
do multi-homing to multiple ISPs.

The advantages of BGP multi-homing for very large businesses are
undeniable, and I do dearly wish the same capabilities were available to
smaller business lacking the resources to obtain and manage an AS number,
but desiring to mitigate their risks of an internet outage. And there is an
advantage of having such an ability to the ISPs themselves - they net more
customers.

But I know I am dreaming.

B) Still non-discussed here is any sane interface to RPL or whatever the
IoT world is going to do if it doesnt just all jump on wifi. I really do
not know how that is going to go, I have now seen wifi enabled devices in
the 2 dollar range. Not that they have any room for even a babel stub.

C) I would like to see more corporate, and academic, and other ongoing
financial support dedicated to improving and maintaining the code.

The level of investment into the people working on core infrastructure like
quagga, babel, bird, ISIS, etc is pathetic. I am seeing a bit of an uptick
in things with the increased popularity of SDN (cumulus is doing some good
work), but still nothing even remotely close to the level of investment
into switching technologies like VXLANS and trill and so on.

If mainstream manufacturers such as d-link, netgear, etc, do not have
something useful and easy to deploy, they will continue to ignore homenet.

D) Certainly the IS-IS folk would be welcomed to try their stuff at the
upcoming battlemesh. The ospf people also. Under test there are OLSR,
batman, BMX, 802.11s, and static routing.

(There was recently some AWESOME work done on improving linux=C2=B4s fib ta=
ble
handling, btw.
https://plus.google.com/u/0/107942175615993706558/posts/aLHkUTqpzkR I am
dying to see the results on home routers)

I do keep hoping, with bake-offs like that, more resources poured into
getting it right, and more testing, that better metrics, techniques, and
code will emerge that make for clear winners among the protocols, and
across the various media types of concern. Thus consensus can be reached,
and world peace, achieved.

--001a11c3251ea3b501050f65195b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>I wanted to note that I embrace and endorse Juliusz=
=C2=B4s and Markus=C2=B4s comments<br>on this thread, and most of the rest =
of the discussion seems pretty sensible.<br><br>Some random comments:<br><b=
r>* I miss the days when rip was ubiquitous. When you needed a routing prot=
ocol, you<br>generally *really* needed one, and being reduced to bridging e=
verything is a PITA.<br>Sure, rip sucked, but it was helpful to always have=
 around.<br><br>* While ram and flash have grown to be essentially &quot;fr=
ee&quot; I really dont see<br>home router and cpe makers rushing to embrace=
 slower languages or bigger flash<br>and memory requirements anytime soon.<=
br><br>Requiring Erlang in a router is a complete non starter for me. Propo=
sing<br>java is almost palatable - a headless android, for example - <br>bu=
t these are devices that are presently struggling to forward packets at<br>=
speeds faster than 100mbit. <br><br></div>I incidentally happen to LIKE Erl=
ang - hot patching is useful (and recently<br>entered the linux kernel itse=
lf). But the market has spoken here. (It also<br>seems to be speaking for t=
he resurgence of c-replacement compiled languages like rust and go - I was<=
br>amazed to see folk reimplementing coreutils in rust recently) <br><div><=
br>* There are other routing protocols out there - OLSR, already mentioned,=
 is <br>popular, and there are others at layer 2, notably batman and 802.11=
s.<br><br>I would like *all* these routing protocols to gain support for so=
urce specific<br>routing. It is a really worthy feature; it is really neede=
d.<br><br>I have generally ruled out batman because it is A) linux-only and=
 B) at layer 2.<br><br>My experience, like jim=C2=B4s with 802.11s, was hor=
rible, but for all I know it can be improved, and there is pretty general s=
upport for it out there. At least some testing with 802.11s + another routi=
ng protocol connected to ethernet connected to 802.14 would be sane.<br><br=
>* I, to this day, have never really got the whole link state argument. Wit=
h DV, if I want to know the topology, I do a traceroute.<br><br>* Moving fo=
rward, there are a couple concerns I would like to see addressed, or declar=
ed out of scope. Maybe they already have, I honestly havent been reading mu=
ch homenet stuff for a year now. I got stuck on waiting for hnetd to stabli=
ze before more fully rolling out source specific routing than I have (3 exi=
t nodes, not 6 as planned, and a hacky non-hnetd solution for address distr=
ibution). I do plan a bigger deployment as part of the make-wifi-fast proje=
ct.<br><br>A) I would like, for one, to actually be able to use a routing p=
rotocol to do multi-homing to multiple ISPs.<br><br>The advantages of BGP m=
ulti-homing for very large businesses are undeniable, and I do dearly wish =
the same capabilities were available to smaller business lacking the resour=
ces to obtain and manage an AS number, but desiring to mitigate their risks=
 of an internet outage. And there is an advantage of having such an ability=
 to the ISPs themselves - they net more customers.<br><br>But I know I am d=
reaming.<br><br>B) Still non-discussed here is any sane interface to RPL or=
 whatever the IoT world is going to do if it doesnt just all jump on wifi. =
I really do not know how that is going to go, I have now seen wifi enabled =
devices in the 2 dollar range. Not that they have any room for even a babel=
 stub.<br><br>C) I would like to see more corporate, and academic, and othe=
r ongoing financial support dedicated to improving and maintaining the code=
.<br><br>The level of investment into the people working on core infrastruc=
ture like quagga, babel, bird, ISIS, etc is pathetic. I am seeing a bit of =
an uptick in things with the increased popularity of SDN (cumulus is doing =
some good work), but still nothing even remotely close to the level of inve=
stment into switching technologies like VXLANS and trill and so on.<br><br>=
</div><div>If mainstream manufacturers such as d-link, netgear, etc, do not=
 have something useful and easy to deploy, they will continue to ignore hom=
enet.<br></div><div><br>D) Certainly the IS-IS folk would be welcomed to tr=
y their stuff at the upcoming battlemesh. The ospf people also. Under test =
there are OLSR, batman, BMX, 802.11s, and static routing.<br><br>(There was=
 recently some AWESOME work done on improving linux=C2=B4s fib table handli=
ng, btw. <a href=3D"https://plus.google.com/u/0/107942175615993706558/posts=
/aLHkUTqpzkR">https://plus.google.com/u/0/107942175615993706558/posts/aLHkU=
TqpzkR</a> I am dying to see the results on home routers)<br><br>I do keep =
hoping, with bake-offs like that, more resources poured into getting it rig=
ht, and more testing, that better metrics, techniques, and code will emerge=
 that make for clear winners among the protocols, and across the various me=
dia types of concern. Thus consensus can be reached, and world peace, achie=
ved. <br></div></div>

--001a11c3251ea3b501050f65195b--


From nobody Wed Feb 18 22:27:08 2015
Return-Path: <mike@mtcc.com>
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 DBC4A1A6F0B for <homenet@ietfa.amsl.com>; Wed, 18 Feb 2015 22:27:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.112
X-Spam-Level: 
X-Spam-Status: No, score=-1.112 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 3ND0Vyq0AwB2 for <homenet@ietfa.amsl.com>; Wed, 18 Feb 2015 22:27:05 -0800 (PST)
Received: from mtcc.com (mtcc.com [50.0.18.224]) (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 5DC051A1F70 for <homenet@ietf.org>; Wed, 18 Feb 2015 22:27:05 -0800 (PST)
Received: from takifugu.mtcc.com (takifugu.mtcc.com [50.0.18.224]) (authenticated bits=0) by mtcc.com (8.14.7/8.14.7) with ESMTP id t1J6R40n008807 for <homenet@ietf.org>; Wed, 18 Feb 2015 22:27:04 -0800
Message-ID: <54E58238.9030809@mtcc.com>
Date: Wed, 18 Feb 2015 22:27:04 -0800
From: Michael Thomas <mike@mtcc.com>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: homenet@ietf.org
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com>
In-Reply-To: <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/4OMS3e6H2Ea3vaZnEAE3iHc_lDc>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 06:27:07 -0000

On 02/18/2015 03:22 PM, Dave Taht wrote:
> I wanted to note that I embrace and endorse Juliusz´s and Markus´s 
> comments
> on this thread, and most of the rest of the discussion seems pretty 
> sensible.
>
> Some random comments:
>
> * I miss the days when rip was ubiquitous. When you needed a routing 
> protocol, you
> generally *really* needed one, and being reduced to bridging 
> everything is a PITA.
> Sure, rip sucked, but it was helpful to always have around.
>
> * While ram and flash have grown to be essentially "free" I really 
> dont see
> home router and cpe makers rushing to embrace slower languages or 
> bigger flash
> and memory requirements anytime soon.
>
> Requiring Erlang in a router is a complete non starter for me. Proposing
> java is almost palatable - a headless android, for example -
> but these are devices that are presently struggling to forward packets at
> speeds faster than 100mbit.

Please, please make me a headless android router. I'll even write an app 
for it :)

But we're not talking about an interpreted language in the forwarding 
plane, right? Is the load
from routing protocols we're talking about likely to have any noticeable 
effect on the the forwarding
rate? even when you're running hot on the routing daemon side, you're 
not too likely to be running hot
on the forwarding side because something is hosed, right?

Mike, in the specific homenet context, of course


From nobody Wed Feb 18 23:43:33 2015
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 2BD381A88A3 for <homenet@ietfa.amsl.com>; Wed, 18 Feb 2015 23:43:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.361
X-Spam-Level: 
X-Spam-Status: No, score=-3.361 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, J_CHICKENPOX_31=0.6, 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 SJ4TdD5LNlo6 for <homenet@ietfa.amsl.com>; Wed, 18 Feb 2015 23:43:29 -0800 (PST)
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 92FF81A0059 for <homenet@ietf.org>; Wed, 18 Feb 2015 23:43:28 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 609A3A2; Thu, 19 Feb 2015 08:43:26 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1424331806; bh=SChntmwZJEbKH+W0OKD1U+a3WzChcbEKnXwkgQ8ffmU=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=mAeBPOY/zGpOB9CP6VOwqe7jZgfPO+M6st9c9rAfZEwdOzIEoVQg43nrooc2LBAWg UP9/akadXlrDzlcimVGlwfQdb7iNevdZFgfOPshJMKiReveJIzJ2BT8ckKUSK9XGI5 7PO0WLtrBDJHyx+eQAmjDlM3vaS+5W/CsDy/5epo=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 5A78DA1; Thu, 19 Feb 2015 08:43:26 +0100 (CET)
Date: Thu, 19 Feb 2015 08:43:26 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Dave Taht <dave.taht@gmail.com>
In-Reply-To: <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com>
Message-ID: <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="-137064504-1111862455-1424331806=:4007"
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/om_86Zuu0J3p4MIaeApvk1oHfsE>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 07:43:32 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

---137064504-1111862455-1424331806=:4007
Content-Type: TEXT/PLAIN; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8BIT

On Wed, 18 Feb 2015, Dave Taht wrote:

> * While ram and flash have grown to be essentially "free" I really dont 
> see home router and cpe makers rushing to embrace slower languages or 
> bigger flash and memory requirements anytime soon.

That's because there has been no requirement to do so, most of the time. 
Basically a device has been sold with a certain amount of features, and 
this featureset hasn't changed over time, thus there is no need to 
future-proof. I see this changing.

Also, currently most routers consists of mostly L2 high speed forwarding, 
with some L3 thrown in between two ports (the WAN port, and the 5th 
internal port to the 5 port switch chip with 4 external ports). With 
homenet, all this changes. Now all ports need to be L3. This is a huge 
change both when it comes to bandwidth needed from the CPU to the ports, 
and also L3 performance needed. This will require home gateway 
manufacturers to make very different devices.

We also have the (previous) mobile SOC:s trickling down into the home 
router space, and these are very price/performance efficient.

> Requiring Erlang in a router is a complete non starter for me. Proposing 
> java is almost palatable - a headless android, for example - but these 
> are devices that are presently struggling to forward packets at speeds 
> faster than 100mbit.

We're talking about a protocol decision here. People seem to focus a lot 
on the "running code" part here. ISIS is used for numerous things of apart 
frmo the MPLS and Traffic engineering space, we also have IEEE 802.1aq 
(SPB) and TRILL, it's also used in the GMPLS control plane. There are 
probably 10-20+ commercial implementations of ISIS, if not perhaps the 
exact TLVs we're talking about here. Most of not all of these standards 
are described in standards track RFCs.

Against this, we have Babel, which as far as I can tell has a single 
implementation that has been forked into two, and is based on a few 
experimental RFCs.

> I have generally ruled out batman because it is A) linux-only and B) at 
> layer 2.

What platforms do the current implementations of Babel support?

> My experience, like jimÂ´s with 802.11s, was horrible, but for all I know 
> it can be improved, and there is pretty general support for it out 
> there. At least some testing with 802.11s + another routing protocol 
> connected to ethernet connected to 802.14 would be sane.

Do we really believe people are going to use wifi links to connect devices 
within their homenet? Also, won't these be 5GHz and avoid a lot of the 
problems we've seen historically with Wifi? Also, don't we think IEEE will 
improve the behaviour of 802.11? It seems to me people are advocating for 
routing protocol selection based on yesteryears problems.

> * I, to this day, have never really got the whole link state argument. 
> With DV, if I want to know the topology, I do a traceroute.

That will give you the path there. That is not the same as topology. We 
need topology for some things, that's why HNCP is a "link state" protocol.

> A) I would like, for one, to actually be able to use a routing protocol 
> to do multi-homing to multiple ISPs.

That is already a requirement as far as I know.

> The advantages of BGP multi-homing for very large businesses are 
> undeniable, and I do dearly wish the same capabilities were available to 
> smaller business lacking the resources to obtain and manage an AS 
> number, but desiring to mitigate their risks of an internet outage. And 
> there is an advantage of having such an ability to the ISPs themselves - 
> they net more customers.
> But I know I am dreaming.

That is exactly what homenet is all about. You're not dreaming.

> C) I would like to see more corporate, and academic, and other ongoing 
> financial support dedicated to improving and maintaining the code.

What code? Routing protocol? Hnetd?

> The level of investment into the people working on core infrastructure 
> like quagga, babel, bird, ISIS, etc is pathetic. I am seeing a bit of an 
> uptick in things with the increased popularity of SDN (cumulus is doing 
> some good work), but still nothing even remotely close to the level of 
> investment into switching technologies like VXLANS and trill and so on.

The Erlang ISIS code is aimed also for this kind of market. I don't have 
details, but I've heard talk that it's also running on SDN kind of 
devices.

> D) Certainly the IS-IS folk would be welcomed to try their stuff at the 
> upcoming battlemesh. The ospf people also. Under test there are OLSR, 
> batman, BMX, 802.11s, and static routing.

Is the "wifi mesh" really the same thing as "homenet"? I'd say the 
requirements are vastly different.

> I do keep hoping, with bake-offs like that, more resources poured into 
> getting it right, and more testing, that better metrics, techniques, and 
> code will emerge that make for clear winners among the protocols, and 
> across the various media types of concern. Thus consensus can be 
> reached, and world peace, achieved.

My employer has so far been very supportive of these kinds of 
implementations. However, we want an extensible protocol (we want to use 
ISIS for more functionality than it's used for currently) and we need 
topology, so babel won't work for us.

I see homenet as primarily wired between the homenet routers. I don't 
believe in wifi for connecting different devices. People don't build 
mobile networks by using the mobile network to connect base stations. They 
use fiber or dedicated point-to-point highspeed microwave links to connect 
the base stations. If you want the homenet to work properly and 
efficiently, then the same thing applies here.

If people are making routing protocol decision based on the fact that they 
think most of the homenet links are going to be current incarnation of 
802.11, then we're lacking consensus on a lot wider range of requirements 
than just the routing protocol. We have different opinions on what homenet 
actually is and what it's going to look like.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se
---137064504-1111862455-1424331806=:4007--


From nobody Wed Feb 18 23:54:49 2015
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 826951A07BE for <homenet@ietfa.amsl.com>; Wed, 18 Feb 2015 23:54:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.661
X-Spam-Level: 
X-Spam-Status: No, score=-1.661 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 NX9aEavKZjDs for <homenet@ietfa.amsl.com>; Wed, 18 Feb 2015 23:54:46 -0800 (PST)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 632FC1A0059 for <homenet@ietf.org>; Wed, 18 Feb 2015 23:54:46 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id EDCE2A2; Thu, 19 Feb 2015 08:54:43 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1424332483; bh=qRhCGu12U5yodmg5qWybpCC1HxqlXFXL23v3diBZWhA=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=swPXEcnEHp3W4ERmIruEzp4n0NYxYv2/gFfsyNtvkwh86YTvD8fRAVMqdf8DxUgKi nH4sTj4X8cO5ENO0aPfrHWnESBjAdoaufTjzftTCgssR7F8MYQBOtLa7AUIyjipNR2 d6ORfRKjmhKSpmGp8cCD1BK2WGArLlJ7LZCx5TQs=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id E030FA1; Thu, 19 Feb 2015 08:54:43 +0100 (CET)
Date: Thu, 19 Feb 2015 08:54:43 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Michael Thomas <mike@mtcc.com>
In-Reply-To: <54E58238.9030809@mtcc.com>
Message-ID: <alpine.DEB.2.02.1502190851300.4007@uplift.swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <54E58238.9030809@mtcc.com>
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/a19ENkRTOltYXS5ujFnNmLB6s2M>
Cc: homenet@ietf.org
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 07:54:48 -0000

On Wed, 18 Feb 2015, Michael Thomas wrote:

> But we're not talking about an interpreted language in the forwarding 
> plane, right? Is the load from routing protocols we're talking about 
> likely to have any noticeable effect on the the forwarding rate? even 
> when you're running hot on the routing daemon side, you're not too 
> likely to be running hot on the forwarding side because something is 
> hosed, right?

The complaints about the Erlang implementation has so far been on memory 
and flash footprint, not CPU resources and affecting performance. The 
above is true for most interpreted languages, such as python etc. When you 
install the environment, they're going to use noticable memory and disk 
space. Next application that needs the environment won't add much to the 
footprint though, it's the environment itself that takes space.

My Python executable on my debian box is 2.7 megabyte. I don't know about 
the rest. So if one wants to run Python on the home gateway, that would 
also use significant space.

But forwarding will be done the same way regardless of what routing 
protocol we use, that'll be done by the kernel. The routing protocol just 
programs the RIB/FIB.

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


From nobody Thu Feb 19 00:26:01 2015
Return-Path: <gert@Space.Net>
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 2DEA81A88EE for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 00:26:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 VdazDm0leZmw for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 00:25:57 -0800 (PST)
Received: from mobil.space.net (mobil.space.net [IPv6:2001:608:2:81::67]) (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 6C7511A88FA for <homenet@ietf.org>; Thu, 19 Feb 2015 00:25:57 -0800 (PST)
X-Original-To: homenet@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id 258896089D for <homenet@ietf.org>; Thu, 19 Feb 2015 09:25:55 +0100 (CET)
X-SpaceNet-Relay: true
Received: from moebius3.space.net (moebius3.Space.Net [IPv6:2001:608:2:2::250]) by mobil.space.net (Postfix) with ESMTPS id E6E876031D for <homenet@ietf.org>; Thu, 19 Feb 2015 09:25:54 +0100 (CET)
Received: (qmail 25839 invoked by uid 1007); 19 Feb 2015 09:25:54 +0100
Date: Thu, 19 Feb 2015 09:25:54 +0100
From: Gert Doering <gert@space.net>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Message-ID: <20150219082554.GH34798@Space.Net>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se>
X-NCC-RegID: de.space
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/v1eWUslfSlM9RInISvDzy7HoyV0>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Dave Taht <dave.taht@gmail.com>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 08:26:00 -0000

Hi,

On Thu, Feb 19, 2015 at 08:43:26AM +0100, Mikael Abrahamsson wrote:
> We're talking about a protocol decision here. People seem to focus a lot 
> on the "running code" part here. ISIS is used for numerous things of apart 
> frmo the MPLS and Traffic engineering space, we also have IEEE 802.1aq 
> (SPB) and TRILL, it's also used in the GMPLS control plane. There are 
> probably 10-20+ commercial implementations of ISIS, if not perhaps the 
> exact TLVs we're talking about here. Most of not all of these standards 
> are described in standards track RFCs.
> 
> Against this, we have Babel, which as far as I can tell has a single 
> implementation that has been forked into two, and is based on a few 
> experimental RFCs.

Just to voice something from the opposite side of the spectrum - I'm a
fan of "do one thing and do it well" approaches, and not so much of a
"oh, we have a kitchen sink here, let's see if we can turn it into a 
living room table".

So for me, the fact that ISIS is used for umpteen other things outside
the homenet environment isn't exactly a plus side.  Yes, it is understood
that basic ISIS works (exchanging TLVs, establishing topology) - but if
you look at it from an implementors point of view that does not have
many years of ISIS background, just figuring out which parts of the
heap of potential ISIS use cases they need to implement sounds much more 
time-consuming than just taking the Babels implementation and compiling it 
for the platform of choice...

We're not talking about a routing protocol for every possible use case
here - we're talking about a fairly well defined environment (aka "fairly
small number of devices, IPv4 and IPv6 only, and implementations constrained
by lack of clue on the manufacturer side").

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444           USt-IdNr.: DE813185279


From nobody Thu Feb 19 00:52:39 2015
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 5B9301A8913 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 00:52:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.661
X-Spam-Level: 
X-Spam-Status: No, score=-1.661 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 5Owe0YBJG87N for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 00:52:36 -0800 (PST)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AD8E11A8903 for <homenet@ietf.org>; Thu, 19 Feb 2015 00:52:36 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id CA09EA3; Thu, 19 Feb 2015 09:52:34 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1424335954; bh=qArd00oKzG0XyRx3EKLO0xesiQKmtuLrAsSGkd3R8vA=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=dMvUtFZcsWKiGv0DTbo3Aw+w0Y5xZO5xvaGQKjYCsyJqI+h3SkQGJIp162q8Qc7ID ZCQ4crJ67uMCZJ20qVvGMJp6HuPR4TE1Kl7jgorGPamQCyAB1pIsagEZkAvc/Hhz2X zjgSxfRCIMqf1WY+Tn7o94GZSY2oCiOb+7tsf0yc=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id C2963A1; Thu, 19 Feb 2015 09:52:34 +0100 (CET)
Date: Thu, 19 Feb 2015 09:52:34 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Gert Doering <gert@space.net>
In-Reply-To: <20150219082554.GH34798@Space.Net>
Message-ID: <alpine.DEB.2.02.1502190931420.4007@uplift.swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <20150219082554.GH34798@Space.Net>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/S0D413qJdNrjBba4Z8Cq4nFymBs>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 08:52:39 -0000

On Thu, 19 Feb 2015, Gert Doering wrote:

> We're not talking about a routing protocol for every possible use case 
> here - we're talking about a fairly well defined environment (aka 
> "fairly small number of devices, IPv4 and IPv6 only, and implementations 
> constrained by lack of clue on the manufacturer side").

Well, to further explain my concern regarding that and current approach, I 
now see that current proposals is to have the HNCP and $ROUTINGPROTOCOL 
split. If we choose Babel, then we've locked outselves into this split and 
HNCP needs to be extended to handle every future functionality needed 
since babel can't do much more than it already does.

For instance the security work now being done on HNCP. Does ISIS already 
offer the same functionality? I can't evaluate security very well, I don't 
know how many active in this working group that can. I would rather use an 
already standardized mechanism for doing this.

It's been a while since the decision to create HNCP (which was originally 
designed so it could work inside a TLV carrying routing protocol) instead 
of carrying the required "homenet" information in the routing protocol. 
The basis for this decision, is that still true (that the routing protocol 
WGs and implementors refused to accept the TLV types needed and the APIs 
needed)?

It's been what, 1.5-2 years since then? We've already noted that HNCP 
looks awfully close to a link state protocol and duplicates quite a lot of 
of functionality.

There is talk about how complicated ISIS is. How complicated is DNCP/HNCP 
going to be when we're done with it? How many LoC is it now?

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


From nobody Thu Feb 19 01:00:35 2015
Return-Path: <dave.taht@gmail.com>
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 B4D791A8930 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 01:00:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.349
X-Spam-Level: **
X-Spam-Status: No, score=2.349 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FB_WORD2_END_DOLLAR=3.294, FREEMAIL_FROM=0.001, LOTS_OF_MONEY=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, US_DOLLARS_3=1.754] autolearn=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 xEeyXPvQweQu for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 01:00:33 -0800 (PST)
Received: from mail-pa0-f44.google.com (mail-pa0-f44.google.com [209.85.220.44]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EA6191A892A for <homenet@ietf.org>; Thu, 19 Feb 2015 01:00:32 -0800 (PST)
Received: by padbj1 with SMTP id bj1so8014013pad.5 for <homenet@ietf.org>; Thu, 19 Feb 2015 01:00:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=heqXthjXfw3CqOEYRd6JJ3U69JcZ4qEfcJcmpjDW4UI=; b=bv7LVAkvoqvZU6/WQ2SGLGDWTLc+aZtC0N6s5zLss7Ip1NIOz8xZG4g1dkIf/lTUXQ NUO2Z5gfv3PZZXiKXjWXJ5P1b4bpeCVNzXrDGg8+5Bx/na2RBqJy02HW/ggu4HmFu1d8 PTN2EqQinEor0F4Isl3ydS79khsbbJ0BN4ZSksHL4HcPzDQiMimXQt1BPr0lcFnYKnd9 axq9s1ZYNOdn42Gg5+LvFR4MTsUKmD4ckNczIqdmltRUMMqei7gmACPIHD3Flrtow94r bhyVV4NJ/zWgnR0VI2pjnEnP1xvT0QaJlUxykgGOvWkbFGfhzug6OQA/5jduvmloRZIa i0OA==
MIME-Version: 1.0
X-Received: by 10.66.154.17 with SMTP id vk17mr5870684pab.5.1424336432606; Thu, 19 Feb 2015 01:00:32 -0800 (PST)
Received: by 10.70.117.162 with HTTP; Thu, 19 Feb 2015 01:00:32 -0800 (PST)
In-Reply-To: <alpine.DEB.2.02.1502190931420.4007@uplift.swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <20150219082554.GH34798@Space.Net> <alpine.DEB.2.02.1502190931420.4007@uplift.swm.pp.se>
Date: Thu, 19 Feb 2015 01:00:32 -0800
Message-ID: <CAA93jw7bWFPs1ntEVyvAoQU-1Zjf1jOhpsW2cDgAjYLvJteuFg@mail.gmail.com>
From: Dave Taht <dave.taht@gmail.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/BiH_fF-K_-mv0to8eRxMC_KiYbo>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Gert Doering <gert@space.net>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 09:00:34 -0000

On Thu, Feb 19, 2015 at 12:52 AM, Mikael Abrahamsson <swmike@swm.pp.se> wro=
te:
> On Thu, 19 Feb 2015, Gert Doering wrote:
>
>> We're not talking about a routing protocol for every possible use case
>> here - we're talking about a fairly well defined environment (aka "fairl=
y
>> small number of devices, IPv4 and IPv6 only, and implementations constra=
ined
>> by lack of clue on the manufacturer side").
>
>
> Well, to further explain my concern regarding that and current approach, =
I
> now see that current proposals is to have the HNCP and $ROUTINGPROTOCOL
> split. If we choose Babel, then we've locked outselves into this split an=
d
> HNCP needs to be extended to handle every future functionality needed sin=
ce
> babel can't do much more than it already does.
>
> For instance the security work now being done on HNCP. Does ISIS already
> offer the same functionality? I can't evaluate security very well, I don'=
t
> know how many active in this working group that can. I would rather use a=
n
> already standardized mechanism for doing this.
>
> It's been a while since the decision to create HNCP (which was originally
> designed so it could work inside a TLV carrying routing protocol) instead=
 of
> carrying the required "homenet" information in the routing protocol. The
> basis for this decision, is that still true (that the routing protocol WG=
s
> and implementors refused to accept the TLV types needed and the APIs
> needed)?
>
> It's been what, 1.5-2 years since then? We've already noted that HNCP loo=
ks
> awfully close to a link state protocol and duplicates quite a lot of of
> functionality.
>
> There is talk about how complicated ISIS is. How complicated is DNCP/HNCP
> going to be when we're done with it? How many LoC is it now?

hnetd exclusive of the library dependencies (which I could easily run
a sloccount for, also, if you care)

d@nuc-client:~/git/hnetd$ sloccount --personcost 110000 generic src test op=
enwrt

SLOC    Directory    SLOC-by-Language (Sorted)
12936   src             ansic=3D12936
5806    test            ansic=3D5806
417     generic         sh=3D417
99      openwrt         sh=3D99


Totals grouped by language (dominant language first):
ansic:        18742 (97.32%)
sh:             516 (2.68%)


Total Physical Source Lines of Code (SLOC)                =3D 19,258
Development Effort Estimate, Person-Years (Person-Months) =3D 4.47 (53.59)
 (Basic COCOMO model, Person-Months =3D 2.4 * (KSLOC**1.05))
Schedule Estimate, Years (Months)                         =3D 0.95 (11.35)
 (Basic COCOMO model, Months =3D 2.5 * (person-months**0.38))
Estimated Average Number of Developers (Effort/Schedule)  =3D 4.72
Total Estimated Cost to Develop                           =3D $ 1,178,896
 (average salary =3D $110,000/year, overhead =3D 2.40).
SLOCCount, Copyright (C) 2001-2004 David A. Wheeler
SLOCCount is Open Source Software/Free Software, licensed under the GNU GPL=
.
SLOCCount comes with ABSOLUTELY NO WARRANTY, and you are welcome to
redistribute it under certain conditions as specified by the GNU GPL licens=
e;
see the documentation for details.
Please credit this data as "generated using David A. Wheeler's 'SLOCCount'.=
"


Babel on the other hand:

SLOC    Directory    SLOC-by-Language (Sorted)
10737   babeld          ansic=3D10474,sh=3D263


Totals grouped by language (dominant language first):
ansic:        10474 (97.55%)
sh:             263 (2.45%)


Total Physical Source Lines of Code (SLOC)                =3D 10,737
Development Effort Estimate, Person-Years (Person-Months) =3D 2.42 (29.02)
 (Basic COCOMO model, Person-Months =3D 2.4 * (KSLOC**1.05))
Schedule Estimate, Years (Months)                         =3D 0.75 (8.99)
 (Basic COCOMO model, Months =3D 2.5 * (person-months**0.38))
Estimated Average Number of Developers (Effort/Schedule)  =3D 3.23
Total Estimated Cost to Develop                           =3D $ 638,353
 (average salary =3D $110,000/year, overhead =3D 2.40).
SLOCCount, Copyright (C) 2001-2004 David A. Wheeler
SLOCCount is Open Source Software/Free Software, licensed under the GNU GPL=
.
SLOCCount comes with ABSOLUTELY NO WARRANTY, and you are welcome to
redistribute it under certain conditions as specified by the GNU GPL licens=
e;
see the documentation for details.
Please credit this data as "generated using David A. Wheeler's 'SLOCCount'.=
"



> --
> Mikael Abrahamsson    email: swmike@swm.pp.se
>
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet



--=20
Dave T=C3=A4ht

thttp://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks


From nobody Thu Feb 19 01:15:51 2015
Return-Path: <markus.stenberg@iki.fi>
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 4BCFE1A8967 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 01:15:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.121
X-Spam-Level: 
X-Spam-Status: No, score=-1.121 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_NEUTRAL=0.779] autolearn=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 hoOL0BVhAdbM for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 01:15:46 -0800 (PST)
Received: from jenni1.inet.fi (mta-out1.inet.fi [62.71.2.195]) by ietfa.amsl.com (Postfix) with ESMTP id 1EF4F1A894C for <homenet@ietf.org>; Thu, 19 Feb 2015 01:15:46 -0800 (PST)
Received: from poro.lan (80.220.64.126) by jenni1.inet.fi (8.5.142.08) (authenticated as stenma-47) id 54E3C703002F0B1C; Thu, 19 Feb 2015 11:15:40 +0200
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Markus Stenberg <markus.stenberg@iki.fi>
In-Reply-To: <alpine.DEB.2.02.1502190931420.4007@uplift.swm.pp.se>
Date: Thu, 19 Feb 2015 11:15:38 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <B52B6CCA-FDAE-4BC7-B876-133C8069404C@iki.fi>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <20150219082554.GH34798@Space.Net> <alpine.DEB.2.02.1502190931420.4007@uplift.swm.pp.se>
To: Mikael Abrahamsson <swmike@swm.pp.se>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/Yz3QfnZXxA6RZl1Z439C9AfYOWE>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Markus Stenberg <markus.stenberg@iki.fi>, Gert Doering <gert@space.net>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 09:15:50 -0000

> On 19.2.2015, at 10.52, Mikael Abrahamsson <swmike@swm.pp.se> wrote:
>> We're not talking about a routing protocol for every possible use =
case here - we're talking about a fairly well defined environment (aka =
"fairly small number of devices, IPv4 and IPv6 only, and implementations =
constrained by lack of clue on the manufacturer side").
> Well, to further explain my concern regarding that and current =
approach, I now see that current proposals is to have the HNCP and =
$ROUTINGPROTOCOL split. If we choose Babel, then we've locked outselves =
into this split and HNCP needs to be extended to handle every future =
functionality needed since babel can't do much more than it already =
does.
>=20
> For instance the security work now being done on HNCP. Does ISIS =
already offer the same functionality? I can't evaluate security very =
well, I don't know how many active in this working group that can. I =
would rather use an already standardized mechanism for doing this.

Luckily I can. The comparison document unfortunately lacks references, =
and I am not motivated enough to look it up, but based on the comparison =
document, it does not.=20

IS-IS essentially offers just the good old =E2=80=98password=E2=80=99 =
scheme (and so does Babel). It is not user-friendly, that=E2=80=99s why =
DNCP has 2 other PKI based modes too (CA hierarchy, trust consensus).

Certainly, we could argue that we use something like mini-HNCP to =
=E2=80=98bootstrap=E2=80=99 IS-IS, but I am not sure that is a clever =
idea either.

> It's been a while since the decision to create HNCP (which was =
originally designed so it could work inside a TLV carrying routing =
protocol) instead of carrying the required "homenet" information in the =
routing protocol. The basis for this decision, is that still true (that =
the routing protocol WGs and implementors refused to accept the TLV =
types needed and the APIs needed)?

At the time there were fears of routing protocol peeing in it=E2=80=99s =
pants, given sufficiently churny data, and/or political process stalling =
us for years. I think we have seen the later effect already. I do not =
believe in the former.

> It's been what, 1.5-2 years since then? We've already noted that HNCP =
looks awfully close to a link state protocol and duplicates quite a lot =
of of functionality.

Right. It is essentially bit more modern take on a link state routing =
protocol. So if you bring it up, I bring up the another argument - why =
not route using it? Cost of doing _that_ is ~100 LoC (+ whatever fancy =
thing we want to do with metrics).

Cheers,

-Markus=


From nobody Thu Feb 19 01:28:33 2015
Return-Path: <cyrus@openwrt.org>
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 E0EA41A8758 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 01:28:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.044
X-Spam-Level: *
X-Spam-Status: No, score=1.044 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FB_WORD2_END_DOLLAR=3.294, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-0.7] autolearn=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 vfs5PMOAAEjR for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 01:28:30 -0800 (PST)
Received: from mail.core-networks.de (mail.core-networks.de [82.96.72.7]) by ietfa.amsl.com (Postfix) with ESMTP id 197861A0397 for <homenet@ietf.org>; Thu, 19 Feb 2015 01:28:30 -0800 (PST)
Received: from localhost ([127.0.0.1]) by mail.core-networks.de id 1YONPG-0005rg-9Y with ESMTPSA (TLSv1.2:DHE-RSA-AES128-SHA:128) for ; Thu, 19 Feb 2015 10:28:26 +0100
Message-ID: <54E5ACB8.6040803@openwrt.org>
Date: Thu, 19 Feb 2015 10:28:24 +0100
From: Steven Barth <cyrus@openwrt.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.4.0
MIME-Version: 1.0
To: Dave Taht <dave.taht@gmail.com>,  Mikael Abrahamsson <swmike@swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <20150219082554.GH34798@Space.Net> <alpine.DEB.2.02.1502190931420.4007@uplift.swm.pp.se> <CAA93jw7bWFPs1ntEVyvAoQU-1Zjf1jOhpsW2cDgAjYLvJteuFg@mail.gmail.com>
In-Reply-To: <CAA93jw7bWFPs1ntEVyvAoQU-1Zjf1jOhpsW2cDgAjYLvJteuFg@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/1OPgKTLtobpW5Io7oEOr889yWQc>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Gert Doering <gert@space.net>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 09:28:32 -0000

On 19.02.2015 10:00, Dave Taht wrote:
>
> hnetd exclusive of the library dependencies (which I could easily run
> a sloccount for, also, if you care)
>
> d@nuc-client:~/git/hnetd$ sloccount --personcost 110000 generic src test openwrt
>
> SLOC    Directory    SLOC-by-Language (Sorted)
> 12936   src             ansic=12936
> 5806    test            ansic=5806
> 417     generic         sh=417
> 99      openwrt         sh=99
As a rough estimate of those 12-13 KLOC only about one sixth should be 
related to DNCP. So I very much doubt that hooking it up to a 3rd-party 
daemon for topology/TLV-management would make any noticable impact.


From nobody Thu Feb 19 01:30:03 2015
Return-Path: <gert@Space.Net>
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 93CAB1A8758 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 01:30:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.61
X-Spam-Level: 
X-Spam-Status: No, score=-2.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 CGNGBv2QbWlM for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 01:29:59 -0800 (PST)
Received: from mobil.space.net (mobil.space.net [195.30.115.67]) (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 73F051A0397 for <homenet@ietf.org>; Thu, 19 Feb 2015 01:29:59 -0800 (PST)
X-Original-To: homenet@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id BB3E46035E for <homenet@ietf.org>; Thu, 19 Feb 2015 10:29:57 +0100 (CET)
X-SpaceNet-Relay: true
Received: from moebius3.space.net (moebius3.Space.Net [IPv6:2001:608:2:2::250]) by mobil.space.net (Postfix) with ESMTPS id 876BA60174 for <homenet@ietf.org>; Thu, 19 Feb 2015 10:29:57 +0100 (CET)
Received: (qmail 37929 invoked by uid 1007); 19 Feb 2015 10:29:57 +0100
Date: Thu, 19 Feb 2015 10:29:57 +0100
From: Gert Doering <gert@space.net>
To: Markus Stenberg <markus.stenberg@iki.fi>
Message-ID: <20150219092957.GK34798@Space.Net>
References: <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <20150219082554.GH34798@Space.Net> <alpine.DEB.2.02.1502190931420.4007@uplift.swm.pp.se> <B52B6CCA-FDAE-4BC7-B876-133C8069404C@iki.fi>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="PAUSoqvtBEM1v/pw"
Content-Disposition: inline
In-Reply-To: <B52B6CCA-FDAE-4BC7-B876-133C8069404C@iki.fi>
X-NCC-RegID: de.space
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/Vck1E72qrod0IygkmLHcc7LIM9g>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Gert Doering <gert@space.net>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 09:30:01 -0000

--PAUSoqvtBEM1v/pw
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi,

On Thu, Feb 19, 2015 at 11:15:38AM +0200, Markus Stenberg wrote:
> [ HNCP ]
>=20
> Right. It is essentially bit more modern take on a link state
> routing protocol. So if you bring it up, I bring up the another
> argument - why not route using it? Cost of doing _that_ is ~100 LoC
> (+ whatever fancy thing we want to do with metrics).

This is actually something I have been wondering about.  Why not use
HNCP to do all the work, when it's already nicely establishing a=20
communication infrastructure?

This decision happened before I joined this list...

Gert Doering
        -- NetMaster
--=20
have you enabled IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444           USt-IdNr.: DE813185279

--PAUSoqvtBEM1v/pw
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIVAwUBVOWtFd9WwGXkzn/FAQLbLA/9F8boPhngEysQLoILrYXmrm1s5d5VJ/V6
E3ep0brG+4zlPdRB7+Slry+7aOlI8LKbWhiOGXYOOUAMk9fS+O0PbEFU3yHnHDOx
OYTLW6Ty9GAMjTP4/ljA/Xfrxzif0HZUkXZtH5jdpcNTF9tVc/OJpeB7/Ww8m2By
8KFfyVJsSDOqaiv9vS8nC9lOw8QGyi30BY9ccahMhC+ZFGUCAuCtP0pmjBM9Or0U
f91SPUSNMrD51VNf3SQuSSuiKA6LTbEFZ0aEh55lA81vfccNcmmO7+9kahAn1Rvm
eDkWXV3NPnLMk+HGcVK4wNKJzyw7SD8z0/FsHuE88NessFxUHPQAId0ADsRSDcoV
1UOowtCsQsi89moEtvyo/ICl5eBnqDr3lBnKQz6f2JZYldqHAmDE0mIfGOXep4Co
VBOmrS8BmoXgTUbscZKBqD5GAqFnbR6H6/h5Q55phcIbSujbwYxpGPoI4QtZRe8+
62crgzCbDSJDkVuF4fxky4RgYK0RT1NbRBzo5dP7Ov8tyT5rx5aqiplyIB0/DQIR
Celo0x8sBPiip6eGJ7jNp2t1Ms9+OAyQ2wq/B6ZqYxpM7YtaYGZ4Kpgvmo3SJ0qJ
8VfY6N5lHXCS8a8+V+652d2FXYxcPCgO08/f2Rdcc73DX84pasfRQMzsXGfgILjW
eijdjejb5NM=
=BRSd
-----END PGP SIGNATURE-----

--PAUSoqvtBEM1v/pw--


From nobody Thu Feb 19 01:43:44 2015
Return-Path: <markus.stenberg@iki.fi>
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 E4E0C1A898B for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 01:43:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.173
X-Spam-Level: **
X-Spam-Status: No, score=2.173 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FB_WORD2_END_DOLLAR=3.294, RCVD_IN_DNSWL_NONE=-0.0001, SPF_NEUTRAL=0.779] autolearn=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 xjLJ1Z0mDgJ9 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 01:43:42 -0800 (PST)
Received: from jenni2.inet.fi (mta-out1.inet.fi [62.71.2.227]) by ietfa.amsl.com (Postfix) with ESMTP id 716D51A8981 for <homenet@ietf.org>; Thu, 19 Feb 2015 01:43:42 -0800 (PST)
Received: from poro.lan (80.220.64.126) by jenni2.inet.fi (8.5.142.08) (authenticated as stenma-47) id 54E3C70700308DDE; Thu, 19 Feb 2015 11:43:36 +0200
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Markus Stenberg <markus.stenberg@iki.fi>
In-Reply-To: <54E5ACB8.6040803@openwrt.org>
Date: Thu, 19 Feb 2015 11:43:35 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <5E38B49C-B2B2-4358-BD5A-7E6AFD08D2E6@iki.fi>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <20150219082554.GH34798@Space.Net> <alpine.DEB.2.02.1502190931420.4007@uplift.swm.pp.se> <CAA93jw7bWFPs1ntEVyvAoQU-1Zjf1jOhpsW2cDgAjYLvJteuFg@mail.gmail.com> <54E5ACB8.6040803@openwrt.org>
To: Steven Barth <cyrus@openwrt.org>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/JMs-wS7DTziRgnJP7kn_n16KQUI>
Cc: Gert Doering <gert@space.net>, "homenet@ietf.org Group" <homenet@ietf.org>, Markus Stenberg <markus.stenberg@iki.fi>, Dave Taht <dave.taht@gmail.com>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 09:43:44 -0000

On 19.2.2015, at 11.28, Steven Barth <cyrus@openwrt.org> wrote:
> On 19.02.2015 10:00, Dave Taht wrote:
>>=20
>> hnetd exclusive of the library dependencies (which I could easily run
>> a sloccount for, also, if you care)
>>=20
>> d@nuc-client:~/git/hnetd$ sloccount --personcost 110000 generic src =
test openwrt
>>=20
>> SLOC    Directory    SLOC-by-Language (Sorted)
>> 12936   src             ansic=3D12936
>> 5806    test            ansic=3D5806
>> 417     generic         sh=3D417
>> 99      openwrt         sh=3D99
> As a rough estimate of those 12-13 KLOC only about one sixth should be =
related to DNCP. So I very much doubt that hooking it up to a 3rd-party =
daemon for topology/TLV-management would make any noticable impact.

Do also note that the current codebase _does_ include the =E2=80=98routing=
=E2=80=99 part too, smirk..

(from dncp-00 branch):

src/dncp*.[ch]: 2.7k LoC
the rest: 12.5k LoC
(=E2=80=99the rest=E2=80=99 seems to be gradually growing but includes =
e.g. both supported platforms=E2=80=99 C code)

src/hncp_routing.[ch] has 309 lines of code, but it also does routing =
protocol election (that is being phased out but remains =
implementation-specific, as current $FOO routing protocol is not really =
usable in the real world).

Cheers,

-Markus


From nobody Thu Feb 19 03:23:05 2015
Return-Path: <mellon@fugue.com>
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 DA8821A888F for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 03:23:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 73hWb4unia27 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 03:23:01 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 979A71A8AB7 for <homenet@ietf.org>; Thu, 19 Feb 2015 03:22:54 -0800 (PST)
Received: from [10.0.20.107] (c-71-233-43-215.hsd1.nh.comcast.net [71.233.43.215]) by toccata.fugue.com (Postfix) with ESMTPSA id B8CD1238039E; Thu, 19 Feb 2015 06:22:52 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se>
Date: Thu, 19 Feb 2015 06:22:24 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <A5767F83-3D0C-40E5-A73B-912E3C160A42@fugue.com>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se>
To: Mikael Abrahamsson <swmike@swm.pp.se>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/ogNFhyW2iNKdUsvCF1PHEp5ZkmY>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Dave Taht <dave.taht@gmail.com>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 11:23:04 -0000

On Feb 19, 2015, at 2:43 AM, Mikael Abrahamsson <swmike@swm.pp.se> =
wrote:
> If people are making routing protocol decision based on the fact that =
they think most of the homenet links are going to be current incarnation =
of 802.11, then we're lacking consensus on a lot wider range of =
requirements than just the routing protocol. We have different opinions =
on what homenet actually is and what it's going to look like.

Mikael, it is common practice to do air-to-air bridging on home networks =
now.   We have discussed whether we want to support this in homenet, and =
concluded that we must.   You are the first person as far as I can =
recall to suggest that this was optional.   Yes, we do need a routing =
protocol that works well when some of the transit networks are wifi =
networks.   This is not an edge case.


From nobody Thu Feb 19 03:26:44 2015
Return-Path: <mellon@fugue.com>
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 531C71A888F for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 03:26:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 3fj6U3kYqf9s for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 03:26:40 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id D25011A8AB7 for <homenet@ietf.org>; Thu, 19 Feb 2015 03:26:40 -0800 (PST)
Received: from [10.0.20.107] (c-71-233-43-215.hsd1.nh.comcast.net [71.233.43.215]) by toccata.fugue.com (Postfix) with ESMTPSA id AEFBC238039E; Thu, 19 Feb 2015 06:26:39 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <alpine.DEB.2.02.1502190931420.4007@uplift.swm.pp.se>
Date: Thu, 19 Feb 2015 06:26:12 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <2154745E-24D7-481C-9A50-C45479DF2B25@fugue.com>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <20150219082554.GH34798@Space.Net> <alpine.DEB.2.02.1502190931420.4007@uplift.swm.pp.se>
To: Mikael Abrahamsson <swmike@swm.pp.se>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/8gF4OSy7DcyoXaIC4oNYdBkIgvU>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Gert Doering <gert@space.net>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 11:26:42 -0000

On Feb 19, 2015, at 3:52 AM, Mikael Abrahamsson <swmike@swm.pp.se> =
wrote:
> For instance the security work now being done on HNCP. Does ISIS =
already offer the same functionality? I can't evaluate security very =
well, I don't know how many active in this working group that can. I =
would rather use an already standardized mechanism for doing this.

IS-IS is a routing protocol, not a configuration protocol.   Its =
security needs are completely orthogonal to what we are doing in =
homenet.   HNCP can probably provide the tokens required to do IS-IS =
security, but IS-IS doesn't bring anything to the table as far as =
homenet security is concerned.   This is basically a red herring: Babel =
as far as I know doesn't bring anything to the table either.


From nobody Thu Feb 19 03:41:07 2015
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 834DC1A8AEF for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 03:41:06 -0800 (PST)
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 BBWp4aLk8XUT for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 03:41:04 -0800 (PST)
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 1BEBE1A8AEA for <homenet@ietf.org>; Thu, 19 Feb 2015 03:41:03 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 7BCC0A3; Thu, 19 Feb 2015 12:41:02 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1424346062; bh=RivsJ2V2aXyglxBrwwU4UIsoGxQ6fRYM6Uj1C9SQlqE=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=CSW2VTMrOs9Qo+cX4FMHtwcL77VkWX0M/WbIHO7wLCORTqhITgBWCSSV/+rHoeGmm b2nef9EdiWyFERuA2JWqTSH37ItNl1XTvmeMR5O3t+IeH5P+sKcm8uBLsCKW9OQhC7 aWCOY0YTGug/lOSl5x2teh27boamMq02I+h10OqM=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 6C0A4A1; Thu, 19 Feb 2015 12:41:02 +0100 (CET)
Date: Thu, 19 Feb 2015 12:41:02 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Ted Lemon <mellon@fugue.com>
In-Reply-To: <A5767F83-3D0C-40E5-A73B-912E3C160A42@fugue.com>
Message-ID: <alpine.DEB.2.02.1502191235240.4007@uplift.swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <A5767F83-3D0C-40E5-A73B-912E3C160A42@fugue.com>
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/eh3Fv2f5QwXfNU-ehZw4_xJtL9g>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 11:41:06 -0000

On Thu, 19 Feb 2015, Ted Lemon wrote:

> Mikael, it is common practice to do air-to-air bridging on home networks 
> now.  We have discussed whether we want to support this in homenet, and 
> concluded that we must.  You are the first person as far as I can recall 
> to suggest that this was optional.  Yes, we do need a routing protocol 
> that works well when some of the transit networks are wifi networks. 
> This is not an edge case.

Then we need to decide what kind of Wifi network we need to handle.

Because if we're trying to support marginal performance mesh networks that 
might change all the time, lose packets, drop multicast packets randomly, 
etc, then those requirements need to be brought to the discussion.

Basically, Dave Taht and Jim Gettys have been working a lot in these 
"marginal networks". They have a lot of experience. Personally, I don't 
see their kind of networks as something Homenet needs to support. I can 
see us needing to support a few wifi bridging hops, but what they're 
referring to is a quite different beast.

Also, how would HNCP perform on those kinds of networks? If we put that as 
an requirement on the routing protocol, then we need to make sure HNCP is 
also resilient facing these kinds of networks.

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


From nobody Thu Feb 19 03:53:23 2015
Return-Path: <mellon@fugue.com>
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 58AEE1A8A99 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 03:53:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 3zBJBDElZ7Jt for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 03:53:20 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id B927B1A8943 for <homenet@ietf.org>; Thu, 19 Feb 2015 03:53:19 -0800 (PST)
Received: from [10.0.20.107] (c-71-233-43-215.hsd1.nh.comcast.net [71.233.43.215]) by toccata.fugue.com (Postfix) with ESMTPSA id 3520F23802B7; Thu, 19 Feb 2015 06:53:17 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <alpine.DEB.2.02.1502191235240.4007@uplift.swm.pp.se>
Date: Thu, 19 Feb 2015 06:52:50 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <BFE3D83C-1BE0-4C7F-9245-1EDE4146A124@fugue.com>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <A5767F83-3D0C-40E5-A73B-912E3C160A42@fugue.com> <alpine.DEB.2.02.1502191235240.4007@uplift.swm.pp.se>
To: Mikael Abrahamsson <swmike@swm.pp.se>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/nHyqQ9ggOnQZv8gx8_Qgv1iaMRg>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 11:53:23 -0000

On Feb 19, 2015, at 6:41 AM, Mikael Abrahamsson <swmike@swm.pp.se> =
wrote:
> Basically, Dave Taht and Jim Gettys have been working a lot in these =
"marginal networks". They have a lot of experience. Personally, I don't =
see their kind of networks as something Homenet needs to support. I can =
see us needing to support a few wifi bridging hops, but what they're =
referring to is a quite different beast.

I think it's reasonable to assume that the network will be somewhat =
marginal; if it's really seriously marginal though maybe the right thing =
to do is have a UI for reporting that to the user so that they can try =
to fix it.   But we want it to work to the extent possible regardless, =
because we are targeting end-users who may not be competent to respond =
to UI indications of that sort.

Dealing with marginal networks obviously isn't something that's going to =
happen in an apartment in Stockholm, but it's pretty easy to imagine =
something like that where I live out in the country, and both Dave and =
Jim have similar situations.   This is exacerbated in my case because we =
used a lot of building materials with metal foils in them, and that =
messes with radio propagation.   I think in Dave's case it's just =
distance.

The point is that I can completely understand your skepticism about =
this, but there's a reason why some working group participants have been =
pushing for functionality in the more marginal cases.

I don't think HNCP has a particular problem here, but maybe Markus can =
speak to that.


From nobody Thu Feb 19 05:18:00 2015
Return-Path: <tony@lavanauts.org>
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 3258E1A8829 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 05:18:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 dbdy0livHf0u for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 05:17:58 -0800 (PST)
Received: from slimemold.creativedynamo.com (slimemold.creativedynamo.com [IPv6:2605:b00:0:2:218:51ff:fea6:15c0]) (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 35E7A1A874E for <homenet@ietf.org>; Thu, 19 Feb 2015 05:17:49 -0800 (PST)
Received: from [2605:e000:d380:ff01:230:1bff:fe3f:6050] (unknown [IPv6:2605:e000:d380:ff01:230:1bff:fe3f:6050]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by slimemold.creativedynamo.com (Postfix) with ESMTPS id 9A851A33D2; Thu, 19 Feb 2015 03:17:46 -1000 (HST)
Date: Thu, 19 Feb 2015 03:17:43 -1000 (HST)
From: Antonio Querubin <tony@lavanauts.org>
X-X-Sender: tony@sol
To: Mikael Abrahamsson <swmike@swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1502191235240.4007@uplift.swm.pp.se>
Message-ID: <alpine.DEB.2.10.1502190314300.24898@sol>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <A5767F83-3D0C-40E5-A73B-912E3C160A42@fugue.com> <alpine.DEB.2.02.1502191235240.4007@uplift.swm.pp.se>
User-Agent: Alpine 2.10 (DEB 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/eXp6YkROoEW2wyL8Edh5t30AeTI>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Ted Lemon <mellon@fugue.com>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 13:18:00 -0000

On Thu, 19 Feb 2015, Mikael Abrahamsson wrote:

> Because if we're trying to support marginal performance mesh networks that 
> might change all the time, lose packets, drop multicast packets randomly, 
> etc, then those requirements need to be brought to the discussion.
>
> Basically, Dave Taht and Jim Gettys have been working a lot in these 
> "marginal networks". They have a lot of experience. Personally, I don't see 
> their kind of networks as something Homenet needs to support. I can see us 
> needing to support a few wifi bridging hops, but what they're referring to is 
> a quite different beast.

Mesh networks are not necessarilly 'marginal'.  They're about extending 
range and mobility.

Antonio Querubin
e-mail:  tony@lavanauts.org
xmpp:  antonioquerubin@gmail.com


From SRS0=JCZa=DF=darou.fr=pierre.pfister@bounces.m4x.org  Thu Feb 19 06:50:17 2015
Return-Path: <SRS0=JCZa=DF=darou.fr=pierre.pfister@bounces.m4x.org>
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 969AF1A1A91 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 06:50:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 O5eed2JXUSFE for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 06:50:15 -0800 (PST)
Received: from mx1.polytechnique.org (mx1.polytechnique.org [129.104.30.34]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A7EC51A87B2 for <homenet@ietf.org>; Thu, 19 Feb 2015 06:50:09 -0800 (PST)
Received: from [10.148.10.162] (173-38-208-170.cisco.com [173.38.208.170]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ssl.polytechnique.org (Postfix) with ESMTPSA id D64401408EFAB; Thu, 19 Feb 2015 15:50:05 +0100 (CET)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Pierre Pfister <pierre.pfister@darou.fr>
In-Reply-To: <B52B6CCA-FDAE-4BC7-B876-133C8069404C@iki.fi>
Date: Thu, 19 Feb 2015 15:50:05 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <2531C6F7-5384-44D4-928E-80E68F8B8EE4@darou.fr>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <20150219082554.GH34798@Space.Net> <alpine.DEB.2.02.1502190931420.4007@uplift.swm.pp.se> <B52B6CCA-FDAE-4BC7-B876-133C8069404C@iki.fi>
To: Markus Stenberg <markus.stenberg@iki.fi>
X-Mailer: Apple Mail (2.1878.6)
X-AV-Checked: ClamAV using ClamSMTP at svoboda.polytechnique.org (Thu Feb 19 15:50:06 2015 +0100 (CET))
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/wog5Rg3gwUyfIKdA5N4sghvxq4s>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Gert Doering <gert@space.net>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 14:50:39 -0000

>=20
>> It's been what, 1.5-2 years since then? We've already noted that HNCP =
looks awfully close to a link state protocol and duplicates quite a lot =
of of functionality.
>=20
> Right. It is essentially bit more modern take on a link state routing =
protocol. So if you bring it up, I bring up the another argument - why =
not route using it? Cost of doing _that_ is ~100 LoC (+ whatever fancy =
thing we want to do with metrics).
>=20

First of all, because there are differences between assigning a prefix =
and using it for routing.=20
- Assigning a prefix does not mean you are the best router to route =
toward it. It may not even mean it is assigned to a link you are =
directly connected to. It may also be an excluded prefix. Assigning a =
prefix just means you reserve that prefix for some usage. One of this =
usage happens to be =91prefix assignment to a link=92, but it may be =
others.
- There is a delay between the assignment and the actual use of a =
prefix. This is called =91Apply Delay=92 in the prefix assignment draft. =
I don=92t think routing based on assigned prefix TLVs is a good idea =
because you would not try to handle assigned prefixes collisions =
correctly.

Second point is that DNCP is going to transport multiple things. This =
will imply churn. As Gert said, I think protocols should do one thing =
and do it well. Babel is a loop-avoiding routing protocol. Do we want to =
put loop-avoidance mechanism in HNCP ? Of course not. Would HNCP be able =
to do routing ? Yes. But would it be able to do it if a buggy node =
constantly sends DNCP updates=85 It is less sure, and depends on the =
quality of the implementation.=20

Last point is that the routing protocol we will agree on will not be the =
last we=92ll ever come-up with. Some other will be invented. Better =
ones. DNCP is an element with a set of requirements. Let=92s keep DNCP =
simple. A routing protocol has other requirements. And maybe some day we =
will decide to move to another routing protocol because we made a =
mistake or a new better routing protocol was designed. We need to make =
sure that this transition will be possible. And I think having an =
independent routing protocol running today will make this transition =
easier.

Cheers,

- Pierre=


From nobody Thu Feb 19 06:58:50 2015
Return-Path: <gert@Space.Net>
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 BB2DC1A87B3 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 06:58:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level: 
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_22=0.6, RCVD_IN_DNSWL_LOW=-0.7, 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 QgLt2jMInxdq for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 06:58:47 -0800 (PST)
Received: from mobil.space.net (mobil.space.net [195.30.115.67]) (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 F26291A001C for <homenet@ietf.org>; Thu, 19 Feb 2015 06:58:46 -0800 (PST)
X-Original-To: homenet@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id E26366095A for <homenet@ietf.org>; Thu, 19 Feb 2015 15:58:44 +0100 (CET)
X-SpaceNet-Relay: true
Received: from moebius3.space.net (moebius3.Space.Net [IPv6:2001:608:2:2::250]) by mobil.space.net (Postfix) with ESMTPS id ABC5E60102 for <homenet@ietf.org>; Thu, 19 Feb 2015 15:58:44 +0100 (CET)
Received: (qmail 4187 invoked by uid 1007); 19 Feb 2015 15:58:44 +0100
Date: Thu, 19 Feb 2015 15:58:44 +0100
From: Gert Doering <gert@space.net>
To: Pierre Pfister <pierre.pfister@darou.fr>
Message-ID: <20150219145844.GX34798@Space.Net>
References: <2531C6F7-5384-44D4-928E-80E68F8B8EE4@darou.fr>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="bL35ULeiEXKGPY0P"
Content-Disposition: inline
In-Reply-To: <2531C6F7-5384-44D4-928E-80E68F8B8EE4@darou.fr>
X-NCC-RegID: de.space
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/IvTBzQEHFpff-76xk3JdiASRE84>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Markus Stenberg <markus.stenberg@iki.fi>, Gert Doering <gert@space.net>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 14:58:49 -0000

--bL35ULeiEXKGPY0P
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi,

On Thu, Feb 19, 2015 at 03:50:05PM +0100, Pierre Pfister wrote:
> Last point is that the routing protocol we will agree on will not
> be the last we?ll ever come-up with. Some other will be invented.
> [..] And
> maybe some day we will decide to move to another routing protocol
> because we made a mistake or a new better routing protocol was
> designed. We need to make sure that this transition will be possible.
> And I think having an independent routing protocol running today
> will make this transition easier.

I disagree with the "it needs to be totally open, extendable, flexible"
line of argument.

Homenet is something that needs to be implemented by *home* CPE vendors,
and interoperate between all those implementations.

Having too much options will make it look like IPSEC.  Nice standards, but
to get two different implementations interoperate, you need a diploma in
troubleshooting.

Gert Doering
        -- NetMaster
--=20
have you enabled IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444           USt-IdNr.: DE813185279

--bL35ULeiEXKGPY0P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIVAwUBVOX6JN9WwGXkzn/FAQILog/8DGCuvkNVBjaJpJHdjFLRho7WTejVPpkD
TXs9DJ/H6+YQacSRAAbYn13TmgeDZLquNwr3CtKZKEpA7eJUFrzoYVsIXKFWOI3r
iAGtEqhDFG04yrNYPwdblJyaeMQeOG2iyOZ+0ekaFxi4+oIEzE23SCFBj04sEXOi
AeB5VtayLgQXeI7PsCZth5Ixo1QCJw9qggVTyQ6/5dyD5GO+ui3iX2RJtrCD5UWG
B75ESEMEZUoZGfP9exuCzOBW82zYlQMJ1FuP+JklxyR8uOHUlBvMjNYnpuIV4FQq
xofAYqfkGDbRO0ZeaziZTHZEDPj14lE02uP/RoMqVyhchEU1bvi8sZfvRlPOZwXv
RCYdxGdffyRD/tDVXZho0FXP+6cRAwrvdiYS5fylhgGSpW1+AsHScTpM+66SnlmV
kWorCOM/pzkk4QZfeoBULuK6d3oUM2EuKlr9Cqez7+krXA4GjfNT3O+8JV4maOop
V9aXXqFDIhcjLJzZX+/i0Mx7W/5Y3uBp6VElg/2KZYMEfT97kL9P2XYW2AfQc1xQ
eaqkUIYa+iL2uOTEyPSd9ZGBZgBpyTipbOvMgqCrVGgRQkaB4AO5l2YPRPrLA6+2
jR2iGOba32diYNoAx/jkWJ2ZwBNKccmhhjFgXKdZWfZpnlN1pMpEr1Nj4T43rx7d
0MaCWnhwLbM=
=bisf
-----END PGP SIGNATURE-----

--bL35ULeiEXKGPY0P--


From nobody Thu Feb 19 07:11:43 2015
Return-Path: <markus.stenberg@iki.fi>
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 BF6F21A9077 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 07:11:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.121
X-Spam-Level: 
X-Spam-Status: No, score=-1.121 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_NEUTRAL=0.779] autolearn=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 e161FlrqpUqY for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 07:11:31 -0800 (PST)
Received: from kirsi2.inet.fi (mta-out1.inet.fi [62.71.2.195]) by ietfa.amsl.com (Postfix) with ESMTP id 51D771A9085 for <homenet@ietf.org>; Thu, 19 Feb 2015 07:11:28 -0800 (PST)
Received: from poro.lan (80.220.64.126) by kirsi2.inet.fi (8.5.142.08) (authenticated as stenma-47) id 54E3C7150003EA46; Thu, 19 Feb 2015 17:11:25 +0200
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Markus Stenberg <markus.stenberg@iki.fi>
In-Reply-To: <2531C6F7-5384-44D4-928E-80E68F8B8EE4@darou.fr>
Date: Thu, 19 Feb 2015 17:11:24 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <2FB6EA85-27C1-46B7-9216-2A0EF810FEB5@iki.fi>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <20150219082554.GH34798@Space.Net> <alpine.DEB.2.02.1502190931420.4007@uplift.swm.pp.se> <B52B6CCA-FDAE-4BC7-B876-133C8069404C@iki.fi> <2531C6F7-5384-44D4-928E-80E68F8B8EE4@darou.fr>
To: Pierre Pfister <pierre.pfister@darou.fr>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/gIRFX1dJ7HDtNnMDLGl_Hc34roM>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Markus Stenberg <markus.stenberg@iki.fi>, Gert Doering <gert@space.net>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 15:11:35 -0000

On 19.2.2015, at 16.50, Pierre Pfister <pierre.pfister@darou.fr> wrote:
>>> It's been what, 1.5-2 years since then? We've already noted that =
HNCP looks awfully close to a link state protocol and duplicates quite a =
lot of of functionality.
>> Right. It is essentially bit more modern take on a link state routing =
protocol. So if you bring it up, I bring up the another argument - why =
not route using it? Cost of doing _that_ is ~100 LoC (+ whatever fancy =
thing we want to do with metrics).
>=20
> First of all, because there are differences between assigning a prefix =
and using it for routing.=20
> - Assigning a prefix does not mean you are the best router to route =
toward it. It may not even mean it is assigned to a link you are =
directly connected to. It may also be an excluded prefix. Assigning a =
prefix just means you reserve that prefix for some usage. One of this =
usage happens to be =91prefix assignment to a link=92, but it may be =
others.

Well, we can officially add =91I haz this address on this interface=92 =
TLV if we care about it and then semantics would be exactly same as with =
e.g. IS-IS. Down to both using link state protocol to transmit the =
information.

> - There is a delay between the assignment and the actual use of a =
prefix. This is called =91Apply Delay=92 in the prefix assignment draft. =
I don=92t think routing based on assigned prefix TLVs is a good idea =
because you would not try to handle assigned prefixes collisions =
correctly.

Again, detail. Which can be addressed if we care enough. And at much =
smaller footprint than second link state database.

> Second point is that DNCP is going to transport multiple things. This =
will imply churn. As Gert said, I think protocols should do one thing =
and do it well. Babel is a loop-avoiding routing protocol. Do we want to =
put loop-avoidance mechanism in HNCP ? Of course not. Would HNCP be able =
to do routing ? Yes. But would it be able to do it if a buggy node =
constantly sends DNCP updates=85 It is less sure, and depends on the =
quality of the implementation.=20

Link state _with_ loops is hard. So I am not sure how this applies.

If buggy nodes happen _for anything_, very little is guaranteed. So =
strawman argument from my point of view.

> Last point is that the routing protocol we will agree on will not be =
the last we=92ll ever come-up with. Some other will be invented. Better =
ones. DNCP is an element with a set of requirements. Let=92s keep DNCP =
simple. A routing protocol has other requirements. And maybe some day we =
will decide to move to another routing protocol because we made a =
mistake or a new better routing protocol was designed. We need to make =
sure that this transition will be possible. And I think having an =
independent routing protocol running today will make this transition =
easier.

I thought the whole thing was to aim for bad transition mechanics; we =
originally proposed =91voting=92 mechanism which was extensible. Also, =
at some point, Steven suggested =91fallback as low priority default=92 =
(while running 0-N routing protocols on top of it with disjoint metric =
spaces). Again, not accepted. =91One routing protocol=92 does not sound =
like the option that is extensible in any direction. Except by saying =
that =91yeah, we have HNCP2=92 with zero-interoperability in either =
direction.

Cheers,

-Markus=


From nobody Thu Feb 19 07:17:56 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 AF8DA1A90F0 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 07:17:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.15
X-Spam-Level: 
X-Spam-Status: No, score=-0.15 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, HELO_EQ_FR=0.35] autolearn=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 2Trprq-8arg4 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 07:17:49 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 EF7CA1A90D3 for <homenet@ietf.org>; Thu, 19 Feb 2015 07:17:20 -0800 (PST)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t1JFHISQ010931; Thu, 19 Feb 2015 16:17:18 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id EC4AE2A0D9D; Thu, 19 Feb 2015 16:17:17 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id WsM2X9rqzUz5; Thu, 19 Feb 2015 16:17:07 +0100 (CET)
Received: from pirx.pps.jussieu.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 117022A0D7B; Thu, 19 Feb 2015 16:17:05 +0100 (CET)
Date: Thu, 19 Feb 2015 16:17:06 +0100
Message-ID: <874mqigcct.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Michael Thomas <mike@mtcc.com>
In-Reply-To: <54E58238.9030809@mtcc.com>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <54E58238.9030809@mtcc.com>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Thu, 19 Feb 2015 16:17:19 +0100 (CET)
X-Miltered: at korolev with ID 54E5FE7E.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54E5FE7E.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54E5FE7E.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/zb2ixCZRB3JfL11FUtsv7NDPm_Q>
Cc: homenet@ietf.org
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 15:17:55 -0000

> Is the load from routing protocols we're talking about likely to have
> any noticeable effect on the the forwarding rate?

Here are the figures given by H. Gredler on p.266 of "The Complete IS-IS
Routing Protocol" for a Cisco GRP 1200:

  Routers      Links   SPF time (ms)
    100         250       4,80
    200         500      12,42
    400        1000      31,22
    600        1500      52,94
    800        2000      76,67
    1000       2500     101,94

I have no idea how a Cisco GRP 1200 compares to a non-superscalar, 250 MHz
MIPS processor with a tiny cache.

-- Juliusz


From nobody Thu Feb 19 07:24:59 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 80E961A9115 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 07:24:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35] autolearn=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 VgxvK6TCip-7 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 07:24:56 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 B99861A9124 for <homenet@ietf.org>; Thu, 19 Feb 2015 07:21:16 -0800 (PST)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t1JFLFeG016333; Thu, 19 Feb 2015 16:21:15 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 518F92A0D7D; Thu, 19 Feb 2015 16:21:15 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id gre7xfvXEH1S; Thu, 19 Feb 2015 16:21:09 +0100 (CET)
Received: from pirx.pps.jussieu.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 4AFED2A0D39; Thu, 19 Feb 2015 16:21:09 +0100 (CET)
Date: Thu, 19 Feb 2015 16:21:10 +0100
Message-ID: <873862gc61.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Mikael Abrahamsson <swmike@swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1502190851300.4007@uplift.swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <54E58238.9030809@mtcc.com> <alpine.DEB.2.02.1502190851300.4007@uplift.swm.pp.se>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Thu, 19 Feb 2015 16:21:15 +0100 (CET)
X-Miltered: at korolev with ID 54E5FF6B.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54E5FF6B.001 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54E5FF6B.001 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/j3HS1QTPi28JV3E2Uq4Pqeu4Y1E>
Cc: homenet@ietf.org
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 15:24:57 -0000

> The complaints about the Erlang implementation has so far been on memory
> and flash footprint, not CPU resources and affecting performance. The
> above is true for most interpreted languages, such as python etc.

Just to clarify -- nobody's complaininng about the Erlang implementation,
which is a fine prototype.  People are complaining about the fact that
there is no implementation other than the Erlang implementation.

While we're willing to believe that it's not difficult to sit down and
write a relatively tight implementation of the (unspecified) Homenet
subset of IS-IS, it is a little worrying that nobody has actually done so.

-- Juliusz


From nobody Thu Feb 19 07:25:23 2015
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 4E2021A912F for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 07:25:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.661
X-Spam-Level: 
X-Spam-Status: No, score=-1.661 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 XrXvnmCJl5dR for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 07:25:14 -0800 (PST)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9E1341A9135 for <homenet@ietf.org>; Thu, 19 Feb 2015 07:21:54 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id BB98DA3; Thu, 19 Feb 2015 16:21:51 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1424359311; bh=S603IOZqhVps0kswQq4Hln066YxjiSl//PinPGamCa0=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=BxN4fnrOYSyedP6VVlcfPCtAq6yJIxbCCzRQ9pSB3qhJACyh9m5cnZGBHjvMHM78j /ymW4G6X6Jh1cWRAGJD9/KQWuGirHgQowbjGtla4S1A8Qqn8o21j4FJ1m23ILPiLXT t9KImc+K1uoQOr5T8mfPw4Hx8MnSzKVby03pbIDY=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id A0AFDA1; Thu, 19 Feb 2015 16:21:51 +0100 (CET)
Date: Thu, 19 Feb 2015 16:21:51 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Pierre Pfister <pierre.pfister@darou.fr>
In-Reply-To: <2531C6F7-5384-44D4-928E-80E68F8B8EE4@darou.fr>
Message-ID: <alpine.DEB.2.02.1502191618320.4007@uplift.swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <20150219082554.GH34798@Space.Net> <alpine.DEB.2.02.1502190931420.4007@uplift.swm.pp.se> <B52B6CCA-FDAE-4BC7-B876-133C8069404C@iki.fi> <2531C6F7-5384-44D4-928E-80E68F8B8EE4@darou.fr>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: MULTIPART/MIXED; BOUNDARY="-137064504-350059187-1424359311=:4007"
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/IXB2fJ2S7ER6qtYuCJvaimmHERE>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Markus Stenberg <markus.stenberg@iki.fi>, Gert Doering <gert@space.net>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 15:25:21 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

---137064504-350059187-1424359311=:4007
Content-Type: TEXT/PLAIN; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8BIT

On Thu, 19 Feb 2015, Pierre Pfister wrote:

> - There is a delay between the assignment and the actual use of a 
> prefix. This is called ‘Apply Delay’ in the prefix assignment draft. I 
> don’t think routing based on assigned prefix TLVs is a good idea because 
> you would not try to handle assigned prefixes collisions correctly.

Hi,

I was not proposing to use the HNCP TLVs for routing. Actually, I wasn't 
proposing to change the internal use of TLV movement much at all in HNCP, 
I was proposing to move them to IS-IS and use that to synchronize them 
instead of using the current transport. I do not see the fundamental 
difference in syncronizing TLVs between machines by means of HNCP (trickle 
based) and by means of a link state protocol (ISIS).

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se
---137064504-350059187-1424359311=:4007--


From nobody Thu Feb 19 07:35:28 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 32A481A90B7 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 07:35:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.15
X-Spam-Level: 
X-Spam-Status: No, score=-0.15 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, HELO_EQ_FR=0.35] autolearn=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 73RqQmoDKhjF for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 07:35:24 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 E966B1A90B0 for <homenet@ietf.org>; Thu, 19 Feb 2015 07:35:23 -0800 (PST)
Received: from potemkin.univ-paris7.fr (potemkin.univ-paris7.fr [IPv6:2001:660:3301:8000::1:1]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t1JFZM2h002767 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 19 Feb 2015 16:35:22 +0100
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by potemkin.univ-paris7.fr (8.14.4/8.14.4/relay2/56228) with ESMTP id t1JFZMxF010494; Thu, 19 Feb 2015 16:35:22 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 7F5472A0DC0; Thu, 19 Feb 2015 16:35:22 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id VqHwiHUeMjud; Thu, 19 Feb 2015 16:35:21 +0100 (CET)
Received: from pirx.pps.jussieu.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id E50052A0D7D; Thu, 19 Feb 2015 16:35:20 +0100 (CET)
Date: Thu, 19 Feb 2015 16:35:21 +0100
Message-ID: <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Mikael Abrahamsson <swmike@swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]); Thu, 19 Feb 2015 16:35:22 +0100 (CET)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Thu, 19 Feb 2015 16:35:22 +0100 (CET)
X-Miltered: at korolev with ID 54E602BA.005 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 54E602BA.003 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54E602BA.005 from potemkin.univ-paris7.fr/potemkin.univ-paris7.fr/null/potemkin.univ-paris7.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Enveloppe: 54E602BA.003 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54E602BA.005 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 54E602BA.003 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/4ZmayakOdyQd43kggfV7CMSyfik>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 15:35:25 -0000

> Also, currently most routers consists of mostly L2 high speed forwarding,
> with some L3 thrown in between two ports (the WAN port, and the 5th
> internal port to the 5 port switch chip with 4 external ports). With
> homenet, all this changes. Now all ports need to be L3.

I'm possibly missing something, but I see no requirement to perform L3
routing between the LAN ports.

> What platforms do the current implementations of Babel support?

The reference implementation supports Linux and multiple BSD variants
(tested on OpenBSD and Mac OS X).  The Quagga implementation supports
whatever Quagga supports.

At any rate, it is portable code -- making a new port consists in writing
a small number of platform-specific functions to interface with the kernel.

> Do we really believe people are going to use wifi links to connect
> devices within their homenet?

Yes.  The ability to simply and cheaply extend one's wireless coverage is
one of the killer features of Homenet, and one that can be easily explained.

-- Juliusz


From nobody Thu Feb 19 07:39:57 2015
Return-Path: <eckert@cisco.com>
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 EE7991A90EE for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 07:39:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -13.911
X-Spam-Level: 
X-Spam-Status: No, score=-13.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_31=0.6, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 a1Z-OFj3UPXh for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 07:39:51 -0800 (PST)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0ED8D1A90C4 for <homenet@ietf.org>; Thu, 19 Feb 2015 07:39:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2830; q=dns/txt; s=iport; t=1424360391; x=1425569991; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=hX80ob70G9UkET00CTIKMBWAcQl0z8hTIcdccl+AqaI=; b=G+XAl78vSarGBbE1e2sbOx82DRAFcpFL7aUjZQBusZn9VkMnHhfbUu5D 49hQQuLckDk5HH5yOEsKqeRqE2EbZXCnIoYfBZ+rUdPihexo/ZQt+o+Rt kkbdTsTa2sVgHhZxANuGo7bEkEjD2I8vWMETt/VYDJi7GjLxo/Jwm28CE A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AHBQDQAuZU/5RdJa1bgwbKCAKBIUMBAQEBAQF8hA8BAQEDATo/BQsLDgoJJQ8FSYg6CNMvAQEBAQEBAQEBAQEBAQEBAQEBAQEBF4sPhBZYB4MWgRQFikSORwGTIiKEDx2BM4FBAQEB
X-IronPort-AV: E=Sophos;i="5.09,609,1418083200"; d="scan'208";a="125090807"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by alln-iport-3.cisco.com with ESMTP; 19 Feb 2015 15:39:50 +0000
Received: from mcast-linux1.cisco.com (mcast-linux1.cisco.com [172.27.244.121]) by rcdn-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id t1JFdnPB018452 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 19 Feb 2015 15:39:50 GMT
Received: from mcast-linux1.cisco.com (localhost.cisco.com [127.0.0.1]) by mcast-linux1.cisco.com (8.13.8/8.13.8) with ESMTP id t1JFdiCD010542; Thu, 19 Feb 2015 07:39:49 -0800
Received: (from eckert@localhost) by mcast-linux1.cisco.com (8.13.8/8.13.8/Submit) id t1JFdcYZ010538; Thu, 19 Feb 2015 07:39:38 -0800
Date: Thu, 19 Feb 2015 07:39:38 -0800
From: Toerless Eckert <eckert@cisco.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Message-ID: <20150219153938.GA3935@cisco.com>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se>
User-Agent: Mutt/1.4.2.2i
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/Vksm9M_uYrEU5nt0f79-iJdP3_E>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Dave Taht <dave.taht@gmail.com>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 15:39:53 -0000

On Thu, Feb 19, 2015 at 08:43:26AM +0100, Mikael Abrahamsson wrote:
> >* While ram and flash have grown to be essentially "free" I really dont 
> >see home router and cpe makers rushing to embrace slower languages or 
> >bigger flash and memory requirements anytime soon.

This worry has been raised by others as well.

> That's because there has been no requirement to do so, most of the time. 
> Basically a device has been sold with a certain amount of features, and 
> this featureset hasn't changed over time, thus there is no need to 
> future-proof. I see this changing.

What are the indicators you see ?

> Also, currently most routers consists of mostly L2 high speed forwarding, 
> with some L3 thrown in between two ports (the WAN port, and the 5th 
> internal port to the 5 port switch chip with 4 external ports). With 
> homenet, all this changes. Now all ports need to be L3. This is a huge 
> change both when it comes to bandwidth needed from the CPU to the ports, 
> and also L3 performance needed. This will require home gateway 
> manufacturers to make very different devices.

Sure. But does homenet give them the right user benefits to make it
worth their while ?  Especially for gear that would not be OEM'ed by
SPs but in retail. 

How many commercial vendors are really selling boxes with OpenWRT (no
homenet) ? To me, OpenWRT (without homenet) has already a lot of
benefits over those vendor specific SW on home routers, but seemingly
that hasn't helped much to proliferate OpenWRT into commercial offerings.

> We also have the (previous) mobile SOC:s trickling down into the home 
> router space, and these are very price/performance efficient.

Just having looked for a good router for homenet, i am not really happy
yet with the choices available. Especially because i'd like to also run a bit more than just basic routing. >= 32MByte memory, >= 16MByte flash for
example. Still seems to be a very limited set of choices.

> Do we really believe people are going to use wifi links to connect devices 
> within their homenet?

Yes. Simply to extend reach. And if i understand it correctly,
If you have the typical setup:

   Internet - router/AP .... wireless1... client/bridge/AP ---- wired
                                                           .... wireless2

AFAIK, this setup is typically sometthing that only works well if
router/AP and client/bridge/AP come from same vendor due to the complexitites
in AP/bridge looking like multiple clients on wireless1. So it
looks like a good opportunity to highlight how homenet would turn
client/bridge/AP into client/router/AP and eliminate those problems,
allowing vendors of such devices to much easier get added - without
expecting that router/AP is upgrade/changed.

Cheers
    Toerless


From nobody Thu Feb 19 07:40:11 2015
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 AC3941A8932 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 07:40:09 -0800 (PST)
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 mSw_-XBaFonk for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 07:40:08 -0800 (PST)
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 B8DCD1A90C4 for <homenet@ietf.org>; Thu, 19 Feb 2015 07:40:06 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 95009A3; Thu, 19 Feb 2015 16:29:36 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1424359776; bh=Di2CE20n4/YWdamdWMnRTkpyhvb/rffS1XkM4XO4QkI=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=mSTwhCieLOC5zHelryOn9oe+gMKITPnPB2dzyrm8jW0dc8YOSRvfA6Kr3JsI5xNDs N90PmrlaDCQGIobF7Zj3Zs2w5HxFxIwFJz7GsVhdjIL+4pPRJ6hYCHJqerfs8mWB3g JGXkMW7PhmAxhSS9U+NCYk/IpD7Vs3a/SM+lMRDg=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 8E126A1; Thu, 19 Feb 2015 16:29:36 +0100 (CET)
Date: Thu, 19 Feb 2015 16:29:36 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
In-Reply-To: <874mqigcct.wl-jch@pps.univ-paris-diderot.fr>
Message-ID: <alpine.DEB.2.02.1502191622510.4007@uplift.swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <54E58238.9030809@mtcc.com> <874mqigcct.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/BAxauyDdUL76Gdg9hE1Mm2oetls>
Cc: homenet@ietf.org, Michael Thomas <mike@mtcc.com>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 15:40:09 -0000

On Thu, 19 Feb 2015, Juliusz Chroboczek wrote:

>> Is the load from routing protocols we're talking about likely to have
>> any noticeable effect on the the forwarding rate?
>
> Here are the figures given by H. Gredler on p.266 of "The Complete IS-IS
> Routing Protocol" for a Cisco GRP 1200:
>
>  Routers      Links   SPF time (ms)
>    100         250       4,80
>    200         500      12,42
>    400        1000      31,22
>    600        1500      52,94
>    800        2000      76,67
>    1000       2500     101,94
>
> I have no idea how a Cisco GRP 1200 compares to a non-superscalar, 250 MHz
> MIPS processor with a tiny cache.

Cisco 12000 with the original GRP (I guess this is what the book is 
referring to) sees to have used a 200Mhz R5000 processor with 512KB L2 
cache. The platform was released back in 1999 if I remember correctly.

From:

http://www.cisco.com/c/en/us/support/docs/routers/12000-series-routers/40060-12000-boot-process-40060.html

cisco 12410/GRP (R5000) processor (revision 0x01) with 524288K bytes of memory.
R5000 CPU at 200Mhz, Implementation 35, Rev 2.1, 512KB L2 Cache

On modern intel based platforms today, SPF calculations typically take a 
few milliseconds, even though the networks have grown larger.

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


From nobody Thu Feb 19 07:41:49 2015
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 5C2F71A90FE for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 07:41:47 -0800 (PST)
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 v4YU0K2u74Sx for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 07:41:45 -0800 (PST)
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 623D41A90F6 for <homenet@ietf.org>; Thu, 19 Feb 2015 07:41:45 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 022F1A5; Thu, 19 Feb 2015 16:41:43 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1424360504; bh=eQyc6l0yEOgW/6F1pd/8vRYlnEUbBKmfR72k7yqWGzA=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=01u2Obu5vWN/Sbk+LFHAzDo4xrw/h7IcwsddyXzZyb4NjWRUwwnZT6xGxX7MmfyPF 1YDZeX7l9rPV2NZNbKeeP3muuMW7uSGWMYKk3Lc5eU6xpNZhP5V/NczFrdN3XR4aHS 6DcCJuHnprMu1xOrudD7UAq6k1cXAUaNieonjHsU=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id F0535A4; Thu, 19 Feb 2015 16:41:43 +0100 (CET)
Date: Thu, 19 Feb 2015 16:41:43 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
In-Reply-To: <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr>
Message-ID: <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.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/_VW_9Fo9dCs0KqtXoXudmBH2WhM>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 15:41:47 -0000

On Thu, 19 Feb 2015, Juliusz Chroboczek wrote:

>> Also, currently most routers consists of mostly L2 high speed forwarding,
>> with some L3 thrown in between two ports (the WAN port, and the 5th
>> internal port to the 5 port switch chip with 4 external ports). With
>> homenet, all this changes. Now all ports need to be L3.
>
> I'm possibly missing something, but I see no requirement to perform L3
> routing between the LAN ports.

Really? Then you and me have fundamental difference in opinion what 
topologies we want to see in homenet. I want to see fewer broadcast 
domains. If we're going to keep the large L2 domains, then we don't really 
need homenet at all. The only reason to have homenet is if you're going to 
have a substantial amount of routers in arbitrary topology, that actually 
route. If we want to L2 switch most traffic, then we have made homenet 
unncessarily complex.

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


From nobody Thu Feb 19 07:52:27 2015
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 C91A81A90E0 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 07:52:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.061
X-Spam-Level: 
X-Spam-Status: No, score=-1.061 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, J_CHICKENPOX_31=0.6, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 oji0TXgCFLv7 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 07:52:24 -0800 (PST)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 84F631A87A1 for <homenet@ietf.org>; Thu, 19 Feb 2015 07:50:37 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id B56F9A5; Thu, 19 Feb 2015 16:50:35 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1424361035; bh=J1zegKT3sHMSeMfwOTXcfbWEbYXVqNDD+mWV5KOYxwQ=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=XY9sI43cgCwa/mogF6qT+6JZFqe7n0BJ1RKd2St2j184gD4y1IBuOxP5tHXo6dIRW Gpb+bewfBHFGHJZoNkCJGBdIkJ30yXY+nQVfdVzVYD3gRTF0hGqnQzE1Rf2FDxsl7N Xwak6FkAJrTLXK+TRxcijyENTOhbPaQ8zEU0AS3Y=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id AEAB9A4; Thu, 19 Feb 2015 16:50:35 +0100 (CET)
Date: Thu, 19 Feb 2015 16:50:35 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Toerless Eckert <eckert@cisco.com>
In-Reply-To: <20150219153938.GA3935@cisco.com>
Message-ID: <alpine.DEB.2.02.1502191641570.4007@uplift.swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <20150219153938.GA3935@cisco.com>
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/wMoPFoN-sJsF801tbWLt1PiIC7Y>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Dave Taht <dave.taht@gmail.com>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 15:52:25 -0000

On Thu, 19 Feb 2015, Toerless Eckert wrote:

>> That's because there has been no requirement to do so, most of the time.
>> Basically a device has been sold with a certain amount of features, and
>> this featureset hasn't changed over time, thus there is no need to
>> future-proof. I see this changing.
>
> What are the indicators you see ?

I see people starting to talk about putting sandboxed applications on the 
HGW:s, so you don't need a new box for each vendor application. I also (in 
NDA talks with some HW vendors) see mobile SoCs trickling down into the 
router space and these have very different performance numbers compared to 
the current low-performance devices.

I also see operators wanting to deploy new services quicker than they can 
today when in the current HGW incarnations most of the functonality is set 
at initial procurement time and then not much more happens over the 5+ 
year lifetime of the device.

> How many commercial vendors are really selling boxes with OpenWRT (no 
> homenet) ? To me, OpenWRT (without homenet) has already a lot of 
> benefits over those vendor specific SW on home routers, but seemingly 
> that hasn't helped much to proliferate OpenWRT into commercial 
> offerings.

I know commercial offerings that use OpenWRT. Unfortunately they are 
usually tied to the SoC vendor kernel because of device-specific "board 
support packages". I see these vendors putting pressure on the SoC 
manufacturers to stop doing this, because if you want to deploy new 
services but you're locked to a Linux 3.2 kernel because otherwise your 
packet accelerator won't work, this is a pain point.

So just the way it was really hard to buy "linux compatible" hardware in 
the 90ties (been there, felt the pain, had to buy 3c509), this is less of 
a problem today, and what I see is that more and more operators want to 
get "deeper" into their HGWs and control the software development 
themselves over time. See Free.fr for instance. In the project I am, we're 
not going to choose a device were we don't have significant control and 
can roll out own images and put on the HGWs.

> Just having looked for a good router for homenet, i am not really happy 
> yet with the choices available. Especially because i'd like to also run 
> a bit more than just basic routing. >= 32MByte memory, >= 16MByte flash 
> for example. Still seems to be a very limited set of choices.

Absolutely. Most devices sold today both to operators and end-users are 
"sell and forget". I am saying I am seeing this trend changing, albeit 
slowly.

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


From nobody Thu Feb 19 07:53:07 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 DBF661A895A for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 07:53:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35] autolearn=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 TEuB_nKzyDmq for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 07:53:04 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 0F20F1A19F8 for <homenet@ietf.org>; Thu, 19 Feb 2015 07:52:04 -0800 (PST)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t1JFq3MP024503; Thu, 19 Feb 2015 16:52:03 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 7DC4F2A0E0C; Thu, 19 Feb 2015 16:52:03 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id jtVZda4YzlB1; Thu, 19 Feb 2015 16:52:01 +0100 (CET)
Received: from pirx.pps.jussieu.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id D9A2C2A0DC0; Thu, 19 Feb 2015 16:52:00 +0100 (CET)
Date: Thu, 19 Feb 2015 16:52:01 +0100
Message-ID: <87zj89gaqm.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Mikael Abrahamsson <swmike@swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1502191235240.4007@uplift.swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <A5767F83-3D0C-40E5-A73B-912E3C160A42@fugue.com> <alpine.DEB.2.02.1502191235240.4007@uplift.swm.pp.se>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Thu, 19 Feb 2015 16:52:03 +0100 (CET)
X-Miltered: at korolev with ID 54E606A3.004 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54E606A3.004 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54E606A3.004 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/JASoOKv8GLQ4rVldvN0djhKgz-Q>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 15:53:06 -0000

>> Mikael, it is common practice to do air-to-air bridging on home networks
>> now.  We have discussed whether we want to support this in homenet, and
>> concluded that we must.  You are the first person as far as I can recall
>> to suggest that this was optional.  Yes, we do need a routing protocol
>> that works well when some of the transit networks are wifi
>> networks. This is not an edge case.

> Then we need to decide what kind of Wifi network we need to handle.
>
> Because if we're trying to support marginal performance mesh networks that
> might change all the time, lose packets, drop multicast packets randomly,
> etc, then those requirements need to be brought to the discussion.

I think that the very minimum requirement is that adding a marginal link
to a working network does not impact the performance of the previously
working part of the network: I don't see myself explaining to my users why
plugging in an extra wireless router in the attic causes their network to
become unusable.

Babel solves this particular issue by a combination of three mechanisms:
(1) automatically assigning a high metric to a marginal link, (2) using
hysteresis to avoid churn due to point 1 above, and (3) by ensuring that
routing loops don't occur even if routing data is not propagated in
a timely manner due to packet loss.

I'm pretty sure somebody sufficiently smart could design a similar scheme
for IS-IS, but be aware that it's somewhat more difficult to get right
than you might expect.  It took me a lot of experimentation to get the
hysteresis algorithm just right, and I'm still working on improving the
link quality algorithm.

-- Juliusz


From nobody Thu Feb 19 07:53:35 2015
Return-Path: <mellon@fugue.com>
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 59DAA1A90B0 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 07:53:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 Xitv3PFPIrtq for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 07:53:29 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id C6D0A1A89B5 for <homenet@ietf.org>; Thu, 19 Feb 2015 07:53:27 -0800 (PST)
Received: from [10.0.20.107] (c-71-233-43-215.hsd1.nh.comcast.net [71.233.43.215]) by toccata.fugue.com (Postfix) with ESMTPSA id A2C07238164C; Thu, 19 Feb 2015 10:53:26 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se>
Date: Thu, 19 Feb 2015 10:52:55 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se>
To: Mikael Abrahamsson <swmike@swm.pp.se>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/oT7vmV4L4HdniIhk50pvA5cQQto>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 15:53:31 -0000

On Feb 19, 2015, at 10:41 AM, Mikael Abrahamsson <swmike@swm.pp.se> =
wrote:
> Really? Then you and me have fundamental difference in opinion what =
topologies we want to see in homenet. I want to see fewer broadcast =
domains. If we're going to keep the large L2 domains, then we don't =
really need homenet at all. The only reason to have homenet is if you're =
going to have a substantial amount of routers in arbitrary topology, =
that actually route. If we want to L2 switch most traffic, then we have =
made homenet unncessarily complex.

So you are, I assume, advocating that all in-home switches also have one =
subnet per port?   I have a 16-port switch, and will probably have to =
add another, so that's going to consume a lot of prefixes.


From nobody Thu Feb 19 07:58:20 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 CF1751A19F8 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 07:58:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35] autolearn=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 7aglCu2Y7jTr for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 07:58:18 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 7F6591A9119 for <homenet@ietf.org>; Thu, 19 Feb 2015 07:57:43 -0800 (PST)
Received: from potemkin.univ-paris7.fr (potemkin.univ-paris7.fr [IPv6:2001:660:3301:8000::1:1]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t1JFvg81031568 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 19 Feb 2015 16:57:42 +0100
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by potemkin.univ-paris7.fr (8.14.4/8.14.4/relay2/56228) with ESMTP id t1JFvg0f005508; Thu, 19 Feb 2015 16:57:42 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 03F472A0E0C; Thu, 19 Feb 2015 16:57:42 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id Q1CX9ECr9IyH; Thu, 19 Feb 2015 16:57:40 +0100 (CET)
Received: from pirx.pps.jussieu.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 774BC2A0DC0; Thu, 19 Feb 2015 16:57:40 +0100 (CET)
Date: Thu, 19 Feb 2015 16:57:41 +0100
Message-ID: <87y4ntgah6.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Mikael Abrahamsson <swmike@swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]); Thu, 19 Feb 2015 16:57:42 +0100 (CET)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Thu, 19 Feb 2015 16:57:42 +0100 (CET)
X-Miltered: at korolev with ID 54E607F6.003 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 54E607F6.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54E607F6.003 from potemkin.univ-paris7.fr/potemkin.univ-paris7.fr/null/potemkin.univ-paris7.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Enveloppe: 54E607F6.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54E607F6.003 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 54E607F6.000 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/HzIwZ2pUq8yLEW8dvWfTAzXePd4>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 15:58:19 -0000

>> I'm possibly missing something, but I see no requirement to perform L3
>> routing between the LAN ports.

> Really? Then you and me have fundamental difference in opinion what
> topologies we want to see in homenet. I want to see fewer broadcast
> domains.

Ah, I see.

I was focusing on avoiding collision domains that contain both Ethernet
and WiFi.  I agree that the natural progression is to have L3 everywhere.

-- Juliusz


From nobody Thu Feb 19 08:05:09 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 836371A9136 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 08:05:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.349
X-Spam-Level: 
X-Spam-Status: No, score=0.349 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HELO_EQ_FR=0.35] autolearn=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 JKJmS8lq1Aph for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 08:05:05 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 418701A90EE for <homenet@ietf.org>; Thu, 19 Feb 2015 08:05:05 -0800 (PST)
Received: from potemkin.univ-paris7.fr (potemkin.univ-paris7.fr [IPv6:2001:660:3301:8000::1:1]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t1JG50Qj008892 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 19 Feb 2015 17:05:00 +0100
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by potemkin.univ-paris7.fr (8.14.4/8.14.4/relay2/56228) with ESMTP id t1JG50f8014511; Thu, 19 Feb 2015 17:05:00 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 356112A0E13; Thu, 19 Feb 2015 17:05:00 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id OZzFW-T_z420; Thu, 19 Feb 2015 17:04:58 +0100 (CET)
Received: from pirx.pps.jussieu.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 85FBC2A0DC0; Thu, 19 Feb 2015 17:04:58 +0100 (CET)
Date: Thu, 19 Feb 2015 17:04:59 +0100
Message-ID: <87wq3dga50.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Toerless Eckert <eckert@cisco.com>
In-Reply-To: <20150219153938.GA3935@cisco.com>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <20150219153938.GA3935@cisco.com>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]); Thu, 19 Feb 2015 17:05:00 +0100 (CET)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Thu, 19 Feb 2015 17:05:00 +0100 (CET)
X-Miltered: at korolev with ID 54E609AC.002 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 54E609AC.003 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54E609AC.002 from potemkin.univ-paris7.fr/potemkin.univ-paris7.fr/null/potemkin.univ-paris7.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Enveloppe: 54E609AC.003 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54E609AC.002 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 54E609AC.003 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/sUV0ftnoEXh4gDRDz_2uNebF1X0>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Dave Taht <dave.taht@gmail.com>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 16:05:06 -0000

>> Basically a device has been sold with a certain amount of features, and 
>> this featureset hasn't changed over time, thus there is no need to 
>> future-proof. I see this changing.
>
> What are the indicators you see ?

I suspect that the two of you may be making different assumptions.  Mikael
is thinking of ISP-provided CPEs (marketed as "boxes" in Europe), which
are slowly becoming fairly powerful devices.  Toerless is thinking of
Plastic Home Routers, which have been stuck at 4MB flash and 8MB RAM for
as long as anyone can remember.

IMHO, both kinds of devices are necessary to the success of Homenet.

-- Juliusz


From nobody Thu Feb 19 08:20:28 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 7A1221A9140 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 08:20:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35] autolearn=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 xzu65-wV4YpX for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 08:20:24 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 2EF2F1A19F8 for <homenet@ietf.org>; Thu, 19 Feb 2015 08:20:24 -0800 (PST)
Received: from potemkin.univ-paris7.fr (potemkin.univ-paris7.fr [IPv6:2001:660:3301:8000::1:1]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t1JGKM2e026218 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 19 Feb 2015 17:20:22 +0100
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by potemkin.univ-paris7.fr (8.14.4/8.14.4/relay2/56228) with ESMTP id t1JGKMiZ031007; Thu, 19 Feb 2015 17:20:22 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id BA7392A0E78; Thu, 19 Feb 2015 17:20:22 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id AA07vgi4baLN; Thu, 19 Feb 2015 17:20:21 +0100 (CET)
Received: from pirx.pps.jussieu.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 207D92A0DC0; Thu, 19 Feb 2015 17:20:21 +0100 (CET)
Date: Thu, 19 Feb 2015 17:20:21 +0100
Message-ID: <87vbixg9fe.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Mikael Abrahamsson <swmike@swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1502191622510.4007@uplift.swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <54E58238.9030809@mtcc.com> <874mqigcct.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191622510.4007@uplift.swm.pp.se>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]); Thu, 19 Feb 2015 17:20:22 +0100 (CET)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Thu, 19 Feb 2015 17:20:22 +0100 (CET)
X-Miltered: at korolev with ID 54E60D46.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 54E60D46.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54E60D46.001 from potemkin.univ-paris7.fr/potemkin.univ-paris7.fr/null/potemkin.univ-paris7.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Enveloppe: 54E60D46.001 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54E60D46.001 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 54E60D46.001 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/uOMVJDRrOgd2wHtFe-sh8GcLmN0>
Cc: homenet@ietf.org
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 16:20:25 -0000

>> Here are the figures given by H. Gredler on p.266 of "The Complete IS-IS
>> Routing Protocol" for a Cisco GRP 1200:
>>
>> Routers      Links   SPF time (ms)
>> 100         250       4,80
>> 200         500      12,42
>> 400        1000      31,22
>> 600        1500      52,94
>> 800        2000      76,67
>> 1000       2500     101,94

> Cisco 12000 with the original GRP (I guess this is what the book is
> referring to) sees to have used a 200Mhz R5000 processor with 512KB L2
> cache.

Since SPF makes random memory accesses, that's probably 10-100 times faster
than a MIPS 4KEc at 250 MHz with its 8KB data cache.

So Homenet probably can afford to make one SPF every second, assuming
a carefully crafted, native-code implementation of SPF.  Which is probably
achievable, but would seem to argue in favour of some smart rate limiting.

You're almost tempting me into trying my hand at it ;-)

-- Juliusz


From nobody Thu Feb 19 08:27:50 2015
Return-Path: <cyrus@openwrt.org>
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 7C22F1A8898 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 08:27:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.25
X-Spam-Level: 
X-Spam-Status: No, score=-2.25 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-0.7] 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 wBf1jepJFzfm for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 08:27:47 -0800 (PST)
Received: from mail.core-networks.de (mail.core-networks.de [82.96.72.7]) by ietfa.amsl.com (Postfix) with ESMTP id D72361A9218 for <homenet@ietf.org>; Thu, 19 Feb 2015 08:27:46 -0800 (PST)
Received: from localhost ([127.0.0.1]) by mail.core-networks.de id 1YOTx1-0004dE-0x with ESMTPSA (TLSv1.2:DHE-RSA-AES128-SHA:128) for ; Thu, 19 Feb 2015 17:27:43 +0100
Message-ID: <54E60EFB.1060004@openwrt.org>
Date: Thu, 19 Feb 2015 17:27:39 +0100
From: Steven Barth <cyrus@openwrt.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.4.0
MIME-Version: 1.0
To: Mikael Abrahamsson <swmike@swm.pp.se>,  Pierre Pfister <pierre.pfister@darou.fr>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <20150219082554.GH34798@Space.Net> <alpine.DEB.2.02.1502190931420.4007@uplift.swm.pp.se> <B52B6CCA-FDAE-4BC7-B876-133C8069404C@iki.fi> <2531C6F7-5384-44D4-928E-80E68F8B8EE4@darou.fr> <alpine.DEB.2.02.1502191618320.4007@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1502191618320.4007@uplift.swm.pp.se>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/10QKpctlLsqz0whAHwvzdBD5i3w>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Markus Stenberg <markus.stenberg@iki.fi>, Gert Doering <gert@space.net>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 16:27:49 -0000

>
> I was not proposing to use the HNCP TLVs for routing. Actually, I 
> wasn't proposing to change the internal use of TLV movement much at 
> all in HNCP, I was proposing to move them to IS-IS and use that to 
> synchronize them instead of using the current transport. I do not see 
> the fundamental difference in syncronizing TLVs between machines by 
> means of HNCP (trickle based) and by means of a link state protocol 
> (ISIS).

One of the problems here I think is that it runs on L2, thus you cannot 
simply encrypt and / or asymmetrical authenticate it with anything like 
IPsec or (D)TLS. Therefore you would need to actually define, maintain 
and implement your own IS-IS specific TLS or IKE-like protocol which 
would actually add a lot more complexity than DNCP as a transport does.

Actually one might even argue in the opposite direction that unless the 
IGP offers some fancy dynamic metrics based on e.g. bandwidth or 
reliablity etc., what would be the point of combining HNCP with a 
single-area LSP if you might as well do a simple graph traversal on the 
HNCP topology to generate routes?


From nobody Thu Feb 19 08:40:23 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 AE0461A892C for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 08:40:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35] autolearn=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 Wm3GLZUktuUC for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 08:40:21 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 724DA1A876E for <homenet@ietf.org>; Thu, 19 Feb 2015 08:40:21 -0800 (PST)
Received: from potemkin.univ-paris7.fr (potemkin.univ-paris7.fr [IPv6:2001:660:3301:8000::1:1]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t1JGeIB9013890 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 19 Feb 2015 17:40:19 +0100
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by potemkin.univ-paris7.fr (8.14.4/8.14.4/relay2/56228) with ESMTP id t1JGeIba017792; Thu, 19 Feb 2015 17:40:18 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id DBCD62A0EA9; Thu, 19 Feb 2015 17:40:18 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id wOF5-5JFM-RE; Thu, 19 Feb 2015 17:40:17 +0100 (CET)
Received: from pirx.pps.jussieu.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 70AF22A0EA8; Thu, 19 Feb 2015 17:40:16 +0100 (CET)
Date: Thu, 19 Feb 2015 17:40:17 +0100
Message-ID: <87sie1g8i6.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Steven Barth <cyrus@openwrt.org>
In-Reply-To: <54E60EFB.1060004@openwrt.org>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <20150219082554.GH34798@Space.Net> <alpine.DEB.2.02.1502190931420.4007@uplift.swm.pp.se> <B52B6CCA-FDAE-4BC7-B876-133C8069404C@iki.fi> <2531C6F7-5384-44D4-928E-80E68F8B8EE4@darou.fr> <alpine.DEB.2.02.1502191618320.4007@uplift.swm.pp.se> <54E60EFB.1060004@openwrt.org>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]); Thu, 19 Feb 2015 17:40:20 +0100 (CET)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Thu, 19 Feb 2015 17:40:18 +0100 (CET)
X-Miltered: at korolev with ID 54E611F2.002 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 54E611F2.004 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54E611F2.002 from potemkin.univ-paris7.fr/potemkin.univ-paris7.fr/null/potemkin.univ-paris7.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Enveloppe: 54E611F2.004 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54E611F2.002 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 54E611F2.004 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/RbsdSBYMGl9DPYE3EVQg11WoLiM>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 16:40:22 -0000

> Actually one might even argue in the opposite direction that unless the
> IGP offers some fancy dynamic metrics based on e.g. bandwidth or
> reliablity etc., what would be the point of combining HNCP with
> a single-area LSP if you might as well do a simple graph traversal on the
> HNCP topology to generate routes?

The Commission for Truth in Advertising requests that I mention that we
haven't evaluated HNCP's behaviour in unstable and marginal networks yet.

(But we will.)

-- Juliusz


From nobody Thu Feb 19 09:01:35 2015
Return-Path: <cyrus@openwrt.org>
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 B838A1AC3B7 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 09:01:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.25
X-Spam-Level: 
X-Spam-Status: No, score=-2.25 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-0.7] 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 RWAGQh_TrM_u for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 09:01:32 -0800 (PST)
Received: from mail.core-networks.de (mail.core-networks.de [82.96.72.7]) by ietfa.amsl.com (Postfix) with ESMTP id 6C2591AC3B5 for <homenet@ietf.org>; Thu, 19 Feb 2015 09:01:32 -0800 (PST)
Received: from localhost ([127.0.0.1]) by mail.core-networks.de id 1YOUTh-0005n1-17 with ESMTPSA (TLSv1.2:DHE-RSA-AES128-SHA:128) for ; Thu, 19 Feb 2015 18:01:29 +0100
Message-ID: <54E616E7.7080103@openwrt.org>
Date: Thu, 19 Feb 2015 18:01:27 +0100
From: Steven Barth <cyrus@openwrt.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.4.0
MIME-Version: 1.0
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com>	<54E48963.5030109@globis.net>	<874mqj715b.wl-jch@pps.univ-paris-diderot.fr>	<alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se>	<87d2575hay.wl-jch@pps.univ-paris-diderot.fr>	<CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com>	<CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com>	<alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se>	<20150219082554.GH34798@Space.Net>	<alpine.DEB.2.02.1502190931420.4007@uplift.swm.pp.se>	<B52B6CCA-FDAE-4BC7-B876-133C8069404C@iki.fi>	<2531C6F7-5384-44D4-928E-80E68F8B8EE4@darou.fr>	<alpine.DEB.2.02.1502191618320.4007@uplift.swm.pp.se>	<54E60EFB.1060004@openwrt.org> <87sie1g8i6.wl-jch@pps.univ-paris-diderot.fr>
In-Reply-To: <87sie1g8i6.wl-jch@pps.univ-paris-diderot.fr>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/fPzDJqbknB2wvTx8NbJ0gEkGZZc>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 17:01:33 -0000

>
> The Commission for Truth in Advertising requests that I mention that we
> haven't evaluated HNCP's behaviour in unstable and marginal networks yet.
I agree, however this would need to be adressed anyway and irregardless 
of the chosen IGP that runs alongside it. I mean the IGP working but 
HNCP failing wouldn't really help the case.

My point is just that I don't see much use in moving away from DNCP (and 
the current profile) as a transport for HNCP unless there is something 
better (i.e. supporting asymmetrical cryptography and encryption in a 
sane way and is proven to work in maginal networks).


From nobody Thu Feb 19 09:04:46 2015
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 BBF631A89C7 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 09:04:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.661
X-Spam-Level: 
X-Spam-Status: No, score=-1.661 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 HeoRjL0MZsW9 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 09:04:43 -0800 (PST)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 129DE1AC3BB for <homenet@ietf.org>; Thu, 19 Feb 2015 09:04:25 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 00150A5; Thu, 19 Feb 2015 18:04:22 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1424365463; bh=b0yYa3SJvne6qdLvXrqxbLbB78cLy8btbHpAnt5Oh/w=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=WNRNUuZvA1xQoibnXGYm3LEcX3LrJBBdZbq+cY+RgW2CLrIwb9l70moVA1SC66sEZ Ac0BVdkyUIk4RsvhIU1urbb3Cj3t0WslwZeIxIuPiqTsRents8e0rJWHkviL13rw03 o/SnQdsVOFWzFefkU9RHsDS+Epo6r9oV7WOJ6JKY=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id EF0DDA4; Thu, 19 Feb 2015 18:04:22 +0100 (CET)
Date: Thu, 19 Feb 2015 18:04:22 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
In-Reply-To: <87zj89gaqm.wl-jch@pps.univ-paris-diderot.fr>
Message-ID: <alpine.DEB.2.02.1502191804050.4007@uplift.swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <A5767F83-3D0C-40E5-A73B-912E3C160A42@fugue.com> <alpine.DEB.2.02.1502191235240.4007@uplift.swm.pp.se> <87zj89gaqm.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/znV2-1t_LlngK7yYwu3zyGiWEGU>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 17:04:44 -0000

On Thu, 19 Feb 2015, Juliusz Chroboczek wrote:

> Babel solves this particular issue by a combination of three mechanisms:
> (1) automatically assigning a high metric to a marginal link, (2) using

How is a "marginal link" defined/detected?

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


From nobody Thu Feb 19 09:05:34 2015
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 804181A8931 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 09:05:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.661
X-Spam-Level: 
X-Spam-Status: No, score=-1.661 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 sam3dh51Bnur for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 09:05:31 -0800 (PST)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 742071A8833 for <homenet@ietf.org>; Thu, 19 Feb 2015 09:05:31 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 0E885A5; Thu, 19 Feb 2015 18:05:30 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1424365530; bh=8+s9FRUmRGTJW65NW7PqlEF6l+sQC+YQp2V4n/WePbw=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=axqUxqeQJi+wiNjH1Pm6BPQ5/18yFSSud2Sx9Hu6DajK5NK2LWpveIGFnCae7pn0V a2kcMBXgZ6coQZd7+JXn5rEcTT0k1WYgzEblwnqQGzcUeNujcWbmBQH8JMZtT6ANGp Yb+Eu01UHlR2e0UzJnBq5IFw78i9eQlVmJLO8TsY=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 06543A4; Thu, 19 Feb 2015 18:05:30 +0100 (CET)
Date: Thu, 19 Feb 2015 18:05:29 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Ted Lemon <mellon@fugue.com>
In-Reply-To: <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com>
Message-ID: <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com>
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/bG9fkJU7muEzV390K6GCj0ZMAfY>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 17:05:32 -0000

On Thu, 19 Feb 2015, Ted Lemon wrote:

> So you are, I assume, advocating that all in-home switches also have one 
> subnet per port?  I have a 16-port switch, and will probably have to add 
> another, so that's going to consume a lot of prefixes.

Yes. I don't see the problem with this.

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


From nobody Thu Feb 19 09:09:29 2015
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 A650D1A89E1 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 09:09:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.661
X-Spam-Level: 
X-Spam-Status: No, score=-1.661 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 vMwtttLvy78J for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 09:09:26 -0800 (PST)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7371B1A8853 for <homenet@ietf.org>; Thu, 19 Feb 2015 09:09:26 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 0B43AA5; Thu, 19 Feb 2015 18:09:25 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1424365765; bh=/sH9SHPvibfxUKm2U+ryeN3w2GWToZgVFaWIHPtcS+8=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=UgnJd0xLhegq8F67UeY0rr/0Q8RC8ZHLUNTn605KsmyCmaUtKcAmQGL3WMOmlto36 YUF7cCU6QcnxEVVFWUo55VJvpxNyVtDPgLCDvXX07770WJILd2UJgFWtm6cCbe7IaP Puhy02pWXUCfpgwOpAPq0HCqhdw1cyppHs+R9Vck=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 03EF1A4; Thu, 19 Feb 2015 18:09:25 +0100 (CET)
Date: Thu, 19 Feb 2015 18:09:24 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
In-Reply-To: <87vbixg9fe.wl-jch@pps.univ-paris-diderot.fr>
Message-ID: <alpine.DEB.2.02.1502191806381.4007@uplift.swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <54E58238.9030809@mtcc.com> <874mqigcct.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191622510.4007@uplift.swm.pp.se> <87vbixg9fe.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/S44TTVbyQWSxUclBDQT75mhArgY>
Cc: homenet@ietf.org
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 17:09:27 -0000

On Thu, 19 Feb 2015, Juliusz Chroboczek wrote:

> Since SPF makes random memory accesses, that's probably 10-100 times 
> faster than a MIPS 4KEc at 250 MHz with its 8KB data cache.

I don't know if this is true or not. I know ISIS was running on Cisco 2500 
routers (which are motorola 68030 at 20MHz. I've had these kinds of 
devices involved in the "single level" ISIS domain for a fairly large 
network (I believe it contained 400 routers, 1300 ISIS "nodes" if I 
remember correctly).

> So Homenet probably can afford to make one SPF every second, assuming
> a carefully crafted, native-code implementation of SPF.  Which is probably
> achievable, but would seem to argue in favour of some smart rate limiting.

ISIS already has these kinds of "rate-limiting" of how things are 
happening. In modern core routers this is often tuned to a lot more 
agressive levels, because the defaults came from the early 90ties where 
the same CPU was used for both control plane and forwarding.

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


From nobody Thu Feb 19 09:19:28 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 A802C1A033B for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 09:19:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35] autolearn=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 OTeoCNCD1pmr for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 09:19:25 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 721B81A014D for <homenet@ietf.org>; Thu, 19 Feb 2015 09:19:25 -0800 (PST)
Received: from potemkin.univ-paris7.fr (potemkin.univ-paris7.fr [IPv6:2001:660:3301:8000::1:1]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t1JHJNW9013619 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 19 Feb 2015 18:19:23 +0100
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by potemkin.univ-paris7.fr (8.14.4/8.14.4/relay2/56228) with ESMTP id t1JHJNeC015079; Thu, 19 Feb 2015 18:19:23 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id BE65F2A0F01; Thu, 19 Feb 2015 18:19:23 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id uHL4LLID98gU; Thu, 19 Feb 2015 18:19:22 +0100 (CET)
Received: from pirx.pps.jussieu.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 2A5962A0EBF; Thu, 19 Feb 2015 18:19:21 +0100 (CET)
Date: Thu, 19 Feb 2015 18:19:21 +0100
Message-ID: <87mw49g6p2.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Mikael Abrahamsson <swmike@swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1502191804050.4007@uplift.swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <A5767F83-3D0C-40E5-A73B-912E3C160A42@fugue.com> <alpine.DEB.2.02.1502191235240.4007@uplift.swm.pp.se> <87zj89gaqm.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191804050.4007@uplift.swm.pp.se>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]); Thu, 19 Feb 2015 18:19:23 +0100 (CET)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Thu, 19 Feb 2015 18:19:23 +0100 (CET)
X-Miltered: at korolev with ID 54E61B1B.002 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 54E61B1B.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54E61B1B.002 from potemkin.univ-paris7.fr/potemkin.univ-paris7.fr/null/potemkin.univ-paris7.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Enveloppe: 54E61B1B.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54E61B1B.002 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 54E61B1B.000 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/CvLHni6O2h2fDjsG6My-q1WSj6Q>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 17:19:26 -0000

>> Babel solves this particular issue by a combination of three mechanisms:
>> (1) automatically assigning a high metric to a marginal link, (2) using

> How is a "marginal link" defined/detected?

The current implementation uses ETX (MobiCom 2003), which is not very good
but relatively easy to implement portably.  See Appendix A2 of RFC 6126
for the gritty details.

(In true truth the it uses something called Z3, which combines ETX with
interference avoidance, and which I haven't published yet.)

We're planning to do something smarter in the future by hooking into
Linux's rate estimator (the idea is due to Dave), but we've got plenty of
more urgent work.  (Such as merging the source-specific code and writing
a paper about Z3.)

At any rate, the current ETX code will remain for non-Linux platforms.

-- Juliusz


From nobody Thu Feb 19 09:22:53 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 6C41A1A039C for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 09:22:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35] autolearn=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 HVE_Lk_PBFCS for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 09:22:51 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 9501A1A1B2F for <homenet@ietf.org>; Thu, 19 Feb 2015 09:22:49 -0800 (PST)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t1JHMmrL015653; Thu, 19 Feb 2015 18:22:48 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 380F52A0F01; Thu, 19 Feb 2015 18:22:48 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id tWfXZqD4FjUN; Thu, 19 Feb 2015 18:22:46 +0100 (CET)
Received: from pirx.pps.jussieu.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id BB7422A0EBF; Thu, 19 Feb 2015 18:22:46 +0100 (CET)
Date: Thu, 19 Feb 2015 18:22:47 +0100
Message-ID: <87lhjtg6jc.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Mikael Abrahamsson <swmike@swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1502191806381.4007@uplift.swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <54E58238.9030809@mtcc.com> <874mqigcct.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191622510.4007@uplift.swm.pp.se> <87vbixg9fe.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191806381.4007@uplift.swm.pp.se>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Thu, 19 Feb 2015 18:22:48 +0100 (CET)
X-Miltered: at korolev with ID 54E61BE8.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54E61BE8.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54E61BE8.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/kP2bN9jwIb3Dstszkl4YNgSbw1c>
Cc: homenet@ietf.org
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 17:22:52 -0000

>> smart rate limiting.

> ISIS already has these kinds of "rate-limiting" of how things are
> happening. In modern core routers this is often tuned

If you need to tune it, it's not smart enough.

-- Juliusz


From nobody Thu Feb 19 09:33:33 2015
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 51B661A039C for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 09:33:31 -0800 (PST)
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 Uks67-ueF5sQ for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 09:33:26 -0800 (PST)
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 47C841A001C for <homenet@ietf.org>; Thu, 19 Feb 2015 09:33:26 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id EDB82A5; Thu, 19 Feb 2015 18:33:23 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1424367203; bh=j5arLdABXsWVov8yYy80RIygRkDS+cFp6OCvMYfXuBE=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=0/7KtKURpfhXJiX1VJEks6siktXarIEIo4hiatNp4e4qlMHo/lWDDiOnf7DgXVEAu y+ioTUpzk1HHQhaQgp/pAbF5y8+xzetrhWSRUtkP9ymV1tQFQxufbl/5u/TWIuj1e8 wjceoeYEVCifI3gtKrqAakVs+c8WETi8O4uMuQwI=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id E50CCA4; Thu, 19 Feb 2015 18:33:23 +0100 (CET)
Date: Thu, 19 Feb 2015 18:33:23 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
In-Reply-To: <87lhjtg6jc.wl-jch@pps.univ-paris-diderot.fr>
Message-ID: <alpine.DEB.2.02.1502191826230.4007@uplift.swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <54E58238.9030809@mtcc.com> <874mqigcct.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191622510.4007@uplift.swm.pp.se> <87vbixg9fe.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191806381.4007@uplift.swm.pp.se> <87lhjtg6jc.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/tck5-ZlkW6XCVdgnOm43Vdhyzx4>
Cc: homenet@ietf.org
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 17:33:31 -0000

On Thu, 19 Feb 2015, Juliusz Chroboczek wrote:

>>> smart rate limiting.
>
>> ISIS already has these kinds of "rate-limiting" of how things are
>> happening. In modern core routers this is often tuned
>
> If you need to tune it, it's not smart enough.

Can babel achieve 200ms convergence times across a network that might span 
continents, out of the box without changing anything? I doubt it.

I don't believe in fit-all default behaviour. I don't even believe in this 
for TCP even. I tune TCP all the time, because TCP has been designed to 
fit everything from 1200 bps links to 100GE links, it doesn't fit each end 
of the extremes very well. This doesn't mean TCP isn't smart (enough) to 
work well in most cases.

Sure, ISIS could be made smarter when it comes to this, but it all comes 
down to what the requirements are. Right now when we started to evaluate 
routing protocols, people started pitching USP for their perticular 
favorite, and we found out we weren't even on the same page when it comes 
to requirements, and even what a homenet looks like.

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


From nobody Thu Feb 19 09:41:48 2015
Return-Path: <John_Leddy@cable.comcast.com>
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 379E11A1AF8 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 09:41:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.225
X-Spam-Level: 
X-Spam-Status: No, score=0.225 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 rcdfd9Xe5ggF for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 09:41:46 -0800 (PST)
Received: from copdcmhout01.cable.comcast.com (copdcmhout01.cable.comcast.com [162.150.44.71]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CA29F1A1AC6 for <homenet@ietf.org>; Thu, 19 Feb 2015 09:41:46 -0800 (PST)
X-AuditID: a2962c47-f795e6d000005066-21-54e62059eb91
Received: from PACDCEXHUB03.cable.comcast.com (pacdcexhub03.cable.comcast.com [24.40.56.116]) by copdcmhout01.cable.comcast.com (SMTP Gateway) with SMTP id CD.D8.20582.95026E45; Thu, 19 Feb 2015 10:41:46 -0700 (MST)
Received: from PACDCEXMB22.cable.comcast.com ([fe80::f887:1b71:477f:d14b]) by PACDCEXHUB03.cable.comcast.com ([fe80::7da6:458a:eadf:dadb%16]) with mapi id 14.03.0181.006; Thu, 19 Feb 2015 12:41:45 -0500
From: "Leddy, John" <John_Leddy@cable.comcast.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Thread-Topic: [homenet] Routing protocol comparison document
Thread-Index: AQHQTGYbpljA4qO18ECjoj8KcSEQaZz4PdmA
Date: Thu, 19 Feb 2015 17:41:44 +0000
Message-ID: <D10B8924.6BD5%John_Leddy@cable.comcast.com>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <A5767F83-3D0C-40E5-A73B-912E3C160A42@fugue.com> <alpine.DEB.2.02.1502191235240.4007@uplift.swm.pp.se> <87zj89gaqm.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191804050.4007@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1502191804050.4007@uplift.swm.pp.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.4.7.141117
x-originating-ip: [24.40.1.154]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <41405368E9843548B75316932E906704@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrHIsWRmVeSWpSXmKPExsUioWFRohul8CzE4MEqPov3iw6xWHz+9I/V 4uXSrWwOzB5Llvxk8ri4+x2jx99JD5kCmKO4bFJSczLLUov07RK4MqbeW8lcMIuv4vWKXuYG xk3cXYwcHBICJhLHP4d2MXICmWISF+6tZ+ti5OIQErjJKHFu9gtGCOcco8TsrW2sIFVsAkYS N1dtYQSxRQTiJba3H2ABGcQsoC9x/6c4iCksYC2xpMUDosJGYv+qVnYI20ji/5MzLCA2i4Cq RPei9WBTeAUsJFa9es8KsWo+q8TpG1vBGjgFnCRmNR8Fa2AEOu77qTVMIDazgLjErSfzmSCO FpBYsuc8M4QtKvHy8T+wM0UF9CRWXm9ig4jLS8z4/QaqV0/ixtQpbBC2g8TF5r9QcW2JZQtf M0McJChxcuYTlgmMErOQrJuFpH0WkvZZSNpnIWlfwMi6ilEuOb8gJTk3I7+0xMBQLzkxKSdV Lzk/NzmxuAREb2IExuqiaTruOxgv9DofYhTgYFTi4V0q+CxEiDWxrLgy9xCjBAezkgjvfk6g EG9KYmVValF+fFFpTmrxIUZpDhYlcd5rJjtChATSE0tSs1NTC1KLYLJMHJxSDYyJRbe/8c6x KItd/ThdPCm8THJyzP7MVVmOP1dIHXL+lb72mPV3XlODeIGju0PPzvXbqzrV+5DHd49btqxm zyaHFVXumLguJfX94pkaNtNZ4pezz/A78nHNB92YfeI7o63O/16RPG+1UcSqxn7/Kd3XZGb/ /ZMx589FfTarrxpC15QvZk/e8m+7EktxRqKhFnNRcSIA36cADdECAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/e7NO6t05ATcjeEkzoHqpY6yJ_H4>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 17:41:48 -0000

Trying to understand the =B3marginal link=B2 definition as well:

Seems like =B3marginal link=B2 is associated with the IGP behavior (static,
DV, link state)

I=B9m assuming:
If the L2 domain signals to the IGP that the link is =B3down=B2, the link i=
s
down.  Even if it does it a lot.  You need to =B3hide=B2 it from the IGP to
create a =B3marginal link=B2.
=B3marginal link=B2 does not say anything about user QOE, throughput or pac=
ket
loss directly.  A link that can hold an adjacency, but is dropping user
traffic, would not be a =B3marginal link=B2 in this case.

Good Link - Link that can form an IGP adjacency and hold it consistently
in the absence of a L2 domain down state.
Bad Link - Link that cannot form an IGP adjacency.  It can be because of a
L2 domain down state, or other cause.
Marginal Link - Link that can form but not hold an IGP adjacency
consistently in the absence of a L2 domain down state.

So for a =B3marginal link=B2:

Hide L2 UP/DOWN state from the IGP (if desired)
Form an adjacency
Exchange any routing info
Don=B9t send any Hello=B9s to actively take down the adjacency
Break adjacency only if routing info updates can=B9t be sent or DOWN state
received

Is this close to what a =B3marginal link=B2 is?

John



On 2/19/15, 12:04 PM, "Mikael Abrahamsson" <swmike@swm.pp.se> wrote:

>On Thu, 19 Feb 2015, Juliusz Chroboczek wrote:
>
>> Babel solves this particular issue by a combination of three mechanisms:
>> (1) automatically assigning a high metric to a marginal link, (2) using
>
>How is a "marginal link" defined/detected?
>
>--=20
>Mikael Abrahamsson    email: swmike@swm.pp.se
>
>_______________________________________________
>homenet mailing list
>homenet@ietf.org
>https://www.ietf.org/mailman/listinfo/homenet
>


From nobody Thu Feb 19 09:54:52 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 4A1751A001C for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 09:54:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35] autolearn=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 FookrEf0ZVPB for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 09:54:49 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 E40F41A0015 for <homenet@ietf.org>; Thu, 19 Feb 2015 09:54:48 -0800 (PST)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t1JHsgTm004812; Thu, 19 Feb 2015 18:54:42 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id DD7062A0F7F; Thu, 19 Feb 2015 18:54:42 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id tH6YNPnzyZ0r; Thu, 19 Feb 2015 18:54:41 +0100 (CET)
Received: from pirx.pps.jussieu.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 603602A0F6F; Thu, 19 Feb 2015 18:54:38 +0100 (CET)
Date: Thu, 19 Feb 2015 18:54:38 +0100
Message-ID: <87h9uhg529.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: "Leddy, John" <John_Leddy@cable.comcast.com>
In-Reply-To: <D10B8924.6BD5%John_Leddy@cable.comcast.com>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <A5767F83-3D0C-40E5-A73B-912E3C160A42@fugue.com> <alpine.DEB.2.02.1502191235240.4007@uplift.swm.pp.se> <87zj89gaqm.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191804050.4007@uplift.swm.pp.se> <D10B8924.6BD5%John_Leddy@cable.comcast.com>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Thu, 19 Feb 2015 18:54:43 +0100 (CET)
X-Miltered: at korolev with ID 54E62362.004 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54E62362.004 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54E62362.004 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/JrG-3ZAUb8RkZZYL3LncL1kiFGs>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 17:54:50 -0000

> Seems like ³marginal link² is associated with the IGP behavior

No.  A marginal link is simply one that has a measurable amount of packet
loss.

On a properly functioning wired network, you don't have any marginal
links: a link is either up or down, and a link that is up has negligible
amount of packet loss (the link, not the switches).  A marginal link is
one that's neither up or down -- it's somewhere in between.

This is made somewhat more complicated by layer 2 ARQ (for example, in
802.11b a link that is marginal at the physical layer will usually appear
as merely slow for unicast traffic, but clearly marginal for multicast;
weirder things are possible in 802.11a/g/n).

> Is this close to what a ³marginal link² is?

No.  Being marginal is a property of a link, it has nothing to do with the
IGP.

-- Juliusz


From nobody Thu Feb 19 10:01:25 2015
Return-Path: <mellon@fugue.com>
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 6BFE21A6FF7 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 10:01:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 qAN0t6MwaY5h for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 10:01:21 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 43A931A1EEF for <homenet@ietf.org>; Thu, 19 Feb 2015 10:01:21 -0800 (PST)
Received: from [10.0.20.107] (c-71-233-43-215.hsd1.nh.comcast.net [71.233.43.215]) by toccata.fugue.com (Postfix) with ESMTPSA id 3865C238164C; Thu, 19 Feb 2015 13:01:19 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se>
Date: Thu, 19 Feb 2015 13:00:47 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se>
To: Mikael Abrahamsson <swmike@swm.pp.se>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/2xdYIN9i6JgbEPKEF8cEpBMbtgU>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 18:01:23 -0000

On Feb 19, 2015, at 12:05 PM, Mikael Abrahamsson <swmike@swm.pp.se> =
wrote:
> Yes. I don't see the problem with this.

It means that every single device on a wired network is on a different =
subnet.   Perhaps it doesn't cause any extreme harm, but it certainly =
makes managing and debugging the network harder, and it means that you =
can't have a layer two switch anymore.   So the question I would ask is =
not "is there a problem with this," because obviously there is, but =
rather "is there a benefit to doing it this way."   I am curious to know =
what you think the benefit is.


From nobody Thu Feb 19 10:02:32 2015
Return-Path: <mellon@fugue.com>
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 F28B61A1EEF for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 10:02:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 ikp9hqQoaHsH for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 10:02:29 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id BADFC1A1B7D for <homenet@ietf.org>; Thu, 19 Feb 2015 10:02:29 -0800 (PST)
Received: from [10.0.20.107] (c-71-233-43-215.hsd1.nh.comcast.net [71.233.43.215]) by toccata.fugue.com (Postfix) with ESMTPSA id D01C0238164C; Thu, 19 Feb 2015 13:02:28 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <alpine.DEB.2.02.1502191806381.4007@uplift.swm.pp.se>
Date: Thu, 19 Feb 2015 13:01:56 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <519D3D33-61FF-4DAB-8BCC-90946D2093DC@fugue.com>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <54E58238.9030809@mtcc.com> <874mqigcct.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191622510.4007@uplift.swm.pp.se> <87vbixg9fe.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191806381.4007@uplift.swm.pp.se>
To: Mikael Abrahamsson <swmike@swm.pp.se>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/hX_Xzm6CfKhEU4Ywgow3emhz84w>
Cc: homenet@ietf.org, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 18:02:31 -0000

On Feb 19, 2015, at 12:09 PM, Mikael Abrahamsson <swmike@swm.pp.se> =
wrote:
> I don't know if this is true or not. I know ISIS was running on Cisco =
2500 routers (which are motorola 68030 at 20MHz. I've had these kinds of =
devices involved in the "single level" ISIS domain for a fairly large =
network (I believe it contained 400 routers, 1300 ISIS "nodes" if I =
remember correctly).

I think we can stipulate that in principle all of the routing protocols =
under consideration can be made to be run in a homenet mode on small =
hardware.   I don't think that's even an interesting basis for =
discriminating between them.


From nobody Thu Feb 19 10:09:00 2015
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 45D501A7029 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 10:08:59 -0800 (PST)
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 Aa8_-CJiLjYC for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 10:08:55 -0800 (PST)
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 AAFAA1A797C for <homenet@ietf.org>; Thu, 19 Feb 2015 10:08:52 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 55E4DA5; Thu, 19 Feb 2015 19:08:50 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1424369330; bh=tuHTntuF7HnNHOJBUl6/7p9i998QFDH0SXY5yhrz7MM=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=nPjNC7nkPW6ri6SJQ1DoPEa0jCRqSLVzKrrjuwG7y7cV8CBtS0qW8nTllGGFIMhhA UZWtoxemMIQntLKh59S/8wJ4sAla9B2vocbZ83pnzpOHtYU48XmiXfir61059wl5Ik chu2UK/lGwKYRr86VGhT2v/iDlU4nALULRl9dBPA=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 4E8BAA4; Thu, 19 Feb 2015 19:08:50 +0100 (CET)
Date: Thu, 19 Feb 2015 19:08:50 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Ted Lemon <mellon@fugue.com>
In-Reply-To: <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com>
Message-ID: <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com>
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/NYv7yuk7R3akkoi_Q4ZvfYT1fIE>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 18:08:59 -0000

On Thu, 19 Feb 2015, Ted Lemon wrote:

> It means that every single device on a wired network is on a different 
> subnet.  Perhaps it doesn't cause any extreme harm, but it certainly 
> makes managing and debugging the network harder, and it means that you 
> can't have a layer two switch anymore.  So the question I would ask is 
> not "is there a problem with this," because obviously there is, but 
> rather "is there a benefit to doing it this way."  I am curious to know 
> what you think the benefit is.

I am not mandating that each and every device is in its own broadcast 
domain, I am however advocating that we leave the model that has been 
prevalent for 10-15 years at least, ie that a home gateway has a "WAN" 
port and 4 "LAN" ports, and these 4 ports are bridged. I'm saying the 
typical device should have 4-5 "L3" ports. You're then free to connect one 
of these to your L2 switch if you so please.

I would like my router-to-router links to not have a lot of hosts in them 
if I can avoid it.

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


From nobody Thu Feb 19 10:12:20 2015
Return-Path: <mellon@fugue.com>
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 D5AD81A1ADC for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 10:12:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 jOlxbm87nP-I for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 10:12:17 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 70D1F1A0019 for <homenet@ietf.org>; Thu, 19 Feb 2015 10:12:17 -0800 (PST)
Received: from [10.0.20.107] (c-71-233-43-215.hsd1.nh.comcast.net [71.233.43.215]) by toccata.fugue.com (Postfix) with ESMTPSA id 57A4A238164C; Thu, 19 Feb 2015 13:12:16 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <alpine.DEB.2.02.1502191826230.4007@uplift.swm.pp.se>
Date: Thu, 19 Feb 2015 13:11:43 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <2FE73365-ECD7-49C3-8476-934CD1032542@fugue.com>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <54E58238.9030809@mtcc.com> <874mqigcct.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191622510.4007@uplift.swm.pp.se> <87vbixg9fe.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191806381.4007@uplift.swm.pp.se> <87lhjtg6jc.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191826230.4007@uplift.swm.pp.se>
To: Mikael Abrahamsson <swmike@swm.pp.se>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/Q8eZGC32MXKtmifkU9yJ37OAV5w>
Cc: homenet@ietf.org, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 18:12:19 -0000

On Feb 19, 2015, at 12:33 PM, Mikael Abrahamsson <swmike@swm.pp.se> =
wrote:
> Sure, ISIS could be made smarter when it comes to this, but it all =
comes down to what the requirements are. Right now when we started to =
evaluate routing protocols, people started pitching USP for their =
perticular favorite, and we found out we weren't even on the same page =
when it comes to requirements, and even what a homenet looks like.

I think it is you who are not on the same page, not the working group.   =
The working group recently published a document describing our goals, =
RFC 7368.   Many of the points you have raised as supposed points of =
disagreement are addressed in the document, although I will admit that =
it is not always obvious that they have been addressed.   The case of =
routing over Wifi was discussed at length; the text referring to it in =
the document is here:

   Due to the use of a variety of diverse underlying link technologies,
   path selection in a homenet may benefit from being more refined than
   minimising hop count.

Regarding your criticism about people pitching their favorite routing =
protocols, you seem to be doing precisely that, so the criticism seems a =
bit unfair.   The responses you have been hearing seem like legitimate =
attempts to address points you have raised on a technical level, not =
mere advocacy, and it is unfortunate that you would suggest otherwise: I =
haven't actually seen you raise any technical points in favor of IS-IS, =
which you seem to be advocating.


From nobody Thu Feb 19 10:14:06 2015
Return-Path: <mellon@fugue.com>
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 ED3FD1A0019 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 10:14:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 d702MeU-DcQD for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 10:14:03 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id CC9BE1A001C for <homenet@ietf.org>; Thu, 19 Feb 2015 10:14:03 -0800 (PST)
Received: from [10.0.20.107] (c-71-233-43-215.hsd1.nh.comcast.net [71.233.43.215]) by toccata.fugue.com (Postfix) with ESMTPSA id 0D049238164C; Thu, 19 Feb 2015 13:14:02 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se>
Date: Thu, 19 Feb 2015 13:13:30 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <8B98F698-983D-4D2A-B5D1-7ACED27C275E@fugue.com>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se>
To: Mikael Abrahamsson <swmike@swm.pp.se>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/tXH3TVA4_ec_ALw8Wt6ZUxIJ0VA>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 18:14:05 -0000

On Feb 19, 2015, at 1:08 PM, Mikael Abrahamsson <swmike@swm.pp.se> =
wrote:
> I would like my router-to-router links to not have a lot of hosts in =
them if I can avoid it.

Why is that?


From nobody Thu Feb 19 10:18:33 2015
Return-Path: <otroan@employees.org>
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 A924D1A046D for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 10:18:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.011
X-Spam-Level: 
X-Spam-Status: No, score=-2.011 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 5of56k3_EThZ for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 10:18:30 -0800 (PST)
Received: from banjo.employees.org (banjo.employees.org [198.137.202.19]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2F4D31A0019 for <homenet@ietf.org>; Thu, 19 Feb 2015 10:18:30 -0800 (PST)
Received: from banjo.employees.org (localhost [127.0.0.1]) by banjo.employees.org (Postfix) with ESMTP id CFF57627A; Thu, 19 Feb 2015 10:18:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; s=selector1; bh=5l8OTTEjTvRaj1vKT6Y/IV6d8Ds=; b= DCxY2H4gZsCMx6VYPx0tE07CXCewwzO4Tfi/FFIS8EaNoSX1oGsoBCpwFIY7AsPE PaqDWLu8AC8lAg7zb7+oF224dDyUmyFvNpGw6A9oHUW/V4LisAS6bQf+gnk87qUA 8j4GyHmTSGWkNOKUOYchPiYBWYaPNG1PbJsxL6bsz+A=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; q=dns; s=selector1; b=l4N5vh4Xl6pIsJEy+eAKTh9/cd K8kmQIK0jnfc1OSnhwYfJmErkB7qBg0u7BHNJs05eZD7cgKSWFFJ/I5JNYga/uQw BTXUiuYDgW3PpsuQTWZ0eM7WXvLl5wkyxKJryX6ujlV74RaUNRgpKBAm2FgM13wO qpbLTAPJ/q2NtGpgE=
Received: from gomlefisk.localdomain (unknown [195.159.234.46]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id 8B17161E9; Thu, 19 Feb 2015 10:18:28 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by gomlefisk.localdomain (Postfix) with ESMTP id 42B583F05EA2; Thu, 19 Feb 2015 19:18:21 +0100 (CET)
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_175A6717-6AB6-49CA-B4E7-04867B290EB2"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.5b5
From: Ole Troan <otroan@employees.org>
In-Reply-To: <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se>
Date: Thu, 19 Feb 2015 19:18:20 +0100
Message-Id: <F2818678-A728-4300-896C-E220A0DF0D1A@employees.org>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se>
To: Mikael Abrahamsson <swmike@swm.pp.se>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/fO8bppLsMWvPPYm38tvsQTPoMlA>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Ted Lemon <mellon@fugue.com>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 18:18:31 -0000

--Apple-Mail=_175A6717-6AB6-49CA-B4E7-04867B290EB2
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

>> It means that every single device on a wired network is on a =
different subnet.  Perhaps it doesn't cause any extreme harm, but it =
certainly makes managing and debugging the network harder, and it means =
that you can't have a layer two switch anymore.  So the question I would =
ask is not "is there a problem with this," because obviously there is, =
but rather "is there a benefit to doing it this way."  I am curious to =
know what you think the benefit is.
>=20
> I am not mandating that each and every device is in its own broadcast =
domain, I am however advocating that we leave the model that has been =
prevalent for 10-15 years at least, ie that a home gateway has a "WAN" =
port and 4 "LAN" ports, and these 4 ports are bridged. I'm saying the =
typical device should have 4-5 "L3" ports. You're then free to connect =
one of these to your L2 switch if you so please.
>=20
> I would like my router-to-router links to not have a lot of hosts in =
them if I can avoid it.

+1.

there are very few shared media around anymore. I don't think I've ever =
been connected to a 10base5.
why should the IP subnet model emulate a shared medium, when the =
physical topology is a star.

wireless with security is also a star topology, with a unidirectional =
broadcast channel.

cheers,
Ole

--Apple-Mail=_175A6717-6AB6-49CA-B4E7-04867B290EB2
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJU5ijtAAoJEFuJXizso86gvyMH/18VUmziEz09zQXmM/Mb4X7I
UGzzXtPBdp6DT7Ox8A3Qi6Hm3OTTATZaLKJxiBbjyDMgV6NJnfHu4I+jMCnn5a8/
pc1MtfvLdreX4IjK5fsuJpCngcZwGRg0JsfESXMqXGxEjLREbTJKPUJWivMfP/IC
+8H9R1DgkaeCOeptuDqZ39+dP/gStCbzgcrBzce8qaRKXYX0GjPNfhVuc1kyHkCd
X46EXbQ64XhyEcZ+4JqLKZjQ0c0tES7EuvrEYObbwe9HTUk+oZ36EDx6k3kv709S
2YxCnyRIIzM1IoZLhOWrLyn5m3Bp1FNHWkQFbwzrX4HmF1CC/qmH10gCZKYYJCY=
=JGLQ
-----END PGP SIGNATURE-----

--Apple-Mail=_175A6717-6AB6-49CA-B4E7-04867B290EB2--


From nobody Thu Feb 19 10:22:56 2015
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 5DD631A0158 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 10:22:55 -0800 (PST)
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 GBTCUErq8LSb for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 10:22:53 -0800 (PST)
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 282611A8729 for <homenet@ietf.org>; Thu, 19 Feb 2015 10:22:36 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id B13B2A5; Thu, 19 Feb 2015 19:22:34 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1424370154; bh=aQh2ACnyyTY4vJ3nLxr8m9aFMAGRJa/fq7Csfv66UmM=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=12OoUZlNGtyX3LbGlhAVYMkyuaczzCYD1vLY1lGiiwQIriwG4YrMkGjDbpEZJBAPc yEEYXAFz5GYYKPSPfWJYlsT9VbUOlx9rEWx39tG//gA1IfECW5bDZio6xPN5YZpSQr zBU+c9HrKe7HyJkFw6/EVQqhuiZRV5G2P4ebiVf8=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id AA2B8A4; Thu, 19 Feb 2015 19:22:34 +0100 (CET)
Date: Thu, 19 Feb 2015 19:22:34 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Ted Lemon <mellon@fugue.com>
In-Reply-To: <8B98F698-983D-4D2A-B5D1-7ACED27C275E@fugue.com>
Message-ID: <alpine.DEB.2.02.1502191920560.4007@uplift.swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <8B98F698-983D-4D2A-B5D1-7ACED27C275E@fugue.com>
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/b5rDN2Ed8aFU0MRj6Qpr6boml0s>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 18:22:55 -0000

On Thu, 19 Feb 2015, Ted Lemon wrote:

> On Feb 19, 2015, at 1:08 PM, Mikael Abrahamsson <swmike@swm.pp.se> wrote:
>> I would like my router-to-router links to not have a lot of hosts in them if I can avoid it.
>
> Why is that?

If we're going to be routing multicast within the home, we're most likely 
going to have to use some kind of variant of PIM. Asking the L2 switches 
people connect to the router to support both PIM and MLD snooping seem 
like it might be asking too much.

I might be wrong though.

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


From nobody Thu Feb 19 10:23:57 2015
Return-Path: <John_Leddy@cable.comcast.com>
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 D8F0A1A1B7D for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 10:23:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.225
X-Spam-Level: 
X-Spam-Status: No, score=0.225 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 yO5NjyABtevZ for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 10:23:54 -0800 (PST)
Received: from pacdcmhout01.cable.comcast.com (PACDCMHOUT01.cable.comcast.com [68.87.31.167]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 36D491A0158 for <homenet@ietf.org>; Thu, 19 Feb 2015 10:23:54 -0800 (PST)
X-AuditID: 44571fa7-f79b96d000002184-6d-54e62a385e3a
Received: from PACDCEXHUB02.cable.comcast.com (pacdcexhub02.cable.comcast.com [24.40.56.115]) by pacdcmhout01.cable.comcast.com (SMTP Gateway) with SMTP id 87.D7.08580.83A26E45; Thu, 19 Feb 2015 13:23:52 -0500 (EST)
Received: from PACDCEXMB22.cable.comcast.com ([fe80::f887:1b71:477f:d14b]) by PACDCEXHUB02.cable.comcast.com ([fe80::2816:661:c294:c863%16]) with mapi id 14.03.0181.006; Thu, 19 Feb 2015 13:23:51 -0500
From: "Leddy, John" <John_Leddy@cable.comcast.com>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Thread-Topic: [homenet] Routing protocol comparison document
Thread-Index: AQHQTGYbpljA4qO18ECjoj8KcSEQaZz4PdmAgABXbgD//7RTgA==
Date: Thu, 19 Feb 2015 18:23:51 +0000
Message-ID: <D10B90D0.6C00%John_Leddy@cable.comcast.com>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <A5767F83-3D0C-40E5-A73B-912E3C160A42@fugue.com> <alpine.DEB.2.02.1502191235240.4007@uplift.swm.pp.se> <87zj89gaqm.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191804050.4007@uplift.swm.pp.se> <D10B8924.6BD5%John_Leddy@cable.comcast.com> <87h9uhg529.wl-jch@pps.univ-paris-diderot.fr>
In-Reply-To: <87h9uhg529.wl-jch@pps.univ-paris-diderot.fr>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.4.7.141117
x-originating-ip: [24.40.1.145]
Content-Type: text/plain; charset="euc-kr"
Content-ID: <C74652F912CDB74CA262034EB61962A9@cable.comcast.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrAIsWRmVeSWpSXmKPExsUioWFRrGuh9SzE4M8VA4v3iw6xWHz+9I/V 4uXSrWwOzB5Llvxk8ri4+x2jx99JD5kCmKO4bFJSczLLUov07RK4Mg59ns5esEmw4tz068wN jD8Euhg5OSQETCR+fjjFBGGLSVy4t56ti5GLQ0jgJqPEqRvXmCGcs4wSf5bPZASpYhMwkri5 aguYLSJgJjGv5zmYzSwQITHjx3WgBg4OYQFriSUtHhAlNhL7V7WyQ9hOEqt6JoItYxFQlVjY 2QDWyitgIbF933J2iF3/WCWed05gBUlwClhJtJ36xAZiMwJd9/3UGiaIXeISt57Mh7paQGLJ nvPMELaoxMvH/8B6RQX0JFZeb2KDiMtLtKzawQzRqyXx5cc+NgjbQWLr/ilQ9ytKTOl+yA5x kKDEyZlPWCYwSsxCsm4WkvZZSNpnIWmfhaR9ASPrKka5gsTklOTcjPzSEgNDveTEpJxUveT8 3OTE4hIQvYkRGK8u4fLLdzDee+F0iFGAg1GJh/eD+rMQIdbEsuLK3EOMEhzMSiK8+zmBQrwp iZVVqUX58UWlOanFhxilOViUxHmvmuwIERJITyxJzU5NLUgtgskycXBKNTBGVXZu3B47/dnW 8/MYtsmZ7jve1nr/WJW/Sdi/mp+OXN0FHXknODe/WO7S2XX+JhN/aPu9bVesSk7Fvn9yJuhb 6eumn8KxZ75rlz6V63N/5Wrxv8kjmOWF70xOx5OZ74sEN26VPLr1gtzfVTMbC2yfGltvWXlO iNvo0KtWe8bJHMeKQm337j6lxFKckWioxVxUnAgAmFNAVdMCAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/YBvuzDnT1y68ioxF-gqb7tiEo_g>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 18:23:56 -0000

V2FzbqGvdCB0aGlua2luZyBRdWFudHVtIE5ldHdvcmtpbmcgd291bGQgcG9wIHVwIHRoaXMgd2F5
oaYNCg0KVGhlIKGwbWFyZ2luYWwgbGlua6GxIGNhbqGvdCBzaW1wbHkgYmUgbWVhc3VyYWJsZSBw
YWNrZXQgbG9zcy4NClRoZXJlIGFyZSBMMiBuZXR3b3Jrcywgd2lyZWQvd2lyZWxlc3MgdGhhdCBj
YW4gaGF2ZSBtZWFzdXJhYmxlIHBhY2tldCBsb3NzDQqhsGFzIHByb3Blcmx5IGRlc2lnbmVkobEu
DQpOb3QgZ29vZCwgYW5kIHlvdSBjb3VsZCBhdm9pZCBpdCwgYnV0IGl0IGlzIGV4cGVjdGVkIGJl
aGF2aW9yLg0KUmVhc29uYWJsZSBzaXplZCAxMEJhc2U1IG5ldHdvcmtzIHdlcmUgZnVuLg0KDQpI
b3BlZnVsbHkgdGhlIHdob2xlIEhvbWVuZXQgZWZmb3J0IGlzIHRvIGtlZXAgdGhlIEhvbWU7IHdp
dGggbXVsdGlwbGUgTUFDDQp0eXBlcywgc3BlZWRzLCB3aXJlZCBhbmQgd2lyZWxlc3MgbGlua3Mg
aW4gYSBsYXJnZSBMMiBicmlkZ2UgZG9tYWluIGZyb20NCmJlaW5nIGEgobBtYXJnaW5hbCBsaW5r
obEuDQoNCk9uIDIvMTkvMTUsIDEyOjU0IFBNLCAiSnVsaXVzeiBDaHJvYm9jemVrIiA8amNoQHBw
cy51bml2LXBhcmlzLWRpZGVyb3QuZnI+DQp3cm90ZToNCg0KPj4gU2VlbXMgbGlrZSCp+G1hcmdp
bmFsIGxpbmup9yBpcyBhc3NvY2lhdGVkIHdpdGggdGhlIElHUCBiZWhhdmlvcg0KPg0KPk5vLiAg
QSBtYXJnaW5hbCBsaW5rIGlzIHNpbXBseSBvbmUgdGhhdCBoYXMgYSBtZWFzdXJhYmxlIGFtb3Vu
dCBvZiBwYWNrZXQNCj5sb3NzLg0KPg0KPk9uIGEgcHJvcGVybHkgZnVuY3Rpb25pbmcgd2lyZWQg
bmV0d29yaywgeW91IGRvbid0IGhhdmUgYW55IG1hcmdpbmFsDQo+bGlua3M6IGEgbGluayBpcyBl
aXRoZXIgdXAgb3IgZG93biwgYW5kIGEgbGluayB0aGF0IGlzIHVwIGhhcyBuZWdsaWdpYmxlDQo+
YW1vdW50IG9mIHBhY2tldCBsb3NzICh0aGUgbGluaywgbm90IHRoZSBzd2l0Y2hlcykuICBBIG1h
cmdpbmFsIGxpbmsgaXMNCj5vbmUgdGhhdCdzIG5laXRoZXIgdXAgb3IgZG93biAtLSBpdCdzIHNv
bWV3aGVyZSBpbiBiZXR3ZWVuLg0KPg0KPlRoaXMgaXMgbWFkZSBzb21ld2hhdCBtb3JlIGNvbXBs
aWNhdGVkIGJ5IGxheWVyIDIgQVJRIChmb3IgZXhhbXBsZSwgaW4NCj44MDIuMTFiIGEgbGluayB0
aGF0IGlzIG1hcmdpbmFsIGF0IHRoZSBwaHlzaWNhbCBsYXllciB3aWxsIHVzdWFsbHkgYXBwZWFy
DQo+YXMgbWVyZWx5IHNsb3cgZm9yIHVuaWNhc3QgdHJhZmZpYywgYnV0IGNsZWFybHkgbWFyZ2lu
YWwgZm9yIG11bHRpY2FzdDsNCj53ZWlyZGVyIHRoaW5ncyBhcmUgcG9zc2libGUgaW4gODAyLjEx
YS9nL24pLg0KPg0KPj4gSXMgdGhpcyBjbG9zZSB0byB3aGF0IGEgqfhtYXJnaW5hbCBsaW5rqfcg
aXM/DQo+DQo+Tm8uICBCZWluZyBtYXJnaW5hbCBpcyBhIHByb3BlcnR5IG9mIGEgbGluaywgaXQg
aGFzIG5vdGhpbmcgdG8gZG8gd2l0aCB0aGUNCj5JR1AuDQo+DQo+LS0gSnVsaXVzeg0KPg0KPl9f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+aG9tZW5ldCBt
YWlsaW5nIGxpc3QNCj5ob21lbmV0QGlldGYub3JnDQo+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFp
bG1hbi9saXN0aW5mby9ob21lbmV0DQo+DQoNCg==


From nobody Thu Feb 19 10:30:02 2015
Return-Path: <rdroms.ietf@gmail.com>
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 D676C1A1B3A for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 10:30:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 JQJPSD6dkNOJ for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 10:29:58 -0800 (PST)
Received: from mail-qa0-x22b.google.com (mail-qa0-x22b.google.com [IPv6:2607:f8b0:400d:c00::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EE54C1A0158 for <homenet@ietf.org>; Thu, 19 Feb 2015 10:29:57 -0800 (PST)
Received: by mail-qa0-f43.google.com with SMTP id bm13so7453727qab.2 for <homenet@ietf.org>; Thu, 19 Feb 2015 10:29:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=UejPl1QlLOCH0RCOptfcijcMy6r4YYN4FZETTEW6vf8=; b=m05hNbLnNrQwaA+QRBv0J2o4s5G5muOO6Or7quJZiJV+cS41kgfkO7ZObwuST1WlVm SiZOdKU5UxJpWVbgERzU/mMMRLhFzf8V+R6IZ2vGtFHjVCSEPacssEUbin4qxhq9/gL5 SJaF+QxhL7RImD5B8SGXXNfasWaa3qQuHFxAPqlO+VP2EsvcyjQVydzIMEIVNkF5h3Kb bhN6deKXw100mHohrDejlRnLVgrjhIK9M8KUMUH5v/65PuHO8Nuh5nV1PdVlVYzRq3xS Btth8uSx9Iuo0esF8KW/e7nG269RCZlrBosIfhdQ1VD95A1hDb6l+blJUBqsnv+jVqB5 VczA==
X-Received: by 10.229.65.8 with SMTP id g8mr10587663qci.15.1424370597167; Thu, 19 Feb 2015 10:29:57 -0800 (PST)
Received: from rtp-vpn1-1597.cisco.com (rtp-isp-nat1.cisco.com. [64.102.254.33]) by mx.google.com with ESMTPSA id m49sm20188105qgd.44.2015.02.19.10.29.55 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 19 Feb 2015 10:29:56 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <F2818678-A728-4300-896C-E220A0DF0D1A@employees.org>
Date: Thu, 19 Feb 2015 13:29:54 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <ADBDED5C-5279-4A04-B7C8-FCCB453A8C4F@gmail.com>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <F2818678-A728-4300-896C-E220A0DF0D1A@employees.org>
To: Ole Troan <otroan@employees.org>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/g9MgCy-AQOS6Z-BFM9yJ1Ytd9Q8>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Ted Lemon <mellon@fugue.com>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 18:30:01 -0000

> On Feb 19, 2015, at 1:18 PM 2/19/15, Ole Troan <otroan@employees.org> =
wrote:
>=20
>>> It means that every single device on a wired network is on a =
different subnet.  Perhaps it doesn't cause any extreme harm, but it =
certainly makes managing and debugging the network harder, and it means =
that you can't have a layer two switch anymore.  So the question I would =
ask is not "is there a problem with this," because obviously there is, =
but rather "is there a benefit to doing it this way."  I am curious to =
know what you think the benefit is.
>>=20
>> I am not mandating that each and every device is in its own broadcast =
domain, I am however advocating that we leave the model that has been =
prevalent for 10-15 years at least, ie that a home gateway has a "WAN" =
port and 4 "LAN" ports, and these 4 ports are bridged. I'm saying the =
typical device should have 4-5 "L3" ports. You're then free to connect =
one of these to your L2 switch if you so please.
>>=20
>> I would like my router-to-router links to not have a lot of hosts in =
them if I can avoid it.
>=20
> +1.
>=20
> there are very few shared media around anymore. I don't think I've =
ever been connected to a 10base5.
> why should the IP subnet model emulate a shared medium, when the =
physical topology is a star.
>=20
> wireless with security is also a star topology, with a unidirectional =
broadcast channel.

If I can extrapolate and oversimplify a bit, now we've gotten to a =
fundamental problem: how does a random collection of devices, links and =
ports sort itself by DWIM into a coherent home network?  How does a =
device with 16 ports decide to group ports (0-5, 7, 10), (6, 8, 12-15) =
and (9, 11) into separate subnets?

- Ralph

>=20
> cheers,
> Ole
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet


From nobody Thu Feb 19 10:32:17 2015
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 C7F4A1A0158 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 10:32:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.661
X-Spam-Level: 
X-Spam-Status: No, score=-1.661 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 bmdvs_vfHGeK for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 10:32:14 -0800 (PST)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 57B321A1B84 for <homenet@ietf.org>; Thu, 19 Feb 2015 10:32:10 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id B5BD3A6; Thu, 19 Feb 2015 19:32:08 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1424370728; bh=prT5S7kEfbuGudQQ1aqEDG2hcbo2Xu7/53gedyUtwDw=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=ORsLfO8Sxseh9Ug89tkCeBl22Kjv55BtitJATJU6hMZ9UkEK/K05wzXOAkJ36g58E oHMLRezjnz8mIOjwCevQZIoPFLKaXHZooBTKu92I2Ptd3phNsduvPLndKx/6+U/dhY actXUw5SZ1OxAqFmIF4yip+tgq0yG4RXWH5d0ivQ=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id B1411A5; Thu, 19 Feb 2015 19:32:08 +0100 (CET)
Date: Thu, 19 Feb 2015 19:32:08 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Ted Lemon <mellon@fugue.com>
In-Reply-To: <2FE73365-ECD7-49C3-8476-934CD1032542@fugue.com>
Message-ID: <alpine.DEB.2.02.1502191924250.4007@uplift.swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <54E58238.9030809@mtcc.com> <874mqigcct.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191622510.4007@uplift.swm.pp.se> <87vbixg9fe.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191806381.4007@uplift.swm.pp.se> <87lhjtg6jc.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191826230.4007@uplift.swm.pp.se> <2FE73365-ECD7-49C3-8476-934CD1032542@fugue.com>
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/GuqnJbeHOPEY3xCeZ0eZ6_QtNtM>
Cc: homenet@ietf.org
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 18:32:15 -0000

On Thu, 19 Feb 2015, Ted Lemon wrote:

> Regarding your criticism about people pitching their favorite routing 
> protocols, you seem to be doing precisely that, so the criticism seems a

I never said I wasn't. People usually have favorites, I am not excluded.

> bit unfair.  The responses you have been hearing seem like legitimate 
> attempts to address points you have raised on a technical level, not 
> mere advocacy, and it is unfortunate that you would suggest otherwise: I 
> haven't actually seen you raise any technical points in favor of IS-IS, 
> which you seem to be advocating.

It wasn't my intention to imply that people didn't have technical reasons 
to suggest what they do. I have reasons to suggest what I do. They have 
theirs.

If people want to choose babel because it works well facing adverse radio 
conditions in a mesh-networking environment (that I know nothing about), I 
however have to question if this is relevant to the discussion we're 
having here. Is that really a requirement for a homenet routing protocol?

If 802.11 is so bad for multicast, do we even want to run IPv6 over it?

I know Dave T is trying to enlighten IEEE about these issues, which is 
great. Do we presume he (and others) succeed in getting 802.11 fixed, or 
do we choose routing protocol based on current 802.11 behavior?

Or do we say we want to avoid multicast altogether in homenet, and include 
an architecture where the ingress homenet router converts multicast TV 
streams to unicast within the home? That would solve some issues...

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


From nobody Thu Feb 19 10:43:05 2015
Return-Path: <mellon@fugue.com>
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 863D41A079D for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 10:43:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 qrM_RIZnF-Uq for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 10:43:03 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 42E8B1A0158 for <homenet@ietf.org>; Thu, 19 Feb 2015 10:43:03 -0800 (PST)
Received: from [10.0.20.107] (c-71-233-43-215.hsd1.nh.comcast.net [71.233.43.215]) by toccata.fugue.com (Postfix) with ESMTPSA id 1DFEE238164C; Thu, 19 Feb 2015 13:43:01 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <alpine.DEB.2.02.1502191920560.4007@uplift.swm.pp.se>
Date: Thu, 19 Feb 2015 13:42:29 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <00896657-5C43-45B4-9307-66391812752C@fugue.com>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <8B98F698-983D-4D2A-B5D1-7ACED27C275E@fugue.com> <alpine.DEB.2.02.1502191920560.4007@uplift.swm.pp.se>
To: Mikael Abrahamsson <swmike@swm.pp.se>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/52bUKLk7uBTEtPIcD8roeJXny6U>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 18:43:04 -0000

On Feb 19, 2015, at 1:22 PM, Mikael Abrahamsson <swmike@swm.pp.se> =
wrote:
> If we're going to be routing multicast within the home, we're most =
likely going to have to use some kind of variant of PIM. Asking the L2 =
switches people connect to the router to support both PIM and MLD =
snooping seem like it might be asking too much.

Hm, maybe so.   Thanks for the more detailed answer.


From nobody Thu Feb 19 10:46:27 2015
Return-Path: <mellon@fugue.com>
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 4289A1A1B3A for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 10:46:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 cdiuRUTmZGoB for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 10:46:25 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 060BB1A0158 for <homenet@ietf.org>; Thu, 19 Feb 2015 10:46:25 -0800 (PST)
Received: from [10.0.20.107] (c-71-233-43-215.hsd1.nh.comcast.net [71.233.43.215]) by toccata.fugue.com (Postfix) with ESMTPSA id B015A238164C; Thu, 19 Feb 2015 13:46:23 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <ADBDED5C-5279-4A04-B7C8-FCCB453A8C4F@gmail.com>
Date: Thu, 19 Feb 2015 13:45:50 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <B2BEAF63-D219-41A0-8209-1EEFE9667440@fugue.com>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <F2818678-A728-4300-896C-E220A0DF0D1A@employees.org> <ADBDED5C-5279-4A04-B7C8-FCCB453A8C4F@gmail.com>
To: Ralph Droms <rdroms.ietf@gmail.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/gL9jQ32JHKxBmeDFld7B0oD9JqE>
Cc: Ole Troan <otroan@employees.org>, "homenet@ietf.org Group" <homenet@ietf.org>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 18:46:26 -0000

On Feb 19, 2015, at 1:29 PM, Ralph Droms <rdroms.ietf@gmail.com> wrote:
> If I can extrapolate and oversimplify a bit, now we've gotten to a =
fundamental problem: how does a random collection of devices, links and =
ports sort itself by DWIM into a coherent home network?  How does a =
device with 16 ports decide to group ports (0-5, 7, 10), (6, 8, 12-15) =
and (9, 11) into separate subnets?

What Mikael is saying is that on homenet devices (not switches) each =
port is treated as a separate network, on the assumption that all of the =
physical ports on the homenet device are likely to connect to routers, =
and that any switched topology would be done using switches connected to =
homenet routers.

I am not convinced by this; one of the issues I see here is that until =
DNSSD comes up with a solution, we are breaking service discovery on the =
home network by doing this.   Granted, we already do that from Wifi to =
wired, but this seems gratuitous.


From nobody Thu Feb 19 10:50:01 2015
Return-Path: <mellon@fugue.com>
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 5424D1A005A for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 10:50:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 r5SSd-U1tn6v for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 10:49:59 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 214001A001C for <homenet@ietf.org>; Thu, 19 Feb 2015 10:49:59 -0800 (PST)
Received: from [10.0.20.107] (c-71-233-43-215.hsd1.nh.comcast.net [71.233.43.215]) by toccata.fugue.com (Postfix) with ESMTPSA id 6D345238164C; Thu, 19 Feb 2015 13:49:58 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <alpine.DEB.2.02.1502191924250.4007@uplift.swm.pp.se>
Date: Thu, 19 Feb 2015 13:49:25 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <DE5D415F-4804-44C2-9621-523C3EFBC859@fugue.com>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <54E58238.9030809@mtcc.com> <874mqigcct.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191622510.4007@uplift.swm.pp.se> <87vbixg9fe.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191806381.4007@uplift.swm.pp.se> <87lhjtg6jc.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191826230.4007@uplift.swm.pp.se> <2FE73365-ECD7-49C3-8476-934CD1032542@fugue.com> <alpine.DEB.2.02.1502191924250.4007@uplift.swm.pp.se>
To: Mikael Abrahamsson <swmike@swm.pp.se>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/TYUeRfTh7CFPtdaAlg3l3CXvPnk>
Cc: homenet@ietf.org
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 18:50:00 -0000

On Feb 19, 2015, at 1:32 PM, Mikael Abrahamsson <swmike@swm.pp.se> =
wrote:
> If 802.11 is so bad for multicast, do we even want to run IPv6 over =
it?

This would be a great objection to using 802.11 for host networks, but =
it's a lousy argument against using 802.11 for transit networks!

> I know Dave T is trying to enlighten IEEE about these issues, which is =
great. Do we presume he (and others) succeed in getting 802.11 fixed, or =
do we choose routing protocol based on current 802.11 behavior?

We have no choice.

> Or do we say we want to avoid multicast altogether in homenet, and =
include an architecture where the ingress homenet router converts =
multicast TV streams to unicast within the home? That would solve some =
issues...

I don't know.   Homenet multicast is an open issue.   But I don't think =
this use case represents a serious problem, because as far as I can tell =
streaming video is not done using multicast in practice anyway.


From nobody Thu Feb 19 10:55:18 2015
Return-Path: <cyrus@openwrt.org>
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 46A1B1A7033 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 10:55:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.25
X-Spam-Level: 
X-Spam-Status: No, score=-2.25 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-0.7] 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 2LTD_Xw2-r7A for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 10:55:15 -0800 (PST)
Received: from mail.core-networks.de (mail.core-networks.de [82.96.72.7]) by ietfa.amsl.com (Postfix) with ESMTP id 6A5411A0158 for <homenet@ietf.org>; Thu, 19 Feb 2015 10:55:15 -0800 (PST)
Received: from localhost ([127.0.0.1]) by mail.core-networks.de id 1YOWFh-0000xy-Vv with ESMTPSA (TLSv1.2:DHE-RSA-AES128-SHA:128) for ; Thu, 19 Feb 2015 19:55:10 +0100
Message-ID: <54E6318C.9030609@openwrt.org>
Date: Thu, 19 Feb 2015 19:55:08 +0100
From: Steven Barth <cyrus@openwrt.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.4.0
MIME-Version: 1.0
To: Ted Lemon <mellon@fugue.com>, Ralph Droms <rdroms.ietf@gmail.com>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <F2818678-A728-4300-896C-E220A0DF0D1A@employees.org> <ADBDED5C-5279-4A04-B7C8-FCCB453A8C4F@gmail.com> <B2BEAF63-D219-41A0-8209-1EEFE9667440@fugue.com>
In-Reply-To: <B2BEAF63-D219-41A0-8209-1EEFE9667440@fugue.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/yD-uWrq1T-kVd7ZeUhknjuCUMNw>
Cc: Ole Troan <otroan@employees.org>, "homenet@ietf.org Group" <homenet@ietf.org>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 18:55:17 -0000

>
> I am not convinced by this; one of the issues I see here is that until DNSSD comes up with a solution, we are breaking service discovery on the home network by doing this.   Granted, we already do that from Wifi to wired, but this seems gratuitous.
There is draft-ietf-dnssd-hybrid-00 for which we have specified glued to 
HNCP and a reference implementation. I think DNSSD is actually mostly 
covered or are you referring to any specific issue of that solution?

UPNP (SSDP) is a different beast though and would probably depend on 
having proper multicast routing.
This is from memory but I guess Markus could elaborate here.


From nobody Thu Feb 19 10:56:02 2015
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 0B2A91A7033 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 10:56:01 -0800 (PST)
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 aj0XhNiSD6rM for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 10:55:59 -0800 (PST)
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 973701A001C for <homenet@ietf.org>; Thu, 19 Feb 2015 10:55:59 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 2A550A5; Thu, 19 Feb 2015 19:55:58 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1424372158; bh=9uLBErQCGlDvLox57JGEGH/p2RJTaPLQMnA8U3ZtsZk=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=A8qhkhqI8I2c3EkMfc9FKi5gF/FrV+FT8dEO3X7bCTYNNfuT0pRC3/uI2cX6gwtYN fXDw2+0A3lGw4XQ0r8kS2b0bHBI7HJgzwPaN9wJ92xwJOITfRXO0k3zfzYq5SXK7qm g0JIZFPjOGOEQ+e4DhcJmPMWINnpB7o5NrayiVZI=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 25E49A4; Thu, 19 Feb 2015 19:55:58 +0100 (CET)
Date: Thu, 19 Feb 2015 19:55:58 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Ted Lemon <mellon@fugue.com>
In-Reply-To: <DE5D415F-4804-44C2-9621-523C3EFBC859@fugue.com>
Message-ID: <alpine.DEB.2.02.1502191951220.4007@uplift.swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <54E58238.9030809@mtcc.com> <874mqigcct.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191622510.4007@uplift.swm.pp.se> <87vbixg9fe.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191806381.4007@uplift.swm.pp.se> <87lhjtg6jc.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191826230.4007@uplift.swm.pp.se> <2FE73365-ECD7-49C3-8476-934CD1032542@fugue.com> <alpine.DEB.2.02.1502191924250.4007@uplift.swm.pp.se> <DE5D415F-4804-44C2-9621-523C3EFBC859@fugue.com>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/6_9s46DBh52u3kLOHZo7nGyZWMo>
Cc: homenet@ietf.org
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 18:56:01 -0000

On Thu, 19 Feb 2015, Ted Lemon wrote:

> This would be a great objection to using 802.11 for host networks, but 
> it's a lousy argument against using 802.11 for transit networks!

Please elaborate.

> I don't know.  Homenet multicast is an open issue.  But I don't think 
> this use case represents a serious problem, because as far as I can tell 
> streaming video is not done using multicast in practice anyway.

What do you mean by "streaming video"?

We have approximately 50 IPv6 multicast TV channels in the test network 
currently.

My employer has millions of subscribers using IPv4 multicast TV channels 
currently.

We are not sure this is the best way forward, perhaps we just stop doing 
multicast to the home network and just do multicast to the nearest PoP or 
alike.

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


From nobody Thu Feb 19 10:57:01 2015
Return-Path: <rdroms.ietf@gmail.com>
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 71C371A871B for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 10:56:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 pvc0pdsgnjIh for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 10:56:57 -0800 (PST)
Received: from mail-qa0-x22c.google.com (mail-qa0-x22c.google.com [IPv6:2607:f8b0:400d:c00::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A17E51A0037 for <homenet@ietf.org>; Thu, 19 Feb 2015 10:56:57 -0800 (PST)
Received: by mail-qa0-f44.google.com with SMTP id n8so7611776qaq.3 for <homenet@ietf.org>; Thu, 19 Feb 2015 10:56:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=NbBRQl/mbvrdIfNLrxPVGsamC5iMTQMZX/IVKqPo8oA=; b=FKzJFNsYo2KhGdvGFZ/52KkVoQ0cUZhWuevHTV61+O0ga34XT68j0sCFcLr+FvcuwQ ZXKZ1bP0Vhxo+gqrEJQZ9yLonTHc4gJxlYqIEHAlbnYQpHmCpqUuMh2McYIrXLCQL/ls gnVYmOKqt0kBTRXLXH5wfm2T5aansdhlhMlOmKI4PlR1Pk4e5c7PycgiRzv38f1PPRXM Lq42Oj+MfLsrzvthbTPpwEEFt2oYGGOfyCLGQ1yczQmXkb4fEmn+iaxXNMVfQWKNf/UY XwLDmLlC/+C4icXO5cspRLmZG0MNMuWl+8lxEIsGJRkBsQ6X5bexzJxnHo8jxmz9LKC0 mFlQ==
X-Received: by 10.140.148.20 with SMTP id 20mr14600596qhu.67.1424372216860; Thu, 19 Feb 2015 10:56:56 -0800 (PST)
Received: from rtp-vpn1-1597.cisco.com (rtp-isp-nat-pool1-2.cisco.com. [64.102.254.35]) by mx.google.com with ESMTPSA id j4sm9526970qgj.37.2015.02.19.10.56.55 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 19 Feb 2015 10:56:56 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <B2BEAF63-D219-41A0-8209-1EEFE9667440@fugue.com>
Date: Thu, 19 Feb 2015 13:56:54 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <812BE11C-CB57-4594-81CD-A54AC8A16EFF@gmail.com>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <F2818678-A728-4300-896C-E220A0DF0D1A@employees.org> <ADBDED5C-5279-4A04-B7C8-FCCB453A8C4F@gmail.com> <B2BEAF63-D219-41A0-8209-1EEFE9667440@fugue.com>
To: Ted Lemon <mellon@fugue.com>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/3kDtc2F4_DTr_u4fa7g9Gryp63Y>
Cc: Ole Troan <otroan@employees.org>, "homenet@ietf.org Group" <homenet@ietf.org>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 18:56:59 -0000

> On Feb 19, 2015, at 1:45 PM 2/19/15, Ted Lemon <mellon@fugue.com> =
wrote:
>=20
> On Feb 19, 2015, at 1:29 PM, Ralph Droms <rdroms.ietf@gmail.com> =
wrote:
>> If I can extrapolate and oversimplify a bit, now we've gotten to a =
fundamental problem: how does a random collection of devices, links and =
ports sort itself by DWIM into a coherent home network?  How does a =
device with 16 ports decide to group ports (0-5, 7, 10), (6, 8, 12-15) =
and (9, 11) into separate subnets?
>=20
> What Mikael is saying is that on homenet devices (not switches) each =
port is treated as a separate network, on the assumption that all of the =
physical ports on the homenet device are likely to connect to routers, =
and that any switched topology would be done using switches connected to =
homenet routers.

But I think one of the important points for homenet is that many people =
will just buy "internet" devices, not routers and switches.  I've been =
out of the loop so I should go back and check the architecture before I =
say too much more ... what is the expectation for grouping ports on =
homenet devices and is there an expectation that people will buy homenet =
devices and switches and know where to use them both?

>=20
> I am not convinced by this; one of the issues I see here is that until =
DNSSD comes up with a solution, we are breaking service discovery on the =
home network by doing this.   Granted, we already do that from Wifi to =
wired, but this seems gratuitous.

..and, of course, if we solve WiFi-wired for DNS-SD, the solution will =
likely work for some small number of subnets.

- Ralph



From nobody Thu Feb 19 11:06:34 2015
Return-Path: <mellon@fugue.com>
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 06FEA1A003A for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 11:06:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 Gfevy-bTMQz8 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 11:06:32 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 187A51A0021 for <homenet@ietf.org>; Thu, 19 Feb 2015 11:06:32 -0800 (PST)
Received: from [10.0.20.107] (c-71-233-43-215.hsd1.nh.comcast.net [71.233.43.215]) by toccata.fugue.com (Postfix) with ESMTPSA id 8AD3A238164C; Thu, 19 Feb 2015 14:06:30 -0500 (EST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <54E6318C.9030609@openwrt.org>
Date: Thu, 19 Feb 2015 14:05:56 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <C8437CBF-DEF5-49D1-9908-6C784DAA0137@fugue.com>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <F2818678-A728-4300-896C-E220A0DF0D1A@employees.org> <ADBDED5C-5279-4A04-B7C8-FCCB453A8C4F@gmail.com> <B2BEAF63-D219-41A0-8209-1EEFE9667440@fugue.com> <54E6318C.9030609@openwrt.org>
To: Steven Barth <cyrus@openwrt.org>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/qlA71TlPRgJZMwngFbRw5B3tb_M>
Cc: Ole Troan <otroan@employees.org>, "homenet@ietf.org Group" <homenet@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 19:06:34 -0000

On Feb 19, 2015, at 1:55 PM, Steven Barth <cyrus@openwrt.org> wrote:
> There is draft-ietf-dnssd-hybrid-00 for which we have specified glued =
to HNCP and a reference implementation. I think DNSSD is actually mostly =
covered or are you referring to any specific issue of that solution?

Hm, I will have to try it out.   Is it in a distribution?


From nobody Thu Feb 19 11:07:09 2015
Return-Path: <mellon@fugue.com>
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 14FA11A00DF for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 11:07:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 7pyDAgnJTrcw for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 11:07:05 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 1EB031A00E5 for <homenet@ietf.org>; Thu, 19 Feb 2015 11:07:05 -0800 (PST)
Received: from [10.0.20.107] (c-71-233-43-215.hsd1.nh.comcast.net [71.233.43.215]) by toccata.fugue.com (Postfix) with ESMTPSA id 64AAD23824F1; Thu, 19 Feb 2015 14:07:04 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <alpine.DEB.2.02.1502191951220.4007@uplift.swm.pp.se>
Date: Thu, 19 Feb 2015 14:06:31 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <F3EC1D5B-B03C-4757-8F04-6A0AEE7DB846@fugue.com>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <54E58238.9030809@mtcc.com> <874mqigcct.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191622510.4007@uplift.swm.pp.se> <87vbixg9fe.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191806381.4007@uplift.swm.pp.se> <87lhjtg6jc.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191826230.4007@uplift.swm.pp.se> <2FE73365-ECD7-49C3-8476-934CD1032542@fugue.com> <alpine.DEB.2.02.1502191924250.4007@uplift.swm.pp.se> <DE5D415F-4804-44C2-9621-523C3EFBC859@fugue.com> <alpine.DEB.2.02.1502191951220.4007@uplift.swm.pp.se>
To: Mikael Abrahamsson <swmike@swm.pp.se>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/e2amADdyHX53OeNuteYQv42DzZ0>
Cc: homenet@ietf.org
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 19:07:08 -0000

On Feb 19, 2015, at 1:55 PM, Mikael Abrahamsson <swmike@swm.pp.se> =
wrote:
> My employer has millions of subscribers using IPv4 multicast TV =
channels currently.

How's that getting through the NAT?


From nobody Thu Feb 19 11:08:35 2015
Return-Path: <mellon@fugue.com>
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 AAB541A0068 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 11:08:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 NXix6suphYLj for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 11:08:28 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 8E4221A0013 for <homenet@ietf.org>; Thu, 19 Feb 2015 11:08:28 -0800 (PST)
Received: from [10.0.20.107] (c-71-233-43-215.hsd1.nh.comcast.net [71.233.43.215]) by toccata.fugue.com (Postfix) with ESMTPSA id 4299623824F1; Thu, 19 Feb 2015 14:08:26 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <812BE11C-CB57-4594-81CD-A54AC8A16EFF@gmail.com>
Date: Thu, 19 Feb 2015 14:07:53 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <23AD334B-6349-4978-B90C-248A22CD5FE7@fugue.com>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <F2818678-A728-4300-896C-E220A0DF0D1A@employees.org> <ADBDED5C-5279-4A04-B7C8-FCCB453A8C4F@gmail.com> <B2BEAF63-D219-41A0-8209-1EEFE9667440@fugue.com> <812BE11C-CB57-4594-81CD-A54AC8A16EFF@gmail.com>
To: Ralph Droms <rdroms.ietf@gmail.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/hYfyYn1nlFUlyhTtbyJjOgdMsQI>
Cc: Ole Troan <otroan@employees.org>, "homenet@ietf.org Group" <homenet@ietf.org>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 19:08:33 -0000

On Feb 19, 2015, at 1:56 PM, Ralph Droms <rdroms.ietf@gmail.com> wrote:
> But I think one of the important points for homenet is that many =
people will just buy "internet" devices, not routers and switches.  I've =
been out of the loop so I should go back and check the architecture =
before I say too much more ... what is the expectation for grouping =
ports on homenet devices and is there an expectation that people will =
buy homenet devices and switches and know where to use them both?

I don't think the architecture document says anything about this.   It's =
how CeroWRT currently operates by default.   I find it to be a royal =
pain, and in fact that's why I run OpenWRT and not CeroWRT.


From nobody Thu Feb 19 11:09:19 2015
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 C14AA1A0006 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 11:09:15 -0800 (PST)
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 Ft_kUE3A-LLb for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 11:09:10 -0800 (PST)
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 749131A0077 for <homenet@ietf.org>; Thu, 19 Feb 2015 11:09:08 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 003DFA5; Thu, 19 Feb 2015 20:09:06 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1424372947; bh=PbRpMd6Ix0+oeq5MAzykloRtXGAUyqRQL2h8UnUD8xs=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=iJlWbPKFxfVkuXsdMc6BdME2Fj9bV3rxQc9uk0IGfm+Vjft0/Oc0slQ26VW4iKRDw jvbvNYi7pSzM6uxFC1Z+A3vuwQhcoEjjOllhTJ6kUcWkxVxhjv1H9JpqxBsYgEuC4W lhoWUyOx5Kc9QOAKNIO9jw/exjztXAeQtUJYFjvQ=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id ED007A4; Thu, 19 Feb 2015 20:09:06 +0100 (CET)
Date: Thu, 19 Feb 2015 20:09:06 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <812BE11C-CB57-4594-81CD-A54AC8A16EFF@gmail.com>
Message-ID: <alpine.DEB.2.02.1502192006310.4007@uplift.swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <F2818678-A728-4300-896C-E220A0DF0D1A@employees.org> <ADBDED5C-5279-4A04-B7C8-FCCB453A8C4F@gmail.com> <B2BEAF63-D219-41A0-8209-1EEFE9667440@fugue.com> <812BE11C-CB57-4594-81CD-A54AC8A16EFF@gmail.com>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/Xm2HQcUjYrTs6GvbHdSj2l066sQ>
Cc: Ole Troan <otroan@employees.org>, Ted Lemon <mellon@fugue.com>, "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 19:09:15 -0000

On Thu, 19 Feb 2015, Ralph Droms wrote:

> But I think one of the important points for homenet is that many people 
> will just buy "internet" devices, not routers and switches.  I've been 
> out of the loop so I should go back and check the architecture before I 
> say too much more ... what is the expectation for grouping ports on 
> homenet devices and is there an expectation that people will buy homenet 
> devices and switches and know where to use them both?

As far as I know, this hasn't been discussed that much. From a quick look 
in the arch document, there are all kinds of examples. Looking for 
instance at 3.2.2.1 we have all kinds of topologies, from router-router 
links without any hosts on it, to subnets with 2 hosts on them, to shared 
networks used to inerconnect routers. From what I remember and what I can 
see the document stating, the solution is supposed to handle all kinds of 
topologies.

> ..and, of course, if we solve WiFi-wired for DNS-SD, the solution will 
> likely work for some small number of subnets.

What is "small" here? If it works for 2, why wouldn't it work for 50?

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


From nobody Thu Feb 19 11:09:44 2015
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 F25CC1A0078 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 11:09:42 -0800 (PST)
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 kTb8Zr3C-U0i for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 11:09:40 -0800 (PST)
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 B82611A0077 for <homenet@ietf.org>; Thu, 19 Feb 2015 11:09:39 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 5A549A5; Thu, 19 Feb 2015 20:09:38 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1424372978; bh=LA07QIhADLWMqzjb20LKmyWttGMbUSdx4SRle+9tj7s=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=d5hI14gPbeMWlYhQA20KABK94MU2dr4zdrF26BXRZ9JY6zOpesotCkphkdACwIVku jn/YVc7z1sR9IMS+p9iSyJPPIp3+oUzUCp8XHgj2KdU63vn3BFX31M8t6+tIj+oG+1 6Amx3eoXK/kaGJz8Pb9H1LGiiPL70bSPzlW4Lm10=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 56296A4; Thu, 19 Feb 2015 20:09:38 +0100 (CET)
Date: Thu, 19 Feb 2015 20:09:38 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Ted Lemon <mellon@fugue.com>
In-Reply-To: <F3EC1D5B-B03C-4757-8F04-6A0AEE7DB846@fugue.com>
Message-ID: <alpine.DEB.2.02.1502192009120.4007@uplift.swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <54E58238.9030809@mtcc.com> <874mqigcct.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191622510.4007@uplift.swm.pp.se> <87vbixg9fe.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191806381.4007@uplift.swm.pp.se> <87lhjtg6jc.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191826230.4007@uplift.swm.pp.se> <2FE73365-ECD7-49C3-8476-934CD1032542@fugue.com> <alpine.DEB.2.02.1502191924250.4007@uplift.swm.pp.se> <DE5D415F-4804-44C2-9621-523C3EFBC859@fugue.com> <alpine.DEB.2.02.1502191951220.4007@uplift.swm.pp.se> <F3EC1D5B-B03C-4757-8F04-6A0AEE7DB846@fugue.com>
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/2HdrvT10Mpv125ipiv6yNMNleDs>
Cc: homenet@ietf.org
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 19:09:43 -0000

On Thu, 19 Feb 2015, Ted Lemon wrote:

> On Feb 19, 2015, at 1:55 PM, Mikael Abrahamsson <swmike@swm.pp.se> wrote:
>> My employer has millions of subscribers using IPv4 multicast TV channels currently.
>
> How's that getting through the NAT?

IGMP proxy in the HGW.

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


From nobody Thu Feb 19 11:11:24 2015
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 62E1F1A0006 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 11:11:23 -0800 (PST)
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 1ofSLlPQUGoE for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 11:11:22 -0800 (PST)
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 020FD1A0063 for <homenet@ietf.org>; Thu, 19 Feb 2015 11:11:22 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 909EBA5; Thu, 19 Feb 2015 20:11:20 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1424373080; bh=JUMP5E6YCEiyuy9Yp1FtAg2tTbqfMyTkK/Ls6QcVTig=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=LCwKwXcZ8rUOiMiHa5u3OuFUgNGY7y715dVwLcTgKWXKNg9lxjuxyjaIsFcAOM26m 05rjmbg7KwEqGyCFJZkHcMzWPGxlIkY8DhK9vtpmdZ98bTWeCmCkPmzaZtvniXKdic 9ZkhX21YzSRQ8GPAePwyblQZOFUVou9c8/Zs3OEo=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 89379A4; Thu, 19 Feb 2015 20:11:20 +0100 (CET)
Date: Thu, 19 Feb 2015 20:11:20 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Ted Lemon <mellon@fugue.com>
In-Reply-To: <23AD334B-6349-4978-B90C-248A22CD5FE7@fugue.com>
Message-ID: <alpine.DEB.2.02.1502192010040.4007@uplift.swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <F2818678-A728-4300-896C-E220A0DF0D1A@employees.org> <ADBDED5C-5279-4A04-B7C8-FCCB453A8C4F@gmail.com> <B2BEAF63-D219-41A0-8209-1EEFE9667440@fugue.com> <812BE11C-CB57-4594-81CD-A54AC8A16EFF@gmail.com> <23AD334B-6349-4978-B90C-248A22CD5FE7@fugue.com>
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/D6A338I4zqniWSP4gydFO8Z4Kzw>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 19:11:23 -0000

On Thu, 19 Feb 2015, Ted Lemon wrote:

> I don't think the architecture document says anything about this.  It's 
> how CeroWRT currently operates by default.  I find it to be a royal 
> pain, and in fact that's why I run OpenWRT and not CeroWRT.

I'd imagine it's easier to do AQM on routed ports instead of switched 
ports as well, that's where I can imagine CeroWRT choosing this approach.

It's good that we're having this discussions since I seem to not be the 
only one thinking that there should be one port per subnet.

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


From nobody Thu Feb 19 11:17:39 2015
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 2B33E1A0023 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 11:17:38 -0800 (PST)
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 oeuOBBoGlVtI for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 11:17:37 -0800 (PST)
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 C35471A0039 for <homenet@ietf.org>; Thu, 19 Feb 2015 11:17:36 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 57A1EA5; Thu, 19 Feb 2015 20:17:34 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1424373454; bh=CEzVdODaAWZrcDYRkDRvsuaiSkXxQ9OJ09FeOF6k65U=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=MkXV+/8qWYbjvxAd6vwXtGZAqHX3L+sKL//EycO0AHSeqloTVVtgKjcVL88q8pDNp PC8XcB3Y4gm9swB0HHbX3l7d8dhS6JopDRjy/soqntHCoSwn96u5Lwh7zhE4nxdeNe WvlBrIY0xUi2TRB4LOjiELIXcWCVef6/CjO3BiU4=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 5158BA4; Thu, 19 Feb 2015 20:17:34 +0100 (CET)
Date: Thu, 19 Feb 2015 20:17:34 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Ted Lemon <mellon@fugue.com>
In-Reply-To: <alpine.DEB.2.02.1502192009120.4007@uplift.swm.pp.se>
Message-ID: <alpine.DEB.2.02.1502192016130.4007@uplift.swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <54E58238.9030809@mtcc.com> <874mqigcct.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191622510.4007@uplift.swm.pp.se> <87vbixg9fe.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191806381.4007@uplift.swm.pp.se> <87lhjtg6jc.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191826230.4007@uplift.swm.pp.se> <2FE73365-ECD7-49C3-8476-934CD1032542@fugue.com> <alpine.DEB.2.02.1502191924250.4007@uplift.swm.pp.se> <DE5D415F-4804-44C2-9621-523C3EFBC859@fugue.com> <alpine.DEB.2.02.1502191951220.4007@uplift.swm.pp.se> <F3EC1D5B-B03C-4757-8F04-6A0AEE7DB846@fugue.com> <alpine.DEB.2.02.1502192009120.4007@uplift.swm.pp.se>
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/OFkt5jYjwKWZFIQwCnauj1fywjA>
Cc: homenet@ietf.org
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 19:17:38 -0000

On Thu, 19 Feb 2015, Mikael Abrahamsson wrote:

> On Thu, 19 Feb 2015, Ted Lemon wrote:
>
>> On Feb 19, 2015, at 1:55 PM, Mikael Abrahamsson <swmike@swm.pp.se> wrote:
>>> My employer has millions of subscribers using IPv4 multicast TV channels 
>>> currently.
>> 
>> How's that getting through the NAT?
>
> IGMP proxy in the HGW.

Perhaps should add that we're doing the same thing for IPv6, but using MLD 
proxy instead, of course.

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


From nobody Thu Feb 19 11:18:59 2015
Return-Path: <mellon@fugue.com>
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 87C551A005C for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 11:18:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 eteKaEWd8Q41 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 11:18:57 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 925921A0013 for <homenet@ietf.org>; Thu, 19 Feb 2015 11:18:55 -0800 (PST)
Received: from [10.0.20.107] (c-71-233-43-215.hsd1.nh.comcast.net [71.233.43.215]) by toccata.fugue.com (Postfix) with ESMTPSA id D0E68238164C; Thu, 19 Feb 2015 14:18:54 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <alpine.DEB.2.02.1502192010040.4007@uplift.swm.pp.se>
Date: Thu, 19 Feb 2015 14:18:21 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <08996755-7862-4CB7-B5B7-9BFBFA7594F6@fugue.com>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <F2818678-A728-4300-896C-E220A0DF0D1A@employees.org> <ADBDED5C-5279-4A04-B7C8-FCCB453A8C4F@gmail.com> <B2BEAF63-D219-41A0-8209-1EEFE9667440@fugue.com> <812BE11C-CB57-4594-81CD-A54AC8A16EFF@gmail.com> <23AD334B-6349-4978-B90C-248A22CD5FE7@fugue.com> <alpine.DEB.2.02 .1502192010040.4007@uplift.swm.pp.se>
To: Mikael Abrahamsson <swmike@swm.pp.se>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/NBr4Cy_DTo_G1v1ofe6g-vjIdN8>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 19:18:58 -0000

On Feb 19, 2015, at 2:11 PM, Mikael Abrahamsson <swmike@swm.pp.se> =
wrote:
> I'd imagine it's easier to do AQM on routed ports instead of switched =
ports as well, that's where I can imagine CeroWRT choosing this =
approach.

I don't think it is easier to do AQM on routed ports.   If you do the =
easy version of AQM for switched ports, that's easy; if you do per-port =
AQM I think it's equally hard in both cases. The plumbing for the L2 =
solution would look different than for the L3 solution, and that might =
make it trickier, though.

CeroWRT did this, as far as I understand it, because Dave wanted to =
shake out cross-subnet issues, not because he felt it was technically =
preferable in the long run, but perhaps I am misrepresenting his =
position on the topic.

> It's good that we're having this discussions since I seem to not be =
the only one thinking that there should be one port per subnet.

Indeed, there are two of you!


From nobody Thu Feb 19 11:27:36 2015
Return-Path: <rdroms.ietf@gmail.com>
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 491801A0063 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 11:27:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 8sz-UBYDJBu9 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 11:27:33 -0800 (PST)
Received: from mail-qg0-x234.google.com (mail-qg0-x234.google.com [IPv6:2607:f8b0:400d:c04::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EA8231A0039 for <homenet@ietf.org>; Thu, 19 Feb 2015 11:27:32 -0800 (PST)
Received: by mail-qg0-f52.google.com with SMTP id h3so8771620qgf.11 for <homenet@ietf.org>; Thu, 19 Feb 2015 11:27:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=K2FAXroB/JRUfPmWFTHHrAzVsKchftiGySLUBbN9nmI=; b=QFAKIJa5DbEMQcXOgvbVYN6KY6L3N6rh6A4jc9XbfgXPQRIqaE3+9lYcGJiRoF5yBU /OI91JGzE4Q8eShnGyzHsF4mJ9xBHukB59KAFZLIeXfCmZePFdNqKK0NYvVggkiafcic ZilUn0vSKhyXbL44UDzAu+Hqi+z+VAotN/rixL59IYki/LhLOcTA0TddK3rUItTziobm ZI5ZA7iN7hmYWXwpKdyEeIkupdLA7Pv5u5oNTk0spTJRWVIoUmuJAOFaNdFpo6VQxGOj Z1rQzp8GUgm3s9Mk1MuNmjZ60BYoxpsA2cLupqbANk2/+cymcpJw77HAffapMluoJmwS nSXw==
X-Received: by 10.140.234.136 with SMTP id f130mr15732749qhc.49.1424374052181;  Thu, 19 Feb 2015 11:27:32 -0800 (PST)
Received: from rtp-vpn1-1597.cisco.com (rtp-isp-nat1.cisco.com. [64.102.254.33]) by mx.google.com with ESMTPSA id a92sm5292208qgf.11.2015.02.19.11.27.31 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 19 Feb 2015 11:27:31 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <alpine.DEB.2.02.1502192006310.4007@uplift.swm.pp.se>
Date: Thu, 19 Feb 2015 14:27:29 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <4CAD8BD6-66DD-4747-8C1A-B5109BD4F01C@gmail.com>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <F2818678-A728-4300-896C-E220A0DF0D1A@employees.org> <ADBDED5C-5279-4A04-B7C8-FCCB453A8C4F@gmail.com> <B2BEAF63-D219-41A0-8209-1EEFE9667440@fugue.com> <812BE11C-CB57-4594-81CD-A54AC8A16EFF@gmail.com> <alpine.DEB.2.02.1502192006310.4007@uplift.swm.pp.se>
To: Mikael Abrahamsson <swmike@swm.pp.se>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/S6SGuWbWne2foG72DYY-WrHImrU>
Cc: Ole Troan <otroan@employees.org>, Ted Lemon <mellon@fugue.com>, "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 19:27:35 -0000

> On Feb 19, 2015, at 2:09 PM 2/19/15, Mikael Abrahamsson =
<swmike@swm.pp.se> wrote:
>=20
> On Thu, 19 Feb 2015, Ralph Droms wrote:
>=20
>> But I think one of the important points for homenet is that many =
people will just buy "internet" devices, not routers and switches.  I've =
been out of the loop so I should go back and check the architecture =
before I say too much more ... what is the expectation for grouping =
ports on homenet devices and is there an expectation that people will =
buy homenet devices and switches and know where to use them both?
>=20
> As far as I know, this hasn't been discussed that much. =46rom a quick =
look in the arch document, there are all kinds of examples. Looking for =
instance at 3.2.2.1 we have all kinds of topologies, from router-router =
links without any hosts on it, to subnets with 2 hosts on them, to =
shared networks used to inerconnect routers. =46rom what I remember and =
what I can see the document stating, the solution is supposed to handle =
all kinds of topologies.

I promise to go back and re-read the architecture document because I'm =
having trouble matching the architecture we're discussing here with the =
desired properties and logical architectures we want the homenet devices =
to self-organize into.

>> ..and, of course, if we solve WiFi-wired for DNS-SD, the solution =
will likely work for some small number of subnets.
>=20
> What is "small" here? If it works for 2, why wouldn't it work for 50?

In theory, sure.  In practice, 25x (or maybe 25^2?) things to break.

- Ralph

>=20
> --=20
> Mikael Abrahamsson    email: swmike@swm.pp.se


From nobody Thu Feb 19 11:38:00 2015
Return-Path: <jmh@joelhalpern.com>
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 B534C1A0021 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 11:37:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 phwgK889jqcW for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 11:37:57 -0800 (PST)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8E70F1A876D for <homenet@ietf.org>; Thu, 19 Feb 2015 11:37:41 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 6B9BE1C05EF; Thu, 19 Feb 2015 11:37:41 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from Joels-MacBook-Pro.local (pool-70-106-135-240.clppva.east.verizon.net [70.106.135.240]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 37AE51C00CD; Thu, 19 Feb 2015 11:37:36 -0800 (PST)
Message-ID: <54E63B40.20301@joelhalpern.com>
Date: Thu, 19 Feb 2015 14:36:32 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Ted Lemon <mellon@fugue.com>, Mikael Abrahamsson <swmike@swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <54E58238.9030809@mtcc.com> <874mqigcct.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191622510.4007@uplift.swm.pp.se> <87vbixg9fe.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191806381.4007@uplift.swm.pp.se> <87lhjtg6jc.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191826230.4007@uplift.swm.pp.se> <2FE73365-ECD7-49C3-8476-934CD1032542@fugue.com>
In-Reply-To: <2FE73365-ECD7-49C3-8476-934CD1032542@fugue.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/bWXPoSIW_CmNHW33kcuMCWFPA-M>
Cc: homenet@ietf.org, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 19:37:58 -0000

I would note that RFC 7368 says that "simple Layer 3 topologies 
involving as few subnets as possible are preferred in home networks".  I 
presume this is reflective of WG agreement.
While it does go on to note that multiple subnets are sometimes needed, 
mandating that each physical port on the access router be a distinct 
subnet (much less extending such a mandate further in the home) seems to 
violate this agreement.

Yours,
Joel M. Halpern

On 2/19/15 1:11 PM, Ted Lemon wrote:
> On Feb 19, 2015, at 12:33 PM, Mikael Abrahamsson <swmike@swm.pp.se> wrote:
>> Sure, ISIS could be made smarter when it comes to this, but it all comes down to what the requirements are. Right now when we started to evaluate routing protocols, people started pitching USP for their perticular favorite, and we found out we weren't even on the same page when it comes to requirements, and even what a homenet looks like.
>
> I think it is you who are not on the same page, not the working group.   The working group recently published a document describing our goals, RFC 7368.   Many of the points you have raised as supposed points of disagreement are addressed in the document, although I will admit that it is not always obvious that they have been addressed.   The case of routing over Wifi was discussed at length; the text referring to it in the document is here:
>
>     Due to the use of a variety of diverse underlying link technologies,
>     path selection in a homenet may benefit from being more refined than
>     minimising hop count.
>
> Regarding your criticism about people pitching their favorite routing protocols, you seem to be doing precisely that, so the criticism seems a bit unfair.   The responses you have been hearing seem like legitimate attempts to address points you have raised on a technical level, not mere advocacy, and it is unfortunate that you would suggest otherwise: I haven't actually seen you raise any technical points in favor of IS-IS, which you seem to be advocating.
>
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>


From nobody Thu Feb 19 11:46:38 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 0C92A1A87B0 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 11:46:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.349
X-Spam-Level: 
X-Spam-Status: No, score=0.349 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, HELO_EQ_FR=0.35] autolearn=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 fvIE4ZwJbG0j for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 11:46:30 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 9CA211A88DA for <homenet@ietf.org>; Thu, 19 Feb 2015 11:46:09 -0800 (PST)
Received: from potemkin.univ-paris7.fr (potemkin.univ-paris7.fr [IPv6:2001:660:3301:8000::1:1]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t1JJk58u013773 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 19 Feb 2015 20:46:05 +0100
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by potemkin.univ-paris7.fr (8.14.4/8.14.4/relay2/56228) with ESMTP id t1JJk4RO007829; Thu, 19 Feb 2015 20:46:05 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id DB9862A1091; Thu, 19 Feb 2015 20:46:04 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id y9NEARypweWH; Thu, 19 Feb 2015 20:45:57 +0100 (CET)
Received: from pirx.pps.jussieu.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id B41732A10B1; Thu, 19 Feb 2015 20:45:57 +0100 (CET)
Date: Thu, 19 Feb 2015 20:45:58 +0100
Message-ID: <87fva1fzwp.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: "Leddy, John" <John_Leddy@cable.comcast.com>
In-Reply-To: <87h9uhg529.wl-jch@pps.univ-paris-diderot.fr>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <A5767F83-3D0C-40E5-A73B-912E3C160A42@fugue.com> <alpine.DEB.2.02.1502191235240.4007@uplift.swm.pp.se> <87zj89gaqm.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191804050.4007@uplift.swm.pp.se> <D10B8924.6BD5%John_Leddy@cable.comcast.com> <87h9uhg529.wl-jch@pps.univ-paris-diderot.fr>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]); Thu, 19 Feb 2015 20:46:05 +0100 (CET)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Thu, 19 Feb 2015 20:46:05 +0100 (CET)
X-Miltered: at korolev with ID 54E63D7D.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 54E63D7C.003 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54E63D7D.001 from potemkin.univ-paris7.fr/potemkin.univ-paris7.fr/null/potemkin.univ-paris7.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Enveloppe: 54E63D7C.003 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54E63D7D.001 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 54E63D7C.003 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/P113ErjLQUTNspHy6ezWKp-w3gY>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: [homenet] More about marginal links [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 19:46:33 -0000

> A marginal link is simply one that has a measurable amount of packet loss.

Ok, re-reading this exchange, it looks like I may have wrongly assumed
that people are aware of background.  I'll need to put that into the
routing comparison document, this is as good a place as any to draft my
text.

Carrier and enterprise routing protocols are optimised for wired networks,
where a link is either down (drops all packets) or up (drops one packet in
10^10).

Home networks usually include link technologies that have an intermediate
"marginal" state: a link that drops a non-negligible fraction of packets.
With 802.11, in particular, marginal links have fairly unpleasant performance
characteristics.  For example, if the BER is 10^-4,

  - multicast packets are dropped at roughly the nominal rate (10% for 120
    byte packets, 90% for 1500 byte packets);
  - unicast packets are dropped at a much lower rate, but the efficiency
    suffers (0.9 for 120 byte packets, 0.1 for 1500 byte packets).
  - unicast packets have a high probability of being duplicated (no
    figures given, I'm too lazy to look up the size of an ACK frame).

This is of course a very naive analysis -- in practice, errors tend to
come in bursts, and furthermore 802.11a/g/n implements some very complex
lower-layer magic.  Don't believe any results from computation or
simulation, with radio, only actual testing in real-world networks is
trustworthy.

This has two consequences for routing protocols:

  (1) the routing protocol must be able to prefer solid links to marginal
      ones when there is enough redundancy;
  (2) control data may fail to be propagated in a timely manner,
      especially if it is sent over multicast.


1. Prefer solid links

This is pretty obvious.  If you can choose between an Ethernet link and
a wireless link with heavy packet loss, choose the Ethernet.  But there
are more subtle cases that are extremely common in practice:

   Internet --- A --- B....C          --- is Ethernet
                 .        .           ... is WiFi
                  ........

A is your CPE, B is the router in your living room, connected by Ethernet
to the CPE, and C is the wireless router in the guest room.  Yeah, it's
a large house.
                  
Suppose now that the wireless link B..C is rock solid, but the longer A..C
link is marginal.  Murphy's law dictates that the link A..C will have huge
packet loss, but it will be just good enough for the routing instances on
A and C to become neighbours.  If the routing protocol performs hop-count
routing, even if it is smart enough to prefer wired to wireless, it will
prefer the highly marginal route A..C to the rock solid route A-B..C.

Note that this is easily fixed by a competent administrator: just disable
the wireless interface on A.  But this is Homenet, and we're assuming
there's no administrator.

In the mesh community, the hop-count metric is known as "worst-path routing".


2. Control data may be delayed

Since multicast has such massive packet drops, the routing data may be
dropped or delayed.  Using a reliable sub-protocol for propagating
critical data, as is done by OSPF, IS-IS and EIGRP might work if the
reliable protocol can cope with the weirdness of the 802.11 MAC.  If it
cannot, it might (or might not, I don't know) suffer from routing
pathologies, such as routing loops in OSPF and IS-IS, inconsistent DR/DER
election, and SIA in EIGRP.

Of course, people have managed to get link-state protocols to work on
wireless networks, even on highly marginal mesh networks, but they had to
design new mechanisms.  OLSR, for example, doesn't use reliable flooding
and DR election, but instead uses unreliable flooding and MPR election,
together with a mechanism that drops marginal links.  I refer you to
RFCs 3626 and 5449.

Babel uses different mechanisms.  Babel uses a feasibility condition
similar to that of EIGRP, which means that it avoids loops even when
control data is delayed.  Unlike EIGRP, however, it doesn't rely on
a reliable subprotocol, and it doesn't have an active phase.  End-to-end
synchronisation is achieved in a softer manner, and a single router that
fails to propagate requests doesn't prevent reconvergence if there are
alternate paths available -- look Ma, no SIA, even with massive packet
loss.  (This is not meant as a critique of EIGRP -- I rather like EIGRP,
and I'm pretty sure it could be adapted to home networks if somebody spent
a couple of years of their life doing that.)


I'd like to finish this slightly lengthy message by stating that the
current implementation of Babel does not work well in networks where all
links are highly marginal; in other words, Babel really wants a solid
backbone to be available.  In particular, Babel tends to aggregate control
data into large packets, which have a higher probability of being dropped,
and tends to drop links that have more than 90% pre-ARQ drop rate for
full-size frames.  There exist specialised, highly tuned protocols that
are able to deal with topologies that rely on such very marginal links,
notably bmx6, BATMAN-adv, and the highly tuned version of OLSR-ETX used by
the Berlin and Vienna meshes.

-- Juliusz


From nobody Thu Feb 19 12:06:08 2015
Return-Path: <pierre.pfister@darou.fr>
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 8BD781A0115 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 12:06:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.357
X-Spam-Level: 
X-Spam-Status: No, score=-1.357 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553, T_RP_MATCHES_RCVD=-0.01] autolearn=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 y4YtIuknswe8 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 12:06:04 -0800 (PST)
Received: from ks395963.kimsufi.com (darou.fr [IPv6:2001:41d0:8:408c::1111]) by ietfa.amsl.com (Postfix) with ESMTP id E65081A00FA for <homenet@ietf.org>; Thu, 19 Feb 2015 12:06:03 -0800 (PST)
Received: by ks395963.kimsufi.com (Postfix, from userid 112) id 015116075F; Thu, 19 Feb 2015 21:06:02 +0100 (CET)
Received: from [172.20.10.2] (unknown [37.162.179.20]) (Authenticated sender: pierre@darou.fr) by ks395963.kimsufi.com (Postfix) with ESMTPSA id 78291602F4; Thu, 19 Feb 2015 21:06:00 +0100 (CET)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Pierre Pfister <pierre.pfister@darou.fr>
In-Reply-To: <54E63B40.20301@joelhalpern.com>
Date: Thu, 19 Feb 2015 21:06:00 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <92BC4482-AF89-4649-816D-9DC80316FD0E@darou.fr>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <54E58238.9030809@mtcc.com> <874mqigcct.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191622510.4007@uplift.swm.pp.se> <87vbixg9fe.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191806381.4007@uplift.swm.pp.se> <87lhjtg6jc.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191826230.4007@uplift.swm.pp.se> <2FE73365-ECD7-49C3-8476-934CD1032542@fugue.com> <54E63B40.20301@joelhalpern.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/X2IrCkYe0DqFEdwh_uCC5yFTLOU>
Cc: homenet@ietf.org, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>, Ted Lemon <mellon@fugue.com>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 20:06:06 -0000

> I would note that RFC 7368 says that "simple Layer 3 topologies =
involving as few subnets as possible are preferred in home networks".  I =
presume this is reflective of WG agreement.
> While it does go on to note that multiple subnets are sometimes =
needed, mandating that each physical port on the access router be a =
distinct subnet (much less extending such a mandate further in the home) =
seems to violate this agreement.
>=20
> Yours,
> Joel M. Halpern

+1

Why would we even want to separate these 4 switched ports in the first =
place ? I know we are L3 people but, this is IMHO, going too far. Don=92t =
kill Ethernet switching.=20
- It works well when you don=92t have drastically different throughputs.=20=

- It has non-expensive and efficient hardware home-router vendors are =
used to put into their devices.
- Home routers mostly don=92t have L3 hardware. They are not able to =
route at 1Gbps.

The goal of introducing L3 routing was to isolate very different link =
types such as Wifi Vs GigabitEthernet.

I know we *did* separate ports in all the homenet demos at bits-n-bites. =
Maybe this was sending the wrong message. The purpose was to show the =
principle of introducing routing in the home. I guess next time it will =
be 2x2 ports instead of 4x1 ports.

- Pierre

>=20
> On 2/19/15 1:11 PM, Ted Lemon wrote:
>> On Feb 19, 2015, at 12:33 PM, Mikael Abrahamsson <swmike@swm.pp.se> =
wrote:
>>> Sure, ISIS could be made smarter when it comes to this, but it all =
comes down to what the requirements are. Right now when we started to =
evaluate routing protocols, people started pitching USP for their =
perticular favorite, and we found out we weren't even on the same page =
when it comes to requirements, and even what a homenet looks like.
>>=20
>> I think it is you who are not on the same page, not the working =
group.   The working group recently published a document describing our =
goals, RFC 7368.   Many of the points you have raised as supposed points =
of disagreement are addressed in the document, although I will admit =
that it is not always obvious that they have been addressed.   The case =
of routing over Wifi was discussed at length; the text referring to it =
in the document is here:
>>=20
>>    Due to the use of a variety of diverse underlying link =
technologies,
>>    path selection in a homenet may benefit from being more refined =
than
>>    minimising hop count.
>>=20
>> Regarding your criticism about people pitching their favorite routing =
protocols, you seem to be doing precisely that, so the criticism seems a =
bit unfair.   The responses you have been hearing seem like legitimate =
attempts to address points you have raised on a technical level, not =
mere advocacy, and it is unfortunate that you would suggest otherwise: I =
haven't actually seen you raise any technical points in favor of IS-IS, =
which you seem to be advocating.
>>=20
>> _______________________________________________
>> homenet mailing list
>> homenet@ietf.org
>> https://www.ietf.org/mailman/listinfo/homenet
>>=20
>=20
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet


From nobody Thu Feb 19 12:12:56 2015
Return-Path: <hrogge@gmail.com>
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 473FF1A006F for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 12:12:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 cmdWdWK7M9Os for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 12:12:54 -0800 (PST)
Received: from mail-wi0-x22c.google.com (mail-wi0-x22c.google.com [IPv6:2a00:1450:400c:c05::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5346D1A013B for <homenet@ietf.org>; Thu, 19 Feb 2015 12:12:50 -0800 (PST)
Received: by mail-wi0-f172.google.com with SMTP id l15so50622372wiw.5 for <homenet@ietf.org>; Thu, 19 Feb 2015 12:12:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=YqZKx7waVGnrP92EV0MHliJUQYrniPtbMRUNHgyouPo=; b=gH75KOfNV7Q2hzSoBUvaAT05cIExM81AxijctwGK4mO3sAPaW4sXx8Xk2fc/mt8m31 xKagBYqv4vHeRiBAmpjSUbSUcWnso+NL0tX2z0dZlMDIDSJKR/NRavsUB99UdTv331Gi ZDrhbxVDx2NFqQWFkDbcCyOF3cj34XI7zuACSEoRASe7NaNEBW0jMOxWzD2ilbYwJBiX 2GoYNdVB7+LrT7SjLShaX8nOiZ+T3J6LK2ExyqZLfAec27qAUZBmqtdoXRj14Cf9uOCE uAnk7CiBtRCUQBZv1FC0Jo3addlRwMnJel4yWtK7rxwt4T8LXc/fdvejh9/Mmv45yQsp GfHQ==
X-Received: by 10.180.102.69 with SMTP id fm5mr17870081wib.61.1424376769040; Thu, 19 Feb 2015 12:12:49 -0800 (PST)
MIME-Version: 1.0
Received: by 10.27.77.212 with HTTP; Thu, 19 Feb 2015 12:12:28 -0800 (PST)
In-Reply-To: <F2818678-A728-4300-896C-E220A0DF0D1A@employees.org>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <F2818678-A728-4300-896C-E220A0DF0D1A@employees.org>
From: Henning Rogge <hrogge@gmail.com>
Date: Thu, 19 Feb 2015 21:12:28 +0100
Message-ID: <CAGnRvuruZUFySm_T8FwEHEonusOvgPL4+bRkxpV6f+OoqPZtNA@mail.gmail.com>
To: Ole Troan <otroan@employees.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/q6EyLx6K_m0r3cKkVGZe3gzjaqM>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Ted Lemon <mellon@fugue.com>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 20:12:55 -0000

On Thu, Feb 19, 2015 at 7:18 PM, Ole Troan <otroan@employees.org> wrote:
> there are very few shared media around anymore. I don't think I've ever been connected to a 10base5.
> why should the IP subnet model emulate a shared medium, when the physical topology is a star.
>
> wireless with security is also a star topology, with a unidirectional broadcast channel.

Unfortunately on layer-1 both are still broadcast... you send a
unicast, it might interfere with anyone else in range.

Henning Rogge


From nobody Thu Feb 19 12:13:14 2015
Return-Path: <fred@cisco.com>
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 462931A88E3 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 12:13:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -114.511
X-Spam-Level: 
X-Spam-Status: No, score=-114.511 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_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] 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 HNJxjq2Vhg0K for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 12:13:11 -0800 (PST)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 192F81A88E1 for <homenet@ietf.org>; Thu, 19 Feb 2015 12:13:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4110; q=dns/txt; s=iport; t=1424376791; x=1425586391; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=ajv6G4L6k6DRGezPwqigReZSJfvV5U/S69nH4PWZUxw=; b=KI6KcYGP885aac7fY0m72N/jCdgWSU5vZ/eXBl/Bv80AgwfhCX1l/ygS pvdb+T0Bysb60OXP5tZblydAmOMEXzSvLYrlipIu9M3gerF6yOIzP5tEw NKOOFxUomuWCKGrAVXSxRZLxR3i7KpV/+yproURrtuiqr4tRgMfydNd34 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AeBQAyQ+ZU/4oNJK1bgwZSWgTCYAqFJ0oCgSNDAQEBAQEBfIQPAQEBBAEBATc0CxACAQgRBAEBAQoUECcLHQgCBAENBQiIJw3UHwEBAQEBAQEBAQEBAQEBAQEBAQEBARMEihF+hD0xB4MWgRQFj0uKWo5Lgz4ig25vgUR/AQEB
X-IronPort-AV: E=Sophos;i="5.09,610,1418083200"; d="scan'208";a="125114795"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by alln-iport-8.cisco.com with ESMTP; 19 Feb 2015 20:13:10 +0000
Received: from xhc-rcd-x06.cisco.com (xhc-rcd-x06.cisco.com [173.37.183.80]) by alln-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id t1JKDA2x009405 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 19 Feb 2015 20:13:10 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.149]) by xhc-rcd-x06.cisco.com ([173.37.183.80]) with mapi id 14.03.0195.001; Thu, 19 Feb 2015 14:13:09 -0600
From: "Fred Baker (fred)" <fred@cisco.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>, Ted Lemon <mellon@fugue.com>, Mikael Abrahamsson <swmike@swm.pp.se>
Thread-Topic: [homenet] Routing protocol comparison document
Thread-Index: AQHQSU34g5PABd2eZECo2yEJ1IgT9Zz2w36AgAAaSgCAABl7AIAABluAgAAB2ICAAHYtgIAAdn0AgACUFwCAAAN+AIAADi6AgAANtACAAAO9gIAAAveAgAAKtYCAABezAP//o5nn
Date: Thu, 19 Feb 2015 20:13:09 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553B0612B2EB@xmb-rcd-x09.cisco.com>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <54E58238.9030809@mtcc.com> <874mqigcct.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191622510.4007@uplift.swm.pp.se> <87vbixg9fe.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191806381.4007@uplift.swm.pp.se> <87lhjtg6jc.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191826230.4007@uplift.swm.pp.se> <2FE73365-ECD7-49C3-8476-934CD1032542@fugue.com>, <54E63B40.20301@joelhalpern.com>
In-Reply-To: <54E63B40.20301@joelhalpern.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.19.64.116]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/rCMbmCCIaod6qe0hjHLm3BfxiE0>
Cc: "homenet@ietf.org" <homenet@ietf.org>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 20:13:13 -0000

It seems, in each case, that the word "RECOMMEND" is far superior to "MUST"=
. If I connect two ports from the same router to the same LAN, I really don=
't normally want them in different subnets (although from a specific reason=
 I might choose that). MIF tells us that we can enumerate members of the sa=
me subnet on different physical media in certain cases. While that is true,=
 to my small mind it's not a great configuration from a routing perspective=
.=0A=
=0A=
I would indeed RECOMMEND that different ports on the same router be, in the=
 normal case, connected to different subnets, and I would RECOMMEND that a =
small simple network be kept as small and simple as meets the design requir=
ements of its operator - which in a home network, is the occupants of the h=
ome. If the person is trying to (as I do) connect things that don't move, l=
ike TVs, using wired media and connect things that do move using wireless, =
or to route high volume data by different paths than occasional data flows,=
 there exist requirements that probably don't belong in a document like thi=
s, but need to be configurable by a clueful operator.=0A=
=0A=
I'd stick to RECOMMEND, and make it clear that the recommendation targets t=
he general case.=0A=
________________________________________=0A=
From: homenet [homenet-bounces@ietf.org] on behalf of Joel M. Halpern [jmh@=
joelhalpern.com]=0A=
Sent: Thursday, February 19, 2015 11:36 AM=0A=
To: Ted Lemon; Mikael Abrahamsson=0A=
Cc: homenet@ietf.org; Juliusz Chroboczek=0A=
Subject: Re: [homenet] Routing protocol comparison document=0A=
=0A=
I would note that RFC 7368 says that "simple Layer 3 topologies=0A=
involving as few subnets as possible are preferred in home networks".  I=0A=
presume this is reflective of WG agreement.=0A=
While it does go on to note that multiple subnets are sometimes needed,=0A=
mandating that each physical port on the access router be a distinct=0A=
subnet (much less extending such a mandate further in the home) seems to=0A=
violate this agreement.=0A=
=0A=
Yours,=0A=
Joel M. Halpern=0A=
=0A=
On 2/19/15 1:11 PM, Ted Lemon wrote:=0A=
> On Feb 19, 2015, at 12:33 PM, Mikael Abrahamsson <swmike@swm.pp.se> wrote=
:=0A=
>> Sure, ISIS could be made smarter when it comes to this, but it all comes=
 down to what the requirements are. Right now when we started to evaluate r=
outing protocols, people started pitching USP for their perticular favorite=
, and we found out we weren't even on the same page when it comes to requir=
ements, and even what a homenet looks like.=0A=
>=0A=
> I think it is you who are not on the same page, not the working group.   =
The working group recently published a document describing our goals, RFC 7=
368.   Many of the points you have raised as supposed points of disagreemen=
t are addressed in the document, although I will admit that it is not alway=
s obvious that they have been addressed.   The case of routing over Wifi wa=
s discussed at length; the text referring to it in the document is here:=0A=
>=0A=
>     Due to the use of a variety of diverse underlying link technologies,=
=0A=
>     path selection in a homenet may benefit from being more refined than=
=0A=
>     minimising hop count.=0A=
>=0A=
> Regarding your criticism about people pitching their favorite routing pro=
tocols, you seem to be doing precisely that, so the criticism seems a bit u=
nfair.   The responses you have been hearing seem like legitimate attempts =
to address points you have raised on a technical level, not mere advocacy, =
and it is unfortunate that you would suggest otherwise: I haven't actually =
seen you raise any technical points in favor of IS-IS, which you seem to be=
 advocating.=0A=
>=0A=
> _______________________________________________=0A=
> homenet mailing list=0A=
> homenet@ietf.org=0A=
> https://www.ietf.org/mailman/listinfo/homenet=0A=
>=0A=
=0A=
_______________________________________________=0A=
homenet mailing list=0A=
homenet@ietf.org=0A=
https://www.ietf.org/mailman/listinfo/homenet=


From nobody Thu Feb 19 12:14:15 2015
Return-Path: <dave.taht@gmail.com>
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 CBE321A882F for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 12:14:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 50u5tv1PzxA9 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 12:14:10 -0800 (PST)
Received: from mail-ob0-x22c.google.com (mail-ob0-x22c.google.com [IPv6:2607:f8b0:4003:c01::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 767141A00AE for <homenet@ietf.org>; Thu, 19 Feb 2015 12:14:10 -0800 (PST)
Received: by mail-ob0-f172.google.com with SMTP id nt9so19010534obb.3 for <homenet@ietf.org>; Thu, 19 Feb 2015 12:14:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=1qxiKMUbcU/yv2gxcBUsk5Jd53Cnse62EWOUR4PSKPY=; b=uzwGLkG5OBqVxynBtMpR5ReVtwTweHut9iPZdurFGAm5KkK5HsnxWtob4hueDUswug iFWPB48Zufnb75psX/sW3qEpv6wSG8gJCv7xrZCfkIUe1krei4FIBQ+AfEUlKSQZ2AcK BzJYX8LMDNsvK4xb+PMG6kc5reGanNeIrpXnscSPqAqEzTw7dMc0EZQgMV1LEzIxEh5l gDbcZI7K8y0nxPOM0fpS706V1dXju2UWvN5NF31RLdvT/CnnZl5glbYl2W/dcKJuEXJB xBg56KPWvjNXTl9G8cOd2CI7rxBqr7L2+dfahDa/3UacLOvLnSNM3oQNQYhknmDXqUNx XvEg==
MIME-Version: 1.0
X-Received: by 10.60.16.230 with SMTP id j6mr4182017oed.8.1424376849763; Thu, 19 Feb 2015 12:14:09 -0800 (PST)
Received: by 10.202.51.66 with HTTP; Thu, 19 Feb 2015 12:14:09 -0800 (PST)
In-Reply-To: <08996755-7862-4CB7-B5B7-9BFBFA7594F6@fugue.com>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <F2818678-A728-4300-896C-E220A0DF0D1A@employees.org> <ADBDED5C-5279-4A04-B7C8-FCCB453A8C4F@gmail.com> <B2BEAF63-D219-41A0-8209-1EEFE9667440@fugue.com> <812BE11C-CB57-4594-81CD-A54AC8A16EFF@gmail.com> <23AD334B-6349-4978-B90C-248A22CD5FE7@fugue.com> <alpine.DEB.2.02.1502192010040.4007@uplift.swm.pp.se> <08996755-7862-4CB7-B5B7-9BFBFA7594F6@fugue.com>
Date: Thu, 19 Feb 2015 12:14:09 -0800
Message-ID: <CAA93jw55iPYzJTG=yy9A7cvOQeWbCrc-QQPJRVcDjT9Z8qaVQQ@mail.gmail.com>
From: Dave Taht <dave.taht@gmail.com>
To: Ted Lemon <mellon@fugue.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/cP7YS-gQ2QUK9-lde0hEvycbCL8>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 20:14:14 -0000

On Thu, Feb 19, 2015 at 11:18 AM, Ted Lemon <mellon@fugue.com> wrote:
> On Feb 19, 2015, at 2:11 PM, Mikael Abrahamsson <swmike@swm.pp.se> wrote:
>> I'd imagine it's easier to do AQM on routed ports instead of switched po=
rts as well, that's where I can imagine CeroWRT choosing this approach.
>
> I don't think it is easier to do AQM on routed ports.   If you do the eas=
y version of AQM for switched ports, that's easy; if you do per-port AQM I =
think it's equally hard in both cases.

In either case AQM and FQ has to be per port in the switch hardware
itself. I have been patiently awaiting for that sort of hardware to
arrive.

On most consumer routers the cpu forwarding path isnt capable of gbit
rates in the first place.

If you are doing software bridging (say between wired and wireless),
you apply fq_codel to the underlying interfaces, not the bridge, and
you are golden, except for dealing with multicast...

>The plumbing for the L2 solution would look different than for the L3 solu=
tion, and that might make it trickier, though.
>
> CeroWRT did this, as far as I understand it, because Dave wanted to shake=
 out cross-subnet issues, not because he felt it was technically preferable=
 in the long run, but perhaps I am misrepresenting his position on the topi=
c.

You are correct, I primarily chose routing between tons of interfaces
precisely to expose what cross-subnet issues existed in the real
world, and to make it be soooo painful as to inspire those writing
code that overused multicast to find unicast solutions!

The core things that break are things we long ago identified - mdns
and local service discovery, notably. (I have generally found that
every android app lets me plug in an ip address for a given service,
so for me it hasnt been a huge problem - except that not having a
dynamic ipv6 to name mapping makes dynamic ipv6 unusable in such
cases)

The net result is a lot of cero people said to hell with that and went
back to bridging everything, instead of working harder on mdns-proxy,
cidr, etc.

This microcosm of induced routing pain was also intended to show how
multicast didnt scale at all into larger wifi networks in the the
small business, or educational campus, that are bridged to wifi, here
the problems induced by multicast are so crippling as to leading to
the vast establishment of things like AP isolation, which disconnects
everyone from everyone else, on the same AP, which to me, is a
terrible solution.

I do note that not bridging ethernet and wifi together in cero has led
to making wifi quite a bit more pleasant and less jittery on apps like
webrtc, at least for me, and there is work in play on improving wifi=C2=B4s
aggregation handling and multicast queue management coming up soon.

>> It's good that we're having this discussions since I seem to not be the =
only one thinking that there should be one port per subnet.

I do like occasionally having more than one vlan, but in the general case,
routing is far more expensive than switching.

The no-nat case here shows the impact of a current 44 entry routing
table on downloads, in the present linux 3.18 fib lookup system.

http://snapon.lab.bufferbloat.net/~d/openwrt-3.18.7/openwrt-wndr3800-3.18.7=
.svg

and also shows the performance difference between ipv6 and ipv4 on
this hardware.

There has been some GREAT work on improving linux=C2=B4s fib lookup system
of late, but hardware bridging will always outperform software
bridging which will always outperform routing, IMHO.

Anyway I cant imagine a homeowner wanting more than 2-3 vlans at most,
and most, just one. There is no problem scaling an ethernet broadcast
domain to 4096 devices. Using up 16 ports on 16 different /64 subnets
is kind of crazy, especially since at least one provider (comcast) is
only supplying a /60 in the first place.

wifi on the other hand, barely scales to 30 active stations.


> Indeed, there are two of you!
>
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet



--=20
Dave T=C3=A4ht

thttp://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks


From nobody Thu Feb 19 12:16:23 2015
Return-Path: <hrogge@gmail.com>
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 3EB011A00AE for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 12:16:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 i72ujgBfrl1g for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 12:16:10 -0800 (PST)
Received: from mail-wi0-x22c.google.com (mail-wi0-x22c.google.com [IPv6:2a00:1450:400c:c05::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2AF1C1A88E3 for <homenet@ietf.org>; Thu, 19 Feb 2015 12:16:09 -0800 (PST)
Received: by mail-wi0-f172.google.com with SMTP id l15so50641649wiw.5 for <homenet@ietf.org>; Thu, 19 Feb 2015 12:16:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=jn47u/JAVG90gwqPB8u5s7CI7ieiY05AVya2Cd5GM+0=; b=npgDt1tZf7hKsftrVViRfRowxgN2KKdD0J9JHIwk6ZuY6UCqDjN1rN3xdZJ7yTbguG KVTWDactxE0LnLXLWCgUVxbVJe0KM4MD9OZFzpMSCVFPmAw4FwZdAzOqePP7kjVbBKE/ MyM+tLDtqhKqItUxfeA6XPCpBcND8mzxrabgGqaT/eOrXznxfL1uZYh9qCYJdBhwCGfn HTpoJxidSRzu8grAbDZWFefNiIR0Fp5eg3a4jfydwz70cA3avYgkOoiMel09d8Kwh9fG UocTF/7jhOEqbolFXvxE0lYQEWIlLl0gq91X1oDjbN6nJe/DG1dHDut7u8voxBvAP72W jW4g==
X-Received: by 10.194.78.231 with SMTP id e7mr12143998wjx.33.1424376966549; Thu, 19 Feb 2015 12:16:06 -0800 (PST)
MIME-Version: 1.0
Received: by 10.27.77.212 with HTTP; Thu, 19 Feb 2015 12:15:46 -0800 (PST)
In-Reply-To: <87fva1fzwp.wl-jch@pps.univ-paris-diderot.fr>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <A5767F83-3D0C-40E5-A73B-912E3C160A42@fugue.com> <alpine.DEB.2.02.1502191235240.4007@uplift.swm.pp.se> <87zj89gaqm.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191804050.4007@uplift.swm.pp.se> <D10B8924.6BD5%John_Leddy@cable.comcast.com> <87h9uhg529.wl-jch@pps.univ-paris-diderot.fr> <87fva1fzwp.wl-jch@pps.univ-paris-diderot.fr>
From: Henning Rogge <hrogge@gmail.com>
Date: Thu, 19 Feb 2015 21:15:46 +0100
Message-ID: <CAGnRvuqXH=NBgtJB7BGD9ohJjpmjF4QH-rC18-xgTEK4HiAVSg@mail.gmail.com>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/YT0899ZHMzUsuGy23v7H4xtj30A>
Cc: "Leddy, John" <John_Leddy@cable.comcast.com>, "homenet@ietf.org Group" <homenet@ietf.org>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] More about marginal links [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 20:16:17 -0000

On Thu, Feb 19, 2015 at 8:45 PM, Juliusz Chroboczek
<jch@pps.univ-paris-diderot.fr> wrote:
>> A marginal link is simply one that has a measurable amount of packet loss.
>
> Ok, re-reading this exchange, it looks like I may have wrongly assumed
> that people are aware of background.  I'll need to put that into the
> routing comparison document, this is as good a place as any to draft my
> text.
>
> Carrier and enterprise routing protocols are optimised for wired networks,
> where a link is either down (drops all packets) or up (drops one packet in
> 10^10).
>
> Home networks usually include link technologies that have an intermediate
> "marginal" state: a link that drops a non-negligible fraction of packets.
> With 802.11, in particular, marginal links have fairly unpleasant performance
> characteristics.  For example, if the BER is 10^-4,
>
>   - multicast packets are dropped at roughly the nominal rate (10% for 120
>     byte packets, 90% for 1500 byte packets);
>   - unicast packets are dropped at a much lower rate, but the efficiency
>     suffers (0.9 for 120 byte packets, 0.1 for 1500 byte packets).
>   - unicast packets have a high probability of being duplicated (no
>     figures given, I'm too lazy to look up the size of an ACK frame).
>
> This is of course a very naive analysis -- in practice, errors tend to
> come in bursts, and furthermore 802.11a/g/n implements some very complex
> lower-layer magic.  Don't believe any results from computation or
> simulation, with radio, only actual testing in real-world networks is
> trustworthy.

There is also the really bad case of wifi links without packet loss
which are stable at 6 Mbit/s... stable but incredible slow.

If you have a combination of two 450 Mbit/s links you can use instead,
you want to do it...

Henning Rogge


From nobody Thu Feb 19 12:19:21 2015
Return-Path: <dave.taht@gmail.com>
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 CBAA01A8924 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 12:19:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 gNLHsVcMO8Cq for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 12:19:12 -0800 (PST)
Received: from mail-ob0-x22f.google.com (mail-ob0-x22f.google.com [IPv6:2607:f8b0:4003:c01::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 311E91A0AFE for <homenet@ietf.org>; Thu, 19 Feb 2015 12:19:11 -0800 (PST)
Received: by mail-ob0-f175.google.com with SMTP id va2so19014300obc.6 for <homenet@ietf.org>; Thu, 19 Feb 2015 12:19:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=fs+9Oo3hrQukVgirGjk+L4kI84wmFcF0C/KLhdlv3QA=; b=D604vH1ANREKPfI1UjacDgg5EC6UwMvV1eAPh+QNF97GLnPAbTcjAz0gU6YsvkMIVn nISBQuJv0XSAdcmreOvn6Z8I/6dEuIpunUHXjkllG3Bf8hy4V0cHkaTRaxKTSzKT/ALU 0M95EEd+Au84wbFrHgEYcdEs8qJV/fHIaB0eglcGw5LvbVDrpl3Hwif7Ac6y/knRn4/d n67KABzhluADd41w98yrVklD9J0/ZrLa0qsRZbZN+cceTpVUOETlYsEYj9/SJaK09AwG mPb5sqt+OgjsaMYlQBX2pLJgZIERsaPmdhi3zQGH1KqRcXekWPZOynqLcNoFKL2GuqRI DW4g==
MIME-Version: 1.0
X-Received: by 10.182.230.165 with SMTP id sz5mr4180854obc.29.1424377150312; Thu, 19 Feb 2015 12:19:10 -0800 (PST)
Received: by 10.202.51.66 with HTTP; Thu, 19 Feb 2015 12:19:10 -0800 (PST)
In-Reply-To: <CAA93jw55iPYzJTG=yy9A7cvOQeWbCrc-QQPJRVcDjT9Z8qaVQQ@mail.gmail.com>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <F2818678-A728-4300-896C-E220A0DF0D1A@employees.org> <ADBDED5C-5279-4A04-B7C8-FCCB453A8C4F@gmail.com> <B2BEAF63-D219-41A0-8209-1EEFE9667440@fugue.com> <812BE11C-CB57-4594-81CD-A54AC8A16EFF@gmail.com> <23AD334B-6349-4978-B90C-248A22CD5FE7@fugue.com> <alpine.DEB.2.02.1502192010040.4007@uplift.swm.pp.se> <08996755-7862-4CB7-B5B7-9BFBFA7594F6@fugue.com> <CAA93jw55iPYzJTG=yy9A7cvOQeWbCrc-QQPJRVcDjT9Z8qaVQQ@mail.gmail.com>
Date: Thu, 19 Feb 2015 12:19:10 -0800
Message-ID: <CAA93jw4LfKULOa33XSZEBLgoBxjtGP_hEPZpTo06c56xddeZ3g@mail.gmail.com>
From: Dave Taht <dave.taht@gmail.com>
To: Ted Lemon <mellon@fugue.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/r6WAv-STcfl1And5-aiiDrNVS1s>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 20:19:18 -0000

On Thu, Feb 19, 2015 at 12:14 PM, Dave Taht <dave.taht@gmail.com> wrote:
> On Thu, Feb 19, 2015 at 11:18 AM, Ted Lemon <mellon@fugue.com> wrote:
>> On Feb 19, 2015, at 2:11 PM, Mikael Abrahamsson <swmike@swm.pp.se> wrote=
:
>>> I'd imagine it's easier to do AQM on routed ports instead of switched p=
orts as well, that's where I can imagine CeroWRT choosing this approach.
>>
>> I don't think it is easier to do AQM on routed ports.   If you do the ea=
sy version of AQM for switched ports, that's easy; if you do per-port AQM I=
 think it's equally hard in both cases.
>
> In either case AQM and FQ has to be per port in the switch hardware
> itself. I have been patiently awaiting for that sort of hardware to
> arrive.
>
> On most consumer routers the cpu forwarding path isnt capable of gbit
> rates in the first place.
>
> If you are doing software bridging (say between wired and wireless),
> you apply fq_codel to the underlying interfaces, not the bridge, and
> you are golden, except for dealing with multicast...
>
>>The plumbing for the L2 solution would look different than for the L3 sol=
ution, and that might make it trickier, though.
>>
>> CeroWRT did this, as far as I understand it, because Dave wanted to shak=
e out cross-subnet issues, not because he felt it was technically preferabl=
e in the long run, but perhaps I am misrepresenting his position on the top=
ic.
>
> You are correct, I primarily chose routing between tons of interfaces
> precisely to expose what cross-subnet issues existed in the real
> world, and to make it be soooo painful as to inspire those writing
> code that overused multicast to find unicast solutions!
>
> The core things that break are things we long ago identified - mdns
> and local service discovery, notably.

Also firewalling became a log(nports) problem without the special solutions
in cerowrt. That became AMAZINGLY slow when we got past 4 interfaces.
It still is quite slow even with the pattern match we use there.

>(I have generally found that
> every android app lets me plug in an ip address for a given service,
> so for me it hasnt been a huge problem - except that not having a
> dynamic ipv6 to name mapping makes dynamic ipv6 unusable in such
> cases)
>
> The net result is a lot of cero people said to hell with that and went
> back to bridging everything, instead of working harder on mdns-proxy,
> cidr, etc.
>
> This microcosm of induced routing pain was also intended to show how
> multicast didnt scale at all into larger wifi networks in the the
> small business, or educational campus, that are bridged to wifi, here
> the problems induced by multicast are so crippling as to leading to
> the vast establishment of things like AP isolation, which disconnects
> everyone from everyone else, on the same AP, which to me, is a
> terrible solution.
>
> I do note that not bridging ethernet and wifi together in cero has led
> to making wifi quite a bit more pleasant and less jittery on apps like
> webrtc, at least for me, and there is work in play on improving wifi=C2=
=B4s
> aggregation handling and multicast queue management coming up soon.
>
>>> It's good that we're having this discussions since I seem to not be the=
 only one thinking that there should be one port per subnet.
>
> I do like occasionally having more than one vlan, but in the general case=
,
> routing is far more expensive than switching.
>
> The no-nat case here shows the impact of a current 44 entry routing
> table on downloads, in the present linux 3.18 fib lookup system.
>
> http://snapon.lab.bufferbloat.net/~d/openwrt-3.18.7/openwrt-wndr3800-3.18=
.7.svg
>
> and also shows the performance difference between ipv6 and ipv4 on
> this hardware.
>
> There has been some GREAT work on improving linux=C2=B4s fib lookup syste=
m
> of late, but hardware bridging will always outperform software
> bridging which will always outperform routing, IMHO.
>
> Anyway I cant imagine a homeowner wanting more than 2-3 vlans at most,
> and most, just one. There is no problem scaling an ethernet broadcast
> domain to 4096 devices. Using up 16 ports on 16 different /64 subnets
> is kind of crazy, especially since at least one provider (comcast) is
> only supplying a /60 in the first place.
>
> wifi on the other hand, barely scales to 30 active stations.
>
>
>> Indeed, there are two of you!
>>
>> _______________________________________________
>> homenet mailing list
>> homenet@ietf.org
>> https://www.ietf.org/mailman/listinfo/homenet
>
>
>
> --
> Dave T=C3=A4ht
>
> thttp://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks



--=20
Dave T=C3=A4ht

thttp://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks


From nobody Thu Feb 19 12:25:45 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 07A661A88F2 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 12:25:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35] autolearn=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 tkCCG399g4KL for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 12:25:43 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 77B611A014C for <homenet@ietf.org>; Thu, 19 Feb 2015 12:25:43 -0800 (PST)
Received: from potemkin.univ-paris7.fr (potemkin.univ-paris7.fr [IPv6:2001:660:3301:8000::1:1]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t1JKPgNt002215 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 19 Feb 2015 21:25:42 +0100
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by potemkin.univ-paris7.fr (8.14.4/8.14.4/relay2/56228) with ESMTP id t1JKPfps026997; Thu, 19 Feb 2015 21:25:41 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id E4496119AD; Thu, 19 Feb 2015 21:25:41 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id S_JLeB2oAmZl; Thu, 19 Feb 2015 21:25:40 +0100 (CET)
Received: from pirx.pps.jussieu.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 7E4CD2A10D2; Thu, 19 Feb 2015 21:25:39 +0100 (CET)
Date: Thu, 19 Feb 2015 21:25:40 +0100
Message-ID: <87egplfy2j.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Mikael Abrahamsson <swmike@swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1502191924250.4007@uplift.swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <54E58238.9030809@mtcc.com> <874mqigcct.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191622510.4007@uplift.swm.pp.se> <87vbixg9fe.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191806381.4007@uplift.swm.pp.se> <87lhjtg6jc.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191826230.4007@uplift.swm.pp.se> <2FE73365-ECD7-49C3-8476-934CD1032542@fugue.com> <alpine.DEB.2.02.1502191924250.4007@uplift.swm.pp.se>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]); Thu, 19 Feb 2015 21:25:42 +0100 (CET)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Thu, 19 Feb 2015 21:25:41 +0100 (CET)
X-Miltered: at korolev with ID 54E646C6.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 54E646C5.003 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54E646C6.000 from potemkin.univ-paris7.fr/potemkin.univ-paris7.fr/null/potemkin.univ-paris7.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Enveloppe: 54E646C5.003 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54E646C6.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 54E646C5.003 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/S0Vrw40nWH8T_HNa6cIJCNBxr50>
Cc: homenet@ietf.org
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 20:25:45 -0000

> If people want to choose babel because it works well facing adverse radio
> conditions in a mesh-networking environment (that I know nothing about),

I think this is misrepresenting the argument somewhat.

We want a routing protocol that works well in an unadministered network
that consists of a mixture of wired and wireless links.  In a previous
mail, I presented a topology that I think is realistic in a Homenet
deployment:

   Internet --- A --- B....C          --- is Ethernet
                 .        .           ... is WiFi
                  ........

Current implementations of Babel are known to work well in such topologies.

As far as I am aware, current implementations of IS-IS are not.  Getting
IS-IS to work well on such topologies is not completely trivial.

-- Juliusz


From nobody Thu Feb 19 12:38:43 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 32B841A0177 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 12:38:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35] autolearn=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 jwVYHQYkAlxu for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 12:38:41 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 011041A0095 for <homenet@ietf.org>; Thu, 19 Feb 2015 12:38:40 -0800 (PST)
Received: from potemkin.univ-paris7.fr (potemkin.univ-paris7.fr [IPv6:2001:660:3301:8000::1:1]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t1JKcddH009469 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 19 Feb 2015 21:38:39 +0100
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by potemkin.univ-paris7.fr (8.14.4/8.14.4/relay2/56228) with ESMTP id t1JKcdYo001569; Thu, 19 Feb 2015 21:38:39 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 6C3B1119AF; Thu, 19 Feb 2015 21:38:39 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id AiXjsklx_UyE; Thu, 19 Feb 2015 21:38:37 +0100 (CET)
Received: from pirx.pps.jussieu.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id D91462A10D2; Thu, 19 Feb 2015 21:38:37 +0100 (CET)
Date: Thu, 19 Feb 2015 21:38:38 +0100
Message-ID: <87d255fxgx.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Henning Rogge <hrogge@gmail.com>
In-Reply-To: <CAGnRvuqXH=NBgtJB7BGD9ohJjpmjF4QH-rC18-xgTEK4HiAVSg@mail.gmail.com>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <A5767F83-3D0C-40E5-A73B-912E3C160A42@fugue.com> <alpine.DEB.2.02.1502191235240.4007@uplift.swm.pp.se> <87zj89gaqm.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191804050.4007@uplift.swm.pp.se> <D10B8924.6BD5%John_Leddy@cable.comcast.com> <87h9uhg529.wl-jch@pps.univ-paris-diderot.fr> <87fva1fzwp.wl-jch@pps.univ-paris-diderot.fr> <CAGnRvuqXH=NBgtJB7BGD9ohJjpmjF4QH-rC18-xgTEK4HiAVSg@mail.gmail.com>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]); Thu, 19 Feb 2015 21:38:39 +0100 (CET)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Thu, 19 Feb 2015 21:38:39 +0100 (CET)
X-Miltered: at korolev with ID 54E649CF.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 54E649CF.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54E649CF.000 from potemkin.univ-paris7.fr/potemkin.univ-paris7.fr/null/potemkin.univ-paris7.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Enveloppe: 54E649CF.001 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54E649CF.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 54E649CF.001 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/dkLsqsl8joRiPLcGjgRi4Znmz88>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] More about marginal links
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 20:38:42 -0000

> There is also the really bad case of wifi links without packet loss
> which are stable at 6 Mbit/s... stable but incredible slow.
>
> If you have a combination of two 450 Mbit/s links you can use instead,
> you want to do it...

Absolutely.  Just to clarify -- Henning is referring to the modulation
rate that is dynamically chosen by the MAC, and may vary over time and be
different for two neighbours on the same interface.

See my previous note about dropping ETX in favour of hooking (non-portably)
into the MAC layer in some future version of Babel.  I believe that
Henning is working on something similar for OLSRv2
(draft-ietf-manet-olsrv2-dat-metric).

-- Juliusz


From nobody Thu Feb 19 13:01:55 2015
Return-Path: <dave.taht@gmail.com>
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 9C15A1A01EC for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 13:01:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 GBXR7nTA4X5p for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 13:01:50 -0800 (PST)
Received: from mail-ob0-x231.google.com (mail-ob0-x231.google.com [IPv6:2607:f8b0:4003:c01::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 100AD1A01D6 for <homenet@ietf.org>; Thu, 19 Feb 2015 13:01:44 -0800 (PST)
Received: by mail-ob0-f177.google.com with SMTP id wp18so18448872obc.8 for <homenet@ietf.org>; Thu, 19 Feb 2015 13:01:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=fT+FKfO0agvfbQqqPEVjJWA84ItLDS93AmSceBlor6c=; b=IVeKgT6hhnHrHtgNIKHoNU6Zk0QgZB8Qm/AIC7kL4Sz3ZdhrtVZgxEBLVtsr6rEMkB kVI2eVmK/UF833KG2BfpW25GoV/SrzT+4tA+dZFSvrMFPmiP27n+482serjwzAKDjzt4 rxXWlKL8Hij6XnwS7xvIe+Ar8m/yx6ZszjulocR6x7k6aaxBjf7BHCh4tYs3Y+1YjpmW 8b/InHSjtSq/vRDQI5VQdy2oxr+rSL1FFI0SZclK3n4xKkO0XTNZwGYW4g5OOJRZpUKY yBwQ2dFahMcA+mYdmR0iNsVMBAggSvB1DlZqNkLbN0+9GJ440oJLonQRZtb8qorMrvmV iPxg==
MIME-Version: 1.0
X-Received: by 10.182.40.135 with SMTP id x7mr4227617obk.45.1424379703274; Thu, 19 Feb 2015 13:01:43 -0800 (PST)
Received: by 10.202.51.66 with HTTP; Thu, 19 Feb 2015 13:01:43 -0800 (PST)
In-Reply-To: <87fva1fzwp.wl-jch@pps.univ-paris-diderot.fr>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <A5767F83-3D0C-40E5-A73B-912E3C160A42@fugue.com> <alpine.DEB.2.02.1502191235240.4007@uplift.swm.pp.se> <87zj89gaqm.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191804050.4007@uplift.swm.pp.se> <D10B8924.6BD5%John_Leddy@cable.comcast.com> <87h9uhg529.wl-jch@pps.univ-paris-diderot.fr> <87fva1fzwp.wl-jch@pps.univ-paris-diderot.fr>
Date: Thu, 19 Feb 2015 13:01:43 -0800
Message-ID: <CAA93jw57sNMPsKkL-W2m3s20DKsFZWNeGZSOgnmRTj3yz+Rgmg@mail.gmail.com>
From: Dave Taht <dave.taht@gmail.com>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/E2-2Vfuau-Xi-AzCwNP3f5myCMk>
Cc: "Leddy, John" <John_Leddy@cable.comcast.com>, "homenet@ietf.org Group" <homenet@ietf.org>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] More about marginal links [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 21:01:53 -0000

On Thu, Feb 19, 2015 at 11:45 AM, Juliusz Chroboczek
<jch@pps.univ-paris-diderot.fr> wrote:
>> A marginal link is simply one that has a measurable amount of packet los=
s.
>
> Ok, re-reading this exchange, it looks like I may have wrongly assumed
> that people are aware of background.  I'll need to put that into the
> routing comparison document, this is as good a place as any to draft my
> text.
>
> Carrier and enterprise routing protocols are optimised for wired networks=
,
> where a link is either down (drops all packets) or up (drops one packet i=
n
> 10^10).

Um, er, ah, an ideal low latency drop or mark rate is about .01-.02%
of big packets on 100mbit links, I dont remember what it is for gigE.
It is much higher at 10mbit. I should just go out and draw the nearly
linear relationship between drop rate and bandwidth for fixed latency
from the data I have...

> Home networks usually include link technologies that have an intermediate
> "marginal" state: a link that drops a non-negligible fraction of packets.

I have over the past year become a reluctantly enthusiastic user of
homeplug powerline technologies. For stuff rated at 600Mbit () I
typically get throughput in the range of 12-140mbits in a small apt
and latencies in the 30-140ms range under load. They degrade
enormously with more than 2 in use and dont work worth a damn in
larger houses... but are still generally faster and less jittery than
present day wifi, when you have an electrical system that they work
on.

These sort of devices would be ideal to add aqm/fq to but public
firmware is non-existent, as near as I can tell.

And, as layer 2 bridging devices, they supply no indications to layer
3 routing protocols that they are weirder than ethernet.

I do like the idea of using RTT based metrics as an abstraction for
determining link quality, but it would be rather nice to also have a
way to get their actual bandwidth and actual load statistics somehow,
for smarter usage.

> With 802.11, in particular, marginal links have fairly unpleasant perform=
ance
> characteristics.  For example, if the BER is 10^-4,
>
>   - multicast packets are dropped at roughly the nominal rate (10% for 12=
0
>     byte packets, 90% for 1500 byte packets);
>   - unicast packets are dropped at a much lower rate, but the efficiency
>     suffers (0.9 for 120 byte packets, 0.1 for 1500 byte packets).
>   - unicast packets have a high probability of being duplicated (no
>     figures given, I'm too lazy to look up the size of an ACK frame).
>
> This is of course a very naive analysis -- in practice, errors tend to
> come in bursts, and furthermore 802.11a/g/n implements some very complex
> lower-layer magic.  Don't believe any results from computation or
> simulation, with radio, only actual testing in real-world networks is
> trustworthy.
>
> This has two consequences for routing protocols:
>
>   (1) the routing protocol must be able to prefer solid links to marginal
>       ones when there is enough redundancy;
>   (2) control data may fail to be propagated in a timely manner,
>       especially if it is sent over multicast.
>
>
> 1. Prefer solid links
>
> This is pretty obvious.  If you can choose between an Ethernet link and

Well, ethernet runs at different speeds and there is no abstraction
for that in babel...

> a wireless link with heavy packet loss, choose the Ethernet.  But there
> are more subtle cases that are extremely common in practice:
>
>    Internet --- A --- B....C          --- is Ethernet
>                  .        .           ... is WiFi
>                   ........
>
> A is your CPE, B is the router in your living room, connected by Ethernet
> to the CPE, and C is the wireless router in the guest room.  Yeah, it's
> a large house.

> Suppose now that the wireless link B..C is rock solid, but the longer A..=
C
> link is marginal.  Murphy's law dictates that the link A..C will have hug=
e
> packet loss, but it will be just good enough for the routing instances on
> A and C to become neighbours.  If the routing protocol performs hop-count
> routing, even if it is smart enough to prefer wired to wireless, it will
> prefer the highly marginal route A..C to the rock solid route A-B..C.
>
> Note that this is easily fixed by a competent administrator: just disable
> the wireless interface on A.  But this is Homenet, and we're assuming
> there's no administrator.
>
> In the mesh community, the hop-count metric is known as "worst-path routi=
ng".
>
>
> 2. Control data may be delayed
>
> Since multicast has such massive packet drops, the routing data may be
> dropped or delayed.  Using a reliable sub-protocol for propagating
> critical data, as is done by OSPF, IS-IS and EIGRP might work if the
> reliable protocol can cope with the weirdness of the 802.11 MAC.  If it
> cannot, it might (or might not, I don't know) suffer from routing
> pathologies, such as routing loops in OSPF and IS-IS, inconsistent DR/DER
> election, and SIA in EIGRP.
>
> Of course, people have managed to get link-state protocols to work on
> wireless networks, even on highly marginal mesh networks, but they had to
> design new mechanisms.  OLSR, for example, doesn't use reliable flooding
> and DR election, but instead uses unreliable flooding and MPR election,
> together with a mechanism that drops marginal links.  I refer you to
> RFCs 3626 and 5449.
>
> Babel uses different mechanisms.  Babel uses a feasibility condition
> similar to that of EIGRP, which means that it avoids loops even when
> control data is delayed.  Unlike EIGRP, however, it doesn't rely on
> a reliable subprotocol, and it doesn't have an active phase.  End-to-end
> synchronisation is achieved in a softer manner, and a single router that
> fails to propagate requests doesn't prevent reconvergence if there are
> alternate paths available -- look Ma, no SIA, even with massive packet
> loss.  (This is not meant as a critique of EIGRP -- I rather like EIGRP,
> and I'm pretty sure it could be adapted to home networks if somebody spen=
t
> a couple of years of their life doing that.)
>
>
> I'd like to finish this slightly lengthy message by stating that the
> current implementation of Babel does not work well in networks where all
> links are highly marginal; in other words, Babel really wants a solid
> backbone to be available.  In particular, Babel tends to aggregate contro=
l
> data into large packets, which have a higher probability of being dropped=
,
> and tends to drop links that have more than 90% pre-ARQ drop rate for
> full-size frames.  There exist specialised, highly tuned protocols that
> are able to deal with topologies that rely on such very marginal links,
> notably bmx6, BATMAN-adv, and the highly tuned version of OLSR-ETX used b=
y
> the Berlin and Vienna meshes.
>
> -- Juliusz
>
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet



--=20
Dave T=C3=A4ht

thttp://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks


From nobody Thu Feb 19 13:19:44 2015
Return-Path: <teco@inf-net.nl>
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 7C21F1A01F9 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 13:19:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 M4Mhgu9f2kBp for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 13:19:40 -0800 (PST)
Received: from mail-we0-f177.google.com (mail-we0-f177.google.com [74.125.82.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 80C651A0181 for <homenet@ietf.org>; Thu, 19 Feb 2015 13:19:39 -0800 (PST)
Received: by wesx3 with SMTP id x3so2196336wes.7 for <homenet@ietf.org>; Thu, 19 Feb 2015 13:19:38 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=Af++CviOWdVVj0OG7IuFxYod8iUMo4dBnY/N4aIEUHw=; b=Uafsfmy5BvvipnSKwDh9zWR3sgGjDPnrpfUbIQv0T9hqFU3ydSEutx0H0eYOhPXRJh BfcF/0pfi4HiN4rgQr/fS9e55tHabFdo8zj3+9iBGY32llDybdrlHZo/H3ACMIUo3q9+ tdebml0x0XNPggjL9INFo26hv31nSDp6hc/couipuEm++bMkZojuPDFovx+QnyYJ44V3 W0bfTqeWxqXqwDeIGOvY9COXhmnPRZWS/Y0kv0pb92WoekmPxK8MlUEKxE8rc+/IGT+k /bKbissFH2AUiTjPDuaItf4rZPCoEYU+uiA+xmBVNMiPBwSjxKQawmLLKrOvMs/20fPs iFfA==
X-Gm-Message-State: ALoCoQnyrL9e0Hst9Hokifh1m2pAc6ZZbD55sVUFbUwWxMV+A1ToARd1C1Nu3C5jTq5tmP8bQn8w
X-Received: by 10.194.143.109 with SMTP id sd13mr13328912wjb.70.1424380778461;  Thu, 19 Feb 2015 13:19:38 -0800 (PST)
Received: from [192.168.178.10] (524A158D.cm-4-3a.dynamic.ziggo.nl. [82.74.21.141]) by mx.google.com with ESMTPSA id vh8sm39092709wjc.12.2015.02.19.13.19.36 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 19 Feb 2015 13:19:37 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Teco Boot <teco@inf-net.nl>
In-Reply-To: <F2818678-A728-4300-896C-E220A0DF0D1A@employees.org>
Date: Thu, 19 Feb 2015 22:19:36 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <42E2F1D5-AF35-404E-9FBE-D1C7341D88B0@inf-net.nl>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <F2818678-A728-4300-896C-E220A0DF0D1A@employees.org>
To: Ole Troan <otroan@employees.org>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/2-_KLKqAowFHx95gYW6oTC6i8a4>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Ted Lemon <mellon@fugue.com>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 21:19:43 -0000

> Op 19 feb. 2015, om 19:18 heeft Ole Troan <otroan@employees.org> het =
volgende geschreven:
>=20
>>> It means that every single device on a wired network is on a =
different subnet.  Perhaps it doesn't cause any extreme harm, but it =
certainly makes managing and debugging the network harder, and it means =
that you can't have a layer two switch anymore.  So the question I would =
ask is not "is there a problem with this," because obviously there is, =
but rather "is there a benefit to doing it this way."  I am curious to =
know what you think the benefit is.
>>=20
>> I am not mandating that each and every device is in its own broadcast =
domain, I am however advocating that we leave the model that has been =
prevalent for 10-15 years at least, ie that a home gateway has a "WAN" =
port and 4 "LAN" ports, and these 4 ports are bridged. I'm saying the =
typical device should have 4-5 "L3" ports. You're then free to connect =
one of these to your L2 switch if you so please.
>>=20
>> I would like my router-to-router links to not have a lot of hosts in =
them if I can avoid it.
>=20
> +1.
>=20
> there are very few shared media around anymore.

Still one to phase out: spectrum ;-)

I would say the opposite, I see kids that have never been connected to a =
wired link. What about wireless repeaters, which forward packets and do =
not have a network jacket? Wireless backhaul links to ISP?

Teco


> I don't think I've ever been connected to a 10base5.
> why should the IP subnet model emulate a shared medium, when the =
physical topology is a star.
>=20
> wireless with security is also a star topology, with a unidirectional =
broadcast channel.
>=20
> cheers,
> Ole
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet


From nobody Thu Feb 19 13:27:34 2015
Return-Path: <otroan@employees.org>
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 CEEEB1A024C for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 13:27:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.011
X-Spam-Level: 
X-Spam-Status: No, score=-2.011 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 ajKtvcy-oCQc for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 13:27:32 -0800 (PST)
Received: from banjo.employees.org (banjo.employees.org [IPv6:2001:1868:205::19]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EEBC81A0181 for <homenet@ietf.org>; Thu, 19 Feb 2015 13:27:31 -0800 (PST)
Received: from banjo.employees.org (localhost [127.0.0.1]) by banjo.employees.org (Postfix) with ESMTP id DF4A861B1; Thu, 19 Feb 2015 13:27:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; s=selector1; bh=A4VvFgGwaInKM8yVrJ7jI9n3ahQ=; b= lDeNhhBCSSaxO1V1CQoBsLYimKlS8QBzCYQaYyq3MsLaeU7WxKYP77JsVTTrVUYN OTP0lM+NntPlB/bBeKTubbR9QcHcEv0AFAajEsa79skliru4Euscd+cEsAfn6QVC 3XusLTKvbOsNM4efSq6XI147Nrj54FED0cauehwlYzw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; q=dns; s=selector1; b=FNP8OkT24ZVxgU2sJvr15vOYAT wtiF+Ci4LB2RKyogpu0lAWlR7Ub9izIRW1MBgvH2V7ARICfYH+hZ9KUA5onIVD31 UOPZsB2ClJcZZh4Y1x/RnzuieYMn417U0vAkwwfjhlhB7TgMpVbhv5BJApitAQ1i wLeNW2rTkJjVZjW5M=
Received: from gomlefisk.localdomain (unknown [195.159.234.46]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id 4968860FF; Thu, 19 Feb 2015 13:27:30 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by gomlefisk.localdomain (Postfix) with ESMTP id 6B6483F0BF91; Thu, 19 Feb 2015 22:27:28 +0100 (CET)
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_247A9F24-AAF8-4F06-A1FA-B9141087E732"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.5b5
From: Ole Troan <otroan@employees.org>
In-Reply-To: <42E2F1D5-AF35-404E-9FBE-D1C7341D88B0@inf-net.nl>
Date: Thu, 19 Feb 2015 22:27:28 +0100
Message-Id: <AD5FCDA8-54E5-45A2-B254-4B9D840F5F48@employees.org>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <F2818678-A728-4300-896C-E220A0DF0D1A@employees.org> <42E2F1D5-AF35-404E-9FBE-D1C7341D88B0@inf-net.nl>
To: Teco Boot <teco@inf-net.nl>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/VHJc8HUbhQELXIArM1TzSGgqxjg>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Ted Lemon <mellon@fugue.com>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 21:27:34 -0000

--Apple-Mail=_247A9F24-AAF8-4F06-A1FA-B9141087E732
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

>>=20
>>>> It means that every single device on a wired network is on a =
different subnet.  Perhaps it doesn't cause any extreme harm, but it =
certainly makes managing and debugging the network harder, and it means =
that you can't have a layer two switch anymore.  So the question I would =
ask is not "is there a problem with this," because obviously there is, =
but rather "is there a benefit to doing it this way."  I am curious to =
know what you think the benefit is.
>>>=20
>>> I am not mandating that each and every device is in its own =
broadcast domain, I am however advocating that we leave the model that =
has been prevalent for 10-15 years at least, ie that a home gateway has =
a "WAN" port and 4 "LAN" ports, and these 4 ports are bridged. I'm =
saying the typical device should have 4-5 "L3" ports. You're then free =
to connect one of these to your L2 switch if you so please.
>>>=20
>>> I would like my router-to-router links to not have a lot of hosts in =
them if I can avoid it.
>>=20
>> +1.
>>=20
>> there are very few shared media around anymore.
>=20
> Still one to phase out: spectrum ;-)
>=20
> I would say the opposite, I see kids that have never been connected to =
a wired link. What about wireless repeaters, which forward packets and =
do not have a network jacket? Wireless backhaul links to ISP?

yes, at L1 but not L2, which was what I was trying to say. citing 802.11 =
as an example.

cheers,
Ole


>=20
> Teco
>=20
>=20
>> I don't think I've ever been connected to a 10base5.
>> why should the IP subnet model emulate a shared medium, when the =
physical topology is a star.
>>=20
>> wireless with security is also a star topology, with a unidirectional =
broadcast channel.
>>=20
>> cheers,
>> Ole
>> _______________________________________________
>> homenet mailing list
>> homenet@ietf.org
>> https://www.ietf.org/mailman/listinfo/homenet


--Apple-Mail=_247A9F24-AAF8-4F06-A1FA-B9141087E732
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJU5lVAAAoJEFuJXizso86gXpoH/3q2hUYRzY/yUrthO3BAiP1Z
WxW/SWRE56xK/p9cLp8hxOKZOOWmIMrBak4bVKNZUyXWeENr5JsvyTOFqHr5PVmG
uF/+0cz9XzRbC7N1eYNkNP4roU8dFkWUuaLiVy31ZAcfN/3vthTZXdNmadnKA2/9
tBGuWx6RsF0c9bFjqrWiijuadUDBup+mj5+CL/EIVDi3JLreurT2xW0uILR2jBHk
6STJumTjLofEkkWqnPqdxz4dyOt9WuXnSnjkHTYwmjontXchc5/REeejrNRQEwPL
xU4MztlSH8RSSexiLgddng6UmWKjEelIUxEyklauKhM8kF0HEDqERs5vqHJGPU8=
=Dpo8
-----END PGP SIGNATURE-----

--Apple-Mail=_247A9F24-AAF8-4F06-A1FA-B9141087E732--


From nobody Thu Feb 19 13:39:12 2015
Return-Path: <teco@inf-net.nl>
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 7B2851A0264 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 13:39:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 2Ksr3vc6Yo1s for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 13:39:08 -0800 (PST)
Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 20EE51A0262 for <homenet@ietf.org>; Thu, 19 Feb 2015 13:39:07 -0800 (PST)
Received: by mail-wg0-f44.google.com with SMTP id k14so9840558wgh.3 for <homenet@ietf.org>; Thu, 19 Feb 2015 13:39:06 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=b92ju8gFwpBE5oPZ3v3x/kgpEhiQv63UAilZ+xLmyF8=; b=PA74TEMmN/LivGQuTB+BXoqtrw76AkyMs6v8roARzdzvNw9k4gw4aNRcaaPE+HI8lj Hz+6RQgcKuuNssh5xvSfgdvWAO1L1zQuVrSLZ9u6AhpRx8tx13pGRAYtJBKKu2AbSS7A cDnFYLG54kSmkC60aE3xH25lMTI0fOHOTqpX+OhELPlS5nUCVMW8jVpIMhoUmvW+3JFL DUlbuRrHebUAgwNdCMUtsSMpXKnRJc6YANtV6PfS9NJcmZIt1pQI99EVTEXoFgC1XAtM DKpMROiFwh6PAbcMu4SKzVB4vNdh/r3kSDCWZORlf5EIlh48+amq5eOVmliybOTxSEpD HdXw==
X-Gm-Message-State: ALoCoQkqcPbeMOHTZfxpY9CLo3cWD/MqRJ4KjLZXasVvwh61thwjeT/RCjcDEiyuQUfq8yof5suy
X-Received: by 10.180.184.230 with SMTP id ex6mr7659604wic.73.1424381946065; Thu, 19 Feb 2015 13:39:06 -0800 (PST)
Received: from [192.168.178.10] (524A158D.cm-4-3a.dynamic.ziggo.nl. [82.74.21.141]) by mx.google.com with ESMTPSA id kj8sm39144921wjc.29.2015.02.19.13.39.04 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 19 Feb 2015 13:39:05 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Teco Boot <teco@inf-net.nl>
In-Reply-To: <87egplfy2j.wl-jch@pps.univ-paris-diderot.fr>
Date: Thu, 19 Feb 2015 22:39:04 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <5E05F947-5B03-4A4D-ABC8-E3D1CB0F8BC3@inf-net.nl>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <54E58238.9030809@mtcc.com> <874mqigcct.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191622510.4007@uplift.swm.pp.se> <87vbixg9fe.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191806381.4007@uplift.swm.pp.se> <87lhjtg6jc.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191826230.4007@uplift.swm.pp.se> <2FE73365-ECD7-49C3-8476-934CD1032542@fugue.com> <alpine.DEB.2.02.1502191924250.4007@uplift.swm.pp.se> <87egplfy2j.wl-jch@pps.univ-paris-diderot.fr>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/xTGl51O7P7wBkrXZwyzqirjAuzI>
Cc: homenet@ietf.org, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 21:39:10 -0000

> Op 19 feb. 2015, om 21:25 heeft Juliusz Chroboczek =
<jch@pps.univ-paris-diderot.fr> het volgende geschreven:
>=20
>> If people want to choose babel because it works well facing adverse =
radio
>> conditions in a mesh-networking environment (that I know nothing =
about),
>=20
> I think this is misrepresenting the argument somewhat.
>=20
> We want a routing protocol that works well in an unadministered =
network
> that consists of a mixture of wired and wireless links.  In a previous
> mail, I presented a topology that I think is realistic in a Homenet
> deployment:
>=20
>   Internet --- A --- B....C          --- is Ethernet
>                 .        .           ... is WiFi
>                  ........
>=20
> Current implementations of Babel are known to work well in such =
topologies.
>=20
> As far as I am aware, current implementations of IS-IS are not.  =
Getting
> IS-IS to work well on such topologies is not completely trivial.

The issue here is link metric feedback into the routing protocol. Can be =
done for both Babel and ISIS. draft-mrw-homenet-rtg-comparison-01 is =
correct.

With ISIS, I am not aware of any implementation for dynamic link metric =
feedback.

And yes, it must be automatic and link metrics for wireless links are =
dynamic, even for static nodes. Other objects may move.

Teco

>=20
> -- Juliusz
>=20
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet


From nobody Thu Feb 19 14:08:02 2015
Return-Path: <teco@inf-net.nl>
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 7DF651A0373 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 14:08:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 8URrpVA5_GVp for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 14:07:59 -0800 (PST)
Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 158BE1A037B for <homenet@ietf.org>; Thu, 19 Feb 2015 14:07:58 -0800 (PST)
Received: by wesw55 with SMTP id w55so2394699wes.5 for <homenet@ietf.org>; Thu, 19 Feb 2015 14:07:57 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=Oio8rKDN5e0xngMYTaLIPRV5suvy446INx1uYJVM79Y=; b=EH+TrBTYu0Dz3ARon43LoCe4zZh7lYI36qlP6vi9Hvqf5JG4b5iJE9s2WAYWNCbxNc ILx5a3B0OvqIIJsoAtHuS1l7KV639EzkUgxGooV1NndAGo5fYCuIwFlLirwccn8Wop2F X9rphFUv+UJMYHIEoBy+XSVPw53LT91ePcWniaK8BE0iKd8/YyhTyZRagpgCSA7wA+wz L4Wek4YjNNiN9RByt3Euo6OGluPN2vI7eLDS9SxCVYBuJ7A9BHdooANV5o5ZkGu95uF4 bcM728XLSHPzUj6NoGhU5OVpYYXv58LIkuoRfAahU6YuCdyRgd3MUjeymEfAck71ez3c TAqw==
X-Gm-Message-State: ALoCoQkZtOqGlaEJKYqqniUchuX4aqntVzX++6bS0HqW3MPXJWMFLFscGDE+AjpHAUX8CWCVFUl/
X-Received: by 10.180.36.212 with SMTP id s20mr14257488wij.58.1424383676378; Thu, 19 Feb 2015 14:07:56 -0800 (PST)
Received: from [192.168.178.10] (524A158D.cm-4-3a.dynamic.ziggo.nl. [82.74.21.141]) by mx.google.com with ESMTPSA id c4sm32047723wik.0.2015.02.19.14.07.54 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 19 Feb 2015 14:07:55 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Teco Boot <teco@inf-net.nl>
In-Reply-To: <AD5FCDA8-54E5-45A2-B254-4B9D840F5F48@employees.org>
Date: Thu, 19 Feb 2015 23:07:54 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <CAEB4CF5-102D-4DAE-BEBD-6D5FFCC2138B@inf-net.nl>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <F2818678-A728-4300-896C-E220A0DF0D1A@employees.org> <42E2F1D5-AF35-404E-9FBE-D1C7341D88B0@inf-net.nl> <AD5FCDA8-54E5-45A2-B254-4B9D840F5F48@employees.org>
To: Ole Troan <otroan@employees.org>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/RA52YtxzFaFma3Uqmf_NwORw_74>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Ted Lemon <mellon@fugue.com>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 22:08:01 -0000

> Op 19 feb. 2015, om 22:27 heeft Ole Troan <otroan@employees.org> het =
volgende geschreven:
>=20
>>>=20
>>>>> It means that every single device on a wired network is on a =
different subnet.  Perhaps it doesn't cause any extreme harm, but it =
certainly makes managing and debugging the network harder, and it means =
that you can't have a layer two switch anymore.  So the question I would =
ask is not "is there a problem with this," because obviously there is, =
but rather "is there a benefit to doing it this way."  I am curious to =
know what you think the benefit is.
>>>>=20
>>>> I am not mandating that each and every device is in its own =
broadcast domain, I am however advocating that we leave the model that =
has been prevalent for 10-15 years at least, ie that a home gateway has =
a "WAN" port and 4 "LAN" ports, and these 4 ports are bridged. I'm =
saying the typical device should have 4-5 "L3" ports. You're then free =
to connect one of these to your L2 switch if you so please.
>>>>=20
>>>> I would like my router-to-router links to not have a lot of hosts =
in them if I can avoid it.
>>>=20
>>> +1.
>>>=20
>>> there are very few shared media around anymore.
>>=20
>> Still one to phase out: spectrum ;-)
>>=20
>> I would say the opposite, I see kids that have never been connected =
to a wired link. What about wireless repeaters, which forward packets =
and do not have a network jacket? Wireless backhaul links to ISP?
>=20
> yes, at L1 but not L2, which was what I was trying to say. citing =
802.11 as an example.

Hmm, I don't know what a L2 shared medium is.

More important: as long as switching IP addresses break connections, =
subnetting WiFi APs is really bad. So what we do today is setup our =
multiple home WiFi AP networks in the same subnet, same broadcast =
domain. Handover isn't great, but it works.

As long as we don't bring in a WLAN controller or alternative, what is =
our plan?  =20

Teco =20


>=20
> cheers,
> Ole
>=20
>=20
>>=20
>> Teco
>>=20
>>=20
>>> I don't think I've ever been connected to a 10base5.
>>> why should the IP subnet model emulate a shared medium, when the =
physical topology is a star.
>>>=20
>>> wireless with security is also a star topology, with a =
unidirectional broadcast channel.
>>>=20
>>> cheers,
>>> Ole
>>> _______________________________________________
>>> homenet mailing list
>>> homenet@ietf.org
>>> https://www.ietf.org/mailman/listinfo/homenet
>=20


From nobody Thu Feb 19 14:23:15 2015
Return-Path: <teco@inf-net.nl>
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 AB97C1A0AF1 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 14:23:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 DNP1lZSPisPr for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 14:23:11 -0800 (PST)
Received: from mail-wi0-f181.google.com (mail-wi0-f181.google.com [209.85.212.181]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A5A911A0372 for <homenet@ietf.org>; Thu, 19 Feb 2015 14:23:11 -0800 (PST)
Received: by mail-wi0-f181.google.com with SMTP id r20so12420165wiv.2 for <homenet@ietf.org>; Thu, 19 Feb 2015 14:23:10 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=HcpfR4JNlVnNyg84tP+bSDY+HF9LsSrF0qjWxZGDPnA=; b=WZWfNCjD3lfYsMYGCQa/IsR0aC7hkXWw1WGCiAZ3uW2hFy4DimjAWiPP1zcUD7vE61 aB4R/Huaj1SLSH8tv5DR6i48xw6fyjGnOue1lzFTL+2XP1CTvcPuxgd2fr6kvxp5pOf6 E3Nu6BseKDvCiJfmoYlTRyo15AOID2W8vEqbPGRJGg2Z52WZxCPF6XMhOtuhcXp2AFaS VMrRVGWjf/UzvyQwjqdM1lYI6HsYGkzMV2PuKO3xTFmLNJ3tcb8JnaId0H0KgS7KBVDA oBX44/i5+zBfgaIPaw0rzQeHYiIbwg9u3/RWAPraxoTWwXVxR8IAPSCpnzzOVSxSwhu6 bgbQ==
X-Gm-Message-State: ALoCoQm/hAf5lpvaxmRD1QTklvX7u+M1nmc2zQd6CGjlcckgFcZ0tTYpGKe37g20keurnOeCZPhw
X-Received: by 10.180.87.106 with SMTP id w10mr18830280wiz.62.1424384590237; Thu, 19 Feb 2015 14:23:10 -0800 (PST)
Received: from [192.168.178.10] (524A158D.cm-4-3a.dynamic.ziggo.nl. [82.74.21.141]) by mx.google.com with ESMTPSA id cj12sm39279629wjb.35.2015.02.19.14.23.08 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 19 Feb 2015 14:23:09 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Teco Boot <teco@inf-net.nl>
In-Reply-To: <CAA93jw57sNMPsKkL-W2m3s20DKsFZWNeGZSOgnmRTj3yz+Rgmg@mail.gmail.com>
Date: Thu, 19 Feb 2015 23:23:08 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <EA20D83F-3E46-4484-AD65-518B1C3836DA@inf-net.nl>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <A5767F83-3D0C-40E5-A73B-912E3C160A42@fugue.com> <alpine.DEB.2.02.1502191235240.4007@uplift.swm.pp.se> <87zj89gaqm.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191804050.4007@uplift.swm.pp.se> <D10B8924.6BD5%John_Leddy@cable.comcast.com> <87h9uhg529.wl-jch@pps.univ-paris-diderot.fr> <87fva1fzwp.wl-jch@pps.univ-paris-diderot.fr> <CAA93jw57sNMPsKkL-W2m3s20DKsFZWNeGZSOgnmRTj3yz+Rgmg@mail.gmail.com>
To: Dave Taht <dave.taht@gmail.com>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/YE0mH8IXkAb_AqJg3mMpsNhw-JU>
Cc: "Leddy, John" <John_Leddy@cable.comcast.com>, Mikael Abrahamsson <swmike@swm.pp.se>, "homenet@ietf.org Group" <homenet@ietf.org>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] More about marginal links [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 22:23:13 -0000

> Op 19 feb. 2015, om 22:01 heeft Dave Taht <dave.taht@gmail.com> het =
volgende geschreven:
>>=20
>> 1. Prefer solid links
>>=20
>> This is pretty obvious.  If you can choose between an Ethernet link =
and
>=20
> Well, ethernet runs at different speeds and there is no abstraction
> for that in babel...

Why not?=20
I mean the babel protocol, not current code.

After having selected the Homenet Routing Protocol, I expect some =
discussion on how to set the metric. If box A from vendor A sets =
cost=3D100 on 1GE links and another box B from vendor B sets cost=3D50 =
on 2Mbit/sec WiFi links, we might have non-optimal paths. No-one around =
to adjust the config, right?

So what I want to see is a proposal for a routing protocol that specify =
link metrics for a set of commonly used link types in homes. This spec =
could be BCP.

Teco



From nobody Thu Feb 19 14:26:32 2015
Return-Path: <mellon@fugue.com>
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 E34B01A0372 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 14:26:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 cLT9BXjNy-Hf for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 14:26:28 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id DBC3E1A001A for <homenet@ietf.org>; Thu, 19 Feb 2015 14:26:26 -0800 (PST)
Received: from [10.0.20.107] (c-71-233-43-215.hsd1.nh.comcast.net [71.233.43.215]) by toccata.fugue.com (Postfix) with ESMTPSA id 37BCE238059C; Thu, 19 Feb 2015 17:26:24 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <EA20D83F-3E46-4484-AD65-518B1C3836DA@inf-net.nl>
Date: Thu, 19 Feb 2015 17:25:48 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <B5DA0C2A-6D01-4A68-8413-50FA5C5FF9D8@fugue.com>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <A5767F83-3D0C-40E5-A73B-912E3C160A42@fugue.com> <alpine.DEB.2.02.1502191235240.4007@uplift.swm.pp.se> <87zj89gaqm.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191804050.4007@uplift.swm.pp.se> <D10B8924.6BD5%John_Leddy@cable.comcast.com> <87h9uhg529.wl-jch@pps.univ-paris-diderot.fr> <87fva1fzwp.wl-jch@pps.univ-paris-diderot.fr> <CAA93jw57sNMPsKkL-W2m3s20DKsFZWNeGZSOgnmRTj3yz+Rgmg@mail.gmail.com> <EA20D83F-3E46-4484-AD65-518B1C3836DA@inf-net.nl>
To: Teco Boot <teco@inf-net.nl>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/Lo0nwk3uHkGqTWsPFp5j6HNuD9A>
Cc: "Leddy, John" <John_Leddy@cable.comcast.com>, "homenet@ietf.org Group" <homenet@ietf.org>, Dave Taht <dave.taht@gmail.com>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] More about marginal links [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 22:26:30 -0000

On Feb 19, 2015, at 5:23 PM, Teco Boot <teco@inf-net.nl> wrote:
> After having selected the Homenet Routing Protocol, I expect some =
discussion on how to set the metric. If box A from vendor A sets =
cost=3D100 on 1GE links and another box B from vendor B sets cost=3D50 =
on 2Mbit/sec WiFi links, we might have non-optimal paths. No-one around =
to adjust the config, right?

Bear in mind that this stuff changes depending on what's plugged in, so =
it's a legitimate point that if you are 1gbps-capable, but a 100mbps =
thing is plugged into one port and a 10mbps into another, you have a =
mismatch to deal with.=


From nobody Thu Feb 19 14:42:28 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 EFD4C1A0007 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 14:42:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35] autolearn=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 afWT-DWw1CAT for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 14:42:25 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 48EAB1A00B1 for <homenet@ietf.org>; Thu, 19 Feb 2015 14:42:23 -0800 (PST)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t1JMgLNN020418; Thu, 19 Feb 2015 23:42:21 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id A8AA711ED5; Thu, 19 Feb 2015 23:42:21 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id IbZzB7Bg7NTH; Thu, 19 Feb 2015 23:42:20 +0100 (CET)
Received: from pirx.pps.jussieu.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 2F7E3119AF; Thu, 19 Feb 2015 23:42:19 +0100 (CET)
Date: Thu, 19 Feb 2015 23:42:19 +0100
Message-ID: <87zj89ed6c.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Teco Boot <teco@inf-net.nl>
In-Reply-To: <EA20D83F-3E46-4484-AD65-518B1C3836DA@inf-net.nl>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <A5767F83-3D0C-40E5-A73B-912E3C160A42@fugue.com> <alpine.DEB.2.02.1502191235240.4007@uplift.swm.pp.se> <87zj89gaqm.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191804050.4007@uplift.swm.pp.se> <D10B8924.6BD5%John_Leddy@cable.comcast.com> <87h9uhg529.wl-jch@pps.univ-paris-diderot.fr> <87fva1fzwp.wl-jch@pps.univ-paris-diderot.fr> <CAA93jw57sNMPsKkL-W2m3s20DKsFZWNeGZSOgnmRTj3yz+Rgmg@mail.gmail.com> <EA20D83F-3E46-4484-AD65-518B1C3836DA@inf-net.nl>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Thu, 19 Feb 2015 23:42:21 +0100 (CET)
X-Miltered: at korolev with ID 54E666CD.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54E666CD.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54E666CD.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/jgNkhUjDvMSd8tIyOHAkcqfHI_w>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] More about marginal links [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 22:42:27 -0000

>> Well, ethernet runs at different speeds and there is no abstraction
>> for that in babel...

> Why not? 

Switches.

Most home routers have their (on-chip) Ethernet interface behind an
internal switch.  That is how they provide 5 or more Ethernet ports using
a single-NIC SoC.

That has the unfortunate consequence that neither carrier sense nor link
speed sensing is going to work on most home routers without model-specific
code.

That is what I allude to in Section 4.3 of the draft, but I see that
I need to be more explicit in -02.  Your (plural) feedback is being
helpful.

> I mean the babel protocol, not current code.

Oh, if I don't have to implement it, then I'm all in favour ;-)

> So what I want to see is a proposal for a routing protocol that specify
> link metrics for a set of commonly used link types in homes.

That's something the IS-IS community has already done, I believe, although
their values might not map directly to Babel metrics (which are just 16 bits
long).

-- Juliusz


From nobody Thu Feb 19 15:03:12 2015
Return-Path: <mcr@sandelman.ca>
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 CA67B1A0372 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 15:03:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 3J-69pYO40uG for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 15:03:08 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ADD241A0371 for <homenet@ietf.org>; Thu, 19 Feb 2015 15:03:08 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 42D0F20012 for <homenet@ietf.org>; Thu, 19 Feb 2015 18:11:03 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id 87B5563A21; Thu, 19 Feb 2015 18:03:07 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 71062637F4 for <homenet@ietf.org>; Thu, 19 Feb 2015 18:03:07 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "homenet\@ietf.org Group" <homenet@ietf.org>
In-Reply-To: <812BE11C-CB57-4594-81CD-A54AC8A16EFF@gmail.com>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <F2818678-A728-4300-896C-E220A0DF0D1A@employees.org> <ADBDED5C-5279-4A04-B7C8-FCCB453A8C4F@gmail.com> <B2BEAF63-D219-41A0-8209-1EEFE9667440@fugue.com> <812BE11C-CB57-4594-81CD-A54AC8A16EFF@gmail.com>
X-Mailer: MH-E 8.6; nmh 1.3-dev; GNU Emacs 24.4.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Thu, 19 Feb 2015 18:03:07 -0500
Message-ID: <21418.1424386987@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/3F19VKQWw1ZsjlCb9CcaqIXYrpE>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 23:03:10 -0000

--=-=-=
Content-Type: text/plain


Ralph Droms <rdroms.ietf@gmail.com> wrote:
    >> What Mikael is saying is that on homenet devices (not switches) each
    >> port is treated as a separate network, on the assumption that all of
    >> the physical ports on the homenet device are likely to connect to
    >> routers, and that any switched topology would be done using switches
    >> connected to homenet routers.

    > But I think one of the important points for homenet is that many people
    > will just buy "internet" devices, not routers and switches.  I've been
    > out of the loop so I should go back and check the architecture before I
    > say too much more ... what is the expectation for grouping ports on
    > homenet devices and is there an expectation that people will buy
    > homenet devices and switches and know where to use them both?

My claim is that overtime there will be no "switches" in the home or in
futureshop/bestbuy/newegg.  They will all be homenet.  It's already been a
decade that people buy new "routers" when they should have bought switches,
and then wind up with dualing DHCP servers, or, as we have discussed here
many times: unintended chains of NAT.

But, as for physical ports on homenet devices, in the architecture we say
that those are supposed to be merged as a single l2 domain, and only split up
if there is some (out of band) reason to do that.


--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEVAwUBVOZrq4CLcPvd0N1lAQLmSQf/dLwXnih2FtMXwcSntYHiS6D9gkQqmGRF
3v8eA68JuORSIbfYrG6rVkGsaxIiAvLUjkejnbdgUdrY4GR8oPwUJemiMd+2fyaQ
nf+ffOFdtC8nmCPx75hGT9CahRxRKZtfpThsSh/YX3u2Eyf1PGhIEDv43cS6aV0z
LFKIMPgtT0npmGnizH+o3T+xwH9KN6R5zDpHM1S2l/LGpJQ8tPl1aMcBA/YAMI/C
aVIuHTLPSr3zhdQD/W8J9bTvzW1YSAsGRmXqK/6eCoh77TbNBsWSlwT37tq3fWvu
SItz+lsghUx6OG/qFHHL7oPuLHKcnKmqdtEAZlPM1bQAJztNCbKz6Q==
=ewFZ
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Thu Feb 19 15:45:08 2015
Return-Path: <sander@steffann.nl>
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 DE2841A1A50 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 15:45:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.094
X-Spam-Level: 
X-Spam-Status: No, score=0.094 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_NL=0.55, HOST_EQ_NL=1.545, SPF_PASS=-0.001] autolearn=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 lNBVMrh5vb8X for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 15:45:06 -0800 (PST)
Received: from mail.sintact.nl (mail.sintact.nl [IPv6:2001:9e0:803::6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 30CC61A1A4F for <homenet@ietf.org>; Thu, 19 Feb 2015 15:45:06 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.sintact.nl (Postfix) with ESMTP id EBF4A40; Fri, 20 Feb 2015 00:45:03 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=steffann.nl; h= x-mailer:references:message-id:content-transfer-encoding:date :date:in-reply-to:from:from:subject:subject:mime-version :content-type:content-type:received:received; s=mail; t= 1424389502; bh=R5SyfS2owl88/EA5nk6IbC7B0N87iAwGZThPbrYgCeo=; b=Z vgw+3lzFnmm9h2I0HpVYd6hQsH90oqdHwzWuYE8oU9BrZEzTl7yCZbtoBOU4Dg6R GFadkbFRWhMRAnq7//thoG5VKRwZte/7Br3hNWHkmK5M7kXjtGWuKgnv6HfqgJBM 4Kw9pCiS5Le+kEJB4Ad4hVJemXA/WuZC5D5rGNmZ2w=
X-Virus-Scanned: Debian amavisd-new at mail.sintact.nl
Received: from mail.sintact.nl ([127.0.0.1]) by localhost (mail.sintact.nl [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id uSjpw8v0jQaF; Fri, 20 Feb 2015 00:45:02 +0100 (CET)
Received: from macpro.10ww.steffann.nl (macpro.10ww.steffann.nl [37.77.56.75]) by mail.sintact.nl (Postfix) with ESMTPSA id B9F883B; Fri, 20 Feb 2015 00:45:01 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2081\))
From: Sander Steffann <sander@steffann.nl>
In-Reply-To: <DE5D415F-4804-44C2-9621-523C3EFBC859@fugue.com>
Date: Fri, 20 Feb 2015 00:45:01 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <DD0D0BE4-3753-4305-85D5-00CC8A37D045@steffann.nl>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <54E58238.9030809@mtcc.com> <874mqigcct.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191622510.4007@uplift.swm.pp.se> <87vbixg9fe.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191806381.4007@uplift.swm.pp.se> <87lhjtg6jc.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191826230.4007@uplift.swm.pp.se> <2FE73365-ECD7-49C3-8476-934CD1032542@fugue.com> <alpine.DEB.2.02.1502191924250.4007@uplift.swm.pp.se> <DE5D415F-4804-44C2-9621-523C3EFBC859@fugue.com>
To: Ted Lemon <mellon@fugue.com>
X-Mailer: Apple Mail (2.2081)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/iqn7prRDMQTqdxRHRdQadAHt3RA>
Cc: homenet@ietf.org, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 23:45:08 -0000

Hi Ted,

> Op 19 feb. 2015, om 19:49 heeft Ted Lemon <mellon@fugue.com> het =
volgende geschreven:
>=20
> I don't know.   Homenet multicast is an open issue.   But I don't =
think this use case represents a serious problem, because as far as I =
can tell streaming video is not done using multicast in practice anyway.

Sorry, bad assumption. I just finished working on a TV streaming project =
for an ISP and there is lots of multicast there. All live TV channel =
streams to STBs are multicast and this is a common setup amongst ISPs.

Cheers,
Sander


From nobody Thu Feb 19 15:46:01 2015
Return-Path: <eckert@cisco.com>
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 36C8A1A1A50 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 15:46:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 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_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 HfiB8iKL5jAC for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 15:45:58 -0800 (PST)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 504F91A1A4F for <homenet@ietf.org>; Thu, 19 Feb 2015 15:45:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1356; q=dns/txt; s=iport; t=1424389558; x=1425599158; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=XlZPIuu6pRWv2YB8VPDA3f+c1kSjXVVlORS5BQCm+nI=; b=RYBn3KQWfOt3ok7ytbPvqazv6xR56ojTxfDtAlJ+/GW/8sYM7vPEi/kO F1L3oeOHBfKBQAqLVQ40B8fKWSi2VtIJhSxnTI2jGePavflDasZBS7NDz eTiqM8xUqAy5amGxxRZhD7nPNRxtEuTx/3yPaPnoKDWm5g03bmcZTl1bY 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AHBQAVdeZU/4MNJK1bgwbKDwKBHUMBAQEBAQF8hBABAQQ6PxALDgoJJQ8FSYhC1B4BAQEBAQEBAQEBAQEBAQEBAQEBAQEXiw+EbgeDFoEUBYpEjkcBkyIihA8dgnQBAQE
X-IronPort-AV: E=Sophos;i="5.09,611,1418083200"; d="scan'208";a="125248023"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by alln-iport-4.cisco.com with ESMTP; 19 Feb 2015 23:45:57 +0000
Received: from mcast-linux1.cisco.com (mcast-linux1.cisco.com [172.27.244.121]) by alln-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id t1JNjvVl011329 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 19 Feb 2015 23:45:57 GMT
Received: from mcast-linux1.cisco.com (localhost.cisco.com [127.0.0.1]) by mcast-linux1.cisco.com (8.13.8/8.13.8) with ESMTP id t1JNju52022965; Thu, 19 Feb 2015 15:45:56 -0800
Received: (from eckert@localhost) by mcast-linux1.cisco.com (8.13.8/8.13.8/Submit) id t1JNjtoH022962; Thu, 19 Feb 2015 15:45:55 -0800
Date: Thu, 19 Feb 2015 15:45:55 -0800
From: Toerless Eckert <eckert@cisco.com>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Message-ID: <20150219234555.GB3935@cisco.com>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <20150219153938.GA3935@cisco.com> <87wq3dga50.wl-jch@pps.univ-paris-diderot.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <87wq3dga50.wl-jch@pps.univ-paris-diderot.fr>
User-Agent: Mutt/1.4.2.2i
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/Hx_YKB5p35UvMOpdpBpKu06rT14>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Dave Taht <dave.taht@gmail.com>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 23:46:00 -0000

On Thu, Feb 19, 2015 at 05:04:59PM +0100, Juliusz Chroboczek wrote:
> I suspect that the two of you may be making different assumptions.  Mikael
> is thinking of ISP-provided CPEs (marketed as "boxes" in Europe), which
> are slowly becoming fairly powerful devices.  Toerless is thinking of
> Plastic Home Routers, which have been stuck at 4MB flash and 8MB RAM for
> as long as anyone can remember.
> 
> IMHO, both kinds of devices are necessary to the success of Homenet.

Right on all points. So the biggest challenge is really how to motivate
better "in-home" devices which are not SP-OEMed and do not connect to a WAN-link.

I think those loadable apps are the key to getting the right HW into the home.

If there is an evolving SW platform for such apps that is not tied to specific
vendors on the HGW, then the same SW platform should easily proliferate
into the non-HGW homenet devices and raie their HW requirements to what we 
want.

Alas, i am not aware of a widely distributed SW platform for "embedded"
apss. Aka: Android/iOS apps - but for devices without display. Not that
it's technically difficult, its more a question of creating a critical mass
of support/interest. Java would likely be nicely lightweight. Docker could
do more and be faster but is likely  a lot more disk heavy, etc. pp.

Cheers
    Toerless


From nobody Thu Feb 19 15:47:19 2015
Return-Path: <dave.taht@gmail.com>
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 732351A1A50 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 15:47:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 XL0vXhrPEIAZ for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 15:47:15 -0800 (PST)
Received: from mail-ob0-x233.google.com (mail-ob0-x233.google.com [IPv6:2607:f8b0:4003:c01::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE53B1A1A4F for <homenet@ietf.org>; Thu, 19 Feb 2015 15:47:15 -0800 (PST)
Received: by mail-ob0-f179.google.com with SMTP id wp4so20926500obc.10 for <homenet@ietf.org>; Thu, 19 Feb 2015 15:47:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=U6Klv8hsaH8smWdPaqtVohZsau8AuBGBy7TNvOIlSAM=; b=jwKyYI04Y6Unz7qEZ0eDM3Rr63ONjs8JGtnlexqDXNCAvjTrG8/mEPgSi14zDRj2dW k7R+jznvj7Nypmd9tILvKXNUAyo+i1M0ky3PlBV5lEs2CiZ3Ghf47/4OoTyLT7EkVgxf l+gI2XWLc/v9qkxkQwXuME+WdpTtMJj0lM1HdyAfIWqJWEZqttSAWSNGwD6hNMiFpzpW 4tF9cm3Qeuu9Dvdow9kYU28+1v2Hsj9KgmCUgV0/k8oQ+1oBPRRg+S47EATfivC3gg5B x8xr8xEBGOkyGCCRuNDAu4Oi4BI5qZx+Fhi38rmTNUdfCXfZxPW8+S4cpAmkO9rKonK8 S9Dg==
MIME-Version: 1.0
X-Received: by 10.182.98.164 with SMTP id ej4mr4807123obb.0.1424389634932; Thu, 19 Feb 2015 15:47:14 -0800 (PST)
Received: by 10.202.51.66 with HTTP; Thu, 19 Feb 2015 15:47:14 -0800 (PST)
In-Reply-To: <87zj89ed6c.wl-jch@pps.univ-paris-diderot.fr>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <A5767F83-3D0C-40E5-A73B-912E3C160A42@fugue.com> <alpine.DEB.2.02.1502191235240.4007@uplift.swm.pp.se> <87zj89gaqm.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191804050.4007@uplift.swm.pp.se> <D10B8924.6BD5%John_Leddy@cable.comcast.com> <87h9uhg529.wl-jch@pps.univ-paris-diderot.fr> <87fva1fzwp.wl-jch@pps.univ-paris-diderot.fr> <CAA93jw57sNMPsKkL-W2m3s20DKsFZWNeGZSOgnmRTj3yz+Rgmg@mail.gmail.com> <EA20D83F-3E46-4484-AD65-518B1C3836DA@inf-net.nl> <87zj89ed6c.wl-jch@pps.univ-paris-diderot.fr>
Date: Thu, 19 Feb 2015 15:47:14 -0800
Message-ID: <CAA93jw68H18g2UXoyyjz-c1RnPF5cj1Qk6umJqaP_0gDGznKeQ@mail.gmail.com>
From: Dave Taht <dave.taht@gmail.com>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/OMUYXGk5l8rQ5YZL_bqFMXWGAh8>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Teco Boot <teco@inf-net.nl>
Subject: Re: [homenet] More about marginal links [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 23:47:18 -0000

On Thu, Feb 19, 2015 at 2:42 PM, Juliusz Chroboczek
<jch@pps.univ-paris-diderot.fr> wrote:
>>> Well, ethernet runs at different speeds and there is no abstraction
>>> for that in babel...
>
>> Why not?
>
> Switches.
>
> Most home routers have their (on-chip) Ethernet interface behind an
> internal switch.  That is how they provide 5 or more Ethernet ports using
> a single-NIC SoC.

It is even worse than that. Many of the more modern devices only have
a single ethernet device, and they use a vlan trick in order to get an
ISP uplink port out of it.

This is one of the cases where applying a hardware rate limited aqm/fq
system doesn=C2=B4t work at all, you end up with Hol as everything in all
directions vanishes into the switch, and of course things like link
detection go by the wayside. Another painful aspect of this is when a
box is supplying a default gateway but actually has not achieved
internet access. Tools like babel-pinger help, but are not tightly
integrated with dhcp.

Welcome to the race to the bottom.

> That has the unfortunate consequence that neither carrier sense nor link
> speed sensing is going to work on most home routers without model-specifi=
c
> code.
>
> That is what I allude to in Section 4.3 of the draft, but I see that
> I need to be more explicit in -02.  Your (plural) feedback is being
> helpful.
>
>> I mean the babel protocol, not current code.
>
> Oh, if I don't have to implement it, then I'm all in favour ;-)
>
>> So what I want to see is a proposal for a routing protocol that specify
>> link metrics for a set of commonly used link types in homes.
>
> That's something the IS-IS community has already done, I believe, althoug=
h
> their values might not map directly to Babel metrics (which are just 16 b=
its
> long).
>
> -- Juliusz
>
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet



--=20
Dave T=C3=A4ht

thttp://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks


From nobody Thu Feb 19 15:49:32 2015
Return-Path: <dave.taht@gmail.com>
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 1DC5D1A1A5A for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 15:49:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 HvSY0BLkdxY1 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 15:49:28 -0800 (PST)
Received: from mail-ob0-x22c.google.com (mail-ob0-x22c.google.com [IPv6:2607:f8b0:4003:c01::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 350491A1A50 for <homenet@ietf.org>; Thu, 19 Feb 2015 15:49:28 -0800 (PST)
Received: by mail-ob0-f172.google.com with SMTP id nt9so21044347obb.3 for <homenet@ietf.org>; Thu, 19 Feb 2015 15:49:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=4pPHnbKbIxLk8K5wuTmGUu5kPKUzwhAsFf0j6if7gCc=; b=X8i3e7zi9S62GZA5dP6OOa8VoWHtwd9EeAoI2YnUupf/o+m3v4e5Pthub+mG2D1PHv 6Bdty0RXjQn4pQgx1QcEc8MHEK7E7c7aURStWaNFN/Ee4uXSmH94Y2KEX5cE5DgXy0ME cCzdGJjoEnfuRM9DkQydp20NC+aleph9+XBSF2yqhx3ig7XRpOp1OkJzUBf9fdFl/Bj7 h8ShRXkpUtGJYH1Fk41tFhRNpfFDiR226pjWqthhfpeqLAIDcWnSna6kS7TNpwJ3gkZc mbBkW0n+ZMj0Pr4vp2ZSIkpFpbjlf+N4R+hEYsvcL67ptbDlMvu4I3C1DJslqdhJoq9D kRzw==
MIME-Version: 1.0
X-Received: by 10.202.3.65 with SMTP id 62mr4383976oid.11.1424389767519; Thu, 19 Feb 2015 15:49:27 -0800 (PST)
Received: by 10.202.51.66 with HTTP; Thu, 19 Feb 2015 15:49:27 -0800 (PST)
In-Reply-To: <DD0D0BE4-3753-4305-85D5-00CC8A37D045@steffann.nl>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <54E58238.9030809@mtcc.com> <874mqigcct.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191622510.4007@uplift.swm.pp.se> <87vbixg9fe.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191806381.4007@uplift.swm.pp.se> <87lhjtg6jc.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191826230.4007@uplift.swm.pp.se> <2FE73365-ECD7-49C3-8476-934CD1032542@fugue.com> <alpine.DEB.2.02.1502191924250.4007@uplift.swm.pp.se> <DE5D415F-4804-44C2-9621-523C3EFBC859@fugue.com> <DD0D0BE4-3753-4305-85D5-00CC8A37D045@steffann.nl>
Date: Thu, 19 Feb 2015 15:49:27 -0800
Message-ID: <CAA93jw7T_zQ0yx+zKpxW0rbuEE4eY5k--AoGmh9BVQXVibENHA@mail.gmail.com>
From: Dave Taht <dave.taht@gmail.com>
To: Sander Steffann <sander@steffann.nl>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/GxmnXEWs0NHhICeKxKSV3kFAXis>
Cc: HOMENET <homenet@ietf.org>, Ted Lemon <mellon@fugue.com>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 19 Feb 2015 23:49:30 -0000

On Thu, Feb 19, 2015 at 3:45 PM, Sander Steffann <sander@steffann.nl> wrote=
:
> Hi Ted,
>
>> Op 19 feb. 2015, om 19:49 heeft Ted Lemon <mellon@fugue.com> het volgend=
e geschreven:
>>
>> I don't know.   Homenet multicast is an open issue.   But I don't think =
this use case represents a serious problem, because as far as I can tell st=
reaming video is not done using multicast in practice anyway.
>
> Sorry, bad assumption. I just finished working on a TV streaming project =
for an ISP and there is lots of multicast there. All live TV channel stream=
s to STBs are multicast and this is a common setup amongst ISPs.

One of the reasons free.fr can=C2=B4t do down to the cpe shaping
effectively is because their multicast IPtv code is deeply embedded
into the DSL framing layer and not visible to the overlying OS.

> Cheers,
> Sander
>
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet



--=20
Dave T=C3=A4ht

thttp://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks


From nobody Thu Feb 19 16:04:45 2015
Return-Path: <andrewmcgr@google.com>
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 E071E1A1A6B for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 16:04:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level: 
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 3Tk3bsWeBJSr for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 16:04:43 -0800 (PST)
Received: from mail-qg0-x22f.google.com (mail-qg0-x22f.google.com [IPv6:2607:f8b0:400d:c04::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 209811A1A42 for <homenet@ietf.org>; Thu, 19 Feb 2015 16:04:42 -0800 (PST)
Received: by mail-qg0-f47.google.com with SMTP id q107so10770931qgd.6 for <homenet@ietf.org>; Thu, 19 Feb 2015 16:04:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ZBStqFMdUmnQptTprmhRlWzutIL7MaYYuhcyqdR0pMk=; b=E0U+Z/1Pw+w8incG7zaLH6AlpOU3NX424wVkDgxET7nKyZDcbX6iMUk/lHaBxYE3HP 9uyeAqYN2UYAxy8fjNX594ZnFN9KzHvpaiULi+iXs4qNtRfbRWzaO9nKXXo46+DYU2qc MwvH8zWbdjSPtD9HDUNRNblGDpcEVed8TXSGnANMcU9f+lWr7eE9DhYE/T9AeX/tst4W Jh2ZqEU+3A7SM2X6oppy7gBLqVEgrOx8SmVGHZBnjcXMcSY7nqr5eD8XqrSsNgS9x+WJ bCHNJLUOwM5q0jEceRZuBdNlK1p3zOYxUggDYvK1jvuoreE2ShIgzasDEf0/MruZo/+x vOfQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=ZBStqFMdUmnQptTprmhRlWzutIL7MaYYuhcyqdR0pMk=; b=Acovn9+KmXi8LoP834TTYWmwM+huUAzzkS6f5So1tp4yX8w1D3PQ8NhJKgh9x9TFpc 9oYsVkq2r2GVQipjFoARf4BS/zmBel9DUxQ3YpxfKnUmxRUgkj3+Nt2NgXY+76YVXZe/ awaTxRsvMqiDnBALEbhHLR0/zVgVIPtYI9lvVQgBw/D0hRUtqx0cAMfR7YWhbKszF4Mx jn4d588m7itZz3vYR/Qnc9RhV/rvTcdc2YBKxqwWM/T1nWPkXL/1TSAG0wLofA5WxUYh 5br5hfXn9b6WA4sXWbJ1AZraUDu6ruirNDZouijr4pDd3zcE3CYQUp7S0JUlbFMHh43k hsdQ==
X-Gm-Message-State: ALoCoQkH3FY6bXbqX+6wgOIQA3pI9ssQTPeJ+89rWKYDFH8xsS1AvyEt5TztPsQslYvg+2Ct6E/N
MIME-Version: 1.0
X-Received: by 10.140.165.209 with SMTP id l200mr18087799qhl.84.1424390682049;  Thu, 19 Feb 2015 16:04:42 -0800 (PST)
Received: by 10.96.68.74 with HTTP; Thu, 19 Feb 2015 16:04:41 -0800 (PST)
In-Reply-To: <alpine.DEB.2.02.1502191920560.4007@uplift.swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <8B98F698-983D-4D2A-B5D1-7ACED27C275E@fugue.com> <alpine.DEB.2.02.1502191920560.4007@uplift.swm.pp.se>
Date: Fri, 20 Feb 2015 11:04:41 +1100
Message-ID: <CAPRuP3mpNJTu6mP+RAVKKO0kt60PogNtNbCUCRRqxe9im3EzjA@mail.gmail.com>
From: Andrew Mcgregor <andrewmcgr@google.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Content-Type: multipart/alternative; boundary=001a1134f1d4a0226c050f79cc06
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/de6gedCUUq-h_ddnfEmKu8fwaiM>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Ted Lemon <mellon@fugue.com>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 00:04:45 -0000

--001a1134f1d4a0226c050f79cc06
Content-Type: text/plain; charset=UTF-8

Why?  PIM and MLD snooping are pretty standard on very low-end enterprise
switches, which will be next year's midrange consumer models.  If the
dumb-as-rocks stuff goes away, that would generally make people happier.

On 20 February 2015 at 05:22, Mikael Abrahamsson <swmike@swm.pp.se> wrote:

> On Thu, 19 Feb 2015, Ted Lemon wrote:
>
>  On Feb 19, 2015, at 1:08 PM, Mikael Abrahamsson <swmike@swm.pp.se> wrote:
>>
>>> I would like my router-to-router links to not have a lot of hosts in
>>> them if I can avoid it.
>>>
>>
>> Why is that?
>>
>
> If we're going to be routing multicast within the home, we're most likely
> going to have to use some kind of variant of PIM. Asking the L2 switches
> people connect to the router to support both PIM and MLD snooping seem like
> it might be asking too much.
>
> I might be wrong though.
>
> --
> Mikael Abrahamsson    email: swmike@swm.pp.se
>
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>



-- 
Andrew McGregor | SRE | andrewmcgr@google.com | +61 4 1071 2221

--001a1134f1d4a0226c050f79cc06
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Why?=C2=A0 PIM and MLD snooping are pretty standard on ver=
y low-end enterprise switches, which will be next year&#39;s midrange consu=
mer models.=C2=A0 If the dumb-as-rocks stuff goes away, that would generall=
y make people happier.</div><div class=3D"gmail_extra"><br><div class=3D"gm=
ail_quote">On 20 February 2015 at 05:22, Mikael Abrahamsson <span dir=3D"lt=
r">&lt;<a href=3D"mailto:swmike@swm.pp.se" target=3D"_blank">swmike@swm.pp.=
se</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"marg=
in:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=3D""=
>On Thu, 19 Feb 2015, Ted Lemon wrote:<br>
<br>
</span><span class=3D""><blockquote class=3D"gmail_quote" style=3D"margin:0=
 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Feb 19, 2015, at 1:08 PM, Mikael Abrahamsson &lt;<a href=3D"mailto:swmik=
e@swm.pp.se" target=3D"_blank">swmike@swm.pp.se</a>&gt; wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
I would like my router-to-router links to not have a lot of hosts in them i=
f I can avoid it.<br>
</blockquote>
<br>
Why is that?<br>
</blockquote>
<br></span>
If we&#39;re going to be routing multicast within the home, we&#39;re most =
likely going to have to use some kind of variant of PIM. Asking the L2 swit=
ches people connect to the router to support both PIM and MLD snooping seem=
 like it might be asking too much.<br>
<br>
I might be wrong though.<span class=3D"im HOEnZb"><br>
<br>
-- <br>
Mikael Abrahamsson=C2=A0 =C2=A0 email: <a href=3D"mailto:swmike@swm.pp.se" =
target=3D"_blank">swmike@swm.pp.se</a><br>
<br></span><div class=3D"HOEnZb"><div class=3D"h5">
______________________________<u></u>_________________<br>
homenet mailing list<br>
<a href=3D"mailto:homenet@ietf.org" target=3D"_blank">homenet@ietf.org</a><=
br>
<a href=3D"https://www.ietf.org/mailman/listinfo/homenet" target=3D"_blank"=
>https://www.ietf.org/mailman/<u></u>listinfo/homenet</a><br>
</div></div></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>=
<div class=3D"gmail_signature"><div dir=3D"ltr"><span style=3D"color:rgb(85=
,85,85);font-family:sans-serif;font-size:small;line-height:1.5em;border-wid=
th:2px 0px 0px;border-style:solid;border-color:rgb(213,15,37);padding-top:2=
px;margin-top:2px">Andrew McGregor=C2=A0|</span><span style=3D"color:rgb(85=
,85,85);font-family:sans-serif;font-size:small;line-height:1.5em;border-wid=
th:2px 0px 0px;border-style:solid;border-color:rgb(51,105,232);padding-top:=
2px;margin-top:2px">=C2=A0SRE=C2=A0|</span><span style=3D"color:rgb(85,85,8=
5);font-family:sans-serif;font-size:small;line-height:1.5em;border-width:2p=
x 0px 0px;border-style:solid;border-color:rgb(0,153,57);padding-top:2px;mar=
gin-top:2px">=C2=A0<a href=3D"mailto:andrewmcgr@google.com" target=3D"_blan=
k">andrewmcgr@google.com</a>=C2=A0|</span><span style=3D"color:rgb(85,85,85=
);font-family:sans-serif;font-size:small;line-height:1.5em;border-width:2px=
 0px 0px;border-style:solid;border-color:rgb(238,178,17);padding-top:2px;ma=
rgin-top:2px">=C2=A0+61 4 1071 2221</span><br></div></div>
</div>

--001a1134f1d4a0226c050f79cc06--


From nobody Thu Feb 19 20:52:34 2015
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 C162A1A6F33 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 20:52:32 -0800 (PST)
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 UfDtWVVMfITn for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 20:52:30 -0800 (PST)
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 728891A6F2F for <homenet@ietf.org>; Thu, 19 Feb 2015 20:52:30 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id D5FF9A5; Fri, 20 Feb 2015 05:52:27 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1424407947; bh=YpHCFtjJ1BqVXnE9HozWJQIpNPvZPTjDC5r4xCSf7LE=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=Wb393ZhDiqm3XacVsWiMJOrRUzdgLFlwr0jctwvnrnU/OXGGybL/YCiWGqEI0yKT+ 65Ap263FFauFbXcKSTf/qJk6GLJ6Uqjwi/tCsEzwg5ji5HXwx3ZH60d+ofTXRRyhk/ K3bkiig4jxozI4yS3PrL3VbxM5PCyO9NNngTQtMo=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id CB4CBA4; Fri, 20 Feb 2015 05:52:27 +0100 (CET)
Date: Fri, 20 Feb 2015 05:52:27 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
In-Reply-To: <54E63B40.20301@joelhalpern.com>
Message-ID: <alpine.DEB.2.02.1502200543260.4007@uplift.swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <54E58238.9030809@mtcc.com> <874mqigcct.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191622510.4007@uplift.swm.pp.se> <87vbixg9fe.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191806381.4007@uplift.swm.pp.se> <87lhjtg6jc.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191826230.4007@uplift.swm.pp.se> <2FE73365-ECD7-49C3-8476-934CD1032542@fugue.com> <54E63B40.20301@joelhalpern.com>
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/S2hzFpO8PUaMSe9udhumdTPoXmo>
Cc: homenet@ietf.org
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 04:52:32 -0000

On Thu, 19 Feb 2015, Joel M. Halpern wrote:

> I would note that RFC 7368 says that "simple Layer 3 topologies involving as 
> few subnets as possible are preferred in home networks".  I presume this is 
> reflective of WG agreement.
> While it does go on to note that multiple subnets are sometimes needed, 
> mandating that each physical port on the access router be a distinct subnet 
> (much less extending such a mandate further in the home) seems to violate 
> this agreement.

I never said I wanted this to be mandated. I have just presumed from 
discussions in the WG and for instance fro RFC 7368 3.2.2.1 figure 1 and 
since the issue of "organizing ports" never came up, that this was the way 
it was supposed to be (and the fact that we've been trying to automate 
"edge discovery etc"). What is the physical layout of the CER in 3.2.2.1 
fig 1?

Does it have 2xWAN ports and 2 blocks of 4xLAN ports and the customer is 
supposed to know how to connect what to where?

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


From nobody Thu Feb 19 21:11:35 2015
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 EE20A1A6F3A for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 21:11:33 -0800 (PST)
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 G4LgKWeDa6mi for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 21:11:32 -0800 (PST)
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 09BD01A6F32 for <homenet@ietf.org>; Thu, 19 Feb 2015 21:11:32 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 9B043A5; Fri, 20 Feb 2015 06:11:30 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1424409090; bh=r40TCAunsqOpPsMaOrFTXFgGpRSHJaYaRIHYZUp+8A8=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=PQGTIft0qPXHeBFhjE/0x/GXXOASfBshQM7BtgL0MZ6r78XTBMOGYjO+QmLwkmq+b AYmvvmUIwU+Ure/ySb7gf9PskcmEqbGoC23YL2z7akGVtg5I19C+WzVLornVLoS89n 3/wsUiSjgdg0EGhyTDdspXiKYWPODUg6diGpcOzM=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 950D1A4; Fri, 20 Feb 2015 06:11:30 +0100 (CET)
Date: Fri, 20 Feb 2015 06:11:30 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Michael Richardson <mcr+ietf@sandelman.ca>
In-Reply-To: <21418.1424386987@sandelman.ca>
Message-ID: <alpine.DEB.2.02.1502200607400.4007@uplift.swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <F2818678-A728-4300-896C-E220A0DF0D1A@employees.org> <ADBDED5C-5279-4A04-B7C8-FCCB453A8C4F@gmail.com> <B2BEAF63-D219-41A0-8209-1EEFE9667440@fugue.com> <812BE11C-CB57-4594-81CD-A54AC8A16EFF@gmail.com> <21418.1424386987@sandelman.ca>
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/sz3RVNapQ5hDHnhvy-G-FMq89K4>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 05:11:34 -0000

On Thu, 19 Feb 2015, Michael Richardson wrote:

> But, as for physical ports on homenet devices, in the architecture we 
> say that those are supposed to be merged as a single l2 domain, and only 
> split up if there is some (out of band) reason to do that.

Are you referring to 3.3.2 now (it took me quite a while to find it)?

3.3.2.  Largest Practical Subnets

    Today's IPv4 home networks generally have a single subnet, and early
    dual-stack deployments have a single congruent IPv6 subnet, possibly
    with some bridging functionality.  More recently, some vendors have
    started to introduce 'home' and 'guest' functions, which in IPv6
    would be implemented as two subnets.

    Future home networks are highly likely to have one or more internal
    routers and thus need multiple subnets for the reasons described
    earlier.  As part of the self-organisation of the network, the
    homenet should subdivide itself into the largest practical subnets
    that can be constructed within the constraints of link-layer
    mechanisms, bridging, physical connectivity, and policy, and where
    applicable, performance or other criteria.  In such subdivisions, the
    logical topology may not necessarily match the physical topology.
    This text does not, however, make recommendations on how such
    subdivision should occur.  It is expected that subsequent documents
    will address this problem.

    While it may be desirable to maximise the chance of link-local
    protocols operating across a homenet by maximising the size of a
    subnet, multi-subnet home networks are inevitable, so their support
    must be included.

The way this is currently written, it does look like we need some kind of 
protocol and intelligence to self-organize the ports into either L2 
domains or dedicated ports, for instance to avoid L2 loops, depending on 
how the user connects things together. I am not aware of any work done in 
this area. 3.3 says the network should be self-organizing, so the user 
should not be required to know what they're doing.

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


From nobody Thu Feb 19 23:56:24 2015
Return-Path: <teco@inf-net.nl>
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 CE39F1A7006 for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 23:56:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  J_CHICKENPOX_44=0.6, RCVD_IN_DNSWL_LOW=-0.7] 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 yZL941p1VbDy for <homenet@ietfa.amsl.com>; Thu, 19 Feb 2015 23:56:20 -0800 (PST)
Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 566041A7008 for <homenet@ietf.org>; Thu, 19 Feb 2015 23:56:19 -0800 (PST)
Received: by mail-wi0-f178.google.com with SMTP id em10so1086438wid.5 for <homenet@ietf.org>; Thu, 19 Feb 2015 23:56:18 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=SFimVSq9zaNScQnNqNf/Zfl/XzHdj89smGlE/SVnm/4=; b=NQih6ZdnbpAxlMgH1puuGryoH22+8wjr56ZXT8lgmUPl80puGWxA0NlYj3BmmrxiKk f/nZCRDpdf6w98DA++YVj3pw5NjRqHJzdrX7WhYw7KhbaijBdlpAp+YQP4v76q8h1PDl XWBvm4Ks7y+TTXtL3TUEsKJrm375DCP1UqK1e4JwAN9UTtTLO0h5qcAW0PoUNnu5oajc NOBJBjKzTACtcCpJB9yS4sZRMJaaCl1r5g4jEP3EjfOUTnwn/9utKA5OGfNPMCbLUhQp 0g4Yj7k53QyGGNaRVbzewbJE4sz6l6IrxxUoRAVX5/H+5rIr97NQPs8WX9KIUhcJG3vq U2Nw==
X-Gm-Message-State: ALoCoQmanw8maMRjH0C8JqAweihFxRYLMtaYJMDOfurz3X1B19lIOo7hc6KRokMbVrZaB21Hff+C
X-Received: by 10.180.99.194 with SMTP id es2mr13834377wib.23.1424418978494; Thu, 19 Feb 2015 23:56:18 -0800 (PST)
Received: from [192.168.178.95] (524A158D.cm-4-3a.dynamic.ziggo.nl. [82.74.21.141]) by mx.google.com with ESMTPSA id l4sm1170048wiw.9.2015.02.19.23.56.16 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 19 Feb 2015 23:56:17 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Teco Boot <teco@inf-net.nl>
In-Reply-To: <87zj89ed6c.wl-jch@pps.univ-paris-diderot.fr>
Date: Fri, 20 Feb 2015 08:56:14 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <86026D9A-78BB-4E5B-A6AA-27FB2E02441F@inf-net.nl>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <A5767F83-3D0C-40E5-A73B-912E3C160A42@fugue.com> <alpine.DEB.2.02.1502191235240.4007@uplift.swm.pp.se> <87zj89gaqm.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191804050.4007@uplift.swm.pp.se> <D10B8924.6BD5%John_Leddy@cable.comcast.com> <87h9uhg529.wl-jch@pps.univ-paris-diderot.fr> <87fva1fzwp.wl-jch@pps.univ-paris-diderot.fr> <CAA93jw57sNMPsKkL-W2m3s20DKsFZWNeGZSOgnmRTj3yz+Rgmg@mail.gmail.com> <EA20D83F-3E46-4484-AD65-518B1C3836DA@inf-net.nl> <87zj89ed6c.wl-jch@pps.univ-paris-diderot.fr>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/xZziph1Cz3GSHYVmbwgKBN68lGo>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] More about marginal links [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 07:56:23 -0000

> Op 19 feb. 2015, om 23:42 heeft Juliusz Chroboczek =
<jch@pps.univ-paris-diderot.fr> het volgende geschreven:
>=20
>>> Well, ethernet runs at different speeds and there is no abstraction
>>> for that in babel...
>=20
>> Why not?=20
>=20
> Switches.
>=20
> Most home routers have their (on-chip) Ethernet interface behind an
> internal switch.  That is how they provide 5 or more Ethernet ports =
using
> a single-NIC SoC.
>=20
> That has the unfortunate consequence that neither carrier sense nor =
link
> speed sensing is going to work on most home routers without =
model-specific
> code.
>=20
> That is what I allude to in Section 4.3 of the draft, but I see that
> I need to be more explicit in -02.  Your (plural) feedback is being
> helpful.
>=20
>> I mean the babel protocol, not current code.
>=20
> Oh, if I don't have to implement it, then I'm all in favour ;-)

Bad luck, I kindly ask you to pay a little more attention to it. Link =
metrics for wireless links are crucial, but let's not forget wired =
links.

Some years ago, Thales NLD worked on olsr-lc (link costs, ETT). A plugin =
probed WiFi link speed with large & small packets, filtered out jitter =
and used the outcome as link metric (merged with ETX, I think). For =
static networks and very patient people, it may work. For mobile =
networks, it is far, far to slow. Convergence is tens of minutes. Speed =
up some timers increases load on the wireless links to unacceptable =
levels. So it died.
=20
But for wired links at homes, this plug&play mechanism could work out =
well. No L2 API needed.

http://sourceforge.net/projects/olsr-lc/

Teco

>=20
>> So what I want to see is a proposal for a routing protocol that =
specify
>> link metrics for a set of commonly used link types in homes.
>=20
> That's something the IS-IS community has already done, I believe, =
although
> their values might not map directly to Babel metrics (which are just =
16 bits
> long).
>=20
> -- Juliusz


From nobody Fri Feb 20 00:05:03 2015
Return-Path: <hrogge@gmail.com>
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 55AC41A7011 for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 00:05:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.4
X-Spam-Level: 
X-Spam-Status: No, score=-1.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, J_CHICKENPOX_44=0.6, SPF_PASS=-0.001] autolearn=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 OqS5grqz9BUH for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 00:05:01 -0800 (PST)
Received: from mail-we0-x22b.google.com (mail-we0-x22b.google.com [IPv6:2a00:1450:400c:c03::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C62851A700E for <homenet@ietf.org>; Fri, 20 Feb 2015 00:05:00 -0800 (PST)
Received: by wevm14 with SMTP id m14so4109033wev.8 for <homenet@ietf.org>; Fri, 20 Feb 2015 00:04:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=9Ky6FG3k2C9M9s8QUCNWcQvwCnf8wwH6YhDAp7QXf/w=; b=w/J/vxrX4R0Bb0XbH7fW8iY1eEJ3XAwkS05+vVwOj1x0vLouodajQKdP97lrEptwhS Vx2Dc4b0kbQ3QfC2Y9EemYWOR6cEn3X0TeEDlwTWWN2SXyBwELFIEhQARFn0q6mKAtc4 zMHyQCBwHmLPa0sKITuAig5ebeOQRZq/suSyjnr+7gNPUlgUqwwJFY1sBgLD0rkeBbdh G0yiUxw8EpdIS+9gtHp8pN3O7FnOiv6DANzacbOA0des80soVFcV83eiRFgw0ljfsSqE ZR76h9qyV4U7MToqVS6NqUN718Gm6ww4Ybv3jf4rqxSrcPzTSHHCVegzJF9Q+rJknmVT ZDwA==
X-Received: by 10.194.177.195 with SMTP id cs3mr15904205wjc.141.1424419499553;  Fri, 20 Feb 2015 00:04:59 -0800 (PST)
MIME-Version: 1.0
Received: by 10.27.77.212 with HTTP; Fri, 20 Feb 2015 00:04:39 -0800 (PST)
In-Reply-To: <86026D9A-78BB-4E5B-A6AA-27FB2E02441F@inf-net.nl>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <A5767F83-3D0C-40E5-A73B-912E3C160A42@fugue.com> <alpine.DEB.2.02.1502191235240.4007@uplift.swm.pp.se> <87zj89gaqm.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191804050.4007@uplift.swm.pp.se> <D10B8924.6BD5%John_Leddy@cable.comcast.com> <87h9uhg529.wl-jch@pps.univ-paris-diderot.fr> <87fva1fzwp.wl-jch@pps.univ-paris-diderot.fr> <CAA93jw57sNMPsKkL-W2m3s20DKsFZWNeGZSOgnmRTj3yz+Rgmg@mail.gmail.com> <EA20D83F-3E46-4484-AD65-518B1C3836DA@inf-net.nl> <87zj89ed6c.wl-jch@pps.univ-paris-diderot.fr> <86026D9A-78BB-4E5B-A6AA-27FB2E02441F@inf-net.nl>
From: Henning Rogge <hrogge@gmail.com>
Date: Fri, 20 Feb 2015 09:04:39 +0100
Message-ID: <CAGnRvuobcSA1wP__rscE+UAMAuxEgOqML5Ute1qcFLSHh+kLng@mail.gmail.com>
To: Teco Boot <teco@inf-net.nl>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/hhJiaBS0ORYzvfKvF5HDL7uJK98>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] More about marginal links [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 08:05:02 -0000

On Fri, Feb 20, 2015 at 8:56 AM, Teco Boot <teco@inf-net.nl> wrote:
> Bad luck, I kindly ask you to pay a little more attention to it. Link met=
rics for wireless links are crucial, but let's not forget wired links.
>
> Some years ago, Thales NLD worked on olsr-lc (link costs, ETT). A plugin =
probed WiFi link speed with large & small packets, filtered out jitter and =
used the outcome as link metric (merged with ETX, I think). For static netw=
orks and very patient people, it may work. For mobile networks, it is far, =
far to slow. Convergence is tens of minutes. Speed up some timers increases=
 load on the wireless links to unacceptable levels. So it died.
>
> But for wired links at homes, this plug&play mechanism could work out wel=
l. No L2 API needed.

There is also the "linklayer database" approach I selected for my
olsrd2 implementation. Instead of hardcoding linklayer specific code
into the metric, I split the codebase into "link layer gathering" code
(which is often OS and linklayer specific), generic routing metric
code... and a generic API in between that stores the values.

This makes it quite easy to adapt the codebase to new linklayer types.

Henning Rogge


From nobody Fri Feb 20 00:19:11 2015
Return-Path: <teco@inf-net.nl>
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 ECF471A7032 for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 00:19:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  J_CHICKENPOX_44=0.6, RCVD_IN_DNSWL_LOW=-0.7] 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 0FuLcUNqMx6o for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 00:19:07 -0800 (PST)
Received: from mail-we0-f175.google.com (mail-we0-f175.google.com [74.125.82.175]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C26D91A7011 for <homenet@ietf.org>; Fri, 20 Feb 2015 00:19:06 -0800 (PST)
Received: by wesx3 with SMTP id x3so4188759wes.6 for <homenet@ietf.org>; Fri, 20 Feb 2015 00:19:05 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=NifiYOA6ZcddM9CRiVsA91cYNuIYKHrHZfXfckdXyws=; b=js/zJyLiy7gia5ROjrmHFRPaHgzI2gkKgPqAzfG2pcj/0kEfsodcWlbJCuiTK/xs9g u3FaCEVK6X61/NerBSC+8w/zxXh/C5lpnHZQkf6aPNqRLEwIhuCFc19+r+qSpkjECtUT 46ZezrT3Hdp2nsch14hatS1B42zlnNhUbOlzSQ7i/giQEYqPZDDZSTQp+eYkAlfoZ441 yKax9yACYd7HybDno5AiQn2ixtm/RFrhvnZpzHkhCqB8Xhsh828vFwYAkPwXv6bJITua he9d+uiRkZSfgHpzpM3nYwYq3k8D2iA+31BqRz08iIGc9QTcos1slgN0dcUVKTbomZ+x vCsw==
X-Gm-Message-State: ALoCoQk3CqBicAiONsj1G7iwfbqrFZpcav82fS/p5NizO/PFYplvL13C0zmOFKDJg2xyl2TGEO1h
X-Received: by 10.180.240.169 with SMTP id wb9mr22285294wic.83.1424420345306;  Fri, 20 Feb 2015 00:19:05 -0800 (PST)
Received: from [192.168.178.95] (524A158D.cm-4-3a.dynamic.ziggo.nl. [82.74.21.141]) by mx.google.com with ESMTPSA id s5sm5708945wia.1.2015.02.20.00.19.04 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 20 Feb 2015 00:19:04 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Teco Boot <teco@inf-net.nl>
In-Reply-To: <CAGnRvuobcSA1wP__rscE+UAMAuxEgOqML5Ute1qcFLSHh+kLng@mail.gmail.com>
Date: Fri, 20 Feb 2015 09:19:02 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <FA70CC1E-37E4-4824-A9F3-9711F1F84777@inf-net.nl>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <A5767F83-3D0C-40E5-A73B-912E3C160A42@fugue.com> <alpine.DEB.2.02.1502191235240.4007@uplift.swm.pp.se> <87zj89gaqm.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191804050.4007@uplift.swm.pp.se> <D10B8924.6BD5%John_Leddy@cable.comcast.com> <87h9uhg529.wl-jch@pps.univ-paris-diderot.fr> <87fva1fzwp.wl-jch@pps.univ-paris-diderot.fr> <CAA93jw57sNMPsKkL-W2m3s20DKsFZWNeGZSOgnmRTj3yz+Rgmg@mail.gmail.com> <EA20D83F-3E46-4484-AD65-518B1C3836DA@inf-net.nl> <87zj89ed6c.wl-jch@pps.univ-paris-diderot.fr> <86026D9A-78BB-4E5B-A6AA-27FB2E02441F@inf-net.nl> <CAGnRvuobcSA1wP__rscE+UAMAuxEgOqML5Ute1qcFLSHh+kLng@mail.gmail.com>
To: Henning Rogge <hrogge@gmail.com>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/DuBM64oNQNwmh3pjZDT8kY8oEtA>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] More about marginal links [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 08:19:09 -0000

> Op 20 feb. 2015, om 09:04 heeft Henning Rogge <hrogge@gmail.com> het =
volgende geschreven:
>=20
> On Fri, Feb 20, 2015 at 8:56 AM, Teco Boot <teco@inf-net.nl> wrote:
>> Bad luck, I kindly ask you to pay a little more attention to it. Link =
metrics for wireless links are crucial, but let's not forget wired =
links.
>>=20
>> Some years ago, Thales NLD worked on olsr-lc (link costs, ETT). A =
plugin probed WiFi link speed with large & small packets, filtered out =
jitter and used the outcome as link metric (merged with ETX, I think). =
For static networks and very patient people, it may work. For mobile =
networks, it is far, far to slow. Convergence is tens of minutes. Speed =
up some timers increases load on the wireless links to unacceptable =
levels. So it died.
>>=20
>> But for wired links at homes, this plug&play mechanism could work out =
well. No L2 API needed.
>=20
> There is also the "linklayer database" approach I selected for my
> olsrd2 implementation. Instead of hardcoding linklayer specific code
> into the metric, I split the codebase into "link layer gathering" code
> (which is often OS and linklayer specific), generic routing metric
> code... and a generic API in between that stores the values.
>=20
> This makes it quite easy to adapt the codebase to new linklayer types.
>=20

So you have the placeholder for an automatic ethernet link speed =
detection. Great!=20

We cannot trust ethernet port L2 feedback. Ports can be connected to =
switches with multi-rate ports. Could be powerline, wired_over_wireless =
bridges or other stuff that hides a slow link. In homes, there is no =
place for protocols that cannot detect and handle such cases.

Teco



From nobody Fri Feb 20 00:23:13 2015
Return-Path: <hrogge@gmail.com>
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 5BBA41A702F for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 00:23:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 srG7WQcexxWn for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 00:23:10 -0800 (PST)
Received: from mail-wi0-x22f.google.com (mail-wi0-x22f.google.com [IPv6:2a00:1450:400c:c05::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 747361A700E for <homenet@ietf.org>; Fri, 20 Feb 2015 00:23:10 -0800 (PST)
Received: by mail-wi0-f175.google.com with SMTP id r20so1231223wiv.2 for <homenet@ietf.org>; Fri, 20 Feb 2015 00:23:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=wWrfgrNtDTkMwFm95wVKogd1FEucup5/zc85wsDIDtY=; b=CnBYHonxhVNDxfC2ZGj60pF05u4xNxHZiTEEY/iy0FXhavYVCSHIIri26jqmUiN9fq nunFat+49NmiaPT3zme/YVyrEwWaVBnIpakp6qKBL/hnTDZvTCuVBRNG1Nzjt3ke7BpV LU0RWRTw7yp3PtUCzH0yR4h3ZYW9N24VFhvjY3dNvonwZjeVOe9alXsMgzzO6fwVffd+ 0yhpZ7Go0yfewl34CKcT3xnohdoC6QlaWjcrugJUjIWzSl0jJTn8VvFWrdbz0m0sPG/8 +rqqukOT7bUOC2PZ6mLLtG0STqDAXB6kCdOLCPQqrKj/tNKGqssUPlDK2p6laWlqwuCv ys6w==
X-Received: by 10.180.107.198 with SMTP id he6mr13307948wib.21.1424420588923;  Fri, 20 Feb 2015 00:23:08 -0800 (PST)
MIME-Version: 1.0
Received: by 10.27.77.212 with HTTP; Fri, 20 Feb 2015 00:22:48 -0800 (PST)
In-Reply-To: <FA70CC1E-37E4-4824-A9F3-9711F1F84777@inf-net.nl>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <A5767F83-3D0C-40E5-A73B-912E3C160A42@fugue.com> <alpine.DEB.2.02.1502191235240.4007@uplift.swm.pp.se> <87zj89gaqm.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191804050.4007@uplift.swm.pp.se> <D10B8924.6BD5%John_Leddy@cable.comcast.com> <87h9uhg529.wl-jch@pps.univ-paris-diderot.fr> <87fva1fzwp.wl-jch@pps.univ-paris-diderot.fr> <CAA93jw57sNMPsKkL-W2m3s20DKsFZWNeGZSOgnmRTj3yz+Rgmg@mail.gmail.com> <EA20D83F-3E46-4484-AD65-518B1C3836DA@inf-net.nl> <87zj89ed6c.wl-jch@pps.univ-paris-diderot.fr> <86026D9A-78BB-4E5B-A6AA-27FB2E02441F@inf-net.nl> <CAGnRvuobcSA1wP__rscE+UAMAuxEgOqML5Ute1qcFLSHh+kLng@mail.gmail.com> <FA70CC1E-37E4-4824-A9F3-9711F1F84777@inf-net.nl>
From: Henning Rogge <hrogge@gmail.com>
Date: Fri, 20 Feb 2015 09:22:48 +0100
Message-ID: <CAGnRvuqUSXpTPCqG4fsNHA=tsge=FvUUXuouwoVsRy1Cw3-cug@mail.gmail.com>
To: Teco Boot <teco@inf-net.nl>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/d8uWdh1a-JkB-7ikvAyG07Pih8c>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] More about marginal links [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 08:23:12 -0000

On Fri, Feb 20, 2015 at 9:19 AM, Teco Boot <teco@inf-net.nl> wrote:
>> There is also the "linklayer database" approach I selected for my
>> olsrd2 implementation. Instead of hardcoding linklayer specific code
>> into the metric, I split the codebase into "link layer gathering" code
>> (which is often OS and linklayer specific), generic routing metric
>> code... and a generic API in between that stores the values.
>>
>> This makes it quite easy to adapt the codebase to new linklayer types.
>>
>
> So you have the placeholder for an automatic ethernet link speed detectio=
n. Great!
>
> We cannot trust ethernet port L2 feedback. Ports can be connected to swit=
ches with multi-rate ports. Could be powerline, wired_over_wireless bridges=
 or other stuff that hides a slow link. In homes, there is no place for pro=
tocols that cannot detect and handle such cases.

At the moment I just get the ethernet port link speed... that is not
really good for switched ports, but its better than nothing.
http://olsr.org/git/?p=3Doonf.git;a=3Dblob;f=3Dsrc-plugins/generic/eth_list=
ener/eth_listener.c;h=3D1646a60722d60c54d7ab6b5df2e67fba7d52de22;hb=3Dmaste=
r

If you have hardware with a built-in switch that can report the
link-speed, it would be easy to add code that integrates this (and
some traffic statistics).

Henning Rogge


From nobody Fri Feb 20 00:51:58 2015
Return-Path: <teco@inf-net.nl>
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 F1C3C1A86FE for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 00:51:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 sKZpZBz0WjUN for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 00:51:54 -0800 (PST)
Received: from mail-we0-f175.google.com (mail-we0-f175.google.com [74.125.82.175]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5023E1A86F6 for <homenet@ietf.org>; Fri, 20 Feb 2015 00:51:53 -0800 (PST)
Received: by wesx3 with SMTP id x3so4325799wes.6 for <homenet@ietf.org>; Fri, 20 Feb 2015 00:51:52 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=er9N2af8aW4Tmd/nMKCwG23DLDxuvCMHTZ92vdWufCc=; b=aPaAIR26E27iQTS7MK43LaImFk5d6J3/FYAfbtB2GkHdVETnPEmr7vqrYnoEbjtbKn 355n20fJJDL6BeUZYgszrvHGK/n8HzkZ9SxRFOdHOhM5swCOuzFU4QVZmUSbxLxexMAp vnAgg2G2BlrE+3S5u72IDuaaMjLDm5h9Mozz+wKPSvs8++V1S64uj1XPdcrKTZSCNNul aIc8L2OYJuKWVdg0bF4A6fT4rvVoNP0ss9q/yfys52tfTHBdlTKf/IKTZa4mKfJNR7AO YgHBR34CDagRseK+dxAWdPHMSWJR/Kl1U898HRTD6JbH6c/Lc49fVMAf6HzspJPAxZJi mSaQ==
X-Gm-Message-State: ALoCoQnOsEn+PoZWnzUyvjaqEbBpPWBQGZerYyIAGWaGxkDNXONdG1aPCKsez8M47zgiKoejRTay
X-Received: by 10.194.52.66 with SMTP id r2mr16282648wjo.61.1424422312346; Fri, 20 Feb 2015 00:51:52 -0800 (PST)
Received: from [192.168.178.95] (524A158D.cm-4-3a.dynamic.ziggo.nl. [82.74.21.141]) by mx.google.com with ESMTPSA id m9sm1333003wiz.24.2015.02.20.00.51.50 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 20 Feb 2015 00:51:51 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Teco Boot <teco@inf-net.nl>
In-Reply-To: <CAGnRvuqUSXpTPCqG4fsNHA=tsge=FvUUXuouwoVsRy1Cw3-cug@mail.gmail.com>
Date: Fri, 20 Feb 2015 09:51:49 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <F6C723B4-7BBE-4C58-9476-2BD74F920C64@inf-net.nl>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <A5767F83-3D0C-40E5-A73B-912E3C160A42@fugue.com> <alpine.DEB.2.02.1502191235240.4007@uplift.swm.pp.se> <87zj89gaqm.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191804050.4007@uplift.swm.pp.se> <D10B8924.6BD5%John_Leddy@cable.comcast.com> <87h9uhg529.wl-jch@pps.univ-paris-diderot.fr> <87fva1fzwp.wl-jch@pps.univ-paris-diderot.fr> <CAA93jw57sNMPsKkL-W2m3s20DKsFZWNeGZSOgnmRTj3yz+Rgmg@mail.gmail.com> <EA20D83F-3E46-4484-AD65-518B1C3836DA@inf-net.nl> <87zj89ed6c.wl-jch@pps.univ-paris-diderot.fr> <86026D9A-78BB-4E5B-A6AA-27FB2E02441F@inf-net.nl> <CAGnRvuobcSA1wP__rscE+UAMAuxEgOqML5Ute1qcFLSHh+kLng@mail.gmail.com> <FA70CC1E-37E4-4824-A9F3-9711F1F84777@inf-net.nl> <CAGnRvuqUSXpTPCqG4fsNHA=tsge=FvUUXuouwoVsRy1Cw3-cug@mail.gmail.com>
To: Henning Rogge <hrogge@gmail.com>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/MIq71YjwcvRM8qs8v7gTFBfISjo>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] More about marginal links [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 08:51:57 -0000

> Op 20 feb. 2015, om 09:22 heeft Henning Rogge <hrogge@gmail.com> het =
volgende geschreven:
>=20
> On Fri, Feb 20, 2015 at 9:19 AM, Teco Boot <teco@inf-net.nl> wrote:
>>> There is also the "linklayer database" approach I selected for my
>>> olsrd2 implementation. Instead of hardcoding linklayer specific code
>>> into the metric, I split the codebase into "link layer gathering" =
code
>>> (which is often OS and linklayer specific), generic routing metric
>>> code... and a generic API in between that stores the values.
>>>=20
>>> This makes it quite easy to adapt the codebase to new linklayer =
types.
>>>=20
>>=20
>> So you have the placeholder for an automatic ethernet link speed =
detection. Great!
>>=20
>> We cannot trust ethernet port L2 feedback. Ports can be connected to =
switches with multi-rate ports. Could be powerline, wired_over_wireless =
bridges or other stuff that hides a slow link. In homes, there is no =
place for protocols that cannot detect and handle such cases.
>=20
> At the moment I just get the ethernet port link speed... that is not
> really good for switched ports, but its better than nothing.
> =
http://olsr.org/git/?p=3Doonf.git;a=3Dblob;f=3Dsrc-plugins/generic/eth_lis=
tener/eth_listener.c;h=3D1646a60722d60c54d7ab6b5df2e67fba7d52de22;hb=3Dmas=
ter
>=20
> If you have hardware with a built-in switch that can report the
> link-speed, it would be easy to add code that integrates this (and
> some traffic statistics).

Your SW depends on ethtool, right? Not a problem, this is implementation =
detail. Link speed probes could be added for verification the ethtool =
provided info.

And yes, I didn't mean we cannot use the 80% solution. What I want to =
say is that the Homenet Routing Protocol shall be able to use all the =
link metrics it can get.

I am still worried about loops caused by dynamic link metrics used by a =
link state routing protocol. For me, this is the major difference =
between ISIS and Babel. Thats because I don't code the protocol. If I =
was, I would be worried about the non-IP transport in ISIS.=20

Teco



From nobody Fri Feb 20 00:54:43 2015
Return-Path: <hrogge@gmail.com>
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 546211A86FB for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 00:54:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 NHxNk0bN_3CC for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 00:54:39 -0800 (PST)
Received: from mail-wi0-x232.google.com (mail-wi0-x232.google.com [IPv6:2a00:1450:400c:c05::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 578871A86F8 for <homenet@ietf.org>; Fri, 20 Feb 2015 00:54:39 -0800 (PST)
Received: by mail-wi0-f178.google.com with SMTP id em10so1367174wid.5 for <homenet@ietf.org>; Fri, 20 Feb 2015 00:54:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=+Gwq7XNOYS76T8PMQk9wLdF90/3icHlqUO2UT6lJn+A=; b=Y7bHO4qMiIvHUlkCnTwcZXN+KZXcfc+EgELpeg00xQj+hEC9/ZNqQ1OtNiCDV14UtS ukH+JpzUGWi+s2cdjDGpXdUNVRVAGDZtY0UuT1vb8KZSp+aGahJsGTB7qBrtYBq+dQ4j rxj14/qz4eaZ/p6ir1EPlNVX1QzdRV0UyojnMmxn/pIvh25zDWxmNtn7wwN27JkIIvJJ SDtmAYj6sFAimTtgQwSERwvHeBy3YMtTiNMYRSushp6T9X29v2NRHamrbCZZyNqTDepe shRtJJpgl/B80BIVwpq248EyWu6t2519jumqF7JhlPhT67GmJf5+lsQu/8XGirUrFmIR nISg==
X-Received: by 10.180.36.174 with SMTP id r14mr13479629wij.93.1424422478091; Fri, 20 Feb 2015 00:54:38 -0800 (PST)
MIME-Version: 1.0
Received: by 10.27.77.212 with HTTP; Fri, 20 Feb 2015 00:54:17 -0800 (PST)
In-Reply-To: <F6C723B4-7BBE-4C58-9476-2BD74F920C64@inf-net.nl>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <A5767F83-3D0C-40E5-A73B-912E3C160A42@fugue.com> <alpine.DEB.2.02.1502191235240.4007@uplift.swm.pp.se> <87zj89gaqm.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191804050.4007@uplift.swm.pp.se> <D10B8924.6BD5%John_Leddy@cable.comcast.com> <87h9uhg529.wl-jch@pps.univ-paris-diderot.fr> <87fva1fzwp.wl-jch@pps.univ-paris-diderot.fr> <CAA93jw57sNMPsKkL-W2m3s20DKsFZWNeGZSOgnmRTj3yz+Rgmg@mail.gmail.com> <EA20D83F-3E46-4484-AD65-518B1C3836DA@inf-net.nl> <87zj89ed6c.wl-jch@pps.univ-paris-diderot.fr> <86026D9A-78BB-4E5B-A6AA-27FB2E02441F@inf-net.nl> <CAGnRvuobcSA1wP__rscE+UAMAuxEgOqML5Ute1qcFLSHh+kLng@mail.gmail.com> <FA70CC1E-37E4-4824-A9F3-9711F1F84777@inf-net.nl> <CAGnRvuqUSXpTPCqG4fsNHA=tsge=FvUUXuouwoVsRy1Cw3-cug@mail.gmail.com> <F6C723B4-7BBE-4C58-9476-2BD74F920C64@inf-net.nl>
From: Henning Rogge <hrogge@gmail.com>
Date: Fri, 20 Feb 2015 09:54:17 +0100
Message-ID: <CAGnRvuq5y0thhQD4FK30710vDnKz1OdvJYq5JBsnGJ2Jq9UnSA@mail.gmail.com>
To: Teco Boot <teco@inf-net.nl>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/8-36ejx-HaeWvaJqRz9EWyL7dKQ>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] More about marginal links [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 08:54:41 -0000

On Fri, Feb 20, 2015 at 9:51 AM, Teco Boot <teco@inf-net.nl> wrote:
>> At the moment I just get the ethernet port link speed... that is not
>> really good for switched ports, but its better than nothing.
>> http://olsr.org/git/?p=3Doonf.git;a=3Dblob;f=3Dsrc-plugins/generic/eth_l=
istener/eth_listener.c;h=3D1646a60722d60c54d7ab6b5df2e67fba7d52de22;hb=3Dma=
ster
>>
>> If you have hardware with a built-in switch that can report the
>> link-speed, it would be easy to add code that integrates this (and
>> some traffic statistics).
>
> Your SW depends on ethtool, right? Not a problem, this is implementation =
detail. Link speed probes could be added for verification the ethtool provi=
ded info.

No, it does directly call into the operation system. Calling a
different executable and parsing the output is a good source for
subtle bugs.

> And yes, I didn't mean we cannot use the 80% solution. What I want to say=
 is that the Homenet Routing Protocol shall be able to use all the link met=
rics it can get.
>
> I am still worried about loops caused by dynamic link metrics used by a l=
ink state routing protocol. For me, this is the major difference between IS=
IS and Babel. Thats because I don't code the protocol. If I was, I would be=
 worried about the non-IP transport in ISIS.

It is a matter of metric stability... so you need a good hysteresis
and post-processing to make it work.

Henning Rogge


From nobody Fri Feb 20 01:11:28 2015
Return-Path: <teco@inf-net.nl>
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 850261A8720 for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 01:11:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 o2eLXV0Ni_61 for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 01:11:25 -0800 (PST)
Received: from mail-we0-f172.google.com (mail-we0-f172.google.com [74.125.82.172]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 853A51A872A for <homenet@ietf.org>; Fri, 20 Feb 2015 01:11:20 -0800 (PST)
Received: by wesx3 with SMTP id x3so4413833wes.6 for <homenet@ietf.org>; Fri, 20 Feb 2015 01:11:19 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=JusDFr+2YDnEX2qx33mLpGKb/Yqjn+C2IqHUgC4w0+E=; b=SXi3nlIqXrVQym1bH3wp6Haplac+21h//mm4NDE+UIjiRS3xsf5l2Eb3H9QWAO5MQg jFQpFqsBtsOowz67flTrJEUxVj6TcB4O24GrU2sZidj0Surd7Tlp3Lo06pC4S0qDAx6V 5DzJroRbAC92MwfR5+wJ5TzkitWrUJ42ECgVxB4lqENQxPTfHiZRTiZLvS+4a2pniGAs n5giDkCmjhhieCBX/VKyG47a/OK9ynJ51+2wQ9t5/+OHmSrlmr0hEnTqhzJujRmhNjoN jaIvDyXfmqHsTknQ3Kcno55PyYP8mJgnSc/gwYMRKG7z04vCw5GqW6cf2pQPdDTpPfQB m+9g==
X-Gm-Message-State: ALoCoQkdFMGKnJTJELkt3RxKnXbHRj7yaisZwkS5f+GnvlVzbbW02BWuELaWXn9hMKHE+hXZWxnD
X-Received: by 10.180.7.131 with SMTP id j3mr17935423wia.55.1424423479030; Fri, 20 Feb 2015 01:11:19 -0800 (PST)
Received: from [192.168.178.95] (524A158D.cm-4-3a.dynamic.ziggo.nl. [82.74.21.141]) by mx.google.com with ESMTPSA id ch6sm41132633wjc.3.2015.02.20.01.11.17 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 20 Feb 2015 01:11:18 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Teco Boot <teco@inf-net.nl>
In-Reply-To: <CAGnRvuq5y0thhQD4FK30710vDnKz1OdvJYq5JBsnGJ2Jq9UnSA@mail.gmail.com>
Date: Fri, 20 Feb 2015 10:11:16 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <D05C9636-0F10-42DE-A30E-7444FE4DFF92@inf-net.nl>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <A5767F83-3D0C-40E5-A73B-912E3C160A42@fugue.com> <alpine.DEB.2.02.1502191235240.4007@uplift.swm.pp.se> <87zj89gaqm.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191804050.4007@uplift.swm.pp.se> <D10B8924.6BD5%John_Leddy@cable.comcast.com> <87h9uhg529.wl-jch@pps.univ-paris-diderot.fr> <87fva1fzwp.wl-jch@pps.univ-paris-diderot.fr> <CAA93jw57sNMPsKkL-W2m3s20DKsFZWNeGZSOgnmRTj3yz+Rgmg@mail.gmail.com> <EA20D83F-3E46-4484-AD65-518B1C3836DA@inf-net.nl> <87zj89ed6c.wl-jch@pps.univ-paris-diderot.fr> <86026D9A-78BB-4E5B-A6AA-27FB2E02441F@inf-net.nl> <CAGnRvuobcSA1wP__rscE+UAMAuxEgOqML5Ute1qcFLSHh+kLng@mail.gmail.com> <FA70CC1E-37E4-4824-A9F3-9711F1F84777@inf-net.nl> <CAGnRvuqUSXpTPCqG4fsNHA=tsge=FvUUXuouwoVsRy1Cw3-cug@mail.gmail.com> <F6C723B4-7BBE-4C58-9476-2BD74F920C64@inf-net.nl> <CAGnRvuq5y0thhQD4FK30710vDnKz1OdvJYq5JBsnGJ2Jq9UnSA@mail.gmail.com>
To: Henning Rogge <hrogge@gmail.com>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/4AxEK2Sa_gKhoREl-sJ8yZTmCro>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] More about marginal links [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 09:11:27 -0000

> Op 20 feb. 2015, om 09:54 heeft Henning Rogge <hrogge@gmail.com> het =
volgende geschreven:
>=20
> On Fri, Feb 20, 2015 at 9:51 AM, Teco Boot <teco@inf-net.nl> wrote:
>>> At the moment I just get the ethernet port link speed... that is not
>>> really good for switched ports, but its better than nothing.
>>> =
http://olsr.org/git/?p=3Doonf.git;a=3Dblob;f=3Dsrc-plugins/generic/eth_lis=
tener/eth_listener.c;h=3D1646a60722d60c54d7ab6b5df2e67fba7d52de22;hb=3Dmas=
ter
>>>=20
>>> If you have hardware with a built-in switch that can report the
>>> link-speed, it would be easy to add code that integrates this (and
>>> some traffic statistics).
>>=20
>> Your SW depends on ethtool, right? Not a problem, this is =
implementation detail. Link speed probes could be added for verification =
the ethtool provided info.
>=20
> No, it does directly call into the operation system. Calling a
> different executable and parsing the output is a good source for
> subtle bugs.

Great.

>=20
>> And yes, I didn't mean we cannot use the 80% solution. What I want to =
say is that the Homenet Routing Protocol shall be able to use all the =
link metrics it can get.
>>=20
>> I am still worried about loops caused by dynamic link metrics used by =
a link state routing protocol. For me, this is the major difference =
between ISIS and Babel. Thats because I don't code the protocol. If I =
was, I would be worried about the non-IP transport in ISIS.
>=20
> It is a matter of metric stability... so you need a good hysteresis
> and post-processing to make it work.

I wonder. If the change hits the hysteresis threshold, two actions will =
happen. SPF calculation is triggered and routes may change. This would =
take place in sub-ms. The other action is sending link state to =
neighbors or flood over the whole network. That takes time, especially =
when there is no triggered update, there are some packets queued, there =
is a shared medium with timer based media access etc. Meanwhile, the =
topology is not guaranteed to be loop-free. Little you can do on the =
node itself. OK, we have the enterprise/ISP loop avoidance mechanisms, =
but to reuse this in homenet? Deploy this year?

I highly appreciate your work on olsrd/olsrd2, of course !!

Teco



From nobody Fri Feb 20 01:57:31 2015
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 549141A877B for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 01:57:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.661
X-Spam-Level: 
X-Spam-Status: No, score=-1.661 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 lGLUBPanhNgi for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 01:57:28 -0800 (PST)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E3C081A877A for <homenet@ietf.org>; Fri, 20 Feb 2015 01:57:27 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 6602FA5; Fri, 20 Feb 2015 10:57:24 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1424426244; bh=YZnLlfLZWxaEugg8ndZQZw6TpZfzsqv2aFcbx1Qr3W0=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=EIqfybLY9eoRN2N207YRt7rc8HuxXs1qLbWw9JU1LcuRgqTzvYvJ+6kDqM4gLGIP2 cPTUeegtJzhESpcinM9zvpbvTaAZJOweqkuOVTToUjiZe1CULju1RTE443k6TDJ4eH D0gGSrgFbOIwxvq2RugnzXoohWqtpz5/jzOqpNDM=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 5FE54A4; Fri, 20 Feb 2015 10:57:24 +0100 (CET)
Date: Fri, 20 Feb 2015 10:57:24 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Andrew Mcgregor <andrewmcgr@google.com>
In-Reply-To: <CAPRuP3mpNJTu6mP+RAVKKO0kt60PogNtNbCUCRRqxe9im3EzjA@mail.gmail.com>
Message-ID: <alpine.DEB.2.02.1502201042330.4007@uplift.swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <8B98F698-983D-4D2A-B5D1-7ACED27C275E@fugue.com> <alpine.DEB.2.02.1502191920560.4007@uplift.swm.pp.se> <CAPRuP3mpNJTu6mP+RAVKKO0kt60PogNtNbCUCRRqxe9im3EzjA@mail.gmail.com>
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/LHk4abRlcnkJN1B4toKRdBCWIJs>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 09:57:30 -0000

On Fri, 20 Feb 2015, Andrew Mcgregor wrote:

> Why?  PIM and MLD snooping are pretty standard on very low-end 
> enterprise switches, which will be next year's midrange consumer models. 
> If the dumb-as-rocks stuff goes away, that would generally make people 
> happier.

There are enterprise switches out there currently (pretty expensive ones) 
that still do not have MLD snooping, and the ones having PIM snooping is 
most likely a lot less. I've been in the networking industry for close to 
20 years, the first "bridge" I laid hands on was a pretty advanced thing 
back in the time with 3 AUI ports, and could barely do 10 megabit/s. I've 
then seen the evolution into 100meg hubs, then 10/100 dual speed hubs 
(basically two hubs with a switch in between), to 10/100 switches with all 
ports switched, to gig equivalent etc. During this entire time, switches 
that could do IGMP snooping has always been substantially more expensive, 
mostly (I guess) they couldn't be implemented in pure switch silicon, but 
always required administration interface, operating system etc. Still 
today, these typically cost 100 USD or more, when you can buy a stupid one 
for 30USD. So yes, over time this might change, but I still think there 
will be cost involved. It might be that the homenet "routers" are going to 
look quite different than the typical router we see today when it comes to 
phsyical ports. Or perhaps they're only going to have 2-3 ports and the 
rest is going to be wifi. What do I know.

What I do know is that so far, cable has always been a lot better than 
radio. Lots of support calls to ISPs end up being related to wifi 
problems. I have CAT6 to every room in my apartment, but then again, I am 
not a typical user. However, I often speak to people who have performance 
problems who then end up pulling a physical cable and after that their 
problems are solved.

With 60GHz wifi, you're going to need line-of-sight to every AP from the 
clients, which will probably be located in the ceiling in every room where 
you want good performance. These APs are going to need physical cables for 
uplinks to get any meaningful bump in performance.

I have thought of this as mostly L3 network. I thought the service 
discovery problem between subnets was being solved or had been solved. 
>From the discussion here the past few days it's clear to me now that the 
mind image of what a future homenet is differs a lot between participants 
in this working group.

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


From nobody Fri Feb 20 04:00:44 2015
Return-Path: <teco@inf-net.nl>
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 211F41A8727 for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 04:00:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 JVlk8Kt4mvd8 for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 04:00:41 -0800 (PST)
Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 602341A1AC6 for <homenet@ietf.org>; Fri, 20 Feb 2015 03:53:05 -0800 (PST)
Received: by wesx3 with SMTP id x3so5166119wes.6 for <homenet@ietf.org>; Fri, 20 Feb 2015 03:53:04 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=mybzKlXE4JDwmy/YkGlfN66wc1W0GH+F2VedYzH4YzI=; b=H/JZk19H8st3Vksr6CJixn3Y8BrLoLQM2BPoyMyWx+y46SKelNqNV4vp+/gVLqhtcv /AeAJj105vJOtW3RVJe98J8TTa5nZCaVAr0hx0ihPDd4yeb3ecFKw7xBckvKR+fpu/qy Jj62A5Mc7ttdcCaLIQl/BAfa3ngN5pTfgqymB1lstuf4M+K1Vc6pJ0mH22mvy73gNNyQ FE9Smvp47oi3m28gi2QkxCDj6tIMLbhNeUWGr3TttGd4FgIKrKtTDqXVOGRu8qaqSFQy Te/Srp0G7ykK1nCpwpul726OLY2hLrEeqhc0mFG1imRMPq8h7tiEkMQaTaMOeZDX2DYN NkbQ==
X-Gm-Message-State: ALoCoQm1/Wx3ArTq9Gm/YCXhv2WdZyJl/Yl/P49W85Es6VSio+GHac6MNptOLpM8JLHPCZHtC0nI
X-Received: by 10.180.35.42 with SMTP id e10mr19134428wij.11.1424433184500; Fri, 20 Feb 2015 03:53:04 -0800 (PST)
Received: from [192.168.178.95] (524A158D.cm-4-3a.dynamic.ziggo.nl. [82.74.21.141]) by mx.google.com with ESMTPSA id fu1sm2078477wic.2.2015.02.20.03.53.02 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 20 Feb 2015 03:53:03 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Teco Boot <teco@inf-net.nl>
In-Reply-To: <alpine.DEB.2.02.1502201042330.4007@uplift.swm.pp.se>
Date: Fri, 20 Feb 2015 12:53:01 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <7A86BDC6-FF4B-49FF-B59C-BA1DEF463173@inf-net.nl>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <8B98F698-983D-4D2A-B5D1-7ACED27C275E@fugue.com> <alpine.DEB.2.02.1502191920560.4007@uplift.swm.pp.se> <CAPRuP3mpNJTu6mP+RAVKKO0kt60PogNtNbCUCRRqxe9im3EzjA@mail.gmail.com> <alpine.DEB.2.02.1502201042330.4007@uplift.swm.pp.se>
To: Mikael Abrahamsson <swmike@swm.pp.se>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/AXJivqYDZzpFMuAzlfDUQqjlNfs>
Cc: Andrew Mcgregor <andrewmcgr@google.com>, "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 12:00:44 -0000

> Op 20 feb. 2015, om 10:57 heeft Mikael Abrahamsson <swmike@swm.pp.se> =
het volgende geschreven:
>=20
> On Fri, 20 Feb 2015, Andrew Mcgregor wrote:
>=20
>> Why?  PIM and MLD snooping are pretty standard on very low-end =
enterprise switches, which will be next year's midrange consumer models. =
If the dumb-as-rocks stuff goes away, that would generally make people =
happier.
>=20
> There are enterprise switches out there currently (pretty expensive =
ones) that still do not have MLD snooping, and the ones having PIM =
snooping is most likely a lot less. I've been in the networking industry =
for close to 20 years, the first "bridge" I laid hands on was a pretty =
advanced thing back in the time with 3 AUI ports, and could barely do 10 =
megabit/s. I've then seen the evolution into 100meg hubs, then 10/100 =
dual speed hubs (basically two hubs with a switch in between), to 10/100 =
switches with all ports switched, to gig equivalent etc. During this =
entire time, switches that could do IGMP snooping has always been =
substantially more expensive, mostly (I guess) they couldn't be =
implemented in pure switch silicon, but always required administration =
interface, operating system etc. Still today, these typically cost 100 =
USD or more, when you can buy a stupid one for 30USD. So yes, over time =
this might change, but I still think there will be cost involved. It =
might be that the homenet "routers" are going to look quite different =
than the typical router we see today when it comes to phsyical ports. Or =
perhaps they're only going to have 2-3 ports and the rest is going to be =
wifi. What do I know.
>=20
> What I do know is that so far, cable has always been a lot better than =
radio. Lots of support calls to ISPs end up being related to wifi =
problems. I have CAT6 to every room in my apartment, but then again, I =
am not a typical user. However, I often speak to people who have =
performance problems who then end up pulling a physical cable and after =
that their problems are solved.
>=20
> With 60GHz wifi, you're going to need line-of-sight to every AP from =
the clients, which will probably be located in the ceiling in every room =
where you want good performance. These APs are going to need physical =
cables for uplinks to get any meaningful bump in performance.
>=20
> I have thought of this as mostly L3 network.

What I can add: the multicast snooping feature could be somewhat behind =
development and deployment of the standards and / or buggy. So some =
administrators switch off the snooping / rate limiting feature. I do.

L3 all the way to switch ports make the network more robust. But this =
requires L3 forwarding in hardware, multicast routing and adjustments in =
discovery protocols. Can all multicast forwarding be performed in =
hardware?

Do you have CAT6 to WiFi APs in every room? Can you share experience =
with moving WiFi devices?

Teco


> I thought the service discovery problem between subnets was being =
solved or had been solved.=20
>> =46rom the discussion here the past few days it's clear to me now =
that the=20
> mind image of what a future homenet is differs a lot between =
participants in this working group.
>=20
> --=20
> Mikael Abrahamsson    email: swmike@swm.pp.se
>=20
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet


From nobody Fri Feb 20 04:24:10 2015
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 C29841A036E for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 04:24:07 -0800 (PST)
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 aOnDTCdfUWcr for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 04:24:01 -0800 (PST)
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 DB79E1A88A3 for <homenet@ietf.org>; Fri, 20 Feb 2015 04:17:19 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id E4CB1A2; Fri, 20 Feb 2015 13:17:17 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1424434637; bh=QSjf+ZOOwyKKog24I2+z5pNmfCOsOXVqLU/kmOTyBEk=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=fVZviOxEEW1lIqWPrJ28ydSo7hP/8aiX2+Ygj45fwGWZOlShPfzSGa1ntGP8DPr8G OE8ggd2dmxGy8q/iS360cnu+byi8CV0vAeIyJFNH9DvOms9yT/CoZQGmcSBdwnYP2l QXb8Ofy3jsVca2uqyp9jcFXVZuWY9S8tdS15N8+8=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id DEB07A1; Fri, 20 Feb 2015 13:17:17 +0100 (CET)
Date: Fri, 20 Feb 2015 13:17:17 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Teco Boot <teco@inf-net.nl>
In-Reply-To: <7A86BDC6-FF4B-49FF-B59C-BA1DEF463173@inf-net.nl>
Message-ID: <alpine.DEB.2.02.1502201310050.4007@uplift.swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <8B98F698-983D-4D2A-B5D1-7ACED27C275E@fugue.com> <alpine.DEB.2.02.1502191920560.4007@uplift.swm.pp.se> <CAPRuP3mpNJTu6mP+RAVKKO0kt60PogNtNbCUCRRqxe9im3EzjA@mail.gmail.com> <alpine.DEB.2.02.1502201042330.4007@uplift.swm.pp.se> <7A86BDC6-FF4B-49FF-B59C-BA1DEF463173@inf-net.nl>
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/B9-4qQMtz4bccE5dR-VWZwUxfTI>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 12:24:07 -0000

On Fri, 20 Feb 2015, Teco Boot wrote:

> Do you have CAT6 to WiFi APs in every room? Can you share experience 
> with moving WiFi devices?

No, my apartment is covered by a single 5GHz AP in the center of the 
apartment.

I mainly use cabled connections for media players and similar devices 
since they work much better over full duplex gige than over wifi. If I 
just could go back to my 1ms RTT Internet access link, things would be a 
lot better because my current DOCSIS3 cable connection is a lot worse (for 
instance when it comes to RTT and PDV) than my previous connection I had 
at the previous apartment which was a lot more consistent.

I tend to use a CAT6 ethernet adapter in my laptop when I'm at my desk, 
even though both my AP and laptop has 802.11ac. Wifi is mostly used to 
handle mobile devices such as tablets and mobile phones.

My experience is that even with state of the art equipment, wifi still is 
not even close in quality of experience compared to cable, apart from very 
light use where it's still sufficient.

My experience with multiple APs (from other places) is that clients don't 
switch APs easily enough so they're seldom connected to the optimal AP.

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


From nobody Fri Feb 20 05:08:19 2015
Return-Path: <teco@inf-net.nl>
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 4C9381A8A16 for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 05:08:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 aVL8vVwL9RHA for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 05:08:16 -0800 (PST)
Received: from mail-wg0-f47.google.com (mail-wg0-f47.google.com [74.125.82.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CF8541A6EF8 for <homenet@ietf.org>; Fri, 20 Feb 2015 05:08:15 -0800 (PST)
Received: by mail-wg0-f47.google.com with SMTP id x12so13038050wgg.6 for <homenet@ietf.org>; Fri, 20 Feb 2015 05:08:14 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=6+7pz4UW9OWXsLNpHYZU0SHPwFy3ZozrDoA2EI6bxNw=; b=X6i/1v6gTcnxVV/Ta9OCeLrbYCrFp0NTpm8+F1zOFv1kqaNT4qTxMWEM89o6o4oDQx npIppOBfFb5MP6S+xaCcu3LuFMU1Hjljru5EeogttYODQaC2SuSCGgkfu2ZdfJoyPbgX L1BjiUuBF97lf61MvO0GL6u6P6gP4+whCfawgD1v3fpF3YifbqgQuM3hzK2ROtfLaum4 LubTAnIaKKAbIQIGTKFrgWX0MgGsM4mDu0alPgqKiSbHK3TmD75+XV5iVwPilz4mf41b qQ1CdGXM1oXx5ZJC8anGr4rz1JEGiEVVgU+OnuVd8sQ5Tdef4W5zn67ED3U5XizoY/is rOlw==
X-Gm-Message-State: ALoCoQmAmHj3P4N4vCYXKjSstcsH2d2RoBpG0qspWxxshQxLkFgaQDyVrnivMQwCZAiIB6+Z8yiR
X-Received: by 10.180.35.42 with SMTP id e10mr19730689wij.11.1424437693948; Fri, 20 Feb 2015 05:08:13 -0800 (PST)
Received: from [192.168.178.95] (524A158D.cm-4-3a.dynamic.ziggo.nl. [82.74.21.141]) by mx.google.com with ESMTPSA id fu1sm2355387wic.2.2015.02.20.05.08.12 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 20 Feb 2015 05:08:12 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Teco Boot <teco@inf-net.nl>
In-Reply-To: <alpine.DEB.2.02.1502201310050.4007@uplift.swm.pp.se>
Date: Fri, 20 Feb 2015 14:08:11 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <09793905-8D12-49E0-A040-490F617C87FF@inf-net.nl>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <8B98F698-983D-4D2A-B5D1-7ACED27C275E@fugue.com> <alpine.DEB.2.02.1502191920560.4007@uplift.swm.pp.se> <CAPRuP3mpNJTu6mP+RAVKKO0kt60PogNtNbCUCRRqxe9im3EzjA@mail.gmail.com> <alpine.DEB.2.02.1502201042330.4007@uplift.swm.pp.se> <7A86BDC6-FF4B-49FF-B59C-BA1DEF463173@inf-net.nl> <alpine.DEB.2.02.1502201310050.4007@uplift.swm.pp.se>
To: Mikael Abrahamsson <swmike@swm.pp.se>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/Ru-77ZdomxOQ0ghJ4yYvEb1Vglk>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 13:08:18 -0000

Thanks sharing this.

What I can add:

Our house is a little bit bigger. It was formerly a farmhouse. It has a =
stone firewall between living room and formerly hay storage place. This =
firewall is quit good in blocking RF.

My "production" network has 2 dual band APs. I have good indoor =
coverage. In summertime, I use WiFi in my garden to watch live TV =
(iPhone, iPad, MacBook, Android gear). It is partly testing, partly =
following Tour de France, news etc. My partner is less a geek and =
carries the TV, coax and power cables. Still possible with some analogue =
channels. Soon we have to carry a lot more stuff to decode DTV, this is =
bad. Or watch over WiFi. I don't want to CAT6 my garden, sorry.

Walking from living room to desk to garden means AP switch-over.=20

I used to have 2.4 and 5GHz SSIDs, this doesn't work well. With exact =
same SSID and keys, handover works. Not well, but it works. With =
different SSIDs and different IP subnets: no, total failure.

There are WiFi AP kits around that operate in same channel and spoof AP =
BSSID. Roaming is transparent for clients. Nice idea, not accepted by =
standards bodies nor by industry.=20

Back to my point: I want L3 on each and every homenet box. At the same =
time, I want high performance wireless links. It must be cheap, I don't =
want to pay =E2=82=AC 1000 for a WLC and =E2=82=AC400 for each AP.

As long as homenet enlarges my WiFi problem, it is useless for me. And I =
thought I was candidate for early adoption, as I have multiple APs, a =
wired backbone, thinking of dual ISP links etc. And as geek, I want to =
pay a bit more for high performance and I am able to troubleshoot a bit.

Back to the subject: What are the requirements of a high performance =
WiFi home network to the homenet routing protocol? I guess we don't =
know.

Teco


> Op 20 feb. 2015, om 13:17 heeft Mikael Abrahamsson <swmike@swm.pp.se> =
het volgende geschreven:
>=20
> On Fri, 20 Feb 2015, Teco Boot wrote:
>=20
>> Do you have CAT6 to WiFi APs in every room? Can you share experience =
with moving WiFi devices?
>=20
> No, my apartment is covered by a single 5GHz AP in the center of the =
apartment.
>=20
> I mainly use cabled connections for media players and similar devices =
since they work much better over full duplex gige than over wifi. If I =
just could go back to my 1ms RTT Internet access link, things would be a =
lot better because my current DOCSIS3 cable connection is a lot worse =
(for instance when it comes to RTT and PDV) than my previous connection =
I had at the previous apartment which was a lot more consistent.
>=20
> I tend to use a CAT6 ethernet adapter in my laptop when I'm at my =
desk, even though both my AP and laptop has 802.11ac. Wifi is mostly =
used to handle mobile devices such as tablets and mobile phones.
>=20
> My experience is that even with state of the art equipment, wifi still =
is not even close in quality of experience compared to cable, apart from =
very light use where it's still sufficient.
>=20
> My experience with multiple APs (from other places) is that clients =
don't switch APs easily enough so they're seldom connected to the =
optimal AP.
>=20
> --=20
> Mikael Abrahamsson    email: swmike@swm.pp.se


From nobody Fri Feb 20 05:26:40 2015
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 C5D9D1A8BB1 for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 05:26:38 -0800 (PST)
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 0YzX9uNVEOkF for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 05:26:36 -0800 (PST)
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 6B3D91A8BB5 for <homenet@ietf.org>; Fri, 20 Feb 2015 05:22:13 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 04FC7A2; Fri, 20 Feb 2015 14:22:11 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1424438532; bh=Q1yoNtRppR+kGZ0h77i50zDyeTW7cznMceoru8bk9aI=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=WVxuXnbDhK2FKfBSKDtV8BaqWrc8a0PIS+P4/niSol9lvLUwS0jm77K3dgw56BGCb oM+xySOLCZaVWNlFKHsGZP/XpPgYosagCcmdI6dyEtNGLuuC3Xbt/WaFuL3DaWpxmg hBGW9lbuDgs5oaAEXB+1dd0AwkK0Td13U0cRXv0o=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id ED3F5A1; Fri, 20 Feb 2015 14:22:11 +0100 (CET)
Date: Fri, 20 Feb 2015 14:22:11 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Teco Boot <teco@inf-net.nl>
In-Reply-To: <09793905-8D12-49E0-A040-490F617C87FF@inf-net.nl>
Message-ID: <alpine.DEB.2.02.1502201410510.4007@uplift.swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <8B98F698-983D-4D2A-B5D1-7ACED27C275E@fugue.com> <alpine.DEB.2.02.1502191920560.4007@uplift.swm.pp.se> <CAPRuP3mpNJTu6mP+RAVKKO0kt60PogNtNbCUCRRqxe9im3EzjA@mail.gmail.com> <alpine.DEB.2.02.1502201042330.4007@uplift.swm.pp.se> <7A86BDC6-FF4B-49FF-B59C-BA1DEF463173@inf-net.nl> <alpine.DEB.2.02.1502201310050.4007@uplift.swm.pp.se> <09793905-8D12-49E0-A040-490F617C87FF@inf-net.nl>
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/gx6mZylEmmTZWpjnd1BEnwIXeRU>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 13:26:39 -0000

On Fri, 20 Feb 2015, Teco Boot wrote:

> Back to the subject: What are the requirements of a high performance 
> WiFi home network to the homenet routing protocol? I guess we don't 
> know.

Within the current framework to solve this problem with what exists today 
when it comes to clients, I would say we need either:

1. HNCP helps set up an overlay L2 tunnel infrastructure connecting all 
the APs using the same SSID, so the SSID can have the same L2 domain. This 
would probably mean we want to increase MTU on the physical links to avoid 
fragmentation. Messy. Possibly we could advertise lower MTU on the wifi 
network to minimize fragmentation if we don't raise MTU.

2. We set up some kind of L2 switching domain between the APs. This would 
require VLAN support in the HGWs, and something to set this up with loop 
avoidance etc. Oh oh oh, we could use IEEE 802.1aq that already uses ISIS 
as control plane, that way we could possibly run the same IGP for both L2 
and L3. Interconnecting APs over wifi seems weird though. Oh, and messy 
sounds like an understatement.

Frankly, I don't know how to solve this without a lot of complication.

We need clients to be able to change IPv6 addresses without losing 
existing connections. SHIM6 anyone? MP-TCP? Asking IEEE to make 802.11 
keep two connections at once and inform the application that one address 
is going away soon so it can do its thing to try to handle this?

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


From nobody Fri Feb 20 05:26:45 2015
Return-Path: <mellon@fugue.com>
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 53FAE1A8BB4 for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 05:26:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 UaRypEPnRi7D for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 05:26:39 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 15CAC1A8BB6 for <homenet@ietf.org>; Fri, 20 Feb 2015 05:23:03 -0800 (PST)
Received: from [10.0.20.107] (c-71-233-43-215.hsd1.nh.comcast.net [71.233.43.215]) by toccata.fugue.com (Postfix) with ESMTPSA id B73E7238059C; Fri, 20 Feb 2015 08:23:01 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <09793905-8D12-49E0-A040-490F617C87FF@inf-net.nl>
Date: Fri, 20 Feb 2015 08:22:14 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <CF1C246E-6F31-43C1-BADB-417CCDF008B4@fugue.com>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <8B98F698-983D-4D2A-B5D1-7ACED27C275E@fugue.com> <alpine.DEB.2.02.1502191920560.4007@uplift.swm.pp.se> <CAPRuP3mpNJTu6mP+RAVKKO0kt60PogNtNbCUCRRqxe9im3EzjA@mail.gmail.com> <alpine.DEB.2.02.1502201042330.4007@uplift.swm.pp.se> <7A86BDC6-FF4B-49FF-B59C-BA1DEF463173@inf-net.nl> <alpine.DEB.2.02.1502201310050.4007 @uplift.swm.pp.se> <09793905-8D12-49E0-A040-490F617C87FF@inf-net.nl>
To: Teco Boot <teco@inf-net.nl>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/QuzgZ9SEWWekyD6QfqcbatTlH2I>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 13:26:41 -0000

So Teco, to satisfy your use case, which I share, you would actually =
need the homenet to identify all Wifi access points that are being used =
to serve hosts, and treat those as a single subnet, correct?


From nobody Fri Feb 20 05:49:28 2015
Return-Path: <otroan@employees.org>
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 B3AD21A7D81 for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 05:49:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.011
X-Spam-Level: 
X-Spam-Status: No, score=-2.011 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 1NTf86uU7zeE for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 05:49:26 -0800 (PST)
Received: from banjo.employees.org (banjo.employees.org [IPv6:2001:1868:205::19]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D4F401A1A99 for <homenet@ietf.org>; Fri, 20 Feb 2015 05:49:25 -0800 (PST)
Received: from banjo.employees.org (localhost [127.0.0.1]) by banjo.employees.org (Postfix) with ESMTP id 8DDB261E9; Fri, 20 Feb 2015 05:49:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; s=selector1; bh=hcBIWHFCdyO17CteWTtj1U78FrI=; b= gFCd18tfEzGEf+sKjdhBCWcbIiifNDsBFhHguGwnhPJp0Rp4FU1lMllDvp+b7NGt 8ynhABgDOx1hPJh3oD8yrIrMEmLDzUU7RHvIzyTrExihIkJNRG7osyoWriuTaUYr sxYr7+xi2MABUIe1ugAYR+SbUHJ2dOqRmgB6L9t4tyg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; q=dns; s=selector1; b=DGPiV68n0OJUgDnQuZbRRatJxb BXai/TPACo0lKI0Ov2wmjVo1aa5XOf3Z/SLHPb3dmUI+6ofth+yDsEjP+K6qjF6s LH05I7mViLcPk6dq5eVlOiSgH6/99trLUjQxK1L8QbyMIV0wUHbie5X2hWG7DF83 Tp57qzTjLpyI2n5Z0=
Received: from gomlefisk.localdomain (173-38-208-169.cisco.com [173.38.208.169]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id 159A161CE; Fri, 20 Feb 2015 05:49:24 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by gomlefisk.localdomain (Postfix) with ESMTP id E27CF3F17AC9; Fri, 20 Feb 2015 14:49:21 +0100 (CET)
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_6CFB8689-3C62-4415-AD0C-4053CF9A10FE"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.5b5
From: Ole Troan <otroan@employees.org>
In-Reply-To: <alpine.DEB.2.02.1502201410510.4007@uplift.swm.pp.se>
Date: Fri, 20 Feb 2015 14:49:21 +0100
Message-Id: <82E892D5-98C3-4DD8-9E78-A754D77A5AF6@employees.org>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <8B98F698-983D-4D2A-B5D1-7ACED27C275E@fugue.com> <alpine.DEB.2.02.1502191920560.4007@uplift.swm.pp.se> <CAPRuP3mpNJTu6mP+RAVKKO0kt60PogNtNbCUCRRqxe9im3EzjA@mail.gmail.com> <alpine.DEB.2.02.1502201042330.4007@uplift.swm.pp.se> <7A86BDC6-FF4B-49FF-B59C-BA1DEF463173@inf-net.nl> <alpine.DEB.2.02.1502201310050.4007@uplift.swm.pp.se> <09793905-8D12-49E0-A040-490F617C87FF@inf-net.nl> <alpine.DEB.2.02.1502201410510.4007@upl ift.swm.pp.se>
To: Mikael Abrahamsson <swmike@swm.pp.se>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/ZDftVVXnYSAQGnE8uOYjcJCWy8I>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Teco Boot <teco@inf-net.nl>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 13:49:27 -0000

--Apple-Mail=_6CFB8689-3C62-4415-AD0C-4053CF9A10FE
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Mikael,

>> Back to the subject: What are the requirements of a high performance =
WiFi home network to the homenet routing protocol? I guess we don't =
know.
>=20
> Within the current framework to solve this problem with what exists =
today when it comes to clients, I would say we need either:
>=20
> 1. HNCP helps set up an overlay L2 tunnel infrastructure connecting =
all the APs using the same SSID, so the SSID can have the same L2 =
domain. This would probably mean we want to increase MTU on the physical =
links to avoid fragmentation. Messy. Possibly we could advertise lower =
MTU on the wifi network to minimize fragmentation if we don't raise MTU.
>=20
> 2. We set up some kind of L2 switching domain between the APs. This =
would require VLAN support in the HGWs, and something to set this up =
with loop avoidance etc. Oh oh oh, we could use IEEE 802.1aq that =
already uses ISIS as control plane, that way we could possibly run the =
same IGP for both L2 and L3. Interconnecting APs over wifi seems weird =
though. Oh, and messy sounds like an understatement.
>=20
> Frankly, I don't know how to solve this without a lot of complication.

why do you think this has to be solved at L2?

> We need clients to be able to change IPv6 addresses without losing =
existing connections. SHIM6 anyone? MP-TCP? Asking IEEE to make 802.11 =
keep two connections at once and inform the application that one address =
is going away soon so it can do its thing to try to handle this?

at least you can do:
L3 - route injection (got a routing protocol there already, use it)
L3.5 - SHIM6. not deployable
L4/L5 - MP-TCP
L5/L7  - MOSH

cheers,
Ole


--Apple-Mail=_6CFB8689-3C62-4415-AD0C-4053CF9A10FE
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJU5zthAAoJEFuJXizso86gK3IH/jZlQ41urQRKXhR/IZnTDkwC
eugrf1CXw4w/SQRwEXmPnMfRkc4fitjwdOLSUH0XcCqSJ8669v+qnvjOIcXgr2rS
BMqBvU/yA/g2Hw0+QuqOBqse2EuJS4X103OXcKiVBeIMoHYCSiCji7JbRBTu0orD
RB4Sk4raqPLZwbbtTjGDm8cyzPqMizSk28gO2I+UITdzcvRDdU4tulybAux9rXp8
YEPyHxPorOqo+uaTx/cA4Imgj1x59uVgANRhGQ6Syu0dWWYDR6l4DI5+XBmTANEB
LiZSdowWTIO/IrV/Ea6QwWOXkBQfqQr9UIKd92VmLOz3YUYXilOAJdmsMJjFJoc=
=JHAv
-----END PGP SIGNATURE-----

--Apple-Mail=_6CFB8689-3C62-4415-AD0C-4053CF9A10FE--


From nobody Fri Feb 20 05:50:24 2015
Return-Path: <teco@inf-net.nl>
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 739301A87BC for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 05:50:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 1zs10t9ezFO3 for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 05:50:18 -0800 (PST)
Received: from mail-wg0-f45.google.com (mail-wg0-f45.google.com [74.125.82.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F8E21A7D81 for <homenet@ietf.org>; Fri, 20 Feb 2015 05:50:18 -0800 (PST)
Received: by mail-wg0-f45.google.com with SMTP id k14so13302463wgh.4 for <homenet@ietf.org>; Fri, 20 Feb 2015 05:50:16 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=OGxckxqG3P4npbZ2vKi4rcY//FwUAm8oSn/KV+BYJ18=; b=OYQk5TQxZ24zgqIvxfHRqOrKgRHTh2ba+NCyPjEr9mfm9ZVEx1Fh9xpqZN5o6aLNuP ACHV056MfTFFDxnJ7QwNV7ZGJVl8eC+/9VKawJYvy04ksBqe+cNJPfU851789EYSTUZB KXbEKKUY2GgUDJup/A85AADTXPst99q1ENtbt2FKs8BbceUOIxHl5kpbfzSMXCSNIh2F pW6in5GzkwP9Mm/mZLhfIQ5rkA3fBKz7vaTeh8knK7nyHYi0EM5U20ThKCQD5ugeVuC/ 4qE1zT1ePbGDzDYeXHcsgKJqfHWNj2s83Mi9o+XGUSxx3+KYsNokzmx/OWFMbrEHok3w VoSA==
X-Gm-Message-State: ALoCoQkG/pS+XD5FWte+45223v5TpHUrMdNhE7mtJrT13DJDECzY5KvvnQvZfMls/j+HK9F/HSMW
X-Received: by 10.180.37.110 with SMTP id x14mr19699529wij.45.1424440215542; Fri, 20 Feb 2015 05:50:15 -0800 (PST)
Received: from [192.168.178.95] (524A158D.cm-4-3a.dynamic.ziggo.nl. [82.74.21.141]) by mx.google.com with ESMTPSA id n1sm2484016wib.11.2015.02.20.05.50.14 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 20 Feb 2015 05:50:14 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Teco Boot <teco@inf-net.nl>
In-Reply-To: <CF1C246E-6F31-43C1-BADB-417CCDF008B4@fugue.com>
Date: Fri, 20 Feb 2015 14:50:12 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <727DF526-F4CB-43C6-891F-4CEA38588AC1@inf-net.nl>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <8B98F698-983D-4D2A-B5D1-7ACED27C275E@fugue.com> <alpine.DEB.2.02.1502191920560.4007@uplift.swm.pp.se> <CAPRuP3mpNJTu6mP+RAVKKO0kt60PogNtNbCUCRRqxe9im3EzjA@mail.gmail.com> <alpine.DEB.2.02.1502201042330.4007@uplift.swm.pp.se> <7A86BDC6-FF4B-49FF-B59C-BA1DEF463173@inf-net.nl> <alpine.DEB.2.02.1502201310050.4007 @uplift.swm.pp.se> <09793905-8D12-49E0-A040-490F617C87FF@inf-net.nl> <CF1C246E-6F31-43C1-BADB-417CCDF008B4@fugue.com>
To: Ted Lemon <mellon@fugue.com>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/DbiW83jHZE3eWXL4m-9rdM-vOcA>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 13:50:23 -0000

> Op 20 feb. 2015, om 14:22 heeft Ted Lemon <mellon@fugue.com> het =
volgende geschreven:
>=20
> So Teco, to satisfy your use case, which I share, you would actually =
need the homenet to identify all Wifi access points that are being used =
to serve hosts, and treat those as a single subnet, correct?

Because I am not optimistic on deployment of mobility protocols in the =
home, my answer is yes. WiFi APs in same home has same SSID(s). Each =
SSID provides an IP subnet.

Providing multiple SSIDs should be in scope, with <my_home> and =
<my_guest> as default SSIDs. Both <my_home> and <my_guest> differ from =
my neighbors SSIDs.

Al least two directions for a solution:=20
 1) the WLAN controller with tunnels between the APs and the WLC.=20
 2) distribute the AP configuration for APs, either manually or guided =
by a homenet protocol. I hope we can circumvent VLANs in homenet. An =
alternative would be /128 prefix routing.

Whatever we choose, we have to keep in mind that dual stack operation =
will not fade away soon.

Teco




From nobody Fri Feb 20 05:57:26 2015
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 526D41A802E for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 05:57:24 -0800 (PST)
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 NS7JsewIpZsy for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 05:57:23 -0800 (PST)
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 C2D5B1A7D81 for <homenet@ietf.org>; Fri, 20 Feb 2015 05:57:22 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 57FADA2; Fri, 20 Feb 2015 14:57:21 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1424440641; bh=6ZKAcenxqKJ88GpWda5UGcLUVUfMC9fO2cSHTmc6xrE=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=Fqmn1C6C5ozpuVzrvoyZVhvj2r8NhoOKoaH/ziUPhBLhtiFA5IJZLN9r7JJgQRGQF hot+R6qjAQnxg/lTTvKMa2iykNkw1wDcOQV+fBtrlfGXKDZDbVDKQ/my3xk+7mN3sR fKl+EIAqV48xUgdAXDeuf7BJbqi5vhpI+2WWiAtE=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 50F01A1; Fri, 20 Feb 2015 14:57:21 +0100 (CET)
Date: Fri, 20 Feb 2015 14:57:21 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Ole Troan <otroan@employees.org>
In-Reply-To: <82E892D5-98C3-4DD8-9E78-A754D77A5AF6@employees.org>
Message-ID: <alpine.DEB.2.02.1502201455500.4007@uplift.swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <8B98F698-983D-4D2A-B5D1-7ACED27C275E@fugue.com> <alpine.DEB.2.02.1502191920560.4007@uplift.swm.pp.se> <CAPRuP3mpNJTu6mP+RAVKKO0kt60PogNtNbCUCRRqxe9im3EzjA@mail.gmail.com> <alpine.DEB.2.02.1502201042330.4007@uplift.swm.pp.se> <7A86BDC6-FF4B-49FF-B59C-BA1DEF463173@inf-net.nl> <alpine.DEB.2.02.1502201310050.4007@uplift.swm.pp.se> <09793905-8D12-49E0-A040-490F617C87FF@inf-net.nl> <alpine.DEB.2.02.1502201410510.4007@upl ift.swm.pp.se> <82E892D5-98C3-4DD8-9E78-A754D77A5AF6@employees.org>
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/1fbuwNPo7qQoyAV1U-u4MNtqKjc>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 13:57:24 -0000

On Fri, 20 Feb 2015, Ole Troan wrote:

>> Frankly, I don't know how to solve this without a lot of complication.
>
> why do you think this has to be solved at L2?

I don't that's why I wrote the next paragraph outlining L3 solutions.

>> We need clients to be able to change IPv6 addresses without losing existing connections. SHIM6 anyone? MP-TCP? Asking IEEE to make 802.11 keep two connections at once and inform the application that one address is going away soon so it can do its thing to try to handle this?
>
> at least you can do:
> L3 - route injection (got a routing protocol there already, use it)

This sounds like it needs at least a coordination protocol between the 
APs?

> L3.5 - SHIM6. not deployable
> L4/L5 - MP-TCP
> L5/L7  - MOSH

I would prefer the last two. I use MOSH all the time, it's great.

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


From nobody Fri Feb 20 06:15:21 2015
Return-Path: <mellon@fugue.com>
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 3C26C1A8759 for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 06:15:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 Oy6nSAr94wya for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 06:15:17 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 270C51A8A1D for <homenet@ietf.org>; Fri, 20 Feb 2015 06:15:05 -0800 (PST)
Received: from [10.0.20.107] (c-71-233-43-215.hsd1.nh.comcast.net [71.233.43.215]) by toccata.fugue.com (Postfix) with ESMTPSA id 2EF43238059C; Fri, 20 Feb 2015 09:15:03 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <alpine.DEB.2.02.1502201410510.4007@uplift.swm.pp.se>
Date: Fri, 20 Feb 2015 09:14:15 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <CC31C560-C688-448C-A296-8D8644DC0F84@fugue.com>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <8B98F698-983D-4D2A-B5D1-7ACED27C275E@fugue.com> <alpine.DEB.2.02.1502191920560.4007@uplift.swm.pp.se> <CAPRuP3mpNJTu6mP+RAVKKO0kt60PogNtNbCUCRRqxe9im3EzjA@mail.gmail.com> <alpine.DEB.2.02.1502201042330.4007@uplift.swm.pp.se> <7A86BDC6-FF4B-49FF-B59C-BA1DEF463173@inf-net.nl> <alpine.DEB.2.02.1502201310050.4007@uplift.swm.pp.se> <09793905-8D12-49E0-A040-490F617C87FF@inf-net.nl> <alpine.DEB.2.02.1502201410510. 4007@uplift.swm.pp.se>
To: Mikael Abrahamsson <swmike@swm.pp.se>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/6LSpELqtCPmXNE9ekjvuD0RK094>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Teco Boot <teco@inf-net.nl>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 14:15:20 -0000

On Feb 20, 2015, at 8:22 AM, Mikael Abrahamsson <swmike@swm.pp.se> =
wrote:
> 2. We set up some kind of L2 switching domain between the APs. This =
would require VLAN support in the HGWs, and something to set this up =
with loop avoidance etc. Oh oh oh, we could use IEEE 802.1aq that =
already uses ISIS as control plane, that way we could possibly run the =
same IGP for both L2 and L3. Interconnecting APs over wifi seems weird =
though. Oh, and messy sounds like an understatement.

Long ago I proposed using Trill to make this work, but nobody =
listened...

:)


From nobody Fri Feb 20 06:16:41 2015
Return-Path: <eckert@cisco.com>
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 186F01A8A1D for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 06:16:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 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_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 SMD83Ae1sdQD for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 06:16:36 -0800 (PST)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6B23F1A879A for <homenet@ietf.org>; Fri, 20 Feb 2015 06:16:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2485; q=dns/txt; s=iport; t=1424441797; x=1425651397; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=jgb63fLdRPSa32wdtTrqLnHCli2P3KqYxPGbkz4eSHY=; b=ZI8REJcbm9MKdh3daLoRlC8fafTOT3zUvPFjm8bqBMp1wqJNnDvtkXlJ Wxgyt91EJqLG7tkFQQMFNutCYFUrjThmqU/qQ1Gqph4IweHE0FkoW9X3/ zFEjpDMlt9PQm5CIQueBNV0fs28RsSXd8gh7/j/s3ebjvj5NCaAfAv2o2 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CVBQDBQOdU/40NJK1RCoMGUlrCagqFJ0oCgRhDAQEBAQEBfIQQAQEEAQEBNzQLEAsOCgklDwUTNhMbiBQN1CUBAQEBAQEBAQEBAQEBAQEBAQEBAQETBIsPhAwGCwFQB4MWgRQFikeORwGTKyKEDx0xgQuBOAEBAQ
X-IronPort-AV: E=Sophos;i="5.09,614,1418083200"; d="scan'208";a="397729588"
Received: from alln-core-8.cisco.com ([173.36.13.141]) by rcdn-iport-7.cisco.com with ESMTP; 20 Feb 2015 14:16:36 +0000
Received: from mcast-linux1.cisco.com (mcast-linux1.cisco.com [172.27.244.121]) by alln-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id t1KEGZJZ029819 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 20 Feb 2015 14:16:35 GMT
Received: from mcast-linux1.cisco.com (localhost.cisco.com [127.0.0.1]) by mcast-linux1.cisco.com (8.13.8/8.13.8) with ESMTP id t1KEGYbg009999; Fri, 20 Feb 2015 06:16:34 -0800
Received: (from eckert@localhost) by mcast-linux1.cisco.com (8.13.8/8.13.8/Submit) id t1KEGYYE009998; Fri, 20 Feb 2015 06:16:34 -0800
Date: Fri, 20 Feb 2015 06:16:34 -0800
From: Toerless Eckert <eckert@cisco.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Message-ID: <20150220141634.GB8096@cisco.com>
References: <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <8B98F698-983D-4D2A-B5D1-7ACED27C275E@fugue.com> <alpine.DEB.2.02.1502191920560.4007@uplift.swm.pp.se>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.DEB.2.02.1502191920560.4007@uplift.swm.pp.se>
User-Agent: Mutt/1.4.2.2i
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/wgfNnPbyqNw8noiOouihGyum4eU>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Ted Lemon <mellon@fugue.com>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 14:16:39 -0000

Snooping switches would certainly be a good reason to prefer MLD proxying
over PIM in homenet. There could be other reasons like reducing codeside
(thats Pierre pet reason ;-). But trying to be compatible with
snooping switches also implies that improvements in MLD that we might
wnat then for homenet would break interoperability with that L2 equipment,
because you must assume this L2 equipment will only correctly react to MLD
message and message sequences as they have been defined 8 years ago.

So foremost, it would be good to understand if there really is home
L2 equipment that MUST see MLD to operate correctly. Otherwise i'd
happily ignore the problem and say there is enough bandwidth to just NOT DO
snooping but have multicast be flooded in the L2 segments.

I only remember vaguely one old data point that seemed to indicate that
some powerline equipment was doing snooping and you couldn't switch it
off. can't find the pointers to this data point though. Would love to
know if any powerline standards exist and what they say about MLD...

Worst case, whatever the preferred solution for IP multicast is in
homenet, if we identify that there is L2 equipment that MUST get MLD,
we need to ALSO have homenet routers send out MLDv1/v2 backward
compatible MLD messages to keep that L2 equipment happy. That is also 
pretty much what we do in commercial environments too, for example in
satellite links where we really want to connect router-to-router 
signaling with PIM, but those routers are set up to ALSO send IGMP/MLD
to keep the satellite modems happy.

Toerless

On Thu, Feb 19, 2015 at 07:22:34PM +0100, Mikael Abrahamsson wrote:
> On Thu, 19 Feb 2015, Ted Lemon wrote:
> 
> >On Feb 19, 2015, at 1:08 PM, Mikael Abrahamsson <swmike@swm.pp.se> wrote:
> >>I would like my router-to-router links to not have a lot of hosts in them 
> >>if I can avoid it.
> >
> >Why is that?
> 
> If we're going to be routing multicast within the home, we're most likely 
> going to have to use some kind of variant of PIM. Asking the L2 switches 
> people connect to the router to support both PIM and MLD snooping seem 
> like it might be asking too much.
> 
> I might be wrong though.
> 
> -- 
> Mikael Abrahamsson    email: swmike@swm.pp.se
> 
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet

-- 
---
Toerless Eckert, eckert@cisco.com


From nobody Fri Feb 20 06:20:59 2015
Return-Path: <eckert@cisco.com>
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 386681A854D for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 06:20:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 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_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 bxPLLWpfYlSY for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 06:20:46 -0800 (PST)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 82B451A8759 for <homenet@ietf.org>; Fri, 20 Feb 2015 06:20:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=701; q=dns/txt; s=iport; t=1424442043; x=1425651643; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=Qg1hdz0cPTwhWHjf4sRMYy7nTykAOceEV8S6L2W644Y=; b=JqMguf1P+QG/r7gvrOXeLsYGcT6pekNf5Sn4Y9kCGrPzcMkQv9jszae4 R7MydWkdckbNehqpCLTbwXoXpvlmkG/tlPeeEyKTRSqipBQ+VcJDiHpG3 Y3mqN7fH6CEto0RbYSkguT2N6croxbqejjSoOcoc5zhpBfYlZY5RcKun5 M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BLBQAuQudU/4kNJK1bgwbKEQKBGEMBAQEBAQF8hBABAQQ6PxALDgoJJQ8FSS6IFNQ9AQEBAQEBAQEBAQEBAQEBAQEBAQEBF4sPhG4HgxaBFAEEikeORwGTKyKEDx2CdAEBAQ
X-IronPort-AV: E=Sophos;i="5.09,614,1418083200"; d="scan'208";a="125420754"
Received: from alln-core-4.cisco.com ([173.36.13.137]) by alln-iport-5.cisco.com with ESMTP; 20 Feb 2015 14:20:42 +0000
Received: from mcast-linux1.cisco.com (mcast-linux1.cisco.com [172.27.244.121]) by alln-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id t1KEKg3J025101 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 20 Feb 2015 14:20:42 GMT
Received: from mcast-linux1.cisco.com (localhost.cisco.com [127.0.0.1]) by mcast-linux1.cisco.com (8.13.8/8.13.8) with ESMTP id t1KEKfnO010264; Fri, 20 Feb 2015 06:20:41 -0800
Received: (from eckert@localhost) by mcast-linux1.cisco.com (8.13.8/8.13.8/Submit) id t1KEKfw0010263; Fri, 20 Feb 2015 06:20:41 -0800
Date: Fri, 20 Feb 2015 06:20:41 -0800
From: Toerless Eckert <eckert@cisco.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Message-ID: <20150220142041.GC8096@cisco.com>
References: <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <8B98F698-983D-4D2A-B5D1-7ACED27C275E@fugue.com> <alpine.DEB.2.02.1502191920560.4007@uplift.swm.pp.se> <CAPRuP3mpNJTu6mP+RAVKKO0kt60PogNtNbCUCRRqxe9im3EzjA@mail.gmail.com> <alpine.DEB.2.02.1502201042330.4007@uplift.swm.pp.se>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.DEB.2.02.1502201042330.4007@uplift.swm.pp.se>
User-Agent: Mutt/1.4.2.2i
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/_ul1v2ldaVQ1FRUCqp5UD_ij3pc>
Cc: Andrew Mcgregor <andrewmcgr@google.com>, "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 14:20:51 -0000

On Fri, Feb 20, 2015 at 10:57:24AM +0100, Mikael Abrahamsson wrote:
> I have thought of this as mostly L3 network. I thought the service 
> discovery problem between subnets was being solved or had been solved. 
> >From the discussion here the past few days it's clear to me now that the 
> mind image of what a future homenet is differs a lot between participants 
> in this working group.

There are good proposal how to do servicce discovery in homenets or
the like with DNS-SD (/mDNS), but i think we should still worry
about compatibility with UPnP. Both of these requirements 
(UPnP and DNS-SD) are IMHO better solved with router-level "proxy"
solutions than with ASM IP multicast. 


From nobody Fri Feb 20 06:38:07 2015
Return-Path: <bs7652@att.com>
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 481DA1A87DF for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 06:38:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level: 
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 TAZ2gRduNa6g for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 06:38:04 -0800 (PST)
Received: from nbfkord-smmo07.seg.att.com (nbfkord-smmo07.seg.att.com [209.65.160.93]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6D1221A87D1 for <homenet@ietf.org>; Fri, 20 Feb 2015 06:38:04 -0800 (PST)
Received: from unknown [144.160.229.23] (EHLO alpi154.enaf.aldc.att.com) by nbfkord-smmo07.seg.att.com(mxl_mta-7.2.4-5) with ESMTP id cc647e45.2b5e9a803940.2961118.00-2424.8364993.nbfkord-smmo07.seg.att.com (envelope-from <bs7652@att.com>);  Fri, 20 Feb 2015 14:38:04 +0000 (UTC)
X-MXL-Hash: 54e746cc2f22adf0-43e41d29f831618261676b8de8633480bbe12754
Received: from unknown [144.160.229.23] (EHLO alpi154.enaf.aldc.att.com) by nbfkord-smmo07.seg.att.com(mxl_mta-7.2.4-5) over TLS secured channel with ESMTP id 9b647e45.0.2960989.00-2122.8364607.nbfkord-smmo07.seg.att.com (envelope-from <bs7652@att.com>);  Fri, 20 Feb 2015 14:37:46 +0000 (UTC)
X-MXL-Hash: 54e746ba60013737-1d3cb55644dfa9c73d86208411467767bb1dc638
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id t1KEbia6018539; Fri, 20 Feb 2015 09:37:44 -0500
Received: from alpi132.aldc.att.com (alpi132.aldc.att.com [130.8.217.2]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id t1KEbfsb018532 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 20 Feb 2015 09:37:42 -0500
Received: from GAALPA1MSGHUBAD.ITServices.sbc.com (GAALPA1MSGHUBAD.itservices.sbc.com [130.8.218.153]) by alpi132.aldc.att.com (RSA Interceptor); Fri, 20 Feb 2015 14:37:38 GMT
Received: from GAALPA1MSGUSRBF.ITServices.sbc.com ([169.254.5.126]) by GAALPA1MSGHUBAD.ITServices.sbc.com ([130.8.218.153]) with mapi id 14.03.0224.002; Fri, 20 Feb 2015 09:37:38 -0500
From: "STARK, BARBARA H" <bs7652@att.com>
To: "'Toerless Eckert'" <eckert@cisco.com>, Mikael Abrahamsson <swmike@swm.pp.se>
Thread-Topic: [homenet] Routing protocol comparison document
Thread-Index: AQHQSU32GNhjW8WFi0qWgaveVMetmJz2sruAgAAaSQCAABl7AIAABlyAgAAB2ICAAHYtgIAAi9MAgACD2oCAAAHHgIAAAyGAgAAURoCAAA90gIAAAkAAgAABTQCAAAKJAIAAX5aAgAClmgCAAEmQgP//rgRw
Date: Fri, 20 Feb 2015 14:37:38 +0000
Message-ID: <2D09D61DDFA73D4C884805CC7865E61130F3035D@GAALPA1MSGUSRBF.ITServices.sbc.com>
References: <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <8B98F698-983D-4D2A-B5D1-7ACED27C275E@fugue.com> <alpine.DEB.2.02.1502191920560.4007@uplift.swm.pp.se> <CAPRuP3mpNJTu6mP+RAVKKO0kt60PogNtNbCUCRRqxe9im3EzjA@mail.gmail.com> <alpine.DEB.2.02.1502201042330.4007@uplift.swm.pp.se> <20150220142041.GC8096@cisco.com>
In-Reply-To: <20150220142041.GC8096@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.61.166.72]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-AnalysisOut: [v=2.0 cv=KNft+i5o c=1 sm=1 a=VXHOiMMwGAwA+y4G3/O+aw==:17 a]
X-AnalysisOut: [=vKzWRVGcsRAA:10 a=BLceEmwcHowA:10 a=kj9zAlcOel0A:10 a=zQP]
X-AnalysisOut: [7CpKOAAAA:8 a=XIqpo32RAAAA:8 a=0HtSIViG9nkA:10 a=48vgC7mUA]
X-AnalysisOut: [AAA:8 a=ZyAdMjAvPDAnrEWUhLEA:9 a=CjuIK1q_8ugA:10]
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2014051901)]
X-MAIL-FROM: <bs7652@att.com>
X-SOURCE-IP: [144.160.229.23]
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/DvIOxsnTAClfVVPCbqd8zW1ZiDQ>
Cc: Andrew Mcgregor <andrewmcgr@google.com>, "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 14:38:06 -0000

> There are good proposal how to do servicce discovery in homenets or the
> like with DNS-SD (/mDNS), but i think we should still worry about
> compatibility with UPnP. Both of these requirements (UPnP and DNS-SD) are
> IMHO better solved with router-level "proxy"
> solutions than with ASM IP multicast.

FYI. I did a presentation to DLNA (which has a lot of key UPnP people) that=
 warned them to start thinking about service discovery in the multi-router =
world, and the world where more and more Wi-Fi APs are limiting the multica=
st that makes it to Wi-Fi devices. I mentioned the DNS-SD proxy work, homen=
et, and told them:
" - People have started to study the current quantity of multicast traffic =
and its impact on power consumption by battery-operated Wi-Fi devices.
http://tools.ietf.org/html/draft-desmouceaux-ipv6-mcast-wifi-power-usage-00
http://tools.ietf.org/html/draft-vyncke-6man-mcast-not-efficient-00
 - Concern is growing and proposals are starting to appear for ways to decr=
ease the quantity of multicast messages.
http://tools.ietf.org/html/draft-yourtchenko-colitti-nd-reduce-multicast-00=
 "

My recommendations were that they had 2 basic options of either also suppor=
ting DNS-SD / mDNS for service discovery, or defining a SSDP proxy similar =
to what I expect will be done for DNS-SD. Anyway, I told them I'd keep them=
 updated on the state of affairs regarding this issue.
Barbara


From nobody Fri Feb 20 06:41:45 2015
Return-Path: <eckert@cisco.com>
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 7C0E31A8033 for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 06:41:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 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_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 4_HYup7f54Wa for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 06:41:41 -0800 (PST)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 513901A87DF for <homenet@ietf.org>; Fri, 20 Feb 2015 06:41:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2794; q=dns/txt; s=iport; t=1424443301; x=1425652901; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=NUsXSIQKLSdNeXMDe/R5A9JhkoESf4H8fPX7knFOwYw=; b=B2A+Ei10fV6adjoIQ12TipaR9DKR+vfJq+SHPGQctPPrzyQqT8Iq+VBK LUofmkqus73cPRFvVg8rux5dizKH7urzrBXBbITXXSCIQfZm0HFiMpt8O MC8YvH1u+VFE9J8CpFfgcPoJr7DOxRwO6eMu1FLZ/gyOTc+RYdy6cDT9M c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CVBQDYRudU/5RdJa1bgwZSWsJqCoUnSgKBGEMBAQEBAQF8hBABAQQBAQEkEzQLBQsLGAklDwUTNhOILw3UMAEBAQEBAQEBAQEBAQEBAQEBAQEBARMEiw+EDBEBUAeDFoEUBYpHgnaLUQGTKyKEDx0xgQuBOAEBAQ
X-IronPort-AV: E=Sophos;i="5.09,615,1418083200"; d="scan'208";a="125419269"
Received: from rcdn-core-12.cisco.com ([173.37.93.148]) by alln-iport-3.cisco.com with ESMTP; 20 Feb 2015 14:41:40 +0000
Received: from mcast-linux1.cisco.com (mcast-linux1.cisco.com [172.27.244.121]) by rcdn-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id t1KEfePT002549 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 20 Feb 2015 14:41:40 GMT
Received: from mcast-linux1.cisco.com (localhost.cisco.com [127.0.0.1]) by mcast-linux1.cisco.com (8.13.8/8.13.8) with ESMTP id t1KEfcsH011672; Fri, 20 Feb 2015 06:41:38 -0800
Received: (from eckert@localhost) by mcast-linux1.cisco.com (8.13.8/8.13.8/Submit) id t1KEfc9b011670; Fri, 20 Feb 2015 06:41:38 -0800
Date: Fri, 20 Feb 2015 06:41:38 -0800
From: Toerless Eckert <eckert@cisco.com>
To: Andrew Mcgregor <andrewmcgr@google.com>
Message-ID: <20150220144138.GD8096@cisco.com>
References: <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <8B98F698-983D-4D2A-B5D1-7ACED27C275E@fugue.com> <alpine.DEB.2.02.1502191920560.4007@uplift.swm.pp.se> <CAPRuP3mpNJTu6mP+RAVKKO0kt60PogNtNbCUCRRqxe9im3EzjA@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAPRuP3mpNJTu6mP+RAVKKO0kt60PogNtNbCUCRRqxe9im3EzjA@mail.gmail.com>
User-Agent: Mutt/1.4.2.2i
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/vbFhC531D6sODPUu-NrqtmmGPeQ>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Ted Lemon <mellon@fugue.com>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 14:41:43 -0000

I have seen more L2 switches that have broken IGMP/MLD snooping than
working ones. I am not aware of real proliferation of PIM snooping.
Snooping in transit LANs with PIM is a bad idea anyhow, and i have
tried to steer any customer who asked me away from it.

Bidir-PIM makes snooping particularily difficult. For once
you have to track DF-winner election messages (difficult) and
secondly you have to then flood all multicast to all DF winners
because you don't know which group-range is served by which RP.

IMHO, there is never enough multicast to justify this snooping complexity.
The only thing to worry about is what packets to send out from a router
to ensure the snooping doesn't screw up the traffic flow.

I would be surprised to find equipemnt that does PIM snooping by default.

So, i'd recommend to a homenet router:

-> even if you don't do PIM, send out PIM Hellos. This should
   effectively make all stupid "enterprise class" IGMP/MLD snooping
   switches (that often have broken IGMP/MLD snooping) send
   you all multicast traffic (inhibits snooping).

-> Still send MLD/IGMP memberships to get traffic through the
   L2 home equipment that has likely never heard about PIM.
   I'd guess that eg: powerline equipment falls into this
   category.

Cheers
    Toerless

On Fri, Feb 20, 2015 at 11:04:41AM +1100, Andrew Mcgregor wrote:
> Why?  PIM and MLD snooping are pretty standard on very low-end enterprise
> switches, which will be next year's midrange consumer models.  If the
> dumb-as-rocks stuff goes away, that would generally make people happier.
> 
> On 20 February 2015 at 05:22, Mikael Abrahamsson <swmike@swm.pp.se> wrote:
> 
> > On Thu, 19 Feb 2015, Ted Lemon wrote:
> >
> >  On Feb 19, 2015, at 1:08 PM, Mikael Abrahamsson <swmike@swm.pp.se> wrote:
> >>
> >>> I would like my router-to-router links to not have a lot of hosts in
> >>> them if I can avoid it.
> >>>
> >>
> >> Why is that?
> >>
> >
> > If we're going to be routing multicast within the home, we're most likely
> > going to have to use some kind of variant of PIM. Asking the L2 switches
> > people connect to the router to support both PIM and MLD snooping seem like
> > it might be asking too much.
> >
> > I might be wrong though.
> >
> > --
> > Mikael Abrahamsson    email: swmike@swm.pp.se
> >
> > _______________________________________________
> > homenet mailing list
> > homenet@ietf.org
> > https://www.ietf.org/mailman/listinfo/homenet
> >
> 
> 
> 
> -- 
> Andrew McGregor | SRE | andrewmcgr@google.com | +61 4 1071 2221

> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet


-- 
---
Toerless Eckert, eckert@cisco.com


From nobody Fri Feb 20 06:56:32 2015
Return-Path: <bs7652@att.com>
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 5E2781A1BB7 for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 06:56:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level: 
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 w-77Z2qsOVUp for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 06:56:27 -0800 (PST)
Received: from nbfkord-smmo06.seg.att.com (nbfkord-smmo06.seg.att.com [209.65.160.94]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 031321A8791 for <homenet@ietf.org>; Fri, 20 Feb 2015 06:56:26 -0800 (PST)
Received: from unknown [144.160.229.23] (EHLO alpi154.enaf.aldc.att.com) by nbfkord-smmo06.seg.att.com(mxl_mta-7.2.4-5) with ESMTP id b1b47e45.2b4be0666940.2965012.00-2474.8388846.nbfkord-smmo06.seg.att.com (envelope-from <bs7652@att.com>);  Fri, 20 Feb 2015 14:56:27 +0000 (UTC)
X-MXL-Hash: 54e74b1b1e4b7ea3-1f4db82d20c39bd6375e779b8bff42534fba909c
Received: from unknown [144.160.229.23] (EHLO alpi154.enaf.aldc.att.com) by nbfkord-smmo06.seg.att.com(mxl_mta-7.2.4-5) over TLS secured channel with ESMTP id 90b47e45.0.2964869.00-2339.8388402.nbfkord-smmo06.seg.att.com (envelope-from <bs7652@att.com>);  Fri, 20 Feb 2015 14:56:10 +0000 (UTC)
X-MXL-Hash: 54e74b0a47eacca6-d186801be0d353062811758650776cc1fa1b8924
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id t1KEu8iC003261; Fri, 20 Feb 2015 09:56:09 -0500
Received: from alpi132.aldc.att.com (alpi132.aldc.att.com [130.8.217.2]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id t1KEtuXC003020 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 20 Feb 2015 09:56:02 -0500
Received: from GAALPA1MSGHUBAE.ITServices.sbc.com (GAALPA1MSGHUBAE.itservices.sbc.com [130.8.218.154]) by alpi132.aldc.att.com (RSA Interceptor); Fri, 20 Feb 2015 14:55:47 GMT
Received: from GAALPA1MSGUSRBF.ITServices.sbc.com ([169.254.5.126]) by GAALPA1MSGHUBAE.ITServices.sbc.com ([130.8.218.154]) with mapi id 14.03.0224.002; Fri, 20 Feb 2015 09:55:47 -0500
From: "STARK, BARBARA H" <bs7652@att.com>
To: "'Teco Boot'" <teco@inf-net.nl>, Dave Taht <dave.taht@gmail.com>
Thread-Topic: [homenet] More about marginal links [was: Routing protocol comparison document]
Thread-Index: AQHQTIdQZefVGhBdf0KPcU80Od5Vz5z44AkAgAC9D4A=
Date: Fri, 20 Feb 2015 14:55:46 +0000
Message-ID: <2D09D61DDFA73D4C884805CC7865E61130F3037C@GAALPA1MSGUSRBF.ITServices.sbc.com>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <A5767F83-3D0C-40E5-A73B-912E3C160A42@fugue.com> <alpine.DEB.2.02.1502191235240.4007@uplift.swm.pp.se> <87zj89gaqm.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191804050.4007@uplift.swm.pp.se> <D10B8924.6BD5%John_Leddy@cable.comcast.com> <87h9uhg529.wl-jch@pps.univ-paris-diderot.fr> <87fva1fzwp.wl-jch@pps.univ-paris-diderot.fr> <CAA93jw57sNMPsKkL-W2m3s20DKsFZWNeGZSOgnmRTj3yz+Rgmg@mail.gmail.com> <EA20D83F-3E46-4484-AD65-518B1C3836DA@inf-net.nl>
In-Reply-To: <EA20D83F-3E46-4484-AD65-518B1C3836DA@inf-net.nl>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.61.166.72]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-AnalysisOut: [v=2.0 cv=V6DKJ5bi c=1 sm=1 a=VXHOiMMwGAwA+y4G3/O+aw==:17 a]
X-AnalysisOut: [=vKzWRVGcsRAA:10 a=BLceEmwcHowA:10 a=kj9zAlcOel0A:10 a=zQP]
X-AnalysisOut: [7CpKOAAAA:8 a=XIqpo32RAAAA:8 a=0HtSIViG9nkA:10 a=wkw6NztJP]
X-AnalysisOut: [U9fJA7A5S0A:9 a=CjuIK1q_8ugA:10]
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2014051901)]
X-MAIL-FROM: <bs7652@att.com>
X-SOURCE-IP: [144.160.229.23]
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/vHcbjOSRts32U4JfLPidT6TMT9s>
Cc: "Leddy, John" <John_Leddy@cable.comcast.com>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>, "homenet@ietf.org Group" <homenet@ietf.org>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] More about marginal links [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 14:56:31 -0000

> So what I want to see is a proposal for a routing protocol that specify l=
ink
> metrics for a set of commonly used link types in homes. This spec could b=
e
> BCP.

Does it need to be a routing protocol? Just to throw another possible proto=
col into the mix being tossed around (like we don't have enough), I'd like =
to suggest that a non-routing protocol be considered for topology discovery=
 and sharing of link metrics. Specifically, IEEE 1905.1a could help with th=
is. It can provide L1 and L2 topology info with link metrics, and identify =
intervening bridges that support LLDP for IEEE 802.1 bridge discovery. I wo=
uldn't want individual devices all doing their own 1905 topology discovery =
-- that's too chatty. But if the all the homenet routers did, and then adve=
rtised a "service" (DNS-SD) that provided a link to a router-provider HTML =
page with the topology and metric info the router can discover provided in =
a standardized XML or JSON syntax, then everything who can discover that se=
rvice (on each router) would have access to this info. Applications could a=
lso make use of this info to do intelligent source address selection in a m=
ulti-WAN-interface network, because routers could report on the speed of th=
eir WAN connections, as well.

Just a thought. I've been working on trying to get myself to write a contri=
bution describing the idea of the router-provided info service for a while =
now.
Barbara


From nobody Fri Feb 20 07:23:04 2015
Return-Path: <philippe@broadcom.com>
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 92BD91A1AB0 for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 07:23:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level: 
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 CqS2GSZWZHGM for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 07:23:00 -0800 (PST)
Received: from mail-gw2-out.broadcom.com (mail-gw2-out.broadcom.com [216.31.210.63]) by ietfa.amsl.com (Postfix) with ESMTP id AFC3A1A87D1 for <homenet@ietf.org>; Fri, 20 Feb 2015 07:14:55 -0800 (PST)
X-IronPort-AV: E=Sophos;i="5.09,615,1418112000"; d="scan'208";a="57597155"
Received: from irvexchcas06.broadcom.com (HELO IRVEXCHCAS06.corp.ad.broadcom.com) ([10.9.208.53]) by mail-gw2-out.broadcom.com with ESMTP; 20 Feb 2015 07:56:10 -0800
Received: from SJEXCHCAS04.corp.ad.broadcom.com (10.16.203.10) by IRVEXCHCAS06.corp.ad.broadcom.com (10.9.208.53) with Microsoft SMTP Server (TLS) id 14.3.174.1; Fri, 20 Feb 2015 07:14:55 -0800
Received: from SJEXCHMB06.corp.ad.broadcom.com ([fe80::65ea:1de7:41c4:e948]) by SJEXCHCAS04.corp.ad.broadcom.com ([::1]) with mapi id 14.03.0174.001; Fri, 20 Feb 2015 07:14:54 -0800
From: Philippe Klein <philippe@broadcom.com>
To: "STARK, BARBARA H" <bs7652@att.com>
Thread-Topic: [homenet] More about marginal links [was: Routing protocol comparison document]
Thread-Index: AQHQTIdMEP1l0unND0u0oxHzBZMK45z5ElMAgAEVVwD//389kQ==
Date: Fri, 20 Feb 2015 15:14:53 +0000
Message-ID: <C420ADBA-0E29-4A08-A605-F0252D25D041@broadcom.com>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <A5767F83-3D0C-40E5-A73B-912E3C160A42@fugue.com> <alpine.DEB.2.02.1502191235240.4007@uplift.swm.pp.se> <87zj89gaqm.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191804050.4007@uplift.swm.pp.se> <D10B8924.6BD5%John_Leddy@cable.comcast.com> <87h9uhg529.wl-jch@pps.univ-paris-diderot.fr> <87fva1fzwp.wl-jch@pps.univ-paris-diderot.fr> <CAA93jw57sNMPsKkL-W2m3s20DKsFZWNeGZSOgnmRTj3yz+Rgmg@mail.gmail.com> <EA20D83F-3E46-4484-AD65-518B1C3836DA@inf-net.nl>, <2D09D61DDFA73D4C884805CC7865E61130F3037C@GAALPA1MSGUSRBF.ITServices.sbc.com>
In-Reply-To: <2D09D61DDFA73D4C884805CC7865E61130F3037C@GAALPA1MSGUSRBF.ITServices.sbc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/yWIosOGhzpDIyi46iCuKz2Hld7M>
Cc: "Leddy, John" <John_Leddy@cable.comcast.com>, Teco Boot <teco@inf-net.nl>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>, Dave Taht <dave.taht@gmail.com>, "homenet@ietf.org Group" <homenet@ietf.org>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] More about marginal links [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 15:23:02 -0000

At the end if the day, L3 will need to get services from L2 to set and mana=
ged constrained  path based on Link attributes. 802.1Q is specifying multi-=
path short path bridging for this purpose and will allow to maximize the BW=
 provide by the whole topology of the home network in a loop free  manner.
L3 and L2 for this manner could share the same IS-IS topology DB.
All the elements are there but require to make a joint IEEE 702.1 and IETF =
effort

/Philippe

Philippe Klein, PhD
Broadcom BTG



Sent from my iPhone

On Feb 20, 2015, at 16:56, STARK, BARBARA H <bs7652@att.com> wrote:

>> So what I want to see is a proposal for a routing protocol that specify =
link
>> metrics for a set of commonly used link types in homes. This spec could =
be
>> BCP.
>=20
> Does it need to be a routing protocol? Just to throw another possible pro=
tocol into the mix being tossed around (like we don't have enough), I'd lik=
e to suggest that a non-routing protocol be considered for topology discove=
ry and sharing of link metrics. Specifically, IEEE 1905.1a could help with =
this. It can provide L1 and L2 topology info with link metrics, and identif=
y intervening bridges that support LLDP for IEEE 802.1 bridge discovery. I =
wouldn't want individual devices all doing their own 1905 topology discover=
y -- that's too chatty. But if the all the homenet routers did, and then ad=
vertised a "service" (DNS-SD) that provided a link to a router-provider HTM=
L page with the topology and metric info the router can discover provided i=
n a standardized XML or JSON syntax, then everything who can discover that =
service (on each router) would have access to this info. Applications could=
 also make use of this info to do intelligent source address selection in a=
 multi-WAN-interface netw
> ork, because routers could report on the speed of their WAN connections, =
as well.
>=20
> Just a thought. I've been working on trying to get myself to write a cont=
ribution describing the idea of the router-provided info service for a whil=
e now.
> Barbara
>=20
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet


From nobody Fri Feb 20 07:26:40 2015
Return-Path: <teco@inf-net.nl>
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 A1A901A1B13 for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 07:26:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 3LYhPJxxAgK5 for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 07:26:36 -0800 (PST)
Received: from mail-wi0-f169.google.com (mail-wi0-f169.google.com [209.85.212.169]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 143A31A8760 for <homenet@ietf.org>; Fri, 20 Feb 2015 07:26:14 -0800 (PST)
Received: by mail-wi0-f169.google.com with SMTP id em10so7143354wid.0 for <homenet@ietf.org>; Fri, 20 Feb 2015 07:26:12 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=pgFDRfdB2uDr4rorsR6YmWSHQzYqwa2zzRIkRBkC1bw=; b=cbNi3RT7PH5CEZ+Z9tMwxVfyrbDIi5t4A0ec4WKdqcHmO5yrz2IZo9tsSfaLUn5t64 bIHtelhKLYSx2qFg2/p5R4jkIGLKxG3DyIeugRt69guDlP/F4HEKhwGsRfCCtQatN4jA GPTuznfKFyQXEI+9v1B4JolIC6mus3xmL7Er2jfuSvHIhKXCBrSrBb73v4LnxP9VaBSe Q+kxCTlVEO69zvDBQxgfXl256aSLHrT4Yj4TCXUKuNTI4FYHEZSrZ+dy+ZShc7TNOeBu UY05cEi4tBB/UiYR1dGbo0X7xKGMWmxz6r9lNAvwSQxq/7WXvN9kU3dbWQmw15iQMALT 9z9w==
X-Gm-Message-State: ALoCoQlZ2tfBEYs9wwikdpkCLGbrG3rv5fZ0GLAaz2wfqWWqHRz0f7obb0tVU84DwTaSZLqTfQK0
X-Received: by 10.194.242.6 with SMTP id wm6mr19593854wjc.7.1424445972610; Fri, 20 Feb 2015 07:26:12 -0800 (PST)
Received: from [192.168.178.95] (524A158D.cm-4-3a.dynamic.ziggo.nl. [82.74.21.141]) by mx.google.com with ESMTPSA id l4sm2835270wiw.9.2015.02.20.07.26.11 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 20 Feb 2015 07:26:11 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Teco Boot <teco@inf-net.nl>
In-Reply-To: <CC31C560-C688-448C-A296-8D8644DC0F84@fugue.com>
Date: Fri, 20 Feb 2015 16:26:09 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <4595B4FB-6F73-4BE7-94FB-CBA36181AF91@inf-net.nl>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <8B98F698-983D-4D2A-B5D1-7ACED27C275E@fugue.com> <alpine.DEB.2.02.1502191920560.4007@uplift.swm.pp.se> <CAPRuP3mpNJTu6mP+RAVKKO0kt60PogNtNbCUCRRqxe9im3EzjA@mail.gmail.com> <alpine.DEB.2.02.1502201042330.4007@uplift.swm.pp.se> <7A86BDC6-FF4B-49FF-B59C-BA1DEF463173@inf-net.nl> <alpine.DEB.2.02.1502201310050.4007@uplift.swm.pp.se> <09793905-8D12-49E0-A040-490F617C87FF@inf-net.nl> <alpine.DEB.2.02.1502201410510. 4007@uplift.swm.pp.se> <CC31C560-C688-448C-A296-8D8644DC0F84@fugue.com>
To: Ted Lemon <mellon@fugue.com>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/aDuGbKWLnZqj4axwtMzrRHyeiLg>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 15:26:38 -0000

Were you before me?
http://www.ietf.org/mail-archive/web/homenet/current/msg00971.html
(November 2011)

More than three years later, same discussion. That makes me sad.

Teco

> Op 20 feb. 2015, om 15:14 heeft Ted Lemon <mellon@fugue.com> het =
volgende geschreven:
>=20
> On Feb 20, 2015, at 8:22 AM, Mikael Abrahamsson <swmike@swm.pp.se> =
wrote:
>> 2. We set up some kind of L2 switching domain between the APs. This =
would require VLAN support in the HGWs, and something to set this up =
with loop avoidance etc. Oh oh oh, we could use IEEE 802.1aq that =
already uses ISIS as control plane, that way we could possibly run the =
same IGP for both L2 and L3. Interconnecting APs over wifi seems weird =
though. Oh, and messy sounds like an understatement.
>=20
> Long ago I proposed using Trill to make this work, but nobody =
listened...
>=20
> :)
>=20


From nobody Fri Feb 20 07:26:57 2015
Return-Path: <mike@mtcc.com>
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 3F25A1A878A for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 07:26:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.112
X-Spam-Level: 
X-Spam-Status: No, score=-1.112 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_ALL=0.8, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 FhXjv6sCFP0b for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 07:26:47 -0800 (PST)
Received: from mtcc.com (mtcc.com [50.0.18.224]) (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 1ED561A87BF for <homenet@ietf.org>; Fri, 20 Feb 2015 07:26:27 -0800 (PST)
Received: from takifugu.mtcc.com (takifugu.mtcc.com [50.0.18.224]) (authenticated bits=0) by mtcc.com (8.14.7/8.14.7) with ESMTP id t1KFQQs2019775; Fri, 20 Feb 2015 07:26:26 -0800
Message-ID: <54E75222.5080604@mtcc.com>
Date: Fri, 20 Feb 2015 07:26:26 -0800
From: Michael Thomas <mike@mtcc.com>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: Mikael Abrahamsson <swmike@swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <54E58238.9030809@mtcc.com> <alpine.DEB.2.02.1502190851300.4007@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1502190851300.4007@uplift.swm.pp.se>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/5mQEFvR9FPnvz4vOyVb73WORSEU>
Cc: homenet@ietf.org
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 15:26:49 -0000

On 02/18/2015 11:54 PM, Mikael Abrahamsson wrote:
> On Wed, 18 Feb 2015, Michael Thomas wrote:
>
>> But we're not talking about an interpreted language in the forwarding 
>> plane, right? Is the load from routing protocols we're talking about 
>> likely to have any noticeable effect on the the forwarding rate? even 
>> when you're running hot on the routing daemon side, you're not too 
>> likely to be running hot on the forwarding side because something is 
>> hosed, right?
>
> The complaints about the Erlang implementation has so far been on 
> memory and flash footprint, not CPU resources and affecting 
> performance. The above is true for most interpreted languages, such as 
> python etc. When you install the environment, they're going to use 
> noticable memory and disk space. Next application that needs the 
> environment won't add much to the footprint though, it's the 
> environment itself that takes space.
>
> My Python executable on my debian box is 2.7 megabyte. I don't know 
> about the rest. So if one wants to run Python on the home gateway, 
> that would also use significant space.
>
> But forwarding will be done the same way regardless of what routing 
> protocol we use, that'll be done by the kernel. The routing protocol 
> just programs the RIB/FIB.
>

One nice side-effect of putting in, say, a headless android into a 
router is that it would forevermore insure that there's
plentiful memory, just like it did for cell phones. It's not like we 
physically can't get enough ram/flash into those boxen
after all... it's the will to bear the cost that's really at issue.

A better development environment for home routers would *really* help 
development efforts along. From what I've seen
they suck out loud.

Mike


From nobody Fri Feb 20 07:37:54 2015
Return-Path: <markus.stenberg@iki.fi>
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 CFE261A874E for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 07:37:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.121
X-Spam-Level: 
X-Spam-Status: No, score=-1.121 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_NEUTRAL=0.779] autolearn=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 0fQe3bdyaq7P for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 07:37:51 -0800 (PST)
Received: from kirsi1.inet.fi (mta-out1.inet.fi [62.71.2.203]) by ietfa.amsl.com (Postfix) with ESMTP id 449591A8033 for <homenet@ietf.org>; Fri, 20 Feb 2015 07:37:49 -0800 (PST)
Received: from poro.lan (80.220.64.126) by kirsi1.inet.fi (8.5.142.08) (authenticated as stenma-47) id 54E3C711005D9388; Fri, 20 Feb 2015 17:37:44 +0200
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Markus Stenberg <markus.stenberg@iki.fi>
In-Reply-To: <alpine.DEB.2.02.1502201410510.4007@uplift.swm.pp.se>
Date: Fri, 20 Feb 2015 17:37:43 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <21FCAC07-1361-4051-B728-38AFB0656009@iki.fi>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <8B98F698-983D-4D2A-B5D1-7ACED27C275E@fugue.com> <alpine.DEB.2.02.1502191920560.4007@uplift.swm.pp.se> <CAPRuP3mpNJTu6mP+RAVKKO0kt60PogNtNbCUCRRqxe9im3EzjA@mail.gmail.com> <alpine.DEB.2.02.1502201042330.4007@uplift.swm.pp.se> <7A86BDC6-FF4B-49FF-B59C-BA1DEF463173@inf-net.nl> <alpine.DEB.2.02.1502201310050.4007@uplift.swm.pp.se> <09793905-8D12-49E0-A040-490F617C87FF@inf-net.nl> <alpine.DEB.2.02.1502201410510.4007@uplift.swm.pp.se>
To: Mikael Abrahamsson <swmike@swm.pp.se>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/OtkO2kEclolpswOBdXbBAExdSWk>
Cc: Teco Boot <teco@inf-net.nl>, Markus Stenberg <markus.stenberg@iki.fi>, "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 15:37:54 -0000

> On 20.2.2015, at 15.22, Mikael Abrahamsson <swmike@swm.pp.se> wrote:
>> Back to the subject: What are the requirements of a high performance =
WiFi home network to the homenet routing protocol? I guess we don't =
know.
> Within the current framework to solve this problem with what exists =
today when it comes to clients, I would say we need either:
>=20
> 1. HNCP helps set up an overlay L2 tunnel infrastructure connecting =
all the APs using the same SSID, so the SSID can have the same L2 =
domain. This would probably mean we want to increase MTU on the physical =
links to avoid fragmentation. Messy. Possibly we could advertise lower =
MTU on the wifi network to minimize fragmentation if we don't raise MTU.
>=20
> 2. We set up some kind of L2 switching domain between the APs. This =
would require VLAN support in the HGWs, and something to set this up =
with loop avoidance etc. Oh oh oh, we could use IEEE 802.1aq that =
already uses ISIS as control plane, that way we could possibly run the =
same IGP for both L2 and L3. Interconnecting APs over wifi seems weird =
though. Oh, and messy sounds like an understatement.
>=20
> Frankly, I don't know how to solve this without a lot of complication.
>=20
> We need clients to be able to change IPv6 addresses without losing =
existing connections. SHIM6 anyone? MP-TCP? Asking IEEE to make 802.11 =
keep two connections at once and inform the application that one address =
is going away soon so it can do its thing to try to handle this?

What if clients do not need to change addresses? In 2 words: Route =
/128s.

Two ways to do it:
- have clients talk stub RP + stub HNCP, be done with it
- have first-hop router do proxying for them by advertising the /128s =
only when they are connected to it (may have issues with e.g. clients =
assuming /64, but nothing a redirect could not fix, hopefully)

This L3(ish) solution actually works for all apps, unlike L4+ solutions =
some people advocated.

Cheers,

-Markus=


From nobody Fri Feb 20 07:42:01 2015
Return-Path: <teco@inf-net.nl>
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 E026B1A87AD for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 07:41:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  J_CHICKENPOX_44=0.6, RCVD_IN_DNSWL_LOW=-0.7] 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 zAqXZUFzkHhD for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 07:41:57 -0800 (PST)
Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 665831A8033 for <homenet@ietf.org>; Fri, 20 Feb 2015 07:41:57 -0800 (PST)
Received: by mail-wi0-f178.google.com with SMTP id em10so3754304wid.5 for <homenet@ietf.org>; Fri, 20 Feb 2015 07:41:56 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=NNg5cklk46n/EHVJgbbz7HFJQlOfsnAtTBcOAjfmiCg=; b=aVe6ScI64PiX4eHnsOijk6km62iglsqKbpHlORGpJBTNCW6MYQ0WW1nV/wpDO6Ux+H DWwPOPGPr6c5yIdoMh/t7ZsZ2tVyedRYBLIXV8BGHQJdi5BtF5FHNsQyPbzT1FCvlHQL OUViiPFphEjKf+jJn1yS4O8qAZP14W+TBCmSQtisMH61Z/M96gky9Cn2G6dkRzBOyWSN VNPPWn7tn9q77nOIM/l/QdGmYfw4qgAMshgli4DPAtrVCq2Rw1TKAGXfHdknnCi04FBC OKpaMb+EtTywvygCQZ3SmQw0fZcI6EcEGlsH2nbZPT5rZidDzMt3Lj9to8v5Dd/xw7nw oS0Q==
X-Gm-Message-State: ALoCoQmYaxhatlsw1qZq+m1QjRWR6/W5ZuRGjUf2xs0ScQEcPdznHeWlxs0aztJmmsohn+OxCRqY
X-Received: by 10.194.52.66 with SMTP id r2mr19542384wjo.61.1424446915909; Fri, 20 Feb 2015 07:41:55 -0800 (PST)
Received: from [192.168.178.95] (524A158D.cm-4-3a.dynamic.ziggo.nl. [82.74.21.141]) by mx.google.com with ESMTPSA id g10sm2894165wic.7.2015.02.20.07.41.54 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 20 Feb 2015 07:41:55 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Teco Boot <teco@inf-net.nl>
In-Reply-To: <2D09D61DDFA73D4C884805CC7865E61130F3037C@GAALPA1MSGUSRBF.ITServices.sbc.com>
Date: Fri, 20 Feb 2015 16:41:53 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <FA674A21-8D36-43C9-ABF3-3E303EEB1397@inf-net.nl>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <A5767F83-3D0C-40E5-A73B-912E3C160A42@fugue.com> <alpine.DEB.2.02.1502191235240.4007@uplift.swm.pp.se> <87zj89gaqm.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191804050.4007@uplift.swm.pp.se> <D10B8924.6BD5%John_Leddy@cable.comcast.com> <87h9uhg529.wl-jch@pps.univ-paris-diderot.fr> <87fva1fzwp.wl-jch@pps.univ-paris-diderot.fr> <CAA93jw57sNMPsKkL-W2m3s20DKsFZWNeGZSOgnmRTj3yz+Rgmg@mail.gmail.com> <EA20D83F-3E46-4484-AD65-518B1C3836DA@inf-net.nl> <2D09D61DDFA73D4C884805CC7865E61130F3037C@GAALPA1MSGUSRBF.ITServices.sbc.com>
To: "STARK, BARBARA H" <bs7652@att.com>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/dqyDQdg16i8yRvzP502Nbye893U>
Cc: "Leddy, John" <John_Leddy@cable.comcast.com>, "homenet@ietf.org Group" <homenet@ietf.org>, Dave Taht <dave.taht@gmail.com>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] More about marginal links [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 15:42:00 -0000

> Op 20 feb. 2015, om 15:55 heeft STARK, BARBARA H <bs7652@att.com> het =
volgende geschreven:
>=20
>> So what I want to see is a proposal for a routing protocol that =
specify link
>> metrics for a set of commonly used link types in homes. This spec =
could be
>> BCP.
>=20
> Does it need to be a routing protocol? Just to throw another possible =
protocol into the mix being tossed around (like we don't have enough),

I don't think current protocols used by ISPs or enterprises fits our =
plug&play requirements. Also, there is a lot more wireless in homes. =
That doesn't mean we cannot build on current protocols.=20


> I'd like to suggest that a non-routing protocol be considered for =
topology discovery and sharing of link metrics. Specifically, IEEE =
1905.1a could help with this. It can provide L1 and L2 topology info =
with link metrics, and identify intervening bridges that support LLDP =
for IEEE 802.1 bridge discovery. I wouldn't want individual devices all =
doing their own 1905 topology discovery -- that's too chatty. But if the =
all the homenet routers did, and then advertised a "service" (DNS-SD) =
that provided a link to a router-provider HTML page with the topology =
and metric info the router can discover provided in a standardized XML =
or JSON syntax, then everything who can discover that service (on each =
router) would have access to this info. Applications could also make use =
of this info to do intelligent source address selection in a =
multi-WAN-interface network, because routers could report on the speed =
of their WAN connections, as well.

My thoughts are as follows: sub-IP mechanisms provide usable metrics. =
Somewhere, near to L3 routing, this information is translated to a =
dimensionless cost metric for each link, where a link is a sub-IP path =
between two routers. Cost is not symmetric, cost A->B can differ from =
B->A. It is the routing protocol to distribute this information in the =
routing domain.

Teco

>=20
> Just a thought. I've been working on trying to get myself to write a =
contribution describing the idea of the router-provided info service for =
a while now.
> Barbara


From nobody Fri Feb 20 07:46:51 2015
Return-Path: <bs7652@att.com>
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 9F24B1A0267 for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 07:46:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level: 
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 0sAHYxtiVAmW for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 07:46:48 -0800 (PST)
Received: from nbfkord-smmo05.seg.att.com (nbfkord-smmo05.seg.att.com [209.65.160.92]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DC23C1A8781 for <homenet@ietf.org>; Fri, 20 Feb 2015 07:46:47 -0800 (PST)
Received: from unknown [144.160.229.23] (EHLO alpi154.enaf.aldc.att.com) by nbfkord-smmo05.seg.att.com(mxl_mta-7.2.4-5) with ESMTP id 7e657e45.2b598022c940.2989571.00-2443.8462856.nbfkord-smmo05.seg.att.com (envelope-from <bs7652@att.com>);  Fri, 20 Feb 2015 15:46:47 +0000 (UTC)
X-MXL-Hash: 54e756e74e771a51-3330bc6c2faade8e5b331685286418a822b0c839
Received: from unknown [144.160.229.23] (EHLO alpi154.enaf.aldc.att.com) by nbfkord-smmo05.seg.att.com(mxl_mta-7.2.4-5) over TLS secured channel with ESMTP id b9657e45.0.2988564.00-2068.8459971.nbfkord-smmo05.seg.att.com (envelope-from <bs7652@att.com>);  Fri, 20 Feb 2015 15:45:38 +0000 (UTC)
X-MXL-Hash: 54e756a21ff2aa5c-988c08d409d69acfa9d5b9b1a94669b1faec2570
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id t1KFjUE0031715; Fri, 20 Feb 2015 10:45:31 -0500
Received: from alpi131.aldc.att.com (alpi131.aldc.att.com [130.8.218.69]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id t1KFjHrj031505 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 20 Feb 2015 10:45:18 -0500
Received: from GAALPA1MSGHUBAG.ITServices.sbc.com (GAALPA1MSGHUBAG.itservices.sbc.com [130.8.218.156]) by alpi131.aldc.att.com (RSA Interceptor); Fri, 20 Feb 2015 15:45:09 GMT
Received: from GAALPA1MSGUSRBF.ITServices.sbc.com ([169.254.5.126]) by GAALPA1MSGHUBAG.ITServices.sbc.com ([130.8.218.156]) with mapi id 14.03.0224.002; Fri, 20 Feb 2015 10:45:09 -0500
From: "STARK, BARBARA H" <bs7652@att.com>
To: "'Sander Steffann'" <sander@steffann.nl>, Ted Lemon <mellon@fugue.com>
Thread-Topic: [homenet] Routing protocol comparison document
Thread-Index: AQHQSU32GNhjW8WFi0qWgaveVMetmJz2sruAgAAaSQCAABl7AIAABlyAgAAB2ICAAHYtgIAAdnwAgACUFwCAAAN+AIAADi6AgAANtQCAAAO9gIAAAvaAgAAKtoCAAAW0AIAABNSAgABSl4CAALAF4A==
Date: Fri, 20 Feb 2015 15:45:09 +0000
Message-ID: <2D09D61DDFA73D4C884805CC7865E61130F303F4@GAALPA1MSGUSRBF.ITServices.sbc.com>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <54E58238.9030809@mtcc.com> <874mqigcct.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191622510.4007@uplift.swm.pp.se> <87vbixg9fe.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191806381.4007@uplift.swm.pp.se> <87lhjtg6jc.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191826230.4007@uplift.swm.pp.se> <2FE73365-ECD7-49C3-8476-934CD1032542@fugue.com> <alpine.DEB.2.02.1502191924250.4007@uplift.swm.pp.se> <DE5D415F-4804-44C2-9621-523C3EFBC859@fugue.com> <DD0D0BE4-3753-4305-85D5-00CC8A37D045@steffann.nl>
In-Reply-To: <DD0D0BE4-3753-4305-85D5-00CC8A37D045@steffann.nl>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.61.166.72]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-AnalysisOut: [v=2.0 cv=EtBlW1gA c=1 sm=1 a=VXHOiMMwGAwA+y4G3/O+aw==:17 a]
X-AnalysisOut: [=vKzWRVGcsRAA:10 a=BLceEmwcHowA:10 a=kj9zAlcOel0A:10 a=zQP]
X-AnalysisOut: [7CpKOAAAA:8 a=XIqpo32RAAAA:8 a=0HtSIViG9nkA:10 a=xzpHuLrVU]
X-AnalysisOut: [kxzpIrpSCIA:9 a=CjuIK1q_8ugA:10]
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2014051901)]
X-MAIL-FROM: <bs7652@att.com>
X-SOURCE-IP: [144.160.229.23]
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/mD6CzQYfCms2y1EE7LobiSNkfsI>
Cc: "homenet@ietf.org" <homenet@ietf.org>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 15:46:49 -0000

> > I don't know.   Homenet multicast is an open issue.   But I don't think=
 this
> use case represents a serious problem, because as far as I can tell strea=
ming
> video is not done using multicast in practice anyway.
>=20
> Sorry, bad assumption. I just finished working on a TV streaming project =
for
> an ISP and there is lots of multicast there. All live TV channel streams =
to STBs
> are multicast and this is a common setup amongst ISPs.

OTT video does not use multicast. IPTV deployments do use multicast. Those =
that I'm aware of require use of the provider-supplied CE router, which has=
 an IGMP proxy (and MLD proxy if IPv6 multicast is supported) for LAN-to-WA=
N multicast management. Where Wi-Fi distribution of these multicast streams=
 is supported, it is only done on a dedicated (and highly managed and somew=
hat proprietary) Wi-Fi network, that is distinct from the general-purpose (=
and not "professionally" managed) Wi-Fi network. The LAN interfaces of the =
provider-supplied CE router do tend to have IGMP/MLD snooping, to keep from=
 flooding the general-purpose network interfaces with large multicast strea=
ms. There may also be a coax networking interface. If there is, this also t=
ends to be dedicated and highly managed. Where Ethernet is used for distrib=
ution of multicast, it is done so that the provider STBs are all attached t=
o the provider CE router via the same Ethernet port (and no other devices u=
se that port) and there are no intervening routers. I mentioned at the last=
 IETF that I expect some "home networks" to have managed and unmanaged segm=
ents. I don't consider the dedicated, managed segments to be part of the ho=
menet domain. I would hope that the provider-supplied CE router would suppo=
rt homenet on its general purpose network interfaces.=20

I'd be curious to learn about multicast IPTV deployments that allow users t=
o supply their own CE routers and send multicast streams on network segment=
s that are also used for general-purpose home networking (especially genera=
l-purpose Wi-Fi networks).=20

BTW, the dedicated, highly-managed and somewhat proprietary Wi-Fi delivery =
of IPTV multicast streams has been very successful.
Barbara


From nobody Fri Feb 20 08:09:49 2015
Return-Path: <John_Leddy@cable.comcast.com>
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 D1A581A0066 for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 08:09:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.225
X-Spam-Level: 
X-Spam-Status: No, score=0.225 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 64EG6DlOZkkG for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 08:09:40 -0800 (PST)
Received: from pacdcmhout01.cable.comcast.com (PACDCMHOUT01.cable.comcast.com [68.87.31.167]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D63F31A6F27 for <homenet@ietf.org>; Fri, 20 Feb 2015 08:09:38 -0800 (PST)
X-AuditID: 44571fa7-f79b96d000002184-8a-54e75c41b967
Received: from PACDCEXHUB03.cable.comcast.com (pacdcexhub03.cable.comcast.com [24.40.56.116]) by pacdcmhout01.cable.comcast.com (SMTP Gateway) with SMTP id AB.78.08580.14C57E45; Fri, 20 Feb 2015 11:09:37 -0500 (EST)
Received: from PACDCEXMB22.cable.comcast.com ([fe80::f887:1b71:477f:d14b]) by PACDCEXHUB03.cable.comcast.com ([fe80::7da6:458a:eadf:dadb%16]) with mapi id 14.03.0181.006; Fri, 20 Feb 2015 11:09:32 -0500
From: "Leddy, John" <John_Leddy@cable.comcast.com>
To: Toerless Eckert <eckert@cisco.com>, Andrew Mcgregor <andrewmcgr@google.com>
Thread-Topic: [homenet] Routing protocol comparison document
Thread-Index: AQHQTRtVpljA4qO18ECjoj8KcSEQaZz5tQAA
Date: Fri, 20 Feb 2015 16:09:31 +0000
Message-ID: <D10CC5CF.6EBF%John_Leddy@cable.comcast.com>
References: <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <8B98F698-983D-4D2A-B5D1-7ACED27C275E@fugue.com> <alpine.DEB.2.02.1502191920560.4007@uplift.swm.pp.se> <CAPRuP3mpNJTu6mP+RAVKKO0kt60PogNtNbCUCRRqxe9im3EzjA@mail.gmail.com> <20150220144138.GD8096@cisco.com>
In-Reply-To: <20150220144138.GD8096@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.4.7.141117
x-originating-ip: [24.40.1.133]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <FD325A580949B64B896CEAF099F4EB97@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrMIsWRmVeSWpSXmKPExsUioWFRousY8zzE4OUcfYveY/PYLPYuv8dm 8X7RIRaLN2uOMFm8XLqVzYHVY8rvjaweTReWsXss2FTqsWTJTyaPv5MeMgWwRnHZpKTmZJal FunbJXBl3O9Yy1LwXaJi8YS1TA2MTSJdjJwcEgImEvt/vmeHsMUkLtxbz9bFyMUhJHCTUWJu 52p2COcco8TSVxvAqtgEjCRurtrCCGKLCARKdHTuZwKxmQXKJE7PaASq4eAQFrCWWNLiAVFi I7F/VSs7hG0k8eXfHxYQm0VAVWLB7ZWsIDavgIXEwytLoHZdZZGYfPYUWAOngJ7E1n+fmEFs RqDrvp9aA7VLXOLWk/lMEFcLSCzZc54ZwhaVePn4H9hQUaDeldeb2CDi8hLr/i1nhOjVkViw +xMbhO0g0T7pETuErS2xbOFrZoiDBCVOznzCMoFRYhaSdbOQtM9C0j4LSfssJO0LGFlXMcoV JCanJOdm5JeWGBjqJScm5aTqJefnJicWl4DoTYzAqHYJl1++g/HeC6dDjAIcjEo8vF1+z0OE WBPLiitzDzFKcDArifCG+gOFeFMSK6tSi/Lji0pzUosPMUpzsCiJ874NB0oJpCeWpGanphak FsFkmTg4pRoYt/5Zc2OPYFq/0MPY61OdWL4fOL86bePzZ/aym2UqtE9ci34xoSO6Xen8tl3l WRn/tL7m3/jBVhrPKa09v2jD0372E43RH0uCFXgthK+nbPij9veowywWi7C5jL1i0T8qvRz3 m29/eevpRfWvk1oqk5akLV0mvI/HvOLVwUebeR4q9IlUBNk8U2Ipzkg01GIuKk4EAFQ84ZPm AgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/XxgY9ASY8HPekoBR7I16_ThznE8>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Ted Lemon <mellon@fugue.com>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 16:09:42 -0000

Has the group considered a Bier model for multicast in the home?


On 2/20/15, 9:41 AM, "Toerless Eckert" <eckert@cisco.com> wrote:

>I have seen more L2 switches that have broken IGMP/MLD snooping than
>working ones. I am not aware of real proliferation of PIM snooping.
>Snooping in transit LANs with PIM is a bad idea anyhow, and i have
>tried to steer any customer who asked me away from it.
>
>Bidir-PIM makes snooping particularily difficult. For once
>you have to track DF-winner election messages (difficult) and
>secondly you have to then flood all multicast to all DF winners
>because you don't know which group-range is served by which RP.
>
>IMHO, there is never enough multicast to justify this snooping complexity.
>The only thing to worry about is what packets to send out from a router
>to ensure the snooping doesn't screw up the traffic flow.
>
>I would be surprised to find equipemnt that does PIM snooping by default.
>
>So, i'd recommend to a homenet router:
>
>-> even if you don't do PIM, send out PIM Hellos. This should
>   effectively make all stupid "enterprise class" IGMP/MLD snooping
>   switches (that often have broken IGMP/MLD snooping) send
>   you all multicast traffic (inhibits snooping).
>
>-> Still send MLD/IGMP memberships to get traffic through the
>   L2 home equipment that has likely never heard about PIM.
>   I'd guess that eg: powerline equipment falls into this
>   category.
>
>Cheers
>    Toerless
>
>On Fri, Feb 20, 2015 at 11:04:41AM +1100, Andrew Mcgregor wrote:
>> Why?  PIM and MLD snooping are pretty standard on very low-end
>>enterprise
>> switches, which will be next year's midrange consumer models.  If the
>> dumb-as-rocks stuff goes away, that would generally make people happier.
>>=20
>> On 20 February 2015 at 05:22, Mikael Abrahamsson <swmike@swm.pp.se>
>>wrote:
>>=20
>> > On Thu, 19 Feb 2015, Ted Lemon wrote:
>> >
>> >  On Feb 19, 2015, at 1:08 PM, Mikael Abrahamsson <swmike@swm.pp.se>
>>wrote:
>> >>
>> >>> I would like my router-to-router links to not have a lot of hosts in
>> >>> them if I can avoid it.
>> >>>
>> >>
>> >> Why is that?
>> >>
>> >
>> > If we're going to be routing multicast within the home, we're most
>>likely
>> > going to have to use some kind of variant of PIM. Asking the L2
>>switches
>> > people connect to the router to support both PIM and MLD snooping
>>seem like
>> > it might be asking too much.
>> >
>> > I might be wrong though.
>> >
>> > --
>> > Mikael Abrahamsson    email: swmike@swm.pp.se
>> >
>> > _______________________________________________
>> > homenet mailing list
>> > homenet@ietf.org
>> > https://www.ietf.org/mailman/listinfo/homenet
>> >
>>=20
>>=20
>>=20
>> --=20
>> Andrew McGregor | SRE | andrewmcgr@google.com | +61 4 1071 2221
>
>> _______________________________________________
>> homenet mailing list
>> homenet@ietf.org
>> https://www.ietf.org/mailman/listinfo/homenet
>
>
>--=20
>---
>Toerless Eckert, eckert@cisco.com
>
>_______________________________________________
>homenet mailing list
>homenet@ietf.org
>https://www.ietf.org/mailman/listinfo/homenet
>


From nobody Fri Feb 20 08:25:36 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 AA7EB1A87DF for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 08:25:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.35
X-Spam-Level: 
X-Spam-Status: No, score=-0.35 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35, J_CHICKENPOX_42=0.6, J_CHICKENPOX_44=0.6] autolearn=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 34u5gNzzV9tO for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 08:25:33 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 A28451A87C9 for <homenet@ietf.org>; Fri, 20 Feb 2015 08:25:32 -0800 (PST)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t1KGPUid027981; Fri, 20 Feb 2015 17:25:30 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 610662BFCE1; Fri, 20 Feb 2015 17:25:30 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id gGUFpH1Lu-Pp; Fri, 20 Feb 2015 17:25:28 +0100 (CET)
Received: from pirx.pps.jussieu.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 77D742BFCD9; Fri, 20 Feb 2015 17:25:28 +0100 (CET)
Date: Fri, 20 Feb 2015 17:25:29 +0100
Message-ID: <87pp94czye.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Henning Rogge <hrogge@gmail.com>
In-Reply-To: <CAGnRvuqUSXpTPCqG4fsNHA=tsge=FvUUXuouwoVsRy1Cw3-cug@mail.gmail.com>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <A5767F83-3D0C-40E5-A73B-912E3C160A42@fugue.com> <alpine.DEB.2.02.1502191235240.4007@uplift.swm.pp.se> <87zj89gaqm.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191804050.4007@uplift.swm.pp.se> <D10B8924.6BD5%John_Leddy@cable.comcast.com> <87h9uhg529.wl-jch@pps.univ-paris-diderot.fr> <87fva1fzwp.wl-jch@pps.univ-paris-diderot.fr> <CAA93jw57sNMPsKkL-W2m3s20DKsFZWNeGZSOgnmRTj3yz+Rgmg@mail.gmail.com> <EA20D83F-3E46-4484-AD65-518B1C3836DA@inf-net.nl> <87zj89ed6c.wl-jch@pps.univ-paris-diderot.fr> <86026D9A-78BB-4E5B-A6AA-27FB2E02441F@inf-net.nl> <CAGnRvuobcSA1wP__rscE+UAMAuxEgOqML5Ute1qcFLSHh+kLng@mail.gmail.com> <FA70CC1E-37E4-4824-A9F3-9711F1F84777@inf-net.nl> <CAGnRvuqUSXpTPCqG4fsNHA=tsge=FvUUXuouwoVsRy1Cw3-cug@mail.gmail.com>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Fri, 20 Feb 2015 17:25:30 +0100 (CET)
X-Miltered: at korolev with ID 54E75FFA.002 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54E75FFA.002 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54E75FFA.002 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/5eXv-Y4Q6H72jSFivMgLLLH4Oqw>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Teco Boot <teco@inf-net.nl>
Subject: Re: [homenet] More about marginal links [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 16:25:34 -0000

> If you have hardware with a built-in switch that can report the link-speed,

The WNDR3700v2 under OpenWRT appears to do so:

    # swconfig dev switch0 show | grep 'link:'
    link: port:0 link:down
    link: port:1 link:down
    link: port:2 link:up speed:100baseT full-duplex 
    link: port:3 link:down
    link: port:4 link:down
    link: port:5 link:up speed:1000baseT full-duplex txflow rxflow auto

but to use this information, you need to know:

  1. that vlan1 on eth0 is connected to ports 0 through 3 of switch0;
  2. that neighbour fe80::dead:beef is connected over port 2.

You could do (1) with a small amount of model-specific code (yuck), but
I have no idea how to do (2).  Consult the ND cache to find out the
neighbour's MAC, then find a way to snoop on the switch's forwarding table?

-- Juliusz


From nobody Fri Feb 20 08:33:28 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 B1C621A6EF0 for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 08:33:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35] autolearn=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 VP_pECrUXJmG for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 08:33:26 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 1D4601A877A for <homenet@ietf.org>; Fri, 20 Feb 2015 08:33:23 -0800 (PST)
Received: from potemkin.univ-paris7.fr (potemkin.univ-paris7.fr [IPv6:2001:660:3301:8000::1:1]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t1KGXHVu000662 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 20 Feb 2015 17:33:17 +0100
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by potemkin.univ-paris7.fr (8.14.4/8.14.4/relay2/56228) with ESMTP id t1KGXHo8009968; Fri, 20 Feb 2015 17:33:17 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 9947D2BFCE4; Fri, 20 Feb 2015 17:33:17 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id kLjAZg1lNoXe; Fri, 20 Feb 2015 17:33:16 +0100 (CET)
Received: from pirx.pps.jussieu.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 1F28B2BFCE1; Fri, 20 Feb 2015 17:33:15 +0100 (CET)
Date: Fri, 20 Feb 2015 17:33:16 +0100
Message-ID: <87oaooczlf.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: "Leddy, John" <John_Leddy@cable.comcast.com>
In-Reply-To: <D10CC5CF.6EBF%John_Leddy@cable.comcast.com>
References: <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <8B98F698-983D-4D2A-B5D1-7ACED27C275E@fugue.com> <alpine.DEB.2.02.1502191920560.4007@uplift.swm.pp.se> <CAPRuP3mpNJTu6mP+RAVKKO0kt60PogNtNbCUCRRqxe9im3EzjA@mail.gmail.com> <20150220144138.GD8096@cisco.com> <D10CC5CF.6EBF%John_Leddy@cable.comcast.com>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]); Fri, 20 Feb 2015 17:33:17 +0100 (CET)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Fri, 20 Feb 2015 17:33:17 +0100 (CET)
X-Miltered: at korolev with ID 54E761CD.003 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 54E761CD.002 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54E761CD.003 from potemkin.univ-paris7.fr/potemkin.univ-paris7.fr/null/potemkin.univ-paris7.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Enveloppe: 54E761CD.002 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54E761CD.003 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 54E761CD.002 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/WHvU668jw8FO0PSw1HEGXaIMi1o>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 16:33:27 -0000

> Has the group considered a Bier model for multicast in the home?

As in a place where you put dead people?

Please explain.

-- Juliusz


From nobody Fri Feb 20 08:39:51 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 3489A1A0113 for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 08:39:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35] autolearn=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 L281yd8RplTj for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 08:39:49 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 EC3041A00FE for <homenet@ietf.org>; Fri, 20 Feb 2015 08:39:48 -0800 (PST)
Received: from potemkin.univ-paris7.fr (potemkin.univ-paris7.fr [IPv6:2001:660:3301:8000::1:1]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t1KGdhWi004771 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 20 Feb 2015 17:39:43 +0100
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by potemkin.univ-paris7.fr (8.14.4/8.14.4/relay2/56228) with ESMTP id t1KGdhkE013904; Fri, 20 Feb 2015 17:39:43 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 8C5B82BFCE5; Fri, 20 Feb 2015 17:39:43 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id sBm4bfcy_LcP; Fri, 20 Feb 2015 17:39:42 +0100 (CET)
Received: from pirx.pps.jussieu.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 040E22BFCD9; Fri, 20 Feb 2015 17:39:41 +0100 (CET)
Date: Fri, 20 Feb 2015 17:39:43 +0100
Message-ID: <87mw48czao.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Ole Troan <otroan@employees.org>
In-Reply-To: <82E892D5-98C3-4DD8-9E78-A754D77A5AF6@employees.org>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <8B98F698-983D-4D2A-B5D1-7ACED27C275E@fugue.com> <alpine.DEB.2.02.1502191920560.4007@uplift.swm.pp.se> <CAPRuP3mpNJTu6mP+RAVKKO0kt60PogNtNbCUCRRqxe9im3EzjA@mail.gmail.com> <alpine.DEB.2.02.1502201042330.4007@uplift.swm.pp.se> <7A86BDC6-FF4B-49FF-B59C-BA1DEF463173@inf-net.nl> <alpine.DEB.2.02.1502201310050.4007@uplift.swm.pp.se> <09793905-8D12-49E0-A040-490F617C87FF@inf-net.nl>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]); Fri, 20 Feb 2015 17:39:43 +0100 (CET)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Fri, 20 Feb 2015 17:39:43 +0100 (CET)
X-Miltered: at korolev with ID 54E7634F.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 54E7634F.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54E7634F.000 from potemkin.univ-paris7.fr/potemkin.univ-paris7.fr/null/potemkin.univ-paris7.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Enveloppe: 54E7634F.001 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54E7634F.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 54E7634F.001 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/8vaz-_hstoQ8cSR_tPpFzz1zHjo>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 16:39:50 -0000

> L3 - route injection (got a routing protocol there already, use it)

Yes, just put a stub router on the host and advertise /128.

As far as I'm aware, current HNCP doesn't provide a way for a host to
request a subnet-independent /128.  What's the thinking on that?  Just
grab a /128 from whichever subnet you happen to be connected to at boot,
and advertise that?

> L3.5 - SHIM6. not deployable
> L4/L5 - MP-TCP
> L5/L7  - MOSH

I don't think that's specific to Homenet -- being able to deal with
multiple addresses that change over time is something that our stacks
don't deal with very well.

-- Juliusz


From nobody Fri Feb 20 08:47:13 2015
Return-Path: <mellon@fugue.com>
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 190561A0187 for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 08:47:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 lUl0nyxeJDJf for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 08:47:10 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id BD33D1A0167 for <homenet@ietf.org>; Fri, 20 Feb 2015 08:47:10 -0800 (PST)
Received: from [10.0.20.107] (c-71-233-43-215.hsd1.nh.comcast.net [71.233.43.215]) by toccata.fugue.com (Postfix) with ESMTPSA id 8BBF3238059C; Fri, 20 Feb 2015 11:47:09 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <87oaooczlf.wl-jch@pps.univ-paris-diderot.fr>
Date: Fri, 20 Feb 2015 11:46:18 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <99D01EFA-4E6C-43F8-BE7F-29EB203F34A0@fugue.com>
References: <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <8B98F698-983D-4D2A-B5D1-7ACED27C275E@fugue.com> <alpine.DEB.2.02.1502191920560.4007@uplift.swm.pp.se> <CAPRuP3mpNJTu6mP+RAVKKO0kt60PogNtNbCUCRRqxe9im3EzjA@mail.gmail.com> <20150220144138.GD8096@cisco.com> <D10CC5CF.6EBF%John_Leddy@cable.comcast.com> <87oaooczlf.wl-jch@pps.univ-paris-diderot.fr>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/tPur7uXQN4vtiT499sQ-ANRbXNM>
Cc: "Leddy, John" <John_Leddy@cable.comcast.com>, "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 16:47:12 -0000

On Feb 20, 2015, at 11:33 AM, Juliusz Chroboczek =
<jch@pps.univ-paris-diderot.fr> wrote:
>> Has the group considered a Bier model for multicast in the home?
>=20
> As in a place where you put dead people?

Bier is a new working group in the routing area.

https://datatracker.ietf.org/wg/bier/charter/


From nobody Fri Feb 20 08:50:17 2015
Return-Path: <dave.taht@gmail.com>
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 D58E81A0368 for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 08:50:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 WNmkwD0npME6 for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 08:50:14 -0800 (PST)
Received: from mail-oi0-x22e.google.com (mail-oi0-x22e.google.com [IPv6:2607:f8b0:4003:c06::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 540701A00FE for <homenet@ietf.org>; Fri, 20 Feb 2015 08:50:11 -0800 (PST)
Received: by mail-oi0-f46.google.com with SMTP id x69so3520633oia.5 for <homenet@ietf.org>; Fri, 20 Feb 2015 08:50:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=R9OEztNPWpV5tSzmH9OXp6tu4tNOHtkJ51JyPKYE/Ak=; b=qJQ2S18GsDjcts/ay0bia0IkwOdyXsLSqZqEkYYCBhb72y2C6otcT/nnIaJyrDj+kZ 8WMPQMpLJvUxXcyiVrzNbMJWXIhXj79IvEfDdli4C8Ew/YdikMNmWCOJwiRgIMhOb8be 3seQzoEaeMu91z6oDuvQPTJfqJGs3S9A5yCl9KrqTA7n4Z1Bmt3gXQMQOVaQ76VvFeXp 56gwz9fsfZCCWZZfQHHK2vYrKIE6hLHDWTk4rfBadxcEXbjZtmxPDKH/Qf4nfyGnItsL NJ7WSGJ98QWWcO5XvpgjoI/Al/NIvyuACPtCJScvjcGR4PGTahLxZ4wp2qc7WB1uW9si 86AA==
MIME-Version: 1.0
X-Received: by 10.202.111.131 with SMTP id v3mr6632633oik.133.1424451010544; Fri, 20 Feb 2015 08:50:10 -0800 (PST)
Received: by 10.202.51.66 with HTTP; Fri, 20 Feb 2015 08:50:10 -0800 (PST)
Date: Fri, 20 Feb 2015 08:50:10 -0800
Message-ID: <CAA93jw7eGxPBNX+5LqX+qTYfRxNDxQpKo1fecUa2XH3bAKgvQQ@mail.gmail.com>
From: Dave Taht <dave.taht@gmail.com>
To: HOMENET <homenet@ietf.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/TDdDdhVTpbdtglWFVruXJCR6nU0>
Subject: [homenet] A poll
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 16:50:16 -0000

The homenet working group has been laboring for several years now to
find ways to make ipv6 more deployable to home (and presumably small
business) users.

In addition to multiple specification documents some code has been
produced to try and make things easier. At least in the USA, comcast
has rolled out IPv6 to everyone that can get dhcpv6 to sort of work on
their router, and/or is willing to install a custom firmware on their
router to get that, and of course tunneling ipv6 is possible if the
ISP does not support it.

So a quick poll:

0) Have you managed to get ipv6 working at all? If so, how? What sort
of problems did you encounter?

1) Have you attempted to deploy a routing protocol in your home? Which
one, and why?

2) Have you attempted to get hnetd's prefix distribution system
working? (it supports linux mainline and openwrt presently)

3) Do you use ethernet? How many clients in your home are ethernet connecte=
d?

4) Do you use wifi? How many clients are wifi connected? Do you use
range extenders?

5) How many devices do you think you will have connected to the
network in your home in 5 years? How many now?

6) Do you use any other network connected technologies (homeplug,
802.14, LTE, etc). If so, which ones, and why?

7) Do you use mdns service discovery?

8) Why are you here? (especially, if your answers to 0-2, are "no")


--=20
Dave T=C3=A4ht

http://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks


From nobody Fri Feb 20 08:51:13 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 30EBD1A1B5E for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 08:51:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35] autolearn=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 fqzykleOmUzh for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 08:51:11 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 C9B141A1B6F for <homenet@ietf.org>; Fri, 20 Feb 2015 08:51:03 -0800 (PST)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t1KGp2ha011438; Fri, 20 Feb 2015 17:51:02 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 6516C2BFCE3; Fri, 20 Feb 2015 17:51:02 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id RGO3L2UxnwVU; Fri, 20 Feb 2015 17:51:00 +0100 (CET)
Received: from pirx.pps.jussieu.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id BACF62BFCE5; Fri, 20 Feb 2015 17:51:00 +0100 (CET)
Date: Fri, 20 Feb 2015 17:51:02 +0100
Message-ID: <87lhjscyrt.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Mikael Abrahamsson <swmike@swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Fri, 20 Feb 2015 17:51:02 +0100 (CET)
X-Miltered: at korolev with ID 54E765F6.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54E765F6.001 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54E765F6.001 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/zujXS_tyJW__CMAiVpd-wMbcCTI>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 16:51:12 -0000

> I am not mandating that each and every device is in its own broadcast
> domain, I am however advocating that we leave the model that has been
> prevalent for 10-15 years at least, ie that a home gateway has a "WAN"
> port and 4 "LAN" ports, and these 4 ports are bridged.

You certainly have a point -- that's something we never discussed, and it
appears that there's no consensus.

> I'm saying the typical device should have 4-5 "L3" ports. You're then
> free to connect one of these to your L2 switch if you so please.

I'll just point out that on all the hardware I know this is
configurable -- it's quite possible to set up an OpenWRT router to put
each Ethernet port on a different VLAN.

So perhaps a Homenet router could ship with the LAN ports bridged, and
have a configuratifon option somewhere in the "Beware the tiger" tab of
the "Advanced" menu that allows unbridging selected ports?

(I'm sure somebody will point out that the right configuration could be
chosen automatically, but I'm not sure I'm comfortable with the set of
interfaces changing at runtime on a home router.)

-- Juliusz


From nobody Fri Feb 20 08:58:50 2015
Return-Path: <sander@steffann.nl>
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 8B04F1A07BE for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 08:58:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.094
X-Spam-Level: 
X-Spam-Status: No, score=0.094 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_NL=0.55, HOST_EQ_NL=1.545, SPF_PASS=-0.001] autolearn=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 EKyGkJWbpIWH for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 08:58:47 -0800 (PST)
Received: from mail.sintact.nl (mail.sintact.nl [IPv6:2001:9e0:803::6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A64AD1A0126 for <homenet@ietf.org>; Fri, 20 Feb 2015 08:58:47 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.sintact.nl (Postfix) with ESMTP id 583E13E; Fri, 20 Feb 2015 17:58:45 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=steffann.nl; h= x-mailer:references:message-id:content-transfer-encoding:date :date:in-reply-to:from:from:subject:subject:mime-version :content-type:content-type:received:received; s=mail; t= 1424451523; bh=RrcJydy1N/XIdVSEtfL5j2qIHBKLo+xYc/QinBiWbYc=; b=d RdfJt5ex0DlrLPFGxep2hjFWnd6Umzw7NiJ5BhcE2CHXT1du0XGBX9bIqkBvZ2Qr ITDJYJzbnb4aoPhJzmf2Z85HEtXJqBIjtgvwgwWVSEzeVtjFKtcWQL4DLnsRIWyB f3sNto2sGFtodUmoUICccipBYxwYWDfJWhDKTiRycU=
X-Virus-Scanned: Debian amavisd-new at mail.sintact.nl
Received: from mail.sintact.nl ([127.0.0.1]) by localhost (mail.sintact.nl [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id Ni2xPJF6vr56; Fri, 20 Feb 2015 17:58:43 +0100 (CET)
Received: from [IPv6:2a00:8640:1::5cd:9639:f69d:258e] (unknown [IPv6:2a00:8640:1:0:5cd:9639:f69d:258e]) by mail.sintact.nl (Postfix) with ESMTPSA id 1476E37; Fri, 20 Feb 2015 17:58:42 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2081\))
From: Sander Steffann <sander@steffann.nl>
In-Reply-To: <2D09D61DDFA73D4C884805CC7865E61130F303F4@GAALPA1MSGUSRBF.ITServices.sbc.com>
Date: Fri, 20 Feb 2015 17:58:42 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <DB65E83A-4CB8-4E3A-9FC7-C1585A4A7552@steffann.nl>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <54E58238.9030809@mtcc.com> <874mqigcct.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191622510.4007@uplift.swm.pp.se> <87vbixg9fe.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191806381.4007@uplift.swm.pp.se> <87lhjtg6jc.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191826230.4007@uplift.swm.pp.se> <2FE73365-ECD7-49C3-8476-934CD1032542@fugue.com> <alpine.DEB.2.02.1502191924250.4007@uplift.swm.pp.se> <DE5D415F-4804-44C2-9621-523C3EFBC859@fugue.com> <DD0D0BE4-3753-4305-85D5-00CC8A37D045@steffann.nl> <2D09D61DDFA73D4C884805CC7865E61130F303F4@GAALPA1MSGUSRBF.ITServices.sbc .com>
To: "STARK, BARBARA H" <bs7652@att.com>
X-Mailer: Apple Mail (2.2081)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/wKdF6yuS5DmWSJSMmJjtKeRdVps>
Cc: "homenet@ietf.org" <homenet@ietf.org>, Ted Lemon <mellon@fugue.com>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 16:58:49 -0000

Hi Barbara,

> OTT video does not use multicast. IPTV deployments do use multicast. =
Those that I'm aware of require use of the provider-supplied CE router, =
which has an IGMP proxy (and MLD proxy if IPv6 multicast is supported) =
for LAN-to-WAN multicast management. Where Wi-Fi distribution of these =
multicast streams is supported, it is only done on a dedicated (and =
highly managed and somewhat proprietary) Wi-Fi network, that is distinct =
from the general-purpose (and not "professionally" managed) Wi-Fi =
network. The LAN interfaces of the provider-supplied CE router do tend =
to have IGMP/MLD snooping, to keep from flooding the general-purpose =
network interfaces with large multicast streams. There may also be a =
coax networking interface. If there is, this also tends to be dedicated =
and highly managed. Where Ethernet is used for distribution of =
multicast, it is done so that the provider STBs are all attached to the =
provider CE router via the same Ethernet port (and no other devices use =
that port) and there are no intervening routers. I mentioned at the last =
IETF that I expect some "home networks" to have managed and unmanaged =
segments. I don't consider the dedicated, managed segments to be part of =
the homenet domain. I would hope that the provider-supplied CE router =
would support homenet on its general purpose network interfaces.=20
>=20
> I'd be curious to learn about multicast IPTV deployments that allow =
users to supply their own CE routers and send multicast streams on =
network segments that are also used for general-purpose home networking =
(especially general-purpose Wi-Fi networks).=20

The above is correct. Provider-supplied CPEs are currently necessary and =
intermediate routers are not supported. The TV streams can be on a =
separate VLAN. But this is what is currently done because of the =
difficulty of doing it over the regular home network. It doesn't mean we =
should design Homenet in the same way. I'd rather see that providers =
supply Homenet routers to their customers and that the multicast TV =
streams just work.

Cheers,
Sander


From nobody Fri Feb 20 09:03:31 2015
Return-Path: <bs7652@att.com>
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 1325B1A1A58 for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 09:03:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.61
X-Spam-Level: 
X-Spam-Status: No, score=-3.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_44=0.6, RCVD_IN_DNSWL_MED=-2.3, 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 lPToRvXyfP0o for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 09:03:28 -0800 (PST)
Received: from nbfkord-smmo07.seg.att.com (nbfkord-smmo07.seg.att.com [209.65.160.93]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 99B6D1A0AC8 for <homenet@ietf.org>; Fri, 20 Feb 2015 09:03:23 -0800 (PST)
Received: from unknown [144.160.229.23] (EHLO alpi154.enaf.aldc.att.com) by nbfkord-smmo07.seg.att.com(mxl_mta-7.2.4-5) with ESMTP id bd867e45.2b5e9ee0a940.3057873.00-2421.8643710.nbfkord-smmo07.seg.att.com (envelope-from <bs7652@att.com>);  Fri, 20 Feb 2015 17:03:23 +0000 (UTC)
X-MXL-Hash: 54e768db5430f956-94cc4c98d297653ba95fd83c003ea33147a0f13a
Received: from unknown [144.160.229.23] (EHLO alpi154.enaf.aldc.att.com) by nbfkord-smmo07.seg.att.com(mxl_mta-7.2.4-5) over TLS secured channel with ESMTP id 7c867e45.0.3057710.00-2307.8643246.nbfkord-smmo07.seg.att.com (envelope-from <bs7652@att.com>);  Fri, 20 Feb 2015 17:03:06 +0000 (UTC)
X-MXL-Hash: 54e768ca02b0b970-567220468101498e5b554c530ce3eadeb3b36d07
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id t1KH32TD027235; Fri, 20 Feb 2015 12:03:02 -0500
Received: from alpi131.aldc.att.com (alpi131.aldc.att.com [130.8.218.69]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id t1KH2llH026951 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 20 Feb 2015 12:02:50 -0500
Received: from GAALPA1MSGHUBAH.ITServices.sbc.com (GAALPA1MSGHUBAH.itservices.sbc.com [130.8.218.157]) by alpi131.aldc.att.com (RSA Interceptor); Fri, 20 Feb 2015 17:02:29 GMT
Received: from GAALPA1MSGUSRBF.ITServices.sbc.com ([169.254.5.126]) by GAALPA1MSGHUBAH.ITServices.sbc.com ([130.8.218.157]) with mapi id 14.03.0224.002; Fri, 20 Feb 2015 12:02:28 -0500
From: "STARK, BARBARA H" <bs7652@att.com>
To: "'Teco Boot'" <teco@inf-net.nl>
Thread-Topic: [homenet] More about marginal links [was: Routing protocol comparison document]
Thread-Index: AQHQTIdQZefVGhBdf0KPcU80Od5Vz5z44AkAgAC9D4CAAGUqgP//sTiA
Date: Fri, 20 Feb 2015 17:02:28 +0000
Message-ID: <2D09D61DDFA73D4C884805CC7865E61130F30472@GAALPA1MSGUSRBF.ITServices.sbc.com>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <A5767F83-3D0C-40E5-A73B-912E3C160A42@fugue.com> <alpine.DEB.2.02.1502191235240.4007@uplift.swm.pp.se> <87zj89gaqm.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191804050.4007@uplift.swm.pp.se> <D10B8924.6BD5%John_Leddy@cable.comcast.com> <87h9uhg529.wl-jch@pps.univ-paris-diderot.fr> <87fva1fzwp.wl-jch@pps.univ-paris-diderot.fr> <CAA93jw57sNMPsKkL-W2m3s20DKsFZWNeGZSOgnmRTj3yz+Rgmg@mail.gmail.com> <EA20D83F-3E46-4484-AD65-518B1C3836DA@inf-net.nl> <2D09D61DDFA73D4C884805CC7865E61130F3037C@GAALPA1MSGUSRBF.ITServices.sbc.com> <FA674A21-8D36-43C9-ABF3-3E303EEB1397@inf-net.nl>
In-Reply-To: <FA674A21-8D36-43C9-ABF3-3E303EEB1397@inf-net.nl>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.61.166.72]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-AnalysisOut: [v=2.0 cv=KNft+i5o c=1 sm=1 a=VXHOiMMwGAwA+y4G3/O+aw==:17 a]
X-AnalysisOut: [=vKzWRVGcsRAA:10 a=BLceEmwcHowA:10 a=kj9zAlcOel0A:10 a=zQP]
X-AnalysisOut: [7CpKOAAAA:8 a=XIqpo32RAAAA:8 a=0HtSIViG9nkA:10 a=zpQLb2yjo]
X-AnalysisOut: [NmmCEORV6cA:9 a=CjuIK1q_8ugA:10]
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2014051901)]
X-MAIL-FROM: <bs7652@att.com>
X-SOURCE-IP: [144.160.229.23]
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/MSFhuxnHHzGrsh39EHek3SW2HA4>
Cc: "Leddy, John" <John_Leddy@cable.comcast.com>, "homenet@ietf.org Group" <homenet@ietf.org>, Dave Taht <dave.taht@gmail.com>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] More about marginal links [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 17:03:30 -0000

> > Does it need to be a routing protocol? Just to throw another possible
> > protocol into the mix being tossed around (like we don't have enough),
>=20
> I don't think current protocols used by ISPs or enterprises fits our plug=
&play
> requirements. Also, there is a lot more wireless in homes. That doesn't m=
ean
> we cannot build on current protocols.

??? Huh? IEEE 1905.1 is being pushed by the likes of Broadcom, Qualcomm, MS=
tar Semiconductor. They've suggested they want to have it in their Wi-Fi, M=
oCA, HomePlug, and Ethernet products, that are targeted at the CE industry.=
 The certification is being offered by HomePlug Alliance. While Orange and =
AT&T have expressed an interest (because helping customers with their home =
networking issues is a huge customer care cost), I wouldn't call a "protoco=
l used by ISPs". And enterprises?! I don't think so. Enterprises are defini=
tely *not* the target audience.

> > I'd like to suggest that a non-routing protocol be considered for topol=
ogy
> discovery and sharing of link metrics. Specifically, IEEE 1905.1a could h=
elp with
> this. It can provide L1 and L2 topology info with link metrics, and ident=
ify
> intervening bridges that support LLDP for IEEE 802.1 bridge discovery. I
> wouldn't want individual devices all doing their own 1905 topology discov=
ery -
> - that's too chatty. But if the all the homenet routers did, and then adv=
ertised
> a "service" (DNS-SD) that provided a link to a router-provider HTML page
> with the topology and metric info the router can discover provided in a
> standardized XML or JSON syntax, then everything who can discover that
> service (on each router) would have access to this info. Applications cou=
ld
> also make use of this info to do intelligent source address selection in =
a multi-
> WAN-interface network, because routers could report on the speed of their
> WAN connections, as well.
>=20
> My thoughts are as follows: sub-IP mechanisms provide usable metrics.
> Somewhere, near to L3 routing, this information is translated to a
> dimensionless cost metric for each link, where a link is a sub-IP path be=
tween
> two routers. Cost is not symmetric, cost A->B can differ from B->A. It is=
 the
> routing protocol to distribute this information in the routing domain.

I don't understand your point here, and whether you're trying to calculate =
the cost of running a L7 (application) protocol, or the relative cost of us=
ing different routes? Note that all protocols used to supply info to routin=
g configuration applications are operating at the application layer (L7). H=
NCP is a L7 protocol. IEEE 1905.1 is a L7 protocol. As are IS-IS, and HTTP.=
 The question is "what information does a router's routing configuration ap=
plication need to properly configure routing behavior?" Once you figure out=
 the info you need, then you can figure out the various options for getting=
 that info to the router. It's not always necessary to multicast or broadca=
st all the information all over the place. Sometimes it's enough (and more =
efficient) to broadcast the existence (and where to get) the information, a=
nd then just let routers (or other devices) who want the info to go and ask=
 for the info (unicast). If info changes, you can broadcast a message sayin=
g something changed, and then let interested devices query to find out what=
 the change was. You could even stick a "for more info" TLV in HNCP that su=
pplies the URL of a router's info-providing web page.
Barbara


From nobody Fri Feb 20 09:05:00 2015
Return-Path: <gettysjim@gmail.com>
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 30E341A0187 for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 09:04:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level: 
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 ZPAy78CGd5A0 for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 09:04:56 -0800 (PST)
Received: from mail-ob0-x22b.google.com (mail-ob0-x22b.google.com [IPv6:2607:f8b0:4003:c01::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1F3671A039D for <homenet@ietf.org>; Fri, 20 Feb 2015 09:04:56 -0800 (PST)
Received: by mail-ob0-f171.google.com with SMTP id gq1so25433595obb.2 for <homenet@ietf.org>; Fri, 20 Feb 2015 09:04:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=mB4j1DKVxBjTus0hmq3pS6jh5SnarJXiaaTr/2wqGDQ=; b=t50ulonBM/LnhuyoF13a86KMbINVI+WKW1wszBK02X9IYfGdHswxYxMVO9LFRdy19C 3qm76J2+XMi0cooC1FvHlif3L/G5dWSXoKpl5d3kHEXHfjSDdz/ikfjaokV/JsW4UlQr DPwFCy+5cUGFuChYidGck3g/UleJjLtLfmCGZs65z/b4gUkGiYfDcJHMeaRTM44s3+sT tUTLHRQJg4Pct7wzPgPADjB8oktxL/0TRF8B1MtGIjsdgNem/q5OJGhsP6zbakVBQatR r5tomhfQ/UvEV/EO9Q6MLA0tc5sDD6V7zy+E/O1b3jiJ/avC15GsbN3P0+zEwAkCBg82 vNVQ==
MIME-Version: 1.0
X-Received: by 10.182.119.232 with SMTP id kx8mr7096749obb.37.1424451895404; Fri, 20 Feb 2015 09:04:55 -0800 (PST)
Sender: gettysjim@gmail.com
Received: by 10.76.76.5 with HTTP; Fri, 20 Feb 2015 09:04:55 -0800 (PST)
In-Reply-To: <CAA93jw7eGxPBNX+5LqX+qTYfRxNDxQpKo1fecUa2XH3bAKgvQQ@mail.gmail.com>
References: <CAA93jw7eGxPBNX+5LqX+qTYfRxNDxQpKo1fecUa2XH3bAKgvQQ@mail.gmail.com>
Date: Fri, 20 Feb 2015 12:04:55 -0500
X-Google-Sender-Auth: NvhWToIUZBK8bCOBXHdrXIeGyMU
Message-ID: <CAGhGL2ALQpb0pfRe1NU6gFdLZR9T-_OSdMnAUVfN4ZOO0zzi4w@mail.gmail.com>
From: Jim Gettys <jg@freedesktop.org>
To: Dave Taht <dave.taht@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c2f43a39ad84050f880dd7
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/h1HNjXfrUyMXEdx_g-mmMZQ9tIU>
Cc: HOMENET <homenet@ietf.org>
Subject: Re: [homenet] A poll
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 17:04:58 -0000

--001a11c2f43a39ad84050f880dd7
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Fri, Feb 20, 2015 at 11:50 AM, Dave Taht <dave.taht@gmail.com> wrote:

> The homenet working group has been laboring for several years now to
> find ways to make ipv6 more deployable to home (and presumably small
> business) users.
>
> In addition to multiple specification documents some code has been
> produced to try and make things easier. At least in the USA, comcast
> has rolled out IPv6 to everyone that can get dhcpv6 to sort of work on
> their router, and/or is willing to install a custom firmware on their
> router to get that, and of course tunneling ipv6 is possible if the
> ISP does not support it.
>
> So a quick poll:
>
> 0) Have you managed to get ipv6 working at all? If so, how? What sort
> of problems did you encounter?
>

=E2=80=8BYes.  Both hurricane electric tunnel=E2=80=8B

=E2=80=8Band Comcast native IPv6.

Getting the HE tunnel configured properly is somewhat a pain, as the
terminology on OpenWrt is slightly different than that used by HE.

The native IPv6 from Comcast has been fine.=E2=80=8B

>
> 1) Have you attempted to deploy a routing protocol in your home? Which
> one, and why?
>

=E2=80=8BBabel.  Out of the box in CeroWrt.=E2=80=8B


>
> 2) Have you attempted to get hnetd's prefix distribution system
> working? (it supports linux mainline and openwrt presently)
>
> 3) Do you use ethernet? How many clients in your home are ethernet
> connected?
>

=E2=80=8BDunno exactly.  Probably around 8-10 devices.=E2=80=8B


>
> 4) Do you use wifi?

=E2=80=8BYes.=E2=80=8B


> How many clients are wifi connected?


=E2=80=8Bmaybe 8-10 devices.=E2=80=8B



> Do you use
> range extenders?
>

=E2=80=8BNo
=E2=80=8B


>
> 5) How many devices do you think you will have connected to the
> network in your home in 5 years?


=E2=80=8B25.=E2=80=8B



> How many now?
>

=E2=80=8BMaybe 16.=E2=80=8B


>
> 6) Do you use any other network connected technologies (homeplug,
> 802.14, LTE, etc). If so, which ones, and why?
>

=E2=80=8BNo.
=E2=80=8B


>
> 7) Do you use mdns service discovery?
>

=E2=80=8BYes.
=E2=80=8B


>
> 8) Why are you here? (especially, if your answers to 0-2, are "no")
>
>
> --
> Dave T=C3=A4ht
>
> http://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks
>
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>

--001a11c2f43a39ad84050f880dd7
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small"><br=
></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Fri, Fe=
b 20, 2015 at 11:50 AM, Dave Taht <span dir=3D"ltr">&lt;<a href=3D"mailto:d=
ave.taht@gmail.com" target=3D"_blank">dave.taht@gmail.com</a>&gt;</span> wr=
ote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border=
-left:1px #ccc solid;padding-left:1ex">The homenet working group has been l=
aboring for several years now to<br>
find ways to make ipv6 more deployable to home (and presumably small<br>
business) users.<br>
<br>
In addition to multiple specification documents some code has been<br>
produced to try and make things easier. At least in the USA, comcast<br>
has rolled out IPv6 to everyone that can get dhcpv6 to sort of work on<br>
their router, and/or is willing to install a custom firmware on their<br>
router to get that, and of course tunneling ipv6 is possible if the<br>
ISP does not support it.<br>
<br>
So a quick poll:<br>
<br>
0) Have you managed to get ipv6 working at all? If so, how? What sort<br>
of problems did you encounter?<br></blockquote><div><br></div><div><div cla=
ss=3D"gmail_default" style=3D"font-size:small;display:inline">=E2=80=8BYes.=
=C2=A0 Both hurricane electric tunnel=E2=80=8B</div>=C2=A0<div class=3D"gma=
il_default" style=3D"font-size:small;display:inline">=E2=80=8Band Comcast n=
ative IPv6.</div></div><div><div class=3D"gmail_default" style=3D"font-size=
:small;display:inline"><br></div></div><div><div class=3D"gmail_default" st=
yle=3D"font-size:small;display:inline">Getting the HE tunnel configured pro=
perly is somewhat a pain, as the terminology on OpenWrt is slightly differe=
nt than that used by HE.</div></div><div><div class=3D"gmail_default" style=
=3D"font-size:small;display:inline"><br></div></div><div><div class=3D"gmai=
l_default" style=3D"font-size:small;display:inline">The native IPv6 from Co=
mcast has been fine.=E2=80=8B</div></div><blockquote class=3D"gmail_quote" =
style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
1) Have you attempted to deploy a routing protocol in your home? Which<br>
one, and why?<br></blockquote><div><br></div><div><div class=3D"gmail_defau=
lt" style=3D"font-size:small;display:inline">=E2=80=8BBabel.=C2=A0 Out of t=
he box in CeroWrt.=E2=80=8B</div>=C2=A0</div><blockquote class=3D"gmail_quo=
te" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"=
>
<br>
2) Have you attempted to get hnetd&#39;s prefix distribution system<br>
working? (it supports linux mainline and openwrt presently)<br>
<br>
3) Do you use ethernet? How many clients in your home are ethernet connecte=
d?<br></blockquote><div><br></div><div><div class=3D"gmail_default" style=
=3D"font-size:small;display:inline">=E2=80=8BDunno exactly.=C2=A0 Probably =
around 8-10 devices.=E2=80=8B</div>=C2=A0</div><blockquote class=3D"gmail_q=
uote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e=
x">
<br>
4) Do you use wifi? </blockquote><div><div class=3D"gmail_default" style=3D=
"font-size:small;display:inline">=E2=80=8BYes.=E2=80=8B</div>=C2=A0</div><b=
lockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px =
#ccc solid;padding-left:1ex">How many clients are wifi connected?</blockquo=
te><div><br></div><div><div class=3D"gmail_default" style=3D"font-size:smal=
l;display:inline">=E2=80=8Bmaybe 8-10 devices.=E2=80=8B</div>=C2=A0</div><d=
iv>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex">Do you use<br>
range extenders?<br></blockquote><div><br></div><div><div class=3D"gmail_de=
fault" style=3D"font-size:small;display:inline">=E2=80=8BNo</div></div><div=
><div class=3D"gmail_default" style=3D"font-size:small;display:inline">=E2=
=80=8B</div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0=
 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
5) How many devices do you think you will have connected to the<br>
network in your home in 5 years?</blockquote><div><br></div><div><div class=
=3D"gmail_default" style=3D"font-size:small;display:inline">=E2=80=8B25.=E2=
=80=8B</div>=C2=A0</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" =
style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">How=
 many now?<br></blockquote><div><br></div><div><div class=3D"gmail_default"=
 style=3D"font-size:small;display:inline">=E2=80=8BMaybe 16.=E2=80=8B</div>=
=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex">
<br>
6) Do you use any other network connected technologies (homeplug,<br>
802.14, LTE, etc). If so, which ones, and why?<br></blockquote><div><br></d=
iv><div><div class=3D"gmail_default" style=3D"font-size:small;display:inlin=
e">=E2=80=8BNo.</div></div><div><div class=3D"gmail_default" style=3D"font-=
size:small;display:inline">=E2=80=8B</div>=C2=A0</div><blockquote class=3D"=
gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-=
left:1ex">
<br>
7) Do you use mdns service discovery?<br></blockquote><div><br></div><div><=
div class=3D"gmail_default" style=3D"font-size:small;display:inline">=E2=80=
=8BYes.</div></div><div><div class=3D"gmail_default" style=3D"font-size:sma=
ll;display:inline">=E2=80=8B</div>=C2=A0</div><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex=
">
<br>
8) Why are you here? (especially, if your answers to 0-2, are &quot;no&quot=
;)<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
<br>
--<br>
Dave T=C3=A4ht<br>
<br>
<a href=3D"http://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks" t=
arget=3D"_blank">http://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Ta=
lks</a><br>
<br>
_______________________________________________<br>
homenet mailing list<br>
<a href=3D"mailto:homenet@ietf.org">homenet@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/homenet" target=3D"_blank"=
>https://www.ietf.org/mailman/listinfo/homenet</a><br>
</font></span></blockquote></div><br></div></div>

--001a11c2f43a39ad84050f880dd7--


From nobody Fri Feb 20 09:09:55 2015
Return-Path: <eckert@cisco.com>
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 016941A1B9C for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 09:09:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 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_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 nKWInmjhmF_E for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 09:09:52 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 180641A1F02 for <homenet@ietf.org>; Fri, 20 Feb 2015 09:09:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1673; q=dns/txt; s=iport; t=1424452181; x=1425661781; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=Dsdxo89ku/oJcf/WFEeALRERXlxTLTdEi6jpBFD0yEM=; b=RkfPiJZQ6ACVgiM4ooMutEU6oWBA3HEac6wHTL16MAC5nV5J0IwdGLDi sNbYNh5T/DBlOdvE1yjS3OsRGH3IzGYRdTq9nr6MrHL2VBcmVoyIZtpjV OcKiH9DAos2xT4RtW+tG66hM5ren0th4NWzZ8oV/DFSceolCfaD+LTDRn A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ANBQAYaedU/40NJK1bgwZSw1KFbwKBGEMBAQEBAQF8hBABAQQ6PxALGAklDwVJExuIFA3VIwEBAQEBAQEBAQEBAQEBAQEBAQEBAReLD4QGGk4HgxeBFAWKR4UIg12FZAGBU5FeIoICHIFxHTGCQwEBAQ
X-IronPort-AV: E=Sophos;i="5.09,615,1418083200"; d="scan'208";a="394702815"
Received: from alln-core-8.cisco.com ([173.36.13.141]) by rcdn-iport-9.cisco.com with ESMTP; 20 Feb 2015 17:09:40 +0000
Received: from mcast-linux1.cisco.com (mcast-linux1.cisco.com [172.27.244.121]) by alln-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id t1KH9d7A019430 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 20 Feb 2015 17:09:40 GMT
Received: from mcast-linux1.cisco.com (localhost.cisco.com [127.0.0.1]) by mcast-linux1.cisco.com (8.13.8/8.13.8) with ESMTP id t1KH9dcr021430; Fri, 20 Feb 2015 09:09:39 -0800
Received: (from eckert@localhost) by mcast-linux1.cisco.com (8.13.8/8.13.8/Submit) id t1KH9dME021429; Fri, 20 Feb 2015 09:09:39 -0800
Date: Fri, 20 Feb 2015 09:09:39 -0800
From: "'Toerless Eckert'" <eckert@cisco.com>
To: "STARK, BARBARA H" <bs7652@att.com>
Message-ID: <20150220170939.GF8096@cisco.com>
References: <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <8B98F698-983D-4D2A-B5D1-7ACED27C275E@fugue.com> <alpine.DEB.2.02.1502191920560.4007@uplift.swm.pp.se> <CAPRuP3mpNJTu6mP+RAVKKO0kt60PogNtNbCUCRRqxe9im3EzjA@mail.gmail.com> <alpine.DEB.2.02.1502201042330.4007@uplift.swm.pp.se> <20150220142041.GC8096@cisco.com> <2D09D61DDFA73D4C884805CC7865E61130F3035D@GAALPA1MSGUSRBF.ITServices.sbc.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <2D09D61DDFA73D4C884805CC7865E61130F3035D@GAALPA1MSGUSRBF.ITServices.sbc.com>
User-Agent: Mutt/1.4.2.2i
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/kT66tPrFj2MlFyszYUqmPUxHhDA>
Cc: Andrew Mcgregor <andrewmcgr@google.com>, "homenet@ietf.org Group" <homenet@ietf.org>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 17:09:54 -0000

Thanks, Barbara.

Lets hope UPnP/DLNA are starting to consider to cooperate with IETF on service
discovery.


On Fri, Feb 20, 2015 at 02:37:38PM +0000, STARK, BARBARA H wrote:
> > There are good proposal how to do servicce discovery in homenets or the
> > like with DNS-SD (/mDNS), but i think we should still worry about
> > compatibility with UPnP. Both of these requirements (UPnP and DNS-SD) are
> > IMHO better solved with router-level "proxy"
> > solutions than with ASM IP multicast.
> 
> FYI. I did a presentation to DLNA (which has a lot of key UPnP people) that warned them to start thinking about service discovery in the multi-router world, and the world where more and more Wi-Fi APs are limiting the multicast that makes it to Wi-Fi devices. I mentioned the DNS-SD proxy work, homenet, and told them:
> " - People have started to study the current quantity of multicast traffic and its impact on power consumption by battery-operated Wi-Fi devices.
> http://tools.ietf.org/html/draft-desmouceaux-ipv6-mcast-wifi-power-usage-00
> http://tools.ietf.org/html/draft-vyncke-6man-mcast-not-efficient-00
>  - Concern is growing and proposals are starting to appear for ways to decrease the quantity of multicast messages.
> http://tools.ietf.org/html/draft-yourtchenko-colitti-nd-reduce-multicast-00 "
> 
> My recommendations were that they had 2 basic options of either also supporting DNS-SD / mDNS for service discovery, or defining a SSDP proxy similar to what I expect will be done for DNS-SD. Anyway, I told them I'd keep them updated on the state of affairs regarding this issue.
> Barbara

-- 
---
Toerless Eckert, eckert@cisco.com


From nobody Fri Feb 20 09:25:16 2015
Return-Path: <bs7652@att.com>
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 701151A1BD7 for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 09:25:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level: 
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 XTxXt8jzAsNL for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 09:25:13 -0800 (PST)
Received: from nbfkord-smmo05.seg.att.com (nbfkord-smmo05.seg.att.com [209.65.160.92]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 17D941A0113 for <homenet@ietf.org>; Fri, 20 Feb 2015 09:25:13 -0800 (PST)
Received: from unknown [144.160.229.23] (EHLO alpi154.enaf.aldc.att.com) by nbfkord-smmo05.seg.att.com(mxl_mta-7.2.4-5) with ESMTP id 9fd67e45.2b598fc45940.3051165.00-2413.8640299.nbfkord-smmo05.seg.att.com (envelope-from <bs7652@att.com>);  Fri, 20 Feb 2015 17:25:13 +0000 (UTC)
X-MXL-Hash: 54e76df94f13b19f-4847ad51b10b378cea20c4a7a6313ffa5e8909fa
Received: from unknown [144.160.229.23] (EHLO alpi154.enaf.aldc.att.com) by nbfkord-smmo05.seg.att.com(mxl_mta-7.2.4-5) over TLS secured channel with ESMTP id eed67e45.0.3051023.00-2318.8639862.nbfkord-smmo05.seg.att.com (envelope-from <bs7652@att.com>);  Fri, 20 Feb 2015 17:25:03 +0000 (UTC)
X-MXL-Hash: 54e76def3b7f3ee9-2b142b0fff7e95bfd8d7253637d02ce86610714a
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id t1KHP2OT013030; Fri, 20 Feb 2015 12:25:02 -0500
Received: from alpi132.aldc.att.com (alpi132.aldc.att.com [130.8.217.2]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id t1KHOvSi012985 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 20 Feb 2015 12:24:57 -0500
Received: from GAALPA1MSGHUBAF.ITServices.sbc.com (GAALPA1MSGHUBAF.itservices.sbc.com [130.8.218.155]) by alpi132.aldc.att.com (RSA Interceptor); Fri, 20 Feb 2015 17:24:42 GMT
Received: from GAALPA1MSGUSRBF.ITServices.sbc.com ([169.254.5.126]) by GAALPA1MSGHUBAF.ITServices.sbc.com ([130.8.218.155]) with mapi id 14.03.0224.002; Fri, 20 Feb 2015 12:24:42 -0500
From: "STARK, BARBARA H" <bs7652@att.com>
To: "'Toerless Eckert'" <eckert@cisco.com>
Thread-Topic: [homenet] Routing protocol comparison document
Thread-Index: AQHQSU32GNhjW8WFi0qWgaveVMetmJz2sruAgAAaSQCAABl7AIAABlyAgAAB2ICAAHYtgIAAi9MAgACD2oCAAAHHgIAAAyGAgAAURoCAAA90gIAAAkAAgAABTQCAAAKJAIAAX5aAgAClmgCAAEmQgP//rgRwgACBMYD//6+rIA==
Date: Fri, 20 Feb 2015 17:24:42 +0000
Message-ID: <2D09D61DDFA73D4C884805CC7865E61130F304F9@GAALPA1MSGUSRBF.ITServices.sbc.com>
References: <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <8B98F698-983D-4D2A-B5D1-7ACED27C275E@fugue.com> <alpine.DEB.2.02.1502191920560.4007@uplift.swm.pp.se> <CAPRuP3mpNJTu6mP+RAVKKO0kt60PogNtNbCUCRRqxe9im3EzjA@mail.gmail.com> <alpine.DEB.2.02.1502201042330.4007@uplift.swm.pp.se> <20150220142041.GC8096@cisco.com> <2D09D61DDFA73D4C884805CC7865E61130F3035D@GAALPA1MSGUSRBF.ITServices.sbc.com> <20150220170939.GF8096@cisco.com>
In-Reply-To: <20150220170939.GF8096@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.61.166.72]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-AnalysisOut: [v=2.0 cv=EtBlW1gA c=1 sm=1 a=VXHOiMMwGAwA+y4G3/O+aw==:17 a]
X-AnalysisOut: [=vKzWRVGcsRAA:10 a=BLceEmwcHowA:10 a=kj9zAlcOel0A:10 a=zQP]
X-AnalysisOut: [7CpKOAAAA:8 a=XIqpo32RAAAA:8 a=0HtSIViG9nkA:10 a=mp_blKtQz]
X-AnalysisOut: [XvtfGqQBi4A:9 a=CjuIK1q_8ugA:10 a=_PnbvynV84gA:10 a=dajxVy]
X-AnalysisOut: [uvXMsA:10]
X-Spam: [F=0.2000000000; CM=0.500; S=0.200(2014051901)]
X-MAIL-FROM: <bs7652@att.com>
X-SOURCE-IP: [144.160.229.23]
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/_Gr1x6Mhu5rGWGs05ACsceyT6Yk>
Cc: Andrew Mcgregor <andrewmcgr@google.com>, "homenet@ietf.org Group" <homenet@ietf.org>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 17:25:14 -0000

> Lets hope UPnP/DLNA are starting to consider to cooperate with IETF on
> service discovery.

"Cooperate" is such a strong word. :) They are aware of the issue, they wil=
l be kept informed as to how the issue is progressing and what homenet and =
dnsext are doing to tackle the issue, and they know what their options are.
Barbara


From nobody Fri Feb 20 10:10:51 2015
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 701401A020A for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 10:10:50 -0800 (PST)
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 HHVkWANXU1dH for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 10:10:48 -0800 (PST)
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 0C8281A037C for <homenet@ietf.org>; Fri, 20 Feb 2015 10:10:43 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id DF7D1A2; Fri, 20 Feb 2015 19:10:41 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1424455841; bh=Er2Ghr6hhm7QLfTQ765Ow/bNHClTXNlIs/Uuvt4ID3A=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=wIGAEcSnVEBzOGHEpunWCoxcdZmN+l3w8G4Mk2rPrgExVjlsKxz8p+B09uef7xxLY Y6sSMdjdhmu+LLVZpSxx5co0lva/XDL4uRe0ZFSlQrIKavWH5F1jbZlKhsKfLbKTDm 0APfKCc4ylxoV6H+pmNNPjqXrYCgomSr1Q7SjtXo=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id D7740A1; Fri, 20 Feb 2015 19:10:41 +0100 (CET)
Date: Fri, 20 Feb 2015 19:10:41 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Toerless Eckert <eckert@cisco.com>
In-Reply-To: <20150220141634.GB8096@cisco.com>
Message-ID: <alpine.DEB.2.02.1502201907480.4007@uplift.swm.pp.se>
References: <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <8B98F698-983D-4D2A-B5D1-7ACED27C275E@fugue.com> <alpine.DEB.2.02.1502191920560.4007@uplift.swm.pp.se> <20150220141634.GB8096@cisco.com>
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/jrXKSXrfACjCLFaRwfOLWzwK5Gs>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 18:10:50 -0000

On Fri, 20 Feb 2015, Toerless Eckert wrote:

> So foremost, it would be good to understand if there really is home L2 
> equipment that MUST see MLD to operate correctly. Otherwise i'd happily 
> ignore the problem and say there is enough bandwidth to just NOT DO 
> snooping but have multicast be flooded in the L2 segments.

I know of ATA (VoIP) devices with 10/half uplinks that fall over HARD when 
they receive two simultaneous IPTV streams when doing channel switching.

So it's not only about bandwidth, but about how much traffic these kinds 
of devices are designed to receive.

Also, remember that we're going to 4k IPTV streams that might be in the 20 
megabit/s range, and we might be doing multiples of them. All devices on 
the subnet will receive this if there is no MLD/PIM snooping precent.

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


From nobody Fri Feb 20 10:17:10 2015
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 D20BB1A6EF8 for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 10:17:08 -0800 (PST)
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 PfbkUrPbonLH for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 10:17:07 -0800 (PST)
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 95C211A1A16 for <homenet@ietf.org>; Fri, 20 Feb 2015 10:17:07 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 49501A2; Fri, 20 Feb 2015 19:16:56 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1424456216; bh=zGAnjyvLqxqCFa3AA0zg7dyIvcaFZhEDGkccyUihhuA=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=nx3HkzmgDfCz3wO/Bm7yCBGOgNJ66XkuJYYGWRxvjWg17zMNXGduBPFgEW5vuY536 TySBKkO+Sm1QVO7mn1PfMaNCJpXaTpt7hygx94jqruOxEH5yqGJshH9IYpdIY4RnMo yphiwuatayA3UIZ7+dOupzf3rOi+Yso0Je8QNcK4=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 3F137A1; Fri, 20 Feb 2015 19:16:56 +0100 (CET)
Date: Fri, 20 Feb 2015 19:16:56 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Markus Stenberg <markus.stenberg@iki.fi>
In-Reply-To: <21FCAC07-1361-4051-B728-38AFB0656009@iki.fi>
Message-ID: <alpine.DEB.2.02.1502201915420.4007@uplift.swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <8B98F698-983D-4D2A-B5D1-7ACED27C275E@fugue.com> <alpine.DEB.2.02.1502191920560.4007@uplift.swm.pp.se> <CAPRuP3mpNJTu6mP+RAVKKO0kt60PogNtNbCUCRRqxe9im3EzjA@mail.gmail.com> <alpine.DEB.2.02.1502201042330.4007@uplift.swm.pp.se> <7A86BDC6-FF4B-49FF-B59C-BA1DEF463173@inf-net.nl> <alpine.DEB.2.02.1502201310050.4007@uplift.swm.pp.se> <09793905-8D12-49E0-A040-490F617C87FF@inf-net.nl> <alpine.DEB.2.02.1502201410510.4007@uplift.swm.pp.se> <21FCAC07-1361-4051-B728-38AFB0656009@iki.fi>
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/i3SzvMMHvKMFCcFFoK9DCyq8S_w>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Teco Boot <teco@inf-net.nl>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 18:17:09 -0000

On Fri, 20 Feb 2015, Markus Stenberg wrote:

> - have clients talk stub RP + stub HNCP, be done with it

Oooh, if we want to require changes to clients, I have all kinds of ideas 
how to solve this in other ways than you propose.

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


From nobody Fri Feb 20 10:23:02 2015
Return-Path: <dave.taht@gmail.com>
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 4BE0F1A001B for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 10:23:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 8b_36BbPuVYM for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 10:22:59 -0800 (PST)
Received: from mail-oi0-x236.google.com (mail-oi0-x236.google.com [IPv6:2607:f8b0:4003:c06::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2CFB01A00FD for <homenet@ietf.org>; Fri, 20 Feb 2015 10:22:58 -0800 (PST)
Received: by mail-oi0-f54.google.com with SMTP id v63so3974692oia.13 for <homenet@ietf.org>; Fri, 20 Feb 2015 10:22:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=Dmj7yYn7emuGglJbBB25/4OSX2V330ZTQpp9dFetamg=; b=qreGmE2U/4bLj9GE2aCiEOMkr949VY5v3E74mmrFcCxbe+dFqHymwbhanOU+F7pUdZ drwkaDpMGOt721smRJTTGFiKqEcS0XYC9ZYrSRn7BaTW5shybO89C9lKQ9jCXfhcRIUC UCe1a4OGe2LxuOvXdhmmjCHqgwwWCupuOoksamFM4RoCpD2vvz+uuq9QkTw3a2oWaiwc Upxvj5JfINHhukZlc1h3BsY+PLlI3f5yRpUumfOlY/GchURw2rPW7ePfk2g5itv3x05m 9AP693rlqk8yLPxuqye43306hw0cEv6AZBLMIuogTgJjlnMiTEi2u0I9B2EMCXD/x0F3 p3CQ==
MIME-Version: 1.0
X-Received: by 10.202.62.70 with SMTP id l67mr7043250oia.59.1424456578107; Fri, 20 Feb 2015 10:22:58 -0800 (PST)
Received: by 10.202.51.66 with HTTP; Fri, 20 Feb 2015 10:22:57 -0800 (PST)
In-Reply-To: <alpine.DEB.2.02.1502201907480.4007@uplift.swm.pp.se>
References: <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <8B98F698-983D-4D2A-B5D1-7ACED27C275E@fugue.com> <alpine.DEB.2.02.1502191920560.4007@uplift.swm.pp.se> <20150220141634.GB8096@cisco.com> <alpine.DEB.2.02.1502201907480.4007@uplift.swm.pp.se>
Date: Fri, 20 Feb 2015 10:22:57 -0800
Message-ID: <CAA93jw4s6E=chd-r9WmgVpNoCO3DUob+_WTBQ+NeNB_WoRcn8w@mail.gmail.com>
From: Dave Taht <dave.taht@gmail.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/Jtid7Iube9kaaTupsHHocM4sFYE>
Cc: Toerless Eckert <eckert@cisco.com>, "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 18:23:01 -0000

On Fri, Feb 20, 2015 at 10:10 AM, Mikael Abrahamsson <swmike@swm.pp.se> wro=
te:
> On Fri, 20 Feb 2015, Toerless Eckert wrote:
>
>> So foremost, it would be good to understand if there really is home L2
>> equipment that MUST see MLD to operate correctly. Otherwise i'd happily
>> ignore the problem and say there is enough bandwidth to just NOT DO snoo=
ping
>> but have multicast be flooded in the L2 segments.
>
>
> I know of ATA (VoIP) devices with 10/half uplinks that fall over HARD whe=
n
> they receive two simultaneous IPTV streams when doing channel switching.
>
> So it's not only about bandwidth, but about how much traffic these kinds =
of
> devices are designed to receive.
>
> Also, remember that we're going to 4k IPTV streams that might be in the 2=
0
> megabit/s range, and we might be doing multiples of them. All devices on =
the
> subnet will receive this if there is no MLD/PIM snooping precent.

Is there a formal definition of IPTV? as used here, it seems to imply multi=
cast.

Frankly, until now, I was expecting the world to go to a HAS model for cont=
ent,
especially big content.

>
> --
> Mikael Abrahamsson    email: swmike@swm.pp.se
>
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet



--=20
Dave T=C3=A4ht

thttp://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks


From nobody Fri Feb 20 10:24:22 2015
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 967801A001B for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 10:24:20 -0800 (PST)
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 vKdUV2dNLRIh for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 10:24:19 -0800 (PST)
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 CD89C1A0358 for <homenet@ietf.org>; Fri, 20 Feb 2015 10:24:17 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 80A35A2; Fri, 20 Feb 2015 19:24:01 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1424456641; bh=L3SSTKVQZYAtTVvR2wRdRUfGVp4GLj7mZRsOQnKq/Ec=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=XZ1U1Q7bqOcllCDWUX00EIYrLG0a2LxMw/A6VL7AR/oc3IZyQgbWrrg2BoeTG5WVs FCjUHvFT8Kz5v5/frNWWofuIiy5u+bEzhTHvNOXm8/gPcKWxbimdl83JSO1HxvxGHR bf1FKoZ/sx/n7RQEv6TwLvKknIv/TKPXeE3BEnA4=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 79F34A1; Fri, 20 Feb 2015 19:24:01 +0100 (CET)
Date: Fri, 20 Feb 2015 19:24:01 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Dave Taht <dave.taht@gmail.com>
In-Reply-To: <CAA93jw7eGxPBNX+5LqX+qTYfRxNDxQpKo1fecUa2XH3bAKgvQQ@mail.gmail.com>
Message-ID: <alpine.DEB.2.02.1502201919170.4007@uplift.swm.pp.se>
References: <CAA93jw7eGxPBNX+5LqX+qTYfRxNDxQpKo1fecUa2XH3bAKgvQQ@mail.gmail.com>
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/AkQARixGSIO180jZL_yjyjBNu4c>
Cc: HOMENET <homenet@ietf.org>
Subject: Re: [homenet] A poll
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 18:24:20 -0000

On Fri, 20 Feb 2015, Dave Taht wrote:

> 1) Have you attempted to deploy a routing protocol in your home? Which
> one, and why?

Home, HE tunnel.

> 2) Have you attempted to get hnetd's prefix distribution system
> working? (it supports linux mainline and openwrt presently)

Yes, I had this working, but since the routers I had available (WNDR3800) 
didn't perform forwarding quickly enough for my everyday needs, I didn't 
put them into "production".

> 3) Do you use ethernet? How many clients in your home are ethernet connected?

Well, since 802.11 is ethernet as well I will interpret this as "how many 
devices in your home use cable", and say 9.

> 4) Do you use wifi? How many clients are wifi connected? Do you use
> range extenders?

I have approximately 8-10 devices connecting using wifi, 6 of them more 
frequently than the others. I do not use wifi range extenders.

> 5) How many devices do you think you will have connected to the
> network in your home in 5 years? How many now?

Good question, I'd say increase of 10 at least, I presume by then I will 
have some kind of "smart home" stuff such as sensors or alike.

> 6) Do you use any other network connected technologies (homeplug,
> 802.14, LTE, etc). If so, which ones, and why?

Well, our mobile phones speak LTE, but apart from that it's the bluetooth 
usage that apples does without me having to know much about it.

> 7) Do you use mdns service discovery?

No, I use single subnet.

> 8) Why are you here? (especially, if your answers to 0-2, are "no")

I want multi-subnet home to work for everyday users such as my mom.

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


From nobody Fri Feb 20 10:26:44 2015
Return-Path: <markus.stenberg@iki.fi>
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 34D211A03E1 for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 10:26:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.521
X-Spam-Level: 
X-Spam-Status: No, score=-0.521 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_35=0.6, RCVD_IN_DNSWL_NONE=-0.0001, SPF_NEUTRAL=0.779] autolearn=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 bnMCvvXnHzMK for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 10:26:40 -0800 (PST)
Received: from jenni1.inet.fi (mta-out1.inet.fi [62.71.2.227]) by ietfa.amsl.com (Postfix) with ESMTP id BA9F61A001B for <homenet@ietf.org>; Fri, 20 Feb 2015 10:26:39 -0800 (PST)
Received: from poro.lan (80.220.64.126) by jenni1.inet.fi (8.5.142.08) (authenticated as stenma-47) id 54E3C703005FDFEA; Fri, 20 Feb 2015 20:26:36 +0200
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Markus Stenberg <markus.stenberg@iki.fi>
In-Reply-To: <CAA93jw7eGxPBNX+5LqX+qTYfRxNDxQpKo1fecUa2XH3bAKgvQQ@mail.gmail.com>
Date: Fri, 20 Feb 2015 20:26:36 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <BB621A07-282E-4814-9D56-3EFBF87814D0@iki.fi>
References: <CAA93jw7eGxPBNX+5LqX+qTYfRxNDxQpKo1fecUa2XH3bAKgvQQ@mail.gmail.com>
To: Dave Taht <dave.taht@gmail.com>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/Nh-O01xyg3PgL3XrraizetPQ2fs>
Cc: HOMENET <homenet@ietf.org>, Markus Stenberg <markus.stenberg@iki.fi>
Subject: Re: [homenet] A poll
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 18:26:43 -0000

On 20.2.2015, at 18.50, Dave Taht <dave.taht@gmail.com> wrote:
> The homenet working group has been laboring for several years now to
> find ways to make ipv6 more deployable to home (and presumably small
> business) users.
>=20
> In addition to multiple specification documents some code has been
> produced to try and make things easier. At least in the USA, comcast
> has rolled out IPv6 to everyone that can get dhcpv6 to sort of work on
> their router, and/or is willing to install a custom firmware on their
> router to get that, and of course tunneling ipv6 is possible if the
> ISP does not support it.
>=20
> So a quick poll:
>=20
> 0) Have you managed to get ipv6 working at all? If so, how? What sort
> of problems did you encounter?

Yes. Used to be he.net tunnel and now 6rd Sonera right up to my home =
(VDSL2).

> 1) Have you attempted to deploy a routing protocol in your home? Which
> one, and why?

OSPFv3 at some point and nowadays Babel. Obvious reasons, homenet ;)

> 2) Have you attempted to get hnetd's prefix distribution system
> working? (it supports linux mainline and openwrt presently)

Yes.

> 3) Do you use ethernet? How many clients in your home are ethernet =
connected?

Dozen-ish.

> 4) Do you use wifi? How many clients are wifi connected? Do you use
> range extenders?

Half dozen. No range extenders.

> 5) How many devices do you think you will have connected to the
> network in your home in 5 years? How many now?

<20 now. Probably 30+ in 5y.

> 6) Do you use any other network connected technologies (homeplug,
> 802.14, LTE, etc). If so, which ones, and why?

LTE. Fallback connectivity.

> 7) Do you use mdns service discovery?

I used to. OS X 10.10 broke it on wlan pretty much. (ping foo.local =3D> =
=E2=80=98foo who?=E2=80=99. ping foo.lan =3D> ok.. sigh.)

> 8) Why are you here? (especially, if your answers to 0-2, are =E2=80=9Cn=
o")

I wonder about it at times. Bad habit?

Cheers,

-Markus=


From nobody Fri Feb 20 10:28:55 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 C151B1A3BA9 for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 10:28:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35] autolearn=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 v_HEHDiHcuIr for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 10:28:52 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 94A261A0040 for <homenet@ietf.org>; Fri, 20 Feb 2015 10:28:52 -0800 (PST)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t1KISpZa001966; Fri, 20 Feb 2015 19:28:51 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 3570A2BFCF6; Fri, 20 Feb 2015 19:28:51 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id mhuO5Tglnsiv; Fri, 20 Feb 2015 19:28:49 +0100 (CET)
Received: from pirx.pps.jussieu.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 9BC072BFCF5; Fri, 20 Feb 2015 19:28:49 +0100 (CET)
Date: Fri, 20 Feb 2015 19:28:50 +0100
Message-ID: <8761awcu8t.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Mikael Abrahamsson <swmike@swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1502201915420.4007@uplift.swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <8B98F698-983D-4D2A-B5D1-7ACED27C275E@fugue.com> <alpine.DEB.2.02.1502191920560.4007@uplift.swm.pp.se> <CAPRuP3mpNJTu6mP+RAVKKO0kt60PogNtNbCUCRRqxe9im3EzjA@mail.gmail.com> <alpine.DEB.2.02.1502201042330.4007@uplift.swm.pp.se> <7A86BDC6-FF4B-49FF-B59C-BA1DEF463173@inf-net.nl> <alpine.DEB.2.02.1502201310050.4007@uplift.swm.pp.se> <09793905-8D12-49E0-A040-490F617C87FF@inf-net.nl> <alpine.DEB.2.02.1502201410510.4007@uplift.swm.pp.se> <21FCAC07-1361-4051-B728-38AFB0656009@iki.fi> <alpine.DEB.2.02.1502201915420.4007@uplift.swm.pp.se>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Fri, 20 Feb 2015 19:28:51 +0100 (CET)
X-Miltered: at korolev with ID 54E77CE3.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54E77CE3.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54E77CE3.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/epDEzLv0BJXwQKyArRAivXepZAU>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: [homenet] Client roaming [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 18:28:53 -0000

>> - have clients talk stub RP + stub HNCP, be done with it

> if we want to require changes to clients, I have all kinds of ideas how
> to solve this in other ways than you propose.

Please share.  We might not implement them, but we'll certainly listen.

(Note that we're not *requiring* changes to hosts, we're just proposing
optional host changes that are likely to enhance the user experience.  I'm
pretty sure that's consistent with Homenet's charter.)

-- Juliusz


From nobody Fri Feb 20 10:41:58 2015
Return-Path: <mike@mtcc.com>
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 7F6C91A87E8 for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 10:41:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.288
X-Spam-Level: 
X-Spam-Status: No, score=0.288 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_ADSP_ALL=0.8, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 LqTWkEr38_JR for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 10:41:52 -0800 (PST)
Received: from mtcc.com (mtcc.com [50.0.18.224]) (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 2B25B1A8870 for <homenet@ietf.org>; Fri, 20 Feb 2015 10:41:45 -0800 (PST)
Received: from takifugu.mtcc.com (takifugu.mtcc.com [50.0.18.224]) (authenticated bits=0) by mtcc.com (8.14.7/8.14.7) with ESMTP id t1KIfipu015961 for <homenet@ietf.org>; Fri, 20 Feb 2015 10:41:44 -0800
Message-ID: <54E77FE8.3010102@mtcc.com>
Date: Fri, 20 Feb 2015 10:41:44 -0800
From: Michael Thomas <mike@mtcc.com>
User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: homenet@ietf.org
References: <CAA93jw7eGxPBNX+5LqX+qTYfRxNDxQpKo1fecUa2XH3bAKgvQQ@mail.gmail.com>
In-Reply-To: <CAA93jw7eGxPBNX+5LqX+qTYfRxNDxQpKo1fecUa2XH3bAKgvQQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/olEY56gag3vsIBr67GFs6Z4ob98>
Subject: Re: [homenet] A poll
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 18:41:53 -0000

On 02/20/2015 08:50 AM, Dave Taht wrote:
> The homenet working group has been laboring for several years now to
> find ways to make ipv6 more deployable to home (and presumably small
> business) users.
>
> In addition to multiple specification documents some code has been
> produced to try and make things easier. At least in the USA, comcast
> has rolled out IPv6 to everyone that can get dhcpv6 to sort of work on
> their router, and/or is willing to install a custom firmware on their
> router to get that, and of course tunneling ipv6 is possible if the
> ISP does not support it.
>
> So a quick poll:
>
> 0) Have you managed to get ipv6 working at all? If so, how? What sort
> of problems did you encounter?

Yes, he. Mostly trying to figure out how to get tunnel endpoints up.

>
> 1) Have you attempted to deploy a routing protocol in your home? Which
> one, and why?

no.

>
> 2) Have you attempted to get hnetd's prefix distribution system
> working? (it supports linux mainline and openwrt presently)

no.
>
> 3) Do you use ethernet? How many clients in your home are ethernet connected?

~ half dozen.
>
> 4) Do you use wifi? How many clients are wifi connected? Do you use
> range extenders?

it's hard to keep track of, but 5-10. and I'm not sure what you'd 
consider the ethernet
cable between my house and my friend's house with two AP's on each end 
to be.

>
> 5) How many devices do you think you will have connected to the
> network in your home in 5 years? How many now?

i expect it will be way more than most of us fear/imagine. now: about 10.

>
> 6) Do you use any other network connected technologies (homeplug,
> 802.14, LTE, etc). If so, which ones, and why?

Nope. LTE obviously for phones, but I don't think that's what you're asking.

>
> 7) Do you use mdns service discovery?

Nope.

>
> 8) Why are you here? (especially, if your answers to 0-2, are "no")
>
>

Mostly interested in the naming problem, and the occasional insight as 
to how service discovery saved $MEGACORP
from the dustbin of history.

Mike


From nobody Fri Feb 20 10:51:36 2015
Return-Path: <jmh@joelhalpern.com>
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 392801A8880 for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 10:51:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 ypFHImFShZaV for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 10:51:33 -0800 (PST)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 58F791A8724 for <homenet@ietf.org>; Fri, 20 Feb 2015 10:51:18 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 3760C1C0A83; Fri, 20 Feb 2015 10:51:18 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from Joels-MacBook-Pro.local (pool-70-106-135-240.clppva.east.verizon.net [70.106.135.240]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id F1B121C0AEB; Fri, 20 Feb 2015 10:51:15 -0800 (PST)
Message-ID: <54E781E0.4040703@joelhalpern.com>
Date: Fri, 20 Feb 2015 13:50:08 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Dave Taht <dave.taht@gmail.com>,  Mikael Abrahamsson <swmike@swm.pp.se>
References: <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <8B98F698-983D-4D2A-B5D1-7ACED27C275E@fugue.com> <alpine.DEB.2.02.1502191920560.4007@uplift.swm.pp.se> <20150220141634.GB8096@cisco.com> <alpine.DEB.2.02.1502201907480.4007@uplift.swm.pp.se> <CAA93jw4s6E=chd-r9WmgVpNoCO3DUob+_WTBQ+NeNB_WoRcn8w@mail.gmail.com>
In-Reply-To: <CAA93jw4s6E=chd-r9WmgVpNoCO3DUob+_WTBQ+NeNB_WoRcn8w@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/Ft5qreUM2CcZtBfA_4sa6gS5XfQ>
Cc: Toerless Eckert <eckert@cisco.com>, "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 18:51:35 -0000

It seems pretty clear that over time, the bulk of video will be unicast, 
in order to meet on-demand needs.  There will always be a few items that 
folks really want to watch live, and thus where multicast may add value. 
  But making multicast the design driver for home networking 
archtiecture seems backwards to me.

Yours,
Joel

On 2/20/15 1:22 PM, Dave Taht wrote:
> On Fri, Feb 20, 2015 at 10:10 AM, Mikael Abrahamsson <swmike@swm.pp.se> wrote:
>> On Fri, 20 Feb 2015, Toerless Eckert wrote:
>>
>>> So foremost, it would be good to understand if there really is home L2
>>> equipment that MUST see MLD to operate correctly. Otherwise i'd happily
>>> ignore the problem and say there is enough bandwidth to just NOT DO snooping
>>> but have multicast be flooded in the L2 segments.
>>
>>
>> I know of ATA (VoIP) devices with 10/half uplinks that fall over HARD when
>> they receive two simultaneous IPTV streams when doing channel switching.
>>
>> So it's not only about bandwidth, but about how much traffic these kinds of
>> devices are designed to receive.
>>
>> Also, remember that we're going to 4k IPTV streams that might be in the 20
>> megabit/s range, and we might be doing multiples of them. All devices on the
>> subnet will receive this if there is no MLD/PIM snooping precent.
>
> Is there a formal definition of IPTV? as used here, it seems to imply multicast.
>
> Frankly, until now, I was expecting the world to go to a HAS model for content,
> especially big content.
>
>>
>> --
>> Mikael Abrahamsson    email: swmike@swm.pp.se
>>
>> _______________________________________________
>> homenet mailing list
>> homenet@ietf.org
>> https://www.ietf.org/mailman/listinfo/homenet
>
>
>


From nobody Fri Feb 20 11:05:38 2015
Return-Path: <gert@Space.Net>
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 C67AF1A1B54 for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 11:05:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.011
X-Spam-Level: 
X-Spam-Status: No, score=-0.011 tagged_above=-999 required=5 tests=[BAYES_20=-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 ynh9ZKKib8j8 for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 11:05:35 -0800 (PST)
Received: from mobil.space.net (mobil.space.net [IPv6:2001:608:2:81::67]) (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 494C91A0068 for <homenet@ietf.org>; Fri, 20 Feb 2015 11:05:34 -0800 (PST)
X-Original-To: homenet@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id 285D36025D for <homenet@ietf.org>; Fri, 20 Feb 2015 20:05:33 +0100 (CET)
X-SpaceNet-Relay: true
Received: from moebius3.space.net (moebius3.Space.Net [IPv6:2001:608:2:2::250]) by mobil.space.net (Postfix) with ESMTPS id D00FE6016D for <homenet@ietf.org>; Fri, 20 Feb 2015 20:05:32 +0100 (CET)
Received: (qmail 4973 invoked by uid 1007); 20 Feb 2015 20:05:32 +0100
Date: Fri, 20 Feb 2015 20:05:32 +0100
From: Gert Doering <gert@space.net>
To: Dave Taht <dave.taht@gmail.com>
Message-ID: <20150220190532.GD34798@Space.Net>
References: <CAA93jw7eGxPBNX+5LqX+qTYfRxNDxQpKo1fecUa2XH3bAKgvQQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAA93jw7eGxPBNX+5LqX+qTYfRxNDxQpKo1fecUa2XH3bAKgvQQ@mail.gmail.com>
X-NCC-RegID: de.space
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/xXWAzJeXjU_79R6ajSewGo0l-Ew>
Cc: HOMENET <homenet@ietf.org>
Subject: Re: [homenet] A poll
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 19:05:37 -0000

Hi,

On Fri, Feb 20, 2015 at 08:50:10AM -0800, Dave Taht wrote:
> So a quick poll:
> 
> 0) Have you managed to get ipv6 working at all? If so, how? What sort
> of problems did you encounter?

Yes, PPPoE/L2TP session to myself as ISP on the other end (so I cheated).

> 1) Have you attempted to deploy a routing protocol in your home? Which
> one, and why?

Did some testing with HCNP/Babels, to see if it works.  But the "production
network" is plain flat L2 today.

> 2) Have you attempted to get hnetd's prefix distribution system
> working? (it supports linux mainline and openwrt presently)

Yes, on OpenWRT.  Worked.

> 3) Do you use ethernet? How many clients in your home are ethernet connected?

Yes, ~10-ish.

> 4) Do you use wifi? How many clients are wifi connected? Do you use
> range extenders?

Yes, ~3-5, no.

> 5) How many devices do you think you will have connected to the
> network in your home in 5 years? How many now?

"More" - I see some sensors coming up, and maybe some of these thingies
people call "smart phones" even if they are neither smart nor very good
phones.

> 6) Do you use any other network connected technologies (homeplug,
> 802.14, LTE, etc). If so, which ones, and why?

No.

> 7) Do you use mdns service discovery?

Half of the devices are Apple built, so, yes.

> 8) Why are you here? (especially, if your answers to 0-2, are "no")

To complain about lack of useful source address selection (aka "prefix
labeling so users can make an informed choice"), and frown about IETF 
committee behaviour.  Or so.

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444           USt-IdNr.: DE813185279


From nobody Fri Feb 20 11:35:14 2015
Return-Path: <cyrus@openwrt.org>
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 A0A031A8999 for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 11:35:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.25
X-Spam-Level: 
X-Spam-Status: No, score=-2.25 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-0.7] 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 SEX1dESFW11G for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 11:35:11 -0800 (PST)
Received: from mail.core-networks.de (mail.core-networks.de [82.96.72.7]) by ietfa.amsl.com (Postfix) with ESMTP id ECF051A87C3 for <homenet@ietf.org>; Fri, 20 Feb 2015 11:35:01 -0800 (PST)
Received: from localhost ([127.0.0.1]) by mail.core-networks.de id 1YOtLi-0005Bq-5p with ESMTPSA (TLSv1.2:DHE-RSA-AES256-SHA:256) for ; Fri, 20 Feb 2015 20:34:54 +0100
User-Agent: K-9 Mail for Android
In-Reply-To: <C8437CBF-DEF5-49D1-9908-6C784DAA0137@fugue.com>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <F2818678-A728-4300-896C-E220A0DF0D1A@employees.org> <ADBDED5C-5279-4A04-B7C8-FCCB453A8C4F@gmail.com> <B2BEAF63-D219-41A0-8209-1EEFE9667440@fugue.com> <54E6318C.9030609@openwrt.org> <C8437CBF-DEF5-49D1-9908-6C784DAA0137@fugue.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset=UTF-8
From: Steven Barth <cyrus@openwrt.org>
Date: Fri, 20 Feb 2015 20:34:48 +0100
To: Ted Lemon <mellon@fugue.com>
Message-ID: <0E03C679-3253-42B3-A9F6-605C27F2BCBA@openwrt.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/7POkIo2v7smCZjvL4u-zxK_MPJM>
Cc: Ole Troan <otroan@employees.org>, Mikael Abrahamsson <swmike@swm.pp.se>, "homenet@ietf.org Group" <homenet@ietf.org>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 19:35:13 -0000

Am 19. Februar 2015 20:05:56 MEZ, schrieb Ted Lemon <mellon@fugue.com>:
>Hm, I will have to try it out.   Is it in a distribution?

ohybridproxy in openwrt. It's mainly useful with hnetd (hncp) though. 

Manual configuration without hncp is a bit awkward since you need to name each link manually and on every router configure the resolver (e.g. dnsmasq). I guess we might want to provide a little example for 2 links at some point.


From nobody Fri Feb 20 11:50:37 2015
Return-Path: <John_Leddy@cable.comcast.com>
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 39C201A8956 for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 11:50:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.225
X-Spam-Level: 
X-Spam-Status: No, score=0.225 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 iP7vgDwXtKTv for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 11:50:34 -0800 (PST)
Received: from pacdcmhout01.cable.comcast.com (PACDCMHOUT01.cable.comcast.com [68.87.31.167]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A54991A88F6 for <homenet@ietf.org>; Fri, 20 Feb 2015 11:50:24 -0800 (PST)
X-AuditID: 44571fa7-f79b96d000002184-f9-54e78fff963f
Received: from pacdcexhub05.cable.comcast.com (pacdcexhub05.cable.comcast.com [24.40.56.122]) by pacdcmhout01.cable.comcast.com (SMTP Gateway) with SMTP id E9.43.08580.FFF87E45; Fri, 20 Feb 2015 14:50:23 -0500 (EST)
Received: from PACDCEXMB22.cable.comcast.com ([fe80::f887:1b71:477f:d14b]) by pacdcexhub05.cable.comcast.com ([fe80::3d40:bdea:7266:7f5a%18]) with mapi id 14.03.0181.006; Fri, 20 Feb 2015 14:50:22 -0500
From: "Leddy, John" <John_Leddy@cable.comcast.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>, Dave Taht <dave.taht@gmail.com>,  Mikael Abrahamsson <swmike@swm.pp.se>
Thread-Topic: [homenet] Routing protocol comparison document
Thread-Index: AQHQTTiJpljA4qO18ECjoj8KcSEQaZz6LeCAgAAHmAD//70AAA==
Date: Fri, 20 Feb 2015 19:50:22 +0000
Message-ID: <D10CF8AA.6F5F%John_Leddy@cable.comcast.com>
References: <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <8B98F698-983D-4D2A-B5D1-7ACED27C275E@fugue.com> <alpine.DEB.2.02.1502191920560.4007@uplift.swm.pp.se> <20150220141634.GB8096@cisco.com> <alpine.DEB.2.02.1502201907480.4007@uplift.swm.pp.se> <CAA93jw4s6E=chd-r9WmgVpNoCO3DUob+_WTBQ+NeNB_WoRcn8w@mail.gmail.com> <54E781E0.4040703@joelhalpern.com>
In-Reply-To: <54E781E0.4040703@joelhalpern.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.4.7.141117
x-originating-ip: [24.40.1.153]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <AB2DABF1E8D76A47BA56E3F522855D4F@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrJIsWRmVeSWpSXmKPExsUioWFRpfu//3mIwe/HKhZ7l99js3i/6BCL xcdTb5gsXi7dyubA4jHl90ZWjyVLfjJ5nJvyndHj76SHTAEsUVw2Kak5mWWpRfp2CVwZzWc3 shR0i1R0vZnB1sC4UqCLkZNDQsBE4tGUKYwQtpjEhXvr2boYuTiEBG4ySrzvW8IM4ZxjlNg+ aSoTSBWbgJHEzVVbwDpEBEolzt9bwwxiMwuESjz+Po+1i5GDQ1jAWmJJiwdEiY3E/lWt7CBh EQEniZUzpUHCLAKqEsun7mUHsXkFLCQW7vnECLHqJ6vEh4PdLCAJTgF9iSVfloAVMQId9/3U GiaIVeISt57MZ4I4WkBiyZ7zzBC2qMTLx/9YQWxRAT2Jldeb2CDi8hIbPv5mg+jVkViw+xOU 7SDx68c+dghbW2LZwtfMEAcJSpyc+YRlAqPELCTrZiFpn4WkfRaS9llI2hcwsq5ilCtITE5J zs3ILy0xMNRLTkzKSdVLzs9NTiwuAdGbGIER7BIuv3wH470XTocYBTgYlXh4hSqfhwixJpYV V+YeYpTgYFYS4bXPAArxpiRWVqUW5ccXleakFh9ilOZgURLnfRsOlBJITyxJzU5NLUgtgsky cXBKNTBOzuM/PlVTSvp/9hUPZtnHwu2NZmefvNtk6LN4Ms/qu49ddBWK5BX1N77bMjeCyVGL sezkc28ZZi3nw/yVm18rz9hf+D3arvZThJ9wcP/Z8P4FNlYcka+kzONM7DJ27zw+WVh8px7z E7u0E5tuxe6RvrHwzPO3Nnl395xcb71G68Lc6GB7lYdKLMUZiYZazEXFiQCX1p9J3AIAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/l1GxIsU84r8wp9nwC0KVgv-9hok>
Cc: Toerless Eckert <eckert@cisco.com>, "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 19:50:36 -0000

Agree.  I would not architect around multi-hop multicast, subnet OK,
targeted probably.

Not sure everyone has had the pleasure of running large IP multicast
infrastructures running video, it is a wonderful challenge.
It also has the side benefit of encouraging poorly designed applications.


Interoperability on even core routers for IP multicast barely exists.  In
a home environment, although smaller, will be even less wonderful.

Just the race conditions between PIM and the IGP are always challenging.

On 2/20/15, 1:50 PM, "Joel M. Halpern" <jmh@joelhalpern.com> wrote:

>It seems pretty clear that over time, the bulk of video will be unicast,
>in order to meet on-demand needs.  There will always be a few items that
>folks really want to watch live, and thus where multicast may add value.
>  But making multicast the design driver for home networking
>archtiecture seems backwards to me.
>
>Yours,
>Joel
>
>On 2/20/15 1:22 PM, Dave Taht wrote:
>> On Fri, Feb 20, 2015 at 10:10 AM, Mikael Abrahamsson <swmike@swm.pp.se>
>>wrote:
>>> On Fri, 20 Feb 2015, Toerless Eckert wrote:
>>>
>>>> So foremost, it would be good to understand if there really is home L2
>>>> equipment that MUST see MLD to operate correctly. Otherwise i'd
>>>>happily
>>>> ignore the problem and say there is enough bandwidth to just NOT DO
>>>>snooping
>>>> but have multicast be flooded in the L2 segments.
>>>
>>>
>>> I know of ATA (VoIP) devices with 10/half uplinks that fall over HARD
>>>when
>>> they receive two simultaneous IPTV streams when doing channel
>>>switching.
>>>
>>> So it's not only about bandwidth, but about how much traffic these
>>>kinds of
>>> devices are designed to receive.
>>>
>>> Also, remember that we're going to 4k IPTV streams that might be in
>>>the 20
>>> megabit/s range, and we might be doing multiples of them. All devices
>>>on the
>>> subnet will receive this if there is no MLD/PIM snooping precent.
>>
>> Is there a formal definition of IPTV? as used here, it seems to imply
>>multicast.
>>
>> Frankly, until now, I was expecting the world to go to a HAS model for
>>content,
>> especially big content.
>>
>>>
>>> --
>>> Mikael Abrahamsson    email: swmike@swm.pp.se
>>>
>>> _______________________________________________
>>> homenet mailing list
>>> homenet@ietf.org
>>> https://www.ietf.org/mailman/listinfo/homenet
>>
>>
>>
>
>_______________________________________________
>homenet mailing list
>homenet@ietf.org
>https://www.ietf.org/mailman/listinfo/homenet
>


From nobody Fri Feb 20 11:55:30 2015
Return-Path: <cyrus@openwrt.org>
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 6CB5D1A894F for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 11:55:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] 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 zjyFoGmS5NgD for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 11:55:27 -0800 (PST)
Received: from mail.core-networks.de (mail.core-networks.de [82.96.72.7]) by ietfa.amsl.com (Postfix) with ESMTP id 87D4A1A88F6 for <homenet@ietf.org>; Fri, 20 Feb 2015 11:55:27 -0800 (PST)
Received: from localhost ([127.0.0.1]) by mail.core-networks.de id 1YOtfZ-00066h-Ls with ESMTPSA (TLSv1.2:DHE-RSA-AES256-SHA:256) for ; Fri, 20 Feb 2015 20:55:26 +0100
User-Agent: K-9 Mail for Android
In-Reply-To: <CAA93jw7eGxPBNX+5LqX+qTYfRxNDxQpKo1fecUa2XH3bAKgvQQ@mail.gmail.com>
References: <CAA93jw7eGxPBNX+5LqX+qTYfRxNDxQpKo1fecUa2XH3bAKgvQQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----UI85ZAN9YAW9LI76UYJAYIHK43B8J3"
Content-Transfer-Encoding: 8bit
From: Steven Barth <cyrus@openwrt.org>
Date: Fri, 20 Feb 2015 20:55:20 +0100
To: Dave Taht <dave.taht@gmail.com>,HOMENET <homenet@ietf.org>
Message-ID: <E9EC49EC-B2FF-4206-AB0B-0F98BFDE430C@openwrt.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/q8R19up9NlLQAGK_Pm1uUKgsDFQ>
Subject: Re: [homenet] A poll
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 19:55:29 -0000

------UI85ZAN9YAW9LI76UYJAYIHK43B8J3
Content-Transfer-Encoding: 8bit
Content-Type: text/plain;
 charset=UTF-8


>So a quick poll:
>
>0) Have you managed to get ipv6 working at all? If so, how? What sort
>of problems did you
Yes. Most foss router software sucked with v6. Tried to fix some things. Still not 100% convinced. 

>
>1) Have you attempted to deploy a routing protocol in your home? Which
>one, and why?
Well babels & autoisis but only for testing purposes. My production network is still single link.

>
>2) Have you attempted to get hnetd's prefix distribution system
>working? (it supports linux mainline and openwrt presently)
Yes

>
>3) Do you use ethernet? How many clients in your home are ethernet
>connected?
3 to 4

>
>4) Do you use wifi? How many clients are wifi connected? Do you use
>range extenders?
Yes. 5 to 8. No.

>
>5) How many devices do you think you will have connected to the
>network in your home in 5 years? How many now?
I guess 50-100% increase.

>
>6) Do you use any other network connected technologies (homeplug,
>802.14, LTE, etc). If so, which ones, and why?
Does bluetooth count? Otherwise 3.5g as connectivity backup.

>
>7) Do you use mdns service discovery?
Seldom. When setting up my printer. Seldomly the .local resolving.
------UI85ZAN9YAW9LI76UYJAYIHK43B8J3
Content-Type: text/html;
 charset=utf-8
Content-Transfer-Encoding: 8bit

<br>
&gt;So a quick poll:<br>
&gt;<br>
&gt;0) Have you managed to get ipv6 working at all? If so, how? What sort<br>
&gt;of problems did you<br>
Yes. Most foss router software sucked with v6. Tried to fix some things. Still not 100% convinced. <br>
<br>
&gt;<br>
&gt;1) Have you attempted to deploy a routing protocol in your home? Which<br>
&gt;one, and why?<br>
Well babels &amp; autoisis but only for testing purposes. My production network is still single link.<br>
<br>
&gt;<br>
&gt;2) Have you attempted to get hnetd&#39;s prefix distribution system<br>
&gt;working? (it supports linux mainline and openwrt presently)<br>
Yes<br>
<br>
&gt;<br>
&gt;3) Do you use ethernet? How many clients in your home are ethernet<br>
&gt;connected?<br>
3 to 4<br>
<br>
&gt;<br>
&gt;4) Do you use wifi? How many clients are wifi connected? Do you use<br>
&gt;range extenders?<br>
Yes. 5 to 8. No.<br>
<br>
&gt;<br>
&gt;5) How many devices do you think you will have connected to the<br>
&gt;network in your home in 5 years? How many now?<br>
I guess 50-100% increase.<br>
<br>
&gt;<br>
&gt;6) Do you use any other network connected technologies (homeplug,<br>
&gt;802.14, LTE, etc). If so, which ones, and why?<br>
Does bluetooth count? Otherwise 3.5g as connectivity backup.<br>
<br>
&gt;<br>
&gt;7) Do you use mdns service discovery?<br>
Seldom. When setting up my printer. Seldomly the .local resolving.
------UI85ZAN9YAW9LI76UYJAYIHK43B8J3--


From nobody Fri Feb 20 12:01:58 2015
Return-Path: <dave.taht@gmail.com>
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 8AAA31A0089 for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 12:01:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 3EdsmAE9v0MG for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 12:01:55 -0800 (PST)
Received: from mail-ob0-x22e.google.com (mail-ob0-x22e.google.com [IPv6:2607:f8b0:4003:c01::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4020E1A0023 for <homenet@ietf.org>; Fri, 20 Feb 2015 12:01:55 -0800 (PST)
Received: by mail-ob0-f174.google.com with SMTP id wo20so26043232obc.5 for <homenet@ietf.org>; Fri, 20 Feb 2015 12:01:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=pPsF7xru7kOD9RZ1wbMeN8/m5bWi4e1o8H6v4omOUvg=; b=t6rrNVYENfFfYUO153wDRuf1Nsg933VU7v29/Kyz89d9QJm5AiiiJAFyjTBszauCPp FKlmbACg1y8l7lf35/MAhHiXeIkX98eDBoUHreRt8v/UEbortKKQyWbYDKzddCq9xX6E PU03IxJkCe75Ah6b+QlEeY2wikbnvMVKchcAyXcDpxzTrgOPeb79Gadi82+ScwIwQJ23 owD7LGjyALfbocpJ1KeWws7guPGIfZTzSJem1tg6/EShr4LfPYaRDFXhNI8UOYETToKH jnqR7qRY79+ivSR7ytBT4GWztgYxDmhLtRnaq5t4MSNmnHsd5DgfTJsRoCsUTs/34Yt5 lbvA==
MIME-Version: 1.0
X-Received: by 10.60.103.234 with SMTP id fz10mr7779595oeb.11.1424462514586; Fri, 20 Feb 2015 12:01:54 -0800 (PST)
Received: by 10.202.51.66 with HTTP; Fri, 20 Feb 2015 12:01:54 -0800 (PST)
In-Reply-To: <0E03C679-3253-42B3-A9F6-605C27F2BCBA@openwrt.org>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <F2818678-A728-4300-896C-E220A0DF0D1A@employees.org> <ADBDED5C-5279-4A04-B7C8-FCCB453A8C4F@gmail.com> <B2BEAF63-D219-41A0-8209-1EEFE9667440@fugue.com> <54E6318C.9030609@openwrt.org> <C8437CBF-DEF5-49D1-9908-6C784DAA0137@fugue.com> <0E03C679-3253-42B3-A9F6-605C27F2BCBA@openwrt.org>
Date: Fri, 20 Feb 2015 12:01:54 -0800
Message-ID: <CAA93jw6MhqJ4OVO5G7gYQf71XVeCzThXJt5QgDaO07Jz0+cWQg@mail.gmail.com>
From: Dave Taht <dave.taht@gmail.com>
To: Steven Barth <cyrus@openwrt.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/V3rKhfBVmO9bhtluRBqDMgb2X_c>
Cc: Ole Troan <otroan@employees.org>, Ralph Droms <rdroms.ietf@gmail.com>, Ted Lemon <mellon@fugue.com>, "homenet@ietf.org Group" <homenet@ietf.org>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 20:01:57 -0000

On Fri, Feb 20, 2015 at 11:34 AM, Steven Barth <cyrus@openwrt.org> wrote:
>
>
> Am 19. Februar 2015 20:05:56 MEZ, schrieb Ted Lemon <mellon@fugue.com>:
>>Hm, I will have to try it out.   Is it in a distribution?
>
> ohybridproxy in openwrt. It's mainly useful with hnetd (hncp) though.
>
> Manual configuration without hncp is a bit awkward since you need to name=
 each link manually and on every router configure the resolver (e.g. dnsmas=
q). I guess we might want to provide a little example for 2 links at some p=
oint.

I would like to deploy hncp in my upcoming make-wifi-fast testbed.
However the biggest headache is ensuring that all the routers
inbetween have hncp burned into them, and are only acting as relays as
I generally only obtain a few (/60) real IPv6 prefixes per GW and they
only need to be on the APs.

GW1 - routerA - routerB - routerC - routerD - AP1
                                         |
GW2 - routerE - routerF - routerG - routerH - AP2
                           |
                         AP3

GW3 ...

(the actual topology of the testbed is way more complex than this
(covering ethernet, wifi, and moca) and I am not going into it here)

1) is there a way to configure hncpd as purely a relay, and NOT do any
address assignment at all on routers B,C,D,F,G,H?

2) have you tested that it is indeed possible to get the separate ipv6
prefixes from GW1,GW2,GW3 to AP1,AP2, AP3?

3) Can ULA and "Real" address assignment be distinguished along the
way? I have no problem assigning ULAs to the routers, but dont want to
use up real addresses on them.

4) What happens when someone pulls the plug on GW1, it reboots, and
gets a new Ipv6 subnet (I have seen comcast do this to me
every time that happens with the code I have in place now - no
retraction, and I go through hell manually eliminating every former
prefix from the network. Yes. I have upses. And cerowrt, at least,
stays up for 90+ days without a problem. But it happens and sucks when
it does)

> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet



--=20
Dave T=C3=A4ht

thttp://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks


From nobody Fri Feb 20 12:02:46 2015
Return-Path: <mellon@fugue.com>
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 CAA811A8894 for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 12:02:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 m1EyVP-lPOSW for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 12:02:44 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 785EC1A0089 for <homenet@ietf.org>; Fri, 20 Feb 2015 12:02:44 -0800 (PST)
Received: from [10.0.20.107] (c-71-233-43-215.hsd1.nh.comcast.net [71.233.43.215]) by toccata.fugue.com (Postfix) with ESMTPSA id 61A08238168C; Fri, 20 Feb 2015 15:02:43 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <BB621A07-282E-4814-9D56-3EFBF87814D0@iki.fi>
Date: Fri, 20 Feb 2015 15:01:50 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <71C98A06-0B23-4916-BFF8-CCF663A3F0A0@fugue.com>
References: <CAA93jw7eGxPBNX+5LqX+qTYfRxNDxQpKo1fecUa2XH3bAKgvQQ@mail.gmail.com> <BB621A07-282E-4814-9D56-3EFBF87814D0@iki.fi>
To: Markus Stenberg <markus.stenberg@iki.fi>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/ZAYonCrHyMHavYwb36KDzEqP7k4>
Cc: HOMENET <homenet@ietf.org>, Dave Taht <dave.taht@gmail.com>
Subject: Re: [homenet] A poll
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 20:02:45 -0000

I'd be a bit curious to know what people are using for test hardware.   =
That's a big issue for me.   I have a WNDR3800 as an internal router, =
and a Mac Mini as my edge router, and haven't had time to really try to =
make HNCP and Babel work with them.   Making IPv6 prefix delegation work =
on a stock Ubuntu device is not seamless.   :/


From nobody Fri Feb 20 12:13:32 2015
Return-Path: <cyrus@openwrt.org>
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 66B8A1A0011 for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 12:13:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] 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 V-49wHUNLzOf for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 12:13:29 -0800 (PST)
Received: from mail.core-networks.de (mail.core-networks.de [82.96.72.7]) by ietfa.amsl.com (Postfix) with ESMTP id 1301B1A0006 for <homenet@ietf.org>; Fri, 20 Feb 2015 12:13:29 -0800 (PST)
Received: from localhost ([127.0.0.1]) by mail.core-networks.de id 1YOtx1-0006be-Cn with ESMTPSA (TLSv1.2:DHE-RSA-AES256-SHA:256) for ; Fri, 20 Feb 2015 21:13:27 +0100
User-Agent: K-9 Mail for Android
In-Reply-To: <71C98A06-0B23-4916-BFF8-CCF663A3F0A0@fugue.com>
References: <CAA93jw7eGxPBNX+5LqX+qTYfRxNDxQpKo1fecUa2XH3bAKgvQQ@mail.gmail.com> <BB621A07-282E-4814-9D56-3EFBF87814D0@iki.fi> <71C98A06-0B23-4916-BFF8-CCF663A3F0A0@fugue.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----OA87AYG0Y3BFE9AZZVE7GD8N30O11C"
Content-Transfer-Encoding: 8bit
From: Steven Barth <cyrus@openwrt.org>
Date: Fri, 20 Feb 2015 21:13:23 +0100
To: Ted Lemon <mellon@fugue.com>,Markus Stenberg <markus.stenberg@iki.fi>
Message-ID: <4CE4405A-B4B3-40A2-AD8D-5127F932255A@openwrt.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/litOaNnQOXFKAr5FDy06Sn06UVQ>
Cc: HOMENET <homenet@ietf.org>, Dave Taht <dave.taht@gmail.com>
Subject: Re: [homenet] A poll
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 20:13:31 -0000

------OA87AYG0Y3BFE9AZZVE7GD8N30O11C
Content-Transfer-Encoding: 8bit
Content-Type: text/plain;
 charset=UTF-8




Am 20. Februar 2015 21:01:50 MEZ, schrieb Ted Lemon <mellon@fugue.com>:
>I'd be a bit curious to know what people are using for test hardware.  
>That's a big issue for me.   I have a WNDR3800 as an internal router,
>and a Mac Mini as my edge router, and haven't had time to really try to
>make HNCP and Babel work with them.   Making IPv6 prefix delegation
>work on a stock Ubuntu device is not seamless.   :/

Buffalo wzr600dhp with some bleeding edge openwrt w/ hnetd (hncp + dhcpv6pd) etc. as primary router + small number of wndr3800 and / or tplinks for testing openwrt and hncp.


------OA87AYG0Y3BFE9AZZVE7GD8N30O11C
Content-Type: text/html;
 charset=utf-8
Content-Transfer-Encoding: 8bit

<br>
<br>
<br>
Am 20. Februar 2015 21:01:50 MEZ, schrieb Ted Lemon &lt;mellon@fugue.com&gt;:<br>
&gt;I&#39;d be a bit curious to know what people are using for test hardware.  <br>
&gt;That&#39;s a big issue for me.   I have a WNDR3800 as an internal router,<br>
&gt;and a Mac Mini as my edge router, and haven&#39;t had time to really try to<br>
&gt;make HNCP and Babel work with them.   Making IPv6 prefix delegation<br>
&gt;work on a stock Ubuntu device is not seamless.   :/<br>
<br>
Buffalo wzr600dhp with some bleeding edge openwrt w/ hnetd (hncp + dhcpv6pd) etc. as primary router + small number of wndr3800 and / or tplinks for testing openwrt and hncp.<br>
<br>

------OA87AYG0Y3BFE9AZZVE7GD8N30O11C--


From nobody Fri Feb 20 12:23:45 2015
Return-Path: <marka@isc.org>
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 8CBF11A0039 for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 12:23:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.911
X-Spam-Level: 
X-Spam-Status: No, score=-6.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 GzN7gnbhnZVa for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 12:23:42 -0800 (PST)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [149.20.64.53]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BC2DC1A001C for <homenet@ietf.org>; Fri, 20 Feb 2015 12:23:42 -0800 (PST)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.pao1.isc.org (Postfix) with ESMTP id B9D1B349409; Fri, 20 Feb 2015 20:23:40 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id EBED2160067; Fri, 20 Feb 2015 20:30:33 +0000 (UTC)
Received: from rock.dv.isc.org (c122-106-252-81.belrs3.nsw.optusnet.com.au [122.106.252.81]) by zmx1.isc.org (Postfix) with ESMTPSA id B7EE416005B; Fri, 20 Feb 2015 20:30:33 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 534582A068E1; Sat, 21 Feb 2015 07:23:35 +1100 (EST)
To: Dave Taht <dave.taht@gmail.com>
From: Mark Andrews <marka@isc.org>
References: <CAA93jw7eGxPBNX+5LqX+qTYfRxNDxQpKo1fecUa2XH3bAKgvQQ@mail.gmail.com>
In-reply-to: Your message of "Fri, 20 Feb 2015 08:50:10 -0800." <CAA93jw7eGxPBNX+5LqX+qTYfRxNDxQpKo1fecUa2XH3bAKgvQQ@mail.gmail.com>
Date: Sat, 21 Feb 2015 07:23:34 +1100
Message-Id: <20150220202335.534582A068E1@rock.dv.isc.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/4LWGh0984s7eD7jq8tJ1YI3N4KA>
Cc: HOMENET <homenet@ietf.org>
Subject: Re: [homenet] A poll
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 20:23:44 -0000

In message <CAA93jw7eGxPBNX+5LqX+qTYfRxNDxQpKo1fecUa2XH3bAKgvQQ@mail.gmail.com>
, Dave Taht writes:
> The homenet working group has been laboring for several years now to
> find ways to make ipv6 more deployable to home (and presumably small
> business) users.
> 
> In addition to multiple specification documents some code has been
> produced to try and make things easier. At least in the USA, comcast
> has rolled out IPv6 to everyone that can get dhcpv6 to sort of work on
> their router, and/or is willing to install a custom firmware on their
> router to get that, and of course tunneling ipv6 is possible if the
> ISP does not support it.
> 
> So a quick poll:
> 
> 0) Have you managed to get ipv6 working at all? If so, how? What sort
> of problems did you encounter?

HE tunnel to a FreeBSD base router.  dhclient-exit-hooks are used to
automatically reconfigure the tunnel on IPv4 renumber events.

HE tunnel to a MacBookPro running 10.8.5.  The kernel panic when suspending
the MacBook with the tunnel enabled.
 
> 1) Have you attempted to deploy a routing protocol in your home? Which
> one, and why?

no.
 
> 2) Have you attempted to get hnetd's prefix distribution system
> working? (it supports linux mainline and openwrt presently)
 
no.

> 3) Do you use ethernet? How many clients in your home are ethernet 
> connected?

yes. 5
 
> 4) Do you use wifi? How many clients are wifi connected? Do you use
> range extenders?

yes. 9 to over 30.  This is bridged to the ethernet segment.
no range extenders.`
 
> 5) How many devices do you think you will have connected to the
> network in your home in 5 years? How many now?

20+

> 6) Do you use any other network connected technologies (homeplug,
> 802.14, LTE, etc). If so, which ones, and why?

no
 
> 7) Do you use mdns service discovery?

Some of the machine use it automaticall. 
 
> 8) Why are you here? (especially, if your answers to 0-2, are "no")
 
> -- 
> Dave Tht
> 
> http://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks
> 
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet

-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Fri Feb 20 12:33:18 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 5BABE1A008F for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 12:33:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.349
X-Spam-Level: 
X-Spam-Status: No, score=0.349 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, HELO_EQ_FR=0.35] autolearn=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 zJ_5lzLCDVCx for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 12:33:08 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 7D08D1A00BF for <homenet@ietf.org>; Fri, 20 Feb 2015 12:33:06 -0800 (PST)
Received: from potemkin.univ-paris7.fr (potemkin.univ-paris7.fr [IPv6:2001:660:3301:8000::1:1]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t1KKX1jq010875 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 20 Feb 2015 21:33:01 +0100
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by potemkin.univ-paris7.fr (8.14.4/8.14.4/relay2/56228) with ESMTP id t1KKX0QM019301; Fri, 20 Feb 2015 21:33:00 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id DA9372BFD0E; Fri, 20 Feb 2015 21:33:00 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id 4s4CUulr2KAi; Fri, 20 Feb 2015 21:32:59 +0100 (CET)
Received: from pirx.pps.jussieu.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 1E34C2BFD09; Fri, 20 Feb 2015 21:32:59 +0100 (CET)
Date: Fri, 20 Feb 2015 21:33:00 +0100
Message-ID: <87zj88b9xf.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Ted Lemon <mellon@fugue.com>
In-Reply-To: <71C98A06-0B23-4916-BFF8-CCF663A3F0A0@fugue.com>
References: <CAA93jw7eGxPBNX+5LqX+qTYfRxNDxQpKo1fecUa2XH3bAKgvQQ@mail.gmail.com> <BB621A07-282E-4814-9D56-3EFBF87814D0@iki.fi> <71C98A06-0B23-4916-BFF8-CCF663A3F0A0@fugue.com>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]); Fri, 20 Feb 2015 21:33:02 +0100 (CET)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Fri, 20 Feb 2015 21:33:01 +0100 (CET)
X-Miltered: at korolev with ID 54E799FD.003 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 54E799FC.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54E799FD.003 from potemkin.univ-paris7.fr/potemkin.univ-paris7.fr/null/potemkin.univ-paris7.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Enveloppe: 54E799FC.001 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54E799FD.003 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 54E799FC.001 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/O8Ge2qaGj9JCE66ZypKr7z-HKH4>
Cc: HOMENET <homenet@ietf.org>
Subject: [homenet] OpenWRT hardware [was: A poll]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 20:33:10 -0000

> I'd be a bit curious to know what people are using for test hardware.

The WNDR3800/WNDR3700v2 is still my favourite.  I've still got a couple
Asus 500GP v1, and they're just fine if you don't need 802.11n and can
fit in the slightly more limited flash.

Both models:

  - are well supported by OpenWRT;
  - are very difficult to brick (just set up a tftp server and interrupt
    the boot sequence to reflash);
  - have a manageable built-in switch that's configurable from OpenWRT.

The WNDR3800 has 16/128 flash/RAM, the 3700v2 16/64, the Asus 8/32.

The WNDR3800/3700v2 has some other nice features, like a second gigabit
NIC that doesn't go through the internal switch (to get VLANs without
messing with the switch), support for 5GHz, and two radios usable
simultaneously (which Babel is able to use for avoiding intra-route
interference).

-- Juliusz


From nobody Fri Feb 20 12:39:01 2015
Return-Path: <daveoran@orandom.net>
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 6DCFE1A1BC5 for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 12:39:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.165
X-Spam-Level: 
X-Spam-Status: No, score=0.165 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, SPF_SOFTFAIL=0.665] autolearn=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 ANuwC53Vkujg for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 12:38:58 -0800 (PST)
Received: from spark.crystalorb.net (spark.crystalorb.net [IPv6:2607:fca8:1530::c]) (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 E4B651A1B36 for <homenet@ietf.org>; Fri, 20 Feb 2015 12:38:58 -0800 (PST)
Received: from [10.131.118.38] (rtp-isp-nat-pool1-1.cisco.com [64.102.254.34]) (authenticated bits=0) by spark.crystalorb.net (8.14.4/8.14.4/Debian-4) with ESMTP id t1KKdZWn005440 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 20 Feb 2015 12:39:36 -0800
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2081\))
From: David Oran <daveoran@orandom.net>
In-Reply-To: <CAA93jw7eGxPBNX+5LqX+qTYfRxNDxQpKo1fecUa2XH3bAKgvQQ@mail.gmail.com>
Date: Fri, 20 Feb 2015 15:38:50 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <CF18E14B-F7A9-4065-940B-67F833CAF91B@orandom.net>
References: <CAA93jw7eGxPBNX+5LqX+qTYfRxNDxQpKo1fecUa2XH3bAKgvQQ@mail.gmail.com>
To: Dave Taht <dave.taht@gmail.com>
X-Mailer: Apple Mail (2.2081)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/Ow7EjAAeV25CKpl0izz5gosG7Ww>
Cc: HOMENET <homenet@ietf.org>
Subject: Re: [homenet] A poll
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 20:39:00 -0000

> On Feb 20, 2015, at 11:50 AM, Dave Taht <dave.taht@gmail.com> wrote:
>=20
> The homenet working group has been laboring for several years now to
> find ways to make ipv6 more deployable to home (and presumably small
> business) users.
>=20
> In addition to multiple specification documents some code has been
> produced to try and make things easier. At least in the USA, comcast
> has rolled out IPv6 to everyone that can get dhcpv6 to sort of work on
> their router, and/or is willing to install a custom firmware on their
> router to get that, and of course tunneling ipv6 is possible if the
> ISP does not support it.
>=20
> So a quick poll:
>=20
> 0) Have you managed to get ipv6 working at all? If so, how? What sort
> of problems did you encounter?
>=20
Works fine at both my Cambridge home and my Mountain View Condo. In both =
cases I=E2=80=99m using Airport Extremes as the home router. In one case =
it=E2=80=99s a DOCSIS 3.0 modem from Comcast, with the Airports doing =
PD. In the other case it=E2=80=99s behind a pair of Ubiquity radios =
homed on a Linux router in turn connected to Comcast business service =
with PD.

> 1) Have you attempted to deploy a routing protocol in your home? Which
> one, and why?
>=20
I run OSPF at home in Cambridge, mostly to route in a controlled way =
among some VLANs I use for isolation purposes. There are trunk VLANs =
running from the main switch to an access switch in my home office.

> 2) Have you attempted to get hnetd's prefix distribution system
> working? (it supports linux mainline and openwrt presently)
>=20
No. The Airport Extreme IPv6 with PD has been adequate for my needs.

> 3) Do you use ethernet? How many clients in your home are ethernet =
connected?
>=20
Yes. Total count excluding 802.11 clients is probably 10-12. 4 macs, a =
NAS, AppleTV, two Tivos, Sonos bridge, 2 printers.

> 4) Do you use wifi?
Yes, extensively - In Cambrige to get coverage I have a WiFi AP in each =
of the 3 floors (Airport Extreme + 2 Airport express.

> How many clients are wifi connected?
additional 5-7

> Do you use
> range extenders?
>=20
No, each of the AP=E2=80=99s is wired with Cat5 to a big Cisco Cat3600 =
switch/router.

> 5) How many devices do you think you will have connected to the
> network in your home in 5 years? How many now?
>=20
In five years, probably at least 50, maybe more if I decide to use WiFi =
light bulbs and window/door sensors and other random stuff.

> 6) Do you use any other network connected technologies (homeplug,
> 802.14, LTE, etc). If so, which ones, and why?
Not at present. All 802.11AC and N.

>=20
> 7) Do you use mdns service discovery?
>=20
Yes, extensively.

> 8) Why are you here? (especially, if your answers to 0-2, are "no=E2=80=9D=
)
Because bridging sucks, and IPv6 allows us to have aminimal-touch =
routing solution that =E2=80=9Cjust works=E2=80=9D.

>=20
>=20
> --=20
> Dave T=C3=A4ht
>=20
> http://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks
>=20
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet


From nobody Fri Feb 20 14:14:35 2015
Return-Path: <markus.stenberg@iki.fi>
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 9C6C71A8865 for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 14:14:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.121
X-Spam-Level: 
X-Spam-Status: No, score=-1.121 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_NEUTRAL=0.779] autolearn=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 axACaXZLW0tp for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 14:14:31 -0800 (PST)
Received: from jenni1.inet.fi (mta-out1.inet.fi [62.71.2.195]) by ietfa.amsl.com (Postfix) with ESMTP id 02EC91A028A for <homenet@ietf.org>; Fri, 20 Feb 2015 14:14:31 -0800 (PST)
Received: from poro.lan (80.220.64.126) by jenni1.inet.fi (8.5.142.08) (authenticated as stenma-47) id 54E3C7030063EBB7; Sat, 21 Feb 2015 00:14:19 +0200
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Markus Stenberg <markus.stenberg@iki.fi>
In-Reply-To: <CAA93jw6MhqJ4OVO5G7gYQf71XVeCzThXJt5QgDaO07Jz0+cWQg@mail.gmail.com>
Date: Sat, 21 Feb 2015 00:14:15 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <14659C51-74F0-442E-9B60-5B98DB957287@iki.fi>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <F2818678-A728-4300-896C-E220A0DF0D1A@employees.org> <ADBDED5C-5279-4A04-B7C8-FCCB453A8C4F@gmail.com> <B2BEAF63-D219-41A0-8209-1EEFE9667440@fugue.com> <54E6318C.9030609@openwrt.org> <C8437CBF-DEF5-49D1-9908-6C784DAA0137@fugue.com> <0E03C679-3253-42B3-A9F6-605C27F2BCBA@openwrt.org> <CAA93jw6MhqJ4OVO5G7gYQf71XVeCzThXJt5QgDaO07Jz0+cWQg@mail.gmail.com>
To: Dave Taht <dave.taht@gmail.com>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/C15meNsjLEkfItmKbjkop-dmsXE>
Cc: Markus Stenberg <markus.stenberg@iki.fi>, Ted Lemon <mellon@fugue.com>, Ole Troan <otroan@employees.org>, Steven Barth <cyrus@openwrt.org>, Ralph Droms <rdroms.ietf@gmail.com>, "homenet@ietf.org Group" <homenet@ietf.org>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 22:14:33 -0000

> On 20.2.2015, at 22.01, Dave Taht <dave.taht@gmail.com> wrote:
> On Fri, Feb 20, 2015 at 11:34 AM, Steven Barth <cyrus@openwrt.org> =
wrote:
>>=20
>> Am 19. Februar 2015 20:05:56 MEZ, schrieb Ted Lemon =
<mellon@fugue.com>:
>>> Hm, I will have to try it out.   Is it in a distribution?
>>=20
>> ohybridproxy in openwrt. It's mainly useful with hnetd (hncp) though.
>>=20
>> Manual configuration without hncp is a bit awkward since you need to =
name each link manually and on every router configure the resolver (e.g. =
dnsmasq). I guess we might want to provide a little example for 2 links =
at some point.
> I would like to deploy hncp in my upcoming make-wifi-fast testbed.
> However the biggest headache is ensuring that all the routers
> inbetween have hncp burned into them, and are only acting as relays as
> I generally only obtain a few (/60) real IPv6 prefixes per GW and they
> only need to be on the APs.
>=20
> GW1 - routerA - routerB - routerC - routerD - AP1
>                                         |
> GW2 - routerE - routerF - routerG - routerH - AP2
>                           |
>                         AP3
>=20
> GW3 ...
>=20
> (the actual topology of the testbed is way more complex than this
> (covering ethernet, wifi, and moca) and I am not going into it here)
>=20
> 1) is there a way to configure hncpd as purely a relay, and NOT do any
> address assignment at all on routers B,C,D,F,G,H?

In theory (=3Dspec), but not in current implementation (I _think_). You =
do not really need non-linklocal addresses for HNCP, or routing =
protocol, so as long as there are no hosts on the link.. (traceroute is =
a bitch though given just linklocals)

As workaround in current implementation, if you set it to assign e.g. =
/80 per link used for your intermediate links, you would have almost all =
of address space left; however, in your case, I am not sure you can even =
afford to split one /64 for that purpose.

> 2) have you tested that it is indeed possible to get the separate ipv6
> prefixes from GW1,GW2,GW3 to AP1,AP2, AP3?

Yes.

> 3) Can ULA and "Real" address assignment be distinguished along the
> way? I have no problem assigning ULAs to the routers, but dont want to
> use up real addresses on them.

In theory (=3Dspec), not in current implementation (ULA is actively =
discouraged in current impl, I cannot remember if there was option to =
override).

> 4) What happens when someone pulls the plug on GW1, it reboots, and
> gets a new Ipv6 subnet (I have seen comcast do this to me
> every time that happens with the code I have in place now - no
> retraction, and I go through hell manually eliminating every former
> prefix from the network. Yes. I have upses. And cerowrt, at least,
> stays up for 90+ days without a problem. But it happens and sucks when
> it does)

Renumbering should just work as usual. I.e. rest of nodes should learn =
of the new prefix, and old one should disappear.

-Markus=


From nobody Fri Feb 20 14:22:45 2015
Return-Path: <dave.taht@gmail.com>
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 6B0521A8885 for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 14:22:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 bHdSCgnKJ_rG for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 14:22:41 -0800 (PST)
Received: from mail-ob0-x22d.google.com (mail-ob0-x22d.google.com [IPv6:2607:f8b0:4003:c01::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 80DDF1A88BE for <homenet@ietf.org>; Fri, 20 Feb 2015 14:22:38 -0800 (PST)
Received: by mail-ob0-f173.google.com with SMTP id uy5so27212919obc.4 for <homenet@ietf.org>; Fri, 20 Feb 2015 14:22:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=Ys0H+uIQzNy7WkzLXE5rQwqhxtEuPTHVmxf+/7EjwvM=; b=MzQNajqFmEXiijZz8Da/Z5uWHkgDFgqntnxXlR3r05PtqmEfrnNzFp2pbaKA5flRqy nXWWtoL287mRVPQms7bsFgCrGkfJSpo746mTSD2hSZgoUB1s8hjaeQpP/EoLwsaMCCVk MbF+PbnwUvVhtBd+VT5AqNRcfByWkL6e6Aj34D7C9yOVpmfOo0qM0n9rXYrEI50BrjXM a5Ict6mTHICT7N+BrHOSLl/36UU76idpharMTTz5fMpUwhFSd3mH0tj7Q6dKf9OmeoAl y5BeRkpbW5VA+jMSLOm2zUMgTPbo7nzexEirx/n69xibrisn4srrCahBowanO1UBJpV9 5MOQ==
MIME-Version: 1.0
X-Received: by 10.202.62.70 with SMTP id l67mr7647148oia.59.1424470957669; Fri, 20 Feb 2015 14:22:37 -0800 (PST)
Received: by 10.202.51.66 with HTTP; Fri, 20 Feb 2015 14:22:37 -0800 (PST)
In-Reply-To: <87zj88b9xf.wl-jch@pps.univ-paris-diderot.fr>
References: <CAA93jw7eGxPBNX+5LqX+qTYfRxNDxQpKo1fecUa2XH3bAKgvQQ@mail.gmail.com> <BB621A07-282E-4814-9D56-3EFBF87814D0@iki.fi> <71C98A06-0B23-4916-BFF8-CCF663A3F0A0@fugue.com> <87zj88b9xf.wl-jch@pps.univ-paris-diderot.fr>
Date: Fri, 20 Feb 2015 14:22:37 -0800
Message-ID: <CAA93jw4ZF8=QFMGmb1uPB+xxcNHadSZCEMkTTuDfOHrABWg3Mg@mail.gmail.com>
From: Dave Taht <dave.taht@gmail.com>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/nIOU3IbZCucCDAmvJ6h6lqOQ8Aw>
Cc: HOMENET <homenet@ietf.org>, Ted Lemon <mellon@fugue.com>
Subject: Re: [homenet] OpenWRT hardware [was: A poll]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 22:22:43 -0000

On Fri, Feb 20, 2015 at 12:33 PM, Juliusz Chroboczek
<jch@pps.univ-paris-diderot.fr> wrote:
>> I'd be a bit curious to know what people are using for test hardware.
>
> The WNDR3800/WNDR3700v2 is still my favourite.  I've still got a couple
> Asus 500GP v1, and they're just fine if you don't need 802.11n and can
> fit in the slightly more limited flash.

Despite evaluating well over 60 products and chipsets in the past 3
years, I have yet to find something as nice as the wndr3800 as either
a R&D or day to day ultra-reliable home router.

More generically the ag71xx/ath9k chipsets it used are the most
aimiable to hacking on and there are hundreds upon hundreds of current
products based on that, like the WZR the homewrt folk used.

However single cpus like that with 32k dcache proved not up to the job
of 802.11ac and there is a lot of chaos and crap gear going around on
that standard.

Elsewhere the whole wifi industry is seemingly in a race to the
bottom. As one example, I use the nanostation M5s heavily, and they
(silently) changed the underlying chipset last year from one with two
ethernet interfaces, to 1 connected to a 100Mbit switch. Result - no
link status anymore, the impossibility of measuring traffic well
across the two interfaces, and an increase of latency under load to
the buffering in the switch.

The new nanostation IS a bit faster (mips 74k based rather than 24k),
and has twice the ram, for the same cost as the old, and it still has
8MB flash, so I should not complain too much, I guess. (My typical
topology is 2 nanostations connected to a picostation  M2HP AP)

I have been seeking an integrated outdoor tri radio replacement for
that particular setup for a long time.

As for everything else I have evaluated, I am thinking of publishing
it all, after I tone down the invective logged in my notes.
Most recently I took a look at two 802.11ac products from d-link.

https://lists.bufferbloat.net/pipermail/bloat/2015-February/002310.html

ubnt is *clued* in comparison to nearly everyone else.

> Both models:
>
>   - are well supported by OpenWRT;
>   - are very difficult to brick (just set up a tftp server and interrupt
>     the boot sequence to reflash);
>   - have a manageable built-in switch that's configurable from OpenWRT.
>
> The WNDR3800 has 16/128 flash/RAM, the 3700v2 16/64, the Asus 8/32.
>
> The WNDR3800/3700v2 has some other nice features, like a second gigabit
> NIC that doesn't go through the internal switch (to get VLANs without
> messing with the switch), support for 5GHz, and two radios usable
> simultaneously (which Babel is able to use for avoiding intra-route
> interference).

With the current chaos calmer code (using linux 3.18) I get a
downstream rate of 560mbits and an upstream of 146 on the ethernet.

The ratio used to be closer to 340/180.

So much else in my lab (notably the tcps) has changed since the last
time I did benchmarking that I have no idea what to point at, and
openwrt enables the wndr3800 vlan by default, which is not my fav
thing, either, and I haven=C2=B4t poked into any of it much, being
presently focused on evaluating the latest patchset for minstrel-blues
( http://www.linuxplumbersconf.org/2014/ocw/sessions/2439 ) right now.


> -- Juliusz
>
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet



--=20
Dave T=C3=A4ht

thttp://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks


From nobody Fri Feb 20 14:24:51 2015
Return-Path: <rdroms.ietf@gmail.com>
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 3ADFC1A88A6 for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 14:24:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 oQsoxsB8VWOt for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 14:24:49 -0800 (PST)
Received: from mail-qa0-x22a.google.com (mail-qa0-x22a.google.com [IPv6:2607:f8b0:400d:c00::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 763991A026E for <homenet@ietf.org>; Fri, 20 Feb 2015 14:24:49 -0800 (PST)
Received: by mail-qa0-f42.google.com with SMTP id w8so14611258qac.1 for <homenet@ietf.org>; Fri, 20 Feb 2015 14:24:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=4zIq60GNvALE9Tbvo3EZLsB4UjaPqSUYzUTWQrHSDho=; b=z0ML/w/6JiGJhfwMWUiNMqmSxG1S29nuDekvPaRtnBG5tbIIrtP6TbZ1nJkXnStlr4 3BroVRGdrMeZgbKn8+3ernj2ifmwnt2bmntxJ4cDbeIjyVyodPZO1DRKfvNmQeMDrpVZ 6DfaJlf5Oyy24w4RINVzCQvDIgY5VQdKrlPSy7zJnymqhYeU/u/1Xo6mMG1NTyJ3m86q fv5icZpRUk3USRKVjELkZBtgb+BXA4UADA5Vawf06YvlWNWm53cG2xKvLXJp7cQRNhfS heoSD50PjsIcG37hyCUT1rEb+Y1o8Dx7uMOa4WWp2VlbrQgumT/ktpvCFOqjqSPSPEK+ Z2WA==
X-Received: by 10.140.106.72 with SMTP id d66mr18656qgf.60.1424471088682; Fri, 20 Feb 2015 14:24:48 -0800 (PST)
Received: from ?IPv6:2601:6:6780:7900:35ce:f98a:96a7:b3f7? ([2601:6:6780:7900:35ce:f98a:96a7:b3f7]) by mx.google.com with ESMTPSA id w4sm4825609qat.49.2015.02.20.14.24.47 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 20 Feb 2015 14:24:48 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <CAA93jw7eGxPBNX+5LqX+qTYfRxNDxQpKo1fecUa2XH3bAKgvQQ@mail.gmail.com>
Date: Fri, 20 Feb 2015 17:24:45 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <CDCC8390-D480-4733-98CA-D90253F92014@gmail.com>
References: <CAA93jw7eGxPBNX+5LqX+qTYfRxNDxQpKo1fecUa2XH3bAKgvQQ@mail.gmail.com>
To: Dave Taht <dave.taht@gmail.com>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/bumIXZEYNgruxgGMUHFXFztFoIk>
Cc: HOMENET <homenet@ietf.org>
Subject: Re: [homenet] A poll
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 22:24:51 -0000

0) Have you managed to get ipv6 working at all? If so, how? What sort
of problems did you encounter?

I originally had IPv6 service through a tunnel to SixXS, which was OK =
once I got the details sorted.

I'm using a Linksy E4200 with development software from a project at =
Cisco that includes IPv6 support.  Without any announcement to me, =
Comcast turned on IPv6 service to my house and AIBFM I had a second =
prefix, advertised from the Linksys home gateway.  Interestingly, it did =
not disrupt my home service at all and I literally discovered the =
service was on as I was working on a project using IPv6 on the home =
network.  Devices on the network were unexpectedly showing a second =
prefix, which I checked to confirm was coming through PD to the Linksys =
home gateway.  I turned off the SixXS tunnel, and am now using just IPv6 =
service from Comcast.

1) Have you attempted to deploy a routing protocol in your home? Which
one, and why?

No.

2) Have you attempted to get hnetd's prefix distribution system
working? (it supports linux mainline and openwrt presently)

No.

3) Do you use ethernet? How many clients in your home are ethernet =
connected?

Yes.  ~7 devices; some through a homeplug extension

4) Do you use wifi? How many clients are wifi connected? Do you use
range extenders?

Yes. ~10 devices.  I have 3 access points on ethernet back to the home =
gateway.

5) How many devices do you think you will have connected to the
network in your home in 5 years? How many now?

30 devices in 5 years; maybe more if sensors and actuators are =
available.  15-20 now, depending on how many little devices are =
connected for projects.

6) Do you use any other network connected technologies (homeplug,
802.14, LTE, etc). If so, which ones, and why?

homeplug, 802.15.4 (for projects; not production)

7) Do you use mdns service discovery?

Extensively.

8) Why are you here? (especially, if your answers to 0-2, are "no")

I'm trying to figure out how we get to a network that provides the =
services I want, avoids performance issues and runs completely =
autonomously.


From nobody Fri Feb 20 14:26:44 2015
Return-Path: <mellon@fugue.com>
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 ADF021A8885 for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 14:26:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 8tZBvj1cM3kR for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 14:26:40 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id B2F2A1A026E for <homenet@ietf.org>; Fri, 20 Feb 2015 14:26:40 -0800 (PST)
Received: from [10.0.20.107] (c-71-233-43-215.hsd1.nh.comcast.net [71.233.43.215]) by toccata.fugue.com (Postfix) with ESMTPSA id ABC55238059C; Fri, 20 Feb 2015 17:26:39 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <CAA93jw4ZF8=QFMGmb1uPB+xxcNHadSZCEMkTTuDfOHrABWg3Mg@mail.gmail.com>
Date: Fri, 20 Feb 2015 17:25:44 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <9AF3D5EB-F092-41F1-989D-E6B28235C78D@fugue.com>
References: <CAA93jw7eGxPBNX+5LqX+qTYfRxNDxQpKo1fecUa2XH3bAKgvQQ@mail.gmail.com> <BB621A07-282E-4814-9D56-3EFBF87814D0@iki.fi> <71C98A06-0B23-4916-BFF8-CCF663A3F0A0@fugue.com> <87zj88b9xf.wl-jch@pps.univ-paris-diderot.fr> <CAA93jw4ZF8=QFMGmb1uPB+xxcNHadSZCEMkTTuDfOHrABWg3Mg@mail.gmail.com>
To: Dave Taht <dave.taht@gmail.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/xnR1bLCY2QCzlRd5__OJsRell9g>
Cc: HOMENET <homenet@ietf.org>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] OpenWRT hardware [was: A poll]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 22:26:42 -0000

On Feb 20, 2015, at 5:22 PM, Dave Taht <dave.taht@gmail.com> wrote:
> Despite evaluating well over 60 products and chipsets in the past 3
> years, I have yet to find something as nice as the wndr3800 as either
> a R&D or day to day ultra-reliable home router.

What about something like the Cubietruck, which isn't strictly a WiFi =
base station, but could function as one?


From nobody Fri Feb 20 14:28:09 2015
Return-Path: <brian.e.carpenter@gmail.com>
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 2EDDD1A8898 for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 14:28:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 hY-kUwyUa1hR for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 14:28:06 -0800 (PST)
Received: from mail-pd0-x229.google.com (mail-pd0-x229.google.com [IPv6:2607:f8b0:400e:c02::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0EF921A019B for <homenet@ietf.org>; Fri, 20 Feb 2015 14:28:06 -0800 (PST)
Received: by pdbfl12 with SMTP id fl12so10647448pdb.2 for <homenet@ietf.org>; Fri, 20 Feb 2015 14:28:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=F6m8uQoPnXpGIla6M2NX7rsDXlsnr/Hg9YamfGIHvd4=; b=Cv4Hlc1HBKQcYcfUsdkRCwnb2DR7J/68IycK5c976Pqcq69Xho04nuiRuEIHW9vptX P139eEFULgzN8sIyQhH3NnsT4c/vqvlQcJBS647fuAn6Mu5niOHT2pBR8JlnAzL+wB1W TVCDg9kX0DqwOYrkFNzyCMLxNLXbNFcSqz2TQPH39q6ioSkqGNARcH06pRMCMbOB1amj i63rTGDcqiE7tsuo/0WzUwc+a1HrhZCXDmk4u/Krj5CyUNqhiM1okfZzcjptyCT9XzUT 1RmzV14x9edtjCftMGjKLc4nOVn2K94sFnxsYe5nzXNkBL0SBdl91TAFy9We/wHFTQ0o KFkg==
X-Received: by 10.70.37.238 with SMTP id b14mr40914pdk.50.1424471285359; Fri, 20 Feb 2015 14:28:05 -0800 (PST)
Received: from ?IPv6:2406:e007:7a9d:1:28cc:dc4c:9703:6781? ([2406:e007:7a9d:1:28cc:dc4c:9703:6781]) by mx.google.com with ESMTPSA id r7sm20330114pdo.90.2015.02.20.14.28.02 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 20 Feb 2015 14:28:04 -0800 (PST)
Message-ID: <54E7B50E.1000908@gmail.com>
Date: Sat, 21 Feb 2015 11:28:30 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Dave Taht <dave.taht@gmail.com>, HOMENET <homenet@ietf.org>
References: <CAA93jw7eGxPBNX+5LqX+qTYfRxNDxQpKo1fecUa2XH3bAKgvQQ@mail.gmail.com>
In-Reply-To: <CAA93jw7eGxPBNX+5LqX+qTYfRxNDxQpKo1fecUa2XH3bAKgvQQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/8jl6qcPuKXkw-2RBf4X_7IgvKfQ>
Subject: Re: [homenet] A poll
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 22:28:08 -0000

On 21/02/2015 05:50, Dave Taht wrote:

> So a quick poll:

Goodie, I love polls (not) ;-)

> 0) Have you managed to get ipv6 working at all? If so, how? What sort
> of problems did you encounter?

Yes.

(a) Using SixXs/ayiya. Geek problems (the SixXs geeky registration
interface, and the fact that installation is definitely not for
the general public). But it works very reliably for a single host.

(b) With my current ISP, native dual stack service via a FritzBox.
Worked out the box. Until it didn't, when the ISP admitted to switching
IPv6 off without warning due to unspecified issues with some customers.
Then they switched it on again without explanation, and it works fine
again. [Probably, the issue was MTU size problems with a well-known
CDN's nearest POP, which was across the Tasman Sea at the time; compounded
by Google's recent bad hair week.]

I've gone into detail there because for more than a year, my wife was
using IPv6 without knowing it (on Windows 8). But when the above mentioned
problems occurred, she noticed PDQ and did not have SixXs to fall back
on. So we had to disable IPv6 on her machine. Happy Eyeballs did *not*
conceal the problem.

> 1) Have you attempted to deploy a routing protocol in your home? Which
> one, and why?

No, sorry, only one link here.

> 2) Have you attempted to get hnetd's prefix distribution system
> working? (it supports linux mainline and openwrt presently)

No

> 3) Do you use ethernet? How many clients in your home are ethernet connected?

Normally zero. I would plug in if I hit wireless issues.

> 4) Do you use wifi? How many clients are wifi connected? 

Two to four (house guests get free Wi-Fi ;-). My ancient
printer refuses to break, so that is hard wired to a computer.

> Do you use range extenders?

No

> 5) How many devices do you think you will have connected to the
> network in your home in 5 years?

Let's guess 10. But the interesting questions are how many
routers, and will it be dual-homed.

> How many now?
> 
> 6) Do you use any other network connected technologies (homeplug,
> 802.14, LTE, etc). If so, which ones, and why?

No.

> 7) Do you use mdns service discovery?

No

> 8) Why are you here? (especially, if your answers to 0-2, are "no")

http://tools.ietf.org/html/rfc3935

   Brian


From nobody Fri Feb 20 14:36:36 2015
Return-Path: <dave.taht@gmail.com>
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 56D541A032D for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 14:36:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 F9ZxTgIiibc7 for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 14:36:33 -0800 (PST)
Received: from mail-oi0-x22c.google.com (mail-oi0-x22c.google.com [IPv6:2607:f8b0:4003:c06::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BA5B01A028A for <homenet@ietf.org>; Fri, 20 Feb 2015 14:36:32 -0800 (PST)
Received: by mail-oi0-f44.google.com with SMTP id a3so5078865oib.3 for <homenet@ietf.org>; Fri, 20 Feb 2015 14:36:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=iBMFqd8DSq08BbvyJLcXtYUFpDsBzRVXF+44UtKa4EU=; b=esHZfncxq1ag1jhiAzPCtrcqx070xEu3XKk/BsTIyonKVGiYcTevLFvhxHbXWUmy/A OJ1z69AcoXaNc7s1cU7vfFL+w97/9v7yXLYFv3eHX/HzqmltEMsDW4UL8uV5KLhslWhm FpW4XUIwQmIyVG6ZT+Sntb3xDxJejOkALJcmY80LrfJdjdROgyX7NiZ4zO4YsuvUDWcW ngWo+7MP3iOt3VpT8lhlTzXgIlOjlUzibjnSyYVQQmgv5tmVRYZj5WkjQVXKx5HPgxEL FG4esvRPiYfedne7/JXs6f6PcFRazlbSS3UnlNr4+oPoen89qVYpJClHcsQTYmu02JQ3 CdGQ==
MIME-Version: 1.0
X-Received: by 10.60.57.9 with SMTP id e9mr53749oeq.24.1424471792033; Fri, 20 Feb 2015 14:36:32 -0800 (PST)
Received: by 10.202.51.66 with HTTP; Fri, 20 Feb 2015 14:36:31 -0800 (PST)
In-Reply-To: <CAA93jw4ZF8=QFMGmb1uPB+xxcNHadSZCEMkTTuDfOHrABWg3Mg@mail.gmail.com>
References: <CAA93jw7eGxPBNX+5LqX+qTYfRxNDxQpKo1fecUa2XH3bAKgvQQ@mail.gmail.com> <BB621A07-282E-4814-9D56-3EFBF87814D0@iki.fi> <71C98A06-0B23-4916-BFF8-CCF663A3F0A0@fugue.com> <87zj88b9xf.wl-jch@pps.univ-paris-diderot.fr> <CAA93jw4ZF8=QFMGmb1uPB+xxcNHadSZCEMkTTuDfOHrABWg3Mg@mail.gmail.com>
Date: Fri, 20 Feb 2015 14:36:31 -0800
Message-ID: <CAA93jw73oCbTRj9LFBPhqq1jj25ks=3-hqb4kV+iWn9wTj__4A@mail.gmail.com>
From: Dave Taht <dave.taht@gmail.com>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/c5ifLM9M-xKNTYZSGNbykqh5-5g>
Cc: HOMENET <homenet@ietf.org>, Ted Lemon <mellon@fugue.com>
Subject: Re: [homenet] OpenWRT hardware [was: A poll]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 22:36:35 -0000

On Fri, Feb 20, 2015 at 2:22 PM, Dave Taht <dave.taht@gmail.com> wrote:
> On Fri, Feb 20, 2015 at 12:33 PM, Juliusz Chroboczek
> <jch@pps.univ-paris-diderot.fr> wrote:
>>> I'd be a bit curious to know what people are using for test hardware.
>>
>> The WNDR3800/WNDR3700v2 is still my favourite.  I've still got a couple
>> Asus 500GP v1, and they're just fine if you don't need 802.11n and can
>> fit in the slightly more limited flash.
>
> Despite evaluating well over 60 products and chipsets in the past 3
> years, I have yet to find something as nice as the wndr3800 as either
> a R&D or day to day ultra-reliable home router.
>
> More generically the ag71xx/ath9k chipsets it used are the most
> aimiable to hacking on and there are hundreds upon hundreds of current
> products based on that, like the WZR the homewrt folk used.
>
> However single cpus like that with 32k dcache proved not up to the job
> of 802.11ac and there is a lot of chaos and crap gear going around on
> that standard.
>
> Elsewhere the whole wifi industry is seemingly in a race to the
> bottom. As one example, I use the nanostation M5s heavily, and they
> (silently) changed the underlying chipset last year from one with two
> ethernet interfaces, to 1 connected to a 100Mbit switch. Result - no
> link status anymore, the impossibility of measuring traffic well
> across the two interfaces, and an increase of latency under load to
> the buffering in the switch.
>
> The new nanostation IS a bit faster (mips 74k based rather than 24k),
> and has twice the ram, for the same cost as the old, and it still has
> 8MB flash, so I should not complain too much, I guess. (My typical
> topology is 2 nanostations connected to a picostation  M2HP AP)
>
> I have been seeking an integrated outdoor tri radio replacement for
> that particular setup for a long time.
>
> As for everything else I have evaluated, I am thinking of publishing
> it all, after I tone down the invective logged in my notes.
> Most recently I took a look at two 802.11ac products from d-link.
>
> https://lists.bufferbloat.net/pipermail/bloat/2015-February/002310.html
>
> ubnt is *clued* in comparison to nearly everyone else.

The tp-link archer C7 v2, after a year of teething pains on the ath10k
interface, is a not horrible platform for openwrt development
(and the ath9k also on board, is great).  Just dont expect the claimed
802.11ac rates on the wifi,  it does not have enough
cpu to push it that hard. It was only getting wndr3800 style
forwarding rates when I last tried on on ethernet also.

I was fairly impressed with the capabilities of the netgear x4, but was
able to crash it regularly in testing when I last pulled it out and I dont =
think
the gpl drop landed yet so there is no open source for it.

There are a couple other 802.11ac routers out there like asus=C2=B4s and
so on, I do hope the market starts sorting out one or more that is useful
to hack on.

Felix recommended trying the d-link DIR-860L *model B*, but as yet I
havent sorted out
how to actually order that. He is also hot on the mt72 chipset in it
as a candidate for multi-station queueing.

I note that I have not, for most of the last year, been heads down
into any of this stuff, I burned out pretty badly as we stablized
cerowrt by last april and needed a major break.

I happen to like gfiber=C2=B4s new ethernet/wifi/video gw quite a bit, but
that is only just now beginning be deployed in austin, and there is
still a need for a followup release of the software, and I cant talk
about it much, since I worked on it. I dont see much hope of seeing
general support for the chipset it used (mindspeed) in mainline linux,
either.

..

I think that is all of my invective-free notes on various existing products=
.

>> Both models:
>>
>>   - are well supported by OpenWRT;
>>   - are very difficult to brick (just set up a tftp server and interrupt
>>     the boot sequence to reflash);
>>   - have a manageable built-in switch that's configurable from OpenWRT.
>>
>> The WNDR3800 has 16/128 flash/RAM, the 3700v2 16/64, the Asus 8/32.
>>
>> The WNDR3800/3700v2 has some other nice features, like a second gigabit
>> NIC that doesn't go through the internal switch (to get VLANs without
>> messing with the switch), support for 5GHz, and two radios usable
>> simultaneously (which Babel is able to use for avoiding intra-route
>> interference).
>
> With the current chaos calmer code (using linux 3.18) I get a
> downstream rate of 560mbits and an upstream of 146 on the ethernet.
>
> The ratio used to be closer to 340/180.
>
> So much else in my lab (notably the tcps) has changed since the last
> time I did benchmarking that I have no idea what to point at, and
> openwrt enables the wndr3800 vlan by default, which is not my fav
> thing, either, and I haven=C2=B4t poked into any of it much, being
> presently focused on evaluating the latest patchset for minstrel-blues
> ( http://www.linuxplumbersconf.org/2014/ocw/sessions/2439 ) right now.
>
>
>> -- Juliusz
>>
>> _______________________________________________
>> homenet mailing list
>> homenet@ietf.org
>> https://www.ietf.org/mailman/listinfo/homenet
>
>
>
> --
> Dave T=C3=A4ht
>
> thttp://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks



--=20
Dave T=C3=A4ht

thttp://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks


From nobody Fri Feb 20 14:40:28 2015
Return-Path: <eckert@cisco.com>
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 EBB131A032D for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 14:40:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 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_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 HL1qeKUGoNBA for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 14:40:25 -0800 (PST)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6FF551A8A75 for <homenet@ietf.org>; Fri, 20 Feb 2015 14:39:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1005; q=dns/txt; s=iport; t=1424471967; x=1425681567; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=Rp0a/aK/9hWHpl2+weOwLcOJ9z7Nq4GpCwkSwgMAEhE=; b=lsCiCc7XCmVWLeDyTg9HdVbA9AK5Dt+ZgRWuRhp04U58mrDtZAz6bKA+ xxiFXkncCy8qFM90aXuw/LcID2+WjFLwvvWbGerPURyJyjEyCnK3ixFy/ Do13VsjbvElLJGwo7ZcfqU5hCkgLv5wNre6FAQTLkCmV3Dvv3+SizxSjn 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AKBQCntudU/49dJa1bgwbKKQKBG0MBAQEBAQF8hBABAQQ6PxALDhMlDwVJLogU1BIBAQEBAQEBAQEBAQEBAQEBAQEBAQEXiw+EbgeEKwEEikeOSQGTMSKCAhyBcR2CdAEBAQ
X-IronPort-AV: E=Sophos;i="5.09,617,1418083200"; d="scan'208";a="397963138"
Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by rcdn-iport-4.cisco.com with ESMTP; 20 Feb 2015 22:39:26 +0000
Received: from mcast-linux1.cisco.com (mcast-linux1.cisco.com [172.27.244.121]) by rcdn-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id t1KMdP1c021934 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 20 Feb 2015 22:39:25 GMT
Received: from mcast-linux1.cisco.com (localhost.cisco.com [127.0.0.1]) by mcast-linux1.cisco.com (8.13.8/8.13.8) with ESMTP id t1KMdOIe017112; Fri, 20 Feb 2015 14:39:24 -0800
Received: (from eckert@localhost) by mcast-linux1.cisco.com (8.13.8/8.13.8/Submit) id t1KMdOCc017111; Fri, 20 Feb 2015 14:39:24 -0800
Date: Fri, 20 Feb 2015 14:39:24 -0800
From: Toerless Eckert <eckert@cisco.com>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Message-ID: <20150220223924.GG8096@cisco.com>
References: <alpine.DEB.2.02.1502191920560.4007@uplift.swm.pp.se> <CAPRuP3mpNJTu6mP+RAVKKO0kt60PogNtNbCUCRRqxe9im3EzjA@mail.gmail.com> <alpine.DEB.2.02.1502201042330.4007@uplift.swm.pp.se> <7A86BDC6-FF4B-49FF-B59C-BA1DEF463173@inf-net.nl> <alpine.DEB.2.02.1502201310050.4007@uplift.swm.pp.se> <09793905-8D12-49E0-A040-490F617C87FF@inf-net.nl> <alpine.DEB.2.02.1502201410510.4007@uplift.swm.pp.se> <21FCAC07-1361-4051-B728-38AFB0656009@iki.fi> <alpine.DEB.2.02.1502201915420.4007@uplift.swm.pp.se> <8761awcu8t.wl-jch@pps.univ-paris-diderot.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <8761awcu8t.wl-jch@pps.univ-paris-diderot.fr>
User-Agent: Mutt/1.4.2.2i
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/jakO-FxuMspMbiFhC2bmj8wNMDM>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] Client roaming [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 22:40:27 -0000

I was going to say host-routes as well but Markus beat me to the punch.

I definitely think we should target a solution without host changes though
as the tactical solution.

I thought LISP had implemented this type of stuff, eg: host address 
mobility for hosts on access-LANs. Can't quite remember how, but it must
be something involving the tracking of a device when it moves from it's
original location, and the first-hop router(s) would then create a host-route
for that host and make sure that the host keeps its address (acting as
DHCP server or the like ?)

Can't be that hard though. Definitely less work than trying to build
an L2 overlay to give stupid L2 APs the ability to do L2 roaming. IN
any case, it should at most be all control-plane, no new forwarding plane.

Of course, host-routes themselves don't solve the possible problem of
link-local multicast after mobility, but i'd very much hope that we
can get rid of apps relying on that anyhow.

Cheers
    Toerless


From nobody Fri Feb 20 14:42:41 2015
Return-Path: <eckert@cisco.com>
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 B31171A0354 for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 14:42:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 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_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 FUhDgixFpPzw for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 14:42:39 -0800 (PST)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 61A161A034C for <homenet@ietf.org>; Fri, 20 Feb 2015 14:42:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=400; q=dns/txt; s=iport; t=1424472148; x=1425681748; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=sIUMI2a7oQrTXiTnyDP6tycuYqsoMflQLqtG2EgU9yE=; b=b/qeFvUQLI9Q71/7xWD8vPF56iFOc7/asXXn2/48aCd3hHPhJuk45IBf 8NWdHdL2ZMZlYOVjLXEZdSWQdaqRicj5v1tZ6lG7ZJtyFTbzY1jbvVT7K v6jenRCEPKXR1tskUgEfE/0BuNUkRRPWuXP/aFT446wnQlET9eIYZckh+ 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AKBQDgtudU/4YNJK1bgwbKKQKBG0MBAQEBAQF8hBABAQQ6PxALDgoJJQ8FSYhC1BIBAQEBAQEBAQEBAQEBAQEBAQEBAQEXiw+EbgeEKwEEikeOSQGTMSKEDx2CdAEBAQ
X-IronPort-AV: E=Sophos;i="5.09,617,1418083200"; d="scan'208";a="125553058"
Received: from alln-core-12.cisco.com ([173.36.13.134]) by alln-iport-2.cisco.com with ESMTP; 20 Feb 2015 22:42:27 +0000
Received: from mcast-linux1.cisco.com (mcast-linux1.cisco.com [172.27.244.121]) by alln-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id t1KMgQrH021229 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 20 Feb 2015 22:42:26 GMT
Received: from mcast-linux1.cisco.com (localhost.cisco.com [127.0.0.1]) by mcast-linux1.cisco.com (8.13.8/8.13.8) with ESMTP id t1KMgPY0017297; Fri, 20 Feb 2015 14:42:25 -0800
Received: (from eckert@localhost) by mcast-linux1.cisco.com (8.13.8/8.13.8/Submit) id t1KMgPkk017296; Fri, 20 Feb 2015 14:42:25 -0800
Date: Fri, 20 Feb 2015 14:42:25 -0800
From: Toerless Eckert <eckert@cisco.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Message-ID: <20150220224225.GH8096@cisco.com>
References: <8B98F698-983D-4D2A-B5D1-7ACED27C275E@fugue.com> <alpine.DEB.2.02.1502191920560.4007@uplift.swm.pp.se> <CAPRuP3mpNJTu6mP+RAVKKO0kt60PogNtNbCUCRRqxe9im3EzjA@mail.gmail.com> <alpine.DEB.2.02.1502201042330.4007@uplift.swm.pp.se> <7A86BDC6-FF4B-49FF-B59C-BA1DEF463173@inf-net.nl> <alpine.DEB.2.02.1502201310050.4007@uplift.swm.pp.se> <09793905-8D12-49E0-A040-490F617C87FF@inf-net.nl> <alpine.DEB.2.02.1502201410510.4007@uplift.swm.pp.se> <82E892D5-98C3-4DD8-9E78-A754D77A5AF6@employees.org> <alpine.DEB.2.02.1502201455500.4007@uplift.swm.pp.se>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.DEB.2.02.1502201455500.4007@uplift.swm.pp.se>
User-Agent: Mutt/1.4.2.2i
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/qU7GEfjkMWJwrHaq6SdhHEqdRLs>
Cc: Ole Troan <otroan@employees.org>, "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 20 Feb 2015 22:42:40 -0000

On Fri, Feb 20, 2015 at 02:57:21PM +0100, Mikael Abrahamsson wrote:
> >L3 - route injection (got a routing protocol there already, use it)
> 
> This sounds like it needs at least a coordination protocol between the APs?

NO, just between the first-hop (homenet) routers. Should work with unchanged
of the shelf crap-APs as long as they're attached to a homenet router.

Cheers
    Toerless


From nobody Fri Feb 20 21:57:51 2015
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 F35EC1A1B37 for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 21:57:49 -0800 (PST)
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 HWGb0s05HDfs for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 21:57:47 -0800 (PST)
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 627F61A1B28 for <homenet@ietf.org>; Fri, 20 Feb 2015 21:57:47 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 649C0A2; Sat, 21 Feb 2015 06:57:44 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1424498264; bh=DCSF9QQCC+ppdc3tTG09H/ONGMlaPRPI1LDOSFHxJQA=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=BLOfBVtt1/EA7iP1tk/1Gw1JfA3W/W7+6KGYDe1q0B11LR4CUT+2BLgyxneJXCGer JKBznw5HpsVyOFUZiCi7txoeNddR/nG0ohcdk0Adx69/FFTWmX9ZvwjZzw61TuGNNu U6lvNWtWy6XYYgm65g+d7V9HuMDOqrRnmpgr2gX8=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 59C34A1; Sat, 21 Feb 2015 06:57:44 +0100 (CET)
Date: Sat, 21 Feb 2015 06:57:44 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Dave Taht <dave.taht@gmail.com>
In-Reply-To: <CAA93jw73oCbTRj9LFBPhqq1jj25ks=3-hqb4kV+iWn9wTj__4A@mail.gmail.com>
Message-ID: <alpine.DEB.2.02.1502210651110.4007@uplift.swm.pp.se>
References: <CAA93jw7eGxPBNX+5LqX+qTYfRxNDxQpKo1fecUa2XH3bAKgvQQ@mail.gmail.com> <BB621A07-282E-4814-9D56-3EFBF87814D0@iki.fi> <71C98A06-0B23-4916-BFF8-CCF663A3F0A0@fugue.com> <87zj88b9xf.wl-jch@pps.univ-paris-diderot.fr> <CAA93jw4ZF8=QFMGmb1uPB+xxcNHadSZCEMkTTuDfOHrABWg3Mg@mail.gmail.com> <CAA93jw73oCbTRj9LFBPhqq1jj25ks=3-hqb4kV+iWn9wTj__4A@mail.gmail.com>
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/y3FrQ6AK4DZ4-Fp5B7rZiklbUKE>
Cc: HOMENET <homenet@ietf.org>, Ted Lemon <mellon@fugue.com>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] OpenWRT hardware [was: A poll]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sat, 21 Feb 2015 05:57:50 -0000

On Fri, 20 Feb 2015, Dave Taht wrote:

> 802.11ac rates on the wifi,  it does not have enough
> cpu to push it that hard. It was only getting wndr3800 style
> forwarding rates when I last tried on on ethernet also.

Which for me was around 100-120 megabit/s with a single session, which is 
definitely not enough for me with my 250/50 megabit/s Internet connection. 
Currently I use the Apple Airport Time Capsule 802.11ac thingie and a HE 
tunnel.

We're going to evaluate a product based on 
http://www.marvell.com/embedded-processors/armada-38x/ which looks very 
promising from a performance point of view.

I'll report back if we successfully get OpenWRT running on it and if I can 
find hardware based on it that can be bought retail if it seems to work 
well.

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


From nobody Fri Feb 20 22:07:39 2015
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 A61451A1B37 for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 22:07:37 -0800 (PST)
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 jy7Oq7AosWTb for <homenet@ietfa.amsl.com>; Fri, 20 Feb 2015 22:07:36 -0800 (PST)
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 9F46E1A1B5F for <homenet@ietf.org>; Fri, 20 Feb 2015 22:02:45 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 2FF2AA2; Sat, 21 Feb 2015 07:02:44 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1424498564; bh=/502PcKQboxtOF0t8zBYi/Jq3+Dyuyq+3hgiewdLn/o=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=3HE4KZ6/yNYbJxo0tT1RxHi7FZBS5u7ME8EC6CEa2riTiAVBU+BtVpFaAZckuI3CE QT252S4AN89CDWTLNam2CuMltEU/cqUC1GD5uieKw1qQ9jqwFzCuBGg+XmvC9TJpFy SZY831zTGQ8AzluVScCt0lOqbjsaxJvdTd71C0bM=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 2323FA1; Sat, 21 Feb 2015 07:02:44 +0100 (CET)
Date: Sat, 21 Feb 2015 07:02:44 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Toerless Eckert <eckert@cisco.com>
In-Reply-To: <20150220224225.GH8096@cisco.com>
Message-ID: <alpine.DEB.2.02.1502210658230.4007@uplift.swm.pp.se>
References: <8B98F698-983D-4D2A-B5D1-7ACED27C275E@fugue.com> <alpine.DEB.2.02.1502191920560.4007@uplift.swm.pp.se> <CAPRuP3mpNJTu6mP+RAVKKO0kt60PogNtNbCUCRRqxe9im3EzjA@mail.gmail.com> <alpine.DEB.2.02.1502201042330.4007@uplift.swm.pp.se> <7A86BDC6-FF4B-49FF-B59C-BA1DEF463173@inf-net.nl> <alpine.DEB.2.02.1502201310050.4007@uplift.swm.pp.se> <09793905-8D12-49E0-A040-490F617C87FF@inf-net.nl> <alpine.DEB.2.02.1502201410510.4007@uplift.swm.pp.se> <82E892D5-98C3-4DD8-9E78-A754D77A5AF6@employees.org> <alpine.DEB.2.02.1502201455500.4007@uplift.swm.pp.se> <20150220224225.GH8096@cisco.com>
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/KCo1cGjRIrcI2dUVhbTCtmpirJA>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sat, 21 Feb 2015 06:07:37 -0000

On Fri, 20 Feb 2015, Toerless Eckert wrote:

> On Fri, Feb 20, 2015 at 02:57:21PM +0100, Mikael Abrahamsson wrote:
>>> L3 - route injection (got a routing protocol there already, use it)
>>
>> This sounds like it needs at least a coordination protocol between the APs?
>
> NO, just between the first-hop (homenet) routers. Should work with unchanged
> of the shelf crap-APs as long as they're attached to a homenet router.

Could someone please explain to me how this is supposed to work? How do 
the first-hop routers figure out where the client is? Do we do /128 route 
injection into the homenet for active IPv6 addresses in that /64, and 
announce the same /64 everywhere, and then we use proxy-nd for all off-L2 
active IPs? I guess we need to handle IPv4 as well, so we use proxy-arp 
for that?

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


From nobody Sat Feb 21 06:41:55 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 5C56A1A6FFC for <homenet@ietfa.amsl.com>; Sat, 21 Feb 2015 06:41:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35] autolearn=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 ICcTVjichW0u for <homenet@ietfa.amsl.com>; Sat, 21 Feb 2015 06:41:52 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 467741A7005 for <homenet@ietf.org>; Sat, 21 Feb 2015 06:41:51 -0800 (PST)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t1LEfoN2005453; Sat, 21 Feb 2015 15:41:50 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 726F62C1D4A; Sat, 21 Feb 2015 15:41:50 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id nvSPLc8IOtx0; Sat, 21 Feb 2015 15:41:48 +0100 (CET)
Received: from pirx.pps.jussieu.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id E74BE2C1D3B; Sat, 21 Feb 2015 15:41:47 +0100 (CET)
Date: Sat, 21 Feb 2015 15:41:47 +0100
Message-ID: <871tljjphw.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Mikael Abrahamsson <swmike@swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1502210658230.4007@uplift.swm.pp.se>
References: <8B98F698-983D-4D2A-B5D1-7ACED27C275E@fugue.com> <alpine.DEB.2.02.1502191920560.4007@uplift.swm.pp.se> <CAPRuP3mpNJTu6mP+RAVKKO0kt60PogNtNbCUCRRqxe9im3EzjA@mail.gmail.com> <alpine.DEB.2.02.1502201042330.4007@uplift.swm.pp.se> <7A86BDC6-FF4B-49FF-B59C-BA1DEF463173@inf-net.nl> <alpine.DEB.2.02.1502201310050.4007@uplift.swm.pp.se> <09793905-8D12-49E0-A040-490F617C87FF@inf-net.nl> <alpine.DEB.2.02.1502201410510.4007@uplift.swm.pp.se> <82E892D5-98C3-4DD8-9E78-A754D77A5AF6@employees.org> <alpine.DEB.2.02.1502201455500.4007@uplift.swm.pp.se> <20150220224225.GH8096@cisco.com> <alpine.DEB.2.02.1502210658230.4007@uplift.swm.pp.se>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Sat, 21 Feb 2015 15:41:50 +0100 (CET)
X-Miltered: at korolev with ID 54E8992E.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54E8992E.001 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54E8992E.001 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/CIf-9FfMs0OJK54DpO4urLzjC9I>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: [homenet] Roaming hosts [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sat, 21 Feb 2015 14:41:54 -0000

>>>> L3 - route injection (got a routing protocol there already, use it)
>>>
>>> This sounds like it needs at least a coordination protocol between the APs?
>>
>> NO, just between the first-hop (homenet) routers. Should work with unchanged
>> of the shelf crap-APs as long as they're attached to a homenet router.

> Could someone please explain to me how this is supposed to work?

The client is running a stub implementation of the routing protocol.  It's
performing the normal routing protocol activities, such as sending
periodic hellos and announcing routes or flooding LSPs.

At any given time, the client has a default route through some
neighbouring Homenet router.  It sends its outgoing traffic through that
router, which presumably knows how to deal with it.

At any given time, the client is announcing a /128 route to itself to all
neighbouring Homenet routers.  This route gets propagated through the
Homenet by the routing protocol, so that all Homenet routers know how to
route to the client.  This assumes that the Homenet is not doing uRPF
internally.

This approach has been extensively tested with Babel, with no link-layer
support, and the outage after roaming has been measured as 2 to 4 Hello
intervals, which is the time needed by the link quality estimator to yield
meaningful data.  (Which, just between the two of us, is pretty annoying,
even if you're using Mosh.)

-- Juliusz


From nobody Sat Feb 21 06:45:49 2015
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 695531A7001 for <homenet@ietfa.amsl.com>; Sat, 21 Feb 2015 06:45:48 -0800 (PST)
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 1mBnEDs3CAgI for <homenet@ietfa.amsl.com>; Sat, 21 Feb 2015 06:45:46 -0800 (PST)
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 4E2981A6FFC for <homenet@ietf.org>; Sat, 21 Feb 2015 06:45:46 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id AB9F6A2; Sat, 21 Feb 2015 15:45:34 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1424529934; bh=bLfUQZvhfePVkOk2inaXRxqqP3F/A54K2QE7JOnGwDE=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=ihuwOD3mQo8VohmkTRhLk2E/+gg8TNacrTOlBIwc6ypApFUP2VbKB3hPxQX82P2Y0 JqcDfXsozGVrcCc3BejE5vPS90je1SGKuUk3K72uMjagUjaaxPn7EGXbMEv3Etcy7U fVgmO9ya87h+vhxQm6G8n94ZN+33S6Y5r0n5kego=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id A3312A1; Sat, 21 Feb 2015 15:45:34 +0100 (CET)
Date: Sat, 21 Feb 2015 15:45:34 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
In-Reply-To: <871tljjphw.wl-jch@pps.univ-paris-diderot.fr>
Message-ID: <alpine.DEB.2.02.1502211544510.4007@uplift.swm.pp.se>
References: <8B98F698-983D-4D2A-B5D1-7ACED27C275E@fugue.com> <alpine.DEB.2.02.1502191920560.4007@uplift.swm.pp.se> <CAPRuP3mpNJTu6mP+RAVKKO0kt60PogNtNbCUCRRqxe9im3EzjA@mail.gmail.com> <alpine.DEB.2.02.1502201042330.4007@uplift.swm.pp.se> <7A86BDC6-FF4B-49FF-B59C-BA1DEF463173@inf-net.nl> <alpine.DEB.2.02.1502201310050.4007@uplift.swm.pp.se> <09793905-8D12-49E0-A040-490F617C87FF@inf-net.nl> <alpine.DEB.2.02.1502201410510.4007@uplift.swm.pp.se> <82E892D5-98C3-4DD8-9E78-A754D77A5AF6@employees.org> <alpine.DEB.2.02.1502201455500.4007@uplift.swm.pp.se> <20150220224225.GH8096@cisco.com> <alpine.DEB.2.02.1502210658230.4007@uplift.swm.pp.se> <871tljjphw.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/gr7T7YOTZqTVbXqdsQOcdEuUHQw>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Roaming hosts [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sat, 21 Feb 2015 14:45:48 -0000

On Sat, 21 Feb 2015, Juliusz Chroboczek wrote:

> The client is running a stub implementation of the routing protocol.

I thought we already had decided we didn't require changes to the host?

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


From nobody Sat Feb 21 07:06:46 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 162101A7016 for <homenet@ietfa.amsl.com>; Sat, 21 Feb 2015 07:06:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35] autolearn=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 YCkEwXXR93Dc for <homenet@ietfa.amsl.com>; Sat, 21 Feb 2015 07:06:44 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 E0FC21A7012 for <homenet@ietf.org>; Sat, 21 Feb 2015 07:06:43 -0800 (PST)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t1LF6gra010444; Sat, 21 Feb 2015 16:06:42 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 7F6E42C1D4A; Sat, 21 Feb 2015 16:06:42 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id MLwqz1-JxH_p; Sat, 21 Feb 2015 16:06:41 +0100 (CET)
Received: from pirx.pps.jussieu.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 04F1C2C1D3B; Sat, 21 Feb 2015 16:06:40 +0100 (CET)
Date: Sat, 21 Feb 2015 16:06:40 +0100
Message-ID: <87wq3bi9rz.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Mikael Abrahamsson <swmike@swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1502211544510.4007@uplift.swm.pp.se>
References: <8B98F698-983D-4D2A-B5D1-7ACED27C275E@fugue.com> <alpine.DEB.2.02.1502191920560.4007@uplift.swm.pp.se> <CAPRuP3mpNJTu6mP+RAVKKO0kt60PogNtNbCUCRRqxe9im3EzjA@mail.gmail.com> <alpine.DEB.2.02.1502201042330.4007@uplift.swm.pp.se> <7A86BDC6-FF4B-49FF-B59C-BA1DEF463173@inf-net.nl> <alpine.DEB.2.02.1502201310050.4007@uplift.swm.pp.se> <09793905-8D12-49E0-A040-490F617C87FF@inf-net.nl> <alpine.DEB.2.02.1502201410510.4007@uplift.swm.pp.se> <82E892D5-98C3-4DD8-9E78-A754D77A5AF6@employees.org> <alpine.DEB.2.02.1502201455500.4007@uplift.swm.pp.se> <20150220224225.GH8096@cisco.com> <alpine.DEB.2.02.1502210658230.4007@uplift.swm.pp.se> <871tljjphw.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502211544510.4007@uplift.swm.pp.se>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Sat, 21 Feb 2015 16:06:42 +0100 (CET)
X-Miltered: at korolev with ID 54E89F02.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54E89F02.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54E89F02.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/XYTDnry6du7EVkebYS_1Qq1rxp8>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Roaming hosts [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sat, 21 Feb 2015 15:06:45 -0000

>> The client is running a stub implementation of the routing protocol.

> I thought we already had decided we didn't require changes to the host?

We don't *require* changes to the host.  We propose optional host
modifications that improve the user experience.

The chairs will correct me if I'm wrong, but I believe this is consistent
with Homenet's charter.

-- Juliusz


From nobody Sat Feb 21 09:31:31 2015
Return-Path: <eckert@cisco.com>
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 87D4F1A8035 for <homenet@ietfa.amsl.com>; Sat, 21 Feb 2015 09:31:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -13.025
X-Spam-Level: 
X-Spam-Status: No, score=-13.025 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FAKE_REPLY_C=1.486, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 n_FKdTzY8r8l for <homenet@ietfa.amsl.com>; Sat, 21 Feb 2015 09:31:29 -0800 (PST)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D746B1A8032 for <homenet@ietf.org>; Sat, 21 Feb 2015 09:31:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3407; q=dns/txt; s=iport; t=1424539888; x=1425749488; h=date:from:to:subject:message-id:mime-version; bh=xePGuaFN5g30JOg1TlTbEFiEY2IMhUdgPl9sWYf/vIY=; b=BQaCxju0VXdq1WhzGIN7hbjJo0cAHEurByFOKiK/1yKqg6iXJANhuf2K 8hE5/6HZB3HC+fkpm1y/zzn3n2a8HEJjvhNA+iuXgU/E4npNZgZHWf4uO ByoIC+a/iID05ltZKF2cceO4eHxoBJX6NiDAk9Q2Xf9yUXi9BRYMsICBe k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AsBQC5v+hU/40NJK1agwbLR0MBAQEBAQF8hA8BAQEDO0QWGAk0BUkBLYgMCNMKAQEBAQEFAQEBAQEBAQEaixOEAx2FAAWKSo5KAYEbjlqDPiKCAgUXgXEdgnQBAQE
X-IronPort-AV: E=Sophos;i="5.09,621,1418083200"; d="scan'208";a="125711347"
Received: from alln-core-8.cisco.com ([173.36.13.141]) by alln-iport-4.cisco.com with ESMTP; 21 Feb 2015 17:31:27 +0000
Received: from mcast-linux1.cisco.com (mcast-linux1.cisco.com [172.27.244.121]) by alln-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id t1LHVQaf004173 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 21 Feb 2015 17:31:27 GMT
Received: from mcast-linux1.cisco.com (localhost.cisco.com [127.0.0.1]) by mcast-linux1.cisco.com (8.13.8/8.13.8) with ESMTP id t1LHVQ16006334; Sat, 21 Feb 2015 09:31:26 -0800
Received: (from eckert@localhost) by mcast-linux1.cisco.com (8.13.8/8.13.8/Submit) id t1LHVQ53006333; Sat, 21 Feb 2015 09:31:26 -0800
Date: Sat, 21 Feb 2015 09:31:26 -0800
From: Toerless Eckert <eckert@cisco.com>
To: Dave Taht <dave.taht@gmail.com>, homenet@ietf.org
Message-ID: <20150221173126.GQ26102@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.2.2i
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/wdAiZb931-xjJBot6NNyyRv6ddo>
Subject: Re: [homenet] A poll
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sat, 21 Feb 2015 17:31:30 -0000

On Fri, Feb 20, 2015 at 08:50:10AM -0800, Dave Taht wrote:
> 0) Have you managed to get ipv6 working at all? If so, how? What sort
> of problems did you encounter?

Yes.

How ? Through configuration ? Don't understand the question.

Problems:

a) IPv6 incapable clients:

2 IP printers
1 printer-adapter for non-IP printer
1 surveillance camera 
2 SIP phones with 10 handsets 
1 SIP adapter (for FAX)
2 wireless SCCP phones
4 IPv6 capable wired SIP phones without IPv6 capable provider
1 PVR
1 Place shifter
1 Terminal Server
6 squeezeboxes
5 remote power switches
1 MacOS 7 system
1 AV receiver
2 Panasonic Smart-TV sets
1 thin client (server side not enabled for IPv6)
1 toaster (ok, just kidding)

thats about 70% of my clients, the IPv6 capable rest are all linux servers,
windows/mac/android clients and RPI as tv clients, but only partial use
of IPv6 primarily due to naming/routing issues:

Outside IPv6 connectibity challenge:

1 VPN provider with IPv6 stability issues
2 ISPs where i haven't found time to walk though their IPv6 registration procedures yet.

Host stack problems:

"IPv6 preferred over IPv4" makes it hard to decide enabling IPv6 at all when
you have challenged IPv6 internet connectivity. Otherwise i'd have enabled a lot
more IPv6 for just in-home IPv6 on IPv6 capable system.s

Naming: Lacking ease-of-use for automatic DNS name registration for clients.
(at least i haven't figured out how to set something up that automates this).

> 1) Have you attempted to deploy a routing protocol in your home? Which
> one, and why?

No. Can't change addressing for VPN segments anyhow, and for
non-VPN segments, additional in-home routing just makes a lot of
the IPv4-only client/server solutions a pain because they just have link
local service discovery. Short term the use-case priority for inter-home routing
is higher than in-home routing for me.

> 2) Have you attempted to get hnetd's prefix distribution system
> working? (it supports linux mainline and openwrt presently)

No. on my list though.

> 3) Do you use ethernet? How many clients in your home are ethernet connected?

Yes. about 25 clients.

> 4) Do you use wifi? How many clients are wifi connected? Do you use
> range extenders?

Yes. About 15 clients.

I try to stay as far away from range extenders as i can.
Had enough trouble trying to help friends set them up as good as possible.

> 5) How many devices do you think you will have connected to the
> network in your home in 5 years? How many now?

Now - maybe 55 ?

5 years: 60 ? Could double if i would decide on an IP connected
home control technology - none deployed yet.

> 6) Do you use any other network connected technologies (homeplug,
> 802.14, LTE, etc). If so, which ones, and why?

Homeplug.
3G Phone with tethering as backup (non IPv6 capable AFAIK)

> 7) Do you use mdns service discovery?

No. But top of my todo list.

> 8) Why are you here? (especially, if your answers to 0-2, are "no")

The above is all just IPv6 in my production home networks, not
stuff in labs i work on. Up to now IPv6 in that home network was mostly hobby,
so i could not invest a lot of time into it. Pretty much just starting to
plan deploying the actual IETF homenet specific software now (eg: just ordered
router for openwrt this week only).

Cheers
    Toerless


From nobody Sat Feb 21 09:50:05 2015
Return-Path: <eckert@cisco.com>
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 7FE2D1A8035 for <homenet@ietfa.amsl.com>; Sat, 21 Feb 2015 09:50:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 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_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 g-MJBS86bZLZ for <homenet@ietfa.amsl.com>; Sat, 21 Feb 2015 09:50:01 -0800 (PST)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2E3841A1B39 for <homenet@ietf.org>; Sat, 21 Feb 2015 09:49:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1858; q=dns/txt; s=iport; t=1424540998; x=1425750598; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=RvkNBxmpkBU8pAOERK26NH6Ma+OlnOr1lnP0dNZeCqI=; b=B39ymWBjgq6g5gtVC8gRbmFXx/VDr1F6iHuCjxo8L9aHqN/KIZsJiQIA AQmRpeKJJ3bgAJNf8KuDmVIEM5wi3hvBiSEPwnL1XLYVT8rs2mVBhJnnN 4Sqrjk3oK4Fj2TzsuDvNIHIsL3MsP3QO+L+yLbS8jtihCvZwC/QplhGAQ w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BIBQAexehU/51dJa1agwZSWsFPgUaFcQKBGTgUAQEBAQEBAXyEDwEBAQMBJxM/BQsLDgoJJQ8FSROIJwgN0n8BAQEBAQEBAQEBAQEBAQEBAQEBAQETBIsThAwRAVAHhCsFikqIZoVkAYEbgxWPAyOEDx0xgQuBOAEBAQ
X-IronPort-AV: E=Sophos;i="5.09,621,1418083200"; d="scan'208";a="125637882"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by alln-iport-8.cisco.com with ESMTP; 21 Feb 2015 17:49:41 +0000
Received: from mcast-linux1.cisco.com (mcast-linux1.cisco.com [172.27.244.121]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id t1LHnfmA019498 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 21 Feb 2015 17:49:41 GMT
Received: from mcast-linux1.cisco.com (localhost.cisco.com [127.0.0.1]) by mcast-linux1.cisco.com (8.13.8/8.13.8) with ESMTP id t1LHneFf016240; Sat, 21 Feb 2015 09:49:40 -0800
Received: (from eckert@localhost) by mcast-linux1.cisco.com (8.13.8/8.13.8/Submit) id t1LHnduX016238; Sat, 21 Feb 2015 09:49:39 -0800
Date: Sat, 21 Feb 2015 09:49:39 -0800
From: Toerless Eckert <eckert@cisco.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Message-ID: <20150221174939.GJ8096@cisco.com>
References: <CAPRuP3mpNJTu6mP+RAVKKO0kt60PogNtNbCUCRRqxe9im3EzjA@mail.gmail.com> <alpine.DEB.2.02.1502201042330.4007@uplift.swm.pp.se> <7A86BDC6-FF4B-49FF-B59C-BA1DEF463173@inf-net.nl> <alpine.DEB.2.02.1502201310050.4007@uplift.swm.pp.se> <09793905-8D12-49E0-A040-490F617C87FF@inf-net.nl> <alpine.DEB.2.02.1502201410510.4007@uplift.swm.pp.se> <82E892D5-98C3-4DD8-9E78-A754D77A5AF6@employees.org> <alpine.DEB.2.02.1502201455500.4007@uplift.swm.pp.se> <20150220224225.GH8096@cisco.com> <alpine.DEB.2.02.1502210658230.4007@uplift.swm.pp.se>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.DEB.2.02.1502210658230.4007@uplift.swm.pp.se>
User-Agent: Mutt/1.4.2.2i
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/UfVxYxAyzUhloh2Oww8TWaGHKTE>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sat, 21 Feb 2015 17:50:03 -0000

On Sat, Feb 21, 2015 at 07:02:44AM +0100, Mikael Abrahamsson wrote:
> >NO, just between the first-hop (homenet) routers. Should work with 
> >unchanged
> >of the shelf crap-APs as long as they're attached to a homenet router.
> 
> Could someone please explain to me how this is supposed to work? How do 
> the first-hop routers figure out where the client is? Do we do /128 route 
> injection into the homenet for active IPv6 addresses in that /64, and 
> announce the same /64 everywhere, and then we use proxy-nd for all off-L2 
> active IPs? I guess we need to handle IPv4 as well, so we use proxy-arp 
> for that?

I was referring to eg:
https://tools.ietf.org/html/draft-hertoghs-lisp-mobility-use-cases-01
and available commercial implementations, eg: from cisco for this
(google lisp host mobility and try to ignore all the lisp details ;-)).

I haven't tried to figure out all details and whether/how we would
want to adopt a similar scheme to homenet. Something like:

 ->  a first-hop-router would need to be able to detect presence of
     a roaming client. Probably based on MAC-address. And then generate
     the /128 (and /32) prefix for the clients address.
     Thats effectivly what LISP does, but they do not need to only
     create a route but feed into their database.
 
 ->  for seamless mobility, you'd need to have on all subnets for the
     default-router the same virtual MAC address (eg: VRRP).
     Thats also someting set up with LISP. This ensures that traffic
     sent by the client will continue to be forwarded after roamin.
 
 ->  What i couldn't figure out quickly yet is how DHCP updates to the
     client are dealt with especially default-router IP address.


Cheers
     Toerless
 
> Mikael Abrahamsson    email: swmike@swm.pp.se

-- 
---
Toerless Eckert, eckert@cisco.com


From nobody Sat Feb 21 10:07:29 2015
Return-Path: <eckert@cisco.com>
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 533AD1A1B9C for <homenet@ietfa.amsl.com>; Sat, 21 Feb 2015 10:07:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 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_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 9tUWZZ2NNo9Q for <homenet@ietfa.amsl.com>; Sat, 21 Feb 2015 10:07:26 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 486E81A1B92 for <homenet@ietf.org>; Sat, 21 Feb 2015 10:07:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3666; q=dns/txt; s=iport; t=1424542046; x=1425751646; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=qGrSOGpyBN7w9451WVHin09RpqeP9PvfwaNmfE45sEw=; b=FuyY2JvzHEfUqpne5W6B2kVDgn/6+AJoRJR8IADwmxtzfIpRqOr5gRfL ttcBu9VRS/mZ100Nm7nALmiKUDo9FHYNeZbHRC4oLDMY6xblFwtFhnVSx LMx3yJBvi+Xu7T2msQ9rgu60BlBsqAY+CUGnzfy7Of8Yl/0d09EJcYAmX c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BMBQClyOhU/5ldJa1agwZSWsMGCoUnSgKBGUMBAQEBAQF8hBABAQQBAQE3NAsQCw4KCSUPBRM2E4gvDdJ8AQEBAQEBAQEBAQEBAQEBAQEBAQEBEwSLE4RuB4QrBYpKjkoBgRuDFYtFgz4iggIcgXEdMYJDAQEB
X-IronPort-AV: E=Sophos;i="5.09,621,1418083200"; d="scan'208";a="398382612"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-2.cisco.com with ESMTP; 21 Feb 2015 18:07:25 +0000
Received: from mcast-linux1.cisco.com (mcast-linux1.cisco.com [172.27.244.121]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id t1LI7K1s010691 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 21 Feb 2015 18:07:20 GMT
Received: from mcast-linux1.cisco.com (localhost.cisco.com [127.0.0.1]) by mcast-linux1.cisco.com (8.13.8/8.13.8) with ESMTP id t1LI7Jxi026235; Sat, 21 Feb 2015 10:07:19 -0800
Received: (from eckert@localhost) by mcast-linux1.cisco.com (8.13.8/8.13.8/Submit) id t1LI7I3h026234; Sat, 21 Feb 2015 10:07:18 -0800
Date: Sat, 21 Feb 2015 10:07:18 -0800
From: Toerless Eckert <eckert@cisco.com>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Message-ID: <20150221180718.GK8096@cisco.com>
References: <alpine.DEB.2.02.1502201042330.4007@uplift.swm.pp.se> <7A86BDC6-FF4B-49FF-B59C-BA1DEF463173@inf-net.nl> <alpine.DEB.2.02.1502201310050.4007@uplift.swm.pp.se> <09793905-8D12-49E0-A040-490F617C87FF@inf-net.nl> <alpine.DEB.2.02.1502201410510.4007@uplift.swm.pp.se> <82E892D5-98C3-4DD8-9E78-A754D77A5AF6@employees.org> <alpine.DEB.2.02.1502201455500.4007@uplift.swm.pp.se> <20150220224225.GH8096@cisco.com> <alpine.DEB.2.02.1502210658230.4007@uplift.swm.pp.se> <871tljjphw.wl-jch@pps.univ-paris-diderot.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <871tljjphw.wl-jch@pps.univ-paris-diderot.fr>
User-Agent: Mutt/1.4.2.2i
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/hAeyUPxnb25fGwrPaPwlBMNPnpE>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] Roaming hosts [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sat, 21 Feb 2015 18:07:28 -0000

I ran RIP on ca. 50 multi-homed clients in the early 90'th wth /32 route injection
for both addresses, which effectively was also used for what we'd call
mobility today. Worked very good. Trying to remember the
reconvergence time after link down... I think i had tuned down the
RIP hello interval. Not quite sure. Stable & slow 10 Mbps
ethernet + fast & flakey 100 Mbps FDDI or 155 Mbps ATM back then was the
use-case. It did keep TCP connections running over link failures.

I would be a big fan of trying to use homenet to bring in a lightweigt
version of something like this into standard OS host stacks. For
real mobility, multi-homing redundancy and to enable anycasting. But
then again, i have also been a fan hostroutes in ISO CLNS and have been
jealous of only L2 switches being privileged to have host-routes for decades now.

I probably would prefer not to use one of the real routing protocols, but
something lightweight. RIP is a stupid routing protocol but just to 
announce aliveness of host interfaces it is pretty ook. And by not using your
production routing protocol, any real router could easily distinguish
those announcement from real routing protocol neighbor updates and accordingly
apply different policies to them as needed.

Of course something defined specific for this purpose (host address aliveness
or the like) would be most clean IMHO. Wouldn't even bother about IPv4 anymore,
so could be done on one of the IPv6 specific signaling protocols we have (ND ?).

Having said this, the proliferation time of host stack improvements is so
slow that i'd certainly not wanted to bet on having this in any IPv6
capable embedded clients in the home i might buy in the next 10 years,
so the hacky way of the default-router proxying the creation of host routes
is likely the necessary stopgap sollution if we want to go this route.

Cheers
   toerless

On Sat, Feb 21, 2015 at 03:41:47PM +0100, Juliusz Chroboczek wrote:
> >>>> L3 - route injection (got a routing protocol there already, use it)
> >>>
> >>> This sounds like it needs at least a coordination protocol between the APs?
> >>
> >> NO, just between the first-hop (homenet) routers. Should work with unchanged
> >> of the shelf crap-APs as long as they're attached to a homenet router.
> 
> > Could someone please explain to me how this is supposed to work?
> 
> The client is running a stub implementation of the routing protocol.  It's
> performing the normal routing protocol activities, such as sending
> periodic hellos and announcing routes or flooding LSPs.
> 
> At any given time, the client has a default route through some
> neighbouring Homenet router.  It sends its outgoing traffic through that
> router, which presumably knows how to deal with it.
> 
> At any given time, the client is announcing a /128 route to itself to all
> neighbouring Homenet routers.  This route gets propagated through the
> Homenet by the routing protocol, so that all Homenet routers know how to
> route to the client.  This assumes that the Homenet is not doing uRPF
> internally.
> 
> This approach has been extensively tested with Babel, with no link-layer
> support, and the outage after roaming has been measured as 2 to 4 Hello
> intervals, which is the time needed by the link quality estimator to yield
> meaningful data.  (Which, just between the two of us, is pretty annoying,
> even if you're using Mosh.)
> 
> -- Juliusz
> 
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet

-- 
---
Toerless Eckert, eckert@cisco.com


From nobody Sat Feb 21 10:52:55 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 1332D1A1B51 for <homenet@ietfa.amsl.com>; Sat, 21 Feb 2015 10:52:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35] autolearn=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 Ku1YpYCMiKrk for <homenet@ietfa.amsl.com>; Sat, 21 Feb 2015 10:52:52 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 F11D81A020A for <homenet@ietf.org>; Sat, 21 Feb 2015 10:52:51 -0800 (PST)
Received: from potemkin.univ-paris7.fr (potemkin.univ-paris7.fr [IPv6:2001:660:3301:8000::1:1]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t1LIqlUm018255 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 21 Feb 2015 19:52:47 +0100
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by potemkin.univ-paris7.fr (8.14.4/8.14.4/relay2/56228) with ESMTP id t1LIqljV020981; Sat, 21 Feb 2015 19:52:47 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 20E732C1D6C; Sat, 21 Feb 2015 19:52:47 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id 4dgiuL7di2sU; Sat, 21 Feb 2015 19:52:45 +0100 (CET)
Received: from pirx.pps.jussieu.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 6451A2C1D67; Sat, 21 Feb 2015 19:52:45 +0100 (CET)
Date: Sat, 21 Feb 2015 19:52:44 +0100
Message-ID: <87y4nrgkqr.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Toerless Eckert <eckert@cisco.com>
In-Reply-To: <20150221180718.GK8096@cisco.com>
References: <alpine.DEB.2.02.1502201042330.4007@uplift.swm.pp.se> <7A86BDC6-FF4B-49FF-B59C-BA1DEF463173@inf-net.nl> <alpine.DEB.2.02.1502201310050.4007@uplift.swm.pp.se> <09793905-8D12-49E0-A040-490F617C87FF@inf-net.nl> <alpine.DEB.2.02.1502201410510.4007@uplift.swm.pp.se> <82E892D5-98C3-4DD8-9E78-A754D77A5AF6@employees.org> <alpine.DEB.2.02.1502201455500.4007@uplift.swm.pp.se> <20150220224225.GH8096@cisco.com> <alpine.DEB.2.02.1502210658230.4007@uplift.swm.pp.se> <871tljjphw.wl-jch@pps.univ-paris-diderot.fr> <20150221180718.GK8096@cisco.com>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]); Sat, 21 Feb 2015 19:52:47 +0100 (CET)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Sat, 21 Feb 2015 19:52:47 +0100 (CET)
X-Miltered: at korolev with ID 54E8D3FF.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 54E8D3FF.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54E8D3FF.000 from potemkin.univ-paris7.fr/potemkin.univ-paris7.fr/null/potemkin.univ-paris7.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Enveloppe: 54E8D3FF.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54E8D3FF.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 54E8D3FF.000 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/dQzxWn3V4ruQalNTfvBKgouEKec>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Roaming hosts [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sat, 21 Feb 2015 18:52:54 -0000

> I think i had tuned down the RIP hello interval.

Impossible.  It was the Update interval that you had tuned down.

> I probably would prefer not to use one of the real routing protocols, but
> something lightweight. RIP is a stupid routing protocol but just to
> announce aliveness of host interfaces it is pretty ook.

RIP(ng) has a major flaw: it doesn't have explicit Hellos.  Reachability
is established by receiving Update packets, which have a size that is
proportional to the number of advertised prefixes.

Modern routing protocols (at least IS-IS, OSPF, EIGRP and Babel) have an
explicit reachability sub-protocol, that consists of explicit Hello
exchanges.  This allows sending Hellos much more often than you send
Updates or topology information.  For example, in Babel a packet
containing just a single, unextended Hello has a payload of just 12 bytes,
independent of the size of the network.

(In principle, you could hack a Hello protocol into RIP by interpreting
empty RIP packets as reachability indications.  But that would no longer
be RIP, right?)

> Of course something defined specific for this purpose (host address
> aliveness or the like) would be most clean IMHO.

I believe that BFD (RFCs 5880 and 5881) is the IETF Standard Track
reachability detection protocol.

-- Juliusz


From nobody Sat Feb 21 11:13:05 2015
Return-Path: <eckert@cisco.com>
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 184F71A039F for <homenet@ietfa.amsl.com>; Sat, 21 Feb 2015 11:13:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 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_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 tx6FrP7HQsSQ for <homenet@ietfa.amsl.com>; Sat, 21 Feb 2015 11:13:02 -0800 (PST)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 63FA51A037D for <homenet@ietf.org>; Sat, 21 Feb 2015 11:13:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2744; q=dns/txt; s=iport; t=1424545982; x=1425755582; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=85uevvrPRoKIkBXRZF45pdUvnlLUltSwcLpEy3ULLCU=; b=XX05v8h6i8wCCvd7U+J36r8rlbS0M/cQEnxfzNS0T149/sRx/eIA8/V6 Tlxy/00mdcQ/IODDyrQnEAJMwBRfmNGvDgTydkwtoWlJhieB0uYysQP9W C5ojCt/PFhOsml6HwdrVOzxStvUtyqGceq5obdlRXfMm4B6uFqbnOuwCS o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BHBQCl1+hU/4oNJK1agwaBLMkBAoEZQwEBAQEBAXyEEAEBBDo/EAsOCgklDwVJE4gv0m0BAQEBAQEBAQEBAQEBAQEBAQEBAQEXihV+hCBOB4QrBYpKjkoBgRuLS4ZNIoF/H4FxHTGCQwEBAQ
X-IronPort-AV: E=Sophos;i="5.09,621,1418083200"; d="scan'208";a="125717682"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by alln-iport-2.cisco.com with ESMTP; 21 Feb 2015 19:13:01 +0000
Received: from mcast-linux1.cisco.com (mcast-linux1.cisco.com [172.27.244.121]) by alln-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id t1LJCuUe004507 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 21 Feb 2015 19:12:56 GMT
Received: from mcast-linux1.cisco.com (localhost.cisco.com [127.0.0.1]) by mcast-linux1.cisco.com (8.13.8/8.13.8) with ESMTP id t1LJCtAx030834; Sat, 21 Feb 2015 11:12:55 -0800
Received: (from eckert@localhost) by mcast-linux1.cisco.com (8.13.8/8.13.8/Submit) id t1LJCte1030833; Sat, 21 Feb 2015 11:12:55 -0800
Date: Sat, 21 Feb 2015 11:12:55 -0800
From: Toerless Eckert <eckert@cisco.com>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Message-ID: <20150221191255.GL8096@cisco.com>
References: <alpine.DEB.2.02.1502201310050.4007@uplift.swm.pp.se> <09793905-8D12-49E0-A040-490F617C87FF@inf-net.nl> <alpine.DEB.2.02.1502201410510.4007@uplift.swm.pp.se> <82E892D5-98C3-4DD8-9E78-A754D77A5AF6@employees.org> <alpine.DEB.2.02.1502201455500.4007@uplift.swm.pp.se> <20150220224225.GH8096@cisco.com> <alpine.DEB.2.02.1502210658230.4007@uplift.swm.pp.se> <871tljjphw.wl-jch@pps.univ-paris-diderot.fr> <20150221180718.GK8096@cisco.com> <87y4nrgkqr.wl-jch@pps.univ-paris-diderot.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <87y4nrgkqr.wl-jch@pps.univ-paris-diderot.fr>
User-Agent: Mutt/1.4.2.2i
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/azuswr11YCJFHYTKU6G33yTMbL4>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Roaming hosts [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sat, 21 Feb 2015 19:13:04 -0000

Of course you're right, but let me play devils advocate for a bit:

I am not sure how important it is to separate fast-hello from route
announcements for hosts. We may have <= 10 addresses on a host. Where would
be have a problem ? processing in the receiving router ? 

Something as simple as RIP also makes it very easy to embed it as
a library into apps, which is particularily good if you have an (anycast)
application specific address and you actually want to make sure the
address is only announced when the app is alive.

BFD takes modularily even one step further and if we used that, then
the benefit of hello/route advertisement separation in the routing 
protocols themselves becomes mood. But it adds even more code and
complexity.

Fast Hellos are good. Actually i'd love to have something thats even
better and can also double to recognize lousy links. Oops: marginal links.
But then there is all this talk about low power wifi clients as well and
that makes active probing supposedly prohibitive.

IMHO, the most important question is: 

Whats the option that could likely be proliferated into eg:
MacOS/Windows/Android ? Lets just say with <= 5 sec failover time.

Cheers
    toerless

On Sat, Feb 21, 2015 at 07:52:44PM +0100, Juliusz Chroboczek wrote:
> > I think i had tuned down the RIP hello interval.
> 
> Impossible.  It was the Update interval that you had tuned down.
> 
> > I probably would prefer not to use one of the real routing protocols, but
> > something lightweight. RIP is a stupid routing protocol but just to
> > announce aliveness of host interfaces it is pretty ook.
> 
> RIP(ng) has a major flaw: it doesn't have explicit Hellos.  Reachability
> is established by receiving Update packets, which have a size that is
> proportional to the number of advertised prefixes.
> 
> Modern routing protocols (at least IS-IS, OSPF, EIGRP and Babel) have an
> explicit reachability sub-protocol, that consists of explicit Hello
> exchanges.  This allows sending Hellos much more often than you send
> Updates or topology information.  For example, in Babel a packet
> containing just a single, unextended Hello has a payload of just 12 bytes,
> independent of the size of the network.
> 
> (In principle, you could hack a Hello protocol into RIP by interpreting
> empty RIP packets as reachability indications.  But that would no longer
> be RIP, right?)
> 
> > Of course something defined specific for this purpose (host address
> > aliveness or the like) would be most clean IMHO.
> 
> I believe that BFD (RFCs 5880 and 5881) is the IETF Standard Track
> reachability detection protocol.
> 
> -- Juliusz

-- 
---
Toerless Eckert, eckert@cisco.com


From nobody Sat Feb 21 11:23:47 2015
Return-Path: <dave.taht@gmail.com>
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 7207B1A1B65 for <homenet@ietfa.amsl.com>; Sat, 21 Feb 2015 11:23:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level: 
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[BAYES_05=-0.5,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, J_CHICKENPOX_31=0.6, SPF_PASS=-0.001] autolearn=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 be7jIzFzxRIu for <homenet@ietfa.amsl.com>; Sat, 21 Feb 2015 11:23:43 -0800 (PST)
Received: from mail-ob0-x233.google.com (mail-ob0-x233.google.com [IPv6:2607:f8b0:4003:c01::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4A7421A007A for <homenet@ietf.org>; Sat, 21 Feb 2015 11:23:43 -0800 (PST)
Received: by mail-ob0-f179.google.com with SMTP id wp4so30118291obc.10 for <homenet@ietf.org>; Sat, 21 Feb 2015 11:23:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=932k30OfcyTkgaDziFixcmRUtjIz53j7Biz3SEYIYRg=; b=JErzCQYHHtEpPtrYmENgADJ+mNiZsIhbQ5O3KputRyBYJJ4mXHY+qeicBjqO+tL5c3 dW4G0wqQ9mz9/ACvCxAw1H+4CigIZMxZC7UMz6ku8AtXHklyv1d3A/vBlmj3Vh5dYklJ kHqdnPUJJ/Nq7txQCkOLy7nsepo88E7OZIEG1jdiRJr33UCxR9qbIy8y52UbRmoQyoOA pZ3sY/i7E73ruhY0BfwS9LZa/sL0XNt3op+1cMK+SQgotvm/WnMoz6BiE6er2DNCLC00 PP34gCdwqlwTpNMMBrfIJkd00UrI2Fs2dqJTqtlPvYZ5X/NXZ+ikaZmdtT26JKuHRZR3 O+VA==
MIME-Version: 1.0
X-Received: by 10.60.145.212 with SMTP id sw20mr2471702oeb.39.1424546622363; Sat, 21 Feb 2015 11:23:42 -0800 (PST)
Received: by 10.202.51.66 with HTTP; Sat, 21 Feb 2015 11:23:42 -0800 (PST)
Date: Sat, 21 Feb 2015 11:23:42 -0800
Message-ID: <CAA93jw7tb6E3cisKLWEpf6xOceakvE8LXeX98k_F-b2THKX+vw@mail.gmail.com>
From: Dave Taht <dave.taht@gmail.com>
To: Markus Stenberg <markus.stenberg@iki.fi>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/BGBTSXgh1G9rcN7QSWfYqqg2ffQ>
Cc: Ted Lemon <mellon@fugue.com>, Ole Troan <otroan@employees.org>, Steven Barth <cyrus@openwrt.org>, Ralph Droms <rdroms.ietf@gmail.com>, "homenet@ietf.org Group" <homenet@ietf.org>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: [homenet] HNCPD usability issues
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sat, 21 Feb 2015 19:23:45 -0000

retitling this because I really, really, really, would like more
people using hncpd
and providing feedback on that, rather than arguing over specification
documents.

On Fri, Feb 20, 2015 at 2:14 PM, Markus Stenberg <markus.stenberg@iki.fi> w=
rote:
>> On 20.2.2015, at 22.01, Dave Taht <dave.taht@gmail.com> wrote:
>> On Fri, Feb 20, 2015 at 11:34 AM, Steven Barth <cyrus@openwrt.org> wrote=
:
>>>
>>> Am 19. Februar 2015 20:05:56 MEZ, schrieb Ted Lemon <mellon@fugue.com>:
>>>> Hm, I will have to try it out.   Is it in a distribution?
>>>
>>> ohybridproxy in openwrt. It's mainly useful with hnetd (hncp) though.
>>>
>>> Manual configuration without hncp is a bit awkward since you need to na=
me each link manually and on every router configure the resolver (e.g. dnsm=
asq). I guess we might want to provide a little example for 2 links at some=
 point.
>> I would like to deploy hncp in my upcoming make-wifi-fast testbed.
>> However the biggest headache is ensuring that all the routers
>> inbetween have hncp burned into them, and are only acting as relays as
>> I generally only obtain a few (/60) real IPv6 prefixes per GW and they
>> only need to be on the APs.
>>
>> GW1 - routerA - routerB - routerC - routerD - AP1
>>                                         |
>> GW2 - routerE - routerF - routerG - routerH - AP2
>>                           |
>>                         AP3
>>
>> GW3 ...
>>
>> (the actual topology of the testbed is way more complex than this
>> (covering ethernet, wifi, and moca) and I am not going into it here)
>>
>> 1) is there a way to configure hncpd as purely a relay, and NOT do any
>> address assignment at all on routers B,C,D,F,G,H?
>
> In theory (=3Dspec), but not in current implementation (I _think_).

Yes, the spec seemed right, but after playing with the code, got
stuck, so I thought I would ask. If you can point me at any specific
area of the code to try to make relaying work, I can dig into it; I am
about a month away from deployment. (and have other things I would
rather do than improve hnetd, like make-wifi-fast)

I think having hncp relaying support universally is needed, and for
devices that are homenet participating but not necessarily full blown
devices - should be configured as a "relay only" by default.

the local multicast proxying problem is partially why pim-sm and
related protocols did not deploy to a huge extent, IGMP notoriously
buggy, etc, etc. See for example, the sad, underused state of pimd.

> You do not really need non-linklocal addresses for HNCP, or routing proto=
col, so as long as there are no hosts on the link..

That to me, was a truly major point of both hncp and routing protocol.

I have seen plenty of people gripe elsewhere about assigning *any*
public ipv6 addresses to a home router, preferring that dnsmasq=C2=B4s
dhcpv6 server work without one, for example.

>(traceroute is a bitch though given just linklocals)

I don=C2=B4t care about traceroute.

>
> As workaround in current implementation, if you set it to assign e.g. /80=
 per link used for your intermediate links, you would have almost all of ad=
dress space left; however, in your case, I am not sure you can even afford =
to split one /64 for that purpose.

Nope, 22+ APs, most with 2 or more subnets, and a couple /60s to play
with. Have no idea with the topology above how IPv6 prefix exaustion
will be handled either.

But - more importantly - I am not interested in exposing intermediate
routers to the wild and wooly internet with public ipv6s. Got enough
firewalling problems as it is.

I realize that my use cases are a bit different than standard
homenet=C2=B4s, but I am very interested in exercising the protocol to a
fuller extent than it has before.

>> 2) have you tested that it is indeed possible to get the separate ipv6
>> prefixes from GW1,GW2,GW3 to AP1,AP2, AP3?
>
> Yes.
>
>> 3) Can ULA and "Real" address assignment be distinguished along the
>> way? I have no problem assigning ULAs to the routers, but dont want to
>> use up real addresses on them.
>
> In theory (=3Dspec), not in current implementation (ULA is actively disco=
uraged in current impl, I cannot remember if there was option to override).

What I had done with ahcpd was: it calls a script to configure every
received address,
filter out anything but ulas, and just configure those. Easy, couple
lines of code.

>
>> 4) What happens when someone pulls the plug on GW1, it reboots, and
>> gets a new Ipv6 subnet (I have seen comcast do this to me
>> every time that happens with the code I have in place now - no
>> retraction, and I go through hell manually eliminating every former
>> prefix from the network. Yes. I have upses. And cerowrt, at least,
>> stays up for 90+ days without a problem. But it happens and sucks when
>> it does)
>
> Renumbering should just work as usual. I.e. rest of nodes should learn of=
 the new prefix, and old one should disappear.

I hope so. Arbitrary renumber is really the biggest PITA I presently
have with comcast.

Well, with the exception of naming - ipv6 mapping - which I have just
totally given up on at present. Try to get a printer to reliably work
with a dynamic public ipv6 address... with mdns... it is less painful
to merely shoot nails into your head.

> -Markus



--=20
Dave T=C3=A4ht

thttp://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks


From nobody Sat Feb 21 11:48:49 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 54F621A1BA0 for <homenet@ietfa.amsl.com>; Sat, 21 Feb 2015 11:48:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35] autolearn=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 7sPhBGRRIwU7 for <homenet@ietfa.amsl.com>; Sat, 21 Feb 2015 11:48:45 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 F28B91A1B34 for <homenet@ietf.org>; Sat, 21 Feb 2015 11:48:34 -0800 (PST)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t1LJmVcU027457; Sat, 21 Feb 2015 20:48:31 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 3CFDE2C1D72; Sat, 21 Feb 2015 20:48:31 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id fdvnqU6vsD3k; Sat, 21 Feb 2015 20:48:29 +0100 (CET)
Received: from pirx.pps.jussieu.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 903F82C1D6E; Sat, 21 Feb 2015 20:48:29 +0100 (CET)
Date: Sat, 21 Feb 2015 20:48:29 +0100
Message-ID: <87twyfgi5u.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Toerless Eckert <eckert@cisco.com>
In-Reply-To: <20150221191255.GL8096@cisco.com>
References: <alpine.DEB.2.02.1502201310050.4007@uplift.swm.pp.se> <09793905-8D12-49E0-A040-490F617C87FF@inf-net.nl> <alpine.DEB.2.02.1502201410510.4007@uplift.swm.pp.se> <82E892D5-98C3-4DD8-9E78-A754D77A5AF6@employees.org> <alpine.DEB.2.02.1502201455500.4007@uplift.swm.pp.se> <20150220224225.GH8096@cisco.com> <alpine.DEB.2.02.1502210658230.4007@uplift.swm.pp.se> <871tljjphw.wl-jch@pps.univ-paris-diderot.fr> <20150221180718.GK8096@cisco.com> <87y4nrgkqr.wl-jch@pps.univ-paris-diderot.fr> <20150221191255.GL8096@cisco.com>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Sat, 21 Feb 2015 20:48:31 +0100 (CET)
X-Miltered: at korolev with ID 54E8E10F.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54E8E10F.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54E8E10F.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/ukXIE9rLcC3mRKVj9VPyXYaYw6I>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Roaming hosts [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sat, 21 Feb 2015 19:48:46 -0000

> I am not sure how important it is to separate fast-hello from route
> announcements for hosts. We may have <= 10 addresses on a host. Where would
> be have a problem ?

Radio congestion due to the announcements from the routers, which in RIP
would be advertising the whole network every Update interval.  One
full-size frame every 72 routes, multiply by the number of routers in
range, divide by the Update interval.

(Recall that multicast is 2Mbit/s at the phy.  13ms for a full-size frame,
not counting the cost of collisions.)

> Something as simple as RIP also makes it very easy to embed it as
> a library into apps

No sensible platform allows unpriviledged code to manipulate the routing
tables.  But if you manage to solve this particular problem, the stub
implementation of Babel is 1000 lines of portable C.

> Lets just say with <= 5 sec failover time.

Babel has consistently been measured as having failover times of 2 to
5 hello intervals over IBSS, with no link-layer support, independent of
update interval (due to triggered updates and reactive route requests).
The protocol supports Hello intervals down to 10ms, and allows varying
Hello intervals dynamically (a feature not used by the current
implementation).

-- Juliusz


From nobody Sat Feb 21 12:26:18 2015
Return-Path: <eckert@cisco.com>
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 CFE1D1A034F for <homenet@ietfa.amsl.com>; Sat, 21 Feb 2015 12:26:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 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_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 Bkwtzc-JiAXo for <homenet@ietfa.amsl.com>; Sat, 21 Feb 2015 12:26:13 -0800 (PST)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B73761A046D for <homenet@ietf.org>; Sat, 21 Feb 2015 12:26:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1093; q=dns/txt; s=iport; t=1424550373; x=1425759973; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=NQY6W6Q9cLd44qIlcHK/pRdAnXZD4m4hi7Qrp0O+F5Q=; b=IUskvglbIfcb5UudcYDfeqgvZtRhUHhpvbCHGbEYJ5JqCMnB1hWSoOf/ ZSnzWARROEqsDcrC9I0wFxp11WQzXN7hbCT4siSO6A6dlLbmoloB7qNE4 u5ljMT68f7a6hCh/jIQykvtwMzC1v88gA4r2wiR6udCT3D0V81ZIQQk0g Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BHBQA96ehU/5ldJa1agwaBLMkAAoEZQwEBAQEBAXyEDwEBAQMBOj8QCw4KCSUPBUkTiCcI0mQBAQEBAQEBAQEBAQEBAQEBAQEBAQEXixOEbgeEKwWKSo5KAYEbi0uGTSKEDx0xgkMBAQE
X-IronPort-AV: E=Sophos;i="5.09,621,1418083200"; d="scan'208";a="398035001"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-5.cisco.com with ESMTP; 21 Feb 2015 20:26:12 +0000
Received: from mcast-linux1.cisco.com (mcast-linux1.cisco.com [172.27.244.121]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id t1LKQB9c004738 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 21 Feb 2015 20:26:12 GMT
Received: from mcast-linux1.cisco.com (localhost.cisco.com [127.0.0.1]) by mcast-linux1.cisco.com (8.13.8/8.13.8) with ESMTP id t1LKQBto009069; Sat, 21 Feb 2015 12:26:11 -0800
Received: (from eckert@localhost) by mcast-linux1.cisco.com (8.13.8/8.13.8/Submit) id t1LKQBpY009068; Sat, 21 Feb 2015 12:26:11 -0800
Date: Sat, 21 Feb 2015 12:26:11 -0800
From: Toerless Eckert <eckert@cisco.com>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Message-ID: <20150221202610.GM8096@cisco.com>
References: <alpine.DEB.2.02.1502201410510.4007@uplift.swm.pp.se> <82E892D5-98C3-4DD8-9E78-A754D77A5AF6@employees.org> <alpine.DEB.2.02.1502201455500.4007@uplift.swm.pp.se> <20150220224225.GH8096@cisco.com> <alpine.DEB.2.02.1502210658230.4007@uplift.swm.pp.se> <871tljjphw.wl-jch@pps.univ-paris-diderot.fr> <20150221180718.GK8096@cisco.com> <87y4nrgkqr.wl-jch@pps.univ-paris-diderot.fr> <20150221191255.GL8096@cisco.com> <87twyfgi5u.wl-jch@pps.univ-paris-diderot.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <87twyfgi5u.wl-jch@pps.univ-paris-diderot.fr>
User-Agent: Mutt/1.4.2.2i
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/w-s1Kebbs1-LtpW56qQ8zCjZbME>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Roaming hosts [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sat, 21 Feb 2015 20:26:17 -0000

On Sat, Feb 21, 2015 at 08:48:29PM +0100, Juliusz Chroboczek wrote:
> (Recall that multicast is 2Mbit/s at the phy.  13ms for a full-size frame,
> not counting the cost of collisions.)

Ok. But we also need a way to support fast router redundancy IMHO.

Cheers
    Toerless

> > Something as simple as RIP also makes it very easy to embed it as
> > a library into apps
> 
> No sensible platform allows unpriviledged code to manipulate the routing
> tables.  But if you manage to solve this particular problem, the stub
> implementation of Babel is 1000 lines of portable C.
> 
> > Lets just say with <= 5 sec failover time.
> 
> Babel has consistently been measured as having failover times of 2 to
> 5 hello intervals over IBSS, with no link-layer support, independent of
> update interval (due to triggered updates and reactive route requests).
> The protocol supports Hello intervals down to 10ms, and allows varying
> Hello intervals dynamically (a feature not used by the current
> implementation).
> 
> -- Juliusz

-- 
---
Toerless Eckert, eckert@cisco.com


From nobody Sat Feb 21 12:29:25 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 9D2F31A046D for <homenet@ietfa.amsl.com>; Sat, 21 Feb 2015 12:29:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35] autolearn=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 jVZ65R8Cft7I for <homenet@ietfa.amsl.com>; Sat, 21 Feb 2015 12:29:22 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 7D0711A034F for <homenet@ietf.org>; Sat, 21 Feb 2015 12:29:22 -0800 (PST)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t1LKTJeG001003; Sat, 21 Feb 2015 21:29:19 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 54D012C1D74; Sat, 21 Feb 2015 21:29:19 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id DPmax_YeCYgT; Sat, 21 Feb 2015 21:29:17 +0100 (CET)
Received: from pirx.pps.jussieu.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id D95F92C1D6E; Sat, 21 Feb 2015 21:29:17 +0100 (CET)
Date: Sat, 21 Feb 2015 21:29:17 +0100
Message-ID: <87ioevgg9u.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Toerless Eckert <eckert@cisco.com>
In-Reply-To: <20150221202610.GM8096@cisco.com>
References: <alpine.DEB.2.02.1502201410510.4007@uplift.swm.pp.se> <82E892D5-98C3-4DD8-9E78-A754D77A5AF6@employees.org> <alpine.DEB.2.02.1502201455500.4007@uplift.swm.pp.se> <20150220224225.GH8096@cisco.com> <alpine.DEB.2.02.1502210658230.4007@uplift.swm.pp.se> <871tljjphw.wl-jch@pps.univ-paris-diderot.fr> <20150221180718.GK8096@cisco.com> <87y4nrgkqr.wl-jch@pps.univ-paris-diderot.fr> <20150221191255.GL8096@cisco.com> <87twyfgi5u.wl-jch@pps.univ-paris-diderot.fr> <20150221202610.GM8096@cisco.com>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Sat, 21 Feb 2015 21:29:19 +0100 (CET)
X-Miltered: at korolev with ID 54E8EA9F.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54E8EA9F.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54E8EA9F.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/uyQh2S-ofJPkM5rhvCcCyxGN1I0>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Roaming hosts [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sat, 21 Feb 2015 20:29:23 -0000

>> (Recall that multicast is 2Mbit/s at the phy.  13ms for a full-size frame,
>> not counting the cost of collisions.)

> Ok. But we also need a way to support fast router redundancy IMHO.

Could you please explain what you mean?

-- Juliusz


From nobody Sat Feb 21 12:32:47 2015
Return-Path: <eckert@cisco.com>
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 0791A1A1AE3 for <homenet@ietfa.amsl.com>; Sat, 21 Feb 2015 12:32:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 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_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 tvV1CQX3rMBj for <homenet@ietfa.amsl.com>; Sat, 21 Feb 2015 12:32:44 -0800 (PST)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A2E0C1A046D for <homenet@ietf.org>; Sat, 21 Feb 2015 12:32:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=590; q=dns/txt; s=iport; t=1424550764; x=1425760364; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=5TVQ8/pJBNClPWFD30MmHDLv2lfLt0nZbgyaf1mQkJk=; b=OsnoGBGDV3rdssQ41/4UY5OOsiWmTnqtHW06Uqr5DD4MHiE/mavkSMXz O+hxVV/k/Vi69ucvZ2J8vakl+K1T9s3DbM2dvuZoPuVyvypyYadfhgU1z R0R6haonV5VggetguQmxDVfr5AEmbD7MzmOc5FybPqWUZdLD4OBQiRfR4 M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AuBQCz6uhU/4UNJK1agwbKLAKBGUMBAQEBAQF8hBABAQQ6PxALDgoJJQ8FSYhC0mIBAQEBAQEBAQEBAQEBAQEBAQEBAQEXixOEbgeEKwEEikqOSgGBG4MVjwMihA8dgnQBAQE
X-IronPort-AV: E=Sophos;i="5.09,621,1418083200"; d="scan'208";a="398046073"
Received: from alln-core-11.cisco.com ([173.36.13.133]) by rcdn-iport-3.cisco.com with ESMTP; 21 Feb 2015 20:32:43 +0000
Received: from mcast-linux1.cisco.com (mcast-linux1.cisco.com [172.27.244.121]) by alln-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id t1LKWgps022038 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 21 Feb 2015 20:32:42 GMT
Received: from mcast-linux1.cisco.com (localhost.cisco.com [127.0.0.1]) by mcast-linux1.cisco.com (8.13.8/8.13.8) with ESMTP id t1LKWfLr012407; Sat, 21 Feb 2015 12:32:41 -0800
Received: (from eckert@localhost) by mcast-linux1.cisco.com (8.13.8/8.13.8/Submit) id t1LKWfgF012406; Sat, 21 Feb 2015 12:32:41 -0800
Date: Sat, 21 Feb 2015 12:32:41 -0800
From: Toerless Eckert <eckert@cisco.com>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Message-ID: <20150221203241.GN8096@cisco.com>
References: <alpine.DEB.2.02.1502201455500.4007@uplift.swm.pp.se> <20150220224225.GH8096@cisco.com> <alpine.DEB.2.02.1502210658230.4007@uplift.swm.pp.se> <871tljjphw.wl-jch@pps.univ-paris-diderot.fr> <20150221180718.GK8096@cisco.com> <87y4nrgkqr.wl-jch@pps.univ-paris-diderot.fr> <20150221191255.GL8096@cisco.com> <87twyfgi5u.wl-jch@pps.univ-paris-diderot.fr> <20150221202610.GM8096@cisco.com> <87ioevgg9u.wl-jch@pps.univ-paris-diderot.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <87ioevgg9u.wl-jch@pps.univ-paris-diderot.fr>
User-Agent: Mutt/1.4.2.2i
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/Ckq8EOUQcpnsf_BhsR9tAd7jEYc>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Roaming hosts [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sat, 21 Feb 2015 20:32:46 -0000

On Sat, Feb 21, 2015 at 09:29:17PM +0100, Juliusz Chroboczek wrote:
> >> (Recall that multicast is 2Mbit/s at the phy.  13ms for a full-size frame,
> >> not counting the cost of collisions.)
> 
> > Ok. But we also need a way to support fast router redundancy IMHO.
> 
> Could you please explain what you mean?

If i unicast fast hellos from the client to the router and that router fails
and the secondary router takes over, how would it know about the aliveness state
of all client. I guess i could have the primary router forward the client aliveness
or something the like...


From nobody Sat Feb 21 15:52:35 2015
Return-Path: <mellon@fugue.com>
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 115D21A0122 for <homenet@ietfa.amsl.com>; Sat, 21 Feb 2015 15:52:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 xSbB8pPT2HSN for <homenet@ietfa.amsl.com>; Sat, 21 Feb 2015 15:52:32 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 0209E1A0123 for <homenet@ietf.org>; Sat, 21 Feb 2015 15:52:32 -0800 (PST)
Received: from [10.0.20.107] (c-71-233-43-215.hsd1.nh.comcast.net [71.233.43.215]) by toccata.fugue.com (Postfix) with ESMTPSA id 40773238038C; Sat, 21 Feb 2015 18:52:28 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <CAA93jw7tb6E3cisKLWEpf6xOceakvE8LXeX98k_F-b2THKX+vw@mail.gmail.com>
Date: Sat, 21 Feb 2015 18:51:13 -0500
Content-Transfer-Encoding: 7bit
Message-Id: <3AE6E54C-1E8C-4D69-981C-E9AFE83A6894@fugue.com>
References: <CAA93jw7tb6E3cisKLWEpf6xOceakvE8LXeX98k_F-b2THKX+vw@mail.gmail.com>
To: Dave Taht <dave.taht@gmail.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/PG6QnWtFCoOyFzYYx3LVroF5HEA>
Cc: Markus Stenberg <markus.stenberg@iki.fi>, Steven Barth <cyrus@openwrt.org>, Ole Troan <otroan@employees.org>, Ralph Droms <rdroms.ietf@gmail.com>, "homenet@ietf.org Group" <homenet@ietf.org>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] HNCPD usability issues
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sat, 21 Feb 2015 23:52:34 -0000

Is there an hncpd howto somewhere?


From nobody Sat Feb 21 17:03:21 2015
Return-Path: <dave.taht@gmail.com>
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 BAC911A0178 for <homenet@ietfa.amsl.com>; Sat, 21 Feb 2015 17:03:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.4
X-Spam-Level: 
X-Spam-Status: No, score=-1.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, J_CHICKENPOX_26=0.6, SPF_PASS=-0.001] autolearn=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 K5LjDttNsxcy for <homenet@ietfa.amsl.com>; Sat, 21 Feb 2015 17:03:18 -0800 (PST)
Received: from mail-ob0-x22f.google.com (mail-ob0-x22f.google.com [IPv6:2607:f8b0:4003:c01::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8A7131A017A for <homenet@ietf.org>; Sat, 21 Feb 2015 17:03:12 -0800 (PST)
Received: by mail-ob0-f175.google.com with SMTP id va2so30885631obc.6 for <homenet@ietf.org>; Sat, 21 Feb 2015 17:03:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=15LsDLMJs3KhzRMCWaY8y9m/UZBju6PX/T4TOwY+3fA=; b=HOMP7DmXFF9oIKmYoctRwhPFOw1GG29iUiWYZlwLwfaOCJSyaXwPbmZPTn7Tl7Nsu3 /jxrmp+6lJpe6otBMFE78FUBRZQfnNf20h54ymZG59H1s0cXVElIRgCV1MsptWaMv4Lj oiI9VZXXi24TtAvC3XCpUlBTBo3Iori7iPtX3bgDCpgHDPtl7aDGSjBWajsQ3kvLQvgj d6Q2k7c3+6MjiXbfBQAdg3rLl71WCn6R9/5eJk55JskZJLWlNJCinUQxBAH8UzSNPMpQ qFC4eLvMJcdVxg6P6IVKxSgkZoRrhpURb9Ifk0SVqCzVlR9x2FjcycqMUYMqWAGKgNXZ 3u+Q==
MIME-Version: 1.0
X-Received: by 10.182.144.136 with SMTP id sm8mr3053394obb.63.1424566991781; Sat, 21 Feb 2015 17:03:11 -0800 (PST)
Received: by 10.202.51.66 with HTTP; Sat, 21 Feb 2015 17:03:11 -0800 (PST)
In-Reply-To: <3AE6E54C-1E8C-4D69-981C-E9AFE83A6894@fugue.com>
References: <CAA93jw7tb6E3cisKLWEpf6xOceakvE8LXeX98k_F-b2THKX+vw@mail.gmail.com> <3AE6E54C-1E8C-4D69-981C-E9AFE83A6894@fugue.com>
Date: Sat, 21 Feb 2015 17:03:11 -0800
Message-ID: <CAA93jw5g1gArQ2M8c9_tmHodvFovfm6nCWY9qW+MH87kM2yh-Q@mail.gmail.com>
From: Dave Taht <dave.taht@gmail.com>
To: Ted Lemon <mellon@fugue.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/_KbqR93X4tLY3ZWKQqo0DcRP1z8>
Cc: Markus Stenberg <markus.stenberg@iki.fi>, Steven Barth <cyrus@openwrt.org>, Ole Troan <otroan@employees.org>, Ralph Droms <rdroms.ietf@gmail.com>, "homenet@ietf.org Group" <homenet@ietf.org>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] HNCPD usability issues
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sun, 22 Feb 2015 01:03:19 -0000

On Sat, Feb 21, 2015 at 3:51 PM, Ted Lemon <mellon@fugue.com> wrote:
> Is there an hncpd howto somewhere?
>

http://www.homewrt.org/doku.php?id=3Doverview

I am not sure if the howto is entirely up to date - for example I hope
they switched to using the standard openwrt ip6assign instead ip6_plen
in the /etc/config/network file.

I note that until last week I had not touched openwrt in 8 months, and
have not yet tried the latest hnetd - what I had tried to do a month
or two back with hnetd was on debian. I filed a couple bugs and then
had to do something else.

https://github.com/sbyx/hnetd/issues

one that was a PITA, now closed:

https://github.com/sbyx/hnetd/issues/21

This dhcpv6 bug with the cablemodem made PD impossible to use - the
"fix" filters it out, but the modem still gets wedged in this state,
and the issue remains unresolved upstream at comcast so far as I know.

https://github.com/sbyx/odhcp6c/issues/27

As for my relay issue in the previous mail, I think the sanest/fastest
thing for me (as opposed to the hnetd folk) to do is write a generic
udp relay program for ipv6,  (there are many for ipv4, none I have yet
found decrement the TTL. Sigh), rather than try to understand the
codebase.

--=20
Dave T=C3=A4ht

http://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks


From nobody Sat Feb 21 18:53:03 2015
Return-Path: <dave.taht@gmail.com>
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 3C5FB1A003A for <homenet@ietfa.amsl.com>; Sat, 21 Feb 2015 18:53:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 AP9VDeRpt2S5 for <homenet@ietfa.amsl.com>; Sat, 21 Feb 2015 18:53:00 -0800 (PST)
Received: from mail-ob0-x231.google.com (mail-ob0-x231.google.com [IPv6:2607:f8b0:4003:c01::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 26AF41A036F for <homenet@ietf.org>; Sat, 21 Feb 2015 18:53:00 -0800 (PST)
Received: by mail-ob0-f177.google.com with SMTP id wp18so29661606obc.8 for <homenet@ietf.org>; Sat, 21 Feb 2015 18:52:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=K3XjiOfqTei7LteKxZ5I+wcciPWFxMGDmQOkPZP7gQ0=; b=f6YcUx7ikbIRPA+w3qYziVwsD8by1qeIcD6vGAKnoT8Ghh2Q9iihv6rQD4eHrODusO Dth2JVStZjCSTsLr28F9vaTZcAvPUYjxwxl78VDk7Qf1scViemAVKu2sQ2b9YZpszfTf IRqzPjNSwKrm+GzzlbRwVaFZi4ZCbY1ZBD/mxr+kcbmGS1d5uRKtAU1gTjkDPpYK5DpN 71Iv7Oebkm/Tm9PqYbF6NwwY0xKwWFDVMBXO+ookJliudUv4IRvtXNuqrqoewf+hdLNI hYx7Kr7YnmoWb+PzydqBC/xySVPVJqW6dj5+AHN2jYTIZWMgyY4d8WfUKk8WFj/QL3TC ItLA==
MIME-Version: 1.0
X-Received: by 10.60.119.4 with SMTP id kq4mr3216492oeb.75.1424573579492; Sat, 21 Feb 2015 18:52:59 -0800 (PST)
Received: by 10.202.51.66 with HTTP; Sat, 21 Feb 2015 18:52:59 -0800 (PST)
In-Reply-To: <CAA93jw5g1gArQ2M8c9_tmHodvFovfm6nCWY9qW+MH87kM2yh-Q@mail.gmail.com>
References: <CAA93jw7tb6E3cisKLWEpf6xOceakvE8LXeX98k_F-b2THKX+vw@mail.gmail.com> <3AE6E54C-1E8C-4D69-981C-E9AFE83A6894@fugue.com> <CAA93jw5g1gArQ2M8c9_tmHodvFovfm6nCWY9qW+MH87kM2yh-Q@mail.gmail.com>
Date: Sat, 21 Feb 2015 18:52:59 -0800
Message-ID: <CAA93jw7ha_JAJO1vEnvy5wqMx+mWCQRdWTjTTXjor2xmei=7Gg@mail.gmail.com>
From: Dave Taht <dave.taht@gmail.com>
To: Ted Lemon <mellon@fugue.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/QvVQUJDd2Z7jE_IqdcOK0MsA4Do>
Cc: Markus Stenberg <markus.stenberg@iki.fi>, Steven Barth <cyrus@openwrt.org>, Ole Troan <otroan@employees.org>, Ralph Droms <rdroms.ietf@gmail.com>, "homenet@ietf.org Group" <homenet@ietf.org>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] HNCPD usability issues
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sun, 22 Feb 2015 02:53:02 -0000

and while I am at it, reviewing the draft shows that:

"  HNCP requires allocation of UDP port numbers HNCP-UDP-PORT and HNCP-
   DTLS-PORT, as well as an IPv6 link-local multicast address All-
   Homenet-Routers."

have these been applied for?

There is no scarcity on ipv6 multicast addresses at least.

In looking at the code base I see it is using

#define HNCP_PORT 8808
#define HNCP_MCAST_GROUP "ff02::8808"

no definition for a DTLS port and 8808 does not show as allocated by IANA.


From nobody Sat Feb 21 18:57:49 2015
Return-Path: <mellon@fugue.com>
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 2DAF21A03A1 for <homenet@ietfa.amsl.com>; Sat, 21 Feb 2015 18:57:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 IeVAMlA9MZcP for <homenet@ietfa.amsl.com>; Sat, 21 Feb 2015 18:57:46 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id F37B91A003A for <homenet@ietf.org>; Sat, 21 Feb 2015 18:57:45 -0800 (PST)
Received: from [10.0.20.107] (c-71-233-43-215.hsd1.nh.comcast.net [71.233.43.215]) by toccata.fugue.com (Postfix) with ESMTPSA id BC634238038C; Sat, 21 Feb 2015 21:57:43 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <CAA93jw7ha_JAJO1vEnvy5wqMx+mWCQRdWTjTTXjor2xmei=7Gg@mail.gmail.com>
Date: Sat, 21 Feb 2015 21:56:26 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <FDF8CADD-C86C-42D6-9650-D11223BF75A0@fugue.com>
References: <CAA93jw7tb6E3cisKLWEpf6xOceakvE8LXeX98k_F-b2THKX+vw@mail.gmail.com> <3AE6E54C-1E8C-4D69-981C-E9AFE83A6894@fugue.com> <CAA93jw5g1gArQ2M8c9_tmHodvFovfm6nCWY9qW+MH87kM2yh-Q@mail.gmail.com> <CAA93jw7ha_JAJO1vEnvy5wqMx+mWCQRdWTjTTXjor2xmei=7Gg@mail.gmail.com>
To: Dave Taht <dave.taht@gmail.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/akyR7XMjMsMQ0HgqkiMiuLCoR0o>
Cc: Markus Stenberg <markus.stenberg@iki.fi>, Steven Barth <cyrus@openwrt.org>, Ole Troan <otroan@employees.org>, Ralph Droms <rdroms.ietf@gmail.com>, "homenet@ietf.org Group" <homenet@ietf.org>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] HNCPD usability issues
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sun, 22 Feb 2015 02:57:47 -0000

Getting an early allocation for two UDP ports is probably not going to =
happen.   A link-local multicast address early allocation isn't out of =
the question, but it would be easier to just publish the document.



From nobody Sat Feb 21 22:38:09 2015
Return-Path: <joelja@bogus.com>
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 6DAC81A1B0D for <homenet@ietfa.amsl.com>; Sat, 21 Feb 2015 22:38:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.01
X-Spam-Level: 
X-Spam-Status: No, score=-0.01 tagged_above=-999 required=5 tests=[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 PThgVusPT5kx for <homenet@ietfa.amsl.com>; Sat, 21 Feb 2015 22:38:04 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) (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 15F151A1B0C for <homenet@ietf.org>; Sat, 21 Feb 2015 22:38:04 -0800 (PST)
Received: from mb-aye.local ([IPv6:2601:9:3402:7bb1:dc23:37b0:8843:73a1]) (authenticated bits=0) by nagasaki.bogus.com (8.14.9/8.14.9) with ESMTP id t1M6c2nT007114 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sun, 22 Feb 2015 06:38:03 GMT (envelope-from joelja@bogus.com)
Message-ID: <54E9794A.2060402@bogus.com>
Date: Sat, 21 Feb 2015 22:38:02 -0800
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:36.0) Gecko/20100101 Thunderbird/36.0
MIME-Version: 1.0
To: Dave Taht <dave.taht@gmail.com>, HOMENET <homenet@ietf.org>
References: <CAA93jw7eGxPBNX+5LqX+qTYfRxNDxQpKo1fecUa2XH3bAKgvQQ@mail.gmail.com>
In-Reply-To: <CAA93jw7eGxPBNX+5LqX+qTYfRxNDxQpKo1fecUa2XH3bAKgvQQ@mail.gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="S2WUHgdKBI9LsjS8O5UrO1wlJhPdbp0lc"
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/BRLk33G6xFRvBrsVcpKHaG0ht2I>
Subject: Re: [homenet] A poll
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sun, 22 Feb 2015 06:38:05 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--S2WUHgdKBI9LsjS8O5UrO1wlJhPdbp0lc
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

On 2/20/15 8:50 AM, Dave Taht wrote:
> The homenet working group has been laboring for several years now to
> find ways to make ipv6 more deployable to home (and presumably small
> business) users.
>=20
> In addition to multiple specification documents some code has been
> produced to try and make things easier. At least in the USA, comcast
> has rolled out IPv6 to everyone that can get dhcpv6 to sort of work on
> their router, and/or is willing to install a custom firmware on their
> router to get that, and of course tunneling ipv6 is possible if the
> ISP does not support it.
>=20
> So a quick poll:
>=20
> 0) Have you managed to get ipv6 working at all? If so, how? What sort
> of problems did you encounter?

yes,

comcast,  docsis 3.0 modem (mot surboard),  d-link dir-860L, cpe set to
auto, did dhcpv6 +pd requested at /64. previously variants of the setup
have have working v6 since 2011 with consumer gateways (mostly netgear).

> 1) Have you attempted to deploy a routing protocol in your home? Which
> one, and why?

routed subnets, (e.g. dmz, internal) no igp

> 2) Have you attempted to get hnetd's prefix distribution system
> working? (it supports linux mainline and openwrt presently)

> 3) Do you use ethernet? How many clients in your home are ethernet conn=
ected?

yes, about half a dozen

> 4) Do you use wifi? How many clients are wifi connected? Do you use
> range extenders?

yes about a dozen

> 5) How many devices do you think you will have connected to the
> network in your home in 5 years? How many now?

more

> 6) Do you use any other network connected technologies (homeplug,
> 802.14, LTE, etc). If so, which ones, and why?

LTE cellular gateway for use when primary is down, failover is not
automatic.

perversely the LTE has v6 when directly attached to a client machine
however not when operating as a gateway (no PD)

> 7) Do you use mdns service discovery?

yes

> 8) Why are you here? (especially, if your answers to 0-2, are "no")

to share the love.

>=20



--S2WUHgdKBI9LsjS8O5UrO1wlJhPdbp0lc
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAlTpeUoACgkQ8AA1q7Z/VrKZFACfeEorLg+4WGTusaustvmCCz1y
Vd0AnRI6zeAUuLM4SlBqfMwysVr1aVCS
=OKIl
-----END PGP SIGNATURE-----

--S2WUHgdKBI9LsjS8O5UrO1wlJhPdbp0lc--


From nobody Sun Feb 22 00:18:03 2015
Return-Path: <cyrus@openwrt.org>
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 75AE71A1B22 for <homenet@ietfa.amsl.com>; Sun, 22 Feb 2015 00:18:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.25
X-Spam-Level: 
X-Spam-Status: No, score=0.25 tagged_above=-999 required=5 tests=[HELO_EQ_DE=0.35, J_CHICKENPOX_26=0.6, RCVD_IN_DNSWL_LOW=-0.7] autolearn=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 2QaQQG4P7rcv for <homenet@ietfa.amsl.com>; Sun, 22 Feb 2015 00:17:59 -0800 (PST)
Received: from mail.core-networks.de (mail.core-networks.de [82.96.72.7]) by ietfa.amsl.com (Postfix) with ESMTP id A05391A1A19 for <homenet@ietf.org>; Sun, 22 Feb 2015 00:17:59 -0800 (PST)
Received: from localhost ([127.0.0.1]) by mail.core-networks.de id 1YPRjc-0001A1-Rf with ESMTPSA (TLSv1.2:DHE-RSA-AES128-SHA:128) for ; Sun, 22 Feb 2015 09:17:53 +0100
Message-ID: <54E990AA.7010402@openwrt.org>
Date: Sun, 22 Feb 2015 09:17:46 +0100
From: Steven Barth <cyrus@openwrt.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.4.0
MIME-Version: 1.0
To: Dave Taht <dave.taht@gmail.com>, Ted Lemon <mellon@fugue.com>
References: <CAA93jw7tb6E3cisKLWEpf6xOceakvE8LXeX98k_F-b2THKX+vw@mail.gmail.com> <3AE6E54C-1E8C-4D69-981C-E9AFE83A6894@fugue.com> <CAA93jw5g1gArQ2M8c9_tmHodvFovfm6nCWY9qW+MH87kM2yh-Q@mail.gmail.com>
In-Reply-To: <CAA93jw5g1gArQ2M8c9_tmHodvFovfm6nCWY9qW+MH87kM2yh-Q@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/pLHbD4os-HeeQ4ps0OjpoEmtFLo>
Cc: Ole Troan <otroan@employees.org>, Markus Stenberg <markus.stenberg@iki.fi>, Ralph Droms <rdroms.ietf@gmail.com>, Mikael Abrahamsson <swmike@swm.pp.se>, "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] HNCPD usability issues
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sun, 22 Feb 2015 08:18:01 -0000

On 22.02.2015 02:03, Dave Taht wrote:
> On Sat, Feb 21, 2015 at 3:51 PM, Ted Lemon <mellon@fugue.com> wrote:
>> Is there an hncpd howto somewhere?
>>
Please see http://www.homewrt.org/doku.php?id=run-conf
It is still up-to-date. The webinterface these days has some support for 
HNCP
configuration as well. Just make sure to not use the names "lan" oder 
"wan" for any hnet.

In the end its just as easy as installing the hnet-full package and 
adding a config section
config interface homenet1
     option ifname eth1
     option proto hncp

for each of your interfaces.

> I am not sure if the howto is entirely up to date - for example I hope
> they switched to using the standard openwrt ip6assign instead ip6_plen
> in the /etc/config/network file.
Not yet.

> As for my relay issue in the previous mail, I think the sanest/fastest
> thing for me (as opposed to the hnetd folk) to do is write a generic
> udp relay program for ipv6,  (there are many for ipv4, none I have yet
> found decrement the TTL. Sigh), rather than try to understand the
> codebase.
As noted before option disable_pa 1 in the relevant interface 
config-section should actually just disable assigning prefixes to that 
interface. Alternatively as noted you can just change the prefix length 
to /80 or so. At some point we added support for assigning only a /128 
to lo but I haven't actually tested it in a while and I don't think its 
in our unittests.


Cheers,

Steven


From nobody Sun Feb 22 00:18:51 2015
Return-Path: <cyrus@openwrt.org>
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 5631F1A1B40 for <homenet@ietfa.amsl.com>; Sun, 22 Feb 2015 00:18:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.35
X-Spam-Level: 
X-Spam-Status: No, score=-0.35 tagged_above=-999 required=5 tests=[HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-0.7] 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 7fsJKVGOWXEJ for <homenet@ietfa.amsl.com>; Sun, 22 Feb 2015 00:18:48 -0800 (PST)
Received: from mail.core-networks.de (mail.core-networks.de [82.96.72.7]) by ietfa.amsl.com (Postfix) with ESMTP id 9195B1A1B37 for <homenet@ietf.org>; Sun, 22 Feb 2015 00:18:48 -0800 (PST)
Received: from localhost ([127.0.0.1]) by mail.core-networks.de id 1YPRkU-0001CP-Ff with ESMTPSA (TLSv1.2:DHE-RSA-AES128-SHA:128) for ; Sun, 22 Feb 2015 09:18:46 +0100
Message-ID: <54E990E2.1030002@openwrt.org>
Date: Sun, 22 Feb 2015 09:18:42 +0100
From: Steven Barth <cyrus@openwrt.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.4.0
MIME-Version: 1.0
To: Dave Taht <dave.taht@gmail.com>, Ted Lemon <mellon@fugue.com>
References: <CAA93jw7tb6E3cisKLWEpf6xOceakvE8LXeX98k_F-b2THKX+vw@mail.gmail.com> <3AE6E54C-1E8C-4D69-981C-E9AFE83A6894@fugue.com> <CAA93jw5g1gArQ2M8c9_tmHodvFovfm6nCWY9qW+MH87kM2yh-Q@mail.gmail.com> <54E990AA.7010402@openwrt.org>
In-Reply-To: <54E990AA.7010402@openwrt.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/mEhtwN0AaI0uUSc9CMmWuGVS9Tc>
Cc: Ole Troan <otroan@employees.org>, Markus Stenberg <markus.stenberg@iki.fi>, Ralph Droms <rdroms.ietf@gmail.com>, "homenet@ietf.org Group" <homenet@ietf.org>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] HNCPD usability issues
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sun, 22 Feb 2015 08:18:49 -0000

>
> In the end its just as easy as installing the hnet-full package and 
> adding a config section
> config interface homenet1
>     option ifname eth1
>     option proto hncp
option proto hnet

sorry, typo ;)


From nobody Sun Feb 22 00:38:27 2015
Return-Path: <dave.taht@gmail.com>
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 6E87E1A01F9 for <homenet@ietfa.amsl.com>; Sun, 22 Feb 2015 00:38:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.5
X-Spam-Level: 
X-Spam-Status: No, score=0.5 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, J_CHICKENPOX_26=0.6, SPF_PASS=-0.001] autolearn=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 4lwISLXr--Vg for <homenet@ietfa.amsl.com>; Sun, 22 Feb 2015 00:38:25 -0800 (PST)
Received: from mail-oi0-x230.google.com (mail-oi0-x230.google.com [IPv6:2607:f8b0:4003:c06::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 29FCF1A0262 for <homenet@ietf.org>; Sun, 22 Feb 2015 00:38:25 -0800 (PST)
Received: by mail-oi0-f48.google.com with SMTP id a3so9140674oib.7 for <homenet@ietf.org>; Sun, 22 Feb 2015 00:38:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=5h9qxQilBIK+2K0AfJZ4WA5YBKTrSQKeX/6tjnXG1CM=; b=HL8JG/6KsbgXgyejhvQSNQrhtNNB9bUVuVl91pjNItmW5C+oyEzIOb9mV45IdHHfyc o6VZnLtwUk5KhyA2QkIR66XKDIU1Fjk+cyzur4HoqPkA2lEYoaMLnHFIDaXOyHKj4hDu F8+RuVaEzpejIuUopJLHhnzDCJpsF6pwB5puN3RIpXtjnJRPhQOqAZ2KrDWo6EmxXJc4 XvO2Y5XBxsHhsC7puTJuPfm9YfAPThvOqgA37lf2fYFVK5eoShxZgtpEPYoGHGALZGoO wRZq0yZezHRXlWvKm3gegdsilwvgCB2zjWwBefVlsknLZEPFgv+pVOt5m9TAVx4ykTNH KVmg==
MIME-Version: 1.0
X-Received: by 10.202.204.88 with SMTP id c85mr3612597oig.81.1424594304058; Sun, 22 Feb 2015 00:38:24 -0800 (PST)
Received: by 10.202.51.66 with HTTP; Sun, 22 Feb 2015 00:38:24 -0800 (PST)
In-Reply-To: <54E990AA.7010402@openwrt.org>
References: <CAA93jw7tb6E3cisKLWEpf6xOceakvE8LXeX98k_F-b2THKX+vw@mail.gmail.com> <3AE6E54C-1E8C-4D69-981C-E9AFE83A6894@fugue.com> <CAA93jw5g1gArQ2M8c9_tmHodvFovfm6nCWY9qW+MH87kM2yh-Q@mail.gmail.com> <54E990AA.7010402@openwrt.org>
Date: Sun, 22 Feb 2015 00:38:24 -0800
Message-ID: <CAA93jw5nPTA0WemT8Kgkp_1rj_ZGt05CV=5ypwECusCA_T6TZQ@mail.gmail.com>
From: Dave Taht <dave.taht@gmail.com>
To: Steven Barth <cyrus@openwrt.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/A92OQWbr2kGzMAnRqHhuaRgfJkM>
Cc: Markus Stenberg <markus.stenberg@iki.fi>, Ted Lemon <mellon@fugue.com>, Ole Troan <otroan@employees.org>, Ralph Droms <rdroms.ietf@gmail.com>, "homenet@ietf.org Group" <homenet@ietf.org>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] HNCPD usability issues
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sun, 22 Feb 2015 08:38:26 -0000

On Sun, Feb 22, 2015 at 12:17 AM, Steven Barth <cyrus@openwrt.org> wrote:
>
> On 22.02.2015 02:03, Dave Taht wrote:
>>
>> On Sat, Feb 21, 2015 at 3:51 PM, Ted Lemon <mellon@fugue.com> wrote:
>>>
>>> Is there an hncpd howto somewhere?
>>>
> Please see http://www.homewrt.org/doku.php?id=3Drun-conf
> It is still up-to-date. The webinterface these days has some support for
> HNCP
> configuration as well. Just make sure to not use the names "lan" oder "wa=
n"
> for any hnet.
>
> In the end its just as easy as installing the hnet-full package and addin=
g a
> config section
> config interface homenet1
>     option ifname eth1
>     option proto hncp
>
> for each of your interfaces.
>
>> I am not sure if the howto is entirely up to date - for example I hope
>> they switched to using the standard openwrt ip6assign instead ip6_plen
>> in the /etc/config/network file.
>
> Not yet.

It is only a sed script away.

>> As for my relay issue in the previous mail, I think the sanest/fastest
>> thing for me (as opposed to the hnetd folk) to do is write a generic
>> udp relay program for ipv6,  (there are many for ipv4, none I have yet
>> found decrement the TTL. Sigh), rather than try to understand the
>> codebase.
>
> As noted before option disable_pa 1 in the relevant interface config-sect=
ion
> should actually just disable assigning prefixes to that interface.
> Alternatively as noted you can just change the prefix length to /80 or so=
.
> At some point we added support for assigning only a /128 to lo but I have=
n't
> actually tested it in a while and I don't think its in our unittests.

OK, I think. So if I have a stanza like this?

config interface 'lan'
        option ifname 'eth0.1'
        option force_link '1'
        option proto 'static'
        option ipaddr '172.21.80.1'
        option netmask '255.255.255.0'
        option ip6assign '64'

config interface 'homenet1'
        option ifname 'eth0.1'
        option proto =C2=B4hnet'
        option disable_pa 1

that interface would act as a relay, and not assign a /64 to the lan interf=
ace?

I note the last time I tried to install hnet-full it bricked the
router, killing dnsmasq entirely, killing dhcp, etc, so I was leery of
experimenting again... but I am willing to try again, being a glutton
for pain at 1AM.

moving on to more complexity, so getting that first 64 would look like?

config interface 'lan'
        option ifname 'eth0.1'
        option force_link '1'
        option proto 'static'
        option ipaddr '172.21.80.1'
        option netmask '255.255.255.0'

config interface 'homenet1'
        option ifname 'eth0.1'
        option proto 'hnet'
        option disable_pa 0
        option p6_plen 64

?

Then getting a dynamic ipv4?

Moving into more functionality, I see the documentation recommends
against using the hnet protocol on predefined interfaces like lan
entirely... if I wanted ipv4 address assignment (and I dont - without
dns to ip mapping actually working finding a box again is impossible),
what happens to these two stanzas?

How does the firewall pick it all up?

And then, there is the final caution to the winds, go pure hnetd
option. This is my freshly built, openwrt chaos calmer based config
file. It is an interior gw router (no nat):

http://snapon.lab.bufferbloat.net/~d/network

What changes are needed to drink the koolaid?

my ip route source specific stuff is working good (actual egress
gateway is like 5 hops away)

default from :: via fe80::28c6:8eff:febb:9ff0 dev eth1  proto babel  metric=
 1024
default from 2001:558:6045:e9:251a:738a:ac86:eaf6 via
fe80::28c6:8eff:febb:9ff0 dev eth1  proto babel  metric 1024
default from 2601:9:4e00:4cb0::/60 via fe80::28c6:8eff:febb:9ff0 dev
eth1  proto babel  metric 1024
2601:9:4e00:4cb1::/64 via fe80::28c6:8eff:febb:9ff0 dev eth1  proto
babel  metric 1024
2601:9:4e00:4cb2::/64 via fe80::28c6:8eff:febb:9ff0 dev eth1  proto
babel  metric 1024
2601:9:4e00:4cb3::/64 via fe80::28c6:8eff:febb:9ff0 dev eth1  proto
babel  metric 1024
2601:9:4e00:4cb4::/64 via fe80::28c6:8eff:febb:9ff0 dev eth1  proto
babel  metric 1024
2601:9:4e00:4cb7::2 via fe80::eea8:6bff:fefe:9a2 dev eth0.1  proto
babel  metric 1024 # manually assigned ip on my desktop
2601:9:4e00:4cb0::/60 via fe80::28c6:8eff:febb:9ff0 dev eth1  proto
babel  metric 1024


>
>
> Cheers,
>
> Steven



--=20
Dave T=C3=A4ht

thttp://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks


From nobody Sun Feb 22 00:55:14 2015
Return-Path: <cyrus@openwrt.org>
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 658741A86E8 for <homenet@ietfa.amsl.com>; Sun, 22 Feb 2015 00:55:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.25
X-Spam-Level: 
X-Spam-Status: No, score=0.25 tagged_above=-999 required=5 tests=[HELO_EQ_DE=0.35, J_CHICKENPOX_26=0.6, RCVD_IN_DNSWL_LOW=-0.7] autolearn=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 zR9eR9NzNr-w for <homenet@ietfa.amsl.com>; Sun, 22 Feb 2015 00:55:12 -0800 (PST)
Received: from mail.core-networks.de (mail.core-networks.de [82.96.72.7]) by ietfa.amsl.com (Postfix) with ESMTP id 676B71A6F7A for <homenet@ietf.org>; Sun, 22 Feb 2015 00:55:12 -0800 (PST)
Received: from localhost ([127.0.0.1]) by mail.core-networks.de id 1YPSJh-0002KU-IM with ESMTPSA (TLSv1.2:DHE-RSA-AES128-SHA:128) for ; Sun, 22 Feb 2015 09:55:09 +0100
Message-ID: <54E99969.3080907@openwrt.org>
Date: Sun, 22 Feb 2015 09:55:05 +0100
From: Steven Barth <cyrus@openwrt.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.4.0
MIME-Version: 1.0
To: Dave Taht <dave.taht@gmail.com>
References: <CAA93jw7tb6E3cisKLWEpf6xOceakvE8LXeX98k_F-b2THKX+vw@mail.gmail.com> <3AE6E54C-1E8C-4D69-981C-E9AFE83A6894@fugue.com> <CAA93jw5g1gArQ2M8c9_tmHodvFovfm6nCWY9qW+MH87kM2yh-Q@mail.gmail.com> <54E990AA.7010402@openwrt.org> <CAA93jw5nPTA0WemT8Kgkp_1rj_ZGt05CV=5ypwECusCA_T6TZQ@mail.gmail.com>
In-Reply-To: <CAA93jw5nPTA0WemT8Kgkp_1rj_ZGt05CV=5ypwECusCA_T6TZQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/QmkWTbrKrfuQ5FAKvr22uYq6UCU>
Cc: Markus Stenberg <markus.stenberg@iki.fi>, Ted Lemon <mellon@fugue.com>, Ole Troan <otroan@employees.org>, Ralph Droms <rdroms.ietf@gmail.com>, "homenet@ietf.org Group" <homenet@ietf.org>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] HNCPD usability issues
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sun, 22 Feb 2015 08:55:13 -0000

On 22.02.2015 09:38, Dave Taht wrote:
> OK, I think. So if I have a stanza like this?
>
> config interface 'lan'
>          option ifname 'eth0.1'
>          option force_link '1'
>          option proto 'static'
>          option ipaddr '172.21.80.1'
>          option netmask '255.255.255.0'
>          option ip6assign '64'
>
> config interface 'homenet1'
>          option ifname 'eth0.1'
>          option proto Â´hnet'
>          option disable_pa 1
>
> that interface would act as a relay, and not assign a /64 to the lan interface?
As noted please avoid assigning the names "lan" or "wan" to interfaces 
running hnet on, but besides that it's worth a try. I'm sort of on 
holiday for a few days, so I can try it out some time late next week.

> I note the last time I tried to install hnet-full it bricked the
> router, killing dnsmasq entirely, killing dhcp, etc, so I was leery of
> experimenting again... but I am willing to try again, being a glutton
> for pain at 1AM.
Was this with CeroWrt? I'd recommend starting with a vanilla OpenWrt.

>
> moving on to more complexity, so getting that first 64 would look like?
>
> config interface 'lan'
>          option ifname 'eth0.1'
>          option force_link '1'
>          option proto 'static'
>          option ipaddr '172.21.80.1'
>          option netmask '255.255.255.0'
>
> config interface 'homenet1'
>          option ifname 'eth0.1'
>          option proto 'hnet'
>          option disable_pa 0
>          option p6_plen 64
>
> ?
>
> Then getting a dynamic ipv4?
Just removing disable_pa and (i)p6_plen will resort to defaults, i.e. 1 
/64 per link for IPv6 and 1 /24 for IPv4.


> Moving into more functionality, I see the documentation recommends
> against using the hnet protocol on predefined interfaces like lan
> entirely... if I wanted ipv4 address assignment (and I dont - without
> dns to ip mapping actually working finding a box again is impossible),
> what happens to these two stanzas?
The only reason to not use "wan" or "lan" is that OpenWrt's firewall has 
some special semantics for interface named after firewall zones. So you 
can just rename the sections and it will work. Or as you noted 
previously you can add an additional static-configuration section for 
the same interface (you just shouldn't name it "lan" or "wan").



> How does the firewall pick it all up?
hnetd tells the firewall which firewall zone ("lan" or "wan") an 
interface should be assigned to. The zones depend on border discovery 
(manual or automatic).


> And then, there is the final caution to the winds, go pure hnetd
> option. This is my freshly built, openwrt chaos calmer based config
> file. It is an interior gw router (no nat):
>
> http://snapon.lab.bufferbloat.net/~d/network
>
> What changes are needed to drink the koolaid?
For each interfaces you want hnet to run on add a config section.
config interface homnet1
     option ifname foo1
     option proto hnet

If the original interface-name was "lan" or "wan" you should rename them 
to something different (but do not need to change anything else).



From nobody Sun Feb 22 00:57:19 2015
Return-Path: <cyrus@openwrt.org>
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 A8F9E1A6F5D for <homenet@ietfa.amsl.com>; Sun, 22 Feb 2015 00:57:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.35
X-Spam-Level: 
X-Spam-Status: No, score=-0.35 tagged_above=-999 required=5 tests=[HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-0.7] 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 x3P4guscoB7L for <homenet@ietfa.amsl.com>; Sun, 22 Feb 2015 00:57:15 -0800 (PST)
Received: from mail.core-networks.de (mail.core-networks.de [82.96.72.7]) by ietfa.amsl.com (Postfix) with ESMTP id C44A01A1F20 for <homenet@ietf.org>; Sun, 22 Feb 2015 00:57:14 -0800 (PST)
Received: from localhost ([127.0.0.1]) by mail.core-networks.de id 1YPSLh-0002Nw-4n with ESMTPSA (TLSv1.2:DHE-RSA-AES128-SHA:128) for ; Sun, 22 Feb 2015 09:57:13 +0100
Message-ID: <54E999E5.6060302@openwrt.org>
Date: Sun, 22 Feb 2015 09:57:09 +0100
From: Steven Barth <cyrus@openwrt.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.4.0
MIME-Version: 1.0
To: Dave Taht <dave.taht@gmail.com>
References: <CAA93jw7tb6E3cisKLWEpf6xOceakvE8LXeX98k_F-b2THKX+vw@mail.gmail.com> <3AE6E54C-1E8C-4D69-981C-E9AFE83A6894@fugue.com> <CAA93jw5g1gArQ2M8c9_tmHodvFovfm6nCWY9qW+MH87kM2yh-Q@mail.gmail.com> <54E990AA.7010402@openwrt.org> <CAA93jw5nPTA0WemT8Kgkp_1rj_ZGt05CV=5ypwECusCA_T6TZQ@mail.gmail.com> <54E99969.3080907@openwrt.org>
In-Reply-To: <54E99969.3080907@openwrt.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/ZGW0Szu6z-iiIEpRi0pi-bMOsYA>
Cc: Markus Stenberg <markus.stenberg@iki.fi>, Ted Lemon <mellon@fugue.com>, Ole Troan <otroan@employees.org>, Ralph Droms <rdroms.ietf@gmail.com>, "homenet@ietf.org Group" <homenet@ietf.org>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] HNCPD usability issues
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sun, 22 Feb 2015 08:57:15 -0000

>
> If the original interface-name was "lan" or "wan" you should rename 
> them to something different (but do not need to change anything else).
>
Additional note:
Do NOT run DHCP or DHCPv6 manually (either server or client) on 
interfaces you run hnet on as this will cause confusion or worse. hnet 
takes care of anything DHCP(v6).


From nobody Sun Feb 22 00:59:58 2015
Return-Path: <dave.taht@gmail.com>
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 622831A6F5D for <homenet@ietfa.amsl.com>; Sun, 22 Feb 2015 00:59:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.1
X-Spam-Level: 
X-Spam-Status: No, score=-0.1 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 zQLQNN2A2h_3 for <homenet@ietfa.amsl.com>; Sun, 22 Feb 2015 00:59:56 -0800 (PST)
Received: from mail-ob0-x232.google.com (mail-ob0-x232.google.com [IPv6:2607:f8b0:4003:c01::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 260471A1F20 for <homenet@ietf.org>; Sun, 22 Feb 2015 00:59:56 -0800 (PST)
Received: by mail-ob0-f178.google.com with SMTP id uz6so31549964obc.9 for <homenet@ietf.org>; Sun, 22 Feb 2015 00:59:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=EHfIid6So5zimYNM5Yvv04hCvgt4qL9u0268RkR5soo=; b=GG7wtpGh0pw1qxCIjXuq4KLtHg23a49H7Xzu4I412w4OjO695B0dZMkCXtU68iwXIg oqmYZF7gaQvSpwWOfjciZZliYXUk2rhbQ6XpmDmnXmqfcoC10Bjw4OZUoLCql97oEbEI cbPxaVhg6eYiTgRb11JwDacLzXqn0dFxBlMnVj8pDb6dv29si6HFJ9a0SsiXNZy1ZO8X 4n02jRiiS21ZQHatVecWhyfM2Ek2biEW2MrPvuPNR3C7kuLCRWhKr0eISHWdEo+vFI3v DByU7nM/8GUvKVh3I1P8QYLpNyPNPGteVsPsHyN9dSMpHRZOP59m5cnVG/jYnZdySIdP tokw==
MIME-Version: 1.0
X-Received: by 10.202.209.23 with SMTP id i23mr3619787oig.108.1424595595468; Sun, 22 Feb 2015 00:59:55 -0800 (PST)
Received: by 10.202.51.66 with HTTP; Sun, 22 Feb 2015 00:59:55 -0800 (PST)
In-Reply-To: <54E999E5.6060302@openwrt.org>
References: <CAA93jw7tb6E3cisKLWEpf6xOceakvE8LXeX98k_F-b2THKX+vw@mail.gmail.com> <3AE6E54C-1E8C-4D69-981C-E9AFE83A6894@fugue.com> <CAA93jw5g1gArQ2M8c9_tmHodvFovfm6nCWY9qW+MH87kM2yh-Q@mail.gmail.com> <54E990AA.7010402@openwrt.org> <CAA93jw5nPTA0WemT8Kgkp_1rj_ZGt05CV=5ypwECusCA_T6TZQ@mail.gmail.com> <54E99969.3080907@openwrt.org> <54E999E5.6060302@openwrt.org>
Date: Sun, 22 Feb 2015 00:59:55 -0800
Message-ID: <CAA93jw5ODoVdpgCWXKQwPJyLJv9ZLqHYgsmORKF_djbNV67gOw@mail.gmail.com>
From: Dave Taht <dave.taht@gmail.com>
To: Steven Barth <cyrus@openwrt.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/DdVJ4n9utteFlJp4VvgNSe6lWzQ>
Cc: Markus Stenberg <markus.stenberg@iki.fi>, Ted Lemon <mellon@fugue.com>, Ole Troan <otroan@employees.org>, Ralph Droms <rdroms.ietf@gmail.com>, "homenet@ietf.org Group" <homenet@ietf.org>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] HNCPD usability issues
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sun, 22 Feb 2015 08:59:57 -0000

A sample, correct, homenet enabled openwrt network file would be good
to show somewhere. I remain a bit confused about interfaces (which are
a hint to the firewall) and ifnames. It sounds like deleting the
lan/wan entries entirely is what you want?

And how do you retain static ipv4 assignment but just get ipv6 dynamically?

On Sun, Feb 22, 2015 at 12:57 AM, Steven Barth <cyrus@openwrt.org> wrote:
>
>>
>> If the original interface-name was "lan" or "wan" you should rename them
>> to something different (but do not need to change anything else).
>>
> Additional note:
> Do NOT run DHCP or DHCPv6 manually (either server or client) on interface=
s
> you run hnet on as this will cause confusion or worse. hnet takes care of
> anything DHCP(v6).



--=20
Dave T=C3=A4ht

thttp://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks


From nobody Sun Feb 22 01:22:26 2015
Return-Path: <cyrus@openwrt.org>
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 C408B1A0171 for <homenet@ietfa.amsl.com>; Sun, 22 Feb 2015 01:22:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.35
X-Spam-Level: 
X-Spam-Status: No, score=-0.35 tagged_above=-999 required=5 tests=[HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-0.7] 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 KfCRdTI-8X-c for <homenet@ietfa.amsl.com>; Sun, 22 Feb 2015 01:22:22 -0800 (PST)
Received: from mail.core-networks.de (mail.core-networks.de [82.96.72.7]) by ietfa.amsl.com (Postfix) with ESMTP id 129821A88C0 for <homenet@ietf.org>; Sun, 22 Feb 2015 01:20:04 -0800 (PST)
Received: from localhost ([127.0.0.1]) by mail.core-networks.de id 1YPShm-0002xU-E5 with ESMTPSA (TLSv1.2:DHE-RSA-AES256-SHA:256) for ; Sun, 22 Feb 2015 10:20:02 +0100
User-Agent: K-9 Mail for Android
In-Reply-To: <CAA93jw5ODoVdpgCWXKQwPJyLJv9ZLqHYgsmORKF_djbNV67gOw@mail.gmail.com>
References: <CAA93jw7tb6E3cisKLWEpf6xOceakvE8LXeX98k_F-b2THKX+vw@mail.gmail.com> <3AE6E54C-1E8C-4D69-981C-E9AFE83A6894@fugue.com> <CAA93jw5g1gArQ2M8c9_tmHodvFovfm6nCWY9qW+MH87kM2yh-Q@mail.gmail.com> <54E990AA.7010402@openwrt.org> <CAA93jw5nPTA0WemT8Kgkp_1rj_ZGt05CV=5ypwECusCA_T6TZQ@mail.gmail.com> <54E99969.3080907@openwrt.org> <54E999E5.6060302@openwrt.org> <CAA93jw5ODoVdpgCWXKQwPJyLJv9ZLqHYgsmORKF_djbNV67gOw@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset=UTF-8
From: Steven Barth <cyrus@openwrt.org>
Date: Sun, 22 Feb 2015 10:19:57 +0100
To: Dave Taht <dave.taht@gmail.com>
Message-ID: <4C3E7E03-71F7-4492-8C8D-F2F2F12503E5@openwrt.org>
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/VigQnmT0L7w_WzhF6FGRFRJGcpI>
Cc: Markus Stenberg <markus.stenberg@iki.fi>, Ted Lemon <mellon@fugue.com>, Ole Troan <otroan@employees.org>, Ralph Droms <rdroms.ietf@gmail.com>, "homenet@ietf.org Group" <homenet@ietf.org>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] HNCPD usability issues
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sun, 22 Feb 2015 09:22:23 -0000

>A sample, correct, homenet enabled openwrt network file would be good
>to show somewhere. I remain a bit confused about interfaces (which are
>a hint to the firewall) and ifnames. It sounds like deleting the
>lan/wan entries entirely is what you want?

Sort of.
A default network-config-file is not trivial since the config file contains the swich config, interface names etc.and this is pretty much different from device to device.


From nobody Sun Feb 22 01:29:52 2015
Return-Path: <dave.taht@gmail.com>
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 987EE1A1F20 for <homenet@ietfa.amsl.com>; Sun, 22 Feb 2015 01:29:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.1
X-Spam-Level: 
X-Spam-Status: No, score=-0.1 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 CLycCrE7z_Xp for <homenet@ietfa.amsl.com>; Sun, 22 Feb 2015 01:29:50 -0800 (PST)
Received: from mail-oi0-x22a.google.com (mail-oi0-x22a.google.com [IPv6:2607:f8b0:4003:c06::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6D3161A00B7 for <homenet@ietf.org>; Sun, 22 Feb 2015 01:29:50 -0800 (PST)
Received: by mail-oi0-f42.google.com with SMTP id h136so9216104oig.1 for <homenet@ietf.org>; Sun, 22 Feb 2015 01:29:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=oU7HXRbEdI4R7Eqwx0JponrFIVZjYFZRZZ59ykxMO7Y=; b=Hz3dj53+bUhOAmctcZdp4x1GXMSUJLX1ij12ed5wW658BPwynchz4XJEFWB8kBbYVs WCMYijAeKNWTt5ZKpPVzWgLMlmDjEx32Gnqe0qP4kQykcJiLI23ixgWZ+fOipHdgKgk0 9oGp9Qm4ZV1YbalTRcHzwd/Q4ZMJzjhZ9JqB7R/BLFxwBBOyV95z0yjgOCccmqklrDbn pxX2VPPFh3Hi7nyF8kBLBn97misMiygTD5hwRTJXl2dGh069f4enLv/QTu0WLNEElwEY coOGIig+qU9vzoSH4QFKnLN62ojgYMQE0Yq6w42/+JqZRe+k8UUt8LRCAsyajG0bNJFW hRqw==
MIME-Version: 1.0
X-Received: by 10.202.204.88 with SMTP id c85mr3705267oig.81.1424597389760; Sun, 22 Feb 2015 01:29:49 -0800 (PST)
Received: by 10.202.51.66 with HTTP; Sun, 22 Feb 2015 01:29:49 -0800 (PST)
In-Reply-To: <4C3E7E03-71F7-4492-8C8D-F2F2F12503E5@openwrt.org>
References: <CAA93jw7tb6E3cisKLWEpf6xOceakvE8LXeX98k_F-b2THKX+vw@mail.gmail.com> <3AE6E54C-1E8C-4D69-981C-E9AFE83A6894@fugue.com> <CAA93jw5g1gArQ2M8c9_tmHodvFovfm6nCWY9qW+MH87kM2yh-Q@mail.gmail.com> <54E990AA.7010402@openwrt.org> <CAA93jw5nPTA0WemT8Kgkp_1rj_ZGt05CV=5ypwECusCA_T6TZQ@mail.gmail.com> <54E99969.3080907@openwrt.org> <54E999E5.6060302@openwrt.org> <CAA93jw5ODoVdpgCWXKQwPJyLJv9ZLqHYgsmORKF_djbNV67gOw@mail.gmail.com> <4C3E7E03-71F7-4492-8C8D-F2F2F12503E5@openwrt.org>
Date: Sun, 22 Feb 2015 01:29:49 -0800
Message-ID: <CAA93jw6jmu+k4nPrwsmuJi1TVLZi-ajUkSxVRpEZ0uo8Mm099Q@mail.gmail.com>
From: Dave Taht <dave.taht@gmail.com>
To: Steven Barth <cyrus@openwrt.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/-l35QBSSaw81tBgy4Q6axxFnPCU>
Cc: Markus Stenberg <markus.stenberg@iki.fi>, Ted Lemon <mellon@fugue.com>, Ole Troan <otroan@employees.org>, Ralph Droms <rdroms.ietf@gmail.com>, "homenet@ietf.org Group" <homenet@ietf.org>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] HNCPD usability issues
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sun, 22 Feb 2015 09:29:51 -0000

On Sun, Feb 22, 2015 at 1:19 AM, Steven Barth <cyrus@openwrt.org> wrote:
>
>
>
>>A sample, correct, homenet enabled openwrt network file would be good
>>to show somewhere. I remain a bit confused about interfaces (which are
>>a hint to the firewall) and ifnames. It sounds like deleting the
>>lan/wan entries entirely is what you want?
>
> Sort of.
> A default network-config-file is not trivial since the config file contai=
ns the swich config, interface names etc.and this is pretty much different =
from device to device.

I will certainly argue that given the adoption and testing rate of
hnetd so far (roughly 0), that anything you can do to make it easier
on those interested in evaluating the work, would be nice. An example
for some of the more common platforms such as the wzr, tp-link, etc
would be good.

Getting the process down to:

get the firmware
flash the firmware via the web gui

opkg install hnet-full
cd /etc/config; wget somewhere/wndr3800/network
reboot; exit # bang you are now homenet enabled

might do wonders. It certainly would in my case. I have tried 5 times
now, multiple different ways, to get it to just work, over the last 6
months, now on both openwrt and debian. Admittedly in the former case,
with my pre-concieved notions as to how things already work for me on
both exterior and interior gateways.




--=20
Dave T=C3=A4ht

thttp://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks


From nobody Sun Feb 22 11:10:06 2015
Return-Path: <joelja@bogus.com>
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 DA4791A6EFC for <homenet@ietfa.amsl.com>; Sun, 22 Feb 2015 11:10:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 b5TaqUh6msaM for <homenet@ietfa.amsl.com>; Sun, 22 Feb 2015 11:09:59 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) (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 8271D1A6EF9 for <homenet@ietf.org>; Sun, 22 Feb 2015 11:09:59 -0800 (PST)
Received: from mb-aye.local ([IPv6:2601:9:3402:7bb1:4a5:16f:dbc8:c25]) (authenticated bits=0) by nagasaki.bogus.com (8.14.9/8.14.9) with ESMTP id t1MJ9tUH014712 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sun, 22 Feb 2015 19:09:56 GMT (envelope-from joelja@bogus.com)
Message-ID: <54EA1A55.5030207@bogus.com>
Date: Sun, 22 Feb 2015 10:05:09 -0800
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:36.0) Gecko/20100101 Thunderbird/36.0
MIME-Version: 1.0
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>, Mikael Abrahamsson <swmike@swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <54E58238.9030809@mtcc.com> <874mqigcct.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191622510.4007@uplift.swm.pp.se> <87vbixg9fe.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191806381.4007@uplift.swm.pp.se> <87lhjtg6jc.wl-jch@pps.univ-paris-diderot.fr>
In-Reply-To: <87lhjtg6jc.wl-jch@pps.univ-paris-diderot.fr>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="TWOnG5rvhghOMG001ePSIEM5k1JSEU3A7"
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/aUaJizJKecOanMMJDodJ_-UbaDM>
Cc: homenet@ietf.org
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sun, 22 Feb 2015 19:10:01 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--TWOnG5rvhghOMG001ePSIEM5k1JSEU3A7
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On 2/19/15 9:22 AM, Juliusz Chroboczek wrote:
>>> smart rate limiting.
>=20
>> ISIS already has these kinds of "rate-limiting" of how things are
>> happening. In modern core routers this is often tuned
>=20
> If you need to tune it, it's not smart enough.

To be fair, network operators have somewhat different priorities, e.g.
rapid convergence at the expense of cpu may be ok, no effective
bandwidth constraints when you're talking about an igp running on a gig
or 10 gig point-to-point link...


> -- Juliusz
>=20
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>=20



--TWOnG5rvhghOMG001ePSIEM5k1JSEU3A7
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAlTqGlUACgkQ8AA1q7Z/VrLJBgCfXvzu362uiF8DOqIS6q3bSZLh
aRgAn0MDSCcOCW1u8vxr8LBDONFI1qiW
=9ZiR
-----END PGP SIGNATURE-----

--TWOnG5rvhghOMG001ePSIEM5k1JSEU3A7--


From nobody Sun Feb 22 11:39:21 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 147841A1A32 for <homenet@ietfa.amsl.com>; Sun, 22 Feb 2015 11:39:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.15
X-Spam-Level: *
X-Spam-Status: No, score=1.15 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_EQ_FR=0.35] autolearn=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 t92VnEHks9q7 for <homenet@ietfa.amsl.com>; Sun, 22 Feb 2015 11:39:19 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 6C7871A0406 for <homenet@ietf.org>; Sun, 22 Feb 2015 11:39:19 -0800 (PST)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t1MJdELU031902; Sun, 22 Feb 2015 20:39:14 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id A19D72C2045; Sun, 22 Feb 2015 20:39:14 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id ropQfGgfYMLI; Sun, 22 Feb 2015 20:39:13 +0100 (CET)
Received: from pirx.pps.jussieu.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 05D5F2C2042; Sun, 22 Feb 2015 20:39:12 +0100 (CET)
Date: Sun, 22 Feb 2015 20:39:13 +0100
Message-ID: <87wq39buse.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: joel jaeggli <joelja@bogus.com>
In-Reply-To: <54EA1A55.5030207@bogus.com>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <54E58238.9030809@mtcc.com> <874mqigcct.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191622510.4007@uplift.swm.pp.se> <87vbixg9fe.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191806381.4007@uplift.swm.pp.se> <87lhjtg6jc.wl-jch@pps.univ-paris-diderot.fr> <54EA1A55.5030207@bogus.com>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Sun, 22 Feb 2015 20:39:14 +0100 (CET)
X-Miltered: at korolev with ID 54EA3062.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54EA3062.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54EA3062.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/J4rpeYSharAZmiuUg6Hf2pFKNOY>
Cc: homenet@ietf.org, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sun, 22 Feb 2015 19:39:21 -0000

>>> ISIS already has these kinds of "rate-limiting" of how things are
>>> happening. In modern core routers this is often tuned

>> If you need to tune it, it's not smart enough.

> To be fair, network operators have somewhat different priorities,

Yes, that was a cheap shot.  Sorry, I couldn't resist.

-- Juliusz


From nobody Sun Feb 22 18:57:50 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 213011A0130 for <homenet@ietfa.amsl.com>; Sun, 22 Feb 2015 18:57:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.15
X-Spam-Level: *
X-Spam-Status: No, score=1.15 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_EQ_FR=0.35] autolearn=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 QSaNNnMFV0Rk for <homenet@ietfa.amsl.com>; Sun, 22 Feb 2015 18:57:47 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 3FE581A0120 for <homenet@ietf.org>; Sun, 22 Feb 2015 18:57:47 -0800 (PST)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t1N2vj4E023992 for <homenet@ietf.org>; Mon, 23 Feb 2015 03:57:45 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 812F22C22CC for <homenet@ietf.org>; Mon, 23 Feb 2015 03:57:45 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id dL7sJ4zcwr0o for <homenet@ietf.org>; Mon, 23 Feb 2015 03:57:44 +0100 (CET)
Received: from pirx.pps.jussieu.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id EDDBD2C22C4 for <homenet@ietf.org>; Mon, 23 Feb 2015 03:57:42 +0100 (CET)
Date: Mon, 23 Feb 2015 03:57:42 +0100
Message-ID: <8761at9vx5.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: "homenet@ietf.org Group" <homenet@ietf.org>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Mon, 23 Feb 2015 03:57:45 +0100 (CET)
X-Miltered: at korolev with ID 54EA9729.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54EA9729.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54EA9729.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/riyXQgKO-wsOeMNzixvg59OBQT8>
Subject: [homenet] DNCP questions
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 23 Feb 2015 02:57:49 -0000

I have a few questions and comments about DNCP.  (I haven't finished
grokking HNCP yet, so that will have to wait.)


1. Fragmentation

The minimum MTU in IPv6 is 1280 bytes, and the minimum maximum packet size
(before fragmentation) is 1500 bytes.  This means that a Short Network
Status can carry information about 160 nodes or so, which is a little
tight for comfort.  Is there a fragmentation mechanism I've missed
somewhere?

Related to that -- what happens if you receive a Node Data Request, and
the reply doesn't fit in the MTU?  Are you allowed to split it into
multiple Node Data Replies?  If so, how do you know if you've received the
whole set?


2. Packet loss

What happens on packet loss?

  * what happens when the reply to a Node Data Request doesn't arrive?
    Are you supposed to resend the request?  With exponential or linear
    backoff, and with what constants?

  * is there a way to detect that a link exhibits packet loss?  There are
    no sequence numbers in state updates (there's the state seqno, but
    that's not incremented with each message), so you cannot easily find
    how many you've missed.

  * Are you allowed to do something special when you have new data to
    publish over a connection that exhibits packet loss?  For example
    keeping I at Imin for two or three updates?


3. Extensibility

What should I do if I receive an unknown TLV?  I assume I should silently
ignore it if it's inside a Data TLV, and include it in my database and
flood it if it's within a Data TLV, right?

Which messages are allowed to contain extra TLVs?  For example, what
should I do if I receive a Long Network State Update with a bunch of
unknown TLVs interleaved with the Node State TLVs?


4. Jitter

Am I missing something or you're not applying jitter to keepalives?


5. Connections

There's a single connection for all neighbours on a given interface,
right?  Why not call that an Interface, then?


6. Link-local addresses

You're assuming a link-local multicast group, right?  What about the
sender address and unicast packets?  What should I do if I receive a DHCP
message from a global address?  Discard it, right?


7. Neighbor graph

The notion of "neighbor graph" suddenly appears in Section 5.4.  It's
pretty obvious what you mean, but this should be precisely defined
somewhere.


-- Juliusz


From nobody Sun Feb 22 19:41:40 2015
Return-Path: <mcr@sandelman.ca>
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 DA3F61A0161 for <homenet@ietfa.amsl.com>; Sun, 22 Feb 2015 19:41:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.389
X-Spam-Level: *
X-Spam-Status: No, score=1.389 tagged_above=-999 required=5 tests=[BAYES_50=0.8, J_CHICKENPOX_16=0.6, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 Uuuakwvn9wMg for <homenet@ietfa.amsl.com>; Sun, 22 Feb 2015 19:41:36 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8F7F91A015F for <homenet@ietf.org>; Sun, 22 Feb 2015 19:41:36 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 44EDB2009E; Sun, 22 Feb 2015 22:49:42 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id 3F2AC63A21; Sun, 22 Feb 2015 22:41:35 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 2176D637F4; Sun, 22 Feb 2015 22:41:35 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Margaret Wasserman <margaretw42@gmail.com>
In-Reply-To: <D80DC12D-AFBA-45D1-9D19-E4D4B24961FA@gmail.com>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E0FB64.8010009@openwrt.org> <87k2ziritt.wl-jch@pps.univ-paris-diderot.fr> <D80DC12D-AFBA-45D1-9D19-E4D4B24961FA@gmail.com>
X-Mailer: MH-E 8.6; nmh 1.3-dev; GNU Emacs 24.4.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Sun, 22 Feb 2015 22:41:35 -0500
Message-ID: <755.1424662895@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/rJW8U4FFYtdAaAolScjOLurn86Q>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 23 Feb 2015 03:41:39 -0000

--=-=-=
Content-Type: text/plain


Margaret Wasserman <margaretw42@gmail.com> wrote:
    >> More generally, I think -01 puts undue stress on scaling and
    >> convergence speed.  Sections 3 and 4 can be summarised as "any
    >> reasonable routing protocol scales sufficiently well and converges
    >> sufficiently fast for the needs of Homenet".

    > The sections in the document started from a list of routing
    > features/properties that were discussed in the WG meeting.  There was
    > quite a bit of discussion of scaling.  In particular, there was a lot
    > of discussion of how these protocols will scale "on Wi-Fi".  I wasn't
    > entirely sure, during the meeting, what special requirements there are
    > for a routing protocol to scale well on Wi-Fi vs. other link types, but
    > perhaps someone on the WG mailing list can clarify?

Counter-intuitively for a broadcast media, multicast on wifi is very
expensive because not all stations can hear each other, and some stations
require higher power lower-speed transmissions.  So each time the AP
transmits a multicast packet, it transmits at the highest power, using the
slowest method.   Many high-end APs (like we use at IETF), will actually
deliver multicast via a series of L2 unicast messages.

What this means is that a protocol that depends upon multicast to achieve
flooding may perform very poorly over wifi compared to a protocol which forms
1:1 links associations.

Now, does this matter in the home: how many homenet capable routers do we
expect to create adjacencies over wifi?  I will claim that over time, if we
get this right, that it will be larger than what we see today in the home
(which is 1 to 3 APs), but it's on the order of
O(p + r):
       p=number of people in home,
       r=number of rooms.

So assuming some decent high-power 802.11ac in the Bradford house
(http://en.wikipedia.org/wiki/Eight_Is_Enough) to link the per-room router to
legacy 802.11b and per-person (phone) router to BTLE/PAN, it means we have
about 30 routers on the wifi.   How much multicast and how much unicast
traffic results?

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEVAwUBVOqhbICLcPvd0N1lAQIsGQgAwlLqYrxe9UqpNRsvTm/XawN9/53myT2M
G3f+H7supuiNfhINsX3iQQ4k//YZvw1AegyAodB8lUbBBwbwLD7cw/cpGvtShvKH
bx43kS+/REExy8zxXv2brcGphq4k1znKmnz7NVTPAZtSIgfa/u3/nEGUtxzV6DEs
k6sSKUY7NHS2JckN5I3yW1Lh3MT6TjXHD+xlqG3fSrrSYNSqF7osk2WMCoKZYpIn
MdygZ8WXkha/B9YMlMrShuF7ldi46M6Y75c2IRI7YYThYBIZtCaDfx/cd0Wnuviz
bMPwOuSiIbisA3btc0Lx2cWIgNfa18XDMlCxFuFL5ybGCWCLUjlWYA==
=QDmm
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Sun Feb 22 20:24:03 2015
Return-Path: <mcr@sandelman.ca>
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 04AF11A019B for <homenet@ietfa.amsl.com>; Sun, 22 Feb 2015 20:24:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.711
X-Spam-Level: 
X-Spam-Status: No, score=-0.711 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_42=0.6, J_CHICKENPOX_44=0.6, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 S1ZtUeCDvlGo for <homenet@ietfa.amsl.com>; Sun, 22 Feb 2015 20:24:01 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D781F1A0195 for <homenet@ietf.org>; Sun, 22 Feb 2015 20:24:00 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 5BF822009E for <homenet@ietf.org>; Sun, 22 Feb 2015 23:32:06 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id 3E8A063A21; Sun, 22 Feb 2015 23:23:59 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 269D3637F4 for <homenet@ietf.org>; Sun, 22 Feb 2015 23:23:59 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "homenet\@ietf.org Group" <homenet@ietf.org>
In-Reply-To: <87pp94czye.wl-jch@pps.univ-paris-diderot.fr>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E48963.5030109@globis.net> <874mqj715b.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502181649530.4007@uplift.swm.pp.se> <87d2575hay.wl-jch@pps.univ-paris-diderot.fr> <CAGhGL2COvZV4V6y18jrKsabqG4Uoc8o1ZzaSnP=2VVCp-Tfdtw@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <A5767F83-3D0C-40E5-A73B-912E3C160A42@fugue.com> <alpine.DEB.2.02.1502191235240.4007@uplift.swm.pp.se> <87zj89gaqm.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191804050.4007@uplift.swm.pp.se> <D10B8924.6BD5%John_Leddy@cable.comcast.com> <87h9uhg529.wl-jch@pps.univ-paris-diderot.fr> <87fva1fzwp.wl-jch@pps.univ-paris-diderot.fr> <CAA93jw57sNMPsKkL-W2m3s20DKsFZWNeGZSOgnmRTj3yz+Rgmg@mail.gmail.com> <EA20D83F-3E46-4484-AD65-518B1C3836DA@inf-net.nl> <87zj89ed6c.wl-jch@pps.univ-paris-diderot.fr> <86026D9A-78BB-4E5B-A6AA-27FB2E02441F@inf-ne t.nl> <CAGnRvuobcSA1wP__rscE+UAMAuxEgOqML5Ute1qcFLSHh+kLng@mail.gmail.com> <FA70CC1E-37E4-4824-A9F3-9711F1F84777@inf-net.nl> <CAGnRvuqUSXpTPCqG4fsNHA=tsge=FvUUXuouwoVsRy1Cw3-cug@mail.gmail.com> <87pp94czye.wl-jch@pps.univ-paris-diderot.fr>
X-Mailer: MH-E 8.6; nmh 1.3-dev; GNU Emacs 24.4.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Sun, 22 Feb 2015 23:23:59 -0500
Message-ID: <9756.1424665439@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/gUXRsoCPd7rfLnvyNWybMpz7wlw>
Subject: Re: [homenet] More about marginal links [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 23 Feb 2015 04:24:02 -0000

--=-=-=
Content-Type: text/plain


Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr> wrote:
    >> If you have hardware with a built-in switch that can report the link-speed,

    > The WNDR3700v2 under OpenWRT appears to do so:

    > # swconfig dev switch0 show | grep 'link:'
    > link: port:0 link:down
    > link: port:1 link:down
    > link: port:2 link:up speed:100baseT full-duplex
    > link: port:3 link:down
    > link: port:4 link:down
    > link: port:5 link:up speed:1000baseT full-duplex txflow rxflow auto

    > but to use this information, you need to know:

    > 1. that vlan1 on eth0 is connected to ports 0 through 3 of switch0;
    > 2. that neighbour fe80::dead:beef is connected over port 2.

    > You could do (1) with a small amount of model-specific code (yuck), but
    > I have no idea how to do (2).  Consult the ND cache to find out the
    > neighbour's MAC, then find a way to snoop on the switch's forwarding table?

And assuming that you could do this, you still don't know that
fe80::dead:beef isn't connected via some *other* layer-2 switch external to
the WRT.

So, if anyone is basing their convergence time summaries upon loss of link,
vs keep-alive timeouts, then they need to recalculate, because we are only
rarely gonna see link-down.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEVAwUBVOqrXICLcPvd0N1lAQIgqQf7BpknibEA2NbpSEMN5G56ZJny7f+i6Tn6
DdPlebe4gA7ta3zQK76Tt3IclJePLieEBrnClWm2QfDlF7hPeaG/VbdaENhYSOOt
FGkR2o4t+74w8j93yfPiUO9luJ2MApszHl7lItAISQ6JglrcE8zuJvhZkZdDF6O9
cOext+54VoW+82XID5wb3kHWl/Ivt5jAIPHNxj+UziC/bJld1k1ur4IYVlorBnpl
Y1X1wku52jANv4TF4Et5VyWePXMrq/RMe3Y4z4X801zZiQUmLwF+tFNP9XzjYBcV
q2dN0JmfejUeCjWdgqUfnoql03+eVVVFyRnPMGzl6xIdMv5acy3uCw==
=MKmJ
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Sun Feb 22 20:45:01 2015
Return-Path: <mcr@sandelman.ca>
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 7507F1A0195 for <homenet@ietfa.amsl.com>; Sun, 22 Feb 2015 20:44:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.789
X-Spam-Level: 
X-Spam-Status: No, score=0.789 tagged_above=-999 required=5 tests=[BAYES_50=0.8, 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 RBpR2IuU6yVB for <homenet@ietfa.amsl.com>; Sun, 22 Feb 2015 20:44:57 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E11411A0167 for <homenet@ietf.org>; Sun, 22 Feb 2015 20:44:56 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 57863203B7 for <homenet@ietf.org>; Sun, 22 Feb 2015 23:53:03 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id 24D6963A21; Sun, 22 Feb 2015 23:44:56 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 139A4637F4 for <homenet@ietf.org>; Sun, 22 Feb 2015 23:44:56 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "homenet\@ietf.org Group" <homenet@ietf.org>
In-Reply-To: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com>
X-Mailer: MH-E 8.6; nmh 1.3-dev; GNU Emacs 24.4.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Sun, 22 Feb 2015 23:44:56 -0500
Message-ID: <14065.1424666696@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/PxvIOaczQzm9ZWaKIFGejuCjSGI>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 23 Feb 2015 04:44:59 -0000

--=-=-=
Content-Type: text/plain


{my comments before reading the ~170 messages on this thread.}

comparison>   [Isn't it also the case that the HOMENET routing protocol will
comparison>   be implemented on lower-end embedded devices, such as nodes in
comparison>   a low-power wireless network?  What is considered to be a
comparison>   reasonable low-end system requirement for a HOMENET router? --
comparison>   mrw]

As specified in the architecture document, section 3.5.1:

rfc7368>   In this homenet architecture, LLNs and other specialised networks
rfc7368> are considered stub areas of the homenet and are thus not expected
rfc7368> to act as a transit for traffic between more traditional media.

So the gateway machine (the 6LBR) will run the HOMENET routing protocol and
the LLN routing protocol (RPL, or some other mesh-under protocol), but the
HOMENET routing protocol will never be run by the sensors.

The section 9, security consideration does indeed miss the mark.
Given that HNCP/DNCP would take care of "higher" identity and authorization
operations, and would produce some set of anchored credentials for the
routing protocols. the security question is not:
        does the protocol support HMAC-FOOBAR.

The questions are rather:
    1) how does the cost and convergence of the protocol change if security
       considerations force the use of (secured 1:1) unicast for all messages
       rather than multicast?

    2) does the protocol include an asymetric method for authentication?

We know that multicast is hard to secure using symetric methods as all
parties involved can impersonate any other party.   To what extent this is a
concern in homenet is not yet known, but on the other hand, in every
risk/cost/benefit analysis, if the cost of securing things is low enough,
it may make no sense not to...

In section 10, it is useful to know if multicast is supported; it is telling
that nobody has implemented multicast routing in ISIS.  It would be
interesting to know how successful multicast routing is in other Link State
and Distance Vector protocols are.  (Can Babel just include DVMRP for
instance?   Why did nobody implement multicast for ISIS?)

A question which I did not see addressed is about debugging.
How easily can one (perhaps more capable, or having better management
interface) router give diagnostics about problems that might be occuring
elsewhere in the homenet?
Can one deal with broken/mis-having peer routers in a unilateral fashion?
(Consider the ability for parents to mitigate a dispute among technically
astute teenagers, while keeping both online)
Can one get diagnostics from just watching the traffic?
As much as we expect the network to be auto-tuning and auto-configuring and
self-healing; if people do get involved, which one is easier to understand?

{my comments after reading the thread}

Important things that I took out of the discussion:

1) Source address specific routing likely doesn't exist in some hardware.
   My response is mostly: we often no idea what hardware can due to NDAs.
   The movement (see netdev01.org conference this past week) is towards
   having hardware which just lives under the linux kernel and its
   configuration is transparent to "userspace"

2) Layer-2 aspect of ISIS.
> We didn't discuss the fact that Babel runs over UDP, while IS-IS runs
> directly over layer 2.  This has a number of consequences, most notably
> related to ease of implementation, portability, and the ability to run
> over tunnels (say, GRE or OpenVPN in tun mode).

It also, btw, makes it unable to run over 15.4, since there is no ethernet
type.  6lo also has been defining ways to run IPv6/6lowPAN over other media
that have never seen IPv6.  Probably doesn't matter as long as these are
really *LLNs*, but it could be that some of these technologies (802.15.4g has
much bigger packet sizes...) get used in new and unanticipated ways in the
IPv6 is dominant future.

3) metrics.
   We don't know how we will assign link metrics, so we don't know how important
   X-bit metrics are.

4) convergence over 802.11 MAC...

5) some amount of "my processor is slower than yours and still ran protocol XYZ"
   (http://www.phespirit.info/montypython/four_yorkshiremen.htm)

6) discussion about multicast: do we even need it. With responses from
   "nobody does it" to "we have 10^X customers" right now.

7) one comment was: "we need topology, so babel won't work for us."

8) some conversation about whether or not one can get link state for a wired
   connection.  I don't see that it matters: there could always be another
   $9 layer-2 switch between the two routers. That's the problem with
   layer-2 switching, we can't see it.

9) then there was a discussion of multiple (wifi) APs, how to either L2-mesh them to
   accomplish mobility, or to do L3-roaming by having stub versions of
   homenet routing protocol and/or RIP.

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        | network architect  [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [

















--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEVAwUBVOqwQYCLcPvd0N1lAQIuSAf/TUY3ppf5N42CGvxgN7YyOV7V+iIFs1d2
XoAz7b9y+oMbMW7zTIFDAP+7AMNEUWse+ylcsjJEPTKQviIiE6k7P4VQrLCdH8jS
uUaeIDuVHSxYS2vvYAXlqatMerVdYnHXFlNalsij2WccBJly8zATpQcIQ9ObqPPE
1Ij0B2uY8/UTML0C7mxpEjL5PSEsxRQezHcgfqAOnDbipYKEpZ3L41FH2GSJIlJp
AU5xfD6DZzKFc4rgO4c4LlKkCj2C7Wv4R756CY+ZkCWW/nXvCRiUcQ+1H/nHnCaI
4s5y4brPnMJL+zj8KteTH0ALQi+Vws0QPu8YQu2WQdzTmvln02aCTA==
=gYjW
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Mon Feb 23 01:00:33 2015
Return-Path: <Ray.Bellis@nominet.org.uk>
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 C26F41A038B for <homenet@ietfa.amsl.com>; Mon, 23 Feb 2015 01:00:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.91
X-Spam-Level: 
X-Spam-Status: No, score=-2.91 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, 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 iH5wZFjP2q49 for <homenet@ietfa.amsl.com>; Mon, 23 Feb 2015 01:00:30 -0800 (PST)
Received: from mx2.nominet.org.uk (mx2.nominet.org.uk [213.248.242.49]) by ietfa.amsl.com (Postfix) with ESMTP id CC3761A0358 for <homenet@ietf.org>; Mon, 23 Feb 2015 01:00:28 -0800 (PST)
DomainKey-Signature: s=main2.dk.nominet.selector; d=nominet.org.uk; c=nofws; q=dns;  h=X-IronPort-AV:X-IPAS-Result:Received:Received:From:To: Subject:Thread-Topic:Thread-Index:Date:Message-ID: Accept-Language:Content-Language:X-MS-Has-Attach: X-MS-TNEF-Correlator:x-originating-ip:Content-Type: Content-ID:Content-Transfer-Encoding:MIME-Version; b=SzDWEgt2EZ0kp+qupnNSKAvlDhRQMOwu9+g7CGRqEZ14+tqNwyWLfUrj vooSYcRUZJMRsh6t0LnBUklC/cQWTklKmXSYsl+VVe2MB6Uqircs50Qtz 1UQ/ti4p5t8CFiqI9uzfPjHcsPzhOsG6hnfxgTBZHTNug/YJRPA7HGCIR 0Z8gU96YdgrglRZNSP4RQRJXEQjtal2yQiO39XFjpXU1fT3JB8jeh+bDE 624OktyUR3TtF7QH1x65Q56/tu4vu;
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nominet.org.uk; i=@nominet.org.uk; q=dns/txt; s=main2.dkim.nominet.selector; t=1424682030; x=1456218030; h=from:to:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=IxwIm7RJDVa/Y0w4xv+/F6y+ckl13tSM/F9ihDqMpgk=; b=fmqEOMMRHfvqZ3TLKP+edQlbEyvo1jn12uxiW/K5/oXvaih//HyNhXL3 q8wvXyvvY2ClQlTfBZ6bRFWTpUoPXDEy/LqRkPu/mj7Bvgd08HoZesAoY RhMXagBCe02bbtR6Twu6M9Oyds/nLOLC8JsUI3rqtBbD06uEKXSdABO4t RM7YSvs2KOQ9utqJ48YlQycY9HLIa/qu2r61zjRmAxBiIuMgHfxRnA172 ho2WmZG0pZqrv0bO3D4mX8Byse4vc;
X-IronPort-AV: E=Sophos;i="5.09,629,1418083200"; d="scan'208";a="16080899"
X-IPAS-Result: A2DbBQCH6+pU/5HF+NVbgmQiAYETHLQmAY5chyNDAQEBAQEBfIQWOhk4AT5CJwSIQwOrHKdQAQEBHoxQAYZOgRQFrEgigg+BX4IzfwEBAQ
Received: from wds-exc2.okna.nominet.org.uk ([213.248.197.145]) by mx2.nominet.org.uk with ESMTP; 23 Feb 2015 09:00:27 +0000
Received: from WDS-EXC1.okna.nominet.org.uk ([fe80::1593:1394:a91f:8f5f]) by wds-exc2.okna.nominet.org.uk ([fe80::7577:eaca:5241:25d4%16]) with mapi id 14.03.0181.006; Mon, 23 Feb 2015 09:00:26 +0000
From: Ray Bellis <Ray.Bellis@nominet.org.uk>
To: "homenet@ietf.org Group" <homenet@ietf.org>
Thread-Topic: Draft submission deadline
Thread-Index: AQHQT0cpfh/5BzcsJUCJS6IqVv6D6w==
Date: Mon, 23 Feb 2015 09:00:24 +0000
Message-ID: <BECAF67C-1DB7-43BE-A8A2-D229C240EF4C@nominet.org.uk>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.2.1]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <AF405D0BDE1ABD41964364B63B70A5E4@okna.nominet.org.uk>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/Nc_qzbEFvK9PdUKxX1C6FuHUMeE>
Subject: [homenet] Draft submission deadline
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 23 Feb 2015 09:00:31 -0000

Just a quick reminder to the WG that the submission cut-off date for Intern=
et Drafts is two weeks today, at 23:59 UTC on March 9th.

Ray


From nobody Mon Feb 23 02:01:02 2015
Return-Path: <markus.stenberg@iki.fi>
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 EC3AA1A038E for <homenet@ietfa.amsl.com>; Mon, 23 Feb 2015 02:01:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.778
X-Spam-Level: 
X-Spam-Status: No, score=0.778 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_NEUTRAL=0.779] autolearn=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 onYaOE0spTlN for <homenet@ietfa.amsl.com>; Mon, 23 Feb 2015 02:00:58 -0800 (PST)
Received: from kirsi1.inet.fi (mta-out1.inet.fi [62.71.2.195]) by ietfa.amsl.com (Postfix) with ESMTP id 5CEC51A0019 for <homenet@ietf.org>; Mon, 23 Feb 2015 02:00:58 -0800 (PST)
Received: from poro.lan (80.220.64.126) by kirsi1.inet.fi (8.5.142.08) (authenticated as stenma-47) id 54E3C71100A91875; Mon, 23 Feb 2015 12:00:53 +0200
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Markus Stenberg <markus.stenberg@iki.fi>
In-Reply-To: <8761at9vx5.wl-jch@pps.univ-paris-diderot.fr>
Date: Mon, 23 Feb 2015 12:00:54 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <7D8C2976-1649-4349-9E90-E24DD2848086@iki.fi>
References: <8761at9vx5.wl-jch@pps.univ-paris-diderot.fr>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/iOLvUNaMAuVLHAYdFkyBYcy8H7s>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Markus Stenberg <markus.stenberg@iki.fi>
Subject: Re: [homenet] DNCP questions
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 23 Feb 2015 10:01:01 -0000

On 23.2.2015, at 4.57, Juliusz Chroboczek =
<jch@pps.univ-paris-diderot.fr> wrote:
> I have a few questions and comments about DNCP.  (I haven't finished
> grokking HNCP yet, so that will have to wait.)

Thanks, we definitely need more eyes on this (keepalive logic was =
actually flawed in -00, but I dare you to find it without looking at our =
git repo on drafts :>).

> 1. Fragmentation
>=20
> The minimum MTU in IPv6 is 1280 bytes, and the minimum maximum packet =
size
> (before fragmentation) is 1500 bytes.  This means that a Short Network
> Status can carry information about 160 nodes or so, which is a little
> tight for comfort.  Is there a fragmentation mechanism I've missed
> somewhere?

I assume you refer to Long Network Status (on multicast); post MTU, or =
in secure mode, it should just use the Short one (which is of fixed =
length).=20
The network state TLV used in the short one is just one hash of (ordered =
sequence of) hashes of all nodes on the network.

The Long is just opportunistic scheme to enable clients to do immediate =
requests for node data, instead of unicast exchange, if network is small =
enough and not in secure mode.

> Related to that -- what happens if you receive a Node Data Request, =
and
> the reply doesn't fit in the MTU?  Are you allowed to split it into
> multiple Node Data Replies?  If so, how do you know if you've received =
the
> whole set?

The assumption currently is that replies are always unicast, and the =
IPv6 fragmentation works on local link. Current assumption is that sane =
set of node data fits inside one (potentially fragmented) IPv6 packet =
(non-jumbogram), essentially limiting the maximum size to <64kb.

(If we hit that size limit, I would rather advocate some sort of node =
data delta transmission protocol in any case.)

> 2. Packet loss
>=20
> What happens on packet loss?
>=20
>  * what happens when the reply to a Node Data Request doesn't arrive?
>    Are you supposed to resend the request?  With exponential or linear
>    backoff, and with what constants?

Nothing happens. You wait for the event that caused the original request =
to happen again (essentially, Trickle ensures that everyone hears of an =
update =E2=80=98few=E2=80=99 times before it backs off down to =
relatively long value.)

>  * is there a way to detect that a link exhibits packet loss?  There =
are
>    no sequence numbers in state updates (there's the state seqno, but
>    that's not incremented with each message), so you cannot easily =
find
>    how many you=E2=80=99ve missed.

Nope.

>  * Are you allowed to do something special when you have new data to
>    publish over a connection that exhibits packet loss?  For example
>    keeping I at Imin for two or three updates?

Not in the current spec; the whole thing is =E2=80=98best-effort=E2=80=99 =
and _intentionally_ much slower than it could be. e.g. initial =
transmission is caused by Trickle, and not immediately, always; a lot of =
routing protocols for example send immediately (at least in some cases), =
but current aim is for =E2=80=9Csufficient=E2=80=9D speed of the state =
sync and processing/bandwidth conservation than raw speed.

As Trickle parameters used are local implementation choice, I _suppose_ =
we could actually mandate just a Trickle-like sending algorithm, with =
default recommendation being Trickle, but it gets complex in writing if =
not in implementation :) Pull requests welcome though.

> 3. Extensibility
>=20
> What should I do if I receive an unknown TLV?  I assume I should =
silently
> ignore it if it's inside a Data TLV, and include it in my database and
> flood it if it=E2=80=99s within a Data TLV, right?

Right. Almost all of node data is essentially opaque to the DNCP base =
protocol, with the few noted exceptions.

> Which messages are allowed to contain extra TLVs?  For example, what
> should I do if I receive a Long Network State Update with a bunch of
> unknown TLVs interleaved with the Node State TLVs?

Any of them. The messages are defined just by the MUST be present TLVs.=20=


However, interesting question is, what if the received payload matches =
multiple messages? Current text=20


> 4. Jitter
>=20
> Am I missing something or you=E2=80=99re not applying jitter to =
keepalives?

That is a good point; we will address that in -01. (Similarly to what we =
do to replies to multicast messages; just [0, Imin/2] SHOULD delay.)

> 5. Connections
>=20
> There's a single connection for all neighbours on a given interface,
> right?  Why not call that an Interface, then?

In case of HNCP, this is true, as it has connection=3D(link-local IPv6 =
UDP-using) interface. In DNCP, a connection may be just e.g. one unicast =
endpoint you want to talk with over the internet.

> 6. Link-local addresses
>=20
> You're assuming a link-local multicast group, right?  What about the
> sender address and unicast packets?  What should I do if I receive a =
DHCP
> message from a global address?  Discard it, right?

This is specified in HNCP as it is the one with link-local address =
binding. DNCP can be also used with globals so I do not think the =
limitation fits there (although obviously the profile will probably want =
to limit global use to secure mode).

> 7. Neighbor graph
>=20
> The notion of "neighbor graph" suddenly appears in Section 5.4.  It's
> pretty obvious what you mean, but this should be precisely defined
> somewhere.


The later traversing definition more or less describes what it =E2=80=98is=
=E2=80=99; any idea of what a good definition would look like?

Cheers,

-Markus=


From nobody Mon Feb 23 05:17:24 2015
Return-Path: <otroan@employees.org>
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 BE3451A1AAA for <homenet@ietfa.amsl.com>; Mon, 23 Feb 2015 05:17:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.011
X-Spam-Level: 
X-Spam-Status: No, score=-2.011 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 WbSpVEYRNESk for <homenet@ietfa.amsl.com>; Mon, 23 Feb 2015 05:17:09 -0800 (PST)
Received: from banjo.employees.org (banjo.employees.org [198.137.202.19]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1B8061A1AA5 for <homenet@ietf.org>; Mon, 23 Feb 2015 05:17:06 -0800 (PST)
Received: from banjo.employees.org (localhost [127.0.0.1]) by banjo.employees.org (Postfix) with ESMTP id B30CB61F7; Mon, 23 Feb 2015 05:17:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; s=selector1; bh=JN80o+Mk4t6+Ig+mxEY6ZWd2U74=; b= aBuP58G8qw1AgO97bYNBKl2TOTINn45lPqpwCPKTIezQ2LaAD8MSXRTvTnQCdrDs FZ5FOIuFbiLI2fcvyN6FnqTViKsmyRSKhR93Z+JAGAe1cuKhG3lo1pKBwOB/FdwP c646S+ZLh6foAq6Xz3+qCMS779bZFlVbODJpHVHzcOE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; q=dns; s=selector1; b=Zf4JkMUGVc6ln2SFQtlhopz9t6 OG4TlBIGpdEjuEpSQBPjLl/q+J4wVDZ5YsqtEvQ626MQGEQwoNPldW1vp7gp8aym H7wLgEKnFhNa7cHxTP0DGnAu/kqwiiOPFhZW84GMhfioz510J4wzQHJ0/ouyTubF rfPzqYZAu+3YwWIXY=
Received: from gomlefisk.localdomain (173-38-208-169.cisco.com [173.38.208.169]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id 669A061EC; Mon, 23 Feb 2015 05:17:04 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by gomlefisk.localdomain (Postfix) with ESMTP id 2435F3F3480A; Mon, 23 Feb 2015 14:17:02 +0100 (CET)
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_8ACBF559-7D72-4FD8-849B-9A21F3EDB591"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.5b5
From: Ole Troan <otroan@employees.org>
In-Reply-To: <87wq3bi9rz.wl-jch@pps.univ-paris-diderot.fr>
Date: Mon, 23 Feb 2015 14:17:01 +0100
Message-Id: <99C39872-38E3-463F-B133-5577E484596C@employees.org>
References: <8B98F698-983D-4D2A-B5D1-7ACED27C275E@fugue.com> <alpine.DEB.2.02.1502191920560.4007@uplift.swm.pp.se> <CAPRuP3mpNJTu6mP+RAVKKO0kt60PogNtNbCUCRRqxe9im3EzjA@mail.gmail.com> <alpine.DEB.2.02.1502201042330.4007@uplift.swm.pp.se> <7A86BDC6-FF4B-49FF-B59C-BA1DEF463173@inf-net.nl> <alpine.DEB.2.02.1502201310050.4007@uplift.swm.pp.se> <09793905-8D12-49E0-A040-490F617C87FF@inf-net.nl> <alpine.DEB.2.02.1502201410510.4007@uplift.swm.pp.se> <82E892D5-98C3-4DD8-9E78-A754D77A5AF6@employees.org> <alpine.DEB.2.02.1502201455500.4007@uplift.swm.pp.se> <20150220224225.GH8096@cisco.com> <alpine.DEB.2.02.1502210658230.4007@uplift.swm.pp.se> <871tljjphw.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502211544510.4007@uplift.swm.pp.se> <87wq3bi9rz.wl-jch@pps.univ-paris-diderot.fr>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/MqWeJicjUNObHHRq_BSXF9CkfKU>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] Roaming hosts [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 23 Feb 2015 13:17:16 -0000

--Apple-Mail=_8ACBF559-7D72-4FD8-849B-9A21F3EDB591
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


> On 21 Feb 2015, at 16:06 , Juliusz Chroboczek =
<jch@pps.univ-paris-diderot.fr> wrote:
>=20
>>> The client is running a stub implementation of the routing protocol.
>=20
>> I thought we already had decided we didn't require changes to the =
host?
>=20
> We don't *require* changes to the host.  We propose optional host
> modifications that improve the user experience.

exactly.
you aren't going to have much fun with multi-prefix multi-homing without =
host changes anyhow.

> The chairs will correct me if I'm wrong, but I believe this is =
consistent
> with Homenet's charter.

cheers,
Ole



--Apple-Mail=_8ACBF559-7D72-4FD8-849B-9A21F3EDB591
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJU6yhNAAoJEFuJXizso86gPAkIAIzk/zQlfgchOTXMaiagwnZL
d6Vim8SY+FSzquBmey78Xrv8z3QYP/sv3vtlJ+imSF1p1lnwKnKVBXvZAuKbVFrX
TQD5PnWbTyKrSZSUYIvx6t2lm+EooecsH7Z5Is7AYPUWfWbsUBHJ3AaEisQXjHQ4
HKK1b7ooDPi7XCovukvlekvV4eLEjZ08Gx9QKNn1/Cf0tHGZ7z4rE+lNGrTDVPSl
liI3ERZVfIghk7bULNIJgd3WlWqMg/n4WvCIHGORUXHDjYbdooDgU8NLl7pxDe5z
n9cyO0oTk4aVRWXzOtXIa0Mbaoj+YGbO9eR6/UCpu6qAqed/o96wsU16Zk5Bu5g=
=Xv4V
-----END PGP SIGNATURE-----

--Apple-Mail=_8ACBF559-7D72-4FD8-849B-9A21F3EDB591--


From nobody Mon Feb 23 05:20:49 2015
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 3FD831A1AC7 for <homenet@ietfa.amsl.com>; Mon, 23 Feb 2015 05:20:48 -0800 (PST)
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 wfrv_Z3JQ23M for <homenet@ietfa.amsl.com>; Mon, 23 Feb 2015 05:20:46 -0800 (PST)
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 8A2121A1AAD for <homenet@ietf.org>; Mon, 23 Feb 2015 05:20:46 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 96350A2; Mon, 23 Feb 2015 14:20:33 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1424697633; bh=d1qCO5GmwHLnK2vEssu4fWlpqKj0O9wgwySdQ1R2laM=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=HDCta+I3d5x1yuucMw053O3E9ZzjgtCwKxFL4ipiaXQSyqk5+mA8ZreCxVUlHkYml vaVgIddbycx7pWsgEl7UirW697DfPV5WyVjlwZe8x0DrFeU8Gkfbg3mIoooywBFjop uB70j5Fllzfa39QnXe7R1uiB8lgrIt7Bw46+P67k=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 914F1A1; Mon, 23 Feb 2015 14:20:33 +0100 (CET)
Date: Mon, 23 Feb 2015 14:20:33 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Ole Troan <otroan@employees.org>
In-Reply-To: <99C39872-38E3-463F-B133-5577E484596C@employees.org>
Message-ID: <alpine.DEB.2.02.1502231418590.4007@uplift.swm.pp.se>
References: <8B98F698-983D-4D2A-B5D1-7ACED27C275E@fugue.com> <alpine.DEB.2.02.1502191920560.4007@uplift.swm.pp.se> <CAPRuP3mpNJTu6mP+RAVKKO0kt60PogNtNbCUCRRqxe9im3EzjA@mail.gmail.com> <alpine.DEB.2.02.1502201042330.4007@uplift.swm.pp.se> <7A86BDC6-FF4B-49FF-B59C-BA1DEF463173@inf-net.nl> <alpine.DEB.2.02.1502201310050.4007@uplift.swm.pp.se> <09793905-8D12-49E0-A040-490F617C87FF@inf-net.nl> <alpine.DEB.2.02.1502201410510.4007@uplift.swm.pp.se> <82E892D5-98C3-4DD8-9E78-A754D77A5AF6@employees.org> <alpine.DEB.2.02.1502201455500.4007@uplift.swm.pp.se> <20150220224225.GH8096@cisco.com> <alpine.DEB.2.02.1502210658230.4007@uplift.swm.pp.se> <871tljjphw.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502211544510.4007@uplift.swm.pp.se> <87wq3bi9rz.wl-jch@pps.univ-paris-diderot.fr> <99C39872-38E3-463F-B133-5577E484596C@employees.org>
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/FJUEWXfO5gOp8dB2NV7vseq2SLI>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] Roaming hosts [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 23 Feb 2015 13:20:48 -0000

On Mon, 23 Feb 2015, Ole Troan wrote:

>
>> On 21 Feb 2015, at 16:06 , Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr> wrote:
>>
>>>> The client is running a stub implementation of the routing protocol.
>>
>>> I thought we already had decided we didn't require changes to the host?
>>
>> We don't *require* changes to the host.  We propose optional host
>> modifications that improve the user experience.
>
> exactly.
> you aren't going to have much fun with multi-prefix multi-homing without host changes anyhow.

Let me get this straight: So the proposal is that end systems will have to 
change their IPv6 address when it moves between wifi APs if it's a current 
end system, and in order to keep its address, it needs to start to speak 
HNCP?

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


From nobody Mon Feb 23 05:39:42 2015
Return-Path: <otroan@employees.org>
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 4812D1A1B8F for <homenet@ietfa.amsl.com>; Mon, 23 Feb 2015 05:39:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.011
X-Spam-Level: 
X-Spam-Status: No, score=-2.011 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 gkqnbH3ijTMV for <homenet@ietfa.amsl.com>; Mon, 23 Feb 2015 05:39:40 -0800 (PST)
Received: from banjo.employees.org (banjo.employees.org [IPv6:2001:1868:205::19]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 83C591A1B9E for <homenet@ietf.org>; Mon, 23 Feb 2015 05:39:38 -0800 (PST)
Received: from banjo.employees.org (localhost [127.0.0.1]) by banjo.employees.org (Postfix) with ESMTP id 9221B62AC; Mon, 23 Feb 2015 05:39:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; s=selector1; bh=K+ln6p+ywf/xKMp87G2jO8wLP6k=; b= gl6xnLPXvWwsrU1mQY8wCvMFqxmNkFzU1g9/eQgN4pjcW5Q67wEeHjxaCu9ylix9 gt2NYyN1bzEdJknBEy0MQNRCcB8b/pCHV0WD2O3b7RbfBjV3SdtNDVibgqAbas9Z nkIkv2TiUwRk/VOPSh+muUwdsNNYXq62kI0eVTlNtnM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=employees.org; h=subject :mime-version:content-type:from:in-reply-to:date:cc:message-id :references:to; q=dns; s=selector1; b=Twk6sY6lafUm09Cd8wQnG65hf9 mmD5U71BYmdjAbD/65tVo8fHiYoJ6GF3GybuBjOYMvb9t+/tXk18sw0Pn/ny4ASX s60D0TAZ1eoPzLVh/rQ9TLqTw0J9z8oRSITq8qBX7kxe6uzYpIPOcKNs83I0D8FB raFJSmOuoG7ZdjOa0=
Received: from gomlefisk.localdomain (173-38-208-169.cisco.com [173.38.208.169]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id 44ECC62A8; Mon, 23 Feb 2015 05:39:37 -0800 (PST)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by gomlefisk.localdomain (Postfix) with ESMTP id F3FDB3F350BA; Mon, 23 Feb 2015 14:39:34 +0100 (CET)
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_CD554062-33D5-4297-BD8C-F1E989BDE3CB"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail 2.5b5
From: Ole Troan <otroan@employees.org>
In-Reply-To: <alpine.DEB.2.02.1502231418590.4007@uplift.swm.pp.se>
Date: Mon, 23 Feb 2015 14:39:34 +0100
Message-Id: <57E592DD-0BDD-4271-B99F-6A3A174F4EB7@employees.org>
References: <8B98F698-983D-4D2A-B5D1-7ACED27C275E@fugue.com> <alpine.DEB.2.02.1502191920560.4007@uplift.swm.pp.se> <CAPRuP3mpNJTu6mP+RAVKKO0kt60PogNtNbCUCRRqxe9im3EzjA@mail.gmail.com> <alpine.DEB.2.02.1502201042330.4007@uplift.swm.pp.se> <7A86BDC6-FF4B-49FF-B59C-BA1DEF463173@inf-net.nl> <alpine.DEB.2.02.1502201310050.4007@uplift.swm.pp.se> <09793905-8D12-49E0-A040-490F617C87FF@inf-net.nl> <alpine.DEB.2.02.1502201410510.4007@uplift.swm.pp.se> <82E892D5-98C3-4DD8-9E78-A754D77A5AF6@employees.org> <alpine.DEB.2.02.1502201455500.4007@uplift.swm.pp.se> <20150220224225.GH8096@cisco.com> <alpine.DEB.2.02.1502210658230.4007@uplift.swm.pp.se> <871tljjphw.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502211544510.4007@uplift.swm.pp.se> <87wq3bi9rz.wl-jch@pps.univ-paris-diderot.fr> <99C39872-38E3-463F-B133-5577E484596C@employees.org> <alpine.DEB.2.02.1502231418590.4007@uplift.swm.pp.se>
To: Mikael Abrahamsson <swmike@swm.pp.se>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/vjNL4MSrSqonS0IOgocsF0UNWHk>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] Roaming hosts [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 23 Feb 2015 13:39:41 -0000

--Apple-Mail=_CD554062-33D5-4297-BD8C-F1E989BDE3CB
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

>>> On 21 Feb 2015, at 16:06 , Juliusz Chroboczek =
<jch@pps.univ-paris-diderot.fr> wrote:
>>>=20
>>>>> The client is running a stub implementation of the routing =
protocol.
>>>=20
>>>> I thought we already had decided we didn't require changes to the =
host?
>>>=20
>>> We don't *require* changes to the host.  We propose optional host
>>> modifications that improve the user experience.
>>=20
>> exactly.
>> you aren't going to have much fun with multi-prefix multi-homing =
without host changes anyhow.
>=20
> Let me get this straight: So the proposal is that end systems will =
have to change their IPv6 address when it moves between wifi APs if it's =
a current end system, and in order to keep its address, it needs to =
start to speak HNCP?

are you replying to the point I made? cause fully functioning MHMP =
requires host support (read MP-TCP/session layer) regardless of moving =
or not.

with regards to a proposal I haven't seen one written up, but I don't =
think what your are stating is it. ;-)

cheers,
Ole

--Apple-Mail=_CD554062-33D5-4297-BD8C-F1E989BDE3CB
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJU6y2WAAoJEFuJXizso86gY4oIAKwSD4ouWmzgWEknDMxM1rEp
kLXPXwoBmuMkbmJmPpZCH9l/R9qZeBI4lr/7awTh/uof25B4uhVSuSrNiSaSdRn8
2JB8/o0pqAsmMc+ZC7Kd/O7nFFy1m2fPrB+w3AfvvqjFmSxWkf/1GzeFmdaqFONc
kBJo9lTuB2uxjrLhvF2rL+ElU0YwXnoF+F7fXgc/fiUfziiJ5AgyE2AoedE02Z/s
Qhy4Ycmtwg/uqKxPe4xPF37pn+h8Okvs38iyuxGH6a0qQYjRC68mAk+TzY7+b4o+
fBvsXhvt9nOKu+ZwnJN6ohWY0Y38joaGX6DKOrO5uQAT5Vbq01i5H4402706KjE=
=xcOJ
-----END PGP SIGNATURE-----

--Apple-Mail=_CD554062-33D5-4297-BD8C-F1E989BDE3CB--


From nobody Mon Feb 23 05:42:05 2015
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 C24AF1A1BC8 for <homenet@ietfa.amsl.com>; Mon, 23 Feb 2015 05:42:03 -0800 (PST)
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 3TOmH4tfzaih for <homenet@ietfa.amsl.com>; Mon, 23 Feb 2015 05:42:03 -0800 (PST)
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 C15F71A1BBB for <homenet@ietf.org>; Mon, 23 Feb 2015 05:42:02 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id C2458A2; Mon, 23 Feb 2015 14:41:49 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1424698909; bh=nRfPq/FvrexM+FRbe3kRinx5ZsXntevB5ZLVZosDRgM=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=o8UF/kVoPDpeNMsM6JkdDWVu7Ly7qopAkNtx1e84FG5aOxc8uUrQXI11rjlQm/uOo 1o3nFFEcsQszaMRVDEQJRDVoWQXEX2TYfhqgQEV25JfBJ+bKOX0IyMbp2PUxITil8e uKcIbGtE7OXKGQwqttT3xqiyEmTkgomCSscs8SfA=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id B921DA1; Mon, 23 Feb 2015 14:41:49 +0100 (CET)
Date: Mon, 23 Feb 2015 14:41:49 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Ole Troan <otroan@employees.org>
In-Reply-To: <57E592DD-0BDD-4271-B99F-6A3A174F4EB7@employees.org>
Message-ID: <alpine.DEB.2.02.1502231440460.4007@uplift.swm.pp.se>
References: <8B98F698-983D-4D2A-B5D1-7ACED27C275E@fugue.com> <alpine.DEB.2.02.1502191920560.4007@uplift.swm.pp.se> <CAPRuP3mpNJTu6mP+RAVKKO0kt60PogNtNbCUCRRqxe9im3EzjA@mail.gmail.com> <alpine.DEB.2.02.1502201042330.4007@uplift.swm.pp.se> <7A86BDC6-FF4B-49FF-B59C-BA1DEF463173@inf-net.nl> <alpine.DEB.2.02.1502201310050.4007@uplift.swm.pp.se> <09793905-8D12-49E0-A040-490F617C87FF@inf-net.nl> <alpine.DEB.2.02.1502201410510.4007@uplift.swm.pp.se> <82E892D5-98C3-4DD8-9E78-A754D77A5AF6@employees.org> <alpine.DEB.2.02.1502201455500.4007@uplift.swm.pp.se> <20150220224225.GH8096@cisco.com> <alpine.DEB.2.02.1502210658230.4007@uplift.swm.pp.se> <871tljjphw.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502211544510.4007@uplift.swm.pp.se> <87wq3bi9rz.wl-jch@pps.univ-paris-diderot.fr> <99C39872-38E3-463F-B133-5577E484596C@employees.org> <alpine.DEB.2.02.1502231418590.4007@uplift.swm.pp.se> <57E592DD-0BDD-4271-B99F-6A3A174F4EB7@employees.org>
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/hGHPRsT4dkaiazwKYVPaDvGWH_8>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] Roaming hosts [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 23 Feb 2015 13:42:03 -0000

On Mon, 23 Feb 2015, Ole Troan wrote:

> are you replying to the point I made? cause fully functioning MHMP 
> requires host support (read MP-TCP/session layer) regardless of moving 
> or not.

If I extrapolated correctly what Juliusz wrote, that is not what he had in 
mind.

> with regards to a proposal I haven't seen one written up, but I don't 
> think what your are stating is it. ;-)

I didn't think so either. :)

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


From nobody Mon Feb 23 06:58:43 2015
Return-Path: <mark@townsley.net>
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 B3EFF1A1AB5 for <homenet@ietfa.amsl.com>; Mon, 23 Feb 2015 06:58:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] 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 2hh54qsAkjdx for <homenet@ietfa.amsl.com>; Mon, 23 Feb 2015 06:58:39 -0800 (PST)
Received: from mail-lb0-f171.google.com (mail-lb0-f171.google.com [209.85.217.171]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 974001A0470 for <homenet@ietf.org>; Mon, 23 Feb 2015 06:58:38 -0800 (PST)
Received: by lbjb6 with SMTP id b6so18820695lbj.12 for <homenet@ietf.org>; Mon, 23 Feb 2015 06:58:36 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=81SIT10lqTK2emSRbbgfOWQdRdM5CBaIqZDfuBKq4do=; b=SqCVuxMapAPIF6S2dBJFXB8J4ECD30hdj2FtLhZLhYsC5DHeWbLTgQRjyVQYLLEJg2 ZGqQK7rIeVCN4XEU8ANs+oI0auF+NqvteBC6g7vinMbweqbGXD17e0ca7b9LlLTNaMln c4KZrpS9Pf5v+DhePIOXWiFlA00QWYai1YXWu3A5aKW1GnucweUIEte+S0FLG6yRgWCU Av1Q+ZvjCLJoLLFdIoaErEEmYFYzO4S8FCqU8Kb3vQxeZ00u2CES20LWtHQE/O9O1ohO X9jMY/u/7FJlUHvBCcmlGv0PXarqkXkDNPHi15Z7LOjH3Tp+d6NPftaunDBKbMkVmX9G 2dZQ==
X-Gm-Message-State: ALoCoQkCYVcx2GMtjvD+J1y8VpiZK9JljgKih3i6zVsPkOQYKNbxYHivFY6NJC1GyLmuZdbHibFq
MIME-Version: 1.0
X-Received: by 10.152.191.135 with SMTP id gy7mr9877616lac.91.1424703516856; Mon, 23 Feb 2015 06:58:36 -0800 (PST)
Received: by 10.112.135.200 with HTTP; Mon, 23 Feb 2015 06:58:36 -0800 (PST)
In-Reply-To: <alpine.DEB.2.02.1502231440460.4007@uplift.swm.pp.se>
References: <8B98F698-983D-4D2A-B5D1-7ACED27C275E@fugue.com> <alpine.DEB.2.02.1502191920560.4007@uplift.swm.pp.se> <CAPRuP3mpNJTu6mP+RAVKKO0kt60PogNtNbCUCRRqxe9im3EzjA@mail.gmail.com> <alpine.DEB.2.02.1502201042330.4007@uplift.swm.pp.se> <7A86BDC6-FF4B-49FF-B59C-BA1DEF463173@inf-net.nl> <alpine.DEB.2.02.1502201310050.4007@uplift.swm.pp.se> <09793905-8D12-49E0-A040-490F617C87FF@inf-net.nl> <alpine.DEB.2.02.1502201410510.4007@uplift.swm.pp.se> <82E892D5-98C3-4DD8-9E78-A754D77A5AF6@employees.org> <alpine.DEB.2.02.1502201455500.4007@uplift.swm.pp.se> <20150220224225.GH8096@cisco.com> <alpine.DEB.2.02.1502210658230.4007@uplift.swm.pp.se> <871tljjphw.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502211544510.4007@uplift.swm.pp.se> <87wq3bi9rz.wl-jch@pps.univ-paris-diderot.fr> <99C39872-38E3-463F-B133-5577E484596C@employees.org> <alpine.DEB.2.02.1502231418590.4007@uplift.swm.pp.se> <57E592DD-0BDD-4271-B99F-6A3A174F4EB7@employees.org> <alpine.DEB.2.02.1502231440460.4007@uplift.swm.pp.se>
Date: Mon, 23 Feb 2015 15:58:36 +0100
Message-ID: <CAESTAVvjazOmppFgoigtAraNUEoKEB5HHmKFgNAe-v31+rOzYg@mail.gmail.com>
From: Mark Townsley <mark@townsley.net>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Content-Type: multipart/alternative; boundary=001a1134303a086bcd050fc2a3d7
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/Yy_eNAwKeSmT6ji_mhDjgGQhMB8>
Cc: Ole Troan <otroan@employees.org>, "homenet@ietf.org Group" <homenet@ietf.org>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] Roaming hosts [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 23 Feb 2015 14:58:41 -0000

--001a1134303a086bcd050fc2a3d7
Content-Type: text/plain; charset=UTF-8

When a host connects to a different link covered by a different subnet,
indeed it will require a new IP address. That's pretty fundamental to what
a subnet is. Hosts are getting better and better at handling multiple
addresses, of both versions, coming and going. MPTCP should continue to
help in this regard. I'm a big fan of seeing more and more MPTCP, and I've
been impressed at the ability of modern devices to upgrade their host
stacks in the past 4-5 years (vs. the decade or so before). I'll remain
cautiously hopeful here for the long term.

In the mean time, I fully expect that to support seamless wifi roaming from
one AP to another there will have to be some sort of bridging or tunneling
(capwap, et. al) taking place to keep the single ethernet wifi subnet alive
for IPv4 and less modern IPv6 hosts. That doesn't mean there will be no
room for routing in the home, as one of the primary motivations for IP
routing is to support diverse media types. i.e, it's much easier I think if
wi-fi only has to worry about roaming within wi-fi, and not MOCA, EoPL,
802.15.4, Bluetooth LE, etc. as well.

One day if/when hosts and apps finally become fully resilient to IP address
changes, then it could become much easier on APs as they will have the
chance to simply hand out a new IPv6 address and route, avoiding bridging
and/or tunneling tricks. That could be a nice win for wifi scalability, but
to be honest is shrouded in so many operational practicalities and moving
parts that it's best not to try pretend that this will come to pass even if
we are successful in providing the world with zero-touch IP routing
technology in the home. It could be a very nice bonus, and I hope it
happens, but I wouldn't want to set the bar that high in the near term as
something homenet can make happen on its own.

- Mark










On Mon, Feb 23, 2015 at 2:41 PM, Mikael Abrahamsson <swmike@swm.pp.se>
wrote:

> On Mon, 23 Feb 2015, Ole Troan wrote:
>
>  are you replying to the point I made? cause fully functioning MHMP
>> requires host support (read MP-TCP/session layer) regardless of moving or
>> not.
>>
>
> If I extrapolated correctly what Juliusz wrote, that is not what he had in
> mind.
>
>  with regards to a proposal I haven't seen one written up, but I don't
>> think what your are stating is it. ;-)
>>
>
> I didn't think so either. :)
>
> --
> Mikael Abrahamsson    email: swmike@swm.pp.se
>
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>

--001a1134303a086bcd050fc2a3d7
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div>When a host connects to a different link covered =
by a different subnet, indeed it will require a new IP address. That&#39;s =
pretty fundamental to what a subnet is. Hosts are getting better and better=
 at handling multiple addresses, of both versions, coming and going. MPTCP =
should continue to help in this regard. I&#39;m a big fan of seeing more an=
d more MPTCP, and I&#39;ve been impressed at the ability of modern devices =
to upgrade their host stacks in the past 4-5 years (vs. the decade or so be=
fore). I&#39;ll remain cautiously hopeful here for the long term.</div><div=
><br></div><div>In the mean time, I fully expect that to support seamless w=
ifi roaming from one AP to another there will have to be some sort of bridg=
ing or tunneling (capwap, et. al) taking place to keep the single ethernet =
wifi subnet alive for IPv4 and less modern IPv6 hosts. That doesn&#39;t mea=
n there will be no room for routing in the home, as one of the primary moti=
vations for IP routing is to support diverse media types. i.e, it&#39;s muc=
h easier I think if wi-fi only has to worry about roaming within wi-fi, and=
 not MOCA, EoPL, 802.15.4, Bluetooth LE, etc. as well.=C2=A0</div><div><br>=
</div><div>One day if/when hosts and apps finally become fully resilient to=
 IP address changes, then it could become much easier on APs as they will h=
ave the chance to simply hand out a new IPv6 address and route, avoiding br=
idging and/or tunneling tricks. That could be a nice win for wifi scalabili=
ty, but to be honest is shrouded in so many operational practicalities and =
moving parts that it&#39;s best not to try pretend that this will come to p=
ass even if we are successful in providing the world with zero-touch IP rou=
ting technology in the home. It could be a very nice bonus, and I hope it h=
appens, but I wouldn&#39;t want to set the bar that high in the near term a=
s something homenet can make happen on its own.</div><div><br></div><div>- =
Mark</div><div><br></div><div><br></div><div><br></div><div><br></div><div>=
<br></div><div><br></div><div><br></div><div><br></div><div><br></div></div=
><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Mon, Feb 23, =
2015 at 2:41 PM, Mikael Abrahamsson <span dir=3D"ltr">&lt;<a href=3D"mailto=
:swmike@swm.pp.se" target=3D"_blank">swmike@swm.pp.se</a>&gt;</span> wrote:=
<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-lef=
t:1px #ccc solid;padding-left:1ex">On Mon, 23 Feb 2015, Ole Troan wrote:<br=
>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
are you replying to the point I made? cause fully functioning MHMP requires=
 host support (read MP-TCP/session layer) regardless of moving or not.<br>
</blockquote>
<br>
If I extrapolated correctly what Juliusz wrote, that is not what he had in =
mind.<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
with regards to a proposal I haven&#39;t seen one written up, but I don&#39=
;t think what your are stating is it. ;-)<br>
</blockquote>
<br>
I didn&#39;t think so either. :)<span class=3D"HOEnZb"><font color=3D"#8888=
88"><br>
<br>
-- <br>
Mikael Abrahamsson=C2=A0 =C2=A0 email: <a href=3D"mailto:swmike@swm.pp.se" =
target=3D"_blank">swmike@swm.pp.se</a><br>
<br>
______________________________<u></u>_________________<br>
homenet mailing list<br>
<a href=3D"mailto:homenet@ietf.org" target=3D"_blank">homenet@ietf.org</a><=
br>
<a href=3D"https://www.ietf.org/mailman/listinfo/homenet" target=3D"_blank"=
>https://www.ietf.org/mailman/<u></u>listinfo/homenet</a><br>
</font></span></blockquote></div><br></div>

--001a1134303a086bcd050fc2a3d7--


From nobody Mon Feb 23 07:25:08 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 6C7741A1AB3 for <homenet@ietfa.amsl.com>; Mon, 23 Feb 2015 07:25:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.15
X-Spam-Level: *
X-Spam-Status: No, score=1.15 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_EQ_FR=0.35] autolearn=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 5RJH20jUlKuo for <homenet@ietfa.amsl.com>; Mon, 23 Feb 2015 07:25:05 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 B68811A1A9D for <homenet@ietf.org>; Mon, 23 Feb 2015 07:24:59 -0800 (PST)
Received: from potemkin.univ-paris7.fr (potemkin.univ-paris7.fr [IPv6:2001:660:3301:8000::1:1]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t1NFOvwR007546 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 23 Feb 2015 16:24:58 +0100
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by potemkin.univ-paris7.fr (8.14.4/8.14.4/relay2/56228) with ESMTP id t1NFOvRC025232; Mon, 23 Feb 2015 16:24:57 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 52F422C2345; Mon, 23 Feb 2015 16:24:57 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id F3Ma1QjMoltr; Mon, 23 Feb 2015 16:24:55 +0100 (CET)
Received: from pirx.pps.jussieu.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 599082C233F; Mon, 23 Feb 2015 16:24:53 +0100 (CET)
Date: Mon, 23 Feb 2015 16:24:54 +0100
Message-ID: <87lhjosla1.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Markus Stenberg <markus.stenberg@iki.fi>
In-Reply-To: <7D8C2976-1649-4349-9E90-E24DD2848086@iki.fi>
References: <8761at9vx5.wl-jch@pps.univ-paris-diderot.fr> <7D8C2976-1649-4349-9E90-E24DD2848086@iki.fi>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]); Mon, 23 Feb 2015 16:24:58 +0100 (CET)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Mon, 23 Feb 2015 16:24:57 +0100 (CET)
X-Miltered: at korolev with ID 54EB4649.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 54EB4649.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54EB4649.001 from potemkin.univ-paris7.fr/potemkin.univ-paris7.fr/null/potemkin.univ-paris7.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Enveloppe: 54EB4649.001 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54EB4649.001 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 54EB4649.001 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/u-QftCKvJcrENd_6hs9a5WTVMPs>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] DNCP questions
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 23 Feb 2015 15:25:07 -0000

>> The minimum MTU in IPv6 is 1280 bytes, and the minimum maximum packet size
>> (before fragmentation) is 1500 bytes.

> I assume you refer to Long Network Status (on multicast);

Yes, sorry.

> post MTU, or in secure mode, it should just use the Short one (which is
> of fixed length).

Ok.  So I send multicast SNS.  I receive NSR.  I'm supposed to send LSR,
right?  But it doesn't fit in maximum packet size, even with fragmentation.

RFC 2460, Section 5:

   A node must be able to accept a fragmented packet that, after
   reassembly, is as large as 1500 octets.  A node is permitted to
   accept fragmented packets that reassemble to more than 1500 octets.
   An upper-layer protocol or application that depends on IPv6
   fragmentation to send packets larger than the MTU of a path should
   not send packets larger than 1500 octets unless it has assurance that
   the destination is capable of reassembling packets of that larger
   size.

> Current assumption is that sane set of node data fits inside one
> (potentially fragmented) IPv6 packet (non-jumbogram), essentially
> limiting the maximum size to <64kb.

You cannot count on that.  See above.

>> What should I do if I receive an unknown TLV?  I assume I should silently
>> ignore it if it's inside a Data TLV, and include it in my database and
>> flood it if itâ€™s within a Data TLV, right?

> Right.

Please make that very clear.  Implementors will get it wrong, and we'll
find ourselves unable to extend the protocol.

>> Which messages are allowed to contain extra TLVs?  For example, what
>> should I do if I receive a Long Network State Update with a bunch of
>> unknown TLVs interleaved with the Node State TLVs?
>
> Any of them. The messages are defined just by the MUST be present TLVs. 

Again, please make this very clear.  In particular, make it clear that
upon encountering an unknown TLV, the rest of the packet must be processed
as usual.  (The other possible choice is that the whole rest of the packet
is ignored.)

>> There's a single connection for all neighbours on a given interface,
>> right?  Why not call that an Interface, then?

> In case of HNCP, this is true, as it has connection=(link-local IPv6
> UDP-using) interface. In DNCP, a connection may be just e.g. one unicast
> endpoint you want to talk with over the internet.

I see.  I still dislike the term of "connection", which seems to imply
a point-to-point thing.  Ideas?

>> 7. Neighbor graph
>>
>> The notion of "neighbor graph" suddenly appears in Section 5.4.  It's
>> pretty obvious what you mean, but this should be precisely defined
>> somewhere.

> The later traversing definition more or less describes what it â€˜isâ€™; any
> idea of what a good definition would look like?

Actually, looking at it again, I'm not sure I know what is the neighbour
graph.  It's the directed graph defined by all neighbour TLVs, or the
undirected graph that you get after removing unidirectional neighbours?
I assume the latter.

-- Juliusz



From nobody Mon Feb 23 07:37:07 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 860DC1A1B30 for <homenet@ietfa.amsl.com>; Mon, 23 Feb 2015 07:37:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.15
X-Spam-Level: 
X-Spam-Status: No, score=-0.15 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, HELO_EQ_FR=0.35] autolearn=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 yNqNctduoE1d for <homenet@ietfa.amsl.com>; Mon, 23 Feb 2015 07:37:05 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 5A5131A1B24 for <homenet@ietf.org>; Mon, 23 Feb 2015 07:37:05 -0800 (PST)
Received: from potemkin.univ-paris7.fr (potemkin.univ-paris7.fr [IPv6:2001:660:3301:8000::1:1]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t1NFb3CE014405 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 23 Feb 2015 16:37:03 +0100
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by potemkin.univ-paris7.fr (8.14.4/8.14.4/relay2/56228) with ESMTP id t1NFb3Zc031514; Mon, 23 Feb 2015 16:37:03 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 9867E2C2349; Mon, 23 Feb 2015 16:37:03 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id d3dwe1TWxX9S; Mon, 23 Feb 2015 16:37:01 +0100 (CET)
Received: from pirx.pps.jussieu.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 2AAAC2C2347; Mon, 23 Feb 2015 16:37:01 +0100 (CET)
Date: Mon, 23 Feb 2015 16:37:01 +0100
Message-ID: <87k2z8skpu.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Michael Richardson <mcr+ietf@sandelman.ca>
In-Reply-To: <14065.1424666696@sandelman.ca>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <14065.1424666696@sandelman.ca>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]); Mon, 23 Feb 2015 16:37:03 +0100 (CET)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Mon, 23 Feb 2015 16:37:03 +0100 (CET)
X-Miltered: at korolev with ID 54EB491F.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 54EB491F.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54EB491F.000 from potemkin.univ-paris7.fr/potemkin.univ-paris7.fr/null/potemkin.univ-paris7.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Enveloppe: 54EB491F.001 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54EB491F.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 54EB491F.001 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/zPrGT9gMR1vgRM4jxA6phvU5WvU>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 23 Feb 2015 15:37:06 -0000

Hi Michael,

The work on the document is being done on https://github.com/choppsv1
and I try to keep an up-to-date version of the generated files on

  http://www.pps.univ-paris-diderot.fr/~jch/private/draft-mrw-homenet-rtg-comparison-XX.html
  http://www.pps.univ-paris-diderot.fr/~jch/private/draft-mrw-homenet-rtg-comparison-XX.txt

> So the gateway machine (the 6LBR) will run the HOMENET routing protocol and
> the LLN routing protocol (RPL, or some other mesh-under protocol), but the
> HOMENET routing protocol will never be run by the sensors.

I've vastly expanded the section about stub networks; please check if it
suits you better or whether you wish anything added.

> It also, btw, makes it unable to run over 15.4,

Noted, will add.

> 3) metrics.
> We don't know how we will assign link metrics, so we don't know how important
> X-bit metrics are.

I've expanded the section about metrics.  The IS-IS part is still woefully
inadequate.

> 4) convergence over 802.11 MAC...

I've expanded this section.

> 5) some amount of "my processor is slower than yours and still ran protocol XYZ"
> (http://www.phespirit.info/montypython/four_yorkshiremen.htm)

Not my choice, sorry.

-- Juliusz


From nobody Mon Feb 23 07:47:14 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 4F6161A1B07 for <homenet@ietfa.amsl.com>; Mon, 23 Feb 2015 07:47:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.15
X-Spam-Level: *
X-Spam-Status: No, score=1.15 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_EQ_FR=0.35] autolearn=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 OXRby4UlT6IC for <homenet@ietfa.amsl.com>; Mon, 23 Feb 2015 07:47:12 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 5AFD01A1B66 for <homenet@ietf.org>; Mon, 23 Feb 2015 07:46:59 -0800 (PST)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t1NFkvLk019460; Mon, 23 Feb 2015 16:46:57 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 37A0C2C234A; Mon, 23 Feb 2015 16:46:57 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id QjG_VofiiAaj; Mon, 23 Feb 2015 16:46:55 +0100 (CET)
Received: from pirx.pps.jussieu.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 0AC012C2345; Mon, 23 Feb 2015 16:46:55 +0100 (CET)
Date: Mon, 23 Feb 2015 16:46:55 +0100
Message-ID: <87ioessk9c.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Michael Richardson <mcr+ietf@sandelman.ca>
In-Reply-To: <755.1424662895@sandelman.ca>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E0FB64.8010009@openwrt.org> <87k2ziritt.wl-jch@pps.univ-paris-diderot.fr> <D80DC12D-AFBA-45D1-9D19-E4D4B24961FA@gmail.com> <755.1424662895@sandelman.ca>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Mon, 23 Feb 2015 16:46:57 +0100 (CET)
X-Miltered: at korolev with ID 54EB4B71.002 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54EB4B71.002 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54EB4B71.002 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/s4QfvGHpIfNBHbMz8fzEEU3MN3Q>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Margaret Wasserman <margaretw42@gmail.com>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 23 Feb 2015 15:47:13 -0000

> So assuming some decent high-power 802.11ac in the Bradford house
> (http://en.wikipedia.org/wiki/Eight_Is_Enough) to link the per-room router to
> legacy 802.11b and per-person (phone) router to BTLE/PAN, it means we have
> about 30 routers on the wifi.

I'm under opposing pressures relating to scaling.  A lot of people, like
you, seem to think it's irrelevant, some others feel very strongly about it.

The current version of the draft has this to say:

    Experts appear to disagree on the expected size of a Homenet: we have
    heard estimates ranging from just one router up to 250 routers. In any
    case, while scaling beyond a few thousand nodes is not likely to be
    relevant to Homenet in the foreseeable future, the Homenet protocols,
    if successful, will be repurposed to larger networks, whether we like
    it or not, and it is desirable to use a protocol that scales well.

The thinking is that if Homenet routers are cheaply and widely available,
then people will use them for larger deployments; no amount of legislating
such uses out of scope will change that fact.  The obvious example would
be a hotel: why pay for a professionally installed network when you can
just plug in a bunch of $40 Homenet routers and be done with your customer
network.  I can well imagine a hotel using 200 routers.

If hotels don't meet your fancy -- think schools, think appartment blocks
in third world countries, think hippy communes.  Do we wish to explicitly
support such use cases?  Hopefully not.  But do we wish to have our
protocols collapse just because we didn't have the foresight to avoid
gratuitious limitations?

-- Juliusz


From nobody Mon Feb 23 08:51:55 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 15D901A1BB4 for <homenet@ietfa.amsl.com>; Mon, 23 Feb 2015 08:51:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.15
X-Spam-Level: *
X-Spam-Status: No, score=1.15 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_EQ_FR=0.35] autolearn=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 g3wKXLrSPx-U for <homenet@ietfa.amsl.com>; Mon, 23 Feb 2015 08:51:52 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 946931A1BDA for <homenet@ietf.org>; Mon, 23 Feb 2015 08:51:52 -0800 (PST)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t1NGppHI019602; Mon, 23 Feb 2015 17:51:51 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 055762C2355; Mon, 23 Feb 2015 17:51:51 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id E4BJDhvs2IT3; Mon, 23 Feb 2015 17:51:49 +0100 (CET)
Received: from pirx.pps.jussieu.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 733A82C234A; Mon, 23 Feb 2015 17:51:47 +0100 (CET)
Date: Mon, 23 Feb 2015 17:51:47 +0100
Message-ID: <874mqcsh98.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Markus Stenberg <markus.stenberg@iki.fi>
In-Reply-To: <7D8C2976-1649-4349-9E90-E24DD2848086@iki.fi>
References: <8761at9vx5.wl-jch@pps.univ-paris-diderot.fr> <7D8C2976-1649-4349-9E90-E24DD2848086@iki.fi>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Mon, 23 Feb 2015 17:51:51 +0100 (CET)
X-Miltered: at korolev with ID 54EB5AA7.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54EB5AA7.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54EB5AA7.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/25oTnrXY6hCQ-UBOPPYG8yMmtxU>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] DNCP questions
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 23 Feb 2015 16:51:54 -0000

Another question -- is it possible to participate in Trickle-driven
flooding without building the full topology graph?

If not, that's a little disappointing, since Trickle is designed so that
it can be implemented while knowing just my immediate neighbours.  But it
looks to me like I cannot do the activities mandated in Section 5.4
without building full topology.

-- Juliusz


From nobody Mon Feb 23 09:00:24 2015
Return-Path: <markus.stenberg@iki.fi>
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 81EAE1A1B87 for <homenet@ietfa.amsl.com>; Mon, 23 Feb 2015 09:00:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.121
X-Spam-Level: 
X-Spam-Status: No, score=-1.121 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_NEUTRAL=0.779] autolearn=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 5y6lrlZoahxF for <homenet@ietfa.amsl.com>; Mon, 23 Feb 2015 09:00:21 -0800 (PST)
Received: from jenni2.inet.fi (mta-out1.inet.fi [62.71.2.195]) by ietfa.amsl.com (Postfix) with ESMTP id 7295E1A1B76 for <homenet@ietf.org>; Mon, 23 Feb 2015 09:00:17 -0800 (PST)
Received: from poro.lan (80.220.64.126) by jenni2.inet.fi (8.5.142.08) (authenticated as stenma-47) id 54E3C70700B45680; Mon, 23 Feb 2015 19:00:13 +0200
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Markus Stenberg <markus.stenberg@iki.fi>
In-Reply-To: <87lhjosla1.wl-jch@pps.univ-paris-diderot.fr>
Date: Mon, 23 Feb 2015 19:00:13 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <BB38C59C-D71D-4AA0-ABFE-04D557C1DCCD@iki.fi>
References: <8761at9vx5.wl-jch@pps.univ-paris-diderot.fr> <7D8C2976-1649-4349-9E90-E24DD2848086@iki.fi> <87lhjosla1.wl-jch@pps.univ-paris-diderot.fr>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/pSH2zvtgFS1E8XorBWOw7ulj_ac>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Markus Stenberg <markus.stenberg@iki.fi>
Subject: Re: [homenet] DNCP questions
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 23 Feb 2015 17:00:23 -0000

On 23.2.2015, at 17.24, Juliusz Chroboczek =
<jch@pps.univ-paris-diderot.fr> wrote:
>> post MTU, or in secure mode, it should just use the Short one (which =
is
>> of fixed length).
> Ok.  So I send multicast SNS.  I receive NSR.  I'm supposed to send =
LSR,
> right?  But it doesn't fit in maximum packet size, even with =
fragmentation.
>=20
> RFC 2460, Section 5:
>=20
>   A node must be able to accept a fragmented packet that, after
>   reassembly, is as large as 1500 octets.  A node is permitted to
>   accept fragmented packets that reassemble to more than 1500 octets.
>   An upper-layer protocol or application that depends on IPv6
>   fragmentation to send packets larger than the MTU of a path should
>   not send packets larger than 1500 octets unless it has assurance =
that
>   the destination is capable of reassembling packets of that larger
>   size.

I guess this is another MUST to be added to HNCP text (DNCP itself is =
not IPv6-specific as such).

I am not convinced by the trend to add fragmentation to every protocol =
on top of IP{v4,v6} but can be convinced otherwise of course given good =
arguments. At least in case of HNCP as it works on link-local level =
only, I think saying you MUST have sane IP stack on both nodes is not =
overreaching it as there are no middleboxes to worry about.

>> Current assumption is that sane set of node data fits inside one
>> (potentially fragmented) IPv6 packet (non-jumbogram), essentially
>> limiting the maximum size to <64kb.
> You cannot count on that.  See above.

I consider it documentation error, see above :)

>>> What should I do if I receive an unknown TLV?  I assume I should =
silently
>>> ignore it if it's inside a Data TLV, and include it in my database =
and
>>> flood it if it=E2=80=99s within a Data TLV, right?
>> Right.
> Please make that very clear.  Implementors will get it wrong, and =
we'll
> find ourselves unable to extend the protocol.

Ok, I will add one more MUST (although reading the text, I thought it =
obvious already from the context but guess not).

+      Whole =E2=80=9Cnode data" is owned by the node that
+      publishes it, and it MUST be passed along as-is, including TLVs
+      unknown to the forwarder.

>>> Which messages are allowed to contain extra TLVs?  For example, what
>>> should I do if I receive a Long Network State Update with a bunch of
>>> unknown TLVs interleaved with the Node State TLVs?
>> Any of them. The messages are defined just by the MUST be present =
TLVs.=20
> Again, please make this very clear.  In particular, make it clear that
> upon encountering an unknown TLV, the rest of the packet must be =
processed
> as usual.  (The other possible choice is that the whole rest of the =
packet
> is ignored.)

       <t>DNCP profiles MAY add additional TLVs to the message specified
-      here, or even define additional messages as needed.</t>
+      here, or even define additional messages as needed. TLVs not
+      recognized by the receiver MUST be ignored. </t>

>>> There's a single connection for all neighbours on a given interface,
>>> right?  Why not call that an Interface, then?
>> In case of HNCP, this is true, as it has connection=3D(link-local =
IPv6
>> UDP-using) interface. In DNCP, a connection may be just e.g. one =
unicast
>> endpoint you want to talk with over the internet.
> I see.  I still dislike the term of "connection", which seems to imply
> a point-to-point thing.  Ideas?

Not from me; we had relatively long (and fruitless) internal discussion =
on this in November IIRC.=20

>>> 7. Neighbor graph
>>>=20
>>> The notion of "neighbor graph" suddenly appears in Section 5.4.  =
It's
>>> pretty obvious what you mean, but this should be precisely defined
>>> somewhere.
>> The later traversing definition more or less describes what it =
=E2=80=98is=E2=80=99; any
>> idea of what a good definition would look like?
> Actually, looking at it again, I'm not sure I know what is the =
neighbour
> graph.  It's the directed graph defined by all neighbour TLVs, or the
> undirected graph that you get after removing unidirectional =
neighbours?
> I assume the latter.

The latter. Edited text a bit in few places, dunno if it really helped =
:)

-Markus=


From nobody Mon Feb 23 09:17:27 2015
Return-Path: <markus.stenberg@iki.fi>
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 C80CD1A1BE8 for <homenet@ietfa.amsl.com>; Mon, 23 Feb 2015 09:17:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.778
X-Spam-Level: 
X-Spam-Status: No, score=0.778 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_NEUTRAL=0.779] autolearn=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 Jaf5h_w-KbAa for <homenet@ietfa.amsl.com>; Mon, 23 Feb 2015 09:17:24 -0800 (PST)
Received: from jenni2.inet.fi (mta-out1.inet.fi [62.71.2.227]) by ietfa.amsl.com (Postfix) with ESMTP id 327731A1BE3 for <homenet@ietf.org>; Mon, 23 Feb 2015 09:17:21 -0800 (PST)
Received: from poro.lan (80.220.64.126) by jenni2.inet.fi (8.5.142.08) (authenticated as stenma-47) id 54E3C70700B4C39D; Mon, 23 Feb 2015 19:17:18 +0200
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Markus Stenberg <markus.stenberg@iki.fi>
In-Reply-To: <874mqcsh98.wl-jch@pps.univ-paris-diderot.fr>
Date: Mon, 23 Feb 2015 19:17:18 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <B5B68563-91D5-455C-A3AB-B1B3969302B7@iki.fi>
References: <8761at9vx5.wl-jch@pps.univ-paris-diderot.fr> <7D8C2976-1649-4349-9E90-E24DD2848086@iki.fi> <874mqcsh98.wl-jch@pps.univ-paris-diderot.fr>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/uDkWrufgXpib-IdENLE3K9uyzgs>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Markus Stenberg <markus.stenberg@iki.fi>
Subject: Re: [homenet] DNCP questions
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 23 Feb 2015 17:17:25 -0000

On 23.2.2015, at 18.51, Juliusz Chroboczek =
<jch@pps.univ-paris-diderot.fr> wrote:
> Another question -- is it possible to participate in Trickle-driven
> flooding without building the full topology graph?
>=20
> If not, that's a little disappointing, since Trickle is designed so =
that
> it can be implemented while knowing just my immediate neighbours.  But =
it
> looks to me like I cannot do the activities mandated in Section 5.4
> without building full topology.

You are coming up with same things I have thought about quite a bit too.

The current answer based on strict reading of the spec is no.

The reason isn=E2=80=99t 5.4 (it is just a SHOULD, because you can =
implement something stubby that just relies on LNS being complete list =
of nodes known by neighbors).=20

Why is it impossible then? Simply because the 5.2 specifies that node =
data requests MUST be always responded to (as you may not want to =
actually store any data about anyone else than yourself to start with). =
I have been debating with myself how to change this.

Is this desirable to be changed? Probably so.=20

Simplest change to achieve this would be simply to add =E2=80=98if =
available=E2=80=99 to 5.2 (and perhaps to note in section 4 that the =
data model is not really normative), and some sort of flag about stubby =
behavior (notably, assume that there is no HNCP talkers behind the node =
so it is asked only about it=E2=80=99s own state).

With this scheme, you can have:

[1] =E2=80=99really stubby HNCP write-only=E2=80=99 which does not store =
anything except (possibly empty-ish set) of it=E2=80=99s own published =
node data and one neighbor - the non-stubby router it has chosen. All it =
needs to know about the other nodes is just a copy of LNS stored =
somewhere so it can interact with non-stubby router (and pretend nobody =
else exists so no need for keeping track of even other local neighbors).=20=


However, I am not sure if this scheme is actually sensible; in practise, =
if you want =E2=80=98write-only=E2=80=99, you really want to just have =
some exchange with a genuine long-lived HNCP participant with a TTL + =
early revocation scheme.

[2] =E2=80=99bit less minimal but still stubby=E2=80=99 HNCP could just =
keep all node data that has reference in LNS of it=E2=80=99s peers but =
otherwise work like [1]. Relatively useful, and much simpler to =
implement than whole thing still.

Note that both of these =E2=80=99stubby=E2=80=99 variants need =
=E2=80=99non-stubby=E2=80=99 one to leech off on the same link. Both =
would be fine to stick in e.g. host though.

Cheers,

-Markus=


From nobody Mon Feb 23 12:00:07 2015
Return-Path: <jhw@nestlabs.com>
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 1CAFC1A6EF9 for <homenet@ietfa.amsl.com>; Mon, 23 Feb 2015 12:00:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.722
X-Spam-Level: 
X-Spam-Status: No, score=0.722 tagged_above=-999 required=5 tests=[BAYES_50=0.8, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] 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 mFX_nXXDA1GO for <homenet@ietfa.amsl.com>; Mon, 23 Feb 2015 12:00:01 -0800 (PST)
Received: from mail-oi0-f52.google.com (mail-oi0-f52.google.com [209.85.218.52]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 732901A6EF4 for <homenet@ietf.org>; Mon, 23 Feb 2015 12:00:01 -0800 (PST)
Received: by mail-oi0-f52.google.com with SMTP id u20so15498654oif.11 for <homenet@ietf.org>; Mon, 23 Feb 2015 12:00:00 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=yylUItpU+gd0PkLfjb4Ppk22qAsC8NL+K5CcJkp/BWs=; b=KM65wNHtLhqVd+H05fUwypi15VBFiS9wnMAVG/ez+Ah4GjxnXgxX/uxobIkRxp6YUC k0CayMfEI0gPhGGqYRMnNlQaESMegrwUqaojbxWn7JHqZBfjx0nW60yAg+RkrnaygPjr lGJHntJi/C6wbYvxs0ZKRabq4p2MOo+6V2EUJMKLMC+UU4LI2+CsiW6b2J+veJqbDpMj Fu2EjVQ3Q5KLZxWfj2YBbWyQapCjc7Z7rrCXN87AxnJ8pxOOkaTkIvCMXpmEE4kt3Nse WwXmEiG1k4LpKObYJ4ybIQQTSqgCcJAj+tPGvahY9k7rBRnTp7xO6LF1Abq7aTJNyO/f zhZA==
X-Gm-Message-State: ALoCoQnITdBo/ksKf63fjbEK4VvFfjFjhYthummc7TUP6OlK6r251si9d5ZKGkLqVdUTioTs3QTc
MIME-Version: 1.0
X-Received: by 10.202.217.9 with SMTP id q9mr8150082oig.35.1424721600664; Mon, 23 Feb 2015 12:00:00 -0800 (PST)
Received: by 10.76.150.2 with HTTP; Mon, 23 Feb 2015 12:00:00 -0800 (PST)
In-Reply-To: <CAA93jw7eGxPBNX+5LqX+qTYfRxNDxQpKo1fecUa2XH3bAKgvQQ@mail.gmail.com>
References: <CAA93jw7eGxPBNX+5LqX+qTYfRxNDxQpKo1fecUa2XH3bAKgvQQ@mail.gmail.com>
Date: Mon, 23 Feb 2015 12:00:00 -0800
Message-ID: <CADhXe526Z-QFMjKXaNNCM2jce=iHkTAq1z8Oj+qyj5Tq=RKo9A@mail.gmail.com>
From: James Woodyatt <jhw@nestlabs.com>
To: HOMENET <homenet@ietf.org>
Content-Type: multipart/alternative; boundary=001a113cd400e9638f050fc6d85d
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/V_ub7aaEkWEPK-PPjdOy7T9g4Sg>
Subject: Re: [homenet] A poll
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 23 Feb 2015 20:00:05 -0000

--001a113cd400e9638f050fc6d85d
Content-Type: text/plain; charset=UTF-8

On Fri, Feb 20, 2015 at 8:50 AM, Dave Taht <dave.taht@gmail.com> wrote:

> 0) Have you managed to get ipv6 working at all? If so, how? What sort
> of problems did you encounter?
>

On my home network, I use Sonic.Net's unsupported private IPv6-over-IPv4
tunnel with an Apple AirPort Extreme base station. Problems I have
encountered in the last year include A) buggy firmware updates from Apple
that breaks the IPv6 tunnel, and B) occasional loss of IPv6 routing because
Sonic.net doesn't officially support IPv6 and feels okay leaving it broken
for days at a time.


> 1) Have you attempted to deploy a routing protocol in your home? Which
> one, and why?
>

No. Because I need only one IEEE 802.1 link for all my devices. Everything
is globally addressed in IPv6, and my AirPort has its IPv6 simple security
mode set for transparency. I have only four public IPv4 addresses, and I
use a second IPv4/NAT router for address amplification.


> 2) Have you attempted to get hnetd's prefix distribution system
> working? (it supports linux mainline and openwrt presently)
>

Nope. I haven't had the time or need to replace my AirPort with an OpenWRT
install on my Netgear router.


> 3) Do you use ethernet? How many clients in your home are ethernet
> connected?
>

Only two hosts on Ethernet now. One is my DNS master, and the other is a
printer. I had five last year.


> 4) Do you use wifi? How many clients are wifi connected? Do you use
> range extenders?
>

Yes and yes. I usually have ten to twelve different stations, many of which
are mobile devices.


> 5) How many devices do you think you will have connected to the
> network in your home in 5 years? How many now?
>

Probably another ten or so. I'm planning to deploy some Nest devices later
this year. Those devices will not yet use HOMENET or a routing protocol on
Wi-fi, because we're still in working group development hell here.


> 6) Do you use any other network connected technologies (homeplug,
> 802.14, LTE, etc). If so, which ones, and why?
>

Not yet. Ethernet and Wi-fi, with some LTE on mobile phones. The coming
Nest devices will use Thread on IEEE 802.15.4.


> 7) Do you use mdns service discovery?
>

Yes. Extensively. I can say that because I know what magical things Apple
is doing that relies on it working seamlessly and transparently so that
people don't know they are using it. When it breaks, of course, people
blame all kinds of unrelated stuff, but it's mDNS-SD that should be the
focus of their attention. There is a reason I haven't upgraded to OS X
10.10 yet, and its name is discoveryd.

-- 
james woodyatt <jhw@nestlabs.com>
Nest Labs, Communications Engineering

--001a113cd400e9638f050fc6d85d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><span class=3D"im" style=3D"font-size:12.8000001907349px">=
On Fri, Feb 20, 2015 at 8:50 AM, Dave Taht=C2=A0<span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:dave.taht@gmail.com" target=3D"_blank">dave.taht@gmail.com</a>=
&gt;</span>=C2=A0wrote:<br></span><div class=3D"gmail_extra" style=3D"font-=
size:12.8000001907349px"><div class=3D"gmail_quote"><span class=3D"im"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left=
-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;paddi=
ng-left:1ex">0) Have you managed to get ipv6 working at all? If so, how? Wh=
at sort<br>of problems did you encounter?<br></blockquote><div><br></div></=
span><div>On my home network, I use Sonic.Net&#39;s unsupported private IPv=
6-over-IPv4 tunnel with an Apple AirPort Extreme base station. Problems I h=
ave encountered in the last year include A) buggy firmware updates from App=
le that breaks the IPv6 tunnel, and B) occasional loss of IPv6 routing beca=
use Sonic.net doesn&#39;t officially support IPv6 and feels okay leaving it=
 broken for days at a time.</div><span class=3D"im"><div>=C2=A0</div><block=
quote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-w=
idth:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding=
-left:1ex">1) Have you attempted to deploy a routing protocol in your home?=
 Which<br>one, and why?<br></blockquote><div><br></div></span><div>No. Beca=
use I need only one IEEE 802.1 link for all my devices. Everything is globa=
lly addressed in IPv6, and my AirPort has its IPv6 simple security mode set=
 for transparency. I have only four public IPv4 addresses, and I use a seco=
nd IPv4/NAT router for address amplification.</div><span class=3D"im"><div>=
=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0=
.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-s=
tyle:solid;padding-left:1ex">2) Have you attempted to get hnetd&#39;s prefi=
x distribution system<br>working? (it supports linux mainline and openwrt p=
resently)<br></blockquote><div><br></div></span><div>Nope. I haven&#39;t ha=
d the time or need to replace my AirPort with an OpenWRT install on my Netg=
ear router.</div><span class=3D"im"><div>=C2=A0</div><blockquote class=3D"g=
mail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-=
left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">3) Do=
 you use ethernet? How many clients in your home are ethernet connected?<br=
></blockquote><div><br></div></span><div>Only two hosts on Ethernet now. On=
e is my DNS master, and the other is a printer. I had five last year.</div>=
<span class=3D"im"><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(20=
4,204,204);border-left-style:solid;padding-left:1ex">4) Do you use wifi? Ho=
w many clients are wifi connected? Do you use<br>range extenders?<br></bloc=
kquote><div><br></div></span><div>Yes and yes. I usually have ten to twelve=
 different stations, many of which are mobile devices.</div><span class=3D"=
im"><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px =
0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);bord=
er-left-style:solid;padding-left:1ex">5) How many devices do you think you =
will have connected to the<br>network in your home in 5 years? How many now=
?<br></blockquote><div><br></div></span><div>Probably another ten or so. I&=
#39;m planning to deploy some Nest devices later this year. Those devices w=
ill not yet use HOMENET or a routing protocol on Wi-fi, because we&#39;re s=
till in working group development hell here.</div><span class=3D"im"><div>=
=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0=
.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-s=
tyle:solid;padding-left:1ex">6) Do you use any other network connected tech=
nologies (homeplug,<br>802.14, LTE, etc). If so, which ones, and why?<br></=
blockquote><div><br></div></span><div>Not yet. Ethernet and Wi-fi, with som=
e LTE on mobile phones. The coming Nest devices will use Thread on IEEE 802=
.15.4.</div><span class=3D"im"><div>=C2=A0</div><blockquote class=3D"gmail_=
quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-=
color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">7) Do you =
use mdns service discovery?<br></blockquote><div><br></div></span><div>Yes.=
 Extensively. I can say that because I know what magical things Apple is do=
ing that relies on it working seamlessly and transparently so that people d=
on&#39;t know they are using it. When it breaks, of course, people blame al=
l kinds of unrelated stuff, but it&#39;s mDNS-SD that should be the focus o=
f their attention. There is a reason I haven&#39;t upgraded to OS X 10.10 y=
et, and its name is discoveryd.</div></div></div><div class=3D"gmail_extra"=
><div><br></div>-- <br><div class=3D"gmail_signature"><div dir=3D"ltr">jame=
s woodyatt &lt;<a href=3D"mailto:jhw@nestlabs.com" target=3D"_blank">jhw@ne=
stlabs.com</a>&gt;<div>Nest Labs, Communications Engineering</div></div></d=
iv>
</div></div>

--001a113cd400e9638f050fc6d85d--


From nobody Mon Feb 23 12:42:52 2015
Return-Path: <eckert@cisco.com>
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 C7F091A6F04 for <homenet@ietfa.amsl.com>; Mon, 23 Feb 2015 12:42:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -13.311
X-Spam-Level: 
X-Spam-Status: No, score=-13.311 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_42=0.6, J_CHICKENPOX_44=0.6, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 O-64iiyo_Rxk for <homenet@ietfa.amsl.com>; Mon, 23 Feb 2015 12:42:50 -0800 (PST)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CF2281A3BA6 for <homenet@ietf.org>; Mon, 23 Feb 2015 12:42:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2488; q=dns/txt; s=iport; t=1424724169; x=1425933769; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=Td6waWJeBwZ3gWPFsTNUSXdoJgn3WltvF8SwA1cRH64=; b=NFw46J49HfkRPoPXmNDxnOeBTJiENw9tFwObfIXnMOFBF2RAGZZdP0VC dg9sTa4iu5Ur8jEG/8vtfEL8zvms7r5/Ks7sYRX2d8mLC/9PQkRfUyM6y tQ9Pwdmkb3n4u4eiCuCYgLbyorb52N2TvEswLNggINJ9fC45gNWfTIXX3 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DFCgB0kOtU/51dJa1bgwZSWsIwYAqFJ0kCgSNDAQEBAQEBfIQQAQEEAQEBNzQLBQsLGAklDwUTNhOILw3TJgEBAQEBAQEBAQEBAQEBAQEBAQEBARMEixOEbgeDF4EUBYpKjkoBkzMiggIcFIFdHTGCQwEBAQ
X-IronPort-AV: E=Sophos;i="5.09,633,1418083200"; d="scan'208";a="126133394"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by alln-iport-1.cisco.com with ESMTP; 23 Feb 2015 20:42:49 +0000
Received: from mcast-linux1.cisco.com (mcast-linux1.cisco.com [172.27.244.121]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id t1NKgm36029357 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 23 Feb 2015 20:42:49 GMT
Received: from mcast-linux1.cisco.com (localhost.cisco.com [127.0.0.1]) by mcast-linux1.cisco.com (8.13.8/8.13.8) with ESMTP id t1NKglLd016593; Mon, 23 Feb 2015 12:42:47 -0800
Received: (from eckert@localhost) by mcast-linux1.cisco.com (8.13.8/8.13.8/Submit) id t1NKglX9016591; Mon, 23 Feb 2015 12:42:47 -0800
Date: Mon, 23 Feb 2015 12:42:47 -0800
From: Toerless Eckert <eckert@cisco.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Message-ID: <20150223204247.GA13304@cisco.com>
References: <87fva1fzwp.wl-jch@pps.univ-paris-diderot.fr> <CAA93jw57sNMPsKkL-W2m3s20DKsFZWNeGZSOgnmRTj3yz+Rgmg@mail.gmail.com> <EA20D83F-3E46-4484-AD65-518B1C3836DA@inf-net.nl> <87zj89ed6c.wl-jch@pps.univ-paris-diderot.fr> <86026D9A-78BB-4E5B-A6AA-27FB2E02441F@inf-net.nl> <CAGnRvuobcSA1wP__rscE+UAMAuxEgOqML5Ute1qcFLSHh+kLng@mail.gmail.com> <FA70CC1E-37E4-4824-A9F3-9711F1F84777@inf-net.nl> <CAGnRvuqUSXpTPCqG4fsNHA=tsge=FvUUXuouwoVsRy1Cw3-cug@mail.gmail.com> <87pp94czye.wl-jch@pps.univ-paris-diderot.fr> <9756.1424665439@sandelman.ca>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <9756.1424665439@sandelman.ca>
User-Agent: Mutt/1.4.2.2i
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/hhVR2Vg6274yeE6nEBwZ_QpTIwg>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] More about marginal links [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 23 Feb 2015 20:42:51 -0000

Some Q/Thoughts:

Q: Did i hear it correctly, there is no standard "show mac-address-table" like
CLI on linux/openwrt for built-in switches ?

Q: Is there ANY code in linux  that propagates L2 switch port status to the attached
L3 interface ? Especially if i do have a 1:1 mapping ? In commercial products
that commonly done.

Thought: In general, my feeling is that L2 link status is widely relied upon in commercial
product/dpeloyments. If homenet feels it can not rely on it due to the non-commercial nature
of its development platforms, thats an interesting aspect, especially because
it could impact an IETF standard that we'd like to see commercially implemented and then
the constraints could be different...

Funny ;-)

Toerless

On Sun, Feb 22, 2015 at 11:23:59PM -0500, Michael Richardson wrote:
> 
> Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr> wrote:
>     >> If you have hardware with a built-in switch that can report the link-speed,
> 
>     > The WNDR3700v2 under OpenWRT appears to do so:
> 
>     > # swconfig dev switch0 show | grep 'link:'
>     > link: port:0 link:down
>     > link: port:1 link:down
>     > link: port:2 link:up speed:100baseT full-duplex
>     > link: port:3 link:down
>     > link: port:4 link:down
>     > link: port:5 link:up speed:1000baseT full-duplex txflow rxflow auto
> 
>     > but to use this information, you need to know:
> 
>     > 1. that vlan1 on eth0 is connected to ports 0 through 3 of switch0;
>     > 2. that neighbour fe80::dead:beef is connected over port 2.
> 
>     > You could do (1) with a small amount of model-specific code (yuck), but
>     > I have no idea how to do (2).  Consult the ND cache to find out the
>     > neighbour's MAC, then find a way to snoop on the switch's forwarding table?
> 
> And assuming that you could do this, you still don't know that
> fe80::dead:beef isn't connected via some *other* layer-2 switch external to
> the WRT.
> 
> So, if anyone is basing their convergence time summaries upon loss of link,
> vs keep-alive timeouts, then they need to recalculate, because we are only
> rarely gonna see link-down.
> 
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>  -= IPv6 IoT consulting =-
> 
> 
> 



> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet


-- 
---
Toerless Eckert, eckert@cisco.com


From nobody Mon Feb 23 12:43:09 2015
Return-Path: <mcr@sandelman.ca>
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 2D2A41A3BA6 for <homenet@ietfa.amsl.com>; Mon, 23 Feb 2015 12:43:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 u4t29rUHiRbR for <homenet@ietfa.amsl.com>; Mon, 23 Feb 2015 12:43:06 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B37A31A6F2A for <homenet@ietf.org>; Mon, 23 Feb 2015 12:42:58 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id C9401203AA for <homenet@ietf.org>; Mon, 23 Feb 2015 15:51:06 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id 4C08B63A21; Mon, 23 Feb 2015 15:42:57 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 340E4637F4 for <homenet@ietf.org>; Mon, 23 Feb 2015 15:42:57 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "homenet\@ietf.org Group" <homenet@ietf.org>
In-Reply-To: <87ioessk9c.wl-jch@pps.univ-paris-diderot.fr>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E0FB64.8010009@openwrt.org> <87k2ziritt.wl-jch@pps.univ-paris-diderot.fr> <D80DC12D-AFBA-45D1-9D19-E4D4B24961FA@gmail.com> <755.1424662895@sandelman.ca> <87ioessk9c.wl-jch@pps.univ-paris-diderot.fr>
X-Mailer: MH-E 8.6; nmh 1.3-dev; GNU Emacs 24.4.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Mon, 23 Feb 2015 15:42:57 -0500
Message-ID: <15559.1424724177@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/JvA6geUifxN8OJzPQKMYZVWCxsI>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 23 Feb 2015 20:43:08 -0000

--=-=-=
Content-Type: text/plain


Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr> wrote:
    >> So assuming some decent high-power 802.11ac in the Bradford house
    >> (http://en.wikipedia.org/wiki/Eight_Is_Enough) to link the per-room router to
    >> legacy 802.11b and per-person (phone) router to BTLE/PAN, it means we have
    >> about 30 routers on the wifi.

    > I'm under opposing pressures relating to scaling.  A lot of people, like
    > you, seem to think it's irrelevant, some others feel very strongly about it.

I'm not claiming its irrelevant, I'm claiming that it won't bite us all at once.
I accept that some homenet-type installations will go up to 250 routers
(which is only 1 order of magnitude larger than 30, btw), but they won't go
up to 250 without some thought about it.  So I totally agree with you:

    > The thinking is that if Homenet routers are cheaply and widely available,
    > then people will use them for larger deployments; no amount of legislating
    > such uses out of scope will change that fact.  The obvious example would
    > be a hotel: why pay for a professionally installed network when you can
    > just plug in a bunch of $40 Homenet routers and be done with your customer
    > network.  I can well imagine a hotel using 200 routers.

but, what I'm claiming is that the 200 routers won't be in a single wifi
channel.    The network will get a small amount of tuning, if only because
the walls will get in the way and some people will have to run some cables in
places.  That's exactly what most of think: that to scale things we need
wired back hauls, so while we hit 250 routers in the routing table, we don't
have to accomodate 250 routers forming adjacencies on a single wifi channel.

    > If hotels don't meet your fancy -- think schools, think appartment blocks
    > in third world countries, think hippy communes.  Do we wish to explicitly
    > support such use cases?  Hopefully not.  But do we wish to have our
    > protocols collapse just because we didn't have the foresight to avoid
    > gratuitious limitations?

So, there are limitations like:
      struct router all_the_routers[256];

and then there are protocol collapses due to taking the entire channel for
adjacencies as happened with OLPC.  The trickle mechanism of DNCP ought to
deal with that.

What we need to do is to make sure that whatever parameters we pick for
scaling fail in a safe way when exceeded.  I'd rather that the router which
has HomeNet v1 parameters in it just stops when it reaches some limit rather
than cause congestion collapse.  The router will then get replaced (or
better, reflashed), but if not, it won't get in the way of the newer, better
tuned devices.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEVAwUBVOuQ0ICLcPvd0N1lAQJn9ggAkEnav7Lb+6tKJ4aocfqJsjSZzuOPsb7b
XQ1Kp+YBydowHxmWfr1i/XVy5wz6415MGfPmCasBz+M3oZU3MsPWGcmcUPf9o5GA
kEbxEb/itsYbaiYEEt/IoBDDw3iu0Dhg+TbFKC3YvLf7GedvyVUK5+p6StcmuYzH
VrG/ADG74Ji0kNsQuFZX+qr2hoM7F9rf9MAVvfMJuiOkm9sp5qCbnyHSeMQJ0CcK
xxzhFdR6n2qiW/7PU6l3cbI+2RGA0/IAI0rrw7R2WxV6PIp4i2Uc0yJdkcn7ek1c
/sazorpGqaXX7rw/XNro+khnZwpxKOubrPwwl28DP7PRI57exei0VQ==
=TQMr
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Mon Feb 23 16:37:43 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 269FF1A1ADB for <homenet@ietfa.amsl.com>; Mon, 23 Feb 2015 16:37:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35] autolearn=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 OKtD4jmhA7y9 for <homenet@ietfa.amsl.com>; Mon, 23 Feb 2015 16:37:40 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 547791A036F for <homenet@ietf.org>; Mon, 23 Feb 2015 16:37:40 -0800 (PST)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t1O0bcsG011369; Tue, 24 Feb 2015 01:37:38 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 3E68512606D; Tue, 24 Feb 2015 01:37:38 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id R-0lBK5-8WHy; Tue, 24 Feb 2015 01:37:36 +0100 (CET)
Received: from pirx.pps.jussieu.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id A39582BE42E; Tue, 24 Feb 2015 01:37:36 +0100 (CET)
Date: Tue, 24 Feb 2015 01:37:37 +0100
Message-ID: <87vbisrvou.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Michael Richardson <mcr+ietf@sandelman.ca>
In-Reply-To: <15559.1424724177@sandelman.ca>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <54E0FB64.8010009@openwrt.org> <87k2ziritt.wl-jch@pps.univ-paris-diderot.fr> <D80DC12D-AFBA-45D1-9D19-E4D4B24961FA@gmail.com> <755.1424662895@sandelman.ca> <87ioessk9c.wl-jch@pps.univ-paris-diderot.fr> <15559.1424724177@sandelman.ca>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Tue, 24 Feb 2015 01:37:38 +0100 (CET)
X-Miltered: at korolev with ID 54EBC7D2.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54EBC7D2.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54EBC7D2.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/pQhio9DSC1nCdF2AKjTuXAr4iNg>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Tue, 24 Feb 2015 00:37:42 -0000

> So, there are limitations like:
> struct router all_the_routers[256];
>
> and then there are protocol collapses due to taking the entire channel for
> adjacencies as happened with OLPC.

We're in full agreement about most of what you say.  Are you happy with
the current wording, or are you suggesting I change something?

-- Juliusz


From nobody Mon Feb 23 16:51:57 2015
Return-Path: <mcr@sandelman.ca>
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 28D231A1B6D for <homenet@ietfa.amsl.com>; Mon, 23 Feb 2015 16:51:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 D0E08uxi8doI for <homenet@ietfa.amsl.com>; Mon, 23 Feb 2015 16:51:54 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4A6641A1B4A for <homenet@ietf.org>; Mon, 23 Feb 2015 16:51:54 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id BE6C5203AA; Mon, 23 Feb 2015 20:00:02 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id 95F3163A21; Mon, 23 Feb 2015 19:51:52 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 77B86637F4; Mon, 23 Feb 2015 19:51:52 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Toerless Eckert <eckert@cisco.com>
In-Reply-To: <20150223204247.GA13304@cisco.com>
References: <87fva1fzwp.wl-jch@pps.univ-paris-diderot.fr> <CAA93jw57sNMPsKkL-W2m3s20DKsFZWNeGZSOgnmRTj3yz+Rgmg@mail.gmail.com> <EA20D83F-3E46-4484-AD65-518B1C3836DA@inf-net.nl> <87zj89ed6c.wl-jch@pps.univ-paris-diderot.fr> <86026D9A-78BB-4E5B-A6AA-27FB2E02441F@inf-net.nl> <CAGnRvuobcSA1wP__rscE+UAMAuxEgOqML5Ute1qcFLSHh+kLng@mail.gmail.com> <FA70CC1E-37E4-4824-A9F3-9711F1F84777@inf-net.nl> <CAGnRvuqUSXpTPCqG4fsNHA=tsge=FvUUXuouwoVsRy1Cw3-cug@mail.gmail.com> <87pp94czye.wl-jch@pps.univ-paris-diderot.fr> <9756.1424665439@sandelman.ca> <20150223204247.GA13304@cisco.com>
X-Mailer: MH-E 8.6; nmh 1.3-dev; GNU Emacs 24.4.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Mon, 23 Feb 2015 19:51:52 -0500
Message-ID: <4247.1424739112@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/MDEY85WeJekDzm2lhf0Mn0A25lk>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] More about marginal links [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Tue, 24 Feb 2015 00:51:56 -0000

--=-=-=
Content-Type: text/plain


Toerless Eckert <eckert@cisco.com> wrote:
    > Q: Did i hear it correctly, there is no standard "show mac-address-table" like
    > CLI on linux/openwrt for built-in switches ?

Correct, because there is no standard interface between the Linux kernel and
the switches. That's because switch chip manufacturers refuse to release
details except under very strong NDAs.   The partial exception, as I
understand it, is the switch chip in the OpenWRT supported SOCs are supposed
by "swconfig", but it's not integrated into the kernel.

This isn't a desireable state.


    > Q: Is there ANY code in linux  that propagates L2 switch port status to the attached
    > L3 interface ? Especially if i do have a 1:1 mapping ? In commercial products
    > that commonly done.

If you unplug the cable on a Linux router that has a supported interface
(i.e. e1000), the L3 status on IPv6 goes immediately.  There are hysterical
rainsons why they don't pull the IPv4 link status immediately.

    > Thought: In general, my feeling is that L2 link status is widely relied
    > upon in commercial product/dpeloyments. If homenet feels it can not
    > rely on it due to the non-commercial nature of its development
    > platforms, thats an interesting aspect, especially because it could
    > impact an IETF standard that we'd like to see commercially implemented
    > and then the constraints could be different...

1) any of the commercial home router vendors (cisco, linksys, belkin, dlink,
   etc.) could read the riot act to one of their higher-end silicon
   suppliers (the people with 1G/s capable L3 forwarding engines).  It only
   takes one to cave: that vendor gets to dictate kernel/switch APIs for the
   next ten years.

2) link status becomes meaningless when the end (home) user chains
   L2-switches together.  Professional operators naturally avoid doing this.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEVAwUBVOvLJICLcPvd0N1lAQKoswf+JAeULb1OlRU0xF0dLfB/4w+iBRn6BzQ0
YnUK5yMDs3/6CMluxvRnG+kPk3VN3WZ35XqCc8FaoyC9UBSLpZCOdXHXPI0aWxWe
ABAXvyplTC2F2YbNYXNv7RVl/I59LrUzqMXli03WjySZLpFM27KAfknQcrN2VfHs
lIflLBFf0PHLRirCYNnkqksOZU5Qu8uVK5ifEsZz9YuXxoSwVIjDfeE/yZlR7s0I
0q5rZSARpLwxjzvV+hMWkbQNhX4e6HHT7PgL/UEF4FX15hgPiCdf95U8xp3zn+q5
Dhiv1i6VuEp2gtxtJanNPru27EminYu212mo1ZNrPbc7yweFa6psiQ==
=6wxK
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Mon Feb 23 17:24:01 2015
Return-Path: <hansliu@gmail.com>
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 F15041A038C for <homenet@ietfa.amsl.com>; Mon, 23 Feb 2015 17:23:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.789
X-Spam-Level: *
X-Spam-Status: No, score=1.789 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MALFORMED_FREEMAIL=2.767, MISSING_HEADERS=1.021, SPF_PASS=-0.001] autolearn=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 BetnOsNKAzCz for <homenet@ietfa.amsl.com>; Mon, 23 Feb 2015 17:23:59 -0800 (PST)
Received: from mail-ig0-x233.google.com (mail-ig0-x233.google.com [IPv6:2607:f8b0:4001:c05::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B987E1A00E1 for <homenet@ietf.org>; Mon, 23 Feb 2015 17:23:58 -0800 (PST)
Received: by mail-ig0-f179.google.com with SMTP id l13so23230397iga.0 for <homenet@ietf.org>; Mon, 23 Feb 2015 17:23:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:cc :content-type; bh=5lrKpSz6i5UTjO3ZoDKZUbPmS69axrVb8RAdlq9c3lY=; b=DY8XOI4EqDjNNx8yfP8XGAlpBMgDAZfEv4bQFqYqMUcRmeMbdequLS9ti9fgDEObPm Gs0WSOJofFOpzL5SmoEipHBzUcf6Eu85hSeojd5yAOfivYKLW2LmW21lal4WD5I14OFe +JvgWFtobH3WkMnEYfjDceNOYl8X/rkuD/Rtv9OwsQBS/suKkIilggJhRA9t2HR8lgdJ OaVCdwXQrJ9VcJTcfyfeQdbTfz15QQnAwNXDOJilyPwELGSN8miSV9tkfmhXYMFY53MJ BYdZSJakKfs+bt+l4GI4o/0kddFVJos2F6K0MorR7/z5LEfI7uOgP3Whjj2UhslA1FBc IW4w==
MIME-Version: 1.0
X-Received: by 10.50.143.44 with SMTP id sb12mr16735429igb.3.1424741037985; Mon, 23 Feb 2015 17:23:57 -0800 (PST)
Received: by 10.64.23.164 with HTTP; Mon, 23 Feb 2015 17:23:57 -0800 (PST)
In-Reply-To: <CAA93jw7eGxPBNX+5LqX+qTYfRxNDxQpKo1fecUa2XH3bAKgvQQ@mail.gmail.com>
References: <CAA93jw7eGxPBNX+5LqX+qTYfRxNDxQpKo1fecUa2XH3bAKgvQQ@mail.gmail.com>
Date: Tue, 24 Feb 2015 09:23:57 +0800
Message-ID: <CAHEOdgs_BSELeMnfGu8FRJ4Ldi+8eZ4sjYW6k3eb2SOQLFv8mA@mail.gmail.com>
From: Hans Liu <hansliu@gmail.com>
Cc: HOMENET <homenet@ietf.org>
Content-Type: multipart/alternative; boundary=001a1134be8c775968050fcb5f08
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/7HDjk66YDqdS-uwovmtpV_y8ikQ>
Subject: Re: [homenet] A poll
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Tue, 24 Feb 2015 01:24:00 -0000

--001a1134be8c775968050fcb5f08
Content-Type: text/plain; charset=UTF-8

>
>
> 0) Have you managed to get ipv6 working at all? If so, how? What sort
> of problems did you encounter?
>

Yes. I use DIR-855L at home, PPPoE. The only problem I have so far is my
ISP gives only /64 via PD.


>
> 1) Have you attempted to deploy a routing protocol in your home? Which
> one, and why?
>

No.


>
> 2) Have you attempted to get hnetd's prefix distribution system
> working? (it supports linux mainline and openwrt presently)
>

Yes.


> 3) Do you use ethernet? How many clients in your home are ethernet
> connected?
>

No, everything goes Wi-Fi.


>
> 4) Do you use wifi? How many clients are wifi connected? Do you use
> range extenders?
>

Yes. I have around 12 devices connected to my Wi-Fi network.
Yes, I use range extenders. Wi-Fi and HomePlug.


>
> 5) How many devices do you think you will have connected to the
> network in your home in 5 years? How many now?
>

10 more, I guess?  Should be connected home devices, such as Thermostat,
smart plug, sensors, IPCam, ...etc.


>
> 6) Do you use any other network connected technologies (homeplug,
> 802.14, LTE, etc). If so, which ones, and why?
>

Yes.  HomePlug/Wi-Fi Extender and Z-Wave.


>
> 7) Do you use mdns service discovery?
>

Yes. We use mDNS-SD for D-Link Connected Home devices.


>
> 8) Why are you here? (especially, if your answers to 0-2, are "no")


>
>
>

--001a1134be8c775968050fcb5f08
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex"><br>
0) Have you managed to get ipv6 working at all? If so, how? What sort<br>
of problems did you encounter?<br></blockquote><div><br></div><div>Yes. I u=
se DIR-855L at home, PPPoE. The only problem I have so far is my ISP gives =
only /64 via PD.=C2=A0</div><div>=C2=A0</div><blockquote class=3D"gmail_quo=
te" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"=
>
<br>
1) Have you attempted to deploy a routing protocol in your home? Which<br>
one, and why?<br></blockquote><div><br></div><div>No.=C2=A0</div><div>=C2=
=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde=
r-left:1px #ccc solid;padding-left:1ex">
<br>
2) Have you attempted to get hnetd&#39;s prefix distribution system<br>
working? (it supports linux mainline and openwrt presently)<br></blockquote=
><div><br></div><div>Yes. =C2=A0=C2=A0</div><div><br></div><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pad=
ding-left:1ex">
<br>
3) Do you use ethernet? How many clients in your home are ethernet connecte=
d?<br></blockquote><div><br></div><div>No, everything goes Wi-Fi.=C2=A0</di=
v><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
4) Do you use wifi? How many clients are wifi connected? Do you use<br>
range extenders?<br></blockquote><div><br></div><div>Yes. I have around 12 =
devices connected to my Wi-Fi network.=C2=A0</div><div>Yes, I use range ext=
enders. Wi-Fi and HomePlug. =C2=A0</div><div>=C2=A0</div><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">
<br>
5) How many devices do you think you will have connected to the<br>
network in your home in 5 years? How many now?<br></blockquote><div><br></d=
iv><div>10 more, I guess?=C2=A0 Should be connected home devices, such as T=
hermostat, smart plug, sensors, IPCam, ...etc. =C2=A0</div><div>=C2=A0</div=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex">
<br>
6) Do you use any other network connected technologies (homeplug,<br>
802.14, LTE, etc). If so, which ones, and why?<br></blockquote><div><br></d=
iv><div>Yes.=C2=A0 HomePlug/Wi-Fi Extender and Z-Wave.=C2=A0</div><div>=C2=
=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde=
r-left:1px #ccc solid;padding-left:1ex">
<br>
7) Do you use mdns service discovery?<br></blockquote><div><br></div><div>Y=
es. We use mDNS-SD for D-Link Connected Home devices.=C2=A0</div><div>=C2=
=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde=
r-left:1px #ccc solid;padding-left:1ex">
<br>
8) Why are you here? (especially, if your answers to 0-2, are &quot;no&quot=
;)=C2=A0</blockquote><blockquote class=3D"gmail_quote" style=3D"margin:0 0 =
0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
<br><br></font></span></blockquote></div><div><br></div>
</div></div>

--001a1134be8c775968050fcb5f08--


From nobody Mon Feb 23 19:13:22 2015
Return-Path: <lorenzo@google.com>
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 749D41A009B for <homenet@ietfa.amsl.com>; Mon, 23 Feb 2015 19:13:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Level: 
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 3ibIMBT2mWoc for <homenet@ietfa.amsl.com>; Mon, 23 Feb 2015 19:13:20 -0800 (PST)
Received: from mail-ig0-x229.google.com (mail-ig0-x229.google.com [IPv6:2607:f8b0:4001:c05::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D45F91A0087 for <homenet@ietf.org>; Mon, 23 Feb 2015 19:13:19 -0800 (PST)
Received: by mail-ig0-f169.google.com with SMTP id hl2so25749365igb.0 for <homenet@ietf.org>; Mon, 23 Feb 2015 19:13:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=0UoHPkjothiTqvwK5TxcC+39bnC2EG3HlPyIjMaJMwc=; b=b/vYxYGLxNXZT+Iena43hZwQOZ85BIw8msFkru9kB9ZZhnoKnDDuR+o8BT7tqtONGE Gp+aGM4nzmZebTGn6TxFENIoV6T3TsSs0setRcQE4Su9JbivJlaz82tHZtI34vhl7ybM tDTq3OOK7GY/2cmPkoHNEp5cSXdERJj78iuWGPfHcXRTTljLDEeyHKhL9dxKxAL8rweF PXs4Af3S59xLCIOInyd9cYYtJ/osVYpXBO/wK9wpX2idjkphO+f+kd8Lbr0oLIfNm7Jk heIiC+KC/GFLUQ36gJUPRO6QdFRmTQyhUuf+KZvfdTSTGl5BoxLGbTP1jszM6OnmK6h7 79pA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=0UoHPkjothiTqvwK5TxcC+39bnC2EG3HlPyIjMaJMwc=; b=meLmAL10UgfP4iXkqjL6Jtf5Axvkwx3NCiTfpqioralobYzljcxq2I1nvrLygFuNbF n3I4m2GRUIvKSLBre8ve2+WaPYB6pcssU7X6fP9FpucZgUTyQoFTaLEDV7FxL+3FpqKl 0pFnItaDF8RYdZHDvcljWY7nRwaPBFBhyNfngCzl/nDNbuUjsKCrrToFHS/svxuBM3PM Dre8cDI6VWj4zhfnOVHA5wTHayKHgxrm2D4UZU9b6eOMAuKDyuYQwxkEiqYCp7aLuGKB YiTX3Cd7c2Boa/dPRKtZ1wuiweVIp4JsMvQhHaOrdNHFahhkYXoDp9cAxXrh5GQ/Uy5C xNOw==
X-Gm-Message-State: ALoCoQnKRJPEwC5nmzDOUQaQ0fYcmAzUaCE9rtjTtoZyhrAD8so+tmDd48YVzqO3v8Cb1WKvzY86
X-Received: by 10.107.152.211 with SMTP id a202mr18026790ioe.59.1424747599021;  Mon, 23 Feb 2015 19:13:19 -0800 (PST)
MIME-Version: 1.0
Received: by 10.64.33.104 with HTTP; Mon, 23 Feb 2015 19:12:58 -0800 (PST)
In-Reply-To: <CAA93jw7eGxPBNX+5LqX+qTYfRxNDxQpKo1fecUa2XH3bAKgvQQ@mail.gmail.com>
References: <CAA93jw7eGxPBNX+5LqX+qTYfRxNDxQpKo1fecUa2XH3bAKgvQQ@mail.gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Tue, 24 Feb 2015 12:12:58 +0900
Message-ID: <CAKD1Yr2N5xCcu1MGb-69aVko_0C4k5UW1snPSEFdpU629pz4xA@mail.gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Content-Type: multipart/alternative; boundary=001a1140f53888e5ee050fcce6dd
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/kfm0jf0ncHBXQA_zLA_mvyjGoYE>
Cc: HOMENET <homenet@ietf.org>
Subject: Re: [homenet] A poll
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Tue, 24 Feb 2015 03:13:21 -0000

--001a1140f53888e5ee050fcce6dd
Content-Type: text/plain; charset=UTF-8

On Sat, Feb 21, 2015 at 1:50 AM, Dave Taht <dave.taht@gmail.com> wrote:

> 0) Have you managed to get ipv6 working at all? If so, how? What sort
> of problems did you encounter?
>

Yes. The only problems were finding an ISP that supported it (Japan has...
special issues with IPv6), and occasional bugs in one of the two
ISP-provided home gateway boxes (which fortunately is optional).


> 1) Have you attempted to deploy a routing protocol in your home? Which
> one, and why?
>

No, I use hierarchical DHCPv6 PD.


> 2) Have you attempted to get hnetd's prefix distribution system
> working? (it supports linux mainline and openwrt presently)
>

No, because I only have one openwrt box.


> 3) Do you use ethernet? How many clients in your home are ethernet
> connected?
>

Everything that can be wired (including my laptop, via docking station) is
on 1Gbps wired Ethernet. All routers are connected to each other via
Ethernet.


> 4) Do you use wifi? How many clients are wifi connected? Do you use
> range extenders?
>

I try to avoid wifi because it's way too slow for my 1Gbps connection. I
also detest the unpredicability, high latency, jitter, and sucky multicast
behaviour of 802.11. On my main mobile device, I often prefer LTE over wifi
because it's fast enough, and doesn't get interrupted when I leave home or
arrive home. No range extenders because Japanese homes aren't big enough to
need them :-)


> 5) How many devices do you think you will have connected to the
> network in your home in 5 years? How many now?
>

2 laptops, 5-10 mobile devices (tablets/phones, but only a few of them on
at any given time), one raspberry pi and a couple of routers.

6) Do you use any other network connected technologies (homeplug,
> 802.14, LTE, etc). If so, which ones, and why?
>

No.


> 7) Do you use mdns service discovery?
>

I would like to for things like Chromecast, but I can't because it doesn't
work across routers. I have to use more than one router because my main
wifi is NAT64 / DNS64 / 464xlat, and the ISP router doesn't support DNS64.


> 8) Why are you here? (especially, if your answers to 0-2, are "no")
>

It would be nice if I didn't have to do hierarchical DHCPv6 PD. It would be
nice if MDNS worked.

--001a1140f53888e5ee050fcce6dd
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On S=
at, Feb 21, 2015 at 1:50 AM, Dave Taht <span dir=3D"ltr">&lt;<a href=3D"mai=
lto:dave.taht@gmail.com" target=3D"_blank">dave.taht@gmail.com</a>&gt;</spa=
n> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px =
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-=
style:solid;padding-left:1ex">0) Have you managed to get ipv6 working at al=
l? If so, how? What sort<br>
of problems did you encounter?<br></blockquote><div><br></div><div>Yes. The=
 only problems were finding an ISP that supported it (Japan has... special =
issues with IPv6), and occasional bugs in one of the two ISP-provided home =
gateway boxes (which fortunately is optional).</div><div>=C2=A0</div><block=
quote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-w=
idth:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding=
-left:1ex">1) Have you attempted to deploy a routing protocol in your home?=
 Which<br>
one, and why?<br></blockquote><div><br></div><div>No, I use hierarchical DH=
CPv6 PD.</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"m=
argin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204=
,204);border-left-style:solid;padding-left:1ex">2) Have you attempted to ge=
t hnetd&#39;s prefix distribution system<br>
working? (it supports linux mainline and openwrt presently)<br></blockquote=
><div><br></div><div>No, because I only have one openwrt box.</div><div>=C2=
=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8e=
x;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-styl=
e:solid;padding-left:1ex">3) Do you use ethernet? How many clients in your =
home are ethernet connected?<br></blockquote><div><br></div><div>Everything=
 that can be wired (including my laptop, via docking station) is on 1Gbps w=
ired Ethernet. All routers are connected to each other via Ethernet.</div><=
div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0=
px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-le=
ft-style:solid;padding-left:1ex">4) Do you use wifi? How many clients are w=
ifi connected? Do you use<br>
range extenders?<br></blockquote><div><br></div><div>I try to avoid wifi be=
cause it&#39;s way too slow for my 1Gbps connection. I also detest the unpr=
edicability, high latency, jitter, and sucky multicast behaviour of 802.11.=
 On my main mobile device, I often prefer LTE over wifi because it&#39;s fa=
st enough, and doesn&#39;t get interrupted when I leave home or arrive home=
. No range extenders because Japanese homes aren&#39;t big enough to need t=
hem :-)</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,=
204);border-left-style:solid;padding-left:1ex">5) How many devices do you t=
hink you will have connected to the<br>
network in your home in 5 years? How many now?<br></blockquote><div><br></d=
iv><div>2 laptops, 5-10 mobile devices (tablets/phones, but only a few of t=
hem on at any given time), one raspberry pi and a couple of routers.</div><=
div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px=
 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left=
-style:solid;padding-left:1ex">6) Do you use any other network connected te=
chnologies (homeplug,<br>
802.14, LTE, etc). If so, which ones, and why?<br></blockquote><div><br></d=
iv><div>No.</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(20=
4,204,204);border-left-style:solid;padding-left:1ex">7) Do you use mdns ser=
vice discovery?<br></blockquote><div><br></div><div>I would like to for thi=
ngs like Chromecast, but I can&#39;t because it doesn&#39;t work across rou=
ters. I have to use more than one router because my main wifi is NAT64 / DN=
S64 / 464xlat, and the ISP router doesn&#39;t support DNS64.</div><div>=C2=
=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8e=
x;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-styl=
e:solid;padding-left:1ex">8) Why are you here? (especially, if your answers=
 to 0-2, are &quot;no&quot;)<br></blockquote><div><br></div><div>It would b=
e nice if I didn&#39;t have to do hierarchical DHCPv6 PD. It would be nice =
if MDNS worked.</div></div></div></div>

--001a1140f53888e5ee050fcce6dd--


From nobody Tue Feb 24 00:29:23 2015
Return-Path: <gert@Space.Net>
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 8995D1A871F for <homenet@ietfa.amsl.com>; Tue, 24 Feb 2015 00:29:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.61
X-Spam-Level: 
X-Spam-Status: No, score=-2.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 63pAYxx6QPO2 for <homenet@ietfa.amsl.com>; Tue, 24 Feb 2015 00:29:19 -0800 (PST)
Received: from mobil.space.net (mobil.space.net [195.30.115.67]) (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 94C751A871B for <homenet@ietf.org>; Tue, 24 Feb 2015 00:29:18 -0800 (PST)
X-Original-To: homenet@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id 2BD0D6004E for <homenet@ietf.org>; Tue, 24 Feb 2015 09:29:17 +0100 (CET)
X-SpaceNet-Relay: true
Received: from moebius3.space.net (moebius3.Space.Net [IPv6:2001:608:2:2::250]) by mobil.space.net (Postfix) with ESMTPS id 01EE06010D for <homenet@ietf.org>; Tue, 24 Feb 2015 09:29:16 +0100 (CET)
Received: (qmail 30826 invoked by uid 1007); 24 Feb 2015 09:29:16 +0100
Date: Tue, 24 Feb 2015 09:29:16 +0100
From: Gert Doering <gert@space.net>
To: Toerless Eckert <eckert@cisco.com>
Message-ID: <20150224082916.GV34798@Space.Net>
References: <CAA93jw57sNMPsKkL-W2m3s20DKsFZWNeGZSOgnmRTj3yz+Rgmg@mail.gmail.com> <EA20D83F-3E46-4484-AD65-518B1C3836DA@inf-net.nl> <87zj89ed6c.wl-jch@pps.univ-paris-diderot.fr> <86026D9A-78BB-4E5B-A6AA-27FB2E02441F@inf-net.nl> <CAGnRvuobcSA1wP__rscE+UAMAuxEgOqML5Ute1qcFLSHh+kLng@mail.gmail.com> <FA70CC1E-37E4-4824-A9F3-9711F1F84777@inf-net.nl> <CAGnRvuqUSXpTPCqG4fsNHA=tsge=FvUUXuouwoVsRy1Cw3-cug@mail.gmail.com> <87pp94czye.wl-jch@pps.univ-paris-diderot.fr> <9756.1424665439@sandelman.ca> <20150223204247.GA13304@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20150223204247.GA13304@cisco.com>
X-NCC-RegID: de.space
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/XkSSgg_IPAiHOs_EzjP9Z5poHHo>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] More about marginal links [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Tue, 24 Feb 2015 08:29:21 -0000

Hi,

On Mon, Feb 23, 2015 at 12:42:47PM -0800, Toerless Eckert wrote:
> Q: Did i hear it correctly, there is no standard "show mac-address-table" like
> CLI on linux/openwrt for built-in switches ?

Right.  Usually communication to these built-in switches is limited due
to lack of documentation, lack of developer time, and so on - so if you
get VLAN configuration and link status, it's already a win.

> Q: Is there ANY code in linux  that propagates L2 switch port status to the attached
> L3 interface ? Especially if i do have a 1:1 mapping ? In commercial products
> that commonly done.

Not that I know of.

It does not really matter here, though - because you can't rely on the
L2 link status to convey end-to-end sanity, as there can always be an
intermediate L2 switch that links "to you" but lost the link on the other 
end... (and this is where ethernet OAM etc. comes into play in commercial
implementations)

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444           USt-IdNr.: DE813185279


From nobody Tue Feb 24 03:15:08 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 BCD1E1A044F for <homenet@ietfa.amsl.com>; Tue, 24 Feb 2015 03:15:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35] autolearn=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 u2ZbB-rxPT5o for <homenet@ietfa.amsl.com>; Tue, 24 Feb 2015 03:15:06 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 0EF8D1A0263 for <homenet@ietf.org>; Tue, 24 Feb 2015 03:15:05 -0800 (PST)
Received: from potemkin.univ-paris7.fr (potemkin.univ-paris7.fr [IPv6:2001:660:3301:8000::1:1]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t1OBF1pi017376 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 24 Feb 2015 12:15:01 +0100
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by potemkin.univ-paris7.fr (8.14.4/8.14.4/relay2/56228) with ESMTP id t1OBF1Z0019459; Tue, 24 Feb 2015 12:15:01 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 676642C2695; Tue, 24 Feb 2015 12:15:01 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id SknXW3mR8tim; Tue, 24 Feb 2015 12:14:59 +0100 (CET)
Received: from pirx.pps.jussieu.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 13C4D2C2691; Tue, 24 Feb 2015 12:14:58 +0100 (CET)
Date: Tue, 24 Feb 2015 12:15:00 +0100
Message-ID: <87a903ef2j.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Toerless Eckert <eckert@cisco.com>
In-Reply-To: <20150223204247.GA13304@cisco.com>
References: <87fva1fzwp.wl-jch@pps.univ-paris-diderot.fr> <CAA93jw57sNMPsKkL-W2m3s20DKsFZWNeGZSOgnmRTj3yz+Rgmg@mail.gmail.com> <EA20D83F-3E46-4484-AD65-518B1C3836DA@inf-net.nl> <87zj89ed6c.wl-jch@pps.univ-paris-diderot.fr> <86026D9A-78BB-4E5B-A6AA-27FB2E02441F@inf-net.nl> <CAGnRvuobcSA1wP__rscE+UAMAuxEgOqML5Ute1qcFLSHh+kLng@mail.gmail.com> <FA70CC1E-37E4-4824-A9F3-9711F1F84777@inf-net.nl> <CAGnRvuqUSXpTPCqG4fsNHA=tsge=FvUUXuouwoVsRy1Cw3-cug@mail.gmail.com> <87pp94czye.wl-jch@pps.univ-paris-diderot.fr> <9756.1424665439@sandelman.ca> <20150223204247.GA13304@cisco.com>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]); Tue, 24 Feb 2015 12:15:01 +0100 (CET)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Tue, 24 Feb 2015 12:15:01 +0100 (CET)
X-Miltered: at korolev with ID 54EC5D35.004 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 54EC5D35.006 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54EC5D35.004 from potemkin.univ-paris7.fr/potemkin.univ-paris7.fr/null/potemkin.univ-paris7.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Enveloppe: 54EC5D35.006 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54EC5D35.004 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 54EC5D35.006 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/1A_wyu7_UWOJmZWo_8DKfFwTvz0>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: [homenet] L2 link status [was: More about marginal links]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Tue, 24 Feb 2015 11:15:07 -0000

> Thought: In general, my feeling is that L2 link status is widely relied
> upon in commercial product/dpeloyments. If homenet feels it can not rely
> on it due to the non-commercial nature of its development platforms,
> thats an interesting aspect, especially because it could impact an IETF
> standard that we'd like to see commercially implemented and then the
> constraints could be different...

Are you referring to the routing protocol comparison, or to something else?

I have the impression that Babel and IS-IS behave essentially the same
wrt. L2 status -- they both converge fast enough after link status has
been established, and they essentially provide the same facilities for
application-layer link sensing (IMHO Babel's Hello/IHU subprotocol is
slightly more flexible, but that's probably not a big deal).

As to wireless links -- as far as I'm aware, making efficient use of
wireless L2 information in a routing protocol is an open research problem.

-- Juliusz


From nobody Tue Feb 24 05:14:45 2015
Return-Path: <mcr@sandelman.ca>
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 B0C891A1A54 for <homenet@ietfa.amsl.com>; Tue, 24 Feb 2015 05:14:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 ekyARoqWqa_V for <homenet@ietfa.amsl.com>; Tue, 24 Feb 2015 05:14:43 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 633D91A1A99 for <homenet@ietf.org>; Tue, 24 Feb 2015 05:14:40 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 82A9F20098 for <homenet@ietf.org>; Tue, 24 Feb 2015 08:22:50 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id 8614163A21; Tue, 24 Feb 2015 08:14:38 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 6DA37637F4 for <homenet@ietf.org>; Tue, 24 Feb 2015 08:14:38 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: homenet@ietf.org
In-Reply-To: <alpine.DEB.2.02.1502230938220.4007@uplift.swm.pp.se>
References: <2697.1424653791@sandelman.ca> <20150223020242.GT26102@cisco.com> <alpine.DEB.2.02.1502230938220.4007@uplift.swm.pp.se>
X-Mailer: MH-E 8.6; nmh 1.3-dev; GNU Emacs 24.4.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Tue, 24 Feb 2015 08:14:38 -0500
Message-ID: <15818.1424783678@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/V8cg52-OvUa2VbGUHXVzaJLjKdw>
Subject: [homenet] homenet hardware requirements
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Tue, 24 Feb 2015 13:14:44 -0000

--=-=-=
Content-Type: text/plain


Mikael wrote privately (and I asked to quote):
    > Since I'm designing for a network with gig speed access to the home, when
    > someone comes and says they want to take into account a 5 year old device
    > with 4 MB flash and a 5 year old slow CPU accessing the network over bad
    > wifi, then it's quite unstandable that the solutions proposed are going to be
    > very different. A lot of these different expectations came up during the
    > discussion, and also some issues that hadn't been adressed so far (for
    > instance if a multi-AP home would have a shared L2 or not), multicast
    > routing, and others.

I think this is an interesting point.
Someone building a FTTH homenet will not have such slow devices at the edge.

But, here is my response: the old devices don't get thrown out if they are
owned by the end user.  Ideally, they get reflashed (usually not), and get
pushed into less busy parts of the (home) network.  This is the same thing
that happens with the core routers of 2001; they were often the edge routers of
2008.  When I sold routing ASICs, the flexibility was one of the features we talked about.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEVAwUBVOx5PoCLcPvd0N1lAQI/LwgAneLB4hb690idtjNa41YOKmIniOr5GF6q
4VgN7mxyc+UOH90JrKsez8vRP+FGkU4xlPywgbDqRhuoICrwwrEDlj9YeAApa/Aj
UZyjgTEKd84v0yAORlfEW8OULKBeOZ8e1Yk/7hBLluLEf0A0jZAQKD2I5SDO98J5
45vWKH8fYgSDYT3u4kndt1VofSubkJc4Hd7knab8YAQhCpRj474qkIrbNXM3ZUWM
GIhHFRoGjbCi0lxhNW3OeRZUIWdWGiBwRKFbPrTkfwaeEH3aG5y9nc4UlkRiK4Zr
n4BVMHKepYxlG7haj/UNRxrFXfQJO9OvXFBm8t96ZqIJiepYFYNAyg==
=IyNB
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Tue Feb 24 10:36:59 2015
Return-Path: <mark@mbaugher.com>
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 684421A8775 for <homenet@ietfa.amsl.com>; Tue, 24 Feb 2015 10:36:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.501
X-Spam-Level: 
X-Spam-Status: No, score=-0.501 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, SPF_HELO_PASS=-0.001] 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 NWBiF3ex-C1h for <homenet@ietfa.amsl.com>; Tue, 24 Feb 2015 10:36:57 -0800 (PST)
Received: from agora.rdrop.com (agora.rdrop.com [IPv6:2607:f678:1010::34]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8BCA21A1BF8 for <homenet@ietf.org>; Tue, 24 Feb 2015 10:36:57 -0800 (PST)
Received: from [192.168.1.36] (c-67-168-203-232.hsd1.or.comcast.net [67.168.203.232]) (authenticated bits=0) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id t1OIaa7X072868 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Tue, 24 Feb 2015 10:36:41 -0800 (PST) (envelope-from mark@mbaugher.com)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Mark Baugher <mark@mbaugher.com>
In-Reply-To: <CAA93jw4ZF8=QFMGmb1uPB+xxcNHadSZCEMkTTuDfOHrABWg3Mg@mail.gmail.com>
Date: Tue, 24 Feb 2015 10:36:37 -0800
Content-Transfer-Encoding: 7bit
Message-Id: <4C09C5D0-7CB9-439A-BFB1-22BC57CA9207@mbaugher.com>
References: <CAA93jw7eGxPBNX+5LqX+qTYfRxNDxQpKo1fecUa2XH3bAKgvQQ@mail.gmail.com> <BB621A07-282E-4814-9D56-3EFBF87814D0@iki.fi> <71C98A06-0B23-4916-BFF8-CCF663A3F0A0@fugue.com> <87zj88b9xf.wl-jch@pps.univ-paris-diderot.fr> <CAA93jw4ZF8=QFMGmb1uPB+xxcNHadSZCEMkTTuDfOHrABWg3Mg@mail.gmail.com>
To: Dave Taht <dave.taht@gmail.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/KfUZuSZrT79NXe873L9j8Q7HzZQ>
Cc: HOMENET <homenet@ietf.org>, Ted Lemon <mellon@fugue.com>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] OpenWRT hardware [was: A poll]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Tue, 24 Feb 2015 18:36:59 -0000

On Feb 20, 2015, at 2:22 PM, Dave Taht <dave.taht@gmail.com> wrote:

> On Fri, Feb 20, 2015 at 12:33 PM, Juliusz Chroboczek
> <jch@pps.univ-paris-diderot.fr> wrote:
>>> I'd be a bit curious to know what people are using for test hardware.
>> 
>> The WNDR3800/WNDR3700v2 is still my favourite.  I've still got a couple
>> Asus 500GP v1, and they're just fine if you don't need 802.11n and can
>> fit in the slightly more limited flash.
> 
> Despite evaluating well over 60 products and chipsets in the past 3
> years, I have yet to find something as nice as the wndr3800 as either
> a R&D or day to day ultra-reliable home router.

That's been my experience, although I have not evaluated dozens of routers.
Of the 8 or so that I have used (from several different vendors), the 3800
had among the most secure default settings:  It doesn't allow someone
to take ownership of the device using a well-known password through a Wi-Fi 
interface.

Mark


From nobody Tue Feb 24 14:57:09 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 549C91A906B for <homenet@ietfa.amsl.com>; Tue, 24 Feb 2015 14:57:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.349
X-Spam-Level: 
X-Spam-Status: No, score=0.349 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HELO_EQ_FR=0.35] autolearn=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 7HL4AlSqbO-5 for <homenet@ietfa.amsl.com>; Tue, 24 Feb 2015 14:57:07 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 958581A906A for <homenet@ietf.org>; Tue, 24 Feb 2015 14:57:05 -0800 (PST)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t1OMv3hb005820; Tue, 24 Feb 2015 23:57:04 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id D2F7A2C26E0; Tue, 24 Feb 2015 23:57:03 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id W6mbhmrx4BZe; Tue, 24 Feb 2015 23:57:02 +0100 (CET)
Received: from pirx.pps.jussieu.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id B84FB2C26D8; Tue, 24 Feb 2015 23:56:57 +0100 (CET)
Date: Tue, 24 Feb 2015 23:56:59 +0100
Message-ID: <87sidudikk.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Markus Stenberg <markus.stenberg@iki.fi>
In-Reply-To: <BB38C59C-D71D-4AA0-ABFE-04D557C1DCCD@iki.fi>
References: <8761at9vx5.wl-jch@pps.univ-paris-diderot.fr> <7D8C2976-1649-4349-9E90-E24DD2848086@iki.fi> <87lhjosla1.wl-jch@pps.univ-paris-diderot.fr> <BB38C59C-D71D-4AA0-ABFE-04D557C1DCCD@iki.fi>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Tue, 24 Feb 2015 23:57:04 +0100 (CET)
X-Miltered: at korolev with ID 54ED01BF.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54ED01BF.001 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54ED01BF.001 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/ASCYRZ7LkHuHWxLplGMAuMCSL-U>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] DNCP questions
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Tue, 24 Feb 2015 22:57:08 -0000

>> should not send packets larger than 1500 octets unless it has assurance
>> that the destination is capable of reassembling packets of that larger
>> size.

> I guess this is another MUST to be added to HNCP text (DNCP itself is
> not IPv6-specific as such).

You mean that every HNCP node MUST ba able to accept packets of up to 64kB?
What's the status of typical embedded stacks?

-- Juliusz


From nobody Tue Feb 24 15:10:13 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 544591A0076 for <homenet@ietfa.amsl.com>; Tue, 24 Feb 2015 15:10:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.349
X-Spam-Level: 
X-Spam-Status: No, score=0.349 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, HELO_EQ_FR=0.35] autolearn=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 ZZu3J70tBo5H for <homenet@ietfa.amsl.com>; Tue, 24 Feb 2015 15:10:11 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 402A11A0070 for <homenet@ietf.org>; Tue, 24 Feb 2015 15:10:11 -0800 (PST)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t1ONA9ND010404; Wed, 25 Feb 2015 00:10:09 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id CD9C36E080; Wed, 25 Feb 2015 00:10:09 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id 2KEG3FODMqUR; Wed, 25 Feb 2015 00:10:08 +0100 (CET)
Received: from pirx.pps.jussieu.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 0D5296E07F; Wed, 25 Feb 2015 00:10:08 +0100 (CET)
Date: Wed, 25 Feb 2015 00:10:09 +0100
Message-ID: <87r3tedhym.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Markus Stenberg <markus.stenberg@iki.fi>
In-Reply-To: <B5B68563-91D5-455C-A3AB-B1B3969302B7@iki.fi>
References: <8761at9vx5.wl-jch@pps.univ-paris-diderot.fr> <7D8C2976-1649-4349-9E90-E24DD2848086@iki.fi> <874mqcsh98.wl-jch@pps.univ-paris-diderot.fr> <B5B68563-91D5-455C-A3AB-B1B3969302B7@iki.fi>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Wed, 25 Feb 2015 00:10:09 +0100 (CET)
X-Miltered: at korolev with ID 54ED04D1.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54ED04D1.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54ED04D1.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/IoZzuO1kVJJuqcwPwWaIY3cuT-I>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] DNCP questions
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Tue, 24 Feb 2015 23:10:12 -0000

>> Another question -- is it possible to participate in Trickle-driven
>> flooding without building the full topology graph?

> The current answer based on strict reading of the spec is no.
[...]
> Is this desirable to be changed? Probably so. 

There's not only the stub case that you consider, but also the pure
client/forwarder node -- a node that doesn't wish to publish any data, but
uses static HNCP data, and serves as a link between two parts of the
network.  Ideally, such a node should not contribute any replicated state.

(Note that a Babel/AHCP router that doesn't announce any routes
contributes no state whatsoever to non-neighbouring nodes.  So you can add
arbitrary many intermediary hops with no cost incurred by distant nodes.)

The reason I'm asking is somewhat out of scope for Homenet -- I'm looking
into deprecating AHCP in mesh networks in favour of a subset implementation
of HNCP.  AHCP is a very simple protocol, and one can implement an AHCP
client/forwarder in constant space.  Not so with HNCP -- in HNCP, every
node has a copy of the topology, and contributes a vertex to the replicated
neighbour graph.

HNCP is naive link state, with no network nodes (pseudonodes) and no
DR/DIS/MPR election.  So its scaling is quadratic in the worst case.
Consider a network containing a switched Ethernet backbone consisting
a mere 30 routers.  Unless I'm missing something, this backbone will
contribute no less than 30 vertices and 435 edges in the neighbour graph,
and this state will be duplicated in every single node in the network.

There's an obvious solution -- it is to have pure client nodes that
participate in Trickle but don't contribute a vertex to the neighbour
graph.  But HNCP doesn't support that.

-- Juliusz


From nobody Tue Feb 24 16:26:10 2015
Return-Path: <andrewmcgr@google.com>
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 A78E11A1A31 for <homenet@ietfa.amsl.com>; Tue, 24 Feb 2015 16:26:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.389
X-Spam-Level: 
X-Spam-Status: No, score=-1.389 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 l1gQ_YAT5rHv for <homenet@ietfa.amsl.com>; Tue, 24 Feb 2015 16:26:07 -0800 (PST)
Received: from mail-qg0-x232.google.com (mail-qg0-x232.google.com [IPv6:2607:f8b0:400d:c04::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 38F991A1A2C for <homenet@ietf.org>; Tue, 24 Feb 2015 16:26:07 -0800 (PST)
Received: by mail-qg0-f50.google.com with SMTP id e89so439166qgf.9 for <homenet@ietf.org>; Tue, 24 Feb 2015 16:26:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=rtCBry8n3nLw0JRdC6g4VuAAnhzB2wD0jnBbSzGPRaM=; b=Hn25v1IB3Bgw7PHa6zHIw3RpW9E43QWIRYV4VBPteK6T5fr8fQNQ9wwZpgqSH91rtp HqsvO7Oc29xOeKsZ39afVj/EnGL/2V+krmGdA1zX+4TQJGXTqKBA/DGf36tvE2/3qRxo CZkTywDoh6AihrpSD/aNx7D40cLFJWzxCmYHjkk3WYkEgMBQaeEcwEdsboFmTUAczLX/ f5dSj2BVGDb9l4BXlPiCEA8GrOILfh1cfwUfQpMHfVBKib1eRlZ7OY1YFryxFXg2aui6 CgPci6D6NytynB2nky5YNQhg8/XybwmvqofmUo/T237gyg6P0ePoJGidgYce1PSkAK1Z 7W1w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=rtCBry8n3nLw0JRdC6g4VuAAnhzB2wD0jnBbSzGPRaM=; b=X1py5leZWfmJ0J+aXM+vbk/EnfrUMyFGiKNywum6bcneGcpLW3b2wJ+SxLP7blFZXc bt1eV2P1L+mYAl50jxEc8O3uLvGhl/ESbGdWRhtBXvuh1SVR3Mim+Yu2q39VgwwXmnfR dQB2HZAzjXgpJLQPXQ9jf4WWgyizF5B4rszFw+UwGXI85UzunkyXKYXKZd5D2aI2n1OF FCE6gvbouOytlynlPPJJrGeB+VDRqm2lJ9KKWfYrB/A+44P0iAPDXK0/kJECeidghiS7 aIptLPE9bDA8YgFq6jyfwLb10GgVRnLY2nLYwmqFMCWmsvVSklZDoa63jv3FXRpEiRin ZrGw==
X-Gm-Message-State: ALoCoQlmQqvLkbXF6UV39MbZNhQqyLA+cZBfL9U478laJN8Q3zNta9IwmFhYd59pzDw4jpRvBhnZ
MIME-Version: 1.0
X-Received: by 10.140.218.202 with SMTP id o193mr1276292qhb.13.1424823966326;  Tue, 24 Feb 2015 16:26:06 -0800 (PST)
Received: by 10.96.68.74 with HTTP; Tue, 24 Feb 2015 16:26:06 -0800 (PST)
In-Reply-To: <4C09C5D0-7CB9-439A-BFB1-22BC57CA9207@mbaugher.com>
References: <CAA93jw7eGxPBNX+5LqX+qTYfRxNDxQpKo1fecUa2XH3bAKgvQQ@mail.gmail.com> <BB621A07-282E-4814-9D56-3EFBF87814D0@iki.fi> <71C98A06-0B23-4916-BFF8-CCF663A3F0A0@fugue.com> <87zj88b9xf.wl-jch@pps.univ-paris-diderot.fr> <CAA93jw4ZF8=QFMGmb1uPB+xxcNHadSZCEMkTTuDfOHrABWg3Mg@mail.gmail.com> <4C09C5D0-7CB9-439A-BFB1-22BC57CA9207@mbaugher.com>
Date: Wed, 25 Feb 2015 11:26:06 +1100
Message-ID: <CAPRuP3kwWyA-oJi7ckPOT+L7XyxCa7aWSw3B9vHXzuiT6AFwjQ@mail.gmail.com>
From: Andrew Mcgregor <andrewmcgr@google.com>
To: Mark Baugher <mark@mbaugher.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/mLfBEJxVvdWxa20vFcMOH7BPqWQ>
Cc: HOMENET <homenet@ietf.org>, Ted Lemon <mellon@fugue.com>, Dave Taht <dave.taht@gmail.com>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] OpenWRT hardware [was: A poll]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Wed, 25 Feb 2015 00:26:08 -0000

I should note that the Netgear series includes all these model numbers:
WNDR37AV v2
WNDR3700 v2 and v4 (NOT v3!!!)
WNDR3800
WNDR4300

Of which, the 4300 is probably the one to have, having 3x3 radios on
both bands and 128 MB of flash (3700 v4 also has the large flash).
Otherwise the differences are minor.

The TP-Link Archer C7 seems quite nice, although I've only been
playing with it less than 24 hours; my opernwrt build seems unable to
send more than 100 Mbps over the ethernet, but the WiFi side is quite
fast; I saw 270 Mbps of TCP sourced from iperf on the device,
undoubtedly CPU limited.

On 25 February 2015 at 05:36, Mark Baugher <mark@mbaugher.com> wrote:
>
> On Feb 20, 2015, at 2:22 PM, Dave Taht <dave.taht@gmail.com> wrote:
>
>> On Fri, Feb 20, 2015 at 12:33 PM, Juliusz Chroboczek
>> <jch@pps.univ-paris-diderot.fr> wrote:
>>>> I'd be a bit curious to know what people are using for test hardware.
>>>
>>> The WNDR3800/WNDR3700v2 is still my favourite.  I've still got a couple
>>> Asus 500GP v1, and they're just fine if you don't need 802.11n and can
>>> fit in the slightly more limited flash.
>>
>> Despite evaluating well over 60 products and chipsets in the past 3
>> years, I have yet to find something as nice as the wndr3800 as either
>> a R&D or day to day ultra-reliable home router.
>
> That's been my experience, although I have not evaluated dozens of routers.
> Of the 8 or so that I have used (from several different vendors), the 3800
> had among the most secure default settings:  It doesn't allow someone
> to take ownership of the device using a well-known password through a Wi-Fi
> interface.
>
> Mark
>
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet



-- 
Andrew McGregor | SRE | andrewmcgr@google.com | +61 4 1071 2221


From nobody Tue Feb 24 18:15:22 2015
Return-Path: <mellon@fugue.com>
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 332641A9073 for <homenet@ietfa.amsl.com>; Tue, 24 Feb 2015 18:15:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 42oPAOI1Uo26 for <homenet@ietfa.amsl.com>; Tue, 24 Feb 2015 18:15:16 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id BDE301A1A0B for <homenet@ietf.org>; Tue, 24 Feb 2015 18:15:16 -0800 (PST)
Received: from [10.0.20.107] (c-71-233-43-215.hsd1.nh.comcast.net [71.233.43.215]) by toccata.fugue.com (Postfix) with ESMTPSA id 2D02723802FA; Tue, 24 Feb 2015 21:15:13 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <CAPRuP3kwWyA-oJi7ckPOT+L7XyxCa7aWSw3B9vHXzuiT6AFwjQ@mail.gmail.com>
Date: Tue, 24 Feb 2015 21:15:10 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <5D8537E9-AECD-4FAE-B5FF-77458A5F21E4@fugue.com>
References: <CAA93jw7eGxPBNX+5LqX+qTYfRxNDxQpKo1fecUa2XH3bAKgvQQ@mail.gmail.com> <BB621A07-282E-4814-9D56-3EFBF87814D0@iki.fi> <71C98A06-0B23-4916-BFF8-CCF663A3F0A0@fugue.com> <87zj88b9xf.wl-jch@pps.univ-paris-diderot.fr> <CAA93jw4ZF8=QFMGmb1uPB+xxcNHadSZCEMkTTuDfOHrABWg3Mg@mail.gmail.com> <4C09C5D0-7CB9-439A-BFB1-22BC57CA9207@mbaugher.com> <CAPRuP3kwWyA-oJi7ckPOT+L7XyxCa7aWSw3B9vHXzuiT6AFwjQ@mail.gmail.com>
To: Andrew Mcgregor <andrewmcgr@google.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/hRTuCxpehBUI-24wlGFwh_s2m1g>
Cc: HOMENET <homenet@ietf.org>, Dave Taht <dave.taht@gmail.com>, Mark Baugher <mark@mbaugher.com>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
Subject: Re: [homenet] OpenWRT hardware [was: A poll]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Wed, 25 Feb 2015 02:15:19 -0000

On Feb 24, 2015, at 7:26 PM, Andrew Mcgregor <andrewmcgr@google.com> =
wrote:
> WNDR4300

It looks like they released a new version in December of 2014 that isn't =
supported by OpenWRT. :(


From nobody Tue Feb 24 21:35:20 2015
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 008861A90AA for <homenet@ietfa.amsl.com>; Tue, 24 Feb 2015 21:35:20 -0800 (PST)
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 p9i3YuwnytaO for <homenet@ietfa.amsl.com>; Tue, 24 Feb 2015 21:35:18 -0800 (PST)
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 F33AF1A90A9 for <homenet@ietf.org>; Tue, 24 Feb 2015 21:35:17 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 7577FA3; Wed, 25 Feb 2015 06:35:05 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1424842505; bh=RqGR6V6wb3lj14nCgwyAalxiIjKNZp5Jcb+NXI1Ls4U=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=ScrpeIn8iqrSUhRgpphmq3KJEEUNzKCnOklafaXRiIQBFZO/Evy8U4SdOSQtd/tT4 XplCbdXx0tebEQQDhzcBVc4CtPxOXohwv4sKfGHmvNoYelNHAusoIf8ghp9jeWGQEB CidVsOUoyWsh0rBnlntPVr5lWRA4sto71xGm3RUE=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 706F9A2; Wed, 25 Feb 2015 06:35:05 +0100 (CET)
Date: Wed, 25 Feb 2015 06:35:05 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Andrew Mcgregor <andrewmcgr@google.com>
In-Reply-To: <CAPRuP3kwWyA-oJi7ckPOT+L7XyxCa7aWSw3B9vHXzuiT6AFwjQ@mail.gmail.com>
Message-ID: <alpine.DEB.2.02.1502250631080.4007@uplift.swm.pp.se>
References: <CAA93jw7eGxPBNX+5LqX+qTYfRxNDxQpKo1fecUa2XH3bAKgvQQ@mail.gmail.com> <BB621A07-282E-4814-9D56-3EFBF87814D0@iki.fi> <71C98A06-0B23-4916-BFF8-CCF663A3F0A0@fugue.com> <87zj88b9xf.wl-jch@pps.univ-paris-diderot.fr> <CAA93jw4ZF8=QFMGmb1uPB+xxcNHadSZCEMkTTuDfOHrABWg3Mg@mail.gmail.com> <4C09C5D0-7CB9-439A-BFB1-22BC57CA9207@mbaugher.com> <CAPRuP3kwWyA-oJi7ckPOT+L7XyxCa7aWSw3B9vHXzuiT6AFwjQ@mail.gmail.com>
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/Lc1YV6eeU5SDcf5yR89F37zuF7w>
Cc: HOMENET <homenet@ietf.org>
Subject: Re: [homenet] OpenWRT hardware [was: A poll]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Wed, 25 Feb 2015 05:35:20 -0000

On Wed, 25 Feb 2015, Andrew Mcgregor wrote:

> The TP-Link Archer C7 seems quite nice, although I've only been playing 
> with it less than 24 hours; my opernwrt build seems unable to send more 
> than 100 Mbps over the ethernet, but the WiFi side is quite fast; I saw 
> 270 Mbps of TCP sourced from iperf on the device, undoubtedly CPU 
> limited.

This is generally the problem, that things are CPU limited, and the CPUs 
in these are not fast enough to move packets around faster than a few 
hundred megabits/s of large packets.

There are several gig capable boxes on the market, but they typically have 
hardware packet routing accelerators with proprietary management APIs that 
need special kernels and special "board support packages" that you only 
get access to after signing NDAs. Usually currently this means a Linux 
kernel 3.2 or 3.4 or around there, which means you're tied to a very old 
kernel limiting other features on the box such as 
virtualisation/containers etc.

But I still have hopes for a brighter future...

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


From nobody Wed Feb 25 00:15:12 2015
Return-Path: <markus.stenberg@iki.fi>
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 DF3D31A1EF1 for <homenet@ietfa.amsl.com>; Wed, 25 Feb 2015 00:15:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.121
X-Spam-Level: 
X-Spam-Status: No, score=-1.121 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_NEUTRAL=0.779] autolearn=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 Yp3mOxv2n5TO for <homenet@ietfa.amsl.com>; Wed, 25 Feb 2015 00:15:08 -0800 (PST)
Received: from kirsi2.inet.fi (mta-out1.inet.fi [62.71.2.227]) by ietfa.amsl.com (Postfix) with ESMTP id BACAB1A1C06 for <homenet@ietf.org>; Wed, 25 Feb 2015 00:15:07 -0800 (PST)
Received: from poro.lan (80.220.64.126) by kirsi2.inet.fi (8.5.142.08) (authenticated as stenma-47) id 54E3C7150010AF46; Wed, 25 Feb 2015 10:15:00 +0200
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Markus Stenberg <markus.stenberg@iki.fi>
In-Reply-To: <87sidudikk.wl-jch@pps.univ-paris-diderot.fr>
Date: Wed, 25 Feb 2015 10:15:01 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <44C94D8E-E037-4186-BC24-C25948B0C9A6@iki.fi>
References: <8761at9vx5.wl-jch@pps.univ-paris-diderot.fr> <7D8C2976-1649-4349-9E90-E24DD2848086@iki.fi> <87lhjosla1.wl-jch@pps.univ-paris-diderot.fr> <BB38C59C-D71D-4AA0-ABFE-04D557C1DCCD@iki.fi> <87sidudikk.wl-jch@pps.univ-paris-diderot.fr>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/Xi6oQCSlQmGWGYc3wVis4M6OwRA>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Markus Stenberg <markus.stenberg@iki.fi>
Subject: Re: [homenet] DNCP questions
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Wed, 25 Feb 2015 08:15:10 -0000

On 25.2.2015, at 0.56, Juliusz Chroboczek =
<jch@pps.univ-paris-diderot.fr> wrote:
>>> should not send packets larger than 1500 octets unless it has =
assurance
>>> that the destination is capable of reassembling packets of that =
larger
>>> size.
>> I guess this is another MUST to be added to HNCP text (DNCP itself is
>> not IPv6-specific as such).
> You mean that every HNCP node MUST ba able to accept packets of up to =
64kB?
> What=E2=80=99s the status of typical embedded stacks?

Configuration dependant more than implementation at least in the few I =
have played with, but usually they=E2=80=99re really short of RAM so =
usually configuration is rather conservative. Sticking (say) DTLS in one =
is probably no-go due to lack of computing power to start with so I am =
not sure this is that relevant.

That said, from my point of view, if this is really thought to be an =
issue by the WG, correct solution is to use TLS (+TCP) instead of DTLS =
(+UDP) in any case.

Cheers,

-Markus=


From nobody Wed Feb 25 00:37:17 2015
Return-Path: <markus.stenberg@iki.fi>
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 A99141A6F04 for <homenet@ietfa.amsl.com>; Wed, 25 Feb 2015 00:37:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.521
X-Spam-Level: 
X-Spam-Status: No, score=-0.521 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_35=0.6, RCVD_IN_DNSWL_NONE=-0.0001, SPF_NEUTRAL=0.779] autolearn=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 E-k-Ah_AUdNM for <homenet@ietfa.amsl.com>; Wed, 25 Feb 2015 00:37:13 -0800 (PST)
Received: from jenni1.inet.fi (mta-out1.inet.fi [62.71.2.203]) by ietfa.amsl.com (Postfix) with ESMTP id 36D751A6EEC for <homenet@ietf.org>; Wed, 25 Feb 2015 00:37:13 -0800 (PST)
Received: from poro.lan (80.220.64.126) by jenni1.inet.fi (8.5.142.08) (authenticated as stenma-47) id 54E3C70300E75326; Wed, 25 Feb 2015 10:37:10 +0200
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Markus Stenberg <markus.stenberg@iki.fi>
In-Reply-To: <87r3tedhym.wl-jch@pps.univ-paris-diderot.fr>
Date: Wed, 25 Feb 2015 10:37:12 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <9D797DF7-D648-42CD-92D5-71630F9846F5@iki.fi>
References: <8761at9vx5.wl-jch@pps.univ-paris-diderot.fr> <7D8C2976-1649-4349-9E90-E24DD2848086@iki.fi> <874mqcsh98.wl-jch@pps.univ-paris-diderot.fr> <B5B68563-91D5-455C-A3AB-B1B3969302B7@iki.fi> <87r3tedhym.wl-jch@pps.univ-paris-diderot.fr>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/1_m3cSUV4ONDZLa37BFCFSW2rYA>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Markus Stenberg <markus.stenberg@iki.fi>
Subject: Re: [homenet] DNCP questions
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Wed, 25 Feb 2015 08:37:14 -0000

On 25.2.2015, at 1.10, Juliusz Chroboczek =
<jch@pps.univ-paris-diderot.fr> wrote:
>>> Another question -- is it possible to participate in Trickle-driven
>>> flooding without building the full topology graph?
>=20
>> The current answer based on strict reading of the spec is no.
> [...]
>> Is this desirable to be changed? Probably so.=20
> There's not only the stub case that you consider, but also the pure
> client/forwarder node -- a node that doesn't wish to publish any data, =
but
> uses static HNCP data, and serves as a link between two parts of the
> network.  Ideally, such a node should not contribute any replicated =
state.
>=20
> (Note that a Babel/AHCP router that doesn't announce any routes
> contributes no state whatsoever to non-neighbouring nodes.  So you can =
add
> arbitrary many intermediary hops with no cost incurred by distant =
nodes.)

That sounds like distance vector <> link state tradeoff (and yes, we =
know HNCP isn=E2=80=99t a routing protocol but it both exists due to =
politics, and isn=E2=80=99t one due to politics; good luck shoving IS-IS =
on top of *TLS, or sticking in dozen+ random TLVs there).

Suggestions on how to address that are welcome of course.

(Forward case is tricky; client isn=E2=80=99t problematic, see below.)

> The reason I'm asking is somewhat out of scope for Homenet -- I'm =
looking
> into deprecating AHCP in mesh networks in favour of a subset =
implementation
> of HNCP.  AHCP is a very simple protocol, and one can implement an =
AHCP
> client/forwarder in constant space.  Not so with HNCP -- in HNCP, =
every
> node has a copy of the topology, and contributes a vertex to the =
replicated
> neighbour graph.
>=20
> HNCP is naive link state, with no network nodes (pseudonodes) and no
> DR/DIS/MPR election.  So its scaling is quadratic in the worst case.
> Consider a network containing a switched Ethernet backbone consisting
> a mere 30 routers.  Unless I'm missing something, this backbone will
> contribute no less than 30 vertices and 435 edges in the neighbour =
graph,
> and this state will be duplicated in every single node in the network.

Yep, intentionally so for now; of course, we could turn it even more in =
the scalable (routing) protocol direction if there is desire. In another =
draft for a different WG I have specified auto-area extension for it =
already :p

> There's an obvious solution -- it is to have pure client nodes that
> participate in Trickle but don't contribute a vertex to the neighbour
> graph.  But HNCP doesn=E2=80=99t support that.

That shouldn=E2=80=99t be hard to address if it seems desirable, but =
doing (robust) (stateless) forwarding that way is problematic. =
Willingness to drop one lets you get the other, but not both I think

For the =E2=80=98pure client=E2=80=99 (and especially =E2=80=98limited =
client=E2=80=99) case, I would argue that they are not interested in =
most of the state in HNCP in any case and would want just some sort of =
request-reply of current state, and possibly notifications about state =
changes from their first-hop non-client node.=20

As an alternative, some flag to say that =E2=80=98I do not want to be =
your neighbor=E2=80=99 would allow read-only client usage of HNCP state =
using normal RNS+RNDxN messages, but I think nodes would be more =
interested in per-TLV state that is applicable, and not retrieving whole =
network state just to get e.g. assigned addresses.

Cheers,

-Markus


From nobody Wed Feb 25 01:27:30 2015
Return-Path: <teco@inf-net.nl>
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 7E8F91A82E2 for <homenet@ietfa.amsl.com>; Wed, 25 Feb 2015 01:27:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  J_CHICKENPOX_44=0.6, RCVD_IN_DNSWL_LOW=-0.7] 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 8eRnkdc821WW for <homenet@ietfa.amsl.com>; Wed, 25 Feb 2015 01:27:27 -0800 (PST)
Received: from mail-wg0-f45.google.com (mail-wg0-f45.google.com [74.125.82.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 116FA1A7D81 for <homenet@ietf.org>; Wed, 25 Feb 2015 01:27:26 -0800 (PST)
Received: by wghk14 with SMTP id k14so2366457wgh.4 for <homenet@ietf.org>; Wed, 25 Feb 2015 01:27:25 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=Wk+4CiFaE42GL68cG3GvEN+K6Vt//aiHaM1/Umu7zIE=; b=jm+FhArMPJ0KTgseeIgPcgp+kXyZ9TIN3WjoLLVE3QbOrnehw4B26/9RynhR4z1OmE A0BTt+6DsM1/RNHGMP9Y7oEVIEzUgAILUqqV0oh2rXLN4kAxa66bMRjaDRAJWaABTcFd AzCf6Sdfi9eGYon+h/FFLnp/Cmjhp/dOvYOYWFsLJIuVKPDHXOa1hnbiMiVa7oddV8ZX i1zksVSblaKjcXH6OIHqGn+Thwx9sjH5nd5m6SytaQOXpuzQjldAq2QDxTLqAA829JN4 ozRh0/zI45GUADuNf3HECedCcQ6UPqqQNGqbKumYSccmPyNxRShG+PDPLw5Hg2L14LX1 AXTQ==
X-Gm-Message-State: ALoCoQkZo9NrIjcr8cxkKIdcBNdZN19a5/npYpgYifSt9HSAL8E/l6RLT9xrmv3wZOkakrSOA0TQ
X-Received: by 10.180.8.65 with SMTP id p1mr4888230wia.42.1424856444777; Wed, 25 Feb 2015 01:27:24 -0800 (PST)
Received: from [192.168.43.109] ([92.69.234.40]) by mx.google.com with ESMTPSA id dn7sm12902399wid.12.2015.02.25.01.27.22 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 25 Feb 2015 01:27:24 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Teco Boot <teco@inf-net.nl>
In-Reply-To: <CAA93jw7eGxPBNX+5LqX+qTYfRxNDxQpKo1fecUa2XH3bAKgvQQ@mail.gmail.com>
Date: Wed, 25 Feb 2015 10:27:22 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <6503A960-8CD8-4C6A-BA32-B7A32E0C20FC@inf-net.nl>
References: <CAA93jw7eGxPBNX+5LqX+qTYfRxNDxQpKo1fecUa2XH3bAKgvQQ@mail.gmail.com>
To: Dave Taht <dave.taht@gmail.com>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/7gSeMMNINeSTVhmXyo1Ft8nCJ44>
Cc: HOMENET <homenet@ietf.org>
Subject: Re: [homenet] A poll
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Wed, 25 Feb 2015 09:27:29 -0000

> Op 20 feb. 2015, om 17:50 heeft Dave Taht <dave.taht@gmail.com> het =
volgende geschreven:
>=20
> The homenet working group has been laboring for several years now to
> find ways to make ipv6 more deployable to home (and presumably small
> business) users.
>=20
> In addition to multiple specification documents some code has been
> produced to try and make things easier. At least in the USA, comcast
> has rolled out IPv6 to everyone that can get dhcpv6 to sort of work on
> their router, and/or is willing to install a custom firmware on their
> router to get that, and of course tunneling ipv6 is possible if the
> ISP does not support it.
>=20
> So a quick poll:
>=20
> 0) Have you managed to get ipv6 working at all? If so, how? What sort
> of problems did you encounter?

Yes, HE tunnel.
Set up a few times, vanished same number of times.
Waiting for IPv6 roll-out in NLD. I'm hopeful for 2015.


>=20
> 1) Have you attempted to deploy a routing protocol in your home? Which
> one, and why?

Having a small olsrd.org testbed for couple of years. IPv4-only.
In mean time, SmartGateway with multi-homing support is running fine. =
This provides connection pinning for mobile nodes, at setup of =
connection, GW is fixed so no NAT / firewall problems.
Tried MPTCP, not integrated with olsrd / sgw yet.

I have plans to move to homenet's protocols.

>=20
> 2) Have you attempted to get hnetd's prefix distribution system
> working? (it supports linux mainline and openwrt presently)

No.

>=20
> 3) Do you use ethernet? How many clients in your home are ethernet =
connected?

Yes.
About 6 nodes, stationary (iMac, TV, MacMini as backup server, Cameras, =
sometimes MacBook).
1x MacBook never connects to ethernet.

>=20
> 4) Do you use wifi? How many clients are wifi connected? Do you use
> range extenders?

Yes.
About 6 nodes. More for testing.
Two own APs in production.
ISP AP with guest access for all ISP customers (millions).
Couple of APs in olsrd testbed.
Phones are APs.

>=20
> 5) How many devices do you think you will have connected to the
> network in your home in 5 years? How many now?

Little more.

>=20
> 6) Do you use any other network connected technologies (homeplug,
> 802.14, LTE, etc). If so, which ones, and why?

LTE (2x phone).
Maybe add ADSL to cable, for redundancy. Waiting for better multi-homing =
support. Now, it only adds complexity and uptime would go down....
Sometimes, tethering to phones (from MacBook) is still active at home. =
Should switch to high speed flat fee WiFi automatically.


>=20
> 7) Do you use mdns service discovery?
>=20

Yes.

> 8) Why are you here? (especially, if your answers to 0-2, are "no")

Current situation is bad. No multi-homing, lousy roaming between APs, =
need for keep-alive to refresh NAT state etc.

I think the homenet protocols have much more potential than just home =
networks. E.g. satcom terminals act like CPE devices. Mobile devices =
roam between homes, cars, trains, @work, hotels.
Also, more plug&play reduces O&M costs.

Teco

>=20
> --=20
> Dave T=C3=A4ht
>=20
> http://www.bufferbloat.net/projects/bloat/wiki/Upcoming_Talks
>=20
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet


From nobody Wed Feb 25 07:48:15 2015
Return-Path: <v6ops@globis.net>
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 474141A90BD for <homenet@ietfa.amsl.com>; Wed, 25 Feb 2015 07:48:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 sW5rOTVA_rwa for <homenet@ietfa.amsl.com>; Wed, 25 Feb 2015 07:48:07 -0800 (PST)
Received: from globis01.globis.net (mail.globis.net [IPv6:2001:470:1f15:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id 896591A90F0 for <homenet@ietf.org>; Wed, 25 Feb 2015 07:47:57 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id 23442871648; Wed, 25 Feb 2015 16:47:56 +0100 (CET)
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kitO6gZb3doY; Wed, 25 Feb 2015 16:47:56 +0100 (CET)
Received: from Rays-iMac.local (092-111-140-211.static.chello.nl [92.111.140.211]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPSA id ED7CB870009; Wed, 25 Feb 2015 16:47:55 +0100 (CET)
Message-ID: <54EDEEAA.5040302@globis.net>
Date: Wed, 25 Feb 2015 16:47:54 +0100
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.11 (Macintosh/20140602)
MIME-Version: 1.0
To: Mikael Abrahamsson <swmike@swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <8B98F698-983D-4D2A-B5D1-7ACED27C275E@fugue.com> <alpine.DEB.2.02.1502191920560.4007@uplift.swm.pp.se> <CAPRuP3mpNJTu6mP+RAVKKO0kt60PogNtNbCUCRRqxe9im3EzjA@mail.gmail.com> <alpine.DEB.2.02.1502201042330.4007@uplift.swm.pp.se> <7A86BDC6-FF4B-49FF-B59C-BA1DEF463173@inf-net.nl> <alpine.DEB.2.02.1502201310050.4007@uplift.swm.pp.se> <09793905-8D12-49E0-A040-490F617C87FF@inf-net.nl> <alpine.DEB.2.02.1502201410510.4007@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1502201410510.4007@uplift.swm.pp.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/g3-QYWEgxQuYLDz8F1yHLP12NWk>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Teco Boot <teco@inf-net.nl>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Wed, 25 Feb 2015 15:48:08 -0000

Mikael Abrahamsson wrote:
> On Fri, 20 Feb 2015, Teco Boot wrote:
>
>> Back to the subject: What are the requirements of a high performance 
>> WiFi home network to the homenet routing protocol? I guess we don't 
>> know.
>
> Within the current framework to solve this problem with what exists 
> today when it comes to clients, I would say we need either:
>
> 1. HNCP helps set up an overlay L2 tunnel infrastructure connecting 
> all the APs using the same SSID, so the SSID can have the same L2 
> domain. This would probably mean we want to increase MTU on the 
> physical links to avoid fragmentation. Messy. Possibly we could 
> advertise lower MTU on the wifi network to minimize fragmentation if 
> we don't raise MTU.
>
> 2. We set up some kind of L2 switching domain between the APs. This 
> would require VLAN support in the HGWs, and something to set this up 
> with loop avoidance etc. Oh oh oh, we could use IEEE 802.1aq that 
> already uses ISIS as control plane, that way we could possibly run the 
> same IGP for both L2 and L3. Interconnecting APs over wifi seems weird 
> though. Oh, and messy sounds like an understatement.
>
> Frankly, I don't know how to solve this without a lot of complication.
>
> We need clients to be able to change IPv6 addresses without losing 
> existing connections. SHIM6 anyone? MP-TCP? Asking IEEE to make 802.11 
> keep two connections at once and inform the application that one 
> address is going away soon so it can do its thing to try to handle this?
>
I agree that WiFi roaming is a problem that needs addressing in Homenet.

One suggestion from my side for handling WiFi roaming is for these 
clients to incorporate a software loopback interface that does not 
renumber, and is always up, and these roaming clients also actively take 
part in HNCP, and the Homenet routing protocol as "stub routers."

That way the devices can roam at L3, without all of the nasty side 
effects of re-establishing TPC sessions, or updating dynamic naming 
services, or having to run an L2 overlay network everywhere, or having 
to support protocols that require a specialised partner in crime on the 
server side (mTCP, shim6 et al).

YMMV.


-- 
Regards,
RayH


From nobody Wed Feb 25 07:58:58 2015
Return-Path: <mellon@fugue.com>
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 64CE21A910F for <homenet@ietfa.amsl.com>; Wed, 25 Feb 2015 07:58:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 WuMHPlveVctF for <homenet@ietfa.amsl.com>; Wed, 25 Feb 2015 07:58:56 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 623361A1B28 for <homenet@ietf.org>; Wed, 25 Feb 2015 07:58:56 -0800 (PST)
Received: from [10.0.20.107] (c-71-233-43-215.hsd1.nh.comcast.net [71.233.43.215]) by toccata.fugue.com (Postfix) with ESMTPSA id 15F212380425; Wed, 25 Feb 2015 10:58:54 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <54EDEEAA.5040302@globis.net>
Date: Wed, 25 Feb 2015 10:58:50 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <3DB6565A-CD7A-4224-BC9B-7493299036E1@fugue.com>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <8B98F698-983D-4D2A-B5D1-7ACED27C275E@fugue.com> <alpine.DEB.2.02.1502191920560.4007@uplift.swm.pp.se> <CAPRuP3mpNJTu6mP+RAVKKO0kt60PogNtNbCUCRRqxe9im3EzjA@mail.gmail.com> <alpine.DEB.2.02.1502201042330.4007@uplift.swm.pp.se> <7A86BDC6-FF4B-49FF-B59C-BA1DEF463173@inf-net.nl> <alpine.DEB.2.02.1502201310050.4007@uplift.swm.pp.se> <09793905-8D12-49E0-A040-490F617C87FF@inf-net.nl> <alpine.DEB.2.02.1502201410510.4007@uplift.swm.pp.se> <54EDEEAA.5040302@globis.net>
To: Ray Hunter <v6ops@globis.net>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/HWArKkYXDWG85Gkg6_fVMou53tk>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Teco Boot <teco@inf-net.nl>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Wed, 25 Feb 2015 15:58:57 -0000

On Feb 25, 2015, at 10:47 AM, Ray Hunter <v6ops@globis.net> wrote:
> One suggestion from my side for handling WiFi roaming is for these =
clients to incorporate a software loopback interface that does not =
renumber, and is always up, and these roaming clients also actively take =
part in HNCP, and the Homenet routing protocol as "stub routers."

Something like this is currently done with Babel, but it's not a =
complete solution because it requires Babel-specific modifications on =
the client.   The proposal to have a single bridged WiFi broadcast =
domain would eliminate this problem, at the cost of some substantial =
pain in terms of how to set that up automatically and in terms of =
performance, which clearly would suffer from the expanded broadcast =
domain.   And there's also the problem of differentiating backbone wifi =
links from wifi leaf networks.


From nobody Wed Feb 25 08:14:54 2015
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 7FDE21A19EC for <homenet@ietfa.amsl.com>; Wed, 25 Feb 2015 08:14:52 -0800 (PST)
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 nOUIjc3LkgTN for <homenet@ietfa.amsl.com>; Wed, 25 Feb 2015 08:14:49 -0800 (PST)
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 AB4981A0636 for <homenet@ietf.org>; Wed, 25 Feb 2015 08:14:49 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 92463A3; Wed, 25 Feb 2015 17:14:47 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1424880887; bh=SCpp2tqkwwwrD+YRTXeGk/3tMj1zVO311CihWHXB/3Q=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=CKjWndSjW8Btv2DwyUbfQxVmA83IRo+i0l6NiCRs8Nfeof5norNoAOsyFU0hKPfHw tIegG/UsBrfDAqOge9gmaN6F+mBdVHs2skw77V6gWbRYSLY9lqwe0xrVgilSP/Mbyx RLBzhVCs4uWI+xPcbAg6Dc8wXulxTPq7aRu4zbI4=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 8A863A2; Wed, 25 Feb 2015 17:14:47 +0100 (CET)
Date: Wed, 25 Feb 2015 17:14:47 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Ray Hunter <v6ops@globis.net>
In-Reply-To: <54EDEEAA.5040302@globis.net>
Message-ID: <alpine.DEB.2.02.1502251711050.4007@uplift.swm.pp.se>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <8B98F698-983D-4D2A-B5D1-7ACED27C275E@fugue.com> <alpine.DEB.2.02.1502191920560.4007@uplift.swm.pp.se> <CAPRuP3mpNJTu6mP+RAVKKO0kt60PogNtNbCUCRRqxe9im3EzjA@mail.gmail.com> <alpine.DEB.2.02.1502201042330.4007@uplift.swm.pp.se> <7A86BDC6-FF4B-49FF-B59C-BA1DEF463173@inf-net.nl> <alpine.DEB.2.02.1502201310050.4007@uplift.swm.pp.se> <09793905-8D12-49E0-A040-490F617C87FF@inf-net.nl> <alpine.DEB.2.02.1502201410510.4007@uplift.swm.pp.se> <54EDEEAA.5040302@globis.net>
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/R0eZhOz7I5cb_WbtgMBVabp5mt4>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Teco Boot <teco@inf-net.nl>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Wed, 25 Feb 2015 16:14:52 -0000

On Wed, 25 Feb 2015, Ray Hunter wrote:

> That way the devices can roam at L3, without all of the nasty side 
> effects of re-establishing TPC sessions, or updating dynamic naming 
> services, or having to run an L2 overlay network everywhere, or having 
> to support protocols that require a specialised partner in crime on the 
> server side (mTCP, shim6 et al).

It's my firm belief that we need to rid clients of IP address dependence 
for its sessions. Asking clients to participate in HNCP only addresses the 
problem where HNCP is used.

Fixing this for real would reap benefits for devices moving between any 
kind of network, multiple providers, mobile/fixed etc.

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


From nobody Wed Feb 25 08:20:47 2015
Return-Path: <v6ops@globis.net>
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 74D161A1B20 for <homenet@ietfa.amsl.com>; Wed, 25 Feb 2015 08:20:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 LQqZrkckaL_k for <homenet@ietfa.amsl.com>; Wed, 25 Feb 2015 08:20:44 -0800 (PST)
Received: from globis01.globis.net (mail.globis.net [IPv6:2001:470:1f15:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id 92BAB1A1AA9 for <homenet@ietf.org>; Wed, 25 Feb 2015 08:20:36 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id 1FA20871648; Wed, 25 Feb 2015 17:20:35 +0100 (CET)
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F3+Jx4Psj-p0; Wed, 25 Feb 2015 17:20:35 +0100 (CET)
Received: from [192.168.1.12] (d75067.upc-d.chello.nl [213.46.75.67]) (Authenticated sender: v6ops@globis.net) by globis01.globis.net (Postfix) with ESMTPSA id F1DF8870040; Wed, 25 Feb 2015 17:20:34 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
From: V6ops <v6ops@globis.net>
X-Mailer: iPad Mail (12B466)
In-Reply-To: <3DB6565A-CD7A-4224-BC9B-7493299036E1@fugue.com>
Date: Wed, 25 Feb 2015 17:20:34 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <85F30F8A-4339-49BF-9488-485AF44C984D@globis.net>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <8B98F698-983D-4D2A-B5D1-7ACED27C275E@fugue.com> <alpine.DEB.2.02.1502191920560.4007@uplift.swm.pp.se> <CAPRuP3mpNJTu6mP+RAVKKO0kt60PogNtNbCUCRRqxe9im3EzjA@mail.gmail.com> <alpine.DEB.2.02.1502201042330.4007@uplift.swm.pp.se> <7A86BDC6-FF4B-49FF-B59C-BA1DEF463173@inf-net.nl> <alpine.DEB.2.02.1502201310050.4007@uplift.swm.pp.se> <09793905-8D12-49E0-A040-490F617C87FF@inf-net.nl> <alpine.DEB.2.02.1502201410510.4007@uplift.swm.pp.se> <54EDEEAA.5040302@globis.net> <3DB6565A-CD7A-4 224-BC9B-7493299036E1@fugue.com>
To: Ted Lemon <mellon@fugue.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/yTpolhSizdpPBd2IwLJNCwWlzJQ>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Teco Boot <teco@inf-net.nl>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Wed, 25 Feb 2015 16:20:45 -0000

> On 25 Feb 2015, at 16:58, Ted Lemon <mellon@fugue.com> wrote:
>=20
>> On Feb 25, 2015, at 10:47 AM, Ray Hunter <v6ops@globis.net> wrote:
>> One suggestion from my side for handling WiFi roaming is for these client=
s to incorporate a software loopback interface that does not renumber, and i=
s always up, and these roaming clients also actively take part in HNCP, and t=
he Homenet routing protocol as "stub routers."
>=20
> Something like this is currently done with Babel, but it's not a complete s=
olution because it requires Babel-specific modifications on the client.   Th=
e proposal to have a single bridged WiFi broadcast domain would eliminate th=
is problem, at the cost of some substantial pain in terms of how to set that=
 up automatically and in terms of performance, which clearly would suffer fr=
om the expanded broadcast domain.   And there's also the problem of differen=
tiating backbone wifi links from wifi leaf networks.

Agreed.

For the purposes of this discussion, I think a soft requirement on a stub-on=
ly implementation of the chosen Homenet routing protocol on a host OS could b=
e an interesting differentiator.=


From nobody Wed Feb 25 11:23:28 2015
Return-Path: <brian.e.carpenter@gmail.com>
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 7B3461A6F3C for <homenet@ietfa.amsl.com>; Wed, 25 Feb 2015 11:23:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 pfsXFYAfi-VO for <homenet@ietfa.amsl.com>; Wed, 25 Feb 2015 11:23:21 -0800 (PST)
Received: from mail-pd0-x230.google.com (mail-pd0-x230.google.com [IPv6:2607:f8b0:400e:c02::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2936F1A7023 for <homenet@ietf.org>; Wed, 25 Feb 2015 11:23:21 -0800 (PST)
Received: by pdbfl12 with SMTP id fl12so7035683pdb.4 for <homenet@ietf.org>; Wed, 25 Feb 2015 11:23:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=NMfccVPnuKeXQwglLh2gPYNNQZzumOBTg0NRPLdPpf0=; b=dJLsN8vozyKM/X84t7F5mdjCu9rSEo2miLKXLL3LcTtWWzgw/k3MVGnCLzF1HdrFT0 fkb4Yy7pccYYo3dlWKvOFkPTmvif7XzgXQgUlEoJiPaefbkU0skHDsyDHPs0mJYgdSgy pJo4eM8obzQMMQz5LmWBJKxhM5Ean81hZmIE5xb/2RQjvSueETF2PFNzci6uIcc8/L3e eskXZ85sm76YY+lm5MCY7QegChKhuu8C5TyVt4u9CaL3MTJCLMRBTMU0sFLgLu0DXeJC c3REb2dM2rXXmD2h5u74XBziyRS1sFon7+0TyJSxp9dDEx8vTeQgb+upk4vHKh7DzV9M whUg==
X-Received: by 10.66.66.133 with SMTP id f5mr8264430pat.20.1424892200386; Wed, 25 Feb 2015 11:23:20 -0800 (PST)
Received: from ?IPv6:2406:e007:6564:1:28cc:dc4c:9703:6781? ([2406:e007:6564:1:28cc:dc4c:9703:6781]) by mx.google.com with ESMTPSA id c8sm6741248pds.5.2015.02.25.11.23.17 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 25 Feb 2015 11:23:19 -0800 (PST)
Message-ID: <54EE212B.8050507@gmail.com>
Date: Thu, 26 Feb 2015 08:23:23 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Markus Stenberg <markus.stenberg@iki.fi>,  Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
References: <8761at9vx5.wl-jch@pps.univ-paris-diderot.fr> <7D8C2976-1649-4349-9E90-E24DD2848086@iki.fi> <87lhjosla1.wl-jch@pps.univ-paris-diderot.fr> <BB38C59C-D71D-4AA0-ABFE-04D557C1DCCD@iki.fi> <87sidudikk.wl-jch@pps.univ-paris-diderot.fr> <44C94D8E-E037-4186-BC24-C25948B0C9A6@iki.fi>
In-Reply-To: <44C94D8E-E037-4186-BC24-C25948B0C9A6@iki.fi>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/C6qumdMm4xjhkIUqEoqgwHETA8Q>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] DNCP questions
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Wed, 25 Feb 2015 19:23:26 -0000

On 25/02/2015 21:15, Markus Stenberg wrote:
> On 25.2.2015, at 0.56, Juliusz Chroboczek <jch@pps.univ-paris-diderot.f=
r> wrote:
>>>> should not send packets larger than 1500 octets unless it has assura=
nce
>>>> that the destination is capable of reassembling packets of that larg=
er
>>>> size.
>>> I guess this is another MUST to be added to HNCP text (DNCP itself is=

>>> not IPv6-specific as such).
>> You mean that every HNCP node MUST ba able to accept packets of up to =
64kB?
>> What=E2=80=99s the status of typical embedded stacks?
>=20
> Configuration dependant more than implementation at least in the few I =
have played with, but usually they=E2=80=99re really short of RAM so usua=
lly configuration is rather conservative. Sticking (say) DTLS in one is p=
robably no-go due to lack of computing power to start with so I am not su=
re this is that relevant.
>=20
> That said, from my point of view, if this is really thought to be an is=
sue by the WG, correct solution is to use TLS (+TCP) instead of DTLS (+UD=
P) in any case.

I've thought about this in the Anima/GDNP context and reached the
same conclusion. Why make life complicated when TLS makes it simple?

   Brian


From nobody Wed Feb 25 11:42:07 2015
Return-Path: <brian.e.carpenter@gmail.com>
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 CC29D1A8780 for <homenet@ietfa.amsl.com>; Wed, 25 Feb 2015 11:42:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 UUQwfL9AfvEp for <homenet@ietfa.amsl.com>; Wed, 25 Feb 2015 11:42:05 -0800 (PST)
Received: from mail-pd0-x22d.google.com (mail-pd0-x22d.google.com [IPv6:2607:f8b0:400e:c02::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 68FD41A8787 for <homenet@ietf.org>; Wed, 25 Feb 2015 11:42:05 -0800 (PST)
Received: by pdno5 with SMTP id o5so7106311pdn.8 for <homenet@ietf.org>; Wed, 25 Feb 2015 11:42:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=riY46KfFwqRLnSrjPTDVAMYSqClJR1Fpo7JEeCwidHk=; b=WCx5CX7Hubz/gbwrzvvFjCKyF8sM+q39jAO2I6TxxTtKFrUlbi89JvzlSQRyd/l9AK /weQshTywUek3GO1bhfbJna09CM44ELWe2RpI3hhydlglAWoqINA12kgKg3trhbxoK4Q bRd+oGYDh3ZUMcQDFz5kclh1eTED5MxsZCHsjeYqOvKKmKcSdz6NpdOip8dLEyRYm290 Lb3WQuTNgx2l70itOnHc/F+6cFHeV1fdFs1MfYgdDqYAirnKIC3VGGKo81U3TRQ4sC87 lDNMYFjLwJfBqd/zyaUAaekLwqpY+Jz6dREizzxJtT84EywzwnRkj0DPcnghNh/Ng2R/ wcTw==
X-Received: by 10.66.219.130 with SMTP id po2mr8279245pac.98.1424893324571; Wed, 25 Feb 2015 11:42:04 -0800 (PST)
Received: from ?IPv6:2406:e007:6564:1:28cc:dc4c:9703:6781? ([2406:e007:6564:1:28cc:dc4c:9703:6781]) by mx.google.com with ESMTPSA id b3sm42132951pbu.0.2015.02.25.11.42.01 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 25 Feb 2015 11:42:03 -0800 (PST)
Message-ID: <54EE258E.8060302@gmail.com>
Date: Thu, 26 Feb 2015 08:42:06 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Mikael Abrahamsson <swmike@swm.pp.se>, Ray Hunter <v6ops@globis.net>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <8B98F698-983D-4D2A-B5D1-7ACED27C275E@fugue.com> <alpine.DEB.2.02.1502191920560.4007@uplift.swm.pp.se> <CAPRuP3mpNJTu6mP+RAVKKO0kt60PogNtNbCUCRRqxe9im3EzjA@mail.gmail.com> <alpine.DEB.2.02.1502201042330.4007@uplift.swm.pp.se> <7A86BDC6-FF4B-49FF-B59C-BA1DEF463173@inf-net.nl> <alpine.DEB.2.02.1502201310050.4007@uplift.swm.pp.se> <09793905-8D12-49E0-A040-490F617C87FF@inf-net.nl> <alpine.DEB.2.02.1502201410510.4007@uplift.swm.pp.se> <54EDEEAA.5040302@globis.net> <alpine.DEB.2.02.1502251711050.4007@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1502251711050.4007@uplift.swm.pp.se>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/qPFWmxoYxVf7yIny8A4oQGpHyM0>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Teco Boot <teco@inf-net.nl>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Wed, 25 Feb 2015 19:42:06 -0000

On 26/02/2015 05:14, Mikael Abrahamsson wrote:
> On Wed, 25 Feb 2015, Ray Hunter wrote:
> 
>> That way the devices can roam at L3, without all of the nasty side effects of re-establishing TPC sessions, or updating
>> dynamic naming services, or having to run an L2 overlay network everywhere, or having to support protocols that require a
>> specialised partner in crime on the server side (mTCP, shim6 et al).
> 
> It's my firm belief that we need to rid clients of IP address dependence for its sessions. Asking clients to participate in HNCP
> only addresses the problem where HNCP is used.
> 
> Fixing this for real would reap benefits for devices moving between any kind of network, multiple providers, mobile/fixed etc.

Violent agreement. This is not a homenet problem; it's an IP problem.
In fact, it's exactly why IP addresses are considered harmful in
some quarters. Trying to fix it just for homenet seems pointless.
http://www.sigcomm.org/ccr/papers/2014/April/0000000.0000008

   Brian


From nobody Wed Feb 25 12:38:14 2015
Return-Path: <curtis@ipv6.occnc.com>
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 70BF61A8707 for <homenet@ietfa.amsl.com>; Wed, 25 Feb 2015 12:38:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.008
X-Spam-Level: *
X-Spam-Status: No, score=1.008 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, MISSING_HEADERS=1.021, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 8G72Lzsro83o for <homenet@ietfa.amsl.com>; Wed, 25 Feb 2015 12:38:10 -0800 (PST)
Received: from maildrop31.somerville.occnc.com (maildrop31.somerville.occnc.com [IPv6:2001:550:3800:203::3131]) (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 7D6551A1B13 for <homenet@ietf.org>; Wed, 25 Feb 2015 12:38:08 -0800 (PST)
Received: from harbor31.somerville.occnc.com (harbor31.somerville.occnc.com [IPv6:2001:550:3800:203::3231]) (authenticated bits=128) by maildrop31.somerville.occnc.com (8.14.9/8.14.9) with ESMTP id t1PKaTq1086409; Wed, 25 Feb 2015 15:36:29 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201502252036.t1PKaTq1086409@maildrop31.somerville.occnc.com>
BTo: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
From: Curtis Villamizar <curtis@ipv6.occnc.com>
In-reply-to: Your message of "Tue, 24 Feb 2015 12:15:00 +0100." <87a903ef2j.wl-jch@pps.univ-paris-diderot.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <86407.1424896588.1@harbor31.somerville.occnc.com>
Date: Wed, 25 Feb 2015 15:36:29 -0500
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/bkFUnsMQB2xgaVTagZ06mk3Yt90>
Cc: Toerless Eckert <eckert@cisco.com>, "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] L2 link status [was: More about marginal links]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.com
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Wed, 25 Feb 2015 20:38:12 -0000

 
In message <87a903ef2j.wl-jch@pps.univ-paris-diderot.fr>
Juliusz Chroboczek writes:
>  
> > Thought: In general, my feeling is that L2 link status is widely relied
> > upon in commercial product/dpeloyments. If homenet feels it can not rely
> > on it due to the non-commercial nature of its development platforms,
> > thats an interesting aspect, especially because it could impact an IETF
> > standard that we'd like to see commercially implemented and then the
> > constraints could be different...
>  
> Are you referring to the routing protocol comparison, or to something else?
>  
> I have the impression that Babel and IS-IS behave essentially the same
> wrt. L2 status -- they both converge fast enough after link status has
> been established, and they essentially provide the same facilities for
> application-layer link sensing (IMHO Babel's Hello/IHU subprotocol is
> slightly more flexible, but that's probably not a big deal).
>  
> As to wireless links -- as far as I'm aware, making efficient use of
> wireless L2 information in a routing protocol is an open research problem.

Other than signal strength and collision rate, what L2 information is
available?  Per MAC information would be nice for the AP side or any
node in mesh or adhoc mode but that isn't collected anywhere AFAIK.

> -- Juliusz
>  
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet


ISPs mostly use Ethernet as point-to-point (PTP) links.  Including
using 100GbE as PTP.  No switches.  L2 Link down is one fast indicator
of link down.  But for Ethernet over transport gear (ie: OTN) BFD is
almost always used.  For short distances L2 over extended reach optics
can be used, including colored optics and WDM.  This is also PTP and
in this case BFD should not be needed.  To the extent that routers use
SONET or OTN interfaces, these have fast L2 link down indication and
are integrated with L3 link down detection.  In all of these detection
is on the order of 10 msec (geographic distance dependent), failover
using FRR is under 50 msec, and IGP convergence is well under a second
(typical 100-200 msec today AFAIK).  L3 hellos are way too slow.

BFD is not heavy weight.  L3 hellos (OSPF, ISIS) can be set down to 1s
with detection in 3s (too slow).

BFD, Hellos, or any form of probe traffic over wireless has the speed
of detection vs overhead issue.  At nominal 10 Mb/s (low end today for
wireless) a small probe would take about 0.1 msec (for example, 125
bytes including all overhead is about 1000 bits).  Not bad if running
100 probes/sec (30 msec detection) unless there are a very large
number of stations using the AP and doing the same thing.  In that
case 10 probes per second might be better.  A very high collision rate
(typically not due to probes, but to real traffic) might result in a
link down indication.  If that is the case, then moving to another AP
would be a good thing.

Flapping needs to be avoided if an alternate is available (ie: with
20% loss, in .2*.2*.2 = .008 = 0.8% of intervale a down indication
would occur).  If any packet received would bring it back up, then at
100 probes / sec, a change in IGP link state could occur about once a
second on average.  Remembering a link down and holding a down state
for a (longish) while would be a good thing.  If there is no alternate
route, not probing at all and/or holding an up state would be good.
OTOH- 20% loss borders on completely unusable.

Curtis


From nobody Wed Feb 25 12:47:12 2015
Return-Path: <hrogge@gmail.com>
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 3D52D1A8854 for <homenet@ietfa.amsl.com>; Wed, 25 Feb 2015 12:47:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 jjfF4g8RmcqJ for <homenet@ietfa.amsl.com>; Wed, 25 Feb 2015 12:47:10 -0800 (PST)
Received: from mail-wg0-x234.google.com (mail-wg0-x234.google.com [IPv6:2a00:1450:400c:c00::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CBA401A1EED for <homenet@ietf.org>; Wed, 25 Feb 2015 12:47:09 -0800 (PST)
Received: by wggz12 with SMTP id z12so6192683wgg.2 for <homenet@ietf.org>; Wed, 25 Feb 2015 12:47:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=j4D0GcKovAoBKmwLyDzsYb0h7vrEeAtSSyNiKylUYhA=; b=0U1IAduBRuOw3dlePER9r9yJP3rg+5eJ1ISoKTY2pceU2xLJnZpeSDJOvSIwQ4551m VX69Co96OGGPcB6AuhVw3kcW7OK/a1s+QpmZ9WpM0EfZ5zn3Myj6qiUS2/pBrJlW+wvI xgljXtvNnvuZkkbn0x0mLmPR8OVDNPawdh5KBujZzaGLrVkYTV7/GdOemedveL/8en4S uOAUgHxjbuiMiPEnnXIjdp1xp3rn8tR7okW8V/M0coi/9oOn1hxHFlOMufczKI6+iNKd HLnIav73RaBYN7t67TGxihwUUE4NY1h+5gMhQXugY3vy8iipNyZD/imxAUKA/2GRTy39 nLVA==
X-Received: by 10.194.78.231 with SMTP id e7mr9678648wjx.33.1424897228630; Wed, 25 Feb 2015 12:47:08 -0800 (PST)
MIME-Version: 1.0
Received: by 10.27.77.212 with HTTP; Wed, 25 Feb 2015 12:46:48 -0800 (PST)
In-Reply-To: <201502252036.t1PKaTq1086409@maildrop31.somerville.occnc.com>
References: <87a903ef2j.wl-jch@pps.univ-paris-diderot.fr> <201502252036.t1PKaTq1086409@maildrop31.somerville.occnc.com>
From: Henning Rogge <hrogge@gmail.com>
Date: Wed, 25 Feb 2015 21:46:48 +0100
Message-ID: <CAGnRvupwF3N9JQmi_TxWBXkEtO_59ZDQqAPCFcSyFDUVQP8EBw@mail.gmail.com>
To: curtis@ipv6.occnc.com
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/JcWvnp1t33cqMeXuO_xI1F4fBm4>
Cc: Toerless Eckert <eckert@cisco.com>, "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] L2 link status [was: More about marginal links]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Wed, 25 Feb 2015 20:47:11 -0000

On Wed, Feb 25, 2015 at 9:36 PM, Curtis Villamizar
<curtis@ipv6.occnc.com> wrote:
> In message <87a903ef2j.wl-jch@pps.univ-paris-diderot.fr>
> Juliusz Chroboczek writes:
>> As to wireless links -- as far as I'm aware, making efficient use of
>> wireless L2 information in a routing protocol is an open research problem.
>
> Other than signal strength and collision rate, what L2 information is
> available?  Per MAC information would be nice for the AP side or any
> node in mesh or adhoc mode but that isn't collected anywhere AFAIK.

Raw linkspeed and (on Linux) even Throughput to each neighbor... and a lot more.

Just run "iw wlan0 station dump" on a Linux system with wifi and you
will be surprised how much information you will get.

Henning Rogge


From nobody Wed Feb 25 12:50:51 2015
Return-Path: <mcr@sandelman.ca>
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 C31D21A8840 for <homenet@ietfa.amsl.com>; Wed, 25 Feb 2015 12:50:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 TWsJ090ZsDhU for <homenet@ietfa.amsl.com>; Wed, 25 Feb 2015 12:50:49 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 352DF1A1F02 for <homenet@ietf.org>; Wed, 25 Feb 2015 12:50:49 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 47E5E20012; Wed, 25 Feb 2015 15:59:04 -0500 (EST)
Received: by sandelman.ca (Postfix, from userid 179) id A01D163A21; Wed, 25 Feb 2015 15:50:47 -0500 (EST)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 84F80636A2; Wed, 25 Feb 2015 15:50:47 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Ray Hunter <v6ops@globis.net>
In-Reply-To: <54EDEEAA.5040302@globis.net>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <8B98F698-983D-4D2A-B5D1-7ACED27C275E@fugue.com> <alpine.DEB.2.02.1502191920560.4007@uplift.swm.pp.se> <CAPRuP3mpNJTu6mP+RAVKKO0kt60PogNtNbCUCRRqxe9im3EzjA@mail.gmail.com> <alpine.DEB.2.02.1502201042330.4007@uplift.swm.pp.se> <7A86BDC6-FF4B-49FF-B59C-BA1DEF463173@inf-net.nl> <alpine.DEB.2.02.1502201310050.4007@uplift.swm.pp.se> <09793905-8D12-49E0-A040-490F617C87FF@inf-net.nl> <alpine.DEB.2.02.1502201410510.4007@uplift.swm.pp.se> <54EDEEAA.5040302@globis.net>
X-Mailer: MH-E 8.6; nmh 1.3-dev; GNU Emacs 24.4.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Wed, 25 Feb 2015 15:50:47 -0500
Message-ID: <17359.1424897447@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/DdYDOpp7pzTQrk_-pTW0cdkMaRw>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>, Teco Boot <teco@inf-net.nl>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Wed, 25 Feb 2015 20:50:50 -0000

--=-=-=
Content-Type: text/plain


Ray Hunter <v6ops@globis.net> wrote:
    > I agree that WiFi roaming is a problem that needs addressing in
    > Homenet.

Yes, but can we rule it out of scope for now?

Can we agree that it's not strictly a routing problem, and that the set of
solutions that we are considering could be used, and that we could also
explain how to do something like automatically setup capwap using HNCP for
discovery, but that we don't have the head-of-queue block on this item for
now?

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-




--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEVAwUBVO41p4CLcPvd0N1lAQLk5QgAp/CBBzr1pw7Q30OENrB3ocw+L2iEeEei
WpfeeUlDFJ+biEUCGzIkrzWUfyacVZSjv3u3RVPYJZwaJq7NZGzup+Ye8yuBeF4c
i6mnTXID5xY6BMynyBu3akwVZQekVsgh7/hoWR64EpUy+W50h6beDBb9STZVRP6G
3Y8wNwIzsIARgxNrDl0VtrKEyeHTRvTo71hwFG9v+A+qkrp1jXBHNQfb8DjZCOeR
11cW6OFkdkbfYJgdBvsNCHyvD06OhRF3U82AJ7Np0uudp0dNEg3YwsOwEIuQ21uH
DCDoNOa+9dpIZWqp60777qtkXlKFmhwcL4MX1j3+zv448R7OWfGo5Q==
=PK4l
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Wed Feb 25 13:00:35 2015
Return-Path: <mark@townsley.net>
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 2A0E31A888F for <homenet@ietfa.amsl.com>; Wed, 25 Feb 2015 13:00:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 TWlo5EQ7eM_C for <homenet@ietfa.amsl.com>; Wed, 25 Feb 2015 13:00:32 -0800 (PST)
Received: from mail-wg0-f46.google.com (mail-wg0-f46.google.com [74.125.82.46]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 76BBC1A888C for <homenet@ietf.org>; Wed, 25 Feb 2015 13:00:32 -0800 (PST)
Received: by wghl18 with SMTP id l18so6201332wgh.7 for <homenet@ietf.org>; Wed, 25 Feb 2015 13:00:31 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=Qb/IASfc1bvhkYPKnhI6/IIXlsOhZEFXxO2xUdTt7bg=; b=iBf/WrMaVaHrQHPnkq90oNDEiuxZHLeyVXfpB7W9g9U+FOlDIlB5NWgTjPG2Q9l+c3 /97IqxrlKE7Xmo7dUMumbhZ/EOBKZyUZ4yd3zLGJsrJxGudJVMOHDo1b5Qk+kIoldALC E3gFsCUHWp3g2WHo+0L7a+IlQt8VY1U0/fGL0QCxvbxutPTTO+4pAXNYKlsdTw5kdkK5 TMAQVL1KFMRWsl9W0n7XpmebK+qEcbXIv3GuljLh/AP4PjPCTiwWOwhPsKxGUQrv08MY +0xgqOKpoSZB42kTfcDTAxiqnde+fGsnOXbmWwm7LkPX5JbBTTlzFLjODmZuRHI9o8yq VJ6w==
X-Gm-Message-State: ALoCoQmDF4T1y3dCXizgdh7PPUgY4bq/sla2oiHou32jpP3G2JZF57u16p3sfLu/YjntFZtHBpD4
X-Received: by 10.194.78.231 with SMTP id e7mr9769311wjx.33.1424898031115; Wed, 25 Feb 2015 13:00:31 -0800 (PST)
Received: from [10.176.116.117] ([37.160.252.109]) by mx.google.com with ESMTPSA id gi9sm26737271wib.21.2015.02.25.13.00.29 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 25 Feb 2015 13:00:30 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
From: Mark Townsley <mark@townsley.net>
X-Mailer: iPad Mail (12B440)
In-Reply-To: <17359.1424897447@sandelman.ca>
Date: Wed, 25 Feb 2015 22:00:26 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <9A5ED36C-D062-4180-AA6D-00346E19A545@townsley.net>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <8B98F698-983D-4D2A-B5D1-7ACED27C275E@fugue.com> <alpine.DEB.2.02.1502191920560.4007@uplift.swm.pp.se> <CAPRuP3mpNJTu6mP+RAVKKO0kt60PogNtNbCUCRRqxe9im3EzjA@mail.gmail.com> <alpine.DEB.2.02.1502201042330.4007@uplift.swm.pp.se> <7A86BDC6-FF4B-49FF-B59C-BA1DEF463173@inf-net.nl> <alpine.DEB.2.02.1502201310050.4007@uplift.swm.pp.se> <09793905-8D12-49E0-A040-490F617C87FF@inf-net.nl> <alpine.DEB.2.02.1502201410510.4007@uplift.swm.pp.se> <54EDEEAA.5040302@globis.net> <17359.1424897447@sandelman.ca>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/PXbTj5l2tUDmZsADao_ovvqGxtw>
Cc: Ray Hunter <v6ops@globis.net>, "homenet@ietf.org Group" <homenet@ietf.org>, Teco Boot <teco@inf-net.nl>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Wed, 25 Feb 2015 21:00:34 -0000

> On Feb 25, 2015, at 9:50 PM, Michael Richardson <mcr+ietf@sandelman.ca> wr=
ote:
>=20
>=20
> Ray Hunter <v6ops@globis.net> wrote:
>> I agree that WiFi roaming is a problem that needs addressing in
>> Homenet.
>=20
> Yes, but can we rule it out of scope for now?

Yes, we can.

I think the WG needs to focus on securing success before taking on wild succ=
ess at this moment in time.=20

- Mark

>=20
> Can we agree that it's not strictly a routing problem, and that the set of=

> solutions that we are considering could be used, and that we could also
> explain how to do something like automatically setup capwap using HNCP for=

> discovery, but that we don't have the head-of-queue block on this item for=

> now?
>=20
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
> -=3D IPv6 IoT consulting =3D-
>=20
>=20
>=20
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet


From nobody Wed Feb 25 14:40:11 2015
Return-Path: <curtis@ipv6.occnc.com>
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 2F2801A8938 for <homenet@ietfa.amsl.com>; Wed, 25 Feb 2015 14:40:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.587
X-Spam-Level: 
X-Spam-Status: No, score=0.587 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, J_CHICKENPOX_27=0.6, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 SPU2P2Ob6fs6 for <homenet@ietfa.amsl.com>; Wed, 25 Feb 2015 14:40:07 -0800 (PST)
Received: from maildrop31.somerville.occnc.com (maildrop31.somerville.occnc.com [IPv6:2001:550:3800:203::3131]) (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 4720F1A1A99 for <homenet@ietf.org>; Wed, 25 Feb 2015 14:40:06 -0800 (PST)
Received: from harbor31.somerville.occnc.com (harbor31.somerville.occnc.com [IPv6:2001:550:3800:203::3231]) (authenticated bits=128) by maildrop31.somerville.occnc.com (8.14.9/8.14.9) with ESMTP id t1PMdqAX088420; Wed, 25 Feb 2015 17:39:52 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201502252239.t1PMdqAX088420@maildrop31.somerville.occnc.com>
To: Mark Townsley <mark@townsley.net>
From: Curtis Villamizar <curtis@ipv6.occnc.com>
In-reply-to: Your message of "Mon, 23 Feb 2015 15:58:36 +0100." <CAESTAVvjazOmppFgoigtAraNUEoKEB5HHmKFgNAe-v31+rOzYg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <88418.1424903992.1@harbor31.somerville.occnc.com>
Content-Transfer-Encoding: quoted-printable
Date: Wed, 25 Feb 2015 17:39:52 -0500
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/rBKGF2ksxD_a1D84V7RJi9TSzQI>
Cc: Ole Troan <otroan@employees.org>, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>, "homenet@ietf.org Group" <homenet@ietf.org>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] Roaming hosts [was: Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.com
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Wed, 25 Feb 2015 22:40:10 -0000

In message <CAESTAVvjazOmppFgoigtAraNUEoKEB5HHmKFgNAe-v31+rOzYg@mail.gmail=
.com>
Mark Townsley writes:
 =

> When a host connects to a different link covered by a different subnet,
> indeed it will require a new IP address. That's pretty fundamental to wh=
at
> a subnet is. Hosts are getting better and better at handling multiple
> addresses, of both versions, coming and going. MPTCP should continue to
> help in this regard. I'm a big fan of seeing more and more MPTCP, and I'=
ve
> been impressed at the ability of modern devices to upgrade their host
> stacks in the past 4-5 years (vs. the decade or so before). I'll remain
> cautiously hopeful here for the long term.
>  =

> In the mean time, I fully expect that to support seamless wifi roaming f=
rom
> one AP to another there will have to be some sort of bridging or tunneli=
ng
> (capwap, et. al) taking place to keep the single ethernet wifi subnet al=
ive
> for IPv4 and less modern IPv6 hosts. That doesn't mean there will be no
> room for routing in the home, as one of the primary motivations for IP
> routing is to support diverse media types. i.e, it's much easier I think=
 if
> wi-fi only has to worry about roaming within wi-fi, and not MOCA, EoPL,
> 802.15.4, Bluetooth LE, etc. as well.
>  =

> One day if/when hosts and apps finally become fully resilient to IP addr=
ess
> changes, then it could become much easier on APs as they will have the
> chance to simply hand out a new IPv6 address and route, avoiding bridgin=
g
> and/or tunneling tricks. That could be a nice win for wifi scalability, =
but
> to be honest is shrouded in so many operational practicalities and movin=
g
> parts that it's best not to try pretend that this will come to pass even=
 if
> we are successful in providing the world with zero-touch IP routing
> technology in the home. It could be a very nice bonus, and I hope it
> happens, but I wouldn't want to set the bar that high in the near term a=
s
> something homenet can make happen on its own.
>  =

> - Mark


The way this was solved circa early-mid 1990s (with configuration
required and a bit of code hack) involved putting a fixed address on
the loopback interface.  For incoming TCP connections, only an
ifconfig lo0 was required.

For outbound TCP connections, no MPTCP was needed, just an ability to
favor binding to the loopback address on critical applications where
an outbound connection is made.  This was the code change needed back
then (and was tupically done to klogin, and the other kerberos enabled
r-commands).  Today, with address selection policy (ie: ip6addrctl on
BSD), no code changes are needed for outbound TCP connections as well.

This type of allocation would work if moving from one AP to another
within an administrative domain (within a homenet or from an office to
a conferance room at work) but not when roaming from home to the
coffee shop wifi AP.

Here is one way it might get done.

It might be worth considering a multiple means to hand out addresses
for lookbacks.  For example extensions to DHCP, SLAAC, DHCPv6, would
require only minimal host changes.  Hosts could also run OSPF and be
stub routers (can be dual or multi homed, but no transit).

A router can use OSPF link local addresses as it does today and make
an implicit request for a loopback address.  The implicit request is
made by its existance in the topology with no routable address.
Allocation can be by the CPE at a provider border for the router
itself, mapping OSPF or ISIS router-id to the requested prefix.
Explicit requests can be made using a TLV with a MAC associated with a
DHCP lease.  Together these two TLVs imply a /32 or /128 stub.

If a host is dual homed and gets information from DHCP, then when
making a request on a second interface, its already allocated /32
and/or /128 or its other MAC can be included in the DHCP request to
avoid a second allocation.  The router could then advertise an
alternate way to reach that loopback.  The host would now be a stub
reachable via two routers.

For the benefit of older OSPF or ISIS implementations if there were
such a thing in the home, any /32 or /128 stub can be explicitly
advertised into the LSDB.

I don't expect a homenet to get overrun with /128 addresses in the
OSPF or ISIS LSDB.

Hosts with a /128 on its own loopback would use the default route to
get to other stubs within the same /64 as its loopback.  This would
only be updated hosts, so it would be safe to assume they won't make
the /128 into a /64.

Note that hosts then don't require routeable interface addresses, only
an address on the loopback.

This works within an administative domain and doesn't require that the
other side of a TCP connection to be upgraded (as is the case with
MPTCP).  There are no TCP stack changes required, but also
implementing MPTCP won't hurt when wandering to the coffee shop.

Old hosts works as they did before.  They get two interface addresses.
As long as they send traffic to an interface that is up and gave it a
default route things should work.  Switch over based on lease expire
would be bad with long lease times (ie: AP is a switch but
router/dhcpd behind the AP went down).

Old routers work as before except for some reason they see a lot of
IPV4 /32 and/or IPv6 /128 stubs.  Old dumb routers work as long as the
WAN port is not used since they act as NAT from the WAN side but act
as a switch on the LAN side.  Switches are tolerated.

If wifi APs are not used for transit and the APs are routers rather
than switches, then there is no reason to run OSPF over wifi in
broadcast mode.  If the APs are dumb switches, the WiFi hosts look
like Ethernet hosts to any router attached to the AP with Ethernet,
therefore the WiFi subnet might see OSPF multicast packets intended
for other OSPF routers.

Curtis


From nobody Thu Feb 26 04:28:37 2015
Return-Path: <teco@inf-net.nl>
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 8871D1A8032 for <homenet@ietfa.amsl.com>; Thu, 26 Feb 2015 04:28:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 9764FjFZlbza for <homenet@ietfa.amsl.com>; Thu, 26 Feb 2015 04:28:32 -0800 (PST)
Received: from mail-ie0-f175.google.com (mail-ie0-f175.google.com [209.85.223.175]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A7C3D1A2119 for <homenet@ietf.org>; Thu, 26 Feb 2015 04:28:31 -0800 (PST)
Received: by iecrl12 with SMTP id rl12so14230796iec.4 for <homenet@ietf.org>; Thu, 26 Feb 2015 04:28:31 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=b+Lf2gcQTR4h21cIwgbA1EZda1LJDLHjIJG/aYoJ5W0=; b=bPSRafDYum6dVorqXr7kc59ZR2dK0TSCcyQGnhbFOECcq3L0lY/eDn5HYURuiRM3nj MeJeUc5MYyRwksyA9mqa8SHX0HvvSHmTdeLrY0aZhwbnmuP5r6Ozdm46UdQ5huo7E2ic ZRT0pJvaLzz7fHzWscV13FcTNlb4irEY8H4BDV3LFAq+5hhHlQi1jsYd/lfPVNne8xfT YCI7VygAREpmzut90xthL0r/Y0c2hm16ofojBY1tz0/7tLtrbsrNmW7zDL7O/sk8R75s gNQxtAZh/4Ccj/MGvwQpsAMrP+lQdjBnC6lgU6Oqx9IC5GIzM8KOy1YyFX+HZffYVxLw zgKw==
X-Gm-Message-State: ALoCoQkg3yq9wimh7YhWzM3VMZ0af4xqnznR4wRUPjSY29BHa2PTeiS4U/zy9FNhbN6LdMqx4xj4
X-Received: by 10.43.140.68 with SMTP id iz4mr9419241icc.77.1424953711334; Thu, 26 Feb 2015 04:28:31 -0800 (PST)
Received: from [10.10.10.211] (CPE68b6fcfdbd03-CM68b6fcfdbd00.cpe.net.cable.rogers.com. [99.240.94.20]) by mx.google.com with ESMTPSA id m38sm297855ioi.39.2015.02.26.04.28.30 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 26 Feb 2015 04:28:30 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Teco Boot <teco@inf-net.nl>
In-Reply-To: <9A5ED36C-D062-4180-AA6D-00346E19A545@townsley.net>
Date: Thu, 26 Feb 2015 13:28:31 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <7B49A1E1-9424-4577-B59A-A75509403A2E@inf-net.nl>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <8B98F698-983D-4D2A-B5D1-7ACED27C275E@fugue.com> <alpine.DEB.2.02.1502191920560.4007@uplift.swm.pp.se> <CAPRuP3mpNJTu6mP+RAVKKO0kt60PogNtNbCUCRRqxe9im3EzjA@mail.gmail.com> <alpine.DEB.2.02.1502201042330.4007@uplift.swm.pp.se> <7A86BDC6-FF4B-49FF-B59C-BA1DEF463173@inf-net.nl> <alpine.DEB.2.02.1502201310050.4007@uplift.swm.pp.se> <09793905-8D12-49E0-A040-490F617C87FF@inf-net.nl> <alpine.DEB.2.02.1502201410510.4007@uplift.swm.pp.se> <54EDEEAA.5040302@globis.net> <17359.1424897447@sandelman.ca> <9A5ED36C-D062-4180-AA6D-00346E19A545@townsley.net>
To: Mark Townsley <mark@townsley.net>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/60K6kqdQHTf3wQzoovJ8BpW0_H4>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, "homenet@ietf.org Group" <homenet@ietf.org>, Mikael Abrahamsson <swmike@swm.pp.se>, Ray Hunter <v6ops@globis.net>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 26 Feb 2015 12:28:34 -0000

> Op 25 feb. 2015, om 22:00 heeft Mark Townsley <mark@townsley.net> het =
volgende geschreven:
>=20
>=20
>=20
>=20
>=20
>> On Feb 25, 2015, at 9:50 PM, Michael Richardson =
<mcr+ietf@sandelman.ca> wrote:
>>=20
>>=20
>> Ray Hunter <v6ops@globis.net> wrote:
>>> I agree that WiFi roaming is a problem that needs addressing in
>>> Homenet.
>>=20
>> Yes, but can we rule it out of scope for now?
>=20
> Yes, we can.
>=20
> I think the WG needs to focus on securing success before taking on =
wild success at this moment in time.=20

When performance in dual stack networks with multiple WiFi AP's in homes =
suffers from homenet protocols, this WG produces dead protocols. I am =
more hopeful. I hope we can enable 802.11 fast handover by distributing =
the required info. Still open question how to route or bridge over the =
wired backbone.

Teco


>=20
> - Mark
>=20
>>=20
>> Can we agree that it's not strictly a routing problem, and that the =
set of
>> solutions that we are considering could be used, and that we could =
also
>> explain how to do something like automatically setup capwap using =
HNCP for
>> discovery, but that we don't have the head-of-queue block on this =
item for
>> now?
>>=20
>> --
>> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>> -=3D IPv6 IoT consulting =3D-
>>=20
>>=20
>>=20
>> _______________________________________________
>> homenet mailing list
>> homenet@ietf.org
>> https://www.ietf.org/mailman/listinfo/homenet


From nobody Thu Feb 26 04:57:08 2015
Return-Path: <mark@townsley.net>
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 123DC1A903A for <homenet@ietfa.amsl.com>; Thu, 26 Feb 2015 04:57:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] 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 FByfMjgNfKZO for <homenet@ietfa.amsl.com>; Thu, 26 Feb 2015 04:57:05 -0800 (PST)
Received: from mail-la0-f52.google.com (mail-la0-f52.google.com [209.85.215.52]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1AAD91A9054 for <homenet@ietf.org>; Thu, 26 Feb 2015 04:56:24 -0800 (PST)
Received: by labhs14 with SMTP id hs14so10750261lab.4 for <homenet@ietf.org>; Thu, 26 Feb 2015 04:56:22 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=es98krpZ6GESNCwyNyUrkxIWngBYBRJcbiUdho7brSc=; b=FRmEPL796YMstUyTwmHELsirjDWR/bujmjd5rOr62tPEr36qfBxX+UYVS2hoHd/L2b uo8NRaCxfVct81ESShvY4x8Oi98gXbdCIXU4OTjU2J6oFD/ZtxcspvOtEmN4Qf1BRWKl 4TrOKXNWSkePFyz6xn85L6mDg/BfzfulDy1s2VwN/C52EwzYf484SkLFwMJjwnzmMX2t rYeZutMymZrzTs3p80zKaBPc1PU7JHyQsqvzShdpRm2u8LiTSmv/2nzmWD3iaSELN/jO Pak5w99A7dFsC8+6m4oM5RjWxbqlFdlwIkooT/yn1r5EX2GFEDThsSD+cf7Q1syZO244 nzmA==
X-Gm-Message-State: ALoCoQnm2PRNR514biUkaGBu9yCAia+6rCizczo2JXj9adwxIhOmNsFeGzSFWFgTBm/guCXDSfgs
MIME-Version: 1.0
X-Received: by 10.152.28.73 with SMTP id z9mr7444849lag.28.1424955382309; Thu, 26 Feb 2015 04:56:22 -0800 (PST)
Received: by 10.112.135.200 with HTTP; Thu, 26 Feb 2015 04:56:21 -0800 (PST)
In-Reply-To: <7B49A1E1-9424-4577-B59A-A75509403A2E@inf-net.nl>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <8B98F698-983D-4D2A-B5D1-7ACED27C275E@fugue.com> <alpine.DEB.2.02.1502191920560.4007@uplift.swm.pp.se> <CAPRuP3mpNJTu6mP+RAVKKO0kt60PogNtNbCUCRRqxe9im3EzjA@mail.gmail.com> <alpine.DEB.2.02.1502201042330.4007@uplift.swm.pp.se> <7A86BDC6-FF4B-49FF-B59C-BA1DEF463173@inf-net.nl> <alpine.DEB.2.02.1502201310050.4007@uplift.swm.pp.se> <09793905-8D12-49E0-A040-490F617C87FF@inf-net.nl> <alpine.DEB.2.02.1502201410510.4007@uplift.swm.pp.se> <54EDEEAA.5040302@globis.net> <17359.1424897447@sandelman.ca> <9A5ED36C-D062-4180-AA6D-00346E19A545@townsley.net> <7B49A1E1-9424-4577-B59A-A75509403A2E@inf-net.nl>
Date: Thu, 26 Feb 2015 13:56:21 +0100
Message-ID: <CAESTAVvs8AOfCDdhETkdcAO3K_3nj+xgL1m89umszP+E3a1fBw@mail.gmail.com>
From: Mark Townsley <mark@townsley.net>
To: Teco Boot <teco@inf-net.nl>
Content-Type: multipart/alternative; boundary=089e0158c026623b51050ffd477d
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/nWf6X6TVPNL5WXVk3SbocGgYs0c>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, "homenet@ietf.org Group" <homenet@ietf.org>, Mikael Abrahamsson <swmike@swm.pp.se>, Ray Hunter <v6ops@globis.net>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 26 Feb 2015 12:57:07 -0000

--089e0158c026623b51050ffd477d
Content-Type: text/plain; charset=UTF-8

On Thu, Feb 26, 2015 at 1:28 PM, Teco Boot <teco@inf-net.nl> wrote:

>
> > Op 25 feb. 2015, om 22:00 heeft Mark Townsley <mark@townsley.net> het
> volgende geschreven:
> >
> >
> >
> >
> >
> >> On Feb 25, 2015, at 9:50 PM, Michael Richardson <mcr+ietf@sandelman.ca>
> wrote:
> >>
> >>
> >> Ray Hunter <v6ops@globis.net> wrote:
> >>> I agree that WiFi roaming is a problem that needs addressing in
> >>> Homenet.
> >>
> >> Yes, but can we rule it out of scope for now?
> >
> > Yes, we can.
> >
> > I think the WG needs to focus on securing success before taking on wild
> success at this moment in time.
>
> When performance in dual stack networks with multiple WiFi AP's in homes
> suffers from homenet protocols, this WG produces dead protocols.


Why would homenet cause wifi APs to suffer more than they do today? Worst
case, wifi remains a single bridged dual-stack LAN. Best case, routing is
possible and hosts are resilient to IP address changes. Somewhere in
between HNCP helps with auto-configuration in one way or another. I don't
see how the status quo path we are without Homenet can be worse with
Homenet (separating out here whatever overhead of getting homenet itself
deployed).


> I am more hopeful. I hope we can enable 802.11 fast handover by
> distributing the required info. Still open question how to route or bridge
> over the wired backbone.
>

 certainly do not want to inhibit your hope in anyway. Indeed, history
shows that we successful protocols are often deployed in ways the designers
do not expect. Just trying to nudge the group towards a bit more focus in
order to ship sooner rather than later.

- Mark


> Teco
>
>
> >
> > - Mark
> >
> >>
> >> Can we agree that it's not strictly a routing problem, and that the set
> of
> >> solutions that we are considering could be used, and that we could also
> >> explain how to do something like automatically setup capwap using HNCP
> for
> >> discovery, but that we don't have the head-of-queue block on this item
> for
> >> now?
> >>
> >> --
> >> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
> >> -= IPv6 IoT consulting =-
> >>
> >>
> >>
> >> _______________________________________________
> >> homenet mailing list
> >> homenet@ietf.org
> >> https://www.ietf.org/mailman/listinfo/homenet
>
>

--089e0158c026623b51050ffd477d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Thu, Feb 26, 2015 at 1:28 PM, Teco Boot <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:teco@inf-net.nl" target=3D"_blank">teco@inf-net.nl</a>&gt;</spa=
n> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px =
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-=
style:solid;padding-left:1ex"><br>
&gt; Op 25 feb. 2015, om 22:00 heeft Mark Townsley &lt;<a href=3D"mailto:ma=
rk@townsley.net">mark@townsley.net</a>&gt; het volgende geschreven:<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;&gt; On Feb 25, 2015, at 9:50 PM, Michael Richardson &lt;<a href=3D"mai=
lto:mcr%2Bietf@sandelman.ca">mcr+ietf@sandelman.ca</a>&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; Ray Hunter &lt;<a href=3D"mailto:v6ops@globis.net">v6ops@globis.ne=
t</a>&gt; wrote:<br>
&gt;&gt;&gt; I agree that WiFi roaming is a problem that needs addressing i=
n<br>
&gt;&gt;&gt; Homenet.<br>
&gt;&gt;<br>
&gt;&gt; Yes, but can we rule it out of scope for now?<br>
&gt;<br>
&gt; Yes, we can.<br>
&gt;<br>
&gt; I think the WG needs to focus on securing success before taking on wil=
d success at this moment in time.<br>
<br>
When performance in dual stack networks with multiple WiFi AP&#39;s in home=
s suffers from homenet protocols, this WG produces dead protocols. </blockq=
uote><div><br></div><div>Why would homenet cause wifi APs to suffer more th=
an they do today? Worst case, wifi remains a single bridged dual-stack LAN.=
 Best case, routing is possible and hosts are resilient to IP address chang=
es. Somewhere in between HNCP helps with auto-configuration in one way or a=
nother. I don&#39;t see how the status quo path we are without Homenet can =
be worse with Homenet (separating out here whatever overhead of getting hom=
enet itself deployed).</div><div>=C2=A0</div><blockquote class=3D"gmail_quo=
te" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-col=
or:rgb(204,204,204);border-left-style:solid;padding-left:1ex">I am more hop=
eful. I hope we can enable 802.11 fast handover by distributing the require=
d info. Still open question how to route or bridge over the wired backbone.=
<br></blockquote><div><br></div><div>=C2=A0certainly do not want to inhibit=
 your hope in anyway.=C2=A0Indeed, history shows that we successful protoco=
ls are often deployed in ways the designers do not expect. Just trying to n=
udge the group towards a bit more focus in order to ship sooner rather than=
 later.=C2=A0</div><div><br></div><div>- Mark</div><div><br></div><blockquo=
te class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-widt=
h:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-le=
ft:1ex">
<br>
Teco<br>
<br>
<br>
&gt;<br>
&gt; - Mark<br>
&gt;<br>
&gt;&gt;<br>
&gt;&gt; Can we agree that it&#39;s not strictly a routing problem, and tha=
t the set of<br>
&gt;&gt; solutions that we are considering could be used, and that we could=
 also<br>
&gt;&gt; explain how to do something like automatically setup capwap using =
HNCP for<br>
&gt;&gt; discovery, but that we don&#39;t have the head-of-queue block on t=
his item for<br>
&gt;&gt; now?<br>
<span class=3D""><font color=3D"#888888">&gt;&gt;<br>
&gt;&gt; --<br>
&gt;&gt; Michael Richardson &lt;<a href=3D"mailto:mcr%2BIETF@sandelman.ca">=
mcr+IETF@sandelman.ca</a>&gt;, Sandelman Software Works<br>
&gt;&gt; -=3D IPv6 IoT consulting =3D-<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; _______________________________________________<br>
&gt;&gt; homenet mailing list<br>
&gt;&gt; <a href=3D"mailto:homenet@ietf.org">homenet@ietf.org</a><br>
&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/homenet" target=
=3D"_blank">https://www.ietf.org/mailman/listinfo/homenet</a><br>
<br>
</font></span></blockquote></div><br></div></div>

--089e0158c026623b51050ffd477d--


From nobody Thu Feb 26 20:27:24 2015
Return-Path: <teco@inf-net.nl>
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 E07761A00DB for <homenet@ietfa.amsl.com>; Thu, 26 Feb 2015 20:27:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 wQfP-8ImE3K9 for <homenet@ietfa.amsl.com>; Thu, 26 Feb 2015 20:27:20 -0800 (PST)
Received: from mail-ie0-f176.google.com (mail-ie0-f176.google.com [209.85.223.176]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 609411A00BF for <homenet@ietf.org>; Thu, 26 Feb 2015 20:27:19 -0800 (PST)
Received: by iecrd18 with SMTP id rd18so25559484iec.8 for <homenet@ietf.org>; Thu, 26 Feb 2015 20:27:19 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=/+XzRP4MFrVWow6qae2umtYU95R2/AKWj9xtoRhNrlc=; b=NS5k6Bb5h6GQLlZAWBDBOTAOk+BQsLyolxp/3RSAutEvu36ajis11IlvySWh4t2m3p hqYvrBKy6MObVcfjT2ymQOHTcViknK1NP37Qaiqs/c4MV2y/DlsHVFV87/X2E3G3MBpC 6+EPzwO8ZlyFtvABVeF5gEcfn+fexJU6doewEXH/cOxZRfodKVmkHP1hetk259uPtReX 2WgEu/lbTJGPX4OEpEBMfqYxugYXd7+vmZzANhQMfI9oYas18fsgBqD5aNZG6DmMcuJe nvF9a+ZFmqE2DZCuVXOG7GF/ADOaJ0E7Mxd7Nk8AY6BlkoQen5D3Y+DT1plR43vgUVHS 43hQ==
X-Gm-Message-State: ALoCoQn3/cKgx6RirUTzTRyOUaH+54c2DByhgdd+SA9juodXQS2lR5Brx2gBTsOzK2APEFFI7oIN
X-Received: by 10.50.66.243 with SMTP id i19mr536603igt.7.1425011239250; Thu, 26 Feb 2015 20:27:19 -0800 (PST)
Received: from [10.10.10.211] (CPE68b6fcfdbd03-CM68b6fcfdbd00.cpe.net.cable.rogers.com. [99.240.94.20]) by mx.google.com with ESMTPSA id y142sm1633879iod.25.2015.02.26.20.27.18 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 26 Feb 2015 20:27:18 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Teco Boot <teco@inf-net.nl>
In-Reply-To: <CAESTAVvs8AOfCDdhETkdcAO3K_3nj+xgL1m89umszP+E3a1fBw@mail.gmail.com>
Date: Fri, 27 Feb 2015 05:27:20 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <E403F12F-53AE-480F-B7D9-BE4621DF21A2@inf-net.nl>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <8B98F698-983D-4D2A-B5D1-7ACED27C275E@fugue.com> <alpine.DEB.2.02.1502191920560.4007@uplift.swm.pp.se> <CAPRuP3mpNJTu6mP+RAVKKO0kt60PogNtNbCUCRRqxe9im3EzjA@mail.gmail.com> <alpine.DEB.2.02.1502201042330.4007@uplift.swm.pp.se> <7A86BDC6-FF4B-49FF-B59C-BA1DEF463173@inf-net.nl> <alpine.DEB.2.02.1502201310050.4007@uplift.swm.pp.se> <09793905-8D12-49E0-A040-490F617C87FF@inf-net.nl> <alpine.DEB.2.02.1502201410510.4007@uplift.swm.pp.se> <54EDEEAA.5040302@globis.net> <17359.1424897447@sandelman.ca> <9A5ED36C-D062-4180-AA6D-00346E19A545@townsley.net> <7B49A1E1-9424-4577-B59A-A75509403A2E@inf-net.nl> <CAESTAVvs8AOfCDdhETkdcAO3K_3nj+xgL1m89umszP+E3a1fBw@mail.gmail.com>
To: Mark Townsley <mark@townsley.net>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/yiXOLJmo1RE_h7FdbSj2Owyjw5w>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, "homenet@ietf.org Group" <homenet@ietf.org>, Mikael Abrahamsson <swmike@swm.pp.se>, Ray Hunter <v6ops@globis.net>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 27 Feb 2015 04:27:23 -0000

> Op 26 feb. 2015, om 13:56 heeft Mark Townsley <mark@townsley.net> het =
volgende geschreven:
>=20
>=20
>=20
> On Thu, Feb 26, 2015 at 1:28 PM, Teco Boot <teco@inf-net.nl> wrote:
>=20
> > Op 25 feb. 2015, om 22:00 heeft Mark Townsley <mark@townsley.net> =
het volgende geschreven:
> >
> >
> >
> >
> >
> >> On Feb 25, 2015, at 9:50 PM, Michael Richardson =
<mcr+ietf@sandelman.ca> wrote:
> >>
> >>
> >> Ray Hunter <v6ops@globis.net> wrote:
> >>> I agree that WiFi roaming is a problem that needs addressing in
> >>> Homenet.
> >>
> >> Yes, but can we rule it out of scope for now?
> >
> > Yes, we can.
> >
> > I think the WG needs to focus on securing success before taking on =
wild success at this moment in time.
>=20
> When performance in dual stack networks with multiple WiFi AP's in =
homes suffers from homenet protocols, this WG produces dead protocols.
>=20
> Why would homenet cause wifi APs to suffer more than they do today? =
Worst case, wifi remains a single bridged dual-stack LAN. Best case, =
routing is possible and hosts are resilient to IP address changes. =
Somewhere in between HNCP helps with auto-configuration in one way or =
another. I don't see how the status quo path we are without Homenet can =
be worse with Homenet (separating out here whatever overhead of getting =
homenet itself deployed).

Today's WiFi stacks typically prefer staying on connected SSID, until =
the link is really bad and breaks. Then the alternative SSID is =
selected, IP address is flushed and a new IP address is requested. This =
takes time. Connections break.

Staying on the same SSID has advantages: IP address survives handover so =
connections continue to work. Also smarter handover can take place, this =
eliminates the bad link.

So my opinion is that the homenet protocols shall be able to support a =
layer-2 backbone over a wired backbone connecting a set of access =
points. Or provide an alternative that works well over a layer-3 =
backbone. I'm all ears.

Teco


> =20
> I am more hopeful. I hope we can enable 802.11 fast handover by =
distributing the required info. Still open question how to route or =
bridge over the wired backbone.
>=20
>  certainly do not want to inhibit your hope in anyway. Indeed, history =
shows that we successful protocols are often deployed in ways the =
designers do not expect. Just trying to nudge the group towards a bit =
more focus in order to ship sooner rather than later.=20
>=20
> - Mark
>=20
>=20
> Teco
>=20
>=20
> >
> > - Mark
> >
> >>
> >> Can we agree that it's not strictly a routing problem, and that the =
set of
> >> solutions that we are considering could be used, and that we could =
also
> >> explain how to do something like automatically setup capwap using =
HNCP for
> >> discovery, but that we don't have the head-of-queue block on this =
item for
> >> now?
> >>
> >> --
> >> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software =
Works
> >> -=3D IPv6 IoT consulting =3D-
> >>
> >>
> >>
> >> _______________________________________________
> >> homenet mailing list
> >> homenet@ietf.org
> >> https://www.ietf.org/mailman/listinfo/homenet
>=20
>=20


From nobody Fri Feb 27 03:39:22 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 10F861A9174 for <homenet@ietfa.amsl.com>; Fri, 27 Feb 2015 03:39:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35] autolearn=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 kDLFYvU3hp8a for <homenet@ietfa.amsl.com>; Fri, 27 Feb 2015 03:39:18 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 4E9301A916C for <homenet@ietf.org>; Fri, 27 Feb 2015 03:39:18 -0800 (PST)
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t1RBdF01017574; Fri, 27 Feb 2015 12:39:15 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id 34EB12C6C67; Fri, 27 Feb 2015 12:39:15 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id wbdXqc6YZGNh; Fri, 27 Feb 2015 12:39:13 +0100 (CET)
Received: from ijon.pps.univ-paris-diderot.fr (user-109-243-141-10.play-internet.pl [109.243.141.10]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 14A512C6C61; Fri, 27 Feb 2015 12:39:08 +0100 (CET)
Date: Fri, 27 Feb 2015 12:39:07 +0100
Message-ID: <87twy7ziqs.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Mark Townsley <mark@townsley.net>
In-Reply-To: <CAESTAVvs8AOfCDdhETkdcAO3K_3nj+xgL1m89umszP+E3a1fBw@mail.gmail.com>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <8B98F698-983D-4D2A-B5D1-7ACED27C275E@fugue.com> <alpine.DEB.2.02.1502191920560.4007@uplift.swm.pp.se> <CAPRuP3mpNJTu6mP+RAVKKO0kt60PogNtNbCUCRRqxe9im3EzjA@mail.gmail.com> <alpine.DEB.2.02.1502201042330.4007@uplift.swm.pp.se> <7A86BDC6-FF4B-49FF-B59C-BA1DEF463173@inf-net.nl> <alpine.DEB.2.02.1502201310050.4007@uplift.swm.pp.se> <09793905-8D12-49E0-A040-490F617C87FF@inf-net.nl> <alpine.DEB.2.02.1502201410510.4007@uplift.swm.pp.se> <54EDEEAA.5040302@globis.net> <17359.1424897447@sandelman.ca> <9A5ED36C-D062-4180-AA6D-00346E19A545@townsley.net> <7B49A1E1-9424-4577-B59A-A75509403A2E@inf-net.nl> <CAESTAVvs8AOfCDdhETkdcAO3K_3nj+xgL1m89umszP+E3a1fBw@mail.gmail.com>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [194.254.61.138]); Fri, 27 Feb 2015 12:39:15 +0100 (CET)
X-Miltered: at korolev with ID 54F05763.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54F05763.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54F05763.000 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/FEDEqmvrLxhcoXLTbFhZd0I4dpE>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, "homenet@ietf.org Group" <homenet@ietf.org>, Teco Boot <teco@inf-net.nl>, Ray Hunter <v6ops@globis.net>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 27 Feb 2015 11:39:20 -0000

>> When performance in dual stack networks with multiple WiFi AP's in homes
>> suffers from homenet protocols, this WG produces dead protocols.

> Why would homenet cause wifi APs to suffer more than they do today?

I think Teco was reacting to the suggestion that we perform wifi-wifi
bridging at a larger scale that is done today.  We'd need to actually try
it out and perform some serious measurements in order to be sure (no, I'm
not volunteering), but I'd expect it to suck, for at least the following
reasons:

1. 802.11 bridging is weird, there are some restrictions on the possible
   topologies (but I don't recall the exact details).

2. I'd expect broadcast/multicast to be fun, especially if the different
   APs are set up to interfere.

3. Things like TRILL aside, bridging performs spanning tree routing, so
   unless you design your topology carefully, you have a good chance of
   pushing all of your traffic through a slow link.  Never mind avoiding
   self-interference.

I've already expressed my opinion (sometimes way too strongly, sorry Ted)
that I'm opposed to reliance on L2 bridging until somebody shows how it
can be made to work with good performance in a hybrid network.  The 802.11s
experience doesn't encourage us to be optimistic.

-- Juliusz


From nobody Fri Feb 27 04:05:01 2015
Return-Path: <jch@pps.univ-paris-diderot.fr>
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 9E1581A9302 for <homenet@ietfa.amsl.com>; Fri, 27 Feb 2015 04:04:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.15
X-Spam-Level: *
X-Spam-Status: No, score=1.15 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_EQ_FR=0.35] autolearn=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 ybyCUzv7NFQl for <homenet@ietfa.amsl.com>; Fri, 27 Feb 2015 04:04:59 -0800 (PST)
Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) (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 9D6CB1A92F9 for <homenet@ietf.org>; Fri, 27 Feb 2015 04:04:58 -0800 (PST)
Received: from potemkin.univ-paris7.fr (potemkin.univ-paris7.fr [IPv6:2001:660:3301:8000::1:1]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/56100) with ESMTP id t1RC4ssp030091 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 27 Feb 2015 13:04:57 +0100
Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by potemkin.univ-paris7.fr (8.14.4/8.14.4/relay2/56228) with ESMTP id t1RC4smP024679; Fri, 27 Feb 2015 13:04:54 +0100
Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id A7CCE2C6C6A; Fri, 27 Feb 2015 13:04:54 +0100 (CET)
X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr
Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id TrSdG8mmqPl0; Fri, 27 Feb 2015 13:04:53 +0100 (CET)
Received: from ijon.pps.univ-paris-diderot.fr (user-109-243-141-10.play-internet.pl [109.243.141.10]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 8EF642C6C6C; Fri, 27 Feb 2015 13:04:51 +0100 (CET)
Date: Fri, 27 Feb 2015 13:04:49 +0100
Message-ID: <87sidrzhjy.wl-jch@pps.univ-paris-diderot.fr>
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Markus Stenberg <markus.stenberg@iki.fi>
In-Reply-To: <9D797DF7-D648-42CD-92D5-71630F9846F5@iki.fi>
References: <8761at9vx5.wl-jch@pps.univ-paris-diderot.fr> <7D8C2976-1649-4349-9E90-E24DD2848086@iki.fi> <874mqcsh98.wl-jch@pps.univ-paris-diderot.fr> <B5B68563-91D5-455C-A3AB-B1B3969302B7@iki.fi> <87r3tedhym.wl-jch@pps.univ-paris-diderot.fr> <9D797DF7-D648-42CD-92D5-71630F9846F5@iki.fi>
User-Agent: Wanderlust/2.15.9
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]); Fri, 27 Feb 2015 13:04:57 +0100 (CET)
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Fri, 27 Feb 2015 13:04:54 +0100 (CET)
X-Miltered: at korolev with ID 54F05D66.001 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-Miltered: at potemkin with ID 54F05D66.000 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)!
X-j-chkmail-Enveloppe: 54F05D66.001 from potemkin.univ-paris7.fr/potemkin.univ-paris7.fr/null/potemkin.univ-paris7.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Enveloppe: 54F05D66.000 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/<jch@pps.univ-paris-diderot.fr>
X-j-chkmail-Score: MSGID : 54F05D66.001 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Score: MSGID : 54F05D66.000 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000
X-j-chkmail-Status: Ham
X-j-chkmail-Status: Ham
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/EJDOjMUNxUy6zs-fe6TLz7xxhp8>
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] DNCP questions
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 27 Feb 2015 12:04:59 -0000

> Yep, intentionally so for now; of course, we could turn it even more in
> the scalable (routing) protocol direction if there is desire.

That's not quite what I meant.  I'll try to put it differently.

Right now, an HNCP node performs the following actions:

1. participate in Trickle-based flooding;
2a. contribute a neighbour TLV to the global state;
2b. optionally contribute other TLVs;
3a. maintain a full set of TLVs being published;
3b. maintain a copy of the topology graph.

Now there are different costs associated to these activities, both for
this node and for other nodes.  (1) is cheap for both.  (2) is cheap for
this node, but expensive for other nodes -- the state being contributed is
replicated in all the other nodes.  (3) is the opposite -- it's expensive
for this node, since it requires storing the whole replicated state, but
doen't contribute anything to other nodes.

Now HNCP doesn't allow participating in just some of those activities.  In
particular, there is no way to participate in flooding without
contributing a neighbour TLV (and hence increasing the size of the
replicated state and the replicated neighbour graph).

When you split HNCP into DNCP, I was hoping that you were providing
a means to have nodes that do (1) and (3a) without contributing to the
replicated global state.  But unless I'm missing something, it doesn't.

-- Juliusz





From nobody Fri Feb 27 04:26:22 2015
Return-Path: <teco@inf-net.nl>
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 A3CA81A6EF4 for <homenet@ietfa.amsl.com>; Fri, 27 Feb 2015 04:26:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 fQdfo0IoKeR2 for <homenet@ietfa.amsl.com>; Fri, 27 Feb 2015 04:26:20 -0800 (PST)
Received: from mail-ie0-f182.google.com (mail-ie0-f182.google.com [209.85.223.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8F0141A0218 for <homenet@ietf.org>; Fri, 27 Feb 2015 04:26:19 -0800 (PST)
Received: by iebtr6 with SMTP id tr6so30095140ieb.7 for <homenet@ietf.org>; Fri, 27 Feb 2015 04:26:18 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=DKzLo+QOKFsTKv6pl9qDAquBTzKEaQspEqOMM5ANIN0=; b=l/ng4Kf5GGHdMMIta0J4BjoTfqPTnP+bSkW4R7ZRorl23tBQECZxbdB6t4tZofkoE8 AhMFQ8ZDENOsBZDs+c1y2otQMbI54eA3EQQmf49L/cX/6h2sdfHBvJDv8xDRyMHgJ0E9 udTJgIxHS7F7+lsUiByud2Iud962AJylA1/3I0eCYUgVnIKMzU/QNYt3CevVtAN1EKS0 76kNMrOHRbdenNC982Pbe4/YqZQMI6tI6MYb6nPpwmKiD5xamjh0TTRbyeiaA/bPm6Rd 7kxe7HiLzPvI38HxVv8haarJes9aI9vYyLIR64n5LK0GVb2SZnw3hFuUUrWtpt3AeVM2 U5Jg==
X-Gm-Message-State: ALoCoQkVsE0F7bHm8v9Z+t6m6cTue7ZYVzzAl4iJYa/Td5Fzi39WzEbPtkaMIXb+q4o/p/Pb6BOs
X-Received: by 10.107.150.149 with SMTP id y143mr17828978iod.22.1425039978554;  Fri, 27 Feb 2015 04:26:18 -0800 (PST)
Received: from [10.10.10.211] (CPE68b6fcfdbd03-CM68b6fcfdbd00.cpe.net.cable.rogers.com. [99.240.94.20]) by mx.google.com with ESMTPSA id 184sm2143080ion.14.2015.02.27.04.26.17 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 27 Feb 2015 04:26:17 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Teco Boot <teco@inf-net.nl>
In-Reply-To: <87twy7ziqs.wl-jch@pps.univ-paris-diderot.fr>
Date: Fri, 27 Feb 2015 13:26:16 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <B510332C-5779-468A-8001-1D9ED4B3E684@inf-net.nl>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <8B98F698-983D-4D2A-B5D1-7ACED27C275E@fugue.com> <alpine.DEB.2.02.1502191920560.4007@uplift.swm.pp.se> <CAPRuP3mpNJTu6mP+RAVKKO0kt60PogNtNbCUCRRqxe9im3EzjA@mail.gmail.com> <alpine.DEB.2.02.1502201042330.4007@uplift.swm.pp.se> <7A86BDC6-FF4B-49FF-B59C-BA1DEF463173@inf-net.nl> <alpine.DEB.2.02.1502201310050.4007@uplift.swm.pp.se> <09793905-8D12-49E0-A040-490F617C87FF@inf-net.nl> <alpine.DEB.2.02.1502201410510.4007@uplift.swm.pp.se> <54EDEEAA.5040302@globis.net> <17359.1424897447@sandelman.ca> <9A5ED36C-D062-4180-AA6D-00346E19A545@townsley.net> <7B49A1E1-9424-4577-B59A-A75509403A2E@inf-net.nl> <CAESTAVvs8AOfCDdhETkdcAO3K_3nj+xgL1m89umszP+E3a1fBw@mail.gmail.com> <87twy7ziqs.wl-jch@pps.univ-paris-diderot.fr>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/-IDbxeFeQMVa4J64MxEHmHFf4II>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, "homenet@ietf.org Group" <homenet@ietf.org>, Mark Townsley <mark@townsley.net>, Ray Hunter <v6ops@globis.net>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 27 Feb 2015 12:26:21 -0000

> Op 27 feb. 2015, om 12:39 heeft Juliusz Chroboczek =
<jch@pps.univ-paris-diderot.fr> het volgende geschreven:
>=20
>>> When performance in dual stack networks with multiple WiFi AP's in =
homes
>>> suffers from homenet protocols, this WG produces dead protocols.
>=20
>> Why would homenet cause wifi APs to suffer more than they do today?
>=20
> I think Teco was reacting to the suggestion that we perform wifi-wifi
> bridging at a larger scale that is done today.

I'm not advocating large layer-2 topologies. I prefer to stay away from =
broadcast storms and other fun. But today's WiFi stack is build on the =
assumption that an SSID equals an IP subnet. WiFi handover is within an =
SSID.=20

My personal goal is to set up a standards based CAT5 + WiFi homenet that =
performs well. I can replace all my switches and wireless routers with =
the monthly budget for cable and mobile connections. But I cannot buy =
something that works, unless I tenfold the budget and buy an enterprise =
solution.

My call is: keep going, let's solve it. If it takes TRILL, CAPWAP, =
CPE/cloud based SDN: so be it. I want to see two- or three-pack high-end =
wired/wireless homenet router kits in the shop that will replace our =
current gear.

Teco


>  We'd need to actually try
> it out and perform some serious measurements in order to be sure (no, =
I'm
> not volunteering), but I'd expect it to suck, for at least the =
following
> reasons:
>=20
> 1. 802.11 bridging is weird, there are some restrictions on the =
possible
>   topologies (but I don't recall the exact details).
>=20
> 2. I'd expect broadcast/multicast to be fun, especially if the =
different
>   APs are set up to interfere.
>=20
> 3. Things like TRILL aside, bridging performs spanning tree routing, =
so
>   unless you design your topology carefully, you have a good chance of
>   pushing all of your traffic through a slow link.  Never mind =
avoiding
>   self-interference.
>=20
> I've already expressed my opinion (sometimes way too strongly, sorry =
Ted)
> that I'm opposed to reliance on L2 bridging until somebody shows how =
it
> can be made to work with good performance in a hybrid network.  The =
802.11s
> experience doesn't encourage us to be optimistic.
>=20
> -- Juliusz


From nobody Fri Feb 27 07:42:00 2015
Return-Path: <mellon@fugue.com>
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 A49A41ACD56 for <homenet@ietfa.amsl.com>; Fri, 27 Feb 2015 07:41:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 5fyub_D2_jvZ for <homenet@ietfa.amsl.com>; Fri, 27 Feb 2015 07:41:57 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 8F80D1ACD4A for <homenet@ietf.org>; Fri, 27 Feb 2015 07:41:57 -0800 (PST)
Received: from [10.0.20.107] (c-71-233-43-215.hsd1.nh.comcast.net [71.233.43.215]) by toccata.fugue.com (Postfix) with ESMTPSA id 7549F23802BB; Fri, 27 Feb 2015 10:41:55 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <B510332C-5779-468A-8001-1D9ED4B3E684@inf-net.nl>
Date: Fri, 27 Feb 2015 10:41:53 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <0FDB6731-24D2-4571-A87C-EEE53EB6201E@fugue.com>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <8B98F698-983D-4D2A-B5D1-7ACED27C275E@fugue.com> <alpine.DEB.2.02.1502191920560.4007@uplift.swm.pp.se> <CAPRuP3mpNJTu6mP+RAVKKO0kt60PogNtNbCUCRRqxe9im3EzjA@mail.gmail.com> <alpine.DEB.2.02.1502201042330.4007@uplift.swm.pp.se> <7A86BDC6-FF4B-49FF-B59C-BA1DEF463173@inf-net.nl> <alpine.DEB.2.02.1502201310050.4007@uplift.swm.pp.se> <09793905-8D12-49E0-A040-490F617C87FF@inf-net.nl> <alpine.DEB.2.02.1502201410510.4007@uplift.swm.pp.se> <54EDEEAA.5040302@globis.net> <17359.142489744 7@sandelman.ca> <9A5ED36C-D062-4180-AA6D-00346E19A545@townsley.net> <7B49A1E1-9424-4577-B59A-A75509403A2E@inf-net.nl> <CAESTAVvs8AOfCDdhETkdcAO3K_3nj+xgL1m89umszP+E3a1fBw@mail.gmail.com> <87twy7ziqs.wl-jch@pps.univ-paris-diderot.fr> <B510332C-5779-468A-8001-1D9ED4B3E684@inf-net.nl>
To: Teco Boot <teco@inf-net.nl>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/tyLdFGUKX0NrcqnMsoaXKx482v4>
Cc: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>, Michael Richardson <mcr+ietf@sandelman.ca>, Mark Townsley <mark@townsley.net>, Ray Hunter <v6ops@globis.net>, "homenet@ietf.org Group" <homenet@ietf.org>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 27 Feb 2015 15:41:59 -0000

On Feb 27, 2015, at 7:26 AM, Teco Boot <teco@inf-net.nl> wrote:
> My call is: keep going, let's solve it. If it takes TRILL, CAPWAP, =
CPE/cloud based SDN: so be it. I want to see two- or three-pack high-end =
wired/wireless homenet router kits in the shop that will replace our =
current gear.

I'd love it if it didn't require that, but in principle I think this is =
an avenue worth exploring.   Maybe we can have a hackathon in Prague... =
:)


From nobody Fri Feb 27 07:53:52 2015
Return-Path: <dave.taht@gmail.com>
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 CF0771ACD56 for <homenet@ietfa.amsl.com>; Fri, 27 Feb 2015 07:53:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.6
X-Spam-Level: 
X-Spam-Status: No, score=-0.6 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 BgkapMRfD5eH for <homenet@ietfa.amsl.com>; Fri, 27 Feb 2015 07:53:46 -0800 (PST)
Received: from mail-oi0-x235.google.com (mail-oi0-x235.google.com [IPv6:2607:f8b0:4003:c06::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3F9371ACD5A for <homenet@ietf.org>; Fri, 27 Feb 2015 07:53:46 -0800 (PST)
Received: by mail-oi0-f53.google.com with SMTP id u20so16179027oif.12 for <homenet@ietf.org>; Fri, 27 Feb 2015 07:53:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=qqWf7HsZoPuhwmNNuVp+roy2XrdYe/ldgrQiLchqxwo=; b=aza1as18t7jUKh9HJ+yGePILz6izT9IanncshkzDgBJogxk1O6ges2PRicAi9KlKkJ HTsV+Q/HQpKT384cNobnnPJjMjpjXi+j30i/kJncuxhk9/GGWeTIQa16Z2vWKgothsz+ SRDJrtfQpzzD6Y3S+txpqZo3dOpWBektQZ9fQsmASCXieHSP0tgbn337IeiS1vftNCtc TeEQKDJCxdM9+WK/gyvFkDMKqyplpAKK5Iod4uwFvdZ/T2nscK13u5871RV60SCL+i2C lfhkjeyLjwwsBNrQZbHSC6NYaXnGLJ8JjI/FPB/aeCudlKKuLlS8jeb0PtsQmYxC9HPn 3yIQ==
MIME-Version: 1.0
X-Received: by 10.182.230.132 with SMTP id sy4mr10541217obc.29.1425052425516;  Fri, 27 Feb 2015 07:53:45 -0800 (PST)
Received: by 10.202.51.66 with HTTP; Fri, 27 Feb 2015 07:53:45 -0800 (PST)
In-Reply-To: <B510332C-5779-468A-8001-1D9ED4B3E684@inf-net.nl>
References: <CAESTAVuqmqSqzkW6HFARbB1LiVcXFqkdkfrPUCHQ35vrMb4pbg@mail.gmail.com> <CAA93jw5swUnVW245rmcVH+RJh7WTWepOsP_u2oGV39a6oVcrDw@mail.gmail.com> <alpine.DEB.2.02.1502190820380.4007@uplift.swm.pp.se> <871tllhq2u.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1502191639010.4007@uplift.swm.pp.se> <3E7E9C84-7EC3-4343-AC87-31D03A67ED79@fugue.com> <alpine.DEB.2.02.1502191804380.4007@uplift.swm.pp.se> <EA65B4B3-01D1-4332-BF55-0FEB1DCD0C31@fugue.com> <alpine.DEB.2.02.1502191905490.4007@uplift.swm.pp.se> <8B98F698-983D-4D2A-B5D1-7ACED27C275E@fugue.com> <alpine.DEB.2.02.1502191920560.4007@uplift.swm.pp.se> <CAPRuP3mpNJTu6mP+RAVKKO0kt60PogNtNbCUCRRqxe9im3EzjA@mail.gmail.com> <alpine.DEB.2.02.1502201042330.4007@uplift.swm.pp.se> <7A86BDC6-FF4B-49FF-B59C-BA1DEF463173@inf-net.nl> <alpine.DEB.2.02.1502201310050.4007@uplift.swm.pp.se> <09793905-8D12-49E0-A040-490F617C87FF@inf-net.nl> <alpine.DEB.2.02.1502201410510.4007@uplift.swm.pp.se> <54EDEEAA.5040302@globis.net> <17359.1424897447@sandelman.ca> <9A5ED36C-D062-4180-AA6D-00346E19A545@townsley.net> <7B49A1E1-9424-4577-B59A-A75509403A2E@inf-net.nl> <CAESTAVvs8AOfCDdhETkdcAO3K_3nj+xgL1m89umszP+E3a1fBw@mail.gmail.com> <87twy7ziqs.wl-jch@pps.univ-paris-diderot.fr> <B510332C-5779-468A-8001-1D9ED4B3E684@inf-net.nl>
Date: Fri, 27 Feb 2015 07:53:45 -0800
Message-ID: <CAA93jw5+ycfx03oX7GFsF8kZYKkQyZ3TRw8v+onuSD2v=aBG0A@mail.gmail.com>
From: Dave Taht <dave.taht@gmail.com>
To: Teco Boot <teco@inf-net.nl>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/Rg6Bo5ubtQ_9m0ZMjphGFCn01HI>
Cc: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>, Michael Richardson <mcr+ietf@sandelman.ca>, Mark Townsley <mark@townsley.net>, Ray Hunter <v6ops@globis.net>, "homenet@ietf.org Group" <homenet@ietf.org>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 27 Feb 2015 15:53:51 -0000

I am glad, incidentally, that for the first time, this wg is
considering some of the problems wifi has, and growing towards
understanding them in more detail. I have long been working on finding
answers to these deep, underlying problems - after first identifying
some the major ones:

https://www.youtube.com/watch?v=Wksh2DPHCDI&feature=youtu.be

and proposing some solutions to the IEEE that still worked inside the
standard (well, obsoleting part of 802.11e entirely)

http://snapon.lab.bufferbloat.net/~d/ieee802.11-sept-17-2014/11-14-1265-00-0wng-More-on-Bufferbloat.pdf

and also proposing some deep changes for 802.11ax (the successor to ac).

Work on getting some of that stuff done is proceeding - unfunded, by
volunteers that care, in their spare time...

(one major set of needed patches: "minstrel-blues" - coupled power and
rate control - is out for review on the linux-wireless mailing list
and it could used an acked-by because it is great and desperately
needed. You don't need to transmit at the highest possible rate when
you are right next to the AP, and vice versa)

Finally, a few weeks ago, I convinced a major wifi testing house to
actually start poking at one subset of the problem, which is multiple
stations attempting to transmit at the same time. This test uses a
single TCP flow each, 1 up, 1 down, and measures the latency.

http://www.candelatech.com/downloads/rtt_fair4be-comparison-box-plot.png

This is on the latest and "best" 802.11ac hardware on the retail
market, transmitting at the highest possible rate, to 4 stations,
under lab conditions. Under load, you presently observe latencies of
50-1000ms, and jitter, same. They only achieved ~ 1/3 the rate of the
base mac capability.

They haven't tried lower rates, or added interference, nor mixed in
multicast, nor tried WDS, or 802.11s, or added stations - any one of
which can mess things up by another order or two or *more* of
magnitude, I am awaiting further results from them, testing lower
rates in particular. But I do hope that they eventually manage to
duplicate the kinds of results I have obtained all over the world in
conference centers, hotels, and apartment buildings, where the typical
latencies I observe can be in the 3-6 second range, and bandwidth,
below a few dozen k, at best.

This sort of result should be concerning to the people that would like
to bridge everything, use range extenders, transmit any multicast at
all (and add in new forms of multicast, like nd/hnetd/babel/etc), or
have hope that wifi can continue to work at all - in the face of
adding lots and lots more (IoT) wifi clients - without some major work
on how our APs and client chipsets work at a deep level.

And thus, this is why I am not paying a whole lot of attention to the
ietf anymore, and sinking more of my energies into finding ways to
preserve and repair one of the coolest, most free-ing internet
technologies that has has ever existed. And it is also sort of why I
am running ethernet or homeplugs everywhere I must.


From nobody Fri Feb 27 13:40:54 2015
Return-Path: <curtis@ipv6.occnc.com>
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 070571A0334 for <homenet@ietfa.amsl.com>; Fri, 27 Feb 2015 13:40:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.912
X-Spam-Level: 
X-Spam-Status: No, score=-1.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, 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 eyNDlfIb3fmM for <homenet@ietfa.amsl.com>; Fri, 27 Feb 2015 13:40:50 -0800 (PST)
Received: from maildrop31.somerville.occnc.com (maildrop31.somerville.occnc.com [IPv6:2001:550:3800:203::3131]) (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 64BB11A0273 for <homenet@ietf.org>; Fri, 27 Feb 2015 13:40:50 -0800 (PST)
Received: from harbor31.somerville.occnc.com (harbor31.somerville.occnc.com [IPv6:2001:550:3800:203::3231]) (authenticated bits=128) by maildrop31.somerville.occnc.com (8.14.9/8.14.9) with ESMTP id t1RLbt3Q020210; Fri, 27 Feb 2015 16:37:55 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201502272137.t1RLbt3Q020210@maildrop31.somerville.occnc.com>
To: Henning Rogge <hrogge@gmail.com>
From: Curtis Villamizar <curtis@ipv6.occnc.com>
In-reply-to: Your message of "Wed, 25 Feb 2015 21:46:48 +0100." <CAGnRvupwF3N9JQmi_TxWBXkEtO_59ZDQqAPCFcSyFDUVQP8EBw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <20208.1425073075.1@harbor31.somerville.occnc.com>
Content-Transfer-Encoding: quoted-printable
Date: Fri, 27 Feb 2015 16:37:55 -0500
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/4hFFZcVZaDNwn8R7NtE70tuuzks>
Cc: Toerless Eckert <eckert@cisco.com>, "homenet@ietf.org Group" <homenet@ietf.org>, curtis@ipv6.occnc.com
Subject: Re: [homenet] L2 link status [was: More about marginal links]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.com
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 27 Feb 2015 21:40:53 -0000

In message <CAGnRvupwF3N9JQmi_TxWBXkEtO_59ZDQqAPCFcSyFDUVQP8EBw@mail.gmail=
.com>
Henning Rogge writes:
 =

> On Wed, Feb 25, 2015 at 9:36 PM, Curtis Villamizar
> <curtis@ipv6.occnc.com> wrote:
> > In message <87a903ef2j.wl-jch@pps.univ-paris-diderot.fr>
> > Juliusz Chroboczek writes:
> >> As to wireless links -- as far as I'm aware, making efficient use of
> >> wireless L2 information in a routing protocol is an open research pro=
blem.
> >
> > Other than signal strength and collision rate, what L2 information is
> > available?  Per MAC information would be nice for the AP side or any
> > node in mesh or adhoc mode but that isn't collected anywhere AFAIK.
>  =

> Raw linkspeed and (on Linux) even Throughput to each neighbor... and a l=
ot more.
>  =

> Just run "iw wlan0 station dump" on a Linux system with wifi and you
> will be surprised how much information you will get.
>  =

> Henning Rogge


Henning,

How can a router make use of throughput to a mostly idle neighbor?
How do you get packets sent to a neighbor that dropped or packets that
a neighbor sent to you that didn't arrive here?  Raw link speed or
packet and byte counts don't by themselves tell you much.  The
equivalent of PPP LQM or MPLS-TP LM OAM would be the sort of thing
needed is you didn't want to use BFD with a high probe rate.

As I said above (or tried to say), the most useful hints that the link
isn't as good as nominal link speed might indicate might be signal
strength and collision rate.  [What I meant above by "available" was
available and useful for "making efficient use of wireless L2
information in a routing protocol" in the quoted text.  So maybe I was
too terse in saying that.]

Thanks for the response though.  I use FreeBSD and other than rate and
S/N there isn't much, so could you send me sample output from a Linux
host or better yet a Linux AP with a few "neighbors".  We can take
this off list and discuss the sample output but so far "lots of stuff"
(sic) doesn't help.

Curtis


ps - maybe I should stop procrastinating and compile and flash openwrt
and see for myself, but for now ...


From nobody Fri Feb 27 13:51:56 2015
Return-Path: <markus.stenberg@iki.fi>
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 E26791A034C for <homenet@ietfa.amsl.com>; Fri, 27 Feb 2015 13:51:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.121
X-Spam-Level: 
X-Spam-Status: No, score=-1.121 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_NEUTRAL=0.779] autolearn=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 ERu4hOe8Vygl for <homenet@ietfa.amsl.com>; Fri, 27 Feb 2015 13:51:52 -0800 (PST)
Received: from kirsi1.inet.fi (mta-out1.inet.fi [62.71.2.227]) by ietfa.amsl.com (Postfix) with ESMTP id 55F8A1A014A for <homenet@ietf.org>; Fri, 27 Feb 2015 13:51:52 -0800 (PST)
Received: from poro.lan (80.220.64.126) by kirsi1.inet.fi (8.5.142.08) (authenticated as stenma-47) id 54E3C711014EC556; Fri, 27 Feb 2015 23:51:27 +0200
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\))
From: Markus Stenberg <markus.stenberg@iki.fi>
In-Reply-To: <201502272137.t1RLbt3Q020210@maildrop31.somerville.occnc.com>
Date: Fri, 27 Feb 2015 23:51:22 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <1A58AAC9-A145-4B8C-8426-712EBE2A5034@iki.fi>
References: <201502272137.t1RLbt3Q020210@maildrop31.somerville.occnc.com>
To: curtis@ipv6.occnc.com
X-Mailer: Apple Mail (2.2070.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/EipFyWc14k7PE33bKLy6MqqF--E>
Cc: Henning Rogge <hrogge@gmail.com>, Toerless Eckert <eckert@cisco.com>, Markus Stenberg <markus.stenberg@iki.fi>, "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] L2 link status [was: More about marginal links]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 27 Feb 2015 21:51:55 -0000

On 27.2.2015, at 23.37, Curtis Villamizar <curtis@ipv6.occnc.com> wrote:
> Thanks for the response though.  I use FreeBSD and other than rate and
> S/N there isn't much, so could you send me sample output from a Linux
> host or better yet a Linux AP with a few "neighbors".  We can take
> this off list and discuss the sample output but so far "lots of stuff"
> (sic) doesn=E2=80=99t help.

Random example output of one.. ;) (I rather not spam the list)

# iw dev wlan1 station dump
Station <mac> (on wlan1)
	inactive time:	1090 ms
	rx bytes:	13841464
	rx packets:	99054
	tx bytes:	65086103
	tx packets:	90179
	tx retries:	1023
	tx failed:	0
	signal:  	-59 [-66, -64] dBm
	signal avg:	-58 [-64, -61] dBm
	tx bitrate:	300.0 MBit/s MCS 15 40MHz short GI
	rx bitrate:	24.0 MBit/s
<snip> irrelevant parts (various flags on/off)
#

I see both tx failed and retries nonzero on some nodes, and for all, =
signal strength, and tx/rx bitrates. I guess all of this could be used =
for _something_ at least..=20

-Markus=


From nobody Fri Feb 27 14:01:52 2015
Return-Path: <curtis@ipv6.occnc.com>
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 399E61A0372 for <homenet@ietfa.amsl.com>; Fri, 27 Feb 2015 14:01:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.912
X-Spam-Level: 
X-Spam-Status: No, score=-1.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, 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 c6pJVO3PYmgr for <homenet@ietfa.amsl.com>; Fri, 27 Feb 2015 14:01:48 -0800 (PST)
Received: from maildrop31.somerville.occnc.com (maildrop31.somerville.occnc.com [IPv6:2001:550:3800:203::3131]) (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 9603D1A014A for <homenet@ietf.org>; Fri, 27 Feb 2015 14:01:48 -0800 (PST)
Received: from harbor31.somerville.occnc.com (harbor31.somerville.occnc.com [IPv6:2001:550:3800:203::3231]) (authenticated bits=128) by maildrop31.somerville.occnc.com (8.14.9/8.14.9) with ESMTP id t1RM0Aru020484; Fri, 27 Feb 2015 17:00:10 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201502272200.t1RM0Aru020484@maildrop31.somerville.occnc.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
From: Curtis Villamizar <curtis@ipv6.occnc.com>
In-reply-to: Your message of "Thu, 26 Feb 2015 08:42:06 +1300." <54EE258E.8060302@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <20482.1425074410.1@harbor31.somerville.occnc.com>
Content-Transfer-Encoding: quoted-printable
Date: Fri, 27 Feb 2015 17:00:10 -0500
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/c0Y1pxVKdk5kCFywSmfFIsLJ4bc>
Cc: Ray Hunter <v6ops@globis.net>, "homenet@ietf.org Group" <homenet@ietf.org>, Teco Boot <teco@inf-net.nl>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.com
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 27 Feb 2015 22:01:50 -0000

In message <54EE258E.8060302@gmail.com>
Brian E Carpenter writes:
 =

> On 26/02/2015 05:14, Mikael Abrahamsson wrote:
> > On Wed, 25 Feb 2015, Ray Hunter wrote:
> > =

> >> That way the devices can roam at L3, without all of the nasty side ef=
fects of re-establishing TPC sessions, or updating
> >> dynamic naming services, or having to run an L2 overlay network every=
where, or having to support protocols that require a
> >> specialised partner in crime on the server side (mTCP, shim6 et al).
> > =

> > It's my firm belief that we need to rid clients of IP address dependen=
ce for its sessions. Asking clients to participate in HNCP
> > only addresses the problem where HNCP is used.
> > =

> > Fixing this for real would reap benefits for devices moving between an=
y kind of network, multiple providers, mobile/fixed etc.
>  =

> Violent agreement. This is not a homenet problem; it's an IP problem.
> In fact, it's exactly why IP addresses are considered harmful in
> some quarters. Trying to fix it just for homenet seems pointless.
> http://www.sigcomm.org/ccr/papers/2014/April/0000000.0000008
>  =

>    Brian


Brian,

Seriously - your paper may be overstating the problem.  At least if we
discount IPv4 and in doing so eliminate NAT we solve a lot of problems
that never should have existed in the first place.  If we carry NAT
over to IPV6, then shame on us.

If we get rid of NAT a big part of the problem just goes away.  No
alternate spaces, kludgy rendezvous mechanisms, etc.  Using an address
on the loopback gets rid of the multiple interface problem and where
it really matters (ISP router and ISP or DS server reachability) this
has been done with configuration for two decades.  The multihoming
failover or roaming are a bit more difficult but things MPTCP is
supposed to address.

Curtis


From nobody Fri Feb 27 14:28:54 2015
Return-Path: <dave.taht@gmail.com>
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 AAF391A0AF7 for <homenet@ietfa.amsl.com>; Fri, 27 Feb 2015 14:28:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 bNI2Tor_QUmW for <homenet@ietfa.amsl.com>; Fri, 27 Feb 2015 14:28:52 -0800 (PST)
Received: from mail-oi0-x236.google.com (mail-oi0-x236.google.com [IPv6:2607:f8b0:4003:c06::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DBFE11A03A1 for <homenet@ietf.org>; Fri, 27 Feb 2015 14:28:39 -0800 (PST)
Received: by mail-oi0-f54.google.com with SMTP id v63so18104198oia.13 for <homenet@ietf.org>; Fri, 27 Feb 2015 14:28:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=2IG2aBVd27k9H+04txXwNyMM/mKy3z2XMFDzZ3GJ7ik=; b=ydnrpwySe5XWkBwX0P+HPXCbFukc2lbFXvvBToknoOf7x3kAajRT2w849SMoOtogHd 70V57HADxa4U9QR3W+7hg3VRDVkgz5PIJq1fhv15O0o0moKerAdhxJlFOC4r4s1L5/Za 0MS+Tq9hxhcoFdj5Oatc7aKkABSBgZt/naC7h5Agb/yifZQ4ODJ5zJ7MicoBLgpJz7Dq NOVtQR48CeBLDWTV6evc4DRI1PgMzBLd18oz8tyaNA5bY1JOnBTAm5OKtQrg50M7e/V1 IZRdnUYOlL9Yop9IHP33gjhvEBCB67J9A3SpRZ2jIFv74Pk7fvlgEYdgI0U+sh+LwXnj PvuQ==
MIME-Version: 1.0
X-Received: by 10.182.1.202 with SMTP id 10mr11590397obo.56.1425076119198; Fri, 27 Feb 2015 14:28:39 -0800 (PST)
Received: by 10.202.51.66 with HTTP; Fri, 27 Feb 2015 14:28:38 -0800 (PST)
In-Reply-To: <201502272200.t1RM0Aru020484@maildrop31.somerville.occnc.com>
References: <54EE258E.8060302@gmail.com> <201502272200.t1RM0Aru020484@maildrop31.somerville.occnc.com>
Date: Fri, 27 Feb 2015 14:28:38 -0800
Message-ID: <CAA93jw4tuMfM_LvZKRX7aRk2Z+HWTw5jBOENpvfEJuT4L9TcUQ@mail.gmail.com>
From: Dave Taht <dave.taht@gmail.com>
To: "<curtis@ipv6.occnc.com>" <curtis@ipv6.occnc.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/sqbzJyewNojl2g_aAeCXHRtVdk8>
Cc: Ray Hunter <v6ops@globis.net>, "homenet@ietf.org Group" <homenet@ietf.org>, Teco Boot <teco@inf-net.nl>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 27 Feb 2015 22:28:53 -0000

On Fri, Feb 27, 2015 at 2:00 PM, Curtis Villamizar
<curtis@ipv6.occnc.com> wrote:
> In message <54EE258E.8060302@gmail.com>
> Brian E Carpenter writes:
>
>> On 26/02/2015 05:14, Mikael Abrahamsson wrote:
>> > On Wed, 25 Feb 2015, Ray Hunter wrote:
>> >
>> >> That way the devices can roam at L3, without all of the nasty side ef=
fects of re-establishing TPC sessions, or updating
>> >> dynamic naming services, or having to run an L2 overlay network every=
where, or having to support protocols that require a
>> >> specialised partner in crime on the server side (mTCP, shim6 et al).
>> >
>> > It's my firm belief that we need to rid clients of IP address dependen=
ce for its sessions. Asking clients to participate in HNCP
>> > only addresses the problem where HNCP is used.
>> >
>> > Fixing this for real would reap benefits for devices moving between an=
y kind of network, multiple providers, mobile/fixed etc.
>>
>> Violent agreement. This is not a homenet problem; it's an IP problem.
>> In fact, it's exactly why IP addresses are considered harmful in
>> some quarters. Trying to fix it just for homenet seems pointless.
>> http://www.sigcomm.org/ccr/papers/2014/April/0000000.0000008
>>
>>    Brian
>
>
> Brian,
>
> Seriously - your paper may be overstating the problem.  At least if we
> discount IPv4 and in doing so eliminate NAT we solve a lot of problems
> that never should have existed in the first place.  If we carry NAT
> over to IPV6, then shame on us.

I am sorry, I no longer share this opinion. The pains of renumbering
someones entire home network every time the ISP feels like it, given
the enormous number of devices I have encountered that don't handle it
well, are just too much to bear.

The next version of cerowrt will do translation from the external IPv6
address range to a static internal one (or ones, in the case of
multiple egress gateways), and lacking a standard for such will use
fcxx/8 addressing. I will make it be an option for people to turn off,
but I've had it with being renumbered.

I am sure this will break stuff, and I don't know what all it will do,
and I intend to find out.

Until some far off day where we have stable name to ipv6 address
mapping, and vice versa, it is otherwise impossible to have useful
ipv6 based services inside the home or small business.

>
> If we get rid of NAT a big part of the problem just goes away.  No
> alternate spaces, kludgy rendezvous mechanisms, etc.  Using an address
> on the loopback gets rid of the multiple interface problem and where
> it really matters (ISP router and ISP or DS server reachability) this
> has been done with configuration for two decades.  The multihoming
> failover or roaming are a bit more difficult but things MPTCP is
> supposed to address.
>
> Curtis
>
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet



--=20
Dave T=C3=A4ht
Let's make wifi fast, less jittery and reliable again!

https://plus.google.com/u/0/107942175615993706558/posts/TVX3o84jjmb


From nobody Fri Feb 27 16:26:51 2015
Return-Path: <dave.taht@gmail.com>
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 A82EB1A1A77 for <homenet@ietfa.amsl.com>; Fri, 27 Feb 2015 16:26:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 g-5ZUm3cCcUC for <homenet@ietfa.amsl.com>; Fri, 27 Feb 2015 16:26:48 -0800 (PST)
Received: from mail-oi0-x22c.google.com (mail-oi0-x22c.google.com [IPv6:2607:f8b0:4003:c06::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 67CC21A1A6E for <homenet@ietf.org>; Fri, 27 Feb 2015 16:26:48 -0800 (PST)
Received: by mail-oi0-f44.google.com with SMTP id a3so18538198oib.3 for <homenet@ietf.org>; Fri, 27 Feb 2015 16:26:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=J/CCuFG1duqBi1o5ielbAsT4NrsOMQgvVWKGdXO39LM=; b=IEjKdY7KhUYDZLqcn2R9TeCj8Bi0yCHnxz+xjdfTjeqaazla4WfrDvDd6CBBO3G+BJ dM/dVPC+K3056LuUZR3MhMFoXyPIRRzPPwQ5UST7+VM6Mse1PPT2JfoXNyqdwW9mFb1L ExWBfD85XdipQ92kzNqhXCBhfvnyuuvk2CROna5C4vQXNxTxMgt/F7ddWM2YCFnFA3a7 I+S8ON1xiFK9OrNQtpGovfxl3/qy+8581UviRa2gTx8gsAFjzsWDBOWeCjepWnpDamSV BvMTX4kQPRY4hU16Tgx7EbWORQxjznX8BQ5oa2yCcQNTfjJwy84p/FFASKW/ndF6hzYH hfvQ==
MIME-Version: 1.0
X-Received: by 10.60.79.10 with SMTP id f10mr10680153oex.8.1425083207711; Fri, 27 Feb 2015 16:26:47 -0800 (PST)
Received: by 10.202.51.66 with HTTP; Fri, 27 Feb 2015 16:26:47 -0800 (PST)
In-Reply-To: <201502252036.t1PKaTq1086409@maildrop31.somerville.occnc.com>
References: <87a903ef2j.wl-jch@pps.univ-paris-diderot.fr> <201502252036.t1PKaTq1086409@maildrop31.somerville.occnc.com>
Date: Fri, 27 Feb 2015 16:26:47 -0800
Message-ID: <CAA93jw627Q12XkZy3CFuV81CLbJc5D9oX6LK1=cgetWsOP1B3g@mail.gmail.com>
From: Dave Taht <dave.taht@gmail.com>
To: "<curtis@ipv6.occnc.com>" <curtis@ipv6.occnc.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/Yzcf596gxqgGvskdMuYY49w0jYY>
Cc: Toerless Eckert <eckert@cisco.com>, "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] L2 link status [was: More about marginal links]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sat, 28 Feb 2015 00:26:50 -0000

On Wed, Feb 25, 2015 at 12:36 PM, Curtis Villamizar
<curtis@ipv6.occnc.com> wrote:
>
> In message <87a903ef2j.wl-jch@pps.univ-paris-diderot.fr>
> Juliusz Chroboczek writes:
>>
>> > Thought: In general, my feeling is that L2 link status is widely relie=
d
>> > upon in commercial product/dpeloyments. If homenet feels it can not re=
ly
>> > on it due to the non-commercial nature of its development platforms,
>> > thats an interesting aspect, especially because it could impact an IET=
F
>> > standard that we'd like to see commercially implemented and then the
>> > constraints could be different...
>>
>> Are you referring to the routing protocol comparison, or to something el=
se?
>>
>> I have the impression that Babel and IS-IS behave essentially the same
>> wrt. L2 status -- they both converge fast enough after link status has
>> been established, and they essentially provide the same facilities for
>> application-layer link sensing (IMHO Babel's Hello/IHU subprotocol is
>> slightly more flexible, but that's probably not a big deal).
>>
>> As to wireless links -- as far as I'm aware, making efficient use of
>> wireless L2 information in a routing protocol is an open research proble=
m.
>
> Other than signal strength and collision rate, what L2 information is
> available?  Per MAC information would be nice for the AP side or any
> node in mesh or adhoc mode but that isn't collected anywhere AFAIK.
>
>> -- Juliusz
>>
>> _______________________________________________
>> homenet mailing list
>> homenet@ietf.org
>> https://www.ietf.org/mailman/listinfo/homenet
>
>
> ISPs mostly use Ethernet as point-to-point (PTP) links.  Including
> using 100GbE as PTP.  No switches.  L2 Link down is one fast indicator
> of link down.  But for Ethernet over transport gear (ie: OTN) BFD is
> almost always used.  For short distances L2 over extended reach optics
> can be used, including colored optics and WDM.  This is also PTP and
> in this case BFD should not be needed.  To the extent that routers use
> SONET or OTN interfaces, these have fast L2 link down indication and
> are integrated with L3 link down detection.  In all of these detection
> is on the order of 10 msec (geographic distance dependent), failover
> using FRR is under 50 msec, and IGP convergence is well under a second
> (typical 100-200 msec today AFAIK).  L3 hellos are way too slow.
>
> BFD is not heavy weight.  L3 hellos (OSPF, ISIS) can be set down to 1s
> with detection in 3s (too slow).
>
> BFD, Hellos, or any form of probe traffic over wireless has the speed
> of detection vs overhead issue.  At nominal 10 Mb/s (low end today for
> wireless) a small probe would take about 0.1 msec (for example, 125
> bytes including all overhead is about 1000 bits).  Not bad if running
> 100 probes/sec (30 msec detection) unless there are a very large
> number of stations using the AP and doing the same thing.  In that

You are thinking about it wrong. Wireless-g is only capable of roughly
1300 TXOPs total per second. Bandwidth has NOTHING to do with it.

I don't have the figure in my head for n or ac, but it is not a lot, and
in the presence of g, falls back to the above figure.

losing 10% of the bandwidth - per station - to run BFD is not an option.

> case 10 probes per second might be better.  A very high collision rate

Still too much. Next question?

> (typically not due to probes, but to real traffic) might result in a
> link down indication.  If that is the case, then moving to another AP
> would be a good thing.
>
> Flapping needs to be avoided if an alternate is available (ie: with
> 20% loss, in .2*.2*.2 =3D .008 =3D 0.8% of intervale a down indication
> would occur).  If any packet received would bring it back up, then at
> 100 probes / sec, a change in IGP link state could occur about once a
> second on average.  Remembering a link down and holding a down state
> for a (longish) while would be a good thing.  If there is no alternate
> route, not probing at all and/or holding an up state would be good.
> OTOH- 20% loss borders on completely unusable.
>
> Curtis
>
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet



--=20
Dave T=C3=A4ht
Let's make wifi fast, less jittery and reliable again!

https://plus.google.com/u/0/107942175615993706558/posts/TVX3o84jjmb


From nobody Fri Feb 27 16:28:52 2015
Return-Path: <dave.taht@gmail.com>
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 50EC21A1A78 for <homenet@ietfa.amsl.com>; Fri, 27 Feb 2015 16:28:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 f9V0vS0SY9Ty for <homenet@ietfa.amsl.com>; Fri, 27 Feb 2015 16:28:49 -0800 (PST)
Received: from mail-oi0-x231.google.com (mail-oi0-x231.google.com [IPv6:2607:f8b0:4003:c06::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8210D1A1A6E for <homenet@ietf.org>; Fri, 27 Feb 2015 16:28:49 -0800 (PST)
Received: by mail-oi0-f49.google.com with SMTP id v63so18486013oia.8 for <homenet@ietf.org>; Fri, 27 Feb 2015 16:28:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=uWU5F/a/WzTLcTHZE9Snu1qhMlDTwzjXwB/zXjfDwvw=; b=olXQmtTGN29MdWnVjCkftbXFga8jFWw9jJqdtoRfwEhBTYZBgkzl9O2BtSxUCnwCeM cgyqcr/ezOPO8zTbhhIEO1hqKWT/5AJrx5BUTEFooNJsCwHO3zQFBzPf/rnKXW0Ufmyy bhoORvbg64xvtu2at3cYR2jx9of1nDYyFi4mdXWvBaYt8QwbHkpyumLol61CYleTBZXB fgMm7dJTucQj8O6/hVJD1IR3QPSNTEJ/TIEH5QhU/fo5a9LO5PRkEsA7SBipBx7l9Oxn TVg3tg+/xiXgdBAa54VnHvUZRMP8ILzdi0qbzWvaorQpS5FT5RI//pdFlxnitPfbgsZ3 Hmrg==
MIME-Version: 1.0
X-Received: by 10.60.47.42 with SMTP id a10mr11885672oen.75.1425083328804; Fri, 27 Feb 2015 16:28:48 -0800 (PST)
Received: by 10.202.51.66 with HTTP; Fri, 27 Feb 2015 16:28:48 -0800 (PST)
In-Reply-To: <201502272137.t1RLbt3Q020210@maildrop31.somerville.occnc.com>
References: <CAGnRvupwF3N9JQmi_TxWBXkEtO_59ZDQqAPCFcSyFDUVQP8EBw@mail.gmail.com> <201502272137.t1RLbt3Q020210@maildrop31.somerville.occnc.com>
Date: Fri, 27 Feb 2015 16:28:48 -0800
Message-ID: <CAA93jw7yYJ4OUagSEd-dn4TTvKuWucyLOQdsqXPHO4aF+3hVsA@mail.gmail.com>
From: Dave Taht <dave.taht@gmail.com>
To: "<curtis@ipv6.occnc.com>" <curtis@ipv6.occnc.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/FQJBaHTYH3fUeE3XWYBbETotGW4>
Cc: Toerless Eckert <eckert@cisco.com>, Henning Rogge <hrogge@gmail.com>, "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] L2 link status [was: More about marginal links]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sat, 28 Feb 2015 00:28:51 -0000

On Fri, Feb 27, 2015 at 1:37 PM, Curtis Villamizar
<curtis@ipv6.occnc.com> wrote:
> In message <CAGnRvupwF3N9JQmi_TxWBXkEtO_59ZDQqAPCFcSyFDUVQP8EBw@mail.gmai=
l.com>
> Henning Rogge writes:
>
>> On Wed, Feb 25, 2015 at 9:36 PM, Curtis Villamizar
>> <curtis@ipv6.occnc.com> wrote:
>> > In message <87a903ef2j.wl-jch@pps.univ-paris-diderot.fr>
>> > Juliusz Chroboczek writes:
>> >> As to wireless links -- as far as I'm aware, making efficient use of
>> >> wireless L2 information in a routing protocol is an open research pro=
blem.
>> >
>> > Other than signal strength and collision rate, what L2 information is
>> > available?  Per MAC information would be nice for the AP side or any
>> > node in mesh or adhoc mode but that isn't collected anywhere AFAIK.
>>
>> Raw linkspeed and (on Linux) even Throughput to each neighbor... and a l=
ot more.
>>
>> Just run "iw wlan0 station dump" on a Linux system with wifi and you
>> will be surprised how much information you will get.
>>
>> Henning Rogge
>
>
> Henning,
>
> How can a router make use of throughput to a mostly idle neighbor?
> How do you get packets sent to a neighbor that dropped or packets that
> a neighbor sent to you that didn't arrive here?  Raw link speed or
> packet and byte counts don't by themselves tell you much.  The
> equivalent of PPP LQM or MPLS-TP LM OAM would be the sort of thing
> needed is you didn't want to use BFD with a high probe rate.
>
> As I said above (or tried to say), the most useful hints that the link
> isn't as good as nominal link speed might indicate might be signal
> strength and collision rate.  [What I meant above by "available" was
> available and useful for "making efficient use of wireless L2
> information in a routing protocol" in the quoted text.  So maybe I was
> too terse in saying that.]
>
> Thanks for the response though.  I use FreeBSD and other than rate and
> S/N there isn't much, so could you send me sample output from a Linux
> host or better yet a Linux AP with a few "neighbors".  We can take
> this off list and discuss the sample output but so far "lots of stuff"
> (sic) doesn't help.
>
> Curtis
>
>
> ps - maybe I should stop procrastinating and compile and flash openwrt
> and see for myself, but for now ...

You don't have to compile a thing, just download the right nightly
from chaos calmer (preferred as hnetd etc are in it), and flash it.

Everyone here, has been 90 bucks, 5 minutes and one reflash away from
eating it's dogfood for 9+ months now.

http://downloads.openwrt.org/snapshots/trunk/




> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet



--=20
Dave T=C3=A4ht
Let's make wifi fast, less jittery and reliable again!

https://plus.google.com/u/0/107942175615993706558/posts/TVX3o84jjmb


From nobody Fri Feb 27 16:56:49 2015
Return-Path: <dave.taht@gmail.com>
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 B4FEB1A1A83 for <homenet@ietfa.amsl.com>; Fri, 27 Feb 2015 16:56:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 MNWTbKc6eDCH for <homenet@ietfa.amsl.com>; Fri, 27 Feb 2015 16:56:46 -0800 (PST)
Received: from mail-ob0-x22b.google.com (mail-ob0-x22b.google.com [IPv6:2607:f8b0:4003:c01::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E21561A1ADF for <homenet@ietf.org>; Fri, 27 Feb 2015 16:56:45 -0800 (PST)
Received: by mail-ob0-f171.google.com with SMTP id gq1so21913315obb.2 for <homenet@ietf.org>; Fri, 27 Feb 2015 16:56:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=LEZb9tmFqm6cXoN9CAeTBALFSbR0KO14/reTFa89D6w=; b=Sc3xkV7T5k5sXoWkW6qUZHrgAo8uoLB2jOQmD80Dtu0//0neHshbn6XbZs/Ku1TR74 /JhUI75xbN2do1EX1Po/SPaRvQZ/tGk+BXHel5b9bZG8fhd5L37KBlpi5bv7RyWkK99l U75AKHm1hl7QwNbRUg23zD2siCMZTa/tycBE6XthplHeeoQozPMtwU0MVJd1Opn4ZTYA 6N/wWXF2zSoZQjWH9ud3QThrjnGTv85+5hhCud3Eyu1a5FQzJYlKhYMOhAlU0zi83vJZ IJVaEjYZJPRDS+Tc03cgOOuT8/T5ATbLTFfEtJkD/0IxjnN2RLA9vuo3UDgMIktTFxMj kNFg==
MIME-Version: 1.0
X-Received: by 10.60.47.42 with SMTP id a10mr11939641oen.75.1425085005150; Fri, 27 Feb 2015 16:56:45 -0800 (PST)
Received: by 10.202.51.66 with HTTP; Fri, 27 Feb 2015 16:56:45 -0800 (PST)
In-Reply-To: <1A58AAC9-A145-4B8C-8426-712EBE2A5034@iki.fi>
References: <201502272137.t1RLbt3Q020210@maildrop31.somerville.occnc.com> <1A58AAC9-A145-4B8C-8426-712EBE2A5034@iki.fi>
Date: Fri, 27 Feb 2015 16:56:45 -0800
Message-ID: <CAA93jw4pXr9tG7Xd+LeUd8CbdYtrKsg93xSbOGWvxJ50NWmxLw@mail.gmail.com>
From: Dave Taht <dave.taht@gmail.com>
To: Markus Stenberg <markus.stenberg@iki.fi>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/Yvakay4a7REnEfxFf2chX4KTl0o>
Cc: Toerless Eckert <eckert@cisco.com>, Henning Rogge <hrogge@gmail.com>, "homenet@ietf.org Group" <homenet@ietf.org>, "<curtis@ipv6.occnc.com>" <curtis@ipv6.occnc.com>
Subject: Re: [homenet] L2 link status [was: More about marginal links]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sat, 28 Feb 2015 00:56:47 -0000

One of the things I am testing is the new (so far pretty wonderful)
minstrel-blues patches for linux which couples rate control with
reducing power where it can, and adds a per station rc_stats_csv file
that can be easily parsed by external utilities. This gives you a
snapshot of the actual rate to the station being achieved, what the
fallback rates are, and the probability of success.

Example stats:

http://snapon.lab.bufferbloat.net/~d/minstrel-ht-stats.xls

minstrel-blues info: http://www.linuxplumbersconf.org/2014/ocw/sessions/2439

Minstrel itself is the base wifi rate estimator for, I don't know, at
least 1/4 billion wifi enabled devices. IMHO, most others are worse.

A sad thing is that the (GREAT) paper on how minstrel actually works
has never managed to get publication (it circulates as samizdat), and
I really do wish more people grokked wifi rate control problems and
realized that the wifi rate is never a constant, and only rarely even
close to the rated specification of the device, and multicast and
management frames are treated very differently from unicast.

And very differently compared to the old shared pre-switched models of ethernet.

Another useful set of statistics (only if you have an ath9k chip) are
summaries of basic
errors and aggregation stats, for each built in 802.11e compliant queue.

root@minstrel-ht:/sys/kernel/debug/ieee80211/phy1/ath9k# cat xmit
                            BE         BK        VI        VO

MPDUs Queued:                0          0         0       182
MPDUs Completed:         50453          0         0       193
MPDUs XRetried:              0          0         0         0
Aggregates:                  0          0         0         0
AMPDUs Queued HW:            0          0         0         0
AMPDUs Queued SW:        50462          0         0        11
AMPDUs Completed:            9          0         0         0
AMPDUs Retried:              0          0         0         0
AMPDUs XRetried:             0          0         0         0
TXERR Filtered:              0          0         0         0
FIFO Underrun:               0          0         0         0
TXOP Exceeded:               0          0         0         0
TXTIMER Expiry:              0          0         0         0
DESC CFG Error:              0          0         0         0
DATA Underrun:               0          0         0         0
DELIM Underrun:              0          0         0         0
TX-Pkts-All:             50462          0         0       193
TX-Bytes-All:          8539213          0         0     21175
HW-put-tx-buf:               1          0         0         1
HW-tx-start:             50462          0         0       193
HW-tx-proc-desc:         50462          0         0       193
TX-Failed:                   0          0         0         0


From nobody Fri Feb 27 17:14:54 2015
Return-Path: <dave.taht@gmail.com>
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 023AD1A1B2E for <homenet@ietfa.amsl.com>; Fri, 27 Feb 2015 17:14:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.6
X-Spam-Level: 
X-Spam-Status: No, score=-0.6 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 ejEUk3EHPYRe for <homenet@ietfa.amsl.com>; Fri, 27 Feb 2015 17:14:50 -0800 (PST)
Received: from mail-ob0-x22f.google.com (mail-ob0-x22f.google.com [IPv6:2607:f8b0:4003:c01::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 480141A1B27 for <homenet@ietf.org>; Fri, 27 Feb 2015 17:14:48 -0800 (PST)
Received: by mail-ob0-f175.google.com with SMTP id va2so22003761obc.6 for <homenet@ietf.org>; Fri, 27 Feb 2015 17:14:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:date:message-id:subject:from:to:content-type; bh=nS7g3s1Ww4Du+GNqLvtMAMJvwRkGqP3GyIfuCCubbGM=; b=LFQKbzJqW4Pm110WJjtJBOVNIL11PMmhnfadP28JT75aw/WZ2HhVVDOpdyEigmCRuI pIkfWZPUvuU6fi9P5FaGVcSeErKC2njKig4bxUsZCqRYrq36w9Kw8Ob5lNqpuockBcTQ ziZlBXGMxdarpWje+slTLmNvOX+alLEfHZHd4riBPBWHecsFfQedlonJeyBy7H2ksiK0 5jOPXH0uWbn04+5qK7nrqylrt/DcdKdegvxgwwkeBw5eB0GSpyxRK7Do28SzCqVjS7yy hkRv4dmZ9GPYdEWbccfW5DRA/TdwXV9khfSjWDEz4yrf6fJoROMsw3USKgtTNXKF0+3w 3cow==
MIME-Version: 1.0
X-Received: by 10.60.79.10 with SMTP id f10mr10773887oex.8.1425086087585; Fri, 27 Feb 2015 17:14:47 -0800 (PST)
Received: by 10.202.51.66 with HTTP; Fri, 27 Feb 2015 17:14:47 -0800 (PST)
Date: Fri, 27 Feb 2015 17:14:47 -0800
Message-ID: <CAA93jw4NUv=enbAaBtLrwVGhf6yvYepaDhhFcNaL5M2GySso-w@mail.gmail.com>
From: Dave Taht <dave.taht@gmail.com>
To: HOMENET <homenet@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/2-nkgNKhd4SFm4NNLiDhDgvdgz0>
Subject: [homenet] a modest plugfest proposal
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sat, 28 Feb 2015 01:14:53 -0000

I hereby request of the chairs of this working group that they cancel
any planned presentations at the upcoming meeting, and instead require
of the group that they actually bring in their own router from
anything off this list:

http://downloads.openwrt.org/snapshots/trunk/

and there be, say, 5 ethernet separate ports with dedicated dhcpv6 pd
availability of a range from a /48 to a /60 - to somewhat test source
specific routing, prefix distribution, etc -

and that you all spend a few hours devouring the dogfood, instead of
reviewing documentation.

That sort of plugfest would get the known users of things like hnetd
up from 2 to at least 50, and I would hope that the increased
operational experience from the ensuing chaos twould be of benefit for
setting future directions of the wg.

Sincerely,

Rube Goldberg


From nobody Sat Feb 28 00:07:40 2015
Return-Path: <gert@Space.Net>
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 9CB511A00E8 for <homenet@ietfa.amsl.com>; Sat, 28 Feb 2015 00:07:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.61
X-Spam-Level: 
X-Spam-Status: No, score=-2.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 CAHHSyx-5sKL for <homenet@ietfa.amsl.com>; Sat, 28 Feb 2015 00:07:36 -0800 (PST)
Received: from mobil.space.net (mobil.space.net [195.30.115.67]) (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 30ECC1A00ED for <homenet@ietf.org>; Sat, 28 Feb 2015 00:02:54 -0800 (PST)
X-Original-To: homenet@ietf.org
Received: from mobil.space.net (localhost [IPv6:::1]) by mobil.space.net (Postfix) with ESMTP id 6C44F62A63 for <homenet@ietf.org>; Sat, 28 Feb 2015 09:02:52 +0100 (CET)
X-SpaceNet-Relay: true
Received: from moebius3.space.net (moebius3.Space.Net [IPv6:2001:608:2:2::250]) by mobil.space.net (Postfix) with ESMTPS id 246CB60274 for <homenet@ietf.org>; Sat, 28 Feb 2015 09:02:52 +0100 (CET)
Received: (qmail 4031 invoked by uid 1007); 28 Feb 2015 09:02:52 +0100
Date: Sat, 28 Feb 2015 09:02:52 +0100
From: Gert Doering <gert@space.net>
To: Dave Taht <dave.taht@gmail.com>
Message-ID: <20150228080252.GC34798@Space.Net>
References: <CAA93jw4NUv=enbAaBtLrwVGhf6yvYepaDhhFcNaL5M2GySso-w@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAA93jw4NUv=enbAaBtLrwVGhf6yvYepaDhhFcNaL5M2GySso-w@mail.gmail.com>
X-NCC-RegID: de.space
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/kv0p-080LgqYR_9-GVUGjCispAs>
Cc: HOMENET <homenet@ietf.org>
Subject: Re: [homenet] a modest plugfest proposal
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sat, 28 Feb 2015 08:07:38 -0000

Hi,

On Fri, Feb 27, 2015 at 05:14:47PM -0800, Dave Taht wrote:
> That sort of plugfest would get the known users of things like hnetd
> up from 2 to at least 50, and I would hope that the increased
> operational experience from the ensuing chaos twould be of benefit for
> setting future directions of the wg.

I very much like that idea.  

(Unfortunately, I won't be at the IETF meeting, but I am one of those few 
that have actually deployed hnetd/HNCP before :) so I claim sufficient
experience)

Gert Doering
        -- NetMaster
-- 
have you enabled IPv6 on something today...?

SpaceNet AG                        Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444           USt-IdNr.: DE813185279


From nobody Sat Feb 28 01:36:51 2015
Return-Path: <hrogge@gmail.com>
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 419FE1A00DB for <homenet@ietfa.amsl.com>; Sat, 28 Feb 2015 01:36:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 2gJPFUu_4CGo for <homenet@ietfa.amsl.com>; Sat, 28 Feb 2015 01:36:49 -0800 (PST)
Received: from mail-we0-x22e.google.com (mail-we0-x22e.google.com [IPv6:2a00:1450:400c:c03::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C6DD31A03FF for <homenet@ietf.org>; Sat, 28 Feb 2015 01:36:48 -0800 (PST)
Received: by wevm14 with SMTP id m14so24534061wev.13 for <homenet@ietf.org>; Sat, 28 Feb 2015 01:36:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=GNKTqeg8nEQHvYGxEJ9Kax9/vczEZokR5jxxfsxsiTY=; b=NZYKDhL9GmlqGQp7yYv8lG3xeDzVOcsiNrmBvdTpzW2jG222M0m4Dec6bARknN5z8n wMmv2T5opq626SXPz3JXE2QvuXElf9Nff3NqrFtX6illgLFelzp8/GWJ+aeD2BAvNSft DEOV4/NotByY3Tk3D0FFSPTZEj/qaR35iCgwgc61Rz07u2qkzOpfMKJ2VVOgHyEmVJ5n XpXduIRIBO0vpeGwfxg1wdRgyEjgYf0Ph/kCC8f39EoSyZQCim0uXxm2U9T4kPHBrQlo 8/ORlRH1nRIcaw6V6ID8BzoMpXyC+ZrmupYeLC4ybkSE9FKTFKSswiHLsTPfTIJeKeVq jvng==
X-Received: by 10.181.8.75 with SMTP id di11mr15134032wid.26.1425116207614; Sat, 28 Feb 2015 01:36:47 -0800 (PST)
MIME-Version: 1.0
Received: by 10.27.77.212 with HTTP; Sat, 28 Feb 2015 01:36:27 -0800 (PST)
In-Reply-To: <201502272137.t1RLbt3Q020210@maildrop31.somerville.occnc.com>
References: <CAGnRvupwF3N9JQmi_TxWBXkEtO_59ZDQqAPCFcSyFDUVQP8EBw@mail.gmail.com> <201502272137.t1RLbt3Q020210@maildrop31.somerville.occnc.com>
From: Henning Rogge <hrogge@gmail.com>
Date: Sat, 28 Feb 2015 10:36:27 +0100
Message-ID: <CAGnRvuq7c0OJab9e8dRtSo1UpMYSZ6fjsD_GspXPaRFF_0SAkQ@mail.gmail.com>
To: curtis@ipv6.occnc.com
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/E1EXjI9Yg6yoXQz9U0fl8hh_oVI>
Cc: Toerless Eckert <eckert@cisco.com>, "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] L2 link status [was: More about marginal links]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sat, 28 Feb 2015 09:36:50 -0000

On Fri, Feb 27, 2015 at 10:37 PM, Curtis Villamizar
<curtis@ipv6.occnc.com> wrote:
> Henning,
>
> How can a router make use of throughput to a mostly idle neighbor?
> How do you get packets sent to a neighbor that dropped or packets that
> a neighbor sent to you that didn't arrive here?  Raw link speed or
> packet and byte counts don't by themselves tell you much.  The
> equivalent of PPP LQM or MPLS-TP LM OAM would be the sort of thing
> needed is you didn't want to use BFD with a high probe rate.

You need a bit of probing traffic... a few packets per second are
enough to give you an idea about the speed of the link. Of course you
only need to probe neighbors that you did not send normal unicast
anyways since the last probe.

Henning Rogge


From nobody Sat Feb 28 07:25:12 2015
Return-Path: <v6ops@globis.net>
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 420E11A1BDC for <homenet@ietfa.amsl.com>; Sat, 28 Feb 2015 07:25:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.789
X-Spam-Level: 
X-Spam-Status: No, score=0.789 tagged_above=-999 required=5 tests=[BAYES_50=0.8, 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 PMWVHMEVhhu3 for <homenet@ietfa.amsl.com>; Sat, 28 Feb 2015 07:25:05 -0800 (PST)
Received: from globis01.globis.net (mail.globis.net [IPv6:2001:470:1f15:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id C0C681A1BCC for <homenet@ietf.org>; Sat, 28 Feb 2015 07:25:03 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id B576787161B; Sat, 28 Feb 2015 16:25:02 +0100 (CET)
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S2+BqRIXw3gY; Sat, 28 Feb 2015 16:25:02 +0100 (CET)
Received: from Rays-iMac.local (092-111-140-214.static.chello.nl [92.111.140.214]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPSA id 94991871611; Sat, 28 Feb 2015 16:25:02 +0100 (CET)
Message-ID: <54F1DDCC.6020807@globis.net>
Date: Sat, 28 Feb 2015 16:25:00 +0100
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.11 (Macintosh/20140602)
MIME-Version: 1.0
To: Dave Taht <dave.taht@gmail.com>
References: <CAA93jw7eGxPBNX+5LqX+qTYfRxNDxQpKo1fecUa2XH3bAKgvQQ@mail.gmail.com>
In-Reply-To: <CAA93jw7eGxPBNX+5LqX+qTYfRxNDxQpKo1fecUa2XH3bAKgvQQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/RTJJg9AxBQfhnhhf85mPGr0vJ_E>
Cc: HOMENET <homenet@ietf.org>
Subject: Re: [homenet] A poll
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sat, 28 Feb 2015 15:25:09 -0000

Dave Taht wrote:
> The homenet working group has been laboring for several years now to
> find ways to make ipv6 more deployable to home (and presumably small
> business) users.
>
> In addition to multiple specification documents some code has been
> produced to try and make things easier. At least in the USA, comcast
> has rolled out IPv6 to everyone that can get dhcpv6 to sort of work on
> their router, and/or is willing to install a custom firmware on their
> router to get that, and of course tunneling ipv6 is possible if the
> ISP does not support it.
>
> So a quick poll:
>
> 0) Have you managed to get ipv6 working at all? If so, how? What sort
> of problems did you encounter?
Been using IPv6 in production at home since around 2010.

Main problems have been:

The assumptions manufacturers have made about how the boxes will be 
plugged together and assuming they're the only router in the home. Hence 
Homenet.
Several bugs in Apple airport and time capsule routers, blocking traffic 
incorrectly.
Lack of Protocol41 forwarding support in a lot of equipment.
Software updates killing 6to4 configured tunnel mode.
Cisco EPC3925 that refused to go into bridge mode (probably by design of 
the ISP).
Lack of fibre into the building means I'm stuck with the local cable 
provider, although there's "net-neutral" fibre in neighbouring streets 
supporting multiple native IPv6 providers.
>
> 1) Have you attempted to deploy a routing protocol in your home? Which
> one, and why?
Yes. Static routing. Nothing else was supported in common, and I wanted 
a mail server on the outside in a DMZ and a private network on the inside.
It took a lot of tweaking to find a topology that worked simultaneously 
with IPv4 and supported what I wanted to do in IPv6.
>
> 2) Have you attempted to get hnetd's prefix distribution system
> working? (it supports linux mainline and openwrt presently)
Yes, but not tested too much yet as I've been moving a data centre.
Just bought a stack of WDR4300's to test with. Also with the intention 
of looking at mesh networking.
So hopefully I'll get around to it $day_job permitting.
> 3) Do you use ethernet? How many clients in your home are ethernet connected?
Ethernet, powerline Ethernet, and wifi.

2 Raspberry Pi's
1 Linux server
2 iMacs
1 windows laptop
bunch of music sequencers and synths
1 printer
a couple of NAS boxes
a few wireless routers
guest devices
Apple TV
2 iPads
1 playstation

so probably ±10 hard wired. The rest wireless.
> 4) Do you use wifi? How many clients are wifi connected? Do you use
> range extenders?
Yes I use wifi extensively.

I used range extension (Apple Airport Extreme) for a while, but ended up 
running a cable.

> 5) How many devices do you think you will have connected to the
> network in your home in 5 years? How many now?
30?

Audio Visual Bridging (AVB) could throw a spanner in the works of having 
seamless connectivity throughout the home.
Hopefully someone will figure out a way of transmitting music/audio 
streams in a sample-coordinated manner at L3.
> 6) Do you use any other network connected technologies (homeplug,
> 802.14, LTE, etc). If so, which ones, and why?
yes. Powerline IP to try to avoid running a cable. It wasn't too successful.

> 7) Do you use mdns service discovery?
Unfortunately yes, and I wonder how this will scale over L3.
UPnP too.
> 8) Why are you here? (especially, if your answers to 0-2, are "no")
Because if Homenet does solve the ISP multihoming problem, and possibly 
the wifi roaming problems at L3, it will also be used extensively in SME 
and SOHO set ups, and perhaps even in campus-size deployments.

-- 
Regards,
RayH


From nobody Sat Feb 28 09:47:18 2015
Return-Path: <dave.taht@gmail.com>
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 3C3461A7028; Sat, 28 Feb 2015 09:47:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.101
X-Spam-Level: 
X-Spam-Status: No, score=-0.101 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 E2ekt3troMtZ; Sat, 28 Feb 2015 09:47:15 -0800 (PST)
Received: from mail-oi0-x22d.google.com (mail-oi0-x22d.google.com [IPv6:2607:f8b0:4003:c06::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB54B1A7021; Sat, 28 Feb 2015 09:47:15 -0800 (PST)
Received: by mail-oi0-f45.google.com with SMTP id i138so20766881oig.4; Sat, 28 Feb 2015 09:47:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=H1OBaaXJhSIyjpUV/hlQM3LXRO4HiqZhiNJh0/+ahzo=; b=ZZqZ4Bn8UALPzQLgANHu7qrf6ggF9A7vt9ojAoR6WtgATsfgxxE7gCRbgm9ReTzRAh 2NG8tRX/M3ZHDyaTeCCauHsNBzOkk9OxbernDS8rEaKIv+Mqe8eHC4C8TUbyR+EnnS4M lfaLkH1X0eoc3CqJ7wbK9viGW16UWwd65Noqmbvh2UOPq3Cx/lgFbmgp7uwWDhWXuDCD un5o7TnIsqPGKX1k2L/JBXRHL+jyCsI9UZkxwR/x1TGQEjYiyto+yRIhVZlWmLuPSyf5 BxJ+rbCFkHBqtvHEWLnvH2F6ZZtxkBDQbxWtEowEZXB9Ule99nGYMxNTmOZ2/1gmEBg7 fDzQ==
MIME-Version: 1.0
X-Received: by 10.60.103.234 with SMTP id fz10mr13964579oeb.11.1425145634997;  Sat, 28 Feb 2015 09:47:14 -0800 (PST)
Received: by 10.202.51.66 with HTTP; Sat, 28 Feb 2015 09:47:14 -0800 (PST)
In-Reply-To: <54F1F630.3080902@wlan-si.net>
References: <54F1F630.3080902@wlan-si.net>
Date: Sat, 28 Feb 2015 09:47:14 -0800
Message-ID: <CAA93jw5pXS5jBwp9w6vAyjpwOgvg40=e864uMfwjRqc=eF1Y_g@mail.gmail.com>
From: Dave Taht <dave.taht@gmail.com>
To: Battle of the Mesh Mailing List <battlemesh@ml.ninux.org>,  "cerowrt-devel@lists.bufferbloat.net" <cerowrt-devel@lists.bufferbloat.net>, "aqm@ietf.org" <aqm@ietf.org>,  HOMENET <homenet@ietf.org>, bloat <bloat@lists.bufferbloat.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/ftAg0GIpw0Vxrf_kMtFuYbPCTds>
Subject: Re: [homenet] [Battlemesh] Battlemesh V8 Logo
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sat, 28 Feb 2015 17:47:17 -0000

On Sat, Feb 28, 2015 at 9:09 AM, Musti <musti@wlan-si.net> wrote:
> Hi folks,
>
> I am happy to present the new logo for Battlemesh V8 in Maribor,
> designed by Barbara :)
>
> http://battlemesh.org/BattleMeshV8/PosterDesign
>
> Comments appreciated!

That is a truly awesome poster! I hope you line up more sponsors for
this conference!

>
> Kind regards,
> Musti
> _______________________________________________
> Battlemesh mailing list
> Battlemesh@ml.ninux.org
> http://ml.ninux.org/mailman/listinfo/battlemesh



--=20
Dave T=C3=A4ht
Let's make wifi fast, less jittery and reliable again!

https://plus.google.com/u/0/107942175615993706558/posts/TVX3o84jjmb


From nobody Sat Feb 28 10:39:10 2015
Return-Path: <curtis@ipv6.occnc.com>
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 493981A7D84 for <homenet@ietfa.amsl.com>; Sat, 28 Feb 2015 10:39:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.912
X-Spam-Level: 
X-Spam-Status: No, score=-1.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, 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 pG8c13kOV5Q6 for <homenet@ietfa.amsl.com>; Sat, 28 Feb 2015 10:39:06 -0800 (PST)
Received: from maildrop31.somerville.occnc.com (maildrop31.somerville.occnc.com [IPv6:2001:550:3800:203::3131]) (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 3C90D1A7D83 for <homenet@ietf.org>; Sat, 28 Feb 2015 10:39:06 -0800 (PST)
Received: from harbor31.somerville.occnc.com (harbor31.somerville.occnc.com [IPv6:2001:550:3800:203::3231]) (authenticated bits=128) by maildrop31.somerville.occnc.com (8.14.9/8.14.9) with ESMTP id t1SIciVB035453; Sat, 28 Feb 2015 13:38:45 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201502281838.t1SIciVB035453@maildrop31.somerville.occnc.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
From: Curtis Villamizar <curtis@ipv6.occnc.com>
In-reply-to: Your message of "Wed, 25 Feb 2015 15:50:47 -0500." <17359.1424897447@sandelman.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <35451.1425148724.1@harbor31.somerville.occnc.com>
Date: Sat, 28 Feb 2015 13:38:44 -0500
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/egAYQPcAJe9AVc0gHQRntd7opo4>
Cc: Ray Hunter <v6ops@globis.net>, "homenet@ietf.org Group" <homenet@ietf.org>, Teco Boot <teco@inf-net.nl>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.com
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sat, 28 Feb 2015 18:39:08 -0000

In message <17359.1424897447@sandelman.ca>
Michael Richardson writes:
 
> Ray Hunter <v6ops@globis.net> wrote:
>     > I agree that WiFi roaming is a problem that needs addressing in
>     > Homenet.
>  
> Yes, but can we rule it out of scope for now?
>  
> Can we agree that it's not strictly a routing problem, and that the set of
> solutions that we are considering could be used, and that we could also
> explain how to do something like automatically setup capwap using HNCP for
> discovery, but that we don't have the head-of-queue block on this item for
> now?
>  
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
>  -= IPv6 IoT consulting =-


Perhaps consider it two problems, roaming within an administrative
domain and roaming into another administrative doamin.

The latter is harder to solve.

Other than bridging all of the AP within an administrative domain,
there is no way to support the former without at least some host
change.  As I mentioned before, I favor putting a /128 on the
loopback and having the routers/APs forward to the interface address
of the moment to that /128.

Curtis


From nobody Sat Feb 28 15:42:26 2015
Return-Path: <curtis@ipv6.occnc.com>
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 612EB1A009B for <homenet@ietfa.amsl.com>; Sat, 28 Feb 2015 15:42:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.512
X-Spam-Level: 
X-Spam-Status: No, score=-0.512 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, SPF_HELO_PASS=-0.001, 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 1pH-2KM6QRDo for <homenet@ietfa.amsl.com>; Sat, 28 Feb 2015 15:42:22 -0800 (PST)
Received: from maildrop31.somerville.occnc.com (maildrop31.somerville.occnc.com [IPv6:2001:550:3800:203::3131]) (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 802461A0097 for <homenet@ietf.org>; Sat, 28 Feb 2015 15:42:22 -0800 (PST)
Received: from harbor31.somerville.occnc.com (harbor31.somerville.occnc.com [IPv6:2001:550:3800:203::3231]) (authenticated bits=128) by maildrop31.somerville.occnc.com (8.14.9/8.14.9) with ESMTP id t1SNeW1h040930; Sat, 28 Feb 2015 18:40:32 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201502282340.t1SNeW1h040930@maildrop31.somerville.occnc.com>
To: Dave Taht <dave.taht@gmail.com>
From: Curtis Villamizar <curtis@ipv6.occnc.com>
In-reply-to: Your message of "Fri, 27 Feb 2015 14:28:38 -0800." <CAA93jw4tuMfM_LvZKRX7aRk2Z+HWTw5jBOENpvfEJuT4L9TcUQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <40928.1425166832.1@harbor31.somerville.occnc.com>
Content-Transfer-Encoding: quoted-printable
Date: Sat, 28 Feb 2015 18:40:32 -0500
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/2hQYrrhNgdtwj3RkY5TYeYGz524>
Cc: Ray Hunter <v6ops@globis.net>, "homenet@ietf.org Group" <homenet@ietf.org>, Teco Boot <teco@inf-net.nl>, Mikael Abrahamsson <swmike@swm.pp.se>, "<curtis@ipv6.occnc.com>" <curtis@ipv6.occnc.com>
Subject: Re: [homenet] Routing protocol comparison document
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.com
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sat, 28 Feb 2015 23:42:25 -0000

In message <CAA93jw4tuMfM_LvZKRX7aRk2Z+HWTw5jBOENpvfEJuT4L9TcUQ@mail.gmail=
.com>
Dave Taht writes:
 =

> On Fri, Feb 27, 2015 at 2:00 PM, Curtis Villamizar
> <curtis@ipv6.occnc.com> wrote:
> > In message <54EE258E.8060302@gmail.com>
> > Brian E Carpenter writes:
> >
> >> On 26/02/2015 05:14, Mikael Abrahamsson wrote:
> >> > On Wed, 25 Feb 2015, Ray Hunter wrote:
> >> >
> >> >> That way the devices can roam at L3, without all of the nasty side=
 effects of re-establishing TPC sessions, or updating
> >> >> dynamic naming services, or having to run an L2 overlay network ev=
erywhere, or having to support protocols that require a
> >> >> specialised partner in crime on the server side (mTCP, shim6 et al=
).
> >> >
> >> > It's my firm belief that we need to rid clients of IP address depen=
dence for its sessions. Asking clients to participate in HNCP
> >> > only addresses the problem where HNCP is used.
> >> >
> >> > Fixing this for real would reap benefits for devices moving between=
 any kind of network, multiple providers, mobile/fixed etc.
> >>
> >> Violent agreement. This is not a homenet problem; it's an IP problem.
> >> In fact, it's exactly why IP addresses are considered harmful in
> >> some quarters. Trying to fix it just for homenet seems pointless.
> >> http://www.sigcomm.org/ccr/papers/2014/April/0000000.0000008
> >>
> >>    Brian
> >
> >
> > Brian,
> >
> > Seriously - your paper may be overstating the problem.  At least if we
> > discount IPv4 and in doing so eliminate NAT we solve a lot of problems
> > that never should have existed in the first place.  If we carry NAT
> > over to IPV6, then shame on us.
>  =

> I am sorry, I no longer share this opinion. The pains of renumbering
> someones entire home network every time the ISP feels like it, given
> the enormous number of devices I have encountered that don't handle it
> well, are just too much to bear.

I renumbered 140.222/16 into 147.225/16 in the mid 1990s (T3-NSFNET to
ANSNET as part of the NSFNET decommissioning).  Not by myself of
course, but there were only a few of us on this.  It wasn't all that
bad and we had about 2,000 things to renumber in hundreds of
locations, many of them not manned.  Shell scripts and ksh (kerberized
rsh, not the Korn shell) made it simpler.  The worst was Cisco routers
and various old DSU/CSU and other commercial stuff since you had to
use "expect" scripts on their CLI rather than just something of the
form "ksh fqdn -l root ifconfig newaddr/mask alias" People with root
on their workstation that didn't give us acess were given notice.  We
used interface aliases and gradually took down the old aliases and
subnet addresses.  Nothing critical was affected.  It took a day or
two, then bake time, then less than a day to remove aliases.

OTOH - Most homes can't run two prefixes for a week or two before
taking the old prefix down.  And lots of consumer devices don't do
aliases.  But now days there is DHCP which didn't exist then (and
ICMPv6 RS/RA and SLAAC).

Are you having problems with the provider not giving you a static IPv6
prefix, but rather changing it on a whim?

I also renumbered my home net multiple times, but again, not much
pain.  Only a few consumer gadgets here have fixed addresses (one
because it never renewed DHCP leases and therefore needed a fixed
address, but that has since been tossed in e-waste recycling).

> The next version of cerowrt will do translation from the external IPv6
> address range to a static internal one (or ones, in the case of
> multiple egress gateways), and lacking a standard for such will use
> fcxx/8 addressing. I will make it be an option for people to turn off,
> but I've had it with being renumbered.

Are you suggesting that we add NAT to IPv6?  [I ask with disbelief.]

I would definitely be turning that off since I have a plenty big and
very static IPv6 prefix.  I also have a (tiny) static IPv4 prefix so I
have no choice but to IPv4 NAT due to its tiny size.

A better option might be to use something that switches over faster
than a DHCP lease times of days.  It seems that ICMPv6 RA can be sent
with prefix prefix information TLV with valid lifetime and/or
preferred valid lifetime of zero.  This is in RFC 4861 on Page 55:

      - If the prefix is already present in the host's Prefix List as
        the result of a previously received advertisement, reset its
        invalidation timer to the Valid Lifetime value in the Prefix
        Information option.  If the new Lifetime value is zero, time-out
        the prefix immediately (see Section 6.3.5).

Would that help?

Also, stateful DHCPv6 can invalidate leases (me thinks)?  Maybe
DHCPv4?  Am I mistaken about that?

> I am sure this will break stuff, and I don't know what all it will do,
> and I intend to find out.

Just breaks the end-to-end principle and requires rendezvous and all
that ugliness.

IMHO it would be better to send an immediate RA with a zero lifetime
on the old prefix and a normal lifetime on the new prefix.  If hosts
don't do the right thing they are in violation of RFC 4861.

OTOH, invalidating a DHCP lease would not do what we want here.

> Until some far off day where we have stable name to ipv6 address
> mapping, and vice versa, it is otherwise impossible to have useful
> ipv6 based services inside the home or small business.

Oh yeah.  And then there is DNS.  Maybe it would be better to keep a
short non-zero valid lifetime (longer than DNS TTL) and a preferred
valid lifetime of zero on that old prefix so it sticks around and is
usable locally but not preferred so not used for outgoing
connections.  Good reason to not set DNS TTL to days.  That way hosts
with cached DNS mapping to the old addresses will still work.

> > If we get rid of NAT a big part of the problem just goes away.  No
> > alternate spaces, kludgy rendezvous mechanisms, etc.  Using an address
> > on the loopback gets rid of the multiple interface problem and where
> > it really matters (ISP router and ISP or DS server reachability) this
> > has been done with configuration for two decades.  The multihoming
> > failover or roaming are a bit more difficult but things MPTCP is
> > supposed to address.
> >
> > Curtis

You want to keep NAT for IPV6?  Really?

Curtis


From nobody Sat Feb 28 15:55:12 2015
Return-Path: <curtis@ipv6.occnc.com>
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 90A731A00A2 for <homenet@ietfa.amsl.com>; Sat, 28 Feb 2015 15:55:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.912
X-Spam-Level: 
X-Spam-Status: No, score=-1.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, 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 A_dJpFq7YnpI for <homenet@ietfa.amsl.com>; Sat, 28 Feb 2015 15:55:10 -0800 (PST)
Received: from maildrop31.somerville.occnc.com (maildrop31.somerville.occnc.com [IPv6:2001:550:3800:203::3131]) (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 095351A009B for <homenet@ietf.org>; Sat, 28 Feb 2015 15:55:09 -0800 (PST)
Received: from harbor31.somerville.occnc.com (harbor31.somerville.occnc.com [IPv6:2001:550:3800:203::3231]) (authenticated bits=128) by maildrop31.somerville.occnc.com (8.14.9/8.14.9) with ESMTP id t1SNqMcZ041025; Sat, 28 Feb 2015 18:52:22 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201502282352.t1SNqMcZ041025@maildrop31.somerville.occnc.com>
To: Dave Taht <dave.taht@gmail.com>
From: Curtis Villamizar <curtis@ipv6.occnc.com>
In-reply-to: Your message of "Fri, 27 Feb 2015 16:26:47 -0800." <CAA93jw627Q12XkZy3CFuV81CLbJc5D9oX6LK1=cgetWsOP1B3g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <41023.1425167542.1@harbor31.somerville.occnc.com>
Content-Transfer-Encoding: quoted-printable
Date: Sat, 28 Feb 2015 18:52:22 -0500
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/qsc_E7WHeq_1DDHs8KGkB-r3AZs>
Cc: Toerless Eckert <eckert@cisco.com>, "homenet@ietf.org Group" <homenet@ietf.org>, "<curtis@ipv6.occnc.com>" <curtis@ipv6.occnc.com>
Subject: Re: [homenet] L2 link status [was: More about marginal links]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.com
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sat, 28 Feb 2015 23:55:11 -0000

In message <CAA93jw627Q12XkZy3CFuV81CLbJc5D9oX6LK1=3DcgetWsOP1B3g@mail.gma=
il.com>
Dave Taht writes:
> >
> > BFD, Hellos, or any form of probe traffic over wireless has the speed
> > of detection vs overhead issue.  At nominal 10 Mb/s (low end today for
> > wireless) a small probe would take about 0.1 msec (for example, 125
> > bytes including all overhead is about 1000 bits).  Not bad if running
> > 100 probes/sec (30 msec detection) unless there are a very large
> > number of stations using the AP and doing the same thing.  In that
>  =

> You are thinking about it wrong. Wireless-g is only capable of roughly
> 1300 TXOPs total per second. Bandwidth has NOTHING to do with it.
>  =

> I don't have the figure in my head for n or ac, but it is not a lot, and
> in the presence of g, falls back to the above figure.
>  =

> losing 10% of the bandwidth - per station - to run BFD is not an option.
>  =

> > case 10 probes per second might be better.  A very high collision rate
>  =

> Still too much. Next question?


Oops yeah.  You are right.  Forgot about TXOPs.

How about a PPP LQM / MPLS-TP LM OAM equivalent?

Briefly:

  "A" sends pkt/byte sent to "B".

  "B" notes pkt/byte recv and adds that to the packet.

  "B" adds its pkt/byte sent and sends that back to "A".

  "A" notes its pkt/byte recv and sends back to "B".  "A" saves this.

  "B" simply receives and saves this.

  Save prior packet, wait some time, and then repeat:

    Now subtract the two sets of counter (new - old packet).

    Each side compares other side sent to their own received.
    Difference is number of packets dropped.

  Repeat forever using prior result to update drop rate.

If any of the control packets drop, drop a partial result, repeat
later, and compare to the last complete result.

Is one cycle per neighbor too much?  How about one cycle per neighbor
each 5 seconds?  If "B" is the AP it sends only one packet per cycle
but both sides get accurate drop rate for both directions.

Curtis


From nobody Sat Feb 28 16:03:45 2015
Return-Path: <curtis@ipv6.occnc.com>
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 8B13C1A00D4 for <homenet@ietfa.amsl.com>; Sat, 28 Feb 2015 16:03:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.912
X-Spam-Level: 
X-Spam-Status: No, score=-1.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, 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 OgNMJ9v9WzBt for <homenet@ietfa.amsl.com>; Sat, 28 Feb 2015 16:03:42 -0800 (PST)
Received: from maildrop31.somerville.occnc.com (maildrop31.somerville.occnc.com [IPv6:2001:550:3800:203::3131]) (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 88C981A0097 for <homenet@ietf.org>; Sat, 28 Feb 2015 16:03:42 -0800 (PST)
Received: from harbor31.somerville.occnc.com (harbor31.somerville.occnc.com [IPv6:2001:550:3800:203::3231]) (authenticated bits=128) by maildrop31.somerville.occnc.com (8.14.9/8.14.9) with ESMTP id t2100qnZ041161; Sat, 28 Feb 2015 19:00:53 -0500 (EST) (envelope-from curtis@ipv6.occnc.com)
Message-Id: <201503010000.t2100qnZ041161@maildrop31.somerville.occnc.com>
To: Dave Taht <dave.taht@gmail.com>
From: Curtis Villamizar <curtis@ipv6.occnc.com>
In-reply-to: Your message of "Fri, 27 Feb 2015 16:28:48 -0800." <CAA93jw7yYJ4OUagSEd-dn4TTvKuWucyLOQdsqXPHO4aF+3hVsA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <41159.1425168052.1@harbor31.somerville.occnc.com>
Content-Transfer-Encoding: quoted-printable
Date: Sat, 28 Feb 2015 19:00:52 -0500
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/8SeyvlAanXphnsYa-cSroxaZULc>
Cc: Toerless Eckert <eckert@cisco.com>, Henning Rogge <hrogge@gmail.com>, "homenet@ietf.org Group" <homenet@ietf.org>, "<curtis@ipv6.occnc.com>" <curtis@ipv6.occnc.com>
Subject: Re: [homenet] L2 link status [was: More about marginal links]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: curtis@ipv6.occnc.com
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sun, 01 Mar 2015 00:03:44 -0000

In message <CAA93jw7yYJ4OUagSEd-dn4TTvKuWucyLOQdsqXPHO4aF+3hVsA@mail.gmail=
.com>
Dave Taht writes:
 =

> On Fri, Feb 27, 2015 at 1:37 PM, Curtis Villamizar
> <curtis@ipv6.occnc.com> wrote:
> > In message <CAGnRvupwF3N9JQmi_TxWBXkEtO_59ZDQqAPCFcSyFDUVQP8EBw@mail.g=
mail.com>
> > Henning Rogge writes:
> >
> >> On Wed, Feb 25, 2015 at 9:36 PM, Curtis Villamizar
> >> <curtis@ipv6.occnc.com> wrote:
> >> > In message <87a903ef2j.wl-jch@pps.univ-paris-diderot.fr>
> >> > Juliusz Chroboczek writes:
> >> >> As to wireless links -- as far as I'm aware, making efficient use =
of
> >> >> wireless L2 information in a routing protocol is an open research =
problem.
> >> >
> >> > Other than signal strength and collision rate, what L2 information =
is
> >> > available?  Per MAC information would be nice for the AP side or an=
y
> >> > node in mesh or adhoc mode but that isn't collected anywhere AFAIK.
> >>
> >> Raw linkspeed and (on Linux) even Throughput to each neighbor... and =
a lot more.
> >>
> >> Just run "iw wlan0 station dump" on a Linux system with wifi and you
> >> will be surprised how much information you will get.
> >>
> >> Henning Rogge
> >
> >
> > Henning,
> >
> > How can a router make use of throughput to a mostly idle neighbor?
> > How do you get packets sent to a neighbor that dropped or packets that
> > a neighbor sent to you that didn't arrive here?  Raw link speed or
> > packet and byte counts don't by themselves tell you much.  The
> > equivalent of PPP LQM or MPLS-TP LM OAM would be the sort of thing
> > needed is you didn't want to use BFD with a high probe rate.
> >
> > As I said above (or tried to say), the most useful hints that the link
> > isn't as good as nominal link speed might indicate might be signal
> > strength and collision rate.  [What I meant above by "available" was
> > available and useful for "making efficient use of wireless L2
> > information in a routing protocol" in the quoted text.  So maybe I was
> > too terse in saying that.]
> >
> > Thanks for the response though.  I use FreeBSD and other than rate and
> > S/N there isn't much, so could you send me sample output from a Linux
> > host or better yet a Linux AP with a few "neighbors".  We can take
> > this off list and discuss the sample output but so far "lots of stuff"
> > (sic) doesn't help.
> >
> > Curtis
> >
> >
> > ps - maybe I should stop procrastinating and compile and flash openwrt
> > and see for myself, but for now ...
>  =

> You don't have to compile a thing, just download the right nightly
> from chaos calmer (preferred as hnetd etc are in it), and flash it.
>  =

> Everyone here, has been 90 bucks, 5 minutes and one reflash away from
> eating it's dogfood for 9+ months now.
>  =

> http://downloads.openwrt.org/snapshots/trunk/


Dave,

I do need to compile if I prefer to try some of my own recipes for dog
food.  Not that I don't also want to try yours.

I'm more interested in Ethernet than WiFi for my home use.  WiFi is
sort of like the penalty box here.  It works fine for normal web
browsing and such.  If I want to move more than just a few bits around
I plug the laptop into a GbE port somewhere.

btw- You do have an advantage in any discussion based on running code.

Curtis


From nobody Sat Feb 28 17:24:19 2015
Return-Path: <brian.e.carpenter@gmail.com>
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 9B5231A0140 for <homenet@ietfa.amsl.com>; Sat, 28 Feb 2015 17:24:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 bP83BunZ0l3z for <homenet@ietfa.amsl.com>; Sat, 28 Feb 2015 17:24:15 -0800 (PST)
Received: from mail-pa0-x229.google.com (mail-pa0-x229.google.com [IPv6:2607:f8b0:400e:c03::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DA2D41A0127 for <homenet@ietf.org>; Sat, 28 Feb 2015 17:24:14 -0800 (PST)
Received: by paceu11 with SMTP id eu11so33032358pac.7 for <homenet@ietf.org>; Sat, 28 Feb 2015 17:24:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=IVWVYxATnV2V5SGeLbYdTszqA4lbur1hZDZq0KqClkE=; b=C5r3uk0R6chGbueGBU/qJqDQUGBpsc0/aE/2ErzqybuifgB/dnUCOFf9XY8NLxeKuP 7P2PnRa26Tbb9okJ2o/zPxS/caImzWhLo9+fUwU2XWjxrFd2iEJBO4TJen2c0jg3R8zk rGzN+Xd+t2YG9Tp7LU5ToksHork0AnxfU/Er9ff1KEOQldduUt5NiFkcto5VuhxZ5Xvy nH+NQp2T0pn8p7+L4Dka1RDe1kO6QZTZtnfqhQ8KcOITiU/uh1wKoS1tqGwzrG3EltlE g8DqS36l40l5llDl4epS83iifJxQ1KNxusaYYDgpEMDZATFAdoIJyBSKsNelwmv9n5Wt RUjA==
X-Received: by 10.66.218.129 with SMTP id pg1mr5371541pac.65.1425173054134; Sat, 28 Feb 2015 17:24:14 -0800 (PST)
Received: from ?IPv6:2406:e007:7c13:1:28cc:dc4c:9703:6781? ([2406:e007:7c13:1:28cc:dc4c:9703:6781]) by mx.google.com with ESMTPSA id ie5sm7936349pbb.14.2015.02.28.17.24.09 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 28 Feb 2015 17:24:13 -0800 (PST)
Message-ID: <54F26A38.8070005@gmail.com>
Date: Sun, 01 Mar 2015 14:24:08 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: curtis@ipv6.occnc.com, Dave Taht <dave.taht@gmail.com>
References: <201502282340.t1SNeW1h040930@maildrop31.somerville.occnc.com>
In-Reply-To: <201502282340.t1SNeW1h040930@maildrop31.somerville.occnc.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/CIZU1DKtfkcW8MkcQmT_K0KaKso>
Cc: Ray Hunter <v6ops@globis.net>, "homenet@ietf.org Group" <homenet@ietf.org>, Teco Boot <teco@inf-net.nl>, Mikael Abrahamsson <swmike@swm.pp.se>
Subject: [homenet] 6renum redux [Routing protocol comparison document]
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Sun, 01 Mar 2015 01:24:17 -0000

Admittedly 6renum was targetted at enterprise networks, partly because
of the
observation that homenets renumber anyway after every power cut. But
we have spent a lot of cycles on this issue.

http://tools.ietf.org/html/rfc4192
http://tools.ietf.org/html/rfc5887
http://tools.ietf.org/html/rfc6866
http://tools.ietf.org/html/rfc6879
http://tools.ietf.org/html/rfc7010
and maybe it's time to revive
https://tools.ietf.org/html/draft-liu-opsarea-ipv6-renumbering-guidelines

   Brian


On 01/03/2015 12:40, Curtis Villamizar wrote:
> In message <CAA93jw4tuMfM_LvZKRX7aRk2Z+HWTw5jBOENpvfEJuT4L9TcUQ@mail.gmail.com>
> Dave Taht writes:
>  
>> On Fri, Feb 27, 2015 at 2:00 PM, Curtis Villamizar
>> <curtis@ipv6.occnc.com> wrote:
>>> In message <54EE258E.8060302@gmail.com>
>>> Brian E Carpenter writes:
>>>
>>>> On 26/02/2015 05:14, Mikael Abrahamsson wrote:
>>>>> On Wed, 25 Feb 2015, Ray Hunter wrote:
>>>>>
>>>>>> That way the devices can roam at L3, without all of the nasty side effects of re-establishing TPC sessions, or updating
>>>>>> dynamic naming services, or having to run an L2 overlay network everywhere, or having to support protocols that require a
>>>>>> specialised partner in crime on the server side (mTCP, shim6 et al).
>>>>>
>>>>> It's my firm belief that we need to rid clients of IP address dependence for its sessions. Asking clients to participate in HNCP
>>>>> only addresses the problem where HNCP is used.
>>>>>
>>>>> Fixing this for real would reap benefits for devices moving between any kind of network, multiple providers, mobile/fixed etc.
>>>>
>>>> Violent agreement. This is not a homenet problem; it's an IP problem.
>>>> In fact, it's exactly why IP addresses are considered harmful in
>>>> some quarters. Trying to fix it just for homenet seems pointless.
>>>> http://www.sigcomm.org/ccr/papers/2014/April/0000000.0000008
>>>>
>>>>    Brian
>>>
>>>
>>> Brian,
>>>
>>> Seriously - your paper may be overstating the problem.  At least if we
>>> discount IPv4 and in doing so eliminate NAT we solve a lot of problems
>>> that never should have existed in the first place.  If we carry NAT
>>> over to IPV6, then shame on us.
>>  
>> I am sorry, I no longer share this opinion. The pains of renumbering
>> someones entire home network every time the ISP feels like it, given
>> the enormous number of devices I have encountered that don't handle it
>> well, are just too much to bear.
> 
> I renumbered 140.222/16 into 147.225/16 in the mid 1990s (T3-NSFNET to
> ANSNET as part of the NSFNET decommissioning).  Not by myself of
> course, but there were only a few of us on this.  It wasn't all that
> bad and we had about 2,000 things to renumber in hundreds of
> locations, many of them not manned.  Shell scripts and ksh (kerberized
> rsh, not the Korn shell) made it simpler.  The worst was Cisco routers
> and various old DSU/CSU and other commercial stuff since you had to
> use "expect" scripts on their CLI rather than just something of the
> form "ksh fqdn -l root ifconfig newaddr/mask alias" People with root
> on their workstation that didn't give us acess were given notice.  We
> used interface aliases and gradually took down the old aliases and
> subnet addresses.  Nothing critical was affected.  It took a day or
> two, then bake time, then less than a day to remove aliases.
> 
> OTOH - Most homes can't run two prefixes for a week or two before
> taking the old prefix down.  And lots of consumer devices don't do
> aliases.  But now days there is DHCP which didn't exist then (and
> ICMPv6 RS/RA and SLAAC).
> 
> Are you having problems with the provider not giving you a static IPv6
> prefix, but rather changing it on a whim?
> 
> I also renumbered my home net multiple times, but again, not much
> pain.  Only a few consumer gadgets here have fixed addresses (one
> because it never renewed DHCP leases and therefore needed a fixed
> address, but that has since been tossed in e-waste recycling).
> 
>> The next version of cerowrt will do translation from the external IPv6
>> address range to a static internal one (or ones, in the case of
>> multiple egress gateways), and lacking a standard for such will use
>> fcxx/8 addressing. I will make it be an option for people to turn off,
>> but I've had it with being renumbered.
> 
> Are you suggesting that we add NAT to IPv6?  [I ask with disbelief.]
> 
> I would definitely be turning that off since I have a plenty big and
> very static IPv6 prefix.  I also have a (tiny) static IPv4 prefix so I
> have no choice but to IPv4 NAT due to its tiny size.
> 
> A better option might be to use something that switches over faster
> than a DHCP lease times of days.  It seems that ICMPv6 RA can be sent
> with prefix prefix information TLV with valid lifetime and/or
> preferred valid lifetime of zero.  This is in RFC 4861 on Page 55:
> 
>       - If the prefix is already present in the host's Prefix List as
>         the result of a previously received advertisement, reset its
>         invalidation timer to the Valid Lifetime value in the Prefix
>         Information option.  If the new Lifetime value is zero, time-out
>         the prefix immediately (see Section 6.3.5).
> 
> Would that help?
> 
> Also, stateful DHCPv6 can invalidate leases (me thinks)?  Maybe
> DHCPv4?  Am I mistaken about that?
> 
>> I am sure this will break stuff, and I don't know what all it will do,
>> and I intend to find out.
> 
> Just breaks the end-to-end principle and requires rendezvous and all
> that ugliness.
> 
> IMHO it would be better to send an immediate RA with a zero lifetime
> on the old prefix and a normal lifetime on the new prefix.  If hosts
> don't do the right thing they are in violation of RFC 4861.
> 
> OTOH, invalidating a DHCP lease would not do what we want here.
> 
>> Until some far off day where we have stable name to ipv6 address
>> mapping, and vice versa, it is otherwise impossible to have useful
>> ipv6 based services inside the home or small business.
> 
> Oh yeah.  And then there is DNS.  Maybe it would be better to keep a
> short non-zero valid lifetime (longer than DNS TTL) and a preferred
> valid lifetime of zero on that old prefix so it sticks around and is
> usable locally but not preferred so not used for outgoing
> connections.  Good reason to not set DNS TTL to days.  That way hosts
> with cached DNS mapping to the old addresses will still work.
> 
>>> If we get rid of NAT a big part of the problem just goes away.  No
>>> alternate spaces, kludgy rendezvous mechanisms, etc.  Using an address
>>> on the loopback gets rid of the multiple interface problem and where
>>> it really matters (ISP router and ISP or DS server reachability) this
>>> has been done with configuration for two decades.  The multihoming
>>> failover or roaming are a bit more difficult but things MPTCP is
>>> supposed to address.
>>>
>>> Curtis
> 
> You want to keep NAT for IPV6?  Really?
> 
> Curtis
> 
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
> 

