IETF Logo Mail Archive

Re: Request for comments: draft-jain-nvo3-overlay-oam-01.txt

Shahram Davari <davari@broadcom.com> Thu, 27 February 2014 15:58 UTC

Return-Path: <davari@broadcom.com>
X-Original-To: l2vpn@ietfa.amsl.com
Delivered-To: l2vpn@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 77FA71A033E for <l2vpn@ietfa.amsl.com>; Thu, 27 Feb 2014 07:58:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.446
X-Spam-Level:
X-Spam-Status: No, score=-2.446 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.547] 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 sHhq-t66xCXK for <l2vpn@ietfa.amsl.com>; Thu, 27 Feb 2014 07:58:10 -0800 (PST)
Received: from mail-gw3-out.broadcom.com (mail-gw3-out.broadcom.com [216.31.210.64]) by ietfa.amsl.com (Postfix) with ESMTP id 63A6F1A00B2 for <l2vpn@ietf.org>; Thu, 27 Feb 2014 07:58:10 -0800 (PST)
X-IronPort-AV: E=Sophos; i="4.97,555,1389772800"; d="scan'208,217"; a="16696187"
Received: from irvexchcas07.broadcom.com (HELO IRVEXCHCAS07.corp.ad.broadcom.com) ([10.9.208.55]) by mail-gw3-out.broadcom.com with ESMTP; 27 Feb 2014 08:09:47 -0800
Received: from SJEXCHCAS04.corp.ad.broadcom.com (10.16.203.10) by IRVEXCHCAS07.corp.ad.broadcom.com (10.9.208.55) with Microsoft SMTP Server (TLS) id 14.3.174.1; Thu, 27 Feb 2014 07:58:08 -0800
Received: from SJEXCHMB12.corp.ad.broadcom.com ([fe80::bc15:c1e1:c29a:36f7]) by SJEXCHCAS04.corp.ad.broadcom.com ([::1]) with mapi id 14.03.0174.001; Thu, 27 Feb 2014 07:58:08 -0800
From: Shahram Davari <davari@broadcom.com>
To: Kanwar Singh <kanwar@nuagenetworks.net>
Subject: Re: Request for comments: draft-jain-nvo3-overlay-oam-01.txt
Thread-Topic: Request for comments: draft-jain-nvo3-overlay-oam-01.txt
Thread-Index: AQHPM9Mh8gEtCy0e4EuWLz1WxAmt5prJQcOt
Date: Thu, 27 Feb 2014 15:58:07 +0000
Message-ID: <B23247FA-7CED-4F78-8858-076CA83F613C@broadcom.com>
References: <CAPCgso32vYqPEq4upa1FG78quZwBOJpzsCSCYTX2R7XgHzLiNA@mail.gmail.com>
In-Reply-To: <CAPCgso32vYqPEq4upa1FG78quZwBOJpzsCSCYTX2R7XgHzLiNA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: multipart/alternative; boundary="_000_B23247FA7CED4F788858076CA83F613Cbroadcomcom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/l2vpn/O_uNJbX9xEZFFZxjZQ9h6QyS4tI
Cc: "l2vpn@ietf.org" <l2vpn@ietf.org>, Pradeep Jain <pradeep@nuagenetworks.net>, Vinay Bannai <vbannai@paypal.com>, Ravi Shekhar <rshekhar@juniper.net>
X-BeenThere: l2vpn@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Layer 2 Virtual Private Networks <l2vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l2vpn/>
List-Post: <mailto:l2vpn@ietf.org>
List-Help: <mailto:l2vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Feb 2014 15:58:16 -0000

Hi

Why don't you use existing IP based OAM messages such as BFD, OWAMP, TWAMP, etc.

Regards,
Shahram


On Feb 27, 2014, at 7:46 AM, "Kanwar Singh" <kanwar@nuagenetworks.net<mailto:kanwar@nuagenetworks.net>> wrote:

Dear All,

We have submitted the below draft that proposes Generic OAM and Datapath Failure Detection Mechanism(s) for Overlay Networks.

We would like to solicit inputs from the members of L2VPN WG.

Please review the same and update us with your inputs/feedback.


Warm Regards

- Kanwar



A new version of I-D, draft-jain-nvo3-overlay-oam-01.txt has been successfully submitted by Kanwar Singh and posted to the

IETF repository.



Name:           draft-jain-nvo3-overlay-oam

Revision:       01
Title:          Generic Overlay OAM and Datapath Failure Detection


Document date:  2014-02-12

Group:          Individual Submission

Pages:          44
URL:            http://www.ietf.org/internet-drafts/draft-jain-nvo3-overlay-oam-01.txt


Status:         https://datatracker.ietf.org/doc/draft-jain-nvo3-overlay-oam/


Htmlized:      http://tools.ietf.org/html/draft-jain-nvo3-overlay-oam-01


Diff:              http://www.ietf.org/rfcdiff?url2=draft-jain-nvo3-overlay-oam-01



Abstract:


   This proposal describes a mechanism that can be used to detect Data


   Path Failures of various overlay technologies as VXLAN, NVGRE,


   MPLSoGRE and MPLSoUDP and verifying/sanity of their Control and Data


   Plane for given Overlay Segment.  This document defines the following


   for each of the above Overlay Technologies:


   o  Encapsulation of OAM Packet, such that it has same Outer and


      Overlay Header as any End-System's data going over the same


      Overlay Segment.


   o  The mechanism to trace the Underlay that is exercised by any


      Overlay Segment.


   o  Procedure to verify presence of any given Tenant VM or End-System


      within a given Overlay Segment at Overlay End-Point.


   Even though the present proposal addresses Overlay OAM for VXLAN,


   NVGRE, MPLSoGRE and MPLSoUDP, but the procedures described are


   generic enough to accommodate OAM for any other Overlay Technology.

v2.8.7 | Report a Bug | By Email