From owner-l2tp@ipsec.org  Thu Jul  6 21:09:20 2000
Received: from ns1.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28400
	for <l2tpext-archive@odin.ietf.org>; Thu, 6 Jul 2000 21:09:19 -0400 (EDT)
Received: (from majordomo@localhost) by ns1.sailpix.com (8.8.8/8.6.9) id QAA08221; Thu, 6 Jul 2000 16:57:33 -0700 (PDT)
Received: from stile.redback.com (stile.redback.com [155.53.36.12]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id QAA08217 for <l2tp@ipsec.org>; Thu, 6 Jul 2000 16:57:09 -0700 (PDT)
Received: (from suhail@localhost)
	by stile.redback.com (8.8.8/8.8.8) id QAA13763;
	Thu, 6 Jul 2000 16:56:38 -0700 (PDT)
From: Suhail Nanji <suhail@redback.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Thu,  6 Jul 2000 16:56:37 -0700 (PDT)
To: James Carlson <james.d.carlson@east.sun.com>
Cc: l2tp@ipsec.org
Subject: Re: I-D ACTION:draft-nanji-l2tp-eth-00.txt
In-Reply-To: <14654.25407.129031.333557@gargle.gargle.HOWL>
References: <200006071415.KAA10987@ietf.org>
	<14654.25407.129031.333557@gargle.gargle.HOWL>
X-Mailer: VM 6.43 under 21.1 (patch 9) "Canyonlands" XEmacs Lucid
Message-ID: <14693.6839.474292.480983@stile.redback.com>
Reply-To: suhail@redback.com (Suhail Nanji)
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

James Carlson writes:
> > 	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?

You make a good point, the draft should at least reference BCP and mention
why it is insufficient.  The next revision of the draft will include this
change.

BCP over PPP over L2TP is reasonable, but this adds protocol overhead, and
requires that someone run PPP.  In many broadband environments, the end
user is communicating from their PC out their Ethernet interface to a
bridging modem.  The end user is not necessarily running PPP.  The modem is
designed to be inexpensive and is also not running PPP.  This is a very
common model for both DSL and Cable.  That Ethernet link then extends to an
access concentrator that may not terminate the connection, but wishes to
tunnel it to another access concentrator.  Since the connection from the
end user is Ethernet, we are proposing a method to extend that
Ethernet link over L2TP. Since Ethernet is a Layer 2 protocol, it seems
reasonable to extend the Layer 2 Tunneling protocol (L2TP) to tunnel it.
In DSL, the individual Ethernet links from each modem are still chanelized
so L2TP seems an ideal way to maintain that chanelization to the LNS.

> 
> -- 
> 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  Fri Jul  7 11:33:04 2000
Received: from ns1.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29834
	for <l2tpext-archive@odin.ietf.org>; Fri, 7 Jul 2000 11:33:03 -0400 (EDT)
Received: (from majordomo@localhost) by ns1.sailpix.com (8.8.8/8.6.9) id HAA10430; Fri, 7 Jul 2000 07:27:47 -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 HAA10426 for <l2tp@ipsec.org>; Fri, 7 Jul 2000 07:27:32 -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 QAA23302;
	Fri, 7 Jul 2000 16:26:48 +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 QAA14348;
	Fri, 7 Jul 2000 16:24:15 +0200 (MET DST)
Received: by MCHH246E with Internet Mail Service (5.5.2448.0)
	id <NATM7AMC>; Fri, 7 Jul 2000 16:27:18 +0200
Message-ID: <3B59676F9ADBD211B5360060086E64EECC017E@MCHH237E>
From: Theimer Thomas <Thomas.Theimer@icn.siemens.de>
To: "'suhail@redback.com'" <suhail@redback.com>
Cc: l2tp@ipsec.org
Subject: RE: I-D ACTION:draft-nanji-l2tp-eth-00.txt
Date: Fri, 7 Jul 2000 16:27:06 +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


	Suhail Nanji writes:
> The end user is not necessarily running PPP.  The modem is
> designed to be inexpensive and is also not running PPP.  This is a very
> common model for both DSL and Cable.  
> 
	[Theimer Thomas]  
	Two questions for clarification:

	1. What is the link layer between modem and access concentrator ? If the answer is ATM or FR, then why is bridging over ATM/FR not sufficient ?

	2. If the modem is so inexpensive that it doesn't even run PPP, would such a modem be capable of running L2TP ?

	Regards,

	Thomas


From owner-l2tp@ipsec.org  Fri Jul  7 15:39:17 2000
Received: from ns1.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11099
	for <l2tpext-archive@odin.ietf.org>; Fri, 7 Jul 2000 15:39:17 -0400 (EDT)
Received: (from majordomo@localhost) by ns1.sailpix.com (8.8.8/8.6.9) id LAA10855; Fri, 7 Jul 2000 11:42:20 -0700 (PDT)
Received: from stile.redback.com (stile.redback.com [155.53.36.12]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id LAA10851 for <l2tp@ipsec.org>; Fri, 7 Jul 2000 11:41:59 -0700 (PDT)
Received: (from suhail@localhost)
	by stile.redback.com (8.8.8/8.8.8) id LAA11705;
	Fri, 7 Jul 2000 11:38:26 -0700 (PDT)
From: Suhail Nanji <suhail@redback.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Fri,  7 Jul 2000 11:38:26 -0700 (PDT)
To: Theimer Thomas <Thomas.Theimer@icn.siemens.de>
Cc: l2tp@ipsec.org
Subject: RE: I-D ACTION:draft-nanji-l2tp-eth-00.txt
In-Reply-To: <3B59676F9ADBD211B5360060086E64EECC017E@MCHH237E>
References: <3B59676F9ADBD211B5360060086E64EECC017E@MCHH237E>
X-Mailer: VM 6.43 under 21.1 (patch 9) "Canyonlands" XEmacs Lucid
Message-ID: <14694.9025.248898.959067@stile.redback.com>
Reply-To: suhail@redback.com (Suhail Nanji)
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Theimer Thomas writes:
> 
> 	Suhail Nanji writes:
> > The end user is not necessarily running PPP.  The modem is
> > designed to be inexpensive and is also not running PPP.  This is a very
> > common model for both DSL and Cable.  
> > 
> 	[Theimer Thomas]  
> 	Two questions for clarification:
> 
> 	1. What is the link layer between modem and access concentrator ? If the answer is ATM or FR, then why is bridging over ATM/FR not sufficient ?
> 

Bridging is sufficient to get it to the first access concentrator but from
there some protocol is needed to have the Ethernet frame tunneled to
another access concentrator which would be the point of termination.

> 	2. If the modem is so inexpensive that it doesn't even run PPP,
would such a modem be capable of running L2TP ?

The modem would not be running L2TP.  The modem would simply be bridging
traffic.  L2TP is between the first access concentrator and another access
concentrator.

> 
> 	Regards,
> 
> 	Thomas


From owner-l2tp@ipsec.org  Fri Jul  7 21:52:38 2000
Received: from ns1.sailpix.com ([155.53.1.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA17591
	for <l2tpext-archive@odin.ietf.org>; Fri, 7 Jul 2000 21:52:37 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns1.sailpix.com (8.8.8/8.6.9) id RAA11334; Fri, 7 Jul 2000 17:42:29 -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 RAA11330 for <l2tp@ipsec.org>; Fri, 7 Jul 2000 17:42:08 -0700 (PDT)
Received: (from carlson@localhost)
	by h006008986325.ne.mediaone.net (8.9.3/8.9.3) id UAA12710;
	Fri, 7 Jul 2000 20:42: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: <14694.30938.75278.240300@h006008986325.ne.mediaone.net>
Date: Fri, 7 Jul 2000 20:42:02 -0400 (EDT)
To: suhail@redback.com (Suhail Nanji)
Cc: l2tp@ipsec.org
Subject: RE: I-D ACTION:draft-nanji-l2tp-eth-00.txt
In-Reply-To: Suhail Nanji's message of 7 July 2000 11:38:26
References: <3B59676F9ADBD211B5360060086E64EECC017E@MCHH237E>
	<14694.9025.248898.959067@stile.redback.com>
X-Mailer: VM 6.75 under Emacs 20.6.1
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Suhail Nanji writes:
> Bridging is sufficient to get it to the first access concentrator but from
> there some protocol is needed to have the Ethernet frame tunneled to
> another access concentrator which would be the point of termination.

OK, so if I understand this correctly, you want something like this:

	PC<--Ethernet-->modem<--DSL-->conc1<--ATM-->conc2

where "conc1" is the first concentrator and "conc2" is the second
concentrator.  Is this correct?

If so, then why not run regular IP over Ethernet between the PC and
conc1, using any convenient encapsulation over the DSL link
(Cisco-style HDLC comes to mind; ATM would also do the trick but would
be needlessly more expensive), and then have conc1 behave as a
learning bridge (called a "switch" by marketing droids these days)?
The link to conc2 can then be either ATM LANE (yecch, but solves the
problem simply), a static VC per MAC (simpler, but like LANE doesn't
scale nicely), or a routed IP over ATM link (a little more complex,
but scales nicely).

Why is IP-over-PPPoE-over-foo-over-L2TP-over-bar necessary?  It only
complicates the software in the PC and breaks (at least) RFC 1661.

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


From owner-l2tp@ipsec.org  Mon Jul 10 10:38:59 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 KAA10904
	for <l2tpext-archive@odin.ietf.org>; Mon, 10 Jul 2000 10:38:56 -0400 (EDT)
Received: (from majordomo@localhost) by ns1.sailpix.com (8.8.8/8.6.9) id GAA07054; Mon, 10 Jul 2000 06:18:12 -0700 (PDT)
Received: from beamer.mchh.siemens.de (beamer.mchh.siemens.de [194.138.158.163]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id GAA07050 for <l2tp@ipsec.org>; Mon, 10 Jul 2000 06:17:52 -0700 (PDT)
Received: from blues.mchh.siemens.de (mail3.mchh.siemens.de [194.138.158.227] (may be forged))
	by beamer.mchh.siemens.de (8.9.3/8.9.3) with ESMTP id PAA18468;
	Mon, 10 Jul 2000 15:17:11 +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 PAA19920;
	Mon, 10 Jul 2000 15:14:35 +0200 (MET DST)
Received: by MCHH246E with Internet Mail Service (5.5.2448.0)
	id <NATM8LXW>; Mon, 10 Jul 2000 15:17:41 +0200
Message-ID: <3B59676F9ADBD211B5360060086E64EECC0180@MCHH237E>
From: Theimer Thomas <Thomas.Theimer@icn.siemens.de>
To: "'suhail@redback.com'" <suhail@redback.com>
Cc: l2tp@ipsec.org
Subject: RE: I-D ACTION:draft-nanji-l2tp-eth-00.txt
Date: Mon, 10 Jul 2000 15:08:08 +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

	Suhail Nanji writes: 
> Theimer Thomas writes:
> > 
> > 	Suhail Nanji writes:
> > > The end user is not necessarily running PPP.  The modem is
> > > designed to be inexpensive and is also not running PPP.  This is a very
> > > common model for both DSL and Cable.  
> > > 
> > 	[Theimer Thomas]  
> > 	Two questions for clarification:
> > 
> > 	1. What is the link layer between modem and access concentrator ? If the answer is ATM or FR, then why is bridging over ATM/FR not sufficient ?
> > 
> 
> Bridging is sufficient to get it to the first access concentrator but from
> there some protocol is needed to have the Ethernet frame tunneled to
> another access concentrator which would be the point of termination.
> 
	[Theimer Thomas]  What is wrong with encapsulating the Ethernet frame in PPP over L2TP ? It only costs a couple of extra header bytes, but does not need any new protocol or encapsulation. You can simply extend the Ethernet-over-ATM bridge into another Ethernet-over-PPP-over-L2TP bridge. Note that PPP here is not per user, it is simply a tunnel encapsulation.

	Thomas


From owner-l2tp@ipsec.org  Mon Jul 10 14:01:14 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 OAA20260
	for <l2tpext-archive@odin.ietf.org>; Mon, 10 Jul 2000 14:01:13 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns1.sailpix.com (8.8.8/8.6.9) id KAA07314; Mon, 10 Jul 2000 10:03:04 -0700 (PDT)
Received: from stile.redback.com (stile.redback.com [155.53.36.12]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id KAA07310 for <l2tp@ipsec.org>; Mon, 10 Jul 2000 10:02:39 -0700 (PDT)
Received: (from suhail@localhost)
	by stile.redback.com (8.8.8/8.8.8) id KAA27911;
	Mon, 10 Jul 2000 10:01:33 -0700 (PDT)
From: Suhail Nanji <suhail@redback.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Mon, 10 Jul 2000 10:01:33 -0700 (PDT)
To: James Carlson <carlson@workingcode.com>
Cc: l2tp@ipsec.org
Subject: RE: I-D ACTION:draft-nanji-l2tp-eth-00.txt
In-Reply-To: <14694.30938.75278.240300@h006008986325.ne.mediaone.net>
References: <3B59676F9ADBD211B5360060086E64EECC017E@MCHH237E>
	<14694.9025.248898.959067@stile.redback.com>
	<14694.30938.75278.240300@h006008986325.ne.mediaone.net>
X-Mailer: VM 6.43 under 21.1 (patch 9) "Canyonlands" XEmacs Lucid
Message-ID: <14698.70.142062.717900@stile.redback.com>
Reply-To: suhail@redback.com (Suhail Nanji)
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

James Carlson writes:
> Suhail Nanji writes:
> > Bridging is sufficient to get it to the first access concentrator but from
> > there some protocol is needed to have the Ethernet frame tunneled to
> > another access concentrator which would be the point of termination.
> 
> OK, so if I understand this correctly, you want something like this:
> 
> 	PC<--Ethernet-->modem<--DSL-->conc1<--ATM-->conc2
> 
> where "conc1" is the first concentrator and "conc2" is the second
> concentrator.  Is this correct?

No, my picture would look something like this:

	PC<--Ethernet-->modem<--DSL-->DSLAM<--ATM-->conc1<--IP-->conc2

The access concentrators are connected via an IP network.  This is why
tunneling is needed to transport the Ethernet frame.

> 
> If so, then why not run regular IP over Ethernet between the PC and
> conc1, using any convenient encapsulation over the DSL link
> (Cisco-style HDLC comes to mind; ATM would also do the trick but would
> be needlessly more expensive), and then have conc1 behave as a
> learning bridge (called a "switch" by marketing droids these days)?
> The link to conc2 can then be either ATM LANE (yecch, but solves the
> problem simply), a static VC per MAC (simpler, but like LANE doesn't
> scale nicely), or a routed IP over ATM link (a little more complex,
> but scales nicely).
> 
> Why is IP-over-PPPoE-over-foo-over-L2TP-over-bar necessary?  It only
> complicates the software in the PC and breaks (at least) RFC 1661.
> 
> -- 
> James Carlson                                  <carlson@workingcode.com>
> "PPP Design and Debugging" --- http://people.ne.mediaone.net/carlson/ppp


From owner-l2tp@ipsec.org  Tue Jul 11 11:39:29 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 LAA04929
	for <l2tpext-archive@odin.ietf.org>; Tue, 11 Jul 2000 11:39:28 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns1.sailpix.com (8.8.8/8.6.9) id HAA10150; Tue, 11 Jul 2000 07:34:08 -0700 (PDT)
Received: from master.crimea.net (Master.crimea.net [212.3.116.70]) by ns1.sailpix.com (8.8.8/8.6.9) with SMTP id HAA10146 for <l2tp@ipsec.org>; Tue, 11 Jul 2000 07:32:12 -0700 (PDT)
From: artz@crimea.net
Received: (qmail 862 invoked by uid 100); 11 Jul 2000 14:28:58 -0000
Message-ID: <20000711142858.861.qmail@master.crimea.net>
Subject: q: l2tpd
To: l2tp@ipsec.org
Date: Tue, 11 Jul 2000 17:28:58 +0300 (EEST)
Reply-To: artz@crimea.net
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=KOI8-R
Content-Transfer-Encoding: 8bit
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 8bit

Hello all,

I'm trying to set up L2TP between linux and RedbackSMS boxes.
Linux box should work as LNS
On linux I set up Spencer's l2tpd with following config:

[global]                        ; Global parameters:
port = 1701                     ; * Bind to port 1701
auth file = /etc/l2tp/l2tp-secrets      ; * Where our challenge secrets are
access control = yes            ; * Refuse connections without IP match


[lns istop]                     ; Our fallthrough LNS definition
exclusive = no                  ; * Only permit one tunnel per host
ip range = 192.168.0.1-192.168.0.20   ; * Allocate from this IP range
no ip range = 192.168.0.3-192.168.0.9 ; * Except these hosts
lac = 10.10.240.2-10.10.240.3   ; * These can connect as LAC's
hidden bit = yes                ; * Use hidden AVP's?
local ip = 10.10.240.1          ; * Our local IP to use
length bit = yes                ; * Use length bit in payload?
require chap = yes              ; * Require CHAP auth. by peer
refuse pap = yes                ; * Refuse PAP authentication
refuse chap = no                ; * Refuse CHAP authentication
refuse authentication = no      ; * Refuse authentication altogether
require authentication = yes    ; * Require peer to authenticate
unix authentication = no        ; * Use /etc/passwd for auth.
name = istop                    ; * Report this as our hostname
ppp debug = yes                 ; * Turn on PPP debugging
call rws = 10                   ; * RWS for call (-1 is valid)
tunnel rws = 4                  ; * RWS for tunnel (must be > 0)
flow bit = yes                  ; * Include sequence numbers
challenge = no 

When I run l2tpd with debug and connect to Redback with PPPoE,
I have the following on my end of L2TP

network_thread: recv packet from 10.10.240.2, size = 172,
tunnel = 0, call = 0
packet dump: 
HEX: { 02 C8 AC 00 00 00 00 00 00 00 00 00 80 08 00 00 00 00 00 01 80 08 00 00 00 02 01 00 80 0A 00 00 00 03 00 00 00 01 80 0A 00 00 00 04 00 00 00 00 00 08 00 00 00 06 01 00 80 0E 00 00 00 07 6E 65 78 78 69 61 32 30 00 16 00 00 00 08 52 65 64 42 61 63 6B 20 4E 65 74 77 6F 72 6B 73 80 08 00 00 00 09 00 9B 80 08 00 00 00 0A 00 0A 00 0E 00 00 00 05 00 00 00 00 D4 8F 01 20 80 32 00 00 00 0B 65 3A 6E FC 54 E3 CD 52 28 EB EE 2B F3 25 5D 90 65 2E 51 CF F8 35 1B FC 1D 5D 48 24 8F 11 FD F4 4C EC 72 A0 D0 BF 72 F8 AB E0 A3 9F }
ASCII: {                                                               nexxia20      RedBack Networks                               2    e:n T  R(  + %] e.Q  5   ]H$    L r   r     }
get_call: allocating new tunnel for host 10.10.240.2, port 1701.
check_control: control, cid = 0, Ns = 0, Nr = 0
handle_avps: handling avp's for tunnel 17767, call 0
message_type_avp: message type 1 (Start-Control-Connection-Request)
protocol_version_avp: peer is using version 1, revision 0.
framing_caps_avp: supported peer frames: sync
: supported peer bearers:
€
firmware_rev_avp: peer reports firmware version 256 (0x0100)
hostname_avp: peer reports hostname 'nexxia20'
vendor_avp: peer reports vendor 'RedBack Networks'
assigned_tunnel_avp: using peer's tunnel 155
receive_window_size_avp: peer wants RWS of 10.  Will use flow control.
handle_avps:  no handler for atribute 5 (Tie Breaker).
challenge_avp: challenge avp found
control_finish: message type is Start-Control-Connection-Request(1).  Tunnel is 155, call is 0.
get_lns: Rule 10.10.240.2 to 10.10.240.2, sense allow matched 10.10.240.2
packet dump:
HEX: { C8 02 00 9C 00 9B 00 00 00 00 00 01 80 08 00 00 00 00 00 02 80 16 00 00 00 24 73 48 33 66 51 DC B0 74 FF 5C 49 19 4A 94 E8 2A 80 08 00 00 00 02 01 00 80 0A 00 00 00 03 00 00 00 03 80 0A 00 00 00 04 00 00 00 00 00 08 00 00 00 06 05 00 80 15 00 00 00 07 69 70 32 35 32 2E 69 73 74 6F 70 2E 63 6F 6D 00 13 00 00 00 08 41 64 74 72 61 6E 2C 20 6C 32 74 70 64 80 08 00 00 00 09 45 67 80 08 00 00 00 0A 00 04 80 16 00 00 00 0D 46 99 6E BA 85 FC 2A A9 A2 3A CA 37 30 B7 26 C1 }
ASCII: {                          $sH3fQ  t \I J  *                                          ip252.istop.com      Adtran, l2tpd      Eg              F n   *  : 70 & }
control_finish: sending SCCRP
network_thread: recv packet from 10.10.240.2, size = 20,
tunnel = 17767, call = 0
packet dump: 
HEX: { 02 C8 14 00 67 45 00 00 01 00 01 00 80 08 00 00 00 00 00 03 }
ASCII: {     gE              }
check_control: control, cid = 0, Ns = 1, Nr = 1
handle_avps: handling avp's for tunnel 17767, call 0
message_type_avp: message type 3 (Start-Control-Connection-Connected)
control_finish: message type is Start-Control-Connection-Connected(3).  Tunnel is 155, call is 0.
control_finish: Connection established to 10.10.240.2, 1701.  Local: 17767, Remote: 155.  LNS session is 'istop'
control_finish: scheduling initial HELLO on 17767
control_zlb: sending control ZLB on tunnel 155
network_thread: recv packet from 10.10.240.2, size = 58,
tunnel = 17767, call = 0
packet dump:
HEX: { 02 C8 3A 00 67 45 00 00 02 00 01 00 80 08 00 00 00 00 00 0A 80 08 00 00 00 0E 00 AC 80 0A 00 00 00 0F 00 00 E2 E1 80 0A 00 00 00 12 00 00 00 01 80 0A 00 00 00 19 07 00 07 AC }
ASCII: {   : gE                                                    }
check_control: control, cid = 0, Ns = 2, Nr = 1
handle_avps: handling avp's for tunnel 17767, call 0
message_type_avp: message type 10 (Incoming-Call-Request)
message_type_avp: new incoming call
assigned_call_avp: using peer's call 172
call_serno_avp: serial number is 58081
bearer_type_avp: peer bears:digital
call_physchan_avp: physical channel is 117442476
control_finish: message type is Incoming-Call-Request(10).  Tunnel is 155, call is 0.
encrypt_avp: The digest to be XOR'ed
bufferDump: buflen=16, buffer[0]: *334b6e33e41bdb1c3b97307dd1280181*
encrypt_avp: The plaintext to be XOR'ed
bufferDump: buflen=16, buffer[0]: *000258ec000000000000000000000000*
encrypt_avp: The result of XOR
bufferDump: buflen=16, buffer[0]: *334936dfe41bdb1c3b97307dd1280181*
packet dump: 
HEX: { C8 02 00 48 00 9B 00 AC 00 01 00 03 80 08 00 00 00 00 00 0B 80 16 00 00 00 24 29 1F 8E 23 CD 7C E8 46 BA 58 1B 3D AB D7 7E 50 C0 16 00 00 00 0E 33 49 36 DF E4 1B DB 1C 3B 97 30 7D D1 28 01 81 80 08 00 00 00 0A 00 0A }
ASCII: {    H                     $)  # | F X =  ~P      3I6     ; 0} (          }
control_finish: Sending ICRP
control_zlb: sending control ZLB on tunnel 155
network_thread: recv packet from 10.10.240.2, size = 185,
tunnel = 17767, call = 50508
packet dump:
HEX: { 02 C8 B9 00 67 45 4C C5 03 00 02 00 80 08 00 00 00 00 00 0C 00 16 00 00 00 1A 02 06 00 00 00 00 00 00 00 00 05 06 00 00 F8 BA 00 14 00 00 00 1B 01 04 05 D4 03 04 C0 23 05 06 04 1B DE E3 00 10 00 00 00 1C 01 04 05 D4 05 06 00 00 F8 BA 00 08 00 00 00 1D 00 03 00 08 00 00 00 20 00 01 80 25 00 00 00 24 23 64 42 3F 4F 84 ED 15 3E 8D EF 2E D8 3B 29 F9 16 A4 D4 8B 8E 51 59 3A 70 EE 17 89 FC FD 5D 40 1C 00 00 00 1E 77 31 C1 90 3A 39 D1 A7 01 8B 01 D9 49 E6 B8 F1 58 ED 93 2C B3 D4 80 06 00 00 00 21 80 0A 00 00 00 13 00 00 00 01 80 0A 00 00 00 18 00 00 4B 00 }
ASCII: {     gEL                                                #                                       %   $#dB?O   >  . ;)      QY:p     ]@     w1  :9      I   X  ,       !                  K }
get_call: can't find call 50508 in tunnel 17767
DEBUG: tunnel=17767, tunnels.head=134622816, st->ourtid=17767, sc=st->call_head: 0
network_thread: no such call 1073783288 on tunnel 134517196.  Sending special ZLB
check_control: control, cid = 50508, Ns = 3, Nr = 2
control_zlb: sending control ZLB on tunnel 155
network_thread: recv packet from 10.10.240.2, size = 39,
tunnel = 17767, call = 50508
packet dump: 
HEX: { 02 48 27 00 67 45 4C C5 00 00 00 00 FF 03 C0 23 01 02 00 17 11 73 74 61 74 69 70 31 40 69 73 74 6F 70 2E 63 6F 6D 00 }
ASCII: {  H' gEL        #     testuser@istop.com }
get_call: can't find call 50508 in tunnel 17767
DEBUG: tunnel=17767, tunnels.head=134622816, st->ourtid=17767, sc=st->call_head: 0
network_thread: no such call 1073783288 on tunnel 134517196.  Sending special ZLB
network_thread: recv packet from 10.10.240.2, size = 39,
tunnel = 17767, call = 50508
packet dump:
HEX: { 02 48 27 00 67 45 4C C5 01 00 00 00 FF 03 C0 23 01 03 00 17 11 73 74 61 74 69 70 31 40 69 73 74 6F 70 2E 63 6F 6D 00 }
ASCII: {  H' gEL        #     testuser@istop.com }
get_call: can't find call 50508 in tunnel 17767
DEBUG: tunnel=17767, tunnels.head=134622816, st->ourtid=17767, sc=st->call_head: 0
network_thread: no such call 1073783288 on tunnel 134517196.  Sending special ZLB
network_thread: recv packet from 10.10.240.2, size = 39,
tunnel = 17767, call = 50508
packet dump: 
HEX: { 02 48 27 00 67 45 4C C5 02 00 00 00 FF 03 C0 23 01 04 00 17 11 73 74 61 74 69 70 31 40 69 73 74 6F 70 2E 63 6F 6D 00 }
ASCII: {  H' gEL        #     testuser@istop.com }
get_call: can't find call 50508 in tunnel 17767
DEBUG: tunnel=17767, tunnels.head=134622816, st->ourtid=17767, sc=st->call_head: 0
network_thread: no such call 1073783288 on tunnel 134517196.  Sending special ZLB
network_thread: recv packet from 10.10.240.2, size = 39,
tunnel = 17767, call = 50508
packet dump: 
HEX: { 02 48 27 00 67 45 4C C5 03 00 00 00 FF 03 C0 23 01 05 00 17 11 73 74 61 74 69 70 31 40 69 73 74 6F 70 2E 63 6F 6D 00 }
ASCII: {  H' gEL        #     testuser@istop.com }
get_call: can't find call 50508 in tunnel 17767
DEBUG: tunnel=17767, tunnels.head=134622816, st->ourtid=17767, sc=st->call_head: 0
network_thread: no such call 1073783288 on tunnel 134517196.  Sending special ZLB
network_thread: recv packet from 10.10.240.2, size = 39,
tunnel = 17767, call = 50508
packet dump:
HEX: { 02 48 27 00 67 45 4C C5 04 00 00 00 FF 03 C0 23 01 06 00 17 11 73 74 61 74 69 70 31 40 69 73 74 6F 70 2E 63 6F 6D 00 }
ASCII: {  H' gEL        #     testuser@istop.com }
get_call: can't find call 50508 in tunnel 17767
DEBUG: tunnel=17767, tunnels.head=134622816, st->ourtid=17767, sc=st->call_head: 0
network_thread: no such call 1073783288 on tunnel 134517196.  Sending special ZLB
network_thread: recv packet from 10.10.240.2, size = 39,
tunnel = 17767, call = 50508
packet dump: 
HEX: { 02 48 27 00 67 45 4C C5 05 00 00 00 FF 03 C0 23 01 07 00 17 11 73 74 61 74 69 70 31 40 69 73 74 6F 70 2E 63 6F 6D 00 }
ASCII: {  H' gEL        #     testuser@istop.com }
get_call: can't find call 50508 in tunnel 17767
DEBUG: tunnel=17767, tunnels.head=134622816, st->ourtid=17767, sc=st->call_head: 0
network_thread: no such call 1073783288 on tunnel 134517196.  Sending special ZLB
network_thread: recv packet from 10.10.240.2, size = 24,
tunnel = 17767, call = 50508
packet dump: 
HEX: { 02 48 18 00 67 45 4C C5 06 00 00 00 FF 03 C0 21 09 01 00 08 00 00 F8 BA }
ASCII: {  H  gEL        !        }
get_call: can't find call 50508 in tunnel 17767
DEBUG: tunnel=17767, tunnels.head=134622816, st->ourtid=17767, sc=st->call_head: 0
network_thread: no such call 1073783288 on tunnel 134517196.  Sending special ZLB
network_thread: recv packet from 10.10.240.2, size = 39,
tunnel = 17767, call = 50508
packet dump:
HEX: { 02 48 27 00 67 45 4C C5 07 00 00 00 FF 03 C0 23 01 08 00 17 11 73 74 61 74 69 70 31 40 69 73 74 6F 70 2E 63 6F 6D 00 }
ASCII: {  H' gEL        #     testuser@istop.com }
get_call: can't find call 50508 in tunnel 17767
DEBUG: tunnel=17767, tunnels.head=134622816, st->ourtid=17767, sc=st->call_head: 0
network_thread: no such call 1073783288 on tunnel 134517196.  Sending special ZLB
network_thread: recv packet from 10.10.240.2, size = 39,
tunnel = 17767, call = 50508
packet dump: 
HEX: { 02 48 27 00 67 45 4C C5 08 00 00 00 FF 03 C0 23 01 09 00 17 11 73 74 61 74 69 70 31 40 69 73 74 6F 70 2E 63 6F 6D 00 }
ASCII: {  H' gEL        #     testuser@istop.com }
get_call: can't find call 50508 in tunnel 17767
DEBUG: tunnel=17767, tunnels.head=134622816, st->ourtid=17767, sc=st->call_head: 0
network_thread: no such call 1073783288 on tunnel 134517196.  Sending special ZLB
network_thread: recv packet from 10.10.240.2, size = 39,
tunnel = 17767, call = 50508
packet dump: 
HEX: { 02 48 27 00 67 45 4C C5 09 00 00 00 FF 03 C0 23 01 0A 00 17 11 73 74 61 74 69 70 31 40 69 73 74 6F 70 2E 63 6F 6D 00 }
ASCII: {  H' gEL        #     testuser@istop.com }
get_call: can't find call 50508 in tunnel 17767
DEBUG: tunnel=17767, tunnels.head=134622816, st->ourtid=17767, sc=st->call_head: 0
network_thread: no such call 1073783288 on tunnel 134517196.  Sending special ZLB
network_thread: recv packet from 10.10.240.2, size = 60,
tunnel = 17767, call = 50508
packet dump:
HEX: { 02 48 3C 00 67 45 4C C5 0A 00 00 00 FF 03 C0 21 05 03 00 2C 46 61 69 6C 65 64 20 74 6F 20 61 75 74 68 65 6E 74 69 63 61 74 65 20 6F 75 72 73 65 6C 76 65 73 20 74 6F 20 70 65 65 72 }
ASCII: {  H< gEL        !   ,Failed to authenticate ourselves to peer}
get_call: can't find call 50508 in tunnel 17767
DEBUG: tunnel=17767, tunnels.head=134622816, st->ourtid=17767, sc=st->call_head: 0
network_thread: no such call 1073783288 on tunnel 134517196.  Sending special ZLB
packet dump: 
HEX: { C8 02 00 14 00 9B 00 00 00 02 00 04 80 08 00 00 00 00 00 06 }
ASCII: {                     }
hello: sending Hello on 17767
hello: scheduling another Hello on 17767
Segmentation fault (core dumped)

So seems to tunnel established, Redback translate ppp auth request,
but l2tpd does not call pppd..



From owner-l2tp@ipsec.org  Tue Jul 11 14:26:35 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 OAA13992
	for <l2tpext-archive@odin.ietf.org>; Tue, 11 Jul 2000 14:26:34 -0400 (EDT)
Received: (from majordomo@localhost) by ns1.sailpix.com (8.8.8/8.6.9) id KAA10362; Tue, 11 Jul 2000 10:27:38 -0700 (PDT)
Received: from shako.cisco.com (shako.cisco.com [161.44.3.76]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id KAA10358 for <l2tp@ipsec.org>; Tue, 11 Jul 2000 10:27:18 -0700 (PDT)
Received: from cisco.com (ch-dhcp207-127.cisco.com [171.69.207.127])
	by shako.cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id NAA10239
	for <l2tp@ipsec.org>; Tue, 11 Jul 2000 13:26:34 -0400 (EDT)
Message-ID: <396B58DD.15C26D70@cisco.com>
Date: Tue, 11 Jul 2000 13:26:53 -0400
From: "W. Mark Townsley" <townsley@cisco.com>
X-Mailer: Mozilla 4.7 [en] (Win95; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: l2tp@ipsec.org
Subject: l2tpext agenda items
References: <14694.8094.801400.716907@stile.redback.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


I still do not know what time slot we have in PA, but these are the
agenda items I have on the list now. If there are any others, please let
me know.

The draft cutoff date is this Friday. If you plan on submitting any
drafts before the meeting, please get them in ASAP.

Thanks,

- Mark

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

Bernard Aboba, Skip Booth
draft-ietf-l2tpext-l2tp-security-01.txt

Danny McPherson
draft-mcpherson-l2tp-es-01.txt

Suhail Nanji
draft-nanji-l2tp-eth-00.txt

W. Mark Townsley
WG Draft Status
l2tpext Charter Revision Discussion
Goals and Milestones


From owner-l2tp@ipsec.org  Mon Jul 17 17:55:42 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 RAA04915
	for <l2tpext-archive@odin.ietf.org>; Mon, 17 Jul 2000 17:55:42 -0400 (EDT)
Received: (from majordomo@localhost) by ns1.sailpix.com (8.8.8/8.6.9) id NAA14823; Mon, 17 Jul 2000 13:31:31 -0700 (PDT)
Received: from mailman.cisco.com (mailman.cisco.com [171.68.225.9]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id NAA14819 for <l2tp@ipsec.org>; Mon, 17 Jul 2000 13:30:46 -0700 (PDT)
Received: from anfreema-pc (dhcp-l21-163.cisco.com [171.68.210.163])
	by mailman.cisco.com (8.9.3/8.9.1) with SMTP id NAA28619;
	Mon, 17 Jul 2000 13:30:12 -0700 (PDT)
Message-Id: <200007172030.NAA28619@mailman.cisco.com>
X-Sender: anfreema@sj-email
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.2 
Date: Mon, 17 Jul 2000 13:27:54 -0700
To: l2tp@ipsec.org, ietf-ppp@merit.edu, ipsec@lists.tislabs.com
From: Anita Freeman <anfreema@cisco.com>
Subject: Application available for Sept 2000 VPN Interoperability
  Workshop
Mime-Version: 1.0
Content-Type: multipart/alternative;
	types="text/plain,text/html";
	boundary="=====================_7250544==_.ALT"
Sender: owner-l2tp@ipsec.org
Precedence: bulk

--=====================_7250544==_.ALT
Content-Type: text/plain; charset="us-ascii"

The application for the September 2000 VPN Interoperability Workshop is now
available at:

http://www.calbug.org:8080/vpnworkshop/

The deadline for the VPN workshop application and hotel reservations is
August 15, 2000.

The VPN Interoperability Workshop will be held September 18-22, 2000, at the
Paradise Point Resort in San Diego, California.

The VPN Workshop is being sponsored by VeriSign, SSH, Hi/fn, WindRiver,
Entrust, Nokia, Alcatel, RedBack, Microsoft, Cisco, and UUNET, a Worldcom
Company.

The protocols being tested at this workshop are:

IPsec
IKE
IPComp
L2TP over Transport-Mode IPsec
PPTP
PPPoE
PPPoATM
L2TPoATM

Hotel reservations may be made by calling Paradise Point Resort at
800-344-2626.  Please register under the VPN Workshop room block for
the discounted rate of $159 per night (plus tax).

If you cannot access the web site above, please send an email to me and I will
forward a text version of the application.

Thanks, Anita Freeman

--=====================_7250544==_.ALT
Content-Type: text/html; charset="us-ascii"

<html>
The application for the September 2000 VPN Interoperability Workshop is
now<br>
available at:<br>
<br>
<a href="http://www.calbug.org:8080/vpnworkshop/" eudora="autourl">http://www.calbug.org:8080/vpnworkshop/</a><br>
<br>
The deadline for the VPN workshop application and hotel reservations
is<br>
August 15, 2000.<br>
<br>
The VPN Interoperability Workshop will be held September 18-22, 2000, at
the<br>
Paradise Point Resort in San Diego, California.<br>
<br>
The VPN Workshop is being sponsored by VeriSign, SSH, Hi/fn, WindRiver,
Entrust, Nokia, Alcatel, RedBack, Microsoft, Cisco, and UUNET, a Worldcom
Company.<br>
<br>
The protocols being tested at this workshop are:<br>
<br>
IPsec<br>
IKE<br>
IPComp<br>
L2TP over Transport-Mode IPsec<br>
PPTP<br>
PPPoE<br>
PPPoATM<br>
L2TPoATM<br>
<br>
Hotel reservations may be made by calling Paradise Point Resort at<br>
800-344-2626.&nbsp; Please register under the <b>VPN Workshop</b> room
block for<br>
the discounted rate of $159 per night (plus tax).<br>
<br>
If you cannot access the web site above, please send an email to me and I
will forward a text version of the application.<br>
<br>
Thanks, Anita Freeman<br>
</html>

--=====================_7250544==_.ALT--



From owner-l2tp@ipsec.org  Tue Jul 18 05:04:59 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 FAA13840
	for <l2tpext-archive@odin.ietf.org>; Tue, 18 Jul 2000 05:04:58 -0400 (EDT)
Received: (from majordomo@localhost) by ns1.sailpix.com (8.8.8/8.6.9) id BAA15480; Tue, 18 Jul 2000 01:11:05 -0700 (PDT)
Received: from enterprise.reliacom.com (enterprise.reliacom.com [209.249.101.16]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id BAA15476 for <l2tp@ipsec.org>; Tue, 18 Jul 2000 01:10:50 -0700 (PDT)
Received: by enterprise.reliacom.com with Internet Mail Service (5.5.2448.0)
	id <N594S08X>; Tue, 18 Jul 2000 04:07:38 -0400
Message-ID: <30D269155F5DD311A2620008C709AC5E8FA957@enterprise.reliacom.com>
From: Scot Kight <skight@reliacom.com>
To: l2tp@ipsec.org
Subject: IPSEC/L2TP on cisco and win2k
Date: Tue, 18 Jul 2000 04:07:32 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="KOI8-R"
Sender: owner-l2tp@ipsec.org
Precedence: bulk

Has anyone here successfully gotten a win2k box to connect to a cisco router
( something like a 3660) with a nat firewall on it?
I am having one heck of a time getting it to work, and really would like a
bit of help..

If you have any working configs, please let me know.  Currently I get a
policy mismatch error, but have tried the microsoft suggested policy, with
no luck. 

Systems are dialup to random ISPs, connecting to a single router providing
ipsec secured l2tp services, they need to get to the internal network on the
router.  Router has 2 interfaces in use, eth1/0 and fe3/1..

Scot Kight


From owner-l2tp@ipsec.org  Wed Jul 19 07:38:42 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 HAA16722
	for <l2tpext-archive@odin.ietf.org>; Wed, 19 Jul 2000 07:38:41 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns1.sailpix.com (8.8.8/8.6.9) id DAA19289; Wed, 19 Jul 2000 03:36:33 -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 DAA19284 for <l2tp@ipsec.org>; Wed, 19 Jul 2000 03:35:10 -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 GAA21191;
	Wed, 19 Jul 2000 06:34:59 -0400 (EDT)
Message-Id: <200007191034.GAA21191@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-fr-00.txt
Date: Wed, 19 Jul 2000 06:34:59 -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		: Layer Two Tunneling Protocol (L2TP) over Frame Relay
	Author(s)	: V. Rawat, R. Tio, R. Verma
	Filename	: draft-ietf-l2tpext-fr-00.txt
	Pages		: 7
	Date		: 18-Jul-00
	
Layer Two Tunneling Protocol describes a mechanism to
tunnel PPP sessions.  The protocol has been designed to be
independent of the media it runs over. The base
specification describes how it should be implemented to
run over UDP and IP. This document describes how the Layer
Two Tunneling Protocol MUST be implemented over Frame
Relay PVCs and SVCs.

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

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

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

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

--OtherAccess--

--NextPart--




From owner-l2tp@ipsec.org  Wed Jul 19 07:39:35 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 HAA17091
	for <l2tpext-archive@odin.ietf.org>; Wed, 19 Jul 2000 07:39:34 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns1.sailpix.com (8.8.8/8.6.9) id DAA19288; Wed, 19 Jul 2000 03:36:28 -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 DAA19280 for <l2tp@ipsec.org>; Wed, 19 Jul 2000 03:35:05 -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 GAA21231;
	Wed, 19 Jul 2000 06:35:03 -0400 (EDT)
Message-Id: <200007191035.GAA21231@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-atmext-03.txt
Date: Wed, 19 Jul 2000 06:35:03 -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		: Layer Two Tunnelling Protocol : ATM access network 
                          extensions.
	Author(s)	: Y. T'Joens, P. Crivellari, B. Sales
	Filename	: draft-ietf-l2tpext-atmext-03.txt
	Pages		: 19
	Date		: 18-Jul-00
	
L2TP [RFC2661] specifies a protocol which permits the tunnelling of
the link layer of PPP over packet based networks, to support remote
access (mainly) by ISDN and PSTN networks. This document augments the
procedures described in [RFC2661] to further support ATM SVC or PVC
based access networks. The extensions defined within this document
allow for asymmetric bi-directional call establishment and service
selection in the ATM access network.

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

ENCODING mime
FILE /internet-drafts/draft-ietf-l2tpext-atmext-03.txt

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

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

--OtherAccess--

--NextPart--




From owner-l2tp@ipsec.org  Thu Jul 20 08:00:35 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 IAA21417
	for <l2tpext-archive@odin.ietf.org>; Thu, 20 Jul 2000 08:00:32 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns1.sailpix.com (8.8.8/8.6.9) id DAA21711; Thu, 20 Jul 2000 03:53:26 -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 DAA21706 for <l2tp@ipsec.org>; Thu, 20 Jul 2000 03:52:04 -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 GAA11627;
	Thu, 20 Jul 2000 06:46:12 -0400 (EDT)
Message-Id: <200007201046.GAA11627@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-l2tp-atm-01.txt
Date: Thu, 20 Jul 2000 06:46:12 -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 Over AAL5 and FUNI
	Author(s)	: M. Davison, A. Lin, A. Singh, J. Stephens, 
                          R. Turner, R. Tio, J. Senthilnathan
	Filename	: draft-ietf-l2tpext-l2tp-atm-01.txt
	Pages		: 11
	Date		: 19-Jul-00
	
The Layer Two Tunneling Protocol (L2TP) [1] provides a standard    
method for transporting the link layer of PPP [2] between a dial-up    
server and a Network Access Server, using a network connection in     
lieu of a physical point to point connection.  This document 
describes the use of an ATM network for the underlying network 
connection. Both ATM UNI [3] with ATM Adaptation Layer 5 [4]  
(AAL5) and ATM with Frame based User-to-Network Interface (FUNI) 
[5] are supported as interfaces to the ATM network.

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

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

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


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

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

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

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

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

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

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

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

--OtherAccess--

--NextPart--




From owner-l2tp@ipsec.org  Thu Jul 20 08:02: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 IAA22171
	for <l2tpext-archive@odin.ietf.org>; Thu, 20 Jul 2000 08:02:02 -0400 (EDT)
Received: (from majordomo@localhost) by ns1.sailpix.com (8.8.8/8.6.9) id DAA21710; Thu, 20 Jul 2000 03:53:19 -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 DAA21702 for <l2tp@ipsec.org>; Thu, 20 Jul 2000 03:51:58 -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 GAA11680;
	Thu, 20 Jul 2000 06:46:16 -0400 (EDT)
Message-Id: <200007201046.GAA11680@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-l2tpbis-00.txt
Date: Thu, 20 Jul 2000 06:46:16 -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		: Layer Two Tunneling Protocol 'L2TP'
	Author(s)	: W. Townsley, A. Valencia, A. Rubens, G. Pall, G. Zorn
                          B. Palter
	Filename	: draft-ietf-l2tpext-l2tpbis-00.txt
	Pages		: 76
	Date		: 19-Jul-00
	
This document describes the Layer Two Tunneling Protocol (L2TP).  RFC
1661 specifies multi-protocol access via PPP [RFC1661].  L2TP
facilitates the tunneling of PPP packets across an intervening
network in a way that is as transparent as possible to both end-users
and applications

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

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

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

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

--OtherAccess--

--NextPart--




From owner-l2tp@ipsec.org  Thu Jul 20 15:56:35 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 PAA27808
	for <l2tpext-archive@odin.ietf.org>; Thu, 20 Jul 2000 15:56:34 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns1.sailpix.com (8.8.8/8.6.9) id LAA22214; Thu, 20 Jul 2000 11:51:05 -0700 (PDT)
Received: from shako.cisco.com (shako.cisco.com [161.44.3.76]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id LAA22203 for <l2tp@ipsec.org>; Thu, 20 Jul 2000 11:48:15 -0700 (PDT)
Received: from shako.cisco.com (shako.cisco.com [161.44.3.76])
	by shako.cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id OAA22899
	for <l2tp@ipsec.org>; Thu, 20 Jul 2000 14:47:25 -0400 (EDT)
Date: Thu, 20 Jul 2000 14:47:24 -0400 (EDT)
From: "W. Mark Townsley" <townsley@cisco.com>
To: l2tp@ipsec.org
Subject: Change detail for l2tpbis
Message-ID: <Pine.GSO.4.10.10007201445520.22264-100000@shako.cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-l2tp@ipsec.org
Precedence: bulk


Here is a summary of the most significant changes to RFC 2661 that 
was recently posted as draft-ietf-l2tpext-l2tpbis-00.txt. Not every 
small editorial change is identified here. To get a full 
representation of all changes, I recommend using wdiff. 

http://www.iro.umontreal.ca/contrib/wdiff

Each numbered change contains a description, and an excerpt from the text. 
(actual text) means that the new text from l2tpbis is included 
(wdiff) means that the wdiff output is included
I included actual text in cases where I felt the changes were 
significant enough (and thus the wdiff output cluttered enough) to 
inhibit clear reading of the new text.

#1 Offset field calculation clarification, new recommended maximum 
suggestion (actual text).

Section 3.1

   The Offset Size field specifies the number of octets past the L2TP
   header at which the payload data is expected to start. If the offset
   field is present, the L2TP header ends after the last octet of the
   offset padding. The offset field itself is considered part of the
   l2tp header, not part of the offset padding. Thus, an offset field
   with a value of zero will add two octets to the header length.
   Actual data within the offset padding is undefined. A recommended
   maximum for the offset value is 7, which allows for 8 octet
   alignment.

#2 New Error code for directing LAC to another LNS (actual text). Yes,
I see the "an comma" typo. 

Section 4.4.2

      9 - Try another directed. If the LNS is aware of other possible
          destinations, it should inform the LAC. The Error Message
          MUST contain an comma separated list of addresses for the LAC
          to choose from. If the L2TP transport is IPv4, then this would
          be a comma separated list of IP addresses in the canonical
          dotted-decimal format. i.e. "10.0.0.1, 10.0.0.2, 10.0.0.3"
          If there are no servers for the LNS to suggest, then Error
          Code 7 should be used. The delimiter between addresses MUST be
          precisely a single comma and a single space.

#3 Suggestion for vendor specific AVP to further clarify a general vendor error. (wdiff)

      When a General Error Code of 6 is used, additional information
      about the error SHOULD be included in the Error Message field.
      {+Further, a vendor specific AVP MAY be sent to indicate the problem
      more precisely.+}

#4 New Framing Capabilites, Bearer Capabilities, Framing Type and Bearer Type text. Most 
significant her is a new 'V' bit for a virtual Bearer, as well as clarificaiton of what
the Bearer and Framing Capabilities refer to. Specifically, Bearer and Framing Capabilities
are now defined as pertaining ONLY to the physical interfaces avaiable for dialout. We
had fundamental problems in the field determining whether these AVPs referred to
the ability of an LAC to place a call, or the LNS to terminate a specific framing or 
bearer type. One AVP cannot be used to specify both. We can consider having two AVPs here,
one for dialout and one for dialin if deemed necessary (actual text). 

Section 4.4.3

   Framing Capabilities (SCCRP, SCCRQ)

      The Framing Capabilities AVP, Attribute Type 3, provides the peer
      with an indication of the types of framing that will be accepted
      or requested by the sender.

      The Attribute Value field for this AVP has the following format:

       0                   1                   2                   3
       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |     Reserved for future framing type definitions          |A|S|
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

      The Attribute Value field is a 32-bit mask, with two bits defined.
      If bit A is set, asynchronous framing is supported. If bit S is
      set, synchronous framing is supported.

      The framing capabilitiies defined in this AVP refer only to the
      physical interfaces available for dialout usage on an LAC. An LNS
      MUST not send an OCRQ with a Framing Type AVP specifying a value
      not advertised in this AVP.  Presence of this message is not a
      guarantee that a given outgoing call will be placed by the sender
      if requested, just that the physical capability exists.

      This AVP may be hidden (the H-bit may be 0 or 1). The M-bit for
      this AVP MUST be set to 1.  The Length (before hiding) is 10.

   Bearer Capabilities (SCCRP, SCCRQ)

      The Bearer Capabilities AVP, Attribute Type 4, provides the peer
      with an indication of the bearer device types supported by the
      hardware interfaces of the sender for outgoing calls.

      The Attribute Value field for this AVP has the following format:

       0                   1                   2                   3
       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |     Reserved for future bearer type definitions         |V|A|D|
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

      This is a 32-bit mask, with two bits defined. If bit A is set,
      analog access is supported. If bit D is set, digital access is
      supported.  Bit V is set, virtual acces is supported. Virtual
      access refers to access where there is no physical point to point
      link.

      The framing capabilitiies defined in this AVP refer only to the
      physical interfaces available for dialout usage on an LAC. An LNS
      MUST not send an OCRQ with a Bearer Type AVP specifying a value
      not advertised in this AVP.

      This AVP MUST be present if the sender can place outgoing calls
      when requested. Presence of this message is not a guarantee that a
      given outgoing call will be placed by the sender if requested,
      just that the physical capability exists.

      This AVP may be hidden (the H-bit may be 0 or 1). The M-bit for
      this AVP MUST be set to 1.  The Length (before hiding) is 10.

   Bearer Type (ICRQ, OCRQ)

      The Bearer Type AVP, Attribute Type 18,  encodes the bearer type
      for the incoming or outgoing call.

      The Attribute Value field for this AVP has the following format:

       0                   1                   2                   3
       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |           Reserved for future Bearer Types              |V|A|D|
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

      The Bearer Type is a 32-bit bit mask indicating the bearer
      capability of the call (ICRQ) or required for the call (OCRQ). Bit
      A refers to an analog channel. Bit D refers to a digital channel.
      Bit V (virtual) refers to a channel for which there is no physical
      point to point link.

      Bits set in the Bearer Type AVP in an OCRQ message indicate which
      bearer type(s) an outgoing call may be placed on.  If more than
      one bit is set, the LAC may choose which bearer type to place the
      call on. If no bits are set, any type of available channel may be
      used.

      Bits in the Value field of this AVP MUST only be set by the LNS
      for an OCRQ if the same bit was set in the Bearer Capabilities AVP
      received from the LAC during control connection establishment.

      Bits set in the Bearer Type AVP in an ICRQ message indicate what
      bearer type an incoming call was received on at the LAC. If no
      bits are set in an ICRQ, then it is assumed that the bearer type
      was indeterminable.

      This AVP may be hidden (the H-bit may be 0 or 1). The M-bit for
      this AVP MUST be set to 1.  The Length (before hiding) of this AVP
      is 10.

   Framing Type (ICCN, OCCN, OCRQ)

      The Framing Type AVP, Attribute Type 19, encodes the framing type
      for the incoming or outgoing call.

      The Attribute Value field for this AVP has the following format:

       0                   1                   2                   3
       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |           Reserved for future Framing Types               |A|S|
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

      The Framing Type is a 32-bit mask, which indicates the type of PPP
      framing requested for an OCRQ, or the type of PPP framing
      negotiated for an OCCN or ICCN.

      Bit A indicates asynchronous framing. Bit S indicates synchronous
      framing. For an OCRQ, both may be set, indicating that the LAC may
      decide the type of framing to be used.

      For an ICRQ, only one framing type bit may be set. The framing
      type SHOULD be used as an indication to PPP on the LNS as to what
      link options to use for LCP negotiation [RFC1662]. For example, if
      the A bit is not set in the Framing Type AVP in an ICRQ message
      and an ACCM LCP option is requested by the PPP client, then the
      LNS should try to respond with no bits set in the ACCM mask as the
      LAC will likely not perform async mapping on a non-async
      interface. Similarly, if the S bit is set, PPP may wish to reject
      address field compression and protocol field compression options.

      Bits in the Value field of this AVP MUST only be set by the LNS
      for an OCRQ if it was set in the Framing Capabilities AVP received
      from the LAC during control connection establishment.

      This AVP may be hidden (the H-bit may be 0 or 1). The M-bit for
      this AVP MUST be set to 1.  The Length (before hiding) of this AVP
      is 10.

#5 Clarification as to what 0 connect speed means. (wdiff)

   (Tx) Connect Speed (ICCN, OCCN)

      The (Tx) Connect Speed BPS AVP, Attribute Type 24, encodes the
      speed of the facility chosen for the connection attempt.

      The Attribute Value field for this AVP has the following format:

       0                   1                   2                   3
       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |                             BPS                               |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

      The (Tx) Connect Speed BPS is a 4 octet value indicating the speed
      in bits per second. {+A value of zero indicates that the speed is
      indeterminable, or there is no physical point to point link.+}

   Rx Connect Speed (ICCN, OCCN)

      The Rx Connect Speed AVP, Attribute Type 38, represents the speed
      of the connection from the perspective of the LAC (e.g. data
      flowing from the remote system to the LAC).

      The Attribute Value field for this AVP has the following format:

       0                   1                   2                   3
       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      |           BPS (H)             |            BPS (L)            |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

      BPS is a 4 octet value indicating the speed in bits per second. {+A
      value of zero indicates that the speed is indeterminable, or there
      is no physical point to point link.+}

#6 Reliable transport optimizations (wdiff)

Section 5.8

   The last received message number, Nr, is used to acknowledge messages
   received by an L2TP peer. It contains the sequence number of the
   message the peer expects to receive next (e.g. the last Ns of a non-
   ZLB message received plus 1, modulo 65536).  While the Nr in a
   received ZLB is used to flush messages from the local retransmit
   queue (see below), Nr of the next message sent is not be updated by
   the Ns of the ZLB. {+As a precaution, Nr should be sanity checked
   before flushing the retransmit queue. e.g. if the Nr received in a
   control message is greater than the last Ns sent plus 1 modulo 65536,
   it is clearly invalid.+}

   The reliable transport at a receiving peer is responsible for making
   sure that control messages are delivered in order and without
   duplication to the upper level. Messages arriving out of order may be
   queued for in-order delivery when the missing messages are received,
   or they may be discarded requiring a retransmission by the peer. {+When
   dropping out of order control packets, Nr MAY be updated before the
   packet is discarded.+}

#7 New text to help prevent race condition at the LAC between receipt
of an SLI and application to the data packets. Further, the SLI MUST now
be sent to the LAC if PPP renegotiation occurs at the LNS (actual text).

6.14 Set-Link-Info (SLI)

   The Set-Link-Info message is an L2TP control message sent by the LNS
   to the LAC after the last LCP Conf ACK is received during PPP LCP
   negotation. This AVP contains any relevant link level parameters that
   the LAC may need to be aware of (for instance, ACCM map info). If
   there is no relevant information to be sent in the SLI, then it MAY
   be omitted.  Since LCP may be renegotiated at any time, an SLI may be
   sent at any time during the life of the call, thus the LAC MUST be
   able to update its internal call information and behavior on an
   active session.  Further, if there are packets in queue at the LAC
   when an SLI is received, these must be flushed before applying the
   SLI information to the link.

   If the PPP session at the LNS renegotiates LCP during the call, an
   SLI MUST be sent to the LAC to return link level information to the
   initial default values while the negotiation occurs. However, if the
   last SLI sent was already set to default values or no SLI was sent at
   all, this step MAY be omitted.

#8 Relaxed requirements for IANA. Most of these are a change from requiring IETF Consensus, 
which requires us to wait until the RFC itself is about to be issued (e.g. after last call
and IESG review) to Expert Review, where the IESG identifies someone (such as an 
Editor or WG chair) to give the OK to obtain a value for IANA (actual text).  

10.1 AVP Attributes

   As defined in section 4.1, AVPs contain vendor ID, Attribute and
   Value fields. For vendor ID value of 0, IANA will maintain a registry
   of assigned Attributes and in some case also values. Attributes 0-39
   are assigned as defined in section 4.4. The remaining values are
   available for assignment upon Expert Review [RFC 2434].

10.2 Message Type AVP Values

   As defined in section 4.4.1, Message Type AVPs (Attribute Type 0)
   have an associated value maintained by IANA. Values 0-16 are defined
   in section 3.2, the remaining values are available for assignment
   upon Expert Review [RFC 2434]

10.3 Result Code AVP Values

   As defined in section 4.4.2, Result Code AVPs (Attribute Type 1)
   contain three fields.  Two of these fields (the Result Code and Error
   Code fields) have associated values maintained by IANA.

10.3.1 Result Code Field Values

   The Result Code AVP may be included in CDN and StopCCN messages. The
   allowable values for the Result Code field of the AVP differ
   depending upon the value of the Message Type AVP.  For the StopCCN
   message, values 0-7 are defined in section 4.4.2; for the CDN
   message, values 0-11 are defined in the same section.  The remaining
   values of the Result Code field for both messages are available for
   assignment upon Expert Review [RFC 2434].

10.3.2 Error Code Field Values

   Values 0-7 are defined in section 4.4.2.  Remaining values are
   available for assignment upon Expert Review [RFC 2434].

10.4 Framing Capabilities & Bearer Capabilities

   The Framing Capabilities AVP and Bearer Capabilities AVPs (defined in
   section 4.4.3) both contain 32-bit bitmasks. Additional bits should
   only be defined via a Standards Action [RFC 2434].

10.5 Proxy Authen Type AVP Values

   The Proxy Authen Type AVP (Attribute Type 29) has an associated value
   maintained by IANA. Values 0-5 are defined in section 4.4.5, the
   remaining values are available for assignment upon Expert Review [RFC
   2434].

10.6 AVP Header Bits

   There are four remaining reserved bits in the AVP header. Additional
   bits should only be assigned via a Standards Action [RFC 2434].







From owner-l2tp@ipsec.org  Sun Jul 23 22:48:54 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 WAA29729
	for <l2tpext-archive@odin.ietf.org>; Sun, 23 Jul 2000 22:48:54 -0400 (EDT)
Received: (from majordomo@localhost) by ns1.sailpix.com (8.8.8/8.6.9) id RAA29295; Sun, 23 Jul 2000 17:15:35 -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 RAA29291 for <l2tp@ipsec.org>; Sun, 23 Jul 2000 17:15:21 -0700 (PDT)
Received: from mira-sjcm-1.cisco.com (mira-sjcm-1.cisco.com [171.69.2.212])
	by sj-msg-core-2.cisco.com (8.9.3/8.9.1) with ESMTP id RAA22142
	for <l2tp@ipsec.org>; Sun, 23 Jul 2000 17:15:06 -0700 (PDT)
Received: from rockys-nt (dhcp-sjc9-233-201.cisco.com [171.71.233.201])
	by mira-sjcm-1.cisco.com (Mirapoint)
	with ESMTP id AIK35283;
	Sun, 23 Jul 2000 17:14:51 -0700 (PDT)
Message-Id: <4.2.0.58.20000723171120.00a7aec0@mira-sjcm-1.cisco.com>
X-Sender: rockys@mira-sjcm-1.cisco.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
Date: Sun, 23 Jul 2000 17:14:45 -0700
To: l2tp@ipsec.org
From: Tejinder Singh <rockys@cisco.com>
Subject: l2tp in linux
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-l2tp@ipsec.org
Precedence: bulk

Hello,

I need help for l2tp in linux, Is there any implementation for l2tp besides 
the one at this site http://www.marko.net/l2tp/.

I tried that one, and  I have had hard time bringing it up,  There is not 
much documentation on how to install or configure it.
I was trying to install it on 2.2.14 and 2.3.99 kernels.  And I have been 
unsuccessful in doing so.  If anybody else has implemented l2tp in linux, I 
would really appreciate there help.


Thanks
Tejinder Singh


From owner-l2tp@ipsec.org  Mon Jul 24 15:03:03 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 PAA01027
	for <l2tpext-archive@odin.ietf.org>; Mon, 24 Jul 2000 15:03:02 -0400 (EDT)
Received: (from majordomo@localhost) by ns1.sailpix.com (8.8.8/8.6.9) id LAA01680; Mon, 24 Jul 2000 11:00:35 -0700 (PDT)
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id LAA01676 for <l2tp@ipsec.org>; Mon, 24 Jul 2000 11:00:18 -0700 (PDT)
Received: from townsley-ultra.cisco.com (townsley-ultra.cisco.com [161.44.58.38])
	by sj-msg-core-1.cisco.com (8.9.3/8.9.1) with ESMTP id LAA17808;
	Mon, 24 Jul 2000 11:00:01 -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 NAA08029; Mon, 24 Jul 2000 13:59:45 -0400 (EDT)
Message-ID: <397C840A.277CA5F4@cisco.com>
Date: Mon, 24 Jul 2000 13:59:38 -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: Tejinder Singh <rockys@cisco.com>
CC: l2tp@ipsec.org
Subject: Re: l2tp in linux
References: <4.2.0.58.20000723171120.00a7aec0@mira-sjcm-1.cisco.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


If you are having trouble with l2tpd, try sending an email to
l2tpd@marko.net with your question.

- Mark

Tejinder Singh wrote:
> 
> Hello,
> 
> I need help for l2tp in linux, Is there any implementation for l2tp besides
> the one at this site http://www.marko.net/l2tp/.
> 
> I tried that one, and  I have had hard time bringing it up,  There is not
> much documentation on how to install or configure it.
> I was trying to install it on 2.2.14 and 2.3.99 kernels.  And I have been
> unsuccessful in doing so.  If anybody else has implemented l2tp in linux, I
> would really appreciate there help.
> 
> Thanks
> Tejinder Singh


From owner-l2tp@ipsec.org  Tue Jul 25 14:41:45 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 OAA26782
	for <l2tpext-archive@odin.ietf.org>; Tue, 25 Jul 2000 14:41:44 -0400 (EDT)
Received: (from majordomo@localhost) by ns1.sailpix.com (8.8.8/8.6.9) id KAA04590; Tue, 25 Jul 2000 10:34:50 -0700 (PDT)
Received: from brahma.roc.com ([203.197.21.148]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id KAA04586 for <l2tp@ipsec.org>; Tue, 25 Jul 2000 10:34:32 -0700 (PDT)
Received: from sridhar.roc.com ([172.16.5.52])
	by brahma.roc.com (8.8.5/8.8.5) with SMTP id XAA23005
	for <l2tp@ipsec.org>; Tue, 25 Jul 2000 23:09:27 +0530 (IST)
Message-Id: <200007251739.XAA23005@brahma.roc.com>
X-Sender: sridhar@172.16.1.10
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0
Date: Tue, 25 Jul 2000 23:12:14 +0530
To: l2tp@ipsec.org
From: Sridhar Malarothu <sridhar@trinc.com>
Subject: outgoing call req
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-l2tp@ipsec.org
Precedence: bulk

Hi,

   In RFC 2661, it is said that the LNS may send outgoing call
reuqest to LAC. Can any one explain the scenarios in which this
is send by LNS.

   Can LNS and LAC be present on the same system simultaneously ?     
 

Best Regards
Sridhar



From owner-l2tp@ipsec.org  Tue Jul 25 14:59:05 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 OAA01684
	for <l2tpext-archive@odin.ietf.org>; Tue, 25 Jul 2000 14:59:04 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns1.sailpix.com (8.8.8/8.6.9) id LAA04721; Tue, 25 Jul 2000 11:09:23 -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 LAA04717 for <l2tp@ipsec.org>; Tue, 25 Jul 2000 11:09:05 -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 MAA19510;
	Tue, 25 Jul 2000 12:08:53 -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 OAA21098;
	Tue, 25 Jul 2000 14:08:52 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.9.3+Sun/8.9.3) id OAA18309;
	Tue, 25 Jul 2000 14:08:54 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14717.55222.209558.175483@gargle.gargle.HOWL>
Date: Tue, 25 Jul 2000 14:08:54 -0400 (EDT)
From: James Carlson <james.d.carlson@east.sun.com>
To: Sridhar Malarothu <sridhar@trinc.com>
Cc: l2tp@ipsec.org
Subject: Re: outgoing call req
In-Reply-To: Sridhar Malarothu's message of 25 July 2000 23:12:14
References: <200007251739.XAA23005@brahma.roc.com>
X-Mailer: VM 6.75 under Emacs 20.7.1
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Sridhar Malarothu writes:
>    In RFC 2661, it is said that the LNS may send outgoing call
> reuqest to LAC. Can any one explain the scenarios in which this
> is send by LNS.

Dial on demand and dial-back (callback) are two common scenarios.
With dial-on-demand, you have a dummy interface route on the LNS
system.  When packets arrive on that interface, you initiate a call to
the remote network.  With callback, the user calls in, provides
credentials (and perhaps a callback number or location identifier),
and then disconnects so the LNS can call him back.

>    Can LNS and LAC be present on the same system simultaneously ?     

Sure.

-- 
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 Jul 25 16:19: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 QAA24417
	for <l2tpext-archive@odin.ietf.org>; Tue, 25 Jul 2000 16:19:07 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns1.sailpix.com (8.8.8/8.6.9) id LAA04869; Tue, 25 Jul 2000 11:58:44 -0700 (PDT)
Received: from ans2-pub.dttus.com ([204.151.11.3]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id LAA04855 for <l2tp@ipsec.org>; Tue, 25 Jul 2000 11:57:30 -0700 (PDT)
Received: by ans2-pub.dttus.com id NAA19643
  (InterLock SMTP Gateway 3.0 for l2tp@ipsec.org);
  Tue, 25 Jul 2000 13:57:08 -0500 (CDT)
Received: by ans2-pub.dttus.com (Internal Mail Agent-2);
  Tue, 25 Jul 2000 13:57:08 -0500 (CDT)
Received: by ans2-pub.dttus.com (Internal Mail Agent-1);
  Tue, 25 Jul 2000 13:57:08 -0500 (CDT)
Message-Id: <2F4A3F6B7BF5D3119E2500508B94E65601DB6C5C@uscntnt405.us.deloitte.com>
From: "Verma, Rohit (US - Chicago)" <rverma@dc.com>
To: Sridhar Malarothu <sridhar@trinc.com>, l2tp@ipsec.org
Subject: RE: outgoing call req
Date: Tue, 25 Jul 2000 13:53:33 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01BFF669.A1E76A40"
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_01BFF669.A1E76A40
Content-Type: text/plain;
	charset="iso-8859-1"

If a host on the network initiates a connection to a host outside a LAN. The
request may be serviced by an LNS as an outbound call to be placed out of a
modem bank attached to the LAC.

10.0.0.10                                                    192.0.0.10
+------+    +------+            +----+          +-----+       +------+
|Host 2|----|Dialup|----PSTN----|LAC |---ISP----| LNS |--LAN--|Host 1|
+------+    +------+            +----+          +-----+       +------+

In the above scenario Host 1 sends a connection initiation request to
10.0.0.10 the LNS detects it and realizes that it needs to request a tunnel
to the LAC. The LAC dials out on behalf of the LNS to the remote site.
Hope this helps.
Yes the LNS and the LAC may be on the same system simultaneously, I am not
sure of the scenario you will have them on other than a Tunnel Switch. When
incoming tunnels are switched to a second set of incoming tunnels.



Regards
-rv
-----Original Message-----
From: Sridhar Malarothu [mailto:sridhar@trinc.com]
Sent: Tuesday, July 25, 2000 1:42 PM
To: l2tp@ipsec.org
Subject: outgoing call req


Hi,

   In RFC 2661, it is said that the LNS may send outgoing call
reuqest to LAC. Can any one explain the scenarios in which this
is send by LNS.

   Can LNS and LAC be present on the same system simultaneously ?     
 

Best Regards
Sridhar

------_=_NextPart_001_01BFF669.A1E76A40
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: outgoing call req</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>If a host on the network initiates a connection to a =
host outside a LAN. The request may be serviced by an LNS as an =
outbound call to be placed out of a modem bank attached to the =
LAC.</FONT></P>

<P><FONT =
SIZE=3D2>10.0.0.10&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 192.0.0.10</FONT>
<BR><FONT SIZE=3D2>+------+&nbsp;&nbsp;&nbsp; =
+------+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; +----+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
+-----+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; +------+</FONT>
<BR><FONT SIZE=3D2>|Host 2|----|Dialup|----PSTN----|LAC |---ISP----| =
LNS |--LAN--|Host 1|</FONT>
<BR><FONT SIZE=3D2>+------+&nbsp;&nbsp;&nbsp; =
+------+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; +----+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
+-----+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; +------+</FONT>
</P>

<P><FONT SIZE=3D2>In the above scenario Host 1 sends a connection =
initiation request to 10.0.0.10 the LNS detects it and realizes that it =
needs to request a tunnel to the LAC. The LAC dials out on behalf of =
the LNS to the remote site.</FONT></P>

<P><FONT SIZE=3D2>Hope this helps.</FONT>
<BR><FONT SIZE=3D2>Yes the LNS and the LAC may be on the same system =
simultaneously, I am not sure of the scenario you will have them on =
other than a Tunnel Switch. When incoming tunnels are switched to a =
second set of incoming tunnels.</FONT></P>
<BR>
<BR>

<P><FONT SIZE=3D2>Regards</FONT>
<BR><FONT SIZE=3D2>-rv</FONT>
<BR><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Sridhar Malarothu [<A =
HREF=3D"mailto:sridhar@trinc.com">mailto:sridhar@trinc.com</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: Tuesday, July 25, 2000 1:42 PM</FONT>
<BR><FONT SIZE=3D2>To: l2tp@ipsec.org</FONT>
<BR><FONT SIZE=3D2>Subject: outgoing call req</FONT>
</P>
<BR>

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

<P><FONT SIZE=3D2>&nbsp;&nbsp; In RFC 2661, it is said that the LNS may =
send outgoing call</FONT>
<BR><FONT SIZE=3D2>reuqest to LAC. Can any one explain the scenarios in =
which this</FONT>
<BR><FONT SIZE=3D2>is send by LNS.</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp; Can LNS and LAC be present on the same =
system simultaneously ?&nbsp;&nbsp;&nbsp;&nbsp; </FONT>
<BR><FONT SIZE=3D2>&nbsp;</FONT>
</P>

<P><FONT SIZE=3D2>Best Regards</FONT>
<BR><FONT SIZE=3D2>Sridhar</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01BFF669.A1E76A40--


From owner-l2tp@ipsec.org  Tue Jul 25 17:12:53 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 RAA08731
	for <l2tpext-archive@odin.ietf.org>; Tue, 25 Jul 2000 17:12:52 -0400 (EDT)
Received: (from majordomo@localhost) by ns1.sailpix.com (8.8.8/8.6.9) id NAA05015; Tue, 25 Jul 2000 13:21:37 -0700 (PDT)
Received: from rambo.globespan.net (p1.globespan.net [209.191.59.250]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id NAA05011 for <l2tp@ipsec.org>; Tue, 25 Jul 2000 13:21:10 -0700 (PDT)
Received: by rambo with Internet Mail Service (5.5.2650.21)
	id <PH0YRYVL>; Tue, 25 Jul 2000 16:22:12 -0400
Received: from globespan.net (SRINIES [192.168.25.14]) by rambo.globespan.net with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id PH0YRYVJ; Tue, 25 Jul 2000 16:22:01 -0400
From: Srinivasan Seshadri <srinies@globespan.net>
To: James Carlson <james.d.carlson@east.sun.com>
Cc: Sridhar Malarothu <sridhar@trinc.com>, l2tp@ipsec.org
Message-ID: <397DF67F.387C628A@globespan.net>
Date: Tue, 25 Jul 2000 16:20:16 -0400
Organization: Globespan, Inc.
X-Mailer: Mozilla 4.51 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: outgoing call req
References: <200007251739.XAA23005@brahma.roc.com> <14717.55222.209558.175483@gargle.gargle.HOWL>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

The other scenario could be that a corporate web service is being accessed from
a CPE (Customer Premise Equipment) side. For ex, in the following situation,

  CPE ------ Central Office ---------
ISPa------------Internet----------ISPb---------Corporate End...
                                     (LAC)
(LNS)                                         (LNS)          (LAC)
A call from CPE to the corporate end will get routed via ISPb, from which the
LNS can trigger an outgoing call request to the LAC (once when the data packets
are to be sent to LAC), if it ever wants to aggregate multiple user side
requests to the corporate....

--Srinivasan.E.S.

James Carlson wrote:

> Sridhar Malarothu writes:
> >    In RFC 2661, it is said that the LNS may send outgoing call
> > reuqest to LAC. Can any one explain the scenarios in which this
> > is send by LNS.
>
> Dial on demand and dial-back (callback) are two common scenarios.
> With dial-on-demand, you have a dummy interface route on the LNS
> system.  When packets arrive on that interface, you initiate a call to
> the remote network.  With callback, the user calls in, provides
> credentials (and perhaps a callback number or location identifier),
> and then disconnects so the LNS can call him back.
>
> >    Can LNS and LAC be present on the same system simultaneously ?
>
> Sure.
>
> --
> 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  Wed Jul 26 00:59:59 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 AAA15917
	for <l2tpext-archive@odin.ietf.org>; Wed, 26 Jul 2000 00:59:58 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns1.sailpix.com (8.8.8/8.6.9) id VAA05828; Tue, 25 Jul 2000 21:02:30 -0700 (PDT)
Received: from amberex01.ambernetworks.com (207-33-177-98.ncal.verio.com [207.33.177.98] (may be forged)) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id VAA05823 for <l2tp@ipsec.org>; Tue, 25 Jul 2000 21:02:17 -0700 (PDT)
Received: by amberex01.ambernetworks.com with Internet Mail Service (5.5.2650.21)
	id <P4JA2BB5>; Tue, 25 Jul 2000 21:04:52 -0700
Message-ID: <50B17D03735BD411B2D000D0B7237DED36B3F9@amberex01.ambernetworks.com>
From: Danny McPherson <Danny@ambernetworks.com>
To: "'l2tp@ipsec.org'" <l2tp@ipsec.org>
Subject: L2TP charter
Date: Tue, 25 Jul 2000 21:04:51 -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


Reminder that we'll be discussing a charter extension at the meeting next
week.  The general goal is to explicitly extend the WG to include protocols
other than the current implicitly assumed PPP-only L2TP model.  If there's
any opposition to this I'd really like to discuss it on the list beforehand
if possible.

With the current round of modifications proposed for RFC2661, the timing is
indeed opportune.
 
Thanks!

-danny  


From owner-l2tp@ipsec.org  Wed Jul 26 07:11:40 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 HAA08996
	for <l2tpext-archive@odin.ietf.org>; Wed, 26 Jul 2000 07:11:39 -0400 (EDT)
Received: (from majordomo@localhost) by ns1.sailpix.com (8.8.8/8.6.9) id DAA07705; Wed, 26 Jul 2000 03:22:41 -0700 (PDT)
Received: from hygro.adsl.duke.edu (root@hygro.adsl.duke.edu [152.16.64.159]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id DAA07701 for <l2tp@ipsec.org>; Wed, 26 Jul 2000 03:22:29 -0700 (PDT)
Received: from hygro.adsl.duke.edu (IDENT:narten@localhost.localdomain [127.0.0.1])
	by hygro.adsl.duke.edu (8.9.3/8.9.3) with ESMTP id CAA02518;
	Wed, 26 Jul 2000 02:23:10 -0400
Message-Id: <200007260623.CAA02518@hygro.adsl.duke.edu>
To: Danny McPherson <Danny@ambernetworks.com>
cc: "'l2tp@ipsec.org'" <l2tp@ipsec.org>
Subject: Re: L2TP charter 
In-Reply-To: Message from Danny McPherson <Danny@ambernetworks.com> 
   of "Tue, 25 Jul 2000 21:04:51 PDT." <50B17D03735BD411B2D000D0B7237DED36B3F9@amberex01.ambernetworks.com> 
Date: Wed, 26 Jul 2000 02:23:10 -0400
From: Thomas Narten <narten@raleigh.ibm.com>
Sender: owner-l2tp@ipsec.org
Precedence: bulk

> Reminder that we'll be discussing a charter extension at the meeting next
> week.  The general goal is to explicitly extend the WG to include protocols
> other than the current implicitly assumed PPP-only L2TP model.  If there's
> any opposition to this I'd really like to discuss it on the list beforehand
> if possible.

If you have changes you'd like to see made, how about proposing them
on the list. I.e., send text for what you'd like the new charter
(and/or milestone) to be so we can discuss.

Thomas


From owner-l2tp@ipsec.org  Wed Jul 26 10:41:35 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 KAA21099
	for <l2tpext-archive@odin.ietf.org>; Wed, 26 Jul 2000 10:41:35 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns1.sailpix.com (8.8.8/8.6.9) id FAA08038; Wed, 26 Jul 2000 05:48:23 -0700 (PDT)
Received: from ans2-pub.dttus.com ([204.151.11.3]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id FAA08034 for <l2tp@ipsec.org>; Wed, 26 Jul 2000 05:46:53 -0700 (PDT)
Received: by ans2-pub.dttus.com id HAA20579
  (InterLock SMTP Gateway 3.0 for l2tp@ipsec.org);
  Wed, 26 Jul 2000 07:46:32 -0500 (CDT)
Received: by ans2-pub.dttus.com (Internal Mail Agent-2);
  Wed, 26 Jul 2000 07:46:32 -0500 (CDT)
Received: by ans2-pub.dttus.com (Internal Mail Agent-1);
  Wed, 26 Jul 2000 07:46:32 -0500 (CDT)
Message-Id: <2F4A3F6B7BF5D3119E2500508B94E65601DF98BB@uscntnt405.us.deloitte.com>
From: "Verma, Rohit (US - Chicago)" <rverma@dc.com>
To: Srinivasan Seshadri <srinies@globespan.net>,
        James Carlson <james.d.carlson@east.sun.com>
Cc: Sridhar Malarothu <sridhar@trinc.com>, l2tp@ipsec.org
Subject: RE: outgoing call req
Date: Wed, 26 Jul 2000 05:43:00 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01BFF6FF.08553B00"
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_01BFF6FF.08553B00
Content-Type: text/plain;
	charset="iso-8859-1"

Your scenario confuses me a little bit. Where will you be doing NCP. And I
am not sure why you need 2 LAC LNS pairs. 
Can you put more words or a more detailed picture to your scenario.
Why can the CPE not dial directly into the LAC for ISPb. Are their any
particular configuration/administrative reasons. What are you trying to
accomplish in the scenario.
Regards
-rv
-----Original Message-----
From: Srinivasan Seshadri [mailto:srinies@globespan.net]
Sent: Tuesday, July 25, 2000 4:20 PM
To: James Carlson
Cc: Sridhar Malarothu; l2tp@ipsec.org
Subject: Re: outgoing call req


The other scenario could be that a corporate web service is being accessed
from
a CPE (Customer Premise Equipment) side. For ex, in the following situation,

  CPE ------ Central Office
---------ISPa------------Internet----------ISPb---------Corporate End...
                  (LAC)
(LNS)                                         (LNS)          (LAC)
A call from CPE to the corporate end will get routed via ISPb, from which
the
LNS can trigger an outgoing call request to the LAC (once when the data
packets
are to be sent to LAC), if it ever wants to aggregate multiple user side
requests to the corporate....

--Srinivasan.E.S.

James Carlson wrote:

> Sridhar Malarothu writes:
> >    In RFC 2661, it is said that the LNS may send outgoing call
> > reuqest to LAC. Can any one explain the scenarios in which this
> > is send by LNS.
>
> Dial on demand and dial-back (callback) are two common scenarios.
> With dial-on-demand, you have a dummy interface route on the LNS
> system.  When packets arrive on that interface, you initiate a call to
> the remote network.  With callback, the user calls in, provides
> credentials (and perhaps a callback number or location identifier),
> and then disconnects so the LNS can call him back.
>
> >    Can LNS and LAC be present on the same system simultaneously ?
>
> Sure.
>
> --
> 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

------_=_NextPart_001_01BFF6FF.08553B00
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: outgoing call req</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Your scenario confuses me a little bit. Where will =
you be doing NCP. And I am not sure why you need 2 LAC LNS pairs. =
</FONT>
<BR><FONT SIZE=3D2>Can you put more words or a more detailed picture to =
your scenario.</FONT>
<BR><FONT SIZE=3D2>Why can the CPE not dial directly into the LAC for =
ISPb. Are their any particular configuration/administrative reasons. =
What are you trying to accomplish in the scenario.</FONT></P>

<P><FONT SIZE=3D2>Regards</FONT>
<BR><FONT SIZE=3D2>-rv</FONT>
<BR><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Srinivasan Seshadri [<A =
HREF=3D"mailto:srinies@globespan.net">mailto:srinies@globespan.net</A>]<=
/FONT>
<BR><FONT SIZE=3D2>Sent: Tuesday, July 25, 2000 4:20 PM</FONT>
<BR><FONT SIZE=3D2>To: James Carlson</FONT>
<BR><FONT SIZE=3D2>Cc: Sridhar Malarothu; l2tp@ipsec.org</FONT>
<BR><FONT SIZE=3D2>Subject: Re: outgoing call req</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>The other scenario could be that a corporate web =
service is being accessed from</FONT>
<BR><FONT SIZE=3D2>a CPE (Customer Premise Equipment) side. For ex, in =
the following situation,</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp; CPE ------ Central Office =
---------ISPa------------Internet----------ISPb---------Corporate =
End...</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (LAC)</FONT>
<BR><FONT =
SIZE=3D2>(LNS)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
(LNS)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
(LAC)</FONT>
<BR><FONT SIZE=3D2>A call from CPE to the corporate end will get routed =
via ISPb, from which the</FONT>
<BR><FONT SIZE=3D2>LNS can trigger an outgoing call request to the LAC =
(once when the data packets</FONT>
<BR><FONT SIZE=3D2>are to be sent to LAC), if it ever wants to =
aggregate multiple user side</FONT>
<BR><FONT SIZE=3D2>requests to the corporate....</FONT>
</P>

<P><FONT SIZE=3D2>--Srinivasan.E.S.</FONT>
</P>

<P><FONT SIZE=3D2>James Carlson wrote:</FONT>
</P>

<P><FONT SIZE=3D2>&gt; Sridhar Malarothu writes:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp; In RFC 2661, it is said =
that the LNS may send outgoing call</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; reuqest to LAC. Can any one explain the =
scenarios in which this</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; is send by LNS.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; Dial on demand and dial-back (callback) are two =
common scenarios.</FONT>
<BR><FONT SIZE=3D2>&gt; With dial-on-demand, you have a dummy interface =
route on the LNS</FONT>
<BR><FONT SIZE=3D2>&gt; system.&nbsp; When packets arrive on that =
interface, you initiate a call to</FONT>
<BR><FONT SIZE=3D2>&gt; the remote network.&nbsp; With callback, the =
user calls in, provides</FONT>
<BR><FONT SIZE=3D2>&gt; credentials (and perhaps a callback number or =
location identifier),</FONT>
<BR><FONT SIZE=3D2>&gt; and then disconnects so the LNS can call him =
back.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;&nbsp;&nbsp;&nbsp; Can LNS and LAC be =
present on the same system simultaneously ?</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; Sure.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; --</FONT>
<BR><FONT SIZE=3D2>&gt; James Carlson, Internet =
Engineering&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
&lt;james.d.carlson@east.sun.com&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; SUN Microsystems / 1 Network Drive&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 71.234W&nbsp;&nbsp; Vox +1 781 442 =
2084</FONT>
<BR><FONT SIZE=3D2>&gt; MS UBUR02-212 / Burlington MA =
01803-2757&nbsp;&nbsp; 42.497N&nbsp;&nbsp; Fax +1 781 442 1677</FONT>
<BR><FONT SIZE=3D2>&gt; &quot;PPP Design and Debugging&quot; --- <A =
HREF=3D"http://people.ne.mediaone.net/carlson/ppp" =
TARGET=3D"_blank">http://people.ne.mediaone.net/carlson/ppp</A></FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01BFF6FF.08553B00--


From owner-l2tp@ipsec.org  Wed Jul 26 10:51: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 KAA22477
	for <l2tpext-archive@odin.ietf.org>; Wed, 26 Jul 2000 10:51:42 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns1.sailpix.com (8.8.8/8.6.9) id GAA08224; Wed, 26 Jul 2000 06:40:24 -0700 (PDT)
Received: from Helios.bitmotel.com (helios.bitmotel.com [204.146.56.5]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id GAA08220 for <l2tp@ipsec.org>; Wed, 26 Jul 2000 06:40:08 -0700 (PDT)
Received: from bitmotel.com (2sa12.Bitmotel.com [204.146.56.114])
	by Helios.bitmotel.com (8.9.3/8.9.3) with ESMTP id JAA15498
	for <l2tp@ipsec.org>; Wed, 26 Jul 2000 09:33:49 -0400 (EDT)
Message-ID: <397EE9F8.1A07FD50@bitmotel.com>
Date: Wed, 26 Jul 2000 09:39:04 -0400
From: Seshu <sthota@bitmotel.com>
X-Mailer: Mozilla 4.61 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: l2tp@ipsec.org
Subject: L2TP and IPSec
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

I have a couple of questions which I could not find answers to searching
several documents.

1) There appears to be a conclusion that L2TP by itself will not
safegaurd against the spoofing, session hijacking and replay attacks.
Thus to provide protection against these, L2TP is deployed in
combination with IPSec. If this is true, Could some one explain in
detail how and why ?

2) L2TP supports other datagrams like IPX etc in addition to IP
datagrams and this, I believe,  is the reason for using L2TP rather than
IPSec alone where the datagrams are IPX. When the case is  IP datagrams
only, there is no compulsion to use L2TP. Is it true?  Are there any
scenarios that mandate the use of L2TP for IP datagrams case ?

Please excuse me if this is not the forum for these questions.

Seshu



From owner-l2tp@ipsec.org  Wed Jul 26 11: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 LAA02543
	for <l2tpext-archive@odin.ietf.org>; Wed, 26 Jul 2000 11:35:05 -0400 (EDT)
Received: (from majordomo@localhost) by ns1.sailpix.com (8.8.8/8.6.9) id HAA08362; Wed, 26 Jul 2000 07:29:01 -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 HAA08358 for <l2tp@ipsec.org>; Wed, 26 Jul 2000 07:28:32 -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 HAA24427;
	Wed, 26 Jul 2000 07:28:24 -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 KAA24507;
	Wed, 26 Jul 2000 10:28:15 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.9.3+Sun/8.9.3) id KAA19696;
	Wed, 26 Jul 2000 10:28:16 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14718.62848.291806.938785@gargle.gargle.HOWL>
Date: Wed, 26 Jul 2000 10:28:16 -0400 (EDT)
From: James Carlson <james.d.carlson@east.sun.com>
To: Seshu <sthota@bitmotel.com>
Cc: l2tp@ipsec.org
Subject: Re: L2TP and IPSec
In-Reply-To: Seshu's message of 26 July 2000 09:39:04
References: <397EE9F8.1A07FD50@bitmotel.com>
X-Mailer: VM 6.75 under Emacs 20.7.1
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Seshu writes:
> 1) There appears to be a conclusion that L2TP by itself will not
> safegaurd against the spoofing, session hijacking and replay attacks.

Yep.  L2TP does have a few simple security mechanisms, but it's not
complete.

> Thus to provide protection against these, L2TP is deployed in
> combination with IPSec. If this is true, Could some one explain in
> detail how and why ?

You mean besides RFC 2661 section 9.4 and the L2TP/IPSec draft
(draft-ietf-l2tpext-security-00.txt)?

> 2) L2TP supports other datagrams like IPX etc in addition to IP
> datagrams and this, I believe,  is the reason for using L2TP rather than
> IPSec alone where the datagrams are IPX.

L2TP neither knows nor cares about IPX datagrams.  PPP runs over L2TP,
and PPP can support IPX (among many other network layer protocols).

> When the case is  IP datagrams
> only, there is no compulsion to use L2TP. Is it true?

Not exactly.  Needing to tunnel IPX does not compel you to use L2TP,
and needing to tunnel only IP doesn't free you from having to use it.

There are many other tunneling protocols besides L2TP.  You could run
IPSec ESP to get secured tunnels.  You can use IP-IP and IP-GRE
tunneling as well.  MPLS can also be used for tunneling.  There are
also the proprietary forerunners to L2TP -- PPTP and L2F.

If you use IP-GRE, you can run IPX over GRE and skip L2TP completely.

>  Are there any
> scenarios that mandate the use of L2TP for IP datagrams case ?

Not as such.  If the peers you're communicating use only LT2P, then
I'd suppose that L2TP is mandated.  Otherwise, it's not.

-- 
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  Wed Jul 26 11:40:53 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 LAA04608
	for <l2tpext-archive@odin.ietf.org>; Wed, 26 Jul 2000 11:40:53 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns1.sailpix.com (8.8.8/8.6.9) id HAA08389; Wed, 26 Jul 2000 07:37:50 -0700 (PDT)
Received: from seattle.3com.com (seattle.3com.com [129.213.128.97]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id HAA08385 for <l2tp@ipsec.org>; Wed, 26 Jul 2000 07:37:39 -0700 (PDT)
From: Madhvi_Verma@3Com.COM
Received: from new-york.3com.com (new-york.3com.com [129.213.157.12])
	by seattle.3com.com (8.8.8/8.8.8) with ESMTP id HAA07466
	for <l2tp@ipsec.org>; Wed, 26 Jul 2000 07:37:08 -0700 (PDT)
Received: from hqoutbound.ops.3com.com (hqoutbound.OPS.3Com.COM [139.87.48.104])
	by new-york.3com.com (8.8.8/8.8.8) with SMTP id HAA02199
	for <l2tp@ipsec.org>; Wed, 26 Jul 2000 07:36:40 -0700 (PDT)
Received: by hqoutbound.ops.3com.com(Lotus SMTP MTA v4.6.7  (934.1 12-30-1999))  id 88256928.00503A05 ; Wed, 26 Jul 2000 07:36:17 -0700
X-Lotus-FromDomain: 3COM
To: l2tp@ipsec.org
Message-ID: <88256928.005036D4.00@hqoutbound.ops.3com.com>
Date: Wed, 26 Jul 2000 09:38:17 -0500
Subject: L2TP over FR medium
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: owner-l2tp@ipsec.org
Precedence: bulk



Hi,
Would anyone be interested in testing L2TP over FR at the Sept. bakeoff ?

-Madhvi




From owner-l2tp@ipsec.org  Wed Jul 26 14:59:55 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 OAA16536
	for <l2tpext-archive@odin.ietf.org>; Wed, 26 Jul 2000 14:59:54 -0400 (EDT)
Received: (from majordomo@localhost) by ns1.sailpix.com (8.8.8/8.6.9) id LAA08945; Wed, 26 Jul 2000 11:00:54 -0700 (PDT)
Received: from brahma.roc.com ([203.197.21.137]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id LAA08941 for <l2tp@ipsec.org>; Wed, 26 Jul 2000 11:00:31 -0700 (PDT)
Received: from sridhar.roc.com ([172.16.5.52])
	by brahma.roc.com (8.8.5/8.8.5) with SMTP id XAA14739
	for <l2tp@ipsec.org>; Wed, 26 Jul 2000 23:35:09 +0530 (IST)
Message-Id: <200007261805.XAA14739@brahma.roc.com>
X-Sender: sridhar@172.16.1.10
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0
Date: Wed, 26 Jul 2000 23:38:32 +0530
To: l2tp@ipsec.org
From: Sridhar Malarothu <sridhar@trinc.com>
Subject: PPP frames on tunnel
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-l2tp@ipsec.org
Precedence: bulk

Hi All,

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



From owner-l2tp@ipsec.org  Wed Jul 26 15:00:55 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 PAA16665
	for <l2tpext-archive@odin.ietf.org>; Wed, 26 Jul 2000 15:00:54 -0400 (EDT)
Received: (from majordomo@localhost) by ns1.sailpix.com (8.8.8/8.6.9) id KAA08902; Wed, 26 Jul 2000 10:47:51 -0700 (PDT)
Received: from stile.redback.com (stile.redback.com [155.53.36.12]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id KAA08898 for <l2tp@ipsec.org>; Wed, 26 Jul 2000 10:47:37 -0700 (PDT)
Received: (from suhail@localhost)
	by stile.redback.com (8.8.8/8.8.8) id KAA08808;
	Wed, 26 Jul 2000 10:47:03 -0700 (PDT)
From: Suhail Nanji <suhail@redback.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Wed, 26 Jul 2000 10:47:03 -0700 (PDT)
To: Madhvi_Verma@3Com.COM
Cc: l2tp@ipsec.org
Subject: Re: L2TP over FR medium
In-Reply-To: <88256928.005036D4.00@hqoutbound.ops.3com.com>
References: <88256928.005036D4.00@hqoutbound.ops.3com.com>
X-Mailer: VM 6.43 under 21.1 (patch 9) "Canyonlands" XEmacs Lucid
Message-ID: <14719.9184.992380.916026@stile.redback.com>
Reply-To: suhail@redback.com (Suhail Nanji)
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Madhvi_Verma@3Com.COM writes:
> 
> 
> Hi,
> Would anyone be interested in testing L2TP over FR at the Sept. bakeoff ?

Yes, I would be interested.  Also, anyone interested in testing L2TP over
ATM?

Suhail

> 
> -Madhvi
> 
> 


From owner-l2tp@ipsec.org  Wed Jul 26 15:11:14 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 PAA18159
	for <l2tpext-archive@odin.ietf.org>; Wed, 26 Jul 2000 15:11:13 -0400 (EDT)
Received: (from majordomo@localhost) by ns1.sailpix.com (8.8.8/8.6.9) id LAA09035; Wed, 26 Jul 2000 11:24:05 -0700 (PDT)
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id LAA09031 for <l2tp@ipsec.org>; Wed, 26 Jul 2000 11:23:51 -0700 (PDT)
Received: from townsley-ultra.cisco.com (townsley-ultra.cisco.com [161.44.58.38])
	by sj-msg-core-1.cisco.com (8.9.3/8.9.1) with ESMTP id LAA22196;
	Wed, 26 Jul 2000 11:23:34 -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 OAA08784; Wed, 26 Jul 2000 14:23:18 -0400 (EDT)
Message-ID: <397F2C89.21DFF4E6@cisco.com>
Date: Wed, 26 Jul 2000 14:23:05 -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: Sridhar Malarothu <sridhar@trinc.com>
CC: l2tp@ipsec.org
Subject: Re: PPP frames on tunnel
References: <200007261805.XAA14739@brahma.roc.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


PPP framing of FFO3, unless ACFC is negotiated, should exist on packets
sent from the LNS and from the LAC.

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


From owner-l2tp@ipsec.org  Wed Jul 26 15:34:16 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 PAA22328
	for <l2tpext-archive@odin.ietf.org>; Wed, 26 Jul 2000 15:34:16 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns1.sailpix.com (8.8.8/8.6.9) id LAA09149; Wed, 26 Jul 2000 11:41:41 -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 LAA09145 for <l2tp@ipsec.org>; Wed, 26 Jul 2000 11:41:22 -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 LAA03338;
	Wed, 26 Jul 2000 11:41:20 -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 OAA24975;
	Wed, 26 Jul 2000 14:41:17 -0400 (EDT)
Received: (from carlsonj@localhost)
	by phorcys.east.sun.com (8.9.3+Sun/8.9.3) id OAA19873;
	Wed, 26 Jul 2000 14:41:19 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14719.12494.997970.346074@gargle.gargle.HOWL>
Date: Wed, 26 Jul 2000 14:41:18 -0400 (EDT)
From: James Carlson <james.d.carlson@east.sun.com>
To: Sridhar Malarothu <sridhar@trinc.com>
Cc: l2tp@ipsec.org
Subject: Re: PPP frames on tunnel
In-Reply-To: Sridhar Malarothu's message of 26 July 2000 23:38:32
References: <200007261805.XAA14739@brahma.roc.com>
X-Mailer: VM 6.75 under Emacs 20.7.1
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

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

Data frames from the LNS should not have an appended CRC, framing, or
transparency bytes, and they should have L2TP headers.

Note that the leading FF 03 (the default values used for the HDLC
Address and Control fields on regular PPP links) must be included on
the tunneled frames, contrary to prior convention (such as described
in RFCs 1598, 1973, and 2364).  So, if you're coming from a regular
PPP over Frame Relay network into an L2TP tunnel, you'll have to add
those extra bytes on entry to the tunnel and remove them before going
into Frame Relay.

-- 
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  Wed Jul 26 15:48: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 PAA25905
	for <l2tpext-archive@odin.ietf.org>; Wed, 26 Jul 2000 15:48:14 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns1.sailpix.com (8.8.8/8.6.9) id LAA09168; Wed, 26 Jul 2000 11:44:12 -0700 (PDT)
Received: from rambo.globespan.net (p1.globespan.net [209.191.59.250]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id LAA09155 for <l2tp@ipsec.org>; Wed, 26 Jul 2000 11:42:23 -0700 (PDT)
Received: by rambo with Internet Mail Service (5.5.2650.21)
	id <PH0YR0S1>; Wed, 26 Jul 2000 14:41:50 -0400
Received: from globespan.net (SRINIES [192.168.25.14]) by rambo.globespan.net with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21)
	id PH0YR0SD; Wed, 26 Jul 2000 14:41:45 -0400
From: Srinivasan Seshadri <srinies@globespan.net>
To: "Verma, Rohit (US - Chicago)" <rverma@dc.com>
Cc: James Carlson <james.d.carlson@east.sun.com>,
        Sridhar Malarothu
	 <sridhar@trinc.com>, l2tp@ipsec.org
Message-ID: <397F30D1.46964E61@globespan.net>
Date: Wed, 26 Jul 2000 14:41:21 -0400
Organization: Globespan, Inc.
X-Mailer: Mozilla 4.51 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: outgoing call req
References: <2F4A3F6B7BF5D3119E2500508B94E65601DF98BB@uscntnt405.us.deloitte.com>
Content-Type: multipart/alternative;
 boundary="------------DC613ECA588359F44736FE58"
Sender: owner-l2tp@ipsec.org
Precedence: bulk


--------------DC613ECA588359F44736FE58
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

The scenario that has been pictured was more related to a broadband
access case, where an end to end access from an user site to the
corporate server, which hosts certain web services, is shown. Assume,
the user site is connected to a DSLAM (DSL access multiplexor) through
the DSL network on the access side and the DSLAM is connected to the ISP
for the data transport. A pair of LAC & LNS would be present in the
DSLAM and the ISP devices respectively. A PPP session, which originates
at the user site would transit via the LAC (thro the L2TP tunnel) and
get terminated at the LNS with the ISP. From there, the datagram gets
routed through the Internet to the destination, which in this scneario,
would be the corporate site. 
Also, assume that the corporate site is also present in the DSL network
as mentioned in the above case. Now, we can safely assume a LNS-LAC pair
on this network also. This is where, the outgoing call would be
initiated from the LNS to the LAC to forward the datagram over the L2TP
session. Hope this is clear now. Won't this be a likely scenario? 

--Srinivasan.E.S. 


"Verma, Rohit (US - Chicago)" wrote: 


  

Your scenario confuses me a little bit. Where will you be doing NCP. And
I am not sure why you need 2 LAC LNS pairs. 
Can you put more words or a more detailed picture to your scenario. 
Why can the CPE not dial directly into the LAC for ISPb. Are their any
particular configuration/administrative reasons. What are you trying to
accomplish in the scenario. 


Regards 
-rv 
-----Original Message----- 
From: Srinivasan Seshadri [ mailto:srinies@globespan.net
<mailto:srinies@globespan.net> ] 
Sent: Tuesday, July 25, 2000 4:20 PM 
To: James Carlson 
Cc: Sridhar Malarothu; l2tp@ipsec.org 
Subject: Re: outgoing call req 


The other scenario could be that a corporate web service is being
accessed from 
a CPE (Customer Premise Equipment) side. For ex, in the following
situation, 


  CPE ------ Central Office
---------ISPa------------Internet----------ISPb---------Corporate End...

                  (LAC) 
(LNS)                                         (LNS)          (LAC) 
A call from CPE to the corporate end will get routed via ISPb, from
which the 
LNS can trigger an outgoing call request to the LAC (once when the data
packets 
are to be sent to LAC), if it ever wants to aggregate multiple user side

requests to the corporate.... 


--Srinivasan.E.S. 


James Carlson wrote: 


> Sridhar Malarothu writes: 
> >    In RFC 2661, it is said that the LNS may send outgoing call 
> > reuqest to LAC. Can any one explain the scenarios in which this 
> > is send by LNS. 
> 
> Dial on demand and dial-back (callback) are two common scenarios. 
> With dial-on-demand, you have a dummy interface route on the LNS 
> system.  When packets arrive on that interface, you initiate a call to

> the remote network.  With callback, the user calls in, provides 
> credentials (and perhaps a callback number or location identifier), 
> and then disconnects so the LNS can call him back. 
> 
> >    Can LNS and LAC be present on the same system simultaneously ? 
> 
> Sure. 
> 
> -- 
> 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
<http://people.ne.mediaone.net/carlson/ppp> 



--------------DC613ECA588359F44736FE58
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
The scenario that has been pictured was more related to a broadband access
case, where an end to end access from an user site to the corporate server,
which hosts certain web services, is shown. Assume, the user site is connected
to a DSLAM (DSL access multiplexor) through the DSL network on the access
side and the DSLAM is connected to the ISP for the data transport. A pair
of LAC &amp; LNS would be present in the DSLAM and the ISP devices respectively.
A PPP session, which originates at the user site would transit via the
LAC (thro the L2TP tunnel) and get terminated at the LNS with the ISP.
From there, the datagram gets routed through the Internet to the destination,
which in this scneario, would be the corporate site.
<br>Also, assume that the corporate site is also present in the DSL network
as mentioned in the above case. Now, we can safely assume a LNS-LAC pair
on this network also. This is where, the outgoing call would be initiated
from the LNS to the LAC to forward the datagram over the L2TP session.
Hope this is clear now. Won't this be a likely scenario?
<p>--Srinivasan.E.S.
<p>"Verma, Rohit (US - Chicago)" wrote:
<blockquote TYPE=CITE>&nbsp;
<p><font size=-1>Your scenario confuses me a little bit. Where will you
be doing NCP. And I am not sure why you need 2 LAC LNS pairs.</font>
<br><font size=-1>Can you put more words or a more detailed picture to
your scenario.</font>
<br><font size=-1>Why can the CPE not dial directly into the LAC for ISPb.
Are their any particular configuration/administrative reasons. What are
you trying to accomplish in the scenario.</font>
<p><font size=-1>Regards</font>
<br><font size=-1>-rv</font>
<br><font size=-1>-----Original Message-----</font>
<br><font size=-1>From: Srinivasan Seshadri [<a href="mailto:srinies@globespan.net">mailto:srinies@globespan.net</a>]</font>
<br><font size=-1>Sent: Tuesday, July 25, 2000 4:20 PM</font>
<br><font size=-1>To: James Carlson</font>
<br><font size=-1>Cc: Sridhar Malarothu; l2tp@ipsec.org</font>
<br><font size=-1>Subject: Re: outgoing call req</font>
<p><font size=-1>The other scenario could be that a corporate web service
is being accessed from</font>
<br><font size=-1>a CPE (Customer Premise Equipment) side. For ex, in the
following situation,</font>
<p><font size=-1>&nbsp; CPE ------ Central Office ---------ISPa------------Internet----------ISPb---------Corporate
End...</font>
<br><font size=-1>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
(LAC)</font>
<br><font size=-1>(LNS)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
(LNS)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (LAC)</font>
<br><font size=-1>A call from CPE to the corporate end will get routed
via ISPb, from which the</font>
<br><font size=-1>LNS can trigger an outgoing call request to the LAC (once
when the data packets</font>
<br><font size=-1>are to be sent to LAC), if it ever wants to aggregate
multiple user side</font>
<br><font size=-1>requests to the corporate....</font>
<p><font size=-1>--Srinivasan.E.S.</font>
<p><font size=-1>James Carlson wrote:</font>
<p><font size=-1>> Sridhar Malarothu writes:</font>
<br><font size=-1>> >&nbsp;&nbsp;&nbsp; In RFC 2661, it is said that the
LNS may send outgoing call</font>
<br><font size=-1>> > reuqest to LAC. Can any one explain the scenarios
in which this</font>
<br><font size=-1>> > is send by LNS.</font>
<br><font size=-1>></font>
<br><font size=-1>> Dial on demand and dial-back (callback) are two common
scenarios.</font>
<br><font size=-1>> With dial-on-demand, you have a dummy interface route
on the LNS</font>
<br><font size=-1>> system.&nbsp; When packets arrive on that interface,
you initiate a call to</font>
<br><font size=-1>> the remote network.&nbsp; With callback, the user calls
in, provides</font>
<br><font size=-1>> credentials (and perhaps a callback number or location
identifier),</font>
<br><font size=-1>> and then disconnects so the LNS can call him back.</font>
<br><font size=-1>></font>
<br><font size=-1>> >&nbsp;&nbsp;&nbsp; Can LNS and LAC be present on the
same system simultaneously ?</font>
<br><font size=-1>></font>
<br><font size=-1>> Sure.</font>
<br><font size=-1>></font>
<br><font size=-1>> --</font>
<br><font size=-1>> James Carlson, Internet Engineering&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&lt;james.d.carlson@east.sun.com></font>
<br><font size=-1>> SUN Microsystems / 1 Network Drive&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
71.234W&nbsp;&nbsp; Vox +1 781 442 2084</font>
<br><font size=-1>> MS UBUR02-212 / Burlington MA 01803-2757&nbsp;&nbsp;
42.497N&nbsp;&nbsp; Fax +1 781 442 1677</font>
<br><font size=-1>> "PPP Design and Debugging" --- <a href="http://people.ne.mediaone.net/carlson/ppp" TARGET="_blank">http://people.ne.mediaone.net/carlson/ppp</a></font></blockquote>
</html>

--------------DC613ECA588359F44736FE58--


From owner-l2tp@ipsec.org  Wed Jul 26 17:18:02 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 RAA23274
	for <l2tpext-archive@odin.ietf.org>; Wed, 26 Jul 2000 17:18:02 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns1.sailpix.com (8.8.8/8.6.9) id NAA09600; Wed, 26 Jul 2000 13:25:31 -0700 (PDT)
Received: from amberex01.ambernetworks.com (207-33-177-98.ncal.verio.com [207.33.177.98] (may be forged)) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id NAA09574 for <l2tp@ipsec.org>; Wed, 26 Jul 2000 13:24:13 -0700 (PDT)
Received: by amberex01.ambernetworks.com with Internet Mail Service (5.5.2650.21)
	id <P4JA2CTY>; Wed, 26 Jul 2000 13:26:59 -0700
Message-ID: <50B17D03735BD411B2D000D0B7237DED36B414@amberex01.ambernetworks.com>
From: Danny McPherson <Danny@ambernetworks.com>
To: "'Thomas Narten'" <narten@raleigh.ibm.com>
Cc: "'l2tp@ipsec.org'" <l2tp@ipsec.org>
Subject: RE: L2TP charter 
Date: Wed, 26 Jul 2000 13:26:57 -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


>If you have changes you'd like to see made, how about 
>proposing them on the list. I.e., send text for what 
>you'd like the new charter (and/or milestone) to be 
>so we can discuss.


Comments?  Original is included below.

Thanks!

-danny

*******************************************************************
Proposed Charter, Goals and Milestones (very little difference)

Description of Working Group:

The Layer 2 Tunneling Protocol (L2TP, RFC 2661), as currently defined, is a 
protocol for tunneling PPP (RFC 1661) sessions over various network types.  
The group will provide a forum for discussion and development of extensions
to
L2TP, to include extending L2TP support for tunneling of PDU types in
addition 
to PPP.  Once defined and incorporated into the base standard, the group
will 
work to actively advance the extended L2TP base protocol to Internet
Standard.

The group will:

Define and advance standard MIB for L2TP management.

Produce documents describing how L2TP operates over link types other
than IP (e.g., ATM, Frame Relay, etc.)

Identify and define specific parameters and modes of IPsec in order to
aid interoperability when IPsec is used to secure L2TP traffic.

Define and review the definition of any additional IETF AVPs which are
of interest to the group.

Produce documents describing how L2TP can carry PDUs other than PPP PDUs.


 Goals and Milestones:

   Oct 99       Advance L2TP MIB to Proposed Standard

   Feb 00       Advance L2TP Security to Proposed Standard

   May 00       Advance L2TP over ATM and Frame Relay to Proposed Standard

   NNN 00       Incorporate support for tunneling PDU types other than
                PPP.
   
   NNN 00       Advance L2TP to Draft Standard, 

  

************************************************************************


From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce: ;
Subject: WG ACTION: Layer Two Tunneling Protocol Extensions (l2tpext)
Date: Wed, 27 Oct 1999 12:00:49 -0400
Sender: scoya@cnri.reston.va.us

A new working group has been formed in the Internet Area of the IETF.
For additional information, contact the Area Directors
or the WG Chair.

Layer Two Tunneling Protocol Extensions (l2tpext)
-------------------------------------------------


 Current Status: Active Working Group

 Chair(s):
     W. Mark Townsley <townsley@cisco.com>

 Internet Area Director(s):
     Thomas Narten  <narten@raleigh.ibm.com>
     Erik Nordmark  <nordmark@eng.sun.com>

 Internet Area Advisor:
     Thomas Narten  <narten@raleigh.ibm.com>

 Mailing Lists:
     General Discussion:l2tp@ipsec.org
     To Subscribe:      l2tp-request@ipsec.org
     Archive:           http://www.ipsec.org/email/l2tp/

Description of Working Group:

The Layer 2 Tunneling Protocol (L2TP, RFC 2661) is a protocol for
tunneling PPP (RFC 1661) sessions over various network types.  The group
will provide a forum for discussion and development of extensions to
L2TP, and actively advance the L2TP base protocol to Internet Standard.

The group will:

Define and advance standard MIB for L2TP management.

Produce documents describing how L2TP operates over link types other
than IP (e.g., ATM, Frame Relay, etc.)

Identify and define specific parameters and modes of IPsec in order to
aid interoperability when IPsec is used to secure L2TP traffic.

Define and review the definition of any additional IETF AVPs which are
of interest to the group.

 Goals and Milestones:

   Oct 99       Advance L2TP MIB to Proposed Standard

   Feb 00       Advance L2TP Security to Proposed Standard

   May 00       Advance L2TP over ATM and Frame Relay to Proposed Standard

   Sep 00       Advance L2TP to Draft Standard



************************************************************************











From owner-l2tp@ipsec.org  Wed Jul 26 18:21:55 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 SAA11782
	for <l2tpext-archive@odin.ietf.org>; Wed, 26 Jul 2000 18:21:55 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns1.sailpix.com (8.8.8/8.6.9) id OAA09991; Wed, 26 Jul 2000 14:11:09 -0700 (PDT)
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id OAA09983 for <l2tp@ipsec.org>; Wed, 26 Jul 2000 14:09:58 -0700 (PDT)
Received: from townsley-ultra.cisco.com (townsley-ultra.cisco.com [161.44.58.38])
	by sj-msg-core-1.cisco.com (8.9.3/8.9.1) with ESMTP id OAA05497;
	Wed, 26 Jul 2000 14:09:41 -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 RAA08803; Wed, 26 Jul 2000 17:09:26 -0400 (EDT)
Message-ID: <397F5378.80A33A82@cisco.com>
Date: Wed, 26 Jul 2000 17:09:12 -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: Danny McPherson <Danny@ambernetworks.com>
CC: "'Thomas Narten'" <narten@raleigh.ibm.com>,
        "'l2tp@ipsec.org'" <l2tp@ipsec.org>
Subject: Re: L2TP charter
References: <50B17D03735BD411B2D000D0B7237DED36B414@amberex01.ambernetworks.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Thanks, Danny, a couple of comments. Others most certainly welcome.

Danny McPherson wrote:
> 
> >If you have changes you'd like to see made, how about
> >proposing them on the list. I.e., send text for what
> >you'd like the new charter (and/or milestone) to be
> >so we can discuss.
> 
> Comments?  Original is included below.
> 
> Thanks!
> 
> -danny
> 
> *******************************************************************
> Proposed Charter, Goals and Milestones (very little difference)
> 
> Description of Working Group:
> 
> The Layer 2 Tunneling Protocol (L2TP, RFC 2661), as currently defined, is a
> protocol for tunneling PPP (RFC 1661) sessions over various network types.
> The group will provide a forum for discussion and development of extensions
> to
> L2TP, to include extending L2TP support for tunneling of PDU types in
> addition
> to PPP.  Once defined and incorporated into the base standard, the group
> will
> work to actively advance the extended L2TP base protocol to Internet
> Standard.

We should to investigate whether this would be a material enough change
to L2TP to require reiteration at Proposed Standard. This is, of course,
something I would like to avoid unless absolutely necessary.

> 
> The group will:
> 
> Define and advance standard MIB for L2TP management.
> 
> Produce documents describing how L2TP operates over link types other
> than IP (e.g., ATM, Frame Relay, etc.)
> 
> Identify and define specific parameters and modes of IPsec in order to
> aid interoperability when IPsec is used to secure L2TP traffic.
> 
> Define and review the definition of any additional IETF AVPs which are
> of interest to the group.
> 
> Produce documents describing how L2TP can carry PDUs other than PPP PDUs.

How about:

Investigate applicability of L2TP to carry PDUs other than PPP and
produce documents describing such if deemed useful.

> 
>  Goals and Milestones:
> 
>    Oct 99       Advance L2TP MIB to Proposed Standard
> 
>    Feb 00       Advance L2TP Security to Proposed Standard
> 
>    May 00       Advance L2TP over ATM and Frame Relay to Proposed Standard
> 
>    NNN 00       Incorporate support for tunneling PDU types other than
>                 PPP.
> 
>    NNN 00       Advance L2TP to Draft Standard,
> 
> 
> 
> ************************************************************************
> 
> From: The IESG <iesg-secretary@ietf.org>
> To: IETF-Announce: ;
> Subject: WG ACTION: Layer Two Tunneling Protocol Extensions (l2tpext)
> Date: Wed, 27 Oct 1999 12:00:49 -0400
> Sender: scoya@cnri.reston.va.us
> 
> A new working group has been formed in the Internet Area of the IETF.
> For additional information, contact the Area Directors
> or the WG Chair.
> 
> Layer Two Tunneling Protocol Extensions (l2tpext)
> -------------------------------------------------
> 
>  Current Status: Active Working Group
> 
>  Chair(s):
>      W. Mark Townsley <townsley@cisco.com>
> 
>  Internet Area Director(s):
>      Thomas Narten  <narten@raleigh.ibm.com>
>      Erik Nordmark  <nordmark@eng.sun.com>
> 
>  Internet Area Advisor:
>      Thomas Narten  <narten@raleigh.ibm.com>
> 
>  Mailing Lists:
>      General Discussion:l2tp@ipsec.org
>      To Subscribe:      l2tp-request@ipsec.org
>      Archive:           http://www.ipsec.org/email/l2tp/
> 
> Description of Working Group:
> 
> The Layer 2 Tunneling Protocol (L2TP, RFC 2661) is a protocol for
> tunneling PPP (RFC 1661) sessions over various network types.  The group
> will provide a forum for discussion and development of extensions to
> L2TP, and actively advance the L2TP base protocol to Internet Standard.
> 
> The group will:
> 
> Define and advance standard MIB for L2TP management.
> 
> Produce documents describing how L2TP operates over link types other
> than IP (e.g., ATM, Frame Relay, etc.)
> 
> Identify and define specific parameters and modes of IPsec in order to
> aid interoperability when IPsec is used to secure L2TP traffic.
> 
> Define and review the definition of any additional IETF AVPs which are
> of interest to the group.
> 
>  Goals and Milestones:
> 
>    Oct 99       Advance L2TP MIB to Proposed Standard
> 
>    Feb 00       Advance L2TP Security to Proposed Standard
> 
>    May 00       Advance L2TP over ATM and Frame Relay to Proposed Standard
> 
>    Sep 00       Advance L2TP to Draft Standard
> 
> ************************************************************************


From owner-l2tp@ipsec.org  Wed Jul 26 18:27:34 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 SAA13124
	for <l2tpext-archive@odin.ietf.org>; Wed, 26 Jul 2000 18:27:34 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns1.sailpix.com (8.8.8/8.6.9) id OAA10012; Wed, 26 Jul 2000 14:20:46 -0700 (PDT)
Received: from amberex01.ambernetworks.com (207-33-177-98.ncal.verio.com [207.33.177.98] (may be forged)) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id OAA10008 for <l2tp@ipsec.org>; Wed, 26 Jul 2000 14:20:30 -0700 (PDT)
Received: by amberex01.ambernetworks.com with Internet Mail Service (5.5.2650.21)
	id <P4JA2C5S>; Wed, 26 Jul 2000 14:23:16 -0700
Message-ID: <50B17D03735BD411B2D000D0B7237DED36B417@amberex01.ambernetworks.com>
From: Danny McPherson <Danny@ambernetworks.com>
To: "'W. Mark Townsley'" <townsley@cisco.com>
Cc: "'l2tp@ipsec.org'" <l2tp@ipsec.org>
Subject: RE: L2TP charter
Date: Wed, 26 Jul 2000 14:23: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


> We should to investigate whether this would be a 
> material enough change to L2TP to require reiteration 
> at Proposed Standard. This is, of course, something I 
> would like to avoid unless absolutely necessary.

Agreed, though if providing the capability with trivial 
modifications is feasible, it perhaps is more useful when
stated in one document versus a patchwork of multiple 
documents.  Though I certainly understand your point.

> Investigate applicability of L2TP to carry PDUs other 
> than PPP and produce documents describing such if deemed 
> useful.

I can deal with this, though some elaboration of "if deemed
useful" would certainly be of benefit.  Stating this in the 
WG charter doesn't express a concisely attainable goal.

-danny


From owner-l2tp@ipsec.org  Wed Jul 26 18:44:29 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 SAA17030
	for <l2tpext-archive@odin.ietf.org>; Wed, 26 Jul 2000 18:44:29 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns1.sailpix.com (8.8.8/8.6.9) id OAA10065; Wed, 26 Jul 2000 14:30:45 -0700 (PDT)
Received: from amberex01.ambernetworks.com (207-33-177-98.ncal.verio.com [207.33.177.98] (may be forged)) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id OAA10058 for <l2tp@ipsec.org>; Wed, 26 Jul 2000 14:30:30 -0700 (PDT)
Received: by amberex01.ambernetworks.com with Internet Mail Service (5.5.2650.21)
	id <P4JA2C71>; Wed, 26 Jul 2000 14:33:14 -0700
Message-ID: <50B17D03735BD411B2D000D0B7237DED36B418@amberex01.ambernetworks.com>
From: Danny McPherson <Danny@ambernetworks.com>
To: "'W. Mark Townsley'" <townsley@cisco.com>
Cc: "'l2tp@ipsec.org'" <l2tp@ipsec.org>
Subject: RE: L2TP charter
Date: Wed, 26 Jul 2000 14:33:14 -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


I'm obviously OK with that :-)

-danny

> Perhaps the investigation can be made quickly and 
> we can move towards your text.


From owner-l2tp@ipsec.org  Wed Jul 26 18:56:17 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 SAA20142
	for <l2tpext-archive@odin.ietf.org>; Wed, 26 Jul 2000 18:56:16 -0400 (EDT)
Received: (from majordomo@localhost) by ns1.sailpix.com (8.8.8/8.6.9) id OAA10033; Wed, 26 Jul 2000 14:29:15 -0700 (PDT)
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id OAA10029 for <l2tp@ipsec.org>; Wed, 26 Jul 2000 14:28:55 -0700 (PDT)
Received: from townsley-ultra.cisco.com (townsley-ultra.cisco.com [161.44.58.38])
	by sj-msg-core-1.cisco.com (8.9.3/8.9.1) with ESMTP id OAA20871;
	Wed, 26 Jul 2000 14:28:39 -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 RAA08815; Wed, 26 Jul 2000 17:28:23 -0400 (EDT)
Message-ID: <397F57EA.819D17B2@cisco.com>
Date: Wed, 26 Jul 2000 17:28:10 -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: Danny McPherson <Danny@ambernetworks.com>
CC: "'l2tp@ipsec.org'" <l2tp@ipsec.org>
Subject: Re: L2TP charter
References: <50B17D03735BD411B2D000D0B7237DED36B417@amberex01.ambernetworks.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



Danny McPherson wrote:
> 
> > We should to investigate whether this would be a
> > material enough change to L2TP to require reiteration
> > at Proposed Standard. This is, of course, something I
> > would like to avoid unless absolutely necessary.
> 
> Agreed, though if providing the capability with trivial
> modifications is feasible, it perhaps is more useful when
> stated in one document versus a patchwork of multiple
> documents.  Though I certainly understand your point.
> 
> > Investigate applicability of L2TP to carry PDUs other
> > than PPP and produce documents describing such if deemed
> > useful.
> 
> I can deal with this, though some elaboration of "if deemed
> useful" would certainly be of benefit.  Stating this in the
> WG charter doesn't express a concisely attainable goal.

Perhaps the investigation can be made quickly and we can move towards
your text.

> 
> -danny


From owner-l2tp@ipsec.org  Wed Jul 26 21:26: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 VAA10531
	for <l2tpext-archive@odin.ietf.org>; Wed, 26 Jul 2000 21:26:08 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns1.sailpix.com (8.8.8/8.6.9) id RAA10377; Wed, 26 Jul 2000 17:21:42 -0700 (PDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id RAA10373 for <l2tp@ipsec.org>; Wed, 26 Jul 2000 17:21:29 -0700 (PDT)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.11.0/calcite) id e6R0LRm02321
	for l2tp@ipsec.org  env-from <vjs>;
	Wed, 26 Jul 2000 18:21:27 -0600 (MDT)
Date: Wed, 26 Jul 2000 18:21:27 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200007270021.e6R0LRm02321@calcite.rhyolite.com>
To: l2tp@ipsec.org
Subject: RE: L2TP charter
Sender: owner-l2tp@ipsec.org
Precedence: bulk

> > Investigate applicability of L2TP to carry PDUs other 
> > than PPP and produce documents describing such if deemed 
> > useful.
>
> I can deal with this, though some elaboration of "if deemed
> useful" would certainly be of benefit.  Stating this in the 
> WG charter doesn't express a concisely attainable goal.


Why wouldn't you simply use the PPP bridging protocol?  


Vernon Schryver    vjs@rhyolite.com


From owner-l2tp@ipsec.org  Wed Jul 26 21:26:48 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 VAA10603
	for <l2tpext-archive@odin.ietf.org>; Wed, 26 Jul 2000 21:26:47 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns1.sailpix.com (8.8.8/8.6.9) id RAA10410; Wed, 26 Jul 2000 17:38:02 -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 RAA10406 for <l2tp@ipsec.org>; Wed, 26 Jul 2000 17:37:46 -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 RAA23605;
	Wed, 26 Jul 2000 17:37:29 -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 UAA08846; Wed, 26 Jul 2000 20:37:01 -0400 (EDT)
Message-ID: <397F841F.C0640A9E@cisco.com>
Date: Wed, 26 Jul 2000 20:36:47 -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: Vernon Schryver <vjs@calcite.rhyolite.com>
CC: l2tp@ipsec.org
Subject: Re: L2TP charter
References: <200007270021.e6R0LRm02321@calcite.rhyolite.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



Vernon Schryver wrote:
> 
> > > Investigate applicability of L2TP to carry PDUs other
> > > than PPP and produce documents describing such if deemed
> > > useful.
> >
> > I can deal with this, though some elaboration of "if deemed
> > useful" would certainly be of benefit.  Stating this in the
> > WG charter doesn't express a concisely attainable goal.
> 
> Why wouldn't you simply use the PPP bridging protocol?

See the recent discussion between James Carlson and Suhail Nanji.

> 
> Vernon Schryver    vjs@rhyolite.com


From owner-l2tp@ipsec.org  Wed Jul 26 21:30:47 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 VAA11104
	for <l2tpext-archive@odin.ietf.org>; Wed, 26 Jul 2000 21:30:46 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns1.sailpix.com (8.8.8/8.6.9) id RAA10400; Wed, 26 Jul 2000 17:36:53 -0700 (PDT)
Received: from mx.databus.com (p101-44.acedsl.com [160.79.101.44]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id RAA10396 for <l2tp@ipsec.org>; Wed, 26 Jul 2000 17:36:41 -0700 (PDT)
Received: (from barney@localhost)
	by mx.databus.com (8.9.3/8.9.3) id UAA64449
	for l2tp@ipsec.org; Wed, 26 Jul 2000 20:36:40 -0400 (EDT)
	(envelope-from barney)
From: Barney Wolff <barney@databus.com>
Message-Id: <200007270036.UAA64449@mx.databus.com>
Subject: Re: L2TP charter
To: l2tp@ipsec.org
Date: Wed, 26 Jul 2000 20:36:40 -0400 (EDT)
X-Mailer: ELM [version 2.4ME+ PL68 (25)]
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

I'd like to register skepticism on extending L2TP to tunnel other
things.  Primarily, I'd resist with vigor any attempt to make
"L2TP standard compliant" depend on support for anything but PPP.
Dunno if the proponents really intend that, but the proposed
charter language makes me a little paranoid.

Secondarily, I'd really like to hear why X needs to be carried over
L2TP, rather than over whatever X is carried over today.

Barney Wolff


From owner-l2tp@ipsec.org  Thu Jul 27 03:01:21 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 DAA17753
	for <l2tpext-archive@odin.ietf.org>; Thu, 27 Jul 2000 03:01:20 -0400 (EDT)
Received: (from majordomo@localhost) by ns1.sailpix.com (8.8.8/8.6.9) id XAA11027; Wed, 26 Jul 2000 23:11:55 -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 XAA11023 for <l2tp@ipsec.org>; Wed, 26 Jul 2000 23:11:39 -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 AAA23349
	for <l2tp@ipsec.org>; Thu, 27 Jul 2000 00:12:29 -0600
Message-Id: <200007270612.AAA23349@tcb.net>
X-Mailer: exmh version 2.0.3
To: l2tp@ipsec.org
From: Danny McPherson <danny@ambernetworks.com>
Reply-To: danny@ambernetworks.com
Subject: Re: L2TP charter 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 27 Jul 2000 00:12:29 -0600
Sender: owner-l2tp@ipsec.org
Precedence: bulk


Because X is an array of protocols (Layer 3 or lower), and ISPs absolutely 
want to converge these services (e.g. ATM & Frame Relay) onto IP core 
networks.  Trivial L2TP extensions provide an elegant mechanism to do this, 
without the baggage of heavier IP tunneling protocols.

-danny

> I'd like to register skepticism on extending L2TP to tunnel other
> things.  Primarily, I'd resist with vigor any attempt to make
> "L2TP standard compliant" depend on support for anything but PPP.
> Dunno if the proponents really intend that, but the proposed
> charter language makes me a little paranoid.
> 
> Secondarily, I'd really like to hear why X needs to be carried over
> L2TP, rather than over whatever X is carried over today.




From owner-l2tp@ipsec.org  Thu Jul 27 03:16: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 DAA22483
	for <l2tpext-archive@odin.ietf.org>; Thu, 27 Jul 2000 03:16:10 -0400 (EDT)
Received: (from majordomo@localhost) by ns1.sailpix.com (8.8.8/8.6.9) id XAA11048; Wed, 26 Jul 2000 23:27:29 -0700 (PDT)
Received: from amberex01.ambernetworks.com (207-33-177-98.ncal.verio.com [207.33.177.98] (may be forged)) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id XAA11044 for <l2tp@ipsec.org>; Wed, 26 Jul 2000 23:26:42 -0700 (PDT)
Received: by amberex01.ambernetworks.com with Internet Mail Service (5.5.2650.21)
	id <P4JA2D6X>; Wed, 26 Jul 2000 23:29:29 -0700
Message-ID: <50B17D03735BD411B2D000D0B7237DED0C077E@amberex01.ambernetworks.com>
From: Nishit Vasavada <Nishit@ambernetworks.com>
To: l2tp@ipsec.org
Subject: RE: I-D ACTION:draft-ietf-l2tpext-ds-00.txt
Date: Wed, 26 Jul 2000 23:29:28 -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

The third paragraph under section 2.1 (Differentiated Services Code Point
AVP) of this draft reads:

"The presence of this AVP in the ICRQ or OCRQ indicates that the tunnel
initiator wishes to use a specific DSCP on all data packets.  However, the
value found in the ICRP or OCRP indicate the value which the Tunnel
Terminator is willing to accept."

Shouldn't it say *session initiator* and *session terminator*?  ICRQ and
OCRQ are call/session related.  And even the paragraph above the reproduced
one identifies the AVP with the specific session ("...all packets related to
the data channel associated with the Tunnel and Call Identifiers in the L2TP
header").

- Nishit
--

Nishit Vasavada
Amber Networks, Inc.


> -----Original Message-----
> From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org]
> Sent: Monday, March 06, 2000 3:58 AM
> To: IETF-Announce
> Cc: l2tp@ipsec.org
> Subject: I-D ACTION:draft-ietf-l2tpext-ds-00.txt
> 
> 
> 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		: Layer Two Tunneling Protocol 'L2TP' 
> IP Differentiated 
>                           Services Extension
> 	Author(s)	: P. Calhoun, K. Peirce
> 	Filename	: draft-ietf-l2tpext-ds-00.txt
> 	Pages		: 5
> 	Date		: 03-Mar-00
> 	
> The L2TP document [1] defines the base protocol which describes the
> method of tunneling PPP data. The L2TP base protocol does not address
> any Differentiated Services extensions.
> The ability to outsource dial access with Quality of Service
> assurances is important to internet applications development. This
> draft addresses this issue by allowing each L2TP Data Session to be
> assigned an appropriate differentiated services indicator.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-l2tpext-ds-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-ds-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-ds-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.
> 


From owner-l2tp@ipsec.org  Thu Jul 27 07:32:48 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 HAA03122
	for <l2tpext-archive@odin.ietf.org>; Thu, 27 Jul 2000 07:32:47 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns1.sailpix.com (8.8.8/8.6.9) id DAA12760; Thu, 27 Jul 2000 03:42:10 -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 DAA12756 for <l2tp@ipsec.org>; Thu, 27 Jul 2000 03:41:46 -0700 (PDT)
Received: (from carlson@localhost)
	by h006008986325.ne.mediaone.net (8.9.3/8.9.3) id GAA18480;
	Thu, 27 Jul 2000 06:41:44 -0400
From: James Carlson <carlson@workingcode.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14720.4583.415598.127833@h006008986325.ne.mediaone.net>
Date: Thu, 27 Jul 2000 06:41:43 -0400 (EDT)
To: danny@ambernetworks.com
Cc: l2tp@ipsec.org
Subject: Re: L2TP charter 
In-Reply-To: Danny McPherson's message of 27 July 2000 00:12:29
References: <200007270612.AAA23349@tcb.net>
X-Mailer: VM 6.75 under Emacs 20.6.1
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Danny McPherson writes:
> Because X is an array of protocols (Layer 3 or lower), and ISPs absolutely 
> want to converge these services (e.g. ATM & Frame Relay) onto IP core 
> networks.  Trivial L2TP extensions provide an elegant mechanism to do this, 
> without the baggage of heavier IP tunneling protocols.

Layer 3 or lower?  Could I interpret this to mean SNA over L2TP or
DECNet over L2TP?

I don't understand your objection to the "heavier" baggage of other IP
tunneling protocols.  L2TP has a default encapsulation of UDP-GRE and
thus is heavier than IP-GRE.  There's some precedent for using IP-GRE
encapsulation to carry non-IP payloads across IP networks.  Do we need
another?

You're right that ISPs do want to converge services, but I don't think
L2TP is the right mechanism for that convergence.  MPLS has much lower
overhead, behaves in a hop-by-hop manner familiar to ATM and Frame
Relay operators and is already quite compatible with those protocols
and defines interworking standards, and (very much unlike L2TP) is
already supported in core routers.  MPLS is much more suited to this
task.

I suggest that L2TP stick to its roots in providing tunneling support
for dial-up network access protocols only.  This should be explicitly
listed in its charter, along with examples of such protocols -- PPP
and SLIP.

(If someone has a need to carry ARAP across a network, I'd waver and
say that the charter is still too broad.  ARAP inexplicably requires
MNP for reliability and might be more suitably tunneled over TCP.)

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


From owner-l2tp@ipsec.org  Thu Jul 27 11:06:51 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 LAA12863
	for <l2tpext-archive@odin.ietf.org>; Thu, 27 Jul 2000 11:06:50 -0400 (EDT)
Received: (from majordomo@localhost) by ns1.sailpix.com (8.8.8/8.6.9) id HAA12958; Thu, 27 Jul 2000 07:08:26 -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 HAA12954 for <l2tp@ipsec.org>; Thu, 27 Jul 2000 07:07:52 -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 IAA25124;
	Thu, 27 Jul 2000 08:08:43 -0600
Message-Id: <200007271408.IAA25124@tcb.net>
X-Mailer: exmh version 2.0.3
To: James Carlson <carlson@workingcode.com>
cc: l2tp@ipsec.org
From: Danny McPherson <danny@ambernetworks.com>
Reply-To: danny@ambernetworks.com
Subject: Re: L2TP charter 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 27 Jul 2000 08:08:43 -0600
Sender: owner-l2tp@ipsec.org
Precedence: bulk


> Layer 3 or lower?  Could I interpret this to mean SNA over L2TP or
> DECNet over L2TP?

Let me clarify -- ANY PDU Type.

> I don't understand your objection to the "heavier" baggage of other IP
> tunneling protocols.  L2TP has a default encapsulation of UDP-GRE and
> thus is heavier than IP-GRE.  There's some precedent for using IP-GRE
> encapsulation to carry non-IP payloads across IP networks.  Do we need
> another?

L2TP clearly provides what's required to support IP-based emulation services, 
tunnel management and similar are already present.  GRE has none of this.

> You're right that ISPs do want to converge services, but I don't think
> L2TP is the right mechanism for that convergence.  MPLS has much lower
> overhead, behaves in a hop-by-hop manner familiar to ATM and Frame
> Relay operators and is already quite compatible with those protocols
> and defines interworking standards, and (very much unlike L2TP) is
> already supported in core routers.  MPLS is much more suited to this
> task.

MPLS-based mechanisms require MPLS.  L2TP doesn't and can be deployed in IP 
networks, both intra-domain and inter-domain today with very little effort, or 
over those MPLS networks.

> I suggest that L2TP stick to its roots in providing tunneling support
> for dial-up network access protocols only.  This should be explicitly
> listed in its charter, along with examples of such protocols -- PPP
> and SLIP.

And then what, create yet another WG to address IP-based tunneling mechanisms, 
or extend GRE (or create a new protocol) that looks and smells like L2TP and 
provides the tunnel management hooks L2TP does, all when L2TP provide an 
elegant way to accomplish this today?  That seems senseless and wasteful to me.

> (If someone has a need to carry ARAP across a network, I'd waver and
> say that the charter is still too broad.  ARAP inexplicably requires
> MNP for reliability and might be more suitably tunneled over TCP.)

I know of at least 3 vendors today that have working code (and hardware) that 
provides L2TP hooks to support tunneling of other-than-PPP PDUs, there's 
obviously sufficient interest and L2TP was the protocol of choice of these 
vendors not after a short-sighted leap into hardware and software development, 
but rather, after an careful consideration of "what's the closest thing there 
today?".  Providing a standards-based mechanism to accomplish this -- with 
very little change, can only be of benefit.  Tons of modifications or efforts 
into beefing up yet another protocol to support this is unnecessary.

-danny



From owner-l2tp@ipsec.org  Thu Jul 27 11:07: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 LAA12968
	for <l2tpext-archive@odin.ietf.org>; Thu, 27 Jul 2000 11:07:37 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns1.sailpix.com (8.8.8/8.6.9) id HAA12975; Thu, 27 Jul 2000 07:28:04 -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 HAA12971 for <l2tp@ipsec.org>; Thu, 27 Jul 2000 07:27:21 -0700 (PDT)
Received: (from carlson@localhost)
	by h006008986325.ne.mediaone.net (8.9.3/8.9.3) id KAA23866;
	Thu, 27 Jul 2000 10:27:18 -0400
From: James Carlson <carlson@workingcode.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14720.18118.129681.677014@h006008986325.ne.mediaone.net>
Date: Thu, 27 Jul 2000 10:27:18 -0400 (EDT)
To: danny@ambernetworks.com
Cc: l2tp@ipsec.org
Subject: Re: L2TP charter 
In-Reply-To: Danny McPherson's message of 27 July 2000 08:08:43
References: <200007271408.IAA25124@tcb.net>
X-Mailer: VM 6.75 under Emacs 20.6.1
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Danny McPherson writes:
> > You're right that ISPs do want to converge services, but I don't think
> > L2TP is the right mechanism for that convergence.  MPLS has much lower
> > overhead, behaves in a hop-by-hop manner familiar to ATM and Frame
> > Relay operators and is already quite compatible with those protocols
> > and defines interworking standards, and (very much unlike L2TP) is
> > already supported in core routers.  MPLS is much more suited to this
> > task.
> 
> MPLS-based mechanisms require MPLS.

Right.  I'm explicitly conjecturing that any major ISP that wants to
supply Frame Relay-like services will do so over his own MPLS network.

>  L2TP doesn't and can be deployed in IP 
> networks, both intra-domain and inter-domain today with very little effort, or 
> over those MPLS networks.

The inter-domain problem for non-IP protocols is much bigger than just
the transport itself.  The bandwidth reservation and ordering
requirements are much taller orders to fill.  The effort, I think, is
better spent on inter-domain QoS mechanisms.

> And then what, create yet another WG to address IP-based tunneling mechanisms, 
> or extend GRE (or create a new protocol) that looks and smells like L2TP and 
> provides the tunnel management hooks L2TP does, all when L2TP provide an 
> elegant way to accomplish this today?  That seems senseless and wasteful to me.

Look at any Cisco router.  You can already configure GRE tunnels for
any protocol you like.  I can see no particular benefit from L2TP's
management or negotiation capabilities.  You'll still have to manually
configure explicit traffic-engineered paths and manually configure
associations between the tunnel endpoints.  The only thing that L2TP
would provide over static configuration is a small amount of
handshake.

No new working group is needed.

> I know of at least 3 vendors today that have working code (and hardware) that 
> provides L2TP hooks to support tunneling of other-than-PPP PDUs, there's 
> obviously sufficient interest and L2TP was the protocol of choice of these 
> vendors not after a short-sighted leap into hardware and software development, 
> but rather, after an careful consideration of "what's the closest thing there 
> today?".

Please don't take it personally.  Mistakes sometimes do occur, and I
believe this to be one.  As for how many folks would like to do this,
see RFC 1925, especially truths (3) and (12).

>  Providing a standards-based mechanism to accomplish this -- with 
> very little change, can only be of benefit.

No.  Where it duplicates an existing mechanism, any such proposal is
to the detriment, not benefit, of the Internet.

If you really need to use L2TP to do this, use the existing mechanism.
Run PPP over L2TP, and run your L3 protocol over PPP.  That's what PPP
is for.  It already does what you want.

>  Tons of modifications or efforts 
> into beefing up yet another protocol to support this is unnecessary.

I wasn't suggesting beefing up any other protocol to support this.
The non-IP transport and interworking capabilities of MPLS already
exist.  The manually configured GRE tunneling capabilities already
exist and have a long history.

I'd suggest that adding these capabilities into L2TP, including the
necessary AVPs and interworking specifications, constitutes an
unwarranted "beefing up" of L2TP.  It duplicates existing PPP
functionality and provides no obvious benefit.

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


From owner-l2tp@ipsec.org  Thu Jul 27 11:28:48 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 LAA18700
	for <l2tpext-archive@odin.ietf.org>; Thu, 27 Jul 2000 11:28:47 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns1.sailpix.com (8.8.8/8.6.9) id HAA13022; Thu, 27 Jul 2000 07:48:06 -0700 (PDT)
Received: from amberex01.ambernetworks.com (207-33-177-98.ncal.verio.com [207.33.177.98] (may be forged)) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id HAA13009 for <l2tp@ipsec.org>; Thu, 27 Jul 2000 07:46:53 -0700 (PDT)
Received: by amberex01.ambernetworks.com with Internet Mail Service (5.5.2650.21)
	id <P4JA21HM>; Thu, 27 Jul 2000 07:49:42 -0700
Message-ID: <50B17D03735BD411B2D000D0B7237DED36B41F@amberex01.ambernetworks.com>
From: Danny McPherson <Danny@ambernetworks.com>
To: "'James Carlson'" <carlson@workingcode.com>
Cc: l2tp@ipsec.org
Subject: RE: L2TP charter 
Date: Thu, 27 Jul 2000 07:49:41 -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



>Right.  I'm explicitly conjecturing that any major 
>ISP that wants to supply Frame Relay-like services 
>will do so over his own MPLS network.

This is not a correct assumption.

>The inter-domain problem for non-IP protocols is 
>much bigger than just the transport itself.  The 
>bandwidth reservation and ordering requirements 
>are much taller orders to fill.  The effort, I 
>think, is better spent on inter-domain QoS 
>mechanisms.

Having worked in the engineering groups of three large
networks, and still being involved with some of those
networks, as well as others, I assure you that inter-
domain QoS isn't high on anyone's priority list today.
Nor is inter-domain MPLS, for that matter.

>Look at any Cisco router.  You can already configure 
>GRE tunnels for any protocol you like.  I can see no 
>particular benefit from L2TP's management or negotiation 
>capabilities.  You'll still have to manually configure 
>explicit traffic-engineered paths and manually configure
>associations between the tunnel endpoints. 

Eh?  I think you're a bit confused here.  TE isn't
required, and it's clearly a bit difficult to accomplish
in only DA-based packet networks (i.e. IP networks).

>The only 
>thing that L2TP would provide over static configuration 
>is a small amount of handshake.

That small amount of handshake, coupled with the AVP 
concept and the other call management stuff makes it
an ideal choice for circuit emulation over IP.  Much,
much more desirable than IP.  If it were really as 
simple as you say, we wouldn't need L2TP, we could 
just use GRE, no?

>No new working group is needed.

If not, then at least a considerable more amount of
work is. 

>Please don't take it personally.  Mistakes sometimes 
>do occur, and I believe this to be one.  As for how 
>many folks would like to do this, see RFC 1925, especially 
>truths (3) and (12).

Cute.  You're obviously missing the point of why GRE
is not the answer.  It requires more than an encapsulation
protocol.

> No.  Where it duplicates an existing mechanism, any 
> such proposal is to the detriment, not benefit, of 
> the Internet.

You've still not explained to me how a simple Encapsulation
Protocol such as GRE performs these functions?  Why, is that?
 
>If you really need to use L2TP to do this, use the 
>existing mechanism. Run PPP over L2TP, and run your L3 
> protocol over PPP.  That's what PPP is for.  It already 
> does what you want.

Ahh, and add additional network overhead, and packet processing,
for that matter -- all unnecessary.  I guess with enough glue 
you could do anything.

>I wasn't suggesting beefing up any other protocol 
>to support this.  The non-IP transport and interworking 
>capabilities of MPLS already exist.  The manually 
>configured GRE tunneling capabilities already
>exist and have a long history.

Manually configured, yes.  Long history as hacks, yes.
So you do see the point -- maybe?

>I'd suggest that adding these capabilities into 
>L2TP, including the necessary AVPs and interworking 
>specifications, constitutes an unwarranted "beefing up" 
>of L2TP.  It duplicates existing PPP functionality 
>and provides no obvious benefit.

You're still missing the point.  L2TP provides the 
dynamic call capabilities that ISPs want.  Not a 
bunch of unmanageable GRE gunk.  

Putting it over PPP would obviously work, though this 
increases network overhead significantly with no obvious 
benefit.  

L2TP is clearly the place to do this.  If requires the
least amount of work and working implementations have 
been demonstrated.  

-danny


From owner-l2tp@ipsec.org  Thu Jul 27 11:31:31 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 LAA19590
	for <l2tpext-archive@odin.ietf.org>; Thu, 27 Jul 2000 11:31:30 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns1.sailpix.com (8.8.8/8.6.9) id HAA13013; Thu, 27 Jul 2000 07:47:23 -0700 (PDT)
Received: from fwns1.raleigh.ibm.com (fwns1d.raleigh.ibm.com [204.146.167.235]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id HAA13005 for <l2tp@ipsec.org>; Thu, 27 Jul 2000 07:46:46 -0700 (PDT)
Received: from rtpmail01.raleigh.ibm.com (rtpmail01.raleigh.ibm.com [9.37.172.24])
	by fwns1.raleigh.ibm.com (8.9.0/8.9.0/RTP-FW-1.2) with ESMTP id KAA17776;
	Thu, 27 Jul 2000 10:45:33 -0400
Received: from ludwigia.raleigh.ibm.com (ludwigia.raleigh.ibm.com [9.37.60.3])
	by rtpmail01.raleigh.ibm.com (8.8.5/8.8.5/RTP-ral-1.1) with ESMTP id KAA30578;
	Thu, 27 Jul 2000 10:45:32 -0400
Received: from ludwigia.raleigh.ibm.com (localhost [127.0.0.1]) by ludwigia.raleigh.ibm.com (8.9.3/8.7/RTP-ral-1.0) with ESMTP id KAA17479; Thu, 27 Jul 2000 10:43:31 -0400
Message-Id: <200007271443.KAA17479@ludwigia.raleigh.ibm.com>
To: danny@ambernetworks.com
cc: James Carlson <carlson@workingcode.com>, l2tp@ipsec.org
Subject: Re: L2TP charter 
In-Reply-To: Message from Danny McPherson <danny@ambernetworks.com> 
   of "Thu, 27 Jul 2000 08:08:43 MDT." <200007271408.IAA25124@tcb.net> 
Date: Thu, 27 Jul 2000 10:43:31 -0400
From: Thomas Narten <narten@raleigh.ibm.com>
Sender: owner-l2tp@ipsec.org
Precedence: bulk

Danny McPherson <danny@ambernetworks.com> writes:
> > I don't understand your objection to the "heavier" baggage of other IP
> > tunneling protocols.  L2TP has a default encapsulation of UDP-GRE and
> > thus is heavier than IP-GRE.  There's some precedent for using IP-GRE
> > encapsulation to carry non-IP payloads across IP networks.  Do we need
> > another?

> L2TP clearly provides what's required to support IP-based emulation
> services, tunnel management and similar are already present.  GRE
> has none of this.

Can you please summarize just what features are needed that are not
present in GRE (or pick your other favorite tunneling scheme)? This
has always been a bit of a gray area to me in that different folks
have different ideas about what is really needed.

I ask also because there are a number of tunneling technologies in
place, yet every WG seems seems to want to tweak its own favorite
rather than fixing one of the more general ones so that it works
properly for a broad range of applications. Case in point, GRE was
recently put on standards track because it was favored by UDLR over
something like IP in IP (which was already on Standards Track). A big
argument for GRE was that it was widely deployed/available.

I can assure you that lots of folks with tunneling needs will never
use L2TP to tunnel (say IP).  I would love to see an effort to clean
up/extend an existing tunneling mechanism to make it generally useful
to lots of applications. But I do wonder whether L2TP is the right
starting point for this.

Thomas


From owner-l2tp@ipsec.org  Thu Jul 27 11:45: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 LAA22188
	for <l2tpext-archive@odin.ietf.org>; Thu, 27 Jul 2000 11:45:11 -0400 (EDT)
Received: (from majordomo@localhost) by ns1.sailpix.com (8.8.8/8.6.9) id HAA13048; Thu, 27 Jul 2000 07:54:45 -0700 (PDT)
Received: from amberex01.ambernetworks.com (207-33-177-98.ncal.verio.com [207.33.177.98] (may be forged)) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id HAA13044 for <l2tp@ipsec.org>; Thu, 27 Jul 2000 07:54:21 -0700 (PDT)
Received: by amberex01.ambernetworks.com with Internet Mail Service (5.5.2650.21)
	id <P4JA212D>; Thu, 27 Jul 2000 07:57:09 -0700
Message-ID: <50B17D03735BD411B2D000D0B7237DED36B420@amberex01.ambernetworks.com>
From: Danny McPherson <Danny@ambernetworks.com>
To: "'Thomas Narten'" <narten@raleigh.ibm.com>
Cc: l2tp@ipsec.org
Subject: RE: L2TP charter 
Date: Thu, 27 Jul 2000 07:57:09 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-l2tp@ipsec.org
Precedence: bulk


> Can you please summarize just what features are needed 
> that are not present in GRE (or pick your other favorite 
> tunneling scheme)? This has always been a bit of a gray 
> area to me in that different folks have different ideas 
> about what is really needed.

The dynamic call capabilities are the most obvious benefit.

>I ask also because there are a number of tunneling 
>technologies in place, yet every WG seems seems to 
>want to tweak its own favorite rather than fixing one 
>of the more general ones so that it works properly 
>for a broad range of applications. Case in point, GRE was
>recently put on standards track because it was favored by 
>UDLR over something like IP in IP (which was already on 
>Standards Track). A big argument for GRE was that it was 
>widely deployed/available.

>I can assure you that lots of folks with tunneling needs 
>will never use L2TP to tunnel (say IP).  I would love to 
>see an effort to clean up/extend an existing tunneling 
>mechanism to make it generally useful to lots of applications. 
>But I do wonder whether L2TP is the right starting point for this.

L2TP seems to be the most obvious place, primarily
because of it's dynamic call capabilities.  It
clearly requires the least amount of work to become
the IP tunneling protocol of choice.  The work
into existing protocol such as GRE are simply because
of current deployment in static environments, and 
existing code.  

A number of folks without the legacy baggage have 
selected L2TP for this purpose, simply because it's
clearly already closest to the end goal.

-danny


From owner-l2tp@ipsec.org  Thu Jul 27 12:26: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 MAA27454
	for <l2tpext-archive@odin.ietf.org>; Thu, 27 Jul 2000 12:26:18 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns1.sailpix.com (8.8.8/8.6.9) id IAA13068; Thu, 27 Jul 2000 08:09:56 -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 IAA13062 for <l2tp@ipsec.org>; Thu, 27 Jul 2000 08:08:49 -0700 (PDT)
Received: (from carlson@localhost)
	by h006008986325.ne.mediaone.net (8.9.3/8.9.3) id LAA18556;
	Thu, 27 Jul 2000 11:08:46 -0400
From: James Carlson <carlson@workingcode.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14720.20605.762535.820263@h006008986325.ne.mediaone.net>
Date: Thu, 27 Jul 2000 11:08:45 -0400 (EDT)
To: Danny McPherson <Danny@ambernetworks.com>
Cc: l2tp@ipsec.org
Subject: RE: L2TP charter 
In-Reply-To: Danny McPherson's message of 27 July 2000 07:49:41
References: <50B17D03735BD411B2D000D0B7237DED36B41F@amberex01.ambernetworks.com>
X-Mailer: VM 6.75 under Emacs 20.6.1
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Danny McPherson writes:
> >Look at any Cisco router.  You can already configure 
> >GRE tunnels for any protocol you like.  I can see no 
> >particular benefit from L2TP's management or negotiation 
> >capabilities.  You'll still have to manually configure 
> >explicit traffic-engineered paths and manually configure
> >associations between the tunnel endpoints. 
> 
> Eh?  I think you're a bit confused here.  TE isn't
> required, and it's clearly a bit difficult to accomplish
> in only DA-based packet networks (i.e. IP networks).

It is required if you hope to emulate Frame Relay's advantages to any
extent.  Yes, it's difficult, but, no it's not impossible in a
hop-by-hop network.

That's beside the point.  If you use L2TP, you'll *still* have to
manually configure the tunnel endpoints.  You'll need to give the LAC
a list of LNS addresses to use for each endpoint in some way.  One way
to do this would be to propose RADIUS extensions to translate, say,
X.121 addresses into IP addresses needed for L2TP.  This is precisely
the same amount of work that's required to make the existing IP-GRE
tunneling mechanism function in the same way.  There's no difference
between the two, and the AVPs still don't provide a benefit for this
application.

> That small amount of handshake, coupled with the AVP 
> concept and the other call management stuff makes it
> an ideal choice for circuit emulation over IP.  Much,
> much more desirable than IP.  If it were really as 
> simple as you say, we wouldn't need L2TP, we could 
> just use GRE, no?

The AVP concept and the existing call management stuff are useful for
the case where you've got many PPP users needing to be tunneled to
various locations based on details available within the PPP
authentication protocols.  They don't much help you to do anything
useful otherwise.

If you believe that these L2TP features are helpful in some way, it
would be helpful to see a written proposal.

> > No.  Where it duplicates an existing mechanism, any 
> > such proposal is to the detriment, not benefit, of 
> > the Internet.
> 
> You've still not explained to me how a simple Encapsulation
> Protocol such as GRE performs these functions?  Why, is that?

Two reasons.  First, for new features, the burden of proof is always
on the claimant.  Because you're suggesting that L2TP be extended for
this new purpose, that happens to be you.  Second, the use of GRE for
tunneling arbitrary protocols is already well described in RFCs 2784
and 1701.

> >If you really need to use L2TP to do this, use the 
> >existing mechanism. Run PPP over L2TP, and run your L3 
> > protocol over PPP.  That's what PPP is for.  It already 
> > does what you want.
> 
> Ahh, and add additional network overhead, and packet processing,
> for that matter -- all unnecessary.  I guess with enough glue 
> you could do anything.

The additional overhead is (with both ACFC and PFC negotiated) exactly
one octet representing the PPP protocol number.  In the worst cast, if
you don't negotiate those options for some reason, it's at most four
octets.  In comparison with deploying yet another protocol extension,
that's not much of a burden.

If that is a burden for some particular application, then I'd suggest
that IP is unnecessary as well.  Run in ships-in-the-night mode, and
you'll be better off.  You'll discard 20+8+4 = 32 octets over L2TP in
that manner.  That's a much bigger win than avoiding PPP's overhead.

> >I wasn't suggesting beefing up any other protocol 
> >to support this.  The non-IP transport and interworking 
> >capabilities of MPLS already exist.  The manually 
> >configured GRE tunneling capabilities already
> >exist and have a long history.
> 
> Manually configured, yes.  Long history as hacks, yes.
> So you do see the point -- maybe?

No.  You'll still need manual configuration with L2TP unless you're
proposing extensions to many other protocols as well.

> You're still missing the point.  L2TP provides the 
> dynamic call capabilities that ISPs want.

No, it doesn't.  L2TP has no general tunnel endpoint locator
mechanism.

>  Not a 
> bunch of unmanageable GRE gunk.  

L2TP data transport is just GRE gunk.

> Putting it over PPP would obviously work, though this 
> increases network overhead significantly

How is one octet of overhead per packet considered significant?
What's the context in which this is true?

> with no obvious 
> benefit.  

The obvious benefit is that *no new extensions* are required.  At
least in the standard IETF balancing act for such things, that's quite
a significant benefit.

> L2TP is clearly the place to do this.  If requires the
> least amount of work and working implementations have 
> been demonstrated.  

It requires extensions and duplicates features already available in
existing protocols.  I don't think you've made the case that L2TP is
clearly the place to supply tunneling facilities all for possible L2
or L3 protocols.

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


From owner-l2tp@ipsec.org  Thu Jul 27 13:26:40 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 NAA08372
	for <l2tpext-archive@odin.ietf.org>; Thu, 27 Jul 2000 13:26:39 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns1.sailpix.com (8.8.8/8.6.9) id JAA13272; Thu, 27 Jul 2000 09:34:31 -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 JAA13268 for <l2tp@ipsec.org>; Thu, 27 Jul 2000 09:34:18 -0700 (PDT)
Received: (from carlson@localhost)
	by h006008986325.ne.mediaone.net (8.9.3/8.9.3) id MAA20294;
	Thu, 27 Jul 2000 12:34:16 -0400
From: James Carlson <carlson@workingcode.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14720.25736.436864.266552@h006008986325.ne.mediaone.net>
Date: Thu, 27 Jul 2000 12:34:16 -0400 (EDT)
To: James Carlson <carlson@workingcode.com>
Cc: Danny McPherson <Danny@ambernetworks.com>, l2tp@ipsec.org
Subject: RE: L2TP charter 
In-Reply-To: James Carlson's message of 27 July 2000 11:08:45
References: <50B17D03735BD411B2D000D0B7237DED36B41F@amberex01.ambernetworks.com>
	<14720.20605.762535.820263@h006008986325.ne.mediaone.net>
X-Mailer: VM 6.75 under Emacs 20.6.1
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

James Carlson writes:
> If that is a burden for some particular application, then I'd suggest
> that IP is unnecessary as well.  Run in ships-in-the-night mode, and
> you'll be better off.  You'll discard 20+8+4 = 32 octets over L2TP in
> that manner.  That's a much bigger win than avoiding PPP's overhead.

Fingers moving faster than brain -- that should be "discard a minimum
of 20+8+6 = 34 octets (plus four more if sequencing on the data
channel were used)."

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


From owner-l2tp@ipsec.org  Thu Jul 27 19:05: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 TAA29659
	for <l2tpext-archive@odin.ietf.org>; Thu, 27 Jul 2000 19:05:56 -0400 (EDT)
Received: (from majordomo@localhost) by ns1.sailpix.com (8.8.8/8.6.9) id PAA13706; Thu, 27 Jul 2000 15:00:20 -0700 (PDT)
Received: from franklin.cisco.com (franklin.cisco.com [171.70.156.17]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id PAA13696 for <l2tp@ipsec.org>; Thu, 27 Jul 2000 15:00:00 -0700 (PDT)
Received: from gwz (atlantis-dial-1-6.cisco.com [171.68.181.7]) by franklin.cisco.com (8.8.6 (PHNE_17190)/CISCO.SERVER.1.2) with SMTP id OAA25096; Thu, 27 Jul 2000 14:58:55 -0700 (PDT)
Reply-To: <gwz@cisco.com>
From: "Glen Zorn" <gwz@cisco.com>
To: "James Carlson" <carlson@workingcode.com>,
        "Danny McPherson" <Danny@ambernetworks.com>
Cc: <l2tp@ipsec.org>
Subject: RE: L2TP charter 
Date: Thu, 27 Jul 2000 14:56:55 -0700
Message-ID: <NDBBIHMPILAAGDHPCIOPGEFNCJAA.gwz@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
In-Reply-To: <14720.20605.762535.820263@h006008986325.ne.mediaone.net>
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

James Carlson [mailto://carlson@workingcode.com] writes:

> Danny McPherson writes:
> > >Look at any Cisco router.  You can already configure 
> > >GRE tunnels for any protocol you like.  I can see no 
> > >particular benefit from L2TP's management or negotiation 
> > >capabilities.  You'll still have to manually configure 
> > >explicit traffic-engineered paths and manually configure
> > >associations between the tunnel endpoints. 
> > 
> > Eh?  I think you're a bit confused here.  TE isn't
> > required, and it's clearly a bit difficult to accomplish
> > in only DA-based packet networks (i.e. IP networks).
> 
> It is required if you hope to emulate Frame Relay's advantages to any
> extent.  Yes, it's difficult, but, no it's not impossible in a
> hop-by-hop network.
> 
> That's beside the point.  If you use L2TP, you'll *still* have to
> manually configure the tunnel endpoints.  You'll need to give the LAC
> a list of LNS addresses to use for each endpoint in some way.  One way
> to do this would be to propose RADIUS extensions to translate, say,
> X.121 addresses into IP addresses needed for L2TP.  

I believe that this could be done with existing attributes from RFC 2868.

<text deleted>


From owner-l2tp@ipsec.org  Thu Jul 27 20:32:05 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 UAA09406
	for <l2tpext-archive@odin.ietf.org>; Thu, 27 Jul 2000 20:32:04 -0400 (EDT)
Received: (from majordomo@localhost) by ns1.sailpix.com (8.8.8/8.6.9) id QAA13840; Thu, 27 Jul 2000 16:39:00 -0700 (PDT)
Received: from amberex01.ambernetworks.com (207-33-177-98.ncal.verio.com [207.33.177.98] (may be forged)) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id QAA13836 for <l2tp@ipsec.org>; Thu, 27 Jul 2000 16:38:21 -0700 (PDT)
Received: by amberex01.ambernetworks.com with Internet Mail Service (5.5.2650.21)
	id <P4JA2FT5>; Thu, 27 Jul 2000 16:41:11 -0700
Message-ID: <50B17D03735BD411B2D000D0B7237DED36B438@amberex01.ambernetworks.com>
From: Danny McPherson <Danny@ambernetworks.com>
To: "'l2tp@ipsec.org'" <l2tp@ipsec.org>
Subject: L2TP charter
Date: Thu, 27 Jul 2000 16:41:03 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="windows-1252"
Sender: owner-l2tp@ipsec.org
Precedence: bulk


OK, let's try this again....

-*Why not use GRE instead of L2TP?  

For starters, if you're of the opinion that GRE is 
sufficient, perhaps reflecting on the initial justification 
of L2TP itself would be of benefit?  That is, why were PPP 
PDUs not tunneled through GRE?  The same advantages L2TP 
brought to PPP can be realized with non-PPP payloads as well,
with little work.

GRE provides only an encapsulation scheme, it provides no 
end-to-end signaling mechanism.

GRE does not generate a Tunnel ID, which can be used to 
assist with processing tunnel payload in hardware.

L2TP allows aggregation of large number of sessions into 
a single tunnel.  This helps to scale the management of 
total number of user sessions in the network.  The ADSL 
forum's proposal of L2TP over AAL5 is an excellent example 
of reducing the number of VCC's in the network.

-*Why not use MPLS?

The intent is to provide a generic tunneling mechanism for
IP networks.  Seamless integration with MPLS is then 
trivial.

An MPLS-based mechanism requires -- MPLS.

MPLS doesn't provide an end-to-end signaling mechanism.

-*Why not do it over PPP?

PPP doesn't provide sufficient parameter capabilities to 
support circuit emulation services (e.g. negotiation of 
specific frame relay or ATM parameters).  As a result, 
another protocol has to be developed.  With both, an 
unnecessary, unclean overlap in function occurs.  This 
quickly became obvious when we were implementing it.

Also, requiring PPP to use L2TP simply isn't clean 
architecturally.

In addition, unnecessary PPP overhead results.  Overhead from
PPP negotiation, it's state machine, and network overhead from
header bytes.

-*Other issues?

L2TP provides for ease of implementation in hardware as the 
switching can be done based on Tunnel and Session ID.

Current proposal is completely inter-operable with existing 
implementations as they can reject Service Type AVP.

The preservation of QoS for L2TP is a function of what's in the 
network (either DiffServ, MPLS or others), and not a function 
of L2TP itself.

L2TP provides a common, well understood mechanism for unifying 
subscriber management tunneling already.

The proposed model doesn't require an intervening LNS.  It 
provides direct LAC - LAC support.

It's obvious that every model will require some configuration.
The amount required, however, is a key component of the value
proposition.


From owner-l2tp@ipsec.org  Thu Jul 27 20:36: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 UAA09904
	for <l2tpext-archive@odin.ietf.org>; Thu, 27 Jul 2000 20:36:37 -0400 (EDT)
Received: (from majordomo@localhost) by ns1.sailpix.com (8.8.8/8.6.9) id QAA13817; Thu, 27 Jul 2000 16:27:51 -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 QAA13813 for <l2tp@ipsec.org>; Thu, 27 Jul 2000 16:27:38 -0700 (PDT)
Received: from ericsson.com (calcium.dev.acc.am.ericsson.se [129.192.57.200])
	by mailsrv.acc.com (8.9.3/8.9.1) with ESMTP id QAA24852;
	Thu, 27 Jul 2000 16:30:58 -0700 (PDT)
Message-ID: <3980C672.16460E45@ericsson.com>
Date: Thu, 27 Jul 2000 16:32:02 -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: Danny McPherson <Danny@ambernetworks.com>
CC: l2tp@ipsec.org
Subject: Re: L2TP charter
References: <50B17D03735BD411B2D000D0B7237DED36B420@amberex01.ambernetworks.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@ipsec.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



Danny McPherson wrote:
> 
> > [snip...]
> 
> The dynamic call capabilities are the most obvious benefit.

what do you mean by "dynamic call capabilities"?

evan
-


From owner-l2tp@ipsec.org  Thu Jul 27 21:02:16 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 VAA12729
	for <l2tpext-archive@odin.ietf.org>; Thu, 27 Jul 2000 21:02:15 -0400 (EDT)
Received: (from majordomo@localhost) by ns1.sailpix.com (8.8.8/8.6.9) id RAA13959; Thu, 27 Jul 2000 17:14:45 -0700 (PDT)
Received: from drawbridge.ascend.com (drawbridge.ascend.com [198.4.92.1]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id RAA13955 for <l2tp@ipsec.org>; Thu, 27 Jul 2000 17:14:30 -0700 (PDT)
Received: from fw-ext.ascend.com (fw-ext [198.4.92.5])
	by drawbridge.ascend.com (8.9.1a/8.9.1) with SMTP id RAA00411;
	Thu, 27 Jul 2000 17:06:57 -0700 (PDT)
Received: from russet.ascend.com by fw-ext.ascend.com
          via smtpd (for drawbridge.ascend.com [198.4.92.1]) with SMTP; 28 Jul 2000 00:14:23 UT
Received: from wopr.eng.ascend.com (wopr.eng.ascend.com [206.65.212.178])
	by russet.ascend.com (8.9.1a/8.9.1) with ESMTP id RAA22576;
	Thu, 27 Jul 2000 17:14:22 -0700 (PDT)
Received: from scamp.eng.ascend.com (scamp.eng.ascend.com [135.140.53.42])
	by wopr.eng.ascend.com (8.9.1/8.9.1) with ESMTP id RAA26775;
	Thu, 27 Jul 2000 17:14:22 -0700 (PDT)
Received: from igoyret-pc.eng.ascend.com by scamp.eng.ascend.com (8.8.8+Sun/SMI-SVR4)
	id RAA00776; Thu, 27 Jul 2000 17:14:21 -0700 (PDT)
Message-Id: <3.0.5.32.20000727171531.01439360@scamp.eng.ascend.com>
X-Sender: igoyret@scamp.eng.ascend.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32)
Date: Thu, 27 Jul 2000 17:15:31 -0700
To: Danny McPherson <Danny@ambernetworks.com>
From: Ignacio Goyret <igoyret@lucent.com>
Subject: Re: L2TP charter
Cc: "'l2tp@ipsec.org'" <l2tp@ipsec.org>
In-Reply-To: <50B17D03735BD411B2D000D0B7237DED36B438@amberex01.ambernetw
 orks.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-l2tp@ipsec.org
Precedence: bulk

At 04:41 PM 7/27/00 -0700, Danny McPherson wrote:
>
>GRE provides only an encapsulation scheme, it provides no 
>end-to-end signaling mechanism.
>
>GRE does not generate a Tunnel ID, which can be used to 
>assist with processing tunnel payload in hardware.

Read rfc2107 for a solution that implements a signaling mechanism
for GRE that negotiates a 'tunnel ID'.



From owner-l2tp@ipsec.org  Thu Jul 27 21:06:05 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 VAA13155
	for <l2tpext-archive@odin.ietf.org>; Thu, 27 Jul 2000 21:06:04 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by ns1.sailpix.com (8.8.8/8.6.9) id RAA13973; Thu, 27 Jul 2000 17:21:03 -0700 (PDT)
Received: from calcite.rhyolite.com (calcite.rhyolite.com [38.159.140.3]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id RAA13969 for <l2tp@ipsec.org>; Thu, 27 Jul 2000 17:20:10 -0700 (PDT)
Received: (from vjs@localhost)
	by calcite.rhyolite.com (8.11.0/calcite) id e6S0K9A02445
	for l2tp@ipsec.org  env-from <vjs>;
	Thu, 27 Jul 2000 18:20:09 -0600 (MDT)
Date: Thu, 27 Jul 2000 18:20:09 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200007280020.e6S0K9A02445@calcite.rhyolite.com>
To: l2tp@ipsec.org
Subject: Re: L2TP charter
Sender: owner-l2tp@ipsec.org
Precedence: bulk

> From: Danny McPherson <Danny@ambernetworks.com>

> ...
> -*Why not use GRE instead of L2TP?  
>
> For starters, if you're of the opinion that GRE is 
> sufficient, perhaps reflecting on the initial justification 
> of L2TP itself would be of benefit?  That is, why were PPP 
> PDUs not tunneled through GRE?  The same advantages L2TP 
> brought to PPP can be realized with non-PPP payloads as well,
> with little work. ...

GRE is in a different universe.

> -*Why not use MPLS?
>
> The intent is to provide a generic tunneling mechanism for
> IP networks.  Seamless integration with MPLS is then 
> trivial.
>
> An MPLS-based mechanism requires -- MPLS.
>
> MPLS doesn't provide an end-to-end signaling mechanism.

Those points are not mutaual consisttent.

> -*Why not do it over PPP?
>
> PPP doesn't provide sufficient parameter capabilities to 
> support circuit emulation services (e.g. negotiation of 
> specific frame relay or ATM parameters).  As a result, 
> another protocol has to be developed.  With both, an 
> unnecessary, unclean overlap in function occurs.  This 
> quickly became obvious when we were implementing it.
>
> Also, requiring PPP to use L2TP simply isn't clean 
> architecturally.
>
> In addition, unnecessary PPP overhead results.  Overhead from
> PPP negotiation, it's state machine, and network overhead from
> header bytes.

The first seems to me to assume characteristics of L2TP that do not exist.
The second is content free.
The third is both wrong and a red herring.

> -*Other issues?
>
> L2TP provides for ease of implementation in hardware as the 
> switching can be done based on Tunnel and Session ID.

Ditto for all of the others.

> Current proposal is completely inter-operable with existing 
> implementations as they can reject Service Type AVP.

ditto.

> The preservation of QoS for L2TP is a function of what's in the 
> network (either DiffServ, MPLS or others), and not a function 
> of L2TP itself.

ditto.

> L2TP provides a common, well understood mechanism for unifying 
> subscriber management tunneling already.

Assumes conclusion. 

> The proposed model doesn't require an intervening LNS.  It 
> provides direct LAC - LAC support.
>
> It's obvious that every model will require some configuration.
> The amount required, however, is a key component of the value
> proposition.

ditto.


L2TP is a very sick protocol that has been almost wrecked
by exactly such accretion as this proposal.  L2TP started out
as a simple thing to solve a couple of known problems that
already had more or less proprietary solutions.   Look at the
mess it has become.
For that matter PPP has a similar history.

The last thing the IETF needs is yet another tunnel protocol.
We already have at least half a dozen (not counting such as IP/SMTP).
Intellectual honesty requires admitting that the proposal
is yet another tunnel protocol, even if it is cloaked in L2TP colors.

See for another such story.
http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=506636+517178+/usr/local/www/db/text/1999/freebsd-hackers/19991003.freebsd-hackers

Vernon Schryver    vjs@rhyolite.com


From owner-l2tp@diameter.org  Thu Jul 27 22:32:50 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA00711
	for <l2tpext-archive@odin.ietf.org>; Thu, 27 Jul 2000 22:32:49 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e6RNgl316000
	for l2tp-list; Thu, 27 Jul 2000 16:42:47 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from sj-msg-core-2.cisco.com (sj-msg-core-2.cisco.com [171.69.43.88])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e6RNgid15994
	for <l2tp@l2tp.net>; Thu, 27 Jul 2000 16:42:44 -0700
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 QAA01610
	for <l2tp@l2tp.net>; Thu, 27 Jul 2000 16:46:33 -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 TAA09325 for <l2tp@l2tp.net>; Thu, 27 Jul 2000 19:46:16 -0400 (EDT)
Message-ID: <3980C9B8.44AA52FA@cisco.com>
Date: Thu, 27 Jul 2000 19:46:00 -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: l2tp@l2tp.net
Subject: test
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Test, please ignore.


From owner-l2tp@diameter.org  Thu Jul 27 23:10:59 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA05115
	for <l2tpext-archive@odin.ietf.org>; Thu, 27 Jul 2000 23:10:58 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e6S0FJ016023
	for l2tp-list; Thu, 27 Jul 2000 17:15:19 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e6S0FHd16017
	for <l2tp@l2tp.net>; Thu, 27 Jul 2000 17:15:17 -0700
Received: from townsley-ultra.cisco.com (townsley-ultra.cisco.com [161.44.58.38])
	by sj-msg-core-1.cisco.com (8.9.3/8.9.1) with ESMTP id RAA10363
	for <l2tp@l2tp.net>; Thu, 27 Jul 2000 17:19:06 -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 UAA09342 for <l2tp@l2tp.net>; Thu, 27 Jul 2000 20:18:50 -0400 (EDT)
Message-ID: <3980D15A.2DC6E793@cisco.com>
Date: Thu, 27 Jul 2000 20:18:34 -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: l2tp@l2tp.net
Subject: May I introduce our new host...
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


Many thanks to Pat Calhoun for volunteering to be the new L2TP mailing
list host. Please address new messages to l2tp@l2tp.net. You can find
some l2tp information at www.l2tp.net, archives since Jan 6, 2000 are
now online here as well. We will be consolidating the archives from the
various past servers shortly. l2tp@ipsec.org will continue to forward
messages until Dave retires or runs into yet another insurmountable
Y2K-type bug in the software he is using (will pppoe@ipsec.org make it
through the unix epoch?). Seriously, many many thanks again to Dave
Carrel for hosting the list over the past year. 

Back to your regularly scheduled discussion,

- Mark


From owner-l2tp@diameter.org  Fri Jul 28 00:04:40 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA14440
	for <l2tpext-archive@odin.ietf.org>; Fri, 28 Jul 2000 00:04:39 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e6S1QIt16113
	for l2tp-list; Thu, 27 Jul 2000 18:26:18 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e6S1QEd16107
	for <l2tp@l2tp.net>; Thu, 27 Jul 2000 18:26:14 -0700
Received: from tcb.net (tcb.net [205.168.100.1]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id SAA14073 for <l2tp@ipsec.org>; Thu, 27 Jul 2000 18:29:56 -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 TAA28430
	for <l2tp@ipsec.org>; Thu, 27 Jul 2000 19:30:48 -0600
Message-Id: <200007280130.TAA28430@tcb.net>
X-Mailer: exmh version 2.0.3
To: l2tp@ipsec.org
From: Danny McPherson <danny@ambernetworks.com>
Reply-To: danny@ambernetworks.com
Subject: Re: L2TP charter 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 27 Jul 2000 19:30:48 -0600
Sender: owner-l2tp@diameter.org
Precedence: bulk


>> -*Why not use MPLS?
>>
>> The intent is to provide a generic tunneling mechanism for
>> IP networks.  Seamless integration with MPLS is then 
>> trivial.
>>
>> An MPLS-based mechanism requires -- MPLS.
>>
>> MPLS doesn't provide an end-to-end signaling mechanism.
>
>Those points are not mutaual consisttent.

Not following you here?

>> -*Why not do it over PPP?
>>
>> PPP doesn't provide sufficient parameter capabilities to 
>> support circuit emulation services (e.g. negotiation of 
>> specific frame relay or ATM parameters).  As a result, 
>> another protocol has to be developed.  With both, an 
>> unnecessary, unclean overlap in function occurs.  This 
>> quickly became obvious when we were implementing it.
>>
>> Also, requiring PPP to use L2TP simply isn't clean 
>> architecturally.
>>
>> In addition, unnecessary PPP overhead results.  Overhead from
>> PPP negotiation, it's state machine, and network overhead from
>> header bytes.
>
>The first seems to me to assume characteristics of L2TP that 
>do not exist.

Which are proposed in our draft, have you read it?

>The second is content free.

Though makes a point --  if another higher-layer protocol
that resides parallel to PPP and performs the same (and 
more functions for the application), it doesn't make sense 
to use PPP as well.

>The third is both wrong and a red herring.

Care to clue me in here?

>> L2TP provides for ease of implementation in hardware as the 
>> switching can be done based on Tunnel and Session ID.
>
>Ditto for all of the others.

Please do elaborate on other IP-based tunneling protocols that 
provide this support (other than ATMP -- for obvious reasons).

>
>> Current proposal is completely inter-operable with existing 
>> implementations as they can reject Service Type AVP.
>
>ditto.

Ditto what?
>
>> The preservation of QoS for L2TP is a function of what's in the 
>> network (either DiffServ, MPLS or others), and not a function 
>> of L2TP itself.
>
>ditto.

Uh, yeah.

>
>> L2TP provides a common, well understood mechanism for unifying 
>> subscriber management tunneling already.
>
>Assumes conclusion. 

Not following you here?

>> The proposed model doesn't require an intervening LNS.  It 
>> provides direct LAC - LAC support.
>>
>> It's obvious that every model will require some configuration.
>> The amount required, however, is a key component of the value
>> proposition.
>
>ditto.
>
>
>L2TP is a very sick protocol that has been almost wrecked
>by exactly such accretion as this proposal.  L2TP started out
>as a simple thing to solve a couple of known problems that
>already had more or less proprietary solutions.   Look at the
>mess it has become.
>For that matter PPP has a similar history.

I suppose you'd prefer to develop a new protocol for every 
tiny new enhancement?  Not happening...

>The last thing the IETF needs is yet another tunnel protocol.

My Point!

>Already have at least half a dozen (not counting such as IP/SMTP).

IP/SMTP, stretching now aren't we...

>Intellectual honesty requires admitting that the proposal
>is yet another tunnel protocol, even if it is cloaked in L2TP colors.

How exactly does a single new AVP (similar to "bearer" one on the
2661bis draft) create an entirely new protocol here?  Given, the 
LAC-LAC model is new, though it's as much a semantics issue.

-danny 




From owner-l2tp@diameter.org  Fri Jul 28 03:09:22 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA29436
	for <l2tpext-archive@odin.ietf.org>; Fri, 28 Jul 2000 03:09:21 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e6S4IAj16229
	for l2tp-list; Thu, 27 Jul 2000 21:18:10 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e6S4I7d16223
	for <l2tp@l2tp.net>; Thu, 27 Jul 2000 21:18:07 -0700
Received: from amberex01.ambernetworks.com (207-33-177-98.ncal.verio.com [207.33.177.98] (may be forged)) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id VAA14181 for <l2tp@ipsec.org>; Thu, 27 Jul 2000 21:21:50 -0700 (PDT)
Received: by amberex01.ambernetworks.com with Internet Mail Service (5.5.2650.21)
	id <P4JA2GDR>; Thu, 27 Jul 2000 21:24:40 -0700
Message-ID: <50B17D03735BD411B2D000D0B7237DED0B1082@amberex01.ambernetworks.com>
From: Andy Koscinski <ANDYK@ambernetworks.com>
To: Ignacio Goyret <igoyret@lucent.com>,
        Danny McPherson
	 <Danny@ambernetworks.com>
Cc: "'l2tp@ipsec.org'" <l2tp@ipsec.org>
Subject: RE: L2TP charter
Date: Thu, 27 Jul 2000 21:24:29 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-l2tp@diameter.org
Precedence: bulk

> -----Original Message-----
> From: Ignacio Goyret [mailto:igoyret@lucent.com]
> Sent: Thursday, July 27, 2000 5:16 PM
> To: Danny McPherson
> Cc: 'l2tp@ipsec.org'
> Subject: Re: L2TP charter
> 
> 
> At 04:41 PM 7/27/00 -0700, Danny McPherson wrote:
> >
> >GRE provides only an encapsulation scheme, it provides no 
> >end-to-end signaling mechanism.
> >
> >GRE does not generate a Tunnel ID, which can be used to 
> >assist with processing tunnel payload in hardware.
> 
> Read rfc2107 for a solution that implements a signaling mechanism
> for GRE that negotiates a 'tunnel ID'.
>

I would advise against using the tunneling
as defined in the rfc2107 for the purpose
of circuit emulation over IP on the following counts:

1. the "tunnel id" is not supported by the GRE any more:
The tunnel id was carried in the "key" field of the GRE tunnel packets
as defined in the RFC1701 (10/1994). The "key" field has been removed
from the newest GRE RFC2784 (3/2000), quote from RFC2784:
"the GRE header will never contain the Key, Sequence Number or Routing 
fields specified in RFC 1701".

2. the tunnel id was 16 bit value, which would never scale up to
the number of sessions required for circuit emulation.
L2TP can support 64,000 x 64,000 sessions.

3. in RFC2107 there is no aggregation scheme to bundle sessions to tunnels.

4. rfc2107 is informational and Ascend proprietory dated 2/97, 
before L2TP was advanced to a standard. A quote from RFC2107:
"There is ongoing effort in an IETF working group which could 
result in a standards track document which specifies a protocol 
which provides similar functionality."


andyk@ambernetworks.com 


From owner-l2tp@diameter.org  Fri Jul 28 03:52:23 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA13269
	for <l2tpext-archive@odin.ietf.org>; Fri, 28 Jul 2000 03:52:22 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e6S4eGG16247
	for l2tp-list; Thu, 27 Jul 2000 21:40:16 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e6S4eDd16241
	for <l2tp@l2tp.net>; Thu, 27 Jul 2000 21:40:13 -0700
Received: from drawbridge.ascend.com (drawbridge.ascend.com [198.4.92.1]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id VAA14191 for <l2tp@ipsec.org>; Thu, 27 Jul 2000 21:43:56 -0700 (PDT)
Received: from fw-ext.ascend.com (fw-ext [198.4.92.5])
	by drawbridge.ascend.com (8.9.1a/8.9.1) with SMTP id VAA11196;
	Thu, 27 Jul 2000 21:36:29 -0700 (PDT)
Received: from russet.ascend.com by fw-ext.ascend.com
          via smtpd (for drawbridge.ascend.com [198.4.92.1]) with SMTP; 28 Jul 2000 04:43:55 UT
Received: from wopr.eng.ascend.com (wopr.eng.ascend.com [206.65.212.178])
	by russet.ascend.com (8.9.1a/8.9.1) with ESMTP id VAA24178;
	Thu, 27 Jul 2000 21:43:55 -0700 (PDT)
Received: from scamp.eng.ascend.com (scamp.eng.ascend.com [135.140.53.42])
	by wopr.eng.ascend.com (8.9.1/8.9.1) with ESMTP id VAA01874;
	Thu, 27 Jul 2000 21:43:55 -0700 (PDT)
Received: from igoyret-pc.eng.ascend.com by scamp.eng.ascend.com (8.8.8+Sun/SMI-SVR4)
	id VAA06239; Thu, 27 Jul 2000 21:43:53 -0700 (PDT)
Message-Id: <3.0.5.32.20000727214514.00b082b0@scamp.eng.ascend.com>
X-Sender: igoyret@scamp.eng.ascend.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32)
Date: Thu, 27 Jul 2000 21:45:14 -0700
To: Andy Koscinski <ANDYK@ambernetworks.com>
From: Ignacio Goyret <igoyret@lucent.com>
Subject: RE: L2TP charter
Cc: Ignacio Goyret <igoyret@lucent.com>,
        Danny McPherson <Danny@ambernetworks.com>,
        "'l2tp@ipsec.org'" <l2tp@ipsec.org>
In-Reply-To: <50B17D03735BD411B2D000D0B7237DED0B1082@amberex01.ambernetw
 orks.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-l2tp@diameter.org
Precedence: bulk

At 09:24 PM 7/27/00 -0700, Andy Koscinski wrote:
>> >
>> >GRE provides only an encapsulation scheme, it provides no 
>> >end-to-end signaling mechanism.
>> >
>> >GRE does not generate a Tunnel ID, which can be used to 
>> >assist with processing tunnel payload in hardware.
>> 
>> Read rfc2107 for a solution that implements a signaling mechanism
>> for GRE that negotiates a 'tunnel ID'.
>
>
>I would advise against using the tunneling
>as defined in the rfc2107 for the purpose
>of circuit emulation over IP on the following counts:

I was not suggesting that you use 2107 as is because it doesn't do
what you want, just like L2TP doesn't do what you want either.

What I was trying to show is that there are ways to add a signaling
mechanism to GRE. 2107 is just an example. It is not the solution to
all problems, just like L2TP isn't either. And yes, it has some
limitations, just like any other protocol does.

Regarding the status of the "Key" field, I suggest you read
draft-dommety-gre-ext-04.txt. If you want to hear more about the
status of GRE, you can subscribe to the gre mailing list at
majordomo@psg.com.



From owner-l2tp@diameter.org  Fri Jul 28 05:56:50 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA24754
	for <l2tpext-archive@odin.ietf.org>; Fri, 28 Jul 2000 05:56:49 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e6S5hMA16276
	for l2tp-list; Thu, 27 Jul 2000 22:43:22 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e6S5hKd16270
	for <l2tp@l2tp.net>; Thu, 27 Jul 2000 22:43:20 -0700
Received: from amberex01.ambernetworks.com (207-33-177-98.ncal.verio.com [207.33.177.98] (may be forged)) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id WAA14225 for <l2tp@ipsec.org>; Thu, 27 Jul 2000 22:47:02 -0700 (PDT)
Received: by amberex01.ambernetworks.com with Internet Mail Service (5.5.2650.21)
	id <P4JA2GHJ>; Thu, 27 Jul 2000 22:49:53 -0700
Message-ID: <50B17D03735BD411B2D000D0B7237DED0B108E@amberex01.ambernetworks.com>
From: Andy Koscinski <ANDYK@ambernetworks.com>
To: Ignacio Goyret <igoyret@lucent.com>
Cc: Danny McPherson <Danny@ambernetworks.com>,
        "'l2tp@ipsec.org'"
	 <l2tp@ipsec.org>,
        Andy Koscinski <ANDYK@ambernetworks.com>
Subject: RE: L2TP charter
Date: Thu, 27 Jul 2000 22:49:45 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-l2tp@diameter.org
Precedence: bulk


> -----Original Message-----
> From: Ignacio Goyret [mailto:igoyret@lucent.com]
> Sent: Thursday, July 27, 2000 9:45 PM
> To: Andy Koscinski
> Cc: Ignacio Goyret; Danny McPherson; 'l2tp@ipsec.org'
> Subject: RE: L2TP charter
> 
> 
> At 09:24 PM 7/27/00 -0700, Andy Koscinski wrote:
> >> >
> >> >GRE provides only an encapsulation scheme, it provides no 
> >> >end-to-end signaling mechanism.
> >> >
> >> >GRE does not generate a Tunnel ID, which can be used to 
> >> >assist with processing tunnel payload in hardware.
> >> 
> >> Read rfc2107 for a solution that implements a signaling mechanism
> >> for GRE that negotiates a 'tunnel ID'.
> >
> >
> >I would advise against using the tunneling
> >as defined in the rfc2107 for the purpose
> >of circuit emulation over IP on the following counts:
> 
> I was not suggesting that you use 2107 as is because it doesn't do
> what you want, just like L2TP doesn't do what you want either.

andyk> but L2TP is very close to support circuit emulation over IP,
much closer than GRE, on the follwing counts:

1. GRE rfc2784 does not specify any end to end signaling
for tunnels or sessions
2. The key field (tunnel id) has been removed in the text of 
the rfc2784 in 3/2000, I quote:
"the GRE header will never contain the
 Key, Sequence Number or Routing fields specified in RFC 1701."

> 
> What I was trying to show is that there are ways to add a signaling
> mechanism to GRE. 2107 is just an example. 

andyk>L2TP rfc 2661 is in my opinion a better example of signaling 
to follow, as suggested by the "informational"
and temporary rfc2107 itself ("There is ongoing effort in an IETF 
working group which could 
result in a standards track document which specifies a protocol 
which provides similar functionality.")

> Regarding the status of the "Key" field, I suggest you read
> draft-dommety-gre-ext-04.txt. 

andyk> I follow:

3. In 3/2000 there was a rfc 2784, removing the key field (with 
the tunnel id) "forever" (I refer to (2) above).

4. in 6/2000 there was the "draft-dommety-gre-ext-04.txt" asking
to re-introduce the key field again (sic!). This draft was submitted
at the same time (6/2000) the draft "draft-mcpherson-l2tp-es-01.txt",
(which is under discussion here) was submitted. How can you expect
the "draft-mcpherson-l2tp-es-01.txt" take an example from a not
yet published "draft-dommety-gre-ext-04.txt", rather than from
rfc 2661?

Regards,

andyk@ambernetworks.com




From owner-l2tp@diameter.org  Fri Jul 28 09:52:56 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA22478
	for <l2tpext-archive@odin.ietf.org>; Fri, 28 Jul 2000 09:52:56 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e6SAge816423
	for l2tp-list; Fri, 28 Jul 2000 03:42:40 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e6SAgUd16417
	for <l2tp@l2tp.net>; Fri, 28 Jul 2000 03:42:30 -0700
Received: from hygro.adsl.duke.edu (root@hygro.adsl.duke.edu [152.16.64.159]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id DAA15733 for <l2tp@ipsec.org>; Fri, 28 Jul 2000 03:46:14 -0700 (PDT)
Received: from hygro.adsl.duke.edu (IDENT:narten@localhost.localdomain [127.0.0.1])
	by hygro.adsl.duke.edu (8.9.3/8.9.3) with ESMTP id GAA01151;
	Fri, 28 Jul 2000 06:45:49 -0400
Message-Id: <200007281045.GAA01151@hygro.adsl.duke.edu>
To: Andy Koscinski <ANDYK@ambernetworks.com>
cc: Ignacio Goyret <igoyret@lucent.com>,
        Danny McPherson <Danny@ambernetworks.com>,
        "'l2tp@ipsec.org'" <l2tp@ipsec.org>
Subject: Re: L2TP charter 
In-Reply-To: Message from Andy Koscinski <ANDYK@ambernetworks.com> 
   of "Thu, 27 Jul 2000 21:24:29 PDT." <50B17D03735BD411B2D000D0B7237DED0B1082@amberex01.ambernetworks.com> 
Date: Fri, 28 Jul 2000 06:45:49 -0400
From: Thomas Narten <narten@raleigh.ibm.com>
Sender: owner-l2tp@diameter.org
Precedence: bulk

> 1. the "tunnel id" is not supported by the GRE any more:
> The tunnel id was carried in the "key" field of the GRE tunnel packets
> as defined in the RFC1701 (10/1994). The "key" field has been removed
> from the newest GRE RFC2784 (3/2000), quote from RFC2784:
> "the GRE header will never contain the Key, Sequence Number or Routing 
> fields specified in RFC 1701".

See draft-dommety-gre-ext-04.txt, "Key and Sequence Number Extensions
to GRE". That document has been approved by the IESG as a Proposed
Standard and is in the RFC Editor's publication queue.

Thomas


From owner-l2tp@diameter.org  Fri Jul 28 19:52:27 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA26442
	for <l2tpext-archive@odin.ietf.org>; Fri, 28 Jul 2000 19:52:26 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e6SKwAg17010
	for l2tp-list; Fri, 28 Jul 2000 13:58:10 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e6SKw7d17004
	for <l2tp@l2tp.net>; Fri, 28 Jul 2000 13:58:07 -0700
Received: from h006008986325.ne.mediaone.net (h006008986325.ne.mediaone.net [24.218.16.153]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id OAA16348 for <l2tp@ipsec.org>; Fri, 28 Jul 2000 14:01:52 -0700 (PDT)
Received: (from carlson@localhost)
	by h006008986325.ne.mediaone.net (8.9.3/8.9.3) id RAA21176;
	Fri, 28 Jul 2000 17:01:36 -0400
From: James Carlson <carlson@workingcode.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <14721.62639.611485.330296@h006008986325.ne.mediaone.net>
Date: Fri, 28 Jul 2000 17:01:35 -0400 (EDT)
To: Danny McPherson <Danny@ambernetworks.com>
Cc: "'l2tp@ipsec.org'" <l2tp@ipsec.org>
Subject: Re: L2TP charter
In-Reply-To: Danny McPherson's message of 27 July 2000 16:41:03
References: <50B17D03735BD411B2D000D0B7237DED36B438@amberex01.ambernetworks.com>
X-Mailer: VM 6.75 under Emacs 20.6.1
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

Danny McPherson writes:
> For starters, if you're of the opinion that GRE is 
> sufficient, perhaps reflecting on the initial justification 
> of L2TP itself would be of benefit?  That is, why were PPP 
> PDUs not tunneled through GRE?  The same advantages L2TP 
> brought to PPP can be realized with non-PPP payloads as well,
> with little work.

L2TP was done because two other proprietary mechanisms -- L2F and PPTP
-- were getting market attention.  Yes, PPP over plain GRE is quite
feasible.  One thing addressed by L2TP is that you bring the PPP
session half-way up, and it's commonly believed that you need some
non-PPP way to transfer the negotiated parameters to the peer.

Of course, that's not quite true.  We could have defined proxy
operations such that they'd work without the L2TP mechanisms.  That's
not what was done.

In the case of putting other protocols over L2TP, especially
protocols above layer two, it's much harder to make the argument that
L2TP provides any noticable benefit.  Would you, say, start doing X.25
call control, stop halfway through, and then tunnel the call control
over the Internet?  If so, then L2TP almost makes sense.  Otherwise, I
don't see how it helps this particular application in any way.

> MPLS doesn't provide an end-to-end signaling mechanism.

RSVP and CR-LDP, q.v.

> -*Why not do it over PPP?
> 
> PPP doesn't provide sufficient parameter capabilities to 
> support circuit emulation services (e.g. negotiation of 
> specific frame relay or ATM parameters).  As a result, 
> another protocol has to be developed.

PPP does indeed negotiate L3 capabilities.  That's the whole point of
PPP.  If you really do need a new L3, this can be added to PPP.  (Of
course, once you do, I'll argue that running MPLS over PPP and CES
over that is better still, since you can take advantage of MPLS's
signaling capabilities.)

Doing it in PPP means that you'll automatically run over everything
else as well, without requiring L2TP.  For instance, it would be handy
to be able to run CES over PPP over SONET.  Interposing L2TP adds
*quite* a lot of overhead, even if you remove PPP.

>  With both, an 
> unnecessary, unclean overlap in function occurs.  This 
> quickly became obvious when we were implementing it.

Sorry, don't see it.

> Also, requiring PPP to use L2TP simply isn't clean 
> architecturally.

That doesn't make sense.  L2TP was explicitly designed for PPP.

> In addition, unnecessary PPP overhead results.  Overhead from
> PPP negotiation, it's state machine, and network overhead from
> header bytes.

Again, you're complaining about another 1 to 4 octets of PPP overhead
versus 36 or more for L2TP.  Removing the former helps only a little
and hurts a lot.  Removing the latter helps quite a bit more.

Another way to look at it is that putting this in L2TP solves only a
few vendors' problems.  Putting it in PPP solves more.

> -*Other issues?
> 
> L2TP provides for ease of implementation in hardware as the 
> switching can be done based on Tunnel and Session ID.

Variable-length headers -- such as the GRE header used for L2TP -- are
a pain in hardware.  I know of few high-speed implementations.

> Current proposal is completely inter-operable with existing 
> implementations as they can reject Service Type AVP.

Same is true for PPP.

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


From owner-l2tp@diameter.org  Fri Jul 28 20:47:11 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA08536
	for <l2tpext-archive@odin.ietf.org>; Fri, 28 Jul 2000 20:47:11 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e6SLvSF17038
	for l2tp-list; Fri, 28 Jul 2000 14:57:28 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e6SLvGd17032
	for <l2tp@l2tp.net>; Fri, 28 Jul 2000 14:57:16 -0700
Received: from amberex01.ambernetworks.com (207-33-177-98.ncal.verio.com [207.33.177.98] (may be forged)) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id PAA16384 for <l2tp@ipsec.org>; Fri, 28 Jul 2000 15:01:02 -0700 (PDT)
Received: by amberex01.ambernetworks.com with Internet Mail Service (5.5.2650.21)
	id <P4JA2HTV>; Fri, 28 Jul 2000 15:03:54 -0700
Message-ID: <50B17D03735BD411B2D000D0B7237DED36B455@amberex01.ambernetworks.com>
From: Danny McPherson <Danny@ambernetworks.com>
To: "'l2tp@ipsec.org'" <l2tp@ipsec.org>
Subject: RE: L2TP charter
Date: Fri, 28 Jul 2000 15:03:49 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-l2tp@diameter.org
Precedence: bulk


> In the case of putting other protocols over L2TP, especially
> protocols above layer two, it's much harder to make the argument that
> L2TP provides any noticable benefit.  Would you, say, start doing X.25
> call control, stop halfway through, and then tunnel the call control
> over the Internet?  If so, then L2TP almost makes sense.  Otherwise, I
> don't see how it helps this particular application in any way.

Perhaps the benefits will become clear when we post the referenced ESP
draft.

> > MPLS doesn't provide an end-to-end signaling mechanism.
> 
> RSVP and CR-LDP, q.v.

However, both are still orthogonal of MPLS.

> PPP does indeed negotiate L3 capabilities.  That's the whole point of
> PPP.  If you really do need a new L3, this can be added to PPP.  (Of
> course, once you do, I'll argue that running MPLS over PPP and CES
> over that is better still, since you can take advantage of Myles's
> signaling capabilities.)

As for your arguing, I'm sure you will.  Though I'm more concerned with
reality and service provider requirements :-)

> Doing it in PPP means that you'll automatically run over everything
> else as well, without requiring L2TP.  For instance, it would be handy
> to be able to run CES over PPP over SONET.  Interposing L2TP adds
> *quite* a lot of overhead, even if you remove PPP.

Though you've omitted the most obvious benefit of L2TP here -- it's IP
tunneling capabilities.  Something that clearly can't be provided in the
scenario you describe.  

> Again, you're complaining about another 1 to 4 octets of PPP overhead
> versus 36 or more for L2TP.  Removing the former helps only a little
> and hurts a lot.  Removing the latter helps quite a bit more.

Though this is in addition to the state machine and other issues.

> Variable-length headers -- such as the GRE header used for L2TP -- are
> a pain in hardware.  I know of few high-speed implementations.

Simply because you know if few implementations is no indication that they
don't exist.

> Same is true for PPP.

Hopefully, the ESP draft will make things clearer.  If not, I'm sure we'll
continue the discussion.

-danny


From owner-l2tp@diameter.org  Fri Jul 28 23:39:58 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA13131
	for <l2tpext-archive@odin.ietf.org>; Fri, 28 Jul 2000 23:39:58 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e6T0Kef17100
	for l2tp-list; Fri, 28 Jul 2000 17:20:40 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from sj-msg-core-1.cisco.com (sj-msg-core-1.cisco.com [171.71.163.11])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e6T0Kbd17094
	for <l2tp@l2tp.net>; Fri, 28 Jul 2000 17:20:37 -0700
Received: from townsley-ultra.cisco.com (townsley-ultra.cisco.com [161.44.58.38])
	by sj-msg-core-1.cisco.com (8.9.3/8.9.1) with ESMTP id RAA22159
	for <l2tp@l2tp.net>; Fri, 28 Jul 2000 17:24:34 -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 UAA09870 for <l2tp@l2tp.net>; Fri, 28 Jul 2000 20:24:18 -0400 (EDT)
Message-ID: <3982241F.A8323CC7@cisco.com>
Date: Fri, 28 Jul 2000 20:23:59 -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: l2tp@l2tp.net
Subject: [Fwd: l2tpext agenda items]
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit


We are scheduled to meet Wednesday, August 2, 2000, 1530-1730 in PA
Here is the agenda:

W. Mark Townsley
Agenda Bashing
5 min

Anita Freeman
VPN Bakeoff Announcement
5 min

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

Bernard Aboba 
draft-ietf-l2tpext-l2tp-security-01.txt
20 min

Ravi Bhat, Danny Mcpherson
draft-mcpherson-l2tp-es-01.txt
20 min

Suhail Nanji
draft-nanji-l2tp-eth-00.txt
15 min

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

W. Mark Townsley
draft-ietf-l2tpext-l2tpbis-00.txt
WG Draft Status
 draft-ietf-l2tpext-l2tp-mib-00.txt
 draft-ietf-l2tpext-l2tphc-02.txt
 draft-ietf-l2tpext-atmext-03.txt
 draft-ietf-l2tpext-sesinfo-01.txt
 linkinfo? adc? ds? mpls?
l2tpext Charter 
Goals and Milestones
30 min


From owner-l2tp@diameter.org  Fri Jul 28 23:43:01 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA13482
	for <l2tpext-archive@odin.ietf.org>; Fri, 28 Jul 2000 23:43:00 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e6T0sPR17120
	for l2tp-list; Fri, 28 Jul 2000 17:54:25 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e6T0sNd17114
	for <l2tp@l2tp.net>; Fri, 28 Jul 2000 17:54:23 -0700
Received: from amberex01.ambernetworks.com (207-33-177-98.ncal.verio.com [207.33.177.98] (may be forged)) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id RAA16544 for <l2tp@ipsec.org>; Fri, 28 Jul 2000 17:58:08 -0700 (PDT)
Received: by amberex01.ambernetworks.com with Internet Mail Service (5.5.2650.21)
	id <P4JA2218>; Fri, 28 Jul 2000 18:01:01 -0700
Message-ID: <50B17D03735BD411B2D000D0B7237DED0B10C9@amberex01.ambernetworks.com>
From: Andy Koscinski <ANDYK@ambernetworks.com>
To: Thomas Narten <narten@raleigh.ibm.com>
Cc: "'l2tp@ipsec.org'" <l2tp@ipsec.org>
Subject: RE: L2TP charter 
Date: Fri, 28 Jul 2000 18:00:57 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-l2tp@diameter.org
Precedence: bulk



> -----Original Message-----
> From: Thomas Narten [mailto:narten@raleigh.ibm.com]
> Sent: Friday, July 28, 2000 3:46 AM
> To: Andy Koscinski
> Cc: Ignacio Goyret; Danny McPherson; 'l2tp@ipsec.org'
> Subject: Re: L2TP charter 
> 
> 
> > 1. the "tunnel id" is not supported by the GRE any more:
> > The tunnel id was carried in the "key" field of the GRE 
> tunnel packets
> > as defined in the RFC1701 (10/1994). The "key" field has 
> been removed
> > from the newest GRE RFC2784 (3/2000), quote from RFC2784:
> > "the GRE header will never contain the Key, Sequence Number 
> or Routing 
> > fields specified in RFC 1701".
> 
> See draft-dommety-gre-ext-04.txt, "Key and Sequence Number Extensions
> to GRE". That document has been approved by the IESG as a Proposed
> Standard and is in the RFC Editor's publication queue.
> 
> Thomas
>

1. In 3/2000 there was a rfc 2784, removing the key field (with 
the tunnel id) "forever", I quote: "the GRE header will never 
contain the Key, Sequence Number or Routing fields specified in RFC 1701."

2. in 6/2000 there was the "draft-dommety-gre-ext-04.txt" asking
to re-introduce the key field again. 

Could you please help understand why such frequent changes?

Regards,

andyk@ambernetworks.com 


From owner-l2tp@diameter.org  Sat Jul 29 12:05:24 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00208
	for <l2tpext-archive@odin.ietf.org>; Sat, 29 Jul 2000 12:05:23 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e6TBf6o17594
	for l2tp-list; Sat, 29 Jul 2000 04:41:06 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e6TBf1d17588
	for <l2tp@l2tp.net>; Sat, 29 Jul 2000 04:41:02 -0700
Received: from franklin.cisco.com (franklin.cisco.com [171.70.156.17]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id EAA18323 for <l2tp@ipsec.org>; Sat, 29 Jul 2000 04:44:48 -0700 (PDT)
Received: from gwz (sj-dial-4-62.cisco.com [171.68.181.191]) by franklin.cisco.com (8.8.6 (PHNE_17190)/CISCO.SERVER.1.2) with SMTP id EAA14996; Sat, 29 Jul 2000 04:43:36 -0700 (PDT)
Reply-To: <gwz@cisco.com>
From: "Glen Zorn" <gwz@cisco.com>
To: "James Carlson" <carlson@workingcode.com>,
        "Danny McPherson" <Danny@ambernetworks.com>
Cc: <l2tp@ipsec.org>
Subject: RE: L2TP charter
Date: Sat, 29 Jul 2000 04:41:07 -0700
Message-ID: <NDBBIHMPILAAGDHPCIOPKEHOCJAA.gwz@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <14721.62639.611485.330296@h006008986325.ne.mediaone.net>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
Importance: Normal
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit

James Carlson [mailto://carlson@workingcode.com] writes:

> Danny McPherson writes:
> > For starters, if you're of the opinion that GRE is
> > sufficient, perhaps reflecting on the initial justification
> > of L2TP itself would be of benefit?  That is, why were PPP
> > PDUs not tunneled through GRE?  The same advantages L2TP
> > brought to PPP can be realized with non-PPP payloads as well,
> > with little work.
>
> L2TP was done because two other proprietary mechanisms -- L2F and PPTP
> -- were getting market attention.

Iteresting statement.  What, then, begat L2F & PPTP?  Given that cisco is
the veritable Land of GRE and PPTP uses essentially the straight GRE header,
it could hardly haave been simple distaste for the protocol.  Could it be
that vanilla GRE just didn't fulfill the requirements?

> Yes, PPP over plain GRE is quite
> feasible.  One thing addressed by L2TP is that you bring the PPP
> session half-way up, and it's commonly believed that you need some
> non-PPP way to transfer the negotiated parameters to the peer.
>
> Of course, that's not quite true.  We could have defined proxy
> operations such that they'd work without the L2TP mechanisms.  That's
> not what was done.

<text deleted>



From owner-l2tp@diameter.org  Sat Jul 29 18:12:06 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26023
	for <l2tpext-archive@odin.ietf.org>; Sat, 29 Jul 2000 18:12:05 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e6TI3lo17733
	for l2tp-list; Sat, 29 Jul 2000 11:03:47 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e6TI3id17724
	for <l2tp@l2tp.net>; Sat, 29 Jul 2000 11:03:44 -0700
Received: from altavistausa.com (max1-3.newyork.corecomm.net [209.81.238.131]) by ns1.sailpix.com (8.8.8/8.6.9) with SMTP id LAA18567; Sat, 29 Jul 2000 11:07:30 -0700 (PDT)
From: <callback123@altavistausa.com>
Subject: Re: From Lorraine,as promised,I can lower your???
Date: Sat, 29 Jul 2000 15:03:53
Message-Id: <53.848596.460141@altavistausa.com>
Mime-Version: 1.0
Content-Type: text/html; charset="us-ascii"
Sender: owner-l2tp@diameter.org
Precedence: bulk


<html>

<head>
<title>Untitled Document</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</head>

<body bgcolor="#FFFFFF">
<div align="center">

<p><a href="http://members.hometown.aol.com/_ht_a/hellotel88/myhomepage/lowrates"><img
src="http://members.hometown.aol.com/_ht_a/hellotel88/myhomepage/lowrates/telephone.gif"
width="250" height="203" border="0"></a> <br>
Today, everyone knows the impact of the Internet.<br>
But not everyone nows how to cut their phone bill in 1/2. Just a Few examples!!!!</p>

<p>Uk $.04&nbsp;&nbsp;&nbsp;&nbsp; France $.06&nbsp;&nbsp;&nbsp; UAE&nbsp; $.31
&nbsp;&nbsp; Saudi Arabia $.59&nbsp;&nbsp;&nbsp;&nbsp; Denmark $.04
&nbsp;&nbsp;&nbsp;&nbsp; Sweden $.05</p>

<p><a href="http://members.hometown.aol.com/_ht_a/hellotel88/myhomepage/lowrates"><font
size="4">Click Here Now. </font></a></p>

<p>If you do not have flash please go to<br>
<a href="http://www.macromedia.com">www.macromedia.com</a><br>
to download it.</p>
</div>
</body>
</html>


From owner-l2tp@diameter.org  Sun Jul 30 15:03:22 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18663
	for <l2tpext-archive@odin.ietf.org>; Sun, 30 Jul 2000 15:03:21 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e6UFpFs23680
	for l2tp-list; Sun, 30 Jul 2000 08:51:15 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from zendo.com (bodhi.zendo.com [205.187.71.2])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e6UFpCd23674
	for <l2tp@l2tp.net>; Sun, 30 Jul 2000 08:51:12 -0700
Received: from vandys-pc.zendo.com (dialup-63.214.8.48.Seattle1.Level3.net [63.214.8.48])
	by zendo.com (8.10.1/8.10.1) with ESMTP id e6U7iaB12671
	for <l2tp@l2tp.net>; Sun, 30 Jul 2000 07:44:37 GMT
Received: from vandys-pc.zendo.com (localhost.zendo.com [127.0.0.1])
	by vandys-pc.zendo.com (8.9.1/8.9.1) with ESMTP id IAA00300
	for <l2tp@l2tp.net>; Sun, 30 Jul 2000 08:53:06 -0700 (PDT)
	(envelope-from vandys@vandys-pc.zendo.com)
Message-Id: <200007301553.IAA00300@vandys-pc.zendo.com>
To: l2tp@l2tp.net
Subject: Re: L2TP charter
Date: Sun, 30 Jul 2000 08:53:05 -0700
From: Andy Valencia <vandys@zendo.com>
Sender: owner-l2tp@diameter.org
Precedence: bulk

Glen Zorn (gwz@cisco.com) writes:

>> L2TP was done because two other proprietary mechanisms -- L2F and PPTP
>> -- were getting market attention.
>Interesting statement. What, then, begat L2F & PPTP? Given that cisco is the
>veritable Land of GRE and PPTP uses essentially the straight GRE header, it
>could hardly haave been simple distaste for the protocol.  Could it be
>that vanilla GRE just didn't fulfill the requirements?

The original protocol spec which became L2F was indeed PPP over GRE.  We
decided to deviate from GRE because there were some pretty major changes
(dynamic tunnels, and a bunch of signalling for instance) which didn't seem
appropriate to paste on top of a stable protocol which was already doing
what it was designed to do.  We also looked at doing PPP-over-PPP, with L2F
being a new NCP.  But again, things we wanted to do (running multiple
sessions over one tunnel) were pretty dissimilar to what PPP was designed to
support.

So if we "stayed with" GRE, but mutated it (perhaps dramatically), would we
be ahead of the game as compared to making Yet Another Tunneling Protocol?
Obviously, we thought not.  And if I were doing it over again, I still would
choose to leave GRE alone, rather than force a bunch of complexity onto a
nice, simple tunneling mechanism.

Andy Valencia
vandys@zendo.com


From owner-l2tp@diameter.org  Mon Jul 31 05:17:25 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA20091
	for <l2tpext-archive@odin.ietf.org>; Mon, 31 Jul 2000 05:17:25 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e6V4JtR23938
	for l2tp-list; Sun, 30 Jul 2000 21:19:55 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from tcb.net (tcb.net [205.168.100.1])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e6V4Jqd23932
	for <l2tp@l2tp.net>; Sun, 30 Jul 2000 21:19:52 -0700
Received: from sofos.tcb.net (sofos.tcb.net [127.0.0.1])
	by tcb.net (8.9.3/8.9.3) with ESMTP id WAA11284
	for <l2tp@l2tp.net>; Sun, 30 Jul 2000 22:24:37 -0600
Message-Id: <200007310424.WAA11284@tcb.net>
To: l2tp@l2tp.net
From: Danny McPherson <danny@tcb.net>
Reply-To: danny@tcb.net
Subject: Re: [Fwd: l2tpext agenda items] 
Date: Sun, 30 Jul 2000 22:24:37 -0600
Sender: owner-l2tp@diameter.org
Precedence: bulk


Is any work being done on draft-ietf-l2tpext-ds-00.txt?  I didn't
see much discussion in the archives and it's not on the agenda.

Thanks!

-danny

> WG Draft Status
>  ...ds?...



From owner-l2tp@diameter.org  Mon Jul 31 11:48:44 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27754
	for <l2tpext-archive@odin.ietf.org>; Mon, 31 Jul 2000 11:48:43 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e6VC6Lv24306
	for l2tp-list; Mon, 31 Jul 2000 05:06:21 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from shako.cisco.com (shako.cisco.com [161.44.3.76])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e6VC6Cd24300
	for <l2tp@l2tp.net>; Mon, 31 Jul 2000 05:06:12 -0700
Received: from cisco.com (rtp-dial-1-27.cisco.com [10.83.97.27])
	by shako.cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id IAA04040;
	Mon, 31 Jul 2000 08:09:10 -0400 (EDT)
Message-ID: <39856C7C.268B31B2@cisco.com>
Date: Mon, 31 Jul 2000 08:09:32 -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: danny@tcb.net
CC: l2tp@l2tp.net
Subject: Re: [Fwd: l2tpext agenda items]
References: <200007310424.WAA11284@tcb.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-l2tp@diameter.org
Precedence: bulk
Content-Transfer-Encoding: 7bit



Danny McPherson wrote:
> 
> Is any work being done on draft-ietf-l2tpext-ds-00.txt?  I didn't
> see much discussion in the archives and it's not on the agenda.

Ken Peirce has indicated to me offline that he plans to resubmit the ds
spec. The mpls spec is dead.

> 
> Thanks!
> 
> -danny
> 
> > WG Draft Status
> >  ...ds?...


From owner-l2tp@diameter.org  Mon Jul 31 15:30:58 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00729
	for <l2tpext-archive@odin.ietf.org>; Mon, 31 Jul 2000 15:30:58 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e6VG0Bk24470
	for l2tp-list; Mon, 31 Jul 2000 09:00:11 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from notes308.nerausa.com (crtntx1-ar4-003-061.biz.dsl.gtei.net [4.35.3.61])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e6VG08d24464
	for <l2tp@l2tp.net>; Mon, 31 Jul 2000 09:00:08 -0700
Subject: Compulsory Tunnelling on Cisco/Windows
To: l2tp@l2tp.net
X-Mailer: Lotus Notes Release 5.0.2a (Intl) 23 November 1999
Message-ID: <OF217F3FAC.7048DF3D-ON0525692D.00580529@nerausa.com>
From: kbourg@nerausa.com
Date: Mon, 31 Jul 2000 11:08:01 -0500
X-MIMETrack: Serialize by Router on NOTES308/USTEL/NERA(Release 5.0.2a (Intl)|23 November 1999) at 07/31/2000 11:07:36 AM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Sender: owner-l2tp@diameter.org
Precedence: bulk

Greetings,

I would like to know how to set up a Cisco 2620 (IOS 11.3 ) and a Win 2K
box for "static compulsory" tunnelling.  I currently have the capability of
establishing a tunnel between our system (LAC) and each of the above
platforms (LNS), as well as the capability of starting sessions and moving
along the way through session establishment, etc.  However, upon
termination of the last session on the tunnel, the LNS (Win 2K and Cisco)
terminates the tunnel connection.  The next time we attempt to establish a
session, the tunnel does not exist and this leads to some problems within
our software (not that we cannot overcome them, it would just be a little
difficult).  Is it possible to configure either/both of the above boxes
such that the tunnel is not terminated by the LNS upon termination of the
last session and leave the tunnel in existence?  I cannot find these
configuration items.

Thanks,

Kevin

BTW, I am having trouble accessing the Archive List at l2tp@l2tp.net.  The
connection is timing out.



From owner-l2tp@diameter.org  Mon Jul 31 19:28:08 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06801
	for <l2tpext-archive@odin.ietf.org>; Mon, 31 Jul 2000 19:28:08 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e6VJpO024763
	for l2tp-list; Mon, 31 Jul 2000 12:51:24 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from ans2-pub.dttus.com (ans2-pub.dttus.com [204.151.11.3])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e6VJpLd24757
	for <l2tp@l2tp.net>; Mon, 31 Jul 2000 12:51:21 -0700
Received: by ans2-pub.dttus.com id OAA21151
  (InterLock SMTP Gateway 3.0 for l2tp@l2tp.net);
  Mon, 31 Jul 2000 14:55:04 -0500 (CDT)
Received: by ans2-pub.dttus.com (Internal Mail Agent-2);
  Mon, 31 Jul 2000 14:55:04 -0500 (CDT)
Received: by ans2-pub.dttus.com (Internal Mail Agent-1);
  Mon, 31 Jul 2000 14:55:04 -0500 (CDT)
Message-Id: <2F4A3F6B7BF5D3119E2500508B94E65601F5A4AC@uscntnt405.us.deloitte.com>
From: "Verma, Rohit (US - Chicago)" <rverma@dc.com>
To: kbourg@nerausa.com, l2tp@l2tp.net
Subject: RE: Compulsory Tunnelling on Cisco/Windows
Date: Mon, 31 Jul 2000 14:51:33 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01BFFB28.BA5AA6F0"
Sender: owner-l2tp@diameter.org
Precedence: bulk

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

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

I just tried www.l2tp.net and it works fine.

Regards

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


-----Original Message-----
From: kbourg@nerausa.com [mailto:kbourg@nerausa.com]
Sent: Monday, July 31, 2000 12:08 PM
To: l2tp@l2tp.net
Subject: Compulsory Tunnelling on Cisco/Windows


Greetings,

I would like to know how to set up a Cisco 2620 (IOS 11.3 ) and a Win 2K
box for "static compulsory" tunnelling.  I currently have the capability of
establishing a tunnel between our system (LAC) and each of the above
platforms (LNS), as well as the capability of starting sessions and moving
along the way through session establishment, etc.  However, upon
termination of the last session on the tunnel, the LNS (Win 2K and Cisco)
terminates the tunnel connection.  The next time we attempt to establish a
session, the tunnel does not exist and this leads to some problems within
our software (not that we cannot overcome them, it would just be a little
difficult).  Is it possible to configure either/both of the above boxes
such that the tunnel is not terminated by the LNS upon termination of the
last session and leave the tunnel in existence?  I cannot find these
configuration items.

Thanks,

Kevin

BTW, I am having trouble accessing the Archive List at l2tp@l2tp.net.  The
connection is timing out.

------_=_NextPart_001_01BFFB28.BA5AA6F0
Content-Type: text/html;
	charset="iso-8859-1"

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

<P><FONT SIZE=2>I just tried www.l2tp.net and it works fine.</FONT>
</P>

<P><FONT SIZE=2>Regards</FONT>
</P>

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

<P><FONT SIZE=2>-----Original Message-----</FONT>
<BR><FONT SIZE=2>From: kbourg@nerausa.com [<A HREF="mailto:kbourg@nerausa.com">mailto:kbourg@nerausa.com</A>]</FONT>
<BR><FONT SIZE=2>Sent: Monday, July 31, 2000 12:08 PM</FONT>
<BR><FONT SIZE=2>To: l2tp@l2tp.net</FONT>
<BR><FONT SIZE=2>Subject: Compulsory Tunnelling on Cisco/Windows</FONT>
</P>
<BR>

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

<P><FONT SIZE=2>I would like to know how to set up a Cisco 2620 (IOS 11.3 ) and a Win 2K</FONT>
<BR><FONT SIZE=2>box for &quot;static compulsory&quot; tunnelling.&nbsp; I currently have the capability of</FONT>
<BR><FONT SIZE=2>establishing a tunnel between our system (LAC) and each of the above</FONT>
<BR><FONT SIZE=2>platforms (LNS), as well as the capability of starting sessions and moving</FONT>
<BR><FONT SIZE=2>along the way through session establishment, etc.&nbsp; However, upon</FONT>
<BR><FONT SIZE=2>termination of the last session on the tunnel, the LNS (Win 2K and Cisco)</FONT>
<BR><FONT SIZE=2>terminates the tunnel connection.&nbsp; The next time we attempt to establish a</FONT>
<BR><FONT SIZE=2>session, the tunnel does not exist and this leads to some problems within</FONT>
<BR><FONT SIZE=2>our software (not that we cannot overcome them, it would just be a little</FONT>
<BR><FONT SIZE=2>difficult).&nbsp; Is it possible to configure either/both of the above boxes</FONT>
<BR><FONT SIZE=2>such that the tunnel is not terminated by the LNS upon termination of the</FONT>
<BR><FONT SIZE=2>last session and leave the tunnel in existence?&nbsp; I cannot find these</FONT>
<BR><FONT SIZE=2>configuration items.</FONT>
</P>

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

<P><FONT SIZE=2>Kevin</FONT>
</P>

<P><FONT SIZE=2>BTW, I am having trouble accessing the Archive List at l2tp@l2tp.net.&nbsp; The</FONT>
<BR><FONT SIZE=2>connection is timing out.</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01BFFB28.BA5AA6F0--


From owner-l2tp@diameter.org  Mon Jul 31 20:51:23 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA19467
	for <l2tpext-archive@odin.ietf.org>; Mon, 31 Jul 2000 20:51:22 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e6VKk5324843
	for l2tp-list; Mon, 31 Jul 2000 13:46:05 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from dfssl.exchange.microsoft.com (dfssl.exchange.microsoft.com [131.107.88.59])
	by charizard.diameter.org (8.10.0/8.10.0) with SMTP id e6VKk2d24837
	for <l2tp@l2tp.net>; Mon, 31 Jul 2000 13:46:02 -0700
Received: from 172.30.236.11 by dfssl.exchange.microsoft.com (InterScan E-Mail VirusWall NT); Mon, 31 Jul 2000 13:34:56 -0700 (Pacific Daylight Time)
Received: from fifi.platinum.corp.microsoft.com ([172.30.236.94]) by yuri.dns.microsoft.com with Microsoft SMTPSVC(5.0.2195.2023);
	 Mon, 31 Jul 2000 13:42:59 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.0.4415.0
content-class: urn:content-classes:message
Subject: RE: Compulsory Tunnelling on Cisco/Windows
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01BFFB2F.BCCA25E4"
Date: Mon, 31 Jul 2000 13:41:43 -0700
Message-ID: <6A05D00595BE644E9F435BE5947423F2038CB510@fifi.platinum.corp.microsoft.com>
Thread-Topic: Compulsory Tunnelling on Cisco/Windows
Thread-Index: Ab/7Ckx+PyfiJBIlR1S+piP6i49GawAIzOeg
From: "William Dixon" <wdixon@Exchange.Microsoft.com>
To: <kbourg@nerausa.com>, <l2tp@l2tp.net>
X-OriginalArrivalTime: 31 Jul 2000 20:42:59.0096 (UTC) FILETIME=[E99B3180:01BFFB2F]
Sender: owner-l2tp@diameter.org
Precedence: bulk

This is a multi-part message in MIME format.

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

Kevin, if you read the L2TP/IPSec security draft,
draft-ietf-l2tp-security-00.txt, it specifically says that IPSec main
mode state should be deleted when the last tunnel session is terminated.
This is exactly so the LAC and LNS will interoperate.  If your LAC
doesn't clean up MM state and the LNS does when the L2TP tunnel
terminates, then you/LAC will initiate quick modes for the next L2TP
session (?) which the LNS doesn't understand.  Still, you/LAC should be
getting IKE delete payloads for the MM delete from the LNS - though as
we all know, they are not reliable (not ack'ed and using UDP) and could
leave lingering state on the LAC, thus the way the draft reads to be
sure both do the same thing. =20

For Win2k, it is possible to configure it so IPSec and L2TP are
independent, by not using the default integration between L2TP and
IPSec.  There is a KB article on support.microsoft.com to explain how to
use a pre-shared key in IKE for IPSec under L2TP - it describes the
registry key (rasman\"DisableIpsec=3D1" I think) to disable automatic
IPSec policy, so you can set any manual IPSec policy settings.  Thus
L2TP will not call to IPSec to delete the IKE state when the tunnel
terminates.  IKE MM & QM state will be independently maintained.
Microsoft does not support the use of manual IPSec policy (incl.
preshared key IKE auth) on the client, but will support it's use on the
server, primarily for gateway-to-gateway tunnel configurations (or yours
since the LAC is a form of gateway) and because the server admin is more
sophisticated and can handle manual IPSec policy config UI. Preshared
key hashes are more vulnerable to attack, so I hope you are using certs
anyway for IKE auth.

-----Original Message-----
From: kbourg@nerausa.com [mailto:kbourg@nerausa.com]
Sent: Monday, July 31, 2000 9:08 AM
To: l2tp@l2tp.net
Subject: Compulsory Tunnelling on Cisco/Windows


Greetings,

I would like to know how to set up a Cisco 2620 (IOS 11.3 ) and a Win 2K
box for "static compulsory" tunnelling.  I currently have the capability
of
establishing a tunnel between our system (LAC) and each of the above
platforms (LNS), as well as the capability of starting sessions and
moving
along the way through session establishment, etc.  However, upon
termination of the last session on the tunnel, the LNS (Win 2K and
Cisco)
terminates the tunnel connection.  The next time we attempt to establish
a
session, the tunnel does not exist and this leads to some problems
within
our software (not that we cannot overcome them, it would just be a
little
difficult).  Is it possible to configure either/both of the above boxes
such that the tunnel is not terminated by the LNS upon termination of
the
last session and leave the tunnel in existence?  I cannot find these
configuration items.

Thanks,

Kevin

BTW, I am having trouble accessing the Archive List at l2tp@l2tp.net.
The
connection is timing out.

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

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.4415.0">
<TITLE>RE: Compulsory Tunnelling on Cisco/Windows</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>Kevin, if you read the L2TP/IPSec security draft, =
draft-ietf-l2tp-security-00.txt, it specifically says that IPSec main =
mode state should be deleted when the last tunnel session is =
terminated.&nbsp; This is exactly so the LAC and LNS will =
interoperate.&nbsp; If your LAC doesn't clean up MM state and the LNS =
does when the L2TP tunnel terminates, then you/LAC will initiate quick =
modes for the next L2TP session (?) which the LNS doesn't =
understand.&nbsp; Still, you/LAC should be getting IKE delete payloads =
for the MM delete from the LNS - though as we all know, they are not =
reliable (not ack'ed and using UDP) and could leave lingering state on =
the LAC, thus the way the draft reads to be sure both do the same =
thing.&nbsp; </FONT></P>

<P><FONT SIZE=3D2>For Win2k, it is possible to configure it so IPSec and =
L2TP are independent, by not using the default integration between L2TP =
and IPSec.&nbsp; There is a KB article on support.microsoft.com to =
explain how to use a pre-shared key in IKE for IPSec under L2TP - it =
describes the registry key (rasman\&quot;DisableIpsec=3D1&quot; I think) =
to disable automatic IPSec policy, so you can set any manual IPSec =
policy settings.&nbsp; Thus L2TP will not call to IPSec to delete the =
IKE state when the tunnel terminates.&nbsp; IKE MM &amp; QM state will =
be independently maintained.&nbsp; Microsoft does not support the use of =
manual IPSec policy (incl. preshared key IKE auth) on the client, but =
will support it's use on the server, primarily for gateway-to-gateway =
tunnel configurations (or yours since the LAC is a form of gateway) and =
because the server admin is more sophisticated and can handle manual =
IPSec policy config UI. Preshared key hashes are more vulnerable to =
attack, so I hope you are using certs anyway for IKE auth.</FONT></P>

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

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

<BR><FONT SIZE=3D2>Sent: Monday, July 31, 2000 9:08 AM</FONT>

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

<BR><FONT SIZE=3D2>Subject: Compulsory Tunnelling on =
Cisco/Windows</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Greetings,</FONT>
</P>

<P><FONT SIZE=3D2>I would like to know how to set up a Cisco 2620 (IOS =
11.3 ) and a Win 2K</FONT>

<BR><FONT SIZE=3D2>box for &quot;static compulsory&quot; =
tunnelling.&nbsp; I currently have the capability of</FONT>

<BR><FONT SIZE=3D2>establishing a tunnel between our system (LAC) and =
each of the above</FONT>

<BR><FONT SIZE=3D2>platforms (LNS), as well as the capability of =
starting sessions and moving</FONT>

<BR><FONT SIZE=3D2>along the way through session establishment, =
etc.&nbsp; However, upon</FONT>

<BR><FONT SIZE=3D2>termination of the last session on the tunnel, the =
LNS (Win 2K and Cisco)</FONT>

<BR><FONT SIZE=3D2>terminates the tunnel connection.&nbsp; The next time =
we attempt to establish a</FONT>

<BR><FONT SIZE=3D2>session, the tunnel does not exist and this leads to =
some problems within</FONT>

<BR><FONT SIZE=3D2>our software (not that we cannot overcome them, it =
would just be a little</FONT>

<BR><FONT SIZE=3D2>difficult).&nbsp; Is it possible to configure =
either/both of the above boxes</FONT>

<BR><FONT SIZE=3D2>such that the tunnel is not terminated by the LNS =
upon termination of the</FONT>

<BR><FONT SIZE=3D2>last session and leave the tunnel in existence?&nbsp; =
I cannot find these</FONT>

<BR><FONT SIZE=3D2>configuration items.</FONT>
</P>

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

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

<P><FONT SIZE=3D2>BTW, I am having trouble accessing the Archive List at =
l2tp@l2tp.net.&nbsp; The</FONT>

<BR><FONT SIZE=3D2>connection is timing out.</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01BFFB2F.BCCA25E4--


From owner-l2tp@diameter.org  Mon Jul 31 23:01:21 2000
Received: from charizard.diameter.org (nobody@c900656-a.plstn1.sfba.home.com [24.20.167.220])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA12805
	for <l2tpext-archive@odin.ietf.org>; Mon, 31 Jul 2000 23:01:20 -0400 (EDT)
Received: (from majordomo@localhost)
	by charizard.diameter.org (8.10.0/8.10.0) id e6VNFsJ24905
	for l2tp-list; Mon, 31 Jul 2000 16:15:54 -0700
X-Authentication-Warning: charizard.diameter.org: majordomo set sender to owner-l2tp@diameter.org using -f
Received: from ns1.sailpix.com (ns1.sailpix.com [155.53.1.250])
	by charizard.diameter.org (8.10.0/8.10.0) with ESMTP id e6VNFdd24899
	for <l2tp@l2tp.net>; Mon, 31 Jul 2000 16:15:39 -0700
Received: from mailman.cisco.com (mailman.cisco.com [171.68.225.9]) by ns1.sailpix.com (8.8.8/8.6.9) with ESMTP id QAA23705 for <l2tp@ipsec.org>; Mon, 31 Jul 2000 16:19:34 -0700 (PDT)
Received: from anfreema-pc (dhcp-l21-163.cisco.com [171.68.210.163])
	by mailman.cisco.com (8.9.3/8.9.1) with SMTP id QAA14257;
	Mon, 31 Jul 2000 16:19:00 -0700 (PDT)
Message-Id: <200007312319.QAA14257@mailman.cisco.com>
X-Sender: anfreema@sj-email
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.2 
Date: Sun, 30 Jul 2000 16:18:13 -0700
To: l2tp@ipsec.org, ietf-ppp@merit.edu, ipsec@lists.tislabs.com
From: Anita Freeman <anfreema@cisco.com>
Subject: Update for Sept 2000 VPN Interoperability Workshop
Mime-Version: 1.0
Content-Type: multipart/alternative;
	types="text/plain,text/html";
	boundary="=====================_18187235==_.ALT"
Sender: owner-l2tp@diameter.org
Precedence: bulk

--=====================_18187235==_.ALT
Content-Type: text/plain; charset="us-ascii"


First a reminder to make your hotel reservations for the VPN Interoperability
Workshop, September 18-22, 2000 at the Paradise Point Resort in San Diego,
California.  The reservation number is 800-344-2626.

Please register under the VPN Workshop room block for the discounted rate of
$159 per night (plus tax).  The cutoff date for this room block is August 15th.

There are a few modifications to the application and schedule for the September
2000 VPN Workshop.

The application for the workshop has been moved to a new server and is now
available at:

http://209.249.66.84/vpnworkshop/

On Tuesday evening, September 19, 2000, the California Broadband User's Group
will sponsor an appreciation event for the workshop attendees.  At 7 PM we will
board a Sternwheeler, the William D. Evans, at the Bahia Resort Hotel for a two
hour cocktail cruise in San Diego's Mission Bay.  

The cruise will replace the reception originally scheduled for September 20,
2000.

The VPN Workshop is being sponsored by VeriSign, SSH, Hi/fn, WindRiver,
Entrust, Nokia, Alcatel, RedBack, Microsoft, Cisco, and UUNET, a Worldcom
Company.

The protocols being tested at this workshop are:

IPsec
IKE
IPComp
L2TP over Transport-Mode IPsec
PPTP
PPPoE
PPPoATM
L2TPoATM

Thanks, Anita Freeman


--=====================_18187235==_.ALT
Content-Type: text/html; charset="us-ascii"

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

--=====================_18187235==_.ALT--



