[pntaw] Fwd: [rfc-dist] RFC 7065 on Traversal Using Relays around NAT (TURN) Uniform Resource Identifiers
"Gonzalo Salgueiro (gsalguei)" <gsalguei@cisco.com> Sat, 23 November 2013 02:40 UTC
Return-Path: <gsalguei@cisco.com>
X-Original-To: pntaw@ietfa.amsl.com
Delivered-To: pntaw@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BCF11A1F72; Fri, 22 Nov 2013 18:40:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.025
X-Spam-Level:
X-Spam-Status: No, score=-15.025 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.525, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 zErRyc7NxCzx; Fri, 22 Nov 2013 18:40:31 -0800 (PST)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by ietfa.amsl.com (Postfix) with ESMTP id 89D291AC3DD; Fri, 22 Nov 2013 18:40:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10366; q=dns/txt; s=iport; t=1385174424; x=1386384024; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=kfq1cGrEG1y7VQ6/pQ73aMNazONfXPuSqSMoZL/Ycz4=; b=I8rMe4tSSfyjdTSYdz53bbtLIe6sb7SkmCzR370RAaiKrAwddeWniWEC bG/gdbcCJwttXkoufBLkvp6rIjjOWVonz+Cs2i1yDItVXbI9MtVPG+o5P 1PJR6UVw61oLoowvtJs/HlOF8Q1M74EhKzPjL7qBIAQFeQ3ZDuxgO5R/c o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhwGAFQVkFKtJXHB/2dsb2JhbAA/GoMHOLQdiEyBIBZ0giUBAQEEAQEBSyAbAgEZAwECDRsHJwoBFAcCCAIEARIJCwcCBIdgDTbAUReONEINCgEGgxqBEwOYFIEwiyOFP4FqgT6BcQ
X-IronPort-AV: E=Sophos; i="4.93,756,1378857600"; d="scan'208,217"; a="286966847"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-2.cisco.com with ESMTP; 23 Nov 2013 02:40:19 +0000
Received: from xhc-rcd-x14.cisco.com (xhc-rcd-x14.cisco.com [173.37.183.88]) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id rAN2eJOT027615 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 23 Nov 2013 02:40:19 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.192]) by xhc-rcd-x14.cisco.com ([173.37.183.88]) with mapi id 14.03.0123.003; Fri, 22 Nov 2013 20:40:18 -0600
From: "Gonzalo Salgueiro (gsalguei)" <gsalguei@cisco.com>
To: "rtcweb@ietf.org" <rtcweb@ietf.org>, "pntaw@ietf.org" <pntaw@ietf.org>, "public-webrtc@w3.org" <public-webrtc@w3.org>, "tram@ietf.org" <tram@ietf.org>
Thread-Topic: [rfc-dist] RFC 7065 on Traversal Using Relays around NAT (TURN) Uniform Resource Identifiers
Thread-Index: AQHO5+pEXQhXjFTbG0WqzojKCtYKrZoyGt30
Date: Sat, 23 Nov 2013 02:40:18 +0000
Message-ID: <C0E6C8D2-EDC6-4CCC-98C5-6A942D1239FB@cisco.com>
References: <20131123011025.1B70275E001@rfc-editor.org>
In-Reply-To: <20131123011025.1B70275E001@rfc-editor.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: multipart/alternative; boundary="_000_C0E6C8D2EDC64CCC98C56A942D1239FBciscocom_"
MIME-Version: 1.0
Subject: [pntaw] Fwd: [rfc-dist] RFC 7065 on Traversal Using Relays around NAT (TURN) Uniform Resource Identifiers
X-BeenThere: pntaw@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion list for practices related to proxies, NATs, TURN, and WebRTC" <pntaw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pntaw>, <mailto:pntaw-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pntaw/>
List-Post: <mailto:pntaw@ietf.org>
List-Help: <mailto:pntaw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pntaw>, <mailto:pntaw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Nov 2013 02:40:34 -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: <rfc-editor@rfc-editor.org<mailto:rfc-editor@rfc-editor.org>>
Date: November 22, 2013 at 8:10:25 PM EST
To: <ietf-announce@ietf.org<mailto:ietf-announce@ietf.org>>, <rfc-dist@rfc-editor.org<mailto:rfc-dist@rfc-editor.org>>
Cc: <drafts-update-ref@iana.org<mailto:drafts-update-ref@iana.org>>, <rfc-editor@rfc-editor.org<mailto:rfc-editor@rfc-editor.org>>
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: petithug@acm.org<mailto:petithug@acm.org>,
snandaku@cisco.com<mailto:snandaku@cisco.com>,
gsalguei@cisco.com<mailto:gsalguei@cisco.com>,
paulej@packetizer.com<mailto: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<mailto: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
_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org<mailto:rfc-dist@rfc-editor.org>
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org
- [pntaw] Fwd: [rfc-dist] RFC 7065 on Traversal Usi… Gonzalo Salgueiro (gsalguei)