Subject: [Time] Introduction to TIME Mailing List

From: Qin Wu <[email-masked]>
Date: Tue, 10 Jun 2014 06:48:10 +0000

Dear all,

This is to introduce the TIME mailing list. TIME stands for "Transport Independent OAM in Multi-Layer Network Entity" .

This mailing list is newly created as a result of a BOF request proposal to OPS Area recently. Here is an initial description of the problem in

https://datatracker.ietf.org/doc/draft-ww-opsawg-multi-layer-oam-00
and we are looking for discussion and feedback on this list, as well as expecting to hammer out a concrete scope and get the first version of draft
charter coming out through this discussion .

Background:

  The basic concepts of Operations, Administration, and Maintenance (OAM) and the
   functional roles in monitoring and diagnosing the behavior of telecommunications networks
   have been long term studied at the Layer 1&2 & Layer 3 levels.  The current practice is that
   many technologies and layers have their own OAM protocols.   There is little or no
   re-use of software and hardware for each existing OAM protocol. Vendors and operators waste
a lot through the whole OAM life-cycle when a new technology is introduced. Integration of OAM
across multiple technologies is extremely difficult. When having networks with more than one technology,
maintenance and troubleshooting are done per technology
   and layer, operation process can be very cumbersome. In many cases it is desirable to have a
   generic OAM to cover heterogeneous networking technologies. Generic OAM tools should be
   deployed over various encapsulating protocols, and in various medium types.

   An example of an environment in which a generic and integrated OAM protocol would be
   valuable is Service Function Chaining. A Service Function Chaining is composed by a series of
   service Functions, that can act in different layers but providing an end-to-end chain or path
   from a source to destination in a given order.  In service function chaining Environment, it is
   necessary to provide end to end OAM across certain or all entities and involving many layers.
   OAM information should be exchanged between service functions in different layers while
   using various encapsulating protocols.  In some cases OAM should cross different
   administration and/or maintenance domains.

The purpose of the list:

   1.understanding and discussing the times when an OAM
   protocol can be tuned and optimised for a specific data plane (for example, OAM in a packet
   network can be very different from OAM in a circuit switched network because of the
   different characteristics of the network)

2.and seeking the best ways:

        O Exchange OAM information at the service layer atop of layer 3

O Abstract OAM information common to different layer

O Provide them via unified interface to management entities.

O Set up Maintenance Domains (MD) and Maintenance Intermediate Points (MIP)

O Enable OAM function at different layer in the multi-layer network

O Activate OAM function a different layer and provide results to management entity

This mailing list is intended to enable discussion of the architecture, use-cases/applicability, and
requirements that provide generic and integrated OAM covering various heterogeneous network technologies.

O Analyse and understand the different motivations and opportunities for optimisation of OAM in different
technology networks, and the trade-offs between those optimisations and the
 overall advantage of a generic OAM mechanism.

O Set out the problem statement and architecture for the
     Transport Independent OAM in the multi-layer network and outlines the problems
     encountered with existing OAM protocol variety and their impact on introduction of new technologies.

You can subscribe to the list at: https://www.ietf.org/mailman/listinfo/time.

To post a message to all the list members, send email to time at ietf.org.

Best Regards,

Qin&Dan