Subject: Re: [mpls] IPR poll on draft-ietf-mpls-ri-rsvp-frr

From: Harish Sitaraman <[email-masked]>
Date: Sat, 4 Nov 2017 15:27:17 +0000

Yes, I'm aware of IPR that applies to this draft. The IPR has been disclosed in compliance with IETF IPR rules (https://datatracker.ietf.org/ipr/2580/).

Harish

From: mpls <[email-masked]<mailto:[email-masked]>> on behalf of "[email-masked]<mailto:[email-masked]>" <[email-masked]<mailto:[email-masked]>>
Date: Saturday, November 4, 2017 at 2:01 AM
To: "[email-masked]<mailto:[email-masked]>" <[email-masked]<mailto:[email-masked]>>, "[email-masked]<mailto:[email-masked]>" <[email-masked]<mailto:[email-masked]>>, "[email-masked]<mailto:[email-masked]>" <[email-masked]<mailto:[email-masked]>>
Subject: [mpls] IPR poll on draft-ietf-mpls-ri-rsvp-frr

Working Group,

We are currently preparing draft-ietf-mpls-ri-rsvp-frr for working group last call. We will do an IPR poll prior to the wglc.

This is to start the IPR Poll.

Are you aware of any IPR that applies to draft-ietf-mpls-ri-rsvp-frr?

If so, has this IPR been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details).

Please note that there is already one IPR disclosed for the individual document:

https://datatracker.ietf.org/ipr/2580/<https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_ipr_2580_&d=DwMFAg&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=CXKOXD_3UIPrRhmyXS8lTOnJ2ZY8S-bng806Yu9IBa0&m=OLUujleLNhj54DgjG0pjq16zck0dtZurYUOAmGelkVg&s=Q_my9kpK_AX0bSoKLj3VZNb5VgZ50oojRGyENuUbuVU&e=>

If you are listed as a document author or contributor please respond to this email regardless of whether or not you are aware of any relevant IPR. *The response needs to be sent to the MPLS wg mailing list.* The document will not advance to the next stage until a response has been received from each author and contributor.

If you are on the MPLS WG email list but are not listed as an author or contributor, then please explicitly respond only if you are aware of any IPR that has not yet been disclosed in conformance with IETF rules.

Best regards

Nic