Debian Codegraph @

rfc2609.html

raw
1 <pre>Network Working Group E. Guttman
2 Request for Comments: 2609 C. Perkins
3 Updates: <a href="./rfc2165">2165</a> J. Kempf
4 Category: Standards Track Sun Microsystems
5 June 1999
6
7
8 <span class="h1">Service Templates and Service: Schemes</span>
9
10 Status of This Memo
11
12 This document specifies an Internet standards track protocol for the
13 Internet community, and requests discussion and suggestions for
14 improvements. Please refer to the current edition of the "Internet
15 Official Protocol Standards" (STD 1) for the standardization state
16 and status of this protocol. Distribution of this memo is unlimited.
17
18 Copyright Notice
19
20 Copyright (C) The Internet Society (1999). All Rights Reserved.
21
22 Abstract
23
24 The "service:" URL scheme name is used to define URLs (called
25 "service: URLs" in this document) that are primarily intended to be
26 used by the Service Location Protocol in order to distribute service
27 access information. These schemes provide an extensible framework
28 for client-based network software to obtain configuration information
29 required to make use of network services. When registering a
30 service: URL, the URL is accompanied by a set of well-defined
31 attributes which define the service. These attributes convey
32 configuration information to client software, or service
33 characteristics meaningful to end users.
34
35 This document describes a formal procedure for defining and
36 standardizing new service types and attributes for use with the
37 "service:" scheme. The formal descriptions of service types and
38 attributes are templates that are human and machine understandable.
39 They SHOULD be used by administrative tools to parse service
40 registration information and by client applications to provide
41 localized translations of service attribute strings.
42
43
44
45
46
47
48
49
50
51
52 <span class="grey">Guttman, et al. Standards Track [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc2609">RFC 2609</a> Service Templates and URLs June 1999</span>
55
56
57 Table of Contents
58
59 1. Introduction 2
60 <a href="#section-1.1">1.1</a>. Terminology . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
61 <a href="#section-1.2">1.2</a>. Service Location Protocol . . . . . . . . . . . . . . <a href="#page-5">5</a>
62 <a href="#section-1.2.1">1.2.1</a>. Compatibility with SLPv1 . . . . . . . . . . . <a href="#page-5">5</a>
63 2. Service URL Syntax and Semantics 5
64 <a href="#section-2.1">2.1</a>. Service URL Syntax . . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
65 <a href="#section-2.2">2.2</a>. Service URL Semantics . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
66 <a href="#section-2.3">2.3</a>. Use of service: URLs . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
67 <a href="#section-2.4">2.4</a>. Specifying the Service Type-Specific URL Syntax. . . . <a href="#page-10">10</a>
68 <a href="#section-2.5">2.5</a>. Accommodating Abstract Service Types . . . . . . . . <a href="#page-10">10</a>
69 <a href="#section-2.5.1">2.5.1</a>. Advertising Abstract Service Types . . . . . . <a href="#page-11">11</a>
70 3. Syntax and Semantics of Service Type Specifications 12
71 <a href="#section-3.1">3.1</a>. Syntax of Service Type Templates . . . . . . . . . . <a href="#page-12">12</a>
72 <a href="#section-3.2">3.2</a>. Semantics of Service Type Templates. . . . . . . . . . <a href="#page-15">15</a>
73 <a href="#section-3.2.1">3.2.1</a>. Definition of a Service Template . . . . . . . <a href="#page-15">15</a>
74 <a href="#section-3.2.2">3.2.2</a>. Service Type . . . . . . . . . . . . . . . . . <a href="#page-16">16</a>
75 <a href="#section-3.2.3">3.2.3</a>. Version Number . . . . . . . . . . . . . . . . <a href="#page-16">16</a>
76 <a href="#section-3.2.4">3.2.4</a>. Description . . . . . . . . . . . . . . . . . <a href="#page-16">16</a>
77 3.2.5. Syntax of the Service Type-specific URL Part . 17
78 <a href="#section-3.2.6">3.2.6</a>. Attribute Definition . . . . . . . . . . . . <a href="#page-17">17</a>
79 4. A Process For Standardizing New Service Types 21
80 5. IANA Considerations 22
81 6. Internationalization Considerations 24
82 <a href="#section-6.1">6.1</a>. Language Identification and Translation. . . . . . . . <a href="#page-24">24</a>
83 7. Security Considerations 25
84 A. Service Template Examples 26
85 <a href="#appendix-A.1">A.1</a>. FOO . . . . . . . . . . . . . . . . . .. . . . . . . . <a href="#page-26">26</a>
86 <a href="#appendix-A.2">A.2</a>. Abstract Service Type: Net-Transducer . . . . . . . . <a href="#page-28">28</a>
87 <a href="#appendix-A.3">A.3</a>. Concrete Service Type: Net-Transducer:Thermometer . . <a href="#page-29">29</a>
88 <a href="#appendix-A.4">A.4</a>. service: URLs and SLP . . . . . . . . . . . . . . . . <a href="#page-30">30</a>
89 B. Acknowledgments 30
90 C. References 31
91 D. Authors' Addresses 32
92 E. Full Copyright Statement 33
93
94 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
95
96 This document describes a URL scheme, called service: URL, which
97 defines network access information for network services using a
98 formal notation. In addition it describes how to define a set of
99 attributes to associate with a service: URL. These attributes will
100 allow end users and programs to select between network services of
101 the same type that have different capabilities. The attributes are
102 defined in a template document that is readable by people and
103 machines.
104
105
106
107
108 <span class="grey">Guttman, et al. Standards Track [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc2609">RFC 2609</a> Service Templates and URLs June 1999</span>
111
112
113 A client uses attributes to select a particular service. Service
114 selection occurs by obtaining the service: URL that offers the right
115 configuration for the client. Service type templates define the
116 syntax of service: URLs for a particular service type, as well as the
117 attributes which accompany a service: URL in a service registration.
118
119 Templates are used for the following distinct purposes:
120
121 1. Standardization
122
123 The template is reviewed before it is standardized. Once it is
124 standardized, all versions of the template are archived by IANA.
125
126 2. Service Registration
127
128 Servers making use of the Service Location Protocol [<a href="#ref-10" title="&quot;Service Location Protocol Version 2&quot;">10</a>] register
129 themselves and their attributes. They use the templates to
130 generate the service registrations. In registering, the service
131 must use the specified values for its attributes.
132
133 3. Client presentation of Service Information
134
135 Client applications may display service information. The
136 template provides type information and explanatory text which may
137 be helpful in producing user interfaces.
138
139 4. Internationalization
140
141 Entities with access to the template for a given service type in
142 two different languages may translate between the two languages.
143
144 A service may register itself in more than one language using
145 templates, though it has been configured by an operator who
146 registered service attributes in a single language.
147
148 All grammar encoding follows the Augmented BNF (ABNF) [<a href="#ref-8" title="&quot;Augmented BNF for Syntax Specifications: ABNF&quot;">8</a>] for syntax
149 specifications.
150
151 <span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Terminology</span>
152
153 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
154 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
155 document are to be interpreted as described in <a href="./rfc2119">RFC 2119</a> [<a href="#ref-6" title="&quot;Key Words for Use in RFCs to Indicate Requirement Levels&quot;">6</a>].
156
157
158
159
160
161
162
163
164 <span class="grey">Guttman, et al. Standards Track [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc2609">RFC 2609</a> Service Templates and URLs June 1999</span>
167
168
169 The following terminology is used for describing service: URLs.
170
171 service scheme
172
173 A URL scheme whose name starts with the string "service:" and
174 is followed by the service type name, constructed according to
175 the rules in this document.
176
177 service: URL
178
179 A URL constructed according to the service scheme definition.
180 It typically provides at least the following: The name of an
181 access protocol, and an address locating this service. The
182 service: URL may include url path information specific to the
183 type of service, as well as attribute information encoded
184 according to the URL grammar. The service: URL is used by the
185 Service Location Protocol to register and discover the location
186 of services. It may be used by other protocols and in
187 documents as well.
188
189 service type
190
191 A name identifying the semantics by which the remainder of the
192 service: URL is to be understood. It may denote either a
193 particular network protocol, or an abstract service associated
194 with a variety of protocols. If the service type denotes a
195 particular protocol, then the service type name SHOULD either
196 be assigned the name of a particular well known port [<a href="#ref-2">2</a>] by
197 convention or be the Assigned Numbers name for the service [<a href="#ref-1">1</a>].
198
199 abstract service type
200
201 A service type name which is associated with a variety of
202 different protocols. An example is given in Section A.
203 <a href="#section-2">Section 2</a> discusses various ways that abstract types can be
204 accommodated.
205
206 service registration
207
208 A service: URL and optionally a set of attributes comprise a
209 service registration. This registration is made by or on
210 behalf of a given service. The URL syntax and attributes must
211 conform to the service template for the registered service.
212
213 service template
214
215 A formal description of the service attributes and service
216 scheme associated with a particular service type.
217
218
219
220 <span class="grey">Guttman, et al. Standards Track [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc2609">RFC 2609</a> Service Templates and URLs June 1999</span>
223
224
225 <span class="h3"><a class="selflink" id="section-1.2" href="#section-1.2">1.2</a>. Service Location Protocol</span>
226
227 The Service Location Protocol version 2 [<a href="#ref-10" title="&quot;Service Location Protocol Version 2&quot;">10</a>] allows service: URLs to
228 be registered and discovered, though service: URLs may be also used
229 in other contexts.
230
231 Client applications discover service registrations by issuing queries
232 for services of a particular type, specifying the attributes of the
233 service: URLs to return. Clients retrieve the attributes of a
234 particular service by supplying its service: URL. Attributes for all
235 service registrations of a particular type can also be retrieved.
236
237 Services may register themselves, or registrations may be made on
238 their behalf. These registrations contain a service: URL, and
239 possibly attributes and digital signatures.
240
241 <span class="h4"><a class="selflink" id="section-1.2.1" href="#section-1.2.1">1.2.1</a>. Compatibility with SLPv1</span>
242
243 This document adopts the encoding conventions of SLPv2.
244
245 Compatibility with SLPv1 [[<a href="#ref-15" title="&quot;Service Location Protocol&quot;">15</a>]] is possible, if the following
246 conventions are observed:
247
248 1. Abstract service types must not be used. SLPv2 specifies the
249 use of Service URLs with abstract service types. SLPv1 does not
250 support them. Thus, a service template which is to serve both
251 SLPv1 and SLPv2 must not use abstract service types.
252
253 2. The syntax for representing opaque values in this document is
254 consistent with SLPv2. The syntax must be converted for use with
255 SLPv1. Instead of a sequence of "\FF" then "\" HEXDIG HEXDIG for
256 each byte in the opaque value, SLPv1 uses radix-64 notation.
257
258 3. Escape characters are significantly differently in SLPv1 and
259 SLPv2. Instead of using escaped byte notation for escaped
260 characters, SLPv1 uses the HTML convention `&amp;' `#' 1*DIGIT `;'.
261
262 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Service URL Syntax and Semantics</span>
263
264 This section describes the syntax and semantics of service: URLs.
265
266 <span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Service URL Syntax</span>
267
268 The syntax of the service: URL MUST conform to an 'absolute URI' as
269 defined by [<a href="#ref-5" title="&quot;Uniform Resource Identifiers (URI): Generic Syntax&quot;">5</a>]. The syntax of a service: URL differs enough from a
270 'generic URI' that it is best to treat it as an opaque URI unless a
271 specific parser for the service: URL is available.
272
273
274
275
276 <span class="grey">Guttman, et al. Standards Track [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc2609">RFC 2609</a> Service Templates and URLs June 1999</span>
279
280
281 All service: URLs have the same syntax up to the 'url-part' The
282 syntax for a service URL depends on the service type following the
283 service scheme. All service: URLs have a service access point
284 portion, indicating the address of the service to access.
285
286 The syntax for the &lt;sap&gt; field depends upon the service type
287 definition. The &lt;sap&gt; field is the service access point, and
288 describes how to access the service. In addition, although both
289 upper case and lower case characters are recognized in the &lt;service-
290 type&gt; field for convenience, the name is case-folded into lower case.
291 Service types are therefore not distinguished on the basis of case,
292 so, for example, "http" and "HTTP" designate the same service type.
293 This is consistent with general URL practice, as outlined in [<a href="#ref-5" title="&quot;Uniform Resource Identifiers (URI): Generic Syntax&quot;">5</a>].
294
295 The ABNF for a service: URL is:
296
297 service: URL = "service:" service-type ":" sap
298 service-type = abstract-type ":" url-scheme / concrete-type
299 abstract-type = type-name [ "." naming-auth ]
300 concrete-type = protocol [ "." naming-auth ]
301 type-name = resname
302 naming-auth = resname
303 url-scheme = resname
304 ; A recognized URL scheme name, standardized
305 ; either through common practice or through
306 ; approval of a standards body.
307 resname = ALPHA [ 1*(ALPHA / DIGIT / "+" / "-") ]
308 sap = site [url-part]
309 site = ipsite / atsite / ipxsite
310 ipsite = "//" [ [ user "@" ] hostport ]
311 hostport = host [ ":" port ]
312 host = hostname / hostnumber
313 hostname = *( domainlabel "." ) toplabel
314 alphanum = ALPHA / DIGIT
315 domainlabel = alphanum / alphanum *[alphanum / "-"] alphanum
316 toplabel = ALPHA / ALPHA *[ alphanum / "-" ] alphanum
317 hostnumber = ipv4-number
318 ipv4-number = 1*3DIGIT 3("." 1*3DIGIT)
319 port = 1*DIGIT
320 ; A port number must be included if the
321 ; protocol field does not have an IANA
322 ; assigned port number.
323 user = *[ uchar / ";" / "+" / "&amp;" / "=" ]
324 ipxsite = "/ipx/" ipx-net ":" ipx-node ":" ipx-socket
325 ipx-net = 8 HEXDIGIT
326 ipx-node = 12 HEXDIGIT
327 ipx-socket = 4 HEXDIGIT
328 atsite = "/at/" at-object ":" at-type "" at-zone
329
330
331
332 <span class="grey">Guttman, et al. Standards Track [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc2609">RFC 2609</a> Service Templates and URLs June 1999</span>
335
336
337 at-object = 1*31apple-char
338 at-type = 1*31apple-char
339 at-zone = 1*31apple-char
340 apple-char = ALPHA / DIGIT / safe / escaped
341 = ; AppleAscii [<a href="#ref-7">7</a>] values that are not
342 = ; from the restricted range must be escaped.
343 = ; NOTE: The escaped values do NOT correspond
344 = ; to UTF-8 values here: They are AppleAscii
345 = ; bytes.
346 url-part = [ url-path ] [ attr-list ]
347 url-path = 1 * ( "/" *xchar )
348 ; Each service type must define its
349 ; own syntax consistent
350 ; with [<a href="#ref-5" title="&quot;Uniform Resource Identifiers (URI): Generic Syntax&quot;">5</a>].
351 attr-list = 1 * ( ";" attr-asgn )
352 attr-asgn = attr-id / attr-id "=" attr-value
353 safe = "$" / "-" / "_" / "." / "~"
354 extra = "!" / "*" / "'" / "(" / ")" / "," / "+"
355 uchar = unreserved / escaped
356 xchar = unreserved / reserved / escaped
357 escaped = 1*(`\' HEXDIG HEXDIG)
358 reserved = ";" / "/" / "?" / ":" / "@" / "&amp;" / "=" / "+"
359 unreserved = ALPHA / DIGIT / safe / extra
360
361 IPX addresses [<a href="#ref-14" title="Version 1.30">14</a>] are composed of a network, node and socket number.
362 The IPX network number is a four-byte number, in network order and
363 expressed in hexadecimal, that signifies an IPX subnet. The node
364 element represents a network interface card. It is a six-byte
365 number, expressed in hexadecimal, that is usually the same as the
366 node ID of the interface card. The socket element represents a
367 specific service access point, given an IPX network and node. IPX
368 sockets are analogous to TCP/IP ports, and are not to be confused
369 with Berkeley sockets.
370
371 AppleTalk addresses [<a href="#ref-9" title="R. Andrews">9</a>] are composed of an object, type and zone.
372 The object is a human readable string. The type is an identifier,
373 not intended for human readability. The zone refers to the AppleTalk
374 Zone name, which is also human readable. The characters composing
375 these names are drawn from the AppleAscii character set [<a href="#ref-7">7</a>]. Thus,
376 they do not equate to escaped ASCII or UTF-8 characters. The
377 characters "=" and "*" are reserved and may not be included in the
378 names even in binary form.
379
380 In cases besides the AppleTalk grammar, some characters must be
381 escaped before use. To escape any character, precede the two digits
382 indicating its ASCII value by '%'.
383
384
385
386
387
388 <span class="grey">Guttman, et al. Standards Track [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc2609">RFC 2609</a> Service Templates and URLs June 1999</span>
391
392
393 <span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. Service URL Semantics</span>
394
395 The service scheme-specific information following the "service:" URL
396 scheme identifier provides information necessary to access the
397 service. As described in the previous subsection, the form of a
398 service: URL is as follows:
399
400 service: URL = "service:" service-type ":" site url-path
401
402 where &lt;site&gt; has one of the following forms could refer to an
403 &lt;ipsite&gt;, &lt;ipxsite&gt; or &lt;atsite&gt; if the service URL locates to an IP,
404 IPX or AppleTalk service access point, respectively.
405
406 As discussed in <a href="#section-1">Section 1</a>, the &lt;service-type&gt; can be either a
407 concrete protocol name, or an abstract type name.
408
409 The &lt;ipsite&gt; field is typically either a domain name (DNS) or an IP
410 network protocol address for the service, and possibly a port number.
411 Note that use of DNS hostnames is preferred for ease of renumbering.
412 The &lt;site&gt; field can be null if other information in the service URL
413 or service attributes is sufficient to use the service.
414
415 The &lt;sap&gt; field allows more information to be provided (by way of
416 &lt;url-path&gt; and &lt;attr-list&gt;) that can uniquely locate the service or
417 resource if the &lt;site&gt; is not sufficient for that purpose. For IP
418 addresses, the &lt;site&gt; field begins with "//". Other address families
419 supported are IPX [<a href="#ref-14" title="Version 1.30">14</a>] and AppleTalk [<a href="#ref-9" title="R. Andrews">9</a>].
420
421 An &lt;attr-list&gt; field appears at the end of the &lt;url-part&gt; field, but
422 is never required to exist in any service location registration.
423
424 The &lt;attr-list&gt; field is composed of a list of semicolon (";")
425 separated attribute assignments of the form:
426
427 attr-id "=" attr-value
428
429 or for keyword attributes:
430
431 attr-id
432
433 Attributes are part of service: URLs when the attributes are required
434 to access a particular service. For instance, an ACAP [<a href="#ref-13" title="&quot;ACAP -- Application Configuration Access Protocol&quot;">13</a>] service
435 might require that the client authenticate with it through Kerberos.
436 Including an attribute in the service registration allows the ACAP
437 client to make use of the correct SASL [<a href="#ref-11" title="&quot;Simple Authentication and Security Layer (SASL)&quot;">11</a>] authentication mechanism.
438 The ACAP server's registration might look like:
439
440 service:acap://some.where.net;authentication=KERBEROSV4
441
442
443
444 <span class="grey">Guttman, et al. Standards Track [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc2609">RFC 2609</a> Service Templates and URLs June 1999</span>
447
448
449 Note that there can be other attributes of an ACAP server which are
450 not appropriate to include in the URL. For instance, the list of
451 users who have access to the server is useful for selecting an ACAP
452 server, but is not required for a client to use the registered
453 service.
454
455 Attributes associated with the service: URL are not typically
456 included in the service: URL. They are stored and retrieved using
457 other mechanisms. The service: URL is uniquely identified with a
458 particular service agent or resource, and is used when registering or
459 requesting the attribute information. The Service Location Protocol
460 specifies how such information is registered by network services and
461 obtained by client software.
462
463 <span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>. Use of service: URLs</span>
464
465 The service: URL is intended to allow arbitrary client/server and
466 peer to peer systems to make use of a standardized dynamic service
467 access point discovery mechanism.
468
469 It is intended that service: URLs be selected according to the
470 suitability of associated attributes. A client application can
471 obtain the URLs of several services of the same type and distinguish
472 the most preferable among them by means of their attributes. The
473 client uses the service: URL to communicate directly to a service.
474
475 Attributes are specified with a formal service template syntax
476 described in <a href="#section-3">Section 3</a>. If a service: URL registration includes
477 attributes, the registering agent SHOULD also keep track of the
478 attributes which characterize the service.
479
480 Registrations can be checked against the formal attribute
481 specification defined in the template by the client or agent
482 representing the client. Service registration are typically done
483 using the Service Location Protocol [<a href="#ref-10" title="&quot;Service Location Protocol Version 2&quot;">10</a>] (SLP). SLP provides a
484 mechanism for service: URLs to be obtained dynamically, according to
485 the service's attributes.
486
487 It is also possible to obtain service: URLs from documents and using
488 other protocols. In this case, the URL may not be accompanied by the
489 service attributes. The context in which the URL appears should make
490 it clear, if possible, when the service is appropriate to use. For
491 example, in a mail message, a service might be recommended for use
492 when the user is in a branch office. Or, an HTML document might
493 include a service: URL as a pointer to a service, describing in text
494 what the service does and who is authorized to use it.
495
496
497
498
499
500 <span class="grey">Guttman, et al. Standards Track [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc2609">RFC 2609</a> Service Templates and URLs June 1999</span>
503
504
505 <span class="h3"><a class="selflink" id="section-2.4" href="#section-2.4">2.4</a>. Specifying the Service Type-Specific URL Syntax</span>
506
507 When a service type is specified, the specification includes the
508 definition of the syntax for all URLs that are registered by services
509 of that particular type. For instance, the "lpr" service type may be
510 defined with service: URLs in the following form:
511
512 service:printer:lpr://&lt;address of printer&gt;/&lt;queue name&gt;
513
514 The section of the URL after the address of the printer:
515
516 "/" &lt;queue name&gt;
517
518 is specific to the lpr service type and corresponds to the &lt;url-path&gt;
519 field of the general service: URL syntax. This part is specified
520 when the lpr service type is specified.
521
522 <span class="h3"><a class="selflink" id="section-2.5" href="#section-2.5">2.5</a>. Accommodating Abstract Service Types</span>
523
524 An abstract service type is a service type that can be implemented by
525 a variety of different service agents.
526
527 In order to register a service: URL for an abstract service type the
528 'abstract-type' grammar rule described in <a href="#section-3.1">section 3.1</a> is used. This
529 will result in a URL which includes enough information to use the
530 service, namely, the protocol, address and path information. Unlike
531 'concrete' service: URLs, however, the service type is not enough to
532 determine the service access. Rather, an abstract service type
533 denotes a class of service types. The following subsection discusses
534 this point in more detail.
535
536 Concrete service templates inherit all attributes defined in the
537 abstract service template from which the concrete service template
538 was derived. Attribute defined in the abstract service template MUST
539 not be defined in the concrete service template as well. This
540 simplifies interpretation of templates.
541
542 For example, if an abstract service template for service type '
543 Abstract' defines an attribute FOO, all concrete service templates
544 derived from the abstract service template, such as '
545 Abstract:Concrete' will implicitly include the definition of
546 attribute FOO. This derived template MUST NOT redefine FOO, according
547 to the rule above.
548
549 A further example is described in Section A.
550
551
552
553
554
555
556 <span class="grey">Guttman, et al. Standards Track [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc2609">RFC 2609</a> Service Templates and URLs June 1999</span>
559
560
561 <span class="h4"><a class="selflink" id="section-2.5.1" href="#section-2.5.1">2.5.1</a>. Advertising Abstract Service Types</span>
562
563 Some services may make use of several protocols that are in common
564 use and are distinct services in their own right. In these cases an
565 abstract service type is appropriate. What is essential is that all
566 the required information for the service is clearly defined.
567
568 For example, suppose a network service is being developed for
569 dynamically loading device drivers. The client requires the
570 following three pieces of information before it can successfully load
571 and instantiate the driver:
572
573 1. The protocol used to load the driver code, for example, "ftp",
574 "http" or "tftp"
575
576 2. A pathname identifying where the driver code is located, for
577 example "/systemhost/drivers/diskdrivers.drv",
578
579 3. The name of the driver, for example, "scsi".
580
581 The temptation is to form the first two items into a URL and embed
582 that into a service: URL. As an example which should be avoided,
583
584 service:ftp:/x3.bean.org/drivers/diskdrivers.drv;driver=scsi
585
586 is a service: URL which seems to indicate where to obtain the driver.
587
588 Rather, an abstract service-type SHOULD be used. The service type is
589 not "ftp", as the example indicates. Rather, it is "device-drivers".
590 The service: URL that should be used, consistent with the rules in
591 section [<a href="#ref-6" title="&quot;Key Words for Use in RFCs to Indicate Requirement Levels&quot;">6</a>], is the following:
592
593 service:device-drivers:ftp://x3.bean.org/drivers/diskdrivers.drv;
594 driver=scsi;platform=sys3.2-rs3000
595
596 Other URLs for the same service using other protocols are also
597 supported, as in:
598
599 service:device-drivers:tftp://x2.bean.org/vol3/disk/drivers.drv;
600 driver=scsi;platform=sys3.2-rs3000
601
602 service:device-drivers:http://www.bean.org/drivers/drivpak.drv;
603 driver=scsi;platform=sys3.2-rs3000
604
605 Using SLP, a search for the service type "device-drivers" may return
606 all of the three URLs listed above. The client selects the most
607 appropriate access protocol for the desired resource.
608
609
610
611
612 <span class="grey">Guttman, et al. Standards Track [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc2609">RFC 2609</a> Service Templates and URLs June 1999</span>
615
616
617 The fundamental requirement is that the abstract service type MUST be
618 well specified. This requirement is imposed so that program code or
619 human users have enough information to access the service. In every
620 case, a well-specified abstract type will include either an access
621 protocol and a network address where the service is available, or an
622 embedded URL for a standardized URL scheme that describes how to
623 access the service. In the example above, there are three further
624 requirements: A URL path is included for access protocols indicating
625 the document to download, and two attributes are included to
626 characterize the driver.
627
628 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Syntax and Semantics of Service Type Specifications</span>
629
630 Service type specifications are documents in a formal syntax defining
631 properties important to service registration. These properties are:
632
633 1. General information on the service type specification itself,
634
635 2. The syntax of the service type-specific part of the service URL,
636
637 3. The definition of attributes associated with a service.
638
639 The service type specification document is the service type template.
640
641 The following subsections describe the syntax and semantics of
642 service type templates.
643
644 <span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Syntax of Service Type Templates</span>
645
646 Service template documents are encoded in a simple form. They may be
647 translated into any language or character set, but the template used
648 for standardization MUST be encoded in the 0x00-0x7F subrange of
649 UTF-8 [<a href="#ref-16" title="&quot;UTF-8, a transformation format of ISO 10646&quot;">16</a>] (which corresponds to ASCII character encoding) and be in
650 English.
651
652 A template document begins with a block of text assigning values to
653 five document identification items. The five identification items
654 can appear in any order within the block, but conventionally the
655 "template-type" item, which assigns the service type name, occurs at
656 the very top of the document in order to provide context for the rest
657 of the document. The attribute definition item occurs after the
658 document identification items.
659
660 All items end with a blank line. The reserved characters are ";",
661 "%", "=", ",", "#", LF, and CR. Reserved characters MUST be escaped.
662 The escape sequence is the same as described in [<a href="#ref-5" title="&quot;Uniform Resource Identifiers (URI): Generic Syntax&quot;">5</a>].
663
664
665
666
667
668 <span class="grey">Guttman, et al. Standards Track [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc2609">RFC 2609</a> Service Templates and URLs June 1999</span>
671
672
673 The service template is encoded in a UTF-8 character set, but
674 submitted as a part of an work in progress, which is encoded in ASCII
675 characters. All characters which are outside of the ASCII range MUST
676 be escaped using the `\' HEXDIG HEXDIG syntax. For example, the
677 letter e accent aigue would be represented as "\c3\a9".
678 Unfortunately, this will detract from the readability of the service
679 template in the service template submission. Hopefully some public
680 domain tools will emerge for translating escaped UTF-8 characters
681 into humanly readable ones.
682
683 Values in value lists are separated by commas. A value list is
684 terminated by a newline not preceded by a comma. If the newline is
685 preceded by a comma, the value list is interpreted to continue onto
686 the next line.
687
688 Attribute identifiers, attribute type names, and flags are all case
689 insensitive. For ease of presentation, upper and lower case
690 characters can be used to represent these in the template document.
691 Newlines are significant in the grammar. They delimit one item from
692 another, as well as separating parts of items internally.
693
694 String values are considered to be a sequence of non-whitespace
695 tokens potentially with embedded whitespace, separated from each
696 other by whitespace. Commas delimit lists of strings. String values
697 are trimmed so as to reduce any sequence of white space interior to a
698 string to a single white space. Preceding or trailing white space is
699 removed. For example:
700
701 " some value , another example "
702
703 is trimmed to
704
705 "some value" and "another example".
706
707 Note that there can be no ambiguity in string tokenization because
708 values in value lists are separated by a comma. String tokens are
709 not delimited by double quotes (") as is usually the case with
710 programming languages.
711
712 Attribute tags and values are useful for directory look-up. In this
713 case, decoding of character escapes and trimming white space MUST be
714 performed before string matching. In addition, string matching
715 SHOULD be case insensitive.
716
717
718
719
720
721
722
723
724 <span class="grey">Guttman, et al. Standards Track [Page 13]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
726 <span class="grey"><a href="./rfc2609">RFC 2609</a> Service Templates and URLs June 1999</span>
727
728
729 Templates obey the following ABNF [<a href="#ref-8" title="&quot;Augmented BNF for Syntax Specifications: ABNF&quot;">8</a>] grammar:
730
731 template = tem-attrs attr-defs
732 tem-attrs = schemetype schemevers schemetext schemeurl
733 schemetype = "template-type=" scheme term
734 schemevers = "template-version=" version-no term
735 schemetext = "template-description=" newline desc term
736 schemeurl = "template-url-syntax=" newline url-bnf term
737 url-bnf = *[ com-chars ]
738 ; An ABNF describing the &lt;url-path&gt; production
739 ; in the service: URL grammar of <a href="#section-2.1">Section 2.1</a>.
740 scheme = service-type [ "." naming-auth ]
741 service-type = scheme-name
742 naming-auth = scheme-name
743 scheme-name = ALPHA [1*schemechar] [ "." 1*schemechar ]
744 schemechar = ALPHA / DIGIT / "-" / "+" /
745 version-no = 1*DIGIT "." 1*DIGIT
746 langtag = 1*8ALPHA ["-" 1*8ALPHA]
747 ; See [<a href="#ref-3" title="&quot;Tags for the Identification of Languages&quot;">3</a>]
748 desc = *[ com-chars ]
749 ; A block of free-form text for reading by
750 ; people describing the service in a short,
751 ; informative manner.
752 term = newline newline
753 attr-defs = *( attr-def / keydef )
754 attr-def = id "=" attrtail
755 keydef = id "=" "keyword" newline [help-text] newline
756 attrtail = type flags newline [value-list] [help-text]
757 [value-list] newline
758 id = 1*attrchar
759 type = "string" / "integer" / "boolean" / "opaque"
760 flags = ["m"/"M"] ["l"/"L"] ["o"/"O"] ["x"/"X"]
761 value-list = value newline / value "," value-list /
762 value "," newline value-list
763 help-text = 1*( "#" help-line )
764 ; A block of free-form text for reading by
765 ; people describing the attribute and
766 ; its values.
767 help-line = *[ com-chars ] newline
768 attrchar = schemechar / ":" / "_" / "$" / "~" / "@" / "." /
769 "|" / "&lt;" / "&gt;" / "*" / "&amp;"
770 value = string / integer / boolean / opaque
771 string = safe-char *[safe-char / white-sp] safe-char
772 integer = [ "+" | "-" ] 1*DIGIT
773 boolean = "true" / "false"
774 opaque = "\FF" 1*( "\" HEXDIG HEXDIG)
775 ; Each byte of opaque value is hex encoded.
776 ; The format corresponds to [<a href="#ref-10" title="&quot;Service Location Protocol Version 2&quot;">10</a>].
777
778
779
780 <span class="grey">Guttman, et al. Standards Track [Page 14]</span></pre>
781 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
782 <span class="grey"><a href="./rfc2609">RFC 2609</a> Service Templates and URLs June 1999</span>
783
784
785 ; Newlines are ignored in decoding opaque
786 ; values.
787 com-chars = safe-char / white-sp / "," / ";"/ "%"
788 safe-char = attrchar / escaped / " " / "!" / '"' / "'" /
789 "|" / "(" / ")" / "+" / "-" / "." / ":" /
790 "=" / "?" / "[" / "]" / "{" / "/" / "{" /
791 "$"
792 ; All UTF-8 printable characters are
793 ; included except ",", "%", ";", and "#".
794 escaped = 1*(`\' HEXDIG HEXDIG)
795 white-sp = SPACE / HT
796 newline = CR / ( CR LF )
797
798 <span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Semantics of Service Type Templates</span>
799
800 The service type template defines the service attributes and service:
801 URL syntax for a particular service type. The attribute definition
802 includes the attribute type, default values, allowed values and other
803 information.
804
805 Note that the 'template-type', 'template-version', 'template-
806 description' and 'template-url-syntax' have all been defined as
807 attributes. These attributes MAY accompany any service registration
808 using SLPv2.
809
810 <span class="h4"><a class="selflink" id="section-3.2.1" href="#section-3.2.1">3.2.1</a>. Definition of a Service Template</span>
811
812 There are four items included in the service template. The semantics
813 of each item is summarized below.
814
815 - template-type
816
817 The scheme name of the service scheme. The scheme name consists
818 of the service type name and an optional naming authority name,
819 separated from the service type name by a period. See 3.2.2 for
820 the conventions governing service type names.
821
822 - template-version
823
824 The version number of the service type specification.
825
826 - template-description
827
828 A description of the service suitable for inclusion in text read
829 by people.
830
831
832
833
834
835
836 <span class="grey">Guttman, et al. Standards Track [Page 15]</span></pre>
837 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
838 <span class="grey"><a href="./rfc2609">RFC 2609</a> Service Templates and URLs June 1999</span>
839
840
841 - template-url-syntax
842
843 The syntax of the service type-specific URL part of the service:
844 URL.
845
846 - attribute definitions
847
848 A collection of zero or more definitions for attributes
849 associated with the service in service registrations.
850
851 Each of the following subsections deals with one of these items.
852
853 <span class="h4"><a class="selflink" id="section-3.2.2" href="#section-3.2.2">3.2.2</a>. Service Type</span>
854
855 The service scheme consists of the service type name and an optional
856 naming authority name separated from the service type name by a
857 period. The service scheme is a string that is appended to the '
858 service:' URL scheme identifier, and is the value of the "template-
859 type" item in the template document. If the naming authority name is
860 absent it is assumed to be IANA.
861
862 <span class="h4"><a class="selflink" id="section-3.2.3" href="#section-3.2.3">3.2.3</a>. Version Number</span>
863
864 The version number of the service type template is the value of the
865 "template-version" item. A draft proposal starts at 0.0, and the
866 minor number increments once per revision. A standardized template
867 starts at 1.0. Additions of optional attributes add one to the minor
868 number, and additions of required attributes, changes of definition,
869 or removal of attributes add one to the major number. The intent is
870 that an old service template still accurately, if incompletely,
871 defines the attributes of a service registration if the template only
872 differs from the registration in its minor version. See <a href="#section-4">Section 4</a>
873 for more detail on how to use the template-version attribute.
874
875 <span class="h4"><a class="selflink" id="section-3.2.4" href="#section-3.2.4">3.2.4</a>. Description</span>
876
877 The description is a block of text readable by people in the language
878 of the template and is the value of the "template-description" item.
879 It should be sufficient to identify the service to human readers and
880 provide a short, informative description of what the service does.
881
882 If the service type corresponds to a particular protocol, the
883 protocol specification must be cited here. The protocol need not be
884 a standardized protocol. The template might refer to a proprietary
885 specification, and refer the reader of the template to a contact
886 person for further information.
887
888
889
890
891
892 <span class="grey">Guttman, et al. Standards Track [Page 16]</span></pre>
893 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
894 <span class="grey"><a href="./rfc2609">RFC 2609</a> Service Templates and URLs June 1999</span>
895
896
897 <span class="h4"><a class="selflink" id="section-3.2.5" href="#section-3.2.5">3.2.5</a>. Syntax of the Service Type-specific URL Part</span>
898
899 The syntax of the service type-specific part of the service: URL is
900 provided in the template document as the value of the "template-url-
901 syntax" item. The &lt;url-path&gt; field of the service: URL is designed
902 to provide additional information to locate a service when the
903 &lt;addr-spec&gt; field is not sufficient. The &lt;url-path&gt; field
904 distinguishes URLs of a particular service type from those of another
905 service type. For instance, in the case of the lpr service type, the
906 &lt;url-path&gt; may be defined so that it must include the queue name, but
907 other service types may not require this information.
908
909 The syntax for the &lt;url-path&gt; field MUST accompany the definition of
910 a new service type, unless the URL scheme has already been
911 standardized and is not a service: URL. The syntax is included in the
912 template document as an ABNF [<a href="#ref-8" title="&quot;Augmented BNF for Syntax Specifications: ABNF&quot;">8</a>] following the rules for URL syntax
913 described in [<a href="#ref-5" title="&quot;Uniform Resource Identifiers (URI): Generic Syntax&quot;">5</a>]. There is no requirement for a service scheme to
914 support a &lt;url-path&gt;. The &lt;url-path&gt; field can be very simple, or
915 even omitted. If the URL scheme has already been standardized, the
916 "template-url-syntax" item SHOULD include a reference to the
917 appropriate standardization documents. Abstract service types may
918 defer this field to the template documents describing their concrete
919 instances.
920
921 <span class="h4"><a class="selflink" id="section-3.2.6" href="#section-3.2.6">3.2.6</a>. Attribute Definition</span>
922
923 The bulk of the template is typically devoted to defining service
924 type-specific attributes. An attribute definition precisely
925 specifies the attribute's type, other restrictions on the attribute
926 (whether it is multi-valued, optional, etc), some text readable by
927 people describing the attribute, and lists of default and allowed
928 values. The only required information is the attribute's type, the
929 rest are optional. Registration, deregistration and the use of
930 attributes in queries can be accomplished using the Service Location
931 Protocol [<a href="#ref-10" title="&quot;Service Location Protocol Version 2&quot;">10</a>] or other means, and discussion of this is beyond the
932 scope of the document.
933
934 Attributes are used to convey information about a given service for
935 purposes of differentiating different services of the same type.
936 They convey information to be used in the selection of a particular
937 service to establish communicate with, either through a program
938 offering a human interface or programmatically. Attributes can be
939 encoded in different character sets and in different languages. The
940 procedure for doing this is described in <a href="#section-6">Section 6</a>.
941
942 An attribute definition begins with the specification of the
943 attribute's identifier and ends with a single empty line. Attributes
944 definitions have five components (in order of appearance in a
945
946
947
948 <span class="grey">Guttman, et al. Standards Track [Page 17]</span></pre>
949 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
950 <span class="grey"><a href="./rfc2609">RFC 2609</a> Service Templates and URLs June 1999</span>
951
952
953 definition):
954
955 1. An attribute identifier which acts as the name of the attribute,
956
957 2. Attribute descriptors (type and flags),
958
959 3. An optional list of values which are assigned to the attribute by
960 default,
961
962 4. An optional block of text readable by people providing a short,
963 informative description of the attribute,
964
965 5. An optional list of allowed values which restrict the value or
966 values the attribute can take on.
967
968 <span class="h5"><a class="selflink" id="section-3.2.6.1" href="#section-3.2.6.1">3.2.6.1</a>. The Attribute Identifier</span>
969
970 An attribute definition starts with the specification of the
971 attribute's identifier. The attribute's identifier functions as the
972 name of the attribute. Note that the characters used to compose an
973 attribute identifier are restricted to those characters considered
974 unrestricted for inclusion in a URL according to [<a href="#ref-5" title="&quot;Uniform Resource Identifiers (URI): Generic Syntax&quot;">5</a>]. The reason is
975 that services can display prominent attributes in their service: URL
976 registrations. Each attribute identifier must be unique in the
977 template. Since identifiers are case folded, upper case and lower
978 case characters are the same.
979
980 <span class="h5"><a class="selflink" id="section-3.2.6.2" href="#section-3.2.6.2">3.2.6.2</a>. The Attribute Type</span>
981
982 Attributes can have one of five different types: string, integer,
983 boolean, opaque, or keyword. The attribute's type specification is
984 separated from the attribute's identifier by an equal sign ("=") and
985 follows the equal sign on the same line. The string, signed integer,
986 and boolean types have the standard programming language or database
987 semantics. Integers are restricted to those signed values that can
988 be represented in 32 bits. The character set used to represent
989 strings is not specified at the time the template is defined, but
990 rather is determined by the service registration. Booleans have the
991 standard syntax. Opaques are byte escaped values that can be used to
992 represent any other kind of data. Keywords are attributes that have
993 no characteristics other than their existence (and possibly the
994 descriptive text in their definition).
995
996 Keyword and boolean attributes impose restrictions on the following
997 parts of the attribute definition. Keyword attribute definitions
998 MUST have no flag information following the type definition, nor any
999 default or allowed values list. Boolean attributes are single value
1000 only, i.e., multi-valued boolean attributes are not allowed.
1001
1002
1003
1004 <span class="grey">Guttman, et al. Standards Track [Page 18]</span></pre>
1005 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
1006 <span class="grey"><a href="./rfc2609">RFC 2609</a> Service Templates and URLs June 1999</span>
1007
1008
1009 <span class="h5"><a class="selflink" id="section-3.2.6.3" href="#section-3.2.6.3">3.2.6.3</a>. Attribute Flags</span>
1010
1011 Flags determine other characteristics of an attribute. With the
1012 exception of keyword attributes, which may not have any flags, flags
1013 follow the attribute type on the same line as the attribute
1014 identifier, and are separated from each other by whitespace. Flags
1015 may appear in any order after the attribute type. Other information
1016 must not follow the flags, and only one flag identifier of a
1017 particular flag type is allowed per attribute definition.
1018
1019 The semantics of the flags are as follows:
1020
1021 - o or O
1022
1023 Indicates that the attribute is optional. If this flag is
1024 missing, the attribute is required in every service registration.
1025
1026 - m or M
1027
1028 Indicates that the attribute can take on multiple values. If
1029 this flag is present, every value in a multi-valued attribute
1030 has the same type as the type specified in the type part of the
1031 attribute definition. Boolean attributes must not include this
1032 flag.
1033
1034 - l or L
1035
1036 Indicates that attribute is literal, i.e. is not meant to be
1037 translated into other languages. If this flag is present, the
1038 attribute is not considered to be readable by people and should
1039 not be translated when the template is translated. See <a href="#section-6">Section 6</a>
1040 for more information about translation.
1041
1042 - x or X
1043
1044 Indicates that clients SHOULD include the indicated attribute
1045 in requests for services. Neglecting to include this attribute
1046 will not sufficiently differentiate the service. If services are
1047 obtained without selecting this attribute they will quite likely
1048 be useless to the client.
1049
1050 The values for multivalued attributes are an unordered set.
1051 Deletions of individual values from a multivalued attribute are not
1052 supported, and deletion of the attribute causes the entire set of
1053 values to be removed.
1054
1055
1056
1057
1058
1059
1060 <span class="grey">Guttman, et al. Standards Track [Page 19]</span></pre>
1061 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
1062 <span class="grey"><a href="./rfc2609">RFC 2609</a> Service Templates and URLs June 1999</span>
1063
1064
1065 <span class="h5"><a class="selflink" id="section-3.2.6.4" href="#section-3.2.6.4">3.2.6.4</a>. Default Value or List</span>
1066
1067 If the attribute definition includes a default value or, in the case
1068 of multivalued attributes, a default values list, it begins on the
1069 second line of the attribute definition and continues over the
1070 following lines until a line ends without a comma. As a consequence,
1071 newlines cannot be embedded in values unless escaped. See <a href="#section-2.1">Section</a>
1072 <a href="#section-2.1">2.1</a>.
1073
1074 Particular attribute types and definitions restrict the default
1075 values list. Keyword attributes must not have a list of defaults.
1076 If an optional attribute's definition has an allowed values list,
1077 then a default value or list is not optional but required. The
1078 motivation for this is that defining an attribute with an allowed
1079 values list is meant to restrict the values the attribute can take
1080 on, and requiring a default value or list assures that the default
1081 value is a member of the given set of allowed values.
1082
1083 The default value or list indicates what values the attribute is
1084 given if no values are assigned to the attribute when a service is
1085 registered. If an optional attribute's definition includes no
1086 default value or list, the following defaults are assigned:
1087
1088 1. String values are assigned the empty string,
1089
1090 2. Integer values are assigned zero,
1091
1092 3. Boolean values are assigned false,
1093
1094 4. Opaque values are assigned a byte array containing no values,
1095
1096 5. Multi-valued attributes are initialized with a single value.
1097
1098 For purposes of translating nonliteral attributes, the default values
1099 list is taken to be an ordered set, and translations MUST maintain
1100 that order.
1101
1102 <span class="h5"><a class="selflink" id="section-3.2.6.5" href="#section-3.2.6.5">3.2.6.5</a>. Descriptive Text</span>
1103
1104 Immediately after the default values list, if any, a block of
1105 descriptive text SHOULD be included in the attribute definition.
1106 This text is meant to be readable by people, and should include a
1107 short, informative description of the attribute. It may also provide
1108 additional information, such as a description of the allowed values.
1109 This text is primarily designed for display by interactive browsing
1110 tools. The descriptive text is set off from the surrounding
1111 definition by a crosshatch character ("#") at the beginning of the
1112 line. The text should not, however, be treated as a comment by
1113
1114
1115
1116 <span class="grey">Guttman, et al. Standards Track [Page 20]</span></pre>
1117 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
1118 <span class="grey"><a href="./rfc2609">RFC 2609</a> Service Templates and URLs June 1999</span>
1119
1120
1121 parsing and other tools, since it is an integral part of the
1122 attribute definition. Within the block of descriptive text, the text
1123 is transferred verbatim, including indentation and line breaks, so
1124 any formatting is preserved.
1125
1126 <span class="h5"><a class="selflink" id="section-3.2.6.6" href="#section-3.2.6.6">3.2.6.6</a>. Allowed Values List</span>
1127
1128 Finally, the attribute definition concludes with an optional allowed
1129 values list. The allowed values list, if any, follows the
1130 descriptive text, or, if the descriptive text is absent, the initial
1131 values list. The syntax of the allowed values list is identical to
1132 that of the initial values list. The allowed values list is also
1133 terminated by a line that does not end in a comma. If the allowed
1134 values list is present, assignment to attributes is restricted to
1135 members of the list.
1136
1137 As with the default values list, the allowed values list is also
1138 considered to be an ordered set for purposes of translation.
1139
1140 <span class="h5"><a class="selflink" id="section-3.2.6.7" href="#section-3.2.6.7">3.2.6.7</a>. Conclusion of An Attribute Definition</span>
1141
1142 An attribute definition concludes with a single empty line.
1143
1144 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. A Process For Standardizing New Service Types</span>
1145
1146 New service types can be suggested simply by providing a service type
1147 template and a short description about how to use the service. The
1148 template MUST have its "template-version" template attribute set to
1149 0.0.
1150
1151 MAJOR revision numbers come before the '.', MINOR revision numbers
1152 come after the '.'.
1153
1154 The minor version number increments once with each change until it
1155 achieves 1.0. There is no guarantee any version of the service
1156 template is backward compatible before it reaches 1.0.
1157
1158 Once a service template has reached 1.0, the definition is "frozen"
1159 for that version. New templates must be defined, of course, to
1160 refine that definition, but the following rules must be followed:
1161
1162 A MINOR revision number signifies the introduction of a compatible
1163 change. A MAJOR revision number signifies the introduction of an
1164 incompatible change. This is formalized by the following rules:
1165
1166 - Any new optional attribute defined for the template increases
1167 the minor version number by one. All other attributes for the
1168 version must continue to be supported as before. A client which
1169
1170
1171
1172 <span class="grey">Guttman, et al. Standards Track [Page 21]</span></pre>
1173 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
1174 <span class="grey"><a href="./rfc2609">RFC 2609</a> Service Templates and URLs June 1999</span>
1175
1176
1177 supports 1.x can still use later versions of 1.y (where x&lt;y) as
1178 it ignores attributes it doesn't know about.
1179
1180 - Adding a required attribute, removing support for an attribute
1181 or changing definition of an attribute requires changing the
1182 major version number of a service template. A client application
1183 may be unable to make use of this information, or it may need
1184 to obtain the most recent service template to help the user
1185 interpret the service information.
1186
1187 The template is submitted to a special mailing list, see <a href="#section-5">section 5</a>.
1188 This document must include a 'template begins here' and 'template
1189 ends here' marking, in text, so that it is trivial to cut and paste
1190 the template from the submission.
1191
1192 The list will be available at [email protected]. Ideally, experts
1193 in the implementation and deployment of the particular protocol are
1194 consulted so as to add or delete attributes or change their
1195 definition to make the template as useful as possible. The mailing
1196 list will be maintained even when the SVRLOC WG goes dormant for the
1197 purpose of discussing service templates.
1198
1199 All published versions of the template must be available on-line,
1200 including obsolete ones.
1201
1202 Once consensus is achieved, the template should be reissued with
1203 possible corrections, having its Version number set to 1.0.
1204 Templates with version numbers below 1.0 are not submitted to the
1205 IANA. From that point onwards, templates are submitted. See <a href="#section-5">Section</a>
1206 <a href="#section-5">5</a> for details on how templates are submitted to an IANA registry of
1207 templates.
1208
1209 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. IANA Considerations</span>
1210
1211 It is the responsibility of the IESG (e.g., Applications Area
1212 director) to appoint a Designated Expert (see [<a href="#ref-12" title="T. and H. Alvestrand">12</a>].) Anyone may ask
1213 for clarification of a service template. This is to solicit input
1214 from the concerned community. It is up to the appointed reviewer to
1215 determine whether clarification requests are satisfied. It is the
1216 reviewer's responsibility to see that all reasonable clarification
1217 requests are met before the template is submitted for inclusion in
1218 the IANA registry.
1219
1220 When the reviewer has determined that the template submission is
1221 ready, he or she will submit the template to the IANA for inclusion
1222 in a registry. Mailing list participants supply input to the process
1223 but do not make the decision whether to accept a service template.
1224
1225
1226
1227
1228 <span class="grey">Guttman, et al. Standards Track [Page 22]</span></pre>
1229 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span>
1230 <span class="grey"><a href="./rfc2609">RFC 2609</a> Service Templates and URLs June 1999</span>
1231
1232
1233 If a dispute arises over the decisions made by the reviewer, the
1234 matter may be appealed according to normal IETF procedure as
1235 described for the Standards Track process.
1236
1237 The IANA will maintain a mail forwarding alias for the work of this
1238 list, so that "[email protected]" points to a mail server supplied
1239 by a volunteer organization.
1240
1241 The service template submission MUST be of the form:
1242
1243 Name of submitter:
1244 Language of service template:
1245 Security Considerations:
1246 Template Text:
1247 ----------------------template begins here-----------------------
1248 . . .
1249 -----------------------template ends here------------------------
1250
1251 The service template file has a naming convention:
1252
1253 &lt;service-type&gt; "." &lt;version-no&gt; "." &lt;langtag&gt;
1254
1255 Each of these fields are defined in <a href="#section-2">Section 2</a>. They correspond to
1256 the values of the template fields "type", "template-version". The
1257 files for the example templates in this document (see Section A) are
1258 called:
1259
1260 "foo.0.0.en",
1261 "Net-Transducer.0.0.en",
1262 "Net-Transducer:Thermometer.0.0.de" and
1263 "Net-Transducer:Thermomoter.0.0.en".
1264
1265 The reviewer will ensure that the template submission to IANA has the
1266 correct form and required fields.
1267
1268 No service type template will be accepted for inclusion in the
1269 service template registry unless the submission includes a security
1270 considerations section and contact information for the template
1271 document author.
1272
1273 The IANA will maintain a registry containing both the service type
1274 templates, and the template description document containing the
1275 service type template, including all previous versions. The IANA
1276 will receive notice to include a service template in the registry
1277 by email from the reviewer. This message will include the service
1278 template itself, which is to be registered.
1279
1280
1281
1282
1283
1284 <span class="grey">Guttman, et al. Standards Track [Page 23]</span></pre>
1285 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span>
1286 <span class="grey"><a href="./rfc2609">RFC 2609</a> Service Templates and URLs June 1999</span>
1287
1288
1289 Neither the reviewer nor the IANA will take any position on claims of
1290 copyright or trademark issues with regard to templates.
1291
1292 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Internationalization Considerations</span>
1293
1294 The service: URL must be encoded using the rules set forth in [<a href="#ref-5" title="&quot;Uniform Resource Identifiers (URI): Generic Syntax&quot;">5</a>].
1295 The character set encoding is limited to specific ranges within the
1296 US-ASCII character set [<a href="#ref-4">4</a>].
1297
1298 The template is encoded in UTF-8 characters.
1299
1300 <span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. Language Identification and Translation</span>
1301
1302 The language used in attribute strings should be identified supplying
1303 a Language Tag [<a href="#ref-3" title="&quot;Tags for the Identification of Languages&quot;">3</a>] in the Service Template submission (see <a href="#section-5">Section</a>
1304 <a href="#section-5">5</a>).
1305
1306 A program can translate a service registration from one language to
1307 another provided it has both the template of the language for the
1308 registration and the template of the desired target language. All
1309 standardized attributes are in the same order in both templates. All
1310 non-arbitrary strings, including the descriptive help text, is
1311 directly translatable from one language to another. Non-literal
1312 attribute definitions, attribute identifiers, attribute type names,
1313 attribute flags, and the boolean constants "true" and "false" are
1314 never translated. Translation of attribute identifiers is prohibited
1315 because, as with domain names, they can potentially be part of a
1316 service: URL and therefore their character set is restricted. In
1317 addition, as with variable identifiers in programming languages, they
1318 could become embedded into program code.
1319
1320 All strings used in attribute values are assumed translatable unless
1321 explicitly defined as being literal, so that best effort translation
1322 (see below) does not modify strings which are meant to be interpreted
1323 by a program, not a person.
1324
1325 An example of a translated service template is included in Section A.
1326
1327 There are two ways to go about translation: standardization and best
1328 effort.
1329
1330 When the service type is standardized, more than one document can be
1331 submitted for review. One service type description is approved as a
1332 master, so that when a service type template is updated in one
1333 language, all the translations (at least eventually) reflect the same
1334 semantics.
1335
1336
1337
1338
1339
1340 <span class="grey">Guttman, et al. Standards Track [Page 24]</span></pre>
1341 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span>
1342 <span class="grey"><a href="./rfc2609">RFC 2609</a> Service Templates and URLs June 1999</span>
1343
1344
1345 If no document exists describing the standard translation of the
1346 service type, a 'best effort' translation for strings should be done.
1347
1348 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Security Considerations</span>
1349
1350 Service type templates provide information that is used to interpret
1351 information obtained by the Service Location Protocol. If these
1352 templates are modified or false templates are distributed, services
1353 may not correctly register themselves, or clients might not be able
1354 to interpret service information.
1355
1356 The service: URLs themselves specify the service access point and
1357 protocol for a particular service type. These service: URLs could be
1358 distributed and indicate the location of a service other than that
1359 normally want to used. The Service Location Protocol [<a href="#ref-10" title="&quot;Service Location Protocol Version 2&quot;">10</a>]
1360 distributes service: URLs and has an authentication mechanism that
1361 allows service: URLs of registered services to be signed and for the
1362 signatures to be verified by clients.
1363
1364 Each Service Template will include a security considerations section
1365 which will describe security issues with using the service scheme for
1366 the specific Service Type.
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396 <span class="grey">Guttman, et al. Standards Track [Page 25]</span></pre>
1397 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span>
1398 <span class="grey"><a href="./rfc2609">RFC 2609</a> Service Templates and URLs June 1999</span>
1399
1400
1401 <span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">A</a>. Service Template Examples</span>
1402
1403 The text in the template example sections is to be taken as being a
1404 single file. They are completely fictitious (ie. the examples do
1405 not represent real services).
1406
1407 The FOO example shows how to use service templates for an application
1408 that has very few attributes. Clients request the FOO server where
1409 their user data is located by including their user name as the value
1410 of the user attribute.
1411
1412 The Net-Transducer example shows how abstract service types are
1413 defined and how a corresponding concrete instance is defined. A
1414 system might support any of several NetTransducer services. Here we
1415 give only one concrete instance of the abstract type.
1416
1417 It is not necessary to register concrete templates for an abstract
1418 service type if the abstract service type template is completely
1419 clear as to what possible values can be used as a concrete type, and
1420 what their interpretation is.
1421
1422 <span class="h3"><a class="selflink" id="appendix-A.1" href="#appendix-A.1">A.1</a>. FOO</span>
1423
1424 The FOO service template submission example follows:
1425
1426 Name of submitter: "Erik Guttman" &lt;[email protected]&gt;
1427 Language of service template: en
1428 Security Considerations:
1429 If the USER and GROUPS attributes are included a
1430 possibility exists that the list of identities for users or groups
1431 can be discovered. This information would otherwise be difficult
1432 to discover.
1433
1434 Template Text:
1435 -------------------------template begins here-----------------------
1436 template-type=FOO
1437
1438 template-version=0.0
1439
1440 template-description=
1441 The FOO service URL provides the location of an FOO service.
1442
1443 template-url-syntax=
1444 url-path= ; There is no URL path defined for a FOO URL.
1445
1446 users= string M L O
1447 # The list of all users which the FOO server supports.
1448
1449
1450
1451
1452 <span class="grey">Guttman, et al. Standards Track [Page 26]</span></pre>
1453 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span>
1454 <span class="grey"><a href="./rfc2609">RFC 2609</a> Service Templates and URLs June 1999</span>
1455
1456
1457 groups= string M L O
1458 # The list of all groups which the FOO server supports.
1459 --------------------------template ends here------------------------
1460
1461 This template could be internationalized by registering another
1462 version, say in German:
1463
1464 Name of submitter: "Erik Guttman" &lt;[email protected]&gt;
1465 Language of service template: de
1466 Security Considerations:
1467 Wenn die USER und GROUPS Eigenschaften inbegriffen sind,
1468 besteht die Moeglichkeit, dass die Liste der Identitaeten
1469 von Benutzern oder Gruppen endeckt werden kann. Diese
1470 Information wurde unter anderen Umstaenden schwierig zu
1471 entdecken sein.
1472
1473 Template Text:
1474 -------------------------template begins here-----------------------
1475 template-type=FOO
1476
1477 template-version=0.0
1478
1479 template-description=
1480 Der FOO Service URL zeigt die Stelle von einem Foo Service an.
1481
1482 template-url-syntax=
1483 url-path= ; Es gibt keinen fuer den FOO URL definierten Pfad.
1484
1485 users= string M L O
1486 # Die Liste aller Users, die der FOO Server unterstuetzt.
1487
1488 groups= string M L O
1489 # Die Liste aller Gruppen, die der FOO Server unterstuetzt.
1490 --------------------------template ends here------------------------
1491
1492 Note that the attribute tags are not translated. If translations
1493 are desired, the suggested convention for doing so is to define a
1494 separate attribute called localize-&lt;tag&gt; for each attribute tag which
1495 is to be localized. This will aid in displaying the attribute tags
1496 in a human interface.
1497
1498 For example, in this case above, the following two attributes could
1499 be defined:
1500
1501 localize-users= string
1502 Benutzer
1503
1504 localize-groups= string
1505
1506
1507
1508 <span class="grey">Guttman, et al. Standards Track [Page 27]</span></pre>
1509 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span>
1510 <span class="grey"><a href="./rfc2609">RFC 2609</a> Service Templates and URLs June 1999</span>
1511
1512
1513 Gruppen
1514
1515 The attributes (in SLPv2 attribute list format) for a service
1516 registration of a FOO service based on this template, in German,
1517 could be:
1518
1519 (users=Hans,Fritz),(groups=Verwaltung,Finanzbuchhaltung),
1520 (template-type=FOO),(template-version=0.0),(template-description=
1521 Der FOO Service URL zeigt die Stelle von einem Foo Service an.),
1522 (template-url-syntax= \OD url-path= ; Es gibt kein fuer den FOO
1523 URL definiert Pfad. \OD),(localize-users=Benutzer),
1524 (localize-groups=Gruppen)
1525
1526 Anyone obtaining these attributes could display "Benutzer=Hans,Fritz"
1527 in a human interface using the included information. Note that the
1528 template attributes have been included in this registration. This is
1529 OPTIONAL, but makes it possible to discover which template was used
1530 to register the service.
1531
1532 <span class="h3"><a class="selflink" id="appendix-A.2" href="#appendix-A.2">A.2</a>. Abstract Service Type: Net-Transducer</span>
1533
1534 An example submission of an abstract service type template is:
1535
1536 Name of submitter: "Erik Guttman" &lt;[email protected]&gt;
1537 Language of service template: en
1538 Security Considerations:
1539 See the security considerations of the concrete service types.
1540
1541 Template Text:
1542 -------------------------template begins here-----------------------
1543 template-type=Net-Transducer
1544
1545 template-version=0.0
1546
1547 template-description=
1548 This is an abstract service type. The purpose of the Net-
1549 Transducer service type is to organize into a single category
1550 all network enabled Transducers which have certain properties.
1551
1552 template-url-syntax=
1553 url-path= ; Depends on the concrete service type.
1554 ; See these templates.
1555
1556 sample-units= string L
1557 # The units of sample that the Transducer provides, for instance
1558 # C (degrees Celsius), V (Volts), kg (Kilograms), etc.
1559
1560 sample-resolution= string L
1561
1562
1563
1564 <span class="grey">Guttman, et al. Standards Track [Page 28]</span></pre>
1565 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span>
1566 <span class="grey"><a href="./rfc2609">RFC 2609</a> Service Templates and URLs June 1999</span>
1567
1568
1569 # The resolution of the Transducer. For instance, 10^-3 means
1570 # that the Transducer has resolution to 0.001 unit.
1571
1572 sample-rate= integer L
1573 # The speed at which samples are obtained per second. For
1574 # instance 1000 means that one sample is obtained every millisecond.
1575
1576 --------------------------template ends here------------------------
1577
1578 <span class="h3"><a class="selflink" id="appendix-A.3" href="#appendix-A.3">A.3</a>. Concrete Service Type: Net-Transducer:Thermometer</span>
1579
1580 This is another service template submission example, supplying a
1581 concrete service type corresponding to the abstract template above.
1582
1583 Name of submitter: "Erik Guttman" &lt;[email protected]&gt;
1584 Language of service template: en
1585 Security Considerations:
1586 There is no authentication of the Transducer output. Thus,
1587 the Thermometer output could easily be spoofed.
1588
1589 Template Text:
1590 -------------------------template begins here-----------------------
1591 template-type=service:Net-Transducer:Thermometer
1592
1593 template-version=0.0
1594
1595 template-description=
1596 The Thermometer is a Net-Transducer capable of reading temperature.
1597 The data is read by opening a TCP connection to one of the ports
1598 in the service URL and reading an ASCII string until an NULL
1599 character is encountered. The client may continue reading data at
1600 no faster than the sample-rate, or close the connection.
1601
1602 template-url-syntax=
1603 url-path = "ports=" ports-list
1604 port-list = port / port "," ports
1605 port = 1*DIGIT
1606 ; See the Service URL &lt;port&gt; production rule.
1607 ; These are the ports connections can be made on.
1608
1609 location-description=string
1610 # The location where the Thermometer is located.
1611
1612 operator=string O
1613 # The operator to contact to have the Thermometer serviced.
1614
1615 --------------------------template ends here------------------------
1616
1617
1618
1619
1620 <span class="grey">Guttman, et al. Standards Track [Page 29]</span></pre>
1621 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-30" ></span>
1622 <span class="grey"><a href="./rfc2609">RFC 2609</a> Service Templates and URLs June 1999</span>
1623
1624
1625 <span class="h3"><a class="selflink" id="appendix-A.4" href="#appendix-A.4">A.4</a>. service: URLs and SLP</span>
1626
1627 A user with an FOO enabled calendar application should not be
1628 bothered with knowing the address of their FOO server. The calendar
1629 client program can use SLP to obtain the FOO service: URL
1630 automatically, say 'service:foo://server1.nosuch.org', by issuing a
1631 Service Request. In the event that this FOO server failed, the
1632 Calendar client can issue the same service request again to find the
1633 backup FOO server, say 'service:foo://server2.nosuch.org'. In both
1634 cases, the service: URL conforms to the FOO service template as do
1635 the associated attributes (user and group.)
1636
1637 A network thermometer based on the above template could be advertised
1638 with the SLPv2 attribute list:
1639
1640 URL = service:net-transducer:thermometer://v33.test/ports=3211
1641 Attributes = (location-description=Missile bay 32),
1642 (operator=Joe Agent), (sample-units=C),
1643 (sample-resolution=10^-1),(sample-rate=10),
1644 (template-type=service:net-transducer:thermometer),
1645 (template-version=0.0),(template-description=
1646 The Thermometer is a Net-Transducer capable of reading temperature.
1647 The data is read by opening a TCP connection to one of the ports
1648 in the service URL and reading an ASCII string until an NULL
1649 character is encountered. The client may continue reading data at
1650 no faster than the sample-rate, or close the connection.),
1651 (template-url-syntax= \0D "ports=" port-list \OD
1652 port-list = port / port "," ports \OD
1653 port = 1*DIGIT \OD
1654 ; See the Service URL &lt;port&gt; production rule. \OD
1655 ; These are the ports connections can be made on.\OD)
1656
1657 This might be very useful for a technician who wanted to find a
1658 Thermometers in Missile bay 32, for example.
1659
1660 Note that the template attributes are advertised. The
1661 template-url-syntax value requires explicit escaped CR characters so
1662 that the ABNF syntax is correct.
1663
1664 <span class="h2"><a class="selflink" id="appendix-B" href="#appendix-B">B</a>. Acknowledgments</span>
1665
1666 Thanks to Michael Day and Leland Wallace for assisting with the IPX
1667 and AppleTalk address syntax portions. Ryan Moats provided valuable
1668 feedback throughout the writing of this document.
1669
1670
1671
1672
1673
1674
1675
1676 <span class="grey">Guttman, et al. Standards Track [Page 30]</span></pre>
1677 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-31" ></span>
1678 <span class="grey"><a href="./rfc2609">RFC 2609</a> Service Templates and URLs June 1999</span>
1679
1680
1681 <span class="h2"><a class="selflink" id="appendix-C" href="#appendix-C">C</a>. References</span>
1682
1683 [<a id="ref-1">1</a>] Protocol and service names, October 1994.
1684 <a href="ftp://ftp.isi.edu/in-notes/iana/assignments/service-names">ftp://ftp.isi.edu/in-notes/iana/assignments/service-names</a>.
1685
1686 [<a id="ref-2">2</a>] Port numbers, July 1997.
1687 <a href="ftp://ftp.isi.edu/in-notes/iana/assignments/port-numbers">ftp://ftp.isi.edu/in-notes/iana/assignments/port-numbers</a>.
1688
1689 [<a id="ref-3">3</a>] Alvestrand, H., "Tags for the Identification of Languages",
1690 <a href="./rfc1766">RFC 1766</a>, March 1995.
1691
1692 [<a id="ref-4">4</a>] ANSI. Coded Character Set -- 7-bit American Standard code for
1693 Information Interchange. X3.4-1986, 1986.
1694
1695 [<a id="ref-5">5</a>] Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform
1696 Resource Identifiers (URI): Generic Syntax", <a href="./rfc2396">RFC 2396</a>,
1697 August 1998.
1698
1699 [<a id="ref-6">6</a>] Bradner, S., "Key Words for Use in RFCs to Indicate
1700 Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
1701
1702 [<a id="ref-7">7</a>] Apple Computer. Inside Macintosh. Addison-Wesley, 1993.
1703
1704 [<a id="ref-8">8</a>] Crocker, D. and P. Overell, "Augmented BNF for Syntax
1705 Specifications: ABNF", <a href="./rfc2234">RFC 2234</a>, November 1997.
1706
1707 [<a id="ref-9">9</a>] S. Gursharan, R. Andrews, and A. Oppenheimer. Inside AppleTalk.
1708 Addison-Wesley, 1990.
1709
1710 [<a id="ref-10">10</a>] Guttman, E., Perkins, C., Veizades, J. and M. Day, "Service
1711 Location Protocol Version 2", <a href="./rfc2608">RFC 2608</a>, June 1999.
1712
1713 [<a id="ref-11">11</a>] Myers, J., "Simple Authentication and Security Layer (SASL)",
1714 <a href="./rfc2222">RFC 2222</a>, October 1997.
1715
1716 [<a id="ref-12">12</a>] Narten, T. and H. Alvestrand, "Guidelines for Writing
1717 an IANA Considerations Section in RFCs, <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>, <a href="./rfc2434">RFC 2434</a>,
1718 October 1998
1719
1720 [<a id="ref-13">13</a>] Newman C. and J. Myers, "ACAP -- Application Configuration
1721 Access Protocol", <a href="./rfc2244">RFC 2244</a>, November 1997.
1722
1723 [<a id="ref-14">14</a>] Inc Novell. IPX RIP and SAP Router Specification. Part Number
1724 107-000029-001, Version 1.30, May 1996.
1725
1726 [<a id="ref-15">15</a>] Veizades, J., Guttman, E., Perkins, C. and S. Kaplan, "Service
1727 Location Protocol", <a href="./rfc2165">RFC 2165</a>, July 1997.
1728
1729
1730
1731
1732 <span class="grey">Guttman, et al. Standards Track [Page 31]</span></pre>
1733 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-32" ></span>
1734 <span class="grey"><a href="./rfc2609">RFC 2609</a> Service Templates and URLs June 1999</span>
1735
1736
1737 [<a id="ref-16">16</a>] Yergeau, F., "UTF-8, a transformation format of ISO 10646",
1738 <a href="./rfc2279">RFC 2279</a>, January 1998.
1739
1740 <span class="h2"><a class="selflink" id="appendix-D" href="#appendix-D">D</a>. Authors' Addresses</span>
1741
1742 Questions about this memo can be directed to:
1743
1744 Erik Guttman
1745 Sun Microsystems
1746 Bahnstr. 2
1747 74915 Waibstadt
1748 Germany
1749
1750 Phone: +49 7263 911484
1751 Fax: +1 650 786 5992
1752 EMail: [email protected]
1753
1754
1755 Charles E. Perkins
1756 Sun Microsystems
1757 15 Network Circle
1758 Menlo Park, CA 94303
1759 USA
1760
1761 Phone: +1 650 786 6464
1762 Fas: +1 650 786 6445
1763 EMail: [email protected]
1764
1765
1766 James Kempf
1767 Sun Microsystems
1768 15 Network Circle
1769 Menlo Park, CA 94303
1770 USA
1771
1772 Phone: +1 650 786 5890
1773 Fax: +1 650 786 6445
1774 EMail: [email protected]
1775
1776
1777
1778
1779
1780
1781
1782
1783
1784
1785
1786
1787
1788 <span class="grey">Guttman, et al. Standards Track [Page 32]</span></pre>
1789 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-33" ></span>
1790 <span class="grey"><a href="./rfc2609">RFC 2609</a> Service Templates and URLs June 1999</span>
1791
1792
1793 <span class="h2"><a class="selflink" id="appendix-E" href="#appendix-E">E</a>. Full Copyright Statement</span>
1794
1795 Copyright (C) The Internet Society (1999). All Rights Reserved.
1796
1797 This document and translations of it may be copied and furnished to
1798 others, and derivative works that comment on or otherwise explain it
1799 or assist in its implementation may be prepared, copied, published
1800 and distributed, in whole or in part, without restriction of any
1801 kind, provided that the above copyright notice and this paragraph are
1802 included on all such copies and derivative works. However, this
1803 document itself may not be modified in any way, such as by removing
1804 the copyright notice or references to the Internet Society or other
1805 Internet organizations, except as needed for the purpose of
1806 developing Internet standards in which case the procedures for
1807 copyrights defined in the Internet Standards process must be
1808 followed, or as required to translate it into languages other than
1809 English.
1810
1811 The limited permissions granted above are perpetual and will not be
1812 revoked by the Internet Society or its successors or assigns.
1813
1814 This document and the information contained herein is provided on an
1815 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
1816 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
1817 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
1818 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
1819 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE."
1820
1821 Acknowledgement
1822
1823 Funding for the RFC Editor function is currently provided by the
1824 Internet Society.
1825
1826
1827
1828
1829
1830
1831
1832
1833
1834
1835
1836
1837
1838
1839
1840
1841
1842
1843
1844 Guttman, et al. Standards Track [Page 33]
1845 </pre>