RFC 7065 on Traversal Using Relays around NAT (TURN) Uniform Resource Identifiers

rfc-editor@rfc-editor.org Sat, 23 November 2013 01:21 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D7AA91AE33F for <ietf-announce@ietfa.amsl.com>; Fri, 22 Nov 2013 17:21:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.427
X-Spam-Level:
X-Spam-Status: No, score=-2.427 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.525, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 ypRWH5LI6mzb for <ietf-announce@ietfa.amsl.com>; Fri, 22 Nov 2013 17:20:59 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:126c::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 5A1301AE2D4 for <ietf-announce@ietf.org>; Fri, 22 Nov 2013 17:20:59 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 1B70275E001; Fri, 22 Nov 2013 17:10:25 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7065 on Traversal Using Relays around NAT (TURN) Uniform Resource Identifiers
From: rfc-editor@rfc-editor.org
Message-Id: <20131123011025.1B70275E001@rfc-editor.org>
Date: Fri, 22 Nov 2013 17:10:25 -0800
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Nov 2013 01:21:01 -0000

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

        
        RFC 7065

        Title:      Traversal Using Relays around NAT 
                    (TURN) Uniform Resource Identifiers 
        Author:     M. Petit-Huguenin, S. Nandakumar,
                    G. Salgueiro, P. Jones
        Status:     Standards Track
        Stream:     IETF
        Date:       November 2013
        Mailbox:    petithug@acm.org, 
                    snandaku@cisco.com, 
                    gsalguei@cisco.com,
                    paulej@packetizer.com
        Pages:      9
        Characters: 16143
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-petithuguenin-behave-turn-uris-08.txt

        URL:        http://www.rfc-editor.org/rfc/rfc7065.txt

This document specifies the syntax of Uniform Resource Identifier
(URI) schemes for the Traversal Using Relays around NAT (TURN)
protocol.  It defines two URI schemes to provision the TURN
Resolution Mechanism (RFC 5928).

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 Internet
Official Protocol Standards (STD 1) 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
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/search/rfc_search.php
For downloading RFCs, see http://www.rfc-editor.org/rfc.html

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