ETSI's Bug Tracker - IPv6 Testing Conformance (TTCN3 + TPs) | |||||||||||||||
View Issue Details | |||||||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||||||||
0000113 | IPv6 Testing Conformance (TTCN3 + TPs) | Test Case (TTCN3 ATS) | public | 16-10-2006 13:07 | 30-10-2007 11:44 | ||||||||||
Reporter | user9 | ||||||||||||||
Assigned To | Alexandre Berge | ||||||||||||||
Priority | normal | Severity | minor | Reproducibility | always | ||||||||||
Status | resolved | Resolution | fixed | ||||||||||||
Platform | OS | OS Version | |||||||||||||
Cor - Mob - Sec - Trans | |||||||||||||||
Summary | 0000113: TC_COR_1082_01 | ||||||||||||||
Description | In the test-case TC_COR_1082_01, function f_TP_twoFragmentsWithSameId sends an Echo Request in two fragments to the IUT. The test-case (and, also the test-purpose) expects no message in reply, and this, the function verifies using the function f_expectNoMessage: The test-case expects no message in reply to the sent message, and this it verifies with f_expectNoMessage. It quotes the reason that, because, the fragment id is the same in both segments, so the packet must be discarded. But as per RFC-2460, both the fragments of the IPv6 Packet must contain the same fragment id. RFC Text : An original packet is reassembled only from fragment packets that have the same Source Address, Destination Address, and Fragment Identification. | ||||||||||||||
Steps To Reproduce | |||||||||||||||
Additional Information | |||||||||||||||
Tags | No tags attached. | ||||||||||||||
Relationships |
| ||||||||||||||
Attached Files | |||||||||||||||
Issue History | |||||||||||||||
Date Modified | Username | Field | Change | ||||||||||||
16-10-2006 13:07 | user9 | New Issue | |||||||||||||
16-10-2006 13:07 | user9 | Source (company - Author) | => Huawei | ||||||||||||
07-11-2006 09:50 | Alexandre Berge | Note Added: 0000189 | |||||||||||||
07-11-2006 09:51 | Alexandre Berge | Status | new => confirmed | ||||||||||||
07-11-2006 09:55 | Alexandre Berge | Relationship added | parent of 0000112 | ||||||||||||
07-11-2006 10:41 | Alexandre Berge | Relationship added | has duplicate 0000011 | ||||||||||||
07-11-2006 10:45 | Alexandre Berge | Relationship deleted | has duplicate 0000011 | ||||||||||||
07-11-2006 10:45 | Alexandre Berge | Relationship added | parent of 0000011 | ||||||||||||
07-11-2006 10:47 | Alexandre Berge | Note Deleted: 0000189 | |||||||||||||
07-11-2006 10:48 | Alexandre Berge | Relationship deleted | parent of 0000112 | ||||||||||||
07-11-2006 10:49 | Alexandre Berge | Relationship added | related to 0000112 | ||||||||||||
07-11-2006 11:26 | Alexandre Berge | Status | confirmed => assigned | ||||||||||||
07-11-2006 11:26 | Alexandre Berge | Assigned To | => Alexandre Berge | ||||||||||||
07-11-2006 17:33 | Alexandre Berge | Note Added: 0000225 | |||||||||||||
12-09-2007 18:48 | user10 | Project | @3@ => IPv6 Testing Conformance (TTCN3 + TPs) | ||||||||||||
29-10-2007 13:51 | Alexandre Berge | Category | Test Case (TTCN3) => Test Case (TTCN3 ATS) | ||||||||||||
30-10-2007 11:44 | Alexandre Berge | Status | assigned => resolved | ||||||||||||
30-10-2007 11:44 | Alexandre Berge | Resolution | open => fixed |
Notes | |||||
|
|||||
|
|