[bess] Re: Call for adoption: draft-mpmz-bess-mup-safi-06 (Ends 2025-11-21)

[Matthew Bocci (Nokia)]

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 
Date: Thursday, 20 November 2025 at 11:28
To: bess@ietf.org 
Cc: bess-cha...@ietf.org , 
draft-mpmz-bess-mup-s...@ietf.org , Matthew 
Bocci (Nokia) 
Subject: Re: [bess] Call for adoption: draft-mpmz-bess-mup-safi-06 (Ends 
2025-11-21)

You don't often get email from satoru.matsush...@gmail.com. Learn why this is 
important

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 
mailto:nore...@ietf.org>> 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 bess@ietf.org 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 -- bess@ietf.org
To unsubscribe send an email to bess-le...@ietf.org
___
BESS mailing list -- bess@ietf.org
To unsubscribe send an email to bess-le...@ietf.org

[bess] Re: Call for adoption: draft-mpmz-bess-mup-safi-06 (Ends 2025-11-21)

[Swadesh Agrawal (swaagraw)]

Hi All,

I support this adoption. And I am not aware of any undisclosed IPR on this 
draft.

Best regards,
Swadesh

From: Matthew Bocci via Datatracker 
Date: Friday, November 7, 2025 at 10:27 AM
To: bess-cha...@ietf.org , bess@ietf.org , 
draft-mpmz-bess-mup-s...@ietf.org 
Subject: 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 bess@ietf.org 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 -- bess@ietf.org
To unsubscribe send an email to bess-le...@ietf.org

[bess] Re: Call for adoption: draft-mpmz-bess-mup-safi-06 (Ends 2025-11-21)

[Krishnaswamy Ananthamurthy (kriswamy)]

I support the WG adoption.

Thanks
Krishna


From: Matthew Bocci via Datatracker 
Date: Friday, November 7, 2025 at 12:28 PM
To: bess-cha...@ietf.org , bess@ietf.org , 
draft-mpmz-bess-mup-s...@ietf.org 
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 bess@ietf.org 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 -- bess@ietf.org
To unsubscribe send an email to bess-le...@ietf.org
___
BESS mailing list -- bess@ietf.org
To unsubscribe send an email to bess-le...@ietf.org

[bess] Re: Call for adoption: draft-mpmz-bess-mup-safi-06 (Ends 2025-11-21)

[Yuya KAWAKAMI]

I support adoption of this document.

Yuya Kawakami

On 2025/11/08 3:27, Matthew Bocci via Datatracker 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 bess@ietf.org 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 -- bess@ietf.org
To unsubscribe send an email to bess-le...@ietf.org


___
BESS mailing list -- bess@ietf.org
To unsubscribe send an email to bess-le...@ietf.org

[bess] Re: Call for adoption: draft-mpmz-bess-mup-safi-06 (Ends 2025-11-21)

[Derek Yeung]

I support adoption of this document.

Derek Yeung
de...@arrcus.com
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 
Date: Friday, November 7, 2025 at 10:28 AM
To: bess-cha...@ietf.org , bess@ietf.org , 
draft-mpmz-bess-mup-s...@ietf.org 
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 bess@ietf.org 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 -- bess@ietf.org
To unsubscribe send an email to bess-le...@ietf.org
[EXTERNAL]
___
BESS mailing list -- bess@ietf.org
To unsubscribe send an email to bess-le...@ietf.org

[bess] Re: Call for adoption: draft-mpmz-bess-mup-safi-06 (Ends 2025-11-21)

[Shengtao Li]

I support adoption of this draft.

Thanks!
Shen
___
BESS mailing list -- bess@ietf.org
To unsubscribe send an email to bess-le...@ietf.org

[bess] Re: Call for adoption: draft-mpmz-bess-mup-safi-06 (Ends 2025-11-21)

[Acee Lindem]

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  
> 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 bess@ietf.org 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 -- bess@ietf.org
> To unsubscribe send an email to bess-le...@ietf.org

___
BESS mailing list -- bess@ietf.org
To unsubscribe send an email to bess-le...@ietf.org

[bess] Re: Call for adoption: draft-mpmz-bess-mup-safi-06 (Ends 2025-11-21)

[Keyur Patel]

Support the adoption as a co-author. I don’t think there are any IPR issues 
related to this draft.

Best Regards,
Keyur

From: Matthew Bocci via Datatracker 
Date: Friday, November 7, 2025 at 10:27 AM
To: bess-cha...@ietf.org , bess@ietf.org , 
draft-mpmz-bess-mup-s...@ietf.org 
Subject: 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 bess@ietf.org 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/



[EXTERNAL]
___
BESS mailing list -- bess@ietf.org
To unsubscribe send an email to bess-le...@ietf.org

[bess] Re: Call for adoption: draft-mpmz-bess-mup-safi-06 (Ends 2025-11-21)

[Tetsuya Murakami]

Hi All,

I support this adoption as a co-author. I don’t think there are any IPR issues 
related to this draft.

Thanks,
Tetsuya

> 11/7/25 午前10:27、Matthew Bocci via Datatracker のメール:
> 
>   IRONSCALES couldn't recognize this email as this is the first time you 
> received an email from this sender noreply @ ietf.org
> 
> 
> 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 bess@ietf.org 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/
> 
> 
> 
> [EXTERNAL]

___
BESS mailing list -- bess@ietf.org
To unsubscribe send an email to bess-le...@ietf.org

[bess] Re: Call for adoption: draft-mpmz-bess-mup-safi-06 (Ends 2025-11-21)

[Satoru Matsushima]

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 <
nore...@ietf.org> 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 bess@ietf.org 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 -- bess@ietf.org
> To unsubscribe send an email to bess-le...@ietf.org
>
___
BESS mailing list -- bess@ietf.org
To unsubscribe send an email to bess-le...@ietf.org

[bess] Re: Call for adoption: draft-mpmz-bess-mup-safi-06 (Ends 2025-11-21)

[Teppei Kamata (tkamata)]

Dear chairs and the WG

I support adoption of the MUP SAFI draft.
Cisco participated at the IETF116 hackathon and interop done with POC code.
https://wiki.ietf.org/en/meeting/116/hackathon

Regards,
Teppei

On 2025/11/08, 3:27, "Matthew Bocci via Datatracker"  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 bess@ietf.org 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 -- bess@ietf.org
To unsubscribe send an email to bess-le...@ietf.org

___
BESS mailing list -- bess@ietf.org
To unsubscribe send an email to bess-le...@ietf.org

[bess] Re: Call for adoption: draft-mpmz-bess-mup-safi-06 (Ends 2025-11-21)

[Gyan Mishra]

I support adoption of the MUP SAFI draft.

Thanks

Gyan

On Fri, Nov 7, 2025 at 1:27 PM Matthew Bocci via Datatracker <
nore...@ietf.org> 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 bess@ietf.org 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 -- bess@ietf.org
> To unsubscribe send an email to bess-le...@ietf.org
>
___
BESS mailing list -- bess@ietf.org
To unsubscribe send an email to bess-le...@ietf.org

[bess] Re: Call for adoption: draft-mpmz-bess-mup-safi-06 (Ends 2025-11-21)

[Zafar Ali (zali)]

Dear chairs and the WG

I support the adoption of this draft.

Thanks

Regards … Zafar


On 11/7/25, 1:27 PM, "Matthew Bocci via Datatracker"  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 bess@ietf.org 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 -- bess@ietf.org
To unsubscribe send an email to bess-le...@ietf.org


Thanks



Regards … Zafar
___
BESS mailing list -- bess@ietf.org
To unsubscribe send an email to bess-le...@ietf.org

[bess] Re: Call for adoption: draft-mpmz-bess-mup-safi-06 (Ends 2025-11-21)

[Dan Voyer (davoyer)]

Hi WG,

As co-author, I'm not aware of any IPR other than the one disclosed.

Thanks,
Dan

On 2025-11-07, 1:27 PM, "Matthew Bocci via Datatracker"  
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 bess@ietf.org 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 -- bess@ietf.org
To unsubscribe send an email to bess-le...@ietf.org

___
BESS mailing list -- bess@ietf.org
To unsubscribe send an email to bess-le...@ietf.org