Re: [RFC 4861] upper-layer reachability confirmation
Sebastien Roy <Sebastien.Roy@Sun.COM> Tue, 24 June 2008 14:32 UTC
Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ipv6-archive@megatron.ietf.org
Delivered-To: ietfarch-ipv6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A53EE3A684C; Tue, 24 Jun 2008 07:32:19 -0700 (PDT)
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A0EC73A684C for <ipv6@core3.amsl.com>; Tue, 24 Jun 2008 07:32:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.046
X-Spam-Level:
X-Spam-Status: No, score=-3.046 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vu4YopncfPel for <ipv6@core3.amsl.com>; Tue, 24 Jun 2008 07:32:17 -0700 (PDT)
Received: from brmea-mail-4.sun.com (brmea-mail-4.Sun.COM [192.18.98.36]) by core3.amsl.com (Postfix) with ESMTP id 4750F3A67E7 for <ipv6@ietf.org>; Tue, 24 Jun 2008 07:32:17 -0700 (PDT)
Received: from fe-amer-10.sun.com ([192.18.109.80]) by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m5OEWIiY027772 for <ipv6@ietf.org>; Tue, 24 Jun 2008 14:32:18 GMT
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0K2Z00M0103RDZ00@mail-amer.sun.com> (original mail from Sebastien.Roy@Sun.COM) for ipv6@ietf.org; Tue, 24 Jun 2008 08:32:18 -0600 (MDT)
Received: from [129.148.174.103] by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0K2Z009M41PK3NH0@mail-amer.sun.com>; Tue, 24 Jun 2008 08:32:09 -0600 (MDT)
Date: Tue, 24 Jun 2008 10:32:08 -0400
From: Sebastien Roy <Sebastien.Roy@Sun.COM>
Subject: Re: [RFC 4861] upper-layer reachability confirmation
In-reply-to: <20080624180617.c1497dec.akisada@tahi.org>
To: Yukiyo Akisada <akisada@tahi.org>
Message-id: <1214317928.18919.40.camel@strat>
Organization: Sun Microsystems
MIME-version: 1.0
X-Mailer: Evolution 2.22.2
References: <20080624180617.c1497dec.akisada@tahi.org>
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org
On Tue, 2008-06-24 at 18:06 +0900, Yukiyo Akisada wrote: > I have a question about upper-layer reachability confirmation defined in RFC 4861. > > When the neighbor cache state for the default router is STALE > and the host sends a packet to off-link, > the default router sends redirect packet to the host. > > Can the host considers that the default router is REACHABLE? > > Personally, I didn't expected this behavior. > But I found that an implementation behaves like this > when I'm developping the conformance tester. > > How do you think about this behavior? That seems reasonable to me. The host sent a packet to the router, and the router responded with one of its own which was received by the host. This is bi-directional reachability. In general though, I cringe at the mention of the word "conformance" in the context of IPv6 neighbor discovery, and your question is an example of why. That's probably a separate discussions though, and one which has already been masticated over numerous times before in the distant past. :-) -Seb -------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
- [RFC 4861] upper-layer reachability confirmation Yukiyo Akisada
- Re: [RFC 4861] upper-layer reachability confirmat… Sebastien Roy
- Re: [RFC 4861] upper-layer reachability confirmat… Vlad Yasevich
- Re: [RFC 4861] upper-layer reachability confirmat… Yukiyo Akisada