From owner-freebsd-net@FreeBSD.ORG  Thu Jan 27 15:00:34 2005
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 9888B16A4CF
	for <net@freebsd.org>; Thu, 27 Jan 2005 15:00:34 +0000 (GMT)
Received: from 212.106.239.101.adsl.jazztel.es
	(212.106.239.101.adsl.jazztel.es [212.106.239.101])
	by mx1.FreeBSD.org (Postfix) with ESMTP id A523A43D2F
	for <net@freebsd.org>; Thu, 27 Jan 2005 15:00:32 +0000 (GMT)
	(envelope-from josemi@freebsd.jazztel.es)
Received: from orion.redesjm.local (orion.redesjm.local [192.168.254.16])
	j0RF0TIK036717
	for <net@freebsd.org>; Thu, 27 Jan 2005 16:00:30 +0100 (CET)
	(envelope-from josemi@freebsd.jazztel.es)
From: Jose M Rodriguez <josemi@freebsd.jazztel.es>
Organization: Redes JM
To: net@freebsd.org
Date: Thu, 27 Jan 2005 16:00:42 +0100
User-Agent: KMail/1.7.1
MIME-Version: 1.0
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200501271600.42408.josemi@freebsd.jazztel.es>
X-AntiVirus: checked by AntiVir Milter (version: 1.1.0-3; AVE: 6.29.0.8;
	VDF: 6.29.0.75; host: antares.redesjm.local)
Subject: [OT] aal5 pdu CRC
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jan 2005 15:00:34 -0000

Hi,

get some free time to work in uadsl, but have a problem.  Hope someone that 
can read ITU I.363 can answer this.

Every usb adsl modem implementation I see doesn't obey aal5 pdu encoding 
standards, which requires that the PDU trailer come at the begin of a fresh 
cell.

So, I think that the modem must rework this and generate two cells on the 
wire.  Due how this modems works, I doubt that the modem recalculate PDU CRC 
itself, So...

Can someone confir if the CRC covers the PAD?  I'm begin to think that the CRC 
only covers the playload and the pdu-trailer.

--
  josemi