Index: [Article Count Order] [Thread]

Date: Tue, 17 Jun 2008 12:00:04 +0300
From: "Vladimir Kuk" <vkuk@marvell.com>
Subject: [users:00777] Self_Test v4.0.1 NDP test v6LC.2.2.19
To: <users@tahi.org>
Message-Id: <A8D19528FBF27C4691BD90C81EB22ABE04B1345E@rdlnexch03.marvell.com>
In-Reply-To: <A8D19528FBF27C4691BD90C81EB22ABE04B13197@rdlnexch03.marvell.com>
References: <20080530095616.101712c1.akisada@tahi.org><4843573E.6080208@miraclelinux.com><20080610105402.b0eb6466.akisada@tahi.org><484F4A89.5040308@miraclelinux.com><20080612094406.372ae3e4.akisada@tahi.org><4851DB56.70005@miraclelinux.com> <20080613130537.f06bad22.akisada@tahi.org> <A8D19528FBF27C4691BD90C81EB22ABE04B13197@rdlnexch03.marvell.com>
X-Mail-Count: 00777

Hello.

I'm running Self Tests for phase 2 host part and ran into some problem
with NDP test 2.2.19.

In it a little problematic to understand the test since the description
in it, is for another test (2.2.12.A).

As far as I can it tests for discarding the invalid prefix for purposes
of autoconfiguration but expects this prefix to be accepted for onlink
determination.

If I understood the test correctly, then there is a problem since RFC
4892 states:

5.5.3. Router Advertisement Processing p.19:

If the sum of the prefix length and interface identifier length
does not equal 128 bits, the Prefix Information option MUST be
ignored. An implementation MAY wish to log a system management
error in this case. The length of the interface identifier is
defined in a separate link-type specific document, which should
also be consistent with the address architecture [RFC4291] (see
Section 2).

Also, in same section:
It should be noted, however, that this does not mean
the advertised prefix length is meaningless. In fact, the
advertised length has non-trivial meaning for on-link
determination in [RFC4861] where the sum of the prefix length and
the interface identifier length may not be equal to 128. Thus, it
should be safe to validate the advertised prefix length here, in
order to detect and avoid a configuration error specifying an
invalid prefix length in the context of address autoconfiguration.


Can anyone shed a light on the matter?


Thank you.

Best regards,
	
	Vladimir Kuk

Marvell Software Solutions Israel Ltd.
Atidim Technological Park Bldg #4
Tel Aviv, 61581, Israel
Email:    vkuk@marvell.com
Office:   +972-3-645-8955
Web site: http://www.marvell.com