From owner-l2tp@ipsec.org  Tue Feb  1 14:08:53 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29227
	for <l2tpext-archive@odin.ietf.org>; Tue, 1 Feb 2000 14:08:51 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]]) by www.sailpix.com (8.8.8/8.6.9) id JAA13048; Tue, 1 Feb 2000 09:44:41 -0800 (PST)
Received: from showboat.teradyne.com (showboat.teradyne.com [198.51.251.10]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id JAA13044 for <l2tp@ipsec.org>; Tue, 1 Feb 2000 09:44:17 -0800 (PST)
Received: from chorus.teradyne.com (chorus.teradyne.com [131.101.1.195])
	by showboat.teradyne.com (8.8.8+Sun/8.8.8) with ESMTP id MAA25515
	for <l2tp@ipsec.org>; Tue, 1 Feb 2000 12:44:01 -0500 (EST)
Received: from notes.teradyne.com (jaypeak.corp.teradyne.com [131.101.17.23]) by chorus.teradyne.com (8.8.8+Sun/8.7.1) with SMTP id MAA07401 for <l2tp@ipsec.org>; Tue, 1 Feb 2000 12:44:08 -0500 (EST)
Received: by notes.teradyne.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 85256878.0061DD2A ; Tue, 1 Feb 2000 12:48:56 -0500
X-Lotus-FromDomain: TERADYNE
From: "David Wong" <David_Wong@notes.teradyne.com>
To: l2tp@ipsec.org
Message-ID: <85256878.0061DB5D.00@notes.teradyne.com>
Date: Tue, 1 Feb 2000 12:43:52 -0500
Subject: Protocol Analyzers and IPSec
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-l2tp@sailpix.com
Precedence: bulk

Along those same lines, are there any network protocol analyzers that can decode
IPSec packets if you give the correct keys (and use manual keying with IPSec)?

Ethereal looked like it was supposed to, but I don't see a way to give it manual
keys to decode with...






Motonori Shindo <mshindo@ascend.co.jp> on 01/31/2000 05:43:38 PM

To:   jeff@assuredaccess.com
cc:   l2tp@ipsec.org (bcc: David Wong/Bos/Teradyne)

Subject:  Re: tcpdump and l2tp?




Jeff,

From: Jeff Enderwick <jeff@assuredaccess.com>
Subject: tcpdump and l2tp?
Date: Mon, 31 Jan 2000 09:40:23 -0800

> Yo,
>
> Has anyone written a tcpdump packet dumper for L2TP?
> Are there any freeware sniffers that run on Linux or BSD?

I did. I placed it at

   ftp://ftp.mbuf.org/pub/l2tp/tcpdump-l2tp.patch

This URL is tentative. Once I place it to more permanent place, I will
announce it to this mailing list again. So please stay tuned:-)

Hope this helps.

> Thanks,
>
> jeff@assuredaccess.com

=====================================================
Motonori Shindo
   Systems Engineer
   Ascend Communications Japan K.K.
   A wholly owned subsidiary of Lucent Technologies.
   email: mshindo@ascend.co.jp or mshindo@lucent.com
   TEL: +81-3-5325-7306
=====================================================






From owner-l2tp@ipsec.org  Wed Feb  2 16:48:03 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22284
	for <l2tpext-archive@odin.ietf.org>; Wed, 2 Feb 2000 16:48:01 -0500 (EST)
Received: (from majordomo@localhost) by www.sailpix.com (8.8.8/8.6.9) id MAA16048; Wed, 2 Feb 2000 12:29:57 -0800 (PST)
Received: from sj-mailhub-3.cisco.com (sj-mailhub-3.cisco.com [171.68.224.215]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id MAA16044 for <l2tp@ipsec.org>; Wed, 2 Feb 2000 12:29:45 -0800 (PST)
Received: from townsley-ultra.cisco.com (townsley-ultra.cisco.com [161.44.49.31])
	by sj-mailhub-3.cisco.com (8.9.1a/8.9.1) with ESMTP id MAA08953
	for <l2tp@ipsec.org>; Wed, 2 Feb 2000 12:48:01 -0800 (PST)
Received: from cisco.com (rtp-pv49-dhcp-135.cisco.com [161.44.49.135]) by townsley-ultra.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) with ESMTP id PAA18625 for <l2tp@ipsec.org>; Wed, 2 Feb 2000 15:28:04 -0500 (EST)
Message-ID: <3898934E.D81A8DD9@cisco.com>
Date: Wed, 02 Feb 2000 15:27:58 -0500
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@ipsec.org
Subject: Call for L2TPEXT Agenda Items for the 47th IETF in Adelaide, Australia
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@sailpix.com
Precedence: bulk
Content-Transfer-Encoding: 7bit


The L2TP WG is planning on meeting in Australia, 
time has not yet been set.

Please send me requests to make presentations.  
Be sure to include all of the below:

1) Name of presenter, including e-mail address
2) Title of presentation
3) Internet draft name, if applicable
4) Amount of time requested

Thanks,

W. Mark Townsley <townsley@cisco.com>


From owner-l2tp@ipsec.org  Wed Feb  2 19:31:06 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA24132
	for <l2tpext-archive@odin.ietf.org>; Wed, 2 Feb 2000 19:31:05 -0500 (EST)
Received: (from majordomo@localhost) by www.sailpix.com (8.8.8/8.6.9) id PAA16349; Wed, 2 Feb 2000 15:23:18 -0800 (PST)
Received: from mail1.cisco.com (mail1.cisco.com [171.68.225.60]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id PAA16345 for <l2tp@ipsec.org>; Wed, 2 Feb 2000 15:22:47 -0800 (PST)
Received: from GEDAVISVPN3 (rsp7000-netlab-y2k.cisco.com [171.70.152.76]) by mail1.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with SMTP id PAA03658; Wed, 2 Feb 2000 15:22:13 -0800 (PST)
From: "gedavis" <gedavis@cisco.com>
To: "David Wong" <David_Wong@notes.teradyne.com>
Cc: <l2tp@ipsec.org>
Subject: RE: L2TP over IPSec
Date: Wed, 2 Feb 2000 15:21:46 -0800
Message-ID: <NBEILNFKKPPCGDCAMJCLKEJGCFAA.gedavis@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
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: <85256877.005A6698.00@notes.teradyne.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Importance: Normal
Disposition-Notification-To: "gedavis" <gedavis@cisco.com>
Sender: owner-l2tp@sailpix.com
Precedence: bulk
Content-Transfer-Encoding: 7bit

now did you load win2000 as  a domain controller (active directory loaded)
or as a stand alone server. Win2k Server and the Certificate services run
cleaner together when set up as domain controller. A large portion of the
policies that you want to enable are under the active directory snap-in, and
under the certificate server snapin, once active directory is loaded. And it
also looks as thought pre-shared keys are your only option? Is your linux
box able to request a certificate online? Or can you import a certificate
into the OS? There are steps also needed to perform that designate what kind
of certificates you will be able to serve, and I believe that they all are
dependent on the CA being a EEEEEnterprise Root CA, which is what it becomes
if you install it on a Domain Controller

Gerald

-----Original Message-----
From: owner-l2tp@sailpix.com [mailto:owner-l2tp@sailpix.com]On Behalf Of
David Wong
Sent: Monday, January 31, 2000 8:23 AM
To: gedavis
Cc: l2tp@ipsec.org
Subject: RE: L2TP over IPSec


The client is a Linux workstation, which currently reads in the
authentication
and encryption key values from a text file. So, right now it only supports
manual keying... I guess what I'm also confused about is while installing
the
Certificate Authority service, I'm asked to enter in the name/address of the
root authority to request a certificate from (even though I've said that the
machine itself will be the root authority).





"gedavis" <gedavis@cisco.com> on 01/30/2000 10:11:11 PM

To:   David Wong/Bos/Teradyne@Teradyne, l2tp@ipsec.org
cc:   gedavis@cisco.com

Subject:  RE: L2TP over IPSec




David,
I have been working some with the MC-CA and what manner of client are you
referring to? router? pc? maybe I can help

Gerald


-----Original Message-----
From: owner-l2tp@sailpix.com [mailto:owner-l2tp@sailpix.com]On Behalf Of
David Wong
Sent: Friday, January 28, 2000 2:56 PM
To: l2tp@ipsec.org
Subject: L2TP over IPSec


I was curious what types of access routers/configurations people have been
successful with configuring/testing L2TP over IPSec.

Also, has anyone used a Cisco1600 series (1605) or a Win2000 Server as the
LNS
while running L2TP over IPSec? The 1605 with the 12.05(T), 56-bit encryption
image does not seem to like an encrypted ICMP Echo Request I send to it in
transport mode (something about bad pad length). I know the Free S/WAN
implementation of IPSec will actually reply back to an encrypted Echo
Request
that I send it.

In terms of using Windows 2000, I've tried installing the Certificate
Authority
service on the machine, without luck, and even if I were to, it's not clear
to
me how to use a certificate if the client I'm using needs the authentication
and
encryption key information in text form.












From owner-l2tp@ipsec.org  Thu Feb  3 08:09:50 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA16443
	for <l2tpext-archive@odin.ietf.org>; Thu, 3 Feb 2000 08:09:49 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]]) by www.sailpix.com (8.8.8/8.6.9) id DAA18207; Thu, 3 Feb 2000 03:40:28 -0800 (PST)
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id DAA18200 for <l2tp@ipsec.org>; Thu, 3 Feb 2000 03:39:59 -0800 (PST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA13264;
	Thu, 3 Feb 2000 06:39:57 -0500 (EST)
Message-Id: <200002031139.GAA13264@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-l2tphc-00.txt
Date: Thu, 03 Feb 2000 06:39:56 -0500
Sender: owner-l2tp@sailpix.com
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		: L2TP Header Compression ('L2TPHC')
	Author(s)	: A. Valencia
	Filename	: draft-ietf-l2tpext-l2tphc-00.txt
	Pages		: 7
	Date		: 02-Feb-00
	
The Layer 2 Tunneling Protocol ('L2TP') [RFC2661] defines a
mechanism for tunneling PPP sessions over arbitrary media.  There
exists a class of specific media and applications for which protocol
overhead may be optimized, and where such reduction results in
improved operation.  This document describes the solution space
addressed, its underlying motivations, and the protocol modifications
required.  The enhancement to the L2TP protocol is called L2TP Header
Compression, or 'L2TPHC'.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-l2tpext-l2tphc-00.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-l2tphc-00.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-l2tphc-00.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:	<20000202101418.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-l2tpext-l2tphc-00.txt

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

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

--OtherAccess--

--NextPart--




From owner-l2tp@ipsec.org  Thu Feb  3 13:21:17 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25940
	for <l2tpext-archive@odin.ietf.org>; Thu, 3 Feb 2000 13:21:16 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]]) by www.sailpix.com (8.8.8/8.6.9) id IAA18554; Thu, 3 Feb 2000 08:49:59 -0800 (PST)
Received: from showboat.teradyne.com (showboat.teradyne.com [198.51.251.10]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id IAA18548 for <l2tp@ipsec.org>; Thu, 3 Feb 2000 08:49:17 -0800 (PST)
Received: from chorus.teradyne.com (chorus.teradyne.com [131.101.1.195])
	by showboat.teradyne.com (8.8.8+Sun/8.8.8) with ESMTP id LAA04534;
	Thu, 3 Feb 2000 11:48:49 -0500 (EST)
Received: from notes.teradyne.com (jaypeak.corp.teradyne.com [131.101.17.23]) by chorus.teradyne.com (8.8.8+Sun/8.7.1) with SMTP id LAA27629; Thu, 3 Feb 2000 11:48:57 -0500 (EST)
Received: by notes.teradyne.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 8525687A.005CD179 ; Thu, 3 Feb 2000 11:53:49 -0500
X-Lotus-FromDomain: TERADYNE
From: "David Wong" <David_Wong@notes.teradyne.com>
To: "gedavis" <gedavis@cisco.com>
cc: l2tp@ipsec.org
Message-ID: <8525687A.005CCF17.00@notes.teradyne.com>
Date: Thu, 3 Feb 2000 11:48:29 -0500
Subject: RE: L2TP over IPSec
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-l2tp@sailpix.com
Precedence: bulk

Actually, I tried both methods. One with the CA being the Enterprise Root CA,
and the other as the Standalone. So, during setup, for either configuration,
what do you do when setup asks for you to enter in the name of the CA to request
the certificate from or else to save the request?

Yes, preshared keys are the only option at this point.
No, the software running on the Linux box can't request a certificate or import
one.
If that's the case, then maybe this won't work? Also, how exactly do
certificates fit in with keys and SAs? Do the certificates themselves contain
the keys? but in some encoded format?






"gedavis" <gedavis@cisco.com> on 02/02/2000 06:21:46 PM

To:   David Wong/Bos/Teradyne@Teradyne
cc:   l2tp@ipsec.org

Subject:  RE: L2TP over IPSec




now did you load win2000 as  a domain controller (active directory loaded)
or as a stand alone server. Win2k Server and the Certificate services run
cleaner together when set up as domain controller. A large portion of the
policies that you want to enable are under the active directory snap-in, and
under the certificate server snapin, once active directory is loaded. And it
also looks as thought pre-shared keys are your only option? Is your linux
box able to request a certificate online? Or can you import a certificate
into the OS? There are steps also needed to perform that designate what kind
of certificates you will be able to serve, and I believe that they all are
dependent on the CA being a EEEEEnterprise Root CA, which is what it becomes
if you install it on a Domain Controller

Gerald

-----Original Message-----
From: owner-l2tp@sailpix.com [mailto:owner-l2tp@sailpix.com]On Behalf Of
David Wong
Sent: Monday, January 31, 2000 8:23 AM
To: gedavis
Cc: l2tp@ipsec.org
Subject: RE: L2TP over IPSec


The client is a Linux workstation, which currently reads in the
authentication
and encryption key values from a text file. So, right now it only supports
manual keying... I guess what I'm also confused about is while installing
the
Certificate Authority service, I'm asked to enter in the name/address of the
root authority to request a certificate from (even though I've said that the
machine itself will be the root authority).





"gedavis" <gedavis@cisco.com> on 01/30/2000 10:11:11 PM

To:   David Wong/Bos/Teradyne@Teradyne, l2tp@ipsec.org
cc:   gedavis@cisco.com

Subject:  RE: L2TP over IPSec




David,
I have been working some with the MC-CA and what manner of client are you
referring to? router? pc? maybe I can help

Gerald


-----Original Message-----
From: owner-l2tp@sailpix.com [mailto:owner-l2tp@sailpix.com]On Behalf Of
David Wong
Sent: Friday, January 28, 2000 2:56 PM
To: l2tp@ipsec.org
Subject: L2TP over IPSec


I was curious what types of access routers/configurations people have been
successful with configuring/testing L2TP over IPSec.

Also, has anyone used a Cisco1600 series (1605) or a Win2000 Server as the
LNS
while running L2TP over IPSec? The 1605 with the 12.05(T), 56-bit encryption
image does not seem to like an encrypted ICMP Echo Request I send to it in
transport mode (something about bad pad length). I know the Free S/WAN
implementation of IPSec will actually reply back to an encrypted Echo
Request
that I send it.

In terms of using Windows 2000, I've tried installing the Certificate
Authority
service on the machine, without luck, and even if I were to, it's not clear
to
me how to use a certificate if the client I'm using needs the authentication
and
encryption key information in text form.
















From owner-l2tp@ipsec.org  Thu Feb  3 14:34:16 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA27985
	for <l2tpext-archive@odin.ietf.org>; Thu, 3 Feb 2000 14:34:15 -0500 (EST)
Received: (from majordomo@localhost) by www.sailpix.com (8.8.8/8.6.9) id JAA18601; Thu, 3 Feb 2000 09:12:51 -0800 (PST)
Received: from showboat.teradyne.com (showboat.teradyne.com [198.51.251.10]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id JAA18597 for <l2tp@ipsec.org>; Thu, 3 Feb 2000 09:12:41 -0800 (PST)
Received: from chorus.teradyne.com (chorus.teradyne.com [131.101.1.195])
	by showboat.teradyne.com (8.8.8+Sun/8.8.8) with ESMTP id MAA14002
	for <l2tp@ipsec.org>; Thu, 3 Feb 2000 12:12:25 -0500 (EST)
Received: from notes.teradyne.com (jaypeak.corp.teradyne.com [131.101.17.23]) by chorus.teradyne.com (8.8.8+Sun/8.7.1) with SMTP id MAA03589 for <l2tp@ipsec.org>; Thu, 3 Feb 2000 12:12:33 -0500 (EST)
Received: by notes.teradyne.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id 8525687A.005F0198 ; Thu, 3 Feb 2000 12:17:43 -0500
X-Lotus-FromDomain: TERADYNE
From: "David Wong" <David_Wong@notes.teradyne.com>
To: l2tp@ipsec.org
Message-ID: <8525687A.005F002E.00@notes.teradyne.com>
Date: Thu, 3 Feb 2000 12:12:26 -0500
Subject: l2tpd and Linux FreeS/WAN
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-l2tp@sailpix.com
Precedence: bulk

Has anyone setup L2TP over IPSec using l2tpd and FreeS/WAN?




From owner-l2tp@ipsec.org  Tue Feb  8 10:15:11 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26217
	for <l2tpext-archive@odin.ietf.org>; Tue, 8 Feb 2000 10:15:10 -0500 (EST)
Received: (from majordomo@localhost) by www.sailpix.com (8.8.8/8.6.9) id FAA00987; Tue, 8 Feb 2000 05:55:18 -0800 (PST)
Received: from fsnt.future.futusoft.com ([203.197.140.35]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id FAA00983 for <l2tp@ipsec.org>; Tue, 8 Feb 2000 05:55:03 -0800 (PST)
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futusoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0000158266@fsnt.future.futusoft.com> for <l2tp@ipsec.org>;
 Tue, 08 Feb 2000 19:32:59 +0530
Received: from aruljp.future.futsoft.com (aruljp.future.futsoft.com [10.0.12.18]) by kailash.future.futsoft.com (8.7.1/8.7.1) with SMTP id TAA26134 for <l2tp@ipsec.org>; Tue, 8 Feb 2000 19:15:11 +0530
Received: by localhost with Microsoft MAPI; Tue, 8 Feb 2000 19:27:20 +0530
Message-Id: <01BF726A.844864E0.aruljp@future.futsoft.com>
From: "aruljp@future.futsoft.com" <aruljp@future.futsoft.com>
Reply-To: "aruljp@future.futsoft.com" <aruljp@future.futsoft.com>
To: "l2tp@ipsec.org" <l2tp@ipsec.org>
Subject: L2TP security
Date: Tue, 8 Feb 2000 19:27:19 +0530
Organization: Future Software
X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211
Sender: owner-l2tp@sailpix.com
Precedence: bulk

Hi,

   Please clear this doubt. If L2TP runs over UDP IPsec can be used for 
security, but if the L2TP media is ATM then is there any security protocol.
Does this mean it is better to have L2TP over UDP/IP media.

Thanks in advance.

Regards,
Arul.
 



From owner-l2tp@ipsec.org  Tue Feb  8 13:16:17 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05842
	for <l2tpext-archive@odin.ietf.org>; Tue, 8 Feb 2000 13:16:16 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]]) by www.sailpix.com (8.8.8/8.6.9) id IAA01209; Tue, 8 Feb 2000 08:57:03 -0800 (PST)
Received: from wacko.redbacknetworks.com (wacko.redbacknetworks.com [155.53.130.200]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id IAA01205 for <l2tp@ipsec.org>; Tue, 8 Feb 2000 08:56:49 -0800 (PST)
Received: from tradrat.redbacknetworks.com (tradrat.redbacknetworks.com [155.53.190.107])
	by wacko.redbacknetworks.com (8.9.3/8.9.3) with ESMTP id IAA10267;
	Tue, 8 Feb 2000 08:55:06 -0800 (PST)
Received: (from tor@localhost) by tradrat.redbacknetworks.com (8.8.8/8.6.9) id IAA24376; Tue, 8 Feb 2000 08:55:06 -0800 (PST)
Date: Tue, 8 Feb 2000 08:55:06 -0800
From: Rene Tio <tor@redback.com>
To: "aruljp@future.futsoft.com" <aruljp@future.futsoft.com>
Cc: "l2tp@ipsec.org" <l2tp@ipsec.org>
Subject: Re: L2TP security
Message-ID: <20000208085505.A24280@redback.com>
References: <01BF726A.844864E0.aruljp@future.futsoft.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
In-Reply-To: <01BF726A.844864E0.aruljp@future.futsoft.com>; from aruljp@future.futsoft.com on Tue, Feb 08, 2000 at 07:27:19PM +0530
Sender: owner-l2tp@sailpix.com
Precedence: bulk

Frame Relay privacy and ATM security are, to my knowledge, still works in
progress.  That does not mean there are no implementations though.  If you
need security, go with whatever works in your network, whether IPsec or ATM
or FR privacy, since L2TP is largely ignorant of the lower layer.

If you run L2TP over running shoes, as the WG chairs once claimed you could,
be sure to arm the person wearing them and chain the packet to his wrist.

Cheers,
Rene


On Tue, Feb 08, 2000 at 07:27:19PM +0530, aruljp@future.futsoft.com wrote:
> Hi,
> 
>    Please clear this doubt. If L2TP runs over UDP IPsec can be used for 
> security, but if the L2TP media is ATM then is there any security protocol.
> Does this mean it is better to have L2TP over UDP/IP media.
> 
> Thanks in advance.
> 
> Regards,
> Arul.
>  
> 


From owner-l2tp@ipsec.org  Tue Feb  8 18:28:20 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13437
	for <l2tpext-archive@odin.ietf.org>; Tue, 8 Feb 2000 18:28:19 -0500 (EST)
Received: (from majordomo@localhost) by www.sailpix.com (8.8.8/8.6.9) id OAA01761; Tue, 8 Feb 2000 14:41:43 -0800 (PST)
Received: from sj-mailhub-2.cisco.com (sj-mailhub-2.cisco.com [171.69.43.88]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id OAA01756 for <l2tp@ipsec.org>; Tue, 8 Feb 2000 14:41:29 -0800 (PST)
Received: from townsley-ultra.cisco.com (townsley-ultra.cisco.com [161.44.49.31])
	by sj-mailhub-2.cisco.com (8.9.1a/8.9.1) with ESMTP id OAA07204;
	Tue, 8 Feb 2000 14:43:53 -0800 (PST)
Received: from cisco.com (townsley-home-1.cisco.com [161.44.99.51]) by townsley-ultra.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) with ESMTP id RAA22113; Tue, 8 Feb 2000 17:39:43 -0500 (EST)
Message-ID: <38A09B1D.4E3AC27B@cisco.com>
Date: Tue, 08 Feb 2000 17:39:25 -0500
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: Srinivasan Chakravarthy <cs@cosinecom.com>
CC: "aruljp@future.futsoft.com" <aruljp@future.futsoft.com>,
        "l2tp@ipsec.org" <l2tp@ipsec.org>
Subject: Re: L2TP security
References: <01BF726A.844864E0.aruljp@future.futsoft.com> <38A09525.9E7A8FFC@cosinecom.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@sailpix.com
Precedence: bulk
Content-Transfer-Encoding: 7bit


1. ECP does not protect the L2TP headers.
2. ECP waves its hands at this tiny thing known as Key Distribution.

Srinivasan Chakravarthy wrote:
> 
> I have a question for you. If PPP supports ECP to encrypt the data, why do you
> need some other protocol to encrypt the data when L2TP is run over ATM or any
> other medium than UDP/IP ?
> 
> aruljp@future.futsoft.com wrote:
> 
> > Hi,
> >
> >    Please clear this doubt. If L2TP runs over UDP IPsec can be used for
> > security, but if the L2TP media is ATM then is there any security protocol.
> > Does this mean it is better to have L2TP over UDP/IP media.
> >
> > Thanks in advance.
> >
> > Regards,
> > Arul.
> >


From owner-l2tp@ipsec.org  Tue Feb  8 18:28:21 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13448
	for <l2tpext-archive@odin.ietf.org>; Tue, 8 Feb 2000 18:28:21 -0500 (EST)
Received: (from majordomo@localhost) by www.sailpix.com (8.8.8/8.6.9) id OAA01707; Tue, 8 Feb 2000 14:14:52 -0800 (PST)
Received: from blue.cosinecom.com (proxy4.cosinecom.com [208.248.148.132]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id OAA01703 for <l2tp@ipsec.org>; Tue, 8 Feb 2000 14:14:40 -0800 (PST)
Received: from cosinecom.com by blue.cosinecom.com (8.8.8+Sun/SMI-SVR4)
	id OAA02533; Tue, 8 Feb 2000 14:13:57 -0800 (PST)
Message-ID: <38A09525.9E7A8FFC@cosinecom.com>
Date: Tue, 08 Feb 2000 14:13:57 -0800
From: Srinivasan Chakravarthy <cs@cosinecom.com>
Organization: CoSine Communications Inc.
X-Mailer: Mozilla 4.06 [en] (WinNT; U)
MIME-Version: 1.0
To: "aruljp@future.futsoft.com" <aruljp@future.futsoft.com>
CC: "l2tp@ipsec.org" <l2tp@ipsec.org>
Subject: Re: L2TP security
References: <01BF726A.844864E0.aruljp@future.futsoft.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@sailpix.com
Precedence: bulk
Content-Transfer-Encoding: 7bit

I have a question for you. If PPP supports ECP to encrypt the data, why do you
need some other protocol to encrypt the data when L2TP is run over ATM or any
other medium than UDP/IP ?

aruljp@future.futsoft.com wrote:

> Hi,
>
>    Please clear this doubt. If L2TP runs over UDP IPsec can be used for
> security, but if the L2TP media is ATM then is there any security protocol.
> Does this mean it is better to have L2TP over UDP/IP media.
>
> Thanks in advance.
>
> Regards,
> Arul.
>



From owner-l2tp@ipsec.org  Tue Feb  8 18:34:43 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13552
	for <l2tpext-archive@odin.ietf.org>; Tue, 8 Feb 2000 18:34:43 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]]) by www.sailpix.com (8.8.8/8.6.9) id OAA01747; Tue, 8 Feb 2000 14:37:59 -0800 (PST)
Received: from wacko.redbacknetworks.com (wacko.redbacknetworks.com [155.53.130.200]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id OAA01741 for <l2tp@ipsec.org>; Tue, 8 Feb 2000 14:37:43 -0800 (PST)
Received: from tradrat.redbacknetworks.com (tradrat.redbacknetworks.com [155.53.190.107])
	by wacko.redbacknetworks.com (8.9.3/8.9.3) with ESMTP id OAA19980;
	Tue, 8 Feb 2000 14:37:12 -0800 (PST)
Received: (from tor@localhost) by tradrat.redbacknetworks.com (8.8.8/8.6.9) id OAA26687; Tue, 8 Feb 2000 14:37:12 -0800 (PST)
Date: Tue, 8 Feb 2000 14:37:12 -0800
From: Rene Tio <tor@redback.com>
To: Srinivasan Chakravarthy <cs@cosinecom.com>
Cc: "aruljp@future.futsoft.com" <aruljp@future.futsoft.com>,
        "l2tp@ipsec.org" <l2tp@ipsec.org>
Subject: Re: L2TP security
Message-ID: <20000208143712.D24561@redback.com>
References: <01BF726A.844864E0.aruljp@future.futsoft.com> <38A09525.9E7A8FFC@cosinecom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
In-Reply-To: <38A09525.9E7A8FFC@cosinecom.com>; from cs@cosinecom.com on Tue, Feb 08, 2000 at 02:13:57PM -0800
Sender: owner-l2tp@sailpix.com
Precedence: bulk

Different ways of skinning a cat.  Suppose you want authentication only and
not privacy.  Or possibly hardware constraints (I'm stepping way out of
where I can speak coherently here), where you'd be encrypting/de-encrypting
a single stream (the tunnel) versus thousands of PPP sessions.

Of course we can get into a LONG discussion over why you would want privacy
over the Internet when that box outside your house is so accessible, but
let's not.

Rene


On Tue, Feb 08, 2000 at 02:13:57PM -0800, Srinivasan Chakravarthy wrote:
> I have a question for you. If PPP supports ECP to encrypt the data, why do you
> need some other protocol to encrypt the data when L2TP is run over ATM or any
> other medium than UDP/IP ?
> 
> aruljp@future.futsoft.com wrote:
> 
> > Hi,
> >
> >    Please clear this doubt. If L2TP runs over UDP IPsec can be used for
> > security, but if the L2TP media is ATM then is there any security protocol.
> > Does this mean it is better to have L2TP over UDP/IP media.
> >
> > Thanks in advance.
> >
> > Regards,
> > Arul.
> >
> 


From owner-l2tp@ipsec.org  Wed Feb  9 01:04:38 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA19323
	for <l2tpext-archive@odin.ietf.org>; Wed, 9 Feb 2000 01:04:37 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]]) by www.sailpix.com (8.8.8/8.6.9) id UAA02319; Tue, 8 Feb 2000 20:50:34 -0800 (PST)
Received: from fsnt.future.futusoft.com ([203.197.140.35]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id UAA02315 for <l2tp@ipsec.org>; Tue, 8 Feb 2000 20:50:17 -0800 (PST)
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futusoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0000160234@fsnt.future.futusoft.com> for <l2tp@ipsec.org>;
 Wed, 09 Feb 2000 10:28:04 +0530
Received: from aruljp.future.futsoft.com (aruljp.future.futsoft.com [10.0.12.18]) by kailash.future.futsoft.com (8.7.1/8.7.1) with SMTP id KAA01782 for <l2tp@ipsec.org>; Wed, 9 Feb 2000 10:10:27 +0530
Received: by localhost with Microsoft MAPI; Wed, 9 Feb 2000 10:22:37 +0530
Message-Id: <01BF72E7.9683DFE0.aruljp@future.futsoft.com>
From: "aruljp@future.futsoft.com" <aruljp@future.futsoft.com>
Reply-To: "aruljp@future.futsoft.com" <aruljp@future.futsoft.com>
To: "l2tp@ipsec.org" <l2tp@ipsec.org>
Subject: L2TP over AAL5
Date: Wed, 9 Feb 2000 10:22:36 +0530
Organization: Future Software
X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211
Sender: owner-l2tp@sailpix.com
Precedence: bulk

Hi ,

    What is the NLPID for L2TP that can be used in AAL5 header. L2TP over AAL5 draft does not
specify this. 

Thanks in advance.

Regards,
Arul.



From owner-l2tp@ipsec.org  Wed Feb  9 02:43:27 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA02080
	for <l2tpext-archive@odin.ietf.org>; Wed, 9 Feb 2000 02:43:27 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]]) by www.sailpix.com (8.8.8/8.6.9) id WAA02519; Tue, 8 Feb 2000 22:48:45 -0800 (PST)
Received: from wacko.redbacknetworks.com (wacko.redbacknetworks.com [155.53.130.200]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id WAA02515 for <l2tp@ipsec.org>; Tue, 8 Feb 2000 22:48:33 -0800 (PST)
Received: from tradrat.redbacknetworks.com (tradrat.redbacknetworks.com [155.53.190.107])
	by wacko.redbacknetworks.com (8.9.3/8.9.3) with ESMTP id WAA26399;
	Tue, 8 Feb 2000 22:48:02 -0800 (PST)
Received: (from tor@localhost) by tradrat.redbacknetworks.com (8.8.8/8.6.9) id WAA27958; Tue, 8 Feb 2000 22:48:02 -0800 (PST)
Date: Tue, 8 Feb 2000 22:48:02 -0800
From: Rene Tio <tor@redback.com>
To: "aruljp@future.futsoft.com" <aruljp@future.futsoft.com>
Cc: "l2tp@ipsec.org" <l2tp@ipsec.org>
Subject: Re: L2TP over AAL5
Message-ID: <20000208224802.C27785@redback.com>
References: <01BF72E7.9683DFE0.aruljp@future.futsoft.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
In-Reply-To: <01BF72E7.9683DFE0.aruljp@future.futsoft.com>; from aruljp@future.futsoft.com on Wed, Feb 09, 2000 at 10:22:36AM +0530
Sender: owner-l2tp@sailpix.com
Precedence: bulk

Firstly, my apologies for not uploading the L2TP over FR draft.  My "other"
job (which happens to be my real job) is impinging on my old job.

Secondly, L2TP over ATM uses the LLC-SNAP format, thus there is no NLPID
required.  The NLPID for Frame Relay is 0x80, which indicates a SNAP header
follows.

Rene


On Wed, Feb 09, 2000 at 10:22:36AM +0530, aruljp@future.futsoft.com wrote:
> Hi ,
> 
>     What is the NLPID for L2TP that can be used in AAL5 header. L2TP over AAL5 draft does not
> specify this. 
> 
> Thanks in advance.
> 
> Regards,
> Arul.
> 


From owner-l2tp@ipsec.org  Wed Feb  9 15:17:19 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21380
	for <l2tpext-archive@odin.ietf.org>; Wed, 9 Feb 2000 15:17:11 -0500 (EST)
Received: (from majordomo@localhost) by www.sailpix.com (8.8.8/8.6.9) id KAA04410; Wed, 9 Feb 2000 10:47:52 -0800 (PST)
Received: from ftpbox.mot.com (ftpbox.mot.com [129.188.136.101]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id KAA04406 for <l2tp@ipsec.org>; Wed, 9 Feb 2000 10:47:31 -0800 (PST)
Received: [from pobox2.mot.com (pobox2.mot.com [136.182.15.8]) by ftpbox.mot.com (VWALL-IN-ftpbox 2.0) with ESMTP id LAA08268 for <l2tp@ipsec.org>; Wed, 9 Feb 2000 11:47:29 -0700 (MST)]
Received: [from ilms06.cig.mot.com (ilms06.cig.mot.com [136.182.15.18]) by pobox2.mot.com (MOT-pobox2 2.0) with ESMTP id LAA18114 for <l2tp@ipsec.org>; Wed, 9 Feb 2000 11:47:28 -0700 (MST)]
Received: from email.mot.com ([160.44.110.59]) by ilms06.cig.mot.com
          (Netscape Messaging Server 3.01)  with ESMTP id AAA6058;
          Wed, 9 Feb 2000 12:47:22 -0600
Message-ID: <38A1ACDA.BC273136@email.mot.com>
Date: Wed, 09 Feb 2000 12:07:22 -0600
From: "Ajoy Singh" <ASINGH1@email.mot.com>
Organization: Motorola
X-Mailer: Mozilla 4.07 [en] (WinNT; I)
MIME-Version: 1.0
To: Rene Tio <tor@redback.com>
CC: "aruljp@future.futsoft.com" <aruljp@future.futsoft.com>,
        "l2tp@ipsec.org" <l2tp@ipsec.org>
Subject: Re: L2TP over AAL5
References: <01BF72E7.9683DFE0.aruljp@future.futsoft.com> <20000208224802.C27785@redback.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@sailpix.com
Precedence: bulk
Content-Transfer-Encoding: 7bit

We still need to get PID for L2TP over AAL5.  I think we should ask IANA to give PID for L2TP. I am
not aware of how this works. Any suggestions !
regards,
ajoy


Rene Tio wrote:

> Firstly, my apologies for not uploading the L2TP over FR draft.  My "other"
> job (which happens to be my real job) is impinging on my old job.
>
> Secondly, L2TP over ATM uses the LLC-SNAP format, thus there is no NLPID
> required.  The NLPID for Frame Relay is 0x80, which indicates a SNAP header
> follows.
>
> Rene
>
> On Wed, Feb 09, 2000 at 10:22:36AM +0530, aruljp@future.futsoft.com wrote:
> > Hi ,
> >
> >     What is the NLPID for L2TP that can be used in AAL5 header. L2TP over AAL5 draft does not
> > specify this.
> >
> > Thanks in advance.
> >
> > Regards,
> > Arul.
> >



From owner-l2tp@ipsec.org  Wed Feb  9 15:39:13 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22670
	for <l2tpext-archive@odin.ietf.org>; Wed, 9 Feb 2000 15:39:10 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]]) by www.sailpix.com (8.8.8/8.6.9) id LAA04482; Wed, 9 Feb 2000 11:26:22 -0800 (PST)
Received: from wacko.redbacknetworks.com (wacko.redbacknetworks.com [155.53.130.200]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id LAA04478 for <l2tp@ipsec.org>; Wed, 9 Feb 2000 11:26:05 -0800 (PST)
Received: from tradrat.redbacknetworks.com (tradrat.redbacknetworks.com [155.53.190.107])
	by wacko.redbacknetworks.com (8.9.3/8.9.3) with ESMTP id LAA09725;
	Wed, 9 Feb 2000 11:25:34 -0800 (PST)
Received: (from tor@localhost) by tradrat.redbacknetworks.com (8.8.8/8.6.9) id LAA08274; Wed, 9 Feb 2000 11:25:34 -0800 (PST)
Date: Wed, 9 Feb 2000 11:25:34 -0800
From: Rene Tio <tor@redback.com>
To: Ajoy Singh <ASINGH1@email.mot.com>
Cc: "aruljp@future.futsoft.com" <aruljp@future.futsoft.com>,
        "l2tp@ipsec.org" <l2tp@ipsec.org>
Subject: Re: L2TP over AAL5
Message-ID: <20000209112534.B8214@redback.com>
References: <01BF72E7.9683DFE0.aruljp@future.futsoft.com> <20000208224802.C27785@redback.com> <38A1ACDA.BC273136@email.mot.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0i
In-Reply-To: <38A1ACDA.BC273136@email.mot.com>; from ASINGH1@email.mot.com on Wed, Feb 09, 2000 at 12:07:22PM -0600
Sender: owner-l2tp@sailpix.com
Precedence: bulk

When we went to IANA for L2TP over FR, we got 0x0007 for L2TP.  Thus for
both Frame Relay and ATM, the OUI is IANA's OUI (00-00-5E) and the PID is
0x0007.

Rene

On Wed, Feb 09, 2000 at 12:07:22PM -0600, Ajoy Singh wrote:
> We still need to get PID for L2TP over AAL5.  I think we should ask IANA to give PID for L2TP. I am
> not aware of how this works. Any suggestions !
> regards,
> ajoy
> 
> 
> Rene Tio wrote:
> 
> > Firstly, my apologies for not uploading the L2TP over FR draft.  My "other"
> > job (which happens to be my real job) is impinging on my old job.
> >
> > Secondly, L2TP over ATM uses the LLC-SNAP format, thus there is no NLPID
> > required.  The NLPID for Frame Relay is 0x80, which indicates a SNAP header
> > follows.
> >
> > Rene
> >
> > On Wed, Feb 09, 2000 at 10:22:36AM +0530, aruljp@future.futsoft.com wrote:
> > > Hi ,
> > >
> > >     What is the NLPID for L2TP that can be used in AAL5 header. L2TP over AAL5 draft does not
> > > specify this.
> > >
> > > Thanks in advance.
> > >
> > > Regards,
> > > Arul.
> > >
> 


From owner-l2tp@ipsec.org  Thu Feb 10 12:22:42 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04764
	for <l2tpext-archive@odin.ietf.org>; Thu, 10 Feb 2000 12:22:41 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]]) by www.sailpix.com (8.8.8/8.6.9) id HAA07016; Thu, 10 Feb 2000 07:57:09 -0800 (PST)
Received: from monitor.internaut.com (mg-206253202-37.ricochet.net [206.253.202.37]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id HAA07012 for <l2tp@ipsec.org>; Thu, 10 Feb 2000 07:56:50 -0800 (PST)
Received: from vaiobean ([204.57.137.66])
	by monitor.internaut.com (8.9.2/8.8.8) with SMTP id HAA19124;
	Thu, 10 Feb 2000 07:44:24 -0800 (PST)
Reply-To: <aboba@internaut.com>
From: "Bernard Aboba" <aboba@internaut.com>
To: "'David Wong'" <David_Wong@notes.teradyne.com>,
        "'gedavis'" <gedavis@cisco.com>
Cc: <l2tp@ipsec.org>
Subject: RE: L2TP over IPSec
Date: Thu, 10 Feb 2000 07:50:46 -0800
Message-ID: <03bd01bf73de$9abc0310$2d8939cc@ntdev.microsoft.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
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)
In-Reply-To: <85256877.005A6698.00@notes.teradyne.com>
X-Mimeole: Produced By Microsoft MimeOLE V5.00.2919.6700
Importance: Normal
Sender: owner-l2tp@sailpix.com
Precedence: bulk
Content-Transfer-Encoding: 7bit

It sounds like the OS you are using does not support IKE. You might
check to see if there is an IKE daemon running. If not, then you
cannot do certificate auth (or dynamic keying with pre-shared keys
for that matter), only manually keyed SAs.

-----Original Message-----
From: owner-l2tp@sailpix.com [mailto:owner-l2tp@sailpix.com]On Behalf Of
David Wong
Sent: Monday, January 31, 2000 8:23 AM
To: gedavis
Cc: l2tp@ipsec.org
Subject: RE: L2TP over IPSec


The client is a Linux workstation, which currently reads in the
authentication
and encryption key values from a text file. So, right now it only supports
manual keying... I guess what I'm also confused about is while installing
the
Certificate Authority service, I'm asked to enter in the name/address of the
root authority to request a certificate from (even though I've said that the
machine itself will be the root authority).
Gerald

me how to use a certificate if the client I'm using needs the authentication
and encryption key information in text form.











From owner-l2tp@ipsec.org  Thu Feb 10 12:24:04 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04844
	for <l2tpext-archive@odin.ietf.org>; Thu, 10 Feb 2000 12:24:03 -0500 (EST)
Received: (from majordomo@localhost) by www.sailpix.com (8.8.8/8.6.9) id HAA06989; Thu, 10 Feb 2000 07:47:50 -0800 (PST)
Received: from monitor.internaut.com (mg-206253202-37.ricochet.net [206.253.202.37]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id HAA06985 for <l2tp@ipsec.org>; Thu, 10 Feb 2000 07:47:28 -0800 (PST)
Received: from vaiobean ([204.57.137.66])
	by monitor.internaut.com (8.9.2/8.8.8) with SMTP id HAA19117;
	Thu, 10 Feb 2000 07:38:39 -0800 (PST)
Reply-To: <aboba@internaut.com>
From: "Bernard Aboba" <aboba@internaut.com>
To: "'Srinivasan Chakravarthy'" <cs@cosinecom.com>,
        <aruljp@future.futsoft.com>
Cc: <l2tp@ipsec.org>
Subject: RE: L2TP security
Date: Thu, 10 Feb 2000 07:45:04 -0800
Message-ID: <03bc01bf73dd$cd7ab180$2d8939cc@ntdev.microsoft.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
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)
In-Reply-To: <38A09525.9E7A8FFC@cosinecom.com>
X-Mimeole: Produced By Microsoft MimeOLE V5.00.2919.6700
Importance: Normal
Sender: owner-l2tp@sailpix.com
Precedence: bulk
Content-Transfer-Encoding: 7bit

In addition to the deficiencies that Mark mentioned, most ECP
ciphers offer encryption without integrity protection. This
creates a vulnerability to "bit flipping" attacks. Plus, without
integrity-protecting the PPP LCP and NCP packets, you open
yourself to "negotiation downgrade" attacks.


-----Original Message-----
From: owner-l2tp@sailpix.com [mailto:owner-l2tp@sailpix.com]On Behalf Of
Srinivasan Chakravarthy
Sent: Tuesday, February 08, 2000 2:14 PM
To: aruljp@future.futsoft.com
Cc: l2tp@ipsec.org
Subject: Re: L2TP security


I have a question for you. If PPP supports ECP to encrypt the data, why do
you
need some other protocol to encrypt the data when L2TP is run over ATM or
any
other medium than UDP/IP ?

aruljp@future.futsoft.com wrote:

> Hi,
>
>    Please clear this doubt. If L2TP runs over UDP IPsec can be used for
> security, but if the L2TP media is ATM then is there any security
protocol.
> Does this mean it is better to have L2TP over UDP/IP media.
>
> Thanks in advance.
>
> Regards,
> Arul.
>




From owner-l2tp@ipsec.org  Sat Feb 12 04:02:12 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA19564
	for <l2tpext-archive@odin.ietf.org>; Sat, 12 Feb 2000 04:02:11 -0500 (EST)
Received: (from majordomo@localhost) by www.sailpix.com (8.8.8/8.6.9) id XAA10808; Fri, 11 Feb 2000 23:34:02 -0800 (PST)
Received: from fsnt.future.futusoft.com ([203.197.140.35]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id XAA10804 for <l2tp@ipsec.org>; Fri, 11 Feb 2000 23:33:47 -0800 (PST)
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futusoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0000172852@fsnt.future.futusoft.com> for <l2tp@ipsec.org>;
 Sat, 12 Feb 2000 13:11:03 +0530
Received: from aruljp.future.futsoft.com (aruljp.future.futsoft.com [10.0.12.18]) by kailash.future.futsoft.com (8.7.1/8.7.1) with SMTP id MAA30178 for <l2tp@ipsec.org>; Sat, 12 Feb 2000 12:53:19 +0530
Received: by localhost with Microsoft MAPI; Sat, 12 Feb 2000 13:05:33 +0530
Message-Id: <01BF7559.D86CA080.aruljp@future.futsoft.com>
From: "aruljp@future.futsoft.com" <aruljp@future.futsoft.com>
Reply-To: "aruljp@future.futsoft.com" <aruljp@future.futsoft.com>
To: "l2tp@ipsec.org" <l2tp@ipsec.org>
Subject: L2TP with FR access network
Date: Sat, 12 Feb 2000 13:05:32 +0530
Importance: high
X-Priority: 1 (Highest)
Organization: Future Software
X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211
Sender: owner-l2tp@sailpix.com
Precedence: bulk

Hi,
   
  Is there any draft for L2TP with FR access network.

Thanks in advance.

Regards,
Arul.





From owner-l2tp@ipsec.org  Tue Feb 15 15:08:32 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20845
	for <l2tpext-archive@odin.ietf.org>; Tue, 15 Feb 2000 15:08:30 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]]) by www.sailpix.com (8.8.8/8.6.9) id KAA28857; Tue, 15 Feb 2000 10:40:04 -0800 (PST)
Received: from spmler1.mail.eds.com (ns3.eds.com [194.128.225.190]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id KAA28850 for <l2tp@ipsec.org>; Tue, 15 Feb 2000 10:39:50 -0800 (PST)
Received: from nnse.eds.com (nnse.eds.com [205.191.69.78])
	by spmler1.mail.eds.com (8.9.3/8.9.3) with ESMTP id SAA00567
	for <l2tp@ipsec.org>; Tue, 15 Feb 2000 18:45:20 GMT
Received: from nnse.eds.com (localhost [127.0.0.1])
	by nnse.eds.com (8.9.3/8.9.3) with ESMTP id SAA02570
	for <l2tp@ipsec.org>; Tue, 15 Feb 2000 18:39:36 GMT
Received: from gbspm002.exemhub.exch.eds.com ([207.37.51.200])
	by nnse.eds.com (8.9.3/8.9.3) with ESMTP id SAA02566
	for <l2tp@ipsec.org>; Tue, 15 Feb 2000 18:39:34 GMT
Received: by GBSPM002 with Internet Mail Service (5.5.2650.21)
	id <19M8S1L0>; Tue, 15 Feb 2000 18:39:34 -0000
Message-ID: <CD66B14E48B5D211AD300008C71ED1B4A26FAD@itrmm001.exit01.exch.eds.com>
From: "Leone, Guido" <guido.leone@eds.com>
To: "'L2TP'" <l2tp@ipsec.org>
Subject: Protocol Number 115
Date: Tue, 15 Feb 2000 17:06:49 -0000
Importance: high
X-Priority: 1
Sensitivity: Company-Confidential
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain
Sender: owner-l2tp@sailpix.com
Precedence: bulk

What is the usage of the Protocol Number 115, assigned to L2TP by IANA ? I'm
assuming the IP header of the packet containing the UDP datagram with L2TP
data should specify 17 (UDP) as the next protocol. Am I wrong ?  

 
Dr. Guido LEONE
EDS Italia SpA
Via Giamaica n.7 - 00040 Pomezia (Roma)
+39.06.91163.403  (ufficio) 
+39.06.91163.726  (facsimile)
+39.(0)335.464580 (telefono mobile)
e-mail: guido.leone@eds.com 


From owner-l2tp@ipsec.org  Tue Feb 15 18:32:42 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27482
	for <l2tpext-archive@odin.ietf.org>; Tue, 15 Feb 2000 18:32:41 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]]) by www.sailpix.com (8.8.8/8.6.9) id OAA29537; Tue, 15 Feb 2000 14:41:34 -0800 (PST)
Received: from kickme.cisco.com (kickme.cisco.com [198.92.30.42]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id OAA29533 for <l2tp@ipsec.org>; Tue, 15 Feb 2000 14:41:15 -0800 (PST)
Received: from haag-ultra.cisco.com (haag-ultra.cisco.com [161.44.49.30])
	by kickme.cisco.com (8.9.1a/8.9.1) with ESMTP id OAA09125;
	Tue, 15 Feb 2000 14:30:58 -0800 (PST)
Received: from cisco.com (townsley-home-1.cisco.com [161.44.99.51]) by haag-ultra.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/CISCO.WS.1.2) with ESMTP id RAA16106; Tue, 15 Feb 2000 17:41:02 -0500 (EST)
Message-ID: <38A9D5D5.B997B238@cisco.com>
Date: Tue, 15 Feb 2000 17:40:21 -0500
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: Andy Valencia <vandys@zendo.com>
CC: l2tp@ipsec.org
Subject: Re: L2TP header compression, link-by-link?
References: <200002151454.OAA16157@bodhi.zendo.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@sailpix.com
Precedence: bulk
Content-Transfer-Encoding: 7bit



Andy Valencia wrote:
> 
> So what's the WG's instinct on link-by-link compression for L2TP (ala RFC
> 2508)?  We're talking (potentially) about:
> 
>         RTP - UDP - IP - PPP - L2TP - UDP - IP - PPP
>         12  + 8   + 20 + 1   + 6    + 8   + 20 + 1      = 76 bytes
> 
> flattening into a single RTP-under-L2TP header (two bytes, I think).
> 
> This'll probably work out nicely for voluntary tunneling configurations.
> For the ATM model presented in DC, chopping just the outer
> PPP/L2TP/UDP/IP/PPP may suffice per VC (since the concentrator may
> multiplex too many sessions for the CID to handle the variance of the
> inner RTP/UDP/IP).  What does the WG think about a link-by-link L2TPHC
> draft, with RTP-over-L2TP, IP-over-L2TP (so carry the RTP/UDP or whatever
> else it is as payload), and just-L2TP compression options?
> 
> It sure won't scale as well on the concentrator side as base L2TP or the
> current L2TPHC drafts.  But header overhead going from 76 to 2 bytes is a
> pretty sweet win for small packet applications like RTP.  Hell, even at
> 1500 byte MTUs you could almost notice it.
> 
> - Is there a good reason why this wouldn't work?
> - Should we choose the current L2TPHC approach over this?

We should at least consider the consolidation of multiple, small, PPP
frames (such as RTP) via:

http://www.ietf.org/internet-drafts/draft-ietf-pppext-pppmux-00.txt

However, there may be latency issues with this approach that your
proposal would not entail. Also, no advantage for larger packets.

> - Vice versa?
> 
> Thanks,
> Andy Valencia
> vandys@zendo.com


From owner-l2tp@ipsec.org  Tue Feb 15 19:14:03 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA28573
	for <l2tpext-archive@odin.ietf.org>; Tue, 15 Feb 2000 19:14:02 -0500 (EST)
Received: (from majordomo@localhost) by www.sailpix.com (8.8.8/8.6.9) id OAA29462; Tue, 15 Feb 2000 14:10:37 -0800 (PST)
Received: from bodhi.zendo.com (bodhi.zendo.com [205.187.71.2]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id OAA29458 for <l2tp@ipsec.org>; Tue, 15 Feb 2000 14:10:23 -0800 (PST)
Received: from localhost.zendo.com (localhost.zendo.com [127.0.0.1]) by bodhi.zendo.com (8.8.5/8.6.12) with SMTP id OAA16157 for <l2tp@ipsec.org>; Tue, 15 Feb 2000 14:54:53 GMT
Message-Id: <200002151454.OAA16157@bodhi.zendo.com>
X-Authentication-Warning: bodhi.zendo.com: localhost.zendo.com [127.0.0.1] didn't use HELO protocol
To: l2tp@ipsec.org
Subject: L2TP header compression, link-by-link?
Date: Tue, 15 Feb 2000 14:54:53 +0000
From: Andy Valencia <vandys@zendo.com>
Sender: owner-l2tp@sailpix.com
Precedence: bulk

So what's the WG's instinct on link-by-link compression for L2TP (ala RFC
2508)?  We're talking (potentially) about:

        RTP - UDP - IP - PPP - L2TP - UDP - IP - PPP
        12  + 8   + 20 + 1   + 6    + 8   + 20 + 1      = 76 bytes

flattening into a single RTP-under-L2TP header (two bytes, I think).

This'll probably work out nicely for voluntary tunneling configurations.
For the ATM model presented in DC, chopping just the outer
PPP/L2TP/UDP/IP/PPP may suffice per VC (since the concentrator may
multiplex too many sessions for the CID to handle the variance of the
inner RTP/UDP/IP).  What does the WG think about a link-by-link L2TPHC
draft, with RTP-over-L2TP, IP-over-L2TP (so carry the RTP/UDP or whatever
else it is as payload), and just-L2TP compression options?

It sure won't scale as well on the concentrator side as base L2TP or the
current L2TPHC drafts.  But header overhead going from 76 to 2 bytes is a
pretty sweet win for small packet applications like RTP.  Hell, even at
1500 byte MTUs you could almost notice it.

- Is there a good reason why this wouldn't work?
- Should we choose the current L2TPHC approach over this?
- Vice versa?

Thanks,
Andy Valencia
vandys@zendo.com


From owner-l2tp@ipsec.org  Tue Feb 15 21:37:19 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA01069
	for <l2tpext-archive@odin.ietf.org>; Tue, 15 Feb 2000 21:37:18 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]]) by www.sailpix.com (8.8.8/8.6.9) id OAA29498; Tue, 15 Feb 2000 14:30:33 -0800 (PST)
Received: from sj-mailhub-3.cisco.com (sj-mailhub-3.cisco.com [171.68.224.215]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id OAA29494 for <l2tp@ipsec.org>; Tue, 15 Feb 2000 14:30:21 -0800 (PST)
Received: from haag-ultra.cisco.com (haag-ultra.cisco.com [161.44.49.30])
	by sj-mailhub-3.cisco.com (8.9.1a/8.9.1) with ESMTP id OAA11223;
	Tue, 15 Feb 2000 14:51:01 -0800 (PST)
Received: from cisco.com (townsley-home-1.cisco.com [161.44.99.51]) by haag-ultra.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/CISCO.WS.1.2) with ESMTP id RAA16094; Tue, 15 Feb 2000 17:29:42 -0500 (EST)
Message-ID: <38A9D32D.FD92CF5A@cisco.com>
Date: Tue, 15 Feb 2000 17:29:01 -0500
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: "Leone, Guido" <guido.leone@eds.com>
CC: "'L2TP'" <l2tp@ipsec.org>
Subject: Re: Protocol Number 115
References: <CD66B14E48B5D211AD300008C71ED1B4A26FAD@itrmm001.exit01.exch.eds.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@sailpix.com
Precedence: bulk
Content-Transfer-Encoding: 7bit


Check out:
http://www.ietf.org/internet-drafts/draft-ietf-pppext-l2tp-security-05.txt

This number may also be used in a future revision of:
http://www.ietf.org/internet-drafts/draft-ietf-l2tpext-l2tphc-00.txt

"Leone, Guido" wrote:
> 
> What is the usage of the Protocol Number 115, assigned to L2TP by IANA ? I'm
> assuming the IP header of the packet containing the UDP datagram with L2TP
> data should specify 17 (UDP) as the next protocol. Am I wrong ?
> 
> 
> Dr. Guido LEONE
> EDS Italia SpA
> Via Giamaica n.7 - 00040 Pomezia (Roma)
> +39.06.91163.403  (ufficio)
> +39.06.91163.726  (facsimile)
> +39.(0)335.464580 (telefono mobile)
> e-mail: guido.leone@eds.com


From owner-l2tp@ipsec.org  Tue Feb 15 21:55:28 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02191
	for <l2tpext-archive@odin.ietf.org>; Tue, 15 Feb 2000 21:55:27 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]]) by www.sailpix.com (8.8.8/8.6.9) id PAA29662; Tue, 15 Feb 2000 15:51:42 -0800 (PST)
Received: from bodhi.zendo.com (bodhi.zendo.com [205.187.71.2]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id PAA29658 for <l2tp@ipsec.org>; Tue, 15 Feb 2000 15:51:31 -0800 (PST)
Received: from localhost.zendo.com (localhost.zendo.com [127.0.0.1]) by bodhi.zendo.com (8.8.5/8.6.12) with SMTP id QAA16348; Tue, 15 Feb 2000 16:36:00 GMT
Message-Id: <200002151636.QAA16348@bodhi.zendo.com>
X-Authentication-Warning: bodhi.zendo.com: localhost.zendo.com [127.0.0.1] didn't use HELO protocol
To: "W. Mark Townsley" <townsley@cisco.com>
cc: l2tp@ipsec.org
Subject: Re: L2TP header compression, link-by-link? 
In-reply-to: Your message of "Tue, 15 Feb 2000 17:40:21 EST."
             <38A9D5D5.B997B238@cisco.com> 
Date: Tue, 15 Feb 2000 16:36:00 +0000
From: Andy Valencia <vandys@zendo.com>
Sender: owner-l2tp@sailpix.com
Precedence: bulk

["W. Mark Townsley" <townsley@cisco.com> writes:]

>We should at least consider the consolidation of multiple, small, PPP
>frames (such as RTP) via:
>http://www.ietf.org/internet-drafts/draft-ietf-pppext-pppmux-00.txt

That draft seems to assume that the PPP header is the primary issue.  In
fact--especially considering that CRC is not an issue for our
application--it is easily the smallest part of the problem (at one byte
per header).

>However, there may be latency issues with this approach that your
>proposal would not entail. Also, no advantage for larger packets.

And really saving only a byte or so per packet, and indeed affecting the
jitter buffering of any carried audio streams.

Andy


From owner-l2tp@ipsec.org  Wed Feb 16 05:35:50 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA21757
	for <l2tpext-archive@odin.ietf.org>; Wed, 16 Feb 2000 05:35:36 -0500 (EST)
Received: (from majordomo@localhost) by www.sailpix.com (8.8.8/8.6.9) id BAA00827; Wed, 16 Feb 2000 01:24:09 -0800 (PST)
Received: from monitor.internaut.com (mg-206253202-37.ricochet.net [206.253.202.37]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id BAA00822 for <l2tp@ipsec.org>; Wed, 16 Feb 2000 01:23:50 -0800 (PST)
Received: from vaiobean ([204.57.137.66])
	by monitor.internaut.com (8.9.2/8.8.8) with SMTP id BAA31148;
	Wed, 16 Feb 2000 01:14:54 -0800 (PST)
Reply-To: <aboba@internaut.com>
From: "Bernard Aboba" <aboba@internaut.com>
To: "'W. Mark Townsley'" <townsley@cisco.com>,
        "'Andy Valencia'" <vandys@zendo.com>
Cc: <l2tp@ipsec.org>
Subject: RE: L2TP header compression, link-by-link?
Date: Wed, 16 Feb 2000 01:23:08 -0800
Message-ID: <051501bf785f$70a39c20$2d8939cc@ntdev.microsoft.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
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)
In-Reply-To: <38A9D5D5.B997B238@cisco.com>
X-Mimeole: Produced By Microsoft MimeOLE V5.00.2919.6700
Importance: Normal
Sender: owner-l2tp@sailpix.com
Precedence: bulk
Content-Transfer-Encoding: 7bit

>We should at least consider the consolidation of multiple, small, PPP
>frames (such as RTP) via:

>http://www.ietf.org/internet-drafts/draft-ietf-pppext-pppmux-00.txt

>However, there may be latency issues with this approach that your
>proposal would not entail. Also, no advantage for larger packets.

The focus here is really on VOIP, right? Even with the full L2TP
header, for 700 octet packets the overhead is not a very big
percentage. So not being able to handle larger packets in PPPMUX 
isn't that much of a liability. 

Looks to me like PPPMUX is most effective at low bit rates (< 56 Kbps)
where the overhead saved might actually be larger than the serialization
time of an uncompressed header. In this case you save both bandwidth
and delay. Also, there's nothing that says that you can't do IP/UDP/RTP
compression within PPPMUX, right? 

Also, I am curious if the presence of the IPSEC header affects any
of these calculations. 










From owner-l2tp@ipsec.org  Wed Feb 16 05:48:31 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA21868
	for <l2tpext-archive@odin.ietf.org>; Wed, 16 Feb 2000 05:48:30 -0500 (EST)
Received: (from majordomo@localhost) by www.sailpix.com (8.8.8/8.6.9) id BAA00856; Wed, 16 Feb 2000 01:30:22 -0800 (PST)
Received: from monitor.internaut.com (mg-206253202-37.ricochet.net [206.253.202.37]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id BAA00852 for <l2tp@ipsec.org>; Wed, 16 Feb 2000 01:30:07 -0800 (PST)
Received: from vaiobean ([204.57.137.66])
	by monitor.internaut.com (8.9.2/8.8.8) with SMTP id BAA31158;
	Wed, 16 Feb 2000 01:21:30 -0800 (PST)
Reply-To: <aboba@internaut.com>
From: "Bernard Aboba" <aboba@internaut.com>
To: "'Andy Valencia'" <vandys@zendo.com>,
        "'W. Mark Townsley'" <townsley@cisco.com>
Cc: <l2tp@ipsec.org>
Subject: RE: L2TP header compression, link-by-link? 
Date: Wed, 16 Feb 2000 01:29:44 -0800
Message-ID: <051601bf7860$5d0a8fb0$2d8939cc@ntdev.microsoft.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 CWS, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <200002151636.QAA16348@bodhi.zendo.com>
X-Mimeole: Produced By Microsoft MimeOLE V5.00.2919.6700
Importance: Normal
Sender: owner-l2tp@sailpix.com
Precedence: bulk
Content-Transfer-Encoding: 7bit

>That draft seems to assume that the PPP header is the primary issue.  

Actually, in IPSEC/L2TP, the IPSEC header is an issue. 
PPPMUX gives you savings there by effectively spreading the IPSEC
overhead over multiple packets. L2TPHC doesn't accomplish this. 

>And really saving only a byte or so per packet, and indeed affecting the
>jitter buffering of any carried audio streams.

With IPSEC in the equation the savings are quite a bit larger. And
if we are talking about low bit rates, then I don't think that there
will be a jitter buffer effect. 

So I think that we might want to look at this some more. 



From owner-l2tp@ipsec.org  Wed Feb 16 07:54:57 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA25342
	for <l2tpext-archive@odin.ietf.org>; Wed, 16 Feb 2000 07:54:49 -0500 (EST)
Received: (from majordomo@localhost) by www.sailpix.com (8.8.8/8.6.9) id DAA02306; Wed, 16 Feb 2000 03:38:59 -0800 (PST)
Received: from sj-mailhub-3.cisco.com (sj-mailhub-3.cisco.com [171.68.224.215]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id DAA02302 for <l2tp@ipsec.org>; Wed, 16 Feb 2000 03:38:43 -0800 (PST)
Received: from haag-ultra.cisco.com (haag-ultra.cisco.com [161.44.49.30])
	by sj-mailhub-3.cisco.com (8.9.1a/8.9.1) with ESMTP id DAA07469;
	Wed, 16 Feb 2000 03:59:49 -0800 (PST)
Received: from cisco.com (townsley-home-1.cisco.com [161.44.99.51]) by haag-ultra.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/CISCO.WS.1.2) with ESMTP id GAA16427; Wed, 16 Feb 2000 06:38:37 -0500 (EST)
Message-ID: <38AA8C12.9AEAA5A0@cisco.com>
Date: Wed, 16 Feb 2000 06:37:54 -0500
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: aboba@internaut.com
CC: "'Andy Valencia'" <vandys@zendo.com>, l2tp@ipsec.org
Subject: Re: L2TP header compression, link-by-link?
References: <051501bf785f$70a39c20$2d8939cc@ntdev.microsoft.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@sailpix.com
Precedence: bulk
Content-Transfer-Encoding: 7bit



Bernard Aboba wrote:
> 
> >We should at least consider the consolidation of multiple, small, PPP
> >frames (such as RTP) via:
> 
> >http://www.ietf.org/internet-drafts/draft-ietf-pppext-pppmux-00.txt
> 
> >However, there may be latency issues with this approach that your
> >proposal would not entail. Also, no advantage for larger packets.
> 
> The focus here is really on VOIP, right? Even with the full L2TP
> header, for 700 octet packets the overhead is not a very big
> percentage. So not being able to handle larger packets in PPPMUX
> isn't that much of a liability.

Of course, as the size of the packet increases, the advantage of any
type of header compression decreases.

> 
> Looks to me like PPPMUX is most effective at low bit rates (< 56 Kbps)
> where the overhead saved might actually be larger than the serialization
> time of an uncompressed header. In this case you save both bandwidth
> and delay. Also, there's nothing that says that you can't do IP/UDP/RTP
> compression within PPPMUX, right?

Certainly. I believe that was an assumption of one of the applications
presented at the last IETF.

> 
> Also, I am curious if the presence of the IPSEC header affects any
> of these calculations.


From owner-l2tp@ipsec.org  Wed Feb 16 07:55:00 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA25343
	for <l2tpext-archive@odin.ietf.org>; Wed, 16 Feb 2000 07:54:52 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]]) by www.sailpix.com (8.8.8/8.6.9) id DAA02330; Wed, 16 Feb 2000 03:45:55 -0800 (PST)
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id DAA02326 for <l2tp@ipsec.org>; Wed, 16 Feb 2000 03:45:39 -0800 (PST)
Received: from haag-ultra.cisco.com (haag-ultra.cisco.com [161.44.49.30])
	by sj-msg-core-1.cisco.com (8.9.3/8.9.1) with ESMTP id DAA17498;
	Wed, 16 Feb 2000 03:45:52 -0800 (PST)
Received: from cisco.com (townsley-home-1.cisco.com [161.44.99.51]) by haag-ultra.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/CISCO.WS.1.2) with ESMTP id GAA16431; Wed, 16 Feb 2000 06:45:32 -0500 (EST)
Message-ID: <38AA8DB1.4D403F0D@cisco.com>
Date: Wed, 16 Feb 2000 06:44:49 -0500
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: aboba@internaut.com
CC: "'Andy Valencia'" <vandys@zendo.com>, l2tp@ipsec.org, ietf-ppp@merit.edu
Subject: Re: L2TP header compression, link-by-link?
References: <051601bf7860$5d0a8fb0$2d8939cc@ntdev.microsoft.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@sailpix.com
Precedence: bulk
Content-Transfer-Encoding: 7bit


Bernard Aboba wrote:
> 
> >That draft seems to assume that the PPP header is the primary issue.
> 
> Actually, in IPSEC/L2TP, the IPSEC header is an issue.
> PPPMUX gives you savings there by effectively spreading the IPSEC
> overhead over multiple packets. L2TPHC doesn't accomplish this.
> 
> >And really saving only a byte or so per packet, and indeed affecting the
> >jitter buffering of any carried audio streams.
> 
> With IPSEC in the equation the savings are quite a bit larger. And
> if we are talking about low bit rates, then I don't think that there
> will be a jitter buffer effect.
> 
> So I think that we might want to look at this some more.

One of the current limitations in pppmux is that it can only multiplex
frames smaller than 128 bytes. I believe this could be increased to 256
fairly easily. 512 might be nice as well, but might not be as simple
with the current design. Beyond that the advantages begin to dwindle as
we approach the 1500 byte MTU. 

I have brought this up with the pppmux authors once before, so the
concept should not be entirely new. Copying ietf-ppp for hope of comment
there.

- Mark


From owner-l2tp@ipsec.org  Wed Feb 16 08:33:17 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA26707
	for <l2tpext-archive@odin.ietf.org>; Wed, 16 Feb 2000 08:33:07 -0500 (EST)
Received: (from majordomo@localhost) by www.sailpix.com (8.8.8/8.6.9) id EAA02493; Wed, 16 Feb 2000 04:35:47 -0800 (PST)
Received: from sigma.cisco.com (sigma.cisco.com [171.69.63.142]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id EAA02489 for <l2tp@ipsec.org>; Wed, 16 Feb 2000 04:35:25 -0800 (PST)
Received: from cisco.com (sushi.cisco.com [171.69.106.82])
	by sigma.cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id EAA20935;
	Wed, 16 Feb 2000 04:30:28 -0800 (PST)
Message-ID: <38AA987F.50A9D26F@cisco.com>
Date: Wed, 16 Feb 2000 07:30:56 -0500
From: Craig Fox <fox@cisco.com>
Organization: Cisco Systems
X-Mailer: Mozilla 4.7 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "W. Mark Townsley" <townsley@cisco.com>
CC: aboba@internaut.com, "'Andy Valencia'" <vandys@zendo.com>, l2tp@ipsec.org,
        ietf-ppp@merit.edu
Subject: Re: L2TP header compression, link-by-link?
References: <051601bf7860$5d0a8fb0$2d8939cc@ntdev.microsoft.com> <38AA8DB1.4D403F0D@cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@sailpix.com
Precedence: bulk
Content-Transfer-Encoding: 7bit

"W. Mark Townsley" wrote:
> 
> Bernard Aboba wrote:
> >
> > >That draft seems to assume that the PPP header is the primary issue.
> >
> > Actually, in IPSEC/L2TP, the IPSEC header is an issue.
> > PPPMUX gives you savings there by effectively spreading the IPSEC
> > overhead over multiple packets. L2TPHC doesn't accomplish this.
> >
> > >And really saving only a byte or so per packet, and indeed affecting the
> > >jitter buffering of any carried audio streams.
> >
> > With IPSEC in the equation the savings are quite a bit larger. And
> > if we are talking about low bit rates, then I don't think that there
> > will be a jitter buffer effect.
> >
> > So I think that we might want to look at this some more.
> 
> One of the current limitations in pppmux is that it can only multiplex
> frames smaller than 128 bytes. I believe this could be increased to 256
> fairly easily. 512 might be nice as well, but might not be as simple
> with the current design. Beyond that the advantages begin to dwindle as
> we approach the 1500 byte MTU.

With the current design, it is not possible to go past 128 bytes.  However,
it occurred to me that a minor mod which would lower the maximum efficient
size to 64 bytes (still above the normal 'small' packet size) would allow
us to multiplex packets up to 16k bytes.  The approach would be to steal
another bit from the length field to identify an extended length field
where the next byte was the rest of the 14 bit length field (two bytes of
length minus two flag bits, one for protocol compression bit and one for
the extended length field flag).  This makes some of the processing more
complex while simplifying other processing since it would no longer be
necessary to flush the multiplexing frame because the next frame to be
added was too long.

What was not clear about the above approach (because I haven't taken the
time to analyze it) was whether it would result in a net savings for
larger (>256 byte) packets that would make it worth reducing the efficiency
of packets between 64 and 128 bytes.

Craig

> 
> I have brought this up with the pppmux authors once before, so the
> concept should not be entirely new. Copying ietf-ppp for hope of comment
> there.
> 
> - Mark


From owner-l2tp@ipsec.org  Wed Feb 16 16:26:53 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14324
	for <l2tpext-archive@odin.ietf.org>; Wed, 16 Feb 2000 16:26:42 -0500 (EST)
Received: (from majordomo@localhost) by www.sailpix.com (8.8.8/8.6.9) id MAA03166; Wed, 16 Feb 2000 12:10:51 -0800 (PST)
Received: from jindo.cisco.com (jindo.cisco.com [171.69.11.73]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id MAA03162 for <l2tp@ipsec.org>; Wed, 16 Feb 2000 12:10:31 -0800 (PST)
Received: from tmima-nt (dhcp-vm22-89-167.cisco.com [171.69.89.167])
	by jindo.cisco.com (8.8.8/2.5.1/Cisco List Logging/8.8.8) with SMTP id MAA13684;
	Wed, 16 Feb 2000 12:05:33 -0800 (PST)
Message-Id: <4.1.20000216115045.040a8700@jindo.cisco.com>
X-Sender: tmima@jindo.cisco.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Wed, 16 Feb 2000 12:04:48 -0800
To: "W. Mark Townsley" <townsley@cisco.com>, aboba@internaut.com
From: Tmima Koren <tmima@cisco.com>
Subject: Re: L2TP header compression, link-by-link?
Cc: "'Andy Valencia'" <vandys@zendo.com>, l2tp@ipsec.org
In-Reply-To: <38AA8C12.9AEAA5A0@cisco.com>
References: <051501bf785f$70a39c20$2d8939cc@ntdev.microsoft.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-l2tp@sailpix.com
Precedence: bulk

At 06:37 AM 2/16/00 -0500, W. Mark Townsley wrote:
>
>
>Bernard Aboba wrote:
>> 
>> >We should at least consider the consolidation of multiple, small, PPP
>> >frames (such as RTP) via:
>> 
>> >http://www.ietf.org/internet-drafts/draft-ietf-pppext-pppmux-00.txt
>> 
>> >However, there may be latency issues with this approach that your
>> >proposal would not entail. Also, no advantage for larger packets.
>> 
>> The focus here is really on VOIP, right? Even with the full L2TP
>> header, for 700 octet packets the overhead is not a very big
>> percentage. So not being able to handle larger packets in PPPMUX
>> isn't that much of a liability.
>
>Of course, as the size of the packet increases, the advantage of any
>type of header compression decreases.
>
>> 
>> Looks to me like PPPMUX is most effective at low bit rates (< 56 Kbps)
>> where the overhead saved might actually be larger than the serialization
>> time of an uncompressed header. In this case you save both bandwidth
>> and delay. Also, there's nothing that says that you can't do IP/UDP/RTP
>> compression within PPPMUX, right?
>
>Certainly. I believe that was an assumption of one of the applications
>presented at the last IETF.

That's TCRTP: Tunneled multiplexed CRTP
TCRTP uses L2TPHC to tunnel CRTP packets, optionally multiplexed using PPPMUX.
Tmima

>
>> 
>> Also, I am curious if the presence of the IPSEC header affects any
>> of these calculations.
>



From owner-l2tp@ipsec.org  Sun Feb 20 22:16:37 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA15781
	for <l2tpext-archive@odin.ietf.org>; Sun, 20 Feb 2000 22:16:36 -0500 (EST)
Received: (from majordomo@localhost) by www.sailpix.com (8.8.8/8.6.9) id RAA13885; Sun, 20 Feb 2000 17:46:42 -0800 (PST)
Received: from smtplink.pulse.com (pulsecom-229.pulse.com [192.77.130.229] (may be forged)) by www.sailpix.com (8.8.8/8.6.9) with SMTP id RAA13881 for <l2tp@ipsec.org>; Sun, 20 Feb 2000 17:46:32 -0800 (PST)
Date: Sun, 20 Feb 2000 16:33 -0500
From: "Vic Diloreto" <Vic.Diloreto@pulse.com>
To: "l2tp@ipsec.org" <l2tp@ipsec.org>
Subject: L2TP Hello Message Semantics
Message-ID: <20000220204224217-22c111d0@pulse.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-l2tp@sailpix.com
Precedence: bulk


A question regarding the hello message exchange between a LAC and an LNS.
We have noticed that when a LAC sends a Hello, and the LNS responds, that
sometimes the ack gets lost due to network congestion. The LAC retries, but the
LNS does not respond as it thinks it has already responded. Is this appropriate 
behavior for the LNS ? Should the LAC be doing something different to make 
sure the Hello gets a response ?

Thanks,

Vic Diloreto


From owner-l2tp@ipsec.org  Sun Feb 20 23:03:56 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA16967
	for <l2tpext-archive@odin.ietf.org>; Sun, 20 Feb 2000 23:03:55 -0500 (EST)
Received: (from majordomo@localhost) by www.sailpix.com (8.8.8/8.6.9) id SAA13957; Sun, 20 Feb 2000 18:56:41 -0800 (PST)
Received: from gate.ascend.co.jp (root@gate.ascend.co.jp [202.246.11.253]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id SAA13953 for <l2tp@ipsec.org>; Sun, 20 Feb 2000 18:56:17 -0800 (PST)
Received: from home.ascend.co.jp (home.ascend.co.jp [202.246.11.1])
	by gate.ascend.co.jp (8.9.1a/3.7W/09/09/99) with ESMTP id LAA28263;
	Mon, 21 Feb 2000 11:56:12 +0900 (JST)
Received: from toshiba.ober.net (dhcp171.ascend.co.jp [202.246.11.171])
	by home.ascend.co.jp (8.8.8/3.7W/10/14/99) with ESMTP id LAA02760;
	Mon, 21 Feb 2000 11:56:12 +0900 (JST)
Received: from localhost (localhost [127.0.0.1])
	by toshiba.ober.net (8.9.3/3.6W/home.ascend.co.jpevision: 1.1 $) with ESMTP id LAA02244;
	Mon, 21 Feb 2000 11:59:01 +0900 (JST)
To: Vic.Diloreto@pulse.com
Cc: l2tp@ipsec.org
Subject: Re: L2TP Hello Message Semantics
From: Motonori Shindo <mshindo@ascend.co.jp>
In-Reply-To: <20000220204224217-22c111d0@pulse.com>
References: <20000220204224217-22c111d0@pulse.com>
X-Mailer: Mew version 1.94b47 on XEmacs 20.4 (Emerald)
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
Message-Id: <20000221115859U.mshindo@ascend.co.jp>
Date: Mon, 21 Feb 2000 11:58:59 +0900
X-Dispatcher: imput version 990731(IM118)
Lines: 52
Sender: owner-l2tp@sailpix.com
Precedence: bulk
Content-Transfer-Encoding: 7bit

Vic,

Here's an exerpt from rfc-2661.

                                                       Such a message
   would be considered a duplicate of a message already received and
   ignored from processing. However, in order to ensure that all
   messages are acknowledged properly (particularly in the case of a
   lost ZLB ACK message), receipt of duplicate messages MUST be
   acknowledged by the reliable transport. This acknowledgement may
   either piggybacked on a message in queue, or explicitly via a ZLB
   ACK.

My view to L2TP is that L2TP protocol stack consists of two distinct
layers: message delivery and protocol processing. From this
perspective, the paragraph above can be elaborated as "ignored by the
protocol processsing layer, however it must be always acknowledged by
the message delivery layer because it must guarantee the reliable
transport.

There used to be an implementation that never acknowledges the
duplicted messages. I know of at least one implementation that had
this problem. Newer version of this software fixed this problem, but
in a little bit weird way.

Regards,

From: "Vic Diloreto" <Vic.Diloreto@pulse.com>
Subject: L2TP Hello Message Semantics
Date: Sun, 20 Feb 2000 16:33 -0500

> 
> A question regarding the hello message exchange between a LAC and an LNS.
> We have noticed that when a LAC sends a Hello, and the LNS responds, that
> sometimes the ack gets lost due to network congestion. The LAC retries, but the
> LNS does not respond as it thinks it has already responded. Is this appropriate 
> behavior for the LNS ? Should the LAC be doing something different to make 
> sure the Hello gets a response ?
> 
> Thanks,
> 
> Vic Diloreto
> 

=====================================================
Motonori Shindo
   Systems Engineer     
   Ascend Communications Japan K.K.
   A wholly owned subsidiary of Lucent Technologies.
   email: mshindo@ascend.co.jp or mshindo@lucent.com
   TEL: +81-3-5325-7306 
=====================================================


From owner-l2tp@ipsec.org  Sun Feb 20 23:34:56 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA17456
	for <l2tpext-archive@odin.ietf.org>; Sun, 20 Feb 2000 23:34:55 -0500 (EST)
Received: (from majordomo@localhost) by www.sailpix.com (8.8.8/8.6.9) id TAA13990; Sun, 20 Feb 2000 19:14:35 -0800 (PST)
Received: from gate.ascend.co.jp (root@gate.ascend.co.jp [202.246.11.253]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id TAA13986 for <l2tp@ipsec.org>; Sun, 20 Feb 2000 19:14:16 -0800 (PST)
Received: from home.ascend.co.jp (home.ascend.co.jp [202.246.11.1])
	by gate.ascend.co.jp (8.9.1a/3.7W/09/09/99) with ESMTP id MAA28476;
	Mon, 21 Feb 2000 12:14:12 +0900 (JST)
Received: from admse.ascend.co.jp (admse.ascend.co.jp [202.246.11.186])
	by home.ascend.co.jp (8.8.8/3.7W/10/14/99) with ESMTP id MAA03044;
	Mon, 21 Feb 2000 12:14:12 +0900 (JST)
Received: from tyanagib.ascend.co.jp (tyanagib2.ascend.co.jp [202.246.11.164])
	by admse.ascend.co.jp (8.8.8/3.7W/08/31/99) with SMTP id MAA29772;
	Mon, 21 Feb 2000 12:14:11 +0900 (JST)
Message-Id: <200002210318.AA00398@tyanagib.ascend.co.jp>
From: Tatsuya Yanagibashi <tyanagibashi@ascend.co.jp>
Date: Mon, 21 Feb 2000 12:18:24 +0900
To: "Vic Diloreto" <Vic.Diloreto@pulse.com>
Cc: "l2tp@ipsec.org" <l2tp@ipsec.org>
Subject: Re: L2TP Hello Message Semantics
In-Reply-To: <20000220204224217-22c111d0@pulse.com>
References: <20000220204224217-22c111d0@pulse.com>
MIME-Version: 1.0
X-Mailer: AL-Mail32 Version 1.11
Content-Type: text/plain; charset=us-ascii
Sender: owner-l2tp@sailpix.com
Precedence: bulk

It happens to lost ZLB Ack from LNS because of network congestion.

From l2tp RFC, a reciever of contorol message MUST acknowledge by piggybacked 
on a message in queue, or explicitly via a ZLB ACK even if that control message 
seem to be duplicated.

Regards,
Tatsuya Yanagibashi

>
>A question regarding the hello message exchange between a LAC and an LNS.
>We have noticed that when a LAC sends a Hello, and the LNS responds, that
>sometimes the ack gets lost due to network congestion. The LAC retries, but the
>LNS does not respond as it thinks it has already responded. Is this appropriate 
>behavior for the LNS ? Should the LAC be doing something different to make 
>sure the Hello gets a response ?
>
>Thanks,
>
>Vic Diloreto
>


From owner-l2tp@ipsec.org  Tue Feb 22 07:58:15 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA09527
	for <l2tpext-archive@odin.ietf.org>; Tue, 22 Feb 2000 07:58:14 -0500 (EST)
Received: (from majordomo@localhost) by www.sailpix.com (8.8.8/8.6.9) id DAA04357; Tue, 22 Feb 2000 03:56:52 -0800 (PST)
Received: from Mitel.COM (newgate.mitel.com [198.53.180.100]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id DAA04353 for <l2tp@ipsec.org>; Tue, 22 Feb 2000 03:56:38 -0800 (PST)
Received: from uk_exchsrvr.mitel.com (uk_exchsrvr.uksemi.mitel.com [134.199.192.51]) 
	by Mitel.COM (V8/MAIL-RELAY-2.1) with ESMTP id GAA24102
	for <l2tp@ipsec.org>; Tue, 22 Feb 2000 06:55:50 -0500 (EST)
Received: by uk_exchsrvr.uksemi.mitel.com with Internet Mail Service (5.5.2448.0)
	id <1HNS8GWF>; Tue, 22 Feb 2000 11:56:38 -0000
Message-ID: <00902F6EFF53D311861B00A0C960128F0D68D7@uk_exchsrvr.uksemi.mitel.com>
From: "Lough, Andrew" <Andrew_Lough@Mitel.COM>
To: "'l2tp@ipsec.org'" <l2tp@ipsec.org>
Subject: Question from an IPSec newbie
Date: Tue, 22 Feb 2000 11:56:30 -0000
Importance: high
X-Priority: 1
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-l2tp@sailpix.com
Precedence: bulk

If Router A was a head office router leased line to ISP and B was a branch
using Dialup ISDN, is it possible, within the IPSec defined standards for
the following to work.

All traffic is initiated from B

B dials an ISP, Negotiates a DYNAMIC IP address, then sets up the IPSec
tunnel to Router A (Router A has a static Internet IP address)

Router A learns the current IP Address or B during negotiation and LAN-LAN
traffic can then be routed.



If this is feasible, could a kind person please point me in the direction of
the relevant RFC and if possible section, as I am currently struggling with
a supplier.

R's

Andy

thanks in advance for your assistance


From owner-l2tp@ipsec.org  Tue Feb 22 08:08:05 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA09526
	for <l2tpext-archive@odin.ietf.org>; Tue, 22 Feb 2000 07:58:14 -0500 (EST)
Received: (from majordomo@localhost) by www.sailpix.com (8.8.8/8.6.9) id DAA04332; Tue, 22 Feb 2000 03:38:18 -0800 (PST)
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id DAA04328 for <l2tp@ipsec.org>; Tue, 22 Feb 2000 03:37:48 -0800 (PST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA08614;
	Tue, 22 Feb 2000 06:37:36 -0500 (EST)
Message-Id: <200002221137.GAA08614@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-00.txt
Date: Tue, 22 Feb 2000 06:37:36 -0500
Sender: owner-l2tp@sailpix.com
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-00.txt
	Pages		: 23
	Date		: 21-Feb-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-00.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-00.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-00.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:	<20000221100456.I-D@ietf.org>

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

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

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

--OtherAccess--

--NextPart--




From owner-l2tp@ipsec.org  Fri Feb 25 16:36:40 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21455
	for <l2tpext-archive@odin.ietf.org>; Fri, 25 Feb 2000 16:36:34 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]]) by www.sailpix.com (8.8.8/8.6.9) id MAA13130; Fri, 25 Feb 2000 12:17:23 -0800 (PST)
Received: from smtprich.nortel.com (smtprich.nortel.com [192.135.215.8]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id MAA13126 for <l2tp@ipsec.org>; Fri, 25 Feb 2000 12:17:06 -0800 (PST)
Received: from zrchb200.us.nortel.com (actually zrchb200) 
          by smtprich.nortel.com; Fri, 25 Feb 2000 14:17:19 -0600
Received: from crchy28b.us.nortel.com ([47.100.128.236]) 
          by zrchb200.us.nortel.com 
          with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) 
          id FBJDNWA5; Fri, 25 Feb 2000 14:16:30 -0600
Received: from americasm01.nt.com (crchi263.us.nortel.com [47.209.85.59]) 
          by crchy28b.us.nortel.com 
          with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) 
          id 15YA1ZNB; Fri, 25 Feb 2000 14:16:27 -0600
Message-ID: <38B6D7D0.93F6EE95@americasm01.nt.com>
Date: Fri, 25 Feb 2000 14:28:16 -0500
From: "Gokul Subramaniam" <gokuls@nortelnetworks.com>
Organization: Nortel Networks
X-Mailer: Mozilla 4.06 [en] (Win95; U)
MIME-Version: 1.0
To: l2tp@ipsec.org
Subject: L2TP Over IPSec & Tunnel Setup
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Orig: <gokuls@americasm01.nt.com>
Sender: owner-l2tp@sailpix.com
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hello.,

Problem Context:
The implementation of an L2TP tunnel was to access private network.
Compulsory tunneling is used. Tunnel setup is done for the users after
authentication using RADIUS.
RADIUS is used to get the tunnel information (using access request and
accept messages passing the LAC-tunnel initiator info in access req and
receiving LNS-tunnel terminator info in access accept message) - in
conformance to IETF Draft: RADIUS Attributes for Tunnel Protocol Support
<draft-ietf-radius-tunnel-auth-09.txt>.

Problem:
Although the RADIUS extension for tunnel-auth provides the LNS ip
address and supported tunnel type, it does not support configuration
information for ipsec.
LNS gets the LAC information from RADIUS. But where does the LNS get
ipsec related information for the tunnel terminator (LAC). This is not
addressed in the RADIUS Tunnel support draft. In order to get the ipsec
profile and ike profiles should the LNS be configured separately on a
per tunnel terminator basis?

Are there any extensions that support getting the profiles or
negotiating the ipsec and ike profiles as part of getting the tunnel
terminator information.

Input is appreciated.



From owner-l2tp@ipsec.org  Fri Feb 25 18:38:02 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA23283
	for <l2tpext-archive@odin.ietf.org>; Fri, 25 Feb 2000 18:38:01 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]]) by www.sailpix.com (8.8.8/8.6.9) id OAA13278; Fri, 25 Feb 2000 14:36:51 -0800 (PST)
Received: from smtprch1.nortel.com (smtprch1.nortelnetworks.com [192.135.215.14]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id OAA13274 for <l2tp@ipsec.org>; Fri, 25 Feb 2000 14:36:15 -0800 (PST)
Received: from zrchb200.us.nortel.com (actually zrchb200) 
          by smtprch1.nortel.com; Fri, 25 Feb 2000 16:34:03 -0600
Received: by zrchb200.us.nortel.com with Internet Mail Service (5.5.2650.21) 
          id <FBJDN79L>; Fri, 25 Feb 2000 16:33:53 -0600
Message-ID: <9A9367D1556AD21182C40000F80930AB01FA228F@crchy28b.us.nortel.com>
From: "Gokul Subramaniam" <gokuls@nortelnetworks.com>
To: l2tp@ipsec.org
Date: Fri, 25 Feb 2000 16:33:49 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01BF7FE0.63E19716"
Sender: owner-l2tp@sailpix.com
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_01BF7FE0.63E19716
Content-Type: text/plain

Hello.,

Problem Context:
Implementation of an L2TP tunnel to access private network.
Compulsory tunneling is used. Tunnel setup is done for the users after
authentication using RADIUS.
RADIUS is used to get the tunnel information (using access request and
accept messages passing the LAC-tunnel initiator info in access req and
receiving LNS-tunnel terminator info in access accept message) - in
conformance to IETF Draft: RADIUS Attributes for Tunnel Protocol Support
<draft-ietf-radius-tunnel-auth-09.txt>.

Problem:
Although the RADIUS extension for tunnel-auth
<draft-ietf-radius-tunnel-auth-09.txt>
provides the LNS ip address and supported tunnel type, it does not support 
configuration information for ipsec.
LNS gets the LAC information from RADIUS. But where does the LNS get
ipsec related information for the tunnel terminator (LAC). This is not
addressed in the RADIUS Tunnel support draft. In order to get the ipsec
profile and ike profiles should the LNS be configured separately on a
per tunnel terminator basis?

Are there any extensions that support getting the profiles or
negotiating the ipsec and ike profiles as part of getting the tunnel
terminator information?

Input is appreciated.
-Gokul.

Gokul V. Subramaniam          
NORTEL Networks
CDMA Wireless Data Development
email:gokuls@nortelnetworks.com
Ph:972 685 8214. ESN:445 8214



------_=_NextPart_001_01BF7FE0.63E19716
Content-Type: text/html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2651.65">
<TITLE></TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=2 FACE="Arial">Hello.,</FONT>
</P>

<P><FONT SIZE=2 FACE="Arial">Problem Context:</FONT>
<BR><FONT SIZE=2 FACE="Arial">Implementation of an L2TP tunnel to access private network.</FONT>
<BR><FONT SIZE=2 FACE="Arial">Compulsory tunneling is used. Tunnel setup is done for the users after</FONT>
<BR><FONT SIZE=2 FACE="Arial">authentication using RADIUS.</FONT>
<BR><FONT SIZE=2 FACE="Arial">RADIUS is used to get the tunnel information (using access request and</FONT>
<BR><FONT SIZE=2 FACE="Arial">accept messages passing the LAC-tunnel initiator info in access req and</FONT>
<BR><FONT SIZE=2 FACE="Arial">receiving LNS-tunnel terminator info in access accept message) - in</FONT>
<BR><FONT SIZE=2 FACE="Arial">conformance to IETF Draft: RADIUS Attributes for Tunnel Protocol Support</FONT>
<BR><FONT SIZE=2 FACE="Arial">&lt;draft-ietf-radius-tunnel-auth-09.txt&gt;.</FONT>
</P>

<P><FONT SIZE=2 FACE="Arial">Problem:</FONT>
<BR><FONT SIZE=2 FACE="Arial">Although the RADIUS extension for tunnel-auth &lt;draft-ietf-radius-tunnel-auth-09.txt&gt;</FONT>
<BR><FONT SIZE=2 FACE="Arial">provides the LNS ip address and supported tunnel type, it does not support </FONT>
<BR><FONT SIZE=2 FACE="Arial">configuration information for ipsec.</FONT>
<BR><FONT SIZE=2 FACE="Arial">LNS gets the LAC information from RADIUS. But where does the LNS get</FONT>
<BR><FONT SIZE=2 FACE="Arial">ipsec related information for the tunnel terminator (LAC). This is not</FONT>
<BR><FONT SIZE=2 FACE="Arial">addressed in the RADIUS Tunnel support draft. In order to get the ipsec</FONT>
<BR><FONT SIZE=2 FACE="Arial">profile and ike profiles should the LNS be configured separately on a</FONT>
<BR><FONT SIZE=2 FACE="Arial">per tunnel terminator basis?</FONT>
</P>

<P><FONT SIZE=2 FACE="Arial">Are there any extensions that support getting the profiles or</FONT>
<BR><FONT SIZE=2 FACE="Arial">negotiating the ipsec and ike profiles as part of getting the tunnel</FONT>
<BR><FONT SIZE=2 FACE="Arial">terminator information?</FONT>
</P>

<P><FONT SIZE=2 FACE="Arial">Input is appreciated.</FONT>
<BR><FONT SIZE=2 FACE="Arial">-Gokul.</FONT>
</P>

<P><B><FONT COLOR="#808000" FACE="Comic Sans MS">Gokul V. Subramaniam&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </FONT></B>
<BR><B><FONT COLOR="#800000" SIZE=2 FACE="Comic Sans MS">NORTEL Networks</FONT></B>
<BR><B><FONT COLOR="#800000" SIZE=2 FACE="Comic Sans MS">CDMA Wireless Data Development</FONT></B>
<BR><B><FONT COLOR="#800000" SIZE=2 FACE="Comic Sans MS">email:gokuls@nortelnetworks.com</FONT></B>
<BR><B><FONT COLOR="#800000" SIZE=2 FACE="Comic Sans MS">Ph:972 685 8214. ESN:445 8214</FONT></B>
</P>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01BF7FE0.63E19716--


From owner-l2tp@ipsec.org  Mon Feb 28 19:06:54 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA24020
	for <l2tpext-archive@odin.ietf.org>; Mon, 28 Feb 2000 19:06:54 -0500 (EST)
Received: (from majordomo@localhost) by www.sailpix.com (8.8.8/8.6.9) id OAA20250; Mon, 28 Feb 2000 14:39:55 -0800 (PST)
Received: from franklin.cisco.com (franklin.cisco.com [171.70.156.17]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id OAA20246 for <l2tp@ipsec.org>; Mon, 28 Feb 2000 14:39:37 -0800 (PST)
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 OAA23811; Mon, 28 Feb 2000 14:38:59 -0800 (PST)
Message-Id: <200002282238.OAA23811@franklin.cisco.com>
X-Sender: gwz@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.2 
Date: Mon, 28 Feb 2000 14:43:11 -0800
To: "Gokul Subramaniam" <gokuls@nortelnetworks.com>
From: Glen Zorn <gwz@cisco.com>
Subject: Re: L2TP Over IPSec & Tunnel Setup
Cc: l2tp@ipsec.org, ietf-radius@livingston.com
In-Reply-To: <38B6D7D0.93F6EE95@americasm01.nt.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-l2tp@sailpix.com
Precedence: bulk

At 02:28 PM 02/25/2000 -0500, Gokul Subramaniam wrote:

Copying the RADIUS list because that's where this belongs
>Hello.,
>
>Problem Context:
>The implementation of an L2TP tunnel was to access private network.
>Compulsory tunneling is used. Tunnel setup is done for the users after
>authentication using RADIUS.
>RADIUS is used to get the tunnel information (using access request and
>accept messages passing the LAC-tunnel initiator info in access req and
>receiving LNS-tunnel terminator info in access accept message) - in
>conformance to IETF Draft: RADIUS Attributes for Tunnel Protocol Support
><draft-ietf-radius-tunnel-auth-09.txt>.
>
>Problem:
>Although the RADIUS extension for tunnel-auth provides the LNS ip
>address and supported tunnel type, it does not support configuration
>information for ipsec.
>LNS gets the LAC information from RADIUS. But where does the LNS get
>ipsec related information for the tunnel terminator (LAC). This is not
>addressed in the RADIUS Tunnel support draft. In order to get the ipsec
>profile and ike profiles should the LNS be configured separately on a
>per tunnel terminator basis?

Yes.
>
>Are there any extensions that support getting the profiles or
>negotiating the ipsec and ike profiles as part of getting the tunnel
>terminator information.

None that are "standard"; I'm sure that there are proprietary extensions.

>
>Input is appreciated.
> 



From owner-l2tp@ipsec.org  Mon Feb 28 19:36:42 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA24446
	for <l2tpext-archive@odin.ietf.org>; Mon, 28 Feb 2000 19:36:42 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]]) by www.sailpix.com (8.8.8/8.6.9) id PAA20397; Mon, 28 Feb 2000 15:52:43 -0800 (PST)
Received: from ns2.accesscom.com (root@ns2.accesscom.com [205.226.156.3]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id PAA20393 for <l2tp@ipsec.org>; Mon, 28 Feb 2000 15:52:31 -0800 (PST)
Received: from shell.accesscom.com (root@shell.accesscom.com [205.226.156.10])
	by ns2.accesscom.com (8.9.3/8.9.3/Debian/GNU) with ESMTP id PAA22156;
	Mon, 28 Feb 2000 15:52:29 -0800
Received: (from sabrina@localhost)
	by shell.accesscom.com (8.9.3/8.9.3/Debian/GNU) id PAA01354;
	Mon, 28 Feb 2000 15:52:29 -0800
From: Sabrina Minshall <sabrina@accesscom.com>
Message-Id: <200002282352.PAA01354@shell.accesscom.com>
Subject: LNS configuration
To: l2tp@ipsec.org
Date: Mon, 28 Feb 2000 15:52:29 -0800 (PST)
CC: sabrina@accesscom.com
X-Mailer: ELM [version 2.4ME+ PL65 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@sailpix.com
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi All,
  I'm looking for information on LNS configuration.

  What are global paramaters? and what's local (ie, per 
  LAC information)?

  How does LNS filter on who (which) LAC's can connect?

  Does the LNS need to maintain per LAC profiles? 
  How the lookup done to retrieve per LAC infomation - 
	based on hostname, etc?

  And, what do the vendors do?

  Appreciate any info or pointers.

  Thanks,

  Adagio


From owner-l2tp@ipsec.org  Mon Feb 28 22:25:23 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA27341
	for <l2tpext-archive@odin.ietf.org>; Mon, 28 Feb 2000 22:25:23 -0500 (EST)
Received: (from majordomo@localhost) by www.sailpix.com (8.8.8/8.6.9) id SAA20602; Mon, 28 Feb 2000 18:22:10 -0800 (PST)
Received: from web106.yahoomail.com (web106.yahoomail.com [205.180.60.73]) by www.sailpix.com (8.8.8/8.6.9) with SMTP id SAA20598 for <l2tp@ipsec.org>; Mon, 28 Feb 2000 18:21:54 -0800 (PST)
Received: (qmail 21944 invoked by uid 60001); 29 Feb 2000 02:27:31 -0000
Message-ID: <20000229022731.21943.qmail@web106.yahoomail.com>
Received: from [208.248.148.131] by web106.yahoomail.com; Mon, 28 Feb 2000 18:27:31 PST
Date: Mon, 28 Feb 2000 18:27:31 -0800 (PST)
From: Venkatesan Pradeep <vpradeepv@yahoo.com>
Subject: interoperability with draft12 LAC
To: l2tp@ipsec.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-l2tp@sailpix.com
Precedence: bulk

I am implementing an LNS and I want to be able to deal with both
draft12 and RFC compliant LACs. I want to have sequence numbers on
all payload packets, by default. Since both RFC and draft12 say that
payload packet sequencing can be dynamically enabled/disabled by the
LNS, I thought it would be a simple matter of having the LNS start
sending out packets with sequence numbers after the session is
established.

However, I found that the LAC (most likely a draft12 implementation)
that I am using does not send sequence numbers unless I send a
RWS AVP in the ICRP. Is the LAC behaving correctly w.r.t draft12?

According to draft12, unless either peer sends a RWS AVP, sequence
numbers are absent for the session but it also says that if the LAC
has not sent the Sequencing Required AVP, the LNS is free to
dyanmically enable or disable sequencing. Perhaps the LAC I am using is
interpreting this to mean that since RWS AVP has not been sent by
either peer there is no sequencing involved and thus the LNS cannot
enable it - it can only disable sequencing if already enabled and
re-enable it.

If the LAC is behaving correctly, how do I deal with this situation?.
I thought of sending an ICRP with the RWS AVP with RW=0 but that
would make me behave like a draft12 LNS.

Thanks,

Pradeep.

__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com


From owner-l2tp@ipsec.org  Mon Feb 28 23:38:36 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA29439
	for <l2tpext-archive@odin.ietf.org>; Mon, 28 Feb 2000 23:38:35 -0500 (EST)
Received: from localhost (localhost [[UNIX: localhost]]) by www.sailpix.com (8.8.8/8.6.9) id TAA20680; Mon, 28 Feb 2000 19:38:04 -0800 (PST)
Received: from franklin.cisco.com (franklin.cisco.com [171.70.156.17]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id TAA20676 for <l2tp@ipsec.org>; Mon, 28 Feb 2000 19:37:51 -0800 (PST)
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 TAA04573; Mon, 28 Feb 2000 19:36:49 -0800 (PST)
Message-Id: <200002290336.TAA04573@franklin.cisco.com>
X-Sender: gwz@localhost
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.2 
Date: Mon, 28 Feb 2000 19:40:06 -0800
To: Sabrina Minshall <sabrina@accesscom.com>
From: Glen Zorn <gwz@cisco.com>
Subject: Re: LNS configuration
Cc: l2tp@ipsec.org, sabrina@accesscom.com
In-Reply-To: <200002282352.PAA01354@shell.accesscom.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-l2tp@sailpix.com
Precedence: bulk

At 03:52 PM 02/28/2000 -0800, Sabrina Minshall wrote:
>Hi All,
>  I'm looking for information on LNS configuration.

P{lease ask your LNS vendor.  This list is for discussing the L2TP _protocol_.
>
>  What are global paramaters? and what's local (ie, per 
>  LAC information)?
>
>  How does LNS filter on who (which) LAC's can connect?
>
>  Does the LNS need to maintain per LAC profiles? 
>  How the lookup done to retrieve per LAC infomation - 
>	based on hostname, etc?
>
>  And, what do the vendors do?
>
>  Appreciate any info or pointers.
>
>  Thanks,
>
>  Adagio
> 



From owner-l2tp@ipsec.org  Tue Feb 29 03:26:35 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA13423
	for <l2tpext-archive@odin.ietf.org>; Tue, 29 Feb 2000 03:26:35 -0500 (EST)
Received: (from majordomo@localhost) by www.sailpix.com (8.8.8/8.6.9) id XAA20873; Mon, 28 Feb 2000 23:15:56 -0800 (PST)
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id XAA20869 for <l2tp@ipsec.org>; Mon, 28 Feb 2000 23:15:30 -0800 (PST)
Received: from haag-ultra.cisco.com (haag-ultra.cisco.com [161.44.49.30])
	by sj-msg-core-1.cisco.com (8.9.3/8.9.1) with ESMTP id XAA22775;
	Mon, 28 Feb 2000 23:15:47 -0800 (PST)
Received: from cisco.com (dhcp-171-69-70-241.cisco.com [171.69.70.241]) by haag-ultra.cisco.com (8.8.5-Cisco.2-SunOS.5.5.1.sun4/CISCO.WS.1.2) with ESMTP id CAA23600; Tue, 29 Feb 2000 02:15:34 -0500 (EST)
Message-ID: <38BB71E2.6C16CEE0@cisco.com>
Date: Tue, 29 Feb 2000 02:14:42 -0500
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: Venkatesan Pradeep <vpradeepv@yahoo.com>
CC: l2tp@ipsec.org
Subject: Re: interoperability with draft12 LAC
References: <20000229022731.21943.qmail@web106.yahoomail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@sailpix.com
Precedence: bulk
Content-Transfer-Encoding: 7bit



Venkatesan Pradeep wrote:
> 
> I am implementing an LNS and I want to be able to deal with both
> draft12 and RFC compliant LACs. I want to have sequence numbers on
> all payload packets, by default. Since both RFC and draft12 say that
> payload packet sequencing can be dynamically enabled/disabled by the
> LNS, I thought it would be a simple matter of having the LNS start
> sending out packets with sequence numbers after the session is
> established.

Should be.

> 
> However, I found that the LAC (most likely a draft12 implementation)
> that I am using does not send sequence numbers unless I send a
> RWS AVP in the ICRP. Is the LAC behaving correctly w.r.t draft12?

It is actually operating pre-draft 12. If it were operating at draft-12,
then it should handle the dynamic sequencing.

> 
> According to draft12, unless either peer sends a RWS AVP, sequence
> numbers are absent for the session but it also says that if the LAC
> has not sent the Sequencing Required AVP, the LNS is free to
> dyanmically enable or disable sequencing. 

That is correct. It had both.

> Perhaps the LAC I am using is
> interpreting this to mean that since RWS AVP has not been sent by
> either peer there is no sequencing involved and thus the LNS cannot
> enable it - it can only disable sequencing if already enabled and
> re-enable it.

No, you had it right the first time.

> 
> If the LAC is behaving correctly, how do I deal with this situation?.
> I thought of sending an ICRP with the RWS AVP with RW=0 but that
> would make me behave like a draft12 LNS.

Depends on how important it is for you to work with this LAC, and/or how
willing they are to change. You are in the "right" given the current
RFC, as well as draft 12. But, if you want to work with them now and
have no other course, it is fairly safe to send the RWS AVP=0 as most
implementations are aware of its existance. If you do this, I would
suggest being able to configure this mode on/off in the hopes of not
needing it one day.

- Mark

> 
> Thanks,
> 
> Pradeep.
> 
> __________________________________________________
> Do You Yahoo!?
> Talk to your friends online with Yahoo! Messenger.
> http://im.yahoo.com


From owner-l2tp@ipsec.org  Tue Feb 29 07:34:07 2000
Received: from www.sailpix.com (mail2.sailpix.com [155.53.200.203])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15702
	for <l2tpext-archive@odin.ietf.org>; Tue, 29 Feb 2000 07:34:06 -0500 (EST)
Received: (from majordomo@localhost) by www.sailpix.com (8.8.8/8.6.9) id DAA22337; Tue, 29 Feb 2000 03:27:21 -0800 (PST)
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www.sailpix.com (8.8.8/8.6.9) with ESMTP id DAA22333 for <l2tp@ipsec.org>; Tue, 29 Feb 2000 03:26:50 -0800 (PST)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA14863;
	Tue, 29 Feb 2000 06:26:48 -0500 (EST)
Message-Id: <200002291126.GAA14863@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-sesinfo-01.txt
Date: Tue, 29 Feb 2000 06:26:48 -0500
Sender: owner-l2tp@sailpix.com
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		: L2TP Session Information (``SESINFO'')
	Author(s)	: W. Palter
	Filename	: draft-ietf-l2tpext-sesinfo-01.txt
	Pages		: 4
	Date		: 28-Feb-00
	
The Layer 2 Tunneling Protocol ('L2TP') [1] defines a mechanism for
tunneling PPP sessions.  The current RFC is lacking a way for the LAC
to provide the LNS with data about the PPP session which can be
useful for accounting and debugging purposes. This is especially a
problem when the session transverses several L2TP tunnels before it
is finally terminated (sometimes called 'tunnel switching' or
'Multihop'). This draft provides additional AVPs that MAY be used to
provide port type and port identication information to the
terminating LNS, for accounting and debugging use.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-l2tpext-sesinfo-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-sesinfo-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-sesinfo-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:	<20000228125630.I-D@ietf.org>

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

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

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

--OtherAccess--

--NextPart--




