From: Toyo Abe <tabe@miraclelinux.com>
To: "YOSHIFUJI Hideaki / 吉藤英明" <yoshfuji@linux-ipv6.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [IPV6] ADDRCONF: Defer dad for global address until dad for linklocal is completed.
Date: Tue, 20 May 2008 21:53:00 +0900 [thread overview]
Message-ID: <4832C9AC.3030502@miraclelinux.com> (raw)
In-Reply-To: <4832C579.2040800@miraclelinux.com>
sorry again. there was typo.
Toyo Abe wrote:
> Sorry for lack of explanation.
>
> > But then, many other test scenarios in TAHI test suite went to FAIL.
> It was because
> > the tester node send RA with prefix option to the host right after
> it receives DAD NS
> > from the host, which is obviously in autoconfiguration process for
> linklocal address.
>
> And the tester node never accepts RS(es) from the host after sending
> the RA. The tester
> node determine FAIL unless it doesn't receive DAD NS for corresponding
> global address
> from the host.
... unless it receives DAD NS for corresponding global address from the host
>
>
> -toyo
>
> Toyo Abe wrote:
>> Yoshifuji-san,
>>
>> Thanks for your response.
>>
>> > Why don't we just ignore RA until DAD for link-local
>> > address has been successfully completed?
>> I was also thinking so. And I tried it at first.
>> But then, many other test scenarios in TAHI test suite went to FAIL.
>> It was because
>> the tester node send RA with prefix option to the host right after it
>> receives DAD NS
>> from the host, which is obviously in autoconfiguration process for
>> linklocal address.
>>
>> Besides, RFC4862 section 4(protocol overview) says;
>> ---
>> To speed the autoconfiguration process, a host may generate its link-
>> local address (and verify its uniqueness) in parallel with waiting
>> for a Router Advertisement. Because a router may delay responding to
>> a Router Solicitation for a few seconds, the total time needed to
>> complete autoconfiguration can be significantly longer if the two
>> steps are done serially.
>> ---
>>
>> The text indicates that a host *may* accept RA including prefix
>> option even before
>> completion of DAD for linklocal address.
>> Since current addrconf code actually accepts RA including prefix
>> option while DAD for
>> linklocal address is processing, changes of the behaviour looks like
>> a degradation for me.
>> Hence, I chose to accept RA at that moment and defer sending DAD NS
>> for global addresses.
>>
>> Thanks,
>> -toyo
>>
>> YOSHIFUJI Hideaki / 吉藤英明 wrote:
>>> In article <48324792.5070309@miraclelinux.com> (at Tue, 20 May 2008
>>> 12:37:54 +0900), Toyo Abe <tabe@miraclelinux.com> says:
>>>
>>>> This patch fixes the problem by deferring DAD initiation for global
>>>> address until
>>>> DAD for linklocal address is completed. Now the failed test
>>>> scenarios noted above
>>>> are all passed.
>>>
>>> Why don't we just ignore RA until DAD for link-local
>>> address has been successfully completed?
>>>
>>> --yoshfuji
>>>
>>>
>>
>>
>
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2008-05-20 12:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-20 3:37 [IPV6] ADDRCONF: Defer dad for global address until dad for linklocal is completed Toyo Abe
2008-05-20 8:33 ` YOSHIFUJI Hideaki / 吉藤英明
2008-05-20 12:27 ` Toyo Abe
2008-05-20 12:35 ` Toyo Abe
2008-05-20 12:53 ` Toyo Abe [this message]
2008-05-21 16:58 ` YOSHIFUJI Hideaki / 吉藤英明
2008-05-21 17:30 ` Toyo Abe
2008-05-21 20:30 ` David Miller
2008-06-20 2:17 ` Toyo Abe
2008-06-20 2:32 ` YOSHIFUJI Hideaki / 吉藤英明
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4832C9AC.3030502@miraclelinux.com \
--to=tabe@miraclelinux.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).