Bo and Jan (CC-ed),
Please reply-all to this email with your response to the original IPR call here:
https://mailarchive.ietf.org/arch/msg/netmod/xHDWFr5e2ykRBEseq-99PhRENGM/
Jason, thank you for highlighting this issue to the chairs.
Kent // as chair
> On Apr 24, 2023, at 5:48 PM, Jason Sterne (Nokia) <[email protected]>
> wrote:
>
> Hello chairs and WG,
>
> (as an author)
>
> We've updated both drafts to refactor Acknowledgements vs Contributors:
> https://datatracker.ietf.org/doc/draft-ietf-netmod-yang-module-versioning/09/
> https://datatracker.ietf.org/doc/draft-ietf-netmod-yang-semver/11/
>
> The IPR call for Module Versioning is complete. It already included all
> authors + contributors.
>
> For YANG Semver, we're missing IPR declarations from the following people (we
> didn't include them in the original IPR call):
> Bo Wu
> [email protected]
>
> Jan Lindblad
> [email protected]
>
> Rgds,
> Jason
>
>> -----Original Message-----
>> From: netmod <[email protected]> On Behalf Of Kent Watsen
>> Sent: Monday, March 13, 2023 7:35 PM
>> To: [email protected]
>> Cc: Rob Wilton (rwilton) <[email protected]>
>> Subject: Re: [netmod] IPR Poll on draft-ietf-netmod-yang-semver-09
>>
>>
>> CAUTION: This is an external email. Please be very careful when clicking
>> links or
>> opening attachments. See http://nok.it/ext for additional information.
>>
>>
>>
>> Authors/All,
>>
>> One of the authors pointed out that the list of contributors was incomplete,
>> and
>> specifically didn't include all listed in the paragraph of the contributors
>> section.
>> We had mistakenly read this paragraph as Acknowledgments versus
>> Contributors. It does appear that some of those listed may be Contributors,
>> i.e.,
>> materially contributed to the technical solution or the text (excluding
>> editorial
>> changes), while others may in fact belong in an Acknowledgement section.
>> Given this, we'd like to ask the authors to refactor the Contributors
>> section into
>> separate Acknowledgement and Contributor sections before moving forward on
>> this document. Once we have the new version, we can then judge if there are
>> any missing IPR statements.
>>
>> Thank you,
>>
>> Kent and Lou
>>
>>
>>> On Jan 16, 2023, at 5:59 PM, Kent Watsen <[email protected]> wrote:
>>>
>>> [NOTE: A response is needed from all listed in this message's "To" line, the
>> authors and contributors listed in the draft]
>>>
>>>
>>> Authors, Contributors, WG,
>>>
>>> In preparation for a WGLC Call:
>>>
>>> Are you aware of any IPR that applies to drafts identified above?
>>>
>>> Please state either:
>>>
>>> "No, I'm not aware of any IPR that applies to this draft"
>>> or
>>> "Yes, I'm aware of IPR that applies to this draft"
>>>
>>> If so, has this IPR been disclosed in compliance with IETF IPR rules
>>> (see RFCs 3669, 5378 and 8179 for more details)?
>>>
>>> If yes to the above, please state either:
>>>
>>> "Yes, the IPR has been disclosed in compliance with IETF IPR rules"
>>> or
>>> "No, the IPR has not been disclosed"
>>>
>>> If you answer no, please provide any additional details you think
>>> appropriate. If you are listed as a document author or contributor
>>> please answer the above by responding to this email regardless
>>> of whether or not you are aware of any relevant IPR. This
>>> document will not advance to the next stage until a response
>>> has been received from each author.
>>>
>>> If you are on the WG email list or attend WG meetings but are not
>>> listed as an author or contributor, we remind you of your obligations
>>> under the IETF IPR rules which encourages you to notify the IETF
>>> if you are aware of IPR of others on an IETF contribution, or to
>>> refrain from participating in any contribution or discussion related
>>> to your undisclosed IPR. For more information, please see the RFCs
>>> listed above and
>>> http://trac.tools.ietf.org/group/iesg/trac/wiki/IntellectualProperty.
>>>
>>> Thank you,
>>> Kent and Lou
>>>
>>> PS Please include all listed in the headers of this message in your
>>> response.
>>> _______________________________________________
>>> netmod mailing list
>>> [email protected]
>>> https://www.ietf.org/mailman/listinfo/netmod
>>
>> _______________________________________________
>> netmod mailing list
>> [email protected]
>> https://www.ietf.org/mailman/listinfo/netmod
>
> _______________________________________________
> netmod mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/netmod
_______________________________________________
netmod mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/netmod
