RE: Design Team on Overlay OAM in Routing is Chartered

Antoni Przygienda <antoni.przygienda@ericsson.com> Wed, 16 December 2015 19:44 UTC

Return-Path: <antoni.przygienda@ericsson.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 DFC8A1A8944; Wed, 16 Dec 2015 11:44:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 HKVxSxrLDqiQ; Wed, 16 Dec 2015 11:44:48 -0800 (PST)
Received: from usplmg20.ericsson.net (usplmg20.ericsson.net [198.24.6.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3233A1A895E; Wed, 16 Dec 2015 11:44:43 -0800 (PST)
X-AuditID: c618062d-f79d16d000001b1c-d6-5671be5e0769
Received: from EUSAAHC004.ericsson.se (Unknown_Domain [147.117.188.84]) by usplmg20.ericsson.net (Symantec Mail Security) with SMTP id 7A.FB.06940.E5EB1765; Wed, 16 Dec 2015 20:41:18 +0100 (CET)
Received: from EUSAAMB103.ericsson.se ([147.117.188.120]) by EUSAAHC004.ericsson.se ([147.117.188.84]) with mapi id 14.03.0248.002; Wed, 16 Dec 2015 14:44:41 -0500
From: Antoni Przygienda <antoni.przygienda@ericsson.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: AQHRODi2qicnuF+7v0a6rdvZxx2DVp7OAULA
Date: Wed, 16 Dec 2015 19:44:40 +0000
Message-ID: <2E4BB27CAB87BF43B4207C0E55860F180EB4CFFA@eusaamb103.ericsson.se>
References: <CAG4d1rdLn2s5tkH7e4ievzJMvExCqRTbeFfs5O5ReFv+PRMY0A@mail.gmail.com>
In-Reply-To: <CAG4d1rdLn2s5tkH7e4ievzJMvExCqRTbeFfs5O5ReFv+PRMY0A@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [147.117.188.9]
Content-Type: multipart/alternative; boundary="_000_2E4BB27CAB87BF43B4207C0E55860F180EB4CFFAeusaamb103erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrHIsWRmVeSWpSXmKPExsUyuXRPiG7cvsIwg3WzdS0+PbzEbHH0sYTF zJ5/jBavTq1htDixZCubxfM5M1ksHhxeyGZx4c1vZovWozdZHTg9zh5ZwOgx5fdGVo+ds+6y exy+cJ/FY8mSn0weM49/YfH4cvkzWwB7FJdNSmpOZllqkb5dAlfG4+cv2QumNTJWrDx6nbWB 8UZtFyMnh4SAicTun/tZIGwxiQv31rN1MXJxCAkcYZRY3jaZBcJZzijRvP0OG0gVm4CFxOVv T5lBbBGBRInWNQ3sIEXMAiuZJO493sgKkhAWsJfoX3ifHaLIQWLNCogVIgJGEh+at4PFWQRU Je4972ICsXkFfCW+z18PZgsJBEicmP8BrJ5TIFBizqeFYPWMQOd9P7UGrIZZQFzi1pP5TBBn C0gs2XOeGcIWlXj5+B8rhK0osa9/OlAvB1B9vsTXnSIQqwQlTs58wjKBUXQWkkmzEKpmIamC CGtKrN+lD1GtKDGl+yE7hK0h0TpnLjuy+AJG9lWMHKXFBTm56UYGmxiBsXxMgk13B+P96Z6H GAU4GJV4eA2SC8KEWBPLiitzDzFKcDArifB+31MYJsSbklhZlVqUH19UmpNafIhRmoNFSZyX kYGBQUggPbEkNTs1tSC1CCbLxMEp1cA4jc/4DduUxa5zwp9fiay6Oz8xf5pl1lHzwx8/thxk 1nrCs833MQtjpVBO9oafHz/8YY/J28K0rbZp5c1nbxf2Pt++P/aWw5f0V3lB/MxXTrxlFpoi Jx1oyt0THdiy4rRW4mPTm+df6AVtcpnVr2bxK3Oh6czXquuCwxS9D5134RHjk+vgdk9QYinO SDTUYi4qTgQAl/SRNOECAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/routing-discussion/hCd9Pzk1Tlku8X_AfcYr529v2zw>
X-Mailman-Approved-At: Wed, 16 Dec 2015 11:47:54 -0800
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: Wed, 16 Dec 2015 19:44:51 -0000

+1, laudable effort & full support …

Thanks Alia

--- tony
_____________________________________________
“Simple, clear purpose and principles give rise to complex and intelligent behavior. Complex rules and regulations give rise to simple and stupid behavior.”
--- Dee Hock

From: rtgwg [mailto:rtgwg-bounces@ietf.org] On Behalf Of Alia Atlas
Sent: Wednesday, December 16, 2015 11:34 AM
To: routing-discussion@ietf.org
Cc: Brian Haberman; rtg-chairs@ietf.org; joel jaeggli; rtg-ads@tools.ietf.org; Benoit Claise; Terry Manderson; rtgwg@ietf.org
Subject: 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