Re: [mdnsext] Wide Area DNS-Based Service Discovery walkthrough

Michael Sweet <msweet@apple.com> Thu, 14 March 2013 14:21 UTC

Return-Path: <msweet@apple.com>
X-Original-To: mdnsext@ietfa.amsl.com
Delivered-To: mdnsext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 84BA811E814E for <mdnsext@ietfa.amsl.com>; Thu, 14 Mar 2013 07:21:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level:
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ONzdEYFKcByB for <mdnsext@ietfa.amsl.com>; Thu, 14 Mar 2013 07:21:45 -0700 (PDT)
Received: from mail-out.apple.com (mail-out.apple.com [17.151.62.50]) by ietfa.amsl.com (Postfix) with ESMTP id 017CB11E8141 for <mdnsext@ietf.org>; Thu, 14 Mar 2013 07:21:45 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7bit
Content-type: text/plain; CHARSET="US-ASCII"
Received: from relay4.apple.com ([17.128.113.87]) by mail-out.apple.com (Oracle Communications Messaging Server 7u4-23.01 (7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTP id <0MJN00648MJX88P1@mail-out.apple.com> for mdnsext@ietf.org; Thu, 14 Mar 2013 07:21:44 -0700 (PDT)
X-AuditID: 11807157-b7fe56d00000700c-a6-5141dcf7edc1
Received: from [17.153.26.213] (Unknown_Domain [17.153.26.213]) (using TLS with cipher AES128-SHA (128/128 bits)) (Client did not present a certificate) by relay4.apple.com (Apple SCV relay) with SMTP id FA.96.28684.8FCD1415; Thu, 14 Mar 2013 07:21:44 -0700 (PDT)
From: Michael Sweet <msweet@apple.com>
In-reply-to: <16853.1363268365@sandelman.ca>
Date: Thu, 14 Mar 2013 10:21:43 -0400
Message-id: <DC80FC69-E991-4565-867E-F61E2609B820@apple.com>
References: <4D59FB04-50A3-4FF6-B8B7-E222C1623A32@apple.com> <16853.1363268365@sandelman.ca>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.1503)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrFLMWRmVeSWpSXmKPExsUiOFPqqu6PO46BBjfbjSx6DvWzW5xccorJ 4si3WAdmj60nf7B5LFnyk8mjZc4e5gDmKC6blNSczLLUIn27BK6Mjh2rWAtaOSrmb93E3MC4 n62LkZNDQsBE4sPLTiYIW0ziwr31YHEhgV4miQ+vDLsYOTiEBTwkjp82AwnzCuhJXPv2lR3E ZhbQkrjx7yVYK5uAmsTvSX2sIDangI7E356lYDaLgKrEuRfzGCHqlSVWTLvBBGFrSyxb+JoZ YqaNxPad+6HWxkjseLgSbL4I0K7lR54xQpwmK/H6+RuWCYz8s5CcMQvJGbOQjF3AyLyKUaAo NSex0kQvsaAgJ1UvOT93EyMoBBsKw3cw/ltmdYhRgINRiYd3R4dDoBBrYllxZe4hRgkOZiUR Xk8vx0Ah3pTEyqrUovz4otKc1OJDjNIcLErivBs67AOFBNITS1KzU1MLUotgskwcnFINjJOX LZ+8aUavbMfbqZXH/kS5MOid9bzC5RoQdIHVgDN0jkrrnlepL6I8DarOKd1M4b8g+qRi+oaL 33Yqpk9gN1h7ZnKwxLR/bq3uD+2nXJqVf+dd075tay4LBkYF/ZhV0+EbZPKIQfnc1atKKbnH JWb2LznAd7WH1Sk46fsOv0kXLm7mXHD1aagSS3FGoqEWc1FxIgC7U2nTPQIAAA==
Cc: IETF mdnsext <mdnsext@ietf.org>
Subject: Re: [mdnsext] Wide Area DNS-Based Service Discovery walkthrough
X-BeenThere: mdnsext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion of extensions to Bonjour \(mDNS and DNS-SD\) for routed networks." <mdnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mdnsext>, <mailto:mdnsext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mdnsext>
List-Post: <mailto:mdnsext@ietf.org>
List-Help: <mailto:mdnsext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mdnsext>, <mailto:mdnsext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Mar 2013 14:21:45 -0000

Michael,

On 2013-03-14, at 9:39 AM, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
> 
> Thanks for that writeup.
> 
> Is there some way for an OSX box to learn what vendor specific printer drivers
> to load from SD?  I assume that OSX can also do the generic thing too?

Part of the whole discovery process gets the TXT record for the service which provides things like make-and-model, product string, etc.  OS X uses that to locate an appropriate driver.

Also in that TXT record is a priority for the protocol - LPD (_printer), AppSocket (_pdl-datastream), and IPP (_ipp) are the common ones.  OS X queries the TXT record for each of the supported print protocols and uses the priority value to choose which protocol to use. The priority value is set by the manufacturer and is sometimes available as a configuration option in the printer's web interface...

_________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair