Re: [Time] TIME proposal in OPS-Area meeting and RTGWG meeting
Qin Wu <bill.wu@huawei.com> Fri, 22 August 2014 06:01 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 D9BFD1A008B for <time@ietfa.amsl.com>; Thu, 21 Aug 2014 23:01:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.418
X-Spam-Level:
X-Spam-Status: No, score=-2.418 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.668, 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 WmYxqHgfrrZY for <time@ietfa.amsl.com>; Thu, 21 Aug 2014 23:01:54 -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 0DDDA1A0077 for <time@ietf.org>; Thu, 21 Aug 2014 23:01:52 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml404-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BIM81306; Fri, 22 Aug 2014 06:01:51 +0000 (GMT)
Received: from NKGEML402-HUB.china.huawei.com (10.98.56.33) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 22 Aug 2014 07:01:50 +0100
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.209]) by nkgeml402-hub.china.huawei.com ([10.98.56.33]) with mapi id 14.03.0158.001; Fri, 22 Aug 2014 14:01:44 +0800
From: Qin Wu <bill.wu@huawei.com>
To: "time@ietf.org" <time@ietf.org>
Thread-Topic: TIME proposal in OPS-Area meeting and RTGWG meeting
Thread-Index: Ac+mZLRdcwchI1ZcRcO1nl5LVG7l8gXaVjEQ
Date: Fri, 22 Aug 2014 06:01:43 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA845BACC0@nkgeml501-mbs.china.huawei.com>
References: <B8F9A780D330094D99AF023C5877DABA84589836@nkgeml501-mbs.china.huawei.com>
In-Reply-To: <B8F9A780D330094D99AF023C5877DABA84589836@nkgeml501-mbs.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.138.41.180]
Content-Type: multipart/alternative; boundary="_000_B8F9A780D330094D99AF023C5877DABA845BACC0nkgeml501mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/time/-kqN11Q5MipcmfqIybz4okh1syw
Cc: Benoit Claise <bclaise@cisco.com>
Subject: Re: [Time] TIME proposal in OPS-Area meeting and RTGWG meeting
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: Fri, 22 Aug 2014 06:01:56 -0000
Hi, Folks: Sorry for late followup. We had a good discussion in RTGWG and OPSAWG meeting. http://www.ietf.org/proceedings/90/minutes/minutes-90-rtgwg Opsawg meeting minutes haven’t been posted yet. People concerned a lot about defining one GOAM protocol in the data plane. There have already had a lot of work in RTGWG to discuss using Generic TLV and Header extension to carry OAM information. Some other effort can be seen in ITU-T. Another concern is if multi-layer management plane consolidation will also cause Crossing layer boundary introduced by inter-layer operation. Based on the discussion in both RTGWG/OPSAWG meeting and in the corridors, We feel look into multi-layer OAM management is good direction and complimentary to what has been done in RTG area regarding data plane OAM(e.g.,Overlay OAM). To address concern raised in the meeting, we propose to focus on management plane consolidation and use layer independent OAM management to replace transport independent OAM. We believe looking into layer independent OAM management and stitching different layer OAMs can provide better OAM visibility. To achieve this, one possible approach is to apply CFM like model to all the existing OAM technologies, then We can model different various OAM protocol in the same way. The problem statement draft and use case draft will be updated soon. The mailing list will be updated as well. We have sent a request to AD. Regards! -Qin 发件人: Time [mailto:time-bounces@ietf.org] 代表 Qin Wu 发送时间: 2014年7月23日 18:55 收件人: time@ietf.org 主题: [Time] TIME proposal in OPS-Area meeting and RTGWG meeting Hi, folks: Just want to remind we have two presentations on TIME Proposal in opsawg meeting and rtgwg meeting. 0900-1130 Morning Session I Ontario OPS opsawg Operations and Management Area Working Group WG - Combined with OPSAREA 1520-1650 Afternoon Session II Ballroom RTG rtgwg Routing Area Working Group WG If you want to know the latest progress and status of TIME proposal, please join us. Your comments/thoughts/concerns are also appreciated. Regards! -Qin