Design Team on Overlay OAM in Routing is Chartered

Alia Atlas <akatlas@gmail.com> Wed, 16 December 2015 19:33 UTC

Return-Path: <akatlas@gmail.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 794E21A892E; Wed, 16 Dec 2015 11:33:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.999
X-Spam-Level:
X-Spam-Status: No, score=-101.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 Mwf7LlNScc6l; Wed, 16 Dec 2015 11:33:35 -0800 (PST)
Received: from mail-ob0-x236.google.com (mail-ob0-x236.google.com [IPv6:2607:f8b0:4003:c01::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 559DB1A8928; Wed, 16 Dec 2015 11:33:35 -0800 (PST)
Received: by mail-ob0-x236.google.com with SMTP id 18so40493472obc.2; Wed, 16 Dec 2015 11:33:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=5GaI/mj8y7nItgbrVsLy22rzf7sX+hFlFrrvRT5aTRg=; b=yT1SxZMJaJpCNjwEcMLknKL3eNyAux+z8cvkFsgx4hoKgKf3bJP6L1yOnVwwzJugVj fZ7h7U103Fx7SnzjEZywMsIGLD8wws2zIQW1sJqggMjBXeJX8s/I6wyERfU9MdLv6Od9 FXX/h4eRu0EoWB7QDUysgwE9mSug+/K5hU2hXPvZ9xo7aw6/0W/1btZiX7yfDVBiL+XZ ZoTcwdAy8KqKFcihm7X9L0uu3OcEVPfMirXOGDA++oSFSAVSHpdqf9c9T/qRqjwyBoZE I/fKGVGGWLHK04sNddy0dxFphYD/1sZX+TvEWB/NcpRrc29V0GYfjc/p+39iTTsgvue8 ZnSw==
MIME-Version: 1.0
X-Received: by 10.182.28.7 with SMTP id x7mr25275370obg.13.1450294414702; Wed, 16 Dec 2015 11:33:34 -0800 (PST)
Received: by 10.60.177.103 with HTTP; Wed, 16 Dec 2015 11:33:34 -0800 (PST)
Date: Wed, 16 Dec 2015 14:33:34 -0500
Message-ID: <CAG4d1rdLn2s5tkH7e4ievzJMvExCqRTbeFfs5O5ReFv+PRMY0A@mail.gmail.com>
Subject: Design Team on Overlay OAM in Routing is Chartered
From: Alia Atlas <akatlas@gmail.com>
To: "routing-discussion@ietf.org" <routing-discussion@ietf.org>
Content-Type: multipart/alternative; boundary=089e015380ba68bf34052708fb81
Archived-At: <http://mailarchive.ietf.org/arch/msg/routing-discussion/ZQYpinvWWdjdLrC-gAtnqat_vSU>
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:33:37 -0000

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.

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