IETF Logo Mail Archive

Re: Transport-independent naming of services

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

Received: from psg.com (mailnull@psg.com [147.28.0.62]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14306 for <dnsext-archive@lists.ietf.org>; Tue, 15 Jul 2003 07:22:28 -0400 (EDT)
Received: from lserv by psg.com with local (Exim 4.14) id 19cNpj-0008F1-Ld for namedroppers-data@psg.com; Tue, 15 Jul 2003 11:18:59 +0000
Received: from [213.178.169.5] (helo=ext1.enyo.de) by psg.com with esmtp (Exim 4.14) id 19cNph-0008Ed-0e for namedroppers@ops.ietf.org; Tue, 15 Jul 2003 11:18:57 +0000
Received: from host-212-9-162-162.dial.netic.de ([212.9.162.162] helo=mail.enyo.de) by ext1.enyo.de with asmtp (Exim 4.20) id 19cNpg-000Li8-1f; Tue, 15 Jul 2003 13:18:56 +0200
Received: from [212.9.189.171] (helo=deneb.enyo.de) by mail.enyo.de with esmtp (Exim 4.20) id 19cNpg-0004qs-G6; Tue, 15 Jul 2003 13:18:56 +0200
Received: from fw by deneb.enyo.de with local (Exim 4.20) id 19cNpf-00051f-Io; Tue, 15 Jul 2003 13:18:55 +0200
To: Marcos Sanz/Denic <sanz@denic.de>
Cc: namedroppers@ops.ietf.org
Subject: Re: Transport-independent naming of services
References: <OFF3415369.19D73DA4-ONC1256D62.004F12BF-C1256D62.004F4290@denic.de>
From: Florian Weimer <fw@deneb.enyo.de>
Mail-Followup-To: Marcos Sanz/Denic <sanz@denic.de>, namedroppers@ops.ietf.org
Date: Tue, 15 Jul 2003 13:18:55 +0200
In-Reply-To: <OFF3415369.19D73DA4-ONC1256D62.004F12BF-C1256D62.004F4290@denic.de> (Marcos Sanz's message of "Sun, 13 Jul 2003 16:28:34 +0200")
Message-ID: <87smp8f36o.fsf@deneb.enyo.de>
User-Agent: Gnus/5.1003 (Gnus v5.10.3) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Spam-Status: No, hits=-35.3 required=5.0 tests=BAYES_20,EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT, REFERENCES,REPLY_WITH_QUOTES,USER_AGENT_GNUS_UA autolearn=ham version=2.53
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk

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/>

v2.23.0 | Report a Bug | By Email