Classic management technology standards
Industry standards
The NFM-P incorporates industry standards and open-standard interfaces. The following table lists and describes the technology standards and interfaces that are represented in the NFM-P design.
Table A-2: Industry standards consulted in NFM-P design
|
Standard |
Description |
|---|---|
|
3GPP |
3rd Generation Partnership Project IRPs for CORBA R8 and SOAP/XML R8 Solution Sets |
|
draft-grant-tacacs-02.txt |
TACACS+ client |
|
draft-ylonen-ssh-protocol-00.txt |
SSH |
|
EJB |
Java EE Enterprise Java Session Bean version 2.1 |
|
HTML5 |
HyperText Markup Language 5 |
|
HTTP(S) |
HyperText Transfer Protocol (Secure) version 1.1 |
|
ITU-T X.721 |
SMI |
|
ITU-T X.734 |
Event report management function |
|
Java SE |
Java Standard Edition version 8 |
|
JBOSS EAP |
Java Bean Open Source Software Enterprise Application Platform version 7 |
|
JMS |
Java Message Service version 1.1 |
|
JSON |
ECMA-404 JavaScript Object Notation Data Interchange Format |
|
JS/ECMAScript 5 |
ECMA-262 ECMA Script Language Specification |
|
M.3100/3120 |
Equipment and connection models |
|
MTOSI |
Compliance of generic network objects, inventory retrieval, and JMS over XML |
|
RFC 0959 |
FTP |
|
RFC 1034 |
DNS |
|
RFC 1213 |
SNMPv1 |
|
RFC 1738 |
Uniform Resource Locators (URL) |
|
RFC 2138 |
RADIUS client 2618 |
|
RFC 2328 |
OSPFv2 |
|
RFC 2385 |
MD5 encryption |
|
RFC 2474 |
DS Field in IPv4 and IPv6 Headers |
|
RFC 2547bis |
BGP/MPLS VPN |
|
RFC 2684 |
Multiprotocol Encapsulation over ATM |
|
RFC 3107 |
Labeling in BGP-4 |
|
RFC 3411-3415 |
SNMPv3 |
|
RFC 3416 |
SNMPv2c |
|
RFC 4115 |
TrTCM |
|
RFC 4379 |
Detecting MPLS Data Plane Failures |
|
RFC 4761 |
VPLS |
|
RFC 5246 |
The Transport Layer Security (TLS) Protocol |
|
RFC 5340 |
OSPFv3 |
|
RFC 5925–5926 |
TCP Authentication Option |
|
RFC 5938 |
Individual Session Control for TWAMP |
|
RFC 6052 |
IPv6 Addressing of IPv4/IPv6 Translators |
|
RFC 6241 |
Network Configuration Protocol (NETCONF) |
|
RFC 6374 |
Packet Loss and Delay Measurement for MPLS Networks |
|
SOAP |
W3C SOAP 1.2 |
|
TMF 509/613 |
Network connectivity model |
|
TR-069 |
TR-069 (Amendment 1) by way of the Home Device Manager |
|
Velocity |
Velocity Engine 2.3 |
|
XML |
W3C XML 1.0 |
|
W3C Namespaces in XML | |
|
W3C XML schemas |
The following standards are considered in the NFM-P GUI design:
-
Sun Microsystems, Java Look and Feel Design Guidelines, Addison-Wesley Publishing Company, Reading, Massachusetts 1999
-
ANSI T1.232-1996, Operations, Administration, and Provisioning (OAM&P)- G Interface Specifications for Use with the Telecommunications Management Network (TMN)
-
Telcordia (Bell Core) GR-2914-CORE Sept. 98, Human Factors Requirements for Equipment to Improve Network Integrity
-
Telcordia (Bell Core) GR-826-CORE, June 1994, Issue 1, Section 10.2 of OTGR, User Interface Generic Requirements for Supporting Network Element Operations
-
ITU-T Recommendation Z.361 (02/99), Design guidelines for Human- Computer Interfaces (HCI) for the management of telecommunications networks
-
ETSI EG 201 204 v1.1.1 (1997-05), Human Factors (HF); User Interface design principles for the Telecommunications Management Network (TMN) applicable to the “G” Interface