Professional Documents
Culture Documents
htm l
1. Short name of protocol, fourteen characters maximum, conforming to normal DNS host name rules: Only
lower-case letters, digits, and hyphens; must begin and end with lower-case letter or digit.
2. Longer, descriptive name of protocol.
3. Name and email address of responsible person.
4. URL giving description of protocol. (Or statement that the protocol is proprietary.)
5. Primary Transport Protocol. ("_udp" or "_tcp", only needed for historical reasons, to determine correct SRV service
type)
6. List of defined TXT record keys (see draft-cheshire-dnsext-dns-sd.txt, Section 6) for this service or URL reference to
document describing defined keys.
The primary historical list of DNS SRV (RFC 2782) service type names for existing protocols with well-known port
numbers is given in the IANA list of assigned port names and numbers. However, that list does not include any
information about the defined DNS-SD TXT keys, and that list includes only protocols that have fixed well-known port
numbers, which is unfortunate, because one of the big benefits of DNS SRV is that it obviates the need for fixed port
numbers in most cases.
For applications that need a fixed well-known port number, you should list your protocol in both places. When you fill
out the IANA "Application for User (Registered) Port Number" form to get a registered port number for your application
protocol, the last section of that form is the space for the fourteen-character service protocol name, used by SRV records
and DNS-SD.
For applications that do not need a fixed well-known port number, you should list your protocol only on this DNS SRV
list. Before you send your email, check the IANA list of assigned port names and numbers to make sure that your chosen
protocol name is not already in use for a different protocol.
As soon as the correct IANA procedures are in place and formalized, the two lists will be re-unified and managed by
IANA.
Unless explicitly specified otherwise, all protocols are assumed to be "_protoname._tcp", not "_protoname._udp". Protocols
that can run over either UDP or TCP (e.g. NFS) are usually advertised using whichever transport is considered the 'normal'
or 'primary' mode of operation (and clients should attempt communication with the service using either or both transports,
as appropriate for the client). Protocols that run only over UDP should of course advertise as "_protoname._udp".
actionitems ActionItems
Sailalong Software <CustomerService at Sailalong.com>
Defined TXT keys: None
addressbook Address-O-Matic
Massimiliano Ribuoli and Marco Stefani <support at address-o-matic.com>
Defined TXT keys: None
airprojector AirProjector
appelezvous Appelezvous
Marco Piovanelli <support at ovolab.com>
Protocol description: Proprietary
Defined TXT keys: None
appletv Apple TV
Amandeep Jawa <daap at apple.com>
Defined TXT keys: txtvers, PrVs, OSsi, MniT
aquamon AquaMon
Defined TXT keys: None
astralite Astralite
async address-o-sync
Markus Brand <address-o-sync at slamslash.com>
Defined TXT keys: None
boundaryscan Proprietary
Uwe Ziegler, Goepel electronic GmbH, <u.ziegler@goepel.com>
Protocol description: Proprietary
Primary Transport Protocol: UDP
Defined TXT keys: blocked=<name of the device>, version=<firmware/instrument controller versio
caltalk CalTalk
Joe Groff <arcata at gmail.com>
Defined TXT keys: None
cpnotebook2 NoteBook 2
Circus Ponies Support <support at circusponies.com>
Protocol description: Proprietary
Defined TXT keys: None
cytv CyTV
Network streaming for Elgato EyeTV
Andreas Junghans <cytv at lucid-cake.net>
Defined TXT keys: None
difi EyeHome
Elgato <support at elgato.com>
Defined TXT keys: None
dropcopy DropCopy
10base-t Interactive <support at 10base-t.com>
Defined TXT keys: None
earphoria Earphoria
Rogue Amoeba <earphoria at rogueamoeba.com>
Defined TXT keys: None
embrace DataEnvoy
Rob MacGregor <rob.macgregor at sympatico.ca>
Defined TXT keys: None
facespan FaceSpan
Kerry Hazelgren <hazelgren at facespan.com>
Defined TXT keys: None
faxstfx FAXstf
Smith Micro <cs at smithmicro.com>
Defined TXT keys: None
fish Fish
Oriol Ferrer Mesia <tm05788 at salleurl.edu>
Defined TXT keys: None
Possible TXT records defined and their values (replace uppercase text with enumerations from
txtvers=1
fix=APPLICATIONVERSION
fix supported=APPLICATIONVERSION[,APPLICATIONVERSION, ... ,APPLICATIONVERSION]
fixt=SESSIONVERSION
fjork Fjork
John Schilling <john at jschilling.net>
Defined TXT keys: None
gbs-smp SnapMail
Eric Harris-Braun <eric at glassbead.com>
Defined TXT keys: None
gbs-stp SnapTalk
Eric Harris-Braun <eric at glassbead.com>
Defined TXT keys: None
growl Growl
Defined TXT keys: None
guid Special service type for resolving by GUID (Globally Unique Identifier)
Defined TXT keys: Varies; Depends on type of service being offered/resolved
Although DNS-SD does not recommend or advocate using GUIDs as the primary name
of an offered service (why not?), it does support use of GUIDs as service names
where developers want to use them that way.
Typically users do not browse for GUIDs. They are not user-friendly and not very
informative. Typically, the service is advertised as usual, using a user-friendly
name. One of the TXT record attributes is a GUID for the service instance.
Once the user has browsed and chosen the desired service instance via its user-friendly
name, the service is resolved, the TXT record is retrieved, and the GUID is stored.
A given network service instance is therefore being advertised two ways, for example:
<User-Friendly-Name>._ptp._tcp.local
<GUID>._guid._tcp.local
On subsequent accesses to the service, the GUID-based name is resolved, and that
particular service instance is discovered, even if the user has subsequently
changed the user-friendly name to something else.
Note: Although each different logical service type needs to have its own different
DNS-SD service type, all GUID-based names use the same pseudo-type: "_guid._tcp".
There is no possibility of name conflict because (by definition) GUIDs are globally unique.
h323 H.323 Real-time audio, video and data communication call setup protocol
Will MacDonald <will at codian.com>
Defined TXT keys: None
hotwayd Hotwayd
Defined TXT keys: None
hpr-db Identifies systems that house databases for the Remote Build System and Remote Test System
Jeffrey J. Walls <jeff.walls at hp.com>
Protocol description: Proprietary
Defined TXT keys: bld, tst, mstr
hpr-toollnx HP Remote System that houses compilers and tools for Linux-based Systems
Jeffrey J. Walls <jeff.walls at hp.com>
Protocol description: Proprietary
Defined TXT keys: rh73, rhel3, rhel4, deb31, suse102
hpr-toolwin HP Remote System that houses compilers and tools for Microsoft Windows Systems
Jeffrey J. Walls <jeff.walls at hp.com>
Protocol description: Proprietary
Defined TXT keys: xp, vista
hydra SubEthaEdit
TheCodingMonkeys <monkeys at codingmonkeys.de>
Defined TXT keys: None
iax Inter Asterisk eXchange, ease-of-use NAT friendly open VoIP protocol
Benjamin Kowarsch <benjamin at sunrise-tel.com> November 2004
Protocol Description: http://www.cornfed.com/iax.pdf (work in progress)
Primary Transport Protocol: UDP
Defined TXT keys:
auth plaintext | md5 | rsakeys
userid alphanumeric, additionally '_', '+', '-'
secret any printable ASCII characters
domain any DNS domain name or IP address
extension alphanumeric, additionally '*', '#', '_', '+', '-'
context alphanumeric, additionally '_', '+', '-'
trunk yes | no | 0 | 1
welcome alphanumeric, additionally '*', '#', '_', '+', '-'
voicemail alphanumeric, additionally '*', '#', '_', '+', '-'
reception alphanumeric, additionally '*', '#', '_', '+', '-'
echotest alphanumeric, additionally '*', '#', '_', '+', '-'
ivrtest alphanumeric, additionally '*', '#', '_', '+', '-'
All of these TXT record keys are optional, they may be omitted.
Further keys may be added in the future.
ichalkboard iChalk
Math Game House Software <mathgamehouse at mac.com>
Defined TXT keys: None
iconquer iConquer
Andrew Zamler-Carhart <andrew at zamler-carhart.com>
Defined TXT keys: None
ilynx iLynX
iOS Software <ios at free.fr>
Defined TXT keys: None
imidi iMidi
Robert Grant <rob at grantedsw.com>
Defined TXT keys: None
ipbroadcaster IP Broadcaster
10base-t Interactive <support at 10base-t.com>
Defined TXT keys: None
isparx iSparx
Philipp Dreiss <dreiss at isparx.de>
Defined TXT keys: None
ishare iShare
Steve Dekorte <steve at dekorte.com>
Defined TXT keys: None
isticky iSticky
Insist <support at isticky.net>
Defined TXT keys: None
istorm iStorm
Math Game House Software <mathgamehouse at mac.com>
jeditx Jedit X
Satoshi Matsumoto <satoshi at artman21.co.jp>
Protocol description: http://www.artman21.net
Defined TXT keys: None
jtag Proprietary
Uwe Ziegler, Goepel electronic GmbH, <u.ziegler@goepel.com>
Protocol description: Proprietary
Defined TXT keys: blocked=<name of the device>, version=<firmware/instrument controller versio
kerberos Kerberos
B. Clifford Neuman <bcn at isi.edu>
Description: draft-ietf-krb-wg-krb-dns-locate-03.txt
Discovery Protocol: RFC 2782
lapse Gawker
Phil Piwonka <wnka at users.sourceforge.net>
Defined TXT keys: None
liaison Liaison
Brian Cully <shmit at kublai.com>
Defined TXT keys: None
lobby Gobby
0x539 dev group gobby.0x539.de
Defined TXT keys: None
model=value (string)
version=value (string)
lxi LXI
Nick Barendt <nbarendt at vxitech.com>
Protocol description: Currently in draft; When published, will be found here: www.lxistandard.
Defined TXT keys: txtvers, *IDN?=<response defined by IEEE 488; e.g., manufacturer, model, ser
macfoh MacFOH
Shaun Wexler <dev at macfoh.com>
Defined TXT keys: None
mcrcp MediaCentral
equinux <mediacentral at equinux.comdu>
Defined TXT keys: None
mxs MatrixStore
Object Matrix <support at object-matrix.com>
Protocol description: Proprietary
Defined TXT keys: None
mxs.system.id=<system id>
mxs.system.version=<system layer version>
mxs.cluster.id=<cluster id the system belongs to>
netrestore NetRestore
Mike Bombich <bombich at apple.com>
Defined TXT keys: message, status, progress
newton-dock Escale
Paul Guyot <pguyot at kallisys.net>
Defined TXT keys: None
ntx Tenasys
Carl Ellis <carl.ellis at tenasys.com>
Protocol description: Proprietary
Primary Transport Protocol: UDP
Defined TXT keys: None
odabsharing OD4Contact
Objective Decision <od4contact at objective-decision.com>
Defined TXT keys: None
omni-bookmark OmniWeb
The Omni Group <info at omnigroup.com>
Defined TXT keys: None
prolog Prolog
Mike Brady <brady at cs.tcd.ie>
Protocol description: Proprietary
Defined TXT keys: version=<version number>
rce PowerCard
DeVoeSquared <support at devoesquared.com>
Defined TXT keys: None
rendezvouspong RendezvousPong
Math Game House Software <mathgamehouse at mac.com>
Defined TXT keys: None
rsync Rsync
Andrew Tridgell <tridge at samba.anu.edu.au>
Protocol description: http://samba.anu.edu.au/rsync
Defined TXT keys: None
sandvox Sandvox
Karelia Software
Protocol description: Proprietary
Defined TXT keys: None
schick Schick
Heiko Kretschmer <info at wurst-wasser.net>
Defined TXT keys: None
scone Scone
James Moore <jam at wirerimmed.com>
see SubEthaEdit 2
TheCodingMonkeys <monkeys at codingmonkeys.de>
Defined TXT keys: txtvers=1, name=<Full Name>, userid=<User ID>, version=2
seeCard seeCard
Stefan Pantke <sales at turingart.com>
Defined TXT keys: None
shell like exec, but automatic authentication is performed as for login server.
Defined TXT keys: None
shoutcast Nicecast
Rogue Amoeba <nicecast at rogueamoeba.com>
Defined TXT keys: None
skype Skype
Protocol description: http://skype.com/products/explained.html
Defined TXT keys: platform, status, auth, rversion, version
spl-itunes launchTunes
David Nanian <dnanian at shirt-pocket.com>
Defined TXT keys: None
spr-itunes netTunes
David Nanian <dnanian at shirt-pocket.com>
Defined TXT keys: None
strateges Strateges
Jean-Olivier Lanctot-D. <jolivierld at clichesw.com>
Defined TXT keys: None
svn Subversion
CollabNet www.collab.net
Defined TXT keys: None
teleport teleport
Julien Robert <jul at abyssoft.com>
Primary Transport Protocol: UDP
Defined TXT keys: None
telnet Telnet
Service name originally allocated for Jon Postel <postel at isi.edu>
Now advertised and browsed-for by numerous independent
server and client implementations.
Protocol description: RFC 854
Defined TXT keys: u=<username> p=<password>
timbuktu Timbuktu
Neal Trautman <neal at netopia.com>
Protocol description: Proprietary
Defined TXT keys: None
tomboy Tomboy
Alex Graveley <alex at beatniksoftware.com>
Protocol description: http://www.beatniksoftware.com/tomboy
Defined TXT keys: None
tryst Tryst
Francisco Ryan Tolmasky <ftolmasky at adelphia.net>
Defined TXT keys: None
tuneranger TuneRanger
Acertant Technologies, Inc.
Protocol description: Proprietary
Defined TXT keys: None
ubertragen Ubertragen
Widgetschmie.de
Defined TXT keys: None
utest uTest
Gregory Power <gpower at apple.com>
Defined TXT keys: None
volley Volley
David Catmull <uncommon at uncommonplace.com>
vue4rendercow VueProRenderCow
Defined TXT keys: None
whamb Whamb
Whamb <support at whamb.com>
Defined TXT keys: None
ws Web Services
Andrew Donoho <awd at us.ibm.com>
Defined TXT keys: None
Subtypes: The specific Web Services-based protocol being offered.
Note: Browsing for _ws._tcp as a generic service is useful only in development tools.
For any given application, it should browse for the specific semantic service (subtype
of _ws._tcp) it requires. Browsing for _ws._tcp would simply find all services that
happened to be built on top of Web Services technology, without regard for whether
the service they provide is at all relevant to what this application wants to do.
xgrid Xgrid
David Kramer <dkramer at apple.com>
Defined TXT keys: None
The following services have been observed 'in the wild' using tools like Bonjour Browser, but they have not been officially
registered at DNS-SD.org, and they are not legal SRV service type names according to IANA rules because they are more
than fourteen characters long and/or contain illegal characters.
clipboardsharing ClipboardSharing
Erik Lagercrantz <erik at lagercrantz.ath.cx>
pop_2_ambrosia Pop-Pop
profCastLicense ProfCast
http://www.dns-sd.org