IETF Logo Mail Archive

Re: [BEHAVE] WGLC: draft-ietf-behave-turn-tcp-04

Ari Keranen <ari.keranen@nomadiclab.com> Wed, 19 August 2009 10:22 UTC

Return-Path: <ari.keranen@nomadiclab.com>
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C99D53A6D4D for <behave@core3.amsl.com>; Wed, 19 Aug 2009 03:22:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.086
X-Spam-Level:
X-Spam-Status: No, score=-5.086 tagged_above=-999 required=5 tests=[AWL=1.163, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZO6TkexAu7Vd for <behave@core3.amsl.com>; Wed, 19 Aug 2009 03:22:56 -0700 (PDT)
Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62]) by core3.amsl.com (Postfix) with ESMTP id C0D513A6902 for <behave@ietf.org>; Wed, 19 Aug 2009 03:22:55 -0700 (PDT)
X-AuditID: c1b4fb3e-b7bf2ae000007ae0-4d-4a8bd283ea30
Received: from esealmw129.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw4.ericsson.se (Symantec Mail Security) with SMTP id 2B.8A.31456.382DB8A4; Wed, 19 Aug 2009 12:22:59 +0200 (CEST)
Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959); Wed, 19 Aug 2009 12:21:30 +0200
Received: from mail.lmf.ericsson.se ([131.160.11.50]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959); Wed, 19 Aug 2009 12:21:28 +0200
Received: from [127.0.0.1] (nomadiclab.lmf.ericsson.se [131.160.33.3]) by mail.lmf.ericsson.se (Postfix) with ESMTP id 43A562495; Wed, 19 Aug 2009 13:21:28 +0300 (EEST)
Message-ID: <4A8BD224.1070508@nomadiclab.com>
Date: Wed, 19 Aug 2009 13:21:24 +0300
From: Ari Keranen <ari.keranen@nomadiclab.com>
User-Agent: Thunderbird 2.0.0.22 (X11/20090608)
MIME-Version: 1.0
To: draft-ietf-behave-turn-tcp@tools.ietf.org
References: <0a9901ca10f2$93cdab60$5f7d150a@cisco.com>
In-Reply-To: <0a9901ca10f2$93cdab60$5f7d150a@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 19 Aug 2009 10:21:28.0691 (UTC) FILETIME=[D0747430:01CA20B6]
X-Brightmail-Tracker: AAAAAA==
Cc: behave@ietf.org
Subject: Re: [BEHAVE] WGLC: draft-ietf-behave-turn-tcp-04
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Aug 2009 10:22:56 -0000

Hi,

One technical issue in draft-ietf-behave-turn-tcp-04 caught my attention:

In section 4.5., "Sending and Receiving Data" is says:

    [...] Data on a data connection MUST NOT
    be interpreted as STUN messages.

I think this is too heavy restriction. What about if the peer wants to 
send some STUN messages on the path via the TURN server and would need 
the TURN client to parse them as STUN?

I would rather make this "SHOULD NOT" to be future proof. Or even 
removing the whole restriction should not do much harm, right?


Cheers,
Ari

v2.23.0 | Report a Bug | By Email