IETF Logo Mail Archive

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

Mach Chen <mach.chen@huawei.com> Thu, 24 December 2015 07:27 UTC

Return-Path: <mach.chen@huawei.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 C0C321AC3A5 for <rtg-ooam-dt@ietfa.amsl.com>; Wed, 23 Dec 2015 23:27:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 qE1uuopFOqns for <rtg-ooam-dt@ietfa.amsl.com>; Wed, 23 Dec 2015 23:27:44 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CBBEE1ABD3C for <rtg-ooam-dt@ietf.org>; Wed, 23 Dec 2015 23:27:42 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml401-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CFW93658; Thu, 24 Dec 2015 07:27:39 +0000 (GMT)
Received: from SZXEMA414-HUB.china.huawei.com (10.82.72.73) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.235.1; Thu, 24 Dec 2015 07:27:35 +0000
Received: from SZXEMA510-MBX.china.huawei.com ([169.254.3.73]) by SZXEMA414-HUB.china.huawei.com ([10.82.72.73]) with mapi id 14.03.0235.001; Thu, 24 Dec 2015 15:27:25 +0800
From: Mach Chen <mach.chen@huawei.com>
To: Gregory Mirsky <gregory.mirsky@ericsson.com>, "rtg-ooam-dt@ietf.org" <rtg-ooam-dt@ietf.org>
Thread-Topic: O-OAM Requirements
Thread-Index: AdE9/wBFKKAC1T+hSLCARUbLOu0FNQAGY4jg
Date: Thu, 24 Dec 2015 07:27:24 +0000
Message-ID: <F73A3CB31E8BE34FA1BBE3C8F0CB2AE28B689B76@SZXEMA510-MBX.china.huawei.com>
References: <7347100B5761DC41A166AC17F22DF112219715D5@eusaamb103.ericsson.se>
In-Reply-To: <7347100B5761DC41A166AC17F22DF112219715D5@eusaamb103.ericsson.se>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.102.135]
Content-Type: multipart/mixed; boundary="_004_F73A3CB31E8BE34FA1BBE3C8F0CB2AE28B689B76SZXEMA510MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020201.567B9E6B.00E5, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.3.73, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 129b4aae67da9e4af425621634911bec
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtg-ooam-dt/iK8Gh6EtbZaBliTEQB-0UsJJW5k>
Cc: "mach.chen@outlook.com" <mach.chen@outlook.com>, "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 07:27:48 -0000

Hi Greg and others,

Merry Christmas and Happy New Year to all of you and your family!

Eirk and I made some experiments to use Office Online for sharing document editing. I think it works although it is harder to use than Google Docs.

I made some modifications(with markups) to performance measurement section. Here are some reasons for the modification:

1) Normally, one-way or two-way is specific to packet delay measurement.
2) For delay measurement, only one-way can be measured in either active or passive way, for two-way, only active method can be used;
3) I also add some requirements about performing per-segment loss/delay measurement, per-segment measurement means measuring a segment of a path, it is useful in fault localization.

Best regards,
Mach

From: Rtg-ooam-dt [mailto:rtg-ooam-dt-bounces@ietf.org] On Behalf Of Gregory Mirsky
Sent: Thursday, December 24, 2015 12:06 PM
To: rtg-ooam-dt@ietf.org
Cc: Alia Atlas (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