Re: Request for comments: draft-jain-nvo3-overlay-oam-01.txt
Pradeep Jain <pradeep@nuagenetworks.net> Fri, 28 February 2014 03:38 UTC
Return-Path: <pradeep@nuagenetworks.net>
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 DB67E1A02D9 for <l2vpn@ietfa.amsl.com>;
Thu, 27 Feb 2014 19:38:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No,
score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,
FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001,
RCVD_IN_DNSWL_LOW=-0.7] 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 c5JAiwrY1qXW for
<l2vpn@ietfa.amsl.com>; Thu, 27 Feb 2014 19:38:15 -0800 (PST)
Received: from mail-ob0-f175.google.com (mail-ob0-f175.google.com
[209.85.214.175]) by ietfa.amsl.com (Postfix) with ESMTP id C83891A02C5 for
<l2vpn@ietf.org>; Thu, 27 Feb 2014 19:38:15 -0800 (PST)
Received: by mail-ob0-f175.google.com with SMTP id uy5so123664obc.6 for
<l2vpn@ietf.org>; Thu, 27 Feb 2014 19:38:14 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net;
s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:date
:message-id:subject:from:to:cc:content-type;
bh=pf1DeWUgUMnTPLhxTGc1ixE07EROUDB0GPjQcIU6vlY=;
b=Tudiz4WMLe/c8mt2LV7vaJoZ/yC+UYg5LF+vuV1jL+IQ0ipu1R6mw0hdHWdOfZVNQf
gvR/QnsrzfXJXgZmfow1MasUs/RP8j3y98BjbZ69d+yKfiy2iGiBC6w6GANuL8DN3ITz
Bj9PrjMRO9WGvEGBXeYPR6oL9MrciWPVXHUTXP5eMosGsMMGQHb74a4dZXQH8nD/dwWe
5yaugG4vBokrkxvHZJza4EfnpnuPEHYTmVouk+RwEk2DO0ijxZcBmTfgx+7eJxXKptWP
thK3bgAcH04sSs5Z2xei+W423BOD/nnmCOtqYI044vthh5wlpqvovFr8kwvSxYDqggdE hsMg==
X-Gm-Message-State: ALoCoQmjGuJMkpEw/GOVrBmbr9nP5Ub7V3Am9KQT/0pkg+KiA3AKXBGkfr3UCXsvV3KwSsS3hZtI
MIME-Version: 1.0
X-Received: by 10.60.134.200 with SMTP id pm8mr498959oeb.40.1393558694001;
Thu, 27 Feb 2014 19:38:14 -0800 (PST)
Received: by 10.76.82.230 with HTTP; Thu, 27 Feb 2014 19:38:13 -0800 (PST)
In-Reply-To: <CAHYfYvLy6ih=3=4BVWSRuajXOt473BVTT2S=c0opg1Zm=Mar4A@mail.gmail.com>
References: <CAPCgso32vYqPEq4upa1FG78quZwBOJpzsCSCYTX2R7XgHzLiNA@mail.gmail.com>
<B23247FA-7CED-4F78-8858-076CA83F613C@broadcom.com>
<CF351FD5.B21EA%wim.henderickx@alcatel-lucent.com>
<D26A6EDE-42D3-45A6-8FFC-3B1850433722@lucidvision.com>
<CF34C0FC.7D7B%alohiya@juniper.net>
<4A6CE49E6084B141B15C0713B8993F281BFCD485@SJEXCHMB12.corp.ad.broadcom.com>
<CAHYfYvLy6ih=3=4BVWSRuajXOt473BVTT2S=c0opg1Zm=Mar4A@mail.gmail.com>
Date: Thu, 27 Feb 2014 19:38:13 -0800
Message-ID: <CAHYfYvL5mPANt56ivvCnyMYfMaPs=GM1cs31VfCK9xAmg9oLpA@mail.gmail.com>
Subject: Re: Request for comments: draft-jain-nvo3-overlay-oam-01.txt
From: Pradeep Jain <pradeep@nuagenetworks.net>
To: Shahram Davari <davari@broadcom.com>
Content-Type: multipart/alternative; boundary=047d7b417831ee144d04f36f2a90
Archived-At: http://mailarchive.ietf.org/arch/msg/l2vpn/pUo3r5W39y7IwPFUWOzIKfDOzJ4
Cc: "l2vpn@ietf.org" <l2vpn@ietf.org>, 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: Fri, 28 Feb 2014 03:38:18 -0000
On Thursday, February 27, 2014, Pradeep Jain <pradeep@nuagenetworks.net> wrote: > Hi Shahram, > > Using BFD mandates that the probes need to be sent continuously. We don't > want to impose this restriction and leave it to the user to decide if they > want an on-demand probe or a continuous probe, which is what has been > defined in the draft.. > > Regarding the second point about including VNI/VSID in TLV, for the > hardware/forwarding plane which is not capable of giving the overlay > context of the packet (based on VNI/VSID) to the control plane, we need to > rely on the VNI/VSID in the TLV to derive the overlay context in the > control plane... > > Regards > Pradeep > > > On Thu, Feb 27, 2014 at 11:19 AM, Shahram Davari <davari@broadcom.com<javascript:_e(%7B%7D,'cvml','davari@broadcom.com');> > > wrote: > > Anil, > > > > I don't agree. If you use for example BFD for inner IP, and if BFD says > connectivity is OK, this implies that the Overlay connectivity is also OK, > since BFD is inside the overlay. > > Also I am not sure why you are adding the VNI, VSID, etc in the message as > TLV, since these value are already in the packet header. > > > > Thx > Shahram > > > > *From:* L2vpn [mailto:l2vpn-bounces@ietf.org] *On Behalf Of *Anil Lohiya > *Sent:* Thursday, February 27, 2014 10:19 AM > *To:* Thomas Nadeau; Henderickx, Wim (Wim) > > *Cc:* l2vpn@ietf.org; Pradeep Jain; Vinay Bannai; Ravi Shekhar > *Subject:* Re: Request for comments: draft-jain-nvo3-overlay-oam-01.txt > > > > > > Existing ping/traceroute mechanisms don't work in the virtualized > environment e.g. ping may report that IP reachability between the ingress > and egress tunnel endpoints is fine but the end systems (i.e. VM, physical > server etc.) connectivity for a tenant could still be broken. This is > because ping only verifies basic connectivity between two endpoints in the > underlay but NOT in the context of overlay segments. Hence, we need > debugging tools that work in the overlay environment. Think why there was a > need to have lsp ping ... requirement with IP overlays is not much different. > > > > Question is not whether applications are resilient or not... One can not > ignore the fact that operators have to think about having the right tools > when that "inevitable" call comes from their customer about deteriorating > application performance or traffic blackhole and there are no tools today > specific to overlay network debugging. > > > > - Anil > > > > *From: *Thomas Nadeau <tnadeau@lucidvision.com> > *Date: *Thursday, February 27, 2014 8:05 AM > *To: *"Henderickx, Wim (Wim)" < > > >
- Request for comments: draft-jain-nvo3-overlay-oam… Kanwar Singh
- Re: Request for comments: draft-jain-nvo3-overlay… Shahram Davari
- Re: Request for comments: draft-jain-nvo3-overlay… Henderickx, Wim (Wim)
- Re: Request for comments: draft-jain-nvo3-overlay… Thomas Nadeau
- Re: Request for comments: draft-jain-nvo3-overlay… Thomas Nadeau
- Re: Request for comments: draft-jain-nvo3-overlay… Henderickx, Wim (Wim)
- Re: Request for comments: draft-jain-nvo3-overlay… Greg Mirsky
- Re: Request for comments: draft-jain-nvo3-overlay… Rabadan, Jorge (Jorge)
- RE: Request for comments: draft-jain-nvo3-overlay… Gregory Mirsky
- Re: Request for comments: draft-jain-nvo3-overlay… Sam Aldrin
- Re: Request for comments: draft-jain-nvo3-overlay… Anil Lohiya
- RE: Request for comments: draft-jain-nvo3-overlay… Shahram Davari
- RE: Request for comments: draft-jain-nvo3-overlay… David Allan I
- Re: Request for comments: draft-jain-nvo3-overlay… S. Davari
- Re: Request for comments: draft-jain-nvo3-overlay… Kanwar Singh
- Re: Request for comments: draft-jain-nvo3-overlay… Pradeep Jain
- Re: Request for comments: draft-jain-nvo3-overlay… S. Davari
- Re: Request for comments: draft-jain-nvo3-overlay… Shahram Davari
- Re: Request for comments: draft-jain-nvo3-overlay… Anil Lohiya
- Re: Request for comments: draft-jain-nvo3-overlay… Henderickx, Wim (Wim)
- Re: Request for comments: draft-jain-nvo3-overlay… Sam Aldrin
- RE: Request for comments: draft-jain-nvo3-overlay… Gregory Mirsky
- RE: Request for comments: draft-jain-nvo3-overlay… Gregory Mirsky
- Re: Request for comments: draft-jain-nvo3-overlay… Shahram Davari
- Re: Request for comments: draft-jain-nvo3-overlay… Sam Aldrin
- Re: Request for comments: draft-jain-nvo3-overlay… Shahram Davari
- Re: Request for comments: draft-jain-nvo3-overlay… Sam Aldrin
- RE: Request for comments: draft-jain-nvo3-overlay… Gregory Mirsky
- Re: Request for comments: draft-jain-nvo3-overlay… Sam Aldrin
- Re: Request for comments: draft-jain-nvo3-overlay… Henderickx, Wim (Wim)
- Re: Request for comments: draft-jain-nvo3-overlay… Henderickx, Wim (Wim)
- RE: Request for comments: draft-jain-nvo3-overlay… Gregory Mirsky
- Re: Request for comments: draft-jain-nvo3-overlay… Henderickx, Wim (Wim)
- Re: Request for comments: draft-jain-nvo3-overlay… Pradeep Jain
- Re: Request for comments: draft-jain-nvo3-overlay… Thomas Nadeau