Subject: [pntaw] Fwd: [rfc-dist] RFC 7065 on Traversal Using Relays around NAT (TURN) Uniform Resource Identifiers

From: "Gonzalo Salgueiro (gsalguei)" <[email-masked]>
Date: Sat, 23 Nov 2013 02:40:18 +0000

[Excuse the cross-post, but I think this is relevant and/or has normative dependence.]

The TURN URI scheme has been published as an RFC.

Regards,

Gonzalo

Begin forwarded message:

From: <[email-masked]<mailto:[email-masked]>>
Date: November 22, 2013 at 8:10:25 PM EST
To: <[email-masked]<mailto:[email-masked]>>, <[email-masked]<mailto:[email-masked]>>
Cc: <[email-masked]<mailto:[email-masked]>>, <[email-masked]<mailto:[email-masked]>>
Subject: [rfc-dist] RFC 7065 on Traversal Using Relays around NAT (TURN) Uniform Resource Identifiers

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:    [email-masked]<mailto:[email-masked]>,
                   [email-masked]<mailto:[email-masked]>,
                   [email-masked]<mailto:[email-masked]>,
                   [email-masked]<mailto:[email-masked]>
       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 [email-masked]<mailto:[email-masked]>.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC

_______________________________________________
rfc-dist mailing list
[email-masked]<mailto:[email-masked]>
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org