Re: [bess] Coverage of ERL label within LSP-Ping Mechanisms for EVPN
Hi Ali, Thank you for this email. We will surely provide our input for the LSP Ping draft ASAP, had we not done it already. I will touch base with Alexander Vainshtein who claims to have found several issues and return back with our input if not shared already. When LSP Ping becomes RFC; surely we will not issue an errata for EVPN FRR before the latter becomes a formal WG draft. We are on the same page. Much obliged, Nitsan From: Ali Sajassi (sajassi) Sent: Thursday, May 18, 2023 8:08 PM To: Nitsan Dolev ; bess@ietf.org; Parag Jain (paragj) ; Luc Andre Burdet (lburdet) Cc: Alexander Vainshtein ; Ron Sdayoor ; Ali Sajassi (sajassi) Subject: [EXTERNAL] Re: Coverage of ERL label within LSP-Ping Mechanisms for EVPN Hi Nitsan, There are a few other extensions that we have in mind for the bis version which Parag and I want to incorporate. However, we don't want to rush that and want to allow time for the new RFC to soak (just like RFC7432) and gather all inputs before doing a bis. We welcome your input (and your collaboration) on the bis version. BTW, draft-burdet-bess-evpn-fast-reroute-03 is just an individual draft. It is not even WG draft. So, even writing an errata for lsp-ping RFC to cover an individual draft is NOT appropriate! And you should wait till that draft becomes at least a WG draft. Cheers, Ali From: Nitsan Dolev mailto:nitsan.do...@rbbn.com>> Date: Thursday, May 18, 2023 at 12:20 AM To: Ali Sajassi (sajassi) mailto:saja...@cisco.com>>, bess@ietf.org<mailto:bess@ietf.org> mailto:bess@ietf.org>>, Parag Jain (paragj) mailto:par...@cisco.com>>, Luc Andre Burdet (lburdet) mailto:lbur...@cisco.com>> Cc: Alexander Vainshtein mailto:alexander.vainsht...@rbbn.com>>, Ron Sdayoor mailto:ron.sday...@rbbn.com>> Subject: RE: Coverage of ERL label within LSP-Ping Mechanisms for EVPN Hi Ali, Thanks for the prompt response. I will file an errata for the published RFC. And we will draft an extension to it in parallel to progress of draft-burdet-bess-evpn-fast-reroute-03 Much oblige, Nitsan From: Ali Sajassi (sajassi) mailto:saja...@cisco.com>> Sent: Thursday, May 18, 2023 1:41 AM To: Nitsan Dolev mailto:nitsan.do...@rbbn.com>>; bess@ietf.org<mailto:bess@ietf.org>; Parag Jain (paragj) mailto:par...@cisco.com>>; Luc Andre Burdet (lburdet) mailto:lbur...@cisco.com>> Cc: Alexander Vainshtein mailto:alexander.vainsht...@rbbn.com>>; Ron Sdayoor mailto:ron.sday...@rbbn.com>> Subject: [EXTERNAL] Re: Coverage of ERL label within LSP-Ping Mechanisms for EVPN Hi Nitsan, This draft has gone through the WGLC as well as IESG review and we are very close to its publication (i.e., too late to make such changes). Once it is published, we welcome enhancements and expansion to this document when needed. IETF has a formal process of reporting "errata" on a published RFC. We encourage you to file an errata on this. We will compile all such errata and we will address them in the bis version of this document. Cheers, Ali From: BESS mailto:bess-boun...@ietf.org>> on behalf of Nitsan Dolev mailto:nitsan.do...@rbbn.com>> Date: Wednesday, May 17, 2023 at 7:25 AM To: bess@ietf.org<mailto:bess@ietf.org> mailto:bess@ietf.org>>, Parag Jain (paragj) mailto:par...@cisco.com>>, Luc Andre Burdet (lburdet) mailto:lbur...@cisco.com>> Cc: Alexander Vainshtein mailto:alexander.vainsht...@rbbn.com>>, Ron Sdayoor mailto:ron.sday...@rbbn.com>> Subject: Re: [bess] Coverage of ERL label within LSP-Ping Mechanisms for EVPN Dear authors of draft-ietf-bess-evpn-lsp-ping-09 and draft-burdet-bess-evpn-fast-reroute-03, Your help with addressing the following question will be most appreciated, As these two mentioned drafts seem to be under consensus; would not it be right to address the coverage of ERL label should within the LSP Ping enhancement for EVPN. Looking forward to getting your answer, Nitsan Dolev Ribbon Communications Notice: This e-mail together with any attachments may contain information of Ribbon Communications Inc. and its Affiliates that is confidential and/or proprietary for the sole use of the intended recipient. Any review, disclosure, reliance or distribution by others or forwarding without express permission is strictly prohibited. If you are not the intended recipient, please notify the sender immediately and then delete all copies, including any attachments. Notice: This e-mail together with any attachments may contain information of Ribbon Communications Inc. and its Affiliates that is confidential and/or proprietary for the sole use of the intended recipient. Any review, disclosure, reliance or distribution by others or forwarding without express permission is strictly prohibited. If you are not the intended recipient, please notify the sender immediately and then delete all copies, including any attachment
Re: [bess] Coverage of ERL label within LSP-Ping Mechanisms for EVPN
Hi Nitsan, There are a few other extensions that we have in mind for the bis version which Parag and I want to incorporate. However, we don’t want to rush that and want to allow time for the new RFC to soak (just like RFC7432) and gather all inputs before doing a bis. We welcome your input (and your collaboration) on the bis version. BTW, draft-burdet-bess-evpn-fast-reroute-03 is just an individual draft. It is not even WG draft. So, even writing an errata for lsp-ping RFC to cover an individual draft is NOT appropriate! And you should wait till that draft becomes at least a WG draft. Cheers, Ali From: Nitsan Dolev Date: Thursday, May 18, 2023 at 12:20 AM To: Ali Sajassi (sajassi) , bess@ietf.org , Parag Jain (paragj) , Luc Andre Burdet (lburdet) Cc: Alexander Vainshtein , Ron Sdayoor Subject: RE: Coverage of ERL label within LSP-Ping Mechanisms for EVPN Hi Ali, Thanks for the prompt response. I will file an errata for the published RFC. And we will draft an extension to it in parallel to progress of draft-burdet-bess-evpn-fast-reroute-03 Much oblige, Nitsan From: Ali Sajassi (sajassi) Sent: Thursday, May 18, 2023 1:41 AM To: Nitsan Dolev ; bess@ietf.org; Parag Jain (paragj) ; Luc Andre Burdet (lburdet) Cc: Alexander Vainshtein ; Ron Sdayoor Subject: [EXTERNAL] Re: Coverage of ERL label within LSP-Ping Mechanisms for EVPN Hi Nitsan, This draft has gone through the WGLC as well as IESG review and we are very close to its publication (i.e., too late to make such changes). Once it is published, we welcome enhancements and expansion to this document when needed. IETF has a formal process of reporting “errata” on a published RFC. We encourage you to file an errata on this. We will compile all such errata and we will address them in the bis version of this document. Cheers, Ali From: BESS mailto:bess-boun...@ietf.org>> on behalf of Nitsan Dolev mailto:nitsan.do...@rbbn.com>> Date: Wednesday, May 17, 2023 at 7:25 AM To: bess@ietf.org<mailto:bess@ietf.org> mailto:bess@ietf.org>>, Parag Jain (paragj) mailto:par...@cisco.com>>, Luc Andre Burdet (lburdet) mailto:lbur...@cisco.com>> Cc: Alexander Vainshtein mailto:alexander.vainsht...@rbbn.com>>, Ron Sdayoor mailto:ron.sday...@rbbn.com>> Subject: Re: [bess] Coverage of ERL label within LSP-Ping Mechanisms for EVPN Dear authors of draft-ietf-bess-evpn-lsp-ping-09 and draft-burdet-bess-evpn-fast-reroute-03, Your help with addressing the following question will be most appreciated, As these two mentioned drafts seem to be under consensus; would not it be right to address the coverage of ERL label should within the LSP Ping enhancement for EVPN. Looking forward to getting your answer, Nitsan Dolev Ribbon Communications Notice: This e-mail together with any attachments may contain information of Ribbon Communications Inc. and its Affiliates that is confidential and/or proprietary for the sole use of the intended recipient. Any review, disclosure, reliance or distribution by others or forwarding without express permission is strictly prohibited. If you are not the intended recipient, please notify the sender immediately and then delete all copies, including any attachments. Notice: This e-mail together with any attachments may contain information of Ribbon Communications Inc. and its Affiliates that is confidential and/or proprietary for the sole use of the intended recipient. Any review, disclosure, reliance or distribution by others or forwarding without express permission is strictly prohibited. If you are not the intended recipient, please notify the sender immediately and then delete all copies, including any attachments. ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
Re: [bess] Coverage of ERL label within LSP-Ping Mechanisms for EVPN
Hi Ali, Thanks for the prompt response. I will file an errata for the published RFC. And we will draft an extension to it in parallel to progress of draft-burdet-bess-evpn-fast-reroute-03 Much oblige, Nitsan From: Ali Sajassi (sajassi) Sent: Thursday, May 18, 2023 1:41 AM To: Nitsan Dolev ; bess@ietf.org; Parag Jain (paragj) ; Luc Andre Burdet (lburdet) Cc: Alexander Vainshtein ; Ron Sdayoor Subject: [EXTERNAL] Re: Coverage of ERL label within LSP-Ping Mechanisms for EVPN Hi Nitsan, This draft has gone through the WGLC as well as IESG review and we are very close to its publication (i.e., too late to make such changes). Once it is published, we welcome enhancements and expansion to this document when needed. IETF has a formal process of reporting "errata" on a published RFC. We encourage you to file an errata on this. We will compile all such errata and we will address them in the bis version of this document. Cheers, Ali From: BESS mailto:bess-boun...@ietf.org>> on behalf of Nitsan Dolev mailto:nitsan.do...@rbbn.com>> Date: Wednesday, May 17, 2023 at 7:25 AM To: bess@ietf.org<mailto:bess@ietf.org> mailto:bess@ietf.org>>, Parag Jain (paragj) mailto:par...@cisco.com>>, Luc Andre Burdet (lburdet) mailto:lbur...@cisco.com>> Cc: Alexander Vainshtein mailto:alexander.vainsht...@rbbn.com>>, Ron Sdayoor mailto:ron.sday...@rbbn.com>> Subject: Re: [bess] Coverage of ERL label within LSP-Ping Mechanisms for EVPN Dear authors of draft-ietf-bess-evpn-lsp-ping-09 and draft-burdet-bess-evpn-fast-reroute-03, Your help with addressing the following question will be most appreciated, As these two mentioned drafts seem to be under consensus; would not it be right to address the coverage of ERL label should within the LSP Ping enhancement for EVPN. Looking forward to getting your answer, Nitsan Dolev Ribbon Communications Notice: This e-mail together with any attachments may contain information of Ribbon Communications Inc. and its Affiliates that is confidential and/or proprietary for the sole use of the intended recipient. Any review, disclosure, reliance or distribution by others or forwarding without express permission is strictly prohibited. If you are not the intended recipient, please notify the sender immediately and then delete all copies, including any attachments. Notice: This e-mail together with any attachments may contain information of Ribbon Communications Inc. and its Affiliates that is confidential and/or proprietary for the sole use of the intended recipient. Any review, disclosure, reliance or distribution by others or forwarding without express permission is strictly prohibited. If you are not the intended recipient, please notify the sender immediately and then delete all copies, including any attachments.___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
Re: [bess] Coverage of ERL label within LSP-Ping Mechanisms for EVPN
Hi Nitsan, This draft has gone through the WGLC as well as IESG review and we are very close to its publication (i.e., too late to make such changes). Once it is published, we welcome enhancements and expansion to this document when needed. IETF has a formal process of reporting “errata” on a published RFC. We encourage you to file an errata on this. We will compile all such errata and we will address them in the bis version of this document. Cheers, Ali From: BESS on behalf of Nitsan Dolev Date: Wednesday, May 17, 2023 at 7:25 AM To: bess@ietf.org , Parag Jain (paragj) , Luc Andre Burdet (lburdet) Cc: Alexander Vainshtein , Ron Sdayoor Subject: Re: [bess] Coverage of ERL label within LSP-Ping Mechanisms for EVPN Dear authors of draft-ietf-bess-evpn-lsp-ping-09 and draft-burdet-bess-evpn-fast-reroute-03, Your help with addressing the following question will be most appreciated, As these two mentioned drafts seem to be under consensus; would not it be right to address the coverage of ERL label should within the LSP Ping enhancement for EVPN. Looking forward to getting your answer, Nitsan Dolev Ribbon Communications Notice: This e-mail together with any attachments may contain information of Ribbon Communications Inc. and its Affiliates that is confidential and/or proprietary for the sole use of the intended recipient. Any review, disclosure, reliance or distribution by others or forwarding without express permission is strictly prohibited. If you are not the intended recipient, please notify the sender immediately and then delete all copies, including any attachments. ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
Re: [bess] Coverage of ERL label within LSP-Ping Mechanisms for EVPN
Dear authors of draft-ietf-bess-evpn-lsp-ping-09 and draft-burdet-bess-evpn-fast-reroute-03, Your help with addressing the following question will be most appreciated, As these two mentioned drafts seem to be under consensus; would not it be right to address the coverage of ERL label should within the LSP Ping enhancement for EVPN. Looking forward to getting your answer, Nitsan Dolev Ribbon Communications Notice: This e-mail together with any attachments may contain information of Ribbon Communications Inc. and its Affiliates that is confidential and/or proprietary for the sole use of the intended recipient. Any review, disclosure, reliance or distribution by others or forwarding without express permission is strictly prohibited. If you are not the intended recipient, please notify the sender immediately and then delete all copies, including any attachments.___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
