[AVT] Progressing the RTP no-op payload format
Colin Perkins <csp@csperkins.org> Wed, 01 August 2007 11:35 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 1IGCUD-00031u-5o; Wed, 01 Aug 2007 07:35:29 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IGCU9-00031p-UW for avt@ietf.org; Wed, 01 Aug 2007 07:35:25 -0400
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IGCU9-0002Wt-JU for avt@ietf.org; Wed, 01 Aug 2007 07:35:25 -0400
Received: from mangole.dcs.gla.ac.uk ([130.209.247.112]:49853) by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.42) id 1IGCU9-0003F9-8V for avt@ietf.org; Wed, 01 Aug 2007 12:35:25 +0100
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Transfer-Encoding: 7bit
Message-Id: <9AF2A1B3-91CD-4A89-A455-2501CE41A72C@csperkins.org>
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
To: AVT WG <avt@ietf.org>
From: Colin Perkins <csp@csperkins.org>
Date: Wed, 01 Aug 2007 12:35:23 +0100
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Subject: [AVT] Progressing the RTP no-op payload format
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
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. Thanks, Colin (as chair) _______________________________________________ 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