Browse Prior Art Database

Service Templates and Service: Schemes (RFC2609)

IP.com Disclosure Number: IPCOM000003196D
Original Publication Date: 1999-Jun-01
Included in the Prior Art Database: 2000-Sep-13
Document File: 27 page(s) / 68K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

E. Guttman: AUTHOR [+3]

Abstract

The "service:" URL scheme name is used to define URLs (called "service: URLs" in this document) that are primarily intended to be used by the Service Location Protocol in order to distribute service access information. These schemes provide an extensible framework for client-based network software to obtain configuration information required to make use of network services. When registering a service: URL, the URL is accompanied by a set of well-defined attributes which define the service. These attributes convey configuration information to client software, or service characteristics meaningful to end users.

This text was extracted from a ASCII Text document.
This is the abbreviated version, containing approximately 4% of the total text.

Network Working Group E. Guttman

Request for Comments: 2609 C. Perkins

Updates: 2165 J. Kempf

Category: Standards Track Sun Microsystems

June 1999

Service Templates and Service: Schemes

Status of This Memo

This document specifies an Internet standards track protocol for the

Internet community, and requests discussion and suggestions for

improvements. Please refer to the current edition of the "Internet

Official Protocol Standards" (STD 1) for the standardization state

and status of this protocol. Distribution of this memo is unlimited.

Copyright Notice

Copyright (C) The Internet Society (1999). All Rights Reserved.

Abstract

The "service:" URL scheme name is used to define URLs (called

"service: URLs" in this document) that are primarily intended to be

used by the Service Location Protocol in order to distribute service

access information. These schemes provide an extensible framework

for client-based network software to obtain configuration information

required to make use of network services. When registering a

service: URL, the URL is accompanied by a set of well-defined

attributes which define the service. These attributes convey

configuration information to client software, or service

characteristics meaningful to end users.

This document describes a formal procedure for defining and

standardizing new service types and attributes for use with the

"service:" scheme. The formal descriptions of service types and

attributes are templates that are human and machine understandable.

They SHOULD be used by administrative tools to parse service

registration information and by client applications to provide

localized translations of service attribute strings.

Table of Contents

1. Introduction 2

1.1. Terminology . . . . . . . . . . . . . . . . . . . . . 3

1.2. Service Location Protocol . . . . . . . . . . . . . . 5

1.2.1. Compatibility with SLPv1 . . . . . . . . . . . 5

2. Service URL Syntax and Semantics 5

2.1. Service URL Syntax . . . . . . . . . . . . . . . . . 5

2.2. Service URL Semantics . . . . . . . . . . . . . . . . 8

2.3. Use of service: URLs . . . . . . . . . . . . . . . . 9

2.4. Specifying the Service Type-Specific URL Syntax. . . . 10

2.5. Accommodating Abstract Service Types . . . . . . . . 10

2.5.1. Advertising Abstract Service Types . . . . . . 11

3. Syntax and Semantics of Service Type Specifications 12

3.1. Syntax of Service Type Templates . . . . . . . . . . 12

3.2. Semantics of Service Type Templates. . . . . . . . . . 15

3.2.1...