I support to move this document forward to publication. There are no IPR that I am aware of related to this document.
Apologies for leaving out IPR statement. Regards -- Aldrin On Mon, Jun 12, 2017 at 12:52 PM Aldrin Isaac <aldrin.is...@gmail.com> wrote: > Yes. I support to move this forward. > > Regards -- Aldrin > On Mon, Jun 12, 2017 at 3:39 PM UTTARO, JAMES <ju1...@att.com> wrote: > >> *Fully support as co-author..I am not aware of any IPR related to this >> document..* >> >> >> >> *Thanks,* >> >> * Jim Uttaro* >> >> >> >> *From:* BESS [mailto:bess-boun...@ietf.org] *On Behalf Of *Senad IETF - >> Internet Engineering Task Force >> *Sent:* Monday, June 12, 2017 3:29 PM >> *To:* Martin Vigoureux <martin.vigour...@nokia.com> >> *Cc:* BESS <bess@ietf.org> >> *Subject:* Re: [bess] WG Last Call for draft-ietf-bess-evpn-usage >> >> >> >> 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&T >> >> [1] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-usage/ >> <https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_draft-2Dietf-2Dbess-2Devpn-2Dusage_&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=s7ZzB4JbPv3nYuoSx5Gy8Q&m=NsXRNCpI-XG9vxejXm9NHxu1FVv_j2gAG3NSW3vZPh8&s=RuJG5P3GiwU0kDVlo12PU41vXQ4DzY-_xqvgolWjkq4&e=> >> [2] >> https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw >> <https://urldefense.proofpoint.com/v2/url?u=https-3A__mailarchive.ietf.org_arch_msg_bess_cG3X1tTqb-5FvPC4rg56SEdkjqDpw&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=s7ZzB4JbPv3nYuoSx5Gy8Q&m=NsXRNCpI-XG9vxejXm9NHxu1FVv_j2gAG3NSW3vZPh8&s=tLVXhULe4bJzbVBsBOybultgu62EreH6szg5v5-j5As&e=> >> >> _______________________________________________ >> BESS mailing list >> BESS@ietf.org >> https://www.ietf.org/mailman/listinfo/bess >> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_bess&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=s7ZzB4JbPv3nYuoSx5Gy8Q&m=NsXRNCpI-XG9vxejXm9NHxu1FVv_j2gAG3NSW3vZPh8&s=ocQqmy844e0BOlY73StBUg5Zh5vxs8JaCD6hhDXfm7Q&e=> >> >> >> _______________________________________________ >> 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
