attachment
<div dir="ltr"><div><div><div><div><div>Hi Mike,<br><br></div>Agreed.<br><br></div>It shouldn't be an opaque blob - the "access-type" should be sufficiently fine-grained<br></div>to allow explicit multi-factor scenarios.<br>
<br></div>And Pete and I want to state that binary data MUST be sent as straight "octetString" <br>and and text data (e.g., password) MUST be sent as UTF-8 (with no trailing '\0').<br><br></div><div>The only downside (potentially pretty large for explicit multi-factor "access-type"<br>
</div><div>values is rapid loss of interoperability when vendors roll their own name values<br></div><div>for combinations we didn't anticipate.<br><br></div><div>Cheers,<br></div><div>- Ira<br><br></div><div class="gmail_extra">
<br clear="all"><div><div dir="ltr">Ira McDonald (Musician / Software Architect)<br>Co-Chair - TCG Trusted Mobility Solutions WG<br>Chair - Linux Foundation Open Printing WG<br>Secretary - IEEE-ISTO Printer Working Group<br>
Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG<br>IETF Designated Expert - IPP & Printer MIB<br>Blue Roof Music / High North Inc<br><a style="color:rgb(51,51,255)" href="http://sites.google.com/site/blueroofmusic" target="_blank">http://sites.google.com/site/blueroofmusic</a><br>
<a style="color:rgb(102,0,204)" href="http://sites.google.com/site/highnorthinc" target="_blank">http://sites.google.com/site/highnorthinc</a><br>mailto: <a href="mailto:blueroofmusic@gmail.com" target="_blank">blueroofmusic@gmail.com</a><br>
Winter 579 Park Place Saline, MI 48176 <a href="tel:734-944-0094" value="+17349440094" target="_blank">734-944-0094</a><br>Summer PO Box 221 Grand Marais, MI 49839 <a href="tel:906-494-2434" value="+19064942434" target="_blank">906-494-2434</a><br>
<br><div style="display:inline"></div><div style="display:inline"></div><div style="display:inline"></div>
<div></div><div></div><div></div><div></div></div></div>
<br><br><div class="gmail_quote">On Mon, Jun 16, 2014 at 11:19 AM, Michael Sweet <span dir="ltr"><<a href="mailto:msweet@apple.com" target="_blank">msweet@apple.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">Ira,<div><br><div><div><div>On Jun 16, 2014, at 11:02 AM, Ira McDonald <<a href="mailto:blueroofmusic@gmail.com" target="_blank">blueroofmusic@gmail.com</a>> wrote:</div><blockquote type="cite">
<div dir="ltr"><div><div><div><div><div><div>Hi Mike,<br><br></div>The reason for some sparse syntax was to support Pete's use case (over the phone)<br></div>of wanting two or more credentials for the *same* destination (i.e., multi-factor auth is<br>
</div>in use). This is a critically important real-world use case.<br></div></div></div></div></blockquote><div><br></div></div>Then we need to define it and its requirements.</div><div><div><br><blockquote type="cite">
<div dir="ltr"><div><div>With the straight parallel 1setOf approach, there has to be a nested collection to hold<br>the auth-type, auth-data, etc. for each credential for one destination - ugly and fragile.<br></div></div>
</div></blockquote><div><br></div></div>If the auth type defines multiple credentials then those can be provided via separate data values in the 1setOf, or using type-specific member attributes. In short, we need to define what the attributes contain, not provide a BLOB holder that will become an interoperability nightmare.</div>
<div><div><br><blockquote type="cite"><div dir="ltr"><div><div>Pete and I particularly liked the use of the simple (1setOf octetString(MAX)) with auto<br>concatenation to support large credentials (X.509 certificates, etc.).<br>
</div></div></div></blockquote></div><div><br></div></div>That is indeed a simple solution, but let's not make it an opaque blob.</div><div><div><br><div>
<span style="border-collapse:separate;color:rgb(0,0,0);font-family:'Andale Mono';font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="border-collapse:separate;color:rgb(0,0,0);font-family:'Andale Mono';font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><div style="word-wrap:break-word">
_________________________________________________________<br>Michael Sweet, Senior Printing System Engineer, PWG Chair</div></span></span>
</div>
<br></div></div></div></blockquote></div><br></div></div>