Re: [tae] New draft: announcing the supported transports via DNS

Melinda Shore <melinda.shore@gmail.com> Fri, 18 September 2009 01:46 UTC

Return-Path: <melinda.shore@gmail.com>
X-Original-To: tae@core3.amsl.com
Delivered-To: tae@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 982873A681A for <tae@core3.amsl.com>; Thu, 17 Sep 2009 18:46:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 FeWwVeABkkDU for <tae@core3.amsl.com>; Thu, 17 Sep 2009 18:46:39 -0700 (PDT)
Received: from mail-px0-f173.google.com (mail-px0-f173.google.com [209.85.216.173]) by core3.amsl.com (Postfix) with ESMTP id E44C73A6828 for <tae@ietf.org>; Thu, 17 Sep 2009 18:46:39 -0700 (PDT)
Received: by pxi3 with SMTP id 3so487735pxi.31 for <tae@ietf.org>; Thu, 17 Sep 2009 18:47:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=30Dt/Gie+nVuJmutrGrb84G1X0gZU7iq+0PDMJmPd+8=; b=MjDul5uROQxO8KEeO+pNk156ip2gdeXwC2gIGzTBl0ZPFpRG8De/bjRPQYTc3jjh2/ 7KmGOk38RfPKXJ1c4IXHg86JBngPtuLgK3y4f3TfuHD2f8F1XRvxmcg5JByqSXO2kk3h zpwqWOJl88sS84PWEAbp4M/48vRToTTDcPus4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=fLrnUp3ZQOiZGbemPttI1+0jJ7HxLQpnAzIFcl9TlOh5zor0wOjR3fl44CB12on6BS dFliUZbqmCK+3vdlVtocUXD4wlwTb69hhlyRlndT9HmdbOdCHbw7kphHi85xiN1fx+mk k1teKcQYefTVjA1mSgB3DJ18LNqNuQ03sucDw=
Received: by 10.114.55.34 with SMTP id d34mr1269212waa.225.1253238448600; Thu, 17 Sep 2009 18:47:28 -0700 (PDT)
Received: from polypro.local (216-67-41-79-rb1.fai.dsl.dynamic.acsalaska.net [216.67.41.79]) by mx.google.com with ESMTPS id 22sm618958pxi.10.2009.09.17.18.47.24 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 17 Sep 2009 18:47:27 -0700 (PDT)
Message-ID: <4AB2E6AB.7020409@gmail.com>
Date: Thu, 17 Sep 2009 17:47:23 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: Caitlin Bestler <cait@asomi.com>
References: <Pine.LNX.4.64.0909180057060.5479@zippy.stdio.be> <77F0974F-62CD-411C-96D3-C29E6D872DEA@asomi.com>
In-Reply-To: <77F0974F-62CD-411C-96D3-C29E6D872DEA@asomi.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: tae@ietf.org
Subject: Re: [tae] New draft: announcing the supported transports via DNS
X-BeenThere: tae@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Transport Architecture Evolution <tae.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tae>, <mailto:tae-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tae>
List-Post: <mailto:tae@ietf.org>
List-Help: <mailto:tae-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tae>, <mailto:tae-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Sep 2009 01:46:40 -0000

Caitlin Bestler wrote:
> The main problem I see is that the comma separated mechanism is probably 
> insufficient to deal with the combination of
> encryption protocols, transport protocols and special adaptations (RDMA, 
> SCTP Partial Reliability, etc.) Something more
> along the lines of a unique Java class name might be needed, with simple 
> reserved names for the obvious: tcp, udp, sctp, ...

I like structured namespaces but I think that an
hierarchical one might be overly limiting for something
like this, where future needs might not be possible
to anticipate.  I'm inclined to think that this is
one application for which a faceted classification/
namespace might be very well-suited.

I'm not crazy about adding yet more cruft to DNS,
either, but its advantage, which isn't trivial, is that
it doesn't require changes to other protocols and that
stuff that implements this approach is interoperable
with stuff that doesn't.  There also shouldn't be
performance impacts on the transport, nor would there
be ... firewall traversal impacts.

Melinda