Re: [RFC 4861] upper-layer reachability confirmation

Vlad Yasevich <vladislav.yasevich@hp.com> Tue, 24 June 2008 15:58 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 092383A6A38; Tue, 24 Jun 2008 08:58:00 -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 E08513A6A1E for <ipv6@core3.amsl.com>; Tue, 24 Jun 2008 08:57:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level:
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 2eDO93C9oiaz for <ipv6@core3.amsl.com>; Tue, 24 Jun 2008 08:57:58 -0700 (PDT)
Received: from g5t0006.atlanta.hp.com (g5t0006.atlanta.hp.com [15.192.0.43]) by core3.amsl.com (Postfix) with ESMTP id 150083A6A38 for <ipv6@ietf.org>; Tue, 24 Jun 2008 08:57:58 -0700 (PDT)
Received: from smtp1.fc.hp.com (smtp.fc.hp.com [15.15.136.127]) by g5t0006.atlanta.hp.com (Postfix) with ESMTP id E3471C3EB; Tue, 24 Jun 2008 15:57:58 +0000 (UTC)
Received: from [192.168.98.100] (squirrel.fc.hp.com [15.11.146.57]) by smtp1.fc.hp.com (Postfix) with ESMTP id D0B001FD638; Tue, 24 Jun 2008 15:50:22 +0000 (UTC)
Message-ID: <48611985.1040407@hp.com>
Date: Tue, 24 Jun 2008 11:57:57 -0400
From: Vlad Yasevich <vladislav.yasevich@hp.com>
User-Agent: Thunderbird 2.0.0.4 (X11/20070604)
MIME-Version: 1.0
To: Sebastien Roy <Sebastien.Roy@Sun.COM>
Subject: Re: [RFC 4861] upper-layer reachability confirmation
References: <20080624180617.c1497dec.akisada@tahi.org> <1214317928.18919.40.camel@strat>
In-Reply-To: <1214317928.18919.40.camel@strat>
X-Enigmail-Version: 0.95.6
X-Brightmail-Tracker: AAAAAQAAAAI=
X-Whitelist: TRUE
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org

Sebastien Roy wrote:
> 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.
> 

It's reasonable as long as the implementation doing so can correctly identify
that it sent the packet triggering the redirect.  If the implementation
can do so, it can assume bi-directional communication.

Personally, I wouldn't consider this upper layer indication, since Redirect
is not strictly upper layer.

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