Hi WG There is consensus to adopt this draft as a BESS WG document.
Authors: Please upload the next revision of the draft as draft-ietf-bess-mup-safi-00. Thanks Matthew From: Satoru Matsushima <[email protected]> Date: Thursday, 20 November 2025 at 11:28 To: [email protected] <[email protected]> Cc: [email protected] <[email protected]>, [email protected] <[email protected]>, Matthew Bocci (Nokia) <[email protected]> Subject: Re: [bess] Call for adoption: draft-mpmz-bess-mup-safi-06 (Ends 2025-11-21) You don't often get email from [email protected]. Learn why this is important<https://aka.ms/LearnAboutSenderIdentification> CAUTION: This is an external email. Please be very careful when clicking links or opening attachments. See the URL nok.it/ext for additional information. Hi all, I support this adoption as a co-author. And I am not aware of any undisclosed IPR on this draft. Best regards, --satoru On Sat, Nov 8, 2025 at 3:28 AM Matthew Bocci via Datatracker <[email protected]<mailto:[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]<mailto:[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]<mailto:[email protected]> To unsubscribe send an email to [email protected]<mailto:[email protected]>
_______________________________________________ BESS mailing list -- [email protected] To unsubscribe send an email to [email protected]
