IETF Logo Mail Archive

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

Fred Baker <fredbaker.ietf@gmail.com> Tue, 11 August 2020 20:47 UTC

Return-Path: <fredbaker.ietf@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C45C73A0CCC; Tue, 11 Aug 2020 13:47:31 -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, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 9m1kCu_GTYhm; Tue, 11 Aug 2020 13:47:30 -0700 (PDT)
Received: from mail-pl1-x631.google.com (mail-pl1-x631.google.com [IPv6:2607:f8b0:4864:20::631]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AEB413A0BF4; Tue, 11 Aug 2020 13:47:30 -0700 (PDT)
Received: by mail-pl1-x631.google.com with SMTP id k13so79812plk.13; Tue, 11 Aug 2020 13:47:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:content-transfer-encoding:mime-version:subject:in-reply-to :date:cc:message-id:references:to; bh=II7wb455YGE8w9pMDvVpWztfij9Oc2PZLB9lQhWA77A=; b=ceb189OYlK98qdiG/3LCB+VSrAiqAyoglQqbnt16tXbghcPr2mP62/s0rK3MuelzeL O4WbW1msvvSHgpT/TWD8sR/FVxjWSjgX3CyBHG25VOmG+tMVKY4Oea6OHYrToLg0QLQP i3ujIDBHzanHd7NStG5aMNXM728aEUj1LQVwGA/VqaR82OY4O+9C8+AZJdFc5tOhNHBc eNl3e8c0Ntcoq9lXScaf6Kr21somxKgN6dtFV6RTUyHqs8lpxbLJEiymeW+5zsG7rt95 fhcVqOMMBmjrmCgzmEtPvvIF9uhUfKUo72bzQKEXZiWu8+fG1I4fOuvkZKMvDGNKXkI/ TFfg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:in-reply-to:date:cc:message-id:references:to; bh=II7wb455YGE8w9pMDvVpWztfij9Oc2PZLB9lQhWA77A=; b=HUN+8IYywbOcVEakGzLtwTazEwQKAKDV5dxWekuVTQFHFnYMRFI0B1nmQLrDiNV6Rh cqtyjBa3ibBnSRVIAkvLGedjBBYeBfK17+a5HWLo95TQ6VDCyBJswT2qTD6JLO0NG+Qp no5p1GcfO/HptkOPPGPtYTY3GW3FZfxazaDDwq94Xv07c6j70LALsun9EBsNMYxiUJiQ JLwFL/FUO7Ra5Qqerp/GmyNUWfgIwXJ5ZumgDlxHrK29Z4LG+BA0OrkwqAol5ZiFgCZG PkAw802nzmDbTarzJwIGad8BgKJSky/HIiZMrS8wL7HjIZJlKOaho+cxNYXsyGLuY8EW vxFA==
X-Gm-Message-State: AOAM532MiS8e/Jd5u6RFWxIEahB2dlLHSyvxJgOg4xtgs8U/RLnqQflh SvQ+XpKSLTxcTCuaZQS+j9joIDsrSCA=
X-Google-Smtp-Source: ABdhPJwlBauTtJRUI0KbQzb22HEd77pXNhuKHS8/aR6uLUg2o1MQ1QJTisof/Y3NAUwVyCxm17xcfA==
X-Received: by 2002:a17:90a:df11:: with SMTP id gp17mr2978836pjb.140.1597178850043; Tue, 11 Aug 2020 13:47:30 -0700 (PDT)
Received: from ?IPv6:2600:8802:5800:652::1011? ([2600:8802:5800:652::1011]) by smtp.gmail.com with ESMTPSA id z4sm26107541pfb.55.2020.08.11.13.47.29 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 11 Aug 2020 13:47:29 -0700 (PDT)
From: Fred Baker <fredbaker.ietf@gmail.com>
X-Google-Original-From: Fred Baker <FredBaker.IETF@gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
In-Reply-To: <F098390D-B8CF-4121-9D5D-F2610144DE9D@fugue.com>
Date: Tue, 11 Aug 2020 13:47:28 -0700
Cc: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>, IPv6 List <ipv6@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>
Message-Id: <DE1679CC-351A-48AF-ABA7-C66A0A81E55C@gmail.com>
References: <F098390D-B8CF-4121-9D5D-F2610144DE9D@fugue.com>
To: Ted Lemon <mellon@fugue.com>
X-Mailer: iPhone Mail (17G68)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/CVd56J_xwSg4UcVutiszyF5OtVc>
Subject: Re: [v6ops] draft-ietf-6man-grand : saving lookups
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Aug 2020 20:47:32 -0000

> Do WiFi base stations implement this correctly, or do they broadcast?

I would expect that WiFi Base Stations multicast. However, understand what that means. 

On the air interface, they are either transmitting or not. In the receiving NIC, the question is whether or not they store the message; if they are not configured to receive a certain multicast group, regardless of transmission type, they receive and store the message and then forget that they have done so, re-using the buffer for the next message. If they forward the message on, it uses the bandwidth on the other side, whatever it is, with the same destination address. 

The place where one might distinguish “broadcast” from “multicast” is on a data center switch, where “multicast” might mean keeping a list of relevant ports and only sending to them. They want to send a message once. If they are sending the same message several times, “to whom” is an important question.

v2.23.0 | Report a Bug | By Email