Re: Design Team on Overlay OAM in Routing is Chartered
Thomas Morin <thomas.morin@orange.com> Fri, 18 December 2015 08:49 UTC
Return-Path: <thomas.morin@orange.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 E579A1B348E; Fri, 18 Dec 2015 00:49:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.194
X-Spam-Level:
X-Spam-Status: No, score=-3.194 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-2.3, SPF_SOFTFAIL=0.665, 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 YoTXMKx4wZb7; Fri, 18 Dec 2015 00:49:37 -0800 (PST)
Received: from r-mail2.rd.orange.com (r-mail2.rd.orange.com [217.108.152.42]) by ietfa.amsl.com (Postfix) with ESMTP id D85071B348B; Fri, 18 Dec 2015 00:49:36 -0800 (PST)
Received: from r-mail2.rd.orange.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 5A87716C002; Fri, 18 Dec 2015 09:49:35 +0100 (CET)
Received: from FTRDCH01.rd.francetelecom.fr (unknown [10.194.32.11]) by r-mail2.rd.orange.com (Postfix) with ESMTP id 48CF916C001; Fri, 18 Dec 2015 09:49:35 +0100 (CET)
Received: from [10.193.71.12] (10.193.71.12) by FTRDCH01.rd.francetelecom.fr (10.194.32.11) with Microsoft SMTP Server id 14.3.266.1; Fri, 18 Dec 2015 09:49:34 +0100
Subject: Re: Design Team on Overlay OAM in Routing is Chartered
To: Loa Andersson <loa@pi.nu>, Alia Atlas <akatlas@gmail.com>, "routing-discussion@ietf.org" <routing-discussion@ietf.org>
References: <CAG4d1rdLn2s5tkH7e4ievzJMvExCqRTbeFfs5O5ReFv+PRMY0A@mail.gmail.com> <56737AE8.8060701@pi.nu>
From: Thomas Morin <thomas.morin@orange.com>
Organization: Orange
Message-ID: <5673C89E.4070507@orange.com>
Date: Fri, 18 Dec 2015 09:49:34 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0
MIME-Version: 1.0
In-Reply-To: <56737AE8.8060701@pi.nu>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/routing-discussion/HQve5GVTYwcVvzRFLsiXGCIFdEM>
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 08:49:39 -0000
Hi everyone, 2015-12-18, Loa Andersson: > Let me know if there is any support I can give from the bottom of my > mpls well. This comment is a good opportunity to highlight the fact that MPLS/GRE and MPLS/UDP are part of various service layer tunnels used for overlays. I will go as far as to suggest that these encaps should be explicitely called out in the DT charter (more than through "other technologies"). Best, -Thomas > 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