IETF Logo Mail Archive

Re: [nvo3] YANG models for OAM

Greg Mirsky <gregimirsky@gmail.com> Fri, 01 August 2014 01:42 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 0C9021A0358; Thu, 31 Jul 2014 18:42:30 -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 loqNCqhYCug8; Thu, 31 Jul 2014 18:42:28 -0700 (PDT)
Received: from mail-vc0-x231.google.com (mail-vc0-x231.google.com [IPv6:2607:f8b0:400c:c03::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 821701A035F; Thu, 31 Jul 2014 18:42:27 -0700 (PDT)
Received: by mail-vc0-f177.google.com with SMTP id hy4so5522852vcb.22 for <multiple recipients>; Thu, 31 Jul 2014 18:42:26 -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=lRR2kV8rhMHbMTe93Q6AG6IuR2LmqzC8cOYPUx5AKQc=; b=hF/leVOF2JZIQz9gMQDIHAFVyXRlKsj7dtogxSaXiH8Vl1aOChuRBvThe5DQWutmpW xysigIINz547WS0FDfwOnBgetYTPiwJMO4QagpFKmusDHz1GIBflOqsN1eex9pg6yk8P +Y905XCt3bP8tjo3parBP/WUxQ3sSgt/7u2cSvpV9cdwY2lyClxGgVJipM4UV6RU7hFY h+GflgNnYPdst5l6YmCIwqh3k2xJepj5jMMl7dmHNYm4trwxHNcAg8YxpOlv73LUO4Xy G0j8Tpb0M/F99u6Tp+VCHRWoGdOAKmWd14Y6Egp4EOigi98izBScmb9fuLYjvR27Bq/5 zCcA==
MIME-Version: 1.0
X-Received: by 10.220.116.196 with SMTP id n4mr2752633vcq.6.1406857346700; Thu, 31 Jul 2014 18:42:26 -0700 (PDT)
Received: by 10.220.15.136 with HTTP; Thu, 31 Jul 2014 18:42:26 -0700 (PDT)
In-Reply-To: <1406847186.16320.YahooMailNeo@web162805.mail.bf1.yahoo.com>
References: <FBEA3E19AA24F847BA3AE74E2FE193562EE91CDA@xmb-rcd-x08.cisco.com> <CA+RyBmVyzyL5XQezXU+EaGLRGieDmzvgnkZVWqNGxB5b7jPZnQ@mail.gmail.com> <1406847186.16320.YahooMailNeo@web162805.mail.bf1.yahoo.com>
Date: Thu, 31 Jul 2014 18:42:26 -0700
Message-ID: <CA+RyBmWyySdwbjoSoWyO443bjrGdJtokH91OS+pw0nGpPDO7cw@mail.gmail.com>
Subject: Re: [nvo3] YANG models for OAM
From: Greg Mirsky <gregimirsky@gmail.com>
To: Tissa Senevirathne <tissasenevirathne@yahoo.com>
Content-Type: multipart/alternative; boundary=047d7b34354c665c7504ff87809e
Archived-At: http://mailarchive.ietf.org/arch/msg/l2vpn/RktkAAT5R_bs5MgHSDiwkCp6nMc
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: Fri, 01 Aug 2014 01:42:30 -0000

Hi Tissa,
I feel that clear definition of the scope of work is important. From
reading the documents, my impression, is that on-demand OAM tools that
support detection and localization of Loss of Continuity defect are in
scope while the rest of OAM is for further study. I think that it would
benefit the documents and discussion if scope be firmly set.

Regards,
Greg


On Thu, Jul 31, 2014 at 3:53 PM, Tissa Senevirathne <
tissasenevirathne@yahoo.com> wrote:

> 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
>
>
>
>
>

v2.8.7 | Report a Bug | By Email