I support adoption of this document. A separate SAFI and unique signaling is required to handle the unique requirements of the use case.
Thanks, Acee > On Nov 7, 2025, at 1:27 PM, Matthew Bocci via Datatracker <[email protected]> > wrote: > > > 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] _______________________________________________ BESS mailing list -- [email protected] To unsubscribe send an email to [email protected]
