RE: [EXTERNAL] [v6ops] draft-ietf-6man-grand : saving lookups

"Templin (US), Fred L" <Fred.L.Templin@boeing.com> Tue, 11 August 2020 19:33 UTC

Return-Path: <Fred.L.Templin@boeing.com>
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 143C33A0B45; Tue, 11 Aug 2020 12:33:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=boeing.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5APb4G5OFX_R; Tue, 11 Aug 2020 12:33:42 -0700 (PDT)
Received: from clt-mbsout-02.mbs.boeing.net (clt-mbsout-02.mbs.boeing.net [130.76.144.163]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 574123A0D52; Tue, 11 Aug 2020 12:33:32 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by clt-mbsout-02.mbs.boeing.net (8.15.2/8.15.2/DOWNSTREAM_MBSOUT) with SMTP id 07BJXSQP001444; Tue, 11 Aug 2020 15:33:30 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=boeing.com; s=boeing-s1912; t=1597174410; bh=EC5jXdEIcM8zn9jUS8MrTh7J/YL/5TLB9s1dU/k9p6o=; h=From:To:CC:Subject:Date:References:In-Reply-To:From; b=OzfDNGP39C+5yZCm/HxmwQ/STJLtTfZIlFdgdBgsFifD3HtzsoYJYBFr4AFwKYRC2 cM6WNLT6gXUWJZ/WDdL8BJ9/dUm9pQOd4o5+wAYIZeRrltGBVl2RKw8/XpC5xcgBow sCcjUlmPA6oa87byXpa/6PTJS5WqaFzbwLtI2M1vIvv8VD0mUCaOsJZCMS7uXqxhBe m5icsROPPnKKLEh+851nbeDY+UYQut0OfmaSYYkDF12aRf7m3cfueWKPRqxRfwD8i4 JYXoEiOH+Ml7u2GAiiW3wMJ2MX6Ec3uIu1tCBp+76dxwcnHTgdN7HucXgsTAAAPNIL /RWWGLhNQeNZQ==
Received: from XCH16-07-07.nos.boeing.com (xch16-07-07.nos.boeing.com [144.115.66.109]) by clt-mbsout-02.mbs.boeing.net (8.15.2/8.15.2/8.15.2/UPSTREAM_MBSOUT) with ESMTPS id 07BJXJsI032089 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Tue, 11 Aug 2020 15:33:19 -0400
Received: from XCH16-07-10.nos.boeing.com (144.115.66.112) by XCH16-07-07.nos.boeing.com (144.115.66.109) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.1.2044.4; Tue, 11 Aug 2020 12:33:18 -0700
Received: from XCH16-07-10.nos.boeing.com ([fe80::1522:f068:5766:53b5]) by XCH16-07-10.nos.boeing.com ([fe80::1522:f068:5766:53b5%2]) with mapi id 15.01.2044.004; Tue, 11 Aug 2020 12:33:17 -0700
From: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
To: Ted Lemon <mellon@fugue.com>
CC: Bob Hinden <bob.hinden@gmail.com>, Nick Hilliard <nick@foobar.org>, "v6ops@ietf.org" <v6ops@ietf.org>, IPv6 List <ipv6@ietf.org>
Subject: RE: [EXTERNAL] [v6ops] draft-ietf-6man-grand : saving lookups
Thread-Topic: [EXTERNAL] [v6ops] draft-ietf-6man-grand : saving lookups
Thread-Index: AQHWcBZDozN/TbgM60KTlQsJYZVlgQ==
Date: Tue, 11 Aug 2020 19:33:17 +0000
Message-ID: <d4dc68ad019f44f09f7e1d791845f0b2@boeing.com>
References: <8b5d5420e55b435aa578c20bd99f3407@boeing.com> <F098390D-B8CF-4121-9D5D-F2610144DE9D@fugue.com> <ae4333439bc6431d91e3b0c0bd43286a@boeing.com> <500105DD-90B0-4870-AF97-6213798221DF@fugue.com>
In-Reply-To: <500105DD-90B0-4870-AF97-6213798221DF@fugue.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [137.137.12.6]
x-tm-snts-smtp: 05BCB4D63E877FEA53F73F591055384B63715E850F7DD4C5E82DE4D13C4532462000:8
Content-Type: multipart/alternative; boundary="_000_d4dc68ad019f44f09f7e1d791845f0b2boeingcom_"
MIME-Version: 1.0
X-TM-AS-GCONF: 00
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/gdY0BBUbeq6Rp4SnIAOv57hoRgo>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
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, 11 Aug 2020 19:33:52 -0000

Hi Ted,


But there’s no reason for an overlay topology. The question is, is there a way for it to know which stations to send the multicast too? If so, then it should just iterate across that set of stations using unicast, which is a lot faster. If not, then it probably has no choice but to broadcast. Sorry if these are naive questions—I haven’t really dug around in the details of how WiFi routers do multicast, so I have just enough knowledge to appear really ignorant.


With my NBMA case, there is a an overlay routing system which has proactive full
knowledge of all active nodes on the link and knows how to unicast-forward to any
of those nodes at any time. In the WiFi base station case, unless there is some way
for the base station to learn the list of active nodes on the link then broadcast is
the last resort. Or, the base station could start out life with a NULL topology table
and then add new nodes as it receives multicasts. Then, as its topology table grows,
it may be able to eventually start to do unicasts to those nodes it has previously
learned about from broadcasts – a learning bridge, in other words – useful?

Fred