I support adoption of this document. Derek Yeung [email protected]<mailto:[email protected]> Main: 408.884.1965
[signature_119155375] 2077 Gateway Place, Suite 400 San Jose, CA. 95110 The contents of this message, together with any attachments, are intended only for the use of the individual or entity to which they are addressed and may contain information that is confidential and proprietary to Arrcus. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this message, or any attachment, is strictly prohibited. If you have received this message in error, please notify the original sender immediately by telephone or by return E-mail and delete this message, along with any attachments, from your computer. Thank you. From: Matthew Bocci via Datatracker <[email protected]> Date: Friday, November 7, 2025 at 10:28 AM To: [email protected] <[email protected]>, [email protected] <[email protected]>, [email protected] <[email protected]> Subject: [bess] Call for adoption: draft-mpmz-bess-mup-safi-06 (Ends 2025-11-21) Subject: Call for adoption: draft-mpmz-bess-mup-safi-06 (Ends 2025-11-21) This message starts a 2-week Call for Adoption for this document. Abstract: This document defines a new SAFI known as a BGP Mobile User Plane (BGP-MUP) SAFI to support MUP Extensions and a extended community for BGP. This document also provides BGP signaling and procedures for the new SAFI to convert mobile session information into appropriate IP forwarding information. These extensions can be used by operators between a PE, and a Controller for integrating mobile user plane into BGP MUP network using the IP based routing. File can be retrieved from: https://datatracker.ietf.org/doc/draft-mpmz-bess-mup-safi/ Please reply to this message keeping [email protected] in copy by indicating whether you support or not the adoption of this draft as a WG document. Comments to motivate your preference are highly appreciated. Authors, and WG participants in general, are reminded of the Intellectual Property Rights (IPR) disclosure obligations described in BCP 79 [2]. Appropriate IPR disclosures required for full conformance with the provisions of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any. Sanctions available for application to violators of IETF IPR Policy can be found at [3]. Thank you. [1] https://datatracker.ietf.org/doc/bcp78/ [2] https://datatracker.ietf.org/doc/bcp79/ [3] https://datatracker.ietf.org/doc/rfc6701/ _______________________________________________ BESS mailing list -- [email protected] To unsubscribe send an email to [email protected] [EXTERNAL]
_______________________________________________ BESS mailing list -- [email protected] To unsubscribe send an email to [email protected]
