ETSI's Bug Tracker |
Anonymous | Login | Signup for local Mantis account | 17-05-2024 02:22 IST |
Main | My View | View Issues | Change Log | Roadmap | Monitor project |
View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||||||
0005573 | 3GPP SA5 Bug Tracking | Quality | public | 22-06-2010 16:53 | 18-02-2011 09:02 | ||||||||
Reporter | user601 | ||||||||||||
Assigned To | Clemens Suerbaum | ||||||||||||
Priority | normal | Severity | minor | Reproducibility | N/A | ||||||||
Status | assigned | Resolution | open | ||||||||||
Platform | OS | OS Version | |||||||||||
Product Version | |||||||||||||
Target Version | Fixed in Version | ||||||||||||
Summary | 0005573: Issues with 32.121 | ||||||||||||
Description | Introduction: The spec titles here do not match 32.122 or the list of spec names at http://www.3gpp.org/ftp/Specs/html-info/TSG-WG--S5.htm [^] "32.121: "Advanced Alarm Management Integration Reference Point (IRP): Requirements"; 32.122: "Advanced Alarm Management Integration Reference Point (IRP): Information Service (IS)"; 32.123: " Advanced Alarm Management Integration Reference Point (IRP): Common Object Request Broker Architecture (CORBA) Solution Set"." References: It's remarkable that a spec called "Advanced Alarm Management" can exist without reference to the Alarm IRP 32.111-x, and still mention "getAlarmList", "alarm notifications" and also state "In the context of this specification the words 'significant' and 'insignificant' have the following implications: IRPAgent shall not report alarms categorized as insignificant. IRPAgent shall report all significant alarms. " without specifying "how" alarms are to be reported…… I guess this is not editorial though ;-) 4.2 Requirements. I am not 100% up to date with recent methodology but the requirements here have a strange format and numbering - I suspect this spec was approved before the methodology improvements? Also, one "requirement" says "Certain types of categorization rules are only to be applied to read the alarm list. The term used for these rules is alarm partitioning rules." Surely this should be defined in the Definitions and Abbreviations, and not within a requirement. | ||||||||||||
Tags | No tags attached. | ||||||||||||
TS/TR Rapporteur | |||||||||||||
Source (company - Author) | Ericsson - John Power | ||||||||||||
TS number | 32.121 | ||||||||||||
TS version | 8.0.0/9.0.0 | ||||||||||||
Clause Reference(s) | Several clauses throughout the spec | ||||||||||||
Attached Files | |||||||||||||
Issue History | |||
Date Modified | Username | Field | Change |
22-06-2010 16:53 | user601 | New Issue | |
22-06-2010 16:53 | user601 | Source (company - Author) | => Ericsson - John Power |
22-06-2010 16:53 | user601 | TS number | => 32.121 |
22-06-2010 16:53 | user601 | TS version | => 8.0.0/9.0.0 |
22-06-2010 16:53 | user601 | Clause Reference(s) | => Several clauses throughout the spec |
18-02-2011 09:02 | Christian Toche | Status | new => assigned |
18-02-2011 09:02 | Christian Toche | Assigned To | => Clemens Suerbaum |
MantisBT 1.2.14 [^] Copyright © 2000 - 2024 MantisBT Team |