Re: [tram] Stephen Farrell's Discuss on draft-ietf-tram-turn-third-party-authz-13: (with DISCUSS and COMMENT)

Brandon Williams <brandon.williams@akamai.com> Tue, 21 April 2015 18:46 UTC

Return-Path: <brandon.williams@akamai.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 146DA1A88C8 for <tram@ietfa.amsl.com>; Tue, 21 Apr 2015 11:46:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 41-7nxfe0Lxm for <tram@ietfa.amsl.com>; Tue, 21 Apr 2015 11:46:20 -0700 (PDT)
Received: from prod-mail-xrelay02.akamai.com (prod-mail-xrelay02.akamai.com [72.246.2.14]) by ietfa.amsl.com (Postfix) with ESMTP id A29A41A893E for <tram@ietf.org>; Tue, 21 Apr 2015 11:46:20 -0700 (PDT)
Received: from prod-mail-xrelay02.akamai.com (localhost [127.0.0.1]) by postfix.imss70 (Postfix) with ESMTP id CAE892852D for <tram@ietf.org>; Tue, 21 Apr 2015 18:46:19 +0000 (GMT)
Received: from prod-mail-relay07.akamai.com (prod-mail-relay07.akamai.com [172.17.121.112]) by prod-mail-xrelay02.akamai.com (Postfix) with ESMTP id B8D642852B for <tram@ietf.org>; Tue, 21 Apr 2015 18:46:19 +0000 (GMT)
Received: from [172.28.115.172] (unknown [172.28.115.172]) by prod-mail-relay07.akamai.com (Postfix) with ESMTP id A902E80059 for <tram@ietf.org>; Tue, 21 Apr 2015 18:46:19 +0000 (GMT)
Message-ID: <55369AFB.4050907@akamai.com>
Date: Tue, 21 Apr 2015 14:46:19 -0400
From: Brandon Williams <brandon.williams@akamai.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: tram@ietf.org
References: <913383AAA69FF945B8F946018B75898A4120E570@xmb-rcd-x10.cisco.com>
In-Reply-To: <913383AAA69FF945B8F946018B75898A4120E570@xmb-rcd-x10.cisco.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/tram/yosmw9jMet_aIRf2tn5J7uLqEjA>
Subject: Re: [tram] Stephen Farrell's Discuss on draft-ietf-tram-turn-third-party-authz-13: (with DISCUSS and COMMENT)
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: Tue, 21 Apr 2015 18:46:22 -0000

On 04/15/2015 12:09 PM, Tirumaleswar Reddy (tireddy) wrote:
>> -----Original Message-----
>> From: tram [mailto:tram-bounces@ietf.org] On Behalf Of Brandon Williams
>> Sent: Tuesday, April 14, 2015 6:07 PM
>>
>> I don't think OOB communication b/w the STUN and auth servers is a
>> solution to the problem of wanting to provide additional details in the
>> token. It defeats a large part of the purpose of moving to a token model in
>> the first place, which was to avoid the need for these two servers to have to
>> communicate directly with each other.
>
> The size of the metadata will determine if in-band or OOB is required.

The point is that OOB direct communication between the STUN and auth 
servers is not even an option for many 3rd party auth use cases. Also, 
if we don't provide a mechanism now then I think it may hurt interop to 
do so later, since servers that don't understand the extra information 
won't know how to handle it.

--Brandon

-- 
Brandon Williams; Chief Architect
Cloud Networking; Akamai Technologies Inc.