Index: [Article Count Order] [Thread]

Date: Thu, 3 Jul 2008 14:36:40 -0600
From: "Leino, Tammy" <tammy_leino@mentor.com>
Subject: [users:00818] Re: MIPv6 - Correspondent Node Self-Test #6 problem
To: <users@tahi.org>
Message-Id: <2F83EB16CD718C43889CBCD31ECFD7F875408E@na2-mail.mgc.mentorg.com>
In-Reply-To: <2F83EB16CD718C43889CBCD31ECFD7F875408D@na2-mail.mgc.mentorg.com>
X-Mail-Count: 00818

Hello All,Test #13 appears to suffer from the same problem - invalid checksum. Best Regards,Tammy Leino -----Original Message-----From: Leino, Tammy Sent: Thursday, July 03, 2008 3:54 PMTo: users@tahi.orgSubject: [users:00817] MIPv6 - Correspondent Node Self-Test #6 problemHello All, When running test #6 for the Correspondent Node self-test suite, I see =that the HoTI message sent from the TAHI node has a wrong checksum =value; therefore, the NUT throws this packet out before trying to =validate the length of the Mobility Header.  This causes the NUT to fail =the test, but this is proper functionality per RFC 3775:9.2.  Processing Mobility Headers   Mobility Header processing MUST observe the following rules:   o  The checksum must be verified as per Section 6.1.  Otherwise, the      node MUST silently discard the message. Can someone please confirm that there is a checksum error in this test?  =I have attached the output file for this test for your reference.Best Regards,Tammy Leino <<6.html>> 
	

818_2.html (attatchment)(tag is disabled)