Re: Transport-independent naming of services

Marcos Sanz/Denic <sanz@denic.de> Sun, 13 July 2003 14:28 UTC

From: Marcos Sanz/Denic <sanz@denic.de>
Subject: Re: Transport-independent naming of services
Date: Sun, 13 Jul 2003 16:28:34 +0200
Lines: 67
Sender: owner-namedroppers@ops.ietf.org
References: <87u19sgj11.fsf@deneb.enyo.de>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=_alternative 004F4085C1256D62_="
Cc: namedroppers@ops.ietf.org
In-Reply-To: <87u19sgj11.fsf@deneb.enyo.de>
To: Florian Weimer <fw@deneb.enyo.de>
Precedence: bulk
Message-ID: <20140418071735.2560.11904.ARCHIVE@ietfa.amsl.com>

On 12.07.2003 12:02 Florian Weimer <fw@deneb.enyo.de> wrote:
> 
> A distributed application APP can use various transports (e.g., TCP and
> SCTP, or, at a higher level, HTTP, HTTPS, WebDAV, SFTP and FTP) to
> access remote resources.  Remote resources are identified by a
> domain name.
> 
> Can existing DNS RRs be used to describe this scenario in a meaningful
> way?  Registering a new SRV service doesn't help because the SRV RR
> data does not indicate the transport service (just its port number,
> which is not enough data).  The only approach seems to be to register
> SRV service names "APP_http", "APP_https" etc. and to query for all
> services the application might support, but this is not very elegant.
> 
> Any suggestions?

A "straightforward" use of NAPTR records (NAPSTR) could be the thing you 
are looking for:
http://www.ietf.org/internet-drafts/draft-daigle-napstr-02.txt

Best regards,
Marcos Sanz
DENIC eG

Transport-independent naming of services Florian Weimer
Re: Transport-independent naming of services Marcos Sanz/Denic
Re: Transport-independent naming of services Brad Hards
Re: Transport-independent naming of services Florian Weimer