[core] Re: IPR poll for draft-ietf-core-coap-pubsub

[Michael Koster <[e-mail]>]

I am not personally aware of any patent claims that would read on this specification.

Best regards,

Michael


> On Jun 25, 2026, at 2:30 AM, Esko Dijk <[e-mail]> wrote:
> 
> (Note: this message is reusing text from an earlier poll from Marco - I'll take the liberty to reuse, thanks. I might even have a license from IETF Trust to do so :)  )
>  
> Dear all,
> 
> I am sending this message as an IPR poll for the document draft-ietf-core-coap-pubsub of which I am the Shepherd.
> 
> https://datatracker.ietf.org/doc/html/draft-ietf-core-coap-pubsub
> 
> As you all know, there are certain requirements about declaring patent claims (called "IPR" in IETF lingo) that you are personally aware of and that apply to a contribution (another IETF term) you make to the IETF.
> 
> These requirements do not change with IESG submission of a document, but that milestone provides a convenient check point, particularly for all authors and contributors listed, to indicate that such "IPR declarations" have been made as required, or possibly an assertion that you are not personally aware of patent claims that would "read" on that document. Note that this is about what you personally know, not about needing to consult your employer's corporate lawyers to state a legal opinion.
> 
> So: If you are **personally aware of any patent claims** that might apply to systems that implement this draft, please review BCP 78 [1] and BCP 79 [2] and make any appropriate IPR declaration now. If you are not sure whether you need to make a declaration or not, please talk to the chairs ([e-mail] <mailto:[e-mail]>).
> 
> **If you are an author or listed contributor** and do not know about a pertinent patent claim (granted or in processing), please simply do a wide reply to this message and state:
> 
> "I am not personally aware of any patent claims that would read on this specification."
> 
> (Creating the Shepherd write-up is blocking on the authors' responses.)
> 
> Best regards,
> Esko Dijk
> 
> [1] https://www.rfc-editor.org/rfc/rfc5378.html
> 
> [2] https://www.rfc-editor.org/rfc/rfc8179.html