Re: Design Team on Overlay OAM in Routing is Chartered
Loa Andersson <loa@pi.nu> Fri, 18 December 2015 03:20 UTC
Return-Path: <loa@pi.nu>
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 89A241B327F; Thu, 17 Dec 2015 19:20:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 8noJb2gqQjZ6; Thu, 17 Dec 2015 19:20:07 -0800 (PST)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B07B41B327D; Thu, 17 Dec 2015 19:20:06 -0800 (PST)
Received: from [192.168.1.13] (unknown [112.205.86.30]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id 49C2D18013CB; Fri, 18 Dec 2015 04:18:55 +0100 (CET)
Subject: Re: Design Team on Overlay OAM in Routing is Chartered
To: Alia Atlas <akatlas@gmail.com>, "routing-discussion@ietf.org" <routing-discussion@ietf.org>
References: <CAG4d1rdLn2s5tkH7e4ievzJMvExCqRTbeFfs5O5ReFv+PRMY0A@mail.gmail.com>
From: Loa Andersson <loa@pi.nu>
Message-ID: <56737AE8.8060701@pi.nu>
Date: Fri, 18 Dec 2015 11:18:00 +0800
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0
MIME-Version: 1.0
In-Reply-To: <CAG4d1rdLn2s5tkH7e4ievzJMvExCqRTbeFfs5O5ReFv+PRMY0A@mail.gmail.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/routing-discussion/fPCzvpoa4ZThj3ciT3083uil-9c>
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 03:20:09 -0000
Alia, Good initiative! Design team, Let me know if there is any support I can give from the bottom of my mpls well. /Loa On 2015-12-17 03:33, Alia Atlas wrote: > 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 > > > > > _______________________________________________ > rtgwg mailing list > rtgwg@ietf.org > https://www.ietf.org/mailman/listinfo/rtgwg >
- Design Team on Overlay OAM in Routing is Chartered Alia Atlas
- RE: Design Team on Overlay OAM in Routing is Char… Antoni Przygienda
- Re: Design Team on Overlay OAM in Routing is Char… Jeff Tantsura
- Re: Design Team on Overlay OAM in Routing is Char… VAN DE VELDE, Gunter (Gunter)
- RE: Design Team on Overlay OAM in Routing is Char… Qin Wu
- Re: Design Team on Overlay OAM in Routing is Char… Loa Andersson
- Re: Design Team on Overlay OAM in Routing is Char… Thomas Morin
- Re: Design Team on Overlay OAM in Routing is Char… Thomas Morin
- Re: Design Team on Overlay OAM in Routing is Char… Manish Kumar (manishkr)
- RE: Design Team on Overlay OAM in Routing is Char… Black, David
- RE: Design Team on Overlay OAM in Routing is Char… Gregory Mirsky
- RE: Design Team on Overlay OAM in Routing is Char… Russ White
- RE: Design Team on Overlay OAM in Routing is Char… Russ White