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

"Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com> Thu, 20 March 2014 14:49 UTC

Return-Path: <tireddy@cisco.com>
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 6CB411A08E6 for <tram@ietfa.amsl.com>; Thu, 20 Mar 2014 07:49:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.047
X-Spam-Level:
X-Spam-Status: No, score=-10.047 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 FrGYtjZAEQsR for <tram@ietfa.amsl.com>; Thu, 20 Mar 2014 07:49:07 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) by ietfa.amsl.com (Postfix) with ESMTP id CB1391A08ED for <tram@ietf.org>; Thu, 20 Mar 2014 07:48:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8805; q=dns/txt; s=iport; t=1395326927; x=1396536527; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=IPf4vajeDk7lVmJDFhzS44Tae+3xNSLlmqcuGbNMlDE=; b=haSamQ5cr5D7Jr9XBMt0K8LZY41aHTR3iyLTPbUXJnfJOvnrvPbYZP4h q4EXM7yET/eSmHuTK4PR8VhJ9rfPpIhdM1hZDESgeAjK5Ohrd8sohTmHM 4A24YS86vTko2z0VMk3dnVX6p9GJtcSB+I3gMM0nw18JVI4BortR8uF8E s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqMFADL/KlOtJV2Z/2dsb2JhbABZgkJEO1eFaLN1iHGBGBZ0giYBAQQtTBACAQgiJDIlAgQBDQ0Th14Nz1UXjjQxB4MkgRQEmXmQfoMtgis
X-IronPort-AV: E=Sophos; i="4.97,695,1389744000"; d="scan'208,217"; a="29020399"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by alln-iport-4.cisco.com with ESMTP; 20 Mar 2014 14:48:46 +0000
Received: from xhc-rcd-x12.cisco.com (xhc-rcd-x12.cisco.com [173.37.183.86]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s2KEmk7u003272 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 20 Mar 2014 14:48:46 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.233]) by xhc-rcd-x12.cisco.com ([173.37.183.86]) with mapi id 14.03.0123.003; Thu, 20 Mar 2014 09:48:46 -0500
From: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
To: Cb B <cb.list6@gmail.com>, Simon Perreault <simon.perreault@viagenie.ca>
Thread-Topic: [tram] TURN server discovery (please discuss!)
Thread-Index: AQHPREOE1UDf9oubAkWwBYvhNFfsfZrqVuQA//+xblA=
Date: Thu, 20 Mar 2014 14:48:45 +0000
Message-ID: <913383AAA69FF945B8F946018B75898A242D8EFD@xmb-rcd-x10.cisco.com>
References: <532AF25B.4020301@viagenie.ca> <CAD6AjGRYE-GcQwnwK14ERrVsKNVq1R1xovJV7HPoZk=R5Yf9hQ@mail.gmail.com>
In-Reply-To: <CAD6AjGRYE-GcQwnwK14ERrVsKNVq1R1xovJV7HPoZk=R5Yf9hQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.65.67.182]
Content-Type: multipart/alternative; boundary="_000_913383AAA69FF945B8F946018B75898A242D8EFDxmbrcdx10ciscoc_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/tram/5uxhVF5Xmye_cpIIdgLOL9-WY1s
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: Thu, 20 Mar 2014 14:49:09 -0000

Just adding a data point, mobile networks generally don't use dhcp so that limits the scope of dhcp as an option.

I anticipate mobile networks will need TURN.

CB
[TR]

we had discussed similar problem to discover PCP servers in Mobile Networks (http://tools.ietf.org/html/draft-chen-pcp-mobile-deployment-04#section-4) sometime back. Based on the discussion
1)DHCPv6 stateless configuration information is supported by 3GPP specification (http://tools.ietf.org/html/rfc6459#section-5.2)

2)Since DHCPv4 is not widely used, possible solutions discussed to solve the problem are anycast, enhancing PCO to provide TURN {PCP} server IP address



-Tiru