attachment-0002
<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; ">Kelly,<div><br></div><div>Comments below...</div><div><br></div><div><br></div><div><div><div>On 2013-02-15, at 9:58 PM, kdLucas <<a href="mailto:kdlucas@google.com">kdlucas@google.com</a>> wrote:</div><blockquote type="cite">Google has drafted a local discovery specification that is based loosely on mDNS. You may recall we asked for input on this while we were researching which protocol to use.<div><br></div><div>Here is our draft, and we'd appreciate any feedback you may have. We hope to implement this over the next few months so it would help if you provided comments within the next few weeks.</div>
</blockquote><br></div><div>OK, so some specific feedback:</div><div><br></div><div>0. Are you also aware of the work in the IETF to extend mDNS beyond subnets?</div><div><div><br></div><div> (<a href="http://tools.ietf.org/html/draft-lynn-mdnsext-requirements-01">http://tools.ietf.org/html/draft-lynn-mdnsext-requirements-01</a>)</div><div><br></div></div><div>1. I'm not happy with the name of the "base_url" key; "server", "base", "url"? Shorter is better for TXT records.</div><div><br></div><div>2. The "type" key in the TXT record is unnecessary; clients can simply browse for the subtypes they are interested in and correlate using the service name.</div><div><br></div><div>3. The "id" key looks like a UUID. If so, it should be documented as such.</div><div><br></div><div>4. The "ds" key doesn't really belong here - TXT records don't generally get updated that frequently and typically have a TTL value of at least several minutes.</div><div><br></div><div>5. The "cs" key is probably ok since the connection state won't change that often, but I think having an explicit "cs=not-configured" value might be useful?</div><div><br></div><div>6. You specifically mention IPv4 link-local, but you also want IPv6 link-local, too, right?</div><div><br></div><div>7. How does one provide a job ticket when printing directly to the printer?</div><div><br></div><div>
<span class="Apple-style-span" style="border-collapse: separate; border-spacing: 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; font-size: medium; "><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><br />--
<br />This message has been scanned for viruses and
<br />dangerous content by
<a href="http://www.mailscanner.info/"><b>MailScanner</b></a>, and is
<br />believed to be clean.
</body></html>