Index: [Article Count Order] [Thread]

Date: Tue, 15 Apr 2008 09:00:22 +0900
From: Yukiyo Akisada <akisada@tahi.org>
Subject: [users:00664] Re: call for public review
To: users@tahi.org
Message-Id: <20080415090022.31e7f52b.akisada@tahi.org>
In-Reply-To: <20080414142219.509b73a8.akisada@tahi.org>
References: <20080414142219.509b73a8.akisada@tahi.org>
X-Mail-Count: 00664

Hi, all.

Let me correct the information.

>     4) Support of On-link Determination
>        - "a host properly rejects an invalid prefix length,
>           however the prefix length is still valid for on-link determination
>           when the on-link flag is true". - RFC 4862 Section 6.3.4

It must be RFC 4861.

Thanks,


On Mon, 14 Apr 2008 14:22:19 +0900
Yukiyo Akisada <akisada@tahi.org> wrote:

> Hi, all.
> 
> The beta version of Self_Test (Self_Test_4-0-0b1) has been released.
> This release is for public review at IPv6 Ready Logo Program.
> 
> Now,
> IPv6 Ready Logo Program is planning to have the major version up.
> 
> You can find upcoming test specification and test scenario at
> <http://www.ipv6ready.org/announcement/public_review20080411_p2core.html>.
> 
> The differences are
>     1) Support of IPv6 Error message - Beyond Scope of Source Address (Code 2)
>        - RFC 4443 Section 3.1
>     2) Support of Deprecation of Type 0 Routing Header - RFC 5095
>     3) Support of Disabling IP Operation once a DAD Failure has occurred.
>        - RFC 4862 Section 5.4.5
>     4) Support of On-link Determination
>        - "a host properly rejects an invalid prefix length,
>           however the prefix length is still valid for on-link determination
>           when the on-link flag is true". - RFC 4862 Section 6.3.4
>     5) Support of Address Architecture - RFC 4291
> 
> If you have comments for test specification and test scenario,
> please post to <ipv6ready-info@ipv6ready.org>.
> 
> If you have comments for test tool itself,
> please post to <contact@tahi.org> or <users@tahi.org>.


-- 
Yukiyo Akisada <akisada@tahi.org>