IETF Logo Mail Archive

Re: [Rtg-ooam-dt] Generic YANG Data Model for Connection Less Operations, Administration, and Maintenance(OAM) protocols

David Mozes <davidm@mellanox.com> Sun, 05 June 2016 15:38 UTC

Return-Path: <davidm@mellanox.com>
X-Original-To: rtg-ooam-dt@ietfa.amsl.com
Delivered-To: rtg-ooam-dt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A1E612B00B for <rtg-ooam-dt@ietfa.amsl.com>; Sun, 5 Jun 2016 08:38:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.101
X-Spam-Level:
X-Spam-Status: No, score=-0.101 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mellanox.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 6Kd4ZxDjSs8Y for <rtg-ooam-dt@ietfa.amsl.com>; Sun, 5 Jun 2016 08:38:02 -0700 (PDT)
Received: from emea01-am1-obe.outbound.protection.outlook.com (mail-am1on0647.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe00::647]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3B928128E18 for <rtg-ooam-dt@ietf.org>; Sun, 5 Jun 2016 08:38:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Mellanox.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=O9SFcEbBRo//Aa1TjoVRoi8NJgi8cWvpgsMQ5Z9wecg=; b=mNphxi1oVgN5Y/3Mrcb9l7yMVcYe2XT/Kp5y20qIyhIlNUK6vyHAFl78umlgyw7N5Yg4DX3ldqnui4u0Nliy9yLj4MEdFyPQfJsOOaDF5K4aw+6pgYY5G6I63X/b92s0Q9nS2o6NVQFptWxWqU/zxCk+1TkC28yhwepYK5jlNlQ=
Received: from VI1PR05MB1456.eurprd05.prod.outlook.com (10.164.85.26) by VI1PR05MB1456.eurprd05.prod.outlook.com (10.164.85.26) with Microsoft SMTP Server (TLS) id 15.1.506.9; Sun, 5 Jun 2016 15:34:35 +0000
Received: from VI1PR05MB1456.eurprd05.prod.outlook.com ([10.164.85.26]) by VI1PR05MB1456.eurprd05.prod.outlook.com ([10.164.85.26]) with mapi id 15.01.0506.014; Sun, 5 Jun 2016 15:34:35 +0000
From: David Mozes <davidm@mellanox.com>
To: "Deepak Kumar (dekumar)" <dekumar@cisco.com>
Thread-Topic: Generic YANG Data Model for Connection Less Operations, Administration, and Maintenance(OAM) protocols
Thread-Index: AdG7SptOzv4AE+4IRpmvSb3idfZdDAAknLwAANcZGWAAAQJuGAAAdasQ
Date: Sun, 05 Jun 2016 15:34:35 +0000
Message-ID: <VI1PR05MB14565267780A002F4006808AB65B0@VI1PR05MB1456.eurprd05.prod.outlook.com>
References: <7347100B5761DC41A166AC17F22DF11221A938B9@eusaamb103.ericsson.se> <VI1PR05MB1456048B0D45F0964F53E9B0B6470@VI1PR05MB1456.eurprd05.prod.outlook.com>, <VI1PR05MB1456147DF3B49327189F87C5B65B0@VI1PR05MB1456.eurprd05.prod.outlook.com> <C5C82091-72DB-4715-B727-BFD591D463B9@cisco.com>
In-Reply-To: <C5C82091-72DB-4715-B727-BFD591D463B9@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: cisco.com; dkim=none (message not signed) header.d=none;cisco.com; dmarc=none action=none header.from=mellanox.com;
x-originating-ip: [193.47.165.251]
x-ms-office365-filtering-correlation-id: bd42364b-c04f-4bf8-07f3-08d38d56e5f3
x-microsoft-exchange-diagnostics: 1; VI1PR05MB1456; 5:JpyD1vYkXKw2jdIrtC93R22XfTtDoOz3fSO2CVEL9OuK5o7KXgzz+EJxxKSh6Oyaq8yn24s8/UoAU88odaJLOetjuPsn8EZi6HiGrmOuN5nt8QL2RNpmWhkP/raVrqu9jmZOUmE8hYj86apjPfuD+Q==; 24:uWDsK5WclozXCDclUVYq9MQWmHDv93wd9/+GhIxcBUcOQlzgDKd1I9PJt6tA8GNC3Zkdnfk+5ig2NGBP6I4a15vyDEMshGl08yta3MP69cM=; 7:fMqg0m/qB+XdE6/Q4FVsuA+1f+x/InUtCWVgWuu7v6kN4edAMiP4ffs97cUnN77O7iTiDGcD+NCNy4wndw37DJ/DQ9bKaYigxH/YgJLQaFgphBCAXLRQMyw7LXAKO0so8akHBW+Op1hWjs6yOQZDh44SSOEMtpSLNzQCAVBA3z+jCyHOj7nH3Hx7XM9v4LEOXZPxfzsvYo9JCoIKdOOrNv9HWGwtirpaKBChexRgwXw=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:VI1PR05MB1456;
x-microsoft-antispam-prvs: <VI1PR05MB1456FFB8E30AFF27AF0DB31CB65B0@VI1PR05MB1456.eurprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(37575265505322)(120809045254105)(95692535739014)(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046)(6055026); SRVR:VI1PR05MB1456; BCL:0; PCL:0; RULEID:; SRVR:VI1PR05MB1456;
x-forefront-prvs: 09645BAC66
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(52044002)(24454002)(377454003)(66066001)(76576001)(8936002)(93886004)(77096005)(86362001)(9686002)(2950100001)(74316001)(4326007)(5008740100001)(81166006)(6116002)(586003)(19625215002)(2900100001)(102836003)(5002640100001)(8676002)(790700001)(3846002)(19300405004)(33656002)(5003600100002)(15975445007)(5003630100001)(2906002)(5004730100002)(122556002)(10400500002)(11100500001)(19617315012)(19609705001)(92566002)(3660700001)(16236675004)(3280700002)(50986999)(87936001)(110136002)(189998001)(54356999)(76176999)(19580395003)(19580405001)(41533002); DIR:OUT; SFP:1101; SCL:1; SRVR:VI1PR05MB1456; H:VI1PR05MB1456.eurprd05.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en;
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_VI1PR05MB14565267780A002F4006808AB65B0VI1PR05MB1456eurp_"
MIME-Version: 1.0
X-OriginatorOrg: Mellanox.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Jun 2016 15:34:35.1641 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: a652971c-7d2e-4d9b-a6a4-d149256f461b
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR05MB1456
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-ooam-dt/A9udm9VcdZXQjli1GN_OLreSMB0>
Cc: "rtg-ooam-dt@ietf.org" <rtg-ooam-dt@ietf.org>
Subject: Re: [Rtg-ooam-dt] Generic YANG Data Model for Connection Less Operations, Administration, and Maintenance(OAM) protocols
X-BeenThere: rtg-ooam-dt@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: List is used by the Routing Area Overlay OAM Design team for internal coordination and discussion <rtg-ooam-dt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-ooam-dt>, <mailto:rtg-ooam-dt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-ooam-dt/>
List-Post: <mailto:rtg-ooam-dt@ietf.org>
List-Help: <mailto:rtg-ooam-dt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-ooam-dt>, <mailto:rtg-ooam-dt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 05 Jun 2016 15:38:04 -0000

Hi ,
Thx Deepak ,
There are as ecial TLV defined  ?
Is it should be done in the data path  ?


Thx
David


From: Deepak Kumar (dekumar) [mailto:dekumar@cisco.com]
Sent: Sunday, June 05, 2016 6:18 PM
To: David Mozes <davidm@mellanox.com>
Cc: rtg-ooam-dt@ietf.org
Subject: Re: Generic YANG Data Model for Connection Less Operations, Administration, and Maintenance(OAM) protocols

Hi,

Inline +++DK:

Sent from my iPhone

On Jun 5, 2016, at 7:51 AM, David Mozes <davidm@mellanox.com<mailto:davidm@mellanox.com>> wrote:
Hi Deepak ,
I saw you are the main contributor on thus draft  .
Can you share more details  ?
See my q below

Thx
David

From: Rtg-ooam-dt [mailto:rtg-ooam-dt-bounces@ietf.org] On Behalf Of David Mozes
Sent: Wednesday, June 01, 2016 11:42 AM
To: Gregory Mirsky <gregory.mirsky@ericsson.com<mailto:gregory.mirsky@ericsson.com>>; rtg-ooam-dt@ietf.org<mailto:rtg-ooam-dt@ietf.org>
Subject: Re: [Rtg-ooam-dt] Generic YANG Data Model for Connection Less Operations, Administration, and Maintenance(OAM) protocols

Hi  * ,
Look into it  have some  beginning quotations for start  discussions

3.3.2.  Path Packet Counters

   Path-packet-counters feature is part of the passive OAM feature set,
   where the meta-data carried is to be interpreted by the passive OAM
   domain's encapsulating and decapsulating nodes.  Sequence numbers are
   the main meta-data added and can be used to detect packet loss,
   packet reordering or packet duplication.

David> Can we have more details on that :
- What is the mechanism ?
- what is the packet format  ?

+++DK:
It's real data traffic determined by configured policy matching traffic.


3.3.3 Proof of Transit

   Proof of transit feature is part of the passive OAM feature set,
   where the path or the service chain is verified.  Service or path
   verification uses methods like nested hashing or nested encryption of
   the meta-data.  By definition of a service chain or a path, some of
   the nodes in the domain participate and some do not.

David> the same  ?

 +++DK:

It's real data traffic determined by policy matching the traffic.

Thanks
Deepak

Thx
David



From: Rtg-ooam-dt [mailto:rtg-ooam-dt-bounces@ietf.org] On Behalf Of Gregory Mirsky
Sent: Tuesday, May 31, 2016 5:45 PM
To: rtg-ooam-dt@ietf.org<mailto:rtg-ooam-dt@ietf.org>
Subject: [Rtg-ooam-dt] Generic YANG Data Model for Connection Less Operations, Administration, and Maintenance(OAM) protocols

Dear All,
I found that part on "passive OAM" in the latest version of the draft Generic YANG Data Model for Connection Less Operations, Administration, and Maintenance(OAM) protocols<https://datatracker.ietf.org/doc/draft-kumar-lime-yang-connectionless-oam/?include_text=1> is, in my opinion, about the telemetry collection. Would appreciate your reviews, comments. Feel free to share on LIME WG list as well.

                Regards,
                                Greg
_______________________________________________
Rtg-ooam-dt mailing list
Rtg-ooam-dt@ietf.org<mailto:Rtg-ooam-dt@ietf.org>
https://www.ietf.org/mailman/listinfo/rtg-ooam-dt

v2.23.0 | Report a Bug | By Email