Re: [AVT] Progressing the RTP no-op payload format
Colin Perkins <csp@csperkins.org> Mon, 20 August 2007 22:50 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 1ING4S-0005xw-8v; Mon, 20 Aug 2007 18:50:04 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1ING4R-0005s1-6G for avt@ietf.org; Mon, 20 Aug 2007 18:50:03 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1ING4Q-0007sQ-PZ for avt@ietf.org; Mon, 20 Aug 2007 18:50:03 -0400
Received: from csperkins-dsl.demon.co.uk ([62.49.4.249]:60795 helo=[192.168.0.4]) by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42) id 1ING4P-00033r-QT for avt@ietf.org; Mon, 20 Aug 2007 23:50:01 +0100
Mime-Version: 1.0 (Apple Message framework v752.2)
In-Reply-To: <9AF2A1B3-91CD-4A89-A455-2501CE41A72C@csperkins.org>
References: <9AF2A1B3-91CD-4A89-A455-2501CE41A72C@csperkins.org>
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <92986A11-DA21-45EF-B58B-329B778DB3FD@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: Re: [AVT] Progressing the RTP no-op payload format
Date: Mon, 20 Aug 2007 23:50:00 +0100
To: AVT WG <avt@ietf.org>
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
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
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
- RE: [AVT] Progressing the RTP no-op payload format Attila Sipos
- [AVT] Progressing the RTP no-op payload format Colin Perkins
- Re: [AVT] Progressing the RTP no-op payload format Colin Perkins
- RE: [AVT] Progressing the RTP no-op payload format Attila Sipos
- Re: [AVT] Progressing the RTP no-op payload format Magnus Westerlund