attachment
<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri",sans-serif;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">Hi,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Canon has some questions about the draft Accounting specification and its use of IPP privacy attributes. Please reference the following specifications:<o:p></o:p></p>
<p class="MsoNormal">- Job Accounting with IPP v1.0 <a href="https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippaccounting10-20191022.pdf">
https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippaccounting10-20191022.pdf</a><o:p></o:p></p>
<p class="MsoNormal">- IPP Privacy Attributes v1.0 (PRIVACY) <a href="https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippprivacy10-20180403.pdf">
https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippprivacy10-20180403.pdf</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">The Job Accounting spec requires printers to conform to the IPP Privacy Attributes v1.0 specification. Per the IPP Privacy Attributes spec, a printer can define what job attributes are considered private as defined in section 4.1.3:
<o:p></o:p></p>
<p class="MsoPlainText">4.1.3 job-privacy-attributes<o:p></o:p></p>
<p class="MsoPlainText"> 'all': All attributes except "job-id", "job-uri", "job-uuid", and "job-printer-uri" are private.<o:p></o:p></p>
<p class="MsoPlainText"> 'default': All Job Description and Template attributes are private.<o:p></o:p></p>
<p class="MsoPlainText"> 'job-description: All Job Description attributes are private.<o:p></o:p></p>
<p class="MsoPlainText"> 'job-template': All Job Template attributes are private.<o:p></o:p></p>
<p class="MsoPlainText"> 'none': No attributes are private.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoPlainText">On the other hand, the following attributes are considered explicitly to contain personal data according to Accounting v1.0.<o:p></o:p></p>
<p class="MsoPlainText">7.3 Privacy and Data Collection<o:p></o:p></p>
<p class="MsoPlainText"> "job-originating-user-name" and "job-originating-user-uri":<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoPlainText">As an example, let’s say the printer does not collect the "job-name" attribute but collects other Job Description attributes.<o:p></o:p></p>
<p class="MsoPlainText">Could another keyword besides 'all'/'default'/'job-description'/'job-template'/'none' be more appropriate for filling in job-privacy-attributes?<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Canon’s assumption is that PWG members might want fewer privacy items to show up on an informed consent dialog, which means coarser granularity purposely defined in the spec. (Accounting v1.0 - "4.4 Informed Consent")<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Is Canon’s understanding correct?<o:p></o:p></p>
<p class="MsoPlainText">Could you tell us the background and logic behind the use of the IPP Privacy Attributes by the Job Accounting spec?<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">Thank you,<o:p></o:p></p>
<p class="MsoPlainText">Rick<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>