[L2tpext] L2TP Header Compression L2TPHC-PPP-Protocol optional AVP

"Daniel Feldman" <daniel@ic4ic.com> Tue, 22 January 2002 10:02 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA14806 for <l2tpext-archive@odin.ietf.org>; Tue, 22 Jan 2002 05:02:25 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA29470; Tue, 22 Jan 2002 04:55:11 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA29440 for <l2tpext@optimus.ietf.org>; Tue, 22 Jan 2002 04:55:08 -0500 (EST)
Received: from exchange.Ic4ic.com ([194.90.135.194]) by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA14726 for <l2tpext@ietf.org>; Tue, 22 Jan 2002 04:55:03 -0500 (EST)
Received: through eSafe SMTP Relay 1011264762; Tue Jan 22 11:57:36 2002
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="windows-1255"
Date: Tue, 22 Jan 2002 11:53:56 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0
Message-ID: <88BC9E379956AE4DB689CC5FF6F5A43D02DE8A@exchange.Ic4ic.com>
Thread-Topic: L2TP Header Compression L2TPHC-PPP-Protocol optional AVP
Thread-Index: AcGjKrVQmjVfObcnSnW8vD6s+NHo2A==
From: Daniel Feldman <daniel@ic4ic.com>
To: l2tpext@ietf.org
Cc: vandys@zendo.com
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id EAA29441
Subject: [L2tpext] L2TP Header Compression L2TPHC-PPP-Protocol optional AVP
Sender: l2tpext-admin@ietf.org
Errors-To: l2tpext-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Layer Two Tunneling Protocol Extensions <l2tpext.ietf.org>
X-BeenThere: l2tpext@ietf.org
Content-Transfer-Encoding: 8bit

	Dear Mr. Valencia and L2TPers,
	reading
http://search.ietf.org/internet-drafts/draft-ietf-l2tpext-l2tphc-04.txt,
I didn't quite understand the usage of the L2TPHC-PPP-Protocol optional
AVP.
	The draft says: 
"Another optional AVP, ``L2TPHC-PPP-Protocol'', may be sent immediately
following the ``L2TPHC-No-Header''. If both sent and received, its Value
field indicates the PPP protocol number which will be the single value
carried in the payload of all PPP packets, and the payload transmitted
through L2TPHC will omit PPP HDLC flags and control, as well as the one
or two byte protocol field. The receiving side would then have to
recreate a suitable PPP header and insert it onto received payload."
	Does this mean that:
a) Only one NCP can run at a given time on the many sessions of the
Tunnel? Or is it per session?
b) There will be absolutely NO LCP packets on this tunnel? Else, how can
they be identified? 

	Thanks in advance,

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Daniel Feldman
System Architecture Team Leader, IC4IC Ltd.
office: +972(4)959-4644 ext. 121
mobile: +972(55)99-0299
fax:    +972(4)959-4944
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


_______________________________________________
L2tpext mailing list
L2tpext@ietf.org
https://www1.ietf.org/mailman/listinfo/l2tpext