1 Scope
2
References
3
Definitions
3.19 Definitions imported from other Recommendations
4
Abbreviations and acronyms
5
Conventions
6
Introduction to the F interface
6.1 Why Is The F interface needed?
7
F interface architecture
7.1 The F interface within the TMN architecture
7.2 TMN functional architecture and the F interface
7.3 TMN Physical architecture and the F interface
7.4 TMN information architecture and the F interface
7.5 F interface/f reference point and the g reference point
7.6 Summary of architectural implications for requirements
8
TMN user’s requirements impacting the F interface
8.1 General requirements
8.2 Task-related user requirements
9
Initialization requirements
10 Object management requirements
10.1 Relationships between WOs and MOs
10.1.1 UMO/MO cardinality
10.2 Naming
10.3 Retrieval
services
10.4 Modification services
10.5 Notification services
10.6 Create services
10.7 Destruction services
11 Shared Management Knowledge
requirements
11.1 Roles
11.2 Establishment of Shared Management Knowledge
12 Event registration/notification
requirements
12.1 Receiving event notifications
12.2 Controlling event notification
13 Location transparencies
requirements
14 Data consistency requirements
15 Quality, performance, and
OA&M requirements
15.1 Initialization performance
15.2 Message transfer
15.3 Reliability, availability, survivability
15.4 Software management
15.5 Real-time message
management
16 Security requirements
16.1 User identification requirements
16.2 Authentication
16.3 Access control
16.4 Data integrity
16.5 Privacy
16.6 Auditing
17 Physical implementation requirements
18 What’s part of WSF but not part
of the F interface
Appendix I – Recommendation M.3300
(1992)
Appendice II – Bibliography