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

Joe Touch <touch@ISI.EDU> Mon, 21 September 2009 14:43 UTC

Return-Path: <touch@ISI.EDU>
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 96B3C3A6ABF for <tae@core3.amsl.com>; Mon, 21 Sep 2009 07:43:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.562
X-Spam-Level:
X-Spam-Status: No, score=-2.562 tagged_above=-999 required=5 tests=[AWL=0.038, 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 hkaL1w7-CLOC for <tae@core3.amsl.com>; Mon, 21 Sep 2009 07:43:06 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by core3.amsl.com (Postfix) with ESMTP id 8B7A23A6AA2 for <tae@ietf.org>; Mon, 21 Sep 2009 07:43:04 -0700 (PDT)
Received: from [75.194.91.99] (99.sub-75-194-91.myvzw.com [75.194.91.99]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id n8LEhZ9N023499 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 21 Sep 2009 07:43:44 -0700 (PDT)
Message-ID: <4AB7910D.3030007@isi.edu>
Date: Mon, 21 Sep 2009 07:43:25 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.23 (Windows/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> <4AB2E6AB.7020409@gmail.com><4AB3A33B.7080909@ifi.uio.no> <4AB3A5DE.1040708@isi.edu> <055001ca388b$163a0070$5da36b80@cisco.com> <4AB3CF61.5060208@isi.edu> <38542A4D-C3D0-4BE8-BF2B-FB99252C596C@asomi.com>
In-Reply-To: <38542A4D-C3D0-4BE8-BF2B-FB99252C596C@asomi.com>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
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: Mon, 21 Sep 2009 14:43:07 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Caitlin Bestler wrote:
> 
> On Sep 18, 2009, at 11:20 AM, Joe Touch wrote:
...
>> As you note, addresses are sometimes used for non-human purposes, and
>> with IPv6 they could be created on the fly - I wouldn't want to have to
>> wait to register them in the DNS vs exchanging them in-band.
> 
> Of course if you have already used application specific mechanisms to
> exchange
> IP addresses in-band then you obviously have the means to specify which
> transport protocol and options to use as well.

I could give you an IP address, and still want you to negotiate a
transport you support with a transport that IP address supports. I can't
know that answer, so it's not my business to specify the transport.

Ultimately, either you're solving the transport discovery problem, or
you're solving some other much more limited, DNS-focused case driven by
a particular example. I'm not sure why that would be useful if you can
solve the general case, but if so, it'd be important to explain that the
'applicability' of DNS-focused solutions.

Joe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)

iEYEARECAAYFAkq3kQwACgkQE5f5cImnZrupagCdFO7Gc4iNmNGrkhrUoSIvX6pJ
t+cAni6PaLP63Zrgo8uvrqgSKe7oJ5wv
=fMso
-----END PGP SIGNATURE-----