RE: Route Information Options in Redirect Messages (updated)

Mark Smith <> Wed, 08 February 2017 20:06 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id ECF8F129461 for <>; Wed, 8 Feb 2017 12:06:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.2
X-Spam-Status: No, score=-1.2 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id QyL1HKSgM0mK for <>; Wed, 8 Feb 2017 12:06:50 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:400c:c05::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id EAA2D12940D for <>; Wed, 8 Feb 2017 12:06:49 -0800 (PST)
Received: by with SMTP id k127so109015153vke.0 for <>; Wed, 08 Feb 2017 12:06:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=oS7zDL6HoCQSxVKWeAOLKu0Ksgads6QvkaR2U+NEeGE=; b=RzHRJgxhN2T/fSEDoKo20kgc47bvVM+fqCZaX1MYomAopA0/HBxZ+oRFwuXCKMtkLV Uz2Tz8NKyhDCGHY2bMRtUy7RT6oTXxu7FBNU3kncwvgiGt4pXR4N6MecS95QjwCKDs/J K4/f3EgvcjVy31FkRL+TaETDUIhH8ZjhUv8/HQiGy7RLwFfkWS2Lciu6+bQgnr2oOTNI rB2D/mFwHZyf+q0+2ZWJeSmSt0nX7PjT6f61MCzcW0FoMvyc1pDWJzi0usCyKR0SrD0b KWn+4tc+eIe2MmUykhmH9C6Ddn2zLXaeVvmzY8dDBPRmLwEVnlihiojIZpiTQm94FFho sYJQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=oS7zDL6HoCQSxVKWeAOLKu0Ksgads6QvkaR2U+NEeGE=; b=pDsONDMumLqPoTns6ReIOzi1jhpe24NikKPnn4DJc1QjnxVd0hCSVzJJ4uMUSIKCOa OxIwQ/96Ziw2CSoXIcaBXjwz8ohiMuVW9Y4PxodqSYCT5RK7JfkbsiXWcwAuFNRIjOJ4 89AdCZiKfzkw3++OH4Zg7XE+v6KSBapyn4TjKZ74enD2shx+9qaTQfEKzkIU0gq88ECF /KYQ0INLIBz1h3W4oe7h4tABWnHzuzgUGJ3L8LZJ/gbTM9hir7KrkbTSmr4b+Yz4ILD9 m8H5APhADfgIcPZT5Grlq8UIQg0ru+NMXLJFd8Pu4xAsKgyXyh9Ycb2WcKb+TDn7FdeS j/Bg==
X-Gm-Message-State: AMke39kt6Rq/VqOhD+4EVyQV2yLpg6dGQJ4IXu71in4jHMkZ1ywH+Hobg0kS6Qb9B/HLb22RntaAtRxAJyqKIA==
X-Received: by with SMTP id b8mr11098322vke.140.1486584408971; Wed, 08 Feb 2017 12:06:48 -0800 (PST)
MIME-Version: 1.0
Received: by with HTTP; Wed, 8 Feb 2017 12:06:18 -0800 (PST)
In-Reply-To: <>
References: <> <> <> <> <> <> <> <> <>
From: Mark Smith <>
Date: Thu, 9 Feb 2017 07:06:18 +1100
Message-ID: <>
Subject: RE: Route Information Options in Redirect Messages (updated)
To: "Templin, Fred L" <>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <>
Cc: james woodyatt <>, 6man WG <>, =?UTF-8?B?56We5piO6YGU5ZOJ?= <>
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 08 Feb 2017 20:06:51 -0000

Hi Fred,

On 8 Feb. 2017 06:54, "Templin, Fred L" <> wrote:

Hi Mark,

> Ø  I think you need to be careful of not effectively reinventing a dynamic routing protocol

> No, there is no reinvention going on here. The behavior parallels redirects

> for singleton destination addresses, where Redirects are accepted from the

> current first-hop router, be it a default or non-default.

So in my proposed case of a stub router receiving and accepting a
prefix redirect, that is where there would be more of behaviour
change, as, per RFC4861,

A router MUST NOT update its routing tables upon receipt of aRedirect.

For these stub routers, accepting a prefix redirect from more than
just a default router is where I think it starts encroaching on the
functionality of a dynamic routing protocol. It starts being possible
to have all the stub routers in the set sending each other prefix
redirects (perhaps maliciously) and ending up with a variety of
different, possibly random paths across the link, with some of those
paths creating forwarding loops. Dynamic routing protocols would
resolve this situation to a single best path as well as eliminating
forwarding loops. That is the sort of functionality that would be (and
should be to keep it simple) missing from a simple prefix redirect

I think limiting the problem space to that of providing a better entry
point into the "proper" routing system/forwarding domain for stub
routers, by only accepting them from default routers learned via RAs
or static configuration, avoids the possibility of encountering and
having to mitigate these more complex issues.

Perhaps that means there needs to be two different validation rules
for the two different types of devices:

- for hosts, accept prefix redirects from current first-hop router for
a destination covered by the prefix

- for stub routers, only accept prefix redirects from default routers

with the fundamental distinguisher between the device types being
whether they forward non-local packets or not, and whether a stub
router accepts them or not being dependent on whether there is a
dynamic routing protocol enabled on the prefix redirect receiving


Thanks - Fred

From: Mark Smith []
Sent: Tuesday, February 07, 2017 11:38 AM

To: Templin, Fred L <>
Cc: 6man WG <>rg>; james woodyatt <>om>; 神明達哉
Subject: RE: Route Information Options in Redirect Messages (updated)

On 8 Feb. 2017 05:43, "Templin, Fred L" <> wrote:

Hi Jinmei-san,

> Hmm, maybe I'm so dumb but I'm afraid I still don't understand intent
> clearly.  Do you mean an operational assumption of this proposal is to
> use it in a link where RA guard isn't deployed?  If so, it's far
> better (at least to me) to just say so.
> BTW, if this proposal keeps the concept of "unsolicited redirect" and
> also allows the destination address of '::' to bypass the host's
> validity check of whether it's really the first hop router for the
> destination,

No, that is not what we want to have happen. The document doesn't
say this currently, but we want to retain a revised version of the validity
check. The revised version of the check would say:

      - The IP source address of the Redirect is the same as the current

        first-hop router for the specified ICMP Destination Address.

      - The IP source address of the Redirect is the same as the current
        first-hop router for the specified ICMP Destination Address, or
        (when the ICMP Destination Address is '::') the same as the current
        first-hop router for the specified RIOs

Would welcome better wording than this, but we definitely do want
to retain the validity check. Comments?

I think you need to be careful of not effectively reinventing a
dynamic routing protocol that ends up missing the necessary
capabilities required of one to keep this method simple.

When I've thought about this sort of capability, I've thought of it as
a hint from the routing system to the users of the forwarding domain -
hosts and stub routers (default and connected route only routers,
possibly with other static routes) - of a better entry point for their
packets into the forwarding domain.

In the case of a stub router, if it needs or would benefit from more
dynamic network information than just a prefix redirect hint, then I
think that is really saying that the stub router shouldn't be a stub
router - it needs to be a full and proper participant in the routing
system (running dynamic routing protocol, discovering and conveying
network topology information etc.), rather than a user of it via
default route to the forwarding domain.

That's why I thought the validation should be that these prefix
redirects are only accepted from a default router learned via an RA or
static default router configuration, as a default router has the role
of offering an entry point into the forwarding domain. It would
enforce the existing boundary between the devices that are users of
the forwarding domain, and the devices that are participants in the
routing system that decide the paths through the forwarding domain.