Re: [bess] WG Last Call and IPR Poll for draft-ietf-bess-bgp-vpls-control-flags-04

[Senad IETF - Internet Engineering Task Force]

Hi,

I am not aware of any IPR issues related to this draft.

/Senad


On Mon, Apr 23, 2018 at 11:00 AM,  wrote:

> Hi WG,
>
>
>
> This email begins a two-week working group last call for
> draft-ietf-bess-bgp-vpls-control-flags-04 [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 won't
> progress without answers from all the authors and contributors.
>
>
>
> Currently there is one IPR declaration against this document (
> https://datatracker.ietf.org/ipr/search/?submit=draft=
> draft-ietf-bess-bgp-vpls-control-flags).
>
>
>
> If you are 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.
>
>
>
> We are also polling for any existing implementations.
>
>
>
> The working group last call closes on 7th May.
>
>
>
> Regards,
>
>
>
> Matthew and Stéphane
>
>
>
> [1] https://datatracker.ietf.org/doc/draft-ietf-bess-bgp-vpls-
> control-flags/
>
>
>
> _
>
> 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
>
>
___
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess

Re: [bess] WG Last Call for draft-ietf-bess-evpn-usage

[Senad IETF - Internet Engineering Task Force]

Full support of this document for RFC publication.  As a co-author, I am
not aware of any IPR related to this document.

On Tue, Jun 6, 2017 at 10:11 AM, Martin Vigoureux <
martin.vigour...@nokia.com> wrote:

> Hello Working Group,
>
> This email starts a Working Group Last Call on
> draft-ietf-bess-evpn-usage-04 [1] which is considered mature and ready for
> a final working group review.
>
> Please read this document if you haven't read the most recent
> version yet, and send your comments to the list, no later than
> *20th of June*.
> Note that this is *not only* a call for comments on the document; it is
> also a call for support (or not) to publish this document as an
> Informational RFC.
>
> *Coincidentally*, we are also polling for knowledge of any IPR that
> applies to draft-ietf-bess-evpn-usage, 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 a document Author or Contributor of
> draft-ietf-bess-evpn-usage-04 please respond to this email and indicate
> whether or not you are aware of any relevant IPR.
>
> Note that, as of today, no IPR has been disclosed against this document or
> its earlier versions.
>
> As opposed to the policy [2], we are not polling for knowledge of
> implementations as it does not seem to make sense in that case. If you feel
> otherwise, please let us know.
>
> Thank you,
> M
>
> [1] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-usage/
> [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw
>
> ___
> 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 Last Call for draft-ietf-bess-dci-evpn-overlay-04

[Senad IETF - Internet Engineering Task Force]

As a co-author, I support this document as Proposed Standard RFC.
I am also not aware of any IPR that has not been disclosed yet.

Thanks - Senad

On Mon, Feb 6, 2017 at 8:07 AM, Martin Vigoureux  wrote:

> Hello Working Group,
>
> This email starts a Working Group Last Call on
> draft-ietf-bess-dci-evpn-overlay-04 [1] which is considered mature and
> ready for a final working group review.
>
> Please read the document if you haven't read the most recent
> version yet, and send your comments to the list, no later than
> *19th of February*.
> Note that this is *not only* a call for comments on the document; it is
> also a call for support (or not) to publish this document as a Proposed
> Standard RFC.
>
> *Coincidentally*, we are also polling for knowledge of any IPR that
> applies to draft-ietf-bess-dci-evpn-overlay, 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 a document author or contributor of
> draft-ietf-bess-dci-evpn-overlay-04 please respond to this email and
> indicate whether or not you are aware of any relevant IPR.
>
> Note that IPR exists and has been disclosed against this document [2].
>
> Thank you,
> M
>
> [1] https://datatracker.ietf.org/doc/draft-ietf-bess-dci-evpn-overlay/
> [2] https://datatracker.ietf.org/ipr/search/?submit=draft=dra
> ft-ietf-bess-dci-evpn-overlay
>
> ___
> 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