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> Wed, 22 April 2015 01:58 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 A64971B3042; Tue, 21 Apr 2015 18:58:36 -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 xvDH-ve93Lwc; Tue, 21 Apr 2015 18:58:35 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AEDE71B304D; Tue, 21 Apr 2015 18:58:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2397; q=dns/txt; s=iport; t=1429667906; x=1430877506; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=pOk2L5yY22EYOilDuxwj6JYBJG6NlRcDn2u3uA/VI4c=; b=eVBJzYzO7/L843+IoNAK15047KOmtr0lKQAXTO477HA/g490VgRD3++0 +4soMrU5CxvSJEwKoPEpKrmhzYvM2TfJTqqvXHcHt2k3Uuzn3PhizsvsN IdSCFJwGb02sJctkl0miFMQQZBso7t8vqLc9qOxkEUAEmAy+UOye2oS4f I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AWBQBE/zZV/4wNJK1bgwxSXAXFNII+hgQCgTlMAQEBAQEBfoQgAQEBBDo/DAQCAQgRBAEBAQoUBQQHIREUCQgBAQQBDQUIAYgOAxENxg8NhTcBAQEBAQEBAQEBAQEBAQEBAQEBAQEXizeCTYFlAQEFGjECBQaDEYEWBZEzhAGEWoJwOoMCigWGSiKCBAEZBBWBPG8BgQo5gQABAQE
X-IronPort-AV: E=Sophos;i="5.11,620,1422921600"; d="scan'208";a="5890389"
Received: from alln-core-7.cisco.com ([173.36.13.140]) by rcdn-iport-8.cisco.com with ESMTP; 22 Apr 2015 01:58:25 +0000
Received: from xhc-aln-x11.cisco.com (xhc-aln-x11.cisco.com [173.36.12.85]) by alln-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id t3M1wOsd011060 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 22 Apr 2015 01:58:24 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.220]) by xhc-aln-x11.cisco.com ([173.36.12.85]) with mapi id 14.03.0195.001; Tue, 21 Apr 2015 20:58:24 -0500
From: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
To: Brandon Williams <brandon.williams@akamai.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: AdB3YVGPL1OX25drRTSYceNRW1EowwFKngkAAAS+0+A=
Date: Wed, 22 Apr 2015 01:58:24 +0000
Message-ID: <913383AAA69FF945B8F946018B75898A41214674@xmb-rcd-x10.cisco.com>
References: <913383AAA69FF945B8F946018B75898A4120E0BD@xmb-rcd-x10.cisco.com> <55369856.7050203@akamai.com>
In-Reply-To: <55369856.7050203@akamai.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.65.50.120]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/tram/nJkC4avjdU6k51b1VbmEX3efRck>
Cc: "rlb@ipv.sx" <rlb@ipv.sx>, "tram-chairs@ietf.org" <tram-chairs@ietf.org>, "Stephen Farrell (stephen.farrell@cs.tcd.ie)" <stephen.farrell@cs.tcd.ie>, "tram@ietf.org" <tram@ietf.org>, "Salz, Rich" <rsalz@akamai.com>
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: Wed, 22 Apr 2015 01:58:36 -0000

> -----Original Message-----
> From: Brandon Williams [mailto:brandon.williams@akamai.com]
> Sent: Wednesday, April 22, 2015 12:05 AM
> To: Tirumaleswar Reddy (tireddy); Martin Thomson
> Cc: tram-chairs@ietf.org; tram@ietf.org; 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 04/15/2015 05:47 AM, Tirumaleswar Reddy (tireddy) wrote:
> >> -----Original Message-----
> >> From: Martin Thomson [mailto:martin.thomson@gmail.com]
> >> Sent: Monday, April 13, 2015 11:47 PM
> >> To: Tirumaleswar Reddy (tireddy)
> >> Cc: Brandon Williams; rlb@ipv.sx; Salz, Rich; Stephen Farrell
> >> (stephen.farrell@cs.tcd.ie); tram@ietf.org; tram-chairs@ietf.org
> >> Subject: Re: [tram] Stephen Farrell's Discuss on draft-ietf-tram-turn-third-
> >> party-authz-13: (with DISCUSS and COMMENT)
> >>
> >>
> >> It does need to deal with algorithm agility and it currently does not.
> >
> > It supports algorithm agility. Please refer to
> http://tools.ietf.org/html/draft-ietf-tram-turn-third-party-authz-
> 13#appendix-B  for the interaction b/w the client and authorization server
> where the client signals the algorithms it supports and server selects an
> HMAC algorithm from the list of algorithms the  client provided and
> determines length of the mac_key based on the selected HMAC algorithm.
> >
> 
> I'm not sure that key length alone is enough to facilitate the current
> hash agility plan, which is to require a client to send both SHA256 and
> SHA1 HMACs. IMO, either this draft should require 256 bit keys minimum
> and describe what to do to generate a SHA1 key (probably run SHA1 on the
> SHA256 key) or the stunbis editors should commit to providing this
> information in stunbis. I just want to be certain that we will be
> telling implementors what to do somewhere.

HKDF https://tools.ietf.org/html/rfc5869 can be used to derive the key for SHA1 from 256-bit key but as per the last mail thread http://www.ietf.org/mail-archive/web/tram/current/msg01525.html, I did not see any consensus if TURN client must include MI calculated using both SHA1 and SHA2. 

-Tiru

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

v2.23.0 | Report a Bug | By Email