attachment
<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi Mike,<div class=""><br class=""></div><div class=""><blockquote type="cite" class=""><div class="">TimeSource (String) system-time-source-configured (type2 keyword | name(MAX))<br class=""></div></blockquote><br class=""></div><div class="">How is this attribute supposed to work? Is this supposed to pertain to NTP / SNTP?</div><div class=""><br class=""><div class="">
Smith<br class=""><br class="">/**<br class=""> Smith Kennedy<br class=""> HP Inc.<br class="">*/
</div>
<div><br class=""><blockquote type="cite" class=""><div class="">On Aug 1, 2019, at 3:08 PM, Michael Sweet via ipp <<a href="mailto:ipp@pwg.org" class="">ipp@pwg.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252" class="">
<div class="">All,<br class="">
<br class="">
At today's IPP workgroup conference call we discussed adding the printer-firmware-xxx attributes that are being registered separately to the IPP System Service specification, as well as additional top-level System Status attributes that expose both the firmware and other attributes from PWG 5110.1-2013: PWG Hardcopy Device Health Assessment Attributes. Ira and I have an action item to review that specification and make recommendations about which attributes should be added, so here is my list:<br class="">
<br class="">
5110.1 Attribute IPP System Status Attribute<br class="">
------------------------------------------- ---------------------------<br class="">
FirmwareName (String*) system-firmware-name (1setOf name(MAX))<br class="">
FirmwarePatches (String*) system-firmware-patches (1setOf text(MAX))<br class="">
FirmwareStringVersion (String*) system-firmware-string-version (1setOf text(MAX))<br class="">
FirmwareVersion (OctetArray*) system-firmware-version (1setOf octetString(64))<br class="">
ResidentApplicationName (String*) system-resident-application-name (1setOf name(MAX))<br class="">
ResidentApplicationPatches (String*) system-resident-application-patches (1setOf text(MAX))<br class="">
ResidentApplicationStringVersion (String*) system-resident-application-string-version (1setOf text(MAX))<br class="">
ResidentApplicationVersion (OctetArray*) system-resident-application-version (1setOf octetString(MAX))<br class="">
TimeSource (String) system-time-source-configured (type2 keyword | name(MAX))<br class="">
UserApplicationName (String*) system-user-application-name (1setOf name(MAX))<br class="">
UserApplicationPatches (String*) system-user-application-patches (1setOf text(MAX))<br class="">
UserApplicationStringVersion (String*) system-user-application-string-version (1setOf text(MAX))<br class="">
UserApplicationVersion (OctetArray*) system-user-application-version (1setOf octetString(64))<br class="">
<br class="">
* = multiple values allowed<br class="">
<br class="">
Some additional notes:<br class="">
<br class="">
- I've limited the xxx-version attributes to 64 octets since that is what the System service limits things (because that's what the TNC binding limits things to...)<br class="">
- Currently the xxx-patches string is not exposed as a Resource Status attribute, but we could easily add that and the corresponding operation attribute as the source of that information.<br class="">
- Currently we do not differentiate between User applications/software and Resident applications/software in the system service spec. Presumably the resident applications are baked into the firmware and won't show up as separate resources, while user applications are separate, "uploadable" executable-software resources?<br class="">
- I have omitted all of the network configuration/state attributes since I figure those would be limited by the network security infrastructure and can be separately queried at that level. My focus is on things an administrator might need to manage the HCD's operating configuration and maintenance.<br class="">
<br class="">
________________________<br class="">
Michael Sweet<br class="">
<br class="">
<br class="">
<br class="">
_______________________________________________<br class="">
ipp mailing list<br class="">
<a href="mailto:ipp@pwg.org" class="">ipp@pwg.org</a><br class="">
<a href="https://protect-us.mimecast.com/s/prFQC73z5zuApQY0lCWRhEG?domain=pwg.org" class="">https://www.pwg.org/mailman/listinfo/ipp</a><br class="">
</div>
</div></blockquote></div><br class=""></div></body></html>