New revision of IPP Firmware Update Extensions v1.0 posted for review

Smith Kennedy via ipp <[email protected]> Tue, 28 Jul 2026 21:22:16 -0600
Newsgroups gmane.ietf.ipp
Message-ID <[email protected]>
--===============7889729497350010428==
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_D908D602-9BD7-4A77-BB1B-8456B15BDDF8"


--Apple-Mail=_D908D602-9BD7-4A77-BB1B-8456B15BDDF8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Greetings,

I have posted the next revision of IPP Firmware Update Extensions v1.0:

   https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippfwupdate10-20260729.pdf=20
   https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippfwupdate10-20260729-rev.pdf=20=

   https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippfwupdate10-20260729-rev.docx=20=

   https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippfwupdate10-20260729.docx

Changes in this revision:
=E2=80=A2 Removed the =E2=80=9Cprinter-support-uri=E2=80=9D attribute =
from the 2026-07-16 draft, since =E2=80=9Cprinter-more-info-manufacturer=E2=
=80=9D [STD92] is already defined. Added =
=E2=80=9Cprinter-more-info-manufacturer=E2=80=9D to section 11;
=E2=80=A2 Updated IANA Considerations and section 7.3 to rename =
=E2=80=98xxx-download-xxx=E2=80=99 keywords to be =
=E2=80=98xxx-acquisition-xxx=E2=80=99;
=E2=80=A2 Added =E2=80=98xxx-activation-xxx=E2=80=99 keywords to section =
7.3;
=E2=80=A2 Added a reference to RFC 9019; and=20
=E2=80=A2 Updated Section 11 to fix editorial issues.

I will be reading RFC 9019 "A Firmware Update Architecture for Internet =
of Things" tomorrow, but at first skim there are some concepts that are =
worth mentioning in our PWG document, and cross referencing and/or =
leveraging terminology from RFC 9019 may be valuable. I won't engage on =
that until group consensus guides me in that direction.

Cheers,

Smith

/**
   Smith Kennedy
   [email protected]
 */




--Apple-Mail=_D908D602-9BD7-4A77-BB1B-8456B15BDDF8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html aria-label=3D"message body"><head><meta http-equiv=3D"content-type" =
content=3D"text/html; charset=3Dutf-8"></head><body =
style=3D"overflow-wrap: break-word; -webkit-nbsp-mode: space; =
line-break: after-white-space;">Greetings,<div><br></div><div>I have =
posted the next revision of IPP Firmware Update Extensions =
v1.0:</div><div><br></div><div><div>&nbsp; &nbsp;<a =
href=3D"https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippfwupdate10-20260729.pdf">=
https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippfwupdate10-20260729.pdf</a>&nbsp;=
</div><div>&nbsp; &nbsp;<a =
href=3D"https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippfwupdate10-20260729-rev.p=
df">https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippfwupdate10-20260729-rev.pdf</=
a>&nbsp;</div><div>&nbsp; &nbsp;<a =
href=3D"https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippfwupdate10-20260729-rev.d=
ocx">https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippfwupdate10-20260729-rev.docx=
</a>&nbsp;</div><div>&nbsp; &nbsp;<a =
href=3D"https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippfwupdate10-20260729.docx"=
>https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippfwupdate10-20260729.docx</a></di=
v><div><br></div><div>Changes in this revision:</div><div><div>=E2=80=A2 =
Removed the =E2=80=9Cprinter-support-uri=E2=80=9D attribute from the =
2026-07-16 draft, since =E2=80=9Cprinter-more-info-manufacturer=E2=80=9D =
[STD92] is already defined. Added =E2=80=9Cprinter-more-info-manufacturer=E2=
=80=9D to section 11;</div><div>=E2=80=A2 Updated IANA Considerations =
and section 7.3 to rename =E2=80=98xxx-download-xxx=E2=80=99 keywords to =
be =E2=80=98xxx-acquisition-xxx=E2=80=99;</div><div>=E2=80=A2 Added =
=E2=80=98xxx-activation-xxx=E2=80=99 keywords to section =
7.3;</div><div>=E2=80=A2 Added a reference to RFC 9019; =
and&nbsp;</div><div>=E2=80=A2 Updated Section 11 to fix editorial =
issues.</div></div><div><br></div><div>I will be reading RFC 9019 "A =
Firmware Update Architecture for Internet of Things" tomorrow, but at =
first skim there are some concepts that are worth mentioning in our PWG =
document, and cross referencing and/or leveraging terminology from RFC =
9019 may be valuable. I won't engage on that until group consensus =
guides me in that =
direction.</div><div><br></div><div>Cheers,</div><div><br></div><div>
<meta =
charset=3D"UTF-8"><div>Smith</div><div><br></div><div>/**</div><div>&nbsp;=
 &nbsp;Smith Kennedy</div><div>&nbsp; =
&nbsp;[email protected]</div><div>&nbsp;*/</div><div><br></div><b=
r class=3D"Apple-interchange-newline">
</div>

<br></div></body></html>=

--Apple-Mail=_D908D602-9BD7-4A77-BB1B-8456B15BDDF8--

--===============7889729497350010428==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ipp mailing list
[email protected]
https://www.pwg.org/mailman/listinfo/ipp

--===============7889729497350010428==--