[pntaw] Fwd: [rfc-dist] RFC 7064 on URI Scheme for the Session Traversal Utilities for NAT (STUN) Protocol

"Gonzalo Salgueiro (gsalguei)" <gsalguei@cisco.com> Fri, 22 November 2013 22:35 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 B8E1A1AE33E; Fri, 22 Nov 2013 14:35:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.026
X-Spam-Level:
X-Spam-Status: No, score=-10.026 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 hapHW19bnCj0; Fri, 22 Nov 2013 14:35:11 -0800 (PST)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) by ietfa.amsl.com (Postfix) with ESMTP id D592F1AE307; Fri, 22 Nov 2013 14:35:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2858; q=dns/txt; s=iport; t=1385159704; x=1386369304; h=from:to:subject:date:message-id:references:content-id: content-transfer-encoding:mime-version; bh=F0VBGrCMKpW2W8DV69dFuf9qzwbN80vFvS6OvXtuGbo=; b=F+MlqRQ2GsPPsqgEu0Ap5dmARQ9eIdXz47UJmQ99nD0RHiJN/N/3L4r8 WjoYRHrlokXyeg6ubCjHhLDeafGuVEOfr+xauGBlcJ82i1vtqWkXTAMof 1K+o/gnLIEi4URRVzbKTrM0MOblCGFpHFyhufL06/8HZHruUfz3gVQcdW g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ai0FAPjaj1KtJXG9/2dsb2JhbAA/GoMHOFO8FYEfFnSCJQEBAQMBAQEBNxQgEAsCARkDAQINEhAnCgEbAggCBAESCQsHAgSHWgYNNsB4F440VQuDGoESA5gUgTCLI4U/gWqBPoFxOQ
X-IronPort-AV: E=Sophos;i="4.93,754,1378857600"; d="scan'208";a="1632156"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by alln-iport-1.cisco.com with ESMTP; 22 Nov 2013 22:35:03 +0000
Received: from xhc-aln-x10.cisco.com (xhc-aln-x10.cisco.com [173.36.12.84]) by rcdn-core2-2.cisco.com (8.14.5/8.14.5) with ESMTP id rAMMZ3bZ000320 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 22 Nov 2013 22:35:03 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.192]) by xhc-aln-x10.cisco.com ([173.36.12.84]) with mapi id 14.03.0123.003; Fri, 22 Nov 2013 16:35:02 -0600
From: "Gonzalo Salgueiro (gsalguei)" <gsalguei@cisco.com>
To: "rtcweb@ietf.org" <rtcweb@ietf.org>, "public-webrtc@w3.org" <public-webrtc@w3.org>, "pntaw@ietf.org" <pntaw@ietf.org>, "tram@ietf.org" <tram@ietf.org>
Thread-Topic: [rfc-dist] RFC 7064 on URI Scheme for the Session Traversal Utilities for NAT (STUN) Protocol
Thread-Index: AQHO57KYv93N3ug+fESuZUXbnGRBSA==
Date: Fri, 22 Nov 2013 22:35:02 +0000
Message-ID: <09DDE5BA-2A28-4031-AB42-5083F3C6290A@cisco.com>
References: <20131122183155.C61FD75E001@rfc-editor.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.82.236.83]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <E1746E103230974C924D1F96EB09C73A@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [pntaw] Fwd: [rfc-dist] RFC 7064 on URI Scheme for the Session Traversal Utilities for NAT (STUN) Protocol
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: Fri, 22 Nov 2013 22:35:12 -0000

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

The STUN URI scheme has been published as RFC.


Cheers,

Gonzalo


Begin forwarded message:

> From: <rfc-editor@rfc-editor.org>;
> Subject: [rfc-dist] RFC 7064 on URI Scheme for the Session Traversal Utilities for NAT (STUN) Protocol
> Date: November 22, 2013 at 12:31:55 PM CST
> To: <ietf-announce@ietf.org>;, <rfc-dist@rfc-editor.org>;
> Cc: <drafts-update-ref@iana.org>;, <rfc-editor@rfc-editor.org>;
> 
> A new Request for Comments is now available in online RFC libraries.
> 
> 
>        RFC 7064
> 
>        Title:      URI Scheme for the Session 
>                    Traversal Utilities for NAT (STUN) Protocol 
>        Author:     S. Nandakumar, G. Salgueiro,
>                    P. Jones, M. Petit-Huguenin
>        Status:     Standards Track
>        Stream:     IETF
>        Date:       November 2013
>        Mailbox:    snandaku@cisco.com, 
>                    gsalguei@cisco.com, 
>                    paulej@packetizer.com,
>                    petithug@acm.org
>        Pages:      9
>        Characters: 15045
>        Updates/Obsoletes/SeeAlso:   None
> 
>        I-D Tag:    draft-nandakumar-rtcweb-stun-uri-08.txt
> 
>        URL:        http://www.rfc-editor.org/rfc/rfc7064.txt
> 
> This document specifies the syntax and semantics of the Uniform
> Resource Identifier (URI) scheme for the Session Traversal Utilities
> for NAT (STUN) protocol.
> 
> 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
> 
> 
> _______________________________________________
> rfc-dist mailing list
> rfc-dist@rfc-editor.org
> https://www.rfc-editor.org/mailman/listinfo/rfc-dist
> http://www.rfc-editor.org