MTNM Release Notes

Release 3.5

RN306
Version 2.1

August 2008
TeleManagement Forum 2007-2009

MTNM Release Notes for Release 3.5

0B

Notice

No recipient of this document shall in any way interpret this document

as representing a position or agreement of TM Forum or its members.
This document is a draft working document of TM Forum and is
provided solely for comments and evaluation. It is not a Forum
Approved Document and is solely circulated for the purposes of
assisting TM Forum in the preparation of a final document in
furtherance of the aims and mission of TM Forum.
Although it is a copyrighted document of TM Forum:

Members of TM Forum are only granted the limited copyright

waiver to distribute this document within their companies and
may not make paper or electronic copies for distribution
outside of their companies.

Non-members of the TM Forum are not permitted to make

copies (paper or electronic) of this draft document other than
for their internal use for the sole purpose of making comments
thereon directly to TM Forum.

If this document forms part of a supply of information in

support of an Industry Group Liaison relationship, the
document may only be used as part of the work identified in
the Liaison and may not be used or further distributed for any
other purposes

Any use of this document by the recipient, other than as set forth
specifically herein, is at its own risk, and under no circumstances will
TM Forum be liable for direct or indirect damages or any costs or
losses resulting from the use of this document by the recipient.
This document is governed by all of the terms and conditions of the
Agreement on Intellectual Property Rights between TMForum and its
members, and may involve a claim of patent rights by one or more
TMForum members or by non-members of TMForum.
Direct inquiries to the TM Forum office:
240 Headquarters Plaza,
East Tower 10th Floor,
Morristown, NJ 07960 USA
Tel No. +1 973 944 5100
Fax No. +1 973 944 5110
TM Forum Web Page: www.tmforum.org
HU

RN312, Version 2.1

UH

TeleManagement Forum 2007-2009

Page 2 of 15

MTNM Release Notes for Release 3.5

1B

Table of Contents

Notice.................................................................................................................................................. 2
Table of Contents................................................................................................................................ 3
List of Tables....................................................................................................................................... 3
Overview of MTNM Release 3.5........................................................................................................... 4
Summary of New Features............................................................................................................ 4
Connectionless Technology Management..................................................................................4
ASON Control Pane Management............................................................................................. 5
Release Definition............................................................................................................................... 7
Document Release Description..................................................................................................... 7
Major Deliverables.................................................................................................................. 10
Model Release Description.......................................................................................................... 11
Administrative Appendix................................................................................................................... 14
Document History...................................................................................................................... 14
Contact....................................................................................................................................... 14
Acknowledgments....................................................................................................................... 15
About TeleManagement Forum.................................................................................................... 15

2B

Table 1. Main Documents in MTNM Release 3.5

Table 2. Supporting Documents in MTNM Release 3.5

Table 3. MTNM Release 3.5 Document Packaging

RN312, Version 2.1

List of Tables

TeleManagement Forum 2007-2009

8
11

Page 3 of 15

MTNM Release Notes for Release 3.5

3B

Overview of MTNM Release 3.5

MTNM Release 3.5 includes two major enhancements of functionality overRelease 3.0. The two
enhancements are:

Connectionless Technology Management

ASON Control Plane Management

Connectionless Technology Management adds support for the management of Connectionless

Technologies with a specific focus in this release on support for Ethernet technology and related
technologies as defined in ITU-T G.8011 and Metro Ethernet Forum (MEF) The term Ethernet
refers to the Ethernet MAC layer (ETH).
ASON Control Plane Management adds support for the management of Control Plane established
Call and Connections. It does not address the configuration/setup of a Control Plane environment
its focus is on enabling an NMS to request that Calls be created by the Control Plane and to
subsequently manage those Calls until such time as the Calls are deleted.

6B

Summary of New Features

13B

Connectionless Technology Management

The MTNM Release 3.5 connectionless solution is primarily targeted at managing Ethernet over
traditional or next generation transport network such as SONET/SDH, WDM, ATM or RPR.This
release provides fully integrated support for SONET/SDH, WDM and ATM from the previous
MTNM release (Release 3.0) while only the access points (Connectionless Port Termination Points
(CPTPs)) are supported in case of RPR transport.
Support for point-to-point services (Ethernet Private Line (EPL), Ethernet Virtual Private Line
(EVPL)) are provided in compliance with the MEF definitions. MEF Phase 2 however has not yet
completed its work on multipoint services (Ethernet Private Local Area Network (EPLAN), Ethernet
Virtual Private Local Area Network (EVPLAN)) at the time Release 3.5 is published. Therefore,
future alignment with MEF (Phase 2) will be required in a subsequent MTMN release. With regard
to the EPL, MTNM Release 3.5 provides an alternative to the existing MTNM Release 3.0 support
based on the connection oriented model and TP containment relationships. An EMS may support
either or both EPL implementations (though not simultaneously on the same object instances) in
order to meet the objectives of the NMS.
The following capabilities are supported in this release:

RN312, Version 2.1

Point-to-point services (EPL, EVPL) in compliance with MEF Service Definition Phase 1

Multipoint services (EPLAN, EVPLAN)

Link Aggregation (LAG)

TeleManagement Forum 2007-2009

Page 4 of 15

MTNM Release Notes for Release 3.5

Point-to-point Call (represent connectionless connectivity between NEs) provisioning

(including Control Plane option)

Diverse routes for point-to-point Calls

Multipoint Topological Links (e.g., for representing RPR transport connectivity)

CPTP provisioning

Fixed MFD modelling (e.g., direct mapped EPL services)

VLAN-unaware routing as per IEEE 802.1D

C-VLAN based tagging as per IEEE 802.1Q

S-VLAN based tagging as per 802.1ad

Port (UNI/NNI), C-VLAN/EVC and/or CoS (802.1p) based classification

Spanning Tree management

Ingress traffic conditioning

C-Tag/S-Tag translation

Non routed layer 2 networks (using singleton Flow Domains)

Integrated or separate transport (SONET/SDH, etc.) and Ethernet EMSs

To support the abovementioned features the following new terms have been defined:

14B

Flow Domain (FD)

Matrix Flow Domain (MFD)

Connectionless Port Termination Point (CPTP)

Flow Point (FP)

Flow Domain Fragment (FDFr)

TC Profile

ASON Control Pane Management

The MTNM Release 3.5 ASON Control Plane solution is primarily targeted at managing Calls and
Connections that may be established through the use of Control Plane protocols.
The Control Plane automates the process for connection setup and tear down in an optical
network. The architecture of the Control Plane is described in ITU-T Recommendation G.8080.
This architecture provides a separation between the Call (which represents the service offered to
the user) and the Connections that deliver the service.
The architecture is described in terms of Control Plane components. The communication between
these components is separated from the bearer plane that is being controlled. To optimise the
performance of the Control Plane and maximize the reuse of existing control protocols the
addressing scheme used by the control components to reference the transport resources is
independent of the addressing scheme used by the management applications.
The request for a Call can originate from a customer directly via a UNI or from an OSS within an
operator's network. For connection request from the UNI the control plane automatically computes

RN312, Version 2.1

TeleManagement Forum 2007-2009

Page 5 of 15

MTNM Release Notes for Release 3.5

a route and initiates signalling to establish the connections. In the case of a request from the
network operator's OSS the request is directed to the ingress point for the call, the operator may
provide may control the routing of the connections by providing an explicit route or routing
constraints or allow the Control Plane freedom to compute the route. In all cases the Control Plane
initiates signalling to establish the required connections. The Control Plane can also perform
automatic restoration in the event of a traffic plane failure. When the failure has been repaired the
Control Plane may force the Connections to revert to their original (home) route.
To support the abovementioned features the following new terms have been defined:

RN312, Version 2.1

MultiLayer Routing Area (MLRA)

Call

Connection

MultiLayer Subnetwork Point Pool (MLSNPP)

MultiLayer Subnetwork Point Pool Link (MLSNPPLink)

Subnetwork Point Pool (SNPP)

Subnetwork Point (SNP)

TeleManagement Forum 2007-2009

Page 6 of 15

MTNM Release Notes for Release 3.5

4B

Release Definition

This section describes the documents included in MTNM Release 3.5.

7B

Document Release Description

As part of MTNM Release 3.0 all of the documents that were part of that release were baselined at
version 3.0. Prior to Release 3.0 the MTNM documents did not have associated version numbers.
For many of the documents that are specific to the MTNM product release 3.5 is the first time that
the document will have been updated since release 3.0 of MTNM; with the exception of those
documents that are also used by the MTOSI product.
All documents with a Mar 2007 date will have been updated specifically for MTNM Release 3.5. All
documents with a Release 3.5 version number of greater than 3.0 but with a date earlier than Mar
2007 will have been updated for the MTOSI product.
It should be noted that the Latest Date column in the table reflects the date of the last change to
the document. It does not necessarily reflect the date on which the document was uploaded to the
TMF Collaboration Workspace (CWS). This uploaded date is indicated in the Last Updated
column on the CWS.
The following two tables list the documents that have been modified for the MTNM Release 3.5.

Table 1. Main Documents in MTNM Release 3.5

Document

Title

Rel 3.0
version

Rel 3.5
version

Latest
Date

Delta

TMF513

MTNM Business
Agreement

3.0

3.2

Aug 2008

Added/updated requirements
and use cases for
Connectionless Technology and
ASON Control Plane
management.

TMF608

MTNM Information
Agreement

3.0

3.5

Aug 2008

Added/updated UML model for

Connectionless Technology and
ASON Control Plane
management.

TMF814

MTNM IDL Solution Set

3.0

3.2

Aug 2008

Added/updated IDL for

Connectionless Technology and
ASON Control Plane
management.

RN312, Version 2.1

TeleManagement Forum 2007-2009

Page 7 of 15

MTNM Release Notes for Release 3.5

Document

Title

Rel 3.0
version

Rel 3.5
version

Latest
Date

Delta

TM814A

MTNM Implementation
Statement and
Guidelines

3.0

3.1

Mar 2007

Updated to support changes to

TMF814.

Table 2. Supporting Documents in MTNM Release 3.5

Document

Title

Rel 3.0
version

Rel 3.5
version

Latest
Date

Delta

SD1-1

Additional Information
Usage

3.0

3.2

Apr 2008

Added new additional

information parameter
definitions.

SD1-2

MTNM Attribute Value

Change & State Change
Notifications

3.0

3.2

Feb 2008

Added support for the new

object classes.

SD1-3

Group Termiantion
Points and Bundled
SNC

3.0

3.0

Jun 2005

SD1-4

Changes between IA
Versions

3.0

5.0

Mar 2007

SD1-5

ATM Conformance
Definitions

3.0

3.0

Nov 2006

SD1-6

Contained TPs

3.0

3.3

Nov 2007

SD1-7

DSL Overview

3.0

3.1

Nov 2005

SD1-8

Coding of X.731 and

M.3100 State and Status
Information

3.0

3.2

Nov 2007

SD1-9

Coding of X.733 Alarm

information

3.0

3.1

Nov 2006

SD1-10

Equipment Model

3.0

3.1

Mar 2006

SD1-11

Feature Matrix

3.0

Release specific details

updated.

No longer part of the release.

Covered by this release note

SD1-12

Summary of MTNM
R3.0 features

3.0

SD1-13

GUI Cut-Through

3.0

3.0

Nov 2006

SD1-14

Inverse Multiplexing
Overview

3.0

3.2

Nov 2007

SD1-15

Iterator Usage

3.0

3.0

Nov 2006

RN312, Version 2.1

No longer part of the release.

Covered by this release note.

TeleManagement Forum 2007-2009

Page 8 of 15

MTNM Release Notes for Release 3.5

Document

Title

Rel 3.0
version

Rel 3.5
version

Latest
Date

Delta

SD1-16

Layered Parameters

3.0

3.3

Nov 2007

Added new layered

transmission parameter
definitions.

SD1-17

Layer Rates

3.0

3.3

Oct 2007

Added new layer rate

definitions.

SD1-18

Functional Modelling
Concepts

3.0

3.3

Aug 2008

Minor enhancements.

SD1-19

Location Identification

3.0

3.0

Apr 2005

SD1-20

Maintenance
Commands

3.0

3.2

Nov 2007

Added new maintenance

command definitions.

SD1-21

Traceability between IA
and SS

3.0

3.2

Jun 2007

Release specific details

updated.

SD1-22

Modelling Components

3.0

3.0

Apr 2005

SD1-23

SNC Management
Modes of Operation

3.0

3.0

Jun 2005

SD1-24

Native EMS Name

3.0

3.0

Nov2006

SD1-25

Multi-Technology
Network Management
support for a Naming
Convention

3.0

3.3

Dec 2007

Added support for the naming of

new object classes

SD1-26

Guidelines for Using the

OMG Notification and
Telecom Log Service

3.0

3.1

Mar 2007

Added definitions for the new

object classes.

SD1-27

Overview of the TMF

MTNM NML-EML
Interface

3.0

3.1

Mar 2007

Release specific details

updated.

SD1-28

Performance
Parameters

3.0

3.1

Oct 2006

SD1-29

PGP Parameters

3.0

3.0

Apr 2005

SD1-30

PM File Format
Definition

3.0

3.2

Dec 2005

SD1-31

PM example text file

3.0

No longer a separate supporting

document. Now part of SD1-30.

SD1-32

PM example Excel
spreadsheet file

3.0

No longer a separate supporting

document. Now part of SD1-30.

SD1-33

Specification of
probableCause strings

3.0

4.1

Oct 2006

SD1-34

Protection Switching

3.0

3.0

Apr 2005

SD1-35

State Diagrams

3.0

3.1

Mar 2007

SD1-36

SNC and Protection

3.0

3.1

Mar 2007

RN312, Version 2.1

Added new diagrams for Call

state changes.

TeleManagement Forum 2007-2009

Page 9 of 15

MTNM Release Notes for Release 3.5

Document

Title

Rel 3.0
version

Rel 3.5
version

Latest
Date

SD1-37

PM Threshold Types

3.0

3.0

Jun 2005

SD1-38

TMF814 Front Matter

3.0

3.2

Aug 2008

Release specific details

updated.

SD1-39

TMF608 HTML Front

Matter

0.0

1.0

Aug 2008

Release specific details

updated.

SD1-40

TMF608 MDL Front

Matter

0.0

1.0

Aug 2008

Release specific details

updated.

SD1-41

Clarification of
relationship between a
TPPool and its
TerminationPoints

3.0

3.0

Apr 2005

SD1-42

Traffic Parameters

3.0

3.1

Apr 2005

SD1-43

Programmatic
Versioning

3.0

3.0

Nov 2006

SD1-44

Connectionless
Technology
Management

1.1

Jun 2008

New in this release.

SD1-45

ASON Control Plane

Mangement-Primer

1.1

Nov 2007

New in this release.

SD1-46

ASON Control Plane

Mangement-Scenarios

1.0

Mar 2007

New in this release.

15B

Delta

Major Deliverables
The MTNM Release 3.5 output consists of 3 major deliverables, i.e., Business Agreement,
Information Agreement, the IDL Solution Set and the Implementation Statement.

16B

TMF513, MTNM Business Agreement

The MTNM business agreement document provides requirements and use cases. The
requirements pertain to the interface itself and describe what is expected of an EMS or NMS that
supports MTNM. The use cases provide interaction scenarios concerning EMSs and NMSs that
support MTNM.
For someone new to the MTNM specifications, it is recommended that one reads TMF513 after
reading the MTNM overview (i.e., this document)

17B

TMF608, MTNM Information Agreement

This document contains the protocol independent UML model for the MTNM interface. In addition
to being used for MTNM this model has also been used by the MTOSI product. However the
MTNM Release 3.5 product is a stand-alone product and as such no references to the MTOSI
product release deliverables are provide as part of MTNM Release 3.5.

RN312, Version 2.1

TeleManagement Forum 2007-2009

Page 10 of 15

MTNM Release Notes for Release 3.5

18B

TMF814, MTNM IDL Solution Set

This document and associated CORBA IDL provides the specification for the MTNM
implementation. This deliverable entails a brief overview of the MTNM CORBA IDL interface and
the CORBA IDL specification itself. The following supporting documents are closely related to
TMF814.

19B

TMF814A, MTNM Implementation Statement

This document provides a template for a compliance statement that is intended to be exchanged
between two parties that are intending to build an MTNM interface. It enables each party to
determine exactly what is supported by both parties implementation.
In addition to these main deliverables there are also a number of supporting documents that
provide additional information to better understand the interface and the functionality that it
supports. Although these documents by themselves are not considered to be a major deliverable
the collection of supporting documents are essential to understanding the MTNM interface.

8B

Model Release Description

The following table describes the various file packages available for MTNM Release 3.5. Note that
each of the major deliverables (i.e., TMF513, TMF608 and TMF814) are packaged along with the
supporting documents that they reference. RN306 will also be made available as a separate
document in addition to be included in each of the three packages listed in the table below.

Table 3. MTNM Release 3.5 Document Packaging

Document

Title

RN312

MTNM 3.5 Release Note

TMF513

MTNMI Business Agreement

TMF608

MTNM Information Agreement

TMF814

MTNM IDL Solution Set

TMF814A

MTNM Implematation
Statement

SD1-1

Additional Information Usage

SD1-2

MTNM Attribute Value Change

& State Change Notifications

SD1-3

Group Termiantion Points and

Bundled SNC

SD1-4

Changes between IA Versions

SD1-5

ATM Conformance Definitions

SD1-6
SD1-7

RN312, Version 2.1

TMF513

TMF608
X

TMF814

TMF814A

X
X
X
X

Contained TPs

DSL Overview

TeleManagement Forum 2007-2009

Page 11 of 15

MTNM Release Notes for Release 3.5

Document

Title

TMF513

TMF608

SD1-8

Coding of X.731 and M.3100

State and Status Information

SD1-9

Coding of X.733 Alarm

information

SD1-10

Equipment Model

SD1-13

GUI Cut-Through

SD1-14

Inverse Multiplexing Overview

SD1-15

Iterator Usage

SD1-16

Layered Parameters

SD1-17

Layer Rates

SD1-18

Functional Modelling Concepts

SD1-19

Location Identification

SD1-20

Maintenance Commands

SD1-21

Traceability between IA and SS

SD1-22

Modelling Components

SD1-23

SNC Management Modes of

Operation

SD1-24

Native EMS Name

SD1-25

Multi-Technology Network
Management support for a
Naming Convention

SD1-26

Guidelines for Using the OMG

Notification and Telecom Log
Service

SD1-27

Overview of the TMF MTNM

NML-EML Interface

SD1-28

Performance Parameters

SD1-29

PGP Parameters

SD1-30

PM File Format Definition

SD1-33

Specification of probableCause
strings

SD1-34

TMF814
X
X

X
X

X
X

X
X

Protection Switching

SD1-35

State Diagrams

SD1-36

SNC and Protection

SD1-37

PM Threshold Types

SD1-38

TMF814 Front Matter

SD1-39

TMF608 HTML Front Matter

RN312, Version 2.1

TMF814A

X
X

TeleManagement Forum 2007-2009

Page 12 of 15

MTNM Release Notes for Release 3.5

Document

Title

TMF513

TMF608

TMF814

SD1-40

TMF608 MDL Front Matter

SD1-41

Clarification of relationship
between a TPPool and its
TerminationPoints

SD1-42

Traffic Parameters

SD1-43

Programmatic Versioning

SD1-44

Connectionless Technology
Management

SD1-45

ASON Control Plane

Mangement-Primer

SD1-46

ASON Control Plane

Mangement-Scenarios

TMF814A

To better understand how these packages are actually delivered as a set of zip file the following
document provides details of the structure of the packages.
Error! Not a valid link.

RN312, Version 2.1

TeleManagement Forum 2007-2009

Page 13 of 15

MTNM Release Notes for Release 3.5

5B

9B

Administrative Appendix

Document History

Version History (This document)

Version Number

Date Modified

Modified by:

Description of
changes

0.1

Mar 2007

MTNM Team

Initial version

2.0

August 2008

MTNM Team

Updated to reflect Post

ME version

2.1

February 2009

Tina OSullivan

Minor corrections

Release Number

Date Modified

Modified by:

Description of changes

3.5

March 2007

MTNM Team

Initial version

Release History (MTNM Release)

10B

Contact
For requests of information or comments concerning this document please contact:

Stephen Fratini (mTOP Team Leader)

Telcordia Technologies
One Telcordia Drive
Room RRC-6Q161
Piscataway, NJ 08854
Phone: +1 732 962 1500
Email: sfratini@telcordia.com
HU

UH

Keith Dorking (MTNM Product Manager)

Ciena Corporation
1185 Sanctuary Parkway
Suite 300
Alpharetta, GA 30004
Phone: +1 678 687 5007
Email: kdorking@ciena.com
HU

RN312, Version 2.1

TeleManagement Forum 2007-2009

UH

Page 14 of 15

MTNM Release Notes for Release 3.5

11B

Acknowledgments
This document was prepared by the members of the TeleManagement Forum MTNM
Release 3.5 team.

12B

About TeleManagement Forum

TeleManagement Forum is an international consortium of communications service
providers and their suppliers. Its mission is to help service providers and network
operators automate their business processes in a cost- and time-effective way.
Specifically, the work of the TM Forum includes:
Establishing operational guidance on the shape of business
processes.
Agreeing on information that needs to flow from one process activity
to another.
Identifying a realistic systems environment
interconnection of operational support systems.

to

support

the

Enabling the development of a market and real products for

integrating and automating telecom operations processes.
The members of TM Forum include service providers, network operators and
suppliers of equipment and software to the communications industry. With that
combination of buyers and suppliers of operational support systems, TM Forum is
able to achieve results in a pragmatic way that leads to product offerings (from
member companies) as well as paper specifications.

RN312, Version 2.1

TeleManagement Forum 2007-2009

Page 15 of 15