[AVTCORE] RFC 6222 on Guidelines for Choosing RTP Control Protocol (RTCP) Canonical Names (CNAMEs)
rfc-editor@rfc-editor.org Thu, 14 April 2011 18:26 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: avt@ietfc.amsl.com
Delivered-To: avt@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id 6154DE08E7; Thu, 14 Apr 2011 11:26:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.065
X-Spam-Level:
X-Spam-Status: No, score=-102.065 tagged_above=-999 required=5 tests=[AWL=-0.065, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hbI0aADQSlDO; Thu, 14 Apr 2011 11:26:25 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by ietfc.amsl.com (Postfix) with ESMTP id ED7FAE08E4; Thu, 14 Apr 2011 11:26:24 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 7A763E0781; Thu, 14 Apr 2011 11:26:24 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20110414182624.7A763E0781@rfc-editor.org>
Date: Thu, 14 Apr 2011 11:26:24 -0700
Cc: avt@ietf.org, rfc-editor@rfc-editor.org
Subject: [AVTCORE] RFC 6222 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: Thu, 14 Apr 2011 18:26:26 -0000
A new Request for Comments is now available in online RFC libraries. RFC 6222 Title: Guidelines for Choosing RTP Control Protocol (RTCP) Canonical Names (CNAMEs) Author: A. Begen, C. Perkins, D. Wing Status: Standards Track Stream: IETF Date: April 2011 Mailbox: abegen@cisco.com, csp@csperkins.org, dwing@cisco.com Pages: 9 Characters: 20393 Updates: RFC3550 I-D Tag: draft-ietf-avt-rtp-cnames-05.txt URL: http://www.rfc-editor.org/rfc/rfc6222.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 are insufficient to achieve this uniqueness. This memo updates those guidelines to allow endpoints to choose unique RTCP CNAMEs. [STANDARDS-TRACK] This document is a product of the Audio/Video Transport Working Group of the IETF. This is now a Proposed Standard Protocol. 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/rfcsearch.html. 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