ETSI's Bug Tracker |
Anonymous | Login | Signup for local Mantis account | 17-05-2024 20:08 IST |
Main | My View | View Issues | Change Log | Roadmap | Stop monitoring project |
View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||
0005642 | IPv6overGeoNetworking | Base Spec | public | 02-08-2010 20:16 | 08-09-2010 17:54 | ||||
Reporter | Andras Kovacs | ||||||||
Assigned To | Roberto Baldessari | ||||||||
Priority | normal | Severity | major | Reproducibility | N/A | ||||
Status | resolved | Resolution | fixed | ||||||
Platform | OS | OS Version | |||||||
Product Version | v0.0.7 | ||||||||
Target Version | Fixed in Version | Next Release | |||||||
Summary | 0005642: TS102636-6-1 v0.0.7 section 8: not enough clarity on the Ethernet header generation for received messages | ||||||||
Description | Based on various other sections, the following assumptions are made for message reception over a TAP virtual device, which should be clearly stated in the relevant paragraph of section 8: - the IPv6overGeoNetworking adaptation generates the Ethernet headers for the received IPv6 message - the Source MAC address is generated through reverse EUI-64 generation procedure from the Sending GN_Address - the Destination MAC address is set to the Ethernet broadcast address for Multicast/Anycast message types - the Destination MAC address is generated through reverse EUI-64 generation procedure from the Destination GN_Address for Unicast message types - the Ethertype is set to IPv6 or ICMPv6 according to received message type Please confirm these assumptions, as some test cases are based on the above. | ||||||||
Tags | No tags attached. | ||||||||
Attached Files | |||||||||
Notes | |
(0009729) Roberto Baldessari (developer) 08-09-2010 17:54 |
Issue 0005642 resolved in v0.0.8 by adding annex D.2 "Packet delivery with Ethernet V2.0/IEEE 802.3 LAN virtual interfaces" which explains the steps undertaken by an implementation using Ethernet virtual interfaces. Please note that the operations of the virtual interfaces are implementation-specific and they can only be recommended in an informative annex. Section 8 (and the whole doc) defines logical operations based on SAPs and in an virtual interface type-independent way. e.g.: using Ethernet VI and creating Ethernet frames to be passed up/down is a way to implement the SAP |
Issue History | |||
Date Modified | Username | Field | Change |
02-08-2010 20:16 | Andras Kovacs | New Issue | |
24-08-2010 10:45 | Sebastian Muellers | Product Version | => v0.0.7 |
24-08-2010 10:48 | Sebastian Muellers | Status | new => assigned |
24-08-2010 10:48 | Sebastian Muellers | Assigned To | => Roberto Baldessari |
08-09-2010 17:54 | Roberto Baldessari | Status | assigned => resolved |
08-09-2010 17:54 | Roberto Baldessari | Fixed in Version | => Next Release |
08-09-2010 17:54 | Roberto Baldessari | Resolution | open => fixed |
08-09-2010 17:54 | Roberto Baldessari | Note Added: 0009729 |
MantisBT 1.2.14 [^] Copyright © 2000 - 2024 MantisBT Team |