Re: Updated IPP Firmware Update Extensions v1.0 draft posted

--===============5393805794009664355==
Content-Type: multipart/alternative; boundary="00000000000053b713064964d050"

--00000000000053b713064964d050
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi

Over all a very good initiative, but i have some concerns - sorry if they
have already been addressed (i couldn't find it).

With this mirroring the installed firmware in being able to communicate
that there are multiple firmware types and versions,
i think it could be worth being super-duper clear on that the contents of
these lists describe a set of firmware files that would get applied
together when triggering an update.
(...and is not to be used to contain multiple versions of the same thing).
A naive implementer might be tempted to list all versions offered, only to
find out the update operation has no way of saying to what version.

I also think it is a mistake to only support, possible even to require,
some online repository for firmware.
I think it would be very good to be able to supply the firmware file(s)
directly from the client.
Files tend to stick around much longer than the services that served them
most of the time.
Currently a lot of firmware updates are simply performed by "printing" a
file with some magic (often PJL) in it.
Also think of use in air-gapped environments, not just post-support-window
devices.
With no standard on what a repository is, there is no guarantee i could
deploy my own.

Br,
Anton

Den tis 27 jan. 2026 kl 19:59 skrev Kennedy, Smith (Wireless & IPP
Standards) via ipp <[email protected]>:

> Greetings,
>
> I've posted a new draft of IPP Firmware Update Extensions v1.0:
>
> https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippfwupdate10-20260127.pdf
> https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippfwupdate10-20260127.docx
> https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippfwupdate10-20260127-rev.pdf
> https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippfwupdate10-20260127-rev.docx
>
>
> Changes:
>
>
>    - Updates to section 4 to consolidate discussion of the linkage
>    between the new operations, the new attributes, and the new values for
>    existing attributes
>    - Updated the abstract
>    - Fixed the document file name
>    - Added section 4.5 =E2=80=9CEnabling or Disabling the Printer Firmwar=
e Update
>    Feature=E2=80=9D and defined the =E2=80=9Cprinter-firmware-update-enab=
led=E2=80=9D attribute to
>    allow a Client to have an easy way to detect support for the feature, =
and
>    to provide the Printer and its Administrator with a way to disable the
>    feature.
>
>
> I know we won't be looking at this Thursday but its there for review
> before the F2F and we could peek at it if we want to.
>
> Cheers,
>
> Smith
>
> /**
>     Smith Kennedy
>     HP Inc.
> */
>
> _______________________________________________
> ipp mailing list
> [email protected]
> https://www.pwg.org/mailman/listinfo/ipp
>

--00000000000053b713064964d050
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div>Hi</div><div><br></div><div>Over all=
 a very good initiative, but i have some concerns - sorry if they have alre=
ady been addressed (i couldn&#39;t find it).</div><div><br></div><div>With =
this mirroring the installed firmware in being able to communicate that the=
re are multiple firmware types and versions,=C2=A0</div><div>i think it cou=
ld be worth being super-duper clear on that the contents of these lists des=
cribe a set of firmware files that would get applied together when triggeri=
ng an update.</div><div>(...and is not to be used to contain multiple versi=
ons of the same thing).</div><div>A naive implementer might be tempted to l=
ist all versions offered, only to find out the update operation has no way =
of saying to what version.</div><div></div><div><br></div><div>I also think=
 it is a mistake to only support, possible even to require, some online rep=
ository for firmware.</div><div>I think it would be very good to be able to=
 supply the firmware file(s) directly from the client.</div><div>Files tend=
 to stick around much longer than the services that served them most of the=
 time.</div><div>Currently a lot of firmware updates are simply performed b=
y &quot;printing&quot; a file with some magic (often PJL) in it.</div><div>=
Also think of use in air-gapped environments, not just post-support-window =
devices.</div><div>With no standard on what a repository is, there is no gu=
arantee i could deploy my own.</div><div><br></div><div>Br,</div><div>Anton=
</div></div><br><div class=3D"gmail_quote gmail_quote_container"><div dir=
=3D"ltr" class=3D"gmail_attr">Den tis 27 jan. 2026 kl 19:59 skrev Kennedy, =
Smith (Wireless &amp; IPP Standards) via ipp &lt;<a href=3D"mailto:ipp@pwg.=
org">[email protected]</a>&gt;:<br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex">



<div>
Greetings,
<div><br>
</div>
<div>I&#39;ve posted a new draft of IPP Firmware Update Extensions v1.0:</d=
iv>
<div><br>
</div>
<blockquote style=3D"margin:0px 0px 0px 40px;border:medium;padding:0px">
<div>
<div><a href=3D"https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippfwupdate10-2026012=
7.pdf" target=3D"_blank">https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippfwupdate1=
0-20260127.pdf</a>=C2=A0</div>
</div>
<div>
<div><a href=3D"https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippfwupdate10-2026012=
7.docx" target=3D"_blank">https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippfwupdate=
10-20260127.docx</a>=C2=A0</div>
</div>
<div>
<div><a href=3D"https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippfwupdate10-2026012=
7-rev.pdf" target=3D"_blank">https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippfwupd=
ate10-20260127-rev.pdf</a>=C2=A0</div>
</div>
<div>
<div><a href=3D"https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippfwupdate10-2026012=
7-rev.docx" target=3D"_blank">https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippfwup=
date10-20260127-rev.docx</a></div>
</div>
</blockquote>
<div>
<div><br>
</div>
<div>Changes:</div>
<div><br>
</div>
<div>
<div>
<ul>
<li>Updates to section 4 to consolidate discussion of the linkage between t=
he new operations, the new attributes, and the new values for existing attr=
ibutes</li><li>Updated the abstract</li><li>Fixed the document file name</l=
i><li>Added section 4.5 =E2=80=9CEnabling or Disabling the Printer Firmware=
 Update Feature=E2=80=9D and defined the =E2=80=9Cprinter-firmware-update-e=
nabled=E2=80=9D attribute to allow a Client to have an easy way to detect s=
upport for the feature, and to provide the Printer and its Administrator
 with a way to disable the feature.</li></ul>
<div><br>
</div>
</div>
</div>
<div>I know we won&#39;t be looking at this Thursday but its there for revi=
ew before the F2F and we could peek at it if we want to.</div>
<div><br>
</div>
<div>Cheers,</div>
<div><br>
</div>
<div>Smith<br>
<br>
/**<br>
=C2=A0 =C2=A0 Smith Kennedy<br>
=C2=A0 =C2=A0 HP Inc.<br>
*/ </div>
<br>
</div>
</div>

_______________________________________________<br>
ipp mailing list<br>
<a href=3D"mailto:[email protected]" target=3D"_blank">[email protected]</a><br>
<a href=3D"https://www.pwg.org/mailman/listinfo/ipp" rel=3D"noreferrer" tar=
get=3D"_blank">https://www.pwg.org/mailman/listinfo/ipp</a><br>
</blockquote></div></div>

--00000000000053b713064964d050--

--===============5393805794009664355==
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

--===============5393805794009664355==--