[tram] RFC 8656 on Traversal Using Relays around NAT (TURN): Relay Extensions to Session Traversal Utilities for NAT (STUN)

rfc-editor@rfc-editor.org Sat, 22 February 2020 06:31 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: tram@ietfa.amsl.com
Delivered-To: tram@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id ED74212080F; Fri, 21 Feb 2020 22:31:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id b9WbbV0Zmgh2; Fri, 21 Feb 2020 22:31:05 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9F56012012C; Fri, 21 Feb 2020 22:31:05 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 79FD2F4071A; Fri, 21 Feb 2020 22:30:58 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, tram@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20200222063058.79FD2F4071A@rfc-editor.org>
Date: Fri, 21 Feb 2020 22:30:58 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/IcqMrS5tPsbUaGQGyZORuvKURaE>
Subject: [tram] =?utf-8?q?RFC_8656_on_Traversal_Using_Relays_around_NAT_?= =?utf-8?q?=28TURN=29=3A_Relay_Extensions_to_Session_Traversal_Utilities_f?= =?utf-8?q?or_NAT_=28STUN=29?=
X-BeenThere: tram@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 22 Feb 2020 06:31:18 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 8656

        Title:      Traversal Using Relays around NAT (TURN):
                    Relay Extensions to Session Traversal 
                    Utilities for NAT (STUN) 
        Author:     T. Reddy, Ed.,
                    A. Johnston, Ed.,
                    P. Matthews,
                    J. Rosenberg
        Status:     Standards Track
        Stream:     IETF
        Date:       February 2020
        Mailbox:    kondtir@gmail.com, 
        Pages:      79
        Obsoletes:  RFC 5766, RFC 6156

        I-D Tag:    draft-ietf-tram-turnbis-29.txt

        URL:        https://www.rfc-editor.org/info/rfc8656

        DOI:        10.17487/RFC8656

If a host is located behind a NAT, it can be impossible for that host
to communicate directly with other hosts (peers) in certain
situations. 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 "Traversal Using
Relays around NAT" (TURN), that allows the host to control the
operation of the relay and to exchange packets with its peers using
the relay. TURN differs from 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 Interactive
Connectivity Establishment (ICE) approach to NAT traversal, though it
can also be used without ICE.

This document obsoletes RFCs 5766 and 6156.

This document is a product of the TURN Revised and Modernized Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC