
From kitamura@da.jp.nec.com  Tue Nov  1 01:14:34 2011
Return-Path: <kitamura@da.jp.nec.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C055621F8B4F for <homenet@ietfa.amsl.com>; Tue,  1 Nov 2011 01:14:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.09
X-Spam-Level: 
X-Spam-Status: No, score=-0.09 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rD+KpJTr24kC for <homenet@ietfa.amsl.com>; Tue,  1 Nov 2011 01:14:34 -0700 (PDT)
Received: from tyo202.gate.nec.co.jp (TYO202.gate.nec.co.jp [202.32.8.206]) by ietfa.amsl.com (Postfix) with ESMTP id 0CDAB21F8B25 for <homenet@ietf.org>; Tue,  1 Nov 2011 01:14:33 -0700 (PDT)
Received: from mailgate3.nec.co.jp ([10.7.69.197]) by tyo202.gate.nec.co.jp (8.13.8/8.13.4) with ESMTP id pA18EWAE026796;  Tue, 1 Nov 2011 17:14:32 +0900 (JST)
Received: (from root@localhost) by mailgate3.nec.co.jp (8.11.7/3.7W-MAILGATE-NEC) id pA18EVj25424; Tue, 1 Nov 2011 17:14:31 +0900 (JST)
Received: from mail01b.kamome.nec.co.jp (mail01b.kamome.nec.co.jp [10.25.43.2]) by mailsv.nec.co.jp (8.13.8/8.13.4) with ESMTP id pA18EUsd006341; Tue, 1 Nov 2011 17:14:30 +0900 (JST)
Received: from kameyata.jp.nec.com ([10.26.220.29] [10.26.220.29]) by mail03.kamome.nec.co.jp with ESMTP id BT-MMP-1795685; Tue, 1 Nov 2011 17:13:40 +0900
Received: from localhost ([10.56.40.24] [10.56.40.24]) by mail.jp.nec.com with ESMTPA id BT-MMP-57007; Tue, 1 Nov 2011 17:13:40 +0900
Date: Tue, 01 Nov 2011 17:13:40 +0900 (JST)
Message-Id: <20111101.171340.45502108.kitamura@da.jp.nec.com>
To: homenet@ietf.org
From: Hiroshi KITAMURA <kitamura@da.jp.nec.com>
In-Reply-To: <20111024070345.29957.24680.idtracker@ietfa.amsl.com>
References: <20111024070345.29957.24680.idtracker@ietfa.amsl.com>
X-Mailer: Mew version 5.2 on Emacs 21.4 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: kitamura@da.jp.nec.com, ata@info.eng.osaka-cu.ac.jp
Subject: [homenet] Requested Agenda item (Re: I-D Action: draft-kitamura-ipv6-auto-name-00.txt)
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 01 Nov 2011 08:14:34 -0000

Dear All,

This is requested agenda item to WG co-chairs.
Chairs suggested us to send e-mail to the mailing list, 
and we follow the suggestion and send e-mail here.

As below attached announcement mail shows, this I-D discusses on NAME
issues for IPv6 addresses. We believe proposed ideas will strongly
contribute to solve some parts of NAME related issues of the Homenet
architecture.

So, could you please read this I-D, and let us know your comments.
Your comments are welcome.
We will be able to answer them at Taipei meeting session.  

Since this I-D is version -00.txt, some parts of this I-D have not
been completed yet. After we get feed back comments from you, we will
complete this.

Thank you.

Regards,
Hiroshi


From: internet-drafts@ietf.org
Subject: I-D Action: draft-kitamura-ipv6-auto-name-00.txt
Date: Mon, 24 Oct 2011 00:03:45 -0700
Message-ID: <20111024070345.29957.24680.idtracker@ietfa.amsl.com>

> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> 
> 	Title           : Corresponding Auto Names for IPv6 Addresses
> 	Author(s)       : Hiroshi Kitamura
>                           Shingo Ata
> 	Filename        : draft-kitamura-ipv6-auto-name-00.txt
> 	Pages           : 14
> 	Date            : 2011-10-24
> 
>    This document discusses notion and actual mechanisms of
>    "Corresponding Auto Names" for IPv6 Addresses. With this mechanism,
>    all IPv6 addresses (even if they are link-local scoped addresses)
>    can obtain their own Names, and it will be able to use Names
>    anywhere instead of IPv6 Addresses.
> 
>    IPv6 address is too long and complicated to remember, and it is
>    very nuisance thing to type a literal IPv6 address manually as an
>    argument of applications. Also, it is very difficult for human
>    beings to tell which IPv6 address is set to which actual IPv6 node.
>    In this sense, literal IPv6 address information can be called
>    meaningless information for human beings.
> 
>    In order to solve above problems and to make the information
>    meaningful, mechanisms called Corresponding Auto Names for IPv6
>    addresses is introduced. They will become gentle information for
>    human beings. By applying a simple naming rule to the Auto Names
>    (e.g., use the same name-prefix for IPv6 addresses that are set to
>    the same interface (node)), this will contribute to help people to
>    understand which IPv6 address / Name indicates which actual IPv6
>    node.
> 
> 
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-kitamura-ipv6-auto-name-00.txt
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> This Internet-Draft can be retrieved at:
> ftp://ftp.ietf.org/internet-drafts/draft-kitamura-ipv6-auto-name-00.txt
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

From mcr@sandelman.ca  Tue Nov  1 07:50:59 2011
Return-Path: <mcr@sandelman.ca>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B81421F9966 for <homenet@ietfa.amsl.com>; Tue,  1 Nov 2011 07:50:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.954
X-Spam-Level: 
X-Spam-Status: No, score=-1.954 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kKIFGfGFespW for <homenet@ietfa.amsl.com>; Tue,  1 Nov 2011 07:50:58 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id 6F35D21F9965 for <homenet@ietf.org>; Tue,  1 Nov 2011 07:50:57 -0700 (PDT)
Received: from marajade.sandelman.ca (office.nvanjou.isp.novavision.ca [38.102.81.98]) by relay.sandelman.ca (Postfix) with ESMTPS id 8D7433418E for <homenet@ietf.org>; Tue,  1 Nov 2011 10:49:39 -0400 (EDT)
Received: by marajade.sandelman.ca (Postfix, from userid 179) id C33FB98B2E; Tue,  1 Nov 2011 10:51:54 -0400 (EDT)
Received: from marajade.sandelman.ca (localhost [127.0.0.1]) by marajade.sandelman.ca (Postfix) with ESMTP id BDC97980ED for <homenet@ietf.org>; Tue,  1 Nov 2011 10:51:54 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: homenet@ietf.org
In-Reply-To: <4EAF4AD5.50303@cisco.com>
References: <20111029153139.31713.66593.idtracker@ietfa.amsl.com> <4EAF4AD5.50303@cisco.com>
X-Mailer: MH-E 8.1; nmh 1.3-dev; XEmacs 21.4 (patch 22)
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Tue, 01 Nov 2011 10:51:54 -0400
Message-ID: <4257.1320159114@marajade.sandelman.ca>
Sender: mcr@sandelman.ca
Subject: [homenet] hierarchial assignment in draft-chakrabarti-homenet-prefix-alloc
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 01 Nov 2011 14:50:59 -0000

--=-=-=
Content-Transfer-Encoding: quoted-printable


I read draft-chakrabarti-homenet-prefix-alloc as being the simplest
thing that might work.  We discussed this hierarchy at the interim
meeting, and we were not generally happy with it, as it seemed we were
restricting IPv6 to fail whenever IPv4 would fail, when we felt we could
in fact do better.=20=20

We further felt that the incidence of users plugging in the wrong port
(plugging the "LAN" into the uplink on the CER), was sufficiently common
that it would be nice to have a system that was immune to this.

The analysis that 3 bits of a /56 gives us essentially three levels of
delegation, and that's probably enough for most places.=20=20

The discussion in section 12 is a bit satisfying that actually IPv6 can
operate better than IPv4.  Figure 6 is likely quite common, particularly
when one considers that Network C is wireless and Network C/D (router Y)
is in fact wired, and the culprit is a PC in bridging mode.  This
happens ridiculously often.  The worst affects in figure 6 in IPv4 are
due to IP address clashes.  If equipment X and Y are from different
vendors, then the IPv4 address clash often goes away, and I've heard lots
of anecdotal stories from less technical friends about how you can never
have more than one router from the same vendor.

That pathology described in figure 7, is, I think, less frequent, simply
because having that many layers is uncommon.  I want to point out that
if router 4 does in fact pict router 3 as it's uplink, router 4 will be
the fourth level, and it will just barely get one /64, in the /56
divided by 3 bits...  The heuristic suggested at the end may be well
worthwhile, as it would make R4 prefer R1.

Some detailed comments:

From=20draft-chakrabarti-homenet-prefix-alloc:

>3.  Conceptual model of a Basic Home Router
>
>   A key assumption we make is that a Basic Home Router has a designated
>   uplink port.  Today such home routers include IPv4 NAT functionality
>   and as IPv6 support is added the goal is to not require IPv6 NAT
>   functionality but instead rely on different prefixes being allocated
>   to different links.

Can we change this text to say:

    A key assumption we make is that a Basic Home Router the ability to
    designate a port as the uplink port.  This may be by external
    convention (a label), or via a to-be-determined heuristic.
    Today such home routers include IPv4 NAT functionality...

(and  s/port is colors/port is colored/)

section 11:
>   The only exception to this is a CER which has been
>   configured to generate and advertise a ULA prefix even when the ISP
>   connection is down; such a CER would sub-delegate and advertise the
>   ULA prefix in parallel with requesting a prefix delegation from the
>   ISP.

What I understand is that a CER which is in factory default
configuration (therefore has never generated a ULA before), which never
connects to an ISP, will not generate a ULA without a manual configuration.
Configuration of the CER would have to be done by link-local address.

I had to write the above sentence out to convince myself that this was an
acceptable compromise.

Why would a CER which has generated a ULA care of it's never connected
to an ISP again?=20=20








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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iQEVAwUATrAHioCLcPvd0N1lAQJOwwgAmM1EuwU6cg6bosnyb2uwrFHw6sNofP+U
dxLkR4qJ8UwKmIgcvcv1dAZzAW46ALh8MCurv0940RgPum/cLhNeDCIrE0xYUWGq
jJuVtlMeAxXCs+DoueUHsxPTfS6Az9I4b8DrOmlHjpSPgu8fuP9veAGXQAbFEvSg
D352gF8pGducwhcfCs+hAiLPRUS3QY7eshHpsEG27jbZsgiRkosuV4iDE/0xFb5S
AYSGNjYOcoLtgEN6izlS5RJUGs0pJkdcbQY/38K2Cl0rzYcHVfcOJUPHvHxgOhpE
R3ViASXOQ6WqQS0qxIXA0TXbcK7Qesh8ahBQBggVyshGQHXohf0gxQ==
=eVqd
-----END PGP SIGNATURE-----
--=-=-=--

From Ray.Bellis@nominet.org.uk  Wed Nov  2 04:47:15 2011
Return-Path: <Ray.Bellis@nominet.org.uk>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FB3111E8148 for <homenet@ietfa.amsl.com>; Wed,  2 Nov 2011 04:47:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.544
X-Spam-Level: 
X-Spam-Status: No, score=-9.544 tagged_above=-999 required=5 tests=[AWL=1.054,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZcEXrJTlP2AV for <homenet@ietfa.amsl.com>; Wed,  2 Nov 2011 04:47:14 -0700 (PDT)
Received: from mx4.nominet.org.uk (mx4.nominet.org.uk [213.248.199.24]) by ietfa.amsl.com (Postfix) with ESMTP id 324CB11E8083 for <homenet@ietf.org>; Wed,  2 Nov 2011 04:47:13 -0700 (PDT)
DomainKey-Signature: s=main.dk.nominet.selector; d=nominet.org.uk; c=nofws; q=dns; h=X-IronPort-AV:Received:Received:From:To:Subject: Thread-Topic:Thread-Index:Date:Message-ID:Accept-Language: Content-Language:X-MS-Has-Attach:X-MS-TNEF-Correlator: Content-Type:MIME-Version; b=yseJozCbnxcgAv3Kx0SZzre06fy4I3Wxil7V1Lb3UlsWNi06/X7ReM8z TstF8CLM5ryS5SRUd0EL8vrZBAYZu8ZpYxXiA03nFn2kD62kBAMytbXPQ pT+Lzx0QvHjmOvV;
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nominet.org.uk; i=Ray.Bellis@nominet.org.uk; q=dns/txt; s=main.dkim.nominet.selector; t=1320234434; x=1351770434; h=from:sender:reply-to:subject:date:message-id:to:cc: mime-version:content-transfer-encoding:content-id: content-description:resent-date:resent-from:resent-sender: resent-to:resent-cc:resent-message-id:in-reply-to: references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:list-owner:list-archive; z=From:=20Ray=20Bellis=20<Ray.Bellis@nominet.org.uk> |Subject:=20IETF82=20Homenet=20WG=20-=20Provisional=20Age nda|Date:=20Wed,=202=20Nov=202011=2011:47:08=20+0000 |Message-ID:=20<690D2821-D6FD-46AE-83C5-0B24BE440C7E@nomi net.org.uk>|To:=20"homenet@ietf.org"=20<homenet@ietf.org> |MIME-Version:=201.0; bh=rmwB9KVRLF9KzqmdGr9690LDXDiHNZtveaKIbobNot0=; b=wqxN6kWRT1OeF/q7ZqAvvbuSEXjvTamY/2VuC3nHX4VJoJuyapv+PMr0 ESzzaobzNf7n7hNHsZV4MlApxehsawO8BFp9ii09VZboBppZmndqyTUJS 6keauCrG2tgHZVW;
X-IronPort-AV: E=Sophos;i="4.69,443,1315177200"; d="scan'208,217";a="29292532"
Received: from wds-exc2.okna.nominet.org.uk ([213.248.197.145]) by mx4.nominet.org.uk with ESMTP; 02 Nov 2011 11:47:10 +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%19]) with mapi; Wed, 2 Nov 2011 11:47:09 +0000
From: Ray Bellis <Ray.Bellis@nominet.org.uk>
To: "homenet@ietf.org" <homenet@ietf.org>
Thread-Topic: IETF82 Homenet WG - Provisional Agenda
Thread-Index: AQHMmVUmc3wuiejDzkiUOBsrNZFkng==
Date: Wed, 2 Nov 2011 11:47:08 +0000
Message-ID: <690D2821-D6FD-46AE-83C5-0B24BE440C7E@nominet.org.uk>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_690D2821D6FD46AE83C50B24BE440C7Enominetorguk_"
MIME-Version: 1.0
Subject: [homenet] IETF82 Homenet WG - Provisional Agenda
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 02 Nov 2011 11:47:15 -0000

--_000_690D2821D6FD46AE83C50B24BE440C7Enominetorguk_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

The provisional agenda for our session at IETF 82 is now online at http://w=
ww.ietf.org/proceedings/82/agenda/homenet.txt and included below.

The longest slot is for draft-chown-homenet-arch since that's the document =
that we expect to become draft-ietf-homenet-arch very shortly after IETF 82=
 and which includes all of the recent input from the Interim meeting and fr=
om the list.

The remaining time is for presentations on a number of drafts that have bee=
n submitted to the WG, and a couple of others that are closely related.

We have only been able to reserve 10 minutes each for those presentations a=
s we only have a single 2.5hr session.

That's actually a longer session than we requested, but I sincerely hope th=
at we don't find ourselves ever needing more than one!

If we have allocated you time but you are unable to present, please either =
nominate a proxy to present for you, or let us know ASAP so we can update t=
he agenda.

Ray and Mark

--8<--8<--

IETF 82
Homenet Working Group
15th November 2011

09:00 - 09:10  Note Well, Jabber Relay, Note taker(s)

09:10 - 10:00  Homenet Architecture

    draft-chown-homenet-arch-01 (Tim Chown / Jari Arkko)

10:00 - 10:35  Prefix Assignment

    Introduction (Ole Troan)
    draft-chakrabarti-homenet-prefix-alloc-00 (Eric Nordmark)
    draft-baker-homenet-prefix-assignment-00 (Fred Baker)
    draft-arkko-homenet-prefix-assignment-01 (Jari Arkko)

10:35 - 11:00  Routing

    Intro (Chairs)
    draft-acee-ospf-ospv3-autoconfig-00 (Acee Lindem)
    draft-howard-up-pio-00 (Lee Howard - draft not on the I-D tracker)

11:00 - 11:10  Security

    draft-vyncke-advanced-ipv6-security-03 (Eric Vyncke)

11:10 - 11:30  Naming and Service Discovery

    draft-kitamura-ipv6-auto-name-00 (Hiroshi Kitamura)
    draft-haddad-homenet-gateway-visibility-00 (Wassim Haddad)

11:30  Close

--8<--8<--


--_000_690D2821D6FD46AE83C50B24BE440C7Enominetorguk_
Content-Type: text/html; charset="us-ascii"
Content-ID: <c1ef30d1-0cb5-430f-88b8-dfe885a57467>
Content-Transfer-Encoding: quoted-printable

<html><head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -we=
bkit-line-break: after-white-space; ">The provisional agenda for our sessio=
n at IETF 82 is now online&nbsp;at&nbsp;<a href=3D"http://www.ietf.org/proc=
eedings/82/agenda/homenet.txt">http://www.ietf.org/proceedings/82/agenda/ho=
menet.txt</a>&nbsp;and included below.<div><br></div><div>The longest slot =
is for draft-chown-homenet-arch since that's the document that we expect to=
 become draft-ietf-homenet-arch very shortly after IETF 82 and which includ=
es all of the recent input from the Interim meeting and from the list.</div=
><div><br></div><div>The remaining time is for presentations on&nbsp;a numb=
er of drafts that have been submitted to the WG, and a couple of others tha=
t are closely related.</div><div><br></div><div>We have only been able to r=
eserve 10 minutes each for those presentations as we only have a single 2.5=
hr session.</div><div><br></div><div><div>That's actually a longer session =
than we requested, but I sincerely hope that we don't find ourselves ever n=
eeding more than one!</div></div><div><br></div><div><div><div>If we have a=
llocated you time but you are unable to present, please either nominate a p=
roxy to present for you, or let us know ASAP so we can update the agenda.</=
div></div><div><br></div></div><div>Ray and Mark</div><div><br></div><div>-=
-8&lt;--8&lt;--</div><div><pre style=3D"color: rgb(0, 0, 0); font-style: no=
rmal; font-variant: normal; font-weight: normal; letter-spacing: normal; li=
ne-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; =
text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-size-adjus=
t: auto; -webkit-text-stroke-width: 0px; word-wrap: break-word; white-space=
: pre-wrap; "><span class=3D"Apple-style-span">IETF 82
Homenet Working Group
15th November 2011

09:00 - 09:10  Note Well, Jabber Relay, Note taker(s)

09:10 - 10:00  Homenet Architecture=20

    draft-chown-homenet-arch-01 </span>(Tim Chown / Jari Arkko)<div><br></d=
iv><span class=3D"Apple-style-span">10:00 - 10:35  Prefix Assignment

    Introduction (Ole Troan)
    draft-chakrabarti-homenet-prefix-alloc-00 (Eric Nordmark)
    draft-baker-homenet-prefix-assignment-00 (Fred Baker)
    draft-arkko-homenet-prefix-assignment-01 (Jari Arkko)

10:35 - 11:00  Routing

    Intro (Chairs)       =20
    draft-acee-ospf-ospv3-autoconfig-00 (Acee Lindem)
    draft-howard-up-pio-00 (Lee Howard - draft not on the I-D tracker)

11:00 - 11:10  Security=20

    draft-vyncke-advanced-ipv6-security-03 (Eric Vyncke)

11:10 - 11:30  Naming and Service Discovery

    draft-kitamura-ipv6-auto-name-00 (Hiroshi Kitamura)
    draft-haddad-homenet-gateway-visibility-00 (Wassim Haddad)

11:30  Close</span></pre><div>--8&lt;--8&lt;--</div></div><div><br></div></=
body></html>=

--_000_690D2821D6FD46AE83C50B24BE440C7Enominetorguk_--

From jyrki.soini@teliasonera.com  Wed Nov  2 06:20:20 2011
Return-Path: <jyrki.soini@teliasonera.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DAD3D21F8C4B for <homenet@ietfa.amsl.com>; Wed,  2 Nov 2011 06:20:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DH9RjWlP782T for <homenet@ietfa.amsl.com>; Wed,  2 Nov 2011 06:20:20 -0700 (PDT)
Received: from smtp.tele.fi (smtp.tele.fi [192.89.123.25]) by ietfa.amsl.com (Postfix) with ESMTP id 3F90A21F8C97 for <homenet@ietf.org>; Wed,  2 Nov 2011 06:20:20 -0700 (PDT)
X-Originating-Ip: [131.177.70.25]
Received: from smtp.extra.sonera.fi (smtp.extra.sonera.fi [131.177.70.25]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.tele.fi (Postfix) with ESMTP id AEAC02856 for <homenet@ietf.org>; Wed,  2 Nov 2011 15:20:11 +0200 (EET)
Received: from smtp.dave.sonera.fi (smtp.dave.sonera.fi [131.177.120.25]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.extra.sonera.fi (Postfix) with ESMTP id 8012E1EE9E7 for <homenet@ietf.org>; Wed,  2 Nov 2011 15:19:46 +0200 (EET)
Received: from [131.177.116.170] (ws870.secureuser.sonera.fi [131.177.116.170]) by smtp.dave.sonera.fi (Postfix) with ESMTP id 41F655803A for <homenet@ietf.org>; Wed,  2 Nov 2011 15:20:10 +0200 (EET)
Message-ID: <4EB14389.1010608@teliasonera.com>
Date: Wed, 02 Nov 2011 15:20:09 +0200
From: Jyrki Soini <jyrki.soini@teliasonera.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:8.0) Gecko/20111019 Thunderbird/8.0
MIME-Version: 1.0
To: homenet@ietf.org
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [homenet] Router movement handling in draft-arkko-homenet-prefix-assignment-01.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 02 Nov 2011 13:20:21 -0000

I read the new version draft-arkko-homenet-prefix-assignment-01.txt
and like the approach.
However I have a question on how the router movement is to be handled.

For instance initial the topology:

                                    CE router
                                       |
                                       P0
                        R1 +-----------+------------+ R2
                         |                             |
                        P1                            P2
                         |
                        R3

and after the move of R3

                                    CE router
                                       |
                                       P0
                        R1 +-----------+------------+ R2
                         |                             |
                        P1                            P2
                                                       (
                                                      R3

After movement R3 has the stored previously assigned prefix P1 for the 
interface but it also learns the P2 prefix from router R2. P3 has the 
numerically highest OSPFv3 router ID of all routers and therefore 
decides the prefix to be used on the link.

 From the rules I tend to believe R3 would learn and start using P2, if 
it is booting up after movement.

BUT: How is the movement detected in case there has been switches 
between the routers and no router is booted nor even any interface 
status has gone down? Would R3 insist on using P1 on the link even 
though it is also assigned by R1 on its interface?
And in that case, what would happen to the link on R1 where P1 is also 
assigned?

Should the prefix assignment be considered each time a OSPFv3 neighbor 
change is detected?

--
Jyrki

From lee.howard@twcable.com  Wed Nov  2 07:36:36 2011
Return-Path: <lee.howard@twcable.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E21A121F8CBD for <homenet@ietfa.amsl.com>; Wed,  2 Nov 2011 07:36:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.749
X-Spam-Level: 
X-Spam-Status: No, score=-0.749 tagged_above=-999 required=5 tests=[AWL=-0.286, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zkrG9LnG0AhS for <homenet@ietfa.amsl.com>; Wed,  2 Nov 2011 07:36:35 -0700 (PDT)
Received: from cdpipgw02.twcable.com (cdpipgw02.twcable.com [165.237.59.23]) by ietfa.amsl.com (Postfix) with ESMTP id DCE5B21F8CA7 for <homenet@ietf.org>; Wed,  2 Nov 2011 07:36:33 -0700 (PDT)
X-SENDER-IP: 10.136.163.12
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.69,443,1315195200";  d="txt'?scan'208";a="277304097"
Received: from unknown (HELO PRVPEXHUB03.corp.twcable.com) ([10.136.163.12]) by cdpipgw02.twcable.com with ESMTP/TLS/RC4-MD5; 02 Nov 2011 10:32:17 -0400
Received: from PRVPEXVS03.corp.twcable.com ([10.136.163.27]) by PRVPEXHUB03.corp.twcable.com ([10.136.163.12]) with mapi; Wed, 2 Nov 2011 10:36:31 -0400
From: "Howard, Lee" <lee.howard@twcable.com>
To: "homenet@ietf.org Group" <homenet@ietf.org>
Date: Wed, 2 Nov 2011 10:36:30 -0400
Thread-Topic: another routing option
Thread-Index: AcyZbM79gx9G/rcMSI2paq3Nbnn4cQ==
Message-ID: <DCC302FAA9FE5F4BBA4DCAD46569377914517EE5FD@PRVPEXVS03.corp.twcable.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/mixed; boundary="_002_DCC302FAA9FE5F4BBA4DCAD46569377914517EE5FDPRVPEXVS03cor_"
MIME-Version: 1.0
Subject: [homenet] another routing option
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 02 Nov 2011 14:36:37 -0000

--_002_DCC302FAA9FE5F4BBA4DCAD46569377914517EE5FDPRVPEXVS03cor_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I've said that I don't think we need a full dynamic routing protocol.  Ther=
e are other options for discovering an available path.  To stimulate creati=
ve thinking, I've written a draft proposing one alternative that should be =
light to implement in home gateways: http://www.asgard.org/images/draft-how=
ard-up-pio-00.txt
If it is interesting, there's more work to be done on it; I could publish i=
t after the pre-meeting publication blackout ends.

Lee




This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

--_002_DCC302FAA9FE5F4BBA4DCAD46569377914517EE5FDPRVPEXVS03cor_
Content-Type: text/plain; name="draft-howard-up-pio-00.txt"
Content-Description: draft-howard-up-pio-00.txt
Content-Disposition: attachment; filename="draft-howard-up-pio-00.txt";
	size=24339; creation-date="Thu, 27 Oct 2011 21:24:08 GMT";
	modification-date="Thu, 27 Oct 2011 21:40:54 GMT"
Content-Transfer-Encoding: base64

CgoKTmV0d29yayBXb3JraW5nIEdyb3VwICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgTC4gSG93YXJkCkludGVybmV0LURyYWZ0ICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICBUaW1lIFdhcm5lciBDYWJsZQpJbnRlbmRlZCBzdGF0dXM6IFN0YW5k
YXJkcyBUcmFjayAgICAgICAgICAgICAgICAgICAgICAgIE9jdG9iZXIgMjcsIDIwMTEKRXhwaXJl
czogQXByaWwgMjksIDIwMTIKCgogICAgICAgICAgVGhlIFVQIFBJTyBGaWVsZDogRmluZGluZyBV
cCBpbiBhbiBVbm1hbmFnZWQgTmV0d29yawogICAgICAgICAgICAgICAgICAgICAgICAgZHJhZnQt
aG93YXJkLXVwLXBpby0wMAoKQWJzdHJhY3QKCiAgIEl0IGlzIGRpZmZpY3VsdCB0byBmaW5kIGEg
cGF0aCB0aHJvdWdoIGFuIHVubWFuYWdlZCBuZXR3b3JrIHdpdGgKICAgbXVsdGlwbGUgcm91dGVy
cy4gIFRoaXMgZG9jdW1lbnQgZGVzY3JpYmVzIGEgbmV3IFByZWZpeCBJbmZvcm1hdGlvbgogICBP
cHRpb24gZmllbGQgd2hpY2ggY2FuIHByb3ZpZGUgaW5mb3JtYXRpb24gdG8gcm91dGVycyB0byBm
aW5kIGEgcGF0aC4KClN0YXR1cyBvZiB0aGlzIE1lbW8KCiAgIFRoaXMgSW50ZXJuZXQtRHJhZnQg
aXMgc3VibWl0dGVkIGluIGZ1bGwgY29uZm9ybWFuY2Ugd2l0aCB0aGUKICAgcHJvdmlzaW9ucyBv
ZiBCQ1AgNzggYW5kIEJDUCA3OS4KCiAgIEludGVybmV0LURyYWZ0cyBhcmUgd29ya2luZyBkb2N1
bWVudHMgb2YgdGhlIEludGVybmV0IEVuZ2luZWVyaW5nCiAgIFRhc2sgRm9yY2UgKElFVEYpLiAg
Tm90ZSB0aGF0IG90aGVyIGdyb3VwcyBtYXkgYWxzbyBkaXN0cmlidXRlCiAgIHdvcmtpbmcgZG9j
dW1lbnRzIGFzIEludGVybmV0LURyYWZ0cy4gIFRoZSBsaXN0IG9mIGN1cnJlbnQgSW50ZXJuZXQt
CiAgIERyYWZ0cyBpcyBhdCBodHRwOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZHJhZnRzL2N1cnJl
bnQvLgoKICAgSW50ZXJuZXQtRHJhZnRzIGFyZSBkcmFmdCBkb2N1bWVudHMgdmFsaWQgZm9yIGEg
bWF4aW11bSBvZiBzaXggbW9udGhzCiAgIGFuZCBtYXkgYmUgdXBkYXRlZCwgcmVwbGFjZWQsIG9y
IG9ic29sZXRlZCBieSBvdGhlciBkb2N1bWVudHMgYXQgYW55CiAgIHRpbWUuICBJdCBpcyBpbmFw
cHJvcHJpYXRlIHRvIHVzZSBJbnRlcm5ldC1EcmFmdHMgYXMgcmVmZXJlbmNlCiAgIG1hdGVyaWFs
IG9yIHRvIGNpdGUgdGhlbSBvdGhlciB0aGFuIGFzICJ3b3JrIGluIHByb2dyZXNzLiIKCiAgIFRo
aXMgSW50ZXJuZXQtRHJhZnQgd2lsbCBleHBpcmUgb24gQXByaWwgMjksIDIwMTIuCgpDb3B5cmln
aHQgTm90aWNlCgogICBDb3B5cmlnaHQgKGMpIDIwMTEgSUVURiBUcnVzdCBhbmQgdGhlIHBlcnNv
bnMgaWRlbnRpZmllZCBhcyB0aGUKICAgZG9jdW1lbnQgYXV0aG9ycy4gIEFsbCByaWdodHMgcmVz
ZXJ2ZWQuCgogICBUaGlzIGRvY3VtZW50IGlzIHN1YmplY3QgdG8gQkNQIDc4IGFuZCB0aGUgSUVU
RiBUcnVzdCdzIExlZ2FsCiAgIFByb3Zpc2lvbnMgUmVsYXRpbmcgdG8gSUVURiBEb2N1bWVudHMK
ICAgKGh0dHA6Ly90cnVzdGVlLmlldGYub3JnL2xpY2Vuc2UtaW5mbykgaW4gZWZmZWN0IG9uIHRo
ZSBkYXRlIG9mCiAgIHB1YmxpY2F0aW9uIG9mIHRoaXMgZG9jdW1lbnQuICBQbGVhc2UgcmV2aWV3
IHRoZXNlIGRvY3VtZW50cwogICBjYXJlZnVsbHksIGFzIHRoZXkgZGVzY3JpYmUgeW91ciByaWdo
dHMgYW5kIHJlc3RyaWN0aW9ucyB3aXRoIHJlc3BlY3QKICAgdG8gdGhpcyBkb2N1bWVudC4gIENv
ZGUgQ29tcG9uZW50cyBleHRyYWN0ZWQgZnJvbSB0aGlzIGRvY3VtZW50IG11c3QKICAgaW5jbHVk
ZSBTaW1wbGlmaWVkIEJTRCBMaWNlbnNlIHRleHQgYXMgZGVzY3JpYmVkIGluIFNlY3Rpb24gNC5l
IG9mCiAgIHRoZSBUcnVzdCBMZWdhbCBQcm92aXNpb25zIGFuZCBhcmUgcHJvdmlkZWQgd2l0aG91
dCB3YXJyYW50eSBhcwogICBkZXNjcmliZWQgaW4gdGhlIFNpbXBsaWZpZWQgQlNEIExpY2Vuc2Uu
CgogICBUaGlzIGRvY3VtZW50IG1heSBjb250YWluIG1hdGVyaWFsIGZyb20gSUVURiBEb2N1bWVu
dHMgb3IgSUVURgoKCgpIb3dhcmQgICAgICAgICAgICAgICAgICAgRXhwaXJlcyBBcHJpbCAyOSwg
MjAxMiAgICAgICAgICAgICAgICAgW1BhZ2UgMV0KDApJbnRlcm5ldC1EcmFmdCAgICAgICAgICAg
ICAgICAgICBVUCBQSU8gICAgICAgICAgICAgICAgICAgICBPY3RvYmVyIDIwMTEKCgogICBDb250
cmlidXRpb25zIHB1Ymxpc2hlZCBvciBtYWRlIHB1YmxpY2x5IGF2YWlsYWJsZSBiZWZvcmUgTm92
ZW1iZXIKICAgMTAsIDIwMDguICBUaGUgcGVyc29uKHMpIGNvbnRyb2xsaW5nIHRoZSBjb3B5cmln
aHQgaW4gc29tZSBvZiB0aGlzCiAgIG1hdGVyaWFsIG1heSBub3QgaGF2ZSBncmFudGVkIHRoZSBJ
RVRGIFRydXN0IHRoZSByaWdodCB0byBhbGxvdwogICBtb2RpZmljYXRpb25zIG9mIHN1Y2ggbWF0
ZXJpYWwgb3V0c2lkZSB0aGUgSUVURiBTdGFuZGFyZHMgUHJvY2Vzcy4KICAgV2l0aG91dCBvYnRh
aW5pbmcgYW4gYWRlcXVhdGUgbGljZW5zZSBmcm9tIHRoZSBwZXJzb24ocykgY29udHJvbGxpbmcK
ICAgdGhlIGNvcHlyaWdodCBpbiBzdWNoIG1hdGVyaWFscywgdGhpcyBkb2N1bWVudCBtYXkgbm90
IGJlIG1vZGlmaWVkCiAgIG91dHNpZGUgdGhlIElFVEYgU3RhbmRhcmRzIFByb2Nlc3MsIGFuZCBk
ZXJpdmF0aXZlIHdvcmtzIG9mIGl0IG1heQogICBub3QgYmUgY3JlYXRlZCBvdXRzaWRlIHRoZSBJ
RVRGIFN0YW5kYXJkcyBQcm9jZXNzLCBleGNlcHQgdG8gZm9ybWF0CiAgIGl0IGZvciBwdWJsaWNh
dGlvbiBhcyBhbiBSRkMgb3IgdG8gdHJhbnNsYXRlIGl0IGludG8gbGFuZ3VhZ2VzIG90aGVyCiAg
IHRoYW4gRW5nbGlzaC4KCgpUYWJsZSBvZiBDb250ZW50cwoKICAgMS4gIEludHJvZHVjdGlvbiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICAzCiAgICAg
MS4xLiAgUmVxdWlyZW1lbnRzIExhbmd1YWdlICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAgMwogICAyLiAgRm9ybWF0IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDMKICAgMy4gIFVzZSBDYXNlcyAgLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICA0CiAgICAgMy4xLiAgRGVm
YXVsdCBSb3V0ZSAgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAg
NAogICAgIDMuMi4gIFdhbGxlZCBHYXJkZW4gIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gIDQKICAgICAzLjMuICBVTEEgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuICA0CiAgICAgMy40LiAgRGVsZWdhdGVkIFBy
ZWZpeCAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgNQogICA0LiAg
SW1wbGVtZW50YXRpb24gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gIDUKICAgICA0LjEuICBIb3N0IEJlaGF2aW9yICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuICA1CiAgICAgNC4yLiAgVGllIEJyZWFraW5nIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgNQogICAgIDQuMy4gIE11bHRp
cGxlIFBhdGhzIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDUK
ICAgICA0LjQuICBSb3V0ZSBXaXRoZHJhd2FsIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuICA2CiAgIDUuICBFeGFtcGxlcyAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgNgogICA2LiAgRXZhbHVhdGlvbiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDgKICAgNy4gIEFk
ZGl0aW9uYWwgV29yayBSZXF1aXJlZCAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIDEwCiAgIDguICBBbHRlcm5hdGl2ZXMgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAxMAogICA5LiAgU2VjdXJpdHkgQ29uc2lkZXJhdGlvbnMgIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gMTAKICAgMTAuIElBTkEgQ29uc2lk
ZXJhdGlvbnMgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIDEwCiAg
IDExLiBSZWZlcmVuY2VzIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAxMQogICAgIDExLjEuIE5vcm1hdGl2ZSBSZWZlcmVuY2VzIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gMTEKICAgICAxMS4yLiBJbmZvcm1hdGl2ZSBSZWZl
cmVuY2VzIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIDExCiAgIEF1dGhvcidz
IEFkZHJlc3MgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAxMQoKCgoKCgoKCgoKCgoKCkhvd2FyZCAgICAgICAgICAgICAgICAgICBFeHBpcmVzIEFwcmls
IDI5LCAyMDEyICAgICAgICAgICAgICAgICBbUGFnZSAyXQoMCkludGVybmV0LURyYWZ0ICAgICAg
ICAgICAgICAgICAgIFVQIFBJTyAgICAgICAgICAgICAgICAgICAgIE9jdG9iZXIgMjAxMQoKCjEu
ICBJbnRyb2R1Y3Rpb24KCiAgIFRoaXMgZG9jdW1lbnQgZGVzY3JpYmVzIGEgbmV3IFByZWZpeCBJ
bmZvcm1hdGlvbiBPcHRpb24gZmllbGQgdG8gYmUKICAgdXNlZCBpbiB1bm1hbmFnZWQgbmV0d29y
a3MgKHN1Y2ggYXMgaG9tZSBuZXR3b3JrcykgdG8gZmluZCBhIHBhdGggdG8KICAgYSBnaXZlbiBw
cmVmaXguICBUaGlzIFBJTyBmaWVsZCBpcyBub3QgaW50ZW5kZWQgdG8gcmVwbGFjZSBkeW5hbWlj
CiAgIHJvdXRpbmcgcHJvdG9jb2xzLCBhbmQgd2lsbCBub3QgZmluZCB0aGUgYmVzdCBwYXRoIHRv
IGEgZ2l2ZW4KICAgZGVzdGluYXRpb24sIHRob3VnaCBpdCBjYW4gcHJvdmlkZSB1c2VmdWwgaW5m
b3JtYXRpb24gdG8gcm91dGVycy4KCjEuMS4gIFJlcXVpcmVtZW50cyBMYW5ndWFnZQoKICAgVGhl
IGtleSB3b3JkcyAiTVVTVCIsICJNVVNUIE5PVCIsICJSRVFVSVJFRCIsICJTSEFMTCIsICJTSEFM
TCBOT1QiLAogICAiU0hPVUxEIiwgIlNIT1VMRCBOT1QiLCAiUkVDT01NRU5ERUQiLCAiTUFZIiwg
YW5kICJPUFRJT05BTCIgaW4gdGhpcwogICBkb2N1bWVudCBhcmUgdG8gYmUgaW50ZXJwcmV0ZWQg
YXMgZGVzY3JpYmVkIGluIFJGQyAyMTE5LiAgW1JGQzIxMTldLgoKCjIuICBGb3JtYXQKICAgICAg
ICAwICAgICAgICAgICAgICAgICAgIDEgICAgICAgICAgICAgICAgICAgMiAgICAgICAgICAgICAg
ICAgICAzCiAgICAgICAgMCAxIDIgMyA0IDUgNiA3IDggOSAwIDEgMiAzIDQgNSA2IDcgOCA5IDAg
MSAyIDMgNCA1IDYgNyA4IDkgMCAxCiAgICAgICArLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSst
Ky0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKwogICAgICAgfCAgICAgVHlwZSAg
ICAgIHwgICAgTGVuZ3RoICAgICB8IFByZWZpeCBMZW5ndGggfEx8QXxSfFV8IFJzdmQxIHwKICAg
ICAgICstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0r
LSstKy0rLSstKy0rCiAgICAgICB8ICAgICAgICAgICAgICAgICAgICAgICAgIFZhbGlkIExpZmV0
aW1lICAgICAgICAgICAgICAgICAgICAgICAgfAogICAgICAgKy0rLSstKy0rLSstKy0rLSstKy0r
LSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSsKICAgICAgIHwgICAg
ICAgICAgICAgICAgICAgICAgIFByZWZlcnJlZCBMaWZldGltZSAgICAgICAgICAgICAgICAgICAg
ICB8CiAgICAgICArLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSst
Ky0rLSstKy0rLSstKy0rLSstKwogICAgICAgfCBEaXN0YW5jZSAgICAgIHwgICAgICAgICAgIFJl
c2VydmVkMiAgICAgICAgICAgICAgICAgICAgICAgICAgIHwKICAgICAgICstKy0rLSstKy0rLSst
Ky0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rCiAgICAg
ICB8ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgfAogICAgICAgKyAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICsKICAgICAgIHwgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICB8CiAgICAgICArICAgICAg
ICAgICAgICAgICAgICAgICAgICAgIFByZWZpeCAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
KwogICAgICAgfCAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgIHwKICAgICAgICsgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICArCiAgICAgICB8ICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgfAogICAgICAg
Ky0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0r
LSstKy0rLSsKCiAgIFRoZSB1c2Ugb2YgTCBhbmQgQSBiaXRzIGFyZSBzcGVjaWZpZWQgaW4gcmZj
NDg2MS4gIFRoZSB1c2Ugb2YgdGhlIFIKICAgYml0IGlzIHNwZWNpZmllZCBpbiByZmMzNzc1LgoK
ICAgVGhpcyBmb3JtYXQgcmVwcmVzZW50cyB0aGUgZm9sbG93aW5nIGNoYW5nZXMgb3ZlciB0aG9z
ZSBSRkNzOgoKICAgICAgVXBzdHJlYW0gUHJlZml4IChVKSAxLWJpdCByb3V0ZXIgYWRkcmVzcyBm
bGFnLiAgV2hlbiB0aGlzIFVQIGJpdAogICAgICBpcyBzZXQgdG8gMSwgaW5kaWNhdGVzIHRoYXQg
dGhlIHByZWZpeCB3YXMgbGVhcm5lZCwgcmF0aGVyIHRoYW4KICAgICAgY29uZmlndXJlZC4KCiAg
ICAgIFJzdmQxIFJlZHVjZWQgZnJvbSBhIDUtYml0IGZpZWxkIHRvIGEgNC1iaXQgZmllbGQgdG8g
YWNjb3VudCBmb3IKICAgICAgdGhlIGFkZGl0aW9uIG9mIHRoZSBhYm92ZSBiaXQuCgoKCgpIb3dh
cmQgICAgICAgICAgICAgICAgICAgRXhwaXJlcyBBcHJpbCAyOSwgMjAxMiAgICAgICAgICAgICAg
ICAgW1BhZ2UgM10KDApJbnRlcm5ldC1EcmFmdCAgICAgICAgICAgICAgICAgICBVUCBQSU8gICAg
ICAgICAgICAgICAgICAgICBPY3RvYmVyIDIwMTEKCgogICAgICBEaXN0YW5jZSBBbiA4LWJpdCBt
ZXRyaWMgdXNlZCB0byBkZXRlcm1pbmUgZGlzdGFuY2UgYW5kIHByZXZlbnQKICAgICAgbG9vcHMu
CgogICBUaGUgVVAgYml0IGlzIHVzZWQgdG8gZmluZCBhIHBhdGggdGhyb3VnaCBhbiB1bm1hbmFn
ZWQgbmV0d29yay4gIFdoZW4KICAgYSByb3V0ZXIgbGVhcm5zIHByZWZpeCBpbmZvcm1hdGlvbiBm
cm9tIGEgUm91dGVyIEFkdmVydGlzZW1lbnQgd2l0aAogICB0aGUgVVAgYml0IHNlbnQsIHRoZSBy
b3V0ZXIgU0hPVUxEIGFkZCB0aGF0IHByZWZpeCB0byBpdHMgb3duIFJBcy4KICAgV2hlbiBzZW5k
aW5nIFJBcyBjb250YWluaW5nIHRoZSBsZWFybmVkIHByZWZpeCwgaXQgTVVTVCBpbmNyZW1lbnQg
dGhlCiAgIERpc3RhbmNlIHZhbHVlIGJ5IG9uZS4KCgozLiAgVXNlIENhc2VzCgozLjEuICBEZWZh
dWx0IFJvdXRlCgogICBUaGUgbW9zdCBjb21tb24gaW1wbGVtZW50YXRpb24gb2YgdGhpcyBmaWVs
ZCB3b3VsZCBiZSB0aGUKICAgYWR2ZXJ0aXNlbWVudCBvZiBhIGRlZmF1bHQgcm91dGUsIHdoZXJl
IFByZWZpeCBMZW5ndGggPSAwIGFuZCBQcmVmaXgKICAgPSAwLiAgQW4gSW50ZXJuZXQgYWNjZXNz
IHByb3ZpZGVyIGNvdWxkIHVzZSBSb3V0ZXIgQWR2ZXJ0aXNlbWVudHMgdG8KICAgY3VzdG9tZXIg
Z2F0ZXdheXMgd2l0aCB0aGUgVVAgYml0IHNldCwgYW5kIGEgZGlzdGFuY2Ugb2YgMCwgdG8KICAg
aW5kaWNhdGUgdGhlIGJvcmRlciBvZiB0aGUgYWRtaW5pc3RyYXRpdmUgZG9tYWluIGFuZCB0aGUg
ZGVmYXVsdAogICBnYXRld2F5IGZvciB0aGUgY3VzdG9tZXIgYWNjZXNzIHJvdXRlci4gIFRoYXQg
Y3VzdG9tZXIgYWNjZXNzIHJvdXRlciwKICAgaGF2aW5nIGxlYXJuZWQgdGhlIGRlZmF1bHQgZ2F0
ZXdheSwgU0hPVUxEIGFkZCB0aGUgcHJlZml4IHRvIGl0cwogICByb3V0aW5nIHRhYmxlLCB0aGVu
IFNIT1VMRCBpbmNsdWRlIHRoaXMgaW5mb3JtYXRpb24gaW4gaXRzIG93biBSQXMuCiAgIFdoZW4g
dGhlIHJvdXRlciBzZW5kcyBSQXMgaW5jbHVkaW5nIHRoaXMgcHJlZml4LCBpdCBNVVNUIGluY3Jl
bWVudAogICB0aGUgRGlzdGFuY2UgaW4gdGhvc2UgUkFzIHRvIGluZGljYXRlIHRoYXQgaXQgaXMg
b25lIGhvcCBmdXJ0aGVyIHRoYW4KICAgdGhlIG9yaWdpbiBvciB0aGUgcHJlZml4LgoKMy4yLiAg
V2FsbGVkIEdhcmRlbgoKICAgRm9yIGEgbmV0d29yayBwcm92aWRlciB3aG8gZG9lcyBub3QgcHJv
dmlkZSBhIGRlZmF1bHQgcm91dGUsIHRoZSBVUAogICBvcHRpb24gY2FuIGJlIHVzZWQgdG8gaW5k
aWNhdGUgdGhhdCBhIHByZWZpeCBpcyBhdmFpbGFibGUuICBGb3IKICAgaW5zdGFuY2UsIGFuIG9w
ZXJhdG9yIHdobyBvbmx5IHdhbnRlZCB0cmFmZmljIGZvciBpdHMgaG9zdGVkIHNlcnZpY2VzCiAg
IG9uIDIwMDE6ZGI4OjovMzIsIHdvdWxkIHNlbmQgYW4gUkEgZm9yIHRoYXQgcHJlZml4IHRvIHRo
ZSBhY2Nlc3MKICAgZ2F0ZXdheSwgd2l0aCBEaXN0YW5jZT0wLiAgVGhhdCBnYXRld2F5IFNIT1VM
RCBhZGQgdGhlIHByZWZpeCB0byBpdHMKICAgcm91dGluZyB0YWJsZSwgdGhlbiBTSE9VTEQgaW5j
bHVkZSB0aGUgcHJlZml4IGluIGl0cyBvd24gUkFzLCBhbmQKICAgTVVTVCBpbmNyZW1lbnQgdGhl
IERpc3RhbmNlIGluIHRob3NlIFJBcyB0byBpbmRpY2F0ZSB0aGF0IGl0IGlzIG9uZQogICBob3Ag
YXdheSBmcm9tIHRoZSBib3JkZXIuCgozLjMuICBVTEEKCiAgIFVuaXF1ZSBMb2NhbCBBZGRyZXNz
ZXMgbWF5IGJlIHVzZWQgZm9yIGEgdmFyaWV0eSBvZiByZWFzb25zCiAgIFtSRkM2MjA0XS4gIFdo
ZW4gYSByb3V0ZXIgZ2VuZXJhdGVzIGEgVUxBIHByZWZpeCwgaXQgTVVTVCBpbmNsdWRlCiAgIHRo
YXQgcHJlZml4IGluIFJBcy4gIEl0IFNIT1VMRCBpbmNsdWRlIHRoZSBVUCBvcHRpb24gZmllbGQs
IHdpdGggYQogICBEaXN0YW5jZSA9IDAuICBXaGVuIGFub3RoZXIgcm91dGVyIGxlYXJucyB0aGF0
IHByZWZpeCwgaXQgU0hPVUxEIGFkZAogICB0aGUgcHJlZml4IHRvIGl0cyByb3V0aW5nIHRhYmxl
LCB0aGVuIFNIT1VMRCBpbmNsdWRlIHRoZSBwcmVmaXggaW4KICAgaXRzIG93biBSQXMsIGFuZCBN
VVNUIGluY3JlbWVudCB0aGUgRGlzdGFuY2UgaW4gdGhvc2UgUkFzIHRvIGluZGljYXRlCiAgIHRo
YXQgaXQgaXMgb25lIGhvcCBhd2F5IGZyb20gdGhlIGJvcmRlci4KCgoKCgpIb3dhcmQgICAgICAg
ICAgICAgICAgICAgRXhwaXJlcyBBcHJpbCAyOSwgMjAxMiAgICAgICAgICAgICAgICAgW1BhZ2Ug
NF0KDApJbnRlcm5ldC1EcmFmdCAgICAgICAgICAgICAgICAgICBVUCBQSU8gICAgICAgICAgICAg
ICAgICAgICBPY3RvYmVyIDIwMTEKCgozLjQuICBEZWxlZ2F0ZWQgUHJlZml4CgogICBJbiBob21l
IG5ldHdvcmsgc2NlbmFyaW9zLCByb3V0ZXJzIGFyZSBvZnRlbiBhbHNvIERIQ1B2NiBzZXJ2ZXJz
LgogICBXaGVuIGEgZGV2aWNlIGlzIGEgREhDUHY2LVBEIHNlcnZlciwgYW5kIHJlY2VpdmVzIGEg
cHJlZml4IHRvIGJlIHVzZWQKICAgZm9yIGhvc3QgYWRkcmVzcyBhc3NpZ25tZW50cyAocmVnYXJk
bGVzcyBvZiBzZXR0aW5nIG9mIE0tYml0KSwgaWYKICAgdGhhdCBkZXZpY2UgaXMgYWxzbyB0aGUg
cm91dGVyIGZvciB0aGF0IHByZWZpeCwgdGhhdCByb3V0ZXIgYmVjb21lcwogICBhdXRob3JpdGF0
aXZlIGZvciB0aGUgcHJlZml4LiAgIkF1dGhvcml0YXRpdmUgZm9yIHRoZSBwcmVmaXgiIGlzCiAg
IGFuYWxvZ291cyB0byB0aGUgbm90aW9uIG9mIHRoZSAiZGVsZWdhdGluZyByb3V0ZXIiIHJlc3Bv
bmRpbmcgdG8gYQogICByZXF1ZXN0IGZyb20gdGhlICJyZXF1ZXN0aW5nIHJvdXRlciIgcGVyIFtS
RkMzNjMzXS4gIEluIG90aGVyIHdvcmRzLAogICB3aGVuIGEgcm91dGVyIHJlY2VpdmVzIFByZWZp
eCBEZWxlZ2F0aW9uLCBpdCBTSE9VTEQgaW5jbHVkZSB0aGF0CiAgIHByZWZpeCBpbiBpdHMgUkFz
LCBhbmQgU0hPVUxEIHNldCB0aGUgRGlzdGFuY2UgdG8gMC4gIE5vdGUgdGhhdCBvdGhlcgogICB2
YWx1ZXMgYXJlIHBvc3NpYmxlLCBidXQgcmVkdWNlIHRoZSBwb3NzaWJsZSBkaWFtZXRlciBvZiB0
aGUgbmV0d29yay4KCiAgIE5vdGUgdGhhdCBpbiB0aGlzIHdheSwgbW9yZSBzcGVjaWZpYyByb3V0
ZXMgbWF5IGJlIHByb3BhZ2F0ZWQgdGhyb3VnaAogICB0aGUgbmV0d29yayB2aWEgUm91dGVyIEFk
dmVydGlzZW1lbnRzLiAgVGhlIGxvbmdlc3QgbWF0Y2ggcnVsZQogICBhcHBsaWVzLCBhbmQgZXN0
YWJsaXNoZXMgdGhlIHJvdXRlIHByZWZlcmVuY2UuICBTZWUgRXhhbXBsZXMgc2VjdGlvbi4KCgo0
LiAgSW1wbGVtZW50YXRpb24KCjQuMS4gIEhvc3QgQmVoYXZpb3IKCiAgIEhvc3RzIHVzZSBSQXMg
YW5kIHRoZSBQSU8gdG8gZmluZCB0aGVpciBuZXh0IGhvcCwgYW5kIGZvciBhZGRyZXNzCiAgIGF1
dG9jb25maWd1cmF0aW9uLiAgTm90aGluZyBpbiB0aGUgdXNlIG9mIHRoZSBVUCBiaXQgY2hhbmdl
cyB0aGVzZQogICBiZWhhdmlvcnMsIHRob3VnaCBpdCBpcyBwb3NzaWJsZSB0aGF0IGhvc3RzIHdp
bGwgbGVhcm4gbXVsdGlwbGUKICAgcHJlZml4ZXMsIGFuZCBtaWdodCBoYXZlIG11bHRpcGxlIHBh
dGhzIHRvIHRoZSBzYW1lIHByZWZpeC4gIEl0IGlzCiAgIGV4cGVjdGVkIHRoYXQgdGhlc2UgYXJl
IGhhcm1sZXNzLiAgRGV0YWlscyBvZiBwYXRoIHNlbGVjdGlvbiBhcmUgbGVmdAogICB0byBpbXBs
ZW1lbnRlcnMuCgogICBBIGhvc3QgTUFZIHVzZSB0aGUgRGlzdGFuY2UgbWV0cmljIHRvIHNlbGVj
dCBhIGJldHRlciBiYXRoIGZvciBhCiAgIHByZWZpeC4gIEEgaG9zdCBtaWdodCBsZWFybiBtdWx0
aXBsZSBwcmVmaXhlcyBmcm9tIHdoaWNoIFNMQUFDIG1heSBiZQogICB1c2VkLiAgVGhpcyBpcyBu
b3QgYSBuZXcgZnVuY3Rpb24gaW50cm9kdWNlZCB3aXRoIHRoZSBVUCBiaXQsIGFuZAogICBob3N0
IGJlaGF2aW9yIGlzIGV4cGVjdGVkIHRvIGJlIHVuY2hhbmdlZC4KCjQuMi4gIFRpZSBCcmVha2lu
ZwoKICAgV2hlbiBhIHJvdXRlciBsZWFybnMgdGhlIHNhbWUgcHJlZml4IGZyb20gdHdvIG90aGVy
IHJvdXRlcnMsIGFuZCBib3RoCiAgIFJBcyBoYXZlIHRoZSBzYW1lIERpc3RhbmNlLCBhIHRpZS1i
cmVha2VyIG1lY2hhbmlzbSBpcyByZXF1aXJlZC4gIFRoZQogICB0aWUtYnJlYWtlciBjb3VsZCBi
ZSBhcmJpdHJhcnksIHN1Y2ggYXMgdGhlIHRpbWUgdGhlIFJBIHdhcyByZWNlaXZlZCwKICAgb3Ig
aXQgY291bGQgYmUgYmFzZWQgb24gKGUuZy4pIHRoZSBQcmVmZXJyZWQgTGlmZXRpbWUgdmFsdWUs
IHRoZQogICBsYXllciAyIGxpbmsgdHlwZSwgb3Igb3RoZXIgc3VpdGFibGUgaW5mb3JtYXRpb25y
LiAgSW1wbGVtZW50ZXJzIE1VU1QKICAgaGF2ZSBhIHRpZS1icmVha2VyIHJ1bGUgb3IgcnVsZXMg
dG8gcmVzb2x2ZSBhbGwgdGllcy4KCjQuMy4gIE11bHRpcGxlIFBhdGhzCgogICBBIHJvdXRlciBy
ZWNlaXZpbmcgbXVsdGlwbGUgUkFzIGZvciB0aGUgc2FtZSBwcmVmaXggbWF5IGNob29zZSB0bwog
ICBkaXNjYXJkIHRoZSBwYXRoIG5vdCBjaG9zZW4sIG9yIG1heSBhZGQgdGhlIHJvdXRlIHRvIGl0
cyByb3V0aW5nCiAgIHRhYmxlIHdpdGggYSBoaWdoZXIgQWRtaW5pc3RyYXRpdmUgRGlzdGFuY2Uu
CgoKCkhvd2FyZCAgICAgICAgICAgICAgICAgICBFeHBpcmVzIEFwcmlsIDI5LCAyMDEyICAgICAg
ICAgICAgICAgICBbUGFnZSA1XQoMCkludGVybmV0LURyYWZ0ICAgICAgICAgICAgICAgICAgIFVQ
IFBJTyAgICAgICAgICAgICAgICAgICAgIE9jdG9iZXIgMjAxMQoKCjQuNC4gIFJvdXRlIFdpdGhk
cmF3YWwKCiAgIEFzIHdpdGggb3RoZXIgUkFzLCB3aGVuIGFuIFJBIGlzIHJlY2VpdmVkIGZyb20g
YSByb3V0ZXIgd2l0aCBubwogICBpbmZvcm1hdGlvbiBmb3IgYSBwcmVmaXgsIGV2ZW4gaWYgdGhh
dCByb3V0ZXIgaGFkIHByZXZpb3VzbHkgcHJvdmlkZWQKICAgcHJlZml4IGluZm9ybWF0aW9uLCB0
aGUgcmVjZWl2ZXIgU0hPVUxEIHJlbW92ZSByZWZlcmVuY2VzIHRvIHRoYXQKICAgcHJlZml4IGZy
b20gaXRzIHJvdXRpbmcgdGFibGUuICBTaW1pbGFybHksIGlmIG5vIFJBcyBhcmUgcmVjZWl2ZWQK
ICAgZnJvbSBhIHJvdXRlciwgdGhlIHByZWZpeCBTSE9VTEQgYmUgcmVtb3ZlZC4gIEZ1cnRoZXIs
IGl0IFNIT1VMRCBzZW5kCiAgIFJBcyB3aXRob3V0IHRoYXQgcHJlZml4LgoKICAgV2hlbiB0aGUg
VmFsaWQgTGlmZXRpbWUgaGFzIHBhc3NlZCwgdGhlIHJvdXRlIE1VU1QgYmUgcmVtb3ZlZC4gIFdo
ZW4KICAgdGhlIFByZWZlcnJlZCBMaWZldGltZSBoYXMgcGFzc2VkLCB0aGUgcm91dGUgTUFZIGJl
IGxvd2VyZWQgaW4KICAgcHJlZmVyZW5jZS4KCgo1LiAgRXhhbXBsZXMKCiAgIENvbnNpZGVyIHRo
ZSBleGFtcGxlIGluIEZpZ3VyZSAxLCBpbiB3aGljaCBhIG5ldHdvcmsgaGFzIHR3byB1cHN0cmVh
bQogICBJU1BzLCBJU1AgQSBhbmQgSVNQIEIuIEEgZGlmZmVyZW50IHJvdXRlciBjb25uZWN0cyB0
byBlYWNoIElTUC4KICAgUm91dGVycyBBIGFuZCBCIGNvbm5lY3QgdG8gdGhlaXIgcmVzcGVjdGl2
ZSB1cHN0cmVhbSBJU1BzLCBhbmQgYQogICBSb3V0ZXIgQyBhbmQgUm91dGVyIEQgY29ubmVjdCB0
byB0aGUgc2FtZSBsaW5rLiAgUm91dGVycyBDIGFuZCBECiAgIHNoYXJlIGFub3RoZXIgbGluaywg
Y2F1c2luZyBhIHBvdGVudGlhbCBsb29wIHNpdHVhdGlvbi4gIEEgSG9zdCAjMQogICBjb25uZWN0
cyB0byB0aGUgc2hhcmVkIGxpbmsgYmV0d2VlbiBSb3V0ZXJzIEEsIEIsIEMsIGFuZCBELiBBIEhv
c3QgIzIKICAgY29ubmVjdHMgdG8gdGhlIHNoYXJlZCBsaW5rIGJldHdlZW4gUm91dGVycyBDIGFu
ZCBELgogICArLS0tLSstLS0tLSsgICAgICAgICAgICAgICAgICAgICAgICAgICAgICArLS0tLS0r
LS0tLSsgICAgXAogICB8ICAgSVNQIEEgIHwgICAgICAgICAgICAgICAgICAgICAgICAgICAgICB8
ICAgSVNQIEIgIHwgICAgIFwKICAgfCAgICAgICAgICB8ICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgfCAgICAgICAgICB8ICAgICB8IFNlcnZpY2UKICAgKy0tLS0rLS0tLS0rICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgKy0tLS0tKy0tLS0rICAgICB8IFByb3ZpZGVyCiAgICAgICAg
fCAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIHwgICAgICAgICAgfCBO
ZXR3b3JrCiAgICAgICAgfCAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
IHwgICAgICAgICAgLwogICAgICAgIHwgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICB8ICAgICAgICAgLwogICArLS0tLSstLS0tLSsgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICArLS0tLS0rLS0tLSsgICAgXAogICB8IFJvdXRlciBBIHwgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICB8IFJvdXRlciBCIHwgICAgIFwKICAgfCAgICAgICAgICB8ICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgfCAgICAgICAgICB8ICAgICAgfAogICArLS0tLSstLS0tLSsg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICArLS0tLS0rLS0tLSsgICAgICB8CiAgICAgICAg
fCAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIHwgICAgICAgICAgIHwg
SG9tZQogICAgICAgIHwgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICB8
ICAgICAgICAgICB8IE5ldHdvcmsKICAgIC0tLS0rLS0tLS0tLS0tLS0tLS0tLS0tLS0tKy0tLS0t
LS0tLS0tLS0tLS0tLS0tKy0tLSAgICAgICAgfAogICAgICAgIHwgICAgICAgICAgICAgICAgICAg
ICB8ICAgICAgICAgICAgICAgICAgICB8ICAgICAgICAgICB8CiAgICstLS0tKy0tLS0tKyAgICAg
ICAgICArLS0tLSstLS0tLSsgICAgICAgICstLS0tLSstLS0tKyAgICAgIHwKICAgfElQdjYgSG9z
dCB8ICAgICAgICAgIHwgUm91dGVyIEMgfCAgICAgICAgfCBSb3V0ZXIgRCB8ICAgICAgfAogICB8
ICAgICMxICAgIHwgICAgICAgICAgfCAgICAgICAgICB8LS0tKy0tLS18ICAgICAgICAgIHwgICAg
IC8KICAgKy0tLS0tLS0tLS0rICAgICAgICAgICstLS0tLS0tLS0tKyAgIHwgICAgKy0tLS0tLS0t
LS0rICAgIC8KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIHwKICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIHwKICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICstLS0tLSstLS0tKwogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgfCBJUHY2IEhvc3R8CiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICB8ICAgIzIg
ICAgIHwKICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICstLS0tLSstLS0tKwoKCgpI
b3dhcmQgICAgICAgICAgICAgICAgICAgRXhwaXJlcyBBcHJpbCAyOSwgMjAxMiAgICAgICAgICAg
ICAgICAgW1BhZ2UgNl0KDApJbnRlcm5ldC1EcmFmdCAgICAgICAgICAgICAgICAgICBVUCBQSU8g
ICAgICAgICAgICAgICAgICAgICBPY3RvYmVyIDIwMTEKCgogICAgICAgICAgICAgICAgICAgICAg
ICAgICBNdWx0aS1ob21lZCBUb3BvbG9neQoKICAgU3VwcG9zZSBJU1AgQSBhbmQgSVNQIEIgYm90
aCBwcm92aWRlIGEgZGVmYXVsdCByb3V0ZSB2aWEgUm91dGVyCiAgIEFkdmVydGlzZW1lbnRzLiAg
RnVydGhlciBzdXBwb3NlIHRoYXQgSVNQIEEgZGVsZWdhdGVzICh2aWEgREhDUHY2KQogICB0aGUg
cHJlZml4IDIwMDE6ZGI4OjAwMGE6Oi80OCwgYW5kIElTUCBCIGRlbGVnYXRlcyB0aGUgcHJlZml4
IDIwMDE6CiAgIGRiODowMDAwOjAwYjA6Oi81Ni4KCiAgIFJvdXRlciBBIHNlbmRzIDA6Oi8wIHdp
dGggVVAgYml0IGFuZCBEaXN0YW5jZT0xLCBhbmQgc2VuZHMgMjAwMTpkYjg6CiAgIGE6Oi80OCB3
aXRoIFVQIGJpdCBhbmQgRGlzdGFuY2U9MC4KCiAgICAgIFJvdXRlciBCIHJlY2VpdmVzIHRoZSBS
QS4gIEl0IHByZWZlcnMgdGhlIGRlZmF1bHQgcm91dGUgZnJvbSBJU1AKICAgICAgQiwgYmVjYXVz
ZSBpdHMgRGlzdGFuY2U9MC4gIEl0IGxlYXJucyBwcmVmaXggMjAwMTpkYjg6YTo6LzQ4IGFuZAog
ICAgICBhZGRzIGl0IHRvIGl0cyByb3V0aW5nIHRhYmxlLgoKICAgICAgUm91dGVyIEMgYW5kIFJv
dXRlciBEIHJlY2VpdmUgdGhlIFJBLiAgVGhleSBlYWNoIGluc3RhbGwgdGhlCiAgICAgIGRlZmF1
bHQgcm91dGUgYW5kIHRoZSAvNDggcHJlZml4IGluIHRoZWlyIHJvdXRpbmcgdGFibGVzLgoKICAg
ICAgSG9zdCAjMSBtaWdodCBjb25maWd1cmUgYW4gYWRkcmVzcyBmcm9tIHRoZSBwcmVmaXggdmlh
IERIQ1Agb3IKICAgICAgU0xBQUMuCgogICBSb3V0ZXIgQiBzZW5kcyAwOjovMCB3aXRoIFVQIGJp
dCBhbmQgRGlzdGFuY2U9MSwgYW5kIHNlbmRzIDIwMDE6ZGI4OgogICAwOmIwOjovNTYgd2l0aCBV
UCBiaXQgYW5kIERpc3RhbmNlPTAuCgogICAgICBSb3V0ZXIgQSByZWNlaXZlcyB0aGUgUkEuICBJ
dCBwcmVmZXJzIHRoZSBkZWZhdWx0IHJvdXRlIGZyb20gSVNQCiAgICAgIEEsIGJlY2F1c2UgaXRz
IERpc3RhbmNlPTAuICBJdCBsZWFybnMgcHJlZml4IDIwMDE6ZGI4OmIwOjovNTYgYW5kCiAgICAg
IGFkZHMgaXQgdG8gaXRzIHJvdXRpbmcgdGFibGUuCgogICAgICBSb3V0ZXIgQyBhbmQgUm91dGVy
IEQgcmVjZWl2ZSB0aGUgUkEuICBUaGV5IGNvbXBhcmUgdGhlIGRlZmF1bHQKICAgICAgcm91dGUg
dG8gdGhlIGV4aXN0aW5nIGRlZmF1bHQgcm91dGUuICBFYWNoIGFwcGxpZXMgaXRzIHRpZS0KICAg
ICAgYnJlYWtpbmcgcnVsZSwgYW5kIGluc3RhbGxzIHRoZSB3aW5uaW5nIHJvdXRlLiAgU3VwcG9z
ZSB0aGV5IGhhdmUKICAgICAgZGlmZmVyZW50IG1ldGhvZHMsIGFuZCBSb3V0ZXIgQyB1c2VzIHRo
ZSBkZWZhdWx0IHRvIFJvdXRlciBBLCBhbmQKICAgICAgUm91dGVyIEQgdXNlcyB0aGUgZGVmYXVs
dCB0byBSb3V0ZXIgQi4gVGhleSBlYWNoIGFkZCB0aGUgLzU2CiAgICAgIHByZWZpeCB0byB0aGVp
ciByb3V0aW5nIHRhYmxlcy4KCiAgICAgIEhvc3QgIzEgbWlnaHQgY29uZmlndXJlIGFuIGFkZGl0
aW9uYWwgYWRkcmVzcyBmcm9tIHRoZSBwcmVmaXggdmlhCiAgICAgIERIQ1Agb3IgU0xBQUMuICBX
aGV0aGVyIGl0IGRvZXMgaXMgYmV5b25kIHRoZSBzY29wZSBvZiB0aGlzCiAgICAgIGRvY3VtZW50
LgoKICAgUm91dGVyIEMgc2VuZHMgMDo6LzAgd2l0aCBVUCBiaXQgYW5kIERpc3RhbmNlPTIsIGFu
ZCBzZW5kcyAyMDAxOmRiODoKICAgYTo6LzQ4IHdpdGggVVAgYml0IGFuZCBEaXN0YW5jZT0yLCBh
bmQgc2VuZHMgMjAwMTpkYjg6MDpiMDo6LzU2IHdpdGgKICAgVVAgYml0IGFuZCBEaXN0YW5jZT0y
LgoKICAgICAgUm91dGVycyBBIGFuZCBCIHJlY2VpdmUgdGhlIFJBcywgYnV0IGlnbm9yZSB0aGUg
ZHVwbGljYXRlIHByZWZpeGVzCiAgICAgIHdpdGhpbiB0aGVtIGJlY2F1c2UgdGhleSBhbHJlYWR5
IGhhdmUgdGhvc2UgcHJlZml4ZXMgd2l0aCBhCiAgICAgIHNob3J0ZXIgRGlzdGFuY2UuCgogICAg
ICBSb3V0ZXIgRCByZWNlaXZlcyB0aGUgUkEgZm9yIDA6Oi8wLCBidXQgYWxyZWFkeSBoYXMgYSBy
b3V0ZSB3aXRoIGEKICAgICAgbG93ZXIgRGlzdGFuY2UuICBSb3V0ZXIgRCByZWNlaXZlcyB0aGUg
UkEgZm9yIDIwMDE6ZGI4OmE6Oi80OCwgYnV0CgoKCkhvd2FyZCAgICAgICAgICAgICAgICAgICBF
eHBpcmVzIEFwcmlsIDI5LCAyMDEyICAgICAgICAgICAgICAgICBbUGFnZSA3XQoMCkludGVybmV0
LURyYWZ0ICAgICAgICAgICAgICAgICAgIFVQIFBJTyAgICAgICAgICAgICAgICAgICAgIE9jdG9i
ZXIgMjAxMQoKCiAgICAgIGFscmVhZHkgaGFzIGEgcm91dGUgd2l0aCBhIGxvd2VyIERpc3RhbmNl
IChmcm9tIFJvdXRlciBBLCB3aGVyZQogICAgICBEaXN0YW5jZT0wKS4gIFJvdXRlciBEIHJlY2Vp
dmVzIHRoZSBSQSBmb3IgMjAwMTpkYjg6MDpiOjovNTYsIGJ1dAogICAgICBhbHJlYWR5IGhhcyBh
IHJvdXRlIHdpdGggYSBsb3dlciBEaXN0YW5jZSAoZnJvbSBSb3V0ZXIgQiwgd2hlcmUKICAgICAg
RGlzdGFuY2U9MCkuCgogICBSb3V0ZXIgQyB0aGVuIHJlY2VpdmVzIGRlbGVnYXRlZCBwcmVmaXgg
MjAwMTpkYjg6YTpjOjovNjQuICBIb3N0ICMyCiAgIGdldHMgYW4gYWRkcmVzcyBmb3IgdGhpcyBw
cmVmaXgsIGVpdGhlciB2aWEgU0xBQUMgb3IgREhDUC4gIFJvdXRlciBDCiAgIHNlbmRzIFJBcyBm
b3IgMjAwMTpkYjg6YTpjOjovNjQgd2l0aCBVUCBiaXQgYW5kIERpc3RhbmNlPTAuICBUaGUgaG9z
dAogICBhbHNvIHJlY2VpdmVzIFJBcyBmb3IgdGhlIC82NCBwcmVmaXguCgogICAgICBSb3V0ZXIg
RCByZWNlaXZlcyB0aGUgUkEgZm9yIDIwMDE6ZGI4OmE6Yzo6LzY0LiAgSXQgaXMgYSBsb25nZXIK
ICAgICAgKG1vcmUgc3BlY2lmaWMgcHJlZml4KSB0aGFuIGl0cyBwcmV2aW91cyAyMDAxOmRiODph
OjovNDggcm91dGUsIHNvCiAgICAgIGl0IGFkZHMgdGhlIG1vcmUgc3BlY2lmaWMgdG8gaXRzIHJv
dXRpbmcgdGFibGUuCgogICAgICBSb3V0ZXJzIEEgYW5kIEIgcmVjZWl2ZSB0aGUgUkEgZm9yIDIw
MDE6ZGI4OmE6Yzo6LzY0LiAgSXQgaXMgYQogICAgICBsb25nZXIgKG1vcmUgc3BlY2lmaWMgcHJl
Zml4KSB0aGFuIHRoZWlyIHByZXZpb3VzIDIwMDE6ZGI4OmE6Oi80OAogICAgICByb3V0ZSwgc28g
dGhleSBhZGQgdGhlIG1vcmUgc3BlY2lmaWMgdG8gaXRzIHJvdXRpbmcgdGFibGUuICBUaGV5CiAg
ICAgIHdpbGwgdXBkYXRlIHRoZWlyIG93biBSQXMsIGJ1dCBSb3V0ZXJzIEMgYW5kIEQgYWxyZWFk
eSBoYXZlIHJvdXRlcwogICAgICB3aXRoIGxvd2VyIERpc3RhbmNlLgoKICAgICAgSWYgUm91dGVy
IEEgb3IgUm91dGVyIEIgc2VuZHMgdGhlIG1vcmUtc3BlY2lmaWMgcHJlZml4IHRvIHRoZSBJU1As
CiAgICAgIHRoZSBJU1AgTUFZIGNob29zZSB0byBhZGQgdGhlIHJvdXRlIG9yIGlnbm9yZSBpdCBp
ZiBhIHJvdXRlCiAgICAgIHByZWZlcnJlZCBieSBwb2xpY3kgZXhpc3RzIChmb3IgdGhlIGRlbGVn
YXRlZCBwcmVmaXgpLgoKCjYuICBFdmFsdWF0aW9uCgogICBIZXJlIGZvbGxvd3MgYW4gZXZhbHVh
dGlvbiBvZiB3aGV0aGVyIHRoaXMgc29sdXRpb24gbWVldHMgYWxsIG9mIHRoZQogICBIb21lbmV0
IHJvdXRpbmcgcmVxdWlyZW1lbnRzLgoKICAgICAgQ2FuIEhvc3QgIzEgcmVhY2ggSG9zdCAjMj8g
IFllcywgdmlhIGEgcGF0aCB0aHJvdWdoIGVpdGhlciByb3V0ZXIuCgogICAgICBJcyB0aGUgbmV0
d29yayBib3JkZXIgY2xlYXI/ICBZZXMsIGFzIERpc3RhbmNlPTAgZm9yIHRoZSBzaG9ydGVzdAog
ICAgICBwcmVmaXguCgogICAgICBDYW4gaXQgaGFuZGxlIGEgcm91dGVyIGJlaW5nIGFkZGVkPyAg
WWVzLCB0aGUgbmV3IHJvdXRlciB3aWxsCiAgICAgIGxlYXJuIHByZWZpeGVzIHZpYSBSQXMgcXVp
Y2tseS4KCiAgICAgIENhbiBpdCBoYW5kbGUgYSByb3V0ZXIgYmVpbmcgbW92ZWQ/ICBZZXMsIHdp
dGggc29tZSBkZWxheSBpbgogICAgICByZWxlYXJuaW5nIHRoZSByb3V0ZXMuICBJZiBIb3N0ICMy
IHdlcmUgYSBSb3V0ZXIgRSwgYW5kIGl0IHdhcwogICAgICBtb3ZlZCB0byB0aGUgc2hhcmVkIEFC
Q0QgbGluayB3aXRob3V0IHRoZSByb3V0ZXIgb3IgaW50ZXJmYWNlCiAgICAgIGdvaW5nIGRvd24g
bG9uZyBlbm91Z2ggZm9yIFJBcyB0byBiZSBtaXNzZWQsIGl0IG1pZ2h0IHByb3BhZ2F0ZQogICAg
ICBSQXMgbGVhcm5lZCBmcm9tIFJvdXRlcnMgQyBhbmQgRC4gSXQgd291bGQgaGF2ZSBhIGhpZ2hl
ciBEaXN0YW5jZQogICAgICBmb3IgdGhlIHNob3J0ZXIgcHJlZml4ZXMgKHRoZSAvMCwgLzQ4LCAv
NTYpLCBzbyBuZWlnaGJvcmluZwogICAgICByb3V0ZXJzIHdvdWxkIGlnbm9yZSBpdHMgUkFzLiAg
SWYgaXQgd2VyZSB0d28gbGF5ZXJzIGRlZXBlciBpbiB0aGUKICAgICAgbmV0d29yaywgc3VjaCB0
aGF0IGl0IGhhZCBhIERpc3RhbmNlPTIgZm9yIGEgbW9yZS1zcGVjaWZpYywgd2hpY2gKICAgICAg
d2FzIGJldHRlciB0aGFuIHRoZSBEaXN0YW5jZSBwcmV2aW91c2x5IHNlZW4gYnkgUm91dGVycyBB
IGFuZCBCLAogICAgICBuZWlnaGJvcnMgd291bGQgcHJlZmVyIGl0cyBSQXMuICBIb3dldmVyLCBp
dCB3b3VsZCBzdG9wIHNlbmRpbmcKCgoKSG93YXJkICAgICAgICAgICAgICAgICAgIEV4cGlyZXMg
QXByaWwgMjksIDIwMTIgICAgICAgICAgICAgICAgIFtQYWdlIDhdCgwKSW50ZXJuZXQtRHJhZnQg
ICAgICAgICAgICAgICAgICAgVVAgUElPICAgICAgICAgICAgICAgICAgICAgT2N0b2JlciAyMDEx
CgoKICAgICAgdGhvc2UgUkFzIG9uY2UgaXQgc3RvcHBlZCByZWNlaXZpbmcgdGhlbS4gIFRoZSBy
b3V0ZXIgd291bGQKICAgICAgY29udGludWUgc2VuZGluZyBSQXMgZm9yIGl0cyBkZWxlZ2F0ZWQg
cHJlZml4IGZvciBhcyBsb25nIGFzIGl0CiAgICAgIGhhZCB0aGF0IHByZWZpeDsgdGhpcyBwcm9i
bGVtIGlzIHJlbGF0ZWQgdG8gYWRkcmVzc2luZywgbm90CiAgICAgIHJvdXRpbmcuCgogICAgICBD
YW4gaXQgaGFuZGxlIGEgcm91dGVyIGJlaW5nIHJlbW92ZWQ/ICBZZXMuIFNvbWUgcm91dGVycyBt
YXkKICAgICAgaW5zdGFsbCBtdWx0aXBsZSByb3V0ZXM7IGFzIHNvb24gYXMgdGhleSBtaXNzIHNl
ZWluZyBhbiBSQSBmb3IgYQogICAgICBwcmVmaXgsIHRoZXkgd2lsbCBoYXZlIGEgYmFjayByb3V0
ZS4gIE90aGVyIHJvdXRlcnMgbWF5IGhhdmUgdG8KICAgICAgd2FpdCB1bnRpbCB0aGV5IHNlZSBh
IG5ldyBSQSBiZWZvcmUgaGF2aW5nIGEgYmFja3VwIHBhdGggdG8gdGhlCiAgICAgIHByZWZpeC4K
CiAgICAgIFdpbGwgaXQgd29yayBpbiBhIG5vLWNvbmZpZ3VyYXRpb24gZW52aXJvbm1lbnQ/ICBZ
ZXMuCgogICAgICBDYW4gaXQgc3VwcG9ydCBtdWx0aXBsZSB1cHN0cmVhbSBuZXR3b3Jrcz8gIFll
cy4gSXQgZG9lcyBub3Qgc29sdmUKICAgICAgYWRkcmVzcyBjb25maWd1cmF0aW9uIG9yIHNvdXJj
ZSBzZWxlY3Rpb24gaXNzdWVzLCBidXQgdGhvc2UgYXJlCiAgICAgIG5vdCByb3V0aW5nIHByb2Js
ZW1zIHBlciBzZS4KCiAgICAgIERvZXMgaXQgd29yayBpZiBwcmVmaXggZGVsZWdhdGlvbiBpcyBu
b3QgaGllcmFyY2hpY2FsPyAgWWVzLiBFYWNoCiAgICAgIHByZWZpeCBoYXMgaXRzIG93biBQcmVm
aXggSW5mb3JtYXRpb24gT3B0aW9uLCBlYWNoIHdpdGggaXRzIG93bgogICAgICBEaXN0YW5jZS4K
CiAgICAgIENhbiBhbm90aGVyIHBhdGggYmUgZm91bmQgaW4gY2FzZSBvZiBmYWlsdXJlPyAgWWVz
LCB3aXRoaW4gYQogICAgICBjb3VwbGUgb2YgUkEgaW50ZXJ2YWxzLgoKICAgICAgRG9lcyBpdCBw
cmV2ZW50IGxvb3BzPyAgWWVzLgoKICAgICAgRG9lcyBpdCBhbGxvdyBmb3Igc3RhYmxlIHByZWZp
eGVzIHRocm91Z2ggcmVib290cz8gIFllcywgdGhvdWdoCiAgICAgIHBhdGhzIHdpbGwgaGF2ZSB0
byBiZSByZWRpc2NvdmVyZWQsIHRocm91Z2ggdGhlIHBlcmlvZCBjb25maWd1cmVkCiAgICAgIGZv
ciBSb3V0ZXIgQWR2ZXJ0aXNlbWVudCB0cmFuc21pc3Npb25zLgoKICAgICAgSXMgaXQgbGlnaHR3
ZWlnaHQvY2hlYXA/ICBZZXMuIEEgc2ltcGxlIGFkZGl0aW9uIHRvIHRoZSBQSU8sIHdoaWNoCiAg
ICAgIGFscmVhZHkgZXhpc3RzLiAgU29tZSBhZGRpdGlvbmFsIHJvdXRpbmcgZGVjaXNpb24tdHJl
ZSBsb2dpYyBpcwogICAgICByZXF1aXJlZCBmb3IgY29tcGFyaW5nIGJlc3QgcGF0aHMsIHRpZS1i
cmVha2luZyBhbW9uZyBlcXVhbCBwYXRocywKICAgICAgZXRjLgoKICAgICAgQ2FuIGl0IGhhbmRs
ZSBtdWx0aXBsZS1kd2VsbGluZyB1bml0cywgb3Igb3RoZXIgcG90ZW50aWFsbHkgZGVuc2UKICAg
ICAgbmV0d29ya3M/ICBFYWNoIHVwc3RyZWFtIHJvdXRlciB3aWxsIGluY3JlbWVudCBEaXN0YW5j
ZSwgc28gZWFjaAogICAgICByb3V0ZXIgc2hvdWxkIGNob29zZSB0aGUgc2hvcnRlc3QgdXBzdHJl
YW0gcGF0aC4gIEhvd2V2ZXIsIGEgaG9zdAogICAgICB3aXRoIG5vIHJvdXRlciBjb3VsZCBlbmQg
dXAgY2hvb3NpbmcgYSBuZWlnaGJvcidzIHJvdXRlciBpbnN0ZWFkCiAgICAgIG9mIHRoZWlyIElT
UC4gIFRoZSBzb2x1dGlvbiBpcyBubyBjaGF0dGllciB0aGFuIGV4aXN0aW5nIFJBcy4KCiAgICAg
IENhbiBpdCBzdGFuZCB1cCB0byB3aXJlbGVzcyBuZXR3b3JrcywgYW5kIG5ldHdvcmtzIHdpdGgg
d2lyZWQgYW5kCiAgICAgIHdpcmVsZXNzIHNlZ21lbnRzPyAgWWVzLCB3aXRoIGNvbnNpZGVyYXRp
b24gZm9yIG11bHRpcGxlLWR3ZWxsaW5nCiAgICAgIHVuaXRzLgoKICAgICAgQ2FuIGl0IHN0YW5k
IHVwIHRvIHVuaW50ZW50aW9uYWwgY29ubmVjdGlvbnMgb2YgbmV0d29ya3M/ICBZZXMuCiAgICAg
IEFsdGhvdWdoIHRoZSBEaXN0YW5jZSB3b3VsZCBzZWVtIHRvIGxpbWl0IHRoZSBkaWFtZXRlciBv
ZiB0aGUKICAgICAgbmV0d29yayB0byAyNTUgc2VnbWVudHMsIHdoZW4gZWFjaCByb3V0ZXIgaXMg
Z2l2ZW4gYSBzdWJuZXQKCgoKSG93YXJkICAgICAgICAgICAgICAgICAgIEV4cGlyZXMgQXByaWwg
MjksIDIwMTIgICAgICAgICAgICAgICAgIFtQYWdlIDldCgwKSW50ZXJuZXQtRHJhZnQgICAgICAg
ICAgICAgICAgICAgVVAgUElPICAgICAgICAgICAgICAgICAgICAgT2N0b2JlciAyMDExCgoKICAg
ICAgcHJlZml4LCBpdCByZXNldHMgdGhlIERpc3RhbmNlIHRvIDAgZm9yIGl0cyBwcmVmaXguICBU
aHVzLCB0aGUKICAgICAgRGlhbWV0ZXIgaXMgYSB3aWRlIGFzIHByZWZpeCB0b3BvbG9neSBhbGxv
d3MuCgoKNy4gIEFkZGl0aW9uYWwgV29yayBSZXF1aXJlZAoKICAgVGhpcyBvcHRpb24gZXNzZW50
aWFsbHkgb3ZlcmxvYWRzIHRoZSBQSU8gdG8gYmUgYSBsaWdodHdlaWdodAogICBkaXN0YW5jZS12
ZWN0b3Igcm91dGluZyBwcm90b2NvbCBvZiBzb3J0cy4gIEFzIHN1Y2gsIGl0IG5lZWRzIHRvCiAg
IGF2b2lkIHRoZSBwcm9ibGVtcyBvZiBkaXN0YW5jZS12ZWN0b3IgcHJvdG9jb2xzLCBzdWNoIGFz
IHRoZSBjb3VudC0KICAgdG8taW5maW5pdHkgcHJvYmxlbS4gIFNldmVyYWwgcG9zc2liaWxpdGll
cyBleGlzdCB0byBtaXRpZ2F0ZSB0aGlzCiAgIHByb2JsZW06CgogICAgICBVc2UgYSBzbWFsbGVy
IHBvc3NpYmxlIGluZmluaXR5IChpLmUuLCBjaGFuZ2UgdGhlIERpc3RhbmNlIGZpZWxkCiAgICAg
IHRvIGJlIGEgNC1iaXQgZmllbGQpCgogICAgICBTaG9ydGVuIHRoZSBSQSB0cmFuc21pc3Npb24g
aW50ZXJ2YWxzCgogICAgICBTcGxpdCBob3Jpem9uIChkbyBub3QgYWR2ZXJ0aXNlIGEgcHJlZml4
IG91dCB0aGUgaW50ZXJmYWNlIGl0IHdhcwogICAgICBsZWFybmVkKSB3aXRoIHBvaXNvbiByZXZl
cnNlICh3aGVuIGEgbmVpZ2hib3IgaXMgbG9zdCwgc2VuZCBhbiBSQQogICAgICB3aXRoIERpc3Rh
bmNlPTI1NSkgY291bGQgYmUgdXNlZAoKCjguICBBbHRlcm5hdGl2ZXMKCiAgIEFuIGV4dGVuc2lv
biBvZiByZmM0MTkxLCBEZWZhdWx0IFJvdXRlciBQcmVmZXJlbmNlcyBhbmQgTW9yZS1TcGVjaWZp
YwogICBSb3V0ZXMsIHdpdGggaXRzIGRlZmluaXRpb24gb2YgYSBSb3V0ZSBJbmZvcm1hdGlvbiBP
cHRpb24sIG1pZ2h0IGJlIGEKICAgY2xvc2VyIGFwcHJveGltYXRpb24gdG8gdGhlIGRpc3RhbmNl
LXZlY3RvciBwcm90b2NvbCBkZXNjcmliZWQgaGVyZS4KCiAgIEEgbGluay1zdGF0ZSBwcm90b2Nv
bCB3b3VsZCBzb2x2ZSBzdGFuZGFyZCBwcm9ibGVtcyB3aXRoIGRpc3RhbmNlLQogICB2ZWN0b3Ig
cHJvdG9jb2xzLiAgSG93ZXZlciwgbW9zdCBsaW5rLXN0YXRlIHByb3RvY29scyBhcmUgbXVjaAog
ICBoZWF2aWVyIGltcGxlbWVudGF0aW9ucy4KCgo5LiAgU2VjdXJpdHkgQ29uc2lkZXJhdGlvbnMK
CiAgIEJ5IHVzaW5nIHVuc2VjdXJlZCBSb3V0ZXIgQWR2ZXJ0aXNlbWVudHMsIGF0dGFja3MgdGhh
dCBjb21wcm9taXNlIFJBcwogICB3b3VsZCBoYXZlIGFuIGV4dGVuZGVkIGVmZmVjdC4gIFVzZSBv
ZiBTZU5EIHNob3VsZCBtaXRpZ2F0ZSB0aGVzZQogICBhdHRhY2tzLgoKCjEwLiAgSUFOQSBDb25z
aWRlcmF0aW9ucwoKICAgVGhlcmUgYXJlIG5vIElBTkEgY29uc2lkZXJhdGlvbnMgb3IgaW1wbGlj
YXRpb25zIHRoYXQgYXJpc2UgZnJvbSB0aGlzCiAgIGRvY3VtZW50LgoKCjExLiAgUmVmZXJlbmNl
cwoKCgoKSG93YXJkICAgICAgICAgICAgICAgICAgIEV4cGlyZXMgQXByaWwgMjksIDIwMTIgICAg
ICAgICAgICAgICAgW1BhZ2UgMTBdCgwKSW50ZXJuZXQtRHJhZnQgICAgICAgICAgICAgICAgICAg
VVAgUElPICAgICAgICAgICAgICAgICAgICAgT2N0b2JlciAyMDExCgoKMTEuMS4gIE5vcm1hdGl2
ZSBSZWZlcmVuY2VzCgogICBbUkZDMjExOV0gICJLZXkgd29yZHMgZm9yIHVzZSBpbiBSRkNzIHRv
IEluZGljYXRlIFJlcXVpcmVtZW50CiAgICAgICAgICAgICAgTGV2ZWxzIi4KCiAgIFtSRkMyNDYx
XSAgIk5laWdoYm9yIERpc2NvdmVyeSBmb3IgSVAgVmVyc2lvbiA2IChJUHY2KSIuCgogICBbUkZD
Mzc3NV0gICJNb2JpbGl0eSBTdXBwb3J0IGluIElQdjYiLgoKICAgW1JGQzQ4NjFdICAiTmVpZ2hi
b3IgRGlzY292ZXJ5IGZvciBJUCB2ZXJzaW9uIDYgKElQdjYpIi4KCjExLjIuICBJbmZvcm1hdGl2
ZSBSZWZlcmVuY2VzCgogICBbUkZDMzYzM10gICJJUHY2IFByZWZpeCBPcHRpb25zIGZvciBEeW5h
bWljIEhvc3QgQ29uZmlndXJhdGlvbgogICAgICAgICAgICAgIFByb3RvY29sIChESENQKSB2ZXJz
aW9uIDYiLgoKICAgW1JGQzYyMDRdICBDaXNjbyBTeXN0ZW1zLCBJbmMuLCBDaXNjbyBTeXN0ZW1z
LCBJbmMuLCBDYWJsZUxhYnMsIEFUJlQsCiAgICAgICAgICAgICAgYW5kIENpc2NvIFN5c3RlbXMs
IEluYy4sICJCYXNpYyBSZXF1aXJlbWVudHMgZm9yIElQdjYKICAgICAgICAgICAgICBDdXN0b21l
ciBFZGdlIFJvdXRlcnMiLgoKCkF1dGhvcidzIEFkZHJlc3MKCiAgIExlZSBIb3dhcmQKICAgVGlt
ZSBXYXJuZXIgQ2FibGUKICAgMTM4MjAgU3VucmlzZSBWYWxsZXkgRHJpdmUKICAgSGVybmRvbiwg
VkEgIDIwMTcxCiAgIFVTCgogICBQaG9uZTogKzEgNzAzIDM0NSAzNTEzCiAgIEVtYWlsOiBsZWUu
aG93YXJkQHR3Y2FibGUuY29tCgoKCgoKCgoKCgoKCgoKCgoKCgoKSG93YXJkICAgICAgICAgICAg
ICAgICAgIEV4cGlyZXMgQXByaWwgMjksIDIwMTIgICAgICAgICAgICAgICAgW1BhZ2UgMTFdCgwK

--_002_DCC302FAA9FE5F4BBA4DCAD46569377914517EE5FDPRVPEXVS03cor_--

From nordmark@cisco.com  Wed Nov  2 10:58:17 2011
Return-Path: <nordmark@cisco.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 023431F0CA0 for <homenet@ietfa.amsl.com>; Wed,  2 Nov 2011 10:58:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.099
X-Spam-Level: 
X-Spam-Status: No, score=-6.099 tagged_above=-999 required=5 tests=[AWL=0.500,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gm1M5oeziQ9b for <homenet@ietfa.amsl.com>; Wed,  2 Nov 2011 10:58:16 -0700 (PDT)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id 6765B1F0C4B for <homenet@ietf.org>; Wed,  2 Nov 2011 10:58:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=nordmark@cisco.com; l=1258; q=dns/txt; s=iport; t=1320256696; x=1321466296; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=SF5u2Ezgldlf215zBaxXbKcFNlG78ccHN5cPijyr2C8=; b=i9XObqx+WtMetZu6G4cSdjZVXJusAk1QY7kWcZHYIuDjc7ntt7wznpYy Vxs7P1Nisnt+IlIXfCzTT0So0HeQ2l+6fMaldXIpKQgNGwcTqG2F8tbd5 KZhbyakHBGX1FVXrfATreqE/vfgod0IBYFjSR1CZUY2UgdgqalFg6gsg7 I=;
X-IronPort-AV: E=Sophos;i="4.69,444,1315180800"; d="scan'208";a="11964605"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-3.cisco.com with ESMTP; 02 Nov 2011 17:58:16 +0000
Received: from [10.33.22.24] ([10.33.22.24]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id pA2HwGdq026518; Wed, 2 Nov 2011 17:58:16 GMT
Message-ID: <4EB184B8.4000901@cisco.com>
Date: Wed, 02 Nov 2011 10:58:16 -0700
From: Erik Nordmark <nordmark@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
References: <4EAD1B77.6010602@piuha.net>
In-Reply-To: <4EAD1B77.6010602@piuha.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "homenet@ietf.org" <homenet@ietf.org>
Subject: Re: [homenet] Prefix stability requirements in draft-arkko-homenet-prefix-assignment-00
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 02 Nov 2011 17:58:17 -0000

Jari,

> The draft associates prefixes with interfaces because that is the only
> thing that it can do alone. But since it monitors prefix assignments by
> both neighboring routers and everyone else, routers are aware of the
> network topology _and_ network prefix assignments. A prefix assignment
> by your neighbor becomes your prefix assignment, too. You use the same
> prefix on the same network, not add another one. And next time if the
> two routers boot in a different order you will remember your neighbor's
> prefix for this network and use it. If the two routers are moved to
> different networks, there will be a collision, it is detected, and one
> of the routers selects a new prefix.

OK. There are probably some important details when there are multiple 
routers wanting to use different prefixes on the same link. If I've had 
the routers in the den happily working for a year, and I decide to bring 
in a router from the garage (which has been in use for a week) and 
connect it to the routers in the den, then a reasonable default behavior 
would be to keep the prefix that has in use on that link for a year.

Some notion of "first time advertised" could be useful for that type of 
tiebreakers.

Thanks,
   Erik

From jari.arkko@piuha.net  Wed Nov  2 11:33:20 2011
Return-Path: <jari.arkko@piuha.net>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7340C11E80F8 for <homenet@ietfa.amsl.com>; Wed,  2 Nov 2011 11:33:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.579
X-Spam-Level: 
X-Spam-Status: No, score=-102.579 tagged_above=-999 required=5 tests=[AWL=0.020, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 42wK7PPE+RWs for <homenet@ietfa.amsl.com>; Wed,  2 Nov 2011 11:33:20 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id B230111E80C8 for <homenet@ietf.org>; Wed,  2 Nov 2011 11:33:19 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 619B72CED1; Wed,  2 Nov 2011 20:33:18 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pTM7-E9Rd0fH; Wed,  2 Nov 2011 20:33:17 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 036FE2CC61; Wed,  2 Nov 2011 20:33:16 +0200 (EET)
Message-ID: <4EB18CEC.1@piuha.net>
Date: Wed, 02 Nov 2011 20:33:16 +0200
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: Erik Nordmark <nordmark@cisco.com>
References: <4EAD1B77.6010602@piuha.net> <4EB184B8.4000901@cisco.com>
In-Reply-To: <4EB184B8.4000901@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "homenet@ietf.org" <homenet@ietf.org>
Subject: Re: [homenet] Prefix stability requirements in draft-arkko-homenet-prefix-assignment-00
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 02 Nov 2011 18:33:20 -0000

Erik,

> OK. There are probably some important details when there are multiple routers wanting to use different prefixes on the same link. If I've had the routers in the den happily working for a year, and I decide to bring in a router from the garage (which has been in use for a week) and connect it to the routers in the den, then a reasonable default behavior would be to keep the prefix that has in use on that link for a year.
>
> Some notion of "first time advertised" could be useful for that type of tiebreakers.

I agree, both about the requirement and that we're probably still missing some of the important details.

But I'll just point out one additional thing. Since only devices (not networks) can have memory and identity, it is hard in general to decide what changed. Say, if you had just one router in the den and another one in the garage, both installed at the same time and then you move the garage router to the den. From a human perspective it would probably make sense to keep the den prefix unchanged, but how do the routers know this? Just looking at the situation locally may not help in this case. There's one router's opinion against the other router's opinion. The times are identical. You could of course inspect whether topology around you changed and infer which one of the devices got moved. But it is hard.

Jari


From ot@cisco.com  Wed Nov  2 14:47:48 2011
Return-Path: <ot@cisco.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ABF8E1F0C63 for <homenet@ietfa.amsl.com>; Wed,  2 Nov 2011 14:47:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.717
X-Spam-Level: 
X-Spam-Status: No, score=-9.717 tagged_above=-999 required=5 tests=[AWL=0.838,  BAYES_00=-2.599, DATE_IN_PAST_03_06=0.044, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9QxxbSYZHMeP for <homenet@ietfa.amsl.com>; Wed,  2 Nov 2011 14:47:48 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id C21EE1F0C5D for <homenet@ietf.org>; Wed,  2 Nov 2011 14:47:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ot@cisco.com; l=589; q=dns/txt; s=iport; t=1320270467; x=1321480067; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=XXzyFisZV8djxqvgo5rPgZ0OBznkcl1d8gu84w8i7h4=; b=G15R6gnXwGG2D/hyNrRuVlpbSpwvCT6NZW74mz/eKztOy7QVIcjZnlE1 oCPTn1nG1dMQYxQZVRDdshfhS1eE1Q+Nu/EJY6evX2PdL3gMM6led9Pa8 +OEKL8vAx3yiCa4LSWn8glDcLSqdLSCvObGMyRgldapQZUa1N6LSSGPbQ 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqoFABe6sU6Q/khR/2dsb2JhbABEJqlNgQWBcgEBAQMBEgEnPwULC0ZXBhwZh2AIljoBnn+IL2EElBSRZg
X-IronPort-AV: E=Sophos;i="4.69,446,1315180800"; d="scan'208";a="59069705"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-2.cisco.com with ESMTP; 02 Nov 2011 21:47:44 +0000
Received: from ams3-vpn-dhcp5749.cisco.com (ams3-vpn-dhcp5749.cisco.com [10.61.86.116]) by ams-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id pA2Llihl008006; Wed, 2 Nov 2011 21:47:44 GMT
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Ole Troan <ot@cisco.com>
In-Reply-To: <DCC302FAA9FE5F4BBA4DCAD46569377914517EE5FD@PRVPEXVS03.corp.twcable.com>
Date: Wed, 2 Nov 2011 17:46:12 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <1864C465-E1AD-4F47-9E9E-5E26B84D2DFC@cisco.com>
References: <DCC302FAA9FE5F4BBA4DCAD46569377914517EE5FD@PRVPEXVS03.corp.twcable.com>
To: "Howard, Lee" <lee.howard@twcable.com>
X-Mailer: Apple Mail (2.1084)
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] another routing option
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 02 Nov 2011 21:47:48 -0000

Howard,

> I've said that I don't think we need a full dynamic routing protocol.  =
There are other options for discovering an available path.  To stimulate =
creative thinking, I've written a draft proposing one alternative that =
should be light to implement in home gateways: =
http://www.asgard.org/images/draft-howard-up-pio-00.txt
> If it is interesting, there's more work to be done on it; I could =
publish it after the pre-meeting publication blackout ends.

aren't you in the end just going to reinvent RAs as a distance vector =
routing protocol...?

cheers,
Ole



From lee.howard@twcable.com  Wed Nov  2 14:53:49 2011
Return-Path: <lee.howard@twcable.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1F1511E80B5 for <homenet@ietfa.amsl.com>; Wed,  2 Nov 2011 14:53:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.23
X-Spam-Level: 
X-Spam-Status: No, score=-1.23 tagged_above=-999 required=5 tests=[AWL=0.233,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FPYCAKoGqfnx for <homenet@ietfa.amsl.com>; Wed,  2 Nov 2011 14:53:49 -0700 (PDT)
Received: from cdpipgw01.twcable.com (cdpipgw01.twcable.com [165.237.59.22]) by ietfa.amsl.com (Postfix) with ESMTP id 3CA7A11E8094 for <homenet@ietf.org>; Wed,  2 Nov 2011 14:53:49 -0700 (PDT)
X-SENDER-IP: 10.136.163.13
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.69,445,1315195200"; d="scan'208";a="292736202"
Received: from unknown (HELO PRVPEXHUB04.corp.twcable.com) ([10.136.163.13]) by cdpipgw01.twcable.com with ESMTP/TLS/RC4-MD5; 02 Nov 2011 17:49:43 -0400
Received: from PRVPEXVS03.corp.twcable.com ([10.136.163.27]) by PRVPEXHUB04.corp.twcable.com ([10.136.163.13]) with mapi; Wed, 2 Nov 2011 17:53:48 -0400
From: "Howard, Lee" <lee.howard@twcable.com>
To: Jari Arkko <jari.arkko@piuha.net>, "homenet@ietf.org" <homenet@ietf.org>
Date: Wed, 2 Nov 2011 17:53:47 -0400
Thread-Topic: [homenet] FW: New Version Notification for draft-arkko-homenet-prefix-assignment-01.txt
Thread-Index: AcyX4MQszCArwQhCR4yMX9rcNUeZTgBx+dlw
Message-ID: <DCC302FAA9FE5F4BBA4DCAD46569377914517EEBA5@PRVPEXVS03.corp.twcable.com>
References: <20111031151951.4438.52423.idtracker@ietfa.amsl.com> <4EAEBCF0.3090305@piuha.net>
In-Reply-To: <4EAEBCF0.3090305@piuha.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [homenet] FW: New Version Notification for	draft-arkko-homenet-prefix-assignment-01.txt
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 02 Nov 2011 21:53:49 -0000

One of the reasons you give for using OSPF is conservation of prefixes.  Si=
nce there's no
need to conserve addresses, you say stingy ISPs force us to conserve prefix=
es.  That
sounds like routing around a Layer 8-9 problem which may not yet have occur=
red.
Wouldn't we prefer to have a clean prefix assignment, assuming enough prefi=
xes (up to,
say /48), and if some ISPs get a barrage of support calls because customers=
' routers
don't work, it serves them right?
(Easy for me to say, as an ISP who intends to give customers what they ask =
for)

Lee



> -----Original Message-----
> From: homenet-bounces@ietf.org [mailto:homenet-bounces@ietf.org] On Behal=
f Of Jari
> Arkko
> Sent: Monday, October 31, 2011 11:21 AM
> To: homenet@ietf.org
> Subject: [homenet] FW: New Version Notification for draft-arkko-homenet-p=
refix-
> assignment-01.txt
>
> FYI. Contains small updates based on input received on the list.
>
> > A new version of I-D, draft-arkko-homenet-prefix-assignment-01.txt has =
been
> successfully submitted by Jari Arkko and posted to the IETF repository.
> >
> > Filename:    draft-arkko-homenet-prefix-assignment
> > Revision:    01
> > Title:               Prefix Assignment in a Home Network
> > Creation date:       2011-10-31
> > WG ID:               Individual Submission
> > Number of pages: 14
> >
> >
>
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet

This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

From lee.howard@twcable.com  Wed Nov  2 14:55:08 2011
Return-Path: <lee.howard@twcable.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 693F511E8094 for <homenet@ietfa.amsl.com>; Wed,  2 Nov 2011 14:55:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.744
X-Spam-Level: 
X-Spam-Status: No, score=-0.744 tagged_above=-999 required=5 tests=[AWL=-0.281, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 02aVx-5Xt+6v for <homenet@ietfa.amsl.com>; Wed,  2 Nov 2011 14:55:07 -0700 (PDT)
Received: from cdpipgw02.twcable.com (cdpipgw02.twcable.com [165.237.59.23]) by ietfa.amsl.com (Postfix) with ESMTP id B078811E80B5 for <homenet@ietf.org>; Wed,  2 Nov 2011 14:55:07 -0700 (PDT)
X-SENDER-IP: 10.136.163.11
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.69,445,1315195200"; d="scan'208";a="277544871"
Received: from unknown (HELO PRVPEXHUB02.corp.twcable.com) ([10.136.163.11]) by cdpipgw02.twcable.com with ESMTP/TLS/RC4-MD5; 02 Nov 2011 17:50:49 -0400
Received: from PRVPEXVS03.corp.twcable.com ([10.136.163.27]) by PRVPEXHUB02.corp.twcable.com ([10.136.163.11]) with mapi; Wed, 2 Nov 2011 17:55:06 -0400
From: "Howard, Lee" <lee.howard@twcable.com>
To: Ole Troan <ot@cisco.com>
Date: Wed, 2 Nov 2011 17:55:05 -0400
Thread-Topic: [homenet] another routing option
Thread-Index: AcyZqRAJhSuUFwYATayAkuzf5lt4iAAANs6Q
Message-ID: <DCC302FAA9FE5F4BBA4DCAD46569377914517EEBAA@PRVPEXVS03.corp.twcable.com>
References: <DCC302FAA9FE5F4BBA4DCAD46569377914517EE5FD@PRVPEXVS03.corp.twcable.com> <1864C465-E1AD-4F47-9E9E-5E26B84D2DFC@cisco.com>
In-Reply-To: <1864C465-E1AD-4F47-9E9E-5E26B84D2DFC@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] another routing option
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 02 Nov 2011 21:55:08 -0000

> -----Original Message-----
> From: Ole Troan [mailto:ot@cisco.com]
> Sent: Wednesday, November 02, 2011 12:46 PM
> To: Howard, Lee
> Cc: homenet@ietf.org Group
> Subject: Re: [homenet] another routing option
>
> Howard,
>
> > I've said that I don't think we need a full dynamic routing protocol.  =
There are other
> options for discovering an available path.  To stimulate creative thinkin=
g, I've written a draft
> proposing one alternative that should be light to implement in home gatew=
ays:
> http://www.asgard.org/images/draft-howard-up-pio-00.txt
> > If it is interesting, there's more work to be done on it; I could publi=
sh it after the pre-
> meeting publication blackout ends.
>
> aren't you in the end just going to reinvent RAs as a distance vector rou=
ting protocol...?

I wanted to debate the point, but I have to conced it.  Yes, that's pretty =
much true.

Lee

>
> cheers,
> Ole
>


This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

From jari.arkko@piuha.net  Wed Nov  2 15:16:56 2011
Return-Path: <jari.arkko@piuha.net>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3264E11E80A5 for <homenet@ietfa.amsl.com>; Wed,  2 Nov 2011 15:16:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.585
X-Spam-Level: 
X-Spam-Status: No, score=-102.585 tagged_above=-999 required=5 tests=[AWL=0.014, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oT2puMrLylT0 for <homenet@ietfa.amsl.com>; Wed,  2 Nov 2011 15:16:55 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id 981BE11E8091 for <homenet@ietf.org>; Wed,  2 Nov 2011 15:16:55 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id E5E772E9F2; Thu,  3 Nov 2011 00:16:54 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K-0TyeiRjCCT; Thu,  3 Nov 2011 00:16:54 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 59EC42E9F1; Thu,  3 Nov 2011 00:16:54 +0200 (EET)
Message-ID: <4EB1C155.5020303@piuha.net>
Date: Thu, 03 Nov 2011 00:16:53 +0200
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: Ole Troan <ot@cisco.com>
References: <DCC302FAA9FE5F4BBA4DCAD46569377914517EE5FD@PRVPEXVS03.corp.twcable.com> <1864C465-E1AD-4F47-9E9E-5E26B84D2DFC@cisco.com>
In-Reply-To: <1864C465-E1AD-4F47-9E9E-5E26B84D2DFC@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "Howard, Lee" <lee.howard@twcable.com>, "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] another routing option
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 02 Nov 2011 22:16:56 -0000

Thanks for writing this up, Howard.

And I think all options should be on the table. That being said, my #1 option for routing was actually RIP, because the code was already on many boxes. I also like OSPF, because it is in theory more robust and works in pretty much under all circumstances.

There has been a series of proposals over the years on using router advertisements for simple default routing. Look for "MANEMO" from the archives, for instance. There are a number of possible designs, from the very simple design that can't even take a look to a full-blown routing protocol carried in RAs. We didn't take that work up for variety of reasons at the time, including some resistance on overloading RAs for other purposes.

Using RAs is certainly a possible approach, though I would probably prefer to just use RIP if "simple" is our guideline, because ultimately that would lead to less new protocols and at least in some cases less new code. Just my opinion, of course.

Jari


From jyrki.soini@teliasonera.com  Thu Nov  3 01:48:29 2011
Return-Path: <jyrki.soini@teliasonera.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1C4511E80A6 for <homenet@ietfa.amsl.com>; Thu,  3 Nov 2011 01:48:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zNwoSZhaam6e for <homenet@ietfa.amsl.com>; Thu,  3 Nov 2011 01:48:29 -0700 (PDT)
Received: from smtp.tele.fi (smtp.tele.fi [192.89.123.25]) by ietfa.amsl.com (Postfix) with ESMTP id 53EF011E80A3 for <homenet@ietf.org>; Thu,  3 Nov 2011 01:48:29 -0700 (PDT)
X-Originating-Ip: [131.177.70.25]
Received: from smtp.extra.sonera.fi (smtp.extra.sonera.fi [131.177.70.25]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.tele.fi (Postfix) with ESMTP id 69E1124CE; Thu,  3 Nov 2011 10:48:27 +0200 (EET)
Received: from smtp.dave.sonera.fi (smtp.dave.sonera.fi [131.177.120.25]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.extra.sonera.fi (Postfix) with ESMTP id F31F31EE9E5; Thu,  3 Nov 2011 10:47:59 +0200 (EET)
Received: from [131.177.116.236] (ws936.secureuser.sonera.fi [131.177.116.236]) by smtp.dave.sonera.fi (Postfix) with ESMTP id 98A7058038; Thu,  3 Nov 2011 10:48:25 +0200 (EET)
Message-ID: <4EB25559.7070307@teliasonera.com>
Date: Thu, 03 Nov 2011 10:48:25 +0200
From: Jyrki Soini <jyrki.soini@teliasonera.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:8.0) Gecko/20111019 Thunderbird/8.0
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
References: <4EAD1B77.6010602@piuha.net> <4EB184B8.4000901@cisco.com> <4EB18CEC.1@piuha.net>
In-Reply-To: <4EB18CEC.1@piuha.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Erik Nordmark <nordmark@cisco.com>, "homenet@ietf.org" <homenet@ietf.org>
Subject: Re: [homenet] Prefix stability requirements in draft-arkko-homenet-prefix-assignment-00
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 03 Nov 2011 08:48:30 -0000

On 21:59, Jari Arkko wrote:
> Erik,
>
>> OK. There are probably some important details when there are multiple routers wanting to use different prefixes on the same link. If I've had the routers in the den happily working for a year, and I decide to bring in a router from the garage (which has been in use for a week) and connect it to the routers in the den, then a reasonable default behavior would be to keep the prefix that has in use on that link for a year.
>>
>> Some notion of "first time advertised" could be useful for that type of tiebreakers.
>
> I agree, both about the requirement and that we're probably still missing some of the important details.
>
> But I'll just point out one additional thing. Since only devices (not networks) can have memory and identity, it is hard in general to decide what changed. Say, if you had just one router in the den and another one in the garage, both installed at the same time and then you move the garage router to the den. From a human perspective it would probably make sense to keep the den prefix unchanged, but how do the routers know this? Just looking at the situation locally may not help in this case. There's one router's opinion against the other router's opinion. The times are identical. You could of course inspect whether topology around you changed and infer which one of the devices got moved. But it is hard.
>
> Jari
>
>

How about calculating the shortest path to the router that has
originated the Usable Address LSA for the candidate prefixes?
Instead of having the highest number OSPFv3 router to select the
address give priority to the router with lower cost path to UA
originator. If both routers have the same path cost use OSPFv3
router-id as tie-breaker.

Router could detect movement if next hop towards UA originator has changed.

The drawback would be more complex computing when the prefix
would be allocated for the link.

--
Jyrki

From mcr@sandelman.ca  Thu Nov  3 11:44:52 2011
Return-Path: <mcr@sandelman.ca>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 93B761F0C7C for <homenet@ietfa.amsl.com>; Thu,  3 Nov 2011 11:44:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.887
X-Spam-Level: 
X-Spam-Status: No, score=-1.887 tagged_above=-999 required=5 tests=[AWL=0.067,  BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0Q0csE-KTBG8 for <homenet@ietfa.amsl.com>; Thu,  3 Nov 2011 11:44:52 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id 2275F1F0C40 for <homenet@ietf.org>; Thu,  3 Nov 2011 11:44:51 -0700 (PDT)
Received: from marajade.sandelman.ca (unknown [132.213.238.4]) by relay.sandelman.ca (Postfix) with ESMTPS id 24070343CB for <homenet@ietf.org>; Thu,  3 Nov 2011 14:43:32 -0400 (EDT)
Received: by marajade.sandelman.ca (Postfix, from userid 179) id A9E9298CAF; Thu,  3 Nov 2011 14:45:29 -0400 (EDT)
Received: from marajade.sandelman.ca (localhost [127.0.0.1]) by marajade.sandelman.ca (Postfix) with ESMTP id A420798B2E for <homenet@ietf.org>; Thu,  3 Nov 2011 14:45:29 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: "homenet@ietf.org" <homenet@ietf.org>
In-Reply-To: <4EB25559.7070307@teliasonera.com>
References: <4EAD1B77.6010602@piuha.net> <4EB184B8.4000901@cisco.com> <4EB18CEC.1@piuha.net> <4EB25559.7070307@teliasonera.com>
X-Mailer: MH-E 8.1; nmh 1.3-dev; XEmacs 21.4 (patch 22)
Date: Thu, 03 Nov 2011 14:45:29 -0400
Message-ID: <24715.1320345929@marajade.sandelman.ca>
Sender: mcr@sandelman.ca
Subject: Re: [homenet] Prefix stability requirements in draft-arkko-homenet-prefix-assignment-00
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 03 Nov 2011 18:44:52 -0000

    >>> OK. There are probably some important details when there are
    >>> multiple routers wanting to use different prefixes on the same
    >>> link. If I've had the routers in the den happily working for a
    >>> year, and I decide to bring in a router from the garage (which
    >>> has been in use for a week) and connect it to the routers in the
    >>> den, then a reasonable default behavior would be to keep the
    >>> prefix that has in use on that link for a year.

I just want to add, that if the (newly acquired) router in the garage
doesn't seem to be working right, perhaps due to too much snow, not
enough electrons, too thick walls (wifi), etc. that bringing it into the
Den to debug it is quite likely.  And it's likely to move again soon.

    >> same time and then you move the garage router to the den. From a
    >> human perspective it would probably make sense to keep the den
    >> prefix unchanged, but how do the routers know this? Just looking
    >> at the situation locally may not help in this case. There's one
    >> router's opinion against the other router's opinion. The times
    >> are identical. You could of course inspect whether topology
    >> around you changed and infer which one of the devices got
    >> moved. But it is hard.

If they were installed at the same time, then neither has really
corrupted more hosts with it's prefix than the other.   I think that it
really doesn't matter which prefix remains, and if you do care, then
it's not zero-conf.

    Jyrki> How about calculating the shortest path to the router that
    Jyrki> has originated the Usable Address LSA for the candidate
    Jyrki> prefixes?  Instead of having the highest number OSPFv3 router
    Jyrki> to select the address give priority to the router with lower
    Jyrki> cost path to UA originator. If both routers have the same
    Jyrki> path cost use OSPFv3 router-id as tie-breaker.

I generally like this better.
For many installations with mostly only two layers (router in basement
where internet comes in, routers in parts of the house where more ports
or stronger wifi signal is necessary), it turns out to be the same
effectively. 

Reading draft-arkko-homenet-prefix-assignment-00, I felt rather squemish
about the fact that the routers basically pick prefixes without
consulting the edge router who owns that prefix, but I grew to like it.

-- 
]       He who is tired of Weird Al is tired of life!           |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
   Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE>
	               then sign the petition. 

From mrossi@swin.edu.au  Thu Nov  3 21:25:07 2011
Return-Path: <mrossi@swin.edu.au>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33C1B11E8081 for <homenet@ietfa.amsl.com>; Thu,  3 Nov 2011 21:25:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level: 
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0bBC2E701S-5 for <homenet@ietfa.amsl.com>; Thu,  3 Nov 2011 21:25:06 -0700 (PDT)
Received: from gpo4.cc.swin.edu.au (gpo4.cc.swin.edu.au [136.186.1.33]) by ietfa.amsl.com (Postfix) with ESMTP id 90B8311E8073 for <homenet@ietf.org>; Thu,  3 Nov 2011 21:25:05 -0700 (PDT)
Received: from mrossi.caia.swin.edu.au (mrossi.caia.swin.edu.au [136.186.229.109]) by gpo4.cc.swin.edu.au (8.14.3/8.14.3) with ESMTP id pA44OrjV012143 for <homenet@ietf.org>; Fri, 4 Nov 2011 15:25:02 +1100
Message-ID: <4EB36915.2090001@swin.edu.au>
Date: Fri, 04 Nov 2011 15:24:53 +1100
From: Mattia Rossi <mrossi@swin.edu.au>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:7.0.1) Gecko/20111004 Thunderbird/7.0.1
MIME-Version: 1.0
To: homenet@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [homenet] Does the draft-arkko-homenet-prefix-assignment-01 block the chances for policies in multihomed networks?
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 04 Nov 2011 04:25:07 -0000

I'm not sure if I'm missing anything here, but as far as I understood, 
the draft does not allow having multiple prefixes within a subnet 
segment. Is tht right?

So in the following case:

    subnet 1    subnet 2
       |            |
      R1           R2
       |            |
       +------------+
       |            |
      H1 - (ISP1)  H2 - (ISP2)


If I want to be able to reach the Internet from a host in subnet 1 via 
H1 or H2, depending on my policy in place, I need to use prefixes of 
both , H1's and H2's prefix pool in subnet 1. So the host can use 
addresses from both subprefixes and make sure that the return packets 
are routed back to the host properly.

draft-arkko-homenet-prefix-assignment-01 anyhow seems to allow only one 
prefix per subnet, e.g. R1 would only get to use one prefix for subnet 
1, which screws the host in subnet1 which might have a policy of using 
H1 for video and H2 for other or any of the other problems discussed in 
this list.

As said, I might miss something here, but it's not clear to me from the 
draft.

Mat

-- 
Mattia Rossi
R&D Engineer
Centre for Advanced Internet Architectures (CAIA)
Faculty of ICT
Swinburne University of Technology
Hawthorn
3122 VIC
Australia

email: mrossi@swin.edu.au
phone: +61 3 9214 4844

From mrossi@swin.edu.au  Thu Nov  3 21:30:48 2011
Return-Path: <mrossi@swin.edu.au>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D4FE11E8081 for <homenet@ietfa.amsl.com>; Thu,  3 Nov 2011 21:30:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level: 
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dYHGLwRUG5Ti for <homenet@ietfa.amsl.com>; Thu,  3 Nov 2011 21:30:47 -0700 (PDT)
Received: from gpo4.cc.swin.edu.au (gpo4.cc.swin.edu.au [136.186.1.33]) by ietfa.amsl.com (Postfix) with ESMTP id 023B211E8073 for <homenet@ietf.org>; Thu,  3 Nov 2011 21:30:46 -0700 (PDT)
Received: from mrossi.caia.swin.edu.au (mrossi.caia.swin.edu.au [136.186.229.109]) by gpo4.cc.swin.edu.au (8.14.3/8.14.3) with ESMTP id pA44UjbR018120 for <homenet@ietf.org>; Fri, 4 Nov 2011 15:30:45 +1100
Message-ID: <4EB36A75.4080507@swin.edu.au>
Date: Fri, 04 Nov 2011 15:30:45 +1100
From: Mattia Rossi <mrossi@swin.edu.au>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:7.0.1) Gecko/20111004 Thunderbird/7.0.1
MIME-Version: 1.0
To: homenet@ietf.org
References: <4EB36915.2090001@swin.edu.au>
In-Reply-To: <4EB36915.2090001@swin.edu.au>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [homenet] Does the draft-arkko-homenet-prefix-assignment-01 block the chances for policies in multihomed networks?
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 04 Nov 2011 04:30:48 -0000

On 04/11/2011 15:24, Mattia Rossi wrote:
[..]
>
> If I want to be able to reach the Internet from a host in subnet 1 via
> H1 or H2, depending on my policy in place, I need to use prefixes of
> both , H1's and H2's prefix pool in subnet 1.

Err.. I meant content sitting at ISP1 or ISP2 not reachable from the 
Internet (walled garden).

Mat



From acee.lindem@ericsson.com  Fri Nov  4 06:00:17 2011
Return-Path: <acee.lindem@ericsson.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0AC6D21F8C34 for <homenet@ietfa.amsl.com>; Fri,  4 Nov 2011 06:00:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.509
X-Spam-Level: 
X-Spam-Status: No, score=-6.509 tagged_above=-999 required=5 tests=[AWL=0.090,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CUI3XpDefyVe for <homenet@ietfa.amsl.com>; Fri,  4 Nov 2011 06:00:16 -0700 (PDT)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by ietfa.amsl.com (Postfix) with ESMTP id C740821F8B7B for <homenet@ietf.org>; Fri,  4 Nov 2011 06:00:15 -0700 (PDT)
Received: from eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id pA4D0EM5032557 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 4 Nov 2011 08:00:15 -0500
Received: from EUSAACMS0702.eamcs.ericsson.se ([169.254.1.105]) by eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) with mapi; Fri, 4 Nov 2011 09:00:13 -0400
From: Acee Lindem <acee.lindem@ericsson.com>
To: Mattia Rossi <mrossi@swin.edu.au>
Date: Fri, 4 Nov 2011 09:00:11 -0400
Thread-Topic: [homenet] Does the draft-arkko-homenet-prefix-assignment-01 block the chances for policies in multihomed networks?
Thread-Index: Acya8bEZs5EI8cA8SN2mid4tlEClJw==
Message-ID: <652D9B70-747E-477A-AF64-8534F274E78B@ericsson.com>
References: <4EB36915.2090001@swin.edu.au>
In-Reply-To: <4EB36915.2090001@swin.edu.au>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "homenet@ietf.org" <homenet@ietf.org>
Subject: Re: [homenet] Does the draft-arkko-homenet-prefix-assignment-01 block the chances for policies in multihomed networks?
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 04 Nov 2011 13:00:17 -0000

Hi Mattia,

On Nov 4, 2011, at 12:24 AM, Mattia Rossi wrote:

> I'm not sure if I'm missing anything here, but as far as I understood,=20
> the draft does not allow having multiple prefixes within a subnet=20
> segment. Is tht right?

No - what it avoids is two prefixes that are subnets of the same prefix adv=
ertised in a Usable Prefix TLV from being assigned on a network segment.=20

Thanks,
Acee=20





>=20
> So in the following case:
>=20
>    subnet 1    subnet 2
>       |            |
>      R1           R2
>       |            |
>       +------------+
>       |            |
>      H1 - (ISP1)  H2 - (ISP2)
>=20
>=20
> If I want to be able to reach the Internet from a host in subnet 1 via=20
> H1 or H2, depending on my policy in place, I need to use prefixes of=20
> both , H1's and H2's prefix pool in subnet 1. So the host can use=20
> addresses from both subprefixes and make sure that the return packets=20
> are routed back to the host properly.
>=20
> draft-arkko-homenet-prefix-assignment-01 anyhow seems to allow only one=20
> prefix per subnet, e.g. R1 would only get to use one prefix for subnet=20
> 1, which screws the host in subnet1 which might have a policy of using=20
> H1 for video and H2 for other or any of the other problems discussed in=20
> this list.






>=20
> As said, I might miss something here, but it's not clear to me from the=20
> draft.
>=20
> Mat
>=20
> --=20
> Mattia Rossi
> R&D Engineer
> Centre for Advanced Internet Architectures (CAIA)
> Faculty of ICT
> Swinburne University of Technology
> Hawthorn
> 3122 VIC
> Australia
>=20
> email: mrossi@swin.edu.au
> phone: +61 3 9214 4844
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet


From Laurent.Toutain@telecom-bretagne.eu  Fri Nov  4 08:30:52 2011
Return-Path: <Laurent.Toutain@telecom-bretagne.eu>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A98E721F8C44 for <homenet@ietfa.amsl.com>; Fri,  4 Nov 2011 08:30:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.924
X-Spam-Level: 
X-Spam-Status: No, score=0.924 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HELO_EQ_FR=0.35, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, SARE_HTML_USL_OBFU=1.666]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gRpuRRBHzbbL for <homenet@ietfa.amsl.com>; Fri,  4 Nov 2011 08:30:51 -0700 (PDT)
Received: from coliposte.enst-bretagne.fr (coliposte.enst-bretagne.fr [192.108.115.12]) by ietfa.amsl.com (Postfix) with ESMTP id 223B121F8C54 for <homenet@ietf.org>; Fri,  4 Nov 2011 08:30:50 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by coliposte.enst-bretagne.fr (8.13.7/8.13.7/2009.11.10) with ESMTP id pA4EldGx011008 for <homenet@ietf.org>; Fri, 4 Nov 2011 15:47:41 +0100
Received: from courrier.enst-bretagne.fr (smtps.telecom-bretagne.eu [10.29.90.4]) by coliposte.enst-bretagne.fr (8.13.7/8.13.7/2009.11.10) with ESMTP id pA4ElWTV010740 for <homenet@ietf.org>; Fri, 4 Nov 2011 15:47:36 +0100
Received: from mail-wy0-f172.google.com (passerelle-interne.enst-bretagne.fr [192.108.117.210]) (user=toutain mech=PLAIN bits=0) by courrier.enst-bretagne.fr (8.13.8/8.13.8/2010.02.22) with ESMTP id pA4ElSZk019846 for <homenet@ietf.org>; Fri, 4 Nov 2011 15:47:28 +0100
Received: by wyg30 with SMTP id 30so2795757wyg.31 for <homenet@ietf.org>; Fri, 04 Nov 2011 07:47:28 -0700 (PDT)
Received: by 10.216.180.132 with SMTP id j4mr1191834wem.95.1320418048128; Fri, 04 Nov 2011 07:47:28 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.216.198.81 with HTTP; Fri, 4 Nov 2011 07:47:07 -0700 (PDT)
In-Reply-To: <4EB36A75.4080507@swin.edu.au>
References: <4EB36915.2090001@swin.edu.au> <4EB36A75.4080507@swin.edu.au>
From: Laurent Toutain <Laurent.Toutain@telecom-bretagne.eu>
Date: Fri, 4 Nov 2011 15:47:07 +0100
Message-ID: <CABONVQY9QPd0WpUeRFroPKu7jXeLm5m3W_WN5xsQuF=kGqQ63Q@mail.gmail.com>
To: Mattia Rossi <mrossi@swin.edu.au>
Content-Type: multipart/alternative; boundary=0016367fa90fb6b87f04b0e9c830
X-Virus-Scanned: amavisd-new at enst-bretagne.fr
Cc: homenet@ietf.org
Subject: Re: [homenet] Does the draft-arkko-homenet-prefix-assignment-01 block the chances for policies in multihomed networks?
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 04 Nov 2011 15:30:52 -0000

--0016367fa90fb6b87f04b0e9c830
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Mattia,

In our proposal, we assigned a SID for each GP prefix, and I think
draft-arkko-homenet-prefix-assignment does the same. but that does not
solve completely the problem:

If a host in subnet 1 selects a prefix from H1 and routing inside the Home
Network send packets to ISP2, in-gress filtering of ISP2 will block the
traffic. The source address must be taken into account to find the ISP.
 Since GP is flooded inside the home network, every router is aware of the
provider prefixes, so routers can be modified to take into account the
source address in the forwarding process.

In [1] you will find more information on the way we solve it. The main idea
is to add another lookup instead of using the default route. When you use
the default route it means that the prefix is outside of the home network.
In that case, we use another "routing table" to find the next hop based on
the prefix included in the source address, so packets reach the right
provider. This table is built the same way, for example a shortest path to
the provider prefix.

The second problem is to inform the host of available services from
provider H1 and  provider H2. Hosts have to be aware of the prefixes they
should used to reach a service. We need to develop a protocol for that and
modify source address selection in the host.

Laurent
---

[1] de Santerre, E.G.; Jammoul, S.; Toutain, L.; , "Solving the Ingress
Filtering Issue in an IPv6 Multihomed Home Network," *Networks (ICN), 2010
Ninth International Conference on* , vol., no., pp.272-278, 11-16 April 201=
0
doi: 10.1109/ICN.2010.50

On Fri, Nov 4, 2011 at 05:30, Mattia Rossi <mrossi@swin.edu.au> wrote:

> On 04/11/2011 15:24, Mattia Rossi wrote:
> [..]
>
>
>> If I want to be able to reach the Internet from a host in subnet 1 via
>> H1 or H2, depending on my policy in place, I need to use prefixes of
>> both , H1's and H2's prefix pool in subnet 1.
>>
>
> Err.. I meant content sitting at ISP1 or ISP2 not reachable from the
> Internet (walled garden).
>
> Mat
>
>
>
> ______________________________**_________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/**listinfo/homenet<https://www.ietf.org/mail=
man/listinfo/homenet>
>



--=20
Laurent Toutain
+--- VoIP (recommended) ---+----------- T=E9l=E9com Bretagne -----------+
| Tel: +33 2 22 06 8156    | Tel: + 33 2 99 12 7026                 | Visit
:
| Fax: +33 2 22 06 8445    | Fax: +33 2 99 12 7030                  |
http://class.touta.in
| Laurent@Touta.in         | Laurent.Toutain@Telecom-Bretagne.eu    |
+--------------------------+----------------------------------------+

--0016367fa90fb6b87f04b0e9c830
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Mattia,<div><br></div><div>In our proposal, we assigned a SID for each G=
P prefix, and I think draft-arkko-homenet-prefix-assignment does the same. =
but that does not solve completely the problem:</div><div><br></div><div>

If a host in subnet 1 selects a prefix from H1 and routing inside the Home =
Network send packets to ISP2, in-gress filtering of ISP2 will block the tra=
ffic. The source address must be taken into account to find the ISP. =A0Sin=
ce GP is flooded inside the home network, every router is aware of the prov=
ider prefixes, so routers can be modified to take into account the source a=
ddress in the forwarding process.=A0</div>

<div><br></div><div>In [1] you will find more information on the way we sol=
ve it. The main idea is to add another lookup instead of using the default =
route. When you use the default route it means that the prefix is outside o=
f the home network. In that case, we use another &quot;routing table&quot; =
to find the next hop based on the prefix included in the source address, so=
 packets reach the right provider. This table is built the same way, for ex=
ample a shortest path to the provider prefix. =A0</div>

<div><br></div><div>The second problem is to inform the host of available s=
ervices from provider H1 and =A0provider H2. Hosts have to be aware of the =
prefixes they should used to reach a service. We need to develop a protocol=
 for that and modify source address selection in the host.=A0</div>

<div><br></div><div>Laurent</div><div>---</div><div><br></div><div>[1]=A0<s=
pan class=3D"Apple-style-span" style=3D"font-family: Times; font-size: medi=
um; ">de Santerre, E.G.; Jammoul, S.; Toutain, L.; , &quot;Solving the Ingr=
ess Filtering Issue in an IPv6 Multihomed Home Network,&quot;=A0</span><i s=
tyle=3D"font-family: Times; font-size: medium; ">Networks (ICN), 2010 Ninth=
 International Conference on</i><span class=3D"Apple-style-span" style=3D"f=
ont-family: Times; font-size: medium; ">=A0, vol., no., pp.272-278, 11-16 A=
pril 2010</span><br style=3D"font-family: Times; font-size: medium; ">

<span class=3D"Apple-style-span" style=3D"font-family: Times; font-size: me=
dium; ">doi: 10.1109/ICN.2010.50=A0</span><br><br><div class=3D"gmail_quote=
">On Fri, Nov 4, 2011 at 05:30, Mattia Rossi <span dir=3D"ltr">&lt;<a href=
=3D"mailto:mrossi@swin.edu.au">mrossi@swin.edu.au</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">On 04/11/2011 15:24, Mattia Rossi wrote:<br=
>
[..]<div class=3D"im"><br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
If I want to be able to reach the Internet from a host in subnet 1 via<br>
H1 or H2, depending on my policy in place, I need to use prefixes of<br>
both , H1&#39;s and H2&#39;s prefix pool in subnet 1.<br>
</blockquote>
<br></div>
Err.. I meant content sitting at ISP1 or ISP2 not reachable from the Intern=
et (walled garden).<br>
<br>
Mat<div class=3D"HOEnZb"><div class=3D"h5"><br>
<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>
</div></div></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>=
Laurent Toutain<br><font face=3D"&#39;courier new&#39;, monospace">+--- VoI=
P (recommended) ---+----------- T=E9l=E9com Bretagne -----------+<br>| Tel:=
 +33 2 22 06 8156 =A0 =A0| Tel: + 33 2 99 12 7026 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 | Visit :<br>

| Fax: +33 2 22 06 8445 =A0 =A0| Fax: +33 2 99 12 7030 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0| =A0<a href=3D"http://class.touta.in" target=3D"_blank">htt=
p://class.touta.in</a><br>| Laurent@Touta.in =A0 =A0 =A0 =A0 | Laurent.Tout=
ain@Telecom-Bretagne.eu =A0 =A0|<br>

+--------------------------+----------------------------------------+</font=
><br>
</div>

--0016367fa90fb6b87f04b0e9c830--

From lee.howard@twcable.com  Fri Nov  4 13:44:14 2011
Return-Path: <lee.howard@twcable.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0197E11E80AC for <homenet@ietfa.amsl.com>; Fri,  4 Nov 2011 13:44:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.728
X-Spam-Level: 
X-Spam-Status: No, score=-0.728 tagged_above=-999 required=5 tests=[AWL=-0.265, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x-uJJAEoYd0V for <homenet@ietfa.amsl.com>; Fri,  4 Nov 2011 13:44:13 -0700 (PDT)
Received: from cdpipgw02.twcable.com (cdpipgw02.twcable.com [165.237.59.23]) by ietfa.amsl.com (Postfix) with ESMTP id 4EDCD11E8082 for <homenet@ietf.org>; Fri,  4 Nov 2011 13:44:13 -0700 (PDT)
X-SENDER-IP: 10.136.163.12
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.69,456,1315195200"; d="scan'208";a="278436934"
Received: from unknown (HELO PRVPEXHUB03.corp.twcable.com) ([10.136.163.12]) by cdpipgw02.twcable.com with ESMTP/TLS/RC4-MD5; 04 Nov 2011 16:39:49 -0400
Received: from PRVPEXVS03.corp.twcable.com ([10.136.163.27]) by PRVPEXHUB03.corp.twcable.com ([10.136.163.12]) with mapi; Fri, 4 Nov 2011 16:44:12 -0400
From: "Howard, Lee" <lee.howard@twcable.com>
To: "homenet@ietf.org Group" <homenet@ietf.org>
Date: Fri, 4 Nov 2011 16:44:12 -0400
Thread-Topic: more comments on draft-arkko-homenet-prefix-assignment
Thread-Index: AcybMoIrZ8Dyt9N1Rh6GoTb15bPjEw==
Message-ID: <DCC302FAA9FE5F4BBA4DCAD46569377914518AFAE5@PRVPEXVS03.corp.twcable.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [homenet] more comments on draft-arkko-homenet-prefix-assignment
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 04 Nov 2011 20:44:14 -0000

This requirement requires justification:
 o  The assignments must be stable across reboots, power cycling,
      router software updates, and preferably, should be stable across
      simple network changes such as adding a new device on the stub
      network segments.

*Why* is that an RFC2119 MUST?
Why is that an RFC2219 SHOULD?  When I see a "should" I like to see an expl=
anation, since the definition is "Do this unless you have a good reason not=
 to," and implementers need guidance about when they might violate that.
I think the reason (as discussed on list a couple of weeks ago) is that whe=
n a router reboots, if it gets renumbered, the hosts attached to it still h=
ave DHCP leases that haven't expired but won't be able to use those address=
es.


   The generation
   of ULAs in this manner -- and indeed even the question of whether
   ULAs are needed -- is outside the scope of this memo, however.

Why is this out of scope?  Will we have a separate document to describe thi=
s?  No addressing or routing solution is complete until it can handle ULA (=
unless we find a way to do away with ULA).


  The lifetime of the prefix SHOULD be advertised as a
   reasonably long period, at least 48 hours or the lifetime of the
   assigned prefixes, whichever is smaller.

Why?


   To support a variety of
   IPv6-only hosts in these networks, the router needs to ensure that
   sufficient DNS discovery mechanisms are enabled.

What kind of variety do you mean?  By "DNS discovery" you mean
methods to advertise resolvers to hosts, not methods to discover
name-address mappings.


   When an OSPFv3 Router receives a global prefix through DHCPv6 prefix
   delegation, manual configuration, or other means, it will advertise
   this prefix by including the Usable Prefix TLV in its OSPFv3 AC LSA.
   This will trigger prefix assignment for auto-configured OSPFv3
   routers within the routing domain including the originating OSPFv3
   router.

If a subtended router is manually configured with a subnet of the /48
assigned to the border router, will both be advertsied as Usable Prefixes?
If so, will other routers try to make Assigned Prefixes from both?


  When an OSPFv3 Router receives a global prefix through DHCPv6 prefix
   delegation, manual configuration, or other means, it will advertise
   this prefix by including the Usable Prefix TLV in its OSPFv3 AC LSA.

Shouldn't the border router assign its local prefix before sending the full
/48 Usable Prefix?  I suppose it doesn't have to be, but that means that
the border sends the Usable Prefix, and all attached routers fight over
who has the highest Router ID; then that router provides the Assigned
Prefix to the link.  It works, it just seems funny to me.


1.  The OSPFv3 Router will determine whether there are any other
       OSPFv3 Routers connected to the same link by examining its list
       of neighbors.

There's at least one, since this algorithm was triggered by receiving an
AC LSA.


Lee


This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

From russw@riw.us  Sat Nov  5 06:12:26 2011
Return-Path: <russw@riw.us>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B359C21F8497 for <homenet@ietfa.amsl.com>; Sat,  5 Nov 2011 06:12:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.377
X-Spam-Level: 
X-Spam-Status: No, score=-2.377 tagged_above=-999 required=5 tests=[AWL=0.222,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yjwZzHoftBRh for <homenet@ietfa.amsl.com>; Sat,  5 Nov 2011 06:12:26 -0700 (PDT)
Received: from ecbiz91.inmotionhosting.com (ecbiz91.inmotionhosting.com [173.205.124.250]) by ietfa.amsl.com (Postfix) with ESMTP id 41A3921F8492 for <homenet@ietf.org>; Sat,  5 Nov 2011 06:12:26 -0700 (PDT)
Received: from rtp-isp-nat1.cisco.com ([64.102.254.33]:47837 helo=[10.117.153.102]) by ecbiz91.inmotionhosting.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <russw@riw.us>) id 1RMg2r-0005lt-7p for homenet@ietf.org; Sat, 05 Nov 2011 09:12:25 -0400
Message-ID: <4EB5363D.3010902@riw.us>
Date: Sat, 05 Nov 2011 09:12:29 -0400
From: Russ White <russw@riw.us>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: homenet@ietf.org
References: <4EAD1B77.6010602@piuha.net> <4EB184B8.4000901@cisco.com> <4EB18CEC.1@piuha.net> <4EB25559.7070307@teliasonera.com>
In-Reply-To: <4EB25559.7070307@teliasonera.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - ecbiz91.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - riw.us
Subject: Re: [homenet] Prefix stability requirements in draft-arkko-homenet-prefix-assignment-00
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 05 Nov 2011 13:12:26 -0000

> How about calculating the shortest path to the router that has
> originated the Usable Address LSA for the candidate prefixes?
> Instead of having the highest number OSPFv3 router to select the
> address give priority to the router with lower cost path to UA
> originator. If both routers have the same path cost use OSPFv3
> router-id as tie-breaker.

This is an interesting idea... The main problems are:

1. How does this edge router know it's the edge router? There must be 
some signaling from "upstream" to tell it, "you have a connection to the 
outside world."

2. How do we resolve multiple devices at the same distance from the edge 
router? Should we include topological as well as physical distance (if 
possible)?

3. What if there are multiple edge devices? I assume the one device 
would/could have multiple addresses in this case?

:-)

Russ

From jari.arkko@piuha.net  Sat Nov  5 11:43:33 2011
Return-Path: <jari.arkko@piuha.net>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79CDB21F8753 for <homenet@ietfa.amsl.com>; Sat,  5 Nov 2011 11:43:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.519
X-Spam-Level: 
X-Spam-Status: No, score=-102.519 tagged_above=-999 required=5 tests=[AWL=0.080, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ua8vNJV8nqYh for <homenet@ietfa.amsl.com>; Sat,  5 Nov 2011 11:43:32 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id A5C5921F867F for <homenet@ietf.org>; Sat,  5 Nov 2011 11:43:24 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id BA0072CC5A; Sat,  5 Nov 2011 20:43:22 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w--X1XC1oYTn; Sat,  5 Nov 2011 20:43:22 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id DBAAA2CC56; Sat,  5 Nov 2011 20:43:21 +0200 (EET)
Message-ID: <4EB583C8.5030907@piuha.net>
Date: Sat, 05 Nov 2011 20:43:20 +0200
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: "Howard, Lee" <lee.howard@twcable.com>
References: <DCC302FAA9FE5F4BBA4DCAD46569377914518AFAE5@PRVPEXVS03.corp.twcable.com>
In-Reply-To: <DCC302FAA9FE5F4BBA4DCAD46569377914518AFAE5@PRVPEXVS03.corp.twcable.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] more comments on draft-arkko-homenet-prefix-assignment
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 05 Nov 2011 18:43:33 -0000

Lee,

Thanks for your feedback and questions. Some answers inline:

> This requirement requires justification:
>   o  The assignments must be stable across reboots, power cycling,
>        router software updates, and preferably, should be stable across
>        simple network changes such as adding a new device on the stub
>        network segments.
>
> *Why* is that an RFC2119 MUST?
> Why is that an RFC2219 SHOULD?  When I see a "should" I like to see an explanation, since the definition is "Do this unless you have a good reason not to," and implementers need guidance about when they might violate that.
> I think the reason (as discussed on list a couple of weeks ago) is that when a router reboots, if it gets renumbered, the hosts attached to it still have DHCP leases that haven't expired but won't be able to use those addresses.

(I did not use RFC 2119 keywords, by the way.)

The reason that you give is the valid reason. If a router is power-cycled and the hosts still have old prefix values, this may result in some breakage. Power cycling may be frequent, e.g., many people regularly turn off their devices. (Not me, how else would I heat my house?)

Real network changes are less frequent, so handling them is not so critical.

But these should be stated in the draft, not just here on the mailing list. I will add them.

>
>
>     The generation
>     of ULAs in this manner -- and indeed even the question of whether
>     ULAs are needed -- is outside the scope of this memo, however.
>
> Why is this out of scope?  Will we have a separate document to describe this?  No addressing or routing solution is complete until it can handle ULA (unless we find a way to do away with ULA).

It was simply outside the scope because I think the mechanisms of distributing prefixes around are separable from the question of what prefix types are used.

I was thinking that we need another document on the use of ULAs, and it would of course reference this spec for the actual distribution within the network.

(But I confess there may be a small personal bias in this decision about the scope as well. I don't seem to be quite as convinced about the blessings of ULAs as some other people in the working group :-)

>
>
>    The lifetime of the prefix SHOULD be advertised as a
>     reasonably long period, at least 48 hours or the lifetime of the
>     assigned prefixes, whichever is smaller.
>
> Why?

Because it would be harmful to have different hosts in the home add/remove prefixes. Sufficiently long lifetimes ensure that a temporary radio glitch or packet loss does not remove your prefixes.

But maybe this should be outside the scope of this document, it is more of an operational consideration. Or not... since there is no operator in the homes the defaults need to be reasonable. Your thoughts?

>
>
>     To support a variety of
>     IPv6-only hosts in these networks, the router needs to ensure that
>     sufficient DNS discovery mechanisms are enabled.
>
> What kind of variety do you mean?

For instance, hosts that support only DHCPv6-based DNS discovery. Hosts that support only RFC 5006 based DNS discovery.

>    By "DNS discovery" you mean
> methods to advertise resolvers to hosts, not methods to discover
> name-address mappings.

Yes.

>
>
>     When an OSPFv3 Router receives a global prefix through DHCPv6 prefix
>     delegation, manual configuration, or other means, it will advertise
>     this prefix by including the Usable Prefix TLV in its OSPFv3 AC LSA.
>     This will trigger prefix assignment for auto-configured OSPFv3
>     routers within the routing domain including the originating OSPFv3
>     router.
>
> If a subtended router is manually configured with a subnet of the /48
> assigned to the border router, will both be advertsied as Usable Prefixes?
> If so, will other routers try to make Assigned Prefixes from both?

Good question. This probably needs further elaboration in the spec.

>
>
>    When an OSPFv3 Router receives a global prefix through DHCPv6 prefix
>     delegation, manual configuration, or other means, it will advertise
>     this prefix by including the Usable Prefix TLV in its OSPFv3 AC LSA.
>
> Shouldn't the border router assign its local prefix before sending the full
> /48 Usable Prefix?  I suppose it doesn't have to be, but that means that
> the border sends the Usable Prefix, and all attached routers fight over
> who has the highest Router ID; then that router provides the Assigned
> Prefix to the link.  It works, it just seems funny to me.

Good point. Maybe we need to think about this in a more fundamental way as well, not sure if there are some boot order issues where this might happen later, too. Or maybe not. On a stable network the routers remember what prefixes they ended up using, and attempt to reuse those upon reboots.

>
>
> 1.  The OSPFv3 Router will determine whether there are any other
>         OSPFv3 Routers connected to the same link by examining its list
>         of neighbors.
>
> There's at least one, since this algorithm was triggered by receiving an
> AC LSA.
>

Ok. Need to look at that.

Thanks again for the feedback. There is certainly material here for updating the draft.

Jari


From Ray.Bellis@nominet.org.uk  Mon Nov  7 07:34:17 2011
Return-Path: <Ray.Bellis@nominet.org.uk>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1824221F8C09 for <homenet@ietfa.amsl.com>; Mon,  7 Nov 2011 07:34:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.606
X-Spam-Level: 
X-Spam-Status: No, score=-9.606 tagged_above=-999 required=5 tests=[AWL=0.992,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1Yrbdr3o6Iwg for <homenet@ietfa.amsl.com>; Mon,  7 Nov 2011 07:34:12 -0800 (PST)
Received: from mx4.nominet.org.uk (mail.nominet.org.uk [213.248.199.24]) by ietfa.amsl.com (Postfix) with ESMTP id E282921F8C07 for <homenet@ietf.org>; Mon,  7 Nov 2011 07:34:10 -0800 (PST)
DomainKey-Signature: s=main.dk.nominet.selector; d=nominet.org.uk; c=nofws; q=dns; h=X-IronPort-AV:Received:Received:From:To:Subject: Thread-Topic:Thread-Index:Date:Message-ID:Accept-Language: Content-Language:X-MS-Has-Attach:X-MS-TNEF-Correlator: Content-Type:MIME-Version; b=uuoVHaEsTzAVLHfJLgJp5msj3jt6wsMoGik9uSeVK6fQ61VkX99CWfFJ btPCymXhL6AwxHW871igFX1smt1xdpDwkQHRw2KY0GVqxvv6ZD+vEfJf/ QkHdUpwkWgKzJR/;
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nominet.org.uk; i=Ray.Bellis@nominet.org.uk; q=dns/txt; s=main.dkim.nominet.selector; t=1320680052; x=1352216052; h=from:sender:reply-to:subject:date:message-id:to:cc: mime-version:content-transfer-encoding:content-id: content-description:resent-date:resent-from:resent-sender: resent-to:resent-cc:resent-message-id:in-reply-to: references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:list-owner:list-archive; z=From:=20Ray=20Bellis=20<Ray.Bellis@nominet.org.uk> |Subject:=20IETF82=20-=20session=20administrivia|Date:=20 Mon,=207=20Nov=202011=2015:34:08=20+0000|Message-ID:=20<D 7D37681-22D1-4799-AF92-009C5A630C32@nominet.org.uk>|To: =20"homenet@ietf.org"=20<homenet@ietf.org>|MIME-Version: =201.0; bh=h5nbt8h5ta2mCgydEu0vPx+AsJ9fwMJEd6+w7+3kYrA=; b=MubgUzBVzfQJ+ZA3/0vRJVI2aEUokGSBUDiJqkB8EbefJoeq8ecfYLYP gyy55S3RV0KJOBroKXRllAWtiy+hPQefPxEfPNeF7CPiJ34pFSyN7Q6Cj mKQiyFAYSWJpSaB;
X-IronPort-AV: E=Sophos;i="4.69,470,1315177200"; d="scan'208,217";a="29375896"
Received: from wds-exc2.okna.nominet.org.uk ([213.248.197.145]) by mx4.nominet.org.uk with ESMTP; 07 Nov 2011 15:34:09 +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%19]) with mapi; Mon, 7 Nov 2011 15:34:08 +0000
From: Ray Bellis <Ray.Bellis@nominet.org.uk>
To: "homenet@ietf.org" <homenet@ietf.org>
Thread-Topic: IETF82 - session administrivia
Thread-Index: AQHMnWKwbPcrGXp+wE6Xaw5tagVsZw==
Date: Mon, 7 Nov 2011 15:34:08 +0000
Message-ID: <D7D37681-22D1-4799-AF92-009C5A630C32@nominet.org.uk>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_D7D3768122D14799AF92009C5A630C32nominetorguk_"
MIME-Version: 1.0
Subject: [homenet] IETF82 - session administrivia
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Nov 2011 15:34:17 -0000

--_000_D7D3768122D14799AF92009C5A630C32nominetorguk_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

At the moment the planned agenda for next week's WG session is unchanged fr=
om the one posted last Wednesday, and online at http://tools.ietf.org/wg/ho=
menet/agenda

If you are scheduled to talk, please if _at all possible_ get your presenta=
tion materials to the Chairs by the evening of Sunday 13th.

If you are prepared to act as a note taker or jabber relay please let us kn=
ow ASAP so that we needn't spend valuable time cajoling people to do that a=
t the start of the session.

thanks,

Ray and Mark


--_000_D7D3768122D14799AF92009C5A630C32nominetorguk_
Content-Type: text/html; charset="us-ascii"
Content-ID: <1cbba56c-90f4-4bd4-98bb-3db81e2c4a3b>
Content-Transfer-Encoding: quoted-printable

<html><head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -we=
bkit-line-break: after-white-space; ">At the moment the planned agenda for =
next week's WG session is unchanged from the one posted last Wednesday, and=
 online at&nbsp;<a href=3D"http://tools.ietf.org/wg/homenet/agenda">http://=
tools.ietf.org/wg/homenet/agenda</a><div><br></div><div>If you are schedule=
d to talk, please if _at all possible_ get your presentation materials to t=
he Chairs by the evening of Sunday 13th.</div><div><br></div><div>If you ar=
e prepared to act as a note taker or jabber relay please let us know ASAP s=
o that we needn't spend valuable time cajoling people to do that at the sta=
rt of the session.</div><div><br></div><div>thanks,</div><div><br></div><di=
v>Ray and Mark</div><div><br></div></body></html>=

--_000_D7D3768122D14799AF92009C5A630C32nominetorguk_--

From mcr@sandelman.ca  Mon Nov  7 07:38:57 2011
Return-Path: <mcr@sandelman.ca>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 461E921F8512 for <homenet@ietfa.amsl.com>; Mon,  7 Nov 2011 07:38:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.892
X-Spam-Level: 
X-Spam-Status: No, score=-1.892 tagged_above=-999 required=5 tests=[AWL=0.062,  BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SqxzRPtpf1Um for <homenet@ietfa.amsl.com>; Mon,  7 Nov 2011 07:38:52 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id AC4A121F85A4 for <homenet@ietf.org>; Mon,  7 Nov 2011 07:38:52 -0800 (PST)
Received: from marajade.sandelman.ca (unknown [132.213.238.4]) by relay.sandelman.ca (Postfix) with ESMTPS id E5C2B343CF for <homenet@ietf.org>; Mon,  7 Nov 2011 10:37:31 -0500 (EST)
Received: by marajade.sandelman.ca (Postfix, from userid 179) id 0B9CC98CAF; Mon,  7 Nov 2011 10:39:53 -0500 (EST)
Received: from marajade.sandelman.ca (localhost [127.0.0.1]) by marajade.sandelman.ca (Postfix) with ESMTP id F075D98B2E for <homenet@ietf.org>; Mon,  7 Nov 2011 10:39:53 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ca>
To: "homenet@ietf.org Group" <homenet@ietf.org>
In-Reply-To: <4EB583C8.5030907@piuha.net>
References: <DCC302FAA9FE5F4BBA4DCAD46569377914518AFAE5@PRVPEXVS03.corp.twcable.com> <4EB583C8.5030907@piuha.net>
X-Mailer: MH-E 8.1; nmh 1.3-dev; XEmacs 21.4 (patch 22)
Date: Mon, 07 Nov 2011 10:39:53 -0500
Message-ID: <13027.1320680393@marajade.sandelman.ca>
Sender: mcr@sandelman.ca
Subject: Re: [homenet] more comments on draft-arkko-homenet-prefix-assignment
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Nov 2011 15:38:57 -0000

>>>>> "Jari" == Jari Arkko <jari.arkko@piuha.net> writes:
    Jari> It was simply outside the scope because I think the mechanisms
    Jari> of distributing prefixes around are separable from the
    Jari> question of what prefix types are used.

    Jari> I was thinking that we need another document on the use of
    Jari> ULAs, and it would of course reference this spec for the
    Jari> actual distribution within the network.

I wonder, given that we don't need to be as conservative with ULAs as we
do with GUA, if we should perhaps do something to allow ULAs to be even
more stable.

In particular, should the ULA used for my PersonalAreaNetwork change,
ever, regardless of whose house/office I'm in?  I think that my personal
gateway should simply use zospf to announce it into my home cloud.

Or, is my PAN actually a kind of walled-garden?

-- 
]       He who is tired of Weird Al is tired of life!           |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
   Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE>
	               then sign the petition. 

From lee.howard@twcable.com  Mon Nov  7 08:35:14 2011
Return-Path: <lee.howard@twcable.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 178E021F8C21 for <homenet@ietfa.amsl.com>; Mon,  7 Nov 2011 08:35:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.713
X-Spam-Level: 
X-Spam-Status: No, score=-0.713 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r6t37PHT3TCV for <homenet@ietfa.amsl.com>; Mon,  7 Nov 2011 08:35:13 -0800 (PST)
Received: from cdpipgw02.twcable.com (cdpipgw02.twcable.com [165.237.59.23]) by ietfa.amsl.com (Postfix) with ESMTP id 325A021F84E5 for <homenet@ietf.org>; Mon,  7 Nov 2011 08:35:12 -0800 (PST)
X-SENDER-IP: 10.136.163.10
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.69,470,1315195200"; d="scan'208";a="279063337"
Received: from unknown (HELO PRVPEXHUB01.corp.twcable.com) ([10.136.163.10]) by cdpipgw02.twcable.com with ESMTP/TLS/RC4-MD5; 07 Nov 2011 11:30:38 -0500
Received: from PRVPEXVS03.corp.twcable.com ([10.136.163.27]) by PRVPEXHUB01.corp.twcable.com ([10.136.163.10]) with mapi; Mon, 7 Nov 2011 11:35:10 -0500
From: "Howard, Lee" <lee.howard@twcable.com>
To: Jari Arkko <jari.arkko@piuha.net>
Date: Mon, 7 Nov 2011 11:35:04 -0500
Thread-Topic: [homenet] more comments on draft-arkko-homenet-prefix-assignment
Thread-Index: Acyb6s6Ly6RQ9SmJTlKl88+uJCxN5wBe7ILQ
Message-ID: <DCC302FAA9FE5F4BBA4DCAD46569377914518B002B@PRVPEXVS03.corp.twcable.com>
References: <DCC302FAA9FE5F4BBA4DCAD46569377914518AFAE5@PRVPEXVS03.corp.twcable.com> <4EB583C8.5030907@piuha.net>
In-Reply-To: <4EB583C8.5030907@piuha.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] more comments on draft-arkko-homenet-prefix-assignment
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Nov 2011 16:35:14 -0000

> -----Original Message-----
> From: Jari Arkko [mailto:jari.arkko@piuha.net]
> Sent: Saturday, November 05, 2011 2:43 PM
> To: Howard, Lee
> Cc: homenet@ietf.org Group
> Subject: Re: [homenet] more comments on draft-arkko-homenet-prefix-assign=
ment
>
> Lee,
>
> Thanks for your feedback and questions. Some answers inline:
>
> > This requirement requires justification:
> >   o  The assignments must be stable across reboots, power cycling,
> >        router software updates, and preferably, should be stable across
> >        simple network changes such as adding a new device on the stub
> >        network segments.
> >
> > *Why* is that an RFC2119 MUST?
> > Why is that an RFC2219 SHOULD?  When I see a "should" I like to see an =
explanation,
> since the definition is "Do this unless you have a good reason not to," a=
nd implementers
> need guidance about when they might violate that.
> > I think the reason (as discussed on list a couple of weeks ago) is that=
 when a router
> reboots, if it gets renumbered, the hosts attached to it still have DHCP =
leases that haven't
> expired but won't be able to use those addresses.
>
> (I did not use RFC 2119 keywords, by the way.)

Section 2 says you're using RFC 2119, so I assumed use of those words was i=
ntended to
imply those definitions.  You didn't capitalize, but that's not required.

> The reason that you give is the valid reason. If a router is power-cycled=
 and the hosts still
> have old prefix values, this may result in some breakage. Power cycling m=
ay be frequent,
> e.g., many people regularly turn off their devices. (Not me, how else wou=
ld I heat my
> house?)

Another way to handle that problem is to have a predictable alogrithm for p=
refix
assignment, so any router plugged into a given point in the network will al=
ways
acquire the same prefix.  That is not true here--if you replace your den ro=
uter, the
new router will have a different rouer ID, and may well get a new prefix.  =
That's
a tolerable limitation, though.
(Surely there are more potent heaters than home gateways.  Minicomputers, f=
or
instance.  I had to describe tape storage to my son yesterday--he'd never s=
een a
tape).

> I was thinking that we need another document on the use of ULAs, and it w=
ould of course
> reference this spec for the actual distribution within the network.
>
> (But I confess there may be a small personal bias in this decision about =
the scope as well. I
> don't seem to be quite as convinced about the blessings of ULAs as some o=
ther people in the
> working group :-)

James has interesting arguments here, which I'm still thinking about.
I do think we as a WG need to expose the requirements for ULAs, and either =
say our
solutions won't support ULA, or require our solutions to describe ULA funct=
ioning.

> >    The lifetime of the prefix SHOULD be advertised as a
> >     reasonably long period, at least 48 hours or the lifetime of the
> >     assigned prefixes, whichever is smaller.
> >
> > Why?
>
> Because it would be harmful to have different hosts in the home add/remov=
e prefixes.
> Sufficiently long lifetimes ensure that a temporary radio glitch or packe=
t loss does not
> remove your prefixes.
>
> But maybe this should be outside the scope of this document, it is more o=
f an operational
> consideration. Or not... since there is no operator in the homes the defa=
ults need to be
> reasonable. Your thoughts?

I'm fine with SHOULD or RECOMMENDED, as long as we explain why.
A shorter lifetime would give the hosts a faster recovery time to prefix ch=
anges.
I don't want to suggest that we should have 30 second DHCP lease times, but
this is the tradeoff we're making.

> >     To support a variety of
> >     IPv6-only hosts in these networks, the router needs to ensure that
> >     sufficient DNS discovery mechanisms are enabled.
> >
> > What kind of variety do you mean?
>
> For instance, hosts that support only DHCPv6-based DNS discovery. Hosts t=
hat support
> only RFC 5006 based DNS discovery.
>
> >    By "DNS discovery" you mean
> > methods to advertise resolvers to hosts, not methods to discover
> > name-address mappings.
>
> Yes.

Thanks for clarifying.  I wasn't sure whether you meant PCs and Macs, or
computers, tablets and game consoles, or Ethernet, MoCA and Wi-Fi.

> > Shouldn't the border router assign its local prefix before sending the =
full
> > /48 Usable Prefix?  I suppose it doesn't have to be, but that means tha=
t
> > the border sends the Usable Prefix, and all attached routers fight over
> > who has the highest Router ID; then that router provides the Assigned
> > Prefix to the link.  It works, it just seems funny to me.
>
> Good point. Maybe we need to think about this in a more fundamental way a=
s well, not sure
> if there are some boot order issues where this might happen later, too. O=
r maybe not. On a
> stable network the routers remember what prefixes they ended up using, an=
d attempt to
> reuse those upon reboots.

Similar to the ULA question: where do you start?

Lee


This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

From pthubert@cisco.com  Wed Nov  9 03:19:02 2011
Return-Path: <pthubert@cisco.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA54221F8C2D for <homenet@ietfa.amsl.com>; Wed,  9 Nov 2011 03:19:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.703
X-Spam-Level: 
X-Spam-Status: No, score=-8.703 tagged_above=-999 required=5 tests=[AWL=1.896,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0LmUPPtwdlJd for <homenet@ietfa.amsl.com>; Wed,  9 Nov 2011 03:19:02 -0800 (PST)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id CDC9D21F8C33 for <homenet@ietf.org>; Wed,  9 Nov 2011 03:19:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=pthubert@cisco.com; l=2283; q=dns/txt; s=iport; t=1320837541; x=1322047141; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to; bh=ur193PtsprVTAoHE8c6MyBdtKLSlbl8BE5ODkb8rasQ=; b=JEYL9nmpShBNdWrJrdb/nPngctujEK0iRDS+vvgTNTcGT16vOA27PzNG dkHz9Bb+hp7Mx/q5Wsl1g6BeltuZuhwWytZZekZypQ6XMVvXDLTa8TgN2 67VsuNglFNiJ+pG1epydh+HhUz1PWO6CHKN/BqdPXMEpP8rlyaVdxt5Zd k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjQFAMxguk6Q/khM/2dsb2JhbABCpzyBOYEngQWBcgEBAQQBAQEPAR0KNBcEAgEIDgMEAQELBhcBBgEbCx8JCAEBBAESCBECB4domSYBkQSOG4kcYwSGSZMahWiGTQ
X-IronPort-AV: E=Sophos;i="4.69,483,1315180800"; d="scan'208";a="121166440"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-1.cisco.com with ESMTP; 09 Nov 2011 11:18:59 +0000
Received: from xbh-ams-101.cisco.com (xbh-ams-101.cisco.com [144.254.74.71]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id pA9BIx6R030843; Wed, 9 Nov 2011 11:18:59 GMT
Received: from xmb-ams-108.cisco.com ([144.254.74.83]) by xbh-ams-101.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Wed, 9 Nov 2011 12:18:59 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 9 Nov 2011 12:17:56 +0100
Message-ID: <BDF2740C082F6942820D95BAEB9E1A845A9789@XMB-AMS-108.cisco.com>
In-Reply-To: <13027.1320680393@marajade.sandelman.ca>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [homenet] more comments on draft-arkko-homenet-prefix-assignment
Thread-Index: AcydY2CECP/2oDj0QKy9aAYEn7PQjgBbNMHQ
References: <DCC302FAA9FE5F4BBA4DCAD46569377914518AFAE5@PRVPEXVS03.corp.twcable.com><4EB583C8.5030907@piuha.net> <13027.1320680393@marajade.sandelman.ca>
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: "Michael Richardson" <mcr@sandelman.ca>, <homenet@ietf.org>
X-OriginalArrivalTime: 09 Nov 2011 11:18:59.0731 (UTC) FILETIME=[60DC5E30:01CC9ED1]
Subject: Re: [homenet] more comments on draft-arkko-homenet-prefix-assignment
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 09 Nov 2011 11:19:03 -0000

Michael:

If you want your PAN network to be reachable from the rest of the world,
you still need some mobility solution.
For instance you could use NEMO. Get a PAN delegated from your home
network and then move around with it.

For local communications, yes you'll want to inject the PAN network
prefix into the local topology.=20
If the local topology trusts you to inject anything which is not a
given.

The combination of the 2 is basically what MANEMO tried to achieve a few
years ago, using what became RPL as the underlying routing protocol.
Maybe the times are getting ripe.

Cheers,

Pascal

-----Original Message-----
From: homenet-bounces@ietf.org [mailto:homenet-bounces@ietf.org] On
Behalf Of Michael Richardson
Sent: lundi 7 novembre 2011 16:40
To: homenet@ietf.org Group
Subject: Re: [homenet] more comments on
draft-arkko-homenet-prefix-assignment


>>>>> "Jari" =3D=3D Jari Arkko <jari.arkko@piuha.net> writes:
    Jari> It was simply outside the scope because I think the mechanisms
    Jari> of distributing prefixes around are separable from the
    Jari> question of what prefix types are used.

    Jari> I was thinking that we need another document on the use of
    Jari> ULAs, and it would of course reference this spec for the
    Jari> actual distribution within the network.

I wonder, given that we don't need to be as conservative with ULAs as we
do with GUA, if we should perhaps do something to allow ULAs to be even
more stable.

In particular, should the ULA used for my PersonalAreaNetwork change,
ever, regardless of whose house/office I'm in?  I think that my personal
gateway should simply use zospf to announce it into my home cloud.

Or, is my PAN actually a kind of walled-garden?

--=20
]       He who is tired of Weird Al is tired of life!           |
firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net
architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device
driver[
   Kyoto Plus: watch the video
<http://www.youtube.com/watch?v=3Dkzx1ycLXQSE>
	               then sign the petition.=20
_______________________________________________
homenet mailing list
homenet@ietf.org
https://www.ietf.org/mailman/listinfo/homenet

From joelja@bogus.com  Thu Nov 10 22:43:31 2011
Return-Path: <joelja@bogus.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BE6621F8540 for <homenet@ietfa.amsl.com>; Thu, 10 Nov 2011 22:43:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.53
X-Spam-Level: 
X-Spam-Status: No, score=-101.53 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DATE_IN_PAST_06_12=1.069, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qvtSa78hCLw9 for <homenet@ietfa.amsl.com>; Thu, 10 Nov 2011 22:43:31 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 1DD3421F853E for <homenet@ietf.org>; Thu, 10 Nov 2011 22:43:17 -0800 (PST)
Received: from Zorch.local ([210.229.158.64]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id pAB6giKO087626 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Fri, 11 Nov 2011 06:43:10 GMT (envelope-from joelja@bogus.com)
Message-ID: <4EBC4FB3.30204@bogus.com>
Date: Thu, 10 Nov 2011 14:26:59 -0800
From: Joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: Erik Nordmark <nordmark@cisco.com>
References: <CAKD1Yr2z65sYrp_NYyaqV-zwR=5KtYEgtSskZr2_XVWKjNZ0Gw@mail.gmail.com> <4E8F441D.9070202@cisco.com> <CAKD1Yr0Zz2DcJBPz0_3pg=Hs1OLQE4Uyu+tc=umHV3rC3H-=2w@mail.gmail.com> <4E8F5E8B.4010102@cisco.com> <AA30D82A-C8B2-471A-8D64-800A1D83FEA4@cisco.com> <4E8F7873.4050505@cisco.com> <4E904CD2.1080705@piuha.net> <4E933756.30506@cisco.com> <2834.1318277864@marajade.sandelman.ca> <4E95BA69.6090507@cisco.com>
In-Reply-To: <4E95BA69.6090507@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Fri, 11 Nov 2011 06:43:13 +0000 (UTC)
Cc: homenet@ietf.org, Michael Richardson <mcr@sandelman.ca>
Subject: Re: [homenet] Homenet strawman slides
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 11 Nov 2011 06:43:31 -0000

On 10/12/11 09:03 , Erik Nordmark wrote:
> On 10/10/11 1:17 PM, Michael Richardson wrote:
>>
>> Moving/repurposing a router without a factory reset seems like the
>> perhaps the most important source of conflict in the architecture that
>> we discussed.  Particularly if the router is put into a junk drawer for
>> a few months until it is needed.
>>
>> So, we might need to consider if we can expire persisted settings after
>> some long (from the point of view of the network) time, like 1 week...
> 
> FWIW My existing IPv4 NATting home routers don't need to be quaranteened
> for a week; I can just rewire. At worst I have to power cycle.

if my routed network with 4-10 routes in it can't reconverge in 3x the
hello interval of the routing protocl there's something seriously wrong
with it...

> I thought IPv6 would make things better ;-)
> 
>    Erik
> 
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
> 


From nordmark@cisco.com  Fri Nov 11 16:26:06 2011
Return-Path: <nordmark@cisco.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED94D21F84AA for <homenet@ietfa.amsl.com>; Fri, 11 Nov 2011 16:26:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.199
X-Spam-Level: 
X-Spam-Status: No, score=-6.199 tagged_above=-999 required=5 tests=[AWL=0.400,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FnCXbPZ9wAyv for <homenet@ietfa.amsl.com>; Fri, 11 Nov 2011 16:26:06 -0800 (PST)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id 295A321F84A9 for <homenet@ietf.org>; Fri, 11 Nov 2011 16:26:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=nordmark@cisco.com; l=1082; q=dns/txt; s=iport; t=1321057566; x=1322267166; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=fwgx3IpnQ+94Ut+m5iW4YYPmC8LpNzYWyoaZjOt0A1A=; b=KFMvkuC1k3lbH7tMJK1vXL4M3/VbRHmWHvjTximVi2ExcbiReXPKxHEQ N6cUtkPH7YDjTCZC6wkJnsSZw8sF/paQo93LD9j43lNzQpozuVS1uUCiy mRWHbkGpH+Rza0e86anAemqIeyUVvU44I/ZlLeZuXHdyro4CtTuU61fV5 0=;
X-IronPort-AV: E=Sophos;i="4.69,497,1315180800"; d="scan'208";a="12142766"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-1.cisco.com with ESMTP; 12 Nov 2011 00:26:05 +0000
Received: from [10.0.1.13] ([10.21.86.156]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id pAC0Q4NF016499; Sat, 12 Nov 2011 00:26:05 GMT
Message-ID: <4EBDBD21.1020307@cisco.com>
Date: Fri, 11 Nov 2011 16:26:09 -0800
From: Erik Nordmark <nordmark@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Joel jaeggli <joelja@bogus.com>
References: <CAKD1Yr2z65sYrp_NYyaqV-zwR=5KtYEgtSskZr2_XVWKjNZ0Gw@mail.gmail.com> <4E8F441D.9070202@cisco.com> <CAKD1Yr0Zz2DcJBPz0_3pg=Hs1OLQE4Uyu+tc=umHV3rC3H-=2w@mail.gmail.com> <4E8F5E8B.4010102@cisco.com> <AA30D82A-C8B2-471A-8D64-800A1D83FEA4@cisco.com> <4E8F7873.4050505@cisco.com> <4E904CD2.1080705@piuha.net> <4E933756.30506@cisco.com> <2834.1318277864@marajade.sandelman.ca> <4E95BA69.6090507@cisco.com> <4EBC4FB3.30204@bogus.com>
In-Reply-To: <4EBC4FB3.30204@bogus.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: homenet@ietf.org, Michael Richardson <mcr@sandelman.ca>
Subject: Re: [homenet] Homenet strawman slides
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 12 Nov 2011 00:26:07 -0000

On 11/10/11 2:26 PM, Joel jaeggli wrote:
> On 10/12/11 09:03 , Erik Nordmark wrote:
>> On 10/10/11 1:17 PM, Michael Richardson wrote:
>>>
>>> Moving/repurposing a router without a factory reset seems like the
>>> perhaps the most important source of conflict in the architecture that
>>> we discussed.  Particularly if the router is put into a junk drawer for
>>> a few months until it is needed.
>>>
>>> So, we might need to consider if we can expire persisted settings after
>>> some long (from the point of view of the network) time, like 1 week...
>>
>> FWIW My existing IPv4 NATting home routers don't need to be quaranteened
>> for a week; I can just rewire. At worst I have to power cycle.
>
> if my routed network with 4-10 routes in it can't reconverge in 3x the
> hello interval of the routing protocl there's something seriously wrong
> with it...

We were talking about the stability of prefix assignment - not routing.

I think IGP convergence was solved a few decades ago, so no need to 
repeat that discussion in homenet.

Regards,
    Erik

From Ray.Bellis@nominet.org.uk  Sat Nov 12 19:25:41 2011
Return-Path: <Ray.Bellis@nominet.org.uk>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0DDD221F8493 for <homenet@ietfa.amsl.com>; Sat, 12 Nov 2011 19:25:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.51
X-Spam-Level: 
X-Spam-Status: No, score=-7.51 tagged_above=-999 required=5 tests=[AWL=-0.911,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L6MTFYkkI8h6 for <homenet@ietfa.amsl.com>; Sat, 12 Nov 2011 19:25:38 -0800 (PST)
Received: from mx1.knowthenet.org.uk (mx1.knowthenet.org.uk [213.248.199.2]) by ietfa.amsl.com (Postfix) with ESMTP id C797121F848A for <homenet@ietf.org>; Sat, 12 Nov 2011 19:25:36 -0800 (PST)
DomainKey-Signature: s=main.dk.nominet.selector; d=nominet.org.uk; c=nofws; q=dns; h=X-IronPort-AV:Received:Received:From:To:Subject: Thread-Topic:Thread-Index:Date:Message-ID:Accept-Language: Content-Language:X-MS-Has-Attach:X-MS-TNEF-Correlator: Content-Type:Content-ID:Content-Transfer-Encoding: MIME-Version; b=u2rPf8a1hueOSSmHGXXMw2UiW051axFn1dYJKANtYFVeNdvszocG5mnT q1Al3cz+OY5UagD4mIHYEgihvNSFT39a/Sdcpexi3mvSWgvBbZK7s7uls exWZwnp2lcNtw+P;
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nominet.org.uk; i=Ray.Bellis@nominet.org.uk; q=dns/txt; s=main.dkim.nominet.selector; t=1321154738; x=1352690738; h=from:sender:reply-to:subject:date:message-id:to:cc: mime-version:content-transfer-encoding:content-id: content-description:resent-date:resent-from:resent-sender: resent-to:resent-cc:resent-message-id:in-reply-to: references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:list-owner:list-archive; z=From:=20Ray=20Bellis=20<Ray.Bellis@nominet.org.uk> |Subject:=20Presentation=20materials|Date:=20Sun,=2013=20 Nov=202011=2003:25:27=20+0000|Message-ID:=20<2BB8BD5F-609 0-42CA-B131-8348135A5D74@nominet.org.uk>|To:=20"homenet@i etf.org"=20<homenet@ietf.org>|MIME-Version:=201.0 |Content-Transfer-Encoding:=20quoted-printable |Content-ID:=20<c1d46a0d-152b-4963-9655-d0277e1a7956>; bh=dU6yoQoUIRY0yOV4uVLct/M37ViBBNZH09zk9XjDisQ=; b=vgH+NbYLWum1iF2kA//qaqyEyWmo29Skf1viFmDal0TRSdKF5wxc+seB Wx3zq3GxnE71erYYiyXuBE4d37ZhKiV20yRSNBajyZnmCFPrZx05jOmHP b4MnUKha9PF4bf0;
X-IronPort-AV: E=Sophos;i="4.69,501,1315177200"; d="scan'208";a="36575024"
Received: from wds-exc2.okna.nominet.org.uk ([213.248.197.145]) by mx3.nominet.org.uk with ESMTP; 13 Nov 2011 03:25:33 +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%19]) with mapi; Sun, 13 Nov 2011 03:25:28 +0000
From: Ray Bellis <Ray.Bellis@nominet.org.uk>
To: "homenet@ietf.org" <homenet@ietf.org>
Thread-Topic: Presentation materials
Thread-Index: AQHMobPjztf1HK5qMkuzeAWt0jIrBg==
Date: Sun, 13 Nov 2011 03:25:27 +0000
Message-ID: <2BB8BD5F-6090-42CA-B131-8348135A5D74@nominet.org.uk>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-ID: <c1d46a0d-152b-4963-9655-d0277e1a7956>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [homenet] Presentation materials
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 13 Nov 2011 03:25:41 -0000

Just a reminder for people due to present Tuesday - please if at all possib=
le get your presentation materials to the chairs by this evening!

thanks,

Ray


From Ray.Bellis@nominet.org.uk  Mon Nov 14 02:10:59 2011
Return-Path: <Ray.Bellis@nominet.org.uk>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6EE2211E80C6 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 02:10:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.469
X-Spam-Level: 
X-Spam-Status: No, score=-7.469 tagged_above=-999 required=5 tests=[AWL=-0.870, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0wYJByv6u652 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 02:10:56 -0800 (PST)
Received: from mx1.knowthenet.org.uk (mx1.knowthenet.org.uk [213.248.199.2]) by ietfa.amsl.com (Postfix) with ESMTP id B808221F8CBE for <homenet@ietf.org>; Mon, 14 Nov 2011 02:05:48 -0800 (PST)
DomainKey-Signature: s=main.dk.nominet.selector; d=nominet.org.uk; c=nofws; q=dns; h=X-IronPort-AV:Received:Received:From:To:Subject: Thread-Topic:Thread-Index:Date:Message-ID:Accept-Language: Content-Language:X-MS-Has-Attach:X-MS-TNEF-Correlator: Content-Type:Content-ID:Content-Transfer-Encoding: MIME-Version; b=Lhn9k6csZRQw3JmugGQcwnxRuZqQjSpR76Sbpc/r5lzqDPHANZ9ch7UU 1SG3m+U9Myjm5rOHFse38zwhF2t1dXVaRToO7FfWzdkbbILpFLAwUnp81 bctn9qW7ATTz/Ew;
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nominet.org.uk; i=Ray.Bellis@nominet.org.uk; q=dns/txt; s=main.dkim.nominet.selector; t=1321265149; x=1352801149; h=from:sender:reply-to:subject:date:message-id:to:cc: mime-version:content-transfer-encoding:content-id: content-description:resent-date:resent-from:resent-sender: resent-to:resent-cc:resent-message-id:in-reply-to: references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:list-owner:list-archive; z=From:=20Ray=20Bellis=20<Ray.Bellis@nominet.org.uk> |Subject:=20Note=20Taker(s)=20and=20Jabber=20Relay=20for =20the=20WG=20session?|Date:=20Mon,=2014=20Nov=202011=201 0:05:27=20+0000|Message-ID:=20<44A64819-6EC3-4E61-871E-28 72E26A5619@nominet.org.uk>|To:=20"homenet@ietf.org"=20<ho menet@ietf.org>|MIME-Version:=201.0 |Content-Transfer-Encoding:=20quoted-printable |Content-ID:=20<f978c4b4-392d-4f08-a205-48f8f9f4ddcd>; bh=J9uBp649aaAj9Kem5YiY6IFiX0EDdGNAOGPId5LNPjQ=; b=Fs+s3BpquIYYkMWjS2eGX6af4uw3nincbGAHX55xaJLYBmDGHptGYHzP BhehM8XL4RG01tESasKS/cxNCnSva97G8669j4kyyKpY/v6oMFEXZ6YZe VcUvYCF0fY2Ejpa;
X-IronPort-AV: E=Sophos;i="4.69,508,1315177200"; d="scan'208";a="36595938"
Received: from wds-exc2.okna.nominet.org.uk ([213.248.197.145]) by mx3.nominet.org.uk with ESMTP; 14 Nov 2011 10:05:29 +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%19]) with mapi; Mon, 14 Nov 2011 10:05:28 +0000
From: Ray Bellis <Ray.Bellis@nominet.org.uk>
To: "homenet@ietf.org" <homenet@ietf.org>
Thread-Topic: Note Taker(s) and Jabber Relay for the WG session?
Thread-Index: AQHMorTv/6A6RwK7qkqI7VNBIK7HNA==
Date: Mon, 14 Nov 2011 10:05:27 +0000
Message-ID: <44A64819-6EC3-4E61-871E-2872E26A5619@nominet.org.uk>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <f978c4b4-392d-4f08-a205-48f8f9f4ddcd>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [homenet] Note Taker(s) and Jabber Relay for the WG session?
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 14 Nov 2011 10:10:59 -0000

Mark and I would appreciate advance volunteers for the r=F4les of Jabber Re=
lay and Note Taker(s) for tomorrow's WG session.  Time is short during the =
session and we'd rather avoid that awkward silence as everyone tries to avo=
id catching our eye if we have to ask for volunteers during the session its=
elf!

For the notes we propose to use the new Etherpad collaborative editing just=
 added to the Tools website - available at <http://tools.ietf.org/wg/homene=
t/minutes>.  It looks fun - please volunteer to try it!

For the jabber room I use the term _relay_ to emphasise that all that is ne=
eded is someone to:

a) pass comments from the jabber room back to the session

b) keep the jabber room updated on who is speaking and what slide they're o=
n, since that's not always obvious from the audio

For those in the jabber room please _explicitly_ state whether you want a c=
omment to be made on your behalf at the mic!

thanks,

Ray and Mark




From alejandroacostaalamo@gmail.com  Mon Nov 14 02:48:46 2011
Return-Path: <alejandroacostaalamo@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E3AFD21F8E92 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 02:48:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D8f0j4XBLOaG for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 02:48:46 -0800 (PST)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 320D121F8DF0 for <homenet@ietf.org>; Mon, 14 Nov 2011 02:48:46 -0800 (PST)
Received: by wwe5 with SMTP id 5so2960527wwe.13 for <homenet@ietf.org>; Mon, 14 Nov 2011 02:48:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=Kc4gDvP+Jz837ZpIB0oV8y6rX3jt+yz29OdYkCLZfg8=; b=WgwmBv+Ezttv1brXqbSktTy4q6296Y7azmW2ULMXmc/b46B7ZqrHv/fnhaMbKKe/aR IDTEn5XBUGfzVFFK+fdU2M3KGvKYy/dmwqItrnlDMBRGNX0BMRGLibivXORu7ELUdEpY n+45IjhhXW/kKuPUTxza0GoHC6CyFGky164YM=
MIME-Version: 1.0
Received: by 10.180.3.33 with SMTP id 1mr24974598wiz.54.1321267725290; Mon, 14 Nov 2011 02:48:45 -0800 (PST)
Received: by 10.180.97.2 with HTTP; Mon, 14 Nov 2011 02:48:45 -0800 (PST)
In-Reply-To: <44A64819-6EC3-4E61-871E-2872E26A5619@nominet.org.uk>
References: <44A64819-6EC3-4E61-871E-2872E26A5619@nominet.org.uk>
Date: Mon, 14 Nov 2011 06:18:45 -0430
Message-ID: <CAOmxzdy4gvJJyRJ1JsUjCgRZk5wc_us63hoeA4PgWgfL2atirA@mail.gmail.com>
From: Alejandro Acosta <alejandroacostaalamo@gmail.com>
To: Ray Bellis <Ray.Bellis@nominet.org.uk>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "homenet@ietf.org" <homenet@ietf.org>
Subject: Re: [homenet] Note Taker(s) and Jabber Relay for the WG session?
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 14 Nov 2011 10:48:47 -0000

Hi All,
  Please count on me as note taker, I would rather if someone else is
also taking notes just in case I miss something since my native
language is not English.

Thanks,

Alejandro,


On Mon, Nov 14, 2011 at 5:35 AM, Ray Bellis <Ray.Bellis@nominet.org.uk> wro=
te:
> Mark and I would appreciate advance volunteers for the r=F4les of Jabber =
Relay and Note Taker(s) for tomorrow's WG session. =A0Time is short during =
the session and we'd rather avoid that awkward silence as everyone tries to=
 avoid catching our eye if we have to ask for volunteers during the session=
 itself!
>
> For the notes we propose to use the new Etherpad collaborative editing ju=
st added to the Tools website - available at <http://tools.ietf.org/wg/home=
net/minutes>. =A0It looks fun - please volunteer to try it!
>
> For the jabber room I use the term _relay_ to emphasise that all that is =
needed is someone to:
>
> a) pass comments from the jabber room back to the session
>
> b) keep the jabber room updated on who is speaking and what slide they're=
 on, since that's not always obvious from the audio
>
> For those in the jabber room please _explicitly_ state whether you want a=
 comment to be made on your behalf at the mic!
>
> thanks,
>
> Ray and Mark
>
>
>
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>

From alejandroacostaalamo@gmail.com  Mon Nov 14 02:50:57 2011
Return-Path: <alejandroacostaalamo@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3EF2E21F8E92 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 02:50:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qm6BigpW2uXZ for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 02:50:56 -0800 (PST)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id 35C501F0C43 for <homenet@ietf.org>; Mon, 14 Nov 2011 02:50:56 -0800 (PST)
Received: by wwe5 with SMTP id 5so2962410wwe.13 for <homenet@ietf.org>; Mon, 14 Nov 2011 02:50:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=tg3vY8bZbKop1GzvSgUc4/T+43U3wvU0Nw46KFIFkFg=; b=CFm7rNswNatS7CQSLrBV+D73Y3e9ZEkL1Xu7TJaAp4Tf780Mm8VXENKUbJcK78DKLR q6cj2FAf924WRE318RiE2UvlyZ4vzdR5u8/V74xdN2aoDHtHeMyBpKcBWF37JlnR+t2r MxSk5ri+5u6+W03xvvN3ZCC+RchIdFiPRXbFY=
MIME-Version: 1.0
Received: by 10.180.87.199 with SMTP id ba7mr25084307wib.27.1321267853049; Mon, 14 Nov 2011 02:50:53 -0800 (PST)
Received: by 10.180.97.2 with HTTP; Mon, 14 Nov 2011 02:50:53 -0800 (PST)
In-Reply-To: <44A64819-6EC3-4E61-871E-2872E26A5619@nominet.org.uk>
References: <44A64819-6EC3-4E61-871E-2872E26A5619@nominet.org.uk>
Date: Mon, 14 Nov 2011 06:20:53 -0430
Message-ID: <CAOmxzdwVvfTzwoev37jhZUkbnwr9ThQD-bgBLmpErujP692FhQ@mail.gmail.com>
From: Alejandro Acosta <alejandroacostaalamo@gmail.com>
To: Ray Bellis <Ray.Bellis@nominet.org.uk>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "homenet@ietf.org" <homenet@ietf.org>
Subject: Re: [homenet] Note Taker(s) and Jabber Relay for the WG session?
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 14 Nov 2011 10:50:57 -0000

BTW, the tool looks nice, I wonder if two people using it at the same
time does not cause confusion during typing. Tomorrow I'll let you
know.

Alejandro,

On Mon, Nov 14, 2011 at 5:35 AM, Ray Bellis <Ray.Bellis@nominet.org.uk> wro=
te:
> Mark and I would appreciate advance volunteers for the r=F4les of Jabber =
Relay and Note Taker(s) for tomorrow's WG session. =A0Time is short during =
the session and we'd rather avoid that awkward silence as everyone tries to=
 avoid catching our eye if we have to ask for volunteers during the session=
 itself!
>
> For the notes we propose to use the new Etherpad collaborative editing ju=
st added to the Tools website - available at <http://tools.ietf.org/wg/home=
net/minutes>. =A0It looks fun - please volunteer to try it!
>
> For the jabber room I use the term _relay_ to emphasise that all that is =
needed is someone to:
>
> a) pass comments from the jabber room back to the session
>
> b) keep the jabber room updated on who is speaking and what slide they're=
 on, since that's not always obvious from the audio
>
> For those in the jabber room please _explicitly_ state whether you want a=
 comment to be made on your behalf at the mic!
>
> thanks,
>
> Ray and Mark
>
>
>
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>

From Ray.Bellis@nominet.org.uk  Mon Nov 14 02:54:06 2011
Return-Path: <Ray.Bellis@nominet.org.uk>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A6141F0C56 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 02:54:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.431
X-Spam-Level: 
X-Spam-Status: No, score=-9.431 tagged_above=-999 required=5 tests=[AWL=1.168,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A5rA9SPJmaJB for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 02:54:05 -0800 (PST)
Received: from mx4.nominet.org.uk (mail.nominet.org.uk [213.248.199.24]) by ietfa.amsl.com (Postfix) with ESMTP id 322DF1F0C43 for <homenet@ietf.org>; Mon, 14 Nov 2011 02:54:05 -0800 (PST)
DomainKey-Signature: s=main.dk.nominet.selector; d=nominet.org.uk; c=nofws; q=dns;  h=X-IronPort-AV: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:Content-Type: Content-ID:Content-Transfer-Encoding:MIME-Version; b=Hh2nTGrHpifBNHzpY+/SZ9QNMCc5bP8hGQoTcIvZHWDVaSSkXfCaOzBQ PHFtmmsMgXaOlZMKl3RIKXN0afaDJ1xR487AIPAgZ8fRscJZAk3u+lXHO qLFbwAyj9vqIHfN;
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nominet.org.uk; i=Ray.Bellis@nominet.org.uk; q=dns/txt; s=main.dkim.nominet.selector; t=1321268045; x=1352804045; h=from:sender:reply-to:subject:date:message-id:to:cc: mime-version:content-transfer-encoding:content-id: content-description:resent-date:resent-from:resent-sender: resent-to:resent-cc:resent-message-id:in-reply-to: references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:list-owner:list-archive; z=From:=20Ray=20Bellis=20<Ray.Bellis@nominet.org.uk> |Subject:=20Re:=20[homenet]=20Note=20Taker(s)=20and=20Jab ber=20Relay=20for=20the=20WG=20session?|Date:=20Mon,=2014 =20Nov=202011=2010:54:01=20+0000|Message-ID:=20<65D48A6C- BC6B-40E9-8E30-3EE5BF66F3B1@nominet.org.uk>|To:=20Alejand ro=20Acosta=20<alejandroacostaalamo@gmail.com>|CC:=20"hom enet@ietf.org"=20<homenet@ietf.org>|MIME-Version:=201.0 |Content-Transfer-Encoding:=20quoted-printable |Content-ID:=20<48961990-f92a-4905-8d33-e9b57bd2d8f7> |In-Reply-To:=20<CAOmxzdy4gvJJyRJ1JsUjCgRZk5wc_us63hoeA4P gWgfL2atirA@mail.gmail.com>|References:=20<44A64819-6EC3- 4E61-871E-2872E26A5619@nominet.org.uk>=0D=0A=20<CAOmxzdy4 gvJJyRJ1JsUjCgRZk5wc_us63hoeA4PgWgfL2atirA@mail.gmail.com >; bh=LAWsZzgWbWcV694l9Syy0UpGBfNYZvrs4S98Womoenc=; b=c+xyK5CzMlhe0yPZXuj3C0+zwRdfAzBeUOhXko6RtEVhr1idU/pG1RVp d2uay3IiLWE0i1noru1ihIvyUE5H0hS0RLyzDgnOsAsUtv9US/sf6Xz4b SGF8IsoKSMjiZRX;
X-IronPort-AV: E=Sophos;i="4.69,508,1315177200"; d="scan'208";a="29538551"
Received: from wds-exc2.okna.nominet.org.uk ([213.248.197.145]) by mx4.nominet.org.uk with ESMTP; 14 Nov 2011 10:54:03 +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%19]) with mapi; Mon, 14 Nov 2011 10:54:03 +0000
From: Ray Bellis <Ray.Bellis@nominet.org.uk>
To: Alejandro Acosta <alejandroacostaalamo@gmail.com>
Thread-Topic: [homenet] Note Taker(s) and Jabber Relay for the WG session?
Thread-Index: AQHMorr8oUjKllxGf0Kw/kXKvRU5BpWsMfmA
Date: Mon, 14 Nov 2011 10:54:01 +0000
Message-ID: <65D48A6C-BC6B-40E9-8E30-3EE5BF66F3B1@nominet.org.uk>
References: <44A64819-6EC3-4E61-871E-2872E26A5619@nominet.org.uk> <CAOmxzdy4gvJJyRJ1JsUjCgRZk5wc_us63hoeA4PgWgfL2atirA@mail.gmail.com>
In-Reply-To: <CAOmxzdy4gvJJyRJ1JsUjCgRZk5wc_us63hoeA4PgWgfL2atirA@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <48961990-f92a-4905-8d33-e9b57bd2d8f7>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "homenet@ietf.org" <homenet@ietf.org>
Subject: Re: [homenet] Note Taker(s) and Jabber Relay for the WG session?
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 14 Nov 2011 10:54:06 -0000

On 14 Nov 2011, at 18:48, Alejandro Acosta wrote:

> Hi All,
>  Please count on me as note taker, I would rather if someone else is
> also taking notes just in case I miss something since my native
> language is not English.
>=20
> Thanks,
>=20
> Alejandro,

Thank you Alejandro - that's much appreciated.

Ray


From guillaume.habault@gmail.com  Mon Nov 14 08:26:29 2011
Return-Path: <guillaume.habault@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68CE311E8149 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 08:26:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oCekyFraw8bI for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 08:26:28 -0800 (PST)
Received: from mail-ey0-f194.google.com (mail-ey0-f194.google.com [209.85.215.194]) by ietfa.amsl.com (Postfix) with ESMTP id F031511E81DB for <homenet@ietf.org>; Mon, 14 Nov 2011 08:26:27 -0800 (PST)
Received: by eyd10 with SMTP id 10so1266792eyd.1 for <homenet@ietf.org>; Mon, 14 Nov 2011 08:26:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=st9DbTn2BnZ02uKVz8e8no3uBwIir9JHX2UrqE5l3Gs=; b=jnbNDhFj51pVYsx0LxdrP0p9FPeylwlsl46C66aqYMhRUebz/jP/5GuBQzRttnnlyD rkmNxCDVUKVGLO+O7EzaAoxf/DbuJyOYpoPR8ZpsnIJ1KScvpG28ZPx9E/MUGWwK66kB sMpzQaNvxZXp4z253/6bSlsQOjDHsRJqV8+mw=
MIME-Version: 1.0
Received: by 10.213.29.138 with SMTP id q10mr590740ebc.35.1321287987116; Mon, 14 Nov 2011 08:26:27 -0800 (PST)
Received: by 10.213.33.74 with HTTP; Mon, 14 Nov 2011 08:26:26 -0800 (PST)
In-Reply-To: <BDF2740C082F6942820D95BAEB9E1A845A9789@XMB-AMS-108.cisco.com>
References: <DCC302FAA9FE5F4BBA4DCAD46569377914518AFAE5@PRVPEXVS03.corp.twcable.com> <4EB583C8.5030907@piuha.net> <13027.1320680393@marajade.sandelman.ca> <BDF2740C082F6942820D95BAEB9E1A845A9789@XMB-AMS-108.cisco.com>
Date: Mon, 14 Nov 2011 17:26:26 +0100
Message-ID: <CA+XPzSY8cC_PyhcMNqhk4+B6tghp8Dpy2-3aMPZmyVRP=AWnaA@mail.gmail.com>
From: Guillaume Habault <guillaume.habault@gmail.com>
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
Content-Type: multipart/alternative; boundary=0015174be8fa1e3aaa04b1b4552e
Cc: homenet@ietf.org, Michael Richardson <mcr@sandelman.ca>
Subject: Re: [homenet] more comments on draft-arkko-homenet-prefix-assignment
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 14 Nov 2011 16:26:29 -0000

--0015174be8fa1e3aaa04b1b4552e
Content-Type: text/plain; charset=ISO-8859-1

Hi,

I would like to add some additional comments/thoughts regarding the draft
and especially on the multihoming part.
It is unclear to me whether you recommend to use the routing protocol or
the host to manage the multihoming, because it is first mentionned in the
section 3.3 that :

      multi-addressed hosts selecting the right source address to avoid
      falling foul of ingress filtering on upstream ISP connections
      [I-D.baker-fun-multi-router].

Maybe i'm wrong but it seems that in this sentence the address selection in
the host will avoid the ingress filtering. But according to me, even though
the host select the appropriate address, the routing protocol may route the
message to the wrong Customer Edge Router (especially if we are in the case
where there is more than one Customer Edge Router in the home network.
However, it could work if Customer Edge Router can talk to each other)...
And in the section 3.4, it is mentionned that :

      To Support multihoming within a homenet, a routing protocol that
      can make routing decisions based on source and destination
      addresses is desirable, to avoid upstream ISP ingress filtering
      problems.

Do you plan to use both solution? or does it depend on the topology? Or
does the aim is to be generic and let implementer decide about the solution
to use ?

In fact, the way i see multihoming in future home network (please correct
me if i'm wrong) is that there would be several CPE Router. And I think
that the ISP behind these CPE will try to differantiate themselves by
offering specific services to their customers. We will then have two cases:

   1. For common services (services that can be found on all ISP), the
   packet could be routed to any CPE in the network;
   2. For specific services offered from one ISP only, the packet will have
   to be routed to this particular CPE. So the host which want to use this
   service will have to select the appropriate address (the one received from
   the CPE) and the routing protocol will have to route the packet to the CPE.

Thus, the host has to be aware of the services available on each CPE. And
the routing protocol should route the packet using both source and
destination address.

Talking about providing different services per ISP, I think that the ISP
could provide different prefixes to the CPE depending on these services. It
could be a method for the ISP to differentiate the flow depending on the
services. Whereas in the draft you stated that:

      a single prefix should be received on the border CPE from the
      upstream ISP


Regards,

2011/11/9 Pascal Thubert (pthubert) <pthubert@cisco.com>

> Michael:
>
> If you want your PAN network to be reachable from the rest of the world,
> you still need some mobility solution.
> For instance you could use NEMO. Get a PAN delegated from your home
> network and then move around with it.
>
> For local communications, yes you'll want to inject the PAN network
> prefix into the local topology.
> If the local topology trusts you to inject anything which is not a
> given.
>
> The combination of the 2 is basically what MANEMO tried to achieve a few
> years ago, using what became RPL as the underlying routing protocol.
> Maybe the times are getting ripe.
>
> Cheers,
>
> Pascal
>
> -----Original Message-----
> From: homenet-bounces@ietf.org [mailto:homenet-bounces@ietf.org] On
> Behalf Of Michael Richardson
> Sent: lundi 7 novembre 2011 16:40
> To: homenet@ietf.org Group
> Subject: Re: [homenet] more comments on
> draft-arkko-homenet-prefix-assignment
>
>
> >>>>> "Jari" == Jari Arkko <jari.arkko@piuha.net> writes:
>    Jari> It was simply outside the scope because I think the mechanisms
>    Jari> of distributing prefixes around are separable from the
>    Jari> question of what prefix types are used.
>
>    Jari> I was thinking that we need another document on the use of
>    Jari> ULAs, and it would of course reference this spec for the
>    Jari> actual distribution within the network.
>
> I wonder, given that we don't need to be as conservative with ULAs as we
> do with GUA, if we should perhaps do something to allow ULAs to be even
> more stable.
>
> In particular, should the ULA used for my PersonalAreaNetwork change,
> ever, regardless of whose house/office I'm in?  I think that my personal
> gateway should simply use zospf to announce it into my home cloud.
>
> Or, is my PAN actually a kind of walled-garden?
>
> --
> ]       He who is tired of Weird Al is tired of life!           |
> firewalls  [
> ]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net
> architect[
> ] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device
> driver[
>   Kyoto Plus: watch the video
> <http://www.youtube.com/watch?v=kzx1ycLXQSE>
>                       then sign the petition.
> _______________________________________________
> 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
>



-- 
Guillaume HABAULT
PhD Student
Institut TELECOM / TELECOM Bretagne

--0015174be8fa1e3aaa04b1b4552e
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi, <br><br>I would like to add some additional comments/thoughts regarding=
 the draft and especially on the multihoming part.<br>It is unclear to me w=
hether you recommend to use the routing protocol or the host to manage the =
multihoming, because it is first mentionned in the section 3.3 that :<br>
<pre>      multi-addressed hosts selecting the right source address to avoi=
d
      falling foul of ingress filtering on upstream ISP connections
      [I-D.baker-fun-multi-router].</pre>Maybe i&#39;m wrong but it seems t=
hat in this sentence the address selection in the host will avoid the ingre=
ss filtering. But according to me, even though the host select the appropri=
ate address, the routing protocol may route the message to the wrong Custom=
er Edge Router (especially if we are in the case where there is more than o=
ne Customer Edge Router in the home network. However, it could work if Cust=
omer Edge Router can talk to each other)... And in the section 3.4, it is m=
entionned that :<br>
<pre>      To Support multihoming within a homenet, a routing protocol that
      can make routing decisions based on source and destination
      addresses is desirable, to avoid upstream ISP ingress filtering
      problems.</pre>Do you plan to use both solution? or does it depend on=
 the topology? Or does the aim is to be generic and let implementer decide =
about the solution to use ?<br><br>In fact, the way i see multihoming in fu=
ture home network (please correct me if i&#39;m wrong) is that there would =
be several CPE Router. And I think that the ISP behind these CPE will try t=
o differantiate themselves by offering specific services to their customers=
. We will then have two cases:<br>
<ol><li>For common services (services that can be found on all ISP), the pa=
cket could be routed to any CPE in the network;</li><li>For specific servic=
es offered from one ISP only, the packet will have to be routed to this par=
ticular CPE. So the host which want to use this service will have to select=
 the appropriate address (the one received from the CPE) and the routing pr=
otocol will have to route the packet to the CPE.</li>
</ol>Thus, the host has to be aware of the services available on each CPE. =
And the routing protocol should route the packet using both source and dest=
ination address.<br><br>Talking about providing different services per ISP,=
 I think that the ISP could provide different prefixes to the CPE depending=
 on these services. It could be a method for the ISP to differentiate the f=
low depending on the services. Whereas in the draft you stated that:<br>
<pre>      a single prefix should be received on the border CPE from the <b=
r>      upstream ISP</pre><br>Regards, <br><br><div class=3D"gmail_quote">2=
011/11/9 Pascal Thubert (pthubert) <span dir=3D"ltr">&lt;<a href=3D"mailto:=
pthubert@cisco.com">pthubert@cisco.com</a>&gt;</span><br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex;">Michael:<br>
<br>
If you want your PAN network to be reachable from the rest of the world,<br=
>
you still need some mobility solution.<br>
For instance you could use NEMO. Get a PAN delegated from your home<br>
network and then move around with it.<br>
<br>
For local communications, yes you&#39;ll want to inject the PAN network<br>
prefix into the local topology.<br>
If the local topology trusts you to inject anything which is not a<br>
given.<br>
<br>
The combination of the 2 is basically what MANEMO tried to achieve a few<br=
>
years ago, using what became RPL as the underlying routing protocol.<br>
Maybe the times are getting ripe.<br>
<br>
Cheers,<br>
<br>
Pascal<br>
<br>
-----Original Message-----<br>
From: <a href=3D"mailto:homenet-bounces@ietf.org">homenet-bounces@ietf.org<=
/a> [mailto:<a href=3D"mailto:homenet-bounces@ietf.org">homenet-bounces@iet=
f.org</a>] On<br>
Behalf Of Michael Richardson<br>
Sent: lundi 7 novembre 2011 16:40<br>
To: <a href=3D"mailto:homenet@ietf.org">homenet@ietf.org</a> Group<br>
<div class=3D"im">Subject: Re: [homenet] more comments on<br>
draft-arkko-homenet-prefix-assignment<br>
<br>
<br>
</div><div><div></div><div class=3D"h5">&gt;&gt;&gt;&gt;&gt; &quot;Jari&quo=
t; =3D=3D Jari Arkko &lt;<a href=3D"mailto:jari.arkko@piuha.net">jari.arkko=
@piuha.net</a>&gt; writes:<br>
 =A0 =A0Jari&gt; It was simply outside the scope because I think the mechan=
isms<br>
 =A0 =A0Jari&gt; of distributing prefixes around are separable from the<br>
 =A0 =A0Jari&gt; question of what prefix types are used.<br>
<br>
 =A0 =A0Jari&gt; I was thinking that we need another document on the use of=
<br>
 =A0 =A0Jari&gt; ULAs, and it would of course reference this spec for the<b=
r>
 =A0 =A0Jari&gt; actual distribution within the network.<br>
<br>
I wonder, given that we don&#39;t need to be as conservative with ULAs as w=
e<br>
do with GUA, if we should perhaps do something to allow ULAs to be even<br>
more stable.<br>
<br>
In particular, should the ULA used for my PersonalAreaNetwork change,<br>
ever, regardless of whose house/office I&#39;m in? =A0I think that my perso=
nal<br>
gateway should simply use zospf to announce it into my home cloud.<br>
<br>
Or, is my PAN actually a kind of walled-garden?<br>
<br>
--<br>
] =A0 =A0 =A0 He who is tired of Weird Al is tired of life! =A0 =A0 =A0 =A0=
 =A0 |<br>
firewalls =A0[<br>
] =A0 Michael Richardson, Sandelman Software Works, Ottawa, ON =A0 =A0|net<=
br>
architect[<br>
] <a href=3D"mailto:mcr@sandelman.ottawa.on.ca">mcr@sandelman.ottawa.on.ca<=
/a> <a href=3D"http://www.sandelman.ottawa.on.ca/" target=3D"_blank">http:/=
/www.sandelman.ottawa.on.ca/</a> |device<br>
driver[<br>
 =A0 Kyoto Plus: watch the video<br>
&lt;<a href=3D"http://www.youtube.com/watch?v=3Dkzx1ycLXQSE" target=3D"_bla=
nk">http://www.youtube.com/watch?v=3Dkzx1ycLXQSE</a>&gt;<br>
 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 then sign the petition.<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>
_______________________________________________<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></div></blockquote></div><br><br clear=3D"all"><br>-- <br>Guillaume H=
ABAULT<br>PhD Student<br>Institut TELECOM / TELECOM Bretagne<br><br><br>

--0015174be8fa1e3aaa04b1b4552e--

From mcr@sandelman.ca  Mon Nov 14 16:41:09 2011
Return-Path: <mcr@sandelman.ca>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F6AF11E80D0 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 16:41:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.582
X-Spam-Level: 
X-Spam-Status: No, score=-1.582 tagged_above=-999 required=5 tests=[AWL=0.372,  BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hWubeaPj25Op for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 16:41:07 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id 65C7711E809B for <homenet@ietf.org>; Mon, 14 Nov 2011 16:41:06 -0800 (PST)
Received: from marajade.sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by relay.sandelman.ca (Postfix) with ESMTPS id 4E69C34011 for <homenet@ietf.org>; Mon, 14 Nov 2011 19:39:40 -0500 (EST)
Received: by marajade.sandelman.ca (Postfix, from userid 179) id 29CC698CB3; Mon, 14 Nov 2011 19:41:05 -0500 (EST)
Received: from marajade.sandelman.ca (localhost [127.0.0.1]) by marajade.sandelman.ca (Postfix) with ESMTP id 2513098CB2 for <homenet@ietf.org>; Mon, 14 Nov 2011 19:41:05 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ca>
To: homenet@ietf.org
In-Reply-To: <CA+XPzSY8cC_PyhcMNqhk4+B6tghp8Dpy2-3aMPZmyVRP=AWnaA@mail.gmail.com>
References: <DCC302FAA9FE5F4BBA4DCAD46569377914518AFAE5@PRVPEXVS03.corp.twcable.com> <4EB583C8.5030907@piuha.net> <13027.1320680393@marajade.sandelman.ca> <BDF2740C082F6942820D95BAEB9E1A845A9789@XMB-AMS-108.cisco.com> <CA+XPzSY8cC_PyhcMNqhk4+B6tghp8Dpy2-3aMPZmyVRP=AWnaA@mail.gmail.com>
X-Mailer: MH-E 8.1; nmh 1.3-dev; XEmacs 21.4 (patch 22)
Date: Mon, 14 Nov 2011 19:41:04 -0500
Message-ID: <3512.1321317664@marajade.sandelman.ca>
Sender: mcr@sandelman.ca
Subject: Re: [homenet] more comments on draft-arkko-homenet-prefix-assignment
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 00:41:09 -0000

>>>>> "Guillaume" == Guillaume Habault <guillaume.habault@gmail.com> writes:
    Guillaume> the host select the appropriate address, the routing
    Guillaume> protocol may route the 
    Guillaume> message to the wrong Customer Edge Router (especially if
    Guillaume> we are in the case 
    Guillaume> where there is more than one Customer Edge Router in the
    Guillaume> home network. 

We have assumed that the home gateways will cooperate and provide source
address routing, making sure that packets are routed out the link which
can accept that source address.

    Guillaume> However, it could work if Customer Edge Router can talk to each other)...
    Guillaume> And in the section 3.4, it is mentionned that :

    Guillaume> To Support multihoming within a homenet, a routing protocol that
    Guillaume> can make routing decisions based on source and destination
    Guillaume> addresses is desirable, to avoid upstream ISP ingress filtering
    Guillaume> problems.

    Guillaume> Do you plan to use both solution? or does it depend on
    Guillaume> the topology? Or 
    Guillaume> does the aim is to be generic and let implementer decide
    Guillaume> about the solution 
    Guillaume> to use ?

You need both pieces.
(Please consider a quoting mechanism that is more robust)

-- 
]       He who is tired of Weird Al is tired of life!           |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
   Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE>
	               then sign the petition. 

From jmh@joelhalpern.com  Mon Nov 14 16:46:39 2011
Return-Path: <jmh@joelhalpern.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8EC9411E80D0 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 16:46:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.265
X-Spam-Level: 
X-Spam-Status: No, score=-102.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D4crM-SoCqR8 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 16:46:39 -0800 (PST)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id 3482C11E80CF for <homenet@ietf.org>; Mon, 14 Nov 2011 16:46:39 -0800 (PST)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by morbo.tigertech.net (Postfix) with ESMTP id 06B39CAD90 for <homenet@ietf.org>; Mon, 14 Nov 2011 16:46:39 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id C53FB1BDC2D2 for <homenet@ietf.org>; Mon, 14 Nov 2011 16:46:38 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from [130.129.38.181] (dhcp-26b5.meeting.ietf.org [130.129.38.181]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id 6711E1BDC2CF for <homenet@ietf.org>; Mon, 14 Nov 2011 16:46:38 -0800 (PST)
Message-ID: <4EC1B66B.9000109@joelhalpern.com>
Date: Mon, 14 Nov 2011 19:46:35 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: homenet@ietf.org
References: <DCC302FAA9FE5F4BBA4DCAD46569377914518AFAE5@PRVPEXVS03.corp.twcable.com> <4EB583C8.5030907@piuha.net> <13027.1320680393@marajade.sandelman.ca> <BDF2740C082F6942820D95BAEB9E1A845A9789@XMB-AMS-108.cisco.com> <CA+XPzSY8cC_PyhcMNqhk4+B6tghp8Dpy2-3aMPZmyVRP=AWnaA@mail.gmail.com> <3512.1321317664@marajade.sandelman.ca>
In-Reply-To: <3512.1321317664@marajade.sandelman.ca>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [homenet] more comments on draft-arkko-homenet-prefix-assignment
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 00:46:39 -0000

Maybe I am missing something basic, but there seems to be a bit of a 
disconnect on our assumption about what we need to have in in-home rotuers.

On the one hand, earlier discussion emphasized that we need to use 
protocols and implementations that are well tested, robust, and simple 
to use.
On the other hand, we have an expectation that these same boxes are 
going to perform source address based forwarding selection, something 
with which there is very little experience anywhere?

Yours,
Joel

On 11/14/2011 7:41 PM, Michael Richardson wrote:
>
>>>>>> "Guillaume" == Guillaume Habault<guillaume.habault@gmail.com>  writes:
>      Guillaume>  the host select the appropriate address, the routing
>      Guillaume>  protocol may route the
>      Guillaume>  message to the wrong Customer Edge Router (especially if
>      Guillaume>  we are in the case
>      Guillaume>  where there is more than one Customer Edge Router in the
>      Guillaume>  home network.
>
> We have assumed that the home gateways will cooperate and provide source
> address routing, making sure that packets are routed out the link which
> can accept that source address.
>
>      Guillaume>  However, it could work if Customer Edge Router can talk to each other)...
>      Guillaume>  And in the section 3.4, it is mentionned that :
>
>      Guillaume>  To Support multihoming within a homenet, a routing protocol that
>      Guillaume>  can make routing decisions based on source and destination
>      Guillaume>  addresses is desirable, to avoid upstream ISP ingress filtering
>      Guillaume>  problems.
>
>      Guillaume>  Do you plan to use both solution? or does it depend on
>      Guillaume>  the topology? Or
>      Guillaume>  does the aim is to be generic and let implementer decide
>      Guillaume>  about the solution
>      Guillaume>  to use ?
>
> You need both pieces.
> (Please consider a quoting mechanism that is more robust)
>

From mcr@sandelman.ca  Mon Nov 14 17:05:08 2011
Return-Path: <mcr@sandelman.ca>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B42221F8F4B for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 17:05:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.594
X-Spam-Level: 
X-Spam-Status: No, score=-1.594 tagged_above=-999 required=5 tests=[AWL=0.360,  BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JXrTXGQ6Ootm for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 17:05:07 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id 6139621F8F4A for <homenet@ietf.org>; Mon, 14 Nov 2011 17:05:07 -0800 (PST)
Received: from marajade.sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by relay.sandelman.ca (Postfix) with ESMTPS id 3CAC6343CD for <homenet@ietf.org>; Mon, 14 Nov 2011 20:03:42 -0500 (EST)
Received: by marajade.sandelman.ca (Postfix, from userid 179) id 9EA3098CB3; Mon, 14 Nov 2011 20:05:07 -0500 (EST)
Received: from marajade.sandelman.ca (localhost [127.0.0.1]) by marajade.sandelman.ca (Postfix) with ESMTP id 996D898CB2 for <homenet@ietf.org>; Mon, 14 Nov 2011 20:05:07 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ca>
To: homenet@ietf.org
In-Reply-To: <CA+XPzSY8cC_PyhcMNqhk4+B6tghp8Dpy2-3aMPZmyVRP=AWnaA@mail.gmail.com>
References: <DCC302FAA9FE5F4BBA4DCAD46569377914518AFAE5@PRVPEXVS03.corp.twcable.com> <4EB583C8.5030907@piuha.net> <13027.1320680393@marajade.sandelman.ca> <BDF2740C082F6942820D95BAEB9E1A845A9789@XMB-AMS-108.cisco.com> <CA+XPzSY8cC_PyhcMNqhk4+B6tghp8Dpy2-3aMPZmyVRP=AWnaA@mail.gmail.com>
X-Mailer: MH-E 8.1; nmh 1.3-dev; XEmacs 21.4 (patch 22)
Date: Mon, 14 Nov 2011 20:05:07 -0500
Message-ID: <7140.1321319107@marajade.sandelman.ca>
Sender: mcr@sandelman.ca
Subject: Re: [homenet] more comments on draft-arkko-homenet-prefix-assignment
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 01:05:08 -0000

    Pascal Thubert (pthubert) <pthubert@cisco.com> wrote:

    >> Michael:
    >> 
    >> If you want your PAN network to be reachable from the rest of the world,
    >> you still need some mobility solution.
    >>
    >> For instance you could use NEMO. Get a PAN delegated from your home
    >> network and then move around with it.

I want my PAN network reachable (and able to reach) the Home network of
the home that I'm in, so exactly:

    >> For local communications, yes you'll want to inject the PAN network
    >> prefix into the local topology.
    >> If the local topology trusts you to inject anything which is not a
    >> given.
    >> 
    >> The combination of the 2 is basically what MANEMO tried to achieve a few
    >> years ago, using what became RPL as the underlying routing protocol.
    >> Maybe the times are getting ripe.

Yes....  Perhaps you see why I care little about Zigbee in my RPL work ;-)

-- 
]       He who is tired of Weird Al is tired of life!           |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
   Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE>
	               then sign the petition. 


From Ray.Bellis@nominet.org.uk  Mon Nov 14 17:08:55 2011
Return-Path: <Ray.Bellis@nominet.org.uk>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BA201F0C8B for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 17:08:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.479
X-Spam-Level: 
X-Spam-Status: No, score=-9.479 tagged_above=-999 required=5 tests=[AWL=1.120,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RDnrFW3hxhxc for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 17:08:55 -0800 (PST)
Received: from mx4.nominet.org.uk (mx4.nominet.org.uk [213.248.199.24]) by ietfa.amsl.com (Postfix) with ESMTP id 387001F0C9B for <homenet@ietf.org>; Mon, 14 Nov 2011 17:08:54 -0800 (PST)
DomainKey-Signature: s=main.dk.nominet.selector; d=nominet.org.uk; c=nofws; q=dns; h=X-IronPort-AV:Received:Received:From:To:Subject: Thread-Topic:Thread-Index:Date:Message-ID:Accept-Language: Content-Language:X-MS-Has-Attach:X-MS-TNEF-Correlator: Content-Type:Content-ID:Content-Transfer-Encoding: MIME-Version; b=hRhmjhrVzHTtN1AOqtZgATxtARBsazQzQD83rV5hp+EFL34JEklhtQiA 2Jsb0tdx1CqtYpffnHplHhWVGtMW/7md8HQfgdft1RovNr+X1tPQXMyio kEVLK6xnvpJFLLi;
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nominet.org.uk; i=Ray.Bellis@nominet.org.uk; q=dns/txt; s=main.dkim.nominet.selector; t=1321319334; x=1352855334; h=from:sender:reply-to:subject:date:message-id:to:cc: mime-version:content-transfer-encoding:content-id: content-description:resent-date:resent-from:resent-sender: resent-to:resent-cc:resent-message-id:in-reply-to: references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:list-owner:list-archive; z=From:=20Ray=20Bellis=20<Ray.Bellis@nominet.org.uk> |Subject:=20Meeting=20Materials|Date:=20Tue,=2015=20Nov =202011=2001:08:49=20+0000|Message-ID:=20<BF488687-6FFB-4 A61-91D3-5DDFD5CA5298@nominet.org.uk>|To:=20"homenet@ietf .org"=20<homenet@ietf.org>|MIME-Version:=201.0 |Content-Transfer-Encoding:=20quoted-printable |Content-ID:=20<5ec5347c-b98b-4d21-a61f-606597790c84>; bh=IS8ZMM9JQvzgX5t0RyFUfrt7RxAwPgqrOXBktLMsg40=; b=LI0yPmv4i8xziH6FtayZeK/3l/Bo1jicHxuBLLYP65R50kBdOGOFgAx+ xYIbYBrzYzdyav8kwFXNnJpitxekll3Mze5jkSkJpm4q9SZNyvldBD6Lc fgg2b5iO3CIsVAS;
X-IronPort-AV: E=Sophos;i="4.69,512,1315177200"; d="scan'208";a="29554329"
Received: from wds-exc2.okna.nominet.org.uk ([213.248.197.145]) by mx4.nominet.org.uk with ESMTP; 15 Nov 2011 01:08:53 +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%19]) with mapi; Tue, 15 Nov 2011 01:08:52 +0000
From: Ray Bellis <Ray.Bellis@nominet.org.uk>
To: "homenet@ietf.org" <homenet@ietf.org>
Thread-Topic: Meeting Materials
Thread-Index: AQHMozMjv11EbjMOfEKoSBFZqC8RaA==
Date: Tue, 15 Nov 2011 01:08:49 +0000
Message-ID: <BF488687-6FFB-4A61-91D3-5DDFD5CA5298@nominet.org.uk>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-ID: <5ec5347c-b98b-4d21-a61f-606597790c84>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [homenet] Meeting Materials
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 01:08:55 -0000

All of the meeting materials are visible at:

<https://datatracker.ietf.org/meeting/82/materials.html>

Unfortunately the meeting agenda page on the Tools website is not updated i=
n real-time as materials are uploaded so is out of date.

Ray


From lorenzo@google.com  Mon Nov 14 17:42:03 2011
Return-Path: <lorenzo@google.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C52911E80DD for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 17:42:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.85
X-Spam-Level: 
X-Spam-Status: No, score=-102.85 tagged_above=-999 required=5 tests=[AWL=0.126, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TMK0OcA1z2yr for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 17:42:02 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id CFC9911E817F for <homenet@ietf.org>; Mon, 14 Nov 2011 17:42:02 -0800 (PST)
Received: by ywt34 with SMTP id 34so5561020ywt.31 for <homenet@ietf.org>; Mon, 14 Nov 2011 17:42:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=mime-version:from:date:message-id:subject:to:cc:content-type :x-system-of-record; bh=fwRaWpt3IRVqNgDCoJLzI5lOsXzPNuB6MQVbkNWHw4w=; b=NgEG2bstg4IAKfbBdBzuEMZvYJe3eqD7a/h5pzmbzuJdGkslxGTUSBLbenQdd4EGxI yKw0DZLP3JBXmzleqdZg==
Received: by 10.101.139.15 with SMTP id r15mr7129242ann.161.1321321322442; Mon, 14 Nov 2011 17:42:02 -0800 (PST)
Received: by 10.101.139.15 with SMTP id r15mr7129230ann.161.1321321322238; Mon, 14 Nov 2011 17:42:02 -0800 (PST)
MIME-Version: 1.0
Received: by 10.150.202.14 with HTTP; Mon, 14 Nov 2011 17:41:40 -0800 (PST)
From: Lorenzo Colitti <lorenzo@google.com>
Date: Tue, 15 Nov 2011 09:41:40 +0800
Message-ID: <CAKD1Yr3uSsNP4avZBdQE7YxFd7D_KOXBOCsfaRfvnWhJoLoY9Q@mail.gmail.com>
To: homenet@ietf.org
Content-Type: multipart/alternative; boundary=0016e68e7f8b0bd1af04b1bc181b
X-System-Of-Record: true
Cc: Acee Lindem <acee.lindem@ericsson.com>, Jari Arkko <jari.arkko@piuha.net>
Subject: [homenet] Comments on draft-acee-ospf-ospfv3-autoconfig-00
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 01:42:03 -0000

--0016e68e7f8b0bd1af04b1bc181b
Content-Type: text/plain; charset=ISO-8859-1

Apologies if ther's already a public comment thread on this; I couldn't
find it. Please feel free to hand me a cluepon.

1. I think the OSPFv3 router ID should not be based on the MAC address
because that will encourage people to assume it's unique "most of the
time". I think we should just make it a pseudo-random number so it's clear
that uniqueness is only guaranteed by collision detection and that
collision detection needs to be robust.

2. The draft mentions links but vaguely says they are "not applicable
to auto-configuration".
Should we just clearly say at the beginning that they're out of scope and
will not work? Or do we need them?

3. Can we use normal LSAs to detect collisions? One idea would be "if you
see your own router ID in the list of neighbours of a network LSA or router
LSA, then there is a collision". Will that work? If so we wouldn't need the
hardware fingerprint at all.

4. For security, I think we should pick an auth scheme and stick to
it, otherwise
it will just lead to fragmentation. Some pre-shared key scheme might be
adequate; I don't know much about security so I don't really care what it
is, but I do think we need to have one and it needs to be the same for
everyone. I think we should say MUST here.

Cheers,
lorenzo

--0016e68e7f8b0bd1af04b1bc181b
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Apologies if ther&#39;s already a public comment thread on this; I couldn&#=
39;t find it. Please feel free to hand me a cluepon.<div><br></div><div>1. =
I think the OSPFv3 router ID should not be based on the MAC address because=
 that will encourage people to assume it&#39;s unique &quot;most of the tim=
e&quot;. I think we should just make it a pseudo-random number so it&#39;s =
clear that uniqueness is only guaranteed by collision detection and that co=
llision detection needs to be robust.</div>

<div><br></div><div>2. The draft mentions links but vaguely says they are &=
quot;<span style=3D"background-color: transparent; ">not applicable to=A0</=
span><span style=3D"background-color: transparent; ">auto-configuration&quo=
t;. Should we just clearly say at the beginning that they&#39;re out of sco=
pe and will not work? Or do we need them?</span></div>

<div><span style=3D"background-color: transparent; "><br></span></div><div>=
<span style=3D"background-color: transparent; ">3. Can we use normal LSAs t=
o detect collisions? One idea would be &quot;if you see your own router ID =
in the list of neighbours of a network LSA or router LSA, then there is a c=
ollision&quot;. Will that work? If so we wouldn&#39;t need the hardware fin=
gerprint at all.</span></div>

<div><span style=3D"background-color: transparent; "><br></span></div><div>=
<span style=3D"background-color: transparent; ">4. For security, I think we=
 should pick an auth scheme and stick to it,=A0</span><span style=3D"backgr=
ound-color: transparent; ">otherwise it will just lead to fragmentation</sp=
an><span style=3D"background-color: transparent; ">. Some pre-shared key sc=
heme might be adequate; I don&#39;t know much about security so I don&#39;t=
 really care what it is, but I do think we need to have one and it needs to=
 be the same for everyone. I think we should say MUST here.</span></div>

<div><br></div><div>Cheers,</div><div>lorenzo</div>

--0016e68e7f8b0bd1af04b1bc181b--

From brian.e.carpenter@gmail.com  Mon Nov 14 17:42:38 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C9DE11E80CC for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 17:42:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.523
X-Spam-Level: 
X-Spam-Status: No, score=-103.523 tagged_above=-999 required=5 tests=[AWL=0.076, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FAx-165OVk5c for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 17:42:37 -0800 (PST)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id BDDEE11E8099 for <homenet@ietf.org>; Mon, 14 Nov 2011 17:42:37 -0800 (PST)
Received: by vws5 with SMTP id 5so6834591vws.31 for <homenet@ietf.org>; Mon, 14 Nov 2011 17:42:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=MHgrCSjwHY/+bdYu3wWpKqYxE0+Ypk6WvyBupp4SiZ0=; b=BtGefTHKAq3RbfLgDV//2U13SfZoeEG+b0+bsRXVBDoSWJuO1j/LLnlWZv7RH57hkm MXZopdoSUgT9dQkIDKEvzBkJ2ibM0hMdk5vXYvnieN1fRlllcZ61IskEWzJeFIFGBr5G 5NAgUqbcFLxW3y2cxRprFcVa/ENkPL1BS1ijQ=
Received: by 10.224.211.194 with SMTP id gp2mr15762745qab.99.1321321357140; Mon, 14 Nov 2011 17:42:37 -0800 (PST)
Received: from [130.129.19.92] (dhcp-135c.meeting.ietf.org. [130.129.19.92]) by mx.google.com with ESMTPS id o15sm15132964qaz.19.2011.11.14.17.42.35 (version=SSLv3 cipher=OTHER); Mon, 14 Nov 2011 17:42:36 -0800 (PST)
Message-ID: <4EC1C386.6010802@gmail.com>
Date: Tue, 15 Nov 2011 14:42:30 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: homenet@ietf.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: [homenet] pervasive v4
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 01:42:38 -0000

If homenet is going to support arbitrary self-configuring topologies,
and pervasive legacy IPv4 is required, we'd surely end up recommending
NAT444-within-the-home as the only remotely practicable approach.
But any such approach would bring in many problems that appear to be
deeply insoluble for IPv4. iirc that was one of the reasons that IPv6
was designed the way it is.

I think we have to recognise that the IPv4 constraint can only apply to
the very simplest homenet topologies.

-- 
Regards
   Brian Carpenter



From mcr@sandelman.ca  Mon Nov 14 17:45:50 2011
Return-Path: <mcr@sandelman.ca>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F279411E81DE for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 17:45:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.606
X-Spam-Level: 
X-Spam-Status: No, score=-1.606 tagged_above=-999 required=5 tests=[AWL=0.348,  BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4N8GtYCrAMsi for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 17:45:49 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id 78F7911E8192 for <homenet@ietf.org>; Mon, 14 Nov 2011 17:45:49 -0800 (PST)
Received: from marajade.sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by relay.sandelman.ca (Postfix) with ESMTPS id 48F2034012 for <homenet@ietf.org>; Mon, 14 Nov 2011 20:44:22 -0500 (EST)
Received: by marajade.sandelman.ca (Postfix, from userid 179) id 7592F98CB3; Mon, 14 Nov 2011 20:45:47 -0500 (EST)
Received: from marajade.sandelman.ca (localhost [127.0.0.1]) by marajade.sandelman.ca (Postfix) with ESMTP id 6656998CB2 for <homenet@ietf.org>; Mon, 14 Nov 2011 20:45:47 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ca>
To: homenet <homenet@ietf.org>
X-Mailer: MH-E 8.1; nmh 1.3-dev; XEmacs 21.4 (patch 22)
Date: Mon, 14 Nov 2011 20:45:47 -0500
Message-ID: <13919.1321321547@marajade.sandelman.ca>
Sender: mcr@sandelman.ca
Subject: [homenet] secret sharing among devices
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 01:45:50 -0000

There have been various discussion in PHL about spreading a secret among
devices so they can authenticate each other.

A super cool idea is a specifically formatted file on a USB drive,
inserted into each system in turn.  While we might be pretty sure
the USB drive (and file system and connector, etc.) is out of scope, the
format for that secret file might be well in scope.

I'd like to suggest that the file format is in scope for the security
work, and would be willing to document such a thing.  (I actually think
the KEYPROV work can be readily adapted)

-- 
]       He who is tired of Weird Al is tired of life!           |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
   Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE>
	               then sign the petition. 


From nordmark@cisco.com  Mon Nov 14 17:50:22 2011
Return-Path: <nordmark@cisco.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A60311E817C for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 17:50:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.266
X-Spam-Level: 
X-Spam-Status: No, score=-6.266 tagged_above=-999 required=5 tests=[AWL=0.333,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x+IgcALE2ZuV for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 17:50:22 -0800 (PST)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id 24CED11E80CC for <homenet@ietf.org>; Mon, 14 Nov 2011 17:50:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=nordmark@cisco.com; l=1017; q=dns/txt; s=iport; t=1321321822; x=1322531422; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=OOxbdGF/SjQrY1c/eeG3H1VHJ2p2E+inqYREDLH+Y0E=; b=O/7Ndx0g/6KG2R+QHp8GsXcWYaI7XGuidEK8Zk6eRVfYYaDZ9vg3S5sf pO5/hLNWEs+yMA9MNRScaNwLx+m139yb9/p6NpzXNnE1YhL91oO/bPARA 1ETokhWVSokAapccFpIfowYB3dlMtxoYYiQDxlTe35ltJJ2AqVQutsJea I=;
X-IronPort-AV: E=Sophos;i="4.69,512,1315180800"; d="scan'208";a="14287985"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-4.cisco.com with ESMTP; 15 Nov 2011 01:50:22 +0000
Received: from [130.129.83.144] (sjc-vpn7-1190.cisco.com [10.21.148.166]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id pAF1oK9w005032; Tue, 15 Nov 2011 01:50:21 GMT
Message-ID: <4EC1C566.2060400@cisco.com>
Date: Mon, 14 Nov 2011 17:50:30 -0800
From: Erik Nordmark <nordmark@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <4EC1C386.6010802@gmail.com>
In-Reply-To: <4EC1C386.6010802@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: homenet@ietf.org
Subject: Re: [homenet] pervasive v4
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 01:50:22 -0000

On 11/14/11 5:42 PM, Brian E Carpenter wrote:
> If homenet is going to support arbitrary self-configuring topologies,
> and pervasive legacy IPv4 is required, we'd surely end up recommending
> NAT444-within-the-home as the only remotely practicable approach.
> But any such approach would bring in many problems that appear to be
> deeply insoluble for IPv4. iirc that was one of the reasons that IPv6
> was designed the way it is.

Brian,

NAT444 doesn't work in an arbitrary topology since you can end up with 
loops through the NATs, and the WG seems to want to support arbitrary 
topologies.

But using whatever prefix assignment method we come up with for IPv6 to 
also hand out subnets out of 192.168/16 works just fine; do NAT44 in the 
customer edge router and route IPv4 (and IPv6) inside the home (using 
whatever routing protocol we choose to route IPv6.

    Erik

> I think we have to recognise that the IPv4 constraint can only apply to
> the very simplest homenet topologies.
>


From mellon@fugue.com  Mon Nov 14 17:53:00 2011
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82D1C11E812C for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 17:53:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.181
X-Spam-Level: 
X-Spam-Status: No, score=-2.181 tagged_above=-999 required=5 tests=[AWL=0.418,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2LOrAd-rkJCK for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 17:52:59 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id A335211E8275 for <homenet@ietf.org>; Mon, 14 Nov 2011 17:52:59 -0800 (PST)
Received: from [IPv6:2001:df8::80:9458:4948:63d6:ca83] (unknown [IPv6:2001:df8:0:80:9458:4948:63d6:ca83]) by toccata.fugue.com (Postfix) with ESMTPSA id 3930D2381CA1; Mon, 14 Nov 2011 20:52:56 -0500 (EST)
References: <13919.1321321547@marajade.sandelman.ca>
In-Reply-To: <13919.1321321547@marajade.sandelman.ca>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii
Message-Id: <A1DF7C4C-276C-4E4C-AC9D-05F2B122236C@fugue.com>
X-Mailer: iPad Mail (9A334)
From: Ted Lemon <mellon@fugue.com>
Date: Tue, 15 Nov 2011 09:53:22 +0800
To: Michael Richardson <mcr@sandelman.ca>
Cc: homenet <homenet@ietf.org>
Subject: Re: [homenet] secret sharing among devices
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 01:53:00 -0000

On Nov 15, 2011, at 9:45 AM, Michael Richardson <mcr@sandelman.ca> wrote:
> I'd like to suggest that the file format is in scope for the security
> work, and would be willing to document such a thing.  (I actually think
> the KEYPROV work can be readily adapted)

I definitely support this proposal.   :)


From brian.e.carpenter@gmail.com  Mon Nov 14 18:19:43 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5749F11E8333 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 18:19:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.534
X-Spam-Level: 
X-Spam-Status: No, score=-103.534 tagged_above=-999 required=5 tests=[AWL=0.065, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JhG2+MstXrtB for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 18:19:42 -0800 (PST)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id B107C11E8332 for <homenet@ietf.org>; Mon, 14 Nov 2011 18:19:42 -0800 (PST)
Received: by vcbfk1 with SMTP id fk1so6757790vcb.31 for <homenet@ietf.org>; Mon, 14 Nov 2011 18:19:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=8tuh4lB2Awngwm+rlxzYau9ME3CBGswisbsUNCfNWWY=; b=m1Ij4q8kdYuMjw0Xx3V1BT1acwRw2NoctwGBTZtCMSkiNvJ5/ceByGyg+WhXapg9lB vCFl7/nKavEb060UYReEMu2j3e6Yp9cdEG47LkxA0psNiLv80hwazd9wJknGbbdUHear 4yqG7bkRBGkMzIMiTSyqgm86uC2v1V/DodiXY=
Received: by 10.229.69.160 with SMTP id z32mr3575000qci.223.1321323582105; Mon, 14 Nov 2011 18:19:42 -0800 (PST)
Received: from [130.129.19.92] (dhcp-135c.meeting.ietf.org. [130.129.19.92]) by mx.google.com with ESMTPS id f6sm23212881qac.21.2011.11.14.18.19.31 (version=SSLv3 cipher=OTHER); Mon, 14 Nov 2011 18:19:32 -0800 (PST)
Message-ID: <4EC1CC2E.30209@gmail.com>
Date: Tue, 15 Nov 2011 15:19:26 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Erik Nordmark <nordmark@cisco.com>
References: <4EC1C386.6010802@gmail.com> <4EC1C566.2060400@cisco.com>
In-Reply-To: <4EC1C566.2060400@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: homenet@ietf.org
Subject: Re: [homenet] pervasive v4
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 02:19:43 -0000

On 2011-11-15 14:50, Erik Nordmark wrote:
> On 11/14/11 5:42 PM, Brian E Carpenter wrote:
>> If homenet is going to support arbitrary self-configuring topologies,
>> and pervasive legacy IPv4 is required, we'd surely end up recommending
>> NAT444-within-the-home as the only remotely practicable approach.
>> But any such approach would bring in many problems that appear to be
>> deeply insoluble for IPv4. iirc that was one of the reasons that IPv6
>> was designed the way it is.
> 
> Brian,
> 
> NAT444 doesn't work in an arbitrary topology since you can end up with
> loops through the NATs, and the WG seems to want to support arbitrary
> topologies.

Right... we could always invent a spanning tree protocol for NAT of course :-).

> 
> But using whatever prefix assignment method we come up with for IPv6 to
> also hand out subnets out of 192.168/16 works just fine; do NAT44 in the
> customer edge router and route IPv4 (and IPv6) inside the home (using
> whatever routing protocol we choose to route IPv6.

Yes, but then we're extending v4 and expecting homenets to run (presumably) RIP.
That seems kind of out of scope for this WG.

   Bria

> 
>    Erik
> 
>> I think we have to recognise that the IPv4 constraint can only apply to
>> the very simplest homenet topologies.
>>
> 
> 

From acee.lindem@ericsson.com  Mon Nov 14 18:26:01 2011
Return-Path: <acee.lindem@ericsson.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6618211E837E for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 18:26:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.516
X-Spam-Level: 
X-Spam-Status: No, score=-6.516 tagged_above=-999 required=5 tests=[AWL=0.083,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cHUpxlf-WCR8 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 18:26:00 -0800 (PST)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 5328B11E8390 for <homenet@ietf.org>; Mon, 14 Nov 2011 18:26:00 -0800 (PST)
Received: from eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id pAF2Pu0V022478; Mon, 14 Nov 2011 20:25:57 -0600
Received: from EUSAACMS0702.eamcs.ericsson.se ([169.254.1.218]) by eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) with mapi; Mon, 14 Nov 2011 21:25:56 -0500
From: Acee Lindem <acee.lindem@ericsson.com>
To: Lorenzo Colitti <lorenzo@google.com>
Date: Mon, 14 Nov 2011 21:25:53 -0500
Thread-Topic: Comments on draft-acee-ospf-ospfv3-autoconfig-00
Thread-Index: AcyjPecuLFzTL+4BQDyIouvYiZJhYg==
Message-ID: <B3BE775A-4EBB-4C17-9EDC-7B9AFCB8867E@ericsson.com>
References: <CAKD1Yr3uSsNP4avZBdQE7YxFd7D_KOXBOCsfaRfvnWhJoLoY9Q@mail.gmail.com>
In-Reply-To: <CAKD1Yr3uSsNP4avZBdQE7YxFd7D_KOXBOCsfaRfvnWhJoLoY9Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/signed; boundary="Apple-Mail-44--580630118"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
Cc: "homenet@ietf.org" <homenet@ietf.org>, Jari Arkko <jari.arkko@piuha.net>
Subject: Re: [homenet] Comments on draft-acee-ospf-ospfv3-autoconfig-00
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 02:26:01 -0000

--Apple-Mail-44--580630118
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi Lorenzo,

On Nov 14, 2011, at 8:41 PM, Lorenzo Colitti wrote:

> Apologies if ther's already a public comment thread on this; I =
couldn't find it. Please feel free to hand me a cluepon.
>=20
> 1. I think the OSPFv3 router ID should not be based on the MAC address =
because that will encourage people to assume it's unique "most of the =
time". I think we should just make it a pseudo-random number so it's =
clear that uniqueness is only guaranteed by collision detection and that =
collision detection needs to be robust.

The draft requires duplicate Router-ID detection and resolution. I don't =
think that the fact that a portion of the MAC address is used as a first =
try is reason for this detection/resolution not to be implemented or =
tested.=20

>=20
> 2. The draft mentions links but vaguely says they are "not applicable =
to auto-configuration". Should we just clearly say at the beginning that =
they're out of scope and will not work? Or do we need them?

I think you mean virtual links. They are definitely not needed in the =
auto-configured environment as they are for providing a backbone path =
through a transit area and the OSPFv3 auto-configured routing domain =
assumes only a backbone area.=20


>=20
> 3. Can we use normal LSAs to detect collisions? One idea would be "if =
you see your own router ID in the list of neighbours of a network LSA or =
router LSA, then there is a collision". Will that work? If so we =
wouldn't need the hardware fingerprint at all.

No. In an arbitrary topology, A router with a duplicate router-id can be =
multiple hops away.=20

>=20
> 4. For security, I think we should pick an auth scheme and stick to =
it, otherwise it will just lead to fragmentation. Some pre-shared key =
scheme might be adequate; I don't know much about security so I don't =
really care what it is, but I do think we need to have one and it needs =
to be the same for everyone. I think we should say MUST here.

If the pre-shared key is hard-coded, it is no better than the OSPFv3 =
Interface Instance ID that is specified to prevent inadvertent =
adjacencies with routers not supporting the auto-configuration. If =
configuration of a pre-shared key is required, you no longer have =
auto-configuration.=20

Thanks,=20
Acee=20



>=20
> Cheers,
> lorenzo


--Apple-Mail-44--580630118
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIM8jCCBDQw
ggMcoAMCAQICECFWwVQHDV12M/Sr0yNv0sYwDQYJKoZIhvcNAQEFBQAwOTERMA8GA1UECgwIRXJp
Y3Nzb24xJDAiBgNVBAMMG0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMTAeFw0xMDEwMDEyMDA0
NTlaFw0xMzEwMDEyMDA0NDhaMG8xETAPBgNVBAoMCEVyaWNzc29uMR8wHQYDVQQDDBZBY2VlIExp
bmRlbSBMaW5kZW0gSUlJMRAwDgYDVQQFEwdlYWxmbGluMScwJQYJKoZIhvcNAQkBFhhhY2VlLmxp
bmRlbUBlcmljc3Nvbi5jb20wgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAI/Dc9ALiZuBMyuv
bsc3eBxjXZpMi45Z0vzsUQZTJGTBeY7p9JsdzXC9J1uMisBxYVi39R3KJo6I4hXVp9wrA1rxh4AE
bnP1+Gxfpj33uWEFYbBnVAJkIWYWF7CYTn8Zm/yd13vPXtuGA6ESeLnnJafwC9Y0YwUQ+4HX7PNv
uauVAgMBAAGjggGEMIIBgDCBwAYDVR0fBIG4MIG1MIGyoIGvoIGshjdodHRwOi8vY3JsLnRydXN0
LnRlbGlhLmNvbS9Fcmljc3Nvbk5MSW5kaXZpZHVhbENBMDEuY3JshnFsZGFwOi8vbGRhcC50cnVz
dC50ZWxpYS5jb20vY249RXJpY3Nzb24lMjBOTCUyMEluZGl2aWR1YWwlMjBDQTAxLG89RXJpY3Nz
b24/Y2VydGlmaWNhdGVyZXZvY2F0aW9ubGlzdDtiaW5hcnk/YmFzZTAjBgNVHREEHDAagRhhY2Vl
LmxpbmRlbUBlcmljc3Nvbi5jb20wRgYDVR0gBD8wPTA7BgYqhXBrAQEwMTAvBggrBgEFBQcCARYj
aHR0cDovL3d3dy5lcmljc3Nvbi5jb20vbGVnYWwuc2h0bWwwHQYDVR0OBBYEFAgOzAPuplmPr7C1
BTqV94OyqUdhMB8GA1UdIwQYMBaAFJYnw7jepV9dRD45UuVFsXZfYzCbMA4GA1UdDwEB/wQEAwIF
oDANBgkqhkiG9w0BAQUFAAOCAQEAE1gyNW6c2t/YsLxW5sm67+gVGK0Lnge4ub+k8dgGrK7Mj7em
nkOIFkjdv/tqdJ/SoUy/WEkBXba2TfpZ+lfluMgLYux1vSvqBUxYBsUHeNth2Q/Y6A9sCaDTBPlK
vZ2jLz814NavrVfgTCLdxX6zNtGdwzhviz+FyqyxYF43Q86RP8Gd/Npaz1W8pmYAHm0+lezuTx5k
F3Av3+SaZ/MR6s+RWuXEIdED36ajeQz+OG8Mh3nplofzdrOeoWGDz53YlfRhgj+TXo+H1lclZAvD
WVaMMXPdb27h9Hngsq87dkCW9uAyv8DI993rdhqzlEgUyQIL32icAXfTmTYgoGPOwjCCBEUwggMt
oAMCAQICEBPJ6v/eJq2p3KTKI4GDR+MwDQYJKoZIhvcNAQEFBQAwRDEaMBgGA1UECgwRVGVsaWFT
b25lcmEgR3JvdXAxJjAkBgNVBAMMHVRlbGlhU29uZXJhIFB1YmxpYyBSb290IENBIHYxMB4XDTA2
MTAwNjEwMDA1M1oXDTE2MTAwMjA1MDQxN1owOTERMA8GA1UECgwIRXJpY3Nzb24xJDAiBgNVBAMM
G0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoC
ggEBALYQd+Q1HuuHxDyNGFlEPzCxuPPFO5W2xyr+nqCVnNJ4QYFe1HACqavqNLwUGIqIEyHv1rLn
fub9LBc7dQpRHjl/dggin0ONOFJ36nbGEbfHjLJz2BzOWvwl84Sc+Fx09IrDU/SZSWFSfhqTu3TT
39h79brHdRkdPBUgBYgsiFKriHI0TjP5G8628H27BDzqUpzGLSYWgt6/tpwuOH5lcfNfHWMcCYXR
lobv0Klu8lxG5amWqAnqrH6ECOyYJTRbHTsaTIZOHy9Qw/0eXPujKT7tU5xxSI2SdceJqzUbAz2o
FRQ6Px7/GydpM/Rl+qYoGPcauHUL1aSeVJZqDFqcIF0CAwEAAaOCATwwggE4MBIGA1UdEwEB/wQI
MAYBAf8CAQAwRgYDVR0gBD8wPTA7BgcqhXAjAgEBMDAwLgYIKwYBBQUHAgEWImh0dHBzOi8vcmVw
b3NpdG9yeS50cnVzdC50ZWxpYS5jb20wgYkGA1UdHwSBgTB/MH2ge6B5hndsZGFwOi8vbGRhcC50
cnVzdC50ZWxpYS5jb20vY249VGVsaWFTb25lcmElMjBQdWJsaWMlMjBSb290JTIwQ0ElMjB2MSxv
PVRlbGlhU29uZXJhJTIwR3JvdXA/YXV0aG9yaXR5cmV2b2NhdGlvbmxpc3Q/YmFzZTAOBgNVHQ8B
Af8EBAMCAQYwHQYDVR0OBBYEFJYnw7jepV9dRD45UuVFsXZfYzCbMB8GA1UdIwQYMBaAFEXb8I+4
GmKhqCMbY4g4o9vgGmLxMA0GCSqGSIb3DQEBBQUAA4IBAQB2AEoqQz+M3Ra9alkpn/YnwhXIv6tP
jhUvSuNs00Nhd0T9XhlIU3a65CaB/UKSqnayE0t7Q0Qq3r+x/GK3in/mik8i/PK2/q8HutzYFSzz
6Npztpo2JG7AEKOJPVaeebjng45m6vNC7RIfzU9sG2LBR/hewS8s6dFFn70w795xUwJBWZ67OzIK
XrIVVvHTOYpbWA+MESKAXwFhnVONrOTWlVwrMUi4HbiPWpOk+xQbgehCEi7mu3cXsaU1Xq3kMXui
NuC7VKoob8mFO9o9RT+dlirD2uRXwNpvCu3but6Kyhu0+nvy2iXGKjdlxlWTsdDyulXYz+OYCMZ9
lFWRzMIPMIIEbTCCA1WgAwIBAgIRAJywjASay5cieGNithuGWj0wDQYJKoZIhvcNAQEFBQAwOjEZ
MBcGA1UEChMQUlNBIFNlY3VyaXR5IEluYzEdMBsGA1UECxMUUlNBIFNlY3VyaXR5IDIwNDggVjMw
HhcNMDYxMDMxMjA0MjI3WhcNMTYxMTAxMTU0MjI1WjBEMRowGAYDVQQKDBFUZWxpYVNvbmVyYSBH
cm91cDEmMCQGA1UEAwwdVGVsaWFTb25lcmEgUHVibGljIFJvb3QgQ0EgdjEwggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQDKTxADapCAq3mplX4R4gNt+WZe5QKGnaVEQSyY7lICKF5DuVdW
PMLHDjzhw5IzDd860ZZx/0VrhGB3DmP4SDIWCKo2PxvY5NckdBWPWp/T2uaQdOAwgqHpN0pe1X7/
jel59WsWYXKGg/81Wth73ZK/geE7Gz9Pvj1LU6N4YhLMgooxKnCS+ZjB5icWAg+Qd1QpQhF46H1i
bp6LsBWDp56MPpg8F5X6y7MGVcKYLdnLOPs84uxRW9qs1kBopzQBj6s5SyVh8A+j5liDBjghXYpw
/+paGEdqHPeSFYxZKeJatmjEKLYlxcZWRKf436KvQA9jBhMEmytMNbGicR1mRH6tAgMBAAGjggFi
MIIBXjAfBgNVHSMEGDAWgBQHw1EwpKrpRa41JPr/JCwz0LGdjDAdBgNVHQ4EFgQURdvwj7gaYqGo
IxtjiDij2+AaYvEwEgYDVR0TAQH/BAgwBgEB/wIBBDCBhQYDVR0gBH4wfDA9BgkqhkiG9w0FBgEw
MDAuBggrBgEFBQcCARYiaHR0cHM6Ly9yZXBvc2l0b3J5LnRydXN0LnRlbGlhLmNvbTA7BgcqhXAj
AgEBMDAwLgYIKwYBBQUHAgEWImh0dHBzOi8vcmVwb3NpdG9yeS50cnVzdC50ZWxpYS5jb20wcAYD
VR0fBGkwZzBloGOgYYZfaHR0cDovL3d3dy5yc2FzZWN1cml0eS5jb20vcHJvZHVjdHMva2Vvbi9y
ZXBvc2l0b3J5L2NlcnRpZmljYXRlX3N0YXR1cy9SU0FfU2VjdXJpdHlfMjA0OF92My5DUkwwDgYD
VR0PAQH/BAQDAgEGMA0GCSqGSIb3DQEBBQUAA4IBAQAEXpos2CnIm7/872ytSrEHWZgvhOUEkUm2
5PWf/XkWko41TaL9vIS1S6AdWChNqWmnYiS7GfaIiDM9s1D6K7hidWBDOm46bNdM3ZwhMyDCfkDJ
SgeJ0w+7YmjvChu7gWqDZCsbtZ5gA1ixCTdDnuZB67JGSPGW6r73coraDP8diOpiQouMvM6bKuTP
BH/1poLccsUxsKgrQ23JC9LWCRb8cYHkZjXFH1K44TsIl5Lne2oT0JI3pwdA2v6jO4p/OLHntP+n
pjwPbedMPUZkDYCkd3LSxj8c3JTxtA8SlPCtIHE1hh65xihg1JRIliSphrqr9kbfwHdeVxPdOI5G
tDYPMYICEjCCAg4CAQEwTTA5MREwDwYDVQQKDAhFcmljc3NvbjEkMCIGA1UEAwwbRXJpY3Nzb24g
TkwgSW5kaXZpZHVhbCBDQTAxAhAhVsFUBw1ddjP0q9Mjb9LGMAkGBSsOAwIaBQCgggEbMBgGCSqG
SIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMTExNTAyMjU1M1owIwYJKoZI
hvcNAQkEMRYEFAPiRrLobYBaGp7jZhJ95/yCa44SMFwGCSsGAQQBgjcQBDFPME0wOTERMA8GA1UE
CgwIRXJpY3Nzb24xJDAiBgNVBAMMG0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMQIQIVbBVAcN
XXYz9KvTI2/SxjBeBgsqhkiG9w0BCRACCzFPoE0wOTERMA8GA1UECgwIRXJpY3Nzb24xJDAiBgNV
BAMMG0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMQIQIVbBVAcNXXYz9KvTI2/SxjANBgkqhkiG
9w0BAQEFAASBgBpA2WQQCnwJwTevfGJZhe8JB2QtbXG8mQqdOB5J873Zkb3HqMoUDIpttTLxMhN6
OON/L+9b0ITqcMlgXSSrl9hU0abhIaiRge/azsSh1IXZe7gjs/pYe8GyvcdxnSzjgi2a7C8p9LSH
1EWXF59vRACtCe5MRlz3tubdlk+B9umnAAAAAAAA

--Apple-Mail-44--580630118--

From mcr@sandelman.ca  Mon Nov 14 18:26:31 2011
Return-Path: <mcr@sandelman.ca>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 42C9211E836A for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 18:26:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.617
X-Spam-Level: 
X-Spam-Status: No, score=-1.617 tagged_above=-999 required=5 tests=[AWL=0.337,  BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2oZWd0dgEMT7 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 18:26:30 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id D795411E837E for <homenet@ietf.org>; Mon, 14 Nov 2011 18:26:30 -0800 (PST)
Received: from marajade.sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by relay.sandelman.ca (Postfix) with ESMTPS id BE05634011; Mon, 14 Nov 2011 21:25:04 -0500 (EST)
Received: by marajade.sandelman.ca (Postfix, from userid 179) id 32DB698CB3; Mon, 14 Nov 2011 21:26:30 -0500 (EST)
Received: from marajade.sandelman.ca (localhost [127.0.0.1]) by marajade.sandelman.ca (Postfix) with ESMTP id 2D0DA98CB2; Mon, 14 Nov 2011 21:26:30 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ca>
To: homenet@ietf.org
X-Mailer: MH-E 8.1; nmh 1.3-dev; XEmacs 21.4 (patch 22)
Date: Mon, 14 Nov 2011 21:26:30 -0500
Message-ID: <19345.1321323990@marajade.sandelman.ca>
Sender: mcr@sandelman.ca
Subject: [homenet] privacy vs subnet-id
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 02:26:31 -0000

Brian Carpenter raised the point at the mic that we have to pay
attention to privacy when it comes to the subnet-id.  We shouldn't make
it possible for members of the household to spy on each other.

My understanding of the purpose of RFC4941 privacy extensions is to make
is hard for an (off-path) observer (including web server operator) to
trivially track a user from location to location by their EUI-64. 

The question is, do we have any similar requirements that we want to
apply to subnet-id.  The example that Brian gave in XMPP was:

BEC> And if you have a separate subnet for the kids' bedroom...
BEC> 'Honey, one of the kids is using Facebook again'

if there is only one possible host on a particular subnet, then RFC4941
can't help disguise who is doing what.  

My question is: what is the real issue here.  It seems that the kind of
things that 4941 deals with, are neither better nor worse.  But maybe
there are other things that we need to concern ourselves with.

-- 
]       He who is tired of Weird Al is tired of life!           |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
   Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE>
	               then sign the petition. 


From touch@isi.edu  Mon Nov 14 18:31:34 2011
Return-Path: <touch@isi.edu>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31E6A11E836A for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 18:31:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.299
X-Spam-Level: 
X-Spam-Status: No, score=-102.299 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RRuH-oeDLGO9 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 18:31:33 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id A6A8411E8360 for <homenet@ietf.org>; Mon, 14 Nov 2011 18:31:27 -0800 (PST)
Received: from [130.129.66.136] (dhcp-4288.meeting.ietf.org [130.129.66.136]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id pAF2UrVB028462 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 14 Nov 2011 18:31:04 -0800 (PST)
Message-ID: <4EC1CEDC.20702@isi.edu>
Date: Mon, 14 Nov 2011 18:30:52 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Michael Richardson <mcr@sandelman.ca>
References: <13919.1321321547@marajade.sandelman.ca>
In-Reply-To: <13919.1321321547@marajade.sandelman.ca>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: homenet <homenet@ietf.org>
Subject: Re: [homenet] secret sharing among devices
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 02:31:34 -0000

On 11/14/2011 5:45 PM, Michael Richardson wrote:
>
> There have been various discussion in PHL about spreading a secret among
> devices so they can authenticate each other.
>
> A super cool idea is a specifically formatted file on a USB drive,
> inserted into each system in turn.  While we might be pretty sure
> the USB drive (and file system and connector, etc.) is out of scope, the
> format for that secret file might be well in scope

Doesn't that assume the device has a USB connector and can mount a stick 
as a drive? While that's common on PCs, it's not on home router boxes 
AFAICT. Many have no USB at all.

Joe

From brian.e.carpenter@gmail.com  Mon Nov 14 18:44:32 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B43811E8103 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 18:44:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.548
X-Spam-Level: 
X-Spam-Status: No, score=-103.548 tagged_above=-999 required=5 tests=[AWL=0.051, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7qg2ltol1YQG for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 18:44:31 -0800 (PST)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id B7B1411E8087 for <homenet@ietf.org>; Mon, 14 Nov 2011 18:44:31 -0800 (PST)
Received: by vcbfk1 with SMTP id fk1so6779870vcb.31 for <homenet@ietf.org>; Mon, 14 Nov 2011 18:44:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=HUfo9aWRxz43qBh5Gr3qhcrhIOsc54/DQ4K0HdK/DVE=; b=Ppiq2rXBgXCturs1cftXV6FuIPpZcTfeDP0Iozw/hgp6cLIZ5wAAjHbj+oNBIZMgrZ Z3OMbS8mUT37rDMinJItglJJm+t4rXDxM3pwV619fd5IRiEbMDhwv4JQa2kuJXPPLQ3W WlXMbzXLbD99YJIWeZyw06JVn92a2ZkpodnzU=
Received: by 10.224.212.10 with SMTP id gq10mr15841629qab.75.1321325068667; Mon, 14 Nov 2011 18:44:28 -0800 (PST)
Received: from [130.129.19.92] (dhcp-135c.meeting.ietf.org. [130.129.19.92]) by mx.google.com with ESMTPS id ha3sm23313069qab.2.2011.11.14.18.44.26 (version=SSLv3 cipher=OTHER); Mon, 14 Nov 2011 18:44:28 -0800 (PST)
Message-ID: <4EC1D206.2070303@gmail.com>
Date: Tue, 15 Nov 2011 15:44:22 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Fred Baker <fred@cisco.com>,  homenet@ietf.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: [homenet] draft-baker-homenet-prefix-assignment
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 02:44:32 -0000

Fred,

The mic line was too long to bring this up:

You suggest using RFC 3633. How about RFC 2894 (Router renumbering) too?

Typo: the draft actually cites RFC 3363, which is not what you intended...

-- 
Regards
   Brian Carpenter



From mellon@fugue.com  Mon Nov 14 18:44:51 2011
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66D8411E8135 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 18:44:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.525
X-Spam-Level: 
X-Spam-Status: No, score=-1.525 tagged_above=-999 required=5 tests=[AWL=-0.322, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vhz4U21InMA2 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 18:44:49 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id A383811E8087 for <homenet@ietf.org>; Mon, 14 Nov 2011 18:44:49 -0800 (PST)
Received: from [IPv6:2001:df8::80:9458:4948:63d6:ca83] (unknown [IPv6:2001:df8:0:80:9458:4948:63d6:ca83]) by toccata.fugue.com (Postfix) with ESMTPSA id 832B2238004A; Mon, 14 Nov 2011 21:44:48 -0500 (EST)
References: <13919.1321321547@marajade.sandelman.ca> <4EC1CEDC.20702@isi.edu>
In-Reply-To: <4EC1CEDC.20702@isi.edu>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <A38099B4-7759-4DD3-92D1-5C6729B445DA@fugue.com>
X-Mailer: iPad Mail (9A334)
From: Ted Lemon <mellon@fugue.com>
Date: Tue, 15 Nov 2011 10:45:15 +0800
To: Joe Touch <touch@isi.edu>
Cc: homenet <homenet@ietf.org>, Michael Richardson <mcr@sandelman.ca>
Subject: Re: [homenet] secret sharing among devices
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 02:44:51 -0000

On Nov 15, 2011, at 10:30 AM, Joe Touch <touch@isi.edu> wrote:
> Doesn't that assume the device has a USB connector and can mount a stick a=
s a drive? While that's common on PCs, it's not on home router boxes AFAICT.=
 Many have no USB at all.

That's why mcr suggested that we not talk about what kind of device is used t=
o share the file.   Actually, though, a lot of routers do have USB ports.   T=
hey also have ethernet ports, which is another way to peer hardware together=
.=

From lorenzo@google.com  Mon Nov 14 18:46:43 2011
Return-Path: <lorenzo@google.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3E411F0D41 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 18:46:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.868
X-Spam-Level: 
X-Spam-Status: No, score=-102.868 tagged_above=-999 required=5 tests=[AWL=0.108, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w+Q5ltEkq9Yi for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 18:46:43 -0800 (PST)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id D7E421F0C69 for <homenet@ietf.org>; Mon, 14 Nov 2011 18:46:42 -0800 (PST)
Received: by ggnr5 with SMTP id r5so1855385ggn.31 for <homenet@ietf.org>; Mon, 14 Nov 2011 18:46:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-system-of-record; bh=VlkohGwjlvJZiR+N0wMJ8oU71HD5Ydb4G1vgeas0OB4=; b=SIpkXMB2Yqin+HAEXB+qp+Q/Oa0WzSPLYm3R63jaqeci3iLfyqIBWmTuQr5Dv4dSN6 pHAXOsFA5HsekrhjB9kg==
Received: by 10.101.42.17 with SMTP id u17mr7487522anj.7.1321325202407; Mon, 14 Nov 2011 18:46:42 -0800 (PST)
Received: by 10.101.42.17 with SMTP id u17mr7487507anj.7.1321325202132; Mon, 14 Nov 2011 18:46:42 -0800 (PST)
MIME-Version: 1.0
Received: by 10.150.202.14 with HTTP; Mon, 14 Nov 2011 18:46:20 -0800 (PST)
In-Reply-To: <B3BE775A-4EBB-4C17-9EDC-7B9AFCB8867E@ericsson.com>
References: <CAKD1Yr3uSsNP4avZBdQE7YxFd7D_KOXBOCsfaRfvnWhJoLoY9Q@mail.gmail.com> <B3BE775A-4EBB-4C17-9EDC-7B9AFCB8867E@ericsson.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Tue, 15 Nov 2011 10:46:20 +0800
Message-ID: <CAKD1Yr0MFdyBopr0E0WiebLSZ+M2J9vAi1U6b66VxhziE2XJpw@mail.gmail.com>
To: Acee Lindem <acee.lindem@ericsson.com>
Content-Type: multipart/alternative; boundary=001636ed71a44e4e4504b1bcfff6
X-System-Of-Record: true
Cc: "homenet@ietf.org" <homenet@ietf.org>, Jari Arkko <jari.arkko@piuha.net>
Subject: Re: [homenet] Comments on draft-acee-ospf-ospfv3-autoconfig-00
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 02:46:43 -0000

--001636ed71a44e4e4504b1bcfff6
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Nov 15, 2011 at 10:25, Acee Lindem <acee.lindem@ericsson.com> wrote:

> > 1. I think the OSPFv3 router ID should not be based on the MAC address
> because that will encourage people to assume it's unique "most of the
> time". I think we should just make it a pseudo-random number so it's clear
> that uniqueness is only guaranteed by collision detection and that
> collision detection needs to be robust.
>
> The draft requires duplicate Router-ID detection and resolution. I don't
> think that the fact that a portion of the MAC address is used as a first
> try is reason for this detection/resolution not to be implemented or tested.
>

In my experience, giving people something that works "most of the time"
will cause the cases where it doesn't work to break. I think it's better to
explicitly provide no guarantees of uniqueness to make it clear that
collision detection needs to be robust. Also, if we rely on collision
detection, then what's the advantage of using the MAC address? We might as
well as make it random all the time - that probably has a lower chance of
collision anyway.

I think you mean virtual links. They are definitely not needed in the
> auto-configured environment as they are for providing a backbone path
> through a transit area and the OSPFv3 auto-configured routing domain
> assumes only a backbone area.
>

Yes, virtual links. Do we need to state explicitly that they cannot exist
and are not supported?


> > 3. Can we use normal LSAs to detect collisions? One idea would be "if
> you see your own router ID in the list of neighbours of a network LSA or
> router LSA, then there is a collision". Will that work? If so we wouldn't
> need the hardware fingerprint at all.
>
> No. In an arbitrary topology, A router with a duplicate router-id can be
> multiple hops away.
>

Yes, but router and network LSAs are flooded, so you'll hear them
regardless of whether your duplicate is multiple hops away, no?


> If the pre-shared key is hard-coded, it is no better than the OSPFv3
> Interface Instance ID that is specified to prevent inadvertent adjacencies
> with routers not supporting the auto-configuration. If configuration of a
> pre-shared key is required, you no longer have auto-configuration.
>

Sorry, that wasn't clear. What I meant to say is that we should pick one
scheme (e.g., HMAC-SHA) and stick to it; we shouldn't support multiple
schemes as that will lead to interoperability issues for devices that use
one scheme and devices that use another scheme.

--001636ed71a44e4e4504b1bcfff6
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div class=3D"gmail_quote">On Tue, Nov 15, 2011 at 10:25, Acee Lindem <span=
 dir=3D"ltr">&lt;<a href=3D"mailto:acee.lindem@ericsson.com">acee.lindem@er=
icsson.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">

<div class=3D"im">&gt; 1. I think the OSPFv3 router ID should not be based =
on the MAC address because that will encourage people to assume it&#39;s un=
ique &quot;most of the time&quot;. I think we should just make it a pseudo-=
random number so it&#39;s clear that uniqueness is only guaranteed by colli=
sion detection and that collision detection needs to be robust.<br>


<br>
</div>The draft requires duplicate Router-ID detection and resolution. I do=
n&#39;t think that the fact that a portion of the MAC address is used as a =
first try is reason for this detection/resolution not to be implemented or =
tested.<br>

</blockquote><div><br>In my experience, giving people something that works =
&quot;most of the time&quot; will cause the cases where it doesn&#39;t work=
 to break.=A0<span style=3D"background-color: transparent; ">I think it&#39=
;s better to explicitly provide no guarantees of uniqueness to make it clea=
r that collision detection needs to be robust. Also, i</span><span style=3D=
"background-color: transparent; ">f we rely on collision detection, then wh=
at&#39;s the advantage of using the MAC address? We might as well as make i=
t random all the time - that probably has a lower chance of collision anywa=
y.</span></div>

<div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex;">
<div class=3D"im"><span style=3D"background-color: transparent; ">I think y=
ou mean virtual links. They are definitely not needed in the auto-configure=
d environment as they are for providing a backbone path through a transit a=
rea and the OSPFv3 auto-configured routing domain assumes only a backbone a=
rea.</span></div>

</blockquote><div><br></div><div>Yes, virtual links. Do we need to state ex=
plicitly that they cannot exist and are not supported?</div><div>=A0</div><=
blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px=
 #ccc solid;padding-left:1ex;">


<div class=3D"im">&gt; 3. Can we use normal LSAs to detect collisions? One =
idea would be &quot;if you see your own router ID in the list of neighbours=
 of a network LSA or router LSA, then there is a collision&quot;. Will that=
 work? If so we wouldn&#39;t need the hardware fingerprint at all.<br>


<br>
</div>No. In an arbitrary topology, A router with a duplicate router-id can=
 be multiple hops away.<br></blockquote><div><br></div><div>Yes, but router=
 and network LSAs are flooded, so you&#39;ll hear them regardless of whethe=
r your duplicate is multiple hops away, no?</div>

<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex;">
<div class=3D"im"><span style=3D"background-color: transparent; ">If the pr=
e-shared key is hard-coded, it is no better than the OSPFv3 Interface Insta=
nce ID that is specified to prevent inadvertent adjacencies with routers no=
t supporting the auto-configuration. If configuration of a pre-shared key i=
s required, you no longer have auto-configuration.</span></div>

</blockquote><div><br></div><div>Sorry, that wasn&#39;t clear. What I meant=
 to say is that we should pick one scheme (e.g., HMAC-SHA) and stick to it;=
 we shouldn&#39;t support multiple schemes as that will lead to interoperab=
ility issues for devices that use one scheme and devices that use another s=
cheme.</div>

</div>

--001636ed71a44e4e4504b1bcfff6--

From rstruik.ext@gmail.com  Mon Nov 14 18:47:43 2011
Return-Path: <rstruik.ext@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69CF611E814B for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 18:47:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.524
X-Spam-Level: 
X-Spam-Status: No, score=-3.524 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JCUtPXtU0GSy for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 18:47:43 -0800 (PST)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id D2B6F11E813E for <homenet@ietf.org>; Mon, 14 Nov 2011 18:47:42 -0800 (PST)
Received: by ggnr5 with SMTP id r5so1856272ggn.31 for <homenet@ietf.org>; Mon, 14 Nov 2011 18:47:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=vNtw+VBjuESohzcS+CNwodtgqXcwS/6lQO+j0Pj+sYY=; b=hJSapSAk0L/LONjUAf5YUwriVF/4EzNGrxqlg0KGNJMP0haQWeR6Ee2AZV+C8P6l7o 2EjaZ7qOenxtrAj1QvviMd4iu3vGJx3BfC4CNyPqFVMZZ9ql/Y4fx2yfNCgVUU8FuKxW lMCnK74l+FZDSWqSWJ/k9MyHnqmx5Yn7wlfhs=
Received: by 10.100.235.40 with SMTP id i40mr7081436anh.39.1321325262446; Mon, 14 Nov 2011 18:47:42 -0800 (PST)
Received: from [192.168.1.103] (CPE0013100e2c51-CM001cea35caa6.cpe.net.cable.rogers.com. [99.231.117.243]) by mx.google.com with ESMTPS id l27sm67646590ani.21.2011.11.14.18.47.41 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 14 Nov 2011 18:47:41 -0800 (PST)
Message-ID: <4EC1D2C6.3020502@gmail.com>
Date: Mon, 14 Nov 2011 21:47:34 -0500
From: Rene Struik <rstruik.ext@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.0; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Ted Lemon <mellon@fugue.com>
References: <13919.1321321547@marajade.sandelman.ca> <4EC1CEDC.20702@isi.edu> <A38099B4-7759-4DD3-92D1-5C6729B445DA@fugue.com>
In-Reply-To: <A38099B4-7759-4DD3-92D1-5C6729B445DA@fugue.com>
X-Enigmail-Version: 1.3.3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: homenet <homenet@ietf.org>, Michael Richardson <mcr@sandelman.ca>, Joe Touch <touch@isi.edu>
Subject: Re: [homenet] secret sharing among devices
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 02:47:43 -0000

Dear colleagues:

Could you elaborate about the security services and deployment
scenario(s) you wish to facilitate, for the benefit of those not at
IETF-82 who subscribe to the mailing list? In other words, what is the
problem one tries and solve here?

Best regards, Rene

On 14/11/2011 9:45 PM, Ted Lemon wrote:
> On Nov 15, 2011, at 10:30 AM, Joe Touch <touch@isi.edu> wrote:
>> Doesn't that assume the device has a USB connector and can mount a stick as a drive? While that's common on PCs, it's not on home router boxes AFAICT. Many have no USB at all.
> That's why mcr suggested that we not talk about what kind of device is used to share the file.   Actually, though, a lot of routers do have USB ports.   They also have ethernet ports, which is another way to peer hardware together.
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet


-- 
email: rstruik.ext@gmail.com
Skype: rstruik
cell: +1 (647) 867-5658
USA Google voice: +1 (415) 690-7363


From rdroms.ietf@gmail.com  Mon Nov 14 18:49:26 2011
Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B72211F0C69 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 18:49:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.266
X-Spam-Level: 
X-Spam-Status: No, score=-103.266 tagged_above=-999 required=5 tests=[AWL=0.333, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PLJPQMts4zNA for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 18:49:26 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 2D3381F0D4D for <homenet@ietf.org>; Mon, 14 Nov 2011 18:49:26 -0800 (PST)
Received: by ywt34 with SMTP id 34so5622455ywt.31 for <homenet@ietf.org>; Mon, 14 Nov 2011 18:49:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=LldZtwc4gimcESL5+Oj0jZPHFHW7a//BfwFR4i+zi5g=; b=rZ///HK1RHinwp3XwuLCK4gjb/AvK5ls6m2dOC63brtl/zG0yaXUYcbzLO6yNPuxla 7v4pGJE797bYHMYV4ThM1xp9iDYQb/W8bt5vmyMYa5YTyV9xJKewkvjC4MLsXYSiJ8RD cfDdm0JjKinRreTWWBZ9l/EYAQ1dNuohSWIMc=
Received: by 10.68.28.4 with SMTP id x4mr55297238pbg.56.1321325365424; Mon, 14 Nov 2011 18:49:25 -0800 (PST)
Received: from sjc-vpn3-1368.cisco.com (128-107-239-233.cisco.com. [128.107.239.233]) by mx.google.com with ESMTPS id jm5sm61328621pbc.1.2011.11.14.18.49.22 (version=SSLv3 cipher=OTHER); Mon, 14 Nov 2011 18:49:24 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <4EC1D206.2070303@gmail.com>
Date: Tue, 15 Nov 2011 10:49:19 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <BEF40C0A-E2C1-44F3-8C06-95817CD655BB@gmail.com>
References: <4EC1D206.2070303@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: homenet@ietf.org, Ralph Droms <rdroms.ietf@gmail.com>, Fred Baker <fred@cisco.com>
Subject: Re: [homenet] draft-baker-homenet-prefix-assignment
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 02:49:26 -0000

On Nov 15, 2011, at 10:44 AM 11/15/11, Brian E Carpenter wrote:

> Fred,
>=20
> The mic line was too long to bring this up:
>=20
> You suggest using RFC 3633. How about RFC 2894 (Router renumbering) =
too?

What device controls the use of RFC 2894?  RFC 3633 triggers assignment =
from the routers that actually need the prefixes.

>=20
> Typo: the draft actually cites RFC 3363, which is not what you =
intended...

Oops.

- Ralph

>=20
> --=20
> Regards
>   Brian Carpenter
>=20
>=20
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet


From mellon@fugue.com  Mon Nov 14 18:51:48 2011
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2FCB21F0D4D for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 18:51:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.496
X-Spam-Level: 
X-Spam-Status: No, score=-1.496 tagged_above=-999 required=5 tests=[AWL=-0.293, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FrwHdit2cTRE for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 18:51:47 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id AD1F81F0D53 for <homenet@ietf.org>; Mon, 14 Nov 2011 18:51:47 -0800 (PST)
Received: from [IPv6:2001:df8::80:9458:4948:63d6:ca83] (unknown [IPv6:2001:df8:0:80:9458:4948:63d6:ca83]) by toccata.fugue.com (Postfix) with ESMTPSA id 4287F238086C; Mon, 14 Nov 2011 21:51:46 -0500 (EST)
References: <4EC1D206.2070303@gmail.com>
In-Reply-To: <4EC1D206.2070303@gmail.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=utf-8
Message-Id: <3C716203-8579-41EA-98CE-6DC3BE9261D8@fugue.com>
X-Mailer: iPad Mail (9A334)
From: Ted Lemon <mellon@fugue.com>
Date: Tue, 15 Nov 2011 10:52:13 +0800
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: "homenet@ietf.org" <homenet@ietf.org>, Fred Baker <fred@cisco.com>
Subject: Re: [homenet] draft-baker-homenet-prefix-assignment
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 02:51:48 -0000

On Nov 15, 2011, at 10:44 AM, Brian E Carpenter <brian.e.carpenter@gmail.com=
> wrote:
> The mic line was too long to bring this up:
> You suggest using RFC 3633. How about RFC 2894 (Router renumbering) too?
> Typo: the draft actually cites RFC 3363, which is not what you intended...=


Ditto on the mic line=E2=80=94very frustrating.   I think you overestimate t=
he obstacles to using DHCPv6 PD for this application.   I don't think any pr=
otocol extension is required.   What is needed is ad-hoc relay configuration=
, which is already anticipated.   The CPE device can just allocate a /64 for=
 any PD it receives, and with ad-hoc relaying, it should all Just Work.

The way ad hoc relaying works is that when you come up, your PD client asks f=
or a prefix on its upstream port.   If it receives PDs, it relays them on it=
s upstream port.   These PDs all wind up at the CPE device, which allocates /=
64s to them and forwards them back, all in accordance with the existing DHCP=
 relay mechanism.

I think homenet would have to do a draft describing how to set this up, but i=
t does not require a DHCP extension.   There'd be some details to document o=
n how the routing topology gets set up; perhaps that could be done with OSPF.=



From brian.e.carpenter@gmail.com  Mon Nov 14 18:53:49 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C1AC1F0D3D for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 18:53:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.553
X-Spam-Level: 
X-Spam-Status: No, score=-103.553 tagged_above=-999 required=5 tests=[AWL=0.046, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5Lo4viDUUVy9 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 18:53:43 -0800 (PST)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 8A2001F0C90 for <homenet@ietf.org>; Mon, 14 Nov 2011 18:53:38 -0800 (PST)
Received: by vws5 with SMTP id 5so6899469vws.31 for <homenet@ietf.org>; Mon, 14 Nov 2011 18:53:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=m05hSWBoOGvpJsDuR0kKZPKZTfOyh08WqwlBndPlb5c=; b=xshxwlQaw6T52q15mtKmTbgBduvXWHPIAH32WsM2t3AykT6CQ9B5mIkrwZ9krR8285 7fQD8Pz7m8sD7Pga3nnx3T2RM+LQ5Vbgb7VnE6914Gs8zhKKDn31MfgLzolPDH1LO7Vz I40VR+AT3F5eAzXpBpK2HAHToNRpiHFUBrtzU=
Received: by 10.52.33.140 with SMTP id r12mr39829093vdi.36.1321325617989; Mon, 14 Nov 2011 18:53:37 -0800 (PST)
Received: from [130.129.19.92] (dhcp-135c.meeting.ietf.org. [130.129.19.92]) by mx.google.com with ESMTPS id r5sm34586512vdj.11.2011.11.14.18.53.35 (version=SSLv3 cipher=OTHER); Mon, 14 Nov 2011 18:53:37 -0800 (PST)
Message-ID: <4EC1D42B.7070105@gmail.com>
Date: Tue, 15 Nov 2011 15:53:31 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Michael Richardson <mcr@sandelman.ca>
References: <19345.1321323990@marajade.sandelman.ca>
In-Reply-To: <19345.1321323990@marajade.sandelman.ca>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: homenet@ietf.org
Subject: Re: [homenet] privacy vs subnet-id
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 02:53:49 -0000

On 2011-11-15 15:26, Michael Richardson wrote:
> Brian Carpenter raised the point at the mic that we have to pay
> attention to privacy when it comes to the subnet-id.  We shouldn't make
> it possible for members of the household to spy on each other.
> 
> My understanding of the purpose of RFC4941 privacy extensions is to make
> is hard for an (off-path) observer (including web server operator) to
> trivially track a user from location to location by their EUI-64. 
> 
> The question is, do we have any similar requirements that we want to
> apply to subnet-id.  The example that Brian gave in XMPP was:
> 
> BEC> And if you have a separate subnet for the kids' bedroom...
> BEC> 'Honey, one of the kids is using Facebook again'
> 
> if there is only one possible host on a particular subnet, then RFC4941
> can't help disguise who is doing what.  
> 
> My question is: what is the real issue here.  It seems that the kind of
> things that 4941 deals with, are neither better nor worse.  But maybe
> there are other things that we need to concern ourselves with.

Waxing philosophical, you can obfuscate an ID but you can't obfuscate
a locator. I really don't see a way out of this. If the admin can
run Wireshark, she can see the locator.

    Brian

From touch@isi.edu  Mon Nov 14 18:54:05 2011
Return-Path: <touch@isi.edu>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6F1311E8176 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 18:54:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.359
X-Spam-Level: 
X-Spam-Status: No, score=-102.359 tagged_above=-999 required=5 tests=[AWL=0.240, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pfbnpf7uBqjL for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 18:54:05 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id 7C07F11E8173 for <homenet@ietf.org>; Mon, 14 Nov 2011 18:54:05 -0800 (PST)
Received: from [130.129.66.136] (dhcp-4288.meeting.ietf.org [130.129.66.136]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id pAF2r75q001124 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 14 Nov 2011 18:53:18 -0800 (PST)
Message-ID: <4EC1D413.2080803@isi.edu>
Date: Mon, 14 Nov 2011 18:53:07 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Ted Lemon <mellon@fugue.com>
References: <13919.1321321547@marajade.sandelman.ca> <4EC1CEDC.20702@isi.edu> <A38099B4-7759-4DD3-92D1-5C6729B445DA@fugue.com>
In-Reply-To: <A38099B4-7759-4DD3-92D1-5C6729B445DA@fugue.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: homenet <homenet@ietf.org>, Michael Richardson <mcr@sandelman.ca>
Subject: Re: [homenet] secret sharing among devices
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 02:54:06 -0000

On 11/14/2011 6:45 PM, Ted Lemon wrote:
> On Nov 15, 2011, at 10:30 AM, Joe Touch<touch@isi.edu>  wrote:
>> Doesn't that assume the device has a USB connector and can mount a stick as a drive? While that's common on PCs, it's not on home router boxes AFAICT. Many have no USB at all.
>
> That's why mcr suggested that we not talk about what kind of device is used to share the file.   Actually, though, a lot of routers do have USB ports.   They also have ethernet ports, which is another way to peer hardware together.

IMO, then explain the format of the key as an ASCII string. The file can 
then be described as the bare key.

Joe

From mellon@fugue.com  Mon Nov 14 18:55:11 2011
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0561C11E8316 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 18:55:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.471
X-Spam-Level: 
X-Spam-Status: No, score=-1.471 tagged_above=-999 required=5 tests=[AWL=-0.268, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rGMIaLjwvF-k for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 18:55:10 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id EF57511E830D for <homenet@ietf.org>; Mon, 14 Nov 2011 18:55:07 -0800 (PST)
Received: from [IPv6:2001:df8::80:9458:4948:63d6:ca83] (unknown [IPv6:2001:df8:0:80:9458:4948:63d6:ca83]) by toccata.fugue.com (Postfix) with ESMTPSA id B87342380950; Mon, 14 Nov 2011 21:55:05 -0500 (EST)
References: <13919.1321321547@marajade.sandelman.ca> <4EC1CEDC.20702@isi.edu> <A38099B4-7759-4DD3-92D1-5C6729B445DA@fugue.com> <4EC1D2C6.3020502@gmail.com>
In-Reply-To: <4EC1D2C6.3020502@gmail.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <6B3A3374-AC8B-49F1-BEBE-46CA3E795874@fugue.com>
X-Mailer: iPad Mail (9A334)
From: Ted Lemon <mellon@fugue.com>
Date: Tue, 15 Nov 2011 10:55:32 +0800
To: Rene Struik <rstruik.ext@gmail.com>
Cc: homenet <homenet@ietf.org>, Michael Richardson <mcr@sandelman.ca>, Joe Touch <touch@isi.edu>
Subject: Re: [homenet] secret sharing among devices
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 02:55:11 -0000

On Nov 15, 2011, at 10:47 AM, Rene Struik <rstruik.ext@gmail.com> wrote:
> Could you elaborate about the security services and deployment
> scenario(s) you wish to facilitate, for the benefit of those not at
> IETF-82 who subscribe to the mailing list? In other words, what is the
> problem one tries and solve here?

We do not want, for example, for devices that aren't supposed to be routers t=
o be routers.   By doing a manual key exchange, we can ensure that only devi=
ces that are intended to be part of the network topology have the keys that a=
re required to join the routing infrastructure.


From rdroms.ietf@gmail.com  Mon Nov 14 18:56:01 2011
Return-Path: <rdroms.ietf@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5646B1F0D5E for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 18:56:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.313
X-Spam-Level: 
X-Spam-Status: No, score=-103.313 tagged_above=-999 required=5 tests=[AWL=0.286, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EtsB9CHeNOO3 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 18:56:00 -0800 (PST)
Received: from mail-pz0-f50.google.com (mail-pz0-f50.google.com [209.85.210.50]) by ietfa.amsl.com (Postfix) with ESMTP id BFD1D1F0D3D for <homenet@ietf.org>; Mon, 14 Nov 2011 18:56:00 -0800 (PST)
Received: by pzk5 with SMTP id 5so11508215pzk.9 for <homenet@ietf.org>; Mon, 14 Nov 2011 18:55:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=YV4iiyxVVRebKoyoRJZHajnpgkd9cqZeGdiadz3S4Mg=; b=oW6gCD5bZSUOnygLeSL3dIm0J8o4ZIySDq0Z0pLDyYHCHehK/+sQC7iorpWskLwXJb +DsllezIRmjtKm0SzQ2g3RO1rcZlgjM+qzFGxkoKfo1Ri6JoIS2r2ybST9VyTWX/6Wsl BwOOewKfB7gTDOOCEyL5MgYjRv6dOtIBimiXE=
Received: by 10.68.72.170 with SMTP id e10mr54638510pbv.6.1321325759255; Mon, 14 Nov 2011 18:55:59 -0800 (PST)
Received: from sjc-vpn3-1368.cisco.com (128-107-239-233.cisco.com. [128.107.239.233]) by mx.google.com with ESMTPS id 4sm61299650pbj.18.2011.11.14.18.55.55 (version=SSLv3 cipher=OTHER); Mon, 14 Nov 2011 18:55:58 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=windows-1252
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <3C716203-8579-41EA-98CE-6DC3BE9261D8@fugue.com>
Date: Tue, 15 Nov 2011 10:55:53 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <3DDB460D-2552-42F2-9BDE-1993E44982A3@gmail.com>
References: <4EC1D206.2070303@gmail.com> <3C716203-8579-41EA-98CE-6DC3BE9261D8@fugue.com>
To: Ted Lemon <mellon@fugue.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: "homenet@ietf.org" <homenet@ietf.org>, Fred Baker <fred@cisco.com>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [homenet] draft-baker-homenet-prefix-assignment
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 02:56:01 -0000

On Nov 15, 2011, at 10:52 AM 11/15/11, Ted Lemon wrote:

> On Nov 15, 2011, at 10:44 AM, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:
>> The mic line was too long to bring this up:
>> You suggest using RFC 3633. How about RFC 2894 (Router renumbering) =
too?
>> Typo: the draft actually cites RFC 3363, which is not what you =
intended...
>=20
> Ditto on the mic line=97very frustrating.   I think you overestimate =
the obstacles to using DHCPv6 PD for this application.   I don't think =
any protocol extension is required.   What is needed is ad-hoc relay =
configuration, which is already anticipated.   The CPE device can just =
allocate a /64 for any PD it receives, and with ad-hoc relaying, it =
should all Just Work.

Yup.  No protocol extensions needed to DHCPv6.  Needs some careful =
thinking about how to use RAs as the trigger for deciding when a prefix =
is needed.

> The way ad hoc relaying works is that when you come up, your PD client =
asks for a prefix on its upstream port.   If it receives PDs, it relays =
them on its upstream port.   These PDs all wind up at the CPE device, =
which allocates /64s to them and forwards them back, all in accordance =
with the existing DHCP relay mechanism.
>=20
> I think homenet would have to do a draft describing how to set this =
up, but it does not require a DHCP extension.   There'd be some details =
to document on how the routing topology gets set up; perhaps that could =
be done with OSPF.

Also might need a little thinking about how to accommodate multi-homed =
networks; e.g., allow the requesting router to take a prefix from each =
of the delegating routers it hears from (as opposed to the address =
assignment strategy of choosing one DHCP server to interact with).

- Ralph


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


From mellon@fugue.com  Mon Nov 14 18:56:28 2011
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CDA201F0D68 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 18:56:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.451
X-Spam-Level: 
X-Spam-Status: No, score=-1.451 tagged_above=-999 required=5 tests=[AWL=-0.248, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YhB9UPHoBfLl for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 18:56:28 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 895D31F0D61 for <homenet@ietf.org>; Mon, 14 Nov 2011 18:56:28 -0800 (PST)
Received: from [IPv6:2001:df8::80:9458:4948:63d6:ca83] (unknown [IPv6:2001:df8:0:80:9458:4948:63d6:ca83]) by toccata.fugue.com (Postfix) with ESMTPSA id 85D092380950; Mon, 14 Nov 2011 21:56:27 -0500 (EST)
References: <13919.1321321547@marajade.sandelman.ca> <4EC1CEDC.20702@isi.edu> <A38099B4-7759-4DD3-92D1-5C6729B445DA@fugue.com> <4EC1D413.2080803@isi.edu>
In-Reply-To: <4EC1D413.2080803@isi.edu>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <B3EE827A-E06D-4B1A-8E20-8BEF17F325D3@fugue.com>
X-Mailer: iPad Mail (9A334)
From: Ted Lemon <mellon@fugue.com>
Date: Tue, 15 Nov 2011 10:56:55 +0800
To: Joe Touch <touch@isi.edu>
Cc: homenet <homenet@ietf.org>, Michael Richardson <mcr@sandelman.ca>
Subject: Re: [homenet] secret sharing among devices
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 02:56:28 -0000

On Nov 15, 2011, at 10:53 AM, Joe Touch <touch@isi.edu> wrote:
> IMO, then explain the format of the key as an ASCII string. The file can t=
hen be described as the bare key.

It's not just one key.   The point of the file is to allow the various devic=
es to *exchange* keys.


From brian.e.carpenter@gmail.com  Mon Nov 14 18:57:46 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD07C1F0C91 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 18:57:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.557
X-Spam-Level: 
X-Spam-Status: No, score=-103.557 tagged_above=-999 required=5 tests=[AWL=0.042, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 46q0Khls3ZdR for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 18:57:46 -0800 (PST)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 35A531F0C8F for <homenet@ietf.org>; Mon, 14 Nov 2011 18:57:46 -0800 (PST)
Received: by vcbfk1 with SMTP id fk1so6791569vcb.31 for <homenet@ietf.org>; Mon, 14 Nov 2011 18:57:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=AF8jpl8EtQ4/nO0CfaAXuo37tdgeczPZa0owyaRha8s=; b=SY9I5RQhE1SxGPlIPJIxZbagkwOFJiPqsGme0aKJ5r9XVHCgwcDwCNvTVY3w0jwaB9 LKPSt84bNFom2Y/aJVXq1bYAw+hXC/5bcTFrLUEjUlUkDZtAo2meLQp3nqWmeAJpb3xJ Sg6cA7ZZkF7HcOkzxp2CA5/dqP8oRe0fAXa5g=
Received: by 10.52.38.6 with SMTP id c6mr40658987vdk.73.1321325865617; Mon, 14 Nov 2011 18:57:45 -0800 (PST)
Received: from [130.129.19.92] (dhcp-135c.meeting.ietf.org. [130.129.19.92]) by mx.google.com with ESMTPS id bu10sm34630006vdb.3.2011.11.14.18.57.43 (version=SSLv3 cipher=OTHER); Mon, 14 Nov 2011 18:57:44 -0800 (PST)
Message-ID: <4EC1D522.4060305@gmail.com>
Date: Tue, 15 Nov 2011 15:57:38 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Ralph Droms <rdroms.ietf@gmail.com>
References: <4EC1D206.2070303@gmail.com> <BEF40C0A-E2C1-44F3-8C06-95817CD655BB@gmail.com>
In-Reply-To: <BEF40C0A-E2C1-44F3-8C06-95817CD655BB@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: homenet@ietf.org, Fred Baker <fred@cisco.com>
Subject: Re: [homenet] draft-baker-homenet-prefix-assignment
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 02:57:46 -0000

On 2011-11-15 15:49, Ralph Droms wrote:
> On Nov 15, 2011, at 10:44 AM 11/15/11, Brian E Carpenter wrote:
> 
>> Fred,
>>
>> The mic line was too long to bring this up:
>>
>> You suggest using RFC 3633. How about RFC 2894 (Router renumbering) too?
> 
> What device controls the use of RFC 2894?  RFC 3633 triggers assignment from the routers that actually need the prefixes.

I would assume it has to be the CE router. But I have no problem if you say that
RFC 2894 is unnecessary; it was an unused solution that we identified in RFC 5887,
so it's in my mental list of loose ends.

   Brian

>> Typo: the draft actually cites RFC 3363, which is not what you intended...
> 
> Oops.
> 
> - Ralph
> 
>> -- 
>> Regards
>>   Brian Carpenter
>>
>>
>> _______________________________________________
>> homenet mailing list
>> homenet@ietf.org
>> https://www.ietf.org/mailman/listinfo/homenet
> 
> 

From fred@cisco.com  Mon Nov 14 18:59:57 2011
Return-Path: <fred@cisco.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63E6C1F0D71 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 18:59:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.776
X-Spam-Level: 
X-Spam-Status: No, score=-109.776 tagged_above=-999 required=5 tests=[AWL=0.823, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3g2bjMWWB0iD for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 18:59:56 -0800 (PST)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id 83FBF1F0D76 for <homenet@ietf.org>; Mon, 14 Nov 2011 18:59:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=527; q=dns/txt; s=iport; t=1321325996; x=1322535596; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to:content-transfer-encoding; bh=Mp7qEft66nrWrfJI+acEO6Pk/B8aXotFGQDe66WbqKU=; b=LnutckOwTv9OtncX085U7jHhB+RoA9dSRLuDDczZ2rKfp1nQCQRMGnpA wih0Rfcbsmh9Yallk0LE/ADjfeGLllIIv7v/eZYnuMlt37srxLhWq32uX LqP5ylhp/Tc1EiQr20lyRNAlqE8bx+WEhJ8YGnNrvHAArnKeRakdxmu58 o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EALbUwU5Io8US/2dsb2JhbABDqWmBBYFyAQEBAwESASc/BQsLRlcGNYdgnA4BnwGJHGMEiA6MIIU7jEs
X-IronPort-AV: E=Sophos;i="4.69,512,1315180800"; d="scan'208";a="121600665"
Received: from bgl-core-3.cisco.com ([72.163.197.18]) by ams-iport-1.cisco.com with ESMTP; 15 Nov 2011 02:59:54 +0000
Received: from dhcp-57cd.meeting.ietf.org (hkidc-vpn-client-235-225.cisco.com [10.75.235.225]) by bgl-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id pAF2xqGA018351; Tue, 15 Nov 2011 02:59:53 GMT
Received: from [127.0.0.1] by dhcp-57cd.meeting.ietf.org (PGP Universal service); Tue, 15 Nov 2011 10:59:53 +0800
X-PGP-Universal: processed; by dhcp-57cd.meeting.ietf.org on Tue, 15 Nov 2011 10:59:53 +0800
Mime-Version: 1.0 (Apple Message framework v1084)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <4EC1D206.2070303@gmail.com>
Date: Tue, 15 Nov 2011 10:59:43 +0800
Message-Id: <04630CC0-C2DF-467D-BF60-DC2CE72B9F70@cisco.com>
References: <4EC1D206.2070303@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1084)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: homenet@ietf.org
Subject: Re: [homenet] draft-baker-homenet-prefix-assignment
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 02:59:57 -0000

On Nov 15, 2011, at 10:44 AM, Brian E Carpenter wrote:

> Fred,
>=20
> The mic line was too long to bring this up:
>=20
> You suggest using RFC 3633. How about RFC 2894 (Router renumbering) =
too?

It makes some "interesting" assumptions; I can point to one router =
vendor that has chosen to not implement it until some of the underlying =
assumptions get fixed.

> Typo: the draft actually cites RFC 3363, which is not what you =
intended...

oops...

> --=20
> Regards
>   Brian Carpenter
>=20
>=20


From mellon@fugue.com  Mon Nov 14 19:00:05 2011
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4EEC1F0D7E for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 19:00:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.433
X-Spam-Level: 
X-Spam-Status: No, score=-1.433 tagged_above=-999 required=5 tests=[AWL=-0.230, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R-OWJqQodPLF for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 19:00:05 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 722211F0D7D for <homenet@ietf.org>; Mon, 14 Nov 2011 19:00:05 -0800 (PST)
Received: from [IPv6:2001:df8::80:9458:4948:63d6:ca83] (unknown [IPv6:2001:df8:0:80:9458:4948:63d6:ca83]) by toccata.fugue.com (Postfix) with ESMTPSA id 9340B2380950; Mon, 14 Nov 2011 22:00:04 -0500 (EST)
References: <4EC1D206.2070303@gmail.com> <3C716203-8579-41EA-98CE-6DC3BE9261D8@fugue.com> <3DDB460D-2552-42F2-9BDE-1993E44982A3@gmail.com>
In-Reply-To: <3DDB460D-2552-42F2-9BDE-1993E44982A3@gmail.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <C5010697-DBD9-4150-9AEC-8BC5859A0AAE@fugue.com>
X-Mailer: iPad Mail (9A334)
From: Ted Lemon <mellon@fugue.com>
Date: Tue, 15 Nov 2011 11:00:32 +0800
To: Ralph Droms <rdroms.ietf@gmail.com>
Cc: "homenet@ietf.org" <homenet@ietf.org>, Fred Baker <fred@cisco.com>, Ralph Droms <rdroms.ietf@gmail.com>
Subject: Re: [homenet] draft-baker-homenet-prefix-assignment
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 03:00:06 -0000

On Nov 15, 2011, at 10:55 AM, Ralph Droms <rdroms.ietf@gmail.com> wrote:
> Also might need a little thinking about how to accommodate multi-homed net=
works; e.g., allow the requesting router to take a prefix from each of the d=
elegating routers it hears from (as opposed to the address assignment strate=
gy of choosing one DHCP server to interact with).

Yup, in my experience multihoming simply doesn't work on a variety of levels=
.   One of the ways in which it doesn't work is that the DHCP protocol doesn=
't really account for it.   We kind of assume that a single DHCP server will=
 be responsible for all prefixes that are advertised on the wire.   We could=
 come up with a way for two DHCP servers to elect a responsible server, or w=
e could decide to expand DHCP to support multiple servers.   I suspect the f=
ormer solution is easier than the latter.


From nordmark@cisco.com  Mon Nov 14 19:04:38 2011
Return-Path: <nordmark@cisco.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C7DCA1F0D79 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 19:04:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PPV1xNsdaMvd for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 19:04:38 -0800 (PST)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id 1B2751F0D48 for <homenet@ietf.org>; Mon, 14 Nov 2011 19:04:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=nordmark@cisco.com; l=475; q=dns/txt; s=iport; t=1321326278; x=1322535878; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=sOFpRljxh247AdLBLady3mN/iFrT4Slog77I12RBcbc=; b=PAWcj/OCcuhFG8uVk/S0Ik5lMxnIa4XRy5iUcqQp7D4gsf6zqRpahM03 JbSFArrfm4kvlf4OJmJZF45GA4sw3rz9jdOz26WhubEWwwRXLAzeU4l4K rkqsCf2qtBVDdhk93n7FOlna+/4+akT8ZENlhPCrL7rJqpFljWogWfZUO c=;
X-IronPort-AV: E=Sophos;i="4.69,512,1315180800"; d="scan'208";a="59848065"
Received: from bgl-core-3.cisco.com ([72.163.197.18]) by ams-iport-2.cisco.com with ESMTP; 15 Nov 2011 03:04:36 +0000
Received: from [130.129.83.144] (sjc-vpn3-1317.cisco.com [10.21.69.37]) by bgl-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id pAF34WFw019180; Tue, 15 Nov 2011 03:04:34 GMT
Message-ID: <4EC1D6C9.3030107@cisco.com>
Date: Mon, 14 Nov 2011 19:04:41 -0800
From: Erik Nordmark <nordmark@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <4EC1C386.6010802@gmail.com> <4EC1C566.2060400@cisco.com> <4EC1CC2E.30209@gmail.com>
In-Reply-To: <4EC1CC2E.30209@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: homenet@ietf.org
Subject: Re: [homenet] pervasive v4
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 03:04:38 -0000

On 11/14/11 6:19 PM, Brian E Carpenter wrote:
> Yes, but then we're extending v4 and expecting homenets to run (presumably) RIP.

Why RIP? Same protocol between the home routers as we will pick for 
routing IPv6 in the home.

> That seems kind of out of scope for this WG.

I think it is an implication of 1) supporting arbitrary topologies and 
2) not breaking IPv4. Thus I don't see a different choice for an 
arbitrary topology routed home network.

    Erik



From tjc@ecs.soton.ac.uk  Mon Nov 14 19:05:03 2011
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A53141F0D93 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 19:05:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.155
X-Spam-Level: 
X-Spam-Status: No, score=-2.155 tagged_above=-999 required=5 tests=[AWL=0.443,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 41-nDNzh5fJI for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 19:05:02 -0800 (PST)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id 61DA31F0D48 for <homenet@ietf.org>; Mon, 14 Nov 2011 19:05:02 -0800 (PST)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id pAF34xMF022059 for <homenet@ietf.org>; Tue, 15 Nov 2011 03:04:59 GMT
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk pAF34xMF022059
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1321326299; bh=P7sK1hboJjHU6eYjXh8XiK3j6/s=; h=From:Mime-Version:Subject:Date:In-Reply-To:To:References; b=PPFC7upUni2r0+KSgxxOykfws7vNQMoym02Qb/g8nyxHXSm09A/VrOWTnuDmdNS6l e6W65rxi5ia6mz2wG923Jdas17sU7qwudA/EputLai2yFaGPqfGRz6RcuBY2rdwrjP lDOi2mJd+8R1jUoEzA4qZoyyLkgLJ3rWUMqD9IUo=
Received: from gander.ecs.soton.ac.uk ([2001:630:d0:f102:250:56ff:fea0:401]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102:250:56ff:fea0:68da]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP id nAE34x0543759921YR ret-id none; Tue, 15 Nov 2011 03:04:59 +0000
Received: from dhcp-1678.meeting.ietf.org (dhcp-1678.meeting.ietf.org [130.129.22.120]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id pAF33Z4F027603 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <homenet@ietf.org>; Tue, 15 Nov 2011 03:03:37 GMT
From: Tim Chown <tjc@ecs.soton.ac.uk>
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: multipart/alternative; boundary="Apple-Mail=_81570DF0-F4C1-4071-804D-6FD58FF25037"
Date: Tue, 15 Nov 2011 03:03:34 +0000
In-Reply-To: <4EC1D42B.7070105@gmail.com>
To: "homenet@ietf.org Group" <homenet@ietf.org>
References: <19345.1321323990@marajade.sandelman.ca> <4EC1D42B.7070105@gmail.com> <E5975A2E-6C4F-42A0-A444-4E1902230C95@ecs.soton.ac.uk>
Message-ID: <EMEW3|c9a6b972cc64ff8b6185463e28c35a72nAE34x03tjc|ecs.soton.ac.uk|E5975A2E-6C4F-42A0-A444-4E1902230C95@ecs.soton.ac.uk>
X-Mailer: Apple Mail (2.1251.1)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=nAE34x054375992100; tid=nAE34x0543759921YR; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=1:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: pAF34xMF022059
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Subject: Re: [homenet] privacy vs subnet-id
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 03:05:03 -0000

--Apple-Mail=_81570DF0-F4C1-4071-804D-6FD58FF25037
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

So at the moment all the arch text says on privacy is:
   Privacy considerations

      There are no specific privacy concerns for this text.  It should
      be noted that most ISPs are expected to offer static IPv6 prefixes
      to customers, and thus the addresses they use would not generally
      change over time.
What would you like to say here instead?

Note 4941 isn't just about source address from location to location but =
also source address over time.

The LNP for IPv6 text (RFC4864) talks about this issue a bit, but this =
is more about obfuscating the topology externally to the user's network, =
rather than internally.   In my view we should probably only consider a =
similar perspective here?

Tim

On 15 Nov 2011, at 02:53, Brian E Carpenter wrote:

> On 2011-11-15 15:26, Michael Richardson wrote:
>> Brian Carpenter raised the point at the mic that we have to pay
>> attention to privacy when it comes to the subnet-id.  We shouldn't =
make
>> it possible for members of the household to spy on each other.
>>=20
>> My understanding of the purpose of RFC4941 privacy extensions is to =
make
>> is hard for an (off-path) observer (including web server operator) to
>> trivially track a user from location to location by their EUI-64.=20
>>=20
>> The question is, do we have any similar requirements that we want to
>> apply to subnet-id.  The example that Brian gave in XMPP was:
>>=20
>> BEC> And if you have a separate subnet for the kids' bedroom...
>> BEC> 'Honey, one of the kids is using Facebook again'
>>=20
>> if there is only one possible host on a particular subnet, then =
RFC4941
>> can't help disguise who is doing what. =20
>>=20
>> My question is: what is the real issue here.  It seems that the kind =
of
>> things that 4941 deals with, are neither better nor worse.  But maybe
>> there are other things that we need to concern ourselves with.
>=20
> Waxing philosophical, you can obfuscate an ID but you can't obfuscate
> a locator. I really don't see a way out of this. If the admin can
> run Wireshark, she can see the locator.
>=20
>    Brian
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet


--Apple-Mail=_81570DF0-F4C1-4071-804D-6FD58FF25037
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">So at =
the moment all the arch text says on privacy is:<div><span =
class=3D"Apple-style-span" style=3D"font-family: Times; "><pre =
style=3D"word-wrap: break-word; white-space: pre-wrap; ">   Privacy =
considerations

      There are no specific privacy concerns for this text.  It should
      be noted that most ISPs are expected to offer static IPv6 prefixes
      to customers, and thus the addresses they use would not generally
      change over time.</pre></span></div><div>What would you like to =
say here instead?</div><div><br></div><div>Note 4941 isn't just about =
source address from location to&nbsp;location but also source address =
over time.</div><div><br></div><div>The LNP for IPv6 text (RFC4864) =
talks about this issue a bit, but this is more about obfuscating the =
topology externally to the user's network, rather than internally. =
&nbsp; In my view we should probably only consider a similar perspective =
here?</div><div><br></div><div>Tim</div><div><br><div><div>On 15 Nov =
2011, at 02:53, Brian E Carpenter wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div>On =
2011-11-15 15:26, Michael Richardson wrote:<br><blockquote =
type=3D"cite">Brian Carpenter raised the point at the mic that we have =
to pay<br></blockquote><blockquote type=3D"cite">attention to privacy =
when it comes to the subnet-id. &nbsp;We shouldn't =
make<br></blockquote><blockquote type=3D"cite">it possible for members =
of the household to spy on each other.<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">My =
understanding of the purpose of RFC4941 privacy extensions is to =
make<br></blockquote><blockquote type=3D"cite">is hard for an (off-path) =
observer (including web server operator) to<br></blockquote><blockquote =
type=3D"cite">trivially track a user from location to location by their =
EUI-64. <br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">The question =
is, do we have any similar requirements that we want =
to<br></blockquote><blockquote type=3D"cite">apply to subnet-id. =
&nbsp;The example that Brian gave in XMPP =
was:<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">BEC&gt; And if =
you have a separate subnet for the kids' =
bedroom...<br></blockquote><blockquote type=3D"cite">BEC&gt; 'Honey, one =
of the kids is using Facebook again'<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">if there is =
only one possible host on a particular subnet, then =
RFC4941<br></blockquote><blockquote type=3D"cite">can't help disguise =
who is doing what. &nbsp;<br></blockquote><blockquote =
type=3D"cite"><br></blockquote><blockquote type=3D"cite">My question is: =
what is the real issue here. &nbsp;It seems that the kind =
of<br></blockquote><blockquote type=3D"cite">things that 4941 deals =
with, are neither better nor worse. &nbsp;But =
maybe<br></blockquote><blockquote type=3D"cite">there are other things =
that we need to concern ourselves with.<br></blockquote><br>Waxing =
philosophical, you can obfuscate an ID but you can't obfuscate<br>a =
locator. I really don't see a way out of this. If the admin can<br>run =
Wireshark, she can see the locator.<br><br> =
&nbsp;&nbsp;&nbsp;Brian<br>_______________________________________________=
<br>homenet mailing list<br><a =
href=3D"mailto:homenet@ietf.org">homenet@ietf.org</a><br>https://www.ietf.=
org/mailman/listinfo/homenet<br></div></blockquote></div><br></div></body>=
</html>=

--Apple-Mail=_81570DF0-F4C1-4071-804D-6FD58FF25037--

From fred@cisco.com  Mon Nov 14 19:08:20 2011
Return-Path: <fred@cisco.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C984C1F0C98 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 19:08:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.806
X-Spam-Level: 
X-Spam-Status: No, score=-107.806 tagged_above=-999 required=5 tests=[AWL=-1.207, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jdtWpKbm2Qpe for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 19:08:20 -0800 (PST)
Received: from ams-iport-3.cisco.com (ams-iport-3.cisco.com [144.254.224.146]) by ietfa.amsl.com (Postfix) with ESMTP id 038BA1F0C92 for <homenet@ietf.org>; Mon, 14 Nov 2011 19:08:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=2737; q=dns/txt; s=iport; t=1321326500; x=1322536100; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to:content-transfer-encoding; bh=eO7ys/GkJjE0VHDcDLQgSQv1mp07VsMKPwK4wE1D5ns=; b=H1f9jz/5QxkfKdnQufl7ZB2zuImayq2MfqLVjdCJL+OzF+rvDMHhPDSr GHu2jwDMP4P1fOFNdmUtDvHw7dGAg6cqAWOMyjXxnbr/7GmqrkeYJVY7p pBe6rT+8zNM1sah78MhLMUlQjCdCXfP4d39EBFFS97vtA5pjDsmiowEeY E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAB7XwU5Io8US/2dsb2JhbABDqWmBBYFyAQEBAwEBAQEPAVsLBQsLDgouIQYwBhMbB4dgCJwkAZ5+BIkcYwSIDowghTuFEIc7
X-IronPort-AV: E=Sophos;i="4.69,512,1315180800";  d="scan'208";a="3068221"
Received: from bgl-core-3.cisco.com ([72.163.197.18]) by ams-iport-3.cisco.com with ESMTP; 15 Nov 2011 03:08:18 +0000
Received: from dhcp-57cd.meeting.ietf.org (hkidc-vpn-client-235-225.cisco.com [10.75.235.225]) by bgl-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id pAF38GjC019793; Tue, 15 Nov 2011 03:08:16 GMT
Received: from [127.0.0.1] by dhcp-57cd.meeting.ietf.org (PGP Universal service); Tue, 15 Nov 2011 11:08:17 +0800
X-PGP-Universal: processed; by dhcp-57cd.meeting.ietf.org on Tue, 15 Nov 2011 11:08:17 +0800
Mime-Version: 1.0 (Apple Message framework v1084)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <3C716203-8579-41EA-98CE-6DC3BE9261D8@fugue.com>
Date: Tue, 15 Nov 2011 11:08:11 +0800
Message-Id: <45C66838-F826-472C-988E-47ACCE5C8D76@cisco.com>
References: <4EC1D206.2070303@gmail.com> <3C716203-8579-41EA-98CE-6DC3BE9261D8@fugue.com>
To: Ted Lemon <mellon@fugue.com>
X-Mailer: Apple Mail (2.1084)
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Cc: "homenet@ietf.org" <homenet@ietf.org>
Subject: Re: [homenet] draft-baker-homenet-prefix-assignment
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 03:08:21 -0000

On Nov 15, 2011, at 10:52 AM, Ted Lemon wrote:

> On Nov 15, 2011, at 10:44 AM, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:
>> The mic line was too long to bring this up:
>> You suggest using RFC 3633. How about RFC 2894 (Router renumbering) =
too?
>> Typo: the draft actually cites RFC 3363, which is not what you =
intended...
>=20
> Ditto on the mic line=97very frustrating.   I think you overestimate =
the obstacles to using DHCPv6 PD for this application.   I don't think =
any protocol extension is required.   What is needed is ad-hoc relay =
configuration, which is already anticipated.   The CPE device can just =
allocate a /64 for any PD it receives, and with ad-hoc relaying, it =
should all Just Work.

It's comforting that you think I overestimate the issues.=20

> The way ad hoc relaying works is that when you come up, your PD client =
asks for a prefix on its upstream port.   If it receives PDs, it relays =
them on its upstream port.   These PDs all wind up at the CPE device, =
which allocates /64s to them and forwards them back, all in accordance =
with the existing DHCP relay mechanism.

Let me say something that will probably get me tarred and feathered. I =
suspect that if we come up with a good solution for the home, it will be =
used in small networks wherever they materialize. So I think of a home =
or SOHO as a special case of a small network. I could imagine, for =
example, a company that has lots of campuses and lots of buildings in =
each campus considering each campus or each building to be a "small =
network" and letting it use this class of procedure within itself.

"upstream port"? If I have a multihomed network with a CPE per upstream, =
and the "inside" interface on one CPE develops an address in a different =
CPE's prefix, is it "upstream" or "downstream" from that other CPE?

Yes, I know those words get printed on plastic my company sells. It =
think it's a pretty bad paradigm for anything I'd call scalable to =
anything but the tiniest domain. I would far rather generate a solution =
that can be used effectively within an arbitrary domain, such as a =
single area OSPF network, without being unnecessarily hobbled in its =
thinking. Anything that gives a router a direction is a rather strange =
hobble in that context.

> I think homenet would have to do a draft describing how to set this =
up, but it does not require a DHCP extension.   There'd be some details =
to document on how the routing topology gets set up; perhaps that could =
be done with OSPF.
>=20
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet


From acee.lindem@ericsson.com  Mon Nov 14 19:11:46 2011
Return-Path: <acee.lindem@ericsson.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 776AC1F0D30 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 19:11:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.518
X-Spam-Level: 
X-Spam-Status: No, score=-6.518 tagged_above=-999 required=5 tests=[AWL=0.080,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iLw9MiHQZ4sB for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 19:11:45 -0800 (PST)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 7DB921F0C92 for <homenet@ietf.org>; Mon, 14 Nov 2011 19:11:45 -0800 (PST)
Received: from eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id pAF3BgtX024303; Mon, 14 Nov 2011 21:11:43 -0600
Received: from EUSAACMS0702.eamcs.ericsson.se ([169.254.1.218]) by eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) with mapi; Mon, 14 Nov 2011 22:11:36 -0500
From: Acee Lindem <acee.lindem@ericsson.com>
To: Lorenzo Colitti <lorenzo@google.com>
Date: Mon, 14 Nov 2011 22:11:33 -0500
Thread-Topic: Comments on draft-acee-ospf-ospfv3-autoconfig-00
Thread-Index: AcyjREg+vvIUREn9SN2YLq5jJX9srA==
Message-ID: <FF6FB9A0-9F91-4658-A265-BA200A0858AF@ericsson.com>
References: <CAKD1Yr3uSsNP4avZBdQE7YxFd7D_KOXBOCsfaRfvnWhJoLoY9Q@mail.gmail.com> <B3BE775A-4EBB-4C17-9EDC-7B9AFCB8867E@ericsson.com> <CAKD1Yr0MFdyBopr0E0WiebLSZ+M2J9vAi1U6b66VxhziE2XJpw@mail.gmail.com>
In-Reply-To: <CAKD1Yr0MFdyBopr0E0WiebLSZ+M2J9vAi1U6b66VxhziE2XJpw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/signed; boundary="Apple-Mail-50--577890397"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
Cc: "homenet@ietf.org" <homenet@ietf.org>, Jari Arkko <jari.arkko@piuha.net>
Subject: Re: [homenet] Comments on draft-acee-ospf-ospfv3-autoconfig-00
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 03:11:46 -0000

--Apple-Mail-50--577890397
Content-Type: multipart/alternative;
	boundary=Apple-Mail-49--577890412


--Apple-Mail-49--577890412
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Nov 14, 2011, at 9:46 PM, Lorenzo Colitti wrote:

> On Tue, Nov 15, 2011 at 10:25, Acee Lindem <acee.lindem@ericsson.com> =
wrote:
> > 1. I think the OSPFv3 router ID should not be based on the MAC =
address because that will encourage people to assume it's unique "most =
of the time". I think we should just make it a pseudo-random number so =
it's clear that uniqueness is only guaranteed by collision detection and =
that collision detection needs to be robust.
>=20
> The draft requires duplicate Router-ID detection and resolution. I =
don't think that the fact that a portion of the MAC address is used as a =
first try is reason for this detection/resolution not to be implemented =
or tested.
>=20
> In my experience, giving people something that works "most of the =
time" will cause the cases where it doesn't work to break. I think it's =
better to explicitly provide no guarantees of uniqueness to make it =
clear that collision detection needs to be robust.

In the OSPF WG, the fact that a mechanism is specified implies that it =
is required to be robust.=20

> Also, if we rely on collision detection, then what's the advantage of =
using the MAC address? We might as well as make it random all the time - =
that probably has a lower chance of collision anyway.

I can't disagree with this argument and think we could go with a =
psuedo-random number seeded with a hash on the hardware fingerprint as =
the first try for router-id.=20

>=20
> I think you mean virtual links. They are definitely not needed in the =
auto-configured environment as they are for providing a backbone path =
through a transit area and the OSPFv3 auto-configured routing domain =
assumes only a backbone area.
>=20
> Yes, virtual links. Do we need to state explicitly that they cannot =
exist and are not supported?

Since the auto-configured routing domain is area 0 only, it is explicit.=20=


> =20
> > 3. Can we use normal LSAs to detect collisions? One idea would be =
"if you see your own router ID in the list of neighbours of a network =
LSA or router LSA, then there is a collision". Will that work? If so we =
wouldn't need the hardware fingerprint at all.
>=20
> No. In an arbitrary topology, A router with a duplicate router-id can =
be multiple hops away.
>=20
> Yes, but router and network LSAs are flooded, so you'll hear them =
regardless of whether your duplicate is multiple hops away, no?

Both OSPFv3 and OSPFv2 would consider an unrecognized self-originated =
LSA, i.e. having our Route-ID, as a stale LSA and purge it. This is a =
very basic mechanism of OSPF. I'd rather use a separate mechanism for =
duplicate Router-ID detection. I considered techniques involving the =
encoding some additional information in the Router-LSA but these all =
seemed to be hacked.=20


> =20
> If the pre-shared key is hard-coded, it is no better than the OSPFv3 =
Interface Instance ID that is specified to prevent inadvertent =
adjacencies with routers not supporting the auto-configuration. If =
configuration of a pre-shared key is required, you no longer have =
auto-configuration.
>=20
> Sorry, that wasn't clear. What I meant to say is that we should pick =
one scheme (e.g., HMAC-SHA) and stick to it; we shouldn't support =
multiple schemes as that will lead to interoperability issues for =
devices that use one scheme and devices that use another scheme.

The OSPFv3 Instance ID is part of the base OSPFv3 specification and I =
think it is a very good mechanism to prevent inadvertent adjacencies. If =
we need real authentication, we'll need a pre-shared key. I don't see =
any advantage of authentication with a well-known pre-shared key to =
prevent inadvertent adjacencies.=20

Thanks for the comments,
Acee=20



--Apple-Mail-49--577890412
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On Nov 14, 2011, at 9:46 PM, Lorenzo Colitti =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div class=3D"gmail_quote">On Tue, Nov 15, 2011 at 10:25, =
Acee Lindem <span dir=3D"ltr">&lt;<a =
href=3D"mailto:acee.lindem@ericsson.com">acee.lindem@ericsson.com</a>&gt;<=
/span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex;">

<div class=3D"im">&gt; 1. I think the OSPFv3 router ID should not be =
based on the MAC address because that will encourage people to assume =
it's unique "most of the time". I think we should just make it a =
pseudo-random number so it's clear that uniqueness is only guaranteed by =
collision detection and that collision detection needs to be robust.<br>


<br>
</div>The draft requires duplicate Router-ID detection and resolution. I =
don't think that the fact that a portion of the MAC address is used as a =
first try is reason for this detection/resolution not to be implemented =
or tested.<br>

</blockquote><div><br>In my experience, giving people something that =
works "most of the time" will cause the cases where it doesn't work to =
break.&nbsp;<span style=3D"background-color: transparent; ">I think it's =
better to explicitly provide no guarantees of uniqueness to make it =
clear that collision detection needs to be robust. =
</span></div></div></blockquote><div><br></div><div>In the OSPF WG, the =
fact that a mechanism is specified implies that it is required to be =
robust.&nbsp;</div><br><blockquote type=3D"cite"><div =
class=3D"gmail_quote"><div><span style=3D"background-color: transparent; =
">Also, i</span><span style=3D"background-color: transparent; ">f we =
rely on collision detection, then what's the advantage of using the MAC =
address? We might as well as make it random all the time - that probably =
has a lower chance of collision =
anyway.</span></div></div></blockquote><div><br></div><div>I can't =
disagree with this argument and think we could go with a psuedo-random =
number seeded with a hash on the hardware fingerprint as the first try =
for router-id.&nbsp;</div><div><br></div><blockquote type=3D"cite"><div =
class=3D"gmail_quote">

<div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class=3D"im"><span style=3D"background-color: transparent; ">I =
think you mean virtual links. They are definitely not needed in the =
auto-configured environment as they are for providing a backbone path =
through a transit area and the OSPFv3 auto-configured routing domain =
assumes only a backbone area.</span></div>

</blockquote><div><br></div><div>Yes, virtual links. Do we need to state =
explicitly that they cannot exist and are not =
supported?</div></div></blockquote><div><br></div><div>Since the =
auto-configured routing domain is area 0 only, it is =
explicit.&nbsp;</div><br><blockquote type=3D"cite"><div =
class=3D"gmail_quote"><div>&nbsp;</div><blockquote class=3D"gmail_quote" =
style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex;">


<div class=3D"im">&gt; 3. Can we use normal LSAs to detect collisions? =
One idea would be "if you see your own router ID in the list of =
neighbours of a network LSA or router LSA, then there is a collision". =
Will that work? If so we wouldn't need the hardware fingerprint at =
all.<br>


<br>
</div>No. In an arbitrary topology, A router with a duplicate router-id =
can be multiple hops away.<br></blockquote><div><br></div><div>Yes, but =
router and network LSAs are flooded, so you'll hear them regardless of =
whether your duplicate is multiple hops away, =
no?</div></div></blockquote><div><br></div><div>Both OSPFv3 and OSPFv2 =
would consider an unrecognized self-originated LSA, i.e. having our =
Route-ID, as a stale LSA and purge it. This is a very basic mechanism of =
OSPF. I'd rather use a separate mechanism for duplicate Router-ID =
detection. I considered techniques involving the encoding some =
additional information in the Router-LSA but these all seemed to be =
hacked.&nbsp;</div><div><br></div><br><blockquote type=3D"cite"><div =
class=3D"gmail_quote">

<div>&nbsp;</div><blockquote class=3D"gmail_quote" style=3D"margin-top: =
0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; =
border-left-width: 1px; border-left-color: rgb(204, 204, 204); =
border-left-style: solid; padding-left: 1ex; position: static; z-index: =
auto; ">
<div class=3D"im"><span style=3D"background-color: transparent; ">If the =
pre-shared key is hard-coded, it is no better than the OSPFv3 Interface =
Instance ID that is specified to prevent inadvertent adjacencies with =
routers not supporting the auto-configuration. If configuration of a =
pre-shared key is required, you no longer have =
auto-configuration.</span></div>

</blockquote><div><br></div><div>Sorry, that wasn't clear. What I meant =
to say is that we should pick one scheme (e.g., HMAC-SHA) and stick to =
it; we shouldn't support multiple schemes as that will lead to =
interoperability issues for devices that use one scheme and devices that =
use another scheme.</div>

</div>
</blockquote><br></div><div>The OSPFv3 Instance ID is part of the base =
OSPFv3 specification and I think it is a very good mechanism to prevent =
inadvertent adjacencies. If we need real authentication, we'll need a =
pre-shared key. I don't see any advantage of authentication with a =
well-known pre-shared key to prevent inadvertent =
adjacencies.&nbsp;</div><div><br></div><div>Thanks for the =
comments,</div><div>Acee&nbsp;</div><div><br></div><br></body></html>=

--Apple-Mail-49--577890412--

--Apple-Mail-50--577890397
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIM8jCCBDQw
ggMcoAMCAQICECFWwVQHDV12M/Sr0yNv0sYwDQYJKoZIhvcNAQEFBQAwOTERMA8GA1UECgwIRXJp
Y3Nzb24xJDAiBgNVBAMMG0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMTAeFw0xMDEwMDEyMDA0
NTlaFw0xMzEwMDEyMDA0NDhaMG8xETAPBgNVBAoMCEVyaWNzc29uMR8wHQYDVQQDDBZBY2VlIExp
bmRlbSBMaW5kZW0gSUlJMRAwDgYDVQQFEwdlYWxmbGluMScwJQYJKoZIhvcNAQkBFhhhY2VlLmxp
bmRlbUBlcmljc3Nvbi5jb20wgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAI/Dc9ALiZuBMyuv
bsc3eBxjXZpMi45Z0vzsUQZTJGTBeY7p9JsdzXC9J1uMisBxYVi39R3KJo6I4hXVp9wrA1rxh4AE
bnP1+Gxfpj33uWEFYbBnVAJkIWYWF7CYTn8Zm/yd13vPXtuGA6ESeLnnJafwC9Y0YwUQ+4HX7PNv
uauVAgMBAAGjggGEMIIBgDCBwAYDVR0fBIG4MIG1MIGyoIGvoIGshjdodHRwOi8vY3JsLnRydXN0
LnRlbGlhLmNvbS9Fcmljc3Nvbk5MSW5kaXZpZHVhbENBMDEuY3JshnFsZGFwOi8vbGRhcC50cnVz
dC50ZWxpYS5jb20vY249RXJpY3Nzb24lMjBOTCUyMEluZGl2aWR1YWwlMjBDQTAxLG89RXJpY3Nz
b24/Y2VydGlmaWNhdGVyZXZvY2F0aW9ubGlzdDtiaW5hcnk/YmFzZTAjBgNVHREEHDAagRhhY2Vl
LmxpbmRlbUBlcmljc3Nvbi5jb20wRgYDVR0gBD8wPTA7BgYqhXBrAQEwMTAvBggrBgEFBQcCARYj
aHR0cDovL3d3dy5lcmljc3Nvbi5jb20vbGVnYWwuc2h0bWwwHQYDVR0OBBYEFAgOzAPuplmPr7C1
BTqV94OyqUdhMB8GA1UdIwQYMBaAFJYnw7jepV9dRD45UuVFsXZfYzCbMA4GA1UdDwEB/wQEAwIF
oDANBgkqhkiG9w0BAQUFAAOCAQEAE1gyNW6c2t/YsLxW5sm67+gVGK0Lnge4ub+k8dgGrK7Mj7em
nkOIFkjdv/tqdJ/SoUy/WEkBXba2TfpZ+lfluMgLYux1vSvqBUxYBsUHeNth2Q/Y6A9sCaDTBPlK
vZ2jLz814NavrVfgTCLdxX6zNtGdwzhviz+FyqyxYF43Q86RP8Gd/Npaz1W8pmYAHm0+lezuTx5k
F3Av3+SaZ/MR6s+RWuXEIdED36ajeQz+OG8Mh3nplofzdrOeoWGDz53YlfRhgj+TXo+H1lclZAvD
WVaMMXPdb27h9Hngsq87dkCW9uAyv8DI993rdhqzlEgUyQIL32icAXfTmTYgoGPOwjCCBEUwggMt
oAMCAQICEBPJ6v/eJq2p3KTKI4GDR+MwDQYJKoZIhvcNAQEFBQAwRDEaMBgGA1UECgwRVGVsaWFT
b25lcmEgR3JvdXAxJjAkBgNVBAMMHVRlbGlhU29uZXJhIFB1YmxpYyBSb290IENBIHYxMB4XDTA2
MTAwNjEwMDA1M1oXDTE2MTAwMjA1MDQxN1owOTERMA8GA1UECgwIRXJpY3Nzb24xJDAiBgNVBAMM
G0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoC
ggEBALYQd+Q1HuuHxDyNGFlEPzCxuPPFO5W2xyr+nqCVnNJ4QYFe1HACqavqNLwUGIqIEyHv1rLn
fub9LBc7dQpRHjl/dggin0ONOFJ36nbGEbfHjLJz2BzOWvwl84Sc+Fx09IrDU/SZSWFSfhqTu3TT
39h79brHdRkdPBUgBYgsiFKriHI0TjP5G8628H27BDzqUpzGLSYWgt6/tpwuOH5lcfNfHWMcCYXR
lobv0Klu8lxG5amWqAnqrH6ECOyYJTRbHTsaTIZOHy9Qw/0eXPujKT7tU5xxSI2SdceJqzUbAz2o
FRQ6Px7/GydpM/Rl+qYoGPcauHUL1aSeVJZqDFqcIF0CAwEAAaOCATwwggE4MBIGA1UdEwEB/wQI
MAYBAf8CAQAwRgYDVR0gBD8wPTA7BgcqhXAjAgEBMDAwLgYIKwYBBQUHAgEWImh0dHBzOi8vcmVw
b3NpdG9yeS50cnVzdC50ZWxpYS5jb20wgYkGA1UdHwSBgTB/MH2ge6B5hndsZGFwOi8vbGRhcC50
cnVzdC50ZWxpYS5jb20vY249VGVsaWFTb25lcmElMjBQdWJsaWMlMjBSb290JTIwQ0ElMjB2MSxv
PVRlbGlhU29uZXJhJTIwR3JvdXA/YXV0aG9yaXR5cmV2b2NhdGlvbmxpc3Q/YmFzZTAOBgNVHQ8B
Af8EBAMCAQYwHQYDVR0OBBYEFJYnw7jepV9dRD45UuVFsXZfYzCbMB8GA1UdIwQYMBaAFEXb8I+4
GmKhqCMbY4g4o9vgGmLxMA0GCSqGSIb3DQEBBQUAA4IBAQB2AEoqQz+M3Ra9alkpn/YnwhXIv6tP
jhUvSuNs00Nhd0T9XhlIU3a65CaB/UKSqnayE0t7Q0Qq3r+x/GK3in/mik8i/PK2/q8HutzYFSzz
6Npztpo2JG7AEKOJPVaeebjng45m6vNC7RIfzU9sG2LBR/hewS8s6dFFn70w795xUwJBWZ67OzIK
XrIVVvHTOYpbWA+MESKAXwFhnVONrOTWlVwrMUi4HbiPWpOk+xQbgehCEi7mu3cXsaU1Xq3kMXui
NuC7VKoob8mFO9o9RT+dlirD2uRXwNpvCu3but6Kyhu0+nvy2iXGKjdlxlWTsdDyulXYz+OYCMZ9
lFWRzMIPMIIEbTCCA1WgAwIBAgIRAJywjASay5cieGNithuGWj0wDQYJKoZIhvcNAQEFBQAwOjEZ
MBcGA1UEChMQUlNBIFNlY3VyaXR5IEluYzEdMBsGA1UECxMUUlNBIFNlY3VyaXR5IDIwNDggVjMw
HhcNMDYxMDMxMjA0MjI3WhcNMTYxMTAxMTU0MjI1WjBEMRowGAYDVQQKDBFUZWxpYVNvbmVyYSBH
cm91cDEmMCQGA1UEAwwdVGVsaWFTb25lcmEgUHVibGljIFJvb3QgQ0EgdjEwggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQDKTxADapCAq3mplX4R4gNt+WZe5QKGnaVEQSyY7lICKF5DuVdW
PMLHDjzhw5IzDd860ZZx/0VrhGB3DmP4SDIWCKo2PxvY5NckdBWPWp/T2uaQdOAwgqHpN0pe1X7/
jel59WsWYXKGg/81Wth73ZK/geE7Gz9Pvj1LU6N4YhLMgooxKnCS+ZjB5icWAg+Qd1QpQhF46H1i
bp6LsBWDp56MPpg8F5X6y7MGVcKYLdnLOPs84uxRW9qs1kBopzQBj6s5SyVh8A+j5liDBjghXYpw
/+paGEdqHPeSFYxZKeJatmjEKLYlxcZWRKf436KvQA9jBhMEmytMNbGicR1mRH6tAgMBAAGjggFi
MIIBXjAfBgNVHSMEGDAWgBQHw1EwpKrpRa41JPr/JCwz0LGdjDAdBgNVHQ4EFgQURdvwj7gaYqGo
IxtjiDij2+AaYvEwEgYDVR0TAQH/BAgwBgEB/wIBBDCBhQYDVR0gBH4wfDA9BgkqhkiG9w0FBgEw
MDAuBggrBgEFBQcCARYiaHR0cHM6Ly9yZXBvc2l0b3J5LnRydXN0LnRlbGlhLmNvbTA7BgcqhXAj
AgEBMDAwLgYIKwYBBQUHAgEWImh0dHBzOi8vcmVwb3NpdG9yeS50cnVzdC50ZWxpYS5jb20wcAYD
VR0fBGkwZzBloGOgYYZfaHR0cDovL3d3dy5yc2FzZWN1cml0eS5jb20vcHJvZHVjdHMva2Vvbi9y
ZXBvc2l0b3J5L2NlcnRpZmljYXRlX3N0YXR1cy9SU0FfU2VjdXJpdHlfMjA0OF92My5DUkwwDgYD
VR0PAQH/BAQDAgEGMA0GCSqGSIb3DQEBBQUAA4IBAQAEXpos2CnIm7/872ytSrEHWZgvhOUEkUm2
5PWf/XkWko41TaL9vIS1S6AdWChNqWmnYiS7GfaIiDM9s1D6K7hidWBDOm46bNdM3ZwhMyDCfkDJ
SgeJ0w+7YmjvChu7gWqDZCsbtZ5gA1ixCTdDnuZB67JGSPGW6r73coraDP8diOpiQouMvM6bKuTP
BH/1poLccsUxsKgrQ23JC9LWCRb8cYHkZjXFH1K44TsIl5Lne2oT0JI3pwdA2v6jO4p/OLHntP+n
pjwPbedMPUZkDYCkd3LSxj8c3JTxtA8SlPCtIHE1hh65xihg1JRIliSphrqr9kbfwHdeVxPdOI5G
tDYPMYICEjCCAg4CAQEwTTA5MREwDwYDVQQKDAhFcmljc3NvbjEkMCIGA1UEAwwbRXJpY3Nzb24g
TkwgSW5kaXZpZHVhbCBDQTAxAhAhVsFUBw1ddjP0q9Mjb9LGMAkGBSsOAwIaBQCgggEbMBgGCSqG
SIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMTExNTAzMTEzM1owIwYJKoZI
hvcNAQkEMRYEFNCIzo9HV3LasCpV46H7H79sKr/zMFwGCSsGAQQBgjcQBDFPME0wOTERMA8GA1UE
CgwIRXJpY3Nzb24xJDAiBgNVBAMMG0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMQIQIVbBVAcN
XXYz9KvTI2/SxjBeBgsqhkiG9w0BCRACCzFPoE0wOTERMA8GA1UECgwIRXJpY3Nzb24xJDAiBgNV
BAMMG0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMQIQIVbBVAcNXXYz9KvTI2/SxjANBgkqhkiG
9w0BAQEFAASBgDzHbjtOvhYVvBdVt15pm6rKL7Xtb6/l9vyd5EGvzU7wipwCodDQJFg10Qv8uSnV
G4E5ztS/cfhatpqoP7uDmo8225A8urX8Yw4Y/jWJYiUeeWfyfoH3OR42n0AVOwrqYjQvuHzXqCUW
PjVFIP4TIRpRoMzHNvdAZYH8mYHYEkpRAAAAAAAA

--Apple-Mail-50--577890397--

From mcr@sandelman.ca  Mon Nov 14 19:15:46 2011
Return-Path: <mcr@sandelman.ca>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AEB5F11E8179 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 19:15:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.627
X-Spam-Level: 
X-Spam-Status: No, score=-1.627 tagged_above=-999 required=5 tests=[AWL=0.327,  BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PWFT+TscYDZY for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 19:15:46 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id 4342711E809F for <homenet@ietf.org>; Mon, 14 Nov 2011 19:15:46 -0800 (PST)
Received: from marajade.sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by relay.sandelman.ca (Postfix) with ESMTPS id 26BAB343CD; Mon, 14 Nov 2011 22:14:20 -0500 (EST)
Received: by marajade.sandelman.ca (Postfix, from userid 179) id 3BF6598CB3; Mon, 14 Nov 2011 22:15:45 -0500 (EST)
Received: from marajade.sandelman.ca (localhost [127.0.0.1]) by marajade.sandelman.ca (Postfix) with ESMTP id 2E7E898CB2; Mon, 14 Nov 2011 22:15:45 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ca>
To: homenet@ietf.org
In-Reply-To: <4EC1B66B.9000109@joelhalpern.com>
References: <DCC302FAA9FE5F4BBA4DCAD46569377914518AFAE5@PRVPEXVS03.corp.twcable.com> <4EB583C8.5030907@piuha.net> <13027.1320680393@marajade.sandelman.ca> <BDF2740C082F6942820D95BAEB9E1A845A9789@XMB-AMS-108.cisco.com> <CA+XPzSY8cC_PyhcMNqhk4+B6tghp8Dpy2-3aMPZmyVRP=AWnaA@mail.gmail.com> <3512.1321317664@marajade.sandelman.ca> <4EC1B66B.9000109@joelhalpern.com>
X-Mailer: MH-E 8.1; nmh 1.3-dev; XEmacs 21.4 (patch 22)
Date: Mon, 14 Nov 2011 22:15:45 -0500
Message-ID: <25988.1321326945@marajade.sandelman.ca>
Sender: mcr@sandelman.ca
Cc: "Joel M. Halpern" <jmh@joelhalpern.com>
Subject: Re: [homenet] more comments on draft-arkko-homenet-prefix-assignment
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 03:15:46 -0000

>>>>> "Joel" == Joel M Halpern <jmh@joelhalpern.com> writes:
    Joel> On the one hand, earlier discussion emphasized that we need to
    Joel> use protocols 
    Joel> and implementations that are well tested, robust, and simple
    Joel> to use. 

    Joel> On the other hand, we have an expectation that these same
    Joel> boxes are going to  perform source address based forwarding
    Joel> selection, something with which there 
    Joel> is very little experience anywhere?

I'm not sure what would count as experience here.

Selecting a destination address routing table to use by source address
is relatively common, done regularly in Linux and Cisco and Brocade and
Juniper... for more than a decade.

If you mean that we don't have a protocol to explain the source
addresses required, then I disagree: the information is already all
there in the RAs, and would also be in the zOSPF for a solution that
uses that.

-- 
]       He who is tired of Weird Al is tired of life!           |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
   Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE>
	               then sign the petition. 


From brian.e.carpenter@gmail.com  Mon Nov 14 19:20:58 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACE8F1F0D9D for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 19:20:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.561
X-Spam-Level: 
X-Spam-Status: No, score=-103.561 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gci0uqBG+Vwy for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 19:20:57 -0800 (PST)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 5A88F1F0DA0 for <homenet@ietf.org>; Mon, 14 Nov 2011 19:20:57 -0800 (PST)
Received: by vcbfk1 with SMTP id fk1so6812506vcb.31 for <homenet@ietf.org>; Mon, 14 Nov 2011 19:20:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=jdMik72f9lyWTSXO8AX9Pu8+rH4VeLsdkCL/NfaQ0Vw=; b=w/LDnkFLiblQ5vsC+fLknFGgegqbCdeBK6nWaa7b0a+mLKLV0Q8Hv44g9E45d3mC1N gYo1XIe2PE6seXkvN4dwNLSJhz9XPBIv1qpgF+LVbwW733k2YScS/jOEwwng6RJr4Kjf ST9YL5q1BabC6fZv9thBFncQs2lfrgNEA9O6E=
Received: by 10.52.29.108 with SMTP id j12mr10149950vdh.40.1321327256876; Mon, 14 Nov 2011 19:20:56 -0800 (PST)
Received: from [130.129.19.92] (dhcp-135c.meeting.ietf.org. [130.129.19.92]) by mx.google.com with ESMTPS id eu4sm34751377vdc.8.2011.11.14.19.20.54 (version=SSLv3 cipher=OTHER); Mon, 14 Nov 2011 19:20:56 -0800 (PST)
Message-ID: <4EC1DA91.7070309@gmail.com>
Date: Tue, 15 Nov 2011 16:20:49 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Tim Chown <tjc@ecs.soton.ac.uk>
References: <19345.1321323990@marajade.sandelman.ca>	<4EC1D42B.7070105@gmail.com>	<E5975A2E-6C4F-42A0-A444-4E1902230C95@ecs.soton.ac.uk> <EMEW3|c9a6b972cc64ff8b6185463e28c35a72nAE34x03tjc|ecs.soton.ac.uk|E5975A2E-6C4F-42A0-A444-4E1902230C95@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|c9a6b972cc64ff8b6185463e28c35a72nAE34x03tjc|ecs.soton.ac.uk|E5975A2E-6C4F-42A0-A444-4E1902230C95@ecs.soton.ac.uk>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] privacy vs subnet-id
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 03:20:59 -0000

On 2011-11-15 16:03, Tim Chown wrote:
> So at the moment all the arch text says on privacy is:
>    Privacy considerations
> 
>       There are no specific privacy concerns for this text.  It should
>       be noted that most ISPs are expected to offer static IPv6 prefixes
>       to customers, and thus the addresses they use would not generally
>       change over time.
> What would you like to say here instead?

Maybe point out that a homenet can be protected against external privacy
threats (possibly citing 4864 etc) but that whatever hosts do, the homenet
admin has the capability to perform traffic analysis down to the subnet level.

    Brian

> 
> Note 4941 isn't just about source address from location to location but also source address over time.
> 
> The LNP for IPv6 text (RFC4864) talks about this issue a bit, but this is more about obfuscating the topology externally to the user's network, rather than internally.   In my view we should probably only consider a similar perspective here?
> 
> Tim
> 
> On 15 Nov 2011, at 02:53, Brian E Carpenter wrote:
> 
>> On 2011-11-15 15:26, Michael Richardson wrote:
>>> Brian Carpenter raised the point at the mic that we have to pay
>>> attention to privacy when it comes to the subnet-id.  We shouldn't make
>>> it possible for members of the household to spy on each other.
>>>
>>> My understanding of the purpose of RFC4941 privacy extensions is to make
>>> is hard for an (off-path) observer (including web server operator) to
>>> trivially track a user from location to location by their EUI-64. 
>>>
>>> The question is, do we have any similar requirements that we want to
>>> apply to subnet-id.  The example that Brian gave in XMPP was:
>>>
>>> BEC> And if you have a separate subnet for the kids' bedroom...
>>> BEC> 'Honey, one of the kids is using Facebook again'
>>>
>>> if there is only one possible host on a particular subnet, then RFC4941
>>> can't help disguise who is doing what.  
>>>
>>> My question is: what is the real issue here.  It seems that the kind of
>>> things that 4941 deals with, are neither better nor worse.  But maybe
>>> there are other things that we need to concern ourselves with.
>> Waxing philosophical, you can obfuscate an ID but you can't obfuscate
>> a locator. I really don't see a way out of this. If the admin can
>> run Wireshark, she can see the locator.
>>
>>    Brian
>> _______________________________________________
>> 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 ot@cisco.com  Mon Nov 14 19:21:28 2011
Return-Path: <ot@cisco.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4A021F0DA4 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 19:21:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iCttXzgFclcu for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 19:21:28 -0800 (PST)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id 583531F0C9F for <homenet@ietf.org>; Mon, 14 Nov 2011 19:21:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ot@cisco.com; l=1602; q=dns/txt; s=iport; t=1321327288; x=1322536888; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=3I/A429pXucfXtTJ5gyW0j7OiNoiv+CpFPe+iCLVggE=; b=J0TsrQeDIy0FhZ8hvWaPvOFPHlhoFpVgj+UbnLapwWAI8KmgnWJJErjZ sA6I/O7EKA8UHTYGblw6EDCq2/1gbglU0dYVx3nhsRQLQ4Um7ND8kfqRR it4eQh2OHdj1N40HniL/blKaF/M1pGMBGtEbH1+IfMsHdeHOabuYp4chT M=;
X-IronPort-AV: E=Sophos;i="4.69,512,1315180800"; d="scan'208";a="14243074"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-3.cisco.com with ESMTP; 15 Nov 2011 03:21:28 +0000
Received: from [10.21.76.126] ([10.21.76.126]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id pAF3LQEF024122; Tue, 15 Nov 2011 03:21:27 GMT
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=windows-1252
From: Ole Troan <ot@cisco.com>
In-Reply-To: <3C716203-8579-41EA-98CE-6DC3BE9261D8@fugue.com>
Date: Tue, 15 Nov 2011 11:17:39 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <FC520CA0-BAA4-4309-A878-CB40308F2562@cisco.com>
References: <4EC1D206.2070303@gmail.com> <3C716203-8579-41EA-98CE-6DC3BE9261D8@fugue.com>
To: Ted Lemon <mellon@fugue.com>
X-Mailer: Apple Mail (2.1084)
Cc: "homenet@ietf.org" <homenet@ietf.org>, Fred Baker <fred@cisco.com>
Subject: Re: [homenet] draft-baker-homenet-prefix-assignment
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 03:21:29 -0000

Ted,

>> The mic line was too long to bring this up:
>> You suggest using RFC 3633. How about RFC 2894 (Router renumbering) =
too?
>> Typo: the draft actually cites RFC 3363, which is not what you =
intended...
>=20
> Ditto on the mic line=97very frustrating.   I think you overestimate =
the obstacles to using DHCPv6 PD for this application.   I don't think =
any protocol extension is required.   What is needed is ad-hoc relay =
configuration, which is already anticipated.   The CPE device can just =
allocate a /64 for any PD it receives, and with ad-hoc relaying, it =
should all Just Work.
>=20
> The way ad hoc relaying works is that when you come up, your PD client =
asks for a prefix on its upstream port.   If it receives PDs, it relays =
them on its upstream port.   These PDs all wind up at the CPE device, =
which allocates /64s to them and forwards them back, all in accordance =
with the existing DHCP relay mechanism.
>=20
> I think homenet would have to do a draft describing how to set this =
up, but it does not require a DHCP extension.   There'd be some details =
to document on how the routing topology gets set up; perhaps that could =
be done with OSPF.

- how do you discovery the DHCP server? do you require a hard-wired =
upstream port for this to work?
- what do you do with two routers on the same link, two separate =
prefixes? (or smart DHCP server (e.g. having the SPF))
- what do you with multiple sources of information? change the DHCP =
protocol so that a client picks _all_ servers, instead of
  the _best_ one?

cheers,
Ole=

From mcr@sandelman.ca  Mon Nov 14 19:23:32 2011
Return-Path: <mcr@sandelman.ca>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 532671F0C97 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 19:23:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.637
X-Spam-Level: 
X-Spam-Status: No, score=-1.637 tagged_above=-999 required=5 tests=[AWL=0.318,  BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pDO8xKtZTmVq for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 19:23:32 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id C5ED11F0C96 for <homenet@ietf.org>; Mon, 14 Nov 2011 19:23:31 -0800 (PST)
Received: from marajade.sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by relay.sandelman.ca (Postfix) with ESMTPS id 6669D34012; Mon, 14 Nov 2011 22:22:02 -0500 (EST)
Received: by marajade.sandelman.ca (Postfix, from userid 179) id 5E0E398CB3; Mon, 14 Nov 2011 22:23:25 -0500 (EST)
Received: from marajade.sandelman.ca (localhost [127.0.0.1]) by marajade.sandelman.ca (Postfix) with ESMTP id 57C6398CB2; Mon, 14 Nov 2011 22:23:25 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ca>
To: Joe Touch <touch@isi.edu>
In-Reply-To: <4EC1CEDC.20702@isi.edu>
References: <13919.1321321547@marajade.sandelman.ca> <4EC1CEDC.20702@isi.edu>
X-Mailer: MH-E 8.1; nmh 1.3-dev; XEmacs 21.4 (patch 22)
Date: Mon, 14 Nov 2011 22:23:25 -0500
Message-ID: <27059.1321327405@marajade.sandelman.ca>
Sender: mcr@sandelman.ca
Cc: homenet <homenet@ietf.org>
Subject: Re: [homenet] secret sharing among devices
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 03:23:32 -0000

>>>>> "Joe" == Joe Touch <touch@isi.edu> writes:
    >> There have been various discussion in PHL about spreading a secret among
    >> devices so they can authenticate each other.
    >> 
    >> A super cool idea is a specifically formatted file on a USB drive,
    >> inserted into each system in turn.  While we might be pretty sure
    >> the USB drive (and file system and connector, etc.) is out of scope, the
    >> format for that secret file might be well in scope

    Joe> Doesn't that assume the device has a USB connector and can
    Joe> mount a stick as a drive? While that's common on PCs, it's not
    Joe> on home router boxes AFAICT. Many have no USB at all.

1) Joe, "the USB drive is out of scope".
   What matters is that you have some method to get the file into the
   device. How is less important. 

2) a USB port is increasing common on home routers, it's where you plug
   the printer in, or the 16G key or 1TB disk, as the home router
   provides NAS as well.

-- 
]       He who is tired of Weird Al is tired of life!           |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
   Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE>
	               then sign the petition. 


From mcr@sandelman.ca  Mon Nov 14 19:25:52 2011
Return-Path: <mcr@sandelman.ca>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 247701F0C97 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 19:25:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.646
X-Spam-Level: 
X-Spam-Status: No, score=-1.646 tagged_above=-999 required=5 tests=[AWL=0.308,  BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XAwPK7Cy6TTT for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 19:25:51 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id 933EE1F0C96 for <homenet@ietf.org>; Mon, 14 Nov 2011 19:25:51 -0800 (PST)
Received: from marajade.sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by relay.sandelman.ca (Postfix) with ESMTPS id 38D1534012 for <homenet@ietf.org>; Mon, 14 Nov 2011 22:24:27 -0500 (EST)
Received: by marajade.sandelman.ca (Postfix, from userid 179) id 9528998CB3; Mon, 14 Nov 2011 22:25:52 -0500 (EST)
Received: from marajade.sandelman.ca (localhost [127.0.0.1]) by marajade.sandelman.ca (Postfix) with ESMTP id 8F15498CB2 for <homenet@ietf.org>; Mon, 14 Nov 2011 22:25:52 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ca>
To: homenet <homenet@ietf.org>
In-Reply-To: <B3EE827A-E06D-4B1A-8E20-8BEF17F325D3@fugue.com>
References: <13919.1321321547@marajade.sandelman.ca> <4EC1CEDC.20702@isi.edu> <A38099B4-7759-4DD3-92D1-5C6729B445DA@fugue.com> <4EC1D413.2080803@isi.edu> <B3EE827A-E06D-4B1A-8E20-8BEF17F325D3@fugue.com>
X-Mailer: MH-E 8.1; nmh 1.3-dev; XEmacs 21.4 (patch 22)
Date: Mon, 14 Nov 2011 22:25:52 -0500
Message-ID: <27409.1321327552@marajade.sandelman.ca>
Sender: mcr@sandelman.ca
Subject: Re: [homenet] secret sharing among devices
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 03:25:52 -0000

>>>>> "Ted" == Ted Lemon <mellon@fugue.com> writes:
    >> IMO, then explain the format of the key as an ASCII string. The
    >> file can then be described as the bare key. 

    Ted> It's not just one key.   The point of the file is to allow the
    Ted> various devices to *exchange* keys. 

Maybe (it could be supported), but go read RFC6030, from it:

   This document defines a standardized XML-based key container, called
   Portable Symmetric Key Container (PSKC), for transporting symmetric
   keys and key-related metadata.  The document also specifies the
   information elements that are required when the symmetric key is
   utilized for specific purposes, such as the initial counter in the
   HMAC-Based One-Time Password (HOTP) [HOTP] algorithm.  It also
   creates an IANA registry for algorithm profiles where algorithms,
   their metadata and PSKC transmission profile can be recorded for a
   centralized, standardized reference.

so, basically, it's an ASCII file with some <>-based decoration of the
key itself.

-- 
]       He who is tired of Weird Al is tired of life!           |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
   Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE>
	               then sign the petition. 

From rstruik.ext@gmail.com  Mon Nov 14 19:27:26 2011
Return-Path: <rstruik.ext@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8FA9A11E8197 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 19:27:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.539
X-Spam-Level: 
X-Spam-Status: No, score=-3.539 tagged_above=-999 required=5 tests=[AWL=0.060,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rKhsjOuMLnwZ for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 19:27:26 -0800 (PST)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id D7F1011E8137 for <homenet@ietf.org>; Mon, 14 Nov 2011 19:27:25 -0800 (PST)
Received: by vcbfk1 with SMTP id fk1so6818089vcb.31 for <homenet@ietf.org>; Mon, 14 Nov 2011 19:27:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=UNKyboIdTG11kHxRcck0TBUj/eo2+hmIkSFf1IWc8GA=; b=u2IfZw4+eKi3LLiy1PYHQlT7hY9SfTibrBwSwCdWwgsVIXqIcb42egfHXjvut2aF28 8/4M6k+cRVITXJYwL7K9hhxxPGIx/GPaijsEFuLw8+NHz1R2Tszq9rC7VAUct85aqTjb dDe6e+/1/Vo4jEtG2XFhtKfh5yLGPfJpmJjfc=
Received: by 10.52.25.75 with SMTP id a11mr39699870vdg.1.1321327645201; Mon, 14 Nov 2011 19:27:25 -0800 (PST)
Received: from [192.168.1.103] (CPE0013100e2c51-CM001cea35caa6.cpe.net.cable.rogers.com. [99.231.117.243]) by mx.google.com with ESMTPS id ib2sm34812562vdb.1.2011.11.14.19.27.24 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 14 Nov 2011 19:27:24 -0800 (PST)
Message-ID: <4EC1DC14.8070302@gmail.com>
Date: Mon, 14 Nov 2011 22:27:16 -0500
From: Rene Struik <rstruik.ext@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.0; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Ted Lemon <mellon@fugue.com>
References: <13919.1321321547@marajade.sandelman.ca> <4EC1CEDC.20702@isi.edu> <A38099B4-7759-4DD3-92D1-5C6729B445DA@fugue.com> <4EC1D2C6.3020502@gmail.com> <6B3A3374-AC8B-49F1-BEBE-46CA3E795874@fugue.com>
In-Reply-To: <6B3A3374-AC8B-49F1-BEBE-46CA3E795874@fugue.com>
X-Enigmail-Version: 1.3.3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: homenet <homenet@ietf.org>, Michael Richardson <mcr@sandelman.ca>, Joe Touch <touch@isi.edu>
Subject: Re: [homenet] secret sharing among devices
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 03:27:26 -0000

Dear Ted:

Your note below (given by example) suggests a standardized physical
interface to be present on each device, suggests clairvoyance of
configuration decision elements, and procurement of devices from a
single source (or via a potentially expensive "work bench type"
installation/configuration approach).

What about making a list of deployment scenarios, and desired security
and usability behavior, expanding on the below?

Desired properties:
-Evidence regarding the true identity of a device (in casu: router vs.
neighbor's router);
-Evidence about fine-grained device role (in casu: router function,
motion sensor capability, etc.)
-Forward secrecy: compromised device does not compromise its entire past
history
[etc]

Questions:
-Homogeneous vs. heterogeneous trust domain?
-Trust lifecycle - what to do with device replacement, device
repurposing, change of controlling device, etc.?
-Trust initialization - how to provide initial privileged information to
the device?
-Device interface with surroundings: physical communication channel and
properties (e.g., location limited channel)?
[etc]

What would prevent an over-the-air provisioning model (reusing existing
infrastructure, e.g., ZigBee-type radio, powerline, etc.)? I can imagine
(depending on problem description) a 2c per device solution there,
without need for USB plugs, big files, etc.

Hence, my question: what is the problem to be solved here?

Best regards, Rene


On 14/11/2011 9:55 PM, Ted Lemon wrote:
> On Nov 15, 2011, at 10:47 AM, Rene Struik <rstruik.ext@gmail.com> wrote:
>> Could you elaborate about the security services and deployment
>> scenario(s) you wish to facilitate, for the benefit of those not at
>> IETF-82 who subscribe to the mailing list? In other words, what is the
>> problem one tries and solve here?
> We do not want, for example, for devices that aren't supposed to be routers to be routers.   By doing a manual key exchange, we can ensure that only devices that are intended to be part of the network topology have the keys that are required to join the routing infrastructure.
>


-- 
email: rstruik.ext@gmail.com
Skype: rstruik
cell: +1 (647) 867-5658
USA Google voice: +1 (415) 690-7363


From brian.e.carpenter@gmail.com  Mon Nov 14 19:27:32 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C14D1F0CB2 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 19:27:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.564
X-Spam-Level: 
X-Spam-Status: No, score=-103.564 tagged_above=-999 required=5 tests=[AWL=0.035, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s0Cp+uH2lDp3 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 19:27:32 -0800 (PST)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id E2FEB1F0C94 for <homenet@ietf.org>; Mon, 14 Nov 2011 19:27:31 -0800 (PST)
Received: by vws5 with SMTP id 5so6929890vws.31 for <homenet@ietf.org>; Mon, 14 Nov 2011 19:27:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=X5Qkf9jEBOTEMAQlFXZy5LwtXuNokVg4x73e9rn9lPk=; b=wQII7Y3+NbS2kyJhdAruzWO8iGk0jymer591JqbSNc7WSbxubBsW235XTf5BBivDX0 07o0OlMyVOqsaB2reyWWU8jETkT7oXzAVlADih7RyZAgHq8oYjlvc7M0HqT1MKRr6Eri BagDWdWJKips5QQnaxv5Jlmuja5NQtByH+5Zc=
Received: by 10.52.23.12 with SMTP id i12mr39663552vdf.37.1321327651237; Mon, 14 Nov 2011 19:27:31 -0800 (PST)
Received: from [130.129.19.92] (dhcp-135c.meeting.ietf.org. [130.129.19.92]) by mx.google.com with ESMTPS id ib2sm34812565vdb.1.2011.11.14.19.27.28 (version=SSLv3 cipher=OTHER); Mon, 14 Nov 2011 19:27:30 -0800 (PST)
Message-ID: <4EC1DC1B.4090603@gmail.com>
Date: Tue, 15 Nov 2011 16:27:23 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Erik Nordmark <nordmark@cisco.com>
References: <4EC1C386.6010802@gmail.com> <4EC1C566.2060400@cisco.com> <4EC1CC2E.30209@gmail.com> <4EC1D6C9.3030107@cisco.com>
In-Reply-To: <4EC1D6C9.3030107@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: homenet@ietf.org
Subject: Re: [homenet] pervasive v4
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 03:27:32 -0000

On 2011-11-15 16:04, Erik Nordmark wrote:
> On 11/14/11 6:19 PM, Brian E Carpenter wrote:
>> Yes, but then we're extending v4 and expecting homenets to run
>> (presumably) RIP.
> 
> Why RIP? Same protocol between the home routers as we will pick for
> routing IPv6 in the home.

Well, my understanding is that RIP is to be found already on
supermarket home routers. I'm assuming that we aren't asking them
to touch their IPv4 code.

There's no reason that I know why a homenet can't run RIP and OSPFv3
simultaneously.

>> That seems kind of out of scope for this WG.
> 
> I think it is an implication of 1) supporting arbitrary topologies and
> 2) not breaking IPv4. Thus I don't see a different choice for an
> arbitrary topology routed home network.

I am not convinced that 1) AND 2) is feasible without creating a mountain
that is impossible to climb. Supporting topologies that are *already*
possible with v4, maybe. But why shouldn't the kids' bedroom be IPv6-only
even if Grandma must have IPv4?

    Brian

From mellon@fugue.com  Mon Nov 14 19:35:14 2011
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 824B11F0C94 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 19:35:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.392
X-Spam-Level: 
X-Spam-Status: No, score=-1.392 tagged_above=-999 required=5 tests=[AWL=-0.189, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YNaZv3r9aLI5 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 19:35:14 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 2B4361F0C48 for <homenet@ietf.org>; Mon, 14 Nov 2011 19:35:14 -0800 (PST)
Received: from [IPv6:2001:df8::80:9458:4948:63d6:ca83] (unknown [IPv6:2001:df8:0:80:9458:4948:63d6:ca83]) by toccata.fugue.com (Postfix) with ESMTPSA id 408282381CA1; Mon, 14 Nov 2011 22:35:13 -0500 (EST)
References: <4EC1D206.2070303@gmail.com> <3C716203-8579-41EA-98CE-6DC3BE9261D8@fugue.com> <FC520CA0-BAA4-4309-A878-CB40308F2562@cisco.com>
In-Reply-To: <FC520CA0-BAA4-4309-A878-CB40308F2562@cisco.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=utf-8
Message-Id: <09215FB7-EA7A-4D9D-8772-737B79CBBD20@fugue.com>
X-Mailer: iPad Mail (9A334)
From: Ted Lemon <mellon@fugue.com>
Date: Tue, 15 Nov 2011 11:35:41 +0800
To: Ole Troan <ot@cisco.com>
Cc: "homenet@ietf.org" <homenet@ietf.org>, Fred Baker <fred@cisco.com>
Subject: Re: [homenet] draft-baker-homenet-prefix-assignment
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 03:35:14 -0000

On Nov 15, 2011, at 11:17 AM, Ole Troan <ot@cisco.com> wrote:
> - how do you discovery the DHCP server? do you require a hard-wired upstre=
am port for this to work?

Multicast will reach the DHCP server.   Otherwise yes, the hard-wired upstre=
am port allows this to work.

> - what do you do with two routers on the same link, two separate prefixes?=
 (or smart DHCP server (e.g. having the SPF))

I don't know what you mean by a "smart DHCP server having SPF."   But if you=
 have two routers on the same link, either the client picks one and doesn't g=
et to use the other link, or the DHCP servers need to cooperate, or we need t=
o teach the client to get prefix delegations from more than one DHCP server.=
   I think having the DHCP servers do an election is probably the easiest so=
lution.

> - what do you with multiple sources of information? change the DHCP protoc=
ol so that a client picks _all_ servers, instead of the _best_ one?

Right now clients don't pick the best one--they just pick one pretty much at=
 random.  But yes, if you have two DHCP servers providing different informat=
ion, you need to resolve that.   We would have to write a spec to handle thi=
s=E2=80=94it's not handled in the existing protocol.

I think changing the DHCP client is a bad idea because it requires that ever=
y client be changed; changing the DHCP server is easy because only homenet D=
HCP servers have to change.


From touch@isi.edu  Mon Nov 14 19:45:42 2011
Return-Path: <touch@isi.edu>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0EF031F0C45 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 19:45:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.399
X-Spam-Level: 
X-Spam-Status: No, score=-102.399 tagged_above=-999 required=5 tests=[AWL=0.200, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5XTLr2Z4IE9l for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 19:45:41 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id 604A71F0C5C for <homenet@ietf.org>; Mon, 14 Nov 2011 19:45:29 -0800 (PST)
Received: from [130.129.66.136] (dhcp-4288.meeting.ietf.org [130.129.66.136]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id pAF3isuJ008171 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 14 Nov 2011 19:45:05 -0800 (PST)
Message-ID: <4EC1E035.5060708@isi.edu>
Date: Mon, 14 Nov 2011 19:44:53 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Michael Richardson <mcr@sandelman.ca>
References: <13919.1321321547@marajade.sandelman.ca> <4EC1CEDC.20702@isi.edu> <27059.1321327405@marajade.sandelman.ca>
In-Reply-To: <27059.1321327405@marajade.sandelman.ca>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: homenet <homenet@ietf.org>
Subject: Re: [homenet] secret sharing among devices
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 03:45:42 -0000

On 11/14/2011 7:23 PM, Michael Richardson wrote:
>>>>>> "Joe" == Joe Touch<touch@isi.edu>  writes:
>      >>  There have been various discussion in PHL about spreading a secret among
>      >>  devices so they can authenticate each other.
>      >>
>      >>  A super cool idea is a specifically formatted file on a USB drive,
>      >>  inserted into each system in turn.  While we might be pretty sure
>      >>  the USB drive (and file system and connector, etc.) is out of scope, the
>      >>  format for that secret file might be well in scope
>
>      Joe>  Doesn't that assume the device has a USB connector and can
>      Joe>  mount a stick as a drive? While that's common on PCs, it's not
>      Joe>  on home router boxes AFAICT. Many have no USB at all.
>
> 1) Joe, "the USB drive is out of scope".
>     What matters is that you have some method to get the file into the
>     device. How is less important.

Agreed. That was my primary point.

> 2) a USB port is increasing common on home routers, it's where you plug
>     the printer in, or the 16G key or 1TB disk, as the home router
>     provides NAS as well.

Verizon doesn't include USB ports on their routers. YMMV, but Verizon is 
a fairly large home network provider.

Joe

From palm@broadcom.com  Mon Nov 14 20:13:48 2011
Return-Path: <palm@broadcom.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F47321F8D89 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 20:13:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PE8nRhrVnOyl for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 20:13:47 -0800 (PST)
Received: from mms2.broadcom.com (mms2.broadcom.com [216.31.210.18]) by ietfa.amsl.com (Postfix) with ESMTP id 2564A21F8D8A for <homenet@ietf.org>; Mon, 14 Nov 2011 20:13:47 -0800 (PST)
Received: from [10.9.200.131] by mms2.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Mon, 14 Nov 2011 20:20:23 -0800
X-Server-Uuid: D3C04415-6FA8-4F2C-93C1-920E106A2031
Received: from IRVEXCHCCR01.corp.ad.broadcom.com ([10.252.49.30]) by IRVEXCHHUB01.corp.ad.broadcom.com ([10.9.200.131]) with mapi; Mon, 14 Nov 2011 20:13:02 -0800
From: "Stephen [kiwin] Palm" <palm@broadcom.com>
To: "'touch@isi.edu'" <touch@isi.edu>, "'mcr@sandelman.ca'" <mcr@sandelman.ca>
Date: Mon, 14 Nov 2011 20:13:02 -0800
Thread-Topic: [homenet] secret sharing among devices
Thread-Index: AcyjSROjfA2MypJsQCWFDVVFNBpECAAA8pCc
Message-ID: <D143FF2D6A52E5409FEE8BC1CD3BC54893992FBB97@IRVEXCHCCR01.corp.ad.broadcom.com>
In-Reply-To: <4EC1E035.5060708@isi.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-WSS-ID: 62DF370D3GG1235505-01-01
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "'homenet@ietf.org'" <homenet@ietf.org>
Subject: Re: [homenet] secret sharing among devices
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 04:13:48 -0000

My phone cannot mount usb devices. Have nio interest to remove the sdcard
-------
Stephen [kiwin] Palm   Ph.D.                     W: http://www.kiwin.com
Senior Technical Director                             T: +1-949-926-PALM
           Broadcom - Broadband Communications Group=20


----- Original Message -----
From: Joe Touch [mailto:touch@isi.edu]
Sent: Monday, November 14, 2011 07:44 PM=0A=
To: Michael Richardson <mcr@sandelman.ca>
Cc: homenet <homenet@ietf.org>
Subject: Re: [homenet] secret sharing among devices



On 11/14/2011 7:23 PM, Michael Richardson wrote:
>>>>>> "Joe" =3D=3D Joe Touch<touch@isi.edu>  writes:
>      >>  There have been various discussion in PHL about spreading a secr=
et among
>      >>  devices so they can authenticate each other.
>      >>
>      >>  A super cool idea is a specifically formatted file on a USB driv=
e,
>      >>  inserted into each system in turn.  While we might be pretty sur=
e
>      >>  the USB drive (and file system and connector, etc.) is out of sc=
ope, the
>      >>  format for that secret file might be well in scope
>
>      Joe>  Doesn't that assume the device has a USB connector and can
>      Joe>  mount a stick as a drive? While that's common on PCs, it's not
>      Joe>  on home router boxes AFAICT. Many have no USB at all.
>
> 1) Joe, "the USB drive is out of scope".
>     What matters is that you have some method to get the file into the
>     device. How is less important.

Agreed. That was my primary point.

> 2) a USB port is increasing common on home routers, it's where you plug
>     the printer in, or the 16G key or 1TB disk, as the home router
>     provides NAS as well.

Verizon doesn't include USB ports on their routers. YMMV, but Verizon is=20
a fairly large home network provider.

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



From joelja@bogus.com  Mon Nov 14 20:25:31 2011
Return-Path: <joelja@bogus.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C36A61F0D54 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 20:25:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.479
X-Spam-Level: 
X-Spam-Status: No, score=-102.479 tagged_above=-999 required=5 tests=[AWL=0.120, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CbVAAIpMIh92 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 20:25:31 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 2C0451F0D51 for <homenet@ietf.org>; Mon, 14 Nov 2011 20:25:31 -0800 (PST)
Received: from dhcp-2510.meeting.ietf.org (dhcp-2510.meeting.ietf.org [130.129.37.16]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id pAF4PRLI088970 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Tue, 15 Nov 2011 04:25:28 GMT (envelope-from joelja@bogus.com)
Message-ID: <4EC1E9B5.1020908@bogus.com>
Date: Tue, 15 Nov 2011 12:25:25 +0800
From: Joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: "Stephen [kiwin] Palm" <palm@broadcom.com>
References: <D143FF2D6A52E5409FEE8BC1CD3BC54893992FBB97@IRVEXCHCCR01.corp.ad.broadcom.com>
In-Reply-To: <D143FF2D6A52E5409FEE8BC1CD3BC54893992FBB97@IRVEXCHCCR01.corp.ad.broadcom.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Tue, 15 Nov 2011 04:25:30 +0000 (UTC)
Cc: "'homenet@ietf.org'" <homenet@ietf.org>, "'mcr@sandelman.ca'" <mcr@sandelman.ca>, "'touch@isi.edu'" <touch@isi.edu>
Subject: Re: [homenet] secret sharing among devices
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 04:25:31 -0000

plugging things into things seems like a rather short-sightt requirement
for a relationship.

joel

On 11/15/11 12:13 , Stephen [kiwin] Palm wrote:
> My phone cannot mount usb devices. Have nio interest to remove the sdcard
> -------
> Stephen [kiwin] Palm   Ph.D.                     W: http://www.kiwin.com
> Senior Technical Director                             T: +1-949-926-PALM
>            Broadcom - Broadband Communications Group 
> 
> 
> ----- Original Message -----
> From: Joe Touch [mailto:touch@isi.edu]
> Sent: Monday, November 14, 2011 07:44 PM
> To: Michael Richardson <mcr@sandelman.ca>
> Cc: homenet <homenet@ietf.org>
> Subject: Re: [homenet] secret sharing among devices
> 
> 
> 
> On 11/14/2011 7:23 PM, Michael Richardson wrote:
>>>>>>> "Joe" == Joe Touch<touch@isi.edu>  writes:
>>      >>  There have been various discussion in PHL about spreading a secret among
>>      >>  devices so they can authenticate each other.
>>      >>
>>      >>  A super cool idea is a specifically formatted file on a USB drive,
>>      >>  inserted into each system in turn.  While we might be pretty sure
>>      >>  the USB drive (and file system and connector, etc.) is out of scope, the
>>      >>  format for that secret file might be well in scope
>>
>>      Joe>  Doesn't that assume the device has a USB connector and can
>>      Joe>  mount a stick as a drive? While that's common on PCs, it's not
>>      Joe>  on home router boxes AFAICT. Many have no USB at all.
>>
>> 1) Joe, "the USB drive is out of scope".
>>     What matters is that you have some method to get the file into the
>>     device. How is less important.
> 
> Agreed. That was my primary point.
> 
>> 2) a USB port is increasing common on home routers, it's where you plug
>>     the printer in, or the 16G key or 1TB disk, as the home router
>>     provides NAS as well.
> 
> Verizon doesn't include USB ports on their routers. YMMV, but Verizon is 
> a fairly large home network provider.
> 
> Joe
> _______________________________________________
> 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 diego@tid.es  Mon Nov 14 20:35:53 2011
Return-Path: <diego@tid.es>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD37511E81BB for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 20:35:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.939
X-Spam-Level: 
X-Spam-Status: No, score=-5.939 tagged_above=-999 required=5 tests=[AWL=0.660,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tU5abO-Si9Qf for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 20:35:53 -0800 (PST)
Received: from correo-bck.tid.es (correo-bck.tid.es [195.235.93.200]) by ietfa.amsl.com (Postfix) with ESMTP id D083911E8160 for <homenet@ietf.org>; Mon, 14 Nov 2011 20:35:52 -0800 (PST)
Received: from sbrightmailg02.hi.inet (Sbrightmailg02.hi.inet [10.95.78.105]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LUO003TTQ3R3Y@tid.hi.inet> for homenet@ietf.org; Tue, 15 Nov 2011 05:35:51 +0100 (MET)
Received: from vanvan (vanvan.hi.inet [10.95.78.49])	by sbrightmailg02.hi.inet (Symantec Messaging Gateway) with SMTP id CA.D5.30058.72CE1CE4; Tue, 15 Nov 2011 05:35:51 +0100 (CET)
Received: from correo.tid.es (mailhost.hi.inet [10.95.64.100]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPS id <0LUO006WZQ3QMS@tid.hi.inet> for homenet@ietf.org; Tue, 15 Nov 2011 05:35:51 +0100 (MET)
Received: from EXCLU2K7.hi.inet ([10.95.67.65]) by htcasmad1.hi.inet ([192.168.0.1]) with mapi; Tue, 15 Nov 2011 05:35:50 +0100
Date: Tue, 15 Nov 2011 05:35:49 +0100
From: DIEGO LOPEZ GARCIA <diego@tid.es>
In-reply-to: <4EC1DA91.7070309@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-id: <B82CF845-1129-44F9-9248-858377CC3F90@tid.es>
MIME-version: 1.0
Content-type: text/plain; charset=utf-8
Content-language: en-US
Content-transfer-encoding: base64
Accept-Language: en-US
Thread-topic: [homenet] privacy vs subnet-id
Thread-index: AcyjUA0u3kpWziwUQqOlO6XLRUvTqQ==
acceptlanguage: en-US
X-AuditID: 0a5f4e69-b7f3d6d00000756a-f7-4ec1ec271b5a
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprKKsWRmVeSWpSXmKPExsXCFe9nqKv+5qCfwcn9IhbvFx1icWD0WLLk J1MAYxSXTUpqTmZZapG+XQJXRnfTccaCf3wVXzcdZWpgPMPXxcjJISFgIvG/6wMLhC0mceHe erYuRi4OIYFtjBK3Wz8yQji/GCWurL0GlWlklOj/+YsNpIVFQFXi4KqHjCA2m4C6RMvRb2Cj hAW0JZomvGEFsTkFNCV+TuljBrFFBIwlGrtOg8WZBQIkmnY9BKvnFbCUWHd6DTOELSjxY/I9 oDgHUI26xJQpuRDl4hLNrTdZIGxFiWmLGsDWMgJd/f3UGiaI8ToS3d/2MELYehK3njSyQNSI StxpX88I8aWAxJI955khbFGJl4//sUL8tYxJYt2JqywTGMVnITljFsIZs5CcMQvJGQsYWVYx ihUnFWWmZ5TkJmbmpBsY6WVk6mXmpZZsYoTEUeYOxuU7VQ4xCnAwKvHwngg56CfEmlhWXJl7 iFGSg0lJlPfYU6AQX1J+SmVGYnFGfFFpTmrxIUYJDmYlEd6Ok0A53pTEyqrUonyYlAwHh5IE 78LXQCnBotT01Iq0zBxgsoBJM3FwgrTzALVPAanhLS5IzC3OTIfIn2KUlBLnnQ2SEABJZJTm wfW+YhQHOlKYdxpIlgeY1uC6XgENZAIauPbgAZCBJYkIKakGxsi9X9J2b11gm9Qd+WDvhrMH DblsrTxr6rkE+oxZmI5uNX220TSfyUm7h3drzO7tKc+Lc3YXyP1MK9h2U2mBQrXRT/XilVpr txyPSv9/4u9ZhkjdF7FTIngVH9+ufysYXfRp/ceZWraXau7yyJ0JbDIy1bwTd8Pvp9DmO5mO Sc3fWreYXD87Q4mlOCPRUIu5qDgRAE6JWxcoAwAA
References: <19345.1321323990@marajade.sandelman.ca> <4EC1D42B.7070105@gmail.com> <E5975A2E-6C4F-42A0-A444-4E1902230C95@ecs.soton.ac.uk> <EMEW3|c9a6b972cc64ff8b6185463e28c35a72nAE34x03tjc|ecs.soton.ac.uk|E5975A2E-6C4F-42A0-A444-4E1902230C95@ecs.soton.ac.uk> <4EC1DA91.7070309@gmail.com>
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] privacy vs subnet-id
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 04:35:53 -0000

DQpPbiAxNSBOb3YgMjAxMSwgYXQgMTE6MjAgLCBCcmlhbiBFIENhcnBlbnRlciB3cm90ZToNCg0K
PiBPbiAyMDExLTExLTE1IDE2OjAzLCBUaW0gQ2hvd24gd3JvdGU6DQo+PiBTbyBhdCB0aGUgbW9t
ZW50IGFsbCB0aGUgYXJjaCB0ZXh0IHNheXMgb24gcHJpdmFjeSBpczoNCj4+ICAgUHJpdmFjeSBj
b25zaWRlcmF0aW9ucw0KPj4NCj4+ICAgICAgVGhlcmUgYXJlIG5vIHNwZWNpZmljIHByaXZhY3kg
Y29uY2VybnMgZm9yIHRoaXMgdGV4dC4gIEl0IHNob3VsZA0KPj4gICAgICBiZSBub3RlZCB0aGF0
IG1vc3QgSVNQcyBhcmUgZXhwZWN0ZWQgdG8gb2ZmZXIgc3RhdGljIElQdjYgcHJlZml4ZXMNCj4+
ICAgICAgdG8gY3VzdG9tZXJzLCBhbmQgdGh1cyB0aGUgYWRkcmVzc2VzIHRoZXkgdXNlIHdvdWxk
IG5vdCBnZW5lcmFsbHkNCj4+ICAgICAgY2hhbmdlIG92ZXIgdGltZS4NCj4+IFdoYXQgd291bGQg
eW91IGxpa2UgdG8gc2F5IGhlcmUgaW5zdGVhZD8NCj4NCj4gTWF5YmUgcG9pbnQgb3V0IHRoYXQg
YSBob21lbmV0IGNhbiBiZSBwcm90ZWN0ZWQgYWdhaW5zdCBleHRlcm5hbCBwcml2YWN5DQo+IHRo
cmVhdHMgKHBvc3NpYmx5IGNpdGluZyA0ODY0IGV0YykgYnV0IHRoYXQgd2hhdGV2ZXIgaG9zdHMg
ZG8sIHRoZSBob21lbmV0DQo+IGFkbWluIGhhcyB0aGUgY2FwYWJpbGl0eSB0byBwZXJmb3JtIHRy
YWZmaWMgYW5hbHlzaXMgZG93biB0byB0aGUgc3VibmV0IGxldmVsLg0KPg0KQW5kIEkgdGhpbmsg
aXQgTVVTVCBoYXZlIHRoYXQgY2FwYWJpbGl0eSB0byBhdm9pZCBwcm9ibGVtcyBhcmlzaW5nIGZy
b20gYW55IGFidXNlIG9yaWdpbmF0ZWQgdGhlcmUsIGVzcGVjaWFsbHkgYXQgdGhlIGd1ZXN0IHN1
Ym5ldC4uLg0KDQotLQ0KIkVzdGEgdmV6IG5vIGZhbGxhcmVtb3MsIERvY3RvciBJbmZpZXJubyIN
Cg0KRHIgRGllZ28gUi4gTG9wZXoNClRlbGVmb25pY2EgSStEDQoNCmUtbWFpbDogZGllZ29AdGlk
LmVzDQpUZWw6ICAgICAgKzM0IDkxMyAxMjkgMDQxDQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLQ0KDQoNCg0KDQoNCg0KRXN0ZSBtZW5zYWplIHNlIGRpcmlnZSBleGNs
dXNpdmFtZW50ZSBhIHN1IGRlc3RpbmF0YXJpby4gUHVlZGUgY29uc3VsdGFyIG51ZXN0cmEgcG9s
w610aWNhIGRlIGVudsOtbyB5IHJlY2VwY2nDs24gZGUgY29ycmVvIGVsZWN0csOzbmljbyBlbiBl
bCBlbmxhY2Ugc2l0dWFkbyBtw6FzIGFiYWpvLg0KVGhpcyBtZXNzYWdlIGlzIGludGVuZGVkIGV4
Y2x1c2l2ZWx5IGZvciBpdHMgYWRkcmVzc2VlLiBXZSBvbmx5IHNlbmQgYW5kIHJlY2VpdmUgZW1h
aWwgb24gdGhlIGJhc2lzIG9mIHRoZSB0ZXJtcyBzZXQgb3V0IGF0Lg0KaHR0cDovL3d3dy50aWQu
ZXMvRVMvUEFHSU5BUy9kaXNjbGFpbWVyLmFzcHgNCg==

From mellon@fugue.com  Mon Nov 14 20:41:28 2011
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 074D01F0DB2 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 20:41:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.364
X-Spam-Level: 
X-Spam-Status: No, score=-1.364 tagged_above=-999 required=5 tests=[AWL=-0.161, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zyFOryRtjqRV for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 20:41:27 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id B437D1F0DA9 for <homenet@ietf.org>; Mon, 14 Nov 2011 20:41:27 -0800 (PST)
Received: from [IPv6:2001:df8::80:a96c:13d3:3d2e:e267] (unknown [IPv6:2001:df8:0:80:a96c:13d3:3d2e:e267]) by toccata.fugue.com (Postfix) with ESMTPSA id D27DD2381DF0; Mon, 14 Nov 2011 23:41:26 -0500 (EST)
References: <D143FF2D6A52E5409FEE8BC1CD3BC54893992FBB97@IRVEXCHCCR01.corp.ad.broadcom.com>
From: Ted Lemon <mellon@fugue.com>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <D143FF2D6A52E5409FEE8BC1CD3BC54893992FBB97@IRVEXCHCCR01.corp.ad.broadcom.com>
Message-Id: <4EF04F37-2474-417E-996A-F3AB77F03043@fugue.com>
Date: Tue, 15 Nov 2011 12:24:47 +0800
To: "Stephen [kiwin] Palm" <palm@broadcom.com>
Mime-Version: 1.0 (1.0)
X-Mailer: iPad Mail (9A334)
Cc: "homenet@ietf.org" <homenet@ietf.org>, "mcr@sandelman.ca" <mcr@sandelman.ca>, "touch@isi.edu" <touch@isi.edu>
Subject: Re: [homenet] secret sharing among devices
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 04:41:28 -0000

On Nov 15, 2011, at 12:13 PM, "Stephen [kiwin] Palm" <palm@broadcom.com> wro=
te:
> My phone cannot mount usb devices. Have nio interest to remove the sdcard

Your phone almost certainly has  a USB interface, so actually it's one of th=
e easier devices to configure.  It may be that it will not act as a USB host=
, but that's an easy problem.=20=

From palm@broadcom.com  Mon Nov 14 20:47:13 2011
Return-Path: <palm@broadcom.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73EE921F8CFA for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 20:47:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xmd3SEDUFzBw for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 20:47:12 -0800 (PST)
Received: from mms2.broadcom.com (mms2.broadcom.com [216.31.210.18]) by ietfa.amsl.com (Postfix) with ESMTP id C06F721F8CF7 for <homenet@ietf.org>; Mon, 14 Nov 2011 20:47:12 -0800 (PST)
Received: from [10.9.200.133] by mms2.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Mon, 14 Nov 2011 20:53:48 -0800
X-Server-Uuid: D3C04415-6FA8-4F2C-93C1-920E106A2031
Received: from IRVEXCHCCR01.corp.ad.broadcom.com ([10.252.49.30]) by IRVEXCHHUB02.corp.ad.broadcom.com ([10.9.200.133]) with mapi; Mon, 14 Nov 2011 20:46:00 -0800
From: "Stephen [kiwin] Palm" <palm@broadcom.com>
To: "'mellon@fugue.com'" <mellon@fugue.com>
Date: Mon, 14 Nov 2011 20:46:28 -0800
Thread-Topic: [homenet] secret sharing among devices
Thread-Index: AcyjUOHNIDE5ZhT7T3qBPrWBboh8sAAAKePX
Message-ID: <D143FF2D6A52E5409FEE8BC1CD3BC54893992FBB98@IRVEXCHCCR01.corp.ad.broadcom.com>
In-Reply-To: <4EF04F37-2474-417E-996A-F3AB77F03043@fugue.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-WSS-ID: 62DF2FD63GG1242855-01-01
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "'homenet@ietf.org'" <homenet@ietf.org>, "'mcr@sandelman.ca'" <mcr@sandelman.ca>, "'touch@isi.edu'" <touch@isi.edu>
Subject: Re: [homenet] secret sharing among devices
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 04:47:13 -0000

You miss the point: while phones certainly do have usb device capability - =
today they are not have host and today they do not accept the A connector -=
 so they cannot accept a standard usb thumb drive - and market forces will =
keep it that way.=20
-------
Stephen [kiwin] Palm   Ph.D.                     W: http://www.kiwin.com
Senior Technical Director                             T: +1-949-926-PALM
           Broadcom - Broadband Communications Group=20


----- Original Message -----
From: Ted Lemon [mailto:mellon@fugue.com]
Sent: Monday, November 14, 2011 08:24 PM=0A=
To: Stephen [kiwin] Palm
Cc: touch@isi.edu <touch@isi.edu>; mcr@sandelman.ca <mcr@sandelman.ca>; hom=
enet@ietf.org <homenet@ietf.org>
Subject: Re: [homenet] secret sharing among devices

On Nov 15, 2011, at 12:13 PM, "Stephen [kiwin] Palm" <palm@broadcom.com> wr=
ote:
> My phone cannot mount usb devices. Have nio interest to remove the sdcard

Your phone almost certainly has  a USB interface, so actually it's one of t=
he easier devices to configure.  It may be that it will not act as a USB ho=
st, but that's an easy problem.=20


From palm@broadcom.com  Mon Nov 14 20:48:55 2011
Return-Path: <palm@broadcom.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C7B5011E80EA for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 20:48:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DPzXZFmTsqDO for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 20:48:54 -0800 (PST)
Received: from mms1.broadcom.com (mms1.broadcom.com [216.31.210.17]) by ietfa.amsl.com (Postfix) with ESMTP id CB9F311E8104 for <homenet@ietf.org>; Mon, 14 Nov 2011 20:48:54 -0800 (PST)
Received: from [10.9.200.133] by mms1.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Mon, 14 Nov 2011 20:56:31 -0800
X-Server-Uuid: 02CED230-5797-4B57-9875-D5D2FEE4708A
Received: from IRVEXCHCCR01.corp.ad.broadcom.com ([10.252.49.30]) by IRVEXCHHUB02.corp.ad.broadcom.com ([10.9.200.133]) with mapi; Mon, 14 Nov 2011 20:48:14 -0800
From: "Stephen [kiwin] Palm" <palm@broadcom.com>
To: "'joelja@bogus.com'" <joelja@bogus.com>
Date: Mon, 14 Nov 2011 20:48:42 -0800
Thread-Topic: [homenet] secret sharing among devices
Thread-Index: AcyjTqFgjv1XygHdSay5jc9rMe/zHgAAzfzT
Message-ID: <D143FF2D6A52E5409FEE8BC1CD3BC54893992FBB99@IRVEXCHCCR01.corp.ad.broadcom.com>
In-Reply-To: <4EC1E9B5.1020908@bogus.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-WSS-ID: 62DF2F753JW17534685-01-01
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "'homenet@ietf.org'" <homenet@ietf.org>, "'mcr@sandelman.ca'" <mcr@sandelman.ca>, "'touch@isi.edu'" <touch@isi.edu>
Subject: Re: [homenet] secret sharing among devices
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 04:48:55 -0000

Agreed. Could be wireless or nfc. The file format won't help much if there =
are multiple ways it might (or might not) be transfered=20
-------
Stephen [kiwin] Palm   Ph.D.                     W: http://www.kiwin.com
Senior Technical Director                             T: +1-949-926-PALM
           Broadcom - Broadband Communications Group=20


----- Original Message -----
From: Joel jaeggli [mailto:joelja@bogus.com]
Sent: Monday, November 14, 2011 08:25 PM=0A=
To: Stephen [kiwin] Palm
Cc: 'touch@isi.edu' <touch@isi.edu>; 'mcr@sandelman.ca' <mcr@sandelman.ca>;=
 'homenet@ietf.org' <homenet@ietf.org>
Subject: Re: [homenet] secret sharing among devices

plugging things into things seems like a rather short-sightt requirement
for a relationship.

joel

On 11/15/11 12:13 , Stephen [kiwin] Palm wrote:
> My phone cannot mount usb devices. Have nio interest to remove the sdcard
> -------
> Stephen [kiwin] Palm   Ph.D.                     W: http://www.kiwin.com
> Senior Technical Director                             T: +1-949-926-PALM
>            Broadcom - Broadband Communications Group=20
>=20
>=20
> ----- Original Message -----
> From: Joe Touch [mailto:touch@isi.edu]
> Sent: Monday, November 14, 2011 07:44 PM
> To: Michael Richardson <mcr@sandelman.ca>
> Cc: homenet <homenet@ietf.org>
> Subject: Re: [homenet] secret sharing among devices
>=20
>=20
>=20
> On 11/14/2011 7:23 PM, Michael Richardson wrote:
>>>>>>> "Joe" =3D=3D Joe Touch<touch@isi.edu>  writes:
>>      >>  There have been various discussion in PHL about spreading a sec=
ret among
>>      >>  devices so they can authenticate each other.
>>      >>
>>      >>  A super cool idea is a specifically formatted file on a USB dri=
ve,
>>      >>  inserted into each system in turn.  While we might be pretty su=
re
>>      >>  the USB drive (and file system and connector, etc.) is out of s=
cope, the
>>      >>  format for that secret file might be well in scope
>>
>>      Joe>  Doesn't that assume the device has a USB connector and can
>>      Joe>  mount a stick as a drive? While that's common on PCs, it's no=
t
>>      Joe>  on home router boxes AFAICT. Many have no USB at all.
>>
>> 1) Joe, "the USB drive is out of scope".
>>     What matters is that you have some method to get the file into the
>>     device. How is less important.
>=20
> Agreed. That was my primary point.
>=20
>> 2) a USB port is increasing common on home routers, it's where you plug
>>     the printer in, or the 16G key or 1TB disk, as the home router
>>     provides NAS as well.
>=20
> Verizon doesn't include USB ports on their routers. YMMV, but Verizon is=
=20
> a fairly large home network provider.
>=20
> Joe
> _______________________________________________
> 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
>=20




From touch@isi.edu  Mon Nov 14 20:49:42 2011
Return-Path: <touch@isi.edu>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7EE521F8D12 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 20:49:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.428
X-Spam-Level: 
X-Spam-Status: No, score=-102.428 tagged_above=-999 required=5 tests=[AWL=0.171, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8dzWQ-qyW2qH for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 20:49:42 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id 7F30721F8CFC for <homenet@ietf.org>; Mon, 14 Nov 2011 20:49:42 -0800 (PST)
Received: from [130.129.66.136] (dhcp-4288.meeting.ietf.org [130.129.66.136]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id pAF4n4h9017627 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 14 Nov 2011 20:49:15 -0800 (PST)
Message-ID: <4EC1EF3F.3010507@isi.edu>
Date: Mon, 14 Nov 2011 20:49:03 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Ted Lemon <mellon@fugue.com>
References: <D143FF2D6A52E5409FEE8BC1CD3BC54893992FBB97@IRVEXCHCCR01.corp.ad.broadcom.com> <4EF04F37-2474-417E-996A-F3AB77F03043@fugue.com>
In-Reply-To: <4EF04F37-2474-417E-996A-F3AB77F03043@fugue.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "homenet@ietf.org" <homenet@ietf.org>, "Stephen \[kiwin\] Palm" <palm@broadcom.com>, "mcr@sandelman.ca" <mcr@sandelman.ca>
Subject: Re: [homenet] secret sharing among devices
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 04:49:43 -0000

On 11/14/2011 8:24 PM, Ted Lemon wrote:
> On Nov 15, 2011, at 12:13 PM, "Stephen [kiwin] Palm"<palm@broadcom.com>  wrote:
>> My phone cannot mount usb devices. Have nio interest to remove the sdcard
>
> Your phone almost certainly has  a USB interface, so actually it's one of the easier devices to configure.  It may be that it will not act as a USB host, but that's an easy problem.

Phones are USB clients, not hosts - I don't think a client is required 
to supply power.

Joe

From mellon@fugue.com  Mon Nov 14 21:15:46 2011
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E12721F0DB9 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 21:15:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.831
X-Spam-Level: 
X-Spam-Status: No, score=-0.831 tagged_above=-999 required=5 tests=[AWL=0.372,  BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zkp6gikHF5yH for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 21:15:46 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 63BD91F0D94 for <homenet@ietf.org>; Mon, 14 Nov 2011 21:15:46 -0800 (PST)
Received: from [172.22.13.155] (unknown [122.147.240.7]) by toccata.fugue.com (Postfix) with ESMTPSA id 375982381DBE; Tue, 15 Nov 2011 00:15:45 -0500 (EST)
References: <D143FF2D6A52E5409FEE8BC1CD3BC54893992FBB98@IRVEXCHCCR01.corp.ad.broadcom.com>
In-Reply-To: <D143FF2D6A52E5409FEE8BC1CD3BC54893992FBB98@IRVEXCHCCR01.corp.ad.broadcom.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <958CCC88-A01D-49FA-9E83-123E62DFAD24@fugue.com>
X-Mailer: iPad Mail (9A334)
From: Ted Lemon <mellon@fugue.com>
Date: Tue, 15 Nov 2011 13:16:12 +0800
To: "Stephen [kiwin] Palm" <palm@broadcom.com>
Cc: "homenet@ietf.org" <homenet@ietf.org>, "mcr@sandelman.ca" <mcr@sandelman.ca>, "touch@isi.edu" <touch@isi.edu>
Subject: Re: [homenet] secret sharing among devices
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 05:15:47 -0000

On Nov 15, 2011, at 12:46 PM, "Stephen [kiwin] Palm" <palm@broadcom.com> wro=
te:
> You miss the point: while phones certainly do have usb device capability -=
 today they are not have host and today they do not accept the A connector -=
 so they cannot accept a standard usb thumb drive - and market forces will k=
eep it that way.

No I didn't miss the point, please don't assume I am stupid.   Your phone ha=
s a USB device.   Therefore there is a physical medium of exchange for the f=
ile we are talking about.   True, the medium of exchange is not a thumb driv=
e, but it could be for example that you plug your phone *in* to your router,=
 or something.   We are talking about what the file would look like, not how=
 the devices are connected.=

From mellon@fugue.com  Mon Nov 14 21:19:30 2011
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 305E611E815C for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 21:19:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.905
X-Spam-Level: 
X-Spam-Status: No, score=-0.905 tagged_above=-999 required=5 tests=[AWL=0.298,  BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nIJ4hKNEtyxg for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 21:19:29 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id C8B6311E80F2 for <homenet@ietf.org>; Mon, 14 Nov 2011 21:19:29 -0800 (PST)
Received: from [172.22.13.155] (unknown [122.147.240.7]) by toccata.fugue.com (Postfix) with ESMTPSA id D309F2381DBE; Tue, 15 Nov 2011 00:19:28 -0500 (EST)
References: <D143FF2D6A52E5409FEE8BC1CD3BC54893992FBB97@IRVEXCHCCR01.corp.ad.broadcom.com> <4EC1E9B5.1020908@bogus.com>
In-Reply-To: <4EC1E9B5.1020908@bogus.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <5100D13B-B2CD-48C8-A829-8AFDB9100EAF@fugue.com>
X-Mailer: iPad Mail (9A334)
From: Ted Lemon <mellon@fugue.com>
Date: Tue, 15 Nov 2011 13:19:56 +0800
To: Joel jaeggli <joelja@bogus.com>
Cc: "homenet@ietf.org" <homenet@ietf.org>, "Stephen \[kiwin\] Palm" <palm@broadcom.com>, "mcr@sandelman.ca" <mcr@sandelman.ca>, "touch@isi.edu" <touch@isi.edu>
Subject: Re: [homenet] secret sharing among devices
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 05:19:30 -0000

On Nov 15, 2011, at 12:25 PM, Joel jaeggli <joelja@bogus.com> wrote:
> plugging things into things seems like a rather short-sightt requirement
> for a relationship.

I will resist the obvious rejoinder.  And no, it is not short-sighted.   Ass=
uming that physical user interfaces are likely to become obsolete in favor o=
f something else is simply not consistent with reality.   Physical UIs are e=
asy to understand.   Making someone go to a configuration page on your route=
r is hard to understand.   I think in fact that one of the reasons we fail i=
n security on the Internet is precisely that we fail to understand how peopl=
e interact with UIs, and design protocols that require UIs with which most p=
eople cannot successfully interact.


From mellon@fugue.com  Mon Nov 14 21:21:05 2011
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE21211E821E for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 21:21:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.955
X-Spam-Level: 
X-Spam-Status: No, score=-0.955 tagged_above=-999 required=5 tests=[AWL=0.248,  BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dOlCx5i87iQb for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 21:21:03 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 2872011E8234 for <homenet@ietf.org>; Mon, 14 Nov 2011 21:20:58 -0800 (PST)
Received: from [172.22.13.155] (unknown [122.147.240.7]) by toccata.fugue.com (Postfix) with ESMTPSA id 6CA572381DBE; Tue, 15 Nov 2011 00:20:54 -0500 (EST)
References: <D143FF2D6A52E5409FEE8BC1CD3BC54893992FBB97@IRVEXCHCCR01.corp.ad.broadcom.com> <4EF04F37-2474-417E-996A-F3AB77F03043@fugue.com> <4EC1EF3F.3010507@isi.edu>
In-Reply-To: <4EC1EF3F.3010507@isi.edu>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <0E496C1B-7304-452F-AB72-4BC46AE7D026@fugue.com>
X-Mailer: iPad Mail (9A334)
From: Ted Lemon <mellon@fugue.com>
Date: Tue, 15 Nov 2011 13:21:22 +0800
To: Joe Touch <touch@isi.edu>
Cc: "homenet@ietf.org" <homenet@ietf.org>, "Stephen \[kiwin\] Palm" <palm@broadcom.com>, "mcr@sandelman.ca" <mcr@sandelman.ca>
Subject: Re: [homenet] secret sharing among devices
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 05:21:05 -0000

On Nov 15, 2011, at 12:49 PM, Joe Touch <touch@isi.edu> wrote:
> Phones are USB clients, not hosts - I don't think a client is required to s=
upply power.

Right, which means you have to plug it into a USB host device.   What's your=
 point?


From touch@isi.edu  Mon Nov 14 21:21:29 2011
Return-Path: <touch@isi.edu>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A87611E8221 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 21:21:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.466
X-Spam-Level: 
X-Spam-Status: No, score=-104.466 tagged_above=-999 required=5 tests=[AWL=2.133, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id opqeowzMpiNM for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 21:21:28 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 3A3CE11E80F2 for <homenet@ietf.org>; Mon, 14 Nov 2011 21:21:25 -0800 (PST)
Received: from [130.129.66.136] (dhcp-4288.meeting.ietf.org [130.129.66.136]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id pAF5KB32028749 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 14 Nov 2011 21:20:21 -0800 (PST)
Message-ID: <4EC1F689.9010401@isi.edu>
Date: Mon, 14 Nov 2011 21:20:09 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Ted Lemon <mellon@fugue.com>
References: <D143FF2D6A52E5409FEE8BC1CD3BC54893992FBB98@IRVEXCHCCR01.corp.ad.broadcom.com> <958CCC88-A01D-49FA-9E83-123E62DFAD24@fugue.com>
In-Reply-To: <958CCC88-A01D-49FA-9E83-123E62DFAD24@fugue.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "homenet@ietf.org" <homenet@ietf.org>, "Stephen \[kiwin\] Palm" <palm@broadcom.com>, "mcr@sandelman.ca" <mcr@sandelman.ca>
Subject: Re: [homenet] secret sharing among devices
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 05:21:29 -0000

On 11/14/2011 9:16 PM, Ted Lemon wrote:
> On Nov 15, 2011, at 12:46 PM, "Stephen [kiwin] Palm"<palm@broadcom.com>  wrote:
>> You miss the point: while phones certainly do have usb device capability - today they are not have host and today they do not accept the A connector - so they cannot accept a standard usb thumb drive - and market forces will keep it that way.
>
> No I didn't miss the point, please don't assume I am stupid. Your
> phone has a USB device. Therefore there is a physical medium of exchange
> for the file we are talking about. True, the medium of exchange is not a
> thumb drive, but it could be for example that you plug your phone *in*
> to your router, or something. We are talking about what the file would
> look like, not how the devices are connected.

I see - you are presuming the phone acts as the thumb drive.

I think we're thinking the phone is the router (ala tethering). In that 
case, there needs to be a way to plug the USB stick into the phone, 
which can't happen (since the phone draws power off the USB, rather than 
delivering it). If the USB were self-powered, it *might* work, but I've 
never seen such a thing.

Joe


From palm@broadcom.com  Mon Nov 14 21:27:43 2011
Return-Path: <palm@broadcom.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E946511E80F2 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 21:27:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hzbnvWXuyVfq for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 21:27:40 -0800 (PST)
Received: from mms1.broadcom.com (mms1.broadcom.com [216.31.210.17]) by ietfa.amsl.com (Postfix) with ESMTP id 78FE511E8073 for <homenet@ietf.org>; Mon, 14 Nov 2011 21:27:40 -0800 (PST)
Received: from [10.9.200.133] by mms1.broadcom.com with ESMTP (Broadcom SMTP Relay (Email Firewall v6.3.2)); Mon, 14 Nov 2011 21:35:17 -0800
X-Server-Uuid: 02CED230-5797-4B57-9875-D5D2FEE4708A
Received: from mail-irva-13.broadcom.com (10.11.16.103) by IRVEXCHHUB02.corp.ad.broadcom.com (10.9.200.133) with Microsoft SMTP Server id 8.2.247.2; Mon, 14 Nov 2011 21:26:59 -0800
Received: from [10.9.254.240] (unknown [10.9.254.240]) by mail-irva-13.broadcom.com (Postfix) with ESMTP id 4956ABC395; Mon, 14 Nov 2011 21:27:27 -0800 (PST)
Message-ID: <4EC1F83E.6060300@broadcom.com>
Date: Mon, 14 Nov 2011 21:27:26 -0800
From: "Stephen [kiwin] PALM" <palm@broadcom.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.24) Gecko/20111103 Lightning/1.0b2 Thunderbird/3.1.16
MIME-Version: 1.0
To: "Ted Lemon" <mellon@fugue.com>
References: <D143FF2D6A52E5409FEE8BC1CD3BC54893992FBB98@IRVEXCHCCR01.corp.ad.broadcom.com> <958CCC88-A01D-49FA-9E83-123E62DFAD24@fugue.com>
In-Reply-To: <958CCC88-A01D-49FA-9E83-123E62DFAD24@fugue.com>
X-WSS-ID: 62DF259F3JW17542871-01-01
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "homenet@ietf.org" <homenet@ietf.org>, "mcr@sandelman.ca" <mcr@sandelman.ca>, "touch@isi.edu" <touch@isi.edu>
Subject: Re: [homenet] secret sharing among devices
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 05:27:44 -0000

On 11/14/2011 9:16 PM, Ted Lemon wrote:
> On Nov 15, 2011, at 12:46 PM, "Stephen [kiwin] Palm"<palm@broadcom.com>  wrote:
>> You miss the point: while phones certainly do have usb device capability - today they are not have host and today they do not accept the A connector - so they cannot accept a standard usb thumb drive - and market forces will keep it that way.
>
> No I didn't miss the point, please don't assume I am stupid.

but many users essentially are!

 > We are talking about what the file would look like, not how the devices are connected.

How the devices connect is an essential part of the user interaction.
If we ask users or manufacturers to do something unnatural - they won't


From mellon@fugue.com  Mon Nov 14 21:32:01 2011
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90BE121F8E2E for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 21:32:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.99
X-Spam-Level: 
X-Spam-Status: No, score=-0.99 tagged_above=-999 required=5 tests=[AWL=0.213,  BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QeCrC4VKdefK for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 21:32:00 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id BCF2121F84A9 for <homenet@ietf.org>; Mon, 14 Nov 2011 21:31:59 -0800 (PST)
Received: from [172.22.13.155] (unknown [122.147.240.7]) by toccata.fugue.com (Postfix) with ESMTPSA id D44162381DBE; Tue, 15 Nov 2011 00:31:55 -0500 (EST)
References: <D143FF2D6A52E5409FEE8BC1CD3BC54893992FBB98@IRVEXCHCCR01.corp.ad.broadcom.com> <958CCC88-A01D-49FA-9E83-123E62DFAD24@fugue.com> <4EC1F689.9010401@isi.edu>
In-Reply-To: <4EC1F689.9010401@isi.edu>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <9FDD02CF-065C-4985-89DB-0B7A69579837@fugue.com>
X-Mailer: iPad Mail (9A334)
From: Ted Lemon <mellon@fugue.com>
Date: Tue, 15 Nov 2011 13:32:23 +0800
To: Joe Touch <touch@isi.edu>
Cc: "homenet@ietf.org" <homenet@ietf.org>, "Stephen \[kiwin\] Palm" <palm@broadcom.com>, "mcr@sandelman.ca" <mcr@sandelman.ca>
Subject: Re: [homenet] secret sharing among devices
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 05:32:01 -0000

On Nov 15, 2011, at 1:20 PM, Joe Touch <touch@isi.edu> wrote:
> I think we're thinking the phone is the router (ala tethering). In that ca=
se, there needs to be a way to plug the USB stick into the phone, which can'=
t happen (since the phone draws power off the USB, rather than delivering it=
). If the USB were self-powered, it *might* work, but I've never seen such a=
 thing.

That would be pretty cool, but that's not what I'm talking about.   The reas=
on we are not saying "thumb drive" is because it may not be the right medium=
 of exchange.   It's a good example of a viable medium of exchange, but it's=
 certainly not the only possible one.   I would expect each device to have a=
 copy of the file that's on the thumb drive.   If your device is not a USB h=
ost, you would plug it into a device that is a USB host, and the file exchan=
ge would proceed.

It's also possible that it might make sense to use some other medium of exch=
ange that's not USB at all.   For example, routers with ethernet ports can s=
imply be connected together, and there you have a physical link.   But for a=
 wireless device with no ethernet ports, that's not an option.


From mellon@fugue.com  Mon Nov 14 21:33:01 2011
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E9F911E8253 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 21:33:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.017
X-Spam-Level: 
X-Spam-Status: No, score=-1.017 tagged_above=-999 required=5 tests=[AWL=0.186,  BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ztjXkCw1wHwp for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 21:33:01 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 9934011E80C4 for <homenet@ietf.org>; Mon, 14 Nov 2011 21:33:00 -0800 (PST)
Received: from [172.22.13.155] (unknown [122.147.240.7]) by toccata.fugue.com (Postfix) with ESMTPSA id 24DDB2381DBE; Tue, 15 Nov 2011 00:32:59 -0500 (EST)
References: <D143FF2D6A52E5409FEE8BC1CD3BC54893992FBB98@IRVEXCHCCR01.corp.ad.broadcom.com> <958CCC88-A01D-49FA-9E83-123E62DFAD24@fugue.com> <4EC1F83E.6060300@broadcom.com>
In-Reply-To: <4EC1F83E.6060300@broadcom.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <B9D9EFDA-1537-4632-BD93-0D1547F086DB@fugue.com>
X-Mailer: iPad Mail (9A334)
From: Ted Lemon <mellon@fugue.com>
Date: Tue, 15 Nov 2011 13:33:25 +0800
To: "Stephen [kiwin] PALM" <palm@broadcom.com>
Cc: "homenet@ietf.org" <homenet@ietf.org>, "mcr@sandelman.ca" <mcr@sandelman.ca>, "touch@isi.edu" <touch@isi.edu>
Subject: Re: [homenet] secret sharing among devices
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 05:33:01 -0000

On Nov 15, 2011, at 1:27 PM, "Stephen [kiwin] PALM" <palm@broadcom.com> wrot=
e:
> How the devices connect is an essential part of the user interaction.
> If we ask users or manufacturers to do something unnatural - they won't

Oh yes, we are in violent agreement on this point!


From lorenzo@google.com  Mon Nov 14 21:42:25 2011
Return-Path: <lorenzo@google.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A0F921F8BAD for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 21:42:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.858
X-Spam-Level: 
X-Spam-Status: No, score=-102.858 tagged_above=-999 required=5 tests=[AWL=0.117, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 01l8lj03dqDy for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 21:42:24 -0800 (PST)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id A5C3421F8BAC for <homenet@ietf.org>; Mon, 14 Nov 2011 21:42:24 -0800 (PST)
Received: by ggnr5 with SMTP id r5so2015569ggn.31 for <homenet@ietf.org>; Mon, 14 Nov 2011 21:42:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-system-of-record; bh=5cbD1akSqtgcV/Fv8uKez+MYUjuThi0I8rRMASPgCfY=; b=k/BQdSjgP7oBxLqKCPnxTooIFNLgknCaujzIvZ7PaUUZTG4pCXshtPF1khSw8fUUoH j7G6TKqhGkDJENM0pRxA==
Received: by 10.101.85.2 with SMTP id n2mr4633361anl.95.1321335744278; Mon, 14 Nov 2011 21:42:24 -0800 (PST)
Received: by 10.101.85.2 with SMTP id n2mr4633355anl.95.1321335744134; Mon, 14 Nov 2011 21:42:24 -0800 (PST)
MIME-Version: 1.0
Received: by 10.150.202.14 with HTTP; Mon, 14 Nov 2011 21:42:03 -0800 (PST)
In-Reply-To: <4EC1C386.6010802@gmail.com>
References: <4EC1C386.6010802@gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Tue, 15 Nov 2011 13:42:03 +0800
Message-ID: <CAKD1Yr02-uj28JnMnNeFPc-nUYGpp-fobZW7wSY_3WTGH0DaBQ@mail.gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=001636ed738aa8804c04b1bf7304
X-System-Of-Record: true
Cc: homenet@ietf.org, Hans Liu <Hans_Liu@dlink.com.tw>
Subject: Re: [homenet] pervasive v4
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 05:42:25 -0000

--001636ed738aa8804c04b1bf7304
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Nov 15, 2011 at 09:42, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> If homenet is going to support arbitrary self-configuring topologies,
> and pervasive legacy IPv4 is required, we'd surely end up recommending
> NAT444-within-the-home as the only remotely practicable approach.


Hans from D-Link suggests that another option is simply to bridge IPv4
packets and route IPv6 packets.

--001636ed738aa8804c04b1bf7304
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div class=3D"gmail_quote">On Tue, Nov 15, 2011 at 09:42, Brian E Carpenter=
 <span dir=3D"ltr">&lt;<a href=3D"mailto:brian.e.carpenter@gmail.com">brian=
.e.carpenter@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex;">

If homenet is going to support arbitrary self-configuring topologies,<br>
and pervasive legacy IPv4 is required, we&#39;d surely end up recommending<=
br>
NAT444-within-the-home as the only remotely practicable approach.</blockquo=
te><div><br></div><div><span style=3D"background-color: transparent; ">Hans=
 from D-Link suggests that another option is simply to bridge IPv4 packets =
and route IPv6 packets.</span></div>

</div>

--001636ed738aa8804c04b1bf7304--

From lee.howard@twcable.com  Mon Nov 14 21:42:49 2011
Return-Path: <lee.howard@twcable.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 02E4B1F0CC6 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 21:42:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.2
X-Spam-Level: 
X-Spam-Status: No, score=-1.2 tagged_above=-999 required=5 tests=[AWL=0.263, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 64T2O1cEc8Nb for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 21:42:48 -0800 (PST)
Received: from cdpipgw01.twcable.com (cdpipgw01.twcable.com [165.237.59.22]) by ietfa.amsl.com (Postfix) with ESMTP id 0A1731F0CB5 for <homenet@ietf.org>; Mon, 14 Nov 2011 21:42:47 -0800 (PST)
X-SENDER-IP: 10.136.163.11
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.69,512,1315195200"; d="scan'208";a="297416820"
Received: from unknown (HELO PRVPEXHUB02.corp.twcable.com) ([10.136.163.11]) by cdpipgw01.twcable.com with ESMTP/TLS/RC4-MD5; 15 Nov 2011 00:38:18 -0500
Received: from PRVPEXVS03.corp.twcable.com ([10.136.163.26]) by PRVPEXHUB02.corp.twcable.com ([10.136.163.11]) with mapi; Tue, 15 Nov 2011 00:42:46 -0500
From: "Howard, Lee" <lee.howard@twcable.com>
To: Ted Lemon <mellon@fugue.com>
Date: Tue, 15 Nov 2011 00:42:45 -0500
Thread-Topic: [homenet] secret sharing among devices
Thread-Index: AcyjWWcZtdOBHejKQkKI6tbEUNLDTg==
Message-ID: <ED4C6FF5-8D9E-4790-A4B1-3164791B24E0@twcable.com>
References: <13919.1321321547@marajade.sandelman.ca> <4EC1CEDC.20702@isi.edu>	<A38099B4-7759-4DD3-92D1-5C6729B445DA@fugue.com> <4EC1D2C6.3020502@gmail.com> <6B3A3374-AC8B-49F1-BEBE-46CA3E795874@fugue.com>
In-Reply-To: <6B3A3374-AC8B-49F1-BEBE-46CA3E795874@fugue.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: homenet <homenet@ietf.org>, Joe Touch <touch@isi.edu>, Rene Struik <rstruik.ext@gmail.com>, Michael Richardson <mcr@sandelman.ca>
Subject: Re: [homenet] secret sharing among devices
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 05:42:49 -0000

On Nov 15, 2011, at 10:55 AM, Ted Lemon wrote:

> On Nov 15, 2011, at 10:47 AM, Rene Struik <rstruik.ext@gmail.com> wrote:
>> Could you elaborate about the security services and deployment
>> scenario(s) you wish to facilitate, for the benefit of those not at
>> IETF-82 who subscribe to the mailing list? In other words, what is the
>> problem one tries and solve here?
>
> We do not want, for example, for devices that aren't supposed to be route=
rs to be routers.   By doing a manual key exchange, we can ensure that only=
 devices that are intended to be part of the network topology have the keys=
 that are required to join the routing infrastructure.


How do we explain to "the typical home user" what a router is, how to decid=
e whether a given thing is one, and how to (in all cases) get the Magic Key=
 onto it?  In other words, when you say "are intended," who is doing the in=
tending?

Lee

This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

From joelja@bogus.com  Mon Nov 14 21:44:17 2011
Return-Path: <joelja@bogus.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 830B611E809C for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 21:44:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.499
X-Spam-Level: 
X-Spam-Status: No, score=-102.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nxVRlvWq7Pyb for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 21:44:16 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id CAAE411E8085 for <homenet@ietf.org>; Mon, 14 Nov 2011 21:44:16 -0800 (PST)
Received: from dhcp-2510.meeting.ietf.org (dhcp-2510.meeting.ietf.org [130.129.37.16]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id pAF5hxCn090537 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Tue, 15 Nov 2011 05:44:01 GMT (envelope-from joelja@bogus.com)
Message-ID: <4EC1FC1C.9090208@bogus.com>
Date: Tue, 15 Nov 2011 13:43:56 +0800
From: Joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Ted Lemon <mellon@fugue.com>
References: <D143FF2D6A52E5409FEE8BC1CD3BC54893992FBB97@IRVEXCHCCR01.corp.ad.broadcom.com> <4EC1E9B5.1020908@bogus.com> <5100D13B-B2CD-48C8-A829-8AFDB9100EAF@fugue.com>
In-Reply-To: <5100D13B-B2CD-48C8-A829-8AFDB9100EAF@fugue.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Tue, 15 Nov 2011 05:44:03 +0000 (UTC)
Cc: "homenet@ietf.org" <homenet@ietf.org>, "Stephen \[kiwin\] Palm" <palm@broadcom.com>, "mcr@sandelman.ca" <mcr@sandelman.ca>, "touch@isi.edu" <touch@isi.edu>
Subject: Re: [homenet] secret sharing among devices
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 05:44:17 -0000

On 11/15/11 13:19 , Ted Lemon wrote:
> On Nov 15, 2011, at 12:25 PM, Joel jaeggli <joelja@bogus.com> wrote:
>> plugging things into things seems like a rather short-sightt
>> requirement for a relationship.
> 
> I will resist the obvious rejoinder.  And no, it is not
> short-sighted.   Assuming that physical user interfaces are likely to
> become obsolete in favor of something else is simply not consistent
> with reality. 

A decade and a half worth of bluetooth security associations including
really bad ones says otherwise.

Personal devices by in large are shedding data-ports where possible and
especially for low speed interaction.

> Physical UIs are easy to understand.   Making someone
> go to a configuration page on your router is hard to understand. 

And I see that as a usable outcome, as rather unlikely.

>  I
> think in fact that one of the reasons we fail in security on the
> Internet is precisely that we fail to understand how people interact
> with UIs, and design protocols that require UIs with which most
> people cannot successfully interact.

As a consumer I want to bring the thing home, turn it on, and have it work.


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


From marka@isc.org  Mon Nov 14 21:45:51 2011
Return-Path: <marka@isc.org>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BA371F0CB5 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 21:45:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[AWL=0.164,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Am60nviXG-LC for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 21:45:35 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id BB8FC1F0C49 for <homenet@ietf.org>; Mon, 14 Nov 2011 21:45:33 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "bikeshed.isc.org", Issuer "ISC CA" (verified OK)) by mx.ams1.isc.org (Postfix) with ESMTPS id 76DBD5F98E1; Tue, 15 Nov 2011 05:45:18 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:6233:4bff:fe01:7585]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id 5AEB7216C6D; Tue, 15 Nov 2011 05:44:46 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id E839817334CE; Tue, 15 Nov 2011 16:44:40 +1100 (EST)
To: Joe Touch <touch@isi.edu>
From: Mark Andrews <marka@isc.org>
References: <D143FF2D6A52E5409FEE8BC1CD3BC54893992FBB98@IRVEXCHCCR01.corp.ad.broadcom.com> <958CCC88-A01D-49FA-9E83-123E62DFAD24@fugue.com> <4EC1F689.9010401@isi.edu>
In-reply-to: Your message of "Mon, 14 Nov 2011 21:20:09 -0800." <4EC1F689.9010401@isi.edu>
Date: Tue, 15 Nov 2011 16:44:40 +1100
Message-Id: <20111115054440.E839817334CE@drugs.dv.isc.org>
Cc: "homenet@ietf.org" <homenet@ietf.org>, "Stephen \[kiwin\] Palm" <palm@broadcom.com>, Ted Lemon <mellon@fugue.com>, "mcr@sandelman.ca" <mcr@sandelman.ca>
Subject: Re: [homenet] secret sharing among devices
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 05:45:55 -0000

In message <4EC1F689.9010401@isi.edu>, Joe Touch writes:
> 
> 
> On 11/14/2011 9:16 PM, Ted Lemon wrote:
> > On Nov 15, 2011, at 12:46 PM, "Stephen [kiwin] Palm"<palm@broadcom.com>  wrote:
> >> You miss the point: while phones certainly do have usb device capability - today they are 
> not have host and today they do not accept the A connector - so they cannot accept a standard
>  usb thumb drive - and market forces will keep it that way.
> >
> > No I didn't miss the point, please don't assume I am stupid. Your
> > phone has a USB device. Therefore there is a physical medium of exchange
> > for the file we are talking about. True, the medium of exchange is not a
> > thumb drive, but it could be for example that you plug your phone *in*
> > to your router, or something. We are talking about what the file would
> > look like, not how the devices are connected.
> 
> I see - you are presuming the phone acts as the thumb drive.
> 
> I think we're thinking the phone is the router (ala tethering). In that 
> case, there needs to be a way to plug the USB stick into the phone, 
> which can't happen (since the phone draws power off the USB, rather than 
> delivering it). If the USB were self-powered, it *might* work, but I've 
> never seen such a thing.
> 
> Joe

It really doesn't matter what it is.

A MicroSD card would be fine for this.  Lots of cell phones already
have MicroSD slots.  The MicroSD card can be put in a USB card
reader for USB based machines possibly using a SD card adaptor.  A
MicroSD card can be put in a SD card adaptor for SD based devices.

Pop the existing card out of the phone.  Plug it into a card reader
and that into the router.  The router updates the key ring.  You
plug the SD card back into the phone and the phone and router can
now play.

Mark
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org

From lorenzo@google.com  Mon Nov 14 21:49:32 2011
Return-Path: <lorenzo@google.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FC7521F8CAC for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 21:49:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.87
X-Spam-Level: 
X-Spam-Status: No, score=-102.87 tagged_above=-999 required=5 tests=[AWL=0.106, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tvg5xwZbhwJ9 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 21:49:31 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 4BE1421F8E3C for <homenet@ietf.org>; Mon, 14 Nov 2011 21:49:31 -0800 (PST)
Received: by ywt34 with SMTP id 34so5784783ywt.31 for <homenet@ietf.org>; Mon, 14 Nov 2011 21:49:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-system-of-record; bh=NTU5MNMjnxJi8OUEO9xi8SgvS5JOgkBgNcJMI08kO34=; b=hDrOPwYoOMiQZLruTBy8WDb6/67+i0SMyoxITQJ6RxrsEPVHx2hsKQN4slq8sRCRjq TFVsiE62Jzd2ca0RKCDA==
Received: by 10.101.139.15 with SMTP id r15mr7491193ann.161.1321336168296; Mon, 14 Nov 2011 21:49:28 -0800 (PST)
Received: by 10.101.139.15 with SMTP id r15mr7491183ann.161.1321336168155; Mon, 14 Nov 2011 21:49:28 -0800 (PST)
MIME-Version: 1.0
Received: by 10.150.202.14 with HTTP; Mon, 14 Nov 2011 21:49:07 -0800 (PST)
In-Reply-To: <4EC1D6C9.3030107@cisco.com>
References: <4EC1C386.6010802@gmail.com> <4EC1C566.2060400@cisco.com> <4EC1CC2E.30209@gmail.com> <4EC1D6C9.3030107@cisco.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Tue, 15 Nov 2011 13:49:07 +0800
Message-ID: <CAKD1Yr3rFJonkJ1CbCgGPpr-WDj1RFmR6q4jDab1Toc0tJJodg@mail.gmail.com>
To: Erik Nordmark <nordmark@cisco.com>
Content-Type: multipart/alternative; boundary=0016e68e7f8bee8b8804b1bf8cba
X-System-Of-Record: true
Cc: homenet@ietf.org
Subject: Re: [homenet] pervasive v4
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 05:49:32 -0000

--0016e68e7f8bee8b8804b1bf8cba
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Nov 15, 2011 at 11:04, Erik Nordmark <nordmark@cisco.com> wrote:

> On 11/14/11 6:19 PM, Brian E Carpenter wrote:
>
>> Yes, but then we're extending v4 and expecting homenets to run
>> (presumably) RIP.
>>
>
> Why RIP? Same protocol between the home routers as we will pick for
> routing IPv6 in the home.


The primitives you have to configure and renumber IPv6 hosts (multiple
addresses, multiple RAs and address deprecation, and so on) are different
from the ones we have in IPv4 (essentially, DHCPv4 and NAT).

So I don't think we will be able to take what we do in IPv6 and apply it
as-is to IPv4. Instead, I think we'll have to either NAT everywhere (like
we do today) or bridge everywhere.

--0016e68e7f8bee8b8804b1bf8cba
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div class=3D"gmail_quote">On Tue, Nov 15, 2011 at 11:04, Erik Nordmark <sp=
an dir=3D"ltr">&lt;<a href=3D"mailto:nordmark@cisco.com">nordmark@cisco.com=
</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">

<div class=3D"im">On 11/14/11 6:19 PM, Brian E Carpenter wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Yes, but then we&#39;re extending v4 and expecting homenets to run (presuma=
bly) RIP.<br>
</blockquote>
<br></div>
Why RIP? Same protocol between the home routers as we will pick for routing=
 IPv6 in the home.</blockquote><div><br></div><div>The primitives you have =
to configure and renumber IPv6 hosts (multiple addresses, multiple RAs and =
address deprecation, and so on) are different from the ones we have in IPv4=
 (essentially, DHCPv4 and NAT).</div>

<div><span style=3D"background-color: transparent; "><br></span></div><div>=
<span style=3D"background-color: transparent; ">So I don&#39;t think we wil=
l be able to take what we do in IPv6 and apply it as-is to IPv4. Instead, I=
 think we&#39;ll have to either=A0</span><span style=3D"background-color: t=
ransparent; ">NAT everywhere (like we do today) or bridge everywhere.</span=
></div>

</div>

--0016e68e7f8bee8b8804b1bf8cba--

From touch@isi.edu  Mon Nov 14 21:58:44 2011
Return-Path: <touch@isi.edu>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ADB1711E816F for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 21:58:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.679
X-Spam-Level: 
X-Spam-Status: No, score=-104.679 tagged_above=-999 required=5 tests=[AWL=1.920, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z+jY332TMm0W for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 21:58:43 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 7161211E811B for <homenet@ietf.org>; Mon, 14 Nov 2011 21:58:42 -0800 (PST)
Received: from [130.129.66.136] (dhcp-4288.meeting.ietf.org [130.129.66.136]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id pAF5vhcf004941 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 14 Nov 2011 21:57:54 -0800 (PST)
Message-ID: <4EC1FF56.9050202@isi.edu>
Date: Mon, 14 Nov 2011 21:57:42 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Mark Andrews <marka@isc.org>
References: <D143FF2D6A52E5409FEE8BC1CD3BC54893992FBB98@IRVEXCHCCR01.corp.ad.broadcom.com> <958CCC88-A01D-49FA-9E83-123E62DFAD24@fugue.com> <4EC1F689.9010401@isi.edu> <20111115054440.E839817334CE@drugs.dv.isc.org>
In-Reply-To: <20111115054440.E839817334CE@drugs.dv.isc.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "homenet@ietf.org" <homenet@ietf.org>, "Stephen \[kiwin\] Palm" <palm@broadcom.com>, Ted Lemon <mellon@fugue.com>, "mcr@sandelman.ca" <mcr@sandelman.ca>
Subject: Re: [homenet] secret sharing among devices
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 05:58:44 -0000

On 11/14/2011 9:44 PM, Mark Andrews wrote:
...
>> I think we're thinking the phone is the router (ala tethering). In that
>> case, there needs to be a way to plug the USB stick into the phone,
>> which can't happen (since the phone draws power off the USB, rather than
>> delivering it). If the USB were self-powered, it *might* work, but I've
>> never seen such a thing.
>>
>> Joe
>
> It really doesn't matter what it is.
>
> A MicroSD card would be fine for this.  Lots of cell phones already
> have MicroSD slots.

Not iPhones ;-)

I agree with Joel - Bluetooth is fine too. But the broader point is not 
to get hung up on the method of file transfer, but rather the info in 
the file.

Joe

From joelja@bogus.com  Mon Nov 14 21:58:58 2011
Return-Path: <joelja@bogus.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7EDA711E81EA for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 21:58:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.513
X-Spam-Level: 
X-Spam-Status: No, score=-102.513 tagged_above=-999 required=5 tests=[AWL=0.086, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WucxdKg4-iNM for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 21:58:57 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 8F80411E81D5 for <homenet@ietf.org>; Mon, 14 Nov 2011 21:58:57 -0800 (PST)
Received: from dhcp-2510.meeting.ietf.org (dhcp-2510.meeting.ietf.org [130.129.37.16]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id pAF5wpl2090830 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Tue, 15 Nov 2011 05:58:53 GMT (envelope-from joelja@bogus.com)
Message-ID: <4EC1FF9A.4080308@bogus.com>
Date: Tue, 15 Nov 2011 13:58:50 +0800
From: Joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Lorenzo Colitti <lorenzo@google.com>
References: <4EC1C386.6010802@gmail.com> <4EC1C566.2060400@cisco.com> <4EC1CC2E.30209@gmail.com> <4EC1D6C9.3030107@cisco.com> <CAKD1Yr3rFJonkJ1CbCgGPpr-WDj1RFmR6q4jDab1Toc0tJJodg@mail.gmail.com>
In-Reply-To: <CAKD1Yr3rFJonkJ1CbCgGPpr-WDj1RFmR6q4jDab1Toc0tJJodg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Tue, 15 Nov 2011 05:58:54 +0000 (UTC)
Cc: Erik Nordmark <nordmark@cisco.com>, homenet@ietf.org
Subject: Re: [homenet] pervasive v4
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 05:58:58 -0000

On 11/15/11 13:49 , Lorenzo Colitti wrote:
> On Tue, Nov 15, 2011 at 11:04, Erik Nordmark <nordmark@cisco.com
> <mailto:nordmark@cisco.com>> wrote:
> 
>     On 11/14/11 6:19 PM, Brian E Carpenter wrote:
> 
>         Yes, but then we're extending v4 and expecting homenets to run
>         (presumably) RIP.
> 
> 
>     Why RIP? Same protocol between the home routers as we will pick for
>     routing IPv6 in the home.
> 
> 
> The primitives you have to configure and renumber IPv6 hosts (multiple
> addresses, multiple RAs and address deprecation, and so on) are
> different from the ones we have in IPv4 (essentially, DHCPv4 and NAT).
> 
> So I don't think we will be able to take what we do in IPv6 and apply it
> as-is to IPv4. Instead, I think we'll have to either NAT everywhere
> (like we do today) or bridge everywhere.

the consumer routinely ends up with double nats today, that's hardly
ideal, but it works for the most part. it doesn't seem likely to get
better esp as it involves the support of legacy devices.

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


From teco@inf-net.nl  Mon Nov 14 22:02:52 2011
Return-Path: <teco@inf-net.nl>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 654A011E816F for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 22:02:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zTAz-9RKEErW for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 22:02:50 -0800 (PST)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 9144911E81CE for <homenet@ietf.org>; Mon, 14 Nov 2011 22:02:50 -0800 (PST)
Received: by ggnr5 with SMTP id r5so2034020ggn.31 for <homenet@ietf.org>; Mon, 14 Nov 2011 22:02:48 -0800 (PST)
Received: by 10.100.99.16 with SMTP id w16mr1007519anb.22.1321336967508; Mon, 14 Nov 2011 22:02:47 -0800 (PST)
Received: from ?IPv6:2001:df8::16:298f:3cfb:2dbf:b779? ([2001:df8:0:16:298f:3cfb:2dbf:b779]) by mx.google.com with ESMTPS id l27sm69484274ani.21.2011.11.14.22.02.40 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 14 Nov 2011 22:02:46 -0800 (PST)
From: Teco Boot <teco@inf-net.nl>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Tue, 15 Nov 2011 07:01:34 +0100
Message-Id: <A3F74192-91F9-4E05-AE74-3845BECF4C68@inf-net.nl>
To: homenet@ietf.org
Mime-Version: 1.0 (Apple Message framework v1251.1)
X-Mailer: Apple Mail (2.1251.1)
Subject: [homenet] Prevent configuration of unneeded prefixes
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 06:02:52 -0000

The BRDP proposal I made for Autoconf (ad hoc networks) has some =
concepts that applies to Homenet also. For example, configuration of =
unneeded prefixes should be prevented. BRDP does so by checking already =
RA advertised prefixes with advertised ISP prefix blocks:
http://tools.ietf.org/html/draft-boot-brdp-framework-00
>    Having multiple prefixes from the same ISP bound on a link
>    is not useful.  So a router requests a prefix from a Border Router
>    only if no other prefix of that Border Router is advertised already
>    by another router on this network segment.
This requires awareness of ISP provided prefix blocks. It is needed by =
source address based forwarding also. So run BRDP or develop something =
similar. =20

A related issue is a requirement, or not, on complete set of on-link =
prefixes in RAs.
RFC 4861 says:
>    A router SHOULD include all its on-link prefixes ...
What to do? Shall all routers on a link repeat the prefix? Or only the =
initiator or election winner and let hosts accumulate the whole set?

Teco


From brian.e.carpenter@gmail.com  Mon Nov 14 22:05:49 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8032021F8E42 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 22:05:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.038
X-Spam-Level: 
X-Spam-Status: No, score=-101.038 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_RECV_IP_061228=0.895, SARE_RECV_SPAM_DOMN0b=1.666, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uZ4zbf-MsZgi for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 22:05:49 -0800 (PST)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id D012321F8E40 for <homenet@ietf.org>; Mon, 14 Nov 2011 22:05:48 -0800 (PST)
Received: by yenq4 with SMTP id q4so4394718yen.31 for <homenet@ietf.org>; Mon, 14 Nov 2011 22:05:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=InIZvYdsXFwsu/oox9BniY+GN+UxEHI0wIu3ZUenrtU=; b=OkqNck/JgrrM97Q94zyUwnbf9b3XqHM4rtB4FY5sqqkvzVekv8F2U6DIAD6jUPECpK pW/K4HKhZYXv0VF+5kBZXPhZQPpSbIbr9GKalcNYo24I+JCtkgyYyglRld7tbiq8YYmC L254XJQyhpesuqirnmCv8BtsNQp6g/AA2vKm0=
Received: by 10.101.105.4 with SMTP id h4mr7314348anm.123.1321337148350; Mon, 14 Nov 2011 22:05:48 -0800 (PST)
Received: from [192.168.0.217] (61-230-53-171.dynamic.hinet.net. [61.230.53.171]) by mx.google.com with ESMTPS id k3sm69622332ann.0.2011.11.14.22.05.45 (version=SSLv3 cipher=OTHER); Mon, 14 Nov 2011 22:05:47 -0800 (PST)
Message-ID: <4EC20135.3030301@gmail.com>
Date: Tue, 15 Nov 2011 19:05:41 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Lorenzo Colitti <lorenzo@google.com>
References: <4EC1C386.6010802@gmail.com> <CAKD1Yr02-uj28JnMnNeFPc-nUYGpp-fobZW7wSY_3WTGH0DaBQ@mail.gmail.com>
In-Reply-To: <CAKD1Yr02-uj28JnMnNeFPc-nUYGpp-fobZW7wSY_3WTGH0DaBQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: homenet@ietf.org, Hans Liu <Hans_Liu@dlink.com.tw>
Subject: Re: [homenet] pervasive v4
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 06:05:49 -0000

On 2011-11-15 18:42, Lorenzo Colitti wrote:
> On Tue, Nov 15, 2011 at 09:42, Brian E Carpenter <
> brian.e.carpenter@gmail.com> wrote:
> 
>> If homenet is going to support arbitrary self-configuring topologies,
>> and pervasive legacy IPv4 is required, we'd surely end up recommending
>> NAT444-within-the-home as the only remotely practicable approach.
> 
> 
> Hans from D-Link suggests that another option is simply to bridge IPv4
> packets and route IPv6 packets.

Iff the bridges support the spanning tree, yes.

  Brian


From mellon@fugue.com  Mon Nov 14 22:07:08 2011
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC44121F8B06 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 22:07:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.131
X-Spam-Level: 
X-Spam-Status: No, score=-1.131 tagged_above=-999 required=5 tests=[AWL=0.072,  BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1sBdeu1R5xWa for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 22:07:07 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 172E321F8E3F for <homenet@ietf.org>; Mon, 14 Nov 2011 22:07:05 -0800 (PST)
Received: from [172.22.13.155] (unknown [122.147.240.7]) by toccata.fugue.com (Postfix) with ESMTPSA id DD9772381C89; Tue, 15 Nov 2011 01:07:03 -0500 (EST)
References: <13919.1321321547@marajade.sandelman.ca> <4EC1CEDC.20702@isi.edu> <A38099B4-7759-4DD3-92D1-5C6729B445DA@fugue.com> <4EC1D2C6.3020502@gmail.com> <6B3A3374-AC8B-49F1-BEBE-46CA3E795874@fugue.com> <ED4C6FF5-8D9E-4790-A4B1-3164791B24E0@twcable.com>
In-Reply-To: <ED4C6FF5-8D9E-4790-A4B1-3164791B24E0@twcable.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <00A4204D-D63F-46EE-BC48-3ED6CD74FBB6@fugue.com>
X-Mailer: iPad Mail (9A334)
From: Ted Lemon <mellon@fugue.com>
Date: Tue, 15 Nov 2011 14:07:32 +0800
To: "Howard, Lee" <lee.howard@twcable.com>
Cc: Michael Richardson <mcr@sandelman.ca>, homenet <homenet@ietf.org>, Rene Struik <rstruik.ext@gmail.com>, Joe Touch <touch@isi.edu>
Subject: Re: [homenet] secret sharing among devices
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 06:07:08 -0000

On Nov 15, 2011, at 1:42 PM, "Howard, Lee" <lee.howard@twcable.com> wrote:
> How do we explain to "the typical home user" what a router is, how to deci=
de whether a given thing is one, and how to (in all cases) get the Magic Key=
 onto it?  In other words, when you say "are intended," who is doing the int=
ending?

Presumably a device that's intended to work in a homenet environment will un=
derstand what's on the key, and a device that isn't won't, so it's a non-iss=
ue.   Just plug it into every device you want to connect to the network.   A=
ctually, devices that are leaf nodes can benefit from this too.

The point here is that you _won't_ plug it into a device that you _don't_ wa=
nt connected to your network.


From brian.e.carpenter@gmail.com  Mon Nov 14 22:11:37 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 366FE11E826B for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 22:11:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.038
X-Spam-Level: 
X-Spam-Status: No, score=-101.038 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_RECV_IP_061228=0.895, SARE_RECV_SPAM_DOMN0b=1.666, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AsyKmUGrlRy4 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 22:11:35 -0800 (PST)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id ABBAD11E8291 for <homenet@ietf.org>; Mon, 14 Nov 2011 22:11:34 -0800 (PST)
Received: by yenq4 with SMTP id q4so4400352yen.31 for <homenet@ietf.org>; Mon, 14 Nov 2011 22:11:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=da+ZZXszLsnW+HaECyg7hBfdNJ7snk5MvDTEJLgld9A=; b=qxrreR44DnTjCl2yznbve1lO8YJLmcfJHRlx41DsJlf4CWV4jSea/Yo61MbiggCd7M NgDwt3n7A8NE4o1xnGinLLcNlgA2MyGHgW/5gfkQ0ts6/HUlQPrXCpHZv53J5UVEDcEZ ikxXb47+dOSCfF/BhILZ/J7g08pTt7U/QWDI0=
Received: by 10.101.151.32 with SMTP id d32mr7574759ano.25.1321337494141; Mon, 14 Nov 2011 22:11:34 -0800 (PST)
Received: from [192.168.0.217] (61-230-53-171.dynamic.hinet.net. [61.230.53.171]) by mx.google.com with ESMTPS id k20sm69608808ann.15.2011.11.14.22.11.31 (version=SSLv3 cipher=OTHER); Mon, 14 Nov 2011 22:11:33 -0800 (PST)
Message-ID: <4EC2028E.6050305@gmail.com>
Date: Tue, 15 Nov 2011 19:11:26 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Joel jaeggli <joelja@bogus.com>
References: <4EC1C386.6010802@gmail.com> <4EC1C566.2060400@cisco.com>	<4EC1CC2E.30209@gmail.com> <4EC1D6C9.3030107@cisco.com>	<CAKD1Yr3rFJonkJ1CbCgGPpr-WDj1RFmR6q4jDab1Toc0tJJodg@mail.gmail.com> <4EC1FF9A.4080308@bogus.com>
In-Reply-To: <4EC1FF9A.4080308@bogus.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Erik Nordmark <nordmark@cisco.com>, homenet@ietf.org, Lorenzo Colitti <lorenzo@google.com>
Subject: Re: [homenet] pervasive v4
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 06:11:39 -0000

And if the user plugs and plays this:

       WAN
        |
     [NAT44]
        |
-------------------
   |           |
[NAT44]     [NAT44]
   |           |
-------------------

what happens? Please script the help desk call.

    Brian

On 2011-11-15 18:58, Joel jaeggli wrote:
> On 11/15/11 13:49 , Lorenzo Colitti wrote:
>> On Tue, Nov 15, 2011 at 11:04, Erik Nordmark <nordmark@cisco.com
>> <mailto:nordmark@cisco.com>> wrote:
>>
>>     On 11/14/11 6:19 PM, Brian E Carpenter wrote:
>>
>>         Yes, but then we're extending v4 and expecting homenets to run
>>         (presumably) RIP.
>>
>>
>>     Why RIP? Same protocol between the home routers as we will pick for
>>     routing IPv6 in the home.
>>
>>
>> The primitives you have to configure and renumber IPv6 hosts (multiple
>> addresses, multiple RAs and address deprecation, and so on) are
>> different from the ones we have in IPv4 (essentially, DHCPv4 and NAT).
>>
>> So I don't think we will be able to take what we do in IPv6 and apply it
>> as-is to IPv4. Instead, I think we'll have to either NAT everywhere
>> (like we do today) or bridge everywhere.
> 
> the consumer routinely ends up with double nats today, that's hardly
> ideal, but it works for the most part. it doesn't seem likely to get
> better esp as it involves the support of legacy devices.
> 
>> _______________________________________________
>> 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 lee.howard@twcable.com  Mon Nov 14 22:12:30 2011
Return-Path: <lee.howard@twcable.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 099E021F86AA for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 22:12:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.713
X-Spam-Level: 
X-Spam-Status: No, score=-0.713 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6WTRltT+ItpX for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 22:12:29 -0800 (PST)
Received: from cdpipgw02.twcable.com (cdpipgw02.twcable.com [165.237.59.23]) by ietfa.amsl.com (Postfix) with ESMTP id EEEAE21F8433 for <homenet@ietf.org>; Mon, 14 Nov 2011 22:12:28 -0800 (PST)
X-SENDER-IP: 10.136.163.11
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.69,512,1315195200"; d="scan'208";a="282127267"
Received: from unknown (HELO PRVPEXHUB02.corp.twcable.com) ([10.136.163.11]) by cdpipgw02.twcable.com with ESMTP/TLS/RC4-MD5; 15 Nov 2011 01:07:23 -0500
Received: from PRVPEXVS03.corp.twcable.com ([10.136.163.26]) by PRVPEXHUB02.corp.twcable.com ([10.136.163.11]) with mapi; Tue, 15 Nov 2011 01:12:19 -0500
From: "Howard, Lee" <lee.howard@twcable.com>
To: Ted Lemon <mellon@fugue.com>
Date: Tue, 15 Nov 2011 01:12:18 -0500
Thread-Topic: [homenet] secret sharing among devices
Thread-Index: AcyjXYgrDAuT4Q4ERXyPoWCgQWjT4w==
Message-ID: <043E032A-6C3F-436B-A41D-FA84F83E89DA@twcable.com>
References: <13919.1321321547@marajade.sandelman.ca> <4EC1CEDC.20702@isi.edu> <A38099B4-7759-4DD3-92D1-5C6729B445DA@fugue.com> <4EC1D2C6.3020502@gmail.com> <6B3A3374-AC8B-49F1-BEBE-46CA3E795874@fugue.com> <ED4C6FF5-8D9E-4790-A4B1-3164791B24E0@twcable.com> <00A4204D-D63F-46EE-BC48-3ED6CD74FBB6@fugue.com>
In-Reply-To: <00A4204D-D63F-46EE-BC48-3ED6CD74FBB6@fugue.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Michael Richardson <mcr@sandelman.ca>, homenet <homenet@ietf.org>, Rene Struik <rstruik.ext@gmail.com>, Joe Touch <touch@isi.edu>
Subject: Re: [homenet] secret sharing among devices
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 06:12:30 -0000

On Nov 15, 2011, at 2:07 PM, Ted Lemon wrote:

> On Nov 15, 2011, at 1:42 PM, "Howard, Lee" <lee.howard@twcable.com> wrote=
:
>> How do we explain to "the typical home user" what a router is, how to de=
cide whether a given thing is one, and how to (in all cases) get the Magic =
Key onto it?  In other words, when you say "are intended," who is doing the=
 intending?
>
> Presumably a device that's intended to work in a homenet environment will=
 understand what's on the key, and a device that isn't won't, so it's a non=
-issue.   Just plug it into every device you want to connect to the network=
.   Actually, devices that are leaf nodes can benefit from this too.
>
> The point here is that you _won't_ plug it into a device that you _don't_=
 want connected to your network.


Ah, I thought you were trying to distinguish routers from hosts, where "hos=
ts" don't have the magic in them.

FWIW, the most common boxes I see have two or more Ethernet ports and some =
Wi-Fi.  I don't want to pay for another interface, especially if it's inten=
ded to be one-time use.  So, if in-line is the only method one has for putt=
ing the Magic Key on the device, are we talking about (t)FTP?  That doesn't=
 sound easier than a GUI to me.  Or do we need to describe or find another =
method for Magic Key discovery and retrieval?

Lee

This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

From mellon@fugue.com  Mon Nov 14 22:13:38 2011
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD02211E825D for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 22:13:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.137
X-Spam-Level: 
X-Spam-Status: No, score=-1.137 tagged_above=-999 required=5 tests=[AWL=0.066,  BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lPa4V8pHfyAN for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 22:13:38 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 328A011E811B for <homenet@ietf.org>; Mon, 14 Nov 2011 22:13:38 -0800 (PST)
Received: from [172.22.13.155] (unknown [122.147.240.7]) by toccata.fugue.com (Postfix) with ESMTPSA id 4AF872381C89; Tue, 15 Nov 2011 01:13:37 -0500 (EST)
References: <D143FF2D6A52E5409FEE8BC1CD3BC54893992FBB97@IRVEXCHCCR01.corp.ad.broadcom.com> <4EC1E9B5.1020908@bogus.com> <5100D13B-B2CD-48C8-A829-8AFDB9100EAF@fugue.com> <4EC1FC1C.9090208@bogus.com>
In-Reply-To: <4EC1FC1C.9090208@bogus.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <6CAC03B6-C5E5-48B3-BE3D-B611BEF54D0C@fugue.com>
X-Mailer: iPad Mail (9A334)
From: Ted Lemon <mellon@fugue.com>
Date: Tue, 15 Nov 2011 14:14:05 +0800
To: Joel jaeggli <joelja@bogus.com>
Cc: "homenet@ietf.org" <homenet@ietf.org>, "Stephen \[kiwin\] Palm" <palm@broadcom.com>, "mcr@sandelman.ca" <mcr@sandelman.ca>, "touch@isi.edu" <touch@isi.edu>
Subject: Re: [homenet] secret sharing among devices
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 06:13:38 -0000

On Nov 15, 2011, at 1:43 PM, Joel jaeggli <joelja@bogus.com> wrote:
> A decade and a half worth of bluetooth security associations including
> really bad ones says otherwise.

Yes, and the reason it works is because for most devices, there is no securi=
ty, and for the remaining devices, there's a screen that can give you instru=
ctions.   Have you ever owned a bluetooth headset that didn't have a PIN of 0=
000?

> Personal devices by in large are shedding data-ports where possible and
> especially for low speed interaction.

Maybe so.   Do you expect the iPad three to get rid of its USB port?   What a=
bout my next Android phone?   If your point is that networks are increasingl=
y going to be wireless-only, with no means of plugging a physical token into=
 the device, then yes, I agree, we can't solve this problem for those device=
s.   Either they aggressively autoconfigure, and form networks that shouldn'=
t have been formed, or they are configured manually, by grandma's grandson.

> And I see that as a usable outcome, as rather unlikely.

No offense, but I don't really care what your opinion is.   What I care abou=
t is what actually happens.   It may be that you are right, but if so, then I=
 don't really think we can solve this problem.

> As a consumer I want to bring the thing home, turn it on, and have it work=
.

As a consumer, I want it to strew flowers at my feet as I walk into the hous=
e, and clean them up afterwards.   What you want as a consumer is probably m=
ore possible than what I want, but what you will get will be a system that h=
as some really bad failure modes.=

From mellon@fugue.com  Mon Nov 14 22:14:46 2011
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DEE7F11E82AC for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 22:14:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.84
X-Spam-Level: 
X-Spam-Status: No, score=-1.84 tagged_above=-999 required=5 tests=[AWL=0.759,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hbAhKEFYJUHf for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 22:14:46 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 6B8C711E8291 for <homenet@ietf.org>; Mon, 14 Nov 2011 22:14:46 -0800 (PST)
Received: from [172.22.13.155] (unknown [122.147.240.7]) by toccata.fugue.com (Postfix) with ESMTPSA id 6E8602381C89; Tue, 15 Nov 2011 01:14:45 -0500 (EST)
References: <D143FF2D6A52E5409FEE8BC1CD3BC54893992FBB98@IRVEXCHCCR01.corp.ad.broadcom.com> <958CCC88-A01D-49FA-9E83-123E62DFAD24@fugue.com> <4EC1F689.9010401@isi.edu> <20111115054440.E839817334CE@drugs.dv.isc.org> <4EC1FF56.9050202@isi.edu>
In-Reply-To: <4EC1FF56.9050202@isi.edu>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii
Message-Id: <8A289B2F-4130-4F91-9DB6-5960184FF22D@fugue.com>
X-Mailer: iPad Mail (9A334)
From: Ted Lemon <mellon@fugue.com>
Date: Tue, 15 Nov 2011 14:15:13 +0800
To: Joe Touch <touch@isi.edu>
Cc: "homenet@ietf.org" <homenet@ietf.org>, "Stephen \[kiwin\] Palm" <palm@broadcom.com>, "mcr@sandelman.ca" <mcr@sandelman.ca>, Mark Andrews <marka@isc.org>
Subject: Re: [homenet] secret sharing among devices
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 06:14:47 -0000

On Nov 15, 2011, at 1:57 PM, Joe Touch <touch@isi.edu> wrote:
> Not iPhones ;-)

iPhones have USB interfaces.

From joelja@bogus.com  Mon Nov 14 22:17:48 2011
Return-Path: <joelja@bogus.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D919F11E81D5 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 22:17:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.524
X-Spam-Level: 
X-Spam-Status: No, score=-102.524 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CjTyXngXTx3T for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 22:17:48 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 5A1B011E80AB for <homenet@ietf.org>; Mon, 14 Nov 2011 22:17:48 -0800 (PST)
Received: from dhcp-2510.meeting.ietf.org (dhcp-2510.meeting.ietf.org [130.129.37.16]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id pAF6HeHv091241 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Tue, 15 Nov 2011 06:17:42 GMT (envelope-from joelja@bogus.com)
Message-ID: <4EC20405.8040505@bogus.com>
Date: Tue, 15 Nov 2011 14:17:41 +0800
From: Joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <4EC1C386.6010802@gmail.com> <4EC1C566.2060400@cisco.com>	<4EC1CC2E.30209@gmail.com> <4EC1D6C9.3030107@cisco.com>	<CAKD1Yr3rFJonkJ1CbCgGPpr-WDj1RFmR6q4jDab1Toc0tJJodg@mail.gmail.com> <4EC1FF9A.4080308@bogus.com> <4EC2028E.6050305@gmail.com>
In-Reply-To: <4EC2028E.6050305@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Tue, 15 Nov 2011 06:17:43 +0000 (UTC)
Cc: Erik Nordmark <nordmark@cisco.com>, homenet@ietf.org, Lorenzo Colitti <lorenzo@google.com>
Subject: Re: [homenet] pervasive v4
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 06:17:49 -0000

On 11/15/11 14:11 , Brian E Carpenter wrote:
> And if the user plugs and plays this:
> 
>        WAN
>         |
>      [NAT44]
>         |
> -------------------
>    |           |
> [NAT44]     [NAT44]
>    |           |
> -------------------
> 
> what happens? Please script the help desk call.

Your exit to the upper element is dependent on which dhcp server answers
first...

if you have an address collision well, you're screwed...


        WAN
         |
      [NAT44]
         |
 -------------------
    |     |      |
 [NAT44]  |   [NAT44]
    |     |      |
 -------------------

seen that too...

> 
>     Brian
> 
> On 2011-11-15 18:58, Joel jaeggli wrote:
>> On 11/15/11 13:49 , Lorenzo Colitti wrote:
>>> On Tue, Nov 15, 2011 at 11:04, Erik Nordmark <nordmark@cisco.com
>>> <mailto:nordmark@cisco.com>> wrote:
>>>
>>>     On 11/14/11 6:19 PM, Brian E Carpenter wrote:
>>>
>>>         Yes, but then we're extending v4 and expecting homenets to run
>>>         (presumably) RIP.
>>>
>>>
>>>     Why RIP? Same protocol between the home routers as we will pick for
>>>     routing IPv6 in the home.
>>>
>>>
>>> The primitives you have to configure and renumber IPv6 hosts (multiple
>>> addresses, multiple RAs and address deprecation, and so on) are
>>> different from the ones we have in IPv4 (essentially, DHCPv4 and NAT).
>>>
>>> So I don't think we will be able to take what we do in IPv6 and apply it
>>> as-is to IPv4. Instead, I think we'll have to either NAT everywhere
>>> (like we do today) or bridge everywhere.
>>
>> the consumer routinely ends up with double nats today, that's hardly
>> ideal, but it works for the most part. it doesn't seem likely to get
>> better esp as it involves the support of legacy devices.
>>
>>> _______________________________________________
>>> 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 mellon@fugue.com  Mon Nov 14 22:19:54 2011
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E1CF91F0D71 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 22:19:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.196
X-Spam-Level: 
X-Spam-Status: No, score=-1.196 tagged_above=-999 required=5 tests=[AWL=0.007,  BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NCJqaR1fOcrh for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 22:19:54 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 7205F1F0D66 for <homenet@ietf.org>; Mon, 14 Nov 2011 22:19:54 -0800 (PST)
Received: from [172.22.13.155] (unknown [122.147.240.7]) by toccata.fugue.com (Postfix) with ESMTPSA id 960D72381C89; Tue, 15 Nov 2011 01:19:53 -0500 (EST)
References: <4EC1C386.6010802@gmail.com> <4EC1C566.2060400@cisco.com> <4EC1CC2E.30209@gmail.com> <4EC1D6C9.3030107@cisco.com> <CAKD1Yr3rFJonkJ1CbCgGPpr-WDj1RFmR6q4jDab1Toc0tJJodg@mail.gmail.com> <4EC1FF9A.4080308@bogus.com>
In-Reply-To: <4EC1FF9A.4080308@bogus.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <BAC2095D-C227-41D4-B107-635ECE82AE8E@fugue.com>
X-Mailer: iPad Mail (9A334)
From: Ted Lemon <mellon@fugue.com>
Date: Tue, 15 Nov 2011 14:20:21 +0800
To: Joel jaeggli <joelja@bogus.com>
Cc: Erik Nordmark <nordmark@cisco.com>, "homenet@ietf.org" <homenet@ietf.org>, Lorenzo Colitti <lorenzo@google.com>
Subject: Re: [homenet] pervasive v4
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 06:19:55 -0000

On Nov 15, 2011, at 1:58 PM, Joel jaeggli <joelja@bogus.com> wrote:
> the consumer routinely ends up with double nats today, that's hardly
> ideal, but it works for the most part. it doesn't seem likely to get
> better esp as it involves the support of legacy devices.

This is sort of true, although cascaded NATs do cause some problems.   But i=
f we can specify it out of dual-stack devices, I think that would be a win.


From mellon@fugue.com  Mon Nov 14 22:20:01 2011
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 883F01F0D57 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 22:20:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.197
X-Spam-Level: 
X-Spam-Status: No, score=-1.197 tagged_above=-999 required=5 tests=[AWL=0.006,  BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m0WiBnGQ6viC for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 22:20:00 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 2B4EC1F0CBB for <homenet@ietf.org>; Mon, 14 Nov 2011 22:20:00 -0800 (PST)
Received: from [172.22.13.155] (unknown [122.147.240.7]) by toccata.fugue.com (Postfix) with ESMTPSA id 529EE2381C89; Tue, 15 Nov 2011 01:19:59 -0500 (EST)
References: <4EC1C386.6010802@gmail.com> <CAKD1Yr02-uj28JnMnNeFPc-nUYGpp-fobZW7wSY_3WTGH0DaBQ@mail.gmail.com>
From: Ted Lemon <mellon@fugue.com>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <CAKD1Yr02-uj28JnMnNeFPc-nUYGpp-fobZW7wSY_3WTGH0DaBQ@mail.gmail.com>
Message-Id: <31F9C098-4263-44DB-8113-79F5949020D0@fugue.com>
Date: Tue, 15 Nov 2011 14:19:10 +0800
To: Lorenzo Colitti <lorenzo@google.com>
Mime-Version: 1.0 (1.0)
X-Mailer: iPad Mail (9A334)
Cc: Hans Liu <Hans_Liu@dlink.com.tw>, "homenet@ietf.org" <homenet@ietf.org>
Subject: Re: [homenet] pervasive v4
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 06:20:01 -0000

On Nov 15, 2011, at 1:42 PM, Lorenzo Colitti <lorenzo@google.com> wrote:
> Hans from D-Link suggests that another option is simply to bridge IPv4 pac=
kets and route IPv6 packets.

If this were part of the homenet requirements, I would be pretty happy with t=
hat.   We'd need to deal with the case where the CPE device is bridged to th=
e provider network, though, rather than routed.=

From touch@isi.edu  Mon Nov 14 22:25:38 2011
Return-Path: <touch@isi.edu>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C80CB11E80AB for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 22:25:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.854
X-Spam-Level: 
X-Spam-Status: No, score=-104.854 tagged_above=-999 required=5 tests=[AWL=1.745, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0M8-W+Rvbv7P for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 22:25:37 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id D3A7E11E81D5 for <homenet@ietf.org>; Mon, 14 Nov 2011 22:25:37 -0800 (PST)
Received: from [130.129.66.136] (dhcp-4288.meeting.ietf.org [130.129.66.136]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id pAF6Otm2009303 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 14 Nov 2011 22:25:05 -0800 (PST)
Message-ID: <4EC205B5.9090208@isi.edu>
Date: Mon, 14 Nov 2011 22:24:53 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Ted Lemon <mellon@fugue.com>
References: <D143FF2D6A52E5409FEE8BC1CD3BC54893992FBB98@IRVEXCHCCR01.corp.ad.broadcom.com> <958CCC88-A01D-49FA-9E83-123E62DFAD24@fugue.com> <4EC1F689.9010401@isi.edu> <20111115054440.E839817334CE@drugs.dv.isc.org> <4EC1FF56.9050202@isi.edu> <8A289B2F-4130-4F91-9DB6-5960184FF22D@fugue.com>
In-Reply-To: <8A289B2F-4130-4F91-9DB6-5960184FF22D@fugue.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "homenet@ietf.org" <homenet@ietf.org>, "Stephen \[kiwin\] Palm" <palm@broadcom.com>, "mcr@sandelman.ca" <mcr@sandelman.ca>, Mark Andrews <marka@isc.org>
Subject: Re: [homenet] secret sharing among devices
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 06:25:38 -0000

On 11/14/2011 10:15 PM, Ted Lemon wrote:
> On Nov 15, 2011, at 1:57 PM, Joe Touch<touch@isi.edu>  wrote:
>> Not iPhones ;-)
>
> iPhones have USB interfaces.

iPhones are (or can be) routers.

iPhones have no microSD.

iPhones have a USB port that does not supply power.

Yes, bluetooth might be a way to get data into the phone (not sure if 
IOS supports the full bluetooth spec this way, though). But you can't 
plug a USB stick into it (even with a physical adapter), and you can't 
plug a SD of any sort into it.

Joe

From marka@isc.org  Mon Nov 14 22:45:52 2011
Return-Path: <marka@isc.org>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2326711E812D for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 22:45:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.438
X-Spam-Level: 
X-Spam-Status: No, score=-2.438 tagged_above=-999 required=5 tests=[AWL=0.161,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iY7QTP8NYn6I for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 22:45:51 -0800 (PST)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [IPv6:2001:500:60::65]) by ietfa.amsl.com (Postfix) with ESMTP id 844A111E8291 for <homenet@ietf.org>; Mon, 14 Nov 2011 22:45:51 -0800 (PST)
Received: from bikeshed.isc.org (bikeshed.isc.org [IPv6:2001:4f8:3:d::19]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "bikeshed.isc.org", Issuer "ISC CA" (verified OK)) by mx.ams1.isc.org (Postfix) with ESMTPS id 755CD5F9899; Tue, 15 Nov 2011 06:45:26 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (unknown [IPv6:2001:470:1f00:820:6233:4bff:fe01:7585]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by bikeshed.isc.org (Postfix) with ESMTPSA id A34DA216C6B; Tue, 15 Nov 2011 06:45:24 +0000 (UTC) (envelope-from marka@isc.org)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (Postfix) with ESMTP id 4B0F51733DE9; Tue, 15 Nov 2011 17:45:17 +1100 (EST)
To: Joe Touch <touch@isi.edu>
From: Mark Andrews <marka@isc.org>
References: <D143FF2D6A52E5409FEE8BC1CD3BC54893992FBB98@IRVEXCHCCR01.corp.ad.broadcom.com> <958CCC88-A01D-49FA-9E83-123E62DFAD24@fugue.com> <4EC1F689.9010401@isi.edu> <20111115054440.E839817334CE@drugs.dv.isc.org> <4EC1FF56.9050202@isi.edu> <8A289B2F-4130-4F91-9DB6-5960184FF22D@fugue.com> <4EC205B5.9090208@isi.edu>
In-reply-to: Your message of "Mon, 14 Nov 2011 22:24:53 -0800." <4EC205B5.9090208@isi.edu>
Date: Tue, 15 Nov 2011 17:45:17 +1100
Message-Id: <20111115064517.4B0F51733DE9@drugs.dv.isc.org>
Cc: "homenet@ietf.org" <homenet@ietf.org>, "Stephen \[kiwin\] Palm" <palm@broadcom.com>, Ted Lemon <mellon@fugue.com>, "mcr@sandelman.ca" <mcr@sandelman.ca>
Subject: Re: [homenet] secret sharing among devices
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 06:45:52 -0000

In message <4EC205B5.9090208@isi.edu>, Joe Touch writes:
> 
> 
> On 11/14/2011 10:15 PM, Ted Lemon wrote:
> > On Nov 15, 2011, at 1:57 PM, Joe Touch<touch@isi.edu>  wrote:
> >> Not iPhones ;-)
> >
> > iPhones have USB interfaces.
> 
> iPhones are (or can be) routers.
> 
> iPhones have no microSD.
> 
> iPhones have a USB port that does not supply power.
> 
> Yes, bluetooth might be a way to get data into the phone (not sure if 
> IOS supports the full bluetooth spec this way, though). But you can't 
> plug a USB stick into it (even with a physical adapter), and you can't 
> plug a SD of any sort into it.

The iPhone is its own thumb drive.
 
> Joe
> _______________________________________________
> 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 joelja@bogus.com  Mon Nov 14 22:46:29 2011
Return-Path: <joelja@bogus.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 852B211E821B for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 22:46:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.532
X-Spam-Level: 
X-Spam-Status: No, score=-102.532 tagged_above=-999 required=5 tests=[AWL=0.067, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v9Bi+2grUshw for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 22:46:29 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 0CF0B11E812D for <homenet@ietf.org>; Mon, 14 Nov 2011 22:46:29 -0800 (PST)
Received: from dhcp-2510.meeting.ietf.org (dhcp-2510.meeting.ietf.org [130.129.37.16]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id pAF6kDf9091791 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Tue, 15 Nov 2011 06:46:15 GMT (envelope-from joelja@bogus.com)
Message-ID: <4EC20AB1.9060809@bogus.com>
Date: Tue, 15 Nov 2011 14:46:09 +0800
From: Joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Ted Lemon <mellon@fugue.com>
References: <D143FF2D6A52E5409FEE8BC1CD3BC54893992FBB97@IRVEXCHCCR01.corp.ad.broadcom.com> <4EC1E9B5.1020908@bogus.com> <5100D13B-B2CD-48C8-A829-8AFDB9100EAF@fugue.com> <4EC1FC1C.9090208@bogus.com> <6CAC03B6-C5E5-48B3-BE3D-B611BEF54D0C@fugue.com>
In-Reply-To: <6CAC03B6-C5E5-48B3-BE3D-B611BEF54D0C@fugue.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Tue, 15 Nov 2011 06:46:16 +0000 (UTC)
Cc: "homenet@ietf.org" <homenet@ietf.org>, "Stephen \[kiwin\] Palm" <palm@broadcom.com>, "mcr@sandelman.ca" <mcr@sandelman.ca>, "touch@isi.edu" <touch@isi.edu>
Subject: Re: [homenet] secret sharing among devices
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 06:46:29 -0000

On 11/15/11 14:14 , Ted Lemon wrote:
> On Nov 15, 2011, at 1:43 PM, Joel jaeggli <joelja@bogus.com> wrote:
>> A decade and a half worth of bluetooth security associations
>> including really bad ones says otherwise.
> 
> Yes, and the reason it works is because for most devices, there is no
> security, 

It's more concise to describe them as offering no MITM protection. The
association is either the product of a predefined shared secret (which
isn't secret) or after bluetooth 2.1 by SSP. the intent to pair in
either case is deliberately initiated.

> and for the remaining devices, there's a screen that can
> give you instructions.   Have you ever owned a bluetooth headset that
> didn't have a PIN of 0000?

yes but that was 1998 and it wasn't the most usable device ever.

>> Personal devices by in large are shedding data-ports where possible
>> and especially for low speed interaction.
> 
> Maybe so.   Do you expect the iPad three to get rid of its USB port?

I expect that devices like the i*/and* as well as other consumer
electronics that are moving onto the network (like televisions speakers
and so forth) will continue to down the road towards shedding their
dependance on tethering to each in a physical fashion. when that happens
precisely is a business decision on the part of their manufacturers and
the suppliers of the application stack and the supporting  accoutrements.

...




From rturner@amalfisystems.com  Mon Nov 14 22:54:24 2011
Return-Path: <rturner@amalfisystems.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CF0D11E8094 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 22:54:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fMraOvYfkqUX for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 22:54:23 -0800 (PST)
Received: from omr17.networksolutionsemail.com (omr17.networksolutionsemail.com [205.178.146.67]) by ietfa.amsl.com (Postfix) with ESMTP id 1897B1F0C3E for <homenet@ietf.org>; Mon, 14 Nov 2011 22:54:23 -0800 (PST)
Received: from cm-omr4 (mail.networksolutionsemail.com [205.178.146.50]) by omr17.networksolutionsemail.com (8.13.8/8.13.8) with ESMTP id pAF6sJrs006224 for <homenet@ietf.org>; Tue, 15 Nov 2011 01:54:21 -0500
Authentication-Results: cm-omr4 smtp.user=rturner@amalfisystems.com; auth=pass (LOGIN)
X-Authenticated-UID: rturner@amalfisystems.com
Received: from [98.151.18.158] ([98.151.18.158:42394] helo=localhost) by cm-omr4 (envelope-from <rturner@amalfisystems.com>) (ecelerity 2.2.2.41 r(31179/31189)) with ESMTPA id 8C/34-04877-B9C02CE4; Tue, 15 Nov 2011 01:54:19 -0500
Date: Mon, 14 Nov 2011 22:54:15 -0800
Message-ID: <x8t6f1v0lqimf54q4kw8fq4x.1321340055797@email.android.com>
Importance: normal
From: Randy Turner <rturner@amalfisystems.com>
To: brian.e.carpenter@gmail.com, tjc@ecs.soton.ac.uk
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="--_com.android.email_106944397222682"
Cc: homenet@ietf.org
Subject: Re: [homenet] privacy vs subnet-id
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 06:54:24 -0000

----_com.android.email_106944397222682
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64

CkhvbWVuZXQgYWRtaW4/CgpSYW5keQoKLS0tLS0tLS0gT3JpZ2luYWwgbWVzc2FnZSAtLS0tLS0t
LQpTdWJqZWN0OiBSZTogW2hvbWVuZXRdIHByaXZhY3kgdnMgc3VibmV0LWlkIApGcm9tOiBCcmlh
biBFIENhcnBlbnRlciA8YnJpYW4uZS5jYXJwZW50ZXJAZ21haWwuY29tPiAKVG86IFRpbSBDaG93
biA8dGpjQGVjcy5zb3Rvbi5hYy51az4gCkNDOiAiaG9tZW5ldEBpZXRmLm9yZyBHcm91cCIgPGhv
bWVuZXRAaWV0Zi5vcmc+IAoKT24gMjAxMS0xMS0xNSAxNjowMywgVGltIENob3duIHdyb3RlOgo+
IFNvIGF0IHRoZSBtb21lbnQgYWxsIHRoZSBhcmNoIHRleHQgc2F5cyBvbiBwcml2YWN5IGlzOgo+
wqDCoMKgIFByaXZhY3kgY29uc2lkZXJhdGlvbnMKPiAKPsKgwqDCoMKgwqDCoCBUaGVyZSBhcmUg
bm8gc3BlY2lmaWMgcHJpdmFjeSBjb25jZXJucyBmb3IgdGhpcyB0ZXh0LsKgIEl0IHNob3VsZAo+
wqDCoMKgwqDCoMKgIGJlIG5vdGVkIHRoYXQgbW9zdCBJU1BzIGFyZSBleHBlY3RlZCB0byBvZmZl
ciBzdGF0aWMgSVB2NiBwcmVmaXhlcwo+wqDCoMKgwqDCoMKgIHRvIGN1c3RvbWVycywgYW5kIHRo
dXMgdGhlIGFkZHJlc3NlcyB0aGV5IHVzZSB3b3VsZCBub3QgZ2VuZXJhbGx5Cj7CoMKgwqDCoMKg
wqAgY2hhbmdlIG92ZXIgdGltZS4KPiBXaGF0IHdvdWxkIHlvdSBsaWtlIHRvIHNheSBoZXJlIGlu
c3RlYWQ/CgpNYXliZSBwb2ludCBvdXQgdGhhdCBhIGhvbWVuZXQgY2FuIGJlIHByb3RlY3RlZCBh
Z2FpbnN0IGV4dGVybmFsIHByaXZhY3kKdGhyZWF0cyAocG9zc2libHkgY2l0aW5nIDQ4NjQgZXRj
KSBidXQgdGhhdCB3aGF0ZXZlciBob3N0cyBkbywgdGhlIGhvbWVuZXQKYWRtaW4gaGFzIHRoZSBj
YXBhYmlsaXR5IHRvIHBlcmZvcm0gdHJhZmZpYyBhbmFseXNpcyBkb3duIHRvIHRoZSBzdWJuZXQg
bGV2ZWwuCgrCoMKgwqAgQnJpYW4KCj4gCj4gTm90ZSA0OTQxIGlzbid0IGp1c3QgYWJvdXQgc291
cmNlIGFkZHJlc3MgZnJvbSBsb2NhdGlvbiB0byBsb2NhdGlvbiBidXQgYWxzbyBzb3VyY2UgYWRk
cmVzcyBvdmVyIHRpbWUuCj4gCj4gVGhlIExOUCBmb3IgSVB2NiB0ZXh0IChSRkM0ODY0KSB0YWxr
cyBhYm91dCB0aGlzIGlzc3VlIGEgYml0LCBidXQgdGhpcyBpcyBtb3JlIGFib3V0IG9iZnVzY2F0
aW5nIHRoZSB0b3BvbG9neSBleHRlcm5hbGx5IHRvIHRoZSB1c2VyJ3MgbmV0d29yaywgcmF0aGVy
IHRoYW4gaW50ZXJuYWxseS7CoMKgIEluIG15IHZpZXcgd2Ugc2hvdWxkIHByb2JhYmx5IG9ubHkg
Y29uc2lkZXIgYSBzaW1pbGFyIHBlcnNwZWN0aXZlIGhlcmU/Cj4gCj4gVGltCj4gCj4gT24gMTUg
Tm92IDIwMTEsIGF0IDAyOjUzLCBCcmlhbiBFIENhcnBlbnRlciB3cm90ZToKPiAKPj4gT24gMjAx
MS0xMS0xNSAxNToyNiwgTWljaGFlbCBSaWNoYXJkc29uIHdyb3RlOgo+Pj4gQnJpYW4gQ2FycGVu
dGVyIHJhaXNlZCB0aGUgcG9pbnQgYXQgdGhlIG1pYyB0aGF0IHdlIGhhdmUgdG8gcGF5Cj4+PiBh
dHRlbnRpb24gdG8gcHJpdmFjeSB3aGVuIGl0IGNvbWVzIHRvIHRoZSBzdWJuZXQtaWQuwqAgV2Ug
c2hvdWxkbid0IG1ha2UKPj4+IGl0IHBvc3NpYmxlIGZvciBtZW1iZXJzIG9mIHRoZSBob3VzZWhv
bGQgdG8gc3B5IG9uIGVhY2ggb3RoZXIuCj4+Pgo+Pj4gTXkgdW5kZXJzdGFuZGluZyBvZiB0aGUg
cHVycG9zZSBvZiBSRkM0OTQxIHByaXZhY3kgZXh0ZW5zaW9ucyBpcyB0byBtYWtlCj4+PiBpcyBo
YXJkIGZvciBhbiAob2ZmLXBhdGgpIG9ic2VydmVyIChpbmNsdWRpbmcgd2ViIHNlcnZlciBvcGVy
YXRvcikgdG8KPj4+IHRyaXZpYWxseSB0cmFjayBhIHVzZXIgZnJvbSBsb2NhdGlvbiB0byBsb2Nh
dGlvbiBieSB0aGVpciBFVUktNjQuIAo+Pj4KPj4+IFRoZSBxdWVzdGlvbiBpcywgZG8gd2UgaGF2
ZSBhbnkgc2ltaWxhciByZXF1aXJlbWVudHMgdGhhdCB3ZSB3YW50IHRvCj4+PiBhcHBseSB0byBz
dWJuZXQtaWQuwqAgVGhlIGV4YW1wbGUgdGhhdCBCcmlhbiBnYXZlIGluIFhNUFAgd2FzOgo+Pj4K
Pj4+IEJFQz4gQW5kIGlmIHlvdSBoYXZlIGEgc2VwYXJhdGUgc3VibmV0IGZvciB0aGUga2lkcycg
YmVkcm9vbS4uLgo+Pj4gQkVDPiAnSG9uZXksIG9uZSBvZiB0aGUga2lkcyBpcyB1c2luZyBGYWNl
Ym9vayBhZ2FpbicKPj4+Cj4+PiBpZiB0aGVyZSBpcyBvbmx5IG9uZSBwb3NzaWJsZSBob3N0IG9u
IGEgcGFydGljdWxhciBzdWJuZXQsIHRoZW4gUkZDNDk0MQo+Pj4gY2FuJ3QgaGVscCBkaXNndWlz
ZSB3aG8gaXMgZG9pbmcgd2hhdC7CoCAKPj4+Cj4+PiBNeSBxdWVzdGlvbiBpczogd2hhdCBpcyB0
aGUgcmVhbCBpc3N1ZSBoZXJlLsKgIEl0IHNlZW1zIHRoYXQgdGhlIGtpbmQgb2YKPj4+IHRoaW5n
cyB0aGF0IDQ5NDEgZGVhbHMgd2l0aCwgYXJlIG5laXRoZXIgYmV0dGVyIG5vciB3b3JzZS7CoCBC
dXQgbWF5YmUKPj4+IHRoZXJlIGFyZSBvdGhlciB0aGluZ3MgdGhhdCB3ZSBuZWVkIHRvIGNvbmNl
cm4gb3Vyc2VsdmVzIHdpdGguCj4+IFdheGluZyBwaGlsb3NvcGhpY2FsLCB5b3UgY2FuIG9iZnVz
Y2F0ZSBhbiBJRCBidXQgeW91IGNhbid0IG9iZnVzY2F0ZQo+PiBhIGxvY2F0b3IuIEkgcmVhbGx5
IGRvbid0IHNlZSBhIHdheSBvdXQgb2YgdGhpcy4gSWYgdGhlIGFkbWluIGNhbgo+PiBydW4gV2ly
ZXNoYXJrLCBzaGUgY2FuIHNlZSB0aGUgbG9jYXRvci4KPj4KPj7CoMKgwqAgQnJpYW4KPj4gX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KPj4gaG9tZW5ldCBt
YWlsaW5nIGxpc3QKPj4gaG9tZW5ldEBpZXRmLm9yZwo+PiBodHRwczovL3d3dy5pZXRmLm9yZy9t
YWlsbWFuL2xpc3RpbmZvL2hvbWVuZXQKPiAKPiAKPiAKPiAtLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0KPiAKPiBf
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwo+IGhvbWVuZXQg
bWFpbGluZyBsaXN0Cj4gaG9tZW5ldEBpZXRmLm9yZwo+IGh0dHBzOi8vd3d3LmlldGYub3JnL21h
aWxtYW4vbGlzdGluZm8vaG9tZW5ldApfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fXwpob21lbmV0IG1haWxpbmcgbGlzdApob21lbmV0QGlldGYub3JnCmh0dHBz
Oi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vaG9tZW5ldAoK

----_com.android.email_106944397222682
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: base64

PGh0bWw+PGhlYWQ+PG1ldGEgaHR0cC1lcXVpdj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0
L2h0bWw7IGNoYXJzZXQ9VVRGLTgiPjwvaGVhZD48Ym9keT48ZGl2Pjxicj48L2Rpdj48ZGl2Pkhv
bWVuZXQgYWRtaW4/PC9kaXY+PGRpdj48YnI+PC9kaXY+PGRpdj5SYW5keTwvZGl2Pjxicj48YnI+
PGJyPi0tLS0tLS0tIE9yaWdpbmFsIG1lc3NhZ2UgLS0tLS0tLS08YnI+U3ViamVjdDogUmU6IFto
b21lbmV0XSBwcml2YWN5IHZzIHN1Ym5ldC1pZCA8YnI+RnJvbTogQnJpYW4gRSBDYXJwZW50ZXIg
Jmx0O2JyaWFuLmUuY2FycGVudGVyQGdtYWlsLmNvbSZndDsgPGJyPlRvOiBUaW0gQ2hvd24gJmx0
O3RqY0BlY3Muc290b24uYWMudWsmZ3Q7IDxicj5DQzogImhvbWVuZXRAaWV0Zi5vcmcgR3JvdXAi
ICZsdDtob21lbmV0QGlldGYub3JnJmd0OyA8YnI+PGJyPjxicj48ZGl2IHN0eWxlPSJ3b3JkLWJy
ZWFrOmJyZWFrLWFsbDsiPk9uIDIwMTEtMTEtMTUgMTY6MDMsIFRpbSBDaG93biB3cm90ZTo8YnI+
Jmd0OyBTbyBhdCB0aGUgbW9tZW50IGFsbCB0aGUgYXJjaCB0ZXh0IHNheXMgb24gcHJpdmFjeSBp
czo8YnI+Jmd0OyZuYnNwOyZuYnNwOyZuYnNwOyBQcml2YWN5IGNvbnNpZGVyYXRpb25zPGJyPiZn
dDsgPGJyPiZndDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgVGhlcmUgYXJl
IG5vIHNwZWNpZmljIHByaXZhY3kgY29uY2VybnMgZm9yIHRoaXMgdGV4dC4mbmJzcDsgSXQgc2hv
dWxkPGJyPiZndDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgYmUgbm90ZWQg
dGhhdCBtb3N0IElTUHMgYXJlIGV4cGVjdGVkIHRvIG9mZmVyIHN0YXRpYyBJUHY2IHByZWZpeGVz
PGJyPiZndDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgdG8gY3VzdG9tZXJz
LCBhbmQgdGh1cyB0aGUgYWRkcmVzc2VzIHRoZXkgdXNlIHdvdWxkIG5vdCBnZW5lcmFsbHk8YnI+
Jmd0OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBjaGFuZ2Ugb3ZlciB0aW1l
Ljxicj4mZ3Q7IFdoYXQgd291bGQgeW91IGxpa2UgdG8gc2F5IGhlcmUgaW5zdGVhZD88YnI+PGJy
Pk1heWJlIHBvaW50IG91dCB0aGF0IGEgaG9tZW5ldCBjYW4gYmUgcHJvdGVjdGVkIGFnYWluc3Qg
ZXh0ZXJuYWwgcHJpdmFjeTxicj50aHJlYXRzIChwb3NzaWJseSBjaXRpbmcgNDg2NCBldGMpIGJ1
dCB0aGF0IHdoYXRldmVyIGhvc3RzIGRvLCB0aGUgaG9tZW5ldDxicj5hZG1pbiBoYXMgdGhlIGNh
cGFiaWxpdHkgdG8gcGVyZm9ybSB0cmFmZmljIGFuYWx5c2lzIGRvd24gdG8gdGhlIHN1Ym5ldCBs
ZXZlbC48YnI+PGJyPiZuYnNwOyZuYnNwOyZuYnNwOyBCcmlhbjxicj48YnI+Jmd0OyA8YnI+Jmd0
OyBOb3RlIDQ5NDEgaXNuJ3QganVzdCBhYm91dCBzb3VyY2UgYWRkcmVzcyBmcm9tIGxvY2F0aW9u
IHRvIGxvY2F0aW9uIGJ1dCBhbHNvIHNvdXJjZSBhZGRyZXNzIG92ZXIgdGltZS48YnI+Jmd0OyA8
YnI+Jmd0OyBUaGUgTE5QIGZvciBJUHY2IHRleHQgKFJGQzQ4NjQpIHRhbGtzIGFib3V0IHRoaXMg
aXNzdWUgYSBiaXQsIGJ1dCB0aGlzIGlzIG1vcmUgYWJvdXQgb2JmdXNjYXRpbmcgdGhlIHRvcG9s
b2d5IGV4dGVybmFsbHkgdG8gdGhlIHVzZXIncyBuZXR3b3JrLCByYXRoZXIgdGhhbiBpbnRlcm5h
bGx5LiZuYnNwOyZuYnNwOyBJbiBteSB2aWV3IHdlIHNob3VsZCBwcm9iYWJseSBvbmx5IGNvbnNp
ZGVyIGEgc2ltaWxhciBwZXJzcGVjdGl2ZSBoZXJlPzxicj4mZ3Q7IDxicj4mZ3Q7IFRpbTxicj4m
Z3Q7IDxicj4mZ3Q7IE9uIDE1IE5vdiAyMDExLCBhdCAwMjo1MywgQnJpYW4gRSBDYXJwZW50ZXIg
d3JvdGU6PGJyPiZndDsgPGJyPiZndDsmZ3Q7IE9uIDIwMTEtMTEtMTUgMTU6MjYsIE1pY2hhZWwg
UmljaGFyZHNvbiB3cm90ZTo8YnI+Jmd0OyZndDsmZ3Q7IEJyaWFuIENhcnBlbnRlciByYWlzZWQg
dGhlIHBvaW50IGF0IHRoZSBtaWMgdGhhdCB3ZSBoYXZlIHRvIHBheTxicj4mZ3Q7Jmd0OyZndDsg
YXR0ZW50aW9uIHRvIHByaXZhY3kgd2hlbiBpdCBjb21lcyB0byB0aGUgc3VibmV0LWlkLiZuYnNw
OyBXZSBzaG91bGRuJ3QgbWFrZTxicj4mZ3Q7Jmd0OyZndDsgaXQgcG9zc2libGUgZm9yIG1lbWJl
cnMgb2YgdGhlIGhvdXNlaG9sZCB0byBzcHkgb24gZWFjaCBvdGhlci48YnI+Jmd0OyZndDsmZ3Q7
PGJyPiZndDsmZ3Q7Jmd0OyBNeSB1bmRlcnN0YW5kaW5nIG9mIHRoZSBwdXJwb3NlIG9mIFJGQzQ5
NDEgcHJpdmFjeSBleHRlbnNpb25zIGlzIHRvIG1ha2U8YnI+Jmd0OyZndDsmZ3Q7IGlzIGhhcmQg
Zm9yIGFuIChvZmYtcGF0aCkgb2JzZXJ2ZXIgKGluY2x1ZGluZyB3ZWIgc2VydmVyIG9wZXJhdG9y
KSB0bzxicj4mZ3Q7Jmd0OyZndDsgdHJpdmlhbGx5IHRyYWNrIGEgdXNlciBmcm9tIGxvY2F0aW9u
IHRvIGxvY2F0aW9uIGJ5IHRoZWlyIEVVSS02NC4gPGJyPiZndDsmZ3Q7Jmd0Ozxicj4mZ3Q7Jmd0
OyZndDsgVGhlIHF1ZXN0aW9uIGlzLCBkbyB3ZSBoYXZlIGFueSBzaW1pbGFyIHJlcXVpcmVtZW50
cyB0aGF0IHdlIHdhbnQgdG88YnI+Jmd0OyZndDsmZ3Q7IGFwcGx5IHRvIHN1Ym5ldC1pZC4mbmJz
cDsgVGhlIGV4YW1wbGUgdGhhdCBCcmlhbiBnYXZlIGluIFhNUFAgd2FzOjxicj4mZ3Q7Jmd0OyZn
dDs8YnI+Jmd0OyZndDsmZ3Q7IEJFQyZndDsgQW5kIGlmIHlvdSBoYXZlIGEgc2VwYXJhdGUgc3Vi
bmV0IGZvciB0aGUga2lkcycgYmVkcm9vbS4uLjxicj4mZ3Q7Jmd0OyZndDsgQkVDJmd0OyAnSG9u
ZXksIG9uZSBvZiB0aGUga2lkcyBpcyB1c2luZyBGYWNlYm9vayBhZ2Fpbic8YnI+Jmd0OyZndDsm
Z3Q7PGJyPiZndDsmZ3Q7Jmd0OyBpZiB0aGVyZSBpcyBvbmx5IG9uZSBwb3NzaWJsZSBob3N0IG9u
IGEgcGFydGljdWxhciBzdWJuZXQsIHRoZW4gUkZDNDk0MTxicj4mZ3Q7Jmd0OyZndDsgY2FuJ3Qg
aGVscCBkaXNndWlzZSB3aG8gaXMgZG9pbmcgd2hhdC4mbmJzcDsgPGJyPiZndDsmZ3Q7Jmd0Ozxi
cj4mZ3Q7Jmd0OyZndDsgTXkgcXVlc3Rpb24gaXM6IHdoYXQgaXMgdGhlIHJlYWwgaXNzdWUgaGVy
ZS4mbmJzcDsgSXQgc2VlbXMgdGhhdCB0aGUga2luZCBvZjxicj4mZ3Q7Jmd0OyZndDsgdGhpbmdz
IHRoYXQgNDk0MSBkZWFscyB3aXRoLCBhcmUgbmVpdGhlciBiZXR0ZXIgbm9yIHdvcnNlLiZuYnNw
OyBCdXQgbWF5YmU8YnI+Jmd0OyZndDsmZ3Q7IHRoZXJlIGFyZSBvdGhlciB0aGluZ3MgdGhhdCB3
ZSBuZWVkIHRvIGNvbmNlcm4gb3Vyc2VsdmVzIHdpdGguPGJyPiZndDsmZ3Q7IFdheGluZyBwaGls
b3NvcGhpY2FsLCB5b3UgY2FuIG9iZnVzY2F0ZSBhbiBJRCBidXQgeW91IGNhbid0IG9iZnVzY2F0
ZTxicj4mZ3Q7Jmd0OyBhIGxvY2F0b3IuIEkgcmVhbGx5IGRvbid0IHNlZSBhIHdheSBvdXQgb2Yg
dGhpcy4gSWYgdGhlIGFkbWluIGNhbjxicj4mZ3Q7Jmd0OyBydW4gV2lyZXNoYXJrLCBzaGUgY2Fu
IHNlZSB0aGUgbG9jYXRvci48YnI+Jmd0OyZndDs8YnI+Jmd0OyZndDsmbmJzcDsmbmJzcDsmbmJz
cDsgQnJpYW48YnI+Jmd0OyZndDsgX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX188YnI+Jmd0OyZndDsgaG9tZW5ldCBtYWlsaW5nIGxpc3Q8YnI+Jmd0OyZndDsg
aG9tZW5ldEBpZXRmLm9yZzxicj4mZ3Q7Jmd0OyBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFu
L2xpc3RpbmZvL2hvbWVuZXQ8YnI+Jmd0OyA8YnI+Jmd0OyA8YnI+Jmd0OyA8YnI+Jmd0OyAtLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS08YnI+Jmd0OyA8YnI+Jmd0OyBfX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fXzxicj4mZ3Q7IGhvbWVuZXQgbWFpbGluZyBsaXN0PGJyPiZndDsg
aG9tZW5ldEBpZXRmLm9yZzxicj4mZ3Q7IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlz
dGluZm8vaG9tZW5ldDxicj5fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fXzxicj5ob21lbmV0IG1haWxpbmcgbGlzdDxicj5ob21lbmV0QGlldGYub3JnPGJyPmh0
dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vaG9tZW5ldDxicj48YnI+PC9kaXY+
PC9ib2R5Pg==

----_com.android.email_106944397222682--



From mellon@fugue.com  Mon Nov 14 23:17:12 2011
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 02D5911E8121 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 23:17:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.356
X-Spam-Level: 
X-Spam-Status: No, score=-1.356 tagged_above=-999 required=5 tests=[AWL=-0.153, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kGELfb9VwX-4 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 23:17:11 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 39CF411E8114 for <homenet@ietf.org>; Mon, 14 Nov 2011 23:17:11 -0800 (PST)
Received: from [IPv6:2001:df8::80:b163:16cd:47c3:6fe1] (unknown [IPv6:2001:df8:0:80:b163:16cd:47c3:6fe1]) by toccata.fugue.com (Postfix) with ESMTPSA id 4A5A72381C89; Tue, 15 Nov 2011 02:17:07 -0500 (EST)
References: <D143FF2D6A52E5409FEE8BC1CD3BC54893992FBB98@IRVEXCHCCR01.corp.ad.broadcom.com> <958CCC88-A01D-49FA-9E83-123E62DFAD24@fugue.com> <4EC1F689.9010401@isi.edu> <20111115054440.E839817334CE@drugs.dv.isc.org> <4EC1FF56.9050202@isi.edu> <8A289B2F-4130-4F91-9DB6-5960184FF22D@fugue.com> <4EC205B5.9090208@isi.edu>
In-Reply-To: <4EC205B5.9090208@isi.edu>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <7705F952-FB2D-4658-A865-6B4770CB8B24@fugue.com>
X-Mailer: iPad Mail (9A334)
From: Ted Lemon <mellon@fugue.com>
Date: Tue, 15 Nov 2011 15:17:35 +0800
To: Joe Touch <touch@isi.edu>
Cc: "homenet@ietf.org" <homenet@ietf.org>, "Stephen \[kiwin\] Palm" <palm@broadcom.com>, "mcr@sandelman.ca" <mcr@sandelman.ca>, Mark Andrews <marka@isc.org>
Subject: Re: [homenet] secret sharing among devices
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 07:17:12 -0000

On Nov 15, 2011, at 2:24 PM, Joe Touch <touch@isi.edu> wrote:
> iPhones are (or can be) routers.
> iPhones have no microSD.
> iPhones have a USB port that does not supply power.

Right, we already covered this. You plug them into a USB host device. If you=
 believe this is impractical, okay, but you never expressed that position.=20=

From mellon@fugue.com  Mon Nov 14 23:21:02 2011
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DBDE1F0CED for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 23:21:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.203
X-Spam-Level: 
X-Spam-Status: No, score=-1.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J5oIXk7aswfe for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 23:21:00 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 436861F0CCB for <homenet@ietf.org>; Mon, 14 Nov 2011 23:21:00 -0800 (PST)
Received: from [130.129.86.106] (dhcp-566a.meeting.ietf.org [130.129.86.106]) by toccata.fugue.com (Postfix) with ESMTPSA id 31A312381C89; Tue, 15 Nov 2011 02:20:58 -0500 (EST)
References: <D143FF2D6A52E5409FEE8BC1CD3BC54893992FBB97@IRVEXCHCCR01.corp.ad.broadcom.com> <4EC1E9B5.1020908@bogus.com> <5100D13B-B2CD-48C8-A829-8AFDB9100EAF@fugue.com> <4EC1FC1C.9090208@bogus.com> <6CAC03B6-C5E5-48B3-BE3D-B611BEF54D0C@fugue.com> <4EC20AB1.9060809@bogus.com>
In-Reply-To: <4EC20AB1.9060809@bogus.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <D1B6270E-4CC6-46F4-AC38-AFE7F11BF468@fugue.com>
X-Mailer: iPad Mail (9A334)
From: Ted Lemon <mellon@fugue.com>
Date: Tue, 15 Nov 2011 15:21:25 +0800
To: Joel jaeggli <joelja@bogus.com>
Cc: "homenet@ietf.org" <homenet@ietf.org>, "Stephen \[kiwin\] Palm" <palm@broadcom.com>, "mcr@sandelman.ca" <mcr@sandelman.ca>, "touch@isi.edu" <touch@isi.edu>
Subject: Re: [homenet] secret sharing among devices
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 07:21:03 -0000

On Nov 15, 2011, at 2:46 PM, Joel jaeggli <joelja@bogus.com> wrote:
> It's more concise to describe them as offering no MITM protection. The
> association is either the product of a predefined shared secret (which
> isn't secret) or after bluetooth 2.1 by SSP. the intent to pair in
> either case is deliberately initiated.

Sure. But because the PIN is fixed, accidental pairing is quite possible.

> I expect that devices like the i*/and* as well as other consumer
> electronics that are moving onto the network (like televisions speakers
> and so forth) will continue to down the road towards shedding their
> dependance on tethering to each in a physical fashion. when that happens
> precisely is a business decision on the part of their manufacturers and
> the suppliers of the application stack and the supporting  accoutrements.

I think it's pointless to try to predict Apple's product strategy ten years o=
ut.  For the moment, their connector seems pretty stable. Of course, iPhones=
 have a UI, so perhaps this point is moot anyway. It's devices that don't ha=
ve a UI that are the problem.=20=

From teco@inf-net.nl  Mon Nov 14 23:26:54 2011
Return-Path: <teco@inf-net.nl>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 84C4511E81BB for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 23:26:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.559
X-Spam-Level: 
X-Spam-Status: No, score=-3.559 tagged_above=-999 required=5 tests=[AWL=0.040,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 65KBZi5V4Rsv for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 23:26:54 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 0115411E81A5 for <homenet@ietf.org>; Mon, 14 Nov 2011 23:26:53 -0800 (PST)
Received: by ywt34 with SMTP id 34so5879230ywt.31 for <homenet@ietf.org>; Mon, 14 Nov 2011 23:26:53 -0800 (PST)
Received: by 10.100.234.39 with SMTP id g39mr7297427anh.29.1321342013136; Mon, 14 Nov 2011 23:26:53 -0800 (PST)
Received: from dhcp-13af.meeting.ietf.org (dhcp-13af.meeting.ietf.org. [130.129.19.175]) by mx.google.com with ESMTPS id k20sm70375497ann.15.2011.11.14.23.26.51 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 14 Nov 2011 23:26:52 -0800 (PST)
From: Teco Boot <teco@inf-net.nl>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Tue, 15 Nov 2011 08:26:48 +0100
Message-Id: <060737C7-7665-4431-AA6F-7C77375B8378@inf-net.nl>
To: homenet@ietf.org
Mime-Version: 1.0 (Apple Message framework v1251.1)
X-Mailer: Apple Mail (2.1251.1)
Subject: [homenet] Other comment on draft-acee-ospf-ospfv3-autoconfig-00
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 07:26:54 -0000

On zeroconf and trouble-free OSPFv3 operation, I enjoyed handling MTU =
mismatch trouble a few times. Better prevent on homenets. Mandate having =
MTU-mismatch detection disabled? Set MTU upper limit to 1280 (like =
virtual links)? Select lowest MTU on link?

Teco.








From hansliu@gmail.com  Mon Nov 14 23:55:01 2011
Return-Path: <hansliu@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A4BF1F0CDE for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 23:55:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.499
X-Spam-Level: 
X-Spam-Status: No, score=-3.499 tagged_above=-999 required=5 tests=[AWL=0.100,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QpItJ+1GE+a7 for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 23:55:00 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id A3CE21F0C47 for <homenet@ietf.org>; Mon, 14 Nov 2011 23:55:00 -0800 (PST)
Received: by iaeo4 with SMTP id o4so10531017iae.31 for <homenet@ietf.org>; Mon, 14 Nov 2011 23:55:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=IoxqYyqR5+eHn5GlhZnT5kUPUds070cv6CR8g5FstJE=; b=GSJ2h//uQlDl8LmptuUr8cYVFdcPafi5XW133p2z38a8sSX0z3OroVJjEleBZncVUE j05FTGvAiHTz2pemrNCGf8c6E2Do6GF4aPjw/7ja9ASxuLeXoTO1ntm+AJaD8PAOjyf4 ZMLeaXv392WktH2A3jclcyoTnKxWzwjuQUZCw=
MIME-Version: 1.0
Received: by 10.231.68.130 with SMTP id v2mr5978653ibi.71.1321343700305; Mon, 14 Nov 2011 23:55:00 -0800 (PST)
Received: by 10.231.172.71 with HTTP; Mon, 14 Nov 2011 23:55:00 -0800 (PST)
In-Reply-To: <4EC1CEDC.20702@isi.edu>
References: <13919.1321321547@marajade.sandelman.ca> <4EC1CEDC.20702@isi.edu>
Date: Tue, 15 Nov 2011 15:55:00 +0800
Message-ID: <CAHEOdgtNG7_qHU0x9eOt=8EgQ24co051XrUvr1TGhbs9YG_pCQ@mail.gmail.com>
From: Hans Liu <hansliu@gmail.com>
To: Joe Touch <touch@isi.edu>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: homenet <homenet@ietf.org>, Michael Richardson <mcr@sandelman.ca>
Subject: Re: [homenet] secret sharing among devices
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 07:55:01 -0000

I believe less then 50% home routers have a USB port.

Sincerely,
Hans

On Tue, Nov 15, 2011 at 10:30 AM, Joe Touch <touch@isi.edu> wrote:
>
>
> On 11/14/2011 5:45 PM, Michael Richardson wrote:
>>
>> There have been various discussion in PHL about spreading a secret among
>> devices so they can authenticate each other.
>>
>> A super cool idea is a specifically formatted file on a USB drive,
>> inserted into each system in turn. =C2=A0While we might be pretty sure
>> the USB drive (and file system and connector, etc.) is out of scope, the
>> format for that secret file might be well in scope
>
> Doesn't that assume the device has a USB connector and can mount a stick =
as
> a drive? While that's common on PCs, it's not on home router boxes AFAICT=
.
> Many have no USB at all.
>
> Joe
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>



--=20
Instead of following the fashion, we lead it through.

From brian.e.carpenter@gmail.com  Mon Nov 14 23:57:09 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7095B1F0D0E for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 23:57:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.569
X-Spam-Level: 
X-Spam-Status: No, score=-103.569 tagged_above=-999 required=5 tests=[AWL=0.031, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cwn9f+KE+WKq for <homenet@ietfa.amsl.com>; Mon, 14 Nov 2011 23:57:08 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 8A7EF1F0D0C for <homenet@ietf.org>; Mon, 14 Nov 2011 23:57:08 -0800 (PST)
Received: by ywt34 with SMTP id 34so5910035ywt.31 for <homenet@ietf.org>; Mon, 14 Nov 2011 23:57:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=BX0ExIRe/4mtSJaAZJc5EGkLdgkePRJL927d6UV8ufs=; b=eNQQ8aKOOn1PrmdVfG7FNj7vBEOdOWA0MKfYl5SlOsrMSiVEILIbRR04hgG8D3ZQQG gmK9doxrB8nH1SEg0WyTiUdpm6nv8O5C/hu7pSrknSlj9/7Zwpk8sYZKu8lhoa90H7kM EElBLS/CUdFtOgnewIhXWXx9fCozis8nI7VKA=
Received: by 10.100.23.14 with SMTP id 14mr7464316anw.135.1321343828075; Mon, 14 Nov 2011 23:57:08 -0800 (PST)
Received: from [130.129.19.92] (dhcp-135c.meeting.ietf.org. [130.129.19.92]) by mx.google.com with ESMTPS id u10sm22764197anj.6.2011.11.14.23.57.05 (version=SSLv3 cipher=OTHER); Mon, 14 Nov 2011 23:57:07 -0800 (PST)
Message-ID: <4EC21B4D.2040305@gmail.com>
Date: Tue, 15 Nov 2011 20:57:01 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Randy Turner <rturner@amalfisystems.com>
References: <x8t6f1v0lqimf54q4kw8fq4x.1321340055797@email.android.com>
In-Reply-To: <x8t6f1v0lqimf54q4kw8fq4x.1321340055797@email.android.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: tjc@ecs.soton.ac.uk, homenet@ietf.org
Subject: Re: [homenet] privacy vs subnet-id
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 07:57:09 -0000

The responsible parent, for example, who does not want to
be fined for their kid's illegal downloads.

Regards
   Brian

On 2011-11-15 19:54, Randy Turner wrote:
> Homenet admin?
> 
> Randy
> 
> -------- Original message --------
> Subject: Re: [homenet] privacy vs subnet-id 
> From: Brian E Carpenter <brian.e.carpenter@gmail.com> 
> To: Tim Chown <tjc@ecs.soton.ac.uk> 
> CC: "homenet@ietf.org Group" <homenet@ietf.org> 
> 
> On 2011-11-15 16:03, Tim Chown wrote:
>> So at the moment all the arch text says on privacy is:
>>     Privacy considerations
>>
>>        There are no specific privacy concerns for this text.  It should
>>        be noted that most ISPs are expected to offer static IPv6 prefixes
>>        to customers, and thus the addresses they use would not generally
>>        change over time.
>> What would you like to say here instead?
> 
> Maybe point out that a homenet can be protected against external privacy
> threats (possibly citing 4864 etc) but that whatever hosts do, the homenet
> admin has the capability to perform traffic analysis down to the subnet level.
> 
>     Brian
> 
>> Note 4941 isn't just about source address from location to location but also source address over time.
>>
>> The LNP for IPv6 text (RFC4864) talks about this issue a bit, but this is more about obfuscating the topology externally to the user's network, rather than internally.   In my view we should probably only consider a similar perspective here?
>>
>> Tim
>>
>> On 15 Nov 2011, at 02:53, Brian E Carpenter wrote:
>>
>>> On 2011-11-15 15:26, Michael Richardson wrote:
>>>> Brian Carpenter raised the point at the mic that we have to pay
>>>> attention to privacy when it comes to the subnet-id.  We shouldn't make
>>>> it possible for members of the household to spy on each other.
>>>>
>>>> My understanding of the purpose of RFC4941 privacy extensions is to make
>>>> is hard for an (off-path) observer (including web server operator) to
>>>> trivially track a user from location to location by their EUI-64. 
>>>>
>>>> The question is, do we have any similar requirements that we want to
>>>> apply to subnet-id.  The example that Brian gave in XMPP was:
>>>>
>>>> BEC> And if you have a separate subnet for the kids' bedroom...
>>>> BEC> 'Honey, one of the kids is using Facebook again'
>>>>
>>>> if there is only one possible host on a particular subnet, then RFC4941
>>>> can't help disguise who is doing what.  
>>>>
>>>> My question is: what is the real issue here.  It seems that the kind of
>>>> things that 4941 deals with, are neither better nor worse.  But maybe
>>>> there are other things that we need to concern ourselves with.
>>> Waxing philosophical, you can obfuscate an ID but you can't obfuscate
>>> a locator. I really don't see a way out of this. If the admin can
>>> run Wireshark, she can see the locator.
>>>
>>>     Brian
>>> _______________________________________________
>>> 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
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
> 

From hansliu@gmail.com  Tue Nov 15 00:10:10 2011
Return-Path: <hansliu@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0697F11E812F for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 00:10:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.524
X-Spam-Level: 
X-Spam-Status: No, score=-3.524 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cBW7Ksar0tE3 for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 00:10:09 -0800 (PST)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id BC22D11E8112 for <homenet@ietf.org>; Tue, 15 Nov 2011 00:10:08 -0800 (PST)
Received: by ggnr5 with SMTP id r5so2161213ggn.31 for <homenet@ietf.org>; Tue, 15 Nov 2011 00:10:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=cpG8NjoCB8sMP4N+8hGgIbARwXoaRJWc9hrlkzY5Eok=; b=N2Y1Qitw2gCrkkUKWmuWBhuSCks/o7RQk6edX9p/UeA5hXHwt89fmzo/JvfBYOW8W3 oRghNm0E/MzAKhPohvimUUperOj0dgmdygpkqJoZBzOhxFzV9iFhsHPaT8KV5KmwmpdP NLXJeZsd0AtB1mUOctgF0yNcO8tSqYjME2CUw=
MIME-Version: 1.0
Received: by 10.50.189.231 with SMTP id gl7mr27971937igc.44.1321344604697; Tue, 15 Nov 2011 00:10:04 -0800 (PST)
Received: by 10.231.172.71 with HTTP; Tue, 15 Nov 2011 00:10:04 -0800 (PST)
In-Reply-To: <CAKD1Yr02-uj28JnMnNeFPc-nUYGpp-fobZW7wSY_3WTGH0DaBQ@mail.gmail.com>
References: <4EC1C386.6010802@gmail.com> <CAKD1Yr02-uj28JnMnNeFPc-nUYGpp-fobZW7wSY_3WTGH0DaBQ@mail.gmail.com>
Date: Tue, 15 Nov 2011 16:10:04 +0800
Message-ID: <CAHEOdgt7vza+T1gf0ZT1dNP53rte3Ls=5iNSRgtHMOau+2L1-w@mail.gmail.com>
From: Hans Liu <hansliu@gmail.com>
To: Lorenzo Colitti <lorenzo@google.com>
Content-Type: text/plain; charset=UTF-8
Cc: Hans Liu <Hans_Liu@dlink.com.tw>, homenet@ietf.org
Subject: Re: [homenet] pervasive v4
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 08:10:10 -0000

On Tue, Nov 15, 2011 at 1:42 PM, Lorenzo Colitti <lorenzo@google.com> wrote:
> On Tue, Nov 15, 2011 at 09:42, Brian E Carpenter
> <brian.e.carpenter@gmail.com> wrote:
>>
>> If homenet is going to support arbitrary self-configuring topologies,
>> and pervasive legacy IPv4 is required, we'd surely end up recommending
>> NAT444-within-the-home as the only remotely practicable approach.
>
> Hans from D-Link suggests that another option is simply to bridge IPv4
> packets and route IPv6 packets.

To be very honest, if you have two D-Link router at home, you put one
after another, it won't work today. I believe the problem is quite
general a case to many NAT boxes today since they all share
192.168.0.0/24 or 192.168.1.0/24.  So what I told Lorenzo is that, in
that case I would like to disable NAT and route IPv6.

Regards,
Hans

From touch@isi.edu  Tue Nov 15 00:23:50 2011
Return-Path: <touch@isi.edu>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6ABFE21F8D21 for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 00:23:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.999
X-Spam-Level: 
X-Spam-Status: No, score=-102.999 tagged_above=-999 required=5 tests=[AWL=-0.400, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6kVpT+6PT-SG for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 00:23:49 -0800 (PST)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id C9CB221F8D1F for <homenet@ietf.org>; Tue, 15 Nov 2011 00:23:49 -0800 (PST)
Received: from [130.129.66.136] (dhcp-4288.meeting.ietf.org [130.129.66.136]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id pAF8MdiY020429 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 15 Nov 2011 00:22:44 -0800 (PST)
Message-ID: <4EC2214D.7090903@isi.edu>
Date: Tue, 15 Nov 2011 00:22:37 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Ted Lemon <mellon@fugue.com>
References: <D143FF2D6A52E5409FEE8BC1CD3BC54893992FBB98@IRVEXCHCCR01.corp.ad.broadcom.com> <958CCC88-A01D-49FA-9E83-123E62DFAD24@fugue.com> <4EC1F689.9010401@isi.edu> <20111115054440.E839817334CE@drugs.dv.isc.org> <4EC1FF56.9050202@isi.edu> <8A289B2F-4130-4F91-9DB6-5960184FF22D@fugue.com> <4EC205B5.9090208@isi.edu> <7705F952-FB2D-4658-A865-6B4770CB8B24@fugue.com>
In-Reply-To: <7705F952-FB2D-4658-A865-6B4770CB8B24@fugue.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "homenet@ietf.org" <homenet@ietf.org>, "Stephen \[kiwin\] Palm" <palm@broadcom.com>, "mcr@sandelman.ca" <mcr@sandelman.ca>, Mark Andrews <marka@isc.org>
Subject: Re: [homenet] secret sharing among devices
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 08:23:50 -0000

On 11/14/2011 11:17 PM, Ted Lemon wrote:
> On Nov 15, 2011, at 2:24 PM, Joe Touch<touch@isi.edu>  wrote:
>> iPhones are (or can be) routers.
>> iPhones have no microSD.
>> iPhones have a USB port that does not supply power.
>
> Right, we already covered this. You plug them into a USB host
> device.If you believe this is impractical, okay,
 > but you never expressed that position.

Then let me specify the case:

- verizon home network (no USB on my home router)
- iPhone and iPad (USB clients, but not hosts)
- no PC (use the iCloud service)

Yes, I can exchange files over the iCloud or with bluetooth.

However, the idea of USB as sneakernet is like a stone and chisel already.

Joe

From robert.cragie@gmail.com  Tue Nov 15 00:45:28 2011
Return-Path: <robert.cragie@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C137E21F8FE1 for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 00:45:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.993
X-Spam-Level: 
X-Spam-Status: No, score=-1.993 tagged_above=-999 required=5 tests=[AWL=-0.683, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, SARE_HTML_USL_OBFU=1.666]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3Vp2yV3O8GnJ for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 00:45:28 -0800 (PST)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id B185D21F8FD8 for <homenet@ietf.org>; Tue, 15 Nov 2011 00:45:27 -0800 (PST)
Received: by vcbfl15 with SMTP id fl15so165718vcb.31 for <homenet@ietf.org>; Tue, 15 Nov 2011 00:45:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:reply-to:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=TJ0usL4rfTnhfeNLlVFmulX1MZz6jW3kugWY6lbbvoM=; b=aCJD8zShnoYUCtPCzp/JAOXXhC0ZfVBBI8LNN57y9DXdU1TZSYLtx7b2udcNTryJST 8YdV4R8I55cvxWiSsp/nbbp+1/a3z/hGym154Rems5RQN9jcLqt0lhv6LXm7VLpbHg71 w1a0n+2bmsVdXyhwOc6EMUSll4q4PxluVrUW4=
MIME-Version: 1.0
Received: by 10.220.107.210 with SMTP id c18mr2855273vcp.12.1321346727135; Tue, 15 Nov 2011 00:45:27 -0800 (PST)
Sender: robert.cragie@gmail.com
Received: by 10.220.188.202 with HTTP; Tue, 15 Nov 2011 00:45:26 -0800 (PST)
In-Reply-To: <4EC2214D.7090903@isi.edu>
References: <D143FF2D6A52E5409FEE8BC1CD3BC54893992FBB98@IRVEXCHCCR01.corp.ad.broadcom.com> <958CCC88-A01D-49FA-9E83-123E62DFAD24@fugue.com> <4EC1F689.9010401@isi.edu> <20111115054440.E839817334CE@drugs.dv.isc.org> <4EC1FF56.9050202@isi.edu> <8A289B2F-4130-4F91-9DB6-5960184FF22D@fugue.com> <4EC205B5.9090208@isi.edu> <7705F952-FB2D-4658-A865-6B4770CB8B24@fugue.com> <4EC2214D.7090903@isi.edu>
Date: Tue, 15 Nov 2011 08:45:26 +0000
X-Google-Sender-Auth: GAFWAhp12Mwcykg4BRrcTT1u52U
Message-ID: <CADrU+dL=guFqU+KNSpqu7GAb+2OCh1efeycAmMC9Jxh_G2t3Qg@mail.gmail.com>
From: Robert Cragie <robert.cragie@gridmerge.com>
To: Joe Touch <touch@isi.edu>
Content-Type: multipart/alternative; boundary=f46d043890f34bc89304b1c20267
Cc: "homenet@ietf.org" <homenet@ietf.org>, "Stephen \[kiwin\] Palm" <palm@broadcom.com>, Ted Lemon <mellon@fugue.com>, "mcr@sandelman.ca" <mcr@sandelman.ca>, Mark Andrews <marka@isc.org>
Subject: Re: [homenet] secret sharing among devices
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: robert.cragie@gridmerge.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: Tue, 15 Nov 2011 08:45:28 -0000

--f46d043890f34bc89304b1c20267
Content-Type: text/plain; charset=ISO-8859-1

Is it really that important to specify USB or even a file format here? The
aim is to get a pre-shared key into devices. The underlying cipher suite
will determine the basic size of the key. There may be additional services
to allow the use of a passphrase in conjunction with a hash to generate the
key. How that key/passphrase gets into the device - is this a concern for
the IETF, considering that there are many different ways to physically do
this (e.g. WPS specifies four mechanisms)?

Robert

On Tue, Nov 15, 2011 at 8:22 AM, Joe Touch <touch@isi.edu> wrote:

>
>
> On 11/14/2011 11:17 PM, Ted Lemon wrote:
>
>> On Nov 15, 2011, at 2:24 PM, Joe Touch<touch@isi.edu>  wrote:
>>
>>> iPhones are (or can be) routers.
>>> iPhones have no microSD.
>>> iPhones have a USB port that does not supply power.
>>>
>>
>> Right, we already covered this. You plug them into a USB host
>> device.If you believe this is impractical, okay,
>>
> > but you never expressed that position.
>
> Then let me specify the case:
>
> - verizon home network (no USB on my home router)
> - iPhone and iPad (USB clients, but not hosts)
> - no PC (use the iCloud service)
>
> Yes, I can exchange files over the iCloud or with bluetooth.
>
> However, the idea of USB as sneakernet is like a stone and chisel already.
>
> Joe
>
> ______________________________**_________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/**listinfo/homenet<https://www.ietf.org/mailman/listinfo/homenet>
>



-- 

Robert Cragie

Gridmerge Ltd.
89 Greenfield Crescent,
Wakefield, WF4 4WA, UK
+44 1924 910888
+1 415 513 0064
http://www.gridmerge.com

--f46d043890f34bc89304b1c20267
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Is it really that important to specify USB or even a file format here? The =
aim is to get a pre-shared key into devices. The underlying cipher suite wi=
ll determine the basic size of the key. There may be additional services to=
 allow the use of a passphrase in conjunction with a hash to generate the k=
ey. How that key/passphrase gets into the device - is this a concern for th=
e IETF, considering that there are many different ways to physically do thi=
s (e.g. WPS specifies four mechanisms)?<div>
<br></div><div>Robert<br><br><div class=3D"gmail_quote">On Tue, Nov 15, 201=
1 at 8:22 AM, Joe Touch <span dir=3D"ltr">&lt;<a href=3D"mailto:touch@isi.e=
du">touch@isi.edu</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote=
" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class=3D"im"><br>
<br>
On 11/14/2011 11:17 PM, Ted Lemon wrote:<br>
</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex"><div class=3D"im">
On Nov 15, 2011, at 2:24 PM, Joe Touch&lt;<a href=3D"mailto:touch@isi.edu" =
target=3D"_blank">touch@isi.edu</a>&gt; =A0wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
iPhones are (or can be) routers.<br>
iPhones have no microSD.<br>
iPhones have a USB port that does not supply power.<br>
</blockquote>
<br>
Right, we already covered this. You plug them into a USB host<br></div>
device.If you believe this is impractical, okay,<br>
</blockquote><div class=3D"im">
&gt; but you never expressed that position.<br>
<br></div>
Then let me specify the case:<br>
<br>
- verizon home network (no USB on my home router)<br>
- iPhone and iPad (USB clients, but not hosts)<br>
- no PC (use the iCloud service)<br>
<br>
Yes, I can exchange files over the iCloud or with bluetooth.<br>
<br>
However, the idea of USB as sneakernet is like a stone and chisel already.<=
span class=3D"HOEnZb"><font color=3D"#888888"><br>
<br>
Joe</font></span><div class=3D"HOEnZb"><div class=3D"h5"><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>
</div></div></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>=
<div><p><font face=3D"verdana, sans-serif"><span style=3D"font-size:large">=
Robert Cragie</span></font></p>
<p><font face=3D"tahoma, sans-serif">Gridmerge Ltd.<br>
89 Greenfield Crescent,<br>
Wakefield, WF4 4WA, UK<br>
+44 1924 910888<br>
+1 415 513 0064<br></font>
<a href=3D"http://www.gridmerge.com/" target=3D"_blank"><font face=3D"tahom=
a, sans-serif">http://www.gridmerge.com</font></a></p></div><br>
</div>

--f46d043890f34bc89304b1c20267--

From mellon@fugue.com  Tue Nov 15 00:58:50 2011
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61FBF21F8D03 for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 00:58:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.349
X-Spam-Level: 
X-Spam-Status: No, score=-1.349 tagged_above=-999 required=5 tests=[AWL=-0.146, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QDtW7L2QfhiR for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 00:58:50 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id E672221F8D06 for <homenet@ietf.org>; Tue, 15 Nov 2011 00:58:49 -0800 (PST)
Received: from [IPv6:2001:df8::80:b163:16cd:47c3:6fe1] (unknown [IPv6:2001:df8:0:80:b163:16cd:47c3:6fe1]) by toccata.fugue.com (Postfix) with ESMTPSA id 50D922381DBE; Tue, 15 Nov 2011 03:58:47 -0500 (EST)
References: <D143FF2D6A52E5409FEE8BC1CD3BC54893992FBB98@IRVEXCHCCR01.corp.ad.broadcom.com> <958CCC88-A01D-49FA-9E83-123E62DFAD24@fugue.com> <4EC1F689.9010401@isi.edu> <20111115054440.E839817334CE@drugs.dv.isc.org> <4EC1FF56.9050202@isi.edu> <8A289B2F-4130-4F91-9DB6-5960184FF22D@fugue.com> <4EC205B5.9090208@isi.edu> <7705F952-FB2D-4658-A865-6B4770CB8B24@fugue.com> <4EC2214D.7090903@isi.edu> <CADrU+dL=guFqU+KNSpqu7GAb+2OCh1efeycAmMC9Jxh_G2t3Qg@mail.gmail.com>
In-Reply-To: <CADrU+dL=guFqU+KNSpqu7GAb+2OCh1efeycAmMC9Jxh_G2t3Qg@mail.gmail.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <6323CAC7-3A50-4981-9BFB-A23F0ABDF160@fugue.com>
X-Mailer: iPad Mail (9A334)
From: Ted Lemon <mellon@fugue.com>
Date: Tue, 15 Nov 2011 16:59:16 +0800
To: "robert.cragie@gridmerge.com" <robert.cragie@gridmerge.com>
Cc: "homenet@ietf.org" <homenet@ietf.org>, "Stephen \[kiwin\] Palm" <palm@broadcom.com>, "mcr@sandelman.ca" <mcr@sandelman.ca>, Mark Andrews <marka@isc.org>, Joe Touch <touch@isi.edu>
Subject: Re: [homenet] secret sharing among devices
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 08:58:50 -0000

On Nov 15, 2011, at 4:45 PM, Robert Cragie <robert.cragie@gridmerge.com> wro=
te:
> Is it really that important to specify USB or even a file format here?

What mcr originally proposed was that we define a file format. USB is an exa=
mple of how the file old be exchanged.=20=

From mellon@fugue.com  Tue Nov 15 01:02:54 2011
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00C3C21F8D4B for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 01:02:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.343
X-Spam-Level: 
X-Spam-Status: No, score=-1.343 tagged_above=-999 required=5 tests=[AWL=-0.140, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PQB7AlJa6Koo for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 01:02:53 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 344B421F8D4A for <homenet@ietf.org>; Tue, 15 Nov 2011 01:02:52 -0800 (PST)
Received: from [IPv6:2001:df8::80:b163:16cd:47c3:6fe1] (unknown [IPv6:2001:df8:0:80:b163:16cd:47c3:6fe1]) by toccata.fugue.com (Postfix) with ESMTPSA id 512232381DBE; Tue, 15 Nov 2011 04:02:51 -0500 (EST)
References: <D143FF2D6A52E5409FEE8BC1CD3BC54893992FBB98@IRVEXCHCCR01.corp.ad.broadcom.com> <958CCC88-A01D-49FA-9E83-123E62DFAD24@fugue.com> <4EC1F689.9010401@isi.edu> <20111115054440.E839817334CE@drugs.dv.isc.org> <4EC1FF56.9050202@isi.edu> <8A289B2F-4130-4F91-9DB6-5960184FF22D@fugue.com> <4EC205B5.9090208@isi.edu> <7705F952-FB2D-4658-A865-6B4770CB8B24@fugue.com> <4EC2214D.7090903@isi.edu>
In-Reply-To: <4EC2214D.7090903@isi.edu>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <5F9F2E55-4C5B-4DD6-AEAC-13BACFA7E582@fugue.com>
X-Mailer: iPad Mail (9A334)
From: Ted Lemon <mellon@fugue.com>
Date: Tue, 15 Nov 2011 17:03:20 +0800
To: Joe Touch <touch@isi.edu>
Cc: "homenet@ietf.org" <homenet@ietf.org>, "Stephen \[kiwin\] Palm" <palm@broadcom.com>, "mcr@sandelman.ca" <mcr@sandelman.ca>, Mark Andrews <marka@isc.org>
Subject: Re: [homenet] secret sharing among devices
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 09:02:54 -0000

On Nov 15, 2011, at 4:22 PM, Joe Touch <touch@isi.edu> wrote:
> - verizon home network (no USB on my home router)
> - iPhone and iPad (USB clients, but not hosts)
> - no PC (use the iCloud service)
>=20
So, one router.=20

> Yes, I can exchange files over the iCloud or with bluetooth.
>=20
> However, the idea of USB as sneakernet is like a stone and chisel already.=


I agree in principal, but how do you get your Verizon router to join a homen=
et then?   It has no UI!   If we support this configuration, it means that w=
e have no protection against unintentional router pairing. I don't think tha=
t's acceptable.=20=

From touch@isi.edu  Tue Nov 15 01:11:32 2011
Return-Path: <touch@isi.edu>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 780DC21F8F3E for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 01:11:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.942
X-Spam-Level: 
X-Spam-Status: No, score=-102.942 tagged_above=-999 required=5 tests=[AWL=-0.343, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XcvDUf7GjmPV for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 01:11:31 -0800 (PST)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 11C5E21F8F36 for <homenet@ietf.org>; Tue, 15 Nov 2011 01:11:31 -0800 (PST)
Received: from [130.129.66.136] (dhcp-4288.meeting.ietf.org [130.129.66.136]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id pAF9Aelr001100 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 15 Nov 2011 01:10:44 -0800 (PST)
Message-ID: <4EC22C8F.2050101@isi.edu>
Date: Tue, 15 Nov 2011 01:10:39 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Ted Lemon <mellon@fugue.com>
References: <D143FF2D6A52E5409FEE8BC1CD3BC54893992FBB98@IRVEXCHCCR01.corp.ad.broadcom.com> <958CCC88-A01D-49FA-9E83-123E62DFAD24@fugue.com> <4EC1F689.9010401@isi.edu> <20111115054440.E839817334CE@drugs.dv.isc.org> <4EC1FF56.9050202@isi.edu> <8A289B2F-4130-4F91-9DB6-5960184FF22D@fugue.com> <4EC205B5.9090208@isi.edu> <7705F952-FB2D-4658-A865-6B4770CB8B24@fugue.com> <4EC2214D.7090903@isi.edu> <5F9F2E55-4C5B-4DD6-AEAC-13BACFA7E582@fugue.com>
In-Reply-To: <5F9F2E55-4C5B-4DD6-AEAC-13BACFA7E582@fugue.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "homenet@ietf.org" <homenet@ietf.org>, "Stephen \[kiwin\] Palm" <palm@broadcom.com>, "mcr@sandelman.ca" <mcr@sandelman.ca>, Mark Andrews <marka@isc.org>
Subject: Re: [homenet] secret sharing among devices
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 09:11:32 -0000

On 11/15/2011 1:03 AM, Ted Lemon wrote:
> On Nov 15, 2011, at 4:22 PM, Joe Touch<touch@isi.edu>  wrote:
>> - verizon home network (no USB on my home router)
>> - iPhone and iPad (USB clients, but not hosts)
>> - no PC (use the iCloud service)
>>
> So, one router.

Two that could be used independently (separately) or possibly even 
together. E.g., the following seems entirely reasonable:

	iPad connected as a host

	iPhone as the router gatewayed to 3G
	verizon box as the router gatewayed to DSL

>> Yes, I can exchange files over the iCloud or with bluetooth.
>>
>> However, the idea of USB as sneakernet is like a stone and chisel already.
>
> I agree in principal, but how do you get your Verizon router to join
> ahomenet then? It has no UI!

I'll remember that next time I login using the iPad to alter its config ;-)

> If we support this configuration, it means
> that we have no protection against unintentional router pairing. I don't
> think that's acceptable.

I could upload files to the verizon box over WiFi as I do right now for 
other files (including firmware updates).

Joe

From robert.cragie@gmail.com  Tue Nov 15 01:35:24 2011
Return-Path: <robert.cragie@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0ED8511E81A9 for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 01:35:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[AWL=0.378,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RW7D5AZgRQ+f for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 01:35:23 -0800 (PST)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id A038811E81BF for <homenet@ietf.org>; Tue, 15 Nov 2011 01:35:22 -0800 (PST)
Received: by vcbfl15 with SMTP id fl15so214514vcb.31 for <homenet@ietf.org>; Tue, 15 Nov 2011 01:35:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:reply-to:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=I8Ki8oy3oam6STd159oAlHq+RJ0YU3347wZ58HcZ/So=; b=XMZhuIo5gOdpXZABWiarX27yGmZ8BlT98JrYy9z7pKMneHWylSkdinuJH/hnLCPmcq GbtEaQ1Z5B5VOja1GQEOsFEsK89AR43/RLmAXoWEPSrwuJrURM7xf7DkoOl3smwPvkz5 Sdsf1HkLNw5CNT1wparca9OVJY1gqo/utKDyA=
MIME-Version: 1.0
Received: by 10.52.185.137 with SMTP id fc9mr41102310vdc.100.1321349722188; Tue, 15 Nov 2011 01:35:22 -0800 (PST)
Sender: robert.cragie@gmail.com
Received: by 10.220.188.202 with HTTP; Tue, 15 Nov 2011 01:35:21 -0800 (PST)
In-Reply-To: <6323CAC7-3A50-4981-9BFB-A23F0ABDF160@fugue.com>
References: <D143FF2D6A52E5409FEE8BC1CD3BC54893992FBB98@IRVEXCHCCR01.corp.ad.broadcom.com> <958CCC88-A01D-49FA-9E83-123E62DFAD24@fugue.com> <4EC1F689.9010401@isi.edu> <20111115054440.E839817334CE@drugs.dv.isc.org> <4EC1FF56.9050202@isi.edu> <8A289B2F-4130-4F91-9DB6-5960184FF22D@fugue.com> <4EC205B5.9090208@isi.edu> <7705F952-FB2D-4658-A865-6B4770CB8B24@fugue.com> <4EC2214D.7090903@isi.edu> <CADrU+dL=guFqU+KNSpqu7GAb+2OCh1efeycAmMC9Jxh_G2t3Qg@mail.gmail.com> <6323CAC7-3A50-4981-9BFB-A23F0ABDF160@fugue.com>
Date: Tue, 15 Nov 2011 09:35:21 +0000
X-Google-Sender-Auth: 7S2KQfZ80ysYGj9jDOaBwR4RurI
Message-ID: <CADrU+dJugg-K0jWA+9ztWoCDgwKc0XDV2HD9zX2p05evn1VJcw@mail.gmail.com>
From: Robert Cragie <robert.cragie@gridmerge.com>
To: Ted Lemon <mellon@fugue.com>
Content-Type: multipart/alternative; boundary=bcaec5485950d0a9d404b1c2b405
Cc: "homenet@ietf.org" <homenet@ietf.org>, "Stephen \[kiwin\] Palm" <palm@broadcom.com>, "mcr@sandelman.ca" <mcr@sandelman.ca>, Mark Andrews <marka@isc.org>, Joe Touch <touch@isi.edu>
Subject: Re: [homenet] secret sharing among devices
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: robert.cragie@gridmerge.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: Tue, 15 Nov 2011 09:35:24 -0000

--bcaec5485950d0a9d404b1c2b405
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Nov 15, 2011 at 8:59 AM, Ted Lemon <mellon@fugue.com> wrote:

> On Nov 15, 2011, at 4:45 PM, Robert Cragie <robert.cragie@gridmerge.com>
> wrote:
> > Is it really that important to specify USB or even a file format here?
>
> What mcr originally proposed was that we define a file format. USB is an
> example of how the file old be exchanged.


Exactly, so why all the conversation about USB? This is the domain of
Wi-Fi/ZigBee/HomePlug/UPnP/DLNA, not really the IETF, IMHO.

Robert

--bcaec5485950d0a9d404b1c2b405
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div class=3D"gmail_quote">On Tue, Nov 15, 2011 at 8:59 AM, Ted Lemon <span=
 dir=3D"ltr">&lt;<a href=3D"mailto:mellon@fugue.com">mellon@fugue.com</a>&g=
t;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0=
 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class=3D"im">On Nov 15, 2011, at 4:45 PM, Robert Cragie &lt;<a href=3D=
"mailto:robert.cragie@gridmerge.com">robert.cragie@gridmerge.com</a>&gt; wr=
ote:<br>
&gt; Is it really that important to specify USB or even a file format here?=
<br>
<br>
</div>What mcr originally proposed was that we define a file format. USB is=
 an example of how the file old be exchanged.</blockquote><div>=A0</div><di=
v>Exactly, so why all the conversation about USB? This is the domain of Wi-=
Fi/ZigBee/HomePlug/UPnP/DLNA, not really the IETF, IMHO.</div>
<div><br></div><div>Robert</div></div>

--bcaec5485950d0a9d404b1c2b405--

From Ray.Bellis@nominet.org.uk  Tue Nov 15 01:42:56 2011
Return-Path: <Ray.Bellis@nominet.org.uk>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D846721F8F1A for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 01:42:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.529
X-Spam-Level: 
X-Spam-Status: No, score=-7.529 tagged_above=-999 required=5 tests=[AWL=-0.931, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wt04u-Q92xDc for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 01:42:56 -0800 (PST)
Received: from mx1.knowthenet.org.uk (mx1.knowthenet.org.uk [213.248.199.2]) by ietfa.amsl.com (Postfix) with ESMTP id EE29021F8F16 for <homenet@ietf.org>; Tue, 15 Nov 2011 01:42:50 -0800 (PST)
DomainKey-Signature: s=main.dk.nominet.selector; d=nominet.org.uk; c=nofws; q=dns; h=X-IronPort-AV:Received:Received:From:To:Subject: Thread-Topic:Thread-Index:Date:Message-ID:References: In-Reply-To:Accept-Language:Content-Language: X-MS-Has-Attach:X-MS-TNEF-Correlator:Content-Type: MIME-Version:MIME-Version; b=qwvbyRD+r7VqiCX4f5FUTOJsJOzASdffGtp06quQM9ORWMw9fraR2mOq zazuO5J6M7G9DQKCf/SH+45uNpQJgCbntQ6ZFz5mcUlJ4PeoV2xTlDejL Qzg3qKrvKLpbIR8;
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nominet.org.uk; i=Ray.Bellis@nominet.org.uk; q=dns/txt; s=main.dkim.nominet.selector; t=1321350171; x=1352886171; h=from:sender:reply-to:subject:date:message-id:to:cc: mime-version:content-transfer-encoding:content-id: content-description:resent-date:resent-from:resent-sender: resent-to:resent-cc:resent-message-id:in-reply-to: references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:list-owner:list-archive; z=From:=20Ray=20Bellis=20<Ray.Bellis@nominet.org.uk> |Subject:=20Re:=20[homenet]=20secret=20sharing=20among=20 devices|Date:=20Tue,=2015=20Nov=202011=2009:42:44=20+0000 |Message-ID:=20<88D9EE54-C8B0-445C-BD13-36B6449B1F9E@nomi net.org.uk>|To:=20"homenet@ietf.org"=20<homenet@ietf.org> |MIME-Version:=201.0|In-Reply-To:=20<CADrU+dJugg-K0jWA+9z tWoCDgwKc0XDV2HD9zX2p05evn1VJcw@mail.gmail.com> |References:=20<D143FF2D6A52E5409FEE8BC1CD3BC54893992FBB9 8@IRVEXCHCCR01.corp.ad.broadcom.com>=0D=0A=20<958CCC88-A0 1D-49FA-9E83-123E62DFAD24@fugue.com>=20<4EC1F689.9010401@ isi.edu>=0D=0A=20<20111115054440.E839817334CE@drugs.dv.is c.org>=20<4EC1FF56.9050202@isi.edu>=0D=0A=20<8A289B2F-413 0-4F91-9DB6-5960184FF22D@fugue.com>=20<4EC205B5.9090208@i si.edu>=0D=0A=20<7705F952-FB2D-4658-A865-6B4770CB8B24@fug ue.com>=20<4EC2214D.7090903@isi.edu>=0D=0A=20<CADrU+dL=3D guFqU+KNSpqu7GAb+2OCh1efeycAmMC9Jxh_G2t3Qg@mail.gmail.com >=0D=0A=20<6323CAC7-3A50-4981-9BFB-A23F0ABDF160@fugue.com >=0D=0A=20<CADrU+dJugg-K0jWA+9ztWoCDgwKc0XDV2HD9zX2p05evn 1VJcw@mail.gmail.com>; bh=QD03W3FY6SjjeG1JSaQJyMJLJO8czQuu27jTntehgYs=; b=GnTYoUJu7axSll4vK46jjcQNsB2/PsZpmnPcDKVknKY6MbntGnzLb+Gv IPXMT630ZatzbEPE30jvupo3+avH83huZqdS7J0aXC7MN4e1AeiSn0O7q 8h/e+IwBLTZA4PC;
X-IronPort-AV: E=Sophos;i="4.69,514,1315177200"; d="scan'208,217";a="36613405"
Received: from wds-exc2.okna.nominet.org.uk ([213.248.197.145]) by mx3.nominet.org.uk with ESMTP; 15 Nov 2011 09:42:50 +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%19]) with mapi; Tue, 15 Nov 2011 09:42:49 +0000
From: Ray Bellis <Ray.Bellis@nominet.org.uk>
To: "homenet@ietf.org" <homenet@ietf.org>
Thread-Topic: [homenet] secret sharing among devices
Thread-Index: AQHMo1mq8cc0chU6ok6et4KN/FVTapWtcEYAgAAE5YCAAAKzgIAADrqAgAASK4CAAAZgAIAAA94AgAAKFYCAAAIQAA==
Date: Tue, 15 Nov 2011 09:42:44 +0000
Message-ID: <88D9EE54-C8B0-445C-BD13-36B6449B1F9E@nominet.org.uk>
References: <D143FF2D6A52E5409FEE8BC1CD3BC54893992FBB98@IRVEXCHCCR01.corp.ad.broadcom.com> <958CCC88-A01D-49FA-9E83-123E62DFAD24@fugue.com> <4EC1F689.9010401@isi.edu> <20111115054440.E839817334CE@drugs.dv.isc.org> <4EC1FF56.9050202@isi.edu> <8A289B2F-4130-4F91-9DB6-5960184FF22D@fugue.com> <4EC205B5.9090208@isi.edu> <7705F952-FB2D-4658-A865-6B4770CB8B24@fugue.com> <4EC2214D.7090903@isi.edu> <CADrU+dL=guFqU+KNSpqu7GAb+2OCh1efeycAmMC9Jxh_G2t3Qg@mail.gmail.com> <6323CAC7-3A50-4981-9BFB-A23F0ABDF160@fugue.com> <CADrU+dJugg-K0jWA+9ztWoCDgwKc0XDV2HD9zX2p05evn1VJcw@mail.gmail.com>
In-Reply-To: <CADrU+dJugg-K0jWA+9ztWoCDgwKc0XDV2HD9zX2p05evn1VJcw@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_88D9EE54C8B0445CBD1336B6449B1F9Enominetorguk_"
MIME-Version: 1.0
Subject: Re: [homenet] secret sharing among devices
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 09:42:57 -0000

--_000_88D9EE54C8B0445CBD1336B6449B1F9Enominetorguk_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


On 15 Nov 2011, at 17:35, Robert Cragie wrote:

Exactly, so why all the conversation about USB? This is the domain of Wi-Fi=
/ZigBee/HomePlug/UPnP/DLNA, not really the IETF, IMHO.

<chair hat=3D"on">

Yes, let's please *not* rathole down the actual exchange mechanism.

</chair>

Ray



--_000_88D9EE54C8B0445CBD1336B6449B1F9Enominetorguk_
Content-Type: text/html; charset="iso-8859-1"
Content-ID: <418f17ec-3dd5-4b05-b73d-ed44fad2be63>
Content-Transfer-Encoding: quoted-printable

<html><head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1"></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -=
webkit-line-break: after-white-space; "><br><div><div>On 15 Nov 2011, at 17=
:35, Robert Cragie wrote:</div><blockquote type=3D"cite"><div class=3D"gmai=
l_quote"><font class=3D"Apple-style-span" color=3D"#000000"><br></font><div=
>Exactly, so why all the conversation about USB? This is the domain of Wi-F=
i/ZigBee/HomePlug/UPnP/DLNA, not really the IETF, IMHO.</div>
</div></blockquote><br></div><div>&lt;chair hat=3D&quot;on&quot;&gt;</div><=
div><br></div><div>Yes, let's please *not* rathole down the actual exchange=
 mechanism.</div><div><br></div><div>&lt;/chair&gt;</div><div><br></div><di=
v>Ray</div><div><br></div><br></body></html>=

--_000_88D9EE54C8B0445CBD1336B6449B1F9Enominetorguk_--

From therbst@silverspringnet.com  Tue Nov 15 02:40:50 2011
Return-Path: <therbst@silverspringnet.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E2C911F0C61 for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 02:40:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fpG816Rhg+mZ for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 02:40:50 -0800 (PST)
Received: from it-ipcorp-01.silverspringnet.com (it-ipcorp-01.silverspringnet.com [74.121.22.25]) by ietfa.amsl.com (Postfix) with ESMTP id 4B1CA1F0C5C for <homenet@ietf.org>; Tue, 15 Nov 2011 02:40:50 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AsoEAD1Bwk4KyAE+/2dsb2JhbABDpwaDaYFyAQEBBAEBATc0CxIBCA0BKCwLCyUBAQQBCQQFGYdxrHKOAIoEBIZOgUOReYVThm4
X-IronPort-AV: E=Sophos;i="4.69,514,1315206000";  d="scan'208";a="7793541"
Received: from unknown (HELO IT-EXCA-02.silverspringnet.com) ([10.200.1.62]) by it-ipcorp-01.silverspringnet.com with ESMTP/TLS/AES128-SHA; 15 Nov 2011 02:40:49 -0800
Received: from IT-EXMB-01.silverspringnet.com ([fe80::b81e:2d5b:d263:6c44]) by IT-EXCA-02.silverspringnet.com ([::1]) with mapi; Tue, 15 Nov 2011 02:40:49 -0800
From: Thomas Herbst <therbst@silverspringnet.com>
To: Michael Richardson <mcr@sandelman.ca>, homenet <homenet@ietf.org>
Date: Tue, 15 Nov 2011 02:40:46 -0800
Thread-Topic: [homenet] secret sharing among devices
Thread-Index: AcyjgwnLG9lz8qcNRYqdowXnEv4TeA==
Message-ID: <CAE77F9E.1325F%therbst@silverspringnet.com>
In-Reply-To: <13919.1321321547@marajade.sandelman.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.10.0.110310
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Thomas Herbst <therbst@silverspringnet.com>
Subject: Re: [homenet] secret sharing among devices
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 10:40:51 -0000

Ignoring the transfer mechanism for a moment, why would a home networking
vendor put this on their products?

Support costs are huge in this market.
In a previous job, I was told that support calls with the home router
still in the shrink wrap were about 20% of units sold.
The first call kills all margin, on the second call the vendor has lost
money by selling the product.
Implementing "features" that increase support calls is a very fast way to
be fired.

We should try to stay focused on features that have some chance of being
implemented.

tom

On 11/14/11 5:45 PM, "Michael Richardson" <mcr@sandelman.ca> wrote:

>
>There have been various discussion in PHL about spreading a secret among
>devices so they can authenticate each other.
>
>A super cool idea is a specifically formatted file on a USB drive,
>inserted into each system in turn.  While we might be pretty sure
>the USB drive (and file system and connector, etc.) is out of scope, the
>format for that secret file might be well in scope.
>
>I'd like to suggest that the file format is in scope for the security
>work, and would be willing to document such a thing.  (I actually think
>the KEYPROV work can be readily adapted)
>
>--=20
>]       He who is tired of Weird Al is tired of life!           |
>firewalls  [
>]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net
>architect[
>] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device
>driver[
>   Kyoto Plus: watch the video
><http://www.youtube.com/watch?v=3Dkzx1ycLXQSE>
>	               then sign the petition.
>
>_______________________________________________
>homenet mailing list
>homenet@ietf.org
>https://www.ietf.org/mailman/listinfo/homenet


From mellon@fugue.com  Tue Nov 15 03:12:57 2011
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB6CA21F8F27 for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 03:12:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level: 
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[AWL=0.704,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PHwNoWdUhMxB for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 03:12:57 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id F099E21F8F25 for <homenet@ietf.org>; Tue, 15 Nov 2011 03:12:56 -0800 (PST)
Received: from [172.22.13.155] (unknown [122.147.240.7]) by toccata.fugue.com (Postfix) with ESMTPSA id 4B01D2381E6A; Tue, 15 Nov 2011 06:12:54 -0500 (EST)
References: <D143FF2D6A52E5409FEE8BC1CD3BC54893992FBB98@IRVEXCHCCR01.corp.ad.broadcom.com> <958CCC88-A01D-49FA-9E83-123E62DFAD24@fugue.com> <4EC1F689.9010401@isi.edu> <20111115054440.E839817334CE@drugs.dv.isc.org> <4EC1FF56.9050202@isi.edu> <8A289B2F-4130-4F91-9DB6-5960184FF22D@fugue.com> <4EC205B5.9090208@isi.edu> <7705F952-FB2D-4658-A865-6B4770CB8B24@fugue.com> <4EC2214D.7090903@isi.edu> <5F9F2E55-4C5B-4DD6-AEAC-13BACFA7E582@fugue.com> <4EC22C8F.2050101@isi.edu>
In-Reply-To: <4EC22C8F.2050101@isi.edu>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii
Message-Id: <BCDA8EB7-49C4-4A49-A30C-F9C489ABF7F8@fugue.com>
X-Mailer: iPad Mail (9A334)
From: Ted Lemon <mellon@fugue.com>
Date: Tue, 15 Nov 2011 19:13:23 +0800
To: Joe Touch <touch@isi.edu>
Cc: "homenet@ietf.org" <homenet@ietf.org>, "Stephen \[kiwin\] Palm" <palm@broadcom.com>, "mcr@sandelman.ca" <mcr@sandelman.ca>, Mark Andrews <marka@isc.org>
Subject: Re: [homenet] secret sharing among devices
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 11:12:58 -0000

On Nov 15, 2011, at 5:10 PM, Joe Touch <touch@isi.edu> wrote:
> I'll remember that next time I login using the iPad to alter its config ;-)

IETF geeks are not the target end user!   :)


From mellon@fugue.com  Tue Nov 15 03:19:12 2011
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A62E21F8F8F for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 03:19:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.239
X-Spam-Level: 
X-Spam-Status: No, score=-1.239 tagged_above=-999 required=5 tests=[AWL=-0.036, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pc4q5w1xtlmp for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 03:19:11 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id A9DA521F8F8B for <homenet@ietf.org>; Tue, 15 Nov 2011 03:19:11 -0800 (PST)
Received: from [172.22.13.155] (unknown [122.147.240.7]) by toccata.fugue.com (Postfix) with ESMTPSA id C063C2381E6A; Tue, 15 Nov 2011 06:19:10 -0500 (EST)
References: <CAE77F9E.1325F%therbst@silverspringnet.com>
In-Reply-To: <CAE77F9E.1325F%therbst@silverspringnet.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <DC4012BE-8EA8-440C-8CDB-25CFBECF1BC7@fugue.com>
X-Mailer: iPad Mail (9A334)
From: Ted Lemon <mellon@fugue.com>
Date: Tue, 15 Nov 2011 19:19:40 +0800
To: Thomas Herbst <therbst@silverspringnet.com>
Cc: homenet <homenet@ietf.org>, Thomas Herbst <therbst@silverspringnet.com>, Michael Richardson <mcr@sandelman.ca>
Subject: Re: [homenet] secret sharing among devices
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 11:19:12 -0000

On Nov 15, 2011, at 6:40 PM, Thomas Herbst <therbst@silverspringnet.com> wro=
te:
> Ignoring the transfer mechanism for a moment, why would a home networking
> vendor put this on their products?

The point of it is to prevent problems that would otherwise occur.   For any=
 home router that has hard-wired ethernet ports, we already have a potential=
 solution to this problem that prevents accidental network merges, although I=
 guess we'd have to talk someone in the IEEE into putting forth the actual 8=
02.xxx protocol that would do what we need.

The point is that two devices that haven't physically touched somehow hadn't=
 ought to automatically form a network together.   Believe me, if they do, t=
hat'll generate plenty of support calls.


From rturner@amalfisystems.com  Tue Nov 15 04:10:58 2011
Return-Path: <rturner@amalfisystems.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F4B711E80A0 for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 04:10:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[AWL=-0.697, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EoUVzPZ-ScIO for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 04:10:57 -0800 (PST)
Received: from omr7.networksolutionsemail.com (omr7.networksolutionsemail.com [205.178.146.57]) by ietfa.amsl.com (Postfix) with ESMTP id 712FD21F8BB8 for <homenet@ietf.org>; Tue, 15 Nov 2011 04:10:57 -0800 (PST)
Received: from cm-omr12 (mail.networksolutionsemail.com [205.178.146.50]) by omr7.networksolutionsemail.com (8.13.8/8.13.8) with ESMTP id pAFCAs28026246 for <homenet@ietf.org>; Tue, 15 Nov 2011 07:10:56 -0500
Authentication-Results: cm-omr12 smtp.user=rturner@amalfisystems.com; auth=pass (CRAM-MD5)
X-Authenticated-UID: rturner@amalfisystems.com
Received: from [98.151.18.158] ([98.151.18.158:52543] helo=[192.168.1.111]) by cm-omr12 (envelope-from <rturner@amalfisystems.com>) (ecelerity 2.2.2.41 r(31179/31189)) with ESMTPSA (cipher=AES128-SHA)  id E4/79-03697-DC652CE4; Tue, 15 Nov 2011 07:10:54 -0500
References: <D143FF2D6A52E5409FEE8BC1CD3BC54893992FBB98@IRVEXCHCCR01.corp.ad.broadcom.com> <958CCC88-A01D-49FA-9E83-123E62DFAD24@fugue.com> <4EC1F689.9010401@isi.edu> <20111115054440.E839817334CE@drugs.dv.isc.org> <4EC1FF56.9050202@isi.edu> <8A289B2F-4130-4F91-9DB6-5960184FF22D@fugue.com> <4EC205B5.9090208@isi.edu> <7705F952-FB2D-4658-A865-6B4770CB8B24@fugue.com> <4EC2214D.7090903@isi.edu> <5F9F2E55-4C5B-4DD6-AEAC-13BACFA7E582@fugue.com> <4EC22C8F.2050101@isi.edu> <BCDA8EB7-49C4-4A49-A30C-F9C489ABF7F8@fugue.com>
In-Reply-To: <BCDA8EB7-49C4-4A49-A30C-F9C489ABF7F8@fugue.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <5311180F-7F0C-4804-84E2-2BF9A865A045@amalfisystems.com>
X-Mailer: iPad Mail (9A334)
From: Randy Turner <rturner@amalfisystems.com>
Date: Tue, 15 Nov 2011 04:10:50 -0800
To: Ted Lemon <mellon@fugue.com>
Cc: "homenet@ietf.org" <homenet@ietf.org>, "Stephen \[kiwin\] Palm" <palm@broadcom.com>, "mcr@sandelman.ca" <mcr@sandelman.ca>, Mark Andrews <marka@isc.org>, Joe Touch <touch@isi.edu>
Subject: Re: [homenet] secret sharing among devices
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 12:10:58 -0000

+(n).  ;)



On Nov 15, 2011, at 3:13 AM, Ted Lemon <mellon@fugue.com> wrote:

> On Nov 15, 2011, at 5:10 PM, Joe Touch <touch@isi.edu> wrote:
>> I'll remember that next time I login using the iPad to alter its config ;=
-)
>=20
> IETF geeks are not the target end user!   :)
>=20
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>=20

From touch@isi.edu  Tue Nov 15 04:19:26 2011
Return-Path: <touch@isi.edu>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A62AD21F8F60 for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 04:19:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.881
X-Spam-Level: 
X-Spam-Status: No, score=-102.881 tagged_above=-999 required=5 tests=[AWL=-0.282, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tkxTxklKYQrN for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 04:19:26 -0800 (PST)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id 3597621F8F62 for <homenet@ietf.org>; Tue, 15 Nov 2011 04:19:26 -0800 (PST)
Received: from [130.129.66.136] (dhcp-4288.meeting.ietf.org [130.129.66.136]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id pAFCIU5t023209 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 15 Nov 2011 04:18:41 -0800 (PST)
Message-ID: <4EC25894.6060202@isi.edu>
Date: Tue, 15 Nov 2011 04:18:28 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Ted Lemon <mellon@fugue.com>
References: <D143FF2D6A52E5409FEE8BC1CD3BC54893992FBB98@IRVEXCHCCR01.corp.ad.broadcom.com> <958CCC88-A01D-49FA-9E83-123E62DFAD24@fugue.com> <4EC1F689.9010401@isi.edu> <20111115054440.E839817334CE@drugs.dv.isc.org> <4EC1FF56.9050202@isi.edu> <8A289B2F-4130-4F91-9DB6-5960184FF22D@fugue.com> <4EC205B5.9090208@isi.edu> <7705F952-FB2D-4658-A865-6B4770CB8B24@fugue.com> <4EC2214D.7090903@isi.edu> <5F9F2E55-4C5B-4DD6-AEAC-13BACFA7E582@fugue.com> <4EC22C8F.2050101@isi.edu> <BCDA8EB7-49C4-4A49-A30C-F9C489ABF7F8@fugue.com>
In-Reply-To: <BCDA8EB7-49C4-4A49-A30C-F9C489ABF7F8@fugue.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "homenet@ietf.org" <homenet@ietf.org>, "Stephen \[kiwin\] Palm" <palm@broadcom.com>, "mcr@sandelman.ca" <mcr@sandelman.ca>, Mark Andrews <marka@isc.org>
Subject: Re: [homenet] secret sharing among devices
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 12:19:26 -0000

On 11/15/2011 3:13 AM, Ted Lemon wrote:
> On Nov 15, 2011, at 5:10 PM, Joe Touch<touch@isi.edu>  wrote:
>> I'll remember that next time I login using the iPad to alter its config ;-)
>
> IETF geeks are not the target end user!   :)

IETF geeks aren't the only ones who login to home routers - that's why 
they have web interfaces. Most of the access points in my neighborhood 
all have non-default SSIDs, as a point of reference (and I live in a 
non-tech city).

Joe

From gettysjim@gmail.com  Tue Nov 15 04:59:16 2011
Return-Path: <gettysjim@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 810E721F8CFC for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 04:59:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.901
X-Spam-Level: 
X-Spam-Status: No, score=-2.901 tagged_above=-999 required=5 tests=[AWL=-0.698, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l6cgAf27FSrT for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 04:59:16 -0800 (PST)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 032F721F8BAA for <homenet@ietf.org>; Tue, 15 Nov 2011 04:59:15 -0800 (PST)
Received: by vws5 with SMTP id 5so7441760vws.31 for <homenet@ietf.org>; Tue, 15 Nov 2011 04:59:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=references:in-reply-to:mime-version:content-transfer-encoding :content-type:message-id:cc:x-mailer:from:subject:date:to; bh=GvUuaOPEDpCSn339D1fJjIKXML1VjiTL/3Fkt09lvi8=; b=jmluoKgkcKCm32g9nv44w890xtZR5u3TFwEGGs0J+WAXa6968svWcDvO68JOc985Th ps/R8UJfqWIz4MwvEDor1+LkeE+8LHt+euEvX2Whn58SI5mfqgyz6cNYE0VSE5siCjIx ARCagtc1oBEIRFA+JIcmGAtVHehxRGgZFlzuE=
Received: by 10.52.69.52 with SMTP id b20mr42608759vdu.85.1321361954334; Tue, 15 Nov 2011 04:59:14 -0800 (PST)
Received: from [192.168.1.2] (c-24-63-191-17.hsd1.ma.comcast.net. [24.63.191.17]) by mx.google.com with ESMTPS id j4sm36664146vdk.5.2011.11.15.04.59.12 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 15 Nov 2011 04:59:13 -0800 (PST)
References: <4EC1C386.6010802@gmail.com> <CAKD1Yr02-uj28JnMnNeFPc-nUYGpp-fobZW7wSY_3WTGH0DaBQ@mail.gmail.com> <CAHEOdgt7vza+T1gf0ZT1dNP53rte3Ls=5iNSRgtHMOau+2L1-w@mail.gmail.com>
In-Reply-To: <CAHEOdgt7vza+T1gf0ZT1dNP53rte3Ls=5iNSRgtHMOau+2L1-w@mail.gmail.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <31492919-4C6F-42C0-B837-043DC6D622D1@gmail.com>
X-Mailer: iPad Mail (9A405)
From: Jim Gettys <gettysjim@gmail.com>
Date: Tue, 15 Nov 2011 07:59:10 -0500
To: Hans Liu <hansliu@gmail.com>
X-Mailman-Approved-At: Tue, 15 Nov 2011 05:15:23 -0800
Cc: Hans Liu <Hans_Liu@dlink.com.tw>, "homenet@ietf.org" <homenet@ietf.org>, Lorenzo Colitti <lorenzo@google.com>
Subject: Re: [homenet] pervasive v4
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 12:59:16 -0000

On Nov 15, 2011, at 3:10 AM, Hans Liu <hansliu@gmail.com> wrote:

> On Tue, Nov 15, 2011 at 1:42 PM, Lorenzo Colitti <lorenzo@google.com> wrot=
e:
>> On Tue, Nov 15, 2011 at 09:42, Brian E Carpenter
>> <brian.e.carpenter@gmail.com> wrote:
>>>=20
>>> If homenet is going to support arbitrary self-configuring topologies,
>>> and pervasive legacy IPv4 is required, we'd surely end up recommending
>>> NAT444-within-the-home as the only remotely practicable approach.
>>=20
>> Hans from D-Link suggests that another option is simply to bridge IPv4
>> packets and route IPv6 packets.
>=20
> To be very honest, if you have two D-Link router at home, you put one
> after another, it won't work today. I believe the problem is quite
> general a case to many NAT boxes today since they all share
> 192.168.0.0/24 or 192.168.1.0/24.  So what I told Lorenzo is that, in
> that case I would like to disable NAT and route IPv6.
>=20

Some automatically switch addresses in this case.

Jim

> Regards,
> Hans
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet

From v6ops@globis.net  Tue Nov 15 05:31:09 2011
Return-Path: <v6ops@globis.net>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C01F611E809C for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 05:31:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.47
X-Spam-Level: 
X-Spam-Status: No, score=-2.47 tagged_above=-999 required=5 tests=[AWL=0.128,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YnxYpCz0Ffg2 for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 05:31:09 -0800 (PST)
Received: from globis01.globis.net (RayH-1-pt.tunnel.tserv11.ams1.ipv6.he.net [IPv6:2001:470:1f14:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id 971EE11E80D3 for <homenet@ietf.org>; Tue, 15 Nov 2011 05:31:08 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id A6EDE8700BC; Tue, 15 Nov 2011 14:31:07 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at globis01.globis.net
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 leFQggHPSSn8; Tue, 15 Nov 2011 14:31:02 +0100 (CET)
Received: from Rays-iMac.local (unknown [192.168.0.3]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPA id 0316F870080; Tue, 15 Nov 2011 14:31:01 +0100 (CET)
Message-ID: <4EC26990.9070508@globis.net>
Date: Tue, 15 Nov 2011 14:30:56 +0100
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox Express 1.0.1 (Macintosh/20100705)
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <4EC1C386.6010802@gmail.com>	<4EC1C566.2060400@cisco.com>	<4EC1CC2E.30209@gmail.com>	<4EC1D6C9.3030107@cisco.com>	<CAKD1Yr3rFJonkJ1CbCgGPpr-WDj1RFmR6q4jDab1Toc0tJJodg@mail.gmail.com>	<4EC1FF9A.4080308@bogus.com> <4EC2028E.6050305@gmail.com>
In-Reply-To: <4EC2028E.6050305@gmail.com>
Content-Type: multipart/alternative; boundary="------------010905000508080006080304"
Cc: Joel jaeggli <joelja@bogus.com>, Erik Nordmark <nordmark@cisco.com>, homenet@ietf.org, Lorenzo Colitti <lorenzo@google.com>
Subject: Re: [homenet] pervasive v4
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 13:31:09 -0000

This is a multi-part message in MIME format.
--------------010905000508080006080304
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Exactly the same as today (before Homenet), so presumably they have that 
helpdesk script already.

If you could bridge IPv4 everywhere (as Lorenzo suggested as a 
possibility) one bridge would go into standby mode and it would all just 
work. A tree of NAT44's on all devices will also work just too (as today).

If you start mixing bridging IPv4 with NAT44: that'll be very nasty. 
Ditto mixing autoconfig IPv4 routers and NAT44.

IMHO In the absence of a reliable Homenet topology detection and 
configuration protocol you'd better stick with NAT44 everywhere. This 
has a huge advantage of being backwards compatible with existing devices 
(not unimportant).  Downside is that you have to print a warning on the 
box that arbitrary topologies are not allowed whilst you are still 
running IPv4: just trees.

regards,
RayH

Brian E Carpenter wrote:
> And if the user plugs and plays this:
>
>         WAN
>          |
>       [NAT44]
>          |
> -------------------
>     |           |
> [NAT44]     [NAT44]
>     |           |
> -------------------
>
> what happens? Please script the help desk call.
>
>      Brian
>
> On 2011-11-15 18:58, Joel jaeggli wrote:
>    
>> On 11/15/11 13:49 , Lorenzo Colitti wrote:
>>      
>>> On Tue, Nov 15, 2011 at 11:04, Erik Nordmark<nordmark@cisco.com
>>> <mailto:nordmark@cisco.com>>  wrote:
>>>
>>>      On 11/14/11 6:19 PM, Brian E Carpenter wrote:
>>>
>>>          Yes, but then we're extending v4 and expecting homenets to run
>>>          (presumably) RIP.
>>>
>>>
>>>      Why RIP? Same protocol between the home routers as we will pick for
>>>      routing IPv6 in the home.
>>>
>>>
>>> The primitives you have to configure and renumber IPv6 hosts (multiple
>>> addresses, multiple RAs and address deprecation, and so on) are
>>> different from the ones we have in IPv4 (essentially, DHCPv4 and NAT).
>>>
>>> So I don't think we will be able to take what we do in IPv6 and apply it
>>> as-is to IPv4. Instead, I think we'll have to either NAT everywhere
>>> (like we do today) or bridge everywhere.
>>>        
>> the consumer routinely ends up with double nats today, that's hardly
>> ideal, but it works for the most part. it doesn't seem likely to get
>> better esp as it involves the support of legacy devices.
>>
>>      
>>> _______________________________________________
>>> 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
>>
>>      
>
>    

--------------010905000508080006080304
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html; charset=ISO-8859-1"
 http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Exactly the same as today (before Homenet), so presumably they have
that helpdesk script already.<br>
<br>
If you could bridge IPv4 everywhere (as Lorenzo suggested as a
possibility) one bridge would go into standby mode and it would all
just work. A tree of NAT44's on all devices will also work just too (as
today).<br>
<br>
If you start mixing bridging IPv4 with NAT44: that'll be very nasty.
Ditto mixing autoconfig IPv4 routers and NAT44.<br>
<br>
IMHO In the absence of a reliable Homenet topology detection and
configuration protocol you'd better stick with NAT44 everywhere. This
has a huge advantage of being backwards compatible with existing
devices (not unimportant).&nbsp; Downside is that you have to print a
warning on the box that arbitrary topologies are not allowed whilst you
are still running IPv4: just trees.<br>
<br>
regards,<br>
RayH<br>
<br>
Brian E Carpenter wrote:
<blockquote cite="mid:%3C4EC2028E.6050305@gmail.com%3E" type="cite">
  <pre wrap="">And if the user plugs and plays this:

       WAN
        |
     [NAT44]
        |
-------------------
   |           |
[NAT44]     [NAT44]
   |           |
-------------------

what happens? Please script the help desk call.

    Brian

On 2011-11-15 18:58, Joel jaeggli wrote:
  </pre>
  <blockquote type="cite">
    <pre wrap="">On 11/15/11 13:49 , Lorenzo Colitti wrote:
    </pre>
    <blockquote type="cite">
      <pre wrap="">On Tue, Nov 15, 2011 at 11:04, Erik Nordmark &lt;<a class="moz-txt-link-abbreviated" href="mailto:nordmark@cisco.com">nordmark@cisco.com</a>
<a class="moz-txt-link-rfc2396E" href="mailto:nordmark@cisco.com">&lt;mailto:nordmark@cisco.com&gt;</a>&gt; wrote:

    On 11/14/11 6:19 PM, Brian E Carpenter wrote:

        Yes, but then we're extending v4 and expecting homenets to run
        (presumably) RIP.


    Why RIP? Same protocol between the home routers as we will pick for
    routing IPv6 in the home.


The primitives you have to configure and renumber IPv6 hosts (multiple
addresses, multiple RAs and address deprecation, and so on) are
different from the ones we have in IPv4 (essentially, DHCPv4 and NAT).

So I don't think we will be able to take what we do in IPv6 and apply it
as-is to IPv4. Instead, I think we'll have to either NAT everywhere
(like we do today) or bridge everywhere.
      </pre>
    </blockquote>
    <pre wrap="">the consumer routinely ends up with double nats today, that's hardly
ideal, but it works for the most part. it doesn't seem likely to get
better esp as it involves the support of legacy devices.

    </pre>
    <blockquote type="cite">
      <pre wrap="">_______________________________________________
homenet mailing list
<a class="moz-txt-link-abbreviated" href="mailto:homenet@ietf.org">homenet@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/homenet">https://www.ietf.org/mailman/listinfo/homenet</a>
      </pre>
    </blockquote>
    <pre wrap="">_______________________________________________
homenet mailing list
<a class="moz-txt-link-abbreviated" href="mailto:homenet@ietf.org">homenet@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/homenet">https://www.ietf.org/mailman/listinfo/homenet</a>

    </pre>
  </blockquote>
  <pre wrap=""><!---->
  </pre>
</blockquote>
</body>
</html>

--------------010905000508080006080304--

From therbst@silverspringnet.com  Tue Nov 15 05:48:21 2011
Return-Path: <therbst@silverspringnet.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71C3D21F8CBC for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 05:48:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FyUyyHkTcHjE for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 05:48:21 -0800 (PST)
Received: from it-ipcorp-01.silverspringnet.com (it-ipcorp-01.silverspringnet.com [74.121.22.25]) by ietfa.amsl.com (Postfix) with ESMTP id EF9A721F8CA8 for <homenet@ietf.org>; Tue, 15 Nov 2011 05:48:20 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ap4AAIBswk4KyAE8/2dsb2JhbABEmWWRDYFyAQEBBHkMBgEIDQQCAgEBAQodORQJCAEBBAoEBQgTwSyJLmMEh2IxkXmMQQ
X-IronPort-AV: E=Sophos;i="4.69,515,1315206000";  d="scan'208";a="7795255"
Received: from unknown (HELO IT-EXCA-01.silverspringnet.com) ([10.200.1.60]) by it-ipcorp-01.silverspringnet.com with ESMTP/TLS/AES128-SHA; 15 Nov 2011 05:48:20 -0800
Received: from IT-EXMB-01.silverspringnet.com ([fe80::b81e:2d5b:d263:6c44]) by IT-EXCA-01.silverspringnet.com ([::1]) with mapi; Tue, 15 Nov 2011 05:48:20 -0800
From: Thomas Herbst <therbst@silverspringnet.com>
To: "'mellon@fugue.com'" <mellon@fugue.com>
Date: Tue, 15 Nov 2011 05:48:19 -0800
Thread-Topic: [homenet] secret sharing among devices
Thread-Index: AcyjiGc6d9aAKWzxQ+mw9/DyaF26wAAFNSEt
Message-ID: <625F39517869164ABE7DB2FFB4CA66A730CCE72B@IT-EXMB-01.silverspringnet.com>
In-Reply-To: <DC4012BE-8EA8-440C-8CDB-25CFBECF1BC7@fugue.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "'homenet@ietf.org'" <homenet@ietf.org>, Thomas Herbst <therbst@silverspringnet.com>, "'mcr@sandelman.ca'" <mcr@sandelman.ca>
Subject: Re: [homenet] secret sharing among devices
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 13:48:21 -0000

Like wifi protected setup? Push button, pass phrase, near field coms and us=
b stick, recently reduced to push button and pass phrase.=20

Not an ietf thing.=20


----- Original Message -----
From: Ted Lemon [mailto:mellon@fugue.com]
Sent: Tuesday, November 15, 2011 03:19 AM=0A=
To: Thomas Herbst
Cc: Michael Richardson <mcr@sandelman.ca>; homenet <homenet@ietf.org>; Thom=
as Herbst
Subject: Re: [homenet] secret sharing among devices

On Nov 15, 2011, at 6:40 PM, Thomas Herbst <therbst@silverspringnet.com> wr=
ote:
> Ignoring the transfer mechanism for a moment, why would a home networking
> vendor put this on their products?

The point of it is to prevent problems that would otherwise occur.   For an=
y home router that has hard-wired ethernet ports, we already have a potenti=
al solution to this problem that prevents accidental network merges, althou=
gh I guess we'd have to talk someone in the IEEE into putting forth the act=
ual 802.xxx protocol that would do what we need.

The point is that two devices that haven't physically touched somehow hadn'=
t ought to automatically form a network together.   Believe me, if they do,=
 that'll generate plenty of support calls.


From acee.lindem@ericsson.com  Tue Nov 15 05:49:57 2011
Return-Path: <acee.lindem@ericsson.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0CD511E8082 for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 05:49:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.521
X-Spam-Level: 
X-Spam-Status: No, score=-6.521 tagged_above=-999 required=5 tests=[AWL=0.077,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xc0Mn4XT01Q5 for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 05:49:57 -0800 (PST)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 18D4521F8CB8 for <homenet@ietf.org>; Tue, 15 Nov 2011 05:49:57 -0800 (PST)
Received: from eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id pAFDnohK014179; Tue, 15 Nov 2011 07:49:52 -0600
Received: from EUSAACMS0702.eamcs.ericsson.se ([169.254.1.218]) by eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) with mapi; Tue, 15 Nov 2011 08:49:49 -0500
From: Acee Lindem <acee.lindem@ericsson.com>
To: Lorenzo Colitti <lorenzo@google.com>
Date: Tue, 15 Nov 2011 08:49:47 -0500
Thread-Topic: [homenet] pervasive v4
Thread-Index: AcyjnXEcDOavP3+oSbi6lM8K/NslAA==
Message-ID: <E0439F8C-7BFE-4FF0-B49C-48EEEAC859E1@ericsson.com>
References: <4EC1C386.6010802@gmail.com> <4EC1C566.2060400@cisco.com> <4EC1CC2E.30209@gmail.com> <4EC1D6C9.3030107@cisco.com> <CAKD1Yr3rFJonkJ1CbCgGPpr-WDj1RFmR6q4jDab1Toc0tJJodg@mail.gmail.com>
In-Reply-To: <CAKD1Yr3rFJonkJ1CbCgGPpr-WDj1RFmR6q4jDab1Toc0tJJodg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/signed; boundary="Apple-Mail-53--539595900"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
Cc: Erik Nordmark <nordmark@cisco.com>, "homenet@ietf.org" <homenet@ietf.org>
Subject: Re: [homenet] pervasive v4
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 13:49:57 -0000

--Apple-Mail-53--539595900
Content-Type: multipart/alternative;
	boundary=Apple-Mail-52--539595915


--Apple-Mail-52--539595915
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

+1=20

On Nov 15, 2011, at 12:49 AM, Lorenzo Colitti wrote:

> On Tue, Nov 15, 2011 at 11:04, Erik Nordmark <nordmark@cisco.com> =
wrote:
> On 11/14/11 6:19 PM, Brian E Carpenter wrote:
> Yes, but then we're extending v4 and expecting homenets to run =
(presumably) RIP.
>=20
> Why RIP? Same protocol between the home routers as we will pick for =
routing IPv6 in the home.
>=20
> The primitives you have to configure and renumber IPv6 hosts (multiple =
addresses, multiple RAs and address deprecation, and so on) are =
different from the ones we have in IPv4 (essentially, DHCPv4 and NAT).
>=20
> So I don't think we will be able to take what we do in IPv6 and apply =
it as-is to IPv4. Instead, I think we'll have to either NAT everywhere =
(like we do today) or bridge everywhere.
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet


--Apple-Mail-52--539595915
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">+1&nbsp;<br><div><br><div><div>On Nov 15, 2011, at 12:49 AM, Lorenzo Colitti wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div class="gmail_quote">On Tue, Nov 15, 2011 at 11:04, Erik Nordmark <span dir="ltr">&lt;<a href="mailto:nordmark@cisco.com">nordmark@cisco.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">

<div class="im">On 11/14/11 6:19 PM, Brian E Carpenter wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Yes, but then we're extending v4 and expecting homenets to run (presumably) RIP.<br>
</blockquote>
<br></div>
Why RIP? Same protocol between the home routers as we will pick for routing IPv6 in the home.</blockquote><div><br></div><div>The primitives you have to configure and renumber IPv6 hosts (multiple addresses, multiple RAs and address deprecation, and so on) are different from the ones we have in IPv4 (essentially, DHCPv4 and NAT).</div>

<div><span style="background-color: transparent; "><br></span></div><div><span style="background-color: transparent; ">So I don't think we will be able to take what we do in IPv6 and apply it as-is to IPv4. Instead, I think we'll have to either&nbsp;</span><span style="background-color: transparent; ">NAT everywhere (like we do today) or bridge everywhere.</span></div>

</div>
_______________________________________________<br>homenet mailing list<br><a href="mailto:homenet@ietf.org">homenet@ietf.org</a><br>https://www.ietf.org/mailman/listinfo/homenet<br></blockquote></div><br></div></body></html>
--Apple-Mail-52--539595915--

--Apple-Mail-53--539595900
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIM8jCCBDQw
ggMcoAMCAQICECFWwVQHDV12M/Sr0yNv0sYwDQYJKoZIhvcNAQEFBQAwOTERMA8GA1UECgwIRXJp
Y3Nzb24xJDAiBgNVBAMMG0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMTAeFw0xMDEwMDEyMDA0
NTlaFw0xMzEwMDEyMDA0NDhaMG8xETAPBgNVBAoMCEVyaWNzc29uMR8wHQYDVQQDDBZBY2VlIExp
bmRlbSBMaW5kZW0gSUlJMRAwDgYDVQQFEwdlYWxmbGluMScwJQYJKoZIhvcNAQkBFhhhY2VlLmxp
bmRlbUBlcmljc3Nvbi5jb20wgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAI/Dc9ALiZuBMyuv
bsc3eBxjXZpMi45Z0vzsUQZTJGTBeY7p9JsdzXC9J1uMisBxYVi39R3KJo6I4hXVp9wrA1rxh4AE
bnP1+Gxfpj33uWEFYbBnVAJkIWYWF7CYTn8Zm/yd13vPXtuGA6ESeLnnJafwC9Y0YwUQ+4HX7PNv
uauVAgMBAAGjggGEMIIBgDCBwAYDVR0fBIG4MIG1MIGyoIGvoIGshjdodHRwOi8vY3JsLnRydXN0
LnRlbGlhLmNvbS9Fcmljc3Nvbk5MSW5kaXZpZHVhbENBMDEuY3JshnFsZGFwOi8vbGRhcC50cnVz
dC50ZWxpYS5jb20vY249RXJpY3Nzb24lMjBOTCUyMEluZGl2aWR1YWwlMjBDQTAxLG89RXJpY3Nz
b24/Y2VydGlmaWNhdGVyZXZvY2F0aW9ubGlzdDtiaW5hcnk/YmFzZTAjBgNVHREEHDAagRhhY2Vl
LmxpbmRlbUBlcmljc3Nvbi5jb20wRgYDVR0gBD8wPTA7BgYqhXBrAQEwMTAvBggrBgEFBQcCARYj
aHR0cDovL3d3dy5lcmljc3Nvbi5jb20vbGVnYWwuc2h0bWwwHQYDVR0OBBYEFAgOzAPuplmPr7C1
BTqV94OyqUdhMB8GA1UdIwQYMBaAFJYnw7jepV9dRD45UuVFsXZfYzCbMA4GA1UdDwEB/wQEAwIF
oDANBgkqhkiG9w0BAQUFAAOCAQEAE1gyNW6c2t/YsLxW5sm67+gVGK0Lnge4ub+k8dgGrK7Mj7em
nkOIFkjdv/tqdJ/SoUy/WEkBXba2TfpZ+lfluMgLYux1vSvqBUxYBsUHeNth2Q/Y6A9sCaDTBPlK
vZ2jLz814NavrVfgTCLdxX6zNtGdwzhviz+FyqyxYF43Q86RP8Gd/Npaz1W8pmYAHm0+lezuTx5k
F3Av3+SaZ/MR6s+RWuXEIdED36ajeQz+OG8Mh3nplofzdrOeoWGDz53YlfRhgj+TXo+H1lclZAvD
WVaMMXPdb27h9Hngsq87dkCW9uAyv8DI993rdhqzlEgUyQIL32icAXfTmTYgoGPOwjCCBEUwggMt
oAMCAQICEBPJ6v/eJq2p3KTKI4GDR+MwDQYJKoZIhvcNAQEFBQAwRDEaMBgGA1UECgwRVGVsaWFT
b25lcmEgR3JvdXAxJjAkBgNVBAMMHVRlbGlhU29uZXJhIFB1YmxpYyBSb290IENBIHYxMB4XDTA2
MTAwNjEwMDA1M1oXDTE2MTAwMjA1MDQxN1owOTERMA8GA1UECgwIRXJpY3Nzb24xJDAiBgNVBAMM
G0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoC
ggEBALYQd+Q1HuuHxDyNGFlEPzCxuPPFO5W2xyr+nqCVnNJ4QYFe1HACqavqNLwUGIqIEyHv1rLn
fub9LBc7dQpRHjl/dggin0ONOFJ36nbGEbfHjLJz2BzOWvwl84Sc+Fx09IrDU/SZSWFSfhqTu3TT
39h79brHdRkdPBUgBYgsiFKriHI0TjP5G8628H27BDzqUpzGLSYWgt6/tpwuOH5lcfNfHWMcCYXR
lobv0Klu8lxG5amWqAnqrH6ECOyYJTRbHTsaTIZOHy9Qw/0eXPujKT7tU5xxSI2SdceJqzUbAz2o
FRQ6Px7/GydpM/Rl+qYoGPcauHUL1aSeVJZqDFqcIF0CAwEAAaOCATwwggE4MBIGA1UdEwEB/wQI
MAYBAf8CAQAwRgYDVR0gBD8wPTA7BgcqhXAjAgEBMDAwLgYIKwYBBQUHAgEWImh0dHBzOi8vcmVw
b3NpdG9yeS50cnVzdC50ZWxpYS5jb20wgYkGA1UdHwSBgTB/MH2ge6B5hndsZGFwOi8vbGRhcC50
cnVzdC50ZWxpYS5jb20vY249VGVsaWFTb25lcmElMjBQdWJsaWMlMjBSb290JTIwQ0ElMjB2MSxv
PVRlbGlhU29uZXJhJTIwR3JvdXA/YXV0aG9yaXR5cmV2b2NhdGlvbmxpc3Q/YmFzZTAOBgNVHQ8B
Af8EBAMCAQYwHQYDVR0OBBYEFJYnw7jepV9dRD45UuVFsXZfYzCbMB8GA1UdIwQYMBaAFEXb8I+4
GmKhqCMbY4g4o9vgGmLxMA0GCSqGSIb3DQEBBQUAA4IBAQB2AEoqQz+M3Ra9alkpn/YnwhXIv6tP
jhUvSuNs00Nhd0T9XhlIU3a65CaB/UKSqnayE0t7Q0Qq3r+x/GK3in/mik8i/PK2/q8HutzYFSzz
6Npztpo2JG7AEKOJPVaeebjng45m6vNC7RIfzU9sG2LBR/hewS8s6dFFn70w795xUwJBWZ67OzIK
XrIVVvHTOYpbWA+MESKAXwFhnVONrOTWlVwrMUi4HbiPWpOk+xQbgehCEi7mu3cXsaU1Xq3kMXui
NuC7VKoob8mFO9o9RT+dlirD2uRXwNpvCu3but6Kyhu0+nvy2iXGKjdlxlWTsdDyulXYz+OYCMZ9
lFWRzMIPMIIEbTCCA1WgAwIBAgIRAJywjASay5cieGNithuGWj0wDQYJKoZIhvcNAQEFBQAwOjEZ
MBcGA1UEChMQUlNBIFNlY3VyaXR5IEluYzEdMBsGA1UECxMUUlNBIFNlY3VyaXR5IDIwNDggVjMw
HhcNMDYxMDMxMjA0MjI3WhcNMTYxMTAxMTU0MjI1WjBEMRowGAYDVQQKDBFUZWxpYVNvbmVyYSBH
cm91cDEmMCQGA1UEAwwdVGVsaWFTb25lcmEgUHVibGljIFJvb3QgQ0EgdjEwggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQDKTxADapCAq3mplX4R4gNt+WZe5QKGnaVEQSyY7lICKF5DuVdW
PMLHDjzhw5IzDd860ZZx/0VrhGB3DmP4SDIWCKo2PxvY5NckdBWPWp/T2uaQdOAwgqHpN0pe1X7/
jel59WsWYXKGg/81Wth73ZK/geE7Gz9Pvj1LU6N4YhLMgooxKnCS+ZjB5icWAg+Qd1QpQhF46H1i
bp6LsBWDp56MPpg8F5X6y7MGVcKYLdnLOPs84uxRW9qs1kBopzQBj6s5SyVh8A+j5liDBjghXYpw
/+paGEdqHPeSFYxZKeJatmjEKLYlxcZWRKf436KvQA9jBhMEmytMNbGicR1mRH6tAgMBAAGjggFi
MIIBXjAfBgNVHSMEGDAWgBQHw1EwpKrpRa41JPr/JCwz0LGdjDAdBgNVHQ4EFgQURdvwj7gaYqGo
IxtjiDij2+AaYvEwEgYDVR0TAQH/BAgwBgEB/wIBBDCBhQYDVR0gBH4wfDA9BgkqhkiG9w0FBgEw
MDAuBggrBgEFBQcCARYiaHR0cHM6Ly9yZXBvc2l0b3J5LnRydXN0LnRlbGlhLmNvbTA7BgcqhXAj
AgEBMDAwLgYIKwYBBQUHAgEWImh0dHBzOi8vcmVwb3NpdG9yeS50cnVzdC50ZWxpYS5jb20wcAYD
VR0fBGkwZzBloGOgYYZfaHR0cDovL3d3dy5yc2FzZWN1cml0eS5jb20vcHJvZHVjdHMva2Vvbi9y
ZXBvc2l0b3J5L2NlcnRpZmljYXRlX3N0YXR1cy9SU0FfU2VjdXJpdHlfMjA0OF92My5DUkwwDgYD
VR0PAQH/BAQDAgEGMA0GCSqGSIb3DQEBBQUAA4IBAQAEXpos2CnIm7/872ytSrEHWZgvhOUEkUm2
5PWf/XkWko41TaL9vIS1S6AdWChNqWmnYiS7GfaIiDM9s1D6K7hidWBDOm46bNdM3ZwhMyDCfkDJ
SgeJ0w+7YmjvChu7gWqDZCsbtZ5gA1ixCTdDnuZB67JGSPGW6r73coraDP8diOpiQouMvM6bKuTP
BH/1poLccsUxsKgrQ23JC9LWCRb8cYHkZjXFH1K44TsIl5Lne2oT0JI3pwdA2v6jO4p/OLHntP+n
pjwPbedMPUZkDYCkd3LSxj8c3JTxtA8SlPCtIHE1hh65xihg1JRIliSphrqr9kbfwHdeVxPdOI5G
tDYPMYICEjCCAg4CAQEwTTA5MREwDwYDVQQKDAhFcmljc3NvbjEkMCIGA1UEAwwbRXJpY3Nzb24g
TkwgSW5kaXZpZHVhbCBDQTAxAhAhVsFUBw1ddjP0q9Mjb9LGMAkGBSsOAwIaBQCgggEbMBgGCSqG
SIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMTExNTEzNDk0OFowIwYJKoZI
hvcNAQkEMRYEFCsR0DaAq/i3e0CaXvdjQNayX1T4MFwGCSsGAQQBgjcQBDFPME0wOTERMA8GA1UE
CgwIRXJpY3Nzb24xJDAiBgNVBAMMG0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMQIQIVbBVAcN
XXYz9KvTI2/SxjBeBgsqhkiG9w0BCRACCzFPoE0wOTERMA8GA1UECgwIRXJpY3Nzb24xJDAiBgNV
BAMMG0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMQIQIVbBVAcNXXYz9KvTI2/SxjANBgkqhkiG
9w0BAQEFAASBgIoiffBC38S2eMV+L4xY1PwKIHyLMGvvZTUVbyyixgC2pf6NXdy+UE6cym6ceyFP
nrieesiaOmibDF15X2dBaWSdhd5ph8tSDOD5P5DKQF+vMoI9cFTFyi3MSm//t2Pv8sZpCvi78IJ7
U4ZVE7Ulm92wZrLH89aksMPToqpW424qAAAAAAAA

--Apple-Mail-53--539595900--

From mcr@sandelman.ca  Tue Nov 15 05:53:56 2011
Return-Path: <mcr@sandelman.ca>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE65121F8D2A for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 05:53:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.662
X-Spam-Level: 
X-Spam-Status: No, score=-1.662 tagged_above=-999 required=5 tests=[AWL=0.292,  BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ifm9XvFmDiUI for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 05:53:48 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id 9559C21F8D27 for <homenet@ietf.org>; Tue, 15 Nov 2011 05:53:48 -0800 (PST)
Received: from marajade.sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by relay.sandelman.ca (Postfix) with ESMTPS id 277273418E for <homenet@ietf.org>; Tue, 15 Nov 2011 08:52:22 -0500 (EST)
Received: by marajade.sandelman.ca (Postfix, from userid 179) id B18F598CB3; Tue, 15 Nov 2011 08:53:47 -0500 (EST)
Received: from marajade.sandelman.ca (localhost [127.0.0.1]) by marajade.sandelman.ca (Postfix) with ESMTP id A65FD98CB1 for <homenet@ietf.org>; Tue, 15 Nov 2011 08:53:47 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ca>
To: "'homenet@ietf.org'" <homenet@ietf.org>
In-Reply-To: <D143FF2D6A52E5409FEE8BC1CD3BC54893992FBB97@IRVEXCHCCR01.corp.ad.broadcom.com>
References: <D143FF2D6A52E5409FEE8BC1CD3BC54893992FBB97@IRVEXCHCCR01.corp.ad.broadcom.com>
X-Mailer: MH-E 8.1; nmh 1.3-dev; XEmacs 21.4 (patch 22)
Date: Tue, 15 Nov 2011 08:53:47 -0500
Message-ID: <15129.1321365227@marajade.sandelman.ca>
Sender: mcr@sandelman.ca
Subject: Re: [homenet] secret sharing among devices
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 13:53:56 -0000

>>>>> "Stephen" == Stephen Palm <Stephen> writes:
    Stephen> My phone cannot mount usb devices. Have nio interest to
    Stephen> remove the sdcard 

what's your point?  I wonder if you even read the thread?

Are you saying that your phone is smart (and open) enough to run zOSPF
(mine is), yet can never transfer files at all?   Mine could trivially
scan a QRcode displayed on a laptop screen and do something interesting
with a secret stored in that.  

-- 
]       He who is tired of Weird Al is tired of life!           |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
   Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE>
	               then sign the petition. 



From acee.lindem@ericsson.com  Tue Nov 15 06:06:49 2011
Return-Path: <acee.lindem@ericsson.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C336421F8C94 for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 06:06:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.524
X-Spam-Level: 
X-Spam-Status: No, score=-6.524 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ML0z9gHfdytO for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 06:06:48 -0800 (PST)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 5183521F8B91 for <homenet@ietf.org>; Tue, 15 Nov 2011 06:06:48 -0800 (PST)
Received: from eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id pAFE6jlD016491; Tue, 15 Nov 2011 08:06:47 -0600
Received: from EUSAACMS0702.eamcs.ericsson.se ([169.254.1.218]) by eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) with mapi; Tue, 15 Nov 2011 09:06:45 -0500
From: Acee Lindem <acee.lindem@ericsson.com>
To: Teco Boot <teco@inf-net.nl>
Date: Tue, 15 Nov 2011 09:06:43 -0500
Thread-Topic: [homenet] Other comment on draft-acee-ospf-ospfv3-autoconfig-00
Thread-Index: Acyjn864HNpFbcmgQeO7T2yJqijPZQ==
Message-ID: <0B3B2B6A-7497-450B-824D-125734C7C498@ericsson.com>
References: <060737C7-7665-4431-AA6F-7C77375B8378@inf-net.nl>
In-Reply-To: <060737C7-7665-4431-AA6F-7C77375B8378@inf-net.nl>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/signed; boundary="Apple-Mail-54--538579839"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
Cc: "homenet@ietf.org" <homenet@ietf.org>
Subject: Re: [homenet] Other comment on draft-acee-ospf-ospfv3-autoconfig-00
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 14:06:49 -0000

--Apple-Mail-54--538579839
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi Teco,

On Nov 15, 2011, at 2:26 AM, Teco Boot wrote:

> On zeroconf and trouble-free OSPFv3 operation, I enjoyed handling MTU =
mismatch trouble a few times.

I remember these problems all too well from the days of bridged =
ethernet, FDDI, token ring, and, worst of all, ATM emulated LANs.=20

> Better prevent on homenets. Mandate having MTU-mismatch detection =
disabled? Set MTU upper limit to 1280 (like virtual links)? Select =
lowest MTU on link?

This would definitely make OSPFv3 adjacency formation more robust. =
However, in the case of an MTU mismatch, you have a problem waiting to =
happen independent of whether or not your OSPFv3 adjacencies come up. =
We'll have to think hard about this.=20

Thanks,
Acee=20


>=20
> Teco.
>=20
>=20
>=20
>=20
>=20
>=20
>=20
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet


--Apple-Mail-54--538579839
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIM8jCCBDQw
ggMcoAMCAQICECFWwVQHDV12M/Sr0yNv0sYwDQYJKoZIhvcNAQEFBQAwOTERMA8GA1UECgwIRXJp
Y3Nzb24xJDAiBgNVBAMMG0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMTAeFw0xMDEwMDEyMDA0
NTlaFw0xMzEwMDEyMDA0NDhaMG8xETAPBgNVBAoMCEVyaWNzc29uMR8wHQYDVQQDDBZBY2VlIExp
bmRlbSBMaW5kZW0gSUlJMRAwDgYDVQQFEwdlYWxmbGluMScwJQYJKoZIhvcNAQkBFhhhY2VlLmxp
bmRlbUBlcmljc3Nvbi5jb20wgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAI/Dc9ALiZuBMyuv
bsc3eBxjXZpMi45Z0vzsUQZTJGTBeY7p9JsdzXC9J1uMisBxYVi39R3KJo6I4hXVp9wrA1rxh4AE
bnP1+Gxfpj33uWEFYbBnVAJkIWYWF7CYTn8Zm/yd13vPXtuGA6ESeLnnJafwC9Y0YwUQ+4HX7PNv
uauVAgMBAAGjggGEMIIBgDCBwAYDVR0fBIG4MIG1MIGyoIGvoIGshjdodHRwOi8vY3JsLnRydXN0
LnRlbGlhLmNvbS9Fcmljc3Nvbk5MSW5kaXZpZHVhbENBMDEuY3JshnFsZGFwOi8vbGRhcC50cnVz
dC50ZWxpYS5jb20vY249RXJpY3Nzb24lMjBOTCUyMEluZGl2aWR1YWwlMjBDQTAxLG89RXJpY3Nz
b24/Y2VydGlmaWNhdGVyZXZvY2F0aW9ubGlzdDtiaW5hcnk/YmFzZTAjBgNVHREEHDAagRhhY2Vl
LmxpbmRlbUBlcmljc3Nvbi5jb20wRgYDVR0gBD8wPTA7BgYqhXBrAQEwMTAvBggrBgEFBQcCARYj
aHR0cDovL3d3dy5lcmljc3Nvbi5jb20vbGVnYWwuc2h0bWwwHQYDVR0OBBYEFAgOzAPuplmPr7C1
BTqV94OyqUdhMB8GA1UdIwQYMBaAFJYnw7jepV9dRD45UuVFsXZfYzCbMA4GA1UdDwEB/wQEAwIF
oDANBgkqhkiG9w0BAQUFAAOCAQEAE1gyNW6c2t/YsLxW5sm67+gVGK0Lnge4ub+k8dgGrK7Mj7em
nkOIFkjdv/tqdJ/SoUy/WEkBXba2TfpZ+lfluMgLYux1vSvqBUxYBsUHeNth2Q/Y6A9sCaDTBPlK
vZ2jLz814NavrVfgTCLdxX6zNtGdwzhviz+FyqyxYF43Q86RP8Gd/Npaz1W8pmYAHm0+lezuTx5k
F3Av3+SaZ/MR6s+RWuXEIdED36ajeQz+OG8Mh3nplofzdrOeoWGDz53YlfRhgj+TXo+H1lclZAvD
WVaMMXPdb27h9Hngsq87dkCW9uAyv8DI993rdhqzlEgUyQIL32icAXfTmTYgoGPOwjCCBEUwggMt
oAMCAQICEBPJ6v/eJq2p3KTKI4GDR+MwDQYJKoZIhvcNAQEFBQAwRDEaMBgGA1UECgwRVGVsaWFT
b25lcmEgR3JvdXAxJjAkBgNVBAMMHVRlbGlhU29uZXJhIFB1YmxpYyBSb290IENBIHYxMB4XDTA2
MTAwNjEwMDA1M1oXDTE2MTAwMjA1MDQxN1owOTERMA8GA1UECgwIRXJpY3Nzb24xJDAiBgNVBAMM
G0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoC
ggEBALYQd+Q1HuuHxDyNGFlEPzCxuPPFO5W2xyr+nqCVnNJ4QYFe1HACqavqNLwUGIqIEyHv1rLn
fub9LBc7dQpRHjl/dggin0ONOFJ36nbGEbfHjLJz2BzOWvwl84Sc+Fx09IrDU/SZSWFSfhqTu3TT
39h79brHdRkdPBUgBYgsiFKriHI0TjP5G8628H27BDzqUpzGLSYWgt6/tpwuOH5lcfNfHWMcCYXR
lobv0Klu8lxG5amWqAnqrH6ECOyYJTRbHTsaTIZOHy9Qw/0eXPujKT7tU5xxSI2SdceJqzUbAz2o
FRQ6Px7/GydpM/Rl+qYoGPcauHUL1aSeVJZqDFqcIF0CAwEAAaOCATwwggE4MBIGA1UdEwEB/wQI
MAYBAf8CAQAwRgYDVR0gBD8wPTA7BgcqhXAjAgEBMDAwLgYIKwYBBQUHAgEWImh0dHBzOi8vcmVw
b3NpdG9yeS50cnVzdC50ZWxpYS5jb20wgYkGA1UdHwSBgTB/MH2ge6B5hndsZGFwOi8vbGRhcC50
cnVzdC50ZWxpYS5jb20vY249VGVsaWFTb25lcmElMjBQdWJsaWMlMjBSb290JTIwQ0ElMjB2MSxv
PVRlbGlhU29uZXJhJTIwR3JvdXA/YXV0aG9yaXR5cmV2b2NhdGlvbmxpc3Q/YmFzZTAOBgNVHQ8B
Af8EBAMCAQYwHQYDVR0OBBYEFJYnw7jepV9dRD45UuVFsXZfYzCbMB8GA1UdIwQYMBaAFEXb8I+4
GmKhqCMbY4g4o9vgGmLxMA0GCSqGSIb3DQEBBQUAA4IBAQB2AEoqQz+M3Ra9alkpn/YnwhXIv6tP
jhUvSuNs00Nhd0T9XhlIU3a65CaB/UKSqnayE0t7Q0Qq3r+x/GK3in/mik8i/PK2/q8HutzYFSzz
6Npztpo2JG7AEKOJPVaeebjng45m6vNC7RIfzU9sG2LBR/hewS8s6dFFn70w795xUwJBWZ67OzIK
XrIVVvHTOYpbWA+MESKAXwFhnVONrOTWlVwrMUi4HbiPWpOk+xQbgehCEi7mu3cXsaU1Xq3kMXui
NuC7VKoob8mFO9o9RT+dlirD2uRXwNpvCu3but6Kyhu0+nvy2iXGKjdlxlWTsdDyulXYz+OYCMZ9
lFWRzMIPMIIEbTCCA1WgAwIBAgIRAJywjASay5cieGNithuGWj0wDQYJKoZIhvcNAQEFBQAwOjEZ
MBcGA1UEChMQUlNBIFNlY3VyaXR5IEluYzEdMBsGA1UECxMUUlNBIFNlY3VyaXR5IDIwNDggVjMw
HhcNMDYxMDMxMjA0MjI3WhcNMTYxMTAxMTU0MjI1WjBEMRowGAYDVQQKDBFUZWxpYVNvbmVyYSBH
cm91cDEmMCQGA1UEAwwdVGVsaWFTb25lcmEgUHVibGljIFJvb3QgQ0EgdjEwggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQDKTxADapCAq3mplX4R4gNt+WZe5QKGnaVEQSyY7lICKF5DuVdW
PMLHDjzhw5IzDd860ZZx/0VrhGB3DmP4SDIWCKo2PxvY5NckdBWPWp/T2uaQdOAwgqHpN0pe1X7/
jel59WsWYXKGg/81Wth73ZK/geE7Gz9Pvj1LU6N4YhLMgooxKnCS+ZjB5icWAg+Qd1QpQhF46H1i
bp6LsBWDp56MPpg8F5X6y7MGVcKYLdnLOPs84uxRW9qs1kBopzQBj6s5SyVh8A+j5liDBjghXYpw
/+paGEdqHPeSFYxZKeJatmjEKLYlxcZWRKf436KvQA9jBhMEmytMNbGicR1mRH6tAgMBAAGjggFi
MIIBXjAfBgNVHSMEGDAWgBQHw1EwpKrpRa41JPr/JCwz0LGdjDAdBgNVHQ4EFgQURdvwj7gaYqGo
IxtjiDij2+AaYvEwEgYDVR0TAQH/BAgwBgEB/wIBBDCBhQYDVR0gBH4wfDA9BgkqhkiG9w0FBgEw
MDAuBggrBgEFBQcCARYiaHR0cHM6Ly9yZXBvc2l0b3J5LnRydXN0LnRlbGlhLmNvbTA7BgcqhXAj
AgEBMDAwLgYIKwYBBQUHAgEWImh0dHBzOi8vcmVwb3NpdG9yeS50cnVzdC50ZWxpYS5jb20wcAYD
VR0fBGkwZzBloGOgYYZfaHR0cDovL3d3dy5yc2FzZWN1cml0eS5jb20vcHJvZHVjdHMva2Vvbi9y
ZXBvc2l0b3J5L2NlcnRpZmljYXRlX3N0YXR1cy9SU0FfU2VjdXJpdHlfMjA0OF92My5DUkwwDgYD
VR0PAQH/BAQDAgEGMA0GCSqGSIb3DQEBBQUAA4IBAQAEXpos2CnIm7/872ytSrEHWZgvhOUEkUm2
5PWf/XkWko41TaL9vIS1S6AdWChNqWmnYiS7GfaIiDM9s1D6K7hidWBDOm46bNdM3ZwhMyDCfkDJ
SgeJ0w+7YmjvChu7gWqDZCsbtZ5gA1ixCTdDnuZB67JGSPGW6r73coraDP8diOpiQouMvM6bKuTP
BH/1poLccsUxsKgrQ23JC9LWCRb8cYHkZjXFH1K44TsIl5Lne2oT0JI3pwdA2v6jO4p/OLHntP+n
pjwPbedMPUZkDYCkd3LSxj8c3JTxtA8SlPCtIHE1hh65xihg1JRIliSphrqr9kbfwHdeVxPdOI5G
tDYPMYICEjCCAg4CAQEwTTA5MREwDwYDVQQKDAhFcmljc3NvbjEkMCIGA1UEAwwbRXJpY3Nzb24g
TkwgSW5kaXZpZHVhbCBDQTAxAhAhVsFUBw1ddjP0q9Mjb9LGMAkGBSsOAwIaBQCgggEbMBgGCSqG
SIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMTExNTE0MDY0NFowIwYJKoZI
hvcNAQkEMRYEFGhOWfjlN5+z5L00hejW4qTJYokOMFwGCSsGAQQBgjcQBDFPME0wOTERMA8GA1UE
CgwIRXJpY3Nzb24xJDAiBgNVBAMMG0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMQIQIVbBVAcN
XXYz9KvTI2/SxjBeBgsqhkiG9w0BCRACCzFPoE0wOTERMA8GA1UECgwIRXJpY3Nzb24xJDAiBgNV
BAMMG0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMQIQIVbBVAcNXXYz9KvTI2/SxjANBgkqhkiG
9w0BAQEFAASBgDbltwyUgyy1HBDkeZepy+NlOHHiPo7GRSEEIAcQNsnWa05rmdFy797MQNznhCPc
PA+kLBPmHqn902Ovpr0GSC0Rsae8hzEtSSAvcsxgBqw0TAfsC0iMFzoofL4bljZabyT7uYNJHtZP
BmC09o25Zb9AmkP/XSqeGagNT9zrvnA5AAAAAAAA

--Apple-Mail-54--538579839--

From mcr@sandelman.ca  Tue Nov 15 06:27:39 2011
Return-Path: <mcr@sandelman.ca>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B40521F8CE8 for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 06:27:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.37
X-Spam-Level: 
X-Spam-Status: No, score=-1.37 tagged_above=-999 required=5 tests=[AWL=-0.016,  BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334, J_CHICKENPOX_42=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5uMyO9i05e5U for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 06:27:34 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id 6A50221F8CDE for <homenet@ietf.org>; Tue, 15 Nov 2011 06:27:34 -0800 (PST)
Received: from marajade.sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by relay.sandelman.ca (Postfix) with ESMTPS id 1FA96343CB for <homenet@ietf.org>; Tue, 15 Nov 2011 09:26:05 -0500 (EST)
Received: by marajade.sandelman.ca (Postfix, from userid 179) id DC0DE98CB3; Tue, 15 Nov 2011 09:27:30 -0500 (EST)
Received: from marajade.sandelman.ca (localhost [127.0.0.1]) by marajade.sandelman.ca (Postfix) with ESMTP id D5CAC98CB1 for <homenet@ietf.org>; Tue, 15 Nov 2011 09:27:30 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ca>
To: "homenet@ietf.org" <homenet@ietf.org>
In-Reply-To: <9FDD02CF-065C-4985-89DB-0B7A69579837@fugue.com>
References: <D143FF2D6A52E5409FEE8BC1CD3BC54893992FBB98@IRVEXCHCCR01.corp.ad.broadcom.com> <958CCC88-A01D-49FA-9E83-123E62DFAD24@fugue.com> <4EC1F689.9010401@isi.edu> <9FDD02CF-065C-4985-89DB-0B7A69579837@fugue.com>
X-Mailer: MH-E 8.1; nmh 1.3-dev; XEmacs 21.4 (patch 22)
Date: Tue, 15 Nov 2011 09:27:30 -0500
Message-ID: <19799.1321367250@marajade.sandelman.ca>
Sender: mcr@sandelman.ca
Subject: Re: [homenet] secret sharing among devices
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 14:27:39 -0000

>>>>> "Ted" == Ted Lemon <mellon@fugue.com> writes:
    Ted> It's also possible that it might make sense to use some other
    Ted> medium of exchange that's not USB at all.   For example,
    Ted> routers with ethernet ports can simply be connected together,
    Ted> and there you have a physical link.   But for a wireless device
    Ted> with no ethernet ports, that's not an option. 

Let's talk about the ethernet port exchange here, lest someone get
unduly excited.  Let's understand the benefit / risk / threat.

To make this really secure, you need to do something that can't be bridged,
because if it can be easily bridged, then it can be MITM'ed sent over wifi,
encapsulated into GRE, etc.   

I think really having physical access is important, and it should take
more than a compromised PC with a hardwire to the router to easily do
the transfer, stealing the key remotely for later use.  

I think that this means something like:
  a) using additional symbols at the MII/MLT-3 layer.
  b) playing with PoE drive levels to confirm
  c) near-simultaenous pushing of an out-of-band button.
  d) maybe simultaenous use of wifi (at extremely low power).
  e) using the ethernet cabling in an entirely different fashion
     (e.g. turning it into RS232...)
  f) maybe something LLDP/CDP 
  g) 802.1ag / 802.3ah can do these things...

I do not propose the IETF standardize anything like this, just the
contents which are eventually transfered.

It's clearly the domain of the IEEE, but a single vertically integrated
vendor who has control (or significant influence) right down to the PHY
could easily innovate within their product line, while still
interoperating 

-- 
]       He who is tired of Weird Al is tired of life!           |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
   Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE>
	               then sign the petition. 

From mcr@sandelman.ca  Tue Nov 15 06:34:59 2011
Return-Path: <mcr@sandelman.ca>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 424D121F8DBC for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 06:34:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.67
X-Spam-Level: 
X-Spam-Status: No, score=-1.67 tagged_above=-999 required=5 tests=[AWL=0.284,  BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8fwN6eegAZIT for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 06:34:59 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id 822D321F8DBB for <homenet@ietf.org>; Tue, 15 Nov 2011 06:34:58 -0800 (PST)
Received: from marajade.sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by relay.sandelman.ca (Postfix) with ESMTPS id 6D30E343CB for <homenet@ietf.org>; Tue, 15 Nov 2011 09:33:32 -0500 (EST)
Received: by marajade.sandelman.ca (Postfix, from userid 179) id 5550998CB3; Tue, 15 Nov 2011 09:34:58 -0500 (EST)
Received: from marajade.sandelman.ca (localhost [127.0.0.1]) by marajade.sandelman.ca (Postfix) with ESMTP id 3AEB898CB1 for <homenet@ietf.org>; Tue, 15 Nov 2011 09:34:58 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ca>
To: "homenet@ietf.org" <homenet@ietf.org>
In-Reply-To: <4EC2214D.7090903@isi.edu>
References: <D143FF2D6A52E5409FEE8BC1CD3BC54893992FBB98@IRVEXCHCCR01.corp.ad.broadcom.com> <958CCC88-A01D-49FA-9E83-123E62DFAD24@fugue.com> <4EC1F689.9010401@isi.edu> <20111115054440.E839817334CE@drugs.dv.isc.org> <4EC1FF56.9050202@isi.edu> <8A289B2F-4130-4F91-9DB6-5960184FF22D@fugue.com> <4EC205B5.9090208@isi.edu> <7705F952-FB2D-4658-A865-6B4770CB8B24@fugue.com> <4EC2214D.7090903@isi.edu>
X-Mailer: MH-E 8.1; nmh 1.3-dev; XEmacs 21.4 (patch 22)
Date: Tue, 15 Nov 2011 09:34:58 -0500
Message-ID: <20865.1321367698@marajade.sandelman.ca>
Sender: mcr@sandelman.ca
Subject: Re: [homenet] secret sharing among devices
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 14:34:59 -0000

>>>>> "Joe" == Joe Touch <touch@isi.edu> writes:
    >>> iPhones are (or can be) routers.
    >>> iPhones have no microSD.
    >>> iPhones have a USB port that does not supply power.
    >> 
    >> Right, we already covered this. You plug them into a USB host
    >> device.If you believe this is impractical, okay,
    >> but you never expressed that position.

    Joe> Then let me specify the case:

    Joe> - verizon home network (no USB on my home router)
    Joe> - iPhone and iPad (USB clients, but not hosts)
    Joe> - no PC (use the iCloud service)

Tell me again why you need homenet on such a simple network?


From mcr@sandelman.ca  Tue Nov 15 07:26:41 2011
Return-Path: <mcr@sandelman.ca>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A64FE21F8B49 for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 07:26:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.69
X-Spam-Level: 
X-Spam-Status: No, score=-1.69 tagged_above=-999 required=5 tests=[AWL=0.264,  BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vRADfDY362TW for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 07:26:37 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id 0FCF421F8B2F for <homenet@ietf.org>; Tue, 15 Nov 2011 07:26:34 -0800 (PST)
Received: from marajade.sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by relay.sandelman.ca (Postfix) with ESMTPS id 502BD3418E for <homenet@ietf.org>; Tue, 15 Nov 2011 10:25:09 -0500 (EST)
Received: by marajade.sandelman.ca (Postfix, from userid 179) id 23E7D98CB3; Tue, 15 Nov 2011 10:26:35 -0500 (EST)
Received: from marajade.sandelman.ca (localhost [127.0.0.1]) by marajade.sandelman.ca (Postfix) with ESMTP id 1BCCF98CB1 for <homenet@ietf.org>; Tue, 15 Nov 2011 10:26:35 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ca>
To: homenet@ietf.org
In-Reply-To: <CAKD1Yr3uSsNP4avZBdQE7YxFd7D_KOXBOCsfaRfvnWhJoLoY9Q@mail.gmail.com>
References: <CAKD1Yr3uSsNP4avZBdQE7YxFd7D_KOXBOCsfaRfvnWhJoLoY9Q@mail.gmail.com>
X-Mailer: MH-E 8.1; nmh 1.3-dev; XEmacs 21.4 (patch 22)
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Tue, 15 Nov 2011 10:26:35 -0500
Message-ID: <28079.1321370795@marajade.sandelman.ca>
Sender: mcr@sandelman.ca
Subject: Re: [homenet] Comments on draft-acee-ospf-ospfv3-autoconfig-00
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 15:26:41 -0000

--=-=-=
Content-Transfer-Encoding: quoted-printable


>>>>> "Lorenzo" =3D=3D Lorenzo Colitti <lorenzo@google.com> writes:
    Lorenzo> 4. For security, I think we should pick an auth scheme and
    Lorenzo> stick to it, otherwise
    Lorenzo> it will just lead to fragmentation. Some pre-shared key
    Lorenzo> scheme might be adequate; I don't know much about security
    Lorenzo> so I don't really care what it is, but I do think we need
    Lorenzo> to have one and it needs to be the same for=20
    Lorenzo> everyone. I think we should say MUST here.

So, let me go over the options in order to violently agree.

1) OSPF is multicast, so we can't use any bilteral key-agreement
   protocol on it's own.  Statically keyed AH can be used for multicast
   traffic, and a router can trivially ignore an AH validation failure in
   order to provide some diagnostics by evaluating the contents of
   the OSPF frame. (This requires hacks on platforms that already have
   IPsec, but if you implement the AH inside the OSPF daemon....)

   (so diagnostics can say, "I saw router FOO on interface BLAH, but
   the key didn't match, so I ignored it", or even, "I saw router FOO
   on interface BLAH, and since the key didn't match, I treated it as a
   guest network".  What router FOO thinks of the packets it receives is an
   open question)

2) While we could invoke some kind of group-KMP, these essentially work
   out to a series of bilateral trust relationships which results in the
   master machine giving out the pre-shared secret in a secure fashion.
   The bilateral trust mechanism needs to be anchored by something,=20
   and you can invoke public key mechanisms, or... shared secret.

   Public key mechanisms with a leap-of-faith and then confirmation via UI,
   would be very cool, but completely exceeds our needs.=20=20

3) my understanding is that OSPFv3 eliminated the plain-text HELLO and
   md5 methods.=20

The major thing we need to specify for zOSPF is that we need to pick a
well-known SPI value for the AH header.  That SPI value will need to
specify an algorithm (HMAC-SHA1, HMAC-SHA2, HMAC-SHA3...) and perhaps a
key length.  We should publish a few choices for future interop, but we
will need to pick one MUST for today.  We can't really be resistant
against a bid-down attack, but even HMAC-SHA1 is pretty resistant today
(vs bare SHA1), and I think that we can count upon being able to specify
HMAC-SHA3 for this work.

=2D-=20
]       He who is tired of Weird Al is tired of life!           |  firewall=
s  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net archit=
ect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device dri=
ver[
   Kyoto Plus: watch the video <http://www.youtube.com/watch?v=3Dkzx1ycLXQS=
E>
	               then sign the petition.=20

=20=20=20=20=20=20=20=20
--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iQEVAwUATsKEqoCLcPvd0N1lAQIxAgf/ScMgw5pM2ONCRMr5nHy/S0l3uxdy+Q+y
QkSe3Wd9mR2i72N6wskMBHynxFtag53V44FLnNXRNv6CvR28zalfrlAWzSuVYybA
fnJqNJ2btGT8Da+g1c1wfINLKdAv7xEdtG3y0qY3PiS5CQukNefbIdf1SycB9bj9
T+fxNtcSIw8xde0leRyZat97bsaabXZplTiaIHtJFMCvC61tTpMexF3PpVSL5H+1
Zoz9VzZacU5txITnsg1bBWA9Vbm3gC6UBF1uEGu7iA2ydOryzI6eIyMi5Z7n9ASy
q8oKj/lp1MBTQhdgqdEEHJHsG0NyjosaOQhfJx03CkrjUinUyWFQqQ==
=wiaH
-----END PGP SIGNATURE-----
--=-=-=--

From mcr@sandelman.ca  Tue Nov 15 07:28:09 2011
Return-Path: <mcr@sandelman.ca>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 138BB21F8B1F for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 07:28:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.696
X-Spam-Level: 
X-Spam-Status: No, score=-1.696 tagged_above=-999 required=5 tests=[AWL=0.258,  BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 94rY0jReiV84 for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 07:28:04 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id 0DDF421F8B20 for <homenet@ietf.org>; Tue, 15 Nov 2011 07:27:57 -0800 (PST)
Received: from marajade.sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by relay.sandelman.ca (Postfix) with ESMTPS id 5BAA0343CD for <homenet@ietf.org>; Tue, 15 Nov 2011 10:26:32 -0500 (EST)
Received: by marajade.sandelman.ca (Postfix, from userid 179) id 543C598CB3; Tue, 15 Nov 2011 10:27:58 -0500 (EST)
Received: from marajade.sandelman.ca (localhost [127.0.0.1]) by marajade.sandelman.ca (Postfix) with ESMTP id 52DC198CB1 for <homenet@ietf.org>; Tue, 15 Nov 2011 10:27:58 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ca>
To: "homenet@ietf.org" <homenet@ietf.org>
In-Reply-To: <B3BE775A-4EBB-4C17-9EDC-7B9AFCB8867E@ericsson.com>
References: <CAKD1Yr3uSsNP4avZBdQE7YxFd7D_KOXBOCsfaRfvnWhJoLoY9Q@mail.gmail.com> <B3BE775A-4EBB-4C17-9EDC-7B9AFCB8867E@ericsson.com>
X-Mailer: MH-E 8.1; nmh 1.3-dev; XEmacs 21.4 (patch 22)
Date: Tue, 15 Nov 2011 10:27:58 -0500
Message-ID: <28274.1321370878@marajade.sandelman.ca>
Sender: mcr@sandelman.ca
Subject: Re: [homenet] Comments on draft-acee-ospf-ospfv3-autoconfig-00
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 15:28:09 -0000

>>>>> "Acee" == Acee Lindem <acee.lindem@ericsson.com> writes:
    >> 4. For security, I think we should pick an auth scheme and stick
    >> to it, otherwise it will just lead to fragmentation. Some
    >> pre-shared key scheme might be adequate; I don't know much about
    >> security so I don't really care what it is, but I do think we
    >> need to have one and it needs to be the same for everyone. I
    >> think we should say MUST here. 

    Acee> If the pre-shared key is hard-coded, it is no better than the
    Acee> OSPFv3 Interface Instance ID that is specified to prevent
    Acee> inadvertent adjacencies with routers not supporting the
    Acee> auto-configuration. If configuration of a pre-shared key is
    Acee> required, you no longer have auto-configuration.  

I agree.

-- 
]       He who is tired of Weird Al is tired of life!           |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
   Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE>
	               then sign the petition. 

From mcr@sandelman.ca  Tue Nov 15 07:36:27 2011
Return-Path: <mcr@sandelman.ca>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE33F21F8B79 for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 07:36:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.402
X-Spam-Level: 
X-Spam-Status: No, score=-1.402 tagged_above=-999 required=5 tests=[AWL=-0.048, BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334, J_CHICKENPOX_45=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id elg8mkJmtF5g for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 07:36:23 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id 4046121F8B37 for <homenet@ietf.org>; Tue, 15 Nov 2011 07:36:23 -0800 (PST)
Received: from marajade.sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by relay.sandelman.ca (Postfix) with ESMTPS id A4609343C9 for <homenet@ietf.org>; Tue, 15 Nov 2011 10:34:57 -0500 (EST)
Received: by marajade.sandelman.ca (Postfix, from userid 179) id 7875198CB3; Tue, 15 Nov 2011 10:36:23 -0500 (EST)
Received: from marajade.sandelman.ca (localhost [127.0.0.1]) by marajade.sandelman.ca (Postfix) with ESMTP id 712FA98CB1 for <homenet@ietf.org>; Tue, 15 Nov 2011 10:36:23 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ca>
To: homenet@ietf.org
In-Reply-To: <4EC21B4D.2040305@gmail.com>
References: <x8t6f1v0lqimf54q4kw8fq4x.1321340055797@email.android.com> <4EC21B4D.2040305@gmail.com>
X-Mailer: MH-E 8.1; nmh 1.3-dev; XEmacs 21.4 (patch 22)
Date: Tue, 15 Nov 2011 10:36:23 -0500
Message-ID: <29433.1321371383@marajade.sandelman.ca>
Sender: mcr@sandelman.ca
Subject: Re: [homenet] privacy vs subnet-id
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 15:36:27 -0000

>>>>> "Brian" == Brian E Carpenter <Brian> writes:
    Brian> The responsible parent, for example, who does not want to
    Brian> be fined for their kid's illegal downloads.

So, something that we could specify is some way to name the subnets,
and to communicate from the CPE router to the ISP about what is what,
particularly in the case where the CPE router is provided by and/or
partially managed by the ISP.

The goal here is to give the ISP some information the network topology
so that the ISP and the responsible parent can more easily work out who
is being complained about.  

Said communication doesn't necessarily mean a protocol between the CPE
router and ISP (although it could via INCH or MILE).  It could be as
simple as deciding upon a clear human readable textual description of the
network, something the responsible parent can copy&paste from a web
interface to an email with the ISP.

-- 
]       He who is tired of Weird Al is tired of life!           |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
   Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE>
	               then sign the petition. 


From rturner@amalfisystems.com  Tue Nov 15 08:26:35 2011
Return-Path: <rturner@amalfisystems.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C12561F0C41 for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 08:26:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.252
X-Spam-Level: 
X-Spam-Status: No, score=-1.252 tagged_above=-999 required=5 tests=[AWL=-0.649, BAYES_00=-2.599, J_CHICKENPOX_45=0.6, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5UTw3tLUo8It for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 08:26:31 -0800 (PST)
Received: from omr15.networksolutionsemail.com (omr15.networksolutionsemail.com [205.178.146.65]) by ietfa.amsl.com (Postfix) with ESMTP id 92E751F0C3F for <homenet@ietf.org>; Tue, 15 Nov 2011 08:26:31 -0800 (PST)
Received: from cm-omr1 (mail.networksolutionsemail.com [205.178.146.50]) by omr15.networksolutionsemail.com (8.13.8/8.13.8) with ESMTP id pAFGQRKQ008313 for <homenet@ietf.org>; Tue, 15 Nov 2011 11:26:27 -0500
Authentication-Results: cm-omr1 smtp.user=rturner@amalfisystems.com; auth=pass (CRAM-MD5)
X-Authenticated-UID: rturner@amalfisystems.com
Received: from [98.151.18.158] ([98.151.18.158:52953] helo=[192.168.1.111]) by cm-omr1 (envelope-from <rturner@amalfisystems.com>) (ecelerity 2.2.2.41 r(31179/31189)) with ESMTPSA (cipher=AES128-SHA)  id F5/29-04999-3B292CE4; Tue, 15 Nov 2011 11:26:27 -0500
References: <x8t6f1v0lqimf54q4kw8fq4x.1321340055797@email.android.com> <4EC21B4D.2040305@gmail.com> <29433.1321371383@marajade.sandelman.ca>
In-Reply-To: <29433.1321371383@marajade.sandelman.ca>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <1B5AB373-0180-49DE-A98D-A5F80BD17334@amalfisystems.com>
X-Mailer: iPad Mail (9A334)
From: Randy Turner <rturner@amalfisystems.com>
Date: Tue, 15 Nov 2011 08:26:23 -0800
To: Michael Richardson <mcr@sandelman.ca>
Cc: "homenet@ietf.org" <homenet@ietf.org>
Subject: Re: [homenet] privacy vs subnet-id
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 16:26:35 -0000

Once HomeNet is "figured out", a real subsequent challenge will be to addres=
s how to translate any leftover configuration required for the end user.  Th=
is would be anything we couldn't figure out how to auto-configure. By "trans=
late" I mean translating any geek-speak config concepts into equivalent mass=
 market concepts that can be easily grasped by the average consumer. If we c=
an't figure this out, and the resulting model has too much policy or buttons=
 and levers to manipulate, then we're probably setting up a nice managed ser=
vice offering for an NSP.

Randy



On Nov 15, 2011, at 7:36 AM, Michael Richardson <mcr@sandelman.ca> wrote:

>=20
>>>>>> "Brian" =3D=3D Brian E Carpenter <Brian> writes:
>    Brian> The responsible parent, for example, who does not want to
>    Brian> be fined for their kid's illegal downloads.
>=20
> So, something that we could specify is some way to name the subnets,
> and to communicate from the CPE router to the ISP about what is what,
> particularly in the case where the CPE router is provided by and/or
> partially managed by the ISP.
>=20
> The goal here is to give the ISP some information the network topology
> so that the ISP and the responsible parent can more easily work out who
> is being complained about. =20
>=20
> Said communication doesn't necessarily mean a protocol between the CPE
> router and ISP (although it could via INCH or MILE).  It could be as
> simple as deciding upon a clear human readable textual description of the
> network, something the responsible parent can copy&paste from a web
> interface to an email with the ISP.
>=20
> --=20
> ]       He who is tired of Weird Al is tired of life!           |  firewal=
ls  [
> ]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net archi=
tect[
> ] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device dr=
iver[
>   Kyoto Plus: watch the video <http://www.youtube.com/watch?v=3Dkzx1ycLXQS=
E>
>                   then sign the petition.=20
>=20
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>=20

From cpignata@cisco.com  Tue Nov 15 09:10:54 2011
Return-Path: <cpignata@cisco.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 625FA21F8B01 for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 09:10:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z07HGhTU9DoG for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 09:10:50 -0800 (PST)
Received: from av-tac-rtp.cisco.com (hen.cisco.com [64.102.19.198]) by ietfa.amsl.com (Postfix) with ESMTP id 2AA5721F8AFF for <homenet@ietf.org>; Tue, 15 Nov 2011 09:10:50 -0800 (PST)
X-TACSUNS: Virus Scanned
Received: from chook.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-rtp.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id pAFHAnVG022576 for <homenet@ietf.org>; Tue, 15 Nov 2011 12:10:49 -0500 (EST)
Received: from [10.117.115.62] (rtp-cpignata-89113.cisco.com [10.117.115.62]) by chook.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id pAFHAmvl017892;  Tue, 15 Nov 2011 12:10:48 -0500 (EST)
Message-ID: <4EC29D17.10302@cisco.com>
Date: Tue, 15 Nov 2011 12:10:47 -0500
From: Carlos Pignataro <cpignata@cisco.com>
Organization: cisco Systems, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.24) Gecko/20100228 Thunderbird/2.0.0.24 Mnenhy/0.7.6.0
MIME-Version: 1.0
To: Acee Lindem <acee.lindem@ericsson.com>
References: <CAKD1Yr3uSsNP4avZBdQE7YxFd7D_KOXBOCsfaRfvnWhJoLoY9Q@mail.gmail.com> <B3BE775A-4EBB-4C17-9EDC-7B9AFCB8867E@ericsson.com> <CAKD1Yr0MFdyBopr0E0WiebLSZ+M2J9vAi1U6b66VxhziE2XJpw@mail.gmail.com> <FF6FB9A0-9F91-4658-A265-BA200A0858AF@ericsson.com>
In-Reply-To: <FF6FB9A0-9F91-4658-A265-BA200A0858AF@ericsson.com>
X-Enigmail-Version: 1.3.3
X-Face: *3w8NvnQ|kS~V{&{U}$?G9U9EJQ8p9)O[1[1F'1i>XIc$5FR!hdAIf5}'Xu-3`^Z']h0J* ccB'fl/XJYR[+,Z+jj`4%06nd'y9[ln&ScJT5S+O18e^
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "homenet@ietf.org" <homenet@ietf.org>, Jari Arkko <jari.arkko@piuha.net>, Lorenzo Colitti <lorenzo@google.com>
Subject: Re: [homenet] Comments on draft-acee-ospf-ospfv3-autoconfig-00
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 17:10:54 -0000

Hi Acee,

On 11/14/2011 10:11 PM, Acee Lindem wrote:
> 
> On Nov 14, 2011, at 9:46 PM, Lorenzo Colitti wrote:
> 
>> On Tue, Nov 15, 2011 at 10:25, Acee Lindem <acee.lindem@ericsson.com
>> <mailto:acee.lindem@ericsson.com>> wrote:
>>
>>     > 1. I think the OSPFv3 router ID should not be based on the MAC
>>     address because that will encourage people to assume it's unique
>>     "most of the time". I think we should just make it a pseudo-random
>>     number so it's clear that uniqueness is only guaranteed by
>>     collision detection and that collision detection needs to be robust.
>>
>>     The draft requires duplicate Router-ID detection and resolution. I
>>     don't think that the fact that a portion of the MAC address is
>>     used as a first try is reason for this detection/resolution not to
>>     be implemented or tested.
>>
>>
>> In my experience, giving people something that works "most of the
>> time" will cause the cases where it doesn't work to break. I think
>> it's better to explicitly provide no guarantees of uniqueness to make
>> it clear that collision detection needs to be robust. 
> 
> In the OSPF WG, the fact that a mechanism is specified implies that it
> is required to be robust. 
> 
>> Also, if we rely on collision detection, then what's the advantage of
>> using the MAC address? We might as well as make it random all the time
>> - that probably has a lower chance of collision anyway.
> 
> I can't disagree with this argument and think we could go with a
> psuedo-random number seeded with a hash on the hardware fingerprint as
> the first try for router-id. 
> 

As a side note, what's your opinion on citing and suggesting/requiring
<http://tools.ietf.org/html/rfc5642#section-4> for manageability?

Thanks,

-- Carlos.

>>
>>     I think you mean virtual links. They are definitely not needed in
>>     the auto-configured environment as they are for providing a
>>     backbone path through a transit area and the OSPFv3
>>     auto-configured routing domain assumes only a backbone area.
>>
>>
>> Yes, virtual links. Do we need to state explicitly that they cannot
>> exist and are not supported?
> 
> Since the auto-configured routing domain is area 0 only, it is explicit. 
> 
>>  
>>
>>     > 3. Can we use normal LSAs to detect collisions? One idea would
>>     be "if you see your own router ID in the list of neighbours of a
>>     network LSA or router LSA, then there is a collision". Will that
>>     work? If so we wouldn't need the hardware fingerprint at all.
>>
>>     No. In an arbitrary topology, A router with a duplicate router-id
>>     can be multiple hops away.
>>
>>
>> Yes, but router and network LSAs are flooded, so you'll hear them
>> regardless of whether your duplicate is multiple hops away, no?
> 
> Both OSPFv3 and OSPFv2 would consider an unrecognized self-originated
> LSA, i.e. having our Route-ID, as a stale LSA and purge it. This is a
> very basic mechanism of OSPF. I'd rather use a separate mechanism for
> duplicate Router-ID detection. I considered techniques involving the
> encoding some additional information in the Router-LSA but these all
> seemed to be hacked. 
> 
> 
>>  
>>
>>     If the pre-shared key is hard-coded, it is no better than the
>>     OSPFv3 Interface Instance ID that is specified to prevent
>>     inadvertent adjacencies with routers not supporting the
>>     auto-configuration. If configuration of a pre-shared key is
>>     required, you no longer have auto-configuration.
>>
>>
>> Sorry, that wasn't clear. What I meant to say is that we should pick
>> one scheme (e.g., HMAC-SHA) and stick to it; we shouldn't support
>> multiple schemes as that will lead to interoperability issues for
>> devices that use one scheme and devices that use another scheme.
> 
> The OSPFv3 Instance ID is part of the base OSPFv3 specification and I
> think it is a very good mechanism to prevent inadvertent adjacencies. If
> we need real authentication, we'll need a pre-shared key. I don't see
> any advantage of authentication with a well-known pre-shared key to
> prevent inadvertent adjacencies. 
> 
> Thanks for the comments,
> Acee 
> 
> 
> 
> 
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet

From acee.lindem@ericsson.com  Tue Nov 15 10:39:01 2011
Return-Path: <acee.lindem@ericsson.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 715A911E80B7 for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 10:39:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.526
X-Spam-Level: 
X-Spam-Status: No, score=-6.526 tagged_above=-999 required=5 tests=[AWL=0.073,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KUJfsoo3ZRwY for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 10:38:57 -0800 (PST)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by ietfa.amsl.com (Postfix) with ESMTP id 4AF0D11E80A6 for <homenet@ietf.org>; Tue, 15 Nov 2011 10:38:57 -0800 (PST)
Received: from eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id pAFIcqpd025535 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 15 Nov 2011 12:38:54 -0600
Received: from EUSAACMS0702.eamcs.ericsson.se ([169.254.1.218]) by eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) with mapi; Tue, 15 Nov 2011 13:38:53 -0500
From: Acee Lindem <acee.lindem@ericsson.com>
To: Carlos Pignataro <cpignata@cisco.com>
Date: Tue, 15 Nov 2011 13:38:51 -0500
Thread-Topic: [homenet] Comments on draft-acee-ospf-ospfv3-autoconfig-00
Thread-Index: AcyjxdKRGH9zWH4wTfO46SSu+PNO6Q==
Message-ID: <6A2F0A68-5D4F-4742-A95F-18688525D6B7@ericsson.com>
References: <CAKD1Yr3uSsNP4avZBdQE7YxFd7D_KOXBOCsfaRfvnWhJoLoY9Q@mail.gmail.com> <B3BE775A-4EBB-4C17-9EDC-7B9AFCB8867E@ericsson.com> <CAKD1Yr0MFdyBopr0E0WiebLSZ+M2J9vAi1U6b66VxhziE2XJpw@mail.gmail.com> <FF6FB9A0-9F91-4658-A265-BA200A0858AF@ericsson.com> <4EC29D17.10302@cisco.com>
In-Reply-To: <4EC29D17.10302@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/signed; boundary="Apple-Mail-58--522252328"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
Cc: "homenet@ietf.org" <homenet@ietf.org>, Jari Arkko <jari.arkko@piuha.net>, Lorenzo Colitti <lorenzo@google.com>
Subject: Re: [homenet] Comments on draft-acee-ospf-ospfv3-autoconfig-00
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 18:39:01 -0000

--Apple-Mail-58--522252328
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi Carlos,

On Nov 15, 2011, at 12:10 PM, Carlos Pignataro wrote:

> Hi Acee,
>=20
> On 11/14/2011 10:11 PM, Acee Lindem wrote:
>>=20
>> On Nov 14, 2011, at 9:46 PM, Lorenzo Colitti wrote:
>>=20
>>> On Tue, Nov 15, 2011 at 10:25, Acee Lindem <acee.lindem@ericsson.com
>>> <mailto:acee.lindem@ericsson.com>> wrote:
>>>=20
>>>> 1. I think the OSPFv3 router ID should not be based on the MAC
>>>    address because that will encourage people to assume it's unique
>>>    "most of the time". I think we should just make it a =
pseudo-random
>>>    number so it's clear that uniqueness is only guaranteed by
>>>    collision detection and that collision detection needs to be =
robust.
>>>=20
>>>    The draft requires duplicate Router-ID detection and resolution. =
I
>>>    don't think that the fact that a portion of the MAC address is
>>>    used as a first try is reason for this detection/resolution not =
to
>>>    be implemented or tested.
>>>=20
>>>=20
>>> In my experience, giving people something that works "most of the
>>> time" will cause the cases where it doesn't work to break. I think
>>> it's better to explicitly provide no guarantees of uniqueness to =
make
>>> it clear that collision detection needs to be robust.=20
>>=20
>> In the OSPF WG, the fact that a mechanism is specified implies that =
it
>> is required to be robust.=20
>>=20
>>> Also, if we rely on collision detection, then what's the advantage =
of
>>> using the MAC address? We might as well as make it random all the =
time
>>> - that probably has a lower chance of collision anyway.
>>=20
>> I can't disagree with this argument and think we could go with a
>> psuedo-random number seeded with a hash on the hardware fingerprint =
as
>> the first try for router-id.=20
>>=20
>=20
> As a side note, what's your opinion on citing and suggesting/requiring
> <http://tools.ietf.org/html/rfc5642#section-4> for manageability?

I think the dynamic host-name is less applicable in an auto-configured =
routing domain than other domains. In the auto-configured routing =
domain, you hope that little monitoring, debugging, or interaction is =
required.=20
Thanks,
Acee



>=20
> Thanks,
>=20
> -- Carlos.
>=20
>>>=20
>>>    I think you mean virtual links. They are definitely not needed in
>>>    the auto-configured environment as they are for providing a
>>>    backbone path through a transit area and the OSPFv3
>>>    auto-configured routing domain assumes only a backbone area.
>>>=20
>>>=20
>>> Yes, virtual links. Do we need to state explicitly that they cannot
>>> exist and are not supported?
>>=20
>> Since the auto-configured routing domain is area 0 only, it is =
explicit.=20
>>=20
>>>=20
>>>=20
>>>> 3. Can we use normal LSAs to detect collisions? One idea would
>>>    be "if you see your own router ID in the list of neighbours of a
>>>    network LSA or router LSA, then there is a collision". Will that
>>>    work? If so we wouldn't need the hardware fingerprint at all.
>>>=20
>>>    No. In an arbitrary topology, A router with a duplicate router-id
>>>    can be multiple hops away.
>>>=20
>>>=20
>>> Yes, but router and network LSAs are flooded, so you'll hear them
>>> regardless of whether your duplicate is multiple hops away, no?
>>=20
>> Both OSPFv3 and OSPFv2 would consider an unrecognized self-originated
>> LSA, i.e. having our Route-ID, as a stale LSA and purge it. This is a
>> very basic mechanism of OSPF. I'd rather use a separate mechanism for
>> duplicate Router-ID detection. I considered techniques involving the
>> encoding some additional information in the Router-LSA but these all
>> seemed to be hacked.=20
>>=20
>>=20
>>>=20
>>>=20
>>>    If the pre-shared key is hard-coded, it is no better than the
>>>    OSPFv3 Interface Instance ID that is specified to prevent
>>>    inadvertent adjacencies with routers not supporting the
>>>    auto-configuration. If configuration of a pre-shared key is
>>>    required, you no longer have auto-configuration.
>>>=20
>>>=20
>>> Sorry, that wasn't clear. What I meant to say is that we should pick
>>> one scheme (e.g., HMAC-SHA) and stick to it; we shouldn't support
>>> multiple schemes as that will lead to interoperability issues for
>>> devices that use one scheme and devices that use another scheme.
>>=20
>> The OSPFv3 Instance ID is part of the base OSPFv3 specification and I
>> think it is a very good mechanism to prevent inadvertent adjacencies. =
If
>> we need real authentication, we'll need a pre-shared key. I don't see
>> any advantage of authentication with a well-known pre-shared key to
>> prevent inadvertent adjacencies.=20
>>=20
>> Thanks for the comments,
>> Acee=20
>>=20
>>=20
>>=20
>>=20
>> _______________________________________________
>> 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


--Apple-Mail-58--522252328
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIM8jCCBDQw
ggMcoAMCAQICECFWwVQHDV12M/Sr0yNv0sYwDQYJKoZIhvcNAQEFBQAwOTERMA8GA1UECgwIRXJp
Y3Nzb24xJDAiBgNVBAMMG0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMTAeFw0xMDEwMDEyMDA0
NTlaFw0xMzEwMDEyMDA0NDhaMG8xETAPBgNVBAoMCEVyaWNzc29uMR8wHQYDVQQDDBZBY2VlIExp
bmRlbSBMaW5kZW0gSUlJMRAwDgYDVQQFEwdlYWxmbGluMScwJQYJKoZIhvcNAQkBFhhhY2VlLmxp
bmRlbUBlcmljc3Nvbi5jb20wgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAI/Dc9ALiZuBMyuv
bsc3eBxjXZpMi45Z0vzsUQZTJGTBeY7p9JsdzXC9J1uMisBxYVi39R3KJo6I4hXVp9wrA1rxh4AE
bnP1+Gxfpj33uWEFYbBnVAJkIWYWF7CYTn8Zm/yd13vPXtuGA6ESeLnnJafwC9Y0YwUQ+4HX7PNv
uauVAgMBAAGjggGEMIIBgDCBwAYDVR0fBIG4MIG1MIGyoIGvoIGshjdodHRwOi8vY3JsLnRydXN0
LnRlbGlhLmNvbS9Fcmljc3Nvbk5MSW5kaXZpZHVhbENBMDEuY3JshnFsZGFwOi8vbGRhcC50cnVz
dC50ZWxpYS5jb20vY249RXJpY3Nzb24lMjBOTCUyMEluZGl2aWR1YWwlMjBDQTAxLG89RXJpY3Nz
b24/Y2VydGlmaWNhdGVyZXZvY2F0aW9ubGlzdDtiaW5hcnk/YmFzZTAjBgNVHREEHDAagRhhY2Vl
LmxpbmRlbUBlcmljc3Nvbi5jb20wRgYDVR0gBD8wPTA7BgYqhXBrAQEwMTAvBggrBgEFBQcCARYj
aHR0cDovL3d3dy5lcmljc3Nvbi5jb20vbGVnYWwuc2h0bWwwHQYDVR0OBBYEFAgOzAPuplmPr7C1
BTqV94OyqUdhMB8GA1UdIwQYMBaAFJYnw7jepV9dRD45UuVFsXZfYzCbMA4GA1UdDwEB/wQEAwIF
oDANBgkqhkiG9w0BAQUFAAOCAQEAE1gyNW6c2t/YsLxW5sm67+gVGK0Lnge4ub+k8dgGrK7Mj7em
nkOIFkjdv/tqdJ/SoUy/WEkBXba2TfpZ+lfluMgLYux1vSvqBUxYBsUHeNth2Q/Y6A9sCaDTBPlK
vZ2jLz814NavrVfgTCLdxX6zNtGdwzhviz+FyqyxYF43Q86RP8Gd/Npaz1W8pmYAHm0+lezuTx5k
F3Av3+SaZ/MR6s+RWuXEIdED36ajeQz+OG8Mh3nplofzdrOeoWGDz53YlfRhgj+TXo+H1lclZAvD
WVaMMXPdb27h9Hngsq87dkCW9uAyv8DI993rdhqzlEgUyQIL32icAXfTmTYgoGPOwjCCBEUwggMt
oAMCAQICEBPJ6v/eJq2p3KTKI4GDR+MwDQYJKoZIhvcNAQEFBQAwRDEaMBgGA1UECgwRVGVsaWFT
b25lcmEgR3JvdXAxJjAkBgNVBAMMHVRlbGlhU29uZXJhIFB1YmxpYyBSb290IENBIHYxMB4XDTA2
MTAwNjEwMDA1M1oXDTE2MTAwMjA1MDQxN1owOTERMA8GA1UECgwIRXJpY3Nzb24xJDAiBgNVBAMM
G0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoC
ggEBALYQd+Q1HuuHxDyNGFlEPzCxuPPFO5W2xyr+nqCVnNJ4QYFe1HACqavqNLwUGIqIEyHv1rLn
fub9LBc7dQpRHjl/dggin0ONOFJ36nbGEbfHjLJz2BzOWvwl84Sc+Fx09IrDU/SZSWFSfhqTu3TT
39h79brHdRkdPBUgBYgsiFKriHI0TjP5G8628H27BDzqUpzGLSYWgt6/tpwuOH5lcfNfHWMcCYXR
lobv0Klu8lxG5amWqAnqrH6ECOyYJTRbHTsaTIZOHy9Qw/0eXPujKT7tU5xxSI2SdceJqzUbAz2o
FRQ6Px7/GydpM/Rl+qYoGPcauHUL1aSeVJZqDFqcIF0CAwEAAaOCATwwggE4MBIGA1UdEwEB/wQI
MAYBAf8CAQAwRgYDVR0gBD8wPTA7BgcqhXAjAgEBMDAwLgYIKwYBBQUHAgEWImh0dHBzOi8vcmVw
b3NpdG9yeS50cnVzdC50ZWxpYS5jb20wgYkGA1UdHwSBgTB/MH2ge6B5hndsZGFwOi8vbGRhcC50
cnVzdC50ZWxpYS5jb20vY249VGVsaWFTb25lcmElMjBQdWJsaWMlMjBSb290JTIwQ0ElMjB2MSxv
PVRlbGlhU29uZXJhJTIwR3JvdXA/YXV0aG9yaXR5cmV2b2NhdGlvbmxpc3Q/YmFzZTAOBgNVHQ8B
Af8EBAMCAQYwHQYDVR0OBBYEFJYnw7jepV9dRD45UuVFsXZfYzCbMB8GA1UdIwQYMBaAFEXb8I+4
GmKhqCMbY4g4o9vgGmLxMA0GCSqGSIb3DQEBBQUAA4IBAQB2AEoqQz+M3Ra9alkpn/YnwhXIv6tP
jhUvSuNs00Nhd0T9XhlIU3a65CaB/UKSqnayE0t7Q0Qq3r+x/GK3in/mik8i/PK2/q8HutzYFSzz
6Npztpo2JG7AEKOJPVaeebjng45m6vNC7RIfzU9sG2LBR/hewS8s6dFFn70w795xUwJBWZ67OzIK
XrIVVvHTOYpbWA+MESKAXwFhnVONrOTWlVwrMUi4HbiPWpOk+xQbgehCEi7mu3cXsaU1Xq3kMXui
NuC7VKoob8mFO9o9RT+dlirD2uRXwNpvCu3but6Kyhu0+nvy2iXGKjdlxlWTsdDyulXYz+OYCMZ9
lFWRzMIPMIIEbTCCA1WgAwIBAgIRAJywjASay5cieGNithuGWj0wDQYJKoZIhvcNAQEFBQAwOjEZ
MBcGA1UEChMQUlNBIFNlY3VyaXR5IEluYzEdMBsGA1UECxMUUlNBIFNlY3VyaXR5IDIwNDggVjMw
HhcNMDYxMDMxMjA0MjI3WhcNMTYxMTAxMTU0MjI1WjBEMRowGAYDVQQKDBFUZWxpYVNvbmVyYSBH
cm91cDEmMCQGA1UEAwwdVGVsaWFTb25lcmEgUHVibGljIFJvb3QgQ0EgdjEwggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQDKTxADapCAq3mplX4R4gNt+WZe5QKGnaVEQSyY7lICKF5DuVdW
PMLHDjzhw5IzDd860ZZx/0VrhGB3DmP4SDIWCKo2PxvY5NckdBWPWp/T2uaQdOAwgqHpN0pe1X7/
jel59WsWYXKGg/81Wth73ZK/geE7Gz9Pvj1LU6N4YhLMgooxKnCS+ZjB5icWAg+Qd1QpQhF46H1i
bp6LsBWDp56MPpg8F5X6y7MGVcKYLdnLOPs84uxRW9qs1kBopzQBj6s5SyVh8A+j5liDBjghXYpw
/+paGEdqHPeSFYxZKeJatmjEKLYlxcZWRKf436KvQA9jBhMEmytMNbGicR1mRH6tAgMBAAGjggFi
MIIBXjAfBgNVHSMEGDAWgBQHw1EwpKrpRa41JPr/JCwz0LGdjDAdBgNVHQ4EFgQURdvwj7gaYqGo
IxtjiDij2+AaYvEwEgYDVR0TAQH/BAgwBgEB/wIBBDCBhQYDVR0gBH4wfDA9BgkqhkiG9w0FBgEw
MDAuBggrBgEFBQcCARYiaHR0cHM6Ly9yZXBvc2l0b3J5LnRydXN0LnRlbGlhLmNvbTA7BgcqhXAj
AgEBMDAwLgYIKwYBBQUHAgEWImh0dHBzOi8vcmVwb3NpdG9yeS50cnVzdC50ZWxpYS5jb20wcAYD
VR0fBGkwZzBloGOgYYZfaHR0cDovL3d3dy5yc2FzZWN1cml0eS5jb20vcHJvZHVjdHMva2Vvbi9y
ZXBvc2l0b3J5L2NlcnRpZmljYXRlX3N0YXR1cy9SU0FfU2VjdXJpdHlfMjA0OF92My5DUkwwDgYD
VR0PAQH/BAQDAgEGMA0GCSqGSIb3DQEBBQUAA4IBAQAEXpos2CnIm7/872ytSrEHWZgvhOUEkUm2
5PWf/XkWko41TaL9vIS1S6AdWChNqWmnYiS7GfaIiDM9s1D6K7hidWBDOm46bNdM3ZwhMyDCfkDJ
SgeJ0w+7YmjvChu7gWqDZCsbtZ5gA1ixCTdDnuZB67JGSPGW6r73coraDP8diOpiQouMvM6bKuTP
BH/1poLccsUxsKgrQ23JC9LWCRb8cYHkZjXFH1K44TsIl5Lne2oT0JI3pwdA2v6jO4p/OLHntP+n
pjwPbedMPUZkDYCkd3LSxj8c3JTxtA8SlPCtIHE1hh65xihg1JRIliSphrqr9kbfwHdeVxPdOI5G
tDYPMYICEjCCAg4CAQEwTTA5MREwDwYDVQQKDAhFcmljc3NvbjEkMCIGA1UEAwwbRXJpY3Nzb24g
TkwgSW5kaXZpZHVhbCBDQTAxAhAhVsFUBw1ddjP0q9Mjb9LGMAkGBSsOAwIaBQCgggEbMBgGCSqG
SIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMTExNTE4Mzg1MVowIwYJKoZI
hvcNAQkEMRYEFO02uYDCZreGOyiTKOs6B7FiArkSMFwGCSsGAQQBgjcQBDFPME0wOTERMA8GA1UE
CgwIRXJpY3Nzb24xJDAiBgNVBAMMG0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMQIQIVbBVAcN
XXYz9KvTI2/SxjBeBgsqhkiG9w0BCRACCzFPoE0wOTERMA8GA1UECgwIRXJpY3Nzb24xJDAiBgNV
BAMMG0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMQIQIVbBVAcNXXYz9KvTI2/SxjANBgkqhkiG
9w0BAQEFAASBgA6uebgSf3ALC/zNZbY0k9nrrbneMbLz+MakZA1AYclPaLPjVxQLJ87924E0taGY
Tba3Hhkn7nqxfHESUEzx1U6PTl1heBsRUHO1Iw5/qRh9SeTwVvUho6zgaLFZBJgY8Bt3MoGQdVWC
r+0KLIxnBzrFFOrcV3a3tFlgTm6P7ktYAAAAAAAA

--Apple-Mail-58--522252328--

From mcr@sandelman.ca  Tue Nov 15 10:49:48 2011
Return-Path: <mcr@sandelman.ca>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97BA411E80BB for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 10:49:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.401
X-Spam-Level: 
X-Spam-Status: No, score=-1.401 tagged_above=-999 required=5 tests=[AWL=-0.047, BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334, J_CHICKENPOX_45=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hrgT+sSb2RQR for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 10:49:44 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id EF6D811E80C3 for <homenet@ietf.org>; Tue, 15 Nov 2011 10:49:43 -0800 (PST)
Received: from marajade.sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by relay.sandelman.ca (Postfix) with ESMTPS id 0DF81343CB; Tue, 15 Nov 2011 13:48:17 -0500 (EST)
Received: by marajade.sandelman.ca (Postfix, from userid 179) id 01C3D98CB3; Tue, 15 Nov 2011 13:49:42 -0500 (EST)
Received: from marajade.sandelman.ca (localhost [127.0.0.1]) by marajade.sandelman.ca (Postfix) with ESMTP id EF42598CB1; Tue, 15 Nov 2011 13:49:42 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ca>
To: Randy Turner <rturner@amalfisystems.com>
In-Reply-To: <1B5AB373-0180-49DE-A98D-A5F80BD17334@amalfisystems.com>
References: <x8t6f1v0lqimf54q4kw8fq4x.1321340055797@email.android.com> <4EC21B4D.2040305@gmail.com> <29433.1321371383@marajade.sandelman.ca> <1B5AB373-0180-49DE-A98D-A5F80BD17334@amalfisystems.com>
X-Mailer: MH-E 8.1; nmh 1.3-dev; XEmacs 21.4 (patch 22)
Date: Tue, 15 Nov 2011 13:49:42 -0500
Message-ID: <24754.1321382982@marajade.sandelman.ca>
Sender: mcr@sandelman.ca
Cc: "homenet@ietf.org" <homenet@ietf.org>
Subject: Re: [homenet] privacy vs subnet-id
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 18:49:48 -0000

{why am I top-quoting?}

So, I agree with you about translating terminology, or at least, picking
sufficiently unique (and multicultural) terminology such that the terms
can be used unambiguously.

The scenario I have in mind is:
    1) ISP gets an abuse complaint about IP 
         2001:DB8:f00d:5634:0243:60ff:fefa:8842

    2) ISP maps this via 2001:DB8:f00d:56/56 to customer FOO.
    3) ISP contacts customer FOO about this issue, noting that
       it's on subnet-id "34".  No end-user is going to know 
       what "34" is, nor what "0243:60ff:fefa:8842" is, and
       given privacy extensions, that might be more random.

So the question is, can we have a way for CPE router to unambiguously
record/communicate that subnet-id is "34" was assigned to "wifi guest
network" on ESSID "garage-party".

Customer then says, "Oh, yeah, last Tuesday, my friend Bob was over,
but he is gone now", or "the garage? Oh wait.  Is that my new PEV Volt?
I guess I need to take it to shop for trojan removal"




>>>>> "Randy" == Randy Turner <rturner@amalfisystems.com> writes:
    Randy> Once HomeNet is "figured out", a real subsequent challenge
    Randy> will be to address how to translate any leftover
    Randy> configuration required for the end user.  This would be
    Randy> anything we couldn't figure out how to auto-configure. By
    Randy> "translate" I mean translating any geek-speak config concepts
    Randy> into equivalent mass market concepts that can be easily
    Randy> grasped by the average consumer. If we can't figure this out,
    Randy> and the resulting model has too much policy or buttons and
    Randy> levers to manipulate, then we're probably setting up a nice
    Randy> managed service offering for an NSP. 

    Randy> Randy



    Randy> On Nov 15, 2011, at 7:36 AM, Michael Richardson <mcr@sandelman.ca> wrote:

    >> 
    >>>>>>> "Brian" == Brian E Carpenter <Brian> writes:
    Brian> The responsible parent, for example, who does not want to
    Brian> be fined for their kid's illegal downloads.
    >> 
    >> So, something that we could specify is some way to name the subnets,
    >> and to communicate from the CPE router to the ISP about what is what,
    >> particularly in the case where the CPE router is provided by and/or
    >> partially managed by the ISP.
    >> 
    >> The goal here is to give the ISP some information the network topology
    >> so that the ISP and the responsible parent can more easily work out who
    >> is being complained about.  
    >> 
    >> Said communication doesn't necessarily mean a protocol between the CPE
    >> router and ISP (although it could via INCH or MILE).  It could be as
    >> simple as deciding upon a clear human readable textual description of the
    >> network, something the responsible parent can copy&paste from a web
    >> interface to an email with the ISP.
    >> 
    >> -- 
    >> ]       He who is tired of Weird Al is tired of life!           |  firewalls  [
    >> ]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
    >> ] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
    >> Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE>
    >> then sign the petition. 
    >> 
    >> _______________________________________________
    >> homenet mailing list
    >> homenet@ietf.org
    >> https://www.ietf.org/mailman/listinfo/homenet
    >> 

From acee.lindem@ericsson.com  Tue Nov 15 10:52:42 2011
Return-Path: <acee.lindem@ericsson.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01DF611E80CC for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 10:52:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.528
X-Spam-Level: 
X-Spam-Status: No, score=-6.528 tagged_above=-999 required=5 tests=[AWL=0.071,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RlN-Aql4v6XN for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 10:52:35 -0800 (PST)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 6E15511E80C8 for <homenet@ietf.org>; Tue, 15 Nov 2011 10:52:29 -0800 (PST)
Received: from eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id pAFIqJFc014428; Tue, 15 Nov 2011 12:52:26 -0600
Received: from EUSAACMS0702.eamcs.ericsson.se ([169.254.1.218]) by eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) with mapi; Tue, 15 Nov 2011 13:52:16 -0500
From: Acee Lindem <acee.lindem@ericsson.com>
To: Michael Richardson <mcr@sandelman.ca>
Date: Tue, 15 Nov 2011 13:52:14 -0500
Thread-Topic: [homenet] Comments on draft-acee-ospf-ospfv3-autoconfig-00
Thread-Index: Acyjx7FK8aZCnMoHTLmYOf01Efwo6A==
Message-ID: <3112C980-7FD1-4BE3-8494-3E89E8D40376@ericsson.com>
References: <CAKD1Yr3uSsNP4avZBdQE7YxFd7D_KOXBOCsfaRfvnWhJoLoY9Q@mail.gmail.com> <28079.1321370795@marajade.sandelman.ca>
In-Reply-To: <28079.1321370795@marajade.sandelman.ca>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<homenet@ietf.org>" <homenet@ietf.org>
Subject: Re: [homenet] Comments on draft-acee-ospf-ospfv3-autoconfig-00
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 18:52:42 -0000

Hi Michael,

On Nov 15, 2011, at 10:26 AM, Michael Richardson wrote:

>=20
>=20
>=20
>>>>>> "Lorenzo" =3D=3D Lorenzo Colitti <lorenzo@google.com> writes:
>    Lorenzo> 4. For security, I think we should pick an auth scheme and
>    Lorenzo> stick to it, otherwise
>    Lorenzo> it will just lead to fragmentation. Some pre-shared key
>    Lorenzo> scheme might be adequate; I don't know much about security
>    Lorenzo> so I don't really care what it is, but I do think we need
>    Lorenzo> to have one and it needs to be the same for=20
>    Lorenzo> everyone. I think we should say MUST here.
>=20
> So, let me go over the options in order to violently agree.
>=20
> 1) OSPF is multicast, so we can't use any bilteral key-agreement
>   protocol on it's own.  Statically keyed AH can be used for multicast
>   traffic, and a router can trivially ignore an AH validation failure in
>   order to provide some diagnostics by evaluating the contents of
>   the OSPF frame. (This requires hacks on platforms that already have
>   IPsec, but if you implement the AH inside the OSPF daemon....)
>=20
>   (so diagnostics can say, "I saw router FOO on interface BLAH, but
>   the key didn't match, so I ignored it", or even, "I saw router FOO
>   on interface BLAH, and since the key didn't match, I treated it as a
>   guest network".  What router FOO thinks of the packets it receives is a=
n
>   open question)
>=20
> 2) While we could invoke some kind of group-KMP, these essentially work
>   out to a series of bilateral trust relationships which results in the
>   master machine giving out the pre-shared secret in a secure fashion.
>   The bilateral trust mechanism needs to be anchored by something,=20
>   and you can invoke public key mechanisms, or... shared secret.
>=20
>   Public key mechanisms with a leap-of-faith and then confirmation via UI=
,
>   would be very cool, but completely exceeds our needs. =20
>=20
> 3) my understanding is that OSPFv3 eliminated the plain-text HELLO and
>   md5 methods.=20
>=20
> The major thing we need to specify for zOSPF is that we need to pick a
> well-known SPI value for the AH header.  That SPI value will need to
> specify an algorithm (HMAC-SHA1, HMAC-SHA2, HMAC-SHA3...) and perhaps a
> key length.  We should publish a few choices for future interop, but we
> will need to pick one MUST for today.  We can't really be resistant
> against a bid-down attack, but even HMAC-SHA1 is pretty resistant today
> (vs bare SHA1), and I think that we can count upon being able to specify
> HMAC-SHA3 for this work.

We will soon have non-IPsec authentication for OSPFv3:

   http://www.ietf.org/id/draft-ietf-ospf-auth-trailer-ospfv3-10.txt=20


The point that I don't understand from this E-mail thread is where the Secu=
rity Association (SA) comes from to use for auto-configured OSPFv3 routers?=
=20
I guess it is from a USB flash drive ;^)). Also, are you and Lorenzo sugges=
ting we make authentication MANDATORY in for auto-configured OSPFv3 routers=
?=20

Thanks,
Acee=20



>=20
> --=20
> ]       He who is tired of Weird Al is tired of life!           |  firewa=
lls  [
> ]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net arch=
itect[
> ] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device d=
river[
>   Kyoto Plus: watch the video <http://www.youtube.com/watch?v=3Dkzx1ycLXQ=
SE>
> 	               then sign the petition.=20
>=20


From touch@isi.edu  Tue Nov 15 13:49:17 2011
Return-Path: <touch@isi.edu>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 02F8E11E80EB for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 13:49:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.299
X-Spam-Level: 
X-Spam-Status: No, score=-106.299 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2OA9Z6AAJb5V for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 13:49:16 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id 82B3511E80E6 for <homenet@ietf.org>; Tue, 15 Nov 2011 13:49:16 -0800 (PST)
Received: from [172.20.0.82] (203-69-99-17.HINET-IP.hinet.net [203.69.99.17] (may be forged)) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id pAFLmdLA001638 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 15 Nov 2011 13:48:48 -0800 (PST)
Message-ID: <4EC2DE34.4010202@isi.edu>
Date: Tue, 15 Nov 2011 13:48:36 -0800
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Michael Richardson <mcr@sandelman.ca>
References: <D143FF2D6A52E5409FEE8BC1CD3BC54893992FBB98@IRVEXCHCCR01.corp.ad.broadcom.com> <958CCC88-A01D-49FA-9E83-123E62DFAD24@fugue.com> <4EC1F689.9010401@isi.edu> <20111115054440.E839817334CE@drugs.dv.isc.org> <4EC1FF56.9050202@isi.edu> <8A289B2F-4130-4F91-9DB6-5960184FF22D@fugue.com> <4EC205B5.9090208@isi.edu> <7705F952-FB2D-4658-A865-6B4770CB8B24@fugue.com> <4EC2214D.7090903@isi.edu> <20865.1321367698@marajade.sandelman.ca>
In-Reply-To: <20865.1321367698@marajade.sandelman.ca>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "homenet@ietf.org" <homenet@ietf.org>
Subject: Re: [homenet] secret sharing among devices
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 21:49:17 -0000

On 11/15/2011 6:34 AM, Michael Richardson wrote:
>
>>>>>> "Joe" == Joe Touch<touch@isi.edu>  writes:
>      >>>  iPhones are (or can be) routers.
>      >>>  iPhones have no microSD.
>      >>>  iPhones have a USB port that does not supply power.
>      >>
>      >>  Right, we already covered this. You plug them into a USB host
>      >>  device.If you believe this is impractical, okay,
>      >>  but you never expressed that position.
>
>      Joe>  Then let me specify the case:
>
>      Joe>  - verizon home network (no USB on my home router)
>      Joe>  - iPhone and iPad (USB clients, but not hosts)
>      Joe>  - no PC (use the iCloud service)
>
> Tell me again why you need homenet on such a simple network?

So my iPad (and/or anything else in the house) can use either the 
verizon path or the iPhone path to the Internet with automatic routing.

If it's too simple, add other routers that still don't have USBs or cameras.

Joe


From mellon@fugue.com  Tue Nov 15 14:40:55 2011
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 869F81F0C6C for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 14:40:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.237
X-Spam-Level: 
X-Spam-Status: No, score=-1.237 tagged_above=-999 required=5 tests=[AWL=-0.034, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gvXbux1YVgWj for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 14:40:55 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 339BD1F0C67 for <homenet@ietf.org>; Tue, 15 Nov 2011 14:40:55 -0800 (PST)
Received: from [172.22.13.155] (unknown [122.147.240.7]) by toccata.fugue.com (Postfix) with ESMTPSA id 04B202381DF4; Tue, 15 Nov 2011 17:40:53 -0500 (EST)
References: <x8t6f1v0lqimf54q4kw8fq4x.1321340055797@email.android.com> <4EC21B4D.2040305@gmail.com> <29433.1321371383@marajade.sandelman.ca> <1B5AB373-0180-49DE-A98D-A5F80BD17334@amalfisystems.com> <24754.1321382982@marajade.sandelman.ca>
In-Reply-To: <24754.1321382982@marajade.sandelman.ca>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <06F16384-4B2C-4D9B-8E5E-34CFD51CD544@fugue.com>
X-Mailer: iPad Mail (9A334)
From: Ted Lemon <mellon@fugue.com>
Date: Wed, 16 Nov 2011 06:41:24 +0800
To: Michael Richardson <mcr@sandelman.ca>
Cc: Randy Turner <rturner@amalfisystems.com>, "homenet@ietf.org" <homenet@ietf.org>
Subject: Re: [homenet] privacy vs subnet-id
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 22:40:55 -0000

On Nov 16, 2011, at 2:49 AM, Michael Richardson <mcr@sandelman.ca> wrote:
> {why am I top-quoting?}
I don't know.=20

> So, I agree with you about translating terminology, or at least, picking
> sufficiently unique (and multicultural) terminology such that the terms
> can be used unambiguously.
>=20
> The scenario I have in mind is:
>    1) ISP gets an abuse complaint about IP=20
>         2001:DB8:f00d:5634:0243:60ff:fefa:8842
>=20
>    2) ISP maps this via 2001:DB8:f00d:56/56 to customer FOO.
>    3) ISP contacts customer FOO about this issue, noting that
>       it's on subnet-id "34".  No end-user is going to know=20
>       what "34" is, nor what "0243:60ff:fefa:8842" is, and
>       given privacy extensions, that might be more random.
>=20
> So the question is, can we have a way for CPE router to unambiguously
> record/communicate that subnet-id is "34" was assigned to "wifi guest
> network" on ESSID "garage-party".

It would certainly be handy if the homenet populated a reverse DNS tree that=
 could be queried.=20=

From mcr@sandelman.ca  Tue Nov 15 14:51:59 2011
Return-Path: <mcr@sandelman.ca>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 673761F0C87 for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 14:51:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level: 
X-Spam-Status: No, score=-1.7 tagged_above=-999 required=5 tests=[AWL=0.254, BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HnFXCJ-HgBL9 for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 14:51:54 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id C67631F0C8C for <homenet@ietf.org>; Tue, 15 Nov 2011 14:51:54 -0800 (PST)
Received: from marajade.sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by relay.sandelman.ca (Postfix) with ESMTPS id 317DD343C9 for <homenet@ietf.org>; Tue, 15 Nov 2011 17:50:28 -0500 (EST)
Received: by marajade.sandelman.ca (Postfix, from userid 179) id DDD9298CB3; Tue, 15 Nov 2011 17:51:53 -0500 (EST)
Received: from marajade.sandelman.ca (localhost [127.0.0.1]) by marajade.sandelman.ca (Postfix) with ESMTP id D2BC098CB1 for <homenet@ietf.org>; Tue, 15 Nov 2011 17:51:53 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ca>
To: "<homenet@ietf.org>" <homenet@ietf.org>
In-Reply-To: <3112C980-7FD1-4BE3-8494-3E89E8D40376@ericsson.com>
References: <CAKD1Yr3uSsNP4avZBdQE7YxFd7D_KOXBOCsfaRfvnWhJoLoY9Q@mail.gmail.com> <28079.1321370795@marajade.sandelman.ca> <3112C980-7FD1-4BE3-8494-3E89E8D40376@ericsson.com>
X-Mailer: MH-E 8.1; nmh 1.3-dev; XEmacs 21.4 (patch 22)
Date: Tue, 15 Nov 2011 17:51:53 -0500
Message-ID: <25559.1321397513@marajade.sandelman.ca>
Sender: mcr@sandelman.ca
Subject: Re: [homenet] Comments on draft-acee-ospf-ospfv3-autoconfig-00
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 22:51:59 -0000

>>>>> "Acee" == Acee Lindem <acee.lindem@ericsson.com> writes:
    Acee> We will soon have non-IPsec authentication for OSPFv3:

    Acee> http://www.ietf.org/id/draft-ietf-ospf-auth-trailer-ospfv3-10.txt 

    Acee> The point that I don't understand from this E-mail thread is
    Acee> where the Security Association (SA) comes from to use for
    Acee> auto-configured OSPFv3 routers?  
    Acee> I guess it is from a USB flash drive ;^)). 

The SA would be keyed from the shared material.
The details of the SA (SPI#, transform, hash) would either be mandated
by document, or from the shared material.

    Acee> Also, are you and
    Acee> Lorenzo suggesting we make authentication MANDATORY in for
    Acee> auto-configured OSPFv3 routers?  

I don't know.  

I sure would like to make it so, but I sure want this thing to work.

We discussed the fact that the home owner needs to enter their "network
key" into every device, and the WPA/WEP keys for non-guest access would
be based upon this.   

Do we need security for wired connections?  It's an open question.
Do we need security for closed wifi connections?  I think maybe.
Do we need security for open/guest wifi connections?  I think definitely.

-- 
]       He who is tired of Weird Al is tired of life!           |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
   Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE>
	               then sign the petition. 



From mellon@fugue.com  Tue Nov 15 14:52:02 2011
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0FD711F0C91 for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 14:52:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[AWL=-0.032, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bGQC3scAb6aB for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 14:52:01 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id A40161F0C86 for <homenet@ietf.org>; Tue, 15 Nov 2011 14:52:01 -0800 (PST)
Received: from [172.22.13.155] (unknown [122.147.240.7]) by toccata.fugue.com (Postfix) with ESMTPSA id AB4C12381DF4; Tue, 15 Nov 2011 17:52:00 -0500 (EST)
References: <625F39517869164ABE7DB2FFB4CA66A730CCE72B@IT-EXMB-01.silverspringnet.com>
In-Reply-To: <625F39517869164ABE7DB2FFB4CA66A730CCE72B@IT-EXMB-01.silverspringnet.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <A1E94F0B-8929-4E80-BD90-784C56874FF9@fugue.com>
X-Mailer: iPad Mail (9A334)
From: Ted Lemon <mellon@fugue.com>
Date: Wed, 16 Nov 2011 06:52:31 +0800
To: Thomas Herbst <therbst@silverspringnet.com>
Cc: "homenet@ietf.org" <homenet@ietf.org>, Thomas Herbst <therbst@silverspringnet.com>, "mcr@sandelman.ca" <mcr@sandelman.ca>
Subject: Re: [homenet] secret sharing among devices
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 22:52:02 -0000

On Nov 15, 2011, at 9:48 PM, Thomas Herbst <therbst@silverspringnet.com> wro=
te:
> Like wifi protected setup? Push button, pass phrase, near field coms and u=
sb stick, recently reduced to push button and pass phrase.

Into which router do you type he pass phrase?   How?=

From mcr@sandelman.ca  Tue Nov 15 15:00:17 2011
Return-Path: <mcr@sandelman.ca>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29E311F0C99 for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 15:00:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.71
X-Spam-Level: 
X-Spam-Status: No, score=-1.71 tagged_above=-999 required=5 tests=[AWL=0.244,  BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OPrNgPipbExc for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 15:00:12 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id 85AE51F0C34 for <homenet@ietf.org>; Tue, 15 Nov 2011 15:00:12 -0800 (PST)
Received: from marajade.sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by relay.sandelman.ca (Postfix) with ESMTPS id A313C343E9 for <homenet@ietf.org>; Tue, 15 Nov 2011 17:58:47 -0500 (EST)
Received: by marajade.sandelman.ca (Postfix, from userid 179) id A518A98CB3; Tue, 15 Nov 2011 18:00:13 -0500 (EST)
Received: from marajade.sandelman.ca (localhost [127.0.0.1]) by marajade.sandelman.ca (Postfix) with ESMTP id 9B2B098CB1 for <homenet@ietf.org>; Tue, 15 Nov 2011 18:00:13 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ca>
To: "homenet@ietf.org" <homenet@ietf.org>
In-Reply-To: <06F16384-4B2C-4D9B-8E5E-34CFD51CD544@fugue.com>
References: <x8t6f1v0lqimf54q4kw8fq4x.1321340055797@email.android.com> <4EC21B4D.2040305@gmail.com> <29433.1321371383@marajade.sandelman.ca> <1B5AB373-0180-49DE-A98D-A5F80BD17334@amalfisystems.com> <24754.1321382982@marajade.sandelman.ca> <06F16384-4B2C-4D9B-8E5E-34CFD51CD544@fugue.com>
X-Mailer: MH-E 8.1; nmh 1.3-dev; XEmacs 21.4 (patch 22)
Date: Tue, 15 Nov 2011 18:00:13 -0500
Message-ID: <26740.1321398013@marajade.sandelman.ca>
Sender: mcr@sandelman.ca
Subject: Re: [homenet] privacy vs subnet-id
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 23:00:17 -0000

>>>>> "Ted" == Ted Lemon <mellon@fugue.com> writes:
    >> So, I agree with you about translating terminology, or at least, picking
    >> sufficiently unique (and multicultural) terminology such that the terms
    >> can be used unambiguously.
    >> 
    >> The scenario I have in mind is:
    >> 1) ISP gets an abuse complaint about IP 
    >> 2001:DB8:f00d:5634:0243:60ff:fefa:8842
    >> 
    >> 2) ISP maps this via 2001:DB8:f00d:56/56 to customer FOO.
    >> 3) ISP contacts customer FOO about this issue, noting that
    >> it's on subnet-id "34".  No end-user is going to know 
    >> what "34" is, nor what "0243:60ff:fefa:8842" is, and
    >> given privacy extensions, that might be more random.
    >> 
    >> So the question is, can we have a way for CPE router to unambiguously
    >> record/communicate that subnet-id is "34" was assigned to "wifi guest
    >> network" on ESSID "garage-party".

    Ted> It would certainly be handy if the homenet populated a reverse
    Ted> DNS tree that could be queried.  

I (you should well remember), as the author of RFC4025, am the biggest
fan of reverse DNS(sec).  (No sarcasm here!!!)   I very very very much
want this tree delegated and populated for home networks.

However, a fully populated reverse DNS, but won't help us when we have
systems with privacy extensions enabled.  

Worse, it won't help us if the machine has moved on, and the DNS has
been updated.  What we have is a locator for the network, and we need
to be able to translate that to human comprehensible form.

-- 
]       He who is tired of Weird Al is tired of life!           |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
   Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE>
	               then sign the petition. 

From mellon@fugue.com  Tue Nov 15 15:15:24 2011
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2268811E808D for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 15:15:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.233
X-Spam-Level: 
X-Spam-Status: No, score=-1.233 tagged_above=-999 required=5 tests=[AWL=-0.030, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E3-awxivuSUv for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 15:15:23 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 19BEB11E8088 for <homenet@ietf.org>; Tue, 15 Nov 2011 15:15:22 -0800 (PST)
Received: from [172.22.13.155] (unknown [122.147.240.7]) by toccata.fugue.com (Postfix) with ESMTPSA id 3C7812381DF0; Tue, 15 Nov 2011 18:15:19 -0500 (EST)
References: <x8t6f1v0lqimf54q4kw8fq4x.1321340055797@email.android.com> <4EC21B4D.2040305@gmail.com> <29433.1321371383@marajade.sandelman.ca> <1B5AB373-0180-49DE-A98D-A5F80BD17334@amalfisystems.com> <24754.1321382982@marajade.sandelman.ca> <06F16384-4B2C-4D9B-8E5E-34CFD51CD544@fugue.com> <26740.1321398013@marajade.sandelman.ca>
In-Reply-To: <26740.1321398013@marajade.sandelman.ca>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <B1D7F6C7-707C-46C2-98E4-F76C11498473@fugue.com>
X-Mailer: iPad Mail (9A334)
From: Ted Lemon <mellon@fugue.com>
Date: Wed, 16 Nov 2011 07:15:50 +0800
To: Michael Richardson <mcr@sandelman.ca>
Cc: "homenet@ietf.org" <homenet@ietf.org>
Subject: Re: [homenet] privacy vs subnet-id
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 23:15:24 -0000

On Nov 16, 2011, at 7:00 AM, Michael Richardson <mcr@sandelman.ca> wrote:
> However, a fully populated reverse DNS, but won't help us when we have
> systems with privacy extensions enabled. =20

True

> Worse, it won't help us if the machine has moved on, and the DNS has
> been updated.  What we have is a locator for the network, and we need
> to be able to translate that to human comprehensible form.

The IP address came out of a log. Presumably the log could have done an RDNS=
 lookup...

But yeah, I don't claim this is a panacea; just potentially interesting, and=
 a possible motivator for populating the RDNS tree.=20=

From fred@cisco.com  Tue Nov 15 15:30:47 2011
Return-Path: <fred@cisco.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A22CA11E8101 for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 15:30:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.641
X-Spam-Level: 
X-Spam-Status: No, score=-107.641 tagged_above=-999 required=5 tests=[AWL=-1.042, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i09Y+CwqawAi for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 15:30:47 -0800 (PST)
Received: from ams-iport-4.cisco.com (ams-iport-4.cisco.com [144.254.224.147]) by ietfa.amsl.com (Postfix) with ESMTP id C598F11E80D4 for <homenet@ietf.org>; Tue, 15 Nov 2011 15:30:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=1772; q=dns/txt; s=iport; t=1321399846; x=1322609446; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to:content-transfer-encoding; bh=suxrKbL5PtDr4qHPhGRfS8bFMf5j0InGN244H3o2qkE=; b=CM0/+95wOv9bJyi11cwfp3pTo/bUAg+GobsyczEX8YhnYYJY3xMSkykU old+K9xYkF5RLu9UCaDIXgFQtRyg172rXMZNOHIuHfRP1qJxu2KLmVsfu DXbqXabOvIFX2jq+Skg36uqigri54sVQRYkr25Xc0bi7AfXec4kT9C5zN M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAPT1wk5Io8UR/2dsb2JhbABDqXGBBYFyAQEBAwESAScyCgMFCwtGVwYKK4dgmkABnk6JLmMEiBGMIYU7jEw
X-IronPort-AV: E=Sophos;i="4.69,517,1315180800";  d="scan'208";a="3153541"
Received: from bgl-core-2.cisco.com ([72.163.197.17]) by ams-iport-4.cisco.com with ESMTP; 15 Nov 2011 23:30:44 +0000
Received: from dhcp-4466.meeting.ietf.org (hkidc-vpn-client-233-167.cisco.com [10.75.233.167]) by bgl-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id pAFNUh8g020120; Tue, 15 Nov 2011 23:30:43 GMT
Received: from [127.0.0.1] by dhcp-4466.meeting.ietf.org (PGP Universal service); Wed, 16 Nov 2011 07:30:44 +0800
X-PGP-Universal: processed; by dhcp-4466.meeting.ietf.org on Wed, 16 Nov 2011 07:30:44 +0800
Mime-Version: 1.0 (Apple Message framework v1084)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <4EC1DA91.7070309@gmail.com>
Date: Wed, 16 Nov 2011 07:30:31 +0800
Message-Id: <79C4D10B-8313-4744-9026-D6124B7F450D@cisco.com>
References: <19345.1321323990@marajade.sandelman.ca>	<4EC1D42B.7070105@gmail.com>	<E5975A2E-6C4F-42A0-A444-4E1902230C95@ecs.soton.ac.uk> <EMEW3|c9a6b972cc64ff8b6185463e28c35a72nAE34x03tjc|ecs.soton.ac.uk|E5975A2E-6C4F-42A0-A444-4E1902230C95@ecs.soton.ac.uk> <4EC1DA91.7070309@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1084)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] privacy vs subnet-id
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 23:30:47 -0000

On Nov 15, 2011, at 11:20 AM, Brian E Carpenter wrote:

> Maybe point out that a homenet can be protected against external =
privacy
> threats (possibly citing 4864 etc) but that whatever hosts do, the =
homenet
> admin has the capability to perform traffic analysis down to the =
subnet level.

The admin can do traffic analysis to the individual host level, and can =
sniff traffic that comes by them.

Personally, I think that this is a place where privacy advocates need to =
think carefully about their position. In at least the US courts, there =
is a concept called a "reasonable expectation of privacy". If I have an =
object in my home or on my person, an investigator needs my permission =
or a court order to gain access to it; if it's in my trash bin on the =
street, I have no "reasonable" expectation of privacy, and the =
investigator is permitted to simply raid it. Someone that understands =
the Internet will tell you that stuff on your computer is hard to see =
outside the computer, but the minute you put it on a wire or its radio =
equivalent the fact that you did so is visible, and if it's not =
encrypted, the content is as well. If you are reachable on the Internet =
- if you have an address - I can traceroute and get some notion of where =
you are.

As you said, you can obfuscate an identifier, but not a locator.

Ways to obfuscate that sort of thing probably include TOR routing, but =
even that is tracable to a degree. If I am watching Bob, see a transfer =
of N bytes from Alice to Bob, and immediately thereafter see a transfer =
of approximately N bytes from Bob to Carol, I can infer that there is =
some likelihood that Alice is talking with Carol. Wars have been fought =
by traffic analysis...=

From mcr@sandelman.ca  Tue Nov 15 15:51:16 2011
Return-Path: <mcr@sandelman.ca>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A20211E813A for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 15:51:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.715
X-Spam-Level: 
X-Spam-Status: No, score=-1.715 tagged_above=-999 required=5 tests=[AWL=0.239,  BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E4FIjvf6RUJY for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 15:51:15 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id C09C911E8137 for <homenet@ietf.org>; Tue, 15 Nov 2011 15:51:15 -0800 (PST)
Received: from marajade.sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by relay.sandelman.ca (Postfix) with ESMTPS id E4AD5343E9; Tue, 15 Nov 2011 18:49:49 -0500 (EST)
Received: by marajade.sandelman.ca (Postfix, from userid 179) id EE54B98CB3; Tue, 15 Nov 2011 18:51:15 -0500 (EST)
Received: from marajade.sandelman.ca (localhost [127.0.0.1]) by marajade.sandelman.ca (Postfix) with ESMTP id E75FA98CB1; Tue, 15 Nov 2011 18:51:15 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ca>
To: Joe Touch <touch@isi.edu>
In-Reply-To: <4EC2DE34.4010202@isi.edu>
References: <D143FF2D6A52E5409FEE8BC1CD3BC54893992FBB98@IRVEXCHCCR01.corp.ad.broadcom.com> <958CCC88-A01D-49FA-9E83-123E62DFAD24@fugue.com> <4EC1F689.9010401@isi.edu> <20111115054440.E839817334CE@drugs.dv.isc.org> <4EC1FF56.9050202@isi.edu> <8A289B2F-4130-4F91-9DB6-5960184FF22D@fugue.com> <4EC205B5.9090208@isi.edu> <7705F952-FB2D-4658-A865-6B4770CB8B24@fugue.com> <4EC2214D.7090903@isi.edu> <20865.1321367698@marajade.sandelman.ca> <4EC2DE34.4010202@isi.edu>
X-Mailer: MH-E 8.1; nmh 1.3-dev; XEmacs 21.4 (patch 22)
Date: Tue, 15 Nov 2011 18:51:15 -0500
Message-ID: <1209.1321401075@marajade.sandelman.ca>
Sender: mcr@sandelman.ca
Cc: "homenet@ietf.org" <homenet@ietf.org>
Subject: Re: [homenet] secret sharing among devices
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 23:51:16 -0000

>>>>> "Joe" == Joe Touch <touch@isi.edu> writes:
    Joe> - verizon home network (no USB on my home router)
    Joe> - iPhone and iPad (USB clients, but not hosts)
    Joe> - no PC (use the iCloud service)
    >> 
    >> Tell me again why you need homenet on such a simple network?

    Joe> So my iPad (and/or anything else in the house) can use either
    Joe> the verizon path or the iPhone path to the Internet with
    Joe> automatic routing. 

At this point, it is still a flat LAN with two exit paths.
It's also WIFI. If it was secured WIFI, then you already entered keys
into all devices, so actually, we are probably done.

So, it's not secured WIFI.  The network is open.  Should we have any
security enabled at all then?

    Joe> If it's too simple, add other routers that still don't have
    Joe> USBs or cameras. 

I agree that it's a problem, but it's not clear to me that it's a real
problem.  I think that USB ports are becoming ubiquitous.

-- 
]       He who is tired of Weird Al is tired of life!           |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
   Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE>
	               then sign the petition. 



From brian.e.carpenter@gmail.com  Tue Nov 15 15:52:46 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E6B111E8119 for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 15:52:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.001
X-Spam-Level: 
X-Spam-Status: No, score=-101.001 tagged_above=-999 required=5 tests=[AWL=0.037, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SARE_RECV_IP_061228=0.895, SARE_RECV_SPAM_DOMN0b=1.666, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ei73cGSuVrgx for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 15:52:46 -0800 (PST)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id DBE5611E8137 for <homenet@ietf.org>; Tue, 15 Nov 2011 15:52:45 -0800 (PST)
Received: by vws5 with SMTP id 5so8234951vws.31 for <homenet@ietf.org>; Tue, 15 Nov 2011 15:52:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=60/EWVvMw0FJAIs+CZjToOkKZg1itm63M6uIXDkUBLI=; b=lYz2mB8GVyVhVjqkdGEUAdrzDy8qhpJc5c6z3TokKPQMe01zlVzFghufHy4Ubzs/qG sZK7Gnjw6zhZmnPF++Pny3bBtK45qpHW6pbWoIDoz9n68fYUEnkO0dwSVo3oA3hKme65 UUhY28PMvfDYVUopXq4NxyN3hJ+O4vuBXZi2A=
Received: by 10.52.114.232 with SMTP id jj8mr46158941vdb.94.1321401165354; Tue, 15 Nov 2011 15:52:45 -0800 (PST)
Received: from [192.168.0.217] (61-230-53-171.dynamic.hinet.net. [61.230.53.171]) by mx.google.com with ESMTPS id co10sm4274890vdc.0.2011.11.15.15.52.42 (version=SSLv3 cipher=OTHER); Tue, 15 Nov 2011 15:52:44 -0800 (PST)
Message-ID: <4EC2FB44.2020807@gmail.com>
Date: Wed, 16 Nov 2011 12:52:36 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Joel jaeggli <joelja@bogus.com>
References: <4EC1C386.6010802@gmail.com> <4EC1C566.2060400@cisco.com>	<4EC1CC2E.30209@gmail.com> <4EC1D6C9.3030107@cisco.com>	<CAKD1Yr3rFJonkJ1CbCgGPpr-WDj1RFmR6q4jDab1Toc0tJJodg@mail.gmail.com> <4EC1FF9A.4080308@bogus.com> <4EC2028E.6050305@gmail.com> <4EC20405.8040505@bogus.com>
In-Reply-To: <4EC20405.8040505@bogus.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Erik Nordmark <nordmark@cisco.com>, homenet@ietf.org, Lorenzo Colitti <lorenzo@google.com>
Subject: Re: [homenet] pervasive v4
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 15 Nov 2011 23:52:46 -0000

As Ray said: if it's broken today with v4, it will still be broken
even if the boxes are running IPv6 routing. But afaik this isn't
the 'make IPv4 work better' WG. That means that the requirement
to not break IPv4 actually constrains the possible topologies
for IPv6. I think we have to suck that up.

Regards
   Brian

On 2011-11-15 19:17, Joel jaeggli wrote:
> On 11/15/11 14:11 , Brian E Carpenter wrote:
>> And if the user plugs and plays this:
>>
>>        WAN
>>         |
>>      [NAT44]
>>         |
>> -------------------
>>    |           |
>> [NAT44]     [NAT44]
>>    |           |
>> -------------------
>>
>> what happens? Please script the help desk call.
> 
> Your exit to the upper element is dependent on which dhcp server answers
> first...
> 
> if you have an address collision well, you're screwed...
> 
> 
>         WAN
>          |
>       [NAT44]
>          |
>  -------------------
>     |     |      |
>  [NAT44]  |   [NAT44]
>     |     |      |
>  -------------------
> 
> seen that too...
> 
>>     Brian
>>
>> On 2011-11-15 18:58, Joel jaeggli wrote:
>>> On 11/15/11 13:49 , Lorenzo Colitti wrote:
>>>> On Tue, Nov 15, 2011 at 11:04, Erik Nordmark <nordmark@cisco.com
>>>> <mailto:nordmark@cisco.com>> wrote:
>>>>
>>>>     On 11/14/11 6:19 PM, Brian E Carpenter wrote:
>>>>
>>>>         Yes, but then we're extending v4 and expecting homenets to run
>>>>         (presumably) RIP.
>>>>
>>>>
>>>>     Why RIP? Same protocol between the home routers as we will pick for
>>>>     routing IPv6 in the home.
>>>>
>>>>
>>>> The primitives you have to configure and renumber IPv6 hosts (multiple
>>>> addresses, multiple RAs and address deprecation, and so on) are
>>>> different from the ones we have in IPv4 (essentially, DHCPv4 and NAT).
>>>>
>>>> So I don't think we will be able to take what we do in IPv6 and apply it
>>>> as-is to IPv4. Instead, I think we'll have to either NAT everywhere
>>>> (like we do today) or bridge everywhere.
>>> the consumer routinely ends up with double nats today, that's hardly
>>> ideal, but it works for the most part. it doesn't seem likely to get
>>> better esp as it involves the support of legacy devices.
>>>
>>>> _______________________________________________
>>>> 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 mellon@fugue.com  Tue Nov 15 16:09:28 2011
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DA4621F8801 for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 16:09:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.232
X-Spam-Level: 
X-Spam-Status: No, score=-1.232 tagged_above=-999 required=5 tests=[AWL=-0.029, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fdBaGp5mRAeS for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 16:09:27 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id D982B21F87E2 for <homenet@ietf.org>; Tue, 15 Nov 2011 16:09:27 -0800 (PST)
Received: from [172.22.13.155] (unknown [122.147.240.7]) by toccata.fugue.com (Postfix) with ESMTPSA id 75A542381DF4; Tue, 15 Nov 2011 19:09:26 -0500 (EST)
References: <4EC1C386.6010802@gmail.com> <4EC1C566.2060400@cisco.com> <4EC1CC2E.30209@gmail.com> <4EC1D6C9.3030107@cisco.com> <CAKD1Yr3rFJonkJ1CbCgGPpr-WDj1RFmR6q4jDab1Toc0tJJodg@mail.gmail.com> <4EC1FF9A.4080308@bogus.com> <4EC2028E.6050305@gmail.com> <4EC20405.8040505@bogus.com> <4EC2FB44.2020807@gmail.com>
In-Reply-To: <4EC2FB44.2020807@gmail.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <D99F1C65-2B6D-407A-88F3-EEAADB7E9B07@fugue.com>
X-Mailer: iPad Mail (9A334)
From: Ted Lemon <mellon@fugue.com>
Date: Wed, 16 Nov 2011 08:09:58 +0800
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: Joel jaeggli <joelja@bogus.com>, Erik Nordmark <nordmark@cisco.com>, "homenet@ietf.org" <homenet@ietf.org>, Lorenzo Colitti <lorenzo@google.com>
Subject: Re: [homenet] pervasive v4
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 16 Nov 2011 00:09:28 -0000

On Nov 16, 2011, at 7:52 AM, Brian E Carpenter <brian.e.carpenter@gmail.com>=
 wrote:
> But afaik this isn't
> the 'make IPv4 work better' WG. That means that the requirement
> to not break IPv4 actually constrains the possible topologies
> for IPv6.

This was definitely not the sense of the working group in the meeting.   The=
 sense of the working group was "if the IPv6 topology works, but the IPv4 to=
pology doesn't, oh well."   The consensus seemed to be that it was better to=
 make IPv6 work well than to constrain the solution so that topologies in wh=
ich IPv4 wouldn't work would also break IPv6 (which, let's be clear, is esse=
ntially what you are suggesting).

Having said that, if there's a way to make IPv4 topologies that either don't=
 work, or work poorly, with a modern IPv4 NAT router, work well with a homen=
et router, and it's possible to get that essentially for free, then I think i=
t's worth getting, even though that's certainly not the problem we've set ou=
t to solve.   And I think what a couple of people have been saying here (wit=
h which I agree) is that it is in fact possible to get this essentially for f=
ree.


From brian.e.carpenter@gmail.com  Tue Nov 15 16:26:10 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DF681F0C45 for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 16:26:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.218
X-Spam-Level: 
X-Spam-Status: No, score=-103.218 tagged_above=-999 required=5 tests=[AWL=0.381, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ihygICRBxRrQ for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 16:26:09 -0800 (PST)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id B66B41F0C3F for <homenet@ietf.org>; Tue, 15 Nov 2011 16:26:09 -0800 (PST)
Received: by vws5 with SMTP id 5so8262875vws.31 for <homenet@ietf.org>; Tue, 15 Nov 2011 16:26:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=eLmTl9JOFGtep/5+RuCbPAZl17fyeIUSqr7AuK5Zc/I=; b=dlwIhU2vilexcj/wfbAfzphbL0aMCRvni5kkSIgxxLtoXglnjMhprtEuBftcQhzeqk L5jyxmOjcLI8cnog47dMD+aCROh7xe4aQHOrJPIjRA3yRcWlcDcN1KnP41ESc8Rwoe3u gPZZhZFDGSSPepxdBxN2jm03GiU54mFpaahMw=
Received: by 10.52.32.163 with SMTP id k3mr46806415vdi.33.1321403169077; Tue, 15 Nov 2011 16:26:09 -0800 (PST)
Received: from [192.168.0.217] (61-31-89-133.static.tfn.net.tw. [61.31.89.133]) by mx.google.com with ESMTPS id t20sm39993112vdi.10.2011.11.15.16.26.05 (version=SSLv3 cipher=OTHER); Tue, 15 Nov 2011 16:26:08 -0800 (PST)
Message-ID: <4EC30317.8080503@gmail.com>
Date: Wed, 16 Nov 2011 13:25:59 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Ted Lemon <mellon@fugue.com>
References: <4EC1C386.6010802@gmail.com> <4EC1C566.2060400@cisco.com> <4EC1CC2E.30209@gmail.com> <4EC1D6C9.3030107@cisco.com> <CAKD1Yr3rFJonkJ1CbCgGPpr-WDj1RFmR6q4jDab1Toc0tJJodg@mail.gmail.com> <4EC1FF9A.4080308@bogus.com> <4EC2028E.6050305@gmail.com> <4EC20405.8040505@bogus.com> <4EC2FB44.2020807@gmail.com> <D99F1C65-2B6D-407A-88F3-EEAADB7E9B07@fugue.com>
In-Reply-To: <D99F1C65-2B6D-407A-88F3-EEAADB7E9B07@fugue.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Joel jaeggli <joelja@bogus.com>, Erik Nordmark <nordmark@cisco.com>, "homenet@ietf.org" <homenet@ietf.org>, Lorenzo Colitti <lorenzo@google.com>
Subject: Re: [homenet] pervasive v4
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 16 Nov 2011 00:26:10 -0000

On 2011-11-16 13:09, Ted Lemon wrote:
> On Nov 16, 2011, at 7:52 AM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>> But afaik this isn't
>> the 'make IPv4 work better' WG. That means that the requirement
>> to not break IPv4 actually constrains the possible topologies
>> for IPv6.
> 
> This was definitely not the sense of the working group in the meeting.   The sense of the working group was "if the IPv6 topology works, but the IPv4 topology doesn't, oh well."   The consensus seemed to be that it was better to make IPv6 work well than to constrain the solution so that topologies in which IPv4 wouldn't work would also break IPv6 (which, let's be clear, is essentially what you are suggesting).

My statement was intended to be conditional, but doesn't quite read that way.

However, I suspect that the average user won't be happy if IPv6 works in
the bedroom but IPv4 doesn't, so I'm not sure the consensus you mention will
hold in the market.

> Having said that, if there's a way to make IPv4 topologies that either don't work, or work poorly, with a modern IPv4 NAT router, work well with a homenet router, and it's possible to get that essentially for free, then I think it's worth getting, even though that's certainly not the problem we've set out to solve.   And I think what a couple of people have been saying here (with which I agree) is that it is in fact possible to get this essentially for free.

Yes, but I'd like to see it described in terms of real products, not
what is theoretically possible.

   Brian

From mellon@fugue.com  Tue Nov 15 16:54:36 2011
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 867BF11E80B2 for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 16:54:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.203
X-Spam-Level: 
X-Spam-Status: No, score=-1.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z98PNdXB1sKt for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 16:54:35 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 31E9011E8082 for <homenet@ietf.org>; Tue, 15 Nov 2011 16:54:35 -0800 (PST)
Received: from [130.129.86.106] (dhcp-566a.meeting.ietf.org [130.129.86.106]) by toccata.fugue.com (Postfix) with ESMTPSA id 1D5C02381DF4; Tue, 15 Nov 2011 19:54:34 -0500 (EST)
References: <4EC1C386.6010802@gmail.com> <4EC1C566.2060400@cisco.com> <4EC1CC2E.30209@gmail.com> <4EC1D6C9.3030107@cisco.com> <CAKD1Yr3rFJonkJ1CbCgGPpr-WDj1RFmR6q4jDab1Toc0tJJodg@mail.gmail.com> <4EC1FF9A.4080308@bogus.com> <4EC2028E.6050305@gmail.com> <4EC20405.8040505@bogus.com> <4EC2FB44.2020807@gmail.com> <D99F1C65-2B6D-407A-88F3-EEAADB7E9B07@fugue.com> <4EC30317.8080503@gmail.com>
In-Reply-To: <4EC30317.8080503@gmail.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <D0811E6D-3AFC-42C3-B590-973BB1C7D141@fugue.com>
X-Mailer: iPad Mail (9A334)
From: Ted Lemon <mellon@fugue.com>
Date: Wed, 16 Nov 2011 08:55:05 +0800
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: Joel jaeggli <joelja@bogus.com>, Erik Nordmark <nordmark@cisco.com>, "homenet@ietf.org" <homenet@ietf.org>, Lorenzo Colitti <lorenzo@google.com>
Subject: Re: [homenet] pervasive v4
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 16 Nov 2011 00:54:36 -0000

On Nov 16, 2011, at 8:25 AM, Brian E Carpenter <brian.e.carpenter@gmail.com>=
 wrote:
> However, I suspect that the average user won't be happy if IPv6 works in
> the bedroom but IPv4 doesn't, so I'm not sure the consensus you mention wi=
ll
> hold in the market.

Why would the average user even notice that IPv4 is broken?   But yes, if th=
ey would notice, then it would be good if it weren't broken.

> Yes, but I'd like to see it described in terms of real products, not
> what is theoretically possible.

If by real products, you mean things you can buy today, I don't agree, but i=
f you mean that homenet gateways ought to not break IPv4, I certainly agree.=



From brian.e.carpenter@gmail.com  Tue Nov 15 17:00:26 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C6F1111E80E4 for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 17:00:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.54
X-Spam-Level: 
X-Spam-Status: No, score=-103.54 tagged_above=-999 required=5 tests=[AWL=0.059, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cAv1Ae82m37R for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 17:00:26 -0800 (PST)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 00E0511E80DD for <homenet@ietf.org>; Tue, 15 Nov 2011 17:00:25 -0800 (PST)
Received: by vws5 with SMTP id 5so8293069vws.31 for <homenet@ietf.org>; Tue, 15 Nov 2011 17:00:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=HVc52hpysMt9tnUnvrwZilz1kv5YBqcq45PQdWd4hgA=; b=IFXub8gdlniCdaEd8rUQibWl2xN8hy6wlabeD3zPdVm1XuvOHbXShfFjKKWkpirQhm MFNfc3YhZPhqn3xvRrGgEUgtds5iwpmBDYuZRKQIr0kIEuWKSXsD+1+nSx4dLVBDV/uY E5Gbn1fA4JhiN17+RC8XGQqYXL3aR/njAqAew=
Received: by 10.52.27.72 with SMTP id r8mr46551877vdg.71.1321405225431; Tue, 15 Nov 2011 17:00:25 -0800 (PST)
Received: from [130.129.19.92] (dhcp-135c.meeting.ietf.org. [130.129.19.92]) by mx.google.com with ESMTPS id eu4sm40197468vdc.8.2011.11.15.17.00.22 (version=SSLv3 cipher=OTHER); Tue, 15 Nov 2011 17:00:24 -0800 (PST)
Message-ID: <4EC30B20.4090507@gmail.com>
Date: Wed, 16 Nov 2011 14:00:16 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Ted Lemon <mellon@fugue.com>
References: <4EC1C386.6010802@gmail.com> <4EC1C566.2060400@cisco.com> <4EC1CC2E.30209@gmail.com> <4EC1D6C9.3030107@cisco.com> <CAKD1Yr3rFJonkJ1CbCgGPpr-WDj1RFmR6q4jDab1Toc0tJJodg@mail.gmail.com> <4EC1FF9A.4080308@bogus.com> <4EC2028E.6050305@gmail.com> <4EC20405.8040505@bogus.com> <4EC2FB44.2020807@gmail.com> <D99F1C65-2B6D-407A-88F3-EEAADB7E9B07@fugue.com> <4EC30317.8080503@gmail.com> <D0811E6D-3AFC-42C3-B590-973BB1C7D141@fugue.com>
In-Reply-To: <D0811E6D-3AFC-42C3-B590-973BB1C7D141@fugue.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: Joel jaeggli <joelja@bogus.com>, Erik Nordmark <nordmark@cisco.com>, "homenet@ietf.org" <homenet@ietf.org>, Lorenzo Colitti <lorenzo@google.com>
Subject: Re: [homenet] pervasive v4
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 16 Nov 2011 01:00:26 -0000

On 2011-11-16 13:55, Ted Lemon wrote:
> On Nov 16, 2011, at 8:25 AM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>> However, I suspect that the average user won't be happy if IPv6 works in
>> the bedroom but IPv4 doesn't, so I'm not sure the consensus you mention will
>> hold in the market.
> 
> Why would the average user even notice that IPv4 is broken?   But yes, if they would notice, then it would be good if it weren't broken.
> 
>> Yes, but I'd like to see it described in terms of real products, not
>> what is theoretically possible.
> 
> If by real products, you mean things you can buy today, I don't agree, but if you mean that homenet gateways ought to not break IPv4, I certainly agree.

What will happen if a user hangs an existing v4-only box bought in the supermarket
off a new homenet-conforming box? I'm not saying we have to guarantee that
it works, but at least we need to understand the possible breakages (IMHO).

   Brian

From mellon@fugue.com  Tue Nov 15 17:07:22 2011
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCF4611E8107 for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 17:07:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.203
X-Spam-Level: 
X-Spam-Status: No, score=-1.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fyq93T28wzgU for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 17:07:21 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 8CFF511E8102 for <homenet@ietf.org>; Tue, 15 Nov 2011 17:07:21 -0800 (PST)
Received: from [130.129.86.106] (dhcp-566a.meeting.ietf.org [130.129.86.106]) by toccata.fugue.com (Postfix) with ESMTPSA id 304512381DF4 for <homenet@ietf.org>; Tue, 15 Nov 2011 20:07:20 -0500 (EST)
References: <4EC1C386.6010802@gmail.com> <4EC1C566.2060400@cisco.com> <4EC1CC2E.30209@gmail.com> <4EC1D6C9.3030107@cisco.com> <CAKD1Yr3rFJonkJ1CbCgGPpr-WDj1RFmR6q4jDab1Toc0tJJodg@mail.gmail.com> <4EC1FF9A.4080308@bogus.com> <4EC2028E.6050305@gmail.com> <4EC20405.8040505@bogus.com> <4EC2FB44.2020807@gmail.com> <D99F1C65-2B6D-407A-88F3-EEAADB7E9B07@fugue.com> <4EC30317.8080503@gmail.com> <D0811E6D-3AFC-42C3-B590-973BB1C7D141@fugue.com> <4EC30B20.4090507@gmail.com>
From: Ted Lemon <mellon@fugue.com>
Content-Type: text/plain; charset=us-ascii
X-Mailer: iPad Mail (9A334)
In-Reply-To: <4EC30B20.4090507@gmail.com>
Message-Id: <C861D22D-4EE1-4E01-8AD2-5CB6345CF14C@fugue.com>
Date: Wed, 16 Nov 2011 09:07:52 +0800
To: "homenet@ietf.org" <homenet@ietf.org>
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
Subject: Re: [homenet] pervasive v4
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 16 Nov 2011 01:07:22 -0000

On Nov 16, 2011, at 9:00 AM, Brian E Carpenter <brian.e.carpenter@gmail.com>=
 wrote:
> What will happen if a user hangs an existing v4-only box bought in the sup=
ermarket
> off a new homenet-conforming box? I'm not saying we have to guarantee that=

> it works, but at least we need to understand the possible breakages (IMHO)=
.

Sure.   In point of fact, it will work just as well as if they did the same t=
hing with a non-homenet-conforming box, and possibly better.   In some cases=
 that means it will work; in some cases it means it will not.   IOW, homenet=
 won't make things worse.   So it's hard to accept the notion that, in the e=
vent that IPv4 breaks in this case, IPv6 ought to break as well.   Of course=
, since this is a non-homenet router, possibly it doesn't support IPv6 anywa=
y.


From lee.howard@twcable.com  Tue Nov 15 18:06:20 2011
Return-Path: <lee.howard@twcable.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 57D281F0C95 for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 18:06:20 -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=[AWL=-0.238, BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E6+eL-TuQUkg for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 18:06:16 -0800 (PST)
Received: from cdpipgw02.twcable.com (cdpipgw02.twcable.com [165.237.59.23]) by ietfa.amsl.com (Postfix) with ESMTP id 3339E11E8156 for <homenet@ietf.org>; Tue, 15 Nov 2011 18:06:16 -0800 (PST)
X-SENDER-IP: 10.136.163.11
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.69,517,1315195200"; d="scan'208";a="282608314"
Received: from unknown (HELO PRVPEXHUB02.corp.twcable.com) ([10.136.163.11]) by cdpipgw02.twcable.com with ESMTP/TLS/RC4-MD5; 15 Nov 2011 21:01:10 -0500
Received: from PRVPEXVS03.corp.twcable.com ([10.136.163.26]) by PRVPEXHUB02.corp.twcable.com ([10.136.163.11]) with mapi; Tue, 15 Nov 2011 21:06:10 -0500
From: "Howard, Lee" <lee.howard@twcable.com>
To: Ted Lemon <mellon@fugue.com>
Date: Tue, 15 Nov 2011 21:06:08 -0500
Thread-Topic: [homenet] pervasive v4
Thread-Index: AcykBE7VNPIda2SIS+K2ZH7oxDpzGA==
Message-ID: <A08E48D6-1867-4AC1-AB6F-B079BBD5C4EB@twcable.com>
References: <4EC1C386.6010802@gmail.com> <4EC1C566.2060400@cisco.com> <4EC1CC2E.30209@gmail.com> <4EC1D6C9.3030107@cisco.com> <CAKD1Yr3rFJonkJ1CbCgGPpr-WDj1RFmR6q4jDab1Toc0tJJodg@mail.gmail.com> <4EC1FF9A.4080308@bogus.com> <4EC2028E.6050305@gmail.com> <4EC20405.8040505@bogus.com> <4EC2FB44.2020807@gmail.com> <D99F1C65-2B6D-407A-88F3-EEAADB7E9B07@fugue.com> <4EC30317.8080503@gmail.com> <D0811E6D-3AFC-42C3-B590-973BB1C7D141@fugue.com> <4EC30B20.4090507@gmail.com> <C861D22D-4EE1-4E01-8AD2-5CB6345CF14C@fugue.com>
In-Reply-To: <C861D22D-4EE1-4E01-8AD2-5CB6345CF14C@fugue.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "homenet@ietf.org" <homenet@ietf.org>
Subject: Re: [homenet] pervasive v4
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 16 Nov 2011 02:06:20 -0000

On Nov 16, 2011, at 9:07 AM, Ted Lemon wrote:

> On Nov 16, 2011, at 9:00 AM, Brian E Carpenter <brian.e.carpenter@gmail.c=
om> wrote:
>> What will happen if a user hangs an existing v4-only box bought in the s=
upermarket
>> off a new homenet-conforming box? I'm not saying we have to guarantee th=
at
>> it works, but at least we need to understand the possible breakages (IMH=
O).
>
> Sure.   In point of fact, it will work just as well as if they did the sa=
me thing with a non-homenet-conforming box, and possibly better.   In some =
cases that means it will work; in some cases it means it will not.   IOW, h=
omenet won't make things worse.   So it's hard to accept the notion that, i=
n the event that IPv4 breaks in this case, IPv6 ought to break as well.   O=
f course, since this is a non-homenet router, possibly it doesn't support I=
Pv6 anyway.
>

I agree with this.  Something breaking in IPv4 does not mean it should brea=
k in IPv6.
My reading of our charter is that we must not break IPv4 in order to get IP=
v6 to work, but that doesn't mean  that IPv6 goodness can't be a superset o=
f IPv4 goodness.

Lee


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


This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

From russw@riw.us  Tue Nov 15 19:18:25 2011
Return-Path: <russw@riw.us>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A627D21F8F4E for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 19:18:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.542
X-Spam-Level: 
X-Spam-Status: No, score=-2.542 tagged_above=-999 required=5 tests=[AWL=0.057,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LncqCs9cjnX6 for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 19:18:25 -0800 (PST)
Received: from ecbiz91.inmotionhosting.com (ecbiz91.inmotionhosting.com [173.205.124.250]) by ietfa.amsl.com (Postfix) with ESMTP id 2A38B21F8F3E for <homenet@ietf.org>; Tue, 15 Nov 2011 19:18:25 -0800 (PST)
Received: from [107.17.45.77] (port=49777) by ecbiz91.inmotionhosting.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <russw@riw.us>) id 1RQW0z-0006pv-Qi; Tue, 15 Nov 2011 22:18:21 -0500
Message-ID: <4EC32B76.8080706@riw.us>
Date: Tue, 15 Nov 2011 22:18:14 -0500
From: Russ White <russw@riw.us>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Ted Lemon <mellon@fugue.com>
References: <4EC1D206.2070303@gmail.com> <3C716203-8579-41EA-98CE-6DC3BE9261D8@fugue.com> <FC520CA0-BAA4-4309-A878-CB40308F2562@cisco.com> <09215FB7-EA7A-4D9D-8772-737B79CBBD20@fugue.com>
In-Reply-To: <09215FB7-EA7A-4D9D-8772-737B79CBBD20@fugue.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - ecbiz91.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - riw.us
Cc: Ole Troan <ot@cisco.com>, "homenet@ietf.org" <homenet@ietf.org>, Fred Baker <fred@cisco.com>
Subject: Re: [homenet] draft-baker-homenet-prefix-assignment
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 16 Nov 2011 03:18:25 -0000

> Right now clients don't pick the best one--they just pick one pretty much at random.  But yes, if you have two DHCP servers providing different information, you need to resolve that.   We would have to write a spec to handle thisâ€”it's not handled in the existing protocol.

We need to be aware that not every network may be able to reach the
Internet... So you might need to have an address from every available
DHCP server, not just the "best," one, or even a "random," one.

For instance, your computer might talk to the power company, but the
power company doesn't want to transit your internet traffic. I'm not
saying this is a certainty, only that we need to think about it somehow.

:-)

Russ


From cpignata@cisco.com  Tue Nov 15 19:34:47 2011
Return-Path: <cpignata@cisco.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 372D21F0C45 for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 19:34:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.33
X-Spam-Level: 
X-Spam-Status: No, score=-104.33 tagged_above=-999 required=5 tests=[AWL=-1.194, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4, RCVD_NUMERIC_HELO=2.067, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lDcPIxK+Ye7H for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 19:34:43 -0800 (PST)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id BF1B81F0C35 for <homenet@ietf.org>; Tue, 15 Nov 2011 19:34:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=cpignata@cisco.com; l=5834; q=dns/txt; s=iport; t=1321414483; x=1322624083; h=subject:references:content-transfer-encoding:from: in-reply-to:message-id:date:to:cc:mime-version; bh=vJctBdhzyKrmz0Ay9+Etu1hdJ1UYYOWoLRcIRh5QOUg=; b=ADIXR0TjPqvrIAhNHjX6HoR3pvwtz+DE3Hp3bVyLA3WTMfW0akVZ+3JS KLJXp6e2ZtO6RQf7YozNRrKTJnqSt6E6K1BL+NUA+7bVQqJ1/X1iTpL0d Wvn5CDv/iM/ulo6HpOUSRIpWo91HkaRkSUume6MgzVJjp+Vztcj9TYfWz 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AoEGADsvw06tJV2c/2dsb2JhbABDqHV7AoEFgXIBAQEDAQEBAQ8BJzQLBQsCAQgYJwcnHxEBAQQTIodgCJpFAZ5ZiTRjBIgUjCCFRIxW
X-IronPort-AV: E=Sophos;i="4.69,518,1315180800"; d="scan'208";a="36397091"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-5.cisco.com with ESMTP; 16 Nov 2011 03:34:38 +0000
Received: from xbh-rcd-102.cisco.com (xbh-rcd-102.cisco.com [72.163.62.139]) by rcdn-core-5.cisco.com (8.14.3/8.14.3) with ESMTP id pAG3YcVq013462;  Wed, 16 Nov 2011 03:34:38 GMT
Received: from xmb-rcd-206.cisco.com ([72.163.62.213]) by xbh-rcd-102.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 15 Nov 2011 21:34:37 -0600
Received: from 72.163.62.136 ([72.163.62.136]) by XMB-RCD-206.cisco.com ([72.163.62.213]) with Microsoft Exchange Server HTTP-DAV ;  Wed, 16 Nov 2011 03:34:37 +0000
References: <CAKD1Yr3uSsNP4avZBdQE7YxFd7D_KOXBOCsfaRfvnWhJoLoY9Q@mail.gmail.com> <B3BE775A-4EBB-4C17-9EDC-7B9AFCB8867E@ericsson.com> <CAKD1Yr0MFdyBopr0E0WiebLSZ+M2J9vAi1U6b66VxhziE2XJpw@mail.gmail.com> <FF6FB9A0-9F91-4658-A265-BA200A0858AF@ericsson.com> <4EC29D17.10302@cisco.com> <6A2F0A68-5D4F-4742-A95F-18688525D6B7@ericsson.com>
Content-Transfer-Encoding: quoted-printable
From: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
Content-Type: text/plain; charset="us-ascii"
In-Reply-To: <6A2F0A68-5D4F-4742-A95F-18688525D6B7@ericsson.com>
thread-topic: [homenet] Comments on draft-acee-ospf-ospfv3-autoconfig-00
Message-ID: <D4EF568D-2AFF-4212-B6C0-960DE0673449@cisco.com>
thread-index: AcykEKpirb2ChjMWRgGSZX55OX0rYQ==
Date: Tue, 15 Nov 2011 22:34:37 -0500
To: "Acee Lindem" <acee.lindem@ericsson.com>
MIME-Version: 1.0 (1.0)
X-OriginalArrivalTime: 16 Nov 2011 03:34:37.0954 (UTC) FILETIME=[AAD6D620:01CCA410]
Cc: homenet@ietf.org, Jari Arkko <jari.arkko@piuha.net>, Lorenzo Colitti <lorenzo@google.com>
Subject: Re: [homenet] Comments on draft-acee-ospf-ospfv3-autoconfig-00
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 16 Nov 2011 03:34:47 -0000

Hi Acee,

On Nov 15, 2011, at 1:39 PM, "Acee Lindem" <acee.lindem@ericsson.com> wrote:=


> Hi Carlos,
>=20
> On Nov 15, 2011, at 12:10 PM, Carlos Pignataro wrote:
>=20
>> Hi Acee,
>>=20
>> On 11/14/2011 10:11 PM, Acee Lindem wrote:
>>>=20
>>> On Nov 14, 2011, at 9:46 PM, Lorenzo Colitti wrote:
>>>=20
>>>> On Tue, Nov 15, 2011 at 10:25, Acee Lindem <acee.lindem@ericsson.com
>>>> <mailto:acee.lindem@ericsson.com>> wrote:
>>>>=20
>>>>> 1. I think the OSPFv3 router ID should not be based on the MAC
>>>>   address because that will encourage people to assume it's unique
>>>>   "most of the time". I think we should just make it a pseudo-random
>>>>   number so it's clear that uniqueness is only guaranteed by
>>>>   collision detection and that collision detection needs to be robust.
>>>>=20
>>>>   The draft requires duplicate Router-ID detection and resolution. I
>>>>   don't think that the fact that a portion of the MAC address is
>>>>   used as a first try is reason for this detection/resolution not to
>>>>   be implemented or tested.
>>>>=20
>>>>=20
>>>> In my experience, giving people something that works "most of the
>>>> time" will cause the cases where it doesn't work to break. I think
>>>> it's better to explicitly provide no guarantees of uniqueness to make
>>>> it clear that collision detection needs to be robust.=20
>>>=20
>>> In the OSPF WG, the fact that a mechanism is specified implies that it
>>> is required to be robust.=20
>>>=20
>>>> Also, if we rely on collision detection, then what's the advantage of
>>>> using the MAC address? We might as well as make it random all the time
>>>> - that probably has a lower chance of collision anyway.
>>>=20
>>> I can't disagree with this argument and think we could go with a
>>> psuedo-random number seeded with a hash on the hardware fingerprint as
>>> the first try for router-id.=20
>>>=20
>>=20
>> As a side note, what's your opinion on citing and suggesting/requiring
>> <http://tools.ietf.org/html/rfc5642#section-4> for manageability?
>=20
> I think the dynamic host-name is less applicable in an auto-configured rou=
ting domain than other domains. In the auto-configured routing domain, you h=
ope that little monitoring, debugging, or interaction is required.=20

I agree that a goal is for less monitoring and interaction in this deploymen=
t model -- however sometimes less troubleshooting is aspirational, and debug=
ging cannot be avoided :-) for those cases, a human-parseable node string is=
 quite handy (especially when with pseudo-random -- potentially changing on r=
eload or electrical hiccup (?) -- router-ids).  Thinking aloud a bit as I se=
e both sides; but acknowledging that a stable node reference can help in tro=
ubleshooting (if/when required)

Thanks!

Carlos P.

> Thanks,
> Acee
>=20
>=20
>=20
>>=20
>> Thanks,
>>=20
>> -- Carlos.
>>=20
>>>>=20
>>>>   I think you mean virtual links. They are definitely not needed in
>>>>   the auto-configured environment as they are for providing a
>>>>   backbone path through a transit area and the OSPFv3
>>>>   auto-configured routing domain assumes only a backbone area.
>>>>=20
>>>>=20
>>>> Yes, virtual links. Do we need to state explicitly that they cannot
>>>> exist and are not supported?
>>>=20
>>> Since the auto-configured routing domain is area 0 only, it is explicit.=
=20
>>>=20
>>>>=20
>>>>=20
>>>>> 3. Can we use normal LSAs to detect collisions? One idea would
>>>>   be "if you see your own router ID in the list of neighbours of a
>>>>   network LSA or router LSA, then there is a collision". Will that
>>>>   work? If so we wouldn't need the hardware fingerprint at all.
>>>>=20
>>>>   No. In an arbitrary topology, A router with a duplicate router-id
>>>>   can be multiple hops away.
>>>>=20
>>>>=20
>>>> Yes, but router and network LSAs are flooded, so you'll hear them
>>>> regardless of whether your duplicate is multiple hops away, no?
>>>=20
>>> Both OSPFv3 and OSPFv2 would consider an unrecognized self-originated
>>> LSA, i.e. having our Route-ID, as a stale LSA and purge it. This is a
>>> very basic mechanism of OSPF. I'd rather use a separate mechanism for
>>> duplicate Router-ID detection. I considered techniques involving the
>>> encoding some additional information in the Router-LSA but these all
>>> seemed to be hacked.=20
>>>=20
>>>=20
>>>>=20
>>>>=20
>>>>   If the pre-shared key is hard-coded, it is no better than the
>>>>   OSPFv3 Interface Instance ID that is specified to prevent
>>>>   inadvertent adjacencies with routers not supporting the
>>>>   auto-configuration. If configuration of a pre-shared key is
>>>>   required, you no longer have auto-configuration.
>>>>=20
>>>>=20
>>>> Sorry, that wasn't clear. What I meant to say is that we should pick
>>>> one scheme (e.g., HMAC-SHA) and stick to it; we shouldn't support
>>>> multiple schemes as that will lead to interoperability issues for
>>>> devices that use one scheme and devices that use another scheme.
>>>=20
>>> The OSPFv3 Instance ID is part of the base OSPFv3 specification and I
>>> think it is a very good mechanism to prevent inadvertent adjacencies. If=

>>> we need real authentication, we'll need a pre-shared key. I don't see
>>> any advantage of authentication with a well-known pre-shared key to
>>> prevent inadvertent adjacencies.=20
>>>=20
>>> Thanks for the comments,
>>> Acee=20
>>>=20
>>>=20
>>>=20
>>>=20
>>> _______________________________________________
>>> 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
>=20

From mellon@fugue.com  Tue Nov 15 20:09:01 2011
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF6C821F8E14 for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 20:09:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.23
X-Spam-Level: 
X-Spam-Status: No, score=-1.23 tagged_above=-999 required=5 tests=[AWL=-0.027,  BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IiMlRXEeALMR for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 20:09:01 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 5EB7D21F8DD9 for <homenet@ietf.org>; Tue, 15 Nov 2011 20:09:01 -0800 (PST)
Received: from [172.22.13.155] (unknown [122.147.240.7]) by toccata.fugue.com (Postfix) with ESMTPSA id 0E47D2381DF4; Tue, 15 Nov 2011 23:08:57 -0500 (EST)
References: <4EC1D206.2070303@gmail.com> <3C716203-8579-41EA-98CE-6DC3BE9261D8@fugue.com> <FC520CA0-BAA4-4309-A878-CB40308F2562@cisco.com> <09215FB7-EA7A-4D9D-8772-737B79CBBD20@fugue.com> <4EC32B76.8080706@riw.us>
In-Reply-To: <4EC32B76.8080706@riw.us>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <7DADF53B-56CA-47CC-BBDA-34300EE4D22D@fugue.com>
X-Mailer: iPad Mail (9A334)
From: Ted Lemon <mellon@fugue.com>
Date: Wed, 16 Nov 2011 12:09:29 +0800
To: Russ White <russw@riw.us>
Cc: Ole Troan <ot@cisco.com>, "homenet@ietf.org" <homenet@ietf.org>, Fred Baker <fred@cisco.com>
Subject: Re: [homenet] draft-baker-homenet-prefix-assignment
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 16 Nov 2011 04:09:01 -0000

On Nov 16, 2011, at 11:18 AM, Russ White <russw@riw.us> wrote:
> We need to be aware that not every network may be able to reach the
> Internet... So you might need to have an address from every available
> DHCP server, not just the "best," one, or even a "random," one.

Yes, this is part of a problem space of which I have become keenly aware ove=
r the course of this IETF meeting.   Expect a draft shortly.   :)


From nordmark@cisco.com  Tue Nov 15 21:31:26 2011
Return-Path: <nordmark@cisco.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 342821F0CB7 for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 21:31:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.313
X-Spam-Level: 
X-Spam-Status: No, score=-6.313 tagged_above=-999 required=5 tests=[AWL=0.286,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oA59G--ps8Jg for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 21:31:21 -0800 (PST)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id 865B61F0C61 for <homenet@ietf.org>; Tue, 15 Nov 2011 21:31:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=nordmark@cisco.com; l=900; q=dns/txt; s=iport; t=1321421481; x=1322631081; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=qXrz/eBUVJkqNkTPweQVougLu9FFmTaKDIIuCWbrzLw=; b=gRRGosp+mfk+D49BWFICe539u0bz86Er8BCj6TDpkcXfNAF8dLt/cM2g i1HWHVN36FztEEGNZ+M8cmnKRpdOZ0JgxzoHa9zQbdUFbxJyq3QTowcXj JgcvY/PwTi/0DHLUFRPgUWuEyLrvzj+ADjqtWz7FDX71K8fHLGFKBGt+W g=;
X-IronPort-AV: E=Sophos;i="4.69,519,1315180800"; d="scan'208";a="12780502"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-1.cisco.com with ESMTP; 16 Nov 2011 05:31:21 +0000
Received: from [130.129.83.144] (sjc-vpn7-626.cisco.com [10.21.146.114]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id pAG5VKf7027932; Wed, 16 Nov 2011 05:31:20 GMT
Message-ID: <4EC34AB2.1040609@cisco.com>
Date: Tue, 15 Nov 2011 21:31:30 -0800
From: Erik Nordmark <nordmark@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: "Howard, Lee" <lee.howard@twcable.com>
References: <4EC1C386.6010802@gmail.com> <4EC1C566.2060400@cisco.com> <4EC1CC2E.30209@gmail.com> <4EC1D6C9.3030107@cisco.com> <CAKD1Yr3rFJonkJ1CbCgGPpr-WDj1RFmR6q4jDab1Toc0tJJodg@mail.gmail.com> <4EC1FF9A.4080308@bogus.com> <4EC2028E.6050305@gmail.com> <4EC20405.8040505@bogus.com> <4EC2FB44.2020807@gmail.com> <D99F1C65-2B6D-407A-88F3-EEAADB7E9B07@fugue.com> <4EC30317.8080503@gmail.com> <D0811E6D-3AFC-42C3-B590-973BB1C7D141@fugue.com> <4EC30B20.4090507@gmail.com> <C861D22D-4EE1-4E01-8AD2-5CB6345CF14C@fugue.com> <A08E48D6-1867-4AC1-AB6F-B079BBD5C4EB@twcable.com>
In-Reply-To: <A08E48D6-1867-4AC1-AB6F-B079BBD5C4EB@twcable.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "homenet@ietf.org" <homenet@ietf.org>, Ted Lemon <mellon@fugue.com>
Subject: Re: [homenet] pervasive v4
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 16 Nov 2011 05:31:26 -0000

On 11/15/11 6:06 PM, Howard, Lee wrote:

> I agree with this.  Something breaking in IPv4 does not mean it should break in IPv6.
> My reading of our charter is that we must not break IPv4 in order to get IPv6 to work, but that doesn't mean  that IPv6 goodness can't be a superset of IPv4 goodness.

If we want to address the consumer expectations about ease of use yet 
deliver more capable home networks, then I think we need to be aware of 
the total complexity of the home network.

A network where both IPv4 and IPv6 are used, yet the topology for the 
inside the home is different, significantly increases the complexity.

The service call will be something like "the internet is working fine, 
but the printer is broken" when the laptop uses dual-stack but the 
printer is IPv4 only.

I uniformity (within the home) is better if we care about complexity.

Regards,
    Erik



From ot@cisco.com  Tue Nov 15 22:05:40 2011
Return-Path: <ot@cisco.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DAA051F0D38 for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 22:05:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ANjq3g25SFiA for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 22:05:36 -0800 (PST)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id A07191F0D32 for <homenet@ietf.org>; Tue, 15 Nov 2011 22:05:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ot@cisco.com; l=569; q=dns/txt; s=iport; t=1321423536; x=1322633136; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=1lGogW/fzewovkBB2McIQ4wb2tx6KYfPFhtwlFiryfc=; b=Lfu4kpf+HIbneowslWbUgitmTpsfjm01Cbomkw4YTSOCRHdwecUcL/46 GrNq6eQ9aoOmJMYK0qQRm7ytnSscBxlM+HhmHBrt5+rwsA+RONPPpK8hG noE2rr5WEHjInsL6Q9cFjNYcI5FFLEs82BJbB+4grhNn1jh7zk83HjdDQ I=;
X-IronPort-AV: E=Sophos;i="4.69,519,1315180800"; d="scan'208";a="14491058"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-3.cisco.com with ESMTP; 16 Nov 2011 06:05:36 +0000
Received: from sjc-vpn6-1305.cisco.com (sjc-vpn6-1305.cisco.com [10.21.125.25]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id pAG65ZVX011256; Wed, 16 Nov 2011 06:05:35 GMT
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Ole Troan <ot@cisco.com>
In-Reply-To: <7DADF53B-56CA-47CC-BBDA-34300EE4D22D@fugue.com>
Date: Wed, 16 Nov 2011 13:52:51 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <7D0889B6-7769-4F74-996D-08CDA02B3670@cisco.com>
References: <4EC1D206.2070303@gmail.com> <3C716203-8579-41EA-98CE-6DC3BE9261D8@fugue.com> <FC520CA0-BAA4-4309-A878-CB40308F2562@cisco.com> <09215FB7-EA7A-4D9D-8772-737B79CBBD20@fugue.com> <4EC32B76.8080706@riw.us> <7DADF53B-56CA-47CC-BBDA-34300EE4D22D@fugue.com>
To: Ted Lemon <mellon@fugue.com>
X-Mailer: Apple Mail (2.1084)
Cc: Russ White <russw@riw.us>, "homenet@ietf.org" <homenet@ietf.org>, Fred Baker <fred@cisco.com>
Subject: Re: [homenet] draft-baker-homenet-prefix-assignment
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 16 Nov 2011 06:05:41 -0000

>> We need to be aware that not every network may be able to reach the
>> Internet... So you might need to have an address from every available
>> DHCP server, not just the "best," one, or even a "random," one.
>=20
> Yes, this is part of a problem space of which I have become keenly =
aware over the course of this IETF meeting.   Expect a draft shortly.   =
:)

do we need to?
in a self organizing unmanaged home; if we were to do a combination of a =
network wide flooding mechanism and RAs. would we need DHCP in the =
network at all?

cheers,
Ole=

From mellon@fugue.com  Tue Nov 15 22:28:46 2011
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8147A11E812B for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 22:28:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.229
X-Spam-Level: 
X-Spam-Status: No, score=-1.229 tagged_above=-999 required=5 tests=[AWL=-0.026, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RMWevLOrla2O for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 22:28:46 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 1DD9C11E8123 for <homenet@ietf.org>; Tue, 15 Nov 2011 22:28:46 -0800 (PST)
Received: from [172.22.13.155] (unknown [122.147.240.7]) by toccata.fugue.com (Postfix) with ESMTPSA id 43CBD2381DF4; Wed, 16 Nov 2011 01:28:43 -0500 (EST)
References: <4EC1C386.6010802@gmail.com> <4EC1C566.2060400@cisco.com> <4EC1CC2E.30209@gmail.com> <4EC1D6C9.3030107@cisco.com> <CAKD1Yr3rFJonkJ1CbCgGPpr-WDj1RFmR6q4jDab1Toc0tJJodg@mail.gmail.com> <4EC1FF9A.4080308@bogus.com> <4EC2028E.6050305@gmail.com> <4EC20405.8040505@bogus.com> <4EC2FB44.2020807@gmail.com> <D99F1C65-2B6D-407A-88F3-EEAADB7E9B07@fugue.com> <4EC30317.8080503@gmail.com> <D0811E6D-3AFC-42C3-B590-973BB1C7D141@fugue.com> <4EC30B20.4090507@gmail.com> <C861D22D-4EE1-4E01-8AD2-5CB6345CF14C@fugue.com> <A08E48D6-1867-4AC1-AB6F-B079BBD5C4EB@twcable.com> <4EC34AB2.1040609@cisco.com>
In-Reply-To: <4EC34AB2.1040609@cisco.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <B4581271-026C-4BE4-B369-44E5E194F2D3@fugue.com>
X-Mailer: iPad Mail (9A334)
From: Ted Lemon <mellon@fugue.com>
Date: Wed, 16 Nov 2011 14:29:16 +0800
To: Erik Nordmark <nordmark@cisco.com>
Cc: "Howard, Lee" <lee.howard@twcable.com>, "homenet@ietf.org" <homenet@ietf.org>
Subject: Re: [homenet] pervasive v4
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 16 Nov 2011 06:28:46 -0000

On Nov 16, 2011, at 1:31 PM, Erik Nordmark <nordmark@cisco.com> wrote:
> The service call will be something like "the internet is working fine, but=
 the printer is broken" when the laptop uses dual-stack but the printer is I=
Pv4 only.
>=20
> I uniformity (within the home) is better if we care about complexity.

This is certainly a valid point, but you've got it backwards, since we're ta=
lking about bridging IPv4.  The real risk is that a bonjour printer will wor=
k only if you are plugged into the same router it is.=20=

From mellon@fugue.com  Tue Nov 15 22:30:30 2011
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66F8511E8144 for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 22:30:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.228
X-Spam-Level: 
X-Spam-Status: No, score=-1.228 tagged_above=-999 required=5 tests=[AWL=-0.025, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lWmzXrqNw2mt for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 22:30:30 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 25ECD11E8123 for <homenet@ietf.org>; Tue, 15 Nov 2011 22:30:30 -0800 (PST)
Received: from [172.22.13.155] (unknown [122.147.240.7]) by toccata.fugue.com (Postfix) with ESMTPSA id 3F5672381DF4; Wed, 16 Nov 2011 01:30:29 -0500 (EST)
References: <4EC1D206.2070303@gmail.com> <3C716203-8579-41EA-98CE-6DC3BE9261D8@fugue.com> <FC520CA0-BAA4-4309-A878-CB40308F2562@cisco.com> <09215FB7-EA7A-4D9D-8772-737B79CBBD20@fugue.com> <4EC32B76.8080706@riw.us> <7DADF53B-56CA-47CC-BBDA-34300EE4D22D@fugue.com> <7D0889B6-7769-4F74-996D-08CDA02B3670@cisco.com>
In-Reply-To: <7D0889B6-7769-4F74-996D-08CDA02B3670@cisco.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <21608A99-B37A-4406-A59A-479C87A2ABDF@fugue.com>
X-Mailer: iPad Mail (9A334)
From: Ted Lemon <mellon@fugue.com>
Date: Wed, 16 Nov 2011 14:31:02 +0800
To: Ole Troan <ot@cisco.com>
Cc: Russ White <russw@riw.us>, "homenet@ietf.org" <homenet@ietf.org>, Fred Baker <fred@cisco.com>
Subject: Re: [homenet] draft-baker-homenet-prefix-assignment
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 16 Nov 2011 06:30:30 -0000

On Nov 16, 2011, at 1:52 PM, Ole Troan <ot@cisco.com> wrote:
> do we need to?
> in a self organizing unmanaged home; if we were to do a combination of a n=
etwork wide flooding mechanism and RAs. would we need DHCP in the network at=
 all?

I am not claiming that we do. However, the problem exists whether we do DHCP=
 in homenet or not.=20=

From ot@cisco.com  Tue Nov 15 22:33:36 2011
Return-Path: <ot@cisco.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B4E9B11E80C6 for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 22:33:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bYNqtiOWX8gk for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 22:33:32 -0800 (PST)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id 3AFB011E8160 for <homenet@ietf.org>; Tue, 15 Nov 2011 22:33:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ot@cisco.com; l=328; q=dns/txt; s=iport; t=1321425211; x=1322634811; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=cFlcAS7k2zWrqmItqQmHsF5laaioGHTN+JLYS5un0fY=; b=BjoguHNs9GOuSr59RFiRc8K+mk66Lpuxi40KZ7rJOKuTIS0rtXewgy9S qiUPM6K9/exZCiTLra/cqUSvvQopftCBSFSe0YDwrWVkTvZN6P3ybGV9d dWUUF/Z9TnGZywwpHzySZW7p6etHqg2uJ4jIGFusMgCkHenjQkVSfwoxF A=;
X-IronPort-AV: E=Sophos;i="4.69,519,1315180800"; d="scan'208";a="12789051"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-1.cisco.com with ESMTP; 16 Nov 2011 06:33:31 +0000
Received: from sjc-vpn6-1305.cisco.com (sjc-vpn6-1305.cisco.com [10.21.125.25]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id pAG6XT3s026300; Wed, 16 Nov 2011 06:33:30 GMT
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Ole Troan <ot@cisco.com>
In-Reply-To: <21608A99-B37A-4406-A59A-479C87A2ABDF@fugue.com>
Date: Wed, 16 Nov 2011 14:33:29 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <6DBAF99F-C7CB-42C0-AC5D-30C50FEA3448@cisco.com>
References: <4EC1D206.2070303@gmail.com> <3C716203-8579-41EA-98CE-6DC3BE9261D8@fugue.com> <FC520CA0-BAA4-4309-A878-CB40308F2562@cisco.com> <09215FB7-EA7A-4D9D-8772-737B79CBBD20@fugue.com> <4EC32B76.8080706@riw.us> <7DADF53B-56CA-47CC-BBDA-34300EE4D22D@fugue.com> <7D0889B6-7769-4F74-996D-08CDA02B3670@cisco.com> <21608A99-B37A-4406-A59A-479C87A2ABDF@fugue.com>
To: Ted Lemon <mellon@fugue.com>
X-Mailer: Apple Mail (2.1084)
Cc: Russ White <russw@riw.us>, "homenet@ietf.org" <homenet@ietf.org>, Fred Baker <fred@cisco.com>
Subject: Re: [homenet] draft-baker-homenet-prefix-assignment
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 16 Nov 2011 06:33:36 -0000

>> do we need to?
>> in a self organizing unmanaged home; if we were to do a combination =
of a network wide flooding mechanism and RAs. would we need DHCP in the =
network at all?
>=20
> I am not claiming that we do. However, the problem exists whether we =
do DHCP in homenet or not.=20

yes, indeed.

cheers,
Ole


From rturner@amalfisystems.com  Tue Nov 15 22:34:00 2011
Return-Path: <rturner@amalfisystems.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C60EF11E80C6 for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 22:34:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.034
X-Spam-Level: 
X-Spam-Status: No, score=-2.034 tagged_above=-999 required=5 tests=[AWL=0.566,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d9n0pFdE59um for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 22:33:56 -0800 (PST)
Received: from omr13.networksolutionsemail.com (omr13.networksolutionsemail.com [205.178.146.63]) by ietfa.amsl.com (Postfix) with ESMTP id 7CFE511E8095 for <homenet@ietf.org>; Tue, 15 Nov 2011 22:33:56 -0800 (PST)
Received: from cm-omr9 (mail.networksolutionsemail.com [205.178.146.50]) by omr13.networksolutionsemail.com (8.13.8/8.13.8) with ESMTP id pAG6XrH9017955 for <homenet@ietf.org>; Wed, 16 Nov 2011 01:33:56 -0500
X-Authenticated-IP: 98.151.18.158
Received: from [98.151.18.158] ([98.151.18.158:64022] helo=[192.168.1.105]) by cm-omr9 (envelope-from <rturner@amalfisystems.com>) (ecelerity 2.2.2.41 r(31179/31189)) with ESMTP id F8/4D-04778-15953CE4; Wed, 16 Nov 2011 01:33:53 -0500
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
From: Randy Turner <rturner@amalfisystems.com>
In-Reply-To: <21608A99-B37A-4406-A59A-479C87A2ABDF@fugue.com>
Date: Tue, 15 Nov 2011 22:33:53 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <EF125DE9-3C87-46A6-B1C0-C0D59C3CF580@amalfisystems.com>
References: <4EC1D206.2070303@gmail.com> <3C716203-8579-41EA-98CE-6DC3BE9261D8@fugue.com> <FC520CA0-BAA4-4309-A878-CB40308F2562@cisco.com> <09215FB7-EA7A-4D9D-8772-737B79CBBD20@fugue.com> <4EC32B76.8080706@riw.us> <7DADF53B-56CA-47CC-BBDA-34300EE4D22D@fugue.com> <7D0889B6-7769-4F74-996D-08CDA02B3670@cisco.com> <21608A99-B37A-4406-A59A-479C87A2ABDF@fugue.com>
To: homenet@ietf.org
X-Mailer: Apple Mail (2.1084)
Subject: Re: [homenet] draft-baker-homenet-prefix-assignment
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 16 Nov 2011 06:34:00 -0000

If you want to configure more than just layer-3 connectivity, seems like =
you would need *something* ...

Randy


On Nov 15, 2011, at 10:31 PM, Ted Lemon wrote:

> On Nov 16, 2011, at 1:52 PM, Ole Troan <ot@cisco.com> wrote:
>> do we need to?
>> in a self organizing unmanaged home; if we were to do a combination =
of a network wide flooding mechanism and RAs. would we need DHCP in the =
network at all?
>=20
> I am not claiming that we do. However, the problem exists whether we =
do DHCP in homenet or not.=20
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>=20


From rturner@amalfisystems.com  Tue Nov 15 22:35:53 2011
Return-Path: <rturner@amalfisystems.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CFBF11E80C6 for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 22:35:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.175
X-Spam-Level: 
X-Spam-Status: No, score=-2.175 tagged_above=-999 required=5 tests=[AWL=0.424,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tbT4np+svmAW for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 22:35:49 -0800 (PST)
Received: from omr5.networksolutionsemail.com (omr5.networksolutionsemail.com [205.178.146.55]) by ietfa.amsl.com (Postfix) with ESMTP id 0881211E8123 for <homenet@ietf.org>; Tue, 15 Nov 2011 22:35:48 -0800 (PST)
Received: from cm-omr9 (mail.networksolutionsemail.com [205.178.146.50]) by omr5.networksolutionsemail.com (8.13.6/8.13.6) with ESMTP id pAG6ZjE5002747 for <homenet@ietf.org>; Wed, 16 Nov 2011 01:35:47 -0500
X-Authenticated-IP: 98.151.18.158
Received: from [98.151.18.158] ([98.151.18.158:64079] helo=[192.168.1.105]) by cm-omr9 (envelope-from <rturner@amalfisystems.com>) (ecelerity 2.2.2.41 r(31179/31189)) with ESMTP id 36/BD-04778-1C953CE4; Wed, 16 Nov 2011 01:35:45 -0500
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
From: Randy Turner <rturner@amalfisystems.com>
In-Reply-To: <B4581271-026C-4BE4-B369-44E5E194F2D3@fugue.com>
Date: Tue, 15 Nov 2011 22:35:44 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <47553E6E-2CEB-492D-9670-92017132C295@amalfisystems.com>
References: <4EC1C386.6010802@gmail.com> <4EC1C566.2060400@cisco.com> <4EC1CC2E.30209@gmail.com> <4EC1D6C9.3030107@cisco.com> <CAKD1Yr3rFJonkJ1CbCgGPpr-WDj1RFmR6q4jDab1Toc0tJJodg@mail.gmail.com> <4EC1FF9A.4080308@bogus.com> <4EC2028E.6050305@gmail.com> <4EC20405.8040505@bogus.com> <4EC2FB44.2020807@gmail.com> <D99F1C65-2B6D-407A-88F3-EEAADB7E9B07@fugue.com> <4EC30317.8080503@gmail.com> <D0811E6D-3AFC-42C3-B590-973BB1C7D141@fugue.com> <4EC30B20.4090507@gmail.com> <C861D22D-4EE1-4E01-8AD2-5CB6345CF14C@fugue.com> <A08E48D6-1867-4AC1-AB6F-B079BBD5C4EB@twcable.com> <4EC34AB2.1040609@cisco.com> <B4581271-026C-4BE4-B369-44E5E194F2D3@fugue.com>
To: homenet@ietf.org
X-Mailer: Apple Mail (2.1084)
Subject: Re: [homenet] pervasive v4
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 16 Nov 2011 06:35:53 -0000

Good points...Speaking of Bonjour, I haven't seen many references to =
support for multicast (yet)...I'm assuming this is on the plate.

Randy

On Nov 15, 2011, at 10:29 PM, Ted Lemon wrote:

> On Nov 16, 2011, at 1:31 PM, Erik Nordmark <nordmark@cisco.com> wrote:
>> The service call will be something like "the internet is working =
fine, but the printer is broken" when the laptop uses dual-stack but the =
printer is IPv4 only.
>>=20
>> I uniformity (within the home) is better if we care about complexity.
>=20
> This is certainly a valid point, but you've got it backwards, since =
we're talking about bridging IPv4.  The real risk is that a bonjour =
printer will work only if you are plugged into the same router it is.=20
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>=20


From Ray.Bellis@nominet.org.uk  Tue Nov 15 22:39:46 2011
Return-Path: <Ray.Bellis@nominet.org.uk>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ADCDF11E815A for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 22:39:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.437
X-Spam-Level: 
X-Spam-Status: No, score=-7.437 tagged_above=-999 required=5 tests=[AWL=-0.838, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4C5uoZR9xElF for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 22:39:42 -0800 (PST)
Received: from mx1.knowthenet.org.uk (mx1.knowthenet.org.uk [213.248.199.2]) by ietfa.amsl.com (Postfix) with ESMTP id 3BA8B11E8196 for <homenet@ietf.org>; Tue, 15 Nov 2011 22:39:40 -0800 (PST)
DomainKey-Signature: s=main.dk.nominet.selector; d=nominet.org.uk; c=nofws; q=dns;  h=X-IronPort-AV: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:Content-Type: Content-ID:Content-Transfer-Encoding:MIME-Version; b=SMwgtOZ1yduJ5P/Piu6UBM+3j1M7ZInUh3TskVaDYPmKSGIMtx/EhROk WulV0IWrnpBcu3rSCX0oGjGK1tLbElTPOmNXX3413bT0loqs59ROL1JRb e9Kmk3rb0Dp+0S7;
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nominet.org.uk; i=Ray.Bellis@nominet.org.uk; q=dns/txt; s=main.dkim.nominet.selector; t=1321425581; x=1352961581; h=from:sender:reply-to:subject:date:message-id:to:cc: mime-version:content-transfer-encoding:content-id: content-description:resent-date:resent-from:resent-sender: resent-to:resent-cc:resent-message-id:in-reply-to: references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:list-owner:list-archive; z=From:=20Ray=20Bellis=20<Ray.Bellis@nominet.org.uk> |Subject:=20Re:=20[homenet]=20pervasive=20v4|Date:=20Wed, =2016=20Nov=202011=2006:39:38=20+0000|Message-ID:=20<00BE 6145-7745-458A-8FFC-3DE8E26E8948@nominet.org.uk>|To:=20Ra ndy=20Turner=20<rturner@amalfisystems.com>|CC:=20"<homene t@ietf.org>"=20<homenet@ietf.org>|MIME-Version:=201.0 |Content-Transfer-Encoding:=20quoted-printable |Content-ID:=20<1da03b4d-c90c-47a8-a12e-f59ec422a5af> |In-Reply-To:=20<47553E6E-2CEB-492D-9670-92017132C295@ama lfisystems.com>|References:=20<4EC1C386.6010802@gmail.com >=20<4EC1C566.2060400@cisco.com>=0D=0A=20<4EC1CC2E.30209@ gmail.com>=20<4EC1D6C9.3030107@cisco.com>=0D=0A=20<CAKD1Y r3rFJonkJ1CbCgGPpr-WDj1RFmR6q4jDab1Toc0tJJodg@mail.gmail. com>=0D=0A=20<4EC1FF9A.4080308@bogus.com>=20<4EC2028E.605 0305@gmail.com>=0D=0A=20<4EC20405.8040505@bogus.com>=20<4 EC2FB44.2020807@gmail.com>=0D=0A=20<D99F1C65-2B6D-407A-88 F3-EEAADB7E9B07@fugue.com>=0D=0A=20<4EC30317.8080503@gmai l.com>=0D=0A=20<D0811E6D-3AFC-42C3-B590-973BB1C7D141@fugu e.com>=0D=0A=20<4EC30B20.4090507@gmail.com>=0D=0A=20<C861 D22D-4EE1-4E01-8AD2-5CB6345CF14C@fugue.com>=0D=0A=20<A08E 48D6-1867-4AC1-AB6F-B079BBD5C4EB@twcable.com>=0D=0A=20<4E C34AB2.1040609@cisco.com>=0D=0A=20<B4581271-026C-4BE4-B36 9-44E5E194F2D3@fugue.com>=0D=0A=20<47553E6E-2CEB-492D-967 0-92017132C295@amalfisystems.com>; bh=Pz29TawE0At5VkQeiXLsQ3iSJTzAckQUAjrwhHuElnQ=; b=rAkK/izucY575YTw3yZfyHwXvrtiWuzSX+lCIy+K4YMN2dXkn9otNl/4 MMhf2lO/yufTjYtRw8Dh6I2s05amVGnNXonP69eeJzA5Yo9WEXBh2JBA/ jtGBkAFk18bz16a;
X-IronPort-AV: E=Sophos;i="4.69,519,1315177200"; d="scan'208";a="36632015"
Received: from wds-exc2.okna.nominet.org.uk ([213.248.197.145]) by mx3.nominet.org.uk with ESMTP; 16 Nov 2011 06:39:38 +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%19]) with mapi; Wed, 16 Nov 2011 06:39:37 +0000
From: Ray Bellis <Ray.Bellis@nominet.org.uk>
To: Randy Turner <rturner@amalfisystems.com>
Thread-Topic: [homenet] pervasive v4
Thread-Index: AQHMozfdTx4hGPHgHEiHCTAbj+9ML5WtK3gAgAAIFgCAAAykgIAALfKAgAACtwCAAAOFAIAAAb+AgAEmvQCAAATbAIAABHmAgAAIIoCAAAFyAIAAAiAAgAAQRwCAADlhAIAAECQAgAABzwCAAAEXAA==
Date: Wed, 16 Nov 2011 06:39:38 +0000
Message-ID: <00BE6145-7745-458A-8FFC-3DE8E26E8948@nominet.org.uk>
References: <4EC1C386.6010802@gmail.com> <4EC1C566.2060400@cisco.com> <4EC1CC2E.30209@gmail.com> <4EC1D6C9.3030107@cisco.com> <CAKD1Yr3rFJonkJ1CbCgGPpr-WDj1RFmR6q4jDab1Toc0tJJodg@mail.gmail.com> <4EC1FF9A.4080308@bogus.com> <4EC2028E.6050305@gmail.com> <4EC20405.8040505@bogus.com> <4EC2FB44.2020807@gmail.com> <D99F1C65-2B6D-407A-88F3-EEAADB7E9B07@fugue.com> <4EC30317.8080503@gmail.com> <D0811E6D-3AFC-42C3-B590-973BB1C7D141@fugue.com> <4EC30B20.4090507@gmail.com> <C861D22D-4EE1-4E01-8AD2-5CB6345CF14C@fugue.com> <A08E48D6-1867-4AC1-AB6F-B079BBD5C4EB@twcable.com> <4EC34AB2.1040609@cisco.com> <B4581271-026C-4BE4-B369-44E5E194F2D3@fugue.com> <47553E6E-2CEB-492D-9670-92017132C295@amalfisystems.com>
In-Reply-To: <47553E6E-2CEB-492D-9670-92017132C295@amalfisystems.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1da03b4d-c90c-47a8-a12e-f59ec422a5af>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<homenet@ietf.org>" <homenet@ietf.org>
Subject: Re: [homenet] pervasive v4
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 16 Nov 2011 06:39:46 -0000

On 16 Nov 2011, at 14:35, Randy Turner wrote:

>=20
> Good points...Speaking of Bonjour, I haven't seen many references to supp=
ort for multicast (yet)...I'm assuming this is on the plate.

Yes, it was one of the topics of discussion at the interim, mostly in the c=
ontext of naming and service discovery.  There hasn't really been any discu=
ssion on the use of multicast as a high bandwidth streaming system.

Ray


From fred@cisco.com  Tue Nov 15 22:43:10 2011
Return-Path: <fred@cisco.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90AAE21F9311 for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 22:43:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.644
X-Spam-Level: 
X-Spam-Status: No, score=-105.644 tagged_above=-999 required=5 tests=[AWL=0.955, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VGM6H8QIY9LN for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 22:43:05 -0800 (PST)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id 7F7D31F0C44 for <homenet@ietf.org>; Tue, 15 Nov 2011 22:43:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=730; q=dns/txt; s=iport; t=1321425785; x=1322635385; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to:content-transfer-encoding; bh=2aP/vA2Iblm8XSzZBBaQjQbiBoHhzt4Id5lic4N1jd0=; b=Dm7MT2TciK/ROss/LAMNNm/s37ZxijihwErb3K+wgsdNHfhAeL2n6iTR 7jzuE3PpXZ4LqezUBWxY6CX6PZfNIysWjgc4ZTc8b9rBWzt0b+vWNTdJf vJKZKj6l4hftLFwNqexF1nZDwm2b9NGcHTdKf4K/KUKqoWIzBZAd8Pwvj Y=;
X-IronPort-AV: E=Sophos;i="4.69,519,1315180800"; d="scan'208";a="12790896"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-1.cisco.com with ESMTP; 16 Nov 2011 06:43:05 +0000
Received: from dhcp-57cd.meeting.ietf.org (sjc-vpn6-1383.cisco.com [10.21.125.103]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id pAG6gEut031344; Wed, 16 Nov 2011 06:43:04 GMT
Received: from [127.0.0.1] by dhcp-57cd.meeting.ietf.org (PGP Universal service); Wed, 16 Nov 2011 14:43:04 +0800
X-PGP-Universal: processed; by dhcp-57cd.meeting.ietf.org on Wed, 16 Nov 2011 14:43:04 +0800
Mime-Version: 1.0 (Apple Message framework v1084)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <7D0889B6-7769-4F74-996D-08CDA02B3670@cisco.com>
Date: Wed, 16 Nov 2011 14:42:04 +0800
Message-Id: <84FD521E-D48C-41C9-935B-9B4695FB658D@cisco.com>
References: <4EC1D206.2070303@gmail.com> <3C716203-8579-41EA-98CE-6DC3BE9261D8@fugue.com> <FC520CA0-BAA4-4309-A878-CB40308F2562@cisco.com> <09215FB7-EA7A-4D9D-8772-737B79CBBD20@fugue.com> <4EC32B76.8080706@riw.us> <7DADF53B-56CA-47CC-BBDA-34300EE4D22D@fugue.com> <7D0889B6-7769-4F74-996D-08CDA02B3670@cisco.com>
To: Ole Troan <ot@cisco.com>
X-Mailer: Apple Mail (2.1084)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: Russ White <russw@riw.us>, "homenet@ietf.org" <homenet@ietf.org>, Ted Lemon <mellon@fugue.com>
Subject: Re: [homenet] draft-baker-homenet-prefix-assignment
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 16 Nov 2011 06:43:10 -0000

On Nov 16, 2011, at 1:52 PM, Ole Troan wrote:

>>> We need to be aware that not every network may be able to reach the
>>> Internet... So you might need to have an address from every =
available
>>> DHCP server, not just the "best," one, or even a "random," one.
>>=20
>> Yes, this is part of a problem space of which I have become keenly =
aware over the course of this IETF meeting.   Expect a draft shortly.   =
:)
>=20
> do we need to?

Need to what? Provide a subnet number on each subnet?

Is that a real question?

> in a self organizing unmanaged home; if we were to do a combination of =
a network wide flooding mechanism and RAs. would we need DHCP in the =
network at all?
>=20
> cheers,
> Ole


From ot@cisco.com  Tue Nov 15 22:46:35 2011
Return-Path: <ot@cisco.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F9CB21F9325 for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 22:46:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bne1eYvWGOer for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 22:46:31 -0800 (PST)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id 0CEA921F9324 for <homenet@ietf.org>; Tue, 15 Nov 2011 22:46:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ot@cisco.com; l=806; q=dns/txt; s=iport; t=1321425991; x=1322635591; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=oItPc68k8BiVz3r6yCPT5OBASvI+UEdE5vDtuWPoef8=; b=NAwTsz/O6+dyChwrac2mBQo+fn3n+QA+BrSXQGe0jJU70kBLfy9nlVNK Hi+OIZjRKeP0eLhNynSkRzPODzpchSqchefKr+7dZe/0mQDaNVu7oL6Wn b2wTOTY1hsgtPbA0XGdUt3q6YJrzG5j6CLd2KGV8CTH1L+ZvyOSqgmOhg g=;
X-IronPort-AV: E=Sophos;i="4.69,519,1315180800"; d="scan'208";a="14490428"
Received: from mtv-core-1.cisco.com ([171.68.58.6]) by mtv-iport-2.cisco.com with ESMTP; 16 Nov 2011 06:46:31 +0000
Received: from sjc-vpn6-1305.cisco.com (sjc-vpn6-1305.cisco.com [10.21.125.25]) by mtv-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id pAG6kT0N032618; Wed, 16 Nov 2011 06:46:30 GMT
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Ole Troan <ot@cisco.com>
In-Reply-To: <84FD521E-D48C-41C9-935B-9B4695FB658D@cisco.com>
Date: Wed, 16 Nov 2011 14:46:29 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <489BE869-79F9-40FC-96B1-6A190620B4CA@cisco.com>
References: <4EC1D206.2070303@gmail.com> <3C716203-8579-41EA-98CE-6DC3BE9261D8@fugue.com> <FC520CA0-BAA4-4309-A878-CB40308F2562@cisco.com> <09215FB7-EA7A-4D9D-8772-737B79CBBD20@fugue.com> <4EC32B76.8080706@riw.us> <7DADF53B-56CA-47CC-BBDA-34300EE4D22D@fugue.com> <7D0889B6-7769-4F74-996D-08CDA02B3670@cisco.com> <84FD521E-D48C-41C9-935B-9B4695FB658D@cisco.com>
To: Fred Baker <fred@cisco.com>
X-Mailer: Apple Mail (2.1084)
Cc: Russ White <russw@riw.us>, "homenet@ietf.org" <homenet@ietf.org>, Ted Lemon <mellon@fugue.com>
Subject: Re: [homenet] draft-baker-homenet-prefix-assignment
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 16 Nov 2011 06:46:35 -0000

Fred,

>>>> We need to be aware that not every network may be able to reach the
>>>> Internet... So you might need to have an address from every =
available
>>>> DHCP server, not just the "best," one, or even a "random," one.
>>>=20
>>> Yes, this is part of a problem space of which I have become keenly =
aware over the course of this IETF meeting.   Expect a draft shortly.   =
:)
>>=20
>> do we need to?
>=20
> Need to what? Provide a subnet number on each subnet?
>=20
> Is that a real question?

extend the DHCP protocol to handle multiple sources of information.


cheers,
Ole

>> in a self organizing unmanaged home; if we were to do a combination =
of a network wide flooding mechanism and RAs. would we need DHCP in the =
network at all?
>>=20
>> cheers,
>> Ole
>=20


From mellon@fugue.com  Tue Nov 15 22:56:13 2011
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F31DF11E81A9 for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 22:56:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.227
X-Spam-Level: 
X-Spam-Status: No, score=-1.227 tagged_above=-999 required=5 tests=[AWL=-0.024, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zxgaacO4leQa for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 22:56:12 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 9A0A311E81A1 for <homenet@ietf.org>; Tue, 15 Nov 2011 22:56:12 -0800 (PST)
Received: from [172.22.13.155] (unknown [122.147.240.7]) by toccata.fugue.com (Postfix) with ESMTPSA id AD2C42381E38; Wed, 16 Nov 2011 01:56:11 -0500 (EST)
References: <4EC1D206.2070303@gmail.com> <3C716203-8579-41EA-98CE-6DC3BE9261D8@fugue.com> <FC520CA0-BAA4-4309-A878-CB40308F2562@cisco.com> <09215FB7-EA7A-4D9D-8772-737B79CBBD20@fugue.com> <4EC32B76.8080706@riw.us> <7DADF53B-56CA-47CC-BBDA-34300EE4D22D@fugue.com> <7D0889B6-7769-4F74-996D-08CDA02B3670@cisco.com> <84FD521E-D48C-41C9-935B-9B4695FB658D@cisco.com> <489BE869-79F9-40FC-96B1-6A190620B4CA@cisco.com>
In-Reply-To: <489BE869-79F9-40FC-96B1-6A190620B4CA@cisco.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <7F630AC9-A369-48B8-BD8F-684C0AC1DDDA@fugue.com>
X-Mailer: iPad Mail (9A334)
From: Ted Lemon <mellon@fugue.com>
Date: Wed, 16 Nov 2011 14:56:44 +0800
To: Ole Troan <ot@cisco.com>
Cc: Russ White <russw@riw.us>, "homenet@ietf.org" <homenet@ietf.org>, Fred Baker <fred@cisco.com>
Subject: Re: [homenet] draft-baker-homenet-prefix-assignment
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 16 Nov 2011 06:56:13 -0000

On Nov 16, 2011, at 2:46 PM, Ole Troan <ot@cisco.com> wrote:
> extend the DHCP protocol to handle multiple sources of information.

I think this winds up being implicit in MIF's charter, although I didn't rea=
lize that until quite recently.=

From rturner@amalfisystems.com  Tue Nov 15 23:06:24 2011
Return-Path: <rturner@amalfisystems.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20EC811E81B7 for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 23:06:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r0SV4mXjirCE for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 23:06:20 -0800 (PST)
Received: from omr15.networksolutionsemail.com (omr15.networksolutionsemail.com [205.178.146.65]) by ietfa.amsl.com (Postfix) with ESMTP id 158AC11E81C6 for <homenet@ietf.org>; Tue, 15 Nov 2011 23:06:19 -0800 (PST)
Received: from cm-omr4 (mail.networksolutionsemail.com [205.178.146.50]) by omr15.networksolutionsemail.com (8.13.8/8.13.8) with ESMTP id pAG76Inx021002 for <homenet@ietf.org>; Wed, 16 Nov 2011 02:06:18 -0500
Authentication-Results: cm-omr4 smtp.user=rturner@amalfisystems.com; auth=pass (LOGIN)
X-Authenticated-UID: rturner@amalfisystems.com
Received: from [198.228.214.196] ([198.228.214.196:60337] helo=localhost) by cm-omr4 (envelope-from <rturner@amalfisystems.com>) (ecelerity 2.2.2.41 r(31179/31189)) with ESMTPA id 9B/05-04877-9E063CE4; Wed, 16 Nov 2011 02:06:18 -0500
Date: Tue, 15 Nov 2011 23:06:12 -0800
Message-ID: <3s4wrwouwuj3hgreefjvoojj.1321427172482@email.android.com>
Importance: normal
From: Randy Turner <rturner@amalfisystems.com>
To: ray.bellis@nominet.org.uk
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="--_com.android.email_158195812595814"
Cc: homenet@ietf.org
Subject: Re: [homenet] pervasive v4
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 16 Nov 2011 07:06:24 -0000

----_com.android.email_158195812595814
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64

V2FzIHRoZSBpbnRlbnQgb2YgbmFtaW5nIGFuZCBkaXNjb3ZlcnkgdG8gdHJ5IGFuZCByZXVzZSB0
aGUgemVyb2NvbmYvbWRucyBzdHVmZiBvciBzb21ldGhpbmcgbmV3PwoKVGhhbmtzIQpSYW5keQoK
LS0tLS0tLS0gT3JpZ2luYWwgbWVzc2FnZSAtLS0tLS0tLQpTdWJqZWN0OiBSZTogW2hvbWVuZXRd
IHBlcnZhc2l2ZSB2NCAKRnJvbTogUmF5IEJlbGxpcyA8UmF5LkJlbGxpc0Bub21pbmV0Lm9yZy51
az4gClRvOiBSYW5keSBUdXJuZXIgPHJ0dXJuZXJAYW1hbGZpc3lzdGVtcy5jb20+IApDQzogIjxo
b21lbmV0QGlldGYub3JnPiIgPGhvbWVuZXRAaWV0Zi5vcmc+IAoKCk9uIDE2IE5vdiAyMDExLCBh
dCAxNDozNSwgUmFuZHkgVHVybmVyIHdyb3RlOgoKPiAKPiBHb29kIHBvaW50cy4uLlNwZWFraW5n
IG9mIEJvbmpvdXIsIEkgaGF2ZW4ndCBzZWVuIG1hbnkgcmVmZXJlbmNlcyB0byBzdXBwb3J0IGZv
ciBtdWx0aWNhc3QgKHlldCkuLi5JJ20gYXNzdW1pbmcgdGhpcyBpcyBvbiB0aGUgcGxhdGUuCgpZ
ZXMsIGl0IHdhcyBvbmUgb2YgdGhlIHRvcGljcyBvZiBkaXNjdXNzaW9uIGF0IHRoZSBpbnRlcmlt
LCBtb3N0bHkgaW4gdGhlIGNvbnRleHQgb2YgbmFtaW5nIGFuZCBzZXJ2aWNlIGRpc2NvdmVyeS7C
oCBUaGVyZSBoYXNuJ3QgcmVhbGx5IGJlZW4gYW55IGRpc2N1c3Npb24gb24gdGhlIHVzZSBvZiBt
dWx0aWNhc3QgYXMgYSBoaWdoIGJhbmR3aWR0aCBzdHJlYW1pbmcgc3lzdGVtLgoKUmF5CgpfX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpob21lbmV0IG1haWxp
bmcgbGlzdApob21lbmV0QGlldGYub3JnCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlz
dGluZm8vaG9tZW5ldAoK

----_com.android.email_158195812595814
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: base64

PGh0bWw+PGhlYWQ+PG1ldGEgaHR0cC1lcXVpdj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0
L2h0bWw7IGNoYXJzZXQ9VVRGLTgiPjwvaGVhZD48Ym9keT5XYXMgdGhlIGludGVudCBvZiBuYW1p
bmcgYW5kIGRpc2NvdmVyeSB0byB0cnkgYW5kIHJldXNlIHRoZSB6ZXJvY29uZi9tZG5zIHN0dWZm
IG9yIHNvbWV0aGluZyBuZXc/PGRpdj48YnI+PC9kaXY+PGRpdj5UaGFua3MhPC9kaXY+PGRpdj5S
YW5keTwvZGl2Pjxicj48YnI+PGJyPi0tLS0tLS0tIE9yaWdpbmFsIG1lc3NhZ2UgLS0tLS0tLS08
YnI+U3ViamVjdDogUmU6IFtob21lbmV0XSBwZXJ2YXNpdmUgdjQgPGJyPkZyb206IFJheSBCZWxs
aXMgJmx0O1JheS5CZWxsaXNAbm9taW5ldC5vcmcudWsmZ3Q7IDxicj5UbzogUmFuZHkgVHVybmVy
ICZsdDtydHVybmVyQGFtYWxmaXN5c3RlbXMuY29tJmd0OyA8YnI+Q0M6ICImbHQ7aG9tZW5ldEBp
ZXRmLm9yZyZndDsiICZsdDtob21lbmV0QGlldGYub3JnJmd0OyA8YnI+PGJyPjxicj48ZGl2IHN0
eWxlPSJ3b3JkLWJyZWFrOmJyZWFrLWFsbDsiPjxicj5PbiAxNiBOb3YgMjAxMSwgYXQgMTQ6MzUs
IFJhbmR5IFR1cm5lciB3cm90ZTo8YnI+PGJyPiZndDsgPGJyPiZndDsgR29vZCBwb2ludHMuLi5T
cGVha2luZyBvZiBCb25qb3VyLCBJIGhhdmVuJ3Qgc2VlbiBtYW55IHJlZmVyZW5jZXMgdG8gc3Vw
cG9ydCBmb3IgbXVsdGljYXN0ICh5ZXQpLi4uSSdtIGFzc3VtaW5nIHRoaXMgaXMgb24gdGhlIHBs
YXRlLjxicj48YnI+WWVzLCBpdCB3YXMgb25lIG9mIHRoZSB0b3BpY3Mgb2YgZGlzY3Vzc2lvbiBh
dCB0aGUgaW50ZXJpbSwgbW9zdGx5IGluIHRoZSBjb250ZXh0IG9mIG5hbWluZyBhbmQgc2Vydmlj
ZSBkaXNjb3ZlcnkuJm5ic3A7IFRoZXJlIGhhc24ndCByZWFsbHkgYmVlbiBhbnkgZGlzY3Vzc2lv
biBvbiB0aGUgdXNlIG9mIG11bHRpY2FzdCBhcyBhIGhpZ2ggYmFuZHdpZHRoIHN0cmVhbWluZyBz
eXN0ZW0uPGJyPjxicj5SYXk8YnI+PGJyPl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fPGJyPmhvbWVuZXQgbWFpbGluZyBsaXN0PGJyPmhvbWVuZXRAaWV0Zi5v
cmc8YnI+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9ob21lbmV0PGJyPjxi
cj48L2Rpdj48L2JvZHk+

----_com.android.email_158195812595814--



From fred@cisco.com  Tue Nov 15 23:41:48 2011
Return-Path: <fred@cisco.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CED71F0C78 for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 23:41:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.608
X-Spam-Level: 
X-Spam-Status: No, score=-107.608 tagged_above=-999 required=5 tests=[AWL=-1.009, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LVyNsHQa18Uo for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 23:41:44 -0800 (PST)
Received: from ams-iport-3.cisco.com (ams-iport-3.cisco.com [144.254.224.146]) by ietfa.amsl.com (Postfix) with ESMTP id D1DC11F0C89 for <homenet@ietf.org>; Tue, 15 Nov 2011 23:41:43 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=995; q=dns/txt; s=iport; t=1321429304; x=1322638904; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to:content-transfer-encoding; bh=n5bPPF7Stb9LANVg0Zf7UujqRwZtxAI8MGACseX1NEs=; b=jyI5omdm7zgHAkLXtDSKFylA7H8DJ/obX6Ryfs3eOXYaq+ysQhsEb8Zg z+SUWZrSaDLFMJHSFYhj2aaXMtmmQSIzgn9G8GQZWPxwfuum4XnQnsgAy rFDMnNt9wMn2Osmxaj72Gyho+p7IiLY0sbKux7BynC9mFo0aXAaLIL2kl Y=;
X-IronPort-AV: E=Sophos;i="4.69,519,1315180800";  d="scan'208";a="3187354"
Received: from bgl-core-4.cisco.com ([72.163.197.19]) by ams-iport-3.cisco.com with ESMTP; 16 Nov 2011 07:41:41 +0000
Received: from dhcp-4466.meeting.ietf.org (hkidc-vpn-client-233-65.cisco.com [10.75.233.65]) by bgl-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id pAG7faWR026524; Wed, 16 Nov 2011 07:41:37 GMT
Received: from [127.0.0.1] by dhcp-4466.meeting.ietf.org (PGP Universal service); Wed, 16 Nov 2011 15:41:37 +0800
X-PGP-Universal: processed; by dhcp-4466.meeting.ietf.org on Wed, 16 Nov 2011 15:41:37 +0800
Mime-Version: 1.0 (Apple Message framework v1084)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <7F630AC9-A369-48B8-BD8F-684C0AC1DDDA@fugue.com>
Date: Wed, 16 Nov 2011 15:41:27 +0800
Message-Id: <72EB15CA-CAB4-4A50-BAB4-E60176109AF5@cisco.com>
References: <4EC1D206.2070303@gmail.com> <3C716203-8579-41EA-98CE-6DC3BE9261D8@fugue.com> <FC520CA0-BAA4-4309-A878-CB40308F2562@cisco.com> <09215FB7-EA7A-4D9D-8772-737B79CBBD20@fugue.com> <4EC32B76.8080706@riw.us> <7DADF53B-56CA-47CC-BBDA-34300EE4D22D@fugue.com> <7D0889B6-7769-4F74-996D-08CDA02B3670@cisco.com> <84FD521E-D48C-41C9-935B-9B4695FB658D@cisco.com> <489BE869-79F9-40FC-96B1-6A190620B4CA@cisco.com> <7F630AC9-A369-48B8-BD8F-684C0AC1DDDA@fugue.com>
To: Ted Lemon <mellon@fugue.com>
X-Mailer: Apple Mail (2.1084)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: Russ White <russw@riw.us>, Ole Troan <ot@cisco.com>, "homenet@ietf.org" <homenet@ietf.org>
Subject: Re: [homenet] draft-baker-homenet-prefix-assignment
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 16 Nov 2011 07:41:48 -0000

I don't much care whose charter it's in. I do think that if we have an =
idea that an ISP will allocate an IA_PD to a directly attached router =
and that router will then, in some way, sub-allocate subnet prefixes to =
subnets in the home, then there is a case in which there are multiple =
ISPs that have separate routers doing that. Ralph and I have suggested =
using the same mechanism that ISPs use to allocate prefixes to the home =
to allocate prefixes within the home, which means having multiple DHCP =
servers. If we do it another way, whether ZOSPF's or some other way, we =
have the same problem in the sense that there will be multiple sources =
of subnet prefixes.

On Nov 16, 2011, at 2:56 PM, Ted Lemon wrote:

> On Nov 16, 2011, at 2:46 PM, Ole Troan <ot@cisco.com> wrote:
>> extend the DHCP protocol to handle multiple sources of information.
>=20
> I think this winds up being implicit in MIF's charter, although I =
didn't realize that until quite recently.


From joelja@bogus.com  Tue Nov 15 23:56:33 2011
Return-Path: <joelja@bogus.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 058DF11E816D for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 23:56:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.499
X-Spam-Level: 
X-Spam-Status: No, score=-102.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EitBigxLUIEV for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 23:56:32 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id E820311E81AC for <homenet@ietf.org>; Tue, 15 Nov 2011 23:56:31 -0800 (PST)
Received: from dhcp-2510.meeting.ietf.org (dhcp-2510.meeting.ietf.org [130.129.37.16]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id pAG7uFqg021977 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Wed, 16 Nov 2011 07:56:17 GMT (envelope-from joelja@bogus.com)
Message-ID: <4EC36C9F.6000504@bogus.com>
Date: Wed, 16 Nov 2011 15:56:15 +0800
From: Joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Fred Baker <fred@cisco.com>
References: <4EC1D206.2070303@gmail.com> <3C716203-8579-41EA-98CE-6DC3BE9261D8@fugue.com> <FC520CA0-BAA4-4309-A878-CB40308F2562@cisco.com> <09215FB7-EA7A-4D9D-8772-737B79CBBD20@fugue.com> <4EC32B76.8080706@riw.us> <7DADF53B-56CA-47CC-BBDA-34300EE4D22D@fugue.com> <7D0889B6-7769-4F74-996D-08CDA02B3670@cisco.com> <84FD521E-D48C-41C9-935B-9B4695FB658D@cisco.com> <489BE869-79F9-40FC-96B1-6A190620B4CA@cisco.com> <7F630AC9-A369-48B8-BD8F-684C0AC1DDDA@fugue.com> <72EB15CA-CAB4-4A50-BAB4-E60176109AF5@cisco.com>
In-Reply-To: <72EB15CA-CAB4-4A50-BAB4-E60176109AF5@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Wed, 16 Nov 2011 07:56:18 +0000 (UTC)
Cc: Russ White <russw@riw.us>, Ole Troan <ot@cisco.com>, "homenet@ietf.org" <homenet@ietf.org>, Ted Lemon <mellon@fugue.com>
Subject: Re: [homenet] draft-baker-homenet-prefix-assignment
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 16 Nov 2011 07:56:33 -0000

On 11/16/11 15:41 , Fred Baker wrote:
> I don't much care whose charter it's in. I do think that if we have
> an idea that an ISP will allocate an IA_PD to a directly attached
> router and that router will then, in some way, sub-allocate subnet
> prefixes to subnets in the home, then there is a case in which there
> are multiple ISPs that have separate routers doing that. Ralph and I
> have suggested using the same mechanism that ISPs use to allocate
> prefixes to the home to allocate prefixes within the home, which
> means having multiple DHCP servers. 

which seems like a slightly more eleborate variation of having multiple
available routers or nexthops due to having multiple RAs.

If we do it another way, whether
> ZOSPF's or some other way, we have the same problem in the sense that
> there will be multiple sources of subnet prefixes.
> 
> On Nov 16, 2011, at 2:56 PM, Ted Lemon wrote:
> 
>> On Nov 16, 2011, at 2:46 PM, Ole Troan <ot@cisco.com> wrote:
>>> extend the DHCP protocol to handle multiple sources of
>>> information.
>> 
>> I think this winds up being implicit in MIF's charter, although I
>> didn't realize that until quite recently.
> 
> _______________________________________________ homenet mailing list 
> homenet@ietf.org https://www.ietf.org/mailman/listinfo/homenet
> 


From mellon@fugue.com  Tue Nov 15 23:58:10 2011
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C41B411E8138 for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 23:58:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.226
X-Spam-Level: 
X-Spam-Status: No, score=-1.226 tagged_above=-999 required=5 tests=[AWL=-0.023, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 14K+zg1mWWXd for <homenet@ietfa.amsl.com>; Tue, 15 Nov 2011 23:58:10 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 0C9C011E80AD for <homenet@ietf.org>; Tue, 15 Nov 2011 23:58:10 -0800 (PST)
Received: from [172.22.13.155] (unknown [122.147.240.7]) by toccata.fugue.com (Postfix) with ESMTPSA id B2E8A2381DF0; Wed, 16 Nov 2011 02:58:08 -0500 (EST)
References: <4EC1D206.2070303@gmail.com> <3C716203-8579-41EA-98CE-6DC3BE9261D8@fugue.com> <FC520CA0-BAA4-4309-A878-CB40308F2562@cisco.com> <09215FB7-EA7A-4D9D-8772-737B79CBBD20@fugue.com> <4EC32B76.8080706@riw.us> <7DADF53B-56CA-47CC-BBDA-34300EE4D22D@fugue.com> <7D0889B6-7769-4F74-996D-08CDA02B3670@cisco.com> <84FD521E-D48C-41C9-935B-9B4695FB658D@cisco.com> <489BE869-79F9-40FC-96B1-6A190620B4CA@cisco.com> <7F630AC9-A369-48B8-BD8F-684C0AC1DDDA@fugue.com> <72EB15CA-CAB4-4A50-BAB4-E60176109AF5@cisco.com>
In-Reply-To: <72EB15CA-CAB4-4A50-BAB4-E60176109AF5@cisco.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <E34DB847-4FC9-4982-A609-B80707F61E45@fugue.com>
X-Mailer: iPad Mail (9A334)
From: Ted Lemon <mellon@fugue.com>
Date: Wed, 16 Nov 2011 15:58:41 +0800
To: Fred Baker <fred@cisco.com>
Cc: Russ White <russw@riw.us>, Ole Troan <ot@cisco.com>, "homenet@ietf.org" <homenet@ietf.org>
Subject: Re: [homenet] draft-baker-homenet-prefix-assignment
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 16 Nov 2011 07:58:10 -0000

On Nov 16, 2011, at 3:41 PM, Fred Baker <fred@cisco.com> wrote:
> If we do it another way, whether ZOSPF's or some other way, we have the sa=
me problem in the sense that there will be multiple sources of subnet prefix=
es.

Yes.   This becomes an even uglier problem as you progress into the network,=
 because while at the edge you can tell that you are talking to two administ=
rative domains, as you move into the network past the first delegating route=
r, you wind up with a single DHCP server presenting the merged configuration=
 information from two administrative domains as if they were a single admini=
strative domain.

I thought I understood how to solve this problem before I started writing th=
e problem statement, and then when I remembered this aspect of it I kind of f=
lung my hands up in disgust.   I think the knowledge that there are two sepa=
rate administrative domains has to be visible throughout the network, but th=
is is really a substantial divergence from what DHCPv6, at least, currently d=
oes.

I can certainly imagine extending DHCPv6 in a cascading prefix delegation sc=
enario where it signals this information down the cascade, but it's conceptu=
ally quite a bit different.


From ot@cisco.com  Wed Nov 16 00:12:45 2011
Return-Path: <ot@cisco.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8FEE321F9413 for <homenet@ietfa.amsl.com>; Wed, 16 Nov 2011 00:12:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.771
X-Spam-Level: 
X-Spam-Status: No, score=-9.771 tagged_above=-999 required=5 tests=[AWL=0.828,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZPjvQQcJ5zQ2 for <homenet@ietfa.amsl.com>; Wed, 16 Nov 2011 00:12:38 -0800 (PST)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id B6C0421F9412 for <homenet@ietf.org>; Wed, 16 Nov 2011 00:12:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ot@cisco.com; l=1573; q=dns/txt; s=iport; t=1321431157; x=1322640757; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=33B64pwCrbGc6XNdRQZtReTLp5weTTyj0x4clJj/8Ro=; b=XLLzAkCzXAHOpYwykF0EUUCq6ppeTdGt0aSVn/zEEgUAW8g0rv51OFXo eVcRKZvmAKKGgpYuNQKecMELdziQdAh5KI6ESh8ebOuV5WjmWP45r4r4t l9Xmn9bULKioi4N5RGKX2pJbhZmRQCPPMzjGhWO/SY5V0ZOh8I4tNuUNx o=;
X-IronPort-AV: E=Sophos;i="4.69,520,1315180800"; d="scan'208";a="121744653"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-1.cisco.com with ESMTP; 16 Nov 2011 08:12:36 +0000
Received: from dhcp-10-55-92-176.cisco.com (dhcp-10-55-92-176.cisco.com [10.55.92.176]) by ams-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id pAG8CXYK017871; Wed, 16 Nov 2011 08:12:34 GMT
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Ole Troan <ot@cisco.com>
In-Reply-To: <E34DB847-4FC9-4982-A609-B80707F61E45@fugue.com>
Date: Wed, 16 Nov 2011 16:12:32 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <E5723B4B-BDE4-47F4-B560-1165F713D5E2@cisco.com>
References: <4EC1D206.2070303@gmail.com> <3C716203-8579-41EA-98CE-6DC3BE9261D8@fugue.com> <FC520CA0-BAA4-4309-A878-CB40308F2562@cisco.com> <09215FB7-EA7A-4D9D-8772-737B79CBBD20@fugue.com> <4EC32B76.8080706@riw.us> <7DADF53B-56CA-47CC-BBDA-34300EE4D22D@fugue.com> <7D0889B6-7769-4F74-996D-08CDA02B3670@cisco.com> <84FD521E-D48C-41C9-935B-9B4695FB658D@cisco.com> <489BE869-79F9-40FC-96B1-6A190620B4CA@cisco.com> <7F630AC9-A369-48B8-BD8F-684C0AC1DDDA@fugue.com> <72EB15CA-CAB4-4A50-BAB4-E60176109AF5@cisco.com> <E34DB847-4FC9-4982-A609-B80707F61E45@fugue.com>
To: Ted Lemon <mellon@fugue.com>
X-Mailer: Apple Mail (2.1084)
Cc: Russ White <russw@riw.us>, "homenet@ietf.org" <homenet@ietf.org>, Fred Baker <fred@cisco.com>
Subject: Re: [homenet] draft-baker-homenet-prefix-assignment
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 16 Nov 2011 08:12:45 -0000

Ted,

>> If we do it another way, whether ZOSPF's or some other way, we have =
the same problem in the sense that there will be multiple sources of =
subnet prefixes.
>=20
> Yes.   This becomes an even uglier problem as you progress into the =
network, because while at the edge you can tell that you are talking to =
two administrative domains, as you move into the network past the first =
delegating router, you wind up with a single DHCP server presenting the =
merged configuration information from two administrative domains as if =
they were a single administrative domain.
>=20
> I thought I understood how to solve this problem before I started =
writing the problem statement, and then when I remembered this aspect of =
it I kind of flung my hands up in disgust.   I think the knowledge that =
there are two separate administrative domains has to be visible =
throughout the network, but this is really a substantial divergence from =
what DHCPv6, at least, currently does.
>=20
> I can certainly imagine extending DHCPv6 in a cascading prefix =
delegation scenario where it signals this information down the cascade, =
but it's conceptually quite a bit different.

that's exactly reasons why we have started looking at flooding type =
protocols in homenet as opposed to request/reply protocols.
it isn't only multiple sources and service discovery that is problematic =
with a request/reply protocol, it is also how it handles dynamism. =
something which was explored in the development of the DNS option for =
RA.

cheers,
Ole


From mellon@fugue.com  Wed Nov 16 00:23:55 2011
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A82B21F9427 for <homenet@ietfa.amsl.com>; Wed, 16 Nov 2011 00:23:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.225
X-Spam-Level: 
X-Spam-Status: No, score=-1.225 tagged_above=-999 required=5 tests=[AWL=-0.022, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JplSZHuqkqEY for <homenet@ietfa.amsl.com>; Wed, 16 Nov 2011 00:23:54 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id B560321F9429 for <homenet@ietf.org>; Wed, 16 Nov 2011 00:23:54 -0800 (PST)
Received: from [172.22.13.155] (unknown [122.147.240.7]) by toccata.fugue.com (Postfix) with ESMTPSA id B17D52380C63; Wed, 16 Nov 2011 03:23:53 -0500 (EST)
References: <4EC1D206.2070303@gmail.com> <3C716203-8579-41EA-98CE-6DC3BE9261D8@fugue.com> <FC520CA0-BAA4-4309-A878-CB40308F2562@cisco.com> <09215FB7-EA7A-4D9D-8772-737B79CBBD20@fugue.com> <4EC32B76.8080706@riw.us> <7DADF53B-56CA-47CC-BBDA-34300EE4D22D@fugue.com> <7D0889B6-7769-4F74-996D-08CDA02B3670@cisco.com> <84FD521E-D48C-41C9-935B-9B4695FB658D@cisco.com> <489BE869-79F9-40FC-96B1-6A190620B4CA@cisco.com> <7F630AC9-A369-48B8-BD8F-684C0AC1DDDA@fugue.com> <72EB15CA-CAB4-4A50-BAB4-E60176109AF5@cisco.com> <E34DB847-4FC9-4982-A609-B80707F61E45@fugue.com> <E5723B4B-BDE4-47F4-B560-1165F713D5E2@cisco.com>
In-Reply-To: <E5723B4B-BDE4-47F4-B560-1165F713D5E2@cisco.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <46CB823A-3C53-4C32-A33C-498CA6413448@fugue.com>
X-Mailer: iPad Mail (9A334)
From: Ted Lemon <mellon@fugue.com>
Date: Wed, 16 Nov 2011 16:24:26 +0800
To: Ole Troan <ot@cisco.com>
Cc: Russ White <russw@riw.us>, "homenet@ietf.org" <homenet@ietf.org>, Fred Baker <fred@cisco.com>
Subject: Re: [homenet] draft-baker-homenet-prefix-assignment
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 16 Nov 2011 08:23:55 -0000

On Nov 16, 2011, at 4:12 PM, Ole Troan <ot@cisco.com> wrote:
> that's exactly reasons why we have started looking at flooding type protoc=
ols in homenet as opposed to request/reply protocols.
> it isn't only multiple sources and service discovery that is problematic w=
ith a request/reply protocol, it is also how it handles dynamism. something w=
hich was explored in the development of the DNS option for RA.

I think that flooding protocols are a good idea for discovering the topology=
 of the homenet and setting up routing.   However, I suspect that you are go=
ing to get your prefix(es) from your provider(s) through DHCPv6 prefix deleg=
ation, so there's still a problem to be thought through.   I don't have a st=
rong opinion yet on whether you should use PD inside of the network, althoug=
h I think once you've discovered the network topology (which you could do wi=
th link-local addresses) it's certainly a viable mechanism.


From fred@cisco.com  Wed Nov 16 01:20:18 2011
Return-Path: <fred@cisco.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DBE9021F9442 for <homenet@ietfa.amsl.com>; Wed, 16 Nov 2011 01:20:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.579
X-Spam-Level: 
X-Spam-Status: No, score=-109.579 tagged_above=-999 required=5 tests=[AWL=1.020, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id io507oc8HdJ9 for <homenet@ietfa.amsl.com>; Wed, 16 Nov 2011 01:20:18 -0800 (PST)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id 09FE121F9479 for <homenet@ietf.org>; Wed, 16 Nov 2011 01:20:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=1018; q=dns/txt; s=iport; t=1321435218; x=1322644818; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to:content-transfer-encoding; bh=LuiamWwlmLGLbkMCes4g+JFtfZ2+62NrDSwqKYem7y4=; b=BqAULniTfnct00DVMTiAc0kId7VvWFPxsnWwUhEj0NcCHN3+NBkH/Uce g/R04Kq0i22dT6hpFi0PolXjXtATEm6zingNPmJrmtji/EJzAo6sWgVKG VDVZpk7CC5vZ8XLeCA068M570qr81+GTZrNJ+dUe2M5GfN4Z4f7Ebl9Zo k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAFB/w05Io8US/2dsb2JhbABDqXOBBYFyAQEBAwESASc/BQsLEgYuISgOBhMih2CaNAGeW4k0YwSIEowihTuFEIc+
X-IronPort-AV: E=Sophos;i="4.69,520,1315180800"; d="scan'208";a="121752518"
Received: from bgl-core-3.cisco.com ([72.163.197.18]) by ams-iport-1.cisco.com with ESMTP; 16 Nov 2011 09:20:16 +0000
Received: from dhcp-4466.meeting.ietf.org (hkidc-vpn-client-233-204.cisco.com [10.75.233.204]) by bgl-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id pAG9KEZx026633; Wed, 16 Nov 2011 09:20:14 GMT
Received: from [127.0.0.1] by dhcp-4466.meeting.ietf.org (PGP Universal service); Wed, 16 Nov 2011 17:20:14 +0800
X-PGP-Universal: processed; by dhcp-4466.meeting.ietf.org on Wed, 16 Nov 2011 17:20:14 +0800
Mime-Version: 1.0 (Apple Message framework v1084)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <CAKD1Yr02-uj28JnMnNeFPc-nUYGpp-fobZW7wSY_3WTGH0DaBQ@mail.gmail.com>
Date: Wed, 16 Nov 2011 17:20:04 +0800
Message-Id: <908FE1EA-C31C-4A57-B8BA-C654C795B98F@cisco.com>
References: <4EC1C386.6010802@gmail.com> <CAKD1Yr02-uj28JnMnNeFPc-nUYGpp-fobZW7wSY_3WTGH0DaBQ@mail.gmail.com>
To: Lorenzo Colitti <lorenzo@google.com>
X-Mailer: Apple Mail (2.1084)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: Hans Liu <Hans_Liu@dlink.com.tw>, homenet@ietf.org
Subject: Re: [homenet] pervasive v4
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 16 Nov 2011 09:20:19 -0000

On Nov 15, 2011, at 1:42 PM, Lorenzo Colitti wrote:

> On Tue, Nov 15, 2011 at 09:42, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:
> If homenet is going to support arbitrary self-configuring topologies,
> and pervasive legacy IPv4 is required, we'd surely end up recommending
> NAT444-within-the-home as the only remotely practicable approach.
>=20
> Hans from D-Link suggests that another option is simply to bridge IPv4 =
packets and route IPv6 packets.

That's what some routers do to provide IPv6 and IPv4 in parallel from an =
ISP. If you start from the assumption, very clearly stated in the =
architecture draft, that one might want to route within the home (for =
example to pull A/V on one path and data, smart grid, or other services =
on another), that's side-stepping the discussion.

We could, for example, simply bridge throughout a data center. It would =
get packets there. Put all the tenants on the same LAN. Oh, there are =
problems? Hmmm, hadn't thought of that.=

From ot@cisco.com  Wed Nov 16 02:04:56 2011
Return-Path: <ot@cisco.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 87DFB21F9641 for <homenet@ietfa.amsl.com>; Wed, 16 Nov 2011 02:04:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PyjtBp5zMCqy for <homenet@ietfa.amsl.com>; Wed, 16 Nov 2011 02:04:55 -0800 (PST)
Received: from mtv-iport-3.cisco.com (mtv-iport-3.cisco.com [173.36.130.14]) by ietfa.amsl.com (Postfix) with ESMTP id D8D8E21F963F for <homenet@ietf.org>; Wed, 16 Nov 2011 02:04:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ot@cisco.com; l=1977; q=dns/txt; s=iport; t=1321437896; x=1322647496; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=F6SEbzDa0ZbSqVEb+pTq60jMris6qEcYZhEAIpjajq4=; b=IEF76Pyfz3kjusQ9bjLWKoLoJuxg1V57YjvGBKDS69+kycVYnIQ9rr91 vFSAIfSX1Eh85TCyZoe923SJm1+z5fqiVibjGhS0DKJ5KoSBw235jfoX0 O+rM6pdiC9bfMe+r2n0JOjzdVJOz/vFIBPfK02Tdk4q3vxaLYxDOGdN8y k=;
X-IronPort-AV: E=Sophos;i="4.69,520,1315180800"; d="scan'208";a="14526189"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-3.cisco.com with ESMTP; 16 Nov 2011 10:04:55 +0000
Received: from [10.21.86.64] ([10.21.86.64]) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id pAGA4sBU027939; Wed, 16 Nov 2011 10:04:54 GMT
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Ole Troan <ot@cisco.com>
In-Reply-To: <4EC38853.3020504@globis.net>
Date: Wed, 16 Nov 2011 18:04:53 +0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <FB5023BD-396C-4C54-A9D0-1E21CC60B25D@cisco.com>
References: <4EC1D206.2070303@gmail.com>	<3C716203-8579-41EA-98CE-6DC3BE9261D8@fugue.com>	<FC520CA0-BAA4-4309-A878-CB40308F2562@cisco.com>	<09215FB7-EA7A-4D9D-8772-737B79CBBD20@fugue.com>	<4EC32B76.8080706@riw.us>	<7DADF53B-56CA-47CC-BBDA-34300EE4D22D@fugue.com>	<7D0889B6-7769-4F74-996D-08CDA02B3670@cisco.com>	<84FD521E-D48C-41C9-935B-9B4695FB658D@cisco.com>	<489BE869-79F9-40FC-96B1-6A190620B4CA@cisco.com>	<7F630AC9-A369-48B8-BD8F-684C0AC1DDDA@fugue.com> <72EB15CA-CAB4-4A50-BAB4-E60176109AF5@cisco.com> <4EC38853.3020504@globis.net>
To: Ray Hunter <Ray.Hunter@globis.net>
X-Mailer: Apple Mail (2.1084)
Cc: Russ White <russw@riw.us>, "homenet@ietf.org" <homenet@ietf.org>, Ted Lemon <mellon@fugue.com>, Fred Baker <fred@cisco.com>
Subject: Re: [homenet] draft-baker-homenet-prefix-assignment
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 16 Nov 2011 10:04:56 -0000

Ray,

> Actually, if you use another mechanism within the home there's a =
danger that it might be worse: you then have potentially different =
semantics of leases and possibly a lack of synchronization of timers: =
the lease on the ISP link may expire, but locally assigned Homenet =
sub-leases not, leading to black holes. Might become significant when =
changing providers or when providers want to renumber.

you already have that. and from what I heard from UNH most CPEs got it =
wrong. (DHCPv6 PD lease timers must be mapped to RA PIO option life =
times).

cheers,
Ole

>=20
> Fred Baker wrote:
>> I don't much care whose charter it's in. I do think that if we have =
an idea that an ISP will allocate an IA_PD to a directly attached router =
and that router will then, in some way, sub-allocate subnet prefixes to =
subnets in the home, then there is a case in which there are multiple =
ISPs that have separate routers doing that. Ralph and I have suggested =
using the same mechanism that ISPs use to allocate prefixes to the home =
to allocate prefixes within the home, which means having multiple DHCP =
servers. If we do it another way, whether ZOSPF's or some other way, we =
have the same problem in the sense that there will be multiple sources =
of subnet prefixes.
>>=20
>> On Nov 16, 2011, at 2:56 PM, Ted Lemon wrote:
>>=20
>>  =20
>>=20
>>> On Nov 16, 2011, at 2:46 PM, Ole Troan <ot@cisco.com>
>>>  wrote:
>>>    =20
>>>=20
>>>> extend the DHCP protocol to handle multiple sources of information.
>>>>      =20
>>>>=20
>>> I think this winds up being implicit in MIF's charter, although I =
didn't realize that until quite recently.
>>>    =20
>>>=20
>>=20
>>=20
>>  =20
>>=20
>=20
> --=20
> Ray Hunter
> Ray.Hunter@globis.net
> Globis Consulting BV, Fazantlaan 23, 5613CB Eindhoven NL,
> Registered at the KvK, Eindhoven, under number BV 17098279
> mobile: +31 620 363864
>=20
> <Ray_Hunter.vcf>


From guillaume.habault@gmail.com  Wed Nov 16 02:05:21 2011
Return-Path: <guillaume.habault@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2AB0A21F9540 for <homenet@ietfa.amsl.com>; Wed, 16 Nov 2011 02:05:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ov3DAdqgIYIn for <homenet@ietfa.amsl.com>; Wed, 16 Nov 2011 02:05:20 -0800 (PST)
Received: from mail-ey0-f194.google.com (mail-ey0-f194.google.com [209.85.215.194]) by ietfa.amsl.com (Postfix) with ESMTP id 477D421F95FE for <homenet@ietf.org>; Wed, 16 Nov 2011 02:05:20 -0800 (PST)
Received: by eyd10 with SMTP id 10so60659eyd.1 for <homenet@ietf.org>; Wed, 16 Nov 2011 02:05:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=VxP77Fl25b2fspsaTBs53CCAXkwjnsQeXvPfWXKViB4=; b=Q+E+iXtFzrOLWel63AtACtzFiFZCtGGXjfYUEVUM/9Bx/3Nszo9Zrb1Nb7ZY7sUPIB KuJg/z6KU1pCtQCG18DR1uffZvWe2tcVuGvRWfMuwiuir4d4AVLSyWYEf0c53rxmOATL XhlWX2HW60WPRWH96zfvs2VLMNgY2HTbZzyUk=
MIME-Version: 1.0
Received: by 10.213.109.1 with SMTP id h1mr207948ebp.73.1321437919333; Wed, 16 Nov 2011 02:05:19 -0800 (PST)
Received: by 10.213.33.74 with HTTP; Wed, 16 Nov 2011 02:05:19 -0800 (PST)
In-Reply-To: <3512.1321317664@marajade.sandelman.ca>
References: <DCC302FAA9FE5F4BBA4DCAD46569377914518AFAE5@PRVPEXVS03.corp.twcable.com> <4EB583C8.5030907@piuha.net> <13027.1320680393@marajade.sandelman.ca> <BDF2740C082F6942820D95BAEB9E1A845A9789@XMB-AMS-108.cisco.com> <CA+XPzSY8cC_PyhcMNqhk4+B6tghp8Dpy2-3aMPZmyVRP=AWnaA@mail.gmail.com> <3512.1321317664@marajade.sandelman.ca>
Date: Wed, 16 Nov 2011 11:05:19 +0100
Message-ID: <CA+XPzSaeg=pqmdSVXr+BQvS2D0+iVqN-q7e4dJoUtA=eA38vGA@mail.gmail.com>
From: Guillaume Habault <guillaume.habault@gmail.com>
To: Michael Richardson <mcr@sandelman.ca>
Content-Type: multipart/alternative; boundary=0015174c0e32c64d6204b1d73d49
Cc: homenet@ietf.org
Subject: Re: [homenet] more comments on draft-arkko-homenet-prefix-assignment
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 16 Nov 2011 10:05:21 -0000

--0015174c0e32c64d6204b1d73d49
Content-Type: text/plain; charset=ISO-8859-1

2011/11/15 Michael Richardson <mcr@sandelman.ca>

>
> >>>>> "Guillaume" == Guillaume Habault <guillaume.habault@gmail.com>
> writes:
>    Guillaume> the host select the appropriate address, the routing
>    Guillaume> protocol may route the
>    Guillaume> message to the wrong Customer Edge Router (especially if
>    Guillaume> we are in the case
>    Guillaume> where there is more than one Customer Edge Router in the
>    Guillaume> home network.
>
> We have assumed that the home gateways will cooperate and provide source
> address routing, making sure that packets are routed out the link which
> can accept that source address.
>

To summarize and to be sure I get what you are planning to do, you will use
a "normal" routing in the home network. Then, home gateways will check the
source address of any packet coming and redirect it to the right home
gateways if the source address is not the good one (just to be sure on what
you mean by cooperate), is that right?
If so, do you planned to have tunnels between home gateways ? Are we sure
that ISPs behind the home gateway will accept to cooperate with each other
(I said that because in France, home gateways are mainly given/lend by
ISPs, and i'm not sure they will be willing to share something with another
ISP)?

-- 
Guillaume HABAULT
PhD Student
Institut TELECOM / TELECOM Bretagne

--0015174c0e32c64d6204b1d73d49
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><br><div class=3D"gmail_quote">2011/11/15 Michael Richardson <span dir=
=3D"ltr">&lt;<a href=3D"mailto:mcr@sandelman.ca">mcr@sandelman.ca</a>&gt;</=
span><br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde=
r-left:1px #ccc solid;padding-left:1ex;">
<br>
&gt;&gt;&gt;&gt;&gt; &quot;Guillaume&quot; =3D=3D Guillaume Habault &lt;<a =
href=3D"mailto:guillaume.habault@gmail.com">guillaume.habault@gmail.com</a>=
&gt; writes:<br>
 =A0 =A0Guillaume&gt; the host select the appropriate address, the routing<=
br>
 =A0 =A0Guillaume&gt; protocol may route the<br>
 =A0 =A0Guillaume&gt; message to the wrong Customer Edge Router (especially=
 if<br>
 =A0 =A0Guillaume&gt; we are in the case<br>
 =A0 =A0Guillaume&gt; where there is more than one Customer Edge Router in =
the<br>
 =A0 =A0Guillaume&gt; home network.<br>
<br>
We have assumed that the home gateways will cooperate and provide source<br=
>
address routing, making sure that packets are routed out the link which<br>
can accept that source address.<br></blockquote><div><br>To summarize and t=
o be sure I get what you are planning to do, you will use a &quot;normal&qu=
ot; routing in the home network. Then, home gateways will check the source =
address of any packet coming and redirect it to the right home gateways if =
the source address is not the good one (just to be sure on what you mean by=
 cooperate), is that right?<br>
If so, do you planned to have tunnels between home gateways ? Are we sure t=
hat ISPs behind the home gateway will accept to cooperate with each other (=
I said that because in France, home gateways are mainly given/lend by=A0 IS=
Ps, and i&#39;m not sure they will be willing to share something with anoth=
er ISP)?=A0 <br>
<br></div></div>-- <br>Guillaume HABAULT<br>PhD Student<br>Institut TELECOM=
 / TELECOM Bretagne<br><br><br>

--0015174c0e32c64d6204b1d73d49--

From v6ops@globis.net  Wed Nov 16 02:16:52 2011
Return-Path: <v6ops@globis.net>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23B0F21F938A for <homenet@ietfa.amsl.com>; Wed, 16 Nov 2011 02:16:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.49
X-Spam-Level: 
X-Spam-Status: No, score=-2.49 tagged_above=-999 required=5 tests=[AWL=0.108,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0OC5HQG54XW5 for <homenet@ietfa.amsl.com>; Wed, 16 Nov 2011 02:16:51 -0800 (PST)
Received: from globis01.globis.net (RayH-1-pt.tunnel.tserv11.ams1.ipv6.he.net [IPv6:2001:470:1f14:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id 50B3A21F9389 for <homenet@ietf.org>; Wed, 16 Nov 2011 02:16:51 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id 830758700E6; Wed, 16 Nov 2011 11:16:49 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at globis01.globis.net
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 PS3oYhOLKqPt; Wed, 16 Nov 2011 11:16:40 +0100 (CET)
Received: from Rays-iMac.local (unknown [192.168.0.3]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPA id BBA6F8700E3; Wed, 16 Nov 2011 11:16:40 +0100 (CET)
Message-ID: <4EC38D88.6080104@globis.net>
Date: Wed, 16 Nov 2011 11:16:40 +0100
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox Express 1.0.1 (Macintosh/20100705)
MIME-Version: 1.0
To: Ole Troan <ot@cisco.com>
References: <4EC1D206.2070303@gmail.com>	<3C716203-8579-41EA-98CE-6DC3BE9261D8@fugue.com>	<FC520CA0-BAA4-4309-A878-CB40308F2562@cisco.com>	<09215FB7-EA7A-4D9D-8772-737B79CBBD20@fugue.com>	<4EC32B76.8080706@riw.us>	<7DADF53B-56CA-47CC-BBDA-34300EE4D22D@fugue.com>	<7D0889B6-7769-4F74-996D-08CDA02B3670@cisco.com>	<84FD521E-D48C-41C9-935B-9B4695FB658D@cisco.com>	<489BE869-79F9-40FC-96B1-6A190620B4CA@cisco.com>	<7F630AC9-A369-48B8-BD8F-684C0AC1DDDA@fugue.com> <72EB15CA-CAB4-4A50-BAB4-E60176109AF5@cisco.com> <4EC38853.3020504@globis.net> <FB5023BD-396C-4C54-A9D0-1E21CC60B25D@cisco.com>
In-Reply-To: <FB5023BD-396C-4C54-A9D0-1E21CC60B25D@cisco.com>
Content-Type: multipart/alternative; boundary="------------000500050306010304000003"
Cc: Russ White <russw@riw.us>, "homenet@ietf.org" <homenet@ietf.org>, Ted Lemon <mellon@fugue.com>, Fred Baker <fred@cisco.com>
Subject: Re: [homenet] draft-baker-homenet-prefix-assignment
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 16 Nov 2011 10:16:52 -0000

This is a multi-part message in MIME format.
--------------000500050306010304000003
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Sure you should cascade the IA_PD timers into the ND RA prefix 
information option lifetime timers. Doh. Wasn't that obvious? Just 
because people got it wrong once doesn't mean we should make things even 
more complex. In fact, that's all the more reason that Homenet should 
address implementation simplicity, and the interaction of timers explicitly.

Ole Troan wrote:
> Ray,
>
>    
>> >  Actually, if you use another mechanism within the home there's a danger that it might be worse: you then have potentially different semantics of leases and possibly a lack of synchronization of timers: the lease on the ISP link may expire, but locally assigned Homenet sub-leases not, leading to black holes. Might become significant when changing providers or when providers want to renumber.
>>      
>
> you already have that. and from what I heard from UNH most CPEs got it wrong. (DHCPv6 PD lease timers must be mapped to RA PIO option life times).
>
> cheers,
> Ole
>
>    

--------------000500050306010304000003
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html; charset=ISO-8859-1"
 http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Sure you should cascade the IA_PD timers into the ND RA prefix
information option lifetime timers. Doh. Wasn't that obvious? Just
because people got it wrong once doesn't mean we should make things
even more complex. In fact, that's all the more reason that Homenet
should address implementation simplicity, and the interaction of timers
explicitly.<br>
<br>
Ole Troan wrote:
<blockquote type="cite">
  <pre wrap="">Ray,

  </pre>
  <blockquote type="cite" style="color: rgb(0, 0, 0);">
    <pre wrap=""><span class="moz-txt-citetags">&gt; </span>Actually, if you use another mechanism within the home there's a danger that it might be worse: you then have potentially different semantics of leases and possibly a lack of synchronization of timers: the lease on the ISP link may expire, but locally assigned Homenet sub-leases not, leading to black holes. Might become significant when changing providers or when providers want to renumber.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
you already have that. and from what I heard from UNH most CPEs got it wrong. (DHCPv6 PD lease timers must be mapped to RA PIO option life times).

cheers,
Ole

  </pre>
</blockquote>
</body>
</html>

--------------000500050306010304000003--

From acee.lindem@ericsson.com  Wed Nov 16 07:11:42 2011
Return-Path: <acee.lindem@ericsson.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D980121F9608 for <homenet@ietfa.amsl.com>; Wed, 16 Nov 2011 07:11:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.534
X-Spam-Level: 
X-Spam-Status: No, score=-6.534 tagged_above=-999 required=5 tests=[AWL=0.065,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P6NTE6LMdnfN for <homenet@ietfa.amsl.com>; Wed, 16 Nov 2011 07:11:42 -0800 (PST)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 1087321F95CF for <homenet@ietf.org>; Wed, 16 Nov 2011 07:11:42 -0800 (PST)
Received: from eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id pAGFBVoI006409; Wed, 16 Nov 2011 09:11:35 -0600
Received: from EUSAACMS0702.eamcs.ericsson.se ([169.254.1.218]) by eusaamw0712.eamcs.ericsson.se ([147.117.20.181]) with mapi; Wed, 16 Nov 2011 10:11:29 -0500
From: Acee Lindem <acee.lindem@ericsson.com>
To: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
Date: Wed, 16 Nov 2011 10:11:26 -0500
Thread-Topic: [homenet] Comments on draft-acee-ospf-ospfv3-autoconfig-00
Thread-Index: AcykcgRelqk4HrMjQmuj08uNVtaSeg==
Message-ID: <B350DA39-4784-4AF5-9E2F-CBD388980CB5@ericsson.com>
References: <CAKD1Yr3uSsNP4avZBdQE7YxFd7D_KOXBOCsfaRfvnWhJoLoY9Q@mail.gmail.com> <B3BE775A-4EBB-4C17-9EDC-7B9AFCB8867E@ericsson.com> <CAKD1Yr0MFdyBopr0E0WiebLSZ+M2J9vAi1U6b66VxhziE2XJpw@mail.gmail.com> <FF6FB9A0-9F91-4658-A265-BA200A0858AF@ericsson.com> <4EC29D17.10302@cisco.com> <6A2F0A68-5D4F-4742-A95F-18688525D6B7@ericsson.com> <D4EF568D-2AFF-4212-B6C0-960DE0673449@cisco.com>
In-Reply-To: <D4EF568D-2AFF-4212-B6C0-960DE0673449@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/signed; boundary="Apple-Mail-65--448296991"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
Cc: "homenet@ietf.org" <homenet@ietf.org>, Jari Arkko <jari.arkko@piuha.net>, Lorenzo Colitti <lorenzo@google.com>
Subject: Re: [homenet] Comments on draft-acee-ospf-ospfv3-autoconfig-00
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 16 Nov 2011 15:11:43 -0000

--Apple-Mail-65--448296991
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi Carlos,=20

On Nov 15, 2011, at 10:34 PM, Carlos Pignataro (cpignata) wrote:

> Hi Acee,
>=20
> On Nov 15, 2011, at 1:39 PM, "Acee Lindem" <acee.lindem@ericsson.com> =
wrote:
>=20
>> Hi Carlos,
>>=20
>> On Nov 15, 2011, at 12:10 PM, Carlos Pignataro wrote:
>>=20
>>> Hi Acee,
>>>=20
>>> On 11/14/2011 10:11 PM, Acee Lindem wrote:
>>>>=20
>>>> On Nov 14, 2011, at 9:46 PM, Lorenzo Colitti wrote:
>>>>=20
>>>>> On Tue, Nov 15, 2011 at 10:25, Acee Lindem =
<acee.lindem@ericsson.com
>>>>> <mailto:acee.lindem@ericsson.com>> wrote:
>>>>>=20
>>>>>> 1. I think the OSPFv3 router ID should not be based on the MAC
>>>>>  address because that will encourage people to assume it's unique
>>>>>  "most of the time". I think we should just make it a =
pseudo-random
>>>>>  number so it's clear that uniqueness is only guaranteed by
>>>>>  collision detection and that collision detection needs to be =
robust.
>>>>>=20
>>>>>  The draft requires duplicate Router-ID detection and resolution. =
I
>>>>>  don't think that the fact that a portion of the MAC address is
>>>>>  used as a first try is reason for this detection/resolution not =
to
>>>>>  be implemented or tested.
>>>>>=20
>>>>>=20
>>>>> In my experience, giving people something that works "most of the
>>>>> time" will cause the cases where it doesn't work to break. I think
>>>>> it's better to explicitly provide no guarantees of uniqueness to =
make
>>>>> it clear that collision detection needs to be robust.=20
>>>>=20
>>>> In the OSPF WG, the fact that a mechanism is specified implies that =
it
>>>> is required to be robust.=20
>>>>=20
>>>>> Also, if we rely on collision detection, then what's the advantage =
of
>>>>> using the MAC address? We might as well as make it random all the =
time
>>>>> - that probably has a lower chance of collision anyway.
>>>>=20
>>>> I can't disagree with this argument and think we could go with a
>>>> psuedo-random number seeded with a hash on the hardware fingerprint =
as
>>>> the first try for router-id.=20
>>>>=20
>>>=20
>>> As a side note, what's your opinion on citing and =
suggesting/requiring
>>> <http://tools.ietf.org/html/rfc5642#section-4> for manageability?
>>=20
>> I think the dynamic host-name is less applicable in an =
auto-configured routing domain than other domains. In the =
auto-configured routing domain, you hope that little monitoring, =
debugging, or interaction is required.=20
>=20
> I agree that a goal is for less monitoring and interaction in this =
deployment model -- however sometimes less troubleshooting is =
aspirational, and debugging cannot be avoided :-) for those cases, a =
human-parseable node string is quite handy (especially when with =
pseudo-random -- potentially changing on reload or electrical hiccup (?) =
-- router-ids).  Thinking aloud a bit as I see both sides; but =
acknowledging that a stable node reference can help in troubleshooting =
(if/when required)

If the router has little to no configuration, from where would the =
dynamic host name originate?

Thanks,
Acee


>=20
> Thanks!
>=20
> Carlos P.
>=20
>> Thanks,
>> Acee
>>=20
>>=20
>>=20
>>>=20
>>> Thanks,
>>>=20
>>> -- Carlos.
>>>=20
>>>>>=20
>>>>>  I think you mean virtual links. They are definitely not needed in
>>>>>  the auto-configured environment as they are for providing a
>>>>>  backbone path through a transit area and the OSPFv3
>>>>>  auto-configured routing domain assumes only a backbone area.
>>>>>=20
>>>>>=20
>>>>> Yes, virtual links. Do we need to state explicitly that they =
cannot
>>>>> exist and are not supported?
>>>>=20
>>>> Since the auto-configured routing domain is area 0 only, it is =
explicit.=20
>>>>=20
>>>>>=20
>>>>>=20
>>>>>> 3. Can we use normal LSAs to detect collisions? One idea would
>>>>>  be "if you see your own router ID in the list of neighbours of a
>>>>>  network LSA or router LSA, then there is a collision". Will that
>>>>>  work? If so we wouldn't need the hardware fingerprint at all.
>>>>>=20
>>>>>  No. In an arbitrary topology, A router with a duplicate router-id
>>>>>  can be multiple hops away.
>>>>>=20
>>>>>=20
>>>>> Yes, but router and network LSAs are flooded, so you'll hear them
>>>>> regardless of whether your duplicate is multiple hops away, no?
>>>>=20
>>>> Both OSPFv3 and OSPFv2 would consider an unrecognized =
self-originated
>>>> LSA, i.e. having our Route-ID, as a stale LSA and purge it. This is =
a
>>>> very basic mechanism of OSPF. I'd rather use a separate mechanism =
for
>>>> duplicate Router-ID detection. I considered techniques involving =
the
>>>> encoding some additional information in the Router-LSA but these =
all
>>>> seemed to be hacked.=20
>>>>=20
>>>>=20
>>>>>=20
>>>>>=20
>>>>>  If the pre-shared key is hard-coded, it is no better than the
>>>>>  OSPFv3 Interface Instance ID that is specified to prevent
>>>>>  inadvertent adjacencies with routers not supporting the
>>>>>  auto-configuration. If configuration of a pre-shared key is
>>>>>  required, you no longer have auto-configuration.
>>>>>=20
>>>>>=20
>>>>> Sorry, that wasn't clear. What I meant to say is that we should =
pick
>>>>> one scheme (e.g., HMAC-SHA) and stick to it; we shouldn't support
>>>>> multiple schemes as that will lead to interoperability issues for
>>>>> devices that use one scheme and devices that use another scheme.
>>>>=20
>>>> The OSPFv3 Instance ID is part of the base OSPFv3 specification and =
I
>>>> think it is a very good mechanism to prevent inadvertent =
adjacencies. If
>>>> we need real authentication, we'll need a pre-shared key. I don't =
see
>>>> any advantage of authentication with a well-known pre-shared key to
>>>> prevent inadvertent adjacencies.=20
>>>>=20
>>>> Thanks for the comments,
>>>> Acee=20
>>>>=20
>>>>=20
>>>>=20
>>>>=20
>>>> _______________________________________________
>>>> 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
>>=20
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet


--Apple-Mail-65--448296991
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIM8jCCBDQw
ggMcoAMCAQICECFWwVQHDV12M/Sr0yNv0sYwDQYJKoZIhvcNAQEFBQAwOTERMA8GA1UECgwIRXJp
Y3Nzb24xJDAiBgNVBAMMG0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMTAeFw0xMDEwMDEyMDA0
NTlaFw0xMzEwMDEyMDA0NDhaMG8xETAPBgNVBAoMCEVyaWNzc29uMR8wHQYDVQQDDBZBY2VlIExp
bmRlbSBMaW5kZW0gSUlJMRAwDgYDVQQFEwdlYWxmbGluMScwJQYJKoZIhvcNAQkBFhhhY2VlLmxp
bmRlbUBlcmljc3Nvbi5jb20wgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAI/Dc9ALiZuBMyuv
bsc3eBxjXZpMi45Z0vzsUQZTJGTBeY7p9JsdzXC9J1uMisBxYVi39R3KJo6I4hXVp9wrA1rxh4AE
bnP1+Gxfpj33uWEFYbBnVAJkIWYWF7CYTn8Zm/yd13vPXtuGA6ESeLnnJafwC9Y0YwUQ+4HX7PNv
uauVAgMBAAGjggGEMIIBgDCBwAYDVR0fBIG4MIG1MIGyoIGvoIGshjdodHRwOi8vY3JsLnRydXN0
LnRlbGlhLmNvbS9Fcmljc3Nvbk5MSW5kaXZpZHVhbENBMDEuY3JshnFsZGFwOi8vbGRhcC50cnVz
dC50ZWxpYS5jb20vY249RXJpY3Nzb24lMjBOTCUyMEluZGl2aWR1YWwlMjBDQTAxLG89RXJpY3Nz
b24/Y2VydGlmaWNhdGVyZXZvY2F0aW9ubGlzdDtiaW5hcnk/YmFzZTAjBgNVHREEHDAagRhhY2Vl
LmxpbmRlbUBlcmljc3Nvbi5jb20wRgYDVR0gBD8wPTA7BgYqhXBrAQEwMTAvBggrBgEFBQcCARYj
aHR0cDovL3d3dy5lcmljc3Nvbi5jb20vbGVnYWwuc2h0bWwwHQYDVR0OBBYEFAgOzAPuplmPr7C1
BTqV94OyqUdhMB8GA1UdIwQYMBaAFJYnw7jepV9dRD45UuVFsXZfYzCbMA4GA1UdDwEB/wQEAwIF
oDANBgkqhkiG9w0BAQUFAAOCAQEAE1gyNW6c2t/YsLxW5sm67+gVGK0Lnge4ub+k8dgGrK7Mj7em
nkOIFkjdv/tqdJ/SoUy/WEkBXba2TfpZ+lfluMgLYux1vSvqBUxYBsUHeNth2Q/Y6A9sCaDTBPlK
vZ2jLz814NavrVfgTCLdxX6zNtGdwzhviz+FyqyxYF43Q86RP8Gd/Npaz1W8pmYAHm0+lezuTx5k
F3Av3+SaZ/MR6s+RWuXEIdED36ajeQz+OG8Mh3nplofzdrOeoWGDz53YlfRhgj+TXo+H1lclZAvD
WVaMMXPdb27h9Hngsq87dkCW9uAyv8DI993rdhqzlEgUyQIL32icAXfTmTYgoGPOwjCCBEUwggMt
oAMCAQICEBPJ6v/eJq2p3KTKI4GDR+MwDQYJKoZIhvcNAQEFBQAwRDEaMBgGA1UECgwRVGVsaWFT
b25lcmEgR3JvdXAxJjAkBgNVBAMMHVRlbGlhU29uZXJhIFB1YmxpYyBSb290IENBIHYxMB4XDTA2
MTAwNjEwMDA1M1oXDTE2MTAwMjA1MDQxN1owOTERMA8GA1UECgwIRXJpY3Nzb24xJDAiBgNVBAMM
G0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoC
ggEBALYQd+Q1HuuHxDyNGFlEPzCxuPPFO5W2xyr+nqCVnNJ4QYFe1HACqavqNLwUGIqIEyHv1rLn
fub9LBc7dQpRHjl/dggin0ONOFJ36nbGEbfHjLJz2BzOWvwl84Sc+Fx09IrDU/SZSWFSfhqTu3TT
39h79brHdRkdPBUgBYgsiFKriHI0TjP5G8628H27BDzqUpzGLSYWgt6/tpwuOH5lcfNfHWMcCYXR
lobv0Klu8lxG5amWqAnqrH6ECOyYJTRbHTsaTIZOHy9Qw/0eXPujKT7tU5xxSI2SdceJqzUbAz2o
FRQ6Px7/GydpM/Rl+qYoGPcauHUL1aSeVJZqDFqcIF0CAwEAAaOCATwwggE4MBIGA1UdEwEB/wQI
MAYBAf8CAQAwRgYDVR0gBD8wPTA7BgcqhXAjAgEBMDAwLgYIKwYBBQUHAgEWImh0dHBzOi8vcmVw
b3NpdG9yeS50cnVzdC50ZWxpYS5jb20wgYkGA1UdHwSBgTB/MH2ge6B5hndsZGFwOi8vbGRhcC50
cnVzdC50ZWxpYS5jb20vY249VGVsaWFTb25lcmElMjBQdWJsaWMlMjBSb290JTIwQ0ElMjB2MSxv
PVRlbGlhU29uZXJhJTIwR3JvdXA/YXV0aG9yaXR5cmV2b2NhdGlvbmxpc3Q/YmFzZTAOBgNVHQ8B
Af8EBAMCAQYwHQYDVR0OBBYEFJYnw7jepV9dRD45UuVFsXZfYzCbMB8GA1UdIwQYMBaAFEXb8I+4
GmKhqCMbY4g4o9vgGmLxMA0GCSqGSIb3DQEBBQUAA4IBAQB2AEoqQz+M3Ra9alkpn/YnwhXIv6tP
jhUvSuNs00Nhd0T9XhlIU3a65CaB/UKSqnayE0t7Q0Qq3r+x/GK3in/mik8i/PK2/q8HutzYFSzz
6Npztpo2JG7AEKOJPVaeebjng45m6vNC7RIfzU9sG2LBR/hewS8s6dFFn70w795xUwJBWZ67OzIK
XrIVVvHTOYpbWA+MESKAXwFhnVONrOTWlVwrMUi4HbiPWpOk+xQbgehCEi7mu3cXsaU1Xq3kMXui
NuC7VKoob8mFO9o9RT+dlirD2uRXwNpvCu3but6Kyhu0+nvy2iXGKjdlxlWTsdDyulXYz+OYCMZ9
lFWRzMIPMIIEbTCCA1WgAwIBAgIRAJywjASay5cieGNithuGWj0wDQYJKoZIhvcNAQEFBQAwOjEZ
MBcGA1UEChMQUlNBIFNlY3VyaXR5IEluYzEdMBsGA1UECxMUUlNBIFNlY3VyaXR5IDIwNDggVjMw
HhcNMDYxMDMxMjA0MjI3WhcNMTYxMTAxMTU0MjI1WjBEMRowGAYDVQQKDBFUZWxpYVNvbmVyYSBH
cm91cDEmMCQGA1UEAwwdVGVsaWFTb25lcmEgUHVibGljIFJvb3QgQ0EgdjEwggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQDKTxADapCAq3mplX4R4gNt+WZe5QKGnaVEQSyY7lICKF5DuVdW
PMLHDjzhw5IzDd860ZZx/0VrhGB3DmP4SDIWCKo2PxvY5NckdBWPWp/T2uaQdOAwgqHpN0pe1X7/
jel59WsWYXKGg/81Wth73ZK/geE7Gz9Pvj1LU6N4YhLMgooxKnCS+ZjB5icWAg+Qd1QpQhF46H1i
bp6LsBWDp56MPpg8F5X6y7MGVcKYLdnLOPs84uxRW9qs1kBopzQBj6s5SyVh8A+j5liDBjghXYpw
/+paGEdqHPeSFYxZKeJatmjEKLYlxcZWRKf436KvQA9jBhMEmytMNbGicR1mRH6tAgMBAAGjggFi
MIIBXjAfBgNVHSMEGDAWgBQHw1EwpKrpRa41JPr/JCwz0LGdjDAdBgNVHQ4EFgQURdvwj7gaYqGo
IxtjiDij2+AaYvEwEgYDVR0TAQH/BAgwBgEB/wIBBDCBhQYDVR0gBH4wfDA9BgkqhkiG9w0FBgEw
MDAuBggrBgEFBQcCARYiaHR0cHM6Ly9yZXBvc2l0b3J5LnRydXN0LnRlbGlhLmNvbTA7BgcqhXAj
AgEBMDAwLgYIKwYBBQUHAgEWImh0dHBzOi8vcmVwb3NpdG9yeS50cnVzdC50ZWxpYS5jb20wcAYD
VR0fBGkwZzBloGOgYYZfaHR0cDovL3d3dy5yc2FzZWN1cml0eS5jb20vcHJvZHVjdHMva2Vvbi9y
ZXBvc2l0b3J5L2NlcnRpZmljYXRlX3N0YXR1cy9SU0FfU2VjdXJpdHlfMjA0OF92My5DUkwwDgYD
VR0PAQH/BAQDAgEGMA0GCSqGSIb3DQEBBQUAA4IBAQAEXpos2CnIm7/872ytSrEHWZgvhOUEkUm2
5PWf/XkWko41TaL9vIS1S6AdWChNqWmnYiS7GfaIiDM9s1D6K7hidWBDOm46bNdM3ZwhMyDCfkDJ
SgeJ0w+7YmjvChu7gWqDZCsbtZ5gA1ixCTdDnuZB67JGSPGW6r73coraDP8diOpiQouMvM6bKuTP
BH/1poLccsUxsKgrQ23JC9LWCRb8cYHkZjXFH1K44TsIl5Lne2oT0JI3pwdA2v6jO4p/OLHntP+n
pjwPbedMPUZkDYCkd3LSxj8c3JTxtA8SlPCtIHE1hh65xihg1JRIliSphrqr9kbfwHdeVxPdOI5G
tDYPMYICEjCCAg4CAQEwTTA5MREwDwYDVQQKDAhFcmljc3NvbjEkMCIGA1UEAwwbRXJpY3Nzb24g
TkwgSW5kaXZpZHVhbCBDQTAxAhAhVsFUBw1ddjP0q9Mjb9LGMAkGBSsOAwIaBQCgggEbMBgGCSqG
SIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMTExNjE1MTEyN1owIwYJKoZI
hvcNAQkEMRYEFAGYixmm054wFExrzp/cDrA9M4+2MFwGCSsGAQQBgjcQBDFPME0wOTERMA8GA1UE
CgwIRXJpY3Nzb24xJDAiBgNVBAMMG0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMQIQIVbBVAcN
XXYz9KvTI2/SxjBeBgsqhkiG9w0BCRACCzFPoE0wOTERMA8GA1UECgwIRXJpY3Nzb24xJDAiBgNV
BAMMG0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMQIQIVbBVAcNXXYz9KvTI2/SxjANBgkqhkiG
9w0BAQEFAASBgDI2GQ7V0j0nNWy8IZstGpCcX0UWYWRphpS7hYgzNaNgSJxdxgEtduXIVHDw/bb0
Ax9G/T9GLetN/3pCLOsN8hWSQJW00c5hAyUGT1n1ojUorrEsXCo/8CuccbLRhKY9G2UlkmVGYsoQ
RF2Heb2hpmUXVl+7XACpmwvdd8lburXEAAAAAAAA

--Apple-Mail-65--448296991--

From cpignata@cisco.com  Wed Nov 16 07:51:31 2011
Return-Path: <cpignata@cisco.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7855911E8094 for <homenet@ietfa.amsl.com>; Wed, 16 Nov 2011 07:51:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level: 
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GlbnfMqK-Fnm for <homenet@ietfa.amsl.com>; Wed, 16 Nov 2011 07:51:30 -0800 (PST)
Received: from av-tac-rtp.cisco.com (hen.cisco.com [64.102.19.198]) by ietfa.amsl.com (Postfix) with ESMTP id 973C021F9509 for <homenet@ietf.org>; Wed, 16 Nov 2011 07:51:30 -0800 (PST)
X-TACSUNS: Virus Scanned
Received: from chook.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-rtp.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id pAGFpTmj027468 for <homenet@ietf.org>; Wed, 16 Nov 2011 10:51:29 -0500 (EST)
Received: from [64.102.157.21] (dhcp-64-102-157-21.cisco.com [64.102.157.21]) by chook.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id pAGFpTva010151;  Wed, 16 Nov 2011 10:51:29 -0500 (EST)
Message-ID: <4EC3DC04.2020409@cisco.com>
Date: Wed, 16 Nov 2011 10:51:32 -0500
From: Carlos Pignataro <cpignata@cisco.com>
Organization: cisco Systems, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.24) Gecko/20100228 Thunderbird/2.0.0.24 Mnenhy/0.7.6.0
MIME-Version: 1.0
To: Acee Lindem <acee.lindem@ericsson.com>
References: <CAKD1Yr3uSsNP4avZBdQE7YxFd7D_KOXBOCsfaRfvnWhJoLoY9Q@mail.gmail.com> <B3BE775A-4EBB-4C17-9EDC-7B9AFCB8867E@ericsson.com> <CAKD1Yr0MFdyBopr0E0WiebLSZ+M2J9vAi1U6b66VxhziE2XJpw@mail.gmail.com> <FF6FB9A0-9F91-4658-A265-BA200A0858AF@ericsson.com> <4EC29D17.10302@cisco.com> <6A2F0A68-5D4F-4742-A95F-18688525D6B7@ericsson.com> <D4EF568D-2AFF-4212-B6C0-960DE0673449@cisco.com> <B350DA39-4784-4AF5-9E2F-CBD388980CB5@ericsson.com>
In-Reply-To: <B350DA39-4784-4AF5-9E2F-CBD388980CB5@ericsson.com>
X-Enigmail-Version: 1.3.3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: "homenet@ietf.org" <homenet@ietf.org>, Jari Arkko <jari.arkko@piuha.net>, Lorenzo Colitti <lorenzo@google.com>
Subject: Re: [homenet] Comments on draft-acee-ospf-ospfv3-autoconfig-00
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 16 Nov 2011 15:51:31 -0000

Hi, Acee,

On 11/16/2011 10:11 AM, Acee Lindem wrote:
> Hi Carlos, 
>
> On Nov 15, 2011, at 10:34 PM, Carlos Pignataro (cpignata) wrote:
>
>> Hi Acee,
>>
>> On Nov 15, 2011, at 1:39 PM, "Acee Lindem" <acee.lindem@ericsson.com> wrote:
>>
>>> Hi Carlos,
>>>
>>> On Nov 15, 2011, at 12:10 PM, Carlos Pignataro wrote:
>>>
>>>> Hi Acee,
>>>>
>>>> On 11/14/2011 10:11 PM, Acee Lindem wrote:
>>>>> On Nov 14, 2011, at 9:46 PM, Lorenzo Colitti wrote:
>>>>>
>>>>>> On Tue, Nov 15, 2011 at 10:25, Acee Lindem <acee.lindem@ericsson.com
>>>>>> <mailto:acee.lindem@ericsson.com>> wrote:
>>>>>>
>>>>>>> 1. I think the OSPFv3 router ID should not be based on the MAC
>>>>>>  address because that will encourage people to assume it's unique
>>>>>>  "most of the time". I think we should just make it a pseudo-random
>>>>>>  number so it's clear that uniqueness is only guaranteed by
>>>>>>  collision detection and that collision detection needs to be robust.
>>>>>>
>>>>>>  The draft requires duplicate Router-ID detection and resolution. I
>>>>>>  don't think that the fact that a portion of the MAC address is
>>>>>>  used as a first try is reason for this detection/resolution not to
>>>>>>  be implemented or tested.
>>>>>>
>>>>>>
>>>>>> In my experience, giving people something that works "most of the
>>>>>> time" will cause the cases where it doesn't work to break. I think
>>>>>> it's better to explicitly provide no guarantees of uniqueness to make
>>>>>> it clear that collision detection needs to be robust. 
>>>>> In the OSPF WG, the fact that a mechanism is specified implies that it
>>>>> is required to be robust. 
>>>>>
>>>>>> Also, if we rely on collision detection, then what's the advantage of
>>>>>> using the MAC address? We might as well as make it random all the time
>>>>>> - that probably has a lower chance of collision anyway.
>>>>> I can't disagree with this argument and think we could go with a
>>>>> psuedo-random number seeded with a hash on the hardware fingerprint as
>>>>> the first try for router-id. 
>>>>>
>>>> As a side note, what's your opinion on citing and suggesting/requiring
>>>> <http://tools.ietf.org/html/rfc5642#section-4> for manageability?
>>> I think the dynamic host-name is less applicable in an auto-configured routing domain than other domains. In the auto-configured routing domain, you hope that little monitoring, debugging, or interaction is required. 
>> I agree that a goal is for less monitoring and interaction in this deployment model -- however sometimes less troubleshooting is aspirational, and debugging cannot be avoided :-) for those cases, a human-parseable node string is quite handy (especially when with pseudo-random -- potentially changing on reload or electrical hiccup (?) -- router-ids).  Thinking aloud a bit as I see both sides; but acknowledging that a stable node reference can help in troubleshooting (if/when required)
> If the router has little to no configuration, from where would the dynamic host name originate?

There is a bit of a potential chicken-egg, but (to not answer and
instead ask more generically, sorry) is a homenet requirement to have
local name services for all devices?

Thanks,

-- Carlos.

> Thanks,
> Acee
>
>
>> Thanks!
>>
>> Carlos P.
>>
>>> Thanks,
>>> Acee
>>>
>>>
>>>
>>>> Thanks,
>>>>
>>>> -- Carlos.
>>>>
>>>>>>  I think you mean virtual links. They are definitely not needed in
>>>>>>  the auto-configured environment as they are for providing a
>>>>>>  backbone path through a transit area and the OSPFv3
>>>>>>  auto-configured routing domain assumes only a backbone area.
>>>>>>
>>>>>>
>>>>>> Yes, virtual links. Do we need to state explicitly that they cannot
>>>>>> exist and are not supported?
>>>>> Since the auto-configured routing domain is area 0 only, it is explicit. 
>>>>>
>>>>>>
>>>>>>> 3. Can we use normal LSAs to detect collisions? One idea would
>>>>>>  be "if you see your own router ID in the list of neighbours of a
>>>>>>  network LSA or router LSA, then there is a collision". Will that
>>>>>>  work? If so we wouldn't need the hardware fingerprint at all.
>>>>>>
>>>>>>  No. In an arbitrary topology, A router with a duplicate router-id
>>>>>>  can be multiple hops away.
>>>>>>
>>>>>>
>>>>>> Yes, but router and network LSAs are flooded, so you'll hear them
>>>>>> regardless of whether your duplicate is multiple hops away, no?
>>>>> Both OSPFv3 and OSPFv2 would consider an unrecognized self-originated
>>>>> LSA, i.e. having our Route-ID, as a stale LSA and purge it. This is a
>>>>> very basic mechanism of OSPF. I'd rather use a separate mechanism for
>>>>> duplicate Router-ID detection. I considered techniques involving the
>>>>> encoding some additional information in the Router-LSA but these all
>>>>> seemed to be hacked. 
>>>>>
>>>>>
>>>>>>
>>>>>>  If the pre-shared key is hard-coded, it is no better than the
>>>>>>  OSPFv3 Interface Instance ID that is specified to prevent
>>>>>>  inadvertent adjacencies with routers not supporting the
>>>>>>  auto-configuration. If configuration of a pre-shared key is
>>>>>>  required, you no longer have auto-configuration.
>>>>>>
>>>>>>
>>>>>> Sorry, that wasn't clear. What I meant to say is that we should pick
>>>>>> one scheme (e.g., HMAC-SHA) and stick to it; we shouldn't support
>>>>>> multiple schemes as that will lead to interoperability issues for
>>>>>> devices that use one scheme and devices that use another scheme.
>>>>> The OSPFv3 Instance ID is part of the base OSPFv3 specification and I
>>>>> think it is a very good mechanism to prevent inadvertent adjacencies. If
>>>>> we need real authentication, we'll need a pre-shared key. I don't see
>>>>> any advantage of authentication with a well-known pre-shared key to
>>>>> prevent inadvertent adjacencies. 
>>>>>
>>>>> Thanks for the comments,
>>>>> Acee 
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> 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
>> _______________________________________________
>> homenet mailing list
>> homenet@ietf.org
>> https://www.ietf.org/mailman/listinfo/homenet

From mcr@sandelman.ca  Wed Nov 16 09:16:00 2011
Return-Path: <mcr@sandelman.ca>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00D5621F94CD for <homenet@ietfa.amsl.com>; Wed, 16 Nov 2011 09:16:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level: 
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[AWL=0.047,  BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j8gTS5hHfJyq for <homenet@ietfa.amsl.com>; Wed, 16 Nov 2011 09:15:58 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id D5C8D21F94C6 for <homenet@ietf.org>; Wed, 16 Nov 2011 09:15:58 -0800 (PST)
Received: from marajade.sandelman.ca (unknown [132.213.238.4]) by relay.sandelman.ca (Postfix) with ESMTPS id 60C4F343E9; Wed, 16 Nov 2011 12:14:28 -0500 (EST)
Received: by marajade.sandelman.ca (Postfix, from userid 179) id 3ECCF98CB5; Wed, 16 Nov 2011 12:15:34 -0500 (EST)
Received: from marajade.sandelman.ca (localhost [127.0.0.1]) by marajade.sandelman.ca (Postfix) with ESMTP id 377B298CB2; Wed, 16 Nov 2011 12:15:34 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ca>
To: homenet@ietf.org
In-Reply-To: <CA+XPzSaeg=pqmdSVXr+BQvS2D0+iVqN-q7e4dJoUtA=eA38vGA@mail.gmail.com>
References: <DCC302FAA9FE5F4BBA4DCAD46569377914518AFAE5@PRVPEXVS03.corp.twcable.com> <4EB583C8.5030907@piuha.net> <13027.1320680393@marajade.sandelman.ca> <BDF2740C082F6942820D95BAEB9E1A845A9789@XMB-AMS-108.cisco.com> <CA+XPzSY8cC_PyhcMNqhk4+B6tghp8Dpy2-3aMPZmyVRP=AWnaA@mail.gmail.com> <3512.1321317664@marajade.sandelman.ca> <CA+XPzSaeg=pqmdSVXr+BQvS2D0+iVqN-q7e4dJoUtA=eA38vGA@mail.gmail.com>
X-Mailer: MH-E 8.1; nmh 1.3-dev; XEmacs 21.4 (patch 22)
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Wed, 16 Nov 2011 12:15:34 -0500
Message-ID: <32238.1321463734@marajade.sandelman.ca>
Sender: mcr@sandelman.ca
Cc: Guillaume Habault <guillaume.habault@gmail.com>
Subject: Re: [homenet] more comments on draft-arkko-homenet-prefix-assignment
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 16 Nov 2011 17:16:00 -0000

--=-=-=
Content-Transfer-Encoding: quoted-printable


>>>>> "Guillaume" =3D=3D Guillaume Habault <guillaume.habault@gmail.com> wr=
ites:
    Guillaume> the host select the appropriate address, the routing
    Guillaume> protocol may route the message to the wrong Customer Edge
    Guillaume> Router (especially if we are in the case where there is
    Guillaume> more than one Customer Edge Router in the home network.

    >> We have assumed that the home gateways will cooperate and provide
    >> source address routing, making sure that packets are routed out
    >> the link which can accept that source address.

    Guillaume> To summarize and to be sure I get what you are planning
    Guillaume> to do, you will use a "normal" routing in the home
    Guillaume> network. Then, home gateways will check the source
    Guillaume> address of any packet coming and redirect it to the right
    Guillaume> home gateways if the source address is not the good one
    Guillaume> (just to be sure on what you mean by cooperate), is that
    Guillaume> right?  If so, do you planned to have tunnels between

So, go to Fred Baker's slides from yesterday:
    http://www.ietf.org/proceedings/82/slides/homenet-8.pptx
(and http://junk.sandelman.ca/junk/ietf82/homenet-8.pdf)
slide "Multihoming"

I think that it's called case 4 in the documents....
    draft-chown-homenet-arch-01
    figure 4 on page 11.

If CPERouter 2 (the right hand-one), receives a packet with a source
address which it knows (due to watching RAs and/or zOSPF) actually=20
belongs to Server Provider A, then instead of handing the packet
up to Service Provider B (where it likely gets dropped), it will
instead forward the packet to Router 1.=20=20

This forward is easy to do if Router 1 and Router 2 are on the same
layer-2 link.  I don't think we've considered the case where they are
not on the same link.

We have said that for cases where there are multiple layers of routers,
that the other layers of router MUST pick the right exit router based
upon source IP, so I think that as long as Router 2 can find a path to
Router 1, it can work even when Router 1 and Router 2 are not on the
same link.

The source-address redirect is necessary only so that we can avoid
imposing a new requirement on the hosts which might be on that layer-2
link.

    Guillaume> If so, do you planned to have tunnels between
    Guillaume> home gateways ? Are we sure that ISPs behind the home
    Guillaume> gateway will accept to cooperate with each other (I said
    Guillaume> that because in France, home gateways are mainly
    Guillaume> given/lend by ISPs, and i'm not sure they will be willing
    Guillaume> to share something with another ISP)?

No, there are no tunnels across the Internet.
The traffic is redirected within the home.

If the ISP provided home router can't speak homenet, then I guess it
won't get the right logo on it.

=2D-=20
]       He who is tired of Weird Al is tired of life!           |  firewall=
s  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net archit=
ect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device dri=
ver[
   Kyoto Plus: watch the video <http://www.youtube.com/watch?v=3Dkzx1ycLXQS=
E>
	               then sign the petition.=20



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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iQEVAwUATsPvtYCLcPvd0N1lAQKWPQf/YhhtzQSuxTWDKOyI1f+D0aUIoo0uclO9
ubJcsdJbZGg0HKv9za62ZwPaR3Eae6tgEcThTotuHgFgz+YDen+smtVI1EjCAhjv
kbggNSXf/sJCvnycUNclF8BsJpdo41ODA9ntEfCWttMFLYtOtFOGlYAvtL5Sr+Au
N53bRvYZw4T7/eClIeu0/OhNE98WPiTSM9crG3Uzgy9Gx+DX+jPhn7q2ppHqqpOA
4ilOJ1T7NRs6NVBiqzkYhe1LSlO9mEB/8T8UA/myEviT2Jv53R+dFWpsKiAWSTIk
U3gSLjmeq8+loVii4ntDy/cglxOB2xox9gL01HAUJSZXk2vcJQhqWw==
=6cgN
-----END PGP SIGNATURE-----
--=-=-=--

From mcr@sandelman.ca  Wed Nov 16 17:28:18 2011
Return-Path: <mcr@sandelman.ca>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F8F41F0C69 for <homenet@ietfa.amsl.com>; Wed, 16 Nov 2011 17:28:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.72
X-Spam-Level: 
X-Spam-Status: No, score=-1.72 tagged_above=-999 required=5 tests=[AWL=0.234,  BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5Re-QB42+dpV for <homenet@ietfa.amsl.com>; Wed, 16 Nov 2011 17:28:17 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id BD3971F0C56 for <homenet@ietf.org>; Wed, 16 Nov 2011 17:28:17 -0800 (PST)
Received: from marajade.sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by relay.sandelman.ca (Postfix) with ESMTPS id 35E77343CB for <homenet@ietf.org>; Wed, 16 Nov 2011 20:26:50 -0500 (EST)
Received: by marajade.sandelman.ca (Postfix, from userid 179) id 8D0B398CB5; Wed, 16 Nov 2011 20:28:17 -0500 (EST)
Received: from marajade.sandelman.ca (localhost [127.0.0.1]) by marajade.sandelman.ca (Postfix) with ESMTP id 8822198CB2 for <homenet@ietf.org>; Wed, 16 Nov 2011 20:28:17 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ca>
To: "homenet@ietf.org" <homenet@ietf.org>
In-Reply-To: <46CB823A-3C53-4C32-A33C-498CA6413448@fugue.com>
References: <4EC1D206.2070303@gmail.com> <3C716203-8579-41EA-98CE-6DC3BE9261D8@fugue.com> <FC520CA0-BAA4-4309-A878-CB40308F2562@cisco.com> <09215FB7-EA7A-4D9D-8772-737B79CBBD20@fugue.com> <4EC32B76.8080706@riw.us> <7DADF53B-56CA-47CC-BBDA-34300EE4D22D@fugue.com> <7D0889B6-7769-4F74-996D-08CDA02B3670@cisco.com> <84FD521E-D48C-41C9-935B-9B4695FB658D@cisco.com> <489BE869-79F9-40FC-96B1-6A190620B4CA@cisco.com> <7F630AC9-A369-48B8-BD8F-684C0AC1DDDA@fugue.com> <72EB15CA-CAB4-4A50-BAB4-E60176109AF5@cisco.com> <E34DB847-4FC9-4982-A609-B80707F61E45@fugue.com> <E5723B4B-BDE4-47F4-B560-1165F713D5E2@cisco.com> <46CB823A-3C53-4C32-A33C-498CA6413448@fugue.com>
X-Mailer: MH-E 8.1; nmh 1.3-dev; XEmacs 21.4 (patch 22)
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Wed, 16 Nov 2011 20:28:17 -0500
Message-ID: <17953.1321493297@marajade.sandelman.ca>
Sender: mcr@sandelman.ca
Subject: Re: [homenet] draft-baker-homenet-prefix-assignment
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 17 Nov 2011 01:28:18 -0000

--=-=-=
Content-Transfer-Encoding: quoted-printable


Is there some reason that the flooding mechanism can't distribute the
list of edge CPE routers, and then DHCPv6 can be used in unicast
request/reply to ask those CPE routers for things.

(I would even wonder if the CPE routers shouldn't be identified by their
ULA rather than self-identifying by the address in the subnet the deal with)

This is how I imagined the DHCPv6 PD mechanism working before
draft-chakrabarti-homenet-prefix-alloc-01 was written, which imagined a
strict hierarchal tree.

=2D-=20
]       He who is tired of Weird Al is tired of life!           |  firewall=
s  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net archit=
ect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device dri=
ver[
   Kyoto Plus: watch the video <http://www.youtube.com/watch?v=3Dkzx1ycLXQS=
E>
	               then sign the petition.=20


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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iQEVAwUATsRjMYCLcPvd0N1lAQJ32wgAnXEbtDn10O/ARfJhpXXK5qWALN+oq4tY
bb8X4LlmHWicygulmHMRItx4+o9snWa1ayG0g85Fu21EkeT32vxFImGKQ8vPNbcs
WBzV+Q4h/oC54bR7F0W5w6pvvSE4y0qLT6NJP97kekbJFS8srqcjL+sUoCy8xM4B
Cb4WFOziJRVqRz0r7Lm+M1VJQkb3mah5ybjyKnBp40+SjaO6hTEQC++4Eae7KIR8
IFy1JAnaA4kxRcR/ohu4KZHZ9fZKXjhLAKQrCCjROGEEYdGBE8b61Fg3s/rRs62h
ghVc9APSAnq4REVdB8FzLmrI+L+JHjigjAIMMx4IDnrd2Yx049bpFw==
=1n2U
-----END PGP SIGNATURE-----
--=-=-=--

From leo.liubing@huawei.com  Wed Nov 16 18:43:03 2011
Return-Path: <leo.liubing@huawei.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 21C2221F8B10; Wed, 16 Nov 2011 18:43:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.156
X-Spam-Level: 
X-Spam-Status: No, score=-4.156 tagged_above=-999 required=5 tests=[AWL=-1.042, BAYES_00=-2.599, CN_BODY_80=0.532, J_CHICKENPOX_13=0.6, J_CHICKENPOX_36=0.6, MIME_BASE64_TEXT=1.753, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6ptxDcg3kNmX; Wed, 16 Nov 2011 18:43:02 -0800 (PST)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id 461AC11E80B0; Wed, 16 Nov 2011 18:43:02 -0800 (PST)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LUS000VQA5EWV@szxga05-in.huawei.com>; Thu, 17 Nov 2011 10:41:38 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LUS006GYA5E9N@szxga05-in.huawei.com>; Thu, 17 Nov 2011 10:41:38 +0800 (CST)
Received: from szxeml206-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA)	with ESMTP id AFA84953; Thu, 17 Nov 2011 10:41:37 +0800
Received: from SZXEML403-HUB.china.huawei.com (10.82.67.35) by szxeml206-edg.china.huawei.com (172.24.2.58) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 17 Nov 2011 10:41:32 +0800
Received: from SZXEML509-MBS.china.huawei.com ([169.254.2.220]) by szxeml403-hub.china.huawei.com ([10.82.67.35]) with mapi id 14.01.0323.003; Thu, 17 Nov 2011 10:36:47 +0800
Date: Thu, 17 Nov 2011 02:36:47 +0000
From: "Leo Liu(bing)" <leo.liubing@huawei.com>
X-Originating-IP: [172.24.2.41]
To: "renum@ietf.org" <renum@ietf.org>, "homenet@ietf.org" <homenet@ietf.org>,  "v6ops@ietf.org" <v6ops@ietf.org>
Message-id: <8AE0F17B87264D4CAC7DE0AA6C406F4523668C32@szxeml509-mbs.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset=gb2312
Content-language: zh-CN
Content-transfer-encoding: base64
Accept-Language: zh-CN, en-US
Thread-topic: [Homenet][6renum][v6ops] ULA discussion
Thread-index: Acyk0cBJgV/lCELMRGui5tWz0sirpA==
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-CFilter-Loop: Reflected
Subject: [homenet] [Homenet][6renum][v6ops] ULA discussion
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 17 Nov 2011 02:43:03 -0000

SGksIGFsbA0KSW4gVHVlc2RheSdzIEhvbWVuZXQgV0cgbWVldGluZywgdGhlcmUgd2FzIGEgYnJp
ZWYgZGlzY3Vzc2lvbiBhYm91dCB3aGV0aGVyIHRvIHVzZSBVTEEsIGJ1dCBubyBjb25zZW5zdXMg
YWNoaWV2ZWQuDQoNCkl0IHdhcyBxdWl0ZSB0aGUgc2FtZSBzaXR1YXRpb24gYXMgaW4gNnJlbnVt
IFdHLiBXZSB1c2VkIHRvIGRpc2N1c3MgVUxBIHVzYWdlIHRvIGF2b2lkIHNvbWUgcmVudW1iZXJp
bmcsIGJ1dCB0aGVyZSdzIG5vIGNvbnNlbnN1cyB5ZXQuIEFzIHRoZSBjaGFpciBzdWdnZXN0ZWQs
IHdlIHRob3VnaHQgdGhlIFVMQSB0b3BpYyBpbnZvbHZpbmcgY29tbW9uIElQdjYgZGVwbG95bWVu
dCBjb25zaWRlcmF0aW9uLiBGb3IgZXhhbXBsZSwgd2hldGhlciBVTEEtb25seStOQVQgaXMgYWNj
ZXB0YWJsZSBvciBub3Q7IFVMQStHbG9iYWwgbXVsdGlwbGUgYWRkcmVzc2luZyBjb25zaWRlciBy
ZWNvbW1lbmRlZCBhcyBwcm92aWRpbmcgc3RhYmxlIGxvY2FsIGNvbW11bmljYXRpb24sIG9yIG5v
dCByZWNvbW1lbmRlZCBhcyBhZGRpbmcgdG9vIG11Y2ggb3BlcmF0aW9uYWwgY29tcGxleGl0eS4N
Cg0KU28gd2UgcHJvZHVjZWQgYSBkcmFmdCBpbiB2Nm9wcyBpbnRlbmQgdG8gZGlzY3VzcyB0aGUg
dG9waWMgYW1vbmcgbW9yZSBwZW9wbGUuDQpJZiB5b3UgY2FyZSBhYm91dCBVTEEsIGhvcGUgeW91
IGNhbiBqb2luIHRoZSBkaXNjdXNzaW9uIGluIHY2b3BzIHRoaXMgYWZ0ZXJub29uKFRodXJzZGF5
KSBhdCAxMzowMC4gKFVMQSB3aWxsIGJlIHRoZSBmaXJzdCB0byBiZSBwcmVzZW50ZWQpDQoNClRo
YW5rcywNCkJpbmcNCg0KVGhlIHNsaWRlc6O6aHR0cDovL3d3dy5pZXRmLm9yZy9wcm9jZWVkaW5n
cy84Mi9zbGlkZXMvdjZvcHMtOC5wcHQgIA0Ko6hJdCBpcyBhIGxpdHRsZSBkaWZmZXJlbnQgZnJv
bSB0aGUgb3JpZ2luYWwgZHJhZnQgc2luY2Ugd2UgaW5jbHVkZWQgc29tZSBmZWVkYmFjayBhZnRl
ciBzdWJtaXR0aW5nIHRoZSAwMCB2ZXJzaW9uo6kNClRoZSBkcmFmdDogaHR0cDovL3Rvb2xzLmll
dGYub3JnL2h0bWwvZHJhZnQtbGl1LXY2b3BzLXVsYS11c2FnZS1hbmFseXNpcy0wMC5odG1s

From mark@townsley.net  Wed Nov 16 21:12:49 2011
Return-Path: <mark@townsley.net>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30D631F0C42; Wed, 16 Nov 2011 21:12:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.482
X-Spam-Level: 
X-Spam-Status: No, score=-2.482 tagged_above=-999 required=5 tests=[AWL=-0.616, BAYES_00=-2.599, CN_BODY_80=0.532, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, J_CHICKENPOX_36=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I5iEMZnG4X5U; Wed, 16 Nov 2011 21:12:48 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 1F9C421F95BF; Wed, 16 Nov 2011 21:12:48 -0800 (PST)
Received: by ywt34 with SMTP id 34so674259ywt.31 for <multiple recipients>; Wed, 16 Nov 2011 21:12:47 -0800 (PST)
Received: by 10.101.138.12 with SMTP id q12mr4708898ann.75.1321506767712; Wed, 16 Nov 2011 21:12:47 -0800 (PST)
Received: from ?IPv6:2001:df8::16:226:bbff:fe1a:79b4? ([2001:df8:0:16:226:bbff:fe1a:79b4]) by mx.google.com with ESMTPS id i31sm70802756anm.19.2011.11.16.21.12.45 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 16 Nov 2011 21:12:46 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-23--401480816
From: Mark Townsley <mark@townsley.net>
In-Reply-To: <8AE0F17B87264D4CAC7DE0AA6C406F4523668C32@szxeml509-mbs.china.huawei.com>
Date: Thu, 17 Nov 2011 12:11:42 +0800
Message-Id: <CAA1F552-D252-47C7-94E1-9E595B2B5947@townsley.net>
References: <8AE0F17B87264D4CAC7DE0AA6C406F4523668C32@szxeml509-mbs.china.huawei.com>
To: "Leo Liu(bing)" <leo.liubing@huawei.com>
X-Mailer: Apple Mail (2.1084)
Cc: "homenet@ietf.org" <homenet@ietf.org>, "renum@ietf.org" <renum@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>
Subject: Re: [homenet] [renum] [Homenet][6renum][v6ops] ULA discussion
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 17 Nov 2011 05:12:49 -0000

--Apple-Mail-23--401480816
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=GB2312


"ULA isolated" in 3.1.1 as well as 3.1.2 "ULA Coexist with Global" is =
important to homenet.=20

It is equally important for "ULA connected" described in section 3.1.1 =
to *not* exist, or if it does for the devices in the homenet to be =
readily aware that the ULA is "connected". See Chris Palmer's =
presentation here for more info: =
http://www.ietf.org/proceedings/81/slides/homenet-5.pdf (I have been =
promised a draft as well - Chris?).=20

- Mark

On Nov 17, 2011, at 10:36 AM, Leo Liu(bing) wrote:

> Hi, all
> In Tuesday's Homenet WG meeting, there was a brief discussion about =
whether to use ULA, but no consensus achieved.
>=20
> It was quite the same situation as in 6renum WG. We used to discuss =
ULA usage to avoid some renumbering, but there's no consensus yet. As =
the chair suggested, we thought the ULA topic involving common IPv6 =
deployment consideration. For example, whether ULA-only+NAT is =
acceptable or not; ULA+Global multiple addressing consider recommended =
as providing stable local communication, or not recommended as adding =
too much operational complexity.
>=20
> So we produced a draft in v6ops intend to discuss the topic among more =
people.
> If you care about ULA, hope you can join the discussion in v6ops this =
afternoon(Thursday) at 13:00. (ULA will be the first to be presented)
>=20
> Thanks,
> Bing
>=20
> The slides=A3=BAhttp://www.ietf.org/proceedings/82/slides/v6ops-8.ppt =20=

> =A3=A8It is a little different from the original draft since we =
included some feedback after submitting the 00 version=A3=A9
> The draft: =
http://tools.ietf.org/html/draft-liu-v6ops-ula-usage-analysis-00.html
> _______________________________________________
> renum mailing list
> renum@ietf.org
> https://www.ietf.org/mailman/listinfo/renum


--Apple-Mail-23--401480816
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=GB2312

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><br></div><div>"ULA isolated" in 3.1.1 as well as 3.1.2 "ULA =
Coexist with Global" is important to =
homenet.&nbsp;</div><div><br></div><div>It is equally important for "ULA =
connected" described in section 3.1.1 to *not* exist, or if it does for =
the devices in the homenet to be readily aware that the ULA is =
"connected". See&nbsp;Chris Palmer's presentation here for more =
info:&nbsp;<a =
href=3D"http://www.ietf.org/proceedings/81/slides/homenet-5.pdf">http://ww=
w.ietf.org/proceedings/81/slides/homenet-5.pdf</a>&nbsp;(I have been =
promised a draft as well - Chris?).&nbsp;</div><div><br></div><div>- =
Mark</div><div><br></div><div><div>On Nov 17, 2011, at 10:36 AM, Leo =
Liu(bing) wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div>Hi, all<br>In Tuesday's Homenet WG meeting, there was =
a brief discussion about whether to use ULA, but no consensus =
achieved.<br><br>It was quite the same situation as in 6renum WG. We =
used to discuss ULA usage to avoid some renumbering, but there's no =
consensus yet. As the chair suggested, we thought the ULA topic =
involving common IPv6 deployment consideration. For example, whether =
ULA-only+NAT is acceptable or not; ULA+Global multiple addressing =
consider recommended as providing stable local communication, or not =
recommended as adding too much operational complexity.<br><br>So we =
produced a draft in v6ops intend to discuss the topic among more =
people.<br>If you care about ULA, hope you can join the discussion in =
v6ops this afternoon(Thursday) at 13:00. (ULA will be the first to be =
presented)<br><br>Thanks,<br>Bing<br><br>The =
slides=A3=BAhttp://www.ietf.org/proceedings/82/slides/v6ops-8.ppt =
&nbsp;<br>=A3=A8It is a little different from the original draft since =
we included some feedback after submitting the 00 version=A3=A9<br>The =
draft: <a =
href=3D"http://tools.ietf.org/html/draft-liu-v6ops-ula-usage-analysis-00.h=
tml">http://tools.ietf.org/html/draft-liu-v6ops-ula-usage-analysis-00.html=
</a><br>_______________________________________________<br>renum mailing =
list<br><a =
href=3D"mailto:renum@ietf.org">renum@ietf.org</a><br>https://www.ietf.org/=
mailman/listinfo/renum<br></div></blockquote></div><br></body></html>=

--Apple-Mail-23--401480816--

From mark@townsley.net  Thu Nov 17 02:16:33 2011
Return-Path: <mark@townsley.net>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0AAAD21F9BA2 for <homenet@ietfa.amsl.com>; Thu, 17 Nov 2011 02:16:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.299
X-Spam-Level: 
X-Spam-Status: No, score=-3.299 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7wErmwh7tNAb for <homenet@ietfa.amsl.com>; Thu, 17 Nov 2011 02:16:32 -0800 (PST)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 8391B21F9B9F for <homenet@ietf.org>; Thu, 17 Nov 2011 02:16:32 -0800 (PST)
Received: by ggnr5 with SMTP id r5so970429ggn.31 for <homenet@ietf.org>; Thu, 17 Nov 2011 02:16:32 -0800 (PST)
Received: by 10.236.116.98 with SMTP id f62mr7796665yhh.48.1321524992152; Thu, 17 Nov 2011 02:16:32 -0800 (PST)
Received: from [172.16.7.11] ([122.147.35.3]) by mx.google.com with ESMTPS id y1sm2426865anj.18.2011.11.17.02.16.31 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 17 Nov 2011 02:16:31 -0800 (PST)
From: Mark Townsley <mark@townsley.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Thu, 17 Nov 2011 18:16:28 +0800
Message-Id: <5EAB9925-C2C7-4431-A826-13EEC46CDADC@townsley.net>
To: "homenet@ietf.org Group" <homenet@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Subject: [homenet] Next steps
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 17 Nov 2011 10:16:33 -0000

Homenet,=20

We ran out of time in homenet this week and did not get a chance to put =
together a "next steps" suggestion to the WG. So, here it is in email.

First, we'd like to formally move draft-chown-homenet-arch-01 to =
draft-ietf-homenet-arch-00. This of course does not mean that the =
document is finished, just that this will be the document the working =
group will recognize as its collective work in progress until it becomes =
an RFC. If anyone has substantive objections to this, please let us know =
within the next week (i.e, by Nov 25).=20

Second, we'd like to reiterate our call for people who have a particular =
routing protocol that they believe would be a good candidate for =
application to the homenet problem space, please let the WG know via an =
Internet Draft submission. Reason being is that we have fewer homenet =
documents submitted thus far than we have heard chatter about in terms =
of possible solutions. Also, a routing solution was listed as one of our =
first deliverables when homenet was chartered.=20

Minutes of the meeting will be coming soon.

Thanks to all for your hard work,=20

- Mark & Ray




From fred@cisco.com  Thu Nov 17 02:38:56 2011
Return-Path: <fred@cisco.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82E2D21F9B8E for <homenet@ietfa.amsl.com>; Thu, 17 Nov 2011 02:38:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.222
X-Spam-Level: 
X-Spam-Status: No, score=-109.222 tagged_above=-999 required=5 tests=[AWL=0.777, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o7Q4QmKPCbCI for <homenet@ietfa.amsl.com>; Thu, 17 Nov 2011 02:38:55 -0800 (PST)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id 2524A21F9B6C for <homenet@ietf.org>; Thu, 17 Nov 2011 02:38:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=6241; q=dns/txt; s=iport; t=1321526335; x=1322735935; h=from:subject:date:references:to:message-id:mime-version: content-transfer-encoding; bh=+YSi1lAvxWkOhHrhDhD9bUpUXuGM8j37R2RqfqWIDX8=; b=gxIhRed1S8fO7j2IGf7gBUA/XcozYHNOvVyvWj7jM73yGF0TRJxkFB9m DV4o9vfoTU/XTeI0eny0RsU54eHlmZMqLbpC6jlyFnqh1eJrcSjNKkZRH aSwknN98KZr/17qUVLuM5Acg0gWptaAmu+3ZCO9LEusQefOdanSeOLi+5 Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAIvjxE5Io8US/2dsb2JhbABBAal+gQWBcgEBAQMBEgEnLRcLHAMBAhoCE00CCAYTGweHYJVqAZ4+hxMBgiBjBIgTjCKFO4xO
X-IronPort-AV: E=Sophos;i="4.69,526,1315180800"; d="scan'208";a="121893981"
Received: from bgl-core-3.cisco.com ([72.163.197.18]) by ams-iport-1.cisco.com with ESMTP; 17 Nov 2011 10:38:53 +0000
Received: from dhcp-4466.meeting.ietf.org (hkidc-vpn-client-233-100.cisco.com [10.75.233.100]) by bgl-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id pAHAc6KA029802 for <homenet@ietf.org>; Thu, 17 Nov 2011 10:38:52 GMT
Received: from [127.0.0.1] by dhcp-4466.meeting.ietf.org (PGP Universal service); Thu, 17 Nov 2011 18:38:52 +0800
X-PGP-Universal: processed; by dhcp-4466.meeting.ietf.org on Thu, 17 Nov 2011 18:38:52 +0800
From: Fred Baker <fred@cisco.com>
Date: Thu, 17 Nov 2011 18:38:52 +0800
References: <754008F3-6B2B-4DD1-B72B-EDE17A4FBF80@cisco.com>
To: "homenet@ietf.org Group" <homenet@ietf.org>
Message-Id: <8B1DA204-3629-4B42-8035-DAFFB480F058@cisco.com>
Mime-Version: 1.0 (Apple Message framework v1084)
X-Mailer: Apple Mail (2.1084)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: [homenet] Fwd: Major use cases for ULA
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 17 Nov 2011 10:38:56 -0000

FYI:

This is a note I sent to v6ops regarding ULAs, but as there is some =
discussion of them in Homenet, it make also be of interest here.

Begin forwarded message:

> From: Fred Baker <fred@cisco.com>
> Date: November 17, 2011 6:37:54 PM GMT+08:00
> To: draft-liu-v6ops-ula-usage-analysis@tools.ietf.org
> Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>
> Subject: Major use cases for ULA
>=20
> Trying to summarize at least my thoughts from the discussion this =
afternoon. Working group, tell me what I'm missing in this.
>=20
> First, as Jari noted from the mike, there is no case in which a ULA is =
required. If one is willing to only have connectivity in the link-local =
environment, one can communicate between two directly connected systems =
using a link-local address. If one has in the past had the use of a =
prefix allocated by someone else, but are right now not connected to the =
Internet, there is no harm in using that prefix even if it is expired. =
Reason: there will be no confusion. As soon as one reconnects, the =
expiration of the prefix needs to take effect, however.
>=20
> To my mind, there are three valid uses of a ULA. The choice of use =
cases center on the word "local".
>=20
> 1) if one is in a network that does not have service from someone that =
will allocate it a prefix and wants to either use addresses that are not =
link-local or addresses that will allow for routing, a ULA provides a =
way to generate a prefix for the purpose. One example of such an =
environment is a Smart Grid HAN in a home that doesn't have an ISP. To =
me, this is a textbook case for the use of a ULA.
>=20
> 2) if one is in a network that DOES have service from someone that =
will allocate it a prefix but wants to use addresses that are not in =
that prefix and are not routed anywhere else, a ULA can provide such a =
prefix. There are a number of possible examples.=20
>=20
> At Cisco, to pick one, we have a number of systems with names like =
http://wwwin.cisco.com - systems that offer no services outside Cisco =
but provide some interior service. There are at least two ways to =
implement that policy. One obvious one would be to put some ACL in the =
routers/firewalls at the edge of the network that drop traffic to or =
from those addresses. Another, which I would only want to implement in =
the presence of that firewall ACL, would be to not advertise the names =
outside the company in DNS (probably by implementing a split DNS). A =
third would be to give them ULA addresses, which are not advertised =
outside the company and are therefore something folks outside can't =
route to.
>=20
> Another example is the one I mentioned in RFC 6296; if you choose to =
use such a translator, you're going to need an interior prefix. That =
could be ULA or global. If it is global and you decide to change away =
from that carrier, you will have to renumber the network. If you find =
that scary, you might choose a ULA as your internal prefix.
>=20
> The key point is not "6296", nor is it "internal-only policy". It's =
"In my addressing plan, I want to use a *different* prefix that is not =
routed outside". If you have that policy, one of the options (and not =
the only option) would be to use a ULA.
>=20
> 3) If you have a special routing scenario, of which =
draft-baker-v6ops-b2b-private-routing is an example, for various reasons =
you might want to have routing that you control and is separate from =
other routing. In the b2b case, even though two companies each have at =
least one ISP, they might choose to ALSO use direct connectivity that =
only connects stated machines, such as a silicon foundry with client =
engineers that use it. A ULA provides a simple way to obtain such a =
prefix that would be used in accordance with an agreement between the =
parties.
>=20
>=20
>=20
> To my mind, the renumbering scenario is a red herring. Thomas Narten =
wanted desperately for me to put it into RFC 4192 as "A ULA could help =
when renumbering a network". However, it doesn't actually do so.
>=20
> Case 1) suppose I am now using prefix 2001:dba:1::/48 and want to =
change to 2001:dba:2:8000::/49. Suppose that I am offering a service =
(web, email, whatever) outside of my network. What RFC 4192 suggests is =
bringing up the two prefixes in parallel (eg, I am now using both =
2001:dba:1::/48 and 2001:dba:2:8000::/49 throughout my network), and =
then take the old one down. The effect: during some part of the =
procedure, my external services have first one address, then two =
addresses, and finally one, but the one is the new one. I completely =
changed my address space, but my service never went down.
>=20
> Case 2) suppose I am now using prefix 2001:dba:1::/48 and want to =
change to 2001:dba:2:8000::/49. Suppose that I am offering a service =
(web, email, whatever) outside of my network. What the ULA advocates =
suggest that I have a ULA up in parallel, either all the time or brought =
up for the purpose. I am in effect now using 2001:dba:1::/48 and the =
ULA. I now take down 2001:dba:1::/48, and either simultaneously or =
subsequently bring up 2001:dba:2:8000::/49. If I do the two =
sequentially, I have an interval in which my services are only reachable =
via the ULA; if I change them at the same time, the ULA allows me to =
maintain control of my network (my network management system and other =
internal uses can use it to access equipment and applications within my =
network), but the disrupted routing makes my services unavailable in =
either global prefix for some period of time. The effect: during some =
part of the procedure, the various systems in my network might have one, =
two, or three addresses, but during any period in which only the ULA has =
stable routing, my services are down as far as any external user is =
concerned.
>=20
> Hence, a ULA is helpful for folks within my own network, but does not =
help keep my externally-facing services running. To my small mind, that =
makes a ULA a nice fallback in case something gets screwed up, but it is =
not a renumbering solution. It fails to prevent a service outage during =
renumbering.


From Anders_Brandt@sigmadesigns.com  Thu Nov 17 02:57:08 2011
Return-Path: <Anders_Brandt@sigmadesigns.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0475921F99A7; Thu, 17 Nov 2011 02:57:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.105
X-Spam-Level: 
X-Spam-Status: No, score=0.105 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  J_CHICKENPOX_13=0.6, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 228Ol0-IGmqb; Thu, 17 Nov 2011 02:57:07 -0800 (PST)
Received: from CPH-EX1.sdesigns.com (unknown [195.215.56.171]) by ietfa.amsl.com (Postfix) with ESMTP id 5D63521F999C; Thu, 17 Nov 2011 02:57:06 -0800 (PST)
Received: from CPH-EX1.sdesigns.com ([192.168.10.36]) by cph-ex1 ([192.168.10.36]) with mapi id 14.01.0270.001; Thu, 17 Nov 2011 11:57:05 +0100
From: Anders Brandt <Anders_Brandt@sigmadesigns.com>
To: Fred Baker <fred@cisco.com>, "draft-liu-v6ops-ula-usage-analysis@tools.ietf.org" <draft-liu-v6ops-ula-usage-analysis@tools.ietf.org>
Thread-Topic: [v6ops] Major use cases for ULA
Thread-Index: AQHMpRV7q3uJbPTXJESRbtUav6pFZpWw4Ym3
Date: Thu, 17 Nov 2011 10:57:04 +0000
Message-ID: <03F31C213F2C6941BFDDBB4336E9E6CD0AB40668@cph-ex1>
References: <754008F3-6B2B-4DD1-B72B-EDE17A4FBF80@cisco.com>
In-Reply-To: <754008F3-6B2B-4DD1-B72B-EDE17A4FBF80@cisco.com>
Accept-Language: en-US, da-DK
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.10.38]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailman-Approved-At: Thu, 17 Nov 2011 06:13:04 -0800
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, "homenet@ietf.org" <homenet@ietf.org>
Subject: Re: [homenet] [v6ops] Major use cases for ULA
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 17 Nov 2011 10:58:50 -0000

May I suggest variant 1b) :

A home control installation with some powerline devices and some wireless d=
evices each part of a lighting control system that MUST ALWAYS work.
Both subnets are installed in autonomous fashion by two different technicia=
ns. Later, their border routers are interconnected via the homenet backbone=
.
We may argue if a ULA prefix is needed in the homenet backbone but both of =
the home control networks need ULA addresses

A: because the devices need stable addresses so that they know where to sen=
d On/Off commands to the other subnet without depending on DNS servers, etc=
.

B: because there is no infrastructure to coordinate the assignment of prefi=
xes in the two home control subnets

C: because LLNs often do use coordinated assignment of short link-layer add=
resses to get shorter frames and to improve header compression.
    These short link-layer would often lead to duplicate IPv6 addresses if =
in the same subnet.=20

Thanks,
  Anders Brandt

________________________________________
From: v6ops-bounces@ietf.org [v6ops-bounces@ietf.org] on behalf of Fred Bak=
er [fred@cisco.com]
Sent: Thursday, November 17, 2011 11:37
To: draft-liu-v6ops-ula-usage-analysis@tools.ietf.org
Cc: v6ops@ietf.org WG
Subject: [v6ops] Major use cases for ULA

Trying to summarize at least my thoughts from the discussion this afternoon=
. Working group, tell me what I'm missing in this.

First, as Jari noted from the mike, there is no case in which a ULA is requ=
ired. If one is willing to only have connectivity in the link-local environ=
ment, one can communicate between two directly connected systems using a li=
nk-local address. If one has in the past had the use of a prefix allocated =
by someone else, but are right now not connected to the Internet, there is =
no harm in using that prefix even if it is expired. Reason: there will be n=
o confusion. As soon as one reconnects, the expiration of the prefix needs =
to take effect, however.

To my mind, there are three valid uses of a ULA. The choice of use cases ce=
nter on the word "local".

1) if one is in a network that does not have service from someone that will=
 allocate it a prefix and wants to either use addresses that are not link-l=
ocal or addresses that will allow for routing, a ULA provides a way to gene=
rate a prefix for the purpose. One example of such an environment is a Smar=
t Grid HAN in a home that doesn't have an ISP. To me, this is a textbook ca=
se for the use of a ULA.

2) if one is in a network that DOES have service from someone that will all=
ocate it a prefix but wants to use addresses that are not in that prefix an=
d are not routed anywhere else, a ULA can provide such a prefix. There are =
a number of possible examples.

At Cisco, to pick one, we have a number of systems with names like http://w=
wwin.cisco.com - systems that offer no services outside Cisco but provide s=
ome interior service. There are at least two ways to implement that policy.=
 One obvious one would be to put some ACL in the routers/firewalls at the e=
dge of the network that drop traffic to or from those addresses. Another, w=
hich I would only want to implement in the presence of that firewall ACL, w=
ould be to not advertise the names outside the company in DNS (probably by =
implementing a split DNS). A third would be to give them ULA addresses, whi=
ch are not advertised outside the company and are therefore something folks=
 outside can't route to.

Another example is the one I mentioned in RFC 6296; if you choose to use su=
ch a translator, you're going to need an interior prefix. That could be ULA=
 or global. If it is global and you decide to change away from that carrier=
, you will have to renumber the network. If you find that scary, you might =
choose a ULA as your internal prefix.

The key point is not "6296", nor is it "internal-only policy". It's "In my =
addressing plan, I want to use a *different* prefix that is not routed outs=
ide". If you have that policy, one of the options (and not the only option)=
 would be to use a ULA.

3) If you have a special routing scenario, of which draft-baker-v6ops-b2b-p=
rivate-routing is an example, for various reasons you might want to have ro=
uting that you control and is separate from other routing. In the b2b case,=
 even though two companies each have at least one ISP, they might choose to=
 ALSO use direct connectivity that only connects stated machines, such as a=
 silicon foundry with client engineers that use it. A ULA provides a simple=
 way to obtain such a prefix that would be used in accordance with an agree=
ment between the parties.



To my mind, the renumbering scenario is a red herring. Thomas Narten wanted=
 desperately for me to put it into RFC 4192 as "A ULA could help when renum=
bering a network". However, it doesn't actually do so.

Case 1) suppose I am now using prefix 2001:dba:1::/48 and want to change to=
 2001:dba:2:8000::/49. Suppose that I am offering a service (web, email, wh=
atever) outside of my network. What RFC 4192 suggests is bringing up the tw=
o prefixes in parallel (eg, I am now using both 2001:dba:1::/48 and 2001:db=
a:2:8000::/49 throughout my network), and then take the old one down. The e=
ffect: during some part of the procedure, my external services have first o=
ne address, then two addresses, and finally one, but the one is the new one=
. I completely changed my address space, but my service never went down.

Case 2) suppose I am now using prefix 2001:dba:1::/48 and want to change to=
 2001:dba:2:8000::/49. Suppose that I am offering a service (web, email, wh=
atever) outside of my network. What the ULA advocates suggest that I have a=
 ULA up in parallel, either all the time or brought up for the purpose. I a=
m in effect now using 2001:dba:1::/48 and the ULA. I now take down 2001:dba=
:1::/48, and either simultaneously or subsequently bring up 2001:dba:2:8000=
::/49. If I do the two sequentially, I have an interval in which my service=
s are only reachable via the ULA; if I change them at the same time, the UL=
A allows me to maintain control of my network (my network management system=
 and other internal uses can use it to access equipment and applications wi=
thin my network), but the disrupted routing makes my services unavailable i=
n either global prefix for some period of time. The effect: during some par=
t of the procedure, the various systems in my network might have one, two, =
or three addres
 ses, but during any period in which only the ULA has stable routing, my se=
rvices are down as far as any external user is concerned.

Hence, a ULA is helpful for folks within my own network, but does not help =
keep my externally-facing services running. To my small mind, that makes a =
ULA a nice fallback in case something gets screwed up, but it is not a renu=
mbering solution. It fails to prevent a service outage during renumbering.
_______________________________________________
v6ops mailing list
v6ops@ietf.org
https://www.ietf.org/mailman/listinfo/v6ops=

From d.sturek@att.net  Thu Nov 17 06:25:17 2011
Return-Path: <d.sturek@att.net>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A9E8D11E8143 for <homenet@ietfa.amsl.com>; Thu, 17 Nov 2011 06:25:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.524
X-Spam-Level: 
X-Spam-Status: No, score=-2.524 tagged_above=-999 required=5 tests=[AWL=0.075,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iAG+8P6JGoZY for <homenet@ietfa.amsl.com>; Thu, 17 Nov 2011 06:25:17 -0800 (PST)
Received: from nm28.access.bullet.mail.mud.yahoo.com (nm28.access.bullet.mail.mud.yahoo.com [66.94.237.93]) by ietfa.amsl.com (Postfix) with SMTP id 5BBF511E813A for <homenet@ietf.org>; Thu, 17 Nov 2011 06:24:54 -0800 (PST)
Received: from [66.94.237.200] by nm28.access.bullet.mail.mud.yahoo.com with NNFMP; 17 Nov 2011 14:24:48 -0000
Received: from [66.94.237.101] by tm11.access.bullet.mail.mud.yahoo.com with NNFMP; 17 Nov 2011 14:24:48 -0000
Received: from [127.0.0.1] by omp1006.access.mail.mud.yahoo.com with NNFMP; 17 Nov 2011 14:24:48 -0000
X-Yahoo-Newman-Id: 400692.76747.bm@omp1006.access.mail.mud.yahoo.com
Received: (qmail 35990 invoked from network); 17 Nov 2011 14:24:48 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=att.net; s=s1024; t=1321539888; bh=phrK57y82uv6kkvE1gAggk+WVjx1OtRNMJrJP29TO7w=; h=X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:Received:User-Agent:Date:Subject:From:To:CC:Message-ID:Thread-Topic:In-Reply-To:Mime-version:Content-type:Content-transfer-encoding; b=E/fxvRIWKoaoU1GgOQ4dMpHzhWm8NSv38HTPKQXKC2xkmMFCmTPvRKNq2nBtMhdx+DZuDOdtgFmAu1LZtdnJTgkEUjpsrk3A+zUhuSsnQXNYGsGjUTdADREHYJ+BPk0fV6Jv2TO7KT3vZaenIYEU6EB+lNK5p7iOg30Ht5HZN6A=
X-Yahoo-Newman-Property: ymail-3
X-YMail-OSG: 9I4Ihm4VM1m.geh8YgzujF8Lo4GS3mmyc9nogFT1jx8MXJl Ys3DnoxNyLmnk7.yVi8LoyXwRNWNnzgtv9lFcfRj2Rm7aL4avfCw_AL5954c sY5Y4hhw7KQvlPaBfPAYInrx37K1PTMxw7hckdENUNTU7ugc6e4Ggmhzljbw ghqScDb.bcPJaBIRv0YfMd0ARJ2OrSQFrh9fKL4rCJ6jY_zmTV2uKrA94K7H JcSb2dUx.jeSzC315JeabYjJnCAUff7q889HwBwz1hFnjONq.TjQkZduL1zP ds9f7OMC.s_S6rWBz2xocTrL9FHdsLbWqXwJwCV.3w79pMeRualHuqDYXsYg 3rHFsqwQEdr0S48_5NMjKmuVT2yA0NLYAyPLlRsF1o5Fj8XTmFL7eG_FHG0K V8uKOD2jeyy92Hulaz2e0lfnhlLnqp5dvB3dJBA--
X-Yahoo-SMTP: fvjol_aswBAraSJvMLe2r1XTzhBhbFxY8q8c3jo-
Received: from [192.168.0.196] (d.sturek@69.105.138.6 with login) by smtp103.sbc.mail.mud.yahoo.com with SMTP; 17 Nov 2011 06:24:47 -0800 PST
User-Agent: Microsoft-MacOutlook/14.13.0.110805
Date: Thu, 17 Nov 2011 06:24:37 -0800
From: Don Sturek <d.sturek@att.net>
To: Anders Brandt <Anders_Brandt@sigmadesigns.com>, Fred Baker <fred@cisco.com>, "draft-liu-v6ops-ula-usage-analysis@tools.ietf.org" <draft-liu-v6ops-ula-usage-analysis@tools.ietf.org>
Message-ID: <CAEA57C3.D409%d.sturek@att.net>
Thread-Topic: [homenet] [v6ops] Major use cases for ULA
In-Reply-To: <03F31C213F2C6941BFDDBB4336E9E6CD0AB40668@cph-ex1>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>, "homenet@ietf.org" <homenet@ietf.org>
Subject: Re: [homenet] [v6ops] Major use cases for ULA
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 17 Nov 2011 14:25:17 -0000

Hi Anders,

+1 on what you wrote.  Here is another reason that ULAs are needed:
1)  If globals were used on the sub nets in your example, there would be a
dependence on the ISP serving the prefix that is unwanted for
communication within the home (eg, on/off for lighting within the home).
2)  For technologies like IEEE 802.15.4, link locals will not work in the
multi subnet scenario below.

It would also be nice within Homenet if we could provide an informational
draft providing guidance to the application development community around
using the proper scoped address type (ie, only use globals where you
really need global addressing, use ULAs for applications which are
designed to communicate within the home and use link locals where you are
sure the device you are trying to communicate with is on the same link as
the sender)

Don




On 11/17/11 2:57 AM, "Anders Brandt" <Anders_Brandt@sigmadesigns.com>
wrote:

>May I suggest variant 1b) :
>
>A home control installation with some powerline devices and some wireless
>devices each part of a lighting control system that MUST ALWAYS work.
>Both subnets are installed in autonomous fashion by two different
>technicians. Later, their border routers are interconnected via the
>homenet backbone.
>We may argue if a ULA prefix is needed in the homenet backbone but both
>of the home control networks need ULA addresses
>
>A: because the devices need stable addresses so that they know where to
>send On/Off commands to the other subnet without depending on DNS
>servers, etc.
>
>B: because there is no infrastructure to coordinate the assignment of
>prefixes in the two home control subnets
>
>C: because LLNs often do use coordinated assignment of short link-layer
>addresses to get shorter frames and to improve header compression.
>    These short link-layer would often lead to duplicate IPv6 addresses
>if in the same subnet.
>
>Thanks,
>  Anders Brandt
>
>________________________________________
>From: v6ops-bounces@ietf.org [v6ops-bounces@ietf.org] on behalf of Fred
>Baker [fred@cisco.com]
>Sent: Thursday, November 17, 2011 11:37
>To: draft-liu-v6ops-ula-usage-analysis@tools.ietf.org
>Cc: v6ops@ietf.org WG
>Subject: [v6ops] Major use cases for ULA
>
>Trying to summarize at least my thoughts from the discussion this
>afternoon. Working group, tell me what I'm missing in this.
>
>First, as Jari noted from the mike, there is no case in which a ULA is
>required. If one is willing to only have connectivity in the link-local
>environment, one can communicate between two directly connected systems
>using a link-local address. If one has in the past had the use of a
>prefix allocated by someone else, but are right now not connected to the
>Internet, there is no harm in using that prefix even if it is expired.
>Reason: there will be no confusion. As soon as one reconnects, the
>expiration of the prefix needs to take effect, however.
>
>To my mind, there are three valid uses of a ULA. The choice of use cases
>center on the word "local".
>
>1) if one is in a network that does not have service from someone that
>will allocate it a prefix and wants to either use addresses that are not
>link-local or addresses that will allow for routing, a ULA provides a way
>to generate a prefix for the purpose. One example of such an environment
>is a Smart Grid HAN in a home that doesn't have an ISP. To me, this is a
>textbook case for the use of a ULA.
>
>2) if one is in a network that DOES have service from someone that will
>allocate it a prefix but wants to use addresses that are not in that
>prefix and are not routed anywhere else, a ULA can provide such a prefix.
>There are a number of possible examples.
>
>At Cisco, to pick one, we have a number of systems with names like
>http://wwwin.cisco.com - systems that offer no services outside Cisco but
>provide some interior service. There are at least two ways to implement
>that policy. One obvious one would be to put some ACL in the
>routers/firewalls at the edge of the network that drop traffic to or from
>those addresses. Another, which I would only want to implement in the
>presence of that firewall ACL, would be to not advertise the names
>outside the company in DNS (probably by implementing a split DNS). A
>third would be to give them ULA addresses, which are not advertised
>outside the company and are therefore something folks outside can't route
>to.
>
>Another example is the one I mentioned in RFC 6296; if you choose to use
>such a translator, you're going to need an interior prefix. That could be
>ULA or global. If it is global and you decide to change away from that
>carrier, you will have to renumber the network. If you find that scary,
>you might choose a ULA as your internal prefix.
>
>The key point is not "6296", nor is it "internal-only policy". It's "In
>my addressing plan, I want to use a *different* prefix that is not routed
>outside". If you have that policy, one of the options (and not the only
>option) would be to use a ULA.
>
>3) If you have a special routing scenario, of which
>draft-baker-v6ops-b2b-private-routing is an example, for various reasons
>you might want to have routing that you control and is separate from
>other routing. In the b2b case, even though two companies each have at
>least one ISP, they might choose to ALSO use direct connectivity that
>only connects stated machines, such as a silicon foundry with client
>engineers that use it. A ULA provides a simple way to obtain such a
>prefix that would be used in accordance with an agreement between the
>parties.
>
>
>
>To my mind, the renumbering scenario is a red herring. Thomas Narten
>wanted desperately for me to put it into RFC 4192 as "A ULA could help
>when renumbering a network". However, it doesn't actually do so.
>
>Case 1) suppose I am now using prefix 2001:dba:1::/48 and want to change
>to 2001:dba:2:8000::/49. Suppose that I am offering a service (web,
>email, whatever) outside of my network. What RFC 4192 suggests is
>bringing up the two prefixes in parallel (eg, I am now using both
>2001:dba:1::/48 and 2001:dba:2:8000::/49 throughout my network), and then
>take the old one down. The effect: during some part of the procedure, my
>external services have first one address, then two addresses, and finally
>one, but the one is the new one. I completely changed my address space,
>but my service never went down.
>
>Case 2) suppose I am now using prefix 2001:dba:1::/48 and want to change
>to 2001:dba:2:8000::/49. Suppose that I am offering a service (web,
>email, whatever) outside of my network. What the ULA advocates suggest
>that I have a ULA up in parallel, either all the time or brought up for
>the purpose. I am in effect now using 2001:dba:1::/48 and the ULA. I now
>take down 2001:dba:1::/48, and either simultaneously or subsequently
>bring up 2001:dba:2:8000::/49. If I do the two sequentially, I have an
>interval in which my services are only reachable via the ULA; if I change
>them at the same time, the ULA allows me to maintain control of my
>network (my network management system and other internal uses can use it
>to access equipment and applications within my network), but the
>disrupted routing makes my services unavailable in either global prefix
>for some period of time. The effect: during some part of the procedure,
>the various systems in my network might have one, two, or three addres
> ses, but during any period in which only the ULA has stable routing, my
>services are down as far as any external user is concerned.
>
>Hence, a ULA is helpful for folks within my own network, but does not
>help keep my externally-facing services running. To my small mind, that
>makes a ULA a nice fallback in case something gets screwed up, but it is
>not a renumbering solution. It fails to prevent a service outage during
>renumbering.
>_______________________________________________
>v6ops mailing list
>v6ops@ietf.org
>https://www.ietf.org/mailman/listinfo/v6ops
>_______________________________________________
>homenet mailing list
>homenet@ietf.org
>https://www.ietf.org/mailman/listinfo/homenet



From mcr@sandelman.ca  Thu Nov 17 06:29:10 2011
Return-Path: <mcr@sandelman.ca>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C365F11E8159 for <homenet@ietfa.amsl.com>; Thu, 17 Nov 2011 06:29:10 -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=[AWL=0.042,  BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wd5TJL1g1cdY for <homenet@ietfa.amsl.com>; Thu, 17 Nov 2011 06:29:10 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id 5676011E8158 for <homenet@ietf.org>; Thu, 17 Nov 2011 06:29:10 -0800 (PST)
Received: from marajade.sandelman.ca (unknown [132.213.237.180]) by relay.sandelman.ca (Postfix) with ESMTPS id 35745343E9 for <homenet@ietf.org>; Thu, 17 Nov 2011 09:27:41 -0500 (EST)
Received: by marajade.sandelman.ca (Postfix, from userid 179) id 0D01A98CB2; Thu, 17 Nov 2011 09:28:48 -0500 (EST)
Received: from marajade.sandelman.ca (localhost [127.0.0.1]) by marajade.sandelman.ca (Postfix) with ESMTP id 09E96980ED for <homenet@ietf.org>; Thu, 17 Nov 2011 09:28:48 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ca>
To: "homenet@ietf.org Group" <homenet@ietf.org>
In-Reply-To: <5EAB9925-C2C7-4431-A826-13EEC46CDADC@townsley.net>
References: <5EAB9925-C2C7-4431-A826-13EEC46CDADC@townsley.net>
X-Mailer: MH-E 8.1; nmh 1.3-dev; XEmacs 21.4 (patch 22)
Date: Thu, 17 Nov 2011 09:28:47 -0500
Message-ID: <6688.1321540127@marajade.sandelman.ca>
Sender: mcr@sandelman.ca
Subject: Re: [homenet] Next steps
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 17 Nov 2011 14:29:10 -0000

>>>>> "Mark" == Mark Townsley <mark@townsley.net> writes:
    Mark> First, we'd like to formally move draft-chown-homenet-arch-01
    Mark> to draft-ietf-homenet-arch-00. This of course does not mean
    Mark> that the document is finished, just that this will be the
    Mark> document the working group will recognize as its collective
    Mark> work in progress until it becomes an RFC. If anyone has

I concur.

    Mark> Second, we'd like to reiterate our call for people who have a
    Mark> particular routing protocol that they believe would be a good
    Mark> candidate for application to the homenet problem space, please
    Mark> let the WG know via an Internet Draft submission. Reason being
    Mark> is that we have fewer homenet documents submitted thus far
    Mark> than we have heard chatter about in terms of possible
    Mark> solutions. Also, a routing solution was listed as one of our
    Mark> first deliverables when homenet was chartered.

Is there a deadline for this?
I think that we need to decide on a protocol soonish.

I do not think that there is a consensus as yet as to how much security
is enough.   I think that this is going to be a major sticking point.

-- 
]       He who is tired of Weird Al is tired of life!           |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
   Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE>
	               then sign the petition. 

From tomasz.mrugalski@gmail.com  Thu Nov 17 06:36:10 2011
Return-Path: <tomasz.mrugalski@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7907A11E8153 for <homenet@ietfa.amsl.com>; Thu, 17 Nov 2011 06:36:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.239
X-Spam-Level: 
X-Spam-Status: No, score=-3.239 tagged_above=-999 required=5 tests=[AWL=-0.240, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hsjjKz3YUkwi for <homenet@ietfa.amsl.com>; Thu, 17 Nov 2011 06:36:10 -0800 (PST)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 6193411E8125 for <homenet@ietf.org>; Thu, 17 Nov 2011 06:36:09 -0800 (PST)
Received: by yenq4 with SMTP id q4so1320101yen.31 for <homenet@ietf.org>; Thu, 17 Nov 2011 06:36:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject :x-enigmail-version:content-type:content-transfer-encoding; bh=a/NfReNCJ4jH7VC+mYwNfgvvQAy/5gJR0MUT5yO7VW8=; b=WvJmQnC7BQA0vVDLIOwAMS48PoZbBx63ESMURMIOVZ+1w6oJnbw9rj4JWN41HjCv+u fqXW3yzV/tTyeYlLaNVouc3jOosf+uyOmK866rdp1dclqLsbvac3Qfm/IkL/4FIWrZ7K nFMPB+yk23+VStBjaywMfsEJjZAbJwQ3B1bY0=
Received: by 10.236.200.131 with SMTP id z3mr9978342yhn.129.1321540567175; Thu, 17 Nov 2011 06:36:07 -0800 (PST)
Received: from dhcp-41d0.meeting.ietf.org ([2001:df8:0:64:de2b:61ff:fee5:409c]) by mx.google.com with ESMTPS id 8sm96528994anv.16.2011.11.17.06.36.04 (version=SSLv3 cipher=OTHER); Thu, 17 Nov 2011 06:36:06 -0800 (PST)
Message-ID: <4EC51BD2.2020404@gmail.com>
Date: Thu, 17 Nov 2011 22:36:02 +0800
From: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: homenet@ietf.org
X-Enigmail-Version: 1.3.3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: [homenet] Discussion on feasibility of route configuration over DHCPv6
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 17 Nov 2011 14:36:10 -0000

Hi,
Everyone's favourite topic is back. There is pretty good chance that
current discussion will lead to either publication of
draft-ietf-mif-dhcpv6-route-option or its abandonment.

If you care about this topic, you are encouraged to read and post in:

Why we need route option thread:
http://www.ietf.org/mail-archive/web/mif/current/msg01431.html

Why we should drop route option thread:
http://www.ietf.org/mail-archive/web/mif/current/msg01432.html

There are questions raised if MIF is the best place for this option, but
since it is adopted there, MIF list seems like a reasonable place to
discuss its faith. There are at least 5 (DHC, MIF, HOMENET, V6OPS, 6MAN)
WGs that may be interested in this. There may be others. I consider
cross-posting to 5 mailing lists as highly inappropriate.

Similar posts as this will be sent to DHC, HOMENET, V6OPS and 6MAN shortly.

Cheers,
Tomek Mrugalski
ISC

From diego@tid.es  Thu Nov 17 19:58:44 2011
Return-Path: <diego@tid.es>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A053711E8073 for <homenet@ietfa.amsl.com>; Thu, 17 Nov 2011 19:58:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.749
X-Spam-Level: 
X-Spam-Status: No, score=-4.749 tagged_above=-999 required=5 tests=[AWL=-0.750, BAYES_50=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fv8sOMYlDtc8 for <homenet@ietfa.amsl.com>; Thu, 17 Nov 2011 19:58:44 -0800 (PST)
Received: from correo-bck.tid.es (correo-bck.tid.es [195.235.93.200]) by ietfa.amsl.com (Postfix) with ESMTP id 9FC4F1F0C74 for <homenet@ietf.org>; Thu, 17 Nov 2011 19:58:43 -0800 (PST)
Received: from sbrightmailg02.hi.inet (Sbrightmailg02.hi.inet [10.95.78.105]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LUU008AN8DTDD@tid.hi.inet> for homenet@ietf.org; Fri, 18 Nov 2011 04:58:41 +0100 (MET)
Received: from vanvan (vanvan.hi.inet [10.95.78.49])	by sbrightmailg02.hi.inet (Symantec Messaging Gateway) with SMTP id 05.29.21312.1F7D5CE4; Fri, 18 Nov 2011 04:58:41 +0100 (CET)
Received: from correo.tid.es (mailhost.hi.inet [10.95.64.100]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPS id <0LUU008AJ8DTDD@tid.hi.inet> for homenet@ietf.org; Fri, 18 Nov 2011 04:58:41 +0100 (MET)
Received: from EXCLU2K7.hi.inet ([10.95.67.65]) by htcasmad1.hi.inet ([192.168.0.1]) with mapi; Fri, 18 Nov 2011 04:58:41 +0100
Date: Fri, 18 Nov 2011 04:58:34 +0100
From: DIEGO LOPEZ GARCIA <diego@tid.es>
In-reply-to: <25559.1321397513@marajade.sandelman.ca>
To: Michael Richardson <mcr@sandelman.ca>
Message-id: <C7AC72F4-51F4-49FD-B814-A82F383E76AB@tid.es>
MIME-version: 1.0
Content-type: text/plain; charset=Windows-1252
Content-language: en-US
Content-transfer-encoding: quoted-printable
Accept-Language: en-US
Thread-topic: [homenet] Comments on draft-acee-ospf-ospfv3-autoconfig-00
Thread-index: AcylplvNWZWoIKWLTni61OsX8tvqwQ==
acceptlanguage: en-US
X-AuditID: 0a5f4e69-b7f1c6d000005340-9a-4ec5d7f1b370
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprGKsWRmVeSWpSXmKPExsXCFe9nqPvx+lE/g7PvJS3eLzrE4sDosWTJ T6YAxigum5TUnMyy1CJ9uwSujCtfp7MWbOOoOLSxpoHxDlsXIyeHhICJxIztDawQtpjEhXvr geJcHEIC2xglfp1uh3J+MUo0LdwH5TQySsx92M0M0sIioCqxZOcWJhCbTUBdouXoNxYQW1jA XaL/9h92EJtTwFTi8KqXYDUiApoSR2a2g9nMAtoSX161M4LYvAKWEk9vLYSyBSV+TL7HAlGj J/Hxz21GCFtcorn1JgtM75N3F8DOZgQ6+/upNVDzPSRmXJnNCmHrSZx8NpMdokZU4k77ekaI NwUkluw5zwxhi0q8fPyPFeKxe4wSd2Y/YZ/AKD4LyR2zkNwxC8kds5DcsYCRZRWjWHFSUWZ6 RkluYmZOuoGRXkamXmZeaskmRkgkZe5gXL5T5RCjAAejEg/vjoSjfkKsiWXFlbmHGCU5mJRE eSWuAYX4kvJTKjMSizPii0pzUosPMUpwMCuJ8DatBMrxpiRWVqUW5cOkZDg4lCR4jS4CpQSL UtNTK9Iyc4DpAibNxMEJ0s4D1N54HaS9uCAxtzgzHSJ/ilFSSpz3A0izAEgiozQPrvcVozjQ kcK87iBtPMDEBtf1CmggE9DA3D1HQAaWJCKkpBoYoz4KaxXfFLm58oh5foud9o9Lm9/IGBhs 3x7jF7Rn2kTRK+VMa22S9k244C/VOtPRacUMuZzwP1aeO+WvVjG9Z1Nc5h51e8bl8mPXDure trqb0/xDfYWvXUmiaGzXBpGiI5EvT0/eGfdDZdbtU2seL8n3K51mzdXcZJz+x1vy1KdZnxz7 lvCdU2Ipzkg01GIuKk4EAAJiYGkpAwAA
References: <CAKD1Yr3uSsNP4avZBdQE7YxFd7D_KOXBOCsfaRfvnWhJoLoY9Q@mail.gmail.com> <28079.1321370795@marajade.sandelman.ca> <3112C980-7FD1-4BE3-8494-3E89E8D40376@ericsson.com> <25559.1321397513@marajade.sandelman.ca>
Cc: "<homenet@ietf.org>" <homenet@ietf.org>
Subject: Re: [homenet] Comments on draft-acee-ospf-ospfv3-autoconfig-00
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 18 Nov 2011 03:58:44 -0000

On 16 Nov 2011, at 06:51 , Michael Richardson wrote:

> Do we need security for wired connections?  It's an open question.
> Do we need security for closed wifi connections?  I think maybe.
> Do we need security for open/guest wifi connections?  I think definitely.


When it comes to wired connections why don't we consider both closed and gu=
est access as in the wireless case? In a densely connected home, some wired=
 points could be intended to be used by, say, someone coming to make some m=
aintenance work=85

--
"Esta vez no fallaremos, Doctor Infierno"

Dr Diego R. Lopez
Telefonica I+D

e-mail: diego@tid.es
Tel:      +34 913 129 041
-----------------------------------------






Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nu=
estra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en el enl=
ace situado m=E1s abajo.
This message is intended exclusively for its addressee. We only send and re=
ceive email on the basis of the terms set out at.
http://www.tid.es/ES/PAGINAS/disclaimer.aspx

From ot@cisco.com  Fri Nov 18 00:14:18 2011
Return-Path: <ot@cisco.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50E4321F953C for <homenet@ietfa.amsl.com>; Fri, 18 Nov 2011 00:14:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.863
X-Spam-Level: 
X-Spam-Status: No, score=-9.863 tagged_above=-999 required=5 tests=[AWL=0.736,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZOIYaeXKwSgQ for <homenet@ietfa.amsl.com>; Fri, 18 Nov 2011 00:14:17 -0800 (PST)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by ietfa.amsl.com (Postfix) with ESMTP id C089721F9536 for <homenet@ietf.org>; Fri, 18 Nov 2011 00:14:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ot@cisco.com; l=764; q=dns/txt; s=iport; t=1321604053; x=1322813653; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=l4qhk7JNmCgeegkUlRmPIdx16AN9WPgeZnpOloCbF3s=; b=STR56vRHHHNQPRorpMGOtV+dCoWDMHNLeCfCODChtjOMVmBmkuiuKf8r KNDEPy5F1PbkWeWTYlatYq2lQfW0twaLhnS+/b8JrOSGtLV9JNaVUbbxc Dv0+i72PvUJ18LNKFpP/3xOmiasWHcySVBrgNHxy5LlC3uBzCMs0FNfVP U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EACkTxk6Q/khL/2dsb2JhbABCqkOBBYFyAQEBAwESASc/BQsLDjhXBjWHYZgtAZ5JiTRjBJQ3kgA
X-IronPort-AV: E=Sophos;i="4.69,532,1315180800"; d="scan'208";a="122008627"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-1.cisco.com with ESMTP; 18 Nov 2011 08:14:12 +0000
Received: from ams3-vpn-dhcp5098.cisco.com (ams3-vpn-dhcp5098.cisco.com [10.61.83.233]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id pAI8EC4k013283; Fri, 18 Nov 2011 08:14:12 GMT
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Ole Troan <ot@cisco.com>
In-Reply-To: <17953.1321493297@marajade.sandelman.ca>
Date: Fri, 18 Nov 2011 09:14:12 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <400C7BA2-3D4D-4663-9B3E-FA2E6C2D8992@cisco.com>
References: <4EC1D206.2070303@gmail.com> <3C716203-8579-41EA-98CE-6DC3BE9261D8@fugue.com> <FC520CA0-BAA4-4309-A878-CB40308F2562@cisco.com> <09215FB7-EA7A-4D9D-8772-737B79CBBD20@fugue.com> <4EC32B76.8080706@riw.us> <7DADF53B-56CA-47CC-BBDA-34300EE4D22D@fugue.com> <7D0889B6-7769-4F74-996D-08CDA02B3670@cisco.com> <84FD521E-D48C-41C9-935B-9B4695FB658D@cisco.com> <489BE869-79F9-40FC-96B1-6A190620B4CA@cisco.com> <7F630AC9-A369-48B8-BD8F-684C0AC1DDDA@fugue.com> <72EB15CA-CAB4-4A50-BAB4-E60176109AF5@cisco.com> <E34DB847-4FC9-4982-A609-B80707F61E45@fugue.com> <E5723B4B-BDE4-47F4-B560-1165F713D5E2@cisco.com> <46CB823A-3C53-4C32-A33C-498CA6413448@fugue.com> <17953.1321493297@marajade.sandelman.ca>
To: Michael Richardson <mcr@sandelman.ca>
X-Mailer: Apple Mail (2.1084)
Cc: "homenet@ietf.org" <homenet@ietf.org>
Subject: Re: [homenet] draft-baker-homenet-prefix-assignment
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 18 Nov 2011 08:14:18 -0000

Michael,

> Is there some reason that the flooding mechanism can't distribute the
> list of edge CPE routers, and then DHCPv6 can be used in unicast
> request/reply to ask those CPE routers for things.
>=20
> (I would even wonder if the CPE routers shouldn't be identified by =
their
> ULA rather than self-identifying by the address in the subnet the deal =
with)
>=20
> This is how I imagined the DHCPv6 PD mechanism working before
> draft-chakrabarti-homenet-prefix-alloc-01 was written, which imagined =
a
> strict hierarchal tree.

that's how I imagined also.
DHCP PD on the edges. flooding protocol between all the internal =
routers. then hosts use RA/DHCP for addresses / other configurations to =
their onlink routers.

cheers,
Ole


From guillaume.habault@gmail.com  Fri Nov 18 02:49:33 2011
Return-Path: <guillaume.habault@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98C1B21F8B14 for <homenet@ietfa.amsl.com>; Fri, 18 Nov 2011 02:49:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TYgKMueJFHR0 for <homenet@ietfa.amsl.com>; Fri, 18 Nov 2011 02:49:29 -0800 (PST)
Received: from mail-ey0-f194.google.com (mail-ey0-f194.google.com [209.85.215.194]) by ietfa.amsl.com (Postfix) with ESMTP id 4332621F8A62 for <homenet@ietf.org>; Fri, 18 Nov 2011 02:49:29 -0800 (PST)
Received: by eyd10 with SMTP id 10so545361eyd.1 for <homenet@ietf.org>; Fri, 18 Nov 2011 02:49:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=OqSkboWuFvlj7ZPSkp62QIjfktAB2n5Xq/JCn0BrVrc=; b=TeRzoZoZSWZ7MqBdjdXWbIgsYNExb6Dj8lZrXomsPKJgMrzTTcwt7MJkmujVAR0/Fl s+s0Uho6DA/3GW7HFFtrbUnqYG2prEj1Axzoi7ssXNgPYHuTfdMAu5ZPj2HckAXyxvp/ OTR0C57E7iH4E0RJfhsbur4c1DFDDr7Q8PqaU=
MIME-Version: 1.0
Received: by 10.14.10.5 with SMTP id 5mr216916eeu.83.1321613360672; Fri, 18 Nov 2011 02:49:20 -0800 (PST)
Received: by 10.213.9.65 with HTTP; Fri, 18 Nov 2011 02:49:20 -0800 (PST)
In-Reply-To: <32238.1321463734@marajade.sandelman.ca>
References: <DCC302FAA9FE5F4BBA4DCAD46569377914518AFAE5@PRVPEXVS03.corp.twcable.com> <4EB583C8.5030907@piuha.net> <13027.1320680393@marajade.sandelman.ca> <BDF2740C082F6942820D95BAEB9E1A845A9789@XMB-AMS-108.cisco.com> <CA+XPzSY8cC_PyhcMNqhk4+B6tghp8Dpy2-3aMPZmyVRP=AWnaA@mail.gmail.com> <3512.1321317664@marajade.sandelman.ca> <CA+XPzSaeg=pqmdSVXr+BQvS2D0+iVqN-q7e4dJoUtA=eA38vGA@mail.gmail.com> <32238.1321463734@marajade.sandelman.ca>
Date: Fri, 18 Nov 2011 11:49:20 +0100
Message-ID: <CA+XPzSb-n=8Ss-OH3TzMXTetwqDJM9_YuvMFxKiWTbJ5fVz3UA@mail.gmail.com>
From: Guillaume Habault <guillaume.habault@gmail.com>
To: Michael Richardson <mcr@sandelman.ca>
Content-Type: multipart/alternative; boundary=001636416ddbe4b02004b20016fc
Cc: homenet@ietf.org
Subject: Re: [homenet] more comments on draft-arkko-homenet-prefix-assignment
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 18 Nov 2011 10:49:33 -0000

--001636416ddbe4b02004b20016fc
Content-Type: text/plain; charset=ISO-8859-1

2011/11/16 Michael Richardson <mcr@sandelman.ca>

>
> >>>>> "Guillaume" == Guillaume Habault <guillaume.habault@gmail.com>
> writes:
>    Guillaume> the host select the appropriate address, the routing
>     Guillaume> protocol may route the message to the wrong Customer Edge
>    Guillaume> Router (especially if we are in the case where there is
>    Guillaume> more than one Customer Edge Router in the home network.
>
>    >> We have assumed that the home gateways will cooperate and provide
>    >> source address routing, making sure that packets are routed out
>    >> the link which can accept that source address.
>
>     Guillaume> To summarize and to be sure I get what you are planning
>    Guillaume> to do, you will use a "normal" routing in the home
>    Guillaume> network. Then, home gateways will check the source
>    Guillaume> address of any packet coming and redirect it to the right
>    Guillaume> home gateways if the source address is not the good one
>    Guillaume> (just to be sure on what you mean by cooperate), is that
>    Guillaume> right?  If so, do you planned to have tunnels between
>
> So, go to Fred Baker's slides from yesterday:
>    http://www.ietf.org/proceedings/82/slides/homenet-8.pptx
> (and http://junk.sandelman.ca/junk/ietf82/homenet-8.pdf)
> slide "Multihoming"
>
> I think that it's called case 4 in the documents....
>    draft-chown-homenet-arch-01
>    figure 4 on page 11.
>
> If CPERouter 2 (the right hand-one), receives a packet with a source
> address which it knows (due to watching RAs and/or zOSPF) actually
> belongs to Server Provider A, then instead of handing the packet
> up to Service Provider B (where it likely gets dropped), it will
> instead forward the packet to Router 1.
>
> This forward is easy to do if Router 1 and Router 2 are on the same
> layer-2 link.  I don't think we've considered the case where they are
> not on the same link.
>
> We have said that for cases where there are multiple layers of routers,
> that the other layers of router MUST pick the right exit router based
> upon source IP, so I think that as long as Router 2 can find a path to
> Router 1, it can work even when Router 1 and Router 2 are not on the
> same link.
>
> The source-address redirect is necessary only so that we can avoid
> imposing a new requirement on the hosts which might be on that layer-2
> link.
>
>    Guillaume> If so, do you planned to have tunnels between
>    Guillaume> home gateways ? Are we sure that ISPs behind the home
>    Guillaume> gateway will accept to cooperate with each other (I said
>    Guillaume> that because in France, home gateways are mainly
>    Guillaume> given/lend by ISPs, and i'm not sure they will be willing
>    Guillaume> to share something with another ISP)?
>
> No, there are no tunnels across the Internet.
> The traffic is redirected within the home.
>
> If the ISP provided home router can't speak homenet, then I guess it
> won't get the right logo on it.
>
>
Ok, I understand now. I did not get that you assumed that both home
gateways were on the same link. It is true that if they are on the same
link you can forward the packet to the other one. However, if it's not the
case and that you need to send back a packet to the right CPE, you somehow
will have to encapsulate this packet so that it can be routed to the other
CPE (that why I was talking about tunnel between CPE previously).

According to me, but maybe i'm wrong, it's a bit late to do the source
address routing in the CPE, especially if we are in a complex topology (I
was assuming that there would be other router inside the home network
(other than the CPE, like in the figure 3 of the
draft-chown-homenet-arch-01)). In fact, if I have a home network with the
following topology:

----------    ---------------------       ------           -----
------       ---------------------    ----------
| ISP A | - | CPE Router A | --- | R1 | ------ | R2 | ------ | R3 | --- |
CPE Router B | - | ISP B |
----------    ---------------------       ------           -----
------       ---------------------    ----------

                      |

                      -------

                   | Host |

                -------

   1. Case 1: CPE Routers are the only one doing the source address routing
   (I assume it's what you were describing)
   If the Host sends a packet, and that this packet, which actually belongs
   to CPE Router B, is routed to the CPE Router A. CPE Router A will have to
   forward it all the way back to CPE Router B.

   2. Case 2: Some Interior Routers are doing the source address routing (I
   think that not all the interior router should do it though)
   If the Host sends the same packet, R3 will directly see that to avoid
   ingress filtering it has to send it to CPE Router B.

As long as the topology is simple (no interior router) or that CPEs are on
the same link, case 1 is fine. However, if we are in a more complex
topology, i think case 2 is the most appropriate. And if interior routers
are doing the source address routing there is no need for the CPE to do it,
unless it had Hosts directly connected to it.


-- 
Guillaume HABAULT
PhD Student
Institut TELECOM / TELECOM Bretagne

--001636416ddbe4b02004b20016fc
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><br><div class=3D"gmail_quote">2011/11/16 Michael Richardson <span dir=
=3D"ltr">&lt;<a href=3D"mailto:mcr@sandelman.ca" target=3D"_blank">mcr@sand=
elman.ca</a>&gt;</span><br><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">


<div><br>
&gt;&gt;&gt;&gt;&gt; &quot;Guillaume&quot; =3D=3D Guillaume Habault &lt;<a =
href=3D"mailto:guillaume.habault@gmail.com" target=3D"_blank">guillaume.hab=
ault@gmail.com</a>&gt; writes:<br>
 =A0 =A0Guillaume&gt; the host select the appropriate address, the routing<=
br>
</div> =A0 =A0Guillaume&gt; protocol may route the message to the wrong Cus=
tomer Edge<br>
 =A0 =A0Guillaume&gt; Router (especially if we are in the case where there =
is<br>
 =A0 =A0Guillaume&gt; more than one Customer Edge Router in the home networ=
k.<br>
<div><br>
 =A0 =A0&gt;&gt; We have assumed that the home gateways will cooperate and =
provide<br>
 =A0 =A0&gt;&gt; source address routing, making sure that packets are route=
d out<br>
 =A0 =A0&gt;&gt; the link which can accept that source address.<br>
<br>
</div> =A0 =A0Guillaume&gt; To summarize and to be sure I get what you are =
planning<br>
 =A0 =A0Guillaume&gt; to do, you will use a &quot;normal&quot; routing in t=
he home<br>
 =A0 =A0Guillaume&gt; network. Then, home gateways will check the source<br=
>
 =A0 =A0Guillaume&gt; address of any packet coming and redirect it to the r=
ight<br>
 =A0 =A0Guillaume&gt; home gateways if the source address is not the good o=
ne<br>
 =A0 =A0Guillaume&gt; (just to be sure on what you mean by cooperate), is t=
hat<br>
 =A0 =A0Guillaume&gt; right? =A0If so, do you planned to have tunnels betwe=
en<br>
<br>
So, go to Fred Baker&#39;s slides from yesterday:<br>
 =A0 =A0<a href=3D"http://www.ietf.org/proceedings/82/slides/homenet-8.pptx=
" target=3D"_blank">http://www.ietf.org/proceedings/82/slides/homenet-8.ppt=
x</a><br>
(and <a href=3D"http://junk.sandelman.ca/junk/ietf82/homenet-8.pdf" target=
=3D"_blank">http://junk.sandelman.ca/junk/ietf82/homenet-8.pdf</a>)<br>
slide &quot;Multihoming&quot;<br>
<br>
I think that it&#39;s called case 4 in the documents....<br>
 =A0 =A0draft-chown-homenet-arch-01<br>
 =A0 =A0figure 4 on page 11.<br>
<br>
If CPERouter 2 (the right hand-one), receives a packet with a source<br>
address which it knows (due to watching RAs and/or zOSPF) actually<br>
belongs to Server Provider A, then instead of handing the packet<br>
up to Service Provider B (where it likely gets dropped), it will<br>
instead forward the packet to Router 1.<br>
<br>
This forward is easy to do if Router 1 and Router 2 are on the same<br>
layer-2 link. =A0I don&#39;t think we&#39;ve considered the case where they=
 are<br>
not on the same link.<br>
<br>
We have said that for cases where there are multiple layers of routers,<br>
that the other layers of router MUST pick the right exit router based<br>
upon source IP, so I think that as long as Router 2 can find a path to<br>
Router 1, it can work even when Router 1 and Router 2 are not on the<br>
same link.<br>
<br>
The source-address redirect is necessary only so that we can avoid<br>
imposing a new requirement on the hosts which might be on that layer-2<br>
link.<br>
<br>
 =A0 =A0Guillaume&gt; If so, do you planned to have tunnels between<br>
 =A0 =A0Guillaume&gt; home gateways ? Are we sure that ISPs behind the home=
<br>
 =A0 =A0Guillaume&gt; gateway will accept to cooperate with each other (I s=
aid<br>
 =A0 =A0Guillaume&gt; that because in France, home gateways are mainly<br>
 =A0 =A0Guillaume&gt; given/lend by ISPs, and i&#39;m not sure they will be=
 willing<br>
 =A0 =A0Guillaume&gt; to share something with another ISP)?<br>
<br>
No, there are no tunnels across the Internet.<br>
The traffic is redirected within the home.<br>
<br>
If the ISP provided home router can&#39;t speak homenet, then I guess it<br=
>
won&#39;t get the right logo on it.<br>
<div><div><br>
</div></div></blockquote></div><br>Ok, I understand now. I did not get that=
 you assumed that both home gateways were on the same link. It is true that=
 if they are on the same link you can forward the packet to the other one. =
However, if it&#39;s not the case and that you need to send back a packet t=
o the right CPE, you somehow will have to encapsulate this packet so that i=
t can be routed to the other CPE (that why I was talking about tunnel betwe=
en CPE previously). <br>


<br>According to me, but maybe i&#39;m wrong, it&#39;s a bit late to do the=
 source address routing in the CPE, especially if we are in a complex topol=
ogy (I was assuming that there would be other router inside the home networ=
k (other than the CPE, like in the figure 3 of the draft-chown-homenet-arch=
-01)). In fact, if I have a home network with the following topology:<br>


<br>---------- =A0=A0 ---------------------=A0=A0=A0=A0=A0=A0 ------ =A0=A0=
=A0=A0=A0=A0=A0=A0=A0 -----=A0=A0=A0=A0=A0=A0=A0 =A0=A0 ------=A0 =A0 =A0=
=A0 ---------------------=A0=A0=A0 ----------<br>| ISP A | - | CPE Router A=
 | --- | R1 | ------ | R2 | ------ | R3 | --- | CPE Router B | - | ISP B |<=
br>


---------- =A0=A0 ---------------------=A0  =A0=A0=A0=A0 ------ =A0=A0=A0=
=A0=A0=A0=A0=A0=A0 -----=A0 =A0 =A0 =A0 =A0=A0 ------=A0 =A0 =A0=A0 -------=
--------------=A0=A0=A0 ----------<br>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 |<br>

=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0 -------<br>
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
 =A0 =A0 =A0 =A0 =A0 =A0 =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0 | Host |<br>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 -------<br><ol><li>Case 1: CPE Routers are t=
he only one doing the source address routing (I assume it&#39;s what you we=
re describing)<br>


If the Host sends a packet, and that this packet, which actually belongs to=
 CPE Router B, is routed to the CPE Router A. CPE Router A will have to for=
ward it all the way back to CPE Router B.<br><br></li><li>Case 2: Some Inte=
rior Routers are doing the source address routing (I think that not all the=
 interior router should do it though)<br>


If the Host sends the same packet, R3 will directly see that to avoid ingre=
ss filtering it has to send it to CPE Router B.</li></ol>As long as the top=
ology is simple (no interior router) or that CPEs are on the same link, cas=
e 1 is fine. However, if we are in a more complex topology, i think case 2 =
is the most appropriate. And if interior routers are doing the source addre=
ss routing there is no need for the CPE to do it, unless it had Hosts direc=
tly connected to it.<br>
<br>
<br>-- <br>Guillaume HABAULT<br>PhD Student<br>Institut TELECOM / TELECOM B=
retagne<br><br><br>

--001636416ddbe4b02004b20016fc--

From teco@inf-net.nl  Fri Nov 18 03:08:15 2011
Return-Path: <teco@inf-net.nl>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CEC5821F84FB for <homenet@ietfa.amsl.com>; Fri, 18 Nov 2011 03:08:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level: 
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AZwzkFrkqRUi for <homenet@ietfa.amsl.com>; Fri, 18 Nov 2011 03:08:11 -0800 (PST)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 0EC2721F8A35 for <homenet@ietf.org>; Fri, 18 Nov 2011 03:08:10 -0800 (PST)
Received: by yenq4 with SMTP id q4so2766364yen.31 for <homenet@ietf.org>; Fri, 18 Nov 2011 03:08:09 -0800 (PST)
Received: by 10.236.154.42 with SMTP id g30mr4064825yhk.3.1321614489705; Fri, 18 Nov 2011 03:08:09 -0800 (PST)
Received: from [172.16.3.54] (114-34-203-163.HINET-IP.hinet.net. [114.34.203.163]) by mx.google.com with ESMTPS id u19sm1126855ank.11.2011.11.18.03.08.06 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 18 Nov 2011 03:08:08 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: multipart/alternative; boundary="Apple-Mail=_2CF88800-57CD-4F28-A3D3-9A325704DE18"
From: Teco Boot <teco@inf-net.nl>
In-Reply-To: <CA+XPzSb-n=8Ss-OH3TzMXTetwqDJM9_YuvMFxKiWTbJ5fVz3UA@mail.gmail.com>
Date: Fri, 18 Nov 2011 12:08:05 +0100
Message-Id: <F48D5746-0911-444E-BD6F-6DD6C0749BB3@inf-net.nl>
References: <DCC302FAA9FE5F4BBA4DCAD46569377914518AFAE5@PRVPEXVS03.corp.twcable.com> <4EB583C8.5030907@piuha.net> <13027.1320680393@marajade.sandelman.ca> <BDF2740C082F6942820D95BAEB9E1A845A9789@XMB-AMS-108.cisco.com> <CA+XPzSY8cC_PyhcMNqhk4+B6tghp8Dpy2-3aMPZmyVRP=AWnaA@mail.gmail.com> <3512.1321317664@marajade.sandelman.ca> <CA+XPzSaeg=pqmdSVXr+BQvS2D0+iVqN-q7e4dJoUtA=eA38vGA@mail.gmail.com> <32238.1321463734@marajade.sandelman.ca> <CA+XPzSb-n=8Ss-OH3TzMXTetwqDJM9_YuvMFxKiWTbJ5fVz3UA@mail.gmail.com>
To: Guillaume Habault <guillaume.habault@gmail.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: homenet@ietf.org, Michael Richardson <mcr@sandelman.ca>
Subject: Re: [homenet] more comments on draft-arkko-homenet-prefix-assignment
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 18 Nov 2011 11:08:15 -0000

--Apple-Mail=_2CF88800-57CD-4F28-A3D3-9A325704DE18
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


Op 18 nov. 2011, om 11:49 heeft Guillaume Habault het volgende =
geschreven:

>=20
>=20
> 2011/11/16 Michael Richardson <mcr@sandelman.ca>
>=20
> >>>>> "Guillaume" =3D=3D Guillaume Habault =
<guillaume.habault@gmail.com> writes:
>    Guillaume> the host select the appropriate address, the routing
>    Guillaume> protocol may route the message to the wrong Customer =
Edge
>    Guillaume> Router (especially if we are in the case where there is
>    Guillaume> more than one Customer Edge Router in the home network.
>=20
>    >> We have assumed that the home gateways will cooperate and =
provide
>    >> source address routing, making sure that packets are routed out
>    >> the link which can accept that source address.
>=20
>    Guillaume> To summarize and to be sure I get what you are planning
>    Guillaume> to do, you will use a "normal" routing in the home
>    Guillaume> network. Then, home gateways will check the source
>    Guillaume> address of any packet coming and redirect it to the =
right
>    Guillaume> home gateways if the source address is not the good one
>    Guillaume> (just to be sure on what you mean by cooperate), is that
>    Guillaume> right?  If so, do you planned to have tunnels between
>=20
> So, go to Fred Baker's slides from yesterday:
>    http://www.ietf.org/proceedings/82/slides/homenet-8.pptx
> (and http://junk.sandelman.ca/junk/ietf82/homenet-8.pdf)
> slide "Multihoming"
>=20
> I think that it's called case 4 in the documents....
>    draft-chown-homenet-arch-01
>    figure 4 on page 11.
>=20
> If CPERouter 2 (the right hand-one), receives a packet with a source
> address which it knows (due to watching RAs and/or zOSPF) actually
> belongs to Server Provider A, then instead of handing the packet
> up to Service Provider B (where it likely gets dropped), it will
> instead forward the packet to Router 1.
>=20
> This forward is easy to do if Router 1 and Router 2 are on the same
> layer-2 link.  I don't think we've considered the case where they are
> not on the same link.
>=20
> We have said that for cases where there are multiple layers of =
routers,
> that the other layers of router MUST pick the right exit router based
> upon source IP, so I think that as long as Router 2 can find a path to
> Router 1, it can work even when Router 1 and Router 2 are not on the
> same link.
>=20
> The source-address redirect is necessary only so that we can avoid
> imposing a new requirement on the hosts which might be on that layer-2
> link.
>=20
>    Guillaume> If so, do you planned to have tunnels between
>    Guillaume> home gateways ? Are we sure that ISPs behind the home
>    Guillaume> gateway will accept to cooperate with each other (I said
>    Guillaume> that because in France, home gateways are mainly
>    Guillaume> given/lend by ISPs, and i'm not sure they will be =
willing
>    Guillaume> to share something with another ISP)?
>=20
> No, there are no tunnels across the Internet.
> The traffic is redirected within the home.
>=20
> If the ISP provided home router can't speak homenet, then I guess it
> won't get the right logo on it.
>=20
>=20
> Ok, I understand now. I did not get that you assumed that both home =
gateways were on the same link. It is true that if they are on the same =
link you can forward the packet to the other one. However, if it's not =
the case and that you need to send back a packet to the right CPE, you =
somehow will have to encapsulate this packet so that it can be routed to =
the other CPE (that why I was talking about tunnel between CPE =
previously).=20
>=20
> According to me, but maybe i'm wrong, it's a bit late to do the source =
address routing in the CPE, especially if we are in a complex topology =
(I was assuming that there would be other router inside the home network =
(other than the CPE, like in the figure 3 of the =
draft-chown-homenet-arch-01)). In fact, if I have a home network with =
the following topology:
>=20
> ----------    ---------------------       ------           -----       =
    ------       ---------------------    ----------
> | ISP A | - | CPE Router A | --- | R1 | ------ | R2 | ------ | R3 | =
--- | CPE Router B | - | ISP B |
> ----------    ---------------------       ------           -----       =
    ------       ---------------------    ----------
>                                                                        =
                |
>                                                                        =
            -------
>                                                                        =
           | Host |
>                                                                        =
            -------
> Case 1: CPE Routers are the only one doing the source address routing =
(I assume it's what you were describing)
> If the Host sends a packet, and that this packet, which actually =
belongs to CPE Router B, is routed to the CPE Router A. CPE Router A =
will have to forward it all the way back to CPE Router B.
>=20
> Case 2: Some Interior Routers are doing the source address routing (I =
think that not all the interior router should do it though)
> If the Host sends the same packet, R3 will directly see that to avoid =
ingress filtering it has to send it to CPE Router B.
> As long as the topology is simple (no interior router) or that CPEs =
are on the same link, case 1 is fine. However, if we are in a more =
complex topology, i think case 2 is the most appropriate. And if =
interior routers are doing the source address routing there is no need =
for the CPE to do it, unless it had Hosts directly connected to it.

If part of the routers do SA routing, doensn't that look loopy?

I say all routers have the same forwarding algorithm.
Two methods: CPE redirects packets to right "other CPE" with tunnel (or =
RH). Or all routers send packets to correct CPE in the first place. =
Latter looks better to me. Time to resubmit =
draft-boot-brdp-based-routing, I think.

Teco


>=20
>=20
> --=20
> Guillaume HABAULT
> PhD Student
> Institut TELECOM / TELECOM Bretagne
>=20
>=20
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet


--Apple-Mail=_2CF88800-57CD-4F28-A3D3-9A325704DE18
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>Op 18 nov. 2011, om 11:49 heeft Guillaume Habault het =
volgende geschreven:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><br><br><div=
 class=3D"gmail_quote">2011/11/16 Michael Richardson <span =
dir=3D"ltr">&lt;<a href=3D"mailto:mcr@sandelman.ca" =
target=3D"_blank">mcr@sandelman.ca</a>&gt;</span><br><blockquote =
class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex">


<div><br>
&gt;&gt;&gt;&gt;&gt; "Guillaume" =3D=3D Guillaume Habault &lt;<a =
href=3D"mailto:guillaume.habault@gmail.com" =
target=3D"_blank">guillaume.habault@gmail.com</a>&gt; writes:<br>
 &nbsp; &nbsp;Guillaume&gt; the host select the appropriate address, the =
routing<br>
</div> &nbsp; &nbsp;Guillaume&gt; protocol may route the message to the =
wrong Customer Edge<br>
 &nbsp; &nbsp;Guillaume&gt; Router (especially if we are in the case =
where there is<br>
 &nbsp; &nbsp;Guillaume&gt; more than one Customer Edge Router in the =
home network.<br>
<div><br>
 &nbsp; &nbsp;&gt;&gt; We have assumed that the home gateways will =
cooperate and provide<br>
 &nbsp; &nbsp;&gt;&gt; source address routing, making sure that packets =
are routed out<br>
 &nbsp; &nbsp;&gt;&gt; the link which can accept that source =
address.<br>
<br>
</div> &nbsp; &nbsp;Guillaume&gt; To summarize and to be sure I get what =
you are planning<br>
 &nbsp; &nbsp;Guillaume&gt; to do, you will use a "normal" routing in =
the home<br>
 &nbsp; &nbsp;Guillaume&gt; network. Then, home gateways will check the =
source<br>
 &nbsp; &nbsp;Guillaume&gt; address of any packet coming and redirect it =
to the right<br>
 &nbsp; &nbsp;Guillaume&gt; home gateways if the source address is not =
the good one<br>
 &nbsp; &nbsp;Guillaume&gt; (just to be sure on what you mean by =
cooperate), is that<br>
 &nbsp; &nbsp;Guillaume&gt; right? &nbsp;If so, do you planned to have =
tunnels between<br>
<br>
So, go to Fred Baker's slides from yesterday:<br>
 &nbsp; &nbsp;<a =
href=3D"http://www.ietf.org/proceedings/82/slides/homenet-8.pptx" =
target=3D"_blank">http://www.ietf.org/proceedings/82/slides/homenet-8.pptx=
</a><br>
(and <a href=3D"http://junk.sandelman.ca/junk/ietf82/homenet-8.pdf" =
target=3D"_blank">http://junk.sandelman.ca/junk/ietf82/homenet-8.pdf</a>)<=
br>
slide "Multihoming"<br>
<br>
I think that it's called case 4 in the documents....<br>
 &nbsp; &nbsp;draft-chown-homenet-arch-01<br>
 &nbsp; &nbsp;figure 4 on page 11.<br>
<br>
If CPERouter 2 (the right hand-one), receives a packet with a source<br>
address which it knows (due to watching RAs and/or zOSPF) actually<br>
belongs to Server Provider A, then instead of handing the packet<br>
up to Service Provider B (where it likely gets dropped), it will<br>
instead forward the packet to Router 1.<br>
<br>
This forward is easy to do if Router 1 and Router 2 are on the same<br>
layer-2 link. &nbsp;I don't think we've considered the case where they =
are<br>
not on the same link.<br>
<br>
We have said that for cases where there are multiple layers of =
routers,<br>
that the other layers of router MUST pick the right exit router =
based<br>
upon source IP, so I think that as long as Router 2 can find a path =
to<br>
Router 1, it can work even when Router 1 and Router 2 are not on the<br>
same link.<br>
<br>
The source-address redirect is necessary only so that we can avoid<br>
imposing a new requirement on the hosts which might be on that =
layer-2<br>
link.<br>
<br>
 &nbsp; &nbsp;Guillaume&gt; If so, do you planned to have tunnels =
between<br>
 &nbsp; &nbsp;Guillaume&gt; home gateways ? Are we sure that ISPs behind =
the home<br>
 &nbsp; &nbsp;Guillaume&gt; gateway will accept to cooperate with each =
other (I said<br>
 &nbsp; &nbsp;Guillaume&gt; that because in France, home gateways are =
mainly<br>
 &nbsp; &nbsp;Guillaume&gt; given/lend by ISPs, and i'm not sure they =
will be willing<br>
 &nbsp; &nbsp;Guillaume&gt; to share something with another ISP)?<br>
<br>
No, there are no tunnels across the Internet.<br>
The traffic is redirected within the home.<br>
<br>
If the ISP provided home router can't speak homenet, then I guess it<br>
won't get the right logo on it.<br>
<div><div><br>
</div></div></blockquote></div><br>Ok, I understand now. I did not get =
that you assumed that both home gateways were on the same link. It is =
true that if they are on the same link you can forward the packet to the =
other one. However, if it's not the case and that you need to send back =
a packet to the right CPE, you somehow will have to encapsulate this =
packet so that it can be routed to the other CPE (that why I was talking =
about tunnel between CPE previously). <br>


<br>According to me, but maybe i'm wrong, it's a bit late to do the =
source address routing in the CPE, especially if we are in a complex =
topology (I was assuming that there would be other router inside the =
home network (other than the CPE, like in the figure 3 of the =
draft-chown-homenet-arch-01)). In fact, if I have a home network with =
the following topology:<br>


<br>---------- &nbsp;&nbsp; =
---------------------&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; ------ =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
-----&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp;&nbsp; =
------&nbsp; &nbsp; &nbsp;&nbsp; ---------------------&nbsp;&nbsp;&nbsp; =
----------<br>| ISP A | - | CPE Router A | --- | R1 | ------ | R2 | =
------ | R3 | --- | CPE Router B | - | ISP B |<br>


---------- &nbsp;&nbsp; ---------------------&nbsp;  =
&nbsp;&nbsp;&nbsp;&nbsp; ------ =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -----&nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp;&nbsp; ------&nbsp; &nbsp; &nbsp;&nbsp; =
---------------------&nbsp;&nbsp;&nbsp; =
----------<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |<br>

=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; -------<br>
=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; | Host =
|<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp; -------<br><ol><li>Case 1: CPE Routers are the only one =
doing the source address routing (I assume it's what you were =
describing)<br>


If the Host sends a packet, and that this packet, which actually belongs =
to CPE Router B, is routed to the CPE Router A. CPE Router A will have =
to forward it all the way back to CPE Router B.<br><br></li><li>Case 2: =
Some Interior Routers are doing the source address routing (I think that =
not all the interior router should do it though)<br>


If the Host sends the same packet, R3 will directly see that to avoid =
ingress filtering it has to send it to CPE Router B.</li></ol>As long as =
the topology is simple (no interior router) or that CPEs are on the same =
link, case 1 is fine. However, if we are in a more complex topology, i =
think case 2 is the most appropriate. And if interior routers are doing =
the source address routing there is no need for the CPE to do it, unless =
it had Hosts directly connected to =
it.<br></blockquote><div><br></div><div>If part of the routers do SA =
routing, doensn't that look loopy?</div><div><br></div><div>I say all =
routers have the same forwarding algorithm.</div><div>Two methods: CPE =
redirects packets to right "other CPE" with tunnel (or RH). Or all =
routers send packets to correct CPE in the first place. Latter looks =
better to me. Time to resubmit&nbsp;draft-boot-brdp-based-routing, I =
think.</div><div><br></div><div>Teco</div><div><br></div><br><blockquote =
type=3D"cite">
<br>
<br>-- <br>Guillaume HABAULT<br>PhD Student<br>Institut TELECOM / =
TELECOM Bretagne<br><br><br>
_______________________________________________<br>homenet mailing =
list<br><a =
href=3D"mailto:homenet@ietf.org">homenet@ietf.org</a><br>https://www.ietf.=
org/mailman/listinfo/homenet<br></blockquote></div><br></body></html>=

--Apple-Mail=_2CF88800-57CD-4F28-A3D3-9A325704DE18--

From russw@riw.us  Fri Nov 18 05:26:33 2011
Return-Path: <russw@riw.us>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9CBF21F8B01 for <homenet@ietfa.amsl.com>; Fri, 18 Nov 2011 05:26:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.56
X-Spam-Level: 
X-Spam-Status: No, score=-2.56 tagged_above=-999 required=5 tests=[AWL=0.039,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R53S+-rklnLL for <homenet@ietfa.amsl.com>; Fri, 18 Nov 2011 05:26:28 -0800 (PST)
Received: from ecbiz91.inmotionhosting.com (ecbiz91.inmotionhosting.com [173.205.124.250]) by ietfa.amsl.com (Postfix) with ESMTP id CB7FC21F8B00 for <homenet@ietf.org>; Fri, 18 Nov 2011 05:26:28 -0800 (PST)
Received: from cpe-065-190-155-146.nc.res.rr.com ([65.190.155.146]:62699 helo=[192.168.100.52]) by ecbiz91.inmotionhosting.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <russw@riw.us>) id 1RROSZ-00008P-Sw for homenet@ietf.org; Fri, 18 Nov 2011 08:26:27 -0500
Message-ID: <4EC65CFF.30201@riw.us>
Date: Fri, 18 Nov 2011 08:26:23 -0500
From: Russ White <russw@riw.us>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: homenet@ietf.org
References: <CAKD1Yr3uSsNP4avZBdQE7YxFd7D_KOXBOCsfaRfvnWhJoLoY9Q@mail.gmail.com> <28079.1321370795@marajade.sandelman.ca> <3112C980-7FD1-4BE3-8494-3E89E8D40376@ericsson.com> <25559.1321397513@marajade.sandelman.ca> <C7AC72F4-51F4-49FD-B814-A82F383E76AB@tid.es>
In-Reply-To: <C7AC72F4-51F4-49FD-B814-A82F383E76AB@tid.es>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - ecbiz91.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - riw.us
Subject: Re: [homenet] Comments on draft-acee-ospf-ospfv3-autoconfig-00
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 18 Nov 2011 13:26:34 -0000

> When it comes to wired connections why don't we consider both closed and guest access as in the wireless case? In a densely connected home, some wired points could be intended to be used by, say, someone coming to make some maintenance work…

I think this is a possible requirement, but... I don't know how you're
going to know what's guest and what's not. I suppose you could do
something like the "plug this usb into your machine to gain access," or
something, but I'm not certain how we could solve this just on the
network side.

:-)

Russ


From mcr@sandelman.ca  Fri Nov 18 10:38:57 2011
Return-Path: <mcr@sandelman.ca>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6D4A11E80C3 for <homenet@ietfa.amsl.com>; Fri, 18 Nov 2011 10:38:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.914
X-Spam-Level: 
X-Spam-Status: No, score=-1.914 tagged_above=-999 required=5 tests=[AWL=0.040,  BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TQh2pWIYnci8 for <homenet@ietfa.amsl.com>; Fri, 18 Nov 2011 10:38:53 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id 29AD921F849C for <homenet@ietf.org>; Fri, 18 Nov 2011 10:38:53 -0800 (PST)
Received: from marajade.sandelman.ca (unknown [132.213.238.4]) by relay.sandelman.ca (Postfix) with ESMTPS id 086F2343D4; Fri, 18 Nov 2011 13:37:25 -0500 (EST)
Received: by marajade.sandelman.ca (Postfix, from userid 179) id 633C298CB5; Fri, 18 Nov 2011 13:38:33 -0500 (EST)
Received: from marajade.sandelman.ca (localhost [127.0.0.1]) by marajade.sandelman.ca (Postfix) with ESMTP id 58D4698CB2; Fri, 18 Nov 2011 13:38:33 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ca>
to: Ole Troan <ot@cisco.com>
In-Reply-To: <400C7BA2-3D4D-4663-9B3E-FA2E6C2D8992@cisco.com>
References: <4EC1D206.2070303@gmail.com> <3C716203-8579-41EA-98CE-6DC3BE9261D8@fugue.com> <FC520CA0-BAA4-4309-A878-CB40308F2562@cisco.com> <09215FB7-EA7A-4D9D-8772-737B79CBBD20@fugue.com> <4EC32B76.8080706@riw.us> <7DADF53B-56CA-47CC-BBDA-34300EE4D22D@fugue.com> <7D0889B6-7769-4F74-996D-08CDA02B3670@cisco.com> <84FD521E-D48C-41C9-935B-9B4695FB658D@cisco.com> <489BE869-79F9-40FC-96B1-6A190620B4CA@cisco.com> <7F630AC9-A369-48B8-BD8F-684C0AC1DDDA@fugue.com> <72EB15CA-CAB4-4A50-BAB4-E60176109AF5@cisco.com> <E34DB847-4FC9-4982-A609-B80707F61E45@fugue.com> <E5723B4B-BDE4-47F4-B560-1165F713D5E2@cisco.com> <46CB823A-3C53-4C32-A33C-498CA6413448@fugue.com> <17953.1321493297@marajade.sandelman.ca> <400C7BA2-3D4D-4663-9B3E-FA2E6C2D8992@cisco.com>
X-Mailer: MH-E 8.1; nmh 1.3-dev; XEmacs 21.4 (patch 22)
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Fri, 18 Nov 2011 13:38:33 -0500
Message-ID: <19855.1321641513@marajade.sandelman.ca>
Sender: mcr@sandelman.ca
Cc: "homenet@ietf.org" <homenet@ietf.org>
Subject: Re: [homenet] draft-baker-homenet-prefix-assignment
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 18 Nov 2011 18:38:57 -0000

--=-=-=
Content-Transfer-Encoding: quoted-printable


>>>>> "Ole" =3D=3D Ole Troan <ot@cisco.com> writes:
    >> Is there some reason that the flooding mechanism can't distribute
    >> the list of edge CPE routers, and then DHCPv6 can be used in
    >> unicast request/reply to ask those CPE routers for things.
    >>=20
    >> (I would even wonder if the CPE routers shouldn't be identified
    >> by their ULA rather than self-identifying by the address in the
    >> subnet the deal with)
    >>=20
    >> This is how I imagined the DHCPv6 PD mechanism working before
    >> draft-chakrabarti-homenet-prefix-alloc-01 was written, which
    >> imagined a strict hierarchal tree.

    Ole> that's how I imagined also.  DHCP PD on the edges. flooding
    Ole> protocol between all the internal routers. then hosts use
    Ole> RA/DHCP for addresses / other configurations to their onlink
    Ole> routers.

so, does this mean we have to write another draft to explain it?

=2D-=20
]       He who is tired of Weird Al is tired of life!           |  firewall=
s  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net archit=
ect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device dri=
ver[
   Kyoto Plus: watch the video <http://www.youtube.com/watch?v=3Dkzx1ycLXQS=
E>
	               then sign the petition.=20


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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iQEVAwUATsamKYCLcPvd0N1lAQJivQf9FydlIC5LBKapfHpgFr4kJG6P978Ujgon
oRblZvOYQsuRgoZqigIeTwoGo8xSdTN00r9tPgV1LoUtEZT0cjvzl+DGN0n8epb4
+otkXWqkkmdPs1QQfe7WI26a6andA9Ua83vgT3AWb2mDxX99A353dYAPW20IEHdI
UJi2F4CNN+rQbfgP3Q3z4R0i55nGP5PzJ1N+1wCMnYKyBufl5nymq6s54HtRER4C
ss+8WU2WrZbC2iVS9V2B2Gac/2Rzt8JWCBmXQfB7e31zqu3Tfqdi5EYHugIjfPZu
o1wc9bHsobnZr97e3iTCZQMCdpyw6bClmMCHQBDSGnFPXOOFPzAqhw==
=hIjv
-----END PGP SIGNATURE-----
--=-=-=--

From mcr@sandelman.ca  Fri Nov 18 10:46:01 2011
Return-Path: <mcr@sandelman.ca>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 042AE21F85C7 for <homenet@ietfa.amsl.com>; Fri, 18 Nov 2011 10:46:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.916
X-Spam-Level: 
X-Spam-Status: No, score=-1.916 tagged_above=-999 required=5 tests=[AWL=0.038,  BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u-02SATwbcJA for <homenet@ietfa.amsl.com>; Fri, 18 Nov 2011 10:46:00 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id 664C321F8562 for <homenet@ietf.org>; Fri, 18 Nov 2011 10:46:00 -0800 (PST)
Received: from marajade.sandelman.ca (unknown [132.213.238.4]) by relay.sandelman.ca (Postfix) with ESMTPS id 7653734419 for <homenet@ietf.org>; Fri, 18 Nov 2011 13:44:33 -0500 (EST)
Received: by marajade.sandelman.ca (Postfix, from userid 179) id 844E398CB5; Fri, 18 Nov 2011 13:45:41 -0500 (EST)
Received: from marajade.sandelman.ca (localhost [127.0.0.1]) by marajade.sandelman.ca (Postfix) with ESMTP id 7CC0A98CB2 for <homenet@ietf.org>; Fri, 18 Nov 2011 13:45:41 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ca>
To: homenet@ietf.org
In-Reply-To: <CA+XPzSb-n=8Ss-OH3TzMXTetwqDJM9_YuvMFxKiWTbJ5fVz3UA@mail.gmail.com>
References: <DCC302FAA9FE5F4BBA4DCAD46569377914518AFAE5@PRVPEXVS03.corp.twcable.com> <4EB583C8.5030907@piuha.net> <13027.1320680393@marajade.sandelman.ca> <BDF2740C082F6942820D95BAEB9E1A845A9789@XMB-AMS-108.cisco.com> <CA+XPzSY8cC_PyhcMNqhk4+B6tghp8Dpy2-3aMPZmyVRP=AWnaA@mail.gmail.com> <3512.1321317664@marajade.sandelman.ca> <CA+XPzSaeg=pqmdSVXr+BQvS2D0+iVqN-q7e4dJoUtA=eA38vGA@mail.gmail.com> <32238.1321463734@marajade.sandelman.ca> <CA+XPzSb-n=8Ss-OH3TzMXTetwqDJM9_YuvMFxKiWTbJ5fVz3UA@mail.gmail.com>
X-Mailer: MH-E 8.1; nmh 1.3-dev; XEmacs 21.4 (patch 22)
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Fri, 18 Nov 2011 13:45:41 -0500
Message-ID: <20861.1321641941@marajade.sandelman.ca>
Sender: mcr@sandelman.ca
Subject: Re: [homenet] more comments on draft-arkko-homenet-prefix-assignment
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 18 Nov 2011 18:46:01 -0000

--=-=-=
Content-Transfer-Encoding: quoted-printable


>>>>> "Guillaume" =3D=3D Guillaume Habault <guillaume.habault@gmail.com> wr=
ites:
    Guillaume> If so, do you planned to have tunnels between home
    Guillaume> gateways ? Are we sure that ISPs behind the home gateway
    Guillaume> will accept to cooperate with each other (I said that
    Guillaume> because in France, home gateways are mainly given/lend by
    Guillaume> ISPs, and i'm not sure they will be willing to share
    Guillaume> something with another ISP)?
    >> No, there are no tunnels across the Internet.  The traffic is
    >> redirected within the home.
    >>=20
    >> If the ISP provided home router can't speak homenet, then I guess
    >> it won't get the right logo on it.

    Guillaume> Ok, I understand now. I did not get that you assumed that
    Guillaume> both home gateways were on the same link. It is true that
    Guillaume> if they are on the same link you can forward the packet
    Guillaume> to the other one. However, if it's not the case and that
    Guillaume> you need to send back a packet to the right CPE, you
    Guillaume> somehow will have to encapsulate this packet so that it
    Guillaume> can be routed to the other CPE (that why I was talking
    Guillaume> about tunnel between CPE previously).

If the two links are not on the same link, then the problem we have is
finding the right router that can send the traffic out.=20=20

We only have to do this for traffic originating on the local link from
hosts on that local link.  We likely also have to do this for traffic to
other links in the homenet as well, as the hosts on the local link won't
have the complete routing table.

For traffic within the homenet, we do normal destination address
routing, and our routing protocol tells us how to do this.   For traffic
out to the other ISP, we have to figure out which is the correct exit
router, and find a route to that CPE router's inside address in our
routing table, and then we can pick the correct direction to forward.

As all homenet routers are expected to do this same source address
routing, I don't think we a tunnel to the exit router.=20=20=20

However, it might be more resilient to pop the packet into an IPIP
header and address the ULA of the inside of the correct CPE router.
I think that we will need keep this option open as a MAY pending
implementation experience.  That means that we need to write a MUST
about decapsulating things to your ULA address in IPIP.

=2D-=20
]       He who is tired of Weird Al is tired of life!           |  firewall=
s  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net archit=
ect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device dri=
ver[
   Kyoto Plus: watch the video <http://www.youtube.com/watch?v=3Dkzx1ycLXQS=
E>
	               then sign the petition.=20

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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iQEVAwUATsan1YCLcPvd0N1lAQI/0Af7BNL4IV/goyPsD+j+d7cXxPSseA7G6kRZ
VDEqIMhDtyp0dBalir53Rjz0K2lyVVmf2Uw79dnb0Jacv8icP4hXfXvUQ5wggj82
r7Vde8xjiSTPvfoKtjoC1bqhJUZiH/+WMbo9OoQGIkptacRHEt8RA4yuIq3g+vgo
p87RF4r+uHnusCcMcKrMyBKfVS39nd/5LGxt2WUZKiOmjz64lIYws2xtaIlmtqw4
FNsk252gkssO75/Zt5KsndXJPrHDtuQMCW5k2xIufusPn/Fj1vVSEm/AEufj/UEh
ab59et+VN/jPMOUH0PjkCeKUwm+Kpv6R/l5slkxS6D3o5VfdKdcp7A==
=SD29
-----END PGP SIGNATURE-----
--=-=-=--

From mcr@sandelman.ca  Fri Nov 18 11:05:11 2011
Return-Path: <mcr@sandelman.ca>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E5D61F0C34 for <homenet@ietfa.amsl.com>; Fri, 18 Nov 2011 11:05:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.918
X-Spam-Level: 
X-Spam-Status: No, score=-1.918 tagged_above=-999 required=5 tests=[AWL=0.036,  BAYES_00=-2.599, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BfvkWxOCpJPS for <homenet@ietfa.amsl.com>; Fri, 18 Nov 2011 11:05:06 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id 64D1F1F0C6A for <homenet@ietf.org>; Fri, 18 Nov 2011 11:05:06 -0800 (PST)
Received: from marajade.sandelman.ca (unknown [132.213.238.4]) by relay.sandelman.ca (Postfix) with ESMTPS id C269B343E8; Fri, 18 Nov 2011 14:03:39 -0500 (EST)
Received: by marajade.sandelman.ca (Postfix, from userid 179) id 4ED0498CB5; Fri, 18 Nov 2011 14:04:48 -0500 (EST)
Received: from marajade.sandelman.ca (localhost [127.0.0.1]) by marajade.sandelman.ca (Postfix) with ESMTP id 4C0B698CB2; Fri, 18 Nov 2011 14:04:48 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ca>
To: homenet@ietf.org
In-Reply-To: <4EC65CFF.30201@riw.us>
References: <CAKD1Yr3uSsNP4avZBdQE7YxFd7D_KOXBOCsfaRfvnWhJoLoY9Q@mail.gmail.com> <28079.1321370795@marajade.sandelman.ca> <3112C980-7FD1-4BE3-8494-3E89E8D40376@ericsson.com> <25559.1321397513@marajade.sandelman.ca> <C7AC72F4-51F4-49FD-B814-A82F383E76AB@tid.es> <4EC65CFF.30201@riw.us>
X-Mailer: MH-E 8.1; nmh 1.3-dev; XEmacs 21.4 (patch 22)
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Fri, 18 Nov 2011 14:04:48 -0500
Message-ID: <23804.1321643088@marajade.sandelman.ca>
Sender: mcr@sandelman.ca
Cc: Russ White <russw@riw.us>
Subject: Re: [homenet] Comments on draft-acee-ospf-ospfv3-autoconfig-00
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 18 Nov 2011 19:05:11 -0000

--=-=-=
Content-Transfer-Encoding: quoted-printable


>>>>> "Russ" =3D=3D Russ White <russw@riw.us> writes:
    >> When it comes to wired connections why don't we consider both
    >> closed and guest access as in the wireless case? In a densely
    >> connected home, some wired points could be intended to be used
    >> by, say, someone coming to make some maintenance work=85

    Russ> I think this is a possible requirement, but... I don't know
    Russ> how you're going to know what's guest and what's not. I
    Russ> suppose you could do something like the "plug this usb into
    Russ> your machine to gain access," or something, but I'm not
    Russ> certain how we could solve this just on the network side.

I think that it's entirely reasonable that some parts of the house
(for instance Fred Baker's home office) would refuse access to his wired
network unless the device authenticated, and if they refused, the switch
would drop them onto a guest network.

This is relatively common deployed 802.1x.  While this switch (and the
radius server behind it) won't be present at Grandma's house, I've
noticed it's available on inexpensive managed switches made by Fred's
preferred network supplier.=20

Or, to put it another way: if you need wired security, we have it,
and homenet doesn't need to deal with this.  If you need to plug
additional homenet routers into the secured wire, then they need to get
past the wired security first.

=2D-=20
]       He who is tired of Weird Al is tired of life!           |  firewall=
s  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net archit=
ect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device dri=
ver[
   Kyoto Plus: watch the video <http://www.youtube.com/watch?v=3Dkzx1ycLXQS=
E>
	               then sign the petition.=20



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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iQEVAwUATsasUICLcPvd0N1lAQK11gf9Gv4ZRRBI4lhwOHJOnyglNXHQ2cnKkG/H
mmPEe7oisOYZrtzaHLW8HKNLRfdPfDLe4GI7TFYFl8QT7AHbjbMofF0a55Q/g8BJ
OIsPymnjNYWchc8jZUqdWArNkNiPvtzRcmx0rvBfT/SFa/4DsV+tjA6M3MLEB75q
RaiyjGLPLb2zNzkMbWPjXh7BYn8+kSwkJDJtDAfga2TRoUXqh24NyJn2TbZM7wsr
58LQA/6HkcRVHMdafGu5OAKO7mONGRuSKe0TmdKexo5+Korj+XA50ZoNPJE0jPEH
8CgiumldkMlG6SU38bK49YmV/1JK5uf7l2r4/swamjd9jhJL8LYcjg==
=zkZj
-----END PGP SIGNATURE-----
--=-=-=--

From teco@inf-net.nl  Fri Nov 18 23:21:43 2011
Return-Path: <teco@inf-net.nl>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A8DD1F0C60 for <homenet@ietfa.amsl.com>; Fri, 18 Nov 2011 23:21:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HuCCcM8FybyT for <homenet@ietfa.amsl.com>; Fri, 18 Nov 2011 23:21:42 -0800 (PST)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id 6AFB01F0C52 for <homenet@ietf.org>; Fri, 18 Nov 2011 23:21:41 -0800 (PST)
Received: by bkbzv15 with SMTP id zv15so5017211bkb.31 for <homenet@ietf.org>; Fri, 18 Nov 2011 23:21:41 -0800 (PST)
Received: by 10.204.156.141 with SMTP id x13mr6527987bkw.54.1321687300758; Fri, 18 Nov 2011 23:21:40 -0800 (PST)
Received: from [10.87.20.8] ([80.187.147.86]) by mx.google.com with ESMTPS id w11sm7835838fad.7.2011.11.18.23.21.37 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 18 Nov 2011 23:21:40 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Teco Boot <teco@inf-net.nl>
In-Reply-To: <20861.1321641941@marajade.sandelman.ca>
Date: Sat, 19 Nov 2011 08:21:37 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <3E2F80D5-0DB2-43A8-BA8F-DAF6E41A9320@inf-net.nl>
References: <DCC302FAA9FE5F4BBA4DCAD46569377914518AFAE5@PRVPEXVS03.corp.twcable.com> <4EB583C8.5030907@piuha.net> <13027.1320680393@marajade.sandelman.ca> <BDF2740C082F6942820D95BAEB9E1A845A9789@XMB-AMS-108.cisco.com> <CA+XPzSY8cC_PyhcMNqhk4+B6tghp8Dpy2-3aMPZmyVRP=AWnaA@mail.gmail.com> <3512.1321317664@marajade.sandelman.ca> <CA+XPzSaeg=pqmdSVXr+BQvS2D0+iVqN-q7e4dJoUtA=eA38vGA@mail.gmail.com> <32238.1321463734@marajade.sandelman.ca> <CA+XPzSb-n=8Ss-OH3TzMXTetwqDJM9_YuvMFxKiWTbJ5fVz3UA@mail.gmail.com> <20861.1321641941@marajade.sandelman.ca>
To: Michael Richardson <mcr@sandelman.ca>
X-Mailer: Apple Mail (2.1251.1)
Cc: homenet@ietf.org
Subject: Re: [homenet] more comments on draft-arkko-homenet-prefix-assignment
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 19 Nov 2011 07:21:43 -0000

Op 18 nov. 2011, om 19:45 heeft Michael Richardson het volgende =
geschreven:

>=20
>>>>>> "Guillaume" =3D=3D Guillaume Habault =
<guillaume.habault@gmail.com> writes:
>    Guillaume> If so, do you planned to have tunnels between home
>    Guillaume> gateways ? Are we sure that ISPs behind the home gateway
>    Guillaume> will accept to cooperate with each other (I said that
>    Guillaume> because in France, home gateways are mainly given/lend =
by
>    Guillaume> ISPs, and i'm not sure they will be willing to share
>    Guillaume> something with another ISP)?
>>> No, there are no tunnels across the Internet.  The traffic is
>>> redirected within the home.
>>>=20
>>> If the ISP provided home router can't speak homenet, then I guess
>>> it won't get the right logo on it.
>=20
>    Guillaume> Ok, I understand now. I did not get that you assumed =
that
>    Guillaume> both home gateways were on the same link. It is true =
that
>    Guillaume> if they are on the same link you can forward the packet
>    Guillaume> to the other one. However, if it's not the case and that
>    Guillaume> you need to send back a packet to the right CPE, you
>    Guillaume> somehow will have to encapsulate this packet so that it
>    Guillaume> can be routed to the other CPE (that why I was talking
>    Guillaume> about tunnel between CPE previously).
>=20
> If the two links are not on the same link, then the problem we have is
> finding the right router that can send the traffic out. =20
>=20
> We only have to do this for traffic originating on the local link from
> hosts on that local link.  We likely also have to do this for traffic =
to
> other links in the homenet as well, as the hosts on the local link =
won't
> have the complete routing table.
>=20
> For traffic within the homenet, we do normal destination address
> routing, and our routing protocol tells us how to do this.   For =
traffic
> out to the other ISP, we have to figure out which is the correct exit
> router, and find a route to that CPE router's inside address in our
> routing table, and then we can pick the correct direction to forward.
>=20
> As all homenet routers are expected to do this same source address
> routing, I don't think we a tunnel to the exit router.  =20
>=20
> However, it might be more resilient to pop the packet into an IPIP
> header and address the ULA of the inside of the correct CPE router.
> I think that we will need keep this option open as a MAY pending
> implementation experience.  That means that we need to write a MUST
> about decapsulating things to your ULA address in IPIP.

Some basic stuff for this is implemented in olsrd (olsr.org), in the =
Smart Gateway facility.
I can't see why inside address of border needs to be ULA.
Since when might tunnels be "more resilient"? :-)

Teco

>=20
> --=20
> ]       He who is tired of Weird Al is tired of life!           |  =
firewalls  [
> ]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net =
architect[
> ] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ =
|device driver[
>   Kyoto Plus: watch the video =
<http://www.youtube.com/watch?v=3Dkzx1ycLXQSE>
> 	               then sign the petition.=20
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet


From mcr@sandelman.ca  Sun Nov 20 17:51:21 2011
Return-Path: <mcr@sandelman.ca>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D13AF11E808D for <homenet@ietfa.amsl.com>; Sun, 20 Nov 2011 17:51:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.985
X-Spam-Level: 
X-Spam-Status: No, score=-0.985 tagged_above=-999 required=5 tests=[AWL=-0.520, BAYES_05=-1.11, HOST_MISMATCH_NET=0.311, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pGnzwOuuQD8I for <homenet@ietfa.amsl.com>; Sun, 20 Nov 2011 17:51:21 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [67.23.6.41]) by ietfa.amsl.com (Postfix) with ESMTP id 0C66B21F8AB0 for <homenet@ietf.org>; Sun, 20 Nov 2011 17:51:20 -0800 (PST)
Received: from marajade.sandelman.ca (wlan203.sandelman.ca [209.87.252.203]) by relay.sandelman.ca (Postfix) with ESMTPS id 5689B3416E; Sun, 20 Nov 2011 20:49:51 -0500 (EST)
Received: by marajade.sandelman.ca (Postfix, from userid 179) id 1F09498CC6; Sun, 20 Nov 2011 20:51:23 -0500 (EST)
Received: from marajade.sandelman.ca (localhost [127.0.0.1]) by marajade.sandelman.ca (Postfix) with ESMTP id 18156980ED; Sun, 20 Nov 2011 20:51:23 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ca>
To: Teco Boot <teco@inf-net.nl>
In-Reply-To: <3E2F80D5-0DB2-43A8-BA8F-DAF6E41A9320@inf-net.nl>
References: <DCC302FAA9FE5F4BBA4DCAD46569377914518AFAE5@PRVPEXVS03.corp.twcable.com> <4EB583C8.5030907@piuha.net> <13027.1320680393@marajade.sandelman.ca> <BDF2740C082F6942820D95BAEB9E1A845A9789@XMB-AMS-108.cisco.com> <CA+XPzSY8cC_PyhcMNqhk4+B6tghp8Dpy2-3aMPZmyVRP=AWnaA@mail.gmail.com> <3512.1321317664@marajade.sandelman.ca> <CA+XPzSaeg=pqmdSVXr+BQvS2D0+iVqN-q7e4dJoUtA=eA38vGA@mail.gmail.com> <32238.1321463734@marajade.sandelman.ca> <CA+XPzSb-n=8Ss-OH3TzMXTetwqDJM9_YuvMFxKiWTbJ5fVz3UA@mail.gmail.com> <20861.1321641941@marajade.sandelman.ca> <3E2F80D5-0DB2-43A8-BA8F-DAF6E41A9320@inf-net.nl>
X-Mailer: MH-E 8.1; nmh 1.3-dev; XEmacs 21.4 (patch 22)
Date: Sun, 20 Nov 2011 20:51:23 -0500
Message-ID: <22056.1321840283@marajade.sandelman.ca>
Sender: mcr@sandelman.ca
Cc: homenet@ietf.org
Subject: Re: [homenet] more comments on draft-arkko-homenet-prefix-assignment
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 21 Nov 2011 01:51:21 -0000

>>>>> "Teco" == Teco Boot <teco@inf-net.nl> writes:
    >> If the two links are not on the same link, then the problem we
    >> have is finding the right router that can send the traffic out.
    >> 
    >> We only have to do this for traffic originating on the local link
    >> from hosts on that local link.  We likely also have to do this
    >> for traffic to other links in the homenet as well, as the hosts
    >> on the local link won't have the complete routing table.
    >> 
    >> For traffic within the homenet, we do normal destination address
    >> routing, and our routing protocol tells us how to do this.  For
    >> traffic out to the other ISP, we have to figure out which is the
    >> correct exit router, and find a route to that CPE router's inside
    >> address in our routing table, and then we can pick the correct
    >> direction to forward.
    >> 
    >> As all homenet routers are expected to do this same source
    >> address routing, I don't think we a tunnel to the exit router.
    >> 
    >> However, it might be more resilient to pop the packet into an
    >> IPIP header and address the ULA of the inside of the correct CPE
    >> router.  I think that we will need keep this option open as a MAY
    >> pending implementation experience.  That means that we need to
    >> write a MUST about decapsulating things to your ULA address in
    >> IPIP.

    Teco> Some basic stuff for this is implemented in olsrd (olsr.org),
    Teco> in the Smart Gateway facility.  I can't see why inside address
    Teco> of border needs to be ULA.  Since when might tunnels be "more
    Teco> resilient"? :-)

When the number of internal LANs exceeds the number of subnets available
from a particular ISP.   

-- 
]       He who is tired of Weird Al is tired of life!           |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
   Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE>
	               then sign the petition. 

From lorenzo@google.com  Mon Nov 21 21:29:23 2011
Return-Path: <lorenzo@google.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F2B71F0C92 for <homenet@ietfa.amsl.com>; Mon, 21 Nov 2011 21:29:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.879
X-Spam-Level: 
X-Spam-Status: No, score=-102.879 tagged_above=-999 required=5 tests=[AWL=0.097, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BPptJA9EtdXV for <homenet@ietfa.amsl.com>; Mon, 21 Nov 2011 21:29:21 -0800 (PST)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id E42181F0C8C for <homenet@ietf.org>; Mon, 21 Nov 2011 21:29:20 -0800 (PST)
Received: by ghrr14 with SMTP id r14so4355920ghr.31 for <homenet@ietf.org>; Mon, 21 Nov 2011 21:29:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-system-of-record; bh=w3Bg9gfc7e9IM2/AJBrzST+LZy3rDNNiXWTFdSbkfzo=; b=xiUyb6DROB4i7O1e0Jlk2uQhO5qWHeHw8XKZw5iy+lEaJEZrkXEzCugztDVo5NQlRi zkDtOEiGOslgjiB4Aj0g==
Received: by 10.100.43.11 with SMTP id q11mr3906416anq.7.1321939760304; Mon, 21 Nov 2011 21:29:20 -0800 (PST)
Received: by 10.100.43.11 with SMTP id q11mr3906408anq.7.1321939760155; Mon, 21 Nov 2011 21:29:20 -0800 (PST)
MIME-Version: 1.0
Received: by 10.150.202.14 with HTTP; Mon, 21 Nov 2011 21:29:00 -0800 (PST)
In-Reply-To: <FF6FB9A0-9F91-4658-A265-BA200A0858AF@ericsson.com>
References: <CAKD1Yr3uSsNP4avZBdQE7YxFd7D_KOXBOCsfaRfvnWhJoLoY9Q@mail.gmail.com> <B3BE775A-4EBB-4C17-9EDC-7B9AFCB8867E@ericsson.com> <CAKD1Yr0MFdyBopr0E0WiebLSZ+M2J9vAi1U6b66VxhziE2XJpw@mail.gmail.com> <FF6FB9A0-9F91-4658-A265-BA200A0858AF@ericsson.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Tue, 22 Nov 2011 14:29:00 +0900
Message-ID: <CAKD1Yr2xPsdgSrGnx19PMZCda6cpwg-sTSoEOM9iP3bUgEAZuw@mail.gmail.com>
To: Acee Lindem <acee.lindem@ericsson.com>
Content-Type: multipart/alternative; boundary=0016e644cb6cd18e5c04b24c1550
X-System-Of-Record: true
Cc: "homenet@ietf.org" <homenet@ietf.org>, Jari Arkko <jari.arkko@piuha.net>
Subject: Re: [homenet] Comments on draft-acee-ospf-ospfv3-autoconfig-00
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 22 Nov 2011 05:29:23 -0000

--0016e644cb6cd18e5c04b24c1550
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Nov 15, 2011 at 12:11, Acee Lindem <acee.lindem@ericsson.com> wrote:

> > 3. Can we use normal LSAs to detect collisions? One idea would be "if
>> you see your own router ID in the list of neighbours of a network LSA or
>> router LSA, then there is a collision". Will that work? If so we wouldn't
>> need the hardware fingerprint at all.
>>
>> No. In an arbitrary topology, A router with a duplicate router-id can be
>> multiple hops away.
>>
>
> Yes, but router and network LSAs are flooded, so you'll hear them
> regardless of whether your duplicate is multiple hops away, no?
>
>
> Both OSPFv3 and OSPFv2 would consider an unrecognized self-originated LSA,
> i.e. having our Route-ID, as a stale LSA and purge it. This is a very basic
> mechanism of OSPF. I'd rather use a separate mechanism for duplicate
> Router-ID detection. I considered techniques involving the encoding some
> additional information in the Router-LSA but these all seemed to be hacked.
>

I think you misunderstood my suggestion.

I'm not suggesting that you listen for router and network LSAs with your
own router-ID. I'm suggesting that you listen for router and network LSAs
*that list your router-ID as a neighbour*. If you see one, but have no
neighbour relationship with the router-ID that originated the LSA, then
there is a collision.

Does that make sense?

 If the pre-shared key is hard-coded, it is no better than the OSPFv3
>> Interface Instance ID that is specified to prevent inadvertent adjacencies
>> with routers not supporting the auto-configuration. If configuration of a
>> pre-shared key is required, you no longer have auto-configuration.
>>
>
> Sorry, that wasn't clear. What I meant to say is that we should pick one
> scheme (e.g., HMAC-SHA) and stick to it; we shouldn't support multiple
> schemes as that will lead to interoperability issues for devices that use
> one scheme and devices that use another scheme.
>
>
> The OSPFv3 Instance ID is part of the base OSPFv3 specification and I
> think it is a very good mechanism to prevent inadvertent adjacencies. If we
> need real authentication, we'll need a pre-shared key. I don't see any
> advantage of authentication with a well-known pre-shared key to prevent
> inadvertent adjacencies.
>

Again, that wasn't clear. What I'm saying is that I think we need to pick
one mechanism (ipsec, SHA1, whatever - I don't even know what the possible
mechanisms are) to implement security. If the user enables security and
configures a key on all the network devices, we use that scheme to secure
the network. All homenet devices MUST support that scheme. If the user
doesn't enable security, then we can leave the packets unauthenticated.

Setting the instance ID to some random number will help in some cases, but
it won't help if by chance you happen to be adjacent to another network
that uses the same value. So I'm not sure if it's a good idea; people might
assume that since collisions are unlikely, then they don't need to support
them. But I don't really know enough about this to comment.

--0016e644cb6cd18e5c04b24c1550
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div class=3D"gmail_quote">On Tue, Nov 15, 2011 at 12:11, Acee Lindem <span=
 dir=3D"ltr">&lt;<a href=3D"mailto:acee.lindem@ericsson.com">acee.lindem@er=
icsson.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">

<div style=3D"word-wrap:break-word"><div><div class=3D"im"><blockquote type=
=3D"cite"><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>&g=
t; 3. Can we use normal LSAs to detect collisions? One idea would be &quot;=
if you see your own router ID in the list of neighbours of a network LSA or=
 router LSA, then there is a collision&quot;. Will that work? If so we woul=
dn&#39;t need the hardware fingerprint at all.<br>




<br>
</div>No. In an arbitrary topology, A router with a duplicate router-id can=
 be multiple hops away.<br></blockquote><div><br></div><div>Yes, but router=
 and network LSAs are flooded, so you&#39;ll hear them regardless of whethe=
r your duplicate is multiple hops away, no?</div>

</div></blockquote><div><br></div></div><div>Both OSPFv3 and OSPFv2 would c=
onsider an unrecognized self-originated LSA, i.e. having our Route-ID, as a=
 stale LSA and purge it. This is a very basic mechanism of OSPF. I&#39;d ra=
ther use a separate mechanism for duplicate Router-ID detection. I consider=
ed techniques involving the encoding some additional information in the Rou=
ter-LSA but these all seemed to be hacked.</div>

</div></div></blockquote><div><br></div><div>I think you misunderstood my s=
uggestion.</div><div><br></div><div>I&#39;m not suggesting that you listen =
for router and network LSAs with your own router-ID. I&#39;m suggesting tha=
t you listen for router and network LSAs *that list your router-ID as a nei=
ghbour*. If you see one, but have no neighbour relationship with the router=
-ID that originated the LSA, then there is a collision.</div>

<div><br></div><div>Does that make sense?</div><div><br></div><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;=
padding-left:1ex;"><div style=3D"word-wrap:break-word"><div><div class=3D"i=
m">
<blockquote type=3D"cite">
<div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margi=
n-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-=
width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;paddin=
g-left:1ex">

<div><span style=3D"background-color:transparent">If the pre-shared key is =
hard-coded, it is no better than the OSPFv3 Interface Instance ID that is s=
pecified to prevent inadvertent adjacencies with routers not supporting the=
 auto-configuration. If configuration of a pre-shared key is required, you =
no longer have auto-configuration.</span></div>



</blockquote><div><br></div><div>Sorry, that wasn&#39;t clear. What I meant=
 to say is that we should pick one scheme (e.g., HMAC-SHA) and stick to it;=
 we shouldn&#39;t support multiple schemes as that will lead to interoperab=
ility issues for devices that use one scheme and devices that use another s=
cheme.</div>



</div>
</blockquote><br></div></div><div>The OSPFv3 Instance ID is part of the bas=
e OSPFv3 specification and I think it is a very good mechanism to prevent i=
nadvertent adjacencies. If we need real authentication, we&#39;ll need a pr=
e-shared key. I don&#39;t see any advantage of authentication with a well-k=
nown pre-shared key to prevent inadvertent adjacencies.=A0</div>

</div></blockquote><div><br></div><div>Again, that wasn&#39;t clear. What I=
&#39;m saying is that I think we need to pick one mechanism (ipsec, SHA1, w=
hatever - I don&#39;t even know what the possible mechanisms are) to implem=
ent security. If the user enables security and configures a key on all the =
network devices, we use that scheme to secure the network. All homenet devi=
ces MUST support that scheme. If the user doesn&#39;t enable security, then=
 we can leave the packets unauthenticated.</div>

<div><br></div><div>Setting the instance ID to some random number will help=
 in some cases, but it won&#39;t help if by chance you happen to be adjacen=
t to another network that uses the same value. So I&#39;m not sure if it&#3=
9;s a good idea; people might assume that since collisions are unlikely, th=
en they don&#39;t need to support them. But I don&#39;t really know enough =
about this to comment.</div>

</div>

--0016e644cb6cd18e5c04b24c1550--

From lorenzo@google.com  Tue Nov 22 00:01:57 2011
Return-Path: <lorenzo@google.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D0E811E8156 for <homenet@ietfa.amsl.com>; Tue, 22 Nov 2011 00:01:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.811
X-Spam-Level: 
X-Spam-Status: No, score=-102.811 tagged_above=-999 required=5 tests=[AWL=0.009, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, SUBJECT_FUZZY_TION=0.156, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6OFlLL9ds5m5 for <homenet@ietfa.amsl.com>; Tue, 22 Nov 2011 00:01:55 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id DA86011E80A2 for <homenet@ietf.org>; Tue, 22 Nov 2011 00:01:54 -0800 (PST)
Received: by ywt34 with SMTP id 34so6737905ywt.31 for <homenet@ietf.org>; Tue, 22 Nov 2011 00:01:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=mime-version:from:date:message-id:subject:to:content-type :x-system-of-record; bh=JYESp+gCxOcFS5ABR4TglaWNB4fwbSyz/EnMRxnC4f8=; b=dolQjfQKsgaMavee04elcdBmpbG0GNwXQvhzJX9KY1C5SmHDIpqF2iYdONWjKOUEgJ lf/mksKc/HsvXiw2/76A==
Received: by 10.101.4.20 with SMTP id g20mr3970055ani.73.1321948914307; Tue, 22 Nov 2011 00:01:54 -0800 (PST)
Received: by 10.101.4.20 with SMTP id g20mr3970052ani.73.1321948914157; Tue, 22 Nov 2011 00:01:54 -0800 (PST)
MIME-Version: 1.0
Received: by 10.150.202.14 with HTTP; Tue, 22 Nov 2011 00:01:33 -0800 (PST)
From: Lorenzo Colitti <lorenzo@google.com>
Date: Tue, 22 Nov 2011 17:01:33 +0900
Message-ID: <CAKD1Yr3Y=EO9siQkAuZd7LtqsOT_8GswWkPOoiJEhtvnULcytw@mail.gmail.com>
To: homenet@ietf.org
Content-Type: multipart/alternative; boundary=001636c92af4708a2d04b24e3779
X-System-Of-Record: true
Subject: [homenet] Creating a security association via physical link + button
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 22 Nov 2011 08:01:58 -0000

--001636c92af4708a2d04b24e3779
Content-Type: text/plain; charset=ISO-8859-1

It would be cool if I could plug in a new router into my homenet, press a
special button on it and on the router I plug it into, and have the new
router download the homenet config (at least the routing protocol key, but
maybe other things like the wifi SSID) from the existing router.

The button would cause the existing router to make the information
available in the clear for, say, 30 seconds, and would cause the new router
to attempt to fetch it from a directly connected neighbour. The combination
of physically plugging something in and pressing the button might provide
enough security to defend against unintended pairings (e.g., because you
plugged something in to the wrong port; maybe to your neighbour's homenet).

I don't know how you would decide who is the "homenet" and who is the "new
router" though.

Comments?

--001636c92af4708a2d04b24e3779
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

It would be cool if I could plug in a new router into my homenet, press a s=
pecial button on it and on the router I plug it into, and have the new rout=
er download the homenet config (at least the routing protocol key, but mayb=
e other things like the wifi SSID) from the existing router.<div>

<br></div><div>The button would cause the existing router to make the infor=
mation available in the clear for, say, 30 seconds, and would cause the new=
 router to attempt to fetch it from a directly connected neighbour. The com=
bination of physically plugging something in and pressing the button might =
provide enough security to defend against unintended pairings (e.g., becaus=
e you plugged something in to the wrong port; maybe to your neighbour&#39;s=
 homenet).</div>

<div><br></div><div>I don&#39;t know how you would decide who is the &quot;=
homenet&quot; and who is the &quot;new router&quot; though.</div><div><br><=
/div><div>Comments?</div>

--001636c92af4708a2d04b24e3779--

From russw@riw.us  Tue Nov 22 04:42:47 2011
Return-Path: <russw@riw.us>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 337AC21F8DF1 for <homenet@ietfa.amsl.com>; Tue, 22 Nov 2011 04:42:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.488
X-Spam-Level: 
X-Spam-Status: No, score=-2.488 tagged_above=-999 required=5 tests=[AWL=-0.045, BAYES_00=-2.599, SUBJECT_FUZZY_TION=0.156]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zcys+aTaWA2h for <homenet@ietfa.amsl.com>; Tue, 22 Nov 2011 04:42:44 -0800 (PST)
Received: from ecbiz91.inmotionhosting.com (ecbiz91.inmotionhosting.com [173.205.124.250]) by ietfa.amsl.com (Postfix) with ESMTP id BFCF121F8D0A for <homenet@ietf.org>; Tue, 22 Nov 2011 04:42:44 -0800 (PST)
Received: from cpe-065-190-155-146.nc.res.rr.com ([65.190.155.146]:52426 helo=[192.168.100.52]) by ecbiz91.inmotionhosting.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <russw@riw.us>) id 1RSpgR-0007KO-Ta; Tue, 22 Nov 2011 07:42:43 -0500
Message-ID: <4ECB98BC.8070600@riw.us>
Date: Tue, 22 Nov 2011 07:42:36 -0500
From: Russ White <russw@riw.us>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Lorenzo Colitti <lorenzo@google.com>
References: <CAKD1Yr3Y=EO9siQkAuZd7LtqsOT_8GswWkPOoiJEhtvnULcytw@mail.gmail.com>
In-Reply-To: <CAKD1Yr3Y=EO9siQkAuZd7LtqsOT_8GswWkPOoiJEhtvnULcytw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - ecbiz91.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - riw.us
Cc: homenet@ietf.org
Subject: Re: [homenet] Creating a security association via physical link + button
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 22 Nov 2011 12:42:47 -0000

> It would be cool if I could plug in a new router into my homenet, press
> a special button on it and on the router I plug it into, and have the
> new router download the homenet config (at least the routing protocol
> key, but maybe other things like the wifi SSID) from the existing router.

This is, generally speaking, how current home routers work... And, I
think, it might be the only way to make a homenet work. The primary key
beyond this is a device being able to figure out "I'm an edge to the
outside world."

If we can sort these two problems, the rest of the problems are mostly a
matter of just thinking through the best solution...

:-)

Russ

From mellon@fugue.com  Tue Nov 22 06:54:35 2011
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 52F3A21F8D07 for <homenet@ietfa.amsl.com>; Tue, 22 Nov 2011 06:54:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.951
X-Spam-Level: 
X-Spam-Status: No, score=-1.951 tagged_above=-999 required=5 tests=[AWL=0.491,  BAYES_00=-2.599, HTML_MESSAGE=0.001, SUBJECT_FUZZY_TION=0.156]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zKUfO6ZJT4IV for <homenet@ietfa.amsl.com>; Tue, 22 Nov 2011 06:54:34 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id EF71D21F8CE1 for <homenet@ietf.org>; Tue, 22 Nov 2011 06:54:34 -0800 (PST)
Received: from [IPv6:2001:470:1f07:1486:a5ed:e487:c35e:62ae] (unknown [IPv6:2001:470:1f07:1486:a5ed:e487:c35e:62ae]) by toccata.fugue.com (Postfix) with ESMTPSA id 04C302380439; Tue, 22 Nov 2011 09:54:31 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: multipart/alternative; boundary="Apple-Mail=_F1B0B526-8DE3-41BC-A3A4-C6D7D62935EE"
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <4ECB98BC.8070600@riw.us>
Date: Tue, 22 Nov 2011 09:54:30 -0500
Message-Id: <ACDC3C9F-85D2-4AF6-AA8C-2A2E6EEDC8EE@fugue.com>
References: <CAKD1Yr3Y=EO9siQkAuZd7LtqsOT_8GswWkPOoiJEhtvnULcytw@mail.gmail.com> <4ECB98BC.8070600@riw.us>
To: Russ White <russw@riw.us>
X-Mailer: Apple Mail (2.1251.1)
Cc: homenet@ietf.org, Lorenzo Colitti <lorenzo@google.com>
Subject: Re: [homenet] Creating a security association via physical link + button
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 22 Nov 2011 14:54:35 -0000

--Apple-Mail=_F1B0B526-8DE3-41BC-A3A4-C6D7D62935EE
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Nov 22, 2011, at 7:42 AM, Russ White wrote:
> This is, generally speaking, how current home routers work... And, I
> think, it might be the only way to make a homenet work. The primary =
key
> beyond this is a device being able to figure out "I'm an edge to the
> outside world."

Yeah, I don't think either device decides that it is the homenet; =
rather, they are regularly dynamically discovering topology, and =
deciding what to do based on whether they are connected to an edge.   =
Possibly both devices are connected to an edge, and cooperate to do =
multihoming.


--Apple-Mail=_F1B0B526-8DE3-41BC-A3A4-C6D7D62935EE
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div>On Nov 22, 2011, at 7:42 AM, Russ White =
wrote:</div><blockquote type=3D"cite"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; font-family: Helvetica; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-align: -webkit-auto; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; ">This is, =
generally speaking, how current home routers work... And, I<br>think, it =
might be the only way to make a homenet work. The primary key<br>beyond =
this is a device being able to figure out "I'm an edge to the<br>outside =
world."</span></blockquote></div><br><div>Yeah, I don't think either =
device decides that it is the homenet; rather, they are regularly =
dynamically discovering topology, and deciding what to do based on =
whether they are connected to an edge. &nbsp; Possibly both devices are =
connected to an edge, and cooperate to do =
multihoming.</div><div><br></div></body></html>=

--Apple-Mail=_F1B0B526-8DE3-41BC-A3A4-C6D7D62935EE--

From acee.lindem@ericsson.com  Tue Nov 22 06:57:40 2011
Return-Path: <acee.lindem@ericsson.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C5B721F8E11 for <homenet@ietfa.amsl.com>; Tue, 22 Nov 2011 06:57:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.537
X-Spam-Level: 
X-Spam-Status: No, score=-6.537 tagged_above=-999 required=5 tests=[AWL=0.061,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yHpgQq+ApV-h for <homenet@ietfa.amsl.com>; Tue, 22 Nov 2011 06:57:39 -0800 (PST)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 82FC021F8D36 for <homenet@ietf.org>; Tue, 22 Nov 2011 06:57:39 -0800 (PST)
Received: from eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id pAMEvSxX032479; Tue, 22 Nov 2011 08:57:36 -0600
Received: from EUSAACMS0702.eamcs.ericsson.se ([169.254.1.25]) by eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) with mapi; Tue, 22 Nov 2011 09:57:31 -0500
From: Acee Lindem <acee.lindem@ericsson.com>
To: Lorenzo Colitti <lorenzo@google.com>
Date: Tue, 22 Nov 2011 09:57:28 -0500
Thread-Topic: Comments on draft-acee-ospf-ospfv3-autoconfig-00
Thread-Index: AcypJw8hoXC8qmZPSg6sxRlcFS8UKw==
Message-ID: <73AFFE73-6978-4320-A2EE-ED386B5D41EE@ericsson.com>
References: <CAKD1Yr3uSsNP4avZBdQE7YxFd7D_KOXBOCsfaRfvnWhJoLoY9Q@mail.gmail.com> <B3BE775A-4EBB-4C17-9EDC-7B9AFCB8867E@ericsson.com> <CAKD1Yr0MFdyBopr0E0WiebLSZ+M2J9vAi1U6b66VxhziE2XJpw@mail.gmail.com> <FF6FB9A0-9F91-4658-A265-BA200A0858AF@ericsson.com> <CAKD1Yr2xPsdgSrGnx19PMZCda6cpwg-sTSoEOM9iP3bUgEAZuw@mail.gmail.com>
In-Reply-To: <CAKD1Yr2xPsdgSrGnx19PMZCda6cpwg-sTSoEOM9iP3bUgEAZuw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/signed; boundary="Apple-Mail-16-69265508"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
Cc: "homenet@ietf.org" <homenet@ietf.org>, Jari Arkko <jari.arkko@piuha.net>
Subject: Re: [homenet] Comments on draft-acee-ospf-ospfv3-autoconfig-00
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 22 Nov 2011 14:57:40 -0000

--Apple-Mail-16-69265508
Content-Type: multipart/alternative;
	boundary=Apple-Mail-15-69265480


--Apple-Mail-15-69265480
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Nov 22, 2011, at 12:29 AM, Lorenzo Colitti wrote:

> On Tue, Nov 15, 2011 at 12:11, Acee Lindem <acee.lindem@ericsson.com> =
wrote:
>> > 3. Can we use normal LSAs to detect collisions? One idea would be =
"if you see your own router ID in the list of neighbours of a network =
LSA or router LSA, then there is a collision". Will that work? If so we =
wouldn't need the hardware fingerprint at all.
>>=20
>> No. In an arbitrary topology, A router with a duplicate router-id can =
be multiple hops away.
>>=20
>> Yes, but router and network LSAs are flooded, so you'll hear them =
regardless of whether your duplicate is multiple hops away, no?
>=20
> Both OSPFv3 and OSPFv2 would consider an unrecognized self-originated =
LSA, i.e. having our Route-ID, as a stale LSA and purge it. This is a =
very basic mechanism of OSPF. I'd rather use a separate mechanism for =
duplicate Router-ID detection. I considered techniques involving the =
encoding some additional information in the Router-LSA but these all =
seemed to be hacked.
>=20
> I think you misunderstood my suggestion.
>=20
> I'm not suggesting that you listen for router and network LSAs with =
your own router-ID. I'm suggesting that you listen for router and =
network LSAs *that list your router-ID as a neighbour*. If you see one, =
but have no neighbour relationship with the router-ID that originated =
the LSA, then there is a collision.
>=20
> Does that make sense?

I understand what you are proposing but it is contrary to the way OSPF =
floods, stores, and interprets LSAs. Only the most recent instance of =
every LSA is maintained and any uni-directional links are treated as =
stale and not used in the routing computation. So, it would be a very =
common event to receive an LSA containing a link to you but to which you =
no longer have a link. I agree one could probably come up with a =
heuristic that would be correct most of the time but why do this when a =
simple hardware fingerprint will do the trick without all the =
complexity.=20


>=20
>> If the pre-shared key is hard-coded, it is no better than the OSPFv3 =
Interface Instance ID that is specified to prevent inadvertent =
adjacencies with routers not supporting the auto-configuration. If =
configuration of a pre-shared key is required, you no longer have =
auto-configuration.
>>=20
>> Sorry, that wasn't clear. What I meant to say is that we should pick =
one scheme (e.g., HMAC-SHA) and stick to it; we shouldn't support =
multiple schemes as that will lead to interoperability issues for =
devices that use one scheme and devices that use another scheme.
>=20
> The OSPFv3 Instance ID is part of the base OSPFv3 specification and I =
think it is a very good mechanism to prevent inadvertent adjacencies. If =
we need real authentication, we'll need a pre-shared key. I don't see =
any advantage of authentication with a well-known pre-shared key to =
prevent inadvertent adjacencies.=20
>=20
> Again, that wasn't clear. What I'm saying is that I think we need to =
pick one mechanism (ipsec, SHA1, whatever - I don't even know what the =
possible mechanisms are) to implement security. If the user enables =
security and configures a key on all the network devices, we use that =
scheme to secure the network. All homenet devices MUST support that =
scheme. If the user doesn't enable security, then we can leave the =
packets unauthenticated.
>=20
> Setting the instance ID to some random number will help in some cases, =
but it won't help if by chance you happen to be adjacent to another =
network that uses the same value. So I'm not sure if it's a good idea; =
people might assume that since collisions are unlikely, then they don't =
need to support them. But I don't really know enough about this to =
comment.

I wasn't suggesting the instance ID would provide authentication - =
simply to prevent inadvertent adjacencies with routers not being =
auto-configured. Even with auto-configuration, I'm against making =
authentication a MUST. Since OSPFv3 only runs on a single link, a =
connected network must be compromised in order for a successful attack.=20=


Thanks,
Acee=20=

--Apple-Mail-15-69265480
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Nov 22, 2011, at 12:29 AM, Lorenzo Colitti wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div class="gmail_quote">On Tue, Nov 15, 2011 at 12:11, Acee Lindem <span dir="ltr">&lt;<a href="mailto:acee.lindem@ericsson.com">acee.lindem@ericsson.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">

<div style="word-wrap:break-word"><div><div class="im"><blockquote type="cite"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>&gt; 3. Can we use normal LSAs to detect collisions? One idea would be "if you see your own router ID in the list of neighbours of a network LSA or router LSA, then there is a collision". Will that work? If so we wouldn't need the hardware fingerprint at all.<br>




<br>
</div>No. In an arbitrary topology, A router with a duplicate router-id can be multiple hops away.<br></blockquote><div><br></div><div>Yes, but router and network LSAs are flooded, so you'll hear them regardless of whether your duplicate is multiple hops away, no?</div>

</div></blockquote><div><br></div></div><div>Both OSPFv3 and OSPFv2 would consider an unrecognized self-originated LSA, i.e. having our Route-ID, as a stale LSA and purge it. This is a very basic mechanism of OSPF. I'd rather use a separate mechanism for duplicate Router-ID detection. I considered techniques involving the encoding some additional information in the Router-LSA but these all seemed to be hacked.</div>

</div></div></blockquote><div><br></div><div>I think you misunderstood my suggestion.</div><div><br></div><div>I'm not suggesting that you listen for router and network LSAs with your own router-ID. I'm suggesting that you listen for router and network LSAs *that list your router-ID as a neighbour*. If you see one, but have no neighbour relationship with the router-ID that originated the LSA, then there is a collision.</div>

<div><br></div><div>Does that make sense?</div></div></blockquote><div><br></div><div>I understand what you are proposing but it is contrary to the way OSPF floods, stores, and interprets LSAs. Only the most recent instance of every LSA is maintained and any uni-directional links are treated as stale and not used in the routing computation. So, it would be a very common event to receive an LSA containing a link to you but to which you no longer have a link. I agree one could probably come up with a heuristic that would be correct most of the time but why do this when a simple hardware fingerprint will do the trick without all the complexity.&nbsp;</div><div><br></div><br><blockquote type="cite"><div class="gmail_quote"><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div style="word-wrap:break-word"><div><div class="im">
<blockquote type="cite">
<div class="gmail_quote"><blockquote class="gmail_quote" style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">

<div><span style="background-color:transparent">If the pre-shared key is hard-coded, it is no better than the OSPFv3 Interface Instance ID that is specified to prevent inadvertent adjacencies with routers not supporting the auto-configuration. If configuration of a pre-shared key is required, you no longer have auto-configuration.</span></div>



</blockquote><div><br></div><div>Sorry, that wasn't clear. What I meant to say is that we should pick one scheme (e.g., HMAC-SHA) and stick to it; we shouldn't support multiple schemes as that will lead to interoperability issues for devices that use one scheme and devices that use another scheme.</div>



</div>
</blockquote><br></div></div><div>The OSPFv3 Instance ID is part of the base OSPFv3 specification and I think it is a very good mechanism to prevent inadvertent adjacencies. If we need real authentication, we'll need a pre-shared key. I don't see any advantage of authentication with a well-known pre-shared key to prevent inadvertent adjacencies.&nbsp;</div>

</div></blockquote><div><br></div><div>Again, that wasn't clear. What I'm saying is that I think we need to pick one mechanism (ipsec, SHA1, whatever - I don't even know what the possible mechanisms are) to implement security. If the user enables security and configures a key on all the network devices, we use that scheme to secure the network. All homenet devices MUST support that scheme. If the user doesn't enable security, then we can leave the packets unauthenticated.</div>

<div><br></div><div>Setting the instance ID to some random number will help in some cases, but it won't help if by chance you happen to be adjacent to another network that uses the same value. So I'm not sure if it's a good idea; people might assume that since collisions are unlikely, then they don't need to support them. But I don't really know enough about this to comment.</div>

</div>
</blockquote></div><br><div>I wasn't suggesting the instance ID would provide authentication - simply to prevent inadvertent adjacencies with routers not being auto-configured. Even with auto-configuration, I'm against making authentication a MUST. Since OSPFv3 only runs on a single link, a connected network must be compromised in order for a successful attack.&nbsp;</div><div><br></div><div>Thanks,</div><div>Acee&nbsp;</div></body></html>
--Apple-Mail-15-69265480--

--Apple-Mail-16-69265508
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIM8jCCBDQw
ggMcoAMCAQICECFWwVQHDV12M/Sr0yNv0sYwDQYJKoZIhvcNAQEFBQAwOTERMA8GA1UECgwIRXJp
Y3Nzb24xJDAiBgNVBAMMG0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMTAeFw0xMDEwMDEyMDA0
NTlaFw0xMzEwMDEyMDA0NDhaMG8xETAPBgNVBAoMCEVyaWNzc29uMR8wHQYDVQQDDBZBY2VlIExp
bmRlbSBMaW5kZW0gSUlJMRAwDgYDVQQFEwdlYWxmbGluMScwJQYJKoZIhvcNAQkBFhhhY2VlLmxp
bmRlbUBlcmljc3Nvbi5jb20wgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAI/Dc9ALiZuBMyuv
bsc3eBxjXZpMi45Z0vzsUQZTJGTBeY7p9JsdzXC9J1uMisBxYVi39R3KJo6I4hXVp9wrA1rxh4AE
bnP1+Gxfpj33uWEFYbBnVAJkIWYWF7CYTn8Zm/yd13vPXtuGA6ESeLnnJafwC9Y0YwUQ+4HX7PNv
uauVAgMBAAGjggGEMIIBgDCBwAYDVR0fBIG4MIG1MIGyoIGvoIGshjdodHRwOi8vY3JsLnRydXN0
LnRlbGlhLmNvbS9Fcmljc3Nvbk5MSW5kaXZpZHVhbENBMDEuY3JshnFsZGFwOi8vbGRhcC50cnVz
dC50ZWxpYS5jb20vY249RXJpY3Nzb24lMjBOTCUyMEluZGl2aWR1YWwlMjBDQTAxLG89RXJpY3Nz
b24/Y2VydGlmaWNhdGVyZXZvY2F0aW9ubGlzdDtiaW5hcnk/YmFzZTAjBgNVHREEHDAagRhhY2Vl
LmxpbmRlbUBlcmljc3Nvbi5jb20wRgYDVR0gBD8wPTA7BgYqhXBrAQEwMTAvBggrBgEFBQcCARYj
aHR0cDovL3d3dy5lcmljc3Nvbi5jb20vbGVnYWwuc2h0bWwwHQYDVR0OBBYEFAgOzAPuplmPr7C1
BTqV94OyqUdhMB8GA1UdIwQYMBaAFJYnw7jepV9dRD45UuVFsXZfYzCbMA4GA1UdDwEB/wQEAwIF
oDANBgkqhkiG9w0BAQUFAAOCAQEAE1gyNW6c2t/YsLxW5sm67+gVGK0Lnge4ub+k8dgGrK7Mj7em
nkOIFkjdv/tqdJ/SoUy/WEkBXba2TfpZ+lfluMgLYux1vSvqBUxYBsUHeNth2Q/Y6A9sCaDTBPlK
vZ2jLz814NavrVfgTCLdxX6zNtGdwzhviz+FyqyxYF43Q86RP8Gd/Npaz1W8pmYAHm0+lezuTx5k
F3Av3+SaZ/MR6s+RWuXEIdED36ajeQz+OG8Mh3nplofzdrOeoWGDz53YlfRhgj+TXo+H1lclZAvD
WVaMMXPdb27h9Hngsq87dkCW9uAyv8DI993rdhqzlEgUyQIL32icAXfTmTYgoGPOwjCCBEUwggMt
oAMCAQICEBPJ6v/eJq2p3KTKI4GDR+MwDQYJKoZIhvcNAQEFBQAwRDEaMBgGA1UECgwRVGVsaWFT
b25lcmEgR3JvdXAxJjAkBgNVBAMMHVRlbGlhU29uZXJhIFB1YmxpYyBSb290IENBIHYxMB4XDTA2
MTAwNjEwMDA1M1oXDTE2MTAwMjA1MDQxN1owOTERMA8GA1UECgwIRXJpY3Nzb24xJDAiBgNVBAMM
G0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoC
ggEBALYQd+Q1HuuHxDyNGFlEPzCxuPPFO5W2xyr+nqCVnNJ4QYFe1HACqavqNLwUGIqIEyHv1rLn
fub9LBc7dQpRHjl/dggin0ONOFJ36nbGEbfHjLJz2BzOWvwl84Sc+Fx09IrDU/SZSWFSfhqTu3TT
39h79brHdRkdPBUgBYgsiFKriHI0TjP5G8628H27BDzqUpzGLSYWgt6/tpwuOH5lcfNfHWMcCYXR
lobv0Klu8lxG5amWqAnqrH6ECOyYJTRbHTsaTIZOHy9Qw/0eXPujKT7tU5xxSI2SdceJqzUbAz2o
FRQ6Px7/GydpM/Rl+qYoGPcauHUL1aSeVJZqDFqcIF0CAwEAAaOCATwwggE4MBIGA1UdEwEB/wQI
MAYBAf8CAQAwRgYDVR0gBD8wPTA7BgcqhXAjAgEBMDAwLgYIKwYBBQUHAgEWImh0dHBzOi8vcmVw
b3NpdG9yeS50cnVzdC50ZWxpYS5jb20wgYkGA1UdHwSBgTB/MH2ge6B5hndsZGFwOi8vbGRhcC50
cnVzdC50ZWxpYS5jb20vY249VGVsaWFTb25lcmElMjBQdWJsaWMlMjBSb290JTIwQ0ElMjB2MSxv
PVRlbGlhU29uZXJhJTIwR3JvdXA/YXV0aG9yaXR5cmV2b2NhdGlvbmxpc3Q/YmFzZTAOBgNVHQ8B
Af8EBAMCAQYwHQYDVR0OBBYEFJYnw7jepV9dRD45UuVFsXZfYzCbMB8GA1UdIwQYMBaAFEXb8I+4
GmKhqCMbY4g4o9vgGmLxMA0GCSqGSIb3DQEBBQUAA4IBAQB2AEoqQz+M3Ra9alkpn/YnwhXIv6tP
jhUvSuNs00Nhd0T9XhlIU3a65CaB/UKSqnayE0t7Q0Qq3r+x/GK3in/mik8i/PK2/q8HutzYFSzz
6Npztpo2JG7AEKOJPVaeebjng45m6vNC7RIfzU9sG2LBR/hewS8s6dFFn70w795xUwJBWZ67OzIK
XrIVVvHTOYpbWA+MESKAXwFhnVONrOTWlVwrMUi4HbiPWpOk+xQbgehCEi7mu3cXsaU1Xq3kMXui
NuC7VKoob8mFO9o9RT+dlirD2uRXwNpvCu3but6Kyhu0+nvy2iXGKjdlxlWTsdDyulXYz+OYCMZ9
lFWRzMIPMIIEbTCCA1WgAwIBAgIRAJywjASay5cieGNithuGWj0wDQYJKoZIhvcNAQEFBQAwOjEZ
MBcGA1UEChMQUlNBIFNlY3VyaXR5IEluYzEdMBsGA1UECxMUUlNBIFNlY3VyaXR5IDIwNDggVjMw
HhcNMDYxMDMxMjA0MjI3WhcNMTYxMTAxMTU0MjI1WjBEMRowGAYDVQQKDBFUZWxpYVNvbmVyYSBH
cm91cDEmMCQGA1UEAwwdVGVsaWFTb25lcmEgUHVibGljIFJvb3QgQ0EgdjEwggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQDKTxADapCAq3mplX4R4gNt+WZe5QKGnaVEQSyY7lICKF5DuVdW
PMLHDjzhw5IzDd860ZZx/0VrhGB3DmP4SDIWCKo2PxvY5NckdBWPWp/T2uaQdOAwgqHpN0pe1X7/
jel59WsWYXKGg/81Wth73ZK/geE7Gz9Pvj1LU6N4YhLMgooxKnCS+ZjB5icWAg+Qd1QpQhF46H1i
bp6LsBWDp56MPpg8F5X6y7MGVcKYLdnLOPs84uxRW9qs1kBopzQBj6s5SyVh8A+j5liDBjghXYpw
/+paGEdqHPeSFYxZKeJatmjEKLYlxcZWRKf436KvQA9jBhMEmytMNbGicR1mRH6tAgMBAAGjggFi
MIIBXjAfBgNVHSMEGDAWgBQHw1EwpKrpRa41JPr/JCwz0LGdjDAdBgNVHQ4EFgQURdvwj7gaYqGo
IxtjiDij2+AaYvEwEgYDVR0TAQH/BAgwBgEB/wIBBDCBhQYDVR0gBH4wfDA9BgkqhkiG9w0FBgEw
MDAuBggrBgEFBQcCARYiaHR0cHM6Ly9yZXBvc2l0b3J5LnRydXN0LnRlbGlhLmNvbTA7BgcqhXAj
AgEBMDAwLgYIKwYBBQUHAgEWImh0dHBzOi8vcmVwb3NpdG9yeS50cnVzdC50ZWxpYS5jb20wcAYD
VR0fBGkwZzBloGOgYYZfaHR0cDovL3d3dy5yc2FzZWN1cml0eS5jb20vcHJvZHVjdHMva2Vvbi9y
ZXBvc2l0b3J5L2NlcnRpZmljYXRlX3N0YXR1cy9SU0FfU2VjdXJpdHlfMjA0OF92My5DUkwwDgYD
VR0PAQH/BAQDAgEGMA0GCSqGSIb3DQEBBQUAA4IBAQAEXpos2CnIm7/872ytSrEHWZgvhOUEkUm2
5PWf/XkWko41TaL9vIS1S6AdWChNqWmnYiS7GfaIiDM9s1D6K7hidWBDOm46bNdM3ZwhMyDCfkDJ
SgeJ0w+7YmjvChu7gWqDZCsbtZ5gA1ixCTdDnuZB67JGSPGW6r73coraDP8diOpiQouMvM6bKuTP
BH/1poLccsUxsKgrQ23JC9LWCRb8cYHkZjXFH1K44TsIl5Lne2oT0JI3pwdA2v6jO4p/OLHntP+n
pjwPbedMPUZkDYCkd3LSxj8c3JTxtA8SlPCtIHE1hh65xihg1JRIliSphrqr9kbfwHdeVxPdOI5G
tDYPMYICEjCCAg4CAQEwTTA5MREwDwYDVQQKDAhFcmljc3NvbjEkMCIGA1UEAwwbRXJpY3Nzb24g
TkwgSW5kaXZpZHVhbCBDQTAxAhAhVsFUBw1ddjP0q9Mjb9LGMAkGBSsOAwIaBQCgggEbMBgGCSqG
SIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMTEyMjE0NTcyOVowIwYJKoZI
hvcNAQkEMRYEFJCziU7R7+HQrn24e/nG72HEAqfBMFwGCSsGAQQBgjcQBDFPME0wOTERMA8GA1UE
CgwIRXJpY3Nzb24xJDAiBgNVBAMMG0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMQIQIVbBVAcN
XXYz9KvTI2/SxjBeBgsqhkiG9w0BCRACCzFPoE0wOTERMA8GA1UECgwIRXJpY3Nzb24xJDAiBgNV
BAMMG0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMQIQIVbBVAcNXXYz9KvTI2/SxjANBgkqhkiG
9w0BAQEFAASBgGqt1Gveg8d6uKPsRwJIOH6DX9RoS4RiAC6cnLCrety9cQ+glKsloSwPqvNKBWqX
HO2+XF+tllt+INYkLTlNpUv0hJwhn5ZvVlmziNXsqzr16ySZ4LZKxM/3fFxh7kzEQbwN2WSMV0ML
YUr05QRfVCJrJ+kebliD6eF7x6+cLp3YAAAAAAAA

--Apple-Mail-16-69265508--

From rturner@amalfisystems.com  Tue Nov 22 09:02:51 2011
Return-Path: <rturner@amalfisystems.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C4F821F8C39 for <homenet@ietfa.amsl.com>; Tue, 22 Nov 2011 09:02:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.181
X-Spam-Level: 
X-Spam-Status: No, score=-2.181 tagged_above=-999 required=5 tests=[AWL=0.261,  BAYES_00=-2.599, HTML_MESSAGE=0.001, SUBJECT_FUZZY_TION=0.156]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ULXN-J2auuba for <homenet@ietfa.amsl.com>; Tue, 22 Nov 2011 09:02:50 -0800 (PST)
Received: from omr14.networksolutionsemail.com (omr14.networksolutionsemail.com [205.178.146.64]) by ietfa.amsl.com (Postfix) with ESMTP id 8A4D821F8C48 for <homenet@ietf.org>; Tue, 22 Nov 2011 09:02:50 -0800 (PST)
Received: from cm-omr5 (mail.networksolutionsemail.com [205.178.146.50]) by omr14.networksolutionsemail.com (8.13.8/8.13.8) with ESMTP id pAMH2lBw025007 for <homenet@ietf.org>; Tue, 22 Nov 2011 12:02:49 -0500
Authentication-Results: cm-omr5 smtp.user=rturner@amalfisystems.com; auth=pass (LOGIN)
X-Authenticated-UID: rturner@amalfisystems.com
Received: from [98.151.18.158] ([98.151.18.158:45176] helo=localhost) by cm-omr5 (envelope-from <rturner@amalfisystems.com>) (ecelerity 2.2.2.41 r(31179/31189)) with ESMTPA id 48/CD-04879-6B5DBCE4; Tue, 22 Nov 2011 12:02:47 -0500
Date: Tue, 22 Nov 2011 09:02:43 -0800
Message-ID: <48naav06liaj3aghl2ixaq64.1321981363649@email.android.com>
Importance: normal
From: Randy Turner <rturner@amalfisystems.com>
To: mellon@fugue.com, russw@riw.us
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="--_com.android.email_173424193199049"
Cc: homenet@ietf.org, lorenzo@google.com
Subject: Re: [homenet] Creating a security association via physical link +	button
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 22 Nov 2011 17:02:51 -0000

----_com.android.email_173424193199049
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64

SG9tZSByb3V0ZXJzIHdpdGggYSBuYXR1cmFsIFdBTiBpbnRlcmZhY2Ugc3VjaCBhcyBEU0wgb3Ig
RG9jc2lzIGFyZSBidWlsdCBmcm9tIHJlZmVyZW5jZSBkZXNpZ25zIHRoYXQgImhhcmR3aXJlIiB0
aGUgImludGVybmV0IiBpbnRlcmZhY2UsIGluY2x1ZGluZyBhbnkgZmlyZXdhbGwtbGlrZSBmdW5j
dGlvbmFsaXR5CgpSYW5keQoKLS0tLS0tLS0gT3JpZ2luYWwgbWVzc2FnZSAtLS0tLS0tLQpTdWJq
ZWN0OiBSZTogW2hvbWVuZXRdIENyZWF0aW5nIGEgc2VjdXJpdHkgYXNzb2NpYXRpb24gdmlhIHBo
eXNpY2FsIGxpbmsgKwlidXR0b24gCkZyb206IFRlZCBMZW1vbiA8bWVsbG9uQGZ1Z3VlLmNvbT4g
ClRvOiBSdXNzIFdoaXRlIDxydXNzd0ByaXcudXM+IApDQzogaG9tZW5ldEBpZXRmLm9yZyxMb3Jl
bnpvIENvbGl0dGkgPGxvcmVuem9AZ29vZ2xlLmNvbT4gCgpPbiBOb3YgMjIsIDIwMTEsIGF0IDc6
NDIgQU0sIFJ1c3MgV2hpdGUgd3JvdGU6ClRoaXMgaXMsIGdlbmVyYWxseSBzcGVha2luZywgaG93
IGN1cnJlbnQgaG9tZSByb3V0ZXJzIHdvcmsuLi4gQW5kLCBJCnRoaW5rLCBpdCBtaWdodCBiZSB0
aGUgb25seSB3YXkgdG8gbWFrZSBhIGhvbWVuZXQgd29yay4gVGhlIHByaW1hcnkga2V5CmJleW9u
ZCB0aGlzIGlzIGEgZGV2aWNlIGJlaW5nIGFibGUgdG8gZmlndXJlIG91dCAiSSdtIGFuIGVkZ2Ug
dG8gdGhlCm91dHNpZGUgd29ybGQuIgoKWWVhaCwgSSBkb24ndCB0aGluayBlaXRoZXIgZGV2aWNl
IGRlY2lkZXMgdGhhdCBpdCBpcyB0aGUgaG9tZW5ldDsgcmF0aGVyLCB0aGV5IGFyZSByZWd1bGFy
bHkgZHluYW1pY2FsbHkgZGlzY292ZXJpbmcgdG9wb2xvZ3ksIGFuZCBkZWNpZGluZyB3aGF0IHRv
IGRvIGJhc2VkIG9uIHdoZXRoZXIgdGhleSBhcmUgY29ubmVjdGVkIHRvIGFuIGVkZ2UuIMKgIFBv
c3NpYmx5IGJvdGggZGV2aWNlcyBhcmUgY29ubmVjdGVkIHRvIGFuIGVkZ2UsIGFuZCBjb29wZXJh
dGUgdG8gZG8gbXVsdGlob21pbmcuCgo=

----_com.android.email_173424193199049
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: base64

PGh0bWw+PGhlYWQ+PG1ldGEgaHR0cC1lcXVpdj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0
L2h0bWw7IGNoYXJzZXQ9VVRGLTgiPjwvaGVhZD48Ym9keT5Ib21lIHJvdXRlcnMgd2l0aCBhIG5h
dHVyYWwgV0FOIGludGVyZmFjZSBzdWNoIGFzIERTTCBvciBEb2NzaXMgYXJlIGJ1aWx0IGZyb20g
cmVmZXJlbmNlIGRlc2lnbnMgdGhhdCAiaGFyZHdpcmUiIHRoZSAiaW50ZXJuZXQiIGludGVyZmFj
ZSwgaW5jbHVkaW5nIGFueSBmaXJld2FsbC1saWtlIGZ1bmN0aW9uYWxpdHk8ZGl2Pjxicj48L2Rp
dj48ZGl2PlJhbmR5PC9kaXY+PGJyPjxicj48YnI+LS0tLS0tLS0gT3JpZ2luYWwgbWVzc2FnZSAt
LS0tLS0tLTxicj5TdWJqZWN0OiBSZTogW2hvbWVuZXRdIENyZWF0aW5nIGEgc2VjdXJpdHkgYXNz
b2NpYXRpb24gdmlhIHBoeXNpY2FsIGxpbmsgKwlidXR0b24gPGJyPkZyb206IFRlZCBMZW1vbiAm
bHQ7bWVsbG9uQGZ1Z3VlLmNvbSZndDsgPGJyPlRvOiBSdXNzIFdoaXRlICZsdDtydXNzd0ByaXcu
dXMmZ3Q7IDxicj5DQzogaG9tZW5ldEBpZXRmLm9yZyxMb3JlbnpvIENvbGl0dGkgJmx0O2xvcmVu
em9AZ29vZ2xlLmNvbSZndDsgPGJyPjxicj48YnI+PGRpdj48ZGl2Pk9uIE5vdiAyMiwgMjAxMSwg
YXQgNzo0MiBBTSwgUnVzcyBXaGl0ZSB3cm90ZTo8L2Rpdj48YmxvY2txdW90ZSB0eXBlPSJjaXRl
Ij48c3BhbiBjbGFzcz0iQXBwbGUtc3R5bGUtc3BhbiIgc3R5bGU9ImZvbnQtZmFtaWx5OiBIZWx2
ZXRpY2E7ICI+VGhpcyBpcywgZ2VuZXJhbGx5IHNwZWFraW5nLCBob3cgY3VycmVudCBob21lIHJv
dXRlcnMgd29yay4uLiBBbmQsIEk8YnI+dGhpbmssIGl0IG1pZ2h0IGJlIHRoZSBvbmx5IHdheSB0
byBtYWtlIGEgaG9tZW5ldCB3b3JrLiBUaGUgcHJpbWFyeSBrZXk8YnI+YmV5b25kIHRoaXMgaXMg
YSBkZXZpY2UgYmVpbmcgYWJsZSB0byBmaWd1cmUgb3V0ICJJJ20gYW4gZWRnZSB0byB0aGU8YnI+
b3V0c2lkZSB3b3JsZC4iPC9zcGFuPjwvYmxvY2txdW90ZT48L2Rpdj48YnI+PGRpdj5ZZWFoLCBJ
IGRvbid0IHRoaW5rIGVpdGhlciBkZXZpY2UgZGVjaWRlcyB0aGF0IGl0IGlzIHRoZSBob21lbmV0
OyByYXRoZXIsIHRoZXkgYXJlIHJlZ3VsYXJseSBkeW5hbWljYWxseSBkaXNjb3ZlcmluZyB0b3Bv
bG9neSwgYW5kIGRlY2lkaW5nIHdoYXQgdG8gZG8gYmFzZWQgb24gd2hldGhlciB0aGV5IGFyZSBj
b25uZWN0ZWQgdG8gYW4gZWRnZS4gJm5ic3A7IFBvc3NpYmx5IGJvdGggZGV2aWNlcyBhcmUgY29u
bmVjdGVkIHRvIGFuIGVkZ2UsIGFuZCBjb29wZXJhdGUgdG8gZG8gbXVsdGlob21pbmcuPC9kaXY+
PGRpdj48YnI+PC9kaXY+PC9ib2R5Pg==

----_com.android.email_173424193199049--



From lee.howard@twcable.com  Tue Nov 22 14:19:14 2011
Return-Path: <lee.howard@twcable.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D8ED11E80E7 for <homenet@ietfa.amsl.com>; Tue, 22 Nov 2011 14:19:14 -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=[AWL=0.194,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368,  HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, SUBJECT_FUZZY_TION=0.156]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ov+5VqGsiuoi for <homenet@ietfa.amsl.com>; Tue, 22 Nov 2011 14:19:12 -0800 (PST)
Received: from cdpipgw01.twcable.com (cdpipgw01.twcable.com [165.237.59.22]) by ietfa.amsl.com (Postfix) with ESMTP id 4CED311E80B9 for <homenet@ietf.org>; Tue, 22 Nov 2011 14:19:12 -0800 (PST)
X-SENDER-IP: 10.136.163.13
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.69,554,1315195200";  d="scan'208,217";a="300949580"
Received: from unknown (HELO PRVPEXHUB04.corp.twcable.com) ([10.136.163.13]) by cdpipgw01.twcable.com with ESMTP/TLS/RC4-MD5; 22 Nov 2011 17:14:28 -0500
Received: from PRVPEXVS03.corp.twcable.com ([10.136.163.26]) by PRVPEXHUB04.corp.twcable.com ([10.136.163.13]) with mapi; Tue, 22 Nov 2011 17:19:11 -0500
From: "Howard, Lee" <lee.howard@twcable.com>
To: Lorenzo Colitti <lorenzo@google.com>, "homenet@ietf.org" <homenet@ietf.org>
Date: Tue, 22 Nov 2011 17:19:09 -0500
Thread-Topic: [homenet] Creating a security association via physical link + button
Thread-Index: Acyo7Qc5X5xQOvZGR8Ovw+bnL+te7QAd4jiQ
Message-ID: <DCC302FAA9FE5F4BBA4DCAD4656937791452BBC096@PRVPEXVS03.corp.twcable.com>
References: <CAKD1Yr3Y=EO9siQkAuZd7LtqsOT_8GswWkPOoiJEhtvnULcytw@mail.gmail.com>
In-Reply-To: <CAKD1Yr3Y=EO9siQkAuZd7LtqsOT_8GswWkPOoiJEhtvnULcytw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_DCC302FAA9FE5F4BBA4DCAD4656937791452BBC096PRVPEXVS03cor_"
MIME-Version: 1.0
Subject: Re: [homenet] Creating a security association via physical link + button
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 22 Nov 2011 22:19:14 -0000

--_000_DCC302FAA9FE5F4BBA4DCAD4656937791452BBC096PRVPEXVS03cor_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

A physical button, or a virtual button?
I don't want to do mechanical engineering here.  And buttons are expensive.

Lee

From: homenet-bounces@ietf.org [mailto:homenet-bounces@ietf.org] On Behalf =
Of Lorenzo Colitti
Sent: Tuesday, November 22, 2011 3:02 AM
To: homenet@ietf.org
Subject: [homenet] Creating a security association via physical link + butt=
on

It would be cool if I could plug in a new router into my homenet, press a s=
pecial button on it and on the router I plug it into, and have the new rout=
er download the homenet config (at least the routing protocol key, but mayb=
e other things like the wifi SSID) from the existing router.

The button would cause the existing router to make the information availabl=
e in the clear for, say, 30 seconds, and would cause the new router to atte=
mpt to fetch it from a directly connected neighbour. The combination of phy=
sically plugging something in and pressing the button might provide enough =
security to defend against unintended pairings (e.g., because you plugged s=
omething in to the wrong port; maybe to your neighbour's homenet).

I don't know how you would decide who is the "homenet" and who is the "new =
router" though.

Comments?

________________________________
This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

--_000_DCC302FAA9FE5F4BBA4DCAD4656937791452BBC096PRVPEXVS03cor_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns=
:odc=3D"urn:schemas-microsoft-com:office:odc" xmlns:oa=3D"urn:schemas-micro=
soft-com:office:activation" xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc=3D"http://m=
icrosoft.com/officenet/conferencing" xmlns:D=3D"DAV:" xmlns:Repl=3D"http://=
schemas.microsoft.com/repl/" xmlns:mt=3D"http://schemas.microsoft.com/share=
point/soap/meetings/" xmlns:x2=3D"http://schemas.microsoft.com/office/excel=
/2003/xml" xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" xmlns:ois=
=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"http://=
schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://www.w3=
.org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint=
/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http=
://www.w3.org/2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sha=
repoint/soap/2002/1/alerts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#"=
 xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" xmlns:sps=3D"http://=
schemas.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001=
/XMLSchema-instance" xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/so=
ap" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udc=
p2p=3D"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf=3D"http:/=
/schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss=3D"http://sche=
mas.microsoft.com/office/2006/digsig-setup" xmlns:dssi=3D"http://schemas.mi=
crosoft.com/office/2006/digsig" xmlns:mdssi=3D"http://schemas.openxmlformat=
s.org/package/2006/digital-signature" xmlns:mver=3D"http://schemas.openxmlf=
ormats.org/markup-compatibility/2006" xmlns:m=3D"http://schemas.microsoft.c=
om/office/2004/12/omml" xmlns:mrels=3D"http://schemas.openxmlformats.org/pa=
ckage/2006/relationships" xmlns:spwp=3D"http://microsoft.com/sharepoint/web=
partpages" xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/20=
06/types" xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/200=
6/messages" xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/Sli=
deLibrary/" xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortal=
Server/PublishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" xmlns:=
st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Times New Roman","serif";
	color:black;
	font-weight:normal;
	font-style:normal;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:black">A physical button, or a =
virtual button?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">I don&#8217;t want to do=
 mechanical engineering here.&nbsp; And buttons are expensive.<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"color:black"><o:p>&nbsp;</o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">Lee<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"color:black"><o:p>&nbsp;</o:p></span>=
</p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> homenet-=
bounces@ietf.org [mailto:homenet-bounces@ietf.org]
<b>On Behalf Of </b>Lorenzo Colitti<br>
<b>Sent:</b> Tuesday, November 22, 2011 3:02 AM<br>
<b>To:</b> homenet@ietf.org<br>
<b>Subject:</b> [homenet] Creating a security association via physical link=
 &#43; button<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">It would be cool if I could plug in a new router int=
o my homenet, press a special button on it and on the router I plug it into=
, and have the new router download the homenet config (at least the routing=
 protocol key, but maybe other things
 like the wifi SSID) from the existing router.<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">The button would cause the existing router to make t=
he information available in the clear for, say, 30 seconds, and would cause=
 the new router to attempt to fetch it from a directly connected neighbour.=
 The combination of physically plugging
 something in and pressing the button might provide enough security to defe=
nd against unintended pairings (e.g., because you plugged something in to t=
he wrong port; maybe to your neighbour's homenet).<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">I don't know how you would decide who is the &quot;h=
omenet&quot; and who is the &quot;new router&quot; though.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Comments?<o:p></o:p></p>
</div>
</div>
</div>
<br>
<hr>
<font face=3D"Arial" color=3D"Gray" size=3D"1">This E-mail and any of its a=
ttachments may contain Time Warner Cable proprietary information, which is =
privileged, confidential, or subject to copyright belonging to Time Warner =
Cable. This E-mail is intended solely
 for the use of the individual or entity to which it is addressed. If you a=
re not the intended recipient of this E-mail, you are hereby notified that =
any dissemination, distribution, copying, or action taken in relation to th=
e contents of and attachments to
 this E-mail is strictly prohibited and may be unlawful. If you have receiv=
ed this E-mail in error, please notify the sender immediately and permanent=
ly delete the original and any copy of this E-mail and any printout.<br>
</font>
</body>
</html>

--_000_DCC302FAA9FE5F4BBA4DCAD4656937791452BBC096PRVPEXVS03cor_--

From lee.howard@twcable.com  Tue Nov 22 14:36:23 2011
Return-Path: <lee.howard@twcable.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1432E11E80E4 for <homenet@ietfa.amsl.com>; Tue, 22 Nov 2011 14:36:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.199
X-Spam-Level: 
X-Spam-Status: No, score=-1.199 tagged_above=-999 required=5 tests=[AWL=0.264,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NKA6vAa4cDd1 for <homenet@ietfa.amsl.com>; Tue, 22 Nov 2011 14:36:22 -0800 (PST)
Received: from cdpipgw01.twcable.com (cdpipgw01.twcable.com [165.237.59.22]) by ietfa.amsl.com (Postfix) with ESMTP id 803E711E80D2 for <homenet@ietf.org>; Tue, 22 Nov 2011 14:36:22 -0800 (PST)
X-SENDER-IP: 10.136.163.10
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.69,555,1315195200"; d="scan'208";a="300957361"
Received: from unknown (HELO PRVPEXHUB01.corp.twcable.com) ([10.136.163.10]) by cdpipgw01.twcable.com with ESMTP/TLS/RC4-MD5; 22 Nov 2011 17:31:38 -0500
Received: from PRVPEXVS03.corp.twcable.com ([10.136.163.26]) by PRVPEXHUB01.corp.twcable.com ([10.136.163.10]) with mapi; Tue, 22 Nov 2011 17:36:22 -0500
From: "Howard, Lee" <lee.howard@twcable.com>
To: "homenet@ietf.org" <homenet@ietf.org>
Date: Tue, 22 Nov 2011 17:36:20 -0500
Thread-Topic: other routing options
Thread-Index: AcypZyepGoWhHzHSQE6bpA+uksKGEg==
Message-ID: <DCC302FAA9FE5F4BBA4DCAD4656937791452BBC0CC@PRVPEXVS03.corp.twcable.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [homenet] other routing options
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 22 Nov 2011 22:36:23 -0000

Ray asked for people to post drafts for anything other than OSPF, because w=
ithout an alternative, it will appear that we have consensus on OSPF.  I ha=
ven't posted a draft on RIPng, because it would just work the way it's desi=
gned.

A few people said  http://tools.ietf.org/html/draft-howard-up-pio-00 is no =
better than RIP, and we already have RIP in home gateways.  Can any gateway=
 vendor confirm whether RIPng is already in gateways?

Proposed alternatives are:
* OSPFv3.  It's heavyweight for home routing.  We still need a way to find =
the border and inject default.  It could be used for DHCP-PD.
* zOSPF.  It requires resurrecting work.  I don't how much work it needs, o=
r how big the protocol is.
* UP PIO.  It's new work, and requires work.  It's lightweight, and solves =
the border problem, but not addressing.
* RIPng.  It's fairly lightweight, and it exists.  It solves only the routi=
ng problem.
* MANEMO.  It requires resurrecting work, is pretty lightweight, and solves=
 addressing and border problems.

If you argue that we should reuse existing protocols (per the architecture =
draft), your choices are OSPFv3 or RIPng.  I really don't like OSPFv3 in th=
e home--it's too much protocol, though if someone can tell me about memory =
footprint, that would be helpful.

I also prefer draft-baker-homenet-prefix-assignment, so we don't need OSPF =
for addressing.

Any discussion?

Lee


This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

From rturner@amalfisystems.com  Tue Nov 22 14:49:18 2011
Return-Path: <rturner@amalfisystems.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C7371F0C5C for <homenet@ietfa.amsl.com>; Tue, 22 Nov 2011 14:49:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dPa9sLpb4hkp for <homenet@ietfa.amsl.com>; Tue, 22 Nov 2011 14:49:17 -0800 (PST)
Received: from omr4.networksolutionsemail.com (omr4.networksolutionsemail.com [205.178.146.54]) by ietfa.amsl.com (Postfix) with ESMTP id 734391F0C56 for <homenet@ietf.org>; Tue, 22 Nov 2011 14:49:17 -0800 (PST)
Received: from cm-omr8 (mail.networksolutionsemail.com [205.178.146.50]) by omr4.networksolutionsemail.com (8.13.6/8.13.6) with ESMTP id pAMMnGd3019048 for <homenet@ietf.org>; Tue, 22 Nov 2011 17:49:16 -0500
Authentication-Results: cm-omr8 smtp.user=rturner@amalfisystems.com; auth=pass (CRAM-MD5)
X-Authenticated-UID: rturner@amalfisystems.com
Received: from [75.212.136.192] ([75.212.136.192:61758] helo=192.sub-75-212-136.myvzw.com) by cm-omr8 (envelope-from <rturner@amalfisystems.com>) (ecelerity 2.2.2.41 r(31179/31189)) with ESMTPSA (cipher=AES128-SHA)  id 51/8C-04746-BE62CCE4; Tue, 22 Nov 2011 17:49:16 -0500
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=windows-1252
From: Randy Turner <rturner@amalfisystems.com>
In-Reply-To: <DCC302FAA9FE5F4BBA4DCAD4656937791452BBC0CC@PRVPEXVS03.corp.twcable.com>
Date: Tue, 22 Nov 2011 14:49:25 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <A7A4DFCE-C09D-49F7-A772-B3FC5F575CA1@amalfisystems.com>
References: <DCC302FAA9FE5F4BBA4DCAD4656937791452BBC0CC@PRVPEXVS03.corp.twcable.com>
To: "Howard, Lee" <lee.howard@twcable.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: "homenet@ietf.org" <homenet@ietf.org>
Subject: Re: [homenet] other routing options
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 22 Nov 2011 22:49:18 -0000

"OSPF is too much protocol=85"

That's how I felt until incredibly elaborate home net topologies were =
suggested -- but it still seems intuitively heavyweight for a "home" =
network.  If we do end up using OSPF, then maybe home networks are *not* =
simple as one would think, but rather a different instantiation of a =
complex routing scenario, just with "zeroconf" requirements.

R.

On Nov 22, 2011, at 2:36 PM, Howard, Lee wrote:

> Ray asked for people to post drafts for anything other than OSPF, =
because without an alternative, it will appear that we have consensus on =
OSPF.  I haven't posted a draft on RIPng, because it would just work the =
way it's designed.
>=20
> A few people said  http://tools.ietf.org/html/draft-howard-up-pio-00 =
is no better than RIP, and we already have RIP in home gateways.  Can =
any gateway vendor confirm whether RIPng is already in gateways?
>=20
> Proposed alternatives are:
> * OSPFv3.  It's heavyweight for home routing.  We still need a way to =
find the border and inject default.  It could be used for DHCP-PD.
> * zOSPF.  It requires resurrecting work.  I don't how much work it =
needs, or how big the protocol is.
> * UP PIO.  It's new work, and requires work.  It's lightweight, and =
solves the border problem, but not addressing.
> * RIPng.  It's fairly lightweight, and it exists.  It solves only the =
routing problem.
> * MANEMO.  It requires resurrecting work, is pretty lightweight, and =
solves addressing and border problems.
>=20
> If you argue that we should reuse existing protocols (per the =
architecture draft), your choices are OSPFv3 or RIPng.  I really don't =
like OSPFv3 in the home--it's too much protocol, though if someone can =
tell me about memory footprint, that would be helpful.
>=20
> I also prefer draft-baker-homenet-prefix-assignment, so we don't need =
OSPF for addressing.
>=20
> Any discussion?
>=20
> Lee
>=20
>=20
> This E-mail and any of its attachments may contain Time Warner Cable =
proprietary information, which is privileged, confidential, or subject =
to copyright belonging to Time Warner Cable. This E-mail is intended =
solely for the use of the individual or entity to which it is addressed. =
If you are not the intended recipient of this E-mail, you are hereby =
notified that any dissemination, distribution, copying, or action taken =
in relation to the contents of and attachments to this E-mail is =
strictly prohibited and may be unlawful. If you have received this =
E-mail in error, please notify the sender immediately and permanently =
delete the original and any copy of this E-mail and any printout.
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>=20


From Hans_Liu@dlink.com.tw  Tue Nov 22 16:04:03 2011
Return-Path: <Hans_Liu@dlink.com.tw>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 300681F0C6E for <homenet@ietfa.amsl.com>; Tue, 22 Nov 2011 16:04:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.582
X-Spam-Level: 
X-Spam-Status: No, score=-0.582 tagged_above=-999 required=5 tests=[AWL=0.525,  BAYES_00=-2.599, HELO_EQ_TW=1.335, HTML_MESSAGE=0.001, SUBJECT_FUZZY_TION=0.156]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CwNvTAGZ7KK8 for <homenet@ietfa.amsl.com>; Tue, 22 Nov 2011 16:04:02 -0800 (PST)
Received: from smtp-tp2.dlink.com.tw (smtp-tp2.dlink.com.tw [60.248.210.36]) by ietfa.amsl.com (Postfix) with ESMTP id 1F28C1F0C7B for <homenet@ietf.org>; Tue, 22 Nov 2011 16:04:02 -0800 (PST)
Received: from HCB-HUB2.dlink.com.tw (localhost.localdomain [127.0.0.1]) by smtp-tp2.dlink.com.tw (Postfix) with ESMTP id CAE9C873F1; Wed, 23 Nov 2011 08:03:47 +0800 (CST)
Received: from MBS-HQ1.dlink.com.tw ([fe80::d145:65e8:91b9:88a0]) by HCB-HUB2.dlink.com.tw ([::1]) with mapi id 14.01.0289.001; Wed, 23 Nov 2011 08:03:48 +0800
From: Hans Liu <Hans_Liu@dlink.com.tw>
To: "Howard, Lee" <lee.howard@twcable.com>
Thread-Topic: [homenet] Creating a security association via physical link + button
Thread-Index: AQHMqO0O9nM0pPV89kSY6gzNafZ1VJW48YyAgACjWZA=
Date: Wed, 23 Nov 2011 00:03:48 +0000
Message-ID: <9B12A77F-91FE-4FAC-B4F9-36E0639B9069@dlink.com.tw>
References: <CAKD1Yr3Y=EO9siQkAuZd7LtqsOT_8GswWkPOoiJEhtvnULcytw@mail.gmail.com>, <DCC302FAA9FE5F4BBA4DCAD4656937791452BBC096@PRVPEXVS03.corp.twcable.com>
In-Reply-To: <DCC302FAA9FE5F4BBA4DCAD4656937791452BBC096@PRVPEXVS03.corp.twcable.com>
Accept-Language: zh-TW, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_9B12A77F91FE4FACB4F936E0639B9069dlinkcomtw_"
MIME-Version: 1.0
Cc: "homenet@ietf.org" <homenet@ietf.org>, Lorenzo Colitti <lorenzo@google.com>
Subject: Re: [homenet] Creating a security association via physical link + button
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 23 Nov 2011 00:04:03 -0000

--_000_9B12A77F91FE4FACB4F936E0639B9069dlinkcomtw_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

There is a physical button for WPS PBC and it is widely adopted in the Wi-F=
i CPE devices. We can use it by defining an extension.

Hans

Sent from Hans' iPad2

On Nov 23, 2011, at 6:19 AM, "Howard, Lee" <lee.howard@twcable.com<mailto:l=
ee.howard@twcable.com>> wrote:

A physical button, or a virtual button?
I don=92t want to do mechanical engineering here.  And buttons are expensiv=
e.

Lee

From: homenet-bounces@ietf.org<mailto:homenet-bounces@ietf.org> [mailto:hom=
enet-bounces@ietf.org] On Behalf Of Lorenzo Colitti
Sent: Tuesday, November 22, 2011 3:02 AM
To: homenet@ietf.org<mailto:homenet@ietf.org>
Subject: [homenet] Creating a security association via physical link + butt=
on

It would be cool if I could plug in a new router into my homenet, press a s=
pecial button on it and on the router I plug it into, and have the new rout=
er download the homenet config (at least the routing protocol key, but mayb=
e other things like the wifi SSID) from the existing router.

The button would cause the existing router to make the information availabl=
e in the clear for, say, 30 seconds, and would cause the new router to atte=
mpt to fetch it from a directly connected neighbour. The combination of phy=
sically plugging something in and pressing the button might provide enough =
security to defend against unintended pairings (e.g., because you plugged s=
omething in to the wrong port; maybe to your neighbour's homenet).

I don't know how you would decide who is the "homenet" and who is the "new =
router" though.

Comments?

________________________________
This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.
_______________________________________________
homenet mailing list
homenet@ietf.org<mailto:homenet@ietf.org>
https://www.ietf.org/mailman/listinfo/homenet

--_000_9B12A77F91FE4FACB4F936E0639B9069dlinkcomtw_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body bgcolor=3D"#FFFFFF">
<div>There is a physical button for WPS PBC and it is widely adopted in the=
 Wi-Fi CPE devices. We can use it by defining an extension.</div>
<div><br>
</div>
<div>Hans</div>
<div><br>
Sent from Hans' iPad2</div>
<div><br>
On Nov 23, 2011, at 6:19 AM, &quot;Howard, Lee&quot; &lt;<a href=3D"mailto:=
lee.howard@twcable.com">lee.howard@twcable.com</a>&gt; wrote:<br>
<br>
</div>
<div></div>
<blockquote type=3D"cite">
<div>
<meta name=3D"Generator" content=3D"Microsoft Word 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Times New Roman","serif";
	color:black;
	font-weight:normal;
	font-style:normal;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:black">A physical button, or a =
virtual button?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:black">I don=92t want to do mec=
hanical engineering here.&nbsp; And buttons are expensive.<o:p></o:p></span=
></p>
<p class=3D"MsoNormal"><span style=3D"color:black"><o:p>&nbsp;</o:p></span>=
</p>
<p class=3D"MsoNormal"><span style=3D"color:black">Lee<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"color:black"><o:p>&nbsp;</o:p></span>=
</p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">
<a href=3D"mailto:homenet-bounces@ietf.org">homenet-bounces@ietf.org</a> [m=
ailto:homenet-bounces@ietf.org]
<b>On Behalf Of </b>Lorenzo Colitti<br>
<b>Sent:</b> Tuesday, November 22, 2011 3:02 AM<br>
<b>To:</b> <a href=3D"mailto:homenet@ietf.org">homenet@ietf.org</a><br>
<b>Subject:</b> [homenet] Creating a security association via physical link=
 &#43; button<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">It would be cool if I could plug in a new router int=
o my homenet, press a special button on it and on the router I plug it into=
, and have the new router download the homenet config (at least the routing=
 protocol key, but maybe other things
 like the wifi SSID) from the existing router.<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">The button would cause the existing router to make t=
he information available in the clear for, say, 30 seconds, and would cause=
 the new router to attempt to fetch it from a directly connected neighbour.=
 The combination of physically plugging
 something in and pressing the button might provide enough security to defe=
nd against unintended pairings (e.g., because you plugged something in to t=
he wrong port; maybe to your neighbour's homenet).<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">I don't know how you would decide who is the &quot;h=
omenet&quot; and who is the &quot;new router&quot; though.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Comments?<o:p></o:p></p>
</div>
</div>
</div>
<br>
<hr>
<font face=3D"Arial" color=3D"Gray" size=3D"1">This E-mail and any of its a=
ttachments may contain Time Warner Cable proprietary information, which is =
privileged, confidential, or subject to copyright belonging to Time Warner =
Cable. This E-mail is intended solely
 for the use of the individual or entity to which it is addressed. If you a=
re not the intended recipient of this E-mail, you are hereby notified that =
any dissemination, distribution, copying, or action taken in relation to th=
e contents of and attachments to
 this E-mail is strictly prohibited and may be unlawful. If you have receiv=
ed this E-mail in error, please notify the sender immediately and permanent=
ly delete the original and any copy of this E-mail and any printout.<br>
</font></div>
</blockquote>
<blockquote type=3D"cite">
<div><span>_______________________________________________</span><br>
<span>homenet mailing list</span><br>
<span><a href=3D"mailto:homenet@ietf.org">homenet@ietf.org</a></span><br>
<span><a href=3D"https://www.ietf.org/mailman/listinfo/homenet">https://www=
.ietf.org/mailman/listinfo/homenet</a></span><br>
</div>
</blockquote>
</body>
</html>

--_000_9B12A77F91FE4FACB4F936E0639B9069dlinkcomtw_--

From mellon@fugue.com  Tue Nov 22 17:37:45 2011
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 590E011E80C8 for <homenet@ietfa.amsl.com>; Tue, 22 Nov 2011 17:37:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.97
X-Spam-Level: 
X-Spam-Status: No, score=-1.97 tagged_above=-999 required=5 tests=[AWL=0.472,  BAYES_00=-2.599, HTML_MESSAGE=0.001, SUBJECT_FUZZY_TION=0.156]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0HtY-oFzhPCq for <homenet@ietfa.amsl.com>; Tue, 22 Nov 2011 17:37:45 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 034A411E80BA for <homenet@ietf.org>; Tue, 22 Nov 2011 17:37:45 -0800 (PST)
Received: from [IPv6:2001:470:1f07:1486:3892:2ed1:fa15:7e5b] (unknown [IPv6:2001:470:1f07:1486:3892:2ed1:fa15:7e5b]) by toccata.fugue.com (Postfix) with ESMTPSA id 8A5582380C97; Tue, 22 Nov 2011 20:37:41 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: multipart/alternative; boundary="Apple-Mail=_B6C93DCB-5470-40A8-AB8D-6BF66BE74786"
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <DCC302FAA9FE5F4BBA4DCAD4656937791452BBC096@PRVPEXVS03.corp.twcable.com>
Date: Tue, 22 Nov 2011 20:37:39 -0500
Message-Id: <8A4DBEDA-3C1F-4EC7-B161-089A4C436BEF@fugue.com>
References: <CAKD1Yr3Y=EO9siQkAuZd7LtqsOT_8GswWkPOoiJEhtvnULcytw@mail.gmail.com> <DCC302FAA9FE5F4BBA4DCAD4656937791452BBC096@PRVPEXVS03.corp.twcable.com>
To: "Howard, Lee" <lee.howard@twcable.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: "homenet@ietf.org" <homenet@ietf.org>, Lorenzo Colitti <lorenzo@google.com>
Subject: Re: [homenet] Creating a security association via physical link + button
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 23 Nov 2011 01:37:45 -0000

--Apple-Mail=_B6C93DCB-5470-40A8-AB8D-6BF66BE74786
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

On Nov 22, 2011, at 5:19 PM, Howard, Lee wrote:
> I don=92t want to do mechanical engineering here.  And buttons are =
expensive.

Great, let's just do a USB port then!   :)

Seriously, if you make a device cheap enough, it simply won't be able to =
do homenet.   The question is, how cheap is that?



--Apple-Mail=_B6C93DCB-5470-40A8-AB8D-6BF66BE74786
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div>On Nov 22, 2011, at 5:19 PM, Howard, Lee =
wrote:</div><blockquote type=3D"cite"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; font-family: Helvetica; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-align: -webkit-auto; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"margin-top: 0in; margin-right: 0in; margin-left: 0in; =
margin-bottom: 0.0001pt; font-size: 12pt; font-family: 'Times New =
Roman', serif; "><span style=3D"color: black; ">I don=92t want to do =
mechanical engineering here.&nbsp; And buttons are =
expensive.</span></div></span></blockquote><br></div><div>Great, let's =
just do a USB port then! &nbsp; :)</div><div><br></div><div>Seriously, =
if you make a device cheap enough, it simply won't be able to do =
homenet. &nbsp; The question is, how cheap is =
that?</div><div><br></div><br></body></html>=

--Apple-Mail=_B6C93DCB-5470-40A8-AB8D-6BF66BE74786--

From fred@cisco.com  Tue Nov 22 22:41:10 2011
Return-Path: <fred@cisco.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54B9C1F0C52 for <homenet@ietfa.amsl.com>; Tue, 22 Nov 2011 22:41:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.46
X-Spam-Level: 
X-Spam-Status: No, score=-105.46 tagged_above=-999 required=5 tests=[AWL=-2.861, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OU5qksujHFg4 for <homenet@ietfa.amsl.com>; Tue, 22 Nov 2011 22:41:09 -0800 (PST)
Received: from bgl-iport-2.cisco.com (bgl-iport-2.cisco.com [72.163.197.26]) by ietfa.amsl.com (Postfix) with ESMTP id 173591F0C43 for <homenet@ietf.org>; Tue, 22 Nov 2011 22:41:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=3012; q=dns/txt; s=iport; t=1322030469; x=1323240069; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to:content-transfer-encoding; bh=0uQRgIamt5RxxFsRFN7plGHrMlznpEjRyrdEGyVpBug=; b=FUXu3ixsKvME/vOOApJj9BfvlYrLDqBt6cCjsItuOmk8TDZgQ2GxUGRS wtcjdI9FBb/Odxh6WGSOamH8GkohUCPfC7494W2u7id9e3U+ifG/XkLy0 NPm0ePyOYGLfRj5qqYDEZzKmMGsXkHTRk4iQgH7mSDVMu+WwA+wcx5233 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ap4EAFiVzE5Io8UY/2dsb2JhbABEq2eBcgEBAQMBAQEBDwEnNAQHBQsLEjQnIg4GEyKHYwiWRwGeLIl/YwSIIIwohT+MbA
X-IronPort-AV: E=Sophos;i="4.69,557,1315180800";  d="scan'208";a="32212"
Received: from vla196-nat.cisco.com (HELO bgl-core-1.cisco.com) ([72.163.197.24]) by bgl-iport-2.cisco.com with ESMTP; 23 Nov 2011 06:41:07 +0000
Received: from Freds-Computer.local (tky-vpn-client-230-235.cisco.com [10.70.230.235]) by bgl-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id pAN6em7U017001; Wed, 23 Nov 2011 06:41:04 GMT
Received: from [127.0.0.1] by Freds-Computer.local (PGP Universal service); Tue, 22 Nov 2011 22:41:05 -0800
X-PGP-Universal: processed; by Freds-Computer.local on Tue, 22 Nov 2011 22:41:05 -0800
Mime-Version: 1.0 (Apple Message framework v1084)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <DCC302FAA9FE5F4BBA4DCAD4656937791452BBC0CC@PRVPEXVS03.corp.twcable.com>
Date: Tue, 22 Nov 2011 22:41:03 -0800
Message-Id: <F4205C7B-9C3E-438A-8E14-0B0CB656CC8F@cisco.com>
References: <DCC302FAA9FE5F4BBA4DCAD4656937791452BBC0CC@PRVPEXVS03.corp.twcable.com>
To: "Howard, Lee" <lee.howard@twcable.com>
X-Mailer: Apple Mail (2.1084)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: "homenet@ietf.org" <homenet@ietf.org>
Subject: Re: [homenet] other routing options
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 23 Nov 2011 06:41:10 -0000

On Nov 22, 2011, at 2:36 PM, Howard, Lee wrote:

> Ray asked for people to post drafts for anything other than OSPF, =
because without an alternative, it will appear that we have consensus on =
OSPF.  I haven't posted a draft on RIPng, because it would just work the =
way it's designed.

Makes sense to me.

> A few people said  http://tools.ietf.org/html/draft-howard-up-pio-00 =
is no better than RIP, and we already have RIP in home gateways.  Can =
any gateway vendor confirm whether RIPng is already in gateways?
>=20
> Proposed alternatives are:
> * OSPFv3.  It's heavyweight for home routing.  We still need a way to =
find the border and inject default.  It could be used for DHCP-PD.
> * zOSPF.  It requires resurrecting work.  I don't how much work it =
needs, or how big the protocol is.

The Internet Draft could be summarized as "Use OSPF, and <do this> for =
subnet allocation". If you don't like OSPF, you don't like zOSPF.

> * UP PIO.  It's new work, and requires work.  It's lightweight, and =
solves the border problem, but not addressing.
> * RIPng.  It's fairly lightweight, and it exists.  It solves only the =
routing problem.

To my way of thinking, as a default protocol for very small networks, =
you could do worse. I personally prefer OSPF, but I'm a snob :-)

> * MANEMO.  It requires resurrecting work, is pretty lightweight, and =
solves addressing and border problems.
>=20
> If you argue that we should reuse existing protocols (per the =
architecture draft), your choices are OSPFv3 or RIPng.  I really don't =
like OSPFv3 in the home--it's too much protocol, though if someone can =
tell me about memory footprint, that would be helpful.

If you're comparing to RIPng, "a lot more". It's a more complex program, =
and it not only stores a route table, it stores a link state database. =
I'd have to go look at something to say this definitively, but I've =
heard the phrase "order of magnitude" in discussions like these.

> I also prefer draft-baker-homenet-prefix-assignment, so we don't need =
OSPF for addressing.

> Any discussion?
>=20
> Lee
>=20
>=20
> This E-mail and any of its attachments may contain Time Warner Cable =
proprietary information, which is privileged, confidential, or subject =
to copyright belonging to Time Warner Cable. This E-mail is intended =
solely for the use of the individual or entity to which it is addressed. =
If you are not the intended recipient of this E-mail, you are hereby =
notified that any dissemination, distribution, copying, or action taken =
in relation to the contents of and attachments to this E-mail is =
strictly prohibited and may be unlawful. If you have received this =
E-mail in error, please notify the sender immediately and permanently =
delete the original and any copy of this E-mail and any printout.
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet


From fred@cisco.com  Tue Nov 22 22:45:31 2011
Return-Path: <fred@cisco.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3F341F0C52 for <homenet@ietfa.amsl.com>; Tue, 22 Nov 2011 22:45:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.413
X-Spam-Level: 
X-Spam-Status: No, score=-105.413 tagged_above=-999 required=5 tests=[AWL=-2.814, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5KGnx92d7BfF for <homenet@ietfa.amsl.com>; Tue, 22 Nov 2011 22:45:31 -0800 (PST)
Received: from bgl-iport-1.cisco.com (bgl-iport-1.cisco.com [72.163.197.25]) by ietfa.amsl.com (Postfix) with ESMTP id 93A3C1F0C43 for <homenet@ietf.org>; Tue, 22 Nov 2011 22:45:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=fred@cisco.com; l=1058; q=dns/txt; s=iport; t=1322030730; x=1323240330; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to:content-transfer-encoding; bh=bkdTM6t5Af3JXOiu9Iv97uLxi3C/qgdvEKSQBViCt2E=; b=ByPc6lPaZOgrMTjWzztAKf0XnORZyvYWqzzGrr0pEnoN0IFI0fHRJYdk IBzvh4lbNoodjCPxuhI2Z4hdXcha+BwjVD4vlGvztpjALN/+FY/mj/Bef ZoVSUj5diX8/l91q7wjDSXuUVq+AMuAg8TAX2FW+sVLeVz/aZEFx+reA0 o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ap0EAAyWzE5Io8UY/2dsb2JhbABEq2eBcgEBAQMBEgEnPwULCw44VwY1h2OWUQGeKYl/YwSIIIwohT+MbA
X-IronPort-AV: E=Sophos;i="4.69,557,1315180800";  d="scan'208";a="33015"
Received: from vla196-nat.cisco.com (HELO bgl-core-1.cisco.com) ([72.163.197.24]) by bgl-iport-1.cisco.com with ESMTP; 23 Nov 2011 06:45:29 +0000
Received: from Freds-Computer.local (tky-vpn-client-230-235.cisco.com [10.70.230.235]) by bgl-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id pAN6em7d017001; Wed, 23 Nov 2011 06:45:27 GMT
Received: from [127.0.0.1] by Freds-Computer.local (PGP Universal service); Tue, 22 Nov 2011 22:45:29 -0800
X-PGP-Universal: processed; by Freds-Computer.local on Tue, 22 Nov 2011 22:45:29 -0800
Mime-Version: 1.0 (Apple Message framework v1084)
From: Fred Baker <fred@cisco.com>
In-Reply-To: <A7A4DFCE-C09D-49F7-A772-B3FC5F575CA1@amalfisystems.com>
Date: Tue, 22 Nov 2011 22:45:25 -0800
Message-Id: <35ABFE5A-789F-4268-812F-BCA00ACC388F@cisco.com>
References: <DCC302FAA9FE5F4BBA4DCAD4656937791452BBC0CC@PRVPEXVS03.corp.twcable.com> <A7A4DFCE-C09D-49F7-A772-B3FC5F575CA1@amalfisystems.com>
To: Randy Turner <rturner@amalfisystems.com>
X-Mailer: Apple Mail (2.1084)
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Cc: "Howard, Lee" <lee.howard@twcable.com>, "homenet@ietf.org" <homenet@ietf.org>
Subject: Re: [homenet] other routing options
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 23 Nov 2011 06:45:31 -0000

On Nov 22, 2011, at 2:49 PM, Randy Turner wrote:

> That's how I felt until incredibly elaborate home net topologies were =
suggested -- but it still seems intuitively heavyweight for a "home" =
network.  If we do end up using OSPF, then maybe home networks are *not* =
simple as one would think, but rather a different instantiation of a =
complex routing scenario, just with "zeroconf" requirements.

well, halfway in between. If you have a wired LAN and a wireless LAN =
with two wired/wireless routers, I suspect you have a routing topology =
with at least one redundant path. I don't care how many nodes you have; =
if you have a tree, it is "simple" for any protocol. If you have =
not-all-that-many nodes but have redundancy in the topology, you have =
the possibility of count-to-infinity problems with a bellman-ford =
protocol like RIPng. I would suspect that a home network is small =
compared to, say, a campus in an enterprise network, but if it has =
redundancy it has at least some probability of the same class of issues.=

From rturner@amalfisystems.com  Tue Nov 22 23:10:37 2011
Return-Path: <rturner@amalfisystems.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3477721F8A35 for <homenet@ietfa.amsl.com>; Tue, 22 Nov 2011 23:10:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.303
X-Spam-Level: 
X-Spam-Status: No, score=-2.303 tagged_above=-999 required=5 tests=[AWL=0.296,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eWcTi86HmjYw for <homenet@ietfa.amsl.com>; Tue, 22 Nov 2011 23:10:35 -0800 (PST)
Received: from omr17.networksolutionsemail.com (omr17.networksolutionsemail.com [205.178.146.67]) by ietfa.amsl.com (Postfix) with ESMTP id C395821F88B6 for <homenet@ietf.org>; Tue, 22 Nov 2011 23:10:34 -0800 (PST)
Received: from cm-omr9 (mail.networksolutionsemail.com [205.178.146.50]) by omr17.networksolutionsemail.com (8.13.8/8.13.8) with ESMTP id pAN7AUIM017167 for <homenet@ietf.org>; Wed, 23 Nov 2011 02:10:33 -0500
X-Authenticated-IP: 98.151.18.158
Received: from [98.151.18.158] ([98.151.18.158:54428] helo=[192.168.1.105]) by cm-omr9 (envelope-from <rturner@amalfisystems.com>) (ecelerity 2.2.2.41 r(31179/31189)) with ESMTP id 0C/1C-04778-66C9CCE4; Wed, 23 Nov 2011 02:10:30 -0500
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Randy Turner <rturner@amalfisystems.com>
In-Reply-To: <35ABFE5A-789F-4268-812F-BCA00ACC388F@cisco.com>
Date: Tue, 22 Nov 2011 23:10:29 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <4CD8F7DD-59C9-428F-A5C4-70FF6C35179B@amalfisystems.com>
References: <DCC302FAA9FE5F4BBA4DCAD4656937791452BBC0CC@PRVPEXVS03.corp.twcable.com> <A7A4DFCE-C09D-49F7-A772-B3FC5F575CA1@amalfisystems.com> <35ABFE5A-789F-4268-812F-BCA00ACC388F@cisco.com>
To: Fred Baker <fred@cisco.com>
X-Mailer: Apple Mail (2.1084)
Cc: "Howard, Lee" <lee.howard@twcable.com>, "homenet@ietf.org" <homenet@ietf.org>
Subject: Re: [homenet] other routing options
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 23 Nov 2011 07:10:37 -0000

So we either bite off much more than we need and get the flexibility of =
link-state (OSPF), or we add "bounds" to a Bellman-Ford implementation =
to constrain the count-to-infinity problem, and say that the increased =
convergence time is ok given that this potential event is unlikely to =
happen, or that the mean-time between these types of "link-down" events =
can absorb an increased convergence time.

I do prefer link-state over DV...I'm just trying to look at alternatives =
:)

We still have the ongoing discussion of how to make all this =
auto-configurable...

R.

On Nov 22, 2011, at 10:45 PM, Fred Baker wrote:

>=20
> On Nov 22, 2011, at 2:49 PM, Randy Turner wrote:
>=20
>> That's how I felt until incredibly elaborate home net topologies were =
suggested -- but it still seems intuitively heavyweight for a "home" =
network.  If we do end up using OSPF, then maybe home networks are *not* =
simple as one would think, but rather a different instantiation of a =
complex routing scenario, just with "zeroconf" requirements.
>=20
> well, halfway in between. If you have a wired LAN and a wireless LAN =
with two wired/wireless routers, I suspect you have a routing topology =
with at least one redundant path. I don't care how many nodes you have; =
if you have a tree, it is "simple" for any protocol. If you have =
not-all-that-many nodes but have redundancy in the topology, you have =
the possibility of count-to-infinity problems with a bellman-ford =
protocol like RIPng. I would suspect that a home network is small =
compared to, say, a campus in an enterprise network, but if it has =
redundancy it has at least some probability of the same class of issues.
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>=20


From rturner@amalfisystems.com  Tue Nov 22 23:29:29 2011
Return-Path: <rturner@amalfisystems.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C517A11E8095 for <homenet@ietfa.amsl.com>; Tue, 22 Nov 2011 23:29:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.345
X-Spam-Level: 
X-Spam-Status: No, score=-2.345 tagged_above=-999 required=5 tests=[AWL=0.254,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y6jt-diK+b20 for <homenet@ietfa.amsl.com>; Tue, 22 Nov 2011 23:29:29 -0800 (PST)
Received: from omr8.networksolutionsemail.com (omr8.networksolutionsemail.com [205.178.146.58]) by ietfa.amsl.com (Postfix) with ESMTP id 1F75311E808E for <homenet@ietf.org>; Tue, 22 Nov 2011 23:29:29 -0800 (PST)
Received: from cm-omr12 (mail.networksolutionsemail.com [205.178.146.50]) by omr8.networksolutionsemail.com (8.13.8/8.13.8) with ESMTP id pAN7TQre005532 for <homenet@ietf.org>; Wed, 23 Nov 2011 02:29:28 -0500
Authentication-Results: cm-omr12 smtp.user=rturner@amalfisystems.com; auth=pass (CRAM-MD5)
X-Authenticated-UID: rturner@amalfisystems.com
Received: from [98.151.18.158] ([98.151.18.158:62041] helo=[192.168.1.114]) by cm-omr12 (envelope-from <rturner@amalfisystems.com>) (ecelerity 2.2.2.41 r(31179/31189)) with ESMTPSA (cipher=AES128-SHA)  id B8/42-03697-5D0ACCE4; Wed, 23 Nov 2011 02:29:26 -0500
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=windows-1252
From: Randy Turner <rturner@amalfisystems.com>
In-Reply-To: <4CD8F7DD-59C9-428F-A5C4-70FF6C35179B@amalfisystems.com>
Date: Tue, 22 Nov 2011 23:29:38 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <96721D08-D39B-4753-9BFA-3AB5B7632E54@amalfisystems.com>
References: <DCC302FAA9FE5F4BBA4DCAD4656937791452BBC0CC@PRVPEXVS03.corp.twcable.com> <A7A4DFCE-C09D-49F7-A772-B3FC5F575CA1@amalfisystems.com> <35ABFE5A-789F-4268-812F-BCA00ACC388F@cisco.com> <4CD8F7DD-59C9-428F-A5C4-70FF6C35179B@amalfisystems.com>
To: Fred Baker <fred@cisco.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: "Howard, Lee" <lee.howard@twcable.com>, "homenet@ietf.org" <homenet@ietf.org>
Subject: Re: [homenet] other routing options
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 23 Nov 2011 07:29:29 -0000

On the point of autoconfig=85in future references to OSPF, can I =
substitute zOSPF ?  I'm assuming that we're not talking about deploying =
an off-the-shelf OSPF implementation because of the configuration impact =
on a home network consumer.  So I was also assuming that I could =
substitute zOSPF anytime someone mentions OSPF.

R.

On Nov 22, 2011, at 11:10 PM, Randy Turner wrote:

>=20
> So we either bite off much more than we need and get the flexibility =
of link-state (OSPF), or we add "bounds" to a Bellman-Ford =
implementation to constrain the count-to-infinity problem, and say that =
the increased convergence time is ok given that this potential event is =
unlikely to happen, or that the mean-time between these types of =
"link-down" events can absorb an increased convergence time.
>=20
> I do prefer link-state over DV...I'm just trying to look at =
alternatives :)
>=20
> We still have the ongoing discussion of how to make all this =
auto-configurable...
>=20
> R.
>=20
> On Nov 22, 2011, at 10:45 PM, Fred Baker wrote:
>=20
>>=20
>> On Nov 22, 2011, at 2:49 PM, Randy Turner wrote:
>>=20
>>> That's how I felt until incredibly elaborate home net topologies =
were suggested -- but it still seems intuitively heavyweight for a =
"home" network.  If we do end up using OSPF, then maybe home networks =
are *not* simple as one would think, but rather a different =
instantiation of a complex routing scenario, just with "zeroconf" =
requirements.
>>=20
>> well, halfway in between. If you have a wired LAN and a wireless LAN =
with two wired/wireless routers, I suspect you have a routing topology =
with at least one redundant path. I don't care how many nodes you have; =
if you have a tree, it is "simple" for any protocol. If you have =
not-all-that-many nodes but have redundancy in the topology, you have =
the possibility of count-to-infinity problems with a bellman-ford =
protocol like RIPng. I would suspect that a home network is small =
compared to, say, a campus in an enterprise network, but if it has =
redundancy it has at least some probability of the same class of issues.
>> _______________________________________________
>> 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
>=20


From Laurent.Toutain@telecom-bretagne.eu  Tue Nov 22 23:36:21 2011
Return-Path: <Laurent.Toutain@telecom-bretagne.eu>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA6EC11E8095 for <homenet@ietfa.amsl.com>; Tue, 22 Nov 2011 23:36:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.409
X-Spam-Level: 
X-Spam-Status: No, score=-0.409 tagged_above=-999 required=5 tests=[AWL=1.333,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HELO_EQ_FR=0.35, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5E+u1wgTWRq3 for <homenet@ietfa.amsl.com>; Tue, 22 Nov 2011 23:36:20 -0800 (PST)
Received: from coliposte.enst-bretagne.fr (coliposte.enst-bretagne.fr [192.108.115.12]) by ietfa.amsl.com (Postfix) with ESMTP id 855D421F84CD for <homenet@ietf.org>; Tue, 22 Nov 2011 23:36:20 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by coliposte.enst-bretagne.fr (8.13.7/8.13.7/2009.11.10) with ESMTP id pAN7aFai022237 for <homenet@ietf.org>; Wed, 23 Nov 2011 08:36:15 +0100
Received: from courrier.enst-bretagne.fr (smtps.enst-bretagne.fr [10.29.90.4]) by coliposte.enst-bretagne.fr (8.13.7/8.13.7/2009.11.10) with ESMTP id pAN7a7Vf022209 for <homenet@ietf.org>; Wed, 23 Nov 2011 08:36:11 +0100
Received: from mail-ww0-f44.google.com (passerelle-interne.enst-bretagne.fr [192.108.117.210]) (user=toutain mech=PLAIN bits=0) by courrier.enst-bretagne.fr (8.13.8/8.13.8/2010.02.22) with ESMTP id pAN7a54p007604 for <homenet@ietf.org>; Wed, 23 Nov 2011 08:36:05 +0100
Received: by wwe5 with SMTP id 5so1316822wwe.13 for <homenet@ietf.org>; Tue, 22 Nov 2011 23:36:05 -0800 (PST)
Received: by 10.216.188.145 with SMTP id a17mr3817238wen.24.1322033765344; Tue, 22 Nov 2011 23:36:05 -0800 (PST)
MIME-Version: 1.0
Received: by 10.216.26.3 with HTTP; Tue, 22 Nov 2011 23:35:44 -0800 (PST)
In-Reply-To: <DCC302FAA9FE5F4BBA4DCAD4656937791452BBC0CC@PRVPEXVS03.corp.twcable.com>
References: <DCC302FAA9FE5F4BBA4DCAD4656937791452BBC0CC@PRVPEXVS03.corp.twcable.com>
From: Laurent Toutain <Laurent.Toutain@telecom-bretagne.eu>
Date: Wed, 23 Nov 2011 08:35:44 +0100
Message-ID: <CABONVQbMsY6MF_8q44XqGmdOMS6Odn+CjBEttaEs9rhmknwRxg@mail.gmail.com>
To: "Howard, Lee" <lee.howard@twcable.com>
Content-Type: multipart/alternative; boundary=0016e659fd0af6e81104b261f8bd
X-Virus-Scanned: amavisd-new at enst-bretagne.fr
Cc: "homenet@ietf.org" <homenet@ietf.org>
Subject: Re: [homenet] other routing options
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 23 Nov 2011 07:36:21 -0000

--0016e659fd0af6e81104b261f8bd
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Tue, Nov 22, 2011 at 23:36, Howard, Lee <lee.howard@twcable.com> wrote:

> Ray asked for people to post drafts for anything other than OSPF, because
> without an alternative, it will appear that we have consensus on OSPF.  I
> haven't posted a draft on RIPng, because it would just work the way it's
> designed.
>
> A few people said  http://tools.ietf.org/html/draft-howard-up-pio-00 is
> no better than RIP, and we already have RIP in home gateways.  Can any
> gateway vendor confirm whether RIPng is already in gateways?
>
> Proposed alternatives are:
> * OSPFv3.  It's heavyweight for home routing.  We still need a way to fin=
d
> the border and inject default.  It could be used for DHCP-PD.
>

I don't understand that: a border gateway is a specific device.


> --

Laurent Toutain
+--- VoIP (recommended) ---+----------- T=E9l=E9com Bretagne -----------+
| Tel: +33 2 22 06 8156    | Tel: + 33 2 99 12 7026                 | Visit
:
| Fax: +33 2 22 06 8445    | Fax: +33 2 99 12 7030                  |
http://class.touta.in
| Laurent@Touta.in         | Laurent.Toutain@Telecom-Bretagne.eu    |
+--------------------------+----------------------------------------+

--0016e659fd0af6e81104b261f8bd
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><br><div class=3D"gmail_quote">On Tue, Nov 22, 2011 at 23:36, Howard, L=
ee <span dir=3D"ltr">&lt;<a href=3D"mailto:lee.howard@twcable.com">lee.howa=
rd@twcable.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">

Ray asked for people to post drafts for anything other than OSPF, because w=
ithout an alternative, it will appear that we have consensus on OSPF. =A0I =
haven&#39;t posted a draft on RIPng, because it would just work the way it&=
#39;s designed.<br>


<br>
A few people said =A0<a href=3D"http://tools.ietf.org/html/draft-howard-up-=
pio-00" target=3D"_blank">http://tools.ietf.org/html/draft-howard-up-pio-00=
</a> is no better than RIP, and we already have RIP in home gateways. =A0Ca=
n any gateway vendor confirm whether RIPng is already in gateways?<br>


<br>
Proposed alternatives are:<br>
* OSPFv3. =A0It&#39;s heavyweight for home routing. =A0We still need a way =
to find the border and inject default. =A0It could be used for DHCP-PD.<br>=
</blockquote><div><br></div><div>I don&#39;t understand that: a border gate=
way is a specific device.</div>

<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex;">--=A0</blockquote></div>Laure=
nt Toutain<br><font face=3D"&#39;courier new&#39;, monospace">+--- VoIP (re=
commended) ---+----------- T=E9l=E9com Bretagne -----------+<br>

| Tel: +33 2 22 06 8156 =A0 =A0| Tel: + 33 2 99 12 7026 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0 | Visit :<br>| Fax: +33 2 22 06 8445 =A0 =A0| Fax: +33 2 99 12=
 7030 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0| =A0<a href=3D"http://class.touta=
.in" target=3D"_blank">http://class.touta.in</a><br>

| Laurent@Touta.in =A0 =A0 =A0 =A0 | Laurent.Toutain@Telecom-Bretagne.eu =
=A0 =A0|<br>+--------------------------+-----------------------------------=
-----+</font><br>

--0016e659fd0af6e81104b261f8bd--

From mark@townsley.net  Tue Nov 22 23:47:48 2011
Return-Path: <mark@townsley.net>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8224A21F87D3 for <homenet@ietfa.amsl.com>; Tue, 22 Nov 2011 23:47:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.449
X-Spam-Level: 
X-Spam-Status: No, score=-3.449 tagged_above=-999 required=5 tests=[AWL=0.150,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D-3vwTFcecHV for <homenet@ietfa.amsl.com>; Tue, 22 Nov 2011 23:47:48 -0800 (PST)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id D15ED21F87E2 for <homenet@ietf.org>; Tue, 22 Nov 2011 23:47:47 -0800 (PST)
Received: by wwe5 with SMTP id 5so1327000wwe.13 for <homenet@ietf.org>; Tue, 22 Nov 2011 23:47:47 -0800 (PST)
Received: by 10.180.92.169 with SMTP id cn9mr21817371wib.62.1322034467002; Tue, 22 Nov 2011 23:47:47 -0800 (PST)
Received: from ams-townsley-8712.cisco.com (64-103-25-233.cisco.com. [64.103.25.233]) by mx.google.com with ESMTPS id dw6sm7825655wib.12.2011.11.22.23.47.44 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 22 Nov 2011 23:47:44 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Mark Townsley <mark@townsley.net>
In-Reply-To: <4CD8F7DD-59C9-428F-A5C4-70FF6C35179B@amalfisystems.com>
Date: Wed, 23 Nov 2011 08:47:42 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <46DE0F06-1317-41E3-84B1-5C8F5AF0C4AA@townsley.net>
References: <DCC302FAA9FE5F4BBA4DCAD4656937791452BBC0CC@PRVPEXVS03.corp.twcable.com> <A7A4DFCE-C09D-49F7-A772-B3FC5F575CA1@amalfisystems.com> <35ABFE5A-789F-4268-812F-BCA00ACC388F@cisco.com> <4CD8F7DD-59C9-428F-A5C4-70FF6C35179B@amalfisystems.com>
To: Randy Turner <rturner@amalfisystems.com>
X-Mailer: Apple Mail (2.1084)
Cc: "Howard, Lee" <lee.howard@twcable.com>, "homenet@ietf.org" <homenet@ietf.org>, Fred Baker <fred@cisco.com>
Subject: Re: [homenet] other routing options
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 23 Nov 2011 07:47:48 -0000

On Nov 23, 2011, at 8:10 AM, Randy Turner wrote:

> We still have the ongoing discussion of how to make all this =
auto-configurable...

Which I think is the more significant piece.... And why we cannot simply =
accept "just use RIPng" on its own. We have to see what any routing =
protocol is going to look like with set (by us) defaults and no user =
configuration, as well as how it either incorporates or interfaces with =
prefix assignment, border detection, etc. Given the ongoing problems =
interfacing ND and DHCPv6 we are living through right now with 6204++, I =
am personally wary to accept that any of these facets in the homenet can =
truly operate independent from one another. As such, if we have separate =
protocols and state machines, their interaction needs to be very tightly =
defined.

- Mark=

From v6ops@globis.net  Wed Nov 23 00:33:18 2011
Return-Path: <v6ops@globis.net>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08C1E21F8B88 for <homenet@ietfa.amsl.com>; Wed, 23 Nov 2011 00:33:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.11
X-Spam-Level: 
X-Spam-Status: No, score=-2.11 tagged_above=-999 required=5 tests=[AWL=-0.396,  BAYES_00=-2.599, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q15hDoGaA5zM for <homenet@ietfa.amsl.com>; Wed, 23 Nov 2011 00:33:17 -0800 (PST)
Received: from globis01.globis.net (RayH-1-pt.tunnel.tserv11.ams1.ipv6.he.net [IPv6:2001:470:1f14:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id F1FF721F853E for <homenet@ietf.org>; Wed, 23 Nov 2011 00:33:16 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id 467AC8700EF; Wed, 23 Nov 2011 09:33:15 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at globis01.globis.net
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 v4qDp51jECEb; Wed, 23 Nov 2011 09:33:08 +0100 (CET)
Received: from Rays-iMac.local (unknown [192.168.0.3]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPA id CFF69870083; Wed, 23 Nov 2011 09:33:07 +0100 (CET)
Message-ID: <4ECCAFC3.5060903@globis.net>
Date: Wed, 23 Nov 2011 09:33:07 +0100
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox Express 1.0.1 (Macintosh/20100705)
MIME-Version: 1.0
To: Laurent Toutain <Laurent.Toutain@telecom-bretagne.eu>
References: <DCC302FAA9FE5F4BBA4DCAD4656937791452BBC0CC@PRVPEXVS03.corp.twcable.com> <CABONVQbMsY6MF_8q44XqGmdOMS6Odn+CjBEttaEs9rhmknwRxg@mail.gmail.com>
In-Reply-To: <CABONVQbMsY6MF_8q44XqGmdOMS6Odn+CjBEttaEs9rhmknwRxg@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------030604070602000705060209"
Cc: "Howard, Lee" <lee.howard@twcable.com>, "homenet@ietf.org" <homenet@ietf.org>
Subject: Re: [homenet] other routing options
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 23 Nov 2011 08:33:18 -0000

This is a multi-part message in MIME format.
--------------030604070602000705060209
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Suspect "border" in this context means "the administrative edge of the 
Homenet domain" and not "OSPF area border router"
Autoconfig has to know when to stop including new devices.

IMHO increasing use of (overlapping) (low power) wireless networks in 
Homenet will only make count to infinity type problems more common, as 
marginal adjacencies come and go. You can solve that within a wireless 
technology, but there's still always going to be the route-over problem 
of overlapping technologies like WiFi versus copper.

What about multicast support for streaming video to my iDevice as I walk 
from the lounge to the pool? AV will likely be a major homenet 
application. OSPF => MOSPF? IPng => DVMRP? Or should that use unicast + 
mobile IPv6?

regards
RayH

Laurent Toutain wrote:
> On Tue, Nov 22, 2011 at 23:36, Howard, Lee <lee.howard@twcable.com 
> <mailto:lee.howard@twcable.com>> wrote:
>
>     Ray asked for people to post drafts for anything other than OSPF,
>     because without an alternative, it will appear that we have
>     consensus on OSPF.  I haven't posted a draft on RIPng, because it
>     would just work the way it's designed.
>
>     A few people said
>     http://tools.ietf.org/html/draft-howard-up-pio-00 is no better
>     than RIP, and we already have RIP in home gateways.  Can any
>     gateway vendor confirm whether RIPng is already in gateways?
>
>     Proposed alternatives are:
>     * OSPFv3.  It's heavyweight for home routing.  We still need a way
>     to find the border and inject default.  It could be used for DHCP-PD.
>
>
> I don't understand that: a border gateway is a specific device.
>
>     -- 
>
> Laurent Toutain
> +--- VoIP (recommended) ---+----------- Télécom Bretagne -----------+
> | Tel: +33 2 22 06 8156    | Tel: + 33 2 99 12 7026                 | 
> Visit :
> | Fax: +33 2 22 06 8445    | Fax: +33 2 99 12 7030                  | 
> http://class.touta.in
> | Laurent@Touta.in         | Laurent.Toutain@Telecom-Bretagne.eu    |
> +--------------------------+----------------------------------------+

--------------030604070602000705060209
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html; charset=ISO-8859-1"
 http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Suspect "border" in this context means "the administrative edge of the
Homenet domain" and not "OSPF area border router"<br>
Autoconfig has to know when to stop including new devices.<br>
<br>
IMHO increasing use of (overlapping) (low power) wireless networks in
Homenet will only make count to infinity type problems more common, as
marginal adjacencies come and go. You can solve that within a wireless
technology, but there's still always going to be the route-over problem
of overlapping technologies like WiFi versus copper.<br>
<br>
What about multicast support for streaming video to my iDevice as I
walk from the lounge to the pool? AV will likely be a major homenet
application. OSPF =&gt; MOSPF? IPng =&gt; DVMRP? Or should that use
unicast + mobile IPv6?<br>
<br>
regards<br>
RayH<br>
<br>
Laurent Toutain wrote:
<blockquote
 cite="mid:%3CCABONVQbMsY6MF_8q44XqGmdOMS6Odn+CjBEttaEs9rhmknwRxg@mail.gmail.com%3E"
 type="cite">
  <div class="gmail_quote">On Tue, Nov 22, 2011 at 23:36, Howard, Lee <span
 dir="ltr">&lt;<a moz-do-not-send="true"
 href="mailto:lee.howard@twcable.com">lee.howard@twcable.com</a>&gt;</span>
wrote:<br>
  <blockquote class="gmail_quote"
 style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Ray
asked for people to post drafts for anything other than OSPF, because
without an alternative, it will appear that we have consensus on OSPF.
&nbsp;I haven't posted a draft on RIPng, because it would just work the way
it's designed.<br>
    <br>
A few people said &nbsp;<a moz-do-not-send="true"
 href="http://tools.ietf.org/html/draft-howard-up-pio-00"
 target="_blank">http://tools.ietf.org/html/draft-howard-up-pio-00</a>
is no better than RIP, and we already have RIP in home gateways. &nbsp;Can
any gateway vendor confirm whether RIPng is already in gateways?<br>
    <br>
Proposed alternatives are:<br>
* OSPFv3. &nbsp;It's heavyweight for home routing. &nbsp;We still need a way to
find the border and inject default. &nbsp;It could be used for DHCP-PD.</blockquote>
  <div><br>
  </div>
  <div>I don't understand that: a border gateway is a specific device.</div>
  <div>&nbsp;</div>
  <blockquote class="gmail_quote"
 style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">--&nbsp;</blockquote>
  </div>
Laurent Toutain<br>
  <font face="'courier new', monospace">+--- VoIP (recommended)
---+----------- T&eacute;l&eacute;com Bretagne -----------+<br>
| Tel: +33 2 22 06 8156 &nbsp; &nbsp;| Tel: + 33 2 99 12 7026 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; |
Visit :<br>
| Fax: +33 2 22 06 8445 &nbsp; &nbsp;| Fax: +33 2 99 12 7030 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;| &nbsp;<a
 moz-do-not-send="true" href="http://class.touta.in" target="_blank">http://class.touta.in</a><br>
| <a class="moz-txt-link-abbreviated" href="mailto:Laurent@Touta.in">Laurent@Touta.in</a> &nbsp; &nbsp; &nbsp; &nbsp; | <a class="moz-txt-link-abbreviated" href="mailto:Laurent.Toutain@Telecom-Bretagne.eu">Laurent.Toutain@Telecom-Bretagne.eu</a> &nbsp; &nbsp;|<br>
+--------------------------+----------------------------------------+</font></blockquote>
</body>
</html>

--------------030604070602000705060209--

From rturner@amalfisystems.com  Wed Nov 23 00:46:46 2011
Return-Path: <rturner@amalfisystems.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F0E1421F8C21 for <homenet@ietfa.amsl.com>; Wed, 23 Nov 2011 00:46:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.714
X-Spam-Level: 
X-Spam-Status: No, score=-1.714 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G4iaN30ujAdD for <homenet@ietfa.amsl.com>; Wed, 23 Nov 2011 00:46:45 -0800 (PST)
Received: from omr13.networksolutionsemail.com (omr13.networksolutionsemail.com [205.178.146.63]) by ietfa.amsl.com (Postfix) with ESMTP id 4287E21F8C20 for <homenet@ietf.org>; Wed, 23 Nov 2011 00:46:39 -0800 (PST)
Received: from cm-omr12 (mail.networksolutionsemail.com [205.178.146.50]) by omr13.networksolutionsemail.com (8.13.8/8.13.8) with ESMTP id pAN8kaqS023899 for <homenet@ietf.org>; Wed, 23 Nov 2011 03:46:38 -0500
Authentication-Results: cm-omr12 smtp.user=rturner@amalfisystems.com; auth=pass (LOGIN)
X-Authenticated-UID: rturner@amalfisystems.com
Received: from [32.155.71.63] ([32.155.71.63:34342] helo=localhost) by cm-omr12 (envelope-from <rturner@amalfisystems.com>) (ecelerity 2.2.2.41 r(31179/31189)) with ESMTPA id 7D/31-03697-9E2BCCE4; Wed, 23 Nov 2011 03:46:35 -0500
Date: Wed, 23 Nov 2011 00:46:26 -0800
Message-ID: <tsbj6let0wnqfal2ns4cy2je.1322037986689@email.android.com>
Importance: normal
From: Randy <rturner@amalfisystems.com>
To: v6ops@globis.net, laurent.toutain@telecom-bretagne.eu
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="--_com.android.email_9737392166021"
Cc: lee.howard@twcable.com, homenet@ietf.org
Subject: Re: [homenet] other routing options
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 23 Nov 2011 08:46:46 -0000

----_com.android.email_9737392166021
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64

SSB3b3VsZCBleHBlY3QgQVYgdHJhZmZpYyB0byBkb21pbmF0ZSBob21lbmV0LCBtb3JlIFYgdGhh
biBBLsKgCgpBbmQgSSAiKzEiIE1hcmsncyBlYXJsaWVyIGNvbW1lbnQgYWJvdXQgwqBhdXRvY29u
ZmlnIGJlaW5nIHRoZSByZWFsIGNoYWxsZW5nZS4gSSBoYXZlIGFzc3VtZWQgdGhpcyBmcm9tIHRo
ZSBzdGFydC4KClIuCgogUmF5IEh1bnRlciA8djZvcHNAZ2xvYmlzLm5ldD4gd3JvdGU6IAoKwqBT
dXNwZWN0ICJib3JkZXIiIGluIHRoaXMgY29udGV4dCBtZWFucyAidGhlIGFkbWluaXN0cmF0aXZl
IGVkZ2Ugb2YgdGhlIEhvbWVuZXQgZG9tYWluIiBhbmQgbm90ICJPU1BGIGFyZWEgYm9yZGVyIHJv
dXRlciIKQXV0b2NvbmZpZyBoYXMgdG8ga25vdyB3aGVuIHRvIHN0b3AgaW5jbHVkaW5nIG5ldyBk
ZXZpY2VzLgoKSU1ITyBpbmNyZWFzaW5nIHVzZSBvZiAob3ZlcmxhcHBpbmcpIChsb3cgcG93ZXIp
IHdpcmVsZXNzIG5ldHdvcmtzIGluIEhvbWVuZXQgd2lsbCBvbmx5IG1ha2UgY291bnQgdG8gaW5m
aW5pdHkgdHlwZSBwcm9ibGVtcyBtb3JlIGNvbW1vbiwgYXMgbWFyZ2luYWwgYWRqYWNlbmNpZXMg
Y29tZSBhbmQgZ28uIFlvdSBjYW4gc29sdmUgdGhhdCB3aXRoaW4gYSB3aXJlbGVzcyB0ZWNobm9s
b2d5LCBidXQgdGhlcmUncyBzdGlsbCBhbHdheXMgZ29pbmcgdG8gYmUgdGhlIHJvdXRlLW92ZXIg
cHJvYmxlbSBvZiBvdmVybGFwcGluZyB0ZWNobm9sb2dpZXMgbGlrZSBXaUZpIHZlcnN1cyBjb3Bw
ZXIuCgpXaGF0IGFib3V0IG11bHRpY2FzdCBzdXBwb3J0IGZvciBzdHJlYW1pbmcgdmlkZW8gdG8g
bXkgaURldmljZSBhcyBJIHdhbGsgZnJvbSB0aGUgbG91bmdlIHRvIHRoZSBwb29sPyBBViB3aWxs
IGxpa2VseSBiZSBhIG1ham9yIGhvbWVuZXQgYXBwbGljYXRpb24uIE9TUEYgPT4gTU9TUEY/IElQ
bmcgPT4gRFZNUlA/IE9yIHNob3VsZCB0aGF0IHVzZSB1bmljYXN0ICsgbW9iaWxlIElQdjY/Cgpy
ZWdhcmRzClJheUgKCkxhdXJlbnQgVG91dGFpbiB3cm90ZToKT24gVHVlLCBOb3YgMjIsIDIwMTEg
YXQgMjM6MzYsIEhvd2FyZCwgTGVlIDxsZWUuaG93YXJkQHR3Y2FibGUuY29tPiB3cm90ZToKUmF5
IGFza2VkIGZvciBwZW9wbGUgdG8gcG9zdCBkcmFmdHMgZm9yIGFueXRoaW5nIG90aGVyIHRoYW4g
T1NQRiwgYmVjYXVzZSB3aXRob3V0IGFuIGFsdGVybmF0aXZlLCBpdCB3aWxsIGFwcGVhciB0aGF0
IHdlIGhhdmUgY29uc2Vuc3VzIG9uIE9TUEYuIMKgSSBoYXZlbid0IHBvc3RlZCBhIGRyYWZ0IG9u
IFJJUG5nLCBiZWNhdXNlIGl0IHdvdWxkIGp1c3Qgd29yayB0aGUgd2F5IGl0J3MgZGVzaWduZWQu
CgpBIGZldyBwZW9wbGUgc2FpZCDCoGh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWhv
d2FyZC11cC1waW8tMDAgaXMgbm8gYmV0dGVyIHRoYW4gUklQLCBhbmQgd2UgYWxyZWFkeSBoYXZl
IFJJUCBpbiBob21lIGdhdGV3YXlzLiDCoENhbiBhbnkgZ2F0ZXdheSB2ZW5kb3IgY29uZmlybSB3
aGV0aGVyIFJJUG5nIGlzIGFscmVhZHkgaW4gZ2F0ZXdheXM/CgpQcm9wb3NlZCBhbHRlcm5hdGl2
ZXMgYXJlOgoqIE9TUEZ2My4gwqBJdCdzIGhlYXZ5d2VpZ2h0IGZvciBob21lIHJvdXRpbmcuIMKg
V2Ugc3RpbGwgbmVlZCBhIHdheSB0byBmaW5kIHRoZSBib3JkZXIgYW5kIGluamVjdCBkZWZhdWx0
LiDCoEl0IGNvdWxkIGJlIHVzZWQgZm9yIERIQ1AtUEQuCgpJIGRvbid0IHVuZGVyc3RhbmQgdGhh
dDogYSBib3JkZXIgZ2F0ZXdheSBpcyBhIHNwZWNpZmljIGRldmljZS4KwqAKLS3CoApMYXVyZW50
IFRvdXRhaW4KKy0tLSBWb0lQIChyZWNvbW1lbmRlZCkgLS0tKy0tLS0tLS0tLS0tIFTDqWzDqWNv
bSBCcmV0YWduZSAtLS0tLS0tLS0tLSsKfCBUZWw6ICszMyAyIDIyIDA2IDgxNTYgwqAgwqB8IFRl
bDogKyAzMyAyIDk5IDEyIDcwMjYgwqAgwqAgwqAgwqAgwqAgwqAgwqAgwqAgfCBWaXNpdCA6Cnwg
RmF4OiArMzMgMiAyMiAwNiA4NDQ1IMKgIMKgfCBGYXg6ICszMyAyIDk5IDEyIDcwMzAgwqAgwqAg
wqAgwqAgwqAgwqAgwqAgwqAgwqB8IMKgaHR0cDovL2NsYXNzLnRvdXRhLmluCnwgTGF1cmVudEBU
b3V0YS5pbiDCoCDCoCDCoCDCoCB8IExhdXJlbnQuVG91dGFpbkBUZWxlY29tLUJyZXRhZ25lLmV1
IMKgIMKgfAorLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0rLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLSsK

----_com.android.email_9737392166021
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: base64

PGh0bWw+PGhlYWQ+PG1ldGEgaHR0cC1lcXVpdj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0
L2h0bWw7IGNoYXJzZXQ9VVRGLTgiPjwvaGVhZD48Ym9keT5JIHdvdWxkIGV4cGVjdCBBViB0cmFm
ZmljIHRvIGRvbWluYXRlIGhvbWVuZXQsIG1vcmUgViB0aGFuIEEuJm5ic3A7PGRpdj48YnI+PC9k
aXY+PGRpdj5BbmQgSSAiKzEiIE1hcmsncyBlYXJsaWVyIGNvbW1lbnQgYWJvdXQgJm5ic3A7YXV0
b2NvbmZpZyBiZWluZyB0aGUgcmVhbCBjaGFsbGVuZ2UuIEkgaGF2ZSBhc3N1bWVkIHRoaXMgZnJv
bSB0aGUgc3RhcnQuPC9kaXY+PGRpdj48YnI+PC9kaXY+PGRpdj5SLjwvZGl2Pjxicj48YnI+PGJy
PiBSYXkgSHVudGVyICZsdDt2Nm9wc0BnbG9iaXMubmV0Jmd0OyB3cm90ZTogPGJyPjxicj48YnI+
Jm5ic3A7U3VzcGVjdCAiYm9yZGVyIiBpbiB0aGlzIGNvbnRleHQgbWVhbnMgInRoZSBhZG1pbmlz
dHJhdGl2ZSBlZGdlIG9mIHRoZQpIb21lbmV0IGRvbWFpbiIgYW5kIG5vdCAiT1NQRiBhcmVhIGJv
cmRlciByb3V0ZXIiPGJyPgpBdXRvY29uZmlnIGhhcyB0byBrbm93IHdoZW4gdG8gc3RvcCBpbmNs
dWRpbmcgbmV3IGRldmljZXMuPGJyPgo8YnI+CklNSE8gaW5jcmVhc2luZyB1c2Ugb2YgKG92ZXJs
YXBwaW5nKSAobG93IHBvd2VyKSB3aXJlbGVzcyBuZXR3b3JrcyBpbgpIb21lbmV0IHdpbGwgb25s
eSBtYWtlIGNvdW50IHRvIGluZmluaXR5IHR5cGUgcHJvYmxlbXMgbW9yZSBjb21tb24sIGFzCm1h
cmdpbmFsIGFkamFjZW5jaWVzIGNvbWUgYW5kIGdvLiBZb3UgY2FuIHNvbHZlIHRoYXQgd2l0aGlu
IGEgd2lyZWxlc3MKdGVjaG5vbG9neSwgYnV0IHRoZXJlJ3Mgc3RpbGwgYWx3YXlzIGdvaW5nIHRv
IGJlIHRoZSByb3V0ZS1vdmVyIHByb2JsZW0Kb2Ygb3ZlcmxhcHBpbmcgdGVjaG5vbG9naWVzIGxp
a2UgV2lGaSB2ZXJzdXMgY29wcGVyLjxicj4KPGJyPgpXaGF0IGFib3V0IG11bHRpY2FzdCBzdXBw
b3J0IGZvciBzdHJlYW1pbmcgdmlkZW8gdG8gbXkgaURldmljZSBhcyBJCndhbGsgZnJvbSB0aGUg
bG91bmdlIHRvIHRoZSBwb29sPyBBViB3aWxsIGxpa2VseSBiZSBhIG1ham9yIGhvbWVuZXQKYXBw
bGljYXRpb24uIE9TUEYgPSZndDsgTU9TUEY/IElQbmcgPSZndDsgRFZNUlA/IE9yIHNob3VsZCB0
aGF0IHVzZQp1bmljYXN0ICsgbW9iaWxlIElQdjY/PGJyPgo8YnI+CnJlZ2FyZHM8YnI+ClJheUg8
YnI+Cjxicj4KTGF1cmVudCBUb3V0YWluIHdyb3RlOgo8YmxvY2txdW90ZSBjaXRlPSJtaWQ6JTND
Q0FCT05WUWJNc1k2TUZfOHE0NFhxR21kT01TNk9kbitDakJFdHRhRXM5cmhta253UnhnQG1haWwu
Z21haWwuY29tJTNFIiB0eXBlPSJjaXRlIj4KICA8ZGl2IGNsYXNzPSJnbWFpbF9xdW90ZSI+T24g
VHVlLCBOb3YgMjIsIDIwMTEgYXQgMjM6MzYsIEhvd2FyZCwgTGVlIDxzcGFuIGRpcj0ibHRyIj4m
bHQ7PGEgbW96LWRvLW5vdC1zZW5kPSJ0cnVlIiBocmVmPSJtYWlsdG86bGVlLmhvd2FyZEB0d2Nh
YmxlLmNvbSI+bGVlLmhvd2FyZEB0d2NhYmxlLmNvbTwvYT4mZ3Q7PC9zcGFuPgp3cm90ZTo8YnI+
CiAgPGJsb2NrcXVvdGUgY2xhc3M9ImdtYWlsX3F1b3RlIiBzdHlsZT0iYm9yZGVyLWxlZnQ6IDFw
eCBzb2xpZCByZ2IoMjA0LCAyMDQsIDIwNCk7IG1hcmdpbjogMHB0IDBwdCAwcHQgMC44ZXg7IHBh
ZGRpbmctbGVmdDogMWV4OyI+UmF5CmFza2VkIGZvciBwZW9wbGUgdG8gcG9zdCBkcmFmdHMgZm9y
IGFueXRoaW5nIG90aGVyIHRoYW4gT1NQRiwgYmVjYXVzZQp3aXRob3V0IGFuIGFsdGVybmF0aXZl
LCBpdCB3aWxsIGFwcGVhciB0aGF0IHdlIGhhdmUgY29uc2Vuc3VzIG9uIE9TUEYuCiZuYnNwO0kg
aGF2ZW4ndCBwb3N0ZWQgYSBkcmFmdCBvbiBSSVBuZywgYmVjYXVzZSBpdCB3b3VsZCBqdXN0IHdv
cmsgdGhlIHdheQppdCdzIGRlc2lnbmVkLjxicj4KICAgIDxicj4KQSBmZXcgcGVvcGxlIHNhaWQg
Jm5ic3A7PGEgbW96LWRvLW5vdC1zZW5kPSJ0cnVlIiBocmVmPSJodHRwOi8vdG9vbHMuaWV0Zi5v
cmcvaHRtbC9kcmFmdC1ob3dhcmQtdXAtcGlvLTAwIiB0YXJnZXQ9Il9ibGFuayI+aHR0cDovL3Rv
b2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaG93YXJkLXVwLXBpby0wMDwvYT4KaXMgbm8gYmV0dGVy
IHRoYW4gUklQLCBhbmQgd2UgYWxyZWFkeSBoYXZlIFJJUCBpbiBob21lIGdhdGV3YXlzLiAmbmJz
cDtDYW4KYW55IGdhdGV3YXkgdmVuZG9yIGNvbmZpcm0gd2hldGhlciBSSVBuZyBpcyBhbHJlYWR5
IGluIGdhdGV3YXlzPzxicj4KICAgIDxicj4KUHJvcG9zZWQgYWx0ZXJuYXRpdmVzIGFyZTo8YnI+
CiogT1NQRnYzLiAmbmJzcDtJdCdzIGhlYXZ5d2VpZ2h0IGZvciBob21lIHJvdXRpbmcuICZuYnNw
O1dlIHN0aWxsIG5lZWQgYSB3YXkgdG8KZmluZCB0aGUgYm9yZGVyIGFuZCBpbmplY3QgZGVmYXVs
dC4gJm5ic3A7SXQgY291bGQgYmUgdXNlZCBmb3IgREhDUC1QRC48L2Jsb2NrcXVvdGU+CiAgPGRp
dj48YnI+CiAgPC9kaXY+CiAgPGRpdj5JIGRvbid0IHVuZGVyc3RhbmQgdGhhdDogYSBib3JkZXIg
Z2F0ZXdheSBpcyBhIHNwZWNpZmljIGRldmljZS48L2Rpdj4KICA8ZGl2PiZuYnNwOzwvZGl2Pgog
IDxibG9ja3F1b3RlIGNsYXNzPSJnbWFpbF9xdW90ZSIgc3R5bGU9ImJvcmRlci1sZWZ0OiAxcHgg
c29saWQgcmdiKDIwNCwgMjA0LCAyMDQpOyBtYXJnaW46IDBwdCAwcHQgMHB0IDAuOGV4OyBwYWRk
aW5nLWxlZnQ6IDFleDsiPi0tJm5ic3A7PC9ibG9ja3F1b3RlPgogIDwvZGl2PgpMYXVyZW50IFRv
dXRhaW48YnI+CiAgPGZvbnQgZmFjZT0iJ2NvdXJpZXIgbmV3JywgbW9ub3NwYWNlIj4rLS0tIFZv
SVAgKHJlY29tbWVuZGVkKQotLS0rLS0tLS0tLS0tLS0gVMOpbMOpY29tIEJyZXRhZ25lIC0tLS0t
LS0tLS0tKzxicj4KfCBUZWw6ICszMyAyIDIyIDA2IDgxNTYgJm5ic3A7ICZuYnNwO3wgVGVsOiAr
IDMzIDIgOTkgMTIgNzAyNiAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNw
OyAmbmJzcDsgJm5ic3A7IHwKVmlzaXQgOjxicj4KfCBGYXg6ICszMyAyIDIyIDA2IDg0NDUgJm5i
c3A7ICZuYnNwO3wgRmF4OiArMzMgMiA5OSAxMiA3MDMwICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZu
YnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7fCAmbmJzcDs8YSBtb3otZG8t
bm90LXNlbmQ9InRydWUiIGhyZWY9Imh0dHA6Ly9jbGFzcy50b3V0YS5pbi8iIHRhcmdldD0iX2Js
YW5rIj5odHRwOi8vY2xhc3MudG91dGEuaW48L2E+PGJyPgp8IDxhIGNsYXNzPSJtb3otdHh0LWxp
bmstYWJicmV2aWF0ZWQiIGhyZWY9Im1haWx0bzpMYXVyZW50QFRvdXRhLmluIj5MYXVyZW50QFRv
dXRhLmluPC9hPiAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgfCA8YSBjbGFzcz0ibW96LXR4
dC1saW5rLWFiYnJldmlhdGVkIiBocmVmPSJtYWlsdG86TGF1cmVudC5Ub3V0YWluQFRlbGVjb20t
QnJldGFnbmUuZXUiPkxhdXJlbnQuVG91dGFpbkBUZWxlY29tLUJyZXRhZ25lLmV1PC9hPiAmbmJz
cDsgJm5ic3A7fDxicj4KKy0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tKy0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0rPC9mb250PjwvYmxvY2txdW90ZT4KCiA8L2JvZHk+

----_com.android.email_9737392166021--



From acee.lindem@ericsson.com  Wed Nov 23 03:02:10 2011
Return-Path: <acee.lindem@ericsson.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D5FE21F8C12 for <homenet@ietfa.amsl.com>; Wed, 23 Nov 2011 03:02:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.539
X-Spam-Level: 
X-Spam-Status: No, score=-6.539 tagged_above=-999 required=5 tests=[AWL=0.060,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mmqySkuya7Td for <homenet@ietfa.amsl.com>; Wed, 23 Nov 2011 03:02:09 -0800 (PST)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by ietfa.amsl.com (Postfix) with ESMTP id 34D5021F8C0F for <homenet@ietf.org>; Wed, 23 Nov 2011 03:02:09 -0800 (PST)
Received: from eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id pANB24dQ030937 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 23 Nov 2011 05:02:05 -0600
Received: from EUSAACMS0702.eamcs.ericsson.se ([169.254.1.25]) by eusaamw0711.eamcs.ericsson.se ([147.117.20.178]) with mapi; Wed, 23 Nov 2011 06:02:04 -0500
From: Acee Lindem <acee.lindem@ericsson.com>
To: Randy Turner <rturner@amalfisystems.com>
Date: Wed, 23 Nov 2011 06:02:01 -0500
Thread-Topic: [homenet] other routing options
Thread-Index: Acypz1S2H01oRmkmTSSA/OGo57rrCA==
Message-ID: <C8807FF6-1CB6-470A-BF9C-D8FC7E13E8E4@ericsson.com>
References: <DCC302FAA9FE5F4BBA4DCAD4656937791452BBC0CC@PRVPEXVS03.corp.twcable.com> <A7A4DFCE-C09D-49F7-A772-B3FC5F575CA1@amalfisystems.com> <35ABFE5A-789F-4268-812F-BCA00ACC388F@cisco.com> <4CD8F7DD-59C9-428F-A5C4-70FF6C35179B@amalfisystems.com> <96721D08-D39B-4753-9BFA-3AB5B7632E54@amalfisystems.com>
In-Reply-To: <96721D08-D39B-4753-9BFA-3AB5B7632E54@amalfisystems.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/signed; boundary="Apple-Mail-17-141538112"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
Cc: "Howard, Lee" <lee.howard@twcable.com>, "homenet@ietf.org" <homenet@ietf.org>, Fred Baker <fred@cisco.com>
Subject: Re: [homenet] other routing options
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 23 Nov 2011 11:02:10 -0000

--Apple-Mail-17-141538112
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On Nov 23, 2011, at 2:29 AM, Randy Turner wrote:

>=20
> On the point of autoconfig=85in future references to OSPF, can I =
substitute zOSPF ?  I'm assuming that we're not talking about deploying =
an off-the-shelf OSPF implementation because of the configuration impact =
on a home network consumer.  So I was also assuming that I could =
substitute zOSPF anytime someone mentions OSPF.

My feeling is that we can continue to call it OSPFv3 with the =
understanding that OSPFv3 can be optionally auto-configuring.=20

Thanks,
Acee=20


>=20
> R.
>=20
> On Nov 22, 2011, at 11:10 PM, Randy Turner wrote:
>=20
>>=20
>> So we either bite off much more than we need and get the flexibility =
of link-state (OSPF), or we add "bounds" to a Bellman-Ford =
implementation to constrain the count-to-infinity problem, and say that =
the increased convergence time is ok given that this potential event is =
unlikely to happen, or that the mean-time between these types of =
"link-down" events can absorb an increased convergence time.
>>=20
>> I do prefer link-state over DV...I'm just trying to look at =
alternatives :)
>>=20
>> We still have the ongoing discussion of how to make all this =
auto-configurable...
>>=20
>> R.
>>=20
>> On Nov 22, 2011, at 10:45 PM, Fred Baker wrote:
>>=20
>>>=20
>>> On Nov 22, 2011, at 2:49 PM, Randy Turner wrote:
>>>=20
>>>> That's how I felt until incredibly elaborate home net topologies =
were suggested -- but it still seems intuitively heavyweight for a =
"home" network.  If we do end up using OSPF, then maybe home networks =
are *not* simple as one would think, but rather a different =
instantiation of a complex routing scenario, just with "zeroconf" =
requirements.
>>>=20
>>> well, halfway in between. If you have a wired LAN and a wireless LAN =
with two wired/wireless routers, I suspect you have a routing topology =
with at least one redundant path. I don't care how many nodes you have; =
if you have a tree, it is "simple" for any protocol. If you have =
not-all-that-many nodes but have redundancy in the topology, you have =
the possibility of count-to-infinity problems with a bellman-ford =
protocol like RIPng. I would suspect that a home network is small =
compared to, say, a campus in an enterprise network, but if it has =
redundancy it has at least some probability of the same class of issues.
>>> _______________________________________________
>>> 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
>>=20
>=20
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet


--Apple-Mail-17-141538112
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIM8jCCBDQw
ggMcoAMCAQICECFWwVQHDV12M/Sr0yNv0sYwDQYJKoZIhvcNAQEFBQAwOTERMA8GA1UECgwIRXJp
Y3Nzb24xJDAiBgNVBAMMG0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMTAeFw0xMDEwMDEyMDA0
NTlaFw0xMzEwMDEyMDA0NDhaMG8xETAPBgNVBAoMCEVyaWNzc29uMR8wHQYDVQQDDBZBY2VlIExp
bmRlbSBMaW5kZW0gSUlJMRAwDgYDVQQFEwdlYWxmbGluMScwJQYJKoZIhvcNAQkBFhhhY2VlLmxp
bmRlbUBlcmljc3Nvbi5jb20wgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAI/Dc9ALiZuBMyuv
bsc3eBxjXZpMi45Z0vzsUQZTJGTBeY7p9JsdzXC9J1uMisBxYVi39R3KJo6I4hXVp9wrA1rxh4AE
bnP1+Gxfpj33uWEFYbBnVAJkIWYWF7CYTn8Zm/yd13vPXtuGA6ESeLnnJafwC9Y0YwUQ+4HX7PNv
uauVAgMBAAGjggGEMIIBgDCBwAYDVR0fBIG4MIG1MIGyoIGvoIGshjdodHRwOi8vY3JsLnRydXN0
LnRlbGlhLmNvbS9Fcmljc3Nvbk5MSW5kaXZpZHVhbENBMDEuY3JshnFsZGFwOi8vbGRhcC50cnVz
dC50ZWxpYS5jb20vY249RXJpY3Nzb24lMjBOTCUyMEluZGl2aWR1YWwlMjBDQTAxLG89RXJpY3Nz
b24/Y2VydGlmaWNhdGVyZXZvY2F0aW9ubGlzdDtiaW5hcnk/YmFzZTAjBgNVHREEHDAagRhhY2Vl
LmxpbmRlbUBlcmljc3Nvbi5jb20wRgYDVR0gBD8wPTA7BgYqhXBrAQEwMTAvBggrBgEFBQcCARYj
aHR0cDovL3d3dy5lcmljc3Nvbi5jb20vbGVnYWwuc2h0bWwwHQYDVR0OBBYEFAgOzAPuplmPr7C1
BTqV94OyqUdhMB8GA1UdIwQYMBaAFJYnw7jepV9dRD45UuVFsXZfYzCbMA4GA1UdDwEB/wQEAwIF
oDANBgkqhkiG9w0BAQUFAAOCAQEAE1gyNW6c2t/YsLxW5sm67+gVGK0Lnge4ub+k8dgGrK7Mj7em
nkOIFkjdv/tqdJ/SoUy/WEkBXba2TfpZ+lfluMgLYux1vSvqBUxYBsUHeNth2Q/Y6A9sCaDTBPlK
vZ2jLz814NavrVfgTCLdxX6zNtGdwzhviz+FyqyxYF43Q86RP8Gd/Npaz1W8pmYAHm0+lezuTx5k
F3Av3+SaZ/MR6s+RWuXEIdED36ajeQz+OG8Mh3nplofzdrOeoWGDz53YlfRhgj+TXo+H1lclZAvD
WVaMMXPdb27h9Hngsq87dkCW9uAyv8DI993rdhqzlEgUyQIL32icAXfTmTYgoGPOwjCCBEUwggMt
oAMCAQICEBPJ6v/eJq2p3KTKI4GDR+MwDQYJKoZIhvcNAQEFBQAwRDEaMBgGA1UECgwRVGVsaWFT
b25lcmEgR3JvdXAxJjAkBgNVBAMMHVRlbGlhU29uZXJhIFB1YmxpYyBSb290IENBIHYxMB4XDTA2
MTAwNjEwMDA1M1oXDTE2MTAwMjA1MDQxN1owOTERMA8GA1UECgwIRXJpY3Nzb24xJDAiBgNVBAMM
G0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoC
ggEBALYQd+Q1HuuHxDyNGFlEPzCxuPPFO5W2xyr+nqCVnNJ4QYFe1HACqavqNLwUGIqIEyHv1rLn
fub9LBc7dQpRHjl/dggin0ONOFJ36nbGEbfHjLJz2BzOWvwl84Sc+Fx09IrDU/SZSWFSfhqTu3TT
39h79brHdRkdPBUgBYgsiFKriHI0TjP5G8628H27BDzqUpzGLSYWgt6/tpwuOH5lcfNfHWMcCYXR
lobv0Klu8lxG5amWqAnqrH6ECOyYJTRbHTsaTIZOHy9Qw/0eXPujKT7tU5xxSI2SdceJqzUbAz2o
FRQ6Px7/GydpM/Rl+qYoGPcauHUL1aSeVJZqDFqcIF0CAwEAAaOCATwwggE4MBIGA1UdEwEB/wQI
MAYBAf8CAQAwRgYDVR0gBD8wPTA7BgcqhXAjAgEBMDAwLgYIKwYBBQUHAgEWImh0dHBzOi8vcmVw
b3NpdG9yeS50cnVzdC50ZWxpYS5jb20wgYkGA1UdHwSBgTB/MH2ge6B5hndsZGFwOi8vbGRhcC50
cnVzdC50ZWxpYS5jb20vY249VGVsaWFTb25lcmElMjBQdWJsaWMlMjBSb290JTIwQ0ElMjB2MSxv
PVRlbGlhU29uZXJhJTIwR3JvdXA/YXV0aG9yaXR5cmV2b2NhdGlvbmxpc3Q/YmFzZTAOBgNVHQ8B
Af8EBAMCAQYwHQYDVR0OBBYEFJYnw7jepV9dRD45UuVFsXZfYzCbMB8GA1UdIwQYMBaAFEXb8I+4
GmKhqCMbY4g4o9vgGmLxMA0GCSqGSIb3DQEBBQUAA4IBAQB2AEoqQz+M3Ra9alkpn/YnwhXIv6tP
jhUvSuNs00Nhd0T9XhlIU3a65CaB/UKSqnayE0t7Q0Qq3r+x/GK3in/mik8i/PK2/q8HutzYFSzz
6Npztpo2JG7AEKOJPVaeebjng45m6vNC7RIfzU9sG2LBR/hewS8s6dFFn70w795xUwJBWZ67OzIK
XrIVVvHTOYpbWA+MESKAXwFhnVONrOTWlVwrMUi4HbiPWpOk+xQbgehCEi7mu3cXsaU1Xq3kMXui
NuC7VKoob8mFO9o9RT+dlirD2uRXwNpvCu3but6Kyhu0+nvy2iXGKjdlxlWTsdDyulXYz+OYCMZ9
lFWRzMIPMIIEbTCCA1WgAwIBAgIRAJywjASay5cieGNithuGWj0wDQYJKoZIhvcNAQEFBQAwOjEZ
MBcGA1UEChMQUlNBIFNlY3VyaXR5IEluYzEdMBsGA1UECxMUUlNBIFNlY3VyaXR5IDIwNDggVjMw
HhcNMDYxMDMxMjA0MjI3WhcNMTYxMTAxMTU0MjI1WjBEMRowGAYDVQQKDBFUZWxpYVNvbmVyYSBH
cm91cDEmMCQGA1UEAwwdVGVsaWFTb25lcmEgUHVibGljIFJvb3QgQ0EgdjEwggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQDKTxADapCAq3mplX4R4gNt+WZe5QKGnaVEQSyY7lICKF5DuVdW
PMLHDjzhw5IzDd860ZZx/0VrhGB3DmP4SDIWCKo2PxvY5NckdBWPWp/T2uaQdOAwgqHpN0pe1X7/
jel59WsWYXKGg/81Wth73ZK/geE7Gz9Pvj1LU6N4YhLMgooxKnCS+ZjB5icWAg+Qd1QpQhF46H1i
bp6LsBWDp56MPpg8F5X6y7MGVcKYLdnLOPs84uxRW9qs1kBopzQBj6s5SyVh8A+j5liDBjghXYpw
/+paGEdqHPeSFYxZKeJatmjEKLYlxcZWRKf436KvQA9jBhMEmytMNbGicR1mRH6tAgMBAAGjggFi
MIIBXjAfBgNVHSMEGDAWgBQHw1EwpKrpRa41JPr/JCwz0LGdjDAdBgNVHQ4EFgQURdvwj7gaYqGo
IxtjiDij2+AaYvEwEgYDVR0TAQH/BAgwBgEB/wIBBDCBhQYDVR0gBH4wfDA9BgkqhkiG9w0FBgEw
MDAuBggrBgEFBQcCARYiaHR0cHM6Ly9yZXBvc2l0b3J5LnRydXN0LnRlbGlhLmNvbTA7BgcqhXAj
AgEBMDAwLgYIKwYBBQUHAgEWImh0dHBzOi8vcmVwb3NpdG9yeS50cnVzdC50ZWxpYS5jb20wcAYD
VR0fBGkwZzBloGOgYYZfaHR0cDovL3d3dy5yc2FzZWN1cml0eS5jb20vcHJvZHVjdHMva2Vvbi9y
ZXBvc2l0b3J5L2NlcnRpZmljYXRlX3N0YXR1cy9SU0FfU2VjdXJpdHlfMjA0OF92My5DUkwwDgYD
VR0PAQH/BAQDAgEGMA0GCSqGSIb3DQEBBQUAA4IBAQAEXpos2CnIm7/872ytSrEHWZgvhOUEkUm2
5PWf/XkWko41TaL9vIS1S6AdWChNqWmnYiS7GfaIiDM9s1D6K7hidWBDOm46bNdM3ZwhMyDCfkDJ
SgeJ0w+7YmjvChu7gWqDZCsbtZ5gA1ixCTdDnuZB67JGSPGW6r73coraDP8diOpiQouMvM6bKuTP
BH/1poLccsUxsKgrQ23JC9LWCRb8cYHkZjXFH1K44TsIl5Lne2oT0JI3pwdA2v6jO4p/OLHntP+n
pjwPbedMPUZkDYCkd3LSxj8c3JTxtA8SlPCtIHE1hh65xihg1JRIliSphrqr9kbfwHdeVxPdOI5G
tDYPMYICEjCCAg4CAQEwTTA5MREwDwYDVQQKDAhFcmljc3NvbjEkMCIGA1UEAwwbRXJpY3Nzb24g
TkwgSW5kaXZpZHVhbCBDQTAxAhAhVsFUBw1ddjP0q9Mjb9LGMAkGBSsOAwIaBQCgggEbMBgGCSqG
SIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMTEyMzExMDIwMlowIwYJKoZI
hvcNAQkEMRYEFOjksA/yT7PgKS2MDAf/dGXBZ/GGMFwGCSsGAQQBgjcQBDFPME0wOTERMA8GA1UE
CgwIRXJpY3Nzb24xJDAiBgNVBAMMG0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMQIQIVbBVAcN
XXYz9KvTI2/SxjBeBgsqhkiG9w0BCRACCzFPoE0wOTERMA8GA1UECgwIRXJpY3Nzb24xJDAiBgNV
BAMMG0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMQIQIVbBVAcNXXYz9KvTI2/SxjANBgkqhkiG
9w0BAQEFAASBgBeBGSZDYCYXsAYA8bTGVQCqU+DMwOOgOqN32bsZxS3vtmxhPPxb1J7ZO2XGvSjY
PHgt+PmCxH4l6RSRMXrc3cEs2S05r5aVmJs73F6LqSVs2UlKz66HWwnNKMajpTdLthY81CmMkp1x
N2k/oS1A1JUkC2E/mg2X09zmlQfGMpPfAAAAAAAA

--Apple-Mail-17-141538112--

From mark@townsley.net  Wed Nov 23 03:18:21 2011
Return-Path: <mark@townsley.net>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B65C921F8A71 for <homenet@ietfa.amsl.com>; Wed, 23 Nov 2011 03:18:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.157
X-Spam-Level: 
X-Spam-Status: No, score=-3.157 tagged_above=-999 required=5 tests=[AWL=-0.158, BAYES_00=-2.599, J_CHICKENPOX_45=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FsK1GvVbDYCm for <homenet@ietfa.amsl.com>; Wed, 23 Nov 2011 03:18:21 -0800 (PST)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id E26A621F8A69 for <homenet@ietf.org>; Wed, 23 Nov 2011 03:18:20 -0800 (PST)
Received: by bkbzv15 with SMTP id zv15so1181945bkb.31 for <homenet@ietf.org>; Wed, 23 Nov 2011 03:18:20 -0800 (PST)
Received: by 10.205.127.77 with SMTP id gz13mr9501932bkc.76.1322047079854; Wed, 23 Nov 2011 03:17:59 -0800 (PST)
Received: from ams-townsley-8712.cisco.com (64-103-25-233.cisco.com. [64.103.25.233]) by mx.google.com with ESMTPS id o7sm12534118bkw.16.2011.11.23.03.17.58 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 23 Nov 2011 03:17:59 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
From: Mark Townsley <mark@townsley.net>
In-Reply-To: <9B12A77F-91FE-4FAC-B4F9-36E0639B9069@dlink.com.tw>
Date: Wed, 23 Nov 2011 12:17:56 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <BB8B2938-1F74-4794-88AA-297DB3AF1022@townsley.net>
References: <CAKD1Yr3Y=EO9siQkAuZd7LtqsOT_8GswWkPOoiJEhtvnULcytw@mail.gmail.com>, <DCC302FAA9FE5F4BBA4DCAD4656937791452BBC096@PRVPEXVS03.corp.twcable.com> <9B12A77F-91FE-4FAC-B4F9-36E0639B9069@dlink.com.tw>
To: "homenet@ietf.org Group" <homenet@ietf.org>
X-Mailer: Apple Mail (2.1084)
Subject: [homenet] Framing homenet borders and default policies
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 23 Nov 2011 11:18:21 -0000

I think I have said this before verbally, but I wanted to put some text =
around it. If folks agree on this framework, the target would be the =
homenet arch document for fleshing out.=20

First, I think we should keep "host to router" links out of scope. Of =
course we need hosts, but they are not our main concern in homenet. =
Hosts that become routers are, and all they have to do is turn on =
"Internet Connection Sharing" to do so. I'd expect these hosts to look =
exactly like a router on the wire.=20

So, scoped to "router-to-router links", let's define 3 different =
pairings we are concerned about:

1. "Local" router to router links within the homenet
2. "Internet" router to Internet Service Provider links
3. "Other Network" links to another network (guest, grid, neighbor, =
etc...)

Note that a router to router "link" may exist virtually *inside* a =
single router. A good example is the case of a home:guest connection on =
two separate SSIDs from the same home router.=20

In terms of what we define in Homenet, let's focus on #1, #2, and =
provide one solid example for #3 (guest) for others to replicate as =
needed. For example, SmartGrid could use our "guest" definition as a =
guideline, either reusing it entirely or providing their own "homenet to =
grid" profile if necessary.=20

Now, the border discovery problem begins to look like this:=20

When a device is connected, we have to discover whether it is a router =
or a host first. If it is a router, we need to discover whether it is =
"in the homenet" or "outside the homenet". If it is "outside the =
homenet" we have to discover whether it is an "ISP" link for the =
homenet, or "other network". For "other networks" we now need to know =
what kind of "other network" which suggests a registry (and that's why =
we have IANA) and a protocol extension (which is why we have a WG).  =
This is a pretty simple cascading flowchart, with each exit point  =
resulting in a default policy for our 5 (6 if we include =
troubleshooting) functional areas.=20

For the 3 base cases listed above (Local, Internet, Guest) If we can =
solidly answer the 5 (6) questions below, we've accomplished well what =
is within our scope:

1. Do we share or accept assigned prefixes over this link?
2. Do we share or accept routing information over this link?
3. Do we share or accept services information over this link?
4. Do we share or accept naming information over this link?
5. Do we allow application traffic to flow over this link? If so, do we =
apply a firewall function?
(6.) Do we allow troubleshooting protocols over this link (ping, =
traceroute - could be part of the FW question in #5)?

We might realize that for all 3 cases and any other case we could dream =
of, the answer for a given default profile question is the same. That's =
goodness. The reason the 5 questions are here is that they correspond to =
the 5 areas of scope we have some control over in homenet, and I think =
helps us to understand what it is we are defining when tackling a given =
area.=20

Comments?

- Mark



From dave.taht@gmail.com  Wed Nov 23 04:35:22 2011
Return-Path: <dave.taht@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E58721F8B9A for <homenet@ietfa.amsl.com>; Wed, 23 Nov 2011 04:35:22 -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=-2.599, J_CHICKENPOX_32=0.6, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hlU2+bMScb5X for <homenet@ietfa.amsl.com>; Wed, 23 Nov 2011 04:35:21 -0800 (PST)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 5181421F8B64 for <homenet@ietf.org>; Wed, 23 Nov 2011 04:35:21 -0800 (PST)
Received: by vcbfy13 with SMTP id fy13so1460132vcb.31 for <homenet@ietf.org>; Wed, 23 Nov 2011 04:35:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type; bh=0npoMPc+0SS92R3mxtVzFFdrrcaD9KZDrKr8amo5vzY=; b=MkOTug3SN7kDRmSauttQCR4J7ah+pu6hUSqeon6+yoQC24DjipSlAmC8R1TqpI2r3l SnBm2ZwxOs5VYAu8PurQk+U3zjTOSrZ3FarDp3Ej5aY+nlLdNTePs6VKuRQn2hoKsw+X 1b8lnb65L74SN+wJXpji6fTYe/zCSq1vf/52I=
Received: by 10.52.16.243 with SMTP id j19mr25220743vdd.109.1322051720490; Wed, 23 Nov 2011 04:35:20 -0800 (PST)
Received: from [132.227.127.166] ([132.227.127.166]) by mx.google.com with ESMTPS id hn2sm23674745vdb.14.2011.11.23.04.35.19 (version=SSLv3 cipher=OTHER); Wed, 23 Nov 2011 04:35:19 -0800 (PST)
Message-ID: <4ECCE885.4080102@gmail.com>
Date: Wed, 23 Nov 2011 13:35:17 +0100
From: =?ISO-8859-1?Q?David_T=E4ht?= <dave.taht@gmail.com>
Organization: Bufferbloat.net
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: homenet@ietf.org
References: <DCC302FAA9FE5F4BBA4DCAD4656937791452BBC0CC@PRVPEXVS03.corp.twcable.com> <F4205C7B-9C3E-438A-8E14-0B0CB656CC8F@cisco.com>
In-Reply-To: <F4205C7B-9C3E-438A-8E14-0B0CB656CC8F@cisco.com>
Content-Type: multipart/mixed; boundary="------------000006040705040102090502"
Subject: Re: [homenet] other routing options
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 23 Nov 2011 12:35:22 -0000

This is a multi-part message in MIME format.
--------------000006040705040102090502
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

On 11/23/2011 07:41 AM, Fred Baker wrote:
> On Nov 22, 2011, at 2:36 PM, Howard, Lee wrote:
>
>> Ray asked for people to post drafts for anything other than OSPF, because without an alternative, it will appear that we have consensus on OSPF.  I haven't posted a draft on RIPng, because it would just work the way it's designed.
I think people should go off and implement *something* in a dual stack 
home routing environment and report back on what happens.

> Makes sense to me.

I have mentioned my fondness for babel earlier in this thread. It's 'RIP 
on speed', and unlike rip doesn't have the counting to infinity 
problem... and does something unique and useful in addition to that, 
supporting mesh routing, which I think is rather important for 
wireless-mostly networks.

Regrettably I do not have time at present to submit a draft on this 
topic, as I'm too busy
actually making code work in cerowrt, fixing bufferbloat, etc. (I'm 
strongly encouraged, btw,
things like the newfangled "byte queue limits" patch and the QFQ queuing 
discipline may actually solve a great deal of the problems we are having 
in this space)

The choice of routing protocol is the least of my problems!

While I'm off on other topics, a version of NAT for ipv6 has been 
submitted to the linux networking mailing list...

Prefix delegation is of interest...

I have wide-dhcpv6 doing pd for example, and I note that the latest 
release candidate of dibbler looks pretty good as active development 
resumed about a year ago. As for how well that can integrate with 
anything else, is kind of unknown.

Does anyone actually have a home router running ospf over ipv6?

a couple more comments below. I'd like to make clear that I'm neutral - 
merely that ospf didn't do what I wanted when last I tried it.

olsr and batman do - except that the former requires two daemons at 
present to run and is weird on ipv6, and batman doesn't do ipv6, which 
reduces my own choices to... no, I'm not going to say it...


>
>> A few people said  http://tools.ietf.org/html/draft-howard-up-pio-00 is no better than RIP, and we already have RIP in home gateways.  Can any gateway vendor confirm whether RIPng is already in gateways?

RIP is not available for v6 in any home gateway I'm aware of. I could be 
out of date on that.
>>
>> Proposed alternatives are:
>> * OSPFv3.  It's heavyweight for home routing.  We still need a way to find the border and inject default.  It could be used for DHCP-PD.
it's a one liner for babel to pick up a default gateway injected by dhcp 
or dhcpv6.


>> * zOSPF.  It requires resurrecting work.  I don't how much work it needs, or how big the protocol is.
> The Internet Draft could be summarized as "Use OSPF, and<do this>  for subnet allocation". If you don't like OSPF, you don't like zOSPF.
>
>> * UP PIO.  It's new work, and requires work.  It's lightweight, and solves the border problem, but not addressing.
>> * RIPng.  It's fairly lightweight, and it exists.  It solves only the routing problem.
> To my way of thinking, as a default protocol for very small networks, you could do worse. I personally prefer OSPF, but I'm a snob :-)

And me, AHCP + babel...

>
>> * MANEMO.  It requires resurrecting work, is pretty lightweight, and solves addressing and border problems.
>>
>> If you argue that we should reuse existing protocols (per the architecture draft), your choices are OSPFv3 or RIPng.  I really don't like OSPFv3 in the home--it's too much protocol, though if someone can tell me about memory footprint, that would be helpful.

  An ipv6 capable home router needs a minimum of 32MB of ram and 16 MB 
of flash, at present. Inside of that are many other daemons that eat up 
over half that ram, and the rest is used for buffering.

It will be nearly impossible to find one that has less than 64MB in the 
fairly near future.

Home routers do not swap. However, when under memory pressure they can 
generally drop read only pages with high effectiveness...

You can dismember any of hundreds of home routers and see the various 
components in action. there are daemons for dhcp, dhcp serving, ntp, 
dns, ra announcements, and a web server, at minimum.

Any set of "inside the home" internal routing tables is likely to be so 
much smaller than the other required features in the device as to be not 
worth thinking about much.

Unless people are seriously considering running BGP on the home router...

... I can't think of any other modern protocol that will eat up more 
memory than (for example) the web server, or wireless management daemon, 
at least, not until we get around to routing thousands of in-home 
movement sensors, or something like that.

This assumption would require testing, of course. Particularly the sensors.


> If you're comparing to RIPng, "a lot more". It's a more complex program, and it not only stores a route table, it stores a link state database. I'd have to go look at something to say this definitively, but I've heard the phrase "order of magnitude" in discussions like these.
>
>> I also prefer draft-baker-homenet-prefix-assignment, so we don't need OSPF for addressing.
>> Any discussion?
>>
>> Lee
>>
>>
>> This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.
>> _______________________________________________
>> 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


-- 
Dave Täht


--------------000006040705040102090502
Content-Type: text/x-vcard; charset=utf-8;
 name="dave_taht.vcf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="dave_taht.vcf"

begin:vcard
fn;quoted-printable:Dave T=C3=A4ht
n;quoted-printable:T=C3=A4ht;Dave
email;internet:dave.taht@gmail.com
tel;home:1-239-829-5608
tel;cell:0638645374
x-mozilla-html:FALSE
version:2.1
end:vcard


--------------000006040705040102090502--

From lee.howard@twcable.com  Wed Nov 23 09:21:55 2011
Return-Path: <lee.howard@twcable.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D921D21F8B4F for <homenet@ietfa.amsl.com>; Wed, 23 Nov 2011 09:21:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.21
X-Spam-Level: 
X-Spam-Status: No, score=-1.21 tagged_above=-999 required=5 tests=[AWL=0.253,  BAYES_00=-2.599, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hSdEpfi2E4Lo for <homenet@ietfa.amsl.com>; Wed, 23 Nov 2011 09:21:55 -0800 (PST)
Received: from cdpipgw01.twcable.com (cdpipgw01.twcable.com [165.237.59.22]) by ietfa.amsl.com (Postfix) with ESMTP id D5AD321F8B4B for <homenet@ietf.org>; Wed, 23 Nov 2011 09:21:54 -0800 (PST)
X-SENDER-IP: 10.136.163.15
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.69,559,1315195200"; d="scan'208";a="301300034"
Received: from unknown (HELO PRVPEXHUB06.corp.twcable.com) ([10.136.163.15]) by cdpipgw01.twcable.com with ESMTP/TLS/RC4-MD5; 23 Nov 2011 12:17:09 -0500
Received: from PRVPEXVS03.corp.twcable.com ([10.136.163.26]) by PRVPEXHUB06.corp.twcable.com ([10.136.163.15]) with mapi; Wed, 23 Nov 2011 12:21:54 -0500
From: "Howard, Lee" <lee.howard@twcable.com>
To: Ray Hunter <v6ops@globis.net>, Laurent Toutain <Laurent.Toutain@telecom-bretagne.eu>
Date: Wed, 23 Nov 2011 12:21:52 -0500
Thread-Topic: [homenet] other routing options
Thread-Index: AcypupRYamvMt6neSriWati+HlqEmgASV7UQ
Message-ID: <DCC302FAA9FE5F4BBA4DCAD4656937791452BBC498@PRVPEXVS03.corp.twcable.com>
References: <DCC302FAA9FE5F4BBA4DCAD4656937791452BBC0CC@PRVPEXVS03.corp.twcable.com> <CABONVQbMsY6MF_8q44XqGmdOMS6Odn+CjBEttaEs9rhmknwRxg@mail.gmail.com> <4ECCAFC3.5060903@globis.net>
In-Reply-To: <4ECCAFC3.5060903@globis.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "homenet@ietf.org" <homenet@ietf.org>
Subject: Re: [homenet] other routing options
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 23 Nov 2011 17:21:56 -0000

> IMHO increasing use of (overlapping) (low power) wireless networks in Hom=
enet will only make
> count to infinity type problems more common, as marginal adjacencies come=
 and go.

You mean 6lowpan type networks?  I thought we had consensus to draw a circl=
e around them and
say, "put a device between that network and this."

> What about multicast support for streaming video to my iDevice as I walk =
from the lounge to
> the pool? AV will likely be a major homenet application. OSPF =3D> MOSPF?=
 IPng =3D> DVMRP?
> Or should that use unicast + mobile IPv6?

Streaming video !=3D multicast.  I don't think we've had any discussion of =
multicast, except in
the context of mDNS.  I don't need it in the home.  Do you?

Lee

This E-mail and any of its attachments may contain Time Warner Cable propri=
etary information, which is privileged, confidential, or subject to copyrig=
ht belonging to Time Warner Cable. This E-mail is intended solely for the u=
se of the individual or entity to which it is addressed. If you are not the=
 intended recipient of this E-mail, you are hereby notified that any dissem=
ination, distribution, copying, or action taken in relation to the contents=
 of and attachments to this E-mail is strictly prohibited and may be unlawf=
ul. If you have received this E-mail in error, please notify the sender imm=
ediately and permanently delete the original and any copy of this E-mail an=
d any printout.

From Ray.Bellis@nominet.org.uk  Wed Nov 23 09:24:12 2011
Return-Path: <Ray.Bellis@nominet.org.uk>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB87F21F8A6C for <homenet@ietfa.amsl.com>; Wed, 23 Nov 2011 09:24:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.42
X-Spam-Level: 
X-Spam-Status: No, score=-9.42 tagged_above=-999 required=5 tests=[AWL=1.179,  BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NxEtif7nABTe for <homenet@ietfa.amsl.com>; Wed, 23 Nov 2011 09:24:12 -0800 (PST)
Received: from mx4.nominet.org.uk (mail.nominet.org.uk [213.248.199.24]) by ietfa.amsl.com (Postfix) with ESMTP id CBC6821F8A67 for <homenet@ietf.org>; Wed, 23 Nov 2011 09:24:11 -0800 (PST)
DomainKey-Signature: s=main.dk.nominet.selector; d=nominet.org.uk; c=nofws; q=dns;  h=X-IronPort-AV: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:Content-Type: Content-ID:Content-Transfer-Encoding:MIME-Version; b=sm7XCi63IbauqaGFMq/tfiA8ZlhnzI3cEJ7FQIKN6I+hMV8tfXN+WTyB wsPciXQWRMG87k6t3lYpK5H7bmb9zn+XA/Ox2B8hrKEqqvmQKlGOPE/4P p4t5VRczkGzYlZY;
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nominet.org.uk; i=Ray.Bellis@nominet.org.uk; q=dns/txt; s=main.dkim.nominet.selector; t=1322069052; x=1353605052; h=from:sender:reply-to:subject:date:message-id:to:cc: mime-version:content-transfer-encoding:content-id: content-description:resent-date:resent-from:resent-sender: resent-to:resent-cc:resent-message-id:in-reply-to: references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:list-owner:list-archive; z=From:=20Ray=20Bellis=20<Ray.Bellis@nominet.org.uk> |Subject:=20Re:=20[homenet]=20other=20routing=20options |Date:=20Wed,=2023=20Nov=202011=2017:24:08=20+0000 |Message-ID:=20<3DC6D987-9EF8-4C6A-9F95-0F32D87B6358@nomi net.org.uk>|To:=20"Howard,=20Lee"=20<lee.howard@twcable.c om>|CC:=20"homenet@ietf.org"=20<homenet@ietf.org> |MIME-Version:=201.0|Content-Transfer-Encoding:=20quoted- printable|Content-ID:=20<0ccfbcf2-1a22-47d3-af22-b8a0190f 6475>|In-Reply-To:=20<DCC302FAA9FE5F4BBA4DCAD465693779145 2BBC498@PRVPEXVS03.corp.twcable.com>|References:=20<DCC30 2FAA9FE5F4BBA4DCAD4656937791452BBC0CC@PRVPEXVS03.corp.twc able.com>=0D=0A=20<CABONVQbMsY6MF_8q44XqGmdOMS6Odn+CjBEtt aEs9rhmknwRxg@mail.gmail.com>=0D=0A=20<4ECCAFC3.5060903@g lobis.net>=0D=0A=20<DCC302FAA9FE5F4BBA4DCAD4656937791452B BC498@PRVPEXVS03.corp.twcable.com>; bh=AkNtHWxs1gH7TUOUA8rv4O8u4KGpbBjKmTd4SUA6Rfk=; b=koN74oWFsJ9zeNjmqMEJLLs6zsU4462iRWLilvXepINDFb8GXfKkT35/ cLzAPjKkoiNPwqS/f0UoTsNlsYdNvvnfm5vrJbpSzLqN6XpcKTCmO0Drw b7yvukWOJk5/BUD;
X-IronPort-AV: E=Sophos;i="4.69,560,1315177200"; d="scan'208";a="29721778"
Received: from wds-exc2.okna.nominet.org.uk ([213.248.197.145]) by mx4.nominet.org.uk with ESMTP; 23 Nov 2011 17:24:10 +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%19]) with mapi; Wed, 23 Nov 2011 17:24:10 +0000
From: Ray Bellis <Ray.Bellis@nominet.org.uk>
To: "Howard, Lee" <lee.howard@twcable.com>
Thread-Topic: [homenet] other routing options
Thread-Index: AQHMqbKdAHYBdJzYf0uhS8NuPgHsBJW6IaeAgACTuwCAAACiAA==
Date: Wed, 23 Nov 2011 17:24:08 +0000
Message-ID: <3DC6D987-9EF8-4C6A-9F95-0F32D87B6358@nominet.org.uk>
References: <DCC302FAA9FE5F4BBA4DCAD4656937791452BBC0CC@PRVPEXVS03.corp.twcable.com> <CABONVQbMsY6MF_8q44XqGmdOMS6Odn+CjBEttaEs9rhmknwRxg@mail.gmail.com> <4ECCAFC3.5060903@globis.net> <DCC302FAA9FE5F4BBA4DCAD4656937791452BBC498@PRVPEXVS03.corp.twcable.com>
In-Reply-To: <DCC302FAA9FE5F4BBA4DCAD4656937791452BBC498@PRVPEXVS03.corp.twcable.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-ID: <0ccfbcf2-1a22-47d3-af22-b8a0190f6475>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "homenet@ietf.org" <homenet@ietf.org>
Subject: Re: [homenet] other routing options
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 23 Nov 2011 17:24:12 -0000

On 23 Nov 2011, at 17:21, Howard, Lee wrote:

> You mean 6lowpan type networks?  I thought we had consensus to draw a cir=
cle around them and say, "put a device between that network and this."


That was certainly the room consensus at the Interim and will hopefully be =
reflected in the architecture draft.

Ray



From rturner@amalfisystems.com  Wed Nov 23 09:52:48 2011
Return-Path: <rturner@amalfisystems.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF05F11E8099 for <homenet@ietfa.amsl.com>; Wed, 23 Nov 2011 09:52:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.377
X-Spam-Level: 
X-Spam-Status: No, score=-2.377 tagged_above=-999 required=5 tests=[AWL=0.222,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id giulqcVkyMOe for <homenet@ietfa.amsl.com>; Wed, 23 Nov 2011 09:52:48 -0800 (PST)
Received: from omr7.networksolutionsemail.com (omr7.networksolutionsemail.com [205.178.146.57]) by ietfa.amsl.com (Postfix) with ESMTP id 795A011E8086 for <homenet@ietf.org>; Wed, 23 Nov 2011 09:52:45 -0800 (PST)
Received: from cm-omr7 (mail.networksolutionsemail.com [205.178.146.50]) by omr7.networksolutionsemail.com (8.13.8/8.13.8) with ESMTP id pANHqfkg010822 for <homenet@ietf.org>; Wed, 23 Nov 2011 12:52:43 -0500
X-Authenticated-IP: 98.151.18.158
Received: from [98.151.18.158] ([98.151.18.158:58487] helo=[192.168.1.105]) by cm-omr7 (envelope-from <rturner@amalfisystems.com>) (ecelerity 2.2.2.41 r(31179/31189)) with ESMTP id 20/E2-04871-9E23DCE4; Wed, 23 Nov 2011 12:52:41 -0500
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Randy Turner <rturner@amalfisystems.com>
In-Reply-To: <DCC302FAA9FE5F4BBA4DCAD4656937791452BBC498@PRVPEXVS03.corp.twcable.com>
Date: Wed, 23 Nov 2011 09:52:40 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <3DEE32C6-E26A-42F5-9A89-D88F3767DECC@amalfisystems.com>
References: <DCC302FAA9FE5F4BBA4DCAD4656937791452BBC0CC@PRVPEXVS03.corp.twcable.com> <CABONVQbMsY6MF_8q44XqGmdOMS6Odn+CjBEttaEs9rhmknwRxg@mail.gmail.com> <4ECCAFC3.5060903@globis.net> <DCC302FAA9FE5F4BBA4DCAD4656937791452BBC498@PRVPEXVS03.corp.twcable.com>
To: "Howard, Lee" <lee.howard@twcable.com>
X-Mailer: Apple Mail (2.1084)
Cc: Ray Hunter <v6ops@globis.net>, Laurent Toutain <Laurent.Toutain@telecom-bretagne.eu>, "homenet@ietf.org" <homenet@ietf.org>
Subject: Re: [homenet] other routing options
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 23 Nov 2011 17:52:49 -0000

Apple, Sony, Samsung, et.al., will use DLNA and other types of =
mechanisms that rely on multicast for service (content) discovery on the =
home network. Once the streams actually "start", they are currently =
unicast, but even this will change very soon.

Randy

On Nov 23, 2011, at 9:21 AM, Howard, Lee wrote:

>> IMHO increasing use of (overlapping) (low power) wireless networks in =
Homenet will only make
>> count to infinity type problems more common, as marginal adjacencies =
come and go.
>=20
> You mean 6lowpan type networks?  I thought we had consensus to draw a =
circle around them and
> say, "put a device between that network and this."
>=20
>> What about multicast support for streaming video to my iDevice as I =
walk from the lounge to
>> the pool? AV will likely be a major homenet application. OSPF =3D> =
MOSPF? IPng =3D> DVMRP?
>> Or should that use unicast + mobile IPv6?
>=20
> Streaming video !=3D multicast.  I don't think we've had any =
discussion of multicast, except in
> the context of mDNS.  I don't need it in the home.  Do you?
>=20
> Lee
>=20
> This E-mail and any of its attachments may contain Time Warner Cable =
proprietary information, which is privileged, confidential, or subject =
to copyright belonging to Time Warner Cable. This E-mail is intended =
solely for the use of the individual or entity to which it is addressed. =
If you are not the intended recipient of this E-mail, you are hereby =
notified that any dissemination, distribution, copying, or action taken =
in relation to the contents of and attachments to this E-mail is =
strictly prohibited and may be unlawful. If you have received this =
E-mail in error, please notify the sender immediately and permanently =
delete the original and any copy of this E-mail and any printout.
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>=20


From v6ops@globis.net  Wed Nov 23 10:06:15 2011
Return-Path: <v6ops@globis.net>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4516011E80AE for <homenet@ietfa.amsl.com>; Wed, 23 Nov 2011 10:06:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.526
X-Spam-Level: 
X-Spam-Status: No, score=-2.526 tagged_above=-999 required=5 tests=[AWL=0.072,  BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hffgp0hfGqMN for <homenet@ietfa.amsl.com>; Wed, 23 Nov 2011 10:06:11 -0800 (PST)
Received: from globis01.globis.net (RayH-1-pt.tunnel.tserv11.ams1.ipv6.he.net [IPv6:2001:470:1f14:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id 74ADB21F8ADC for <homenet@ietf.org>; Wed, 23 Nov 2011 10:06:08 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id 0BEDF87007F; Wed, 23 Nov 2011 19:06:06 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at globis01.globis.net
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 5Fx9F6cB8ARc; Wed, 23 Nov 2011 19:06:01 +0100 (CET)
Received: from Rays-iMac.local (unknown [192.168.0.3]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPA id E799A870067; Wed, 23 Nov 2011 19:06:00 +0100 (CET)
Message-ID: <4ECD3608.5020502@globis.net>
Date: Wed, 23 Nov 2011 19:06:00 +0100
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox Express 1.0.1 (Macintosh/20100705)
MIME-Version: 1.0
To: "Howard, Lee" <lee.howard@twcable.com>
References: <DCC302FAA9FE5F4BBA4DCAD4656937791452BBC0CC@PRVPEXVS03.corp.twcable.com>	<CABONVQbMsY6MF_8q44XqGmdOMS6Odn+CjBEttaEs9rhmknwRxg@mail.gmail.com> <4ECCAFC3.5060903@globis.net> <DCC302FAA9FE5F4BBA4DCAD4656937791452BBC498@PRVPEXVS03.corp.twcable.com>
In-Reply-To: <DCC302FAA9FE5F4BBA4DCAD4656937791452BBC498@PRVPEXVS03.corp.twcable.com>
Content-Type: multipart/alternative; boundary="------------020904060709080306070703"
Cc: Laurent Toutain <Laurent.Toutain@telecom-bretagne.eu>, "homenet@ietf.org" <homenet@ietf.org>
Subject: Re: [homenet] other routing options
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 23 Nov 2011 18:06:15 -0000

This is a multi-part message in MIME format.
--------------020904060709080306070703
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

>
>> >  IMHO increasing use of (overlapping) (low power) wireless networks in Homenet will only make
>> >  count to infinity type problems more common, as marginal adjacencies come and go.
>>      
>
> You mean 6lowpan type networks?  I thought we had consensus to draw a circle around them and
> say, "put a device between that network and this."
>
>    
I agree on 6LoWPAN: it has a clear gateway router, it's own routing 
protocol, and should not be expected to provide an inter-Homenet link.

But you can still have various flavors of WiFi that could be acting as a 
(marginal) inter-router link, in parallel with copper.
What about those? Are they also stub networks that only service end 
nodes? How do you know? How do you avoid 2 routers forming an OSPF/RIPng 
adjacency if it's a single SSID just within wireless range of each 
other? That might be exactly what you want in some cases.
>> >  What about multicast support for streaming video to my iDevice as I walk from the lounge to
>> >  the pool? AV will likely be a major homenet application. OSPF =>  MOSPF? IPng =>  DVMRP?
>> >  Or should that use unicast + mobile IPv6?
>>      
>
> Streaming video != multicast.  I don't think we've had any discussion of multicast, except in
> the context of mDNS.  I don't need it in the home.  Do you?
>    
That was exactly my question. As a consumer I'd like video distributed 
around my home available to mobile devices: I don't really care how it's 
transported. The video may well arrive into the home via multicast over 
cable via DOCSIS. The set top box is in the living room but my TV is in 
the bedroom. Do we expect people to run the cable TV network to every 
room to separate set top boxes with their own decryption cards and keep 
this outside of Homenet? Do we expect AV manufacturers to always unicast 
video within the Homenet? e.g. if I want my camera with my own copyright 
content to play on a remote system? Or should we discuss whether the 
choice of unicast routing protocol has a knock on effect to multicast 
routing?

I'd like to keep things simple too, but I think it's an important 
scoping question to get clear consensus on.

regards,
RayH

--------------020904060709080306070703
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html; charset=ISO-8859-1"
 http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<blockquote type="cite">
  <div class="moz-text-plain" wrap="true" graphical-quote="true"
 style="font-size: 13px;" lang="x-western">
  <blockquote type="cite" style="color: rgb(0, 0, 0); display: block;">
    <pre wrap=""><span class="moz-txt-citetags">&gt; </span>IMHO increasing use of (overlapping) (low power) wireless networks in Homenet will only make
<span class="moz-txt-citetags">&gt; </span>count to infinity type problems more common, as marginal adjacencies come and go.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
You mean 6lowpan type networks?  I thought we had consensus to draw a circle around them and
say, "put a device between that network and this."

  </pre>
  </div>
</blockquote>
I agree on 6LoWPAN: it has a clear gateway router, it's own routing
protocol, and should not be expected to provide an inter-Homenet link.<br>
<br>
But you can still have various flavors of WiFi that could be acting as
a (marginal) inter-router link, in parallel with copper.<br>
What about those? Are they also stub networks that only service end
nodes? How do you know? How do you avoid 2 routers forming an
OSPF/RIPng adjacency if it's a single SSID just within wireless range
of each other? That might be exactly what you want in some cases.<br>
<blockquote type="cite">
  <div class="moz-text-plain" wrap="true" graphical-quote="true"
 style="font-size: 13px;" lang="x-western">
  <pre wrap=""></pre>
  <blockquote type="cite" style="color: rgb(0, 0, 0); display: block;">
    <pre wrap=""><span class="moz-txt-citetags">&gt; </span>What about multicast support for streaming video to my iDevice as I walk from the lounge to
<span class="moz-txt-citetags">&gt; </span>the pool? AV will likely be a major homenet application. OSPF =&gt; MOSPF? IPng =&gt; DVMRP?
<span class="moz-txt-citetags">&gt; </span>Or should that use unicast + mobile IPv6?
    </pre>
  </blockquote>
  <pre wrap=""><!---->
Streaming video != multicast.  I don't think we've had any discussion of multicast, except in
the context of mDNS.  I don't need it in the home.  Do you?
  </pre>
  </div>
</blockquote>
That was exactly my question. As a consumer I'd like video distributed
around my home available to mobile devices: I don't really care how
it's transported. The video may well arrive into the home via multicast
over cable via DOCSIS. The set top box is in the living room but my TV
is in the bedroom. Do we expect people to run the cable TV network to
every room to separate set top boxes with their own decryption cards
and keep this outside of Homenet? Do we expect AV manufacturers to
always unicast video within the Homenet? e.g. if I want my camera with
my own copyright content to play on a remote system? Or should we
discuss whether the choice of unicast routing protocol has a knock on
effect to multicast routing?<br>
<br>
I'd like to keep things simple too, but I think it's an important
scoping question to get clear consensus on.<br>
<br>
regards,<br>
RayH<br>
</body>
</html>

--------------020904060709080306070703--

From brian.e.carpenter@gmail.com  Wed Nov 23 12:39:33 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C75A11E808D for <homenet@ietfa.amsl.com>; Wed, 23 Nov 2011 12:39:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.246
X-Spam-Level: 
X-Spam-Status: No, score=-103.246 tagged_above=-999 required=5 tests=[AWL=-0.247, BAYES_00=-2.599, J_CHICKENPOX_45=0.6, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IssyFGpMzKz5 for <homenet@ietfa.amsl.com>; Wed, 23 Nov 2011 12:39:32 -0800 (PST)
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 60AF911E8082 for <homenet@ietf.org>; Wed, 23 Nov 2011 12:39:32 -0800 (PST)
Received: by vcbfy13 with SMTP id fy13so2064019vcb.31 for <homenet@ietf.org>; Wed, 23 Nov 2011 12:39:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=wyyOEAzFUblv5tGYRRSqzHihXWJQwvP/cCoxkSMt3fA=; b=ir/s9PY3rU7uUBPfU1YmWf+SFhZ8k/R5PT1NlgGwsAd4hH6R4xs9JsIsM9H+O88xWO uMPaWj/H3GQM12Ap+aoTo7Pa7o1S1O7RsNIP8inX+tgEOitMdehTrP5yw2VeqbEBbgFU LSUNuG7rnTwWbfhnCbxXOyjPgeVvKDT/KaxZ8=
Received: by 10.52.93.146 with SMTP id cu18mr27292704vdb.56.1322080771932; Wed, 23 Nov 2011 12:39:31 -0800 (PST)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz. [130.216.38.124]) by mx.google.com with ESMTPS id ir2sm7223894vdb.9.2011.11.23.12.39.28 (version=SSLv3 cipher=OTHER); Wed, 23 Nov 2011 12:39:30 -0800 (PST)
Message-ID: <4ECD59FD.5050703@gmail.com>
Date: Thu, 24 Nov 2011 09:39:25 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Mark Townsley <mark@townsley.net>
References: <CAKD1Yr3Y=EO9siQkAuZd7LtqsOT_8GswWkPOoiJEhtvnULcytw@mail.gmail.com>, <DCC302FAA9FE5F4BBA4DCAD4656937791452BBC096@PRVPEXVS03.corp.twcable.com>	<9B12A77F-91FE-4FAC-B4F9-36E0639B9069@dlink.com.tw> <BB8B2938-1F74-4794-88AA-297DB3AF1022@townsley.net>
In-Reply-To: <BB8B2938-1F74-4794-88AA-297DB3AF1022@townsley.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Framing homenet borders and default policies
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 23 Nov 2011 20:39:33 -0000

Mark,

> 3. "Other Network" links to another network (guest, grid, neighbor, etc...)

I find this category troubling. Either the other network is part of the Internet,
except that it isn't an ISP network (i.e. it is a peer that does not offer
transit), or it is part of the homenet (i.e. it is a stub within the homenet).
Thus a guest network (your friend who's living in your garage) is not in
the same category as your neighbour's peer network.

The considerations are totally different for the two cases. For example: in some
jurisdictions, the homenet operator might be legally liable for any activity
performed within a stub of the homenet, but not for activity performed within a
non-transit peer. So the approach to security would be completely different
in the two cases. In some sense the non-transit peers would be reached
by an EGP (even if we actually used a trditional IGP protocol).

Regards
   Brian

On 2011-11-24 00:17, Mark Townsley wrote:
> I think I have said this before verbally, but I wanted to put some text around it. If folks agree on this framework, the target would be the homenet arch document for fleshing out. 
> 
> First, I think we should keep "host to router" links out of scope. Of course we need hosts, but they are not our main concern in homenet. Hosts that become routers are, and all they have to do is turn on "Internet Connection Sharing" to do so. I'd expect these hosts to look exactly like a router on the wire. 
> 
> So, scoped to "router-to-router links", let's define 3 different pairings we are concerned about:
> 
> 1. "Local" router to router links within the homenet
> 2. "Internet" router to Internet Service Provider links
> 3. "Other Network" links to another network (guest, grid, neighbor, etc...)
> 
> Note that a router to router "link" may exist virtually *inside* a single router. A good example is the case of a home:guest connection on two separate SSIDs from the same home router. 
> 
> In terms of what we define in Homenet, let's focus on #1, #2, and provide one solid example for #3 (guest) for others to replicate as needed. For example, SmartGrid could use our "guest" definition as a guideline, either reusing it entirely or providing their own "homenet to grid" profile if necessary. 
> 
> Now, the border discovery problem begins to look like this: 
> 
> When a device is connected, we have to discover whether it is a router or a host first. If it is a router, we need to discover whether it is "in the homenet" or "outside the homenet". If it is "outside the homenet" we have to discover whether it is an "ISP" link for the homenet, or "other network". For "other networks" we now need to know what kind of "other network" which suggests a registry (and that's why we have IANA) and a protocol extension (which is why we have a WG).  This is a pretty simple cascading flowchart, with each exit point  resulting in a default policy for our 5 (6 if we include troubleshooting) functional areas. 
> 
> For the 3 base cases listed above (Local, Internet, Guest) If we can solidly answer the 5 (6) questions below, we've accomplished well what is within our scope:
> 
> 1. Do we share or accept assigned prefixes over this link?
> 2. Do we share or accept routing information over this link?
> 3. Do we share or accept services information over this link?
> 4. Do we share or accept naming information over this link?
> 5. Do we allow application traffic to flow over this link? If so, do we apply a firewall function?
> (6.) Do we allow troubleshooting protocols over this link (ping, traceroute - could be part of the FW question in #5)?
> 
> We might realize that for all 3 cases and any other case we could dream of, the answer for a given default profile question is the same. That's goodness. The reason the 5 questions are here is that they correspond to the 5 areas of scope we have some control over in homenet, and I think helps us to understand what it is we are defining when tackling a given area. 
> 
> Comments?
> 
> - Mark
> 
> 
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
> 

From mark@townsley.net  Wed Nov 23 15:27:48 2011
Return-Path: <mark@townsley.net>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F283D11E80AA for <homenet@ietfa.amsl.com>; Wed, 23 Nov 2011 15:27:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.142
X-Spam-Level: 
X-Spam-Status: No, score=-3.142 tagged_above=-999 required=5 tests=[AWL=-0.143, BAYES_00=-2.599, J_CHICKENPOX_45=0.6, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KNvYQyEdOuCx for <homenet@ietfa.amsl.com>; Wed, 23 Nov 2011 15:27:47 -0800 (PST)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id B9D6F11E808F for <homenet@ietf.org>; Wed, 23 Nov 2011 15:27:46 -0800 (PST)
Received: by wwp14 with SMTP id 14so461269wwp.13 for <homenet@ietf.org>; Wed, 23 Nov 2011 15:27:46 -0800 (PST)
Received: by 10.181.13.82 with SMTP id ew18mr26686539wid.16.1322090865495; Wed, 23 Nov 2011 15:27:45 -0800 (PST)
Received: from ams-townsley-8712.cisco.com (64-103-25-233.cisco.com. [64.103.25.233]) by mx.google.com with ESMTPS id v10sm8736881wiy.23.2011.11.23.15.27.43 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 23 Nov 2011 15:27:44 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Mark Townsley <mark@townsley.net>
In-Reply-To: <4ECD59FD.5050703@gmail.com>
Date: Thu, 24 Nov 2011 00:27:42 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <D7F399E7-18C5-4BA1-87F4-90B6851D61C7@townsley.net>
References: <CAKD1Yr3Y=EO9siQkAuZd7LtqsOT_8GswWkPOoiJEhtvnULcytw@mail.gmail.com>, <DCC302FAA9FE5F4BBA4DCAD4656937791452BBC096@PRVPEXVS03.corp.twcable.com>	<9B12A77F-91FE-4FAC-B4F9-36E0639B9069@dlink.com.tw> <BB8B2938-1F74-4794-88AA-297DB3AF1022@townsley.net> <4ECD59FD.5050703@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1084)
Cc: "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Framing homenet borders and default policies
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 23 Nov 2011 23:27:48 -0000

On Nov 23, 2011, at 9:39 PM, Brian E Carpenter wrote:

> Mark,
>=20
>> 3. "Other Network" links to another network (guest, grid, neighbor, =
etc...)
>=20
> I find this category troubling.

OK, let's see what we can do about that.=20

> Either the other network is part of the Internet,
> except that it isn't an ISP network (i.e. it is a peer that does not =
offer
> transit), or it is part of the homenet (i.e. it is a stub within the =
homenet).

I think this is mostly semantics. I'm describing this from the =
perspective of the homenet, and what I am trying to outline is that the =
"pairing" between any two routers leads to a default policy. That policy =
is either "these routers are part of the same homenet" and thus "share =
everything", or not. If not, it's either an Internet Service Provider =
link with an associated default policy, or a link to some "other =
network" for which we're only going to define what Guest means and leave =
the rest to others. The policy questions were worded in both  directions =
on purpose (sharing with others, accepting from others), so even if you =
describe the border associations from another point of view, you'll end =
up with the same policy questions to answer, just from a different =
relative perspective. Does this help?


> Thus a guest network (your friend who's living in your garage) is not =
in
> the same category as your neighbour's peer network.

I agree. That's why the "neighbor peer" would have to define what kind =
of default policy it would conform too. Same for your 6lowpan, etc. =
We'll tackle one, just to prove if it can be done or not. I'm suggesting =
it be "guest".=20

>=20
> The considerations are totally different for the two cases. For =
example: in some
> jurisdictions, the homenet operator might be legally liable for any =
activity
> performed within a stub of the homenet, but not for activity performed =
within a
> non-transit peer. So the approach to security would be completely =
different
> in the two cases. In some sense the non-transit peers would be reached
> by an EGP (even if we actually used a trditional IGP protocol).

Yes, those are the devilish details. My email was just a framework.=20

I'd hope that we could at least define the default policy for a retail =
homenet router. If that needed to be modified for sale in a certain =
country, or as equipment supplied by a certain ISP, so be it, but at =
least it would still hopefully be within the framework.

- Mark

>=20
> Regards
>   Brian
>=20
> On 2011-11-24 00:17, Mark Townsley wrote:
>> I think I have said this before verbally, but I wanted to put some =
text around it. If folks agree on this framework, the target would be =
the homenet arch document for fleshing out.=20
>>=20
>> First, I think we should keep "host to router" links out of scope. Of =
course we need hosts, but they are not our main concern in homenet. =
Hosts that become routers are, and all they have to do is turn on =
"Internet Connection Sharing" to do so. I'd expect these hosts to look =
exactly like a router on the wire.=20
>>=20
>> So, scoped to "router-to-router links", let's define 3 different =
pairings we are concerned about:
>>=20
>> 1. "Local" router to router links within the homenet
>> 2. "Internet" router to Internet Service Provider links
>> 3. "Other Network" links to another network (guest, grid, neighbor, =
etc...)
>>=20
>> Note that a router to router "link" may exist virtually *inside* a =
single router. A good example is the case of a home:guest connection on =
two separate SSIDs from the same home router.=20
>>=20
>> In terms of what we define in Homenet, let's focus on #1, #2, and =
provide one solid example for #3 (guest) for others to replicate as =
needed. For example, SmartGrid could use our "guest" definition as a =
guideline, either reusing it entirely or providing their own "homenet to =
grid" profile if necessary.=20
>>=20
>> Now, the border discovery problem begins to look like this:=20
>>=20
>> When a device is connected, we have to discover whether it is a =
router or a host first. If it is a router, we need to discover whether =
it is "in the homenet" or "outside the homenet". If it is "outside the =
homenet" we have to discover whether it is an "ISP" link for the =
homenet, or "other network". For "other networks" we now need to know =
what kind of "other network" which suggests a registry (and that's why =
we have IANA) and a protocol extension (which is why we have a WG).  =
This is a pretty simple cascading flowchart, with each exit point  =
resulting in a default policy for our 5 (6 if we include =
troubleshooting) functional areas.=20
>>=20
>> For the 3 base cases listed above (Local, Internet, Guest) If we can =
solidly answer the 5 (6) questions below, we've accomplished well what =
is within our scope:
>>=20
>> 1. Do we share or accept assigned prefixes over this link?
>> 2. Do we share or accept routing information over this link?
>> 3. Do we share or accept services information over this link?
>> 4. Do we share or accept naming information over this link?
>> 5. Do we allow application traffic to flow over this link? If so, do =
we apply a firewall function?
>> (6.) Do we allow troubleshooting protocols over this link (ping, =
traceroute - could be part of the FW question in #5)?
>>=20
>> We might realize that for all 3 cases and any other case we could =
dream of, the answer for a given default profile question is the same. =
That's goodness. The reason the 5 questions are here is that they =
correspond to the 5 areas of scope we have some control over in homenet, =
and I think helps us to understand what it is we are defining when =
tackling a given area.=20
>>=20
>> Comments?
>>=20
>> - Mark
>>=20
>>=20
>> _______________________________________________
>> homenet mailing list
>> homenet@ietf.org
>> https://www.ietf.org/mailman/listinfo/homenet
>>=20


From rturner@amalfisystems.com  Wed Nov 23 21:50:12 2011
Return-Path: <rturner@amalfisystems.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A1F021F84BC for <homenet@ietfa.amsl.com>; Wed, 23 Nov 2011 21:50:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.52
X-Spam-Level: 
X-Spam-Status: No, score=-2.52 tagged_above=-999 required=5 tests=[AWL=-0.078,  BAYES_00=-2.599, HTML_MESSAGE=0.001, SUBJECT_FUZZY_TION=0.156]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a+VTe+04pY40 for <homenet@ietfa.amsl.com>; Wed, 23 Nov 2011 21:50:12 -0800 (PST)
Received: from omr3.networksolutionsemail.com (omr3.networksolutionsemail.com [205.178.146.53]) by ietfa.amsl.com (Postfix) with ESMTP id 5BD1F21F8876 for <homenet@ietf.org>; Wed, 23 Nov 2011 21:50:11 -0800 (PST)
Received: from cm-omr8 (mail.networksolutionsemail.com [205.178.146.50]) by omr3.networksolutionsemail.com (8.13.6/8.13.6) with ESMTP id pAO5o3ex032155 for <homenet@ietf.org>; Thu, 24 Nov 2011 00:50:06 -0500
Authentication-Results: cm-omr8 smtp.user=rturner@amalfisystems.com; auth=pass (LOGIN)
X-Authenticated-UID: rturner@amalfisystems.com
Received: from [198.228.215.218] ([198.228.215.218:43695] helo=localhost) by cm-omr8 (envelope-from <rturner@amalfisystems.com>) (ecelerity 2.2.2.41 r(31179/31189)) with ESMTPA id A5/0B-04746-A0BDDCE4; Thu, 24 Nov 2011 00:50:03 -0500
Date: Wed, 23 Nov 2011 21:49:56 -0800
Message-ID: <4eca41jshv11sjybxjlem8wn.1322113796801@email.android.com>
Importance: normal
From: Randy Turner <rturner@amalfisystems.com>
To: mellon@fugue.com, lee.howard@twcable.com
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="--_com.android.email_5601223039223"
Cc: homenet@ietf.org, lorenzo@google.com
Subject: Re: [homenet] Creating a security association via physical link +	button
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Nov 2011 05:50:12 -0000

----_com.android.email_5601223039223
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64

ImhvdyBjaGVhcD8iCgppdCBkZXBlbmRzIC0tIHdoZXRoZXIgeW91J3JlIHRhbGtpbmcgYWJvdXQg
cmV0YWlsLCBvciB0aGUgYmFyZSBib25lcyBwcmljZXMgYmVpbmcgZGVtYW5kZWQgYnkgTlNQcyBm
cm9tIGJveCB2ZW5kb3JzIGFuZCB3aGV0aGVyIG9yIG5vdCB0aGVzZSBOU1BzIGhhdmUgYSBicm9h
ZCBhbmQgcG9wdWxhciBzdWl0ZSBvZiBob21lbmV0IHNlcnZpY2VzIHRvIGFsbG93IHN1YnNpZGl6
aW5nIHRoZSBib3hlcwoKVGhlIG92ZXJhbGwgcG9pbnQgaGVyZSBpcyB0aGF0IHRoZXNlIGJveGVz
IHByb2JhYmx5IGhhdmUgdG8gaGl0IHZlcnkgaW5leHBlbnNpdmUgcHJpY2UgcG9pbnRzLi4uZWFz
aWx5IHN1YiAkNTAgdG8gdGhlIE5TUHMKClIuCgotLS0tLS0tLSBPcmlnaW5hbCBtZXNzYWdlIC0t
LS0tLS0tClN1YmplY3Q6IFJlOiBbaG9tZW5ldF0gQ3JlYXRpbmcgYSBzZWN1cml0eSBhc3NvY2lh
dGlvbiB2aWEgcGh5c2ljYWwgbGluayArCWJ1dHRvbiAKRnJvbTogVGVkIExlbW9uIDxtZWxsb25A
ZnVndWUuY29tPiAKVG86ICJIb3dhcmQsIExlZSIgPGxlZS5ob3dhcmRAdHdjYWJsZS5jb20+IApD
QzogImhvbWVuZXRAaWV0Zi5vcmciIDxob21lbmV0QGlldGYub3JnPixMb3JlbnpvIENvbGl0dGkg
PGxvcmVuem9AZ29vZ2xlLmNvbT4gCgpPbiBOb3YgMjIsIDIwMTEsIGF0IDU6MTkgUE0sIEhvd2Fy
ZCwgTGVlIHdyb3RlOgpJIGRvbuKAmXQgd2FudCB0byBkbyBtZWNoYW5pY2FsIGVuZ2luZWVyaW5n
IGhlcmUuwqAgQW5kIGJ1dHRvbnMgYXJlIGV4cGVuc2l2ZS4KCkdyZWF0LCBsZXQncyBqdXN0IGRv
IGEgVVNCIHBvcnQgdGhlbiEgwqAgOikKClNlcmlvdXNseSwgaWYgeW91IG1ha2UgYSBkZXZpY2Ug
Y2hlYXAgZW5vdWdoLCBpdCBzaW1wbHkgd29uJ3QgYmUgYWJsZSB0byBkbyBob21lbmV0LiDCoCBU
aGUgcXVlc3Rpb24gaXMsIGhvdyBjaGVhcCBpcyB0aGF0PwoKCg==

----_com.android.email_5601223039223
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: base64

PGh0bWw+PGhlYWQ+PG1ldGEgaHR0cC1lcXVpdj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0
L2h0bWw7IGNoYXJzZXQ9VVRGLTgiPjwvaGVhZD48Ym9keT4iaG93IGNoZWFwPyI8ZGl2Pjxicj48
L2Rpdj48ZGl2Pml0IGRlcGVuZHMgLS0gd2hldGhlciB5b3UncmUgdGFsa2luZyBhYm91dCByZXRh
aWwsIG9yIHRoZSBiYXJlIGJvbmVzIHByaWNlcyBiZWluZyBkZW1hbmRlZCBieSBOU1BzIGZyb20g
Ym94IHZlbmRvcnMgYW5kIHdoZXRoZXIgb3Igbm90IHRoZXNlIE5TUHMgaGF2ZSBhIGJyb2FkIGFu
ZCBwb3B1bGFyIHN1aXRlIG9mIGhvbWVuZXQgc2VydmljZXMgdG8gYWxsb3cgc3Vic2lkaXppbmcg
dGhlIGJveGVzPC9kaXY+PGRpdj48YnI+PC9kaXY+PGRpdj5UaGUgb3ZlcmFsbCBwb2ludCBoZXJl
IGlzIHRoYXQgdGhlc2UgYm94ZXMgcHJvYmFibHkgaGF2ZSB0byBoaXQgdmVyeSBpbmV4cGVuc2l2
ZSBwcmljZSBwb2ludHMuLi5lYXNpbHkgc3ViICQ1MCB0byB0aGUgTlNQczwvZGl2PjxkaXY+PGJy
PjwvZGl2PjxkaXY+Ui48L2Rpdj48YnI+PGJyPjxicj4tLS0tLS0tLSBPcmlnaW5hbCBtZXNzYWdl
IC0tLS0tLS0tPGJyPlN1YmplY3Q6IFJlOiBbaG9tZW5ldF0gQ3JlYXRpbmcgYSBzZWN1cml0eSBh
c3NvY2lhdGlvbiB2aWEgcGh5c2ljYWwgbGluayArCWJ1dHRvbiA8YnI+RnJvbTogVGVkIExlbW9u
ICZsdDttZWxsb25AZnVndWUuY29tJmd0OyA8YnI+VG86ICJIb3dhcmQsIExlZSIgJmx0O2xlZS5o
b3dhcmRAdHdjYWJsZS5jb20mZ3Q7IDxicj5DQzogImhvbWVuZXRAaWV0Zi5vcmciICZsdDtob21l
bmV0QGlldGYub3JnJmd0OyxMb3JlbnpvIENvbGl0dGkgJmx0O2xvcmVuem9AZ29vZ2xlLmNvbSZn
dDsgPGJyPjxicj48YnI+PGRpdj48ZGl2Pk9uIE5vdiAyMiwgMjAxMSwgYXQgNToxOSBQTSwgSG93
YXJkLCBMZWUgd3JvdGU6PC9kaXY+PGJsb2NrcXVvdGUgdHlwZT0iY2l0ZSI+PHNwYW4gY2xhc3M9
IkFwcGxlLXN0eWxlLXNwYW4iIHN0eWxlPSJmb250LWZhbWlseTogSGVsdmV0aWNhOyAiPjxkaXYg
c3R5bGU9Im1hcmdpbi10b3A6IDBpbjsgbWFyZ2luLXJpZ2h0OiAwaW47IG1hcmdpbi1sZWZ0OiAw
aW47IG1hcmdpbi1ib3R0b206IDAuMDAwMXB0OyBmb250LXNpemU6IDEycHQ7IGZvbnQtZmFtaWx5
OiAnVGltZXMgTmV3IFJvbWFuJywgc2VyaWY7ICI+PHNwYW4gc3R5bGU9ImNvbG9yOiBibGFjazsg
Ij5JIGRvbuKAmXQgd2FudCB0byBkbyBtZWNoYW5pY2FsIGVuZ2luZWVyaW5nIGhlcmUuJm5ic3A7
IEFuZCBidXR0b25zIGFyZSBleHBlbnNpdmUuPC9zcGFuPjwvZGl2Pjwvc3Bhbj48L2Jsb2NrcXVv
dGU+PGJyPjwvZGl2PjxkaXY+R3JlYXQsIGxldCdzIGp1c3QgZG8gYSBVU0IgcG9ydCB0aGVuISAm
bmJzcDsgOik8L2Rpdj48ZGl2Pjxicj48L2Rpdj48ZGl2PlNlcmlvdXNseSwgaWYgeW91IG1ha2Ug
YSBkZXZpY2UgY2hlYXAgZW5vdWdoLCBpdCBzaW1wbHkgd29uJ3QgYmUgYWJsZSB0byBkbyBob21l
bmV0LiAmbmJzcDsgVGhlIHF1ZXN0aW9uIGlzLCBob3cgY2hlYXAgaXMgdGhhdD88L2Rpdj48ZGl2
Pjxicj48L2Rpdj48YnI+PC9ib2R5Pg==

----_com.android.email_5601223039223--



From pthubert@cisco.com  Wed Nov 23 23:32:45 2011
Return-Path: <pthubert@cisco.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C98D1F0C71 for <homenet@ietfa.amsl.com>; Wed, 23 Nov 2011 23:32:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.071
X-Spam-Level: 
X-Spam-Status: No, score=-9.071 tagged_above=-999 required=5 tests=[AWL=1.527,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7+XEt37ugG60 for <homenet@ietfa.amsl.com>; Wed, 23 Nov 2011 23:32:43 -0800 (PST)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id 7E8BC1F0C6A for <homenet@ietf.org>; Wed, 23 Nov 2011 23:32:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=pthubert@cisco.com; l=12048; q=dns/txt; s=iport; t=1322119962; x=1323329562; h=mime-version:subject:date:message-id:in-reply-to: references:from:to:cc; bh=r+WKaZfryEQGsX1FmAmCzWmEALN1NBH5bAV8JxPBZoA=; b=RkUA6KjEj2HLn1P/WCN8JzSnU8wvKyqVXB33sEB8h4oeJeI4ZO8pyf3a e107uAtelTx5t6maEc30QJQL2S7ITZqAhDU+Uy7AP5V1mL1wjQ6T0DJTO wLSVlnz4gO7GgI0Qb7lOrwxu+Nwpi/CxRO6JDjdHKAyBhgHbgw8N7Xy16 I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgAFACLyzU6Q/khR/2dsb2JhbABEgk2oJoEFgXIBAQEDARIBCREDSQULAgEIDgMEAQELBhcBBgFFCQgBAQQTCBqHY5YzAZ48iX9jBKZW
X-IronPort-AV: E=Sophos;i="4.69,563,1315180800"; d="scan'208,217";a="60354450"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-2.cisco.com with ESMTP; 24 Nov 2011 07:32:41 +0000
Received: from xbh-ams-101.cisco.com (xbh-ams-101.cisco.com [144.254.74.71]) by ams-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id pAO7WfmH023293; Thu, 24 Nov 2011 07:32:41 GMT
Received: from xmb-ams-108.cisco.com ([144.254.74.83]) by xbh-ams-101.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 24 Nov 2011 08:32:41 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CCAA7B.3F841DCB"
Date: Thu, 24 Nov 2011 08:31:29 +0100
Message-ID: <BDF2740C082F6942820D95BAEB9E1A846E5B05@XMB-AMS-108.cisco.com>
In-Reply-To: <4ECD3608.5020502@globis.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [homenet] other routing options
Thread-Index: AcyqCqLKY68gmLGvTrmKjj0O8kw1VwAaoL3w
References: <DCC302FAA9FE5F4BBA4DCAD4656937791452BBC0CC@PRVPEXVS03.corp.twcable.com>	<CABONVQbMsY6MF_8q44XqGmdOMS6Odn+CjBEttaEs9rhmknwRxg@mail.gmail.com><4ECCAFC3.5060903@globis.net><DCC302FAA9FE5F4BBA4DCAD4656937791452BBC498@PRVPEXVS03.corp.twcable.com> <4ECD3608.5020502@globis.net>
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: "Ray Hunter" <v6ops@globis.net>, "Howard, Lee" <lee.howard@twcable.com>
X-OriginalArrivalTime: 24 Nov 2011 07:32:41.0197 (UTC) FILETIME=[3F9EC1D0:01CCAA7B]
Cc: Laurent Toutain <Laurent.Toutain@telecom-bretagne.eu>, homenet@ietf.org
Subject: Re: [homenet] other routing options
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Nov 2011 07:32:45 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CCAA7B.3F841DCB
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

6LoWPAN is not that specific and if every home usage needs a special
gateway, we're designing against the end to end principle.

=20

Take the stereo / home theater. This is prone to become an ad hoc
network where infrared and cable connections will be replaced by various
flavors of 802.15, e.g. Bluetooth for RCA replacement, Zigbee for
infrared, and UWB for HDMI.=20

=20

RPL is designed to accommodate that. It can build multiple constrained
routing topologies within a same subnet. For instance one topology can
be rooted at the screen, and dedicated to video by constraining the
links to UWB. =20

=20

And a recent draft allows cascading topologies.

=20

Cheers,

=20

Pascal

=20

From: homenet-bounces@ietf.org [mailto:homenet-bounces@ietf.org] On
Behalf Of Ray Hunter
Sent: mercredi 23 novembre 2011 19:06
To: Howard, Lee
Cc: Laurent Toutain; homenet@ietf.org
Subject: Re: [homenet] other routing options

=20

		> IMHO increasing use of (overlapping) (low power)
wireless networks in Homenet will only make
		> count to infinity type problems more common, as
marginal adjacencies come and go.
		   =20

	=20
	You mean 6lowpan type networks?  I thought we had consensus to
draw a circle around them and
	say, "put a device between that network and this."
	=20
	 =20

I agree on 6LoWPAN: it has a clear gateway router, it's own routing
protocol, and should not be expected to provide an inter-Homenet link.

But you can still have various flavors of WiFi that could be acting as a
(marginal) inter-router link, in parallel with copper.
What about those? Are they also stub networks that only service end
nodes? How do you know? How do you avoid 2 routers forming an OSPF/RIPng
adjacency if it's a single SSID just within wireless range of each
other? That might be exactly what you want in some cases.



	> What about multicast support for streaming video to my iDevice
as I walk from the lounge to
	> the pool? AV will likely be a major homenet application. OSPF
=3D> MOSPF? IPng =3D> DVMRP?
	> Or should that use unicast + mobile IPv6?
	   =20

=20
Streaming video !=3D multicast.  I don't think we've had any discussion =
of
multicast, except in
the context of mDNS.  I don't need it in the home.  Do you?
 =20

That was exactly my question. As a consumer I'd like video distributed
around my home available to mobile devices: I don't really care how it's
transported. The video may well arrive into the home via multicast over
cable via DOCSIS. The set top box is in the living room but my TV is in
the bedroom. Do we expect people to run the cable TV network to every
room to separate set top boxes with their own decryption cards and keep
this outside of Homenet? Do we expect AV manufacturers to always unicast
video within the Homenet? e.g. if I want my camera with my own copyright
content to play on a remote system? Or should we discuss whether the
choice of unicast routing protocol has a knock on effect to multicast
routing?

I'd like to keep things simple too, but I think it's an important
scoping question to get clear consensus on.

regards,
RayH


------_=_NextPart_001_01CCAA7B.3F841DCB
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";
	color:black;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";
	color:black;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;
	color:black;}
span.moz-txt-citetags
	{mso-style-name:moz-txt-citetags;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body bgcolor=3Dwhite lang=3DFR =
link=3Dblue vlink=3Dpurple><div class=3DWordSection1><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>6LoWPAN is not that specific and if every home usage needs a special =
gateway, we&#8217;re designing against the end to end =
principle.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Take the stereo / home theater. This is prone to become an ad hoc =
network where infrared and cable connections will be replaced by various =
flavors of 802.15, e.g. Bluetooth for RCA replacement, Zigbee for =
infrared, and UWB for HDMI. <o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>RPL is designed to accommodate that. It can build multiple =
constrained routing topologies within a same subnet. For instance one =
topology can be rooted at the screen, and dedicated to video by =
constraining the links to UWB. &nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>And a recent draft allows cascading =
topologies.<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Cheers,<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'>Pascal<o:p></o:p></span></p></div><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div><div =
style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm =
0cm 0cm'><p class=3DMsoNormal><b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowt=
ext'>From:</span></b><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowt=
ext'> homenet-bounces@ietf.org [mailto:homenet-bounces@ietf.org] <b>On =
Behalf Of </b>Ray Hunter<br><b>Sent:</b> mercredi 23 novembre 2011 =
19:06<br><b>To:</b> Howard, Lee<br><b>Cc:</b> Laurent Toutain; =
homenet@ietf.org<br><b>Subject:</b> Re: [homenet] other routing =
options<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><div><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><pre><span =
class=3Dmoz-txt-citetags>&gt; </span>IMHO increasing use of =
(overlapping) (low power) wireless networks in Homenet will only =
make<o:p></o:p></pre><pre><span class=3Dmoz-txt-citetags>&gt; =
</span>count to infinity type problems more common, as marginal =
adjacencies come and go.<o:p></o:p></pre><pre>&nbsp;&nbsp;&nbsp; =
<o:p></o:p></pre></blockquote><pre><o:p>&nbsp;</o:p></pre><pre>You mean =
6lowpan type networks?&nbsp; I thought we had consensus to draw a circle =
around them and<o:p></o:p></pre><pre>say, &quot;put a device between =
that network and =
this.&quot;<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>&nbsp; =
<o:p></o:p></pre></div></blockquote><p class=3DMsoNormal>I agree on =
6LoWPAN: it has a clear gateway router, it's own routing protocol, and =
should not be expected to provide an inter-Homenet link.<br><br>But you =
can still have various flavors of WiFi that could be acting as a =
(marginal) inter-router link, in parallel with copper.<br>What about =
those? Are they also stub networks that only service end nodes? How do =
you know? How do you avoid 2 routers forming an OSPF/RIPng adjacency if =
it's a single SSID just within wireless range of each other? That might =
be exactly what you want in some =
cases.<br><br><o:p></o:p></p><div><blockquote =
style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><pre><span =
class=3Dmoz-txt-citetags>&gt; </span>What about multicast support for =
streaming video to my iDevice as I walk from the lounge =
to<o:p></o:p></pre><pre><span class=3Dmoz-txt-citetags>&gt; </span>the =
pool? AV will likely be a major homenet application. OSPF =3D&gt; MOSPF? =
IPng =3D&gt; DVMRP?<o:p></o:p></pre><pre><span =
class=3Dmoz-txt-citetags>&gt; </span>Or should that use unicast + mobile =
IPv6?<o:p></o:p></pre><pre>&nbsp;&nbsp;&nbsp; =
<o:p></o:p></pre></blockquote><pre><o:p>&nbsp;</o:p></pre><pre>Streaming =
video !=3D multicast.&nbsp; I don't think we've had any discussion of =
multicast, except in<o:p></o:p></pre><pre>the context of mDNS.&nbsp; I =
don't need it in the home.&nbsp; Do you?<o:p></o:p></pre><pre>&nbsp; =
<o:p></o:p></pre></div><p class=3DMsoNormal>That was exactly my =
question. As a consumer I'd like video distributed around my home =
available to mobile devices: I don't really care how it's transported. =
The video may well arrive into the home via multicast over cable via =
DOCSIS. The set top box is in the living room but my TV is in the =
bedroom. Do we expect people to run the cable TV network to every room =
to separate set top boxes with their own decryption cards and keep this =
outside of Homenet? Do we expect AV manufacturers to always unicast =
video within the Homenet? e.g. if I want my camera with my own copyright =
content to play on a remote system? Or should we discuss whether the =
choice of unicast routing protocol has a knock on effect to multicast =
routing?<br><br>I'd like to keep things simple too, but I think it's an =
important scoping question to get clear consensus =
on.<br><br>regards,<br>RayH<o:p></o:p></p></div></body></html>
------_=_NextPart_001_01CCAA7B.3F841DCB--

From Ray.Bellis@nominet.org.uk  Thu Nov 24 00:14:04 2011
Return-Path: <Ray.Bellis@nominet.org.uk>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2DA501F0C74 for <homenet@ietfa.amsl.com>; Thu, 24 Nov 2011 00:14:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.451
X-Spam-Level: 
X-Spam-Status: No, score=-9.451 tagged_above=-999 required=5 tests=[AWL=1.147,  BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FF0INx4j3PhN for <homenet@ietfa.amsl.com>; Thu, 24 Nov 2011 00:14:02 -0800 (PST)
Received: from mx4.nominet.org.uk (mx4.nominet.org.uk [213.248.199.24]) by ietfa.amsl.com (Postfix) with ESMTP id A3D501F0C72 for <homenet@ietf.org>; Thu, 24 Nov 2011 00:14:01 -0800 (PST)
DomainKey-Signature: s=main.dk.nominet.selector; d=nominet.org.uk; c=nofws; q=dns;  h=X-IronPort-AV: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:Content-Type: MIME-Version; b=mhLB6X3MsYTR32zrw7UiYtRIDLB/pCPNcuzfbDzuR/6LgCdSAiU8rm7V v4DadsVAoGWJ4KCexDY2mwk40fX2gL451fm2mh8kbLMxA3hmbR8S/Kh2c 0sfT2kV8mVauQW5;
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nominet.org.uk; i=Ray.Bellis@nominet.org.uk; q=dns/txt; s=main.dkim.nominet.selector; t=1322122441; x=1353658441; h=from:sender:reply-to:subject:date:message-id:to:cc: mime-version:content-transfer-encoding:content-id: content-description:resent-date:resent-from:resent-sender: resent-to:resent-cc:resent-message-id:in-reply-to: references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:list-owner:list-archive; z=From:=20Ray=20Bellis=20<Ray.Bellis@nominet.org.uk> |Subject:=20Re:=20[homenet]=20other=20routing=20options |Date:=20Thu,=2024=20Nov=202011=2008:13:58=20+0000 |Message-ID:=20<B16D09C6-66AA-4FCC-9A3A-5CB2C2921523@nomi net.org.uk>|To:=20"Pascal=20Thubert=20(pthubert)"=20<pthu bert@cisco.com>|CC:=20"homenet@ietf.org"=20<homenet@ietf. org>|MIME-Version:=201.0|In-Reply-To:=20<BDF2740C082F6942 820D95BAEB9E1A846E5B05@XMB-AMS-108.cisco.com>|References: =20<DCC302FAA9FE5F4BBA4DCAD4656937791452BBC0CC@PRVPEXVS03 .corp.twcable.com>=0D=0A=09<CABONVQbMsY6MF_8q44XqGmdOMS6O dn+CjBEttaEs9rhmknwRxg@mail.gmail.com><4ECCAFC3.5060903@g lobis.net><DCC302FAA9FE5F4BBA4DCAD4656937791452BBC498@PRV PEXVS03.corp.twcable.com>=0D=0A=20<4ECD3608.5020502@globi s.net>=0D=0A=20<BDF2740C082F6942820D95BAEB9E1A846E5B05@XM B-AMS-108.cisco.com>; bh=3oF2lu3t9HQtbBX5BVmc4aTTmIFMMZ83aEcBF/9S46Q=; b=jHvoZbQyHyfGf269/T0Idc2escufKUNqkp8AiUKNhtob3TAbSOSr1C3c M9xX9hicoU+h59RXNmhRmLkbJojp4cj7uq4rJ2fZOTwfTDsI8s9FCYATa Q8vIejczeoK4rax;
X-IronPort-AV: E=Sophos;i="4.69,564,1315177200"; d="scan'208,217";a="29724364"
Received: from wds-exc2.okna.nominet.org.uk ([213.248.197.145]) by mx4.nominet.org.uk with ESMTP; 24 Nov 2011 08:13:59 +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%19]) with mapi; Thu, 24 Nov 2011 08:13:58 +0000
From: Ray Bellis <Ray.Bellis@nominet.org.uk>
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
Thread-Topic: [homenet] other routing options
Thread-Index: AQHMqbKdAHYBdJzYf0uhS8NuPgHsBJW6IaeAgACTuwCAAAxVAIAA4QyAgAAL3wA=
Date: Thu, 24 Nov 2011 08:13:58 +0000
Message-ID: <B16D09C6-66AA-4FCC-9A3A-5CB2C2921523@nominet.org.uk>
References: <DCC302FAA9FE5F4BBA4DCAD4656937791452BBC0CC@PRVPEXVS03.corp.twcable.com> <CABONVQbMsY6MF_8q44XqGmdOMS6Odn+CjBEttaEs9rhmknwRxg@mail.gmail.com><4ECCAFC3.5060903@globis.net><DCC302FAA9FE5F4BBA4DCAD4656937791452BBC498@PRVPEXVS03.corp.twcable.com> <4ECD3608.5020502@globis.net> <BDF2740C082F6942820D95BAEB9E1A846E5B05@XMB-AMS-108.cisco.com>
In-Reply-To: <BDF2740C082F6942820D95BAEB9E1A846E5B05@XMB-AMS-108.cisco.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_B16D09C666AA4FCC9A3A5CB2C2921523nominetorguk_"
MIME-Version: 1.0
Cc: "homenet@ietf.org" <homenet@ietf.org>
Subject: Re: [homenet] other routing options
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Nov 2011 08:14:04 -0000

--_000_B16D09C666AA4FCC9A3A5CB2C2921523nominetorguk_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


On 24 Nov 2011, at 07:31, Pascal Thubert (pthubert) wrote:

RPL is designed to accommodate that.

Please see our message of 17th November.

If your favourite routing protocol is not being considered, please write a =
draft describing its applicability to Homenet.

thanks,

Ray


--_000_B16D09C666AA4FCC9A3A5CB2C2921523nominetorguk_
Content-Type: text/html; charset="us-ascii"
Content-ID: <790de0c4-271c-41b6-8bd9-f187ee0f6548>
Content-Transfer-Encoding: quoted-printable

<html><head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
><base href=3D"x-msg://29/"></head><body style=3D"word-wrap: break-word; -w=
ebkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><=
div>On 24 Nov 2011, at 07:31, Pascal Thubert (pthubert) wrote:</div><br cla=
ss=3D"Apple-interchange-newline"><blockquote type=3D"cite"><span class=3D"A=
pple-style-span" style=3D"color: rgb(31, 73, 125); font-family: Calibri, sa=
ns-serif; font-size: 15px; ">RPL is designed to accommodate that.</span></b=
lockquote><br></div><div>Please see our message of 17th November.</div><div=
><br></div><div>If your favourite routing protocol is not being considered,=
 please write a draft describing its applicability to Homenet.</div><div><b=
r></div><div>thanks,</div><div><br></div><div>Ray</div><div><br></div></bod=
y></html>=

--_000_B16D09C666AA4FCC9A3A5CB2C2921523nominetorguk_--

From lorenzo@google.com  Thu Nov 24 01:44:32 2011
Return-Path: <lorenzo@google.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 523C621F89BA for <homenet@ietfa.amsl.com>; Thu, 24 Nov 2011 01:44:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.844
X-Spam-Level: 
X-Spam-Status: No, score=-102.844 tagged_above=-999 required=5 tests=[AWL=-0.024, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, SUBJECT_FUZZY_TION=0.156, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3wrotTmKSGZV for <homenet@ietfa.amsl.com>; Thu, 24 Nov 2011 01:44:31 -0800 (PST)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id C7BC721F8B7D for <homenet@ietf.org>; Thu, 24 Nov 2011 01:44:31 -0800 (PST)
Received: by ghrr14 with SMTP id r14so2804394ghr.31 for <homenet@ietf.org>; Thu, 24 Nov 2011 01:44:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-system-of-record; bh=L+sn3tgDcdHtXCgkSj9AWLibwByMH7cEKB37RSPlyYc=; b=kHuLx+ioSv83zpzH5W1AUJpETVpNdOu/rVMtUzhnOgvAX+ysWdzQrzm7TlZKPWun5J G/OPsJWFCot46NoIsxpg==
Received: by 10.236.75.167 with SMTP id z27mr40475691yhd.53.1322127871372; Thu, 24 Nov 2011 01:44:31 -0800 (PST)
Received: by 10.236.75.167 with SMTP id z27mr40475666yhd.53.1322127871172; Thu, 24 Nov 2011 01:44:31 -0800 (PST)
MIME-Version: 1.0
Received: by 10.150.202.14 with HTTP; Thu, 24 Nov 2011 01:44:10 -0800 (PST)
In-Reply-To: <ACDC3C9F-85D2-4AF6-AA8C-2A2E6EEDC8EE@fugue.com>
References: <CAKD1Yr3Y=EO9siQkAuZd7LtqsOT_8GswWkPOoiJEhtvnULcytw@mail.gmail.com> <4ECB98BC.8070600@riw.us> <ACDC3C9F-85D2-4AF6-AA8C-2A2E6EEDC8EE@fugue.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 24 Nov 2011 18:44:10 +0900
Message-ID: <CAKD1Yr26zO0Dbco35ngWhj4W0hv_d_zJTCcbB-SSKqPpQab=ig@mail.gmail.com>
To: Ted Lemon <mellon@fugue.com>
Content-Type: multipart/alternative; boundary=20cf3005dde61bdf8104b277e2f3
X-System-Of-Record: true
Cc: Russ White <russw@riw.us>, homenet@ietf.org
Subject: Re: [homenet] Creating a security association via physical link + button
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Nov 2011 09:44:32 -0000

--20cf3005dde61bdf8104b277e2f3
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Nov 22, 2011 at 23:54, Ted Lemon <mellon@fugue.com> wrote:

> Yeah, I don't think either device decides that it is the homenet; rather,
> they are regularly dynamically discovering topology, and deciding what to
> do based on whether they are connected to an edge.   Possibly both devices
> are connected to an edge, and cooperate to do multihoming.
>

Let me rephrase my original question. You connect two routers and press the
button on both. What happens, and who gets the config from whom?

If one is a member of a homenet and an ISP connection already, and one has
a blank config, then you might assume that  the one with the blank config
should join the existing homenet. What if they both have a config on them?
What if you're actually merging two separate networks?

--20cf3005dde61bdf8104b277e2f3
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div class=3D"gmail_quote">On Tue, Nov 22, 2011 at 23:54, Ted Lemon <span d=
ir=3D"ltr">&lt;<a href=3D"mailto:mellon@fugue.com">mellon@fugue.com</a>&gt;=
</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .=
8ex;border-left:1px #ccc solid;padding-left:1ex;">

<div style=3D"word-wrap:break-word"><div>Yeah, I don&#39;t think either dev=
ice decides that it is the homenet; rather, they are regularly dynamically =
discovering topology, and deciding what to do based on whether they are con=
nected to an edge. =A0 Possibly both devices are connected to an edge, and =
cooperate to do multihoming.</div>

</div></blockquote><div><br></div><div>Let me rephrase my original question=
.=A0You connect two routers and press the button on both. What happens, and=
 who gets the config from whom?</div><div><br></div><div>If one is a member=
 of a homenet and an ISP connection already, and one has a blank config, th=
en you might assume that =A0the one with the blank config should join the e=
xisting homenet. What if they both have a config on them? What if you&#39;r=
e actually merging two separate networks?</div>

</div>

--20cf3005dde61bdf8104b277e2f3--

From mellon@fugue.com  Thu Nov 24 08:27:21 2011
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C69B21F8B4D for <homenet@ietfa.amsl.com>; Thu, 24 Nov 2011 08:27:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.988
X-Spam-Level: 
X-Spam-Status: No, score=-1.988 tagged_above=-999 required=5 tests=[AWL=0.454,  BAYES_00=-2.599, HTML_MESSAGE=0.001, SUBJECT_FUZZY_TION=0.156]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RGTLcFa7LAXY for <homenet@ietfa.amsl.com>; Thu, 24 Nov 2011 08:27:20 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 7BF1E21F8B48 for <homenet@ietf.org>; Thu, 24 Nov 2011 08:27:20 -0800 (PST)
Received: from [IPv6:2001:470:1f07:1486:25c7:9f16:4c39:9f38] (unknown [IPv6:2001:470:1f07:1486:25c7:9f16:4c39:9f38]) by toccata.fugue.com (Postfix) with ESMTPSA id B4E7D2381FB2; Thu, 24 Nov 2011 11:27:17 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: multipart/alternative; boundary="Apple-Mail=_21179358-AE1F-47AF-B54A-CA501D16DA99"
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <CAKD1Yr26zO0Dbco35ngWhj4W0hv_d_zJTCcbB-SSKqPpQab=ig@mail.gmail.com>
Date: Thu, 24 Nov 2011 11:27:16 -0500
Message-Id: <5C87A581-B2FD-4A1B-AD6B-7823279631BE@fugue.com>
References: <CAKD1Yr3Y=EO9siQkAuZd7LtqsOT_8GswWkPOoiJEhtvnULcytw@mail.gmail.com> <4ECB98BC.8070600@riw.us> <ACDC3C9F-85D2-4AF6-AA8C-2A2E6EEDC8EE@fugue.com> <CAKD1Yr26zO0Dbco35ngWhj4W0hv_d_zJTCcbB-SSKqPpQab=ig@mail.gmail.com>
To: Lorenzo Colitti <lorenzo@google.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: Russ White <russw@riw.us>, homenet@ietf.org
Subject: Re: [homenet] Creating a security association via physical link + button
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Nov 2011 16:27:21 -0000

--Apple-Mail=_21179358-AE1F-47AF-B54A-CA501D16DA99
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

On Nov 24, 2011, at 4:44 AM, Lorenzo Colitti wrote:
> If one is a member of a homenet and an ISP connection already, and one =
has a blank config, then you might assume that  the one with the blank =
config should join the existing homenet. What if they both have a config =
on them? What if you're actually merging two separate networks?

I think that's the idea.   The user is saying "merge the two networks" =
in this case.


--Apple-Mail=_21179358-AE1F-47AF-B54A-CA501D16DA99
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div>On Nov 24, 2011, at 4:44 AM, Lorenzo Colitti =
wrote:</div><blockquote type=3D"cite"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; font-family: Helvetica; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-align: -webkit-auto; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; ">If one is a =
member of a homenet and an ISP connection already, and one has a blank =
config, then you might assume that &nbsp;the one with the blank config =
should join the existing homenet. What if they both have a config on =
them? What if you're actually merging two separate =
networks?</span></blockquote></div><br><div>I think that's the idea. =
&nbsp; The user is saying "merge the two networks" in this =
case.</div><div><br></div></body></html>=

--Apple-Mail=_21179358-AE1F-47AF-B54A-CA501D16DA99--

From lorenzo@google.com  Thu Nov 24 16:47:17 2011
Return-Path: <lorenzo@google.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24B0C11E80A5 for <homenet@ietfa.amsl.com>; Thu, 24 Nov 2011 16:47:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.843
X-Spam-Level: 
X-Spam-Status: No, score=-102.843 tagged_above=-999 required=5 tests=[AWL=-0.023, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, SUBJECT_FUZZY_TION=0.156, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5hsKyoSFFv-v for <homenet@ietfa.amsl.com>; Thu, 24 Nov 2011 16:47:16 -0800 (PST)
Received: from mail-gx0-f172.google.com (mail-gx0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 9AC5211E809D for <homenet@ietf.org>; Thu, 24 Nov 2011 16:47:16 -0800 (PST)
Received: by ggnp4 with SMTP id p4so3669210ggn.31 for <homenet@ietf.org>; Thu, 24 Nov 2011 16:47:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-system-of-record; bh=zM0DamK/22yD8b5wG3N/9CNi4dnDxYB4kfFvnoRtMeg=; b=xaYM9KtNy0JDlzg+04uX/8zktfdhHlLLJKRLm2vNbLN8wJJ+kmCUHveI2TVyV0jZJ2 29XxwwKuoluOWF0en2Jw==
Received: by 10.236.183.52 with SMTP id p40mr44268999yhm.19.1322182036228; Thu, 24 Nov 2011 16:47:16 -0800 (PST)
Received: by 10.236.183.52 with SMTP id p40mr44268988yhm.19.1322182036121; Thu, 24 Nov 2011 16:47:16 -0800 (PST)
MIME-Version: 1.0
Received: by 10.150.202.14 with HTTP; Thu, 24 Nov 2011 16:46:56 -0800 (PST)
In-Reply-To: <5C87A581-B2FD-4A1B-AD6B-7823279631BE@fugue.com>
References: <CAKD1Yr3Y=EO9siQkAuZd7LtqsOT_8GswWkPOoiJEhtvnULcytw@mail.gmail.com> <4ECB98BC.8070600@riw.us> <ACDC3C9F-85D2-4AF6-AA8C-2A2E6EEDC8EE@fugue.com> <CAKD1Yr26zO0Dbco35ngWhj4W0hv_d_zJTCcbB-SSKqPpQab=ig@mail.gmail.com> <5C87A581-B2FD-4A1B-AD6B-7823279631BE@fugue.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Fri, 25 Nov 2011 09:46:56 +0900
Message-ID: <CAKD1Yr3zp1Gn1P-jDVgna2ViWeQiyCaTM=hTchpJq2snPSL-hw@mail.gmail.com>
To: Ted Lemon <mellon@fugue.com>
Content-Type: multipart/alternative; boundary=bcaec52c5ea997692104b2847ed6
X-System-Of-Record: true
Cc: Russ White <russw@riw.us>, homenet@ietf.org
Subject: Re: [homenet] Creating a security association via physical link + button
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 25 Nov 2011 00:47:17 -0000

--bcaec52c5ea997692104b2847ed6
Content-Type: text/plain; charset=ISO-8859-1

On Fri, Nov 25, 2011 at 01:27, Ted Lemon <mellon@fugue.com> wrote:

> If one is a member of a homenet and an ISP connection already, and one has
> a blank config, then you might assume that  the one with the blank config
> should join the existing homenet. What if they both have a config on them?
> What if you're actually merging two separate networks?
>
> I think that's the idea.   The user is saying "merge the two networks" in
> this case.
>

Ok, so it would seem to me that to support that case then we need to either
a) support multiple simultaneous keys in the IGP or b) provide a mechanism
to tell a number of homenet routers that "the key to the IGP is changing".
Both are non-trivial. Any other ideas?

--bcaec52c5ea997692104b2847ed6
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div class=3D"gmail_quote">On Fri, Nov 25, 2011 at 01:27, Ted Lemon <span d=
ir=3D"ltr">&lt;<a href=3D"mailto:mellon@fugue.com">mellon@fugue.com</a>&gt;=
</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .=
8ex;border-left:1px #ccc solid;padding-left:1ex;">

<div style=3D"word-wrap:break-word"><div class=3D"im"><div><blockquote type=
=3D"cite"><span style=3D"border-collapse:separate;font-family:Helvetica;fon=
t-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal=
;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:=
none;white-space:normal;word-spacing:0px;font-size:medium">If one is a memb=
er of a homenet and an ISP connection already, and one has a blank config, =
then you might assume that =A0the one with the blank config should join the=
 existing homenet. What if they both have a config on them? What if you&#39=
;re actually merging two separate networks?</span></blockquote>

</div></div><div>I think that&#39;s the idea. =A0 The user is saying &quot;=
merge the two networks&quot; in this case.</div></div></blockquote><div><br=
></div><div>Ok, so it would seem to me that to support that case then we ne=
ed to either a) support multiple simultaneous keys in the IGP or b) provide=
 a mechanism to tell a number of homenet routers that &quot;the key to the =
IGP is changing&quot;. Both are non-trivial. Any other ideas?</div>

</div>

--bcaec52c5ea997692104b2847ed6--

From mellon@fugue.com  Thu Nov 24 18:42:50 2011
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A7DA21F8B31 for <homenet@ietfa.amsl.com>; Thu, 24 Nov 2011 18:42:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.004
X-Spam-Level: 
X-Spam-Status: No, score=-2.004 tagged_above=-999 required=5 tests=[AWL=0.438,  BAYES_00=-2.599, HTML_MESSAGE=0.001, SUBJECT_FUZZY_TION=0.156]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7muGwJ1o8KrU for <homenet@ietfa.amsl.com>; Thu, 24 Nov 2011 18:42:50 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 0223321F8B2A for <homenet@ietf.org>; Thu, 24 Nov 2011 18:42:50 -0800 (PST)
Received: from [IPv6:2001:470:1f07:1486:d9d1:86ec:f45a:98f] (unknown [IPv6:2001:470:1f07:1486:d9d1:86ec:f45a:98f]) by toccata.fugue.com (Postfix) with ESMTPSA id 71D1723805B3; Thu, 24 Nov 2011 21:42:46 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: multipart/alternative; boundary="Apple-Mail=_FA351F88-12AF-41D5-8D4A-FCE25F7BE3C2"
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <CAKD1Yr3zp1Gn1P-jDVgna2ViWeQiyCaTM=hTchpJq2snPSL-hw@mail.gmail.com>
Date: Thu, 24 Nov 2011 21:42:41 -0500
Message-Id: <E70EE283-116C-49CD-854C-2DA20783FFD7@fugue.com>
References: <CAKD1Yr3Y=EO9siQkAuZd7LtqsOT_8GswWkPOoiJEhtvnULcytw@mail.gmail.com> <4ECB98BC.8070600@riw.us> <ACDC3C9F-85D2-4AF6-AA8C-2A2E6EEDC8EE@fugue.com> <CAKD1Yr26zO0Dbco35ngWhj4W0hv_d_zJTCcbB-SSKqPpQab=ig@mail.gmail.com> <5C87A581-B2FD-4A1B-AD6B-7823279631BE@fugue.com> <CAKD1Yr3zp1Gn1P-jDVgna2ViWeQiyCaTM=hTchpJq2snPSL-hw@mail.gmail.com>
To: Lorenzo Colitti <lorenzo@google.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: Russ White <russw@riw.us>, homenet@ietf.org
Subject: Re: [homenet] Creating a security association via physical link + button
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 25 Nov 2011 02:42:50 -0000

--Apple-Mail=_FA351F88-12AF-41D5-8D4A-FCE25F7BE3C2
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

On Nov 24, 2011, at 7:46 PM, Lorenzo Colitti wrote:
> Ok, so it would seem to me that to support that case then we need to =
either a) support multiple simultaneous keys in the IGP or b) provide a =
mechanism to tell a number of homenet routers that "the key to the IGP =
is changing". Both are non-trivial. Any other ideas?

I think a security model that doesn't have each router generating its =
own keys, and using public key cryptography, is doomed.   If you use a =
shared secret, it's too easy to pwn your network because it has to be =
exchanged in the clear.   If the IGP protocol we want doesn't support =
this, then it pretty much has to be fixed, or we just can't do this.


--Apple-Mail=_FA351F88-12AF-41D5-8D4A-FCE25F7BE3C2
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div>On Nov 24, 2011, at 7:46 PM, Lorenzo Colitti =
wrote:</div><blockquote type=3D"cite"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; font-family: Helvetica; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-align: -webkit-auto; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; ">Ok, so it =
would seem to me that to support that case then we need to either a) =
support multiple simultaneous keys in the IGP or b) provide a mechanism =
to tell a number of homenet routers that "the key to the IGP is =
changing". Both are non-trivial. Any other =
ideas?</span></blockquote></div><br><div>I think a security model that =
doesn't have each router generating its own keys, and using public key =
cryptography, is doomed. &nbsp; If you use a shared secret, it's too =
easy to pwn your network because it has to be exchanged in the clear. =
&nbsp; If the IGP protocol we want doesn't support this, then it pretty =
much has to be fixed, or we just can't do =
this.</div><div><br></div></body></html>=

--Apple-Mail=_FA351F88-12AF-41D5-8D4A-FCE25F7BE3C2--

From teco@inf-net.nl  Thu Nov 24 23:47:54 2011
Return-Path: <teco@inf-net.nl>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BFD121F8A58 for <homenet@ietfa.amsl.com>; Thu, 24 Nov 2011 23:47:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8k4OSVTyuIrE for <homenet@ietfa.amsl.com>; Thu, 24 Nov 2011 23:47:54 -0800 (PST)
Received: from mail-ww0-f44.google.com (mail-ww0-f44.google.com [74.125.82.44]) by ietfa.amsl.com (Postfix) with ESMTP id E247621F8A56 for <homenet@ietf.org>; Thu, 24 Nov 2011 23:47:53 -0800 (PST)
Received: by wwp14 with SMTP id 14so2441182wwp.13 for <homenet@ietf.org>; Thu, 24 Nov 2011 23:47:52 -0800 (PST)
Received: by 10.180.108.114 with SMTP id hj18mr33331409wib.2.1322207272471; Thu, 24 Nov 2011 23:47:52 -0800 (PST)
Received: from [10.175.173.2] (524A158D.cm-4-3a.dynamic.ziggo.nl. [82.74.21.141]) by mx.google.com with ESMTPS id hq5sm10367218wib.7.2011.11.24.23.47.50 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 24 Nov 2011 23:47:51 -0800 (PST)
From: Teco Boot <teco@inf-net.nl>
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: multipart/alternative; boundary="Apple-Mail=_6399CF27-9652-4275-A607-53B88C1D6605"
Date: Fri, 25 Nov 2011 08:47:51 +0100
In-Reply-To: <B16D09C6-66AA-4FCC-9A3A-5CB2C2921523@nominet.org.uk>
To: homenet@ietf.org
References: <DCC302FAA9FE5F4BBA4DCAD4656937791452BBC0CC@PRVPEXVS03.corp.twcable.com> <CABONVQbMsY6MF_8q44XqGmdOMS6Odn+CjBEttaEs9rhmknwRxg@mail.gmail.com><4ECCAFC3.5060903@globis.net><DCC302FAA9FE5F4BBA4DCAD4656937791452BBC498@PRVPEXVS03.corp.twcable.com> <4ECD3608.5020502@globis.net> <BDF2740C082F6942820D95BAEB9E1A846E5B05@XMB-AMS-108.cisco.com> <B16D09C6-66AA-4FCC-9A3A-5CB2C2921523@nominet.org.uk>
Message-Id: <5A35BCB0-B7B6-41FE-BA6E-2778D5D479AC@inf-net.nl>
X-Mailer: Apple Mail (2.1251.1)
Subject: Re: [homenet] other routing options
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 25 Nov 2011 07:47:54 -0000

--Apple-Mail=_6399CF27-9652-4275-A607-53B88C1D6605
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


Op 24 nov. 2011, om 09:13 heeft Ray Bellis het volgende geschreven:

>=20
> On 24 Nov 2011, at 07:31, Pascal Thubert (pthubert) wrote:
>=20
>> RPL is designed to accommodate that.
>=20
> Please see our message of 17th November.
>=20
> If your favourite routing protocol is not being considered, please =
write a draft describing its applicability to Homenet.

IS-IS is not my favorite. Also, I know almost nothing about TRILL. But I =
think these should be considered. Don't expect a draft from me.

Teco


>=20
> thanks,
>=20
> Ray
>=20
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet


--Apple-Mail=_6399CF27-9652-4275-A607-53B88C1D6605
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>Op 24 nov. 2011, om 09:13 heeft Ray Bellis het volgende =
geschreven:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite">
<meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dus-ascii"><base href=3D"x-msg://29/"><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><br><div><div>On 24 Nov 2011, at 07:31, Pascal =
Thubert (pthubert) wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"color: rgb(31, 73, 125); =
font-family: Calibri, sans-serif; font-size: 15px; ">RPL is designed to =
accommodate that.</span></blockquote><br></div><div>Please see our =
message of 17th November.</div><div><br></div><div>If your favourite =
routing protocol is not being considered, please write a draft =
describing its applicability to =
Homenet.</div></div></blockquote><div><br></div><div>IS-IS is not my =
favorite. Also, I know almost nothing about TRILL. But I think these =
should be considered. Don't expect a draft from =
me.</div><div><br></div><div>Teco</div><div><br></div><br><blockquote =
type=3D"cite"><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space; =
"><div><br></div><div>thanks,</div><div><br></div><div>Ray</div><div><br><=
/div></div>_______________________________________________<br>homenet =
mailing list<br><a =
href=3D"mailto:homenet@ietf.org">homenet@ietf.org</a><br>https://www.ietf.=
org/mailman/listinfo/homenet<br></blockquote></div><br></body></html>=

--Apple-Mail=_6399CF27-9652-4275-A607-53B88C1D6605--

From townsley@cisco.com  Fri Nov 25 00:44:01 2011
Return-Path: <townsley@cisco.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C468721F8B8F for <homenet@ietfa.amsl.com>; Fri, 25 Nov 2011 00:44:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.22
X-Spam-Level: 
X-Spam-Status: No, score=-10.22 tagged_above=-999 required=5 tests=[AWL=-0.378, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_46=0.6, RCVD_IN_DNSWL_HI=-8, SUBJECT_FUZZY_TION=0.156]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Joy8udpaWgiX for <homenet@ietfa.amsl.com>; Fri, 25 Nov 2011 00:44:00 -0800 (PST)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id 3533921F8B8E for <homenet@ietf.org>; Fri, 25 Nov 2011 00:44:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=townsley@cisco.com; l=8132; q=dns/txt; s=iport; t=1322210640; x=1323420240; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to; bh=zL3JqhyFCFGSIrnuEYr3xHaqUUXtASlICrB3UD4PJBg=; b=YTuYQnz9iYOL86d81nHZeWWO3gpRPDKGv8Y6BCzunel62bVw7IKhhNut sXs4dMtdumykQZ6fSle9yjYLcCaA1Vrp0hjktBa6aK6UI6MmJhwlZW4Lx hXjl1Vm0PFuGlyXxjZypy9iDmdh5H9dsiFcGsglEkM+1CV/gX2rfMRh6i w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAAtUz06Q/khN/2dsb2JhbAA6Cqp0gQWBcgEBAQMBAQEBDwFbCwULCxguJzAGEyKHYwiXRwGdcgSHLoJRYwSUSpIM
X-IronPort-AV: E=Sophos;i="4.69,570,1315180800"; d="scan'208,217";a="60400622"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-2.cisco.com with ESMTP; 25 Nov 2011 08:43:58 +0000
Received: from ams-townsley-8712.cisco.com (ams-townsley-8712.cisco.com [10.55.233.227]) by ams-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id pAP8hwK4021499; Fri, 25 Nov 2011 08:43:58 GMT
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-15-306054432
From: Mark Townsley <townsley@cisco.com>
In-Reply-To: <CAKD1Yr3zp1Gn1P-jDVgna2ViWeQiyCaTM=hTchpJq2snPSL-hw@mail.gmail.com>
Date: Fri, 25 Nov 2011 09:43:57 +0100
Message-Id: <9956D114-4D15-4F60-A444-745857F12816@cisco.com>
References: <CAKD1Yr3Y=EO9siQkAuZd7LtqsOT_8GswWkPOoiJEhtvnULcytw@mail.gmail.com> <4ECB98BC.8070600@riw.us> <ACDC3C9F-85D2-4AF6-AA8C-2A2E6EEDC8EE@fugue.com> <CAKD1Yr26zO0Dbco35ngWhj4W0hv_d_zJTCcbB-SSKqPpQab=ig@mail.gmail.com> <5C87A581-B2FD-4A1B-AD6B-7823279631BE@fugue.com> <CAKD1Yr3zp1Gn1P-jDVgna2ViWeQiyCaTM=hTchpJq2snPSL-hw@mail.gmail.com>
To: Lorenzo Colitti <lorenzo@google.com>
X-Mailer: Apple Mail (2.1084)
Cc: Russ White <russw@riw.us>, homenet@ietf.org, Ted Lemon <mellon@fugue.com>
Subject: Re: [homenet] Creating a security association via physical link + button
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 25 Nov 2011 08:44:01 -0000

--Apple-Mail-15-306054432
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


Before we decide that we must have an IGP, that it must be =
cryptographically secured, and that we have to tackle key distribution =
for it, I'd like to take a step or two back from the routing protocol =
part of the equation.

First things first, we have to detect that there is a device present, =
whether it is a router or not, and if so what kind of router to router =
border we have on that link so that we can apply a policy. If that =
policy allows sending and receiving of addressing and routing =
information, from the perspective of the routing protocol it has every =
thing it needs to start sending IGP packets in the clear on that link. =
In terms of usability, the homenet cannot afford crypto security or key =
exchange at every layer. I think we must inherently trust security from =
layer 2 or physical, just like we do today between routers and hosts (or =
nat-routers and nat-routers for IPv4) in the home.=20

In practical terms, I think this means that if two routers are connected =
with a physical link, that link should be trusted enough to send =
packets, in the clear, which can at least identify what kind of router =
to router link this is (e.g., local, ISP, etc.). The same applies if two =
routers are connected over a secured wireless L2 link.  Similarly, a =
wired broadband or 3G/LTE wireless connection to an ISP router in the =
neighborhood has its own authentication and policy enforcement happening =
at L2.=20

In terms of UI, if one of those two routers is actually a PC or phone, =
we shouldn't worry about the "pairing" issues much as there is enough =
user interaction to sort that out (I do think that the state of the art =
could be improved here, but that's for the UI wizards make better, not =
protocol hacks like us). The most problematic real-world case today that =
comes to mind would be in how to establish homenet routers that are =
connected via a wireless link should be considered part of the same =
network. A link+button might be the best way to make this happen for =
some routers, but others might prefer a UI from a PC (e.g., the "airport =
utility") with passwords. I think the furthest we can go here is to say =
that such a link must exist, and what the minimum level of packet =
exchange should be allowed before discovering what type of =
router-to-router link is present.=20

- Mark



On Nov 25, 2011, at 1:46 AM, Lorenzo Colitti wrote:

> On Fri, Nov 25, 2011 at 01:27, Ted Lemon <mellon@fugue.com> wrote:
>> If one is a member of a homenet and an ISP connection already, and =
one has a blank config, then you might assume that  the one with the =
blank config should join the existing homenet. What if they both have a =
config on them? What if you're actually merging two separate networks?
>=20
> I think that's the idea.   The user is saying "merge the two networks" =
in this case.
>=20
> Ok, so it would seem to me that to support that case then we need to =
either a) support multiple simultaneous keys in the IGP or b) provide a =
mechanism to tell a number of homenet routers that "the key to the IGP =
is changing". Both are non-trivial. Any other ideas?
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet


--Apple-Mail-15-306054432
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><br></div><div>Before we decide that we must have an IGP, that it =
must be cryptographically secured, and that we have to tackle key =
distribution for it, I'd like to take a step or two back from the =
routing protocol part of the equation.</div><div><br></div><div>First =
things first, we have to detect that there is a device present, whether =
it is a router or not, and if so what kind of router to router border we =
have on that link so that we can apply a policy. If that policy allows =
sending and receiving of addressing and routing information, from the =
perspective of the routing protocol it has every thing it needs to start =
sending IGP packets in the clear on that link. In terms of usability, =
the homenet cannot afford crypto security or key exchange at every =
layer. I think we must inherently trust security from layer 2 or =
physical, just like we do today between routers and hosts (or =
nat-routers and nat-routers for IPv4)&nbsp;in the =
home.&nbsp;</div><div><br></div><div>In practical terms, I think this =
means that if two routers are connected with a physical link, that link =
should be trusted enough to send packets, in the clear, which can at =
least identify what kind of router to router link this is (e.g., local, =
ISP, etc.). The same applies if two routers are connected over a secured =
wireless L2 link. &nbsp;Similarly, a wired broadband or 3G/LTE wireless =
connection to an ISP router in the neighborhood has its own =
authentication and policy enforcement happening at =
L2.&nbsp;</div><div><br></div><div>In terms of UI, if one of those two =
routers is actually a PC or phone, we shouldn't worry about the =
"pairing" issues much as there is enough user interaction to sort that =
out (I do think that the state of the art could be improved here, but =
that's for the UI wizards make better, not protocol hacks like =
us).&nbsp;The most problematic real-world case today that comes to mind =
would be in how to establish homenet routers that are connected via a =
wireless link should be considered part of the same network. A =
link+button might be the best way to make this happen for some routers, =
but others might prefer a UI from a PC (e.g., the "airport utility") =
with passwords. I think the furthest we can go here is to say that such =
a link must exist, and what the minimum level of packet exchange should =
be allowed before discovering what type of router-to-router link is =
present.&nbsp;</div><div><br></div><div>- =
Mark</div><div><br></div><div><br></div><br><div><div>On Nov 25, 2011, =
at 1:46 AM, Lorenzo Colitti wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div =
class=3D"gmail_quote">On Fri, Nov 25, 2011 at 01:27, Ted Lemon <span =
dir=3D"ltr">&lt;<a =
href=3D"mailto:mellon@fugue.com">mellon@fugue.com</a>&gt;</span> =
wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex;">

<div style=3D"word-wrap:break-word"><div class=3D"im"><div><blockquote =
type=3D"cite"><span =
style=3D"border-collapse:separate;font-family:Helvetica;font-style:normal;=
font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:n=
ormal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-sp=
ace:normal;word-spacing:0px;font-size:medium">If one is a member of a =
homenet and an ISP connection already, and one has a blank config, then =
you might assume that &nbsp;the one with the blank config should join =
the existing homenet. What if they both have a config on them? What if =
you're actually merging two separate networks?</span></blockquote>

</div></div><div>I think that's the idea. &nbsp; The user is saying =
"merge the two networks" in this =
case.</div></div></blockquote><div><br></div><div>Ok, so it would seem =
to me that to support that case then we need to either a) support =
multiple simultaneous keys in the IGP or b) provide a mechanism to tell =
a number of homenet routers that "the key to the IGP is changing". Both =
are non-trivial. Any other ideas?</div>

</div>
_______________________________________________<br>homenet mailing =
list<br><a =
href=3D"mailto:homenet@ietf.org">homenet@ietf.org</a><br>https://www.ietf.=
org/mailman/listinfo/homenet<br></blockquote></div><br></body></html>=

--Apple-Mail-15-306054432--

From townsley@cisco.com  Fri Nov 25 00:50:36 2011
Return-Path: <townsley@cisco.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 99BA621F8C36 for <homenet@ietfa.amsl.com>; Fri, 25 Nov 2011 00:50:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.394
X-Spam-Level: 
X-Spam-Status: No, score=-10.394 tagged_above=-999 required=5 tests=[AWL=0.048, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, SUBJECT_FUZZY_TION=0.156]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 91y3ny1ZMKvN for <homenet@ietfa.amsl.com>; Fri, 25 Nov 2011 00:50:35 -0800 (PST)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id 9C1EF21F84B2 for <homenet@ietf.org>; Fri, 25 Nov 2011 00:50:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=townsley@cisco.com; l=4326; q=dns/txt; s=iport; t=1322211033; x=1323420633; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to; bh=4OxhWyOAKGPfPUZnsYpP08O7p06rpw22IF4IDSUkt28=; b=OCzg/+x9VerUdQgYqmjZaydRNNoJ5Sa2gqHfkb4UgtRliV4i7EmhwQP9 4ZUEmkbIH6T4713taWIIuRjYWbYjwzjRFShh0s7mIiSL51RwYpLJys9CR l+ujqXTVQk8R2M3GsI5aYHIIvbuOos84A7tz1V0uSUop9ZaNg8IbUZVmg Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAFNWz06Q/khN/2dsb2JhbABEqnSBBYFyAQEBAwEBAQEPAVsLBQsLBAoKLicwBhMih2MIl00BnXIEiX9jBJRKkgw
X-IronPort-AV: E=Sophos;i="4.69,570,1315180800"; d="scan'208,217";a="60400896"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-2.cisco.com with ESMTP; 25 Nov 2011 08:50:32 +0000
Received: from ams-townsley-8712.cisco.com (ams-townsley-8712.cisco.com [10.55.233.227]) by ams-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id pAP8oWVe023277; Fri, 25 Nov 2011 08:50:32 GMT
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-16-306448365
From: Mark Townsley <townsley@cisco.com>
In-Reply-To: <E70EE283-116C-49CD-854C-2DA20783FFD7@fugue.com>
Date: Fri, 25 Nov 2011 09:50:31 +0100
Message-Id: <97F2586F-3E18-47F3-B369-47BE7517204A@cisco.com>
References: <CAKD1Yr3Y=EO9siQkAuZd7LtqsOT_8GswWkPOoiJEhtvnULcytw@mail.gmail.com> <4ECB98BC.8070600@riw.us> <ACDC3C9F-85D2-4AF6-AA8C-2A2E6EEDC8EE@fugue.com> <CAKD1Yr26zO0Dbco35ngWhj4W0hv_d_zJTCcbB-SSKqPpQab=ig@mail.gmail.com> <5C87A581-B2FD-4A1B-AD6B-7823279631BE@fugue.com> <CAKD1Yr3zp1Gn1P-jDVgna2ViWeQiyCaTM=hTchpJq2snPSL-hw@mail.gmail.com> <E70EE283-116C-49CD-854C-2DA20783FFD7@fugue.com>
To: Ted Lemon <mellon@fugue.com>
X-Mailer: Apple Mail (2.1084)
Cc: Russ White <russw@riw.us>, homenet@ietf.org, Lorenzo Colitti <lorenzo@google.com>
Subject: Re: [homenet] Creating a security association via physical link + button
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 25 Nov 2011 08:50:36 -0000

--Apple-Mail-16-306448365
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Nov 25, 2011, at 3:42 AM, Ted Lemon wrote:

> On Nov 24, 2011, at 7:46 PM, Lorenzo Colitti wrote:
>> Ok, so it would seem to me that to support that case then we need to =
either a) support multiple simultaneous keys in the IGP or b) provide a =
mechanism to tell a number of homenet routers that "the key to the IGP =
is changing". Both are non-trivial. Any other ideas?
>=20
> I think a security model that doesn't have each router generating its =
own keys, and using public key cryptography, is doomed.   If you use a =
shared secret, it's too easy to pwn your network because it has to be =
exchanged in the clear.   If the IGP protocol we want doesn't support =
this, then it pretty much has to be fixed, or we just can't do this.

In the email I just sent, I'm making an argument for why this is not the =
case. An IGP in a homenet setting needs crypto security no more than =
DHCP, ND or mDNS would. It's just another configuration protocol within =
the home.=20

Yes, this means that we need to trust L2 or physical security. But =
that's already very much the case today. If we add keys and crypto at =
every layer we are doomed before we start on usability alone.=20

- Mark

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


--Apple-Mail-16-306448365
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On Nov 25, 2011, at 3:42 AM, Ted Lemon wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><div>On Nov 24, 2011, at =
7:46 PM, Lorenzo Colitti wrote:</div><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Helvetica; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; ">Ok, so it =
would seem to me that to support that case then we need to either a) =
support multiple simultaneous keys in the IGP or b) provide a mechanism =
to tell a number of homenet routers that "the key to the IGP is =
changing". Both are non-trivial. Any other =
ideas?</span></blockquote></div><br><div>I think a security model that =
doesn't have each router generating its own keys, and using public key =
cryptography, is doomed. &nbsp; If you use a shared secret, it's too =
easy to pwn your network because it has to be exchanged in the clear. =
&nbsp; If the IGP protocol we want doesn't support this, then it pretty =
much has to be fixed, or we just can't do =
this.</div></div></blockquote><div><br></div><div>In the email I just =
sent, I'm making an argument for why this is not the case. An IGP in a =
homenet setting needs crypto security no more than DHCP, ND or mDNS =
would. It's just another configuration protocol within the =
home.&nbsp;</div><div><br></div><div>Yes, this means that we need to =
trust L2 or physical security. But that's already very much the case =
today. If we add keys and crypto at every layer we are doomed before we =
start on usability alone.&nbsp;</div><div><br></div><div>- =
Mark</div><br><blockquote type=3D"cite"><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; =
"><div><br></div></div>_______________________________________________<br>=
homenet mailing list<br><a =
href=3D"mailto:homenet@ietf.org">homenet@ietf.org</a><br>https://www.ietf.=
org/mailman/listinfo/homenet<br></blockquote></div><br></body></html>=

--Apple-Mail-16-306448365--

From rturner@amalfisystems.com  Fri Nov 25 04:30:18 2011
Return-Path: <rturner@amalfisystems.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5298321F8C98 for <homenet@ietfa.amsl.com>; Fri, 25 Nov 2011 04:30:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.323
X-Spam-Level: 
X-Spam-Status: No, score=-2.323 tagged_above=-999 required=5 tests=[AWL=0.119,  BAYES_00=-2.599, HTML_MESSAGE=0.001, SUBJECT_FUZZY_TION=0.156]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KUD73aoDzd4Z for <homenet@ietfa.amsl.com>; Fri, 25 Nov 2011 04:30:17 -0800 (PST)
Received: from omr16.networksolutionsemail.com (omr16.networksolutionsemail.com [205.178.146.66]) by ietfa.amsl.com (Postfix) with ESMTP id 893A821F8C97 for <homenet@ietf.org>; Fri, 25 Nov 2011 04:30:17 -0800 (PST)
Received: from cm-omr5 (mail.networksolutionsemail.com [205.178.146.50]) by omr16.networksolutionsemail.com (8.13.8/8.13.8) with ESMTP id pAPCUEkw004618 for <homenet@ietf.org>; Fri, 25 Nov 2011 07:30:16 -0500
Authentication-Results: cm-omr5 smtp.user=rturner@amalfisystems.com; auth=pass (LOGIN)
X-Authenticated-UID: rturner@amalfisystems.com
Received: from [98.151.18.158] ([98.151.18.158:60446] helo=localhost) by cm-omr5 (envelope-from <rturner@amalfisystems.com>) (ecelerity 2.2.2.41 r(31179/31189)) with ESMTPA id 1B/DC-04879-45A8FCE4; Fri, 25 Nov 2011 07:30:13 -0500
Date: Fri, 25 Nov 2011 04:30:08 -0800
Message-ID: <kkblj0mbs8xw8pp32w219ww6.1322224208905@email.android.com>
Importance: normal
From: Randy Turner <rturner@amalfisystems.com>
To: townsley@cisco.com, mellon@fugue.com
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="--_com.android.email_88778320156503"
Cc: russw@riw.us, homenet@ietf.org, lorenzo@google.com
Subject: Re: [homenet] Creating a security association via physical link +	button
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 25 Nov 2011 12:30:18 -0000

----_com.android.email_88778320156503
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64

CkkgdGhpbmsgSSBhZ3JlZSB0aGF0IGNvbmZpZGVudGlhbGl0eSBvZiByb3V0aW5nIHRyYWZmaWMg
aXMgcHJvYmFibHkgbm90IGFuIGlzc3VlIGZvciBIb21lbmV0IC0gaG93ZXZlciwgSSBkbyB0aGlu
ayB3ZSBzaG91bGQgY29uc2lkZXIgaW50ZWdyaXR5IG9mIHJvdXRpbmcgdHJhZmZpYyAtIGllLCBy
b3V0ZXIgQSBzaG91bGQgInRydXN0IiB0aGF0IHJvdXRlIHVwZGF0ZXMgZnJvbSByb3V0ZXIgQiBh
cmUgY29ycmVjdC4gVGhhdCBiZWluZyBzYWlkLCB0aGlzIGlzIGp1c3QgYW4gaW50dWl0aXZlIGZl
ZWxpbmcgcmVnYXJkaW5nIHNlY3VyaXR5IC0gbWF5YmUgd2UgbmVlZCBzb21lb25lIHRvIHdvcmsg
b24gYSB0aHJlYXQgYW5hbHlzaXMgYW5kIHdoYXQgdGhlIGltcGxpY2F0aW9ucyBjb3VsZCBiZSB0
byB0aGUgdHlwZXMgb2YgYXBwbGljYXRpb25zIHdlIGFudGljaXBhdGUKClJhbmR5CgotLS0tLS0t
LSBPcmlnaW5hbCBtZXNzYWdlIC0tLS0tLS0tClN1YmplY3Q6IFJlOiBbaG9tZW5ldF0gQ3JlYXRp
bmcgYSBzZWN1cml0eSBhc3NvY2lhdGlvbiB2aWEgcGh5c2ljYWwgbGluayArCWJ1dHRvbiAKRnJv
bTogTWFyayBUb3duc2xleSA8dG93bnNsZXlAY2lzY28uY29tPiAKVG86IFRlZCBMZW1vbiA8bWVs
bG9uQGZ1Z3VlLmNvbT4gCkNDOiBSdXNzIFdoaXRlIDxydXNzd0ByaXcudXM+LGhvbWVuZXRAaWV0
Zi5vcmcsTG9yZW56byBDb2xpdHRpIDxsb3JlbnpvQGdvb2dsZS5jb20+IAoKCk9uIE5vdiAyNSwg
MjAxMSwgYXQgMzo0MiBBTSwgVGVkIExlbW9uIHdyb3RlOgoKT24gTm92IDI0LCAyMDExLCBhdCA3
OjQ2IFBNLCBMb3JlbnpvIENvbGl0dGkgd3JvdGU6Ck9rLCBzbyBpdCB3b3VsZCBzZWVtIHRvIG1l
IHRoYXQgdG8gc3VwcG9ydCB0aGF0IGNhc2UgdGhlbiB3ZSBuZWVkIHRvIGVpdGhlciBhKSBzdXBw
b3J0IG11bHRpcGxlIHNpbXVsdGFuZW91cyBrZXlzIGluIHRoZSBJR1Agb3IgYikgcHJvdmlkZSBh
IG1lY2hhbmlzbSB0byB0ZWxsIGEgbnVtYmVyIG9mIGhvbWVuZXQgcm91dGVycyB0aGF0ICJ0aGUg
a2V5IHRvIHRoZSBJR1AgaXMgY2hhbmdpbmciLiBCb3RoIGFyZSBub24tdHJpdmlhbC4gQW55IG90
aGVyIGlkZWFzPwoKSSB0aGluayBhIHNlY3VyaXR5IG1vZGVsIHRoYXQgZG9lc24ndCBoYXZlIGVh
Y2ggcm91dGVyIGdlbmVyYXRpbmcgaXRzIG93biBrZXlzLCBhbmQgdXNpbmcgcHVibGljIGtleSBj
cnlwdG9ncmFwaHksIGlzIGRvb21lZC4gwqAgSWYgeW91IHVzZSBhIHNoYXJlZCBzZWNyZXQsIGl0
J3MgdG9vIGVhc3kgdG8gcHduIHlvdXIgbmV0d29yayBiZWNhdXNlIGl0IGhhcyB0byBiZSBleGNo
YW5nZWQgaW4gdGhlIGNsZWFyLiDCoCBJZiB0aGUgSUdQIHByb3RvY29sIHdlIHdhbnQgZG9lc24n
dCBzdXBwb3J0IHRoaXMsIHRoZW4gaXQgcHJldHR5IG11Y2ggaGFzIHRvIGJlIGZpeGVkLCBvciB3
ZSBqdXN0IGNhbid0IGRvIHRoaXMuCgpJbiB0aGUgZW1haWwgSSBqdXN0IHNlbnQsIEknbSBtYWtp
bmcgYW4gYXJndW1lbnQgZm9yIHdoeSB0aGlzIGlzIG5vdCB0aGUgY2FzZS4gQW4gSUdQIGluIGEg
aG9tZW5ldCBzZXR0aW5nIG5lZWRzIGNyeXB0byBzZWN1cml0eSBubyBtb3JlIHRoYW4gREhDUCwg
TkQgb3IgbUROUyB3b3VsZC4gSXQncyBqdXN0IGFub3RoZXIgY29uZmlndXJhdGlvbiBwcm90b2Nv
bCB3aXRoaW4gdGhlIGhvbWUuwqAKClllcywgdGhpcyBtZWFucyB0aGF0IHdlIG5lZWQgdG8gdHJ1
c3QgTDIgb3IgcGh5c2ljYWwgc2VjdXJpdHkuIEJ1dCB0aGF0J3MgYWxyZWFkeSB2ZXJ5IG11Y2gg
dGhlIGNhc2UgdG9kYXkuIElmIHdlIGFkZCBrZXlzIGFuZCBjcnlwdG8gYXQgZXZlcnkgbGF5ZXIg
d2UgYXJlIGRvb21lZCBiZWZvcmUgd2Ugc3RhcnQgb24gdXNhYmlsaXR5IGFsb25lLsKgCgotIE1h
cmsKCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpob21l
bmV0IG1haWxpbmcgbGlzdApob21lbmV0QGlldGYub3JnCmh0dHBzOi8vd3d3LmlldGYub3JnL21h
aWxtYW4vbGlzdGluZm8vaG9tZW5ldAoK

----_com.android.email_88778320156503
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: base64

PGh0bWw+PGhlYWQ+PG1ldGEgaHR0cC1lcXVpdj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0
L2h0bWw7IGNoYXJzZXQ9VVRGLTgiPjwvaGVhZD48Ym9keT48ZGl2Pjxicj48L2Rpdj48ZGl2Pkkg
dGhpbmsgSSBhZ3JlZSB0aGF0IGNvbmZpZGVudGlhbGl0eSBvZiByb3V0aW5nIHRyYWZmaWMgaXMg
cHJvYmFibHkgbm90IGFuIGlzc3VlIGZvciBIb21lbmV0IC0gaG93ZXZlciwgSSBkbyB0aGluayB3
ZSBzaG91bGQgY29uc2lkZXIgaW50ZWdyaXR5IG9mIHJvdXRpbmcgdHJhZmZpYyAtIGllLCByb3V0
ZXIgQSBzaG91bGQgInRydXN0IiB0aGF0IHJvdXRlIHVwZGF0ZXMgZnJvbSByb3V0ZXIgQiBhcmUg
Y29ycmVjdC4gVGhhdCBiZWluZyBzYWlkLCB0aGlzIGlzIGp1c3QgYW4gaW50dWl0aXZlIGZlZWxp
bmcgcmVnYXJkaW5nIHNlY3VyaXR5IC0gbWF5YmUgd2UgbmVlZCBzb21lb25lIHRvIHdvcmsgb24g
YSB0aHJlYXQgYW5hbHlzaXMgYW5kIHdoYXQgdGhlIGltcGxpY2F0aW9ucyBjb3VsZCBiZSB0byB0
aGUgdHlwZXMgb2YgYXBwbGljYXRpb25zIHdlIGFudGljaXBhdGU8L2Rpdj48ZGl2Pjxicj48L2Rp
dj48ZGl2PlJhbmR5PC9kaXY+PGJyPjxicj48YnI+LS0tLS0tLS0gT3JpZ2luYWwgbWVzc2FnZSAt
LS0tLS0tLTxicj5TdWJqZWN0OiBSZTogW2hvbWVuZXRdIENyZWF0aW5nIGEgc2VjdXJpdHkgYXNz
b2NpYXRpb24gdmlhIHBoeXNpY2FsIGxpbmsgKwlidXR0b24gPGJyPkZyb206IE1hcmsgVG93bnNs
ZXkgJmx0O3Rvd25zbGV5QGNpc2NvLmNvbSZndDsgPGJyPlRvOiBUZWQgTGVtb24gJmx0O21lbGxv
bkBmdWd1ZS5jb20mZ3Q7IDxicj5DQzogUnVzcyBXaGl0ZSAmbHQ7cnVzc3dAcml3LnVzJmd0Oyxo
b21lbmV0QGlldGYub3JnLExvcmVuem8gQ29saXR0aSAmbHQ7bG9yZW56b0Bnb29nbGUuY29tJmd0
OyA8YnI+PGJyPjxicj48YnI+PGRpdj48ZGl2Pk9uIE5vdiAyNSwgMjAxMSwgYXQgMzo0MiBBTSwg
VGVkIExlbW9uIHdyb3RlOjwvZGl2PjxiciBjbGFzcz0iQXBwbGUtaW50ZXJjaGFuZ2UtbmV3bGlu
ZSI+PGJsb2NrcXVvdGUgdHlwZT0iY2l0ZSI+PGRpdiBzdHlsZT0id29yZC13cmFwOiBicmVhay13
b3JkOyAtd2Via2l0LW5ic3AtbW9kZTogc3BhY2U7IC13ZWJraXQtbGluZS1icmVhazogYWZ0ZXIt
d2hpdGUtc3BhY2U7ICI+PGRpdj48ZGl2Pk9uIE5vdiAyNCwgMjAxMSwgYXQgNzo0NiBQTSwgTG9y
ZW56byBDb2xpdHRpIHdyb3RlOjwvZGl2PjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiPjxzcGFuIGNs
YXNzPSJBcHBsZS1zdHlsZS1zcGFuIiBzdHlsZT0iZm9udC1mYW1pbHk6IEhlbHZldGljYTsgIj5P
aywgc28gaXQgd291bGQgc2VlbSB0byBtZSB0aGF0IHRvIHN1cHBvcnQgdGhhdCBjYXNlIHRoZW4g
d2UgbmVlZCB0byBlaXRoZXIgYSkgc3VwcG9ydCBtdWx0aXBsZSBzaW11bHRhbmVvdXMga2V5cyBp
biB0aGUgSUdQIG9yIGIpIHByb3ZpZGUgYSBtZWNoYW5pc20gdG8gdGVsbCBhIG51bWJlciBvZiBo
b21lbmV0IHJvdXRlcnMgdGhhdCAidGhlIGtleSB0byB0aGUgSUdQIGlzIGNoYW5naW5nIi4gQm90
aCBhcmUgbm9uLXRyaXZpYWwuIEFueSBvdGhlciBpZGVhcz88L3NwYW4+PC9ibG9ja3F1b3RlPjwv
ZGl2Pjxicj48ZGl2PkkgdGhpbmsgYSBzZWN1cml0eSBtb2RlbCB0aGF0IGRvZXNuJ3QgaGF2ZSBl
YWNoIHJvdXRlciBnZW5lcmF0aW5nIGl0cyBvd24ga2V5cywgYW5kIHVzaW5nIHB1YmxpYyBrZXkg
Y3J5cHRvZ3JhcGh5LCBpcyBkb29tZWQuICZuYnNwOyBJZiB5b3UgdXNlIGEgc2hhcmVkIHNlY3Jl
dCwgaXQncyB0b28gZWFzeSB0byBwd24geW91ciBuZXR3b3JrIGJlY2F1c2UgaXQgaGFzIHRvIGJl
IGV4Y2hhbmdlZCBpbiB0aGUgY2xlYXIuICZuYnNwOyBJZiB0aGUgSUdQIHByb3RvY29sIHdlIHdh
bnQgZG9lc24ndCBzdXBwb3J0IHRoaXMsIHRoZW4gaXQgcHJldHR5IG11Y2ggaGFzIHRvIGJlIGZp
eGVkLCBvciB3ZSBqdXN0IGNhbid0IGRvIHRoaXMuPC9kaXY+PC9kaXY+PC9ibG9ja3F1b3RlPjxk
aXY+PGJyPjwvZGl2PjxkaXY+SW4gdGhlIGVtYWlsIEkganVzdCBzZW50LCBJJ20gbWFraW5nIGFu
IGFyZ3VtZW50IGZvciB3aHkgdGhpcyBpcyBub3QgdGhlIGNhc2UuIEFuIElHUCBpbiBhIGhvbWVu
ZXQgc2V0dGluZyBuZWVkcyBjcnlwdG8gc2VjdXJpdHkgbm8gbW9yZSB0aGFuIERIQ1AsIE5EIG9y
IG1ETlMgd291bGQuIEl0J3MganVzdCBhbm90aGVyIGNvbmZpZ3VyYXRpb24gcHJvdG9jb2wgd2l0
aGluIHRoZSBob21lLiZuYnNwOzwvZGl2PjxkaXY+PGJyPjwvZGl2PjxkaXY+WWVzLCB0aGlzIG1l
YW5zIHRoYXQgd2UgbmVlZCB0byB0cnVzdCBMMiBvciBwaHlzaWNhbCBzZWN1cml0eS4gQnV0IHRo
YXQncyBhbHJlYWR5IHZlcnkgbXVjaCB0aGUgY2FzZSB0b2RheS4gSWYgd2UgYWRkIGtleXMgYW5k
IGNyeXB0byBhdCBldmVyeSBsYXllciB3ZSBhcmUgZG9vbWVkIGJlZm9yZSB3ZSBzdGFydCBvbiB1
c2FiaWxpdHkgYWxvbmUuJm5ic3A7PC9kaXY+PGRpdj48YnI+PC9kaXY+PGRpdj4tIE1hcms8L2Rp
dj48YnI+PGJsb2NrcXVvdGUgdHlwZT0iY2l0ZSI+PGRpdiBzdHlsZT0id29yZC13cmFwOiBicmVh
ay13b3JkOyAtd2Via2l0LW5ic3AtbW9kZTogc3BhY2U7IC13ZWJraXQtbGluZS1icmVhazogYWZ0
ZXItd2hpdGUtc3BhY2U7ICI+PGRpdj48YnI+PC9kaXY+PC9kaXY+X19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX188YnI+aG9tZW5ldCBtYWlsaW5nIGxpc3Q8YnI+
PGEgaHJlZj0ibWFpbHRvOmhvbWVuZXRAaWV0Zi5vcmciPmhvbWVuZXRAaWV0Zi5vcmc8L2E+PGJy
Pmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vaG9tZW5ldDxicj48L2Jsb2Nr
cXVvdGU+PC9kaXY+PGJyPjwvYm9keT4=

----_com.android.email_88778320156503--



From acee.lindem@ericsson.com  Fri Nov 25 05:34:05 2011
Return-Path: <acee.lindem@ericsson.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CAB521F8B88 for <homenet@ietfa.amsl.com>; Fri, 25 Nov 2011 05:34:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.162
X-Spam-Level: 
X-Spam-Status: No, score=-6.162 tagged_above=-999 required=5 tests=[AWL=-0.320, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_46=0.6, RCVD_IN_DNSWL_MED=-4, SUBJECT_FUZZY_TION=0.156]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PofGzFf3UbZF for <homenet@ietfa.amsl.com>; Fri, 25 Nov 2011 05:34:04 -0800 (PST)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 33E9221F8B85 for <homenet@ietf.org>; Fri, 25 Nov 2011 05:34:04 -0800 (PST)
Received: from eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id pAPDXpkS012421; Fri, 25 Nov 2011 07:33:53 -0600
Received: from EUSAACMS0702.eamcs.ericsson.se ([169.254.1.25]) by eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) with mapi; Fri, 25 Nov 2011 08:33:51 -0500
From: Acee Lindem <acee.lindem@ericsson.com>
To: Mark Townsley <townsley@cisco.com>
Date: Fri, 25 Nov 2011 08:33:49 -0500
Thread-Topic: [homenet] Creating a security association via physical link + button
Thread-Index: Acyrdt6KEMcTRy+bSOyFKvseuFwBuw==
Message-ID: <00D50698-B1C5-4A51-9359-EFF352EFB349@ericsson.com>
References: <CAKD1Yr3Y=EO9siQkAuZd7LtqsOT_8GswWkPOoiJEhtvnULcytw@mail.gmail.com> <4ECB98BC.8070600@riw.us> <ACDC3C9F-85D2-4AF6-AA8C-2A2E6EEDC8EE@fugue.com> <CAKD1Yr26zO0Dbco35ngWhj4W0hv_d_zJTCcbB-SSKqPpQab=ig@mail.gmail.com> <5C87A581-B2FD-4A1B-AD6B-7823279631BE@fugue.com> <CAKD1Yr3zp1Gn1P-jDVgna2ViWeQiyCaTM=hTchpJq2snPSL-hw@mail.gmail.com> <9956D114-4D15-4F60-A444-745857F12816@cisco.com>
In-Reply-To: <9956D114-4D15-4F60-A444-745857F12816@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/signed; boundary="Apple-Mail-2-323446007"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
Cc: Russ White <russw@riw.us>, "<homenet@ietf.org>" <homenet@ietf.org>, Ted Lemon <mellon@fugue.com>, Lorenzo Colitti <lorenzo@google.com>
Subject: Re: [homenet] Creating a security association via physical link +	button
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 25 Nov 2011 13:34:05 -0000

--Apple-Mail-2-323446007
Content-Type: multipart/alternative;
	boundary=Apple-Mail-1-323445986


--Apple-Mail-1-323445986
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

I agree. Given that the routing protocols under considerations use IPv6 =
link-local addresses and are confined to a packet exchanges between =
routers on the same link, this model seems appropriate.=20
Thanks,
Acee=20
On Nov 25, 2011, at 3:43 AM, Mark Townsley wrote:

>=20
> Before we decide that we must have an IGP, that it must be =
cryptographically secured, and that we have to tackle key distribution =
for it, I'd like to take a step or two back from the routing protocol =
part of the equation.
>=20
> First things first, we have to detect that there is a device present, =
whether it is a router or not, and if so what kind of router to router =
border we have on that link so that we can apply a policy. If that =
policy allows sending and receiving of addressing and routing =
information, from the perspective of the routing protocol it has every =
thing it needs to start sending IGP packets in the clear on that link. =
In terms of usability, the homenet cannot afford crypto security or key =
exchange at every layer. I think we must inherently trust security from =
layer 2 or physical, just like we do today between routers and hosts (or =
nat-routers and nat-routers for IPv4) in the home.=20
>=20
> In practical terms, I think this means that if two routers are =
connected with a physical link, that link should be trusted enough to =
send packets, in the clear, which can at least identify what kind of =
router to router link this is (e.g., local, ISP, etc.). The same applies =
if two routers are connected over a secured wireless L2 link.  =
Similarly, a wired broadband or 3G/LTE wireless connection to an ISP =
router in the neighborhood has its own authentication and policy =
enforcement happening at L2.=20
>=20
> In terms of UI, if one of those two routers is actually a PC or phone, =
we shouldn't worry about the "pairing" issues much as there is enough =
user interaction to sort that out (I do think that the state of the art =
could be improved here, but that's for the UI wizards make better, not =
protocol hacks like us). The most problematic real-world case today that =
comes to mind would be in how to establish homenet routers that are =
connected via a wireless link should be considered part of the same =
network. A link+button might be the best way to make this happen for =
some routers, but others might prefer a UI from a PC (e.g., the "airport =
utility") with passwords. I think the furthest we can go here is to say =
that such a link must exist, and what the minimum level of packet =
exchange should be allowed before discovering what type of =
router-to-router link is present.=20
>=20
> - Mark
>=20
>=20
>=20
> On Nov 25, 2011, at 1:46 AM, Lorenzo Colitti wrote:
>=20
>> On Fri, Nov 25, 2011 at 01:27, Ted Lemon <mellon@fugue.com> wrote:
>>> If one is a member of a homenet and an ISP connection already, and =
one has a blank config, then you might assume that  the one with the =
blank config should join the existing homenet. What if they both have a =
config on them? What if you're actually merging two separate networks?
>>=20
>> I think that's the idea.   The user is saying "merge the two =
networks" in this case.
>>=20
>> Ok, so it would seem to me that to support that case then we need to =
either a) support multiple simultaneous keys in the IGP or b) provide a =
mechanism to tell a number of homenet routers that "the key to the IGP =
is changing". Both are non-trivial. Any other ideas?
>> _______________________________________________
>> homenet mailing list
>> homenet@ietf.org
>> https://www.ietf.org/mailman/listinfo/homenet
>=20


--Apple-Mail-1-323445986
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I agree. Given that the routing protocols under considerations use IPv6 link-local addresses and are confined to a packet exchanges between routers on the same link, this model seems appropriate.&nbsp;<div>Thanks,</div><div>Acee&nbsp;<br><div><div>On Nov 25, 2011, at 3:43 AM, Mark Townsley wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">



<meta http-equiv="Content-Type" content="text/html; charset=utf-8">

<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<div><br>
</div>
<div>Before we decide that we must have an IGP, that it must be cryptographically secured, and that we have to tackle key distribution for it, I'd like to take a step or two back from the routing protocol part of the equation.</div>
<div><br>
</div>
<div>First things first, we have to detect that there is a device present, whether it is a router or not, and if so what kind of router to router border we have on that link so that we can apply a policy. If that policy allows sending and receiving of addressing
 and routing information, from the perspective of the routing protocol it has every thing it needs to start sending IGP packets in the clear on that link. In terms of usability, the homenet cannot afford crypto security or key exchange at every layer. I think
 we must inherently trust security from layer 2 or physical, just like we do today between routers and hosts (or nat-routers and nat-routers for IPv4)&nbsp;in the home.&nbsp;</div>
<div><br>
</div>
<div>In practical terms, I think this means that if two routers are connected with a physical link, that link should be trusted enough to send packets, in the clear, which can at least identify what kind of router to router link this is (e.g., local, ISP, etc.).
 The same applies if two routers are connected over a secured wireless L2 link. &nbsp;Similarly, a wired broadband or 3G/LTE wireless connection to an ISP router in the neighborhood has its own authentication and policy enforcement happening at L2.&nbsp;</div>
<div><br>
</div>
<div>In terms of UI, if one of those two routers is actually a PC or phone, we shouldn't worry about the "pairing" issues much as there is enough user interaction to sort that out (I do think that the state of the art could be improved here, but that's for
 the UI wizards make better, not protocol hacks like us).&nbsp;The most problematic real-world case today that comes to mind would be in how to establish homenet routers that are connected via a wireless link should be considered part of the same network. A link+button
 might be the best way to make this happen for some routers, but others might prefer a UI from a PC (e.g., the "airport utility") with passwords. I think the furthest we can go here is to say that such a link must exist, and what the minimum level of packet
 exchange should be allowed before discovering what type of router-to-router link is present.&nbsp;</div>
<div><br>
</div>
<div>- Mark</div>
<div><br>
</div>
<div><br>
</div>
<br>
<div>
<div>On Nov 25, 2011, at 1:46 AM, Lorenzo Colitti wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div class="gmail_quote">On Fri, Nov 25, 2011 at 01:27, Ted Lemon <span dir="ltr">
&lt;<a href="mailto:mellon@fugue.com">mellon@fugue.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div style="word-wrap:break-word">
<div class="im">
<div>
<blockquote type="cite"><span style="border-collapse:separate;font-family:Helvetica;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;font-size:medium">If
 one is a member of a homenet and an ISP connection already, and one has a blank config, then you might assume that &nbsp;the one with the blank config should join the existing homenet. What if they both have a config on them? What if you're actually merging two
 separate networks?</span></blockquote>
</div>
</div>
<div>I think that's the idea. &nbsp; The user is saying "merge the two networks" in this case.</div>
</div>
</blockquote>
<div><br>
</div>
<div>Ok, so it would seem to me that to support that case then we need to either a) support multiple simultaneous keys in the IGP or b) provide a mechanism to tell a number of homenet routers that "the key to the IGP is changing". Both are non-trivial. Any
 other ideas?</div>
</div>
_______________________________________________<br>
homenet mailing list<br>
<a href="mailto:homenet@ietf.org">homenet@ietf.org</a><br>
<a href="https://www.ietf.org/mailman/listinfo/homenet">https://www.ietf.org/mailman/listinfo/homenet</a><br>
</blockquote>
</div>
<br>
</div>

</blockquote></div><br></div></body></html>
--Apple-Mail-1-323445986--

--Apple-Mail-2-323446007
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIM8jCCBDQw
ggMcoAMCAQICECFWwVQHDV12M/Sr0yNv0sYwDQYJKoZIhvcNAQEFBQAwOTERMA8GA1UECgwIRXJp
Y3Nzb24xJDAiBgNVBAMMG0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMTAeFw0xMDEwMDEyMDA0
NTlaFw0xMzEwMDEyMDA0NDhaMG8xETAPBgNVBAoMCEVyaWNzc29uMR8wHQYDVQQDDBZBY2VlIExp
bmRlbSBMaW5kZW0gSUlJMRAwDgYDVQQFEwdlYWxmbGluMScwJQYJKoZIhvcNAQkBFhhhY2VlLmxp
bmRlbUBlcmljc3Nvbi5jb20wgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAI/Dc9ALiZuBMyuv
bsc3eBxjXZpMi45Z0vzsUQZTJGTBeY7p9JsdzXC9J1uMisBxYVi39R3KJo6I4hXVp9wrA1rxh4AE
bnP1+Gxfpj33uWEFYbBnVAJkIWYWF7CYTn8Zm/yd13vPXtuGA6ESeLnnJafwC9Y0YwUQ+4HX7PNv
uauVAgMBAAGjggGEMIIBgDCBwAYDVR0fBIG4MIG1MIGyoIGvoIGshjdodHRwOi8vY3JsLnRydXN0
LnRlbGlhLmNvbS9Fcmljc3Nvbk5MSW5kaXZpZHVhbENBMDEuY3JshnFsZGFwOi8vbGRhcC50cnVz
dC50ZWxpYS5jb20vY249RXJpY3Nzb24lMjBOTCUyMEluZGl2aWR1YWwlMjBDQTAxLG89RXJpY3Nz
b24/Y2VydGlmaWNhdGVyZXZvY2F0aW9ubGlzdDtiaW5hcnk/YmFzZTAjBgNVHREEHDAagRhhY2Vl
LmxpbmRlbUBlcmljc3Nvbi5jb20wRgYDVR0gBD8wPTA7BgYqhXBrAQEwMTAvBggrBgEFBQcCARYj
aHR0cDovL3d3dy5lcmljc3Nvbi5jb20vbGVnYWwuc2h0bWwwHQYDVR0OBBYEFAgOzAPuplmPr7C1
BTqV94OyqUdhMB8GA1UdIwQYMBaAFJYnw7jepV9dRD45UuVFsXZfYzCbMA4GA1UdDwEB/wQEAwIF
oDANBgkqhkiG9w0BAQUFAAOCAQEAE1gyNW6c2t/YsLxW5sm67+gVGK0Lnge4ub+k8dgGrK7Mj7em
nkOIFkjdv/tqdJ/SoUy/WEkBXba2TfpZ+lfluMgLYux1vSvqBUxYBsUHeNth2Q/Y6A9sCaDTBPlK
vZ2jLz814NavrVfgTCLdxX6zNtGdwzhviz+FyqyxYF43Q86RP8Gd/Npaz1W8pmYAHm0+lezuTx5k
F3Av3+SaZ/MR6s+RWuXEIdED36ajeQz+OG8Mh3nplofzdrOeoWGDz53YlfRhgj+TXo+H1lclZAvD
WVaMMXPdb27h9Hngsq87dkCW9uAyv8DI993rdhqzlEgUyQIL32icAXfTmTYgoGPOwjCCBEUwggMt
oAMCAQICEBPJ6v/eJq2p3KTKI4GDR+MwDQYJKoZIhvcNAQEFBQAwRDEaMBgGA1UECgwRVGVsaWFT
b25lcmEgR3JvdXAxJjAkBgNVBAMMHVRlbGlhU29uZXJhIFB1YmxpYyBSb290IENBIHYxMB4XDTA2
MTAwNjEwMDA1M1oXDTE2MTAwMjA1MDQxN1owOTERMA8GA1UECgwIRXJpY3Nzb24xJDAiBgNVBAMM
G0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoC
ggEBALYQd+Q1HuuHxDyNGFlEPzCxuPPFO5W2xyr+nqCVnNJ4QYFe1HACqavqNLwUGIqIEyHv1rLn
fub9LBc7dQpRHjl/dggin0ONOFJ36nbGEbfHjLJz2BzOWvwl84Sc+Fx09IrDU/SZSWFSfhqTu3TT
39h79brHdRkdPBUgBYgsiFKriHI0TjP5G8628H27BDzqUpzGLSYWgt6/tpwuOH5lcfNfHWMcCYXR
lobv0Klu8lxG5amWqAnqrH6ECOyYJTRbHTsaTIZOHy9Qw/0eXPujKT7tU5xxSI2SdceJqzUbAz2o
FRQ6Px7/GydpM/Rl+qYoGPcauHUL1aSeVJZqDFqcIF0CAwEAAaOCATwwggE4MBIGA1UdEwEB/wQI
MAYBAf8CAQAwRgYDVR0gBD8wPTA7BgcqhXAjAgEBMDAwLgYIKwYBBQUHAgEWImh0dHBzOi8vcmVw
b3NpdG9yeS50cnVzdC50ZWxpYS5jb20wgYkGA1UdHwSBgTB/MH2ge6B5hndsZGFwOi8vbGRhcC50
cnVzdC50ZWxpYS5jb20vY249VGVsaWFTb25lcmElMjBQdWJsaWMlMjBSb290JTIwQ0ElMjB2MSxv
PVRlbGlhU29uZXJhJTIwR3JvdXA/YXV0aG9yaXR5cmV2b2NhdGlvbmxpc3Q/YmFzZTAOBgNVHQ8B
Af8EBAMCAQYwHQYDVR0OBBYEFJYnw7jepV9dRD45UuVFsXZfYzCbMB8GA1UdIwQYMBaAFEXb8I+4
GmKhqCMbY4g4o9vgGmLxMA0GCSqGSIb3DQEBBQUAA4IBAQB2AEoqQz+M3Ra9alkpn/YnwhXIv6tP
jhUvSuNs00Nhd0T9XhlIU3a65CaB/UKSqnayE0t7Q0Qq3r+x/GK3in/mik8i/PK2/q8HutzYFSzz
6Npztpo2JG7AEKOJPVaeebjng45m6vNC7RIfzU9sG2LBR/hewS8s6dFFn70w795xUwJBWZ67OzIK
XrIVVvHTOYpbWA+MESKAXwFhnVONrOTWlVwrMUi4HbiPWpOk+xQbgehCEi7mu3cXsaU1Xq3kMXui
NuC7VKoob8mFO9o9RT+dlirD2uRXwNpvCu3but6Kyhu0+nvy2iXGKjdlxlWTsdDyulXYz+OYCMZ9
lFWRzMIPMIIEbTCCA1WgAwIBAgIRAJywjASay5cieGNithuGWj0wDQYJKoZIhvcNAQEFBQAwOjEZ
MBcGA1UEChMQUlNBIFNlY3VyaXR5IEluYzEdMBsGA1UECxMUUlNBIFNlY3VyaXR5IDIwNDggVjMw
HhcNMDYxMDMxMjA0MjI3WhcNMTYxMTAxMTU0MjI1WjBEMRowGAYDVQQKDBFUZWxpYVNvbmVyYSBH
cm91cDEmMCQGA1UEAwwdVGVsaWFTb25lcmEgUHVibGljIFJvb3QgQ0EgdjEwggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQDKTxADapCAq3mplX4R4gNt+WZe5QKGnaVEQSyY7lICKF5DuVdW
PMLHDjzhw5IzDd860ZZx/0VrhGB3DmP4SDIWCKo2PxvY5NckdBWPWp/T2uaQdOAwgqHpN0pe1X7/
jel59WsWYXKGg/81Wth73ZK/geE7Gz9Pvj1LU6N4YhLMgooxKnCS+ZjB5icWAg+Qd1QpQhF46H1i
bp6LsBWDp56MPpg8F5X6y7MGVcKYLdnLOPs84uxRW9qs1kBopzQBj6s5SyVh8A+j5liDBjghXYpw
/+paGEdqHPeSFYxZKeJatmjEKLYlxcZWRKf436KvQA9jBhMEmytMNbGicR1mRH6tAgMBAAGjggFi
MIIBXjAfBgNVHSMEGDAWgBQHw1EwpKrpRa41JPr/JCwz0LGdjDAdBgNVHQ4EFgQURdvwj7gaYqGo
IxtjiDij2+AaYvEwEgYDVR0TAQH/BAgwBgEB/wIBBDCBhQYDVR0gBH4wfDA9BgkqhkiG9w0FBgEw
MDAuBggrBgEFBQcCARYiaHR0cHM6Ly9yZXBvc2l0b3J5LnRydXN0LnRlbGlhLmNvbTA7BgcqhXAj
AgEBMDAwLgYIKwYBBQUHAgEWImh0dHBzOi8vcmVwb3NpdG9yeS50cnVzdC50ZWxpYS5jb20wcAYD
VR0fBGkwZzBloGOgYYZfaHR0cDovL3d3dy5yc2FzZWN1cml0eS5jb20vcHJvZHVjdHMva2Vvbi9y
ZXBvc2l0b3J5L2NlcnRpZmljYXRlX3N0YXR1cy9SU0FfU2VjdXJpdHlfMjA0OF92My5DUkwwDgYD
VR0PAQH/BAQDAgEGMA0GCSqGSIb3DQEBBQUAA4IBAQAEXpos2CnIm7/872ytSrEHWZgvhOUEkUm2
5PWf/XkWko41TaL9vIS1S6AdWChNqWmnYiS7GfaIiDM9s1D6K7hidWBDOm46bNdM3ZwhMyDCfkDJ
SgeJ0w+7YmjvChu7gWqDZCsbtZ5gA1ixCTdDnuZB67JGSPGW6r73coraDP8diOpiQouMvM6bKuTP
BH/1poLccsUxsKgrQ23JC9LWCRb8cYHkZjXFH1K44TsIl5Lne2oT0JI3pwdA2v6jO4p/OLHntP+n
pjwPbedMPUZkDYCkd3LSxj8c3JTxtA8SlPCtIHE1hh65xihg1JRIliSphrqr9kbfwHdeVxPdOI5G
tDYPMYICEjCCAg4CAQEwTTA5MREwDwYDVQQKDAhFcmljc3NvbjEkMCIGA1UEAwwbRXJpY3Nzb24g
TkwgSW5kaXZpZHVhbCBDQTAxAhAhVsFUBw1ddjP0q9Mjb9LGMAkGBSsOAwIaBQCgggEbMBgGCSqG
SIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMTEyNTEzMzM1MFowIwYJKoZI
hvcNAQkEMRYEFBenJjrVZj/h0G5mqUNJxZpAxmAhMFwGCSsGAQQBgjcQBDFPME0wOTERMA8GA1UE
CgwIRXJpY3Nzb24xJDAiBgNVBAMMG0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMQIQIVbBVAcN
XXYz9KvTI2/SxjBeBgsqhkiG9w0BCRACCzFPoE0wOTERMA8GA1UECgwIRXJpY3Nzb24xJDAiBgNV
BAMMG0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMQIQIVbBVAcNXXYz9KvTI2/SxjANBgkqhkiG
9w0BAQEFAASBgFHMWZe58oU6Pso88aHMmoROqoiVFs6470FZyeTmdyGkmCY42GFrXutSzp/8rswC
rIDGDU1Ssn8fGB8Ih2p6sevtFiEIo3UEn1i9/2eXm1vAgYU11dOWOCaYE/PE4z2Ha6KWpC2/tUVY
MvonjAJ/lJHpUe+3pXWxVNaZRUFtD8+SAAAAAAAA

--Apple-Mail-2-323446007--

From mellon@fugue.com  Fri Nov 25 09:22:45 2011
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E076421F8B24 for <homenet@ietfa.amsl.com>; Fri, 25 Nov 2011 09:22:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.019
X-Spam-Level: 
X-Spam-Status: No, score=-2.019 tagged_above=-999 required=5 tests=[AWL=0.423,  BAYES_00=-2.599, HTML_MESSAGE=0.001, SUBJECT_FUZZY_TION=0.156]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XM6Dyysj9Y8e for <homenet@ietfa.amsl.com>; Fri, 25 Nov 2011 09:22:44 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 84F5021F8A62 for <homenet@ietf.org>; Fri, 25 Nov 2011 09:22:44 -0800 (PST)
Received: from [IPv6:2001:470:1f07:1486:941f:74f9:f58d:df48] (unknown [IPv6:2001:470:1f07:1486:941f:74f9:f58d:df48]) by toccata.fugue.com (Postfix) with ESMTPSA id AD46623806D4; Fri, 25 Nov 2011 12:22:42 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: multipart/alternative; boundary="Apple-Mail=_41BABD4F-92B7-4484-A307-56B52B1A4EA1"
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <97F2586F-3E18-47F3-B369-47BE7517204A@cisco.com>
Date: Fri, 25 Nov 2011 12:22:40 -0500
Message-Id: <9735297F-F9A5-4D40-BBAE-A9B5EB9FFF2A@fugue.com>
References: <CAKD1Yr3Y=EO9siQkAuZd7LtqsOT_8GswWkPOoiJEhtvnULcytw@mail.gmail.com> <4ECB98BC.8070600@riw.us> <ACDC3C9F-85D2-4AF6-AA8C-2A2E6EEDC8EE@fugue.com> <CAKD1Yr26zO0Dbco35ngWhj4W0hv_d_zJTCcbB-SSKqPpQab=ig@mail.gmail.com> <5C87A581-B2FD-4A1B-AD6B-7823279631BE@fugue.com> <CAKD1Yr3zp1Gn1P-jDVgna2ViWeQiyCaTM=hTchpJq2snPSL-hw@mail.gmail.com> <E70EE283-116C-49CD-854C-2DA20783FFD7@fugue.com> <97F2586F-3E18-47F3-B369-47BE7517204A@cisco.com>
To: Mark Townsley <townsley@cisco.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: Russ White <russw@riw.us>, homenet@ietf.org, Lorenzo Colitti <lorenzo@google.com>
Subject: Re: [homenet] Creating a security association via physical link + button
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 25 Nov 2011 17:22:46 -0000

--Apple-Mail=_41BABD4F-92B7-4484-A307-56B52B1A4EA1
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Nov 25, 2011, at 3:50 AM, Mark Townsley wrote:
> In the email I just sent, I'm making an argument for why this is not =
the case. An IGP in a homenet setting needs crypto security no more than =
DHCP, ND or mDNS would. It's just another configuration protocol within =
the home.=20

I liked the email you just sent, and agree with most of it.   However...

> Yes, this means that we need to trust L2 or physical security. But =
that's already very much the case today. If we add keys and crypto at =
every layer we are doomed before we start on usability alone.=20

As mcr pointed out, we have to make sure the thing we are talking on is =
actually an L2 link, and not an L3 link, so the key handshake you're =
talking about has to be done with some kind of 802.1x-ey protocol.   But =
you admitted that we need to be able to do this for wireless devices as =
well as wired.   If that's the case, there *has* to be a public/private =
key pair, or you might as well not bother with a crypto key at all.

But the notion that having to have a public/private key pair is onerous =
doesn't make sense anyway.  Public keys are just as easy as shared =
secrets, as long as you have space to store them. Why are we even =
debating this?


--Apple-Mail=_41BABD4F-92B7-4484-A307-56B52B1A4EA1
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div>On Nov 25, 2011, at 3:50 AM, Mark Townsley =
wrote:</div><blockquote type=3D"cite"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; font-family: Helvetica; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-align: -webkit-auto; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div>In the =
email I just sent, I'm making an argument for why this is not the case. =
An IGP in a homenet setting needs crypto security no more than DHCP, ND =
or mDNS would. It's just another configuration protocol within the =
home.&nbsp;</div></span></blockquote><div><br></div>I liked the email =
you just sent, and agree with most of it. &nbsp; =
However...</div><div><br><blockquote type=3D"cite">Yes, this means that =
we need to trust L2 or physical security. But that's already very much =
the case today. If we add keys and crypto at every layer we are doomed =
before we start on usability alone.&nbsp;</blockquote></div><br><div>As =
mcr pointed out, we have to make sure the thing we are talking on is =
actually an L2 link, and not an L3 link, so the key handshake you're =
talking about has to be done with some kind of 802.1x-ey protocol. =
&nbsp; But you admitted that we need to be able to do this for wireless =
devices as well as wired. &nbsp; If that's the case, there *has* to be a =
public/private key pair, or you might as well not bother with a crypto =
key at all.</div><div><br></div><div>But the notion that having to have =
a public/private key pair is onerous doesn't make sense anyway. =
&nbsp;Public keys are just as easy as shared secrets, as long as you =
have space to store them. Why are we even debating =
this?</div><div><br></div></body></html>=

--Apple-Mail=_41BABD4F-92B7-4484-A307-56B52B1A4EA1--

From mellon@fugue.com  Fri Nov 25 09:28:06 2011
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1919921F8548 for <homenet@ietfa.amsl.com>; Fri, 25 Nov 2011 09:28:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.033
X-Spam-Level: 
X-Spam-Status: No, score=-2.033 tagged_above=-999 required=5 tests=[AWL=0.409,  BAYES_00=-2.599, HTML_MESSAGE=0.001, SUBJECT_FUZZY_TION=0.156]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MN2n54jTby+O for <homenet@ietfa.amsl.com>; Fri, 25 Nov 2011 09:28:05 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id BCC1321F853E for <homenet@ietf.org>; Fri, 25 Nov 2011 09:28:05 -0800 (PST)
Received: from [IPv6:2001:470:1f07:1486:941f:74f9:f58d:df48] (unknown [IPv6:2001:470:1f07:1486:941f:74f9:f58d:df48]) by toccata.fugue.com (Postfix) with ESMTPSA id 0F0092380431; Fri, 25 Nov 2011 12:28:03 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: multipart/alternative; boundary="Apple-Mail=_5D9C9DE6-1765-4A1D-9ECB-DB1B509C9B63"
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <kkblj0mbs8xw8pp32w219ww6.1322224208905@email.android.com>
Date: Fri, 25 Nov 2011 12:28:01 -0500
Message-Id: <5B97FD15-7CE9-4FB8-88A4-36C4D0930BEF@fugue.com>
References: <kkblj0mbs8xw8pp32w219ww6.1322224208905@email.android.com>
To: Randy Turner <rturner@amalfisystems.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: russw@riw.us, townsley@cisco.com, homenet@ietf.org, lorenzo@google.com
Subject: Re: [homenet] Creating a security association via physical link +	button
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 25 Nov 2011 17:28:06 -0000

--Apple-Mail=_5D9C9DE6-1765-4A1D-9ECB-DB1B509C9B63
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Nov 25, 2011, at 7:30 AM, Randy Turner wrote:
> I think I agree that confidentiality of routing traffic is probably =
not an issue for Homenet - however, I do think we should consider =
integrity of routing traffic - ie, router A should "trust" that route =
updates from router B are correct.

Exactly.

> That being said, this is just an intuitive feeling regarding security =
- maybe we need someone to work on a threat analysis and what the =
implications could be to the types of applications we anticipate


Yes, I think this would be worthwhile.   I'm certainly arguing based on =
intuition at the moment.


--Apple-Mail=_5D9C9DE6-1765-4A1D-9ECB-DB1B509C9B63
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div>On Nov 25, 2011, at 7:30 AM, Randy Turner =
wrote:</div><blockquote type=3D"cite"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; font-family: Helvetica; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-align: -webkit-auto; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; ">I think I =
agree that confidentiality of routing traffic is probably not an issue =
for Homenet - however, I do think we should consider integrity of =
routing traffic - ie, router A should "trust" that route updates from =
router B are =
correct.</span></blockquote><div><br></div><div>Exactly.</div></div><div><=
br><blockquote type=3D"cite"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; font-family: Helvetica; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-align: -webkit-auto; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; ">That being =
said, this is just an intuitive feeling regarding security - maybe we =
need someone to work on a threat analysis and what the implications =
could be to the types of applications we =
anticipate</span></blockquote></div><div><br></div><div>Yes, I think =
this would be worthwhile. &nbsp; I'm certainly arguing based on =
intuition at the moment.</div><div><br></div></body></html>=

--Apple-Mail=_5D9C9DE6-1765-4A1D-9ECB-DB1B509C9B63--

From brian.e.carpenter@gmail.com  Fri Nov 25 11:12:38 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E150721F8B3A for <homenet@ietfa.amsl.com>; Fri, 25 Nov 2011 11:12:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.501
X-Spam-Level: 
X-Spam-Status: No, score=-103.501 tagged_above=-999 required=5 tests=[AWL=0.098, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DgIp7s0gv6Na for <homenet@ietfa.amsl.com>; Fri, 25 Nov 2011 11:12:38 -0800 (PST)
Received: from mail-bw0-f44.google.com (mail-bw0-f44.google.com [209.85.214.44]) by ietfa.amsl.com (Postfix) with ESMTP id CC06C21F86A4 for <homenet@ietf.org>; Fri, 25 Nov 2011 11:12:37 -0800 (PST)
Received: by bkbzv15 with SMTP id zv15so5006595bkb.31 for <homenet@ietf.org>; Fri, 25 Nov 2011 11:12:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=mbLlm6GYZmSNF3H08bHdjSBWwfF7JeNXOwvnjoh+GRI=; b=cjfkvp1MhBeDvIyBKR7mDI0UUYke8+UOP9ooFtitb3GOoTd5wsGTrKt4v14fzAMU0r BX9TyjfGGzVCt7K2V263EVjKXorio0Wk1xbWgenq5yZ2LRhaiFfWW7XuwMf2fMkT12bd NfiffZ1qtin8UP0nLesBoGS/zBxZKYStSXUpo=
Received: by 10.204.152.196 with SMTP id h4mr34773253bkw.1.1322248356859; Fri, 25 Nov 2011 11:12:36 -0800 (PST)
Received: from [10.1.1.4] ([121.98.251.219]) by mx.google.com with ESMTPS id l18sm29426788fab.9.2011.11.25.11.12.34 (version=SSLv3 cipher=OTHER); Fri, 25 Nov 2011 11:12:35 -0800 (PST)
Message-ID: <4ECFE895.3080209@gmail.com>
Date: Sat, 26 Nov 2011 08:12:21 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Teco Boot <teco@inf-net.nl>
References: <DCC302FAA9FE5F4BBA4DCAD4656937791452BBC0CC@PRVPEXVS03.corp.twcable.com>	<CABONVQbMsY6MF_8q44XqGmdOMS6Odn+CjBEttaEs9rhmknwRxg@mail.gmail.com><4ECCAFC3.5060903@globis.net><DCC302FAA9FE5F4BBA4DCAD4656937791452BBC498@PRVPEXVS03.corp.twcable.com>	<4ECD3608.5020502@globis.net>	<BDF2740C082F6942820D95BAEB9E1A846E5B05@XMB-AMS-108.cisco.com>	<B16D09C6-66AA-4FCC-9A3A-5CB2C2921523@nominet.org.uk> <5A35BCB0-B7B6-41FE-BA6E-2778D5D479AC@inf-net.nl>
In-Reply-To: <5A35BCB0-B7B6-41FE-BA6E-2778D5D479AC@inf-net.nl>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: homenet@ietf.org
Subject: Re: [homenet] other routing options
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 25 Nov 2011 19:12:39 -0000

On 2011-11-25 20:47, Teco Boot wrote:
...
> IS-IS is not my favorite. Also, I know almost nothing about TRILL. But I think these should be considered. Don't expect a draft from me.

TRILL is not an IP routing protocol. It's a layer 2 bridging protocol more
complicated than the spanning tree, and seems completely unnecessary for
the small size of bridged networks to be expected in homenets.

   Brian

From joelja@bogus.com  Fri Nov 25 11:59:58 2011
Return-Path: <joelja@bogus.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF39221F8B42 for <homenet@ietfa.amsl.com>; Fri, 25 Nov 2011 11:59:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.524
X-Spam-Level: 
X-Spam-Status: No, score=-102.524 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5BTIvnket2JM for <homenet@ietfa.amsl.com>; Fri, 25 Nov 2011 11:59:58 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 60F1421F8B3F for <homenet@ietf.org>; Fri, 25 Nov 2011 11:59:58 -0800 (PST)
Received: from Zorch.local (c-76-115-174-157.hsd1.wa.comcast.net [76.115.174.157]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id pAPJxqb6075741 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Fri, 25 Nov 2011 19:59:52 GMT (envelope-from joelja@bogus.com)
Message-ID: <4ECFF3B3.5050407@bogus.com>
Date: Fri, 25 Nov 2011 11:59:47 -0800
From: Joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Ray Hunter <v6ops@globis.net>
References: <DCC302FAA9FE5F4BBA4DCAD4656937791452BBC0CC@PRVPEXVS03.corp.twcable.com>	<CABONVQbMsY6MF_8q44XqGmdOMS6Odn+CjBEttaEs9rhmknwRxg@mail.gmail.com> <4ECCAFC3.5060903@globis.net> <DCC302FAA9FE5F4BBA4DCAD4656937791452BBC498@PRVPEXVS03.corp.twcable.com> <4ECD3608.5020502@globis.net>
In-Reply-To: <4ECD3608.5020502@globis.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Fri, 25 Nov 2011 19:59:54 +0000 (UTC)
Cc: "Howard, Lee" <lee.howard@twcable.com>, Laurent Toutain <Laurent.Toutain@telecom-bretagne.eu>, "homenet@ietf.org" <homenet@ietf.org>
Subject: Re: [homenet] other routing options
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 25 Nov 2011 19:59:59 -0000

On 11/23/11 10:06 , Ray Hunter wrote:
>>> > IMHO increasing use of (overlapping) (low power) wireless networks in Homenet will only make
>>> > count to infinity type problems more common, as marginal adjacencies come and go.
>>>     
>>
>> You mean 6lowpan type networks?  I thought we had consensus to draw a circle around them and
>> say, "put a device between that network and this."
>>
>>   
> I agree on 6LoWPAN: it has a clear gateway router, it's own routing
> protocol, and should not be expected to provide an inter-Homenet link.
> 
> But you can still have various flavors of WiFi that could be acting as a
> (marginal) inter-router link, in parallel with copper.
> What about those? Are they also stub networks that only service end
> nodes? How do you know? How do you avoid 2 routers forming an OSPF/RIPng
> adjacency if it's a single SSID just within wireless range of each
> other? That might be exactly what you want in some cases.
>>> > What about multicast support for streaming video to my iDevice as I walk from the lounge to
>>> > the pool? AV will likely be a major homenet application. OSPF => MOSPF? IPng => DVMRP?
>>> > Or should that use unicast + mobile IPv6?
>>>     
>>
>> Streaming video != multicast.  I don't think we've had any discussion of multicast, except in
>> the context of mDNS.  I don't need it in the home.  Do you?
>>   
> That was exactly my question. As a consumer I'd like video distributed
> around my home available to mobile devices: I don't really care how it's
> transported. The video may well arrive into the home via multicast over
> cable via DOCSIS. The set top box is in the living room but my TV is in
> the bedroom. Do we expect people to run the cable TV network to every
> room to separate set top boxes with their own decryption cards and keep
> this outside of Homenet? Do we expect AV manufacturers to always unicast
> video within the Homenet? e.g. if I want my camera with my own copyright
> content to play on a remote system? Or should we discuss whether the
> choice of unicast routing protocol has a knock on effect to multicast
> routing?

multicast as frequently deployed on wireless networks tends to be
terribly expensive, e.g. if it's transmitted at the lowest available rate.

within the home, at least with fairly high rate wireless devices you'll
probably find it more scalable to unicast it.

> I'd like to keep things simple too, but I think it's an important
> scoping question to get clear consensus on.
> 
> regards,
> RayH
> 
> 
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet


From rturner@amalfisystems.com  Fri Nov 25 12:15:30 2011
Return-Path: <rturner@amalfisystems.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17DBE21F8B57 for <homenet@ietfa.amsl.com>; Fri, 25 Nov 2011 12:15:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.842
X-Spam-Level: 
X-Spam-Status: No, score=-1.842 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_46=0.6, SUBJECT_FUZZY_TION=0.156]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zhOuP64V86bb for <homenet@ietfa.amsl.com>; Fri, 25 Nov 2011 12:15:29 -0800 (PST)
Received: from omr7.networksolutionsemail.com (omr7.networksolutionsemail.com [205.178.146.57]) by ietfa.amsl.com (Postfix) with ESMTP id 0341021F8B59 for <homenet@ietf.org>; Fri, 25 Nov 2011 12:15:28 -0800 (PST)
Received: from cm-omr5 (mail.networksolutionsemail.com [205.178.146.50]) by omr7.networksolutionsemail.com (8.13.8/8.13.8) with ESMTP id pAPKFPbe028777 for <homenet@ietf.org>; Fri, 25 Nov 2011 15:15:28 -0500
Authentication-Results: cm-omr5 smtp.user=rturner@amalfisystems.com; auth=pass (CRAM-MD5)
X-Authenticated-UID: rturner@amalfisystems.com
Received: from [75.217.224.201] ([75.217.224.201:55884] helo=201.sub-75-217-224.myvzw.com) by cm-omr5 (envelope-from <rturner@amalfisystems.com>) (ecelerity 2.2.2.41 r(31179/31189)) with ESMTPSA (cipher=AES128-SHA)  id 07/4A-04879-C57FFCE4; Fri, 25 Nov 2011 15:15:25 -0500
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: multipart/alternative; boundary="Apple-Mail=_B06308B6-7EF4-4A0B-A4A5-5DEBA05F7E0A"
From: Randy Turner <rturner@amalfisystems.com>
In-Reply-To: <9956D114-4D15-4F60-A444-745857F12816@cisco.com>
Date: Fri, 25 Nov 2011 12:15:16 -0800
Message-Id: <B251A185-8440-40C0-8D85-F376A9D758D6@amalfisystems.com>
References: <CAKD1Yr3Y=EO9siQkAuZd7LtqsOT_8GswWkPOoiJEhtvnULcytw@mail.gmail.com> <4ECB98BC.8070600@riw.us> <ACDC3C9F-85D2-4AF6-AA8C-2A2E6EEDC8EE@fugue.com> <CAKD1Yr26zO0Dbco35ngWhj4W0hv_d_zJTCcbB-SSKqPpQab=ig@mail.gmail.com> <5C87A581-B2FD-4A1B-AD6B-7823279631BE@fugue.com> <CAKD1Yr3zp1Gn1P-jDVgna2ViWeQiyCaTM=hTchpJq2snPSL-hw@mail.gmail.com> <9956D114-4D15-4F60-A444-745857F12816@cisco.com>
To: Mark Townsley <townsley@cisco.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: homenet@ietf.org
Subject: Re: [homenet] Creating a security association via physical link + button
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 25 Nov 2011 20:15:30 -0000

--Apple-Mail=_B06308B6-7EF4-4A0B-A4A5-5DEBA05F7E0A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

> "Similarly, a wired broadband or 3G/LTE wireless connection to an ISP =
router in the neighborhood has its own authentication and policy =
enforcement happening at L2. "

I'm curious if we want to "assume" a particular type of broadband =
connection is in use, or do we want the Homenet solution to be =
"broadband-agnostic", and supply a robust solution without any knowledge =
of ISP/NSP connectivity method?  If we make no assumptions, then our =
work is harder - if we "assume" certain types of links in place, then we =
may or may not fail in certain Homenet connectivity scenarios where our =
assumptions are incorrect, but the scope of our work will be less.

Randy


On Nov 25, 2011, at 12:43 AM, Mark Townsley wrote:

>=20
> Before we decide that we must have an IGP, that it must be =
cryptographically secured, and that we have to tackle key distribution =
for it, I'd like to take a step or two back from the routing protocol =
part of the equation.
>=20
> First things first, we have to detect that there is a device present, =
whether it is a router or not, and if so what kind of router to router =
border we have on that link so that we can apply a policy. If that =
policy allows sending and receiving of addressing and routing =
information, from the perspective of the routing protocol it has every =
thing it needs to start sending IGP packets in the clear on that link. =
In terms of usability, the homenet cannot afford crypto security or key =
exchange at every layer. I think we must inherently trust security from =
layer 2 or physical, just like we do today between routers and hosts (or =
nat-routers and nat-routers for IPv4) in the home.=20
>=20
> In practical terms, I think this means that if two routers are =
connected with a physical link, that link should be trusted enough to =
send packets, in the clear, which can at least identify what kind of =
router to router link this is (e.g., local, ISP, etc.). The same applies =
if two routers are connected over a secured wireless L2 link.  =
Similarly, a wired broadband or 3G/LTE wireless connection to an ISP =
router in the neighborhood has its own authentication and policy =
enforcement happening at L2.=20
>=20
> In terms of UI, if one of those two routers is actually a PC or phone, =
we shouldn't worry about the "pairing" issues much as there is enough =
user interaction to sort that out (I do think that the state of the art =
could be improved here, but that's for the UI wizards make better, not =
protocol hacks like us). The most problematic real-world case today that =
comes to mind would be in how to establish homenet routers that are =
connected via a wireless link should be considered part of the same =
network. A link+button might be the best way to make this happen for =
some routers, but others might prefer a UI from a PC (e.g., the "airport =
utility") with passwords. I think the furthest we can go here is to say =
that such a link must exist, and what the minimum level of packet =
exchange should be allowed before discovering what type of =
router-to-router link is present.=20
>=20
> - Mark
>=20
>=20
>=20
> On Nov 25, 2011, at 1:46 AM, Lorenzo Colitti wrote:
>=20
>> On Fri, Nov 25, 2011 at 01:27, Ted Lemon <mellon@fugue.com> wrote:
>>> If one is a member of a homenet and an ISP connection already, and =
one has a blank config, then you might assume that  the one with the =
blank config should join the existing homenet. What if they both have a =
config on them? What if you're actually merging two separate networks?
>>=20
>> I think that's the idea.   The user is saying "merge the two =
networks" in this case.
>>=20
>> Ok, so it would seem to me that to support that case then we need to =
either a) support multiple simultaneous keys in the IGP or b) provide a =
mechanism to tell a number of homenet routers that "the key to the IGP =
is changing". Both are non-trivial. Any other ideas?
>> _______________________________________________
>> homenet mailing list
>> homenet@ietf.org
>> https://www.ietf.org/mailman/listinfo/homenet
>=20
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet


--Apple-Mail=_B06308B6-7EF4-4A0B-A4A5-5DEBA05F7E0A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><blockquote type=3D"cite"><div style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div>"Similarly, a wired broadband or 3G/LTE wireless connection to an =
ISP router in the neighborhood has its own authentication and policy =
enforcement happening at L2. =
"</div></div></blockquote><div><br></div><div>I'm curious if we want to =
"assume" a particular type of broadband connection is in use, or do we =
want the Homenet solution to be "broadband-agnostic", and supply a =
robust solution without any knowledge of ISP/NSP connectivity method? =
&nbsp;If we make no assumptions, then our work is harder - if we =
"assume" certain types of links in place, then we may or may not fail in =
certain Homenet connectivity scenarios where our assumptions are =
incorrect, but the scope of our work will be =
less.</div><div><br></div><div>Randy</div><div><br></div><br><div><div>On =
Nov 25, 2011, at 12:43 AM, Mark Townsley wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><br></div><div>Before we =
decide that we must have an IGP, that it must be cryptographically =
secured, and that we have to tackle key distribution for it, I'd like to =
take a step or two back from the routing protocol part of the =
equation.</div><div><br></div><div>First things first, we have to detect =
that there is a device present, whether it is a router or not, and if so =
what kind of router to router border we have on that link so that we can =
apply a policy. If that policy allows sending and receiving of =
addressing and routing information, from the perspective of the routing =
protocol it has every thing it needs to start sending IGP packets in the =
clear on that link. In terms of usability, the homenet cannot afford =
crypto security or key exchange at every layer. I think we must =
inherently trust security from layer 2 or physical, just like we do =
today between routers and hosts (or nat-routers and nat-routers for =
IPv4)&nbsp;in the home.&nbsp;</div><div><br></div><div>In practical =
terms, I think this means that if two routers are connected with a =
physical link, that link should be trusted enough to send packets, in =
the clear, which can at least identify what kind of router to router =
link this is (e.g., local, ISP, etc.). The same applies if two routers =
are connected over a secured wireless L2 link. &nbsp;Similarly, a wired =
broadband or 3G/LTE wireless connection to an ISP router in the =
neighborhood has its own authentication and policy enforcement happening =
at L2.&nbsp;</div><div><br></div><div>In terms of UI, if one of those =
two routers is actually a PC or phone, we shouldn't worry about the =
"pairing" issues much as there is enough user interaction to sort that =
out (I do think that the state of the art could be improved here, but =
that's for the UI wizards make better, not protocol hacks like =
us).&nbsp;The most problematic real-world case today that comes to mind =
would be in how to establish homenet routers that are connected via a =
wireless link should be considered part of the same network. A =
link+button might be the best way to make this happen for some routers, =
but others might prefer a UI from a PC (e.g., the "airport utility") =
with passwords. I think the furthest we can go here is to say that such =
a link must exist, and what the minimum level of packet exchange should =
be allowed before discovering what type of router-to-router link is =
present.&nbsp;</div><div><br></div><div>- =
Mark</div><div><br></div><div><br></div><br><div><div>On Nov 25, 2011, =
at 1:46 AM, Lorenzo Colitti wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div =
class=3D"gmail_quote">On Fri, Nov 25, 2011 at 01:27, Ted Lemon <span =
dir=3D"ltr">&lt;<a =
href=3D"mailto:mellon@fugue.com">mellon@fugue.com</a>&gt;</span> =
wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex;">

<div style=3D"word-wrap:break-word"><div class=3D"im"><div><blockquote =
type=3D"cite"><span =
style=3D"border-collapse:separate;font-family:Helvetica;font-style:normal;=
font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:n=
ormal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-sp=
ace:normal;word-spacing:0px;font-size:medium">If one is a member of a =
homenet and an ISP connection already, and one has a blank config, then =
you might assume that &nbsp;the one with the blank config should join =
the existing homenet. What if they both have a config on them? What if =
you're actually merging two separate networks?</span></blockquote>

</div></div><div>I think that's the idea. &nbsp; The user is saying =
"merge the two networks" in this =
case.</div></div></blockquote><div><br></div><div>Ok, so it would seem =
to me that to support that case then we need to either a) support =
multiple simultaneous keys in the IGP or b) provide a mechanism to tell =
a number of homenet routers that "the key to the IGP is changing". Both =
are non-trivial. Any other ideas?</div>

</div>
_______________________________________________<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">https://www.ietf.or=
g/mailman/listinfo/homenet</a><br></blockquote></div><br></div>___________=
____________________________________<br>homenet mailing list<br><a =
href=3D"mailto:homenet@ietf.org">homenet@ietf.org</a><br>https://www.ietf.=
org/mailman/listinfo/homenet<br></blockquote></div><br></body></html>=

--Apple-Mail=_B06308B6-7EF4-4A0B-A4A5-5DEBA05F7E0A--

From townsley@cisco.com  Fri Nov 25 17:15:50 2011
Return-Path: <townsley@cisco.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDBF121F8AC9 for <homenet@ietfa.amsl.com>; Fri, 25 Nov 2011 17:15:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.406
X-Spam-Level: 
X-Spam-Status: No, score=-10.406 tagged_above=-999 required=5 tests=[AWL=0.036, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8, SUBJECT_FUZZY_TION=0.156]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aiaDzXozs8dD for <homenet@ietfa.amsl.com>; Fri, 25 Nov 2011 17:15:50 -0800 (PST)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id 8E94421F8AB8 for <homenet@ietf.org>; Fri, 25 Nov 2011 17:15:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=townsley@cisco.com; l=6119; q=dns/txt; s=iport; t=1322270149; x=1323479749; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to; bh=2R210SPj16uMREUEDlQznLsta+/vgyGyXkNV6fW/nv4=; b=ZS9h/hmY7U8vhkiW9JRNIxA8M+Grkw5u4sCLXZMtU8Ld5jXJwo3FMcUQ 9TAAOH2VAqYrdOdmFqE+qp0o9mrI4FndOsu7ZNU2Koy4K/cPr+e4N5sds B3CYGMFo30gkjNzUMnUBMzcz1iYqGb6BdJkscILumu6vnXmzbRCEuykBq g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EADw90E6Q/khM/2dsb2JhbABEqwCBBYFyAQEBAwEBAQEPAVsLBQsLDgouJzAGEyKHYwiYCAGeBgSJf2MElEqSDA
X-IronPort-AV: E=Sophos;i="4.69,574,1315180800"; d="scan'208,217";a="60432688"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-2.cisco.com with ESMTP; 26 Nov 2011 01:15:48 +0000
Received: from ams-townsley-8712.cisco.com (ams-townsley-8712.cisco.com [10.55.233.227]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id pAQ1Fl8a000747; Sat, 26 Nov 2011 01:15:47 GMT
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-25-365563922
From: Mark Townsley <townsley@cisco.com>
In-Reply-To: <9735297F-F9A5-4D40-BBAE-A9B5EB9FFF2A@fugue.com>
Date: Sat, 26 Nov 2011 02:15:47 +0100
Message-Id: <837D261D-6D78-47EF-B0B1-25CFF80D7F64@cisco.com>
References: <CAKD1Yr3Y=EO9siQkAuZd7LtqsOT_8GswWkPOoiJEhtvnULcytw@mail.gmail.com> <4ECB98BC.8070600@riw.us> <ACDC3C9F-85D2-4AF6-AA8C-2A2E6EEDC8EE@fugue.com> <CAKD1Yr26zO0Dbco35ngWhj4W0hv_d_zJTCcbB-SSKqPpQab=ig@mail.gmail.com> <5C87A581-B2FD-4A1B-AD6B-7823279631BE@fugue.com> <CAKD1Yr3zp1Gn1P-jDVgna2ViWeQiyCaTM=hTchpJq2snPSL-hw@mail.gmail.com> <E70EE283-116C-49CD-854C-2DA20783FFD7@fugue.com> <97F2586F-3E18-47F3-B369-47BE7517204A@cisco.com> <9735297F-F9A5-4D40-BBAE-A9B5EB9FFF2A@fugue.com>
To: Ted Lemon <mellon@fugue.com>
X-Mailer: Apple Mail (2.1084)
Cc: Russ White <russw@riw.us>, homenet@ietf.org, Lorenzo Colitti <lorenzo@google.com>
Subject: Re: [homenet] Creating a security association via physical link + button
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 26 Nov 2011 01:15:51 -0000

--Apple-Mail-25-365563922
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Nov 25, 2011, at 6:22 PM, Ted Lemon wrote:

> On Nov 25, 2011, at 3:50 AM, Mark Townsley wrote:
>> In the email I just sent, I'm making an argument for why this is not =
the case. An IGP in a homenet setting needs crypto security no more than =
DHCP, ND or mDNS would. It's just another configuration protocol within =
the home.=20
>=20
> I liked the email you just sent, and agree with most of it.   =
However...
>=20
>> Yes, this means that we need to trust L2 or physical security. But =
that's already very much the case today. If we add keys and crypto at =
every layer we are doomed before we start on usability alone.=20
>=20
> As mcr pointed out, we have to make sure the thing we are talking on =
is actually an L2 link, and not an L3 link, so the key handshake you're =
talking about has to be done with some kind of 802.1x-ey protocol.   But =
you admitted that we need to be able to do this for wireless devices as =
well as wired. =20

Actually, I suggested that wired wouldn't need any key handshake. =
Wireless would, and such handshakes require UI. The UI is the problem if =
there are two devices that are not used to having any serious UI. I'm =
not sure I know how to solve that, but I'm not sure it's our problem to =
solve either.=20

> If that's the case, there *has* to be a public/private key pair, or =
you might as well not bother with a crypto key at all.

What's the common case at L2 in homes today?

> But the notion that having to have a public/private key pair is =
onerous doesn't make sense anyway.  Public keys are just as easy as =
shared secrets, as long as you have space to store them. Why are we even =
debating this?

You are debating the kind of keys to use, I'm not. I'm saying that once =
you need any more keys that we already have at L2, we've made the =
problem harder than it needs to be.=20

- Mark

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


--Apple-Mail-25-365563922
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On Nov 25, 2011, at 6:22 PM, Ted Lemon wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><div>On Nov 25, 2011, at =
3:50 AM, Mark Townsley wrote:</div><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Helvetica; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div>In the =
email I just sent, I'm making an argument for why this is not the case. =
An IGP in a homenet setting needs crypto security no more than DHCP, ND =
or mDNS would. It's just another configuration protocol within the =
home.&nbsp;</div></span></blockquote><div><br></div>I liked the email =
you just sent, and agree with most of it. &nbsp; =
However...</div><div><br><blockquote type=3D"cite">Yes, this means that =
we need to trust L2 or physical security. But that's already very much =
the case today. If we add keys and crypto at every layer we are doomed =
before we start on usability alone.&nbsp;</blockquote></div><br><div>As =
mcr pointed out, we have to make sure the thing we are talking on is =
actually an L2 link, and not an L3 link, so the key handshake you're =
talking about has to be done with some kind of 802.1x-ey protocol. =
&nbsp; But you admitted that we need to be able to do this for wireless =
devices as well as wired. =
&nbsp;</div></div></blockquote><div><br></div><div>Actually, I suggested =
that wired wouldn't need any key handshake. Wireless would, and such =
handshakes require UI. The UI is the problem if there are two devices =
that are not used to having any serious UI. I'm not sure I know how to =
solve that, but I'm not sure it's our problem to solve =
either.&nbsp;</div><br><blockquote type=3D"cite"><div style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space; "><div> If that's the case, there *has* to be a =
public/private key pair, or you might as well not bother with a crypto =
key at all.</div></div></blockquote><div><br></div><div>What's the =
common case at L2 in homes today?</div><br><blockquote type=3D"cite"><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div>But the notion that having =
to have a public/private key pair is onerous doesn't make sense anyway. =
&nbsp;Public keys are just as easy as shared secrets, as long as you =
have space to store them. Why are we even debating =
this?</div></div></blockquote><div><br></div><div>You are debating the =
kind of keys to use, I'm not. I'm saying that once you need any more =
keys that we already have at L2, we've made the problem harder than it =
needs to be.&nbsp;</div><div><br></div><div>- Mark</div><br><blockquote =
type=3D"cite"><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space; =
"><div><br></div></div>_______________________________________________<br>=
homenet mailing list<br><a =
href=3D"mailto:homenet@ietf.org">homenet@ietf.org</a><br>https://www.ietf.=
org/mailman/listinfo/homenet<br></blockquote></div><br></body></html>=

--Apple-Mail-25-365563922--

From townsley@cisco.com  Fri Nov 25 17:17:39 2011
Return-Path: <townsley@cisco.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 84B7B21F8B15 for <homenet@ietfa.amsl.com>; Fri, 25 Nov 2011 17:17:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.413
X-Spam-Level: 
X-Spam-Status: No, score=-8.413 tagged_above=-999 required=5 tests=[AWL=-1.971, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, SUBJECT_FUZZY_TION=0.156]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 65xZAJNJEfmd for <homenet@ietfa.amsl.com>; Fri, 25 Nov 2011 17:17:39 -0800 (PST)
Received: from ams-iport-4.cisco.com (ams-iport-4.cisco.com [144.254.224.147]) by ietfa.amsl.com (Postfix) with ESMTP id 945BC21F8B13 for <homenet@ietf.org>; Fri, 25 Nov 2011 17:17:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=townsley@cisco.com; l=4606; q=dns/txt; s=iport; t=1322270258; x=1323479858; h=subject:mime-version:from:in-reply-to:date:cc:message-id: references:to; bh=PCyVI/BWg5n5MKCB1SADT8wooEoDgeYpAuqoRw69Fds=; b=FH21a27XW4dcXzWS/qJLxm/xRM04Xe7r0NT1v6ZgPLAgz8NoFNA0lvE+ jMC9wKfc6G/ljKTZijcIq3M8pYnpauh7TkzwmQfJq31p8USoxyHGD3fLt u8agDuqOEbkFQuTzem59IlUG2UUg4mixYKeVUo9ulYRMX56107f2/MHhK I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av4EAMI90E6Q/khL/2dsb2JhbABEqwCBBYFyAQEBAwEBAQEPAVsLBQsLBAoKLicwBhMbB4djCJgIAZ4GBIl/YwSUSpIM
X-IronPort-AV: E=Sophos;i="4.69,574,1315180800"; d="scan'208,217";a="3900668"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by ams-iport-4.cisco.com with ESMTP; 26 Nov 2011 01:17:37 +0000
Received: from ams-townsley-8712.cisco.com (ams-townsley-8712.cisco.com [10.55.233.227]) by ams-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id pAQ1Hb80000463; Sat, 26 Nov 2011 01:17:37 GMT
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-26-365673442
From: Mark Townsley <townsley@cisco.com>
In-Reply-To: <5B97FD15-7CE9-4FB8-88A4-36C4D0930BEF@fugue.com>
Date: Sat, 26 Nov 2011 02:17:36 +0100
Message-Id: <A23A4334-44A8-45ED-B3CB-B601C0021BF4@cisco.com>
References: <kkblj0mbs8xw8pp32w219ww6.1322224208905@email.android.com> <5B97FD15-7CE9-4FB8-88A4-36C4D0930BEF@fugue.com>
To: Ted Lemon <mellon@fugue.com>
X-Mailer: Apple Mail (2.1084)
Cc: russw@riw.us, Randy Turner <rturner@amalfisystems.com>, homenet@ietf.org, lorenzo@google.com
Subject: Re: [homenet] Creating a security association via physical link + button
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 26 Nov 2011 01:17:39 -0000

--Apple-Mail-26-365673442
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Nov 25, 2011, at 6:28 PM, Ted Lemon wrote:

> On Nov 25, 2011, at 7:30 AM, Randy Turner wrote:
>> I think I agree that confidentiality of routing traffic is probably =
not an issue for Homenet - however, I do think we should consider =
integrity of routing traffic - ie, router A should "trust" that route =
updates from router B are correct.
>=20
> Exactly.

I see no difference really between the difficulty between an =
integrity-only solution and a confidentiality solution. Both require =
keys. It's the keys that are the real problem, not the work done on the =
packets.

And, yes, key exchange being hard is based on a certain amount of =
intuition for my part as well.=20

- Mark

>=20
>> That being said, this is just an intuitive feeling regarding security =
- maybe we need someone to work on a threat analysis and what the =
implications could be to the types of applications we anticipate
>=20
>=20
> Yes, I think this would be worthwhile.   I'm certainly arguing based =
on intuition at the moment.
>=20
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet


--Apple-Mail-26-365673442
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><br><div><div>On Nov 25, 2011, at 6:28 PM, Ted Lemon wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><div>On Nov 25, 2011, at =
7:30 AM, Randy Turner wrote:</div><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Helvetica; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; ">I think I =
agree that confidentiality of routing traffic is probably not an issue =
for Homenet - however, I do think we should consider integrity of =
routing traffic - ie, router A should "trust" that route updates from =
router B are =
correct.</span></blockquote><div><br></div><div>Exactly.</div></div></div>=
</blockquote><div><br></div><div>I see no difference really between the =
difficulty between an integrity-only solution and a confidentiality =
solution. Both require keys. It's the keys that are the real problem, =
not the work done on the packets.</div><div><br></div><div>And, yes, key =
exchange being hard is based on a certain amount of intuition for my =
part as well.&nbsp;</div><div><br></div><div>- Mark</div><br><blockquote =
type=3D"cite"><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space; "><div><br><blockquote =
type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-collapse: =
separate; font-family: Helvetica; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; ">That being =
said, this is just an intuitive feeling regarding security - maybe we =
need someone to work on a threat analysis and what the implications =
could be to the types of applications we =
anticipate</span></blockquote></div><div><br></div><div>Yes, I think =
this would be worthwhile. &nbsp; I'm certainly arguing based on =
intuition at the =
moment.</div><div><br></div></div>________________________________________=
_______<br>homenet mailing list<br><a =
href=3D"mailto:homenet@ietf.org">homenet@ietf.org</a><br>https://www.ietf.=
org/mailman/listinfo/homenet<br></blockquote></div><br></body></html>=

--Apple-Mail-26-365673442--

From hansliu@gmail.com  Fri Nov 25 17:53:10 2011
Return-Path: <hansliu@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1767421F8500 for <homenet@ietfa.amsl.com>; Fri, 25 Nov 2011 17:53:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.408
X-Spam-Level: 
X-Spam-Status: No, score=-3.408 tagged_above=-999 required=5 tests=[AWL=0.035,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SUBJECT_FUZZY_TION=0.156]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KHLbhRrPwJUu for <homenet@ietfa.amsl.com>; Fri, 25 Nov 2011 17:53:09 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 97E5921F84FC for <homenet@ietf.org>; Fri, 25 Nov 2011 17:53:09 -0800 (PST)
Received: by iaeo4 with SMTP id o4so6367624iae.31 for <homenet@ietf.org>; Fri, 25 Nov 2011 17:53:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=/QVLsWy3sFK0XegcpvstSOamJXykWKgWKNo786fRz3k=; b=saR0e2VSfvAgz4eURWqlwQATlVg86n5Ec8Mam5gIsE/ipwz94EnRtmIzyypZ9d3XA4 Y0o3+VKcnXRVxNQ4wLczlQWvIDEUDyJZyh7JFHYsV9YTeU7zs2ud3qcaPI2rhVJF+19S x5x0LuJmWQj66zXrJ566D/sZgGy++ZWfpX59Y=
MIME-Version: 1.0
Received: by 10.50.189.231 with SMTP id gl7mr42529650igc.44.1322272389276; Fri, 25 Nov 2011 17:53:09 -0800 (PST)
Received: by 10.231.172.71 with HTTP; Fri, 25 Nov 2011 17:53:09 -0800 (PST)
In-Reply-To: <837D261D-6D78-47EF-B0B1-25CFF80D7F64@cisco.com>
References: <CAKD1Yr3Y=EO9siQkAuZd7LtqsOT_8GswWkPOoiJEhtvnULcytw@mail.gmail.com> <4ECB98BC.8070600@riw.us> <ACDC3C9F-85D2-4AF6-AA8C-2A2E6EEDC8EE@fugue.com> <CAKD1Yr26zO0Dbco35ngWhj4W0hv_d_zJTCcbB-SSKqPpQab=ig@mail.gmail.com> <5C87A581-B2FD-4A1B-AD6B-7823279631BE@fugue.com> <CAKD1Yr3zp1Gn1P-jDVgna2ViWeQiyCaTM=hTchpJq2snPSL-hw@mail.gmail.com> <E70EE283-116C-49CD-854C-2DA20783FFD7@fugue.com> <97F2586F-3E18-47F3-B369-47BE7517204A@cisco.com> <9735297F-F9A5-4D40-BBAE-A9B5EB9FFF2A@fugue.com> <837D261D-6D78-47EF-B0B1-25CFF80D7F64@cisco.com>
Date: Sat, 26 Nov 2011 09:53:09 +0800
Message-ID: <CAHEOdgtuMdA84uh477gcSq_4tqJqj-yfWy4Bto+gq=6ZfbyBpQ@mail.gmail.com>
From: Hans Liu <hansliu@gmail.com>
To: Mark Townsley <townsley@cisco.com>
Content-Type: text/plain; charset=UTF-8
Cc: Russ White <russw@riw.us>, homenet@ietf.org, Ted Lemon <mellon@fugue.com>, Lorenzo Colitti <lorenzo@google.com>
Subject: Re: [homenet] Creating a security association via physical link + button
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 26 Nov 2011 01:53:10 -0000

Mark,

> Actually, I suggested that wired wouldn't need any key handshake. Wireless
> would, and such handshakes require UI. The UI is the problem if there are
> two devices that are not used to having any serious UI. I'm not sure I know
> how to solve that, but I'm not sure it's our problem to solve either.
>

Take Wi-Fi for example, WPS PBC requires no UI. WPS PIN.

Hans

From hansliu@gmail.com  Fri Nov 25 18:02:52 2011
Return-Path: <hansliu@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0917A21F8B16 for <homenet@ietfa.amsl.com>; Fri, 25 Nov 2011 18:02:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.412
X-Spam-Level: 
X-Spam-Status: No, score=-3.412 tagged_above=-999 required=5 tests=[AWL=0.031,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, SUBJECT_FUZZY_TION=0.156]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aktCPse2yqie for <homenet@ietfa.amsl.com>; Fri, 25 Nov 2011 18:02:51 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 869B321F8B13 for <homenet@ietf.org>; Fri, 25 Nov 2011 18:02:51 -0800 (PST)
Received: by iaeo4 with SMTP id o4so6379184iae.31 for <homenet@ietf.org>; Fri, 25 Nov 2011 18:02:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=408xEL56Okh9vEA16oyOtGQCyeoJVZRAD9xQ8nVeCjk=; b=Ft8NjJl4PxzDqusfQk+/l8YRYbbMvwqHm6l8PERBZnDCoZS4+EfLUYZ6K37r+q9XsL 0ae+bFNBoK9yfTSXLCgGrQvKvI3XEFQL9ck6v6z/gLYCXarbEF68N5mP7WVyUhbDTXfY SqJI49jY2HEsQ7oUgjZybwbkIZdfQTq2GHZmA=
MIME-Version: 1.0
Received: by 10.231.73.139 with SMTP id q11mr626904ibj.97.1322272971113; Fri, 25 Nov 2011 18:02:51 -0800 (PST)
Received: by 10.231.172.71 with HTTP; Fri, 25 Nov 2011 18:02:50 -0800 (PST)
In-Reply-To: <CAHEOdgtuMdA84uh477gcSq_4tqJqj-yfWy4Bto+gq=6ZfbyBpQ@mail.gmail.com>
References: <CAKD1Yr3Y=EO9siQkAuZd7LtqsOT_8GswWkPOoiJEhtvnULcytw@mail.gmail.com> <4ECB98BC.8070600@riw.us> <ACDC3C9F-85D2-4AF6-AA8C-2A2E6EEDC8EE@fugue.com> <CAKD1Yr26zO0Dbco35ngWhj4W0hv_d_zJTCcbB-SSKqPpQab=ig@mail.gmail.com> <5C87A581-B2FD-4A1B-AD6B-7823279631BE@fugue.com> <CAKD1Yr3zp1Gn1P-jDVgna2ViWeQiyCaTM=hTchpJq2snPSL-hw@mail.gmail.com> <E70EE283-116C-49CD-854C-2DA20783FFD7@fugue.com> <97F2586F-3E18-47F3-B369-47BE7517204A@cisco.com> <9735297F-F9A5-4D40-BBAE-A9B5EB9FFF2A@fugue.com> <837D261D-6D78-47EF-B0B1-25CFF80D7F64@cisco.com> <CAHEOdgtuMdA84uh477gcSq_4tqJqj-yfWy4Bto+gq=6ZfbyBpQ@mail.gmail.com>
Date: Sat, 26 Nov 2011 10:02:50 +0800
Message-ID: <CAHEOdgvrtGPb4=hGYy08=nfcgGw0n1V_rs3jDOu1QXmY=AoRkA@mail.gmail.com>
From: Hans Liu <hansliu@gmail.com>
To: Mark Townsley <townsley@cisco.com>
Content-Type: text/plain; charset=UTF-8
Cc: Russ White <russw@riw.us>, homenet@ietf.org, Ted Lemon <mellon@fugue.com>, Lorenzo Colitti <lorenzo@google.com>
Subject: Re: [homenet] Creating a security association via physical link + button
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 26 Nov 2011 02:02:52 -0000

On Sat, Nov 26, 2011 at 9:53 AM, Hans Liu <hansliu@gmail.com> wrote:
> Mark,
>
>> Actually, I suggested that wired wouldn't need any key handshake. Wireless
>> would, and such handshakes require UI. The UI is the problem if there are
>> two devices that are not used to having any serious UI. I'm not sure I know
>> how to solve that, but I'm not sure it's our problem to solve either.
>>
>
> Take Wi-Fi for example, WPS PBC requires no UI. WPS PIN.
WPS PIN does.
> Hans
>



-- 
Instead of following the fashion, we lead it through.

From mellon@fugue.com  Fri Nov 25 18:07:50 2011
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 93B1B21F8AB8 for <homenet@ietfa.amsl.com>; Fri, 25 Nov 2011 18:07:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.046
X-Spam-Level: 
X-Spam-Status: No, score=-2.046 tagged_above=-999 required=5 tests=[AWL=0.396,  BAYES_00=-2.599, HTML_MESSAGE=0.001, SUBJECT_FUZZY_TION=0.156]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id x47spxs2JNPX for <homenet@ietfa.amsl.com>; Fri, 25 Nov 2011 18:07:50 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 2F52321F899F for <homenet@ietf.org>; Fri, 25 Nov 2011 18:07:50 -0800 (PST)
Received: from [IPv6:2001:470:1f07:1486:941f:74f9:f58d:df48] (unknown [IPv6:2001:470:1f07:1486:941f:74f9:f58d:df48]) by toccata.fugue.com (Postfix) with ESMTPSA id BA9B02380533; Fri, 25 Nov 2011 21:07:47 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: multipart/alternative; boundary="Apple-Mail=_65252A65-34E6-42C9-B9DA-2FA8A9A47563"
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <837D261D-6D78-47EF-B0B1-25CFF80D7F64@cisco.com>
Date: Fri, 25 Nov 2011 21:07:36 -0500
Message-Id: <5CE7A6B6-64DC-4BA9-9DEA-53D94BEF599E@fugue.com>
References: <CAKD1Yr3Y=EO9siQkAuZd7LtqsOT_8GswWkPOoiJEhtvnULcytw@mail.gmail.com> <4ECB98BC.8070600@riw.us> <ACDC3C9F-85D2-4AF6-AA8C-2A2E6EEDC8EE@fugue.com> <CAKD1Yr26zO0Dbco35ngWhj4W0hv_d_zJTCcbB-SSKqPpQab=ig@mail.gmail.com> <5C87A581-B2FD-4A1B-AD6B-7823279631BE@fugue.com> <CAKD1Yr3zp1Gn1P-jDVgna2ViWeQiyCaTM=hTchpJq2snPSL-hw@mail.gmail.com> <E70EE283-116C-49CD-854C-2DA20783FFD7@fugue.com> <97F2586F-3E18-47F3-B369-47BE7517204A@cisco.com> <9735297F-F9A5-4D40-BBAE-A9B5EB9FFF2A@fugue.com> <837D261D-6D78-47EF-B0B1-25CFF80D7F64@cisco.com>
To: Mark Townsley <townsley@cisco.com>
X-Mailer: Apple Mail (2.1251.1)
Cc: Russ White <russw@riw.us>, homenet@ietf.org, Lorenzo Colitti <lorenzo@google.com>
Subject: Re: [homenet] Creating a security association via physical link + button
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 26 Nov 2011 02:07:50 -0000

--Apple-Mail=_65252A65-34E6-42C9-B9DA-2FA8A9A47563
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Nov 25, 2011, at 8:15 PM, Mark Townsley wrote:
> What's the common case at L2 in homes today?

Stuff that needs to be secure uses SSL.   Gateways are trivially pwned =
by whatever malware is running on your PC.   I don't think we should =
feel complacent about this.


--Apple-Mail=_65252A65-34E6-42C9-B9DA-2FA8A9A47563
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div>On Nov 25, 2011, at 8:15 PM, Mark Townsley =
wrote:</div><blockquote type=3D"cite"><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; font-family: Helvetica; font-style: =
normal; font-variant: normal; font-weight: normal; letter-spacing: =
normal; line-height: normal; orphans: 2; text-align: -webkit-auto; =
text-indent: 0px; text-transform: none; white-space: normal; widows: 2; =
word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; ">What's the =
common case at L2 in homes today?</span><br =
class=3D"Apple-interchange-newline"></blockquote></div><br><div>Stuff =
that needs to be secure uses SSL. &nbsp; Gateways are trivially pwned by =
whatever malware is running on your PC. &nbsp; I don't think we should =
feel complacent about this.</div><div><br></div></body></html>=

--Apple-Mail=_65252A65-34E6-42C9-B9DA-2FA8A9A47563--

From russw@riw.us  Fri Nov 25 18:17:55 2011
Return-Path: <russw@riw.us>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A6C521F84D5 for <homenet@ietfa.amsl.com>; Fri, 25 Nov 2011 18:17:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.564
X-Spam-Level: 
X-Spam-Status: No, score=-2.564 tagged_above=-999 required=5 tests=[AWL=0.035,  BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zYLZdYeSC-+9 for <homenet@ietfa.amsl.com>; Fri, 25 Nov 2011 18:17:54 -0800 (PST)
Received: from ecbiz91.inmotionhosting.com (ecbiz91.inmotionhosting.com [173.205.124.250]) by ietfa.amsl.com (Postfix) with ESMTP id E988421F84BA for <homenet@ietf.org>; Fri, 25 Nov 2011 18:17:52 -0800 (PST)
Received: from cpe-065-190-155-146.nc.res.rr.com ([65.190.155.146]:58123 helo=[192.168.100.52]) by ecbiz91.inmotionhosting.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <russw@riw.us>) id 1RU7pv-0002nc-0G for homenet@ietf.org; Fri, 25 Nov 2011 21:17:51 -0500
Message-ID: <4ED04C42.2080809@riw.us>
Date: Fri, 25 Nov 2011 21:17:38 -0500
From: Russ White <russw@riw.us>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: homenet@ietf.org
References: <DCC302FAA9FE5F4BBA4DCAD4656937791452BBC0CC@PRVPEXVS03.corp.twcable.com>	<CABONVQbMsY6MF_8q44XqGmdOMS6Odn+CjBEttaEs9rhmknwRxg@mail.gmail.com><4ECCAFC3.5060903@globis.net><DCC302FAA9FE5F4BBA4DCAD4656937791452BBC498@PRVPEXVS03.corp.twcable.com>	<4ECD3608.5020502@globis.net>	<BDF2740C082F6942820D95BAEB9E1A846E5B05@XMB-AMS-108.cisco.com>	<B16D09C6-66AA-4FCC-9A3A-5CB2C2921523@nominet.org.uk> <5A35BCB0-B7B6-41FE-BA6E-2778D5D479AC@inf-net.nl> <4ECFE895.3080209@gmail.com>
In-Reply-To: <4ECFE895.3080209@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - ecbiz91.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - riw.us
Subject: Re: [homenet] other routing options
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 26 Nov 2011 02:17:55 -0000

> TRILL is not an IP routing protocol. It's a layer 2 bridging protocol more
> complicated than the spanning tree, and seems completely unnecessary for
> the small size of bridged networks to be expected in homenets.

What might actually be ideal is something that can route both at layer 2
and at layer 3 --I.e., that can treat layer 2 and layer 3 within the
home identically...

:-)

Russ

From rturner@amalfisystems.com  Fri Nov 25 22:18:10 2011
Return-Path: <rturner@amalfisystems.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 863DB21F8557 for <homenet@ietfa.amsl.com>; Fri, 25 Nov 2011 22:18:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.335
X-Spam-Level: 
X-Spam-Status: No, score=-2.335 tagged_above=-999 required=5 tests=[AWL=0.107,  BAYES_00=-2.599, HTML_MESSAGE=0.001, SUBJECT_FUZZY_TION=0.156]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rwp0AiQrRWYS for <homenet@ietfa.amsl.com>; Fri, 25 Nov 2011 22:18:09 -0800 (PST)
Received: from omr8.networksolutionsemail.com (omr8.networksolutionsemail.com [205.178.146.58]) by ietfa.amsl.com (Postfix) with ESMTP id AEFD221F84D5 for <homenet@ietf.org>; Fri, 25 Nov 2011 22:18:08 -0800 (PST)
Received: from cm-omr7 (mail.networksolutionsemail.com [205.178.146.50]) by omr8.networksolutionsemail.com (8.13.8/8.13.8) with ESMTP id pAQ6I4di022514 for <homenet@ietf.org>; Sat, 26 Nov 2011 01:18:06 -0500
Authentication-Results: cm-omr7 smtp.user=rturner@amalfisystems.com; auth=pass (CRAM-MD5)
X-Authenticated-UID: rturner@amalfisystems.com
Received: from [98.151.18.158] ([98.151.18.158:56222] helo=[192.168.1.114]) by cm-omr7 (envelope-from <rturner@amalfisystems.com>) (ecelerity 2.2.2.41 r(31179/31189)) with ESMTPSA (cipher=AES128-SHA)  id 98/42-04871-C9480DE4; Sat, 26 Nov 2011 01:18:04 -0500
From: Randy Turner <rturner@amalfisystems.com>
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: multipart/alternative; boundary="Apple-Mail=_A7BA175D-98EB-48D9-8D00-DD9D38918F31"
Date: Fri, 25 Nov 2011 22:18:05 -0800
In-Reply-To: <A23A4334-44A8-45ED-B3CB-B601C0021BF4@cisco.com>
To: homenet@ietf.org
References: <kkblj0mbs8xw8pp32w219ww6.1322224208905@email.android.com> <5B97FD15-7CE9-4FB8-88A4-36C4D0930BEF@fugue.com> <A23A4334-44A8-45ED-B3CB-B601C0021BF4@cisco.com>
Message-Id: <BDF1CF4F-5282-4FCE-A1FD-51B8698EC47D@amalfisystems.com>
X-Mailer: Apple Mail (2.1251.1)
Subject: Re: [homenet] Creating a security association via physical link + button
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 26 Nov 2011 06:18:10 -0000

--Apple-Mail=_A7BA175D-98EB-48D9-8D00-DD9D38918F31
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


You maybe right about the equivalent key-management scope, however, I =
believe any work in the key distribution area applied to the "integrity =
of routing updates" would pay off more than expending this effort on the =
"confidentiality of routing update" problem.  One of the devices we are =
considering as a "router" in the Homenet is a Windows machine where the =
end user has simply turned on internet connection sharing (ICS).  =
Assuming this machine is their home PC, we're talking about the target =
of practically every attack profile on the internet, so I think it's =
worth the effort to establish a trust model.  Even an android-based =
phone could inject false (untrusted) routes into the Homenet, but then =
again I'm getting ahead of myself in pre-supposing attack vectors on the =
Homenet.  I'm keeping an open mind on all of this until we have a =
document or other work that performs the due diligence on threats to the =
Homenet.

Randy

On Nov 25, 2011, at 5:17 PM, Mark Townsley wrote:

>=20
> On Nov 25, 2011, at 6:28 PM, Ted Lemon wrote:
>=20
>> On Nov 25, 2011, at 7:30 AM, Randy Turner wrote:
>>> I think I agree that confidentiality of routing traffic is probably =
not an issue for Homenet - however, I do think we should consider =
integrity of routing traffic - ie, router A should "trust" that route =
updates from router B are correct.
>>=20
>> Exactly.
>=20
> I see no difference really between the difficulty between an =
integrity-only solution and a confidentiality solution. Both require =
keys. It's the keys that are the real problem, not the work done on the =
packets.
>=20
> And, yes, key exchange being hard is based on a certain amount of =
intuition for my part as well.=20
>=20
> - Mark
>=20
>>=20
>>> That being said, this is just an intuitive feeling regarding =
security - maybe we need someone to work on a threat analysis and what =
the implications could be to the types of applications we anticipate
>>=20
>>=20
>> Yes, I think this would be worthwhile.   I'm certainly arguing based =
on intuition at the moment.
>>=20
>> _______________________________________________
>> homenet mailing list
>> homenet@ietf.org
>> https://www.ietf.org/mailman/listinfo/homenet
>=20


--Apple-Mail=_A7BA175D-98EB-48D9-8D00-DD9D38918F31
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><br></div>You maybe right about the equivalent key-management =
scope, however, I believe any work in the key distribution area applied =
to the "integrity of routing updates" would pay off more than expending =
this effort on the "confidentiality of routing update" problem. =
&nbsp;One of the devices we are considering as a "router" in the Homenet =
is a Windows machine where the end user has simply turned on internet =
connection sharing (ICS). &nbsp;Assuming this machine is their home PC, =
we're talking about the target of practically every attack profile on =
the internet, so I think it's worth the effort to establish a trust =
model. &nbsp;Even an android-based phone could inject false (untrusted) =
routes into the Homenet, but then again I'm getting ahead of myself in =
pre-supposing attack vectors on the Homenet. &nbsp;I'm keeping an open =
mind on all of this until we have a document or other work that performs =
the due diligence on threats to the =
Homenet.<div><br></div><div>Randy</div><div><br></div><div><div><div>On =
Nov 25, 2011, at 5:17 PM, Mark Townsley wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><br><div><div>On Nov 25, 2011, =
at 6:28 PM, Ted Lemon wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote type=3D"cite"><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><div>On Nov 25, 2011, at =
7:30 AM, Randy Turner wrote:</div><blockquote type=3D"cite"><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
font-family: Helvetica; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: =
none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; ">I think I =
agree that confidentiality of routing traffic is probably not an issue =
for Homenet - however, I do think we should consider integrity of =
routing traffic - ie, router A should "trust" that route updates from =
router B are =
correct.</span></blockquote><div><br></div><div>Exactly.</div></div></div>=
</blockquote><div><br></div><div>I see no difference really between the =
difficulty between an integrity-only solution and a confidentiality =
solution. Both require keys. It's the keys that are the real problem, =
not the work done on the packets.</div><div><br></div><div>And, yes, key =
exchange being hard is based on a certain amount of intuition for my =
part as well.&nbsp;</div><div><br></div><div>- Mark</div><br><blockquote =
type=3D"cite"><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; -webkit-line-break: after-white-space; "><div><br><blockquote =
type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-collapse: =
separate; font-family: Helvetica; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; ">That being =
said, this is just an intuitive feeling regarding security - maybe we =
need someone to work on a threat analysis and what the implications =
could be to the types of applications we =
anticipate</span></blockquote></div><div><br></div><div>Yes, I think =
this would be worthwhile. &nbsp; I'm certainly arguing based on =
intuition at the =
moment.</div><div><br></div></div>________________________________________=
_______<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">https://www.ietf.or=
g/mailman/listinfo/homenet</a><br></blockquote></div><br></div></blockquot=
e></div><br></div></body></html>=

--Apple-Mail=_A7BA175D-98EB-48D9-8D00-DD9D38918F31--

From robert.cragie@gridmerge.com  Sat Nov 26 01:52:59 2011
Return-Path: <robert.cragie@gridmerge.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA35A21F84CC for <homenet@ietfa.amsl.com>; Sat, 26 Nov 2011 01:52:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.521
X-Spam-Level: 
X-Spam-Status: No, score=-2.521 tagged_above=-999 required=5 tests=[AWL=-0.079, BAYES_00=-2.599, HTML_MESSAGE=0.001, SUBJECT_FUZZY_TION=0.156]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UxT-8VFIBZ66 for <homenet@ietfa.amsl.com>; Sat, 26 Nov 2011 01:52:59 -0800 (PST)
Received: from mail78.extendcp.co.uk (mail78.extendcp.co.uk [79.170.40.78]) by ietfa.amsl.com (Postfix) with ESMTP id 5E4C421F84C2 for <homenet@ietf.org>; Sat, 26 Nov 2011 01:52:57 -0800 (PST)
Received: from client-86-31-198-101.oxfd.adsl.virginmedia.com ([86.31.198.101] helo=[192.168.0.2]) by mail78.extendcp.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) id 1RUEwF-00007q-Qq for homenet@ietf.org; Sat, 26 Nov 2011 09:52:52 +0000
Message-ID: <4ED0B6EC.8030404@gridmerge.com>
Date: Sat, 26 Nov 2011 09:52:44 +0000
From: Robert Cragie <robert.cragie@gridmerge.com>
Organization: Gridmerge Ltd.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: homenet@ietf.org
References: <kkblj0mbs8xw8pp32w219ww6.1322224208905@email.android.com> <5B97FD15-7CE9-4FB8-88A4-36C4D0930BEF@fugue.com> <A23A4334-44A8-45ED-B3CB-B601C0021BF4@cisco.com> <BDF1CF4F-5282-4FCE-A1FD-51B8698EC47D@amalfisystems.com>
In-Reply-To: <BDF1CF4F-5282-4FCE-A1FD-51B8698EC47D@amalfisystems.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms030802070402020906090109"
X-Authenticated-As: robert.cragie@gridmerge.com
Subject: Re: [homenet] Creating a security association via physical link + button
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: robert.cragie@gridmerge.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, 26 Nov 2011 09:52:59 -0000

This is a cryptographically signed message in MIME format.

--------------ms030802070402020906090109
Content-Type: multipart/alternative;
 boundary="------------030605020306010909070402"

This is a multi-part message in MIME format.
--------------030605020306010909070402
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable

I've been following this thread with interest. Some points (from someone =

who has a particular 802.15.4-based mesh networking viewpoint):

  * There probably isn't any need to specify cryptographic security for
    an IGP on the basis that the packets are link-local and can
    therefore be protected at L2.
  * Network access control can set up secure channels to deliver keying
    information. Therefore in theory this can be used to deliver keying
    information for any protocols, although in practice it is often just
    L2 keying information. The focus then turns to which credentials are
    used for network access control. Whilst I support the use of public
    key crypto., it is not essential for homenet and there are solutions
    (not perfect, IMHO, but adequate) which exist now for easy joining
    (e.g. WPS) based on a pre-shared key/passphrase. Having said that,
    the burden and complexity of using public key crypto. for network
    access and mutual authentication is perhaps not as great as one may
    think.
  * The original question was about merging networks in the home. Again,
    I don't think it is that complex if dealt with from a network access
    point of view. Whether one becomes secondary and assumes the keying
    information from the primary network (probably preferable if the
    topology is a mesh) or the two simply join at a common router and
    retain their own keying information, either is possible and not
    difficult.

Robert

On 26/11/2011 6:18 AM, Randy Turner wrote:
>
> You maybe right about the equivalent key-management scope, however, I=20
> believe any work in the key distribution area applied to the=20
> "integrity of routing updates" would pay off more than expending this=20
> effort on the "confidentiality of routing update" problem.  One of the =

> devices we are considering as a "router" in the Homenet is a Windows=20
> machine where the end user has simply turned on internet connection=20
> sharing (ICS).  Assuming this machine is their home PC, we're talking=20
> about the target of practically every attack profile on the internet,=20
> so I think it's worth the effort to establish a trust model.  Even an=20
> android-based phone could inject false (untrusted) routes into the=20
> Homenet, but then again I'm getting ahead of myself in pre-supposing=20
> attack vectors on the Homenet.  I'm keeping an open mind on all of=20
> this until we have a document or other work that performs the due=20
> diligence on threats to the Homenet.
>
> Randy
>
> On Nov 25, 2011, at 5:17 PM, Mark Townsley wrote:
>
>>
>> On Nov 25, 2011, at 6:28 PM, Ted Lemon wrote:
>>
>>> On Nov 25, 2011, at 7:30 AM, Randy Turner wrote:
>>>> I think I agree that confidentiality of routing traffic is probably =

>>>> not an issue for Homenet - however, I do think we should consider=20
>>>> integrity of routing traffic - ie, router A should "trust" that=20
>>>> route updates from router B are correct.
>>>
>>> Exactly.
>>
>> I see no difference really between the difficulty between an=20
>> integrity-only solution and a confidentiality solution. Both require=20
>> keys. It's the keys that are the real problem, not the work done on=20
>> the packets.
>>
>> And, yes, key exchange being hard is based on a certain amount of=20
>> intuition for my part as well.
>>
>> - Mark
>>
>>>
>>>> That being said, this is just an intuitive feeling regarding=20
>>>> security - maybe we need someone to work on a threat analysis and=20
>>>> what the implications could be to the types of applications we=20
>>>> anticipate
>>>
>>> Yes, I think this would be worthwhile.   I'm certainly arguing based =

>>> on intuition at the moment.
>>>
>>> _______________________________________________
>>> homenet mailing list
>>> homenet@ietf.org <mailto:homenet@ietf.org>
>>> https://www.ietf.org/mailman/listinfo/homenet
>>
>
>
>
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet

--------------030605020306010909070402
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<html>
  <head>
    <meta content=3D"text/html; charset=3DISO-8859-1"
      http-equiv=3D"Content-Type">
  </head>
  <body bgcolor=3D"#FFFFFF" text=3D"#000000">
    I've been following this thread with interest. Some points (from
    someone who has a particular 802.15.4-based mesh networking
    viewpoint):<br>
    <br>
    <ul>
      <li>There probably isn't any need to specify cryptographic
        security for an IGP on the basis that the packets are link-local
        and can therefore be protected at L2.</li>
      <li>Network access control can set up secure channels to deliver
        keying information. Therefore in theory this can be used to
        deliver keying information for any protocols, although in
        practice it is often just L2 keying information. The focus then
        turns to which credentials are used for network access control.
        Whilst I support the use of public key crypto., it is not
        essential for homenet and there are solutions (not perfect,
        IMHO, but adequate) which exist now for easy joining (e.g. WPS)
        based on a pre-shared key/passphrase. Having said that, the
        burden and complexity of using public key crypto. for network
        access and mutual authentication is perhaps not as great as one
        may think.</li>
      <li>The original question was about merging networks in the home.
        Again, I don't think it is that complex if dealt with from a
        network access point of view. Whether one becomes secondary and
        assumes the keying information from the primary network
        (probably preferable if the topology is a mesh) or the two
        simply join at a common router and retain their own keying
        information, either is possible and not difficult.</li>
    </ul>
    Robert<br>
    <br>
    On 26/11/2011 6:18 AM, Randy Turner wrote:
    <blockquote
      cite=3D"mid:BDF1CF4F-5282-4FCE-A1FD-51B8698EC47D@amalfisystems.com"=

      type=3D"cite">
      <div><br>
      </div>
      You maybe right about the equivalent key-management scope,
      however, I believe any work in the key distribution area applied
      to the "integrity of routing updates" would pay off more than
      expending this effort on the "confidentiality of routing update"
      problem. &nbsp;One of the devices we are considering as a "router" =
in
      the Homenet is a Windows machine where the end user has simply
      turned on internet connection sharing (ICS). &nbsp;Assuming this
      machine is their home PC, we're talking about the target of
      practically every attack profile on the internet, so I think it's
      worth the effort to establish a trust model. &nbsp;Even an
      android-based phone could inject false (untrusted) routes into the
      Homenet, but then again I'm getting ahead of myself in
      pre-supposing attack vectors on the Homenet. &nbsp;I'm keeping an o=
pen
      mind on all of this until we have a document or other work that
      performs the due diligence on threats to the Homenet.
      <div><br>
      </div>
      <div>Randy</div>
      <div><br>
      </div>
      <div>
        <div>
          <div>On Nov 25, 2011, at 5:17 PM, Mark Townsley wrote:</div>
          <br class=3D"Apple-interchange-newline">
          <blockquote type=3D"cite">
            <div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space=
;
              -webkit-line-break: after-white-space; "><br>
              <div>
                <div>On Nov 25, 2011, at 6:28 PM, Ted Lemon wrote:</div>
                <br class=3D"Apple-interchange-newline">
                <blockquote type=3D"cite">
                  <div style=3D"word-wrap: break-word; -webkit-nbsp-mode:=

                    space; -webkit-line-break: after-white-space; ">
                    <div>
                      <div>On Nov 25, 2011, at 7:30 AM, Randy Turner
                        wrote:</div>
                      <blockquote type=3D"cite"><span
                          class=3D"Apple-style-span"
                          style=3D"border-collapse: separate; font-family=
:
                          Helvetica; font-style: normal; font-variant:
                          normal; font-weight: normal; letter-spacing:
                          normal; line-height: normal; orphans: 2;
                          text-align: -webkit-auto; text-indent: 0px;
                          text-transform: none; white-space: normal;
                          widows: 2; word-spacing: 0px;
                          -webkit-border-horizontal-spacing: 0px;
                          -webkit-border-vertical-spacing: 0px;
                          -webkit-text-decorations-in-effect: none;
                          -webkit-text-size-adjust: auto;
                          -webkit-text-stroke-width: 0px; font-size:
                          medium; ">I think I agree that confidentiality
                          of routing traffic is probably not an issue
                          for Homenet - however, I do think we should
                          consider integrity of routing traffic - ie,
                          router A should "trust" that route updates
                          from router B are correct.</span></blockquote>
                      <div><br>
                      </div>
                      <div>Exactly.</div>
                    </div>
                  </div>
                </blockquote>
                <div><br>
                </div>
                <div>I see no difference really between the difficulty
                  between an integrity-only solution and a
                  confidentiality solution. Both require keys. It's the
                  keys that are the real problem, not the work done on
                  the packets.</div>
                <div><br>
                </div>
                <div>And, yes, key exchange being hard is based on a
                  certain amount of intuition for my part as well.&nbsp;<=
/div>
                <div><br>
                </div>
                <div>- Mark</div>
                <br>
                <blockquote type=3D"cite">
                  <div style=3D"word-wrap: break-word; -webkit-nbsp-mode:=

                    space; -webkit-line-break: after-white-space; ">
                    <div><br>
                      <blockquote type=3D"cite"><span
                          class=3D"Apple-style-span"
                          style=3D"border-collapse: separate; font-family=
:
                          Helvetica; font-style: normal; font-variant:
                          normal; font-weight: normal; letter-spacing:
                          normal; line-height: normal; orphans: 2;
                          text-align: -webkit-auto; text-indent: 0px;
                          text-transform: none; white-space: normal;
                          widows: 2; word-spacing: 0px;
                          -webkit-border-horizontal-spacing: 0px;
                          -webkit-border-vertical-spacing: 0px;
                          -webkit-text-decorations-in-effect: none;
                          -webkit-text-size-adjust: auto;
                          -webkit-text-stroke-width: 0px; font-size:
                          medium; ">That being said, this is just an
                          intuitive feeling regarding security - maybe
                          we need someone to work on a threat analysis
                          and what the implications could be to the
                          types of applications we anticipate</span></blo=
ckquote>
                    </div>
                    <div><br>
                    </div>
                    <div>Yes, I think this would be worthwhile. &nbsp; I'=
m
                      certainly arguing based on intuition at the
                      moment.</div>
                    <div><br>
                    </div>
                  </div>
                  _______________________________________________<br>
                  homenet mailing list<br>
                  <a moz-do-not-send=3D"true"
                    href=3D"mailto:homenet@ietf.org">homenet@ietf.org</a>=
<br>
                  <a moz-do-not-send=3D"true"
                    href=3D"https://www.ietf.org/mailman/listinfo/homenet=
">https://www.ietf.org/mailman/listinfo/homenet</a><br>
                </blockquote>
              </div>
              <br>
            </div>
          </blockquote>
        </div>
        <br>
      </div>
      <br>
      <fieldset class=3D"mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap=3D"">_______________________________________________
homenet mailing list
<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:homenet@ietf.org">ho=
menet@ietf.org</a>
<a class=3D"moz-txt-link-freetext" href=3D"https://www.ietf.org/mailman/l=
istinfo/homenet">https://www.ietf.org/mailman/listinfo/homenet</a>
</pre>
    </blockquote>
  </body>
</html>

--------------030605020306010909070402--

--------------ms030802070402020906090109
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIP3jCC
BIowggNyoAMCAQICECf06hH0eobEbp27bqkXBwcwDQYJKoZIhvcNAQEFBQAwbzELMAkGA1UE
BhMCU0UxFDASBgNVBAoTC0FkZFRydXN0IEFCMSYwJAYDVQQLEx1BZGRUcnVzdCBFeHRlcm5h
bCBUVFAgTmV0d29yazEiMCAGA1UEAxMZQWRkVHJ1c3QgRXh0ZXJuYWwgQ0EgUm9vdDAeFw0w
NTA2MDcwODA5MTBaFw0yMDA1MzAxMDQ4MzhaMIGuMQswCQYDVQQGEwJVUzELMAkGA1UECBMC
VVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVUaGUgVVNFUlRSVVNUIE5l
dHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2MDQGA1UEAxMtVVRO
LVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsMIIBIjANBgkqhkiG
9w0BAQEFAAOCAQ8AMIIBCgKCAQEAsjmFpPJ9q0E7YkY3rs3BYHW8OWX5ShpHornMSMxqmNVN
NRm5pELlzkniii8efNIxB8dOtINknS4p1aJkxIW9hVE1eaROaJB7HHqkkqgX8pgV8pPMyaQy
lbsMTzC9mKALi+VuG6JG+ni8om+rWV6lL8/K2m2qL+usobNqqrcuZzWLeeEeaYji5kbNoKXq
vgvOdjp6Dpvq/NonWz1zHyLmSGHGTPNpsaguG7bUMSAsvIKKjqQOpdeJQ/wWWq8dcdcRWdq6
hw2v+vPhwvCkxWeM1tZUOt4KpLoDd7NlyP0e03RiqhjKaJMeoYV+9Udly/hNVyh00jT/MLbu
9mIwFIws6wIDAQABo4HhMIHeMB8GA1UdIwQYMBaAFK29mHo0tCb3+sQmVO8DveAky1QaMB0G
A1UdDgQWBBSJgmd9xJ0mcABLtFBIfN49rgRufTAOBgNVHQ8BAf8EBAMCAQYwDwYDVR0TAQH/
BAUwAwEB/zB7BgNVHR8EdDByMDigNqA0hjJodHRwOi8vY3JsLmNvbW9kb2NhLmNvbS9BZGRU
cnVzdEV4dGVybmFsQ0FSb290LmNybDA2oDSgMoYwaHR0cDovL2NybC5jb21vZG8ubmV0L0Fk
ZFRydXN0RXh0ZXJuYWxDQVJvb3QuY3JsMA0GCSqGSIb3DQEBBQUAA4IBAQAZ2IkRbyispgCi
54fBm5AD236hEv0e8+LwAamUVEJrmgnEoG3XkJIEA2Z5Q3H8+G+v23ZF4jcaPd3kWQR4rBz0
g0bzes9bhHIt5UbBuhgRKfPLSXmHPLptBZ2kbWhPrXIUNqi5sf2/z3/wpGqUNVCPz4FtVbHd
WTBK322gnGQfSXzvNrv042n0+DmPWq1LhTq3Du3Tzw1EovsEv+QvcI4l+1pUBrPQxLxtjftz
Mizpm4QkLdZ/kXpoAlAfDj9N6cz1u2fo3BwuO/xOzf4CjuOoEwqlJkRl6RDyTVKnrtw+ymsy
XEFs/vVdoOr/0fqbhlhtPZZH5f4ulQTCAMyOofK7MIIFGjCCBAKgAwIBAgIQbRnqpxlPajMi
5iIyeqpx3jANBgkqhkiG9w0BAQUFADCBrjELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAlVUMRcw
FQYDVQQHEw5TYWx0IExha2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVTVCBOZXR3b3Jr
MSEwHwYDVQQLExhodHRwOi8vd3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMTLVVUTi1VU0VS
Rmlyc3QtQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBFbWFpbDAeFw0xMTA0MjgwMDAwMDBa
Fw0yMDA1MzAxMDQ4MzhaMIGTMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5j
aGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDE5
MDcGA1UEAxMwQ09NT0RPIENsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgU2VjdXJlIEVtYWls
IENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAkoSEW0tXmNReL4uk4UDIo1NY
X2Zl8TJO958yfVXQeExVt0KU4PkncQfFxmmkuTLE8UAakMwnVmJ/F7Vxaa7lIBvky2NeYMqi
QfZq4aP/uN8fSG1lQ4wqLitjOHffsReswtqCAtbUMmrUZ28gE49cNfrlVICv2HEKHTcKAlBT
bJUdqRAUtJmVWRIx/wmi0kzcUtve4kABW0ho3cVKtODtJB86r3FfB+OsvxQ7sCVxaD30D9YX
WEYVgTxoi4uDD216IVfmNLDbMn7jSuGlUnJkJpFOpZIP/+CxYP0ab2hRmWONGoulzEKbm30i
Y9OpoPzOnpDfRBn0XFs1uhbzp5v/wQIDAQABo4IBSzCCAUcwHwYDVR0jBBgwFoAUiYJnfcSd
JnAAS7RQSHzePa4Ebn0wHQYDVR0OBBYEFHoTTgB0W8Z4Y2QnwS/ioFu8ecV7MA4GA1UdDwEB
/wQEAwIBBjASBgNVHRMBAf8ECDAGAQH/AgEAMBEGA1UdIAQKMAgwBgYEVR0gADBYBgNVHR8E
UTBPME2gS6BJhkdodHRwOi8vY3JsLnVzZXJ0cnVzdC5jb20vVVROLVVTRVJGaXJzdC1DbGll
bnRBdXRoZW50aWNhdGlvbmFuZEVtYWlsLmNybDB0BggrBgEFBQcBAQRoMGYwPQYIKwYBBQUH
MAKGMWh0dHA6Ly9jcnQudXNlcnRydXN0LmNvbS9VVE5BZGRUcnVzdENsaWVudF9DQS5jcnQw
JQYIKwYBBQUHMAGGGWh0dHA6Ly9vY3NwLnVzZXJ0cnVzdC5jb20wDQYJKoZIhvcNAQEFBQAD
ggEBAIXWvnhXVW0zf0RS/kLVBqgBA4CK+w2y/Uq/9q9BSfUbWsXSrRtzbj7pJnzmTJjBMCjf
y/tCPKElPgp11tA9OYZm0aGbtU2bb68obB2v5ep0WqjascDxdXovnrqTecr+4pEeVnSy+I3T
4ENyG+2P/WA5IEf7i686ZUg8mD2lJb+972DgSeUWyOs/Q4Pw4O4NwdPNM1+b0L1garM7/vrU
yTo8H+2b/5tJM75CKTmD7jNpLoKdRU2oadqAGx490hpdfEeZpZsIbRKZhtZdVwcbpzC+S0lE
uJB+ytF5OOu0M/qgOl0mWJ5hVRi0IdWZ1eBDQEIwvuql55TSsP7zdfl/bucwggYuMIIFFqAD
AgECAhBcMVDbxC2oy5hyHl/adO9mMA0GCSqGSIb3DQEBBQUAMIGTMQswCQYDVQQGEwJHQjEb
MBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQK
ExFDT01PRE8gQ0EgTGltaXRlZDE5MDcGA1UEAxMwQ09NT0RPIENsaWVudCBBdXRoZW50aWNh
dGlvbiBhbmQgU2VjdXJlIEVtYWlsIENBMB4XDTExMDkwMjAwMDAwMFoXDTE0MDkwMTIzNTk1
OVowggE3MQswCQYDVQQGEwJHQjEQMA4GA1UEERMHV0Y0IDRXQTEXMBUGA1UECBMOV2VzdCBZ
b3Jrc2hpcmUxEjAQBgNVBAcTCVdha2VmaWVsZDEUMBIGA1UECRMLR3JhbmdlIE1vb3IxHzAd
BgNVBAkTFjg5IEdyZWVuZmllbGQgQ3Jlc2NlbnQxFzAVBgNVBAoTDkdyaWRtZXJnZSBMdGQu
MTQwMgYDVQQLEytJc3N1ZWQgdGhyb3VnaCBHcmlkbWVyZ2UgTHRkLiBFLVBLSSBNYW5hZ2Vy
MR8wHQYDVQQLExZDb3Jwb3JhdGUgU2VjdXJlIEVtYWlsMRYwFAYDVQQDEw1Sb2JlcnQgQ3Jh
Z2llMSowKAYJKoZIhvcNAQkBFhtyb2JlcnQuY3JhZ2llQGdyaWRtZXJnZS5jb20wggEiMA0G
CSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCtxOGq8t5ZTVDVkmadv7ZRBLA5ApaiTcDUzCTn
zYB2/BoBDIEWWI/InSRcmq3A0Ghm+T7dYmvRADllGv4nTHexdWlzFp2iM/Yc3PLWCyAO0gYb
yW2hTi+ZfUDwFOU4hRP4+Dyn9tKu7FXS/PQJHyGjaGxHRmLm9T6tAo2ZuC59uRaGVCcwRiOS
d6axwtB/DVhnP3S1rrt2g0O6MXLr5fojToemO52AxjHxt2w1LnFUUXC4EDV6o1Ctr7EvOEI5
5f088H/Mrryp02GueLdY9gb0SFK3gPOT7EjP2GPvCtRkhVcNM+xjyptRIFWnCbMjmUIc+DO6
sfU4rtbCCkNKyXmnAgMBAAGjggHVMIIB0TAfBgNVHSMEGDAWgBR6E04AdFvGeGNkJ8Ev4qBb
vHnFezAdBgNVHQ4EFgQUEI5c0f6UObxT2DLdvdtG+vG8qCswDgYDVR0PAQH/BAQDAgWgMAwG
A1UdEwEB/wQCMAAwHQYDVR0lBBYwFAYIKwYBBQUHAwQGCCsGAQUFBwMCMEYGA1UdIAQ/MD0w
OwYMKwYBBAGyMQECAQMFMCswKQYIKwYBBQUHAgEWHWh0dHBzOi8vc2VjdXJlLmNvbW9kby5u
ZXQvQ1BTMFcGA1UdHwRQME4wTKBKoEiGRmh0dHA6Ly9jcmwuY29tb2RvY2EuY29tL0NPTU9E
T0NsaWVudEF1dGhlbnRpY2F0aW9uYW5kU2VjdXJlRW1haWxDQS5jcmwwgYgGCCsGAQUFBwEB
BHwwejBSBggrBgEFBQcwAoZGaHR0cDovL2NydC5jb21vZG9jYS5jb20vQ09NT0RPQ2xpZW50
QXV0aGVudGljYXRpb25hbmRTZWN1cmVFbWFpbENBLmNydDAkBggrBgEFBQcwAYYYaHR0cDov
L29jc3AuY29tb2RvY2EuY29tMCYGA1UdEQQfMB2BG3JvYmVydC5jcmFnaWVAZ3JpZG1lcmdl
LmNvbTANBgkqhkiG9w0BAQUFAAOCAQEAPpv87QuQ9q+RHhmeirGDQB3szd24Obi7N+uVfh5y
CrnoJx3B37dNrLPsTB6PfTChUyZMqQD80pFoJ3TBUz3yx4X+hmNco7ujVIfbuKBGcZJaMKhZ
ex3AkZ9ltie9wgiGGzEmgI81t5JHsLQ8AUMqw/fGsnIwcyWMgmyhFtm79+dg3IVaH05d/t9g
k4aYoMoCFJptQZ+Fju6a9T139hOqjTZDpjMLt3jM80bVrvkC4dIRyF/oZ0qrJwbfwjnL2OUN
ph9eymhLc+VM0Ih5k41s5IxmB+2c0RUqr5JbK0WrIb/z53Cmb9rXYox7HknyIfBpQqP77Y7a
sAU2MMOpel4RijGCBAwwggQIAgEBMIGoMIGTMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3Jl
YXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0Eg
TGltaXRlZDE5MDcGA1UEAxMwQ09NT0RPIENsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgU2Vj
dXJlIEVtYWlsIENBAhBcMVDbxC2oy5hyHl/adO9mMAkGBSsOAwIaBQCgggI4MBgGCSqGSIb3
DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMTEyNjA5NTI0NFowIwYJKoZI
hvcNAQkEMRYEFAdez/dKK5aSFxm+mxZihLec1uIVMF8GCSqGSIb3DQEJDzFSMFAwCwYJYIZI
AWUDBAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUr
DgMCBzANBggqhkiG9w0DAgIBKDCBuQYJKwYBBAGCNxAEMYGrMIGoMIGTMQswCQYDVQQGEwJH
QjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYD
VQQKExFDT01PRE8gQ0EgTGltaXRlZDE5MDcGA1UEAxMwQ09NT0RPIENsaWVudCBBdXRoZW50
aWNhdGlvbiBhbmQgU2VjdXJlIEVtYWlsIENBAhBcMVDbxC2oy5hyHl/adO9mMIG7BgsqhkiG
9w0BCRACCzGBq6CBqDCBkzELMAkGA1UEBhMCR0IxGzAZBgNVBAgTEkdyZWF0ZXIgTWFuY2hl
c3RlcjEQMA4GA1UEBxMHU2FsZm9yZDEaMBgGA1UEChMRQ09NT0RPIENBIExpbWl0ZWQxOTA3
BgNVBAMTMENPTU9ETyBDbGllbnQgQXV0aGVudGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBD
QQIQXDFQ28QtqMuYch5f2nTvZjANBgkqhkiG9w0BAQEFAASCAQA8dQrGUZ5q+3SA3sL+dIoA
/tDE0brGikyh/X5pmZAG80va8nHlSKup8KKLCxNJ+FHouCIjWrB3e5SCbPFeuTgsbjGboQ/F
YW5mE6gkAbCHiro5MfnmxJL6rPnV26TwSojjRmJa9ok6qkCLmY4KeGUDTGfdIxdQ/8TQJ8xT
biTER6LKWUVGDOyyMyAwjzXhOxaRySMHY6A4xKOxqYHf973nNUshO0zPtM0akIH/gaWG2sFE
PVTGvUWcquGFMRFo17kvDOePL3EGrdNaRjO1SZGJCkknq6yVYdu7eIaOBAPLxwKuidJAyVXW
qvBp6g8uMFC9ANj4uMoIw3h/ewpcw1BzAAAAAAAA
--------------ms030802070402020906090109--

From teco@inf-net.nl  Sat Nov 26 03:58:50 2011
Return-Path: <teco@inf-net.nl>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F217C21F8BBB for <homenet@ietfa.amsl.com>; Sat, 26 Nov 2011 03:58:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Qbyg+bf3r1De for <homenet@ietfa.amsl.com>; Sat, 26 Nov 2011 03:58:50 -0800 (PST)
Received: from mail-ww0-f42.google.com (mail-ww0-f42.google.com [74.125.82.42]) by ietfa.amsl.com (Postfix) with ESMTP id 458DA21F8BB9 for <homenet@ietf.org>; Sat, 26 Nov 2011 03:58:49 -0800 (PST)
Received: by wwo28 with SMTP id 28so3933229wwo.1 for <homenet@ietf.org>; Sat, 26 Nov 2011 03:58:48 -0800 (PST)
Received: by 10.227.204.197 with SMTP id fn5mr20023138wbb.15.1322308728512; Sat, 26 Nov 2011 03:58:48 -0800 (PST)
Received: from [10.175.173.2] (524A158D.cm-4-3a.dynamic.ziggo.nl. [82.74.21.141]) by mx.google.com with ESMTPS id dw6sm11857050wib.12.2011.11.26.03.58.47 (version=TLSv1/SSLv3 cipher=OTHER); Sat, 26 Nov 2011 03:58:47 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Teco Boot <teco@inf-net.nl>
In-Reply-To: <4ED04C42.2080809@riw.us>
Date: Sat, 26 Nov 2011 12:58:45 +0100
Content-Transfer-Encoding: 7bit
Message-Id: <59445D1D-9D4A-4066-AD25-FED7A9839862@inf-net.nl>
References: <DCC302FAA9FE5F4BBA4DCAD4656937791452BBC0CC@PRVPEXVS03.corp.twcable.com>	<CABONVQbMsY6MF_8q44XqGmdOMS6Odn+CjBEttaEs9rhmknwRxg@mail.gmail.com><4ECCAFC3.5060903@globis.net><DCC302FAA9FE5F4BBA4DCAD4656937791452BBC498@PRVPEXVS03.corp.twcable.com>	<4ECD3608.5020502@globis.net>	<BDF2740C082F6942820D95BAEB9E1A846E5B05@XMB-AMS-108.cisco.com>	<B16D09C6-66AA-4FCC-9A3A-5CB2C2921523@nominet.org.uk> <5A35BCB0-B7B6-41FE-BA6E-2778D5D479AC@inf-net.nl> <4ECFE895.3080209@gmail.com> <4ED04C42.2080809@riw.us>
To: Russ White <russw@riw.us>
X-Mailer: Apple Mail (2.1251.1)
Cc: homenet@ietf.org
Subject: Re: [homenet] other routing options
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 26 Nov 2011 11:58:51 -0000

Op 26 nov. 2011, om 03:17 heeft Russ White het volgende geschreven:

> 
>> TRILL is not an IP routing protocol. It's a layer 2 bridging protocol more
>> complicated than the spanning tree, and seems completely unnecessary for
>> the small size of bridged networks to be expected in homenets.
> 
> What might actually be ideal is something that can route both at layer 2
> and at layer 3 --I.e., that can treat layer 2 and layer 3 within the
> home identically...

Yes, route VLANs. It makes sense to bind equivalent L2 links to a single L3 
link. Dummies are faced the fact that broadcasts on home link and guest link
simply works. No need for new protocols, L3 multicast and app upgrades.

As long as dual stack is in use, dummies don't understand different 
topologies for the stacks. They should not be aware of dual stack in the 
first place.

Teco 

> 
> :-)
> 
> Russ
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet


From acee.lindem@ericsson.com  Sat Nov 26 04:06:05 2011
Return-Path: <acee.lindem@ericsson.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F21821F8B33 for <homenet@ietfa.amsl.com>; Sat, 26 Nov 2011 04:06:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.454
X-Spam-Level: 
X-Spam-Status: No, score=-6.454 tagged_above=-999 required=5 tests=[AWL=-0.012, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, SUBJECT_FUZZY_TION=0.156]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iToRMD7i+S0L for <homenet@ietfa.amsl.com>; Sat, 26 Nov 2011 04:06:04 -0800 (PST)
Received: from imr3.ericy.com (imr3.ericy.com [198.24.6.13]) by ietfa.amsl.com (Postfix) with ESMTP id 73C8721F8B32 for <homenet@ietf.org>; Sat, 26 Nov 2011 04:06:04 -0800 (PST)
Received: from eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) by imr3.ericy.com (8.13.8/8.13.8) with ESMTP id pAQC5vJr007608 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 26 Nov 2011 06:05:58 -0600
Received: from EUSAACMS0702.eamcs.ericsson.se ([169.254.1.25]) by eusaamw0707.eamcs.ericsson.se ([147.117.20.32]) with mapi; Sat, 26 Nov 2011 07:05:57 -0500
From: Acee Lindem <acee.lindem@ericsson.com>
To: "robert.cragie@gridmerge.com" <robert.cragie@gridmerge.com>
Date: Sat, 26 Nov 2011 07:05:54 -0500
Thread-Topic: [homenet] Creating a security association via physical link + button
Thread-Index: AcysM8Dni867JYOGTUWdZCUGweTUMw==
Message-ID: <340EFC23-D685-497A-AF6A-374462017A10@ericsson.com>
References: <kkblj0mbs8xw8pp32w219ww6.1322224208905@email.android.com> <5B97FD15-7CE9-4FB8-88A4-36C4D0930BEF@fugue.com> <A23A4334-44A8-45ED-B3CB-B601C0021BF4@cisco.com> <BDF1CF4F-5282-4FCE-A1FD-51B8698EC47D@amalfisystems.com> <4ED0B6EC.8030404@gridmerge.com>
In-Reply-To: <4ED0B6EC.8030404@gridmerge.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/signed; boundary="Apple-Mail-6-404571228"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
Cc: "<homenet@ietf.org>" <homenet@ietf.org>
Subject: Re: [homenet] Creating a security association via physical link + button
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 26 Nov 2011 12:06:05 -0000

--Apple-Mail-6-404571228
Content-Type: multipart/alternative;
	boundary=Apple-Mail-5-404571208


--Apple-Mail-5-404571208
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

I agree - once we have a threat document, this should one of the =
security models on which we map the threats.=20
Thanks,
Acee
On Nov 26, 2011, at 4:52 AM, Robert Cragie wrote:

> I've been following this thread with interest. Some points (from =
someone who has a particular 802.15.4-based mesh networking viewpoint):
>=20
> There probably isn't any need to specify cryptographic security for an =
IGP on the basis that the packets are link-local and can therefore be =
protected at L2.
> Network access control can set up secure channels to deliver keying =
information. Therefore in theory this can be used to deliver keying =
information for any protocols, although in practice it is often just L2 =
keying information. The focus then turns to which credentials are used =
for network access control. Whilst I support the use of public key =
crypto., it is not essential for homenet and there are solutions (not =
perfect, IMHO, but adequate) which exist now for easy joining (e.g. WPS) =
based on a pre-shared key/passphrase. Having said that, the burden and =
complexity of using public key crypto. for network access and mutual =
authentication is perhaps not as great as one may think.
> The original question was about merging networks in the home. Again, I =
don't think it is that complex if dealt with from a network access point =
of view. Whether one becomes secondary and assumes the keying =
information from the primary network (probably preferable if the =
topology is a mesh) or the two simply join at a common router and retain =
their own keying information, either is possible and not difficult.
> Robert
>=20
> On 26/11/2011 6:18 AM, Randy Turner wrote:
>>=20
>>=20
>> You maybe right about the equivalent key-management scope, however, I =
believe any work in the key distribution area applied to the "integrity =
of routing updates" would pay off more than expending this effort on the =
"confidentiality of routing update" problem.  One of the devices we are =
considering as a "router" in the Homenet is a Windows machine where the =
end user has simply turned on internet connection sharing (ICS).  =
Assuming this machine is their home PC, we're talking about the target =
of practically every attack profile on the internet, so I think it's =
worth the effort to establish a trust model.  Even an android-based =
phone could inject false (untrusted) routes into the Homenet, but then =
again I'm getting ahead of myself in pre-supposing attack vectors on the =
Homenet.  I'm keeping an open mind on all of this until we have a =
document or other work that performs the due diligence on threats to the =
Homenet.
>>=20
>> Randy
>>=20
>> On Nov 25, 2011, at 5:17 PM, Mark Townsley wrote:
>>=20
>>>=20
>>> On Nov 25, 2011, at 6:28 PM, Ted Lemon wrote:
>>>=20
>>>> On Nov 25, 2011, at 7:30 AM, Randy Turner wrote:
>>>>> I think I agree that confidentiality of routing traffic is =
probably not an issue for Homenet - however, I do think we should =
consider integrity of routing traffic - ie, router A should "trust" that =
route updates from router B are correct.
>>>>=20
>>>> Exactly.
>>>=20
>>> I see no difference really between the difficulty between an =
integrity-only solution and a confidentiality solution. Both require =
keys. It's the keys that are the real problem, not the work done on the =
packets.
>>>=20
>>> And, yes, key exchange being hard is based on a certain amount of =
intuition for my part as well.=20
>>>=20
>>> - Mark
>>>=20
>>>>=20
>>>>> That being said, this is just an intuitive feeling regarding =
security - maybe we need someone to work on a threat analysis and what =
the implications could be to the types of applications we anticipate
>>>>=20
>>>>=20
>>>> Yes, I think this would be worthwhile.   I'm certainly arguing =
based on intuition at the moment.
>>>>=20
>>>> _______________________________________________
>>>> homenet mailing list
>>>> homenet@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/homenet
>>>=20
>>=20
>>=20
>>=20
>> _______________________________________________
>> homenet mailing list
>> homenet@ietf.org
>> https://www.ietf.org/mailman/listinfo/homenet


--Apple-Mail-5-404571208
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I agree - once we have a threat document, this should one of the security models on which we map the threats.&nbsp;<div>Thanks,</div><div>Acee<br><div><div>On Nov 26, 2011, at 4:52 AM, Robert Cragie wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">



<meta http-equiv="Content-Type" content="text/html; charset=utf-8">

<div bgcolor="#FFFFFF" text="#000000">
I've been following this thread with interest. Some points (from someone who has a particular 802.15.4-based mesh networking viewpoint):<br>
<br>
<ul>
<li>There probably isn't any need to specify cryptographic security for an IGP on the basis that the packets are link-local and can therefore be protected at L2.
</li><li>Network access control can set up secure channels to deliver keying information. Therefore in theory this can be used to deliver keying information for any protocols, although in practice it is often just L2 keying information. The focus then turns to which
 credentials are used for network access control. Whilst I support the use of public key crypto., it is not essential for homenet and there are solutions (not perfect, IMHO, but adequate) which exist now for easy joining (e.g. WPS) based on a pre-shared key/passphrase.
 Having said that, the burden and complexity of using public key crypto. for network access and mutual authentication is perhaps not as great as one may think.
</li><li>The original question was about merging networks in the home. Again, I don't think it is that complex if dealt with from a network access point of view. Whether one becomes secondary and assumes the keying information from the primary network (probably
 preferable if the topology is a mesh) or the two simply join at a common router and retain their own keying information, either is possible and not difficult.
</li></ul>
Robert<br>
<br>
On 26/11/2011 6:18 AM, Randy Turner wrote:
<blockquote cite="mid:BDF1CF4F-5282-4FCE-A1FD-51B8698EC47D@amalfisystems.com" type="cite">
<div><br>
</div>
You maybe right about the equivalent key-management scope, however, I believe any work in the key distribution area applied to the "integrity of routing updates" would pay off more than expending this effort on the "confidentiality of routing update" problem.
 &nbsp;One of the devices we are considering as a "router" in the Homenet is a Windows machine where the end user has simply turned on internet connection sharing (ICS). &nbsp;Assuming this machine is their home PC, we're talking about the target of practically every
 attack profile on the internet, so I think it's worth the effort to establish a trust model. &nbsp;Even an android-based phone could inject false (untrusted) routes into the Homenet, but then again I'm getting ahead of myself in pre-supposing attack vectors on
 the Homenet. &nbsp;I'm keeping an open mind on all of this until we have a document or other work that performs the due diligence on threats to the Homenet.
<div><br>
</div>
<div>Randy</div>
<div><br>
</div>
<div>
<div>
<div>On Nov 25, 2011, at 5:17 PM, Mark Townsley wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space;
              -webkit-line-break: after-white-space; ">
<br>
<div>
<div>On Nov 25, 2011, at 6:28 PM, Ted Lemon wrote:</div>
<br class="Apple-interchange-newline">
<blockquote type="cite">
<div style="word-wrap: break-word; -webkit-nbsp-mode:
                    space; -webkit-line-break: after-white-space; ">
<div>
<div>On Nov 25, 2011, at 7:30 AM, Randy Turner wrote:</div>
<blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family:
                          Helvetica; font-style: normal; font-variant:
                          normal; font-weight: normal; letter-spacing:
                          normal; line-height: normal; orphans: 2;
                          text-align: -webkit-auto; text-indent: 0px;
                          text-transform: none; white-space: normal;
                          widows: 2; word-spacing: 0px;
                          -webkit-border-horizontal-spacing: 0px;
                          -webkit-border-vertical-spacing: 0px;
                          -webkit-text-decorations-in-effect: none;
                          -webkit-text-size-adjust: auto;
                          -webkit-text-stroke-width: 0px; font-size:
                          medium; ">I
 think I agree that confidentiality of routing traffic is probably not an issue for Homenet - however, I do think we should consider integrity of routing traffic - ie, router A should "trust" that route updates from router B are correct.</span></blockquote>
<div><br>
</div>
<div>Exactly.</div>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>I see no difference really between the difficulty between an integrity-only solution and a confidentiality solution. Both require keys. It's the keys that are the real problem, not the work done on the packets.</div>
<div><br>
</div>
<div>And, yes, key exchange being hard is based on a certain amount of intuition for my part as well.&nbsp;</div>
<div><br>
</div>
<div>- Mark</div>
<br>
<blockquote type="cite">
<div style="word-wrap: break-word; -webkit-nbsp-mode:
                    space; -webkit-line-break: after-white-space; ">
<div><br>
<blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family:
                          Helvetica; font-style: normal; font-variant:
                          normal; font-weight: normal; letter-spacing:
                          normal; line-height: normal; orphans: 2;
                          text-align: -webkit-auto; text-indent: 0px;
                          text-transform: none; white-space: normal;
                          widows: 2; word-spacing: 0px;
                          -webkit-border-horizontal-spacing: 0px;
                          -webkit-border-vertical-spacing: 0px;
                          -webkit-text-decorations-in-effect: none;
                          -webkit-text-size-adjust: auto;
                          -webkit-text-stroke-width: 0px; font-size:
                          medium; ">That
 being said, this is just an intuitive feeling regarding security - maybe we need someone to work on a threat analysis and what the implications could be to the types of applications we anticipate</span></blockquote>
</div>
<div><br>
</div>
<div>Yes, I think this would be worthwhile. &nbsp; I'm certainly arguing based on intuition at the moment.</div>
<div><br>
</div>
</div>
_______________________________________________<br>
homenet mailing list<br>
<a moz-do-not-send="true" href="mailto:homenet@ietf.org">homenet@ietf.org</a><br>
<a moz-do-not-send="true" href="https://www.ietf.org/mailman/listinfo/homenet">https://www.ietf.org/mailman/listinfo/homenet</a><br>
</blockquote>
</div>
<br>
</div>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset> <br>
<pre wrap="">_______________________________________________
homenet mailing list
<a class="moz-txt-link-abbreviated" href="mailto:homenet@ietf.org">homenet@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/homenet">https://www.ietf.org/mailman/listinfo/homenet</a>
</pre>
</blockquote>
</div>

</blockquote></div><br></div></body></html>
--Apple-Mail-5-404571208--

--Apple-Mail-6-404571228
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIM8jCCBDQw
ggMcoAMCAQICECFWwVQHDV12M/Sr0yNv0sYwDQYJKoZIhvcNAQEFBQAwOTERMA8GA1UECgwIRXJp
Y3Nzb24xJDAiBgNVBAMMG0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMTAeFw0xMDEwMDEyMDA0
NTlaFw0xMzEwMDEyMDA0NDhaMG8xETAPBgNVBAoMCEVyaWNzc29uMR8wHQYDVQQDDBZBY2VlIExp
bmRlbSBMaW5kZW0gSUlJMRAwDgYDVQQFEwdlYWxmbGluMScwJQYJKoZIhvcNAQkBFhhhY2VlLmxp
bmRlbUBlcmljc3Nvbi5jb20wgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAI/Dc9ALiZuBMyuv
bsc3eBxjXZpMi45Z0vzsUQZTJGTBeY7p9JsdzXC9J1uMisBxYVi39R3KJo6I4hXVp9wrA1rxh4AE
bnP1+Gxfpj33uWEFYbBnVAJkIWYWF7CYTn8Zm/yd13vPXtuGA6ESeLnnJafwC9Y0YwUQ+4HX7PNv
uauVAgMBAAGjggGEMIIBgDCBwAYDVR0fBIG4MIG1MIGyoIGvoIGshjdodHRwOi8vY3JsLnRydXN0
LnRlbGlhLmNvbS9Fcmljc3Nvbk5MSW5kaXZpZHVhbENBMDEuY3JshnFsZGFwOi8vbGRhcC50cnVz
dC50ZWxpYS5jb20vY249RXJpY3Nzb24lMjBOTCUyMEluZGl2aWR1YWwlMjBDQTAxLG89RXJpY3Nz
b24/Y2VydGlmaWNhdGVyZXZvY2F0aW9ubGlzdDtiaW5hcnk/YmFzZTAjBgNVHREEHDAagRhhY2Vl
LmxpbmRlbUBlcmljc3Nvbi5jb20wRgYDVR0gBD8wPTA7BgYqhXBrAQEwMTAvBggrBgEFBQcCARYj
aHR0cDovL3d3dy5lcmljc3Nvbi5jb20vbGVnYWwuc2h0bWwwHQYDVR0OBBYEFAgOzAPuplmPr7C1
BTqV94OyqUdhMB8GA1UdIwQYMBaAFJYnw7jepV9dRD45UuVFsXZfYzCbMA4GA1UdDwEB/wQEAwIF
oDANBgkqhkiG9w0BAQUFAAOCAQEAE1gyNW6c2t/YsLxW5sm67+gVGK0Lnge4ub+k8dgGrK7Mj7em
nkOIFkjdv/tqdJ/SoUy/WEkBXba2TfpZ+lfluMgLYux1vSvqBUxYBsUHeNth2Q/Y6A9sCaDTBPlK
vZ2jLz814NavrVfgTCLdxX6zNtGdwzhviz+FyqyxYF43Q86RP8Gd/Npaz1W8pmYAHm0+lezuTx5k
F3Av3+SaZ/MR6s+RWuXEIdED36ajeQz+OG8Mh3nplofzdrOeoWGDz53YlfRhgj+TXo+H1lclZAvD
WVaMMXPdb27h9Hngsq87dkCW9uAyv8DI993rdhqzlEgUyQIL32icAXfTmTYgoGPOwjCCBEUwggMt
oAMCAQICEBPJ6v/eJq2p3KTKI4GDR+MwDQYJKoZIhvcNAQEFBQAwRDEaMBgGA1UECgwRVGVsaWFT
b25lcmEgR3JvdXAxJjAkBgNVBAMMHVRlbGlhU29uZXJhIFB1YmxpYyBSb290IENBIHYxMB4XDTA2
MTAwNjEwMDA1M1oXDTE2MTAwMjA1MDQxN1owOTERMA8GA1UECgwIRXJpY3Nzb24xJDAiBgNVBAMM
G0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoC
ggEBALYQd+Q1HuuHxDyNGFlEPzCxuPPFO5W2xyr+nqCVnNJ4QYFe1HACqavqNLwUGIqIEyHv1rLn
fub9LBc7dQpRHjl/dggin0ONOFJ36nbGEbfHjLJz2BzOWvwl84Sc+Fx09IrDU/SZSWFSfhqTu3TT
39h79brHdRkdPBUgBYgsiFKriHI0TjP5G8628H27BDzqUpzGLSYWgt6/tpwuOH5lcfNfHWMcCYXR
lobv0Klu8lxG5amWqAnqrH6ECOyYJTRbHTsaTIZOHy9Qw/0eXPujKT7tU5xxSI2SdceJqzUbAz2o
FRQ6Px7/GydpM/Rl+qYoGPcauHUL1aSeVJZqDFqcIF0CAwEAAaOCATwwggE4MBIGA1UdEwEB/wQI
MAYBAf8CAQAwRgYDVR0gBD8wPTA7BgcqhXAjAgEBMDAwLgYIKwYBBQUHAgEWImh0dHBzOi8vcmVw
b3NpdG9yeS50cnVzdC50ZWxpYS5jb20wgYkGA1UdHwSBgTB/MH2ge6B5hndsZGFwOi8vbGRhcC50
cnVzdC50ZWxpYS5jb20vY249VGVsaWFTb25lcmElMjBQdWJsaWMlMjBSb290JTIwQ0ElMjB2MSxv
PVRlbGlhU29uZXJhJTIwR3JvdXA/YXV0aG9yaXR5cmV2b2NhdGlvbmxpc3Q/YmFzZTAOBgNVHQ8B
Af8EBAMCAQYwHQYDVR0OBBYEFJYnw7jepV9dRD45UuVFsXZfYzCbMB8GA1UdIwQYMBaAFEXb8I+4
GmKhqCMbY4g4o9vgGmLxMA0GCSqGSIb3DQEBBQUAA4IBAQB2AEoqQz+M3Ra9alkpn/YnwhXIv6tP
jhUvSuNs00Nhd0T9XhlIU3a65CaB/UKSqnayE0t7Q0Qq3r+x/GK3in/mik8i/PK2/q8HutzYFSzz
6Npztpo2JG7AEKOJPVaeebjng45m6vNC7RIfzU9sG2LBR/hewS8s6dFFn70w795xUwJBWZ67OzIK
XrIVVvHTOYpbWA+MESKAXwFhnVONrOTWlVwrMUi4HbiPWpOk+xQbgehCEi7mu3cXsaU1Xq3kMXui
NuC7VKoob8mFO9o9RT+dlirD2uRXwNpvCu3but6Kyhu0+nvy2iXGKjdlxlWTsdDyulXYz+OYCMZ9
lFWRzMIPMIIEbTCCA1WgAwIBAgIRAJywjASay5cieGNithuGWj0wDQYJKoZIhvcNAQEFBQAwOjEZ
MBcGA1UEChMQUlNBIFNlY3VyaXR5IEluYzEdMBsGA1UECxMUUlNBIFNlY3VyaXR5IDIwNDggVjMw
HhcNMDYxMDMxMjA0MjI3WhcNMTYxMTAxMTU0MjI1WjBEMRowGAYDVQQKDBFUZWxpYVNvbmVyYSBH
cm91cDEmMCQGA1UEAwwdVGVsaWFTb25lcmEgUHVibGljIFJvb3QgQ0EgdjEwggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQDKTxADapCAq3mplX4R4gNt+WZe5QKGnaVEQSyY7lICKF5DuVdW
PMLHDjzhw5IzDd860ZZx/0VrhGB3DmP4SDIWCKo2PxvY5NckdBWPWp/T2uaQdOAwgqHpN0pe1X7/
jel59WsWYXKGg/81Wth73ZK/geE7Gz9Pvj1LU6N4YhLMgooxKnCS+ZjB5icWAg+Qd1QpQhF46H1i
bp6LsBWDp56MPpg8F5X6y7MGVcKYLdnLOPs84uxRW9qs1kBopzQBj6s5SyVh8A+j5liDBjghXYpw
/+paGEdqHPeSFYxZKeJatmjEKLYlxcZWRKf436KvQA9jBhMEmytMNbGicR1mRH6tAgMBAAGjggFi
MIIBXjAfBgNVHSMEGDAWgBQHw1EwpKrpRa41JPr/JCwz0LGdjDAdBgNVHQ4EFgQURdvwj7gaYqGo
IxtjiDij2+AaYvEwEgYDVR0TAQH/BAgwBgEB/wIBBDCBhQYDVR0gBH4wfDA9BgkqhkiG9w0FBgEw
MDAuBggrBgEFBQcCARYiaHR0cHM6Ly9yZXBvc2l0b3J5LnRydXN0LnRlbGlhLmNvbTA7BgcqhXAj
AgEBMDAwLgYIKwYBBQUHAgEWImh0dHBzOi8vcmVwb3NpdG9yeS50cnVzdC50ZWxpYS5jb20wcAYD
VR0fBGkwZzBloGOgYYZfaHR0cDovL3d3dy5yc2FzZWN1cml0eS5jb20vcHJvZHVjdHMva2Vvbi9y
ZXBvc2l0b3J5L2NlcnRpZmljYXRlX3N0YXR1cy9SU0FfU2VjdXJpdHlfMjA0OF92My5DUkwwDgYD
VR0PAQH/BAQDAgEGMA0GCSqGSIb3DQEBBQUAA4IBAQAEXpos2CnIm7/872ytSrEHWZgvhOUEkUm2
5PWf/XkWko41TaL9vIS1S6AdWChNqWmnYiS7GfaIiDM9s1D6K7hidWBDOm46bNdM3ZwhMyDCfkDJ
SgeJ0w+7YmjvChu7gWqDZCsbtZ5gA1ixCTdDnuZB67JGSPGW6r73coraDP8diOpiQouMvM6bKuTP
BH/1poLccsUxsKgrQ23JC9LWCRb8cYHkZjXFH1K44TsIl5Lne2oT0JI3pwdA2v6jO4p/OLHntP+n
pjwPbedMPUZkDYCkd3LSxj8c3JTxtA8SlPCtIHE1hh65xihg1JRIliSphrqr9kbfwHdeVxPdOI5G
tDYPMYICEjCCAg4CAQEwTTA5MREwDwYDVQQKDAhFcmljc3NvbjEkMCIGA1UEAwwbRXJpY3Nzb24g
TkwgSW5kaXZpZHVhbCBDQTAxAhAhVsFUBw1ddjP0q9Mjb9LGMAkGBSsOAwIaBQCgggEbMBgGCSqG
SIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMTEyNjEyMDU1NVowIwYJKoZI
hvcNAQkEMRYEFE5o0OzfH3oxfYA51fAwqqb1bK0UMFwGCSsGAQQBgjcQBDFPME0wOTERMA8GA1UE
CgwIRXJpY3Nzb24xJDAiBgNVBAMMG0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMQIQIVbBVAcN
XXYz9KvTI2/SxjBeBgsqhkiG9w0BCRACCzFPoE0wOTERMA8GA1UECgwIRXJpY3Nzb24xJDAiBgNV
BAMMG0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMQIQIVbBVAcNXXYz9KvTI2/SxjANBgkqhkiG
9w0BAQEFAASBgIJjYyr2E9D4xPmywndllgswtq6H9zGIT0/xkjVga86I2WP3JI3yc8fiwhXYuuvE
TanBe/WvVGCF7OMqGL2K2vfrWZEpoElLKpoq4BmVhe8YaEqY7794I2titfkrdblMemMA39moInc9
jnzH2iJ9W+XkE/fQGGNzXFAa6lTYlOwlAAAAAAAA

--Apple-Mail-6-404571228--

From mellon@fugue.com  Sat Nov 26 10:24:16 2011
Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E9C221F8B65 for <homenet@ietfa.amsl.com>; Sat, 26 Nov 2011 10:24:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.059
X-Spam-Level: 
X-Spam-Status: No, score=-2.059 tagged_above=-999 required=5 tests=[AWL=0.383,  BAYES_00=-2.599, HTML_MESSAGE=0.001, SUBJECT_FUZZY_TION=0.156]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nBinWnHqap4J for <homenet@ietfa.amsl.com>; Sat, 26 Nov 2011 10:24:15 -0800 (PST)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 9043A21F8B61 for <homenet@ietf.org>; Sat, 26 Nov 2011 10:24:15 -0800 (PST)
Received: from [IPv6:2001:470:1f07:1486:9808:31a:b4af:d6c7] (unknown [IPv6:2001:470:1f07:1486:9808:31a:b4af:d6c7]) by toccata.fugue.com (Postfix) with ESMTPSA id 6E0D223806D4; Sat, 26 Nov 2011 13:24:12 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: multipart/alternative; boundary="Apple-Mail=_B8D5D2F6-3343-4C7C-92EB-C4FDABC6BA27"
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <4ED0B6EC.8030404@gridmerge.com>
Date: Sat, 26 Nov 2011 13:24:03 -0500
Message-Id: <EDFBD7C6-2A64-4341-BBEC-0D73A7E4531A@fugue.com>
References: <kkblj0mbs8xw8pp32w219ww6.1322224208905@email.android.com> <5B97FD15-7CE9-4FB8-88A4-36C4D0930BEF@fugue.com> <A23A4334-44A8-45ED-B3CB-B601C0021BF4@cisco.com> <BDF1CF4F-5282-4FCE-A1FD-51B8698EC47D@amalfisystems.com> <4ED0B6EC.8030404@gridmerge.com>
To: robert.cragie@gridmerge.com
X-Mailer: Apple Mail (2.1251.1)
Cc: homenet@ietf.org
Subject: Re: [homenet] Creating a security association via physical link + button
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 26 Nov 2011 18:24:16 -0000

--Apple-Mail=_B8D5D2F6-3343-4C7C-92EB-C4FDABC6BA27
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

On Nov 26, 2011, at 4:52 AM, Robert Cragie wrote:
> Network access control can set up secure channels to deliver keying =
information.

It sounds like you're talking about some kind of central management =
software/protocol here.


--Apple-Mail=_B8D5D2F6-3343-4C7C-92EB-C4FDABC6BA27
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=iso-8859-1

<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Nov 26, 2011, at 4:52 AM, Robert Cragie wrote:</div><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">Network access control can set up secure channels to deliver keying information.</span></blockquote></div><br><div>It sounds like you're talking about some kind of central management software/protocol here.</div><div><br></div></body></html>
--Apple-Mail=_B8D5D2F6-3343-4C7C-92EB-C4FDABC6BA27--

From diego@tid.es  Sun Nov 27 13:50:00 2011
Return-Path: <diego@tid.es>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D7CD21F8C07 for <homenet@ietfa.amsl.com>; Sun, 27 Nov 2011 13:50:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.943
X-Spam-Level: 
X-Spam-Status: No, score=-5.943 tagged_above=-999 required=5 tests=[AWL=0.656,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z2baSV98bj3B for <homenet@ietfa.amsl.com>; Sun, 27 Nov 2011 13:49:59 -0800 (PST)
Received: from correo-bck.tid.es (correo-bck.tid.es [195.235.93.200]) by ietfa.amsl.com (Postfix) with ESMTP id 41D3A21F8BF0 for <homenet@ietf.org>; Sun, 27 Nov 2011 13:49:59 -0800 (PST)
Received: from sbrightmailg02.hi.inet (Sbrightmailg02.hi.inet [10.95.78.105]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LVC003X79Z9TJ@tid.hi.inet> for homenet@ietf.org; Sun, 27 Nov 2011 22:49:57 +0100 (MET)
Received: from vanvan (vanvan.hi.inet [10.95.78.49])	by sbrightmailg02.hi.inet (Symantec Messaging Gateway) with SMTP id FC.2F.21312.580B2DE4; Sun, 27 Nov 2011 22:49:57 +0100 (CET)
Received: from correo.tid.es (mailhost.hi.inet [10.95.64.100]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPS id <0LVC003X49Z9TJ@tid.hi.inet> for homenet@ietf.org; Sun, 27 Nov 2011 22:49:57 +0100 (MET)
Received: from EXCLU2K7.hi.inet ([10.95.67.65]) by htcasmad1.hi.inet ([192.168.0.1]) with mapi; Sun, 27 Nov 2011 22:49:57 +0100
Date: Sun, 27 Nov 2011 22:49:55 +0100
From: DIEGO LOPEZ GARCIA <diego@tid.es>
In-reply-to: <4ED04C42.2080809@riw.us>
To: "<homenet@ietf.org> Group" <homenet@ietf.org>
Message-id: <F9F264FB-3517-4761-91FF-E5E99AEF4FD8@tid.es>
MIME-version: 1.0
Content-type: text/plain; charset=utf-8
Content-language: en-US
Content-transfer-encoding: base64
Accept-Language: en-US
Thread-topic: [homenet] other routing options
Thread-index: AcytToChdGmMWLeMTxGwaAgRpfD2WA==
acceptlanguage: en-US
X-AuditID: 0a5f4e69-b7f1c6d000005340-c2-4ed2b085efbc
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupkleLIzCtJLcpLzFFi42Lhivcz1G3dcMnP4N5/dYv3iw6xODB6LFny kymAMYrLJiU1J7MstUjfLoEr4+SDOSwFHbwVkzdMYW1gvMPTxcjJISFgIvFhxUR2CFtM4sK9 9WxdjFwcQgLbGCX+r1sD5fxilNhy6D8jhNPIKLH+6zSwFhYBVYn9LxeA2WwC6hItR7+xgNjC AjoS3a+vsoLYnAJqEnen3geLiwgYSux8NJkJxOYVsJSYPv88O4QtKPFj8j2gGg4OZqA5U6bk goSZBcQlmltvskDYihLTFjUwgtiMQJd+P7WGCWKkrsSi45fYIGw9ia5J3VA1ohJ32tczQnwm ILFkz3lmCFtU4uXjf6wQv/SxSBw5NZFtAqPYLCRnzEI4YxaSM2YhOWMBI8sqRrHipKLM9IyS 3MTMnHQDI72MTL3MvNSSTYyQeMncwbh8p8ohRgEORiUe3gOfz/sJsSaWFVfmHmKU5GBSEuWd tv6SnxBfUn5KZUZicUZ8UWlOavEhRgkOZiURXg6QHG9KYmVValE+TEqGg0NJgncGSEqwKDU9 tSItMweYFGDSTBycIO08QO2dYO3FBYm5xZnpEPlTjJJS4rwFIAkBkERGaR5c7ytGcaAjhXmj QbI8wPQF1/UKaCATyD0zL4AMLElESEk1ME5anDXx+qUl13p/1BR9ql/Iev/X1vkC5VUXis/U 7Lx4Z+oe/5pyZa05nbZdd8NNblfEJF5pef3O6LDvktB7zFcUd9y/b1bSZ/SV7eL8I6GWZhEP l3T2TfmzfvNWxhb2mHf5/xi9O94tmXzM5cLOZzNSz93/P3EO67f5Jq1ZoTM/nL0jpLr5p6e0 EktxRqKhFnNRcSIA7jl0fRwDAAA=
References: <DCC302FAA9FE5F4BBA4DCAD4656937791452BBC0CC@PRVPEXVS03.corp.twcable.com> <CABONVQbMsY6MF_8q44XqGmdOMS6Odn+CjBEttaEs9rhmknwRxg@mail.gmail.com> <4ECCAFC3.5060903@globis.net> <DCC302FAA9FE5F4BBA4DCAD4656937791452BBC498@PRVPEXVS03.corp.twcable.com> <4ECD3608.5020502@globis.net> <BDF2740C082F6942820D95BAEB9E1A846E5B05@XMB-AMS-108.cisco.com> <B16D09C6-66AA-4FCC-9A3A-5CB2C2921523@nominet.org.uk> <5A35BCB0-B7B6-41FE-BA6E-2778D5D479AC@inf-net.nl> <4ECFE895.3080209@gmail.com> <4ED04C42.2080809@riw.us>
Subject: Re: [homenet] other routing options
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 27 Nov 2011 21:50:00 -0000

DQpPbiAyNiBOb3YgMjAxMSwgYXQgMDM6MTcgLCBSdXNzIFdoaXRlIHdyb3RlOg0KDQo+DQo+PiBU
UklMTCBpcyBub3QgYW4gSVAgcm91dGluZyBwcm90b2NvbC4gSXQncyBhIGxheWVyIDIgYnJpZGdp
bmcgcHJvdG9jb2wgbW9yZQ0KPj4gY29tcGxpY2F0ZWQgdGhhbiB0aGUgc3Bhbm5pbmcgdHJlZSwg
YW5kIHNlZW1zIGNvbXBsZXRlbHkgdW5uZWNlc3NhcnkgZm9yDQo+PiB0aGUgc21hbGwgc2l6ZSBv
ZiBicmlkZ2VkIG5ldHdvcmtzIHRvIGJlIGV4cGVjdGVkIGluIGhvbWVuZXRzLg0KPg0KPiBXaGF0
IG1pZ2h0IGFjdHVhbGx5IGJlIGlkZWFsIGlzIHNvbWV0aGluZyB0aGF0IGNhbiByb3V0ZSBib3Ro
IGF0IGxheWVyIDINCj4gYW5kIGF0IGxheWVyIDMgLS1JLmUuLCB0aGF0IGNhbiB0cmVhdCBsYXll
ciAyIGFuZCBsYXllciAzIHdpdGhpbiB0aGUNCj4gaG9tZSBpZGVudGljYWxseS4uLg0KDQoNCldl
IGhhdmUgYSBzYXlpbmcgaW4gU3BhbmlzaCBhYm91dCAia2lsbGluZyBmbGllcyB3aXRoIGNhbm5v
bmJhbGxzIiwgYW5kIHByb2JhYmx5IHdoYXQgSSBzdWdnZXN0IGhlcmUgd2lsbCBiZSwgYnV0IEkg
aGF2ZSBiZWVuIHRoZSB3aG9sZSB3ZWVrIHJlYWRpbmcgYW5kIGRpc2N1c3NpbmcgYWJvdXQgU2Vh
bWxlc3MgTVBMUywgYW5kIGl0IHNvdW5kZWQgcHJlY2lzZWx5IGxpa2UgeW91IHNhaWQuLi4NCg0K
DQotLQ0KIkVzdGEgdmV6IG5vIGZhbGxhcmVtb3MsIERvY3RvciBJbmZpZXJubyINCg0KRHIgRGll
Z28gUi4gTG9wZXoNClRlbGVmb25pY2EgSStEDQoNCmUtbWFpbDogZGllZ29AdGlkLmVzDQpUZWw6
ICAgICAgKzM0IDkxMyAxMjkgMDQxDQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLQ0KDQoNCg0KDQoNCg0KRXN0ZSBtZW5zYWplIHNlIGRpcmlnZSBleGNsdXNpdmFtZW50
ZSBhIHN1IGRlc3RpbmF0YXJpby4gUHVlZGUgY29uc3VsdGFyIG51ZXN0cmEgcG9sw610aWNhIGRl
IGVudsOtbyB5IHJlY2VwY2nDs24gZGUgY29ycmVvIGVsZWN0csOzbmljbyBlbiBlbCBlbmxhY2Ug
c2l0dWFkbyBtw6FzIGFiYWpvLg0KVGhpcyBtZXNzYWdlIGlzIGludGVuZGVkIGV4Y2x1c2l2ZWx5
IGZvciBpdHMgYWRkcmVzc2VlLiBXZSBvbmx5IHNlbmQgYW5kIHJlY2VpdmUgZW1haWwgb24gdGhl
IGJhc2lzIG9mIHRoZSB0ZXJtcyBzZXQgb3V0IGF0Lg0KaHR0cDovL3d3dy50aWQuZXMvRVMvUEFH
SU5BUy9kaXNjbGFpbWVyLmFzcHgNCg==

From joelja@bogus.com  Sun Nov 27 16:24:59 2011
Return-Path: <joelja@bogus.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E2FD21F8BBC for <homenet@ietfa.amsl.com>; Sun, 27 Nov 2011 16:24:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.539
X-Spam-Level: 
X-Spam-Status: No, score=-102.539 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B7XT-LRaqh-8 for <homenet@ietfa.amsl.com>; Sun, 27 Nov 2011 16:24:58 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 6112E21F8B75 for <homenet@ietf.org>; Sun, 27 Nov 2011 16:24:58 -0800 (PST)
Received: from Zorch.local (c-76-115-174-157.hsd1.wa.comcast.net [76.115.174.157]) (authenticated bits=0) by nagasaki.bogus.com (8.14.4/8.14.4) with ESMTP id pAS0OteJ028646 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NOT); Mon, 28 Nov 2011 00:24:56 GMT (envelope-from joelja@bogus.com)
Message-ID: <4ED2D4D1.1080907@bogus.com>
Date: Sun, 27 Nov 2011 16:24:49 -0800
From: Joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: DIEGO LOPEZ GARCIA <diego@tid.es>
References: <DCC302FAA9FE5F4BBA4DCAD4656937791452BBC0CC@PRVPEXVS03.corp.twcable.com> <CABONVQbMsY6MF_8q44XqGmdOMS6Odn+CjBEttaEs9rhmknwRxg@mail.gmail.com> <4ECCAFC3.5060903@globis.net> <DCC302FAA9FE5F4BBA4DCAD4656937791452BBC498@PRVPEXVS03.corp.twcable.com> <4ECD3608.5020502@globis.net> <BDF2740C082F6942820D95BAEB9E1A846E5B05@XMB-AMS-108.cisco.com> <B16D09C6-66AA-4FCC-9A3A-5CB2C2921523@nominet.org.uk> <5A35BCB0-B7B6-41FE-BA6E-2778D5D479AC@inf-net.nl> <4ECFE895.3080209@gmail.com> <4ED04C42.2080809@riw.us> <F9F264FB-3517-4761-91FF-E5E99AEF4FD8@tid.es>
In-Reply-To: <F9F264FB-3517-4761-91FF-E5E99AEF4FD8@tid.es>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (nagasaki.bogus.com [147.28.0.81]); Mon, 28 Nov 2011 00:24:57 +0000 (UTC)
Cc: "<homenet@ietf.org> Group" <homenet@ietf.org>
Subject: Re: [homenet] other routing options
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 28 Nov 2011 00:24:59 -0000

On 11/27/11 13:49 , DIEGO LOPEZ GARCIA wrote:
> 
> On 26 Nov 2011, at 03:17 , Russ White wrote:
> 
>> 
>>> TRILL is not an IP routing protocol. It's a layer 2 bridging
>>> protocol more complicated than the spanning tree, and seems
>>> completely unnecessary for the small size of bridged networks to
>>> be expected in homenets.
>> 
>> What might actually be ideal is something that can route both at
>> layer 2 and at layer 3 --I.e., that can treat layer 2 and layer 3
>> within the home identically...
> 
> 
> We have a saying in Spanish about "killing flies with cannonballs",
> and probably what I suggest here will be, but I have been the whole
> week reading and discussing about Seamless MPLS, and it sounded
> precisely like you said...

Having routing protocols that are in-fact agnostic about what AF they
are carrying as in the past proved useful when it was found necessary to
carry another one.

> 
> -- "Esta vez no fallaremos, Doctor Infierno"
> 
> Dr Diego R. Lopez Telefonica I+D
> 
> e-mail: diego@tid.es Tel:      +34 913 129 041 
> -----------------------------------------
> 
> 
> 
> 
> 
> 
> Este mensaje se dirige exclusivamente a su destinatario. Puede
> consultar nuestra polÃ­tica de envÃ­o y recepciÃ³n de correo electrÃ³nico
> en el enlace situado mÃ¡s abajo. This message is intended exclusively
> for its addressee. We only send and receive email on the basis of the
> terms set out at. http://www.tid.es/ES/PAGINAS/disclaimer.aspx 
> _______________________________________________ homenet mailing list 
> homenet@ietf.org https://www.ietf.org/mailman/listinfo/homenet
> 


From rturner@amalfisystems.com  Sun Nov 27 19:50:41 2011
Return-Path: <rturner@amalfisystems.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4470B21F8B74 for <homenet@ietfa.amsl.com>; Sun, 27 Nov 2011 19:50:41 -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=[none]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WPf6RY0sNbr4 for <homenet@ietfa.amsl.com>; Sun, 27 Nov 2011 19:50:40 -0800 (PST)
Received: from omr12.networksolutionsemail.com (omr12.networksolutionsemail.com [205.178.146.62]) by ietfa.amsl.com (Postfix) with ESMTP id ACC5221F8B72 for <homenet@ietf.org>; Sun, 27 Nov 2011 19:50:37 -0800 (PST)
Received: from cm-omr14 (mail.networksolutionsemail.com [205.178.146.50]) by omr12.networksolutionsemail.com (8.13.8/8.13.8) with ESMTP id pAS3oWEn002765 for <homenet@ietf.org>; Sun, 27 Nov 2011 22:50:34 -0500
Authentication-Results: cm-omr14 smtp.user=rturner@amalfisystems.com; auth=pass (CRAM-MD5)
X-Authenticated-UID: rturner@amalfisystems.com
Received: from [98.151.18.158] ([98.151.18.158:54022] helo=[192.168.1.109]) by cm-omr14 (envelope-from <rturner@amalfisystems.com>) (ecelerity 2.2.2.41 r(31179/31189)) with ESMTPA id B1/6D-24418-80503DE4; Sun, 27 Nov 2011 22:50:32 -0500
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Apple Message framework v1251.1)
From: Randy Turner <rturner@amalfisystems.com>
In-Reply-To: <4ED04C42.2080809@riw.us>
Date: Sun, 27 Nov 2011 19:50:33 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <50A98AAC-22F2-4622-847C-5117BCF6B828@amalfisystems.com>
References: <DCC302FAA9FE5F4BBA4DCAD4656937791452BBC0CC@PRVPEXVS03.corp.twcable.com>	<CABONVQbMsY6MF_8q44XqGmdOMS6Odn+CjBEttaEs9rhmknwRxg@mail.gmail.com><4ECCAFC3.5060903@globis.net><DCC302FAA9FE5F4BBA4DCAD4656937791452BBC498@PRVPEXVS03.corp.twcable.com>	<4ECD3608.5020502@globis.net>	<BDF2740C082F6942820D95BAEB9E1A846E5B05@XMB-AMS-108.cisco.com>	<B16D09C6-66AA-4FCC-9A3A-5CB2C2921523@nominet.org.uk> <5A35BCB0-B7B6-41FE-BA6E-2778D5D479AC@inf-net.nl> <4ECFE895.3080209@gmail.com> <4ED04C42.2080809@riw.us>
To: homenet@ietf.org
X-Mailer: Apple Mail (2.1251.1)
Subject: Re: [homenet] other routing options
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 28 Nov 2011 03:50:41 -0000

Should we be looking at what the IEEE p1905.1 group is doing=85their PAR =
reads like there may be some synergy between what we have been =
discussing and their scope of work. =20

Apologies if this has come up before=85

Randy


From lorenzo@google.com  Mon Nov 28 00:50:23 2011
Return-Path: <lorenzo@google.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A783E21F8C3A for <homenet@ietfa.amsl.com>; Mon, 28 Nov 2011 00:50:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.948
X-Spam-Level: 
X-Spam-Status: No, score=-100.948 tagged_above=-999 required=5 tests=[AWL=-0.728, BAYES_50=0.001, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, SUBJECT_FUZZY_TION=0.156, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6AF1r-pTBRWL for <homenet@ietfa.amsl.com>; Mon, 28 Nov 2011 00:50:23 -0800 (PST)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 9F5B121F8C44 for <homenet@ietf.org>; Mon, 28 Nov 2011 00:50:17 -0800 (PST)
Received: by ghrr18 with SMTP id r18so1036115ghr.31 for <homenet@ietf.org>; Mon, 28 Nov 2011 00:50:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=beta; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-system-of-record; bh=Vn+xXx1eW70/rrfZfZdn3hP1z9uXt3W8zSsWvfEfleA=; b=Jpbdu6nvTzSRjW7TLefKH3ET78ibQu7eOuGBlfRhBckq8CoUi51Rn+n6ESmr1ZyqWl vk2/vWkkIqLhCj6HzdKA==
Received: by 10.236.131.82 with SMTP id l58mr3600215yhi.36.1322470217276; Mon, 28 Nov 2011 00:50:17 -0800 (PST)
Received: by 10.236.131.82 with SMTP id l58mr3600206yhi.36.1322470217182; Mon, 28 Nov 2011 00:50:17 -0800 (PST)
MIME-Version: 1.0
Received: by 10.150.202.14 with HTTP; Mon, 28 Nov 2011 00:49:56 -0800 (PST)
In-Reply-To: <9956D114-4D15-4F60-A444-745857F12816@cisco.com>
References: <CAKD1Yr3Y=EO9siQkAuZd7LtqsOT_8GswWkPOoiJEhtvnULcytw@mail.gmail.com> <4ECB98BC.8070600@riw.us> <ACDC3C9F-85D2-4AF6-AA8C-2A2E6EEDC8EE@fugue.com> <CAKD1Yr26zO0Dbco35ngWhj4W0hv_d_zJTCcbB-SSKqPpQab=ig@mail.gmail.com> <5C87A581-B2FD-4A1B-AD6B-7823279631BE@fugue.com> <CAKD1Yr3zp1Gn1P-jDVgna2ViWeQiyCaTM=hTchpJq2snPSL-hw@mail.gmail.com> <9956D114-4D15-4F60-A444-745857F12816@cisco.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Mon, 28 Nov 2011 17:49:56 +0900
Message-ID: <CAKD1Yr37cmOsTopCXUs7hDh_HkwZD=Eh71pG8KM1xXvm+A-ZGQ@mail.gmail.com>
To: Mark Townsley <townsley@cisco.com>
Content-Type: multipart/alternative; boundary=20cf3011e203856fb304b2c79795
X-System-Of-Record: true
Cc: Russ White <russw@riw.us>, homenet@ietf.org, Ted Lemon <mellon@fugue.com>
Subject: Re: [homenet] Creating a security association via physical link + button
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 28 Nov 2011 08:50:23 -0000

--20cf3011e203856fb304b2c79795
Content-Type: text/plain; charset=ISO-8859-1

On Fri, Nov 25, 2011 at 17:43, Mark Townsley <townsley@cisco.com> wrote:

> Before we decide that we must have an IGP, that it must be
> cryptographically secured, and that we have to tackle key distribution for
> it, I'd like to take a step or two back from the routing protocol part of
> the equation.
>

I'm not saying we need to secure the IGP. I'm saying that we need homenet
devices to know if they're "part of the same homenet" or not. This is
important for border detection, among other things.

One easy way to do this, if you have an IGP anyway, is to say that all the
devices that are part of the same IGP domain, (and thus share the same
key), are on the same homenet. It might - just - be possible for users to
understand that to "join the network" you need "the password for the
network". Then all you need to do is find a way to share a key.

This simple solution falls over if a device needs to be part of two
homenets at the same time, or if you want to merge two homenets.

Is that clearer now?

--20cf3011e203856fb304b2c79795
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div class=3D"gmail_quote">On Fri, Nov 25, 2011 at 17:43, Mark Townsley <sp=
an dir=3D"ltr">&lt;<a href=3D"mailto:townsley@cisco.com">townsley@cisco.com=
</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">

<div style=3D"word-wrap:break-word"><div>Before we decide that we must have=
 an IGP, that it must be cryptographically secured, and that we have to tac=
kle key distribution for it, I&#39;d like to take a step or two back from t=
he routing protocol part of the equation.</div>

</div></blockquote><div><br></div><div>I&#39;m not saying we need to secure=
 the IGP. I&#39;m saying that we need homenet devices to know if they&#39;r=
e &quot;part of the same homenet&quot; or not. This is important for border=
 detection, among other things.</div>

<div><br></div><div>One easy way to do this, if you have an IGP anyway, is =
to say that all the devices that are part of the same IGP domain, (and thus=
 share the same key), are on the same homenet. It might - just - be possibl=
e for users to understand that to &quot;join the network&quot; you need &qu=
ot;the password for the network&quot;. Then all you need to do is find a wa=
y to share a key.</div>

<div><br></div><div>This simple solution falls over if a device needs to be=
 part of two homenets at the same time, or if you want to merge two homenet=
s.</div><div><br></div><div>Is that clearer now?</div></div>

--20cf3011e203856fb304b2c79795--

From acee.lindem@ericsson.com  Mon Nov 28 05:22:06 2011
Return-Path: <acee.lindem@ericsson.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5B1E21F8C7E for <homenet@ietfa.amsl.com>; Mon, 28 Nov 2011 05:22:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.442
X-Spam-Level: 
X-Spam-Status: No, score=-6.442 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, SUBJECT_FUZZY_TION=0.156]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LkuJPieJLxy1 for <homenet@ietfa.amsl.com>; Mon, 28 Nov 2011 05:22:06 -0800 (PST)
Received: from imr4.ericy.com (imr4.ericy.com [198.24.6.9]) by ietfa.amsl.com (Postfix) with ESMTP id 11C1621F8C7B for <homenet@ietf.org>; Mon, 28 Nov 2011 05:22:06 -0800 (PST)
Received: from eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) by imr4.ericy.com (8.14.3/8.14.3/Debian-9.1ubuntu1) with ESMTP id pASDLZad022546; Mon, 28 Nov 2011 07:21:36 -0600
Received: from EUSAACMS0702.eamcs.ericsson.se ([169.254.1.25]) by eusaamw0706.eamcs.ericsson.se ([147.117.20.31]) with mapi; Mon, 28 Nov 2011 08:21:27 -0500
From: Acee Lindem <acee.lindem@ericsson.com>
To: Lorenzo Colitti <lorenzo@google.com>
Date: Mon, 28 Nov 2011 08:21:26 -0500
Thread-Topic: [homenet] Creating a security association via physical link + button
Thread-Index: Acyt0KHire6IiBK+R8+0dpbLLu3TEg==
Message-ID: <21B4CB3E-5635-4200-AA83-EA2677A052CF@ericsson.com>
References: <CAKD1Yr3Y=EO9siQkAuZd7LtqsOT_8GswWkPOoiJEhtvnULcytw@mail.gmail.com> <4ECB98BC.8070600@riw.us>	<ACDC3C9F-85D2-4AF6-AA8C-2A2E6EEDC8EE@fugue.com> <CAKD1Yr26zO0Dbco35ngWhj4W0hv_d_zJTCcbB-SSKqPpQab=ig@mail.gmail.com> <5C87A581-B2FD-4A1B-AD6B-7823279631BE@fugue.com> <CAKD1Yr3zp1Gn1P-jDVgna2ViWeQiyCaTM=hTchpJq2snPSL-hw@mail.gmail.com> <9956D114-4D15-4F60-A444-745857F12816@cisco.com> <CAKD1Yr37cmOsTopCXUs7hDh_HkwZD=Eh71pG8KM1xXvm+A-ZGQ@mail.gmail.com>
In-Reply-To: <CAKD1Yr37cmOsTopCXUs7hDh_HkwZD=Eh71pG8KM1xXvm+A-ZGQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/signed; boundary="Apple-Mail-2-581902847"; protocol="application/pkcs7-signature"; micalg=sha1
MIME-Version: 1.0
Cc: Russ White <russw@riw.us>, Mark Townsley <townsley@cisco.com>, "homenet@ietf.org" <homenet@ietf.org>, Ted Lemon <mellon@fugue.com>
Subject: Re: [homenet] Creating a security association via physical link +	button
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 28 Nov 2011 13:22:06 -0000

--Apple-Mail-2-581902847
Content-Type: multipart/alternative;
	boundary=Apple-Mail-1-581902832


--Apple-Mail-1-581902832
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Nov 28, 2011, at 3:49 AM, Lorenzo Colitti wrote:

> On Fri, Nov 25, 2011 at 17:43, Mark Townsley <townsley@cisco.com> =
wrote:
> Before we decide that we must have an IGP, that it must be =
cryptographically secured, and that we have to tackle key distribution =
for it, I'd like to take a step or two back from the routing protocol =
part of the equation.
>=20
> I'm not saying we need to secure the IGP. I'm saying that we need =
homenet devices to know if they're "part of the same homenet" or not. =
This is important for border detection, among other things.
>=20
> One easy way to do this, if you have an IGP anyway, is to say that all =
the devices that are part of the same IGP domain, (and thus share the =
same key), are on the same homenet. It might - just - be possible for =
users to understand that to "join the network" you need "the password =
for the network". Then all you need to do is find a way to share a key.
>=20
> This simple solution falls over if a device needs to be part of two =
homenets at the same time, or if you want to merge two homenets.
>=20
> Is that clearer now?

I think the confusion stems from the fact that people have different =
views on both the HOMENET security requirements and the associated =
security operations model.=20

Acee=20



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


--Apple-Mail-1-581902832
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=us-ascii

<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Nov 28, 2011, at 3:49 AM, Lorenzo Colitti wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div class="gmail_quote">On Fri, Nov 25, 2011 at 17:43, Mark Townsley <span dir="ltr">&lt;<a href="mailto:townsley@cisco.com">townsley@cisco.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">

<div style="word-wrap:break-word"><div>Before we decide that we must have an IGP, that it must be cryptographically secured, and that we have to tackle key distribution for it, I'd like to take a step or two back from the routing protocol part of the equation.</div>

</div></blockquote><div><br></div><div>I'm not saying we need to secure the IGP. I'm saying that we need homenet devices to know if they're "part of the same homenet" or not. This is important for border detection, among other things.</div>

<div><br></div><div>One easy way to do this, if you have an IGP anyway, is to say that all the devices that are part of the same IGP domain, (and thus share the same key), are on the same homenet. It might - just - be possible for users to understand that to "join the network" you need "the password for the network". Then all you need to do is find a way to share a key.</div>

<div><br></div><div>This simple solution falls over if a device needs to be part of two homenets at the same time, or if you want to merge two homenets.</div><div><br></div><div>Is that clearer now?</div></div></blockquote><div><br></div><div>I think the confusion stems from the fact that people have different views on both the HOMENET security requirements and the associated security operations model.&nbsp;</div><div><br></div><div>Acee&nbsp;</div><div><br></div><div><br></div><br><blockquote type="cite">
_______________________________________________<br>homenet mailing list<br><a href="mailto:homenet@ietf.org">homenet@ietf.org</a><br>https://www.ietf.org/mailman/listinfo/homenet<br></blockquote></div><br></body></html>
--Apple-Mail-1-581902832--

--Apple-Mail-2-581902847
Content-Disposition: attachment; filename="smime.p7s"
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIM8jCCBDQw
ggMcoAMCAQICECFWwVQHDV12M/Sr0yNv0sYwDQYJKoZIhvcNAQEFBQAwOTERMA8GA1UECgwIRXJp
Y3Nzb24xJDAiBgNVBAMMG0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMTAeFw0xMDEwMDEyMDA0
NTlaFw0xMzEwMDEyMDA0NDhaMG8xETAPBgNVBAoMCEVyaWNzc29uMR8wHQYDVQQDDBZBY2VlIExp
bmRlbSBMaW5kZW0gSUlJMRAwDgYDVQQFEwdlYWxmbGluMScwJQYJKoZIhvcNAQkBFhhhY2VlLmxp
bmRlbUBlcmljc3Nvbi5jb20wgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAI/Dc9ALiZuBMyuv
bsc3eBxjXZpMi45Z0vzsUQZTJGTBeY7p9JsdzXC9J1uMisBxYVi39R3KJo6I4hXVp9wrA1rxh4AE
bnP1+Gxfpj33uWEFYbBnVAJkIWYWF7CYTn8Zm/yd13vPXtuGA6ESeLnnJafwC9Y0YwUQ+4HX7PNv
uauVAgMBAAGjggGEMIIBgDCBwAYDVR0fBIG4MIG1MIGyoIGvoIGshjdodHRwOi8vY3JsLnRydXN0
LnRlbGlhLmNvbS9Fcmljc3Nvbk5MSW5kaXZpZHVhbENBMDEuY3JshnFsZGFwOi8vbGRhcC50cnVz
dC50ZWxpYS5jb20vY249RXJpY3Nzb24lMjBOTCUyMEluZGl2aWR1YWwlMjBDQTAxLG89RXJpY3Nz
b24/Y2VydGlmaWNhdGVyZXZvY2F0aW9ubGlzdDtiaW5hcnk/YmFzZTAjBgNVHREEHDAagRhhY2Vl
LmxpbmRlbUBlcmljc3Nvbi5jb20wRgYDVR0gBD8wPTA7BgYqhXBrAQEwMTAvBggrBgEFBQcCARYj
aHR0cDovL3d3dy5lcmljc3Nvbi5jb20vbGVnYWwuc2h0bWwwHQYDVR0OBBYEFAgOzAPuplmPr7C1
BTqV94OyqUdhMB8GA1UdIwQYMBaAFJYnw7jepV9dRD45UuVFsXZfYzCbMA4GA1UdDwEB/wQEAwIF
oDANBgkqhkiG9w0BAQUFAAOCAQEAE1gyNW6c2t/YsLxW5sm67+gVGK0Lnge4ub+k8dgGrK7Mj7em
nkOIFkjdv/tqdJ/SoUy/WEkBXba2TfpZ+lfluMgLYux1vSvqBUxYBsUHeNth2Q/Y6A9sCaDTBPlK
vZ2jLz814NavrVfgTCLdxX6zNtGdwzhviz+FyqyxYF43Q86RP8Gd/Npaz1W8pmYAHm0+lezuTx5k
F3Av3+SaZ/MR6s+RWuXEIdED36ajeQz+OG8Mh3nplofzdrOeoWGDz53YlfRhgj+TXo+H1lclZAvD
WVaMMXPdb27h9Hngsq87dkCW9uAyv8DI993rdhqzlEgUyQIL32icAXfTmTYgoGPOwjCCBEUwggMt
oAMCAQICEBPJ6v/eJq2p3KTKI4GDR+MwDQYJKoZIhvcNAQEFBQAwRDEaMBgGA1UECgwRVGVsaWFT
b25lcmEgR3JvdXAxJjAkBgNVBAMMHVRlbGlhU29uZXJhIFB1YmxpYyBSb290IENBIHYxMB4XDTA2
MTAwNjEwMDA1M1oXDTE2MTAwMjA1MDQxN1owOTERMA8GA1UECgwIRXJpY3Nzb24xJDAiBgNVBAMM
G0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoC
ggEBALYQd+Q1HuuHxDyNGFlEPzCxuPPFO5W2xyr+nqCVnNJ4QYFe1HACqavqNLwUGIqIEyHv1rLn
fub9LBc7dQpRHjl/dggin0ONOFJ36nbGEbfHjLJz2BzOWvwl84Sc+Fx09IrDU/SZSWFSfhqTu3TT
39h79brHdRkdPBUgBYgsiFKriHI0TjP5G8628H27BDzqUpzGLSYWgt6/tpwuOH5lcfNfHWMcCYXR
lobv0Klu8lxG5amWqAnqrH6ECOyYJTRbHTsaTIZOHy9Qw/0eXPujKT7tU5xxSI2SdceJqzUbAz2o
FRQ6Px7/GydpM/Rl+qYoGPcauHUL1aSeVJZqDFqcIF0CAwEAAaOCATwwggE4MBIGA1UdEwEB/wQI
MAYBAf8CAQAwRgYDVR0gBD8wPTA7BgcqhXAjAgEBMDAwLgYIKwYBBQUHAgEWImh0dHBzOi8vcmVw
b3NpdG9yeS50cnVzdC50ZWxpYS5jb20wgYkGA1UdHwSBgTB/MH2ge6B5hndsZGFwOi8vbGRhcC50
cnVzdC50ZWxpYS5jb20vY249VGVsaWFTb25lcmElMjBQdWJsaWMlMjBSb290JTIwQ0ElMjB2MSxv
PVRlbGlhU29uZXJhJTIwR3JvdXA/YXV0aG9yaXR5cmV2b2NhdGlvbmxpc3Q/YmFzZTAOBgNVHQ8B
Af8EBAMCAQYwHQYDVR0OBBYEFJYnw7jepV9dRD45UuVFsXZfYzCbMB8GA1UdIwQYMBaAFEXb8I+4
GmKhqCMbY4g4o9vgGmLxMA0GCSqGSIb3DQEBBQUAA4IBAQB2AEoqQz+M3Ra9alkpn/YnwhXIv6tP
jhUvSuNs00Nhd0T9XhlIU3a65CaB/UKSqnayE0t7Q0Qq3r+x/GK3in/mik8i/PK2/q8HutzYFSzz
6Npztpo2JG7AEKOJPVaeebjng45m6vNC7RIfzU9sG2LBR/hewS8s6dFFn70w795xUwJBWZ67OzIK
XrIVVvHTOYpbWA+MESKAXwFhnVONrOTWlVwrMUi4HbiPWpOk+xQbgehCEi7mu3cXsaU1Xq3kMXui
NuC7VKoob8mFO9o9RT+dlirD2uRXwNpvCu3but6Kyhu0+nvy2iXGKjdlxlWTsdDyulXYz+OYCMZ9
lFWRzMIPMIIEbTCCA1WgAwIBAgIRAJywjASay5cieGNithuGWj0wDQYJKoZIhvcNAQEFBQAwOjEZ
MBcGA1UEChMQUlNBIFNlY3VyaXR5IEluYzEdMBsGA1UECxMUUlNBIFNlY3VyaXR5IDIwNDggVjMw
HhcNMDYxMDMxMjA0MjI3WhcNMTYxMTAxMTU0MjI1WjBEMRowGAYDVQQKDBFUZWxpYVNvbmVyYSBH
cm91cDEmMCQGA1UEAwwdVGVsaWFTb25lcmEgUHVibGljIFJvb3QgQ0EgdjEwggEiMA0GCSqGSIb3
DQEBAQUAA4IBDwAwggEKAoIBAQDKTxADapCAq3mplX4R4gNt+WZe5QKGnaVEQSyY7lICKF5DuVdW
PMLHDjzhw5IzDd860ZZx/0VrhGB3DmP4SDIWCKo2PxvY5NckdBWPWp/T2uaQdOAwgqHpN0pe1X7/
jel59WsWYXKGg/81Wth73ZK/geE7Gz9Pvj1LU6N4YhLMgooxKnCS+ZjB5icWAg+Qd1QpQhF46H1i
bp6LsBWDp56MPpg8F5X6y7MGVcKYLdnLOPs84uxRW9qs1kBopzQBj6s5SyVh8A+j5liDBjghXYpw
/+paGEdqHPeSFYxZKeJatmjEKLYlxcZWRKf436KvQA9jBhMEmytMNbGicR1mRH6tAgMBAAGjggFi
MIIBXjAfBgNVHSMEGDAWgBQHw1EwpKrpRa41JPr/JCwz0LGdjDAdBgNVHQ4EFgQURdvwj7gaYqGo
IxtjiDij2+AaYvEwEgYDVR0TAQH/BAgwBgEB/wIBBDCBhQYDVR0gBH4wfDA9BgkqhkiG9w0FBgEw
MDAuBggrBgEFBQcCARYiaHR0cHM6Ly9yZXBvc2l0b3J5LnRydXN0LnRlbGlhLmNvbTA7BgcqhXAj
AgEBMDAwLgYIKwYBBQUHAgEWImh0dHBzOi8vcmVwb3NpdG9yeS50cnVzdC50ZWxpYS5jb20wcAYD
VR0fBGkwZzBloGOgYYZfaHR0cDovL3d3dy5yc2FzZWN1cml0eS5jb20vcHJvZHVjdHMva2Vvbi9y
ZXBvc2l0b3J5L2NlcnRpZmljYXRlX3N0YXR1cy9SU0FfU2VjdXJpdHlfMjA0OF92My5DUkwwDgYD
VR0PAQH/BAQDAgEGMA0GCSqGSIb3DQEBBQUAA4IBAQAEXpos2CnIm7/872ytSrEHWZgvhOUEkUm2
5PWf/XkWko41TaL9vIS1S6AdWChNqWmnYiS7GfaIiDM9s1D6K7hidWBDOm46bNdM3ZwhMyDCfkDJ
SgeJ0w+7YmjvChu7gWqDZCsbtZ5gA1ixCTdDnuZB67JGSPGW6r73coraDP8diOpiQouMvM6bKuTP
BH/1poLccsUxsKgrQ23JC9LWCRb8cYHkZjXFH1K44TsIl5Lne2oT0JI3pwdA2v6jO4p/OLHntP+n
pjwPbedMPUZkDYCkd3LSxj8c3JTxtA8SlPCtIHE1hh65xihg1JRIliSphrqr9kbfwHdeVxPdOI5G
tDYPMYICEjCCAg4CAQEwTTA5MREwDwYDVQQKDAhFcmljc3NvbjEkMCIGA1UEAwwbRXJpY3Nzb24g
TkwgSW5kaXZpZHVhbCBDQTAxAhAhVsFUBw1ddjP0q9Mjb9LGMAkGBSsOAwIaBQCgggEbMBgGCSqG
SIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMTEyODEzMjEyNlowIwYJKoZI
hvcNAQkEMRYEFNplFnV0JhGQDOoVLh71vHgkpADwMFwGCSsGAQQBgjcQBDFPME0wOTERMA8GA1UE
CgwIRXJpY3Nzb24xJDAiBgNVBAMMG0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMQIQIVbBVAcN
XXYz9KvTI2/SxjBeBgsqhkiG9w0BCRACCzFPoE0wOTERMA8GA1UECgwIRXJpY3Nzb24xJDAiBgNV
BAMMG0VyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EwMQIQIVbBVAcNXXYz9KvTI2/SxjANBgkqhkiG
9w0BAQEFAASBgEI6PO+GqQ7APppJInYnWgHDrGWfoiZuVaSLVGqyyhBBU18c19RaIKa4gqw2V4Cw
XfY1xRi6upn/q5P/+4OyEg7Ht3ltae/BCcs1ajTZOCHvayFsUH7/KEjcdWZPJlTdCVg/Lw7Vvq2j
WvYdMqE3k+OgT5UM4BAcSnxQRd/SbjE3AAAAAAAA

--Apple-Mail-2-581902847--

From brian.e.carpenter@gmail.com  Mon Nov 28 13:35:36 2011
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A0DC11E80E8 for <homenet@ietfa.amsl.com>; Mon, 28 Nov 2011 13:35:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level: 
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id f3DOoancWigQ for <homenet@ietfa.amsl.com>; Mon, 28 Nov 2011 13:35:35 -0800 (PST)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id C57DE11E8085 for <homenet@ietf.org>; Mon, 28 Nov 2011 13:35:35 -0800 (PST)
Received: by ywm13 with SMTP id 13so4436403ywm.31 for <homenet@ietf.org>; Mon, 28 Nov 2011 13:35:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Zx8Mu9afxsFHadEX5lxrnDwXGbMY20oU3ncQsIOKCc8=; b=FsNqRez60qXlFMGQI9gjD7Vl3x1h6j2JE5rKJXtiyaE7dBoZ5U8nR9yDtosuO9kkKr 2z5DB7SVCIcoI1K3Q3AWCKia1K1RVSXFhLW14BhVczcHUR7fPPaUhBTPPtS3e2th6zAb +UX3p0YRxE0aS6GfIFAPZsAeRh4FBpeCQ/B6k=
Received: by 10.101.194.39 with SMTP id w39mr6055259anp.115.1322516135201; Mon, 28 Nov 2011 13:35:35 -0800 (PST)
Received: from [130.216.38.124] (stf-brian.sfac.auckland.ac.nz. [130.216.38.124]) by mx.google.com with ESMTPS id q5sm52824416yhm.7.2011.11.28.13.35.32 (version=SSLv3 cipher=OTHER); Mon, 28 Nov 2011 13:35:34 -0800 (PST)
Message-ID: <4ED3FEA1.6060009@gmail.com>
Date: Tue, 29 Nov 2011 10:35:29 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Russ White <russw@riw.us>
References: <DCC302FAA9FE5F4BBA4DCAD4656937791452BBC0CC@PRVPEXVS03.corp.twcable.com>	<CABONVQbMsY6MF_8q44XqGmdOMS6Odn+CjBEttaEs9rhmknwRxg@mail.gmail.com><4ECCAFC3.5060903@globis.net><DCC302FAA9FE5F4BBA4DCAD4656937791452BBC498@PRVPEXVS03.corp.twcable.com>	<4ECD3608.5020502@globis.net>	<BDF2740C082F6942820D95BAEB9E1A846E5B05@XMB-AMS-108.cisco.com>	<B16D09C6-66AA-4FCC-9A3A-5CB2C2921523@nominet.org.uk>	<5A35BCB0-B7B6-41FE-BA6E-2778D5D479AC@inf-net.nl>	<4ECFE895.3080209@gmail.com> <4ED04C42.2080809@riw.us>
In-Reply-To: <4ED04C42.2080809@riw.us>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: homenet@ietf.org
Subject: Re: [homenet] other routing options
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 28 Nov 2011 21:35:36 -0000

On 2011-11-26 15:17, Russ White wrote:
>> TRILL is not an IP routing protocol. It's a layer 2 bridging protocol more
>> complicated than the spanning tree, and seems completely unnecessary for
>> the small size of bridged networks to be expected in homenets.
> 
> What might actually be ideal is something that can route both at layer 2
> and at layer 3 --I.e., that can treat layer 2 and layer 3 within the
> home identically...

I have no doubt that if you convinced Radia about this, she could suggest
an IS-IS-TRILL variant that would achieve it.

But I'm not sure I really understand the need for it. There's no shortage
of IPv4 address space in homenets, because they are small and in RFC 1918
space. So if you are routing IPv6 in a home net, why not also route IPv4?

   Brian

From robert.cragie@gridmerge.com  Mon Nov 28 14:12:20 2011
Return-Path: <robert.cragie@gridmerge.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D1A6911E8125 for <homenet@ietfa.amsl.com>; Mon, 28 Nov 2011 14:12:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.442
X-Spam-Level: 
X-Spam-Status: No, score=-2.442 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, SUBJECT_FUZZY_TION=0.156]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M0SFzqFVhctp for <homenet@ietfa.amsl.com>; Mon, 28 Nov 2011 14:12:20 -0800 (PST)
Received: from mail78.extendcp.co.uk (mail78.extendcp.co.uk [79.170.40.78]) by ietfa.amsl.com (Postfix) with ESMTP id E213111E80FC for <homenet@ietf.org>; Mon, 28 Nov 2011 14:12:19 -0800 (PST)
Received: from client-86-31-198-101.oxfd.adsl.virginmedia.com ([86.31.198.101] helo=[192.168.0.2]) by mail78.extendcp.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) id 1RV9Qr-00014n-4l for homenet@ietf.org; Mon, 28 Nov 2011 22:12:13 +0000
Message-ID: <4ED40733.9050201@gridmerge.com>
Date: Mon, 28 Nov 2011 22:12:03 +0000
From: Robert Cragie <robert.cragie@gridmerge.com>
Organization: Gridmerge Ltd.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: homenet@ietf.org
References: <kkblj0mbs8xw8pp32w219ww6.1322224208905@email.android.com> <5B97FD15-7CE9-4FB8-88A4-36C4D0930BEF@fugue.com> <A23A4334-44A8-45ED-B3CB-B601C0021BF4@cisco.com> <BDF1CF4F-5282-4FCE-A1FD-51B8698EC47D@amalfisystems.com> <4ED0B6EC.8030404@gridmerge.com> <EDFBD7C6-2A64-4341-BBEC-0D73A7E4531A@fugue.com>
In-Reply-To: <EDFBD7C6-2A64-4341-BBEC-0D73A7E4531A@fugue.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms050901090506090501010403"
X-Authenticated-As: robert.cragie@gridmerge.com
Subject: Re: [homenet] Creating a security association via physical link + button
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: robert.cragie@gridmerge.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: Mon, 28 Nov 2011 22:12:20 -0000

This is a cryptographically signed message in MIME format.

--------------ms050901090506090501010403
Content-Type: multipart/alternative;
 boundary="------------000000060002030008020303"

This is a multi-part message in MIME format.
--------------000000060002030008020303
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable

Not necessarily. It could centralized, it could be distributed or=20
collaborative. Generally most edge networks have an access policy; it is =

rare to find a true open access network these days. If there is a=20
network access policy, a single node generally has to act as=20
authenticator for the purposes of network access (e.g. 802.1X/PANA/EAP=20
model). However, the capability to authenticate and authorize could be=20
distributed. Considering a ubiquitous model in the home now, there is an =

access point which acts as authenticator based on nodes joining with a=20
pre-shared key/passphrase, so that is a centralized function. Consider=20
how to extend that model to other networks in the home; if the homeowner =

essentially manages all the networks then other networks could simply=20
become subordinate and assume security parameters of the primary=20
network. If there is a need for another peer network, these could keep=20
their own security parameters and a common node would need to be=20
authenticated on both. When it comes to actual packet security, there=20
are also a number of possibilities, including group keying, network-wide =

keying or, depending on the network topology, node to access point keying=
=2E

Robert

On 26/11/2011 6:24 PM, Ted Lemon wrote:
> On Nov 26, 2011, at 4:52 AM, Robert Cragie wrote:
>> Network access control can set up secure channels to deliver keying=20
>> information.
>
> It sounds like you're talking about some kind of central management=20
> software/protocol here.
>
>
>
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet

--------------000000060002030008020303
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<html>
  <head>
    <meta content=3D"text/html; charset=3DISO-8859-1"
      http-equiv=3D"Content-Type">
  </head>
  <body bgcolor=3D"#FFFFFF" text=3D"#000000">
    Not necessarily. It could centralized, it could be distributed or
    collaborative. Generally most edge networks have an access policy;
    it is rare to find a true open access network these days. If there
    is a network access policy, a single node generally has to act as
    authenticator for the purposes of network access (e.g.
    802.1X/PANA/EAP model). However, the capability to authenticate and
    authorize could be distributed. Considering a ubiquitous model in
    the home now, there is an access point which acts as authenticator
    based on nodes joining with a pre-shared key/passphrase, so that is
    a centralized function. Consider how to extend that model to other
    networks in the home; if the homeowner essentially manages all the
    networks then other networks could simply become subordinate and
    assume security parameters of the primary network. If there is a
    need for another peer network, these could keep their own security
    parameters and a common node would need to be authenticated on both.
    When it comes to actual packet security, there are also a number of
    possibilities, including group keying, network-wide keying or,
    depending on the network topology, node to access point keying.<br>
    <br>
    Robert<br>
    <br>
    On 26/11/2011 6:24 PM, Ted Lemon wrote:
    <blockquote
      cite=3D"mid:EDFBD7C6-2A64-4341-BBEC-0D73A7E4531A@fugue.com"
      type=3D"cite">
      <div>
        <div>On Nov 26, 2011, at 4:52 AM, Robert Cragie wrote:</div>
        <blockquote type=3D"cite"><span class=3D"Apple-style-span"
            style=3D"border-collapse: separate; font-family: Helvetica;
            font-style: normal; font-variant: normal; font-weight:
            normal; letter-spacing: normal; line-height: normal;
            orphans: 2; text-align: -webkit-auto; text-indent: 0px;
            text-transform: none; white-space: normal; widows: 2;
            word-spacing: 0px; -webkit-border-horizontal-spacing: 0px;
            -webkit-border-vertical-spacing: 0px;
            -webkit-text-decorations-in-effect: none;
            -webkit-text-size-adjust: auto; -webkit-text-stroke-width:
            0px; font-size: medium; ">Network access control can set up
            secure channels to deliver keying information.</span></blockq=
uote>
      </div>
      <br>
      <div>It sounds like you're talking about some kind of central
        management software/protocol here.</div>
      <div><br>
      </div>
      <br>
      <fieldset class=3D"mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap=3D"">_______________________________________________
homenet mailing list
<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:homenet@ietf.org">ho=
menet@ietf.org</a>
<a class=3D"moz-txt-link-freetext" href=3D"https://www.ietf.org/mailman/l=
istinfo/homenet">https://www.ietf.org/mailman/listinfo/homenet</a>
</pre>
    </blockquote>
  </body>
</html>

--------------000000060002030008020303--

--------------ms050901090506090501010403
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIP3jCC
BIowggNyoAMCAQICECf06hH0eobEbp27bqkXBwcwDQYJKoZIhvcNAQEFBQAwbzELMAkGA1UE
BhMCU0UxFDASBgNVBAoTC0FkZFRydXN0IEFCMSYwJAYDVQQLEx1BZGRUcnVzdCBFeHRlcm5h
bCBUVFAgTmV0d29yazEiMCAGA1UEAxMZQWRkVHJ1c3QgRXh0ZXJuYWwgQ0EgUm9vdDAeFw0w
NTA2MDcwODA5MTBaFw0yMDA1MzAxMDQ4MzhaMIGuMQswCQYDVQQGEwJVUzELMAkGA1UECBMC
VVQxFzAVBgNVBAcTDlNhbHQgTGFrZSBDaXR5MR4wHAYDVQQKExVUaGUgVVNFUlRSVVNUIE5l
dHdvcmsxITAfBgNVBAsTGGh0dHA6Ly93d3cudXNlcnRydXN0LmNvbTE2MDQGA1UEAxMtVVRO
LVVTRVJGaXJzdC1DbGllbnQgQXV0aGVudGljYXRpb24gYW5kIEVtYWlsMIIBIjANBgkqhkiG
9w0BAQEFAAOCAQ8AMIIBCgKCAQEAsjmFpPJ9q0E7YkY3rs3BYHW8OWX5ShpHornMSMxqmNVN
NRm5pELlzkniii8efNIxB8dOtINknS4p1aJkxIW9hVE1eaROaJB7HHqkkqgX8pgV8pPMyaQy
lbsMTzC9mKALi+VuG6JG+ni8om+rWV6lL8/K2m2qL+usobNqqrcuZzWLeeEeaYji5kbNoKXq
vgvOdjp6Dpvq/NonWz1zHyLmSGHGTPNpsaguG7bUMSAsvIKKjqQOpdeJQ/wWWq8dcdcRWdq6
hw2v+vPhwvCkxWeM1tZUOt4KpLoDd7NlyP0e03RiqhjKaJMeoYV+9Udly/hNVyh00jT/MLbu
9mIwFIws6wIDAQABo4HhMIHeMB8GA1UdIwQYMBaAFK29mHo0tCb3+sQmVO8DveAky1QaMB0G
A1UdDgQWBBSJgmd9xJ0mcABLtFBIfN49rgRufTAOBgNVHQ8BAf8EBAMCAQYwDwYDVR0TAQH/
BAUwAwEB/zB7BgNVHR8EdDByMDigNqA0hjJodHRwOi8vY3JsLmNvbW9kb2NhLmNvbS9BZGRU
cnVzdEV4dGVybmFsQ0FSb290LmNybDA2oDSgMoYwaHR0cDovL2NybC5jb21vZG8ubmV0L0Fk
ZFRydXN0RXh0ZXJuYWxDQVJvb3QuY3JsMA0GCSqGSIb3DQEBBQUAA4IBAQAZ2IkRbyispgCi
54fBm5AD236hEv0e8+LwAamUVEJrmgnEoG3XkJIEA2Z5Q3H8+G+v23ZF4jcaPd3kWQR4rBz0
g0bzes9bhHIt5UbBuhgRKfPLSXmHPLptBZ2kbWhPrXIUNqi5sf2/z3/wpGqUNVCPz4FtVbHd
WTBK322gnGQfSXzvNrv042n0+DmPWq1LhTq3Du3Tzw1EovsEv+QvcI4l+1pUBrPQxLxtjftz
Mizpm4QkLdZ/kXpoAlAfDj9N6cz1u2fo3BwuO/xOzf4CjuOoEwqlJkRl6RDyTVKnrtw+ymsy
XEFs/vVdoOr/0fqbhlhtPZZH5f4ulQTCAMyOofK7MIIFGjCCBAKgAwIBAgIQbRnqpxlPajMi
5iIyeqpx3jANBgkqhkiG9w0BAQUFADCBrjELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAlVUMRcw
FQYDVQQHEw5TYWx0IExha2UgQ2l0eTEeMBwGA1UEChMVVGhlIFVTRVJUUlVTVCBOZXR3b3Jr
MSEwHwYDVQQLExhodHRwOi8vd3d3LnVzZXJ0cnVzdC5jb20xNjA0BgNVBAMTLVVUTi1VU0VS
Rmlyc3QtQ2xpZW50IEF1dGhlbnRpY2F0aW9uIGFuZCBFbWFpbDAeFw0xMTA0MjgwMDAwMDBa
Fw0yMDA1MzAxMDQ4MzhaMIGTMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3JlYXRlciBNYW5j
aGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0EgTGltaXRlZDE5
MDcGA1UEAxMwQ09NT0RPIENsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgU2VjdXJlIEVtYWls
IENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAkoSEW0tXmNReL4uk4UDIo1NY
X2Zl8TJO958yfVXQeExVt0KU4PkncQfFxmmkuTLE8UAakMwnVmJ/F7Vxaa7lIBvky2NeYMqi
QfZq4aP/uN8fSG1lQ4wqLitjOHffsReswtqCAtbUMmrUZ28gE49cNfrlVICv2HEKHTcKAlBT
bJUdqRAUtJmVWRIx/wmi0kzcUtve4kABW0ho3cVKtODtJB86r3FfB+OsvxQ7sCVxaD30D9YX
WEYVgTxoi4uDD216IVfmNLDbMn7jSuGlUnJkJpFOpZIP/+CxYP0ab2hRmWONGoulzEKbm30i
Y9OpoPzOnpDfRBn0XFs1uhbzp5v/wQIDAQABo4IBSzCCAUcwHwYDVR0jBBgwFoAUiYJnfcSd
JnAAS7RQSHzePa4Ebn0wHQYDVR0OBBYEFHoTTgB0W8Z4Y2QnwS/ioFu8ecV7MA4GA1UdDwEB
/wQEAwIBBjASBgNVHRMBAf8ECDAGAQH/AgEAMBEGA1UdIAQKMAgwBgYEVR0gADBYBgNVHR8E
UTBPME2gS6BJhkdodHRwOi8vY3JsLnVzZXJ0cnVzdC5jb20vVVROLVVTRVJGaXJzdC1DbGll
bnRBdXRoZW50aWNhdGlvbmFuZEVtYWlsLmNybDB0BggrBgEFBQcBAQRoMGYwPQYIKwYBBQUH
MAKGMWh0dHA6Ly9jcnQudXNlcnRydXN0LmNvbS9VVE5BZGRUcnVzdENsaWVudF9DQS5jcnQw
JQYIKwYBBQUHMAGGGWh0dHA6Ly9vY3NwLnVzZXJ0cnVzdC5jb20wDQYJKoZIhvcNAQEFBQAD
ggEBAIXWvnhXVW0zf0RS/kLVBqgBA4CK+w2y/Uq/9q9BSfUbWsXSrRtzbj7pJnzmTJjBMCjf
y/tCPKElPgp11tA9OYZm0aGbtU2bb68obB2v5ep0WqjascDxdXovnrqTecr+4pEeVnSy+I3T
4ENyG+2P/WA5IEf7i686ZUg8mD2lJb+972DgSeUWyOs/Q4Pw4O4NwdPNM1+b0L1garM7/vrU
yTo8H+2b/5tJM75CKTmD7jNpLoKdRU2oadqAGx490hpdfEeZpZsIbRKZhtZdVwcbpzC+S0lE
uJB+ytF5OOu0M/qgOl0mWJ5hVRi0IdWZ1eBDQEIwvuql55TSsP7zdfl/bucwggYuMIIFFqAD
AgECAhBcMVDbxC2oy5hyHl/adO9mMA0GCSqGSIb3DQEBBQUAMIGTMQswCQYDVQQGEwJHQjEb
MBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQK
ExFDT01PRE8gQ0EgTGltaXRlZDE5MDcGA1UEAxMwQ09NT0RPIENsaWVudCBBdXRoZW50aWNh
dGlvbiBhbmQgU2VjdXJlIEVtYWlsIENBMB4XDTExMDkwMjAwMDAwMFoXDTE0MDkwMTIzNTk1
OVowggE3MQswCQYDVQQGEwJHQjEQMA4GA1UEERMHV0Y0IDRXQTEXMBUGA1UECBMOV2VzdCBZ
b3Jrc2hpcmUxEjAQBgNVBAcTCVdha2VmaWVsZDEUMBIGA1UECRMLR3JhbmdlIE1vb3IxHzAd
BgNVBAkTFjg5IEdyZWVuZmllbGQgQ3Jlc2NlbnQxFzAVBgNVBAoTDkdyaWRtZXJnZSBMdGQu
MTQwMgYDVQQLEytJc3N1ZWQgdGhyb3VnaCBHcmlkbWVyZ2UgTHRkLiBFLVBLSSBNYW5hZ2Vy
MR8wHQYDVQQLExZDb3Jwb3JhdGUgU2VjdXJlIEVtYWlsMRYwFAYDVQQDEw1Sb2JlcnQgQ3Jh
Z2llMSowKAYJKoZIhvcNAQkBFhtyb2JlcnQuY3JhZ2llQGdyaWRtZXJnZS5jb20wggEiMA0G
CSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCtxOGq8t5ZTVDVkmadv7ZRBLA5ApaiTcDUzCTn
zYB2/BoBDIEWWI/InSRcmq3A0Ghm+T7dYmvRADllGv4nTHexdWlzFp2iM/Yc3PLWCyAO0gYb
yW2hTi+ZfUDwFOU4hRP4+Dyn9tKu7FXS/PQJHyGjaGxHRmLm9T6tAo2ZuC59uRaGVCcwRiOS
d6axwtB/DVhnP3S1rrt2g0O6MXLr5fojToemO52AxjHxt2w1LnFUUXC4EDV6o1Ctr7EvOEI5
5f088H/Mrryp02GueLdY9gb0SFK3gPOT7EjP2GPvCtRkhVcNM+xjyptRIFWnCbMjmUIc+DO6
sfU4rtbCCkNKyXmnAgMBAAGjggHVMIIB0TAfBgNVHSMEGDAWgBR6E04AdFvGeGNkJ8Ev4qBb
vHnFezAdBgNVHQ4EFgQUEI5c0f6UObxT2DLdvdtG+vG8qCswDgYDVR0PAQH/BAQDAgWgMAwG
A1UdEwEB/wQCMAAwHQYDVR0lBBYwFAYIKwYBBQUHAwQGCCsGAQUFBwMCMEYGA1UdIAQ/MD0w
OwYMKwYBBAGyMQECAQMFMCswKQYIKwYBBQUHAgEWHWh0dHBzOi8vc2VjdXJlLmNvbW9kby5u
ZXQvQ1BTMFcGA1UdHwRQME4wTKBKoEiGRmh0dHA6Ly9jcmwuY29tb2RvY2EuY29tL0NPTU9E
T0NsaWVudEF1dGhlbnRpY2F0aW9uYW5kU2VjdXJlRW1haWxDQS5jcmwwgYgGCCsGAQUFBwEB
BHwwejBSBggrBgEFBQcwAoZGaHR0cDovL2NydC5jb21vZG9jYS5jb20vQ09NT0RPQ2xpZW50
QXV0aGVudGljYXRpb25hbmRTZWN1cmVFbWFpbENBLmNydDAkBggrBgEFBQcwAYYYaHR0cDov
L29jc3AuY29tb2RvY2EuY29tMCYGA1UdEQQfMB2BG3JvYmVydC5jcmFnaWVAZ3JpZG1lcmdl
LmNvbTANBgkqhkiG9w0BAQUFAAOCAQEAPpv87QuQ9q+RHhmeirGDQB3szd24Obi7N+uVfh5y
CrnoJx3B37dNrLPsTB6PfTChUyZMqQD80pFoJ3TBUz3yx4X+hmNco7ujVIfbuKBGcZJaMKhZ
ex3AkZ9ltie9wgiGGzEmgI81t5JHsLQ8AUMqw/fGsnIwcyWMgmyhFtm79+dg3IVaH05d/t9g
k4aYoMoCFJptQZ+Fju6a9T139hOqjTZDpjMLt3jM80bVrvkC4dIRyF/oZ0qrJwbfwjnL2OUN
ph9eymhLc+VM0Ih5k41s5IxmB+2c0RUqr5JbK0WrIb/z53Cmb9rXYox7HknyIfBpQqP77Y7a
sAU2MMOpel4RijGCBAwwggQIAgEBMIGoMIGTMQswCQYDVQQGEwJHQjEbMBkGA1UECBMSR3Jl
YXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYDVQQKExFDT01PRE8gQ0Eg
TGltaXRlZDE5MDcGA1UEAxMwQ09NT0RPIENsaWVudCBBdXRoZW50aWNhdGlvbiBhbmQgU2Vj
dXJlIEVtYWlsIENBAhBcMVDbxC2oy5hyHl/adO9mMAkGBSsOAwIaBQCgggI4MBgGCSqGSIb3
DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTExMTEyODIyMTIwM1owIwYJKoZI
hvcNAQkEMRYEFNjoiVy+dSYOw2ALnWkntkz6xATBMF8GCSqGSIb3DQEJDzFSMFAwCwYJYIZI
AWUDBAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggqhkiG9w0DAgIBQDAHBgUr
DgMCBzANBggqhkiG9w0DAgIBKDCBuQYJKwYBBAGCNxAEMYGrMIGoMIGTMQswCQYDVQQGEwJH
QjEbMBkGA1UECBMSR3JlYXRlciBNYW5jaGVzdGVyMRAwDgYDVQQHEwdTYWxmb3JkMRowGAYD
VQQKExFDT01PRE8gQ0EgTGltaXRlZDE5MDcGA1UEAxMwQ09NT0RPIENsaWVudCBBdXRoZW50
aWNhdGlvbiBhbmQgU2VjdXJlIEVtYWlsIENBAhBcMVDbxC2oy5hyHl/adO9mMIG7BgsqhkiG
9w0BCRACCzGBq6CBqDCBkzELMAkGA1UEBhMCR0IxGzAZBgNVBAgTEkdyZWF0ZXIgTWFuY2hl
c3RlcjEQMA4GA1UEBxMHU2FsZm9yZDEaMBgGA1UEChMRQ09NT0RPIENBIExpbWl0ZWQxOTA3
BgNVBAMTMENPTU9ETyBDbGllbnQgQXV0aGVudGljYXRpb24gYW5kIFNlY3VyZSBFbWFpbCBD
QQIQXDFQ28QtqMuYch5f2nTvZjANBgkqhkiG9w0BAQEFAASCAQCEzGkmzkXfjF+j/p4ADOKt
clussaZ2W0jq9AuzDkN08WP5WuD0zWbwXJqJBpgOTycDo//CTo7Qj/AxWUn5xktjZuww8bwA
c4J9XcAfJjX2i37U82yEAQplLIm1hcdKyqoSveX9igI7EYlOuvwu4kTsA05mlYH5uTOPPkvs
HoA77dVdoXoyxfhHNKd6Fj4i6mOF9IzXpPiD/ATrCKpveGTCrI8FqcYsfbrfA0vxf+PjrF60
NdJ5u6+ETty2HNf/QsK/ZC5Rltv435TV8HN/zD724Ab1We/RxJLXuNUEzrGq8kgtjEouKPX2
8drdD/duyQ6hD1YRwbd1YanYT3zbw2YyAAAAAAAA
--------------ms050901090506090501010403--

From mark@mbaugher.com  Mon Nov 28 15:57:38 2011
Return-Path: <mark@mbaugher.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D3CF11E80BA for <homenet@ietfa.amsl.com>; Mon, 28 Nov 2011 15:57:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.443
X-Spam-Level: 
X-Spam-Status: No, score=-2.443 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, SUBJECT_FUZZY_TION=0.156]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PAJC1XxmYn3I for <homenet@ietfa.amsl.com>; Mon, 28 Nov 2011 15:57:38 -0800 (PST)
Received: from agora.rdrop.com (agora.rdrop.com [IPv6:2607:f678:1010::34]) by ietfa.amsl.com (Postfix) with ESMTP id EC11E11E8097 for <homenet@ietf.org>; Mon, 28 Nov 2011 15:57:37 -0800 (PST)
Received: from sjc-mbaugher-8715.cisco.com (128-107-239-233.cisco.com [128.107.239.233]) (authenticated bits=0) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id pASNvXUe070145 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for <homenet@ietf.org>; Mon, 28 Nov 2011 15:57:34 -0800 (PST) (envelope-from mark@mbaugher.com)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
From: Mark Baugher <mark@mbaugher.com>
In-Reply-To: <4ED40733.9050201@gridmerge.com>
Date: Mon, 28 Nov 2011 15:57:32 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <883A3AB7-4D48-40CE-BE1F-C90A47CB6CD8@mbaugher.com>
References: <kkblj0mbs8xw8pp32w219ww6.1322224208905@email.android.com> <5B97FD15-7CE9-4FB8-88A4-36C4D0930BEF@fugue.com> <A23A4334-44A8-45ED-B3CB-B601C0021BF4@cisco.com> <BDF1CF4F-5282-4FCE-A1FD-51B8698EC47D@amalfisystems.com> <4ED0B6EC.8030404@gridmerge.com> <EDFBD7C6-2A64-4341-BBEC-0D73A7E4531A@fugue.com> <4ED40733.9050201@gridmerge.com>
To: homenet@ietf.org
X-Mailer: Apple Mail (2.1084)
Subject: Re: [homenet] Creating a security association via physical link + button
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 28 Nov 2011 23:57:38 -0000

In my experience, there is no single mechanism for establishing what is =
alternatively called 'pairing,' 'introduction,'  'enrollment,' on in the =
case of the WiFi Protected Setup a 'mental model.'  The techniques have =
been called "ceremonies" by Carl Ellison and Jesse Walker, and they =
serve as a replacement for a system administrator in an unmanaged =
network by automating the process of adding an authorization, such as to =
a public key, username/password or other credential.  The security rests =
on showing locality and control of the device, which doesn't work well =
if the gateway or device is in some publicly-accessible location, which =
is usually not the case in a home.  The efficacy of any particular =
technique depends on the capabilities of the devices that are being =
paired.  Some research at UC-Irvine, for example, suggests that a short =
authentication string is the most usable method for most people in cases =
where there is a keypad or display.  In other cases, the USB key and =
push-button configuration techniques may be suitable.   I am not aware =
of any studies that push button is a particularly intuitive HCI for most =
people.   PBC uses weak identification and has a lot of vulnerabilities =
that require various mechanisms such as "walk time" in the WPS =
specification.

For homenet, I would expect that we would use or adapt the 'mental =
models' of the WiFi Alliance for our purposes.   Or at least we should =
consider this course.  In the case of the NFC mental model, I believe =
that particular method has been withdrawn by the WFA due to a dearth of =
shipped implementations that use it.  I am also not aware of =
interoperable implementations of the USB key WPS technique.  As I =
understand it, new techniques can be introduced or deprecated techniques =
can be re-introduced at the behest of interested parties.

Mark


From bs7652@att.com  Tue Nov 29 10:04:16 2011
Return-Path: <bs7652@att.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD28621F8BBD for <homenet@ietfa.amsl.com>; Tue, 29 Nov 2011 10:04:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.27
X-Spam-Level: 
X-Spam-Status: No, score=-106.27 tagged_above=-999 required=5 tests=[AWL=0.172, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, SUBJECT_FUZZY_TION=0.156, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 42+qcXXj1A9g for <homenet@ietfa.amsl.com>; Tue, 29 Nov 2011 10:04:16 -0800 (PST)
Received: from mail119.messagelabs.com (mail119.messagelabs.com [216.82.241.195]) by ietfa.amsl.com (Postfix) with ESMTP id D4B9721F86B3 for <homenet@ietf.org>; Tue, 29 Nov 2011 10:04:15 -0800 (PST)
X-Env-Sender: bs7652@att.com
X-Msg-Ref: server-12.tower-119.messagelabs.com!1322589852!3360507!1
X-Originating-IP: [144.160.20.146]
X-StarScan-Version: 6.3.6; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 32440 invoked from network); 29 Nov 2011 18:04:12 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpd194.enaf.sfdc.sbc.com) (144.160.20.146) by server-12.tower-119.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 29 Nov 2011 18:04:12 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd194.enaf.sfdc.sbc.com (8.14.4/8.14.5) with ESMTP id pATI2iX6016840; Tue, 29 Nov 2011 13:02:45 -0500
Received: from 01AL10015010626.AD.BLS.COM (sfldmibbcraeninet1.pmtr.mwst.att.com [10.231.16.33]) by mlpd194.enaf.sfdc.sbc.com (8.14.4/8.14.5) with ESMTP id pATI2ZCW016644; Tue, 29 Nov 2011 13:02:36 -0500
Received: from 01NC27689010627.AD.BLS.COM ([90.144.44.202]) by 01AL10015010626.AD.BLS.COM with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 29 Nov 2011 12:03:12 -0600
Received: from 01NC27689010650.AD.BLS.COM ([90.144.44.120]) by 01NC27689010627.AD.BLS.COM with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 29 Nov 2011 13:03:11 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CCAEC1.1ED10ABC"
Date: Tue, 29 Nov 2011 13:03:43 -0500
Message-ID: <750BF7861EBBE048B3E648B4BB6E8F4F212EB2B7@crexc50p>
In-Reply-To: <97F2586F-3E18-47F3-B369-47BE7517204A@cisco.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [homenet] Creating a security association via physical link +button
Thread-Index: AcyrTza1kNjyQOPcTHehS4vJuC/2iQCqaqbw
References: <CAKD1Yr3Y=EO9siQkAuZd7LtqsOT_8GswWkPOoiJEhtvnULcytw@mail.gmail.com><4ECB98BC.8070600@riw.us><ACDC3C9F-85D2-4AF6-AA8C-2A2E6EEDC8EE@fugue.com><CAKD1Yr26zO0Dbco35ngWhj4W0hv_d_zJTCcbB-SSKqPpQab=ig@mail.gmail.com><5C87A581-B2FD-4A1B-AD6B-7823279631BE@fugue.com><CAKD1Yr3zp1Gn1P-jDVgna2ViWeQiyCaTM=hTchpJq2snPSL-hw@mail.gmail.com><E70EE283-116C-49CD-854C-2DA20783FFD7@fugue.com> <97F2586F-3E18-47F3-B369-47BE7517204A@cisco.com>
From: "STARK, BARBARA H" <bs7652@att.com>
To: "Mark Townsley" <townsley@cisco.com>, "Ted Lemon" <mellon@fugue.com>
X-OriginalArrivalTime: 29 Nov 2011 18:03:11.0850 (UTC) FILETIME=[28830CA0:01CCAEC1]
Cc: Russ White <russw@riw.us>, homenet@ietf.org, Lorenzo Colitti <lorenzo@google.com>
Subject: Re: [homenet] Creating a security association via physical link +button
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 29 Nov 2011 18:04:16 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CCAEC1.1ED10ABC
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

+1

=20

And if the goal is just to identify the boundaries, I don't think that
passphrases and encryption are the right way to go about that. But to be
honest, I'm sort of fuzzy as to what the goals really are.

Barbara

=20

An IGP in a homenet setting needs crypto security no more than DHCP, ND
or mDNS would. It's just another configuration protocol within the home.


=20

Yes, this means that we need to trust L2 or physical security. But
that's already very much the case today. If we add keys and crypto at
every layer we are doomed before we start on usability alone.=20

=20

- Mark


------_=_NextPart_001_01CCAEC1.1ED10ABC
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" =
xmlns:p=3D"urn:schemas-microsoft-com:office:powerpoint" =
xmlns:a=3D"urn:schemas-microsoft-com:office:access" =
xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" =
xmlns:s=3D"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" =
xmlns:rs=3D"urn:schemas-microsoft-com:rowset" xmlns:z=3D"#RowsetSchema" =
xmlns:b=3D"urn:schemas-microsoft-com:office:publisher" =
xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadsheet" =
xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" =
xmlns:odc=3D"urn:schemas-microsoft-com:office:odc" =
xmlns:oa=3D"urn:schemas-microsoft-com:office:activation" =
xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" =
xmlns:rtc=3D"http://microsoft.com/officenet/conferencing" =
xmlns:D=3D"DAV:" xmlns:Repl=3D"http://schemas.microsoft.com/repl/" =
xmlns:mt=3D"http://schemas.microsoft.com/sharepoint/soap/meetings/" =
xmlns:x2=3D"http://schemas.microsoft.com/office/excel/2003/xml" =
xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" =
xmlns:ois=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" =
xmlns:dir=3D"http://schemas.microsoft.com/sharepoint/soap/directory/" =
xmlns:ds=3D"http://www.w3.org/2000/09/xmldsig#" =
xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint/dsp" =
xmlns:udc=3D"http://schemas.microsoft.com/data/udc" =
xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" =
xmlns:sub=3D"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/"=
 xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#" =
xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" =
xmlns:sps=3D"http://schemas.microsoft.com/sharepoint/soap/" =
xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance" =
xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/soap" =
xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" =
xmlns:udcp2p=3D"http://schemas.microsoft.com/data/udc/parttopart" =
xmlns:wf=3D"http://schemas.microsoft.com/sharepoint/soap/workflow/" =
xmlns:dsss=3D"http://schemas.microsoft.com/office/2006/digsig-setup" =
xmlns:dssi=3D"http://schemas.microsoft.com/office/2006/digsig" =
xmlns:mdssi=3D"http://schemas.openxmlformats.org/package/2006/digital-sig=
nature" =
xmlns:mver=3D"http://schemas.openxmlformats.org/markup-compatibility/2006=
" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns:mrels=3D"http://schemas.openxmlformats.org/package/2006/relationshi=
ps" xmlns:spwp=3D"http://microsoft.com/sharepoint/webpartpages" =
xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/2006/types"=
 =
xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/2006/messag=
es" =
xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/=
" =
xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortalServer/Pub=
lishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" =
xmlns:st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 12 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.apple-style-span
	{mso-style-name:apple-style-span;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple style=3D'word-wrap: break-word;-webkit-nbsp-mode: =
space;-webkit-line-break: after-white-space'><div =
class=3DWordSection1><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>+1<o:p></o:=
p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>And if the =
goal is just to identify the boundaries, I don&#8217;t think that =
passphrases and encryption are the right way to go about that. But to be =
honest, I&#8217;m sort of fuzzy as to what the goals really =
are.<o:p></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Barbara<o:p=
></o:p></span></p><p class=3DMsoNormal><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497=
D'><o:p>&nbsp;</o:p></span></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'><div><div><p class=3DMsoNormal>An IGP in a homenet setting needs =
crypto security no more than DHCP, ND or mDNS would. It's just another =
configuration protocol within the =
home.&nbsp;<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p =
class=3DMsoNormal>Yes, this means that we need to trust L2 or physical =
security. But that's already very much the case today. If we add keys =
and crypto at every layer we are doomed before we start on usability =
alone.&nbsp;<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal>- =
Mark<o:p></o:p></p></div></div></div></div></body></html>
------_=_NextPart_001_01CCAEC1.1ED10ABC--

From russw@riw.us  Tue Nov 29 13:52:27 2011
Return-Path: <russw@riw.us>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A14E11E80F9 for <homenet@ietfa.amsl.com>; Tue, 29 Nov 2011 13:52:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Uc6GhwWTbuwL for <homenet@ietfa.amsl.com>; Tue, 29 Nov 2011 13:52:26 -0800 (PST)
Received: from ecbiz91.inmotionhosting.com (ecbiz91.inmotionhosting.com [173.205.124.250]) by ietfa.amsl.com (Postfix) with ESMTP id B41F911E80F8 for <homenet@ietf.org>; Tue, 29 Nov 2011 13:52:23 -0800 (PST)
Received: from cpe-065-190-155-146.nc.res.rr.com ([65.190.155.146]:62490 helo=[192.168.100.52]) by ecbiz91.inmotionhosting.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <russw@riw.us>) id 1RVVbB-00069y-OA; Tue, 29 Nov 2011 16:52:21 -0500
Message-ID: <4ED55411.1000502@riw.us>
Date: Tue, 29 Nov 2011 16:52:17 -0500
From: Russ White <russw@riw.us>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <DCC302FAA9FE5F4BBA4DCAD4656937791452BBC0CC@PRVPEXVS03.corp.twcable.com>	<CABONVQbMsY6MF_8q44XqGmdOMS6Odn+CjBEttaEs9rhmknwRxg@mail.gmail.com><4ECCAFC3.5060903@globis.net><DCC302FAA9FE5F4BBA4DCAD4656937791452BBC498@PRVPEXVS03.corp.twcable.com>	<4ECD3608.5020502@globis.net>	<BDF2740C082F6942820D95BAEB9E1A846E5B05@XMB-AMS-108.cisco.com>	<B16D09C6-66AA-4FCC-9A3A-5CB2C2921523@nominet.org.uk>	<5A35BCB0-B7B6-41FE-BA6E-2778D5D479AC@inf-net.nl>	<4ECFE895.3080209@gmail.com> <4ED04C42.2080809@riw.us> <4ED3FEA1.6060009@gmail.com>
In-Reply-To: <4ED3FEA1.6060009@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - ecbiz91.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - riw.us
Cc: homenet@ietf.org
Subject: Re: [homenet] other routing options
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 29 Nov 2011 21:52:27 -0000

> I have no doubt that if you convinced Radia about this, she could suggest
> an IS-IS-TRILL variant that would achieve it.
> 
> But I'm not sure I really understand the need for it. There's no shortage
> of IPv4 address space in homenets, because they are small and in RFC 1918
> space. So if you are routing IPv6 in a home net, why not also route IPv4?

My point is that just as we have applications that want layer 2
connectivity between data centers today, I can easily imagine such
applications within a home... So why not plan for a single control plane
that can route _anything_ from the very beginning.

TRILL is way overkill for this application --go back to the original,
simple idea of just placing layer 2 addresses in a different AF in an
existing and proven routing protocol, like OSPFv3. Use some MANET
extensions to make it scale at the control plane level, and use AF's to
provide routing of anything to anything within the local domain. Assume
you won't have flooding domain boundaries, etc., and no interaction with
spanning tree, either.

In other words --we often think about routing a particular "thing." For
homenet, it makes more sense to provide a generic control plane, and
then figure out how to provide reachability for anything you can throw
at it. IPv4? Shouldn't be an issue. IPv6? Same thing. Ethernet? A new AF
and you're done. Bluetooth extension over the network? I don't see why
it should matter --one control plane, all applications.

Russ

From shane@castlepoint.net  Tue Nov 29 17:55:24 2011
Return-Path: <shane@castlepoint.net>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F56721F8ACE for <homenet@ietfa.amsl.com>; Tue, 29 Nov 2011 17:55:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lJo9ACmC+Yqz for <homenet@ietfa.amsl.com>; Tue, 29 Nov 2011 17:55:18 -0800 (PST)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133]) by ietfa.amsl.com (Postfix) with ESMTP id 4F01B21F8ABE for <homenet@ietf.org>; Tue, 29 Nov 2011 17:55:18 -0800 (PST)
Received: by dog.tcb.net (Postfix, from userid 0) id EEA2B3681BB; Tue, 29 Nov 2011 18:55:17 -0700 (MST)
Received: from mbpw.castlepoint.net (216-160-173-30.hlrn.qwest.net [216.160.173.30]) (authenticated-user smtp) (TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP; Tue, 29 Nov 2011 18:55:17 -0700 (MST) (envelope-from shane@castlepoint.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=216.160.173.30; client-port=55678; syn-fingerprint=65535:54:1:64:M1452,N,W1,N,N,T,S; data-bytes=0
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Shane Amante <shane@castlepoint.net>
In-Reply-To: <4ED55411.1000502@riw.us>
Date: Tue, 29 Nov 2011 18:55:00 -0700
Content-Transfer-Encoding: 7bit
Message-Id: <E8AB6FBC-F5D1-4B9A-8AA5-902C3BF5865C@castlepoint.net>
References: <DCC302FAA9FE5F4BBA4DCAD4656937791452BBC0CC@PRVPEXVS03.corp.twcable.com>	<CABONVQbMsY6MF_8q44XqGmdOMS6Odn+CjBEttaEs9rhmknwRxg@mail.gmail.com><4ECCAFC3.5060903@globis.net><DCC302FAA9FE5F4BBA4DCAD4656937791452BBC498@PRVPEXVS03.corp.twcable.com>	<4ECD3608.5020502@globis.net>	<BDF2740C082F6942820D95BAEB9E1A846E5B05@XMB-AMS-108.cisco.com>	<B16D09C6-66AA-4FCC-9A3A-5CB2C2921523@nominet.org.uk>	<5A35BCB0-B7B6-41FE-BA6E-2778D5D479AC@inf-net.nl>	<4ECFE895.3080209@gmail.com> <4ED04C42.2080809@riw.us> <4ED3FEA1.6060009@gmail.com> <4ED55411.1000502@riw.us>
To: Russ White <russw@riw.us>
X-Mailer: Apple Mail (2.1251.1)
Cc: homenet@ietf.org
Subject: Re: [homenet] other routing options
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 30 Nov 2011 01:55:24 -0000

On Nov 29, 2011, at 2:52 PM, Russ White wrote:
>> I have no doubt that if you convinced Radia about this, she could suggest
>> an IS-IS-TRILL variant that would achieve it.
>> 
>> But I'm not sure I really understand the need for it. There's no shortage
>> of IPv4 address space in homenets, because they are small and in RFC 1918
>> space. So if you are routing IPv6 in a home net, why not also route IPv4?
> 
> My point is that just as we have applications that want layer 2
> connectivity between data centers today, I can easily imagine such
> applications within a home... So why not plan for a single control plane
> that can route _anything_ from the very beginning.
> 
> TRILL is way overkill for this application --go back to the original,
> simple idea of just placing layer 2 addresses in a different AF in an
> existing and proven routing protocol, like OSPFv3. Use some MANET
> extensions to make it scale at the control plane level, and use AF's to
> provide routing of anything to anything within the local domain. Assume
> you won't have flooding domain boundaries, etc., and no interaction with
> spanning tree, either.
> 
> In other words --we often think about routing a particular "thing." For
> homenet, it makes more sense to provide a generic control plane, and
> then figure out how to provide reachability for anything you can throw
> at it. IPv4? Shouldn't be an issue. IPv6? Same thing. Ethernet? A new AF
> and you're done. Bluetooth extension over the network? I don't see why
> it should matter --one control plane, all applications.

+1

-shane

From teco@inf-net.nl  Tue Nov 29 23:53:19 2011
Return-Path: <teco@inf-net.nl>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A29DE11E8089 for <homenet@ietfa.amsl.com>; Tue, 29 Nov 2011 23:53:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VFwEPwJfC6hV for <homenet@ietfa.amsl.com>; Tue, 29 Nov 2011 23:53:19 -0800 (PST)
Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id E07C511E8098 for <homenet@ietf.org>; Tue, 29 Nov 2011 23:53:17 -0800 (PST)
Received: by eabm6 with SMTP id m6so348437eab.31 for <homenet@ietf.org>; Tue, 29 Nov 2011 23:53:17 -0800 (PST)
Received: by 10.213.105.204 with SMTP id u12mr270603ebo.85.1322639596688; Tue, 29 Nov 2011 23:53:16 -0800 (PST)
Received: from [10.175.173.2] (524A158D.cm-4-3a.dynamic.ziggo.nl. [82.74.21.141]) by mx.google.com with ESMTPS id d6sm3421334eec.10.2011.11.29.23.53.14 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 29 Nov 2011 23:53:15 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Teco Boot <teco@inf-net.nl>
In-Reply-To: <4ED55411.1000502@riw.us>
Date: Wed, 30 Nov 2011 08:55:55 +0100
Content-Transfer-Encoding: 7bit
Message-Id: <1320A097-FCAE-4FFB-8AC8-F9F0F2698605@inf-net.nl>
References: <DCC302FAA9FE5F4BBA4DCAD4656937791452BBC0CC@PRVPEXVS03.corp.twcable.com>	<CABONVQbMsY6MF_8q44XqGmdOMS6Odn+CjBEttaEs9rhmknwRxg@mail.gmail.com><4ECCAFC3.5060903@globis.net><DCC302FAA9FE5F4BBA4DCAD4656937791452BBC498@PRVPEXVS03.corp.twcable.com>	<4ECD3608.5020502@globis.net>	<BDF2740C082F6942820D95BAEB9E1A846E5B05@XMB-AMS-108.cisco.com>	<B16D09C6-66AA-4FCC-9A3A-5CB2C2921523@nominet.org.uk>	<5A35BCB0-B7B6-41FE-BA6E-2778D5D479AC@inf-net.nl>	<4ECFE895.3080209@gmail.com> <4ED04C42.2080809@riw.us> <4ED3FEA1.6060009@gmail.com> <4ED55411.1000502@riw.us>
To: Russ White <russw@riw.us>
X-Mailer: Apple Mail (2.1251.1)
Cc: homenet@ietf.org
Subject: Re: [homenet] other routing options
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@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, 30 Nov 2011 07:53:19 -0000

Let's not classify protocols yet. Maybe IS-IS-TRILL is overkill and
OSPFv3-&AF-&MANETextensions-&L2extensions is not. Or otherwise.

The main point is: we have to deal with v4, v6 and VLANs. Dual stack 
guest network may have multiple L2 links, connected via some kind of 
backbone link (e.g. powerline), and hooked up to a firewall somewhere.

Teco


Op 29 nov. 2011, om 22:52 heeft Russ White het volgende geschreven:

> 
>> I have no doubt that if you convinced Radia about this, she could suggest
>> an IS-IS-TRILL variant that would achieve it.
>> 
>> But I'm not sure I really understand the need for it. There's no shortage
>> of IPv4 address space in homenets, because they are small and in RFC 1918
>> space. So if you are routing IPv6 in a home net, why not also route IPv4?
> 
> My point is that just as we have applications that want layer 2
> connectivity between data centers today, I can easily imagine such
> applications within a home... So why not plan for a single control plane
> that can route _anything_ from the very beginning.
> 
> TRILL is way overkill for this application --go back to the original,
> simple idea of just placing layer 2 addresses in a different AF in an
> existing and proven routing protocol, like OSPFv3. Use some MANET
> extensions to make it scale at the control plane level, and use AF's to
> provide routing of anything to anything within the local domain. Assume
> you won't have flooding domain boundaries, etc., and no interaction with
> spanning tree, either.
> 
> In other words --we often think about routing a particular "thing." For
> homenet, it makes more sense to provide a generic control plane, and
> then figure out how to provide reachability for anything you can throw
> at it. IPv4? Shouldn't be an issue. IPv6? Same thing. Ethernet? A new AF
> and you're done. Bluetooth extension over the network? I don't see why
> it should matter --one control plane, all applications.
> 
> Russ
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet

