[Time] Use Case 2 for TIME: OAM atop of layer 3
Qin Wu <bill.wu@huawei.com> Wed, 18 June 2014 07:39 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 DE16C1A005D for <time@ietfa.amsl.com>; Wed, 18 Jun 2014 00:39:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.413
X-Spam-Level:
X-Spam-Status: No, score=-4.413 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_IMAGE_ONLY_32=0.001, 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 dDDqszmzTm_2 for <time@ietfa.amsl.com>; Wed, 18 Jun 2014 00:39:52 -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 541A71A002B for <time@ietf.org>; Wed, 18 Jun 2014 00:39:51 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml406-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BIO03515; Wed, 18 Jun 2014 07:39:50 +0000 (GMT)
Received: from nkgeml409-hub.china.huawei.com (10.98.56.40) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 18 Jun 2014 08:39:48 +0100
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.193]) by nkgeml409-hub.china.huawei.com ([10.98.56.40]) with mapi id 14.03.0158.001; Wed, 18 Jun 2014 15:39:42 +0800
From: Qin Wu <bill.wu@huawei.com>
To: "time@ietf.org" <time@ietf.org>
Thread-Topic: Use Case 2 for TIME: OAM atop of layer 3
Thread-Index: Ac+KyHcDWudJqExoRySNBTLE7M7uJg==
Date: Wed, 18 Jun 2014 07:39:41 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA8454CF0F@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_B8F9A780D330094D99AF023C5877DABA8454CF0Fnkgeml501mbschi_"; type="multipart/alternative"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/time/q49nysnvMk8r50wgxzRjfPRtvXE
Subject: [Time] Use Case 2 for TIME: OAM atop of layer 3
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:39:55 -0000
[cid:image001.png@01CF8B0B.8526FE20] This is Service Function Chain related use case, each service function in the chain is at different layer. Any two measurement point can be located at different layer. There is no layer 4-7 OAM to be defined yet for this use case. However it is possible to extend protocol header or use BFD to support multi-layer OAM in this case.