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

Joe Touch <touch@ISI.EDU> Fri, 18 September 2009 18:21 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 4FDA028C118 for <tae@core3.amsl.com>; Fri, 18 Sep 2009 11:21:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.434
X-Spam-Level:
X-Spam-Status: No, score=-2.434 tagged_above=-999 required=5 tests=[AWL=0.165, 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 2BtfeEFIO9qw for <tae@core3.amsl.com>; Fri, 18 Sep 2009 11:21:00 -0700 (PDT)
Received: from nitro.isi.edu (nitro.isi.edu [128.9.208.207]) by core3.amsl.com (Postfix) with ESMTP id 2702C3A6A3D for <tae@ietf.org>; Fri, 18 Sep 2009 11:21:00 -0700 (PDT)
Received: from [75.237.87.16] (16.sub-75-237-87.myvzw.com [75.237.87.16]) (authenticated bits=0) by nitro.isi.edu (8.13.8/8.13.8) with ESMTP id n8IIKIFK006386 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 18 Sep 2009 11:20:22 -0700 (PDT)
Message-ID: <4AB3CF61.5060208@isi.edu>
Date: Fri, 18 Sep 2009 11:20:17 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Dan Wing <dwing@cisco.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>
In-Reply-To: <055001ca388b$163a0070$5da36b80@cisco.com>
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-MailScanner-ID: n8IIKIFK006386
X-ISI-4-69-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: Fri, 18 Sep 2009 18:21:01 -0000

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



Dan Wing wrote:
>  
> 
>> -----Original Message-----
>> From: tae-bounces@ietf.org [mailto:tae-bounces@ietf.org] On 
>> Behalf Of Joe Touch
>> Sent: Friday, September 18, 2009 8:23 AM
>> To: Michael Welzl
>> Cc: tae@ietf.org
>> Subject: Re: [tae] New draft: announcing the supported 
>> transports via DNS
>>
> 
> 
> Michael Welzl wrote:
>>>> Hi all,
>>>>
>>>> This discussion reminds me of something else:
>>>> someone (I think Jana?) mentioned the possibility of negotiating
>>>> more than just the transport protocol, e.g. even the usage of IPv6,
>>>> with a negotiation protocol.
>>>>
>>>> I recently talked about this with someone who knows more about
>>>> IPv6 than me (actually not hard to find such a person!), and that
>>>> someone said that a standard is already in place for determining
>>>> whether IPv6 can be used **via DNS**.
> That presumes two things:
> 
> a) you know which protocol to use to get to the DNS
> 
> b) not everybody uses the DNS, at which point you definitely need to
> know the address format since you need to know the address
> 
>> Not everybody uses TCP, either.  For example, RTP is commonly
>> sent over UDP and the IPv4 addresses are commonly signaled in
>> SDP as IPv4 address literals.  So RTP doesn't use DNS or TCP.
> 
>> But DNS-less and TCP-less applications or usage are not the
>> 80% that is the interesting problem.  I can't maintain
>> host tables for the Internet anymore -- it's too big.  The need
>> for DNS is more acute with long and awkward IPv6 addresses.

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.

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

iEYEARECAAYFAkqzz2EACgkQE5f5cImnZrtbuwCeJ1q/llgMNdSjgTjxqeVV8wRl
eUYAoIojx7AegGO5bDY8NC+Hikegb6st
=Wya+
-----END PGP SIGNATURE-----