IETF Logo Mail Archive

Re: [Rtg-ooam-dt] O-OAM Requirements

Gregory Mirsky <gregory.mirsky@ericsson.com> Sun, 27 December 2015 16:35 UTC

Return-Path: <gregory.mirsky@ericsson.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 03D481A1AF6 for <rtg-ooam-dt@ietfa.amsl.com>; Sun, 27 Dec 2015 08:35:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.5
X-Spam-Level:
X-Spam-Status: No, score=-101.5 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 bj2xu-dYJSmu for <rtg-ooam-dt@ietfa.amsl.com>; Sun, 27 Dec 2015 08:35:02 -0800 (PST)
Received: from usplmg20.ericsson.net (usplmg20.ericsson.net [198.24.6.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 37CE01A1AF0 for <rtg-ooam-dt@ietf.org>; Sun, 27 Dec 2015 08:35:01 -0800 (PST)
X-AuditID: c618062d-f79d16d000001b1c-e8-568011e1f595
Received: from EUSAAHC003.ericsson.se (Unknown_Domain [147.117.188.81]) by usplmg20.ericsson.net (Symantec Mail Security) with SMTP id D5.6A.06940.1E110865; Sun, 27 Dec 2015 17:29:21 +0100 (CET)
Received: from EUSAAMB103.ericsson.se ([147.117.188.120]) by EUSAAHC003.ericsson.se ([147.117.188.81]) with mapi id 14.03.0248.002; Sun, 27 Dec 2015 11:34:59 -0500
From: Gregory Mirsky <gregory.mirsky@ericsson.com>
To: "Nagendra Kumar Nainar (naikumar)" <naikumar@cisco.com>, "rtg-ooam-dt@ietf.org" <rtg-ooam-dt@ietf.org>
Thread-Topic: [Rtg-ooam-dt] O-OAM Requirements
Thread-Index: AQHRPkvjJ+k9zTW3h0a6gOsGVKRsAZ7fCKVw
Date: Sun, 27 Dec 2015 16:34:58 +0000
Message-ID: <7347100B5761DC41A166AC17F22DF112219726E0@eusaamb103.ericsson.se>
References: <D2A0E1EE.CAFD4%naikumar@cisco.com>
In-Reply-To: <D2A0E1EE.CAFD4%naikumar@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [147.117.188.11]
Content-Type: multipart/alternative; boundary="_000_7347100B5761DC41A166AC17F22DF112219726E0eusaamb103erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprLIsWRmVeSWpSXmKPExsUyuXRPoO5DwYYwg2+rtS0+PbzEbPF64lQ2 i3+te1kdmD2m/N7I6rFz1l12jyVLfjIFMEdx2aSk5mSWpRbp2yVwZWzu2c9U8DOy4nLjWaYG xu9+XYycHBICJhJbF15ghbDFJC7cW8/WxcjFISRwhFHizoG37BDOckaJxccesoFUsQkYSbzY 2MMOYosI5Ejs2/6OEcRmFrCQuNGyGmySsICuxJJtb1ggavQkzn6+wAZhG0k8mXMHyObgYBFQ lfj2KgUkzCvgK/Hq8TawciEBfYkZP+eAjeEUMJA4MnUW2HhGoOO+n1rDBLFKXOLWk/lMEEcL SCzZc54ZwhaVePn4H9QzShIff89nh6jPl9g3ZQ8zxC5BiZMzn7BMYBSdhWTULCRls5CUQcR1 JBbs/sQGYWtLLFv4mhnGPnPgMROy+AJG9lWMHKXFBTm56UYGmxiBkXZMgk13B+P96Z6HGAU4 GJV4eDccqQ8TYk0sK67MPcQowcGsJMJbebUuTIg3JbGyKrUoP76oNCe1+BCjNAeLkjjv/P3V YUIC6YklqdmpqQWpRTBZJg5OqQbGRnbVneHrDy6f/j3u5hLz6p99X0pu9U0Jzeyarlv2Knpp ccGSB1/nLNN/cyq89M91e/t5yXuzHnlzhqZs05/RK7S9b27C2sjUv89nNxv9sua9OatgNfN+ 891v2fnTm6eJdl0oD3vdptJlH3jqs+6cD0L/f3aarTesd1aNUpz+WmvBvewXD4+oKLEUZyQa ajEXFScCAOP4jSOwAgAA
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtg-ooam-dt/n2sR0_u2O17-DfnqyXIdg1JjITc>
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: Sun, 27 Dec 2015 16:35:05 -0000

Hi Nagendra,
thank you for your comments.
I agree with PMTUD. Though am not certain about the ECMP as far as pro-active monitoring if only tracing, i.e. on-demand. I think it would be great topic for us to discuss during the next call.
Would January 5th, 2016 @ 07:00 PST work? Would Tuesdays @ 07:00 PST work as regular meeting time?

                Regards,
                                Greg

From: Nagendra Kumar Nainar (naikumar) [mailto:naikumar@cisco.com]
Sent: Thursday, December 24, 2015 5:06 AM
To: Gregory Mirsky; rtg-ooam-dt@ietf.org
Cc: Alia Atlas (akatlas@gmail.com)
Subject: Re: [Rtg-ooam-dt] O-OAM Requirements

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

v2.8.7 | Report a Bug | By Email