RFC 7443 on Application-Layer Protocol Negotiation (ALPN) Labels for Session Traversal Utilities for NAT (STUN) Usages
rfc-editor@rfc-editor.org Fri, 23 January 2015 04:28 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 E066A1A8F4C; Thu, 22 Jan 2015 20:28:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.912
X-Spam-Level:
X-Spam-Status: No, score=-106.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] 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 yl9C47bPSp_s; Thu, 22 Jan 2015 20:28:53 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 5471E1A1A6C; Thu, 22 Jan 2015 20:28:50 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id AA17C187E27; Thu, 22 Jan 2015 20:28:25 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7443 on Application-Layer Protocol Negotiation (ALPN) Labels for Session Traversal Utilities for NAT (STUN) Usages
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150123042825.AA17C187E27@rfc-editor.org>
Date: Thu, 22 Jan 2015 20:28:25 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/dAGPz2m8r_gDeV_DkUi214E2rH8>
Cc: drafts-update-ref@iana.org, tram@ietf.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: Fri, 23 Jan 2015 04:28:56 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7443
Title: Application-Layer Protocol Negotiation (ALPN) Labels
for Session Traversal Utilities for NAT
(STUN) Usages
Author: P. Patil, T. Reddy,
G. Salgueiro, M. Petit-Huguenin
Status: Informational
Stream: IETF
Date: January 2015
Mailbox: praspati@cisco.com,
tireddy@cisco.com,
gsalguei@cisco.com,
marc@petit-huguenin.org
Pages: 5
Characters: 9145
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-tram-alpn-08.txt
URL: https://www.rfc-editor.org/info/rfc7443
Application-Layer Protocol Negotiation (ALPN) labels for Session
Traversal Utilities for NAT (STUN) usages, such as Traversal Using
Relays around NAT (TURN) and NAT discovery, are defined in this
document to allow an application layer to negotiate STUN usages
within the Transport Layer Security (TLS) connection. ALPN protocol
identifiers defined in this document apply to both TLS and Datagram
Transport Layer Security (DTLS).
This document is a product of the TURN Revised and Modernized Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://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