Ketan Talaulikar has entered the following ballot position for draft-ietf-bess-bgp-sdwan-usage-36: Abstain
When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ for more information about how to handle DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-bess-bgp-sdwan-usage/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Thanks to the authors and the WG for their work on this document. I appreciate the responsiveness from the authors (specifically Linda) in addressing most of the technical comments in my original ballot with DISCUSS position. There are multiple SD-WAN solutions that have been developed by various vendors using IETF technologies like BGP (but with proprietary extensions) or entirely proprietary solutions. I welcome the use of IETF protocols. However, AFAIK, none of these solutions support interoperability between SD-WAN gateways and controllers from different vendors. So, I wonder where and how the standardization of SD-WAN at the IETF is happening to enable such interoperability. After all the goal of IETF standardization is interoperability. Also, the BGP extensions are but a small portion of what an SD-WAN solution entails (some of this is now clarified in the document). There is no SD-WAN WG that is chartered today to study and undertake the work necessary for a standards based open and interoperable SD-WAN solution. Without that in place, I do not understand the value or benefit of publication of this document via the IETF stream. It could as well be via ISE? That said, I am moving my position to Abstain since I do not wish to stand in the way of publication of this document that has taken years through the BESS WG and IETF consensus process. _______________________________________________ BESS mailing list -- [email protected] To unsubscribe send an email to [email protected]
