Re: [tram] FW: New Version Notification for draft-patil-tram-turn-serv-disc-01.txt

Paul Kyzivat <pkyzivat@alum.mit.edu> Fri, 02 May 2014 18:43 UTC

Return-Path: <pkyzivat@alum.mit.edu>
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 E4CFB1A6FA9 for <tram@ietfa.amsl.com>; Fri, 2 May 2014 11:43:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level:
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665] autolearn=no
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 D9mq37ipPVJX for <tram@ietfa.amsl.com>; Fri, 2 May 2014 11:43:59 -0700 (PDT)
Received: from qmta08.westchester.pa.mail.comcast.net (qmta08.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:80]) by ietfa.amsl.com (Postfix) with ESMTP id C30081A0913 for <tram@ietf.org>; Fri, 2 May 2014 11:43:58 -0700 (PDT)
Received: from omta10.westchester.pa.mail.comcast.net ([76.96.62.28]) by qmta08.westchester.pa.mail.comcast.net with comcast id x4Qn1n0090cZkys586jwzu; Fri, 02 May 2014 18:43:56 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta10.westchester.pa.mail.comcast.net with comcast id x6jw1n00A3ZTu2S3W6jwfr; Fri, 02 May 2014 18:43:56 +0000
Message-ID: <5363E76C.1050807@alum.mit.edu>
Date: Fri, 02 May 2014 14:43:56 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: tram@ietf.org
References: <20140502095509.21732.16127.idtracker@ietfa.amsl.com> <CF8969C6.32FD1%praspati@cisco.com>
In-Reply-To: <CF8969C6.32FD1%praspati@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1399056236; bh=cJdCqnP84k7yJd7jKkpZSRzkQYKCS3Ln1nHrDtIyJq0=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=dewE6Vk18TX7xEHDrzYFZZKr6eZzqdoJB6DBzX/qavdsGXEWiFnJxihy5Wjwu+sci 7FgpsQcJ4HA5V80Dc+JZP6QG7+q5rdIRWMzoEeTtLkb8LPFnIfj+PM218Z2HNlyTry u9DzK6skiBUhoMGvapTWTF7Cck/3iBfmyJZzD4xjFn4rf/P6H0VGTS5LW8vYIbQJW1 ou0OnNHYKT5niW9ZThOSygPAKxlY+ek34jse6V/aMzu42KUBxzAuu6XgOoElvQw2KJ OpF0AB/EFwRWFCa3brPlcctWc62ir0v82z5CMDHiHiy5kLr04yxKSXO6MkjKMA3Sdp VW89KT3/ovPaA==
Archived-At: http://mailarchive.ietf.org/arch/msg/tram/wInDyuCp5wAAD56fO_vOf4tm6zw
Subject: Re: [tram] FW: New Version Notification for draft-patil-tram-turn-serv-disc-01.txt
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, 02 May 2014 18:44:00 -0000

There is another possible mechanism for retrieving a domain name for 
service discovery that isn't mentioned. It is analogous to "From own 
Identity". I guess I would call it "From target identity". In the case 
of SIP it would be to use the domain name of the To-URI.

This would be useful when a domain wants to make itself be reachable 
even from clients that have no better way of discovering a TURN server.

In general it is probably better to use one of the other techniques when 
possible, because the result can be used to talk to any target. But this 
is still a good option when the others fail. And it should be attractive 
to servers that want to maximize their reachability.

(I mentioned this one before, some time ago, but I guess it got lost 
along the way.)

Is there any reason not to include this as 4.1.4?

	Thanks,
	Paul

On 5/2/14 6:02 AM, Prashanth Patil (praspati) wrote:
> A new revision of the TURN server discovery draft has been published.
> Notable updates :
>
> * 300 (Try Alternate) response for anycast.
> * Mechanism described in draft-kist-alto-3pdisc i.e. using the clients own
> address to populate the DNS reverse zone (i.e., in-addr.arpa or ip6.arpa)
> with appropriate NAPTR records pointing to the TURN server.
> * Learning domain names from own identity.
>
> -Prashanth
>
>
> On 5/2/14 3:25 PM, "internet-drafts@ietf.org" <internet-drafts@ietf.org>
> wrote:
>
>>
>> A new version of I-D, draft-patil-tram-turn-serv-disc-01.txt
>> has been successfully submitted by Prashanth Patil and posted to the
>> IETF repository.
>>
>> Name:		draft-patil-tram-turn-serv-disc
>> Revision:	01
>> Title:		TURN Server Auto Discovery
>> Document date:	2014-05-02
>> Group:		Individual Submission
>> Pages:		11
>> URL:
>> http://www.ietf.org/internet-drafts/draft-patil-tram-turn-serv-disc-01.txt
>> Status:
>> https://datatracker.ietf.org/doc/draft-patil-tram-turn-serv-disc/
>> Htmlized:
>> http://tools.ietf.org/html/draft-patil-tram-turn-serv-disc-01
>> Diff:
>> http://www.ietf.org/rfcdiff?url2=draft-patil-tram-turn-serv-disc-01
>>
>> Abstract:
>>    Current Traversal Using Relays around NAT (TURN) server discovery
>>    mechanisms are relatively static and limited to explicit
>>    configuration.  These are usually under the administrative control of
>>    the application or TURN service provider, and not the enterprise or
>>    the ISP, the network in which the client is located.  Enterprises and
>>    ISPs wishing to provide their own TURN servers need auto discovery
>>    mechanisms that a TURN client could use with no or minimal
>>    configuration.  This document describes two such mechanisms for TURN
>>    server discovery.
>>
>>
>>
>>
>>
>> Please note that it may take a couple of minutes from the time of
>> submission
>> until the htmlized version and diff are available at tools.ietf.org.
>>
>> The IETF Secretariat
>>
>
> _______________________________________________
> tram mailing list
> tram@ietf.org
> https://www.ietf.org/mailman/listinfo/tram
>