Hi All, I am not aware of any IPR associated with this document.
As a co-author, I would request the WG to support adoption - this updates the RFC9252 that was produced by our WG and provides clarifications that were found to be required during the multi-vendor interop. Thanks, Ketan On Thu, Sep 28, 2023 at 8:19 PM Matthew Bocci (Nokia) < matthew.bo...@nokia.com> wrote: > This email begins a two-week WG adoption and IPR poll for > draft-trr-bess-bgp-srv6-args-02 [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 or not 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 to the IPR poll 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 Thursday 12th October 2023. > > > > [1] draft-trr-bess-bgp-srv6-args-02 - SRv6 Argument Signaling for BGP > Services (ietf.org) > <https://datatracker.ietf.org/doc/draft-trr-bess-bgp-srv6-args/> >
_______________________________________________ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess