Re: Incremental De-sync. for OptiDAD? (was Re: Comment on draft-ietf-ipv6-optimistic-dad-06.txt)

Christian Vogt <chvogt@tm.uka.de> Tue, 08 November 2005 12:59 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EZT4s-0008QE-3R; Tue, 08 Nov 2005 07:59:54 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EZT4q-0008Q8-Il for ipv6@megatron.ietf.org; Tue, 08 Nov 2005 07:59:52 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA04285 for <ipv6@ietf.org>; Tue, 8 Nov 2005 07:59:26 -0500 (EST)
Received: from iramx2.ira.uni-karlsruhe.de ([141.3.10.81] ident=[U2FsdGVkX18ncGQKNfyfOP13hjjRTkL/4oIIAyvY2bE=]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EZTKb-000393-V3 for ipv6@ietf.org; Tue, 08 Nov 2005 08:16:13 -0500
Received: from i72archimedes.tm.uni-karlsruhe.de ([141.3.71.83]) by iramx2.ira.uni-karlsruhe.de with esmtpsa id 1EZT4g-0005tk-7I; Tue, 08 Nov 2005 13:59:44 +0100
Message-ID: <4370A13D.6000602@tm.uka.de>
Date: Tue, 08 Nov 2005 13:59:41 +0100
From: Christian Vogt <chvogt@tm.uka.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-DE; rv:1.7.12) Gecko/20050923 Thunderbird/1.0.7 Mnenhy/0.7.2.0
X-Accept-Language: de-DE, de, en-us, en
MIME-Version: 1.0
To: Nick 'Sharkey' Moore <sharkey@zoic.org>
References: <4353DBE2.4010601@tm.uka.de> <20051019114715.GA4074@zoic.org> <4356B259.4080701@tm.uka.de> <20051031031201.GA14479@zoic.org> <43661280.9090108@tm.uka.de> <20051101115923.GA32582@zoic.org> <436E12E9.2000205@tm.uka.de> <20051108032241.GB25376@zoic.org>
In-Reply-To: <20051108032241.GB25376@zoic.org>
X-Enigmail-Version: 0.90.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: -102.7 (---------------------------------------------------)
X-Spam-Status: No
X-Spam-Report: -100 ATIS_ASMTP SMTP with authentification via ATIS-Server -1.8 ALL_TRUSTED Passed through trusted hosts only via SMTP 0.0 BAYES_50 BODY: Bayesian spam probability is 40 to 60% [score: 0.5000] -0.9 AWL AWL: From: address is in the auto white-list
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Content-Transfer-Encoding: 7bit
Cc: IPv6 <ipv6@ietf.org>
Subject: Re: Incremental De-sync. for OptiDAD? (was Re: Comment on draft-ietf-ipv6-optimistic-dad-06.txt)
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org

 > Given that the original (RFC2462, 5.4.2) is a "should delay":
 > |
 > | If the Neighbor Solicitation is the first message to be sent from an
 > | interface after interface (re)initialization, the node should delay
 > | sending the message by a random delay between 0 and
 > | MAX_RTR_SOLICITATION_DELAY as specified in [DISCOVERY].
 >
 > I'm happy to just recommend a "SHOULD NOT delay" in OptiDAD, as this
 > was something I'd been assuming all along.  Does anyone in here
 > object?

Yes, I agree.  This solution makes sense.

- Christian

-- 
Christian Vogt, Institute of Telematics, University of Karlsruhe
www.tm.uka.de/~chvogt/pubkey/


Nick 'Sharkey' Moore wrote:
> On 2005-11-06, Christian Vogt wrote:
> 
>>I see, it's an implementation issue.
> 
> 
> Sadly, true.  Whilst we're not really meant to worry about these,
> sometimes they can't be ignored.
> 
> 
>>(3)  Given that you cannot really know whether the ON is stationary or
>>mobile, the following may be a good approach:  Send the pair of MLD
>>Report and NS multiple times with incremental de-synchonization delays,
>>but allow for immediate use of the OA:
> 
> 
> Now, I'm not saying that this is a bad idea, but I do think it's
> adding unwarranted complexity for OptiDAD's purposes.
> 
> On the other hand, a more flexible desync backoff algorithm might
> e a good research paper topic perhaps.
> 
> Given that the original (RFC2462, 5.4.2) is a "should delay":
> |
> | If the Neighbor Solicitation is the first message to be sent from an
> | interface after interface (re)initialization, the node should delay
> | sending the message by a random delay between 0 and
> | MAX_RTR_SOLICITATION_DELAY as specified in [DISCOVERY].
> 
> I'm happy to just recommend a "SHOULD NOT delay" in OptiDAD, as this
> was something I'd been assuming all along.  Does anyone in here object?
> 
> -----Nick



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