IETF Logo Mail Archive

Re: [homenet] Updates to Homenet Architecture Principles doc

Ted Lemon <mellon@fugue.com> Fri, 13 June 2014 13:57 UTC

Return-Path: <mellon@fugue.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C00A1B290F for <homenet@ietfa.amsl.com>; Fri, 13 Jun 2014 06:57:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.552
X-Spam-Level:
X-Spam-Status: No, score=-2.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sxGvQNSvGNmt for <homenet@ietfa.amsl.com>; Fri, 13 Jun 2014 06:57:12 -0700 (PDT)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 7E7DB1A03ED for <homenet@ietf.org>; Fri, 13 Jun 2014 06:57:12 -0700 (PDT)
Received: from [10.0.10.40] (c-174-62-147-182.hsd1.nh.comcast.net [174.62.147.182]) by toccata.fugue.com (Postfix) with ESMTPSA id BD28E23824E3; Fri, 13 Jun 2014 09:57:09 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\))
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <CAKD1Yr1nhnvG2H_9eeW-Dono3cZqYaxMZaCR1vcueOQgW4xqYQ@mail.gmail.com>
Date: Fri, 13 Jun 2014 09:57:08 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <E66DDB31-C318-4025-BF8A-15F2336A2A08@fugue.com>
References: <BEB843C7-EB1D-486A-A9A1-B99D48775D33@nominet.org.uk> <85F978F4-1293-4F9E-B5C7-068F95A0B626@nominet.org.uk> <CAKD1Yr2mzZOvCDwyyEZHef1rk5PAxtNZRVRys43SXnD=gVxLBA@mail.gmail.com> <143C7553-11D4-41A9-910E-FAD26F484635@fugue.com> <CAKD1Yr0hr8Pa_QU_9mjRjbxffQ=mdgOWYSQUyLc5ewkpuf5OmA@mail.gmail.com> <F08A2136-E88F-4785-BE01-14D386B9C2D9@fugue.com> <CAKD1Yr1nhnvG2H_9eeW-Dono3cZqYaxMZaCR1vcueOQgW4xqYQ@mail.gmail.com>
To: Lorenzo Colitti <lorenzo@google.com>
X-Mailer: Apple Mail (2.1878.2)
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/RN6AKgqvMW-xynkOM-awNeE8j2M
Cc: Ray Bellis <Ray.Bellis@nominet.org.uk>, "homenet@ietf.org Group" <homenet@ietf.org>
Subject: Re: [homenet] Updates to Homenet Architecture Principles doc
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Jun 2014 13:57:13 -0000

On Jun 13, 2014, at 9:48 AM, Lorenzo Colitti <lorenzo@google.com> wrote:
> Not to me they didn't. Seriously - if you understand what we're being asked to do, and it's simple to explain, then it shouldn't take long for you to type. Please?

The working group would presumably like for there to be routing on the homenet.   What problems is the routing supposed to solve?   What things are priorities?   What things aren't priorities?

Clearly we need the routing solution to get packets to the right egress based on source address.   Do we also need it to do load sharing across parallel links, if such links exist?   Is it important to minimize the number of hops?   How long of a delay can there be between changes to the topology (e.g., a router being unplugged) and recovery, assuming that a flow was going through that router?   Is it okay to break a flow in that situation, or does it need to survive the transition?   Does the routing protocol need to be aware of the type of media a given link crosses, and does it need to prefer one media type over another where both are available?

I'm basically making questions up here.   The document should say what the working group wants routing to accomplish.   Right now it's a bit of a kitchen sink, with a lot of (IMHO) inappropriately prescriptive text.

v2.23.0 | Report a Bug | By Email