ETSI's Bug Tracker - ASN.1
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0006053ASN.1Base Specpublic19-04-2012 13:3815-05-2012 10:34
ReporterSebastian Muellers 
Assigned ToAndras Kovacs 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version 
Target VersionFixed in Versionv0.0.1 
Summary0006053: resolution of deltaTime
DescriptionRegarding the resolution of deltatime I checked with SAE. The resolution should be 10 ms, but keeping the 16 bit, i.e. the delta time is increased to 655349 ms, 65535 = not available

Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
19-04-2012 13:38Sebastian MuellersNew Issue
25-04-2012 16:52Sebastian MuellersStatusnew => assigned
25-04-2012 16:52Sebastian MuellersAssigned To => Andras Kovacs
30-04-2012 19:04Andras KovacsStatusassigned => resolved
30-04-2012 19:04Andras KovacsResolutionopen => fixed
30-04-2012 19:04Andras KovacsNote Added: 0010593
15-05-2012 10:34Sebastian MuellersStatusresolved => closed
15-05-2012 10:34Sebastian MuellersFixed in Version => v0.0.1

Notes
(0010593)
Andras Kovacs   
30-04-2012 19:04   
I have changed the PathDeltaTime in the ITS container as follows:
PathDeltaTime ::= INTEGER { tenMilliSecondsInPast(1), unavailable(65535) } (0..65535, ...)
Now the base range can only represent values in the past (this is what WG1 wanted), but I kept the extensibility of this type, so that later on we can also send path descriptions describing a future path

In the CAM I kept the GenerationDeltaTime resolution according to the definition in the xls table:
 GenerationDeltaTime ::= INTEGER { oneMilliSec(1), unavailable(65535) } (0..65535)