From pppext-bounces@ietf.org Wed Jan 18 11:18:30 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EzG10-0000S8-JR; Wed, 18 Jan 2006 11:18:30 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EzG0z-0000Rz-Ok
	for pppext@megatron.ietf.org; Wed, 18 Jan 2006 11:18:29 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00399
	for <pppext@ietf.org>; Wed, 18 Jan 2006 11:17:02 -0500 (EST)
Received: from hoemail1.lucent.com ([192.11.226.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EzG9L-0008K3-17
	for pppext@ietf.org; Wed, 18 Jan 2006 11:27:08 -0500
Received: from nj0117exch001p.wins.lucent.com (h135-5-177-157.lucent.com
	[135.5.177.157])
	by hoemail1.lucent.com (8.12.11/8.12.11) with ESMTP id k0IGIKi1010441
	for <pppext@ietf.org>; Wed, 18 Jan 2006 10:18:20 -0600 (CST)
Received: by nj0117exch001p.wh.lucent.com with Internet Mail Service
	(5.5.2657.72) id <XN58YT2F>; Wed, 18 Jan 2006 11:18:19 -0500
Message-ID: <6CF036121950A44C93F5DB88CF3398D415AF3447@nj0117exch001u.wh.lucent.com>
From: "Couch, William Garrant, JR (Garry)" <couch@lucent.com>
To: "'pppext@ietf.org'" <pppext@ietf.org>
Date: Wed, 18 Jan 2006 11:18:17 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
Subject: [Pppext] Address and Control Field Compression in RFC 1661
X-BeenThere: pppext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: PPP Extensions <pppext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pppext>,
	<mailto:pppext-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pppext@ietf.org>
List-Help: <mailto:pppext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pppext>,
	<mailto:pppext-request@ietf.org?subject=subscribe>
Sender: pppext-bounces@ietf.org
Errors-To: pppext-bounces@ietf.org

PPPEXTers,

I'm hoping that one or more of you can shed some light on section 6.6, Address and Control Field Compression, in RFC 1661.  Is this intended to refer to a specific compression method, a general compression method, or just to the dropping of prefixed zero octets (as in the previous section, 6.5, on Protocol Field Compression)?

Garry Couch
System Engineer
CDMA Radio Access Networks
Whippany, NJ
973 386-7437


_______________________________________________
Pppext mailing list
Pppext@ietf.org
https://www1.ietf.org/mailman/listinfo/pppext



From pppext-bounces@ietf.org Wed Jan 18 11:31:44 2006
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1EzGDo-0004u6-JJ; Wed, 18 Jan 2006 11:31:44 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1EzGDm-0004tQ-PA
	for pppext@megatron.ietf.org; Wed, 18 Jan 2006 11:31:43 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01503
	for <pppext@ietf.org>; Wed, 18 Jan 2006 11:30:15 -0500 (EST)
Received: from nwkea-mail-1.sun.com ([192.18.42.13])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EzGM6-0000MN-UA
	for pppext@ietf.org; Wed, 18 Jan 2006 11:40:21 -0500
Received: from eastmail2bur.East.Sun.COM ([129.148.13.40])
	by nwkea-mail-1.sun.com (8.12.10/8.12.9) with ESMTP id k0IGVXdK019538
	for <pppext@ietf.org>; Wed, 18 Jan 2006 08:31:34 -0800 (PST)
Received: from phorcys.East.Sun.COM (phorcys.East.Sun.COM [129.148.174.143])
	by eastmail2bur.East.Sun.COM (8.12.10+Sun/8.12.10/ENSMAIL,
	v2.2) with ESMTP id k0IGVXWa017042
	for <pppext@ietf.org>; Wed, 18 Jan 2006 11:31:33 -0500 (EST)
Received: from phorcys.East.Sun.COM (localhost [127.0.0.1])
	by phorcys.East.Sun.COM (8.13.5+Sun/8.13.5) with ESMTP id
	k0IGVXA4027398; Wed, 18 Jan 2006 11:31:33 -0500 (EST)
Received: (from carlsonj@localhost)
	by phorcys.East.Sun.COM (8.13.5+Sun/8.13.5/Submit) id k0IGVXLE027395;
	Wed, 18 Jan 2006 11:31:33 -0500 (EST)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <17358.28005.389870.298390@gargle.gargle.HOWL>
Date: Wed, 18 Jan 2006 11:31:33 -0500
From: James Carlson <james.d.carlson@sun.com>
To: "Couch, William Garrant, JR (Garry)" <couch@lucent.com>
Subject: Re: [Pppext] Address and Control Field Compression in RFC 1661
In-Reply-To: Couch, William Garrant,
	JR (Garry)'s message of 18 January 2006 11:18:17
References: <6CF036121950A44C93F5DB88CF3398D415AF3447@nj0117exch001u.wh.lucent.com>
X-Mailer: VM 7.01 under Emacs 21.3.1
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Content-Transfer-Encoding: 7bit
Cc: "'pppext@ietf.org'" <pppext@ietf.org>
X-BeenThere: pppext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: PPP Extensions <pppext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pppext>,
	<mailto:pppext-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pppext@ietf.org>
List-Help: <mailto:pppext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pppext>,
	<mailto:pppext-request@ietf.org?subject=subscribe>
Sender: pppext-bounces@ietf.org
Errors-To: pppext-bounces@ietf.org

Couch, William Garrant, JR (Garry) writes:
> PPPEXTers,
> 
> I'm hoping that one or more of you can shed some light on section 6.6, Address and Control Field Compression, in RFC 1661.  Is this intended to refer to a specific compression method, a general compression method, or just to the dropping of prefixed zero octets (as in the previous section, 6.5, on Protocol Field Compression)?

It refers only to the _removal_ of the HDLC Address and Control fields
from the frames.  It has nothing to do with data compression or zero
octets.

The Address and Control field values are (assuming you're not using
Frame Relay, RFC 1663, or some other HDLC-based scheme that relies on
those fields) a fixed hex FF 03 on each packet.  Since "FF 03" can
never be a legal protocol number, it's safe to just discard those two
bytes -- omit them entirely from the datagram sent on the wire.  This
option negotiates that feature.

-- 
James Carlson, KISS Network                    <james.d.carlson@sun.com>
Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

_______________________________________________
Pppext mailing list
Pppext@ietf.org
https://www1.ietf.org/mailman/listinfo/pppext



