Hi,

Current status of RFC Compliance check for DHCPv6 is:

+----------------------+---------+------+------+-----+----------------------------------------------------------------------------------------+
| Sub Components |  Total  | Pass | Fail | N/A |
Failed Testcase IDs                                                      |
+----------------------+---------+------+------+-----+----------------------------------------------------------------------------------------+
|  RFC3315            |   99      |  62  |  32   |  5   | 5,7,14, 25, 27,
29, 35, 42-45, 49-53, 56-64, 66, 68, 69, 76, 77, 79, 81 |
|  RFC3646            |   31      |   9   |  17   |  5   | 3, 5, 7, 10, 11,
13-15, 18-25, 27
 |
|  RFC3736            |   31      |  22  |   4    |  5   | 2, 8, 13, 27

           |
+----------------------+---------+------+------+-----+---------------------------------------------------------------------------------------+

Version used:
 * Connman-1.15x
 * Source from git commit 77ade69cce17c24ade7c5d99ff04841adae22156 (dhcpv6:
Make sure release message is sent)
  * And two patches:
     1) dhcpv6: Enable checking of reply error codes
     2) dhcpv6: Most of the reply error handling was missing

Details for failed test cases are provided in attached Excel sheet.

~HK



On Thu, Jun 6, 2013 at 11:15 AM, harshal patel <harshal...@gmail.com> wrote:

> HI Jukka,
>
> I applied following 2 patches:
> *  dhcpv6: Enable checking of reply error codes
> * dhcpv6: Most of the reply error handling was missing
>
> I couldn't apply patches directly, so applied it manually and build the
> ConnMan.
>
> Following the status of testing of  DHCP_CONF.1.3.3: Client Initiated
> Exchange - Reception:
> A, B, C, D, E, H, J -> PASS
> F, G, I, K -> FAIL
>
> F is failing because, Request message is not observed in response to Reply
> w/IA option(Status code=NoBinding).
> G & I failing with error "Could not get Rebind Message". ConnMan is not
> sending rebind message before T2 time expires.
>
> As support of "Decline Message" is yet not added, K fails with message
> "Could not get Decline Message".
>
> As of now I tested only above tests with these changes, I shall make full
> round of test to ensure proper functionality of other testcases.
>
> ~HK
>
>
>
> On Wed, Jun 5, 2013 at 7:45 PM, Jukka Rissanen <
> jukka.rissa...@linux.intel.com> wrote:
>
>> On 05.06.2013 17:07, Daniel Wagner wrote:
>>
>>> I guess, I am missing some prerequisite patch. Do I need to apply any
>>>> other
>>>> patches before applying this patch?
>>>>
>>>
>>> I get the same issue. I think Jukka's patch is not based on the head
>>> version.
>>>
>>>
>>>
>> Sorry about that, too many things going on at the same time. I just
>> missed one patch from the set.
>>
>>
>> Cheers,
>> Jukka
>>
>>
>> ______________________________**_________________
>> connman mailing list
>> connman@connman.net
>> https://lists.connman.net/**mailman/listinfo/connman<https://lists.connman.net/mailman/listinfo/connman>
>>
>
>

Attachment: Connman_DHCPv6_RFC_Compliance_20130607_1.0.xlsx
Description: application/vnd.openxmlformats-officedocument.spreadsheetml.sheet

_______________________________________________
connman mailing list
connman@connman.net
https://lists.connman.net/mailman/listinfo/connman

Reply via email to