Re: [Time] Fwd: New Liaison Statement, "Liaison to IETF on YANG Service OAM models"

"Romascanu, Dan (Dan)" <> Sun, 14 September 2014 14:33 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 42CBF1A03B5 for <>; Sun, 14 Sep 2014 07:33:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -8.551
X-Spam-Status: No, score=-8.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.652] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 7zhZX7w14tUw for <>; Sun, 14 Sep 2014 07:33:52 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 4FDA91A03CF for <>; Sun, 14 Sep 2014 07:33:52 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos; i="5.04,521,1406606400"; d="scan'208,217"; a="82389493"
Received: from unknown (HELO ([]) by with ESMTP; 14 Sep 2014 10:33:50 -0400
X-OutboundMail_SMTP: 1
Received: from unknown (HELO ([]) by with ESMTP/TLS/AES128-SHA; 14 Sep 2014 10:33:39 -0400
Received: from ([fe80::6db7:b0af:8480:c126]) by ([]) with mapi id 14.03.0174.001; Sun, 14 Sep 2014 16:33:37 +0200
From: "Romascanu, Dan (Dan)" <>
To: Qin Wu <>, Benoit Claise <>, "" <>
Thread-Topic: [Time] Fwd: New Liaison Statement, "Liaison to IETF on YANG Service OAM models"
Thread-Index: AQHPyz0w3Tz+hCcPY0ei/vkmJvN+mZv9DPwggAOtJ3A=
Date: Sun, 14 Sep 2014 14:33:37 +0000
Message-ID: <>
References: <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_9904FB1B0159DA42B0B887B7FA8119CA5C89AD33AZFFEXMB04globa_"
MIME-Version: 1.0
Subject: Re: [Time] Fwd: New Liaison Statement, "Liaison to IETF on YANG Service OAM models"
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Transport Independent OAM in Multi-Layer network Entity \(TIME\) discussion list." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sun, 14 Sep 2014 14:33:55 -0000


My opinion is that the IETF should be involved in the development of data models (using YANG or other Data Modeling Languages) only when these model IETF technologies (for example routing protocols). Data models (using YANG or other DMLs) that refer to technologies developed out of the IETF (like layer 2 protocols, or ITU-T OAM) should be developed by the respective organizations.

If Generic multi-layer OAM is defined by the IETF, a possible data model can be developed here.



From: Time [] On Behalf Of Qin Wu
Sent: Friday, September 12, 2014 9:27 AM
To: Benoit Claise;
Subject: Re: [Time] Fwd: New Liaison Statement, "Liaison to IETF on YANG Service OAM models"

Hi, Benoit:
My understanding to what MEF is doing regarding service OAM:


MEF_38 and MEF_39 are focus on Ethernet specific OAM Module development. They are not dealing with multi-layer OAM.

But MEF_38 and MEF_39 are two very good basis to define generic OAM Management Model, we should make an effort to refer to these documents rather than develop its own protocol.

In addition,

I don't think IETF should only provide YANG syntax and semantics for other SDOs to build various technology specific YANG Module,

IETF can also build various technology specific YANG Modules and technology independent YANG module (i.e., Generic OAM Management Model).

Let me know what you think about this?


发件人: Time [] 代表 Benoit Claise
发送时间: 2014年9月8日 16:16
主题: [Time] Fwd: New Liaison Statement, "Liaison to IETF on YANG Service OAM models"


Regards, Benoit

-------- Original Message --------

New Liaison Statement, "Liaison to IETF on YANG Service OAM models"


Wed, 20 Aug 2014 13:08:06 -0700


Liaison Statement Management Tool <><>


<Jürgen Schönwälder <><>, <>, Tom Nadeau <><>, <>>


Benoit Claise <><>, Joel Jaeggli <><>, "Nan Chen" <><>, Bill Bjorkman <><>, Raghu Ranganathan <><>, <><>, <><>, <><>, <><>, <><>, <><>, <><>

Title: Liaison to IETF on YANG Service OAM models

Submission Date: 2014-07-31

URL of the IETF Web page:

From: MEF (Mike Bencheck <><>)

To: NETCONF Data Modeling Language (Jürgen Schönwälder <><>, Tom Nadeau <><>)

Cc: Benoit Claise <><>,Joel Jaeggli <><>,Nan Chen <><>,Bill Bjorkman <><>,Raghu Ranganathan <><>,,,,,<,,,,>

Response Contact:<>,<>

Technical Contact:

Purpose: For information

Body: Dear Jürgen Schönwälder, Tom Nadeau, and Benoit Claise:

The MEF wants to communicate to the IETF NETCONF Data Modeling Language (netmod) Working Group that MEF has existing YANG Service OAM Fault Monitoring (MEF 38) and Service OAM Performance Monitoring (MEF 39) specifications.

MEF 38 and MEF 39 are published specifications and can be found on the MEF public website at:

There appears to be some direct overlap with these specifications and the goals of the Working Group, specifically in the area of MD, MA (MEG) and MEP definitions as found in

We request that IETF review and consider using these models, if applicable. We look forward to feedback from you on this subject.

The MEF Technical Committee meets next in Atlanta in October 27-29, 2014.


    Liaison to IETF on YANG Service OAM models