From owner-l2tp@diameter.org  Tue Aug  1 04:31:53 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA26421
	for <l2tpext-archive@odin.ietf.org>; Tue, 1 Aug 2000 04:31:52 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e715Qpt25101
	for l2tp-list; Mon, 31 Jul 2000 22:26:51 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e715Qmd25095
	for <l2tp@l2tp.net>; Mon, 31 Jul 2000 22:26:48 -0700
Received: from webveda.com (root@host-216-226-254-55.interpacket.net [216.226.254.55]) by ns1.sailpix.com (8.8.8/8.6.9) with SMTP id WAA01135 for <l2tp@ipsec.org>; Mon, 31 Jul 2000 22:30:44 -0700 (PDT)
Received: from webveda.com ([216.226.254.55]) by webveda.com ; Tue, 01 Aug 2000 19:29:31 -0400
From: "Shankar" <shankarv@webveda.com>
Reply-to: shankarv@webveda.com
To: l2tp@ipsec.org
Date: Tue, 01 Aug 2000 11:00:39 +0600
Subject: Proxy LCP and Authentication 
X-Mailer: CWMail Web to Mail Gateway 2.5e, http://netwinsite.com/top_mail.htm
Message-id: <39875d5b.5740.0@webveda.com>
X-User-Info: 203.197.138.194
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi folks,

if LAC answers the call to identify the tunnel (based on the domain name), the
LCP nego that happens btwn LAC and the client called proxy LCP ? if not what
exactly is proxy LCP.

does proxy auth go hand in hand with proxy LCP ? 
is there a option in cisco to disable proxy auth at the 
LAC side?

tia
shankar

-------------------------------------------------
Make webveda your permanent address like i have.
Get 15 MB Free space only at http://www.webveda.com


From owner-l2tp@diameter.org  Tue Aug  1 04:56:44 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01721
	for <l2tpext-archive@odin.ietf.org>; Tue, 1 Aug 2000 04:56:43 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e7168wl25139
	for l2tp-list; Mon, 31 Jul 2000 23:08:58 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e7168ud25133
	for <l2tp@l2tp.net>; Mon, 31 Jul 2000 23:08:56 -0700
Received: from shako.cisco.com (shako.cisco.com [161.44.3.76]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id XAA01161 for <l2tp@ipsec.org>; Mon, 31 Jul 2000 23:12:52 -0700 (PDT)
Received: from cisco.com (rtp-dial-1-199.cisco.com [10.83.97.199])
	by shako.cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id CAA02542;
	Tue, 1 Aug 2000 02:12:01 -0400 (EDT)
Message-ID: <39866A48.1788BEA1@cisco.com>
Date: Tue, 01 Aug 2000 02:12:24 -0400
From: "W. Mark Townsley" <townsley@cisco.com>
X-Mailer: Mozilla 4.7 [en] (Win95; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: shankarv@webveda.com
CC: l2tp@ipsec.org
Subject: Re: Proxy LCP and Authentication
References: <39875d5b.5740.0@webveda.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



Shankar wrote:
> 
> Hi folks,
> 
> if LAC answers the call to identify the tunnel (based on the domain name), the
> LCP nego that happens btwn LAC and the client called proxy LCP ? if not what
> exactly is proxy LCP.

Proxy LCP is the forwarding of the negotiation that takes place between
the client and the LAC to the LNS.

> 
> does proxy auth go hand in hand with proxy LCP ?

Yes.

> is there a option in cisco to disable proxy auth at the
> LAC side?

No.

> 
> tia
> shankar
> 
> -------------------------------------------------
> Make webveda your permanent address like i have.
> Get 15 MB Free space only at http://www.webveda.com


From owner-l2tp@diameter.org  Tue Aug  1 08:13:23 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17009
	for <l2tpext-archive@odin.ietf.org>; Tue, 1 Aug 2000 08:13:23 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e719H9225314
	for l2tp-list; Tue, 1 Aug 2000 02:17:09 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from tele-post-20.mail.demon.net (tele-post-20.mail.demon.net [194.217.242.20])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e719H6d25308
	for <l2tp@l2tp.net>; Tue, 1 Aug 2000 02:17:06 -0700
Received: from [194.217.45.89] (helo=ABICKFORD01)
	by tele-post-20.mail.demon.net with smtp (Exim 2.12 #2)
	id 13JYEN-000P4T-0K
	for l2tp@l2tp.net; Tue, 1 Aug 2000 09:20:59 +0000
Reply-To: <abickford@ipwireless.com>
From: "Andy Bickford" <abickford@ipwireless.com>
To: <l2tp@l2tp.net>
Subject: Re: PPP Frames on tunnel
Date: Tue, 1 Aug 2000 10:16:13 +0100
Message-ID: <64BA237E6022D411BD4900B0D02192E802E176@IPWIRELESSINC01>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi folks,

Can anybody clarify the replies to Sridhar's question, as they appear to
contradict each other.

Hence what should be added to the PPP frames being sent from the LAC to
the LNS and the LNS to the LAC ?

How does the LAC/LNS distinguish between the FF 03 bytes that have been
added as extra bytes on entry to the tunnel and the real address and control
fields ?

Apologies if the questions have already been answered.

Best Regards

Andy Bickford
Technical Associate
IPWireless Inc


>Sridhar Malarothu wrote:
>
> Hi All,
>
>     LAC before sending ppp frames on tunnel to LAC should strip of
> the CRC, Link Framing and transperancy bytes, encapsulate them in L2TP
> header. But what should be status of the PPP frames on tunnel, if send
> by LNS.
>
> Best Regards
> Sridhar


>Mark Townsley's reply was:
>
>PPP framing of FF03, unless ACFC is negotiated, should exist on packets
>sent from the LNS and from the LAC.

>James Carlson's reply was:
>
>Data frames from the LNS should not have an appended CRC, framing, or
>transparency bytes, and they should have L2TP headers.
>
>Note that the leading FF 03 (the default values used for the HDLC Address
>and Control fields on regular PPP links) must be included on the tunneled
>frames, contrary to prior convention (such as described in RFCs 1598, 1973,
>and 2364). So, if you're coming from a regular PPP over Frame Relay network
>into an L2TP tunnel, you'll have to add those extra bytes on entry to the
>tunnel and remove them before going into Frame Relay.





From owner-l2tp@diameter.org  Tue Aug  1 09:53:24 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10570
	for <l2tpext-archive@odin.ietf.org>; Tue, 1 Aug 2000 09:53:23 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e71AMGw25450
	for l2tp-list; Tue, 1 Aug 2000 03:22:16 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e71AMEd25444
	for <l2tp@l2tp.net>; Tue, 1 Aug 2000 03:22:14 -0700
Received: from webveda.com (root@host-216-226-254-55.interpacket.net [216.226.254.55]) by ns1.sailpix.com (8.8.8/8.6.9) with SMTP id DAA02590 for <l2tp@ipsec.org>; Tue, 1 Aug 2000 03:26:10 -0700 (PDT)
Received: from webveda.com ([216.226.254.55]) by webveda.com ; Wed, 02 Aug 2000 00:24:54 -0400
From: "Shankar" <shankarv@webveda.com>
Reply-to: shankarv@webveda.com
To: "W. Mark Townsley" <townsley@cisco.com>
Cc: l2tp@ipsec.org
Date: Tue, 01 Aug 2000 15:55:23 +0600
Subject: Re: Proxy LCP and Authentication
X-Mailer: CWMail Web to Mail Gateway 2.5e, http://netwinsite.com/top_mail.htm
Message-id: <3987a296.66cc.0@webveda.com>
X-User-Info: 203.197.138.194
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

>> is there a option in cisco to disable proxy auth at the
>> LAC side?
>
>No.

is it advisable to provide a feature, in which the authentication at the LAC
can be disabled ? 

dont know what will be the use of such a feature,
but is it ok ?

does any implementation of LAC has such a feature ?

tia 
shankar
-------------------------------------------------
Make webveda your permanent address like i have.
Get 15 MB Free space only at http://www.webveda.com


From owner-l2tp@diameter.org  Tue Aug  1 09:58:47 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11836
	for <l2tpext-archive@odin.ietf.org>; Tue, 1 Aug 2000 09:58:46 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e71AXFM25464
	for l2tp-list; Tue, 1 Aug 2000 03:33:15 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e71AXCd25458
	for <l2tp@l2tp.net>; Tue, 1 Aug 2000 03:33:12 -0700
Received: from webveda.com (root@host-216-226-254-55.interpacket.net [216.226.254.55]) by ns1.sailpix.com (8.8.8/8.6.9) with SMTP id DAA02613 for <l2tp@ipsec.org>; Tue, 1 Aug 2000 03:37:09 -0700 (PDT)
Received: from webveda.com ([216.226.254.55]) by webveda.com ; Wed, 02 Aug 2000 00:35:58 -0400
From: "Shankar" <shankarv@webveda.com>
Reply-to: shankarv@webveda.com
To: l2tp@ipsec.org
Date: Tue, 01 Aug 2000 16:06:25 +0600
Subject: tunnel domain 
X-Mailer: CWMail Web to Mail Gateway 2.5e, http://netwinsite.com/top_mail.htm
Message-id: <3987a52e.6782.0@webveda.com>
X-User-Info: 203.197.138.194
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Hi folks,

what is a tunnel domain that is mentioned in the latest draft
mib for l2tp. rfc2661 has no reference to such a term.
can anyone help me where to find further info about this 
tunnel domain ?

tia
shankar
-------------------------------------------------
Make webveda your permanent address like i have.
Get 15 MB Free space only at http://www.webveda.com


From owner-l2tp@diameter.org  Tue Aug  1 10:20:28 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20179
	for <l2tpext-archive@odin.ietf.org>; Tue, 1 Aug 2000 10:20:26 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e71B0bB25491
	for l2tp-list; Tue, 1 Aug 2000 04:00:37 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from eins.siemens.at (eins.siemens.at [193.81.246.11])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e71B0Yd25485
	for <l2tp@l2tp.net>; Tue, 1 Aug 2000 04:00:34 -0700
Received: from scesie13.sie.siemens.at (forix-hme0 [10.1.140.2])
	by eins.siemens.at  with ESMTP id MAA18301;
	Tue, 1 Aug 2000 12:56:24 +0200 (MET DST)
Received: (from smap@localhost)
	by scesie13.sie.siemens.at (8.9.3/8.9.3) id NAA25142;
	Tue, 1 Aug 2000 13:04:25 +0200 (MET DST)
Received: from vies141a.sie.siemens.at(195.1.196.56) by scesie13 via smap (V2.0beta)
	id xma023765; Tue, 1 Aug 00 13:03:21 +0200
Received: by vies141a.sie.siemens.at with Internet Mail Service (5.5.2650.21)
	id <PVCTFFNN>; Tue, 1 Aug 2000 13:02:23 +0200
Message-ID: <D9F2B9CD7BD5D21196BC0800060D9ED601EFBEF8@vies186a.sie.siemens.at>
From: Klausberger Walter <walter.klausberger@siemens.at>
To: "'abickford@ipwireless.com'" <abickford@ipwireless.com>, l2tp@l2tp.net
Subject: AW: PPP Frames on tunnel
Date: Tue, 1 Aug 2000 13:02:22 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by charizard.diameter.org id e71B0Zd25486
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

Hi,

Well I don't see any contradiction in the replies of Mark and James. In my
opinion Mark states that FF 03 has to be added by LNS when sending packets
(unless ACFC is negotiated of course) and James says that FF03 must be added
to the tunneled frames (by the LNS).

I had similar questions about two years ago, when I stated that L2TP was too
much restricted to ISDN or modem access. The answer then was "Let's think
about that in a later extension, we want the draft to become RFC". Because
the LNSs in the fields would have to handle all types of framing (eg. Frame
Relay, ATM and so on) the whole thing was simply restricted to the
address/control field. This must be sent, because common PPP implementations
assume that this is a negotiable header for links over HDLC.

So a LAC having access over ATM, Frame Relay or even Ethernet has to be a
little bit intelligent to add and remove the address/control field.

Hope I'm not wrong
with best regards
Walter Klausberger
Siemens AG Austria 

-----Ursprüngliche Nachricht-----
Von: Andy Bickford [mailto:abickford@ipwireless.com]
Gesendet am: Dienstag, 01. August 2000 11:16
An: l2tp@l2tp.net
Betreff: Re: PPP Frames on tunnel

Hi folks,

Can anybody clarify the replies to Sridhar's question, as they appear to
contradict each other.

Hence what should be added to the PPP frames being sent from the LAC to
the LNS and the LNS to the LAC ?

How does the LAC/LNS distinguish between the FF 03 bytes that have been
added as extra bytes on entry to the tunnel and the real address and control
fields ?

Apologies if the questions have already been answered.

Best Regards

Andy Bickford
Technical Associate
IPWireless Inc


>Sridhar Malarothu wrote:
>
> Hi All,
>
>     LAC before sending ppp frames on tunnel to LAC should strip of
> the CRC, Link Framing and transperancy bytes, encapsulate them in L2TP
> header. But what should be status of the PPP frames on tunnel, if send
> by LNS.
>
> Best Regards
> Sridhar


>Mark Townsley's reply was:
>
>PPP framing of FF03, unless ACFC is negotiated, should exist on packets
>sent from the LNS and from the LAC.

>James Carlson's reply was:
>
>Data frames from the LNS should not have an appended CRC, framing, or
>transparency bytes, and they should have L2TP headers.
>
>Note that the leading FF 03 (the default values used for the HDLC Address
>and Control fields on regular PPP links) must be included on the tunneled
>frames, contrary to prior convention (such as described in RFCs 1598, 1973,
>and 2364). So, if you're coming from a regular PPP over Frame Relay network
>into an L2TP tunnel, you'll have to add those extra bytes on entry to the
>tunnel and remove them before going into Frame Relay.




From owner-l2tp@diameter.org  Tue Aug  1 13:13:06 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06729
	for <l2tpext-archive@odin.ietf.org>; Tue, 1 Aug 2000 13:13:05 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e71DwjF25808
	for l2tp-list; Tue, 1 Aug 2000 06:58:45 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from shako.cisco.com (shako.cisco.com [161.44.3.76])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e71Dwgd25802
	for <l2tp@l2tp.net>; Tue, 1 Aug 2000 06:58:42 -0700
Received: from cisco.com (sj-dial-2-173.cisco.com [10.19.226.174])
	by shako.cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id KAA06068;
	Tue, 1 Aug 2000 10:01:29 -0400 (EDT)
Message-ID: <3986D850.85045ED8@cisco.com>
Date: Tue, 01 Aug 2000 10:01:52 -0400
From: "W. Mark Townsley" <townsley@cisco.com>
X-Mailer: Mozilla 4.7 [en] (Win95; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: Klausberger Walter <walter.klausberger@siemens.at>
CC: "'abickford@ipwireless.com'" <abickford@ipwireless.com>, l2tp@l2tp.net
Subject: Re: AW: PPP Frames on tunnel
References: <D9F2B9CD7BD5D21196BC0800060D9ED601EFBEF8@vies186a.sie.siemens.at>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

Klausberger Walter wrote:
> 
> Hi,
> 
> Well I don't see any contradiction in the replies of Mark and James. In my
> opinion Mark states that FF 03 has to be added by LNS when sending packets
> (unless ACFC is negotiated of course) and James says that FF03 must be added
> to the tunneled frames (by the LNS).
> 
> I had similar questions about two years ago, when I stated that L2TP was too
> much restricted to ISDN or modem access. The answer then was "Let's think
> about that in a later extension, we want the draft to become RFC". Because

Given the obvious HDLC mindset of the day, there were valid arguments
for keeping the framing present of the tunneled packets --  For
instance, though not used so often today, RFC1663 requires the Address
and Control fields (for better or worse there was a lot of talk at the
time about making the data channel reliable... this was our way of
answering that request). Further, given the ability to negotiate away
the framing fields with ACFC, effectively adding another method to do so
in L2TP seemed a bit redundant. There could be other extensions to PPP
down the road that used these fields as well. I would say that there was
a certain amount of intrepidation about "backing ourselves into a
corner" by not requiring the framing to be sent, particularly given that
there was already an established way of getting rid of it via existing
PPP methods if desired.

With the increased usage of PPP over eth, ATM, FR, etc. together with
many LACs tunneling PPP without first stepping through LCP to determine
whether ACFC was negotiated, perhaps a "raw" framing type belongs in
l2tp-bis. I suspect that there are probably a handful of L2TP systems
that do not add or subtract the Address and Control fields properly now,
but PPP is resilient to the error. The reality is that most PPP
implementations are very forgiving of the presence of framing upon
receipt of a packet. 

> the LNSs in the fields would have to handle all types of framing (eg. Frame
> Relay, ATM and so on) the whole thing was simply restricted to the
> address/control field. This must be sent, because common PPP implementations
> assume that this is a negotiable header for links over HDLC.
> 
> So a LAC having access over ATM, Frame Relay or even Ethernet has to be a
> little bit intelligent to add and remove the address/control field.
> 
> Hope I'm not wrong
> with best regards
> Walter Klausberger
> Siemens AG Austria
> 
> -----Ursprüngliche Nachricht-----
> Von: Andy Bickford [mailto:abickford@ipwireless.com]
> Gesendet am: Dienstag, 01. August 2000 11:16
> An: l2tp@l2tp.net
> Betreff: Re: PPP Frames on tunnel
> 
> Hi folks,
> 
> Can anybody clarify the replies to Sridhar's question, as they appear to
> contradict each other.
> 
> Hence what should be added to the PPP frames being sent from the LAC to
> the LNS and the LNS to the LAC ?
> 
> How does the LAC/LNS distinguish between the FF 03 bytes that have been
> added as extra bytes on entry to the tunnel and the real address and control
> fields ?
> 
> Apologies if the questions have already been answered.
> 
> Best Regards
> 
> Andy Bickford
> Technical Associate
> IPWireless Inc
> 
> >Sridhar Malarothu wrote:
> >
> > Hi All,
> >
> >     LAC before sending ppp frames on tunnel to LAC should strip of
> > the CRC, Link Framing and transperancy bytes, encapsulate them in L2TP
> > header. But what should be status of the PPP frames on tunnel, if send
> > by LNS.
> >
> > Best Regards
> > Sridhar
> 
> >Mark Townsley's reply was:
> >
> >PPP framing of FF03, unless ACFC is negotiated, should exist on packets
> >sent from the LNS and from the LAC.
> 
> >James Carlson's reply was:
> >
> >Data frames from the LNS should not have an appended CRC, framing, or
> >transparency bytes, and they should have L2TP headers.
> >
> >Note that the leading FF 03 (the default values used for the HDLC Address
> >and Control fields on regular PPP links) must be included on the tunneled
> >frames, contrary to prior convention (such as described in RFCs 1598, 1973,
> >and 2364). So, if you're coming from a regular PPP over Frame Relay network
> >into an L2TP tunnel, you'll have to add those extra bytes on entry to the
> >tunnel and remove them before going into Frame Relay.


From owner-l2tp@diameter.org  Tue Aug  1 13:13:10 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06768
	for <l2tpext-archive@odin.ietf.org>; Tue, 1 Aug 2000 13:13:09 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e71EN3e25842
	for l2tp-list; Tue, 1 Aug 2000 07:23:03 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from ganymede.or.intel.com (ganymede.or.intel.com [134.134.248.3])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e71EN1d25836
	for <l2tp@l2tp.net>; Tue, 1 Aug 2000 07:23:01 -0700
Received: from SMTP (orsmsxvs02-1.jf.intel.com [192.168.65.201])
	by ganymede.or.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.30 2000/06/08 18:25:35 dmccart Exp $) with SMTP id HAA06533;
	Tue, 1 Aug 2000 07:26:43 -0700 (PDT)
Received: from orsmsx29.jf.intel.com ([192.168.70.29]) by 192.168.70.201
  (Norton AntiVirus for Internet Email Gateways 1.0) ;
  Tue, 01 Aug 2000 14:26:43 0000 (GMT)
Received: by orsmsx29.jf.intel.com with Internet Mail Service (5.5.2650.21)
	id <PY8F287Z>; Tue, 1 Aug 2000 07:26:41 -0700
Message-ID: <392A357CE6FFD111AC3E00A0C99848B00369501E@hdsmsx31.hd.intel.com>
From: "Shriver, John" <john.shriver@intel.com>
To: "'W. Mark Townsley'" <townsley@cisco.com>,
        Klausberger Walter
	 <walter.klausberger@siemens.at>
Cc: "'abickford@ipwireless.com'" <abickford@ipwireless.com>, l2tp@l2tp.net
Subject: RE: AW: PPP Frames on tunnel
Date: Tue, 1 Aug 2000 07:26:38 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-l2tp@diameter.org
Precedence: bulk

Let's be honest about why the Address and Control fields are there in PPP.
PPP was a grand compromise deal between Cisco, Proteon, ACC, Wellfleet (were
they there then?) and a few other early router vendors to have a consistent
data link.  None of the vendors were willing to redesign their hardware to
me compatible with PPP.  Someone was using a serial controller that was one
of those old "smart" X.25 controllers, and could not deal with packets not
having the address and control fields.  So they were made part of the
default standard configuration, but anyone not using that brain-dead chip
could negotiate it away.

Similarly, PPP allows link layer padding bytes because (at least) Cisco and
Proteon had boards that could only send packets of an even number of bytes.

Any arguments that the address and control fields on PPP were there for any
useful reason are completely specious.  Let's not reinvent history.

What's two bytes among friends.  Any header blows the 1500 byte frame...



From owner-l2tp@diameter.org  Tue Aug  1 15:00:22 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21306
	for <l2tpext-archive@odin.ietf.org>; Tue, 1 Aug 2000 15:00:21 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e71FYRq26245
	for l2tp-list; Tue, 1 Aug 2000 08:34:27 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from shako.cisco.com (shako.cisco.com [161.44.3.76])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e71FYNd26239
	for <l2tp@l2tp.net>; Tue, 1 Aug 2000 08:34:23 -0700
Received: from cisco.com (sj-dial-2-228.cisco.com [10.19.226.229])
	by shako.cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id LAA20652;
	Tue, 1 Aug 2000 11:37:04 -0400 (EDT)
Message-ID: <3986EEB7.990C840A@cisco.com>
Date: Tue, 01 Aug 2000 11:37:27 -0400
From: "W. Mark Townsley" <townsley@cisco.com>
X-Mailer: Mozilla 4.7 [en] (Win95; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: "Shriver, John" <john.shriver@intel.com>
CC: Klausberger Walter <walter.klausberger@siemens.at>,
        "'abickford@ipwireless.com'" <abickford@ipwireless.com>, l2tp@l2tp.net
Subject: Re: AW: PPP Frames on tunnel
References: <392A357CE6FFD111AC3E00A0C99848B00369501E@hdsmsx31.hd.intel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



"Shriver, John" wrote:
> 
> Let's be honest about why the Address and Control fields are there in PPP.
> PPP was a grand compromise deal between Cisco, Proteon, ACC, Wellfleet (were
> they there then?) and a few other early router vendors to have a consistent
> data link.  None of the vendors were willing to redesign their hardware to

Your PPP history certainly goes back further than mine, John. Thanks for
the lesson.

> me compatible with PPP.  Someone was using a serial controller that was one
> of those old "smart" X.25 controllers, and could not deal with packets not
> having the address and control fields.  So they were made part of the
> default standard configuration, but anyone not using that brain-dead chip
> could negotiate it away.
> 
> Similarly, PPP allows link layer padding bytes because (at least) Cisco and
> Proteon had boards that could only send packets of an even number of bytes.
> 
> Any arguments that the address and control fields on PPP were there for any
> useful reason are completely specious.  Let's not reinvent history.

This thread wasn't about why PPP Address and control fields are present
in PPP, but why they remained present on the tunnel. A tunneled PPP
frame terminated at an LNS does not utilize the serial chipsets you
refer to... It's all a virtual interface at that point. As far as
alignment of the PPP datagram, the L2TP offset can ensure that on the
tunneled packet.

The "back ourselves into a corner" comment was a quote (as I remember it
from a bakeoff long ago) from one of the original authors of the L2TP
spec... I am not trying to reinvent anything.

> 
> What's two bytes among friends.  Any header blows the 1500 byte frame...

True. One of the arguments given at the time and still somewhat valid
today. One catch is whether or not you know if you should tack on the
header. If the LAC did not go through LCP, short of snooping the
negotiation, it is impossible to know. The link-info draft would solve
this, but no one has implemented it that I know of. As would an
additional framing type. The prudent thing to do these days would be to
always tack on the framing as PPP can handle the FF03 whether ACFC was
negotiated or not.

- Mark


From owner-l2tp@diameter.org  Tue Aug  1 15:13:36 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22864
	for <l2tpext-archive@odin.ietf.org>; Tue, 1 Aug 2000 15:13:35 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e71FxtJ26277
	for l2tp-list; Tue, 1 Aug 2000 08:59:55 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from thalia.fm.intel.com (thalia.fm.intel.com [132.233.247.11])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e71Fxrd26271
	for <l2tp@l2tp.net>; Tue, 1 Aug 2000 08:59:53 -0700
Received: from SMTP (fmsmsxvs01-1.fm.intel.com [132.233.42.201])
	by thalia.fm.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.30 2000/06/08 18:25:35 dmccart Exp $) with SMTP id QAA10144;
	Tue, 1 Aug 2000 16:04:33 GMT
Received: from fmsmsx17.intel.com ([132.233.48.17]) by 132.233.48.201
  (Norton AntiVirus for Internet Email Gateways 1.0) ;
  Tue, 01 Aug 2000 16:03:36 0000 (GMT)
Received: by fmsmsx17.fm.intel.com with Internet Mail Service (5.5.2650.21)
	id <PT8B2R0F>; Tue, 1 Aug 2000 09:03:34 -0700
Message-ID: <392A357CE6FFD111AC3E00A0C99848B003695021@hdsmsx31.hd.intel.com>
From: "Shriver, John" <john.shriver@intel.com>
To: "'W. Mark Townsley'" <townsley@cisco.com>
Cc: Klausberger Walter <walter.klausberger@siemens.at>,
        "'abickford@ipwireless.com'" <abickford@ipwireless.com>, l2tp@l2tp.net
Subject: RE: AW: PPP Frames on tunnel
Date: Tue, 1 Aug 2000 09:00:34 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-l2tp@diameter.org
Precedence: bulk

I think that the address and control fields remain present on the tunnel
because L2TP inherited the "very dumb LAC" model from the PPTP PAC.  In
PPTP, the PAC never participated in PPP at the LCP layer or higher, it was a
modem bank that understood HDLC framing (sync or async) and nothing more.
This is still one of the two modes of L2TP.

L2TP is not an ideal standard, it was a political compromise between Cisco
(L2F) and Microsoft (PPTP).  This was one of Microsoft's "design wins" in
the merged protocol.

I know that the IETF doesn't like to think that their protocols are designed
on a political basis, but it happens, but normally in less explicit ways.
It happened in L2TP, and it happend (back-room) in PPP.

(I'll admit that I haven't been following the full thread, and will sign off
this discussion now.)



From owner-l2tp@diameter.org  Tue Aug  1 15:33:11 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25072
	for <l2tpext-archive@odin.ietf.org>; Tue, 1 Aug 2000 15:33:10 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e71GJB926319
	for l2tp-list; Tue, 1 Aug 2000 09:19:11 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e71GJ7d26313
	for <l2tp@l2tp.net>; Tue, 1 Aug 2000 09:19:07 -0700
Received: from antares.trt20.gov.br (root@antares.trt20.gov.br.49.241.200.in-addr.arpa [200.241.49.11] (may be forged)) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id JAA02910 for <l2tp@ipsec.org>; Tue, 1 Aug 2000 09:23:01 -0700 (PDT)
Received: from FABIO ([200.241.49.205])
	by antares.trt20.gov.br (8.9.3/8.8.7) with SMTP id OAA28022;
	Tue, 1 Aug 2000 14:29:53 -0300
Message-ID: <023b01bffbd5$01d16850$cd0100c0@FABIO>
From: =?iso-8859-1?Q?F=E1bio_Santana_Bispo?= <fabio@trt20.gov.br>
To: <l2tp@ipsec.org>, <ietf-ppp@merit.edu>, <ipsec@lists.tislabs.com>,
        "Anita Freeman" <anfreema@cisco.com>
References: <200007312319.QAA14257@mailman.cisco.com>
Subject: Re: Update for Sept 2000 VPN Interoperability Workshop
Date: Tue, 1 Aug 2000 13:24:46 -0300
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0238_01BFFBBB.DC6ED390"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Sender: owner-l2tp@diameter.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_0238_01BFFBBB.DC6ED390
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hello,

    I will make a work about VPN and maybe implement one. I want to know =
the best book about VPN and sites that talk about it.

Thanks

F=E1bio
  ----- Original Message -----=20
  From: Anita Freeman=20
  To: l2tp@ipsec.org ; ietf-ppp@merit.edu ; ipsec@lists.tislabs.com=20
  Sent: Sunday, July 30, 2000 8:18 PM
  Subject: Update for Sept 2000 VPN Interoperability Workshop


  First a reminder to make your hotel reservations for the VPN =
Interoperability Workshop, September 18-22, 2000 at the Paradise Point =
Resort in San Diego, California. The reservation number is 800-344-2626. =
Please register under the VPN Workshop room block for the discounted =
rate of $159 per night (plus tax). The cutoff date for this room block =
is August 15th. There are a few modifications to the application and =
schedule for the September 2000 VPN Workshop. The application for the =
workshop has been moved to a new server and is now available at: =
http://209.249.66.84/vpnworkshop/ On Tuesday evening, September 19, =
2000, the California Broadband User's Group will sponsor an appreciation =
event for the workshop attendees. At 7 PM we will board a Sternwheeler, =
the William D. Evans, at the Bahia Resort Hotel for a two hour cocktail =
cruise in San Diego's Mission Bay. The cruise will replace the reception =
originally scheduled for September 20, 2000. The VPN Workshop is being =
sponsored by VeriSign, SSH, Hi/fn, WindRiver, Entrust, Nokia, Alcatel, =
RedBack, Microsoft, Cisco, and UUNET, a Worldcom Company. The protocols =
being tested at this workshop are: IPsec IKE IPComp L2TP over =
Transport-Mode IPsec PPTP PPPoE PPPoATM L2TPoATM Thanks, Anita Freeman=20

------=_NextPart_000_0238_01BFFBBB.DC6ED390
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2920.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hello,</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp;&nbsp; I will make a work =
about VPN and=20
maybe implement one. I want to know the best book about VPN and sites =
that talk=20
about it.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Thanks</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>F=E1bio</FONT></DIV>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #000000 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: =
0px; PADDING-LEFT: 5px; PADDING-RIGHT: 0px">
  <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV=20
  style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
  <A href=3D"mailto:anfreema@cisco.com" title=3Danfreema@cisco.com>Anita =
Freeman</A>=20
  </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
href=3D"mailto:l2tp@ipsec.org"=20
  title=3Dl2tp@ipsec.org>l2tp@ipsec.org</A> ; <A =
href=3D"mailto:ietf-ppp@merit.edu"=20
  title=3Dietf-ppp@merit.edu>ietf-ppp@merit.edu</A> ; <A=20
  href=3D"mailto:ipsec@lists.tislabs.com"=20
  title=3Dipsec@lists.tislabs.com>ipsec@lists.tislabs.com</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Sunday, July 30, 2000 =
8:18 PM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> Update for Sept 2000 =
VPN=20
  Interoperability Workshop</DIV>
  <DIV><BR></DIV>First a reminder to make your hotel reservations for =
the VPN=20
  Interoperability Workshop, September 18-22, 2000 at the Paradise Point =
Resort=20
  in San Diego, California. The reservation number is 800-344-2626. =
Please=20
  register under the VPN Workshop room block for the discounted rate of =
$159 per=20
  night (plus tax). The cutoff date for this room block is August 15th. =
There=20
  are a few modifications to the application and schedule for the =
September 2000=20
  VPN Workshop. The application for the workshop has been moved to a new =
server=20
  and is now available at: http://209.249.66.84/vpnworkshop/ On Tuesday =
evening,=20
  September 19, 2000, the California Broadband User's Group will sponsor =
an=20
  appreciation event for the workshop attendees. At 7 PM we will board a =

  Sternwheeler, the William D. Evans, at the Bahia Resort Hotel for a =
two hour=20
  cocktail cruise in San Diego's Mission Bay. The cruise will replace =
the=20
  reception originally scheduled for September 20, 2000. The VPN =
Workshop is=20
  being sponsored by VeriSign, SSH, Hi/fn, WindRiver, Entrust, Nokia, =
Alcatel,=20
  RedBack, Microsoft, Cisco, and UUNET, a Worldcom Company. The =
protocols being=20
  tested at this workshop are: IPsec IKE IPComp L2TP over Transport-Mode =
IPsec=20
  PPTP PPPoE PPPoATM L2TPoATM Thanks, Anita Freeman =
</BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0238_01BFFBBB.DC6ED390--



From owner-l2tp@diameter.org  Tue Aug  1 15:33:35 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25124
	for <l2tpext-archive@odin.ietf.org>; Tue, 1 Aug 2000 15:33:34 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e71FwFK26268
	for l2tp-list; Tue, 1 Aug 2000 08:58:15 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from drawbridge.ascend.com (drawbridge.ascend.com [198.4.92.1])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e71FwCd26262
	for <l2tp@l2tp.net>; Tue, 1 Aug 2000 08:58:12 -0700
Received: from fw-ext.ascend.com (fw-ext [198.4.92.5])
	by drawbridge.ascend.com (8.9.1a/8.9.1) with SMTP id IAA02380;
	Tue, 1 Aug 2000 08:54:30 -0700 (PDT)
Received: from russet.ascend.com by fw-ext.ascend.com
          via smtpd (for drawbridge.ascend.com [198.4.92.1]) with SMTP; 1 Aug 2000 16:01:56 UT
Received: from wopr.eng.ascend.com (wopr.eng.ascend.com [206.65.212.178])
	by russet.ascend.com (8.9.1a/8.9.1) with ESMTP id JAA12353;
	Tue, 1 Aug 2000 09:01:55 -0700 (PDT)
Received: from scamp.eng.ascend.com (scamp.eng.ascend.com [135.140.53.42])
	by wopr.eng.ascend.com (8.9.1/8.9.1) with ESMTP id JAA29456;
	Tue, 1 Aug 2000 09:01:56 -0700 (PDT)
Received: from igoyret-pc.eng.ascend.com by scamp.eng.ascend.com (8.8.8+Sun/SMI-SVR4)
	id JAA25728; Tue, 1 Aug 2000 09:01:54 -0700 (PDT)
Message-Id: <3.0.5.32.20000801090253.03da8660@scamp.eng.ascend.com>
X-Sender: igoyret@scamp.eng.ascend.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32)
Date: Tue, 01 Aug 2000 09:02:53 -0700
To: "W. Mark Townsley" <townsley@cisco.com>
From: Ignacio Goyret <igoyret@lucent.com>
Subject: Re: AW: PPP Frames on tunnel
Cc: "Shriver, John" <john.shriver@intel.com>,
        Klausberger Walter <walter.klausberger@siemens.at>,
        "'abickford@ipwireless.com'" <abickford@ipwireless.com>, l2tp@l2tp.net
In-Reply-To: <3986EEB7.990C840A@cisco.com>
References: <392A357CE6FFD111AC3E00A0C99848B00369501E@hdsmsx31.hd.intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-l2tp@diameter.org
Precedence: bulk

At 11:37 AM 8/1/00 -0400, W. Mark Townsley wrote:
>The prudent thing to do these days would be to
>always tack on the framing as PPP can handle the FF03 whether ACFC was
>negotiated or not.

... unless the packet in question already has the FF03. Otherwise, you can
end up with FF03FF03002145.... which PPP will have a hard time dealing with.




From owner-l2tp@diameter.org  Tue Aug  1 15:37:03 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25521
	for <l2tpext-archive@odin.ietf.org>; Tue, 1 Aug 2000 15:37:02 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e71G6pF26297
	for l2tp-list; Tue, 1 Aug 2000 09:06:51 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e71G6md26291
	for <l2tp@l2tp.net>; Tue, 1 Aug 2000 09:06:48 -0700
Received: from center.mshindo.net (center.mshindo.net [210.231.221.221]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id JAA02901 for <l2tp@ipsec.org>; Tue, 1 Aug 2000 09:10:45 -0700 (PDT)
Received: from cosinecom.com (E175151.dion.ne.jp [210.238.175.151])
	by center.mshindo.net (8.9.3/3.7W/00041811) with SMTP id BAA75975;
	Wed, 2 Aug 2000 01:14:15 +0900 (JST)
Date: Wed, 02 Aug 2000 01:11:15 +0900 (JST)
Message-Id: <20000802.011115.74755573.mshindo@cosinecom.com>
To: shankarv@webveda.com
Cc: townsley@cisco.com, l2tp@ipsec.org
Subject: Re: Proxy LCP and Authentication
From: Motonori Shindo <mshindo@cosinecom.com>
In-Reply-To: <3987a296.66cc.0@webveda.com>
References: <3987a296.66cc.0@webveda.com>
X-Mailer: Mew version 1.95b30 on XEmacs 21.1 (Canyonlands)
X-PGP-fingerprint: 06 B0 B1 A4 06 C1 6A 14  63 C0 D7 18 01 CD D9 83
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Shankar,

From: "Shankar" <shankarv@webveda.com>
Subject: Re: Proxy LCP and Authentication
Date: Tue, 01 Aug 2000 15:55:23 +0600

> >> is there a option in cisco to disable proxy auth at the
> >> LAC side?
> >
> >No.
> 
> is it advisable to provide a feature, in which the authentication at the LAC
> can be disabled ? 

Sending proxy lcp/auth doesn't really harm anything (except for a
little bit of overhead in traffic-wise). It's usually up to the LNS
whether it will use such information or not. Even when the LNS
receives a proxy lcp/auth from the LAC, LNS may still renegotiate
lcp/auth all over again.

> dont know what will be the use of such a feature,
> but is it ok ?

Controlling such a thing at the LAC won't break the protocol, but I
see little usefullness.

> does any implementation of LAC has such a feature ?

I haven't seen such a software/hardware so far.

=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=
 +----+----+     
 |.. .|    |     Motonori Shindo
 |_~__|    |     
 | .. |~~_~|     Sr. Systems Engineer
 | .  |    |     CoSine Communications Inc.
 +----+----+     
 C o S i n e     e-mail:  mshindo@cosinecom.com 
Communications
=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=



From owner-l2tp@diameter.org  Tue Aug  1 16:48:52 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04454
	for <l2tpext-archive@odin.ietf.org>; Tue, 1 Aug 2000 16:48:50 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e71GD2C26309
	for l2tp-list; Tue, 1 Aug 2000 09:13:02 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from zev.net (zev.net [206.111.135.146])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e71GCwd26303
	for <l2tp@l2tp.net>; Tue, 1 Aug 2000 09:12:58 -0700
Received: from zev.net (localhost.zev.net [127.0.0.1] (may be forged))
	by zev.net (8.9.3/8.9.3) with ESMTP id JAA03349;
	Tue, 1 Aug 2000 09:12:32 -0700 (PDT)
Message-Id: <200008011612.JAA03349@zev.net>
To: "Shriver, John" <john.shriver@intel.com>
cc: "'W. Mark Townsley'" <townsley@cisco.com>,
        Klausberger Walter <walter.klausberger@siemens.at>,
        "'abickford@ipwireless.com'" <abickford@ipwireless.com>, l2tp@l2tp.net
Subject: Re: AW: PPP Frames on tunnel 
In-reply-to: Your message of "Tue, 01 Aug 2000 09:00:34 PDT."
             <392A357CE6FFD111AC3E00A0C99848B003695021@hdsmsx31.hd.intel.com> 
Date: Tue, 01 Aug 2000 09:12:32 -0700
From: Bill Palter <palter@zev.net>
Sender: owner-l2tp@diameter.org
Precedence: bulk

> I think that the address and control fields remain present on the tunnel
> because L2TP inherited the "very dumb LAC" model from the PPTP PAC.  In
> PPTP, the PAC never participated in PPP at the LCP layer or higher, it was a
> modem bank that understood HDLC framing (sync or async) and nothing more.
> This is still one of the two modes of L2TP.
> 
> L2TP is not an ideal standard, it was a political compromise between Cisco
> (L2F) and Microsoft (PPTP).  This was one of Microsoft's "design wins" in
> the merged protocol.
> 

  L2F also had the FF03 field present, but for different reasons....So it
wasn't so much a compromise as something that was the same that no one saw 
the need to change. When the desire to change it came up, we had already 
shown interoperability at 2 bakeoffs so we din't want to change it that late 
in the game (of course, as it turned out there would have been plenty of time
to change it)...

> I know that the IETF doesn't like to think that their protocols are designed
> on a political basis, but it happens, but normally in less explicit ways.
> It happened in L2TP, and it happend (back-room) in PPP.
> 
> (I'll admit that I haven't been following the full thread, and will sign off
> this discussion now.)
--
Bill Palter (Palter@zev.net)


From owner-l2tp@diameter.org  Tue Aug  1 17:23:03 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA08864
	for <l2tpext-archive@odin.ietf.org>; Tue, 1 Aug 2000 17:23:02 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e71HXYu26416
	for l2tp-list; Tue, 1 Aug 2000 10:33:34 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e71HXVd26410
	for <l2tp@l2tp.net>; Tue, 1 Aug 2000 10:33:31 -0700
Received: from dfw-smtpout3.email.verio.net (dfw-smtpout3.email.verio.net [129.250.36.43]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id KAA03058 for <l2tp@ipsec.org>; Tue, 1 Aug 2000 10:37:29 -0700 (PDT)
Received: from [129.250.38.64] (helo=dfw-mmp4.email.verio.net)
	by dfw-smtpout3.email.verio.net with esmtp (Exim 3.12 #7)
	id 13Jfyp-0001ZN-00; Tue, 01 Aug 2000 17:37:27 +0000
Received: from [209.21.27.82] (helo=rapid5.com)
	by dfw-mmp4.email.verio.net with esmtp (Exim 3.15 #4)
	id 13Jfyo-0003hl-00; Tue, 01 Aug 2000 17:37:26 +0000
Received: from srik (dell_pc12 [10.1.1.143])
	by rapid5.com (8.9.1b+Sun/8.8.8) with SMTP id KAA02944;
	Tue, 1 Aug 2000 10:37:24 -0700 (PDT)
From: "Srikrishnan Subramanian" <srikrish@rapid5.com>
To: <shankarv@webveda.com>, <l2tp@ipsec.org>
Subject: RE: tunnel domain 
Date: Tue, 1 Aug 2000 10:41:24 -0700
Message-ID: <NDBBJPNHOLJCLNDHELHBGEPECBAA.srikrish@rapid5.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
In-Reply-To: <3987a52e.6782.0@webveda.com>
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

hi shankar,

   Tunnel Domain, according to my understanding is logical thing
   used while configuring L2TP in a system.

   Group of tunnels with similar characterisitcs can be defined
   under one domain.

   For ex: All tunnels (if there are multiple tunnels) going to
   one LNS can be defined under that particular LNS domain name.

   It has nothing to do with protocol as such. Thatz the reason
   you're not seeing them in RFC2661

   Hope this helps

Regards
Srikrishnan

-----Original Message-----
From: owner-l2tp@diameter.org [mailto:owner-l2tp@diameter.org]On Behalf
Of Shankar
Sent: Tuesday, August 01, 2000 3:06 AM
To: l2tp@ipsec.org
Subject: tunnel domain 



Hi folks,

what is a tunnel domain that is mentioned in the latest draft
mib for l2tp. rfc2661 has no reference to such a term.
can anyone help me where to find further info about this 
tunnel domain ?

tia
shankar
-------------------------------------------------
Make webveda your permanent address like i have.
Get 15 MB Free space only at http://www.webveda.com



From owner-l2tp@diameter.org  Tue Aug  1 17:25:47 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09204
	for <l2tpext-archive@odin.ietf.org>; Tue, 1 Aug 2000 17:25:46 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e71GvJt26372
	for l2tp-list; Tue, 1 Aug 2000 09:57:19 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e71GvGd26366
	for <l2tp@l2tp.net>; Tue, 1 Aug 2000 09:57:16 -0700
Received: from eastmail1.East.Sun.COM ([129.148.1.240])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id LAA04479;
	Tue, 1 Aug 2000 11:01:07 -0600 (MDT)
Received: from phorcys.east.sun.com (phorcys.East.Sun.COM [129.148.174.143])
	by eastmail1.East.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id NAA13383;
	Tue, 1 Aug 2000 13:01:06 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.9.3+Sun/8.9.3) id NAA26695;
	Tue, 1 Aug 2000 13:01:08 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14727.596.182509.474813@gargle.gargle.HOWL>
Date: Tue, 1 Aug 2000 13:01:08 -0400 (EDT)
From: James Carlson <james.d.carlson@east.sun.com>
To: "Shriver, John" <john.shriver@intel.com>
Cc: "'W. Mark Townsley'" <townsley@cisco.com>,
        Klausberger Walter
	 <walter.klausberger@siemens.at>,
        "'abickford@ipwireless.com'" <abickford@ipwireless.com>, l2tp@l2tp.net
Subject: RE: AW: PPP Frames on tunnel
In-Reply-To: Shriver, John's message of 1 August 2000 07:26:38
References: <392A357CE6FFD111AC3E00A0C99848B00369501E@hdsmsx31.hd.intel.com>
X-Mailer: VM 6.75 under Emacs 20.7.1
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Shriver, John writes:
> Let's be honest about why the Address and Control fields are there in PPP.

That's true for the reason HDLC fields are there in the default
encapsulation of PPP over simple point-to-point links, but this does
nothing to explain the need for those fields over tunnels.  Indeed,
there's much more precedent to assert that PPP should *NOT* include
these fields.  That they're present in L2TP is an anomaly.

The RFC 1663 argument doesn't work so well for me, either.  LAP-B
can't tolerate reordering and (generally) only makes the end-to-end
loss problems with L2TP *worse*.  Delaying all flows because the
tunnel itself is experiencing congestion only increases the amount of
useless retransmission at the transport layer and lowers performance.
If you do run 1663, you ought to be terminating the LAP-B session at
the LAC and not carrying it across the tunnel, but there's
unfortunately no draft that describes how or why to do this.  (Of
course, this also implies that the present mechanism that transports
LCP transparently from the LNS isn't right, either.)

> Any arguments that the address and control fields on PPP were there for any
> useful reason are completely specious.  Let's not reinvent history.

It's not reinventing history to say that the PPP frame has been
traditionally taken to be the PPP Protocol and Information fields
alone, exclusive of HDLC Address, Control, and FCS.  See RFCs 1598,
1973, 2363, and 2364.  See also the definition of the PPP MRU in 1661.
That L2TP does it differently is not a feature, but a bug.

We got here by market forces, not so much by deliberate action.

-- 
James Carlson, Internet Engineering       <james.d.carlson@east.sun.com>
SUN Microsystems / 1 Network Drive         71.234W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.497N   Fax +1 781 442 1677
"PPP Design and Debugging" --- http://people.ne.mediaone.net/carlson/ppp


From owner-l2tp@diameter.org  Tue Aug  1 19:25:05 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA03918
	for <l2tpext-archive@odin.ietf.org>; Tue, 1 Aug 2000 19:25:04 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e71K5I426676
	for l2tp-list; Tue, 1 Aug 2000 13:05:18 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from shako.cisco.com (shako.cisco.com [161.44.3.76])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e71K5Fd26670
	for <l2tp@l2tp.net>; Tue, 1 Aug 2000 13:05:15 -0700
Received: from cisco.com (rtp-dial-1-248.cisco.com [10.83.97.248])
	by shako.cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id QAA29427;
	Tue, 1 Aug 2000 16:07:18 -0400 (EDT)
Message-ID: <39872E0C.A0F72926@cisco.com>
Date: Tue, 01 Aug 2000 16:07:40 -0400
From: "W. Mark Townsley" <townsley@cisco.com>
X-Mailer: Mozilla 4.7 [en] (Win95; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: James Carlson <james.d.carlson@east.sun.com>
CC: "Shriver, John" <john.shriver@intel.com>,
        Klausberger Walter <walter.klausberger@siemens.at>,
        "'abickford@ipwireless.com'" <abickford@ipwireless.com>, l2tp@l2tp.net
Subject: Re: AW: PPP Frames on tunnel
References: <392A357CE6FFD111AC3E00A0C99848B00369501E@hdsmsx31.hd.intel.com> <14727.596.182509.474813@gargle.gargle.HOWL>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



James Carlson wrote:
> 
> Shriver, John writes:
> > Let's be honest about why the Address and Control fields are there in PPP.
> 
> That's true for the reason HDLC fields are there in the default
> encapsulation of PPP over simple point-to-point links, but this does
> nothing to explain the need for those fields over tunnels.  Indeed,
> there's much more precedent to assert that PPP should *NOT* include
> these fields.  That they're present in L2TP is an anomaly.
> 
> The RFC 1663 argument doesn't work so well for me, either.  LAP-B
> can't tolerate reordering and (generally) only makes the end-to-end
> loss problems with L2TP *worse*.  Delaying all flows because the
> tunnel itself is experiencing congestion only increases the amount of
> useless retransmission at the transport layer and lowers performance.

Precisely the reason Flow Control was removed from L2TP. Something that
was admittedly difficult given the precedence in PPTP. 

I wasn't necessarily recommending use of 1663, just stating for the
record some of the arguments from the time. 

> If you do run 1663, you ought to be terminating the LAP-B session at
> the LAC and not carrying it across the tunnel, but there's
> unfortunately no draft that describes how or why to do this.  (Of
> course, this also implies that the present mechanism that transports
> LCP transparently from the LNS isn't right, either.)
> 
> > Any arguments that the address and control fields on PPP were there for any
> > useful reason are completely specious.  Let's not reinvent history.
> 
> It's not reinventing history to say that the PPP frame has been
> traditionally taken to be the PPP Protocol and Information fields
> alone, exclusive of HDLC Address, Control, and FCS.  See RFCs 1598,
> 1973, 2363, and 2364.  See also the definition of the PPP MRU in 1661.
> That L2TP does it differently is not a feature, but a bug.
> 
> We got here by market forces, not so much by deliberate action.
> 
> --
> James Carlson, Internet Engineering       <james.d.carlson@east.sun.com>
> SUN Microsystems / 1 Network Drive         71.234W   Vox +1 781 442 2084
> MS UBUR02-212 / Burlington MA 01803-2757   42.497N   Fax +1 781 442 1677
> "PPP Design and Debugging" --- http://people.ne.mediaone.net/carlson/ppp


From owner-l2tp@diameter.org  Wed Aug  2 09:06:46 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03293
	for <l2tpext-archive@odin.ietf.org>; Wed, 2 Aug 2000 09:06:45 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e7291cS27200
	for l2tp-list; Wed, 2 Aug 2000 02:01:38 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from pmr-linux.flowpoint.com (host233.yagosys.com [207.135.89.233])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e7291ad27194
	for <l2tp@l2tp.net>; Wed, 2 Aug 2000 02:01:36 -0700
Received: from localhost (pmr@localhost)
	by pmr-linux.flowpoint.com (8.9.3/8.9.3) with ESMTP id CAA19434;
	Wed, 2 Aug 2000 02:04:22 -0700
X-Authentication-Warning: pmr-linux.flowpoint.com: pmr owned process doing -bs
Date: Wed, 2 Aug 2000 02:04:22 -0700 (PDT)
From: "P. Rakity" <pmr@flowpoint.com>
To: "Shriver, John" <john.shriver@intel.com>
cc: "'W. Mark Townsley'" <townsley@cisco.com>,
        Klausberger Walter <walter.klausberger@siemens.at>,
        "'abickford@ipwireless.com'" <abickford@ipwireless.com>, l2tp@l2tp.net
Subject: RE: AW: PPP Frames on tunnel
In-Reply-To: <392A357CE6FFD111AC3E00A0C99848B003695021@hdsmsx31.hd.intel.com>
Message-ID: <Pine.LNX.4.21.0008020202130.19412-100000@pmr-linux.flowpoint.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-l2tp@diameter.org
Precedence: bulk


Folks,

At one of the early bake-off's we suggested changing the frame format to
not have the FF 03.  This change could not be done

a) because the rfc was moments from being published 
b) there we exisiting working implementations.

The reality was b) was certainly true and a) took another year.

regards,

Philip


On Tue, 1 Aug 2000, Shriver, John wrote:

> I think that the address and control fields remain present on the tunnel
> because L2TP inherited the "very dumb LAC" model from the PPTP PAC.  In
> PPTP, the PAC never participated in PPP at the LCP layer or higher, it was a
> modem bank that understood HDLC framing (sync or async) and nothing more.
> This is still one of the two modes of L2TP.
> 
> L2TP is not an ideal standard, it was a political compromise between Cisco
> (L2F) and Microsoft (PPTP).  This was one of Microsoft's "design wins" in
> the merged protocol.
> 
> I know that the IETF doesn't like to think that their protocols are designed
> on a political basis, but it happens, but normally in less explicit ways.
> It happened in L2TP, and it happend (back-room) in PPP.
> 
> (I'll admit that I haven't been following the full thread, and will sign off
> this discussion now.)
> 

-- 
----------------------------------------------------------------------------
Efficient Networks
5200 Great America Parkway
Santa Clara, CA 95054-1108

prakity@efficient.com
(408) 878-6825 (Direct)
(408) 878-6800 (Main)
(408) 878-6801 (Fax)




From owner-l2tp@diameter.org  Wed Aug  2 11:44:10 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28606
	for <l2tpext-archive@odin.ietf.org>; Wed, 2 Aug 2000 11:44:09 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e72CYnK27458
	for l2tp-list; Wed, 2 Aug 2000 05:34:49 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from shako.cisco.com (shako.cisco.com [161.44.3.76])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e72CYbd27452
	for <l2tp@l2tp.net>; Wed, 2 Aug 2000 05:34:39 -0700
Received: from cisco.com (sj-dial-2-215.cisco.com [10.19.226.216])
	by shako.cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id IAA13766;
	Wed, 2 Aug 2000 08:37:15 -0400 (EDT)
Message-ID: <39881612.CAD24264@cisco.com>
Date: Wed, 02 Aug 2000 08:37:38 -0400
From: "W. Mark Townsley" <townsley@cisco.com>
X-Mailer: Mozilla 4.7 [en] (Win95; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: "P. Rakity" <pmr@flowpoint.com>
CC: "Shriver, John" <john.shriver@intel.com>,
        Klausberger Walter <walter.klausberger@siemens.at>,
        "'abickford@ipwireless.com'" <abickford@ipwireless.com>, l2tp@l2tp.net
Subject: Re: AW: PPP Frames on tunnel
References: <Pine.LNX.4.21.0008020202130.19412-100000@pmr-linux.flowpoint.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



"P. Rakity" wrote:
> 
> Folks,
> 
> At one of the early bake-off's we suggested changing the frame format to
> not have the FF 03.  This change could not be done
> 
> a) because the rfc was moments from being published
> b) there we exisiting working implementations.
> 
> The reality was b) was certainly true and a) took another year.
> 

These were certainly two strong arguments. Two that we all remember
well. I am definitely not challenging that. 

The other reasons that I stated at the beginning of this thread were
some that were sited at the time *in addition* to these. Nothing more.

> regards,
> 
> Philip
> 
> On Tue, 1 Aug 2000, Shriver, John wrote:
> 
> > I think that the address and control fields remain present on the tunnel
> > because L2TP inherited the "very dumb LAC" model from the PPTP PAC.  In
> > PPTP, the PAC never participated in PPP at the LCP layer or higher, it was a
> > modem bank that understood HDLC framing (sync or async) and nothing more.
> > This is still one of the two modes of L2TP.
> >
> > L2TP is not an ideal standard, it was a political compromise between Cisco
> > (L2F) and Microsoft (PPTP).  This was one of Microsoft's "design wins" in
> > the merged protocol.
> >
> > I know that the IETF doesn't like to think that their protocols are designed
> > on a political basis, but it happens, but normally in less explicit ways.
> > It happened in L2TP, and it happend (back-room) in PPP.
> >
> > (I'll admit that I haven't been following the full thread, and will sign off
> > this discussion now.)
> >
> 
> --
> ----------------------------------------------------------------------------
> Efficient Networks
> 5200 Great America Parkway
> Santa Clara, CA 95054-1108
> 
> prakity@efficient.com
> (408) 878-6825 (Direct)
> (408) 878-6800 (Main)
> (408) 878-6801 (Fax)


From owner-l2tp@diameter.org  Wed Aug  2 13:08:53 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27507
	for <l2tpext-archive@odin.ietf.org>; Wed, 2 Aug 2000 13:08:53 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e72E9sL27645
	for l2tp-list; Wed, 2 Aug 2000 07:09:54 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from shako.cisco.com (shako.cisco.com [161.44.3.76])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e72E9pd27639
	for <l2tp@l2tp.net>; Wed, 2 Aug 2000 07:09:51 -0700
Received: from cisco.com (sj-dial-2-116.cisco.com [10.19.226.117])
	by shako.cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id KAA23978;
	Wed, 2 Aug 2000 10:12:28 -0400 (EDT)
Message-ID: <398742E6.88F70C5B@cisco.com>
Date: Tue, 01 Aug 2000 17:36:38 -0400
From: "W. Mark Townsley" <townsley@cisco.com>
X-Mailer: Mozilla 4.7 [en] (Win95; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: "Shriver, John" <john.shriver@intel.com>
CC: Klausberger Walter <walter.klausberger@siemens.at>,
        "'abickford@ipwireless.com'" <abickford@ipwireless.com>, l2tp@l2tp.net
Subject: Re: AW: PPP Frames on tunnel
References: <392A357CE6FFD111AC3E00A0C99848B003695021@hdsmsx31.hd.intel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



"Shriver, John" wrote:
> 
> I think that the address and control fields remain present on the tunnel
> because L2TP inherited the "very dumb LAC" model from the PPTP PAC.  In
> PPTP, the PAC never participated in PPP at the LCP layer or higher, it was a
> modem bank that understood HDLC framing (sync or async) and nothing more.
> This is still one of the two modes of L2TP.

Yes. Not removing FF03 allowed the LAC to be a dumb bridge for HDLC, a
significant design constraint at the time. The question now is whether
we should force non-HDLC PPP LACs to be 'smart' and make the tunneled
frames look like they came from an HDLC device regardless. 

> 
> L2TP is not an ideal standard, it was a political compromise between Cisco
> (L2F) and Microsoft (PPTP).  This was one of Microsoft's "design wins" in
> the merged protocol.

The fact that both L2F and PPTP came up with the same result was
certainly signficant in the design (or merging) of L2TP. 

> 
> I know that the IETF doesn't like to think that their protocols are designed
> on a political basis, but it happens, but normally in less explicit ways.
> It happened in L2TP, and it happend (back-room) in PPP.
> 
> (I'll admit that I haven't been following the full thread, and will sign off
> this discussion now.)




From owner-l2tp@diameter.org  Wed Aug  2 13:16:28 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00154
	for <l2tpext-archive@odin.ietf.org>; Wed, 2 Aug 2000 13:16:27 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e72EAOU27655
	for l2tp-list; Wed, 2 Aug 2000 07:10:24 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from shako.cisco.com (shako.cisco.com [161.44.3.76])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e72EALd27649
	for <l2tp@l2tp.net>; Wed, 2 Aug 2000 07:10:21 -0700
Received: from cisco.com (sj-dial-2-116.cisco.com [10.19.226.117])
	by shako.cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id KAA23909;
	Wed, 2 Aug 2000 10:12:14 -0400 (EDT)
Message-ID: <39874164.8215EBDA@cisco.com>
Date: Tue, 01 Aug 2000 17:30:12 -0400
From: "W. Mark Townsley" <townsley@cisco.com>
X-Mailer: Mozilla 4.7 [en] (Win95; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: Ignacio Goyret <igoyret@lucent.com>
CC: "Shriver, John" <john.shriver@intel.com>,
        Klausberger Walter <walter.klausberger@siemens.at>,
        "'abickford@ipwireless.com'" <abickford@ipwireless.com>, l2tp@l2tp.net
Subject: Re: AW: PPP Frames on tunnel
References: <392A357CE6FFD111AC3E00A0C99848B00369501E@hdsmsx31.hd.intel.com> <3.0.5.32.20000801090253.03da8660@scamp.eng.ascend.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



Ignacio Goyret wrote:
> 
> At 11:37 AM 8/1/00 -0400, W. Mark Townsley wrote:
> >The prudent thing to do these days would be to
> >always tack on the framing as PPP can handle the FF03 whether ACFC was
> >negotiated or not.
> 
> ... unless the packet in question already has the FF03. Otherwise, you can
> end up with FF03FF03002145.... which PPP will have a hard time dealing with.

Of course. This is what I intended, but thanks for the needed
clarification.




From owner-l2tp@diameter.org  Wed Aug  2 16:34:41 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07253
	for <l2tpext-archive@odin.ietf.org>; Wed, 2 Aug 2000 16:34:40 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e72HS0A27822
	for l2tp-list; Wed, 2 Aug 2000 10:28:00 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from zendo.com (bodhi.zendo.com [205.187.71.2])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e72HRvd27816
	for <l2tp@l2tp.net>; Wed, 2 Aug 2000 10:27:57 -0700
Received: from vandys-pc.zendo.com (dialup-209.245.173.34.Seattle1.Level3.net [209.245.173.34])
	by zendo.com (8.10.1/8.10.1) with ESMTP id e729LWB18285
	for <l2tp@l2tp.net>; Wed, 2 Aug 2000 09:21:32 GMT
Received: from vandys-pc.zendo.com (localhost.zendo.com [127.0.0.1])
	by vandys-pc.zendo.com (8.9.1/8.9.1) with ESMTP id KAA00269
	for <l2tp@l2tp.net>; Wed, 2 Aug 2000 10:30:07 -0700 (PDT)
	(envelope-from vandys@vandys-pc.zendo.com)
Message-Id: <200008021730.KAA00269@vandys-pc.zendo.com>
To: l2tp@l2tp.net
Subject: Re: PPP Frames on tunnel
Date: Wed, 02 Aug 2000 10:30:07 -0700
From: Andy Valencia <vandys@zendo.com>
Sender: owner-l2tp@diameter.org
Precedence: bulk

>  Let's be honest about why the Address and Control fields are there in
>  PPP.   

Since I'm as responsible as anybody for this, I may as well respond to this
point.

The reason A/C was left in was that, at the time this was all being
assembled, PPP-over-HDLC was pretty much the only game in town.  At the
time, my perception of the FR and ATM people was that they were going to go
their own way, and reinvent everything they needed.

PPP over Ethernet was, to put it mildly, right off the radar screen.

So, in this environment, I looked at PPP, and saw that if I didn't monkey
with A/C, then A/C compression would still be available (so the overhead
isn't mandatory), and I wouldn't have to spend time explaining why disabling
RFC1663 (which at least some of *my* customers, at the time, used) was a
Good Idea.  So that was the encap used in L2F, and by the time Gurdeep and I
were assembling L2TP, this was working out fine in practice, so we left the
encap the way you find it today.

With the possibility of L2TP extensions to carry other circuit services, I
certainly agree that we're at a very nice point to parameterize the
encapsulation, and thus permit "raw" PPP as well as HDLC PPP.  If L2TP ends
up not being used as a circuit tunnel, then it probably still makes sense
for L2TPbis to add an appropriate AVP.

$0.02,
Andy Valencia


From owner-l2tp@diameter.org  Wed Aug  2 16:34:57 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07347
	for <l2tpext-archive@odin.ietf.org>; Wed, 2 Aug 2000 16:34:56 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e72GkeX27795
	for l2tp-list; Wed, 2 Aug 2000 09:46:40 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from shako.cisco.com (shako.cisco.com [161.44.3.76])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e72Gkbd27789
	for <l2tp@l2tp.net>; Wed, 2 Aug 2000 09:46:37 -0700
Received: from cisco.com (rtp-dial-1-14.cisco.com [10.83.97.14])
	by shako.cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id MAA14259
	for <l2tp@l2tp.net>; Wed, 2 Aug 2000 12:50:18 -0400 (EDT)
Message-ID: <39885164.1837E7AA@cisco.com>
Date: Wed, 02 Aug 2000 12:50:44 -0400
From: "W. Mark Townsley" <townsley@cisco.com>
X-Mailer: Mozilla 4.7 [en] (Win95; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: l2tp@l2tp.net
Subject: Revised l2tpext agenda
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


15:30 Agenda Bashing
      Mark Townsley

15:35 VPN Bakeoff Announcement
      Anita Freeman

15:40 draft-ietf-l2tpext-ppp-discinfo-00.txt, 
      Madhvi Verma, James Carlson

15:55 draft-ietf-l2tpext-l2tp-security-01.txt, 
      draft-aboba-nat-ipsec-01.txt 
      Bernard Aboba 

16:10 draft-ietf-l2tpext-l2tpbis-00.txt
      Mark Townsley

16:20 WG draft status,
      Mark Townsley	

16:25 draft-ietf-l2tpext-fr-00.txt, 
      draft-ietf-l2tpext-l2tp-atm-01.txt,
      Suhail Nanji

16:30 draft-nanji-l2tp-eth-00.txt
      Suhail Nanji 

16:50 draft-mcpherson-l2tp-es-01.txt
      Ravi Baht, Danny Mcpherson

17:10 l2tpext charter, goals and milestones
      Mark Townsley


From owner-l2tp@diameter.org  Fri Aug  4 11:55:06 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25217
	for <l2tpext-archive@odin.ietf.org>; Fri, 4 Aug 2000 11:55:04 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e74DDfN29573
	for l2tp-list; Fri, 4 Aug 2000 06:13:41 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e74DDcd29567
	for <l2tp@l2tp.net>; Fri, 4 Aug 2000 06:13:38 -0700
Received: from gm01rl.cwusa.com (hoya.cwusa.com [146.135.27.10]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id GAA16785 for <l2tp@ipsec.org>; Fri, 4 Aug 2000 06:17:34 -0700 (PDT)
Received: from wsglicks.plc.com ([172.25.6.236])
 by GM01RL.CWUSA.COM (PMDF V6.0-24 #46354)
 with ESMTPA id <0FYR001BXRK9FF@GM01RL.CWUSA.COM> for l2tp@ipsec.org; Fri,
 04 Aug 2000 13:16:58 +0000 (GMT)
Date: Fri, 04 Aug 2000 14:12:31 +0100
From: Stephen Glick <stephen.glick@cw.com>
Subject: l2tp-request@ipsec.org
To: l2tp@ipsec.org
Reply-to: stephen.glick@cw.com
Message-id: <00ae01bffe15$a5a84560$ec0619ac@plc.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0
Content-type: multipart/mixed;
 boundary="----=_NextPart_000_00AF_01BFFE1E.076CAD60"
Importance: Normal
X-Priority: 3 (Normal)
X-MSMail-priority: Normal
X-MS-TNEF-Correlator: 00000000CABDC912D766D411A38800508B51264584EB2600
Sender: owner-l2tp@diameter.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_00AF_01BFFE1E.076CAD60
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

l2tp-request@ipsec.org 


------=_NextPart_000_00AF_01BFFE1E.076CAD60
Content-Type: application/ms-tnef;
	name="winmail.dat"
Content-Disposition: attachment;
	filename="winmail.dat"
Content-Transfer-Encoding: base64

eJ8+Ih8NAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEIgAcAGAAAAElQTS5NaWNy
b3NvZnQgTWFpbC5Ob3RlADEIAQ2ABAACAAAAAgACAAEGgAMADgAAANAHCAAEAA4ADAAAAAUAAgEB
A5AGAMgEAAAnAAAACwACAAEAAAALACMAAAAAAAMAJgAAAAAACwApAAAAAAADADYAAAAAAB4AcAAB
AAAAGAAAAGwydHAtcmVxdWVzdEBpcHNlYy5vcmcgAAIBcQABAAAAFgAAAAG//hWlOhHwqF9p6BHU
o4gAUItRJkUAAAIBHQwBAAAAGgAAAFNNVFA6U1RFUEhFTi5HTElDS0BDVy5DT00AAAALAAEOAAAA
AEAABg4A0MeSFf6/AQIBCg4BAAAAGAAAAAAAAADKvckS12bUEaOIAFCLUSZFwoAAAAsAHw4BAAAA
AwAGEJw5hk4DAAcQFQAAAB4ACBABAAAAFgAAAEwyVFAtUkVRVUVTVEBJUFNFQ09SRwAAAAIBCRAB
AAAAkwAAAI8AAADOAAAATFpGdZLD4OIDAAoAcmNwZzEyNSYyAPgLYG5nAdA1N50B9yACpANjAgBj
aArA4HNldDAgB20CgwBQLwPUENkHEwKAfQqBdWNDAFALA3NiMTABQHOiYRVSdWxuAiBlArFAIGwy
dHAtCXBxMQpQc3RABSARMGMu/QWwZwrjCoQLMBKzDAEYEwUUYQAZ0AADABAQAAAAAAMAERAAAAAA
CwABgAggBgAAAAAAwAAAAAAAAEYAAAAAA4UAAAAAAAADAAOACCAGAAAAAADAAAAAAAAARgAAAAAQ
hQAAAAAAAAMAK4AIIAYAAAAAAMAAAAAAAABGAAAAAFKFAADwEwAAHgAsgAggBgAAAAAAwAAAAAAA
AEYAAAAAVIUAAAEAAAAEAAAAOC41AAsALYAIIAYAAAAAAMAAAAAAAABGAAAAAAaFAAAAAAAAAwAu
gAggBgAAAAAAwAAAAAAAAEYAAAAAAYUAAAAAAAALADeACCAGAAAAAADAAAAAAAAARgAAAAAOhQAA
AAAAAAMAOIAIIAYAAAAAAMAAAAAAAABGAAAAABGFAAAAAAAAAwA6gAggBgAAAAAAwAAAAAAAAEYA
AAAAGIUAAAAAAAAeAEmACCAGAAAAAADAAAAAAAAARgAAAAA2hQAAAQAAAAEAAAAAAAAAHgBKgAgg
BgAAAAAAwAAAAAAAAEYAAAAAN4UAAAEAAAABAAAAAAAAAB4AS4AIIAYAAAAAAMAAAAAAAABGAAAA
ADiFAAABAAAAAQAAAAAAAAALAFOACCAGAAAAAADAAAAAAAAARgAAAACChQAAAQAAAAsA6YALIAYA
AAAAAMAAAAAAAABGAAAAAACIAAAAAAAACwDqgAsgBgAAAAAAwAAAAAAAAEYAAAAABYgAAAAAAAAC
AfgPAQAAABAAAADKvckS12bUEaOIAFCLUSZFAgH6DwEAAAAQAAAAyr3JEtdm1BGjiABQi1EmRQIB
+w8BAAAAcwAAAAAAAAA4obsQBeUQGqG7CAArKlbCAABQU1RQUlguRExMAAAAAAAAAABOSVRB+b+4
AQCqADfZbgAAAEM6XFdJTkRPV1NcQXBwbGljYXRpb24gRGF0YVxNaWNyb3NvZnRcT3V0bG9va1xv
dXRsb29rLnBzdAAAAwD+DwUAAAADAA00/TcAAAIBfwABAAAAMQAAADAwMDAwMDAwQ0FCREM5MTJE
NzY2RDQxMUEzODgwMDUwOEI1MTI2NDU4NEVCMjYwMAAAAABtyw==

------=_NextPart_000_00AF_01BFFE1E.076CAD60--



From owner-l2tp@diameter.org  Fri Aug  4 21:24:27 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA13317
	for <l2tpext-archive@odin.ietf.org>; Fri, 4 Aug 2000 21:24:27 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e74MIhB30229
	for l2tp-list; Fri, 4 Aug 2000 15:18:43 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from shako.cisco.com (shako.cisco.com [161.44.3.76])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e74MIed30223
	for <l2tp@l2tp.net>; Fri, 4 Aug 2000 15:18:40 -0700
Received: from cisco.com (rtp-dial-1-14.cisco.com [10.83.97.14])
	by shako.cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id SAA04049;
	Fri, 4 Aug 2000 18:22:20 -0400 (EDT)
Message-ID: <398B4234.D7510DB8@cisco.com>
Date: Fri, 04 Aug 2000 18:22:44 -0400
From: "W. Mark Townsley" <townsley@cisco.com>
X-Mailer: Mozilla 4.7 [en] (Win95; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: l2tp@l2tp.net, minutes@ietf.org
Subject: Minutes from 48th IETF l2tpext WG meeting
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


L2TPExt WG 15:30 2AUG00 Pittsburgh
Chair: Mark Townsley
Minute-taker: Dory Leifer

Agenda Bashing
No changes suggested to the prepared agenda

VPN Bakeoff announcement
San Diego bakeoff announcement was given by Mark in Anita's absence

l2tp-bis-00 presented by Mark
slides "l2tp-bis-00" presented:
 Ambiguity in bearer capabilities discovered in workshop and required
clarification.
 New codepoints may need to be assigned by IANA
 Bearer-capabilities should only be used for dial-out
 New "V" bit for virtual bearer - if no bits are set, it's something we
don't know
 Will followup at September workshop to see how well the "V" bit helps,
it
may come out

draft-ietf-l2tpext-ppp-discinfo-00.txt
Madhvi Verma, James Carlson, Rohit Verma
Slides presented with Madhvi Verma 
  New proposed optional AVP in call disconnect
  Can be sent by LAC or LNS
  Motivated by lack of disconnection information
  Disconnect code broken into 3 parts
  Would be desirable to log AVP in RADIUS accounting message
  Desire to move draft to proposed standard

WG unpassionately agreed that the draft was useful. No additional
comments.

draft-ietf-l2tpext-l2tp-security-01.txt

Presented by William Dixon
Would like to go to working group last call
Presented overview slides summarizing draft
MTU changes are possible and observed
Highlighted issue Filter proposed in IKE Quick Mode ProxyID (establish
and
rekey)
Filter that is property of IPSEC SA - post decrypt check to be sure
received traffic is what was expected for SA (useful for NAT)
Issue from list: teardown slide "teardown" presented
Need to coordinate IPSEC state after teardown
Certificate Handling
Separate users from machines

WG discussion:

User credentials may need to be prompted but is implementation specific
but
not part of the protocol
Question about xoff, inconfig - not addressed by this draft
Using standard IPSEC transport mode to secure L2TP
Using user credential is better than using machine credential
Certs dont know if they are machine or user - its a matter of policy to
decide which is acceptable
This is typically only a problem from a client
How should the draft be worded "MUST accept machine credentials?"
Zorn: customers do see the difference between the two cases referenced
in
"question" on certificate handling.
WG consenus is that it is a matter of local policy if machine or user
cert
(and MAY is ok)
Mark: ready for last call?
Steve Belovin has reportedly determined that there may be security
problems
but nobody has seen them posted
Would be nice to see this to see if we can improve the security

Mark 
L2TP MIB last call on May 31st
atmext-03 ready for last call
l2tphc - significant changes Andy posted another draft - no comments on
list - ready for Last Call
sessinfo-01  ready for last call
linkinfo - needs resubmission - nice thing to have but have not seen
interest. Mark may resubmit. Someone says nice to have also
adc - stalled
diffserv - Ken plans to resubmit with changes
Suhail Nanji took over Rene Tio's draft on atm - ready for last call
there

We're not going to talk about L2TP/IPsec NAT because has been presented
in two
other working groups already.

Time 16:30

Ethernet over L2TP
draft-nanji-l2tp-eth-00.txt
Suhail Nanji
Tunnel should be able to support PPP and eth over L2TP
ppp/pppoe/802.3/l2tp
(two other configurations)
Explained motivation in slide "PPPoE with Ethernet over L2TP"
Need to carry the PPPoE traffic
Doesn't seem useful for voluntary but Ross pointed out you can use PPPoe
and L2tp on the same client
There are other alternative for doing the tunneling
There is a standard way to do this with BCP - why not.
Issue with MTU and with mixed non-ethernet media where MAC address has
different ordering.

l2tp Circuit Emulation Services (CES) Extension
draft-mcpherson-l2tp-es-01.txt
Danny McPherson
Slides presented
Motivation payload may be other frame services (???)
Service type AVP may be needed
Goal provide IP-based circuit emulation services
Jim Boyle is presenting STS services over IP and RTP definition. They
don't
specify IP tunneling protocol.
It is preferable to use L2TP vs. GRE because of session aggregation and
call setup (signaling)
Tunnel frame relay over IP infrastructure
GRE does support multiple sessions in single tunnel.
Argument about the above and current deposition of GRE RFC and
key/sequence
field
More discussion about whether GRE or L2TP is better for this application
Discussion about RTP, GRE, MPLS
L2TP work over MPLS is still ongoing and could be useful to the
applications.
boyle's draft explains service provider specifics over IP (will post
reference to the list)
Doesn't RTP give you what you want?
L2TP provides RTP and the signaling information (may need to exchange
circuit parameters like low-layer framing[??])
Why not use a PPP NCP? Scalability could be a problem
If there is interest may come up with applicability statement
What should the working group do? The products are coming out.
Do we want to open L2TP to protocols other than PPP?
The CES is way beyond the scope of this working group.
Maybe there should be a CES working group?
Signaling mechanisms could be used with RTP but "seemed heavy".
Plan to publish an informational document describing Danny's
implementation.
Mark asks "this is how you transport things other than PPP over
L2TP" should we take that on in this working group?
Other protocols could use AVP for service-specific items
This is better done inside RTP or protocol carried inside L2TP - just
need
a single AVP
Glen asked who else is doing this or is going to do this?
Maybe Redback but that is for something else.
3 vendors are at least interested now
debating if should go to bakeoff
ethernet over L2TP
Glen suggests that both parties create a single draft
Need to bound to changes to call setup AVP
Mark asked if reasonable for us to take on service-type AVP on call
setup
and handle non-ppp frames
will try to get consensus from the list
charter will need to get modified
Should this be informational on the first pass.
Glen says he would like it "vendor-specific standards track" if there is
sufficient interest, it can progress


Meeting end 17:30

None of the below talked about.

draft-adoba-nat-ipsec-01.txt
Bernard Aboba, et al

WG draft status

draft-ietf-l2tpext-fr-00.txt
draft-ietf-l2tpext-l2tp-atm-01.txt
Suhail Nanji


From owner-l2tp@diameter.org  Fri Aug  4 21:42:41 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA19196
	for <l2tpext-archive@odin.ietf.org>; Fri, 4 Aug 2000 21:42:40 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e74Mwrk30268
	for l2tp-list; Fri, 4 Aug 2000 15:58:53 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from shako.cisco.com (shako.cisco.com [161.44.3.76])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e74Mwod30262
	for <l2tp@l2tp.net>; Fri, 4 Aug 2000 15:58:50 -0700
Received: from cisco.com (rtp-dial-1-14.cisco.com [10.83.97.14])
	by shako.cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id TAA07338;
	Fri, 4 Aug 2000 19:02:02 -0400 (EDT)
Message-ID: <398B4B82.467B4CD0@cisco.com>
Date: Fri, 04 Aug 2000 19:02:26 -0400
From: "W. Mark Townsley" <townsley@cisco.com>
X-Mailer: Mozilla 4.7 [en] (Win95; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: nordmark@eng.sun.com, narten@raleigh.ibm.com
CC: l2tp@l2tp.net
Subject: l2tpext meeting synopsis
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

draft-ietf-l2tpext-ppp-discinfo-00.txt generally accepted as a Good
Thing. 
draft-ietf-l2tpext-l2tp-security-01.txt is fairly stable and should move
forward. Some discussion about ipsra, Xauth, etc. ensued. It was noted
that this draft defines how to protect L2TP with IPsec only. Changes to
IPsec are clearly outside the scope of the WG. 

The following drafts are ready for WG last call: 

draft-ietf-l2tpext-ppp-discinfo-00.txt 
draft-ietf-l2tpext-atmext-03.txt 
draft-ietf-l2tpext-l2tphc-02.txt 
draft-ietf-l2tpext-sessinfo-01.txt 
draft-ietf-l2tp-security-00.txt
draft-ietf-l2tpext-fr-00.txt
draft-ietf-l2tpext-l2tp-atm-01.txt,

The following draft needs resubmission with last call changes before
IETF last call.

draft-ietf-l2tpext-l2tp-mib-00.txt

linkinfo draft will be resubmitted.

Much discussion ensued about L2TP being used to carry PDUs other than
PPP after presentation of draft-nanji-l2tp-eth-00.txt and
draft-mcpherson-l2tp-es-01.txt. It is fairly clear that there are
multiple vendors choosing L2TP to tunnel  protocols other than PPP.
There was discussion about L2TP vs. other tunneling methods,
particularly GRE. Proponents cite L2TP's call setup and well
standardized tunnel/session aggregation as reasons for choosing the
protocol as their solution. 

Consensus in the meeting was that l2tpext will define only the
extensions necessary to L2TP for carrying other PDUs, within the
confines of L2TP's extensibility framework (e.g. new AVPs, but no
changes in the L2TP protocol itself). This will involve standardization
of the AVP(s) that identify the type of PDU to be carried, and new or
existing AVPs that will be used during L2TP call setup or teardown. Any
real time signaling or modifications to the particular protocol being
carried by L2TP are outside the scope of l2tpext WG. If consensus is
concurred on the mailing list, l2tp-bis and the l2tpext charter will be
revised accordingly.


From owner-l2tp@diameter.org  Fri Aug  4 23:07:25 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA09039
	for <l2tpext-archive@odin.ietf.org>; Fri, 4 Aug 2000 23:07:24 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e74NQ3r30328
	for l2tp-list; Fri, 4 Aug 2000 16:26:03 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from shako.cisco.com (shako.cisco.com [161.44.3.76])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e74NPxd30322
	for <l2tp@l2tp.net>; Fri, 4 Aug 2000 16:26:00 -0700
Received: from cisco.com (rtp-dial-1-14.cisco.com [10.83.97.14])
	by shako.cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id TAA09653
	for <l2tp@l2tp.net>; Fri, 4 Aug 2000 19:29:42 -0400 (EDT)
Message-ID: <398B51FE.BF29691C@cisco.com>
Date: Fri, 04 Aug 2000 19:30:06 -0400
From: "W. Mark Townsley" <townsley@cisco.com>
X-Mailer: Mozilla 4.7 [en] (Win95; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: l2tp@l2tp.net
Subject: Working group last call items
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


This is last call.  I will advise the area directors on September 4,
2000, that we want to take the following drafts to Proposed Standard
unless there is substantive comment raised on this list.

draft-ietf-l2tpext-ppp-discinfo-00.txt 
draft-ietf-l2tpext-atmext-03.txt 
draft-ietf-l2tpext-l2tphc-02.txt 
draft-ietf-l2tpext-sessinfo-01.txt 
draft-ietf-l2tpext-security-00.txt
draft-ietf-l2tpext-fr-00.txt
draft-ietf-l2tpext-l2tp-atm-01.txt

Thanks,

- Mark


From owner-l2tp@diameter.org  Sat Aug  5 02:24:30 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA24143
	for <l2tpext-archive@odin.ietf.org>; Sat, 5 Aug 2000 02:24:30 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e752kn430444
	for l2tp-list; Fri, 4 Aug 2000 19:46:49 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from tcb.net (tcb.net [205.168.100.1])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e752kGd30438
	for <l2tp@l2tp.net>; Fri, 4 Aug 2000 19:46:16 -0700
Received: from sofos.tcb.net (sofos.tcb.net [127.0.0.1])
	by tcb.net (8.9.3/8.9.3) with ESMTP id UAA14626
	for <l2tp@l2tp.net>; Fri, 4 Aug 2000 20:51:17 -0600
Message-Id: <200008050251.UAA14626@tcb.net>
X-Mailer: exmh version 2.0.3
To: l2tp@l2tp.net
From: Danny McPherson <danny@tcb.net>
Reply-To: danny@tcb.net
Subject: Re: Minutes from 48th IETF l2tpext WG meeting 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 04 Aug 2000 20:51:16 -0600
Sender: owner-l2tp@diameter.org
Precedence: bulk


References to the two drafts related to IP CES stuff that I mentioned during the WG session are provided below.  Both are available via the IETF ftp server.

draft-boyle-sts-ip-00.txt
draft-white-sonet-format-rtp-00.txt

-danny



From owner-l2tp@diameter.org  Sat Aug  5 09:44:44 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26604
	for <l2tpext-archive@odin.ietf.org>; Sat, 5 Aug 2000 09:44:43 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e75Alkj30655
	for l2tp-list; Sat, 5 Aug 2000 03:47:46 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e75Alhd30649
	for <l2tp@l2tp.net>; Sat, 5 Aug 2000 03:47:43 -0700
Received: from webveda.com (root@host-216-226-254-55.interpacket.net [216.226.254.55]) by ns1.sailpix.com (8.8.8/8.6.9) with SMTP id DAA08598 for <l2tp@ipsec.org>; Sat, 5 Aug 2000 03:51:43 -0700 (PDT)
Received: from webveda.com ([216.226.254.55]) by webveda.com ; Sun, 06 Aug 2000 00:50:29 -0400
From: "Shankar" <shankarv@webveda.com>
Reply-to: shankarv@webveda.com
To: l2tp@ipsec.org
Date: Sat, 05 Aug 2000 16:22:33 +0600
Subject: Outgoing call
X-Mailer: CWMail Web to Mail Gateway 2.5e, http://netwinsite.com/top_mail.htm
Message-id: <398cee95.53df.0@webveda.com>
X-User-Info: 203.197.138.194
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi folks,

What I actually want to know is when a LNS would
go for a outgoing call ?

one scenario that I can think of is, the remote client may ask
the HOME LAN to call back, he does not want to pay for the call
he is making he HOME LAN management will cover the charge.

am i right ? if wrong pl. correct me.

any other scenarios ?

tia
shankar

-------------------------------------------------
Make webveda your permanent address like i have.
Get 15 MB Free space only at http://www.webveda.com


From owner-l2tp@diameter.org  Sat Aug  5 16:07:56 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14547
	for <l2tpext-archive@odin.ietf.org>; Sat, 5 Aug 2000 16:07:55 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e75HDmF30998
	for l2tp-list; Sat, 5 Aug 2000 10:13:48 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e75HDkd30992
	for <l2tp@l2tp.net>; Sat, 5 Aug 2000 10:13:46 -0700
Received: from brahma.roc.com ([202.54.67.220]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id KAA08826 for <l2tp@ipsec.org>; Sat, 5 Aug 2000 10:17:53 -0700 (PDT)
Received: from sridhar.roc.com ([172.16.5.52])
	by brahma.roc.com (8.8.5/8.8.5) with SMTP id WAA27836
	for <l2tp@ipsec.org>; Sat, 5 Aug 2000 22:53:01 +0530 (IST)
Message-Id: <200008051723.WAA27836@brahma.roc.com>
X-Sender: sridhar@172.16.1.10 (Unverified)
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0
Date: Sat, 05 Aug 2000 22:56:52 +0530
To: l2tp@ipsec.org
From: Sridhar Malarothu <sridhar@trinc.com>
Subject: AVP Type 20
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-l2tp@diameter.org
Precedence: bulk

Hi All,

   In the RFC 2661, AVP Type 20 is missing. Can someone 
give me some Information about this AVP ?
   

Best Regards
Sridhar




From owner-l2tp@diameter.org  Sat Aug  5 23:27:02 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA21380
	for <l2tpext-archive@odin.ietf.org>; Sat, 5 Aug 2000 23:27:01 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e760Y0031182
	for l2tp-list; Sat, 5 Aug 2000 17:34:00 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e760Xpd31176
	for <l2tp@l2tp.net>; Sat, 5 Aug 2000 17:33:51 -0700
Received: from shako.cisco.com (shako.cisco.com [161.44.3.76]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id RAA09082 for <l2tp@ipsec.org>; Sat, 5 Aug 2000 17:38:03 -0700 (PDT)
Received: from cisco.com (rtp-dial-1-243.cisco.com [10.83.97.243])
	by shako.cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id UAA17930;
	Sat, 5 Aug 2000 20:37:08 -0400 (EDT)
Message-ID: <398CB34B.1D3660B0@cisco.com>
Date: Sat, 05 Aug 2000 20:37:31 -0400
From: "W. Mark Townsley" <townsley@cisco.com>
X-Mailer: Mozilla 4.7 [en] (Win95; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: Sridhar Malarothu <sridhar@trinc.com>
CC: l2tp@ipsec.org
Subject: Re: AVP Type 20
References: <200008051723.WAA27836@brahma.roc.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


See:

http://www.townsley.net/mark/l2tp/draft-ietf-pppext-l2tp-12.txt

This was part of flow control which has been deprecated.

Sridhar Malarothu wrote:
> 
> Hi All,
> 
>    In the RFC 2661, AVP Type 20 is missing. Can someone
> give me some Information about this AVP ?
> 
> 
> Best Regards
> Sridhar


From owner-l2tp@diameter.org  Sat Aug  5 23:50:50 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA24964
	for <l2tpext-archive@odin.ietf.org>; Sat, 5 Aug 2000 23:50:49 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e760vPd31200
	for l2tp-list; Sat, 5 Aug 2000 17:57:25 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e760vNd31194
	for <l2tp@l2tp.net>; Sat, 5 Aug 2000 17:57:23 -0700
Received: from center.mshindo.net (center.mshindo.net [210.231.221.221]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id SAA09099 for <l2tp@ipsec.org>; Sat, 5 Aug 2000 18:01:33 -0700 (PDT)
Received: from cosinecom.com (pl007.nas911.n-yokohama.nttpc.ne.jp [210.139.55.7])
	by center.mshindo.net (8.9.3/3.7W/00041811) with SMTP id KAA84961;
	Sun, 6 Aug 2000 10:05:01 +0900 (JST)
Date: Sun, 06 Aug 2000 10:00:53 +0900 (JST)
Message-Id: <20000806.100053.74755583.mshindo@mshindo.net>
To: sridhar@trinc.com
Cc: l2tp@ipsec.org
Subject: Re: AVP Type 20
From: Motonori Shindo <mshindo@mshindo.net>
In-Reply-To: <200008051723.WAA27836@brahma.roc.com>
References: <200008051723.WAA27836@brahma.roc.com>
X-Mailer: Mew version 1.95b30 on XEmacs 21.1 (Canyonlands)
X-PGP-fingerprint: 06 B0 B1 A4 06 C1 6A 14  63 C0 D7 18 01 CD D9 83
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Sridhar,

AVP Type 20 used to be a 'Packet Processcing Delay', which we don't
support in RFC2661. This was one of the things which was inheritated
from PPTP. The reason why this AVP no longer exists in the RFC2661 has
to do with the fact that we don't support flow control at the moment,
I guess.

Regards,

From: Sridhar Malarothu <sridhar@trinc.com>
Subject: AVP Type 20
Date: Sat, 05 Aug 2000 22:56:52 +0530

> Hi All,
> 
>    In the RFC 2661, AVP Type 20 is missing. Can someone 
> give me some Information about this AVP ?
>    
> 
> Best Regards
> Sridhar

=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=
 +----+----+     
 |.. .|    |     Motonori Shindo
 |_~__|    |     
 | .. |~~_~|     Sr. Systems Engineer
 | .  |    |     CoSine Communications Inc.
 +----+----+     
 C o S i n e     e-mail:  mshindo@cosinecom.com 
Communications
=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=


From owner-l2tp@diameter.org  Wed Aug  9 22:07:57 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA25630
	for <l2tpext-archive@odin.ietf.org>; Wed, 9 Aug 2000 22:07:56 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e79N5gC08905
	for l2tp-list; Wed, 9 Aug 2000 16:05:42 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e79N5Cd08899
	for <l2tp@l2tp.net>; Wed, 9 Aug 2000 16:05:12 -0700
Received: from mx1-11.onmedia.com (mx1-11.onmedia.com [209.133.35.16]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id QAA19024 for <l2tp@ipsec.org>; Wed, 9 Aug 2000 16:09:37 -0700 (PDT)
Received: from GP1 (root@localhost)
	by mx1-11.onmedia.com (8.8.8/OICP2.0.5b1/8.8.8/OICP2.0.5b1) with OICP id QAA83970
	for l2tp@ipsec.org; Wed, 9 Aug 2000 16:05:13 -0700 (PDT)
Received: from OnMedia Mail (GPX1)
	by mx1-11.onmedia.com ($Revision: 2.3 $) with OICP
	id 99934241; Wed, 09 Aug 2000 16:05:13 -0800
Subject: Doubt regarding testing LNS......
Date: Wed, 09 Aug 2000 16:05:06 -0800
Message-Id: <99934241.1.373@mx1-11.onmedia.com>
Reply-to: "laxmanb" <laxmanb@goplay.com>
From: "laxmanb" <laxmanb@goplay.com>
To: l2tp@ipsec.org
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi all,
       I want to test L2TP-LNS with L2TP-LAC(win 2k).my set up is like 
this.
 PPPclient(pc1)=====>Win 2k(LAC)====>LAN1=====>LAN2===>LNS====>pc2
I have to dail from ppp client.
Here i got some doubts.
How to configure Win 2k for accepting dail from ppp client ?
How to configure win 2k LAC to start negotiating L2TP tunnel between 
LAC and LNS?
What r the configurations to be required for setting L2TP LAC in win 
2k?
please let me clarify all the doubts regarding this?
regards
laxman


+--------------------------------------------------------------------------+
| The coolest site for free home pages, email, chat, e-cards, movie info.. |
|               http://www.goplay.com - it's time to Go Play!              |
+--------------------------------------------------------------------------+


From owner-l2tp@diameter.org  Thu Aug 10 00:33:46 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA29113
	for <l2tpext-archive@odin.ietf.org>; Thu, 10 Aug 2000 00:33:45 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e7A2HP209009
	for l2tp-list; Wed, 9 Aug 2000 19:17:25 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e7A2HMd09003
	for <l2tp@l2tp.net>; Wed, 9 Aug 2000 19:17:22 -0700
Received: from dfssl.exchange.microsoft.com (dfssl.exchange.microsoft.com [131.107.88.59]) by ns1.sailpix.com (8.8.8/8.6.9) with SMTP id TAA19177 for <l2tp@ipsec.org>; Wed, 9 Aug 2000 19:21:48 -0700 (PDT)
Received: from 172.30.236.11 by dfssl.exchange.microsoft.com (InterScan E-Mail VirusWall NT); Wed, 09 Aug 2000 17:49:57 -0700 (Pacific Daylight Time)
Received: from SIT.platinum.corp.microsoft.com ([172.30.236.233]) by yuri.dns.microsoft.com with Microsoft SMTPSVC(5.0.2195.2023);
	 Wed, 9 Aug 2000 17:38:42 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C00260.A59A50E6"
Subject: RE: Doubt regarding testing LNS......
Date: Wed, 9 Aug 2000 17:19:28 -0700
Message-ID: <19398D273324D3118A2B0008C7E9A5690DE7BA5B@SIT.platinum.corp.microsoft.com>
Thread-Topic: Doubt regarding testing LNS......
Thread-Index: AcACWLeuTTZEIq1mTH2o2tmHM+fHTwAB544w
From: "Rob Trace" <robt@Exchange.Microsoft.com>
To: "laxmanb" <laxmanb@goplay.com>, <l2tp@ipsec.org>
X-OriginalArrivalTime: 10 Aug 2000 00:38:42.0997 (UTC) FILETIME=[55BEF650:01C00263]
Sender: owner-l2tp@diameter.org
Precedence: bulk

This is a multi-part message in MIME format.

------_=_NextPart_001_01C00260.A59A50E6
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Laxman,

Unfortunately Windows 2000 does not support compulsory tunneling like
you are trying to enable.  The closest we will come to this is to
configure a gateway to gateway connection between 2 Windows 2000 boxes
using a dial on demand L2TP/IPSEC connection.  Let me know if you have
any other questions.

Thanks!!

Rob Trace
Program Manager - Virtual Private Networking
Microsoft Corporation

-----Original Message-----
From: laxmanb [mailto:laxmanb@goplay.com]
Sent: Wednesday, August 09, 2000 5:05 PM
To: l2tp@ipsec.org
Subject: Doubt regarding testing LNS......


Hi all,
       I want to test L2TP-LNS with L2TP-LAC(win 2k).my set up is like=20
this.
 PPPclient(pc1)=3D=3D=3D=3D=3D>Win =
2k(LAC)=3D=3D=3D=3D>LAN1=3D=3D=3D=3D=3D>LAN2=3D=3D=3D>LNS=3D=3D=3D=3D>pc2=

I have to dail from ppp client.
Here i got some doubts.
How to configure Win 2k for accepting dail from ppp client ?
How to configure win 2k LAC to start negotiating L2TP tunnel between=20
LAC and LNS?
What r the configurations to be required for setting L2TP LAC in win=20
2k?
please let me clarify all the doubts regarding this?
regards
laxman


+-----------------------------------------------------------------------
---+
| The coolest site for free home pages, email, chat, e-cards, movie
info.. |
|               http://www.goplay.com - it's time to Go Play!
|
+-----------------------------------------------------------------------
---+

------_=_NextPart_001_01C00260.A59A50E6
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.4417.0">
<TITLE>RE: Doubt regarding testing LNS......</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>Hi Laxman,</FONT>
</P>

<P><FONT SIZE=3D2>Unfortunately Windows 2000 does not support compulsory =
tunneling like you are trying to enable.&nbsp; The closest we will come =
to this is to configure a gateway to gateway connection between 2 =
Windows 2000 boxes using a dial on demand L2TP/IPSEC connection.&nbsp; =
Let me know if you have any other questions.</FONT></P>

<P><FONT SIZE=3D2>Thanks!!</FONT>
</P>

<P><FONT SIZE=3D2>Rob Trace</FONT>

<BR><FONT SIZE=3D2>Program Manager - Virtual Private Networking</FONT>

<BR><FONT SIZE=3D2>Microsoft Corporation</FONT>
</P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>

<BR><FONT SIZE=3D2>From: laxmanb [<A =
HREF=3D"mailto:laxmanb@goplay.com">mailto:laxmanb@goplay.com</A>]</FONT>

<BR><FONT SIZE=3D2>Sent: Wednesday, August 09, 2000 5:05 PM</FONT>

<BR><FONT SIZE=3D2>To: l2tp@ipsec.org</FONT>

<BR><FONT SIZE=3D2>Subject: Doubt regarding testing LNS......</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Hi all,</FONT>

<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; I want to test =
L2TP-LNS with L2TP-LAC(win 2k).my set up is like </FONT>

<BR><FONT SIZE=3D2>this.</FONT>

<BR><FONT SIZE=3D2>&nbsp;PPPclient(pc1)=3D=3D=3D=3D=3D&gt;Win =
2k(LAC)=3D=3D=3D=3D&gt;LAN1=3D=3D=3D=3D=3D&gt;LAN2=3D=3D=3D&gt;LNS=3D=3D=3D=
=3D&gt;pc2</FONT>

<BR><FONT SIZE=3D2>I have to dail from ppp client.</FONT>

<BR><FONT SIZE=3D2>Here i got some doubts.</FONT>

<BR><FONT SIZE=3D2>How to configure Win 2k for accepting dail from ppp =
client ?</FONT>

<BR><FONT SIZE=3D2>How to configure win 2k LAC to start negotiating L2TP =
tunnel between </FONT>

<BR><FONT SIZE=3D2>LAC and LNS?</FONT>

<BR><FONT SIZE=3D2>What r the configurations to be required for setting =
L2TP LAC in win </FONT>

<BR><FONT SIZE=3D2>2k?</FONT>

<BR><FONT SIZE=3D2>please let me clarify all the doubts regarding =
this?</FONT>

<BR><FONT SIZE=3D2>regards</FONT>

<BR><FONT SIZE=3D2>laxman</FONT>
</P>
<BR>

<P><FONT =
SIZE=3D2>+---------------------------------------------------------------=
-----------+</FONT>

<BR><FONT SIZE=3D2>| The coolest site for free home pages, email, chat, =
e-cards, movie info.. |</FONT>

<BR><FONT =
SIZE=3D2>|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp; <A =
HREF=3D"http://www.goplay.com">http://www.goplay.com</A> - it's time to =
Go =
Play!&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp; |</FONT>

<BR><FONT =
SIZE=3D2>+---------------------------------------------------------------=
-----------+</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C00260.A59A50E6--


From owner-l2tp@diameter.org  Thu Aug 10 00:37:35 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA29156
	for <l2tpext-archive@odin.ietf.org>; Thu, 10 Aug 2000 00:37:34 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e7A2YxF09029
	for l2tp-list; Wed, 9 Aug 2000 19:34:59 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e7A2Yvd09023
	for <l2tp@l2tp.net>; Wed, 9 Aug 2000 19:34:57 -0700
Received: from mx1-13.onmedia.com (mx1-13.onmedia.com [209.133.35.11]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id TAA19191 for <l2tp@ipsec.org>; Wed, 9 Aug 2000 19:39:12 -0700 (PDT)
Received: from GP1 (root@localhost)
	by mx1-13.onmedia.com (8.8.8/OICP2.0.5b1/8.8.8/OICP2.0.5b1) with OICP id TAA20455;
	Wed, 9 Aug 2000 19:36:16 -0700 (PDT)
Received: from OnMedia Mail (GPX1)
	by mx1-13.onmedia.com ($Revision: 2.3 $) with OICP
	id 99969404; Wed, 09 Aug 2000 19:36:15 -0800
Subject: RE: Doubt regarding testing LNS......
Date: Wed, 09 Aug 2000 19:35:57 -0800
Message-Id: <99969404.1.562@mx1-13.onmedia.com>
Reply-to: "laxmanb" <laxmanb@goplay.com>
From: "laxmanb" <laxmanb@goplay.com>
To: "Rob Trace" <robt@Exchange.Microsoft.com>, <l2tp@ipsec.org>
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi Rob Trace,
            Thanks alot for u'r reply.But can u suggest me the way to
test my L2TP-LNS with LAC.I want to test LNS with full real traffic
like ping,FTP and Telnet.So as u r telling is it not possible to test
with WIN2K L2TP-LAC.
thanks and regards
laxman




"Rob Trace" <robt@Exchange.Microsoft.com> wrote on Wednesday August 9,
2000 at  7:23pm:
>Hi Laxman,
>
>Unfortunately Windows 2000 does not support compulsory tunneling like
>you are trying to enable.  The closest we will come to this is to
>configure a gateway to gateway connection between 2 Windows 2000 boxes
>using a dial on demand L2TP/IPSEC connection.  Let me know if you have
>any other questions.
>
>Thanks!!
>
>Rob Trace
>Program Manager - Virtual Private Networking
>Microsoft Corporation
>
>-----Original Message-----
>From: laxmanb [mailto:laxmanb@goplay.com]
>Sent: Wednesday, August 09, 2000 5:05 PM
>To: l2tp@ipsec.org
>Subject: Doubt regarding testing LNS......
>
>
>Hi all,
>       I want to test L2TP-LNS with L2TP-LAC(win 2k).my set up is like
>this.
> PPPclient(pc1)=====>Win 2k(LAC)====>LAN1=====>LAN2===>LNS====>pc2
>I have to dail from ppp client.
>Here i got some doubts.
>How to configure Win 2k for accepting dail from ppp client ?
>How to configure win 2k LAC to start negotiating L2TP tunnel between
>LAC and LNS?
>What r the configurations to be required for setting L2TP LAC in win
>2k?
>please let me clarify all the doubts regarding this?
>regards
>laxman
>
>
>+-----------------------------------------------------------------------
>---+
>| The coolest site for free home pages, email, chat, e-cards, movie
>info.. |
>|               http://www.goplay.com - it's time to Go Play!
>|
>+-----------------------------------------------------------------------
>---+




+--------------------------------------------------------------------------+
| The coolest site for free home pages, email, chat, e-cards, movie info.. |
|               http://www.goplay.com - it's time to Go Play!              |
+--------------------------------------------------------------------------+


From owner-l2tp@diameter.org  Thu Aug 10 09:50:06 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA22617
	for <l2tpext-archive@odin.ietf.org>; Thu, 10 Aug 2000 09:50:05 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e7AAmbh09221
	for l2tp-list; Thu, 10 Aug 2000 03:48:37 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e7AAmLd09215
	for <l2tp@l2tp.net>; Thu, 10 Aug 2000 03:48:21 -0700
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id DAA20781 for <l2tp@ipsec.org>; Thu, 10 Aug 2000 03:52:47 -0700 (PDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA14148;
	Thu, 10 Aug 2000 06:52:36 -0400 (EDT)
Message-Id: <200008101052.GAA14148@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce:;
Cc: l2tp@ipsec.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-l2tpext-security-01.txt
Date: Thu, 10 Aug 2000 06:52:35 -0400
Sender: owner-l2tp@diameter.org
Precedence: bulk

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Layer Two Tunneling Protocol Extensions Working Group of the IETF.

	Title		: Securing L2TP using IPSEC
	Author(s)	: B. Patel, B. Aboba, W. Dixon, G. Zorn, S. Booth
	Filename	: draft-ietf-l2tpext-security-01.txt
	Pages		: 22
	Date		: 09-Aug-00
	
This document discusses how L2TP may utilize IPSEC to provide for tunnel
authentication, privacy protection, integrity checking and replay
protection. Both the voluntary and compulsory tunneling cases are
discussed.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-l2tpext-security-01.txt

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-l2tpext-security-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-l2tpext-security-01.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20000809142403.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-l2tpext-security-01.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-l2tpext-security-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20000809142403.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-l2tp@diameter.org  Thu Aug 10 12:08:09 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02306
	for <l2tpext-archive@odin.ietf.org>; Thu, 10 Aug 2000 12:08:08 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e7ADRNd09516
	for l2tp-list; Thu, 10 Aug 2000 06:27:23 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e7ADRKd09510
	for <l2tp@l2tp.net>; Thu, 10 Aug 2000 06:27:20 -0700
Received: from picard.noroff.no ([212.20.204.3]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id GAA21080 for <l2tp@ipsec.org>; Thu, 10 Aug 2000 06:31:46 -0700 (PDT)
Received: by picard.noroff.no (Postfix, from userid 815)
	id 97C5522002; Thu, 10 Aug 2000 16:15:53 +0200 (CEST)
Received: from loki.ietf.org (loki.ietf.org [132.151.1.177])
	by picard.noroff.no (Postfix) with ESMTP id D5292B3802
	for <magg@NOROFF.NO>; Thu, 10 Aug 2000 16:15:50 +0200 (CEST)
Received: (from adm@localhost)
	by loki.ietf.org (8.9.1b+Sun/8.9.1) id IAA05922
	for ietf-123-outbound.09@ietf.org; Thu, 10 Aug 2000 08:55:02 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28])
	by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id GAA04744
	for <all-ietf@loki.ietf.org>; Thu, 10 Aug 2000 06:52:46 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA14148;
	Thu, 10 Aug 2000 06:52:36 -0400 (EDT)
Message-Id: <200008101052.GAA14148@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce:;
Cc: l2tp@ipsec.org
From: Internet-Drafts@ietf.org
Reply-To: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-l2tpext-security-01.txt
Date: Thu, 10 Aug 2000 06:52:35 -0400
X-AntiVirus: scanned for viruses by Amavis 0.2.1-pre2
Sender: owner-l2tp@diameter.org
Precedence: bulk

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Layer Two Tunneling Protocol Extensions Working Group of the IETF.

	Title		: Securing L2TP using IPSEC
	Author(s)	: B. Patel, B. Aboba, W. Dixon, G. Zorn, S. Booth
	Filename	: draft-ietf-l2tpext-security-01.txt
	Pages		: 22
	Date		: 09-Aug-00
	
This document discusses how L2TP may utilize IPSEC to provide for tunnel
authentication, privacy protection, integrity checking and replay
protection. Both the voluntary and compulsory tunneling cases are
discussed.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-l2tpext-security-01.txt

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-l2tpext-security-01.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-l2tpext-security-01.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20000809142403.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-l2tpext-security-01.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-l2tpext-security-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20000809142403.I-D@ietf.org>

--OtherAccess--

--NextPart--




From owner-l2tp@diameter.org  Thu Aug 10 13:44:15 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06399
	for <l2tpext-archive@odin.ietf.org>; Thu, 10 Aug 2000 13:44:15 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e7AFgbK09635
	for l2tp-list; Thu, 10 Aug 2000 08:42:37 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e7AFgZd09629
	for <l2tp@l2tp.net>; Thu, 10 Aug 2000 08:42:35 -0700
Received: from rambo.globespan.net (p1.globespan.net [209.191.59.250]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id IAA21252 for <l2tp@ipsec.org>; Thu, 10 Aug 2000 08:47:01 -0700 (PDT)
Received: by rambo with Internet Mail Service (5.5.2650.21)
	id <QDYNXMVP>; Thu, 10 Aug 2000 11:46:03 -0400
Received: from globespan.net (SMITTAL [192.168.25.27]) by rambo.globespan.net with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id QDYNXMVN; Thu, 10 Aug 2000 11:45:52 -0400
From: Sumati Mittal <smittal@globespan.net>
To: l2tp@ipsec.org
Message-ID: <3992CE38.84895617@globespan.net>
Date: Thu, 10 Aug 2000 11:46:00 -0400
Organization: Globespan, Inc.
X-Mailer: Mozilla 4.5 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
Subject: LCP Negotiation
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,

I have a question regarding LCP negotiation. These are the two
scenarios:

1. LAC does Proxy LCP with the remote system. LNS re-negotiates the
non-ACCM LCP parameters.
2. Only LNS negotiates LCP with the remote system.

Is there a way for LAC to know the negotiated LCP parameters except by
silent observation ?

I have tried to search for draft-ietf-l2tpext-link-00.txt hoping to find
answers there but cannot trace the draft.

Thanks in advance,
Sumati.

Sumati Mittal
GlobeSpan, Inc. 
Voice : (732) 345-6240
mailto:smittal@globespan.net
Web: http://www.globespan.net


From owner-l2tp@diameter.org  Thu Aug 10 14:58:49 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10458
	for <l2tpext-archive@odin.ietf.org>; Thu, 10 Aug 2000 14:58:49 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e7AGvMR09676
	for l2tp-list; Thu, 10 Aug 2000 09:57:22 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e7AGvId09670
	for <l2tp@l2tp.net>; Thu, 10 Aug 2000 09:57:18 -0700
Received: from zev.net (zev.net [206.111.135.146]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id KAA21346 for <l2tp@ipsec.org>; Thu, 10 Aug 2000 10:01:46 -0700 (PDT)
Received: from zev.net (localhost.zev.net [127.0.0.1] (may be forged))
	by zev.net (8.9.3/8.9.3) with ESMTP id JAA12017;
	Thu, 10 Aug 2000 09:57:39 -0700 (PDT)
Message-Id: <200008101657.JAA12017@zev.net>
To: Sumati Mittal <smittal@globespan.net>
cc: l2tp@ipsec.org
Subject: Re: LCP Negotiation 
In-reply-to: Your message of "Thu, 10 Aug 2000 11:46:00 EDT."
             <3992CE38.84895617@globespan.net> 
Date: Thu, 10 Aug 2000 09:57:39 -0700
From: Bill Palter <palter@zev.net>
Sender: owner-l2tp@diameter.org
Precedence: bulk

	
	I'll resubmit the link draft...

Bill


> Hi,
> 
> I have a question regarding LCP negotiation. These are the two
> scenarios:
> 
> 1. LAC does Proxy LCP with the remote system. LNS re-negotiates the
> non-ACCM LCP parameters.
> 2. Only LNS negotiates LCP with the remote system.
> 
> Is there a way for LAC to know the negotiated LCP parameters except by
> silent observation ?
> 
> I have tried to search for draft-ietf-l2tpext-link-00.txt hoping to find
> answers there but cannot trace the draft.
> 
> Thanks in advance,
> Sumati.
> 
> Sumati Mittal
> GlobeSpan, Inc. 
> Voice : (732) 345-6240
> mailto:smittal@globespan.net
> Web: http://www.globespan.net
--
Bill Palter (Palter@zev.net)


From owner-l2tp@diameter.org  Thu Aug 10 16:49:16 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13652
	for <l2tpext-archive@odin.ietf.org>; Thu, 10 Aug 2000 16:49:15 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e7AIHqL09761
	for l2tp-list; Thu, 10 Aug 2000 11:17:52 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e7AIHod09755
	for <l2tp@l2tp.net>; Thu, 10 Aug 2000 11:17:50 -0700
Received: from rambo.globespan.net (p1.globespan.net [209.191.59.250]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id LAA21459 for <l2tp@ipsec.org>; Thu, 10 Aug 2000 11:22:15 -0700 (PDT)
Received: by rambo with Internet Mail Service (5.5.2650.21)
	id <QDYNXN67>; Thu, 10 Aug 2000 14:21:25 -0400
Received: from globespan.net (SMITTAL [192.168.25.27]) by rambo.globespan.net with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id QDYNXN66; Thu, 10 Aug 2000 14:21:19 -0400
From: Sumati Mittal <smittal@globespan.net>
To: "Verma, Rohit (US - Chicago)" <rverma@dc.com>
Cc: l2tp@ipsec.org
Message-ID: <3992F2A6.48092CF4@globespan.net>
Date: Thu, 10 Aug 2000 14:21:26 -0400
Organization: Globespan, Inc.
X-Mailer: Mozilla 4.5 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: LCP Negotiation
References: <2F4A3F6B7BF5D3119E2500508B94E65602292D12@uscntnt405.us.deloitte.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

All of the LCP negotiated parameters. For example, FCS Alternative - LAC
negotiates 16-bit FCS with the remote system, while the LNS renegotiates
it to 32-bit FCS. 

"Verma, Rohit (US - Chicago)" wrote:
> 
> As of now there is no mechanism to do it other than snooping. What
> specific parameters is the LAC interested in?
> 
> Rohit Verma
> Deloitte Consulting
> 180, N. Stetson Avenue
> Chicago, Illinois 60601
> Phone: 312-374-2475
> 
> -----Original Message-----
> From: Sumati Mittal [mailto:smittal@globespan.net]
> Sent: Thursday, August 10, 2000 10:46 AM
> To: l2tp@ipsec.org
> Subject: LCP Negotiation
> 
> Hi,
> 
> I have a question regarding LCP negotiation. These are the two
> scenarios:
> 
> 1. LAC does Proxy LCP with the remote system. LNS re-negotiates the
> non-ACCM LCP parameters.
> 2. Only LNS negotiates LCP with the remote system.
> 
> Is there a way for LAC to know the negotiated LCP parameters except by
> 
> silent observation ?
> 
> I have tried to search for draft-ietf-l2tpext-link-00.txt hoping to
> find
> answers there but cannot trace the draft.
> 
> Thanks in advance,
> Sumati.
> 
> Sumati Mittal
> GlobeSpan, Inc.
> Voice : (732) 345-6240
> mailto:smittal@globespan.net
> Web: http://www.globespan.net


From owner-l2tp@diameter.org  Thu Aug 10 16:59:43 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13851
	for <l2tpext-archive@odin.ietf.org>; Thu, 10 Aug 2000 16:59:42 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e7AJYLM09811
	for l2tp-list; Thu, 10 Aug 2000 12:34:21 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e7AJXod09805
	for <l2tp@l2tp.net>; Thu, 10 Aug 2000 12:33:50 -0700
Received: from rambo.globespan.net (p1.globespan.net [209.191.59.250]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id MAA21633 for <l2tp@ipsec.org>; Thu, 10 Aug 2000 12:38:16 -0700 (PDT)
Received: by rambo with Internet Mail Service (5.5.2650.21)
	id <QDYNX3L7>; Thu, 10 Aug 2000 15:37:27 -0400
Received: from globespan.net (SMITTAL [192.168.25.27]) by rambo.globespan.net with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id QDYNX3L6; Thu, 10 Aug 2000 15:37:25 -0400
From: Sumati Mittal <smittal@globespan.net>
To: Arthur Mistler <amistler@erols.com>
Cc: l2tp@ipsec.org
Message-ID: <3993047C.1312ABF7@globespan.net>
Date: Thu, 10 Aug 2000 15:37:32 -0400
Organization: Globespan, Inc.
X-Mailer: Mozilla 4.5 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: LCP Negotiation
References: <3992CE38.84895617@globespan.net> <3992F273.D93C4180@erols.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Arthur,

Thanks for your reply. 

In both the methods you suggest, once LCP negotiation is done (whether
by LAC-remote system in method 1 or by LAC configuration in method 2),
it is not done again. However, in RFC 2661, the explanation of
Set-Link-Info section 6.14 says PPP options can change at any time
during the call, thus LAC must be able to update its internal call
information and behavior on an active PPP session.

Regards,
Sumati.

Arthur Mistler wrote:
> 
> I may be way off base here because I'm not familiar with the link extension
> draft you mentioned, however I see it exists because someone states they'll
> repost it.
> 
> But these are my impressions on your questions:
> 
> 1. The LNS does not renegotiate any LCP parameters, once LCP is completed
> between the client and LAC, it can't be re-opened, and keeping the session
> in the negotiation phase between initial LAC negotiation, tunnel opening,
> then letting the LNS go with the client may be too lengthy and therefore LCP
> on the client may time out.  So I completely establish the LCP session
> between the client and the LAC, and do a full proxy at the LNS, and if there
> is an LCP option that the LNS really can't agree to, then the session
> fails.  This means that either your LNS needs to be very flexible, or you
> should at least have matching LCP option negotiation requirements for both
> LAC and LNS.  I haven't found it to be too much of a problem doing it this
> way.
> 


> 2. This is what I call service routing, the first one which uses a proxy -
> most likely because you needed to authenticate, I call subscriber routing.
> Forgetting what I call them, though this second method I support by
> configuration.  In other words, my LAC has configuration settings per access
> resource, or per caller ID, stuff like that, where a tunnel is always opened
> for those certain class of calls, and then full negotiation of LCP is the
> responsibility of the LNS.  <I've found it useful to support both methods 1
> and 2.>
> 
> The only way the LAC can know of the negotiate LCP parameters is either to
> do method 1, where it is an active participant in the negotiation, or as you
> say, by silent observation.  But that implies you're using method 2, where
> all LCP negotiation is performed between the client and the LNS.  So in
> effect, the tunnel session is already open, so the only reason the LAC would
> want to know anything about the LCP negotiated parameters would be for
> informational purposes only, and it really doesn't seem to be worth the
> bother.
> 
> Hope this helps.
> 
> - RT
> ==============================
> Artie Mistler
> President
> Advanced Software Consultants, Inc.
> 12 Gale Road
> Sutton, MA  01590
> (508) 581-9815
> mailto:amistler@erols.com
> http://www.erols.com/amistler/ascihome.html
> ==============================
> 
> Sumati Mittal wrote:
> 
> > Hi,
> >
> > I have a question regarding LCP negotiation. These are the two
> > scenarios:
> >
> > 1. LAC does Proxy LCP with the remote system. LNS re-negotiates the
> > non-ACCM LCP parameters.
> > 2. Only LNS negotiates LCP with the remote system.
> >
> > Is there a way for LAC to know the negotiated LCP parameters except by
> > silent observation ?
> >
> > I have tried to search for draft-ietf-l2tpext-link-00.txt hoping to find
> > answers there but cannot trace the draft.
> >
> > Thanks in advance,
> > Sumati.
> >
> > Sumati Mittal
> > GlobeSpan, Inc.
> > Voice : (732) 345-6240
> > mailto:smittal@globespan.net
> > Web: http://www.globespan.net


From owner-l2tp@diameter.org  Thu Aug 10 17:02:51 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13946
	for <l2tpext-archive@odin.ietf.org>; Thu, 10 Aug 2000 17:02:50 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e7AIXBS09780
	for l2tp-list; Thu, 10 Aug 2000 11:33:11 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e7AIWed09774
	for <l2tp@l2tp.net>; Thu, 10 Aug 2000 11:32:40 -0700
Received: from center.mshindo.net (center.mshindo.net [210.231.221.221]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id LAA21513 for <l2tp@ipsec.org>; Thu, 10 Aug 2000 11:37:06 -0700 (PDT)
Received: from cosinecom.com (pl007.nas911.n-yokohama.nttpc.ne.jp [210.139.55.7])
	by center.mshindo.net (8.9.3/3.7W/00041811) with SMTP id DAA92858;
	Fri, 11 Aug 2000 03:42:41 +0900 (JST)
Date: Fri, 11 Aug 2000 03:37:18 +0900 (JST)
Message-Id: <20000811.033718.38716007.mshindo@mshindo.net>
To: smittal@globespan.net
Cc: l2tp@ipsec.org
Subject: Re: LCP Negotiation
From: Motonori Shindo <mshindo@mshindo.net>
In-Reply-To: <3992CE38.84895617@globespan.net>
References: <3992CE38.84895617@globespan.net>
X-Mailer: Mew version 1.95b30 on XEmacs 21.1 (Canyonlands)
X-PGP-fingerprint: 06 B0 B1 A4 06 C1 6A 14  63 C0 D7 18 01 CD D9 83
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Sumati,

From: Sumati Mittal <smittal@globespan.net>
Subject: LCP Negotiation
Date: Thu, 10 Aug 2000 11:46:00 -0400

> Hi,
> 
> I have a question regarding LCP negotiation. These are the two
> scenarios:
> 
> 1. LAC does Proxy LCP with the remote system. LNS re-negotiates the
> non-ACCM LCP parameters.
> 2. Only LNS negotiates LCP with the remote system.
> 
> Is there a way for LAC to know the negotiated LCP parameters except by
> silent observation ?
> 
> I have tried to search for draft-ietf-l2tpext-link-00.txt hoping to find
> answers there but cannot trace the draft.

L2TP protocol doesn't provide such a mechanism. However, it is
technically possible for a LAC to inspect (snoop) the PPP frames
exchanged between a remote system and an LNS to know how LCP (or even
IPCP and CCP) negotiation ended up. I don't know of any implementation
that does this type of snooping.

=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=
 +----+----+     
 |.. .|    |     Motonori Shindo
 |_~__|    |     
 | .. |~~_~|     Sr. Systems Engineer
 | .  |    |     CoSine Communications Inc.
 +----+----+     
 C o S i n e     e-mail:  mshindo@cosinecom.com 
Communications
=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=






From owner-l2tp@diameter.org  Thu Aug 10 17:20:45 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA14217
	for <l2tpext-archive@odin.ietf.org>; Thu, 10 Aug 2000 17:20:44 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e7AHo5209726
	for l2tp-list; Thu, 10 Aug 2000 10:50:05 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e7AHo3d09720
	for <l2tp@l2tp.net>; Thu, 10 Aug 2000 10:50:03 -0700
Received: from ans2-pub.dttus.com (ans2-pub.dttus.com [204.151.11.3]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id KAA21423 for <l2tp@ipsec.org>; Thu, 10 Aug 2000 10:54:30 -0700 (PDT)
Received: by ans2-pub.dttus.com id MAA13007
  (InterLock SMTP Gateway 3.0 for l2tp@ipsec.org);
  Thu, 10 Aug 2000 12:54:27 -0500 (CDT)
Received: by ans2-pub.dttus.com (Internal Mail Agent-2);
  Thu, 10 Aug 2000 12:54:27 -0500 (CDT)
Received: by ans2-pub.dttus.com (Internal Mail Agent-1);
  Thu, 10 Aug 2000 12:54:27 -0500 (CDT)
Message-Id: <2F4A3F6B7BF5D3119E2500508B94E65602292D12@uscntnt405.us.deloitte.com>
From: "Verma, Rohit (US - Chicago)" <rverma@dc.com>
To: Sumati Mittal <smittal@globespan.net>, l2tp@ipsec.org
Subject: RE: LCP Negotiation
Date: Thu, 10 Aug 2000 10:50:34 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C002F3.7C20D990"
Sender: owner-l2tp@diameter.org
Precedence: bulk

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C002F3.7C20D990
Content-Type: text/plain;
	charset="iso-8859-1"

As of now there is no mechanism to do it other than snooping. What specific
parameters is the LAC interested in?

Rohit Verma
Deloitte Consulting
180, N. Stetson Avenue
Chicago, Illinois 60601
Phone: 312-374-2475


-----Original Message-----
From: Sumati Mittal [mailto:smittal@globespan.net]
Sent: Thursday, August 10, 2000 10:46 AM
To: l2tp@ipsec.org
Subject: LCP Negotiation


Hi,

I have a question regarding LCP negotiation. These are the two
scenarios:

1. LAC does Proxy LCP with the remote system. LNS re-negotiates the
non-ACCM LCP parameters.
2. Only LNS negotiates LCP with the remote system.

Is there a way for LAC to know the negotiated LCP parameters except by
silent observation ?

I have tried to search for draft-ietf-l2tpext-link-00.txt hoping to find
answers there but cannot trace the draft.

Thanks in advance,
Sumati.

Sumati Mittal
GlobeSpan, Inc. 
Voice : (732) 345-6240
mailto:smittal@globespan.net
Web: http://www.globespan.net

------_=_NextPart_001_01C002F3.7C20D990
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2652.35">
<TITLE>RE: LCP Negotiation</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=2>As of now there is no mechanism to do it other than snooping. What specific parameters is the LAC interested in?</FONT>
</P>

<P><FONT SIZE=2>Rohit Verma</FONT>
<BR><FONT SIZE=2>Deloitte Consulting</FONT>
<BR><FONT SIZE=2>180, N. Stetson Avenue</FONT>
<BR><FONT SIZE=2>Chicago, Illinois 60601</FONT>
<BR><FONT SIZE=2>Phone: 312-374-2475</FONT>
</P>
<BR>

<P><FONT SIZE=2>-----Original Message-----</FONT>
<BR><FONT SIZE=2>From: Sumati Mittal [<A HREF="mailto:smittal@globespan.net">mailto:smittal@globespan.net</A>]</FONT>
<BR><FONT SIZE=2>Sent: Thursday, August 10, 2000 10:46 AM</FONT>
<BR><FONT SIZE=2>To: l2tp@ipsec.org</FONT>
<BR><FONT SIZE=2>Subject: LCP Negotiation</FONT>
</P>
<BR>

<P><FONT SIZE=2>Hi,</FONT>
</P>

<P><FONT SIZE=2>I have a question regarding LCP negotiation. These are the two</FONT>
<BR><FONT SIZE=2>scenarios:</FONT>
</P>

<P><FONT SIZE=2>1. LAC does Proxy LCP with the remote system. LNS re-negotiates the</FONT>
<BR><FONT SIZE=2>non-ACCM LCP parameters.</FONT>
<BR><FONT SIZE=2>2. Only LNS negotiates LCP with the remote system.</FONT>
</P>

<P><FONT SIZE=2>Is there a way for LAC to know the negotiated LCP parameters except by</FONT>
<BR><FONT SIZE=2>silent observation ?</FONT>
</P>

<P><FONT SIZE=2>I have tried to search for draft-ietf-l2tpext-link-00.txt hoping to find</FONT>
<BR><FONT SIZE=2>answers there but cannot trace the draft.</FONT>
</P>

<P><FONT SIZE=2>Thanks in advance,</FONT>
<BR><FONT SIZE=2>Sumati.</FONT>
</P>

<P><FONT SIZE=2>Sumati Mittal</FONT>
<BR><FONT SIZE=2>GlobeSpan, Inc. </FONT>
<BR><FONT SIZE=2>Voice : (732) 345-6240</FONT>
<BR><FONT SIZE=2><A HREF="mailto:smittal@globespan.net">mailto:smittal@globespan.net</A></FONT>
<BR><FONT SIZE=2>Web: <A HREF="http://www.globespan.net" TARGET="_blank">http://www.globespan.net</A></FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C002F3.7C20D990--


From owner-l2tp@diameter.org  Thu Aug 10 18:29:26 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15300
	for <l2tpext-archive@odin.ietf.org>; Thu, 10 Aug 2000 18:29:25 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e7AJjGN09823
	for l2tp-list; Thu, 10 Aug 2000 12:45:16 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from shako.cisco.com (shako.cisco.com [161.44.3.76])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e7AJiBd09817
	for <l2tp@l2tp.net>; Thu, 10 Aug 2000 12:44:11 -0700
Received: from cisco.com (rtp7-dhcp-58-134.cisco.com [161.44.58.134])
	by shako.cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id PAA03330;
	Thu, 10 Aug 2000 15:47:41 -0400 (EDT)
Message-ID: <399306F6.6B09021A@cisco.com>
Date: Thu, 10 Aug 2000 15:48:06 -0400
From: "W. Mark Townsley" <townsley@cisco.com>
X-Mailer: Mozilla 4.7 [en] (Win95; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: Bill Palter <palter@zev.net>
CC: l2tp@l2tp.net
Subject: Re: LCP Negotiation
References: <200008101657.JAA12017@zev.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Thanks, Bill. It seems that I issued last call on a couple of expired
drafts. I will reissue last call once the drafts are available.

Thanks,

- Mark

Bill Palter wrote:
> 
> 
>         I'll resubmit the link draft...
> 
> Bill
> 
> > Hi,
> >
> > I have a question regarding LCP negotiation. These are the two
> > scenarios:
> >
> > 1. LAC does Proxy LCP with the remote system. LNS re-negotiates the
> > non-ACCM LCP parameters.
> > 2. Only LNS negotiates LCP with the remote system.
> >
> > Is there a way for LAC to know the negotiated LCP parameters except by
> > silent observation ?
> >
> > I have tried to search for draft-ietf-l2tpext-link-00.txt hoping to find
> > answers there but cannot trace the draft.
> >
> > Thanks in advance,
> > Sumati.
> >
> > Sumati Mittal
> > GlobeSpan, Inc.
> > Voice : (732) 345-6240
> > mailto:smittal@globespan.net
> > Web: http://www.globespan.net
> --
> Bill Palter (Palter@zev.net)


From owner-l2tp@diameter.org  Thu Aug 10 20:56:01 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA17657
	for <l2tpext-archive@odin.ietf.org>; Thu, 10 Aug 2000 20:55:58 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e7ALidm09948
	for l2tp-list; Thu, 10 Aug 2000 14:44:39 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e7ALiad09942
	for <l2tp@l2tp.net>; Thu, 10 Aug 2000 14:44:36 -0700
Received: from dfw-smtpout2.email.verio.net (dfw-smtpout2.email.verio.net [129.250.36.42]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id OAA21779 for <l2tp@ipsec.org>; Thu, 10 Aug 2000 14:49:04 -0700 (PDT)
Received: from [129.250.38.64] (helo=dfw-mmp4.email.verio.net)
	by dfw-smtpout2.email.verio.net with esmtp (Exim 3.12 #7)
	id 13N0CE-0003eP-00; Thu, 10 Aug 2000 21:49:02 +0000
Received: from [209.21.27.82] (helo=rapid5.com)
	by dfw-mmp4.email.verio.net with esmtp (Exim 3.15 #4)
	id 13N0CE-00010v-00; Thu, 10 Aug 2000 21:49:02 +0000
Received: from srik ([10.1.1.143])
	by rapid5.com (8.9.1b+Sun/8.8.8) with SMTP id OAA16528;
	Thu, 10 Aug 2000 14:48:59 -0700 (PDT)
From: "Srikrishnan Subramanian" <srikrish@rapid5.com>
To: "Sumati Mittal" <smittal@globespan.net>,
        "Arthur Mistler" <amistler@erols.com>
Cc: <l2tp@ipsec.org>
Subject: RE: LCP Negotiation
Date: Thu, 10 Aug 2000 14:52:48 -0700
Message-ID: <NDBBJPNHOLJCLNDHELHBMECFCCAA.srikrish@rapid5.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
In-reply-to: <3993047C.1312ABF7@globespan.net>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Sumathi,

  According to RFC 2661, its only ACCM option. So we can
  assume (!!) that other options should not change.

  Best way to do it is to configure the LAC profiles based
  on LNS requirements. (which I guess will most of the implementations
  will do)

  Only other option in PPP which may cause problem is MRU.
  ( I am not considering MLPPP) MRU is driver capability and if
   it got changed in LNS re-negotiation, then there could be problem.
  Which I assume implementations (LNS) should make sure that, it
  wont cross the previously agreed upon value ( Which was given to
  LNS in proxy LCP packet)

  Hope this helps

Regards
Srikrishnan


-----Original Message-----
From: owner-l2tp@diameter.org [mailto:owner-l2tp@diameter.org]On Behalf
Of Sumati Mittal
Sent: Thursday, August 10, 2000 12:38 PM
To: Arthur Mistler
Cc: l2tp@ipsec.org
Subject: Re: LCP Negotiation


Arthur,

Thanks for your reply.

In both the methods you suggest, once LCP negotiation is done (whether
by LAC-remote system in method 1 or by LAC configuration in method 2),
it is not done again. However, in RFC 2661, the explanation of
Set-Link-Info section 6.14 says PPP options can change at any time
during the call, thus LAC must be able to update its internal call
information and behavior on an active PPP session.

Regards,
Sumati.

Arthur Mistler wrote:
>
> I may be way off base here because I'm not familiar with the link
extension
> draft you mentioned, however I see it exists because someone states
they'll
> repost it.
>
> But these are my impressions on your questions:
>
> 1. The LNS does not renegotiate any LCP parameters, once LCP is completed
> between the client and LAC, it can't be re-opened, and keeping the session
> in the negotiation phase between initial LAC negotiation, tunnel opening,
> then letting the LNS go with the client may be too lengthy and therefore
LCP
> on the client may time out.  So I completely establish the LCP session
> between the client and the LAC, and do a full proxy at the LNS, and if
there
> is an LCP option that the LNS really can't agree to, then the session
> fails.  This means that either your LNS needs to be very flexible, or you
> should at least have matching LCP option negotiation requirements for both
> LAC and LNS.  I haven't found it to be too much of a problem doing it this
> way.
>


> 2. This is what I call service routing, the first one which uses a proxy -
> most likely because you needed to authenticate, I call subscriber routing.
> Forgetting what I call them, though this second method I support by
> configuration.  In other words, my LAC has configuration settings per
access
> resource, or per caller ID, stuff like that, where a tunnel is always
opened
> for those certain class of calls, and then full negotiation of LCP is the
> responsibility of the LNS.  <I've found it useful to support both methods
1
> and 2.>
>
> The only way the LAC can know of the negotiate LCP parameters is either to
> do method 1, where it is an active participant in the negotiation, or as
you
> say, by silent observation.  But that implies you're using method 2, where
> all LCP negotiation is performed between the client and the LNS.  So in
> effect, the tunnel session is already open, so the only reason the LAC
would
> want to know anything about the LCP negotiated parameters would be for
> informational purposes only, and it really doesn't seem to be worth the
> bother.
>
> Hope this helps.
>
> - RT
> ==============================
> Artie Mistler
> President
> Advanced Software Consultants, Inc.
> 12 Gale Road
> Sutton, MA  01590
> (508) 581-9815
> mailto:amistler@erols.com
> http://www.erols.com/amistler/ascihome.html
> ==============================
>
> Sumati Mittal wrote:
>
> > Hi,
> >
> > I have a question regarding LCP negotiation. These are the two
> > scenarios:
> >
> > 1. LAC does Proxy LCP with the remote system. LNS re-negotiates the
> > non-ACCM LCP parameters.
> > 2. Only LNS negotiates LCP with the remote system.
> >
> > Is there a way for LAC to know the negotiated LCP parameters except by
> > silent observation ?
> >
> > I have tried to search for draft-ietf-l2tpext-link-00.txt hoping to find
> > answers there but cannot trace the draft.
> >
> > Thanks in advance,
> > Sumati.
> >
> > Sumati Mittal
> > GlobeSpan, Inc.
> > Voice : (732) 345-6240
> > mailto:smittal@globespan.net
> > Web: http://www.globespan.net



From owner-l2tp@diameter.org  Wed Aug 16 00:42:58 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA06944
	for <l2tpext-archive@odin.ietf.org>; Wed, 16 Aug 2000 00:42:57 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e7G1RiM21945
	for l2tp-list; Tue, 15 Aug 2000 18:27:44 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e7G1Rfd21939
	for <l2tp@l2tp.net>; Tue, 15 Aug 2000 18:27:41 -0700
Received: from dfw-smtpout1.email.verio.net (dfw-smtpout1.email.verio.net [129.250.36.41]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id SAA05115 for <l2tp@ipsec.org>; Tue, 15 Aug 2000 18:32:26 -0700 (PDT)
Received: from [129.250.38.62] (helo=dfw-mmp2.email.verio.net)
	by dfw-smtpout1.email.verio.net with esmtp (Exim 3.12 #7)
	id 13Os48-0003fP-00
	for l2tp@ipsec.org; Wed, 16 Aug 2000 01:32:24 +0000
Received: from [209.21.27.82] (helo=rapid5.com)
	by dfw-mmp2.email.verio.net with esmtp (Exim 3.15 #4)
	id 13Os48-0002e6-00
	for l2tp@ipsec.org; Wed, 16 Aug 2000 01:32:24 +0000
Received: from srik ([10.1.1.143])
	by rapid5.com (8.9.1b+Sun/8.8.8) with SMTP id SAA27714
	for <l2tp@ipsec.org>; Tue, 15 Aug 2000 18:32:19 -0700 (PDT)
X-Recipient: <l2tp@ipsec.org>
Deliver-To: <l2tp@ipsec.org>
From: "Srikrishnan Subramanian" <srikrish@rapid5.com>
To: "L2TP IPSEC" <l2tp@ipsec.org>
Subject: Anvil L2TP?
Date: Tue, 15 Aug 2000 18:36:32 -0700
Message-ID: <NDBBJPNHOLJCLNDHELHBKEDICCAA.srikrish@rapid5.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi Guys,

  Has anyone used Anvil's L2TP - PPP Stack for testing L2TP/PPP stacks?

  If anyone has used, can u please send how useful is that product?

Regards
Srikrishnan


From owner-l2tp@diameter.org  Wed Aug 16 05:30:55 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA20562
	for <l2tpext-archive@odin.ietf.org>; Wed, 16 Aug 2000 05:30:55 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e7G6gng22159
	for l2tp-list; Tue, 15 Aug 2000 23:42:49 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e7G6gjd22153
	for <l2tp@l2tp.net>; Tue, 15 Aug 2000 23:42:45 -0700
Received: from webveda.com (root@host-216-226-254-55.interpacket.net [216.226.254.55]) by ns1.sailpix.com (8.8.8/8.6.9) with SMTP id XAA05499 for <l2tp@ipsec.org>; Tue, 15 Aug 2000 23:47:26 -0700 (PDT)
Received: from webveda.com ([216.226.254.55]) by webveda.com ; Wed, 16 Aug 2000 20:45:56 -0400
From: "Shankar" <shankarv@webveda.com>
Reply-to: shankarv@webveda.com
To: l2tp@ipsec.org
Date: Wed, 16 Aug 2000 12:14:53 +0600
Subject: Outgoing call
X-Mailer: CWMail Web to Mail Gateway 2.5e, http://netwinsite.com/top_mail.htm
Message-id: <399b35c4.5021.0@webveda.com>
X-User-Info: 203.197.138.194
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



Hi gyz,

can a LAC make an outgoing call ?

tia
shankar
-------------------------------------------------
Make webveda your permanent address like i have.
Get 15 MB Free space only at http://www.webveda.com


From owner-l2tp@diameter.org  Wed Aug 16 09:27:44 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA24315
	for <l2tpext-archive@odin.ietf.org>; Wed, 16 Aug 2000 09:27:44 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e7GBNIm22575
	for l2tp-list; Wed, 16 Aug 2000 04:23:18 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e7GBN9d22569
	for <l2tp@l2tp.net>; Wed, 16 Aug 2000 04:23:10 -0700
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id EAA07102 for <l2tp@ipsec.org>; Wed, 16 Aug 2000 04:27:55 -0700 (PDT)
Received: from eastmail2.East.Sun.COM ([129.148.1.241])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id EAA28983;
	Wed, 16 Aug 2000 04:27:50 -0700 (PDT)
Received: from phorcys.east.sun.com (phorcys.East.Sun.COM [129.148.174.143])
	by eastmail2.East.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id HAA15983;
	Wed, 16 Aug 2000 07:27:49 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.9.3+Sun/8.9.3) id HAA11669;
	Wed, 16 Aug 2000 07:27:49 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14746.31413.193429.197633@gargle.gargle.HOWL>
Date: Wed, 16 Aug 2000 07:27:49 -0400 (EDT)
From: James Carlson <james.d.carlson@east.sun.com>
To: shankarv@webveda.com
Cc: l2tp@ipsec.org
Subject: Re: Outgoing call
In-Reply-To: Shankar's message of 16 August 2000 12:14:53
References: <399b35c4.5021.0@webveda.com>
X-Mailer: VM 6.75 under Emacs 20.7.1
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Shankar writes:
> can a LAC make an outgoing call ?

RFC 2661, section 5.2.2.

-- 
James Carlson, Internet Engineering       <james.d.carlson@east.sun.com>
SUN Microsystems / 1 Network Drive         71.234W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.497N   Fax +1 781 442 1677
"PPP Design and Debugging" --- http://people.ne.mediaone.net/carlson/ppp


From owner-l2tp@diameter.org  Wed Aug 16 13:08:46 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00351
	for <l2tpext-archive@odin.ietf.org>; Wed, 16 Aug 2000 13:08:45 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e7GESlb22811
	for l2tp-list; Wed, 16 Aug 2000 07:28:47 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e7GESCd22805
	for <l2tp@l2tp.net>; Wed, 16 Aug 2000 07:28:12 -0700
Received: from pita.cisco.com (pita.cisco.com [171.71.68.13]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id HAA07237 for <l2tp@ipsec.org>; Wed, 16 Aug 2000 07:32:48 -0700 (PDT)
From: kyork@cisco.com
Received: from cisco.com (show-129.cisco.com [171.68.213.129])
	by pita.cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id HAA00822;
	Wed, 16 Aug 2000 07:32:38 -0700 (PDT)
Message-ID: <399AA5B7.DE933ABE@cisco.com>
Date: Wed, 16 Aug 2000 07:31:19 -0700
X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.1 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Srikrishnan Subramanian <srikrish@rapid5.com>
CC: L2TP IPSEC <l2tp@ipsec.org>
Subject: Re: Anvil L2TP?
References: <NDBBJPNHOLJCLNDHELHBKEDICCAA.srikrish@rapid5.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Greetings,

Srikrishnan Subramanian wrote:
> 
> Hi Guys,
> 
>   Has anyone used Anvil's L2TP - PPP Stack for testing L2TP/PPP stacks?
> 
>   If anyone has used, can u please send how useful is that product?
> 

Unless they've made <major> changes in the last year, this product,
though excellent for PPP, is absolutely useless for L2TP

-- 
Kyle A. York
Subordinate Grunt
CLOB


From owner-l2tp@diameter.org  Wed Aug 16 15:01:28 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA02298
	for <l2tpext-archive@odin.ietf.org>; Wed, 16 Aug 2000 15:01:27 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e7GH0VU22904
	for l2tp-list; Wed, 16 Aug 2000 10:00:31 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e7GH0Sd22898
	for <l2tp@l2tp.net>; Wed, 16 Aug 2000 10:00:28 -0700
Received: from sanjose.broadpac.com (adsl-63-199-87-5.dsl.snfc21.pacbell.net [63.199.87.5]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id KAA07410 for <l2tp@ipsec.org>; Wed, 16 Aug 2000 10:05:15 -0700 (PDT)
Received: by sanjose.broadpac.com with Internet Mail Service (5.5.2650.21)
	id <Q03NTGBW>; Wed, 16 Aug 2000 10:03:10 -0700
Message-ID: <517244DCC735D411A9BF00E029309B37015AEE@sanjose.broadpac.com>
From: Ruchir Malhotra <ruchir@broadpac.com>
To: "'Srikrishnan Subramanian'" <srikrish@rapid5.com>,
        L2TP IPSEC
	 <l2tp@ipsec.org>
Subject: RE: Anvil L2TP?
Date: Wed, 16 Aug 2000 10:03:09 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-l2tp@diameter.org
Precedence: bulk

Hi Srikrishnan,
We have been using Anvil testing software for the past few months, and it
has helped us a lot in detecting bugs in the PPP, L2TP and PPTP modules. The
test cases are quite thorough, and they bring out the small mistakes which
one might generally overlook.

Regards
Ruchir Malhotra

-----Original Message-----
From: Srikrishnan Subramanian [mailto:srikrish@rapid5.com]
Sent: Tuesday, August 15, 2000 6:37 PM
To: L2TP IPSEC
Subject: Anvil L2TP?


Hi Guys,

  Has anyone used Anvil's L2TP - PPP Stack for testing L2TP/PPP stacks?

  If anyone has used, can u please send how useful is that product?

Regards
Srikrishnan


From owner-l2tp@diameter.org  Wed Aug 16 15:49:25 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03074
	for <l2tpext-archive@odin.ietf.org>; Wed, 16 Aug 2000 15:49:24 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e7GG7Bs22870
	for l2tp-list; Wed, 16 Aug 2000 09:07:11 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e7GG79d22864
	for <l2tp@l2tp.net>; Wed, 16 Aug 2000 09:07:09 -0700
Received: from jasmine.vif.com (mail.vif.net [205.205.128.153]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id JAA07347 for <l2tp@ipsec.org>; Wed, 16 Aug 2000 09:11:56 -0700 (PDT)
From: talist@vif.com
Received: from shan (IP station [216.94.204.137]) by jasmine.vif.com
 (Sendmail  SMTPRA 4.1.0) with SMTP id <B0006223235@jasmine.vif.com> for <l2tp@ipsec.org>;
 Wed, 16 Aug 2000 12:11:00 -0400
Message-ID: <003b01c0079c$87e77740$89cc5ed8@shan>
To: <l2tp@ipsec.org>
Subject: current RFC for RedBack SMS
Date: Wed, 16 Aug 2000 12:10:43 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I am looking for the RFC or DRAFT number that a REDBACK SMS1000 is supposed
to be following for L2TP
FIRMWARE_REV=16809998
AOS 3.1.4.33





From owner-l2tp@diameter.org  Wed Aug 16 17:08:39 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04031
	for <l2tpext-archive@odin.ietf.org>; Wed, 16 Aug 2000 17:08:38 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e7GIgPN22998
	for l2tp-list; Wed, 16 Aug 2000 11:42:25 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e7GIgMd22992
	for <l2tp@l2tp.net>; Wed, 16 Aug 2000 11:42:22 -0700
Received: from stn.springtidenet.com (stn.springtidenet.com [63.88.111.246]) by ns1.sailpix.com (8.8.8/8.6.9) with SMTP id LAA07480 for <l2tp@ipsec.org>; Wed, 16 Aug 2000 11:47:09 -0700 (PDT)
Received: from stn15.springtidenet.com by stn.springtidenet.com
          via smtpd (for mail1.sailpix.com [155.53.1.248]) with SMTP; 16 Aug 2000 18:47:09 UT
Received: from 172.16.6.11 by stn15.springtidenet.com (InterScan E-Mail VirusWall NT); Wed, 16 Aug 2000 14:42:57 -0400 (Eastern Daylight Time)
Received: from sol.springtidenet.com (sol.springtidenet.com [172.20.20.4])
	by stn11.springtidenet.com (Build 101 8.9.3/NT-8.9.3) with ESMTP id OAA20790;
	Wed, 16 Aug 2000 14:48:24 -0400
Received: by sol.springtidenet.com with Internet Mail Service (5.5.2650.21)
	id <Q0WJTSBS>; Wed, 16 Aug 2000 14:48:21 -0400
Message-ID: <F10A2DA74539D311BD67009027719FD293080D@sol.springtidenet.com>
From: "Phaneuf, Brian" <bphaneuf@springtidenet.com>
To: "'Ruchir Malhotra'" <ruchir@broadpac.com>,
        "'Srikrishnan Subramanian'"
	 <srikrish@rapid5.com>,
        L2TP IPSEC <l2tp@ipsec.org>
Subject: RE: Anvil L2TP?
Date: Wed, 16 Aug 2000 14:48:21 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-l2tp@diameter.org
Precedence: bulk

I have used the test suite as well. It was useful, but it had
quite a few bugs. ANVL/Midnight/Hammer has reportedly fixed quite
a number of them.

One note of caution: If you attempt to "pass" all of the negative
defensive tests, you are likely to have interoperability problems
with all but the most militantly conformant L2TP implementations.


-----Original Message-----
From: Ruchir Malhotra [mailto:ruchir@broadpac.com]
Sent: Wednesday, August 16, 2000 1:03 PM
To: 'Srikrishnan Subramanian'; L2TP IPSEC
Subject: RE: Anvil L2TP?


Hi Srikrishnan,
We have been using Anvil testing software for the past few months, and it
has helped us a lot in detecting bugs in the PPP, L2TP and PPTP modules. The
test cases are quite thorough, and they bring out the small mistakes which
one might generally overlook.

Regards
Ruchir Malhotra

-----Original Message-----
From: Srikrishnan Subramanian [mailto:srikrish@rapid5.com]
Sent: Tuesday, August 15, 2000 6:37 PM
To: L2TP IPSEC
Subject: Anvil L2TP?


Hi Guys,

  Has anyone used Anvil's L2TP - PPP Stack for testing L2TP/PPP stacks?

  If anyone has used, can u please send how useful is that product?

Regards
Srikrishnan


From owner-l2tp@diameter.org  Wed Aug 16 18:43:23 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04797
	for <l2tpext-archive@odin.ietf.org>; Wed, 16 Aug 2000 18:43:23 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e7GJgA623067
	for l2tp-list; Wed, 16 Aug 2000 12:42:10 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e7GJg7d23061
	for <l2tp@l2tp.net>; Wed, 16 Aug 2000 12:42:07 -0700
Received: from stile.redback.com (stile.redback.com [155.53.36.12]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id MAA07624 for <l2tp@ipsec.org>; Wed, 16 Aug 2000 12:46:55 -0700 (PDT)
Received: (from suhail@localhost)
	by stile.redback.com (8.8.8/8.8.8) id MAA02580;
	Wed, 16 Aug 2000 12:46:23 -0700 (PDT)
From: Suhail Nanji <suhail@redback.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Wed, 16 Aug 2000 12:46:23 -0700 (PDT)
To: talist@vif.com
Cc: <l2tp@ipsec.org>
Subject: Re: current RFC for RedBack SMS
In-Reply-To: <003b01c0079c$87e77740$89cc5ed8@shan>
References: <003b01c0079c$87e77740$89cc5ed8@shan>
X-Mailer: VM 6.43 under 21.1 (patch 9) "Canyonlands" XEmacs Lucid
Message-ID: <14746.61259.570151.169375@stile.redback.com>
Reply-To: suhail@redback.com (Suhail Nanji)
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


The implementation is compliant the RFC 2661.

Suhail

talist@vif.com writes:
> I am looking for the RFC or DRAFT number that a REDBACK SMS1000 is supposed
> to be following for L2TP
> FIRMWARE_REV=16809998
> AOS 3.1.4.33
> 
> 
> 


From owner-l2tp@diameter.org  Thu Aug 17 15:54:59 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03733
	for <l2tpext-archive@odin.ietf.org>; Thu, 17 Aug 2000 15:54:58 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e7HH1KW23834
	for l2tp-list; Thu, 17 Aug 2000 10:01:20 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e7HH1Cd23828
	for <l2tp@l2tp.net>; Thu, 17 Aug 2000 10:01:12 -0700
Received: from mail.yourdomain.com (m319-mp1-cvx1a.man.ntl.com [62.252.197.63]) by ns1.sailpix.com (8.8.8/8.6.9) with SMTP id KAA09955 for <l2tp@ipsec.org>; Thu, 17 Aug 2000 10:05:47 -0700 (PDT)
From: announce@leisurewebcams.com
Message-Id: <200008171705.KAA09955@ns1.sailpix.com>
Date: Thu, 17 Aug 2000 14:30:16
To: <l2tp@ipsec.org>
Subject: LeisureWebcams.com - See the World
Sender: owner-l2tp@diameter.org
Precedence: bulk

LeisureWebcams.com is a recently launched website
specialising in providing free LIVE access to over
1,500 webcams and 2,000 Tourist Offices world wide.

Check it out:-

http://www.leisurewebcams.com/

This offers you the chance to check out live and
frequently updated images of your chosen location
through the webcams and get detailed local knowledge
through the Tourist Offices. Along with booking
holidays direct through our travel partner, there is
the opportunity to sell your unwanted clothes and
equipment through our free Swap Shop.

There is a lot to see, so if you have enjoyed your
trip through our site, do tell your friends and let
us know through 'Your Views'. If you have any
suggestions for the site, or queries, please feel
free to contact me at cy@LeisureWebcams.com.

I look forward to hearing from you.

Kind regards,

Charlie Yates
MARKETING DIRECTOR
LeisureWebcams.com
 
 
 
 
 
 
 
 
 
 


From owner-l2tp@diameter.org  Fri Aug 18 20:03:41 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA10961
	for <l2tpext-archive@odin.ietf.org>; Fri, 18 Aug 2000 20:03:41 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e7IKqC124967
	for l2tp-list; Fri, 18 Aug 2000 13:52:12 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e7IKq9W24961
	for <l2tp@l2tp.net>; Fri, 18 Aug 2000 13:52:09 -0700
Received: from dfw-smtpout2.email.verio.net (dfw-smtpout2.email.verio.net [129.250.36.42]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id NAA12532 for <l2tp@ipsec.org>; Fri, 18 Aug 2000 13:56:50 -0700 (PDT)
Received: from [129.250.38.64] (helo=dfw-mmp4.email.verio.net)
	by dfw-smtpout2.email.verio.net with esmtp (Exim 3.12 #7)
	id 13PtC4-0000kx-00
	for l2tp@ipsec.org; Fri, 18 Aug 2000 20:56:48 +0000
Received: from [209.21.27.82] (helo=rapid5.com)
	by dfw-mmp4.email.verio.net with esmtp (Exim 3.15 #4)
	id 13PtC3-0005Uk-00
	for l2tp@ipsec.org; Fri, 18 Aug 2000 20:56:47 +0000
Received: from srik ([10.1.1.143])
	by rapid5.com (8.9.1b+Sun/8.8.8) with SMTP id NAA29247
	for <l2tp@ipsec.org>; Fri, 18 Aug 2000 13:56:40 -0700 (PDT)
X-Recipient: <l2tp@ipsec.org>
Deliver-To: <l2tp@ipsec.org>
From: "Srikrishnan Subramanian" <srikrish@rapid5.com>
To: "L2TP IPSEC" <l2tp@ipsec.org>
Subject: L2TP Test Utility
Date: Fri, 18 Aug 2000 14:00:59 -0700
Message-ID: <NDBBJPNHOLJCLNDHELHBOEELCCAA.srikrish@rapid5.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi guys,

  Thanks for your responses on Anvil L2TP/PPP.

  I heard mixed response for Anvil L2TP Test suite.
  But most said, its not very good.

  Do u guys know any other test suite which can be
  used to test L2TP/PPP implementation?

  Or whatz the common way used to test L2TP (LAC/LNS) & PPP? 
  Is it tested directly with available products?

Thanks in Advance,
-Sriks


From owner-l2tp@diameter.org  Mon Aug 21 10:31:41 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01534
	for <l2tpext-archive@odin.ietf.org>; Mon, 21 Aug 2000 10:31:36 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e7LBJaK32344
	for l2tp-list; Mon, 21 Aug 2000 04:19:36 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e7LBJMW32338
	for <l2tp@l2tp.net>; Mon, 21 Aug 2000 04:19:23 -0700
Received: from cvis29.marconicomms.com (cvis29.marconicomms.com [195.99.244.61]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id EAA19108 for <l2tp@ipsec.org>; Mon, 21 Aug 2000 04:24:24 -0700 (PDT)
Received: from cvis01.gpt.co.uk (cvis01.gpt.co.uk) by cvis29.marconicomms.com
 (Content Technologies SMTPRS 4.1.5) with ESMTP id <Tc363f43db64e29cb169f@cvis29.marconicomms.com>;
 Mon, 21 Aug 2000 12:23:44 +0100
Received: from marconicomms.com by cvis01.gpt.co.uk with SMTP
 (8.8.8+Sun/cvms-28) id MAA26558; Mon, 21 Aug 2000 12:23:42 +0100 (BST)
Received: by marconicomms.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 80256942.003E9580 ; Mon, 21 Aug 2000 12:23:35 +0100
X-Lotus-FromDomain: MCMAIN@MCEXT
From: "Federica Anfosso" <Federica.Anfosso@marconi.com>
To: "Phaneuf, Brian" <bphaneuf@springtidenet.com>
cc: l2tp@ipsec.org
Message-ID: <80256942.003E42ED.00@marconicomms.com>
Date: Mon, 21 Aug 2000 13:19:55 +0200
Subject: RE: Anvil L2TP?
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-l2tp@diameter.org
Precedence: bulk



Hi,
since I am going to use ANVL L2TP test suite to test a LAC, could you be so kind
to better explain me what you mean with "interoperability problems with all but
the most militantly conformant L2TP implementations"?
Thanks a lot, Federica Anfosso



I have used the test suite as well. It was useful, but it had
quite a few bugs. ANVL/Midnight/Hammer has reportedly fixed quite
a number of them.

One note of caution: If you attempt to "pass" all of the negative
defensive tests, you are likely to have interoperability problems
with all but the most militantly conformant L2TP implementations.


-----Original Message-----
From: Ruchir Malhotra [mailto:ruchir@broadpac.com]
Sent: Wednesday, August 16, 2000 1:03 PM
To: 'Srikrishnan Subramanian'; L2TP IPSEC
Subject: RE: Anvil L2TP?


Hi Srikrishnan,
We have been using Anvil testing software for the past few months, and it
has helped us a lot in detecting bugs in the PPP, L2TP and PPTP modules. The
test cases are quite thorough, and they bring out the small mistakes which
one might generally overlook.

Regards
Ruchir Malhotra

-----Original Message-----
From: Srikrishnan Subramanian [mailto:srikrish@rapid5.com]
Sent: Tuesday, August 15, 2000 6:37 PM
To: L2TP IPSEC
Subject: Anvil L2TP?


Hi Guys,

  Has anyone used Anvil's L2TP - PPP Stack for testing L2TP/PPP stacks?

  If anyone has used, can u please send how useful is that product?

Regards
Srikrishnan







From owner-l2tp@diameter.org  Mon Aug 21 12:23:11 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04065
	for <l2tpext-archive@odin.ietf.org>; Mon, 21 Aug 2000 12:23:11 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e7LDWr332412
	for l2tp-list; Mon, 21 Aug 2000 06:32:53 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e7LDWoW32406
	for <l2tp@l2tp.net>; Mon, 21 Aug 2000 06:32:50 -0700
Received: from stn.springtidenet.com ([63.88.111.246]) by ns1.sailpix.com (8.8.8/8.6.9) with SMTP id GAA19179 for <l2tp@ipsec.org>; Mon, 21 Aug 2000 06:37:53 -0700 (PDT)
Received: from stn15.springtidenet.com by stn.springtidenet.com
          via smtpd (for mail1.sailpix.com [155.53.1.248]) with SMTP; 21 Aug 2000 13:37:52 UT
Received: from 172.16.6.11 by stn15.springtidenet.com (InterScan E-Mail VirusWall NT); Mon, 21 Aug 2000 09:33:27 -0400 (Eastern Daylight Time)
Received: from sol.springtidenet.com (sol.springtidenet.com [172.20.20.4])
	by stn11.springtidenet.com (Build 101 8.9.3/NT-8.9.3) with ESMTP id JAA29947;
	Mon, 21 Aug 2000 09:39:13 -0400
Received: by sol.springtidenet.com with Internet Mail Service (5.5.2650.21)
	id <Q0WJT5YJ>; Mon, 21 Aug 2000 09:38:58 -0400
Message-ID: <F10A2DA74539D311BD67009027719FD2930822@sol.springtidenet.com>
From: "Phaneuf, Brian" <bphaneuf@springtidenet.com>
To: "'Federica Anfosso'" <Federica.Anfosso@marconi.com>,
        "Phaneuf, Brian"
	 <bphaneuf@springtidenet.com>
Cc: l2tp@ipsec.org
Subject: RE: Anvil L2TP?
Date: Mon, 21 Aug 2000 09:38:57 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-l2tp@diameter.org
Precedence: bulk

By attempting to pass all of the ANVL tests which
sent L2TP messages that were technically in violation
of the spec, we had problems interoperating some other
implementations which weren't as strict in what they sent
or perhaps had a slightly different interpretation of what
was compliant.

After a few minor changes made at the bake off and by 
adopting the "be strict in what you send and liberal in what
you receive" philosophy, we were able to interoperate
quite well.


-----Original Message-----
From: Federica Anfosso [mailto:Federica.Anfosso@marconi.com]
Sent: Monday, August 21, 2000 7:20 AM
To: Phaneuf, Brian
Cc: l2tp@ipsec.org
Subject: RE: Anvil L2TP?




Hi,
since I am going to use ANVL L2TP test suite to test a LAC, could you be so
kind
to better explain me what you mean with "interoperability problems with all
but
the most militantly conformant L2TP implementations"?
Thanks a lot, Federica Anfosso



I have used the test suite as well. It was useful, but it had
quite a few bugs. ANVL/Midnight/Hammer has reportedly fixed quite
a number of them.

One note of caution: If you attempt to "pass" all of the negative
defensive tests, you are likely to have interoperability problems
with all but the most militantly conformant L2TP implementations.


-----Original Message-----
From: Ruchir Malhotra [mailto:ruchir@broadpac.com]
Sent: Wednesday, August 16, 2000 1:03 PM
To: 'Srikrishnan Subramanian'; L2TP IPSEC
Subject: RE: Anvil L2TP?


Hi Srikrishnan,
We have been using Anvil testing software for the past few months, and it
has helped us a lot in detecting bugs in the PPP, L2TP and PPTP modules. The
test cases are quite thorough, and they bring out the small mistakes which
one might generally overlook.

Regards
Ruchir Malhotra

-----Original Message-----
From: Srikrishnan Subramanian [mailto:srikrish@rapid5.com]
Sent: Tuesday, August 15, 2000 6:37 PM
To: L2TP IPSEC
Subject: Anvil L2TP?


Hi Guys,

  Has anyone used Anvil's L2TP - PPP Stack for testing L2TP/PPP stacks?

  If anyone has used, can u please send how useful is that product?

Regards
Srikrishnan






From owner-l2tp@diameter.org  Mon Aug 21 18:09:19 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA10256
	for <l2tpext-archive@odin.ietf.org>; Mon, 21 Aug 2000 18:09:19 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e7LJ9QL00361
	for l2tp-list; Mon, 21 Aug 2000 12:09:26 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e7LJ9NW00355
	for <l2tp@l2tp.net>; Mon, 21 Aug 2000 12:09:23 -0700
Received: from mailsrv.acc.com (mailsrv.acc.com [129.192.64.128]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id MAA19476 for <l2tp@ipsec.org>; Mon, 21 Aug 2000 12:14:27 -0700 (PDT)
Received: from acc.com (evanhome.acc.com [129.192.23.98])
	by mailsrv.acc.com (8.9.3/8.9.1) with ESMTP id MAA20715
	for <l2tp@ipsec.org>; Mon, 21 Aug 2000 12:17:49 -0700 (PDT)
Message-ID: <39A02DD0.3DF89543@acc.com>
Date: Sun, 20 Aug 2000 12:13:20 -0700
From: Evan Caves <evan@acc.com>
X-Mailer: Mozilla 4.5 [en]C-CCK-MCD {Firstrade Securities Inc.}  (Win98; I)
X-Accept-Language: en,zh
MIME-Version: 1.0
To: l2tp@ipsec.org
Subject: L2TP Diffserv Draft
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Is this draft going anywhere?

evan
-


From owner-l2tp@diameter.org  Tue Aug 22 11:15:27 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08166
	for <l2tpext-archive@odin.ietf.org>; Tue, 22 Aug 2000 11:15:27 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e7MBmS001361
	for l2tp-list; Tue, 22 Aug 2000 04:48:28 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from e2.ny.us.ibm.com (e2.ny.us.ibm.com [32.97.182.102])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e7MBmHW01355
	for <l2tp@diameter.org>; Tue, 22 Aug 2000 04:48:18 -0700
Received: from northrelay02.pok.ibm.com (northrelay02.pok.ibm.com [9.117.200.22])
	by e2.ny.us.ibm.com (8.9.3/8.9.3) with ESMTP id HAA62550
	for <l2tp@diameter.org>; Tue, 22 Aug 2000 07:50:36 -0400
From: streifer@us.ibm.com
Received: from D51MTA06.pok.ibm.com (d51mta06.pok.ibm.com [9.117.200.34])
	by northrelay02.pok.ibm.com (8.8.8m3/NCO v4.93) with SMTP id HAA49804
	for <l2tp@diameter.org>; Tue, 22 Aug 2000 07:50:41 -0400
Received: by D51MTA06.pok.ibm.com(Lotus SMTP MTA v4.6.5  (863.2 5-20-1999))  id 85256943.00410D75 ; Tue, 22 Aug 2000 07:50:32 -0400
X-Lotus-FromDomain: IBMUS
To: l2tp@diameter.org
Message-ID: <85256943.00410C04.00@D51MTA06.pok.ibm.com>
Date: Tue, 22 Aug 2000 06:50:46 -0500
Subject: L2TP Tunnel Authentication with RADIUS
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-l2tp@diameter.org
Precedence: bulk


Are there any L2TP implementations that use RADIUS for L2TP tunnel
authentication ?

Looking through the various RADIUS RFCs it looks like RADIUS can be used
for PPP authentication after the tunnel and call are established but I
can't see a way to get a RADIUS Server to send back a MD5 Hash value or a
password to use for a Challenge-Response for tunnel authentication. There
is a Tunnel-Password attribute but it is only sent back in an Access-Accept
packet. From an LNS standpoint it looks to me that I would need a tunnel
password stored locally in order to generate a Challenge-Response which
would defeat the purpose of using RADIUS to consolidate authentication
administration to a single system.

Am I missing something ?


Thanks,

Kurt Streifert
IBM AS/400 Endicott Programming Lab




From owner-l2tp@diameter.org  Tue Aug 22 14:58:31 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13118
	for <l2tpext-archive@odin.ietf.org>; Tue, 22 Aug 2000 14:58:31 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e7MFlML01739
	for l2tp-list; Tue, 22 Aug 2000 08:47:22 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from franklin.cisco.com (franklin.cisco.com [171.70.156.17])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e7MFlHW01733
	for <l2tp@diameter.org>; Tue, 22 Aug 2000 08:47:17 -0700
Received: from gwz (ssh.cisco.com [171.69.10.34]) by franklin.cisco.com (8.8.6 (PHNE_17190)/CISCO.SERVER.1.2) with SMTP id IAA06686; Tue, 22 Aug 2000 08:49:18 -0700 (PDT)
Reply-To: <gwz@cisco.com>
From: "Glen Zorn" <gwz@cisco.com>
To: <streifer@us.ibm.com>
Cc: <l2tp@diameter.org>, <gwz@cisco.com>
Subject: RE: L2TP Tunnel Authentication with RADIUS
Date: Tue, 22 Aug 2000 08:47:20 -0700
Message-ID: <NDBBIHMPILAAGDHPCIOPCEMHCKAA.gwz@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Importance: Normal
In-Reply-To: <85256943.00410C04.00@D51MTA06.pok.ibm.com>
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

streifer@us.ibm.com writes:

> Are there any L2TP implementations that use RADIUS for L2TP tunnel
> authentication ?
>
> Looking through the various RADIUS RFCs it looks like RADIUS can be used
> for PPP authentication after the tunnel and call are established but I
> can't see a way to get a RADIUS Server to send back a MD5 Hash value or a
> password to use for a Challenge-Response for tunnel authentication.

There isn't any need.  L2TP tunnel authentication works just the same as
CHAP; you can use the same RADIUS attributes and the same method as you
would for PPP.

> There
> is a Tunnel-Password attribute but it is only sent back in an
> Access-Accept
> packet. From an LNS standpoint it looks to me that I would need a tunnel
> password stored locally in order to generate a Challenge-Response which
> would defeat the purpose of using RADIUS to consolidate authentication
> administration to a single system.
>
> Am I missing something ?
>
>
> Thanks,
>
> Kurt Streifert
> IBM AS/400 Endicott Programming Lab
>
>
>



From owner-l2tp@diameter.org  Tue Aug 22 15:41:36 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14301
	for <l2tpext-archive@odin.ietf.org>; Tue, 22 Aug 2000 15:41:35 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e7MGZDA01835
	for l2tp-list; Tue, 22 Aug 2000 09:35:13 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from center.mshindo.net (center.mshindo.net [210.231.221.221])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e7MGZ8W01829
	for <l2tp@diameter.org>; Tue, 22 Aug 2000 09:35:09 -0700
Received: from cosinecom.com (pl007.nas911.n-yokohama.nttpc.ne.jp [210.139.55.7])
	by center.mshindo.net (8.9.3/3.7W/00041811) with SMTP id BAA14464;
	Wed, 23 Aug 2000 01:31:21 +0900 (JST)
Date: Wed, 23 Aug 2000 01:38:13 +0900 (JST)
Message-Id: <20000823.013813.104026357.mshindo@mshindo.net>
To: streifer@us.ibm.com
Cc: l2tp@diameter.org
Subject: Re: L2TP Tunnel Authentication with RADIUS
From: Motonori Shindo <mshindo@mshindo.net>
In-Reply-To: <85256943.00410C04.00@D51MTA06.pok.ibm.com>
References: <85256943.00410C04.00@D51MTA06.pok.ibm.com>
X-Mailer: Mew version 1.95b30 on XEmacs 21.1 (Canyonlands)
X-PGP-fingerprint: 06 B0 B1 A4 06 C1 6A 14  63 C0 D7 18 01 CD D9 83
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,

AFAIK, Lucent TNT (as a LAC) can make use of RADIUS for tunnel
authentication using Tunnel-Password attribute. I haven't tested
myself the LNS side of Lucent products, but I assume it can. There
seems to be several other vendors that support Tunnel-Password, but be
aware that some of them don't support encrypted Tunnel-Password. Of
course, RADIUS server has to support Tunnel-Password encryption to
make the whole system works. Ascend Free RADIUS and Lucent NavisRADIUS
do support Tunnel-Password encyption.

Regards,

From: streifer@us.ibm.com
Subject: L2TP Tunnel Authentication with RADIUS
Date: Tue, 22 Aug 2000 06:50:46 -0500

> Are there any L2TP implementations that use RADIUS for L2TP tunnel
> authentication ?
> 
> Looking through the various RADIUS RFCs it looks like RADIUS can be used
> for PPP authentication after the tunnel and call are established but I
> can't see a way to get a RADIUS Server to send back a MD5 Hash value or a
> password to use for a Challenge-Response for tunnel authentication. There
> is a Tunnel-Password attribute but it is only sent back in an Access-Accept
> packet. From an LNS standpoint it looks to me that I would need a tunnel
> password stored locally in order to generate a Challenge-Response which
> would defeat the purpose of using RADIUS to consolidate authentication
> administration to a single system.
> 
> Am I missing something ?
> 
> 
> Thanks,
> 
> Kurt Streifert
> IBM AS/400 Endicott Programming Lab

=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=
 +----+----+     
 |.. .|    |     Motonori Shindo
 |_~__|    |     
 | .. |~~_~|     Sr. Systems Engineer
 | .  |    |     CoSine Communications Inc.
 +----+----+     
 C o S i n e     e-mail:  mshindo@cosinecom.com 
Communications
=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=


From owner-l2tp@diameter.org  Tue Aug 22 16:26:27 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15066
	for <l2tpext-archive@odin.ietf.org>; Tue, 22 Aug 2000 16:26:26 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e7MHdF201892
	for l2tp-list; Tue, 22 Aug 2000 10:39:15 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from h006008986325.ne.mediaone.net (h006008986325.ne.mediaone.net [24.218.16.153])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e7MHdAW01886
	for <l2tp@diameter.org>; Tue, 22 Aug 2000 10:39:10 -0700
Received: (from carlson@localhost)
	by h006008986325.ne.mediaone.net (8.9.3/8.9.3) id NAA16482;
	Tue, 22 Aug 2000 13:44:17 -0400
From: James Carlson <carlson@workingcode.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14754.48112.886636.194366@h006008986325.ne.mediaone.net>
Date: Tue, 22 Aug 2000 13:44:16 -0400 (EDT)
To: streifer@us.ibm.com
Cc: l2tp@diameter.org
Subject: Re: L2TP Tunnel Authentication with RADIUS
In-Reply-To: streifer@us.ibm.com's message of 22 August 2000 06:50:46
References: <85256943.00410C04.00@D51MTA06.pok.ibm.com>
X-Mailer: VM 6.75 under Emacs 20.6.1
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

streifer@us.ibm.com writes:
> From an LNS standpoint it looks to me that I would need a tunnel
> password stored locally in order to generate a Challenge-Response which
> would defeat the purpose of using RADIUS to consolidate authentication
> administration to a single system.
> 
> Am I missing something ?

Nope.  This is the same problem as with RADIUS for regular CHAP --
RADIUS doesn't support the authenticatee (aka "client") role; only
authenticator.

Yes, you need either a locally-stored password, a RADIUS extension, or
a different authentication protocol.

-- 
James Carlson                                  <carlson@workingcode.com>
"PPP Design and Debugging" --- http://people.ne.mediaone.net/carlson/ppp


From owner-l2tp@diameter.org  Tue Aug 22 17:28:14 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16188
	for <l2tpext-archive@odin.ietf.org>; Tue, 22 Aug 2000 17:28:13 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e7MInSI01974
	for l2tp-list; Tue, 22 Aug 2000 11:49:28 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e7MInOW01968
	for <l2tp@l2tp.net>; Tue, 22 Aug 2000 11:49:24 -0700
Received: from fcs-nt1.futsoft.com (fcs-nt1.futsoft.com [38.242.189.2]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id LAA22172 for <l2tp@ipsec.org>; Tue, 22 Aug 2000 11:54:31 -0700 (PDT)
Received: from sanjose.futsoft.com (unverified) by fcs-nt1.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with SMTP id <B0000126214@fcs-nt1.futsoft.com> for <l2tp@ipsec.org>;
 Tue, 22 Aug 2000 11:38:16 -0700
Received: from rajeshs ([38.242.189.59])
	by sanjose.futsoft.com (8.9.3/8.8.7) with SMTP id KAA02571
	for <l2tp@ipsec.org>; Tue, 22 Aug 2000 10:47:01 -0700
Received: by localhost with Microsoft MAPI; Tue, 22 Aug 2000 12:11:08 -0700
Message-Id: <01C00C32.0DA6B0A0.rajeshs@futsoft.com>
From: Rajesh Kumar <rajeshs@futsoft.com>
Reply-To: "rajeshs@futsoft.com" <rajeshs@futsoft.com>
To: "'l2tp@ipsec.org'" <l2tp@ipsec.org>
Subject: Is an outgoing call useful at a DSL LAC?
Date: Tue, 22 Aug 2000 12:11:07 -0700
Organization: Future Communications Software
X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

(1) How useful is a LAC with completely DSL access lines for subscribers (no dialup access at the LAC)? What would typical applications be?

(2) For a LAC positioned at DSL access, is support for outgoing calls useful? What would typical applications be?


Thanks
Rajesh


From owner-l2tp@diameter.org  Wed Aug 23 02:00:42 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA29974
	for <l2tpext-archive@odin.ietf.org>; Wed, 23 Aug 2000 02:00:39 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e7N2JcI02407
	for l2tp-list; Tue, 22 Aug 2000 19:19:38 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from otherland.dyndns.org (IDENT:root@[209.141.29.236])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e7N2JXW02401
	for <l2tp@diameter.org>; Tue, 22 Aug 2000 19:19:34 -0700
Received: from foobar ([10.10.10.3])
	by otherland.dyndns.org (8.9.3/8.9.3) with SMTP id VAA05068
	for <l2tp@diameter.org>; Tue, 22 Aug 2000 21:23:32 -0500
Message-ID: <003201c00ca9$23cb3460$030a0a0a@dyndns.org>
From: "Mike Wronski" <mike@wronski.net>
To: <l2tp@diameter.org>
Subject: Strange AVP's from RedBack DSLAM
Date: Tue, 22 Aug 2000 21:23:34 -0500
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_002F_01C00C7F.3A768680"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.3018.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300
Sender: owner-l2tp@diameter.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_002F_01C00C7F.3A768680
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I am attempting to get a RedBack DSLAM (SMS1000) acting as LAC to =
terminate sessions on a 3Com HiPer ARC (LNS). The Session open coming =
from the DSLAM has AVP's 43,44,& 46.. I found 44 & 46 in a extension =
draft written by a member of RedBack.. I cant figure out what 43 is but =
it is causing the HiPer ARC to attempt to renegotiate SPI.. When this =
happens the Redback complains about invalid lenght of AVP's.. After =
looking at the packet sent from the HARC I can see no problem with the =
lengths in any of the data fields..  Can anyone shed some light on what =
AVP #43 is and where it is documented? Also if you have had some success =
with redback and 3com HiPer ARC please forward that along as well..

-M


------=_NextPart_000_002F_01C00C7F.3A768680
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.3019.2500" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>I am attempting to get a RedBack DSLAM =
(SMS1000)=20
acting as LAC to terminate sessions on a 3Com HiPer ARC (LNS). The =
Session open=20
coming from the DSLAM has AVP's 43,44,&amp; 46.. I found 44 &amp; 46 in =
a=20
extension draft written by a member of RedBack.. I cant figure out what =
43 is=20
but it is causing the HiPer ARC to attempt to renegotiate SPI.. When =
this=20
happens the Redback complains about invalid lenght of AVP's.. After =
looking at=20
the packet sent from the HARC I can see no problem with the lengths in =
any of=20
the data fields..&nbsp; Can anyone shed some light on what AVP #43 is =
and where=20
it is documented? Also if you have had some success with redback and =
3com HiPer=20
ARC please forward that along as well..</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>-M</FONT></DIV>
<DIV>&nbsp;</DIV></BODY></HTML>

------=_NextPart_000_002F_01C00C7F.3A768680--



From owner-l2tp@diameter.org  Wed Aug 23 15:50:04 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22205
	for <l2tpext-archive@odin.ietf.org>; Wed, 23 Aug 2000 15:50:03 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e7NGxIh03281
	for l2tp-list; Wed, 23 Aug 2000 09:59:18 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from fcs-nt1.futsoft.com (fcs-nt1.futsoft.com [38.242.189.2])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e7NGxEW03275
	for <l2tp@diameter.org>; Wed, 23 Aug 2000 09:59:14 -0700
Received: from sanjose.futsoft.com (unverified) by fcs-nt1.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with SMTP id <B0000127840@fcs-nt1.futsoft.com> for <l2tp@diameter.org>;
 Wed, 23 Aug 2000 09:48:32 -0700
Received: from rajeshs ([38.242.189.59])
	by sanjose.futsoft.com (8.9.3/8.8.7) with SMTP id IAA05887
	for <l2tp@diameter.org>; Wed, 23 Aug 2000 08:57:15 -0700
Received: by localhost with Microsoft MAPI; Wed, 23 Aug 2000 10:21:32 -0700
Message-Id: <01C00CEB.E874F200.rajeshs@futsoft.com>
From: Rajesh Kumar <rajeshs@futsoft.com>
Reply-To: "rajeshs@futsoft.com" <rajeshs@futsoft.com>
To: "l2tp@diameter.org" <l2tp@diameter.org>
Subject: Is an outgoing call useful at a DSL LAC?
Date: Wed, 23 Aug 2000 10:21:31 -0700
Organization: Future Communications Software
X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

(1) How useful is a LAC with completely DSL access lines for subscribers (no dialup access at the LAC)? What would typical applications be?

(2) For a LAC positioned at DSL access, is support for outgoing calls useful? What would typical applications be?


Thanks
Rajesh


From owner-l2tp@diameter.org  Thu Aug 24 00:01:08 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA28696
	for <l2tpext-archive@odin.ietf.org>; Thu, 24 Aug 2000 00:01:05 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e7O1YvA03604
	for l2tp-list; Wed, 23 Aug 2000 18:34:57 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from center.mshindo.net (center.mshindo.net [210.231.221.221])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e7O1YrW03598
	for <l2tp@diameter.org>; Wed, 23 Aug 2000 18:34:53 -0700
Received: from cosinecom.com (G24210.dion.ne.jp [210.251.24.210])
	by center.mshindo.net (8.9.3/3.7W/00041811) with SMTP id KAA16634;
	Thu, 24 Aug 2000 10:32:47 +0900 (JST)
Date: Thu, 24 Aug 2000 10:10:53 +0900 (JST)
Message-Id: <20000824.101053.104025596.mshindo@mshindo.net>
To: mike@wronski.net
Cc: l2tp@diameter.org
Subject: Re: Strange AVP's from RedBack DSLAM
From: Motonori Shindo <mshindo@mshindo.net>
In-Reply-To: <003201c00ca9$23cb3460$030a0a0a@dyndns.org>
References: <003201c00ca9$23cb3460$030a0a0a@dyndns.org>
X-Mailer: Mew version 1.95b30 on XEmacs 21.1 (Canyonlands)
X-PGP-fingerprint: 06 B0 B1 A4 06 C1 6A 14  63 C0 D7 18 01 CD D9 83
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Mike,

From: "Mike Wronski" <mike@wronski.net>
Subject: Strange AVP's from RedBack DSLAM
Date: Tue, 22 Aug 2000 21:23:34 -0500

> I am attempting to get a RedBack DSLAM (SMS1000) acting as LAC to
> terminate sessions on a 3Com HiPer ARC (LNS). The Session open
> coming from the DSLAM has AVP's 43,44,& 46.. I found 44 & 46 in a
> extension draft written by a member of RedBack.. I cant figure out
> what 43 is but it is causing the HiPer ARC to attempt to renegotiate
> SPI.. When this happens the Redback complains about invalid lenght
> of AVP's.. After looking at the packet sent from the HARC I can see
> no problem with the lengths in any of the data fields..  Can anyone
> shed some light on what AVP #43 is and where it is documented? Also
> if you have had some success with redback and 3com HiPer ARC please
> forward that along as well..

I don't know what Redback's AVP 43 is. But it is interesting to see
that 3Com's VendorID is coincidentally 43! Are you really seeing
Redback's (VendorID = 2352) AVP 43? If you can send me a raw tcpdump
trace data, I might be able to help you figure out what's happening.

BTW, are you using IPsec with L2TP? If so, why don't you turn off
IPsec and see if exactly the same thing happen or not.

=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=
 +----+----+     
 |.. .|    |     Motonori Shindo
 |_~__|    |     
 | .. |~~_~|     Sr. Systems Engineer
 | .  |    |     CoSine Communications Inc.
 +----+----+     
 C o S i n e     e-mail:  mshindo@cosinecom.com 
Communications
=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=



From owner-l2tp@diameter.org  Fri Aug 25 16:11:52 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28523
	for <l2tpext-archive@odin.ietf.org>; Fri, 25 Aug 2000 16:11:51 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e7PH7a405159
	for l2tp-list; Fri, 25 Aug 2000 10:07:36 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from mailsrv.acc.com (mailsrv.acc.com [129.192.64.128])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e7PH7FW05153
	for <l2tp@diameter.org>; Fri, 25 Aug 2000 10:07:15 -0700
Received: from ericsson.com (calcium.dev.acc.am.ericsson.se [129.192.57.200])
	by mailsrv.acc.com (8.9.3/8.9.1) with ESMTP id KAA04991
	for <l2tp@diameter.org>; Fri, 25 Aug 2000 10:14:02 -0700 (PDT)
Message-ID: <39A6A9AA.1EF54EDA@ericsson.com>
Date: Fri, 25 Aug 2000 10:15:22 -0700
From: Evan Caves <evan.caves@ericsson.com>
X-Mailer: Mozilla 4.61 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: l2tp@diameter.org
Subject: L2TP Diffserv Draft
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I have a number of question regarding this draft which I hope one
of the authors can comment on.

1. Is the DSCP AVP a six or eight bit value?

2. What DSCP value is used for tunnel control messages? If the
   session DSCP has a 'higher priority' than the tunnels then
   payload packets may arrive before session setup completion.

3. Why is this AVP restricted to just sessions? One could conceive
   bringing up a tunnel for each PHB and forwarding all tunnel
   traffic (control and payload) with one of the PHB class DSCPs.

4. This draft makes a big assumption that the tunnel traverses a
   single DS domain. If the tunnel traverses multiple DS domains
   the DSCP to PHB mappings could be different (this may mean
   that each tunnel endpoint uses different DSCP marks that get
   translated at some DS boundary). How is this resolved?

5. Related to 4 it would seem that it may be more appropriate that
   the tunnel initiator ask for a PHB rather than a DSCP and then
   let each endpoint decide how that PHB maps to a DSCP.

evan
-


From owner-l2tp@diameter.org  Sat Aug 26 00:26:04 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA06475
	for <l2tpext-archive@odin.ietf.org>; Sat, 26 Aug 2000 00:26:03 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e7Q2Mft05425
	for l2tp-list; Fri, 25 Aug 2000 19:22:41 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from postal.redback.com (postal.redback.com [155.53.12.9])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e7Q2MbW05419
	for <l2tp@diameter.org>; Fri, 25 Aug 2000 19:22:37 -0700
Received: from phillips.redback.com (dhcp-33-102.redback.com [155.53.33.102])
	by postal.redback.com (Postfix) with ESMTP
	id D055417BC06; Fri, 25 Aug 2000 19:27:50 -0700 (PDT)
Message-Id: <4.3.2.7.2.20000825191904.00db1de0@pop.redback.com>
X-Sender: dphillip@pop.redback.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 25 Aug 2000 19:28:19 -0700
To: "Mike Wronski" <mike@wronski.net>, <l2tp@diameter.org>
From: David Phillips <dphillips@redback.com>
Subject: Re: Strange AVP's from RedBack DSLAM
In-Reply-To: <003201c00ca9$23cb3460$030a0a0a@dyndns.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-l2tp@diameter.org
Precedence: bulk

At 07:23 PM 8/22/00, Mike Wronski wrote:
>I am attempting to get a RedBack DSLAM (SMS1000) acting as LAC to 
>terminate sessions on a 3Com HiPer ARC (LNS). The Session open coming from 
>the DSLAM has AVP's 43,44,& 46.. I found 44 & 46 in a extension draft 
>written by a member of RedBack.. I cant figure out what 43 is but it is 
>causing the HiPer ARC to attempt to renegotiate SPI.. When this happens 
>the Redback complains about invalid lenght of AVP's.. After looking at the 
>packet sent from the HARC I can see no problem with the lengths in any of 
>the data fields..  Can anyone shed some light on what AVP #43 is and where 
>it is documented? Also if you have had some success with redback and 3com 
>HiPer ARC please forward that along as well..

L2TP attribute 43 is a Redback VSA and it's documented in the, um, 
documentation ;-)  Check the configuration guide and look at the L2TP 
attributes section at the end.

It is the NAS Port Type AVP.  It tells you what the port type on the LAC is.

BTW, The Redback SMS is not a DSLAM.  It's just an SMS.

/// Dave ///



From owner-l2tp@diameter.org  Mon Aug 28 12:37:44 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15217
	for <l2tpext-archive@odin.ietf.org>; Mon, 28 Aug 2000 12:37:43 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e7SD4Cj12770
	for l2tp-list; Mon, 28 Aug 2000 06:04:12 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e7SD3eW12764
	for <l2tp@l2tp.net>; Mon, 28 Aug 2000 06:03:40 -0700
Received: from brahma.roc.com ([203.197.20.172]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id GAA04144 for <l2tp@ipsec.org>; Mon, 28 Aug 2000 06:09:01 -0700 (PDT)
Received: from sridhar.roc.com ([172.16.5.52])
	by brahma.roc.com (8.8.5/8.8.5) with SMTP id SAA02349
	for <l2tp@ipsec.org>; Mon, 28 Aug 2000 18:43:46 +0530 (IST)
Message-Id: <200008281313.SAA02349@brahma.roc.com>
X-Sender: sridhar@172.16.1.10
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0
Date: Mon, 28 Aug 2000 18:48:12 +0530
To: l2tp@ipsec.org
From: Sridhar Malarothu <sridhar@trinc.com>
Subject: Tunnel  
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-l2tp@diameter.org
Precedence: bulk

Hi, 

   An L2TP implementation can act as both LNS and LAC. Also a Tunnel is not
distinguishable between the LNS and LAC. So can an Implementation (which
acts as both LNS and LAC) use the Tunnel for placing Outgoing Call Requests
and Incoming Call Requests (assuming that the Peer is also capable of acting
both as LAC and LNS) ?
   

Best Regards
Sridhar



From owner-l2tp@diameter.org  Wed Aug 30 06:39:42 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA23316
	for <l2tpext-archive@odin.ietf.org>; Wed, 30 Aug 2000 06:39:41 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e7U7mXj14337
	for l2tp-list; Wed, 30 Aug 2000 00:48:33 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e7U7mUW14331
	for <l2tp@l2tp.net>; Wed, 30 Aug 2000 00:48:30 -0700
Received: from brahma.roc.com ([202.54.67.219]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id AAA08185 for <l2tp@ipsec.org>; Wed, 30 Aug 2000 00:53:56 -0700 (PDT)
Received: from sridhar.roc.com ([172.16.5.52])
	by brahma.roc.com (8.8.5/8.8.5) with SMTP id NAA03858
	for <l2tp@ipsec.org>; Wed, 30 Aug 2000 13:28:33 +0530 (IST)
Message-Id: <200008300758.NAA03858@brahma.roc.com>
X-Sender: sridhar@172.16.1.10 (Unverified)
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0
Date: Wed, 30 Aug 2000 13:33:40 +0530
To: l2tp@ipsec.org
From: Sridhar Malarothu <sridhar@trinc.com>
Subject: Reliable delivery of control Messages
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-l2tp@diameter.org
Precedence: bulk

Hi All,

   Should Acknowledgement for a control message (if it has been 
received in order) be always piggy-backed on to the repsonse 
message (if one exists exists) ? If not then its better to start 
timers when replies for some control messages are awaited.

   I want some clarification on synchronous framing for PPP. PPP
will not add link framing (flags 0x7e) and crc bytes. but what 
about the async mapping for synchronous lines? 
 
Best Regards
Sridhar



From owner-l2tp@diameter.org  Wed Aug 30 11:05:10 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01316
	for <l2tpext-archive@odin.ietf.org>; Wed, 30 Aug 2000 11:05:10 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e7UBWnh14632
	for l2tp-list; Wed, 30 Aug 2000 04:32:49 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e7UBWiW14626
	for <l2tp@l2tp.net>; Wed, 30 Aug 2000 04:32:44 -0700
Received: from center.mshindo.net (center.mshindo.net [210.231.221.221]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id EAA09520 for <l2tp@ipsec.org>; Wed, 30 Aug 2000 04:38:16 -0700 (PDT)
Received: from cosinecom.com (G24219.dion.ne.jp [210.251.24.219])
	by center.mshindo.net (8.9.3/3.7W/00041811) with SMTP id UAA28577;
	Wed, 30 Aug 2000 20:33:26 +0900 (JST)
Date: Wed, 30 Aug 2000 20:37:40 +0900 (JST)
Message-Id: <20000830.203740.104025736.mshindo@mshindo.net>
To: sridhar@trinc.com
Cc: l2tp@ipsec.org
Subject: Re: Reliable delivery of control Messages
From: Motonori Shindo <mshindo@mshindo.net>
In-Reply-To: <200008300758.NAA03858@brahma.roc.com>
References: <200008300758.NAA03858@brahma.roc.com>
X-Mailer: Mew version 1.95b30 on XEmacs 21.1 (Canyonlands)
X-PGP-fingerprint: 06 B0 B1 A4 06 C1 6A 14  63 C0 D7 18 01 CD D9 83
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Sridhar,

From: Sridhar Malarothu <sridhar@trinc.com>
Subject: Reliable delivery of control Messages
Date: Wed, 30 Aug 2000 13:33:40 +0530

> Hi All,
> 
>    Should Acknowledgement for a control message (if it has been 
> received in order) be always piggy-backed on to the repsonse 
> message (if one exists exists) ? 

It should but it's not mandatory.

> If not then its better to start 
> timers when replies for some control messages are awaited.

Whenever a control message is sent, a timer associated with it should
be started. The only exception to this rule is a ZLB. Since ZLB
doesn't consume a sequence number space, timer invocation is not
necessary. As a consequence, ZLB will not be retransmitted.

>    I want some clarification on synchronous framing for PPP. PPP
> will not add link framing (flags 0x7e) and crc bytes. 

True.

> but what 
> about the async mapping for synchronous lines? 

Sorry, I don't understand your question. Someone else will shed more
light on this.

Regards,

=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=
 +----+----+     
 |.. .|    |     Motonori Shindo
 |_~__|    |     
 | .. |~~_~|     Sr. Systems Engineer
 | .  |    |     CoSine Communications Inc.
 +----+----+     
 C o S i n e     e-mail:  mshindo@cosinecom.com 
Communications
=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=



From owner-l2tp@diameter.org  Wed Aug 30 13:40:14 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05542
	for <l2tpext-archive@odin.ietf.org>; Wed, 30 Aug 2000 13:40:12 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e7UEYge14753
	for l2tp-list; Wed, 30 Aug 2000 07:34:42 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e7UEYcW14747
	for <l2tp@l2tp.net>; Wed, 30 Aug 2000 07:34:38 -0700
Received: from brahma.roc.com ([202.54.67.219]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id HAA09758 for <l2tp@ipsec.org>; Wed, 30 Aug 2000 07:40:05 -0700 (PDT)
Received: from sridhar.roc.com ([172.16.5.52])
	by brahma.roc.com (8.8.5/8.8.5) with SMTP id UAA16564
	for <l2tp@ipsec.org>; Wed, 30 Aug 2000 20:14:48 +0530 (IST)
Message-Id: <200008301444.UAA16564@brahma.roc.com>
X-Sender: sridhar@172.16.1.10
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0
Date: Wed, 30 Aug 2000 20:19:51 +0530
To: l2tp@ipsec.org
From: Sridhar Malarothu <sridhar@trinc.com>
Subject: Re: Reliable delivery of control Messages
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-l2tp@diameter.org
Precedence: bulk

Shindo,

   Thanks for the Information.

   If suppose an implementation cannot immediately decide whether
the Tunnel/Call Request is acceptable or not (May be it has to 
get the request verified by someone else). Then It will be better, if
the packet could be acknowledged immediately (by ZLB ack) and send 
response later.

   Regarding the next question, I want to know whether any charecter stuffing
(Async Control Charecter MAP) will be done by PPP for synchronous lines.

Best Regards
Sridhar

At 08:37 PM 8/30/00 +0900, you wrote:
>Sridhar,
>
>From: Sridhar Malarothu <sridhar@trinc.com>
>Subject: Reliable delivery of control Messages
>Date: Wed, 30 Aug 2000 13:33:40 +0530
>
>> Hi All,
>> 
>>    Should Acknowledgement for a control message (if it has been 
>> received in order) be always piggy-backed on to the repsonse 
>> message (if one exists exists) ? 
>
>It should but it's not mandatory.
>
>> If not then its better to start 
>> timers when replies for some control messages are awaited.
>
>Whenever a control message is sent, a timer associated with it should
>be started. The only exception to this rule is a ZLB. Since ZLB
>doesn't consume a sequence number space, timer invocation is not
>necessary. As a consequence, ZLB will not be retransmitted.
>
>>    I want some clarification on synchronous framing for PPP. PPP
>> will not add link framing (flags 0x7e) and crc bytes. 
>
>True.
>
>> but what 
>> about the async mapping for synchronous lines? 
>
>Sorry, I don't understand your question. Someone else will shed more
>light on this.
>
>Regards,
>
>=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=
> +----+----+     
> |.. .|    |     Motonori Shindo
> |_~__|    |     
> | .. |~~_~|     Sr. Systems Engineer
> | .  |    |     CoSine Communications Inc.
> +----+----+     
> C o S i n e     e-mail:  mshindo@cosinecom.com 
>Communications
>=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=
> 



From owner-l2tp@diameter.org  Wed Aug 30 20:18:06 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11536
	for <l2tpext-archive@odin.ietf.org>; Wed, 30 Aug 2000 20:18:05 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e7UK2QK15041
	for l2tp-list; Wed, 30 Aug 2000 13:02:26 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e7UK1mW15035
	for <l2tp@l2tp.net>; Wed, 30 Aug 2000 13:01:48 -0700
Received: from h006008986325.ne.mediaone.net (h006008986325.ne.mediaone.net [24.218.16.153]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id NAA10154 for <l2tp@ipsec.org>; Wed, 30 Aug 2000 13:07:11 -0700 (PDT)
Received: (from carlson@localhost)
	by h006008986325.ne.mediaone.net (8.9.3/8.9.3) id QAA17932;
	Wed, 30 Aug 2000 16:06:47 -0400
From: James Carlson <carlson@workingcode.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14765.26966.447791.606983@h006008986325.ne.mediaone.net>
Date: Wed, 30 Aug 2000 16:06:46 -0400 (EDT)
To: Sridhar Malarothu <sridhar@trinc.com>
Cc: l2tp@ipsec.org
Subject: Re: Reliable delivery of control Messages
In-Reply-To: Sridhar Malarothu's message of 30 August 2000 20:19:51
References: <200008301444.UAA16564@brahma.roc.com>
X-Mailer: VM 6.75 under Emacs 20.6.1
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Sridhar Malarothu writes:
>    If suppose an implementation cannot immediately decide whether
> the Tunnel/Call Request is acceptable or not (May be it has to 
> get the request verified by someone else). Then It will be better, if
> the packet could be acknowledged immediately (by ZLB ack) and send 
> response later.

Right.  This can be done by a timer.

>    Regarding the next question, I want to know whether any charecter stuffing
> (Async Control Charecter MAP) will be done by PPP for synchronous lines.

No.  This is documented in RFC 1662.  Synchronous lines use
bit-stuffing, not octet-stuffing.

-- 
James Carlson                                  <carlson@workingcode.com>
"PPP Design and Debugging" --- http://people.ne.mediaone.net/carlson/ppp


