IETF Logo Mail Archive

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

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 20 October 2017 19:28 UTC

Return-Path: <brian.e.carpenter@gmail.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 0045713431F; Fri, 20 Oct 2017 12:28:26 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 NZ1oOja53Dn6; Fri, 20 Oct 2017 12:28:25 -0700 (PDT)
Received: from mail-pf0-x229.google.com (mail-pf0-x229.google.com [IPv6:2607:f8b0:400e:c00::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 46FF2132F84; Fri, 20 Oct 2017 12:28:25 -0700 (PDT)
Received: by mail-pf0-x229.google.com with SMTP id e64so12385116pfk.9; Fri, 20 Oct 2017 12:28:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=u9f6raITG8J8M8vkQvIpw8wTdDrKhHlq6d+9r0cMiDQ=; b=W/z7V9+8I4/xpPWeJvu8TTjPrUFZwFw8bYBRf+J8sAKWfNiQwfF5BNIMaC/XC6l3fO pVBpJa+Sdu8enGhgiT3uzZYnOAyNqFhYXXV7P7CzkkyDP5iMIARYLSjjph9bB1DAt6Kk GOuOVzLs6oIn+ChQn4nLeF5X+lxeVHinsfLXlGCE4PnTWSRINnhKlLC6nXeD2yikHYPD Ky/vNLgk4TyMnvfuaS4utBAFyM4cxX8lO7A2g6PNDqvgcBw3B2Isqjdo7JKdzEGHrV3D YDlIXWFs8c4lGGlbGiDLH3p4TuN29ANXgdQMT8Nruff8Hjr4H5m6GAEKfAbKEoS9mn6e u5Sw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=u9f6raITG8J8M8vkQvIpw8wTdDrKhHlq6d+9r0cMiDQ=; b=RmOBKuOZmNE6jvE+L7jXxWZ/lj0WC+9DuxfmpRLO4pshegrNJT6sNU5JGKFvdETCKD q8rf25Q9dnyqtKttaL1gjWFvcGKrmBLk6ihtXgZH3XfRjV2l55Vx856lwlfklKmj+7o6 s3s2+s/vXL/3Pqp3zX7QYuIJx8j3xlAYSmjm+fbwhuakhipqSODNM7KZDmVCPoZ92znH JIn6qPjzUvN1Fez+dRIRx1GD3KJzX3S5RHrxgI6xs7OuOxRcFXmRr5Z8GdQPYf7rEXa0 Ayt8f/Qymqx1TCP0vWImM/AtS7Pdz42wz3wXPEHMayciK1BqFZ+eMvrTkYF0hNSAsniz kWdw==
X-Gm-Message-State: AMCzsaXGWrEuaaILpJMEyXXuK+70Ctqhgn4KbONQjF42FTY0qiIiPMyA IMe5BvoJxOLAGrt8CtCfG9w5EQ==
X-Google-Smtp-Source: ABhQp+TbUN/bKEN9e98+wsEs2NLAxjrnLlgx6MD3vaiyqrZ/mLf6tERrRhZXbTif/MSd0d4fxIr5DA==
X-Received: by 10.84.211.144 with SMTP id c16mr4965306pli.218.1508527704559; Fri, 20 Oct 2017 12:28:24 -0700 (PDT)
Received: from ?IPv6:2406:e007:6d3c:1:28cc:dc4c:9703:6781? ([2406:e007:6d3c:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id k11sm2945462pfh.134.2017.10.20.12.28.21 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 20 Oct 2017 12:28:23 -0700 (PDT)
To: Greg Mirsky <gregimirsky@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>, draft-ietf-lime-yang-connectionless-oam@ietf.org
Cc: Carlos Pignataro <cpignata@cisco.com>, lime-chairs@ietf.org, lime@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>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <6cae8b90-4ae5-4560-f316-5db684fed0a6@gmail.com>
Date: Sat, 21 Oct 2017 08:28:30 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <CA+RyBmXfB2fPn8GzaWYKwUJZhLwnKc_raO9ELf+8ANnAcED-vA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/lime/abXxMjjSrYGyI3sWbMmy-P_8Il4>
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: Fri, 20 Oct 2017 19:28:27 -0000

Greg,
On 21/10/2017 01:34, Greg Mirsky wrote:
...
> 
>       session-delay-statistics and session-jitter-statistics are too
> limiting in many dimensions - no support to reflect one-way (far-end
> and near-end) and round-trip measurements for the same test session,
> and too few metrics., e.g. no report of percentile.
> 
>       -
> 
>       session-delay-statistics does not reflect type of delay
> variation being calculated. As analyzed in RFC 5481, PDV and IPDV
> characterize different conditions (Section 5) and at least reflecting
> which one being calculated and reported is very informative.
> 

I had similar comments on draft-ietf-lime-yang-connectionless-oam-methods-09
in my Gen-ART review at
https://mailarchive.ietf.org/arch/msg/gen-art/qA38WYm5ookOePfnhqO4yM09cvc.
I haven't reviewed draft-ietf-lime-yang-connectionless-oam itself,
but it seems that the authors have chosen to leave quite a few things
under-defined, which bothers me from the interoperability viewpoint.
Presumably the existing implementations have taken specific decisions
on these points, which could be documented, even as default recommendations?

Regards
     Brian

v2.23.0 | Report a Bug | By Email