Re: [tram] I-D Action: draft-ietf-tram-turnbis-19.txt

"Ram Mohan R (rmohanr)" <rmohanr@cisco.com> Thu, 14 June 2018 05:52 UTC

Return-Path: <rmohanr@cisco.com>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 559DB1310A8 for <tram@ietfa.amsl.com>; Wed, 13 Jun 2018 22:52:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 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_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 c7Z1f73qhUo0 for <tram@ietfa.amsl.com>; Wed, 13 Jun 2018 22:52:17 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F37F8130E85 for <tram@ietf.org>; Wed, 13 Jun 2018 22:52:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6820; q=dns/txt; s=iport; t=1528955536; x=1530165136; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=XglPR/j1KRX5u5LzpuNG30CO82FRZ300QrNghXhWlTs=; b=IW5Y6A7bV/uTDwKZmzkyaJJgAemwwlE/QcBykyfQd8QUp3R6WBLRIxfE uZObGCoyV6w85aUn9SYWZdXVFP8Swat3s1NhtxFyIBrVqSO0xF7GXMZ8s gqpPm4IHHHNDjE1bNL/l+XkmFn4Ew3sX2GThQth9xHGVJBY9lACCmNpUI 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DAAAD8ASJb/4YNJK1cGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAYNIYn8oCoNviASMaIF/lGsUgWQLGAuESQIXgiQhNBgBAgE?= =?us-ascii?q?BAQEBAQJtHAyFKAEBAQQBASEROgsMBAIBCBEDAQEBAwIjAwICAiULFAEICAI?= =?us-ascii?q?EAQ0FgyICgX8PqiqBIIIciEaBaIELh0CCE4EPJIJogxEBAQIBARaBCQEJARI?= =?us-ascii?q?BHwczgkcxgiQCjDmMUwkChXWJCIE/QYM+h3iKDYcNAhETAYEkHThhcXAVGiE?= =?us-ascii?q?qAYIYCYsIhT5vAY5RgR+BGgEB?=
X-IronPort-AV: E=Sophos;i="5.51,222,1526342400"; d="scan'208";a="129667653"
Received: from alln-core-12.cisco.com ([173.36.13.134]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 14 Jun 2018 05:52:16 +0000
Received: from XCH-RTP-016.cisco.com (xch-rtp-016.cisco.com [64.101.220.156]) by alln-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id w5E5qFfs004627 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 14 Jun 2018 05:52:15 GMT
Received: from xch-rtp-017.cisco.com (64.101.220.157) by XCH-RTP-016.cisco.com (64.101.220.156) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Thu, 14 Jun 2018 01:52:15 -0400
Received: from xch-rtp-017.cisco.com ([64.101.220.157]) by XCH-RTP-017.cisco.com ([64.101.220.157]) with mapi id 15.00.1320.000; Thu, 14 Jun 2018 01:52:15 -0400
From: "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>
To: "Konda, Tirumaleswar Reddy" <TirumaleswarReddy_Konda@McAfee.com>, "Justin Uberti" <juberti=40google.com@dmarc.ietf.org>
CC: "tram@ietf.org" <tram@ietf.org>
Thread-Topic: [tram] I-D Action: draft-ietf-tram-turnbis-19.txt
Thread-Index: AQHUA6PYn295Bq8Zm0CePE6OhHY+WA==
Date: Thu, 14 Jun 2018 05:52:15 +0000
Message-ID: <7F95390B-F7BA-41C1-97C9-AE1E7FD37F2F@cisco.com>
References: <152809326560.20924.1993421118096117008@ietfa.amsl.com> <BN6PR16MB14259FA70767BA31FB3E35EBEA670@BN6PR16MB1425.namprd16.prod.outlook.com> <CAOJ7v-0V-riJU8Cv0Jw0vrGbBYfMa8giUnyDx2zbs_UiVdrMPQ@mail.gmail.com> <BN6PR16MB1425FBFFA3B03170DDC2B4E9EA7F0@BN6PR16MB1425.namprd16.prod.outlook.com>
In-Reply-To: <BN6PR16MB1425FBFFA3B03170DDC2B4E9EA7F0@BN6PR16MB1425.namprd16.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.b.0.180311
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.196.93.103]
Content-Type: text/plain; charset="utf-8"
Content-ID: <4F0006B2B071294A903D1ED5D809FE82@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/A3b-nUhizZcS_ToGXFd4S4dZVP8>
Subject: Re: [tram] I-D Action: draft-ietf-tram-turnbis-19.txt
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.26
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 14 Jun 2018 05:52:20 -0000

Hi Tiru,

I reviewed the section on handling inbound STUN packets on relay
address before permissions are created  (based on configuration knob) and it looks fine to me.

Regards,
Ram

-----Original Message-----
From: tram <tram-bounces@ietf.org> on behalf of "Konda, Tirumaleswar Reddy" <TirumaleswarReddy_Konda@McAfee.com>
Date: Tuesday, 12 June 2018 at 10:01 PM
To: Justin Uberti <juberti=40google.com@dmarc.ietf.org>
Cc: "tram@ietf.org" <tram@ietf.org>
Subject: Re: [tram] I-D Action: draft-ietf-tram-turnbis-19.txt

    Thanks Justin. Fixed in my local copy.
     
    -Tiru
     
    From: tram [mailto:tram-bounces@ietf.org] On Behalf Of
    Justin Uberti
    Sent: Tuesday, June 12, 2018 6:45 AM
    To: Konda, Tirumaleswar Reddy <TirumaleswarReddy_Konda@McAfee.com>
    Cc: tram@ietf.org
    Subject: Re: [tram] I-D Action: draft-ietf-tram-turnbis-19.txt
    
    
     
    CAUTION: External email. Do not click links or open
     attachments unless you recognize the sender and know the content is safe.
    ________________________________________
    
    
    The revised text in Section 2.3 LGTM.
     
    
    I noticed the acknowledgements section (Section 23) refers to SSODA, but this name doesn't appear elsewhere in the document. Perhaps it should say "the ADDITIONAL-ADDRESS-FAMILY mechanism"?
    
    
     
    On Sun, Jun 3, 2018 at 11:24 PM Konda, Tirumaleswar Reddy <TirumaleswarReddy_Konda@mcafee.com> wrote:
    
    
    This revision addresses comments from Justin.
    
    -Tiru
    
    > -----Original Message-----
    > From: tram [mailto:tram-bounces@ietf.org] On Behalf Of internet-
    > drafts@ietf.org
    > Sent: Monday, June 4, 2018 11:51 AM
    > To: i-d-announce@ietf.org
    > Cc: tram@ietf.org
    > Subject: [tram] I-D Action: draft-ietf-tram-turnbis-19.txt
    > 
    > 
    > 
    > A New Internet-Draft is available from the on-line Internet-Drafts directories.
    > This draft is a work item of the TURN Revised and Modernized WG of the IETF.
    > 
    >         Title           : Traversal Using Relays around NAT (TURN): Relay Extensions
    > to Session Traversal Utilities for NAT (STUN)
    >         Authors         : Tirumaleswar Reddy
    >                           Alan Johnston
    >                           Philip Matthews
    >                           Jonathan Rosenberg
    >       Filename        : draft-ietf-tram-turnbis-19.txt
    >       Pages           : 84
    >       Date            : 2018-06-03
    > 
    > Abstract:
    >    If a host is located behind a NAT, then in certain situations it can
    >    be impossible for that host to communicate directly with other hosts
    >    (peers).  In these situations, it is necessary for the host to use
    >    the services of an intermediate node that acts as a communication
    >    relay.  This specification defines a protocol, called TURN (Traversal
    >    Using Relays around NAT), that allows the host to control the
    >    operation of the relay and to exchange packets with its peers using
    >    the relay.  TURN differs from some other relay control protocols in
    >    that it allows a client to communicate with multiple peers using a
    >    single relay address.
    > 
    >    The TURN protocol was designed to be used as part of the ICE
    >    (Interactive Connectivity Establishment) approach to NAT traversal,
    >    though it also can be used without ICE.
    > 
    >    This document obsoletes RFC 5766 and RFC 6156.
    > 
    > 
    > The IETF datatracker status page for this draft is:
    > 
    https://datatracker.ietf.org/doc/draft-ietf-tram-turnbis/ <https://datatracker.ietf.org/doc/draft-ietf-tram-turnbis/>
    > 
    > There are also htmlized versions available at:
    > 
    https://tools.ietf.org/html/draft-ietf-tram-turnbis-19 <https://tools.ietf.org/html/draft-ietf-tram-turnbis-19>
    > 
    https://datatracker.ietf.org/doc/html/draft-ietf-tram-turnbis-19 <https://datatracker.ietf.org/doc/html/draft-ietf-tram-turnbis-19>
    > 
    > A diff from the previous version is available at:
    > 
    https://www.ietf.org/rfcdiff?url2=draft-ietf-tram-turnbis-19 <https://www.ietf.org/rfcdiff?url2=draft-ietf-tram-turnbis-19>
    > 
    > 
    > Please note that it may take a couple of minutes from the time of submission
    > until the htmlized version and diff are available at 
    tools.ietf.org <http://tools.ietf.org>.
    > 
    > Internet-Drafts are also available by anonymous FTP at:
    > ftp://ftp.ietf.org/internet-drafts/
    > 
    > _______________________________________________
    > tram mailing list
    > tram@ietf.org
    > https://www.ietf.org/mailman/listinfo/tram
    
    _______________________________________________
    tram mailing list
    tram@ietf.org
    https://www.ietf.org/mailman/listinfo/tram