FWD: A change to Service URLs?

Reviewing and/or approving specific URL schemes is beyond the scope of
the URLREG WG.  However, if any individuals on this list have suggestions
for Erik, please feel free to communicate them to him or to the _SRVLOC_
list directly.

Rich Petke ([email protected])

---------- Forwarded Message ----------

From:	Erik Guttman, >INTERNET:[email protected]
TO:	(unknown), INTERNET:[email protected]
CC:	Erik Guttman, INTERNET:[email protected]
DATE:	2/18/1998 2:04 AM

RE:	A change to Service URLs?

Sender: [email protected]
Received: from wicked.neato.org (wicked.neato.org [198.70.96.252])
	by dub-img-7.compuserve.com (8.8.6/8.8.6/2.10) with ESMTP id CAA20054
	for <[email protected]>; Wed, 18 Feb 1998 02:04:42 -0500 (EST)
Received: from localhost (daemon@localhost)
	by wicked.neato.org (8.8.5/8.8.5) with SMTP id WAA26852;
	Tue, 17 Feb 1998 22:54:51 -0800 (PST)
Received: by wicked.neato.org (bulk_mailer v1.5); Tue, 17 Feb 1998 22:54:50 -0800
Received: (from majordom@localhost)
	by wicked.neato.org (8.8.5/8.8.5) id WAA26838
	for srvloc-outgoing; Tue, 17 Feb 1998 22:54:46 -0800 (PST)
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by wicked.neato.org (8.8.5/8.8.5) with SMTP id WAA26834
	for <[email protected]>; Tue, 17 Feb 1998 22:54:43 -0800 (PST)
Received: from Eng.Sun.COM (engmail2 [129.146.1.25]) by mercury.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id WAA21176 for <[email protected]>; Tue, 17 Feb 1998 22:50:33 -0800
Received: from hsmpka.eng.sun.com (phys-hsmpka.Eng.Sun.COM [129.146.121.37])
	by Eng.Sun.COM (SMI-8.6/SMI-5.3) with SMTP id WAA08822;
	Tue, 17 Feb 1998 22:50:31 -0800
Received: from vayne by hsmpka.eng.sun.com (SMI-8.6/SMI-SVR4)
	id WAA01690; Tue, 17 Feb 1998 22:50:28 -0800
Date: Wed, 18 Feb 1998 07:53:00 +0100 (MET)
From: Erik Guttman <[email protected]>
Reply-To: Erik Guttman <[email protected]>
Subject: A change to Service URLs?
To: [email protected]
Cc: Erik Guttman <[email protected]>
Message-ID: <[email protected]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Sender: [email protected]


I have been examining other service representations, such as the 
format for /etc/services and SRV RRs (RFC 2052).

I believe it might be wise for the Service URL to have the following
production:

  "service:" <srvtype> "://" [<transport> "@"] <host> [":" <port>] ["/" <path>
]

The new part is the 'transport' section.  This is optional.  The default
transport is "TCP".  If another transport is used, such as UDP, then this
field is added.  A service which supports both would be represented
as two service URLs, one for the TCP and one for UDP - for example:

  service:kerberos://somehost.someorg.org:750
  service:kerberos://[email protected]:750

Other transports could be added here, such as NETBLT, RDP, IL, etc. if
desired.

It is far better to add these in the URL than as an attribute as the 
set of attributes may not be available if the URL is obtained in a context
outside of SLP.  The other option, of course would be to add a 'transport'
attribute to registrations.  A service could *list* the transports it provides
in this attribute.  

Please let me know what you think.

Erik Guttman