Re: [Lime] Last Call: <draft-ietf-lime-yang-connectionless-oam-11.txt> (Generic YANG Data Model for Connectionless Operations, Administration, and Maintenance(OAM) protocols) to Proposed Standard

Benoit Claise <bclaise@cisco.com> Tue, 28 November 2017 07:36 UTC

Return-Path: <bclaise@cisco.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 DB391124B17; Mon, 27 Nov 2017 23:36:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.499
X-Spam-Level:
X-Spam-Status: No, score=-14.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 0HXNuSHyTh6v; Mon, 27 Nov 2017 23:36:39 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E9C5F1200E5; Mon, 27 Nov 2017 23:36:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7750; q=dns/txt; s=iport; t=1511854598; x=1513064198; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to; bh=6Fro7gb8eh228a0hIMji+sRiVIjHRUMeiMcV454I3+k=; b=MjcfhHXuT9j5QQBaRTZ+itHS3ouL7X1H1UbFIm+ujrxLCo9rCnjwq6sV 58CC/7JqmrP761nL76f6Y9rRQjAwrwtGx9dL0h3Hh1TaBMpsKs2VC0dHd CKuVnasD3sgyoN3NUlU4ZO6Io7wU+4K/myMpFv5liBL10bKmywXH/KCc6 E=;
X-IronPort-AV: E=Sophos;i="5.44,467,1505779200"; d="scan'208,217";a="521175"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 28 Nov 2017 07:36:36 +0000
Received: from [10.61.99.179] (dhcp-10-61-99-179.cisco.com [10.61.99.179]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id vAS7aZ1F003380; Tue, 28 Nov 2017 07:36:35 GMT
To: huubatwork@gmail.com, Greg Mirsky <gregimirsky@gmail.com>, Qin Wu <bill.wu@huawei.com>, "iesg@ietf.org" <iesg@ietf.org>
Cc: Carlos Pignataro <cpignata@cisco.com>, "ietf@ietf.org" <ietf@ietf.org>, Ron Bonica <rbonica@juniper.net>, "lime-chairs@ietf.org" <lime-chairs@ietf.org>, "lime@ietf.org" <lime@ietf.org>, "draft-ietf-lime-yang-connectionless-oam@ietf.org" <draft-ietf-lime-yang-connectionless-oam@ietf.org>
References: <150772925005.24695.3851410645764765123.idtracker@ietfa.amsl.com> <CA+RyBmVq9MnC97LuVRzhYiR+_dj0gQ2YRSp+b-223fjQXvhR_w@mail.gmail.com> <CA+RyBmXfB2fPn8GzaWYKwUJZhLwnKc_raO9ELf+8ANnAcED-vA@mail.gmail.com> <B8F9A780D330094D99AF023C5877DABA9AC0F246@nkgeml513-mbx.china.huawei.com> <CA+RyBmXhhxcrrhfB+ZT9A813_M35U4zuirWpt6YhM5rwGN09eQ@mail.gmail.com> <B8F9A780D330094D99AF023C5877DABA9AC15C2E@nkgeml513-mbx.china.huawei.com> <CA+RyBmV9vN-pzUjBNmDhYL7=E52w3NNDGk5OWGNnn1g1wrkrjA@mail.gmail.com> <B8F9A780D330094D99AF023C5877DABA9AC173CC@nkgeml513-mbx.china.huawei.com> <CA+RyBmXsE6WHEWBb4ReYN3O6ztNTFZ4nG-YOBvxjQvckxc=XHQ@mail.gmail.com> <499e8dc0-fcac-a3a9-e3ae-630691b70bc4@gmail.com>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <0888e2d6-f39f-1683-b174-5e3d19df1eae@cisco.com>
Date: Tue, 28 Nov 2017 08:36:35 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <499e8dc0-fcac-a3a9-e3ae-630691b70bc4@gmail.com>
Content-Type: multipart/alternative; boundary="------------EDF2D987899B3FF8EA00F902"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/lime/SNE4s5WwpfYLlRBkkQMFbfy0004>
X-Mailman-Approved-At: Tue, 28 Nov 2017 03:55:44 -0800
Subject: Re: [Lime] Last Call: <draft-ietf-lime-yang-connectionless-oam-11.txt> (Generic YANG Data Model for Connectionless Operations, Administration, and Maintenance(OAM) protocols) to Proposed Standard
X-BeenThere: lime@ietf.org
X-Mailman-Version: 2.1.22
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: Tue, 28 Nov 2017 07:36:41 -0000

Huub,

For your information, the document is now in the RFC editor queue, ready 
to be published.
https://datatracker.ietf.org/doc/draft-ietf-lime-yang-connectionless-oam/

Regards, Benoit
> Hello Greg,
>
> I agree with you that the current (version 18) text in section 3.3 is 
> very confusing.
>
> Authors:
>
> If I look at the definition of TP in section 2.2 I think a TP is similar
> to a maintenance point as defined for Ethernet. Am I correct?
>
> I don't understand why there are TPs with no neighboring TPs,
> where will their initiated OAM test be sent? Or where are OAM
> tests they react to initiated?
>
> It is IMHO also possible that there are TPs with a neighboring
> TP before AND a neighboring TP after the current TP.
>
> Please explain.
>
> Regards, Huub.
>
> ---------
>
>> Dear All,
>> I was under impression that that question of oam-neighboring-tps has 
>> been discussed and since authors couldn't produce technical rationale 
>> for this object we've agreed that it will be removed altogether from 
>> the grouping connectionless-oam-tps. But authors just changed name 
>> from level to position but had missed to synchronize descriptions in 
>> the model and in section 3.3. The later still refers to vertical layers:
>>                       "List of related neighboring test points in adjacent
>>                       layers up and down the stack for the same interface
>>                       that are related to the current test point.";
>> while the model insists that it is peering relationship:
>>          description
>>            "The relative position
>>             of neighboring test point
>>             corresponding to the current
>>             test point. Level 0 indicates no neighboring
>>             test points placed before or after the current
>>             test point in the same layer.-1 means there is
>>             a neighboring test point placed before the current
>>             test point in the same layer and +1 means there is
>>             a neighboring test point placed after the current
>>             test point in same layer.";
>> So, what is it? Perhaps it is time to remove list oam-neighboring-tps 
>> altogether also because having it s fixed size list is plain wrong. 
>> (Sorry for being so blunt but I commented too many times on the same 
>> to no avail from the authors).
>>
>> Regards,
>> Greg
>
>
> -- 
> ================================================================
> Always remember that you are unique...just like everyone else...
> .