1 Introduction on the TMN F Interface
    1.1 Why Is The F Interface Needed?
    1.2 Document Organization
    1.3 The F Interface Within The TMN Architecture
          1.3.1 F Interface Within the TMN Functional
                 Architecture
          Figure 1-1
          1.3.2 F Interface Within the TMN Physical
                 Architecture
          1.3.3 F Interface Within the TMN Information
                 Architecture
    1.4 F Interface/Reference Point Versus The g Reference
          Point
2 TMN User's Requirements Impacting the F Interface
    2.1 General Requirements
    2.2 Task-Related User Requirements
    2.3 Management Services F Interface Requirements
3 Initialization Of An F Interface Association Requirements
4 Communications Styles Between TMN Building Blocks
    4.1 Propagation of Management Mechanisms
    4.2 Communications Between WS and OS
    4.3 For System Management of the WS
    4.4 For System Management of the OS
    4.5 Communications Between WS and NE
5 Resource Representation Management Requirements
    5.1 Resource Representations
    5.2 Naming
    5.3 Retrieval Services
    5.4 Modification Services
    5.5 Notification Services
    5.6 Create Services
    5.7 Destruction Services
    5.8 Representations of Support Entities in the WS
    5.9 What's Not In The Interface
6 Shared Management Knowledge Requirements
    6.1 Roles
    6.2 Establishment of Shared Management Knowledge
    6.3 Management Information Conversion Over F Interface
    6.4 What's Not Part of the F Interface
7 Even Registration/Notification Requirements
    7.1 Receiving Event Notifications
    7.2 Controlling Event Notification
    7.3 Examples
    7.4 Generic Management Services
    7.5 What's Not Part of the F Interface
8 Logs and Log Management Requirements
9 Location Transparencies Requirements
    9.1 Requirements from TMN
    9.2 TMN Functional Components
    9.3 Naming/Addressing Support
    9.4 Shared Management Knowledge
    9.5 Security Support
    9.6 Administrative Usage
    9.7 Other Distribution Transparency Services
10 Transaction Management Requirements and Concurrency Control
    Requirements
    10.1 Transaction Management
    10.2 Concurrency Control
    10.3 Resource Allocation and Deadlock Requirements
11 Data Consistency Requirements
12 Performance, Reliability, Availability, etc. Requirements
    12.1 Message Transfer
    12.2 Reliability, Availability, Survivability
    12.3 Software Management
    12.4 Real-time Message Management
    12.5 Cost
13 Security Requirements
    13.1 Security Threats
    13.2 Security Requirements Impacting the F Interface
          13.2.1 User Identification Requirements Impacting
                  F Interface
          13.2.2 Authentication Requirements Impacting
                  F Interface
          13.2.3 Access Control Requirements Impacting F
                  Interface
          13.2.4 Data Integrity Requirements Impacting
                  F Interface
          13.2.5 Privacy Requirements Impacting F Interface
          13.2.6 Audit Requirements Impacting F Interface
14 Requirements Which Will Impact Information Models
15 F Interface Requirements and Software/Hardware
    Implementation
16 TMN Interface Conformance and the F Interface
References
List of Figures
1-1 F Interface Within The TMN Functional Architecture
1-2 F Interface Within the TMN Physical Architecture
1-3 F Interface Within the TMN Information Architecture
5-1 Relationship Between User Interface Objects, WS Resource
    Representations, and Managed Resource Representations
5-2 Closing a UI View
6-1 Managed Resource Representations Mapped to Multiple WSs
9-1 Location Transparency Services and the F Interface