IETF Logo Mail Archive

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

"Dan Wing" <dwing@cisco.com> Fri, 18 September 2009 18:34 UTC

Return-Path: <dwing@cisco.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 0D4EC3A6842 for <tae@core3.amsl.com>; Fri, 18 Sep 2009 11:34:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.532
X-Spam-Level:
X-Spam-Status: No, score=-6.532 tagged_above=-999 required=5 tests=[AWL=0.067, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 9Dr+x1eQYUJ4 for <tae@core3.amsl.com>; Fri, 18 Sep 2009 11:34:55 -0700 (PDT)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by core3.amsl.com (Postfix) with ESMTP id 5E7393A6991 for <tae@ietf.org>; Fri, 18 Sep 2009 11:34:54 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ap0EAHdvs0qrR7PE/2dsb2JhbACKbat+iFABkBYFhBuBXYki
X-IronPort-AV: E=Sophos;i="4.44,411,1249257600"; d="scan'208";a="95312701"
Received: from sj-dkim-4.cisco.com ([171.71.179.196]) by sj-iport-5.cisco.com with ESMTP; 18 Sep 2009 18:35:49 +0000
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-4.cisco.com (8.12.11/8.12.11) with ESMTP id n8IIZn4I016039; Fri, 18 Sep 2009 11:35:49 -0700
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id n8IIZnuM000596; Fri, 18 Sep 2009 18:35:49 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 18 Sep 2009 11:35:48 -0700
Received: from dwingwxp01 ([10.32.240.198]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 18 Sep 2009 11:35:48 -0700
From: Dan Wing <dwing@cisco.com>
To: 'Joe Touch' <touch@ISI.EDU>
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>
Date: Fri, 18 Sep 2009 11:35:48 -0700
Message-ID: <057601ca388e$d775e620$5da36b80@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: Aco4jOdDGRCFGJzPQlGnGqPTsK72cwAAOjaA
In-Reply-To: <4AB3CF61.5060208@isi.edu>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-OriginalArrivalTime: 18 Sep 2009 18:35:48.0606 (UTC) FILETIME=[D788D1E0:01CA388E]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=916; t=1253298949; x=1254162949; c=relaxed/simple; s=sjdkim4002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=dwing@cisco.com; z=From:=20=22Dan=20Wing=22=20<dwing@cisco.com> |Subject:=20RE=3A=20[tae]=20New=20draft=3A=20announcing=20t he=20supported=20transports=20via=20DNS |Sender:=20; bh=mBANJZmPa4TcI85jVQEVQkcIgipeLI6bYfxZqyljU9o=; b=Z5b+8Ty05rALjlEFlHr2nsBYhxezUuDgu8p8F1hIGLK8jF/ZxGuldsoJpl 7e+piELxrw94xtZwDOtGp81uKEBAMih6rXw1cx4sQJ4YIUApxCXL8NRxYpPu d3gcxygFkS;
Authentication-Results: sj-dkim-4; header.From=dwing@cisco.com; dkim=pass ( sig from cisco.com/sjdkim4002 verified; );
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:34:56 -0000

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

So, when you exchange them (in whatever application-specific protocol 
you're using to exchange those addresses, e.g., SDP for RTSP, SAP, 
and SIP) using that application-specific protocol is the best place 
to indicate which transport protocol is supported on the host.  This
is exactly how ICE extended SDP to allow indicating other transport
protocols, http://tools.ietf.org/html/draft-ietf-mmusic-ice-19.
The GROBJ BoF is where we're hoping to provide similar guidance to 
application developers who are referring IPv6/IPv4 addresses 
around.


Absent such an application-specific protocol to exchange addresses
we have the Internet's protocol to exchange addresses:  DNS.

-d

v2.23.0 | Report a Bug | By Email