RE: Design Team on Overlay OAM in Routing is Chartered

Qin Wu <bill.wu@huawei.com> Fri, 18 December 2015 02:40 UTC

Return-Path: <bill.wu@huawei.com>
X-Original-To: routing-discussion@ietfa.amsl.com
Delivered-To: routing-discussion@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B87D21B324C; Thu, 17 Dec 2015 18:40:07 -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 jJQjyMEEGfrV; Thu, 17 Dec 2015 18:40:05 -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 599191B324B; Thu, 17 Dec 2015 18:40:02 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml405-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CFP35152; Fri, 18 Dec 2015 02:39:59 +0000 (GMT)
Received: from lhreml704-cah.china.huawei.com (10.201.5.130) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.235.1; Fri, 18 Dec 2015 02:39:57 +0000
Received: from NKGEML413-HUB.china.huawei.com (10.98.56.74) by lhreml704-cah.china.huawei.com (10.201.5.130) with Microsoft SMTP Server (TLS) id 14.3.235.1; Fri, 18 Dec 2015 02:39:57 +0000
Received: from NKGEML513-MBX.china.huawei.com ([169.254.1.252]) by NKGEML413-HUB.china.huawei.com ([10.98.56.74]) with mapi id 14.03.0235.001; Fri, 18 Dec 2015 10:39:50 +0800
From: Qin Wu <bill.wu@huawei.com>
To: Alia Atlas <akatlas@gmail.com>, "routing-discussion@ietf.org" <routing-discussion@ietf.org>
Subject: RE: Design Team on Overlay OAM in Routing is Chartered
Thread-Topic: Design Team on Overlay OAM in Routing is Chartered
Thread-Index: AQHRODiyMASoEZ3WikWLSdL3pmJj6Z7QCIHg
Date: Fri, 18 Dec 2015 02:39:49 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA852A7D97@nkgeml513-mbx.china.huawei.com>
References: <CAG4d1rdLn2s5tkH7e4ievzJMvExCqRTbeFfs5O5ReFv+PRMY0A@mail.gmail.com>
In-Reply-To: <CAG4d1rdLn2s5tkH7e4ievzJMvExCqRTbeFfs5O5ReFv+PRMY0A@mail.gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.136.79.8]
Content-Type: multipart/alternative; boundary="_000_B8F9A780D330094D99AF023C5877DABA852A7D97nkgeml513mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020204.56737200.003D, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.1.252, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: c1e870f168b1c2ee6a2f453551e8dc4b
Archived-At: <http://mailarchive.ietf.org/arch/msg/routing-discussion/_JJtM92ddkMyVh-hP9L_TAwe7Kg>
Cc: Brian Haberman <brian@innovationslab.net>, "rtg-chairs@ietf.org" <rtg-chairs@ietf.org>, joel jaeggli <joelja@bogus.com>, "rtg-ads@tools.ietf.org" <rtg-ads@tools.ietf.org>, Benoit Claise <bclaise@cisco.com>, "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/routing-discussion/>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Dec 2015 02:40:07 -0000

Good to know this activity to be setup. I believe this work is complementary to what LIME WG is doing since
1. LIME is focusing modeling existing OAM technology and not tasked to develop any new OAM protocols.
2. If any new protocol can be developed through this activity, common YANG model proposed in LIME WG can really benefit from it.

-Qin
发件人: routing-discussion [mailto:routing-discussion-bounces@ietf.org] 代表 Alia Atlas
发送时间: 2015年12月17日 3:34
收件人: routing-discussion@ietf.org
抄送: Brian Haberman; rtg-chairs@ietf.org; joel jaeggli; rtg-ads@tools.ietf.org; Benoit Claise; rtgwg@ietf.org
主题: Design Team on Overlay OAM in Routing is Chartered

Based on the presentation by Greg Mirsky and discussion in rtgwg and elsewhere, I have decided to charter a fast-moving Routing Area design team to work on Overlay OAM.

The charter is below:

In the Routing Area, several WGs (e.g. NVO3, BIER, and SFC) are working on relatively new encapsulations to create overlays. These overlay or service encapsulations are transport-independent since they may be over different transports or at different layers in the networking stack. Each WG is starting to discuss what OAM and tools need to be developed (see draft-ietf-sfc-oam-framework-00, draft-ietf-bier-oam-requirements-00, and individual drafts in NVO3). With increasing use of overlay and service layer tunnels, extensions to traceroute to allow visibility into multiple layers are being discussed (e.g. draft-nordmark-nvo3-transcending-traceroute-01).

There is an opportunity to propose protocols and methods to provide Overlay OAM in a sufficiently generic fashion that they can meet the requirements and be applied to at least BIER, NSH, VXLAN-GPE, GENEVE, and GUE. A truly successful result would also be applicable to other technologies.

This Design Team is chartered to first produce a brief gap analysis and requirements document to focus its work on protocol extensions. This should be published by March 2016. With that basis, this Design Team is chartered to rapidly propose extensions to existing IETF OAM protocols such as those discussed in [RFC 7276] and new ones to support the requirements for OAM from NVO3, BIER, and SFC. The Design Team will produce an initial proposal by IETF 95. It is expected that the initial proposal will provide guidance to additional people who will be interested in working on the details and gaps.

The Design Team will consider the preliminary OAM requirements from NVO3, BIER, and SFC. The Design Team should align with the LIME WG's work on common YANG models of OAM.
The members of the design team are:
   Greg Mirsky (DT lead)
   Ignas Bagdonas
   Erik Nordmark
   Carlos Pignataro
   Mach Chen
   Santosh Pallagatti
   Deepak Kumarde
   David Mozes
   Nagendra Kumar Nainar

The design team has a private mailing list that will be publicly archived.
The mailing list is rtg-ooam-dt@ietf.org<mailto:rtg-ooam-dt@ietf.org>.

The design team will also use a wiki to track some information.  Others are also welcome to comment and interact there.
The wiki is at:  http://wiki.tools.ietf.org/area/rtg/trac/wiki/RtgOoamDT

Regards,
Alia