Re: [Lime-oam-model] OAM Model analisys. First cut

Tom Taylor <> Wed, 04 February 2015 21:12 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 0C6B51A88D4 for <>; Wed, 4 Feb 2015 13:12:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ll1SlL9pZHxW for <>; Wed, 4 Feb 2015 13:12:56 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:4001:c05::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id CAA7B1A88CB for <>; Wed, 4 Feb 2015 13:12:26 -0800 (PST)
Received: by with SMTP id h15so21531655igd.4 for <>; Wed, 04 Feb 2015 13:12:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=SI56DIiqW9R1MvzhNHXBpJRKSF56eYmTp4nk5XQWm9Q=; b=OYOdmIPbrCjK1c3CnodyEIxg7NbUOzgTmd7IE0A6AuXz9qpAOUWXfPFYHZNjJNUEQg FQtucJ2kDqopjuyAKJ8Za92ZJb3/AXxWyFYLu4hrsJeHbEBMVPH3qhrNO6SfhDmwbuGz BnNWO8+E8GF6fBAk/zVrOu978OFYzgV8uSR5jHNiHui46b2dqscjcffOmIzsByq35daJ dAlDt9N2S2irzSoIkbngQ26AodcZVKAM97Xduba5c2ivew3+pEFY4BCT3NXp0x+tsffa YlICmg0vhqZO9SpFjP8L456304Kw0BIKojSjHh/3H9y8yHDZcgON1/LFv9to/m8BT+yQ gKnA==
X-Received: by with SMTP id zg4mr3869902icb.69.1423084345991; Wed, 04 Feb 2015 13:12:25 -0800 (PST)
Received: from [] ( []) by with ESMTPSA id t1sm10046133igs.0.2015. (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 04 Feb 2015 13:12:25 -0800 (PST)
Message-ID: <>
Date: Wed, 04 Feb 2015 16:12:21 -0500
From: Tom Taylor <>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Gregory Mirsky <>, Qin Wu <>, "" <>
References: <> <> <>
In-Reply-To: <>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <>
Subject: Re: [Lime-oam-model] OAM Model analisys. First cut
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: LIME WG OAM Model Design Team <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 04 Feb 2015 21:12:58 -0000

Thanks for your work, Greg. I'll get into this discussion later today 
(which amounts to tomorrow your time). I have some other work in hand at 
the moment.


On 04/02/2015 2:54 PM, Gregory Mirsky wrote:
> Hi Qin,
> I believe that LIME charter is not to develop new OAM tools but to work on OAM data model that is relevant to all or some OAM models. If some OAM models do not have some of functions we find in other models, then we can flag that and discuss but in other group. The table you find in my writing is only start of what OAM model analysis may look like. I’d like the team to review it and help with comments and suggestions to extend the table. Then we can come to informed decision on what is common among IETF OAM models and discuss how useful data model of that common set may be.
>                  Regards,
>                                  Greg
> From: Qin Wu []
> Sent: Tuesday, February 03, 2015 6:03 PM
> To: Gregory Mirsky;
> Subject: RE: OAM Model analisys. First cut
> Greg:
> What conclusion do you make from this analysis? Do you want to make BDI and FDI being supported as common OAM function? Or do you want to make linktrace and loop back layer independent? Aren’t linktrace and loopback Ethernet specific functions?
> I think the example you give in the table 1 gets complete alignment with the Table 4 in the section 5.2 of RFC7276.
> [cid:image001.jpg@01D04071.5BF724F0]
> That is to say Continuity Check, Connectivity Verification, Path Discovery, Performance measurement are common OAM functions for the all the OAM technologies.
> Besides Common OAM functions, we also have fault domain, test point, addressing, technology type, sub technology type, specific layer. They are all common things
> for all the OAM technologies.
> Regards!
> -Qin
> 发件人: Lime-oam-model [] 代表 Gregory Mirsky
> 发送时间: 2015年2月4日 9:22
> 收件人:<>
> 主题: [Lime-oam-model] OAM Model analisys. First cut
> Dear All,
> apologies for belated update. Attached please find first cut of the proposal for approach to OAM Model comparison and example of it being used.
> Your questions, comments, suggestions always welcome and greatly appreciated.
>                  Regards,
>                                  Greg
> _______________________________________________
> Lime-oam-model mailing list