ANSI INCITS 288 : 1999

1 Scope
2 Normative References
   2.1 Approved references
   2.2 References under development
   2.3 Other references
3 Definitions and conventions
   3.1 Definitions
   3.2 Editorial Conventions
   3.3 Abbreviations, acronyms and symbols
4 Common transport for FC services (CT)
   4.1 Overview
   4.2 General concepts
   4.3 CT protocol
   4.4 FC-2 mapping and management
   4.5 Error handling
   4.6 FS information units
   4.7 Correlation of requests and responses
5 Overview of directory (name) service
   5.1 Introduction to the directory service model
6 Name Server
   6.1 Name Service protocol
   6.2 Transportation of Name Server IUs
   6.3 FC-PH constructs
   6.4 Name Server objects - Formats
   6.5 FS_RJT reason code explanations
   6.6 Queries
   6.7 Registration
   6.8 Deregistration
7 SNMP based management service
   7.1 Configuration management
   7.2 Performance management
   7.3 Fault management
   7.4 Security management
   7.5 Accounting management
   7.6 SNMP model
   7.7 Native SNMP Mapping
   7.8 Management information base
   7.9 Agent addressing
   7.10 Other management models
8 Time service
   8.1 Functional model
   8.2 Basic TS protocol interaction
   8.3 Distributed time service
9 Alias Server
   9.1 Alias service protocol
   9.2 Use of FC-PH constructs
   9.3 Information units
   9.4 Alias service requests
   9.5 Alias server replies
   9.6 Function flow
   9.7 Alias server functions
   9.8 Alias routing
   9.9 IPA Considerations
10 Security-key distribution service
   10.1 Introduction
   10.2 Communications model
   10.3 FC-PH Constructs
   10.4 Security-key services
   10.5 Security Data Bases
   10.6 Encryption Algorithm
Annex A (Informative) Service Interface Provided by FC-CT
      A.1 FC-CT Session Services
      A.2 FC-CT Transaction Services
Annex B (Informative) Encryption Algorithm Recommendation
      B.1 DES
      B.2 RC2 and RC4
      B.3 Minimal Key Length
Annex C (Informative) Name Server Request Mnemonics
      C.1 Changed Name Server Mnemonics