attachment
<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Smith,<div><br><div><div>On Feb 10, 2014, at 5:51 PM, Kennedy, Smith (Wireless Architect) <<a href="mailto:smith.kennedy@hp.com">smith.kennedy@hp.com</a>> wrote:</div><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Hi there,<div><br></div><div>I agree that Push should be optional.<div><br></div><div>Would we imagine that a client would filter on the Push URI schemes it supported? If so, Pete’s key with a value listing the supported schemes is preferable.</div></div></div></blockquote><div><br></div>See my other message to Ira; I don't see clients doing this, if for any other reason that having the printer push the content to a destination is simply a software optimization - the client is perfectly capable of pulling the content and forwarding it to the destination on its own.</div><div><br><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div><div>For advertising Push via DNS-SD, the design decision should come down to balancing the size of the TXT record against the desire to discover or filter this capability using purely the values in the TXT record vs. having to do a follow-up interrogation, which is generally expensive and not desirable.</div></div></div></blockquote><div><br></div>I generally think we should limit capabilities in the TXT record to those that cannot be easily simulated in software such as color support or things that have obvious utility/convenience to end users such as auto-duplex, auto-document-feeder, etc.</div><div><br></div><div>Push scan support can be easily simulated in software and may be preferable to MFD-provided push support for things like emailing confidential documents - the client has no idea what security policies are in place for the MFD's email gateway but it *will* know the user's email gateway configuration.</div><div><br></div><div><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div><div>Also, should IPP Scan include a way for the MFD to find Push scan destinations?</div></div></div></blockquote><br></div><div>That is an interesting idea, but I think it should be out-of-scope for IPP Scan since it applies to any destination URI (not just push scan), would be fairly involved on its own, and there are existing definitions of Bonjour and LDAP services that can be used by an implementation (think LDAP email directories that most MFDs already support today...)</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>