Thank you, this has been acknowledged. Please update MEF internally to Mplify or Mplify Alliance as per below.
As of 24 June 2025, MEF Forum has rebranded as Mplify Alliance. Please find the official press release attached for your reference. Going forward, all references to the organization should be updated from "MEF" to "Mplify" or from the legal name "MEF Forum" to "Mplify Alliance". The updated domain for Mplify Alliance is https://www.mplify.net<https://www.mplify.net/> Please direct future liaison communications to: * Mplify Liaisons - [email protected]<mailto:[email protected]> Branding guidelines and logos can be found on the Mplify Wiki: https://wiki.mplify.net/display/MKT/Mplify+Brand+Center (if you need access, contact [email protected]<mailto:[email protected]> ) Standards Naming Update * Standards published prior to 24 June will retain their original MEF numbering (e.g. MEF 10.4) * New standards released after 24 June will be issued under the Mplify brand (e.g. Mplify 110 or Mplify 80.0.1) The complete library of current and archived standards can be found here: https://www.mplify.net/learn/technical-standards-sdks/ Examples of references: * MEF 10.4, Subscriber Ethernet Service Attributes, Mplify Alliance, December 2018 * Mplify 110, Product Offering Availability and Pricing Discovery - Business Requirements and Use Cases, June 2025 * Mplify 80.0.1, Amendment to MEF 80: Quote Management Requirements and Use Cases, June 2025 The next meeting of Mplify's Committees, whose structure and mandates are unchanged, will be at GNE, 10-14 November, Dallas, Texas, USA. For further event details see: https://GNE.mplify.net<https://gne.mplify.net/> On behalf of the Committee co-Chairs and the Mplify Alliance, Mplify Alliance 12130 Millennium Dr Suite 2-167 Los Angeles, CA 90094 Phone: +1 310 642 2800<tel:3106422800> From: Liaison Statement Management Tool <[email protected]> Date: Wednesday, September 24, 2025 at 11:44 To: Mplify Liaisons <[email protected]> Cc: BGP Enabled Services <[email protected]>, Gunter Van de Velde <[email protected]>, Inter-Domain Routing <[email protected]>, Jim Guichard <[email protected]>, Ketan Talaulikar <[email protected]>, Routing Area Working Group <[email protected]>, [email protected] <[email protected]> Subject: New Liaison Statement, "Liaison Statement from the IETF Routing Area to Mplify on SD-WAN Related Work" Title: Liaison Statement from the IETF Routing Area to Mplify on SD-WAN Related Work Submission Date: 2025-09-24 URL of the IETF Web page: https://datatracker.ietf.org/liaison/2066/ To: MEF From: Routing Area (rtg) Purpose: For information Email Addresses --------------- From: [email protected] To: [email protected] Cc: Gunter Van de Velde <[email protected]>,Ketan Talaulikar <[email protected]>,Jim Guichard <[email protected]>,Inter-Domain Routing <[email protected]>,BGP Enabled Services <[email protected]>,Routing Area Working Group <[email protected]> Response Contacts: Jim Guichard <[email protected]>,Gunter Van de Velde <[email protected]>,Ketan Talaulikar <[email protected]> Technical Contacts: Body: Dear Mplify colleagues, On behalf of the IETF Routing Area, we would like to inform you that several SD-WAN related documents have been adopted as Working Group drafts within the IETF. This liaison is provided for information and to invite your review and feedback, with the objective of ensuring that Mplify considerations are taken into account in the ongoing work. draft-ietf-bess-bgp-sdwan-usage (Now under WG last call in BESS WG - [email protected]) Abstract: This document explores the complexities involved in managing large scale Software Defined WAN (SD-WAN) overlay networks, along with various SD-WAN scenarios. Its objective is to illustrate how a BGP-based control plane can effectively manage these overlay networks by distributing edge service reachability information, WAN port attributes, and underlay path details, thereby minimizing manual provisioning. draft-ietf-idr-sdwan-edge-discovery (WG document in IDR WG - [email protected]) Abstract: The document describes the BGP mechanisms for SD-WAN (Software Defined Wide Area Network) edge node attribute discovery. These mechanisms include a new tunnel type and sub-TLVs for the BGP Tunnel-Encapsulation Attribute [RFC9012] and set of NLRI (network layer reachability information) for SD-WAN underlay information. In the context of this document, BGP Route Reflector (RR) is the component of the SD-WAN Controller that receives the BGP UPDATE from SD-WAN edges and in turn propagates the information to the intended peers that are authorized to communicate via the SD-WAN overlay network. draft-ietf-rtgwg-multisegment-sdwan (WG document in RTGWG WG - [email protected]) Abstract: This document describes a method for seamlessly interconnecting geographically separated SD-WAN segments via a Cloud Backbone without requiring Cloud Gateways (GWs) to decrypt and re-encrypt traffic. By encapsulating IPsec-encrypted payloads within GENEVE headers (RFC 8926), the approach enables Cloud GWs to forward encrypted traffic directly between distant Customer Premises Equipment (CPEs). This reduces processing overhead, improves scalability, and preserves the confidentiality of enterprise data while ensuring secure and efficient multi-segment SD-WAN connectivity. Feedback from Mplify would be valuable to ensure broad applicability and alignment across industry activities. In particular, timely input during the Working Group Last Calls and subsequent IETF Last Calls is especially important, as it ensures that comments can be fully considered and incorporated before the documents advance further in the publication process. We invite Mplify participants to review these documents and provide comments on the relevant WG mailing lists as indicated against each of the documents. Participation in IETF mailing lists is open, and we welcome your input. Sincerely, Gunter Van de Velde Ketan Talaulikar Jim Guichard IETF Routing Area Directors Attachments: No document has been attached
_______________________________________________ rtgwg mailing list -- [email protected] To unsubscribe send an email to [email protected]
