IETF Logo Mail Archive

Re: [homenet] biggest L2 domain

Michael Richardson <mcr@sandelman.ca> Fri, 13 December 2019 20:11 UTC

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 77F83120089 for <homenet@ietfa.amsl.com>; Fri, 13 Dec 2019 12:11:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IQoApFEGVX8D for <homenet@ietfa.amsl.com>; Fri, 13 Dec 2019 12:11:23 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E34C212002E for <homenet@ietf.org>; Fri, 13 Dec 2019 12:11:22 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id AF7CA389B7; Fri, 13 Dec 2019 15:07:30 -0500 (EST)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id A853B75A; Fri, 13 Dec 2019 15:11:21 -0500 (EST)
From: Michael Richardson <mcr@sandelman.ca>
To: Gert Doering <gert@space.net>
cc: homenet <homenet@ietf.org>
In-Reply-To: <20191213172646.GI72330@Space.Net>
References: <20241.1576248848@localhost> <20191213172646.GI72330@Space.Net>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <4502.1576267881.1@localhost>
Content-Transfer-Encoding: quoted-printable
Date: Fri, 13 Dec 2019 15:11:21 -0500
Message-ID: <4503.1576267881@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/Wp_Mvrx8L0ERg0InqZjhiXrxIzg>
Subject: Re: [homenet] biggest L2 domain
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Dec 2019 20:11:24 -0000

Gert Doering <gert@space.net> wrote:
    > On Fri, Dec 13, 2019 at 09:54:08AM -0500, Michael Richardson wrote:
    >> I thought that we wrote somewhere in RFC7368 that the Homenet router should
    >> collect as many ports as possible together into a single L2 zone.
    >> I can't find that text right now. Did it go away?
    >>
    >> In testing, we have found a device that does not put it's 5-"LAN" ports into
    >> a bridge.  That's probably a missing configuration, but in the meantime, we
    >> have an interesting HNCP and naming setup!

    > My understanding of "homenet" and "HNCP" devices has always been "every
    > single hole in the box is a routed port".  Now that's my understanding and
    > not necessarily written down somewhere.

It wasn't intended to be automatic, but rather based upon provisioned
knowledge that a device had.

The intent was to avoid routing-at-layer-two (i.e. spanning tree, etc.), but
not to replace switches.

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        |    IoT architect   [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [

v2.23.0 | Report a Bug | By Email