[AVTCORE] RFC 7022 on Guidelines for Choosing RTP Control Protocol (RTCP) Canonical Names (CNAMEs)
rfc-editor@rfc-editor.org Tue, 03 September 2013 22:41 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 750B211E8151; Tue, 3 Sep 2013 15:41:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.92
X-Spam-Level:
X-Spam-Status: No, score=-101.92 tagged_above=-999 required=5 tests=[AWL=0.080, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PS7TA-sBDuyH; Tue, 3 Sep 2013 15:41:06 -0700 (PDT)
Received: from rfc-editor.org (unknown [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id E49AC11E814F; Tue, 3 Sep 2013 15:41:05 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id C22FBB1E00A; Tue, 3 Sep 2013 15:35:31 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20130903223531.C22FBB1E00A@rfc-editor.org>
Date: Tue, 03 Sep 2013 15:35:31 -0700
Cc: drafts-update-ref@iana.org, avt@ietf.org, rfc-editor@rfc-editor.org
Subject: [AVTCORE] RFC 7022 on Guidelines for Choosing RTP Control Protocol (RTCP) Canonical Names (CNAMEs)
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Sep 2013 22:41:06 -0000
A new Request for Comments is now available in online RFC libraries. RFC 7022 Title: Guidelines for Choosing RTP Control Protocol (RTCP) Canonical Names (CNAMEs) Author: A. Begen, C. Perkins, D. Wing, E. Rescorla Status: Standards Track Stream: IETF Date: September 2013 Mailbox: abegen@cisco.com, csp@csperkins.org, dwing@cisco.com, ekr@rtfm.com Pages: 10 Characters: 21717 Obsoletes: RFC 6222 Updates: RFC 3550 I-D Tag: draft-ietf-avtcore-6222bis-06.txt URL: http://www.rfc-editor.org/rfc/rfc7022.txt The RTP Control Protocol (RTCP) Canonical Name (CNAME) is a persistent transport-level identifier for an RTP endpoint. While the Synchronization Source (SSRC) identifier of an RTP endpoint may change if a collision is detected or when the RTP application is restarted, its RTCP CNAME is meant to stay unchanged, so that RTP endpoints can be uniquely identified and associated with their RTP media streams. For proper functionality, RTCP CNAMEs should be unique within the participants of an RTP session. However, the existing guidelines for choosing the RTCP CNAME provided in the RTP standard (RFC 3550) are insufficient to achieve this uniqueness. RFC 6222 was published to update those guidelines to allow endpoints to choose unique RTCP CNAMEs. Unfortunately, later investigations showed that some parts of the new algorithms were unnecessarily complicated and/or ineffective. This document addresses these concerns and replaces RFC 6222. This document is a product of the Audio/Video Transport Core Maintenance 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 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