IETF Logo Mail Archive

Re: [AVT] accepting draft-begen-avt-rtp-cnames-02 as a WG document

"Van Caenegem, Tom (Tom)" <tom.van_caenegem@alcatel-lucent.com> Fri, 04 June 2010 15:11 UTC

Return-Path: <tom.van_caenegem@alcatel-lucent.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3032E3A6800 for <avt@core3.amsl.com>; Fri, 4 Jun 2010 08:11:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.166
X-Spam-Level:
X-Spam-Status: No, score=0.166 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9Hp6TiHGTXGu for <avt@core3.amsl.com>; Fri, 4 Jun 2010 08:11:41 -0700 (PDT)
Received: from smail6.alcatel.fr (smail6.alcatel.fr [62.23.212.42]) by core3.amsl.com (Postfix) with ESMTP id 854A63A67BD for <avt@ietf.org>; Fri, 4 Jun 2010 08:11:40 -0700 (PDT)
Received: from FRMRSSXCHHUB01.dc-m.alcatel-lucent.com (FRMRSSXCHHUB01.dc-m.alcatel-lucent.com [135.120.45.61]) by smail6.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id o54FBMRa018024 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 4 Jun 2010 17:11:22 +0200
Received: from FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com ([135.120.45.41]) by FRMRSSXCHHUB01.dc-m.alcatel-lucent.com ([135.120.45.61]) with mapi; Fri, 4 Jun 2010 17:11:22 +0200
From: "Van Caenegem, Tom (Tom)" <tom.van_caenegem@alcatel-lucent.com>
To: Roni Even <Even.roni@huawei.com>, 'IETF AVT WG' <avt@ietf.org>
Date: Fri, 04 Jun 2010 17:11:21 +0200
Thread-Topic: [AVT] accepting draft-begen-avt-rtp-cnames-02 as a WG document
Thread-Index: AcsD94cg99aMaKl6ToCSaC4Vj+K4lQAAJfqA
Message-ID: <EC3FD58E75D43A4F8807FDE0749175460A2DF1BB@FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com>
References: <044001cb03f7$8ed1f140$ac75d3c0$%roni@huawei.com>
In-Reply-To: <044001cb03f7$8ed1f140$ac75d3c0$%roni@huawei.com>
Accept-Language: nl-NL, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: nl-NL, en-US
Content-Type: multipart/alternative; boundary="_000_EC3FD58E75D43A4F8807FDE0749175460A2DF1BBFRMRSSXCHMBSB1d_"
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.64 on 155.132.188.84
Subject: Re: [AVT] accepting draft-begen-avt-rtp-cnames-02 as a WG document
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 04 Jun 2010 15:11:42 -0000

Roni,

I support this work,
Tom

________________________________
From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of Roni Even
Sent: vrijdag 4 juni 2010 17:07
To: 'IETF AVT WG'
Subject: [AVT] accepting draft-begen-avt-rtp-cnames-02 as a WG document

Hi,

In Section 6.5.1 of RFC3550, there are a number of recommendations for choosing a unique RTCP CNAME for an RTP endpoint.  However, in  practice, some of these methods are not guaranteed to produce a  unique CNAME.

http://tools.ietf.org/html/draft-begen-avt-rtp-cnames-02 proposes updated guidelines for choosing CNAMEs, superseding those presented in Section 6.5.1 of [RFC3550].



This was recognized as an issue to solve in the last IETF meetings.



The AVT chairs would like to ask if the group feels that this document should be accepted as a starting point for the working group document for resolving the issue.



Please send any comments till June 12th



Thanks

Roni Even

AVT co-chair

v2.23.0 | Report a Bug | By Email