[Time] Use Case 4 for TIME: Segment OAM

Qin Wu <bill.wu@huawei.com> Wed, 18 June 2014 07:44 UTC

Return-Path: <bill.wu@huawei.com>
X-Original-To: time@ietfa.amsl.com
Delivered-To: time@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 451EE1A005D for <time@ietfa.amsl.com>; Wed, 18 Jun 2014 00:44:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.01
X-Spam-Level:
X-Spam-Status: No, score=-3.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_IMAGE_ONLY_28=1.404, HTML_IMAGE_RATIO_02=0.437, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] 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 gIzRkQ4_RWlt for <time@ietfa.amsl.com>; Wed, 18 Jun 2014 00:44:48 -0700 (PDT)
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 B91D81A007C for <time@ietf.org>; Wed, 18 Jun 2014 00:44:46 -0700 (PDT)
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 BIO04045; Wed, 18 Jun 2014 07:44:45 +0000 (GMT)
Received: from nkgeml405-hub.china.huawei.com (10.98.56.36) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 18 Jun 2014 08:44:43 +0100
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.193]) by nkgeml405-hub.china.huawei.com ([10.98.56.36]) with mapi id 14.03.0158.001; Wed, 18 Jun 2014 15:44:38 +0800
From: Qin Wu <bill.wu@huawei.com>
To: "time@ietf.org" <time@ietf.org>
Thread-Topic: Use Case 4 for TIME: Segment OAM
Thread-Index: Ac+KySeuykCSuCfCR2SOiyL827ZAyQ==
Date: Wed, 18 Jun 2014 07:44:37 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA8454CF2F@nkgeml501-mbs.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.138.41.180]
Content-Type: multipart/related; boundary="_004_B8F9A780D330094D99AF023C5877DABA8454CF2Fnkgeml501mbschi_"; type="multipart/alternative"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/time/qs-z_F2xcMOItskpTm842eX9CUc
Subject: [Time] Use Case 4 for TIME: Segment OAM
X-BeenThere: time@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Transport Independent OAM in Multi-Layer network Entity \(TIME\) discussion list." <time.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/time>, <mailto:time-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/time/>
List-Post: <mailto:time@ietf.org>
List-Help: <mailto:time-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/time>, <mailto:time-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Jun 2014 07:44:51 -0000

[cid:image001.png@01CF8B0C.35D20B20]
Each segment OAM can be stitched together to form end to end OAM. How we can do this, it may needs a centralized OSS/NMS to get involved in.