ETSI's Bug Tracker - IPv6overGeoNetworking
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0005643IPv6overGeoNetworkingBase Specpublic03-08-2010 10:0709-09-2010 16:14
ReporterAndras Kovacs 
Assigned ToRoberto Baldessari 
PrioritynormalSeverityminorReproducibilityN/A
StatusresolvedResolutionno change required 
PlatformOSOS Version
Product Versionv0.0.7 
Target VersionFixed in VersionNext Release 
Summary0005643: TS102636-6-1 v0.0.7 section 8 and Annex A: missing prefix information in MIB
DescriptionSection 8 text states for processing of received unicasts:
"If the IPv6 source address has a scope greater than link-scope and one or more GVLs exist in the itsgn6aslVLTable whose GVL Area contains the GeoNetworking source node’s position, GN6ASL shall, among those GVLs, select one (if present) that is associated to a virtual interface for which that prefix is considered to be on-link"

However since there is no GVL-associated prefix information saved in the MIB, the on-link determination is only possible through querying of IPv6 routing data, which is a strange cross-border solution.
It is recommended to save prefix data in the MIB from the incoming Router Advertisements, so that on-link determination could be done directly before the GVL selection.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
03-08-2010 10:07Andras KovacsNew Issue
24-08-2010 10:45Sebastian MuellersProduct Version => v0.0.7
24-08-2010 10:48Sebastian MuellersStatusnew => assigned
24-08-2010 10:48Sebastian MuellersAssigned To => Roberto Baldessari
09-09-2010 16:14Roberto BaldessariStatusassigned => resolved
09-09-2010 16:14Roberto BaldessariFixed in Version => Next Release
09-09-2010 16:14Roberto BaldessariResolutionopen => no change required
09-09-2010 16:14Roberto BaldessariNote Added: 0009730

Notes
(0009730)
Roberto Baldessari   
09-09-2010 16:14   
IPv6 already maintains the Prefix List for prefix on-link determination. The IPv6 Prefix List is accessible by other protocol entities as it is part of the IPv6 MIB (ipv6AddrPrefixTable, RFC2465). It would not make sense to replicate a prefix list inside GN6ASL, as it would be an exactly replicated function. Please note that a single link may be assigned multiple prefixes and each prefix has a limited lifetime based on the RA parameters. All of that is already specified in IPv6 and GN6ASL can rely on it.
Please contact me if you don't considered the issue resolved.