Re: [dnsext] New Version Notification - draft-gudmundsson-dnsext-srv-clarify-01.txt (fwd)

Florian Weimer <fweimer@bfk.de> Thu, 01 July 2010 07:29 UTC

Return-Path: <owner-namedroppers@ops.ietf.org>
X-Original-To: ietfarch-namedroppers-archive-gleetwall6@core3.amsl.com
Delivered-To: ietfarch-namedroppers-archive-gleetwall6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2BEB93A67C3; Thu, 1 Jul 2010 00:29:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.896
X-Spam-Level:
X-Spam-Status: No, score=0.896 tagged_above=-999 required=5 tests=[AWL=0.146, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_EQ_DE=0.35, HELO_MISMATCH_DE=1.448, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xxrX+yDVImBU; Thu, 1 Jul 2010 00:29:38 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by core3.amsl.com (Postfix) with ESMTP id 03C4D3A67D7; Thu, 1 Jul 2010 00:29:37 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.72 (FreeBSD)) (envelope-from <owner-namedroppers@ops.ietf.org>) id 1OUE6t-000G5C-3N for namedroppers-data0@psg.com; Thu, 01 Jul 2010 07:22:59 +0000
Received: from [193.227.124.2] (helo=mx01.bfk.de) by psg.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <fweimer@bfk.de>) id 1OUE6q-000G4T-Gq for namedroppers@ops.ietf.org; Thu, 01 Jul 2010 07:22:56 +0000
Received: from mx00.int.bfk.de ([10.119.110.2]) by mx01.bfk.de with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) id 1OUE6l-00038h-IP; Thu, 01 Jul 2010 07:22:51 +0000
Received: by bfk.de with local id 1OUE6h-0006QG-1C; Thu, 01 Jul 2010 07:22:47 +0000
To: Alfred =?hp-roman8?B?SM5uZXM=?= <ah@TR-Sys.de>
Cc: namedroppers@ops.ietf.org, dnsop@ietf.org, apps-discuss@ietf.org
Subject: Re: [dnsext] New Version Notification - draft-gudmundsson-dnsext-srv-clarify-01.txt (fwd)
References: <201006301816.UAA26126@TR-Sys.de>
From: Florian Weimer <fweimer@bfk.de>
Date: Thu, 01 Jul 2010 07:22:46 +0000
In-Reply-To: <201006301816.UAA26126@TR-Sys.de> (Alfred's message of "Wed\, 30 Jun 2010 20\:16\:20 +0200 \(MESZ\)")
Message-ID: <82fx031xa1.fsf@mid.bfk.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: owner-namedroppers@ops.ietf.org
Precedence: bulk
List-ID: <namedroppers.ops.ietf.org>
List-Unsubscribe: To unsubscribe send a message to namedroppers-request@ops.ietf.org with
List-Unsubscribe: the word 'unsubscribe' in a single line as the message text body.
List-Archive: <http://ops.ietf.org/lists/namedroppers/>

* Alfred:

> My apologies for cross-posting,
> but this is inherently a cross-wg and cross-area topic:
>
> The revised draft contains clarifications for DNS service discovery
> using SRV RRs and suggests methods to deal with the restrictions
> imposed by draft-ietf-tsvwg-iana-ports.  It is intended that both
> drafts will eventually be published in a coordinated manner.
>
>
> Abstract
>
>    The DNS SRV record has been specified in RFC 2052 and RFC 2782 for
>    use in dynamic service discovery for a domain.  These two RFCs did
>    not clearly specify an IANA registry for the names of the services
>    and their underlying protocols.  This document clarifies RFC 2782
>    regarding the formation and use of the Service Prefix in the owner
>    name of SRV records, based on the unified IANA registry for "Service
>    Names and Transport Protocol Port Numbers".

Wouldn't it be better to put that effort into a SRV successor which
focuses on cryptographic binding and the introduction of (generic,
cross-application) transports above TCP/UDP?

Right now, we've got many protocols which can run over HTTP(S) and
home-grown pseudo-transport layers, and with SRV records, it is not
possible to figure out if HTTP is to be used or not.

-- 
Florian Weimer                <fweimer@bfk.de>
BFK edv-consulting GmbH       http://www.bfk.de/
Kriegsstraße 100              tel: +49-721-96201-1
D-76133 Karlsruhe             fax: +49-721-96201-99