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; -webkit-line-break: after-white-space;">Ira,<div><br><div><div>On Jun 16, 2014, at 11:02 AM, Ira McDonald <<a href="mailto:blueroofmusic@gmail.com">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>Then we need to define it and its requirements.</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>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><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>That is indeed a simple solution, but let's not make it an opaque blob.</div><div><br><div>
<span class="Apple-style-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; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span class="Apple-style-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; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">_________________________________________________________<br>Michael Sweet, Senior Printing System Engineer, PWG Chair</div></span></span>
</div>
<br></div></body></html>