Re: Transport-independent naming of services

Florian Weimer <fw@deneb.enyo.de> Tue, 15 July 2003 11:18 UTC

From: Florian Weimer <fw@deneb.enyo.de>
Subject: Re: Transport-independent naming of services
Date: Tue, 15 Jul 2003 13:18:55 +0200
Lines: 16
Sender: owner-namedroppers@ops.ietf.org
References: <OFF3415369.19D73DA4-ONC1256D62.004F12BF-C1256D62.004F4290@denic.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Cc: namedroppers@ops.ietf.org
X-From: owner-namedroppers@ops.ietf.org Tue Jul 15 13:26:40 2003
Return-path: <owner-namedroppers@ops.ietf.org>
To: Marcos Sanz/Denic <sanz@denic.de>
Mail-Followup-To: Marcos Sanz/Denic <sanz@denic.de>, namedroppers@ops.ietf.org
In-Reply-To: <OFF3415369.19D73DA4-ONC1256D62.004F12BF-C1256D62.004F4290@denic.de> (Marcos Sanz's message of "Sun, 13 Jul 2003 16:28:34 +0200")
User-Agent: Gnus/5.1003 (Gnus v5.10.3) Emacs/21.3 (gnu/linux)
Precedence: bulk
X-Message-ID:
Message-ID: <20140418071735.2560.27254.ARCHIVE@ietfa.amsl.com>

Marcos Sanz/Denic <sanz@denic.de> writes:

> 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

Thanks.  This proposal adds the an indirection that straight usage of
SRV RRs lacks, and it appears to be sufficient.

I still have to check if the protocol ballast is acceptable, though.

--
to unsubscribe send a message to namedroppers-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/namedroppers/>