RE: [AVT] Progressing the RTP no-op payload format

"Attila Sipos" <attila.sipos@vegastream.com> Tue, 21 August 2007 10:38 UTC

Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1INR89-0004Sl-4K; Tue, 21 Aug 2007 06:38:37 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1INR88-0004SD-Fs for avt@ietf.org; Tue, 21 Aug 2007 06:38:36 -0400
Received: from cluster-f.mailcontrol.com ([85.119.2.190]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1INR85-0000yr-Sl for avt@ietf.org; Tue, 21 Aug 2007 06:38:34 -0400
Received: from rly30f.srv.mailcontrol.com (localhost.localdomain [127.0.0.1]) by rly30f.srv.mailcontrol.com (MailControl) with ESMTP id l7LAcOhH014636 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <avt@ietf.org>; Tue, 21 Aug 2007 11:38:24 +0100
Received: from submission.mailcontrol.com (submission.mailcontrol.com [86.111.216.190]) by rly30f.srv.mailcontrol.com (MailControl) id l7LAbxME011856 for avt@ietf.org; Tue, 21 Aug 2007 11:37:59 +0100
Received: from exsmtp01.nasstar-t1.net (exsmtp01.nasstar-t1.net [89.28.233.12]) by rly30f-eth0.srv.mailcontrol.com (envelope-sender attila.sipos@vegastream.com) (MIMEDefang) with ESMTP id l7LAbj88010441; Tue, 21 Aug 2007 11:37:59 +0100 (BST)
Received: from ExBE03.nasstar-t1.net ([10.2.10.102]) by exsmtp01.nasstar-t1.net with Microsoft SMTPSVC(6.0.3790.1830); Tue, 21 Aug 2007 11:36:53 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Subject: RE: [AVT] Progressing the RTP no-op payload format
Date: Tue, 21 Aug 2007 11:34:28 +0100
Message-ID: <165288C2C3E29449AFDE022DD10CC471071285E4@ExBE03.nasstar-t1.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [AVT] Progressing the RTP no-op payload format
Thread-Index: AcfjfJVlxbH2YkSGQ4CUdjjRN5NQZAAYYkaQ
From: Attila Sipos <attila.sipos@vegastream.com>
To: Colin Perkins <csp@csperkins.org>, AVT WG <avt@ietf.org>
X-OriginalArrivalTime: 21 Aug 2007 10:36:53.0176 (UTC) FILETIME=[3059EB80:01C7E3DF]
X-Scanned-By: MailControl A-07-08-00 (www.mailcontrol.com) on 10.70.1.140
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Cc:
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Looks like a useful draft to me.

I think maybe the draft doesn't sound exciting and
so people won't express strong opinions one way or another.

Perosnally, I wouldn't like to see this draft disappear.

Regards,

Attila



-----Original Message-----
From: Colin Perkins [mailto:csp@csperkins.org] 
Sent: 20 August 2007 23:50
To: AVT WG
Subject: Re: [AVT] Progressing the RTP no-op payload format

On 1 Aug 2007, at 12:35, Colin Perkins wrote:
> The No-Op Payload Format for RTP (draft-ietf-avt-rtp-no-op-04.txt) is 
> technically complete. There has been, however, some discussion on IPR 
> relating to the draft: see http://www1.ietf.org/ietf/IPR/ 
> cisco-ipr-draft-ietf-avt-rtp-no-op-04.txt and http://www1.ietf.org/ 
> mail-archive/web/avt/current/msg08380.html and followups.
>
> My understanding is that some claims on the patent application are 
> sufficiently broad that it will be difficult to develop a no-op format

> which is not covered, should the patent be awarded. Given this, and 
> the IPR statement linked above, I'd like to ask the working group two 
> questions, so we can decide how to proceed with the draft:
>
> 1) Do you believe an RTP no-op payload format is useful to 
> standardise, given the other keep alive mechanisms that now exist?
>
> 2) Do you believe the working group should proceed with this 
> particular draft?
>
> Response to the list preferred, but private responses accepted and 
> I'll summarise.

No response - is everybody on vacation, or is there no interest in
pursuing this draft?

--
Colin Perkins
http://csperkins.org/



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

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