IETF Logo Mail Archive

Re: [tram] TURN server discovery (please discuss!)

Simon Perreault <simon.perreault@viagenie.ca> Fri, 21 March 2014 13:02 UTC

Return-Path: <simon.perreault@viagenie.ca>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B14721A04FA for <tram@ietfa.amsl.com>; Fri, 21 Mar 2014 06:02:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level:
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s9k4CLq5qq36 for <tram@ietfa.amsl.com>; Fri, 21 Mar 2014 06:02:17 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id C49481A03D2 for <tram@ietf.org>; Fri, 21 Mar 2014 06:02:17 -0700 (PDT)
Received: from porto.nomis80.org (unknown [IPv6:2620:0:230:c000:f981:e226:281f:c92d]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 4E03F40203; Fri, 21 Mar 2014 09:02:08 -0400 (EDT)
Message-ID: <532C384F.4080601@viagenie.ca>
Date: Fri, 21 Mar 2014 09:02:07 -0400
From: Simon Perreault <simon.perreault@viagenie.ca>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>, Cb B <cb.list6@gmail.com>
References: <913383AAA69FF945B8F946018B75898A242D98F2@xmb-rcd-x10.cisco.com>
In-Reply-To: <913383AAA69FF945B8F946018B75898A242D98F2@xmb-rcd-x10.cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/tram/sGvdclCJv-z72j0XFjjyqaujdVA
Cc: "tram@ietf.org" <tram@ietf.org>
Subject: Re: [tram] TURN server discovery (please discuss!)
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussing the creation of a Turn Revised And Modernized \(TRAM\) WG, which goal is to consolidate the various initiatives to update TURN and STUN." <tram.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tram>, <mailto:tram-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tram/>
List-Post: <mailto:tram@ietf.org>
List-Help: <mailto:tram-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tram>, <mailto:tram-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Mar 2014 13:02:19 -0000

Le 2014-03-21 03:36, Tirumaleswar Reddy (tireddy) a écrit :
>> Today with IMS in mobile networks, NAPTR is used in DNS, so in would suggest that as a viable path 
> 
> Even the TURN discovery draft is using NAPTR http://tools.ietf.org/html/draft-patil-tram-turn-serv-disc-00#section-4.2; But DHCP is used to get the domain name to be used for TURN service discovery. 
> Is there any other mechanism to get the domain name ?

Yes. Please refer to:
http://tools.ietf.org/html/draft-kist-alto-3pdisc

That discovery mechanism looks up NAPTR records in the
{in-addr,ip6}.arpa zone corresponding to the IP address(es) that the
client was assigned by the network. No DHCP involved.

Simon
-- 
DTN made easy, lean, and smart --> http://postellation.viagenie.ca
NAT64/DNS64 open-source        --> http://ecdysis.viagenie.ca
STUN/TURN server               --> http://numb.viagenie.ca

v2.23.0 | Report a Bug | By Email