Re: [bess] Implementation poll for draft-ietf-bess-evpn-lsp-ping-05
Greg Mirsky <gregimirsky@gmail.com> Fri, 03 September 2021 14:41 UTC
Return-Path: <gregimirsky@gmail.com>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
by ietfa.amsl.com (Postfix) with ESMTP id B0D623A20C2;
Fri, 3 Sep 2021 07:41:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.996
X-Spam-Level:
X-Spam-Status: No, score=-1.996 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001,
HTML_FONT_FACE_BAD=0.001, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1,
SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001]
autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key)
header.d=gmail.com
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 DeeltIv5RTjg; Fri, 3 Sep 2021 07:41:05 -0700 (PDT)
Received: from mail-ej1-x62d.google.com (mail-ej1-x62d.google.com
[IPv6:2a00:1450:4864:20::62d])
(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 EAE3E3A20BC;
Fri, 3 Sep 2021 07:41:04 -0700 (PDT)
Received: by mail-ej1-x62d.google.com with SMTP id bt14so12558447ejb.3;
Fri, 03 Sep 2021 07:41:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;
h=mime-version:references:in-reply-to:from:date:message-id:subject:to
:cc; bh=2d6jz69g+m4/TVlBzY4cr8NGEwYs0tflwwOPWHW2RBY=;
b=buNS/Tn4M8w8LNlWajkHodMiybmbyaBzslZRAAcu/20o2q0NBj40AXQ0v2x5eq6FDk
9NA5cchqq0NsqkLyImyKcEYxmgvyAal8or+dlGzMrRqbpMMQ02JZFZ8oh0oESdqey0Wz
c8H9hJkVDT53IBVQdaweDFkVEk+/mIe9PpSrSTB22FnWoNgvCTkwEKF+1/8QkTVQNB4I
gfjiWqT98DNJRjLWVLmF/VNbUepV48dPPEd9IkVXb7U78qmgegzlyaTZRuey1jN+lB1a
PQSCINqx7DmrkFvRbBInti7nw15XS0lyXyAw2wXwLnwe3PKilZgXRvZXKI9fBSeN8ml1
9Yyw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:references:in-reply-to:from:date
:message-id:subject:to:cc;
bh=2d6jz69g+m4/TVlBzY4cr8NGEwYs0tflwwOPWHW2RBY=;
b=sxPTBBIb6R9ICtIjlfIakPMkqBjUIIe/KHbPIub5typYNu2rx1k8s6bR9JBS/TNB3G
Oa25L7d3J43Fc7v/M9SNly/GJyhZUhCjTJtFJvCQHEYwQxxv276rcpkqSCPBxCtX8YN0
H5rEDJMSmEn9EzD7orG0GLxJ81y4CIankr7sKqtIKgfjn4/NcuKW5vlb1uon6Juzq1tx
GREKmgAce2sKtNhs8ThrstRHCWrVh4J646+b2Do6XJjqckqByrVm4DiAUCzdVl3VGS3d
ZI7XEop6bEPY06OS9EZx63yhSPg1DJnHBMeNYrlr0Shw7t+f487HeCBV3wLdozs1vmnj
zhrQ==
X-Gm-Message-State: AOAM530nQEkyqS/ma8CJWKKcjH+aNyHwvoKeVowAJV1N8busEjLVGUEZ
OSYxuNAD63udJa8mZScPNnfzA5n24AvL419UBbs=
X-Google-Smtp-Source: ABdhPJxVGZQZ2IHAe2TA7Z8UmNVUfANd5W25Alsa9tKMhkGQtVt221KouMprAcEE5Pt0uC4yU/UxYVa+uOrT1UhyUOU=
X-Received: by 2002:a17:906:369a:: with SMTP id
a26mr4551693ejc.539.1630680063114;
Fri, 03 Sep 2021 07:41:03 -0700 (PDT)
MIME-Version: 1.0
References: <CO1PR05MB8088C1596C134FE2958CF5D1C7CC9@CO1PR05MB8088.namprd05.prod.outlook.com>
<202109010536357895706@zte.com.cn>
In-Reply-To: <202109010536357895706@zte.com.cn>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Fri, 3 Sep 2021 07:40:50 -0700
Message-ID: <CA+RyBmVsXK=2g83faPokxhhGp4EOVJ1aK9jPeDzzOZqFsESMfw@mail.gmail.com>
To: "Bocci, Matthew (Nokia - GB)" <matthew.bocci@nokia.com>,
BESS <bess@ietf.org>
Cc: John E Drake <jdrake=40juniper.net@dmarc.ietf.org>,
sajassi=40cisco.com@dmarc.ietf.org,
draft-ietf-bess-evpn-lsp-ping@ietf.org,
Greg Mirsky <gregory.mirsky@ztetx.com>
Content-Type: multipart/related; boundary="000000000000e8004c05cb184939"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/jA9ym_EPso2ULioPD2puEW_WjIE>
Subject: Re: [bess] Implementation poll for draft-ietf-bess-evpn-lsp-ping-05
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>,
<mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>,
<mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Sep 2021 14:41:11 -0000
Hi Matthew and BESS WG, I was informed that our product does support using most of the sub-TLVs defined in the draft. Please let me know if you have any further questions regarding the implementation. Regards, Greg On Tue, Aug 31, 2021 at 2:36 PM <gregory.mirsky@ztetx.com> wrote: > Hi Matthew, > > my apologies for the belated response: > > 1. > > I am still awaiting a response from our product team on whether any > part of the draft is supported. > 2. > > I concur with Ali. LSP Ping is a broadly used OAM tool detecting and > localizing failures, including discrepancies between the data and control > planes. The document defines necessary Target FEC sub-TLVs for EVPN and > MVPN cases. > > > Regards, > > Greg Mirsky > > > Sr. Standardization Expert > 预研标准部/有线研究院/有线产品经营部 Standard Preresearch Dept./Wireline Product R&D > Institute/Wireline Product Operation Division > > > > E: gregory.mirsky@ztetx.com > www.zte.com.cn > Original Mail > *Sender: *JohnEDrake > *To: *Ali Sajassi (sajassi);Bocci, Matthew (Nokia - GB);bess@ietf.org; > draft-ietf-bess-evpn-lsp-ping@ietf.org; > *Date: *2021/08/31 11:34 > *Subject: **Re: [bess] Implementation poll for > draft-ietf-bess-evpn-lsp-ping-05* > _______________________________________________ > BESS mailing list > BESS@ietf.org > https://www.ietf.org/mailman/listinfo/bess > > Hi, > > > > I agree with Ali. > > > > Yours Irrespectively, > > > > John > > > > > > Juniper Business Use Only > > *From:* BESS <bess-bounces@ietf.org> *On Behalf Of * Ali Sajassi (sajassi) > *Sent:* Friday, August 27, 2021 9:54 PM > *To:* Bocci, Matthew (Nokia - GB) <matthew.bocci@nokia.com>om>; bess@ietf.org; > draft-ietf-bess-evpn-lsp-ping@ietf.org > *Subject:* Re: [bess] Implementation poll for > draft-ietf-bess-evpn-lsp-ping-05 > > > > *[External Email. Be cautious of content]* > > > > Hi Matthew, > > > > Some of the co-authors are on PTO and I couldn’t reach them (typical of > the month of August). So, I’d like to get a bit more extension. > > > > Regarding the two questions below: > > 1. > > My company hasn’t implemented it. > 2. > > I do think that we should process with the publication as it describes > how LSP ping can be used to detect data-plane failures for various EVPN > functionality including aliasing, split-horizon filtering using ESI label, > multicast, l2-unicast, l3-unicast, IRB, etc. For MPLS transport tunnel, I > am not aware of any other tool/draft that allows us to do data-plane > failure detection. Thus, I think it is important to proceed with its > publications. > > > > Still I’d like to hear from other co-authors and other people in this > community. > > > > Regards, > > Ali > > > > *From: *Bocci, Matthew (Nokia - GB) <matthew.bocci@nokia.com> > *Date: *Monday, August 9, 2021 at 6:25 AM > *To: *bess@ietf.org <bess@ietf.org>rg>, > draft-ietf-bess-evpn-lsp-ping@ietf.org < > draft-ietf-bess-evpn-lsp-ping@ietf.org> > *Subject: *Implementation poll for draft-ietf-bess-evpn-lsp-ping-05 > > WG and Authors > > Unfortunately I have not seen any responses indicating that there are any > known implementations of this draft. I also did not see any responses to > Stephane's question if we should proceed regardless. > > As per the BESS WG implementation policy ( > https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw/ > <https://urldefense.com/v3/__https:/mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw/__;!!NEt6yMaO-gk!RoQdN1xrngG7wEPSC6AqHesQtzGvBMP82cosyeO0PYZjTGA5JLyFmli4v8nM3No$>), > please can you respond to this email indicating either: > > - That you are aware of any implementations (ideally providing some > details) > - If you are not aware of any, if you think the WG should proceed with the > draft's publication and why. > > I will close this poll on 25th August 2021. > > Regards > > Matthew > > > On 14/06/2021, 17:38, "BESS on behalf of internet-drafts@ietf.org" <bess-bounces@ietf.org > on behalf of internet-drafts@ietf.org> wrote: > > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > This draft is a work item of the BGP Enabled ServiceS WG of the IETF. > > Title : LSP-Ping Mechanisms for EVPN and PBB-EVPN > Authors : Parag Jain > Samer Salam > Ali Sajassi > Sami Boutros > Greg Mirsky > Filename : draft-ietf-bess-evpn-lsp-ping-05.txt > Pages : 15 > Date : 2021-06-14 > > Abstract: > LSP-Ping is a widely deployed Operation, Administration, and > Maintenance (OAM) mechanism in MPLS networks. This document > describes mechanisms for detecting data-plane failures using LSP > Ping > in MPLS based EVPN and PBB-EVPN networks. > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-lsp-ping/ > <https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/draft-ietf-bess-evpn-lsp-ping/__;!!NEt6yMaO-gk!RoQdN1xrngG7wEPSC6AqHesQtzGvBMP82cosyeO0PYZjTGA5JLyFmli4CFZvJAM$> > > There is also an htmlized version available at: > https://datatracker.ietf.org/doc/html/draft-ietf-bess-evpn-lsp-ping-05 > <https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/html/draft-ietf-bess-evpn-lsp-ping-05__;!!NEt6yMaO-gk!RoQdN1xrngG7wEPSC6AqHesQtzGvBMP82cosyeO0PYZjTGA5JLyFmli4RLT2-5Q$> > > A diff from the previous version is available at: > https://www.ietf.org/rfcdiff?url2=draft-ietf-bess-evpn-lsp-ping-05 > <https://urldefense.com/v3/__https:/www.ietf.org/rfcdiff?url2=draft-ietf-bess-evpn-lsp-ping-05__;!!NEt6yMaO-gk!RoQdN1xrngG7wEPSC6AqHesQtzGvBMP82cosyeO0PYZjTGA5JLyFmli44UwE5yg$> > > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > <https://urldefense.com/v3/__ftp:/ftp.ietf.org/internet-drafts/__;!!NEt6yMaO-gk!RoQdN1xrngG7wEPSC6AqHesQtzGvBMP82cosyeO0PYZjTGA5JLyFmli4trDqUTY$> > > > _______________________________________________ > BESS mailing list > BESS@ietf.org > https://www.ietf.org/mailman/listinfo/bess > <https://urldefense.com/v3/__https:/www.ietf.org/mailman/listinfo/bess__;!!NEt6yMaO-gk!RoQdN1xrngG7wEPSC6AqHesQtzGvBMP82cosyeO0PYZjTGA5JLyFmli4YoTqkAc$> > > >
- [bess] Implementation poll for draft-ietf-bess-ev… Bocci, Matthew (Nokia - GB)
- Re: [bess] Implementation poll for draft-ietf-bes… Ali Sajassi (sajassi)
- Re: [bess] Implementation poll for draft-ietf-bes… John E Drake
- Re: [bess] Implementation poll for draft-ietf-bes… gregory.mirsky
- Re: [bess] Implementation poll for draft-ietf-bes… Gyan Mishra
- Re: [bess] Implementation poll for draft-ietf-bes… Rabadan, Jorge (Nokia - US/Mountain View)
- Re: [bess] Implementation poll for draft-ietf-bes… Dikshit, Saumya
- Re: [bess] Implementation poll for draft-ietf-bes… Parag Jain (paragj)
- Re: [bess] Implementation poll for draft-ietf-bes… Samer Salam (ssalam)
- Re: [bess] Implementation poll for draft-ietf-bes… Greg Mirsky
- Re: [bess] [**EXTERNAL**] Re: Implementation poll… Boutros, Sami
- Re: [bess] [**EXTERNAL**] Re: Implementation poll… Boutros, Sami
- Re: [bess] Implementation poll for draft-ietf-bes… Bocci, Matthew (Nokia - GB)
- Re: [bess] Implementation poll for draft-ietf-bes… Dikshit, Saumya
- Re: [bess] Implementation poll for draft-ietf-bes… Bocci, Matthew (Nokia - GB)