Re: [AVT] Comments on draft-ietf-avt-rfc2793bis-01
Colin Perkins <csp@csperkins.org> Wed, 21 January 2004 20:30 UTC
Received: from optimus.ietf.org ([132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06793 for <avt-archive@odin.ietf.org>; Wed, 21 Jan 2004 15:30:41 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AjOzM-0008HE-GS for avt-archive@odin.ietf.org; Wed, 21 Jan 2004 15:30:12 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i0LKUC1e031766 for avt-archive@odin.ietf.org; Wed, 21 Jan 2004 15:30:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AjOzD-0008Cp-5z; Wed, 21 Jan 2004 15:30:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1AjOyU-00083c-Ip for avt@optimus.ietf.org; Wed, 21 Jan 2004 15:29:18 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06705 for <avt@ietf.org>; Wed, 21 Jan 2004 15:29:16 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1AjOyT-0000Cm-00 for avt@ietf.org; Wed, 21 Jan 2004 15:29:17 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1AjOxV-0000AI-00 for avt@ietf.org; Wed, 21 Jan 2004 15:28:17 -0500
Received: from dundee.dcs.gla.ac.uk ([130.209.242.163]) by ietf-mx with esmtp (Exim 4.12) id 1AjOwf-00006W-00 for avt@ietf.org; Wed, 21 Jan 2004 15:27:25 -0500
Received: from csperkins-dsl.demon.co.uk ([80.176.225.173]:61777 helo=mangole.dcs.gla.ac.uk) by dundee.dcs.gla.ac.uk with asmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.04) id 1AjOvq-0005AK-00; Wed, 21 Jan 2004 20:26:34 +0000
Date: Wed, 21 Jan 2004 20:26:44 +0000
From: Colin Perkins <csp@csperkins.org>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Cc: gunnar.hellstrom@omnitor.com, paulej@packetizer.com, avt@ietf.org
Subject: Re: [AVT] Comments on draft-ietf-avt-rfc2793bis-01
Message-Id: <20040121202644.6eb04350.csp@csperkins.org>
In-Reply-To: <400EBB85.3060704@ericsson.com>
References: <400EBB85.3060704@ericsson.com>
Organization: http://csperkins.org/
X-Mailer: Sylpheed version 0.9.8a (GTK+ 1.2.10; i386-portbld-freebsd4.9)
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
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>
Content-Transfer-Encoding: 7bit
--> Magnus Westerlund <magnus.westerlund@ericsson.com> writes:
> Hi Gunnar and Paul,
>
> Here is my comments on the payload format.
...
> 12. In regards to the robustness options. As we now have available
> mechanism to report packet losses, RFC 3611, but probably more important
> draft-ietf-avt-rtcp-feedback and its NACK format, there is now
> possibilities to do reactive repairs. I think the possibility should at
> least be mentioned, or if it doesn't work, that should be motivated.
> Please investigate this.
Unless specified otherwise, it should be assumed that the standard, payload
format independent, repair schemes can be used with any new payload format.
I don't see any need to list them specially here.
> 14. Section 6.3: The RED SDP examples. Why does on have a=fmtp lines
> like this? To my understanding of the pt list it should only contain a
> single 98. This is either a bug here, or problem in the text/red
> document.
The SDP fragments such as
m=text 11000 RTP/AVP 98 100
a=rtpmap:98 t140/1000
a=rtpmap:100 red/1000
a=fmtp:100 98/98
appear to be correct. The "a=fmtp:100 98/98" line indicates that both
primary and redundant coding use payload type 98.
> 15. Section 7: I think the security section can be improved:
> - Separate the three main issues, confidentiality, integrity, and source
> authentication. They are different, and have different severity and
> attacks, and different counters.
> - The section should give recommendations to mechanism that allows one
> to counter these problems. For the two first SRTP works very well. For
> the last it provides some properties that can be used to accomplish
> that, combined with the signalling.
> So please expand this.
Note that this is recommendations, rather than "MUST" requirements, since
SRTP is not appropriate in all cases.
--
Colin Perkins
http://csperkins.org/
_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt
- [AVT] Comments on draft-ietf-avt-rfc2793bis-01 Magnus Westerlund
- Re: [AVT] Comments on draft-ietf-avt-rfc2793bis-01 Colin Perkins
- Re: [AVT] Comments on draft-ietf-avt-rfc2793bis-01 Magnus Westerlund