RE: [L2tpext] L2TP Header Compression

"Daniel Feldman" <daniel@ic4ic.com> Mon, 28 January 2002 15:43 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 KAA29859 for <l2tpext-archive@odin.ietf.org>; Mon, 28 Jan 2002 10:43:19 -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 KAA17553; Mon, 28 Jan 2002 10:37:37 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA17526 for <l2tpext@optimus.ietf.org>; Mon, 28 Jan 2002 10:37:34 -0500 (EST)
Received: from exchange.Ic4ic.com ([194.90.135.194]) by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA29611 for <l2tpext@ietf.org>; Mon, 28 Jan 2002 10:37:28 -0500 (EST)
Received: through eSafe SMTP Relay 1011879144; Mon Jan 28 17:40:11 2002
content-class: urn:content-classes:message
Subject: RE: [L2tpext] L2TP Header Compression
MIME-Version: 1.0
Content-Type: text/plain; charset="Windows-1252"
Date: Mon, 28 Jan 2002 17:36:17 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0
Message-ID: <88BC9E379956AE4DB689CC5FF6F5A43D15C9E1@exchange.Ic4ic.com>
Thread-Topic: [L2tpext] L2TP Header Compression
Thread-Index: AcGoEJUxlqR5w7afTS24h4nUemGrHQAAFr8g
From: Daniel Feldman <daniel@ic4ic.com>
To: l2tpext@ietf.org
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by optimus.ietf.org id KAA17527
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

Hi Jitender,
the whole idea of L2TPHC is reducing the size of the header. In order to
do this, it is assumed there is only one tunnel per session. It would be
possible to use bits 3 and 4 (for example), in the same way bits 1 and 2
are used, to determine if there is a tunnel or not. If there are enough
people interested in the issue of multiple tunnels...
    Regards,
        Daniel.

-----Original Message-----
From: Jitender Arora [mailto:jitender@nortelnetworks.com]
Sent: Monday, January 28, 2002 5:26 PM
To: l2tpext@ietf.org
Subject: RE: [L2tpext] L2TP Header Compression 



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 <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
<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
<https://www1.ietf.org/mailman/listinfo/l2tpext>  


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