Re: [bess] WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02
Hi Ketan, Thank you for the update and the email. Diff looks good to me. --Bruno From: Ketan Talaulikar Sent: Wednesday, March 20, 2024 3:03 AM To: DECRAENE Bruno INNOV/NET Cc: Matthew Bocci (Nokia) ; draft-trr-bess-bgp-srv6-a...@ietf.org; bess@ietf.org Subject: Re: WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02 Hi Bruno/All, This is a short note to update that the v01 with the changes discussed/agreed in this thread has been posted. https://datatracker.ietf.org/doc/html/draft-ietf-bess-bgp-srv6-args-01 Thanks, Ketan (on behalf of co-authors) On Wed, Oct 25, 2023 at 5:25 PM Ketan Talaulikar mailto:ketant.i...@gmail.com>> wrote: Hi Bruno, Thanks for confirming. These changes will be included in the v01 of the draft. Thanks, Ketan On Tue, Oct 24, 2023 at 6:13 PM mailto:bruno.decra...@orange.com>> wrote: Hi Ketan, Thanks for your reply. Your proposed changes look good to me. Thanks for this. --Bruno From: Ketan Talaulikar mailto:ketant.i...@gmail.com>> Sent: Monday, October 23, 2023 1:06 PM To: DECRAENE Bruno INNOV/NET mailto:bruno.decra...@orange.com>> Cc: Matthew Bocci (Nokia) mailto:matthew.bo...@nokia.com>>; draft-trr-bess-bgp-srv6-a...@ietf.org<mailto:draft-trr-bess-bgp-srv6-a...@ietf.org>; bess@ietf.org<mailto:bess@ietf.org> Subject: Re: WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02 Hi Bruno, Thanks for your support and comments. Please check inline below for response. On Wed, Oct 11, 2023 at 7:51 PM mailto:bruno.decra...@orange.com>> wrote: I support adoption : clarifying spec and improving interop is important. Thank you for section 4 regarding Backward Compatibility. May be 1 comment although I didn’t take time to read everything in details and I’m not familiar with EVPN. It’s not completely clear to me whether backward compatibility MAY be preserved or MUST be preserved. Unless there is a good technical reason, my preference would be for “MUST be preserved”. e.g. §4 OLD: Backward compatibility with implementations doing the bitwise logical-OR operation can be preserved by the advertisement of SIDs NEW: Backward compatibility with implementations doing the bitwise logical-OR operation is preserved thanks to the advertisement of SIDs KT> Ack. We will incorporate this change in the next version. §3.1 OLD: it is REQUIRED that proper LBL, LNL, and FL values be set corresponding to the supported SID Structure for the End.DT2M SRv6 Service SIDs. KT> In this context, the "proper" values are the same values as signaled via the SID Structure for the End.DT2M SID. Would the following work? NEW: it is REQUIRED that the LBL, LNL, and FL values be set as indicated via the SID Structure for the End.DT2M SRv6 Service SIDs. Given that this is already the second spec to clarify this, may be “proper [..] value” could be expanded so as to specify the precise behavior which is REQUIRED. Probably similar comment for §3.2 (“The LBL, LNL, and FL MUST be set to appropriate values”). KT> Perhaps the word "appropriate" is redundant here ... would removing it help? Thanks, Ketan Thanks, Regards, --Bruno Orange Restricted Orange Restricted From: BESS mailto:bess-boun...@ietf.org>> On Behalf Of Matthew Bocci (Nokia) Sent: Thursday, September 28, 2023 4:49 PM To: bess@ietf.org<mailto:bess@ietf.org> Cc: draft-trr-bess-bgp-srv6-a...@ietf.org<mailto:draft-trr-bess-bgp-srv6-a...@ietf.org> Subject: [bess] WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02 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/> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegie
Re: [bess] WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02
Hi Bruno/All, This is a short note to update that the v01 with the changes discussed/agreed in this thread has been posted. https://datatracker.ietf.org/doc/html/draft-ietf-bess-bgp-srv6-args-01 Thanks, Ketan (on behalf of co-authors) On Wed, Oct 25, 2023 at 5:25 PM Ketan Talaulikar wrote: > Hi Bruno, > > Thanks for confirming. These changes will be included in the v01 of the > draft. > > Thanks, > Ketan > > > On Tue, Oct 24, 2023 at 6:13 PM wrote: > >> Hi Ketan, >> >> >> >> Thanks for your reply. >> >> >> >> Your proposed changes look good to me. >> >> >> >> Thanks for this. >> >> >> >> --Bruno >> >> >> >> *From:* Ketan Talaulikar >> *Sent:* Monday, October 23, 2023 1:06 PM >> *To:* DECRAENE Bruno INNOV/NET >> *Cc:* Matthew Bocci (Nokia) ; >> draft-trr-bess-bgp-srv6-a...@ietf.org; bess@ietf.org >> *Subject:* Re: WG adoption and IPR poll for >> draft-trr-bess-bgp-srv6-args-02 >> >> >> >> Hi Bruno, >> >> >> >> Thanks for your support and comments. Please check inline below for >> response. >> >> >> >> On Wed, Oct 11, 2023 at 7:51 PM wrote: >> >> I support adoption : clarifying spec and improving interop is important. >> >> >> >> Thank you for section 4 regarding Backward Compatibility. >> >> May be 1 comment although I didn’t take time to read everything in >> details and I’m not familiar with EVPN. >> >> >> >> It’s not completely clear to me whether backward compatibility MAY be >> preserved or MUST be preserved. >> >> Unless there is a good technical reason, my preference would be for “MUST >> be preserved”. >> >> e.g. >> >> §4 >> >> OLD: Backward compatibility with implementations doing the bitwise >> >>logical-OR operation can be preserved by the advertisement of SIDs >> >> >> >> NEW: Backward compatibility with implementations doing the bitwise >> >>logical-OR operation is preserved thanks to the advertisement of SIDs >> >> >> >> >> >> KT> Ack. We will incorporate this change in the next version. >> >> >> >> §3.1 >> >> OLD: >> >> it is >> >>REQUIRED that proper LBL, LNL, and FL values be set corresponding to >> >>the supported SID Structure for the End.DT2M SRv6 Service SIDs. >> >> >> >> KT> In this context, the "proper" values are the same values as signaled >> via the SID Structure for the End.DT2M SID. Would the following work? >> >> >> >> NEW: >> >> it is >> >> REQUIRED that the LBL, LNL, and FL values be set as indicated via >> >> the SID Structure for the End.DT2M SRv6 Service SIDs. >> >> >> >> >> >> >> >> >> >> Given that this is already the second spec to clarify this, may be >> “proper [..] value” could be expanded so as to specify the precise behavior >> which is REQUIRED. >> >> >> >> Probably similar comment for §3.2 (“The LBL, LNL, and FL MUST be set to >> appropriate values”). >> >> >> >> KT> Perhaps the word "appropriate" is redundant here ... would removing >> it help? >> >> >> >> Thanks, >> >> Ketan >> >> >> >> >> >> Thanks, >> >> Regards, >> >> --Bruno >> >> >> >> >> >> Orange Restricted >> >> >> >> Orange Restricted >> >> *From:* BESS *On Behalf Of *Matthew Bocci (Nokia) >> *Sent:* Thursday, September 28, 2023 4:49 PM >> *To:* bess@ietf.org >> *Cc:* draft-trr-bess-bgp-srv6-a...@ietf.org >> *Subject:* [bess] WG adoption and IPR poll for >> draft-trr-bess-bgp-srv6-args-02 >> >> >> >> 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 o
Re: [bess] WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02
Hi Bruno, Thanks for confirming. These changes will be included in the v01 of the draft. Thanks, Ketan On Tue, Oct 24, 2023 at 6:13 PM wrote: > Hi Ketan, > > > > Thanks for your reply. > > > > Your proposed changes look good to me. > > > > Thanks for this. > > > > --Bruno > > > > *From:* Ketan Talaulikar > *Sent:* Monday, October 23, 2023 1:06 PM > *To:* DECRAENE Bruno INNOV/NET > *Cc:* Matthew Bocci (Nokia) ; > draft-trr-bess-bgp-srv6-a...@ietf.org; bess@ietf.org > *Subject:* Re: WG adoption and IPR poll for > draft-trr-bess-bgp-srv6-args-02 > > > > Hi Bruno, > > > > Thanks for your support and comments. Please check inline below for > response. > > > > On Wed, Oct 11, 2023 at 7:51 PM wrote: > > I support adoption : clarifying spec and improving interop is important. > > > > Thank you for section 4 regarding Backward Compatibility. > > May be 1 comment although I didn’t take time to read everything in details > and I’m not familiar with EVPN. > > > > It’s not completely clear to me whether backward compatibility MAY be > preserved or MUST be preserved. > > Unless there is a good technical reason, my preference would be for “MUST > be preserved”. > > e.g. > > §4 > > OLD: Backward compatibility with implementations doing the bitwise > >logical-OR operation can be preserved by the advertisement of SIDs > > > > NEW: Backward compatibility with implementations doing the bitwise > >logical-OR operation is preserved thanks to the advertisement of SIDs > > > > > > KT> Ack. We will incorporate this change in the next version. > > > > §3.1 > > OLD: > > it is > >REQUIRED that proper LBL, LNL, and FL values be set corresponding to > >the supported SID Structure for the End.DT2M SRv6 Service SIDs. > > > > KT> In this context, the "proper" values are the same values as signaled > via the SID Structure for the End.DT2M SID. Would the following work? > > > > NEW: > > it is > > REQUIRED that the LBL, LNL, and FL values be set as indicated via > > the SID Structure for the End.DT2M SRv6 Service SIDs. > > > > > > > > > > Given that this is already the second spec to clarify this, may be “proper > [..] value” could be expanded so as to specify the precise behavior which > is REQUIRED. > > > > Probably similar comment for §3.2 (“The LBL, LNL, and FL MUST be set to > appropriate values”). > > > > KT> Perhaps the word "appropriate" is redundant here ... would removing it > help? > > > > Thanks, > > Ketan > > > > > > Thanks, > > Regards, > > --Bruno > > > > > > Orange Restricted > > > > Orange Restricted > > *From:* BESS *On Behalf Of *Matthew Bocci (Nokia) > *Sent:* Thursday, September 28, 2023 4:49 PM > *To:* bess@ietf.org > *Cc:* draft-trr-bess-bgp-srv6-a...@ietf.org > *Subject:* [bess] WG adoption and IPR poll for > draft-trr-bess-bgp-srv6-args-02 > > > > 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/> > > > > Ce message et ses pieces jointes peuvent contenir des informations > confidentielles ou privilegiees et ne doivent donc > > pas etre diffuses, exploites ou copies sans autorisat
Re: [bess] WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02
Hi Ketan, Thanks for your reply. Your proposed changes look good to me. Thanks for this. --Bruno From: Ketan Talaulikar Sent: Monday, October 23, 2023 1:06 PM To: DECRAENE Bruno INNOV/NET Cc: Matthew Bocci (Nokia) ; draft-trr-bess-bgp-srv6-a...@ietf.org; bess@ietf.org Subject: Re: WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02 Hi Bruno, Thanks for your support and comments. Please check inline below for response. On Wed, Oct 11, 2023 at 7:51 PM mailto:bruno.decra...@orange.com>> wrote: I support adoption : clarifying spec and improving interop is important. Thank you for section 4 regarding Backward Compatibility. May be 1 comment although I didn’t take time to read everything in details and I’m not familiar with EVPN. It’s not completely clear to me whether backward compatibility MAY be preserved or MUST be preserved. Unless there is a good technical reason, my preference would be for “MUST be preserved”. e.g. §4 OLD: Backward compatibility with implementations doing the bitwise logical-OR operation can be preserved by the advertisement of SIDs NEW: Backward compatibility with implementations doing the bitwise logical-OR operation is preserved thanks to the advertisement of SIDs KT> Ack. We will incorporate this change in the next version. §3.1 OLD: it is REQUIRED that proper LBL, LNL, and FL values be set corresponding to the supported SID Structure for the End.DT2M SRv6 Service SIDs. KT> In this context, the "proper" values are the same values as signaled via the SID Structure for the End.DT2M SID. Would the following work? NEW: it is REQUIRED that the LBL, LNL, and FL values be set as indicated via the SID Structure for the End.DT2M SRv6 Service SIDs. Given that this is already the second spec to clarify this, may be “proper [..] value” could be expanded so as to specify the precise behavior which is REQUIRED. Probably similar comment for §3.2 (“The LBL, LNL, and FL MUST be set to appropriate values”). KT> Perhaps the word "appropriate" is redundant here ... would removing it help? Thanks, Ketan Thanks, Regards, --Bruno Orange Restricted Orange Restricted From: BESS mailto:bess-boun...@ietf.org>> On Behalf Of Matthew Bocci (Nokia) Sent: Thursday, September 28, 2023 4:49 PM To: bess@ietf.org<mailto:bess@ietf.org> Cc: draft-trr-bess-bgp-srv6-a...@ietf.org<mailto:draft-trr-bess-bgp-srv6-a...@ietf.org> Subject: [bess] WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02 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/> Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies
Re: [bess] WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02
Hi Ketan Thanks. That works. Matthew From: Ketan Talaulikar Date: Monday, 23 October 2023 at 12:07 To: Matthew Bocci (Nokia) Cc: bess@ietf.org , draft-trr-bess-bgp-srv6-a...@ietf.org Subject: Re: WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02 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 Matthew, We have just posted the WG version of the draft that is identical to the one that was up for adoption. We will post another update after incorporating the changes to address Bruno's comments after we conclude on the text changes. Thanks, Ketan On Wed, Oct 18, 2023 at 4:10 PM Matthew Bocci (Nokia) mailto:matthew.bo...@nokia.com>> wrote: WG, There is consensus to adopt this draft as a BESS WG document. Authors: please respond to the one comment form Bruno and upload a new version of the draft as draft-ietf-bess-bgp-srv6-args-00. Thanks Matthew From: Matthew Bocci (Nokia) mailto:matthew.bo...@nokia.com>> Date: Thursday, 28 September 2023 at 15:49 To: bess@ietf.org<mailto:bess@ietf.org> mailto:bess@ietf.org>> Cc: draft-trr-bess-bgp-srv6-a...@ietf.org<mailto:draft-trr-bess-bgp-srv6-a...@ietf.org> mailto:draft-trr-bess-bgp-srv6-a...@ietf.org>> Subject: WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02 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
Re: [bess] WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02
Hi Matthew, We have just posted the WG version of the draft that is identical to the one that was up for adoption. We will post another update after incorporating the changes to address Bruno's comments after we conclude on the text changes. Thanks, Ketan On Wed, Oct 18, 2023 at 4:10 PM Matthew Bocci (Nokia) < matthew.bo...@nokia.com> wrote: > WG, > > > > There is consensus to adopt this draft as a BESS WG document. > > > > Authors: please respond to the one comment form Bruno and upload a new > version of the draft as draft-ietf-bess-bgp-srv6-args-00. > > > > Thanks > > > > Matthew > > > > *From: *Matthew Bocci (Nokia) > *Date: *Thursday, 28 September 2023 at 15:49 > *To: *bess@ietf.org > *Cc: *draft-trr-bess-bgp-srv6-a...@ietf.org < > draft-trr-bess-bgp-srv6-a...@ietf.org> > *Subject: *WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02 > > 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
Re: [bess] WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02
Hi Bruno, Thanks for your support and comments. Please check inline below for response. On Wed, Oct 11, 2023 at 7:51 PM wrote: > I support adoption : clarifying spec and improving interop is important. > > > > Thank you for section 4 regarding Backward Compatibility. > > May be 1 comment although I didn’t take time to read everything in details > and I’m not familiar with EVPN. > > > > It’s not completely clear to me whether backward compatibility MAY be > preserved or MUST be preserved. > > Unless there is a good technical reason, my preference would be for “MUST > be preserved”. > > e.g. > > §4 > > OLD: Backward compatibility with implementations doing the bitwise > >logical-OR operation can be preserved by the advertisement of SIDs > > > > NEW: Backward compatibility with implementations doing the bitwise > >logical-OR operation is preserved thanks to the advertisement of SIDs > > > KT> Ack. We will incorporate this change in the next version. > §3.1 > > OLD: > > it is > >REQUIRED that proper LBL, LNL, and FL values be set corresponding to > >the supported SID Structure for the End.DT2M SRv6 Service SIDs. > > KT> In this context, the "proper" values are the same values as signaled via the SID Structure for the End.DT2M SID. Would the following work? NEW: it is REQUIRED that the LBL, LNL, and FL values be set as indicated via the SID Structure for the End.DT2M SRv6 Service SIDs. > > > Given that this is already the second spec to clarify this, may be “proper > [..] value” could be expanded so as to specify the precise behavior which > is REQUIRED. > > > > Probably similar comment for §3.2 (“The LBL, LNL, and FL MUST be set to > appropriate values”). > > KT> Perhaps the word "appropriate" is redundant here ... would removing it help? Thanks, Ketan > > > Thanks, > > Regards, > > --Bruno > > > > > > Orange Restricted > > *From:* BESS *On Behalf Of *Matthew Bocci (Nokia) > *Sent:* Thursday, September 28, 2023 4:49 PM > *To:* bess@ietf.org > *Cc:* draft-trr-bess-bgp-srv6-a...@ietf.org > *Subject:* [bess] WG adoption and IPR poll for > draft-trr-bess-bgp-srv6-args-02 > > > > 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/> > > > Ce message et ses pieces jointes peuvent contenir des informations > confidentielles ou privilegiees et ne doivent donc > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu > ce message par erreur, veuillez le signaler > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages > electroniques etant susceptibles d'alteration, > Orange decline toute responsabilite si ce message a ete altere, deforme ou > falsifie. Merci. > > This message and its attachments may contain confidential or privileged > information that may be protected by law; > they should not be distributed, used or copied without authorisation. > If you have received this email in error, please notify the sender and delete > this message and its attachments. > As emails may be altered, Orange is not liable for messages that have been > modified, changed or falsified. > Thank you. > > ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
Re: [bess] WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02
WG, There is consensus to adopt this draft as a BESS WG document. Authors: please respond to the one comment form Bruno and upload a new version of the draft as draft-ietf-bess-bgp-srv6-args-00. Thanks Matthew From: Matthew Bocci (Nokia) Date: Thursday, 28 September 2023 at 15:49 To: bess@ietf.org Cc: draft-trr-bess-bgp-srv6-a...@ietf.org Subject: WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02 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
Re: [bess] WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02
I support the adoption of this document: it provides an important clarification for interop Regards, Luc André Luc André Burdet | Cisco | laburdet.i...@gmail.com | Tel: +1 613 254 4814 From: BESS on behalf of Matthew Bocci (Nokia) Date: Thursday, September 28, 2023 at 10:51 To: bess@ietf.org Cc: draft-trr-bess-bgp-srv6-a...@ietf.org Subject: [bess] WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02 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
Re: [bess] WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02
I support adoption : clarifying spec and improving interop is important.
Thank you for section 4 regarding Backward Compatibility.
May be 1 comment although I didn't take time to read everything in details and
I'm not familiar with EVPN.
It's not completely clear to me whether backward compatibility MAY be preserved
or MUST be preserved.
Unless there is a good technical reason, my preference would be for "MUST be
preserved".
e.g.
§4
OLD: Backward compatibility with implementations doing the bitwise
logical-OR operation can be preserved by the advertisement of SIDs
NEW: Backward compatibility with implementations doing the bitwise
logical-OR operation is preserved thanks to the advertisement of SIDs
§3.1
OLD:
it is
REQUIRED that proper LBL, LNL, and FL values be set corresponding to
the supported SID Structure for the End.DT2M SRv6 Service SIDs.
Given that this is already the second spec to clarify this, may be "proper [..]
value" could be expanded so as to specify the precise behavior which is
REQUIRED.
Probably similar comment for §3.2 ("The LBL, LNL, and FL MUST be set to
appropriate values").
Thanks,
Regards,
--Bruno
Orange Restricted
From: BESS On Behalf Of Matthew Bocci (Nokia)
Sent: Thursday, September 28, 2023 4:49 PM
To: bess@ietf.org
Cc: draft-trr-bess-bgp-srv6-a...@ietf.org
Subject: [bess] WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02
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/>
Ce message et ses pieces jointes peuvent contenir des informations
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou
falsifie. Merci.
This message and its attachments may contain confidential or privileged
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been
modified, changed or falsified.
Thank you.
___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess
Re: [bess] WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02
Hello, I reviewed draft-trr-bess-bgp-srv6-args-02. I consider that this I-D is ready for endorsement by the BESS WG. Many Thanks, -- Brd From: BESS On Behalf Of Matthew Bocci (Nokia) Sent: Thursday, September 28, 2023 4:49 PM To: bess@ietf.org Cc: draft-trr-bess-bgp-srv6-a...@ietf.org Subject: [bess] WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02 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
Re: [bess] WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02
Support the adoption of this draft. Be well, G/ From: BESS On Behalf Of Matthew Bocci (Nokia) Sent: Thursday, September 28, 2023 4:49 PM To: bess@ietf.org Cc: draft-trr-bess-bgp-srv6-a...@ietf.org Subject: [bess] WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02 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
Re: [bess] WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02
I support the adoption. Thanks to the authors and all the other folks providing inputs to improve the draft. Richard From: BESS on behalf of "Matthew Bocci (Nokia)" Date: Thursday, September 28, 2023 at 10:49 AM To: "bess@ietf.org" Cc: "draft-trr-bess-bgp-srv6-a...@ietf.org" Subject: [EXT][bess] WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02 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
Re: [bess] WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02
Hi WG, I've read the draft and support this adoption. Best Regards, Ran Original From: MatthewBocci(Nokia) To: bess@ietf.org ; Cc: draft-trr-bess-bgp-srv6-a...@ietf.org ; Date: 2023年09月28日 22:51 Subject: [bess] WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02 ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess 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)___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
Re: [bess] WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02
I support the WG adoption of this draft. It's an important update for RFC9252 and benifits the implementation. Regards, Yao___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
Re: [bess] WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02
I reviewed the draft and it’s important updates to RFC 9252 to support SRV6 BGP service overlay to support SRv6 SID ARG field for endpoint behaviors that require it namely with EVPN RT-1 and RT-3. I support WG adoption. Thanks Gyan On Thu, Sep 28, 2023 at 10:50 AM 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 > ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
Re: [bess] WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02
I support the WG adoption of this draft. Thanks Dan From: BESS on behalf of "Matthew Bocci (Nokia)" Date: Thursday, September 28, 2023 at 10:49 AM To: "bess@ietf.org" Cc: "draft-trr-bess-bgp-srv6-a...@ietf.org" Subject: [EXT][bess] WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02 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
Re: [bess] WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02
I support the WG adoption of this draft. Thanks. Diego. From: BESS on behalf of "Matthew Bocci (Nokia)" Date: Thursday, September 28, 2023 at 7:51 AM To: "bess@ietf.org" Cc: "draft-trr-bess-bgp-srv6-a...@ietf.org" Subject: [bess] WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02 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
Re: [bess] WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02
As co-author, support the WG adoption of this draft. I am unaware of any IPR related to this draft. Thanks, Wen Juniper Business Use Only From: Mankamana Mishra (mankamis) Date: Thursday, September 28, 2023 at 2:15 PM To: Matthew Bocci (Nokia) , bess@ietf.org Cc: draft-trr-bess-bgp-srv6-a...@ietf.org Subject: Re: WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02 [External Email. Be cautious of content] Support the adoption of this draft. From: BESS on behalf of Matthew Bocci (Nokia) Date: Thursday, September 28, 2023 at 7:51 AM To: bess@ietf.org Cc: draft-trr-bess-bgp-srv6-a...@ietf.org Subject: [bess] WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02 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://urldefense.com/v3/__https:/datatracker.ietf.org/doc/draft-trr-bess-bgp-srv6-args/__;!!NEt6yMaO-gk!HyMbTyuMEqiUj3epjLIYHBBbKLT03UfPt9_iCGnsPWfKYFKkp8yyJE-rZ276PZegt4QPv0vZCIVEzX1B7iYyQNo_gWCpeA$> ___ BESS mailing list BESS@ietf.org https://www.ietf.org/mailman/listinfo/bess
Re: [bess] WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02
I support for adoption. Thanks Krishna From: BESS on behalf of "Matthew Bocci (Nokia)" Date: Thursday, September 28, 2023 at 9:51 AM To: "bess@ietf.org" Cc: "draft-trr-bess-bgp-srv6-a...@ietf.org" Subject: [bess] WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02 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
Re: [bess] WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02
Support the adoption of this draft. From: BESS on behalf of Matthew Bocci (Nokia) Date: Thursday, September 28, 2023 at 7:51 AM To: bess@ietf.org Cc: draft-trr-bess-bgp-srv6-a...@ietf.org Subject: [bess] WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02 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
Re: [bess] WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02
As a co-author, I support the WG adoption of this document. I am not aware of any IPR associated with this document/draft. Thanks. From: Ketan Talaulikar Date: Thursday, September 28, 2023 at 1:36 PM To: Matthew Bocci (Nokia) Cc: bess@ietf.org , draft-trr-bess-bgp-srv6-a...@ietf.org Subject: Re: WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02 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) mailto: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
Re: [bess] WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02
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
Re: [bess] WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02
Hi, As co-author, I support the document for WG adoption. It is important to have this adopted as soon as possible to make sure all EVPN SRv6 multi-homing implementations follow the same procedures. Not aware of any relevant IPR. Thanks. Jorge From: Matthew Bocci (Nokia) Date: Thursday, September 28, 2023 at 7:50 AM To: bess@ietf.org Cc: draft-trr-bess-bgp-srv6-a...@ietf.org Subject: WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02 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
[bess] WG adoption and IPR poll for draft-trr-bess-bgp-srv6-args-02
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
