Re: [v6ops] privacy point re. unsolicited NA / router neighbor cache

Mark Smith <markzzzsmith@gmail.com> Wed, 24 July 2019 01:14 UTC

Return-Path: <markzzzsmith@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 AF6BB1209B4 for <v6ops@ietfa.amsl.com>; Tue, 23 Jul 2019 18:14:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.498
X-Spam-Level:
X-Spam-Status: No, score=-0.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=0.999, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no 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 TE8U3a5Jat6Y for <v6ops@ietfa.amsl.com>; Tue, 23 Jul 2019 18:14:09 -0700 (PDT)
Received: from mail-oi1-x22a.google.com (mail-oi1-x22a.google.com [IPv6:2607:f8b0:4864:20::22a]) (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 503A412034B for <v6ops@ietf.org>; Tue, 23 Jul 2019 18:14:09 -0700 (PDT)
Received: by mail-oi1-x22a.google.com with SMTP id m206so33795475oib.12 for <v6ops@ietf.org>; Tue, 23 Jul 2019 18:14:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=1UFZ1HAl4obkiKglKjv1dmDOtV+GmL+fHgAUYB069dQ=; b=GEoyPmK3Geeo1blZamFg0BqmhXSiZqdh6+WO1MZKIN0YuMvV1bnU/+5FXm9oLNbUjD xX4TKIorgdCTmgHPUk9DwJ2dF0h3xkvwu61cevkiXaN6ro9wmPD17oRoYMVLpVIwBFzS d2PPzOJPcpdlZwg9/jAUEPOlUDJDBuhECP5DLUOw8CuPSz5nsZAGhaF9rMP7LMjpzdHw HlqxLnjXB1DeJoIBFr2ds64RY3TVkQ4bBrOp6tLmDfAN2Iq2bX/lXtmgM1TXPYdkCuEd z1sB25v4t3p5Qp3J4lVjHqsOY7zlyAiVb8wwjvi+VOCgIdkR9SoutKWg9zaTSxRnAupI Fheg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=1UFZ1HAl4obkiKglKjv1dmDOtV+GmL+fHgAUYB069dQ=; b=VS4Nb19z/i7zCAcRg5U0M4PA/wntgNnXDJzn8ung253ollcYfBN+jEywMDni7i5Se2 frt5rOoGrqN/1dOv+V70V0Owfl35LMbrtMsiBbeBe++kxU82/sSzGslXLFbqjj3qiW6/ sfz5WZtubN6y8Agr306496+MaIhM37si2FmAIE8Ys9oBWYe2ZnODLyAaWaJLusY85ukz gEeHnHlOa27OlihFbOajkvMNA3hvhVRly0S+OR43l39Y/2LXbUva708N3uu91ORfTwpO MtAFydy6TMD1fQWRotAy/FceAHMrTrfHZxMWfqQrdXKgtwLDXKxpB+PStwOkLQQLcpg9 QHPw==
X-Gm-Message-State: APjAAAX1636Ngpl9IPeyMwNzn3ajjqS+U3XPvsNBG5Je93waTbyiy40v SbNvgatK1YT1WG3gblaYQ6tsdBW0aePsylMqiiyaJAJi
X-Google-Smtp-Source: APXvYqye9Nqf717LlZ6Vi5Bve8NL4+MRNoaXmkqSX644q5fS1C+LUWcO0bZ18DXr6nrfSrBLfKPAt2vLp+AbwJrwRw8=
X-Received: by 2002:aca:c584:: with SMTP id v126mr39861814oif.60.1563930848505; Tue, 23 Jul 2019 18:14:08 -0700 (PDT)
MIME-Version: 1.0
References: <20190722213727.GI34551@eidolon.nox.tf> <CAO42Z2zn-V9HrKGDC_api7BE4Sy6jmcrfKR7nbnSrHA5NpxYjQ@mail.gmail.com> <20190723000049.GJ34551@eidolon.nox.tf> <20190723070141.GG60824@Space.Net> <9740316D-61DE-4BF4-87C2-5BCA5575BC27@steffann.nl>
In-Reply-To: <9740316D-61DE-4BF4-87C2-5BCA5575BC27@steffann.nl>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Wed, 24 Jul 2019 11:13:42 +1000
Message-ID: <CAO42Z2ykSZ02pqTu0RYMLX6piVu6BrCA3nR_4w8+HT70y-5eSg@mail.gmail.com>
To: Sander Steffann <sander@steffann.nl>
Cc: Gert Doering <gert@space.net>, v6ops list <v6ops@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000adb515058e630696"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/ePpVPQMmI0Nox1O2BcLMah3GKgc>
Subject: Re: [v6ops] privacy point re. unsolicited NA / router neighbor cache
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: Wed, 24 Jul 2019 01:14:11 -0000

On Tue., 23 Jul. 2019, 23:33 Sander Steffann, <sander@steffann.nl> wrote:

> Hi,
>
> > The general idea that on-link multicast is a positive aspect of IPv6
> > is nice, but wrong.
>
> Well, a little bit :)
>
> There is still the advantage that the NIC can apply its MAC address
> filter. L2 destination FF:FF:FF:FF:FF:FF can't be filtered there, but
> 33:33:* can :)



It's no surprise that Steve Deering also wrote RFC 1112, "Host Extensions
for IP Multicasting", which says,

"7.4. Extensions to an Ethernet Local Network Module
...
It is highly desirable to take advantage of any address
   filtering capabilities that the Ethernet hardware interface may have,
   so that the host receives only those packets that are destined to it."
...

IPv4 and IPX uses/used link-layer broadcasts. Appletalk used link-layer
multicasts, however, from memory, it used the same or a few multicast
address for everything.

IPv6 improves Appletalk by using much more specific link-layer multicast
addresses for different purposes, which allows NIC filtering to be much
more fine grained.

If a host is only running protocols that use link-layer multicasts, then it
could switch off broadcast reception in its NIC (IFF_BROADCAST interface
flag).

For example, an IPv6 only host attached to a link that also has IPv4 hosts
would be able to drop in its NIC hardware IPv4 ARPs and DHCPv4 DISCOVERS,
rather than processing and then dropping them at higher layers in the stack.


Regards,
Mark.




> Cheers,
> Sander
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>