[xrblock] FW: [AVTCORE] Last Call: <draft-ietf-avtcore-6222bis-03.txt> (Guidelines for Choosing RTP Control Protocol (RTCP) Canonical Names (CNAMEs)) to Proposed Standard
"Romascanu, Dan (Dan)" <dromasca@avaya.com> Wed, 29 May 2013 08:30 UTC
Return-Path: <dromasca@avaya.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB34621F9058 for <xrblock@ietfa.amsl.com>; Wed, 29 May 2013 01:30:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.474
X-Spam-Level:
X-Spam-Status: No, score=-103.474 tagged_above=-999 required=5 tests=[AWL=0.125, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 2KqZve2JRf0a for <xrblock@ietfa.amsl.com>; Wed, 29 May 2013 01:30:39 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by ietfa.amsl.com (Postfix) with ESMTP id 6ED7A21F9051 for <xrblock@ietf.org>; Wed, 29 May 2013 01:30:39 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgUFAAH/ZlHGmAcF/2dsb2JhbABQgmUhNsFIgQcWdIIfAQEBAQMBAQEPKDQXBgEIDQQEAQELFAUELgsUBwEBBQUEEwgah3IBC5wRhCudDBeOZSYYglphA5gjhQaKaIFVgTaCKA
X-IronPort-AV: E=Sophos;i="4.87,456,1363147200"; d="scan'208";a="13280047"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 29 May 2013 04:30:37 -0400
Received: from unknown (HELO AZ-FFEXHC03.global.avaya.com) ([135.64.58.13]) by co300216-co-erhwest-out.avaya.com with ESMTP; 29 May 2013 04:25:02 -0400
Received: from AZ-FFEXMB04.global.avaya.com ([fe80::6db7:b0af:8480:c126]) by AZ-FFEXHC03.global.avaya.com ([135.64.58.13]) with mapi id 14.02.0328.009; Wed, 29 May 2013 04:30:36 -0400
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: 'xrblock' <xrblock@ietf.org>
Thread-Topic: [AVTCORE] Last Call: <draft-ietf-avtcore-6222bis-03.txt> (Guidelines for Choosing RTP Control Protocol (RTCP) Canonical Names (CNAMEs)) to Proposed Standard
Thread-Index: AQHOW+W8XrXWGOgt+UKwE2Yy9Yen7pkb1VqQ
Date: Wed, 29 May 2013 08:30:35 +0000
Message-ID: <9904FB1B0159DA42B0B887B7FA8119CA17A22A@AZ-FFEXMB04.global.avaya.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.64.58.45]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: [xrblock] FW: [AVTCORE] Last Call: <draft-ietf-avtcore-6222bis-03.txt> (Guidelines for Choosing RTP Control Protocol (RTCP) Canonical Names (CNAMEs)) to Proposed Standard
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/xrblock>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 May 2013 08:30:46 -0000
I am not sure if there are participants in XRBLOCK who do not follow also AVTCORE, but in case there are, please pay attention to this IETF Last Call. Regards, Dan -----Original Message----- From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of The IESG Sent: Tuesday, May 28, 2013 11:56 PM To: IETF-Announce Cc: avt@ietf.org Subject: [AVTCORE] Last Call: <draft-ietf-avtcore-6222bis-03.txt> (Guidelines for Choosing RTP Control Protocol (RTCP) Canonical Names (CNAMEs)) to Proposed Standard The IESG has received a request from the Audio/Video Transport Core Maintenance WG (avtcore) to consider the following document: - 'Guidelines for Choosing RTP Control Protocol (RTCP) Canonical Names (CNAMEs)' <draft-ietf-avtcore-6222bis-03.txt> as Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2013-06-11. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract 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. 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. The file can be obtained via http://datatracker.ietf.org/doc/draft-ietf-avtcore-6222bis/ IESG discussion can be tracked via http://datatracker.ietf.org/doc/draft-ietf-avtcore-6222bis/ballot/ No IPR declarations have been submitted directly on this I-D. _______________________________________________ Audio/Video Transport Core Maintenance avt@ietf.org https://www.ietf.org/mailman/listinfo/avt
- [xrblock] FW: [AVTCORE] Last Call: <draft-ietf-av… Romascanu, Dan (Dan)