Re: ICMPv6 question

Mark Smith <markzzzsmith@gmail.com> Fri, 01 September 2017 00:27 UTC

Return-Path: <markzzzsmith@gmail.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 CBA2F132ED9 for <ipv6@ietfa.amsl.com>; Thu, 31 Aug 2017 17:27:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.498
X-Spam-Level:
X-Spam-Status: No, score=-1.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.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 gPKeHYVTc3oN for <ipv6@ietfa.amsl.com>; Thu, 31 Aug 2017 17:27:20 -0700 (PDT)
Received: from mail-ua0-x22b.google.com (mail-ua0-x22b.google.com [IPv6:2607:f8b0:400c:c08::22b]) (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 0D251132FCF for <ipv6@ietf.org>; Thu, 31 Aug 2017 17:27:20 -0700 (PDT)
Received: by mail-ua0-x22b.google.com with SMTP id j46so3407909uag.5 for <ipv6@ietf.org>; Thu, 31 Aug 2017 17:27:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=xU839au7Lr9sh8LrptzGG4TwqX907Qzu7dL9bqgGewo=; b=OUz//B5+IFnZGZ+htn8GcK72kovRe8zj33Y0IeNQShYR1ulgOKJssr9Yl63Vfxc6AD M45/qd6eo+8QvJdtLSwzshLV+MSSd5TMrGexlu72YM9Xdz3fYUMlRMlm8UNK4lhIIy9Y swK3mKK1rnVe/w0PwmX30DjUvYPrDt/I7hMwsVD9w2crDgj0K4/ZBvmIUV5oea9T5db5 uXgs81h3tuv59kRAcNTbNA1Hw9Ndh30K9wta974Mh5Q7S0/w9SN5jQzti+qWRAS8eN/3 nT394T/wJ1hVY8lZFFoptyWO8imC2qA8IjYSJXf6Bzkq5YvldG7/Ej/vUZvUtoINCfbG cA4w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=xU839au7Lr9sh8LrptzGG4TwqX907Qzu7dL9bqgGewo=; b=hmAFdn/kgeVLU3Fb7hdwWravbfXzVoHL3O7hIH0fXufJbGmqFx7DZTMYqsr5boAnZg OElGZmsH8ARl10gO/OX5dqqUv20TdEtCGi7g/ixMhZli/V5cK2dj85i4zJ4X8yl2E9+N 8Ni08kuXnNtPxcoXboIVl5heO/PaK0pWHSAhUr7IVZbvh73QFz2ypWQEGgammcH6LvGM xQgM1FZ8p2GDlDF497jbn3UbaiEXx3ur6f/VwQPqLd0eMCSMCg1T4ggoYzErEXRfAzG2 cQnkFBmK2ly9H280aWzzqP1J+K2cadti3L3iaKFwPKbA92/RkfI/DJgWA7VKsOKH1qIt 1aJQ==
X-Gm-Message-State: AHPjjUhUbhZVZpztrNOmcqZkZlS0660tUYCsfSi4bqgTZd0hqwbibjov 6eGShBbAU7oVdpYt8DdlBy4lXyIsTg==
X-Google-Smtp-Source: ADKCNb7jNbm27zVEb0nCc5PDYVDdHYJucHyDCHfY45NCwJ9LRTG2P5+0Oc/7PgcjExHJi313B4nPCxyPJ8YGaFq1G6M=
X-Received: by 10.176.26.173 with SMTP id j45mr162284uai.33.1504225639091; Thu, 31 Aug 2017 17:27:19 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.27.19 with HTTP; Thu, 31 Aug 2017 17:26:48 -0700 (PDT)
In-Reply-To: <952aab1a2c824a79b98a3f9d2b3a473a@XCH15-06-08.nw.nos.boeing.com>
References: <952aab1a2c824a79b98a3f9d2b3a473a@XCH15-06-08.nw.nos.boeing.com>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Fri, 01 Sep 2017 10:26:48 +1000
Message-ID: <CAO42Z2xYD-aQAQjFFFh2=iqF42izQw30NnTLPWAvpivFBGPkpg@mail.gmail.com>
Subject: Re: ICMPv6 question
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
Cc: 6man WG <ipv6@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/Mr-cqh7pxu2W3sUfsMSG0cNf9u4>
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: Fri, 01 Sep 2017 00:27:22 -0000

2001:db8::f00

On 1 September 2017 at 09:07, Templin, Fred L <Fred.L.Templin@boeing.com> wrote:
> I have a question. If an IPV6 host with address 2001:db8::f00 assigned to an interface
> receives a packet with destination address 2001:db8::baa over that interface, what
> should it do? Drop the packet silently, or drop and return an ICMPv6 Destination
> Unreachable?
>

Hmm, at face value it appears to be a simple question and the answer
would be DU.

Looking at RFC4443, it limits generation of DUs to routers or the
packet source host:

"A Destination Unreachable message SHOULD be generated by a router, or
   by the IPv6 layer in the originating node, in response to a packet
   that cannot be delivered to its destination address for reasons other
   than congestion.  (An ICMPv6 message MUST NOT be generated if a
   packet is dropped due to congestion.)A Destination Unreachable
message SHOULD be generated by a router, or
   by the IPv6 layer in the originating node, in response to a packet
   that cannot be delivered to its destination address for reasons other
   than congestion.  (An ICMPv6 message MUST NOT be generated if a
   packet is dropped due to congestion.)"


Per RFC8200 (a.k.a. new RFC2460), we have these definitions for a
router and a host

   router       a node that forwards IPv6 packets not explicitly
                addressed to itself.  (See Note below.)

   host         any node that is not a router.  (See Note below.)



A host is therefore to ignore "IPv6 packets not explicitly addressed
to itself", which I think means a host does not generate a DU for
misdirected packets.


I was wondering about how this could happen and I think there could be
two possible causes,

- incorrect ND cache entry for 2001:db8::baa2001:db8::baa, somehow
with the link layer address of 2001:db8::f00

- host attached to one end of a point-to-point link, and the upstream
device (likely router) is blindly forwarding packets over the p2p link
assuming the destination is at the other end rather than performing ND
to discover and continue to verify the presence of the specific
addresses at the other end of the link (That's why I think ND should
be performed on p2p links. Even a /127 configured on one end of the
link doesn't guarantee the other address within the /127 is present.
If a router performed ND on p2p links, it could discover the DA for a
packet is not present and generate a DU for it.)

Regards,
Mark.




> Thanks - Fred
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------