Re: [Lime] New Version Notification for draft-ietf-lime-yang-oam-model-07.txt

wangzitao <wangzitao@huawei.com> Fri, 08 July 2016 14:38 UTC

Return-Path: <wangzitao@huawei.com>
X-Original-To: lime@ietfa.amsl.com
Delivered-To: lime@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B316312D1A1 for <lime@ietfa.amsl.com>; Fri, 8 Jul 2016 07:38:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.647
X-Spam-Level:
X-Spam-Status: No, score=-5.647 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 XW3k4wbUrSFb for <lime@ietfa.amsl.com>; Fri, 8 Jul 2016 07:38:40 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A70A312D121 for <lime@ietf.org>; Fri, 8 Jul 2016 07:38:39 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml705-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CNJ06102; Fri, 08 Jul 2016 14:38:37 +0000 (GMT)
Received: from SZXEML427-HUB.china.huawei.com (10.82.67.182) by lhreml705-cah.china.huawei.com (10.201.5.168) with Microsoft SMTP Server (TLS) id 14.3.235.1; Fri, 8 Jul 2016 15:38:36 +0100
Received: from SZXEML501-MBX.china.huawei.com ([169.254.1.225]) by szxeml427-hub.china.huawei.com ([10.82.67.182]) with mapi id 14.03.0235.001; Fri, 8 Jul 2016 22:38:25 +0800
From: wangzitao <wangzitao@huawei.com>
To: "lime@ietf.org" <lime@ietf.org>, Deepak Kumar <dekumar@cisco.com>, Qin Wu <bill.wu@huawei.com>
Thread-Topic: New Version Notification for draft-ietf-lime-yang-oam-model-07.txt
Thread-Index: AQHR2SXuvdRWw6GKck6tYpIGlFbr6qAOmhVg
Date: Fri, 08 Jul 2016 14:38:24 +0000
Message-ID: <E6BC9BBCBCACC246846FC685F9FF41EAD52BF7@szxeml501-mbx.china.huawei.com>
References: <20160708143407.32095.72286.idtracker@ietfa.amsl.com>
In-Reply-To: <20160708143407.32095.72286.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.45.2.45]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090204.577FBAED.00AB, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.1.225, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 2ad7df040d1ba2d484243dafe630a52a
Archived-At: <https://mailarchive.ietf.org/arch/msg/lime/sVVQGQ4caAHqqEE2pp5Apj3qyIs>
Subject: Re: [Lime] New Version Notification for draft-ietf-lime-yang-oam-model-07.txt
X-BeenThere: lime@ietf.org
X-Mailman-Version: 2.1.17
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: Fri, 08 Jul 2016 14:38:43 -0000

Hi WG,

According to Email-list discussion, we prepare a version update. The main changes are:

# add a “MA-ID” choice/case node, which contains two case: one for MA-ID, one for MEG-ID;
# add a cc-enable leaf into MA and MEP list to indicate whether proactive CCs enabled
# remove the mep-direction, transmit-interval, and ttl from the MA list.
# remove the connectivity-context attribute from MEP list and Session list.
# remove the source-mep, enable, and ttl attribute from the session list.
# in rpc blocks, change MD-name-string & MA-name-string’s type to leafref. Therefore, it can be refer to the corresponding config leaves. 
# add the continuity-check and traceroute feature.
# add a defect-cleared notification.
# rewritten the defect-types (add a loss-of-continuity identity, modify remote-rdi to rdi, add some description about cross-connect-defect )
# update some text description to make it consistent and clear.

Please review it and let us know whether this version can address your questions.

Best Regards!
-Michael

-----邮件原件-----
发件人: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
发送时间: 2016年7月8日 22:34
收件人: Deepak Kumar; wangzitao; Qin Wu; wangzitao
主题: New Version Notification for draft-ietf-lime-yang-oam-model-07.txt


A new version of I-D, draft-ietf-lime-yang-oam-model-07.txt
has been successfully submitted by Michael Wang and posted to the IETF repository.

Name:		draft-ietf-lime-yang-oam-model
Revision:	07
Title:		Generic YANG Data Model for Connection Oriented Operations, Administration, and Maintenance(OAM) protocols
Document date:	2016-07-08
Group:		lime
Pages:		49
URL:            https://www.ietf.org/internet-drafts/draft-ietf-lime-yang-oam-model-07.txt
Status:         https://datatracker.ietf.org/doc/draft-ietf-lime-yang-oam-model/
Htmlized:       https://tools.ietf.org/html/draft-ietf-lime-yang-oam-model-07
Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-lime-yang-oam-model-07

Abstract:
   This document presents a base YANG Data model for connection oriented
   OAM protocols.  It provides a technology-independent abstraction of
   key OAM constructs for such protocols.  The model presented here can
   be extended to include technology specific details.  This guarantees
   uniformity in the management of OAM protocols and provides support
   for nested OAM workflows (i.e., performing OAM functions at different
   levels through a unified interface)

                                                                                  


Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat