RE: [L2tpext] L2TP Header Compression
"Jitender Arora"<jitender@nortelnetworks.com> Mon, 28 January 2002 15:33 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 KAA29416 for <l2tpext-archive@odin.ietf.org>; Mon, 28 Jan 2002 10:33:12 -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 KAA16618; Mon, 28 Jan 2002 10:26:58 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA16589 for <l2tpext@optimus.ietf.org>; Mon, 28 Jan 2002 10:26:56 -0500 (EST)
Received: from zrc2s0jx.nortelnetworks.com (zrc2s0jx.nortelnetworks.com [47.103.122.112]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29119 for <l2tpext@ietf.org>; Mon, 28 Jan 2002 10:26:51 -0500 (EST)
Received: from zsc4c000.us.nortel.com (zsc4c000.us.nortel.com [47.81.138.47]) by zrc2s0jx.nortelnetworks.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g0SFQM602617 for <l2tpext@ietf.org>; Mon, 28 Jan 2002 09:26:22 -0600 (CST)
Received: by zsc4c000.us.nortel.com with Internet Mail Service (5.5.2653.19) id <D248SM6A>; Mon, 28 Jan 2002 07:26:14 -0800
Message-ID: <8B888AAAAB0FD31189590008C791844309DC064B@zbl6c002.corpeast.baynetworks.com>
From: Jitender Arora <jitender@nortelnetworks.com>
To: l2tpext@ietf.org
Subject: RE: [L2tpext] L2TP Header Compression
Date: Mon, 28 Jan 2002 07:26:14 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C1A810.1FC82CC0"
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
Hello ,
Is it possible to make the provision in the L2TPHC for the tunnel
id ....as in our implementation of the L2TP , we can have multiple tunnels
between the LAC and the LNS ......So it won't be possible for us to use the
L2TPHC if we cannot have the tunnel id ....
Regards,
Jitender
-----Original Message-----
From: Daniel Feldman [mailto:daniel@ic4ic.com]
Sent: Monday, January 28, 2002 2:35 AM
To: l2tpext@ietf.org; vandys@zendo.com
Subject: [L2tpext] L2TP Header Compression L2TPHC-PPP-Protocol optional
AVP
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
- RE: [L2tpext] L2TP Header Compression Jitender Arora
- RE: [L2tpext] L2TP Header Compression Daniel Feldman