[RFC 4861] upper-layer reachability confirmation
Yukiyo Akisada <akisada@tahi.org> Tue, 24 June 2008 09:08 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 2855A3A684C; Tue, 24 Jun 2008 02:08:22 -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 6CC6D3A688F for <ipv6@core3.amsl.com>; Tue, 24 Jun 2008 02:08:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.185
X-Spam-Level:
X-Spam-Status: No, score=-0.185 tagged_above=-999 required=5 tests=[BAYES_40=-0.185]
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 Xrpsxk49Mzpw for <ipv6@core3.amsl.com>; Tue, 24 Jun 2008 02:08:19 -0700 (PDT)
Received: from ns.64translator.com (ns.64translator.com [202.214.123.16]) by core3.amsl.com (Postfix) with ESMTP id 7AC4D3A6829 for <ipv6@ietf.org>; Tue, 24 Jun 2008 02:08:18 -0700 (PDT)
Received: from bahamas.64translator.com (bahamas.64translator.com [10.21.32.3]) by ns.64translator.com (8.14.2/8.14.2) with ESMTP id m5O8ggKe055286 for <ipv6@ietf.org>; Tue, 24 Jun 2008 17:43:00 +0900 (JST) (envelope-from akisada@tahi.org)
Received: from localhost (dhcp163.64translator.com [10.21.32.163]) by bahamas.64translator.com (8.13.6/8.13.6) with SMTP id m5O96ZpF027101 for <ipv6@ietf.org>; Tue, 24 Jun 2008 18:06:35 +0900 (JST) (envelope-from akisada@tahi.org)
Date: Tue, 24 Jun 2008 18:06:17 +0900
From: Yukiyo Akisada <akisada@tahi.org>
To: ipv6@ietf.org
Subject: [RFC 4861] upper-layer reachability confirmation
Message-Id: <20080624180617.c1497dec.akisada@tahi.org>
Organization: TAHI Project
X-Mailer: Sylpheed version 2.3.0beta5 (GTK+ 2.8.12; i386-portbld-freebsd4.11)
Mime-Version: 1.0
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
Hi, all. 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? Thanks, -- Yukiyo Akisada <akisada@tahi.org> -------------------------------------------------------------------- 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