[tram] RFC 8489 on 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 8A2F7120123; Fri, 21 Feb 2020 22:31:05 -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 cYQGaC_mrhCi; Fri, 21 Feb 2020 22:31:00 -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 6FB2012012C; Fri, 21 Feb 2020 22:31:00 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 45203F406DA; Fri, 21 Feb 2020 22:30:53 -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: <20200222063053.45203F406DA@rfc-editor.org>
Date: Fri, 21 Feb 2020 22:30:53 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tram/pRVeyGlb0tZt73wViSHW-f0AUo0>
Subject: [tram] =?utf-8?q?RFC_8489_on_Session_Traversal_Utilities_for_NAT?= =?utf-8?q?_=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:06 -0000

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

        RFC 8489

        Title:      Session Traversal Utilities for NAT (STUN) 
        Author:     M. Petit-Huguenin,
                    G. Salgueiro,
                    J. Rosenberg, 
                    D. Wing,
                    R. Mahy, 
                    P. Matthews
        Status:     Standards Track
        Stream:     IETF
        Date:       February 2020
        Mailbox:    marc@petit-huguenin.org, 
        Pages:      67
        Obsoletes:  RFC 5389

        I-D Tag:    draft-ietf-tram-stunbis-21.txt

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

        DOI:        10.17487/RFC8489

Session Traversal Utilities for NAT (STUN) is a protocol that serves
as a tool for other protocols in dealing with NAT traversal.  It can
be used by an endpoint to determine the IP address and port allocated
to it by a NAT.  It can also be used to check connectivity between
two endpoints and as a keep-alive protocol to maintain NAT bindings.
STUN works with many existing NATs and does not require any special
behavior from them.

STUN is not a NAT traversal solution by itself.  Rather, it is a tool
to be used in the context of a NAT traversal solution.

This document obsoletes RFC 5389.

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.

[Note: This RFC is intentionally not published in the v3 format.]  

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