RFC 7675 on Session Traversal Utilities for NAT (STUN) Usage for Consent Freshness
rfc-editor@rfc-editor.org Mon, 19 October 2015 22:58 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 12E5C1B2E53; Mon, 19 Oct 2015 15:58:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.912
X-Spam-Level:
X-Spam-Status: No, score=-101.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 6glsQj2paUuN; Mon, 19 Oct 2015 15:58:03 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 7F65B1B2E52; Mon, 19 Oct 2015 15:57:56 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id BDC1A187E28; Mon, 19 Oct 2015 15:57:27 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7675 on Session Traversal Utilities for NAT (STUN) Usage for Consent Freshness
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20151019225727.BDC1A187E28@rfc-editor.org>
Date: Mon, 19 Oct 2015 15:57:27 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/TAbtfZl0BJU4wkrRCm-R9x1eMuk>
Cc: rtcweb@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: <https://mailarchive.ietf.org/arch/browse/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: Mon, 19 Oct 2015 22:58:09 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7675
Title: Session Traversal Utilities for NAT
(STUN) Usage for Consent Freshness
Author: M. Perumal, D. Wing,
R. Ravindranath, T. Reddy, M. Thomson
Status: Standards Track
Stream: IETF
Date: October 2015
Mailbox: muthu.arul@gmail.com,
dwing@cisco.com,
rmohanr@cisco.com,
tireddy@cisco.com,
martin.thomson@gmail.com
Pages: 10
Characters: 22346
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-rtcweb-stun-consent-freshness-16.txt
URL: https://www.rfc-editor.org/info/rfc7675
DOI: http://dx.doi.org/10.17487/RFC7675
To prevent WebRTC applications, such as browsers, from launching
attacks by sending traffic to unwilling victims, periodic consent to
send needs to be obtained from remote endpoints.
This document describes a consent mechanism using a new Session
Traversal Utilities for NAT (STUN) usage.
This document is a product of the Real-Time Communication in WEB-browsers Working Group of the IETF.
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 Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) 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
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