RFC 8828 on WebRTC IP Address Handling Requirements

rfc-editor@rfc-editor.org Mon, 18 January 2021 23: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 (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 456633A0CD4; Mon, 18 Jan 2021 15:28:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 snbG9iwnIZJd; Mon, 18 Jan 2021 15:28:04 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DDA423A0A1D; Mon, 18 Jan 2021 15:28:03 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 9133CF40779; Mon, 18 Jan 2021 15:27:48 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?UkZDIDg4Mjggb24gV2ViUlRDIElQIEFkZHJlc3MgSGFuZGxpbmcgUmVxdWlyZW1lbnRz?=
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, rtcweb@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20210118232748.9133CF40779@rfc-editor.org>
Date: Mon, 18 Jan 2021 15:27:48 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/y1emY7-dMuUr-A9TtHVqmHVILmQ>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
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, 18 Jan 2021 23:28:05 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8828

        Title:      WebRTC IP Address Handling Requirements 
        Author:     J. Uberti,
                    G. Shieh
        Status:     Standards Track
        Stream:     IETF
        Date:       January 2021
        Mailbox:    justin@uberti.name,
                    guoweis@gmail.com
        Pages:      9
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-rtcweb-ip-handling-12.txt

        URL:        https://www.rfc-editor.org/info/rfc8828

        DOI:        10.17487/RFC8828

This document provides information and requirements for how IP
addresses should be handled by Web Real-Time Communication (WebRTC)
implementations.

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/retrieve/bulk

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