[BEHAVE] FW: New Version Notification for draft-reddy-behave-turn-auth-02.txt

"Ram Mohan R (rmohanr)" <rmohanr@cisco.com> Tue, 18 June 2013 04:53 UTC

Return-Path: <rmohanr@cisco.com>
X-Original-To: behave@ietfa.amsl.com
Delivered-To: behave@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 900AB21F9DCA for <behave@ietfa.amsl.com>; Mon, 17 Jun 2013 21:53:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.3
X-Spam-Level:
X-Spam-Status: No, score=-9.3 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E8x0y8yB9nzx for <behave@ietfa.amsl.com>; Mon, 17 Jun 2013 21:53:34 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id 6C66921F9AAB for <behave@ietf.org>; Mon, 17 Jun 2013 21:53:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1677; q=dns/txt; s=iport; t=1371531214; x=1372740814; h=from:to:subject:date:message-id:in-reply-to:content-id: content-transfer-encoding:mime-version; bh=+9GIWlJPYDL/OeG6SpwBYdhF3xaEv8+4xnFyq2Tuugk=; b=dV+14JsnJCDXEstlfaVsFsp+l2KxvCqfitYcIRXSMbDkTqWfBHC5bJjV 4cGzc9OJVnHJdXIUeYqhNNdOV2XxbtBfocYcY+Rpyy41ZXNy82L7DRhMI DV+egDKwTnJ6dwZAdoV0oHc8nNTkW16OT3MBFaWjVuejmeSqDgfBI8MX5 E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ArAGAEDnv1GtJV2Z/2dsb2JhbABagwkxQwa/BX8WbQeCIwEBAQMBOj0HDQEIIhRCGwEGAwIEEwgBh38GBwWaBaBAjxQ4gn9hA5hqkBqDD4Io
X-IronPort-AV: E=Sophos;i="4.87,886,1363132800"; d="scan'208";a="224044278"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-8.cisco.com with ESMTP; 18 Jun 2013 04:53:33 +0000
Received: from xhc-aln-x12.cisco.com (xhc-aln-x12.cisco.com [173.36.12.86]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id r5I4rXs6026319 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <behave@ietf.org>; Tue, 18 Jun 2013 04:53:33 GMT
Received: from xmb-aln-x05.cisco.com ([169.254.11.242]) by xhc-aln-x12.cisco.com ([173.36.12.86]) with mapi id 14.02.0318.004; Mon, 17 Jun 2013 23:53:33 -0500
From: "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>
To: "behave@ietf.org" <behave@ietf.org>
Thread-Topic: New Version Notification for draft-reddy-behave-turn-auth-02.txt
Thread-Index: AQHOZ1hEvEcLpFOM4U2OtQirK7luDJk7oYQA
Date: Tue, 18 Jun 2013 04:53:32 +0000
Message-ID: <E92E67B176B8B64D8D3A8F5E44E9D8F41EC0FE43@xmb-aln-x05.cisco.com>
In-Reply-To: <20130612103314.16399.8755.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.3.2.130206
x-originating-ip: [72.163.212.105]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <D2EFA41B1ECBEA49A5E3F2317A50310D@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [BEHAVE] FW: New Version Notification for draft-reddy-behave-turn-auth-02.txt
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Tue, 18 Jun 2013 04:53:39 -0000

We have published the revision of this draft. This has changes to
following text of "Problems with STUN Authentication" section

<snip>
5.  Hosting multiple realms on a single IP address is challenging
       with TURN.  When a TURN server needs to send the REALM attribute
       in response to an unauthenticated request, it has no useful
       information for determining which realm it should send, except
       the source transport address of the TURN request.  Note this is a
       problem with multi-tenant scenarios only.  This is not a problem
       when deployed in Enterprise.


</snip>

Please review and provide any inputs/comments on this draft.

Authors

> On 12/06/13 4:03 PM, "internet-drafts@ietf.org"
><internet-drafts@ietf.org> wrote:

>
>A new version of I-D, draft-reddy-behave-turn-auth-02.txt
>has been successfully submitted by Tirumaleswar Reddy and posted to the
>IETF repository.
>
>Filename:	 draft-reddy-behave-turn-auth
>Revision:	 02
>Title:		 Problems with STUN Authentication for TURN
>Creation date:	 2013-06-12
>Group:		 Individual Submission
>Number of pages: 7
>URL:             
>http://www.ietf.org/internet-drafts/draft-reddy-behave-turn-auth-02.txt
>Status:          
>http://datatracker.ietf.org/doc/draft-reddy-behave-turn-auth
>Htmlized:        
>http://tools.ietf.org/html/draft-reddy-behave-turn-auth-02
>Diff:            
>http://www.ietf.org/rfcdiff?url2=draft-reddy-behave-turn-auth-02
>
>Abstract:
>   This document discusses some of the issues with STUN authentication
>   for TURN messages.
>
>                  
>        
>
>
>The IETF Secretariat
>
>