Re: [AVT] jitter+seqno generation 3550
"Greg Herlein" <gherlein@herlein.com> Fri, 11 January 2008 15:04 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 1JDLRH-0001T5-NN; Fri, 11 Jan 2008 10:04:55 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JDLRG-0001Sz-Q8 for avt@ietf.org; Fri, 11 Jan 2008 10:04:54 -0500
Received: from hs-out-0708.google.com ([64.233.178.241] helo=hs-out-2122.google.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1JDLRG-0006Xr-F5 for avt@ietf.org; Fri, 11 Jan 2008 10:04:54 -0500
Received: by hs-out-2122.google.com with SMTP id 54so1048399hsz.5 for <avt@ietf.org>; Fri, 11 Jan 2008 07:04:54 -0800 (PST)
Received: by 10.142.98.18 with SMTP id v18mr1685859wfb.61.1200063893467; Fri, 11 Jan 2008 07:04:53 -0800 (PST)
Received: by 10.142.132.17 with HTTP; Fri, 11 Jan 2008 07:04:53 -0800 (PST)
Message-ID: <31d1be720801110704m4eaa355aqe7cb359236d1e318@mail.gmail.com>
Date: Fri, 11 Jan 2008 07:04:53 -0800
From: Greg Herlein <gherlein@herlein.com>
To: Lakshmi Thampi <lakshmi.thampi@sasken.com>
Subject: Re: [AVT] jitter+seqno generation 3550
In-Reply-To: <DDC158258E79D342BE1BE1C5F0BD92053E4565@EXGZ01.sasken.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <DDC158258E79D342BE1BE1C5F0BD92053E4565@EXGZ01.sasken.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Cc: avt@ietf.org
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
Well, at a minimum it's useful to detect (and correct) out of order
packets. But, I suppose there's nothing to say you cannot just ignore
it.
Why do so few implementations support RTCP? It's one of my pet
peeves. RTCP is well worth adding. Why not add it?
Greg
On 1/11/08, Lakshmi Thampi <lakshmi.thampi@sasken.com> wrote:
>
>
> Hello
> In reference to RFC 3550, Appendix A.1
>
> If the RTCP functionality is not used then can we assume that sequence no is
> not a valid in RTP header
>
> regards
> LakshmiSASKEN BUSINESS DISCLAIMER
> -------------------------
> This message may contain confidential, proprietary or legally privileged
> information. In
> case you are not the original intended Recipient of the message, you must
> not, directly or
> indirectly, use, Disclose, distribute, print, or copy any part of this
> message and you are
> requested to delete it and inform the sender. Any views expressed in this
> message are
> those of the individual sender unless otherwise stated. Nothing contained in
> this message
> shall be construed as an offer or acceptance of any offer by Sasken
> Communication
> Technologies Limited ("Sasken") unless sent with that express intent and
> with due
> authority of Sasken. Sasken has taken enough precautions to prevent the
> spread of
> viruses. However the company accepts no liability for any damage caused by
> any virus
> transmitted by this email
>
>
> _______________________________________________
> 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
- [AVT] jitter+seqno generation 3550 Lakshmi Thampi
- Re: [AVT] jitter+seqno generation 3550 Greg Herlein
- Re: [AVT] jitter+seqno generation 3550 Bob Gilman
- Re: [AVT] jitter+seqno generation 3550 Greg Herlein
- Re: [AVT] jitter+seqno generation 3550 Bob Gilman
- RE: [AVT] jitter+seqno generation 3550 Even, Roni