From owner-l2tp@diameter.org  Wed Oct  4 16:49: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 SMTP id QAA01450
	for <l2tpext-archive@odin.ietf.org>; Wed, 4 Oct 2000 16:49:58 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e94HN0m01090
	for l2tp-list; Wed, 4 Oct 2000 10:23:00 -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 e94HMvl01084
	for <l2tp@diameter.org>; Wed, 4 Oct 2000 10:22:57 -0700
Received: from gwzpc (rtp-dial-2-12.cisco.com [10.83.96.12]) by franklin.cisco.com (8.8.6 (PHNE_17190)/CISCO.SERVER.1.2) with SMTP id KAA14921; Wed, 4 Oct 2000 10:26:23 -0700 (PDT)
Reply-To: <gwz@cisco.com>
From: "Glen Zorn" <gwz@cisco.com>
To: "Danny McPherson" <Danny@ambernetworks.com>, <suhail@redback.com>
Cc: <gwz@cisco.com>, "l2tpext" <l2tp@diameter.org>
Subject: IANA considerations in draft-ietf-l2tpext-svctype-00.txt
Date: Wed, 4 Oct 2000 10:26:11 -0700
Message-ID: <NDBBIHMPILAAGDHPCIOPAELLCMAA.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)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

"Specification Required" might be a more appropriate allocation policy for
Service Type numbers than FCFS, since an RFC is required in section 10
anyway.  Therefore, I suggest that Section 10 be deleted and Section 8 be
changed to read:

8. IANA Considerations

   The Service Type AVP namespace will be registered and maintained by
   IANA as follows:

    o Values 0 and 65535 are reserved.

    o Value 1 is reserved for PPP payloads.

    o Values between 2 and 65534 are to be assigned by IANA, using
      the "Specification Required" policy [RFC 2434].


8.1. Specification Requirements for New Service Types
   To define a new Service Type for a payload other than PPP, a new RFC
   MUST be drafted which MUST:

    o Identify any new L2TP AVPs or control messases necessary for the
      establishment, maintenance, and teardown of the non-PPP session.

    o Identify which AVPs must be present (new or existing) in each
      existing or new control message with a given service type.

    o Identify any existing AVPs which have a new or revised meaning for
      a given Service Type beyond that defined in RFC2661.



From owner-l2tp@diameter.org  Wed Oct  4 17:24: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 SMTP id RAA02097
	for <l2tpext-archive@odin.ietf.org>; Wed, 4 Oct 2000 17:24:42 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e94I3J801184
	for l2tp-list; Wed, 4 Oct 2000 11:03:19 -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 e94I3El01178
	for <l2tp@diameter.org>; Wed, 4 Oct 2000 11:03:15 -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 MAA08372;
	Wed, 4 Oct 2000 12:08:55 -0600
Message-Id: <200010041808.MAA08372@tcb.net>
To: gwz@cisco.com
cc: suhail@redback.com, "l2tpext" <l2tp@diameter.org>
From: Danny McPherson <danny@tcb.net>
Reply-To: danny@tcb.net
Subject: Re: IANA considerations in draft-ietf-l2tpext-svctype-00.txt 
Date: Wed, 04 Oct 2000 12:08:55 -0600
Sender: owner-l2tp@diameter.org
Precedence: bulk


OK by me...  Thanks Glen,

-danny

> "Specification Required" might be a more appropriate allocation policy for
> Service Type numbers than FCFS, since an RFC is required in section 10
> anyway.  Therefore, I suggest that Section 10 be deleted and Section 8 be
> changed to read:


From owner-l2tp@diameter.org  Wed Oct  4 22:01:21 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 SMTP id WAA07037
	for <l2tpext-archive@odin.ietf.org>; Wed, 4 Oct 2000 22:01:20 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e94NU7R01468
	for l2tp-list; Wed, 4 Oct 2000 16:30:07 -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 e94NU3l01462
	for <l2tp@l2tp.net>; Wed, 4 Oct 2000 16:30:03 -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 QAA24961 for <l2tp@ipsec.org>; Wed, 4 Oct 2000 16:36:13 -0700 (PDT)
Received: from sanjose.futsoft.com (unverified) by fcs-nt1.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with SMTP id <B0000206793@fcs-nt1.futsoft.com> for <l2tp@ipsec.org>;
 Wed, 04 Oct 2000 16:16:52 -0700
Received: from localhost (rajeshs@localhost)
	by sanjose.futsoft.com (8.9.3/8.8.7) with ESMTP id PAA26228
	for <l2tp@ipsec.org>; Wed, 4 Oct 2000 15:22:45 -0700
Date: Wed, 4 Oct 2000 15:22:45 -0700 (PDT)
From: "S.Rajesh Kumar" <rajeshs@futsoft.com>
To: l2tp@ipsec.org
Subject: Does an outgoing call make sense at a DSL LAC?
Message-Id: <Pine.LNX.4.10.10010041518300.26202-100000@sanjose.futsoft.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-l2tp@diameter.org
Precedence: bulk

(1) Assume a LAC has purely DSL interfaces (no dialup). Is there any
way that it can support outgoing calls? Are there any applications
that use this facility currently?

(2) If a system has purely DSL interfaces (no dialup), does LAC
functionality make sense? Do any of the deployed systems - Cisco, Redback,
etc. implement this?

Thanks
Rajesh



From owner-l2tp@diameter.org  Wed Oct  4 22:47:12 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 SMTP id WAA08317
	for <l2tpext-archive@odin.ietf.org>; Wed, 4 Oct 2000 22:47:12 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e94Nl4d01507
	for l2tp-list; Wed, 4 Oct 2000 16:47:04 -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 e94Nkml01497
	for <l2tp@l2tp.net>; Wed, 4 Oct 2000 16:46:48 -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 QAA24979 for <l2tp@ipsec.org>; Wed, 4 Oct 2000 16:52:58 -0700 (PDT)
Received: from sanjose.futsoft.com (unverified) by fcs-nt1.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with SMTP id <B0000206809@fcs-nt1.futsoft.com> for <l2tp@ipsec.org>;
 Wed, 04 Oct 2000 16:33:40 -0700
Received: from localhost (rajeshs@localhost)
	by sanjose.futsoft.com (8.9.3/8.8.7) with ESMTP id PAA26345
	for <l2tp@ipsec.org>; Wed, 4 Oct 2000 15:39:33 -0700
Date: Wed, 4 Oct 2000 15:39:33 -0700 (PDT)
From: "S.Rajesh Kumar" <rajeshs@futsoft.com>
To: l2tp@ipsec.org
Subject: multilink ppp with l2tp?
Message-Id: <Pine.LNX.4.10.10010041534250.26301-100000@sanjose.futsoft.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-l2tp@diameter.org
Precedence: bulk

(1) Does anyone use l2tp to tunnel multilink ppp?
Any well-known issues?

(2) How does ProxyLCP work in this case? Is the LAC expected to be
the same for all links in a bundle? What if multiple links in a bundle
go through different LACs?

(3) RFC1990 on Multilink PPP suggests a mechanism of using increasing
sequence numbers on links within a multilink bundle alongwith a scheme
where a receiver can quickly detect a lost fragment. Would this break
if the ppp session (multilink) were tunneled over an IP network, with its
possibility of reordering?

Thanks
Rajesh



From owner-l2tp@diameter.org  Thu Oct  5 08:22:12 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 SMTP id IAA27323
	for <l2tpext-archive@odin.ietf.org>; Thu, 5 Oct 2000 08:22:12 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e959nXA03238
	for l2tp-list; Thu, 5 Oct 2000 02:49: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 e959nUl03232
	for <l2tp@l2tp.net>; Thu, 5 Oct 2000 02:49:30 -0700
Received: from arianne.in.ishoni.com ([164.164.83.132]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id CAA25477 for <l2tp@ipsec.org>; Thu, 5 Oct 2000 02:55:37 -0700 (PDT)
Received: from rohit ([192.168.1.133])
	by arianne.in.ishoni.com (8.9.3/8.9.3) with SMTP id PAA12179
	for <l2tp@ipsec.org>; Thu, 5 Oct 2000 15:29:30 +0530
Reply-To: <rkhosla@ishoni.com>
From: "Rohit Khosla" <rkhosla@ishoni.com>
To: <l2tp@ipsec.org>
Subject: IPSec test suites.
Date: Thu, 5 Oct 2000 15:36:24 +0530
Message-ID: <C182A5918209D41190DE00C04F0CCD254BAE56@LEONOID>
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.2911.0)
In-reply-to: <C182A5918209D41190DE00C04F0CCD2555FFA2@LEONOID>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi,

	I am looking for some freely available test tool or test suites to test the
IPSec implementation.

Thanks,
Rohit.


-----Original Message-----
From: owner-l2tp@diameter.org [mailto:owner-l2tp@diameter.org]On Behalf
Of S.Rajesh Kumar
Sent: Thursday, October 05, 2000 4:10 AM
To: l2tp@ipsec.org
Subject: multilink ppp with l2tp?


(1) Does anyone use l2tp to tunnel multilink ppp?
Any well-known issues?

(2) How does ProxyLCP work in this case? Is the LAC expected to be
the same for all links in a bundle? What if multiple links in a bundle
go through different LACs?

(3) RFC1990 on Multilink PPP suggests a mechanism of using increasing
sequence numbers on links within a multilink bundle alongwith a scheme
where a receiver can quickly detect a lost fragment. Would this break
if the ppp session (multilink) were tunneled over an IP network, with its
possibility of reordering?

Thanks
Rajesh



From owner-l2tp@diameter.org  Thu Oct  5 10:26:29 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 SMTP id KAA29753
	for <l2tpext-archive@odin.ietf.org>; Thu, 5 Oct 2000 10:26:28 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e95CHMd03891
	for l2tp-list; Thu, 5 Oct 2000 05:17: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 e95CHIl03882
	for <l2tp@l2tp.net>; Thu, 5 Oct 2000 05:17:18 -0700
Received: from mail3.belgacom.be (mail3.belgacom.be [195.13.11.162]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id FAA26818 for <l2tp@ipsec.org>; Thu, 5 Oct 2000 05:23:29 -0700 (PDT)
From: paolo.crivellari@belgacom.be
Received: from exhub01.bc (mh2ex [45.34.4.231])
	by mail3.belgacom.be  with SMTP id OAA13635;
	Thu, 5 Oct 2000 14:17:51 +0200
Received: from 127.0.0.1 by exhub01.bc (InterScan E-Mail VirusWall NT); Thu, 05 Oct 2000 14:23:12 +0200 (W. Europe Daylight Time)
Received: by exhub01.bc with Internet Mail Service (5.5.2650.21)
	id <SG12RV79>; Thu, 5 Oct 2000 14:23:12 +0200
Message-ID: <95C94B2F0094D21180710008C75DD6A4046A2A49@apl541.bc>
To: rajeshs@futsoft.com
Cc: l2tp@ipsec.org
Subject: draft-ietf-l2tpext-atmext-03 (http://www.ietf.org/internet-drafts
	/draft-ietf-l2
Date: Thu, 5 Oct 2000 14:23:13 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_000_01C02EC7.073E0AD0"
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_000_01C02EC7.073E0AD0
Content-Type: text/plain;
	charset="ISO-8859-1"

  See
 
 http://www.ietf.org/internet-drafts/draft-ietf-l2tpext-atmext-03.txt

**** DISCLAIMER **** 
"This e-mail and any attachments thereto may contain information 
which is confidential and/or protected by intellectual property 
rights and are intended for the sole use of the recipient(s) named above. 
Any use of the information contained herein (including, but not limited to, 
total or partial reproduction, communication or distribution in any form) 
by persons other than the designated recipient(s) is prohibited. 
If you have received this e-mail in error, please notify the sender either 
by telephone or by e-mail and delete the material from any computer. 
Thank you for your cooperation."

 <<draft-ietf-l2tpext-atmext-03.url>>  

------_=_NextPart_000_01C02EC7.073E0AD0
Content-Type: application/octet-stream;
	name="draft-ietf-l2tpext-atmext-03.url"
Content-Disposition: attachment;
	filename="draft-ietf-l2tpext-atmext-03.url"

[InternetShortcut]
URL=http://www.ietf.org/internet-drafts/draft-ietf-l2tpext-atmext-03.txt
Modified=E0B756A5C62EC00147

------_=_NextPart_000_01C02EC7.073E0AD0--


From owner-l2tp@diameter.org  Thu Oct  5 11:39: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 SMTP id LAA01408
	for <l2tpext-archive@odin.ietf.org>; Thu, 5 Oct 2000 11:39:00 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e95Cna504039
	for l2tp-list; Thu, 5 Oct 2000 05:49: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 e95CmHl04033
	for <l2tp@l2tp.net>; Thu, 5 Oct 2000 05:48:17 -0700
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id FAA26851 for <l2tp@ipsec.org>; Thu, 5 Oct 2000 05:54:29 -0700 (PDT)
Received: from eastmail1.East.Sun.COM ([129.148.1.240])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id GAA28455;
	Thu, 5 Oct 2000 06:54:26 -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 IAA07367;
	Thu, 5 Oct 2000 08:54:26 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.9.3+Sun/8.9.3) id IAA05080;
	Thu, 5 Oct 2000 08:54:29 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14812.31236.973520.711575@gargle.gargle.HOWL>
Date: Thu, 5 Oct 2000 08:54:28 -0400 (EDT)
From: James Carlson <james.d.carlson@east.sun.com>
To: <rkhosla@ishoni.com>
Cc: <ietf-ppp@merit.edu>, <l2tp@ipsec.org>
Subject: Re: IPSec test suite
In-Reply-To: Rohit Khosla's message of 5 October 2000 15:40:29
References: <C182A5918209D41190DE00C04F0CCD2555FFA2@LEONOID>
	<C182A5918209D41190DE00C04F0CCD254BAE56@LEONOID>
	<C182A5918209D41190DE00C04F0CCD254CC2A4@LEONOID>
	<C182A5918209D41190DE00C04F0CCD254BAE59@LEONOID>
X-Mailer: VM 6.75 under Emacs 20.7.1
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Rohit Khosla writes:
> 	I am looking for some freely available test tool or test suites to test the
> IPSec implementation.

The message you sent wasn't appropriate for either of the two lists
to which you sent it.  IPSec isn't L2TP nor is it PPP.

For a free one, you might try:

	http://www.antd.nist.gov/antd/html/wit.html

Empirix (nee Teradyne, nee Hammer, nee Midnight Networks) claims to
have what you want, though it's not free:

	http://www.hammer.com/p_datacom.htm

-- 
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
Second Edition now available - http://people.ne.mediaone.net/carlson/ppp


From owner-l2tp@diameter.org  Fri Oct  6 04:26: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 SMTP id EAA26690
	for <l2tpext-archive@odin.ietf.org>; Fri, 6 Oct 2000 04:26:16 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e965PkO06032
	for l2tp-list; Thu, 5 Oct 2000 22:25:46 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from postal.redback.com (hiddenuser@postal.redback.com [155.53.12.9])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e965Pgl06026
	for <l2tp@diameter.org>; Thu, 5 Oct 2000 22:25:42 -0700
Received: from redback.com (express.redback.com [155.53.32.60])
	by postal.redback.com (Postfix) with ESMTP id DD43B17BC05
	for <l2tp@diameter.org>; Thu,  5 Oct 2000 22:30:42 -0700 (PDT)
Message-ID: <39DD6382.B8DB7027@redback.com>
Date: Thu, 05 Oct 2000 22:30:42 -0700
From: Siva Sthanukrishnan <siva@redback.com>
Organization: Redback Networks
X-Mailer: Mozilla 4.7 [en] (X11; U; NetBSD 1.4.2 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: l2tp@diameter.org
Subject: l2tp test tool
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

hi all,

  Is there a l2tp test tool that is available for FreeBSD/NetBSD/linux
that can be used to test l2tp implementation?  Thanks.

- Siva



From owner-l2tp@diameter.org  Fri Oct  6 11:18:40 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 SMTP id LAA06164
	for <l2tpext-archive@odin.ietf.org>; Fri, 6 Oct 2000 11:18:39 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e96CZ2X06995
	for l2tp-list; Fri, 6 Oct 2000 05:35:02 -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 e96CXwl06988
	for <l2tp@l2tp.net>; Fri, 6 Oct 2000 05:33:58 -0700
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id FAA29231 for <l2tp@ipsec.org>; Fri, 6 Oct 2000 05:40:12 -0700 (PDT)
Received: from eastmail1.East.Sun.COM ([129.148.1.240])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id GAA10670;
	Fri, 6 Oct 2000 06:40:09 -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 IAA18883;
	Fri, 6 Oct 2000 08:40:08 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.9.3+Sun/8.9.3) id IAA07120;
	Fri, 6 Oct 2000 08:40:12 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14813.51243.491519.695635@gargle.gargle.HOWL>
Date: Fri, 6 Oct 2000 08:40:11 -0400 (EDT)
From: James Carlson <james.d.carlson@east.sun.com>
To: "S.Rajesh Kumar" <rajeshs@futsoft.com>
Cc: l2tp@ipsec.org
Subject: Re: multilink ppp with l2tp?
In-Reply-To: S.Rajesh Kumar's message of 4 October 2000 15:39:33
References: <Pine.LNX.4.10.10010041534250.26301-100000@sanjose.futsoft.com>
X-Mailer: VM 6.75 under Emacs 20.7.1
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

S.Rajesh Kumar writes:
> (1) Does anyone use l2tp to tunnel multilink ppp?
> Any well-known issues?

Yes; many.  Multilink is negotiated by way of LCP MRRU.  Many L2TP
implementations negotiate LCP in the LAC before ever contacting the
LNS.  This means that the caller who is trying to establish a second
link must be tolerant of getting a reject on MRRU at first (from the
LAC), followed by LCP renegotiation (by the LNS) with MRRU.  (I know
of no demand-dialing peers that are so tolerant, and I think making
them tolerant to accomodate an L2TP problem would be unwarranted.)

I think it's fair to say that MP interacts poorly with most L2TP
implementations.  L2TP is far from transparent.

(This is not true if you're not doing proxy LCP.  If L2TP is merely a
configured tunnel between the LAC and LNS, then this part of the
problem is simpler.)

> (2) How does ProxyLCP work in this case? Is the LAC expected to be
> the same for all links in a bundle? What if multiple links in a bundle
> go through different LACs?

They'll either have to be configured to give the same LCP Endpoint-
Discriminator, or the peer will have to be tolerant of being presented
with the "wrong" E-D and having LCP renegotiated with the "right" one
later.

> (3) RFC1990 on Multilink PPP suggests a mechanism of using increasing
> sequence numbers on links within a multilink bundle alongwith a scheme
> where a receiver can quickly detect a lost fragment.

It's quite a bit more than a suggestion.  It's a requirement.  MP will
fail miserably if you reorder fragments.

> Would this break
> if the ppp session (multilink) were tunneled over an IP network, with its
> possibility of reordering?

Unless you use the "Sequencing Required" option in L2TP, you may well
break the ordering rule in MP.

I'm probably in the minority on this, but I'd recommend doing the
bundling locally -- on the LAC if possible -- and then carrying the
reassembled packets back to the LNS via L2TP.  You have to do stateful
inspection and modification of the LCP messages at the LAC in order to
do this, so that the LNS can remain unaware of the MP options, but
it's not an impossible thing to do; ISDN TAs have done it for years.
(There are, of course, other problems; for instance, this mode of
operation breaks CHAP.)

The reason I recommend bundling locally is twofold.  First, as you've
noticed, L2TP interacts with MP in some undesirable ways in the
establishment of links.  Second, and more subtly, MP performs very
badly when there's differential delay between the links or noticable
fragment loss, as occurs with non-error (congestion) events.
Tunneling the links across an internet is one good way to destroy MP
performance.

You might want to get a copy of Rich Shea's book on L2TP.  It covers a
number of deployment issues such as this.

-- 
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
Second Edition now available - http://people.ne.mediaone.net/carlson/ppp


From owner-l2tp@diameter.org  Fri Oct  6 13:38:18 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 SMTP id NAA09223
	for <l2tpext-archive@odin.ietf.org>; Fri, 6 Oct 2000 13:38:18 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e96EOn507296
	for l2tp-list; Fri, 6 Oct 2000 07:24: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 e96EOkl07290
	for <l2tp@l2tp.net>; Fri, 6 Oct 2000 07:24:46 -0700
Received: from eins.siemens.at (eins.siemens.at [193.81.246.11]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id HAA29316 for <l2tp@ipsec.org>; Fri, 6 Oct 2000 07:30:56 -0700 (PDT)
Received: from scesie13.sie.siemens.at (forix-hme0 [10.1.140.2])
	by eins.siemens.at  with ESMTP id QAA02423;
	Fri, 6 Oct 2000 16:21:32 +0200 (MET DST)
Received: (from smap@localhost)
	by scesie13.sie.siemens.at (8.9.3/8.9.3) id QAA21465;
	Fri, 6 Oct 2000 16:30:22 +0200 (MET DST)
Received: from vies194a.sie.siemens.at(195.1.196.94) by scesie13 via smap (V2.0beta)
	id xma020947; Fri, 6 Oct 00 16:30:07 +0200
Received: by vies194a.sie.siemens.at with Internet Mail Service (5.5.2650.21)
	id <4FYL2VW2>; Fri, 6 Oct 2000 16:30:06 +0200
Message-ID: <D9F2B9CD7BD5D21196BC0800060D9ED601EFBFF1@vies186a.sie.siemens.at>
From: Klausberger Walter <walter.klausberger@siemens.at>
To: "'James Carlson'" <james.d.carlson@east.sun.com>
Cc: l2tp@ipsec.org
Subject: AW: multilink ppp with l2tp?
Date: Fri, 6 Oct 2000 16:30:04 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
X-MIME-Autoconverted: from quoted-printable to 8bit by charizard.diameter.org id e96EOkl07291
Sender: owner-l2tp@diameter.org
Precedence: bulk
X-MIME-Autoconverted: from 8bit to quoted-printable by charizard.diameter.org id e96EOn507296
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id NAA09223

I like the idea of terminating the MP in the LAC, although I am not sure if
anyone ever tried this.

Let me ask another question. What about MP over multi-chassis?
- Is it really common to forward the PPP connection from one chassis to the
other via L2TP, or is there another way (I would have to implement LNS on a
LAC!)?
- Is there a common way to distribute information about incomming PPP
sessions between the chassis?
- Would you recommend to terminate the MP in this chassis anyway to avoid
multiple links over the L2TP to the remote LNS?

with best regards
Walter Klausberger

-------------------------------
Siemens AG Austria
Boschstrasse 10
1190 Vienna
Austria

Tel: +49(5)1707-42683
<walter.klausberger@siemens.at>
-------------------------------

-----Ursprüngliche Nachricht-----
Von: James Carlson [mailto:james.d.carlson@east.sun.com]
Gesendet am: Freitag, 06. Oktober 2000 14:40
An: S.Rajesh Kumar
Cc: l2tp@ipsec.org
Betreff: Re: multilink ppp with l2tp?

S.Rajesh Kumar writes:
> (1) Does anyone use l2tp to tunnel multilink ppp?
> Any well-known issues?

Yes; many.  Multilink is negotiated by way of LCP MRRU.  Many L2TP
implementations negotiate LCP in the LAC before ever contacting the
LNS.  This means that the caller who is trying to establish a second
link must be tolerant of getting a reject on MRRU at first (from the
LAC), followed by LCP renegotiation (by the LNS) with MRRU.  (I know
of no demand-dialing peers that are so tolerant, and I think making
them tolerant to accomodate an L2TP problem would be unwarranted.)

I think it's fair to say that MP interacts poorly with most L2TP
implementations.  L2TP is far from transparent.

(This is not true if you're not doing proxy LCP.  If L2TP is merely a
configured tunnel between the LAC and LNS, then this part of the
problem is simpler.)

> (2) How does ProxyLCP work in this case? Is the LAC expected to be
> the same for all links in a bundle? What if multiple links in a bundle
> go through different LACs?

They'll either have to be configured to give the same LCP Endpoint-
Discriminator, or the peer will have to be tolerant of being presented
with the "wrong" E-D and having LCP renegotiated with the "right" one
later.

> (3) RFC1990 on Multilink PPP suggests a mechanism of using increasing
> sequence numbers on links within a multilink bundle alongwith a scheme
> where a receiver can quickly detect a lost fragment.

It's quite a bit more than a suggestion.  It's a requirement.  MP will
fail miserably if you reorder fragments.

> Would this break
> if the ppp session (multilink) were tunneled over an IP network, with its
> possibility of reordering?

Unless you use the "Sequencing Required" option in L2TP, you may well
break the ordering rule in MP.

I'm probably in the minority on this, but I'd recommend doing the
bundling locally -- on the LAC if possible -- and then carrying the
reassembled packets back to the LNS via L2TP.  You have to do stateful
inspection and modification of the LCP messages at the LAC in order to
do this, so that the LNS can remain unaware of the MP options, but
it's not an impossible thing to do; ISDN TAs have done it for years.
(There are, of course, other problems; for instance, this mode of
operation breaks CHAP.)

The reason I recommend bundling locally is twofold.  First, as you've
noticed, L2TP interacts with MP in some undesirable ways in the
establishment of links.  Second, and more subtly, MP performs very
badly when there's differential delay between the links or noticable
fragment loss, as occurs with non-error (congestion) events.
Tunneling the links across an internet is one good way to destroy MP
performance.

You might want to get a copy of Rich Shea's book on L2TP.  It covers a
number of deployment issues such as this.

-- 
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
Second Edition now available - http://people.ne.mediaone.net/carlson/ppp


From owner-l2tp@diameter.org  Fri Oct  6 14:02:48 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 SMTP id OAA09599
	for <l2tpext-archive@odin.ietf.org>; Fri, 6 Oct 2000 14:02:47 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e96EcdF07344
	for l2tp-list; Fri, 6 Oct 2000 07:38: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 e96EcZl07338
	for <l2tp@l2tp.net>; Fri, 6 Oct 2000 07:38:35 -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 HAA29353 for <l2tp@ipsec.org>; Fri, 6 Oct 2000 07:44:51 -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 HAA16575;
	Fri, 6 Oct 2000 07:44:46 -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 KAA13961;
	Fri, 6 Oct 2000 10:44:45 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.9.3+Sun/8.9.3) id KAA07334;
	Fri, 6 Oct 2000 10:44:48 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14813.58720.71376.625782@gargle.gargle.HOWL>
Date: Fri, 6 Oct 2000 10:44:48 -0400 (EDT)
From: James Carlson <james.d.carlson@east.sun.com>
To: Klausberger Walter <walter.klausberger@siemens.at>
Cc: l2tp@ipsec.org
Subject: Re: AW: multilink ppp with l2tp?
In-Reply-To: Klausberger Walter's message of 6 October 2000 16:30:04
References: <D9F2B9CD7BD5D21196BC0800060D9ED601EFBFF1@vies186a.sie.siemens.at>
X-Mailer: VM 6.75 under Emacs 20.7.1
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Klausberger Walter writes:
> I like the idea of terminating the MP in the LAC, although I am not sure if
> anyone ever tried this.
> 
> Let me ask another question. What about MP over multi-chassis?
> - Is it really common to forward the PPP connection from one chassis to the
> other via L2TP, or is there another way (I would have to implement LNS on a
> LAC!)?

I don't know how common it is to use L2TP for this, but it's certainly
the way Xylogics/Bay Networks/Nortel servers worked.  See RFC 2701.

Yes, you do need LNS functionality in the access server to do this.  I
don't understand the "!" in your comment, though, since once you have
LAC functionality there, LNS isn't so hard -- it reuses a fair part of
the code.

There are other, proprietary schemes to forward the MP links within a
multi-chassis group.  I would assume (but don't know for certain) that
Cisco uses L2F.  Ascend/Lucent used an ad-hoc UDP-based protocol (you
can find some reverse-engineered documentation of it in my book) to do
both bundle head discovery and the data forwarding.  I'm not sure what
Livingston/Lucent did.

An alternative is to toss the whole mess out and put the LAC
functionality into the so-called "client" system.  You'd then dial in
using normal MP to the access server for regular Internet (not VPN)
access, and run PPP/L2TP/UDP (or Mobile IP) over that connection.
This avoids the multilink problems in L2TP and, as a bonus, gives
control of the tunneling and security back to the user.  (I'm sure
ISPs wouldn't be thrilled about that; I believe they intend to charge
extra for VPN services.  There are also cases where this couldn't be
made to work, such as if the access server is connected to a non-IP
network and provides no local Internet access.)

> - Is there a common way to distribute information about incomming PPP
> sessions between the chassis?

There are, unfortunately, many proprietary systems.  One (Nortel's) is
documented.  The others, Cisco's SGBP (Stack Group Bidding Protocol)
and Ascend's STACKS, aren't.

> - Would you recommend to terminate the MP in this chassis anyway to avoid
> multiple links over the L2TP to the remote LNS?

Yes, that was my point, though I didn't make it clear enough.  Local
connections are better for MP link forwarding than non-local ones.

-- 
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
Second Edition now available - http://people.ne.mediaone.net/carlson/ppp


From owner-l2tp@diameter.org  Fri Oct  6 16:04: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 SMTP id QAA11935
	for <l2tpext-archive@odin.ietf.org>; Fri, 6 Oct 2000 16:04:21 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e96GZFe07689
	for l2tp-list; Fri, 6 Oct 2000 09:35:15 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from dfw-smtpout4.email.verio.net (dfw-smtpout4.email.verio.net [129.250.36.44])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e96GZCl07683
	for <l2tp@diameter.org>; Fri, 6 Oct 2000 09:35:12 -0700
Received: from [129.250.38.64] (helo=dfw-mmp4.email.verio.net)
	by dfw-smtpout4.email.verio.net with esmtp (Exim 3.12 #7)
	id 13haXG-0005zR-00; Fri, 06 Oct 2000 16:39:50 +0000
Received: from [209.21.27.82] (helo=rapid5.com)
	by dfw-mmp4.email.verio.net with esmtp (Exim 3.15 #4)
	id 13haXF-0000B2-00; Fri, 06 Oct 2000 16:39:49 +0000
Received: from seanixpc32 ([10.1.1.140])
	by rapid5.com (8.9.1b+Sun/8.8.8) with SMTP id JAA19525;
	Fri, 6 Oct 2000 09:39:15 -0700 (PDT)
From: "Srikrish" <Srikrish@rapid5.com>
To: "Siva Sthanukrishnan" <siva@redback.com>
Cc: <l2tp@diameter.org>
Subject: RE: l2tp test tool
Date: Fri, 6 Oct 2000 09:40:56 -0700
Message-ID: <NDBBJPNHOLJCLNDHELHBCEPICCAA.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: <39DD6382.B8DB7027@redback.com>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Anvil (Hammer technologies) provides one L2TP tool.
(which test L2TP protocol stack)

But its not freeware.

I was trying to get some details on that from user
groups sometime back.. and there were mixed responses.
(some said.. its strict RFC complaint testing and lot
of stacks may fail etc.)

Hope this helps

-Srikrishnan

-----Original Message-----
From: owner-l2tp@diameter.org [mailto:owner-l2tp@diameter.org]On Behalf
Of Siva Sthanukrishnan
Sent: October 5, 2000 10:31 PM
To: l2tp@diameter.org
Subject: l2tp test tool


hi all,

  Is there a l2tp test tool that is available for FreeBSD/NetBSD/linux
that can be used to test l2tp implementation?  Thanks.

- Siva




From owner-l2tp@diameter.org  Fri Oct  6 21:45: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 SMTP id VAA17266
	for <l2tpext-archive@odin.ietf.org>; Fri, 6 Oct 2000 21:45:27 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e96MhC708586
	for l2tp-list; Fri, 6 Oct 2000 15:43: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 e96Mh8l08580
	for <l2tp@l2tp.net>; Fri, 6 Oct 2000 15:43:09 -0700
Received: from imchub1.cosinecom.com (imchub1.cosinecom.com [63.88.104.18]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id PAA29771 for <l2tp@ipsec.org>; Fri, 6 Oct 2000 15:49:24 -0700 (PDT)
Received: by imchub1.cosinecom.com with Internet Mail Service (5.5.2650.21)
	id <TFHCKXA6>; Fri, 6 Oct 2000 15:44:02 -0700
Message-ID: <04E4C688484FD41186E100D0B73EC6EF6032BE@exchsrv2.cosinecom.com>
From: Tatsuya Yanagibashi <tyanagibashi@cosinecom.com>
To: "'James Carlson '" <james.d.carlson@east.sun.com>,
        "'Klausberger Walter '"
	 <walter.klausberger@siemens.at>
Cc: "'l2tp@ipsec.org '" <l2tp@ipsec.org>
Subject: RE: AW: multilink ppp with l2tp?
Date: Fri, 6 Oct 2000 15:50:49 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C02FE6.ECA7DC02"
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_01C02FE6.ECA7DC02
Content-Type: text/plain;
	charset="iso-8859-1"


I was working for mp on l2tp problem before. The another 
problem could appear in following situation.

(1)LAC and remote PPP device negotiated LCP config option 
which is including "Multi-Link Endpoint-Discriminator(ED)".

(2)If LNS is going to "re"negotiate LCP config again, this 
ED value might be different from old value which LAC sent 
before.

On normal PPP device implementation, it will not expect to
recieve ED value which is changed during LCP negotiation 
on same physical link. These client implementation cannot 
establish even PPP session itself.

One of solution is LAC is doing ProxyLCP which is including 
original ED value, then LNS must not renegotiate or LNS 
resend the same ED which LAC and client have negotiated 
already during LCP renegotiation, I think.

Regards,   


_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/

 +----+----+     
 |.. .|    |            Tatsuya Yanagibashi
 |_~__|    |     
 | .. |~~_~|             Network Consultant
 | .  |    |          CoSine Communications Inc.
 +----+----+     
 C o S i n e     e-mail:  tyanagibashi@cosinecom.com 
Communications

_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/


-----Original Message-----
From: James Carlson
To: Klausberger Walter
Cc: l2tp@ipsec.org
Sent: 2000/10/06 7:44
Subject: Re: AW: multilink ppp with l2tp?

Klausberger Walter writes:
> I like the idea of terminating the MP in the LAC, although I am not
sure if
> anyone ever tried this.
> 
> Let me ask another question. What about MP over multi-chassis?
> - Is it really common to forward the PPP connection from one chassis
to the
> other via L2TP, or is there another way (I would have to implement LNS
on a
> LAC!)?

I don't know how common it is to use L2TP for this, but it's certainly
the way Xylogics/Bay Networks/Nortel servers worked.  See RFC 2701.

Yes, you do need LNS functionality in the access server to do this.  I
don't understand the "!" in your comment, though, since once you have
LAC functionality there, LNS isn't so hard -- it reuses a fair part of
the code.

There are other, proprietary schemes to forward the MP links within a
multi-chassis group.  I would assume (but don't know for certain) that
Cisco uses L2F.  Ascend/Lucent used an ad-hoc UDP-based protocol (you
can find some reverse-engineered documentation of it in my book) to do
both bundle head discovery and the data forwarding.  I'm not sure what
Livingston/Lucent did.

An alternative is to toss the whole mess out and put the LAC
functionality into the so-called "client" system.  You'd then dial in
using normal MP to the access server for regular Internet (not VPN)
access, and run PPP/L2TP/UDP (or Mobile IP) over that connection.
This avoids the multilink problems in L2TP and, as a bonus, gives
control of the tunneling and security back to the user.  (I'm sure
ISPs wouldn't be thrilled about that; I believe they intend to charge
extra for VPN services.  There are also cases where this couldn't be
made to work, such as if the access server is connected to a non-IP
network and provides no local Internet access.)

> - Is there a common way to distribute information about incomming PPP
> sessions between the chassis?

There are, unfortunately, many proprietary systems.  One (Nortel's) is
documented.  The others, Cisco's SGBP (Stack Group Bidding Protocol)
and Ascend's STACKS, aren't.

> - Would you recommend to terminate the MP in this chassis anyway to
avoid
> multiple links over the L2TP to the remote LNS?

Yes, that was my point, though I didn't make it clear enough.  Local
connections are better for MP link forwarding than non-local ones.

-- 
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
Second Edition now available - http://people.ne.mediaone.net/carlson/ppp

------_=_NextPart_001_01C02FE6.ECA7DC02
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 =
5.5.2650.12">
<TITLE>RE: AW: multilink ppp with l2tp?</TITLE>
</HEAD>
<BODY>
<BR>

<P><FONT SIZE=3D2>I was working for mp on l2tp problem before. The =
another </FONT>
<BR><FONT SIZE=3D2>problem could appear in following situation.</FONT>
</P>

<P><FONT SIZE=3D2>(1)LAC and remote PPP device negotiated LCP config =
option </FONT>
<BR><FONT SIZE=3D2>which is including &quot;Multi-Link =
Endpoint-Discriminator(ED)&quot;.</FONT>
</P>

<P><FONT SIZE=3D2>(2)If LNS is going to &quot;re&quot;negotiate LCP =
config again, this </FONT>
<BR><FONT SIZE=3D2>ED value might be different from old value which LAC =
sent </FONT>
<BR><FONT SIZE=3D2>before.</FONT>
</P>

<P><FONT SIZE=3D2>On normal PPP device implementation, it will not =
expect to</FONT>
<BR><FONT SIZE=3D2>recieve ED value which is changed during LCP =
negotiation </FONT>
<BR><FONT SIZE=3D2>on same physical link. These client implementation =
cannot </FONT>
<BR><FONT SIZE=3D2>establish even PPP session itself.</FONT>
</P>

<P><FONT SIZE=3D2>One of solution is LAC is doing ProxyLCP which is =
including </FONT>
<BR><FONT SIZE=3D2>original ED value, then LNS must not renegotiate or =
LNS </FONT>
<BR><FONT SIZE=3D2>resend the same ED which LAC and client have =
negotiated </FONT>
<BR><FONT SIZE=3D2>already during LCP renegotiation, I think.</FONT>
</P>

<P><FONT SIZE=3D2>Regards,&nbsp;&nbsp; </FONT>
</P>
<BR>

<P><FONT =
SIZE=3D2>_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_=
/_/</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;+----+----+&nbsp;&nbsp;&nbsp;&nbsp; </FONT>
<BR><FONT SIZE=3D2>&nbsp;|.. .|&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Tatsuya Yanagibashi</FONT>
<BR><FONT SIZE=3D2>&nbsp;|_~__|&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp; </FONT>
<BR><FONT SIZE=3D2>&nbsp;| .. =
|~~_~|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp; Network Consultant</FONT>
<BR><FONT SIZE=3D2>&nbsp;| .&nbsp; |&nbsp;&nbsp;&nbsp; =
|&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CoSine =
Communications Inc.</FONT>
<BR><FONT SIZE=3D2>&nbsp;+----+----+&nbsp;&nbsp;&nbsp;&nbsp; </FONT>
<BR><FONT SIZE=3D2>&nbsp;C o S i n e&nbsp;&nbsp;&nbsp;&nbsp; =
e-mail:&nbsp; tyanagibashi@cosinecom.com </FONT>
<BR><FONT SIZE=3D2>Communications</FONT>
</P>

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

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: James Carlson</FONT>
<BR><FONT SIZE=3D2>To: Klausberger Walter</FONT>
<BR><FONT SIZE=3D2>Cc: l2tp@ipsec.org</FONT>
<BR><FONT SIZE=3D2>Sent: 2000/10/06 7:44</FONT>
<BR><FONT SIZE=3D2>Subject: Re: AW: multilink ppp with l2tp?</FONT>
</P>

<P><FONT SIZE=3D2>Klausberger Walter writes:</FONT>
<BR><FONT SIZE=3D2>&gt; I like the idea of terminating the MP in the =
LAC, although I am not</FONT>
<BR><FONT SIZE=3D2>sure if</FONT>
<BR><FONT SIZE=3D2>&gt; anyone ever tried this.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Let me ask another question. What about MP over =
multi-chassis?</FONT>
<BR><FONT SIZE=3D2>&gt; - Is it really common to forward the PPP =
connection from one chassis</FONT>
<BR><FONT SIZE=3D2>to the</FONT>
<BR><FONT SIZE=3D2>&gt; other via L2TP, or is there another way (I =
would have to implement LNS</FONT>
<BR><FONT SIZE=3D2>on a</FONT>
<BR><FONT SIZE=3D2>&gt; LAC!)?</FONT>
</P>

<P><FONT SIZE=3D2>I don't know how common it is to use L2TP for this, =
but it's certainly</FONT>
<BR><FONT SIZE=3D2>the way Xylogics/Bay Networks/Nortel servers =
worked.&nbsp; See RFC 2701.</FONT>
</P>

<P><FONT SIZE=3D2>Yes, you do need LNS functionality in the access =
server to do this.&nbsp; I</FONT>
<BR><FONT SIZE=3D2>don't understand the &quot;!&quot; in your comment, =
though, since once you have</FONT>
<BR><FONT SIZE=3D2>LAC functionality there, LNS isn't so hard -- it =
reuses a fair part of</FONT>
<BR><FONT SIZE=3D2>the code.</FONT>
</P>

<P><FONT SIZE=3D2>There are other, proprietary schemes to forward the =
MP links within a</FONT>
<BR><FONT SIZE=3D2>multi-chassis group.&nbsp; I would assume (but don't =
know for certain) that</FONT>
<BR><FONT SIZE=3D2>Cisco uses L2F.&nbsp; Ascend/Lucent used an ad-hoc =
UDP-based protocol (you</FONT>
<BR><FONT SIZE=3D2>can find some reverse-engineered documentation of it =
in my book) to do</FONT>
<BR><FONT SIZE=3D2>both bundle head discovery and the data =
forwarding.&nbsp; I'm not sure what</FONT>
<BR><FONT SIZE=3D2>Livingston/Lucent did.</FONT>
</P>

<P><FONT SIZE=3D2>An alternative is to toss the whole mess out and put =
the LAC</FONT>
<BR><FONT SIZE=3D2>functionality into the so-called &quot;client&quot; =
system.&nbsp; You'd then dial in</FONT>
<BR><FONT SIZE=3D2>using normal MP to the access server for regular =
Internet (not VPN)</FONT>
<BR><FONT SIZE=3D2>access, and run PPP/L2TP/UDP (or Mobile IP) over =
that connection.</FONT>
<BR><FONT SIZE=3D2>This avoids the multilink problems in L2TP and, as a =
bonus, gives</FONT>
<BR><FONT SIZE=3D2>control of the tunneling and security back to the =
user.&nbsp; (I'm sure</FONT>
<BR><FONT SIZE=3D2>ISPs wouldn't be thrilled about that; I believe they =
intend to charge</FONT>
<BR><FONT SIZE=3D2>extra for VPN services.&nbsp; There are also cases =
where this couldn't be</FONT>
<BR><FONT SIZE=3D2>made to work, such as if the access server is =
connected to a non-IP</FONT>
<BR><FONT SIZE=3D2>network and provides no local Internet =
access.)</FONT>
</P>

<P><FONT SIZE=3D2>&gt; - Is there a common way to distribute =
information about incomming PPP</FONT>
<BR><FONT SIZE=3D2>&gt; sessions between the chassis?</FONT>
</P>

<P><FONT SIZE=3D2>There are, unfortunately, many proprietary =
systems.&nbsp; One (Nortel's) is</FONT>
<BR><FONT SIZE=3D2>documented.&nbsp; The others, Cisco's SGBP (Stack =
Group Bidding Protocol)</FONT>
<BR><FONT SIZE=3D2>and Ascend's STACKS, aren't.</FONT>
</P>

<P><FONT SIZE=3D2>&gt; - Would you recommend to terminate the MP in =
this chassis anyway to</FONT>
<BR><FONT SIZE=3D2>avoid</FONT>
<BR><FONT SIZE=3D2>&gt; multiple links over the L2TP to the remote =
LNS?</FONT>
</P>

<P><FONT SIZE=3D2>Yes, that was my point, though I didn't make it clear =
enough.&nbsp; Local</FONT>
<BR><FONT SIZE=3D2>connections are better for MP link forwarding than =
non-local ones.</FONT>
</P>

<P><FONT SIZE=3D2>-- </FONT>
<BR><FONT SIZE=3D2>James Carlson, Internet =
Engineering&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&lt;james.d.carlson@east.sun.com&gt;</FONT>
<BR><FONT SIZE=3D2>SUN Microsystems / 1 Network =
Drive&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
71.234W&nbsp;&nbsp; Vox +1 781 442 2084</FONT>
<BR><FONT SIZE=3D2>MS UBUR02-212 / Burlington MA 01803-2757&nbsp;&nbsp; =
42.497N&nbsp;&nbsp; Fax +1 781 442 1677</FONT>
<BR><FONT SIZE=3D2>Second Edition now available - <A =
HREF=3D"http://people.ne.mediaone.net/carlson/ppp" =
TARGET=3D"_blank">http://people.ne.mediaone.net/carlson/ppp</A></FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C02FE6.ECA7DC02--


From owner-l2tp@diameter.org  Sat Oct  7 01:32:48 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 SMTP id BAA24135
	for <l2tpext-archive@odin.ietf.org>; Sat, 7 Oct 2000 01:32:48 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e9726iX08947
	for l2tp-list; Fri, 6 Oct 2000 19:06: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 e9726Zl08941
	for <l2tp@l2tp.net>; Fri, 6 Oct 2000 19:06:35 -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 TAA29914 for <l2tp@ipsec.org>; Fri, 6 Oct 2000 19:12:51 -0700 (PDT)
Received: (from carlson@localhost)
	by h006008986325.ne.mediaone.net (8.11.0/8.11.0) id e972CnV06028;
	Fri, 6 Oct 2000 22:12:49 -0400
From: James Carlson <carlson@workingcode.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14814.34464.361607.964083@h006008986325.ne.mediaone.net>
Date: Fri, 6 Oct 2000 22:12:48 -0400 (EDT)
To: Tatsuya Yanagibashi <tyanagibashi@cosinecom.com>
Cc: "'James Carlson '" <james.d.carlson@east.sun.com>,
        "'Klausberger Walter '"
	 <walter.klausberger@siemens.at>,
        "'l2tp@ipsec.org '" <l2tp@ipsec.org>
Subject: RE: AW: multilink ppp with l2tp?
In-Reply-To: Tatsuya Yanagibashi's message of 6 October 2000 15:50:49
References: <04E4C688484FD41186E100D0B73EC6EF6032BE@exchsrv2.cosinecom.com>
X-Mailer: VM 6.75 under Emacs 20.6.1
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Tatsuya Yanagibashi writes:
> (2)If LNS is going to "re"negotiate LCP config again, this 
> ED value might be different from old value which LAC sent 
> before.
> 
> On normal PPP device implementation, it will not expect to
> recieve ED value which is changed during LCP negotiation 
> on same physical link. These client implementation cannot 
> establish even PPP session itself.

Right.  Actually, in any decent implementation, the changing of the ED
doesn't itself cause a problem.  It merely means that if it was part
of a bundle with the original value, then it's not with the new value.

The real problem is that the initial value that the LAC sends out may
not match what the client side saw from another LAC or the LNS itself.

Consider a client that establishes link 1 through LAC A, then
renegotiates LCP with the LNS in order to get MP running.  In the
process it gets an ED value from its peer.  The client then attempts
to establish link 2 through LAC B.  If LAC B unwittingly offers an ED
value -- on initial negotiation before the LNS identity is even known
-- that happens to be different from the one that the LNS has offered
for its side, then the client will tear down link 2, since it appears
to have landed on the wrong system.

The client side doesn't (and shouldn't) know that these LACs are
standing in the way of connecting to the LNS.  The problem is that, in
terms of the packets the client sees, the LACs don't always look
exactly the same as the LNS does.

> One of solution is LAC is doing ProxyLCP which is including 
> original ED value, then LNS must not renegotiate or LNS 
> resend the same ED which LAC and client have negotiated 
> already during LCP renegotiation, I think.

Actually, it's worse than that.  By definition of MP, the ED values
that the "client" end of the link sees from the peer must be the same
on all links.  This implies that the LACs must all give the same ED
value.

ProxyLCP doesn't fix this.  (In fact, I see nothing for which ProxyLCP
is actually required.  But that's another story ...)

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


From owner-l2tp@diameter.org  Tue Oct 10 12:40: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 SMTP id MAA07842
	for <l2tpext-archive@odin.ietf.org>; Tue, 10 Oct 2000 12:40:05 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e9AD8ch17013
	for l2tp-list; Tue, 10 Oct 2000 06:08:38 -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 e9AD8Yl17007
	for <l2tp@l2tp.net>; Tue, 10 Oct 2000 06:08:34 -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 GAA08894 for <l2tp@ipsec.org>; Tue, 10 Oct 2000 06:15:01 -0700 (PDT)
Received: from cvis03.gpt.co.uk (unverified) by cvis29.marconicomms.com
 (Content Technologies SMTPRS 4.1.5) with ESMTP id <Tc363f43d4f2b76a331@cvis29.marconicomms.com> for <l2tp@ipsec.org>;
 Tue, 10 Oct 2000 13:13:31 +0100
Received: from marconicomms.com by cvis03.gpt.co.uk with SMTP
 (8.8.8+Sun/cvms-28) id NAA21270; Tue, 10 Oct 2000 13:13:29 +0100 (BST)
Received: by marconicomms.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 80256974.0042D80E ; Tue, 10 Oct 2000 13:10:06 +0100
X-Lotus-FromDomain: MCMAIN@MCEXT
From: "Luca Risso" <Luca.Risso@marconi.com>
To: l2tp@ipsec.org
Message-ID: <80256974.00427925.00@marconicomms.com>
Date: Tue, 10 Oct 2000 14:05:05 +0200
Subject: WIN2000 as LNS
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-l2tp@diameter.org
Precedence: bulk



Hi,
does anybody know if Win2000 is able to work as a L2TP Network Server (LNS)
without using IPSec?
If it is possible, how can I configure it?

Thanks in advance

     Luca Risso




From owner-l2tp@diameter.org  Tue Oct 10 15:43: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 SMTP id PAA11837
	for <l2tpext-archive@odin.ietf.org>; Tue, 10 Oct 2000 15:43:09 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e9AGxbW17209
	for l2tp-list; Tue, 10 Oct 2000 09:59: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 e9AGxXl17203
	for <l2tp@l2tp.net>; Tue, 10 Oct 2000 09:59:33 -0700
Received: from thalia.fm.intel.com (thalia.fm.intel.com [132.233.247.11]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id KAA09222 for <l2tp@ipsec.org>; Tue, 10 Oct 2000 10:06:01 -0700 (PDT)
Received: from SMTP (fmsmsxvs04-1.fm.intel.com [132.233.42.204])
	by thalia.fm.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.31 2000/08/22 00:15:13 dmccart Exp $) with SMTP id RAA20995;
	Tue, 10 Oct 2000 17:07:10 GMT
Received: from fmsmsx26.fm.intel.com ([132.233.48.26]) by 132.233.48.204
  (Norton AntiVirus for Internet Email Gateways 1.0) ;
  Tue, 10 Oct 2000 17:05:55 0000 (GMT)
Received: by fmsmsx26.fm.intel.com with Internet Mail Service (5.5.2650.21)
	id <4LBQTQW8>; Tue, 10 Oct 2000 10:05:54 -0700
Message-ID: <F70F37F77E9FD211AC3F00A0C96B78DA0678A8C7@orsmsx47.jf.intel.com>
From: "Veeraiyan, Ayyappan" <ayyappan.veeraiyan@intel.com>
To: "Veeraiyan, Ayyappan" <ayyappan.veeraiyan@intel.com>,
        "'Luca Risso'"
	 <Luca.Risso@marconi.com>,
        "'l2tp@ipsec.org'" <l2tp@ipsec.org>
Subject: RE: WIN2000 as LNS
Date: Tue, 10 Oct 2000 10:05:47 -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

Quick correction.

> 	2. Create a DWORD value with a name "ProhibitIPSec" and 
> give a value of 1 in the left hand side of the pane.

In RIGHT HAND SIDE of the pane.

-Ayyappan V.

> 
> Hi,
> These are the steps for making Win2K as LNS without IPSec..
> Assuming, you already configured Win2k box as 'LNS with 
> IPSec' successfully.
> 	
> 	1. Go to 
> HKEY_LOCAL_MACHINE\SYSTEM\Currentcontrolset\Services\RasMan\Pa
> rameters in the Win2k Registry.
> 	2. Create a DWORD value with a name "ProhibitIPSec" and 
> give a value of 1 in the left hand side of the pane.
> 	3. In the Dos box, execute the following commands.
> 		Stop remoteaccess
> 		start remoteaccess
> 		Stop policyagent
> 	That's it.
> 	
> 	Now L2TP traffic will go in CLEAR.
> 
> Hope this helps.
> 
> -Ayyappan V.
> 	
> > -----Original Message-----
> > From: Luca Risso [mailto:Luca.Risso@marconi.com]
> > Sent: Tuesday, October 10, 2000 5:05 AM
> > To: l2tp@ipsec.org
> > Subject: WIN2000 as LNS
> > 
> > 
> > 
> > 
> > Hi,
> > does anybody know if Win2000 is able to work as a L2TP 
> > Network Server (LNS)
> > without using IPSec?
> > If it is possible, how can I configure it?
> > 
> > Thanks in advance
> > 
> >      Luca Risso
> > 
> > 
> > 
> 



From owner-l2tp@diameter.org  Tue Oct 10 15:49: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 SMTP id PAA12038
	for <l2tpext-archive@odin.ietf.org>; Tue, 10 Oct 2000 15:49:22 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e9AH0h717220
	for l2tp-list; Tue, 10 Oct 2000 10:00:43 -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 e9AH0el17214
	for <l2tp@l2tp.net>; Tue, 10 Oct 2000 10:00:40 -0700
Received: from thalia.fm.intel.com (thalia.fm.intel.com [132.233.247.11]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id KAA09225 for <l2tp@ipsec.org>; Tue, 10 Oct 2000 10:07:08 -0700 (PDT)
Received: from SMTP (fmsmsxvs05-1.fm.intel.com [132.233.42.205])
	by thalia.fm.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.31 2000/08/22 00:15:13 dmccart Exp $) with SMTP id RAA21557;
	Tue, 10 Oct 2000 17:08:19 GMT
Received: from fmsmsx28.fm.intel.com ([132.233.48.28]) by 132.233.48.205
  (Norton AntiVirus for Internet Email Gateways 1.0) ;
  Tue, 10 Oct 2000 17:03:17 0000 (GMT)
Received: by fmsmsx28.fm.intel.com with Internet Mail Service (5.5.2650.21)
	id <4L8HXF92>; Tue, 10 Oct 2000 10:03:16 -0700
Message-ID: <F70F37F77E9FD211AC3F00A0C96B78DA0678A8C6@orsmsx47.jf.intel.com>
From: "Veeraiyan, Ayyappan" <ayyappan.veeraiyan@intel.com>
To: "'Luca Risso'" <Luca.Risso@marconi.com>, l2tp@ipsec.org
Cc: "Veeraiyan, Ayyappan" <ayyappan.veeraiyan@intel.com>
Subject: RE: WIN2000 as LNS
Date: Tue, 10 Oct 2000 10:03:10 -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,
These are the steps for making Win2K as LNS without IPSec..
Assuming, you already configured Win2k box as 'LNS with IPSec' successfully.
	
	1. Go to
HKEY_LOCAL_MACHINE\SYSTEM\Currentcontrolset\Services\RasMan\Parameters in
the Win2k Registry.
	2. Create a DWORD value with a name "ProhibitIPSec" and give a value
of 1 in the left hand side of the pane.
	3. In the Dos box, execute the following commands.
		Stop remoteaccess
		start remoteaccess
		Stop policyagent
	That's it.
	
	Now L2TP traffic will go in CLEAR.

Hope this helps.

-Ayyappan V.
	
> -----Original Message-----
> From: Luca Risso [mailto:Luca.Risso@marconi.com]
> Sent: Tuesday, October 10, 2000 5:05 AM
> To: l2tp@ipsec.org
> Subject: WIN2000 as LNS
> 
> 
> 
> 
> Hi,
> does anybody know if Win2000 is able to work as a L2TP 
> Network Server (LNS)
> without using IPSec?
> If it is possible, how can I configure it?
> 
> Thanks in advance
> 
>      Luca Risso
> 
> 
> 



From owner-l2tp@diameter.org  Tue Oct 10 15:54: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 SMTP id PAA12157
	for <l2tpext-archive@odin.ietf.org>; Tue, 10 Oct 2000 15:54:23 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e9AHGUu17261
	for l2tp-list; Tue, 10 Oct 2000 10:16:30 -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 e9AHFCl17255
	for <l2tp@l2tp.net>; Tue, 10 Oct 2000 10:15:12 -0700
Received: from enterprise.reliacom.com (enterprise.reliacom.com [209.249.101.16]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id KAA09235 for <l2tp@ipsec.org>; Tue, 10 Oct 2000 10:21:40 -0700 (PDT)
Received: by exchange.reliacom.com with Internet Mail Service (5.5.2650.21)
	id <4QTXJ8J7>; Tue, 10 Oct 2000 13:17:10 -0400
Message-ID: <30D269155F5DD311A2620008C709AC5E8FB0A2@exchange.reliacom.com>
From: Scot Kight <skight@reliacom.com>
To: "'Luca.Risso@marconi.com'" <Luca.Risso@marconi.com>,
        "'l2tp@ipsec.org'" <l2tp@ipsec.org>
Subject: Re: WIN2000 as LNS
Date: Tue, 10 Oct 2000 13:17:08 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain
Sender: owner-l2tp@diameter.org
Precedence: bulk

Yes you can.  It requires a reg mod to not auto establish the ipsec setup.

Do a search for ipsec on support.microsoft.com under win2k
I think its 
Hklm/system/ccs/?/prohibitipsec with the bit set at 1.  The key needs to be
added, so you can't search for it in the reg... 


From owner-l2tp@diameter.org  Tue Oct 10 17:10:20 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 SMTP id RAA13474
	for <l2tpext-archive@odin.ietf.org>; Tue, 10 Oct 2000 17:10:19 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e9AHPxw17307
	for l2tp-list; Tue, 10 Oct 2000 10:25: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 e9AHPtl17301
	for <l2tp@l2tp.net>; Tue, 10 Oct 2000 10:25:55 -0700
Received: from mailsrv.campio.com ([38.186.47.7]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id KAA09241 for <l2tp@ipsec.org>; Tue, 10 Oct 2000 10:32:13 -0700 (PDT)
Received: by MAILSRV with Internet Mail Service (5.5.2650.21)
	id <4TM41N4G>; Tue, 10 Oct 2000 10:41:53 -0700
Message-ID: <D55193A1090CD4118171009027DC8CEB1E6A0A@MAILSRV>
From: Naveen PN Gowda <NaveenPN@campio.com>
To: Luca Risso <Luca.Risso@marconi.com>, l2tp@ipsec.org
Subject: RE: WIN2000 as LNS
Date: Tue, 10 Oct 2000 10:41:52 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C032E1.602BFDA0"
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_01C032E1.602BFDA0
Content-Type: text/plain;
	charset="ISO-8859-1"

Hi,
	Refer to following link, this may be useful
	
http://www.diameter.org/cgi-bin/lwgate/L2TP/archives/l2tp.archive.0004/date/
article-73.html
Naveen

-----Original Message-----
From: Luca Risso [mailto:Luca.Risso@marconi.com]
Sent: Tuesday, October 10, 2000 5:05 AM
To: l2tp@ipsec.org
Subject: WIN2000 as LNS




Hi,
does anybody know if Win2000 is able to work as a L2TP Network Server (LNS)
without using IPSec?
If it is possible, how can I configure it?

Thanks in advance

     Luca Risso


------_=_NextPart_001_01C032E1.602BFDA0
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 =
5.5.2652.35">
<TITLE>RE: WIN2000 as LNS</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Hi,</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2>Refer to =
following link, this may be useful</FONT>
<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <FONT SIZE=3D2><A =
HREF=3D"http://www.diameter.org/cgi-bin/lwgate/L2TP/archives/l2tp.archiv=
e.0004/date/article-73.html" =
TARGET=3D"_blank">http://www.diameter.org/cgi-bin/lwgate/L2TP/archives/l=
2tp.archive.0004/date/article-73.html</A></FONT>
<BR><FONT SIZE=3D2>Naveen</FONT>
</P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Luca Risso [<A =
HREF=3D"mailto:Luca.Risso@marconi.com">mailto:Luca.Risso@marconi.com</A>=
]</FONT>
<BR><FONT SIZE=3D2>Sent: Tuesday, October 10, 2000 5:05 AM</FONT>
<BR><FONT SIZE=3D2>To: l2tp@ipsec.org</FONT>
<BR><FONT SIZE=3D2>Subject: WIN2000 as LNS</FONT>
</P>
<BR>
<BR>
<BR>

<P><FONT SIZE=3D2>Hi,</FONT>
<BR><FONT SIZE=3D2>does anybody know if Win2000 is able to work as a =
L2TP Network Server (LNS)</FONT>
<BR><FONT SIZE=3D2>without using IPSec?</FONT>
<BR><FONT SIZE=3D2>If it is possible, how can I configure it?</FONT>
</P>

<P><FONT SIZE=3D2>Thanks in advance</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp; Luca Risso</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C032E1.602BFDA0--


From owner-l2tp@diameter.org  Mon Oct 23 07:47: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 SMTP id HAA04892
	for <l2tpext-archive@odin.ietf.org>; Mon, 23 Oct 2000 07:47:21 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e9N82ox01593
	for l2tp-list; Mon, 23 Oct 2000 01:02:50 -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 e9N82mo01587
	for <l2tp@l2tp.net>; Mon, 23 Oct 2000 01:02:48 -0700
Received: from eins.siemens.at (eins.siemens.at [193.81.246.11]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id BAA13721 for <l2tp@ipsec.org>; Mon, 23 Oct 2000 01:08:15 -0700 (PDT)
Received: from scesie13.sie.siemens.at (forix-hme0 [10.1.140.2])
	by eins.siemens.at  with ESMTP id JAA04093
	for <l2tp@ipsec.org>; Mon, 23 Oct 2000 09:58:40 +0200 (MET DST)
Received: (from smap@localhost)
	by scesie13.sie.siemens.at (8.9.3/8.9.3) id KAA08388
	for <l2tp@ipsec.org>; Mon, 23 Oct 2000 10:07:37 +0200 (MET DST)
Received: from vies141a.sie.siemens.at(195.1.196.56) by scesie13 via smap (V2.0beta)
	id xma006927; Mon, 23 Oct 00 10:06:54 +0200
Received: by vies141a.sie.siemens.at with Internet Mail Service (5.5.2650.21)
	id <45G4RWQ6>; Mon, 23 Oct 2000 10:06:47 +0200
Message-ID: <D9F2B9CD7BD5D21196BC0800060D9ED604372F74@vies186a.sie.siemens.at>
From: Klausberger Walter <walter.klausberger@siemens.at>
To: l2tp@ipsec.org
Subject: expired l2tp drafts
Date: Mon, 23 Oct 2000 10:06:45 +0200
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 everybody,

I had a brief look at the actual drafts and I think they need some
refreshment. Especially the L2TP MIB and the Diffserv Draft seem to be
expired. Will there be new versions soon?

Another question:
How do the DiffServ draft and the new RFC (about Diffserv and Tunnels) fit
together?

with best regards
Walter Klausberger

-------------------------------
Siemens AG Austria
Boschstrasse 10
1190 Vienna
Austria

Tel: +49(5)1707-42683
<walter.klausberger@siemens.at>
-------------------------------


From owner-l2tp@diameter.org  Mon Oct 23 13:01: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 SMTP id NAA14553
	for <l2tpext-archive@odin.ietf.org>; Mon, 23 Oct 2000 13:01:44 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e9ND5ZQ02110
	for l2tp-list; Mon, 23 Oct 2000 06:05:35 -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 e9ND5Wo02104
	for <l2tp@l2tp.net>; Mon, 23 Oct 2000 06:05:32 -0700
Received: from tcb.net (tcb.net [205.168.100.1]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id GAA15200 for <l2tp@ipsec.org>; Mon, 23 Oct 2000 06:11:00 -0700 (PDT)
Received: from sofos.tcb.net (sofos.tcb.net [127.0.0.1])
	by tcb.net (8.9.3/8.9.3) with ESMTP id HAA16909;
	Mon, 23 Oct 2000 07:10:54 -0600
Message-Id: <200010231310.HAA16909@tcb.net>
To: Klausberger Walter <walter.klausberger@siemens.at>
cc: l2tp@ipsec.org
From: Danny McPherson <danny@tcb.net>
Reply-To: danny@tcb.net
Subject: Re: expired l2tp drafts 
Date: Mon, 23 Oct 2000 07:10:54 -0600
Sender: owner-l2tp@diameter.org
Precedence: bulk


> I had a brief look at the actual drafts and I think they need some
> refreshment. Especially the L2TP MIB and the Diffserv Draft seem to be
> expired. Will there be new versions soon?
> 
> Another question:
> How do the DiffServ draft and the new RFC (about Diffserv and Tunnels) fit
> together?

We're working with the DS folks (including the author of the DS & Tunnels 
document) on the updated revision of the L2TP DS document.  It should be 
available RSN.

-danny


From owner-l2tp@diameter.org  Mon Oct 23 14:18: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 SMTP id OAA25918
	for <l2tpext-archive@odin.ietf.org>; Mon, 23 Oct 2000 14:18:40 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e9NGC5302475
	for l2tp-list; Mon, 23 Oct 2000 09:12: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 e9NGAho02469
	for <l2tp@l2tp.net>; Mon, 23 Oct 2000 09:10:43 -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 JAA15357 for <l2tp@ipsec.org>; Mon, 23 Oct 2000 09:16:11 -0700 (PDT)
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 JAA06374;
	Mon, 23 Oct 2000 09:19:38 -0700 (PDT)
Message-ID: <39F46575.945F2864@ericsson.com>
Date: Mon, 23 Oct 2000 09:21:09 -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: Klausberger Walter <walter.klausberger@siemens.at>
CC: l2tp@ipsec.org
Subject: Re: expired l2tp drafts
References: <D9F2B9CD7BD5D21196BC0800060D9ED604372F74@vies186a.sie.siemens.at>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

There will be a revised MIB in the next few weeks.

evan
-

Klausberger Walter wrote:
> 
> Hi everybody,
> 
> I had a brief look at the actual drafts and I think they need some
> refreshment. Especially the L2TP MIB and the Diffserv Draft seem to be
> expired. Will there be new versions soon?
> 
> Another question:
> How do the DiffServ draft and the new RFC (about Diffserv and Tunnels) fit
> together?
> 
> with best regards
> Walter Klausberger
> 
> -------------------------------
> Siemens AG Austria
> Boschstrasse 10
> 1190 Vienna
> Austria
> 
> Tel: +49(5)1707-42683
> <walter.klausberger@siemens.at>
> -------------------------------


From owner-l2tp@diameter.org  Mon Oct 23 21:07: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 SMTP id VAA21684
	for <l2tpext-archive@odin.ietf.org>; Mon, 23 Oct 2000 21:07:50 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e9NMd9502888
	for l2tp-list; Mon, 23 Oct 2000 15:39:09 -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 e9NMc8o02882
	for <l2tp@l2tp.net>; Mon, 23 Oct 2000 15:38:09 -0700
Received: from baynet.baynetworks.com (ns1.BayNetworks.COM [134.177.3.20]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id PAA15822 for <l2tp@ipsec.org>; Mon, 23 Oct 2000 15:43:38 -0700 (PDT)
Received: from mailhost.BayNetworks.COM (h016b.s86b1.BayNetworks.COM [134.177.1.107])
	by baynet.baynetworks.com (8.9.1/8.9.1) with ESMTP id PAA05092
	for <l2tp@ipsec.org>; Mon, 23 Oct 2000 15:41:28 -0700 (PDT)
Received: from shasta-exch.shastanets.com (mailserver.shastanets.com [47.82.16.150])
	by mailhost.BayNetworks.COM (8.9.1/8.8.8) with ESMTP id PAA15326
	for <l2tp@ipsec.org>; Mon, 23 Oct 2000 15:41:27 -0700 (PDT)
Received: by mailserver.shastanets.com with Internet Mail Service (5.5.2650.21)
	id <T7JFGBHG>; Mon, 23 Oct 2000 15:40:53 -0700
Message-ID: <940E42DB5D7FD4119C420004ACE6E0A0341420@mailserver.shastanets.com>
From: Vipin Jain <vipin@shastanets.com>
To: l2tp@ipsec.org
Subject: ZLB Ack question
Date: Mon, 23 Oct 2000 15:40:47 -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



LAC  ---- seq #1 --> *LOST*       LNS
LAC  ----- seq #2 --------------> LNS
LAC  ------ seq #3 -------------> LNS
LAC  ------ seq #4 -------------> LNS
LAC  <------ seq #33 ------------- LNS

Should LAC ZLB Ack LNS seq#33?
If so what should be Ns in ZLB Ack?
Or should LAC retransmit seq #1 to LNS acking seq#33?

**** LAC Actually times out on seq #1 here ***



Thanks for any insights.
-- vipin


From owner-l2tp@diameter.org  Tue Oct 24 00:07: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 SMTP id AAA24259
	for <l2tpext-archive@odin.ietf.org>; Tue, 24 Oct 2000 00:07:01 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e9O1AQZ02989
	for l2tp-list; Mon, 23 Oct 2000 18:10: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 e9O1ANo02983
	for <l2tp@l2tp.net>; Mon, 23 Oct 2000 18:10:23 -0700
Received: from southpass.baynetworks.com (ns2.BayNetworks.COM [134.177.3.16]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id SAA15944 for <l2tp@ipsec.org>; Mon, 23 Oct 2000 18:15:53 -0700 (PDT)
Received: from mailhost.BayNetworks.COM (h016b.s86b1.BayNetworks.COM [134.177.1.107])
	by southpass.baynetworks.com (8.9.1/8.9.1) with ESMTP id SAA06910;
	Mon, 23 Oct 2000 18:06:49 -0700 (PDT)
Received: from shasta-exch.shastanets.com (mailserver.shastanets.com [47.82.16.150])
	by mailhost.BayNetworks.COM (8.9.1/8.8.8) with ESMTP id SAA28680;
	Mon, 23 Oct 2000 18:13:43 -0700 (PDT)
Received: by mailserver.shastanets.com with Internet Mail Service (5.5.2650.21)
	id <T7JFGCB8>; Mon, 23 Oct 2000 18:13:09 -0700
Message-ID: <940E42DB5D7FD4119C420004ACE6E0A0341427@mailserver.shastanets.com>
From: Vipin Jain <vipin@shastanets.com>
To: "'Madhvi_Verma@3com.com'" <Madhvi_Verma@3Com.COM>,
        Vipin Jain
	 <vipin@shastanets.com>
Cc: l2tp@ipsec.org
Subject: RE: ZLB Ack question
Date: Mon, 23 Oct 2000 18:13:04 -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

<<thans for responding, more comments in>>

-----Original Message-----
From: Madhvi_Verma@3com.com [mailto:Madhvi_Verma@3com.com]
Sent: Monday, October 23, 2000 6:07 PM
To: Vipin Jain
Cc: l2tp@ipsec.org
Subject: Re: ZLB Ack question




Vipin,
The LAC retransmitting the seq # 1 and acking seq # 33 are two independent
things.
It should retransmit seq #1 only when the retransmit timer for #1 fires.
<<agree>>

1 case :
Assume , for this case, that the timer has not yet fired when it gets seq
#33.
At this point, it may either ack #33 with a ZLB (assuming it has no data to
send, and Ns for the ZLB will be 5), or apply some sort of delayed ack
mechanism; i.e wait for some control packet to be sent and make its Nr as
34.
<< My question was about this case: Delayed ack timer expires before re-xmt
timer>>
<< remote is going to throw this because this is out of its receive window,
there by creating unwanted noise traffic, any way to avoid this unwanted and
useless traffic? >>

2 case:
Assume , now  the case where the retransmit timer for #1 fires just after it
gets #33. In that scenario, it could transmit the packet  with Ns=1 and Nr =
34.
<<agree>>

Madhvi




Vipin Jain <vipin@shastanets.com> on 10/23/2000 11:40:47 PM

Sent by:  Vipin Jain <vipin@shastanets.com>


To:   l2tp@ipsec.org
cc:    (Madhvi Verma/MW/US/3Com)
Subject:  ZLB Ack question





LAC  ---- seq #1 --> *LOST*       LNS
LAC  ----- seq #2 --------------> LNS
LAC  ------ seq #3 -------------> LNS
LAC  ------ seq #4 -------------> LNS
LAC  <------ seq #33 ------------- LNS

Should LAC ZLB Ack LNS seq#33?
If so what should be Ns in ZLB Ack?
Or should LAC retransmit seq #1 to LNS acking seq#33?

**** LAC Actually times out on seq #1 here ***



Thanks for any insights.
-- vipin





From owner-l2tp@diameter.org  Tue Oct 24 01:07: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 SMTP id BAA06515
	for <l2tpext-archive@odin.ietf.org>; Tue, 24 Oct 2000 01:07:26 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e9O3b2W03076
	for l2tp-list; Mon, 23 Oct 2000 20:37:02 -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 e9O3axo03070
	for <l2tp@l2tp.net>; Mon, 23 Oct 2000 20:36:59 -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 UAA16072 for <l2tp@ipsec.org>; Mon, 23 Oct 2000 20:42:29 -0700 (PDT)
Received: from cosinecom.com (016.cosine.nttpc.gr.jp [202.229.42.16] (may be forged))
	by center.mshindo.net (8.9.3/3.7W/00041811) with SMTP id MAA34234;
	Tue, 24 Oct 2000 12:52:42 +0900 (JST)
Date: Tue, 24 Oct 2000 12:43:03 +0900 (JST)
Message-Id: <20001024.124303.41626315.mshindo@mshindo.net>
To: vipin@shastanets.com
Cc: l2tp@ipsec.org
Subject: Re: ZLB Ack question
From: Motonori Shindo <mshindo@mshindo.net>
In-Reply-To: <940E42DB5D7FD4119C420004ACE6E0A0341420@mailserver.shastanets.com>
References: <940E42DB5D7FD4119C420004ACE6E0A0341420@mailserver.shastanets.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

Vipin,

From: Vipin Jain <vipin@shastanets.com>
Subject: ZLB Ack question
Date: Mon, 23 Oct 2000 15:40:47 -0700

> LAC  ---- seq #1 --> *LOST*       LNS
> LAC  ----- seq #2 --------------> LNS
> LAC  ------ seq #3 -------------> LNS
> LAC  ------ seq #4 -------------> LNS
> LAC  <------ seq #33 ------------- LNS
> 
> Should LAC ZLB Ack LNS seq#33?

Yes, it should Ack it. However, it doesn't have to be ZLB. It could
also be any control message, assuming there is still an open window
for this control channel.

> If so what should be Ns in ZLB Ack?

Ns should be 5. 

> Or should LAC retransmit seq #1 to LNS acking seq#33?

LAC may retransmit seq #1 if the timer expires associated with
it. This retransmission could also act as an Ack for seq #33 message.
Please be aware that Ns of retransmitted packet must remains the same
but Nr must be updated, reflecting the most up-to-date Nr value.

Whether the acknowledge for seq#33 (by sending a message with Nr=34)
is done by sending a ZLB or a retransmission of seq#1 is up to the
implementation and often a timing issue.

Regards,

> **** LAC Actually times out on seq #1 here ***
> 
> 
> 
> Thanks for any insights.
> -- vipin
> 

=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=
 +----+----+     
 |.. .|    |     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  Sun Oct 29 11:16: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 SMTP id LAA11497
	for <l2tpext-archive@odin.ietf.org>; Sun, 29 Oct 2000 11:16:03 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e9TEN2j13177
	for l2tp-list; Sun, 29 Oct 2000 06:23:02 -0800
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 e9TEMwo13171
	for <l2tp@l2tp.net>; Sun, 29 Oct 2000 06:22:59 -0800
Received: from brahma.roc.com ([202.54.67.218]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id GAA05242 for <l2tp@ipsec.org>; Sun, 29 Oct 2000 06:28:41 -0800 (PST)
Received: from sridhar.roc.com ([172.16.5.52])
	by brahma.roc.com (8.8.5/8.8.5) with SMTP id UAA04259
	for <l2tp@ipsec.org>; Sun, 29 Oct 2000 20:04:03 +0530 (IST)
Message-Id: <200010291434.UAA04259@brahma.roc.com>
X-Sender: sridhar@172.16.5.5
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0
Date: Sun, 29 Oct 2000 20:07:22 +0530
To: l2tp@ipsec.org
From: Sridhar Malarothu <sridhar@trinc.com>
Subject: Non Existing Tunnel
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-l2tp@diameter.org
Precedence: bulk

Hi,

   There may be possible situations where Control
Messages like Hello, session messages, etc can be 
received from a Peer for a non-existing Tunnel.

Should StopCCN message be sent to the Peer. If so
the Tunnel Id in StopCCN Hdr should be kept as zero
and the Assigned Tunnel Id in the StopCCN should be
kept as whatever the Tunnel ID in the Hdr of the
control message received from peer.

Or should the control message silently be discarded, so
that the Peer's reliable logic closes the Tunnel because
of failure to deliver a control message.

If a data message is received for a non-existing tunnel
should a StopCCN message be sent to Peer.

Also is there a possibility to receive a data message or 
WEN, SLI messages for a non-existing session (Tunnel is present).
If so what action should be taken.


Best Regards
Sridhar


From owner-l2tp@diameter.org  Sun Oct 29 12:17: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 SMTP id MAA00930
	for <l2tpext-archive@odin.ietf.org>; Sun, 29 Oct 2000 12:17:24 -0500 (EST)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e9TE60m13153
	for l2tp-list; Sun, 29 Oct 2000 06:06:00 -0800
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 e9TE5Wo13147
	for <l2tp@l2tp.net>; Sun, 29 Oct 2000 06:05:32 -0800
Received: from brahma.roc.com ([202.54.67.218]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id GAA05234 for <l2tp@ipsec.org>; Sun, 29 Oct 2000 06:11:16 -0800 (PST)
Received: from sridhar.roc.com ([172.16.5.52])
	by brahma.roc.com (8.8.5/8.8.5) with SMTP id TAA04025
	for <l2tp@ipsec.org>; Sun, 29 Oct 2000 19:46:44 +0530 (IST)
Message-Id: <200010291416.TAA04025@brahma.roc.com>
X-Sender: sridhar@172.16.5.5
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0
Date: Sun, 29 Oct 2000 19:50:03 +0530
To: l2tp@ipsec.org
From: Sridhar Malarothu <sridhar@trinc.com>
Subject: Control Message Header Errors
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-l2tp@diameter.org
Precedence: bulk

Hi 

  There can be lot of errors while decoding the Control 
Packet Header. In that case Should the reliable logic 
consider the Ns and Nr fields of the Control Packet.

The errors can be

1. Packet Length indicated by the Length field is not
matching the bytes received.
2. Version Number is not supported by the Implementation.
In this case the Ns and Nr fields shouldn't be considered
by the Reliable Logic.
3. Length and/or Sequence Bits not Set.
4. Offset and/or Parity Bits set.
5. Any unknown Reserved Bit set. The Ns and Nr fields should
be considered by the Reliable Logic.

Can some body explain whether Iam correct in cases 2 and 5.
Also what's need to be done by the reliable logic for other cases.


Best Regards
Sridhar


