IETF Logo Mail Archive

Re: a draft about on-link and submit prefixes

Michael Richardson <mcr+ietf@sandelman.ca> Tue, 14 March 2017 23:01 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE8BB129BC6 for <ipv6@ietfa.amsl.com>; Tue, 14 Mar 2017 16:01:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.002
X-Spam-Level:
X-Spam-Status: No, score=-0.002 tagged_above=-999 required=5 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-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 ktJT1qGf71T0 for <ipv6@ietfa.amsl.com>; Tue, 14 Mar 2017 16:01:04 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C9F78129440 for <ipv6@ietf.org>; Tue, 14 Mar 2017 16:01:04 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 2108A205AB; Tue, 14 Mar 2017 19:24:07 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 13B4A636E0; Tue, 14 Mar 2017 19:01:03 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: ipv6@ietf.org
cc: sthaug@nethelp.no, lorenzo@google.com, jinmei@wide.ad.jp
Subject: Re: a draft about on-link and submit prefixes
In-Reply-To: <20170314.142023.41722849.sthaug@nethelp.no>
References: <026FE8B0-6FFA-4835-8D72-D4CBC6187A2D@employees.org> <20170314.132640.74662612.sthaug@nethelp.no> <CAKD1Yr1G-65Vw0OyKP8CDPuUY7+-Q_hBrLY8E6wAoHHYM9jHsg@mail.gmail.com> <20170314.142023.41722849.sthaug@nethelp.no>
X-Mailer: MH-E 8.6; nmh 1.6+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: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Tue, 14 Mar 2017 19:01:03 -0400
Message-ID: <22051.1489532463@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/Hx7i1CRXsy3MWiohNp5v5_o8-uE>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Mar 2017 23:01:06 -0000

sthaug@nethelp.no wrote:
    > I haven't seen a definition of what an IPv6 subnet is. I specifically
    > haven't seen where it is defined that a given subnet prefix can be
    > spread across multiple links - especially since RFC 4291 says

    > "Currently, IPv6 continues the IPv4 model in that a subnet prefix is
    > associated with one link."

My goal is to get rid of layer-2 games; most of which were caused by lack of
subnets in IP4b., They have become huge un-seeable/un-traceable protocols
stacks of various kinds of poorly implemented STP.

v6 prefixes are plentiful, and we should use them... but we haven't found
"the" solution to discovery across subnets, and haven't made side-wide
multicast work easily, so we are doing site-wide discovery via other methods.

So, many want to keep bridging networks with 1000:1 bandwidth ratios
(GbE vs -70dbm wifi at 1Mb/s... )

Maybe there are some happy middle ground that comes from the revelation
that subnets != links.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-

v2.23.0 | Report a Bug | By Email