IETF Logo Mail Archive

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

"Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com> Tue, 14 April 2015 06:02 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 72ECA1B33FE; Mon, 13 Apr 2015 23:02:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, 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 DqCGMOlvXVO7; Mon, 13 Apr 2015 23:02:37 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 06F291B33FB; Mon, 13 Apr 2015 23:02:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2258; q=dns/txt; s=iport; t=1428991357; x=1430200957; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=gVrEF8tgI9yBNeLg7Pt28WA/qohyOZYLJVyoiifNTA4=; b=Dc5jxeOKrIFxQbkJVPHDqSakayZ3kOHLqUjvgLn8FVLCpeodzSzoYgRS gMGXXPOAr+De86qIXV7fpZ/XcRS4QQJtWA/bkdx4uckNSqR9Fa+JizdQU tBUkcifQ/fcVjAGMtfHLhipNJU1RcZ/X1yQ3bEQ0e7LKeEBnedhADgqX/ U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ARBQA5rCxV/4gNJK1cgwxSXAWDEMFAgj2GAQIcgSpMAQEBAQEBfoQfAQEBBCMRMxIMBAIBCA4DBAEBAQICBhkEAwICAh8RFAEICAIEAQ0FCIgOAxENth+QTw2FPwEBAQEBAQEBAQEBAQEBAQEBAQEBARMEgSGKCoJIgWkaFhsHBoJiL4EWAQSRDIN5hEmPf4Y6IoIzgTxvgUR/AQEB
X-IronPort-AV: E=Sophos;i="5.11,574,1422921600"; d="scan'208";a="411613691"
Received: from alln-core-3.cisco.com ([173.36.13.136]) by rcdn-iport-3.cisco.com with ESMTP; 14 Apr 2015 06:02:37 +0000
Received: from xhc-aln-x05.cisco.com (xhc-aln-x05.cisco.com [173.36.12.79]) by alln-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id t3E62asC017997 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 14 Apr 2015 06:02:36 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.220]) by xhc-aln-x05.cisco.com ([173.36.12.79]) with mapi id 14.03.0195.001; Tue, 14 Apr 2015 01:02:35 -0500
From: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
To: Oleg Moskalenko <mom040267@gmail.com>, Martin Thomson <martin.thomson@gmail.com>
Thread-Topic: [tram] Stephen Farrell's Discuss on draft-ietf-tram-turn-third-party-authz-13: (with DISCUSS and COMMENT)
Thread-Index: AQHQc8XlvscJvCv8tEiY7AOvXxiXD51G/ZcAgAALUcCABI95gIAAuwQA//+zguA=
Date: Tue, 14 Apr 2015 06:02:34 +0000
Message-ID: <913383AAA69FF945B8F946018B75898A4120D628@xmb-rcd-x10.cisco.com>
References: <20150410193813.20376.40907.idtracker@ietfa.amsl.com> <55282B4E.4000409@akamai.com> <913383AAA69FF945B8F946018B75898A411FFC5F@xmb-rcd-x10.cisco.com> <CABkgnnUyHTd83LWM0Lp0xOJnVp3Gt6KvrbuGkraejP7kwEJf7w@mail.gmail.com> <CALDtMrLO-kqM4LTOgKJq90swE52k0draQ110t5Q8GVfUwPFpUQ@mail.gmail.com>
In-Reply-To: <CALDtMrLO-kqM4LTOgKJq90swE52k0draQ110t5Q8GVfUwPFpUQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.65.68.121]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/tram/J-z7-sj0hkW1n0nR32JSnDnZvXg>
Cc: "tram-chairs@ietf.org" <tram-chairs@ietf.org>, "tram@ietf.org" <tram@ietf.org>, Brandon Williams <brandon.williams@akamai.com>, "rlb@ipv.sx" <rlb@ipv.sx>, "Salz, Rich" <rsalz@akamai.com>, "Stephen Farrell (stephen.farrell@cs.tcd.ie)" <stephen.farrell@cs.tcd.ie>
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, 14 Apr 2015 06:02:38 -0000

> -----Original Message-----
> From: Oleg Moskalenko [mailto:mom040267@gmail.com]
> Sent: Tuesday, April 14, 2015 10:57 AM
> To: Martin Thomson
> Cc: Tirumaleswar Reddy (tireddy); tram-chairs@ietf.org; tram@ietf.org;
> Brandon Williams; rlb@ipv.sx; Salz, Rich; Stephen Farrell
> (stephen.farrell@cs.tcd.ie)
> Subject: Re: [tram] Stephen Farrell's Discuss on draft-ietf-tram-turn-third-
> party-authz-13: (with DISCUSS and COMMENT)
> 
> On Mon, Apr 13, 2015 at 11:17 AM, Martin Thomson
> <martin.thomson@gmail.com> wrote:
> >
> > Section 4 doesn't permit any additional information to be carried in
> > the token.  Therefore, the STUN/TURN server is unable to apply any
> > additional policies that the authorization server might impose, such
> > as limits on the length of the session, the number of ports allocated,
> > or the bandwidth that is allocated.  (Or whatever we might later
> > conceive of.)
> 
> I believe that extra token information is a very very bad idea - it kills the
> whole interoperability thing in the draft. If we are adding "extra"
> information to the token, we can as well just kill the draft and tell the STUN
> server developers "do whatever you want, secure the stuff somehow, we do
> not care".

It was discussed in the WG and decision was not to carry any extra token information so as to keep the token size small. In future an out-of-band communication mechanism b/w STUN and authorization server to exchange the token related metadata can be defined similar to the OAuth 2.0 Token Introspection method defined in https://tools.ietf.org/html/draft-ietf-oauth-introspection-07. 

-Tiru

v2.23.0 | Report a Bug | By Email