Re: [nvo3] YANG models for OAM

Greg Mirsky <gregimirsky@gmail.com> Thu, 31 July 2014 23:48 UTC

Return-Path: <gregimirsky@gmail.com>
X-Original-To: l2vpn@ietfa.amsl.com
Delivered-To: l2vpn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C7EA1A0301; Thu, 31 Jul 2014 16:48:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ae6ZX4jkrm7a; Thu, 31 Jul 2014 16:48:38 -0700 (PDT)
Received: from mail-vc0-x236.google.com (mail-vc0-x236.google.com [IPv6:2607:f8b0:400c:c03::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 69A051A0080; Thu, 31 Jul 2014 16:48:37 -0700 (PDT)
Received: by mail-vc0-f182.google.com with SMTP id hy4so5583197vcb.13 for <multiple recipients>; Thu, 31 Jul 2014 16:48:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=sge4oNtRxrM8fZ+UfI5apucWM0vTaalAtmc/COBoa1k=; b=U5HLBDUknIvggfeW5Ff1XgKL3tsyanxURJ84l/E4SNdt5xscksiRIbAqrfc186l4PN 6FcJJtDek73yeXpwnWjmdAhcLOWr93dV9GxkK7h7/eW5cVAJiA7lJYrvCvymbW7u/K82 NLPal+hxgDyeSk1pjmigh9w7x95qW06u+T0URGbJzJi0c+AtLvI7z8KOVnjYGmVBGBqJ uYnsR5HBaNGp8VszbhkQjl1Rf9sj0df5sgJESMGUzJfus+EddKbTcrqbQMEJ1+bH5Ma6 5jJeXfRTRqvTJ/VFefYj3m/PJRSD6xLzHBI3mtXRaJdzr5B0bPpotlFyqtRRwTbeSzri S6hA==
MIME-Version: 1.0
X-Received: by 10.52.232.200 with SMTP id tq8mr1747682vdc.32.1406850516525; Thu, 31 Jul 2014 16:48:36 -0700 (PDT)
Received: by 10.220.15.136 with HTTP; Thu, 31 Jul 2014 16:48:36 -0700 (PDT)
In-Reply-To: <7DFA7869D33BD44A9A84BA24AD75BDE6D9E4645D@RCHEXMBP1.fnc.net.local>
References: <FBEA3E19AA24F847BA3AE74E2FE193562EE91CDA@xmb-rcd-x08.cisco.com> <CA+RyBmVyzyL5XQezXU+EaGLRGieDmzvgnkZVWqNGxB5b7jPZnQ@mail.gmail.com> <1406847186.16320.YahooMailNeo@web162805.mail.bf1.yahoo.com> <7DFA7869D33BD44A9A84BA24AD75BDE6D9E4645D@RCHEXMBP1.fnc.net.local>
Date: Thu, 31 Jul 2014 16:48:36 -0700
Message-ID: <CA+RyBmX9hjcANjfAEH_xeCud=7213tD5yLaNk70AeLkSXvpyMA@mail.gmail.com>
Subject: Re: [nvo3] YANG models for OAM
From: Greg Mirsky <gregimirsky@gmail.com>
To: "O'Connor, Don" <don.oconnor@us.fujitsu.com>
Content-Type: multipart/alternative; boundary=089e0122f5fa4a297104ff85e9c4
Archived-At: http://mailarchive.ietf.org/arch/msg/l2vpn/P-hYYgYqzr2HnB4qSxKzsxroSR8
Cc: "l2vpn@ietf.org" <l2vpn@ietf.org>, "netmod@ietf.org" <netmod@ietf.org>, "nvo3@ietf.org" <nvo3@ietf.org>, "trill@ietf.org" <trill@ietf.org>, "opsawg@ietf.org" <opsawg@ietf.org>
X-BeenThere: l2vpn@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Layer 2 Virtual Private Networks <l2vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l2vpn/>
List-Post: <mailto:l2vpn@ietf.org>
List-Help: <mailto:l2vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Jul 2014 23:48:40 -0000

Hi Don,
thank you for the reference. And I'd point that ITU SG15 is working on
standardizing "generic protocol-neutral management information model" for
transport network, including OAM. Hence my question, What is the scope of
these documents?

Regards,
Greg


On Thu, Jul 31, 2014 at 4:31 PM, O'Connor, Don <don.oconnor@us.fujitsu.com>
wrote:

>  Tissa, Greg, all
>
>
>
> Metro Ethernet Forum has already standardized Yang Modules for Ethernet
> Service OAM Performance Monitoring and Fault Management. Please see MEF 38
> and 39
>
>
>
> http://metroethernetforum.org/carrier-ethernet/technical-specifications
>
>
>
> Regards
>
>
>
> Don
>
>
>
> *From:* L2vpn [mailto:l2vpn-bounces@ietf.org] *On Behalf Of *Tissa
> Senevirathne
> *Sent:* Thursday, July 31, 2014 5:53 PM
> *To:* Greg Mirsky; Tissa Senevirathne (tsenevir)
>
> *Cc:* l2vpn@ietf.org; opsawg@ietf.org; nvo3@ietf.org; netmod@ietf.org;
> trill@ietf.org
> *Subject:* Re: [nvo3] YANG models for OAM
>
>
>
> Greg
>
>
>
> Yes it is, generic YANG model steup the base framework. It can be extended
> to add tools as well as other elements as well technology deviations.
> Alarms etc either be part of this document will be a separate document that
> specifies them. That is the reason we have designed the model as modular as
> possible and extensible as possible.
>
>
>
> Please let us know if any of the parts are not extensible or not modular
> enough.
>
>
>
> Thanks
>
> Tissa
>
>
>
> On Thursday, July 31, 2014 3:17 PM, Greg Mirsky <gregimirsky@gmail.com>
> wrote:
>
>
>
> Hi Tissa, authors, et. al,
>
> I've read documents and would like to clarify scope of these documents.
> OAM is not limited to ping and traceroute functions. It even not limited to
> continuity check. And in connectionless networks there would not be
> connectivity verification. And the performance measurement is the big part
> of OAM as well as protection coordination, defect alarms, and etc. Hence my
> question, is it in plans of the authors to address all of OAM in respective
> documents?
>
> Regards,
>
> Greg
>
>
>
> On Tue, Jun 10, 2014 at 12:03 PM, Tissa Senevirathne (tsenevir) <
> tsenevir@cisco.com> wrote:
>
> All
>
>
>
> We have published YANG model for OAM. #1 draft below place the generic
> framework for OAM, that can be augmented for different technologies. #2 and
> #3 are application of the concept to NVO3 and TRILL,
>
>
>
> 1.      http://datatracker.ietf.org/doc/draft-tissa-netmod-oam/
>
> 2.      http://datatracker.ietf.org/doc/draft-tissa-nvo3-yang-oam/
>
> 3.      http://datatracker.ietf.org/doc/draft-tissa-trill-yang-oam/
>
>
>
> Please review and share your comments
>
>
>
> Thanks
>
> Tissa
>
>
>
>
>
>
> _______________________________________________
> nvo3 mailing list
> nvo3@ietf.org
> https://www.ietf.org/mailman/listinfo/nvo3
>
>
>
>
>