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

Stephan Wenger <stewe@stewe.org> Fri, 04 June 2010 15:20 UTC

Return-Path: <stewe@stewe.org>
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 8F4C03A67AD for <avt@core3.amsl.com>; Fri, 4 Jun 2010 08:20:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.398
X-Spam-Level: *
X-Spam-Status: No, score=1.398 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.396]
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 c20UcfkQiuON for <avt@core3.amsl.com>; Fri, 4 Jun 2010 08:20:00 -0700 (PDT)
Received: from stewe.org (stewe.org [85.214.122.234]) by core3.amsl.com (Postfix) with ESMTP id A233F3A680E for <avt@ietf.org>; Fri, 4 Jun 2010 08:19:59 -0700 (PDT)
Received: from [192.168.1.104] (unverified [24.5.132.232]) by stewe.org (SurgeMail 3.9e) with ESMTP id 680881-1743317 for multiple; Fri, 04 Jun 2010 17:19:45 +0200
User-Agent: Microsoft-Entourage/12.24.0.100205
Date: Fri, 04 Jun 2010 08:19:12 -0700
From: Stephan Wenger <stewe@stewe.org>
To: "Van Caenegem, Tom (Tom)" <tom.van_caenegem@alcatel-lucent.com>, Roni Even <Even.roni@huawei.com>, 'IETF AVT WG' <avt@ietf.org>
Message-ID: <C82E6780.21EAF%stewe@stewe.org>
Thread-Topic: [AVT] accepting draft-begen-avt-rtp-cnames-02 as a WG document
Thread-Index: AcsD94cg99aMaKl6ToCSaC4Vj+K4lQAAJfqAAABKiqY=
In-Reply-To: <EC3FD58E75D43A4F8807FDE0749175460A2DF1BB@FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3358484380_357396"
X-Originating-IP: 24.5.132.232
X-Authenticated-User: stewe@stewe.org
X-ORBS-Stamp: Your IP (24.5.132.232) was found in the spamhaus database. http://www.spamhaus.net
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:20:01 -0000

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