Re: [bess] Implementation poll for draft-ietf-bess-evpn-lsp-ping-05
Thank you. I believe we have consensus to publish the document. Please look out for the document shepherd write-up and publication request. Best regards Matthew From: Dikshit, Saumya Date: Wednesday, 13 October 2021 at 05:14 To: Bocci, Matthew (Nokia - GB) , Greg Mirsky , BESS Cc: Greg Mirsky , sajassi=40cisco@dmarc.ietf.org , draft-ietf-bess-evpn-lsp-p...@ietf.org , John E Drake Subject: RE: [bess] Implementation poll for draft-ietf-bess-evpn-lsp-ping-05 Hi Mathew, +1 on going ahead with this draft. As Greg suggested in the other thread, we can draft an extension to include the new proposal. Thanks Saumya. From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Bocci, Matthew (Nokia - GB) Sent: Tuesday, October 12, 2021 2:17 PM To: Greg Mirsky ; BESS Cc: Greg Mirsky ; sajassi=40cisco@dmarc.ietf.org; draft-ietf-bess-evpn-lsp-p...@ietf.org; John E Drake Subject: Re: [bess] Implementation poll for draft-ietf-bess-evpn-lsp-ping-05 Greg Thank you I am good to close the implementation poll, but I believe there may be some outstanding comments to address from Saumya on the other thread. Please can you look at that? Thanks Matthew From: Greg Mirsky mailto:gregimir...@gmail.com>> Date: Friday, 3 September 2021 at 15:41 To: Bocci, Matthew (Nokia - GB) mailto:matthew.bo...@nokia.com>>, BESS mailto:bess@ietf.org>> Cc: John E Drake mailto:jdrake=40juniper@dmarc.ietf.org>>, sajassi=40cisco@dmarc.ietf.org<mailto:sajassi=40cisco@dmarc.ietf.org> mailto:sajassi=40cisco@dmarc.ietf.org>>, draft-ietf-bess-evpn-lsp-p...@ietf.org<mailto:draft-ietf-bess-evpn-lsp-p...@ietf.org> mailto:draft-ietf-bess-evpn-lsp-p...@ietf.org>>, Greg Mirsky mailto:gregory.mir...@ztetx.com>> Subject: Re: [bess] Implementation poll for draft-ietf-bess-evpn-lsp-ping-05 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 mailto: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 Institute/Wireline Product Operation Division [cid:image001.gif@01D7C01D.0563F360] [cid:image002.gif@01D7C01D.0563F360] E: gregory.mir...@ztetx.com<mailto:gregory.mir...@ztetx.com> www.zte.com.cn<http://www.zte.com.cn/> Original Mail Sender: JohnEDrake To: Ali Sajassi (sajassi);Bocci, Matthew (Nokia - GB);bess@ietf.org<mailto:bess@ietf.org>;draft-ietf-bess-evpn-lsp-p...@ietf.org<mailto: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<mailto:BESS@ietf.org> https://www.ietf.org/mailman/listinfo/bess Hi, I agree with Ali. Yours Irrespectively, John Juniper Business Use Only From: BESS mailto:bess-boun...@ietf.org>> On Behalf Of Ali Sajassi (sajassi) Sent: Friday, August 27, 2021 9:54 PM To: Bocci, Matthew (Nokia - GB) mailto:matthew.bo...@nokia.com>>; bess@ietf.org<mailto:bess@ietf.org>; draft-ietf-bess-evpn-lsp-p...@ietf.org<mailto: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) mailto:matthew.bo...@nokia.com>> Date: Monday, August 9, 2021 at 6:25 AM To: bess@ietf.org<mailto:bess@ietf.org> mailto:bess@ietf.org>>, draft-ietf-bess-evpn-lsp-p...@ietf.org<mailto:draft-ietf-bess-evpn-lsp-p...@ietf.org> mailto:
Re: [bess] Implementation poll for draft-ietf-bess-evpn-lsp-ping-05
Hi Mathew, +1 on going ahead with this draft. As Greg suggested in the other thread, we can draft an extension to include the new proposal. Thanks Saumya. From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Bocci, Matthew (Nokia - GB) Sent: Tuesday, October 12, 2021 2:17 PM To: Greg Mirsky ; BESS Cc: Greg Mirsky ; sajassi=40cisco@dmarc.ietf.org; draft-ietf-bess-evpn-lsp-p...@ietf.org; John E Drake Subject: Re: [bess] Implementation poll for draft-ietf-bess-evpn-lsp-ping-05 Greg Thank you I am good to close the implementation poll, but I believe there may be some outstanding comments to address from Saumya on the other thread. Please can you look at that? Thanks Matthew From: Greg Mirsky mailto:gregimir...@gmail.com>> Date: Friday, 3 September 2021 at 15:41 To: Bocci, Matthew (Nokia - GB) mailto:matthew.bo...@nokia.com>>, BESS mailto:bess@ietf.org>> Cc: John E Drake mailto:jdrake=40juniper@dmarc.ietf.org>>, sajassi=40cisco@dmarc.ietf.org<mailto:sajassi=40cisco@dmarc.ietf.org> mailto:sajassi=40cisco@dmarc.ietf.org>>, draft-ietf-bess-evpn-lsp-p...@ietf.org<mailto:draft-ietf-bess-evpn-lsp-p...@ietf.org> mailto:draft-ietf-bess-evpn-lsp-p...@ietf.org>>, Greg Mirsky mailto:gregory.mir...@ztetx.com>> Subject: Re: [bess] Implementation poll for draft-ietf-bess-evpn-lsp-ping-05 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 mailto: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 Institute/Wireline Product Operation Division [cid:image001.gif@01D7C016.D9BF37C0] [cid:image002.gif@01D7C016.D9BF37C0] E: gregory.mir...@ztetx.com<mailto:gregory.mir...@ztetx.com> www.zte.com.cn<http://www.zte.com.cn/> Original Mail Sender: JohnEDrake To: Ali Sajassi (sajassi);Bocci, Matthew (Nokia - GB);bess@ietf.org<mailto:bess@ietf.org>;draft-ietf-bess-evpn-lsp-p...@ietf.org<mailto: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<mailto:BESS@ietf.org> https://www.ietf.org/mailman/listinfo/bess<https://www.ietf.org/mailman/listinfo/bess> Hi, I agree with Ali. Yours Irrespectively, John Juniper Business Use Only From: BESS mailto:bess-boun...@ietf.org>> On Behalf Of Ali Sajassi (sajassi) Sent: Friday, August 27, 2021 9:54 PM To: Bocci, Matthew (Nokia - GB) mailto:matthew.bo...@nokia.com>>; bess@ietf.org<mailto:bess@ietf.org>; draft-ietf-bess-evpn-lsp-p...@ietf.org<mailto: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) mailto:matthew.bo...@nokia.com>> Date: Monday, August 9, 2021 at 6:25 AM To: bess@ietf.org<mailto:bess@ietf.org> mailto:bess@ietf.org>>, draft-ietf-bess-evpn-lsp-p...@ietf.org<mailto:draft-ietf-bess-evpn-lsp-p...@ietf.org> mailto: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/cG
Re: [bess] Implementation poll for draft-ietf-bess-evpn-lsp-ping-05
Greg Thank you I am good to close the implementation poll, but I believe there may be some outstanding comments to address from Saumya on the other thread. Please can you look at that? Thanks Matthew From: Greg Mirsky Date: Friday, 3 September 2021 at 15:41 To: Bocci, Matthew (Nokia - GB) , BESS Cc: John E Drake , sajassi=40cisco@dmarc.ietf.org , draft-ietf-bess-evpn-lsp-p...@ietf.org , Greg Mirsky Subject: Re: [bess] Implementation poll for draft-ietf-bess-evpn-lsp-ping-05 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 mailto: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 Institute/Wireline Product Operation Division [cid:image001.gif@01D7BF4E.0D139360] [cid:image002.gif@01D7BF4E.0D139360] E: gregory.mir...@ztetx.com<mailto:gregory.mir...@ztetx.com> www.zte.com.cn<http://www.zte.com.cn/> Original Mail Sender: JohnEDrake To: Ali Sajassi (sajassi);Bocci, Matthew (Nokia - GB);bess@ietf.org<mailto:bess@ietf.org>;draft-ietf-bess-evpn-lsp-p...@ietf.org<mailto: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<mailto:BESS@ietf.org> https://www.ietf.org/mailman/listinfo/bess Hi, I agree with Ali. Yours Irrespectively, John Juniper Business Use Only From: BESS mailto:bess-boun...@ietf.org>> On Behalf Of Ali Sajassi (sajassi) Sent: Friday, August 27, 2021 9:54 PM To: Bocci, Matthew (Nokia - GB) mailto:matthew.bo...@nokia.com>>; bess@ietf.org<mailto:bess@ietf.org>; draft-ietf-bess-evpn-lsp-p...@ietf.org<mailto: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) mailto:matthew.bo...@nokia.com>> Date: Monday, August 9, 2021 at 6:25 AM To: bess@ietf.org<mailto:bess@ietf.org> mailto:bess@ietf.org>>, draft-ietf-bess-evpn-lsp-p...@ietf.org<mailto:draft-ietf-bess-evpn-lsp-p...@ietf.org> mailto: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<mailto:internet-dra...@ietf.org>" mailto:bess-boun...@ietf.org%20on%20behalf%20of%20internet-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-Pi
Re: [bess] Implementation poll for draft-ietf-bess-evpn-lsp-ping-05
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 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 > 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 *On Behalf Of * Ali Sajassi (sajassi) > *Sent:* Friday, August 27, 2021 9:54 PM > *To:* Bocci, Matthew (Nokia - GB) ; 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) > *Date: *Monday, August 9, 2021 at 6:25 AM > *To: *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" > 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 > > A
Re: [bess] Implementation poll for draft-ietf-bess-evpn-lsp-ping-05
Hi Matthew, As others have indicated, this draft defines necessary mechanisms to apply LSP-Ping to EVPN, and provides much needed OAM capabilities. I believe we should proceed with publication. Thank you, Samer On 8/9/21, 4:25 PM, "Bocci, Matthew (Nokia - GB)" wrote: 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/), 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" 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/ There is also an htmlized version available at: https://datatracker.ietf.org/doc/html/draft-ietf-bess-evpn-lsp-ping-05 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-bess-evpn-lsp-ping-05 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
Re: [bess] Implementation poll for draft-ietf-bess-evpn-lsp-ping-05
Hi Matthew, Cisco does not have a shipping implementation of the draft. As Ali and many other experts replied, LSP ping is widely used for detecting data plane failures in mpls network. This draft defines necessary Target FEC sub-TLVs for EVPN and I think this is an important draft that should proceed with publication. Thanks Parag On 2021-08-09, 9:25 AM, "Bocci, Matthew (Nokia - GB)" wrote: 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/), 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" 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/ There is also an htmlized version available at: https://datatracker.ietf.org/doc/html/draft-ietf-bess-evpn-lsp-ping-05 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-bess-evpn-lsp-ping-05 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
Re: [bess] Implementation poll for draft-ietf-bess-evpn-lsp-ping-05
I have following queries regarding this draft: >>>> Do we intend-to-use/call-out-usage-of “wild-card/don’t-care” values for >>>> attributes carried in the sub-TLVs ? For example, If the admin intends to check the reachability to host (MAC_X/IP_X) published (in route-type-2) by remote PE. The remote PE learnt it locally over ESI_X against Vlan X (mapped to BD_XYZ). Is it possible, that the “EVPN MAC sub-tlv” can carry the “Route Distinguisher” and “Ethernet Segment Identifier” as don’t care. >>>> Another caseto handle would be test the reachability to tenant-VRF VRF_X >>>> (with EVPN mapped EVI) configured on the remote PE, PE1. VRF_X has no active IP/IPv6 interface configured and its sole usage is to obtain the leaked (via IVRL) routes from other VRFs (non-EVPN) and PE1 published this to other peers via EVPN control plane. Till the first prefix (learnt ) route is published (Route Type 5) by PE1 for the EVI (mapped to VRF_X), the tunnels will not be provisioned on other PEs. In order to test the reachability to VRF_X (on PE1) from another PEs, let’s say, PE2 or a centralized-controller (which can emulate/supports MPLS), It may need to carry all/subset-of attributes with “don’t-care/wild-card” in “EVPN IP Prefix Sub-TLV”. Please let know your thoughts on above. Thanks Saumya. From: BESS [mailto:bess-boun...@ietf.org] On Behalf Of Gyan Mishra Sent: Wednesday, September 1, 2021 11:26 AM To: gregory.mir...@ztetx.com Cc: matthew.bo...@nokia.com; sajassi=40cisco@dmarc.ietf.org; draft-ietf-bess-evpn-lsp-p...@ietf.org; jdrake=40juniper....@dmarc.ietf.org; bess@ietf.org Subject: Re: [bess] Implementation poll for draft-ietf-bess-evpn-lsp-ping-05 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 mailto: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 Institute/Wireline Product Operation Division [cid:image001.gif@01D79F59.CAE267A0] [cid:image002.gif@01D79F59.CAE267A0] E: gregory.mir...@ztetx.com<mailto:gregory.mir...@ztetx.com> www.zte.com.cn<http://www.zte.com.cn/> Original Mail Sender: JohnEDrake To: Ali Sajassi (sajassi);Bocci, Matthew (Nokia - GB);bess@ietf.org<mailto:bess@ietf.org>;draft-ietf-bess-evpn-lsp-p...@ietf.org<mailto: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<mailto:BESS@ietf.org> https://www.ietf.org/mailman/listinfo/bess<https://www.ietf.org/mailman/listinfo/bess> Hi, I agree with Ali. Yours Irrespectively, John Juniper Business Use Only From: BESS mailto:bess-boun...@ietf.org>> On Behalf Of Ali Sajassi (sajassi) Sent: Friday, August 27, 2021 9:54 PM To: Bocci, Matthew (Nokia - GB) mailto:matthew.bo...@nokia.com>>; bess@ietf.org<mailto:bess@ietf.org>; draft-ietf-bess-evpn-lsp-p...@ietf.org<mailto: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 awar
Re: [bess] Implementation poll for draft-ietf-bess-evpn-lsp-ping-05
Ali’s reasoning makes sense to me too. Thanks. Jorge From: BESS on behalf of gregory.mir...@ztetx.com Date: Tuesday, August 31, 2021 at 11:37 PM To: jdrake=40juniper@dmarc.ietf.org Cc: Bocci, Matthew (Nokia - GB) , sajassi=40cisco@dmarc.ietf.org , draft-ietf-bess-evpn-lsp-p...@ietf.org , bess@ietf.org Subject: Re: [bess] Implementation poll for draft-ietf-bess-evpn-lsp-ping-05 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 Institute/Wireline Product Operation Division [cid:image001.gif@01D79F54.64C30290] [cid:image002.gif@01D79F54.64C30290] E: gregory.mir...@ztetx.com<mailto:gregory.mir...@ztetx.com> www.zte.com.cn<http://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 On Behalf Of Ali Sajassi (sajassi) Sent: Friday, August 27, 2021 9:54 PM To: Bocci, Matthew (Nokia - GB) ; 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) mailto:matthew.bo...@nokia.com>> Date: Monday, August 9, 2021 at 6:25 AM To: bess@ietf.org<mailto:bess@ietf.org> mailto:bess@ietf.org>>, draft-ietf-bess-evpn-lsp-p...@ietf.org<mailto:draft-ietf-bess-evpn-lsp-p...@ietf.org> mailto: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<mailto:internet-dra...@ietf.org>" mailto:bess-boun...@ietf.org%20on%20behalf%20of%20internet-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
Re: [bess] Implementation poll for draft-ietf-bess-evpn-lsp-ping-05
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 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 > 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 *On Behalf Of * Ali Sajassi (sajassi) > *Sent:* Friday, August 27, 2021 9:54 PM > *To:* Bocci, Matthew (Nokia - GB) ; 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) > *Date: *Monday, August 9, 2021 at 6:25 AM > *To: *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" > on behalf of internet-dra...@ietf.org> wrote: > > > A New Internet-Draft is available from the on-line I
Re: [bess] Implementation poll for draft-ietf-bess-evpn-lsp-ping-05
Hi Matthew, my apologies for the belated response: I am still awaiting a response from our product team on whether any part of the draft is supported. 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 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 On Behalf Of Ali Sajassi (sajassi) Sent: Friday, August 27, 2021 9:54 PM To: Bocci, Matthew (Nokia - GB) ; 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: My company hasn’t implemented it. 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) Date: Monday, August 9, 2021 at 6:25 AM To: bess@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/), 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" 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/ There is also an htmlized version available at: https://datatracker.ietf.org/doc/html/draft-ietf-bess-evpn-lsp-ping-05 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-bess-evpn-lsp-ping-05 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
Re: [bess] Implementation poll for draft-ietf-bess-evpn-lsp-ping-05
Hi, I agree with Ali. Yours Irrespectively, John Juniper Business Use Only From: BESS On Behalf Of Ali Sajassi (sajassi) Sent: Friday, August 27, 2021 9:54 PM To: Bocci, Matthew (Nokia - GB) ; 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) mailto:matthew.bo...@nokia.com>> Date: Monday, August 9, 2021 at 6:25 AM To: bess@ietf.org<mailto:bess@ietf.org> mailto:bess@ietf.org>>, draft-ietf-bess-evpn-lsp-p...@ietf.org<mailto:draft-ietf-bess-evpn-lsp-p...@ietf.org> mailto: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<mailto:internet-dra...@ietf.org>" mailto:bess-boun...@ietf.org%20on%20behalf%20of%20internet-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<mailto: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
Re: [bess] Implementation poll for draft-ietf-bess-evpn-lsp-ping-05
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) Date: Monday, August 9, 2021 at 6:25 AM To: bess@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/), 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" 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/ There is also an htmlized version available at: https://datatracker.ietf.org/doc/html/draft-ietf-bess-evpn-lsp-ping-05 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-bess-evpn-lsp-ping-05 Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
