Hi, as a co-author of the draft I’m not aware of any relevant IPR.

Alex

On Mon, Nov 3, 2025 at 3:56 PM Alex Nichol <[email protected]> wrote:

>
> Hi, as a co-author I support the adoption of this draft.
>
> Alex
>
>
>>
>> *From: *Stephane Litkowski (slitkows) <slitkows=
>> [email protected]>
>> *Date: *Tuesday, October 14, 2025 at 8:17 AM
>> *To: *[email protected] <[email protected]>
>> *Cc: *[email protected] <[email protected]>
>> *Subject: *[bess] WG adoption and IPR poll for
>> draft-sajassi-bess-evpn-umr-mobility
>>
>> Hello,
>>
>> This email begins a two-week WG adoption poll for
>> draft-sajassi-bess-evpn-umr-mobility-03 [1].
>>
>> Please review the draft and post any comments to the BESS working group
>> list.
>>
>> We are also polling for knowledge of any undisclosed IPR that applies to
>> this document, to ensure that IPR has been disclosed in compliance with
>> IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details).
>>
>> If you are listed as an author or a contributor of this document, please
>> respond to this email and indicate whether you are aware of any relevant
>> undisclosed IPR, copying the BESS mailing list. The document will not
>> progress without answers from all the authors and contributors.
>>
>> Currently, there is currently no IPR disclosure against this document.
>>
>> If you are not listed as an author or a contributor, then please
>> explicitly respond only if you are aware of any IPR that has not yet been
>> disclosed in conformance with IETF rules.
>>
>> This poll for adoption closes on Oct 28th 2025.
>>
>> Regards,
>>
>> Stephane, Matthew, and Jeffrey
>>
>> [1] *https://datatracker.ietf.org/doc/draft-sajassi-bess-evpn-umr-mobility/
>> <https://datatracker.ietf.org/doc/draft-sajassi-bess-evpn-umr-mobility/>*
>>
>>
>> _______________________________________________
>> 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]

Reply via email to