IETF Logo Mail Archive

RE: [AVT] RFC 2733 in 802.11

"Adam Li" <adamli@icsl.ucla.edu> Wed, 22 September 2004 05:14 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 BAA01962 for <avt-archive@ietf.org>; Wed, 22 Sep 2004 01:14:00 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1C9zYa-0006TU-Cd for avt-archive@ietf.org; Wed, 22 Sep 2004 01:20:45 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C9zNb-00031s-87; Wed, 22 Sep 2004 01:09:23 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1C9zDI-0000Pp-1h for avt@megatron.ietf.org; Wed, 22 Sep 2004 00:58:44 -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 AAA00880 for <avt@ietf.org>; Wed, 22 Sep 2004 00:58:40 -0400 (EDT)
Received: from mail5.dslextreme.com ([66.51.199.81]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1C9zJc-000683-Hm for avt@ietf.org; Wed, 22 Sep 2004 01:05:27 -0400
Received: (qmail 19177 invoked from network); 22 Sep 2004 03:57:56 -0000
Received: from unknown (HELO server.hyervision.com) (66.159.193.111) by 192.168.8.93 with (EDH-RSA-DES-CBC3-SHA encrypted) SMTP; Wed, 22 Sep 2004 03:57:56 +0000
Received: from peacock (adsl-66-159-193-142.dslextreme.com [66.159.193.142]) by server.hyervision.com (8.12.11/8.12.11) with ESMTP id i8M40N2v018338; Tue, 21 Sep 2004 21:00:23 -0700 (PDT)
From: Adam Li <adamli@icsl.ucla.edu>
To: linux_fan@spymac.com, avt@ietf.org
Subject: RE: [AVT] RFC 2733 in 802.11
Date: Tue, 21 Sep 2004 20:57:32 -0700
Message-ID: <000c01c4a058$4a3d8b10$658ea8c0@peacock>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2616
Importance: Normal
In-Reply-To: <20040922022419.D2ACE38084@spy23.spymac.net>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
X-AntiVirus: scanned for viruses by AMaViS 0.2.1 (http://amavis.org/)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Content-Transfer-Encoding: 7bit
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>
Sender: avt-bounces@ietf.org
Errors-To: avt-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Content-Transfer-Encoding: 7bit

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 [mailto: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



_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt

v2.30.2 | Report a Bug | By Email | System Status