IETF Logo Mail Archive

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

Jean-Francois Mule <jf.mule@cablelabs.com> Fri, 04 June 2010 15:25 UTC

Return-Path: <jf.mule@cablelabs.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 479803A67D1 for <avt@core3.amsl.com>; Fri, 4 Jun 2010 08:25:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.906
X-Spam-Level: *
X-Spam-Status: No, score=1.906 tagged_above=-999 required=5 tests=[AWL=-0.046, BAYES_40=-0.185, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, 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 NTUny5Ky279X for <avt@core3.amsl.com>; Fri, 4 Jun 2010 08:25:12 -0700 (PDT)
Received: from ondar.cablelabs.com (ondar.cablelabs.com [192.160.73.61]) by core3.amsl.com (Postfix) with ESMTP id 00C8D3A67AD for <avt@ietf.org>; Fri, 4 Jun 2010 08:25:11 -0700 (PDT)
Received: from kyzyl.cablelabs.com (kyzyl [10.253.0.7]) by ondar.cablelabs.com (8.14.4/8.14.4) with ESMTP id o54FNA9t012045; Fri, 4 Jun 2010 09:23:10 -0600
Received: from srvxchg.cablelabs.com (10.5.0.15) by kyzyl.cablelabs.com (F-Secure/fsigk_smtp/303/kyzyl.cablelabs.com); Fri, 4 Jun 2010 09:23:10 -0700 (MST)
X-Virus-Status: clean(F-Secure/fsigk_smtp/303/kyzyl.cablelabs.com)
Received: from srvxchg.cablelabs.com ([10.5.0.15]) by srvxchg ([10.5.0.15]) with mapi; Fri, 4 Jun 2010 09:23:10 -0600
From: Jean-Francois Mule <jf.mule@cablelabs.com>
To: Stephan Wenger <stewe@stewe.org>, "Van Caenegem, Tom (Tom)" <tom.van_caenegem@alcatel-lucent.com>, Roni Even <Even.roni@huawei.com>, 'IETF AVT WG' <avt@ietf.org>
Date: Fri, 04 Jun 2010 09:23:06 -0600
Thread-Topic: [AVT] accepting draft-begen-avt-rtp-cnames-02 as a WG document
Thread-Index: AcsD94cg99aMaKl6ToCSaC4Vj+K4lQAAJfqAAABKiqYAAB7xwA==
Message-ID: <76AC5FEF83F1E64491446437EA81A61F7CF49FACDE@srvxchg>
References: <EC3FD58E75D43A4F8807FDE0749175460A2DF1BB@FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com> <C82E6780.21EAF%stewe@stewe.org>
In-Reply-To: <C82E6780.21EAF%stewe@stewe.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_76AC5FEF83F1E64491446437EA81A61F7CF49FACDEsrvxchg_"
MIME-Version: 1.0
X-Approved: ondar
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:25:13 -0000

I also support this work.

Jean-Francois.

From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] On Behalf Of Stephan Wenger
Sent: Friday, June 04, 2010 9:19 AM
To: Van Caenegem, Tom (Tom); Roni Even; 'IETF AVT WG'
Subject: Re: [AVT] accepting draft-begen-avt-rtp-cnames-02 as a WG document

Me as well.
Stephan


On 6.4.2010 08:11 , "Van Caenegem, Tom (Tom)" <tom.van_caenegem@alcatel-lucent.com> wrote:
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



________________________________
_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www.ietf.org/mailman/listinfo/avt

v2.23.0 | Report a Bug | By Email