From owner-l2tp@ipsec.org  Thu Jun  1 13:11:08 2000
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27702
	for <l2tpext-archive@odin.ietf.org>; Thu, 1 Jun 2000 13:11:07 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns1.sailpix.com (8.8.8/8.6.9) id GAA06958; Thu, 1 Jun 2000 06:40:38 -0700 (PDT)
Received: from baynet.baynetworks.com (ns1.BayNetworks.COM [134.177.3.20]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id GAA06951 for <l2tp@ipsec.org>; Thu, 1 Jun 2000 06:39:18 -0700 (PDT)
Received: from mailhost.BayNetworks.COM (h016b.s86b1.BayNetworks.COM [134.177.1.107])
	by baynet.baynetworks.com (8.9.1/8.9.1) with ESMTP id JAA16317;
	Thu, 1 Jun 2000 09:01:02 -0700 (PDT)
Received: from shasta-exch.shastanets.com (mailserver.shastanets.com [47.82.16.150])
	by mailhost.BayNetworks.COM (8.9.1/8.8.8) with ESMTP id JAA20324;
	Thu, 1 Jun 2000 09:01:00 -0700 (PDT)
Received: by mailserver.shastanets.com with Internet Mail Service (5.5.2650.21)
	id <L0A5R11Q>; Thu, 1 Jun 2000 09:02:17 -0700
Message-ID: <4DEC824F6F1FD3119BEF0000E86CEA0101E497BD@mailserver.shastanets.com>
From: Ly Loi <LLL@shastanets.com>
To: "'gwz@cisco.com'" <gwz@cisco.com>, Ly Loi <LLL@shastanets.com>,
        "'Skip Booth'" <ebooth@cisco.com>
Cc: aboba@internaut.com, l2tp@ipsec.org, wdixon@MICROSOFT.com,
        townsley@cisco.com
Subject: RE: Comments/questions to l2tp over ipsec draft
Date: Thu, 1 Jun 2000 09:02:15 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-l2tp@ipsec.org
Precedence: bulk

Glen, in my drawing, the LNS and the IPSEC tunnel terminator reside on the
same box. What is your point?
Mine is regarding covering this scenario in the draft. I believe we all
agree that L2TP over IPSEC is run with ipsec in transport mode if the l2tp
tunnel initiator resides on the same box as the ipsec initiator, but ipsec
is run in tunnel mode if they aren't on the box. So why not also cover the
latter in the draft? Sure, as you pointed out, the draft shouldn't cover all
the possible scenarios, but it could cover the most common ones. I believe
that the scenario I've described below is quite common.

- Ly

> -----Original Message-----
> From: Glen Zorn [mailto:gwz@cisco.com]
> Sent: Wednesday, May 31, 2000 5:36 PM
> To: Ly Loi; 'Skip Booth'
> Cc: aboba@internaut.com; l2tp@ipsec.org; wdixon@MICROSOFT.com;
> townsley@cisco.com
> Subject: RE: Comments/questions to l2tp over ipsec draft
> 
> 
> Ly Loi [mailto:LLL@shastanets.com] writes:
> 
> > Glen, the LNS is the tunnel terminator; e.g. the security gateway.
> 
> An LNS doesn't terminate IPSEC tunnels, though.  The LNS and "Security
> Gateway" may reside on the same box, but they are logically 
> distinct, right?
> 
> >
> > - Ly
> >
> > > -----Original Message-----
> > > From: Glen Zorn [mailto:gwz@cisco.com]
> > > Sent: Saturday, May 27, 2000 11:16 AM
> > > To: Ly Loi; 'Skip Booth'
> > > Cc: aboba@internaut.com; l2tp@ipsec.org; wdixon@MICROSOFT.com;
> > > townsley@cisco.com; Glen Zorn
> > > Subject: RE: Comments/questions to l2tp over ipsec draft
> > >
> > >
> > > Ly Loi [mailto://LLL@shastanets.com] writes:
> > >
> > > > Skip, security between the client and the LAC isn't what I was
> > > > referring to.
> > > > In my scenario, the PPP and the LAC can reside on the box,
> > > or different
> > > > boxes. However, the LAC doesn't reside on the same box as
> > > the IPSEC tunnel
> > > > initiator.
> > > > To be more specific, what I have in mind is a group of LACs
> > > > sharing 1 IPSEC
> > > > SA. This IPSEC SA is between the gateway and the LNS.
> > > >
> > > > LAC1---------gateway------------ipsec_tunnel--------------LNS
> > > > LAC2-----------|
> > > > LAC3-----------|
> > >
> > > It appears that you are missing a "security gateway" at 
> the LNS end.
> > >
> > > >
> > > > Unlike the cases covered by the draft where each L2TP tunnel is
> > > > mapped to an
> > > > IPSEC SA, here, multiple L2TP tunnels map to one IPSEC SA.
> > > If the draft
> > > > could also cover this case, it'd be more complete.
> > >
> > > I don't think that the point of the draft is to present an
> > > exhaustive list
> > > of every method (no  matter how lame) that can be used to
> > > "secure" L2TP
> > > tunnels.
> > >
> > > >
> > > > A few more comments:
> > > >
> > > > 1. Could you not require that L2TP start the 
> retransmission timer
> > > > only after
> > > > the IPSEC SA has come up (section 9.2.2)? I stated the reason in
> > > > my original
> > > > email. In addition, in the above scenario, this requirement
> > > wouldn't be
> > > > applicable.
> > > >
> > > > 2. The draft lists the IPSEC filters as if they represent
> > > both the IPSEC
> > > > policies and the IPSEC SAs, which is rather confusing since
> > > IPSEC SAs are
> > > > derived from IPSEC policies. If you could decouple them in
> > > your examples,
> > > > it'd be great.
> > > >
> > > > 3. I don't know how others feel about having an external entity
> > > > (e.g. L2TP)
> > > > injecting some filters into the IPSEC policy database, but
> > > this appears to
> > > > me to be a local implementation issue. Also, this wouldn't
> > > be feasible for
> > > > the above scenario. I however appreciate the problems the draft
> > > > is trying to
> > > > solve.
> > > >
> > > > Thanks,
> > > >
> > > > - Ly
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: Skip Booth [mailto:ebooth@cisco.com]
> > > > > Sent: Friday, May 26, 2000 12:36 PM
> > > > > To: Ly Loi
> > > > > Cc: 'aboba@internaut.com'; l2tp@ipsec.org; gwz@cisco.com;
> > > > > wdixon@MICROSOFT.com; townsley@cisco.com
> > > > > Subject: RE: Comments/questions to l2tp over ipsec draft
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On Fri, 26 May 2000, Ly Loi wrote:
> > > > >
> > > > > > Skip, I was referring to the case where the LAC and the
> > > ipsec tunnel
> > > > > > initiator didn't reside on the same device:
> > > > > > LAC---gateway(ipsec tunnel
> > > initiator)---------------LNS(ipsec tunnel
> > > > > > terminator)
> > > > > >
> > > > > > Is the draft supposed to cover this case too? This case
> > > > > would be considered
> > > > > > compulsory tunneling, ipsec tunneling :-)
> > > > >
> > > > > The draft discusses security concerns in the compulsory
> > > > > model.  Specifically, it
> > > > > talks about how the link between the client and the LAC is
> > > > > potentially not
> > > > > secure and that clients may require end to end security.  If
> > > > > the client is
> > > > > running end to end security than potentially no encryption is
> > > > > required for L2TP
> > > > > data packets between the LAC and LNS, but authentication may
> > > > > be.  As you noted
> > > > > however, currently there is no way standardized method
> > > for IPsec to
> > > > > differentiate between L2TP data and control packets.
> > > > >
> > > > > Does the draft need to go into more detail in this area?  If
> > > > > so what more would
> > > > > you like to be discussed?
> > > > >
> > > > > > If L2TP and IPSEC reside on the same device, then yes, we
> > > > > all agree IPSEC
> > > > > > would run in transport mode and I trust this will be stated
> > > > > in a future
> > > > > > version of the draft, thanks.
> > > > >
> > > > > Yes.
> > > > >
> > > > > -Skip
> > > > >
> > > > > >
> > > > > > - Ly
> > > > > >
> > > > >
> > > > > [rest of text snipped]
> > > > >
> > > >
> > > >
> > >
> >
> >
> 


From owner-l2tp@ipsec.org  Thu Jun  1 15:22:32 2000
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01336
	for <l2tpext-archive@odin.ietf.org>; Thu, 1 Jun 2000 15:22:31 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns1.sailpix.com (8.8.8/8.6.9) id JAA07138; Thu, 1 Jun 2000 09:04:00 -0700 (PDT)
Received: from uzura.cisco.com (uzura.cisco.com [161.44.3.77]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id JAA07133 for <l2tp@ipsec.org>; Thu, 1 Jun 2000 09:02:35 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by uzura.cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id OAA25709;
	Thu, 1 Jun 2000 14:21:03 -0400 (EDT)
Date: Thu, 1 Jun 2000 14:21:03 -0400 (EDT)
From: Skip Booth <ebooth@cisco.com>
To: Ly Loi <LLL@shastanets.com>
cc: "'gwz@cisco.com'" <gwz@cisco.com>, aboba@internaut.com, l2tp@ipsec.org,
        wdixon@MICROSOFT.com, townsley@cisco.com
Subject: RE: Comments/questions to l2tp over ipsec draft
In-Reply-To: <4DEC824F6F1FD3119BEF0000E86CEA0101E497BD@mailserver.shastanets.com>
Message-ID: <Pine.GSO.4.10.10006011418290.24927-100000@uzura.cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-l2tp@ipsec.org
Precedence: bulk



On Thu, 1 Jun 2000, Ly Loi wrote:

> Glen, in my drawing, the LNS and the IPSEC tunnel terminator reside on the
> same box. What is your point?
> Mine is regarding covering this scenario in the draft. I believe we all
> agree that L2TP over IPSEC is run with ipsec in transport mode if the l2tp
> tunnel initiator resides on the same box as the ipsec initiator, but ipsec
> is run in tunnel mode if they aren't on the box. So why not also cover the
> latter in the draft? Sure, as you pointed out, the draft shouldn't cover all
> the possible scenarios, but it could cover the most common ones. I believe
> that the scenario I've described below is quite common.

I don't think this is scenario we should cover since this has security holes in
it.  The L2TP tunnel(s) are unprotected between the LAC and the first Security
Gateway and thus this scenario should not be considered in the L2TP Security
draft.  To protect L2TP sufficiently (end to end), IPsec MUST run on the LAC and
the LNS.

-Skip

> 
> - Ly
> 
> > -----Original Message-----
> > From: Glen Zorn [mailto:gwz@cisco.com]
> > Sent: Wednesday, May 31, 2000 5:36 PM
> > To: Ly Loi; 'Skip Booth'
> > Cc: aboba@internaut.com; l2tp@ipsec.org; wdixon@MICROSOFT.com;
> > townsley@cisco.com
> > Subject: RE: Comments/questions to l2tp over ipsec draft
> > 
> > 
> > Ly Loi [mailto:LLL@shastanets.com] writes:
> > 
> > > Glen, the LNS is the tunnel terminator; e.g. the security gateway.
> > 
> > An LNS doesn't terminate IPSEC tunnels, though.  The LNS and "Security
> > Gateway" may reside on the same box, but they are logically 
> > distinct, right?
> > 
> > >
> > > - Ly
> > >
> > > > -----Original Message-----
> > > > From: Glen Zorn [mailto:gwz@cisco.com]
> > > > Sent: Saturday, May 27, 2000 11:16 AM
> > > > To: Ly Loi; 'Skip Booth'
> > > > Cc: aboba@internaut.com; l2tp@ipsec.org; wdixon@MICROSOFT.com;
> > > > townsley@cisco.com; Glen Zorn
> > > > Subject: RE: Comments/questions to l2tp over ipsec draft
> > > >
> > > >
> > > > Ly Loi [mailto://LLL@shastanets.com] writes:
> > > >
> > > > > Skip, security between the client and the LAC isn't what I was
> > > > > referring to.
> > > > > In my scenario, the PPP and the LAC can reside on the box,
> > > > or different
> > > > > boxes. However, the LAC doesn't reside on the same box as
> > > > the IPSEC tunnel
> > > > > initiator.
> > > > > To be more specific, what I have in mind is a group of LACs
> > > > > sharing 1 IPSEC
> > > > > SA. This IPSEC SA is between the gateway and the LNS.
> > > > >
> > > > > LAC1---------gateway------------ipsec_tunnel--------------LNS
> > > > > LAC2-----------|
> > > > > LAC3-----------|
> > > >
> > > > It appears that you are missing a "security gateway" at 
> > the LNS end.
> > > >
> > > > >
> > > > > Unlike the cases covered by the draft where each L2TP tunnel is
> > > > > mapped to an
> > > > > IPSEC SA, here, multiple L2TP tunnels map to one IPSEC SA.
> > > > If the draft
> > > > > could also cover this case, it'd be more complete.
> > > >
> > > > I don't think that the point of the draft is to present an
> > > > exhaustive list
> > > > of every method (no  matter how lame) that can be used to
> > > > "secure" L2TP
> > > > tunnels.
> > > >
> > > > >
> > > > > A few more comments:
> > > > >
> > > > > 1. Could you not require that L2TP start the 
> > retransmission timer
> > > > > only after
> > > > > the IPSEC SA has come up (section 9.2.2)? I stated the reason in
> > > > > my original
> > > > > email. In addition, in the above scenario, this requirement
> > > > wouldn't be
> > > > > applicable.
> > > > >
> > > > > 2. The draft lists the IPSEC filters as if they represent
> > > > both the IPSEC
> > > > > policies and the IPSEC SAs, which is rather confusing since
> > > > IPSEC SAs are
> > > > > derived from IPSEC policies. If you could decouple them in
> > > > your examples,
> > > > > it'd be great.
> > > > >
> > > > > 3. I don't know how others feel about having an external entity
> > > > > (e.g. L2TP)
> > > > > injecting some filters into the IPSEC policy database, but
> > > > this appears to
> > > > > me to be a local implementation issue. Also, this wouldn't
> > > > be feasible for
> > > > > the above scenario. I however appreciate the problems the draft
> > > > > is trying to
> > > > > solve.
> > > > >
> > > > > Thanks,
> > > > >
> > > > > - Ly
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Skip Booth [mailto:ebooth@cisco.com]
> > > > > > Sent: Friday, May 26, 2000 12:36 PM
> > > > > > To: Ly Loi
> > > > > > Cc: 'aboba@internaut.com'; l2tp@ipsec.org; gwz@cisco.com;
> > > > > > wdixon@MICROSOFT.com; townsley@cisco.com
> > > > > > Subject: RE: Comments/questions to l2tp over ipsec draft
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Fri, 26 May 2000, Ly Loi wrote:
> > > > > >
> > > > > > > Skip, I was referring to the case where the LAC and the
> > > > ipsec tunnel
> > > > > > > initiator didn't reside on the same device:
> > > > > > > LAC---gateway(ipsec tunnel
> > > > initiator)---------------LNS(ipsec tunnel
> > > > > > > terminator)
> > > > > > >
> > > > > > > Is the draft supposed to cover this case too? This case
> > > > > > would be considered
> > > > > > > compulsory tunneling, ipsec tunneling :-)
> > > > > >
> > > > > > The draft discusses security concerns in the compulsory
> > > > > > model.  Specifically, it
> > > > > > talks about how the link between the client and the LAC is
> > > > > > potentially not
> > > > > > secure and that clients may require end to end security.  If
> > > > > > the client is
> > > > > > running end to end security than potentially no encryption is
> > > > > > required for L2TP
> > > > > > data packets between the LAC and LNS, but authentication may
> > > > > > be.  As you noted
> > > > > > however, currently there is no way standardized method
> > > > for IPsec to
> > > > > > differentiate between L2TP data and control packets.
> > > > > >
> > > > > > Does the draft need to go into more detail in this area?  If
> > > > > > so what more would
> > > > > > you like to be discussed?
> > > > > >
> > > > > > > If L2TP and IPSEC reside on the same device, then yes, we
> > > > > > all agree IPSEC
> > > > > > > would run in transport mode and I trust this will be stated
> > > > > > in a future
> > > > > > > version of the draft, thanks.
> > > > > >
> > > > > > Yes.
> > > > > >
> > > > > > -Skip
> > > > > >
> > > > > > >
> > > > > > > - Ly
> > > > > > >
> > > > > >
> > > > > > [rest of text snipped]
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> > >
> > 
> 
> 



From owner-l2tp@ipsec.org  Thu Jun  1 17:23:46 2000
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04181
	for <l2tpext-archive@odin.ietf.org>; Thu, 1 Jun 2000 17:23:45 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns1.sailpix.com (8.8.8/8.6.9) id KAA07276; Thu, 1 Jun 2000 10:41:36 -0700 (PDT)
Received: from databus.databus.com (databus.databus.com [198.186.154.34]) by ns1.sailpix.com (8.8.8/8.6.9) with SMTP id KAA07272 for <l2tp@ipsec.org>; Thu, 1 Jun 2000 10:41:21 -0700 (PDT)
From: Barney Wolff <barney@databus.com>
To: l2tp@ipsec.org
Date: Thu, 1 Jun 2000 15:56 EDT
Subject: RE: Comments/questions to l2tp over ipsec draft
Content-Type: text/plain
Message-ID: <3936c1f80.4908@databus.databus.com>
Sender: owner-l2tp@ipsec.org
Precedence: bulk

This is the right answer, but the wrong reason.  If the two end nets
are secure, but connected by an insecure path, tunnel mode may be
all that's needed and perfectly appropriate.  But if it's not something
the LAC or LNS are themselves doing, IPsec becomes just like a link
encryptor that works transparently, with the two ends being unaware
of it.  Of course if the SG's don't operate transparently, such as
by not passing UDP at all or restricting it to port 1701, then things
may not work.  But this is the L2TP-thru-the-firewall scenario, not
something unique to IPsec.

Barney Wolff

> Date: Thu, 1 Jun 2000 14:21:03 -0400 (EDT)
> From: Skip Booth <ebooth@cisco.com>
> 
> I don't think this is scenario we should cover since this has security holes in
> it.  The L2TP tunnel(s) are unprotected between the LAC and the first Security
> Gateway and thus this scenario should not be considered in the L2TP Security
> draft.  To protect L2TP sufficiently (end to end), IPsec MUST run on the LAC and
> the LNS.


From owner-l2tp@ipsec.org  Fri Jun  2 08:54:00 2000
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA01069
	for <l2tpext-archive@odin.ietf.org>; Fri, 2 Jun 2000 08:53:58 -0400 (EDT)
Received: (from majordomo@localhost) by ns1.sailpix.com (8.8.8/8.6.9) id BAA08297; Fri, 2 Jun 2000 01:19:32 -0700 (PDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id BAA08293 for <l2tp@ipsec.org>; Fri, 2 Jun 2000 01:18:53 -0700 (PDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA27487;
	Fri, 2 Jun 2000 06:42:45 -0400 (EDT)
Message-Id: <200006021042.GAA27487@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-ppp-discinfo-00.txt
Date: Fri, 02 Jun 2000 06:42:44 -0400
Sender: owner-l2tp@ipsec.org
Precedence: bulk

--NextPart

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

	Title		: L2TP Disconnect Cause Information
	Author(s)	: R. Verma, M. Verma, J. Carlson
	Filename	: draft-ietf-l2tpext-ppp-discinfo-00.txt
	Pages		: 8
	Date		: 01-Jun-00
	
The Layer 2 Tunneling Protocol ('L2TP') defines a mechanism for
tunneling PPP sessions.  The current RFC lacks a mechanism for the
LNS to provide PPP related disconnect cause information to the LAC.
This information, provided by the extension described in this
document, can be useful for accounting and debugging purposes.

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

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

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

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

--OtherAccess--

--NextPart--




From owner-l2tp@ipsec.org  Tue Jun  6 09:58:33 2000
Received: from ns1.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04536
	for <l2tpext-archive@odin.ietf.org>; Tue, 6 Jun 2000 09:58:32 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns1.sailpix.com (8.8.8/8.6.9) id BAA18769; Tue, 6 Jun 2000 01:26:38 -0700 (PDT)
Received: from michael.checkpoint.com (michael.checkpoint.com [199.203.73.68]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id BAA18765 for <l2tp@ipsec.org>; Tue, 6 Jun 2000 01:26:18 -0700 (PDT)
Received: from yago (localhost [127.0.0.1])
	by michael.checkpoint.com (8.9.3/8.9.1) with SMTP id NAA17254
	for <l2tp@ipsec.org>; Tue, 6 Jun 2000 13:49:12 +0300 (IDT)
From: "Keren Epstein" <keren@checkpoint.com>
To: <l2tp@ipsec.org>
Subject: L2TP configuration problems
Date: Tue, 6 Jun 2000 13:50:50 +0200
Message-ID: <000101bfcfad$76a5c350$2d8d96d4@checkpoint.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 8.5, Build 4.71.2173.0
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hello,

I'm a beginner with L2TP... so I guess I'm confronting very trivial
problems:

I have w2k Professional and w2k Server configured to do L2TP, using LAN
connection and no IPSEC.

I configured a static IP address pool on the server, but when the client
tries to connect:
TCP/IP CP reported error 52: A duplicate name exists on the network.

What am I doing wrong? Any help would be great!

Keren







From owner-l2tp@ipsec.org  Tue Jun  6 11:13:03 2000
Received: from ns1.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09620
	for <l2tpext-archive@odin.ietf.org>; Tue, 6 Jun 2000 11:13:03 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns1.sailpix.com (8.8.8/8.6.9) id EAA20212; Tue, 6 Jun 2000 04:34:13 -0700 (PDT)
Received: from sj-msg-core-2.cisco.com (sj-msg-core-2.cisco.com [171.69.43.88]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id EAA20208 for <l2tp@ipsec.org>; Tue, 6 Jun 2000 04:33:55 -0700 (PDT)
Received: from townsley-ultra.cisco.com (townsley-ultra.cisco.com [161.44.58.38])
	by sj-msg-core-2.cisco.com (8.9.3/8.9.1) with ESMTP id GAA20339;
	Tue, 6 Jun 2000 06:57:32 -0700 (PDT)
Received: from cisco.com (townsley-home.cisco.com [161.44.99.50]) by townsley-ultra.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) with ESMTP id JAA25677; Tue, 6 Jun 2000 09:57:23 -0400 (EDT)
Message-ID: <393D0332.2815CB33@cisco.com>
Date: Tue, 06 Jun 2000 09:57:06 -0400
From: "W. Mark Townsley" <townsley@cisco.com>
Organization: cisco Systems
X-Mailer: Mozilla 4.7 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Keren Epstein <keren@checkpoint.com>
CC: l2tp@ipsec.org
Subject: Re: L2TP configuration problems
References: <000101bfcfad$76a5c350$2d8d96d4@checkpoint.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Please direct operational questions about Windows 2000 to Microsoft. The
following resource has been identified as the proper place for this:

"The news group for Windows 2000 networking functionality in general is:
microsoft.public.win2000.networking"

Thanks,

- Mark

Keren Epstein wrote:
> 
> Hello,
> 
> I'm a beginner with L2TP... so I guess I'm confronting very trivial
> problems:
> 
> I have w2k Professional and w2k Server configured to do L2TP, using LAN
> connection and no IPSEC.
> 
> I configured a static IP address pool on the server, but when the client
> tries to connect:
> TCP/IP CP reported error 52: A duplicate name exists on the network.
> 
> What am I doing wrong? Any help would be great!
> 
> Keren


From owner-l2tp@ipsec.org  Tue Jun  6 19:27:39 2000
Received: from ns1.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA20559
	for <l2tpext-archive@odin.ietf.org>; Tue, 6 Jun 2000 19:27:38 -0400 (EDT)
Received: (from majordomo@localhost) by ns1.sailpix.com (8.8.8/8.6.9) id NAA20784; Tue, 6 Jun 2000 13:15:43 -0700 (PDT)
Received: from fcs-nt1.futsoft.com (fcs-nt1.futsoft.com [38.242.189.2]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id NAA20780 for <l2tp@ipsec.org>; Tue, 6 Jun 2000 13:15:30 -0700 (PDT)
Received: from sanjose.futsoft.com (unverified) by fcs-nt1.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with SMTP id <B0000058348@fcs-nt1.futsoft.com> for <l2tp@ipsec.org>;
 Tue, 06 Jun 2000 15:26:12 -0700
Received: from localhost (rajeshs@localhost)
	by sanjose.futsoft.com (8.9.3/8.8.7) with ESMTP id OAA15145
	for <l2tp@ipsec.org>; Tue, 6 Jun 2000 14:34:07 -0700
Date: Tue, 6 Jun 2000 14:34:07 -0700 (PDT)
From: "S.Rajesh Kumar" <rajeshs@futsoft.com>
To: l2tp@ipsec.org
Subject: L2TP link extensions
Message-Id: <Pine.LNX.4.10.10006061429330.15129-100000@sanjose.futsoft.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-l2tp@ipsec.org
Precedence: bulk

The "L2TP link extensions (draft-ietf-l2tpext-link-00.txt) defines
AVPs for the LAC to influence LCP parameters negotiated by the LNS.
Pardon my ignorance, but - What is the use of this? If the LAC has
the parameters that it wants negotiated on the PPP session, the LAC
could do proxy-LCP to ensure that these are used? Why is it necessary
to make the LNS negotiate these parameters?

Also - why should the LAC influence the parameters negotiated by the
LNS?

Thanks in advance for the clarification
Rajesh



From owner-l2tp@ipsec.org  Tue Jun  6 20:52:54 2000
Received: from ns1.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA21317
	for <l2tpext-archive@odin.ietf.org>; Tue, 6 Jun 2000 20:52:53 -0400 (EDT)
Received: (from majordomo@localhost) by ns1.sailpix.com (8.8.8/8.6.9) id OAA20927; Tue, 6 Jun 2000 14:36:35 -0700 (PDT)
Received: from h006008986325.ne.mediaone.net (h006008986325.ne.mediaone.net [24.218.16.153]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id OAA20923 for <l2tp@ipsec.org>; Tue, 6 Jun 2000 14:36:16 -0700 (PDT)
Received: (from carlson@localhost)
	by h006008986325.ne.mediaone.net (8.9.3/8.9.3) id UAA09056;
	Tue, 6 Jun 2000 20:00:13 -0400
From: James Carlson <carlson@workingcode.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14653.37004.686531.397292@h006008986325.ne.mediaone.net>
Date: Tue, 6 Jun 2000 20:00:12 -0400 (EDT)
To: "S.Rajesh Kumar" <rajeshs@futsoft.com>
Cc: l2tp@ipsec.org
Subject: Re: L2TP link extensions
In-Reply-To: S.Rajesh Kumar's message of 6 June 2000 14:34:07
References: <Pine.LNX.4.10.10006061429330.15129-100000@sanjose.futsoft.com>
X-Mailer: VM 6.75 under Emacs 20.6.1
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

S.Rajesh Kumar writes:
> The "L2TP link extensions (draft-ietf-l2tpext-link-00.txt) defines
> AVPs for the LAC to influence LCP parameters negotiated by the LNS.
> Pardon my ignorance, but - What is the use of this? If the LAC has
> the parameters that it wants negotiated on the PPP session, the LAC
> could do proxy-LCP to ensure that these are used?

Right; if the LAC is filtering the LCP options and mediating the
negotiation, then there's no reason at all for the SLI.

> Why is it necessary
> to make the LNS negotiate these parameters?

There are some who believe that the LAC should pass all LCP frames
unmolested and that the LNS should therefore have intimate
understanding of (or at least tolerance for) the vagaries of the link
types that all of the LACs support.  But that's just my reading.  ;-}

> Also - why should the LAC influence the parameters negotiated by the
> LNS?

If the LNS is doing LCP on behalf of the LAC, then it will need this
information to set link-related parameters correctly.

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


From owner-l2tp@ipsec.org  Tue Jun  6 21:51:08 2000
Received: from ns1.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA22525
	for <l2tpext-archive@odin.ietf.org>; Tue, 6 Jun 2000 21:51:08 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns1.sailpix.com (8.8.8/8.6.9) id PAA21027; Tue, 6 Jun 2000 15:38:59 -0700 (PDT)
Received: from claret.cisco.com (claret.cisco.com [161.44.3.78]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id PAA21023 for <l2tp@ipsec.org>; Tue, 6 Jun 2000 15:38:33 -0700 (PDT)
Received: from cisco.com (rtp7-dhcp-58-147.cisco.com [161.44.58.147]) by claret.cisco.com (8.8.4-Cisco.1/8.6.5) with ESMTP id VAA01400; Tue, 6 Jun 2000 21:01:53 -0400 (EDT)
Message-ID: <393D9EFF.8CC3AB19@cisco.com>
Date: Tue, 06 Jun 2000 21:01:51 -0400
From: "W. Mark Townsley" <townsley@cisco.com>
X-Mailer: Mozilla 4.7 [en] (Win95; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: James Carlson <carlson@workingcode.com>
CC: "S.Rajesh Kumar" <rajeshs@futsoft.com>, l2tp@ipsec.org
Subject: Re: L2TP link extensions
References: <Pine.LNX.4.10.10006061429330.15129-100000@sanjose.futsoft.com> <14653.37004.686531.397292@h006008986325.ne.mediaone.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



James Carlson wrote:
> 
> S.Rajesh Kumar writes:
> > The "L2TP link extensions (draft-ietf-l2tpext-link-00.txt) defines
> > AVPs for the LAC to influence LCP parameters negotiated by the LNS.
> > Pardon my ignorance, but - What is the use of this? If the LAC has
> > the parameters that it wants negotiated on the PPP session, the LAC
> > could do proxy-LCP to ensure that these are used?
> 
> Right; if the LAC is filtering the LCP options and mediating the
> negotiation, then there's no reason at all for the SLI.

Big "if"

> 
> > Why is it necessary
> > to make the LNS negotiate these parameters?
> 
> There are some who believe that the LAC should pass all LCP frames
> unmolested and that the LNS should therefore have intimate
> understanding of (or at least tolerance for) the vagaries of the link
> types that all of the LACs support.  But that's just my reading.  ;-}

It is reality as well. It was an original design constraint that the LAC
not need to be cognizant of contents of the packets it is tunneling once
the L2TP session is up.

> 
> > Also - why should the LAC influence the parameters negotiated by the
> > LNS?
> 
> If the LNS is doing LCP on behalf of the LAC, then it will need this
> information to set link-related parameters correctly.

It *could* need this information in some cases, so link-info exists to
identify a standard and extensible method for packaging this information
(rather than in individual AVPs, as is done with the current ACCM format
in the SLI). 

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


From owner-l2tp@ipsec.org  Wed Jun  7 11:43:17 2000
Received: from ns1.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13559
	for <l2tpext-archive@odin.ietf.org>; Wed, 7 Jun 2000 11:43:16 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns1.sailpix.com (8.8.8/8.6.9) id EAA23283; Wed, 7 Jun 2000 04:52:24 -0700 (PDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id EAA23279 for <l2tp@ipsec.org>; Wed, 7 Jun 2000 04:51:43 -0700 (PDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10987;
	Wed, 7 Jun 2000 10:15:30 -0400 (EDT)
Message-Id: <200006071415.KAA10987@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-nanji-l2tp-eth-00.txt
Date: Wed, 07 Jun 2000 10:15:29 -0400
Sender: owner-l2tp@ipsec.org
Precedence: bulk

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: Ethernet Encapsulation Extensions to Layer Two 
                          Tunneling Protocol
	Author(s)	: S. Nanji
	Filename	: draft-nanji-l2tp-eth-00.txt
	Pages		: 5
	Date		: 06-Jun-00
	
The Layer Two Tunneling Protocol (L2TP) [1] provides a standard
method for tunneling PPP [2] packets.  This document describes an
extension to L2TP which will allows for Ethernet frames to be
transported over a session in an L2TP tunnel.  These extensions
provide added functionality, but are optional and preserve
compatibility.  Also, the same tunnel SHALL carry both PPP and
Ethernet L2TP sessions if needed.

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

ENCODING mime
FILE /internet-drafts/draft-nanji-l2tp-eth-00.txt

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

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

--OtherAccess--

--NextPart--




From owner-l2tp@ipsec.org  Wed Jun  7 12:57:51 2000
Received: from ns1.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15909
	for <l2tpext-archive@odin.ietf.org>; Wed, 7 Jun 2000 12:57:50 -0400 (EDT)
Received: (from majordomo@localhost) by ns1.sailpix.com (8.8.8/8.6.9) id FAA23368; Wed, 7 Jun 2000 05:35:31 -0700 (PDT)
Received: from lukla.Sun.COM (lukla.Sun.COM [192.18.98.31]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id FAA23364 for <l2tp@ipsec.org>; Wed, 7 Jun 2000 05:35:18 -0700 (PDT)
Received: from eastmail1.East.Sun.COM ([129.148.1.240])
	by lukla.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id IAA11862
	for <l2tp@ipsec.org>; Wed, 7 Jun 2000 08:59:12 -0600 (MDT)
Received: from phorcys.east.sun.com (phorcys.East.Sun.COM [129.148.174.143])
	by eastmail1.East.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id KAA25835
	for <l2tp@ipsec.org>; Wed, 7 Jun 2000 10:59:11 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.9.3+Sun/8.9.3) id KAA01104;
	Wed, 7 Jun 2000 10:59:11 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14654.25407.129031.333557@gargle.gargle.HOWL>
Date: Wed, 7 Jun 2000 10:59:11 -0400 (EDT)
From: James Carlson <james.d.carlson@east.sun.com>
To: l2tp@ipsec.org
Subject: Re: I-D ACTION:draft-nanji-l2tp-eth-00.txt
In-Reply-To: Internet-Drafts@ietf.org's message of 7 June 2000 10:15:29
References: <200006071415.KAA10987@ietf.org>
X-Mailer: VM 6.75 under Emacs 20.6.1
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

> 	Title		: Ethernet Encapsulation Extensions to Layer Two 
>                           Tunneling Protocol

Two questions: doesn't BCP over PPP already provide a well-defined,
standards-track superset of this functionality?  Shouldn't this draft
at least reference BCP and indicate why the currently used mechanisms
for bridging over point-to-point links are insufficient?

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


From owner-l2tp@ipsec.org  Thu Jun  8 20:00:22 2000
Received: from ns1.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA19327
	for <l2tpext-archive@odin.ietf.org>; Thu, 8 Jun 2000 20:00:21 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns1.sailpix.com (8.8.8/8.6.9) id NAA26900; Thu, 8 Jun 2000 13:12:54 -0700 (PDT)
Received: from fcs-nt1.futsoft.com (fcs-nt1.futsoft.com [38.242.189.2]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id NAA26896 for <l2tp@ipsec.org>; Thu, 8 Jun 2000 13:12:42 -0700 (PDT)
Received: from sanjose.futsoft.com (unverified) by fcs-nt1.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with SMTP id <B0000059608@fcs-nt1.futsoft.com> for <l2tp@ipsec.org>;
 Thu, 08 Jun 2000 15:23:15 -0700
Received: from localhost (rajeshs@localhost)
	by sanjose.futsoft.com (8.9.3/8.8.7) with ESMTP id OAA23943
	for <l2tp@ipsec.org>; Thu, 8 Jun 2000 14:31:05 -0700
Date: Thu, 8 Jun 2000 14:31:05 -0700 (PDT)
From: "S.Rajesh Kumar" <rajeshs@futsoft.com>
To: l2tp@ipsec.org
Subject: data packet length in l2tp
Message-Id: <Pine.LNX.4.10.10006081427470.23924-100000@sanjose.futsoft.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-l2tp@ipsec.org
Precedence: bulk

L2tp data packets may or may not have a length field.
In the absence of a length field, how does an implementation
working over say BSD 4.3 udp sockets, find the length of a
data packet? And then read in a complete packet?

An approach of reading in avp by avp (since length of each avp
element is specified) sounds pretty slow....

Thanks
Rajesh



From owner-l2tp@ipsec.org  Thu Jun  8 20:08:48 2000
Received: from ns1.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA19416
	for <l2tpext-archive@odin.ietf.org>; Thu, 8 Jun 2000 20:08:47 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns1.sailpix.com (8.8.8/8.6.9) id NAA26934; Thu, 8 Jun 2000 13:22:36 -0700 (PDT)
Received: from zev.net (zev.net [206.111.135.146]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id NAA26930 for <l2tp@ipsec.org>; Thu, 8 Jun 2000 13:22:23 -0700 (PDT)
Received: from zev.net (localhost.zev.net [127.0.0.1] (may be forged))
	by zev.net (8.9.3/8.9.3) with ESMTP id PAA03422;
	Thu, 8 Jun 2000 15:45:59 -0700 (PDT)
Message-Id: <200006082245.PAA03422@zev.net>
To: "S.Rajesh Kumar" <rajeshs@futsoft.com>
cc: l2tp@ipsec.org
Subject: Re: data packet length in l2tp 
In-reply-to: Your message of "Thu, 08 Jun 2000 14:31:05 PDT."
             <Pine.LNX.4.10.10006081427470.23924-100000@sanjose.futsoft.com> 
Date: Thu, 08 Jun 2000 15:45:59 -0700
From: Bill Palter <palter@zev.net>
Sender: owner-l2tp@ipsec.org
Precedence: bulk

> L2tp data packets may or may not have a length field.
> In the absence of a length field, how does an implementation
> working over say BSD 4.3 udp sockets, find the length of a
> data packet? And then read in a complete packet?
> 
> An approach of reading in avp by avp (since length of each avp
> element is specified) sounds pretty slow....
> 
> Thanks
> Rajesh

  UDP is record based, the read should give you the entire message....


--
Bill Palter (Palter@zev.net)


From owner-l2tp@ipsec.org  Thu Jun  8 20:28:39 2000
Received: from ns1.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA19521
	for <l2tpext-archive@odin.ietf.org>; Thu, 8 Jun 2000 20:28:39 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns1.sailpix.com (8.8.8/8.6.9) id OAA27040; Thu, 8 Jun 2000 14:00:18 -0700 (PDT)
Received: from fcs-nt1.futsoft.com (fcs-nt1.futsoft.com [38.242.189.2]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id OAA27036 for <l2tp@ipsec.org>; Thu, 8 Jun 2000 14:00:02 -0700 (PDT)
Received: from sanjose.futsoft.com (unverified) by fcs-nt1.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with SMTP id <B0000059622@fcs-nt1.futsoft.com> for <l2tp@ipsec.org>;
 Thu, 08 Jun 2000 16:10:33 -0700
Received: from localhost (rajeshs@localhost)
	by sanjose.futsoft.com (8.9.3/8.8.7) with ESMTP id PAA24118
	for <l2tp@ipsec.org>; Thu, 8 Jun 2000 15:18:23 -0700
Date: Thu, 8 Jun 2000 15:18:22 -0700 (PDT)
From: "S.Rajesh Kumar" <rajeshs@futsoft.com>
To: l2tp@ipsec.org
Subject: Regarding l2tp-mpls extension
Message-Id: <Pine.LNX.4.10.10006081517580.24047-100000@sanjose.futsoft.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-l2tp@ipsec.org
Precedence: bulk

Regarding l2tp-mpls extension:

The draft on l2tp-mpls-extension "draft-ietf-l2tpext-mpls-00"
proposes that the l2tp peers exchange an LSPID in a new AVP
defined for carrying the LSPID.

The objective is that L2TP Data Sessions can be assigned an
MPLS Label Switched Path Id (LSPID) for an explicit route (ER).

What is the basis of mapping a session to an LSPID? I'm not
asking for the mechanism to get an LSPID - that's the job of
CRLDP, sure. I'm asking how do you decide that session-A is
to use LSPID-1 and session-B to use LSPID-2 and so on....

Is this based on user-id in the PPP session? - which then
suggests that ProxyLCP is a necessity at the LAC?

Any comments......

Thanks
Rajesh



From owner-l2tp@ipsec.org  Thu Jun  8 21:17:32 2000
Received: from ns1.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA20052
	for <l2tpext-archive@odin.ietf.org>; Thu, 8 Jun 2000 21:17:32 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns1.sailpix.com (8.8.8/8.6.9) id OAA27162; Thu, 8 Jun 2000 14:42:25 -0700 (PDT)
Received: from ans2-pub.dttus.com (ans2-pub.dttus.com [204.151.11.3]) by ns1.sailpix.com (8.8.8/8.6.9) with SMTP id OAA27158 for <l2tp@ipsec.org>; Thu, 8 Jun 2000 14:41:25 -0700 (PDT)
Received: by ans2-pub.dttus.com id TAA29470
  (InterLock SMTP Gateway 3.0 for l2tp@ipsec.org);
  Thu, 8 Jun 2000 19:05:14 -0500
Received: by ans2-pub.dttus.com (Internal Mail Agent-2);
  Thu, 8 Jun 2000 19:05:14 -0500
Received: by ans2-pub.dttus.com (Internal Mail Agent-1);
  Thu, 8 Jun 2000 19:05:14 -0500
Message-Id: <2F4A3F6B7BF5D3119E2500508B94E656971B21@uscntnt405.us.deloitte.com>
From: "Verma, Rohit (US - Chicago)" <rverma@dc.com>
To: "'S.Rajesh Kumar'" <rajeshs@futsoft.com>, l2tp@ipsec.org
Subject: RE: data packet length in l2tp
Date: Thu, 8 Jun 2000 17:01:39 -0700 
Mime-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01BFD1A5.E30F4120"
Sender: owner-l2tp@ipsec.org
Precedence: bulk

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

------_=_NextPart_001_01BFD1A5.E30F4120
Content-Type: text/plain;
	charset="iso-8859-1"

Rajesh,
In most cases you should not completely rely on the length specified in the
packet when allocating memory or parsing the packet. Doing that with a
corrupted packet can land you into trouble. 
The best way is to rely on the underlying layers to give you the length and
decrement the length as you process the packet. It is usually a good idea to
check the length specified in the packet header with that specified to you
by the underlying layer a mismatch shows a clear problem. 
 
Since you need to process the AVPs any way, finding out the length will be
part of it so I don't think it makes you any slower.
I hope I have addressed your concerns.

Regards

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


-----Original Message-----
From: S.Rajesh Kumar [mailto:rajeshs@futsoft.com]
Sent: Thursday, June 08, 2000 4:31 PM
To: l2tp@ipsec.org
Subject: data packet length in l2tp


L2tp data packets may or may not have a length field.
In the absence of a length field, how does an implementation
working over say BSD 4.3 udp sockets, find the length of a
data packet? And then read in a complete packet?

An approach of reading in avp by avp (since length of each avp
element is specified) sounds pretty slow....

Thanks
Rajesh

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2652.35">
<TITLE>RE: data packet length in l2tp</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Rajesh,</FONT>
<BR><FONT SIZE=3D2>In most cases you should not completely rely on the =
length specified in the packet when allocating memory or parsing the =
packet. Doing that with a corrupted packet can land you into trouble. =
</FONT></P>

<P><FONT SIZE=3D2>The best way is to rely on the underlying layers to =
give you the length and decrement the length as you process the packet. =
It is usually a good idea to check the length specified in the packet =
header with that specified to you by the underlying layer a mismatch =
shows a clear problem. </FONT></P>

<P><FONT SIZE=3D2>&nbsp;</FONT>
<BR><FONT SIZE=3D2>Since you need to process the AVPs any way, finding =
out the length will be part of it so I don't think it makes you any =
slower.</FONT></P>

<P><FONT SIZE=3D2>I hope I have addressed your concerns.</FONT>
</P>

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

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

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: S.Rajesh Kumar [<A =
HREF=3D"mailto:rajeshs@futsoft.com">mailto:rajeshs@futsoft.com</A>]</FON=
T>
<BR><FONT SIZE=3D2>Sent: Thursday, June 08, 2000 4:31 PM</FONT>
<BR><FONT SIZE=3D2>To: l2tp@ipsec.org</FONT>
<BR><FONT SIZE=3D2>Subject: data packet length in l2tp</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>L2tp data packets may or may not have a length =
field.</FONT>
<BR><FONT SIZE=3D2>In the absence of a length field, how does an =
implementation</FONT>
<BR><FONT SIZE=3D2>working over say BSD 4.3 udp sockets, find the =
length of a</FONT>
<BR><FONT SIZE=3D2>data packet? And then read in a complete =
packet?</FONT>
</P>

<P><FONT SIZE=3D2>An approach of reading in avp by avp (since length of =
each avp</FONT>
<BR><FONT SIZE=3D2>element is specified) sounds pretty slow....</FONT>
</P>

<P><FONT SIZE=3D2>Thanks</FONT>
<BR><FONT SIZE=3D2>Rajesh</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01BFD1A5.E30F4120--


From owner-l2tp@ipsec.org  Thu Jun  8 21:58:44 2000
Received: from ns1.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA21455
	for <l2tpext-archive@odin.ietf.org>; Thu, 8 Jun 2000 21:58:43 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns1.sailpix.com (8.8.8/8.6.9) id PAA27348; Thu, 8 Jun 2000 15:25:19 -0700 (PDT)
Received: from h006008986325.ne.mediaone.net (h006008986325.ne.mediaone.net [24.218.16.153]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id PAA27344 for <l2tp@ipsec.org>; Thu, 8 Jun 2000 15:25:04 -0700 (PDT)
Received: (from carlson@localhost)
	by h006008986325.ne.mediaone.net (8.9.3/8.9.3) id UAA07426;
	Thu, 8 Jun 2000 20:49:02 -0400
From: James Carlson <carlson@workingcode.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14656.16125.163388.450978@h006008986325.ne.mediaone.net>
Date: Thu, 8 Jun 2000 20:49:01 -0400 (EDT)
To: "S.Rajesh Kumar" <rajeshs@futsoft.com>
Cc: l2tp@ipsec.org
Subject: Re: data packet length in l2tp
In-Reply-To: S.Rajesh Kumar's message of 8 June 2000 14:31:05
References: <Pine.LNX.4.10.10006081427470.23924-100000@sanjose.futsoft.com>
X-Mailer: VM 6.75 under Emacs 20.6.1
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

S.Rajesh Kumar writes:
> L2tp data packets may or may not have a length field.
> In the absence of a length field, how does an implementation
> working over say BSD 4.3 udp sockets, find the length of a
> data packet? And then read in a complete packet?

The return value from read() will be the length of the packet.

> An approach of reading in avp by avp (since length of each avp
> element is specified) sounds pretty slow....

Besides slow, it wouldn't work.  Reading from a datagram socket is
destructive.  If you don't ask for the whole packet the first time,
the rest is just discarded.

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


From owner-l2tp@ipsec.org  Mon Jun 12 22:09:04 2000
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA15340
	for <l2tpext-archive@odin.ietf.org>; Mon, 12 Jun 2000 22:09:04 -0400 (EDT)
Received: (from majordomo@localhost) by ns1.sailpix.com (8.8.8/8.6.9) id RAA00473; Mon, 12 Jun 2000 17:46:34 -0700 (PDT)
Received: from relay1.marconi.it (relay1.marconi.it [192.106.52.1]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id RAA00453 for <l2tp@ipsec.org>; Mon, 12 Jun 2000 17:46:00 -0700 (PDT)
Received: from marconicomms.com (localhost [127.0.0.1])
	by relay1.marconi.it (8.9.1a/8.9.1) with SMTP id RAA16888
	for <l2tp@ipsec.org>; Mon, 12 Jun 2000 17:44:23 +0200 (MET DST)
Received: by marconicomms.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id C12568FC.0056D13B ; Mon, 12 Jun 2000 17:48:16 +0200
X-Lotus-FromDomain: MCMAIN@MCEXT
From: "Luigi Campora" <Luigi.Campora@marconi.com>
To: l2tp@ipsec.org
cc: "Flavio Morando" <Flavio.Morando@marconi.com>,
        "Fabio Poggi" <Fabio.Poggi@marconi.com>
Message-ID: <C12568FC.0056D018.00@marconicomms.com>
Date: Mon, 12 Jun 2000 17:48:12 +0200
Subject: PPPoE Framing Type
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-l2tp@ipsec.org
Precedence: bulk




Dear subscribers,
I have a doubt concerning PPP Framing when PPPoE sessions
have to be multiplexed over a L2TP tunnel.

Suppose my LAC is also a PPPoE server: then it receives PPP
packets having the PPPoE framing, i.e., no address/control field
is inserted by the PPPoE client.
Bearer type AVP is not mandatory, thus there is no way of
informing the LNS about this framing
(Framing Type AVP can't help, because PPPoE framing is
neither synchronous nor asynchronous in my opinion...).

Do I have to insert address and control before sending PPP
packets through the L2TP tunnel?
In other words, do I have to provide some PPP bridging
functionality at the LAC?

Regards.

Luigi



----------------------------------------------------------
Luigi Campora

     Phone:      +39 10 600 2511
     Facsimile:  +39 10 600 3849
     E-mail:     luigi.campora@marconi.com

     MARCONI COMMUNICATIONS
     Access Networks Division
     Via A. Negrone 1A -  16153 Genova (Italy)




From owner-l2tp@ipsec.org  Tue Jun 13 04:46:24 2000
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA00803
	for <l2tpext-archive@odin.ietf.org>; Tue, 13 Jun 2000 04:46:23 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns1.sailpix.com (8.8.8/8.6.9) id AAA01359; Tue, 13 Jun 2000 00:26:37 -0700 (PDT)
Received: from relay1.marconi.it (relay1.marconi.it [192.106.52.1]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id AAA01355 for <l2tp@ipsec.org>; Tue, 13 Jun 2000 00:26:19 -0700 (PDT)
Received: from marconicomms.com (localhost [127.0.0.1])
	by relay1.marconi.it (8.9.1a/8.9.1) with SMTP id JAA21674
	for <l2tp@ipsec.org>; Tue, 13 Jun 2000 09:21:37 +0200 (MET DST)
Received: by marconicomms.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id C12568FD.0028C8FB ; Tue, 13 Jun 2000 09:25:28 +0200
X-Lotus-FromDomain: MCMAIN@MCEXT
From: "Luigi Campora" <Luigi.Campora@marconi.com>
To: l2tp@ipsec.org
Message-ID: <C12568FD.0028C838.00@marconicomms.com>
Date: Tue, 13 Jun 2000 09:25:35 +0200
Subject: PPPoE/L2TP Framing Type
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-l2tp@ipsec.org
Precedence: bulk



Dear subscribers,
I have a doubt concerning PPP Framing when PPPoE sessions
have to be multiplexed over a L2TP tunnel.

Suppose my LAC is also a PPPoE server: then it receives PPP
packets having the PPPoE framing, i.e., no address/control field
is inserted by the PPPoE client.
Bearer type AVP is not mandatory, thus there is no way of
informing the LNS about this framing
(Framing Type AVP can't help, because PPPoE framing is
neither synchronous nor asynchronous in my opinion...).

Do I have to insert address and control before sending PPP
packets through the L2TP tunnel?
In other words, do I have to provide some PPP bridging
functionality at the LAC?

Regards.

Luigi




From owner-l2tp@ipsec.org  Tue Jun 13 08:02:50 2000
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA04134
	for <l2tpext-archive@odin.ietf.org>; Tue, 13 Jun 2000 08:02:50 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns1.sailpix.com (8.8.8/8.6.9) id DAA02888; Tue, 13 Jun 2000 03:53:22 -0700 (PDT)
Received: from relay1.marconi.it (relay1.marconi.it [192.106.52.1]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id DAA02884 for <l2tp@ipsec.org>; Tue, 13 Jun 2000 03:52:49 -0700 (PDT)
Received: from marconicomms.com (localhost [127.0.0.1])
	by relay1.marconi.it (8.9.1a/8.9.1) with SMTP id MAA27384
	for <l2tp@ipsec.org>; Tue, 13 Jun 2000 12:48:07 +0200 (MET DST)
Received: by marconicomms.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id C12568FD.003BB0E0 ; Tue, 13 Jun 2000 12:51:59 +0200
X-Lotus-FromDomain: MCMAIN@MCEXT
From: "Ettore Guadagnino" <Ettore.Guadagnino@marconi.com>
To: l2tp@ipsec.org
Message-ID: <C12568FD.003BB0A9.00@marconicomms.com>
Date: Tue, 13 Jun 2000 12:52:08 +0200
Subject: L2TP MIB support for PPP over ATM
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-l2tp@ipsec.org
Precedence: bulk



Hi all,

we have a question about use of the Session Map Table as defined
in the  L2TP-MIB (<draft-ietf-l2tpext-l2tp-mib-00.txt>) and would
appreciate any clarification from you.

Paragraph 3.4 of the document states:

"...l2tpSessionMapTable table provides management
 applications to determine which session within a
 tunnel a particular interface  (either a PPP or DS0
 interface) is mapped to. On the LAC it also provides
 a management application the ability to map a particular
 physical or virtual interface terminating a PPP link
 to a particular L2TP tunnel. This is required since the
 interface stacking as performed (and instrumented by
 the ifStackTable) on the LNS cannot be applied at the LAC.
"

When the subscriber is connected via PPP over ATM,  the interface terminating
the PPP link on a LAC should be of type AAL5.
As AAL5 supports multiplexing of VC connections, a single AAL5 interface
could terminate many VCCs from one or more subscribers.  In this context a
PPP session is associated to a VCC on an AAL5 interface and thus is uniquely
identified by the triplet  <aal5IfIndex, Vpi, Vci>

The l2tpSessionMapTable as defined into the MIB does not allow to associate
the PPP  session inside a tunnel to a VCC.  A similar problem seems to be
present also for the l2tpSessionStatsTable.

Does this mean we need to define one virtual interface for each VCC
carrying PPP packets?  This would imply an heavy overhead to fully support
all mandatory ifTable objects and ifStackTable bindings, althought not stricly
neeeded.

The same considerations seems apply also to PPPoE.
What is your opinion about this point?

Thank you in advance,
Ettore & Giovanni

===================================================================
Ettore Guadagnino
Marconi Communications
E-mail: ettore.guadagnino@marconi.com
tel: +39 10 6003622
===================================================================
Giovanni Vitiello
Getronics
E-mail: giovanni.vitiello@getronics.com
tel: +39 125 521261
===================================================================




From owner-l2tp@ipsec.org  Tue Jun 13 08:35:06 2000
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA05242
	for <l2tpext-archive@odin.ietf.org>; Tue, 13 Jun 2000 08:35:06 -0400 (EDT)
Received: (from majordomo@localhost) by ns1.sailpix.com (8.8.8/8.6.9) id EAA02931; Tue, 13 Jun 2000 04:30:39 -0700 (PDT)
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id EAA02927 for <l2tp@ipsec.org>; Tue, 13 Jun 2000 04:30:19 -0700 (PDT)
Received: from eastmail2.East.Sun.COM ([129.148.1.241])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id EAA16447;
	Tue, 13 Jun 2000 04:30:16 -0700 (PDT)
Received: from phorcys.east.sun.com (phorcys.East.Sun.COM [129.148.174.143])
	by eastmail2.East.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v1.7) with ESMTP id HAA03164;
	Tue, 13 Jun 2000 07:30:15 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.9.3+Sun/8.9.3) id HAA09353;
	Tue, 13 Jun 2000 07:30:15 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14662.6983.323797.864067@gargle.gargle.HOWL>
Date: Tue, 13 Jun 2000 07:30:15 -0400 (EDT)
From: James Carlson <james.d.carlson@east.sun.com>
To: "Luigi Campora" <Luigi.Campora@marconi.com>
Cc: l2tp@ipsec.org, "Flavio Morando" <Flavio.Morando@marconi.com>,
        "Fabio Poggi" <Fabio.Poggi@marconi.com>
Subject: Re: PPPoE Framing Type
In-Reply-To: Luigi Campora's message of 12 June 2000 17:48:12
References: <C12568FC.0056D018.00@marconicomms.com>
X-Mailer: VM 6.75 under Emacs 20.6.1
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Luigi Campora writes:
> Suppose my LAC is also a PPPoE server: then it receives PPP
> packets having the PPPoE framing, i.e., no address/control field
> is inserted by the PPPoE client.

Right.

> Bearer type AVP is not mandatory, thus there is no way of
> informing the LNS about this framing
> (Framing Type AVP can't help, because PPPoE framing is
> neither synchronous nor asynchronous in my opinion...).

Yes, unless you invent a new Framing Type just for "real PPP without
the HDLC headers."  (In my opinion, that's how L2TP should have been
done in the first place.  Then it would have been compatible with the
other encapsulations, like RFC 1598 and RFC 1973.  Oh well.)

> Do I have to insert address and control before sending PPP
> packets through the L2TP tunnel?
> In other words, do I have to provide some PPP bridging
> functionality at the LAC?

Yes.  The HDLC headers are (rather unexpectedly) necessary for PPP
data on L2TP.

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


From owner-l2tp@ipsec.org  Tue Jun 13 22:15:57 2000
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA27595
	for <l2tpext-archive@odin.ietf.org>; Tue, 13 Jun 2000 22:15:53 -0400 (EDT)
Received: (from majordomo@localhost) by ns1.sailpix.com (8.8.8/8.6.9) id SAA04310; Tue, 13 Jun 2000 18:06:48 -0700 (PDT)
Received: from mailsrv.acc.com (mailsrv.acc.com [129.192.64.128]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id SAA04306 for <l2tp@ipsec.org>; Tue, 13 Jun 2000 18:06:10 -0700 (PDT)
Received: from ericsson.com (unk105122.acc.com [129.192.105.122])
	by mailsrv.acc.com (8.9.3/8.9.1) with ESMTP id SAA22999;
	Tue, 13 Jun 2000 18:09:03 -0700 (PDT)
Message-ID: <3946DB61.85BDBEE6@ericsson.com>
Date: Tue, 13 Jun 2000 18:09:53 -0700
From: Evan Caves <evan.caves@ericsson.com>
X-Mailer: Mozilla 4.61 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Ettore Guadagnino <Ettore.Guadagnino@marconi.com>
CC: l2tp@ipsec.org
Subject: Re: L2TP MIB support for PPP over ATM
References: <C12568FD.003BB0A9.00@marconicomms.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



Ettore Guadagnino wrote:
> 
> Hi all,
> 
> we have a question about use of the Session Map Table as defined
> in the  L2TP-MIB (<draft-ietf-l2tpext-l2tp-mib-00.txt>) and would
> appreciate any clarification from you.
> 
> Paragraph 3.4 of the document states:
> 
> "...l2tpSessionMapTable table provides management
>  applications to determine which session within a
>  tunnel a particular interface  (either a PPP or DS0
>  interface) is mapped to. On the LAC it also provides
>  a management application the ability to map a particular
>  physical or virtual interface terminating a PPP link
>  to a particular L2TP tunnel. This is required since the
>  interface stacking as performed (and instrumented by
>  the ifStackTable) on the LNS cannot be applied at the LAC.
> "
> 
> When the subscriber is connected via PPP over ATM,  the interface terminating
> the PPP link on a LAC should be of type AAL5.
> As AAL5 supports multiplexing of VC connections, a single AAL5 interface
> could terminate many VCCs from one or more subscribers.  In this context a
> PPP session is associated to a VCC on an AAL5 interface and thus is uniquely
> identified by the triplet  <aal5IfIndex, Vpi, Vci>
> 
> The l2tpSessionMapTable as defined into the MIB does not allow to associate
> the PPP  session inside a tunnel to a VCC.  A similar problem seems to be
> present also for the l2tpSessionStatsTable.
> 
> Does this mean we need to define one virtual interface for each VCC
> carrying PPP packets?  

Yes.

> This would imply an heavy overhead to fully support
> all mandatory ifTable objects and ifStackTable bindings, althought not stricly
> neeeded.

If you were not tunneling PPP you would have to bind the <al5IfIndex,
Vpi, Vci>
to a virtual port anyways otherwise you could not manage the PPP
interface.

evan
-
> 
> The same considerations seems apply also to PPPoE.
> What is your opinion about this point?
> 
> Thank you in advance,
> Ettore & Giovanni
> 
> ===================================================================
> Ettore Guadagnino
> Marconi Communications
> E-mail: ettore.guadagnino@marconi.com
> tel: +39 10 6003622
> ===================================================================
> Giovanni Vitiello
> Getronics
> E-mail: giovanni.vitiello@getronics.com
> tel: +39 125 521261
> ===================================================================


From owner-l2tp@ipsec.org  Thu Jun 22 18:37:07 2000
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16880
	for <l2tpext-archive@odin.ietf.org>; Thu, 22 Jun 2000 18:37:06 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns1.sailpix.com (8.8.8/8.6.9) id OAA00506; Thu, 22 Jun 2000 14:13:54 -0700 (PDT)
Received: from s4.smtp.oleane.net (s4.smtp.oleane.net [195.25.12.14]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id OAA00502 for <l2tp@ipsec.org>; Thu, 22 Jun 2000 14:13:36 -0700 (PDT)
Received: from smtp1.cluster.oleane.net (smtp1.cluster.oleane.net [195.25.12.16])
	by s4.smtp.oleane.net (Postfix) with ESMTP id B84E820C16
	for <l2tp@ipsec.org>; Thu, 22 Jun 2000 13:46:47 +0200 (CEST)
Received: from oleane  (dyn-1-1-153.Vin.dialup.oleane.fr [195.25.4.153])  by smtp1.cluster.oleane.net  with SMTP id OAA97373 for <l2tp@ipsec.org>; Thu, 22 Jun 2000 14:47:55 +0200 (CEST)
Message-ID: <088e01bfdc48$48a08a60$0401a8c0@oleane.com>
From: "Peter Lewis" <peter.lewis@upperside.fr>
To: <l2tp@ipsec.org>
Date: Thu, 22 Jun 2000 14:49:19 +0200
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_088B_01BFDC59.0BE636E0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Sender: owner-l2tp@ipsec.org
Precedence: bulk

This is a multi-part message in MIME format.

------=_NextPart_000_088B_01BFDC59.0BE636E0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

test

------=_NextPart_000_088B_01BFDC59.0BE636E0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2314.1000" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>test</FONT></DIV></BODY></HTML>

------=_NextPart_000_088B_01BFDC59.0BE636E0--



From owner-l2tp@ipsec.org  Thu Jun 22 18:39:09 2000
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16910
	for <l2tpext-archive@odin.ietf.org>; Thu, 22 Jun 2000 18:39:08 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns1.sailpix.com (8.8.8/8.6.9) id OAA00569; Thu, 22 Jun 2000 14:38:35 -0700 (PDT)
Received: from claret.cisco.com (claret.cisco.com [161.44.3.78]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id OAA00564 for <l2tp@ipsec.org>; Thu, 22 Jun 2000 14:38:20 -0700 (PDT)
Received: from cisco.com (rtp7-dhcp-58-147.cisco.com [161.44.58.147]) by claret.cisco.com (8.8.4-Cisco.1/8.6.5) with ESMTP id RAA01233; Thu, 22 Jun 2000 17:37:57 -0400 (EDT)
Message-ID: <39528734.F71083D4@cisco.com>
Date: Thu, 22 Jun 2000 17:37:56 -0400
From: "W. Mark Townsley" <townsley@cisco.com>
X-Mailer: Mozilla 4.7 [en] (Win95; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: "S.Rajesh Kumar" <rajeshs@futsoft.com>
CC: l2tp@ipsec.org
Subject: Re: data packet length in l2tp
References: <Pine.LNX.4.10.10006081427470.23924-100000@sanjose.futsoft.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



"S.Rajesh Kumar" wrote:
> 
> L2tp data packets may or may not have a length field.
> In the absence of a length field, how does an implementation
> working over say BSD 4.3 udp sockets, find the length of a
> data packet? And then read in a complete packet?
> 
> An approach of reading in avp by avp (since length of each avp
> element is specified) sounds pretty slow....

I assume you are referring to L2TP control packets, not data packets,
since you mention reading in AVPs.

L2TP Control packets always have a length field.

> 
> Thanks
> Rajesh


From owner-l2tp@ipsec.org  Fri Jun 23 17:15:46 2000
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19440
	for <l2tpext-archive@odin.ietf.org>; Fri, 23 Jun 2000 17:15:45 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns1.sailpix.com (8.8.8/8.6.9) id MAA03321; Fri, 23 Jun 2000 12:41:04 -0700 (PDT)
Received: from tcb.net (tcb.net [205.168.100.1]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id MAA03317 for <l2tp@ipsec.org>; Fri, 23 Jun 2000 12:40:46 -0700 (PDT)
Received: from sofos.tcb.net (sofos.tcb.net [127.0.0.1])
	by tcb.net (8.9.3/8.9.3) with ESMTP id NAA18791
	for <l2tp@ipsec.org>; Fri, 23 Jun 2000 13:41:52 -0600
Message-Id: <200006231941.NAA18791@tcb.net>
X-Mailer: exmh version 2.0.3
To: l2tp@ipsec.org
From: Danny McPherson <danny@ambernetworks.com>
Subject: Agenda Items
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 23 Jun 2000 13:41:52 -0600
Sender: owner-l2tp@ipsec.org
Precedence: bulk


I haven't seen a "Call for Agenda Items" as of yet, I don't believe I've 
missed it.

Consulting the list archives reveals that they're _still broken, I'd be glad 
to fix them if there's some problem?

As for agenda items, I have two I've discussed Mark already, and wanted folks 
to begin thinking about.

The first is regarding a revision of the working group charter to include 
support for protocols other than PPP.

The second item pertains to draft-mcpherson-l2tp-es-01.txt (L2TP Circuit 
Emulation Extension).  We're planning to present the draft in Pittsburgh and 
would like it to become a working group item.  We've received quite a bit of 
positive feedback on it so far, and have seen no objections.

If any has objections, concerns or comments with either of these items hashing 
them out in advance will save time in Pittsburgh.

Thanks!

-danny



From owner-l2tp@ipsec.org  Fri Jun 23 18:00:07 2000
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20196
	for <l2tpext-archive@odin.ietf.org>; Fri, 23 Jun 2000 18:00:06 -0400 (EDT)
Received: (from majordomo@localhost) by ns1.sailpix.com (8.8.8/8.6.9) id NAA03450; Fri, 23 Jun 2000 13:57:46 -0700 (PDT)
Received: from vernier.com (mail.vernier.com [209.162.206.11]) by ns1.sailpix.com (8.8.8/8.6.9) with SMTP id NAA03445 for <l2tp@ipsec.org>; Fri, 23 Jun 2000 13:57:38 -0700 (PDT)
Received: from Vernier_Software-Message_Server by vernier.com
	with Novell_GroupWise; Fri, 23 Jun 2000 13:54:49 -0700
Message-Id: <s9536c29.018@vernier.com>
X-Mailer: Novell GroupWise 5.5
Date: Fri, 23 Jun 2000 13:54:09 -0700
From: "David Gardner" <DGARDNER@vernier.com>
To: <l2tp@ipsec.org>
Subject:  remove
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: inline
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ietf.org id SAA20196

remove



From owner-l2tp@ipsec.org  Fri Jun 23 18:01:19 2000
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20266
	for <l2tpext-archive@odin.ietf.org>; Fri, 23 Jun 2000 18:01:18 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns1.sailpix.com (8.8.8/8.6.9) id OAA03500; Fri, 23 Jun 2000 14:14:00 -0700 (PDT)
Received: from claret.cisco.com (claret.cisco.com [161.44.3.78]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id OAA03496 for <l2tp@ipsec.org>; Fri, 23 Jun 2000 14:13:37 -0700 (PDT)
Received: from claret.cisco.com (claret.cisco.com [161.44.3.78]) by claret.cisco.com (8.8.4-Cisco.1/8.6.5) with ESMTP id RAA16616; Fri, 23 Jun 2000 17:13:04 -0400 (EDT)
Date: Fri, 23 Jun 2000 17:13:03 -0400 (EDT)
From: "W. Mark Townsley" <townsley@cisco.com>
To: Danny McPherson <danny@ambernetworks.com>
cc: l2tp@ipsec.org
Subject: Re: Agenda Items
In-Reply-To: <200006231941.NAA18791@tcb.net>
Message-ID: <Pine.GSO.4.10.10006231710170.16494-100000@claret.cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-l2tp@ipsec.org
Precedence: bulk

On Fri, 23 Jun 2000, Danny McPherson wrote:

> 
> I haven't seen a "Call for Agenda Items" as of yet, I don't believe I've 
> missed it.

Consider this the call then.

> 
> Consulting the list archives reveals that they're _still broken, I'd be glad 
> to fix them if there's some problem?

They had a Y2K bug. I solicited a volunteer to take over the list, but he
has not followed through. Consider this a resolicitation.

> 
> As for agenda items, I have two I've discussed Mark already, and wanted folks 
> to begin thinking about.
> 
> The first is regarding a revision of the working group charter to include 
> support for protocols other than PPP.
> 
> The second item pertains to draft-mcpherson-l2tp-es-01.txt (L2TP Circuit 
> Emulation Extension).  We're planning to present the draft in Pittsburgh and 
> would like it to become a working group item.  We've received quite a bit of 
> positive feedback on it so far, and have seen no objections.
> 
> If any has objections, concerns or comments with either of these items hashing 
> them out in advance will save time in Pittsburgh.

I already had you scheduled for the meeting. I will put you down for two
slots.

> 
> Thanks!
> 
> -danny
> 
> 
> 



From owner-l2tp@ipsec.org  Sat Jun 24 21:55:30 2000
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA17582
	for <l2tpext-archive@odin.ietf.org>; Sat, 24 Jun 2000 21:55:29 -0400 (EDT)
Received: (from majordomo@localhost) by ns1.sailpix.com (8.8.8/8.6.9) id RAA06331; Sat, 24 Jun 2000 17:38:34 -0700 (PDT)
Received: from gate.ascend.co.jp (root@gate.ascend.co.jp [202.246.11.253]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id RAA06327 for <l2tp@ipsec.org>; Sat, 24 Jun 2000 17:38:16 -0700 (PDT)
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 JAA07159
	for <l2tp@ipsec.org>; Sun, 25 Jun 2000 09:38:13 +0900 (JST)
Received: from admse.ascend.co.jp (admse.ascend.co.jp [202.246.11.186])
	by home.ascend.co.jp (8.9.3/3.7W/05/18/00) with ESMTP id JAA96623
	for <l2tp@ipsec.org>; Sun, 25 Jun 2000 09:38:13 +0900 (JST)
Received: from ascend.co.jp ([135.255.40.137])
	by admse.ascend.co.jp (8.9.3/3.7W/04/03/00) with ESMTP id JAA18223
	for <l2tp@ipsec.org>; Sun, 25 Jun 2000 09:38:12 +0900 (JST)
Message-ID: <3955545B.F20E4D79@ascend.co.jp>
Date: Sun, 25 Jun 2000 09:37:47 +0900
From: Tatsuya Yanagibashi <tyanagibashi@ascend.co.jp>
X-Mailer: Mozilla 4.6 [ja] (Win98; I)
X-Accept-Language: ja
MIME-Version: 1.0
To: l2tp@ipsec.org
Subject: Multilink PPP on l2tp
Content-Type: text/plain; charset=iso-2022-jp
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Folks,

I am having issue regarding to Multilink PPP on L2TP. As you know, 
MP on L2TP has potentially problem when it happens to renegotiate 
LCP configuration option. I think this problem depend on that 
Endpoint-Discriminator(ED) could be changed during LCP renegotiation. 
I feel that some Terminal Adaptor doesn't expect to recieve sencond 
ED value on single link which is different from 1st value is 
negotiated with LAC. 

One of solution is ProxyLCP. If LNS is able to agree with  all 
parameter, we can avoid renegotiation. But unfortunately, it cannot
be useful for all cases because LNS sometime want to renegotiate. 
In this case, LNS sends new ED value which is generated by LNS 
itself even if LNS knows the ED value which is negotiated between 
remote user and LAC. 

Does anybody know there is LNS implementation to send same ED 
value in LCP renotiation which LNS learns by ProxyLCP from LAC.

Regards,
Tatsuya


From owner-l2tp@ipsec.org  Mon Jun 26 06:20:11 2000
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA28971
	for <l2tpext-archive@odin.ietf.org>; Mon, 26 Jun 2000 06:20:10 -0400 (EDT)
Received: (from majordomo@localhost) by ns1.sailpix.com (8.8.8/8.6.9) id BAA09095; Mon, 26 Jun 2000 01:57:54 -0700 (PDT)
Received: from gorilla.mchh.siemens.de (gorilla.mchh.siemens.de [194.138.158.18]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id BAA09091 for <l2tp@ipsec.org>; Mon, 26 Jun 2000 01:57:45 -0700 (PDT)
Received: from blues.mchh.siemens.de (mail3.mchh.siemens.de [194.138.158.227] (may be forged))
	by gorilla.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id KAA08973
	for <l2tp@ipsec.org>; Mon, 26 Jun 2000 10:57:10 +0200 (MET DST)
Received: from mchh246e.demchh201e.icn.siemens.de ([218.1.68.146])
	by blues.mchh.siemens.de (8.9.1/8.9.1) with ESMTP id KAA22844
	for <l2tp@ipsec.org>; Mon, 26 Jun 2000 10:54:40 +0200 (MET DST)
Received: by MCHH246E with Internet Mail Service (5.5.2448.0)
	id <NATM4XRB>; Mon, 26 Jun 2000 11:00:20 +0200
Message-ID: <BFF965F47F6BD31182740008C7DBACD179C9CF@MCHH254E>
From: Simmet Franz <Franz.Simmet@icn.siemens.de>
To: l2tp@ipsec.org
Subject: remove
Date: Mon, 26 Jun 2000 11:00:03 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain
Sender: owner-l2tp@ipsec.org
Precedence: bulk

remove


From owner-l2tp@ipsec.org  Wed Jun 28 18:55:52 2000
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05816
	for <l2tpext-archive@odin.ietf.org>; Wed, 28 Jun 2000 18:55:51 -0400 (EDT)
Received: (from majordomo@localhost) by ns1.sailpix.com (8.8.8/8.6.9) id OAA17279; Wed, 28 Jun 2000 14:21:46 -0700 (PDT)
Received: from swa.smdc.army.mil (swa.smdc.army.mil [164.49.251.3]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id OAA17275 for <l2tp@ipsec.org>; Wed, 28 Jun 2000 14:21:37 -0700 (PDT)
Received: from swa.smdc.army.mil (root@localhost)
	by swa.smdc.army.mil with ESMTP id QAA15951
	for <l2tp@ipsec.org>; Wed, 28 Jun 2000 16:21:57 -0500 (CDT)
Received: from mailex1.smdc.army.mil (mailex1.smdc.army.mil [164.49.1.61])
	by swa.smdc.army.mil with ESMTP id QAA15945
	for <l2tp@ipsec.org>; Wed, 28 Jun 2000 16:21:56 -0500 (CDT)
Received: by mailex1.smdc.army.mil with Internet Mail Service (5.5.2650.21)
	id <NZBFF3YV>; Wed, 28 Jun 2000 21:19:40 -0000
Message-ID: <D7EDF909795ED211BFB500805FA70BBA068BA1E9@mailex1.smdc.army.mil>
From: "Powers, Lanny Mr" <lanny.powers@smdc.army.mil>
To: "'l2tp@ipsec.org'" <l2tp@ipsec.org>
Subject: L2TP + IPSec client for window 95,98, and NT 
Date: Wed, 28 Jun 2000 21:19:39 -0000
X-Mailer: Internet Mail Service (5.5.2650.21)
Sender: owner-l2tp@ipsec.org
Precedence: bulk

Is there a L2TP + IPSec client for window 95,98, and NT ? 


From owner-l2tp@ipsec.org  Thu Jun 29 04:19:06 2000
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA24256
	for <l2tpext-archive@odin.ietf.org>; Thu, 29 Jun 2000 04:19:05 -0400 (EDT)
Received: (from majordomo@localhost) by ns1.sailpix.com (8.8.8/8.6.9) id XAA18001; Wed, 28 Jun 2000 23:59:23 -0700 (PDT)
Received: from hotmail.com (f260.law7.hotmail.com [216.33.236.138]) by ns1.sailpix.com (8.8.8/8.6.9) with SMTP id XAA17997 for <l2tp@ipsec.org>; Wed, 28 Jun 2000 23:59:07 -0700 (PDT)
Received: (qmail 42161 invoked by uid 0); 29 Jun 2000 06:58:37 -0000
Message-ID: <20000629065837.42160.qmail@hotmail.com>
Received: from 193.64.193.124 by www.hotmail.com with HTTP;
	Wed, 28 Jun 2000 23:58:37 PDT
X-Originating-IP: [193.64.193.124]
From: "Tim Rochford" <roch4d@hotmail.com>
To: l2tp@ipsec.org
Cc: roch4d@hotmail.com
Subject: L2TP implementation issues when running over IpSec
Date: Thu, 29 Jun 2000 06:58:37 GMT
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Sender: owner-l2tp@ipsec.org
Precedence: bulk

Hi,
   I'm working on an implementation of L2TP over IPSec, and I would like to 
find out about how over people have gone about implementing L2TP when they 
know that the IP level is secure.
   For example, RFC2661(Section 9.1) states that the Assigned Tunnel ID and 
Assigned Session ID be chosen in a unpredicatble manner. If Im developing a 
L2TP implementation over IPSec though can't I just use a simple counter for 
these ID values ?
   Also there would be no need to use the Challenge / Response AVPs, or use 
AVP hiding if running over IPSec.
   Are there any parts of L2TP that could not be used, or are made redundant 
when using L2TP-IPSec ?
   Any thoughts ?
Thank you.
Tim

________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com



From owner-l2tp@ipsec.org  Thu Jun 29 05:42:43 2000
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA24807
	for <l2tpext-archive@odin.ietf.org>; Thu, 29 Jun 2000 05:42:43 -0400 (EDT)
Received: (from majordomo@localhost) by ns1.sailpix.com (8.8.8/8.6.9) id BAA18075; Thu, 29 Jun 2000 01:10:51 -0700 (PDT)
Received: from relay1.marconi.it (relay1.marconi.it [192.106.52.1]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id BAA18071 for <l2tp@ipsec.org>; Thu, 29 Jun 2000 01:10:35 -0700 (PDT)
Received: from marconicomms.com (localhost [127.0.0.1])
	by relay1.marconi.it (8.9.1a/8.9.1) with SMTP id KAA25256
	for <l2tp@ipsec.org>; Thu, 29 Jun 2000 10:05:31 +0200 (MET DST)
Received: by marconicomms.com(Lotus SMTP MTA v4.6.3  (733.2 10-16-1998))  id C125690D.002CCAFE ; Thu, 29 Jun 2000 10:09:15 +0200
X-Lotus-FromDomain: MCMAIN@MCEXT
From: "Barbara Nichel" <Barbara.Nichel@marconi.com>
To: l2tp@ipsec.org
Message-ID: <C125690D.002CC96A.00@marconicomms.com>
Date: Thu, 29 Jun 2000 10:09:31 +0200
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-l2tp@ipsec.org
Precedence: bulk



Dear subscribers,

We have a doubt about the possibility to open multiple tunnels with the same
LNS.
In case LAC needs to open more than one tunnel with the same LNS, is it
necessary
to specify different IP addresses or different UDP ports?

Thanks in advance for your help.

Barbara and Massimiliano.




From owner-l2tp@ipsec.org  Thu Jun 29 06:01:15 2000
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA24942
	for <l2tpext-archive@odin.ietf.org>; Thu, 29 Jun 2000 06:01:15 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns1.sailpix.com (8.8.8/8.6.9) id BAA18133; Thu, 29 Jun 2000 01:56:06 -0700 (PDT)
Received: from baynet.baynetworks.com (ns1.BayNetworks.COM [134.177.3.20]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id BAA18129 for <l2tp@ipsec.org>; Thu, 29 Jun 2000 01:55:48 -0700 (PDT)
Received: from mailhost.BayNetworks.COM (h016b.s86b1.BayNetworks.COM [134.177.1.107])
	by baynet.baynetworks.com (8.9.1/8.9.1) with ESMTP id BAA01904;
	Thu, 29 Jun 2000 01:53:46 -0700 (PDT)
Received: from shasta-exch.shastanets.com (mailserver.shastanets.com [47.82.16.150])
	by mailhost.BayNetworks.COM (8.9.1/8.8.8) with ESMTP id BAA23541;
	Thu, 29 Jun 2000 01:53:46 -0700 (PDT)
Received: by mailserver.shastanets.com with Internet Mail Service (5.5.2650.21)
	id <NH8Y9C0N>; Thu, 29 Jun 2000 01:54:41 -0700
Message-ID: <4DEC824F6F1FD3119BEF0000E86CEA010287E579@mailserver.shastanets.com>
From: Vipin Jain <vipin@shastanets.com>
To: "'Barbara Nichel'" <Barbara.Nichel@marconi.com>, l2tp@ipsec.org
Subject: RE: 
Date: Thu, 29 Jun 2000 01:54:40 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-l2tp@ipsec.org
Precedence: bulk

nope. only a different tunnel-id is necessary.

-----Original Message-----
From: Barbara Nichel [mailto:Barbara.Nichel@marconi.com]
Sent: Thursday, June 29, 2000 1:10 AM
To: l2tp@ipsec.org
Subject: 




Dear subscribers,

We have a doubt about the possibility to open multiple tunnels with the same
LNS.
In case LAC needs to open more than one tunnel with the same LNS, is it
necessary
to specify different IP addresses or different UDP ports?

Thanks in advance for your help.

Barbara and Massimiliano.



From owner-l2tp@ipsec.org  Thu Jun 29 07:49:38 2000
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA26852
	for <l2tpext-archive@odin.ietf.org>; Thu, 29 Jun 2000 07:49:38 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns1.sailpix.com (8.8.8/8.6.9) id DAA19601; Thu, 29 Jun 2000 03:47:46 -0700 (PDT)
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id DAA19597 for <l2tp@ipsec.org>; Thu, 29 Jun 2000 03:47:02 -0700 (PDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA25255;
	Thu, 29 Jun 2000 06:47:01 -0400 (EDT)
Message-Id: <200006291047.GAA25255@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-02.txt
Date: Thu, 29 Jun 2000 06:47:01 -0400
Sender: owner-l2tp@ipsec.org
Precedence: bulk

--NextPart

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

	Title		: L2TP Header Compression ('L2TPHC')
	Author(s)	: A. Valencia
	Filename	: draft-ietf-l2tpext-l2tphc-02.txt
	Pages		: 7
	Date		: 28-Jun-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 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-02.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-02.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-02.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:	<20000628133426.I-D@ietf.org>

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

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

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

--OtherAccess--

--NextPart--




From owner-l2tp@ipsec.org  Thu Jun 29 07:49:46 2000
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA26875
	for <l2tpext-archive@odin.ietf.org>; Thu, 29 Jun 2000 07:49:46 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns1.sailpix.com (8.8.8/8.6.9) id DAA19551; Thu, 29 Jun 2000 03:28:26 -0700 (PDT)
Received: from center.mshindo.net (center.mshindo.net [210.231.221.221]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id DAA19547 for <l2tp@ipsec.org>; Thu, 29 Jun 2000 03:28:04 -0700 (PDT)
Received: from cosinecom.com (pl018.nas132.k-tokyo.nttpc.ne.jp [210.165.163.18])
	by center.mshindo.net (8.9.3/3.7W/00041811) with SMTP id TAA06355;
	Thu, 29 Jun 2000 19:23:08 +0900 (JST)
Date: Thu, 29 Jun 2000 19:28:43 +0900 (JST)
Message-Id: <20000629.192843.78701481.mshindo@cosinecom.com>
To: Barbara.Nichel@marconi.com
Cc: l2tp@ipsec.org
Subject: multiple tunnels between given LAC/LNS pair
From: Motonori Shindo <mshindo@cosinecom.com>
In-Reply-To: <C125690D.002CC96A.00@marconicomms.com>
References: <C125690D.002CC96A.00@marconicomms.com>
X-Mailer: Mew version 1.95b30 on XEmacs 21.1 (Canyonlands)
X-PGP-fingerprint: 06 B0 B1 A4 06 C1 6A 14  63 C0 D7 18 01 CD D9 83
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Barbara

From: "Barbara Nichel" <Barbara.Nichel@marconi.com>
Subject: 
Date: Thu, 29 Jun 2000 10:09:31 +0200

> We have a doubt about the possibility to open multiple tunnels with
> the same LNS.  In case LAC needs to open more than one tunnel with
> the same LNS, is it necessary to specify different IP addresses or
> different UDP ports?

No. Because LAC can choose an arbitary source port number, it can
establish two or more tunnels to the LNS with single destination IP
address and port number.

However, when a call comes in, the way how to determine wheter it will
establsh a new tunnel or stay in an already-established tunnel is up
to the implementation. Most of the implementation available today will
stay in an already-established tunnel, but it is also possible to
create a new tunnel every time a call comes in, in an extreme case.

Regards,

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


From owner-l2tp@ipsec.org  Thu Jun 29 16:32:23 2000
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA19608
	for <l2tpext-archive@odin.ietf.org>; Thu, 29 Jun 2000 16:32:23 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns1.sailpix.com (8.8.8/8.6.9) id MAA20125; Thu, 29 Jun 2000 12:05:21 -0700 (PDT)
Received: from sj-msg-core-2.cisco.com (sj-msg-core-2.cisco.com [171.69.43.88]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id MAA20121 for <l2tp@ipsec.org>; Thu, 29 Jun 2000 12:05:00 -0700 (PDT)
Received: from townsley-ultra.cisco.com (townsley-ultra.cisco.com [161.44.58.38])
	by sj-msg-core-2.cisco.com (8.9.3/8.9.1) with ESMTP id MAA18107;
	Thu, 29 Jun 2000 12:04:38 -0700 (PDT)
Received: from cisco.com (townsley-home.cisco.com [161.44.99.50]) by townsley-ultra.cisco.com (8.8.4-Cisco.1/CISCO.WS.1.2) with ESMTP id PAA03200; Thu, 29 Jun 2000 15:04:27 -0400 (EDT)
Message-ID: <395B9D71.9A6357C1@cisco.com>
Date: Thu, 29 Jun 2000 15:03:13 -0400
From: "W. Mark Townsley" <townsley@cisco.com>
Organization: cisco Systems
X-Mailer: Mozilla 4.7 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Tim Rochford <roch4d@hotmail.com>
CC: l2tp@ipsec.org
Subject: Re: L2TP implementation issues when running over IpSec
References: <20000629065837.42160.qmail@hotmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



Tim Rochford wrote:
> 
> Hi,
>    I'm working on an implementation of L2TP over IPSec, and I would like to
> find out about how over people have gone about implementing L2TP when they
> know that the IP level is secure.
>    For example, RFC2661(Section 9.1) states that the Assigned Tunnel ID and
> Assigned Session ID be chosen in a unpredicatble manner. If Im developing a
> L2TP implementation over IPSec though can't I just use a simple counter for
> these ID values ?

Yes.

>    Also there would be no need to use the Challenge / Response AVPs, or use
> AVP hiding if running over IPSec.

Tunnel authentication is a bit redundant, unless you need to tie into a
legacy AAA system.

>    Are there any parts of L2TP that could not be used, or are made redundant
> when using L2TP-IPSec ?
>    Any thoughts ?
> Thank you.
> Tim
> 
> ________________________________________________________________________
> Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com


