DynamicTMN® Protocol Stacks

Monfox provides a variety of protocol stack implementations for use with the DynamicTMN® tools and Software Development Kits (SDKs). The currently supported DynamicTMN® stacks are:

• DynamicTMN® RFC1006 Stack
• DynamicTMN® ROSE Stack
• DynamicTMN® LOCAL Stack
• DynamicTMN® eBonding Stack
• DynamicTMN® NPAC/LNP Stack
• DynamicTMN® OSI/X.25 Stack Adaptor

If you require an protocol stack other than the ones listed above, please contact us. We can typically develop a custom protocol stack for both proprietary and standard security/communication specifications as little or no additional cost to you.

The DynamicTMN® RFC1006 Stack is a plug-in RFC1006 protocol adapter module for use with the DynamicTMN® SDKs and tools. It provides a 100% Java, fully-interoperable, standard-compliant implementation of the RFC1006 standard for OSI over TCP including an implementation of the upper layer OSI standards required for interoperable communication between CMISE and ACSE application service elements. The following standards are implemented by the RFC1006 stack:

• RFC 1006: OSI over TCPIP (CMIP/OSI over TCP/IP)
• ITU-T X.214: OSI - Transport Service Definition
• ITU-T X.215: OSI - Session Service Definition
• ITU-T X.216: OSI - Presentation Service Definition
• ITU-T X.217: Association Control Service Element (ACSE) Definition
• ITU-T X.219: Remote Operations (ROSE) Service Definition
• ITU-T X.224: OSI - Transport Protocol Specification
• ITU-T X.225: OSI - Session Protocol Specification
• ITU-T X.226: OSI - Presentation Protocol Specification
• ITU-T X.227: Association Control Service Element (ACSE) Protocol
• ITU-T X.229: Remote Operations (ROSE) Protocol

---

Features:

• 100% Java (no JNI)
• Easy to use Java Stack API
• Easily configurable via XML configuration files
• Runs in the application space (no separate stack processes)
• Extensible Stack API (add custom stack security, etc)
• Interoperable with all 3rd party RFC1006 stacks

---

Java Platform Requirements:

• Java 2: JDK 1.2 or newer

---

NOTE 1: the DynamicTMN® RFC1006 Stack is included with all DynamicTMN® Protocol SDKs and management tools.

NOTE 2: Monfox also offers the DynamicTMN® OSI/RC1006 Stack SDK which is a Standalone Java OSI/RFC1006 Stack and API for use in developing other types of OSI applications which use RFC1006 for the lower layer protocol.

The DynamicTMN® ROSE/TCPIP Stack is a plug-in lightweight protocol adapter module for use with the DynamicTMN® SDKs and tools. The ROSE stack is typically used for optimized communication between different DynamicTMN® applications. It bypasses OSI protocol layers 4-6 by transferring CMIP messages using ROSE protocol data units (PDUs) directly over a TCP/IP connection.

The following standards are implemented by the ROSE stack:

• ITU-T X.219: Remote Operations (ROSE) Service Definition
• ITU-T X.229: Remote Operations (ROSE) Protocol

---

Features:

• 100% Java (no JNI)
• Lightweight for optimal performance
• Easy to use Java Stack API
• Easily configurable via XML configuration files
• Runs in the application space (no separate stack processes)
• Extensible Stack API (add custom stack security, etc)

---

Java Platform Requirements:

• Java 2: JDK 1.2 or newer

---

NOTE: the DynamicTMN® ROSE Stack is included with all DynamicTMN® Protocol SDKs and management tools.

The DynamicTMN® LOCAL Stack is a plug-in CMIP protocol adapter module for use with the DynamicTMN® SDKs. It allows for optimized communication between DynamicTMN® Manager and Agent entities operating within the same JVM. This stack is often used to add a Craft Interface or other CMIP manager module to an agent application.

---

Features:

• 100% Java
• Easy to use Java Stack API
• Easily configurable via XML configuration files
• Runs in the application space (no separate stack processes)
• Encoding free ultra-lightweight/high-performance stack
• Used only for Intra-JVM communications

---

Java Platform Requirements:

• Java 2: JDK 1.2 or newer

---

NOTE: the DynamicTMN® LOCAL Stack is included with all DynamicTMN® Protocol SDKs and management tools.

The DynamicTMN® eBonding Stack is a specialized plug-in protocol adapter module for use with the DynamicTMN® SDKs and tools. It implements the ANSI TR.40 Security specification used by eBonding gateways in North America. This stack provides the ability to establish a secure/authenticated connection between your DynamicTMN® application and another eBonding gateway. The following standards are implemented by the eBonding stack:

• ANSI.TR-40: Security Requirements for Electronic Bonding
• RFC 1006: OSI over TCPIP (CMIP/OSI over TCP/IP)
• ITU-T X.214: OSI - Transport Service Definition
• ITU-T X.215: OSI - Session Service Definition
• ITU-T X.216: OSI - Presentation Service Definition
• ITU-T X.217: Association Control Service Element (ACSE) Definition
• ITU-T X.219: Remote Operations (ROSE) Service Definition
• ITU-T X.224: OSI - Transport Protocol Specification
• ITU-T X.225: OSI - Session Protocol Specification
• ITU-T X.226: OSI - Presentation Protocol Specification
• ITU-T X.227: Association Control Service Element (ACSE) Protocol
• ITU-T X.229: Remote Operations (ROSE) Protocol

---

Features:

• 100% Java (no JNI)
• Easy to use Java Stack API
• Easily configurable via XML configuration files
• Runs in the application space (no separate stack processes)
• Supports automatic key changes
• Uses industry standard agent gateway key files
• Interoperable with all 3rd party eBonding gateways

---

Java Platform Requirements:

• Java 2 with JCE: [JDK 1.2|1.3 + JCE1.2.2] or [ J2SDK1.4 or newer ]

---

NOTE: the DynamicTMN® eBonding Stack is included in the DynamicTMN® CMIP eBonding/TA SDK.

The DynamicTMN® NPAC/LNP Stack is a specialized plug-in protocol adapter module for use with the DynamicTMN® SDKs and tools. It implements the NPAC SMS Interoperable Interface Specification (IIS) requirements for Secure Assocation Establishment used by the different regional NPAC SMS in North America. This stack provides the ability to establish, maintain and recover secure/authenticated communications between your DynamicTMN® SOA or LSMS application and any of the regional NPAC SMS instances.

The LNP stack also provides an LNP Key Administration tool which performs the following functions defined in the North American Numbering Council (NANC) Functional Requirements Specification:

• NPAC RSA public and private key file generation
• NPAC RSA public key acknowledgement file generation
• NPAC RSA public key file validation

The following standards are implemented by the NPAC/LNP stack:

• NPAC IIS: LNP Secure Association Establishment
• RFC 1006: OSI over TCPIP (CMIP/OSI over TCP/IP)
• ITU-T X.214: OSI - Transport Service Definition
• ITU-T X.215: OSI - Session Service Definition
• ITU-T X.216: OSI - Presentation Service Definition
• ITU-T X.217: Association Control Service Element (ACSE) Definition
• ITU-T X.219: Remote Operations (ROSE) Service Definition
• ITU-T X.224: OSI - Transport Protocol Specification
• ITU-T X.225: OSI - Session Protocol Specification
• ITU-T X.226: OSI - Presentation Protocol Specification
• ITU-T X.227: Association Control Service Element (ACSE) Protocol
• ITU-T X.229: Remote Operations (ROSE) Protocol

---

Features:

• 100% Java (no JNI)
• Easy to use Java LNP Stack API
• Easily configurable via XML configuration files
• Runs in the application space (no separate stack processes)
• Supports automatic key change according to the NPAC IIS procedure
• Uses NPAC defined RSA key file formats
• Interoperable with regional NPAC SMSs

---

Java Platform Requirements:

• Java 2: J2SDK1.4 or newer

NOTE: the DynamicTMN® NPAC/LNP Stack is included in the DynamicTMN® CMIP NPAC/LNP SDK.

The DynamicTMN® OSI/X.25 Stack Adaptor is a standalone RFC1006 to OSI gateway application for the Solaris operating system. The adaptor runs as a standalone process which allows a DynamicTMN® application to communicate over a full OSI stack through an X.25 or OSI LAN interface. It acts as a transport layer gateway between the DynamicTMN® application and the OSI/X.25 network.

---

Features:

• runs as a standalone Solaris process
• configurable through simple configuration files
• allows for both agent and manager DynamicTMN® applications
• works with ANY DynamicTMN® application
• no changes required to existing DynamicTMN® applications

---

Platform Requirements: (must be purchased from Sun Microsystems)

• Sun SPARC workstation or server
• Solaris 8 or newer
• Solstice OSI 9.0/SPARC
• Solstice X.25 9.2/SPARC (for X.25 networks)
• Sun HSI Card (for X.25 networks)

Note: the stack adaptor is a an OS neutral application written using the the Transport Layer Interface (TLI) C API supported by many of the traditional OSI stack vendors. If you require a different hardware or software configuration from that specified above, please contact us at info@monfox.com to see if we can support your specific requirements.