RE: [AVT] RFC 2733 in 802.11
McArthor Lee <linux_fan@spymac.com> Wed, 22 September 2004 05:07 UTC
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA01505 for <avt-archive@ietf.org>; Wed, 22 Sep 2004 01:07:46 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C9zSY-0006Kk-V8 for avt-archive@ietf.org; Wed, 22 Sep 2004 01:14:31 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C9z9n-00086Z-H3; Wed, 22 Sep 2004 00:55:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C9z8F-0007i3-CR for avt@megatron.ietf.org; Wed, 22 Sep 2004 00:53:31 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA00491 for <avt@ietf.org>; Wed, 22 Sep 2004 00:53:27 -0400 (EDT)
Received: from mail3.spymac.net ([195.225.149.3] helo=spy23.spymac.net) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C9zEk-00060D-5P for avt@ietf.org; Wed, 22 Sep 2004 01:00:14 -0400
Received: from webmail1.spymac.com (webmail1.spymac.net [195.225.149.201]) by spy23.spymac.net (Postfix) with ESMTP id 1063738047 for <avt@ietf.org>; Wed, 22 Sep 2004 06:53:28 +0200 (CEST)
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Mime-Version: 1.0
From: McArthor Lee <linux_fan@spymac.com>
To: avt@ietf.org
Subject: RE: [AVT] RFC 2733 in 802.11
X-Mailer: AtMail 4.02
X-Origin: 60.25.114.238
X-Uidl: 1095826495.H701254P6861.mail-in1.spymac.net
Date: Tue, 21 Sep 2004 22:53:25 -0600
Message-Id: <20040922045328.1063738047@spy23.spymac.net>
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Content-Transfer-Encoding: quoted-printable
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: linux_fan@spymac.com
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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Content-Transfer-Encoding: quoted-printable
would you please give some examples for specific "end-to-end error characteristics of each situation"? ======================= Thanks & Regards McArthor Lee On Tue Sep 21 21:57 , 'Adam Li' adamli@icsl.ucla.edu> sent: >The FEC in 802.11 is for physical and link layers. It is at different >layers from the FEC in RFC 2733. Whether RFC 2733 is necessary depends >on the detail of the end-to-end error characteristics of each situation >you are dealing with. > >Adam > >-----Original Message----- >From: avt-bounces@ietf.org [avt-bounces@ietf.org','','','')">avt-bounces@ietf.org] On Behalf Of >McArthor Lee >Sent: Tuesday, September 21, 2004 7:24 PM >To: avt@ietf.org >Subject: [AVT] RFC 2733 in 802.11 > >hi all, > >as we know, IEEE 802.11 has FEC mechanism built-in, so is RFC 2733's FEC >necessary? > >======================= >Thanks & Regards >McArthor Lee > > > >---- Get Urchin 6 On Demand web analytics. Because you can't wait to be >found. > >_______________________________________________ >Audio/Video Transport Working Group >avt@ietf.org >https://www1.ietf.org/mailman/listinfo/avt ---- Get Urchin 6 On Demand web analytics. Because you can't wait to be found. _______________________________________________ Audio/Video Transport Working Group avt@ietf.org https://www1.ietf.org/mailman/listinfo/avt
- [AVT] RFC 2733 in 802.11 McArthor Lee
- RE: [AVT] RFC 2733 in 802.11 McArthor Lee
- RE: [AVT] RFC 2733 in 802.11 Adam Li