RE: [L2tpext] L2TP Header Compression L2TPHC-PPP-Protocol optiona l AVP

"Jitender Arora"<jitender@nortelnetworks.com> Mon, 28 January 2002 15:49 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 KAA00034 for <l2tpext-archive@odin.ietf.org>; Mon, 28 Jan 2002 10:49:34 -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 KAA17597; Mon, 28 Jan 2002 10:37:46 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id KAA17569 for <l2tpext@optimus.ietf.org>; Mon, 28 Jan 2002 10:37:44 -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 KAA29626 for <l2tpext@ietf.org>; Mon, 28 Jan 2002 10:37:39 -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 g0SFb8605539; Mon, 28 Jan 2002 09:37:08 -0600 (CST)
Received: by zsc4c000.us.nortel.com with Internet Mail Service (5.5.2653.19) id <D248SNC2>; Mon, 28 Jan 2002 07:37:00 -0800
Message-ID: <8B888AAAAB0FD31189590008C791844309DC064C@zbl6c002.corpeast.baynetworks.com>
From: Jitender Arora <jitender@nortelnetworks.com>
To: 'Daniel Feldman' <daniel@ic4ic.com>, l2tpext@ietf.org, vandys@zendo.com
Subject: RE: [L2tpext] L2TP Header Compression L2TPHC-PPP-Protocol optiona l AVP
Date: Mon, 28 Jan 2002 07:37:02 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C1A811.A1903EE0"
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 ,

     As far as as i have understood , If we use the L2TPHC-PPP-Protocol AVP
, then before that we must have sent the L2TPHC-No-Header , and it is
written in the draft that if we use the L2TPHC-No-Header AVP then we can
have only one session ( with the session id  equal to 0 ) ...SO there can't
be multiple sessions in that tunnel , there will be only one session .
      I am also having the same doubt that if we send the Protocol field
with this AVP , then how can we use LCP,CCPand NCP protocols for that
session .......means how are we going to switch from LCP to CCP and from CCP
to NCP....... 

Thanks and 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