STANDARD

1. The name of the specification.

M.3016.4 Security for the Management Plane: Profile Proforma

2. A short statement (<100 words) of the purpose and function of the specification.

This Recommendation specifies a Proforma for the security requirements, mechanisms and services in Recommendations M.3016.1-3. The Proforma when completed by different organizations results in a profile for the security requirements, services and mechanisms. These profiles may be used by implementations to specify conformance.

3. The version number (or other distinct identifier) of the most recently approved version of the specification.

M.3016.4-2005

4. If the specification is part of a group of explicitly related specifications from the same source, the name of the group of specifications.

NGN Management

5. URI for the normative text of the specification.

www.itu.int/rec/recommendation.asp?type=products&lang=e&parent=T-REC-M

SOURCE

6. The name of the SDO that generated/authored/hosted the specification.

ITU-T (Study Group 4)

7. URI for the SDO.

www.itu.int/ITU-T/studygroups/com04/index.asp

8. The level of approval that the SDO has conferred on the specification as described by the SDO's process.

Approved

9. The language or languages in which the specification is available.

English initially, Spanish, French, Arabic, Chinese, Russian

SUBJECT

10. Which of the ITU-T TMN FCAPS model layers does the specification's functionality address?

• Fault Management: Fixing broken resources.
• Configuration Management: Controlling a resource's operational parameters.
• Accounting Management: Recording and analyzing resource use.
• Performance Management: Controlling speed and efficiency of resource use.
• Security Management: Controlling access to resources.

12. Where does the specification directly operate, as among the layers defined in the ISO Open System Interconnect (OSI) model?

• Physical layer
• Data link layer
• Network layer
• Transport layer
• Session layer
• Presentation layer
• Application layer.

13. Which of the following (CIM based) functional areas does the model of the specification address?

• Security

OPTIONAL

14. The level of approval of the specification in this generic lifecycle taxonomy:

• Approved

15. URI for the applicable SDO's patent and copyright rules, if any, applicable to development and use of the specification.

N/A

16. URI for the SDO's posting location, if any, for notices from participants or individuals regarding claims under number 15.

N/A

17. Interoperability, conformance, or certification test activity for the specification (by owner name or URI).

N/A

18. Known implementations of the specification (by owner name or URI).

N/A

19. A list (or URI pointer to same) of the other specifications that are normatively referenced in the specification.

N/A

20. A list (or URI pointer to same) of the other specifications that are explicitly referenced in the specification (except the ones listed in number 19).

N/A

21. A list (or URI pointer to same) of otherspecifications with which the specification may (speculatively) interoperate or act in complementary, compatible fashion.

N/A

22. A list (or URI pointer to same) of other specifications. (Whether or not substitutable.)

T1.276 (approved by ATIS TMOC)