Re: Route Information Options in Redirect Messages (updated)

神明達哉 <jinmei@wide.ad.jp> Thu, 09 February 2017 18:26 UTC

Return-Path: <jinmei.tatuya@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 AFA9E129444 for <ipv6@ietfa.amsl.com>; Thu, 9 Feb 2017 10:26:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.597
X-Spam-Level:
X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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=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 bMQH42X0DaiB for <ipv6@ietfa.amsl.com>; Thu, 9 Feb 2017 10:26:35 -0800 (PST)
Received: from mail-qk0-x22a.google.com (mail-qk0-x22a.google.com [IPv6:2607:f8b0:400d:c09::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 09255129434 for <ipv6@ietf.org>; Thu, 9 Feb 2017 10:26:35 -0800 (PST)
Received: by mail-qk0-x22a.google.com with SMTP id s186so13797839qkb.1 for <ipv6@ietf.org>; Thu, 09 Feb 2017 10:26:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=F7OxmcTK2lpB2y+ZKSwffiP7IVtl00U4mWk1U3uZUuE=; b=S2d6k1MYdG+u2QloTVyW2YR3rBx85/hGXnc00CgElMQDD/LIlDj89BhBCmemIh4uxA tfK2LGZIgOQTY4aTdiFnUxdMQ+FNhpL1lJLhLYQKplqSFw/9YBYyRtdESwevYsDIe6e3 fe3KN9mDa8tM92Hsys7+hkXiDEy0hOtFyOS4+xXEz0ehF6AqtFU5RWm1h0HBgD2CnAad WSQj+EyE+Mht1afcpy6mFG+x2mOlcsumuiVG3VVXWUAU0WyrPGmeFLv8K0CzkCCgVsuW VM4yj9Ku8JGZD+YVQ2s/MjKHCOhLjxuobs8M9ixfYZpumgMLbpKAHcF3vvFDhT/MH+Se 6OTg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=F7OxmcTK2lpB2y+ZKSwffiP7IVtl00U4mWk1U3uZUuE=; b=Hpw2QZDPPm/E1NRVLz88xyVbVAcxCJUbMywkJni1e2bP0iYqUfnYS2epxY5sYiJvRE G/NSf8N9fdXoULTE7Ll3IX0h5/5bZwDbqnBhWlzNmyPdTDYg6BnNKQZruLpf79ub9Vu4 Ukdlvj9qPx/l3mvun8OouX0fFHQq1ydD6MbMGZndkYN1LpDJFPueVhN6EqPjiefnIszd hNDQivC4JN1aI7uM6KyKOvVsutzbeqGiHSyvXTgfcSlARYw/UBWPiHVQUJldwRuuP7fl cLoee650nmJ4Dei+8SSkB/I6jC1YZsoLTSE7vUF2FmTqJnitjHWom/Pcms4Bn6Tl30N0 qj/A==
X-Gm-Message-State: AMke39kJBHqsrZoJbU9BBt6Vl345L4HJ5DktclsFNTbV2f/F3Vb+fBChQbYTdkxX08pfu6Wtrm6ZHNZ7YCNg0Q==
X-Received: by 10.55.189.130 with SMTP id n124mr4561423qkf.235.1486664793983; Thu, 09 Feb 2017 10:26:33 -0800 (PST)
MIME-Version: 1.0
Sender: jinmei.tatuya@gmail.com
Received: by 10.237.60.29 with HTTP; Thu, 9 Feb 2017 10:26:33 -0800 (PST)
In-Reply-To: <614ead862aa54a548ed4835a998a42e4@XCH15-06-08.nw.nos.boeing.com>
References: <9910b4acd87044e89fad83bb5c795b77@XCH15-06-08.nw.nos.boeing.com> <CAJE_bqfJMW5SRDxm04rC67Xvf4YqaxihyCRUXfGW3TUq42Xk-A@mail.gmail.com> <5ebd374f4ec8454b8a3796cffe5e1919@XCH15-06-08.nw.nos.boeing.com> <CAJE_bqfN9x031TXBd8Hpiv5168=zXXN+U02gGqsxyXhpQ-SDWA@mail.gmail.com> <E291D7B9-7492-4043-BE4F-E45CB54985D7@google.com> <CAJE_bqePL1bKAZL53=oebn=2eiYKdxyULd5jS4uJk9jo1sFrcA@mail.gmail.com> <614ead862aa54a548ed4835a998a42e4@XCH15-06-08.nw.nos.boeing.com>
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Date: Thu, 9 Feb 2017 10:26:33 -0800
X-Google-Sender-Auth: 3juyeA6Ew5w92HrQ9uSmuZ8RQYg
Message-ID: <CAJE_bqf2Vc9nocdh+Y-fDj_nLL4-b-W=ysb8raCFg2Qj6k6wBA@mail.gmail.com>
Subject: Re: Route Information Options in Redirect Messages (updated)
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/zdRGbQ581uDZ2pAHvX3K3HWLXKw>
Cc: james woodyatt <jhw@google.com>, IPv6 List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
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: Thu, 09 Feb 2017 18:26:36 -0000

At Tue, 7 Feb 2017 18:43:12 +0000,
"Templin, Fred L" <Fred.L.Templin@boeing.com> wrote:

> > 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:
>
> OLD:
>       - The IP source address of the Redirect is the same as the current
>         first-hop router for the specified ICMP Destination Address.
>
> NEW:
>       - 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?

Okay, I now understand the intent.  In that case I think the
validation logic (currently described in Section 3.1) will have to be
more detailed.  It will also have to cover some corner cases such as
where some of RIOs contain pass the above validation but some others
don't.  Similarly, I guess it should specify which RIOs can be
accepted by the receiving host in general (e.g., when the destination
address is 2001:db8:a::1, should the host accept an RIO for
2001:db8:b::/48?).

--
JINMEI, Tatuya