As a WG member providing operators feedback, I agree with Ali that we should proceed with publication. I support progression of this draft.
As Greg has noted that LSP OAM ping has been utilized as a critical tool for operations in data plane troubleshooting of control plane against data plane failures. This document describes a critical mechanism for operators to detect data plane failures using the same LSP ping widely used, now being applied to MPLS or SR-MPLS based NG L2 VPN EVPN & PBB-EVPN using 4 new FEC Stack Sub TLVs, EVPN MAC/IP Sub TLV for EVPN Type 2 advertisements, EVPN I-PMSI inclusive P-Tree for EVPN Type 3 advertisement, EVPN Auto discovery Sub TLV for EVPN Type 1 AD advertisement and finally EVPN IP Prefix Sub TLV for EVPN Type 5 advertisement. Kind Regards Gyan Verizon On Tue, Aug 31, 2021 at 5:36 PM <gregory.mir...@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.mir...@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-p...@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-boun...@ietf.org> *On Behalf Of * Ali Sajassi (sajassi) > *Sent:* Friday, August 27, 2021 9:54 PM > *To:* Bocci, Matthew (Nokia - GB) <matthew.bo...@nokia.com>; bess@ietf.org; > draft-ietf-bess-evpn-lsp-p...@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.bo...@nokia.com> > *Date: *Monday, August 9, 2021 at 6:25 AM > *To: *bess@ietf.org <bess@ietf.org>, > draft-ietf-bess-evpn-lsp-p...@ietf.org < > draft-ietf-bess-evpn-lsp-p...@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-dra...@ietf.org" > <bess-boun...@ietf.org > on behalf of internet-dra...@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 mailing list > BESS@ietf.org > https://www.ietf.org/mailman/listinfo/bess > -- <http://www.verizon.com/> *Gyan Mishra* *Network Solutions A**rchitect * *Email gyan.s.mis...@verizon.com <gyan.s.mis...@verizon.com>* *M 301 502-1347*
_______________________________________________ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
