Re: [Lime] Call for Adoption: draft-tissa-lime-yang-oam-model-06

"Varma, Eve L (Eve)" <eve.varma@alcatel-lucent.com> Mon, 24 August 2015 23:19 UTC

Return-Path: <eve.varma@alcatel-lucent.com>
X-Original-To: lime@ietfa.amsl.com
Delivered-To: lime@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD2601B2B82 for <lime@ietfa.amsl.com>; Mon, 24 Aug 2015 16:19:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.909
X-Spam-Level:
X-Spam-Status: No, score=-6.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] 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 VnUTXRcjJxSz for <lime@ietfa.amsl.com>; Mon, 24 Aug 2015 16:19:33 -0700 (PDT)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 261DB1B2B0A for <lime@ietf.org>; Mon, 24 Aug 2015 16:19:33 -0700 (PDT)
Received: from us70uusmtp4.zam.alcatel-lucent.com (unknown [135.5.2.66]) by Websense Email Security Gateway with ESMTPS id 593EB9F9CDA6A; Mon, 24 Aug 2015 23:19:25 +0000 (GMT)
Received: from US70UWXCHHUB01.zam.alcatel-lucent.com (us70uwxchhub01.zam.alcatel-lucent.com [135.5.2.48]) by us70uusmtp4.zam.alcatel-lucent.com (GMO) with ESMTP id t7ONJSl9026410 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 24 Aug 2015 23:19:28 GMT
Received: from US70UWXCHMBA03.zam.alcatel-lucent.com ([169.254.9.242]) by US70UWXCHHUB01.zam.alcatel-lucent.com ([135.5.2.48]) with mapi id 14.03.0195.001; Mon, 24 Aug 2015 19:19:28 -0400
From: "Varma, Eve L (Eve)" <eve.varma@alcatel-lucent.com>
To: Gregory Mirsky <gregory.mirsky@ericsson.com>, "Carlos Pignataro (cpignata)" <cpignata@cisco.com>, "lime@ietf.org" <lime@ietf.org>
Thread-Topic: Call for Adoption: draft-tissa-lime-yang-oam-model-06
Thread-Index: AQHQ0hZtXgg3DXSRsEGgq7M9c/wmVZ4WtZRwgAUszsA=
Date: Mon, 24 Aug 2015 23:19:28 +0000
Message-ID: <6D32668528F93D449A073F45707153D8BEB9DDB9@US70UWXCHMBA03.zam.alcatel-lucent.com>
References: <8E812CBB-1058-40C0-815F-CF8C008F0582@cisco.com> <7347100B5761DC41A166AC17F22DF112218ABD6B@eusaamb103.ericsson.se>
In-Reply-To: <7347100B5761DC41A166AC17F22DF112218ABD6B@eusaamb103.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.5.27.16]
Content-Type: multipart/alternative; boundary="_000_6D32668528F93D449A073F45707153D8BEB9DDB9US70UWXCHMBA03z_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/lime/Sx59adqh_XFQ1ZhM1Z0u1z-7858>
Cc: "draft-tissa-lime-yang-oam-model@tools.ietf.org" <draft-tissa-lime-yang-oam-model@tools.ietf.org>
Subject: Re: [Lime] Call for Adoption: draft-tissa-lime-yang-oam-model-06
X-BeenThere: lime@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Layer Independent OAM Management in Multi-Layer Environment \(LIME\) discussion list." <lime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lime>, <mailto:lime-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lime/>
List-Post: <mailto:lime@ietf.org>
List-Help: <mailto:lime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lime>, <mailto:lime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Aug 2015 23:19:36 -0000

I concur with Greg's concerns.

Best regards,
Eve

From: Lime [mailto:lime-bounces@ietf.org] On Behalf Of Gregory Mirsky
Sent: Friday, August 21, 2015 12:33 PM
To: Carlos Pignataro (cpignata); lime@ietf.org
Cc: draft-tissa-lime-yang-oam-model@tools.ietf.org
Subject: Re: [Lime] Call for Adoption: draft-tissa-lime-yang-oam-model-06

I do not support adoption of this document as WG item.

I believe that until Applicability of Generic YANG Data Model for layer Independent OAM Management demonstrates that the proposed model indeed is common among OAM technologies developed at IETF, e.g. IP, IP/MPLS, MPLS-TP, and TRILL, beyond just YANG customization mechanisms adopting this draft as WG item is premature. And the applicability document has not demonstrated that yet as you can see from the attached comments to the  Applicability of the draft-tissa-lime-yang-oam-model and couple more generic notes:

  *   Operations, Administration and Maintenance address Fault Management and Performance Monitoring of the FCAPS. If the scope of the document does not include both then I suggest not to refer to is as OAM but perhaps On-demand Continuity Check and Connectivity Verification, i.e. ping and traceroute, Common YANG model;
  *   section 4 is more about general YANG extensibility than of the proposed OAM YANG data model;
  *   IP/MPLS OAM not being separated from MPLS-TP OAM;
  *   Performance Monitoring arbitrary being left outside the scope for some technologies, e.g. Ethernet;
  *   often Service OAM being presented as Transport OAM, e.g. VPLS, NVO3.


Regards,
        Greg

From: Lime [mailto:lime-bounces@ietf.org] On Behalf Of Carlos Pignataro (cpignata)
Sent: Saturday, August 08, 2015 1:12 PM
To: lime@ietf.org<mailto:lime@ietf.org>
Cc: draft-tissa-lime-yang-oam-model@tools.ietf.org<mailto:draft-tissa-lime-yang-oam-model@tools.ietf.org>
Subject: [Lime] Call for Adoption: draft-tissa-lime-yang-oam-model-06

LIME,

This email starts a two-week poll on adopting draft-tissa-lime-yang-oam-model-06 [1] as a LIME working group item.

Please send comments to the list and state if you support adoption or not (in the later case, please also state the reasons).

This poll runs until ** August 24th, 2015 **.

We are also polling for knowledge of any IPR that applies to this draft, to ensure that IPR has been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details).

*If you are listed as a document author or contributor*, please respond to this email and indicate whether or not you are aware of any relevant IPR.

The draft will not be adopted until a response has been received from each author and contributor.

If you are not listed as an author or contributor, then please explicitly respond only if you are aware of any IPR that has not yet been disclosed in conformance with IETF rules.

Thank you,

Ron Bonica / Carlos Pignataro
LIME co-chairs

[1] http://datatracker.ietf.org/doc/draft-tissa-lime-yang-oam-model/