W3C home > Mailing lists > Public > www-xkms@w3.org > September 2002

XKMS tokens for use with SRV

From: Joseph Reagle <reagle@w3.org>
Date: Wed, 18 Sep 2002 12:47:40 -0400
To: XKMS <www-xkms@w3.org>
Message-Id: <200209181247.40727.reagle@w3.org>

>13 Clarification/ Phill Hallam- Baker, Joseph Reagle [ Sept 2002 F2F]
>[Part I - 2002/08/01]
>The SRV prefix for an XKMS service in DNS should be specified here once it 
>is established. Make changes as described.  [ Sept 2002F2F]

I have briefly investigated the registration of SRV service tokens for XKMS. 
SRV allows a single server (e.g., example.com) to delegate services to 
specific services. An example from from RFC2782:
   _Service._Proto.Name TTL Class SRV Priority Weight Port Target
I'm no expert in this, I've never heard of it prior to this issue being 

My conclusion is:
1. This is a relatively new standards track document and it's not clear that 
there's any immediate requirement for this from XKMS. Presently, SIP is the 
only registered service.
2. There's no easy registration form for such values:
We would need to publish some form of informational RFC, I don't know what 
the requirements for such a document are.
2. I'm not sure if SRV's are intended to be used with services on top of 
HTTP. There is no _Proto corresponding to HTTP, and to be more specific 
(e.g,. _TCP or _UDP) would be inappropriate. One might take the cross 
product and have a service for every single protocol binding, such as 
XKMS+TCP, XKMS+UDP, XKMS+SMTP, etc., but this is not that compelling to me 
and I still can't distinguish between those on HTTP, and one actually 
running directly on TCP.

Consequently I recommend we take no action and wait for those Web services 
with actual requirements to take the lead if ever considered necessary.
Received on Wednesday, 18 September 2002 12:48:02 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:07:20 UTC