Re: [Rtg-ooam-dt] O-OAM Requirements
"Nagendra Kumar Nainar (naikumar)" <naikumar@cisco.com> Thu, 24 December 2015 13:06 UTC
Return-Path: <naikumar@cisco.com>
X-Original-To: rtg-ooam-dt@ietfa.amsl.com
Delivered-To: rtg-ooam-dt@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1])
by ietfa.amsl.com (Postfix) with ESMTP id 8B8341A9139
for <rtg-ooam-dt@ietfa.amsl.com>; Thu, 24 Dec 2015 05:06:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 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, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5]
autolearn=ham
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 6rwdik1V-F5E for <rtg-ooam-dt@ietfa.amsl.com>;
Thu, 24 Dec 2015 05:06:24 -0800 (PST)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95])
(using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id 7C2DC1A9138
for <rtg-ooam-dt@ietf.org>; Thu, 24 Dec 2015 05:06:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;
d=cisco.com; i=@cisco.com; l=7042; q=dns/txt; s=iport;
t=1450962384; x=1452171984;
h=from:to:cc:subject:date:message-id:mime-version;
bh=i4e0HvdgQbEYTh7y0MnFljeJdheARlu5pEuyIYh21jY=;
b=HfW6cw6ADgZcqPsR2NHh7rG6hzow+7Ixo4R5FG33/xUHkwPBSygVxW23
FqjSteVeOkv+xAajuBOF8PlXtkC2EKS69al1BxafnBFihzUlGH6rdzAlG
+eMi1EajJQ9tyUg0vlDK2uV1hZBs5DqebZ/XDIKVhB3tX+EHDIGatPa1R c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ARAgAQ7XtW/4MNJK1egm5MUm0GiFO0c?=
=?us-ascii?q?QENgWSGD4EfOBQBAQEBAQEBgQqENAECBC1MEgEIEQMBAigoERQJCgQBDQWIGgM?=
=?us-ascii?q?SvQkNg3UBAQEBAQEBAQEBAQEBAQEBAQEBAQEYi1WCT4IohEYFjXKJEwGLEkOBe?=
=?us-ascii?q?IFcFodWhTGGYYNmg3MBIAEBQoQLcoRDgQgBAQE?=
X-IronPort-AV: E=Sophos;i="5.20,474,1444694400";
d="scan'208,217";a="221256092"
Received: from alln-core-1.cisco.com ([173.36.13.131])
by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA;
24 Dec 2015 13:06:23 +0000
Received: from XCH-RCD-015.cisco.com (xch-rcd-015.cisco.com [173.37.102.25])
by alln-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id tBOD6NAn013615
(version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL);
Thu, 24 Dec 2015 13:06:23 GMT
Received: from xch-rcd-015.cisco.com (173.37.102.25) by XCH-RCD-015.cisco.com
(173.37.102.25) with Microsoft SMTP Server (TLS) id 15.0.1104.5;
Thu, 24 Dec 2015 07:06:22 -0600
Received: from xch-rcd-015.cisco.com ([173.37.102.25]) by
XCH-RCD-015.cisco.com ([173.37.102.25]) with mapi id 15.00.1104.009; Thu, 24
Dec 2015 07:06:22 -0600
From: "Nagendra Kumar Nainar (naikumar)" <naikumar@cisco.com>
To: Gregory Mirsky <gregory.mirsky@ericsson.com>, "rtg-ooam-dt@ietf.org"
<rtg-ooam-dt@ietf.org>
Thread-Topic: [Rtg-ooam-dt] O-OAM Requirements
Thread-Index: AQHRPkvjJ+k9zTW3h0a6gOsGVKRsAQ==
Date: Thu, 24 Dec 2015 13:06:22 +0000
Message-ID: <D2A0E1EE.CAFD4%naikumar@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.5.7.151005
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.82.233.129]
Content-Type: multipart/alternative;
boundary="_000_D2A0E1EECAFD4naikumarciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtg-ooam-dt/S5hmLbfBCvey4IwiBOiAD4t89iE>
Cc: "Alia Atlas \(akatlas@gmail.com\)" <akatlas@gmail.com>
Subject: Re: [Rtg-ooam-dt] O-OAM Requirements
X-BeenThere: rtg-ooam-dt@ietf.org
X-Mailman-Version: 2.1.15
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: Thu, 24 Dec 2015 13:06:26 -0000
Hi Greg,
Merry Christmas and Happy New year!!
It is a good start. A couple of points that quickly popped up are below:
1. ECMP awareness - I think we should also include ECMP awareness as one of the requirement. We may need a right terminology that depicts ECMP and is applicable on different overlay.
2. Path MTU - I see this as one of the topic coming up with different overlay. It is better to include this in the requirement.
Will read more and share any more comments.
Thanks,
Nagendra
From: Rtg-ooam-dt <rtg-ooam-dt-bounces@ietf.org<mailto:rtg-ooam-dt-bounces@ietf.org>> on behalf of Gregory Mirsky <gregory.mirsky@ericsson.com<mailto:gregory.mirsky@ericsson.com>>
Date: Wednesday, December 23, 2015 at 11:05 PM
To: "rtg-ooam-dt@ietf.org<mailto:rtg-ooam-dt@ietf.org>" <rtg-ooam-dt@ietf.org<mailto:rtg-ooam-dt@ietf.org>>
Cc: "Alia Atlas (akatlas@gmail.com<mailto:akatlas@gmail.com>)" <akatlas@gmail.com<mailto:akatlas@gmail.com>>
Subject: [Rtg-ooam-dt] O-OAM Requirements
Dear All,
happy holidays, Merry Christmas and Happy New Year to All!
I put down some OAM requirements. Greatly appreciate your comments. Can we put it somewhere, somehow for everyone to edit?
You'll notice that some requirements are explicitly point to unidirectional character of OAM. I think that services provided y an overlay network are unidirectional and bi-directional Fault Monitoring and Performance Measurement are unnecessary. Though in some cases egress node may use IP network to send notification to the ingress node. What do you think?
Regards,
Greg
- [Rtg-ooam-dt] O-OAM Requirements Gregory Mirsky
- Re: [Rtg-ooam-dt] O-OAM Requirements Nagendra Kumar Nainar (naikumar)
- Re: [Rtg-ooam-dt] O-OAM Requirements Mach Chen
- Re: [Rtg-ooam-dt] O-OAM Requirements David Mozes
- Re: [Rtg-ooam-dt] O-OAM Requirements Nagendra Kumar Nainar (naikumar)
- Re: [Rtg-ooam-dt] O-OAM Requirements Gregory Mirsky
- Re: [Rtg-ooam-dt] O-OAM Requirements David Mozes
- Re: [Rtg-ooam-dt] O-OAM Requirements Gregory Mirsky
- Re: [Rtg-ooam-dt] O-OAM Requirements Mach Chen
- Re: [Rtg-ooam-dt] O-OAM Requirements David Mozes
- Re: [Rtg-ooam-dt] O-OAM Requirements Gregory Mirsky
- Re: [Rtg-ooam-dt] O-OAM Requirements David Mozes
- Re: [Rtg-ooam-dt] O-OAM Requirements Gregory Mirsky
- Re: [Rtg-ooam-dt] O-OAM Requirements David Mozes
- Re: [Rtg-ooam-dt] O-OAM Requirements Deepak Kumar (dekumar)
- Re: [Rtg-ooam-dt] O-OAM Requirements Gregory Mirsky
- Re: [Rtg-ooam-dt] O-OAM Requirements Nagendra Kumar Nainar (naikumar)
- Re: [Rtg-ooam-dt] O-OAM Requirements Deepak Kumar (dekumar)